Ericsson 3G Chapter 3 (Service Accessibility) - WCDMA RAN Opt - P7

WCDMA RAN P6 Optimization
Chapter 3: Service Accessibility

Chapter 3 Objectives
After this module, the participants will be able to:
1. Explain the function of Idle Mode Behavior,

2. Explain the function and impact of admission control
3. Explain the function and impact of congestion control
4. Explain the function and impact of load sharing
5. Explain which counters and formulas to use in order to retrieve the
worst cells
6. Explain techniques for troubleshooting Accessibility KPIs,
clustering and drill through statistics analyze.
7. Analyze data from real networks and propose changes in order to
improve the network performance related to retainability
© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

. A Figure2 3 - Service Accessibility
Accessibility

Accessibility
Accessibility is defined as the ability of a user to obtain

requested service from the system.

UMTS - Hierarchy of Bearers
UMTS
TE MT UTRAN CN Iu CN TE
TE MT UTRAN CN Iu CN TE
edge Gateway
edge Gateway
node
node
End-to-End Service
TE/MT Local UMTS Bearer Service External

Bearer Service Bearer Service
Radio Access Bearer Service CN Bearer

Service
Radio Bearer Iu Bearer Backbone

Service Service Bearer Service
UTRAN Physical
RAB FDD/TDD Bearer
Service Service
3GPP TS 23.107, QoS Concept and Architecture

Uu Protocol Structure
NAS – Non Access Stratum
RRC – Radio Resource Control
Control Plane RLC – Radio Link Control
MAC – Medium Access Control
PDCP – Packet Data Convergence Protocol
NAS BMC – Broadcast/Multicast Control
User Plane
User Radio Bearers

Control Layer 3 Network Layer
RRC
Control
Measurements
Control
Signaling Radio Bearers PDCP BMC
RLC
RLC Data Link Layer
Layer 2
Logical Channels
MAC
Control
Transport Channels
Physical
PhysicalLayer
layer Layer 1

A mobile originating call setup
workflow
MS Originating Call Setup
Random Access
RRC Connection Setup
NAS procedures:
Service Request
Authentication
Security
RAB Assignment

Service Accessibility Workflow
Other Modules
Recommendatio
Performance Performance Verification of
n&
Measurements Analysis changes
Implementation
Idle mode Squal, Srxlev,

Alarms qQualmin, qRxLevMin,
Cell Availability RRC Connection
Random Access maxTxPowerUl, t3212,
NAS t3312, aichPower,
Counters powerOffsetP0,
RAB Assignment
preambleRetransMax,
constantValueCprach
pmTotNoRrcConnectCsSucc
pmTotNoRrcConnectPsSucc
pmNoRabEstablishAttempt<RAB>
pmNoRabEstablishSuccess<RAB>
pmNoPageDiscardCmpLoadC
pmNoPagingAttemptUtranRejected

Performance Measurements

Performance Measurements
Worst Cells – 1st and 2nd KPI
There are two categories of KPIs:
 1st category KPIs is to identify which cells or RBSs having accessibility

problems (e.g. RRC connection successful rate and RAB establishment
successful rate)
 2nd category KPIs is to imply the reasons of failures (e.g. cell down time
and admission control deny).
1. In order to find areas with high RRC or RAB establishment failures, the
1st category KPI’s should be used to identify the 10-15 worst performing
cells and their surrounding cells.
2. Afterwards, using 2nd category KPIs estimates the reasons of failures.

. A Figure103 - Service Accessibility
CS Accessibility

Accessibility – Worst performing
cells
• UE may perform cell re-selection during RRC Connection
• It may repeat RRC Connection Request message N300

times which may arrive at different cell,
• There is a chance that access success rate for some cells

may show larger than 100% success rate.

cells
 Which setup success rate should be used for finding
worst cells?
 If the optimization strategy is to handle all the worst
cells regarding a certain service, then formulas for each
service should be used.
 pmTotNoRrcConnectReqCsSucc   pmTotNoRabEstablishSuccess  RAB  

    
 pmTotNoRrcConnectReqCs - pmNoLoadSharingRrcConnCs   pmTotNoRabEstablishAttempt  RAB  - pmDirRetry 
Where <RAB> = Speech, CS64 or CS57

cells
 pmTotNoRrcConnectReqCsSucc   pmTotNoRabEstablishSuccess  RAB  
    
 pmTotNoRrcConnectReqCs - pmNoLoadSharingRrcConnCs   pmTotNoRabEstablishAttempt  RAB  - pmDirRetry 
• exclude directed-retry to GSM from the RAB establishment

attempt, so that it is not counted as access failure on WCDMA
RAN.
• The load-sharing with GSM from the RRC Request

Success can also be removed.

cells
Especially for AMR calls:
 pmTotNoRab EstablishSuccessAmrNb 
100   
 pmTotNoRab EstablishAttemptAmrNb 
The percentage of AMR calls compared to the normal speech

calls:
 pmTotNoRab EstablishSuccessAmrNb 
100   
 pmTotNoRab EstablishSuccessSpeech 

cells
Especially for HS calls:
pmTotRrcCo nnectReqPsSucc(UtranCell) ptnNoRubEstablishSuccessPacketInteractiveHs(UtranCell )
HS _ A(UtranCell )  100 %  
ptnTotNoRr cConnectReqPs(UtranCell) ptnNoRubEstablishAttemptPacketInteractiveHs (UtranCell )
The percentage of EUL calls

pmTotNoRrc ConnectReqPsSucc(UtranCell ) pmNoRubEstablishSuccessPacketInteractiveEal (UtranCell )
EUL _ A(UtranCell )  100 %   pmNoRubEstablishAttemptPacketInteractiveEal (UtranCell )
pmTotNoRrc ConnectReqPs (UtranCell )

Performance Analysis

Idle mode tasks
 PLMN selection and reselection
 Cell selection and reselection
 Location area (LA) and routing area (RA) registration
 Paging procedure
 Reading system information

The Idle mode tasks
Automatic/Manual Indication to user
mode selection
PLMN Selection
PLMN selected PLMNs

available
LR Response
Cell Selection/Reselection
Registration
area changes
Location
registration

PLMN Selection
PLMN selection is the first step in the registration process that
allows a UE to carry out or receive services from an operator.
The UE normally operates on its home PLMN. However, a Visited

PLMN (VPLMN) may be selected if the UE loses coverage.
A UE successfully registers on a PLMN if it finds a suitable cell to

camp on within the selected PLMN. The UE displays to the user
that this PLMN is registered. When a UE does not find a suitable
cell in the selected PLMN, it tries to camp on any other acceptable
cell within an allowed PLMN.

Determination of Cell Selection
Criteria • qQualmin
CPICH • qRxLevMin
• Qqualmeas • maxPowerul
• Qrxlevmeas P-CCPCH
Squal = Qqualmeas- qQualMin > 0

Suitable
cell Srxlev = Qrxlevmeas – qRxLevMin – Pcompensation > 0
Where Pcompensation = max(maxTxPowerul – P;0)

Determination of Cell Selection Criteria
Details
• qQualmin is sent in the broadcast information (SIB 3 for
serving cell and SIB 11 for adjacent cells) and indicates the
minimum required quality value. The UE measures the
received quality, “Qqualmeas”; on the CPICH (CPICH Ec/No)
and calculates Squal. This is only done for WCDMA cells.
• qRxLevMin is also sent in the system information (SIB 3

for serving cell and in SIB 11 for adjacent cells) and indicates
the minimum required signal strength. The UE measures the
received signal Code Power (CPICH RSCP) and obtains
Srxlev

Details
• maxTxPowerUl is the maximum transmission power
during random access on the RACH and that value is sent in
the system information (SIB 3).
• P is the UE maximum output power according to its class.

Details
Details
• The UE shall measure the CPICH Ec/No and the CPICH

RSCP of the serving cell and evaluate the cell selection
criterion, S, at least every DRX cycle.
• The UE shall filter the Ec/No and RSCP measurements of

the serving cell using at least two measurements.

Details
Parameters
To control the cell size in Idle mode use
qHyst - (presented by qHyst1 and qHyst2) are added to the

measured values of the serving cell. These parameters
expand the cell borders of the serving cell in order to avoid
ping-pong effects
qOffset – (qOffset1 or qOffset2) add an offset value for a

cell-to-cell relation that are used to move the borders
between the cells.

HCS feature
The P6 Hierarchical Cell Structures (HCS) optional feature
makes it possible to control camping of UEs in Idle mode and
in states CELL_FACH and URA_PCH, not only according to
best cell using the measurement quantity CPICH RSCP or
CPICH Ec/No, but also according to cell hierarchy.
The use of HCS is controlled by the cell parameters
hcsUsageidleMode
and
hcsUsageconnectedMode

HCS feature
Priority is defined by an integer between 0 and 7.
HCS priority level 0 is the lowest priority and level 7 is the

highest priority.
The HCS priority level for the serving cell is configurable and
set by parameter:
hcsSib3Config.hcsPrio
and for inter-frequency neighbor relations
For intra-frequency and GSM cell relations no HCS priority

level can be configured,default value of 0 applies.
HCS Priority Example
HCS feature
Priority
0-7
7
Example = 7
Priority Priority
7 7
Priority
0
Default
Priority Priority
0 0
0-7
Example = 0
Serving Cell hcsSib3Config.hcsPrio
ricsson AB 2007 LZU 108 6911 R1A Figure 3-6 P6 Radio Network Features
HCS feature
Once camped on the cell the UE will look for
hcsUsage.idleMode in SIB 11
and
hcsUsage.connectedMode in Sib 12
If these are set to ‘TRUE (1)’ cell reselection will be based on

the HCS criteria.

HCS feature
The UE performs ranking of all cells with highest HCS_PRIO
among the measured cells fulfilling the S- and H-criteria
S > 0 and H ≥ 0
If no cell fulfils the H-criteria, the UE shall not consider the

HCS priority when ranking the cells.
The UE ranks the cells according to the R-criteria
S>0 and R > 0

Cell Reselection (H-Criteria)
H-criteria Serving cell hcsSib3Config.qHcs
RSCP or Ec/No 0 to 99, Default = 0
H(s) = Qmeas(s) - Qhcs(s) ≥ 0

H(n) = Qmeas(n) - Qhcs(n) - TO(n)* ≥ 0
Neighbor cell hcsSib11Config.qHcs
RSCP or Ec/No 0 to 99, Default = 0
Used when qualMeasQuantity = 1 (CPICH RSCP) 0 to 60 s
infinity, 3, 6, 9, 12, 15, 18, 21 dB, Default = infinity dB Default= 0 s
hcsSib11Config.temporaryOffset1
*TO(n): OR applied for hcsSib11Config.penaltyTime
hcsSib11Config.temporaryOffset2
Used when qualMeasQuantity = 2 (CPICH Ec/No)

infinity, 1, 3, 4, 6, 8, 10, 12 dB, Default = infinity dB
H≥0 H≥0 H≥0 H≥0

H≥0 H≥0 H≥0 H≥0
H≥0 H≥0 H≥0
Cell Reselection (R-Criteria)
R-criteria Priority 7
Used when qualMeasQuantity = 1 (CPICH RSCP) R(neighbor)
0 to 40 Default = 4 Rank 1
qHyst1
R(serving) =
R(serving) = Qmeas(s)
Qmeas(s) +
+ or + Qoffmbms
+ Qoffmbms*1 Priority 7
qHyst2 R(neighbor)
Rank 2
0 to 40 Default = 4 Priority 7
Used when qualMeasQuantity = 1 (CPICH RSCP)
R(neighbor)
-50 to 50 dB Default = 0 dB (WCDMA) 7 dB (GSM) Rank 3
qOffset1sn
R(neighbor) = Qmeas(n) --
R(neighbor) = Qmeas(n) or + Qoffmbms
+ Qoffmbms11 -- TO(n)
TO(n)22 ‘treSelection’
qOffset2sn (2 sec default)

