ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

(1)

Alcatel-Lucent W-CDMA - Introduction to UTRAN QoS and Traffic Load Monitoring

Alcatel-Lucent UTRAN 3G QoS

analysis and Traffic Monitoring

TRAINING MANUAL

3FL12826ABAAZZZZA Edition 1

(2)

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring

2

Legal Notice

Switch to notes view!

Safety Warning

Both lethal and dangerous voltages are present within the equipment. Do not wear conductive jewelry while working on the equipment. Always observe all safety precautions and do not work on the equipment alone.

Caution

The equipment used during this course is electrostatic sensitive. Please observe correct anti-static precautions.

Trade Marks

Alcatel and MainStreet are trademarks of Alcatel.

All other trademarks, service marks and logos (“Marks”) are the property of their respective holders including Alcatel-Lucent. Users are not permitted to use these Marks without the prior consent of Alcatel or such third party owning the Mark. The absence of a Mark identifier is not a representation that a particular product or service name is not a Mark.

Copyright

This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No other use or transmission of all or any part of this document is permitted without Alcatel-Lucent’s written permission, and must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from Alcatel-Lucent.

Use or transmission of all or any part of this document in violation of any applicable Canadian or other legislation is hereby expressly prohibited.

User obtains no rights in the information or in any product, process, technology or trademark which it includes or describes, and is expressly prohibited from modifying the information or creating derivative works without the express written consent of Alcatel-Lucent.

Lucent, The Lucent logo, MainStreet and Newbridge are registered trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is subject to change without notice. © 2007 Alcatel-Lucent. All rights reserved.

Disclaimer

In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including lost profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not Alcatel has been advised of the possibility of such damages.

Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an endorsement nor a recommendation.

Please refer to technical practices supplied by Lucent for current information concerning Alcatel-Lucent equipment and its operation.

(3)

3

Switch to notes view!

Page Section 1: Radio Network Performance overview

Section 2: Monitor the Radio Network Performance Section 3: Monitoring and Troubelshootin Methods

Section 4: Network Accessibility Monitoring & Troubleshooting Section 5: Retainibility Monitoring & Troubleshooting

Section 6: Mobility Monitoring & Troubleshooting

Section 7: Network Quality Monitoring & Troubleshooting Section 8: Capacity Monitoring & Troubleshooting

Section 9: Traffic/Call Profile Monitoring Section 10: Stability Troubelshooting Section 11: HSxPA Performance Monitoring Section 12: Appendices

(4)

4

Table of Contents [cont.]

Switch to notes view!

(5)

5

Course Objectives

Switch to notes view!

Welcome to Introduction to UTRAN QoS and Traffic Load Monitoring

After successful completion of this course, you should be able to:

Explain what is UTRAN QoS and what are the available Alcatel-Lucent performance

information sources for that purpose.

Detect an immediate UTRAN problem triggered by a QoS Alerter.

Detect a QoS problem with Key Performance Indicators.

Apply the Alcatel-Lucent methods to diagnose a QoS problem and find a probable cause for

3 QoS problem cases.

(6)

6

Course Objectives [cont.]

Switch to notes view!

(7)

7

About this Student Guide

Switch to notes view!

Conventions used in this guide

Where you can get further information

If you want further information you can refer to the following: Technical Practices for the specific product

Technical support page on the Alcatel website: http://www.alcatel-lucent.com

Note

Provides you with additional information about the topic being discussed. Although this information is not required knowledge, you might find it useful or interesting.

Technical Reference

(1) 24.348.98 – Points you to the exact section of Alcatel-Lucent Technical Practices where you can find more information on the topic being discussed.

Warning

Alerts you to instances where non-compliance could result in equipment damage or personal injury.

(8)

8

About this Student Guide [cont.]

Switch to notes view!

(9)

9

Self-Assessment of Objectives

At the end of each section you will be asked to fill this questionnaire

Please, return this sheet to the trainer at the end of the training

Switch to notes view!

Instructional objectives Yes (or globally yes) No (or globally no) Comments Contract number : Course title :

Client (Company, Center) :

Language : Dates from : to :

Number of trainees : Location :

Surname, First name :

Did you meet the following objectives ? Tick the corresponding box

Please, return this sheet to the trainer at the end of the training

(10)

10

Self-Assessment of Objectives [cont.]

Switch to notes view!

(11)

Section 1 Page 1

Do not delete this graphic elements in here:

Alcatel-Lucent W-CDMA UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring

1

3FL12921AAAAWBZZA Edition 1

Section 1 Radio Network

Performance Overview

(12)

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring

Radio Network Performance Overview Section 1 Page 2

Blank Page

This page is left blank intentionally

Second edition EL ABED, Achrafe 2007-10-20 02 First edition EL ABED, Achrafe 2007-08-24 01 Remarks Author Date Edition Document History

(13)

Section 1 Page 3

Objectives

To be able to explain what is UTRAN QoS and what are

