WCDMA RAN P6 Optimization

Chapter 2: Data Collection

 Chapter 2 Objectives

After this module, the participants will be able to:

1. Explain the collection and storage process for performance

statistics
2. Explain the different counter types and their limitations
3. Explain the OSS-RC Data Collection (Subscription Profiles)
4. Setup formulas and statistics for RAN optimization
5. Calculate the traffic volumes and retrieve the busy hour in the
network

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure2 2 - Data Collection
 Data Collection
The procedure:

1. Performance Statistics (PS) are continuously collected from

all Network Elements (NE)

2. PS are stored persistently in Operation Support System,

Radio and Core (OSS-RC).

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure3 2 - Data Collection
 Data Collection
The complete WCDMA Radio Access Network (RAN)
Performance Management (PM) collects data from:

• Radio Base Station (RBS)

• Radio Network Controller (RNC)

• Radio Access Network Aggregator (RANAG – RXI)

• OSS-RC.

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure4 2 - Data Collection
 Counters used for BH calculation
 BH calculation based on the total number of successful RRC
Connection requests - pmTotNoRrcConnectReqSuccess

 BH calculation based on the total payload concerning the traffic

carried both in UL and DL on dedicated and common channels, both
for PS and CS services - payload traffic counters:

Radio Connection type UL Payload counter DL Payload counter

Speech pmUlTrafficVolumeCs12 pmDlTrafficVolumeCs12
PS64/64 pmUlTrafficVolumePs64 pmDlTrafficVolumePs64
PS64/128 pmUlTrafficVolume Ps128 pmDlTrafficVolume Ps128
PS 64/384 pmUlTrafficVolume Ps384 pmDlTrafficVolume Ps384
CS 57.6 (streaming) pmUlTrafficVolumeCs57 pmDlTrafficVolumeCs57
CS 64 (UDI) pmUlTrafficVolumeCs57 pmDlTrafficVolumeCs57
Speech/PS 64 multirab pmUlTrafficVolumeCs12Ps64 pmDlTrafficVolumeCs12Ps64
PS Common pmUlTrafficVolumePsCommon pmDlTrafficVolumePsCommo
n

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure5 2 - Data Collection
 Busy Hour - Example
 Example of traffic distributed over 10 days

Traffic distribution changes per day and per service

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure6 2 - Data Collection
 Counter types
 Peg counters - A counter that is increased by 1 at each occurrence of a
specific activity.
 Gauge counters - A counter that can be increased or decreased
depending on the activity in the system.
 Accumulator counters - A counter that is increased by the value of a
sample.
 Scan counters - A counter that is increased by 1 each time the
corresponding accumulator counter is increased.
 Probability Density Function counters - A PDF counter is a list of range
values. A value is sampled (read) periodically.
 Discrete distributed measurements – DDM counters are series of values
recorded during a reporting period.
 ATrigAcc counter – a counter that is increased by the value of a sample
and the sampling is only done when there is some activity.
 ATrigScan counter - a counter that is increased by 1 each time the
corresponding TrigAcc counter is increased.
 Calculated Statistics counters - A counter whose value is determined by
other counters.

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure7 2 - Data Collection
 Counter types
Gauge counters

Example: ATM Adaption Layer 2 Access Point Counters,

pmExisOrigConns, which is the number of existing
connections for the AP originating in this node.

Accumulator counters

Increased by the value of a sample.

Indicates the total sum of all sample values taken during a
certain time.
The name of an accumulator counter begins either with
pmSum or pmSumOfSamp.
Example:pmSumOfSampAseDl

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure8 2 - Data Collection
 Counter types, con’t
Scan counters

Increased by one each time the corresponding accumulator

counter is increased.

It indicates how many samples have been read, and added to

the related accumulator counter.

Scan counters => measure the average value of all samples

by dividing the accumulator counter by the scan counter.

The name of a scan counter begins with pmSamples or

pmNoOfSamp.

Example: pmNoOfSampAseDl
© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev
. A Figure9 2 - Data Collection
 Counter types, con’t I
NUMBER OF SCANS

• Every specific period of time the scan counters are increased

by one

• Accumulator counters are scanned and the scanning results

are added to the accumulation counters

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure102 - Data Collection
 Recording Period
Recording Period = 40 seconds

Device
Scanning Intervals = 5 or 10 seconds

5 devices 5 10 10 10 5