-50 to 50 dB Default = 0 dB
Qoffmbms = qualityOffset parameter for
1 2
H-criteria
MBMS. Not used with HCS temporary offset

Qmeas mapping
Qmeas Mappings
standard mappings from TS25. 133
Qmeas value Measured quantity value Unit
CPICH_RSCP_LEV _-05 CPICH RSCP <-120 dBm

CPICH_RSCP_LEV _-04 -120  CPICH RSCP < -119 dBm
CPICH_RSCP_LEV _-03 -119  CPICH RSCP < -118 dBm
… … …
CPICH_RSCP_LEV _89 -27  CPICH RSCP < -26 dBm
CPICH_RSCP_LEV _90 -26  CPICH RSCP < -25 dBm
CPICH_RSCP_LEV _91 -25  CPICH RSCP dBm
Qmeas value Measured quantity value Unit
CPICH_Ec/No _00 CPICH Ec/Io < -24 dB

CPICH_Ec/No _01 -24  CPICH Ec/Io < -23.5 dB
CPICH_Ec/No _02 -23.5  CPICH Ec/Io < -23 dB
… … …
CPICH_Ec/No _47 -1  CPICH Ec/Io < -0.5 dB
CPICH_Ec/No _48 -0.5  CPICH Ec/Io < 0 dB
CPICH_Ec/No _49 0  CPICH Ec/Io dB
Ericsson AB AB
© Ericsson 2007
2008LZU 108 6911
03_03813 LZUR1A
108 6924 Uen Rev
. A Figure
Figure3333--8 P6 Radio
Service Network Features
Accessibility
Qmeas mapping - HINT
What if both WCDMA and GSM cells fulfill the ‘S-criteria’?
• first ranking is made using the measurement quantity CPICH

RSCP.
• If a GSM cell is ranked as the best candidate, the UE

performs cell reselection to that cell.
• If a WCDMA cell is ranked as the best candidate and the

measurement quantity for cell reselection is set to CPICH
RSCP, the UE performs cell reselection to that cell.

Qmeas mapping - HINT
• If a WCDMA cell is ranked as the best candidate and the
measurement quantity for cell reselection is set to CPICH
Ec/No, the UE performs a second ranking of the WCDMA cells
based on CPICH Ec/No.
The UE reselects the new cell if it is better ranked than the

serving cell during a time interval ‘treSelection’ which can be
set from 0 to 30 seconds with a default setting of 2 seconds.

Qmeas mapping - Suggestions
Suggestions:
1. have HCS turned ON for UEs in Idle Mode but turned OFF
for UEs in Connected Mode.
2. Cells in the non-HSDPA layer (frequency band) shall be set

to higher priority than the cells in the HSDPA layer.
With this setting most UEs will prefer to camp on the non-
HSDPA carrier.
With HCS turned OFF in Connected Mode, UEs in Cell_FACH

or URA_PCH states will not easily leave the HSDPA layer.

Cell update procedure
Cell update procedures can happen at:
• cell update in the same cell (periodic update),
• cell update in a new cell (cell reselection),
• cell update during channel switching
• cell update during RAB establishment.

Cell update procedure
The success rate for cell updates can be found with the
following formula:
pmNoCellUpdSuccess
100 
pmNoCellUpdAttempt
pmNoCellUpdSuccess - Total number of successful cell

updates (periodic and cell reselection, RNC Cell Update
procedure for Cell Reselection or Periodic Cell Update
completed successfully.
pmNoCellUpdAttempt - Total number of attempted cell

update procedures (periodic and cell reselection, RRC Cell
Update message received with Cell Update Cause = Cell
Reselection or Periodic Cell Update)
Location and Routing Area update
There are three types of LA and RA registration updates:
1. International Mobile Subscriber Identity (IMSI) attach or detach
2. Normal LA and RA updating
3. Periodic LA and RA updating

Periodic Registration
UE moves to UE moves to
UE in idle mode connected mode idle mode
t3212 t3212
LA Update LA Update LA Update
Periodic registration (LA and RA updating) is used to locate the UE to avoid

unnecessary paging attempts for a UE that has lost coverage and is not able
to inform the CN that it is inactive.
Timer t3212 controls the periodic LA update procedure
Timer t3312 controls the periodic RA update procedure
RRC Service State Description
CELL_DCH state
UE is known by its serving RNC (SRNC), on cell level or active

set level. UE has been allocated a dedicated channel. Dedicated
control channels (DCCH) are used for control signaling and a
dedicated traffic channel (DTCH) is used for user data
transmission. DCCH and DTCH are mapped onto dedicated
transport channels (DCH).
For multimode terminals (WCDMA – GSM/GPRS) it is possible to

perform Inter Radio Access Technology handover (IRATHO)
(WCDMA to GSM) and Inter Radio Access Technology Cell
Change (IRATCC) (WCDMA to GPRS).
HS-DSCH can only be operated in CELL_DCH state

CELL_FACH state
UE has no dedicated channel allocated.
UE uses the common channels, RACH and FACH, for signaling

messages and small amounts of data (best effort).
The UE is known on cell level in the RNC and need to send Cell
Update messages to RNC every time it selects a new cell. In this
state the UE need to decode system information, which is mapped
on FACH.

CELL_PCH state
The UE is known on a cell level in the SRNC for CELL_PCH, but

it can only be reached via the Paging Indicator Channel (PICH).
Therefore is the battery consumption of the UE very low because
the PICH includes Discontinuous Reception (DRX) functionality.
If the network wants to initiate any activity, it first needs to page

the UE. When the UE receives the paging it changes to the
CELL_FACH state, and performs a Cell Update. Whenever the UE
wants to initiate any activity it triggers a switch to the CELL_FACH
state by performing a Cell Update

URA_PCH
The URA_PCH state is similar to the CELL_PCH state.
The difference is that the UE does not execute Cell Update

after Cell reselection, but instead it reads the UTRAN
Registration Area (URA) identities from the broadcast channel
and only when URA changes, the UE performs a URA Update.
URA Update is also initiated when the UE enters a cell that has
no URAs defined. This will trigger a release of the RRC
Connection and the UE enters Idle mode.

URA update
In state URA_PCH, the procedure URA Update is used to keep WCDMA
RAN informed about the UEs location on a URA level.
As part of a supervision mechanism, URA Update is performed periodically.

The periodicity is controlled by the timer t305.
The success rate of the URA update can be found with the following
formula:
pmNoUraUpdSuccess
100 
pmNoUraUpdAttempt

Paging
Paging is initiated upon request from the CN (when UE is in idle
mode) or triggered in UTRAN
It is used to notify the UE of different events

These events are:
UE terminating service request for PS or CS services (CN

initiated). CN initiated paging is applicable to UEs in idle
mode.
UTRAN initiated broadcast to inform UEs when System

Information is modified. UTRAN initiated paging is used
whenever System Information has been updated (e.g.
information about cell selection/ reselection,
addition/replacement of neighbours, handover etc).

Paging
The paging message has the following characteristics:
• Type of paging message: Paging Type 1 or Paging Type 2
• UE identity used in the message (IMSI, TMSI, P-TMSI,

changing in length)
• The physical radio channels and type of resource required
• The area in which the page will be broadcasted (LA, RA or

globally)

Paging
The paging message type 1:
UE in Idle Mode
A PCH frame carries one “Paging Type 1” message of 10 ms
It may contain between 3-5 paging records depending on

whether the paging uses IMSI or TMSI/P-TMSI.
The paging message type 2:
UE in Cell_FACH or Cell_DCH (common or dedicated

physical channels are already in use)
Used for Broadcasting of System Info changes

Paging success rate in MSC
If the operator wants to check the paging success rate, this should be
done on MSC level.
Successful First and Repeated Page attempts of total number of first

attempts.
Paging success rate in a MSC:
 NPAG1RESUC C  NPAG2RESUC C 
100   
 NPAG1GLTOT  NPAG1LOTOT 

Paging counters and formulas
RAN considerations
Total number of pages discarded due to central MP load control for a
RNC pmNoPageDiscardCmpLoadC
Pages request rejection for a cell pmNoPagingAttemptUtranRejected
Paging intensity per cell in a RNC (if RNC, LA and RA consist of exact
same cells):
pmCnInitPa gingToIdle UeLa  pmCnInitPa gingToIdle UeRa  pmCnInitPa gingToIdle Ue

measuremen t period  total number of cells in that RNC
Check next slide

The Paging counter flowchart
Dashed arrows and boxes considers the packet switched
paging.
For all counter flow, the following are applied:

RBS counters: <Counter Name> (Green colour)
RNC Counters: <Counter Name> (Blue colour)
MSC Counters: <COUNTER NAME> (Orange colour, capital
letters)
Exceptions, Failures:
Successful Outcomes:
Counter Scope: (Scope) <Counter Name>

The Paging counter flowchart
RNC received Paging
message from the CN
Connected
Check UE
(RNC) pmcNoPagingAttemptCnInitDcch + status
Idle
RNC Sends to the UE Yes
Paging Type 2 Message MP
Overload?
No
(RNC) pmcNoPagDiscardCmpLoadC +
Yes
Paging is not Sent Paging Area is
a defined LA?
No (RNC) pmCnInitPagingToIdleUeLA +
Yes Paging Area is

a defined RA?
(RA) pmcnInitPagingToIdleUeRA + No
(RNC) pmInitPagingToIdleUE +

Paging counter flow (cont)
No (RNC) pmCnInitPagingToIdleLA +
Yes
Paging Area
is a defined
(RA) pmCnInitPagingToIdleUeRA +
RA?No
Area is a
defined URA?
Yes
pmCnInitPagingToUraUe + No
(RNC) pmCnInitPagingToIdleUE +
Yes
Paging que
full?
(Cell) pmcnInitPagingAttemptUtranRejected + No
Paging is not Sent Paging is Sent

System Information
The system information explains to the UE how to behave in
the cell (parameters).
The system information elements are broadcasted in System

Information Blocks (SIB) where it groups together system
information elements of the same nature
A Master Information Block (MIB) gives references to a number

of SIBs in a cell, including scheduling information for those
SIBs (If a change in System information has occurred, the MIB informs the UE by assigning
value tags for each SIB. This is to prevent unnecessary decoding of same information)
SIBs are organized as a tree . SIB messages are sent on

BCCH logical channel
FACH transport BCH transport
UEs in Cell_FACH UEs in idle mode, Cell_PCH URA_PCH
System Information
The table below contains a description of the information that is carried
by the MIB and the SIBs
SIB SIB SIB SIB SIB SIB SIB
Contents MIB
1 2 3 5 7 11 12
PLMN Identity X
LA and RA updating X
Cell Selection / Reselection
X X
Parameters
Power Control on Common
X
Channel
Paging Parameters X
URA Identity list X
Measurement Management X X
Cell and common channel
X
configuration
Timers and counters in Idle mode X
Random Access Process

Random Access
General process
The UE is in idle state => it sends the RRC Connection Request

message.
The RNC has correctly received the request over the Random
Access Channel (RACH).
If the RNC does not receive the RRC Connection Request

message the UE returns in Idle state

Random Access – RRC connection
establishment

Random Access counter flow
Problem: There is no statistic counter to directly present

random access procedure failure behavior.
Solution: The preamble or AICH counters can be analyzed in

order to determine the probability of occurring random access
procedure failure problem.

Random Access counter flow
Case: Maximum allowed attempts (N300=5) has been reached
Reason: cause of failure is that
1. either RBS has blocked the access (negative AICH)
2. or preambles sent by the UE are not received
3. or ignored (no AICH is sent)
4. or UE does not receive the AICH positive for any reason

(power control).

Random Access - AICH

e AICH process
The UE transmits a preamble with an initial transmit power

sed on the open-loop estimate but modified by a predefined
gative power offset.
After transmission of the preamble, the UE checks for the

ception of an Acquisition Indicator (AI) on the downlink
quisition Indicator Channel (AICH). The AI is transmitted on the
ception of a sufficiently strong preamble.
If no AI is detected, the UE retransmits the preamble with a

edefined increase in the transmit power.
If a positive AI is received, the UE transmits the random-access

essage.
REMEMBER:
1. AICH is not continuously broadcast in the cell.
2. Its power, aichPower, is expressed as an offset relative to the PCPICH power.

Random Access Counter flow
Random Access is NAttempts =0
the same for every
kind of service: CS, NAttempts =+1
PS, Registrations,
Signalling, SMS,
etc. NAttemptsi >
Yes Random
N300 (=5)? Access
No
Failure
UE sends preambles
sequences
No response is sent
and/or received by Negative AICH is sent
UE over AICH
(Cell) pmNegativeMessages +
Positive AICH is sent

(Cell) pmPositiveMessages +
UE does not receive
positive AICH
(Cell) pmFaultyTransportBlocks +
UE receives positive
AICH

Random Access counter flow (cont)
UE does not receive
positive AICH
(Cell) pmFaultyTransportBlocks +
UE receives positive AICH
UE sends message
“RRC Connection Request”
RNC does not receive

the message RNC receives the message
(Cell) pmTotNoRrcConnectReq +
(Cell) pmTotNoRrcConnectReqCs +
(Cell) pmNoRecRandomAccSuccess +
(Cell) pmTransportBlocks +

Negative AICH - explanation
UE uses Transport Channel RACH (Random Access Channel)
to access the UTRAN.
Information about available sub-channels and available

preamble signatures according to ASC (Access Service
Class) is included in PRACH (Physical RACH) information (or
PRACH information).
According to the PRACH information, a preamble signature

is assigned to a UE depending on what ASC the UE intends to
use on an available RACH sub-channel. The preamble
signature is determined uniformly, randomly based on the IMSI
(International Mobile Subscriber Identity) of the UE and time
information.

After the preamble signature is determined, access slots
for the preamble are determined.
UE transmits to the UTRAN the preamble with the determined

signature in the access slots with predetermined power.
UTRAN checks for the signatures and determines whether an

RACH corresponding to the preamble signature is already in
use.
If the RACH is not used UTRAN transmits the AICH to the UE.
If the RACH is in use, the UTRAN transmits a negative AICH to

the UE
Random Access - Reselection
Attention!!!!
During the RACH procedure, the UE is allowed to make a cell

reselection.
In case of cell reselection or when the response from the

RNC is delayed more than T300 (=1 sec) more than one
RRC Connection Request could be sent to the RNC.
Only the first attempt is counted by pmTotNoRrcConnectReq

and pmTotNoRrcConnectReqCs counters.

Random Access - TEMS Investigation
In case trouble-shooting drive test is done, from TEMS, the

symptoms of this problem are:
1. UE repeatedly prepares RRC connection request messages in L3.
2. UE camps onto a cell and does not change cells.
3. UE does not receive RRC connection setup or RRC connection

reject message.

Random Access – Optimization Hints
Statement
Random access problems => UE TX power does not reach

to the maximum allowed UE TX power.
Reason: UL/DL unbalance or swapped feeders.
1. UL/DL unbalance => “too large CPICH power setting”,

“imbalance in UL/DL feeder loss”, “high UL RSSI noise rise”
and “cell down”.
2. Also verify if there is any mistake in the antenna system

configuration and feeder attenuation settings in the system.

Random Access – Optimization Hints
3. If the preamble and RACH message part are wrongly
recognized or lost, it could also be that the AICH power is not
large enough.
Solution: check if the aichPower is set as default. If needed,

increase aichPower.

WCDMA Power Control
WCDMA Power Control
BLE R:Blo ck E rror Ra te
SIR: S ignal to Inte rfer ence Ratio Uplink
Uplink SIR target outer loop
TPC: Transmit Po wer Control
BLER-Measured
Inner loop
SIR-Target
Downlink TPC modified
Uplink
TPC Uplink SIR-Target
Downlink Uplink SIR error
Downlink SIR target
outer loop
RNC
BLER-Measured Open loop
SIR-Target Starting power
modified
1/ 038 13 - EN/LZU 108 5686 PA3 22 WCDMA Radio Network Functionality

Open Loop power control
The aim of open loop power control in the uplink is to ensure
that new connections are established causing minimum
interference.
Using open loop power control in the downlink will minimize

the power used to setup a connection thus maximizing the
capacity.

Uplink Open Loop Power Control
Dedicated channel at just enough power Connection

established
with minimum
interference
to other users
wer
UE 1 po
ted
ula
l c
1) UE measures Pilot t ca
a
its
2) Reads interference nsm 4) The power is ramped
level from Broadcast Tra up until a response is
channel 3)
heard or maximum
number of re-attempts is
reached
RBS
UE 2
Downlink Open Loop Power Control
Dedicated channel at just enough power
wer
po
ted
ula
alc 1) Uses
c
s at parameters to
it calculate
UE 1 m
ans required power
) Tr
2
3) The power is ramped
up until a response is Minimum downlink
heard or until a certain power used to setup a
maximum power is connection thus
reached maximizing downlink
capacity
UE 2 RBS