the main performance optimization steps

Main steps:

Define the end-user QoS in UMTS and localize where the

UTRAN QoS take place.

(14)

Objectives [cont.]

(15)

Section 1 Page 5

Switch to notes view!

Page

1 Define QoS inside the Network 7

What is End user QoS over UMTS ? 8

What is End user QoS over UMTS ? 9

UMTS Traffic Classes 10

Standard QoS Bearer 11

Mapping Teleservices to QoS 12

What is QoS UTRAN in UMTS? 13

What is QoS UTRAN in UMTS 14

2 Network optimization process 15

Network Life cycle 16

Network Deployment 17

Pre-launch Optimization 18

Pre-launch Optimization 19

Cluster Optimisation 20

Cluster Optimisation – Data + Voice 21

Cluster Optimisation – 3G-2G+other services 22

Cluster Optimisation – 3G-2G+other services 23

Network Optimization 24

Network Acceptance 25

Key Performance Indicators (KPI) 26

Network Acceptance 27

Network Optimization 28

Self-Assessment on the Objectives 29

(16)

Table of Contents [cont.]

Switch to notes view!

(17)

Section 1 Page 7

(18)

Radio Network Performance Overview Section 1 Page 8 1 Define QoS inside the Network

What is End user QoS over UMTS ?

Quick data

transmission

(delay & bit rate)

Several

applications

simultaneaously

...

More

interactivity

(delay & jitter)

End user expectations concerning services usage over UMTS

I want to download the new Formula One game while discussing with my daughters,

But I need a sufficient bit rate in order to download this famous game …

(19)

Section 1 Page 9

•Various data rates

(from voice 12.2kbps up to 384 Kbps FDD)

•Various connections (real time CS & non real time PS) •Asymmetric traffic patterns

•Various QoS (blocking, delay, throughput, BLER)

Multi-services environment

Load optimisation over

a common transmission medium

Scarce & costly radio resources Heterogeneous terrestrial resources

1 Define QoS inside the Network

What is End user QoS over UMTS ?

But technology constraints…

leading to an efficient usage of resources over UMTS

UMTS networks have been designed to transmit packet and circuit switched applications on the same medium (radio or terrestrial)

Information generated by independent sources must be efficiently multiplexed on the same transmission medium UMTS supports traffic with very different bandwidth and QoS requirements. For instance :

Traffic generated by data transfer services and Internet access is essentially bursty and unpredictable Data transmission between machines is sensitive to loss but usually not to end-to-end delay or jitter Speech (and, more generally, real-time applications) requires strict limits on the transmission delay, but

can cope with reasonable loss rates

The system must use the transmission resources efficiently (not only scarce radio spectrum, but also terrestrial resources) Especially the radio and access part (e.g. "Last Mile") must provide a cost-effective transfer service while minimising investment and operating costs

Transmission links and the radio interface must be loaded as heavily as possible to achieve statistical multiplexing gain while meeting the QoS requirements (but operator must make a trade-off between subscribed QoS and radio constraints)

(20)

Transfer Delay requirement

Transfer Delay variation

Low bit Error rate Guatanteed bit rate Conversational Streaming Interactive

Example of Multimedia Applications with their QoS requirements

Conversational Real time services:VoIP, Video Call, Audio-conferencing

Streaming Broadcast services (audio, video), News, Sports

Interactive WEB browsing, Interactive Chat, Games, m-commerce

Background E-mail, SMS, database downloads, measurements transfer

Required QoS depends on the applications

UMTS Traffic Classes

Four QoS Classes defined in 3GPP standards

Transfer Delay requirement

Transfer Delay variation

Low bit Error rate

Guatanteed bit rate Conversational stringent stringent less constrained stringent

Streaming less constrained constrained less constrained constrained

Interactive constrained not constrained constrained not constrained

Four QoS classes are defined in 3GPP standards. Conversational Class:

Preserve time relation (variation) between information entities of the stream Conversational pattern (stringent and low delay)

e.g. voice

Streaming Class:

Preserve time relation (variation) between information entities of the stream e.g. streaming video

Interactive Class:

Request Response pattern Preserve Payload content Web Browsing

Background Class:

Destination is not expecting the data within a certain time Preserve payload content

Background download of Emails. Exercise:

(21)

Section 1 Page 11

Standard QoS Bearer

UTRAN

CN

Gateway

UE

UMTS Bearer Service

External Bearer

Service

UMTS Bearer Service

Radio Access Bearer Service

(RAB)

CN Bearer

Service

Backbone

Bearer Service

Iu Bearer

Service

Radio Bearer

Service

Radio Physical

Bearer Service

Physical

Bearer Service

Uu

Iu

Teleservice

...

UE

Node

(22)

Mapping Teleservices to QoS

Conversational (delay <<1 sec)

Interactive (delay approx.1 sec)

Streaming (delay <10 sec)

Background (delay >10 sec) Conversational