1 2 3
1 x x x x
4 5
2 x x

6 7 8
3 x x

9 10
4 x x x

11 12 13
5 x

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure112 - Data Collection
 Traffic flow

Number of Seizures is the number of seized devices only during the

recording period of time
All the above values are obtained from the different counters defined in the system.

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure122 - Data Collection
 Counter types, con’t II
ATrigAcc & ATrigScan counters

ATrigAcc increased by the value of a sample and the sampling

is only done when there is some activity.

The name of an TrigAcc counter begins with pmSumAct and

of a TrigScan with pmSamples

TrigACC and TrigSCAN counter form pairs

Average value can be calculated by TrigACC / TrigSCAN.

Example: A trigger can be incoming 3GPP message, internal

system event etc,
ATrigAcc: pmSumUlRssi, ATrigScan: pmSamplesUlRssi
© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev
. A Figure132 - Data Collection
 Counter types, con’t III
Probability Density Function (PDF)counters

1. A value is sampled periodically.

2. If the value falls within a certain range, the range counter

for that range is increased.

All range counter values are collected and stored in a ROP file
at the end of each reporting period.

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure142 - Data Collection
 Counter types, con’t IV
Probability Density Function (PDF)counters

Example: SIR values are split into three ranges:

1. Range1 = [-11 dB – -4 dB],

2. Range2 = [-4 dB – +4 dB],
3. Range3 = (+4 dB – +20 dB],

Values are read every 3 minutes over a 15 minute period with

Results => reported values = -10, -3, +5, +5, +6

Range Counters reports are:

1. RangeCounter1 = 1
2. RangeCounter2 = 1
3. RangeCounter3 = 3
© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev
. A Figure152 - Data Collection
 Example of statistics from a PDF
counter

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure162 - Data Collection
 Counter types, con’t V
Calculated Statistics counters

• Counter produced by other counters.

• The calculation is performed in the OSS-RC Statistics

database.

• The ROP files are opened in order to be transferred into the

database and the calculations are made by the database itself
during this process.

Important!!!
Names of all the counters created in NEs start with pm,
Names of the OSS-RC calculated statistics counters start
with cm.
© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev
. A Figure172 - Data Collection
 Counter Classification
 There are two general classifications of the statistic
counters:

Grouped depending on where they are generated (specific NE)

Grouped depending on the area of interest

 Radio Network – RNC specific counters

 Radio Network – RBS specific counters

 Transport Network counters

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure182 - Data Collection
 Grouping the counters based on
their NE Origin

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure192 - Data Collection
 Statistics Setup

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure202 - Data Collection
 Statistics Setup

In order to monitor the statistics counter

values throughout the time, specific
counters have to be active.

Only when a counter is active, values are

generated, collected and can be analysed.

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure212 - Data Collection
 Statistics profile
Statistics Profile:
Profile

The definition of a set of one or more counters that the user

wants to activate

Statistics profile = an entity in the OSS-RC GUI that helps

users to manipulate counter administration.

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure222 - Data Collection
 Statistics profile activation
1. NE type
2. One or more NE instances
3. MO Class or MO Instance type
4. Cell selection - Only for these
cells, the counters will be handle
through the profile
5. One or more selected counters -
each counter is activated only
once - one profile
6. Scheduling
Continuous – changes only by the user
Scheduled –starts at a specified point in time and stops
after a specified duration
Periodical - Repeated a specified no of times in intervals

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure232 - Data Collection
 Pre-defined profiles
When a profile is created by a user in OSS-RC it is called
user-defined profile

pre-defined profiles are profiles available immediately after the

start-up of new NEs.

Network Pre-defined Content

Element Profile
RNC Primary Counters needed for main Radio Network KPIs
RNC Secondary Most important counters for troubleshooting
RBS Primary Most important Radio Network counters on the
RBS level

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure242 - Data Collection
 Main differences between user-defined
and pre-defined profiles
Action User-defined Profiles Pre-defined Profiles
Create Possible Not Possible
Modify Partially ** Not Possible
Schedule Possible Continuous only
Suspend Possible Possible
Resume Possible Possible
Delete Possible Not Possible*
Type MO Possible for RNC for Not Possible
Instance Utran Utran Cell and
Utran Relation
counters
* Pre-defined profiles can still be deleted but only via direct PM IRP operations, however they cannot be
recreated