RACH Preamble Power Setting
The UE will transmit its first RACH preamble at a PRACH
Calculated power (P_PRACH).
After the first preamble, if no acknowledgement is received for the

successive preambles, a preamble power ramping is adopted with
step equal to the parameter ‘powerOffsetPO’ which may be set
between 1 and 8 dB in steps of 1 dB. default value is 3 dB
Each preamble will be ramped up by 3 dB from the previous

until an Acquisition Indication Channel (AICH) is received or the
maximum number of attempts has been made.
Maximum number of attempts is set with the parameter

‘preambleRetransMax’, which can be set from 1 to 64 with a
default of 8.
RACH Preamble Power Setting
If the maximum number of attempts has been exceeded another
preamble cycle may be started and a new value for P_PRACH
calculated. The maximum number of preamble cycles is set with
the parameter ‘maxPreambleCycle’ which can be set from 1 to
32 (default = 4).
If a positive AICH is received the UE will transmit the RACH

message at a power above the last preamble by a value set by
Parameter ‘powerOffsetPpm’ (Range [ –5,10 dB] in steps of
1 dB, default value of –4dB).

RACH Preamble Ramping
powerOffsetPO powerOffsetPpM
2
nd
Preamble
UE
1st
P_PRACH Control Part
Preamble
AICH AICH
powerOffsetPO = 1 to 8 dB default = 3 dB
powerOffsetPpM = -5 to 10 dB default = -4dB
preambleRetransMax = 1 … 64 default = 8
RBS
maxPreambleCycle = 1…32 default = 4

Open power control
Criteria to be fulfilled:
powerOffsetP0 x preambleRetransMax + constantValueCprach >= predefined preamble threshold
and
n x powerOffsetP0 + powerOffsetPpm >= 0 , n belongs [0, preambleRetransMax]
Preamble is detected but there is

Signal-to-interference ratio of all
no enough energy in message
access attempts above the
part, due to noise on the random
preamble threshold on RACH for a
access channel for a carrier:
carrier:
pmNoPreambleFalseDetection
pmReceivedPreambleSir and
Number of samples of
or
pmReceivedPreambleSir
pmNoPreamb leFalseDet ection
100%
pmPositive Messages

Open power control
n case of RACH problems due to power control, check if the
arameters are set properly.
. increase constantValueCprach (by tuning offset C)
ConstantValueCprach = SIR_TARGET_RACH - 10 logSF +C
r/and
. Increase powerOffsetPpm

RRC Connection counter flow
RRC Connection
The UE always initiates the establishment of an RRC

connection by sending the RRC Connection Request
message
Inside this message there always exist an establishment code

(Emergency call, Registration, Originating Call, IRAT Cell
Reselection...).

RRC Connection counter flow
RNC receives the message
After RRC Connection Establishment message, RRC Connection is
RRC Connection Request
assigned an U-RNTI (PLMN-unique), that is SRNC identity and an
idle S-RNTI (RNC-unique). A UE context is established for this UE.
UE context allocation
Context allocation failure
OK
(Cell) pmNoOfRedirectedEmergencycalls + Emergency Call

Redirection of
Emergency Call
No
(Cell) pmNoRejRrcConnMmpLoadC + Processor Load control (MP)

Access not
allowed OK
Access not
(Cell) pmNoReqDeniedAdm + allowed Admission Control
Access not allowed
OK
Load Sharing Multifrequency Load Sharing
Load Sharing
RRC Redirection
No
(Cell) pmTotNoUtranRejRrcConnReq + Channel code allocation

(Cell) pmNoDlChCodeAllocAttemptSf128 +
Admission Control algorithm checks if the new radio link can
be allowed in the cell
Code Control algorithms allocate the uplink scrambling code, downlink scrambling code
and downlink channelization code.
RRC Connection counter flow (cont)
Channel code allocation

Code not available (Cell) pmNoDlChCodeAllocAttemptSf128 +
(Cell) pmNoDlChCodeAllocFailureSf128+ OK
(UL BBP) pmSetupFailureSf64 + Radio Link Setup

RAX or TXB (UL BBP) pmSetupAttemptsSf64 +
(DL BBP) pmSetupFailureSf128 +
Congestion (DL BBP) pmSetupAttemptsSf128 +
(Cell) pmNoFailedAfterAdm +
AAL2 Setup
AAL2 Failure
(Cell) pmTotNoUtranRejRrcConnReq +
OK
RNC sends the message RNC sends the message

RRC Connection Reject RRC Connection Setup

RRC Connection – Emergency Calls
The following RNC counters, counts the number of successful
emergency positioning attempts excluding reattempts:
pmPositioningReqSuccEsAgps
 100%
pmPositioningReqAttEsAgps
AGPS = UE-Based Assisted GPS (AGPS) Positioning
Parameter agpsEnable= True in RNC

When AGPS feature is 'on' and in operation the following
parameter settings are needed in order for the call to have
the possibility to be served in UMTS and positioned by
UMTS:
ecCnSbhoRequestIgnore = TRUE,
ecLocationAttemptUmts = Yes.
When redirect of emergency calls to GSM feature = on,

the request to establish an RRC connection shall be rejected
for all UEs indicating 'Emergency call'.


RRC Connection – Emergency
Calls (cont)
The following RNC counter, counts the number of

successful emergency establishment attempts:
pmRabEstablishEcSuccess
100%
pmRabEstablishEcAttempt

RRC Connection – MP Load
RRC connection rejection rate due to module MP load control

for a cell could be found in the following formula:
pmNoRejRrcConnMpLoad C
100%
pmTotNoRrc ConnectReq - pmNoLoadSh aringRrcCo nn
One reason for MP load can be too many periodic registrations

(LA, RA updates)
RRC Connection – Admission control
WCDMA Capacity = Admission Control + Congestion
Control
Admission control blocks new incoming calls as well as

handover attempts when the load (power) in the system is
high, thus reducing the dropping probability
The admission decision is based on air interface load, by using

measurements of uplink interference, downlink output power
as well as the actual number of users.

Admission control is together with Congestion control
WCDMA Capacity Management (Admission Control)
part of the WCDMA Capacity Management.
Admission
limit
Cell Load
RBS
The UE is blocked because the cell load has reached the

1/ 038 13 - EN/LZU 108 5686 PA1 22 WCDMA Radio Network Functionality
defined ‘admission limit’

Problems with Admission Control
Admission Control blocks due to improper admission threshold

settings.
There are nine admission policies to control the blocking:
UL ASE, DL ASE,
DL TX cell power, spreading factor usage,
code usage, Hw usage,
amount of HS users, congestion
number of users in compressed mode.
Understanding of which cause(s) to trigger blocking is