voice and video Voice messaging

Streaming audio

and video Fax

E-mail arrival notification FTP, still image E-commerce, WWW browsing, Telnet, Interactive games Increasing Error Tolerance Increasing Delay Tolerance

(23)

Section 1 Page 13

What is QoS UTRAN in UMTS?

SGSN GGSN RNC RNC NodeB NodeB Border Gateway MT UMTS bearer IP IP IP IP GTP GTP GTP

Multimedia or Data Application

GTP tunnel _GTP

ATM PVC

IP IP IP IP

RADIO Bearer _{MPLS Tunnel} _{MPLS Tunnel}

Media Gateway

PDP PDP

IPv4 / IPv6 Backbone

(24)

What is QoS UTRAN in UMTS

A comprehensive set of mechanisms answering end users expectations

Several

applications

simultaneaously

...

✓ Multi RAB per user

✓ RAB parameters mapping flexibility

Quick data

transmission

(delay & bit rate)

✓ Power control

✓ HSDPA/HSUPA channels

✓ DiffServ within RNC

More

interactivity

(delay & jitter)

✓ iRM/Always On transitions

✓ DiffServ within RNC

To insure simultaneous applications for a given user the network should:

Allow multi RAB per user

A certain flexibility in the mapping of RAB parameters (at logical, transport and physical layers)

Quick data transmission is directly impacted by:

Power control efficiency

The usage of the HSDPA/HSUPA channels

And the usage of DiffServ within the RNC over IuPS interface to insure higher priority for high bit

rate services

More services interactivity is achieved by:

Appropriate iRM and AO states transitions

(25)

Section 1 Page 15

(26)

Radio Network Performance Overview Section 1 Page 16 2 Network optimization process

Network Life cycle

Network

Design

Pre-launch

Optimization

Network

Planning

Network

Deployment

Network

Acceptance

Network

Optimization

N

e

tw

o

rk

D

e

n

si

fi

ca

ti

o

n

N

e

tw

o

rk

S

u

p

e

rv

is

io

n

Performance Management in the UTRAN consists in

collection and record by Network Element

administration by NM

storage, consolidation and display at the OS (NPA + RNO)

Areas of performance evaluation are

traffic levels for both user and signalling traffic

traffic load on the radio interface (signalling and user traffic); usage of resources within the network nodes;

user activation and use of supplementary services, etc.

resource access measurements

resource availability

(27)

Section 1 Page 17

Network Deployment

After a site installation, a verification procedure is performed

Drive Tests procedure:

Scanner + Mobile locked in 3G

AMR service only

Incar measurements

Optimisation tasks:

Validate Softer HO for each sector.

No cross sector.

Reliability of site identifiers applied at OMC (Lac, Rac, SC, …)

Site report

A site report embedded to the commissioning report is provided

Network Design Pre-launch Optimization Network Planning Network Deployment Network Acceptance Network Optimization N e tw o rk D e n si fi ca ti o n N e tw o rk S up e rv is io n

(28)

Why Pre-launch Optimization is so important in a 3G network ?

CDMA is a frequency re-use 1 technique

Reducing the interference directly leads to optimized coverage and capacity

Network design installation errors may lead to more interference

Wrong parameter settings (e.g. wrong neighbor declaration) may lead to

more interference

2 Network optimization process

Pre-launch Optimization

Network Design Network Deployment Network Planning Pre-launch Optimization Network Acceptance Network Optimization N e tw o rk D e n si fi ca ti o n N e tw o rk S up e rv is io n