** The operator is allowed to change the attributes of all unlocked user-defined Subscription Profiles with
Inactive Admin state and/or change the network element selection for an unlocked, standard user defined
standard statistics profile with Active Admin state.
© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev
. A Figure252 - Data Collection
 Statistics Scanner

The statistics profiles are only visible in the OSS-

RC GUI.

The actual communication between OSS-RC and

NEs is performed on another level – through
statistics scanners.

A statistics scanner is a sort of instance of a

specific profile at a specific NE.

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure262 - Data Collection
 Profiles, Scanners and Counters –
RNC example
Example: One profile may be
mapped to a corresponding
scanner (“A”) at several NE
instances ,
i.e. RNC Profile “A” mapped
to scanner “A” at RNC1 and
RNC2.

Profiles active or suspended

=> corresponding scanners at
selected NEs also active or
inactive.

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure272 - Data Collection
 Pre-Defined Scanner Types

There are only two predefined scanners in the RNC.

• Primary Scanners contain only the most important RNC

radio network counters, used to calculate high-level KPIs.

• Secondary Scanners contain important counters mainly

used for troubleshooting.

Both PRIMARY and SECONDARY scanners are initially

active on startup of the RNC

For predefined counters in the scanners check on CPI,

Performance Statistics Description 25/1551-AXD 105 03/1 Uen H

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure282 - Data Collection
 Counter Limitations

There are limitations on the total amount of counter instances that can be
simultaneously active in each NE.

RNC

Total counters RNC can handle in a ROP: 1,700,000 counters

Incremented Counters: 750,000 with R4 HW or later on the O&M board.

Incremented Counters: 230,000 (in total 500,000) with R3 HW

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure292 - Data Collection
 Counter Limitations

RBS – 17,000 counters

RXI – 65,000 counters

Before activating statistics profiles it is recommended to check if the

number of counters would exceed the limits for each NE.

For more details on counter limitations please see section 3.4 Counter
Limitations in CPI 85/1553-HSD 101 02/4 Uen.

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure302 - Data Collection
 Counter Optimization – Hints
how to calculate number of counters

For large RNC configurations it is recommended to set the following rules:

• Keep the primary profile active all the time, thus allowing the radio network KPI
performance monitoring on cell and higher levels.

• Keep the secondary profile active all the time if possible. If not, keep it active all
the time when there is no other competing activity.

• Keep the most important UniSaalTp, Aal2Ap, NniSaalTp, AtmPort, ImaGroup,

ImaLink, VclTp, VpcTp and VplTp counters active all the time. This is for the
continuous transport network KPI performance monitoring.

Set the parameter counterAlarmThreshold so that a warning alarm is

issued when that allowed limit for the Total no of counters is reached.

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure312 - Data Collection
 Counter Optimization – Hints
• Define Radio Network troubleshooting clusters, typically
about 20 RBSs.

Attention: In MO instance activation (i.e. a sub-set of the cells)

the maximum limit for each performance monitoring is 72, 000
counter instances.

• Perform Radio Network troubleshooting on specific clusters,

not on the whole RNC.

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure322 - Data Collection
 Counter Optimization – Hints
Problem

Functions contribute with a substantial number of counters

their counters cannot be simultaneously active.

Solution: Troubleshoot a function at a time

choose between troubleshooting inter-frequency handover,

soft/softer handover, inter-RAT handover, transport network
functions or all other radio network functions.

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure332 - Data Collection
 Counter Optimization – Hints con,t
• Some functions’ counters can be activated per cluster RBS

i.e. handover and all cell based counters

• some functions’ counters cannot be activated per cluster

i.e. transport network counters

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure342 - Data Collection
 Counter Activation
 Once the wanted profiles and counters are activated, their values are
generated and being collected after each reporting period.

 A reporting period is always set to 15min starting at the 00, 15, 30 or

45 minute in an hour. When all profiles at one NE gets suspended,
the generation and collection stops for that NE.

 When a counter is active, a value is generated every Result Output

Period (ROP). At the end of each ROP, all the counter values
produced during that period are stored in one ROP file at the NE.
This file is in XML format and compressed using GZIP. The ROP
period is 15 minutes.

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure352 - Data Collection
 Radio Environment Statistics (RES)
RES can help Operators to:
 Evaluate and supervise network performance
 Estimate subscriber-perceived quality
 Perform network tuning and optimization