necessary to solve the problem.
RRC Connection – Admission
control (cont I)
RESOURCE REQUEST
Is admission control YES, then
blocked by congestion block
control?
NO, then
accept
NO YES, then
YES, then block
block Requested + est # compressed Requested HW + estimated
mode RL > CompModeAdm HW > ulHwAdm
NO NO
YES, then YES, then
block Requested + estimated code Requested + estimated # HS block
usage > DlCodeAdm users > hsdpaUsersAdm
NO NO YES, then
YES, then Sf = 8 block
block Requested DL SF + est. Dl Req. + est. # Eul users in serving
SF > SfXAdm, sf =16 cell> eulServingCellUsersAdm
sf = 32
NO NO
Requested ASE dl + est. ASE Requested + estimated # Eul users
dl > AseDlAdm in non serving cell > YES, then
YES, then
eulNonServingCellUsersAdm block
block NO
NO
Requested ASE Ul + est. Requested DL pwr + YES, then
YES, then ASE Ul > AseUlAdm estimated pwr > pwrAdm block
NO
block

The Admission’s Algorithm
• New resources are needed for a radio connection ( new

radio link set up or existing radio link modified),
• Admission Control function receives a request for

admission (specifies estimated amount of dedicated
monitored resources for that radio connection).
• Resource estimation is compared to the available

resources and the configured threshold limits for admission
set by the operator (i.e. ulHwAdm, hsdpaUsersAdm maximumTransmissionPower,
aseUlAdmOffset, beMarginAseDl, beMarginAseUl, beMarginDlCode, compModeAdm, dlCodeAdm)
, and a response is sent out to grant or deny the new radio

link access to a cell.
control (cont II)
Counter Description
pmNoReqDeniedAdm Number of RAB establishment and RRC requests denied due
to AC, both drifting and non-drifting UEs. This counter is
increased when admission is denied for radio resources.
pmNoFailedAfterAdm Number of RRC establishment requests and RAB
establishment requests failed after being admitted, both
drifting and non-drifting UEs. This counter is increased after
the admission is accepted for radio resources issue, but when
it is denied due to a shortage of transport network
resources/channel elements
pmNoRrcReqDeniedAdm Number of RRC requests denied due to AC, both drifting and
non-drifting UEs. This counter is increased when admission
is denied for radio resources.
When new resources are needed To decide on the requests, it requires

for a radio connection the information about the load and the
Admission Control function amount of resources needed by the
receives a request for admission requester.
ARP
The Capacity Management algorithms in the P6 RAN have
been improved allowing a much more flexible approach to
Admission and Congestion control.
Admission and Congestion control now use the Allocation

Retention Priority ARP of the RAB when making a decision to
allow or remove the connection.

ARP
Depending on the RANAP attributes the ARP table
determines:
• The priority level (1… 15) where value 15 means 'no priority'
and 1 is highest priority.
• The Pre-emption Capability Indicator (PCI) which consists of

two values, 'shall not trigger pre-emption' and 'may trigger
pre-emption' (this indicates the pre-emption capability of the
request).
• The Pre-emption Vulnerability Indicator (PVI) with the values

"not pre-emptable" and "pre-emptable". Note that the pre-
emption vulnerability indicates whether a RAB in the
connection can be released due to the admission of a higher
priority, pre-emption capable request or not.
ARP
The default mapping of the ARP attributes is based on the
traffic class (conversational, streaming, interactive,
background), CN indicator (CS/PS), Source Statistics
Descriptor (SSD) (speech).
The THP feature allows the setting of different priorities for

interactive packet data RABs, and for an interactive data with
THP = 1 a separate priority based on the Signaling Indicator
(SI) is allowed. Both the Traffic Handling Priority (THP) value
(1-3) and the SI (on/off) are received from the CN in the RAB
assignment request. .

Default ARP Mapping
Internal ARP RANAP Attributes
These
parameters
can be used
for ARP
Configuration:
•intPrio
•pci
•pvi
‘RAB Assignment
Request’ message
0 to 15 ecCnPriorityLevel
Default= 7
RNC CN

Default ARP Mapping
In the event of congestion, a request for a new connection
that produces ‘Yes’ for the ARP ‘Pre-emption Capability’ will
be allowed to drop an existing connection of lower
Allocation/Retention priority whose ‘Pre-emption Vulnerability’
is set to ‘Yes’.
The ARP mapping is the default mapping used when the

optional ‘Flexible Quality of Service and Allocation/Retention
Handling’ feature is not enabled.
This feature allows the Operator to configure their own
RANAP to internal ARP mapping.

. A Figure100
3- Service Accessibility
Default ARP Mapping
The admission request attributes are determined depending
on the parts for the radio connection for which additional
resources are needed.
For example, in case the radio connection includes a

conversational CS speech RAB and interactive PS RAB, a
reconfiguration of the interactive PS connection part would
lead to determination of the request attributes based on that
connection part only.
In case more connection parts are the basis for requested

attribute determination, the following is applied:

. A Figure101
Default ARP Mapping
The request class is ‘non-guaranteed’ if at least one of the
connection parts for which admission is requested is non-
guaranteed. For example when adding conv. CS Speech
(guaranteed) and Interactive PS 64/64 (non-guaranteed, as
PS 0/0 is a lower resource consuming alternative) the request
class is non-guaranteed.
The request priority is the highest ARP priority of the