Pre-launch in a 3G network is much more important than in 2G where imperfections of design (best

(29)

Section 1 Page 19

Pre-launch Optimization

Lessons from customers’ roll-out

Drive test roads define thanks to the RNP study.

AMR service.

If the network if already commercially open => NO LOAD should be

applied .

Mobiles should be locked and unlocked in 3G mode .

Roll-out to be driven by cluster definition to ensure an optimal

Optimisation work.

Definition

A cluster is a group of sites.

core cluster: inner sites, covering the area to be optimize

ring: surrounding ring of sites circling the core cluster

CORE

(30)

Cluster Optimisation

Optimisation unit = cluster

A cluster is a group of sites located inside a polygon.

The clusters are defined according to site priority.

Optimisation phases = 3G+Voice, 3G-2G+others

Drive Test procedure for 3G+Voice

Scanner +Mobiles Originating calls:

AMR services : locked in 3G long calls

Mobile originating calls

The drive test roads should de defined in advance based on RNP study.

Incar measurements

CORE RING

(31)

Section 1 Page 21

Cluster Optimisation – Data + Voice

Analysis

3G layers

Quality & RF coverage

SHO area

Validation of the drive test roads

Verification of the exclusion area

Typical problems

Weak coverage

Missing neighbor

Corrective tasks performed

Tilt and azimuth modification (Operator is informed)

Neighbor declaration

(32)

Cluster Optimisation – 3G-2G+other services

Drive Tests procedure for optimisation

Scanner

Mobiles:

Voice Mobile Originating Call: Unlock 3G, long call, short call (90’, 30’’)

Video Mobile to Mobile: locked in 3G, long call, Short calls (90’, 15’’). The

terminating mobile stays under good radio condition

PS DL XXX, locked in 3G. (384 Kbps => 4 Mo, 128 Kbps => 2 Mo)

Incar measurements

CORE RING

(33)

Section 1 Page 23

Cluster Optimisation – 3G-2G+other services

Analysis

Interference

Quality & RF coverage

SHO & HHO area

Drop and Establishment Failures

Typical problems

Pilot overshooting

Weak coverage

Missing neighbor

Corrective tasks performed

Tilt and azimuth modification (Operator is informed)

Neighbor declaration (inter system included)

(34)

Network Optimization

Network optimization with radio load

Same activities as in cluster optimization but network (city) wide, to

ensure the homogeneous quality of the network

Optimize a group of clusters covering a certain region (city)

Focus done in the inter-cluster areas

Test bearers which were not tested during cluster optimization

Radio Simulated load: OCNS in DL, UL load

To check the UMTS inter-working with GSM in order to improve the

QoS:

in idle mode: 3G-to-2G cell reselection

in dedicated mode: 3G-to-2G handover

Pre-launch Optimization

Lessons learnt from customer roll-out:

Network optimization without load could be removed

Radio problems already seen during cluster optimization or network optimization with load time

saving

Most constraining service tested: CS64

(35)

Section 1 Page 25

Network Acceptance

The contract is based on commitments,

defined in order to ensure the required

radio quality of service.

Radio Fine Tuning

Network Design Network Deployment Network Planning Pre-launch Optimization Network Optimization N e tw o rk D e n si fi ca ti o n N e tw o rk S up e rv is io n Network Acceptance

The commitments are based at city level, and they enable to get a Go

decision for :

Commercial opening

Payment triggering

After completion of network optimisation, then Network Acceptance will be performed:

It is performed with operator’s radio engineers

It enables to check the radio optimisation performed by Alcatel

It acts as a green light to open services to customers

The acceptance procedure may be divided in several steps:

Radio Acceptance

System Acceptance

Inter RAT Acceptance

Lessons learnt from customer roll-out for Acceptance:

The acceptance services can be Voice, Video and PS DL

=>Radio acceptance

The other services /applications can be tested under good radio condition (fix points or under 2/3

NodeB) on several parts of the network. =>System acceptance

(36)

Key Performance Indicators (KPI)

Define a set of KPIs with corresponding thresholds

Common approach between Customer and Alcatel

Network Acceptance

> Commitment by Alcatel on

KPIs in a turnkey deployment

Call set-up

success rate

Handover

success rate

Call drop rate

Quality of CS

& PS call

End-user

quality for

voice

KPIs are measured at each Acceptance phase:

Mobile KPI (such as voice CDR in 3G-locked) during Radio Acceptance

Static KPI (such as PING) during System Acceptance

Inter-RAT KPI (such as voice CDR in 3G-2G) during Inter-RAT Acceptance

Define the right KPI (Key Performance Indicator):

Call set-up success rate: Ratio of successful call set-up over attempted call set-up

Handover success rate: Ratio of successful handovers over attempted handovers

Call drop rate: Number of calls which are prematurely terminated over the total number of calls

Quality of CS & PS call: Block error rate on transport channel blocks depending on the radio bearer

End-user quality for voice: MOS (Mean Opinion Score) combining perception and comfort

End-user quality for applications over IP: Throughput, response time, jitter and Packet Loss Rate for

streaming application

Typical KPIs:

AMR 12.2: Long voice calls

Number of call drop per hour, BLER

Visio CS64: 2-minute calls

Call success rate (number of call maintained during 2 min/call attempts), BLER

(37)

Section 1 Page 27

Network Acceptance

After completion of network optimisation, then Network Acceptance

will be performed :

It is performed with operator’s radio engineers

It enables to check the radio optimisation performed by Alcatel

It acts as a green light to open services to customers

The acceptance procedure may be divided in several steps:

Radio Acceptance

System Acceptance

Inter RAT Acceptance

KPI are measured at each Acceptance phase

Mobile KPI (such as voice CDR in 3G-locked) during Radio Acceptance

Static KPI (such as PING) during System Acceptance

(38)

Network traffic allows to use

OMC-R QoS statistics for Optimization

Some QoS problems can be found

that were had been observed

during Pre-launch optimization

Post-launch optimization aims at

Solve QoS degradations occuring during network life

Equipment failure

Traffic increase

Improving QoS by changing

radio parameters value from their default setting : Radio Fine Tuning

Antenna system configuration (height, tilt, azimuth): Design Fine Tuning

2 Network optimization process

Network Optimization

Network Design Pre-launch Optimization Network Planning Network Acceptance Network Optimization N e tw o rk D e n si fi ca ti o n N e tw o rk S up e rv is io n Network Deployment

Pre-launch optimization is based on drive tests. Therefore some QoS problems do not have been detected

when Post-launch optimization takes place after commercial launch and traffic ramp up.

Radio Fine Tuning is just one way of optimization for the Radio Network Optimizer.

RFT is used in order to optimize values of some key parameters whose current setting does not match the signal propagation or traffic characteristics in a certain area.

(39)

Section 1 Page 29

Self-Assessment on the Objectives

Please be reminded to fill in the form

Self-Assessment on the Objectives

for this module

The form can be found in the first part

(40)

(41)

Section 2 Page 1

Do not delete this graphic elements in here:

Alcatel-Lucent W-CDMA UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring

2

3FL12921AAAAWBZZA Edition 1

Section 2 Monitor the Radio

Network Performance

(42)

Monitor the Radio Network Performance Section 2 Page2

Blank Page

This page is left blank intentionally

Second edition EL ABED, Achrafe 2007-10-20 02 First edition EL ABED, Achrafe 2007-08-24 01 Remarks Author Date Edition Document History

(43)

Section 2 Page 3

Objectives

To be able to explain what are the available

Alcatel-Lucent UTRAN performance monitoring information

sources

Main steps:

Define what are the characteristics of the QoS counters and

the QoS indicators.

Interpret QoS reports

Correlate a QoS problem with information coming from

(44)

Objectives [cont.]

(45)

Section 2 Page 5

Switch to notes view!

Page

1 Define the QoS counters properties 7

Introduction 8

Counters Applicability 9

Counters: Definition 10

Collect performance data with ALU Solution (1/3) 11

Counter Data Management (1/3) 14

Counter Data Management (2/2) 15

NPO Introduction Plan 16

NPO Products for UTRAN monitoring 17

NPO Products for UTRAN monitoring 18

Counter Groups and Families (2/2) 19

Counter Types (1/6) 20 Counter Types (2/6) 21 Counter Types (3/6) 22 Counter Types (4/6) 23 Counter Types (5/6) 24 Counter Types (6/6) 25

Load (or SI) Counter: example 26

Counter Locations for C-Node Families 27

Counter Locations for BTS Families 30

Counter Locations for Passport Families 31

Counter’s Screenings 32

Counter’s Screenings 33

2 Define metrics properties and Analysis 34

Metrics Definitions 35

Metrics Generic Formulas 36

Metric Format 37

Example: RRC Connection Success 38

Counter Aggregation 39

Report Definition 40

Report generation 41

Evolution report 42

Top N Report 43

Alarm Detection Report 44

Key Performance Indicators 45

Network Key Performance Indicators 46

Counter based KPIs 47

Methodological precautions 48

KPI value 49

Network Element aggregation 50

With other indicators 51

With alarms 52

With parameters modification 53

3 Alcatel-Lucent Call Trace Solution Overview 54

Introduction 55

Call Trace Applicability 56

Call Trace Session Types (1/4) 57

(46)

Table of Contents [cont.]

Switch to notes view!

Page

Configuring a Call Trace Session 62

Configuring a Call Trace Session 63

Post Processing Call Trace Data (2/2) 64

Self-Assessment on the Objectives 65

(47)

Section 2 Page 7

(48)

The Alcatel-Lucent Performance Management Solution is based on:

Observation Counters

Call Trace

Counters and Call Trace allow to:

Implement an Accurate Performance Management Activity

Increase Control over Global Network Performance

Cover all aspects of QOS (Reliability, Accessibility, Retainbility, Quality, Traffic and Capacity, …)

Provide Fast and Appropriate response to Performance Issues

Implement mechanisms allowing to identify, troubleshoot and solve network issues and malfunctions in a timely manner

Provide invaluable data for network optimization, network evolution and business planning

1 Define the QoS counters properties

Introduction

Network Design Pre-launch Optimization Network Planning Network Acceptance Network Optimization N e tw o rk D e n si fi ca ti o n N e tw o rk S u p e rv is io n Network Deployment

(49)

Section 2 Page 9

Counters Applicability 1 Define the QoS counters properties

Counters Applicability

Monitoring and troubleshooting

• Issues & nw malfuctions detection • Failure identification and analysis

Report Executive level KPIs

• Accessibility • Retainability • Network Quality

• Network Traffic and Congestion • Network Reliability

Network expansion planning • Derive Call Models

• Capacity Evaluation / Growth planning • Network architecture optimization • Transmission plan optimization • New services introduction

Network Optimization

• Detailed Performance monitoring • Quality of Service Evaluation • Network Parameters Tunning • Cell level optimisation (RF & Cell Parameters)

(50)

RNC 1 Define the QoS counters properties

Counters: Definition

• Counters measure a number of specific events (occurring in an entity of

the UTRAN), during a defined period

• Counter values are generated by

either the Control Node part of the RNC equipment

or the BTS equipment

• Counter values are then stored in the performance server

Performance Server BTS

BTS counters (every 60’)

CN & Passport counters (every 15’)

The wording “counter and “measurement” are often equally used in the documentation for

identifying the same concept.

Usually, Alcatel-Lucent prefers to use the term “counter” to distinguish a counter from a

“(radio) measurement” (3GPP concept). A counter is periodically elaborated on periods expressed in minutes or hours, e.g. 30 min, while a measurement is elaborated on periods expressed in milliseconds, e.g. 500 ms.

Periods of counter

Granularity Period (GP)

It is the duration of the events counting in the selected entity of the network.

It corresponds to the minimum time granularity at which counters are provided. It can be modified. The QoS monitoring daily and hourly periods are used. By default:

RNC counters are uploaded every 15 min.

BTS counters are uploaded every hour (minimum).

Observation Period (or Measurement Period)

It is the time period for which the counter will be used for metric computation and display

on operator request.

Busy hour corresponds to the hour of the day when the traffic is the highest. It allows to

analyze performances of the cells, when the traffic is higher. It is really important for congestion/capacity analysis and also forecasting.

Daily period gives global information on the day. To compare busy hour and daily data, is

necessary to check the influence of the traffic.

Weekly period

(51)

Section 2 Page 11

Monitor the Radio Network Performance Section 2 Page11 1 Define the QoS counters properties

Collect performance data with ALU Solution (1/3)

RNC

W-NMS

BTS WIRELINE BACKBONE OBS Observation File containing counters OBS

At the end of Granularity period the file is sent to

the W-NMS. 15 minutes for CN/AN/IN

Equipments

The Equipment resets the counters and starts incrementing the counters OBS OBS Observation files Database OBS OBS

(52)

Collect performance data with ALU Solution (2/3)

Performance Server

Observation files Database OBS OBS Citrix Server VPN / Internet LAN PrOptima Client Citrix Client PrOptima Client PrOptima Server

(53)

Section 2 Page 13

Collect performance data with ALU Solution (3/3)

Generation of reports

Executive reports at

weekly and daily level.

Detailed reports at 15-mn level on specific network elements

Proptima

Creating metrics

Executive Detailed reports

Analysis of the reports

Graphs creation

Alarms on thresholds on raw counters and metrics

Creating metrics

Formula editor Thresholds setting

Proptima provides a very easy way to instantly create new reports and KPI

(54)

BTS Counters RNC C-Node Counters

NIMS – PrOptima Server

ADI APM

BTS RNC

NIMS – PrOptima Client

Performance Server

XML Observation files (3GPP I/F)

ADI: Access Data Interface APM: Access Performance Mgt

3GPP XML – 3rd Party Tool

Passport Platform Counters

ALU Proprietary I/F

Counter Data Management (1/3)

The Performance Server is responsible for Data Collection, Mediation and Storage:

Counters are organised in 3GPP compliant XML record files

Each record file contains the counters produced by a single NE collector (NodeB, RNC C-Node Counters, RNC Passport, AN/POC Passport) for a given observation period

The XML files are optionally compressed on W-NMS Performance Server to reduce storage space

The Performance Server Provides some temporal aggregation of data:

Single Observation Period (corresponds to the original collection

granularity)

Hourly Aggregation

(55)

Section 2 Page 15

Counter Data Management (2/2)

/opt/nortel/data/access/observation

YYYYMMDD/<NE>

<hourly aggregated o bs file name> 32.104 -01.dtd

<daily aggregated obs file name> 20020613/RNC-RNC14_CN h20010613.1800+0100 -1900+0100_RNC-RNC14_CN d20010613.0000+0100 -0000+0100_RNC-RNC14_CN 20020613/BTSEq -XXXX070 A20010613.1800+0100 -1900+0100_ BTSEq -XXXX070 h20010613.1800+0100 -1900+0100_ BTSEq -XXXX070 d20010613.0000+0100 -0000+0100_ BTSEq -XXXX070 A20010613.1845+0100 -1900+0100_RNC-RNC14_CN A20010613.1800+0100 -1815+0100_RNC-RNC14_CN A20010613.1815+0100 -1830+0100_RNC-RNC14_CN A20010613.1830+0100 -1845+0100_RNC-RNC14_CN XML DTD (Document Type Definition) available on W-NMS, compliant with 3GPP

Tree Structure generic example

RNC C-Node example, quarter hour observation files

BTS Counters example, hourly observation files

RNC C-Node example, hour and daily observation files

The data is organised in the following Performance Server directories:

BTS Counters - /opt/nortel/data/access/observation/<YYYYMMDD>/BTSEq-<neName>

RNC CNode Counters

-/opt/nortel/data/access/observation/<YYYYMMDD>/<neName>_CN Passport Platform Counters

RNC INode

-/opt/nortel/data/access/observation/<YYYYMMDD>/<neName>_IN

RNC ANode / POC

(56)

NPO Introduction Plan

OAM5.1 OAM06 OAM5.0 NPO NIMS PrOptima™ based PR OAM5.2 UA5.0 UA5.0 UA5.1 UA5.0 UA5.1 UA06 New UA05 PM Customers

Inband Migration Database Migration

Current NIMS PrOptima™ Customers or New UA4.2 PM customers

UTRAN upgrade to UA5.0/5.1 UA5.0 UA5.1 UA5.0 UA4.2 UA4.2

(57)

Section 2 Page 17

NPO Products for UTRAN monitoring

Integrated into UTRAN program

Mono ROC

Mono technology

Integrated into MS-OMC

Multi ROC

Multi Technology

W-NPO

MS-NPO

(OAM06)

W-NMS

W-NPO

MS-OMC

MS-NPO

MS-Portal client

W-NMS

2G OMC-R

Customer NMS

MS-SUP

(58)

Alcatel-Lucent Groups the Access Network observation in 3 major groups: 1 Define the QoS counters properties

Counter Groups and Families (1/2)

RNC Passport Platform Counters

RNC C-Node counters

•RNC C-Node counters – To monitor the UMTS features & functionalities at the

RNC

•BTS counters – To monitor the UMTS functionalities and Node-B platform

•RNC Passport platform counters – To monitor the RNC platform and the ATM

layer

C-Node Application Counters Node-B Counters

I-Node Platform Counters A-Node Platform Counters

(59)

Section 2 Page 19

Counter Groups and Families (2/2)

RNC C-Node counter families

• Radio Link Management

• Handover

• Power Management

• RRC Connection

• IU Connection

• RAB and RB Management

• Security

• Paging

• Mobility

• Radio Measurement

• QOS Performance

• User Plane Common Traffic

• IUR Interface

• User Plane Dedicated Traffic

RNC PASSPORT Platform counter families

• ATM port

• Logical Processor Use

• Adjunct Processor Stats

• Account ATM Vcc • Account ATM Vpc BTS counter families • PCM statistics • Radio counters • CallP counters • ATM statistics • EEC • IMA statistics • IP statistics • HSDPA statistics • HSUPA statistics • Radio statistics

The Counter Groups are further divided in Families according to a

given UMTS feature or to a Performance Management purpose

(60)

Cumulative Counter (CC)

• A cumulative counter provide raw counts of events.

• Is incremented each time the counted event occurs.

Counter Types (1/6)

E = triggering Event

Xi = registered measurement sample

Counter.Cum=

∑

_GP

X

_i X₂ X₁ X₃ X₄ X₅ X₆ Xi

Granularity Period

GP begins GP ends E E E E E E E

(61)

Section 2 Page 21

Cumulative Counter Example

Ex: RRC.SuccConnEstab

Number of successful RRC connection establishments

Counter Types (2/6)

E = triggering Event = Reception by the RNC of a RRC CONNECTION SETUP COMPLETE message

Xi = registered measurement sample

Counter.Cum=

∑

_GP

X

_i X₂ X₁ X₃ X₄ X₅ X₆ Xi

Granularity Period

GP begins GP ends E E E E E E E

(62)

Value Counter (DER - Discrete Event Registration)

•

These counters provide the average values from raw counts base on

internal events.

•

The time interval between two events is random and is not

accessible to users

•

A value counter is incremented by a value attached to the event

itself.

•

Each Value counter provides:

Cumulated value

Number of events

Minimum value

Maximum value

Averaged value - computed using the cumulated value divided by

the number of events

(63)

Section 2 Page 23

DER counter example

VS.UplinkRssi - Provides the uplink RSSI per cell during a reporting period.

Counter Types (4/6)

Counter.Cum = ∑_GPX_i

Counter.Nbevt = N

Counter.Avg = Counter.Cum / Counter.Nbevt

X₂ X₁ X₃ X₄ X₅ X_i X_N

Granularity Period

GP begins E E E E E E E Counter.Min =Min_GP(X_i) Counter.Max =Max_GP(X_i)

E = triggering Event = The Uplink RSSI is updated on each reception on a NBAP common measurement containing an uplink RSSI measurement

(64)

Load Counter (SI – Status Inspection)

• These counters provide average values from raw counts obtained by internal

sampling

• The time interval between two events is constant and is not accessible to

users

• The counter is incremented by a sampled value on the sampling event

occurrence (every 100ms). Data related to the mean value is captured every nth sampling, where n can be 1 or larger

• Each counter provides:

Cumulated value

Number of events

Minimum value

Maximum value

Averaged value - computed using the

cumulated value divided by the number of events

Start End

(65)

Section 2 Page 25

Load Counter (SI – Status Inspection) example

Counter #13 VS.RadioLinkEstablishedPerCellprovides the average, min and max number of NBAP Radio Links simultaneously established in a cell

Event E_a= setup of radio link(s) Event E_b= addition of a radio link(s) Event E_c= deletion of a radio link(s)

X_i= number of Radio Links simultaneously established

Counter Types (6/6)

Granularity Period

GP begins _{GP ends} X₁ T X₂ X₃ X₄ X_n-1 X_n T X_i E_c T E_b E_a E_a

Only VS.RadioLinkEstablishedPerCell .Avg, .Min, .Max

(66)

Load (or SI) Counter: example

Counter VS.RadioLinkEstablishedPerCell #13

RL established

3 4 RL setup (1RL) RL addition (2RL) 6 5 RL deletion (1RL)

time

Granularity Period

T

X_i= 3 4 4 4 6 6 6 6 6 5 5 5 5 5

#11.Nbevt = 15

#11.Min = 3

#11.Cumul = 75

#11.Max = 6

#11.Avg = #11.Cumul / #11.Nbevt = 75/15 = 5

(67)

Section 2 Page 27

Counter Locations for C-Node Families

FddCell counter

• A “FddCell”counter is incremented

for each FddCell of the serving RNC on which the mobile is connected to, when the event occurs.

Ex:

VS.RadioLinkSetupSuccess.DlAsCnfCsSpeech–

Providing the number of NBAP RL Setup Successes for DL Speech

RNC counter

• A “RNC”counter is incremented

when an event occurs on the serving RNC of a connection.

Ex: VS.IuSccpCnxSuccess. CsReqByRNC –

Providing the number of SCCP connection successes requested by the RNC on the Iu CS interface Serving RNC Drift RNC Iur

(68)

Counter Locations for C-Node Families

Reference FddCell counter

• A “Reference FddCell”counter is

incremented only for the FddCell identified as the Primary FddCell of the connection when the event occurs .

• Such a counter is only incremented

if the reference FddCell belongs to the serving RNC on the connection. Otherwise Neighbouring RNC location is used.

Ex: VS.RadioBearerSetupSuccess.TgtCallHsdpa

–Providing the number RRC Radio Bearer

Setups Sucesses when the target DL Radio Bearer is HSDPA Serving RNC Drift RNC Iur

(69)

Section 2 Page 29

Counter Locations for C-Node Families

Neighbouring RNC counter

• A “Neighbouring RNC”counter is

incremented when:

The even is occuring on a neigbouring RNC

Ex: VS.IurSccpCnxSuccess.

EstablishedAsDriftRnc–Providing the number

of successful SCCP established connections when this neighbouring RNC serves as a drift.

When the Primary Cell on the Active Set is controlled by a Drift-RNC Ex: VS.RadioBearerSetupSuccessNeighbRnc.

TgtCallPsIb384 –Providing the number RRC

Radio Bearer Setups Successes when the target DL Radio Bearer is DL PS I/B 386 and the Primary Cell of the connection is controlled by a D-RNC. Serving RNC Drift RNC Iur

(70)

Counter Locations for BTS Families

The BTS Counters are available at:

• AtmVcc • Board • BTSCell • BTSEquipment • IMAgroup • IPinterface • PCMLink • Passive Component New UA05 Locations:

• LocalCellGroup

(71)

Section 2 Page 31

Counter Locations for Passport Families

The Passport counters are

available at:

•AtmPort

•Lp (Logical Processor)

•Ap (Adjunct Processor - UA05) •AtmPort/Vcc (UA05)

•AtmPort/Vpc (UA05)

(72)

Counter’s Screenings

Most of Alcatel-Lucent counters provide measurements for more

than one observation.

Counters are breakdown into sub-counters (referred in Alcatel-Lucent’s

nomenclature as counter screenings)

Examples of counter screenings are:

Split per failure reason of counters providing number of failures (number of drops, procedure failures, etc …)

Split per establishment cause (ex. RRC Connection Establishment counters) Split per service type, DL bit rate, UL bit rate, HSDPA, RAB type, etc. Split per domain (CS, PS)

Split per 3GPP cause value (provided in Information Elements of exchanged signalling)

…

Main screenings:

1. Uplink Traffic Counter Screenings

2. Downlink Traffic Counter Screenings

3. DlRbSetId,UlRbSetId,TrafficClass derived screening per granted Rab

4. Target type of call for Radio Link Reconfiguration

5. Source Type of call release mapping

6. Derived AsConf Screening for PS DlAsConfId

7. Derived AsConf Screening for CS DlAsConfId

8. Derived AsConf Screening for DlAsConfId Avg Nbr Estab

9. Derived AsConf Screening for UlAsConfId Avg Nbr Estab

10.Type of call for dropped last radio link

11.Target Type of call setup mapping

12.Target type of call for Radio Bearer Reconfiguration

13.Traffic Class Combined UL and DL RbSetIds (COMB UL DL RBSET) .

(73)

Section 2 Page 33

Counter’s Screenings

Example: Screenings on the left table are applicable to the counters on the right table

(74)