How?
Performing statistical measurements of important radio
characteristics per cell and save the results as
statistical distributions.
What's the main goal of this feature?
RES can be used to quickly find cells in the network
with coverage problems, or to find cells with bad
speech quality and high Block Error Rates (BLER)

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure362 - Data Collection
 RES Measurement and Services
RES measurements can be performed separately for
different services.
Measurement quantities: RES measurements
•DL BLER services:
•UL BLER Speech NB 12.2, 4.75, 5.9 and 7.95
Video; Streaming; Interactive;
•UE Tx power InteractiveHS; StreamingHS;
•DL CPICH Ec/No InteractiveEUL
•DL CPICH RSCP Speech NB 12.2 + Interactive
Speech NB 12.2 + Streaming
Speech NB 12.2 + InteractiveHS
Speech NB 12.2 + StreamingHS
Speech AMR-WB
Speech AMR-WB + Interactive
Speech AMR-WB + InteractiveHS
Speech AMR-WB + Streaming

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure372 - Data Collection
 RES Interface and Activation
Measurement Result Recording WCDMA ( MRR-W )
 Is an OSS-RC application that contains all necessary
user interfaces, post processing, KPI calculations and
reports
 MRR-W is part of the RNO package and contains GUIs to
define and manage the recording and post processing
and reports to present the results to the user
 The user interface is implemented by the MRR-W feature
as an application in OSS-RC
 MRR-W application in OSS-RC is used for RES
configuration and activation

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure382 - Data Collection
 RES Measurement Quantities
Diferent measurement areas can be activated:
UE Measurement
DL BLER; UE Tx power; DL CPICH Ec/No; DL CPICH RSCP
RNC Measurement
The UL BLER is implemented as:
number of transport blocks with faulty CRC
number of received transport blocks

RBS Measurement
Measurements of DL Tx code power per Spreading Factor (SF) are
implemented in the RBS
pmDpchCodePowerSf4 ….…up to……….pmDpchCodePowerSf256
Each counter has a range of 6 to 43 dBm and a resolution of 0.5 dBm

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure392 - Data Collection
 RES Results and Counters

Measurement results are stored in up to UL and DL BLER measurements

six pdf counter distributions per cell. pmResX[0] = 256 * “service”
pmResX[1] 0 ≤ BLER < 0.5
These counters are written in ROP files pmResX[2] 0.5 ≤ BLER < 1
in XML format as any other counter, but pmResX[3] 1 ≤ BLER < 1.5
are only active while a RES recording is pmResX[4] 1.5 ≤ BLER < 2
pmResX[5] 2 ≤ BLER < 2.5
active.
pmResX[6] 2.5 ≤ BLER < 3
pmResX[0] = 256 * ”service” + pmResX[7] 3 ≤ BLER < 3.5
pmResX[8] 3.5 ≤ BLER < 4
“measurement quantity”.
pmResX[9] 4 ≤ BLER < 4.5
The service variable is coded as follows: 0 pmResX[10] 4.5 ≤ BLER < 5
pmResX[11] 5 ≤ BLER < 6
= not active, 1 = speech, 2 = video …. pmResX[12] 6 ≤ BLER < 7
pmResX[13] 7 ≤ BLER < 8
The measurement quantity variable is pmResX[14] 8 ≤ BLER < 9
coded as follows: 0 = not active, 1 = DL pmResX[15] 9 ≤ BLER < 10
pmResX[16] 10 ≤ BLER < 15
BLER, 2 = UL BLER, 3 = UE Tx power,
pmResX[17] 15 ≤ BLER < 20
4 = CPICH Ec/No, 5 = CPICH RSCP. pmResX[18] 20 ≤ BLER

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure402 - Data Collection
 Statistical Data Mart
 The Statistics Data Mart is an optional database in OSS-RC3 and not
standard database, available for storing the statistics counters.
 It provides the ability to store the data for up to one year. All stored
data can be accessed through the SQL interface.
 The SDM offers the ability to aggregate the raw data based on time
and object, provides data reliability indicators, and generates the
Calculated Statistics counters.
 The time aggregation is performed for different periods – hour, day,
peak hours/day and week.
 The object aggregation is performed only for the Utran Cell counters
as they are aggregated on the RNC and then together with other
RNC counters up-to System level.

© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev

. A Figure412 - Data Collection
© Ericsson AB 2008 02_03813 LZU 108 6924 Uen Rev
. A Figure422 - Data Collection