connection parts for which admission is requested (for
example when requesting resources for conv. CS Speech
(priority 3) and Interactive PS (priority 7), the request priority is
3.
The preemption capability is set to capable in case at least
one of the connection parts for which admission is requested
is pre-emption capable.
. A Figure102
Default ARP Mapping
Resource requests will fall into one of four categories below:
1. guaranteed, non-handover
2. guaranteed, handover
3. non-guaranteed, non-handover
4. non-guaranteed, handover
MBMS is treated as guaranteed, non-handover.

. A Figure103
Default ARP Mapping Top ri
e
pt Resource Requests Categories corner
field-m
custom
e partne
pt See B
for exa
xt
pt
5
pt
‘Non-guaranteed’ if at least one connection part is ‘non-guaranteed’

ARP is highest of connection parts
‘Pre-empt capable’ if at least one connection part is ‘pre-empt capable’
© Ericsson AB 2007 LZU 108 6911 R1A Figure 3-11 P6 Radio Network Features

. A Figure104
RRC Connection – Congestion
Control
Congestion control is used to resolve overload in both the
uplink and the downlink.
Congestion due to radio overload in uplink is detected when
Uplink Received Total uplink congestion threshold
Wideband Power (RWTP) iFCong + iFOffset
For more than hysteresis time iFHyst.

. A Figure105
Control
Congestion Control considers uplink congestion to be

resolved when:
RTWP for a particular cell iFCong
For more than hysteresis time iFHyst.

. A Figure106
RRC Connection – Congestion Control
Congestion Control

. A Figure107
Control
Congestion control is used to resolve overload in both the uplink and the downlink.
It uses Power and RTWP (Received Total Wideband Power ) measurements.
Number of times congestion control is triggered due to high DL power for a cell:
pmSumOfTimesMeasOlDl
Number of times congestion control is triggered due to high UL interference for a cell:
pmSumOfTimesMeasOlUl
pmNoOfTermHsCong & pmNoOfIurTermHsCong - RNC counters monitoring no. of HSDPA

users released due to congestion
The total amount of time (sec) was congested in DL during a reporting period for a cell:
pmTotalTimeDlCellCong
The total amount of time (sec) was congested in UL during a reporting period for a cell:
pmTotalTimeUlCellCong

. A Figure108
Control
Average DL TX power for a cell-carrier:

102
  i 

i 0


pmTransmit tedCarrierPower 
i  
 2 
102
 pmTransmittedCarrierPower
i 0
i
Average UL RSSI for a cell-carrier: GSM Signal Strength:

Received Signal
62
Strength Indication
  pmAverageRssi
i 0
i   0.5  i  110.5  
(RSSI)
Samples of the UL RSSI for a

62 cell-carrier could be found in
 pmAverageRssi
i 0
i the counter pmAverageRssi

. A Figure109
TEMS Investigation with high
UTRA Carrier RSSI
UE send RRC
Connection
Request,
UTRAN send
RRC Connection
Reject with
cause =
congestion.
TEMS
Investigation
with high
UTRA Carrier
RSSI

. A Figure110
TEMS Investigation with high
UTRA Carrier RSSI
The UL RSSI can be high due to the following:
• non-traffic (external) interference
• High TX power from a UE that is connected to a far cell

(soft handover).
This can happen due to missing neighbors.

. A Figure111
Admission Policy
The WCDMA admission policies and how they are used for
the various channel types are given in next slides

. A Figure112
Admission
RequestPolicy
T
Admission Attributes c
f
c
Channel type Channel type Channel type Channel type p
Admission Policy S
DCH/DCH DCH/HSDPA EUL/HSDPA MBMS
f
DL Ch Code Adm Yes Yes (DL code for Yes (DL code for Yes
Policy SRB part on DCH) SRB part on DCH)
DL Power Adm Policy Yes Yes Yes Yes
DL ASE Adm Policy Yes Yes, (GBR-part on Yes, (GBR-part on Yes
HSDPA and SRB- HSDPA and SRB-
part on DCH) part on DCH)
UL ASE Adm Policy Yes Yes Yes No
DL SF Adm Policy Yes, ( SF 8, 16, 32) No No No
UL SF Adm Policy Yes, ( SF 8, 16, 32) Yes, ( SF 8, 16, 32) No No
CPM Adm Policy Yes No No No
Serving HS Adm No Yes Yes No
Policy
Serving EUL Adm No No Yes No
Policy
Non-serving EUL Adm No No Yes No
Policy
DL RBS HW Adm Yes Yes Yes Yes
Policy
UL RBS HW Adm Yes Yes Yes No
Policy
. A Figure113
Admission Policy
When a request is Conditionally Blocked the behavior of Radio
Network (RN) Soft Congestion control differs depending on the Top
e title
RN class
40 pt request SoftasCongestion
illustrated corn
field
cus
btitle part
24 pt See
for e
Text
24 pt
l 2-5
20 pt
© Ericsson
© Ericsson AB AB 2007 LZU
2008 03_03813 LZU108
1086911
6924R1A
Uen Rev
. A Figure
Figure 3 -3-15
114 P6 Radio Network
Service Features
Accessibility
Admission Policy
Non-guaranteed requests:
Can reduce the rate of other lower priority, non-guaranteed

connection parts in steps (for example from interactive PS
384/64 to interactive PS 128/64), down to their lowest
retainable rate.
Equal priority request and connection parts will equally balance

their resource utilization (for example a request for interactive
PS 64/64 can reduce the rate of an equal priority interactive PS
128/64 to interactive PS 64/64, but not to lower rates).

. A Figure115
Admission Policy
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 pre-empt

existing guaranteed RABs of lower priority, or non-guaranteed
RABs at the lowest retainable rate if the request is pre-emption
capable and connection part targeted is pre-emption
vulnerable.
For example conv. CS Speech (priority=3, pre-emption

capable) can pre-empt conv. CS unknown (priority=4, pre-
emption vulnerable).

. A Figure116
The Uplink RBS HW
Admission Policy

. A Figure117
The Uplink RBS HW Admission Policy
RBS Hardware Monitor provides Admission Control with the
estimation of the hardware usage in a local cell group,
separately for the uplink and the downlink.
The relation among:
• the RBS hardware admission policy parameters,
• the downlink resource usage in the relevant local cell

group and
• the admission request parameters
are almost the same as the uplink resource check:

. A Figure118
RBS HW Admission Policy
The parameters,
ulHwAdm, dlHwAdm,
beMarginUlHw and
beMargindlHw, are
related to the RBS HW
check and are used by
Admission Control to
decide which admission
requests to admit or
reject
The HW is checked towards the

licence key

. A Figure119
beMarginUlHw / beMargindlHw : Parameter that defines the
admission limit for the uplink/downlink hardware usage in the
cell group in order to reserve some resources for guaranteed
and guaranteed-hs service class connections.
Applicable to following admission requests:
(non-guaranteed, non-handover),
(guaranteed-hs, non-handover) and
(guaranteed, non-handover).

. A Figure120
ulHwAdm / dlWwAdm : Parameter that defines the admission
limit for the uplink / downlink hardware usage in the cell group.
(non-guaranteed, non-handover),
(guaranteed-hs, non-handover) and
(guaranteed, non-handover).

. A Figure121
Non-guaranteed, non-handover
admission requests can be granted when:
• resource usage ulHwAdm - beMarginUlHw level
• possible to free uplink resources by downswitching a non-

guaranteed user with a lower UL spreading factor than the UL
spreading factor being requested in the admission request
(soft congestion control).

. A Figure122
(Guaranteed, non-handover) & (guaranteed-hs, handover)
• resource usage ulHwAdm - beMarginUlHw level
• soft-congestion can free up resources
• physical resources are available

. A Figure123
(Guaranteed, handover) & (Non-guaranteed, handover)
uplink hardware usage 100% utilization
Soft-congestion action could be triggered in these cases.

. A Figure124
The Downlink RBS HW Admission
Policy
Blocked
RN Soft Congestion
action triggered
100%
+ Resource
Licensed HW The parameters,
limit ulHwAdm and
Conditionally Blocked dlHwAdm, are
related to the
RBS HW check
dlHwAdm
and are used by
Admission
0-100 Control to decide
Default= 100
Resources freed by RN which admission
Soft Congestion requests to
admit or reject
Time

. A Figure125
RBS HW Management
Some counters are very useful to help the operators
control the Channel Element usage.
 pmUlCredits
 pmDlCredits
 Explanation: next slide
pmSumUlCredits
 pmSumDlCredits
 pmSamplesDlCredits
 pmSamplesUlCredits
The License has a limit of Credits.

One Credit = One Channel Element.

. A Figure126
RBS HW Management
pmSumDlCredits : Aggregate of total consumed RBS DL credit
measurements (in credits).
pmSamplesDlCredits : Number of samples in pmSumDlCredits (that is,

pmSamplesDlCredits = pmSamplesDlCredits +1, whenever pmSumDlCredits is to
be updated). Reset at each ROP period.
pmSumSqrDlCredits : Aggregate of the squares of the individual

measurements in pmSumDlCredits (that is, pmSumSqrDlCredits =
pmSumSqrDlCredits + measurement_value^2).

. A Figure127
RBS HW Management

. A Figure128
control on RBS
Counter Description
pmNoFailedRabEstAttemptLackUlHwBest Number of failed RAB establishment attempts due to

lack of UL hardware resources, for the best cell in the
active set
pmNoFailedRabEstAttemptLackUlHw Number of failed RAB establishment attempts due to

lack of UL hardware resources.
pmNoFailedRabEstAttemptLackDlHwBest Number of failed RAB establishment attempts due to

lack of DL hardware resources, for the best cell in the
active set
pmNoFailedRabEstAttemptLackDlHw Number of failed RAB establishment attempts due to

lack of DL hardware resources.

. A Figure129
control on RBS
The parameters, hsdpaUsersAdm , beMarginUlHw and beMargindlHw,
are related to the RBS HW check and are used by Admission Control to
decide which admission requests to admit or reject
The Problem:
Problem
HS-DSCH (shared transport channel) can support very large

amount of users simultaneously.
the throughput per user can become very low.
end-to-end quality is degraded.

. A Figure130
control on RBS
The Solution:
Solution It is beneficial to limit the number of users
that can be allocated to the HS-DSCH in a cell.
Admission Control blocks new radio link admission requests

which involve the allocation to HS-PDSCH/HS-SCCH when
the number of users assigned

to the HS-DSCH in the cell hsdpaUsersAdm
Counter pmNoOfNonHoReqDeniedHs will be stepped. (not

stepped in the DRNC).
. A Figure131
control on RBS
The Admission Algorithm:

Algorithm
• If UL 384 is active, an HSDPA RAB establishment is

attempted first on the 384/HS RAB.
• If for some reason (admission, failed path loss check) the

packet call cannot be setup on the 384/HS RAB, an attempt
is made on the 64/HS RAB provided that:
hsdpaUsersAdm value is not exceeded

. A Figure132
control on RBS
pmNoServingCellReqDeniedEul is stepped at admission reject when

requesting the cell as serving cell due to the number of Enhanced
Uplink resources (E-DCH) users is above the admission threshold
pmNoNonServingCellReqDeniedEul is stepped at admission reject

when requesting the cell as non-serving cell due to the number of E-
DCH users is above the admission threshold.

. A Figure133
HSDPA – Admission Control Policy
HS-DSCH
Blocked Cell
Admitted Change
maxNumHsdpaUsers
Blocked 0-64
Default= 16
Admitted
hsdpaUsersAdm
pmNoOfNonHoReqDeniedHs 0-1000
Admission Control blocks new radio link admission Default= 10
requests which involve the allocation to HS-
PDSCH/HS-SCCH when the number of users assigned
to the HS-DSCH in the cell exceeds hsdpaUsersAdm Time

. A Figure134
HSUPA – Admission Control Policy
pmNoServingCellReqDeniedEul
is stepped at admission
Blocked Blocked
reject when requesting the
0-100
Default= 100
cell as serving cell due to
the number of E-DCH
eulNonServingCellUsersAdm users is above the
+ Resource admission threshold.
Number of Users
pmNoNonServingCellReq
DeniedEul
0-100 is stepped at admission
Default= 4 reject when requesting
the cell as non-serving
eulServingCellUsersAdm cell due to the number of
+ Resource E-DCH users is above
the admission threshold.
Serving Non-serving

. A Figure135
The Downlink Transmitted Carrier
Power Admission Policy

. A Figure136
pwrAdm,
pwrAdm
beMarginDlPwr
pwrAdmOffset
are related to downlink transmitted carrier power and are

used by Admission Control to decide which admission
requests to admit or reject.
Next slide presents the relation between these parameters

and the downlink transmitted carrier power.

. A Figure137
Three parameters,
pwrAdm,
beMarginDlPwr and
pwrAdmOffset, are
related to downlink
transmitted carrier power
and are used by
Admission Control to
decide which admission
requests to admit or
reject

The operator can limit the total
pmTransmittedCarrierPower
maximum power that is allowed
 pmTransmittedCarrierPowernonHS
to be transmitted by an RBS in a
 pmNoOfSwDownNgAdm
cell by setting
maximumTransmissionPower
. A Figure138
pwrAdm : Cell parameter that defines the absolute admission
limit for downlink power utilization.
(guaranteed, non-handover)
(non-guaranteed, handover)
It is relative to the min(maximumTransmissionPower,

maxDlPowerCapability), it is expressed as a percentage and
that is a precentage of min(maximumTransmissionPower,
maxDlPowerCapability).

. A Figure139
beMarginDlPwr: Cell parameter that defines an admission
margin on pwrAdm in order to reserve some of the resource
for guaranteed and guaranteed-hs service class connections.
Applicable only to (non-guaranteed, non-handover) admission

requests.
It is relative to the min(maximumTransmissionPower,

maxDlPowerCapability), it is expressed as a percentage and
that is a precentage of min(maximumTransmissionPower,
maxDlPowerCapability).

. A Figure140
pwrAdmoffset: Cell parameter that defines an admission
margin on pwrAdm in order to reserve some of the resource
for mobility of guaranteed service class connections and
guaranteed-hs service class connections.
pwrOffset: Cell parameter that defines the margin on

pwrAdmOffset to be used as detection level for downlink cell
congestion.

. A Figure141
Relation between R99 connections and High Speed
The operator can limit the total maximum power utilized by

R99 connections that is allowed to be transmitted by an RBS
in a cell by setting maximumTransmissionPower.
Remaining power can then be used for transmission of HS-

PDSCH/HS-SCCH channels to HSDPA users
Total power = Total R99 RBS power + HSDPA power

. A Figure142
Total Available Power in the Cell
When:
maximumTransmissionPower maxDlPowerCapability,
maxDlPowerCapability is automatically taken as limit of the

total maximum power allowed in the cell.

. A Figure143
Total Available Power in the Cell
pwrAdm => can configure the portion of downlink power

reserved for HSDPA connections.
Default settings balance a mix of R99 and available power for

HSDPA, => minimum of 25% power to HSDPA,
Exceptions: cases that R99 takes part of that power due to

mobility and power variations of users in the cell.

. A Figure144
The Downlink Transmitted Carrier Power
Admission Policy - Congestion
Congestion due to radio overload in downlink transmitted carrier
power is detected when:
measured downlink transmitted pwrAdm + pwrAdmOffset + pwrOffset

carrier power
Congestion resolution:
measured downlink transmitted pwrAdm + pwrAdmOffset + pwrOffset

carrier power
for a longer time than the hysteresis time pwrHyst.

. A Figure145
Admission Policy

. A Figure146
The Downlink Transmitted Carrier Power Admission Policy
Special Case:
Case A cell with predominant R99 traffic,
Requirements: It is possible to increase the power admission

threshold in order to maximize capacity.
Solution: Make use of the complete capability before the

congestion resolve mechanism is activated (fast congestion
control mechanism in the RBS).
pwrAdm + pwrAdmOffset + pwrOffset = 99%
(congestion resolve actions can still be triggered for1%)
Hints: pwrAdm can be set to 84% maintaining pwrAdmOffset at 10%

and pwrOffset at 5%.

. A Figure147
Admission Policy – Service class
Non-guaranteed, non-handover:
The following request is granted when:
• admission request pwrAdm - beMarginDlPwr level
• soft-congestion will free up resources,
• cell not DL congested.

. A Figure148
Non-guaranteed, handover:
The following requests are granted when:
• admission request pwrAdm level

. A Figure149
Guaranteed, non-handover:
The following requests are granted when:
• admission request pwrAdm level

. A Figure150
Admission Policy – Counters
pmNoFailedRabEstAttemptLackDlPwr: is increased whenever
a RAB establishment failed due to lack of downlink power.
pmTransmittedCarrierPower: Samples of the DL TX power for

a cell-carrier. This counter is an RBS PDF counter, this
includes the power used for HSDPA as well.
pmTransmittedCarrierPowerNonHs non-HS users transmitted

carrier power.
pmNoOfSwDownNgAdm: How many down-switches due to

best effort clean up (triggered by DL TX power and code usage
admission policies).
. A Figure151
Blocked pmTransmittedCarrierPower
pmTransmittedCarrierPowernonHS
All requests Blocked
pmNoOfSwDownNgAdm
blocked if cell
Downlink Tx Carrier Power [%]
pmNoFailedRabEstAttemptLackDlPwr
is overloaded Conditionally
Blocked Max
+ Resource (100%)
The operator can
limit the total
pwrAdm maximum power
0-100% that is allowed to
Resources
freed by RN Default= 75% be transmitted by
Soft an RBS in a cell
Congestion by setting
Non-HS Tx Carrier maximumTransm
Power issionPower
Time

. A Figure152
Air Interface Speech Equivalents (ASE)
The Uplink ASE Admission Policy

. A Figure153
ASE Algorithm
The ASE Monitor algorithm monitors ASE usage at cell carrier

level in both uplink and downlink.
This monitor accounts for the air interface resources usage in

a cell (separately for the uplink and downlink), by means of an
average static load estimation of the contribution of each radio
link in the cell.
ASE of a single radio link depends on the radio connection

type  expressed in terms of the equivalent number of
speech radio bearers that generate the same amount of
air interface load.

. A Figure154
ASE Algorithm, con’t
Example:
A downlink radio link with ASE = 3 is expected to generate as

much interference in downlink as three speech radio bearers
in the cell.

. A Figure155
The UL/DL ASE
ASE Estimation
Attention: The number of uplink radio link per cell ASE is divided by the
number of radio links within the RNC.
Reason: Average uplink interference (created by a UE in the respective cell)
is proportional to the number of cells to which it is connected. I.e. A
UE is connected to two cells it only requires approximately half the
Ec/No compared to using one cell.
. A Figure156
ASE Estimation
Example: Suppose the following conditions
1. The uplink ASE for a radio connection is four,

2. SRNC has one radio link and
3. DRNC has two radio links,
Solution: ASE value for the radio link in SRNC = 4 and in

DRNC = 2.
Consequence: Therefore, the ASE values for connections

with radio links over the Iur are overestimated
when compared to all radio links being in the
same RNC.
. A Figure157
ASE Estimation
General formula to estimate ASE:
ASE for a radio link is the sum of the ASE of all DCHs associated to a certain radio
connection type.
Example: AMR 12.2 radio connection type consists of both the speech radio bearer
(ASE = 1) and the signaling radio bearer (ASE = 0.61)
ASEAMR = 1 + 0.61

. A Figure158
ASE uplink admission policy:
• (Non-guaranteed, non-handover) admission requests are

blocked if
ASE uplink usage aseUlAdm - beMarginAseUl.
• (Non-guaranteed, handover) & (guaranteed, non-

handover) & (guaranteed-hs, non-handover) admission
requests are blocked when
ASE uplink usage aseUlAdm
• (Guaranteed, handover) & (guranteed-hs, handover)

admission requests are blocked when
ASE uplink usage aseUlAdm + aseUlAdmOffset.
. A Figure159
In uplink, ASE is a resource that

is controlled to allow admission
and modifications. Therefore,
the parameters, aseUlAdm and
aseDlAdm are controlling the
overload

. A Figure160
Counter Description
pmSumOfSampAseUl Total ASE UL, that is sum of all sample values recorded
pmSumOfSampAseDl Total ASE DL, that is sum of all sample values recorded
pmNoOfSampAseUl Number of samples of ASE UL increased at every
occasion when the corresponding Sum counter is
increased, sampled every 30 seconds
pmNoOfSampAseDl Number of samples of ASE DL increased at every
occasion when the corresponding Sum counter is
increased, sampled every 30s
pmNoFailedRabEstAttemptLackUlAse Number of failed RAB establishment attempts due to
lack of UL ASE
pmNoFailedRabEstAttemptLackDlAse Number of failed RAB establishment attempts due to
lack of DL ASE
The formulas for checking the average usage of ASE in the

downlink and uplink for a cell can be found below.
pmSumOfSampAseDl pmSumOfSampAseUl
Average UL ASE for a cell: Average DL ASE for a cell:
pmNoOfSampAseDl pmNoOfSampAseUl
. A Figure161
Always In uplink, ASE is a

Admitted resource that is
controlled to allow
admission and
Number of ASEs used in UL
modifications.
Conditionally Therefore, the
Blocked parameters,
aseUlAdm and
aseDlAdm are
controlling the
aseUlAdm overload in up and
down link.
0-500
Resources freed
Default= 160
by RN Soft
Congestion
Time
. A Figure162
Spreading Factor
Admission Policy

. A Figure163
The Spreading Factor Admission
Admission
Control controls
the spreading
Blocked Blocked Blocked Blocked
factor usage in
0-32 the downlink
Default= 32 and up link at
0-16 0-16 cell level. The
Default= 16 sf32Adm Default= 16 following
0-8 parameters can
Default= 8 + Resource
sf16Adm sf16gAdm be adjusted to
+ Resource control the up
+ Resource
sf8Adm link: sf4AdmUl;
+ Resource
sf8AdmUl;
sf16AdmUl;
sf8gAdmUl
8 16 32 16
Spreading Factor pmNoFailedRabEstAttemptExceedConnLimit

. A Figure164
Compressed Mode Admission Policy
Blocked
Compressed Mode pmCmStop
pmCmAttUlSf2,
Requests pmCmSuccUlSf2
GSM pmCmAttDlSf2,
pmCmSuccDlSf2
WCDMA
Number of CPM Radio Links
pmCmAttUlHls,
pmCmSuccUlHls
pmCmAttDlHls
pmCmSuccDlHls
compModeAdm
+ Resource
0-128
Default= 15
WCDMA f1
WCDMA f2 pmSumCompMode
pmSamplesCompMode

. A Figure165
The Downlink Channelization Code
Admission Policy
Code blocking for non-hand over requests exists to reserve
codes for users in hand over
Requests for hand over are not blocked by the downlink

channelization code admission policy.
Default admission limit:
• parameter dlCodeAdm set to 80% (reserving 20% of the

code tree for new handover legs).
• parameter dlCodeAdm set to 75% when HSDPA is not

enabled in the cell.
. A Figure166
Admission Policy
• In a network with both HSDPA and R99 traffic, this value
needs to be increased even further in order to avoid
unnecessary code blocking.
Hint: dlCodeAdm set to 85% and beMarginDlCode set to

5% will maximize the code tree usage and still allow a margin
for new soft handover legs.

. A Figure167
Admission Policy
The operator has the
possibility to configure
and change the number
of HS-PDSCH codes
allocated in a cell for
HSDPA by tuning
numHsPdschCodes.
The counter shows the number of RRC connection

requests and RAB establishment denied by admission
control due to lack of power, code utilization limit, ASE
limit and compressed mode limit.
. A Figure168
Admission Policy
Blocked
RN Soft Congestion
action triggered The operator has the
Max (100%) possibility to configure
and change the
CH Code Tree usage [%]
Conditionally
Blocked + Resource number of HS-PDSCH
codes allocated in a
cell for HSDPA by
tuning
dlCodeAdm numHsPdschCodes.
Admitted
Resources freed by 0-100%
RN Soft Default= 80%
Congestion
+ Resource
pmNoFailedRabEstAttemptLackDlChnlCode
Time
. A Figure169
control - counters
Code allocation failure could be found in the following counter:
pmNoFailedRabEstAttemptLackDlChnlCode
Average number of user in compressed mode for a cell :
pmSumCompMode
pmSamplesCompMode

. A Figure170
Lack of Transmission Resources
AAL2 establishment failure can be observed by:
 Non-zero radio link setup failure rate in RRC establishment with

no admission control blocking, no code allocation failure, no HW
failure
 High number of interactive RAB failure (= low interactive RAB

establishment successful rate) but not much admission control
blocking.
 High number of samples at the counter pmNoFailedAfterAdm

. A Figure171
Lack of Transmission Resources
(cont)
The counter pmNoOfDiscardedNbapMessages will
increase if the number of Node B Application Part
(NBAP): Radio Link Setup Messages reject by Admission
Control due to User Network Interface Signaling ATM
Adaptation Layer (UNI-SAAL) congestion.
Iu Signalling success rate:

pmNoIuSigEstablishSuccess  CS or PS 
pmNoIuSigEstablisAttempt  CS or PS 

. A Figure172
Uplink Cell Congestion Due to Uplink
RTWP
0 to 621
Congestion
[-112.0 to -49.9 dBm]
Detected Default= 621 [-49.9 dBm]
ifCong
ifHyst ifHyst
Congestion
Resolved
0 to 6000
[0 to 60000 ms]
Default= 6000 [60000 msec]
(1 minute)
Time

. A Figure173
DL Cell Congestion Detection
Max (100%)
Congestion Detected
0 to 100%
Non-HS Tx Carrier Power Default= 5%
pwrOffset
pwrHyst pwrHyst
Congestion
Resolved
0 to 6000
[0 to 60000 ms] pwrAdm
Default=
Default=6000
300 [60000
[3000 msec]
msec]
(3 seconds) 0-100%
Default= 75%
Time
. A Figure174
HSDPA Cell Congestion Detection
Congestion
Detected
Max (100%)
maxPowerOverloadHystTime Congestion
Resolved
0 to 50 seconds
Default= 10 seconds
Non-HS Tx Carrier Power
HS-DSCH Required Power Value
Time
. A 3 --
Figure175 Service Accessibility
Congestion Control Detection
Counters
The following methods are used to detect cell congestion:
 Uplink Cell Congestion Detection,

 Downlink Cell Congestion Detection
 HSDPA Cell Congestion Detection
Number of times congestion control is triggered due to high DL power for a cell:
pmSumOfTimesMeasOlDl
Number of times congestion control is triggered due to high UL interference for a cell:
pmSumOfTimesMeasOlUl
pmHsdschOverloadDetection & pmTotalTimeHsdschOverload

- RNC counters monitoring HSDPA
The total amount of time (s) was congested in DL during a reporting period for a cell:
pmTotalTimeDlCellCong
The total amount of time (s) was congested in UL during a reporting period for a cell:
pmTotalTimeUlCellCong

. A Figure176
RRC Connection – Load Sharing

. A Figure177
Load sharing enhances the performance of a Radio Access

Network by pooling together resources from different parts of
the entire network.
Currently, two load-sharing features are available in the

WCDMA RAN:
• Inter-Frequency Load Sharing
• Directed Retry to GSM

. A Figure178
Inter-Frequency Load Sharing activated in RNC by:
parameter loadSharingRrcEnabled = TRUE
Load-sharing neighbors must be defined before any load-

sharing action can take place.
Directed Retry to GSM is activated in an RNC by:
parameter loadSharingDirRetryEnabled to TRUE

. A Figure179
Ratio between RRC connection returning and redirection due to load

sharing for a cell:
pmNoOfReturningRrcConn
pmNoLoadSharing RrcConn

. A Figure180
Cell load is measured as the ratio between the downlink
transmitted carrier power and the admission limit (parameter
pwrAdm).
For HSDPA cells, only the non-HSDPA part are counted (i.e.,
the cell load for load-sharing purpose does not include the
power used for HS-PDSCH and HS-SCCH).
The downlink transmitted carrier power for the non-HSDPA

part is measured by the RBS and periodically reported to the
RNC.

. A Figure181
The load sharing counter flow
Load Sharing
Redirection Info IE tells the mobile to try to
access the network via a specified frequency
RNC sends RRC Connection Reject
message including the Redirection Info IE
(Cell) pmNoLoadSharingRrcConn +
(Cell) pmTotNoUtranRejRrcConnReq +
The UE reselects a cell in the specified

frequency and tries to access the network
The UE succeeds to Does the UE return RRC Conn. Setup Failure

setup RRC conn. in back to the original UE goes back to Idle state
the new freq? No frequency? No
Yes Yes
(Cell) pmTotNoRrcConnectReqSuccess + (Cell) pmNoOfReturningRrcConn +
(Cell) pmTotNoRrcConnectReqCsSuc +
Random Access
Load Sharing is not allowed in
this 2nd access attempt

. A Figure182
(cont)
Ratio between RRC connection returning and redirection due
to load sharing for a cell:
pmNoOfReturningRrcConn
pmNoLoadSharing RrcConn

. A Figure183
(cont)
Reasons for high RRC Connection direction:
 Too large difference of the pilot power setting between two
carriers – primaryCpichPower
 Too large difference of the RF patterns between two carriers
 Improper inter-frequency cell re-selection parameter setting -
interFreqFddMeasIndicator, qHyst2, qOffset2sn and sInterSeach
 Improper capacity management parameter setting -
maximumTransmissionPower and pwrAdm
 Incorrect definition of a target cell candidate -
loadSharingCandidate

. A Figure184
Directed Retry to GSM – Load
Sharing (cont)
Reasons for high directed retry failure:
 If the GSM cell is congested (add another TRU)
 The loadSharingGsmThreshold can be increased or
loadSharingGsmFraction can be reduced
 Incorrect definition of a target cell candidate -
loadSharingCandidate
 Coverage difference between the different technologies
pmNoDirRetryAtt gives the total

pmNoDirRetrySuccess number of Directed Retry attempts
100% pmNoDirRetrySuccess gives the
pmNoDirectedRetryAtt number of successful attempts.

. A Figure185
Radio Link Setup Procedures

. A Figure186
UE RBS RNC
Power control,
Radio link setup
admission control, etc.
Radio Link Setup Request
Resource allocation
Radio Link Setup Response

AAL2 connection
setup
Start Rx and radio connection
supervision

. A Figure187
Radio Link Setup Procedures (cont I)
UE RBS RNC
Radio link synchronization Transport channel

synch.
Start Tx
L1 synch.
Radio Link Restore Indication
Radio link synchronization procedure happens both during

RRC connection establishment but also during RAB
establishment.

. A Figure188

. A Figure189
Radio Link Setup Procedures (cont I)
RNC orders the RBS to reserve the necessary resources for a new RBS
communication context in the RBS.
RBS reserves the necessary resources for a new communication context in

the RBS.
RBS calculates link characteristic parameters from the received uplink and
downlink Transport Format Combination Set (TFCS) and Transport
Format Set (TFS) information.
RBS responds to the RNC that the necessary resources are allocated for the
radio link (binding identifier and transport layer address for AAL2
connection)
The transport bearer (AAL2 connection) needed for signaling is set up over
Iub by the RNC.
The Radio Link Set Supervision algorithm in the RBS starts evaluating the
synchronization status of the RLS and also the RCS algorithm in the RNC
is started.
. A Figure190
Radio Link Setup counter flow
AAL2 Setup
AAL2
(Cell) pmNoFailedAfterAdm + failure
OK
RNC sends the message
(Cell) pmTotNoUtranRejRrcConnReq + RRC Connection Setup
RNC sends the message

RRC Connection Reject No “RRC Connection
Setup Complete”
received
Yes Redirection of
Call Yes
Redirected to Emergency
Calls?
GSM No Restore Indication
No received from RBS
(Cell)pmNoCellDchDisconnectAbnorm +
Yes
RRC Conn. Setup Failure.
UE goes back to idle state (Cell)pmNoFailedAfterAdm +
(Cell) pmTotNoRrcConnectReqSuccess +
(Cell) pmTotNoRrcConnectReqCsSuc +

. A Figure191
Loss of RBS contact
1. RNC sends “radio link setup request” to RBS
2. RNC does not receive any response from RBS and the
timer expires.
3. Classification of “loss of RBS contact” initiated.

. A Figure192
Radio Link Setup – L1
synchronization
The L1 synchronization has to be achieved in both DL and
UL. To achieve this, correct power settings are needed for
DlinitSirTarget and UlInitSirTarget.
primaryCpichPower : downlink output power used for the

PCPICH in the cell where the connection is set
upEc/No_PCPICH: measured Ec/No on PCPICH in the cell

where the connection is set up, received from the UE.
dlInitSirTarget: required initial SIR target for the downlink

DPDCH.

. A Figure193
synchronization
…To remember
The transport channel E-DCH is mapped to the E-DCH

Dedicated Physical Data Channel (E-DPDCH) and the E-
DCH Dedicated Physical Control Channel (E-DPCCH) in
the uplink.
E-DPDCH carries user data and uses a variable spreading

factor

. A Figure194
synchronization
The synchronization is first achieved in the DL.
The UE will then wait SRBdelay number of frames (1 to 7)

before it sends the RRC Connection Setup Complete
message.
It is very difficult to trouble-shoot the radio link synchronization failure .
There are several counters that has to be taken into account when
analyzing the L1 synchronization problems.

. A Figure195
synchronization (cont)

. A Figure196
Radio Link Setup – L1 synchronization troubleshooting
There are several methods to handle these L1 synchronization
failure caused due to coverage issues on Signaling Radio
Bearers (SRB) and/or DCH on drive test:
• check the parameter settings of dlattenuation and

ulattenuation
• Check the antenna configuration.
• find out if the system is balanced regarding UL and DL cell

coverage.
. A Figure197
Parameters cPO and cBackOff can also be increased in order to
obtain larger initial DL DPDCH and UL DPCCH powers.
cBackOff: back off the Open Loop Power Control estimate to a

conservative starting point or to increase the initial downlink
power to improve the call setup reliability. This parameter will
allow some flexibility in the Open Loop Power Control upon
establishment of downlink dedicated channel.
cPO: set the uplink DPCCH power offset to a conservative level

to avoid excessive UL interference, i.e
DPCCH_POWER_OFFSET = primaryCpichPower + RTWP + ulInitSirTarget - 10 log (SF_DPCCH) + cPO

. A Figure198
Unbalance
1. The DL SRB / DCH maximum power:
minPwrMax (only for DL coverage issue)
Should be increased
2. CPICH power can be reduced in order to get a system that

is more balanced.
Check next slide

. A Figure199
minPwrMax: Cell parameter that defines the minimum
relative power for maximum downlink power mapping for
resource estimation

. A Figure200
Radio Link Synchronization failure

. A Figure201
Radio Link Setup
S-CCPCH (FACH1) power

. A Figure202
Radio Link Setup - S-CCPCH (FACH1) power
UE is in Idle mode or in state URA_PCH
Two different physical channels are used in order to exchange

proper information between the WCDMA RAN and the UE:
PICH and S-CCPCH (carries the PCH).
There is a fixed timing relation between a PICH frame and the

associated S-CCPCH frame.

. A Figure203
Radio Link Setup - S-CCPCH
(FACH1) power
UE is in Idle mode or in state URA_PCH
PICH is used to indicate to the UE when it should read the

S-CCPCH.
PCH is used to carry the RRC message "Paging type 1",

(containing the actual paging information.
The number of times the WCDMA RAN will transmit the

paging information to a UE is determined by the configurable
parameter noOfPagingRecordTransm.

. A Figure204
Radio Link Setup - S-CCPCH
(FACH1) power
Due to lack of S-CCPCH power, the UE cannot receive
the RRC connection setup message.
The following formula should only be used if drive tests have been
performed in order to verify the S-CCPCH power.
Number of AICH_ACK - Number of RRC connection setup - Number of cell (re)selection during RRC establishment
 100%
Number of AICH_ACK
One solution to the problem is to increase maxFach1Power.

. A Figure205
Radio Link setup failure:
AICH problem in TEMS Investigation
The UE sends out several RRC

Connection request but it does not
receive the RRC Connection setup
from the UTRAN. The RF conditions
could be fairly. The UE does not get
the AICH. It can be seen in the
Random access reports, in the mode
reports window.
One solution to the problem is to
increase maxFach1Power

. A Figure206
Non Access Stratum (NAS)
Procedures

. A Figure207
Non Access Stratum (NAS)
Procedures
Mobile Originating Call Setup
Random Access
RRC Connection Setup
NAS procedures:
Service Request
Authentication Security
RAB Assignment

. A Figure208
NAS failure: CM service reject in
TEMS Investigation
CM Service reject
with cause:
Network failure

. A Figure209
Speech, CS 64, Streaming 57.6
RAB establishment
 A ‘RAB
ASSIGNMENT DPDCH/DPCCH
REQUEST’ is UE State
SRB Signaling Connection
received from the Cell_DCH DPDCH/DPCCH
CN The SRNC Non Access Stratum call setup
determines the new RAB assignment

request 1
RC configuration Setup new Radio Bearer id= Speech,CS64
or streaming 57.6
DPDCH/DPCCH
and also check the UE State 3 New Signaling Connection
SPEECH
UE capabilities. Cell_DCH
User plane Radio Bearer Setup Iu bearer
(AAL2) 2
DPDCH/DPCCH
 The SRNC initiates

the setup of an
AAL2 connection  The UE is ordered to setup a new Radio
for the Iu bearer. Bearer (RB) and activate the new
configuration. When finished the UE
acknowledges the successful RB setup
and the UE will be in CELL_DCH state.

. A Figure210
Interactive RAB Establishment
 A ‘RAB
ASSIGNMENT UE State
DPDCH/DPCCH
Signaling Connection
REQUEST’ is SRB
Cell_DCH DPDCH/DPCCH
received from the Non Access Stratum call setup
CN The SRNC RAB assignment
determines the new Setup new Radio Bearer
request
id= Interactive
1
RC configuration UE State
FACH/DCH
3 New Signaling Connection
and also check the Cell_FACH
User plane Radio Bearer Existing AAL5 Iu
or
UE capabilities. Cell_DCH RACH/DCH
bearer is used
2
Data Buffers
 The existing AAL5

signalling Iu bearer
 The UE is ordered by the SRNC to set up
is used to carry the a new RB. In the case of cell_FACH the
user plane traffic UE will also perform a Cell Update after
the RB is set up

. A Figure211
Default ARP Mapping
The RNC creates an internal Allocation/Retention Priority
(ARP) from the RANAP ‘RAB Assignment Request’ message
attributes received from the Core Network.
The RNC will choose a internal ARP base on the combination

of
• ‘Traffic Class’,
• ‘CN indicator (CN-ind)’ and
• ‘Source Statistics Descriptor (SSD)’
from RANAP ‘RAB Assignment Request’ message

. A Figure212
Default ARP Mapping
Top right
Slide title
40 pt RAN Synchronization corner for
field-mark,
customer or
Slide subtitle Internal ARP RANAP Attributes partner logotypes.
24 pt See Best practice
CN Allocation/Retention
Priority
Pre-empt
Capability
Pre-empt
Vulnerability
Traffic class CN-ind SSD Emergency for example.
Text 1 Yes No Conv. CS Speech Yes

24 pt
3 No Yes Conv. CS Speech N
Bullets level 2-5
20 pt 4 No Yes Conv. CS Unkn N
5 No Yes Stream. CS Unkn N
6 No Yes Stream. PS Unkn N
7 No Yes Interactive PS - N
7 No Yes Background PS - N
3 No Yes MBMS PS Unkn N
‘RAB Assignment
Request’ message
0 to 15 ecCnPriorityLevel
RNC Default= 7 CN

. A Figure213
PDP Context Activation Failure

. A Figure214
PDP Context Activation Failure

. A Figure215
UE Cell reselection during handover

. A Figure216
Radio Bearer Setup (cont)

. A Figure217
Performance Evaluation
The basic performance indicator to be used during Capacity

Investigation can be divided into 6 groups:
(1) KPIs related to request blocking

(2) KPIs that indicates a limitation on “radio resource”
(3) KPIs that indicates “congestion” or “soft-congestion” action
(4) KPIs that indicates a limitation on “non-radio resource” (e.g. transport
network)
(5) KPIs for “radio resource” behavior characterization
(6) KPIs used to group cells into specific cell profile based on certain cell
attributes

. A Figure218
BARN (BRIEF AUDIT OF RADIO
NETWORK) - Finding a worst cell
 Busy hour data
 Several RNCs involved
 Simple KPIs to identify critical cells
– RRC “guaranteed” blocked > 1%
Worst Cell cell42721
– RAB “guaranteed” blocked > 1% 5
4,5
– RAB “non-guaranteed” blocked > RRC_Setup_Fail_Adm
RRC_Fail_Adm
4
3,5 Req_Denied_Adm_PS
5% 3
2,5
– Terminated “guaranteed” >0 2
– Switch to common “non- 1,5
1
guaranteed” > 10 0,5
0
15-gen 16-gen 17-gen 18-gen 19-gen
Date
If many transport network issues (e.g. AAL2 failure due to transport

network blocking on the Iub link) recommend a “WDMA Transport Network
Review and Re-engineering” service

. A Figure219
Cell Profiles Characterization
 Cell attributes related to the
Cell 42721 Cell 6322
users’ behavior
– used when deciding the
HO_Rate [HO/UE/min] 0.5 2.11
test cases for capacity
– cells with matching RRC_Int [RRC att/min] 27.2 12
profiles are likely to Perc_G [%] 74 89
share a similar resource
Perc_GHS [%] 0 0
control policy
Perc_NG [%] 26 11
ChSw_Act [uspsw/ng 0.48 1.28
 Cell attributes related to users/min]
cell/RBS configuration
Cell_Carrier “first carrier” “first carrier”
– Upgrade resource (e.g.
hardware CE) Cell_HSDPA_Enabled “no” “no”
– Additional resources Cell_Iur_Border “yes” “no”
(e.g. higher power Cell_Power_Avail [dBm] 43 43
amplifiers or second
RBS_CE_UL_Avail [CE] N/A N/A
carrier)
– Current degree of RBS_CE_DL_Avail [CE] N/A N/A
sharing of resources
among different layers
. A Figure220
Cell attributes related to cell/RBS
configuration

. A Figure221
Critical Cells Optimization
Operator’s strategy should be well known
 Primary goals:
– Avoid dropping of guaranteed services due to congestion
– Avoid blocking of handover request for guaranteed services
– Avoid blocking of non-handover requests for guaranteed
services
 Fine tuning:
– Improve the situation for guaranteed-hs and non-
guaranteed services
 Basic actions:
– Raise absolute level at which this kind of requests are
blocked/affected
– Increase the margin between the threshold for this kind of
requests and the threshold for the lower priority requests

. A Figure222
RRC blocking example
 Data aggregated over
the evalutaion period for Blocking for RRC Conn and PS Int RAB Establishment
day hour 1.5
RRC Adm
PS Inter Adm
Blocking percentage [%]

 Who is blocked?  RRC
blocking can be reflected 1
in “guaranteed” service
blocking
0.5
 What is the limiting

resource?  100%
blocking due to DL
0
transmitted carrier power 1 2 3 4 5 6 7 8 9 101112131415161718192021222324
day hour
pmNoOfRrcReqDeniedAdm; pmNoOfRrcCsReqDeniedAdm;
pmNoOfNonHoReqDenied<RAB>; pmNoFailedRabEstAttempt<CAUSE>
. A Figure223
Failures contribution to capacity
limitations 3
Handover Failures
Failure percentage [%]

2.5
 Noticeable soft handover
addition failures 2
 Significant percentage of 1.5

non-guaranteed services 1
up.switches
0.5
 However, these KPIs
considers any failure 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
day hour
reason! Channel Switching Failures DCH-DCH
12
Failure percentage [%]

10
GPEH enables the precise calculation of
who is blocked (e.g. g/g-hs/ng; ho/non- 8
ho) and what is the limiting resource 6
INTERNAL_SYSTEM_BLOCK
4
INTERNAL_ADMISSION_CONTROL_RESPONSE
INTERNAL_CHANNEL_SWITCHING 2
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
day hour
. A Figure224
Failures contribution to capacity
limitations
 Soft Congestion and Congestion policies have affected “non-
guaranteed” connections
 No impact on “guaranteed” ones
Soft congestion actions for PS interactive Congestion actions for PS interactive
12 20
18
10
Number of occurrences
Number of occurrences
16
14
8
12
6 10
8
4 6
4
2
2
0 1 2 3 4 5 6 7 8 9 101112131415161718192021222324 0 1 2 3 4 5 6 7 8 9 101112131415161718192021222324
day hour day hour

. A Figure225
Critical Cells Optimization
Parameter Value
 TC1 and TC2 aims at
Ref TC1 TC2 TC3 protecting the guaranteed
service connections (and the
non-guaranteed/handovers)
pwrAdm 85 85 85 85 by means of an increase of
beMarginDlPwr
beMarginDlPwr 0 5 10 5
 TC3 tries to minimize the
possible problems for
pwrAdmOffset 0 0 0 5 guaranteed/handover
requests and to reduce the
probability of entering a
pwrOffset 5 5 5 5 congestion situation

. A Figure226
“Radio” Resource Characterization
 What: determine the current status of the "radio
resources“
 Why: operator can understand which resources are
close to "congestion" and how many cells are going
into "congestion" sooner or later  Network
expansion/upgrade; Traffic Steering; New features
introduction
 How:
1. Calculate the distribution of peak radio resource usage
during the evaluation period.
2. Take a certain percentile of the distribution (e.g. 90th).
3. Compare with the Capacity Management thresholds
 The results can be grouped for the cells that have

similar profiles in terms of resource configuration
. A Figure227
Downlink Power utilization
 Based on:
– pmTransmittedCarrierPower for Hs cells
– pmTransmittedCarrierPowerNonHs for non-Hs cells
 Peak values (e.g. 95° percentile per ROP) can be easily obtained (pdf
counters)
 Values normalized with MaximumTransmissionPower parameter (to
be compared with AC threshold, pwrAdm)
first layer < 1% first layer second layer

Pu>70% (HSDPA cells) 9%
19% 17% 21% 19% 50%<Pu<70%
32%
Pu<30% 50%<Pu<70% Pu<30% 50%<Pu<70%
Pu<30%
63% 60% 59%

30%<Pu<50% 30%<Pu<50% 30%<Pu<50%

. A Figure228
Peak to average factor consumption
 Based on:
– pmSum<RAB>Establish,
pmSamples<RAB>Establish
and numHsPdschCodes
– pmSumDlCode and
pmSamplesDlCode
– GPEH
INTERNAL_DOWNLINK_CHANNELIZATION
_CODE_ALLOCATION
- Factor 2 (at RBS level)
 Peak-to-average factor must be
used! Based on:
– pmNoOfRadioLinks[SF_dl]
– Same GPEH as above

. A Figure229
Downlink Code utilization 30%<Cu<50%
3%
First layer
(non-HS)
Distribution of Peak DL code usage per cell
1 97%
First layer non-hs
0.9 Cu<30%
First layer hsdpa
Second layer
0.8
0.7
45%
0.6 First layer
50%<Cu<70%
(HS)
cdf
0.5 55%
30%<Cu<50%
0.4
0.3
0.2 30%<Cu<50%
0.1
9%
0
Second layer
10 20 30 40 50 60 70 80 90
DL Code Usage [%]
91%
Cu<30%

. A Figure230
Uplink hardware utilization
Current RBS HW availability
14% 64 CE
 Based on: 96 CE
128 CE
– pmNoOfRadioLinks[SF_ul/dl] 42%
in P4
– Pm[Ul/Dl]Credits from P5.0.17
44%
– GPEH
INTERNAL_RBS_HARDWARE_MONIT
OR_UPDATE Distribution peak UL HW usage per RBS
1
 Peak values can be easily 0.9
0.8
obtained 0.7
 Normalized with TX/RAX 0.6

64 CE RBSs
cdf 0.5 96 CE RBSs
board capacity or licensed 0.4
128 CE RBSs
capacity (to be compared 0.3

0.2
with AC threshold, 0.1
ul/dlHwAdm) 0
0 20 40 60 80 100
Peak UL hardware usage per RBS [%]
. A Figure231
Interpolation graph for KPIs
 What: capacity projection per cell
 Why: how much additional traffic a certain cell can cope with before reaching the
limit for a certain “radio resource”
 How:
1. Evaluate Traffic Indicator for each sample (15 minutes ROP) of the evaluation
period.
2. Evaluate peak resource usage indicator for each sample.
3. Sort the data per Traffic Indicator.
4. Aggregate samples with similar Traffic Indicator values to reach statistical
significance.
5. Evaluate average Traffic Indicator and average peak resource usage for the
aggregated block.
6. Repeat until all samples are included
x
PI x
x
x Evaluate Trend
x
TI

. A Figure232
Break Point 90
880
90
Break
Break point
pointanalysis
analysis(Cell
(Celllevel)
level)
Congestion limit
Congestion limit
DL code usage [%]

Analysis (Cell)
Peak DL code usage [%]

0
70
70
actual distr
interp
interp
60
60
trend interp (lower bound)
trend
trend interp (upper bound)
50
50 interp
Max traf
Max traf
40
40
Av
Avtraf
traf Max traf projection
Max traf projection
Break
Break point
pointanalysis
analysis(Cell
(Celllevel)
level) 30
30
Av traf
Av trafprojection
projection
42.5
42.5
Congestion limit
Congestion limit 20
20
4242 10
Peak DL Power [dBm]
0
0 50
50
100
100
150
150
200
200
250
250
300
300
350
350
400
400
450
450
DL Power [dBm]
41.5 41.5
Average DL traffic volume [kbps/cell]
Average DL traffic volume [kbps/cell]
41 41
40.5
40.5
40 40
 Power “congested” now!
actual distr
39.5 39.5 interp
interp
trend interp (lower bound)
39 39
trend
trend interp (upper bound)  Additional traffic before any
interp
Av. Traf.
Av. Traf. Max. Traf.
Max. Traf. DL code limitation issues
38.5
38.5
0
0
20
20
40
40
60
60
80
80
100
100
120
120
Average
AverageDL
Average DLtraffic
DL traffic
trafficvolume
volume[kbps/cell]
volume [kbps/cell]
[kbps/cell]

. A Figure233
Break Point Analysis (RNC)
 Capacity projection for
the whole RNC Break point analysis (RNC level)
30
 Sum up the results for
each cell of the RNC 25
DL Power
Critical cells [%]

20
 How much traffic can DL Codes

15
be handled before X%
of the cells are 10
“congested”? 5
Traffic Projections
 What is likely to be the Current traffic
0
most limiting resource 10 15 20 25 30
Average served RNC traffic per week [kbps/cell]
35 40
in the near future

. A Figure234
. A Figure235

Ericsson 3G Chapter 3 (Service Accessibility) - WCDMA RAN Opt - P7

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Ericsson 3G Chapter 3 (Service Accessibility) - WCDMA RAN Opt - P7

Caricato da

Copyright:

Formati disponibili

WCDMA RAN P6 Optimization

Chapter 3: Service Accessibility

1. Explain the function of Idle Mode Behavior,

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

Accessibility is defined as the ability of a user to obtain

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

TE/MT Local UMTS Bearer Service External

Radio Access Bearer Service CN Bearer

Radio Bearer Iu Bearer Backbone

3GPP TS 23.107, QoS Concept and Architecture

User Radio Bearers

Signaling Radio Bearers PDCP BMC

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

RRC Connection Setup

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

Idle mode Squal, Srxlev,

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

 1st category KPIs is to identify which cells or RBSs having accessibility

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

• It may repeat RRC Connection Request message N300

• There is a chance that access success rate for some cells

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

 pmTotNoRrcConnectReqCsSucc   pmTotNoRabEstablishSuccess  RAB  

Where <RAB> = Speech, CS64 or CS57

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

• exclude directed-retry to GSM from the RAB establishment

• The load-sharing with GSM from the RRC Request

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

The percentage of AMR calls compared to the normal speech

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

The percentage of EUL calls

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

 PLMN selection and reselection

 Cell selection and reselection

 Location area (LA) and routing area (RA) registration

 Reading system information

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

PLMN selected PLMNs

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

The UE normally operates on its home PLMN. However, a Visited

A UE successfully registers on a PLMN if it finds a suitable cell to

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

Squal = Qqualmeas- qQualMin > 0

Where Pcompensation = max(maxTxPowerul – P;0)

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

• qRxLevMin is also sent in the system information (SIB 3

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

• P is the UE maximum output power according to its class.

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

• The UE shall measure the CPICH Ec/No and the CPICH

• The UE shall filter the Ec/No and RSCP measurements of

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

To control the cell size in Idle mode use

qHyst - (presented by qHyst1 and qHyst2) are added to the

qOffset – (qOffset1 or qOffset2) add an offset value for a

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

The use of HCS is controlled by the cell parameters

© Ericsson AB 2008 03_03813 LZU 108 6924 Uen Rev

HCS priority level 0 is the lowest priority and level 7 is the