ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

524
UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring - Page 1 All Rights Reserved © 2007, Alcatel-Lucent All rights reserved © 2007, Alcatel-Lucent 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 Copyright © 2007 by Alcatel-Lucent - All rights reserved Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent

description

ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Transcript of ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Page 1: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring - Page 1All Rights Reserved © 2007, Alcatel-Lucent

All rights reserved © 2007, Alcatel-Lucent

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

Alcatel-Lucent UTRAN 3G QoSanalysis and Traffic Monitoring

TRAINING MANUAL

3FL12826ABAAZZZZAEdition 1

Copyright © 2007 by Alcatel-Lucent - All rights reservedPassing on and copying of this document, use and

communication of its contents not permitted without written authorization from Alcatel-Lucent

Page 2: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring - Page 2All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © Alcatel-Lucent 2007

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.

Alcatel-Lucent, The Alcatel-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 Alcatel-Lucent for current information concerning Alcatel-

Lucent equipment and its operation.

Page 3: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring - Page 3All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring

3

Table of Contents

� 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

Section 13: Glossary

Page 4: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring - Page 4All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring

4

Table of Contents [cont.]

� Switch to notes view!

This page is left blank intentionally

Page 5: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring - Page 5All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring

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.

� Diagnose a dimensioning or load problem by monitoring the cell and the Node B traffic.

Page 6: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring - Page 6All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring

6

Course Objectives [cont.]

� Switch to notes view!

This page is left blank intentionally

Page 7: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring - Page 7All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring

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.

WarningAlerts you to instances where non-compliance could result in equipment

damage or personal injury.

Page 8: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring - Page 8All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring

8

About this Student Guide [cont.]

� Switch to notes view!

This page is left blank intentionally

Page 9: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring - Page 9All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring

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

����

Thank you for your answers to this questionnaire

Page 10: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring - Page 10All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load Monitoring

10

Self-Assessment of Objectives [cont.]

� Switch to notes view!

Other comments

����

Page 11: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 1

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

Do not delete this graphic elements in here:

All Rights Reserved © Alcatel-Lucent 2007

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

1 3FL12921AAAAWBZZA Edition 1

Section 1Radio Network

Performance Overview

Page 12: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 2

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

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 editionEL ABED, Achrafe2007-10-2002

First editionEL ABED, Achrafe2007-08-2401

RemarksAuthorDateEdition

Document History

Page 13: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 3

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview 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.

� Define the network optimization process

Page 14: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 4

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 4

Objectives [cont.]

This page is left blank intentionally

Page 15: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 5

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 5

Table of Contents

Switch to notes view!Page

1 Define QoS inside the Network 7What is End user QoS over UMTS ? 8What is End user QoS over UMTS ? 9UMTS Traffic Classes 10Standard QoS Bearer 11Mapping Teleservices to QoS 12What is QoS UTRAN in UMTS? 13What is QoS UTRAN in UMTS 14

2 Network optimization process 15Network Life cycle 16Network Deployment 17Pre-launch Optimization 18Pre-launch Optimization 19Cluster Optimisation 20Cluster Optimisation – Data + Voice 21Cluster Optimisation – 3G-2G+other services 22Cluster Optimisation – 3G-2G+other services 23Network Optimization 24Network Acceptance 25Key Performance Indicators (KPI) 26Network Acceptance 27Network Optimization 28Self-Assessment on the Objectives 29End of Module 30

Page 16: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 6

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 6

Table of Contents [cont.]

Switch to notes view!

This page is left blank intentionally

Page 17: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 7

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 7

1 Define QoS inside the Network

Page 18: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 8

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

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 …

And I do not want to wait when I ask for a new web page !

Page 19: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 9

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview 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 environmentLoad 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)

�Therefore it is important to identify mechanisms that optimise the load

Page 20: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 10

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 10

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

1 Define QoS inside the Network

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:

Fill the table with the following:

1. Yes

2. No

3. Stringent

4. Constrained

5. Less constrained

Page 21: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 11

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 11

1 Define QoS inside the Network

Standard QoS Bearer

UTRAN CN CNGateway

UE

UMTS Bearer Service External BearerService

UMTS Bearer Service

Radio Access Bearer Service(RAB)

CN BearerService

BackboneBearer Service

Iu BearerService

Radio BearerService

Radio Physical Bearer Service

PhysicalBearer Service

Uu Iu

Teleservice

... ...

UENode

Page 22: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 12

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 12

1 Define QoS inside the Network

Mapping Teleservices to QoS

Conversational(delay <<1 sec)

Interactive(delayapprox.1 sec)

Streaming(delay <10 sec)

Background(delay >10 sec)

Conversationalvoice and video

Voice messaging Streaming audioand video

Fax

E-mail arrivalnotification

FTP, still imageE-commerce,WWW browsing,

Telnet,Interactive games

IncreasingError

Tolerance

IncreasingDelay Tolerance

Page 23: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 13

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 13

1 Define QoS inside the Network

What is QoS UTRAN in UMTS?

SGSNGGSN

RNC

RNCNodeB

NodeB

BorderGateway

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

MediaGateway

PDP PDP

IPv4 / IPv6 Backbone

RSP RSP

Page 24: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 14

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 14

1 Define QoS inside the Network

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

� As well as the usage of DiffServ within the RNC to provide higher priority for interactive services

Page 25: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 15

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 15

2 Network optimization process

Page 26: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 16

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 16

2 Network optimization process

Network Life cycle

NetworkDesign

Pre-launch Optimization

NetworkPlanning

NetworkDeployment

NetworkAcceptance

NetworkOptimization

Network

Densification N

etwork

Supervisio

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

� Quality of Service

Page 27: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 17

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 17

2 Network optimization process

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

NetworkDesign

Pre-launch Optimization

NetworkPlanning

NetworkDeployment

NetworkAcceptance

NetworkOptimization

Network

Densification N

etwork

Supervisio

n

Page 28: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 18

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 18

� 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

NetworkDesign

Network Deployment

NetworkPlanning

Pre-launch Optimization

NetworkAcceptance

NetworkOptimization

Network

Densification N

etwork

Supervisio

n

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

servers distribution) can be masked by a frequency planning. In 3G a re-use 1 is the standard.

Page 29: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 19

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 19

2 Network optimization process

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 beapplied .

� 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

RING

Page 30: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 20

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 20

2 Network optimization process

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

Page 31: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 21

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 21

2 Network optimization process

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

� Parameter modification

Page 32: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 22

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 22

2 Network optimization process

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

Page 33: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 23

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 23

2 Network optimization process

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)

� Parameter modification.

Page 34: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 24

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 24

2 Network optimization process

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

� AMR service to test mobility to 2G

Page 35: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 25

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 25

2 Network optimization process

Network Acceptance

� The contract is based on commitments,

defined in order to ensure the required

radio quality of service.

Radio Fine TuningRadio Fine Tuning

NetworkDesign

Network Deployment

NetworkPlanning

Pre-launch Optimization

NetworkOptimization

Network

Densification N

etwork

Supervisio

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

Page 36: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 26

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 26

2 Network optimization process

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 rateQuality 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

� Packet background 64/384kbit/s

� Call success rate (number of call maintained until the end of transfer/call attempts), FTP throughput,

BLER

� Accessibility: short successive AMR & PS calls

� Call set-up success rate

Page 37: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 27

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 27

2 Network optimization process

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

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

Page 38: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 28

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 28

� 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

NetworkDesign

Pre-launch Optimization

NetworkPlanning

NetworkAcceptance

NetworkOptimization

Network

Densification N

etwork

Supervisio

n

NetworkDeployment

� 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.

It can also be used when other better solutions can not be implemented in a short time frame.

Page 39: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 29

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 29

Self-Assessment on the Objectives

� Please be reminded to fill in the formSelf-Assessment on the Objectivesfor this module

� The form can be found in the first partof this course documentation

Page 40: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1 � Page 30

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Radio Network Performance Overview Section 1� Page 30

End of Module

Page 41: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 1

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

Do not delete this graphic elements in here:

All Rights Reserved © Alcatel-Lucent 2007

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

2 3FL12921AAAAWBZZA Edition 1

Section 2Monitor the Radio

Network Performance

Page 42: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 2

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 2

Blank Page

This page is left blank intentionally

Second editionEL ABED, Achrafe2007-10-2002

First editionEL ABED, Achrafe2007-08-2401

RemarksAuthorDateEdition

Document History

Page 43: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 3

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance 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 other sources.

Page 44: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 4

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 4

Objectives [cont.]

This page is left blank intentionally

Page 45: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 5

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 5

Table of Contents

Switch to notes view!Page

1 Define the QoS counters properties 7Introduction 8Counters Applicability 9Counters: Definition 10Collect performance data with ALU Solution (1/3) 11Collect performance data with ALU Solution (2/3) 12Collect performance data with ALU Solution (3/3) 13Counter Data Management (1/3) 14Counter Data Management (2/2) 15NPO Introduction Plan 16NPO Products for UTRAN monitoring 17NPO Products for UTRAN monitoring 18Counter Groups and Families (2/2) 19Counter Types (1/6) 20Counter Types (2/6) 21Counter Types (3/6) 22Counter Types (4/6) 23Counter Types (5/6) 24Counter Types (6/6) 25Load (or SI) Counter: example 26Counter Locations for C-Node Families 27Counter Locations for C-Node Families 28Counter Locations for C-Node Families 29Counter Locations for BTS Families 30Counter Locations for Passport Families 31Counter’s Screenings 32Counter’s Screenings 33

2 Define metrics properties and Analysis 34Metrics Definitions 35Metrics Generic Formulas 36Metric Format 37Example: RRC Connection Success 38Counter Aggregation 39Report Definition 40Report generation 41Evolution report 42Top N Report 43Alarm Detection Report 44Key Performance Indicators 45Network Key Performance Indicators 46Counter based KPIs 47Methodological precautions 48KPI value 49Network Element aggregation 50With other indicators 51With alarms 52With parameters modification 53

3 Alcatel-Lucent Call Trace Solution Overview 54Introduction 55Call Trace Applicability 56Call Trace Session Types (1/4) 57Call Trace Session Types (2/4) 58Call Trace Session Types (3/4) 59Call Trace Session Types (4/4) 60Configuring a Call Trace Session 61

Page 46: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 6

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 6

Table of Contents [cont.]

Switch to notes view!Page

Configuring a Call Trace Session 62Configuring a Call Trace Session 63Post Processing Call Trace Data (2/2) 64Self-Assessment on the Objectives 65End of Module 66

Page 47: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 7

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 7

1 Define the QoS counters properties

Page 48: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 8

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 8

� 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

NetworkDesign

Pre-launch Optimization

NetworkPlanning

NetworkAcceptance

NetworkOptimization

Network

Densification N

etwork

Supervision

NetworkDeployment

All these factors contribute to NW Management OPEX Reduction

Page 49: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 9

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 9

CountersApplicability

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)• New features introduction

Page 50: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 10

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 10

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

� Monthly period

Page 51: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 11

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 11

1 Define the QoS counters properties

Collect performance data with ALU Solution (1/3)

RNC

W-NMS

BTS

WIRELINE BACKBONE

OBS

ObservationFile containingcounters

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

Page 52: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 12

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 12

1 Define the QoS counters properties

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

Page 53: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 13

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 13

1 Define the QoS counters properties

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 creat e new reports and KPI

Creation of metrics formulae through formula editor

Page 54: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 14

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 14

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 PlatformCounters

ALU Proprietary I/F

1 Define the QoS counters properties

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

� Daily Aggregation

Page 55: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 15

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 15

1 Define the QoS counters properties

Counter Data Management (2/2)

/opt/nortel/data/access/observation

YYYYMMDD/<NE>

<single-period obs file name>

<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 C-Node Counters -

/opt/nortel/data/access/observation/<YYYYMMDD>/<neName>_CN

� Passport Platform Counters

� RNC I-Node -

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

� RNC A-Node / POC -

/opt/nortel/data/access/observation/<YYYYMMDD>/<neName>_AN

Page 56: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 16

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 16

1 Define the QoS counters properties

NPO Introduction Plan

OAM5.1 OAM06OAM5.0

NPO

NIMS

PrOptima ™

based PR

OAM5.2

UA5.0 UA5.0UA5.1

UA5.0UA5.1UA06

New UA05 PM Customers

Inband Migration

Database Migration

Current NIMS PrOptima™ Customers or

New UA4.2 PM customersUTRAN upgrade to

UA5.0/5.1

UA5.0UA5.1

UA5.0

UA4.2UA4.2

Page 57: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 17

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 17

1 Define the QoS counters properties

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-NMS2G OMC-R

Customer NMS

MS-SUP

Page 58: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 18

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 18

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

BTS counters

Page 59: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 19

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 19

1 Define the QoS counters properties

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

Page 60: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 20

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 20

Cumulative Counter (CC)• A cumulative counter provide raw counts of events. • Is incremented each time the counted event occurs.

1 Define the QoS counters properties

Counter Types (1/6)

E = triggering Event

Xi = registered measurement sample

Counter.Cum= ∑GP Xi

X2X1 X3 X4 X5 X6 Xi

Granularity Period

GP begins

GP ends

EE E E E E E

Page 61: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 21

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 21

Cumulative Counter ExampleEx: RRC.SuccConnEstabNumber of successful RRC connection establishments

1 Define the QoS counters properties

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 Xi

X2X1 X3 X4 X5 X6 Xi

Granularity Period

GP begins

GP ends

EE E E E E E

Page 62: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 22

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 22

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

1 Define the QoS counters properties

Counter Types (3/6)

Page 63: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 23

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 23

DER counter exampleVS.UplinkRssi - Provides the uplink RSSI per cell during a reporting period.

1 Define the QoS counters properties

Counter Types (4/6)

Counter.Cum = ∑GP XiCounter.Nbevt = NCounter.Avg = Counter.Cum / Counter.Nbevt

X2X1 X3 X4 X5 Xi XN

Granularity Period

GP begins

EE E E E E E

Counter.Min = MinGP(Xi)Counter.Max = MaxGP(Xi)

E = triggering Event = The Uplink RSSI is updated on each reception on a NBAP

common measurement containing an uplink RSSI measurement

Xi = registered measurement sample

Page 64: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 24

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 24

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

1 Define the QoS counters properties

Counter Types (5/6)

Page 65: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 25

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 25

Load Counter (SI – Status Inspection) exampleCounter #13 VS.RadioLinkEstablishedPerCell provides the average,min and max number of NBAP Radio Links simultaneously established ina cell

Event Ea = setup of radio link(s) Event Eb = addition of a radio link(s) Event Ec = deletion of a radio link(s)

Xi = number of Radio Links simultaneously established

1 Define the QoS counters properties

Counter Types (6/6)

Granularity Period

GP begins GP ends

X1

T

X2 X3 X4 Xn-1 Xn

T

Xi

Ec Ea EaEbT

Only VS.RadioLinkEstablishedPerCell .Avg, .Min, .Maxare meaningful but .Cum and .Nbevt are also computed for Aggregation of metrics

Page 66: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 26

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 26

1 Define the QoS counters properties

Load (or SI) Counter: example

Counter VS.RadioLinkEstablishedPerCell #13RL established

3

4

RL setup (1RL)

RL addition (2RL)

6

5

RL deletion (1RL)

timeGranularity Period

T

Xi = 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

5

Page 67: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 27

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 27

1 Define the QoS counters properties

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

ServingRNC

DriftRNCIur

Page 68: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 28

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 28

1 Define the QoS counters properties

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

ServingRNC

DriftRNCIur

Page 69: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 29

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 29

1 Define the QoS counters properties

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.

ServingRNC

DriftRNCIur

Page 70: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 30

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 30

1 Define the QoS counters properties

Counter Locations for BTS Families

The BTS Counters are available at:• AtmVcc• Board• BTSCell• BTSEquipment• IMAgroup• IPinterface• PCMLink• Passive Component

New UA05 Locations:• LocalCellGroup• PCMATM

Page 71: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 31

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 31

1 Define the QoS counters properties

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)

The Objects collecting counters are those underlined

Page 72: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 32

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 32

1 Define the QoS counters properties

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 p er 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 Reconfiguratio n

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

The List of available screenings is given in the appendix.

Page 73: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 33

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 33

1 Define the QoS counters properties

Counter’s Screenings

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

Page 74: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 34

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 34

2 Define metrics properties and Analysis

Page 75: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 35

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 35

2 Define metrics properties and Analysis

Metrics Definitions

Metric = f (counter1, counter2, …)

A formula composed of one or several counters.

For instance: ∑ RRC.SuccConnEstab [RRC screenings]

• Metric definitions may include counter screening such as voice, video, or data.

• Some counters screened by As Conf Id (DL or UL), or RRC establishment causes.

• Other counters are provided with screening details.

� To interpret data coming from the counters, it is necessary to define some metrics.

� A metric is composed of one or several counters.

� These counters can be screened for some specific metrics:

� Counters screened by As Conf Id (DL or UL), or RRC establishment causes.

The screening is detailed in the appendix.

� Other counters with screening details.

The screening value used in the metric is directly set with the counter.

� Note that if no screening details are given (no brackets), all screenings of the counter must

be used for the metric.

� The screening is identified as followed:

� Downlink As Conf Id = DL_AsConfId_Screenings (screened by SRB, CS, PS, Combined, PS 8,

PS 32, PS 64, PS 128, PS 256, PS 384, CS 14.4, CS 57.6, CS 64, Voice)

� Uplink As Conf Id = UL_AsConfId_Screenings

� RRC release = RRC_Release_Screenings (specific screening for RRC Failures)

� RRC establishment causes = RRC_Screenings (screened by Call, CS, PS, Identification)

� RAB = RAB_Screenings (screened by CS, PS)

Page 76: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 36

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 36

2 Define metrics properties and Analysis

Metrics Generic Formulas

Request

FailureSuccess

Counter: RequestPM Counter

Calculated Indicator

Legend

Success Rate Failure Rate

Indicator: Request – SuccessCounter: Success

Indicator: Success/request Indicator: Failure / request

Number of requests = PM counter

Number of successes = PM counter

Success rate = Successes / Requests

Number of failures = Requests - Successes

Failure rate = Failures / Requests

Ratio for Sub-group X (e.g. a cause X among a set of causes [0..N])

� Calculated as: Number of events with X / Number of events with [0..N]

Page 77: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 37

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 37

2 Define metrics properties and Analysis

Metric Format

Optional: Comment or monitoring recommendation Comment

Counter: #Counter Id = Name of the counter [all possible screenings]

Associated counters

Metric formula with counter name, or metric id with specific screenings used

Metric formula

����

NetworkRNCGroup of cells

Cell

NC

ApplicabilityMetric history

Metric NameMetric Id

�Metric Id allows to identify the metric. It is expressed as Subfamily-xxx where:

� subfamily is the family of the counters composing the metrics (RRC, Iu, RL…),

� xxx is the number of the metric inside the subfamily.

�Metric history can be either

� NEW, the metric has been created for the given release,

� UPDATE, the metric existed in the previous release but counters have been modified,

� NC, No change, the metric existed in the previous release and stays as it is in the current

one.

�Applicability: Level at which the metric can be computed.

�Metric formula is expressed with counter external names.

When it is composed of the sum of all the screenings of one counter it will be expressed as

the following example:

∑Counter_name [List_screenings]

Ex.: Total number of RRC attempts = ∑(VS.RRC.AttConnEstab [RRC screenings])

The list of the RRC screenings can be found in the appendix of the document.

� When the metric is composed of the sum of some screenings of one counter but not of the

entire list it will be expressed as follow:

Counter_name [screening1 + screening3 + screening 8]

Ex.1: Number of RRC attempts for CS calls = VS.RRC.AttConnEstab[0 + 1 + 5 + 6 + 9]

Ex.2: Average Iu SCCP established = VS.IuAvgNbrSccpCnx [WithCoreNetworkCs.Avg

+WithCoreNetworkPs.Avg]

Page 78: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 38

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 38

2 Define metrics properties and Analysis

Example: RRC Connection Success

Necessary for the calculation of RRC Connection success rate, this metric allows also to see the call distribution in terms of success of the request.

Indeed, this metric can be computed per RRC establishment cause:• Calls: RRC call screenings• CS calls: RRC CS call screenings• PS calls: RRC PS call screenings• Registration: RRC identification screenings

Monitoring recommendation

#0403 RRC.SuccConnEstab (RRC establishment causes )Associated Counters

∑ (RRC.SuccConnEstab [RRC screenings] )Metric formula

Number of RRC connection success (sum of all causes)Meaning

����

NetworkRNCGroup of cellsCell

NC

ApplicabilityMetric history

RRC connection success RRC001

� The first phase of a call establishment (speech or data) is the RRC connection. One RRC

connection can lead to:

� several Iu SCCP connections ( multi service CS+PS, simultaneous CS + PS attach/detach, CS

location update during a PS call)

� no RAB in case of signaling connections

� 1 (or several RAB) in case of one call (multi service).

Page 79: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 39

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 39

GP = 15mn

2 Define metrics properties and Analysis

Counter Aggregation

CV2CV1 CV3 CVi CV96Start

Object aggregation is needed for:• RNC level metric based on FDDCell counters• Network level metricTime aggregation is needed:• when Observation Period of the metric is bigger than

the Granularity Period of the counters used

Observation Period = 1 day

See comments below

CV: Counter Value

�The default granularity period are 60 minutes for BTS and 15 minutes for RNC.

They are configurable.

�The following rules shall be followed for time aggregation.

�Rtotal is the rule applied to CC counters:

�CV.cum = CV1.cum + CV2.cum + …+ CVn.cum

�Rload / Rval is the set of rules appled to SI and DER counters

�CV.cum = CV1.cum + … + CVn.cum

�CV.nbevt = CV1.nbevt + … + CVn.nbevt

�CV.avg = (CV1.cum + .. + CVn.cum) / (CV1.nbevt + .. +CV2.nbevt)

�CV.min = min (CV1.min, .., CVn.min)

�CV.maCV = maCV (CV1.max, .., CVn.max)

Page 80: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 40

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 40

2 Define metrics properties and Analysis

Report Definition

� A report is a set of metrics.

� Report can be from high level to a low level to help investigate/analyze from general to specifice.g. network level report -> RNC level report -> FddCell level report

� Some reports are pre-defined, others are created/customized by the user.

� Types of reports:

� Evolution report

� Top N report

� Alarm detection report

� Alcatel-Lucent proposes pre-defined reports

� A report consists of a set of metrics going from a high level view to a low level (from a

network view to a network element view, i.e. Network -> RNC -> Fddcell):

� Set of reports at executive level.

� Detailed reports (evolution and top N reports).

� Reports based on alarm generation.

� The format of the report is a graph or a table.

� In order to be efficient it’s recommendable to name the reports with prefixes that indicates

what level they are referring to (RNC, fddcell) followed by the report name.

� Several types of reports can be used:

� Evolution report: the objective of the evolution reports is to show and compare the

statistics related to a set of NEs, over a period of time.

� Top N report: the objective of top N reports is to filter the N worst (or best) NEsaccording to a specific criterion. Such reports are run over a set of NEs and for a single date.

� Alarm detection report: every report can be complemented with reports coming from

alarm detection based on thresholds.

Page 81: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 41

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 41

2 Define metrics properties and Analysis

Report generation

RNC1

Report generation

Page 82: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 42

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 42

2 Define metrics properties and Analysis

Evolution report

RRC Cnx Estab. Fail. RatioRRC Abnormal Termination rateTotal RRC cnx Request

12/08/2007 13/08/2007 14/08/2007 15/08/2007 16/08/2007

12% 18% 8% 24% 10%

2% 5% 8% 12% 4%

125 229 45 5 78

8% 2% 4% 12% 9%

15% 8% 5% 8% 12%

52 127 88 74 78

8% 4% 7% 14% 6%

3% 2% 5% 10% 5%

42 58 38 99 28

NE-Id 10

NE-Id 1

NE-Id 21

The objective of the evolution reports is to show and compare the

statistics related to a set of NEs, over a period of time.

in order to be readable, such reports shall not contain too many metrics or NEs.

Page 83: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 43

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 43

2 Define metrics properties and Analysis

Top N Report

Date RRC Cnx Estab. Fail. ratio RRC Abnormal Termination rate Total RRC cnx Request

FddCell 10 12% 2% 125

FddCell 1 8% 15% 52

FddCell 21 8% 3% 42

FddCell 5 7% 1% 78

… … …

•The objective of TOP N reports is to filter the N worst (or best)

NEs according to a specific criterion.

•Such reports are run over the set of NEs and for a single date.

Page 84: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 44

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 44

2 Define metrics properties and Analysis

Alarm Detection Report

The following applied at PrOptima tool. Alarms are set by the users to be automatically triggered when some values of the metrics are either below or beyond a fixed threshold.

Report can be automatically exported on alarm (xml, html, ascii, file, mail).

Once alarms have been generated, they can be displayed by means of PrOptima.

When the counter value is higher than the selected condition on the Alarm Description, this value is highlighted in the report in different colors.

Page 85: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 45

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 45

2 Define metrics properties and Analysis

Key Performance Indicators

� Measure the performance of the complete network !

� Example: indicator Call Drop Rate.

Weekly CDR “UMTS"

0,00%

0,50%

1,00%

1,50%

2,00%

2,50%

3,00%

3,50%

1 5 9 13 17 21 25 29 33 37 41 45week number

CD

R

weekly call drop rate

contractual call drop rate

quality CDR

Measure the performance of the complete network

� Analyzed according their trend and values

� Usually every day (week, month)

� Compared with:

� Competitor results if available

� Contractual requirements

� Internal quality requirements

The Call Drop rate at network level has to be compared to:

� Contractual threshold: can be requested by the operator management to the operational radio

team, can be requested by the operator to the provider on swap or network installation

� Quality threshold: fixed internally by radio team management.

� Quality thresholds are usually more tight than contractual ones.

Page 86: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 46

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 46

2 Define metrics properties and Analysis

Network Key Performance Indicators

TRAINING EXERCISE: KPI OR NOT

INDICATOR DESCRIPTION KPI ?

average of call setup success rate for the network Yes

No

call drop rate in your capital

call drop rate of the cell covering a specific buidling

call success of 1 PLMN

% of cells being congested today

rate of call lost due to radio problem on cell CI=14, LAC=234

% of user in Soft HO for the network

average rate of paging discarded for all the RNCs

% of Cell_DCH and cell_FACH transition in hot spot zone

Page 87: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 47

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 47

2 Define metrics properties and Analysis

Counter based KPIs

Network Accessibility

NetworkRetainability

NetworkQuality

NetworkTraffic

NetworkCongestion

Counter based KPIs

Capacity/

Load

Call ProfileHSxPA

RRM

NetworkMobility

Will be developed in next chapters

Page 88: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 48

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 48

2 Define metrics properties and Analysis

Methodological precautions

METHODOLOGICAL PRECAUTIONS

� Avoid typical errors regarding indicators interpretation

Page 89: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 49

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 49

A good value for a KPI indicator

⇓⇓⇓⇓All network components are OK regarding this indicator

Example

� A global call drop rate of 1%

� Can hide some cells with 10 % of call drop rate

2 Define metrics properties and Analysis

KPI value

Page 90: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 50

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 50

2 Define metrics properties and Analysis

Network Element aggregation

� THE AVERAGE VALUE OF AN INDICATOR FOR A NETWORK

� IS NOT THE AVERAGE OF CELL RESULTS (or any sub-part of it)

� BUT THE AVERAGE WEIGHTED BY THE TRAFFIC

number of calls number of call drop call drop ratecell 1 390 8 2,10%cell 2 546 29 5,25%cell 3 637 20 3,10%cell 4 1029 12 1,14%cell 5 536 3 0,50%cell 6 2 1 50,00%cell 7 3 1 33,00%cell 8 210 4 2,11%cell 9 432 5 1,20%cell 10 321 4 1,11%

average of cell results 9,95%total nb of drop/total number of calls 2,10%

Page 91: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 51

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 51

2 Define metrics properties and Analysis

With other indicators

Total Call Drop Rate

0,0%

10,0%

20,0%

30,0%

40,0%

50,0%

60,0%

70,0%

25-05-

2005

26-05-

2005

27-05-

2005

28-05-

2005

29-05-

2005

30-05-

2005

31-05-

2005

01-06-

2005

02-06-

2005

03-06-

2005

04-06-

2005

05-06-

2005

06-06-

2005

07-06-

2005

% CS call drop

% PS call drop

Percentage of calls dropped due to RL failure

0,0%

10,0%

20,0%

30,0%

40,0%

50,0%

60,0%

70,0%

25-05-

2005

26-05-

2005

27-05-

2005

28-05-

2005

29-05-

2005

30-05-

2005

31-05-

2005

01-06-

2005

02-06-

2005

03-06-

2005

04-06-

2005

05-06-

2005

06-06-

2005

07-06-

2005

% CS call drop

% PS call drop

Page 92: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 52

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 52

2 Define metrics properties and Analysis

With alarms

10

20

30

40

50

60

70

80

90

0,5

11,5

2

2,5

3

3,54

4,5

5

PRACH fail

PRACH succ

% PRACH fail

PRACH reception in Cell

?

Page 93: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 53

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 53

2 Define metrics properties and Analysis

With parameters modification

� QoS degradation after parameter change

93%

94%

95%

96%

97%

98%

99%

100%

06/3

0/20

05

07/0

2/20

05

07/0

4/20

05

07/0

6/20

05

07/0

8/20

05

07/1

0/20

05

07/1

2/20

05

07/1

4/20

05

07/1

6/20

050

10000

20000

30000

40000

50000

60000

AMR calls % CSSR

Reference New set

Page 94: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 54

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 54

3 Alcatel-Lucent Call Trace Solution Overview

Page 95: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 55

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 55

3 Alcatel-Lucent Call Trace Solution Overview

Introduction

� Call Trace is a very powerful feature that allows the collection of very detailed information on:

� One or more mobiles

� One or more cells

� Network Interfaces

� Other network elements and internal procedures

Call Trace can be seen as a probe embedded inside the RNC and therefore is not limited to the data that can be collected by network probes monitoring the accessible external network interfaces (Iub, Iur, Iu-CS, Iu-PS,…)

Page 96: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 56

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 56

Call TraceApplicability

3 Alcatel-Lucent Call Trace Solution Overview

Call Trace Applicability

Detailed troubleshooting• Reduced need for external probes• Over the air message flows• Over the air message content• Internal network messaging on all external interfaces• Internal Network events• Error message analysis

Remote Optimization• Avoid Unecessary & Costly Drive Tests• Scrambling Code Analysis• Detailed Handover Statistics• Neighbouring List Tunning• RF Coverage Control • RF Coverage Improvement

Network Validation & IOT• Inter-operability testing with mobile vendors• Inter-operability with Core Network• NW Acceptance and New Services indroductionAdvanced Optimization

• Detailed Performance monitoring• Quality of Service Evaluation• Detailed Parameter Optimisation (Power Control, BLER targets, ...)• New features introduction• Dropped Call and Access Failures root cause analysis

Detailed KPIs• Possibility to Merge Call Trace data with Drive Tests logs• Detailed per RNC, Cell & Service Statistics

Page 97: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 57

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 57

3 Alcatel-Lucent Call Trace Solution Overview

Call Trace Session Types (1/4)

� Core Network Invoked Call Trace - CTa� To trace one or several UE calls selected by the Core Network - UE call is traced in a RNS if a RANAP CN_INVOKE_TRACE message is received on a SCCP connection dedicated to the UE on Iu interface

� To trace UE emergency calls - If a RRC connection request received in the RNC with the cause “Emergency Call” will be traced by the RNC as a CTa session, without waiting the Core Network trigger

� Access Invoked Call Trace – CTb� To trace the dedicated data for calls based on a predefined UE identity (specified at the OMC-R when creating a CTb session). The UE identity may be one of the following:

�TMSI

�P-TMSI

� IMSI

� IMEI

Call Trace Solution comprises several types of traces:

Page 98: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 58

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 58

3 Alcatel-Lucent Call Trace Solution Overview

Call Trace Session Types (2/4)

� Geographic Call Trace – CTg

� To trace the dedicated for calls established within a geographical area in the UTRAN (may be a cell, a set of cells or all the cells in the RNS)

� From UA05 calls to be traced can be filtered based on the RRC Establishment Cause (i.e., user can for instance decide to trace only the mobile originated calls with RRC Establishment Cause “OriginatedBackground Call”)

� From UA06 (POI) the calls to be traced can be filtered on a part of the IMEI can be given (the remaining will be wild cards). This will allow concentrating the traces on a certain kind of UEs which can be useful for troubleshooting purposes when a certain UE model is known to be introducing problems in the network.

Page 99: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 59

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 59

3 Alcatel-Lucent Call Trace Solution Overview

Call Trace Session Types (3/4)

� Object Trace on the cell object – OTCell

� To trace data related to a cell or several cells (i.e. NBAP common)

� As example, this trace session is useful to obtain detailed cell level measurements on:

� Transmitted Carrier Power

� UL RSSI

� Neighbouring Call Trace – CTn (from UA05)

� To trace mobility specific events:

� SRNC relocation

� Incoming and outgoing HHO to 2G network

� Radio link setup / addition, deletion

� HO failed (with failure cause)

� Relocation failed (with failure cause)

� HSDPA mobility

� Change of Primary Cell

� Detected cells (missing neighbours)

� …

Page 100: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 60

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 60

3 Alcatel-Lucent Call Trace Solution Overview

Call Trace Session Types (4/4)

� Object Trace on IuCs object – OTIuCs

� To trace common Iu CS data (i.e. not linked to a given call) - RANAP messages on Iu Cs interface.

� Object Trace on IuPs object – OTIuPs

� To trace common Iu PS data (i.e. not linked to a given call) - RANAP messages on Iu Ps interface.

� Object Trace on IuR object – OTIuR (from UA05)

� To trace common Iur data (i.e. not linked to a given call) - RNSAP messages on Iur interface.

� Object Trace on IuBC object – OTIuBC (from UA05)

� To trace common (i.e. not linked to a given call) SABP messages on IuBCinterface.

Page 101: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 61

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 61

Creation mode

ParametersSession

Cell, Geographical Sessions

Access Session

3 Alcatel-Lucent Call Trace Solution Overview

Configuring a Call Trace Session

Data Collected in the Trace Sessions

The data provided by the Network Elements is organized into different traced

Functions and Sub-Functions.

Each traced Function / Sub-Function provides information on a particular

aspect of the Call processing:

� As example, the trace sub-function named “RRC dedicated traffic” covers

the RRC signalling messages exchanged between the UE and the network in

dedicated mode.

NE collected records are presented according to three different “Trace

modes”

� Mode 1 - “Event only” (contains the traced function and sub-function, the

event name, a time-stamp, the related cell Id, the related RNC Id)

� Mode 2 - “ASN.1” (contains a header and the full record information, coded

in ASN.1 - applies only to UTRAN protocols PDUs)

� Mode 3 - “Ctx_full” (provides a specific set of additional data associated to

the event)

To ease Call Trace configuration the traceable Function / Sub-Functions and

associated Trace Modes are organised in predefined “Session Templates”

(user configurable). The user does not need to specify exhaustibly the

required information every time a session is created.

Page 102: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 62

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 62

Call Trace Management and Data Flows

3 Alcatel-Lucent Call Trace Solution Overview

Call Trace Data Management

PrOptima ClientOMC GUI

Main Server Performance Server

WQA

OMC-R is responsible for the management of the Call Trace application in the RNC

Call Trace data is collected and stored in files by the RNC according to the configured filters (session templates)

When a file becomes available for upload from the RNC the Main Server is notified through a dedicated event by the RNC.

The Main Server sends Trace file availability events to the Performance Server.

The Performance Server ADI uploads Call trace files from RNC and purges the call trace data files from the RNC.

The ADI decodes received files, mediates Call trace files, and converts them to XML format.

NIMS-PrOptima™ or WQA (for CTn in UA05) are used as Post-Processing tools.

Page 103: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 63

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 63

3 Alcatel-Lucent Call Trace Solution Overview

Post Processing Call Trace Data (1/2)

� It provides:� Data Importation and Storage

� Trace Record Decoding

� Data Filtering depending on parameters

� UMTS Call Re-assembly and Storage

� Call Indexing mechanism based on call parameters (Session type, Session id, UE type and value, Domain, Traffic class, etc.)

� Call Event Analysis module which contains the Call Record player (Call Trace Navigator).

� Performance Management Statistics module which allows to examine several call trace and object trace files and to generate customized reports.

� Detailed Protocol Analysis

NIMS PrOptima Call Trace Module is the standard too l to Post-Process Call Trace data (except CTn)

Page 104: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 64

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 64

WQA (Cell 1 - Cell 2)

0 ,00 %

0 ,50 %

1 ,00 %

1 ,50 %

2 ,00 %

2 ,50 %

3 ,00 %

3 ,50 %

-3 5 -2 5 -1 5 -5 5 1 5 2 5 35 45 55

C/I (dB)

perc

enta

ge to

tal

inte

rfer

ence

0 ,0 0%

1 0,00 %

2 0,00 %

3 0,00 %

4 0,00 %

5 0,00 %

6 0,00 %

7 0,00 %

8 0,00 %

9 0,00 %1 00,0 0%

cum

ulat

ive

dist

ribu

tion

Matrices Computation

CTnW-NMS

UTRAN

WirelessProvisioning

System(a.k.a. WPS)

ParametersChangesfor NetworkTuning

Upload of CTnTraces for analysis

OptimizationCycle

3 Alcatel-Lucent Call Trace Solution Overview

Post Processing Call Trace Data (2/2)

� WQA is a Tool introduced to post-process CTn log files.

CTn Session Type and WQA – Wireless Quality Analyser (UA05)

� Provides recommendations:

�Adjacencies to be added/removed

�Modification can be fed into WPS and then applied on the Network

� Several Reports (matrices) are available:

�Per Neighbouring Relation & Per HO type (Soft/Softer, HSxPA, InterFreq, 2G<->3G)

�Includes HO failure analysis

�Analysis of Ping Pong HO

A CTn Call Trace session only logs the events associated to (SHO/HHO)mobility and is fully dedicated to the neighboring tuning activities.

Updated neighbouring lists (inter/intra frequencies, inter-system) are crucial to deliver the desired end2end user QoS:

� Neighbouring tuning can represent 80% of optimisation activity

WQA is a Tool introduced to post-process CTn log files.

Several Reports (matrices) are available:

� Per Neighbouring Relation & Per HO type (Soft/Softer, HSxPA, InterFreq, 2G<->3G)

� Includes HO failure analysis

� Analysis of Ping Pong HO

Provides recommendations:

� Cells to be added in the neighbouring list

� Cells to be removed from the neighbouring list

� Modification can be fed into WPS and then applied on the Network

Page 105: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 65

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 65

Self-Assessment on the Objectives

� Please be reminded to fill in the formSelf-Assessment on the Objectivesfor this module

� The form can be found in the first partof this course documentation

Page 106: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 2 � Page 66

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitor the Radio Network Performance Section 2 � Page 66

End of Module

Page 107: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 1

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

Do not delete this graphic elements in here:

All Rights Reserved © Alcatel-Lucent 2007

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

3 3FL12921AAAAWBZZA Edition 1

Section 3Monitoring &

Troubleshooting methods

Page 108: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 2

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 2

Blank Page

This page is left blank intentionally

Second editionEL ABED, Achrafe2007-10-2002

First editionEL ABED, Achrafe2007-08-2401

RemarksAuthorDateEdition

Document History

Page 109: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 3

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 3

Objectives

� To be able to explain what is the QoS monitoring and troubleshooting process

� To be able to identify the performance reports

Page 110: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 4

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 4

Objectives [cont.]

This page is left blank intentionally

Page 111: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 5

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 5

Table of Contents

Switch to notes view!Page

1 Monitoring and troubleshooting process 7Monitoring & Troubleshooting Methods 8Criteria Definition(1/3) 9Criteria Definition (2/3) 10Criteria Definition (3/3) 11Observation 12Analysis 13Correction 14Validation 15

2 Define Performance Reports 16High level reports 17Troubleshooting reports 18RNC panel 19Cell panel 20Recommendations 21Recommendations 22Self-Assessment on the Objectives 23End of Module 24

Page 112: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 6

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 6

Table of Contents [cont.]

Switch to notes view!

This page is left blank intentionally

Page 113: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 7

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 7

1 Monitoring and troubleshooting process

Page 114: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 8

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 8

1 Monitoring and troubleshooting process

Monitoring & Troubleshooting Methods

The basic method for monitoring is based on a detection method

Data RetrieveDefinition

Criteria Definition

Observation

Analysis

Correction

Validation

• Hourly / Busy Hour, Daily, Weekly

• Alarm detection

• NEs (RNC, FddCell , SGSN, …)

Engineering

O&M

O&M

Mon

itorin

g P

roce

ss

• Counters

• Metrics

• Reports

• Alarms

!

Tool implementation: PrOptima, NPO, Optima, etcPost-processing solution: Report, Graph, implementation. Automatization

Mon

itorin

g S

etup

Implementation

The basic method for monitoring is based on a detection method :

A problem or a need of improvement will be detected when, part of the network doesn’t fit the «required performances»:

- Performances not in accordance with the operator’s needs or expectations.

- Difference of performances with the rest of the network

- Sudden degradation of performances

Performances could be defined as rates of operations completion or usage of the resources.

Page 115: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 9

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 9

1 Monitoring and troubleshooting process

Criteria Definition(1/3)

� From top to bottom approach:� Metrics & reports are selected going from a high level (executive reports) to

a deeper level (detailed reports)

� Monitor the distribution of a set of KPIs of the different network elements for the different resources at network level. Spatial view/Time view

� Then a threshold/alarm for troubleshooting is set to focus on the worst cases under these thresholds: 10th percentile

RNC panels

Executive panels

Metrics and reports will be selected, going from a high level with the executive reports to a deeper level with the detailed reports. This is a strategy from the top to the bottom. The format of the reports will be graph or table.

Page 116: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 10

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 10

1 Monitoring and troubleshooting process

Criteria Definition (2/3)

� Bottom up approach:� According to one metric, Network Elements are ordered (Metric view)

� Analysis is done on most problematic Network Elements

Top N worst cells

Troubleshooting panels & charts

Page 117: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 11

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 11

1 Monitoring and troubleshooting process

Criteria Definition (3/3)

� The granularity for reporting must be also selected in terms of time (hourly, daily, weekly…)

� The output of this step is coming with a set of deliverable reports to use for monitoring activities:� Weekly Performance Monitoring reports based mainly on RNC Panel

� Daily Performance Monitoring reports based on worst cell lists

� Investigation reports based on troubleshooting metrics.

Page 118: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 12

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 12

1 Monitoring and troubleshooting process

Observation

� Observation has to be achieved on a daily basis

�Results must be compared every day

� Monitoring has to be executed according to top to bottom approach

� Customer complaints

Observation

Analysis

Correction

Validation

O&M

O&M

Mon

itori

ng P

roce

ss

!

To quickly react to any degradation of the quality of service and keep the satisfaction of the

subscribers, it is really important to detect any trouble as soon as it occurs.

For this purpose, observation has to be achieved on a daily basis.

In order to have a relevant monitoring, the results must be compared every day. The behavior of

a network appears generally different depending on the time of the day, the day of the week or

of the month. So, to make sure that the picture of the network is complete, data shall be taken

every day.

Data have to be reliable. It means that enough data are cumulated before taking assumptions on

the network behavior, so, a serious background of network pictures is required (depending on

the traffic, one month data could be needed to be sure of the network behavior and

performances).

Monitoring has to be executed first at a global level, then at a RNC levels and then at the

fddcell level with help of the top N and the alarm reports.

Customer complaints, network daily tracking (that contains any network configuration change –software, hardware, parameter changes…) and network stability status can help to find and

solve any bad performances of the network.

Figures have to be captured also at the times the network is the most demanded: data for busy

hour are needed every day.

Page 119: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 13

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 13

1 Monitoring and troubleshooting process

Analysis

� The aim of KPIs analysis is to:� Detect possible network problems

� Shape global network view

� If first analysis is not enough or some hypothesis have to be confirmed

further investigation are necessary:

� System check

� Verify operation and maintenance reporting.

� Iub, Iu, Iur Interface traces and mobile traces

Observation

Analysis

Correction

Validation

O&M

O&M

Mon

itori

ng P

roce

ss

!

To analyze a problem, many data are available. They have to be correlated together and also

with the network configuration.

The aim of this task is to detect the different problems, analyzing and correlating with the rest of

statistics to have a global network view at the same time that problems are detected and

different steps can be followed in order to fix them.

If a first analysis is not enough or some hypothesis have to be confirmed further investigation

are necessary:

- System check

- Verify operation and maintenance reporting.

- Iub Iu Iur Interface traces and mobile traces

Page 120: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 14

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 14

1 Monitoring and troubleshooting process

Correction

Observation

Analysis

Correction

Validation

O&M

O&M

Mon

itori

ng P

roce

ss

!

Radio Fine Tuning :

Radio parameters values setting

(Power, CAC, iRM, AO… )

Design Fine Tuning :

Antenna system configuration

(Height, Azimuth, Tilt … )

After Analysis solutions could be proposed

After analysis, some solutions are proposed. A report describing the problem, its analysis and

the corrective actions has to be written, to keep a trace in the network history and helping in

the new issues.

A solution can be a parameters fine tuning for a process and/or in a part of the network. New

setting of the parameters can be loaded

To correct radio problems, actions on the radio designed are proposed: tilting antennas,

modifying the output power, parameter changes...

Modifying the network configuration may be necessary.

Page 121: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 15

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 15

1 Monitoring and troubleshooting process

Validation

� Validation occurs after corrective action implementation:� Monitoring must show that the problem has

disappeared

� Monitoring has to confirm that the other parts of the network have not been degraded by the correction action: no side effects

Observation

Analysis

Correction

Validation

O&M

O&M

Mon

itori

ng P

roce

ss

!

It must be observed during several days

When the corrective action has been implemented, it has to be validated.

Monitoring must show that the problem has disappeared, on a long term period (one week). No

more alarms, or absence of the top 30, or evolution in a good trend.

Monitoring has to confirm that the other parts of the network have not been degraded by the

correction action: no side effects. It must be observed during several days.

Page 122: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 16

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 16

2 Define Performance Reports

Page 123: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 17

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 17

2 Define Performance Reports

High level reports

Report Type Observation

PeriodGranularities Comment

Executive panel Weekly Evolution One Month Network/per weekThe objective of this report is to give an overview of the

network’s performances over several weeks

Executive panel Daily Evolution One Week Network / per dayThe objective of this report is to get an overview of the

network’s behaviour during the last week

RNC panel Weekly Evolution One Month per RNC / per weekThe objective of this report is to give an overview of the RNC’s

performances over several weeks

RNC panel Daily Evolution One Week per RNC / per day

The objective of this report is to have a global view (RNC level).

It will lead to more detailed investigation in case of issues in

some of its metrics

Cell panel Daily evolution One Week per FddCell/ one day

Valid to monitor a cluster of fddcell or Node Bs performance, to

support the monitoring when activating new features in a

limited area or cluster of cells

Warning: In case of Multi-Layer, some metric can only make

sense at Node B level.

It's necessary to have statistic meaningful attempts or traffic to

assess the performance per cell otherwise degradations of the

metrics can be linked to the lack of traffic

These reports are used in “from Top to Bottom appro ach”

This report, named RNC Panel gives a global view of the network. It highlights roughly the main results in terms of accesibility, mobility achievement, traffic indicators, etc

The metrics are associated to the main phases of a call:

- RRC connections set-up

- IU SCCP connections set-up

- Radio Access Bearers establishment

- Call Drops

- Mobility efficiency

- Congestion detection

- Quality

- Traffic

This report has to be used at RNC level.

It reflects the quality of actual network, and it will Lead to deeper investigations with additional metrics: the

troubleshooting investigations.

Page 124: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 18

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 18

2 Define Performance Reports

Troubleshooting reports

These reports are used for specific investigations

Report Type Observation

PeriodGranularities Criteria (Top N/other) Comment

RRC Daily evolution one week per RNC/ Day

The objective of this report is to have a global view (RNC level)

of RRC connections over a one-week period. The results of this

report could be compared with the results processed at FddCell

level (report below).

RRC Top N one day per FddCell/ one day

Use the daily evolution of

the executive report and

select the date for which

the “RRC Connection

Establishment Failure rate”

is the worst.

The objective of this report is to identify the FddCells that

would have potential RRC connections establishment issues.

RRC Daily evolution one week per FddCell / day

Use the N FddCells that

were filtered by the

previous TOP N report.

The objective of this report is to verify that the potential RRC

connections establishment issues identified by the TOP N report

were real (and need deeper investigations) or not.

Iu SCCP Daily evolution one week per RNC/ DayThe objective of this report is to focus on SCCP connections and

identify potential issues.

Iu SCCP Hourly evolution one day per RNC/ hour

Use the date for which the

“Iu CS SCCP Failure rate” or

“Iu CS SCCP Failure rate” is

the worst in the previous

report.

The objective of this report is to check whether the bad SCCP

connection statistics are related to specific periods of time or

not in order to correlate later with alarms or even tracking

RAB Management Daily evolution one week per RNC/ Day

The RAB Assignment Analysis aims at determining at RNC level:

the service degradation and the reasons (congestion reasons or

other)

Radio Bearer Daily evolution one week per RNC/ Day

This report helps to know it the traffic radio bearer is ok

attempted each time the RNC tries to allocate traffic resources

to a UE to perform a voice and/or data call, etc.

Radio Bearer Top N one week per RNC/ Dayfddcells “Radio Bearer

Success rate” is worst

This report helps to identify the fddcell to monitor with the

following report

Radio Bearer Daily evolution one week per FddCell / day

This report help to know it the traffic radio bearer is ok

attempted each time the RNC tries to allocate traffic resources

to a UE to perform a voice and/or data call, etc for an specific

fddcee

Radio Bearer Blocking Top N one week per FddCell Top Blocking rate fddcells Track of most Blocked cells

fddcell

Page 125: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 19

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 19

2 Define Performance Reports

RNC panel

� RNC Panel gives a global view of the network� It reflects the quality of actual network� it will Lead to deeper investigations with additional metrics: the

troubleshooting investigations.

Example: FamilyNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

Accessibility RNC 50_CSSR005_R%Cs Call Setup Success Rate%Cs%50_CSSR005_R

Accessibility RNC 50_CSSR005_R%Ps Call Setup Success Rate%Ps%50_CSSR005_R

Accessibility RNC 50_IuSCCP006_R%Cs IuSCCP Success Rate%Cs%50_IuSCCP006_R

Accessibility RNC 50_IuSCCP006_R%Ps IuSCCP Success Rate%Ps%50_IuSCCP006_R

Accessibility RNC 50_RAB011_R%CsSpeech RAB Establishment Success Rate per Requested RAB%CsSpeech%50_RAB011_R

Accessibility RNC 50_RAB011_R%CsVideo RAB Establishment Success Rate per Requested RAB%CsVideo%50_RAB011_R

Accessibility RNC 50_RAB011_R%Ps RAB Establishment Success Rate per Requested RAB%Ps%50_RAB011_R

Accessibility RNC 50_RAB022_R%CsVideo RAB Assignment Success per Granted RAB type%CsVideo%50_RAB022_R

Accessibility RNC 50_RAB022_R%CsVoice RAB Assignment Success per Granted RAB type%CsVoice%50_RAB022_R

Accessibility RNC 50_RAB022_R%HSDPA RAB Assignment Success per Granted RAB type%HSDPA%50_RAB022_R

Accessibility RNC 50_RAB022_R%Ps RAB Assignment Success per Granted RAB type%Ps%50_RAB022_R

Accessibility RNC 50_RRC003_CR%Cs RRC Connection Success Rate%Cs%50_RRC003_CR

Quality RNC 50_RRA008_R UL Upsize Attempts%50_RRA008_R

Retainability RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

Retainability RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

Retainability RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Retainability RNC 50_IU019_R%CsVideo Number of Drops per Minute of Calls%CsVideo%50_IU019_R

Retainability RNC 50_IU019_R%CsVoice Number of Drops per Minute of Calls%CsVoice%50_IU019_R

Retainability RNC 50_IU019_R%HSDPA Number of Drops per Minute of Calls%HSDPA%50_IU019_R

Retainability RNC 50_IU019_R%Ps Number of Drops per Minute of Calls%Ps%50_IU019_R

Traffic RNC 50_RAB012_R%CsVideo Average Number of RAB Established%CsVideo%50_RAB012_R

Traffic RNC 50_RAB012_R%CsVoice Average Number of RAB Established%CsVoice%50_RAB012_R

Page 126: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 20

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 20

2 Define Performance Reports

Cell panel

� Useful in case of new feature activation in a group of cells and correlate

problems with cell performance.

� Also to build Top N worst cells according to certain parameters.Family Type

Network

Element5.0_Metric id or counter id 5.0_Metric name

Accessibility counter Fddcell 639 VS.CallEstablishmentDuration - Conversational

Accessibility counter Fddcell 639 VS.CallEstablishmentDuration - Streaming

Accessibility counter Fddcell 639 VS.CallEstablishmentDuration - Interactive

Accessibility counter Fddcell 639 VS.CallEstablishmentDuration - Background

Accessibility metric Fddcell 50_RB002_C Radio Bearer Setup Success Rate%50_RB002_C

Accessibility metric Fddcell 50_RB011_C%CsSpeech Radio Bearer Setup Success%CsSpeech%50_RB011_C

Accessibility metric Fddcell 50_RB011_C%CsVideo Radio Bearer Setup Success%CsVideo%50_RB011_C

Accessibility metric Fddcell 50_RB011_C%Ps Radio Bearer Setup Success%Ps%50_RB011_C

Accessibility metric Fddcell 50_RRC001_CR RRC Connection Success%50_RRC001_CR

Accessibility metric Fddcell 50_RRC001_CR%Cs RRC Connection Success%Cs%50_RRC001_CR

Accessibility metric Fddcell 50_RRC001_CR%Ps RRC Connection Success%Ps%50_RRC001_CR

Accessibility metric Fddcell 50_RRC002_CR RRC Connection Requests%50_RRC002_CR

Accessibility metric Fddcell 50_RRC002_CR%Cs RRC Connection Requests%Cs%50_RRC002_CR

Accessibility metric Fddcell 50_RRC002_CR%Ps RRC Connection Requests%Ps%50_RRC002_CR

Congestion metric Fddcell 50_RL037_CR Radio Link Addition Blocking Rate%50_RL037_CR

Congestion metric Fddcell 50_RRC008_CR RRC Connection Reject Rate System%50_RRC008_CR

Mobility metric Fddcell 50_HO3G2G001_C%Cs 3G2G HHO Execution Attempts%Cs%50_HO3G2G001_C

Mobility metric Fddcell 50_HO3G2G002_C%Ps 3G2G HHO Execution Failure Rate on 2G%Ps%50_HO3G2G002_C

Mobility metric Fddcell 50_HO3G2G003_C%Cs 3G2G HHO CS Detection radio%Cs%50_HO3G2G003_C

Mobility metric Fddcell 50_HO3G2G003_C%Ps 3G2G HHO PS Detection radio%Ps%50_HO3G2G003_C

Mobility metric Fddcell 50_HO3G2G019_C%Cs 3G2G HHO radio Success Rate%Cs%50_HO3G2G019_C

Mobility metric Fddcell 50_HO3G2G020_C%Cs 3G2G HHO Execution Success Rate%Cs%50_HO3G2G020_C

Mobility metric Fddcell 50_SHO007_CR SHO Failure Rate%50_SHO007_CR

Quality metric Fcell&RNC 50_RB015_CR Radio Bearer Reconfiguration Success Rate%50_RB015_CR

Quality metric Fddcell 50_RL030_CR Radio Link Reconfiguration Preparation Attempt%50_RL030_CR

Quality metric Fddcell 50_RL032_CR Radio Link Reconfig Prepare Success Rate%50_RL032_CR

Quality metric Fddcell 50_RL038_CR Radio Link Reconfiguration Blocking Rate%50_RL038_CR

Retainability metric Fddcell 50_IU006_C%Cs Call Drop Rate%Cs%50_IU006_C

Retainability metric Fddcell 50_IU006_C%Ps Call Drop Rate%Ps%50_IU006_C

Retainability metric Fddcell 50_IU008_C%CsVideo Iu Abnormal Release Request%CsVideo%50_IU008_C

Retainability metric Fddcell 50_IU008_C%CsVoice Iu Abnormal Release Request%CsVoice%50_IU008_C

Example:

Page 127: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 21

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 21

2 Define Performance Reports

Recommendations

� Once reports have been generated and scheduled it can be necessary a

postprocessing based on the use of excel macros to display the

information in a friendly way. Also it exist the possibility to use the

PrOptima module: NIMS Web Portal. RRC Success (CS/PS)

80%

82%

84%

86%

88%

90%

92%

94%

96%

98%

100%

Week05 Week06 Week07 Week08 Week0 9 Week10 Week11 Week12 Week13 Week14 Week15 Week16 Week17 Week18 Week19 Week20 Week21 Week2 2 Week23 Week24 Week25

Pe

rcen

tage

0

50000

100000

150000

200000

250000

Vol

ume

VO_42_RRC002_Fcell&RNC_CS%RRC Connection Requests

VO_42_RRC002_Fcell&RNC_PS%RRC Connection Requests

VO_42_RRC003_Fcell&RNC_CS%RRC Connection Success Rate

VO_42_RRC003_Fcell&RNC_PS%RRC Connection Success Rate

In order to validate the trend of a metric in a period of time in a specific network it’s recommended to calculate the standard error. With this value it would be possible to discriminate if average values are representative of the metric trend or specific investigation must be done and it will lead to troubleshooting investigations.

Page 128: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 22

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 22

2 Define Performance Reports

Recommendations

� To validate a metric trend its recommended to calculate the standard error

� If the standard error is very low: the average value is really a trend

� If the standard error is very high: the trend is not stable (Stability issues,

parameters changes, Network element failures …)

� It is necessary to distinguish between two type of KPIs

� Success KPI: Low values represent bad performance (Percentile should be

low values:10th perc, 20th perc)

� Failure KPI. High values represent bad performance (Percentile should be a

high value: 80th perc, 90th perc)

If the standard error is very low we can conclude that the average value is really a trend (even if the average value is low, the trend cause can be due to configuration, network release trend, mobile release). If the standard error it is very high then, it means that the trend was not stable we could conclude that there were issues in the network (stability, parameters changes, problems occurring in the networks element, issues related to network and mobile release that appear in the network, etc).

Page 129: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 23

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 23

Self-Assessment on the Objectives

� Please be reminded to fill in the formSelf-Assessment on the Objectivesfor this module

� The form can be found in the first partof this course documentation

Page 130: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 3 � Page 24

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Monitoring & Troubleshooting methods Section 3 �Page 24

End of Module

Page 131: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 1

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

Do not delete this graphic elements in here:

All Rights Reserved © Alcatel-Lucent 2007

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

4 3FL12921AAAAWBZZA Edition 1

Section 4Network Accessibility

Monitoring & Troubleshooting

Page 132: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 2

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 2

Blank Page

This page is left blank intentionally

Second editionEL ABED, Achrafe2007-10-2002

First editionEL ABED, Achrafe2007-08-2401

RemarksAuthorDateEdition

Document History

Page 133: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 3

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 3

Objectives

� At the end of this module you will be able to :

� Describe the accessibility metric family

� Illustrate the call flows associated with the metric family

� Identify counters and locate them in the call flow procedure

� Define metrics and recognize its key counters

� Analyze each metric

Page 134: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 4

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 4

Objectives [cont.]

This page is left blank intentionally

Page 135: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 5

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 5

Table of Contents

Switch to notes view!Page

1 Accessibility analysis 7KPIs Families Reminder 8Accessibility Flow Diagrams 9Accessibility issues causes 10

2 RRC Connection Phase 11RRC Connection 12RRC Connection Success: Flow 13RRC Connection Success: counters 14RRC Connection Preparation Failure 15RRC Connection Execution Failure 16RRC Connection : Counter Tree 17RRC Connection Success Rate 18

3 RRC Troubleshooting 19RRC Accessibility analysis 20RRC Accessibility analysis 21RRC Accessibility analysis 22RRC Failure Cause Analysis 23RRC Failure Cause Analysis 24RRC Connection / RF Conditions Analysis 25RRC Connection / RF Conditions Analysis 26RRC Connection / RF Conditions Analysis 27RRC Connection / RRM Capacity Analysis 28Corrective actions (1/2) 29Corrective actions (2/2) 30Case Analysis 31Case Analysis (1/3): Burst of RRC failures in an area of few cells 32Case Analysis (2/3): Burst of RRC failures in an area of few cells 33Case Analysis (3/3): Burst of RRC failures in an area of few cells 34RRC Burst of failures (summary) 35RRC connection Troubleshooting panels: First Radio link 36RRC connection Troubleshooting panels: Others 37RRC connection Troubleshooting panels: Others 38RAB Assignment Flow: Exercise 39RAB Assignment Success: Counters 40RAB Assignment Preparation Failure 41RAB Assignment Execution Failure 42RAB Assignment: RNC Counter Tree 43RB Establishment: Cell Counter Tree 44RAB Assignment Success Rate (RNC level) 45RB To Be Setup Success Rate (Cell level) 46RAB Analysis 47RAB Analysis: Failure analysis 48Corrective actions 49Corrective actions 50Corrective actions 51Exercise: Success Rates Initiated by the RNC 52Exercise (cont’d): Success Rates Initiated by the RNC 53SCCP Connection: Success Flow 54SCCP Connection: Failure Flow 55SCCP Connection : Counter Tree 56Iu SCCP Analysis (success rates initiated by the RNC) 57SCCP connection panels 58Iu SCCP analysis method 59

5 IuSCCP Troubleshooting AnalysisCase Study 60Example (1/2): IuSCCP analysis 61

Page 136: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 6

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 6

Table of Contents [cont.]

Switch to notes view!Page

Example (2/2): IuSCCP analysis 62Example (2/2): IuSCCP analysis 63Security Mode Success: Flow 64Security Mode Failure: RNC 65Security Mode Failure: UE 66Security Mode Command Success Ratio 67Ciphering analysis 68Ciphering analysis 69Exercise 70Exercise 71Call Set Up Success Rate 72Accessibility Troubleshooting Chart 73

7 Call Setup Success Rate Troubleshooting AnalysisCase Study 74

Case Study : Accessibility Monitoring & Troubleshooting 75Case Study : Accessibility Monitoring & Troubleshooting 76Self-Assessment on the Objectives 77End of Module 78

Page 137: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 7

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 7

1 Accessibility analysis

Page 138: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 8

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 8

1 Accessibility analysis

KPIs Families Reminder

Network Accessibility

NetworkRetainability

NetworkQuality

NetworkTraffic

NetworkCongestion

Counter based KPIs

Capacity/

Load

Call ProfileHSxPA

RRM

NetworkMobility

5.0_Report (PMG) Family TypeNetwork

Element5.0_Metric id or counter id 5.0_Metric name

RNC panel Accessibility metric RNC 50_CSSR005_R%Cs Call Setup Success Rate%Cs%50_CSSR005_R

RNC panel Accessibility metric RNC 50_CSSR005_R%Ps Call Setup Success Rate%Ps%50_CSSR005_R

RNC panel Accessibility metric RNC 50_IuSCCP006_R%Cs IuSCCP Success Rate%Cs%50_IuSCCP006_R

RNC panel Accessibility metric RNC 50_IuSCCP006_R%Ps IuSCCP Success Rate%Ps%50_IuSCCP006_R

RNC panel Accessibility metric RNC 50_RAB011_R%CsSpeech RAB Establishment Success Rate per Requested RAB%CsSpeech%50_RAB011_R

RNC panel Accessibility metric RNC 50_RAB011_R%CsVideo RAB Establishment Success Rate per Requested RAB%CsVideo%50_RAB011_R

RNC panel Accessibility metric RNC 50_RAB011_R%Ps RAB Establishment Success Rate per Requested RAB%Ps%50_RAB011_R

RNC panel Accessibility metric RNC 50_RAB022_R%CsVideo RAB Assignment Success per Granted RAB type%CsVideo%50_RAB022_R

RNC panel Accessibility metric RNC 50_RAB022_R%CsVoice RAB Assignment Success per Granted RAB type%CsVoice%50_RAB022_R

RNC panel Accessibility metric RNC 50_RAB022_R%HSDPA RAB Assignment Success per Granted RAB type%HSDPA%50_RAB022_R

RNC panel Accessibility metric RNC 50_RAB022_R%Ps RAB Assignment Success per Granted RAB type%Ps%50_RAB022_R

RNC panel Accessibility metric RNC 50_RRC003_CR%Cs RRC Connection Success Rate%Cs%50_RRC003_CR

RNC panel Accessibility metric RNC 50_RRC003_CR%Ps RRC Connection Success Rate%Ps%50_RRC003_CR

RNC panel Accessibility metric RNC 50_RRC013_CR%Cs First RRC Connection Success Rate%Cs%50_RRC013_CR

RNC panel Accessibility metric RNC 50_RRC013_CR%Ps First RRC Connection Success Rate%Ps%50_RRC013_CR

RNC panel Accessibility metric RNC 50_RRC015_CR%Cs First RRC Connection Request%Cs%50_RRC015_CR

RNC panel Accessibility metric RNC 50_RRC015_CR%Ps First RRC Connection Request%Ps%50_RRC015_CR

RNC panel Accessibility metric RNC 50_SMC001_R%Cs Security Mode Command%Cs%50_SMC001_R

RNC panel Accessibility metric RNC 50_SMC001_R%Ps Security Mode Command%Ps%50_SMC001_R

RNC panel Accessibility metric RNC 50_SMC002_R%Cs Security Mode Command Success Rate%Cs%50_SMC002_R

RNC panel Accessibility metric RNC 50_SMC002_R%Ps Security Mode Command Success Rate%Ps%50_SMC002_R

Accessibility monitoring - RNC panel

Page 139: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 9

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 9

1 Accessibility analysis

Accessibility Flow Diagrams

UERRC Connection Request

RRC Connection Complete

RRC Connection Setup

Radio Link Setup Request

Radio Link Setup Response

Measurement Control

Init Direct Transfer

RNCNode B CN

SCCP connection confirm

SCCP connection req.

Security mode command

Security mode complete

Security mode command

Security mode completeCommon id

RAB assignment req.

Radio Bearer Setup

Radio Bearer Setup Complete RAB assignment resp.

S.R.L.R. Procedure

RR

C c

onne

ctio

nS

CC

Pco

nn.

Sec

urity

mod

eR

AB

esta

blsh

t

S.R.L.R. : Synchronized Radio Link Reconfiguration

Page 140: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 10

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 10

1 Accessibility analysis

Accessibility issues causes

Degradation of Accessibility KPIs

Radio problems

Capacity

HW problemsSW problems

✁❁❚❅❒✟▼❃❙◆❉

❐✟▲❄❒✁❆✟ ❊▲❄❆✁✟ ❏❋❇❑❈

Investigation methods

in next chapters

Metrics and reports will be selected, going from a high level with the executive reports to a deeper level with the detailed reports. This is a strategy from the top to the bottom. The format of the reports will be graph or table.

The granularity for reporting must be also selected in terms of time (hourly, daily, weekly…) and the network elements for each reports.

The output of this step is coming with a set of deliverable reports to use for monitoring activities.

The following shows an example of deliverable reports for a network on the UTRAN side:

- Weekly Performance Monitoring reports based mainly on RNC Panel

- Daily Performance Monitoring reports based on worst cell lists

- Investigation reports based on troubleshooting metrics.

Page 141: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 11

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 11

2 RRC Connection Phase

Page 142: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 12

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 12

2 RRC Connection Phase

RRC Connection

�Logical connection between UE and UTRAN.

�It carries control plane information between UE and UTRAN.

�Each UE can have only one RRC connection at any time with the UTRAN.

Core Network

Circuit Domain

Packet Domain

UE Node B RNC

Physical channel AAL2 bearer SIG/AAL5

RRC (logical channel)

RR

C c

onne

ctio

n

� RRC connection is a logical connection between UE and UTRAN. It carries control plane

information between UE and UTRAN.

� Before anything can be done in UMTS, the RRC connection must be established.

� RRC Connection is one of functions of RRC Layer (Layer 3). All messages sent over this

connection are part of the RRC protocol.

� The establishment of an RRC connection includes cell reselection, admission control and

layer2 signaling link establishment.

� Each UE can have only one RRC connection at any time with the UTRAN. It is used by the

UTRAN to track both the location and state of the user during the life of a call or packet data

session.

� The release of an RRC connection can be triggered by request from upper layer or by the RRC

layer itself in case of connection failure.

Page 143: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 13

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 13

2 RRC Connection Phase

RRC Connection Success: Flow

RRC Connection Phase

CCCH / FACH / SCCPCH

CCCH / RACH / PRACH

DCCH / DCH / DPDCH+DPCCH

UE RNCNode B

RRC Connection Request

RRC Connection Complete

RRC Connection Setup

Radio Link Setup Request

Radio Link Setup Response

Measurement Control

Init Direct Transfer

RR

C c

onne

ctio

n

� This scenario is applied in case of RRC connection establishment in cell_DCH state

Page 144: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 14

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 14

2 RRC Connection Phase

RRC Connection Success: counters

#409RRC Connection Request#419First RRC Connection

Request

#403RRC Connection Success

#416RRC Connection Setup

FDDCell counters

UE RNCNode B

RRC Connection Request

RRC Connection Complete

RRC Connection Setup

Radio Link Setup Request

Radio Link Setup Response

Measurement Control

Init Direct Transfer

RR

C c

onne

ctio

n

RRC.AttConnEstab #409 : This measurement provides the number of RRC connection requests screened by establishment cause.

Screening (below): see RRC connection establishment causes:

0 --> Originating Conversational call 1 ---> Originating Streaming call

2 --> Originating Interactive call 3 ---> Originating Background call

4 --> Originating Subscribed Traffic call (PS call) 5 ---> Terminating Conversational call

6 --> Terminating Streaming call 7 ---> Terminating Interactive call

8 --> Terminating Background call 9 ---> Emergency call

10 ---> Intersystem cell re-selection (2G to 3G cell-reselection for CS and PS performed by mobile on its own in idlemode ; used for Location Area Update/Routing Area Update NAS transactions )

11 ---> Intersystem cell change order (2G to 3G handover for PS when triggered by BSS, using a Cell Change Order command: Network Controlled Cell Reselection Mode 2: used to open the RRC connection in order to resume data transfer)

12 --> Registration 13 --> Detach

14 --> Originating High priority signaling 15 --> Originating Low priority signaling

16 --> Call re-establishment 17 --> Terminating High priority signaling

18 --> Terminating Low priority signaling 19 --> Terminating: Cause unknown

20-31 --> Spare causes (not used: provisioned for future use) as defined in TS25.331

VS.FirstRrcConnectionRequest #419 : while #0409 counter counts all requests and thus repetition, the #0419 counts only the first one and provides more accurate measures.

RRC.SuccConnEstab #403 : This measurement provides the number of successful RRC connection establishments screened by establishment cause.

VS.RrcConnectionSetup #416 : This measurement provides the number of RRC Connection Setup messages sent to the UE in response of an RRC Connection Request. Only the initial Setup message and the first repetition at T351 expiry are counted. Quick repetition are not counted.

Screened by cause for sending the RRC Connection Setup.

0 : Initial RRC Cnx Setup without quick repeat

1 : Initial RRC Cnx Setup with quick repeat

2 : first repetition of RRC Cnx Setup without quick repeat

3 : first repetition of RRC Cnx Setup with quick repeat

Note about UE RRC connection request: if this request does not reach the RNC it is impossible to measure it.

Page 145: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 15

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 15

2 RRC Connection Phase

RRC Connection Preparation Failure

FDDCell counter

CAC failureOrRNC Overload

#404 RRC Connection Reject[all screenings except 0]

UE RNCNode B

RRC Connection Request

RRC Connection Reject (wait time)

With Redirection to GSM if:• MO Conversational or Emergency call• a blind 2G neighbor cell is declared

RR

C c

onne

ctio

n

RRC.FailConnEstab #404: This measurement provides the number of RRC connection establishment failures screened by establishment failure cause.

Screening:

• Sub-Counter #0 : timeout• Sub-Counter #1 : unavailable dl code resources• Sub-Counter #2 : unavailable dl power resources• Sub-Counter #3 : Unspecified• Sub-Counter #4 : RSSI• Sub-Counter #5 : Cell Fach Unspecified CAC• Sub-Counter #6 : Overload• Sub-Counter #7 : 3G to 2G Redirection for Emergency Calls• Sub-Counter #8 : RRC context CAC, pegged when CAC fails for the current RRC connectionrequest.• Sub-Counter #9 : Unavailable RRC context resource, pegged when the number of RRCcontexts is exhausted• Sub-Counter #10 : Unavailable FACH context resource, pegged when the number of FACHcontexts in RNC_CALL is exhausted.• Sub-Counter #11 : No answer from the NodeB• Sub-Counter #12 : Lack of C-RNTI• Sub-Counter #13 : UE Ec/No lower than qQualityMin

Page 146: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 16

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 16

2 RRC Connection Phase

RRC Connection Execution Failure

CAC success

#404 RRC Connection Failure[screening 0]

UE RNCNode B

RRC Connection Request

RRC Connection Setup

FDDCell counter

T352 expiry

RR

C c

onne

ctio

n

RRC.FailConnEstab #404: This measurement provides the number of RRC connection establishment failures screened by establishment failure cause.

Screening:

• Sub-Counter #0 : timeout• Sub-Counter #1 : unavailable dl code resources• Sub-Counter #2 : unavailable dl power resources• Sub-Counter #3 : Unspecified• Sub-Counter #4 : RSSI• Sub-Counter #5 : Cell Fach Unspecified CAC• Sub-Counter #6 : Overload• Sub-Counter #7 : 3G to 2G Redirection for Emergency Calls• Sub-Counter #8 : RRC context CAC, pegged when CAC fails for the current RRC connectionrequest.• Sub-Counter #9 : Unavailable RRC context resource, pegged when the number of RRCcontexts is exhausted• Sub-Counter #10 : Unavailable FACH context resource, pegged when the number of FACHcontexts in RNC_CALL is exhausted.• Sub-Counter #11 : No answer from the NodeB• Sub-Counter #12 : Lack of C-RNTI• Sub-Counter #13 : UE Ec/No lower than qQualityMin

Page 147: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 17

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 17

2 RRC Connection Phase

RRC Connection : Counter Tree

Request#409 and #419

Preparation failure#404 [all screenings except 0]

Setup#416

Execution failure#404 [0]

Success#403

RRC.FailConnEstab

RRC.FailConnEstab

RRC.AttConnEstabVS.FirstRrcConnectionRequest

VS.RrcConnectionSetup

RRC.SuccConnEstab

FDDCell counters

RR

C c

onne

ctio

n

� Reference: UTRAN traffic management UMT/SYS/DD0031 – 03.02/EN

Page 148: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 18

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 18

2 RRC Connection Phase

RRC Connection Success Rate

FDDCell metrics

#409.[0,1,2,3,4,5,6,7,8,9,14,16,17,19]

#403.[0,1,2,3,4,5,6,7,8,9,14,16,17,19] RRC connection success rate

(calls only)=

System view

User View

RRC003[calls]

RR

C c

onne

ctio

n

#419.[0,1,2,3,4,5,6,7,8,9,14,16,17,19]

#403.[0,1,2,3,4,5,6,7,8,9,14,16,17,19] RRC connection success rate

(calls only)=

RRC013[calls]

�RRC Connection success rate can be monitored at FDD Cell level.

�It is proposed to select the RRC causes which are taken by the calls:

� Screening from 0 to 9: Originating / Terminating Traffic Classes and Emergency call

� Screening 14, Originating High Priority Signaling:

� 3GPP: this screening is used for Supplementary Services in CS, and to Modify/Deactivate a PDP Context in PS

� Alcatel-Lucent comment: Qualcomm UE systematically uses this cause to establish PS call

� Screening 16, Call re-establishment:

� 3GPP: this screening is used for CS Call re-establishment, or Routing Area Update – for the case of ‘Directed Signaling Connection Re-Establishment‘

� Alcatel-Lucent comment: it may be also used to re-establish PS call after an Always-On Step 2 downsize (always-on …)

� Screening 17, Terminating High Priority Signaling:

� Is also used to establish PS calls

� Screening 19, Terminating – cause unknown:

� 3GPP: This cause is used by the UE whenever it responds to a paging message in which the paging cause has not been set (the "paging cause" information element is an optional field of the paging message)

�The first phase of a call establishment (speech or data) is the RRC connection. One RRC connection can lead to

� Several Iu SCCP connections ( multi service CS+PS, simultaneous CS + PS attach/detach, CS location update during a PS call),

� No RAB in case of signaling connections,

� 1 (or several RAB) in case of one call (multi service).

We can also have:

CS RRC Connection success rate= (∑#403.[0,5,9]) / (∑#409.[0,5,9])

PS RRC Connection success rate=

(∑#403[1,2,3,4,6,7,8,14,16,17,19]) / (∑#409[1,2,3,4,6,7, 8,14,16,17,19])

Page 149: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 19

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 19

3 RRC Troubleshooting

Page 150: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 20

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 20

� In case of RRC failures it’s not possible to differ entiate simultaneously the failure cause and the service ca use

� Two parallel analysis are necessary to correlate fa ilure cause with the failure service cause:

�Failure cases analysis: Distribution of the failure causes screenings

�Establishment failure analysis: which RRC establish ment causes (Originating / Terminating Traffic Classes, convers ational, I / B…) failed

� Problem Detection: RRC CSR lower than 95%

3 RRC Troubleshooting

RRC Accessibility analysis

Page 151: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 21

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 21

3 RRC Troubleshooting

RRC Accessibility analysis

RRC Accessibility Analysis

RRC failure cases RRC establishment failure cases

First Radio Link Cell Inactivity

RRC failure causes

distribution deduced from

#404[screening]

RRC establishment

failure cases (per RRC request

cause)#409 - 416

[screening]

Failure estab. causes

#20[failure causes]

RRC Sleepy Cell

inactivity

#0015

RRC accessibility troubleshooting:

� RRC failure causes distribution

� RRC establishment failure cases (per rrc request cause)

� First Radio Link

� Failure Establishment cause

� Failure cause

� RRC Cell inactivity

RRC connection Troubleshooting panel (RRC establishment cause failures)

TypeNetwork

Element5.0_Metric id or counter id 5.0_Metric name

counter Fcell&RNC 409/403RRC.AttConnEstab.0 - Originating Conversational call /

RRC.SuccConnEstab.0 - Originating Conversational call

counter Fcell&RNC 409/403RRC.AttConnEstab.1 - Originating Streaming call /

RRC.SuccConnEstab.1 - Originating Streaming call

counter Fcell&RNC 409/403RRC.AttConnEstab.10 - Intersystem cell re-selection /

RRC.SuccConnEstab.10 - Intersystem cell re-selection

counter Fcell&RNC 409/403RRC.AttConnEstab.11 - Intersystem cell change order /

RRC.SuccConnEstab.11 - Intersystem cell change order

counter Fcell&RNC 409/403RRC.AttConnEstab.12 - Registration /

RRC.SuccConnEstab.12 - Registration

counter Fcell&RNC 409/403RRC.AttConnEstab.13 - Detach /

RRC.SuccConnEstab.13 - Detach

counter Fcell&RNC 409/403RRC.AttConnEstab.14 - Originating High priority signalling /

RRC.SuccConnEstab.14 - Originating High priority signalling

counter Fcell&RNC 409/403RRC.AttConnEstab.15 - Originating Low priority signalling /

RRC.SuccConnEstab.15 - Originating Low priority signalling

counter Fcell&RNC 409/403RRC.AttConnEstab.16 - Call re-establishment /

RRC.SuccConnEstab.16 - Call re-establishment

counter Fcell&RNC 409/403RRC.AttConnEstab.17 - Terminating High priority signalling /

RRC.SuccConnEstab.17 - Terminating High priority signalling

counter Fcell&RNC 409/403RRC.AttConnEstab.18 - Terminating Low priority signalling /

RRC.SuccConnEstab.18 - Terminating Low priority signalling

counter Fcell&RNC 409/403RRC.AttConnEstab.19 - Terminating : Cause unknown /

RRC.SuccConnEstab.19 - Terminating : Cause unknown

Page 152: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 22

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 22

� Issue characterization: �Can it affect certain/all services (CS, PS, etc)�Certain/all Network elements, Top N cells�Certain/all period of time, since when�Certain failure causes�After certain event (upgrade, feature activation, c onfiguration changes)

3 RRC Troubleshooting

RRC Accessibility analysis

RRC connection Troubleshooting panel (RRC establishment cause failures)

TypeNetwork

Element5.0_Metric id or counter id 5.0_Metric name

counter Fcell&RNC 409/403RRC.AttConnEstab.2 - Originating Interactive call /

RRC.SuccConnEstab.2 - Originating Interactive call

counter Fcell&RNC 409/403RRC.AttConnEstab.20 - Spare cause (not used) as defined in TS25.331 /

RRC.SuccConnEstab.20 - Spare cause (not used) as defined in TS25.331

counter Fcell&RNC 409/403RRC.AttConnEstab.3 - Originating Background call /

RRC.SuccConnEstab.3 - Originating Background call

counter Fcell&RNC 409/403RRC.AttConnEstab.4 - Originating Subscribed Traffic call /

RRC.SuccConnEstab.4 - Originating Subscribed Traffic call

counter Fcell&RNC 409/403RRC.AttConnEstab.5 - Terminating Conversational call /

RRC.SuccConnEstab.5 - Terminating Conversational call

counter Fcell&RNC 409/403RRC.AttConnEstab.6 - Terminating Streaming call /

RRC.SuccConnEstab.6 - Terminating Streaming call

counter Fcell&RNC 409/403RRC.AttConnEstab.7 - Terminating Interactive call /

RRC.SuccConnEstab.7 - Terminating Interactive call

counter Fcell&RNC 409/403RRC.AttConnEstab.8 - Terminating Background call /

RRC.SuccConnEstab.8 - Terminating Background call

counter Fcell&RNC 409/403RRC.AttConnEstab.9 - Emergency call /

RRC.SuccConnEstab.9 - Emergency call

counter Fcell&RNC 403 RRC.SuccConnEstab.10 - InterRAT

counter Fcell&RNC 409 RRC.AttConnEstab.10 - InterRAT

metric Fcell&RNC 50_RRC001_CR RRC Connection Success%50_RRC001_CR

counter Fcell&RNC 50_RRC001_CR%Calls RRC Connection Success%Calls%50_RRC001_CR

counter Fcell&RNC 50_RRC001_CR%Cs RRC Connection Success%Cs%50_RRC001_CR

counter Fcell&RNC 50_RRC001_CR%Ps RRC Connection Success%Ps%50_RRC001_CR

counter Fcell&RNC 50_RRC002_CR RRC Connection Requests%50_RRC002_CR

counter Fcell&RNC 50_RRC002_CR%Calls RRC Connection Requests%Calls%50_RRC002_CR

counter Fcell&RNC 50_RRC002_CR%Cs RRC Connection Requests%Cs%50_RRC002_CR

metric Fcell&RNC 50_RRC003_CR RRC Connection Success Rate%50_RRC003_CR

counter Fcell&RNC 50_RRC003_CR%Cs RRC Connection Success Rate%Cs%50_RRC003_CR

counter Fcell&RNC 50_RRC003_CR%InterRAT RRC Connection Success Rate%InterRAT%50_RRC003_CR

counter Fcell&RNC 50_RRC003_CR%Ps RRC Connection Success Rate%Ps%50_RRC003_CR

counter Fcell&RNC 50_RRC003_CR%Registration RRC Connection Success Rate%Registration%50_RRC003_CR

Page 153: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 23

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 23

3 RRC Troubleshooting

RRC Failure Cause Analysis

Cell InactivityFirst Radio LinkRRC establishment

failure cases

RRC Accessibility Analysis

RRC failure cases

RRC Connection success rate RNC level

RF Conditions Analysis Cell level

RRM Capacity AnalysisCell level

High nb ofUL RSSI

High nb of Failure Dl Power

Refer to the RRC Connection failures counters (#0404)

UL RF condition DL RF condition

For one/several RNC

Top N CellsRRC Connection Failure rate

Determine the worst period during the day

RRC CSRRRC003 < 95%

RF tuning of - RRC timers analysis

- Common power channel- Cell Reselection parameters

High nb of UE Ec/No lowerthan qQualityMin

High nb of No answer

from the NodeB

High nb of Failure Time out

High nb of Failure Dl Codes

RRC connection Troubleshooting panel (RRC Failure cause)

TypeNetwork

Element5.0_Metric id or counter id 5.0_Metric name

counter Fcell&RNC 404 RRC.FailConnEstab - 0 - Time out

counter Fcell&RNC 404 RRC.FailConnEstab - 1 - unavailable DL code resources

counter Fcell&RNC 404 RRC.FailConnEstab - 10- Unavailable FACH context resources.

counter Fcell&RNC 404 RRC.FailConnEstab - 11 - No answer from the NodeB

counter Fcell&RNC 404 RRC.FailConnEstab - 12 -Lack of C-RNTI

counter Fcell&RNC 404 RRC.FailConnEstab - 13 -UE Ec/No lower than qQualityMin

counter Fcell&RNC 404 RRC.FailConnEstab - 2 - unavailable DL power resources

counter Fcell&RNC 404 RRC.FailConnEstab - 3 - Unspecified

counter Fcell&RNC 404 RRC.FailConnEstab - 4 - RSSI

counter Fcell&RNC 404 RRC.FailConnEstab - 5 - Cell Fach CAC

counter Fcell&RNC 404 RRC.FailConnEstab - 6 - Overload

counter Fcell&RNC 404 RRC.FailConnEstab - 7 - 3G to 2G Redirection for Emergency Calls

counter Fcell&RNC 404 RRC.FailConnEstab - 8 - RRC context CAC. This screening is to be pegged when CAC

fails for the current RRC connection request. Not implemented

counter Fcell&RNC 404 RRC.FailConnEstab - 9 - Unavailable RRC context resource. To be pegged when the

number of RRC contexts is exhausted. Not implemented

metric Fcell&RNC 50_RRC004_CR RRC Connection Failure%50_RRC004_CR

metric Fcell&RNC 50_RRC008_CR RRC Connection Reject Rate System%50_RRC008_CR

metric Fcell&RNC 50_RRC017_CR%3G2GRedirectEmerg RRC Conn Failure Distribution%3G2GRedirectEmerg%50_RRC017_CR

metric Fcell&RNC 50_RRC017_CR%CellFACHCAC RRC Conn Failure Distribution%CellFACHCAC%50_RRC017_CR

metric Fcell&RNC 50_RRC017_CR%DLCodeResources RRC Conn Failure Distribution%DLCodeResources%50_RRC017_CR

metric Fcell&RNC 50_RRC017_CR%DLPowerResources RRC Conn Failure Distribution%DLPowerResources%50_RRC017_CR

metric Fcell&RNC 50_RRC017_CR%Overload RRC Conn Failure Distribution%Overload%50_RRC017_CR

metric Fcell&RNC 50_RRC017_CR%RRCcontextCAC RRC Conn Failure Distribution%RRCcontextCAC%50_RRC017_CR

metric Fcell&RNC 50_RRC017_CR%RSSI RRC Conn Failure Distribution%RSSI%50_RRC017_CR

metric Fcell&RNC 50_RRC017_CR%T352Expiration RRC Conn Failure Distribution%T352Expiration%50_RRC017_CR

metric Fcell&RNC 50_RRC017_CR%Unspecified RRC Conn Failure Distribution%Unspecified%50_RRC017_CR

metric Fcell&RNC 50_RRC017_CR%UnvailableFACHcontext RRC Conn Failure Distribution%UnvailableFACHcontext%50_RRC017_CR

metric Fcell&RNC 50_RRC017_CR%UnvailableRRCcontext RRC Conn Failure Distribution%UnvailableRRCcontext%50_RRC017_CR

Page 154: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 24

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 24

3 RRC Troubleshooting

RRC Failure Cause Analysis

Cell InactivityFirst Radio LinkRRC establishment failure cases

RRC Accessibility Analysis

RRC failure cases

High nb ofFailure Overload

High nb of CELL FACH CAC

Overload parametertuning. Correlation

with TMU load

High nb of3G to 2G Redirection for Emergency Calls

High nb of Unspecified

Cell stabilityanalysis

Alarm correlation/CTg Analysis

High nb of CAC

High nb of Unavailable FACH

Resources

High nb of Unavailable RRC oontext resources

Capacity Analysis

Feature 3G 2gredirection speechcalls-RRC redirect

High nb of Lack of C-RNTI

Refer to the RRC Connection failures counters (#0404)

For one/several RNC

Top N CellsRRC Connection Failure rate

Determine the worst period during the day

RRC CSRRRC003 < 95%

RRC Connection success rate RNC level

The analysis is based on the screenings of the counter RRC.FailConnEstab - #404:

• Sub-Counter #0 : timeout

• Sub-Counter #1 : unavailable dl code resources

• Sub-Counter #2 : unavailable dl power resources

• Sub-Counter #3 : Unspecified

• Sub-Counter #4 : RSSI

• Sub-Counter #5 : Cell Fach Unspecified CAC

• Sub-Counter #6 : Overload

• Sub-Counter #7 : 3G to 2G Redirection for Emergency Calls

• Sub-Counter #8 : RRC context CAC, pegged when CAC fails for the current RRC connection

request.

• Sub-Counter #9 : Unavailable RRC context resource, pegged when the number of RRC

contexts is exhausted

• Sub-Counter #10 : Unavailable FACH context resource, pegged when the number of FACH

contexts in RNC_CALL is exhausted.

• Sub-Counter #11 : No answer from the NodeB

• Sub-Counter #12 : Lack of C-RNTI

• Sub-Counter #13 : UE Ec/No lower than qQualityMin

Page 155: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 25

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 25

3 RRC Troubleshooting

RRC Connection / RF Conditions Analysis

#1001.[0,1]

∑ #1001.[0,1,2,3]

CPICH Ec/N0

RNC

CPICH

VS.IrmcacDistributionEcN0 #1043

FDDCell counter

Ec/N0 Distribution = Ec/N0 Distribution = #1043.[i]

#1043.[0,1,2,3,4]

Cell007

Helpful counters

RR

C c

onne

ctio

n

-24dB -15dB -13dB -7dB-11dB

[0] [1] [2] [3]

0dB

[4]

VS.IrmcacDistributionEcN0 - #1043

: This counter provides the distribution of Ec/N0 measurements received per range from UEswith that reference cell.

CPICH Ec/N0 are RRC measurements sent by UE to RNC.

Screening:

� Sub-Counter #0 : -24 dB <= Measurement < -15 dB

� • Sub-Counter #1 : -15 dB <= Measurement < -13 dB

� • Sub-Counter #2 : -13 dB <= Measurement < -11 dB

� • Sub-Counter #3 : -11 dB <= Measurement < -7 dB

� • Sub-Counter #4 : -7 dB <= Measurement < 0 dB

Page 156: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 26

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 26

3 RRC Troubleshooting

RRC Connection / RF Conditions Analysis

#1001.[0,1]

∑ #1001.[0,1,2,3]

CPICH RSCP

RNC

CPICH

VS.IrmcacDistributionRscp #1158

Reference FDDCell counter

-120dBm -110dBm -105dBm -80dBm-95dBm

[0] [1] [2] [3]

-25dBm

[4]

Distribution of RSCP = Distribution of RSCP = #1158.[i]

#1158.[0,1,2,3,4]

Cell008

Helpful counters

RR

C c

onne

ctio

n

VS.IrmcacDistributionRscp #1158: This counter provides the distribution of RSCP measurements received per range from UEs with that reference.

CPICH RSCP are RRC measurements sent by UE to RNC.

A set of subcounters screened on: Measurement Report power range

• Sub-Counter #0 : -120 dBm <= Measurement < -110 dBm

• Sub-Counter #1 : -110 dBm <= Measurement < -105 dBm

• Sub-Counter #2 : -105 dBm <= Measurement < -95 dBm

• Sub-Counter #3 : -95 dBm <= Measurement < -80 dBm

• Sub-Counter #4 : -80 dBm <= Measurement <= -25 dBm

Page 157: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 27

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 27

3 RRC Troubleshooting

RRC Connection / RF Conditions Analysis

UL RSSI = -112dBm + 10 Log(VS.UplinkRssi.Avg[FddCell,Time]Too high UL RSSI if > -98 dBmToo low UL RSSI if < -112 dBm

UL RSSI = -112dBm + 10 Log(VS.UplinkRssi.Avg[FddCell,Time]Too high UL RSSI if > -98 dBmToo low UL RSSI if < -112 dBm

UL RSSI

RNC

Reference FDDCell counter

VS.UplinkRssi.Avg #303

Helpful counters

RR

C c

onne

ctio

n

VS.DistRSSI #1042-97dBm -100dBm -103dBm -105dBm

[0] [1] [2] [3] [4]

VS.UplinkRssi.Avg #303: This SI counter provides the Averaged uplink RSSI per cell during a reporting period. The Averaged uplink RSSI (or UL RTWP) is updated on each reception on a NBAP common measurement.

Page 158: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 28

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 28

3 RRC Troubleshooting

RRC Connection / RRM Capacity Analysis

SF128 Code usage =SF128 Code usage =128 – #1126.[5].[Avg]

128

Sub-counter #5 => SF = 128

CS

call

case

Channelization Code shortage

SF4 SF8 SF16 SF32 SF64 SF128 SF256

[0] [1] [2] [3] [4] [5] [6]

VS.IRMTimeFreeDlCodesBySpreadingFactor #1126

FDDCell counter

Cell009

Helpful counters

RR

C c

onne

ctio

n

VS.IRMTimeFreeDlCodesBySpreadingFactor #1126: This SI counter provides the average number of free downlink channelization codes per spreading factor. It also provides the minimum and maximum value.

Screening:

� 0 ---> Spreading factor = 4

� 1 ---> Spreading factor = 8

� 2 ---> Spreading factor = 16

� 3 ---> Spreading factor = 32

� 4 ---> Spreading factor = 64

� 5 ----> Spreading factor = 128 (voice call, PS always on)

� 6 ---> Spreading factor = 256

SF128 is used for:

� Voice call at 12.2K

� Always on: DL at 8kbps

Page 159: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 29

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 29

3 RRC Troubleshooting

Corrective actions (1/2)

� After cause identification by mean of RRC accessibility troubleshooting panel &

charts

� Corrective actions according the identified cause:

Radio Issue?

Call Admision issue?Capacity/Load ssue?

Configuration issue?

•RF control (Interference study, antenna orientation & tilts, addition of sites), •Paramenter tuning: RRC timers checking, Cell selecti on/reselection parameter, Power channels adjustments,…, etc

•Admission failures are not necessarily issues, they can be explained by loaded areas. Admission failures will be investigat ed in case of significant and unexpected increase•RRM analysis, capacity analysis that can lead to pa rameter tunings or addition of resources•Overload parameter tuning, correlation with TMU loa d

•Parameter/feature audits and correlation through di fferent Network element, or different releases & parameter changes, reset node B in case of bad cell creation

Transmission issue? •Node B PCM stability, alarms, or CTg->Check Tx links

Page 160: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 30

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 30

3 RRC Troubleshooting

Corrective actions (2/2)

Mobile issue?•Burst of RRC failures) ����Traces to identify IMSI and type of mobile•After CTg analysis bad mobile behaviour is discovere d����Open a case

HW issue/BTS Cabling?

•Cause detected by means of NodeB/RNC alarms, RF an alysis or Stability analysis•Correction: Normally to check or replace certain ca rd, BTS cable, etc (see RF analysis)

SW issue?•Normally after CTg analysis/other traces analysis, a bad system behaviour is discovered ���� Open case and attach the traces for investigation: CTg, Iub, mobile, etc

Unknown issue?•After depth investigation non identified cause ����Open a case and attach the traces for investigation: CTg, Iub, mobile, etc

� Corrective actions according the identified cause:

Page 161: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 31

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 31

3 RRC Troubleshooting

Case Analysis

� Analyse the charts given in next slides !

� What could you say about RRC performances ?

Page 162: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 32

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 32

3 RRC Troubleshooting

Case Analysis (1/3): Burst of RRC failures in an area of few cells

PS RRC Connection Success rate per RNC

70,00%

75,00%

80,00%

85,00%

90,00%

95,00%

100,00%

105,00%

22-sept-04

23-sept-04

24-sept-04

25-sept-04

26-sept-04

27-sept-04

28-sept-04

29-sept-04

30-sept-04

1 Oct 04

2 Oct 04

3 Oct 04

4 Oct 04

5 Oct 04

6 Oct 04

7 Oct 04

8 Oct 04

9 Oct 04

10 Oct 04

GQ01

GQ02

KQ01

OQ01

OQ02

The decrease of the RRC Connection success rate, th e 5th and the 6th of October, is due to a drop of the PS RRC Connecti on success rate in the RNC OQ02.

Page 163: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 33

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 33

3 RRC Troubleshooting

Case Analysis (2/3): Burst of RRC failures in an area of few cells

PS RRC Connection Success rate in the RNC OQ02

100,00%100,00%

80,95%

96,97%100,00%

64,98%57,74%

51,09%

100,00%

44,55%48,35%51,29%

100,00%95,70%97,12%100,90%99,43%100,00%100,00%

0

50

100

150

200

250

300

5/1

0/04, 00

:00

5/1

0/04, 01

:00

5/1

0/04, 02

:00

5/1

0/04, 03

:00

5/1

0/04, 04

:00

5/1

0/04, 05

:00

5/1

0/04, 06

:00

5/1

0/04, 07

:00

5/1

0/04, 08

:00

5/1

0/04, 09

:00

5/1

0/04, 10

:00

5/1

0/04, 11

:00

5/1

0/04, 12

:00

5/1

0/04, 13

:00

5/1

0/04, 14

:00

5/1

0/04, 15

:00

5/1

0/04, 16

:00

5/1

0/04, 17

:00

5/1

0/04, 18

:00

5/1

0/04, 19

:00

5/1

0/04, 20

:00

5/1

0/04, 21

:00

5/1

0/04, 22

:00

5/1

0/04, 23

:00

0,00%

20,00%

40,00%

60,00%

80,00%

100,00%

120,00%

PS RRC

Connection

attempts

PS RRC

Connection

success rate

The PS RRC Connection success rate falls from 10:00 am to 13:00 pm and from 14:00 pm to 17:00 pm, when the number of a ttempts is the highest. This phenomenon occurs during the 5th and 6th of October

Page 164: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 34

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 34

PS RRC Connection Failures RNC OQ02 Vs (N889/U1 & N 889/U2)

0

50

100

150

200

250

6/10/04, 00:00

6/10/04, 01:00

6/10/04, 02:00

6/10/04, 03:00

6/10/04, 04:00

6/10/04, 05:00

6/10/04, 06:00

6/10/04, 07:00

6/10/04, 08:00

6/10/04, 09:00

6/10/04, 10:00

6/10/04, 11:00

6/10/04, 12:00

6/10/04, 13:00

6/10/04, 14:00

6/10/04, 15:00

6/10/04, 16:00

6/10/04, 17:00

6/10/04, 18:00

6/10/04, 19:00

6/10/04, 20:00

6/10/04, 21:00

6/10/04, 22:00

6/10/04, 23:00PS RRC Connection

failures in the RNC

OQ02

PS RRC Connection

failures in the N889/U1

& N889/U2

3 RRC Troubleshooting

Case Analysis (3/3): Burst of RRC failures in an area of few cells

Investigations at cell level indicate that main of the PS RRC Connection Failure during these two periods are concentrating two cells: N889/U1 and N889/U3.Based on the RL Setup phase, most of these requests in those two cells are in fact request for Signaling (Attach, Registration, …) instead of Background, Interactive or Streaming. Complementary study could be to take traces on Iub interface/CT of the N889 site in order to identify the call flow and the type of mobile

Page 165: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 35

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 35

3 RRC Troubleshooting

RRC Burst of failures (summary)

� Problem description

� Burst of PS Failures in RRC.FailConnEstab.2 counter.

� Consider the following counter related to Originating Interactive Call:

� RRC.FailConnEstab.2 = RRC.AttConnEstab.2 – RRC.SuccConnEstab.2

� The cell is almost randomly every time, so this suggests a UE issue.

� Sometimes this problem cause a lot of failures (>100 in a 15 minutes period) on the cells X, but also is present, with

less percentage, in the neighbours of cell X.

� Detection

� Activate an alarm with quarter of hour granularity:

� RRC.Fail.2 + RRC.Fail.14 > 100 [FddCell, Quarter of Hour]=> ALARM!

� Investigation

� Once time the alarm appears on the Alarm Monitoring, the following is a needed:

� Activate an OTCell Trace in the cell identified by the alarm (1 hour)

� Possibility also to activate Iub trace in this cell to find the IMSI

� Process the OTCell Trace in order to find the PTMSI of the mobile causing the problem (assuming that it’s due only to one mobile)

� Associate the PTMSI found with the IMSI, using the two files collected

Page 166: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 36

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 36

3 RRC Troubleshooting

RRC connection Troubleshooting panels: First Radio link

RRC Connection Request

RRC Connection CompleteRRC Connection Setup

Radio Link Setup RequestRadio Link Setup Response RRC Connection Phase

UE Node B RNC

TypeNetwork

Element5.0_Metric id or counter id5.0_Metric name

counter Fcell&RNC 20 VS.RadioLinkFirstSetupFailure

metric Fcell&RNC 27 VS.RadioLinkFirstSetupRequest

counter Fcell&RNC 27-all scr VS.RadioLinkFirstSetupRequest-AsConf/Rab/Traffic Class rework.

metric Fcell&RNC 50_RL026_CR Radio Link First Setup Success Rate%50_RL026_CR

counter Fcell&RNC 20 VS.RadioLinkFirstSetupFailure.RadioLinkSetupFailure

counter Fcell&RNC 20 VS.RadioLinkFirstSetupFailure.TimeoutNbap

counter Fcell&RNC 20 VS.RadioLinkFirstSetupFailure.RrmRefusal

counter Fcell&RNC 20 VS.RadioLinkFirstSetupFailure.unused

counter Fcell&RNC 20 VS.RadioLinkFirstSetupFailure.LackOfNodeBDlProcessingResources

counter Fcell&RNC 20 VS.RadioLinkFirstSetupFailure.LackOfNodeBUlProcessingResources

counter Fcell&RNC 20 VS.RadioLinkFirstSetupFailure.LackCidIub

counter Fcell&RNC 20 VS.RadioLinkFirstSetupFailure.LackBwthIub

counter Fcell&RNC 20 VS.RadioLinkFirstSetupFailure.INodeRefusal

counter Fcell&RNC 18 VS.RadioLinkFailureIndication

Page 167: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 37

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 37

3 RRC Troubleshooting

RRC connection Troubleshooting panels: Others

Connection

termination

Cell inactivity

Cell inactivity

� Top N cells high VS.RrcSleepy Cell inactivity (#0015)

� If VS.RLSleepy Cell inactivity (#0016) is ok� Bad

creation of cell common channels

� If VS.RLSleepy Cell inactivity (#0016) is also high�

Check cell configuration, and alarms, hardware

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

counter FDDCELL 15 VS.RrcSleepyCellInactivity

counter FDDCELL 16 VS.RlSleepyCellInactivity

counter FDDCELL 17 VS.PagingSleepyCellInactivity

counter Fcell&RNC 405 VS.RrcConnectionRelease.NormalEvent

counter Fcell&RNC 405 VS.RrcConnectionRelease.UnspecifiedSccpReleaseCause

counter Fcell&RNC 405 VS.RrcConnectionRelease.PreemptiveRelease

counter Fcell&RNC 405 VS.RrcConnectionRelease.Congestion

counter Fcell&RNC 405 VS.RrcConnectionRelease.ReestablishmentReject

counter Fcell&RNC 405 VS.RrcConnectionRelease.UserInactivity

counter Fcell&RNC 0405-6 VS.RrcConnectionRelease.DirectedSignallingConnectionReestablishement

metric FDDCELL 50_RRC006_C RRC Connection abnormal termination Rate%50_RRC006_C

metric RNC 50_RRC006_R RRC Connection abnormal termination Rate%50_RRC006_R

metric FDDCELL 50_RRC007_C RRC Connection Release%50_RRC007_C

metric RNC 50_RRC007_R RRC Connection Release%50_RRC007_R

Page 168: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 38

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 38

4 RAB Establishment and Troubleshooting

Analysis

Divider Section Break Pages

• Title block set 28/32pt Trebuchet white, flush left with text box positioned at,

Horizontal 1.87” and Vertical 2.87”

• This slide is to be used to create Section Divider slides

• Please copy, paste and modify this slide to reflect your specific needs. It is not

generated from a Master slide template

Page 169: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 39

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 39

4 RAB Establishment and Troubleshooting Analysis

RAB Assignment Flow: Exercise

� In which family of counters (number range?) will you find the counters related to the RAB assignment? See previous section ☺

� Find the counters shown below on the message flow relating to RAB assignment.

UE RNCNode B CN

RAB assignment req.

Radio Bearer Setup

Radio Bearer Setup Complete

RAB assignment resp.

S.R.L.R. Procedure

RA

Bes

tabl

sht

Internal RRM decision to

assign resources

#?

#?

#?

� Help/reference:

� UMTS access counter list

� UTRAN key performance metric definitions

Page 170: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 40

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 40

4 RAB Establishment and Troubleshooting Analysis

RAB Assignment Success: Counters

UE RNCNode B CN

RAB assignment req.

Radio Bearer Setup

Radio Bearer Setup Complete

RAB assignment resp.

S.R.L.R. Procedure

RA

Bes

tabl

sht

#671 Rab Establish. Requests Per RabType

RNC counter

Reference FDDCell counter

#691 RB to be setup

CAC success

#672 RAB assignment success per Requested RAB type#673 RAB assignment success per Granted RAB type

RNC counters

#687 RB setup success

VS.RabEstablishmentRequestsPerRabType #671: Number of RAB Establishments Requests per RAB type. This measurement provides the number of RAB establishment attempts.

Screening: by requested RAB Type (DlRbSetId, UlRbSetId, Traffic Class) see table COMB UL

DL RBSET in appendix.

VS.RabEstablishmentSuccessPerRequestedRabType #672: Number of successful RAB establishments per Requested RAB type. This measurement provides the number of successful Radio Access Bearer establishments per RAB type as requested by the Core Network (even if the actual RAB type Granted by the UTRAN is different than the RAB type that was requested by the CN).

Screening: per requested RAB type (requested should be understood to be after RAB matching).

VS.RabEstablishmentSuccessPerGrantedRabType #673: Number of successful RAB establishments per Granted RAB type. This measurement provides the number of successful RAB establishment per RAB type as granted by the UTRAN.

Screening: per granted RAB type (granted should be understood to be after iRM Table matching).

VS.RadioBearerSetupRequest #691: Number of Radio-Bearer establishments to be performed following a valid RAB assignment request received from the CN. This measurement provides the number of RB to be setup before CAC is carried out.

Screening: per DlAsConfId

VS.RadioBearerSetupSuccess #687: Number of successful Radio-Bearer establishments. This measurement provides the number of successful RB setup.

Screening: per DlAsConfId

Page 171: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 41

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 41

#631 RB establishmentunsuccess

4 RAB Establishment and Troubleshooting Analysis

RAB Assignment Preparation Failure

RAB assignment request

RAB assignment response (RAB can not be established)

Invalid RAB parametersor

CAC failure

Reference FDDCell counter

#677 RAB assignment setup unsuccess

RNC counter

RA

B e

stab

lsht

UE RNCNode B CN

RAB assignment req.

VS.RadioBearerEstablishmentUnsuccess #631: Number of rejected Radio-Bearer Establishments. This measurement provides the number of RB establishment refusals before any sending of RRC RADIO BEARER SETUP. It mainly corresponds to CAC failure cases.

Screening:

� 0 : invalid RAB parameters value.

� 1 : Unavailable OVSF code

� 2 : Unavailable power

� 3 : Unspecified (including NBAP failure, Drop during RAB establishment procedure)

� 5 : unused

� 6 : Lack of RNC processing resources

� 7 : No Node B CEM resources available in DL (not used in this release)

� 8 : No Node B CEM resources available in UL (not used in this release)

� 9 : Lack of CID on the Iu

� 10 : Lack of bandwidth on the Iu

� 11 : Lack of CID on the Iur

� 12 : Lack of bandwidth on the Iur

� 13 : Lack of CID on the Iub

� 14 : Lack of bandwidth on the Iub

VS.RabAssignmentSetupUnsuccess #677: Number of failed RAB establishments. This measurement provides the number of unsuccessful Radio Access Bearer establishments.

Screening: by requested RAB Type (DlRbSetId, UlRbSetId, Traffic Class) see table COMB UL

DL RBSET in appendix.

Page 172: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 42

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 42

4 RAB Establishment and Troubleshooting Analysis

RAB Assignment Execution Failure

RAB assignment request

#677 RAB assignment setupunsuccess

Valid RAB parametersand

CAC success

Reference FDDCell counter

RNC counter

Radio Bearer Setup

Radio Bearer Setup Failure

#602[1] RB setup unsuccess

or No response from UE#602[0] RB setup unsuccess

#602

RAB assignment response (RAB can not be established)

S.R.L.R. Procedure

RAB assignment request

UE RNCNode B CN

RA

B e

stab

lsht

#687: Number of successful Radio-bearer establishments per cell. This measurement provides the number of successful radio bearer establishment procedures, for each cell controlled by the RNC which is the reference cell. Screening: DlAsConf Id

#602: Number of failed Radio-bearer Establishments per cell. This measurement provides the number of RB establishment procedures failures, screened by establishment failure cause, for each cell controlled by the RNC which is the primary cell.During such a procedure, the measurement attached to a given cell is incremented if the cell is in the primary cell of the active set of the involved UE. Screening:

� #0 ---> Time-out expired without reception of a RADIO BEARER SETUP COMPLETE message or a RADIO BEARER SETUP FAILURE message.

� #1 ---> Reception of a RRC RADIO BEARER SETUP FAILURE message

#631: Number of refused Radio-bearer Establishments per cell. This measurement provides the number of RB establishment refusals before any sending of RRC RADIO BEARER SETUP, screened by establishment refusal cause, for each cell controlled by the RNC which is the reference cell. Screening:

� #0 --> Invalid RB parameter value #1 --> Unavailable downlink code resources

� #2 --> Unavailable downlink power resources #3 --> Unspecified

#672: Number of successful RAB establishments. This measurement provides the number of successful Radio Access Bearer establishments per requested RAB type. This measurement provides the number of successful RAB establishment, screened per requested RAB type (requested should be understood to be after RAB matching). Screening:

� #0 --> Traffic Class 0, i.e. Conversational #1 --> Traffic Class 1, i.e. Streaming

� #2 --> Traffic Class 2, i.e. Interactive #3 --> Traffic Class 3, i.e. Background

#677: Number of failed RAB establishments. This measurement provides the nb of unsuccessful Radio Access Bearer establishments, screened by traffic class. Screening: same as #604.

#671: Number of RAB Establishments Requests per RAB type. This measurement provides the number of RAB establishment attempts. Screening: by requested RAB Type (Traffic Class, UL bitrate, DL bitrate).

#0672: Number of RAB establishments success per requested RAB type. This measurement provides the number of successful RAB establishment, screened per requested RAB type (requested should be understood to be after RAB matching).

Page 173: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 43

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 43

4 RAB Establishment and Troubleshooting Analysis

RAB Assignment: RNC Counter Tree

Request#671

Failure#677

Success#672#673

VS.RabAssignmentSetupUnsuccess

VS.RabEstablishmentRequestsPerRabType

RNC counters

VS.RabEstablishmentSuccessPerRequestedRabTypeVS.RabEstablishmentSuccessPerGrantedRabType

RA

B e

stab

lsht

RAB monitoring panel

TypeNetwork

Element5.0_Metric id or counter id 5.0_Metric name

metric RNC 50_RAB004_R%Ps128 RB PS Maintained iRM CAC%Ps128%50_RAB004_R

metric RNC 50_RAB004_R%Ps256 RB PS Maintained iRM CAC%Ps256%50_RAB004_R

metric RNC 50_RAB004_R%Ps384 RB PS Maintained iRM CAC%Ps384%50_RAB004_R

metric RNC 50_RAB004_R%Ps64 RB PS Maintained iRM CAC%Ps64%50_RAB004_R

metric RNC 50_RAB004_R RB PS Maintained iRM CAC%50_RAB004_R

metric RNC 50_RAB005_R RB PS Downgraded iRM CAC%50_RAB005_R

metric RNC 50_RAB005_R%Ps128 RB PS Downgraded iRM CAC%Ps128%50_RAB005_R

metric RNC 50_RAB005_R%Ps256 RB PS Downgraded iRM CAC%Ps256%50_RAB005_R

metric RNC 50_RAB005_R%Ps384 RB PS Downgraded iRM CAC%Ps384%50_RAB005_R

metric RNC 50_RAB005_R%Ps64 RB PS Downgraded iRM CAC%Ps64%50_RAB005_R

metric RNC 50_RAB006_R RB PS Rejected iRM CAC%50_RAB006_R

metric RNC 50_RAB006_R%Ps128 RB PS Rejected iRM CAC%Ps128%50_RAB006_R

metric RNC 50_RAB006_R%Ps256 RB PS Rejected iRM CAC%Ps256%50_RAB006_R

metric RNC 50_RAB006_R%Ps384 RB PS Rejected iRM CAC%Ps384%50_RAB006_R

metric RNC 50_RAB006_R%Ps64 RB PS Rejected iRM CAC%Ps64%50_RAB006_R

metric RNC 50_RAB011_R RAB Establishment Success Rate per Requested RAB%50_RAB011_R

metric RNC 50_RAB011_R%Cs RAB Establishment Success Rate per Requested RAB%Cs%50_RAB011_R

metric RNC 50_RAB011_R%CsSpeech RAB Establishment Success Rate per Requested RAB%CsSpeech%50_RAB011_R

metric RNC 50_RAB011_R%CsVideo RAB Establishment Success Rate per Requested RAB%CsVideo%50_RAB011_R

metric RNC 50_RAB011_R%Ps RAB Establishment Success Rate per Requested RAB%Ps%50_RAB011_R

metric RNC 50_RAB013_R RAB Establishment Requests per RAB type%50_RAB013_R

metric RNC 50_RAB013_R%CsVideo RAB Establishment Requests per RAB type%CsVideo%50_RAB013_R

metric RNC 50_RAB013_R%CsVoice RAB Establishment Requests per RAB type%CsVoice%50_RAB013_R

metric RNC 50_RAB013_R%Ps RAB Establishment Requests per RAB type%Ps%50_RAB013_R

metric RNC 50_RAB014_R RAB Normal Release per Granted RAB Ratio%50_RAB014_R

metric RNC 50_RAB014_R%HSDPA RAB Normal Release per Granted RAB Ratio%HSDPA%50_RAB014_R

metric RNC 50_RAB018_R RB Maintained by iRM CAC Rate%50_RAB018_R

metric RNC 50_RAB019_R RB Downgraded by iRM CAC Rate%50_RAB019_R

metric RNC 50_RAB020_R RB Rejected by iRM CAC Rate%50_RAB020_R

metric RNC 50_RAB022_R RAB Assignment Success per Granted RAB type%50_RAB022_R

metric RNC 50_RAB022_R%Cs RAB Assignment Success per Granted RAB type%Cs%50_RAB022_R

metric RNC 50_RAB022_R%CsVideo RAB Assignment Success per Granted RAB type%CsVideo%50_RAB022_R

metric RNC 50_RAB022_R%CsVoice RAB Assignment Success per Granted RAB type%CsVoice%50_RAB022_R

metric RNC 50_RAB022_R%HSDPA RAB Assignment Success per Granted RAB type%HSDPA%50_RAB022_R

metric RNC 50_RAB022_R%Ps RAB Assignment Success per Granted RAB type%Ps%50_RAB022_R

Page 174: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 44

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 44

4 RAB Establishment and Troubleshooting Analysis

RB Establishment: Cell Counter Tree

Request#691

Preparation Failure#631

Attempt#687 + #602

Execution failure#602

Success#687

VS.RadioBearerEstablishmentUnsuccess

VS.RadioBearerSetupUnsuccess

VS.RadioBearerSetupRequest

VS.RadioBearerSetupSuccess

Reference FDDCell counters

Invalid RAB params#631[0]

CAC failures#631[1-14]

RB setup failure from UE#602[1]

No answer from UE#602[0] R

AB

est

abls

ht

Radio Bearer blocking panel

TypeNetwork

Element

5.0_Metric id or

counter id5.0_Metric name

metric Fddcell 50_RB009_C Radio Bearer Establishment Unsuccess RNC Rejection%50_RB009_C

metric RNC 50_RB009_R Radio Bearer Establishment Unsuccess RNC Rejection%50_RB009_R

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.InvalidRabParametersValue

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.UnavailableDlCodeResources

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackBwthIu

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackCidIur

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackBwthIur

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackCidIub

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackBwthIub

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.UnavailableDlPowerResources

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.Unspecified

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackOfRncProcessingResources

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackOfNodeBDlProcessingResources

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackOfNodeBUlProcessingResources

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackCidIu

metric Fddcell 50_RB014_C RB Blocking Rate%50_RB014_C

metric RNC 50_RB014_R RB Blocking Rate%50_RB014_R

Page 175: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 45

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 45

4 RAB Establishment and Troubleshooting Analysis

RAB Assignment Success Rate (RNC level)

RNC metrics

Voice RAB Assignment success rate = #672.[1] / #671.[1]Voice RAB Assignment success rate = #672.[1] / #671.[1]

Video RAB Assignment success rate = #672.[2] / #671.[2]Video RAB Assignment success rate = #672.[2] / #671.[2]

PS RAB Assignment success rate = #672.[0,5-42] / #671.[0,5-42]PS RAB Assignment success rate = #672.[0,5-42] / #671.[0,5-42]

RA

B e

stab

lsht

RB007

Radio Bearer panel. Establishment cause

TypeNetwork

Element

5.0_Metric id or

counter id5.0_Metric name

metric Fddcell 50_RB009_C Radio Bearer Establishment Unsuccess RNC Rejection%50_RB009_C

metric RNC 50_RB009_R Radio Bearer Establishment Unsuccess RNC Rejection%50_RB009_R

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.InvalidRabParametersValue

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.UnavailableDlCodeResources

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackBwthIu

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackCidIur

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackBwthIur

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackCidIub

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackBwthIub

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.UnavailableDlPowerResources

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.Unspecified

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackOfRncProcessingResources

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackOfNodeBDlProcessingResources

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackOfNodeBUlProcessingResources

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.LackCidIu

metric Fddcell 50_RB014_C RB Blocking Rate%50_RB014_C

metric RNC 50_RB014_R RB Blocking Rate%50_RB014_R

Page 176: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 46

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 46

4 RAB Establishment and Troubleshooting Analysis

RB To Be Setup Success Rate (Cell level)

Reference FDDCell metrics

Voice RB to be setup success rateVoice RB to be setup success rate#691[same screenings]

#687.[1,5,9,10,15,16,17,18,22,26]

RB007

Video RB to be setup success rate =Video RB to be setup success rate =#691[same screenings]

#687.[0,21,29]

PS RB to be setup success rate =PS RB to be setup success rate =#691[same screenings]

#687.[2,4,6,7,9-12,15-19,21-26,28-30]

RA

B e

stab

lsht

=

Page 177: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 47

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 47

4 RAB Establishment and Troubleshooting Analysis

RAB Analysis

� Issue characterization:

� Can it affect certain/all services (CS, PS, etc)?

� Certain/all Network elements, Top N cells

� Certain/all period of time, since when

� Certain failure causes

� After certain event (upgrade, feature activation, configuration changes)

� Correlation between 2 parallel analysis

� RB failure cause analysis #0631- all failure causes

� RB failure establishment analysis, #0687 VS.RadioBearerSetupSuccess , 0689 VS.RadioBearerSetupSuccessNeighbRnc & # 0691 VS.RadioBearerSetupRequest[Target Call SetUp ] –For troubleshooting.

� RB blocking panel - it contains RB failure counters

� Radio Bearer panel - it contains RB data per service+other metrics

� Radio Link Management panel

� List of counters described in the previous slides

RA

B e

stab

lsht

Page 178: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 48

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 48

4 RAB Establishment and Troubleshooting Analysis

RAB Analysis: Failure analysis

Iub Capacity analysisNodeB Level

Refer to the distribution of

RB Establishment Unsuccess causes

RAB panel RNC level

RB panel Fddcelllevel

Establishment failure cause

RAB assignment SRRAB011 < 99%

Iur & Iu capacity analysisRNC Level

RB blocked due to Lack of

DL codesRB blocked due to Lack of

other resources

RAB assignment analysis Network level

Mean RB Blocking rateDuring BH > 2%

Determine the RNCwith lack of DL codes

PS or CS RABRejected ?

PS/CS DL codesCapacity analysis

RNC Level

RB blocked due to Lack of

DL Power

Determine the RNCwith lack of DL Power

PS or CS RABRejected ?

PS/CS DL PowerCapacity analysis

RNC Level

RB blocked due to Unspecified

reasons

Determine the RNCwith Unspecified reasons

PS or CS RABRejected ?

PS/CSHW Capacity analysis

RNC Level

Characterize the issue in TIME, SPATIAL aggregations and KPIs

RA

B e

stab

lsht

This chart will be completed with Capacity (load/congestion analysis)

RB blocking panel

5.0_Metric id

or counter id5.0_Metric name

50_RB009_C Radio Bearer Establishment Unsuccess RNC Rejection%50_RB009_C

631 VS.RadioBearerEstablishmentUnsuccess.InvalidRabParametersValue

631 VS.RadioBearerEstablishmentUnsuccess.UnavailableDlCodeResources

631 VS.RadioBearerEstablishmentUnsuccess.LackBwthIu

631 VS.RadioBearerEstablishmentUnsuccess.LackCidIur

631 VS.RadioBearerEstablishmentUnsuccess.LackBwthIur

631 VS.RadioBearerEstablishmentUnsuccess.LackCidIub

631 VS.RadioBearerEstablishmentUnsuccess.LackBwthIub

631 VS.RadioBearerEstablishmentUnsuccess.UnavailableDlPowerResources

631 VS.RadioBearerEstablishmentUnsuccess.Unspecified

631 VS.RadioBearerEstablishmentUnsuccess.LackOfRncProcessingResources

631 VS.RadioBearerEstablishmentUnsuccess.LackOfNodeBDlProcessingResources

631 VS.RadioBearerEstablishmentUnsuccess.LackOfNodeBUlProcessingResources

631 VS.RadioBearerEstablishmentUnsuccess.LackCidIu

50_RB014_C RB Blocking Rate%50_RB014_C

Page 179: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 49

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 49

4 RAB Establishment and Troubleshooting Analysis

Corrective actions

� Cause identification by mean of RAB troubleshooting panel & charts, corrective actions according the identified cause:

Radio Issue?

Call Admission issue?Capacity/Load issue?

Configuration issue?

•RF control (Interference study, antenna orientation & tilts, addition of sites), •Parameter tuning: Mobility feature tuning

•Admission failures are not necessarily issues, they can be explained by loaded areas. Admission failures will be investigat ed in case of significant and unexpected increase•RRM analysis, capacity analysis that can lead to pa rameter tunings or addition of resources•Overload parameter tuning, correlation with TMU loa d

•False congestion due to bad parameterization, Param eter/feature audits and correlation through different Network element, or d ifferent releases & parameter changes

Transmission issue? •Failure congestion due to Node B PCM stability, ala rms, or CTg->Check Txlinks

RA

B e

stab

lsht

Page 180: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 50

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 50

4 RAB Establishment and Troubleshooting Analysis

Corrective actions

� Cause identification by mean of RAB troubleshooting panel & charts, corrective actions according the identified cause:

Mobile issue?•RAB invalid parameters, Traces to identify IMSI and type of mobile (ie, mobile does not support certain RAB), After CTg analysis ba d mobile behavoiur is discovered ����Open a case

HW issue/BTS Cabling?

•Cause detected by means of NodeB/RNC alarms, RF an alysis or Stability analysis•Correction: Normally to check or replace certain ca rd, BTS cable, etc (see RF analysis)

SW issue?•Normally after CTg analysis/other traces analysis, a bad system behaviour is discovered ���� Open case and attach the traces for investigation: CTg, Iub, mobile, etc

Unknown issue?•After depth investigation non identified cause ����Open a case and attach the traces for investigation: CTg, Iub trace, mobile, et c

RA

B e

stab

lsht

Page 181: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 51

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 51

5 IuSCCP Troubleshooting Analysis

Divider Section Break Pages

• Title block set 28/32pt Trebuchet white, flush left with text box positioned at,

Horizontal 1.87” and Vertical 2.87”

• This slide is to be used to create Section Divider slides

• Please copy, paste and modify this slide to reflect your specific needs. It is not

generated from a Master slide template

Page 182: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 52

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 52

5 IuSCCP Troubleshooting Analysis

Exercise: Success Rates Initiated by the RNC

1. Find the counters associated with the successful and failed SCCP connections requested by RNC at Iu interface for CS services.

2. Locate them on the chartHelp/reference:

� UMTS access counter list (look at the #05xx counters)

� UTRAN key performance metric definitions

SCCP connection confirm

(…)

SCCP connection req.

SC

CP

conn

.

UE RNCNode B CN

Page 183: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 53

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 53

5 IuSCCP Troubleshooting Analysis

Exercise (cont’d): Success Rates Initiated by the RNC

�With the counters you identify at the previous step, define the following metrics:

Iu SCCP success rate = Iu SCCP success rate =

CS Iu SCCP success rate = CS Iu SCCP success rate =

PS Iu SCCP success rate = PS Iu SCCP success rate =

SC

CP

con

n.

Page 184: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 54

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 54

5 IuSCCP Troubleshooting Analysis

SCCP Connection: Success Flow

SCCP connection confirm

(…)

SCCP connection request

#548[0,1]:successful SCCP connections initiated by RNC at Iu interface

SC

CP

con

n.

RNC counter

UE RNCNode B CN

VS.IuSccpCnxSuccess #548: This counter provides the number of successful SCCP connections atIu interface, screened by CN domain and by peer entity having refused the connection.

Screening:

� 0 : With CS core network (connection requested by RNC)

� 1 : With PS core network (connection requested by RNC)

� 2 : With CS core network (connection requested by core network)

� 3 : With PS core network (connection requested by core network)

Page 185: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 55

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 55

5 IuSCCP Troubleshooting Analysis

SCCP Connection: Failure Flow

(…)

SCCP connection request

#502[0,2] : failed SCCP connections initiated by RNC at Iu interface

SC

CP

con

n.

SCCP connection refusal

RNC counter

UE RNCNode B CN

VS.IuSccpCnxUnsuccess #502: This counter provides the number of failed SCCP connections at Iuinterface, screened by CN domain and by peer entity having refused the connection.

� 0 --> Connection on Iu-CS initiated by RNC refused (by the CN or SCCP layer of RNC)

� 1 --> Connection on Iu-CS initiated by CN refused by the RNC

� 2 --> Connection on Iu-PS initiated by RNC refused (by the CN or SCCP layer of RNC)

� 3 --> Connection on Iu-PS initiated by CN refused by the RNC

Page 186: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 56

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 56

5 IuSCCP Troubleshooting Analysis

SCCP Connection : Counter Tree

Request by RNC#548[0,1] + #502[0,2]

Failure#502[0,2]

Success#548[0,1]

VS.IuSccpCnxUnsuccess

VS.IuSccpCnxSuccess - VS.IuSccpCnxUnsuccess

VS.IuSccpCnxSuccess

RNC counters

SC

CP

con

n.

Page 187: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 57

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 57

5 IuSCCP Troubleshooting Analysis

Iu SCCP Analysis (success rates initiated by the RNC)

Iu SCCP success rate = Iu SCCP success rate =

#548.[0,1]

#548.[0,1] + #502.[0,2]

CS Iu SCCP success rate = CS Iu SCCP success rate =

#548.[0]

#548.[0] + #502.[0]

PS Iu SCCP success rate = PS Iu SCCP success rate = #548.[1]

#548.[1] + #502.[2]

SC

CP

con

n.

IuSCCP006

IuSCCP006[CS]

IuSCCP006[PS]

RNC metrics

Page 188: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 58

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 58

5 IuSCCP Troubleshooting Analysis

SCCP connection panels

Iu SCCP

Iur SCCP

Monitoring

Troubleshooting

Iu/Iur SCCP

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

counter RNC 502 VS.IuSccpCnxUnsuccess

counter RNC 516 VS.IuReceivedSccpAbnormalDisconnectsCs

counter RNC 517 VS.IuEmittedSccpAbnormalDisconnectsPs

counter RNC 518 VS.IuReceivedSccpAbnormalDisconnectsPs

counter RNC 532 VS.IuEmittedSccpAbnormalDisconnectsCs

counter RNC 548 VS.IuSccpCnxSuccess

counter RNC 1311 VS.IurSccpCnxSuccess

counter RNC 1312 VS.IurSccpCnxUnsuccess

counter RNC 1315 VS.IurAvgNbrInitSccpCnx

counter RNC 1316 VS.IurAvgNbrTermSccpCnx

counter RNC 1317 VS.IurEmittedSccpAbnormalDisconnects

counter RNC 1318 VS.IurReceivedSccpAbnormalDisconnects

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNCNot id yet in the

libraryIur SCCP Connection attempts

metric RNC 50_IurSCCP001_R IurSCCP Failure Rate%50_IurSCCP001_R

metric RNC 50_IuSCCP003_R%Cs IuSCCP Established Average%Cs%50_IuSCCP003_R

metric RNC 50_IuSCCP003_R%Ps IuSCCP Established Average%Ps%50_IuSCCP003_R

metric RNC 50_IuSCCP005_R%Cs IuSCCP Connection Attempts%Cs%50_IuSCCP005_R

metric RNC 50_IuSCCP005_R%Ps IuSCCP Connection Attempts%Ps%50_IuSCCP005_R

metric RNC 50_IuSCCP006_R%Cs IuSCCP Success Rate%Cs%50_IuSCCP006_R

metric RNC 50_IuSCCP006_R%Ps IuSCCP Success Rate%Ps%50_IuSCCP006_R

Page 189: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 59

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 59

5 IuSCCP Troubleshooting Analysis

Iu SCCP analysis method

Issue characterization:• Iu CS or Iu PS issue?• Affecting all RNC/only specific RNC• Punctual degradation that disappear?

Or degradation remains?• Certain/all period of time, since when

Iu SCCP Analysis –RNC level

Low CS/PS Iu SCCP Connection success rateIuSCCP006 in all RNCs

of the same core network?

Core outage(upgrade, failure or

issue clearlyidentified as core

issue?

First RNC in this UTRAN version release?

Yes No

Yes No

No investigation needed

•HW Stability Analysis –RNC – MSC Interface/RNC-SGSN Intefaces•CTg traces•Iu traces

Yes No

Analysis of CR fixesAnd evolution introduced

Configuration Audit

•Configuration Audit•Parameter correlationswith other RNCs

Threshold need to be adapted to theoperator case, see threshold info

Page 190: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 60

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 60

5 IuSCCP Troubleshooting Analysis

Case Study

� Analyse metric graphs given bellow !

� What could you say about IuSCCP performances ?

90.00%

92.00%

94.00%

96.00%

98.00%

100.00%

01/09/2006

03/09/2006

05/09/2006

07/09/2006

09/09/2006

11/09/2006

13/09/2006

15/09/2006

17/09/2006

19/09/2006

21/09/2006

23/09/2006

25/09/2006

27/09/2006

29/09/2006PS Call Setup Success Rate CS Call Setup Success Rate

96.00%96.50%97.00%97.50%98.00%98.50%99.00%99.50%

100.00%

01/09/2006

03/09/2006

05/09/2006

07/09/2006

09/09/2006

11/09/2006

13/09/2006

15/09/2006

17/09/2006

19/09/2006

21/09/2006

23/09/2006

25/09/2006

27/09/2006

29/09/2006

PS Iu SCCP success rate CS Iu SCCP success rate

Iu SCCP PS success rate (IuSCCP006)

95.00%

96.00%

97.00%

98.00%

99.00%

100.00%

21/08/0622/08/0623/08/0624/08/0625/08/0626/08/0627/08/0628/08/0629/08/0630/08/0631/08/0601/09/0602/09/0603/09/0604/09/0605/09/0606/09/0607/09/0608/09/0609/09/0610/09/0611/09/0612/09/0613/09/0614/09/0615/09/0616/09/0617/09/0618/09/0619/09/0620/09/0621/09/0622/09/0623/09/0624/09/0625/09/0626/09/0627/09/0628/09/0629/09/0630/09/0601/10/0602/10/0603/10/0604/10/0605/10/0606/10/0607/10/0608/10/0609/10/0610/10/0611/10/0612/10/0613/10/0614/10/0615/10/06

GQ01

GQ02

GQ03

KQ01

KQ02

OQ01

OQ02

OQ03

OQ04

Page 191: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 61

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 61

5 IuSCCP Troubleshooting Analysis

Example (1/2): IuSCCP analysis

� Issue characterization:

� Iu CS or Iu PS issue? � PS

� Affecting all RNC/only specific RNC� ?

� Punctual degradation that disappear?Or degradation remains?� Punctual 28/09/05

90.00%

92.00%

94.00%

96.00%

98.00%

100.00%

01/09/2006

03/09/2006

05/09/2006

07/09/2006

09/09/2006

11/09/2006

13/09/2006

15/09/2006

17/09/2006

19/09/2006

21/09/2006

23/09/2006

25/09/2006

27/09/2006

29/09/2006

PS Call Setup Success Rate CS Call Setup Success Rate

96.00%96.50%97.00%97.50%98.00%98.50%99.00%99.50%

100.00%

01/09/2006

03/09/2006

05/09/2006

07/09/2006

09/09/2006

11/09/2006

13/09/2006

15/09/2006

17/09/2006

19/09/2006

21/09/2006

23/09/2006

25/09/2006

27/09/2006

29/09/2006

PS Iu SCCP success rate CS Iu SCCP success rate

Page 192: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 62

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 62

5 IuSCCP Troubleshooting Analysis

Example (2/2): IuSCCP analysis

Iu SCCP PS success rate (IuSCCP006)

95.00%

96.00%

97.00%

98.00%

99.00%

100.00%

21/08/0622/08/0623/08/0624/08/0625/08/0626/08/0627/08/0628/08/0629/08/0630/08/0631/08/0601/09/0602/09/0603/09/0604/09/0605/09/0606/09/0607/09/0608/09/0609/09/0610/09/0611/09/0612/09/0613/09/0614/09/0615/09/0616/09/0617/09/0618/09/0619/09/0620/09/0621/09/0622/09/0623/09/0624/09/0625/09/0626/09/0627/09/0628/09/0629/09/0630/09/0601/10/0602/10/0603/10/0604/10/0605/10/0606/10/0607/10/0608/10/0609/10/0610/10/0611/10/0612/10/0613/10/0614/10/0615/10/06

GQ01

GQ02

GQ03

KQ01

KQ02

OQ01

OQ02

OQ03

OQ04

� Issue characterization:� Iu CS or Iu PS issue? � PS

� Affecting all RNC/only specific RNC�All RNCs

� Punctual degradation that disappear?Or degradation remains?� Punctual 28/09/05

To correlate with O&M tracking event:Upgrades/outages/alarmsin PS Core Network

UA4.2 Operator example

Page 193: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 63

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 63

6 Security Mode Troubleshooting Analysis

Divider Section Break Pages

• Title block set 28/32pt Trebuchet white, flush left with text box positioned at,

Horizontal 1.87” and Vertical 2.87”

• This slide is to be used to create Section Divider slides

• Please copy, paste and modify this slide to reflect your specific needs. It is not

generated from a Master slide template

Page 194: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 64

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 64

6 Security Mode Troubleshooting Analysis

Security Mode Success: Flow

UERRC Connection Request

RRC Connection Complete

RRC Connection Setup

Radio Link Setup Request

Radio Link Setup Response

Measurement Control

Init Direct Transfer

RNCNode B CN

SCCP connection confirm

SCCP connection req.

Security mode command

Security mode complete

Security mode command

Security mode completeCommon id

RR

C c

onne

ctio

nS

CC

Pco

nn.

Sec

urity

mod

e

#701:successful Security Mode procedures

VS.SmcSuccess #701: This counter provides the number of successful RANAP Security Mode Command procedures screened by Core Network domain.

Screening:

� • 0 : SMC on Iu-CS

� • 1 : SMC on Iu-PS

Page 195: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 65

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 65

6 Security Mode Troubleshooting Analysis

Security Mode Failure: RNC

Security mode command

Security mode reject#702:rejected Security Mode procedures

Sec

urity

mod

e

RNC counter

Cause = "Requested Ciphering

and/or Integrity Protection Algorithms

not Supported"

UE RNCNode B CN

VS.RejectedSmc #702: This counter provides the number of failed RANAP Security Mode Command procedures (before sending the RRC SMC) screened by Core Network domain.

Screening:

� • 0 : SMC on Iu-CS

� • 1 : SMC on Iu-PS

Page 196: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 66

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 66

6 Security Mode Troubleshooting Analysis

Security Mode Failure: UE

Security mode commandSecurity mode command

Security mode failureSecurity mode reject

#703:failed Security Mode procedures

Cause = same as in previous page

Security mode commandSecurity mode command

Security mode reject

#703:failed Security Mode procedures

Cause = "Failure in the Radio Interface Procedure”

No answer from UE

1st

case

2nd

case

RNC counters

UE RNCNode B CN

Sec

urity

mod

e

VS.FailedRrcSmc #703: This counter provides the number of failed RRC Security Mode Command procedures screened by Core Network domain.

Screening:

� • 0 : SMC on Iu-CS

� • 1 : SMC on Iu-PS

Page 197: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 67

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 67

6 Security Mode Troubleshooting Analysis

Security Mode Command Success Ratio

Core CSSecurity ModeCmd success ratio

Core CSSecurity ModeCmd success ratio

#701.[0]

#701.[0] + #702.[0] + #703.[0]=

Core PSSecurity ModeCmd success ratio

Core PSSecurity ModeCmd success ratio

#701.[1]

#701.[1] + #702.[1] + #703.[1]=

RNC metrics

Sec

urity

mod

e

� For the three following metrics the screening is:

� 0 ---> Circuit Switched 1 ---> Packet Switched

#701 Number of successful RANAP security mode command procedures. This measurement provides the number of successful RANAP Security Mode Command procedures screened by Core Network domain.

#702 Number of failed RANAP security mode command procedures. This measurement provides the number of failed RANAP Security Mode Command procedures (before sending the RRC SMC) screened by Core Network domain.

#703 Number of failed RRC security mode command procedures. This measurement provides the number of failed RRC Security Mode Command procedures screened by Core Network domain.

Page 198: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 68

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 68

6 Security Mode Troubleshooting Analysis

Ciphering analysis

� If the SMC Failure rate is high, it means that the accessibility performance

results are weak due to Ciphering phase.

� SMC failures can affect to signaling procedures (LAU, RAU…) but also calls.

� There is not way to split the failures in traffic/signaling, so some signaling

failures could mask the call success rate,

� If the RNC receives a certain number of consecutive RRC messages with wrong

integrity data, it requests to release the call by sending a RANAP Iu Release

Request with cause Repeated Integrity Protection Check Failure to the Core.

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_SMC001_R%Cs Security Mode Command%Cs%50_SMC001_R

metric RNC 50_SMC001_R%Ps Security Mode Command%Ps%50_SMC001_R

metric RNC 50_SMC002_R%Cs Security Mode Command Success Rate%Cs%50_SMC002_R

metric RNC 50_SMC002_R%Ps Security Mode Command Success Rate%Ps%50_SMC002_R

Page 199: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 69

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 69

7 Call Setup Success Rate Troubleshooting Analysis

Divider Section Break Pages

• Title block set 28/32pt Trebuchet white, flush left with text box positioned at,

Horizontal 1.87” and Vertical 2.87”

• This slide is to be used to create Section Divider slides

• Please copy, paste and modify this slide to reflect your specific needs. It is not

generated from a Master slide template

Page 200: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 70

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 70

7 Call Setup Success Rate Troubleshooting Analysis

Exercise

Call set upsuccess rate

Call set upsuccess rate

=

� Using the formerly defined metrics define the Call Setup SuccessRate formula !

Page 201: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 71

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 71

7 Call Setup Success Rate Troubleshooting Analysis

Exercise

This page is intentionally left blank

Page 202: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 72

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 72

7 Call Setup Success Rate Troubleshooting Analysis

Call Set Up Success Rate

�RRC003 = RRC connection success rate (see Accessibility: RRC Connection Success Rate)

�IuSCCP006 = Iu SCCP success rate (see Iu SCCP Analysis)

�SMC002 = Security mode command success ratio (see Security mode command success ratio)

�RAB011 = RAB establishment success rate per requested RAB (see RAB Assignment Analysis)

Call set upsuccess rate

Call set upsuccess rate

RRC003 (calls only) x IuSCCP006x SMC002 x RAB011

=

SC

CP

con

n.R

RC

con

nect

ion

Sec

urity

mod

eR

AB

est

abls

ht

� The call set up success rate at RNC indicates the rate of successful call establishment vs. call

establishment attempts. Product of RRC success rate (calls only) * Iu SCCP success rate * RAB

establishment success rate * SMC success rate.

Page 203: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 73

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 73

7 Call Setup Success Rate Troubleshooting Analysis

Accessibility Troubleshooting Chart

Network Accessibility Analysis –RNC level

RRC Connection Analysis –RNC/ Cell level

Iu SCCP Analysis –RNC level

RAB Assignment Analysis –RNC level

Iu SCCP Connection Success rate

IuSCCP006<99%

RAB Assignm ent Success rateRAB011 <99%

Call setup success rateCSSR005wka < 94%

No

Low CSSR with Ciphering

Ciphering Analysis –RNC level

RRC Connection Success rate

RRC003 < 95%RRC013

Yes

Low SMC success rate

SMC002

Top N CellsCSSRYes

CTg Analysis –Cell level

No

Page 204: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 74

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 74

7 Call Setup Success Rate Troubleshooting Analysis

Case Study

� Analyse metric graphs given bellow !

� What is your conclusion ?

90.00%

92.00%

94.00%

96.00%

98.00%

100.00%

01/09/2006

03/09/2006

05/09/2006

07/09/2006

09/09/2006

11/09/2006

13/09/2006

15/09/2006

17/09/2006

19/09/2006

21/09/2006

23/09/2006

25/09/2006

27/09/2006

29/09/2006

PS Call Setup Success Rate CS Call Setup Success Rate

96.00%

97.00%

98.00%

99.00%

100.00%

01/09/2006

03/09/2006

05/09/2006

07/09/2006

09/09/2006

11/09/2006

13/09/2006

15/09/2006

17/09/2006

19/09/2006

21/09/2006

23/09/2006

25/09/2006

27/09/2006

29/09/2006

PS RRC Connection success rate CS RRC Connection success rate

PS First RRC Connection success rate CS First RRC Connection success rate

96.00%

97.00%

98.00%

99.00%

100.00%01/09/2006

03/09/2006

05/09/2006

07/09/2006

09/09/2006

11/09/2006

13/09/2006

15/09/2006

17/09/2006

19/09/2006

21/09/2006

23/09/2006

25/09/2006

27/09/2006

29/09/2006

PS RAB Establishments success rate RAB type

CS RAB Establishments success rate RAB type

96.00%96.50%97.00%97.50%98.00%98.50%99.00%99.50%

100.00%

01/09/2006

03/09/2006

05/09/2006

07/09/2006

09/09/2006

11/09/2006

13/09/2006

15/09/2006

17/09/2006

19/09/2006

21/09/2006

23/09/2006

25/09/2006

27/09/2006

29/09/2006

PS Iu SCCP success rate CS Iu SCCP success rate

Page 205: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 75

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 75

90.00%

92.00%

94.00%

96.00%

98.00%

100.00%

01/09/2006

03/09/2006

05/09/2006

07/09/2006

09/09/2006

11/09/2006

13/09/2006

15/09/2006

17/09/2006

19/09/2006

21/09/2006

23/09/2006

25/09/2006

27/09/2006

29/09/2006

PS Call Setup Success Rate CS Call Setup Success Rate

96.00%96.50%97.00%97.50%98.00%98.50%99.00%99.50%

100.00%

01/09/2006

03/09/2006

05/09/2006

07/09/2006

09/09/2006

11/09/2006

13/09/2006

15/09/2006

17/09/2006

19/09/2006

21/09/2006

23/09/2006

25/09/2006

27/09/2006

29/09/2006

PS Iu SCCP success rate CS Iu SCCP success rate

96.00%

97.00%

98.00%

99.00%

100.00%

01/09/2006

03/09/2006

05/09/2006

07/09/2006

09/09/2006

11/09/2006

13/09/2006

15/09/2006

17/09/2006

19/09/2006

21/09/2006

23/09/2006

25/09/2006

27/09/2006

29/09/2006

PS RRC Connection success rate CS RRC Connection success rate

PS First RRC Connection success rate CS First RRC Connection success rate

96.00%

97.00%

98.00%

99.00%

100.00%

01/09/2006

03/09/2006

05/09/2006

07/09/2006

09/09/2006

11/09/2006

13/09/2006

15/09/2006

17/09/2006

19/09/2006

21/09/2006

23/09/2006

25/09/2006

27/09/2006

29/09/2006

PS RAB Establishments success rate RAB type

CS RAB Establishments success rate RAB type

7 Call Setup Success Rate Troubleshooting Analysis

Case Study : Accessibility Monitoring & Troubleshooting

Page 206: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 76

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 76

7 Call Setup Success Rate Troubleshooting Analysis

Case Study : Accessibility Monitoring & Troubleshooting

Network Accessibility Analysis –RNC level

RRC Connection Analysis –RNC/ Cell level

Iu SCCP Analysis –RNC level

Iu SCCP Connection Success rate

IuSCCP006<99%

Refer to the Accessibility

metrics in RNC Panel

Call Setup Success Rate

CSSR005wka < 94%No

RRC Connection Success rateRRC003 or RRC013 < 95%

RAB Assignment Analysis –RNC level

RAB Assignment Success rate

RAB011 <99%

CS/PS

Low CSSR with Ciphering/Authentication

Refer to the CSSR with Ciphering

/Authentication metric

Ciphering/AuthenticationAnalysis –RNC level

YesYes

Page 207: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 77

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 77

Self-Assessment on the Objectives

� Please be reminded to fill in the formSelf-Assessment on the Objectivesfor this module

� The form can be found in the first partof this course documentation

Page 208: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 4 � Page 78

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Accessibility Monitoring & Troubleshooting Section 4 �Page 78

End of Module

Page 209: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 1

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

Do not delete this graphic elements in here:

All Rights Reserved © Alcatel-Lucent 2007

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

5 3FL12921AAAAWBZZA Edition 1

Section 5Retainibility Monitoring &

Troubleshooting

Page 210: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 2

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 2

Blank Page

This page is left blank intentionally

Second editionEL ABED, Achrafe2007-10-2002

First editionEL ABED, Achrafe2007-08-2401

RemarksAuthorDateEdition

Document History

Page 211: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 3

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 3

Objectives

� After this course, you will be able to :

� Describe the retainability metric family

� Illustrate the call flows associated with the metric family

� Identify counters and locate them in the call flow procedure

� Define metrics and recognize its key counters

� Analyze each metric

Page 212: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 4

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 4

Objectives [cont.]

This page is left blank intentionally

Page 213: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 5

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 5

Table of Contents

Switch to notes view!Page

1 Retainability analysis 7KPIs families Reminder 8Call Drop: Definition 9Network Retainability Performance 10Call Drop: UL RL Failure detected 11Call Drop: DL RL Failure detected 12Call Drops due to UTRAN generated reasons 13Call Drops due to UTRAN generated reasons 14Call Drops due to UTRAN generated reasons 15Call Drops due to UTRAN generated reasons 16Call Drops due to UTRAN generated reasons 17

2 Retainability troubleshooting 18Call Drop Rate Analysis 19Retainibility issues causes 20Retainibility issues causes 21Retainability Troubleshooting Chart: Failure Drop cause 22Self-Assessment on the Objectives 23End of Module 24

Page 214: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 6

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 6

Table of Contents [cont.]

Switch to notes view!

This page is left blank intentionally

Page 215: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 7

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 7

1 Retainability analysis

Page 216: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 8

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 8

1 Retainability analysis

KPIs families Reminder

Network Accessibility

NetworkRetainability Network

Quality

NetworkTraffic

NetworkCongestion

Counter based KPIs

Capacity/

Load

Call ProfileHSxPA

RRM

NetworkMobility

Retainability monitoring - RNC panel

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 217: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 9

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 9

1 Retainability analysis

Call Drop: Definition

� User view

� call drop is seen as a service interruption

� mainly perceived for CS calls (voice, video calls)

� data service almost never broke off (throughput degradation only)

� UTRAN system view

� call drop is seen as an abnormal RAB release initiated by the RNC

� affects CS and PS services as well

� data service is often resumed by UE or CN after a PS drop

� CN system view

� closer to User view than UTRAN system view

When a RAB or a list of RABs must be reset for any reason, i.e: normal release or abnormal release, a RANAP Release procedure has to be triggered almost every time.

In UMTS standard, there are different ways at RANAP protocol level, to release a RAB, or a list of RABsrelated to a particular UE:

• RAB Release request: triggered by the RNC, requesting the CN to release a particular RAB or a set ofRABs for a specific UE. RRC connection may still active.

The Core network may trigger or a RAB Assignment procedure or an Iu Release procedure.

• Iu Release request: triggered by the RNC, requesting the CN to release the Iu connection related to a specific UE. This will release all the RABs (PS+CS) related to that UE. RRC connection is also released. The CN could respond with Iu Release command.

• RAB Assignment request: triggered by the CN (or response to the RAB release request) and asking the RNC to release one or a list of RABs.

• Iu Release command: Triggered by the CN (or response to the RAB release request or Iu release request) and asking the RNC to release all the resources (RRC + RBs) of a UE.

Call drop counters are be counted on the messages described above per Reference FDDCell and per DlAsConfId or at least per CN domain (CS,PS).

Page 218: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 10

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 10

1 Retainability analysis

Network Retainability Performance

� The objective of the retainability metrics is to evaluate the ability of the network to provide reliable service to the end user.

� If and only if a call is dropped, the RNC sends the RANAP Iu Release Request message with the field abnormal reasons.

� A good part of the calls dropped are originated by a Radio Link Failure Indication message

Page 219: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 11

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 11

1 Retainability analysis

Call Drop: UL RL Failure detected

Node B RNC CN

Radio Link Failure Indication

Radio Link Deletion Resp

Iu Release Request“UTRAN generated reason”

Iu Release Command

Radio Link Deletion Req

UE

Loss of UL synchro detected on last RL #34 Last Radio Link drops

FDDCell counter

#572 Iu abnormal release request CS#573 Iu abnormal release request PS

#576[4] Iu release request CS#577[6] Iu release request PS

Reference FDDCell counters

#505[2] Iu release command CS#506[2] Iu release command PS

Reference FDDCell counters

Iu Release Complete

Question:What is the difference

between #576 & #572 ?

VS.IuReleaseReqCs - #576Number of RANAP/IU_RELEASE_REQUEST sent by RNC to CoreNetwork CSA set of subcounters screened on: Reason to send Release Request CS Cause• Sub-Counter #0 : OAM Intervention • Sub-Counter #1 : Unspecified Failure• Sub-Counter #2 : Repeated Integrity Check Failure • Sub-Counter #3 : UE generated signalling cnxrelease• Sub-Counter #4 : Radio cnx with UE lost • Sub-Counter #5 : Abnormal condition with causeTRelocOveral expiry• Sub-Counter #6 : Other causes • Sub-Counter #7 : DL RLC error on SRB• Sub-Counter #8 : UL RLC error on SRB • Sub-Counter #9 : T360 ExpiryVS.IuReleaseReqPs - #577A set of subcounters screened on: Release Request Cause PS• Sub-Counter #0 : User Inactivity • Sub-Counter #1 : IU User Plane Failure• Sub-Counter #2 : OAM Intervention • Sub-Counter #3 : Unspecified Failure• Sub-Counter #4 : Repeated Integrity Check Failure • Sub-Counter #5 : UE generated signalling cnxrelease• Sub-Counter #6 : Radio cnx with UE lost • Sub-Counter #7 : Abnormal condition with causeTRelocOveral expiry• Sub-Counter #8 : Other causes • Sub-Counter #9 : DL RLC error on SRB• Sub-Counter #10 : UL RLC error on SRB • Sub-Counter #11 : DL RLC error on TRB• Sub-Counter #12 : UL RLC error on TRB • Sub-Counter #13 : T360 ExpiryVS.IuAbnormalReleaseRequestCs - #572This measurement represents the number of Iu CS release requests due to abnormal conditions.A set of subcounters screened on: Derived AsConf Screening for CS DlAsConfId:• Sub-Counter #0 : Other • Sub-Counter #1 : Signalling Only• Sub-Counter #2 : CS speech • Sub-Counter #3 : CS data• Sub-Counter #4 : CS Streaming 57.6 • Sub-Counter #5 : CS Streaming 14.4• Sub-Counter #6 : CS Signalling + PSVS.IuAbnormalReleaseRequestPs - #573This measurement represents the number of Iu PS release requests due to abnormal conditions.A set of subcounters screened on: Derived AsConf Screening for PS DlAsConfId:• Sub-Counter #0 : Signalling Only • Sub-Counter #1 : PS Streaming 16• Sub-Counter #2 : PS Streaming 64 • Sub-Counter #3 : PS Streaming 128

Page 220: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 12

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 12

1 Retainability analysis

Call Drop: DL RL Failure detected

Node B RNC CN

Radio Link Deletion Resp

Iu Release Request“UTRAN generated reason”

Iu Release Command

Radio Link Deletion Req

UE

RL or RLC failure DL detected

#572 Iu abnormal release request CS#573 Iu abnormal release request PS

#576[7] Iu release request CS#577[9] Iu release request PS

#505[2] Iu release command CS#506[2] Iu release command PS

Iu Release Complete

Cell Update“radio link failure” or “RLC unrecoverable error”

#571 Iu release complete CS#539 Iu release complete PS

Reference FDDCell counters

VS.IuReleaseCompleteCs #571: Number of times the RNC sends an Iu release complete on Iu-CS interface to MSC. It corresponds to all cases of Iu release scenario, normal and abnormal.

Screening: DlAsConfId

VS.IuReleaseCompletePs #539: Number of times the RNC sends an Iu release complete on Iu-PS interface to SGSN. It corresponds to all cases of Iu release scenario, normal and abnormal.

Screening: DlAsConfId

Page 221: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 13

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 13

1 Retainability analysis

Call Drops due to UTRAN generated reasons

� All call drops generated by UTRAN are counted in

� VS.IuAbnormRelReqCs #572 for CS

� VS.IuAbnormRelReqPs #573 for PS

� Call drops due to UTRAN are counted in

� VS.IuAbnormRelReqCs #576 for CSAll screenings except

� 4: Release due to UE

� VS.IuAbnormRelReqPs #577 for PSAll screenings except

� 0: User inactivity (Always On step 2)

� 5: Release due to UE

Reference FDDCell counters

VS.IuAbnormRelReqCs #546: Number of times the RNC requests an Iu release on Iu-CS interface due to abnormal conditions. It corresponds to all cases of call drops CS due to UTRAN

Screening: DlAsConfId

VS.IuAbnormRelReqPs #547: Number of times the RNC requests an Iu release on Iu-PS interface due to abnormal conditions. It corresponds to all cases of call drops PS due to UTRAN

Screening: DlAsConfId

VS.IuAbnormRelReqCs #540: Number of times the RNC sends an Iu release request message to the MSC (counts normal and abnormal releases).

Screening: DlAsConfId

0 : Release due to OAM intervention 6 : Relocation too long (timer on relocation expiry).

1 : Iu User-plane failure 7 : Other cause (For future use, not implemented)

2 : Unspecified failure 8 : DL RLC error on SRB

3 : Repeated Integrity protection check failure 9 : UL RLC error on SRB

4 : Release due to UE 10 : DL RLC error on TRB

5 : Radio connection lost with UE 11 : UL RLC error on TRB

VS.IuReleaseRequestPs #541: Number of times the RNC sends an Iu release request message to the SGSN (counts normal and abnormal releases).

Screening: DlAsConfId

0 : User inactivity (Always On step 2)

1 : Iu User-plane failure 7 : Relocation too long (timer on relocation expiry).

2 : Release due to OAM intervention 8 : Other cause (For future use, not implemented)

3 : Unspecified failure 9 : DL RLC error on SRB

4 : Repeated Integrity protection check failure 10 : UL RLC error on SRB

5 : Release due to UE 11 : DL RLC error on TRB

6 : Radio connection lost with UE 12 : UL RLC error on TRB

Page 222: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 14

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 14

1 Retainability analysis

Call Drop Rate: RNC level

� Metric definition: call drop rate at RNC level

Number of Iu abnormal release request

Number of granted RAB

=

Σ(#573 + #561).[ 2,4,6,7,9-12,15-19,21-26,28-30]

#673.[0,5-42]=

RNC metric

Σ(#572 + #560).[0,1,5,8-10,14-18,21,22,26,29]

#673.[1-4]

RNC metric

CS call drop rate

at RNC level

PS call drop rate

at RNC level

=

Iu007[CS]

Iu007[PS]

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 223: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 15

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

Retainability troubelshootin pannel – service split (1/2)

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 15

1 Retainability analysis

CS Call Drop Rate: Reference FDDCell level

� Metric definition: CS call drop rate at cell level

Number of Iu abnormal release request on Iu-CS

Number of CS RAB released

� Iu-CS connection released each time CS RAB is released

� For normal and abnormal reasons

� Nb of RAB released used instead of Nb of RAB established

#576.[0,1,5,8-10,14-18,21,22,26,29]

#571.[0,1,5,8-10,14-18,21,22,26,29]=

Reference FDDCell metric Iu006[CS]

CS call drop rate

at cell level

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

counter Fcell&RNC 572 VS.IuAbnormalReleaseRequestCS - all screenings

counter Fcell&RNC 573 VS.IuAbnormalReleaseRequestPS - all screenings

metric Fcell&RNC ? PS R99DL%Iu Abnormal Release Request

metric RNC 50_IU019_R%Ps R99 Number of Drops per Minute of Calls%Ps%50_IU019_R R99?

metric Fddcell 50_IU006_C%Cs Call Drop Rate%Cs%50_IU006_C

metric Fddcell 50_IU006_C%CsSRB Call Drop Rate%CsSRB%50_IU006_C

metric Fddcell 50_IU006_C%Ps Call Drop Rate%Ps%50_IU006_C

metric RNC 50_IU007_R%Cs Call Drop Rate%Cs%50_IU007_R

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%HSDPA Call Drop Rate%HSDPA%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

metric Fcell&RNC 50_IU008_C%CsSRB Iu Abnormal Release Request%CsSRB%50_IU008_C

metric Fcell&RNC 50_IU008_R%Cs Iu Abnormal Release Request%Cs%50_IU008_R

metric Fcell&RNC 50_IU008_R%CsVideo Iu Abnormal Release Request%CsVideo%50_IU008_R

metric Fcell&RNC 50_IU008_R%CsVoice Iu Abnormal Release Request%CsVoice%50_IU008_R

metric Fcell&RNC 50_IU008_R%HSDPA Iu Abnormal Release Request%HSDPA%50_IU008_R

metric Fcell&RNC 50_IU008_R%Ps Iu Abnormal Release Request%Ps%50_IU008_R

metric Fcell&RNC 50_IU008_R%Ps128 Iu Abnormal Release Request%Ps128%50_IU008_R

Page 224: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 16

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

Retainability roubelshootin pannel – service split (2/2)

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 16

1 Retainability analysis

PS Call Drop Rate: Reference FDDCell level

� Metric definition: PS call drop rate at cell level

Number of Iu abnormal release request on Iu-PS

Number of PS RAB released

� Number of PS RAB released = (Abnormal + Normal) release

� Abnormal release = Iu Release Request sent by RNC on Iu-PS

� Normal release = Radio Bearer Release Complete received by RNC

� Normal release = RRC Connection Release Complete after user inactivity is detected (AO step2 success)

=

Reference FDDCell metric

#573.[2,4,6,7,9-12,15-19,21-26,28-30]

#573.[same screenings] + #688.[PS] + #1163.[PS]

Iu006[PS]

=PS call drop rate

at cell level

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric Fcell&RNC 50_IU008_R%Ps256 Iu Abnormal Release Request%Ps256%50_IU008_R

metric Fcell&RNC 50_IU008_R%Ps32 Iu Abnormal Release Request%Ps32%50_IU008_R

metric Fcell&RNC 50_IU008_R%Ps384 Iu Abnormal Release Request%Ps384%50_IU008_R

metric Fcell&RNC 50_IU008_R%Ps64 Iu Abnormal Release Request%Ps64%50_IU008_R

metric Fcell&RNC 50_IU008_R%Ps8 Iu Abnormal Release Request%Ps8%50_IU008_R

metric Fcell&RNC 50_IU008_R%PsFach Iu Abnormal Release Request%PsFach%50_IU008_R

metric Fcell&RNC 50_IU010_R%Cs Iu Release Command%Cs%50_IU010_R

metric Fcell&RNC 50_IU010_R%Ps Iu Release Command%Ps%50_IU010_R

metric Fcell&RNC 50_IU011_R%CsVideo Iu Release Complete per RefCell%CsVideo%50_IU011_R

metric Fcell&RNC 50_IU011_R%CsVoice Iu Release Complete per RefCell%CsVoice%50_IU011_R

metric Fcell&RNC 50_IU012_R Percentage of CS Calls Dropped due to RL Failure%50_IU012_R

metric Fcell&RNC 50_IU013_R Percentage of PS Calls Dropped due to RL Failure%50_IU013_R

metric RNC 50_IU019_R%Cs Number of Drops per Minute of Calls%Cs%50_IU019_R

metric RNC 50_IU019_R%CsVideo Number of Drops per Minute of Calls%CsVideo%50_IU019_R

metric RNC 50_IU019_R%CsVoice Number of Drops per Minute of Calls%CsVoice%50_IU019_R

metric RNC 50_IU019_R%HSDPA Number of Drops per Minute of Calls%HSDPA%50_IU019_R

metric RNC 50_IU019_R%Ps Number of Drops per Minute of Calls%Ps%50_IU019_R

metric Fcell&RNC 50_RL007_CR Last Radio Link Dropped%50_RL007_CR

metric Fcell&RNC 50_RL007_CR%Cs Last Radio Link Dropped%Cs%50_RL007_CR

metric Fcell&RNC 50_RL007_CR%CsVideo Last Radio Link Dropped%CsVideo%50_RL007_CR

metric Fcell&RNC 50_RL007_CR%CsVoice Last Radio Link Dropped%CsVoice%50_RL007_CR

metric Fcell&RNC 50_RL007_CR%HSDPA Last Radio Link Dropped%HSDPA%50_RL007_CR

metric Fcell&RNC 50_RL007_CR%Ps Last Radio Link Dropped%Ps%50_RL007_CR

Page 225: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 17

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 17

1 Retainability analysis

CS Call Drop Rate Analysis

� Use some metrics to discriminate CS call drops due to

� RF Conditions

� UTRAN system problems

� Metric definition: % of CS calls dropped due to RL failure

Number of Iu-CS release request due to RF problem

Total number of Iu-CS release request

=

Reference FDDCell metric

Percentage of CS calls dropped due to RL failure

#576.[4]

#576.[0-9]

Iu012

=

VS.IuAbnormRelReqCs #540: Number of times the RNC sends an Iu release request message to the MSC (counts normal and abnormal releases).

Screening: DlAsConfId

0 : Release due to OAM intervention 6 : Relocation too long (timer on relocation expiry).

1 : Iu User-plane failure 7 : Other cause (For future use, not implemented)

2 : Unspecified failure 8 : DL RLC error on SRB

3 : Repeated Integrity protection check failure 9 : UL RLC error on SRB

4 : Release due to UE 10 : DL RLC error on TRB

5 : Radio connection lost with UE 11 : UL RLC error on TRB

Retainability troubelshootin pannel – drop failure cause (1/2)

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

counter Fcell&RNC 576 VS.IuReleaseReqCs.OamIntervention

counter Fcell&RNC 576 VS.IuReleaseReqCs.IuUserPlaneFailure

counter Fcell&RNC 576 VS.IuReleaseReqCs.UnspecifiedFailure

counter Fcell&RNC 576 VS.IuReleaseReqCs.RepeatedIntegrityCheckFailure

counter Fcell&RNC 576 VS.IuReleaseReqCs.UeGeneratedSignallingConnectionRelease

counter Fcell&RNC 576 VS.IuReleaseReqCs.RadioConnectionWithUeLost

counter Fcell&RNC 576 VS.IuReleaseReqCs.AbnormalConditionTimerRelocExpiry

counter Fcell&RNC 576 VS.IuReleaseReqCs.OtherCause

counter Fcell&RNC 576 VS.IuReleaseReqCs.DlRLCErrSRB

counter Fcell&RNC 576 VS.IuReleaseReqCs.UlRLCErrSRB

counter Fcell&RNC 576 VS.IuReleaseReqCs.T360Expiry

counter Fcell&RNC 577 VS.IuReleaseReqPs.AlwaysOnDowngrade

counter Fcell&RNC 577 VS.IuReleaseReqPs.IuUserPlaneFailure

Page 226: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 18

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 18

2 Retainability troubleshooting

Page 227: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 19

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 19

2 Retainability troubleshooting

Call Drop Rate Analysis

� To define Call Drop problem, 2 parallel analysis to correlate:� Distribution per Failure cases analysis: which failure cause� Distribution per Service failure analysis (which RB are affected?)

� Issue characterization:� Can it affect certain/all services (CS, PS, SRB,etc)� Certain/all Network elements, Top N cells� Certain/all period of time, since when� Certain failure causes� After certain event (upgrade, feature activation, configuration changes)

VS.RadioBearerReleaseSuccess #688: number of successful radio bearer releases for each cell controlled by the RNC which is the primary cell for the call. This counter is pegged by the RNC at the reception of a RRC RADIO BEARER RELEASE COMPLETE message following the emission of a RRC RADIO BEARER RELEASE message.

Screening: DlAsConfId

VS.RadioBearerReleaseSuccess #1163: number of downsizing step 2 successes for each cell controlled by the RNC which is the primary cell of the call.

This counter is pegged each time an "Always On" algorithm decision taken by the RNC to release an UE call due to the UE inactivity is successfully carried out. It is started on reception of a RRC CONNECTION RELEASE COMPLETE message for "User inactivity" reason.

Screening: DlAsConfId

PS screenings = 2,4,6,7,9-12,15-19,21-26,28-30

Total number of Iu Release Request sent by RNC on Iu-PS is not used since in case the feature “Limited Iu Release” is activated the RNC does not ask the CN to release the Iu-PS connection when the a PS RAB is released.

Page 228: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 20

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 20

2 Retainability troubleshooting

Retainibility issues causes

Degradation of Retainability KPIs

RNC Instability

NodeB Instability

DL/UL RF Conditions

- Monitor Ec/No & RSCP- Monitor UL RSSI

- Monitor PCM Counters

-Monitor CPU Counters-Monitor PS-FP couters

Metrics and reports will be selected, going from a high level with the executive reports to a deeper level with the detailed reports. This is a strategy from the top to the bottom. The format of the reports will be graph or table.

The granularity for reporting must be also selected in terms of time (hourly, daily, weekly…) and the network elements for each reports.

The output of this step is coming with a set of deliverable reports to use for monitoring activities.

The following shows an example of deliverable reports for a network on the UTRAN side:

- Weekly Performance Monitoring reports based mainly on RNC Panel

- Daily Performance Monitoring reports based on worst cell lists

- Investigation reports based on troubleshooting metrics.

Page 229: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 21

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 21

Retainability Analysis RNC level

CS High Call drop rateat RNC level

Iu007- CS >2%

PS High Call drop rate at RNC level

Iu007- PS >4%

PS Retainability per RBRNC level

CS RetainabilityRNC level

Iu007>3%

2 Retainability troubleshooting

Retainability Troubleshooting

High Call Drop Rateat RNC levelSRB

Iu008, Iu007 SRB increases

Accessibility AnalysisRNC level

Retainability troubelshootin pannel – drop failure cause (2/2)

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

counter Fcell&RNC 577 VS.IuReleaseReqPs.IuUserPlaneFailure

counter Fcell&RNC 577 VS.IuReleaseReqPs.UlRLCErrSRB

counter Fcell&RNC 577 VS.IuReleaseReqPs.DlRLCErrTRB

counter Fcell&RNC 577 VS.IuReleaseReqPs.UlRLCErrTRB

counter Fcell&RNC 577 VS.IuReleaseReqPs.OamIntervention

counter Fcell&RNC 577 VS.IuReleaseReqPs.UnspecifiedFailure

counter Fcell&RNC 577 VS.IuReleaseReqPs.RepeatedIntegrityCheckFailure

counter Fcell&RNC 577 VS.IuReleaseReqPs.UeGeneratedSignallingConnectionRelease

counter Fcell&RNC 577 VS.IuReleaseReqPs.RadioCnxUeLost

counter Fcell&RNC 577 VS.IuReleaseReqPs.AbnormalConditionTimerRelocExpiry

counter Fcell&RNC 577 VS.IuReleaseReqPs.OtherCause

counter Fcell&RNC 577 VS.IuReleaseReqPs.DlRLCErrSRB

counter Fcell&RNC 577 VS.IuReleaseReqPs.T360Expiry

metric Fcell&RNC 50_HO3G2G024_R%Cs Number of CS calls dropped due to 3G2G HHO%Cs%50_HO3G2G024_R

Page 230: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 22

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 22

2 Retainability troubleshooting

Retainability Troubleshooting Chart: Failure Drop cause

Retainability Analysis –RNC level

CS High Call drop rate at RNC level PS High Call drop rate at RNC level

AbnormalConditionTimerRelocExpiryRadioConnection

WithUeLostDlRLCErrSRBDlRLCErrTRB UlRLCErrSRBUlRLCErrTRB

RepeatedIntegrityCheckFailure

UeGeneratedSignalling

ConnectionRelease

IuUserPlaneFailure

OAM Intervention

No action

Counters: #576*, 577* (Iureleaserequest CS/PS)

Integrity Analysis

CTg analisys

Blackberry issue?CTg to check

Valid for CS/PS

3g 2g mobility analysis

UnspecifiedFailure

Actions: Check TX

links, HW, etc

� Two Analysis

•Distribution per failure cause

•Top N worst cells for the causes that have more weight in the distribution

Capacity AnalysisCPU PMCRAB

DL/UL RF analysisDL BLER analysis

Stability AnalysisPCM, RNC

Node BAlarm correlation?

Bad DL BLER?RB reconfiguration

success rate decrease?Quality Analysis

SHO failure metric increase?RL036, RL037

SHO analysis

Failures in radio link

reconfiguration?SRLR parametersCapacity analysis

#0008 – all failures

It can be correlated wtihRL failure indication

T360 expiry

Abnormal resource releases

To correlate with Abnormal release counters

Note: RLC error on CS calls is only possible forSRB

RLC is in transparent mode so there is no way to detect error with CS

TRB. Only the associated CS SRB can detected issue at RLC layer

Page 231: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 23

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 23

Self-Assessment on the Objectives

� Please be reminded to fill in the formSelf-Assessment on the Objectivesfor this module

� The form can be found in the first partof this course documentation

Page 232: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 5 � Page 24

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Retainibility Monitoring & Troubleshooting Section 5 �Page 24

End of Module

Page 233: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 1

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

Do not delete this graphic elements in here:

All Rights Reserved © Alcatel-Lucent 2007

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

6 3FL12921AAAAWBZZA Edition 1

Section 6Mobility Monitoring &

Troubleshooting

Page 234: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 2

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 2

Blank Page

This page is left blank intentionally

Second editionEL ABED, Achrafe2007-10-2002

First editionEL ABED, Achrafe2007-08-2401

RemarksAuthorDateEdition

Document History

Page 235: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 3

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 3

Objectives

� At the end of this module, you will be able to:

� Describe the mobility metric family

� Illustrate the call flows associated with the metric family

� Identify counters and locate them in the call flow procedure

� Define metrics and recognize its key counters

� Analyze each metric

Page 236: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 4

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 4

Objectives [cont.]

This page is left blank intentionally

Page 237: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 5

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 5

Table of Contents

Switch to notes view!Page

1 Mobility Overview 7KPIs families Reminder 8Mobility overview 9

2 SHO Monitoring and Troubleshooting 10SHO: Active Set Update 11SHO main metrics 12SHO Troubleshooting Chart 13SHO Troubleshooting Chart 14

3 HHO Monitoring and Troubleshooting 153G-2G CS Handover Success: Counters 163G2G Global CS HHO Success Rate 173G-2G CS Handover Preparation Success 183G-2G CS HO Preparation Success 193G-2G CS Handover Preparation Failure 203G-2G CS Handover Failure: Exercise 213G-2G CS HO Preparation Failure Rate 223G-2G CS Handover Execution Success 233G-2G CS Handover: FDDCell Counter Tree 243G-2G CS HO Execution Success Rate 253G-2G CS Handover Execution Failure 263G-2G CS HO Execution Failure Rate (2G synchronization failure) 273G-2G CS HO Execution Failure Rate (2G synchronization failure) 283G-2G CS HO Execution Failure Rate (call lost) 293G-2G CS HO Execution Failure Rate (call lost) 303G-2G CS HO Execution Failure Analysis 313G-2G PS Handover Success: Counters 323G-2G PS Handover Execution Failure (2G synchronization failure) 333G-2G PS HO Execution Failure Rate (2G synchronization failure) 343G-2G PS HO Execution Failure Rate (2G synchronization failure) 353G 2G analysis 363G 2G monitoring 37CS Mobility Monitoring & Troubleshooting Panel 38PS Mobility Monitoring & Troubleshooting Panel 39Mobility Monitoring -Others 40Mobility Troubleshooting counters 41CS 3G 2G Mobility Analysis & Troubleshooting 42CS 3G 2G Mobility Analysis & Troubleshooting 43CS 3G 2G Mobility Analysis & Troubleshooting 44Action to improve the Preparation phase 45Actions to improve the Execution phase 46Self-Assessment on the Objectives 47End of Module 48

Page 238: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 6

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 6

Table of Contents [cont.]

Switch to notes view!

This page is left blank intentionally

Page 239: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 7

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 7

1 Mobility Overview

Page 240: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 8

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 8

1 Mobility Overview

KPIs families Reminder

Network Accessibility

NetworkRetainability

NetworkQuality

NetworkTraffic

NetworkCongestion

Counter based KPIs

Capacity/

Load

Call ProfileHSxPA

RRM

NetworkMobility

Mobility monitoring 3G-3G

Family TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

Mobility_3G3G metric Fcell&RNC 50_HO3G3G002_CR%Cs Incoming 3G3G HHO Preparation Success Rate%Cs%50_HO3G3G002_CR

Mobility_3G3G metric RNC 50_HO3G3G003_R%Cs Incoming 3G3G HHO Execution Success Rate%Cs%50_HO3G3G003_R

Mobility_3G3G metric Fcell&RNC 50_HO3G3G004_CR%Ps Incoming 3G3G HHO Preparation Success Rate%Ps%50_HO3G3G004_CR

Mobility_3G3G metric RNC 50_HO3G3G005_R%Ps Incoming 3G3G HHO Execution Success Rate%Ps%50_HO3G3G005_R

Mobility_3G3G metric RNC 50_HO3G3G007_R%Cs Outgoing 3G3G HHO Preparation Success Rate%Cs%50_HO3G3G007_R

Mobility_3G3G metric RNC 50_HO3G3G007_R%Ps Outgoing 3G3G HHO Preparation Success Rate%Ps%50_HO3G3G007_R

Mobility_3G3G metric RNC 50_HO3G3G008_R%Cs Outgoing 3G3G HHO Execution Success Rate%Cs%50_HO3G3G008_R

Mobility_3G3G metric RNC 50_HO3G3G009_R%Ps Outgoing 3G3G HHO Execution Success Rate%Ps%50_HO3G3G009_R

Mobility_3G3G metric Fcell&RNC 50_HO3G3G010_CR 3G3G HHO Inter PLMN Outgoing Success Rate%50_HO3G3G010_CR

Mobility_3G3G metric Fcell&RNC 50_HO3G3G011_CR 3G3G HHO Intra RNC Outgoing Failure Rate%50_HO3G3G011_CR

Mobility_3G3G metric Fcell&RNC 50_HO3G3G012_CR 3G3G HHO Intra RNCIncoming Failure Rate%50_HO3G3G012_CR

Mobility_3G3G metric Fcell&RNC 50_HO3G3G013_CR 3G3G HHO Inter RNC Outgoing Without iuR Success Rate%50_HO3G3G013_CR

Mobility_3G3G metric Fcell&RNC 50_HO3G3G014_CR 3G3G HHO Inter RNC HHO Incoming Without iuR Success Rate%50_HO3G3G014_CR

Mobility_3G3G metric RNC 50_HO3G3G015_R Ratio of incoming SRNS relocations%50_HO3G3G015_R

Mobility_3G3G metric RNC 50_HO3G3G016_R Ratio of outgoing SRNS relocations%50_HO3G3G016_R

Mobility_3G3G metric RNC 50_TRS001_C IntraRnc Incoming Connection Attempts%50_TRS001_C

Mobility_3G3G metric RNC 50_TRS002_C IntraRnc Outgoing Connection Attempts%50_TRS002_C

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_HO3G2G002_C%Ps 3G2G HHO Execution Failure Rate on 2G%Ps%50_HO3G2G002_C

metric RNC 50_HO3G2G003_R%Cs 3G2G HHO CS Detection radio%Cs%50_HO3G2G003_R

metric RNC 50_HO3G2G003_R%Ps 3G2G HHO PS Detection radio%Ps%50_HO3G2G003_R

metric RNC 50_HO3G2G018_R%Cs 3G2G HHO Preparation Failure Rate%Cs%50_HO3G2G018_R

metric RNC 50_HO3G2G020_R%Cs 3G2G HHO Execution Success Rate%Cs%50_HO3G2G020_R

3G-2G Family

Page 241: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 9

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 9

1 Mobility Overview

Mobility overview

� The Network Mobility analysis consists of:

� In connection mode:

�3G2G Mobility analysis: The 3G2G Mobility analysis aims at evaluating the inter

RAT (3G to 2G) HO performance results and at indicating where are the failures

in the 2G or in the 3G

�3G3G Mobility analysis:

� SHO Mobility analysis: The SHO Mobility analysis estimate if the SHO is efficiently used

and so avoid that calls are dropped

� Other feature monitoring, like Traffic segmentation, inter frequency 3g3g ho, call

redirection, etc…

� In idle mode:

�Mobile traces.

� Study RRC counters/RRC transitions (RRC panel)

� It’s also necessary to divide into CS and PS domain.

Page 242: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 10

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 10

2 SHO Monitoring and Troubleshooting

Page 243: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 11

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 11

2 SHO Monitoring and Troubleshooting

SHO: Active Set Update

Active Set Update

Measurement Report (event)

#415 successful Active Setup Update procedure

UE Node B RNC

Active Set Update Complete

SUCCESS

FAILURE

Active Set Update

Measurement Report (event)

#402 unsuccessfulActive Setup Update procedure

UE Node B RNC

Active Set Update FailureActive Set Update

Measurement Report (event)

UE Node B RNC

No answer from UE

FDDCell Counters

VS.RrcActiveSetUpdateCompleteProcedure #415: This measurement provides the number of successful RRC Active Set Update procedures, for which the cell is the in the list of the active set before or after the Active Set Update execution (even if it is added or removed due to this procedure). It is incremented once per procedure, whatever the number of cells.

VS.RrcActiveSetUpdateUnsuccess #402: This measurement provides the number of failed RRC ACTIVE SET UPDATE procedures managed by a RNC, for each cell controlled by the RNC. The measurement attached to a given cell is incremented for a failed addition or removal of this cell from the active set.

Screening:

� 0 : RRC ACTIVE SET UPDATE FAILURE reception

� 1 : Time-out

Page 244: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 12

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 12

2 SHO Monitoring and Troubleshooting

SHO main metrics

SHO Failure Rate SHO Failure Rate #402.[0,1]

#402.[0,1] + #415=

SHO007FDDCell metric

#25.[0].Avg + 2x(#25.[1].Avg+#25.[2].Avg) + 3x(#25.[3].Avg+…) + …

#25.[all screenings].Avg=

RL016Reference FDDCell metric

� Other counters and metrics of the SHO panel bellow could be used for SHO troubleshooting:� It includes inter & intra SHO information�Failure cause identification�Counters to identify services

Mean Sector per User

� #0025 VS.UeWithNRadioLinksEstCellsBts[Number of RL screenings] . This measurement

provides the average number of mobiles having N Radio-Links in their Active Set, during an

observation period.

A set of subcounters screened on: Number of radio links

SHO monitoring & troubleshooting panel (1/2)

Family TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

inter SHO counter Fddcell 407 VS.RrcActiveSetUpdateUnsuccessNeighbRnc.RrcActiveSetUpdateFailure

inter SHO counter Fddcell 407 VS.RrcActiveSetUpdateUnsuccessNeighbRnc.Timeout

intra SHO counter Fddcell 402 VS.RrcActiveSetUpdateUnsuccess.RrcActiveSetUpdateFailure

intra SHO counter Fddcell 415 VS.RrcActiveSetUpdateCompleteProcedure

intra SHO counter Fddcell 418 SHO.SuccRLAddUESide

intra SHO counter Fddcell 418 SHO.SuccRLDelUESide

Iur RL counter Fddcell 1302 VS.IurDrncRadioLinkSetupUnsuccess.Unspecified

Iur RL counter Fddcell 1302 VS.IurDrncRadioLinkSetupUnsuccess.NoRadioResource

Iur RL counter Fddcell 1302 VS.IurDrncRadioLinkSetupUnsuccess.NbapRefusal

Iur RL counter Fddcell 1302 VS.IurDrncRadioLinkSetupUnsuccess.RequestedConfigurationNotSupport

Iur RL counter Fddcell 1304 VS.IurDrncRadioLinkAdditionUnsuccess.Unspecified

Iur RL counter Fddcell 1304 VS.IurDrncRadioLinkAdditionUnsuccess.NoRadioResource

Iur RL counter Fddcell 1304 VS.IurDrncRadioLinkAdditionUnsuccess.NbapRefusal

Page 245: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 13

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 13

2 SHO Monitoring and Troubleshooting

SHO Troubleshooting Chart

SHO Mobility AnalysisRNC level

High SPU

RL016

SHO Analysis RNC level

Check SHO algorithm Parameters settings / RF tuning

Low SPU

RL016

RL036, RL037- RNC levelSHO007- cell level

� Issue characterization: � Can it affect certain/all services (CS, PS,etc)� Certain/all Network elements, Top N cells� Certain/all period of time, since when� Certain failure causes� After certain event (upgrade, feature activation, configuration changes in Iur,

repartentings?

•Besides the following counters can be checked

#402 VS.RrcActiveSetUpdateUnsuccess#407 VS.RrcActiveSetUpdateUnsuccessNeighbRnc#415 VS.RrcActiveSetUpdateCompleteProcedure#416 VS.RrcConnectionSetup#418 SHO#421 VS.ActiveSetUpdatePerRnc#422 VS.RrcActiveSetUpdateSuccessNeighbRnc

SHO monitoring & troubleshooting panel (2/2)

Family TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

Iur RL counter Fddcell 1304 VS.IurDrncRadioLinkAdditionUnsuccess.RequestedConfigurationNotSupport

Iur RL counter Fddcell 1304 VS.IurDrncRadioLinkAdditionUnsuccess.LackCidIur

Iur RL counter Fddcell 1304 VS.IurDrncRadioLinkAdditionUnsuccess.LackBwthIur

Iur RL counter Fddcell 1304 VS.IurDrncRadioLinkAdditionUnsuccess.LackCidIub

Iur RL counter Fddcell 1304 VS.IurDrncRadioLinkAdditionUnsuccess.LackBwthIub

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.RadioLinkSetupFailure

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.Timeout

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.RrmRefusal

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.Unused

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.LackOfNodeBDlProcessingResources

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.LackOfNodeBUlProcessingResources

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.LackCidIub

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.LackBwthIub

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.INodeRefusal

RL counter Fddcell 4 VS.RadioLinkAdditionUnsuccess.RadioLinkAdditionFailure

RL counter Fddcell 4 VS.RadioLinkAdditionUnsuccess.Timeout

RL counter Fddcell 4 VS.RadioLinkAdditionUnsuccess.RrmRefusal

RL counter Fddcell 4 VS.RadioLinkAdditionUnsuccess.INodeRefusal

RL counter Fddcell 4 VS.RadioLinkAdditionUnsuccess.LackOfNodeBDlProcessingResources

RL counter Fddcell 4 VS.RadioLinkAdditionUnsuccess.LackOfNodeBUlProcessingResources

RL metric Fcell&RNC 50_RL036_CR Radio Link Setup Blocking Rate%50_RL036_CR

RL metric Fcell&RNC 50_RL037_CR Radio Link Addition Blocking Rate%50_RL037_CR

SHO counter Fddcell 402 VS.RrcActiveSetUpdateUnsuccess.Timeout

SHO counter Fddcell 406 VS.RrcActiveSetUpdateSuccessNeighbRnc

SHO metric Fcell&RNC 50_SHO005_CR Number of SHO Radio Link requests%50_SHO005_CR

SHO metric Fcell&RNC 50_SHO006_CR Number of SHO Radio Link Successfully established%50_SHO006_CR

SHO metric Fcell&RNC 50_SHO007_CR SHO Failure Rate%50_SHO007_CR

Page 246: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 14

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 14

RRM Capacity AnalysisCell level

50_RL037_CRRL Addition

Blocking Rate

RL AdditionUnsuccess

[failure causes]

•Top worst cells

Few cells?

Correlate with Node B alarms

2 SHO Monitoring and Troubleshooting

SHO Troubleshooting Chart

SHO AnalysisRNC level

RL036, RL037- RNC levelSHO007- cell level

CEM & Iub Capacity AnalysisNode B level

RRM Capacity Analysis Cell level

50_RL036_CRRL Setup

Blocking Rate

RL SetupUnsuccess

[failure causes]

•Top worst cells

High Iur Radio link failures(setup/addition)

All cells? Or set of cells

Inter RNC SHO analysis

Capacity analysis cell level

Check configuration for the set of cellsCorrelate with events that affect Iur:

i.e configuration changes like reparenting

Yes

No

SHO monitoring & troubleshooting panel (2/2)

Family TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

Iur RL counter Fddcell 1304 VS.IurDrncRadioLinkAdditionUnsuccess.RequestedConfigurationNotSupport

Iur RL counter Fddcell 1304 VS.IurDrncRadioLinkAdditionUnsuccess.LackCidIur

Iur RL counter Fddcell 1304 VS.IurDrncRadioLinkAdditionUnsuccess.LackBwthIur

Iur RL counter Fddcell 1304 VS.IurDrncRadioLinkAdditionUnsuccess.LackCidIub

Iur RL counter Fddcell 1304 VS.IurDrncRadioLinkAdditionUnsuccess.LackBwthIub

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.RadioLinkSetupFailure

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.Timeout

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.RrmRefusal

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.Unused

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.LackOfNodeBDlProcessingResources

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.LackOfNodeBUlProcessingResources

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.LackCidIub

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.LackBwthIub

RL counter Fddcell 2 VS.RadioLinkSetupUnsuccess.INodeRefusal

RL counter Fddcell 4 VS.RadioLinkAdditionUnsuccess.RadioLinkAdditionFailure

RL counter Fddcell 4 VS.RadioLinkAdditionUnsuccess.Timeout

RL counter Fddcell 4 VS.RadioLinkAdditionUnsuccess.RrmRefusal

RL counter Fddcell 4 VS.RadioLinkAdditionUnsuccess.INodeRefusal

RL counter Fddcell 4 VS.RadioLinkAdditionUnsuccess.LackOfNodeBDlProcessingResources

RL counter Fddcell 4 VS.RadioLinkAdditionUnsuccess.LackOfNodeBUlProcessingResources

RL metric Fcell&RNC 50_RL036_CR Radio Link Setup Blocking Rate%50_RL036_CR

RL metric Fcell&RNC 50_RL037_CR Radio Link Addition Blocking Rate%50_RL037_CR

SHO counter Fddcell 402 VS.RrcActiveSetUpdateUnsuccess.Timeout

SHO counter Fddcell 406 VS.RrcActiveSetUpdateSuccessNeighbRnc

SHO metric Fcell&RNC 50_SHO005_CR Number of SHO Radio Link requests%50_SHO005_CR

SHO metric Fcell&RNC 50_SHO006_CR Number of SHO Radio Link Successfully established%50_SHO006_CR

SHO metric Fcell&RNC 50_SHO007_CR SHO Failure Rate%50_SHO007_CR

Page 247: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 15

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 15

3 HHO Monitoring and Troubleshooting

Page 248: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 16

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 16

3 HHO Monitoring and Troubleshooting

3G-2G CS Handover Success: Counters

UE Node B RNC CN

Handover from UTRAN Command

BSS

Relocation Command

Radio Lnk Del. req.Radio Lnk Del. resp.

Relocation Required

Physical information

Measurement Report

Handover Access

Handover CompleteIu Release Command“successful 3G to 2G

relocation”

Iu Release Complete

Decision for 3G->2G HHO

Released

….#164[0] 3G to 2G HO detection

#167[0], #168[0]successful 3G to 2G outgoing handovers

Reference FDDCell counters

preparation

execution

#505[1] Iu Release Command CS

� VS.3gto2gHoDetectionFromFddcell #164: Number of 3G TO 2G handover requests per cell. This measurement provides the number of RRM decisions for a 3G TO 2G handover performed by a RNC, screened by reference cell from which the UEs have left the 3G Network, when these cells are controlled by the considered RNC. This measurement considers both CS and PS handovers.

� Screening:

� 0 --> Rescue CS 2 --> Service

� 1 --> Rescue PS 3 --> No resource available (CAC failure)� VS.3gto2gOutHoSuccess #167: This measurement provides the number of successful 3G to 2G outgoing

Handovers. It is incremented at the reception of an Iu_Release_Command with cause « Successful 3G to 2G Relocation »

� Screening:

• Sub-Counter #0 : rescue CS • Sub-Counter #1 : rescue PS• Sub-Counter #2 : service CS • Sub-Counter #3 : Service PS• Sub-Counter #4 : No resource available CS (CAC failure) • Sub-Counter #5 : No resource

available PS (CAC failure)� VS.IuReleaseCommandCs - #505: This measurement provides the total number of Iu Release Command

CS received by the RNC. It is incremented at the reception of an Iu_Release_Command with any cause value.

� Screening: per Iu Release Command cause

� 0 : Normal end of communication (3GPP RANAP cause 83)

� 1 : Successful 3G/2G relocation (3GPP RANAP cause 11)

� 2 : UTRAN generated reason (3GPP RANAP cause 15 or Iu_Release_Request sent by RNC)

� 3 : Other cause (all other 3GPP RANAP causes)

� 4 : Relocation Cancelled (3GPP RANAP cause 10)

� 5 : O&M Intervention (3GPP RANAP cause 113)

� 6 : Unspecified Failure (3GPP RANAP cause 115)

� 7 : User Inactivity (3GPP RANAP cause 16)

� 8 : No Remaining RAB (3GPP RANAP cause 31)

� 9 : Successful 3G/3G relocation (3GPP RANAP cause 11)

Page 249: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 17

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 17

3 HHO Monitoring and Troubleshooting

3G2G Global CS HHO Success Rate

� The 3G2G Global CS HHO success rate evaluates success rate of the overall 3G2G CS HHO procedure by considering all the cases of failures (3G or 2G failures).

CS 3G-2G HO Execution Success Rate

CS 3G-2G HO Execution Success Rate

#167.[0]

#164.[0]=

HO3G2G019Reference FDDCell metric

Global 3G-2G CS HO success rate

Global 3G-2G CS HO success rate

∑#167.[0] + ∑neigborRNC(#168.[0])

∑cell(#164.[0]) + ∑neigborRNC(#165.[0])=

RNC metric

The metric is based on the following counters:

� The number of Iu release command (Successful 3G2G Relocation) (#505),

� The number of RRM decisions for 3G to 2G handovers (#109 and #110).

If 3G2G Global CS HHO success rate is very low, then investigate the steps preparation or

execution based on the previous metrics and determine the failure causes.

The 3G2G Global CS HHO success rate can be approximated at cell level based on the following

counters (w/o the RRM decisions for 3G to 2G handovers when the cell is not managed by the

SRNC):

� The number of successful outgoing 3g-2G handovers (#134),

� The number of RRM decisions for 3G to 2G handovers (#109).

Page 250: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 18

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 18

3 HHO Monitoring and Troubleshooting

3G-2G CS Handover Preparation Success

UE Node B RNC CN

Handover from UTRAN Command

BSS

Relocation Command

Relocation Required

Measurement Report

….

#164[0]; #165[0] 3G to 2G HO detection

#556[2]Iu relocation required

#557[2] Iu relocation command

{#154[0] - #159[0]}HO from UTRAN command

Reference FDDCell counter

RNC counter

RNC counter

Reference FDDCell counter

� #154 VS.RrcHoFromUtranCmdTrigByEcNo� #155 VS.RrcHoFromUtranCmdTrigByEcNoNRnc� #156 VS.RrcHoFromUtranCmdTrigByRscp� #157 VS.RrcHoFromUtranCmdTrigByRscpNRnc� #158 VS.RrcHoFromUtranCmdTrigRnc� #159 VS.RrcHoFromUtranCmdTrigRncNrnc� #164 VS.3gto2gHoDetectionFromFddcell� #165 VS.3gto2gHoDetectionFromFddcellNeighbRnc� #556 VS.IuRelocationRequired� #557 VS.IuRelocationCommands

Page 251: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 19

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 19

3 HHO Monitoring and Troubleshooting

3G-2G CS HO Preparation Success

� The main metrics used to monitor the CS HHO (3G to 2G and 3G to 3G) preparation phase on the target side are:

� Failures from the target network when allocating the resources for the mobile (Relocation Preparation Failure).

� Failures from 2G due to wrong neighboring definition of 2G in 3G & opposite.

� Call dropped after Relocation Required & before HO from UTRAN Command.

3G2G HHO CS radio detection3G2G HHO CS radio detection #164.[0] + #165.[0]=

RNC metric

3G2G HHO CS radio detection3G2G HHO CS radio detection #164.[0]=

HO3G2G003Reference FDDCell metric

The RNC metric is based on the following counters:

� Number of Iu Relocation Required in CS domain (#549.[0]),

� Number of Iu Relocation Command in CS domain (#550.[0]).

The Reference FDDCell metric is based on the following counters:

� Number of 3G to 2G CS HHO detection (#109.[0]),

� Number of HO from UTRAN Command sent to UE (#101.[0]).

Page 252: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 20

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 20

#???#568[2] Relocation cancel

3 HHO Monitoring and Troubleshooting

3G-2G CS Handover Preparation Failure

Relocation Required

Measurement Report

Relocation Cancel

TRELOCprepexpiry

Relocation Failure due to TRELOCprep timer expiry

Decision for HHO

Relocation Prep. Failure

Relocation Required

Measurement Report

Decision for HHOHandover failure on the 2G side

Handoverfailure

Relocation Preparation Failure

UE Node B RNC CN BSS

EXERCISE: Find the two counters in the catalogue

#???

#???#558[5-9] Relocation command failure

#???

1st

case

2nd

case

� TRELOCprep = Timer RELOcation preparation

Page 253: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 21

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 21

3 HHO Monitoring and Troubleshooting

3G-2G CS Handover Failure: Exercise

Relocation Required

Measurement Report Decision for HHO

UE Node B RNC CN BSS

EXERCISE:

Find the main differences between counters #558 and #135 ?

What will #558 be used for ?

Page 254: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 22

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 22

3 HHO Monitoring and Troubleshooting

3G-2G CS HO Preparation Failure Rate

3G-2G CS HO Preparation failure rate3G-2G CS HO Preparation failure rate#558.[5-9]

#556.[2]=

RNC metric HO3G2G018

3G-2G CS+PS HO Preparation failure rate3G-2G CS+PS HO Preparation failure rate#135[0]

#164[0,1]=

Reference FDDCell metrics Can not be provided for CS only

VS.3g2gOutHoFailure #135: This measurement provides the number of failed 3G to 2G outgoing Handovers from a cell.

Condition:

Reception of RANAP Relocation Preparation Failure or RANAP Relocation Cancel or

RANAP Iu Release Command or RRC HO From UTRAN Failure or RRC Cell Change Order From UTRAN Failure.

Screening:

� 0 : Relocation Preparation Failure or Relocation Preparation Cancellation

� 1 : Relocation Completion Failure

� 2 : CS Failure in the radio procedures

� 3 : PS Failure in the radio procedures

� 4 : Unexpected cause

VS.3gto2gHoDetectionFromFddcell #109: Number of 3G TO 2G handover requests per cell. This measurement provides the number of RRM decisions for a 3G TO 2G handover performed by a RNC, screened by reference cell from which the UEs have left the 3G Network, when these cells are controlled by the considered RNC. This measurement considers both CS and PS handovers.

Screening:

0 --> Rescue CS

1 --> Rescue PS

2 --> Service CS

3 --> Blind speech redirection

4 --> Non blind speech redirection

Page 255: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 23

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 23

#505[1] Iu Release Command CS

#167[0]successful 3G to 2G outgoing handovers

3 HHO Monitoring and Troubleshooting

3G-2G CS Handover Execution Success

UE Node B RNC CN

Handover from UTRAN Command

BSS

Relocation Command

#154[0] - #159[0]HO from UTRAN command

Reference FDDCell counters

Radio Lnk Del. req.Radio Lnk Del. resp.

Physical informationHandover Access

Handover CompleteIu Release Command“successful 3G to 2G

relocation”

Iu Release CompleteReleased

Page 256: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 24

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 24

3 HHO Monitoring and Troubleshooting

3G-2G CS Handover: FDDCell Counter Tree

Preparation failure#164[0] – Σ[#154-#159]

VS.3gto2gHoDetectionFromFddcell

VS.RrcHoFromUtranCommand

Request#164[0]

Execution failureΣ[#154-#159]- #167[0,2,4]

Success#167[0,2,4]

VS.RadioBearerSetupUnsuccess

HO from UTRAN Failure#160[0]

HHO dropΣ[#154-#159]- #167[0,2,4] - #160[0]

AttemptΣ[#154-#159]

Page 257: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 25

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 25

3 HHO Monitoring and Troubleshooting

3G-2G CS HO Execution Success Rate

Σcell(#167.[0,2,4]) + ΣneighborRNC (#168.[0,2])

Σ#154 + Σ#155 + Σ#156 + Σ#157 + Σ#158 + Σ#159=

#167.[0,2,4]

Σ#154 + Σ#156 + Σ#158=

HO3G2G020

RNC metric

Reference FDDCell metric

3G-2G CS HO Execution Success Rate

3G-2G CS HO Execution Success Rate

Page 258: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 26

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 26

3 HHO Monitoring and Troubleshooting

3G-2G CS Handover Execution Failure

Handover from UTRAN cmdRelocation Command

Handover failure on the target system

Handover from UTRAN FailureRelocation Cancel

UE fails to connect to 2G and reverts to 3G

#160, #161 HO From UTRAN Failure

UE Node B RNC CN - CS BSS

1st

case

HO Request Ack

2nd

case

Handover from UTRAN cmdRelocation Command

UE fails to connect to 2G and fails to reverts to 3G

HO Request Ack

Iu release timer

Iu Release Request

HHO Drop

expiry

Reference FDDCell counter

Page 259: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 27

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 27

3 HHO Monitoring and Troubleshooting

3G-2G CS HO Execution Failure Rate (2G synchronization failure)

� If the UE can not synchronize with the 2G target network during the 3G2G HHO execution phase, the UE sends the HO from UTRAN Failuremessage to the RNC to come back on the 3G network.

� The CS 3G2G HHO execution failure rate (2G synchonization failure)metric is proposed to evaluate the 2G target cell synchronization failure.

� If this metric is high => check the target 2G Network and the 2G cell identity in the 3G OMC

Page 260: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 28

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 28

3 HHO Monitoring and Troubleshooting

3G-2G CS HO Execution Failure Rate (2G synchronization failure)

CS 3G-2G HO Execution Failure Rate(2G synchronization failure)

CS 3G-2G HO Execution Failure Rate(2G synchronization failure)

Σcell(#160) + ΣneighborRNC(#161)

Σ[#154-#159] =

RNC metric HO3G2G002-CS

CS 3G-2G HO Execution Failure Rate(2G synchronization failure)

CS 3G-2G HO Execution Failure Rate(2G synchronization failure)

#160

Σ#154 + Σ#156 + Σ#158=

Reference FDDCell metric HO3G2G002-CS

Reference FDDCell metric:CS 3G-2G HO Execution Failure Rate (2G synchronization failure) = ΣVS.RrcHoFromUtranFailure /

ΣVS.RrcHoFromUtranCmdTrigByEcNo + Σ VS.RrcHoFromUtranCmdTrigByRscp + ΣVS.RrcHoFromUtranCmdTrigRnc

RNC Metric:CS 3G-2G HO Execution Failure Rate (2G synchronization failure) =

(ΣVS.RrcHoFromUtranFailure + ΣVS.RrcHoFromUtranFailureNeighbRnc ) / ΣVS.RrcHoFromUtranCmdTrigByEcNo + ΣVS.RrcHoFromUtranCmdTrigByEcNoNrnc + ΣVS.RrcHoFromUtranCmdTrigByRscp + ΣVS.RrcHoFromUtranCmdTrigByRscpNrnc+ΣΣΣΣVS.RrcHoFromUtranCmdTrigRnc + ΣVS.RrcHoFromUtranCmdTrigRncNrnc

Page 261: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 29

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 29

3 HHO Monitoring and Troubleshooting

3G-2G CS HO Execution Failure Rate (call lost)

� If the RNC does not receive the HO from UTRAN Failure RRC message from the UE or the Iu release command with the cause “successful 3g2g relocation” from the CN, there is failure at 3G side (the call is dropped during the 3G2G HHO).

� The CS 3G2G HHO execution failure rate (3G side) metric is proposed to evaluate the calls dropped during the 3G2G CS HHO.

� High 3G2G HHO CS execution failure rate (3G side) performance =>determine the worst cells of this RNC and the worst hours of the day.

Page 262: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 30

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 30

3 HHO Monitoring and Troubleshooting

3G-2G CS HO Execution Failure Rate (call lost)

= Σ#154 + Σ#156 + Σ#158 - #160.[0] - #505.[1]

Reference FDDCell metric HO3G2G024

#167.[0,2,4]

= Σ#154 + Σ#156 + Σ#158 - #160.[0]= 1 -

3G-2G CS HO which leads either to a Success or to a Drop

Reference FDDCell metric HO3G2G022

Nb of CS calls lostduring 3G2G HO

CS 3G-2G HO Execution Failure Rate (call lost)

1. The number of calls lost during a 3G-2G HO is:

Number of HO Command sent to UE – Number of HO Failure received from UE

� – Number of HO success to 2G

2. CS 3g-2G HO Execution Failure rate (call lost):

The HO Failures to 2G with UE successfully reverting to 3G are not taken into account.

Page 263: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 31

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 31

3 HHO Monitoring and Troubleshooting

3G-2G CS HO Execution Failure Analysis

RF Analysis of Target 2G neighbor cells

Check parameters of 3G-2G CS HO radio algorithms

3G-2G CS HO Execution Success Rate

2G synchronization failure Call lost

� The RRC Connection analysis aims at evaluating the most common RRC Connection failures in

case of degradation of the RRC Connection success rate.

� When the main RRC failure causes are identified, then determine the main cells and the RRC

failure peak periods.

� Moreover, the top 10 worst cells (managed by the RNC) should be identified by considering the

lowest RRC Connection success rate with a representative number of RRC Connection

requests.

� The next step consists of looking at the RRC connection failure causes and analyze them.

Page 264: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 32

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 32

3 HHO Monitoring and Troubleshooting

3G-2G PS Handover Success: Counters

Cell Change Order from UTRAN

Radio Lnk Del. Req.Radio Lnk Del. Resp.

RA update response

Measurement Report

RA update request

Iu Release Command

Iu Release Complete

Decision for HHO

….

#164[1]3G to 2G HO detection

#167[1,3,5]successful 3G to 2G outgoing handovers SRNS Data Fwd Cmd

UE Node B RNC CN - CS BSS

#506[1] Iu Release Command PS

Reference FDDCell counters

� VS.IuReleaseCommandPs #506: Number of Iu Release Commands on Iu PS. This measurement

provides the number of RANAP “IU RELEASE COMMAND” messages received by the RNC on Iu PS.

� Screening:

� 0 : Normal end of communication (3GPP RANAP cause 83)

� 2 : UTRAN generated reason (3GPP RANAP cause 15 or

� Iu_Release_Request sent by RNC)

� 3 : Other cause (all other 3GPP RANAP causes)

� 4 : Relocation Cancelled (3GPP RANAP cause 10)

� 5 : O&M Intervention (3GPP RANAP cause 113)

� 6 : Unspecified Failure (3GPP RANAP cause 115)

� 7 : User Inactivity (3GPP RANAP cause 16)

� 8 : No Remaining RAB (3GPP RANAP cause 31)

� 9 : Successful 3G/3G relocation (3GPP RANAP cause 11)

Page 265: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 33

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 33

3 HHO Monitoring and Troubleshooting

3G-2G PS Handover Execution Failure (2G synchronization failure)

Cell Change Order from UTRAN

Measurement ReportDecision for

HHO

#162Cell Change Order from UTRAN

#163Cell Change Order from UTRAN FailureCell Change Order from UTRAN

Failure

UE Node B RNC

Reference FDDCell counters

IRATHO.AttOutPSUTRAN - #162

the number of RRC CELL CHANGE ORDER FROM UTRAN messages (3G to 2G handover

for PS only) emitted by an RNC, acting as serving RNC, for each cell controlled by this RNC.

The reference cell of the involved UE has to be under the control of this RNC.

A set of subcounters screened on: HO reason for which the rrc

CELL_CHANGE_ORDER_FROM_UTRAN message is sent

• Sub-Counter #0 : Rescue PS

• Sub-Counter #1 : Service PS

• Sub-Counter #2 : No resource available (CAC failure)

IRATHO.FailOutPSUTRAN - #163

the number of RRC CELL CHANGE ORDER FROM UTRAN FAILURE messages received by

a RNC (3G to 2G handover for PS only), for each cell controlled by the RNC and acting as a

reference cell, i.e. an involved UE in the procedure is served by a RNC which is the controlling

RNC of its reference cell.

A set of subcounters screened on: HO reason for which the rrc

CELL_CHANGE_ORDER_FROM_UTRAN message is sent

• Sub-Counter #0 : Rescue PS

• Sub-Counter #1 : Service PS

• Sub-Counter #2 : No resource available (CAC failure)

Page 266: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 34

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 34

3 HHO Monitoring and Troubleshooting

3G-2G PS HO Execution Failure Rate (2G synchronization failure)

� If the UE cannot synchronize with the 2G target network during the 3G2G HHO execution phase, the UE sends the Cell Change Order from UTRAN Failure message to the RNC to come back on the 3G network.

� The 3G-2G PS HO execution failure rate (2G synchronization failure)metric is proposed to evaluate the 2G target cell synchronization failure.

� If this metric is high => check the target 2G Network and the 2G cell identity in the 3G OMC

Page 267: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 35

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 35

3 HHO Monitoring and Troubleshooting

3G-2G PS HO Execution Failure Rate (2G synchronization failure)

3G-2G HO PS Execution Failure rate(2G synchronization failure)

3G-2G HO PS Execution Failure rate(2G synchronization failure)

Σcell(#163) + ΣneighborRNC(#108.[0])

Σcell(#162) + ΣneighborRNC(#106 .[0])=

RNC metric HO3G2G002-PS

Page 268: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 36

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 36

3 HHO Monitoring and Troubleshooting

3G 2G analysis

� 3G 2G procedure is divided into two phases, preparation and execution.

� 3G2G HO Global metric gives a global view of 3G2G HO procedure (E2E)

� 3G2G HO preparation success rate monitors of the preparation phase on the 2G

side.

� 3G2G Ho execution success rate monitors the execution of the 3G2G HO (from "HO

from UTRAN Command" to the release of the IU interface after the success of the

relocation).

� 3G2G Ho execution success rate (at 3G side) monitors the execution of the 3G2G HO on the

3G side only (without taking into account the cases where the Mobile fails to Synchronize

on the 2G).

Page 269: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 37

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 37

3 HHO Monitoring and Troubleshooting

3G 2G monitoring

Subset of metric of RNC panel

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_HO3G2G002_C%Ps 3G2G HHO Execution Failure Rate on 2G%Ps%50_HO3G2G002_C

metric RNC 50_HO3G2G003_R%Cs 3G2G HHO CS Detection radio%Cs%50_HO3G2G003_R

metric RNC 50_HO3G2G003_R%Ps 3G2G HHO PS Detection radio%Ps%50_HO3G2G003_R

metric RNC 50_HO3G2G018_R%Cs 3G2G HHO Preparation Failure Rate%Cs%50_HO3G2G018_R

metric RNC 50_HO3G2G020_R%Cs 3G2G HHO Execution Success Rate%Cs%50_HO3G2G020_R

Page 270: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 38

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 38

3 HHO Monitoring and Troubleshooting

CS Mobility Monitoring & Troubleshooting Panel

It includes:

• 3G3G metrics

• 3G2G metrics

Family TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

Mobility_3G3G metric Fcell&RNC 50_HO3G3G002_CR%Cs Incoming 3G3G HHO Preparation Success Rate%Cs%50_HO3G3G002_CR

Mobility_3G3G metric RNC 50_HO3G3G003_R%Cs Incoming 3G3G HHO Execution Success Rate%Cs%50_HO3G3G003_R

Mobility_3G3G metric Fcell&RNC 50_HO3G3G004_CR%Ps Incoming 3G3G HHO Preparation Success Rate%Ps%50_HO3G3G004_CR

Mobility_3G3G metric RNC 50_HO3G3G005_R%Ps Incoming 3G3G HHO Execution Success Rate%Ps%50_HO3G3G005_R

Mobility_3G3G metric RNC 50_HO3G3G007_R%Cs Outgoing 3G3G HHO Preparation Success Rate%Cs%50_HO3G3G007_R

Mobility_3G3G metric RNC 50_HO3G3G007_R%Ps Outgoing 3G3G HHO Preparation Success Rate%Ps%50_HO3G3G007_R

Mobility_3G3G metric RNC 50_HO3G3G008_R%Cs Outgoing 3G3G HHO Execution Success Rate%Cs%50_HO3G3G008_R

Mobility_3G3G metric RNC 50_HO3G3G009_R%Ps Outgoing 3G3G HHO Execution Success Rate%Ps%50_HO3G3G009_R

Mobility_3G3G metric Fcell&RNC 50_HO3G3G010_CR 3G3G HHO Inter PLMN Outgoing Success Rate%50_HO3G3G010_CR

Mobility_3G3G metric Fcell&RNC 50_HO3G3G011_CR 3G3G HHO Intra RNC Outgoing Failure Rate%50_HO3G3G011_CR

Mobility_3G3G metric Fcell&RNC 50_HO3G3G012_CR 3G3G HHO Intra RNCIncoming Failure Rate%50_HO3G3G012_CR

Mobility_3G3G metric Fcell&RNC 50_HO3G3G013_CR 3G3G HHO Inter RNC Outgoing Without iuR Success Rate%50_HO3G3G013_CR

Mobility_3G3G metric Fcell&RNC 50_HO3G3G014_CR 3G3G HHO Inter RNC HHO Incoming Without iuR Success Rate%50_HO3G3G014_CR

Mobility_3G3G metric RNC 50_HO3G3G015_R Ratio of incoming SRNS relocations%50_HO3G3G015_R

Mobility_3G3G metric RNC 50_HO3G3G016_R Ratio of outgoing SRNS relocations%50_HO3G3G016_R

Mobility_3G3G metric RNC 50_TRS001_C IntraRnc Incoming Connection Attempts%50_TRS001_C

Mobility_3G3G metric RNC 50_TRS002_C IntraRnc Outgoing Connection Attempts%50_TRS002_C

Page 271: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 39

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 39

3 HHO Monitoring and Troubleshooting

PS Mobility Monitoring & Troubleshooting Panel

Family TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

Mobility_3G2G_PS metric Fcell&RNC 50_RRC003_CR%InterRATRRC Connection Success Rate%InterRAT%50_RRC003_CR

Mobility_3G2G_PS counter Fcell&RNC 0 IRATHO.AttOutPSUTRAN

Mobility_3G2G_PS counter Fcell&RNC 0 IRATHO.FailOutPSUTRAN

Mobility_3G2G_PS counter RNC 106 VS.RrcCellChangeOrderNeighbRnc.RescuePs

Mobility_3G2G_PS counter Fcell&RNC 106 VS.RrcCellChangeOrderNeighbRnc.ServicePs

Mobility_3G2G_PS counter RNC 108 VS.RrcCellChangeOrderFailureNeighbRnc.RescuePs

Mobility_3G2G_PS counter Fcell&RNC 108 VS.RrcCellChangeOrderFailureNeighbRnc.ServicePs

Mobility_3G2G_PS counter Fcell&RNC 506 IRATHO.SuccOutPSUTRAN

Mobility_3G2G_PS counter Fcell&RNC 409/403RRC.AttConnEstab.10 - Intersystem cell re-selection /

RRC.SuccConnEstab.10 - Intersystem cell re-selection

Mobility_3G2G_PS metric RNC 50_HO3G2G001_R%Ps 3G2G HHO Execution Attempts%Ps%50_HO3G2G001_R

Mobility_3G2G_PS metric RNC 50_HO3G2G002_R%Ps 3G2G HHO Execution Failure Rate on 2G%Ps%50_HO3G2G002_R

Mobility_3G2G_PS metric RNC 50_HO3G2G003_R%Ps 3G2G HHO PS Detection radio%Ps%50_HO3G2G003_R

Mobility_3G2G_PS metric RNC 50_HO3G2G014_R%CsVoiceHO3G2G CS per Call%CsVoice%50_HO3G2G014_R

Mobility_3G2G_PS metric RNC 50_HO3G2G015_R%Ps HO3G2G PS per Call%Ps%50_HO3G2G015_R

Page 272: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 40

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 40

3 HHO Monitoring and Troubleshooting

Mobility Monitoring -Others

Family TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

Mobility_3G3G metric Fcell&RNC 50_HO3G3G002_CR%Cs Incoming 3G3G HHO Preparation Success Rate%Cs%50_HO3G3G002_CR

Mobility_3G3G metric RNC 50_HO3G3G003_R%Cs Incoming 3G3G HHO Execution Success Rate%Cs%50_HO3G3G003_R

Mobility_3G3G metric Fcell&RNC 50_HO3G3G004_CR%Ps Incoming 3G3G HHO Preparation Success Rate%Ps%50_HO3G3G004_CR

Mobility_3G3G metric RNC 50_HO3G3G005_R%Ps Incoming 3G3G HHO Execution Success Rate%Ps%50_HO3G3G005_R

Mobility_3G3G metric RNC 50_HO3G3G007_R%Cs Outgoing 3G3G HHO Preparation Success Rate%Cs%50_HO3G3G007_R

Mobility_3G3G metric RNC 50_HO3G3G007_R%Ps Outgoing 3G3G HHO Preparation Success Rate%Ps%50_HO3G3G007_R

Mobility_3G3G metric RNC 50_HO3G3G008_R%Cs Outgoing 3G3G HHO Execution Success Rate%Cs%50_HO3G3G008_R

Mobility_3G3G metric RNC 50_HO3G3G009_R%Ps Outgoing 3G3G HHO Execution Success Rate%Ps%50_HO3G3G009_R

Mobility_3G3G metric Fcell&RNC 50_HO3G3G010_CR 3G3G HHO Inter PLMN Outgoing Success Rate%50_HO3G3G010_CR

Mobility_3G3G metric Fcell&RNC 50_HO3G3G011_CR 3G3G HHO Intra RNC Outgoing Failure Rate%50_HO3G3G011_CR

Mobility_3G3G metric Fcell&RNC 50_HO3G3G012_CR 3G3G HHO Intra RNCIncoming Failure Rate%50_HO3G3G012_CR

Mobility_3G3G metric Fcell&RNC 50_HO3G3G013_CR 3G3G HHO Inter RNC Outgoing Without iuR Success Rate%50_HO3G3G013_CR

Mobility_3G3G metric Fcell&RNC 50_HO3G3G014_CR 3G3G HHO Inter RNC HHO Incoming Without iuR Success Rate%50_HO3G3G014_CR

Mobility_3G3G metric RNC 50_HO3G3G015_R Ratio of incoming SRNS relocations%50_HO3G3G015_R

Mobility_3G3G metric RNC 50_HO3G3G016_R Ratio of outgoing SRNS relocations%50_HO3G3G016_R

Mobility_3G3G metric RNC 50_TRS001_C IntraRnc Incoming Connection Attempts%50_TRS001_C

Mobility_3G3G metric RNC 50_TRS002_C IntraRnc Outgoing Connection Attempts%50_TRS002_C

Page 273: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 41

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 41

3 HHO Monitoring and Troubleshooting

Mobility Troubleshooting counters

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

counter RNC 558 VS.IuRelocationCmdFailuresCs.3Gto3GRelocTimeoutUeInv

counter RNC 558 VS.IuRelocationCmdFailuresCs.3Gto3GAlreadyInProgrUeInv

counter RNC 558 VS.IuRelocationCmdFailuresCs.3Gto3GFailTargetUeInv

counter RNC 558 VS.IuRelocationCmdFailuresCs.3Gto3GUnableToEstabUeInv

counter RNC 558 VS.IuRelocationCmdFailuresCs.3Gto3GOtherUeInv

counter RNC 558 VS.IuRelocationCmdFailuresCs.3Gto2GRelocTimeoutUeInv

counter RNC 558 VS.IuRelocationCmdFailuresCs.3Gto2GAlreadyInProgrUeInv

counter RNC 558 VS.IuRelocationCmdFailuresCs.3Gto2GFailTargetUeInv

counter RNC 558 VS.IuRelocationCmdFailuresCs.3Gto2GUnableToEstabUeInv

counter RNC 558 VS.IuRelocationCmdFailuresCs.3Gto2GOtherUeInv

counter RNC 558 VS.IuRelocationCmdFailuresCs.3Gto3GRelocTimeoutUeNotInv

counter RNC 558 VS.IuRelocationCmdFailuresCs.3Gto3GAlreadyInProgrUeNotInv

counter RNC 558 VS.IuRelocationCmdFailuresCs.3Gto3GFailTargetUeNotInv

counter RNC 558 VS.IuRelocationCmdFailuresCs.3Gto3GOtherUeNotInv

counter RNC 559 VS.IuRelocationCommandFailuresPs.RelocTimeoutUeInv

counter RNC 559 VS.IuRelocationCommandFailuresPs.RelocAlreadyInProgressUeInv

counter RNC 559 VS.IuRelocationCommandFailuresPs.RelocFailureInTargetSystemUeInv

counter RNC 559 VS.IuRelocationCommandFailuresPs.RelocUnableEstablishUeInv

counter RNC 559 VS.IuRelocationCommandFailuresPs.RelocOtherCausesUeInv

counter RNC 559 VS.IuRelocationCommandFailuresPs.RelocTimeoutUeNotInv

counter RNC 559 VS.IuRelocationCommandFailuresPs.RelocAlreadyInProgressUeNotInv

counter RNC 559 VS.IuRelocationCommandFailuresPs.RelocFailureInTargetSystemUeNotInv

counter RNC 559 VS.IuRelocationCommandFailuresPs.RelocOtherCausesUeNotInv

Page 274: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 42

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 42

3 HHO Monitoring and Troubleshooting

CS 3G 2G Mobility Analysis & Troubleshooting

CS 3G2G Mobility Analysis –Network level

Counters

CS 3G2G Mobility Analysis –RNC levelCounters

CS 3G2GPreparation Analysis – Cell level

Counters

CS 3G2G Mobility Analysis –RNC levelCounters

CS 3G2GPreparation Analysis – Selected Cells

CTG Analysis

Preparation part Low rate execution part 2G side

CTG Analysis

CS 3G2G Mobility Analysis –Network level

3G 2G CS HHO Success Rate <95%

HO3G2G019

3G-2G HHO CS executionsuccess rate

3G2G HHO CS preparationsuccess rate

CS 3G2G Preparation Analysis –RNC level

CS 3G2G Execution Analysis –RNC level

Determine the RNC with

Low (1-HO3G2G018)Determine the RNC with

Low HO3G2G020

•HS3G2G003 and HO3G2G004 to monitor the detection.

Page 275: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 43

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 43

To determine the worst N cells with a

representative number of HO From

UTRAN Failures:the highest number

of CS HO From UTRAN Failure

3 HHO Monitoring and Troubleshooting

3G2G CS Execution Analysis & Troubleshooting

3G2G CS HHO Execution Analysis –RNC level

Low HHO 3G2G CS execution success ratio

HO3G2G020

3G-2G HHO CS execution failure rate (2G side )

HO3G2G002_CS_RNC

Target 2G neighboring cells RF condition analysis

Check the setting of 3G2G CS HHO

Algorithm Parameters

3G-2G HHO CS execution failure rate (2G side

TOP N Cells

HO3G2G002_CS_Cell

3G-2G HHO CS execution failure rate (3G side)TOP N Cells

HO3G2G022_Cell

To determine the worst N cells with a

representative number of HO From

UTRAN Failures:the highest number

of CS Calls drop due to CS 3G2G

HHO

3G-2G HHO CS execution failure rate (3G side )

HO3G2G0022 RNC

Threshold need to be adapted to theoperator case, see threshold info

Page 276: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 44

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 44

3 HHO Monitoring and Troubleshooting

Preparation 3G2G CS HHO Analysis & Troubleshooting

Preparation 3G2G CS HHO Analysis –RNC level

3G2G HHO CS preparation success rate

1-HO3G2G018

High CS 3G2G RejectionSuccess rate

due to Time out

Check Outage in Transmission NetworkBetween 3G CN and 2G network

Check the Outage in the 2G target network identified

High CS 3G2G RejectionSuccess rate

due to unable to establish

Check the Neighbouring cells definition

High CS 3G2G RejectionSuccess rate

due to Failure in Target System

To determine the rejection causes (Refer to 3GPP TS 25.413):

#0558 Iu relocation command failures CS

Preparation 3G2G HHO Failures TOP N Cells

Check the 2G Neighbouring Cells capacity Analysis

High CS 3G2G RejectionSuccess rate

due to Other Reasons

Preparation 3G2G HHO FailuresTOP N Cells

To determine the worst N cells with a representative number of Preparation 3G2G HHO Failures:the highest number of #0109 -#0101VS.3gto2gHoDetectionFromFddcell -

VS.RrcHoFromUtranCommand

Preparation 3G2G HHO Failures TOP N Cells

Threshold need to be adapted to theoperator case, see threshold info

5.0_Metric id

or counter id5.0_Metric name

558 VS.IuRelocationCmdFailuresCs.3Gto2GRelocTimeoutUeInv

558 VS.IuRelocationCmdFailuresCs.3Gto2GAlreadyInProgrUeInv

558 VS.IuRelocationCmdFailuresCs.3Gto2GFailTargetUeInv

558 VS.IuRelocationCmdFailuresCs.3Gto2GUnableToEstabUeInv

558 VS.IuRelocationCmdFailuresCs.3Gto2GOtherUeInv

Page 277: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 45

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 45

3 HHO Monitoring and Troubleshooting

Action to improve the Preparation phase

� The 3G2G HHO Preparation Failure causes are the following ones:

� Failure in 2G target cell (congestion, outage)

� Wrong definition of 3G neighbouring identifiers (cells, LAC…) in 2G network

� Wrong definition of 2G neighbouring identifiers (cells, LAC…) in 3G network

� Timeout in the procedure (mainly on 2G side as 3G is just relaying messages)

� Call dropped between “Iu Relocation Required” and “HO from UTRAN Command”

� Any failure from the RNC and/or BTS during the procedure

� When the 3G2G HHO Preparation Success rate is very low, it means that the

failure causes are not occasional ones:

� Either wrong definition of 3G neighboring identifiers (cells, LAC…) in 2G network

� Or wrong definition of 2G neighboring identifiers (cells, LAC,…) in 3G network

Page 278: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 46

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 46

3 HHO Monitoring and Troubleshooting

Actions to improve the Execution phase

� The 3G2G HHO Execution Failure causes are the following ones:

� Mobile synchronization issue with 2G target cell

� Radio issue to access the 2G target cell

� Call Dropped (3G side) after HO from UTRAN command

� When the 3G2G HHO Execution Success rate is very low, it means that

the failures are not due to some mobiles but rather to a radio issue on

the 2G target cell

Page 279: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 47

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 47

Self-Assessment on the Objectives

� Please be reminded to fill in the formSelf-Assessment on the Objectivesfor this module

� The form can be found in the first partof this course documentation

Page 280: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 6 � Page 48

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Mobility Monitoring & Troubleshooting Section 6 �Page 48

End of Module

Page 281: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 1

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

Do not delete this graphic elements in here:

All Rights Reserved © Alcatel-Lucent 2007

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

7 3FL12921AAAAWBZZA Edition 1

Section 7Network Quality

Monitoring & Troubleshooting

Page 282: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 2

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 2

Blank Page

This page is left blank intentionally

Second editionEL ABED, Achrafe2007-10-2002

First editionEL ABED, Achrafe2007-08-2401

RemarksAuthorDateEdition

Document History

Page 283: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 3

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 3

Objectives

� At the end of this module, you will be able to:

� Describe the quality metric family

� Illustrate the call flows associated with the metric family

� Identify counters and locate them in the call flow procedure

� Define metrics and recognize its key counters

� Analyze each metric

Page 284: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 4

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 4

Objectives [cont.]

This page is left blank intentionally

Page 285: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 5

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 5

Table of Contents

Switch to notes view!Page

1 Network Quality Overview 7KPIs families Reminder 8Quality Overview (1/2) 9Quality Overview (2/2) 10

2 Network Quality Monitoring and Analysis 11Quality Monitoring & Troubleshooting 12DL BLER Monitoring 13DL BLER Troubleshooting chart 14Throughput Monitoring panel 15Throughput & BLER troubleshooting panels 16Throughput chart 17RF Monitoring 18RF Conditions Analysis 19RRC Procedure Performance 20RRC Procedure Performance 21DL RF analysis 22Indicators to correlate with DL Radio measurements 23Indicator to correlate with UL measurements 24UL RSSI introduction (1/2) 25UL RSSI introduction (2/2) 26Self-Assessment on the Objectives 27End of Module 28

Page 286: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 6

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 6

Table of Contents [cont.]

Switch to notes view!

This page is left blank intentionally

Page 287: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 7

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 7

1 Network Quality Overview

Page 288: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 8

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 8

1 Network Quality Overview

KPIs families Reminder

Network Accessibility

NetworkRetainability

NetworkQuality

NetworkTraffic

NetworkCongestion

Counter based KPIs

Capacity/

Load

Call ProfileHSxPA

RRM

NetworkMobility

5.0_Report (PMG) Family TypeNetwork

Element5.0_Metric id or counter id 5.0_Metric name

RNC panel Accessibility metric RNC 50_CSSR005_R%Cs Call Setup Success Rate%Cs%50_CSSR005_R

RNC panel Accessibility metric RNC 50_CSSR005_R%Ps Call Setup Success Rate%Ps%50_CSSR005_R

RNC panel Accessibility metric RNC 50_IuSCCP006_R%Cs IuSCCP Success Rate%Cs%50_IuSCCP006_R

RNC panel Accessibility metric RNC 50_IuSCCP006_R%Ps IuSCCP Success Rate%Ps%50_IuSCCP006_R

RNC panel Accessibility metric RNC 50_RAB011_R%CsSpeech RAB Establishment Success Rate per Requested RAB%CsSpeech%50_RAB011_R

RNC panel Accessibility metric RNC 50_RAB011_R%CsVideo RAB Establishment Success Rate per Requested RAB%CsVideo%50_RAB011_R

RNC panel Accessibility metric RNC 50_RAB011_R%Ps RAB Establishment Success Rate per Requested RAB%Ps%50_RAB011_R

RNC panel Accessibility metric RNC 50_RAB022_R%CsVideo RAB Assignment Success per Granted RAB type%CsVideo%50_RAB022_R

RNC panel Accessibility metric RNC 50_RAB022_R%CsVoice RAB Assignment Success per Granted RAB type%CsVoice%50_RAB022_R

RNC panel Accessibility metric RNC 50_RAB022_R%HSDPA RAB Assignment Success per Granted RAB type%HSDPA%50_RAB022_R

RNC panel Accessibility metric RNC 50_RAB022_R%Ps RAB Assignment Success per Granted RAB type%Ps%50_RAB022_R

RNC panel Accessibility metric RNC 50_RRC003_CR%Cs RRC Connection Success Rate%Cs%50_RRC003_CR

RNC panel Accessibility metric RNC 50_RRC003_CR%Ps RRC Connection Success Rate%Ps%50_RRC003_CR

RNC panel Accessibility metric RNC 50_RRC013_CR%Cs First RRC Connection Success Rate%Cs%50_RRC013_CR

RNC panel Accessibility metric RNC 50_RRC013_CR%Ps First RRC Connection Success Rate%Ps%50_RRC013_CR

RNC panel Accessibility metric RNC 50_RRC015_CR%Cs First RRC Connection Request%Cs%50_RRC015_CR

RNC panel Accessibility metric RNC 50_RRC015_CR%Ps First RRC Connection Request%Ps%50_RRC015_CR

RNC panel Accessibility metric RNC 50_SMC001_R%Cs Security Mode Command%Cs%50_SMC001_R

RNC panel Accessibility metric RNC 50_SMC001_R%Ps Security Mode Command%Ps%50_SMC001_R

RNC panel Accessibility metric RNC 50_SMC002_R%Cs Security Mode Command Success Rate%Cs%50_SMC002_R

RNC panel Accessibility metric RNC 50_SMC002_R%Ps Security Mode Command Success Rate%Ps%50_SMC002_R

Accessibility monitoring - RNC panel

Page 289: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 9

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 9

1 Network Quality Overview

Quality Overview (1/2)

� Defines the ability of the network to provide quality transmission of the user requested services

� In UA 5.0 the main focus will be to maximize� Throughput metrics� DL BLER� Network availability (by mean of Accessibility & Retainability analysis)

Page 290: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 10

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 10

1 Network Quality Overview

Quality Overview (2/2)

Actions to improve

Quality KPIs

Server parameters

Network topology

UTRAN:�RF Coverage Control�RF Quality

�RLC parameters

�RRM Algorithms Fine tuning, mainly

�RB Adaptation downsize

�RB Adaptation upsize

�iRM Sched downgrade / DlTxPwr

�iRM Power Preemption

�iRM Sched upgrading based on TxCPalgorithm

�AO downsize

�AO upsize

Core Network parameters

Page 291: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 11

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 11

2 Network Quality Monitoring and Analysis

Page 292: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 12

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 12

2 Network Quality Monitoring and Analysis

Quality Monitoring & Troubleshooting

� BLER Monitoring & Troubleshooting� HSDPA Quality Monitoring (Throughput+BLER)� Throughput Monitoring & Troubleshooting

� Call reconfiguration Quality (affecting, BLER and throughput)� Lack of resources to perform RRM transitions like AO Upsize, Irm Scheduling Upgrade�call is not reconfigured and this will have impact in user throughput

� Radio link reconfiguration Unsuccess (iRM reconfiguration)� Radio link setup unsucess (AON)� AON/iRM failure counters

� RF Quality� DL

� Focus on RF measurements: Ec/No, RSCP, SPU, DL BLER, ASU/sec, Primary cell update(possible in HSDPA)

� Failure metric/counters to correlate� HHO failures� Failure due to radio DL issues

� UL. Mainly focus on RSSI, also UL BLER (this metric is not available, in restriction)� Failure metric/counters to correlate

� HHO failures� Failure due to radio UL issues

Page 293: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 13

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 13

2 Network Quality Monitoring and Analysis

DL BLER Monitoring

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric Fcell&RNC 50_BLER005_CR%CsVoice Uplink BLER%CsVoice%50_BLER005_CR

metric Fcell&RNC 50_BLER006_CR%HSDPA Downlink BLER%HSDPA%50_BLER006_CR

metric Fcell&RNC 50_BLER006_CR%Ps Downlink BLER%Ps%50_BLER006_CR

metric Fcell&RNC 50_BLER006_CR%Ps128 Downlink BLER%Ps128%50_BLER006_CR

metric Fcell&RNC 50_BLER006_CR%Ps256 Downlink BLER%Ps256%50_BLER006_CR

metric Fcell&RNC 50_BLER006_CR%Ps32 Downlink BLER%Ps32%50_BLER006_CR

metric Fcell&RNC 50_BLER006_CR%Ps384 Downlink BLER%Ps384%50_BLER006_CR

metric Fcell&RNC 50_BLER006_CR%Ps64 Downlink BLER%Ps64%50_BLER006_CR

metric Fcell&RNC 50_BLER008_CR Downlink BLER%50_BLER008_CR

metric Fcell&RNC 50_BLER009_CR Uplink BLER%50_BLER009_CR

metric Fcell&RNC 50_BLER009_CR%AMR10p2 Uplink BLER%AMR10p2%50_BLER009_CR

metric Fcell&RNC 50_BLER009_CR%AMR12p2 Uplink BLER%AMR12p2%50_BLER009_CR

metric Fcell&RNC 50_BLER009_CR%AMR4p75 Uplink BLER%AMR4p75%50_BLER009_CR

metric Fcell&RNC 50_BLER009_CR%AMR5p9 Uplink BLER%AMR5p9%50_BLER009_CR

metric Fcell&RNC 50_BLER009_CR%AMR6p7 Uplink BLER%AMR6p7%50_BLER009_CR

metric Fcell&RNC 50_BLER009_CR%AMR7p95 Uplink BLER%AMR7p95%50_BLER009_CR

Page 294: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 14

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 14

2 Network Quality Monitoring and Analysis

DL BLER Troubleshooting chart

Network Quality Analysis –RNC level

High BLER PS

BLER006

Low BLER PS

BLER006

RF Conditions Analysis –RNC/ Cell level

High # of iRM Downgrading

UL BLER chart not possible

Irm downgrade success ratio decrease?

RRA downsizesuccess ratio decrease

RRA panel

IRM Scheduling(RLC BLER orTxCP)Parameter tuningor & ConfiguracioncheckingCTg Analysis

iRM panel

RRA analusisParamenter tuning & ConfigurationcheckingCTg analysis

Reconfiguration rate decreases?

Issue characterization: • Which PS rate is

affected?• Affecting all RNC/only

specific RNC• Affected some specific

cells?• Punctual degradation that

disappear?Or degradationremains?

• Certain/all period of time, since when: upgrades, feature activations, etc?

RF Audit panels

SRLRRadio link failures

Capacityanalysis

Correlated?

Correlated?

•Correlation with someATM counters/metricsis missed

Page 295: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 15

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 15

2 Network Quality Monitoring and Analysis

Throughput Monitoring panel

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name Type

Network

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_HSDPA008_C%RLC Throughput per cell %RLC%50_HSDPA008_C metric Fddcell 50_Traffic028_C%HSDPA Traffic DL Throughput in kbps%HSDPA%50_Traffic028_C

metric Fcell&RNC 50_HSDPA008_C MAC-d throughput per cell %50_HSDPA008_C metric Fddcell 50_Traffic028_C%Ps128 Traffic DL Throughput in kbps%Ps128%50_Traffic028_C

metric Fddcell 50_HSDPA035_C HSDPA cell throughput%50_HSDPA035_C metric Fddcell 50_Traffic028_C%Ps256 Traffic DL Throughput in kbps%Ps256%50_Traffic028_C

metric Fddcell 50_HSDPA008_C%RLC Throughput per cell %RLC%50_HSDPA008_C metric Fddcell 50_Traffic028_C%Ps384 Traffic DL Throughput in kbps%Ps384%50_Traffic028_C

metric RNC 50_Traffic011_R%CsVideo Average DL Activity Factor%CsVideo%50_Traffic011_R metric Fddcell 50_Traffic028_C%Ps64 Traffic DL Throughput in kbps%Ps64%50_Traffic028_C

metric RNC 50_Traffic011_R%CsVoice Average DL Activity Factor%CsVoice%50_Traffic011_R metric Fddcell 50_Traffic029_C%CsVideo Activity Factor DL%CsVideo%50_Traffic029_C

metric RNC 50_Traffic011_R%Ps128 Average DL Activity Factor%Ps128%50_Traffic011_R metric Fddcell 50_Traffic029_C%CsVoice Activity Factor DL%CsVoice%50_Traffic029_C

metric RNC 50_Traffic011_R%Ps256 Average DL Activity Factor%Ps256%50_Traffic011_R metric Fddcell 50_Traffic029_C%Ps128 Activity Factor DL%Ps128%50_Traffic029_C

metric RNC 50_Traffic011_R%Ps384 Average DL Activity Factor%Ps384%50_Traffic011_R metric Fddcell 50_Traffic029_C%Ps256 Activity Factor DL%Ps256%50_Traffic029_C

metric RNC 50_Traffic011_R%Ps64 Average DL Activity Factor%Ps64%50_Traffic011_R metric Fddcell 50_Traffic029_C%Ps384 Activity Factor DL%Ps384%50_Traffic029_C

metric RNC 50_Traffic012_R%CsVideo Average UL Activity Factor%CsVideo%50_Traffic012_R metric Fddcell 50_Traffic029_C%Ps64 Activity Factor DL%Ps64%50_Traffic029_C

metric RNC 50_Traffic012_R%CsVoice Average UL Activity Factor%CsVoice%50_Traffic012_R metric Fddcell 50_Traffic030_C%CsVideo Traffic DL active throughput in kbps%CsVideo%50_Traffic030_C

metric RNC 50_Traffic012_R%Ps128 Average UL Activity Factor%Ps128%50_Traffic012_R metric Fddcell 50_Traffic030_C%CsVoice Traffic DL active throughput in kbps%CsVoice%50_Traffic030_C

metric RNC 50_Traffic012_R%Ps32 Average UL Activity Factor%Ps32%50_Traffic012_R metric Fddcell 50_Traffic030_C%HSDPA Traffic DL active throughput in kbps%HSDPA%50_Traffic030_C

metric RNC 50_Traffic012_R%Ps384 Average UL Activity Factor%Ps384%50_Traffic012_R metric Fddcell 50_Traffic030_C%Ps128 Traffic DL active throughput in kbps%Ps128%50_Traffic030_C

metric RNC 50_Traffic012_R%Ps64 Average UL Activity Factor%Ps64%50_Traffic012_R metric Fddcell 50_Traffic030_C%Ps256 Traffic DL active throughput in kbps%Ps256%50_Traffic030_C

metric RNC 50_Traffic022_CR%HSDPA RAB Activity DL%HSDPA%50_Traffic022_CR metric Fddcell 50_Traffic030_C%Ps384 Traffic DL active throughput in kbps%Ps384%50_Traffic030_C

metric RNC 50_Traffic023_CR%HSUPA RAB Activity UL%HSUPA%50_Traffic023_CR metric Fddcell 50_Traffic030_C%Ps64 Traffic DL active throughput in kbps%Ps64%50_Traffic030_C

metric RNC 50_Traffic024_R%CsVideo Traffic DL Throughput in kbps%CsVideo%50_Traffic024_R metric Fddcell 50_Traffic031_C%CsVideo Traffic UL active throughput in kbps%CsVideo%50_Traffic031_C

metric RNC 50_Traffic024_R%CsVoice Traffic DL Throughput in kbps%CsVoice%50_Traffic024_R metric Fddcell 50_Traffic031_C%CsVoice Traffic UL active throughput in kbps%CsVoice%50_Traffic031_C

metric RNC 50_Traffic024_R%Ps128 Traffic DL Throughput in kbps%Ps128%50_Traffic024_R metric Fddcell 50_Traffic031_C%HSUPA Traffic UL active throughput in kbps%HSUPA%50_Traffic031_C

metric RNC 50_Traffic024_R%Ps256 Traffic DL Throughput in kbps%Ps256%50_Traffic024_R metric Fddcell 50_Traffic031_C%Ps128 Traffic UL active throughput in kbps%Ps128%50_Traffic031_C

metric RNC 50_Traffic024_R%Ps384 Traffic DL Throughput in kbps%Ps384%50_Traffic024_R metric Fddcell 50_Traffic031_C%Ps32 Traffic UL active throughput in kbps%Ps32%50_Traffic031_C

metric RNC 50_Traffic024_R%Ps64 Traffic DL Throughput in kbps%Ps64%50_Traffic024_R metric Fddcell 50_Traffic031_C%Ps384 Traffic UL active throughput in kbps%Ps384%50_Traffic031_C

metric RNC 50_Traffic025_R%CsVideo Traffic UL Throughput in kbps%CsVideo%50_Traffic025_R metric Fddcell 50_Traffic031_C%Ps64 Traffic UL active throughput in kbps%Ps64%50_Traffic031_C

metric RNC 50_Traffic025_R%CsVoice Traffic UL Throughput in kbps%CsVoice%50_Traffic025_R metric Fddcell 50_Traffic032_C%HSUPA Traffic UL Throughput in kbps%HSUPA%50_Traffic032_C

metric RNC 50_Traffic025_R%HSUPA Traffic UL Throughput in kbps%HSUPA%50_Traffic025_R metric Fddcell 50_Traffic032_C%Ps128 Traffic UL Throughput in kbps%Ps128%50_Traffic032_C

metric RNC 50_Traffic025_R%Ps128 Traffic UL Throughput in kbps%Ps128%50_Traffic025_R metric Fddcell 50_Traffic032_C%Ps384 Traffic UL Throughput in kbps%Ps384%50_Traffic032_C

metric RNC 50_Traffic025_R%Ps32 Traffic UL Throughput in kbps%Ps32%50_Traffic025_R metric Fddcell 50_Traffic032_C%Ps64 Traffic UL Throughput in kbps%Ps64%50_Traffic032_C

metric RNC 50_Traffic025_R%Ps384 Traffic UL Throughput in kbps%Ps384%50_Traffic025_R metric Fddcell 50_Traffic033_C%Ps128 Activity Factor UL%Ps128%50_Traffic033_C

metric RNC 50_Traffic025_R%Ps64 Traffic UL Throughput in kbps%Ps64%50_Traffic025_R metric Fddcell 50_Traffic033_C%Ps384 Activity Factor UL%Ps384%50_Traffic033_C

metric Fddcell 50_Traffic033_C%Ps64 Activity Factor UL%Ps64%50_Traffic033_C

Page 296: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 16

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 16

2 Network Quality Monitoring and Analysis

Throughput & BLER troubleshooting panels

� RRM panel

� iRM panel

� AO panel

� Radio Link panel

� RF Audit, panels to correlate with DL/UL RF

� Drops panel from retainability analysis

Please find these panels in the annex

Page 297: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 17

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 17

2 Network Quality Monitoring and Analysis

Throughput chart

PS Throughput Analysis –RNC level

Maximizing:

•Throughput based on RAB allocation time

•Throughput HSDPA

•Activity factors

•Kbps before drop

Minimizing

•PS Call drop per minute

AO upsizing Success Ratio

Decrease?

Irm upgrade success ratio decrease?

•Correlation with•PS Drop Call indicator: high?

•PS Drop Call rate•HSDPA Drop Call rate

•Number of Drops •per Minute of Calls

Reconfiguration rate decreases?

•ThroughputMonitoringpanel

All cells of RNC?Yes

PS retainability

Cell Analysis

No

RF AnalysisIrm, AO,RRA

Analysis

Top N CellsHigh # Drops

High # Drop call rate

Fddcell

•Throughput decreases

No

PS retainabilityRNC level

YesDecrease of Throughput

Affect all fddcells?R99: Traffic028

HSDPA throughput at RLC levelNoFddcell

Top Worst Cells

AO analysisParameter tuning

or check ConfiguratonCTg Analysis

RRA Upsizing success ratio decrease

RRA panelRRA panel-fddcell

iRM panel (BLER &TxCP) –fddcell

AO panel- fddcell

RF audit-fddcell

•Panels to correlate with RF Audit

AO panel- RNC

IRM Scheduling(RLC BLER orTxCP)Parameter tuningor & ConfiguracioncheckingCTg Analysis

iRM panel

RRA analusisParamenter tuning & ConfigurationcheckingCTg analysis

Yes

Capacityanalysis

SRLRRadio link failures

RL panel

Correlated?Correlated?

•Low Kbps before drop

•Top_ PS Call drop per minute

Page 298: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 18

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 18

2 Network Quality Monitoring and Analysis

RF Monitoring

DL/UL measurments• RSCP, RSSI, Ec/No+BLERSPU, ASU/S, Primary CellUpdate

Family TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

Accessibility metric FDDCELL 50_RB011_C Radio Bearer Setup Success%50_RB011_C

Capacity metric Fcell&RNC 50_RL016_CR MeanSector per user%50_RL016_CR

Capacity/Load metric FDDCELL 50_BLER006_CR%HSDPA Downlink BLER%HSDPA%50_BLER006_CR

Capacity/Load counter FDDCELL 50_Cell007_C%minusx to minusY All ranges EcN0 Distribution%minusX to minusY%50_Cell007_C All ranges

Capacity/Load counter FDDCELL 50_Cell008_C%minusX to minusY All ranges RSCP Distribution%minusX to minusY%50_Cell008_C All ranges

Mobility metric Fcell&RNC 50_HSDPA039_CR HSDPA To HSDPA Primary Cell Change Per Min%50_HSDPA039_CR

Mobility metric RNC 50_RL020_C_Indicator Missing metric in PMM/Library

Mobility metric Fddcell 50_RL020_CR ActiveSetUpdate per second per RL%50_RL020_CR

Power Mngmt counter FDDCELL 301 VS.AveragePowerUsedForSpeech

Power Mngmt counter FDDCELL 302 VS.AveragePowerUsedForData

Power Mngmt counter FDDCELL 303 VS.UplinkRssi

Power Mngmt counter FDDCELL 304 VS.AveragePowerUsedForSignalling

Power Mngmt counter FDDCELL 305 VS.AveragePowerUsedForMiscellaneous

Power Mngmt counter FDDCELL 1002 VS.AvgTxPower

Power Mngmt counter BTSCELL 10201 VS.RadioWBandRxMainPwr

Power Mngmt counter BTSCELL 10202 VS.RadioWBandRxDivPwr

Power Mngmt counter BTSCELL 10203 VS.RadioTxCarrierPwr -

Power Mngmt counter BTSCELL 10204 VS.MCPAPower

Power Mngmt metric Fcell&RNC 50_HSDPA010_CR Average HSDPA Power used%50_HSDPA010_CR

QoS metric FDDCELL 50_BLER005_CR%CsVoice Uplink BLER%CsVoice%50_BLER005_CR

QoS metric FDDCELL 50_BLER006_CR%Ps128 Downlink BLER%Ps128%50_BLER006_CR

QoS metric FDDCELL 50_BLER006_CR%Ps256 Downlink BLER%Ps256%50_BLER006_CR

QoS metric FDDCELL 50_BLER006_CR%Ps32 Downlink BLER%Ps32%50_BLER006_CR

QoS metric FDDCELL 50_BLER006_CR%Ps384 Downlink BLER%Ps384%50_BLER006_CR

QoS metric FDDCELL 50_BLER006_CR%Ps64 Downlink BLER%Ps64%50_BLER006_CR

QoS metric FDDCELL 50_BLER006_CR%SRB Downlink BLER%SRB%50_BLER006_CR

QoS metric FDDCELL 50_BLER008_CR Downlink BLER%50_BLER008_CR

QoS metric FDDCELL 50_BLER009_CR Uplink BLER%50_BLER009_CR

QoS metric FDDCELL 50_BLER009_CR%AMR10p2 Uplink BLER%AMR10p2%50_BLER009_CR

QoS metric FDDCELL 50_BLER009_CR%AMR12p2 Uplink BLER%AMR12p2%50_BLER009_CR

QoS metric FDDCELL 50_BLER009_CR%AMR4p75 Uplink BLER%AMR4p75%50_BLER009_CR

QoS metric FDDCELL 50_BLER009_CR%AMR5p9 Uplink BLER%AMR5p9%50_BLER009_CR

QoS metric FDDCELL 50_BLER009_CR%AMR6p7 Uplink BLER%AMR6p7%50_BLER009_CR

QoS metric FDDCELL 50_BLER009_CR%AMR7p95 Uplink BLER%AMR7p95%50_BLER009_CR

•New metrics in 5.0 for hsdpaand distribution of power

metrics can be also used in thispanel

Page 299: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 19

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 19

2 Network Quality Monitoring and Analysis

RF Conditions Analysis

RF Conditions Analysis –Cell level

Call Trace VerificationDeep RF study

Low UL RSSI

UL Interference issues

High Percentage of

Bad RSCP

DL Coverageissues

High Percentage of

Bad Ec/N0

DL Interference &/ or DL Coverage

issuesUL Interference issues

High UL RSSI

Main and Diversity!

UL Interference issuesOptimization

High UL RSSI

Site Visit/Others

*50% de charge uplink

RF control & optimization: •Tilts, Antena Orientation,RF parameter tuning•Avoid Pilot pollution, Slow handovers, Overshooting•Cell customization paramters for difference scenarios(dense, rural, corner sites)•Power settings•3g2g strategy, 3g2g tuning, iRM strategy•Site densification

Page 300: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 20

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 20

2 Network Quality Monitoring and Analysis

RRC Procedure Performance

� To evaluate the radio conditions when the calls are established, the following indicators can be used:

RRC.SuccConnEstab[RRC cause]

RRC.AttConnEstab[RRC cause]=RRC Connection

Success Rate

VS.RrcConnectionSetup.*

RRC.AttConnEstab.*=

Ratio of RRC ConnectionSetup repetitions

The RRC performance of Terminating calls can be better than Originating (highest probability of sending/receiving RRC messages or user trying to re-establish the call in bad radio conditions)

If there is a high repetition rate, it means that the call try to setup already in bad radio conditions (lack or coverage or interfered area)

(VS.RrcConnectionSetup.InitialWithQuickRepeat + VS.RrcConnectionSetup.FirstRepetitionWithQuickRepeat) / VS.RrcConnectionSetup.*

=Ratio of RRC QuickRepeat usage

If there is a high repetition rate, it means that the call try to setup already in bad radio conditions (lack or coverage or interfered area)

If QR is used, the call try to setup with a bad Ec/Io

By using the Reference observation Counters files, find the definition of these counters and there relative screening!

Page 301: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 21

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 21

3 RF Quality Analysis

Page 302: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 22

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 22

Operator dependantAccording to RF designstrategy for the differentservices

3 RF Quality Analysis

DL RF analysis

RF Conditions Analysis –Cell level

High Percentage ofBad RSCP*

DL Coverageissues

High Percentage of

Bad Ec/N0*

DL Interference &/ or DL Coverage

issues

RF control & optimization: •Tilts, Antenna Orientation,RF parameter tuning•Avoid Pilot pollution, Slow handovers, Overshooting•Cell customization paramters for difference scenarios(dense, rural, corner sites)•Ping-pong areas optimization•Power settings•3g2g strategy, 3g2g tuning, iRM strategy•Site densification

Correlation withHigh SPU (RL016)High ASU/s (Rl020)Also DL indicators

(see next slide)

•Top N worst cells

Correlationwith

DL indicatorsIe, higher Radio drops

Operator dependanceAccording to RF designstrategy for thedifferent services

•Note: be aware of ifFET is activated, radio measurements can be not representativestatically

Page 303: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 23

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 23

3 RF Quality Analysis

Indicators to correlate with DL Radio measurements

•Note: the list of indicators tocorrelate are indicators that can increase when DL Radio issues

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric Fcell&RNC 50_RL016_CR MeanSector per user%50_RL016_CR

counter Fcell&RNC 576 VS.IuReleaseReqCs.UnspecifiedFailure

counter Fcell&RNC 576 VS.IuReleaseReqCs.RadioCnxUeLost

counter Fcell&RNC 576 VS.IuReleaseReqCs.AbnormalConditionTimerRelocExpiry

counter Fcell&RNC 576 VS.IuReleaseReqCs.DlRLCErrSRB

counter Fcell&RNC 577 VS.IuReleaseReqPs.UnspecifiedFailure

counter Fcell&RNC 577 VS.IuReleaseReqPs.AbnormalConditionTimerRelocExpiry

counter Fcell&RNC 577 VS.IuReleaseReqPs.RadioCnxUeLost

counter Fddcell 0 IRATHO.FailOutCS

counter Fddcell 0 IRATHO.FailOutPS

counter Fddcell 0 IRATHO.AttOutCS

counter Fddcell 0 IRATHO.AttOutPS

counter Fddcell 2 VS.RadioLinkSetupUnsuccess.RadioLinkSetupFailure

counter Fddcell 2 VS.RadioLinkSetupUnsuccess.Timeout

metric Fcell&RNC 50_HO3G2G014_R%CsVoice HO3G2G CS per Call%CsVoice%50_HO3G2G014_R

metric Fcell&RNC 50_HO3G2G015_R%PS HO3G2G CS per Call%PS%50_HO3G2G015_R

metric Fddcell 50_HO3G2G024_C%Cs Number of CS calls dropped due to 3G2G HHO%Cs%50_HO3G2G024_C

metric Fddcell 50_RL020_CR ActiveSetUpdate per second per RL%50_RL020_CR

metric RNC 50_RL020_R ActiveSetUpdate per second per RAB%50_RL020_R

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.UnavailableDlPowerResources

counter Fcell&RNC 631 VS.RadioBearerEstablishmentUnsuccess.Unspecified

counter Fcell&RNC 20 VS.RadioLinkFirstSetupFailure.RadioLinkSetupFailure

counter Fcell&RNC 20 VS.RadioLinkFirstSetupFailure.TimeoutNbap

metric Fcell&RNC 50_RL001_CR Radio Link Setup Unsuccess%50_RL001_CR

metric Fcell&RNC 50_RL002_CR Radio Link Setup Success%50_RL002_CR

metric Fcell&RNC 50_RL036_CR Radio Link Setup Blocking Rate%50_RL036_CR

metric Fcell&RNC 50_RL037_CR Radio Link Addition Blocking Rate%50_RL037_CR

counter Fcell&RNC 404 RRC.FailConnEstab - 0 - Time out

counter Fcell&RNC 404 RRC.FailConnEstab - 2 - unavailable DL power resources

counter Fcell&RNC 404 RRC.FailConnEstab - 3 - Unspecified

counter Fcell&RNC 404 RRC.FailConnEstab - 13 -UE Ec/No lower than qQualityMin

metric Fcell&RNC 50_RRC017_CR%DLPowerResources RRC Conn Failure Distribution%DLPowerResources%50_RRC017_CR

metric Fcell&RNC 50_RRC017_CR%T352Expiration RRC Conn Failure Distribution%T352Expiration%50_RRC017_CR

metric Fcell&RNC 50_RRC017_CR%Unspecified RRC Conn Failure Distribution%Unspecified%50_RRC017_CR

Page 304: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 24

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 24

3 RF Quality Analysis

Indicator to correlate with UL measurements

• Note: the list ofindicators to correlateare indicators that can increase when UL Radio issues

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

counter Fcell&RNC 576 VS.IuReleaseReqCs.UnspecifiedFailure

counter Fcell&RNC 576 VS.IuReleaseReqCs.RadioCnxUeLost

counter Fcell&RNC 576 VS.IuReleaseReqCs.AbnormalConditionTimerRelocExpiry

counter Fcell&RNC 576 VS.IuReleaseReqCs.UlRLCErrSRB

counter Fcell&RNC 577 VS.IuReleaseReqPs.UnspecifiedFailure

counter Fcell&RNC 577 VS.IuReleaseReqPs.AbnormalConditionTimerRelocExpiry

counter Fcell&RNC 577 VS.IuReleaseReqPs.RadioCnxUeLost

metric Fcell&RNC 50_IU012_C Percentage of CS Calls Dropped due to RL Failure%50_IU012_C

metric Fcell&RNC 50_IU014_C Percentage of Calls Dropped due to RL Failure%50_IU014_C

counter Fddcell 0 IRATHO.FailOutCS

counter Fddcell 0 IRATHO.FailOutPS

counter Fddcell 0 IRATHO.AttOutCS

counter Fddcell 0 IRATHO.AttOutPS

counter Fddcell 2 VS.RadioLinkSetupUnsuccess.RadioLinkSetupFailure

counter Fddcell 2 VS.RadioLinkSetupUnsuccess.Timeout

metric Fcell&RNC 50_HO3G2G014_R%CsVoice HO3G2G CS per Call%CsVoice%50_HO3G2G014_R

metric Fcell&RNC 50_HO3G2G015_R%PS HO3G2G PS per Call%PS%50_HO3G2G015_R

metric Fddcell 50_HO3G2G024_C%Cs Number of CS calls dropped due to 3G2G HHO%Cs%50_HO3G2G024_C

counter Fcell&RNC 20 VS.RadioLinkFirstSetupFailure.RadioLinkSetupFailure

counter Fcell&RNC 20 VS.RadioLinkFirstSetupFailure.TimeoutNbap

metric Fcell&RNC 50_RL001_CR Radio Link Setup Unsuccess%50_RL001_CR

metric Fcell&RNC 50_RL004_CR Radio Link Addition Unsuccess%50_RL004_CR

metric Fcell&RNC 50_RL036_CR Radio Link Setup Blocking Rate%50_RL036_CR

metric Fcell&RNC 50_RL037_CR Radio Link Addition Blocking Rate%50_RL037_CR

counter Fcell&RNC 404 RRC.FailConnEstab - 0 - Time out

counter Fcell&RNC 404 RRC.FailConnEstab - 3 - Unspecified

counter Fcell&RNC 404 RRC.FailConnEstab - 4 - RSSI

metric Fcell&RNC 50_RRC017_CR%RSSI RRC Conn Failure Distribution%RSSI%50_RRC017_CR

metric Fcell&RNC 50_RRC017_CR%T352Expiration RRC Conn Failure Distribution%T352Expiration%50_RRC017_CR

metric Fcell&RNC 50_RRC017_CR%Unspecified RRC Conn Failure Distribution%Unspecified%50_RRC017_CR

Page 305: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 25

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 25

3 RF Quality Analysis

UL RSSI introduction (1/2)

� Calculation of expected UL RSSI per cell

(TMA, cable length, jumpers, cable type

etc), in non-traffic scenario

� Reporting Range [-112…-50]dBm

� Accuracy:

� Absolute +/-4dBm

� Relative +/-0.5dBm

� Measurement done at TRM level, and

reported at reference point.

� Due to uncertainties in TMA, DDM and

iTRM gain, the expected UL RSSI

distribution for a unloaded cell is -

105dBm with a +/-4dBm accuracy.

iBTSDDM iTRM

Rx Channelizer

DDM gain

Reference Point

Internal cable loss and gain from iTRM input to measurement block in channelizer is taking into account in a hard coded SW value

Page 306: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 26

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 26

3 RF Quality Analysis

UL RSSI introduction (2/2)

UL RSSI

RNC

VS.UplinkRssi.Avg #303

UL RSSI = -112dBm + 10 Log(VS.UplinkRssi.Avg[FddCell,Time]

RTWP = -120dBm+10Log10((VS.RadioWBandRxDivPwr.Avg[FddCell,Time]+

VS.RadioWBandRxMainPwr.Avg[FddCell,Time])/2))

Too high UL RSSI if > -98 dBm

Too low UL RSSI if < -112 dBm

VS.RadioWBandRx__Pwr#10201, #10202

All counters are using the RTWP measurement from the TRM :

� Counter at RNC level : Vs.UplinkRssi (min, max, avg):

� Average of main and div RTWP measurements (done each 100ms); average value reported each 10s to

the RNC in NBAP common measurements. RNC send min, max, avg values from these measurements each

15 minutes. Unit is 10^-11.2 dBm. Average value is computed at the end of the observation period, min

and max values are reassessed each 10s

� Triggering event: reception of NBAP COMMON MEASUREMENT (parameter dependant)

� Counter at NodeB level VS.RadioWBandRxMain/Div.Pwr:

� The RTWP value measured each 100ms are reported to the perf server each hour. 6 values are reported

: (main, div) * (min, max, avg). Unit is 10^-12 dBm. Average value is computed at the end of the

observation period, min and max values are reassessed each 100ms

� Triggering event: a sampling event generated every 100 ms

� RadioWBandRxMainPwr : min/max/linear average (software filtered) wide-band received power per

sector, per frequency, at the Rx main channelizer

� RadioWBandRxDivPwr: min/max/linear average (software filtered) wide-band received power per

sector, per frequency, at the Rx diversity channelizer

� All in Watts not in dBm: RSSI = (RadioWBandRxMainPwr + RadioWBandRxDivPwr)/2

� Relation between Watts and dBm: Power in dBm = 10 log ( P in miliWatts)

RTWP :

(-

(120)+(10.0*Log10(((!VS.RadioWBandRxDivPwr.Avg![FddCell,Time]+!VS.RadioWBandRxMainPwr.Avg![FddCell,

Time])/2.0))))

RSSI :

(-(112)+(10.0*Log10('VS.UplinkRssi.Avg'[FddCell,Time])))

Page 307: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 27

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 27

Self-Assessment on the Objectives

� Please be reminded to fill in the formSelf-Assessment on the Objectivesfor this module

� The form can be found in the first partof this course documentation

Page 308: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 7 � Page 28

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Network Quality Monitoring & Troubleshooting Section 7 �Page 28

End of Module

Page 309: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 1

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

Do not delete this graphic elements in here:

All Rights Reserved © Alcatel-Lucent 2007

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

8 3FL12921AAAAWBZZA Edition 1

Section 8Capacity Monitoring &

Troubleshooting

Page 310: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 2

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 2

Blank Page

This page is left blank intentionally

Second editionEL ABED, Achrafe2007-10-2002

First editionEL ABED, Achrafe2007-08-2401

RemarksAuthorDateEdition

Document History

Page 311: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 3

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 3

Objectives

� At the end of this module, you will be able to:

� Describe the capacity metric family

� Illustrate the call flows associated with the metric family

� Identify counters and locate them in the call flow procedure

� Define metrics and recognize its key counters

� Analyze each metric

Page 312: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 4

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 4

Objectives [cont.]

This page is left blank intentionally

Page 313: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 5

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 5

Table of Contents

Switch to notes view!Page

1 Capacity Monitoring 7KPIs families Reminder 8UTRAN capacity analysis introduction 9UTRAN capacity analysis introduction: Reactive capacity planning 10UTRAN capacity analysis introduction: Capacity monitoring 11UTRAN congestion detection principles 12Blocking Characterization 13Load Resources 14

2 Capacity Analysis 15Capacity Analysis 16General Network View: NETWORK CONGESTION AND LOAD 17Congested cells at Network level: Global Blocking – example 18Load at Network level: CEM Load – example 19Load at Network level: Iub Load – example 20Load at Network level: DL Power Load – example 21Load at Network level: Codes Load – example 22Load at Network level: RNC CPU Load – example 23Load at Network level: RNC CPU Load – Monitoring 24

3 Capacity Troubleshooting 25Capacity Troubleshooting per Resource – UTRAN CAPACITY ANALYSIS 26Capacity Troubleshooting per Resource – UTRAN CAPACITY ANALYSIS 27Capacity Troubleshooting per Resource – UTRAN CAPACITY ANALYSIS 28Top ‘N’ most congested cells identification 29Top ‘N’ most congested cells identification 30Top ‘N’ most congested cells identification 31Bottleneck analysis RB Allocation Procedure (1/2) 32Bottleneck analysis RB Allocation Procedure (2/2) 33Bottleneck analysis “Unspecified” Blocking detection 34Bottleneck analysis “Unspecified” Detailed investigation method 35Bottleneck analysis BTS Channel elements (CEM) Blocking Detection 36Bottleneck analysis BTS (CE) Resource Load evaluation 37Bottleneck analysis BTS (CE) Detailed investigation method 38Bottleneck analysis Iub Interface Blocking Detection 39Bottleneck analysis Iub Interface Resource Load evaluation 40Bottleneck analysis Iub Interface Detailed investigation method 41Bottleneck analysis: BTS DL RF Power Blocking Detection 42Bottleneck analysis BTS DL RF Power Blocking Detection 43Bottleneck analysis: BTS DL RF Power Resource Load evaluation 44Bottleneck analysis: BTS DL RF Power Detailed investigation method 45Bottleneck analysis: OVSF Codes Blocking Detection 46Bottleneck analysis: OVSF Codes Resource Load evaluation 47Bottleneck analysis: OVSF Codes Resource Load evaluation 48Bottleneck analysis: OVSF Codes Detailed investigation method 49Bottleneck analysis:Blocked traffic investigation 50Case Study: Congestion due to bad parameterization 51Self-Assessment on the Objectives 52End of Module 53

Page 314: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 6

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 6

Table of Contents [cont.]

Switch to notes view!

This page is left blank intentionally

Page 315: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 7

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 7

1 Capacity Monitoring

Page 316: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 8

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 8

1 Capacity Monitoring

KPIs families Reminder

Network Accessibility

NetworkRetainability

NetworkQuality

NetworkTraffic

NetworkCongestion

Counter based KPIs

Capacity/

Load

Call ProfileHSxPA

RRM

NetworkMobility

Page 317: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 9

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 9

1 Capacity Monitoring

UTRAN capacity analysis introduction

� Objective:

� Networks have been deployed focusing on the service availability at the expense of capacity

� Traffic is growing constantly :

� Operators start to experience some congestion in their networks and foresee further

capacity issues.

� Two methodology are possible to follow:

� Reactive capacity planning

� Pro-active capacity planning

T ra ffic evo lu tio n d u rin g las t 6 m o n th s

0

20000000

40000000

60000000

80000000

100000000

120000000

140000000

160000000

180000000

20000000001

-oct

-05

08-o

ct-0

5

15-o

ct-0

5

22-o

ct-0

5

29-o

ct-0

5

05-n

ov-0

5

12-n

ov-0

5

19-n

ov-0

5

26-n

ov-0

5

3 D

ec 0

5

10 D

ec 0

5

17 D

ec 0

5

24 D

ec 0

5

31 D

ec 0

5

07-ja

nv-0

6

14-ja

nv-0

6

21-ja

nv-0

6

28-ja

nv-0

6

4 F

eb 0

6

11 F

eb 0

6

18 F

eb 0

6

25 F

eb 0

6

04-m

ars-

06

11-m

ars-

06

18-m

ars-

06

25-m

ars-

06

1 A

pr 0

6

8 A

pr 0

6

15 A

pr 0

6

CS DL t raffic K B y tes P S DL Tra ffic K B y tes to ta l P S + CS

Page 318: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 10

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 10

1 Capacity Monitoring

UTRAN capacity analysis introduction: Reactive capacity planning

� Done on a regular basis (daily to weekly) in order to react to

observed issues.

� Load and Blocking are monitored and actions are taken based on

threshold comparison.

� First reaction is based on «system optimization» in order to get the

best of the actual system by means of parameter fine tuning.

� Second is to add small H/W component: CEM, E1,..

In summary, the methodology for reactive capacity analysis will be the following:

�Bottleneck identification�Detection and characterization �Resolution by tuning or resource addition

Metrics will have to be monitored on the cells/clusters or RNC. It is recommended to observe the trend of the daily values at least during one week.

Period with abnormal events like holidays, special events, etc, are from high interest regarding capacity aspects and should be monitored as well.

Granularity and period of time have to be defined for monitoring reports, but Busy Hours are the critical periods to study.

Page 319: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 11

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 11

1 Capacity Monitoring

UTRAN capacity analysis introduction: Capacity monitoring

RB Blocking RateRB Blocking RateΣ # 631.[RB estab. unsuccess causes ]

Σ # 691.[Target Call SetUp ]=

RB014_R

RL Set-up Blocking RateRL Set-up Blocking RateΣ #2.[All screenings except timeout ]

Σ #35.[Call Type]=

RL036_CR

RL Addition Blocking RateRL Addition Blocking RateΣ #4.[All screenings except timeout ]

Σ #36.[Call Type]=

RL037_CR

RL Reconfiguration Blocking RateRL Reconfiguration Blocking RateΣ #8.[All screenings except timeout ]

Σ #37.[Call Type]=

RL038_CR

RRC Connection Reject RateRRC Connection Reject RateΣ #404.[RRC failure causes ]

Σ #409.[RRC establishment causes]=

RRC008

#631 VS.RadioBearerEstablishmentUnsuccess: the number of Radio-Bearer establishments that have been rejected by the RNC (no RB Setup Request sent) [screening: RB estab.unsuccess causes]– Reference FDD Cell

#691 VS.RadioBearerSetupRequest: the number of Radio Bearer setup decisions by the RNC, incremented based on reference cell. It counts based on the requested Dowlnlink AsConfID ((DL Access stratum Configuration) . Before CR Q01244717, counters was pegged based on targetDlAsconfId (obtained as output of IRM algorithm), therefore could not be pegged in case of CAC rejection. Since CR Q01244717, counter is pegged accordingly to the requested Downlink AsConfId, then allowing pegging also in case of CAC rejection.

RRC Connection Reject Rate System%50_RRC008_CR

50_RRC008_CR

RNCmetricCongestion

Radio Link Reconfiguration Blocking Rate%50_RL038_CR

50_RL038_CRRNCmetricCongestion

Radio Link Addition Blocking Rate%50_RL037_CR

50_RL037_CRRNCmetricCongestion

Radio Link Setup Blocking Rate%50_RL036_CR50_RL036_CRRNCmetricCongestion

RB Blocking Rate%50_RB014_R50_RB014_RRNCmetricCongestion

Metric name_5.0Metric id_5.0NetworkElement

TypeFamily

Page 320: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 12

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 12

� Principle of congestion detection� Combination of blocking + load

indicators for a specific resource

� 3 states� No blocking � No action

� Blocking, low load � Capacity analysis and tuning required

� Blocking + High load � Capacity analysis and tuning required and/or resource addition

Blocking?Status Green

No action required

Load

=0

Status YellowCapacity analysis/tuning

Status RedCapacity analysis/tuning

and/orResources addition

Low

High

>0

1 Capacity Monitoring

UTRAN congestion detection principles

Page 321: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 13

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 13

� Blocking situation definition : each time the UE requests an UTRAN

resource and is not getting it because the resource is not available.

Additional RL not added in the Active Set (risk of call drop)

Call is not reconfigured (impact on user throughput)

Call admission failure

Effect

- RL Setup Unsuccess

- RL Addition Unsuccess

- RL & RB Reconfiguration Unssuccessfor HSDPA

- RL Reconfiguration Unsuccess (iRM Reconf)

- RL Setup Unsuccess (AON)

- AON/iRM Scheduling failure counters

- RB Establishment Unsuccess

- RL Reconfiguration Unsuccess and Cancel

Monitoring detection method

Lack of resources to perform iRM transitions (AON Upsize, iRM SchedUpgrade)

Call Reconfiguration

No resources available for additional RL

Mobility

Lack of resources at call setup

Call Admission

Blocking CauseCall Phase

1 Capacity Monitoring

Blocking Characterization

Page 322: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 14

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 14

Main possible bottleneck resources monitored at UTRAN Level: � BTS Channel Elements - BTS Resource

� The load can be monitored at BTS level

� Blocking of this resource ⇒ RB rejection or RL Setup/Reconfiguration failures

� Iub ATM� The load can be monitored at BTS level (AAL2&AAL5 traffic)

� alternative solution – monitor the Traffic load per BTS at RNC level

� Blocking of this resource ⇒ RB rejection

� RF power - BTS Resource � The load can be monitored per cell via BTS or RNC counters

� Blocking of this resource ⇒ RB rejection

� OVSF Codes - RNC Resource � The load can be monitored per cell via RNC counters

� Blocking of this resource ⇒ RB rejection

� RNC CPU� The load can be monitored at card level through RNC counters

� Blocking of this resource ⇒ Overload mechanism => RB rejection

1 Capacity Monitoring

Load Resources

Page 323: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 15

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 15

2 Capacity Analysis

Page 324: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 16

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 16

2 Capacity Analysis

Capacity Analysis

� Two strategies are used for capacity analysis

� General network view (top to bottom approach).

� Monitoring the distribution of the congestion & load of the different

network elements for the different resources at network level. Spatial

view/Time view

� Then a threshold for troubleshooting is set to focus on the worst cases per

resources

� Top N most congested network element (Bottom up approach)

� According to one metric, network element are ordered.

� Thresholds for troubleshooting are also set with this methodology.

Page 325: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 17

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 17

2 Capacity Analysis

General Network View: NETWORK CONGESTION AND LOAD

� Congestion at network level is evaluated through Blocking Rate distribution per

cell.

� Blocking Rate per cell is computed as a ratio between the RB Blocking at BH and RB Setup Request at

BH for the entire observation period.

� The BH is based on the most loaded Hour of the day in terms of Radio Bearer Setup Request

and it is calculated for each cell, each day. It can be different for each cell, each day.

� Load is analyzed by bottleneck type at the BH of each Cell:

� CEM Load – through Max of CEMUsed.Avg & Max per cell at BH.

� Iub Load – through Max of Iub Load DL metric calculated per day

� DL Power Load – trough Tx Carrier Power Avg & Max at BH divided by PA Power

available@ref_point (calculated)

� Codes load – through Average of Free codes SF128 Min at BH metric

� PMC(TMU) load – through Average and Maximum PMC Load supporting TMU function for the

entire period (for each RNC)

Page 326: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 18

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 18

2 Capacity Analysis

Congested cells at Network level: Global Blocking – example

• Significant amount of blocking (> 2%) observed during at Cell BH for 22% of the cells

Blocking Rate at cell BH Distribution

4989

2807

2102

1083

273104 37 3 2

0

500

1000

1500

2000

2500

3000

3500

4000

4500

5000

>=0% >0% >0,5% >2% >5% >7% >10% >20% >30%

Blocking rate > x %

Nb

of C

ells

con

cern

ed

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

% o

f cel

ls

Blocked cells Count Blocked cells %

Page 327: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 19

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 19

CEM Load Distribution (Avg & Max @ BH)

49794757

4144

2717

1060

27964 17 6 1

4757

3482

765

116 15 4 0 0 0 00

500

1000

1500

2000

2500

3000

3500

4000

4500

5000

>10% >20% >30% >40% >50% >60% >70% >80% >90% >95%

CEMUsed > x %

Nb

of C

ells

con

cern

ed

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

% o

f cel

ls

Max Load Count Avg Load Count Max Load (%) Avg Load (%)

2 Capacity Analysis

Load at Network level: CEM Load – example

� Only D-BBU is considered in this part, as H-BBU is limited by the max number of HSDPA Users (cf HSDPA CAC)

� CEM Blocking can be triggered at call setup or during inter Node B mobility (Radio Link Setup Failure)

� It can also be triggered during Radio Link Reconfigurations: failures during AO Upgrade, iRM scheduling and RB Adaptation

� BTS Control Plane Monitoring

Direct BTS counters may be used to monitor the capacity consumed by control plan processing:

#10403 VS.CpuLoad.Max.CEM; #10403 VS.CpuLoad.Max.CCM; #10403 VS.CpuLoad.Avg.CEM; #10403VS.CpuLoad.Avg.CCM

� BTS User Plane Monitoring

CEM load in term of user plane capacity may be monitored through the following counter: #10301 VS.CEMUsedDCH.Max

Recommendation:

The counter VS.CEMUsedDCH.Max must not be higher than 71%. Else there is a significant risk that new PS calls to be rejected (PS384 calls first, etc…).

Remark:

To have a view on the amount of blocking due to lack of CEM resources, the counter #10302 VS.CEMAllocFail may be observed.

� Number of BTS with % CEM DCH Used Above 60% : Metric ID: Board003 (Applicability: RNC, network)

This metric allows having a view on the number of BTS that are high loaded on the network. This metric may be applicable to a RNC or to the network. It is applicable on a day minimum time basis.

Recommendation:

To avoid any risk of capacity issue, it should be of course better to have the less possible value for this metrics; nevertheless it is naturally a question of compromise since operators should always want to optimize their investments.

� Percentage of BTS with % CEM DCH Used Above 60% : Metric ID: Board004 ( Applicability: RNC, network)

This metric provides the percentage of BTS loaded at more than 60% on the network. This metric may be applicable to a RNC or to the network. It is applicable on a day minimum time basis.

� DL CEM load Monitoring

Percentage of time the DL CEM load is yellow: #1177 VS.QosDlCemLdClrYellow

Percentage of time the DL CEM load is red: #1178 VS.QosDlCemLdClrRed

These counters provide the percentage of time where the CEM is considered as red or yellow (from a DL point of view). They should be observed during BTS Busy Hour.

Recommendation:

To minimize the impact on the end user these percentage of time should be at low as possible.

� UL CEM load Monitoring

Percentage of time the UL CEM load is yellow: #1180 VS.QosUlCemLdClrYellow

Percentage of time the UL CEM load is red: #1181 VS.QosUlCemLdClrRed

These counters provide the percentage of time where the CEM is considered as red or yellow (from a UL point of view). They should be observed during BTS Busy Hour.

Page 328: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 20

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 20

2 Capacity Analysis

Load at Network level: Iub Load – example

Iub real Load Distribution (Max@BH)

4484

3016

1074

311112 48 18 0 0

0

500

1000

1500

2000

2500

3000

3500

4000

4500

5000

>2% >5% >10% >15% >20% >25% >30% >35% 40%

Iub Load > x %

Nb

of C

ells

con

cern

ed

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

% o

f cel

ls

Max Load Count Max Load (%)

• Iub utilization is very low, not exceeding 35% of the Iub bandwidth. This is not preventing from having Iub blocking as the admission criteria is based on the estimated Iub load (at the RNC)

� As it is based on a BTS counter, the monitored Iub load (@ BH) has to be seen as the average load per hour.

� In the graph, the Max of these averages (for the observation period) is captured.

Limitations

�Not possible to have Iub blocking rate per RB or RAB requested / granted

�If the RB allocated is smaller than the one requested (e.g. I/B384 RB requested and I/B64 is allocated), this is considered as successful RB allocation: no blocking is detected

�No monitoring of blocking rate faced during reconfiguration (RB upsize, AO upsize, iRM upgrade) or during mobility (inter Node B)

Iub Bandwidth monitoring - TrafficIub Load on BTS can be monitored on hourly basis

�Summing ATM cells received by the Node B (#10101, #10110) and averaging it on the monitored period and the # of E1s

�Includes R99 and HSDPA traffic

�For example, on a site with 1 E1: Iub Load Indicator = (#10101 + #10110) / (3600*4528)

Iub Load Indicator on BTS will never reach 100%

�The Iub Load is averaged over a minimal monitoring window (min 1h)

�VP traffic shaping limits the number of ATM cells sent toward the Node B

�Does not monitor blocking of R99 calls (also linked to EBR settings)The bandwidth usage can be monitored on RNC for all the Nodes B with:

�VS.TxMaxCellRate / VS.ProvRate (#20005/#20001) downlink monitoring

�VS.RxMaxCellRate / VS.ProvRate (#20008 /#20001) uplink monitoring

�The screening must be on the ATM Interface for Iub ( ATMIF / 800 )Iub AAL5 & AAL2 discarded frames can be monitored with:

�VS.AAL2NbCPSHecErr + VS.AAL2NbCpsLengthMismatch – (#10105 + #10107)

�VS.AAL5NbLengthErr or VS.AAL5NbCrcFrameErr – (#10112 | #10113)

RNC Iub oversubscription doesn’t impact the BTS, but the Iub bandwidth usage of each RNC should be monitored in order to not approach physical capacity of the link

Iub bandwidth monitoring – Iub Link Color

Monitoring of the real R99 traffic on Iub (measured every 10sec).

Monitor the percentage of time the Iub color is yellow/red

VS.IrmTimeDlIubTransportColorYellow - provides the ratio of time a cell is considered yellow for Downlink IubTransport by iRM during a reporting period (Average value). The minimum value allows to know if the cell has never been considered yellow by the iRM during the reporting period. The maximum value allows to know if the cell has been considered yellow, at least once, by the iRMduring the reporting period

VS.IrmTimeDlIubTransportColorRed - provides the ratio of time a cell is considered red for Downlink IubTransport by iRM during a reporting period (Average value). The minimum value allows to know if the cell has never been considered red by the iRM during the reporting period. The maximum value allows to know if the cell has been considered red, at least once, by the iRM during the

Page 329: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 21

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 21

2 Capacity Analysis

Load at Network level: DL Power Load – example

DL RF Power Distribution (Avg & Max)

49574780

4326

3080

1486

514

151 45 8 3 1

4954

4390

2503

28383 26 12 3 0 0 0

0

500

1000

1500

2000

2500

3000

3500

4000

4500

5000

>10% >20% >25% >30% >35% >40% >45% >50% >60% >70% >80%

DL Power Load > x %

Nb

of C

ells

con

cern

ed

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

% o

f cel

ls

Max Load Count Avg Load Count Max Load (%) Avg Load (%)

� RF available power computed on RNC is used for Call Admission of R99 calls using either algo1 or algo2

� Lack of RF Power will result in blocking of R99 calls if iRM Cell Color based on power is not activated

� RF power usage for R99 calls is optimized by iRM Cell Color based on Power Usage: a new call is not blocked but it is downgraded to a lower RB

� Lack of RF Power will result in low performance of HSDPA calls and PA overload

Page 330: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 22

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 22

2 Capacity Analysis

Load at Network level: Codes Load – example

� Available OVSF codes are monitored and used by the RNC for Call Admission of any radio link

(regarding their SF).

� Lack of codes will result in blocking of the radio links using the smallest spreading factors

� DL PS384 will be first to be blocked (uses 1 code SF8 � 16 codes at SF128 level)

� OVSF Code usage for all calls is optimized by iRM Cell Color based on code tree usage

OVSF Codes Load Distribution (Avg & Max @ BH)

4933 4873

3377

1352

459

54 12 2 0

4797

3746

745

93 10 0 0 0 00

500

1000

1500

2000

2500

3000

3500

4000

4500

5000

>5% >10% >20% >30% >40% >50% >60% >70% >80%

Codes Load > x %

Nb

of C

ells

con

cern

ed

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

% o

f cel

ls

Max Load Count Avg Load Count Max Load (%) Avg Load (%)

Page 331: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 23

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 23

2 Capacity Analysis

Load at Network level: RNC CPU Load – example

� HSDPA has about the same impact on RNC CPU as the one of a PS call (additional processing is

performed by Node B – no Diversity on RNC).

� Only TMU CPU load is available through:

� E3PrLoadCnTmu.Sbc_Max & Avg (#3001_Max & #3001_Avg).

� Load of PMC-RAB can’t be monitored.

TMU load Avg & Max

0

10

20

30

40

50

60

70

80

90

100

13/3/06

0:00

13/3/06

6:00

13/3/06

12:00

13/3/06

18:00

14/3/06

0:00

14/3/06

6:00

14/3/06

12:00

14/3/06

18:00

15/3/06

0:00

15/3/06

6:00

15/3/06

12:00

15/3/06

18:00

16/3/06

0:00

16/3/06

6:00

16/3/06

12:00

16/3/06

18:00

17/3/06

0:00

17/3/06

6:00

17/3/06

12:00

17/3/06

18:00

18/3/06

0:00

TM

U L

oad

(%)

GRENOBLE1 Avg

GRENOBLE1 Max

LYONECUL1 Avg

LYONECUL1 Max

MONTPELL1 Avg

MONTPELL1 Max

RNCs

Page 332: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 24

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 24

Load at Network level: RNC CPU Load – Monitoring

� Load of PMC-RAB can’t be monitored.

� It can be evaluated by summing all the traffic at RLC level:

� Sum (DedicatedDownlinkKbytesRlcReferenceCell, all UL/DL_bit_rate)

� When the RNC is in overload, establishment of new calls are rejected, this

situation can be monitored:

� RRC.FailConnEstab_6 (#404) – Rejection of mobiles due to RNC Overload

� UnhandledPagingRequestsCs_4 (#810) – Paging not processed due to Overload

� VS.RadioBearerEstablishmentUnsuccess_6 (#631_6) – Lack of RNC processing resources

Max should be <70% during busy hour.

Network operationsimpact the counter and must be removed

CPU load of the signaling units of the RNC

Very low chances to trigger

Usage_TMU_Avg_RNC

Usage_TMU_Max_RNC

User RejectedRejection of new RRC Connection due to RNC Overload protection mechanismBlocking_Overload_RNC

ThresholdUsageMetric

Page 333: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 25

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 25

3 Capacity Troubleshooting

Page 334: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 26

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 26

3 Capacity Troubleshooting

Capacity Troubleshooting per Resource – UTRAN CAPACITY ANALYSIS

� The following UTRAN capacity counter table will be developed in the followings slides:

Upgrade to RNC

higher model

(add more packet

server)

No Tuning

Available#631 VS.RadioBearerEstablishmentUnsuccess.[6]#3001 VS.E3PrLoadCnTmu.Sbc

RNC

TMU CPU

E1EBR#631 VS.RadioBearerEstablishmentUnsuccess.[9-14]

#10101 VS.AAL2NbReceivedCell

#10110 VS.AAL5NbReceivedCell

#10115 VS.AAL2NbSentCell

#10116 VS.AAL5NbSentCell

Transport

New CEM#10302 VS.CEMAllocFail#10301 VS.CEMUsedChannelElements

2nd frequency#631 VS.RadioBearerEstablishmentUnsuccess.[2]#1126

VS.IRMTimeFreeDlCodesBySpreadingFactor

OVSF

Codes

2nd frequency;

Site DensificationIRM CAC

Cell FACH

(AO-step 4)

#631 VS.RadioBearerEstablishmentUnsuccess.[1]

#1124 VS.IRMTimeCellRadioColorRed

#1125 VS.IRMTimeCellRadioColorYellow

#1127 VS.IRMTimeCellRadioColorGreen

DL RF

Power

ResourceadditionTuningBlocking countersLoad counters

Bottlenecks

ResolutionMonitoring

Cell

Site

RNC

Page 335: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 27

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 27

3 Capacity Troubleshooting

Capacity Troubleshooting per Resource – UTRAN CAPACITY ANALYSIS

X % of Cells with Blocking > 2%

Capacity Dashboard

Capacity Analysis

Dashboard to provide a synthetic UTRAN resource usage and evolution

CAPACITY PANEL REPORT � Monitored on daily basis at RNC level

Criteria to start troubleshooting exercise

Troubleshooting : capacity analysis of UTRAN resources

RESOURCE PANELRADIO BEARER BLOCKING REPORT – FDDCELL

Page 336: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 28

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 28

DL Codes Capacity Analysis –RNC level

ATM & HW Capacity Analysis –RNC level

Accessibility Congestion Analysis –Network level

High Mean RB

Blocking rate

Determine the RNCwith Lack of DL Codes

High Mean RB Blocking rate

due to Lack of DL Codes

High Mean RB Blocking rate

due to Unspecified reasonsThe bad day(s)

identified:

The RNC identified

High Mean RB Blocking rate

due to Lack of DL Power

DL Power Capacity Analysis –RNC level

Determine the RNCwith Lack of DL Power

Refer to counter #0631

Determine the RNCwith High Blocking due to

Unspecified reasons

3 Capacity Troubleshooting

Capacity Troubleshooting per Resource – UTRAN CAPACITY ANALYSIS

Metric id_5.0 Metric name_5.0

50_RB014_C RB Blocking Rate%50_RB014_C

#631-0 VS.RadioBearerEstablishmentUnsuccess.InvalidRabParametersValue

#631-10 VS.RadioBearerEstablishmentUnsuccess.LackBwthIu

#631-14 VS.RadioBearerEstablishmentUnsuccess.LackBwthIub

#631-12 VS.RadioBearerEstablishmentUnsuccess.LackBwthIur

#631-9 VS.RadioBearerEstablishmentUnsuccess.LackCidIu

#631-13 VS.RadioBearerEstablishmentUnsuccess.LackCidIub

#631-11 VS.RadioBearerEstablishmentUnsuccess.LackCidIur

#631-7 VS.RadioBearerEstablishmentUnsuccess.LackOfNodeBDlProcessingResources

#631-8 VS.RadioBearerEstablishmentUnsuccess.LackOfNodeBUlProcessingResources

#631-6 VS.RadioBearerEstablishmentUnsuccess.LackOfRncProcessingResources

#631-1 VS.RadioBearerEstablishmentUnsuccess.UnavailableDlCodeResources

#631-2 VS.RadioBearerEstablishmentUnsuccess.UnavailableDlPowerResources

#631-3 VS.RadioBearerEstablishmentUnsuccess.Unspecified

This chart allows to identify the spatial, temporal and main causes to be used for capacity analysis

Metric id_5.0 Metric name_5.0

50_RB014_C RB Blocking Rate%50_RB014_C

#631-0 VS.RadioBearerEstablishmentUnsuccess.InvalidRabParametersValue

#631-10 VS.RadioBearerEstablishmentUnsuccess.LackBwthIu

#631-14 VS.RadioBearerEstablishmentUnsuccess.LackBwthIub

#631-12 VS.RadioBearerEstablishmentUnsuccess.LackBwthIur

#631-9 VS.RadioBearerEstablishmentUnsuccess.LackCidIu

#631-13 VS.RadioBearerEstablishmentUnsuccess.LackCidIub

#631-11 VS.RadioBearerEstablishmentUnsuccess.LackCidIur

#631-7 VS.RadioBearerEstablishmentUnsuccess.LackOfNodeBDlProcessingResources

#631-8 VS.RadioBearerEstablishmentUnsuccess.LackOfNodeBUlProcessingResources

#631-6 VS.RadioBearerEstablishmentUnsuccess.LackOfRncProcessingResources

#631-1 VS.RadioBearerEstablishmentUnsuccess.UnavailableDlCodeResources

#631-2 VS.RadioBearerEstablishmentUnsuccess.UnavailableDlPowerResources

#631-3 VS.RadioBearerEstablishmentUnsuccess.Unspecified

Page 337: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 29

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 29

3 Capacity Troubleshooting

Top ‘N’ most congested cells identification

� Counters Granularity: Hour

For each Cell : 4 metrics calculation

∑∑∑∑RbRejected@BH where BH=Hour[Max(RbSetReq)] days

∑∑∑∑RbRejected@BkH where BkH=Hour[Max(RbRejected)] days

∑∑∑∑ ∑∑∑∑ RbRejecteddays hour

BHBKRate(%) = RbRejected / RbSetReq (@BH)

Condition1= NbrDays[BHBKRate(%)> 0%]Condition2= NbrDays[BHBKRate(%)> 2%]

Note: RbRejected corresponds to counter VS.RadioBearerEstablishmentUnsucces (without screening 0)

RbSetReq corresponds to counter VS.RadioBearerSetupRequest

• Method aims to create a list of most representative cells in terms of blocking by taking into account the amount of rejections at different periods of the day but also the persistence in time of the issue.

Page 338: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 30

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 30

3 Capacity Troubleshooting

Top ‘N’ most congested cells identification

CellsRanking[∑∑∑∑ ∑∑∑∑ RbRejected]day hour

CellsRanking[∑∑∑∑RbRejected@BH]

CellsRanking[∑∑∑∑RbRejected@BkH]

+

Cells Filtering [Condition1>X & Condition2>Y ]

X > Y

Bottleneck Identification[RbRejected Screening]

Final cells List to investigate

Example of Study :Obs.Period = 14 days

X= 7Y=4

BK Day Setup Day Bk rate day Bk & BH Setup & BH Bk rate BH Bk & BkH Setup & BkH Bk rate BhK rankdays with

Bk>2%days with

Bk>0%796 75504 1,1% 230 6126 3,8% 516 4638 11,1% 1 4 7515 23104 2,2% 142 2382 6,0% 227 2045 11,1% 3 7 8279 21612 1,3% 188 2313 8,1% 227 1909 11,9% 6 7 9338 27698 1,2% 124 2797 4,4% 224 2352 9,5% 6 5 10504 1962 25,7% 143 370 38,6% 158 314 50,3% 7 8 8297 20546 1,4% 101 2483 4,1% 193 1782 10,8% 9 4 7317 20132 1,6% 81 2054 3,9% 192 1507 12,7% 12 4 7

Page 339: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 31

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 31

� Ranking is helping to focus on cells with important amount of traffic and blocking

(putting in lower priority low loaded cells or low blocked cells)

� the temporal factor is considered during the filtering – only cells with constant

blocking are picked up

� The double filter, even it is not mandatory (simple filter could be enough for most of

the cases), add to detect cells exceeding a given threshold (condition 1) and also

cells with constant load (condition 2)

=> The method can be improved by analyzing two different BH (CS&PS)

3 Capacity Troubleshooting

Top ‘N’ most congested cells identification

BK Day Setup Day Bk rate day Bk & BH Setup & BH Bk rate BH rank Blocking Causedays with

Bk>2%days with

Bk>0%796 75504 1,1% 230 6126 3,8% 1 Unspecified 4 7515 23104 2,2% 142 2382 6,0% 3 LackOfBandwidth & Unspecified 7 8279 21612 1,3% 188 2313 8,1% 6 Unspecified 7 9338 27698 1,2% 124 2797 4,4% 6 Unspecified 5 10504 1962 25,7% 143 370 38,6% 7 LackOfBandwidth 8 8297 20546 1,4% 101 2483 4,1% 9 LackOfBandwidth & Unspecified 4 7317 20132 1,6% 81 2054 3,9% 12 LackOfBandwidth & Unspecified 4 7245 17564 1,4% 105 2036 5,2% 12 LackOfBandwidth & Unspecified 6 7267 17850 1,5% 80 1949 4,1% 16 LackOfBandwidth & Unspecified 5 7247 20098 1,2% 86 2213 3,9% 17 Unspecified 5 8279 7600 3,7% 86 818 10,5% 21 LackOfBandwidth 8 8179 12697 1,4% 103 1369 7,5% 22 LackOfBandwidth & Unspecified 7 9249 5761 4,3% 76 713 10,7% 22 LackOfBandwidth 8 9172 13129 1,3% 100 1378 7,3% 23 Unspecified 6 9193 14707 1,3% 76 1690 4,5% 25 Unspecified 5 7310 4504 6,9% 70 739 9,5% 26 LackOfBandwidth 11 11144 11916 1,2% 74 1393 5,3% 31 Unspecified 6 7161 13154 1,2% 84 1524 5,5% 31 LackOfBandwidth & Unspecified 6 7145 9049 1,6% 59 1034 5,7% 43 Unspecified 5 8161 14210 1,1% 58 1457 4,0% 44 Unspecified 4 7215 10344 2,1% 52 1101 4,7% 52 LackOfBandwidth & Unspecified 7 9

List of Cells

Page 340: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 32

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 32

3 Capacity Troubleshooting

Bottleneck analysis RB Allocation Procedure (1/2)

Radio Bearer Setup Complete

Radio Link Reconfiguration Prepare

Radio Bearer Setup

Radio Link Reconfiguration Ready

RAB Assignment Request

RAB Assignment Response

Radio Link Reconfiguration Commit

UE Node B RNC CN - CS

UP / DL Synchronization

UP / UL Synchronization

AAL2 / ERQ

AAL2 / ECF

UP / Initialization

UP / Initialization Ack.

CAC

1

2

3

4

5

6

7

8

Page 341: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 33

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 33

3 Capacity Troubleshooting

Bottleneck analysis RB Allocation Procedure (2/2)

1

2 #0631.0 - RB Establishment Unsuccess cause “ Invalid RAB parameters value ”

#0625 - RB Setup Request (Downlink Access Stratum)

3 #0631 - RB Establishment Unsuccess1 - “Unavailable code resource”2 - “Unavailable Power resource”4 - “Lack of bandwidth” (replaced by screenings #10, #12 and #14 in UA04.2 )5 - “Lack of CID” (replaced by screenings #9, #11 and #13 in UA04.2)6 - “RNC Processing resources”9 - “Lack of CID on IU” (introduced in UA04.2)

10 - “Lack of bandwidth on IU” (introduced in UA04.2)11 - “Lack of CID on IUR” (introduced in UA04.2)12 - “Lack of bandwidth on IUR” (introduced in UA04.2)13 - “Lack of CID on IUB” (introduced in UA04.2)14 - “Lack of bandwidth on IUB” (introduced in UA04.2)

4 #0023 – Radio Link Reconfiguration Request (Downlink Access Stratum) (introduced in UA04.2)5 #0007 – Radio Link Reconfiguration Success (Downlink Access Stratum)

#0008 – Radio Link Reconfiguration Prepare Unsuccess0 - Reception of RL Reconfiguration Failure 1 - Time-out2 - Rrm refusal (ie: no more power available, no more code available, ...)3 - I-Node refusal (replaced by screenings #6, #7 and #8 in UA04.2)6 - Lack of CID on the Iub (introduced in UA04.2)7 - Lack of bandwidth on the Iub (introduced in UA04.2)8 - I-Node refusal (ie: other I-Node resource not av ailable ...) (introduced in UA04.2)

6 #0631.3 - RB Establishment Unsuccess cause “ Unspecified ”

7 #0010 - Radio Link Reconfiguration Commit (Downlink Access Stratum)#0009 - Radio Link Reconfiguration Cancel (Downlink Access Stratum)

8 #0601 - Radio Bearer Setup Success (Downlink Access Stratum)#0602 - Radio Bearer Setup Unuccess (Failure cause)

Page 342: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 34

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 34

� The “Unspecified” RB Establishment Unsuccess is not always directly linked to a specific

UTRAN bottleneck, thus the association with the load is not obvious for this blocking

cause.

� This blocking cause is identified through screening “Unspecified” of the VS.RadioBearerEstablishmentUnsuccess counter - See bullet 6 in the RB Allocation Procedure Data Flow Diagram.

� It covers the following Call Setup failures causes:

� CEM resources shortage

� User Plane Initialization failure between RNC and Core Network (Iu issues).

� From UA4.2 the HSDPA CAC rejected calls are also pegging this counter.

� It is a good method to detect the CEM resources shortage as the CEMAlloc.Fail counter has

some limitations

� CEM Allocation failure during call setup & upsize:

� RadioLinkReconfigurationPrepareUnsuccess.RadioLinkReconfigurationFailure (#0008)

� Does not detect CEM failure during mobility (Soft HO)

� included in the counter RadioLinkSetupUnsuccess.RadioLinkSetupFailure

� HSDPA CAC is also peg through the UnsuccesfulHsdpaCac counter (#0958)

3 Capacity Troubleshooting

Bottleneck analysis “Unspecified” Blocking detection

Page 343: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 35

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 35

RB Establishment UnsuccessUnspecified > 0

Stop

RL Reconfiguration Cancel > 0 And correlated in time with

RB Establishment UnsuccessUnspecified

no

yes

noPossible RNC - Core Network UPlane initialization iss ues. Confirm if the issue occurs on several BTSs of the same RNC (depending on their traffic load).It is possible to identify the Core domain generati ng the issue by checking the RadioLinkReconfigurationCancel.DlAccessStratumConf for CS & PS Check Core Network Counters & Alarms for more detai ls

3 Capacity Troubleshooting

Bottleneck analysis “Unspecified” Detailed investigation method

RL Reconfiguration Prepare UnsuccessRLReconfFailure ≥ RB Establishment Unsuccess

Unspecified

Call allocation failure due to lack of CEM resource s (HBBU or DBBU) => relay on CEM Bottleneck analysis

yes

yes

no

Unsucc. HSDPA CAC > 0 And correlated in time with

RB Establishment UnsuccessUnspecified

The HSDPA limit of 48 UEs per cell is reached (HSDPA CAC) yes

Page 344: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 36

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 36

3 Capacity Troubleshooting

Bottleneck analysis BTS Channel elements (CEM) Blocking Detection

� The CEM blocking is particular annoying as this resource is not managed by the RNC. Thus,

if no CEM resources available, the call is released (no iRM downgrade based on this

resources load is possible until UA5.0)

� Call admission blocking due to CEM resources shortage can be detected by two methods:

1. Using the VS.RadioBearerEstablishmentUnsuccess.Unspecified counter

2. Using BTS counter CEMAllocFail. Method drawbacks:

� This counter provides the % of CEM resources requests that are refused from total CEM resources

requests. All requests are considered: RL Setup SRB or TRB, RL Reconfiguration Up or Down… thus it

will be slightly incremented even in case of high blocking.

� It is rounded to Integer (if 0.8% is calculated => 0% is displayed)

� Recommendation: use the first method and only confirm (if it is the case) with the

CEMAllocFail method.

Page 345: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 37

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 37

3 Capacity Troubleshooting

Bottleneck analysis BTS (CE) Resource Load evaluation

� CEM load (for D-BBU only) is measured by means of CEMUsed (BTS counter)

� The CEMUsed screenings (Avg, Min, Max.) allows to:

� Min – during the night it will provide info on Common Channels utilization (usually 18% for STSR1 on 1

iCEM64)

� Avg – Average load during one Hour – used for dimensioning purposes

� Max – allows to determine the moments when the “alarm” thresholds were exceeded triggering

blocking.

� CEMUsed booking levels for

the most used RABs in

case of 1 iCEM64:

� Recommendation: set an Yellow alarm monitoring trigger for CEMUsed.Avg exceeding 50%

and a red one for CEMUsed.Max exceeding constantly 70%.

� CEM load (HBBU) cannot be directly monitored in UA4.2. Alternative through

DlAsConfIdAvgNbrEstab.Max is proposed (next slide). Complete solution in UA5.0

65%PS 384/0 (HSDPA)

72%PS 64/384

85%

98%

Block. Thresholds

In case of 1 D-BBU

PS 64/64, 128/128, 128/384, 128/0 (HSDPA)

CS 12.2/12.2

RAB Type (UL/DL)

Page 346: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 38

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 38

MAX [DlAsConfIdAvgNbrEstab.Max (scr.27)] ~ 48

“Unspecified” analysis shows CEM blocking Stop

CEMAllocFail > 0

no

yes

yes (Optional)

CEMAllocFail could display “0” even with High PS blocking if there are many resources requests that are accepted (small RABs) => continue CEM investigation

no

-Potential issues with CEM configuration (check CCP configuration).- STSR2 is activated and the traffic is unbalanced between frequencies => Add additional CEM resources

3 Capacity Troubleshooting

Bottleneck analysis BTS (CE) Detailed investigation method

yes

CEMUsed.Max > 70%

Plan to add additional CEM (DBBU) resources

yes no

Call allocation failure due to lack of CEM

yesno Plan to add additional CEM (HBBU) resources

Page 347: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 39

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 39

3 Capacity Troubleshooting

Bottleneck analysis Iub Interface Blocking Detection

� The Iub resources management is done at RNC Level. From UA4.2 this

resource is taken into account in the iRM @ CAC mechanism.

� Call admission blocking due to Iub resources shortage can be detected

through the counter:

VS.RadioBearerEstablishmentUnsuccess.LackOfBandwidth & LackOfCid

� Additional indication about call admission blocking and iRM upgrade

procedures fail due to lack of Iub resources is provided by:

VS.RadioLinkReconfigurationPrepareUnsuccess. INodeRefusal (enhanced

by two screenings since UA4.2 LackBwthIub & LackCid)

� When the mobility is affected by the lack of Iub resources the following

counter will be pegged: VS.RadioLinkSetupUnsuccess.INodeRefusal

(enhanced by LackBwthIub & LackCid)

VS.RadioLinkReconfigurationPrepareUnsuccess - #8

This measurement is based on four different events: - Receipt of a NBAP RADIO LINK RECONFIGURATION

FAILURE message sent by Node B to the Controlling RNC in response to a

RADIO LINK RECONFIGURATION PREPARE message. - No reception of RADIO LINK RECONFIGURATION

READY message before a time-out - RRM refusal (e.g. no power allocation,

no code allocation) - RNC I-Node refusal (e.g. no CID allocation)

Screenings:

Sub-Counter #0 : RADIO_LINK_RECONFIGURATION_FAILURE

• Sub-Counter #1 : Timeout nbap

• Sub-Counter #2 : Rrm refusal

• Sub-Counter #3 : Unused

• Sub-Counter #4 : Rrm refusal (DL NodeB resource lack, or NodeB resource lack)

• Sub-Counter #5 : Rrm refusal (UL NodeB resource lack)

• Sub-Counter #6 : Lack of CID on the Iub

• Sub-Counter #7 : Lack of bandwidth on the Iub

� Sub-Counter #8 : INode refusal

Page 348: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 40

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 40

3 Capacity Troubleshooting

Bottleneck analysis Iub Interface Resource Load evaluation

� Iub Load indicators available in UA5.0:

� Real load of the Iub calculated from BTS Transport counters (average/hour):

Monitored_Iub_Load = (VS.AAL2NbReceivedCell + VS.AAL5NbReceivedCell) / (4528x3600)

� The Iub Load estimated by the RNC and used by iRM CAC:

RNC_Estimated_Iub_load = (∑∑∑∑ RadioLinkEstablishedPerCell.Avg) * ECR * SrHO% (at cell level)

The ECRs are calculated from configured EBRs.

� If the EBR configuration is very conservative (AF 100% considered for all RBs,

especially the big PS RBs), the gap between the Monitored_Iub_Load and

RNC_Estimated_Iub_load will be important and the blocking will be seen with very low

Iub traffic.

� From UA4.2, the real Iub load is taken into consideration in the iRM and it will be

possible to monitor the percentage of time a certain load level was reached

through iRM specific counters:

� #1155 VS.IRMTimeCellDlIubTransportColorYellow (recommended threshold @ 70%)

� #1148 VS.IRMTimeCellDlIubTransportColorRed (recommended threshold @ 90%)

Page 349: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 41

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 41

RB Establishment UnsuccessLack of bandwidth > 0

OrLack of CID > 0

yes

3 Capacity Troubleshooting

Bottleneck analysis Iub Interface Detailed investigation method

yes (optional)

yes

Stopno

IRMTimeCellDlIubTransportColorRed ≥ X%

Plan to add additional PCM resources

yes

Call allocation failure due to Iub Lack of bandwidth or CIDs

no

Do EBR Tuning

RL Reconfig Prepare UnsuccessINodeRefusal ≥ RB Establishment Unsuccess

LackOfBandwidth

Call allocation & iRM Sched. upgrade failure due to lack of Iub Resources

Transport configuration allows EBR Tuning?

no yes

- X can vary with EBR config., traffic type (R99/HSDPA) and Y2R/R2Y Iub thresholds- For R99, EBR at max and Y2R/R2Y Iub = 90%/80%, X is expected to be ≤ 1%Additional analysis is needed for HSDPA

RB Establishment Unsuccess “LackOfBandwidth” was replaced in UA4.2 by• LackOfBandwidthOnIu• LackOfBandwidthOnIur• LackOfBandwidthOnIubAnd “Lack of CID”• LackOfCidOnIu• LackOfCidOnIur• LackOfCidOnIub

RadioLink Reconfiguration Prepare Unsuccess “INodeRefusal” is completed since UA4.2 with:• LackBwthIub• LackOfCid

Page 350: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 42

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 42

3 Capacity Troubleshooting

Bottleneck analysis: BTS DL RF Power Blocking Detection

� The DL Power management is done by the RNC. This resource is taken into

account in the iRM @ CAC mechanism

� the blocking due to this resource can be controlled through cell color thresholds

� Call admission blocking R99 due to DL RF Power shortage can be detected

through the counter:

� VS.RadioBearerEstablishmentUnsuccess.UnavailableDlPowerResources (#631)

� It can be monitored also by the following counter (includes the OVSF blocking)

� RadioLinkReconfigurationPrepareUnsuccess.RrmRefusal (#8)

� Blocking of the mobility of the R99 calls due to lack of power (& codes) can be

monitored :

� RadioLinkSetupUnsuccess.RrmRefusal (#2) for Soft Handover Mobility

� RadioLinkAdditionUnsuccess.RrmRefusal (#4) for Softer Handover Mobility

Page 351: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 43

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 43

3 Capacity Troubleshooting

Bottleneck analysis BTS DL RF Power Blocking Detection

� When iRM Cell Color on Power is activated, the RB establishment is not failing but it is

downgraded to a lower RB thanks to iRM table.

� Cell Color (due to power or codes) can be monitored with:

� VS.IRMTimeCellColorYellow (#1125)

� VS.IRMTimeCellColorRed (#1124)

Avg gives a percentage of time the cell is on a certain color and max provides information if cell

has been of that color at least once in the monitored period.

� iRM congestion due to power can be monitored by:

� VS.IrmPreemptionTimeCellColorCongestedBecauseOfPower (#1138)

Page 352: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 44

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 44

3 Capacity Troubleshooting

Bottleneck analysis: BTS DL RF Power Resource Load evaluation

� Power utilization is measured by means of VS.AvgTxPower counter

� Power usage is computed based on PA_Power @ Reference point

Power_Load (%) = VS.AvgTxPower / PA_Power@Refpoint

PA_Power@Refpoint = maxPowerAmplification – TotalLoss

� Call Admission is applied on 85% of Power_Traffic:

Power_Traffic= PA_Power@Refpoint – Power_Common_Channel

� Recommendation: set an alarm monitoring trigger for Power_Load Max (based on

VS.AvgTxPower.Max) exceeding constantly 80%

� Number of times that the total transmit power exceeds 90% of the max Tx

Power:� VS.HsdpaPAOverload (#10817) – sampling 100ms

� Power allocated for HSDPA calls:� VS.HsdpaHSPDSCHTxPwr (#10801) - Unit: 100mW for all Codes - sampling: 2ms

� VS.HsdpaHSSCCHTxPwr (#10803) - Unit: 100mW for all HS-SCCH – sampling: 2ms.

Page 353: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 45

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 45

RB Establishment UnsuccessUnavailableDlPowerResources > 0

RL Reconfig Prepare UnsuccessRrmRefusal > RB Establishment Unsuccess

UnavailableDlPowerResources

yes

3 Capacity Troubleshooting

Bottleneck analysis: BTS DL RF Power Detailed investigation method

yes (optional)

yes

Stopno

Power_Load.Max (%) > 80 %

yes

Call allocation failure due to lack of DL Power resources

Call allocation & iRM Sched. upgrade failure due to lack of DL Power resources

- Reduction of iRM Power Thresholds- Tuning of Power allocation of Radio Bearer- Tuning of Power allocation of common Channels- Add a new capacity Layer

Power_Load % = VS.AvgTxPower / PA_Power@Refpoint

PA_Power@Refpoint = Min(PAMax – Loss, MaxTxPower)

Page 354: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 46

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 46

3 Capacity Troubleshooting

Bottleneck analysis: OVSF Codes Blocking Detection

� The OVSF codes management is done by the RNC.

� This resource is taken into account in the iRM @ CAC mechanism (the blocking due

to this resource can be controlled through cell color thresholds).

� Call Setup blocking due to OVSF Codes shortage can be detected through the

counter:

� VS.RadioBearerEstablishmentUnsuccess.UnavailableDlCodeResources (#631)

� Additional indication about call admission blocking and iRM upgrade procedures

fail due to lack of codes is provided by:

� VS.RadioLinkReconfigurationPrepareUnsuccess.RrmRefusal

� When the mobility is affected by the lack of codes the following counter will be

pegged: VS.RadioLinkSetupUnsuccess.RrmRefusal

� The RrmRefusal cause is also covering the lack of DL Power resources.

Page 355: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 47

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 47

3 Capacity Troubleshooting

Bottleneck analysis: OVSF Codes Resource Load evaluation

� Codes load is measured by means of VS.IRMTimeFreeDlCodesBySpreadingFactor counter.

It is recommended to use SF128 as it has a better granularity (used for Signaling and for

Voice)

� Following metric is to be used to monitor the Codes load:

128_Codes_load (%) = (128 - VS.IRMTimeFreeDlCodesBySpreadingFactor.128) / 128

� The VS.IRMTimeFreeDlCodesBySpreadingFactor screenings (Avg, Min, Max.) allows to:

� Max – during the night it will provide info on Common Channels utilization (usually 3-4%)

� Min – allows to determine the moments when the “alarm” thresholds were exceeded

triggering blocking.

� OVSF Codes bloking levels for the most used DL RBs:

78%PS 384

90%PS 128

97%

99%

SF128_Blocking threshold

PS 64

CS12.2

RB Type (DL)

� HSDPA Cell with

� 5 HS-PDSCH & 2 HS-SCCH: 45% of

Code Load

� 10 HS-PDSCH & 2 HS-SCCH: 76%

of Code Load

Page 356: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 48

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 48

3 Capacity Troubleshooting

Bottleneck analysis: OVSF Codes Resource Load evaluation

� When iRM Cell Color on codes is activated, the RB is downgraded to a lower

RB thanks to iRM table.

� Cell Color (due to power or codes) can be monitored with:

� VS.IRMTimeCellColorYellow (#1125)

� VS.IRMTimeCellColorRed (#1124)

� Avg gives a percentage of time the cell is on a certain color

� Max provides information if cell has been of that color at least once in the

monitored period.

� iRM congestion due to codes can be monitored by:

� VS. IrmPreemptionTimeCellColorCongestedBecauseOfOvsfCodes

(#1137)

Page 357: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 49

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 49

RB Establishment UnsuccessUnavailableDlCodeResources > 0

RL Reconfig Prepare UnsuccessRrmRefusal > RB Establishment Unsuccess

UnavailableDlCodeResources

yes

3 Capacity Troubleshooting

Bottleneck analysis: OVSF Codes Detailed investigation method

yes (optional)

yes

Stopno

128_Codes_load_Max (%) > 70%

Plan to add additional frequency (additional codes tree)

yes

Call allocation failure due to lack of OVSF codes

iRM threshold for codes (green2Yellow & yellow2RedC LCThreshold) reduction is another alternative but it has to be c orrelated with operator strategy against user service quality…

yes (optional)

Call allocation & iRM Sched. upgrade failure due to lack of OVSF codes

Page 358: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 50

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 50

3 Capacity Troubleshooting

Bottleneck analysis:Blocked traffic investigation

� Even it is an optional step in the capacity bottlenecks study, it is an important

pointy of investigation which can provide important information on the cause and the

source of blocking.

� Once the bottleneck identified, the blocking investigation can be pushed further by

analyzing the difference:

VS.RadioBearerSetupRequest.DlAccessStratumConf.X – VS.RadioBearerSetupSuccess.DlAccessStratumConf.X (X from 0 to 29)

� This will reveal the RB blocked an can indicate some actions to take:

� If CS is blocked, there is not too much tuning to perform – resources addition is needed.

� If PS is blocked there is still iRM tuning to foresee before deciding to add resources.

Page 359: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 51

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 51

3 Capacity Troubleshooting

Case Study: Congestion due to bad parameterization

�Monitoring CEM load

�NodeB1 has CEM rejection with a very low iCEMused.

�NodeB1 has 3 CEMs inserted on the BTS but only 1 vcc CCP ,then CEM in the board 7 and 8 are in state coldStandby (can not carry traffic) and creating CEM cac rejection on this bts.

�There is some CEM installed on the BTS but not carrying traffic because they do not have CCP VCC provisioned

�Superpose number of simultaneous Radio Link per Cell with Blocking

� When the cell hosts 2 simultaneous 384 RL then blocking happens

� Iub ATM load < 3% but AAL2 CAC refuses several calls setup

�The limiting resource is Iub DL load which exhibits the lowest load among all resources

Parameter audits to avoid some Performance & Capaci ty issues

RB Blocking in CELL3 Vs Max PS384 RL

00,5

11,5

22,5

33,5

44,5

09:00

10:00

11:00

12:00

13:00

14:00

15:00

16:00

17:00

18:00

19:00

20:00

21:00

22:00

23:00

0

0,5

1

1,5

2

2,5

Radio Bearer Establishment Unsuccess Max PS384 Radio Link in the cell 3

NodeB1_iCemUsedEvolution

05

101520253035

Day

1 0

1:00

Day

1 0

9:00

Day

1 1

7:00

Day

2 0

1:00

Day

2 0

9:00

Day

2 1

7:00

Day

3 0

1:00

Day

3 0

9:00

Day

3 1

7:00

Day

4 0

1:00

Day

4 0

9:00

Day

4 1

7:00

Day

5 0

1:00

Day

5 0

9:00

Day

5 1

7:00

Day

5 0

1:00

Day

5 0

9:00

Day

5 1

7:00

Day

6 0

1:00

Day

6 0

9:00

Day

6 1

7:00

Day

7 0

1:00

Day

7 0

9:00

Day

7 1

7:00

0

1

2

CEMUsedMax%

CEMUsedMin%

CEMAllocFail

INVccGroup

VCC OAM

VCC DS traffic

VCC NodeBCPVCC CCP

VCC NDS traffic

VPi/VCi

VPi/VCiVPi/VCi

VPi/VCi/PathId/QoSIdVPi/VCi/PathId/QoSId

RNC

VCC HSDPA traffic VPi/VCi/PathId/QoSId

Page 360: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 52

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 52

Self-Assessment on the Objectives

� Please be reminded to fill in the formSelf-Assessment on the Objectivesfor this module

� The form can be found in the first partof this course documentation

Page 361: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 8 � Page 53

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Capacity Monitoring & Troubleshooting Section 8 �Page 53

End of Module

Page 362: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf
Page 363: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 1

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

Do not delete this graphic elements in here:

All Rights Reserved © Alcatel-Lucent 2007

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

9 3FL12921AAAAWBZZA Edition 1

Section 9Traffic/Call Profile

Monitoring

Page 364: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 2

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 2

Blank Page

This page is left blank intentionally

Second editionEL ABED, Achrafe2007-10-2002

First editionEL ABED, Achrafe2007-08-2401

RemarksAuthorDateEdition

Document History

Page 365: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 3

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 3

Objectives

� After this module, you will be able to

� Describe the traffic and call profile metric family

� Illustrate the call flows associated with the metric family

� Identify counters and locate them in the call flow procedure

� Define metrics and recognize its key counters

� Analyze each metric

Page 366: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 4

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 4

Objectives [cont.]

This page is left blank intentionally

Page 367: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 5

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 5

Table of Contents

Switch to notes view!Page

1 Traffic Monitoring 7KPIs families Reminder 8Network Traffic 9Average Number of Calls per Day 10Average Number of Calls per Day 11Average Number of Calls per Day 12Uplink/ Downlink PS Traffic 13Uplink/ Downlink PS Traffic per RNC 14Traffic Monitoring Panel 15Example: Operator Traffic- Averate # of DL RB Established 16

2 Call Profile Monitoring 17Call profile Overview (1/2) 18Call profile overview (2/2) 19UTRAN Call profile 20Call profile Monitoring panel- Traffic 21Call profile panel-Other domains 22Example: Normal day vs Christmas & New Year Eve 23Self-Assessment on the Objectives 24End of Module 25

Page 368: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 6

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 6

Table of Contents [cont.]

Switch to notes view!

This page is left blank intentionally

Page 369: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 7

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 7

1 Traffic Monitoring

Page 370: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 8

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 8

1 Traffic Monitoring

KPIs families Reminder

Network Accessibility

NetworkRetainability

NetworkQuality

NetworkTraffic

NetworkCongestion

Counter based KPIs

Capacity/

Load

Call ProfileHSxPA

RRM

NetworkMobility

Page 371: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 9

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 9

1 Traffic Monitoring

Network Traffic

� The objective of the Traffic metrics is to evaluate the traffic volume seen on the network in downlink and in uplink.

� Therefore the metric results are helpful to define the overall call model in the network (e.g. what is the main service used: PS, voice, video…).

� These inputs are also very useful complementary information to better understand the other performance results: accessibility, retainability, mobility & congestion.

Page 372: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 10

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 10

1 Traffic Monitoring

Average Number of Calls per Day

� RNC level:

� The average number of calls per day is based on the counter: VS.NumberOfRabEstablished.Avg (#675).

� It is defined as: “the average number of RABs established RAB of the “granted RAB type” in the RNS.

� It is screened per DL Access Stratum configuration

� Cell level:

� The average number of calls per day is based on the counter: VS.DlAsConfIdAvgNbrEstablished (#692) for DLVS.UlAsConfIdAvgNbrEstablished (#693) for UL

� It is defined as: “the average number of DlAsConfIds established in the Reference FDDCell,

� It is screened per UL Access Stratum configuration

Page 373: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 11

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 11

1 Traffic Monitoring

Average Number of Calls per Day

Average nb of Voice calls Per day

Average nb of Voice calls Per day

= #675.[Avg].[1]

Average nb ofVideo calls per dayAverage nb ofVideo calls per day

= #675.[Avg].[2]

Average nb of Data calls per day

Average nb of Data calls per day = #675.[Avg].[0,5-16]

RNC metricsRAB012[voice]

RAB012[video]

RAB012[data]

VS.NumberOfRabEstablished #627: This counter provides the average number of RABsestablished of the "granted RAB type" in the RNS during a reporting period. Hence, the counter does not peg when an Always On Downsize occurs.

Minimum and maximum number of RABs over the period are also provided. RAB granted should be understood as RAB effectively established (iRM can modify the characteristics of a RAB, either at call admission or during the call for PS : iRM Scheduling downgrade, upgrade, Always ON).

Screened per granted RAB type (DlRbSetId, UlRbSetId, Traffic Class) see table in appendix.

Page 374: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 12

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 12

1 Traffic Monitoring

Average Number of Calls per Day

Average nb of DLVoice calls Per day

Average nb of DLVoice calls Per day

= #692.[1]

Average nb of DLVideo calls per dayAverage nb of DLVideo calls per day

= #692.[2]

Average nb of DLData calls per day

Average nb of DLData calls per day

= #692.[4-15]

Reference FDDCell metricsRAB013_DL[voice]

RAB013_DL[video]

RAB013_DL[data]

VS.DlAsConfIdAvgNbrEstablished #660: This counter provides the average number number ofDlAsConfIds established per Reference FDDCell.

Screened per granted DlAsConfId see table in appendix.

Another counter can be used to assess the Average number of calls per Cell:

VS.RadioLinkEstablishedPerCell #11: This counter provides the average number number of NBAP Radio Links established per FDDCell. As long as, from an FDDCell point of view, a RL is equivalent to a call, this metric gives the average number of call established on this cell.

Screened per granted DlAsConfId see table in appendix.

Page 375: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 13

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 13

1 Traffic Monitoring

Uplink/ Downlink PS Traffic

� RNC level:

� Total count of RLC payload on dedicated channels containing Packet Switched data (in Kbytes): VS.DedicatedDownlinkKbytesRlc (#1473) for DL VS.DedicatedUplinkKbytesRlc(#1472) for UL

� It is screened per UL & DL MAX RATE

� Cell level:

� Total count of RLC payload on dedicated channels containing Packet Switched data (in Kbytes): VS.DedicatedDownlinkKbytesRlcActiveCells (#1485) for DLVS.DedicatedUplinkKbytesRlcActiveCells (#1484) for UL

� It is screened per UL & DL MAX RATE

Reference Cell level:

� Total count of RLC payload on dedicated channels containing Packet Switched data (in

Kbytes):

VS.DedicatedDownlinkKbytesReferenceCells(#1487) for DL

VS.DedicatedUplinkKbytesRlcReferenceCells (#1486) for UL

� It is screened per COMB UL & DL MAX RATE

Page 376: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 14

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 14

1 Traffic Monitoring

Uplink/ Downlink PS Traffic per RNC

DL PS Traffic per RNC = #1473.[6-13]DL PS Traffic per RNC = #1473.[6-13]

UL PS Traffic per RNC = #1472.[6-12]UL PS Traffic per RNC = #1472.[6-12]

Traffic015[data]

Traffic016[data]

RNC metrics

FDDCell metrics

DL PS Traffic per RNC = #1485.[6-13]DL PS Traffic per RNC = #1485.[6-13]

UL PS Traffic per RNC = #1484.[6-12]UL PS Traffic per RNC = #1484.[6-12]

Traffic017[data]

Traffic018[data]

Page 377: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 15

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 15

1 Traffic Monitoring

Traffic Monitoring Panel

RNC panel subset for Traffic monitoring

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_RAB012_R%CsVideo Average Number of RAB Established%CsVideo%50_RAB012_R

metric RNC 50_RAB012_R%CsVoice Average Number of RAB Established%CsVoice%50_RAB012_R

metric RNC 50_RAB012_R%HSDPA Average Number of RAB Established%HSDPA%50_RAB012_R

metric RNC 50_RAB012_R%Ps Average Number of RAB Established%Ps%50_RAB012_R

metric RNC 50_Traffic015_R%CsVideo Traffic DL SDU payload in Kbytes%CsVideo%50_Traffic015_R

metric RNC 50_Traffic015_R%CsVoice Traffic DL SDU payload in Kbytes%CsVoice%50_Traffic015_R

metric RNC 50_Traffic015_R%HSDPA Traffic DL SDU payload in Kbytes%HSDPA%50_Traffic015_R

metric RNC 50_Traffic015_R%Ps Traffic DL SDU payload in Kbytes%Ps%50_Traffic015_R

metric RNC 50_Traffic016_R%CsVideo Traffic UL SDU payload in Kbytes%CsVideo%50_Traffic016_R

metric RNC 50_Traffic016_R%CsVoice Traffic UL SDU payload in Kbytes%CsVoice%50_Traffic016_R

metric RNC 50_Traffic016_R%HSUPA Traffic UL SDU payload in Kbytes%HSUPA%50_Traffic016_R

metric RNC 50_Traffic016_R%Ps Traffic UL SDU payload in Kbytes%Ps%50_Traffic016_R

Page 378: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 16

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 16

1 Traffic Monitoring

Example: Operator Traffic- Averate # of DL RB Established

Operator ExamplePS orientedMBK traffic

0

20

40

60

80

100

120

140

160

01/09

/2006

02/09

/2006

03/09

/2006

04/09/200

6

05/09

/2006

06/09

/2006

07/09

/2006

08/09

/2006

09/09/200

6

10/09

/2006

11/09

/2006

12/09

/2006

13/09

/2006

14/09/200

6

15/09

/2006

16/09

/2006

17/09

/2006

18/09

/2006

19/09/200

6

20/09

/2006

21/09

/2006

22/09

/2006

23/09

/2006

24/09/200

6

25/09

/2006

26/09

/2006

27/09

/2006

28/09

/2006

29/09/200

6

30/09

/2006

Average number of PS DL RB established per RNC Average number of CS Video DL RB established per RNCAverage number of CS Voice DL RB established per RNC Average number of HSDPA DL RB established per RNC

Operator example

MBK traffic

0.00

200.00

400.00

600.00

800.00

1000.00

1200.00

1400.00

01/09

/2006

02/09/200

6

03/09/20

06

04/09

/2006

05/09/200

6

06/09/20

06

07/09/200

6

08/09/20

06

09/09

/2006

10/09/200

6

11/09/20

06

12/09

/2006

13/09/20

06

14/09

/2006

15/09/200

6

16/09/20

06

17/09

/2006

18/09/200

6

19/09

/2006

20/09/200

6

21/09/20

06

22/09

/2006

23/09/200

6

24/09/20

06

25/09/200

6

26/09/20

06

27/09

/2006

28/09/200

6

29/09/20

06

30/09

/2006

Average number of PS DL RB established Average number of CS Video DL RB established

Average number of CS Voice DL RB established Average number of HSDPA DL RB established

4.2 operator exampleOperator example

Page 379: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 17

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 17

2 Call Profile Monitoring

Page 380: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 18

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 18

2 Call Profile Monitoring

Call profile Overview (1/2)

� A call profile characterizes the behavior of a typical subscriber within a

network.

� The UTRAN call profile defines the different aspects of the user behaviour

which contribute to the load of the observed product (RNC)

� Traffic: characterizes radio resource usage generated by the subscriber

(distribution of the calls on UMTS bearers, duration)

�Mobility: characterizes the impact of the mobility procedures which are resource

consuming, but not revenue generating. This means mobility in connected mode

(in UMTS : Soft HO and Hard HO) and idle mode (Registration, Location/Routing

Area Update)

� RRM: impact of the PS call management algorithms designed to guarantee Quality

of Service (Always ON, IRM Scheduling, CELL FACH)

Page 381: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 19

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 19

2 Call Profile Monitoring

Call profile overview (2/2)

� Call Profile monitoring relies on a statistical approach at network level

over a reference period of time (the Busy Hour) : it consists in

measuring the amount of procedures performed per user in order to

quantify the CPU cost induced by each subscriber on the network

equipment.

� Dedicated metrics are defined for Call model monitoring, in order to

perform the mapping between the counters captured by the node (RNC)

and the synthetic indicator (amount of procedures per subscriber)

required to model the relevant procedures in the capacity tools.

Page 382: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 20

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 20

2 Call Profile Monitoring

UTRAN Call profile

� The metrics to monitor shall be able to quantify the CPU Load of the various elements of the RNC.

The RNC is made of two functional entities:

� User Plane (Traffic): monitoring is straightforward based on traffic counters.

� Control Plane (signalling): the monitoring is more complex as the CPU load is dependent on many

events. The main contributors to C-Plane load are:

� Busy Hour call Attempts: includes the different steps to establish a call and release it.

� Macro-diversity: mobility managed by UTRAN (parameter: Active Set Update/sec and distribution of SHO into

inter-RNC, inter NodeB, intra NodeB, etc)

� NAS signaling: procedures performed at the Core Network level are transparent to the UTRAN and called Non

Access Stratum (NAS) procedures, ie. Mobility and Session Management procedures.

� PS call management features including (synchronous) radio link reconfiguration of the call (Always ON, IRM

Scheduling, Always ON)

� Other features

RAB Assignment RAB Release

Active Set UpdateRRC MeasReport

RNC-CPlane CPU

Active Set Update Period

Attach DetachRAB Assignment RAB Release

Active Set UpdateRRC MeasReport

RNC-CPlane CPU

Active Set Update Period

Attach Detach

Page 383: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 21

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 21

2 Call Profile Monitoring

Call profile Monitoring panel- Traffic

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_AO012_R AO Downsizing Step 1 Success%50_AO012_R

metric RNC 50_RAB021_R%CsVideo Mean Call Duration%CsVideo%50_RAB021_R

metric RNC 50_RAB021_R%CsVoice Mean Call Duration%CsVoice%50_RAB021_R

metric RNC 50_RAB021_R%HSDPA Mean Call Duration%HSDPA%50_RAB021_R

metric RNC 50_RAB021_R%HSUPA Mean Call Duration%HSUPA%50_RAB021_R

metric RNC 50_RAB021_R%Ps128 Mean Call Duration%Ps128%50_RAB021_R

metric RNC 50_RAB021_R%Ps256 Mean Call Duration%Ps256%50_RAB021_R

metric RNC 50_RAB021_R%Ps32 Mean Call Duration%Ps32%50_RAB021_R

metric RNC 50_RAB021_R%Ps384 Mean Call Duration%Ps384%50_RAB021_R

metric RNC 50_RAB021_R%Ps64 Mean Call Duration%Ps64%50_RAB021_R

metric RNC 50_RAB021_R%Ps8 Mean Call Duration%Ps8%50_RAB021_R

metric RNC 50_RAB022_R%CsVideo RAB Assignment Success per Granted RAB type%CsVideo%50_RAB022_R

metric RNC 50_RAB022_R%CsVoice RAB Assignment Success per Granted RAB type%CsVoice%50_RAB022_R

metric RNC 50_RAB022_R%HSDPA RAB Assignment Success per Granted RAB type%HSDPA%50_RAB022_R

metric RNC 50_RAB022_R%HSUPA RAB Assignment Success per Granted RAB type%HSUPA%50_RAB022_R

metric RNC 50_RB011_R%CsSpeech Radio Bearer Setup Success%CsSpeech%50_RB011_R

metric RNC 50_RB011_R%CsVideo Radio Bearer Setup Success%CsVideo%50_RB011_R

metric RNC 50_RB011_R%DL128 Radio Bearer Setup Success%DL128%50_RB011_R

metric RNC 50_RB011_R%DL256 Radio Bearer Setup Success%DL256%50_RB011_R

metric RNC 50_RB011_R%DL32 Radio Bearer Setup Success%DL32%50_RB011_R

metric RNC 50_RB011_R%DL384 Radio Bearer Setup Success%DL384%50_RB011_R

metric RNC 50_RB011_R%DL64 Radio Bearer Setup Success%DL64%50_RB011_R

metric RNC 50_RB011_R%DL8 Radio Bearer Setup Success%DL8%50_RB011_R

metric RNC 50_Traffic011_R%CsVideo Traffic011_RNC_CS Voice%Activity Factor

metric RNC 50_Traffic011_R%CsVoice Traffic011_RNC_CS Video%Activity Factor

metric RNC 50_Traffic011_R%CsVoice Average DL Activity Factor%CsVoice%50_Traffic011_R

metric RNC 50_Traffic011_R%CsVideo Average DL Activity Factor%CsVideo%50_Traffic011_R

metric RNC 50_Traffic011_R%Ps64 Average DL Activity Factor%Ps64%50_Traffic011_R

metric RNC 50_Traffic011_R%Ps128 Average DL Activity Factor%Ps128%50_Traffic011_R

metric RNC 50_Traffic011_R%Ps256 Average DL Activity Factor%Ps256%50_Traffic011_R

metric RNC 50_Traffic011_R%Ps384 Average DL Activity Factor%Ps384%50_Traffic011_R

metric RNC 50_Traffic012_R%Ps32 Average UL Activity Factor%Ps32%50_Traffic012_R

metric RNC 50_Traffic012_R%Ps64 Average UL Activity Factor%Ps64%50_Traffic012_R

metric RNC 50_Traffic012_R%Ps128 Average UL Activity Factor%Ps128%50_Traffic012_R

metric RNC 50_Traffic012_R%Ps384 Average UL Activity Factor%Ps384%50_Traffic012_R

metric RNC 50_Traffic012_R%CsVoice Average UL Activity Factor%CsVoice%50_Traffic012_R

metric RNC 50_Traffic012_R%CsVideo Average UL Activity Factor%CsVideo%50_Traffic012_R

metric RNC 50_Traffic015_R%CsVideo Traffic DL SDU payload in Kbytes%CsVideo%50_Traffic015_R

metric RNC 50_Traffic015_R%CsVoice Traffic DL SDU payload in Kbytes%CsVoice%50_Traffic015_R

metric RNC 50_Traffic015_R%HSDPA Traffic DL SDU payload in Kbytes%HSDPA%50_Traffic015_R

metric RNC 50_Traffic016_R%CsVideo Traffic UL SDU payload in Kbytes%CsVideo%50_Traffic016_R

metric RNC 50_Traffic016_R%CsVoice Traffic UL SDU payload in Kbytes%CsVoice%50_Traffic016_R

metric RNC 50_Traffic016_R%HSUPA Traffic UL SDU payload in Kbytes%HSUPA%50_Traffic016_R

metric RNC 50_Traffic022_CR%HSDPA RAB Activity DL%HSDPA%50_Traffic022_CR

metric RNC 50_Traffic023_CR%HSUPA RAB Activity UL%HSUPA%50_Traffic023_CR

Page 384: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 22

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 22

2 Call Profile Monitoring

Call profile panel-Other domains

Family TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

ALWAYS ON metric RNC 50_AO008_R Number of AO Downsize per call%50_AO008_R

ALWAYS ON metric RNC 50_AO009_R Number of AO Upsize per call%50_AO009_R

ALWAYS ON metric RNC 50_AO010_R Number of AO Release per call%50_AO010_R

ALWAYS ON metric RNC 50_AO011_CR Ratio of users Downgraded%50_AO011_CR

BLER metric RNC 50_BLER006_CR%Ps Downlink BLER%Ps%50_BLER006_CR

CELL FACH counter RNC 412 VS.RrcTransitionCellFachToCellDch.AlwaysOnUpgrade

CELL FACH counter RNC 413 VS.RrcTransitionCellDchToCellFach

CELL FACH metric RNC 50_CellFACH001_CR Number of Cell Update Rejects%50_CellFACH001_CR

CELL FACH metric RNC 50_CellFACH002_CR Number of Cell Update%50_CellFACH002_CR

EVENT TRIGGER metric RNC 50_Meas006_R EventMode RRC Measurement Report per second%50_Meas006_R

HHO counter RNC 535 Number of 2G-3G CS HHOVS.IuRelocationRequests.Cs2Gto3GRelocation

HHO counter RNC 535 Number of 3G-3G CS HHOVS.IuRelocationRequests.Cs3Gto3GRelocation

HHO counter RNC 535 Number of 3G-3G PS HHOVS.IuRelocationRequests.Ps3Gto3GRelocation

HHO counter RNC 535 VS.IuRelocationRequests.Cs3Gto3GRelocationUeNotInv

HHO counter RNC 535 VS.IuRelocationRequests.Ps3Gto3GRelocationUeNotInv

HHO counter RNC 556 VS.IuRelocationRequired.3Gto3GCsUeNotInv

HHO counter RNC 556 VS.IuRelocationRequired.3Gto3GPsUeNotInv

HHO metric RNC 50_HO3G2G014_R%CsVoice HO3G2G CS per Call%CsVoice%50_HO3G2G014_R

HHO metric RNC 50_HO3G2G015_R%Ps HO3G2G PS per Call%Ps%50_HO3G2G015_R

HHO metric RNC 50_Meas004_R Compressed mode activation per hour%50_Meas004_R

iRM metric RNC 50_IRM008_R Number of iRM Scheduling Downsize per call%50_IRM008_R

iRM metric RNC 50_IRM009_R Number of iRM Scheduling Upgrade per call%50_IRM009_R

Mobility metric RNC 50_HO3G3G017_R Nb of incoming SRNS relocations%50_HO3G3G017_R

Mobility metric RNC 50_HO3G3G018_R Nb of outgoing SRNS relocations%50_HO3G3G018_R

Mobility metric RNC 50_HSDPA039_CR HSDPA To HSDPA Primary Cell Change Per Min%50_HSDPA039_CR

NAS counter RNC 403 Number of Inter-RAT cell reselectionvs.RRC.SuccConnEstab.10

NAS counter RNC 403 Number of Registrationsvs.RRC.SuccConnEstab.12

NAS counter RNC 403 Number of Detachvs.RRC.SuccConnEstab.13

NAS metric RNC 50_NAS001_CR Number of SMS%50_NAS001_CR

PAGING metric RNC 50_Paging004_R%Cs Number of Paging Request%Cs%50_Paging004_R

PAGING metric RNC 50_Paging004_R%Ps Number of Paging Request%Ps%50_Paging004_R

PAGING metric RNC 50_Paging005_R%Cs Number of Paging Record on PCCH%Cs%50_Paging005_CR

PAGING metric RNC 50_Paging005_R%Ps Number of Paging Record on PCCH%Ps%50_Paging005_CR

PERIODIC MEAS metric RNC 50_Meas001_CR RRC Measurement Report per second%50_Meas001_CR

RRC metric RNC 50_RRC004_CR RRC Connection Failure%50_RRC004_CR

RRC metric RNC 50_RRC018_CR RRC Connection Failure Ratio%50_RRC018_CR

SHO metric RNC 50_RL016_CR MeanSector per user%50_RL016_CR

SHO metric RNC 50_RL020_R ActiveSetUpdate per second per RAB%50_RL020_R

SHO metric RNC 50_RL020_R_Indicator Missing metric in the 5.0 PMM/Library

SHO metric RNC 50_RL021_CR Percentage of softer HO%50_RL021_CR

SHO metric RNC 50_RL039_R Percentage of interRNC SHO%50_RL039_R

Page 385: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 23

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 23

2 Call Profile Monitoring

Example: Normal day vs Christmas & New Year Eve

Analysis of one operator call model during Holidays: Xmas(24/12), New Years Eve(01/01/06) against normal day

>Specifity of call model during special Events• Higher CS BHCA and shorter durations (NYE: BHCA Voice x2, CSD X4)• Lower PS BHCA (less business users)• High volume of SMS sent (send greetings to relatives): X10• Peaks of registrations (UE switched at NY eve)• No change on SHO metrics: ASU rate, SHO factor

> Different Busy Hour: 8pm 24/12, 0am 01/01> Different stress on UTRAN Equipment

CSV CSDPS 384

PS 128

PS 64

CSV CSDPS 384

PS 128

PS 64

CSV CSDPS 384

PS 128

PS64

BHCA 0,70 0,01 0,19 0,02 0,01 0,93 0,02 0,16 0,04 0,01 1,60 0,04 0,08 0,08 0,01

Mean Call Duration 57 52 32 40 12 55 50 35 22 20 36 46 26 23 16

Registrations (combined)DetachInter-RAT cell reselectionSMSBUSY HOURCapacity

Family Metric name NORMAL DAY XMAS NEW YEARS EVE

Traffic

NAS

1,65 1,63 3,2

0,02 0,03 0,06

1,48 1,00 1,23

0,22 1,68 2,2018-19H 20-21H 0-1 AM

-14% -15%

Page 386: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 24

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 24

Self-Assessment on the Objectives

� Please be reminded to fill in the formSelf-Assessment on the Objectivesfor this module

� The form can be found in the first partof this course documentation

Page 387: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 9 � Page 25

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Traffic/Call Profile Monitoring Section 9 � Page 25

End of Module

Page 388: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf
Page 389: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 10 � Page 1

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

Do not delete this graphic elements in here:

All Rights Reserved © Alcatel-Lucent 2007

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

10 3FL12921AAAAWBZZA Edition 1

Section 10Stability Troubleshooting

Page 390: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 10 � Page 2

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Stability Troubleshooting Section 10 � Page 2

Blank Page

This page is left blank intentionally

Second editionEL ABED, Achrafe2007-10-2002

First editionEL ABED, Achrafe2007-08-2401

RemarksAuthorDateEdition

Document History

Page 391: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 10 � Page 3

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Stability Troubleshooting Section 10 � Page 3

Objectives

� At the end of this module you will be able to analyse and troubleshoot the main Network Elements stability issues

Page 392: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 10 � Page 4

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Stability Troubleshooting Section 10 � Page 4

Objectives [cont.]

This page is left blank intentionally

Page 393: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 10 � Page 5

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Stability Troubleshooting Section 10 � Page 5

Table of Contents

Switch to notes view!Page

1 NodeB Analysis 7Node B analysis (1/3) 8Node B analysis (2/3) 9Node B analysis (3/3): PCM stability chart 10

2 RNC Analysis 11RNC stability 12

3 HW troubleshooting through ATM counters 13Hardware throubleshooting through ATM counters 14Self-Assessment on the Objectives 15End of Module 16

Page 394: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 10 � Page 6

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Stability Troubleshooting Section 10 � Page 6

Table of Contents [cont.]

Switch to notes view!

This page is left blank intentionally

Page 395: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 10 � Page 7

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Stability Troubleshooting Section 10 � Page 7

1 NodeB Analysis

Page 396: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 10 � Page 8

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Stability Troubleshooting Section 10 � Page 8

1 NodeB Analysis

Node B analysis (1/3)

� Problem description� Stability problems in the Node Bs that leads to quality degrationor drop calls.

�Detection� Monitoring PCM counters during a period of time shows us Node B stability problems.

� (PcmLink,PcmLos,Pcmais,PcmLfa,,PcmFe,PcmCrc,PcmRai,PcmFas,PcmEbits,PcmSlip,PcmBpv,PcmEs,PcmSes,PcmBbe,PcmUas)

Page 397: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 10 � Page 9

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Stability Troubleshooting Section 10 � Page 9

1 NodeB Analysis

Node B analysis (2/3)

� Description� For this is also equivalent to check the Historical Fault browser (HBS) where the OMC alarms are

pegged to the PCM counters.� These counters are based on algorithm described in ITU-T G826

� Depending of the quantity of noise in the E1 several effects can be expected based on Alcatel-lucent Field experience:� Below 10BBE/sec no effect

� More than 10BBE/secs and no SES: ftp Throughput degraded but no RLC reset (SRB & TRB), VT degraded

� If there is second of SES , when 10 consecutives seconds of SES are reached, SES is not incremented anymore and UnavailableSeconds counters begins to increase (Unavailable seconds means seconds bts goes down)=> alarm in the bts and call drop of all calls on the bts)Background

� Block Errors indicates a high number of RLC repetition and so can be correlated with throughput degradation

� Severely Errored Seconds should provide good indications of calls drop due to PCM HW instability

Counter id PCM Stability Analysis

#10011 Errored Seconds

#10012 Severely Errored Seconds

#10014 Unavailable Seconds

#10013 Background Block Errors

PCM Link

Page 398: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 10 � Page 10

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Stability Troubleshooting Section 10 � Page 10

1 NodeB Analysis

Node B analysis (3/3): PCM stability chart

PCM Stability Analysis –Network level

PS QoS Analisys –Bts level

Yes

For the TOP N BTS

Correlation with alarms (HFB) at the same period

Is there Ses?

No

No

PCM BbeTOP N BTS

PCM SesTOP N BTS

More than 10 BBe in the shortestGranularity monitoring period

PCM Ses (more than 10 consecutive seconds)during several days? & Unvailable seconds?

Yes

All (or almost) SesWithin a short period

Retainability Analisys –Bts level

Yes

YesPCM minilink

shall be checked

Page 399: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 10 � Page 11

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Stability Troubleshooting Section 10 � Page 11

2 RNC Analysis

Page 400: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 10 � Page 12

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Stability Troubleshooting Section 10 � Page 12

2 RNC Analysis

RNC stability

� Problem description� RNC stability (TMU, AP restarts):

�Check VS.ApCpuUtilizationAvg per AP counter

�Detection� PS-FP restarts:

�Current Retro-fit of some PS-FP could provoke the reset of PS-FP cards

�PMC.RAB of PS-FP card are processing the RAB of AAL2 Path. So it will affect to Retainability analysis

� In case of reset of PS FP card, all the RAB’s are dropped�These events can not be easily monitored by counters but only with alarms

� In case of low VS.ApCpuUtilizationAvg values (or 0) correlate with alarms and Network scheduled events for troubleshooting

Page 401: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 10 � Page 13

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Stability Troubleshooting Section 10 � Page 13

3 HW troubleshooting through ATM counters

Page 402: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 10 � Page 14

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Stability Troubleshooting Section 10 � Page 14

3 HW troubleshooting through ATM counters

Hardware throubleshooting through ATM counters

� Problem description� ATM Frames with CRC errors on some BTS.

� Detection� ATM counters per VCC but aggregated by NodeB

� VS.AAL5NbCrcFrameErr different from zero and >100

� Investigation� Although there is no alarm related to bad ATM frames, the counters can be enough to detect hardware problems.

� If there are some repetitive ATM Frames with CRC errors on some BTSs, there could have been a hardware problem: it can be a faulty CCM card (in this case, the ATM bad frames are related to only one BTS) or it can be a faulty STM1/E1 converting board in the ATM switch and in this case, it is a group of Node B that have ATM frames with bad CRC.

� This could be also due to a problem of the transmission link.

� Corrective action� Change CCM card.

� Change ATM switch faulty board.

� Checking and changes of the transmission link (if micro link, E1s…)

Page 403: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 10 � Page 15

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Stability Troubleshooting Section 10 � Page 15

Self-Assessment on the Objectives

� Please be reminded to fill in the formSelf-Assessment on the Objectivesfor this module

� The form can be found in the first partof this course documentation

Page 404: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 10 � Page 16

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Stability Troubleshooting Section 10 � Page 16

End of Module

Page 405: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 1

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

Do not delete this graphic elements in here:

All Rights Reserved © Alcatel-Lucent 2007

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

11 3FL12921AAAAWBZZA Edition 1

Section 11HSxPA Performance

Monitoring

Page 406: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 2

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 2

Blank Page

This page is left blank intentionally

Second editionEL ABED, Achrafe2007-10-2002

First editionEL ABED, Achrafe2007-08-2401

RemarksAuthorDateEdition

Document History

Page 407: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 3

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 3

Objectives

� After this section, you will be able to

� Describe HSxPA main KPIs families

� Understand the main HSxPA Accessibility, Retainability, Quality, Traffic and mobility metrics.

Page 408: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 4

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 4

Objectives [cont.]

This page is left blank intentionally

Page 409: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 5

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 5

Table of Contents

Switch to notes view!Page

1 HSDPA Performance Monitoring 7HSDPA Distributed Architecture 8Cell Topologies in networks 9HSDPA Main KPIs 10HSDPA Monitoring main challenges 11Accessibility Monitoring 12Accessibility Flow Diagrams 13RAB Matching and CAC 14HSDPA to DCH Fallback 15HSDPA Accessibility KPIs 16HSDPA Accessibility KPIs 17HSDPA Accessibility KPIs 18HSDPA Accessibility KPIs 19RAB Assignment Success: Counters 20HSDPA Accessibility KPIs 21Retainability Monitoring 22Network Retainability Performance 23Total number of RABs 24Abnormal Release Caused by RL Failure 25Call Abnormal Release 26Call Drops due to UTRAN generated reasons 27Call Drops due to UTRAN generated reasons 28Call Drops due to UTRAN generated reasons 29Call Drops due to UTRAN generated reasons 30Call Drops due to UTRAN generated reasons 31Mobility Monitoring 32HSDPA Mobility scenarios 33HSDPA Mobility scenarios 34HSDPA Mobility scenarios 35HSDPA Mobility scenarios 36HSDPA Mobility scenarios 37HSDPA Mobility scenarios 38Capacity Monitoring 39Capacity Monitoring 40Capacity Monitoring 41Capacity Monitoring 42Capacity Monitoring 43Capacity Monitoring 44Capacity Monitoring 45Capacity Monitoring 46Capacity Monitoring 47Capacity Monitoring 48Capacity Monitoring 49Capacity Monitoring 50Traffic Monitoring 51Traffic Monitoring 52Traffic Monitoring 53Traffic Monitoring 54Traffic Monitoring 55Traffic Monitoring 56Traffic Monitoring 57Traffic Monitoring 58Traffic Monitoring 59Quality Monitoring 60Quality Monitoring 61

Page 410: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 6

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 6

Table of Contents [cont.]

Switch to notes view!Page

Quality Monitoring 62Quality Monitoring 63Quality Monitoring 64

2 HSUPA Performance Monitoring 65Transport & Physical Channels 66Accessibility Monitoring 67HSUPA Accessibility Monitoring 68Number of CAC reject on e-DCH cell 69Successful rate DCH to HSUPA transitions 70Proportion of HSUPA Fallback 71Retainability Monitoring 72HSUPA Retainability Monitoring 73HSUPA Mobility Call Drop rate 74HSUPA Radio Call Drop rate 75Mobility Monitoring 76HSUPA Mobility Monitoring 77HSUPA Mobility Success Rate 78Primary Cell Change per minute of call HSUPA 79Capacity Monitoring 80HSUPA Capacity Monitoring 81HSUPA Common Channel Power 82UL Cell Load 83Average Thermal Noise 84HSUPA UL Load Management 85Quality Monitoring 86HSUPA Quality Monitoring 87HSUPA HARQ BLER & Average Throughput 88UL Radio Quality 89UL Traffic Quality 90Traffic Monitoring 91HSUPA Traffic Monitoring 92HSUPA Activity & Penetration factors 93HSUPA Traffic volume metrics 94Self-Assessment on the Objectives 95End of Module 96

Page 411: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 7

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 7

1 HSDPA Performance Monitoring

Page 412: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 8

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 8

1 HSDPA Performance Monitoring

HSDPA Distributed Architecture

Uu Iub

MAC-d

RLC

HS-DSCH FP

MAC-hsHS-DSCH

FP

RLC

L2 L2

Flow control

PHY PHY L1 L1

New Transport channelHS-DSCH

RNCNodeBUE

HS-SCCHDownlink Transfer Information(UEid, OVSF,...)

HS-PDSCHData Transfer (PS I/B)

HS-DPCCH Feedback Information (CQI, ACK/NACK)

DPCHUpper Layer Signaling

RNC

New Frame ProtocolsHS-DSCH

Introduction of MAC-hs

Iub

MAC-d

MAC-hs

HSDPA is an increment on UTRAN procedures, and is fully compatible with R4 layer 1 and

layer 2. It is based on the introduction of a new MAC entity (MAC-hs) in the Node B, that

is in charge of scheduling / repeating the data on a new physical channel (HS-DSCH)

shared between all users.

This has a minor impact on network architecture. There is no impact on RLC protocol and

HSDPA is compatible with all transport options (AAL2 and IP).

On the Node B side, MAC-hs layer provides the following functionalities:

� Fast repetition layer handled by HARQ processes

� Adaptive Modulation and Coding

� New transport channel High Speed Downlink Shared Channel (HS-DSCH)

� Flow control procedure to manage Node B buffering

Some new L1 new functionalities are introduced compared to R4:

� 3 new physical channels: HS-PDSCH to send DL data, HS-SCCH to send DL control

information relative to HS-PDSCH, and HS-DPCCH to receive UL control information

� New channel coding chain for HS-DSCH transport channel and HS-SCCH physical channel

Page 413: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 9

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 9

1 HSDPA Performance Monitoring

Cell Topologies in networks

� 3 cell topologies are currently deployed in the networks:�One Frequency with only R99 traffic:

�Represented in this document by

�Do not carry any HSDPA traffic

�One Frequency with HSDPA/ R99:�Represented in this document by

� R99 and HSDPA traffic are cohabiting on the same frequency

�Only 5 OVSF DL SF16 codes statistically booked & mainly 1 PCM deployed

�Two Frequencies with HSDPA/ R99:

�Represented in this document by

�HSDPA traffic is carried on a dedicated carrier

�10 OVSF DL SF16 codes statistically booked & more than 1 PCM generally deployed

�Mostly STSR2 deployed and very few STSR1+1

R99

R99 / HSDPA

R99

HSDPA

Assumption: HSUPA is activated wherever HSDPA is activated � No Only HSDPA UA5.0 target topologies are treated

Page 414: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 10

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 10

1 HSDPA Performance Monitoring

HSDPA Main KPIs

Network Accessibility

NetworkRetainability

NetworkQualityNetwork

Traffic

HSDPA KPIs

Capacity

NetworkMobility

The following performance domains will be covered:

• Accessibility: what is the success rate for the HSxPA RB to access the

network resources?

• Retainability: what is success rate for the HSxPA RB to end normally? How

long time the HSxPA RB can remain without dropping in a cell?

• Mobility: What is the mobility success rate for HSxPA RB?

• Capacity: HSxPA could consume high network resources capacity (e.g. high

power usage). What is the part HSxPA radio resources shared?

• Traffic: What is the amount of HSxPA traffic and the HSxPA activity duration?

• Quality: Key metrics. What is the throughput provided based on radio quality

and on limitations?

For all the metrics listed, it is recommended to monitor daily during at least 2 weeks

before analyzing results and take the appropriate actions.

Page 415: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 11

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 11

1 HSDPA Performance Monitoring

HSDPA Monitoring main challenges

� HSDPA is a key technology for operators and then is a key interest for monitoring

� HSDPA is a high throughput bearer it can lead to the saturation of radio resources and degradation of RF conditions.

Then for the monitoring of HSDPA specific focus will be made on

� CapacityE.g : Power/Code usage

� PS PerformanceE.g: Throughput

BLER

Page 416: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 12

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 12

Accessibility Monitoring

Page 417: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 13

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 13

1 HSDPA Performance Monitoring

Accessibility Flow Diagrams

UERRC Connection Request

RRC Connection Complete

RRC Connection Setup

Radio Link Setup Request

Radio Link Setup Response

Measurement Control

Init Direct Transfer

RNCNode B CN

SCCP connection confirm

SCCP connection req.

Security mode command

Security mode complete

Security mode command

Security mode completeCommon id

RAB assignment req.

Radio Bearer Setup

Radio Bearer Setup Complete RAB assignment resp.

S.R.L.R. Procedure

RR

C c

onne

ctio

nS

CC

Pco

nn.

Sec

urity

mod

eR

AB

esta

blsh

t

S.R.L.R. : Synchronized Radio Link Reconfiguration

Page 418: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 14

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 14

1 HSDPA Performance Monitoring

RAB Matching and CAC

HSDPA RAB

Service = PS?

Traffic Class = I/B?

R99 RAB

YES

YES

YES

RAB Request

NO

NO

NO

RNCRNC

HSDPA UE?

Primary Cell = HSDPA Cell?

YES

NO

HSDPA CAC

Any PS RAB request with Interactive or Background traffic class is matched to the HSDPA

Radio Bearer configuration if the mobile is HSDPA capable and the primary cell of the

active set supports HSDPA. If it is not the case, the request is mapped on DCH as usual

(iRM CAC is performed).

In UA5 the admission process in the RNC for HSDPA admits any I/B RAB request on HSDPA

until the maximum number of simultaneous users allowed on HSDPA is reached. In this

version there is no other admission criteria.

� RNC CAC:

� RNC rejects when the current number of HSDPA users in the cell is equal to

maximumNumberOfUsers parameter value.

� In UA5 this number has been extended compared to UA4.2 (from 20 to 48)

� BTS CAC:

� The BTS limits the number of simultaneous HS-DSCH radio-links because of limited

processing capacity. If the limit is reached, the radio-link setup/reconfiguration is

rejected. This leads to a RAB reject by the RNC.

� BTS rejects when the current number of HSDPA users managed by the H-BBU equal to

hsdpaMaxNumberUserHbbu parameter value.

� BTS rejects when the current number of HSDPA users managed by the NodeB equal to

hsdpaMaxNumberUserPerNodeB parameter value.

In case of HSDPA CAC failure (lack of resource) HSDPA to DCH fallback is triggered in order

to reconfigure the request to DCH as if the UE was not HSDPA capable.

Page 419: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 15

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 15

1 HSDPA Performance Monitoring

HSDPA to DCH Fallback

HSDPA RB to established

CAC OK ?

DCH RB to established

HSDPA RB established

Yes

No

HSDPA to DCH Fallback

RAB assignment (to establish or to release)IU release

Primary cell changeIncoming Inter-RNC UE involved Hard Handover

Incoming Intra-RNC Alarm Hard Handover

Mobility

RabAssignment

HSPA to DCH fallback feature allows to establish or reconfigure the PS I/B RAB into DCH in case of HSDPA or HSUPA CAC failure. The following HSxPA CAC failure scenarios trigger such a fallback:

� RAB assignment (to establish or to release)

� IU release

� Primary cell change

� Inter-RNC UE involved Hard Handover

� Alarm Hard Handover

If for whatever reason the CAC fails when allocating the new radio bearer on HS-DSCH, the RNC will try to fallback the radio bearer on DCH (this may be deactivated by the operator).

In this case, the RAB matching will be played again on DCH as if the mobile was not HSDPA capable. If the output of the iRM table is “reject” then the fallback wil not be attempted and the RAB will be rejected.

If the call admission on DCH rejects the fallback then the RAB will be rejected (but the existing ones will be kept), except if there is another layer, in which case iMCTA (for CAC failure reason) is played.

If the UE has already a PS I/B RAB mapped on HS-DSCH then the RNC will try also to reconfigure this one to DCH. If the CAC fails on the new configuration only the new RAB will be rejected (iMCTA may be also played) but the existing ones will be kept.

RNC tries and remaps a call establish “fall-backed to DCH RAB” onto HSDPA or HSUPA in the following cases:

� RAB assignment (to establish or to release a second RAB)

� Primary Cell change

� Inter-RNC (UE involved or not) HHO

HSPA to DCH fallback at Always-On upsize is not supported in UA5.0. However, fallback at Always-On upsize

is triggered when a second RAB is being established (either CS or PS).

In case HSPA to DCH fallback is disabled, any HSxPA CAC failure leads to an IU-PS Release procedure.

Page 420: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 16

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 16

1 HSDPA Performance Monitoring

HSDPA Accessibility KPIs

� The only admission control done for HSDPA RB is based on the maximum number of simultaneous users allowed.

� A HSDPA RB can not be rejected by the RNC for lack of network resources (Power, OVSF Codes, Iub ATM (EBR=0)).

� In case of CAC failure, the Feature 32602 HSPA to DCH Fallback allows to reconfigure in DCH.

• #958 VS.HsdpaCACUnsuccessful: Unsuccessful access to the cell for an HSDPA call during mobility or establishment procedure.

• A set of subcounters screened on: Reason for the HSDPA CAC failure- Sub-Counter #0 : Maximum number of HSDPA users exceede- Sub-Counter #1 : Maximum number of Streaming HSDPA users exceeded- Sub-Counter #1 : Maximum number of Streaming HSDPA users exceeded- Sub-Counter #2 : Maximum Aggregated GBR exceeded

• #1601 VS.SucHspaToDchFallbackCell

• #1602 VS.SucHspaToDchFallbackNrnc

• #1603 VS.UnsucHspaToDchFallbackCell

• #1604 VS.UnsucHspaToDchFallbackNrnc

• #0673 VS.RabEstablishmentSuccessPerGrantedRabType

• #687 VS.RadioBearerSetupSuccess: the number of successful radio bearer establishment procedures, for each cell controlled by the RNC which is the reference cell. During such a procedure, the measurement attached to a given cell is incremented if the cell is the primary cell of the active set of the UE.

• A set of subcounters screened on: Target Type of call setup mapping , see also Annex: T14- Sub-Counter #0 : Other combinations - Sub-Counter #1 : CS Speech - Sub-Counter #2 : CS Data- Sub-Counter #3 : CS Streaming - Sub-Counter #4 : PS Streaming 1- Sub-Counter #5 : PS Streaming 64 - Sub-Counter #6 : PS Streaming 128- Sub-Counter #7 : PS Streaming 256 - Sub-Counter #8 : PS I/B 8 - Sub-Counter #9 : PS I/B 32- Sub-Counter #10 : PS I/B 64 - Sub-Counter #11 : PS I/B 128- Sub-Counter #12 : PS I/B 256 - Sub-Counter #13 : PS I/B 384 - Sub-Counter #14 : HSDPA

• #1165 VS.UpsizingSuccess: the number of successful upsizings, screened by Downlink Access Stratum Configuration, for A set of subcounters screened on: NT Upsizing or Downsizing Rate Mapping- Sub-Counter #0 : HSDPA - Sub-Counter #1 : DCH PS I/B 32- Sub-Counter #2 : DCH PS I/B 64 - Sub-Counter #3 : DCH PS I/B 128- Sub-Counter #4 : DCH PS I/B 256 - Sub-Counter #5 : DCH PS I/B 384

Page 421: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 17

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 17

1 HSDPA Performance Monitoring

HSDPA Accessibility KPIs

HSDPA Cac failed admission = Σ #0958[HSDPA CAC failure causes]HSDPA Cac failed admission = Σ #0958[HSDPA CAC failure causes]

HSDPA002FDDCell metric

� Recommendation:This indicator has to be monitored on the areas (group of cells/ RNC’s) where HSDPA has been activated. The CAC failure can happen either during RAB establishment or during AO upsize or during change of primary cell.

� Expected result:Based on Performance Field Assessment and Configuration audit performed in the Q4 2006, all the HSDPA cells accept up to 48 simultaneous HSDPA users and the number of HSDPA CAC Failed admission is always equal to 0.

• #958 VS.HsdpaCACUnsuccessful: Unsuccessful access to the cell for an HSDPA call during mobility or establishment procedure.

• A set of subcounters screened on: Reason for the HSDPA CAC failure- Sub-Counter #0 : Maximum number of HSDPA users exceede- Sub-Counter #1 : Maximum number of Streaming HSDPA users exceeded- Sub-Counter #1 : Maximum number of Streaming HSDPA users exceeded- Sub-Counter #2 : Maximum Aggregated GBR exceeded

• #1601 VS.SucHspaToDchFallbackCell

• #1602 VS.SucHspaToDchFallbackNrnc

• #1603 VS.UnsucHspaToDchFallbackCell

• #1604 VS.UnsucHspaToDchFallbackNrnc

• #0673 VS.RabEstablishmentSuccessPerGrantedRabType

• #687 VS.RadioBearerSetupSuccess: the number of successful radio bearer establishment procedures, for each cell controlled by the RNC which is the reference cell. During such a procedure, the measurement attached to a given cell is incremented if the cell is the primary cell of the active set of the UE.

• A set of subcounters screened on: Target Type of call setup mapping , see also Annex: T14- Sub-Counter #0 : Other combinations - Sub-Counter #1 : CS Speech - Sub-Counter #2 : CS Data- Sub-Counter #3 : CS Streaming - Sub-Counter #4 : PS Streaming 1- Sub-Counter #5 : PS Streaming 64 - Sub-Counter #6 : PS Streaming 128- Sub-Counter #7 : PS Streaming 256 - Sub-Counter #8 : PS I/B 8 - Sub-Counter #9 : PS I/B 32- Sub-Counter #10 : PS I/B 64 - Sub-Counter #11 : PS I/B 128- Sub-Counter #12 : PS I/B 256 - Sub-Counter #13 : PS I/B 384 - Sub-Counter #14 : HSDPA

• #1165 VS.UpsizingSuccess: the number of successful upsizings, screened by Downlink Access Stratum Configuration, for A set of subcounters screened on: NT Upsizing or Downsizing Rate Mapping- Sub-Counter #0 : HSDPA - Sub-Counter #1 : DCH PS I/B 32- Sub-Counter #2 : DCH PS I/B 64 - Sub-Counter #3 : DCH PS I/B 128- Sub-Counter #4 : DCH PS I/B 256 - Sub-Counter #5 : DCH PS I/B 384

Page 422: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 18

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 18

1 HSDPA Performance Monitoring

HSDPA Accessibility KPIs

HSDPA CAC FAILURE RATE =HSDPA CAC FAILURE RATE =

HSDPA036FDDCell metric

#0958 [HSDPA CAC failure causes]

#0957 + #0958. [HSDPA CAC failure causes]

HSDPA CAC

0

1000

2000

3000

4000

5000

6000

7000

8000

9000

8 Feb 07 9 Feb 07 10 Feb 07 11 Feb 07 12 Feb 07 13 Feb 07 14 Feb 07 15 Feb 07 16 Feb 07 17 Feb 07 18 Feb 07 19 Feb 07 20 Feb 07 21 Feb 07

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

Outdoor276654_0 VS.HsdpaCACSuccess Outdoor276654_1 VS.HsdpaCACSuccess

Outdoor276654_2 VS.HsdpaCACSuccess Outdoor276654_3 VS.HsdpaCACSuccess

Outdoor276654_4 VS.HsdpaCACSuccess Outdoor276654_5 VS.HsdpaCACSuccess

Outdoor276654_0 HSDPA Cac Failure rate%50_HSDPA036_CR Outdoor276654_1 HSDPA Cac Failure rate%50_HSDPA036_CR

Outdoor276654_2 HSDPA Cac Failure rate%50_HSDPA036_CR Outdoor276654_3 HSDPA Cac Failure rate%50_HSDPA036_CR

Outdoor276654_4 HSDPA Cac Failure rate%50_HSDPA036_CR Outdoor276654_5 HSDPA Cac Failure rate%50_HSDPA036_CR

• #958 VS.HsdpaCACUnsuccessful: Unsuccessful access to the cell for an HSDPA call during mobility or establishment procedure.• A set of subcounters screened on: Reason for the HSDPA CAC failure• • Sub-Counter #0 : Maximum number of HSDPA users exceeded• • Sub-Counter #1 : Maximum number of Streaming HSDPA users exceeded• • Sub-Counter #2 : Maximum Aggregated GBR exceeded#957 VS.HsdpaCACSuccess: Successful access to the cell for an HSDPA call during mobility,

establishment or reconfigurationfrom DCH to HSDPA procedure.

� Recommendation:This indicator has to be monitored on the areas (group of cells/ RNC’s) where HSDPA has been activated. The

CAC failure can happen either during RAB establishment or during AO upsize or during change of primary cell.

� Expected result:Based on Performance Field Assessment and Configuration audit performed in the Q4 2006, all the HSDPA cells

accept up to 20 simultaneous HSDPA users and the number of HSDPA CAC Failure rate is always equal to 0

Page 423: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 19

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 19

1 HSDPA Performance Monitoring

HSDPA Accessibility KPIs

PROPORTION OF HSDPA/HSUPA FALLBACK

PROPORTION OF HSDPA/HSUPA FALLBACK

HSDPA046RNC metric

Σ #1601.[0,2] + #1602

Σ #0673.[10,16] + #1601.[0,2] + #1602 + #1603[0,2] + #1604=

=

� Recommendation:This indicator has to be monitored on the areas (group of cells/ RNC’s) where HSPA to DCH Fallback (Feature 32602) has been activated. The HSDPA Fallback happens after a CAC failure either during RAB establishment or during AO upsize or during change of primary cell.

� Expected result:It is not currently common to have representative number of HSDPA CAC Failure. Therefore the proportion of HSDPA Fallback should be low. If it becomes representative in some identified areas, then densification should be forecasted.

• #958 VS.HsdpaCACUnsuccessful: Unsuccessful access to the cell for an HSDPA call during mobility or establishment procedure.

• A set of subcounters screened on: Reason for the HSDPA CAC failure- Sub-Counter #0 : Maximum number of HSDPA users exceede- Sub-Counter #1 : Maximum number of Streaming HSDPA users exceeded- Sub-Counter #1 : Maximum number of Streaming HSDPA users exceeded- Sub-Counter #2 : Maximum Aggregated GBR exceeded

• #1601 VS.SucHspaToDchFallbackCell

• #1602 VS.SucHspaToDchFallbackNrnc

• #1603 VS.UnsucHspaToDchFallbackCell

• #1604 VS.UnsucHspaToDchFallbackNrnc

• #0673 VS.RabEstablishmentSuccessPerGrantedRabType

• #687 VS.RadioBearerSetupSuccess: the number of successful radio bearer establishment procedures, for each cell controlled by the RNC which is the reference cell. During such a procedure, the measurement attached to a given cell is incremented if the cell is the primary cell of the active set of the UE.

• A set of subcounters screened on: Target Type of call setup mapping , see also Annex: T14- Sub-Counter #0 : Other combinations - Sub-Counter #1 : CS Speech - Sub-Counter #2 : CS Data- Sub-Counter #3 : CS Streaming - Sub-Counter #4 : PS Streaming 1- Sub-Counter #5 : PS Streaming 64 - Sub-Counter #6 : PS Streaming 128- Sub-Counter #7 : PS Streaming 256 - Sub-Counter #8 : PS I/B 8 - Sub-Counter #9 : PS I/B 32- Sub-Counter #10 : PS I/B 64 - Sub-Counter #11 : PS I/B 128- Sub-Counter #12 : PS I/B 256 - Sub-Counter #13 : PS I/B 384 - Sub-Counter #14 : HSDPA

• #1165 VS.UpsizingSuccess: the number of successful upsizings, screened by Downlink Access Stratum Configuration, for A set of subcounters screened on: NT Upsizing or Downsizing Rate Mapping- Sub-Counter #0 : HSDPA - Sub-Counter #1 : DCH PS I/B 32- Sub-Counter #2 : DCH PS I/B 64 - Sub-Counter #3 : DCH PS I/B 128- Sub-Counter #4 : DCH PS I/B 256 - Sub-Counter #5 : DCH PS I/B 384

Page 424: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 20

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 20

1 HSDPA Performance Monitoring

RAB Assignment Success: Counters

UE RNCNode B CN

RAB assignment req.

Radio Bearer Setup

Radio Bearer Setup Complete

RAB assignment resp.

S.R.L.R. Procedure

RA

Bes

tabl

sht

#673 RAB establishment success per Granted RAB type

RNC counter

#691 RB Setup request

FDDCell counter

Internal RRM decision to

assign resources

VS.RabEstablishmentRequestsPerRabType #621: Number of RAB Establishments Requests per RAB type. This measurement provides the number of RAB establishment attempts.

Screening: by requested RAB Type (DlRbSetId, UlRbSetId, Traffic Class) see table COMB UL

DL RBSET in appendix.

VS.RabEstablishmentSuccessPerRequestedRabType #672: Number of successful RAB establishments per Requested RAB type. This measurement provides the number of successful Radio Access Bearer establishments per RAB type as requested by the Core Network (even if the actual RAB type Granted by the UTRAN is different than the RAB type that was requested by the CN).

Screening: per requested RAB type (requested should be understood to be after RAB matching).

VS.RabEstablishmentSuccessPerGrantedRabType #623: Number of successful RAB establishments per Granted RAB type. This measurement provides the number of successful RAB establishment per RAB type as granted by the UTRAN.

Screening: per granted RAB type (granted should be understood to be after iRM Table matching).

VS.RadioBearerSetupRequest #625: Number of Radio-Bearer establishments to be performed following a valid RAB assignment request received from the CN. This measurement provides the number of RB to be setup before CAC is carried out.

Screening: per DlAsConfId

VS.RadioBearerSetupSuccess #601: Number of successful Radio-Bearer establishments. This measurement provides the number of successful RB setup.

Screening: per DlAsConfId

Page 425: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 21

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 21

1 HSDPA Performance Monitoring

HSDPA Accessibility KPIs

RAB Assignment Success per Granted RAB type%HSDPA%50_RAB022_R

RAB Assignment Success per Granted RAB type%HSDPA%50_RAB022_R

RAB022RNC metric

Σ #673. [10-16]=

Radio Bearer to be Setup%HSDPA%50_RB008_C

Radio Bearer to be Setup%HSDPA%50_RB008_C

RB008FDDCell metric

= Σ #691. [14]

• #958 VS.HsdpaCACUnsuccessful: Unsuccessful access to the cell for an HSDPA call during mobility or establishment procedure.

• A set of subcounters screened on: Reason for the HSDPA CAC failure- Sub-Counter #0 : Maximum number of HSDPA users exceede- Sub-Counter #1 : Maximum number of Streaming HSDPA users exceeded- Sub-Counter #1 : Maximum number of Streaming HSDPA users exceeded- Sub-Counter #2 : Maximum Aggregated GBR exceeded

• #1601 VS.SucHspaToDchFallbackCell

• #1602 VS.SucHspaToDchFallbackNrnc

• #1603 VS.UnsucHspaToDchFallbackCell

• #1604 VS.UnsucHspaToDchFallbackNrnc

• #0673 VS.RabEstablishmentSuccessPerGrantedRabType

• #687 VS.RadioBearerSetupSuccess: the number of successful radio bearer establishment procedures, for each cell controlled by the RNC which is the reference cell. During such a procedure, the measurement attached to a given cell is incremented if the cell is the primary cell of the active set of the UE.

• A set of subcounters screened on: Target Type of call setup mapping , see also Annex: T14- Sub-Counter #0 : Other combinations - Sub-Counter #1 : CS Speech - Sub-Counter #2 : CS Data- Sub-Counter #3 : CS Streaming - Sub-Counter #4 : PS Streaming 1- Sub-Counter #5 : PS Streaming 64 - Sub-Counter #6 : PS Streaming 128- Sub-Counter #7 : PS Streaming 256 - Sub-Counter #8 : PS I/B 8 - Sub-Counter #9 : PS I/B 32- Sub-Counter #10 : PS I/B 64 - Sub-Counter #11 : PS I/B 128- Sub-Counter #12 : PS I/B 256 - Sub-Counter #13 : PS I/B 384 - Sub-Counter #14 : HSDPA

• #1165 VS.UpsizingSuccess: the number of successful upsizings, screened by Downlink Access Stratum Configuration, for A set of subcounters screened on: NT Upsizing or Downsizing Rate Mapping- Sub-Counter #0 : HSDPA - Sub-Counter #1 : DCH PS I/B 32- Sub-Counter #2 : DCH PS I/B 64 - Sub-Counter #3 : DCH PS I/B 128- Sub-Counter #4 : DCH PS I/B 256 - Sub-Counter #5 : DCH PS I/B 384

Page 426: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 22

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 22

Retainability Monitoring

Page 427: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 23

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 23

1 HSDPA Performance Monitoring

Network Retainability Performance

� The objective of the retainability metrics is to evaluate the ability of the network to provide reliable service to the end user.

� If and only if a call is dropped, the RNC sends the RANAP Iu Release Request message with the field abnormal reasons.

� A good part of the calls dropped are originated by a Radio Link Failure Indication message

Page 428: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 24

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 24

1 HSDPA Performance Monitoring

Total number of RABs

UE

RAB assigt resp*

(…)

(…)

RNCNode B

RRC Connection Setup

MSC

RANAP/RAB assigt req

RRC Connection Complete

#0672 RAB establishtsuccess

*RANAP/RAB assigt resp.: can be several responses.

Radio access bearer

assignment procedure

#0533: Number of Abnormal RELEASE Requests on Iu CS. This measurement represents the number of Iu CS release requests due to abnormal conditions. Screening: by DLAsConf.

Condition = on RNC requests Iu CS release due to abnormal conditions:

� O&M intervention

� Repeated integrity check failure

� Radio connection lost

� Relocation timeout (corresponding to timeout of TrelocoverallExpiry and

TrelocCompleteExpiry)

� Unspecified failure

#0622: Number of RAB Establishments SUccess Per Requested RAB type. This measurement provides the number of successful RAB establishment, screened per requested RAB type (requested should be understood to be after RAB matching). Screening by RAB Type. Screening: by requested RAB Type.

Page 429: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 25

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 25

#0572 Iu abnormal release request CS#0573 Iu abnormal release request PS

1 HSDPA Performance Monitoring

Abnormal Release Caused by RL Failure

Node B RNC CN

Radio Link Failure Indication

Radio Link Deletion Resp

Iu Release Req

#0505 Iu release command CS#0506 Iu release command PS

#034 Dropped Last Radio Links

Iu Release Command

Radio Link Deletion Req

Iu Release Complete

#034: Number of dropped calls on last radio-link release. This measurement provides the number of dropped calls (on last radio-link release), for each cell controlled by the RNC. Screening: by DlAsConf.

#0505: Number of RELEASE COMMANDs on Iu CS. This measurement provides the number of RANAP IU RELEASE COMMAND messages received by the RNC on Iu CS.

#0506: Number of RELEASE COMMANDs on Iu PS. This measurement provides the number of RANAP “IU RELEASE COMMAND” messages received by the RNC on Iu PS.

#505 & #506 screening:

� #0 --> Normal end of communication

� #1 --> Successful 3G/2G or 3G/3G relocation (3GPP RANAP cause 11)

� #2 --> UTRAN generated reason (3GPP RANAP cause 15) or Iu_release_request sent by RNC before

� #3 --> Other cause (all other 3GPP RANAP causes)

� #4 --> Relocation Cancelled (3GPP RANAP cause 10)

� #5 --> O&M Intervention (3GPP RANAP cause 113)

� #6 --> Unspecified Failure (3GPP RANAP cause 115)

� #7 --> User Inactivity (3GPP RANAP cause 16)

� #8 --> No Remaining RAB (3GPP RANAP cause 31)

#0572: Number of Abnormal RELEASE Requests on Iu CS. This measurement represents the number of Iu CS release requests due to abnormal conditions. Screening by DlAsConf (DL AS configuration). Screening: by DlAsConf.

#0573: Number of Abnormal RELEASE Requests on Iu PS. This measurement represents the number of Iu PS release requests due to abnormal conditions. Screening by DlAsConf (DL AS configuration). Screening: by DlAsConf.

Page 430: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 26

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 26

1 HSDPA Performance Monitoring

Call Abnormal Release

#0576 Iu release request CS (cell)#0577 Iu release request PS (cell)#0572 Iu abnormal release request CS (cell)#0573 Iu abnormal release request PS (cell)

#0505 Iu release command CS#0506 Iu release command PS

Node B RNC CN

Radio Link Deletion Response

Iu Release Request

Iu Release Command

Radio Link Deletion Request

Iu Release Complete

#0571 Iu release complete CS

Issue detected

#576 (#577): This measurement provides the number of RANAP IU_RELEASE_REQUEST sent by RNC to Core Network CS (PS).

• Sub-Counter #0 : Release due to OAM intervention

• Sub-Counter #1 : Iu User-plane failure

• Sub-Counter #2 : Unspecified failure

• Sub-Counter #3 : Repeated Integrity protection check failure

• Sub-Counter #4 : Release due to UE

• Sub-Counter #5 : Radio connection lost with UE

• Sub-Counter #6 : Relocation too long (timer on relocation expiry).

• Sub-Counter #8 : DL RLC error on SRB

• Sub-Counter #9 : UL RLC error on SRB

• Sub-Counter #10 : DL RLC error on TRB

• Sub-Counter #11 : UL RLC error on TRB

#572 (#573): Number of Iu abnormal release request that increments whenever RNC requests Iu release due to abnormal conditions to CS (PS) CN. Instance FDDCell / DlAsConf (Reference).

Dropped call KPIs will only be calculated on calls with an AsConfId (Q01158696-01). Some counters already exist for IU release requests: counters 576 and 577 (VS.IuReleaseRequestCs. And VS.IuReleaseRequestPs.) These ones are incremented for all cases (normal or abnormal); the normal cases are: - release due to UE generated signnaling connection relaese (abnormal TBC) - user inactivity (in case of always on) - Last remaining RAB all other cases are considred as abnormal. The abnormal cases currently covered are the following ones: - OandM intervention - Repeated integrity check failure -Radio connection lost - Relocation timeout (corresponding to timeout of TrelocoverallExpiry and TrelocCompleteExpiry) - Unspecified failure

Page 431: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 27

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 27

1 HSDPA Performance Monitoring

Call Drops due to UTRAN generated reasons

� All call drops generated by UTRAN are counted in

� VS.IuAbnormRelReqCs #572 for CS

� VS.IuAbnormRelReqPs #573 for PS

� Call drops due to UTRAN are counted in

� VS.IuAbnormRelReqCs #576 for CSAll screenings except

� 3: UE generated signalling cnx release

� VS.IuAbnormRelReqPs #577 for PSAll screenings except

� 0: User inactivity (Always On step 2)

� 5: UE generated signalling cnx release

Reference FDDCell counters

VS.IuAbnormRelReqCs #572: Number of times the RNC requests an Iu release on Iu-CS interface due to abnormal conditions. It corresponds to all cases of call drops CS due to UTRAN

Screening: DlAsConfId

VS.IuAbnormRelReqPs #573: Number of times the RNC requests an Iu release on Iu-PS interface due to abnormal conditions. It corresponds to all cases of call drops PS due to UTRAN

Screening: DlAsConfId

VS.IuAbnormRelReqCs #576: Number of times the RNC sends an Iu release request message to the MSC (counts normal and abnormal releases).

Screening: DlAsConfId

0 : Release due to OAM intervention 6 : Relocation too long (timer on relocation expiry).

1 : Iu User-plane failure 7 : Other cause (For future use, not implemented)

2 : Unspecified failure 8 : DL RLC error on SRB

3 : Repeated Integrity protection check failure 9 : UL RLC error on SRB

4 : Release due to UE 10 : DL RLC error on TRB

5 : Radio connection lost with UE 11 : UL RLC error on TRB

VS.IuReleaseRequestPs #577: Number of times the RNC sends an Iu release request message to the SGSN (counts normal and abnormal releases).

Screening: DlAsConfId

0 : User inactivity (Always On step 2)

1 : Iu User-plane failure 7 : Relocation too long (timer on relocation expiry).

2 : Release due to OAM intervention 8 : Other cause (For future use, not implemented)

3 : Unspecified failure 9 : DL RLC error on SRB

4 : Repeated Integrity protection check failure 10 : UL RLC error on SRB

5 : Release due to UE 11 : DL RLC error on TRB

6 : Radio connection lost with UE 12 : UL RLC error on TRB

Page 432: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 28

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

HSDPA Call Drop indicator ( HSDPA032) :

VS.IuAbnormalReleaseRequestPs.DlAsCnfHsdpa /

(VS.IuAbnormalReleaseRequestPs.DlAsCnfHsdpa + VS.RadioBearerReleaseSuccess.TgtCallHsdpa+VS.HsdpaToDCH

Succ.RABSetup+ VS.HsdpaToDCHSucc.RABRelease + Max((VS.DownsizingStep1Success.DchHsdpa -

VS.UpsizingSuccess.DchHsdpa, 0.0)))

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 28

1 HSDPA Performance Monitoring

HSDPA Call Drop Indicator

=#573.[27]

(#573.[27]+#688.[27]+#0954.[0,1]+Max(#1159.[0]- #1165.[0]; 0,0))

FDDCell metric

HSDPA

Call Drop

Indicator

Call Drop

0

1000

2000

3000

4000

5000

6000

7000

8000

9000

8 Feb 07 9 Feb 07 10 Feb 07 11 Feb 07 12 Feb 07 13 Feb 07 14 Feb 07 15 Feb 07 16 Feb 07 17 Feb 07 18 Feb 07 19 Feb 07 20 Feb 07 21 Feb 07

CA

C S

ucce

ss

0,00%

10,00%

20,00%

30,00%

40,00%

50,00%

60,00%

70,00%

80,00%

90,00%

Cal

l Dro

p R

ate

Outdoor276654_0 Outdoor276654_1 Outdoor276654_2 Outdoor276654_3 Outdoor276654_4 Outdoor276654_5

Outdoor276654_0 Outdoor276654_1 Outdoor276654_2 Outdoor276654_3 Outdoor276654_4 Outdoor276654_5

=

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 433: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 29

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

HSDPA Call Drop indicator ( HSDPA032) :

VS.IuAbnormalReleaseRequestPs.DlAsCnfHsdpa /

(VS.IuAbnormalReleaseRequestPs.DlAsCnfHsdpa + VS.RadioBearerReleaseSuccess.TgtCallHsdpa+VS.HsdpaToDCH

Succ.RABSetup+ VS.HsdpaToDCHSucc.RABRelease + Max((VS.DownsizingStep1Success.DchHsdpa -

VS.UpsizingSuccess.DchHsdpa, 0.0)))

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 29

HSDPA Call Drop Indicator

� Recommendation:This indicator has to be monitored on the cells where HSDPA has been activated. Some HSDPA RB can downsize in one cell and upsize in another cell, so the metric is more accurate at RNC level. Besides, it is assumed that there is no ping pong between HSDPA state and DCH state (i.e. repetitions of multi-service during the same HSDPA call are negligible).

� Expected result:The metric could be impacted by iRM parameter settings (e.g. if very short Always-On Timers, the number of HSDPA RB could increase), therefore it is difficult to provide expected result; Nevertheless based on field measurements, the Call Drop Indicator shall be contained between 2% and 15% depending also on the mobility environment.

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 434: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 30

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 30

1 HSDPA Performance Monitoring

HSDPA Call Drop Rate

� Metric definition: HSDPA call drop rate at RNC level

Number of Iu abnormal release request

Number of granted RAB

=HSDPA call drop rate

at RNC level

Σ #573.[12] + Σ #561.[12]

#673.[10-16]

RNC metric

=

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 435: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 31

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 31

1 HSDPA Performance Monitoring

Number of HSDPA Drops Per Minutes

� Recommendation :This indicator has to be monitored on the areas where the HSDPA has been activated.

� Expected result :The number of drops per hour of HSDPA call should not exceed 2 drops per hourmeaning 1 HSDPA every 30 minutes of RB allocation (this is not yet a troubleshooting threshold but an upper limit of what is surely not acceptable).:The value is highly dependant on the HSDPA RB Activity Factor: the number of HSDPA drops per hour is from 0,2 to 1 drops per hour.

=

NUMBER OF HSDPA DROPS PER MINUTE

600 x #573.[12]

#692.[14]

RNC metric

=

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 436: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 32

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 32

Mobility Monitoring

Page 437: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 33

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 33

1 HSDPA Performance Monitoring

HSDPA Mobility scenarios

R99 cell R99/HSDPA cell

HSDPA cell

RNC

HSDPA cell

Traffic Segmentation feature allows to deal with a multi-layer scenario where HSDPA is available in only one of the layers.

Mobiles are redirected to the right layer at RRC connection establishment in order that mobiles that are eligible to HSDPA are directed towards the HSDPA layer and that the other ones are directed towards the non-HSDPA layer. The redirection is based on the twin-cell configuration. The call flow is not modified compared to a normal call setup, the redirection only consists in indicating a target frequency in the RRC Connection Setup message (frequency info IE).

Mobiles in idle mode will select a layer according to radio conditions criteria. The cell selection/reselection algorithm is not governed by HSDPA availability so it is not possible to guarantee that an HSDPA mobile will select the HSDPA layer (and vice versa a non-HSDPA mobile will select the non-HSDPA layer).

Segmentation is done by the RNC when a mobile tries to establish a RRC connection. It is based on the Access Stratum Release Indicator IE present in RRC Connection Request, knowing that R4 mobiles do not support HSDPA. If a R4 mobile sends its connection request in the HSDPA layer, it is redirected to the non-HSPDA layer in the RRC Connection Setup message. If a R5 (or later release) mobile sends its connection request in the non-HSDPA layer, it is redirected to the HSDPA layer.

Page 438: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 34

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 34

1 HSDPA Performance Monitoring

Mobility Success Rate

=Successful HSDPA HSDPA mobility rate (intra-freq)

#950.[0]

#950.[0] + #951.[0]

FDDCell metric

=

=Successful HSDPA HSDPA mobility rate (inter-freq)

#950.[3]

#950.[3] + #951.[3]

FDDCell metric

=

=HSDPA_ R99 mobility success rate (intra Freq)

#950.[2]

#950.[2] + #951.[2]

FDDCell metric

=

HSDPA_R99 mobility success rate (inter Freq)

#950.[5]

#950.[5] + #951.[5]

FDDCell metric

=

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 439: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 35

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 35

1 HSDPA Performance Monitoring

HSDPA Mobility scenarios

R99 cell R99/HSDPA cell

HSDPA cell

RNC

RRC Connection Setup(Redirection to F2)

HSDPA cell

Traffic Segmentation feature allows to deal with a multi-layer scenario where HSDPA is available in only one of the layers.

Mobiles are redirected to the right layer at RRC connection establishment in order that mobiles that are eligible to HSDPA are directed towards the HSDPA layer and that the other ones are directed towards the non-HSDPA layer. The redirection is based on the twin-cell configuration. The call flow is not modified compared to a normal call setup, the redirection only consists in indicating a target frequency in the RRC Connection Setup message (frequency info IE).

Mobiles in idle mode will select a layer according to radio conditions criteria. The cell selection/reselection algorithm is not governed by HSDPA availability so it is not possible to guarantee that an HSDPA mobile will select the HSDPA layer (and vice versa a non-HSDPA mobile will select the non-HSDPA layer).

Segmentation is done by the RNC when a mobile tries to establish a RRC connection. It is based on the Access Stratum Release Indicator IE present in RRC Connection Request, knowing that R4 mobiles do not support HSDPA. If a R4 mobile sends its connection request in the HSDPA layer, it is redirected to the non-HSPDA layer in the RRC Connection Setup message. If a R5 (or later release) mobile sends its connection request in the non-HSDPA layer, it is redirected to the HSDPA layer.

Page 440: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 36

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 36

1 HSDPA Performance Monitoring

Mobility Success Rate

=R99_HSDPA mobility success rate (intra Freq)

#950.[1]

#950.[1] + #951.[1]

FDDCell metric

=

R99_HSDPA mobility success rate (inter Freq)

#950.[4]

#950.[4] + #951.[4]

FDDCell metric

=

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 441: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 37

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 37

1 HSDPA Performance Monitoring

HSDPA/DCH transitions

=R99_HSDPA mobility success rate (intra Freq)

#954

#954 + #956

FDDCell metric

=

R99_HSDPA mobility success rate (inter Freq)

#953

#953+ #955

FDDCell metric

=

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 442: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 38

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 38

1 HSDPA Performance Monitoring

HSDPA TO HSDPA PRIMARY CELL CHANGE PER MINUTE OF CALL

=HSDPA TO HSDPA PRIMARY CELL CHANGE PER MINUTE OF CALL

#950.[0]

#692.[14]

FDDCell metric

=

� Recommendation :The metric has to be monitored when HSDPA is activated to measure the frequency of Primary Cell change from HSDPA to HSDPA. This is very important since each primary cell change impacts the HSDPA Throughput: there is time interruption and the HSDPA traffic can no be transferred.

� Expected result :In case of areas with high frequency results, then mobility parameter settings should be studied so that the number of primary cell change can decrease without impacting R99 traffic. Field Performance Assessment show that the frequency is very low in few network (equal to 0,04 primary cell change / min) but is mainly contain from 0,4 to 0,8 Primary Cell Change / Min of Call.

600 x

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 443: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 39

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 39

Capacity Monitoring

Page 444: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 40

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 40

1 HSDPA Performance Monitoring

HSDPA Capacity Monitoring

� The Power used for HSDPA shall be evaluated in order to estimate if the Power is a limitation resource to reach the target HSDPA throughput.

DCH

CCCNodeBNodeBNodeBNodeB

OCNS (opt.)

PMaxCell

E-DCH

PHsdpaHS-DSCH

DCH marginNodeB

NodeB

HS-SCCH

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 445: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 41

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 41

1 HSDPA Performance Monitoring

HSDPA Capacity Monitoring

� Recommendation :The metric has to be monitored when HSDPA is activated to measure its impact on the PA occupancy. It is usable when HSDPA is activated in the Cell only and the unit is mW. This indicator can be correlated to the counter RadioTxCarrierPwr (#10204) to assess the part of HSDPA Power on the total Power used. Moreover; the HSDPA Power used could be compared with the expected Power for HS-PDSCH based on the Measurement PowerOffset(MPO) setting in order to identify limitations (e.g. PDU limitations due to lack of Iub Bandwidth).

� Expected result :It depends on the HSDPA Traffic and the UTRAN parameter settings.

=10801.[Avg] + #10803.[Avg]

100

FDDCell metric

=AVERAGE HSDPA

POWER USED

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 446: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 42

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 42

1 HSDPA Performance Monitoring

HSDPA Capacity Monitoring

� Recommendation :The metric has to be monitored when HSDPA is activated to measure its impact on the PA occupancy. It is usable when HSDPA is activated in the Cell only and it represents the average (in linear) of the total transmitted power per sector and per frequency at the Tx Channelizer estimated every 100 ms available for HSDPA. The unit is in Watts.

� Expected result :If this metric indicates that the available radio tx carrier power for HSDPA is too low to reach HSDPA throughput target, then appropriate actions have to be considered.

=#10205.[0].[Avg]- #10205.[1].[Avg]

FDDCell metric

=AVAILABLE RADIO TX CARRIER POWER (W) 1000

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 447: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 43

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 43

1 HSDPA Performance Monitoring

HSDPA Capacity Monitoring

=

#10817

FDDCell metric

=NUMBER OF PA OVERLOAD SAMPLES

DCH

CCCNodeBNodeBNodeBNodeB

OCNS (opt.)

PMaxCell

E-DCH

PHsdpaHS-DSCH

DCH margin

NodeB

NodeB

HS-SCCH

90%

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 448: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 44

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 44

1 HSDPA Performance Monitoring

HSDPA Capacity Monitoring

� Expected result :If this counter is regularly incremented, then appropriate actions should be taken (e.g. go to STSR1+1 or re-set MeasurementPowerOffset parameter).

However note that the counter VS.HsdpaPAOverload is incremented each time the average power during 100ms is more than 90% of max power configured after reception of PMM which is not synchronized with Tx Carrier Power calculation samples frequency.

This is the reason why this indicator could be incremented without the maximum Total Transmitted Carrier Power indicator over 90%.

Based on Performance Field Assessment performed in the last quarter 2006, the number of cells with PA overload samples incremented during Busy Hour is from 0 to 50 cells. It depends on the network size and the HSDPA carrier configuration (shared or dedicated carrier).

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 449: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 45

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 45

1 HSDPA Performance Monitoring

HSDPA Capacity Monitoring

� Recommendation :The metric has to be monitored when HSDPA is activated to measure its impact on the PA occupancy. It is usable when HSDPA is activated in the Cell only and it represents the average/ min & max (in linear) of the total transmitted power per sector and per frequency at the Tx Channelizerestimated every 100 ms. The unit is in Percentage.The monitoring of the Radio Tx Carrier Power usage shall be completed with the distribution of the DL Tx carrier power.

� Expected result :If this metric indicates that the radio tx carrier power usage is too high, thenappropriate actions have to be considered.

#10205.[1].[Avg]FDDCell metric

=Average Radio TX Carrier Power Usage (%) #10205.[0].[Avg]

#10205.[1].[Max]FDDCell metric

=Max Radio TX Carrier Power Usage (%) #10205.[0].[Max]

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 450: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 46

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 46

1 HSDPA Performance Monitoring

HSDPA Capacity Monitoring

� Recommendation :The metric has to be monitored when HSDPA is activated to measure its impact on the PA occupancy. The DL TX power ratio P/Pmax received from NBAP common measurement per cell. It details the number of common measurements, according to their respective ranges and during the reporting period. It is useful to assess the PA capacity usage.

� Expected result:The distribution of high Dl Power Usage shall increase with the HSDPA activity penetration.

#0307.[i]FDDCell metric

=Part of time with Radio TxCarrier Power above xx % #0307

100%90%80%40% 70%

[4][3][2][1]

0%

[0]

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 451: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 47

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 47

1 HSDPA Performance Monitoring

DL Power Capacity Analysis

RB Establishment Unsuccess

UnavailableDlPowerResources > 0

RL Reconfig Prepare UnsuccessRrmRefusal > RB Establishment Unsuccess

UnavailableDlPowerResources

yes

yes (optional)

yes

Stopno

Power_Load.Max (%) > 80 %

yes

Call allocation failure due to lack of DL Power resources

Call allocation & iRM Sched. upgrade failure due to lack of DL Power resources

- Reduction of iRM Power Thresholds- Tuning of Power allocation of Radio Bearer- Tuning of Power allocation of common Channels- Add a new capacity Layer

Power_Load % = VS.AvgTxPower / PA_Power@RefpointPA_Power@Refpoint = Min(PAMax – Loss, MaxTxPower)

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 452: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 48

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 48

1 HSDPA Performance Monitoring

HSDPA Capacity Monitoring

� Recommendation :The metric has to be monitored when HSDPA is activated the mean number of OVSF codes SF16 that are really used. It can be used to compare with the expected number of SF16 codes taken by the HSDPA users in the cell and to identify cells with high limitations (e.g. Power limitation).

� Expected result:Based on the Performance Field Assessment performed Q42006, the mean number of HS-DSCH Codes per User is between 3,3 to 4,1 HS-DSCH codes per HSDPA User while it should go up to 5 codes (for Category 12 or 6). This is explained by low CQI or lack of PDU (due to Power /Transport limitations or HSDPA call profile).

#10802FDDCell metric

=MEAN NUMBER OF HS-DSCH CODES PER USER #10804

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 453: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 49

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 49

1 HSDPA Performance Monitoring

HSDPA Capacity Monitoring

� Recommendation :These indicators shall be impacted by the policy of HSDPA RB allocation (HSDPA Always On timers) and should be correlated with the average number of HSDPA RB Established (RB013).

� Expected result:Result will depend on the iRM policy of the customer.

#10820

FDDCell metric

=NUMBER OF HSDPA UE PER H-BBU

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 454: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 50

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

For CS domain:

CS call drop rate can be computed for Voice and Video services specifically

For PS domain:

PS call drop rate is sensitive to the duration used before PS RAB is released to maintain the PS RAB when traffic activity tops. Therefore PS call drop rate highly depends on Always-On algorithm parameters setting.

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 50

1 HSDPA Performance Monitoring

HSDPA Capacity Monitoring

� Recommendation :The raw counter monitoring will be useful to monitor the MAC-hs schedulerimprovement.

� Expected result:Less MAC-d PDU’s discarded due to Timer expiry means less data stocked in the Node B buffer

#10816

FDDCell metric

=NUMBER OF KBITS BUFFERED IN NODE B

TypeNetwork

Element

5.0_Metric id

or counter id5.0_Metric name

metric RNC 50_IU007_R%CsVideo Call Drop Rate%CsVideo%50_IU007_R

metric RNC 50_IU007_R%CsVoice Call Drop Rate%CsVoice%50_IU007_R

metric RNC 50_IU007_R%Ps Call Drop Rate%Ps%50_IU007_R

Page 455: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 51

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 51

Traffic Monitoring

Page 456: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 52

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 52

1 HSDPA Performance Monitoring

HSDPA Quality Monitoring

� Recommendation :This indicator has to be monitored on the RNC where HSDPA has been activated to assess the number of HSDPA RAB granted successfullyestablished. However, the HSDPA RB set-up can reconfigure in PS R99 RB as soon as it leaves the HSDPA area.

� Expected result:The result can be impacted by the RRM strategy (e.g. Always-On strategy).

#0673.[ 10-16]

RNC metric

=NUMBER OF HSDPA GRANTED RAB

Page 457: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 53

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

RNC pannel subset

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 53

1 HSDPA Performance Monitoring

HSDPA Quality Monitoring

� Recommendation:This indicator has to be monitored on the RNC where HSDPA has been activated to assess the activity factor of the HSDPA RB.

� Expected result:Based on the Performance Field Assessment performed Q4 2006, theHSDPA Activity Factor is very different depending on HSDPA Call Profile from 3% to 36%.

RNC metric

=HSDPA RAB ACTIVITY FACTOR#1526[6]

#692[14] x 100

Page 458: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 54

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 54

1 HSDPA Performance Monitoring

HSDPA Quality Monitoring

� Recommendation:This indicator has to be monitored on the RNC where HSDPA has been activated to assess the amount of data in kbps that are transferred during the HSDPA RB allocation.

� Expected result:The result will depend on the HSDPA Call Profile and shall have the same trend as the HSDPA RAB Activity Factor trend.

#1473[6] x 10RNC metric

=HSDPA RAB USAGE (KBPS) AT RNC LEVEL #692.[14]

Page 459: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 55

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

HSDPA RAB USAGE (KBPS) AT CELL LEVEL

Metric definition : #1457.[43-50]/#0011.[27]

Metric Id : Traffic028

Applicability : Cell – Group of cells

Associated counters :

#0011 - VS.RadioLinkEstablishedPerCell

#1457 - VS.DedicatedDownlinkKbytesRlcActiveCells

Recommendation :

This indicator has to be monitored on the cell where HSDPA has been activated to

assess the amount of data in kbps that are transferred during the HSDPA RL

allocation in active cells. In case of several cells in the AS, then the indicator will also

consider the active cells (and not only the Primary cell) even if there is no HSDPA sent

in the air interface.

Expected result :

The result will depend on the HSDPA Call Profile and can be impacted by high value

of mean sector per user.

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 55

1 HSDPA Performance Monitoring

HSDPA Quality Monitoring

� Recommendation:This indicator has to be monitored on the cell where HSDPA has been activated to assess the percentage of time radio resources occupied by HSDPA.

� Expected result:The result will depend on the HSDPA traffic in the cell: based on the Performance Field Assessment performed in Q4 2006, the daily HSDPA duration is from 1 minute to 7 minutes of HSDPA activity duration. Note that the trend is increasing very highly on the most HSDPA loaded networks.

#10818RNC metric

=HSDPA ACTIVITY RATE#10803.NbEvnt

Page 460: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 56

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 56

1 HSDPA Performance Monitoring

HSDPA Quality Monitoring

� Recommendation:This indicator has to be monitored on the RNC where HSDPA has been activated to assess the mean call duration for HSDPA Traffic. It represents the mean duration of the RAB configured in HSDPA.

� Expected result:Based on Performance Field Assessment performed in Q4 2006, the mean HSDPA RB duration is from 10 seconds to 143 seconds depending on the HSDPA Call Profile in each network.

#692.[14].cum x 0.1RNC metric

=HSDPA MEAN CALL DURATION AT RNC LEVEL #673.[ 10-16]

Page 461: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 57

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 57

1 HSDPA Performance Monitoring

HSDPA Quality Monitoring

� Recommendation:This indicator has to be monitored on the Cell where HSDPA has been activated to assess the 16 QAM usage penetrations.

� Expected result:The result shall increase with the new category of UE available and supported in UA5.0.

#10805FDDCell metric

=HSDPA 16QAM USAGE#10804.[Cum]

Page 462: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 58

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 58

1 HSDPA Performance Monitoring

HSDPA Quality Monitoring

� Recommendation:This indicator has to be monitored on the Cell where HSDPA has been activated to assess the penetration of HSDPA traffic compared to the total PS traffic.

� Expected result:The result will increase with the HSDPA traffic and also due to the PS traffic transformation (e.g. replacement of R99 data-cards by R5 or R6 data-cards). Based on Performance Field Assessment performed in Q4 2006, the HSDPA Traffic Penetration in each network is very different from 5% to 78%.

#1526.[6]FDDCell metric

=HSDPA TRAFFIC PENETRATION (%)#1526.[6-13]

Page 463: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 59

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

DISTRIBUTION OF UE CATEGORY CALL ATTEMPTS (%)

Metric definition :

• Proportion of UE Category 6 Call Attempts = #0668.[5]/#0668

• Proportion of UE Category 7 Call Attempts = #0668.[6]/#0668

• Proportion of UE Category 8 Call Attempts = #0668.[7]/#0668

• Proportion of UE Category 9 Call Attempts = #0668.[8]/#0668

• Proportion of UE Category 10 Call Attempts = #0668.[9]/#0668

• Proportion of UE Category 12 Call Attempts = #0668.[11]/#0668

Metric Id : HSDPA048

Applicability : Cell – Group of cells - RNC - Network

Associated counters :

#1526 - VS.CallAttemptsUeCat (#0668)

Recommendation :

This indicator has to be monitored on the Cell where HSDPA has been activated to

assess the repartition of UE category inside the HSDPA traffic.

Expected result :

The result will depend on the HSDPA type of UE.

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 59

1 HSDPA Performance Monitoring

HSDPA Quality Monitoring

#668.[i-1]FDDCell metric

=DISTRIBUTION OF UE CATEGORY i CALL ATTEMPTS (%) Σ #668[0-11]

1.8 MbpsQPSK only15Category 12

0.9 MbpsQPSK only25Category 11

14.4 MbpsQPSK & 16-QAM115Category 10

10.2 MbpsQPSK & 16-QAM115Category 9

7.3 MbpsQPSK & 16-QAM110Category 8

7.3 MbpsQPSK & 16-QAM110Category 7

3.6 MbpsQPSK & 16-QAM15Category 6

3.6 MbpsQPSK & 16-QAM15Category 5

1.8 MbpsQPSK & 16-QAM25Category 4

1.8 MbpsQPSK & 16-QAM25Category 3

1.2 MbpsQPSK & 16-QAM35Category 2

1.2 MbpsQPSK & 16-QAM35Category 1

Max Peak RateModulationInter-TTI Min IntervalHS-PDSCH Max NumberHS-DSCH Category

1.8 MbpsQPSK only15Category 12

0.9 MbpsQPSK only25Category 11

14.4 MbpsQPSK & 16-QAM115Category 10

10.2 MbpsQPSK & 16-QAM115Category 9

7.3 MbpsQPSK & 16-QAM110Category 8

7.3 MbpsQPSK & 16-QAM110Category 7

3.6 MbpsQPSK & 16-QAM15Category 6

3.6 MbpsQPSK & 16-QAM15Category 5

1.8 MbpsQPSK & 16-QAM25Category 4

1.8 MbpsQPSK & 16-QAM25Category 3

1.2 MbpsQPSK & 16-QAM35Category 2

1.2 MbpsQPSK & 16-QAM35Category 1

Max Peak RateModulationInter-TTI Min IntervalHS-PDSCH Max NumberHS-DSCH Category

Available

Categories

Page 464: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 60

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 60

Quality Monitoring

Page 465: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 61

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

HSDPA CELL THROUGHPUT

Metric definition : 500*(#10809 / #10818)

Metric id : Traffic035

Applicability : - Cell - Group of Cells - RNC - Network

Associated counters :

#10809 – VS.HsdpaTxDataBitsSchedTota.Cum

#10818 - VS.HsdpaTTIsUsed

Recommendation :

This indicator will measure the HSDPA throughput per cell in the air interface including

the retransmissions at MAC-d level.

Expected result: Based on the Performance Field Assessment performed in Q4

2006, the HSDPA Cell Throughput is from 950 kbps to 1170 kbps.

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 61

1 HSDPA Performance Monitoring

HSDPA Quality Monitoring

#10806

FDDCell metric

=MAC-D THROUGHPUT PER CELL#10818

500 x

� Recommendation:It is the key metric for measuring the HSDPA throughput during transfer period by considering only the acknowledged MAC-d PDU’s. This indicator can be correlated to the Part of radio resources shared to approximate the Mac-d throughput per user (and not per cell) by dividing this indicator by [1+”Part of radio resources shared”].

� Expected result:Based on Performance Field Assessment performed in Q4 2006, the MAC-d Throughput per cell is between 790 kbps and 980 kbps in each network depending mainly on the hardware deployment and on the radio conditions. This metric is impacted when there is low ACK ratio, the ACK ratio (which is around 87% in main networks).

Page 466: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 62

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 62

1 HSDPA Performance Monitoring

HSDPA Quality Monitoring

#1490.[6]FDDCell metric

=RESIDUAL BLER AT RLC LAYER#1489.[6]

� Recommendation:It is useful to observe the Residual BLER at RLC layer.

� Expected result:The Residual BLER shall be very low since it is mainly caused by RLC timers or by the few MAC-d PDU’s discarded in the BTS. Based on Performance Field Assessment performed in Q4 2006, the Residual BLER is quite different depending the networks: from 0,4% to 1,8%. It can be assumed that the Residual BLER shall not exceed 1%.

Page 467: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 63

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 63

1 HSDPA Performance Monitoring

HSDPA Quality Monitoring

#10812FDDCell metric

=DTX RATIO#10810 + #10811 + #10812)

#10810FDDCell metric

=ACK RATIO#10810 + #10811 + #10812)

#10811FDDCell metric

=NACK RATIO#10810 + #10811 + #10812)

CQI + NACK

CQI + ACK CQI + DTX

Data

Data

Page 468: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 64

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

DISTRIBUTION OF RECEIVED CQIMetric definition :· Distribution of Received CQI from 0 to 9= #10819.[0-9]/ #10819· Distribution of Received CQI from 10 to 14= #10819.[10-14]/ #10819· Distribution of Received CQI from 15 to 17 = #10819.[15-17]/ #10819· Distribution of Received CQI from 18 to 20 = #10819.[18-20]/ #10819· Distribution of Received CQI from 21 to 22 = #10819.[21-22]/ #10819· Distribution of Received CQI from 23 to 25 = #10819.[23-25]/ #10819· Distribution of Received CQI from 26 to 30 = #10819.[26-30]/ #10819· Distribution of Received CQI not detected = #10819.[31]/ #10819Metric id : HSDPA049Applicability : - Cell - Group of Cells - RNC - NetworkAssociated counters :#10819 - HsdpaReceivedCQIRecommendation :It is useful to observe the received CQI to assess the level of quality reception forHSDPA. This information is essential during investigation after HSDPA Throughputdegradation.Expected result:The distribution of received CQI will depend only on radio conditions. When thedistribution of Received CQI below 15 is important, then the HSDPA Throughput ishighly impacted.

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 64

1 HSDPA Performance Monitoring

HSDPA Quality Monitoring

#10819.[x-y]

FDDCell metric

=DISTRIBUTION OF RECEIVED CQI from x to y #10819

#10819.[31]

FDDCell metric

=DISTRIBUTION OF RECEIVED CQI not detected #10819

16-QAM3024 kbps530

16-QAM3024 kbps529

............

16-QAM1440 kbps516

QPSK1296 kbps515

QPSK1008 kbps414

QPSK864 kbps413

QPSK720 kbps312

QPSK576 kbps311

QPSK432 kbps310

QPSK288 kbps29

QPSK288 kbps28

QPSK144 kbps27

QPSK144 kbps16

QPSK144 kbps15

QPSK0 kbps14

QPSK0 kbps13

QPSK0 kbps12

QPSK0 kbps11

out of range0

ModulationRLC ThroughputHS-PDSCH NumberCQI Value

Category 6 UE CQI Mapping Table

CQI Distribution for Site OutDoor example

CQI Distribution%0to9

CQI Distribution%23to25

CQI Distribution%21to22

CQI Distribution%18to20

CQI Distribution%10to14

CQI Distribution%15to17

CQI Distribution%26to30

CQI Distribution%NotDete

cted

CQI Distribution%0to9 CQI Distribution%10to14 CQI Distribution%15to17

CQI Distribution%18to20 CQI Distribution%21to22 CQI Distribution%23to25

CQI Distribution%26to30 CQI Distribution%NotDetected

Page 469: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 65

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 65

2 HSUPA Performance Monitoring

Page 470: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 66

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 66

2 HSUPA Performance Monitoring

Transport & Physical Channels

E-D

PCC

HE-

DPD

CH

E-H

ICH

E-AG

CH

E-R

GC

H

� Uplink:� E-DPCCH: for signaling data (SF 256)

E-TFCI, RSN, happy bit

� E-DPDCH: for traffic data (SF 2, 4, …, 256)Traffic data, scheduling information

� Downlink� E-AGCH: Absolute Grant Channel (SF256)

E-RNTI, grant index information

� E-HICH: HARQ Indicator Channel (SF 128)ACK/NACK information

� E-RGCH: Relative Grant Channel (SF 128)+1/0/-1 from RLS

�A specific E-DCH transport channel is defined. As the classical DCH transport channel it

allows to offer transport services to higher layers.

�The E-DCH transport channel is defined by the following characteristics:

� Only for UL

� Two possible TTI : 10ms and 2ms. Only 10ms is used in UA5.

� Transport block size and Transport Block set size are free attributes of the transport

format.

� Possibility of HARQ process with retransmission procedures applied at Node B. Max

number of retransmission must be defined. Each transmitted blocks are numbered.

� Two HARQ types can be used: Chase Combining/cc and incremental redundancy/ir

� Possibility of smart redundancy management at Rx. The Redundancy Version (RV) used for the transmission must be managed in order to apply Chase combining or Incremental

Combining mechanisms

� RV always = rv0 in case of cc

� RV = any rvindex of the RV table in case of ir

� Turbo coding with rate 1/3 is used

� CRC is 24 bits length

� E-TFCI (Transport Format Combination Indication for E-DCH) indicates which format is

currently used for the UL transmission.

Page 471: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 67

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 67

Accessibility Monitoring

Page 472: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 68

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 68

2 HSUPA Performance Monitoring

HSUPA Accessibility Monitoring

Cell&RncAccessibilityNew Raw CounterE-DCH Cac RejectionVS.EdchIuRelAbnormal.CACReject

Cell&RncAccessibilityNewSuccessful rate DCH to eDCHHSUPA012

RncAccessibilityNewPROPORTION OF E-DCH FALLBACKHSUPA005

Page 473: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 69

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 69

MonoStepMultiStep

2 HSUPA Performance Monitoring

Number of CAC reject on e-DCH cell

FDDCell metric

Number of CAC reject on e-DCH cell = #0963.[0]

HSUPA/HSDPA RB to established

CAC OK ?

DCH/HSDPA RB to established

Yes

No

RAB assignment (to establish or to release)IU release

Primary cell changeIncoming Inter-RNC UE involved Hard Handover

Incoming Intra-RNC Alarm Hard HandoverMobility

RabAssignment

HSUPA to DCH Fallback Steps

HSUPA/HSDPA RB established DCH/DCH RB

to established

New RNC counter available in UA5.0 to assess the number of CAC reject on e-DCH cell:

� VS.EdchIuRelAbnormal (#0963)

� Definition: Number of Iu release requested by e-DCH call after CAC reject or a Mobility procedure failure

� Location: Reference FDDCell

� Screening 0: CAC reject on the e-DCH call

� Screening 1: Mobility procedure failure (CAC or Mobility)

Metric based on this raw counter is enough to the number of CAC failure in E-DCH cell:

Metric definition : #0963.[0]

Metric Id: NOK

Applicability : Cell - Group of Cells – RNC - Network

Associated counters :

#0963 - VS.EdchIuRelAbnormal

Recommendation :

This indicator has to be monitored on the areas (group of cells/ RNC’s) where HSUPA

has been activated. It represents the number of Iu release requested by e-DCH call

after CAC reject.

Expected result :

It should be low in most of HSUPA cells.

Page 474: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 70

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 70

2 HSUPA Performance Monitoring

Successful rate DCH to HSUPA transitions

ReferenceFDDCell metric

Successful rate DCH to E-DCH =#0696.[0]

#0696.[0] + #0697.[0]

RANAP/ RAB A ss ignm ent R equest (RAB param , b ind ing Id )

RRC/ RB S etup (E -DCH info , E -RNTI ,

CFN )

RRC/ RB Se tup Com p lete

The UE is p rovid ed w ith th e n ew rad io lin k

con figu ra tion . A n ew RAB (co rrespond ing to th e

n ew D TC H ) is added to the cu rren t con figu ra tion

NBAP/ Rad io L ink Reconf igurat ion Prepare (

E -D PCH info , E -DCH FDD info , E -DCH m ac-d flow to add , Se rv ing

E -DCH RL , E -DCH RL ind ication=E -DCH , E -DCH Specif ic I nfo… .)

NBAP/ Rad io L ink R econf igurat ion R eady (E -DCH FDD info Response , E -DCH FDD D L

Contro l Channe l …

The Rad io L in k is recon figu red to add th e E -

D PCH in up lin k in th e se rv ing ce ll. (The H S -

D SC H pa rt is no t show n)

NBAP/ Rad io L ink Reconfigurat ion Comm it (

CFN )

UE RNCNode B MSC

New RNC counter available in UA5.0 to assess the number of CAC reject on e-DCH cell:

� VS.SucDchToEdchTrans (#0696)

� Definition: Number of successful DCH to E-DCH transitions trigged on RAB assignement

� Location: Reference FDDCell

� Screening 0: RAB Setup

� Screening 1: RAB Release

� VS.UnsucDchToEdchTrans (#0697)

� Definition: Number of Unsuccessful DCH to E-DCH transitions trigged on RAB assignment

� Location: Reference FDDCell

� Screening 0: RAB Setup

� Screening 1: RAB Release

Page 475: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 71

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 71

Max users HSU or HSD

2 HSUPA Performance Monitoring

Proportion of HSUPA Fallback

failure!

Core Network

Rabassignment

Primary cell change

Inter RNC HHO

Internal to RNC: reach the maximum number of HSDPA or HSUPA usersExternal to RNC: NBAP or RNSAP failure

Alarm HHO

NBAP or RNSAP failure

The following HSxPA CAC failure scenarios trigger such a fallback

ReferenceFDDCell metric

PROPORTION OF

E-DCH FALLBACK=

#1601.[1,2]

#0673.[12,13]+ #1601.[1,2]+#1603.[1,2]

New RNC counter available in UA5.0 to assess the HSUPA Fallback to DCH:

� VS.SucHspaToDchFallbackCell (#1601)

� Definition: Number of calls succesfully fallbacked from HSPA to DCH on RAB assignment, mobility or reconfiguration event.

� Location: Reference FDDCell

� Screening 0: HSDPA/DCH to DCH/DCH

� Screening 1: HSDPA/HSUPA to HSDPA/DCH

� Screening 2: HSDPA/HSUPA to DCH/DCH� VS.UnsucHspaToDchFallbackCell (#1603)

� Definition: Number of calls succesfully fallbacked from HSPA to DCH on RAB assignment, mobility or reconfiguration event.

� Location: Reference FDDCell

� Screening 0: HSDPA/DCH to DCH/DCH

� Screening 1: HSDPA/HSUPA to HSDPA/DCH

� Screening 2: HSDPA/HSUPA to DCH/DCH� And VS.RabEstablishmentSuccessPerGrantedRabType (#0673) with the screening 12 & 13 pointed to HSUPA

Page 476: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 72

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 72

Retainability Monitoring

Page 477: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 73

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 73

2 HSUPA Performance Monitoring

HSUPA Retainability Monitoring

Cell&RncRetainabilityNewNumber of HSUPA Radio drops per minute of callsHSUPA014

Cell&RncRetainabilityNewHSUPA Radio Call drops rateHSUPA013

Cell&RncRetainabilityNewHSUPA Mobility Call drops rateHSUPA003

Cell&RncRetainabilityNewNumber of HSUPA Mobility drops per minute of callsHSUPA002

Page 478: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 74

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 74

2 HSUPA Performance Monitoring

HSUPA Mobility Call Drop rate

RNC metric

HSUPA Mobility Call drops rate =

Σ #963.[1]

#0673.[12,13]

Node B RNC CN

Radio Link Deletion Resp

Iu Release Request

Iu Release Command

Radio Link Deletion Req

UE

#963 VS.EdchIuRelAbnormal

Iu Release Complete

E-DCH mobility Failure(NBAP or RRC)

New RNC counter available in UA5.0:

� VS.EdchIuRelAbnormal (#0963)

� Definition: Number of Iu release requested by e-DCH call after CAC reject or a Mobility procedure failure

� Location: Reference FDDCell

� Screening 0: CAC reject on the e-DCH call

� Screening 1: Mobility procedure failure (CAC or Mobility)

� VS.RabEstablishmentSuccessPerGrantedRabType (#0673) with the screening 12 & 13 pointed to HSUPA

New RNC counter available in UA5.0:

� VS.EdchIuRelAbnormal (#0963)

� VS.UlAsConfIdAvgNbrEstablished (#0693) with the screening 13 pointed to HSUPA

HSUPA002 : Number of HSUPA Mobility drops per minute of calls

VS.EdchIuRelAbnormal.MobilityFailure / VS.UlAsConfIdAvgNbrEstablished.UlAsCnfHsupa.Cum

Page 479: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 75

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 75

#962.[1] VS.EdchIuRelAbnormal

Loss of UL synchro detected on E-DCH RL

2 HSUPA Performance Monitoring

HSUPA Radio Call Drop rate

RNC metric

HSUPA Radio Call Drop rateat RNC level

=Σ #962.[1]

#0673.[12,13]

#962.[0] VS.EdchCellDeletion

Node B RNC CN

Iu Release Request“UTRAN generated reason”

Iu Release Command

UE

Active Set Update“Deletion of E-DCH RL”

Node B RNC CN

Radio Link Failure Indication

Iu Release Request“UTRAN generated reason”

Iu Release Command

UE

New RNC counter available in UA5.0:

� VS.EdchCellDeletion (#0962)

� Definition: Number of E-dch cell deletion: The primary cell which is also the E-DCH cell has been deleted.

� Screening 0: Deletion during an ASU procedure

� Screening 1: RL Failure on the E-DCH RL Failure

� Location: Reference FDDCell

� VS.RabEstablishmentSuccessPerGrantedRabType (#0673) with the screening 12 & 13 pointed to HSUPA

� VS.UlAsConfIdAvgNbrEstablished (#0693) with the screening 13 pointed to HSUPA

HSUPA Radio Call Drop rate per minute = 600*(#0962.[1]/#0693 [13]) .cum

HSUPA Mobility Call Drop rate per minute = 600*(#0963.[1]/#0693.[13]) .cum

Page 480: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 76

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 76

Mobility Monitoring

Page 481: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 77

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 77

2 HSUPA Performance Monitoring

HSUPA Mobility Monitoring

Cell&RncMobilityNewPrimary Cell Change per Minute of HSUPA CallHSUPA006

Cell&RncMobilityNewHSUPA Mobility success rateHSUPA001

Page 482: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 78

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 78

2 HSUPA Performance Monitoring

HSUPA Mobility Success Rate

RNCsource Node B target Node B UE

RB Reconfiguration (Activation CFN, new E-RNTI, Serving E-DCH RL, E-AGCH info, E-HICH info)

RL Reconfiguration Ready

Measurement Control (new neighbouring list)

RL Reconfiguration Prepare

RB Reconfiguration Complete

Primary cell change

RL Reconfiguration Ready

RL Reconfiguration Prepare

RL Reconfiguration Commit (Activation CFN)

Activation CFN

Reference FDDCell metric

HSUPA Mobility Success Rate =

#960.[mobility type]

#960.[mobility type] + #961.[mobility type]

UA5.0 Counter used:

� VS.EdchSucMobility (#0960)

� Screening 0/3: E-DCH Cell to E-DCH (Intra/Inter)

� Screening 1/4: non E-DCH Cell to E-DCH (Intra/Inter)

� Screening 2/5: non E-DCH Cell to non E-DCH (Intra/Inter)

� Location: FDDCell

� VS.EdchUnsucMobility (#0961)

� Screening 0/3: E-DCH Cell to E-DCH (Intra/Inter)

� Screening 1/4: non E-DCH Cell to E-DCH (Intra/Inter)

� Screening 2/5: non E-DCH Cell to non E-DCH (Intra/Inter)

� Location: FDDCell

Page 483: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 79

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 79

2 HSUPA Performance Monitoring

Primary Cell Change per minute of call HSUPA

� Recommendation:The metric has to be monitored when e-DCH is activated to measure the frequency of Primary Cell change from e-DCH to e-DCH. This is very important since each primary cell change impacts the HSUPA Throughput: there is time interruption and the HSUPA traffic can no be transferred.

� Expected result:In case of areas with high frequency results, then mobility parameter settings should be studied so that the number of primary cell change can decrease without impacting R99 traffic.

Reference FDDCell metric

Primary Cell Change per minute of call =#960.[0,3]

#693[13].cum600 x

Page 484: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 80

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 80

Capacity Monitoring

Page 485: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 81

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 81

2 HSUPA Performance Monitoring

HSUPA Capacity Monitoring

Cell&RncCapacityNew Raw CounterThe Rise over Thermal (Rot) VS.eDCHriseOverThermal

Cell&RncCapacityNew Raw CounterNUMBER OF LOAD EXCESS STATUS

VS.eDCHstatus

Cell&RncCapacityNewAVERAGE THERMAL NOISE

ULOAD004

Cell&RncCapacityNewUplink Cell Load ULOAD001

Cell&RncCapacityNewHSUPA Common DL Power UsageHSUPA007

Page 486: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 82

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 82

2 HSUPA Performance Monitoring

HSUPA Common Channel Power

FDDCell metric

HSUPA Common Channel Power =#10901.Avg

#10205.[1].Avg100 x

E-AGCH

E-HICH

E-H

ICH

E-HICH

E-H

ICH

E-AGCH

E-A

GC

H

E-A

GC

H

� VS.eDCHcommonChannelsTxPower (#10901)

� Total Transmitted power on all allocated e-AGCH and e-HICH/ e-RGCH channels per 2 ms period.

� Unit: 100 mW

� Location: FDDCell

VS.RadioTxCarrierPwr - #10205

average value of the total transmitted power - at the Tx channelizer - for each cell (i.e. per sector

and per frequency). The cumulated value at the end of the observation period and the number

of samples are provided. The minimum and maximum powers during the reporting period

are also provided.

A set of subcounters screened on: distribution according thresholds

• Sub-Counter #0 : Operational Max Power

• Sub-Counter #1 : Power used

Page 487: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 83

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 83

2 HSUPA Performance Monitoring

UL Cell Load

E-DCH

E-D

CHD

CH

FDDCell metrics

Minimum Uplink Cell Load = 10 x #10211.[Min]

Maximum Uplink Cell Load = 10 x #10211.[Max]

Average Uplink Cell Load = 10 x #10211.[Avg]

Thermal Noise

R99 traffic+ Interference

E-DCH traffic

100%% cell load

RTWPref

RTWPref + TotalRotMax

RTWPmeas

RTWPmeas

New UA5.0 NodeB Counter used:

� VS.CellULLoad (#10211)

� Average/ Min/ Max mean UL Load

� Unit: 0,1%

� Location: FDDCell

Page 488: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 84

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 84

2 HSUPA Performance Monitoring

Average Thermal Noise

E-DCH

E-D

CHD

CH

Thermal Noise

R99 traffic+ Interference

E-DCH traffic

100%% cell load

RTWPref

RTWPref + TotalRotMaxRTWP MainRTWP Div.

FDDCell metric

Average Thermal Noise =#10201.[Avg] + #10202.[Avg]

2(1- #10211.[Avg]) x

1000

New UA5.0 NodeB Counter used:

� VS.CellULLoad (#10211)

� VS.RadioWBandRxMainPwr (#10201)

� min/ max/ linear average wide-band received power per sector, per frequency, at the Rx main channelizer(sampled every 100 ms)

� VS.RadioWBandRxMainPwr (#10202)

� min/ max/ linear average wide-band received power per sector, per frequency, at the Rx diversity channelizer(sampled every 100 ms)

Recommendation :

This metric is useful to assess the average thermal noise.

Expected result :

The result of this metric should be between -109 dBm and -102 dBm.

Page 489: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 85

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 85

#10907

2 HSUPA Performance Monitoring

HSUPA UL Load Management

Thermal Noise

R99 traffic+ Interference

E-DCH traffic

RTWPref

RTWPref + TotalRotMax

RoT

RTWPmeas

Thermal Noise

R99 traffic+ Interference

E-DCH traffic

RTWPref

RTWPref + TotalRotMax

RoT

RTWPmeas

FDDCell metrics

HSUPA Rise Over Thermal = 100 x #10906.[Min/Max/Avg.]

Number Of Load Excess Status = #10907

#10906

� VS.eDCHriseOverThermal (#10906)

� The average/min/max RoT evaluated every 100 ms

� Unit: 0,01 dB

� Location: FDDCell

� VS.eDCHstatus (#10907)

� The number of period (equal to 100ms) where RTWP > RTWPmax

Page 490: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 86

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 86

Quality Monitoring

Page 491: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 87

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 87

2 HSUPA Performance Monitoring

HSUPA Quality Monitoring

Cell&RncQualityNew Raw CounterSignal to Interference Ratio for all communications per Spreading Factor VS.SIRperSF

Cell&RncQualityUpdate ( New Screening )Traffic UL Throughput at cell level ( based on activity time)

Traffic031

RncQualityUpdate ( New Screening )Traffic UL Throughput at RNC level (based on RB allocation)Traffic025

Cell&RncQualityNewUplink RSSI distributionULOAD003

Cell&RncQualityNewUplink RSSI in dbmULOAD002

Cell&RncQualityNewAverage HSUPA Throughput per UserHSUPA009

Cell&RncQualityNewHSUPA BLERHSUPA004

Page 492: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 88

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 88

2 HSUPA Performance Monitoring

HSUPA HARQ BLER & Average Throughput

FDDCell metrics

HSUPA HARQ BLER =#10903.[Cum]

#10903.[NbofEvt] + #10903.[Cum]

FDDCell metrics

Avg UL Throughput per User =500 x # 10902 .[Cum]

#10905.[Cum]

� VS.eDCHretransBlocks (#10903)

� Total number of necessary retransmissions for acknowledged Transport blocks (0 means the has been correctly

received after the first retransmission). The blocks discarded due to the maximum number of retransmissions

reached are not taken into account.

� Location: FDDCell

� VS.eDCHDataBitsentToRNC (#10902)

� Total number of necessary retransmissions for acknowledged Transport blocks (0 means the has been correctly

received after the first retransmission). The blocks discarded due to the maximum number of retransmissions

reached are not taken into account.

� Location: FDDCell

� VS.eDCHactiveusers (#10905)

� The Min/Max/Cum number of active user for a cell is cumulated every 2 ms.

� Unit: nb of user

� Location: FDDCell

Page 493: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 89

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 89

2 HSUPA Performance Monitoring

UL Radio Quality

FDDCell metrics

UL RSSI = 10*Log(#303)

FDDCell metrics

Minimum SIR for SF2 i+2 = #10206.[i].[Min]

Average SIR for SF2 i+2 = #10206.[i].[Avg]

Maximum SIR for SF2 i+2 = #10206.[i].[Max]

FDDCell metrics

#1042UL RSSI Distribution =

#1042.[i]

-105dBm-103dBm-100dBm

[4][3][2][1]

-97dBm

[0]

VS.UplinkRssi (#0303)

� Average/ Min/ Max Uplink RSSI received from NBAP Common measurement per cell

� Location: FDDCell

� VS.DistRssi (#1042)

� Provides the UL RSSI measurements received by NBAP Common according to the ranges defined in the observation

period

� Location: FDDCell

� Recommendation :

� This indicator is based on RTWP sent on NBAP Common measurement. In UA5.0, it

� is mandatory to set to TRUE the 3 following parameters: isUplinkRadioLoadEnabled,

� isNbapCommonMeasRTWPAllowed, isUlRadioLoadColorEnabled, in order to allow

� the sending of NBAP Common Measurements.

� Moreover, in case of Node B UA4.2/ UA5.0 mixed, the indictor will not represent the

� same value:

� • For UA4.2 Node B: UL RSSI estimated by the Node B

� • For UA5.0 Node B: -106;1+ RoT estimated by the Node B

� Therefore the metric can not be applied for a mixed group of cells.

� Expected result :

� The result will depend on the situation of the site.

� VS.SIRperSF (#10206)

� Average/ Min/ Max Signal to Interference Ratio for all communications per Spreading Factor

� Location: Node B

Page 494: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 90

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 90

2 HSUPA Performance Monitoring

UL Traffic Quality

FDDCell metrics

HSUPA Throughput

at RLC Layer=

#1486.[12] x 8 x1024

#0693.[13].[Cum]x100

FDDCell metrics

MAC-D HSUPA User Throughput (KBPS)

=500 * #10902

#10905.[Cum]

#1486 - VS.DedicatedUplinkKbytesRlcReferenceCell

#0693 - VS.UlAsConfIdAvgNbrEstablished

Recommendation :

It is one of the key metric to monitor to assess HSUPA quality performances. All the

retransmissions at RLC or MAC-e layers are not considered in this indicator

Expected result :

The result will depend on the radio conditions.

MAC-D HSUPA USER THROUGHPUT (KBPS)

Metric definition : 500 * #10902 / #10905.[Cum]

Metric Id : TRAFFIC001

Applicability : Cell – Group of cells - RNC - Network

Associated counters :

#10902 - VS.eDCHDataBitsentToRNC

#10905 - VS.eDCHactiveusers

Recommendation :

It is one of the key metric to monitor to assess HSUPA quality performances per User.

All the retransmissions at MAC-e layers are not considered in this indicator

Expected result :

The result will depend on the radio conditions.

Page 495: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 91

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 91

Traffic Monitoring

Page 496: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 92

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 92

2 HSUPA Performance Monitoring

HSUPA Traffic Monitoring

Cell&RncTrafficNew Raw Counter

HSUPA UL TRAFFIC (Kbytes)VS.DedicatedUplinkKbytesRlcReferenceCell.UlRabHsupa

Cell&RncTrafficNew Raw Counter

AVERAGE NUMBER OF HSUPA RBVS.UlAsConfIdAvgNbrEstablished.UlAsCnfHsupa

Cell&RncTrafficNew Raw Counter

AVERAGE/Maximum NUMBER OF HSUPA ACTIVE USERSVS.eDCHactiveusers

Cell&RncTrafficUpdate ( New Screening )

NUMBER OF HSUPA GRANTED RABRAB022

CellTrafficUpdate ( New Screening )Traffic UL (SDU payload) in Kbytes at cell level

Traffic018

RncTrafficUpdate ( New Screening )Traffic UL (SDU payload) in Kbytes at RNC level

Traffic016

RncTrafficUpdate ( New Screening )Average number of UL Bearers established

RB013_UL

Cell&RncTrafficUpdate ( New Screening )RAB Activity UL

Traffic023

Cell&RncTrafficNeweDCH Penetration factorHSUPA011

Cell&RncTrafficNewHSUPA Activity FactorHSUPA010

Page 497: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 93

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 93

2 HSUPA Performance Monitoring

HSUPA Activity & Penetration factors

FDDCell metrics

HSUPA Activity Factor =#10905.[Cum]

20 x #6903.[Cum]

FDDCell metrics

HSUPA Penetration =#1486.[12]

#1486.[6-12]

VS.eDCHactiveusers (#10905)

� VS.UlAsConfIdAvgNbrEstablished (#0693)

� Indicates the average number of UL As Conf Id over an observation period

� Location: Reference FDDCell

� VS.eDCHactiveusers (#10905)

� VS.UlAsConfIdAvgNbrEstablished (#0693)

� Indicates the average number of UL As Conf Id over an observation period

� Location: Reference FDDCell

HSUPA Penetration

#1486 - VS.DedicatedUplinkKbytesRlcReferenceCell

Recommendation :

This indicator has to be monitored on the Cell where HSUPA has been activated to

assess the number of Kbytes of SDU sent on UL for the reference cell.

Expected result :

The result will depend on the HSUPA traffic.

Page 498: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 94

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 94

2 HSUPA Performance Monitoring

HSUPA Traffic volume metrics

FDDCell metrics

Number of granted HSUPA RAB = #0673.[12,13]

FDDCell metrics

Average Number of HSUPA RB = #0693.[Avg]

FDDCell metrics

Average Number of HSUPA Active Users = #10905.[Avg]

FDDCell metrics

Amount of HSUPA Traffic (Kbytes) = #1486.[12]

Here is the UA5.0 Node B counter available:

� VS.RabEstablishmentSuccessPerGrantedRabType (#0673) Number of successful RAB establishment per granted RAB type

By using directly the raw counter, it is possible to assess the number of HSUPA active users:

� Number of HSUPA RAB Granted = #0673.[12,13]

Recommendation :

This indicator has to be monitored on the Cell where HSUPA has been activated to

assess the number of HSUPA calls at RNC or network level.

Expected result :

The result will depend on the HSUPA traffic.� VS.eDCHactiveusers (#10905)

� The number of active user for a cell is cumulated every 2 ms.

� Unit: nb of user

� Triggered every 2 ms (3 slots)

By using directly the raw counter, it is possible to assess the number of HSUPA active users:

� Average number of HSUPA Active Users = #10905.[Avg]

� Maximum number of HSUPA Active Users = #10905.[Max]

� VS.UlAsConfIdAvgNbrEstablished (#0693)

� Indicates the average number of UL As Conf Id over an observation period

� Location: Reference FDDCell

Here are the metrics linked to HSUPA RB allocation:

� Average number of HSUPA RB = #0693.[Avg]

� HSUPA Activity Factor = #10905.[Cum]/ (50 * #0693.[Cum])

VS.DedicatedUplinkKbytesRlcReferenceCell (#1486)

� Number of Kbytes of SDU sent on UL for the reference cell

� Unit: Kbytes

� Location: Reference FDDCell

Page 499: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 95

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 95

Self-Assessment on the Objectives

� Please be reminded to fill in the formSelf-Assessment on the Objectivesfor this module

� The form can be found in the first partof this course documentation

Page 500: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Section 1& � Page 96

All Rights Reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All Rights Reserved © Alcatel-Lucent 2007

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

HSxPA Performance Monitoring Section 11 � Page 96

End of Module

Page 501: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Appendices � Page 1

All rights reserved © 2007, Alcatel-Lucent

3FL12812ABAA Edition 1

Do not delete this graphic elements in here:

All rights reserved © 2007, Alcatel-Lucent

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

12Section 12Appendices

3FL12921AAAAWBZZA2 Edition 1

Page 502: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Appendices � Page 2

All rights reserved © 2007, Alcatel-Lucent

3FL12812ABAA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Appendices Appendices � 2

Blank Page

This page is left blank intentionally

First editionEL ABED, Achrafe2007-08-2401

RemarksAuthorDateEdition

Document History

Page 503: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Appendices � Page 3

All rights reserved © 2007, Alcatel-Lucent

3FL12812ABAA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Appendices Appendices � 3

UA5.0 screenings

� Switch to notes view!

Page 504: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Appendices � Page 4

All rights reserved © 2007, Alcatel-Lucent

3FL12812ABAA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Appendices Appendices � 4

UA5.0 screenings [cont.]

� Switch to notes view!

Page 505: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Appendices � Page 5

All rights reserved © 2007, Alcatel-Lucent

3FL12812ABAA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Appendices Appendices � 5

UA5.0 screenings [cont.]

� Switch to notes view!

Page 506: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Appendices � Page 6

All rights reserved © 2007, Alcatel-Lucent

3FL12812ABAA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Appendices Appendices � 6

UA5.0 screenings [cont.]

� Switch to notes view!

Page 507: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Appendices � Page 7

All rights reserved © 2007, Alcatel-Lucent

3FL12812ABAA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Appendices Appendices � 7

UA5.0 screenings [cont.]

� Switch to notes view!

Page 508: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Appendices � Page 8

All rights reserved © 2007, Alcatel-Lucent

3FL12812ABAA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Appendices Appendices � 8

UA5.0 screenings [cont.]

� Switch to notes view!

Page 509: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Appendices � Page 9

All rights reserved © 2007, Alcatel-Lucent

3FL12812ABAA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Appendices Appendices � 9

UA5.0 screenings [cont.]

� Switch to notes view!

Page 510: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Appendices � Page 10

All rights reserved © 2007, Alcatel-Lucent

3FL12812ABAA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Appendices Appendices � 10

UA5.0 screenings [cont.]

� Switch to notes view!

Page 511: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Appendices � Page 11

All rights reserved © 2007, Alcatel-Lucent

3FL12812ABAA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Appendices Appendices � 11

UA5.0 screenings [cont.]

� Switch to notes view!

Page 512: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Appendices � Page 12

All rights reserved © 2007, Alcatel-Lucent

3FL12812ABAA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Appendices Appendices � 12

UA5.0 screenings [cont.]

� Switch to notes view!

Page 513: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Appendices � Page 13

All rights reserved © 2007, Alcatel-Lucent

3FL12812ABAA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Appendices Appendices � 13

UA5.0 screenings [cont.]

� Switch to notes view!

Page 514: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Appendices � Page 14

All rights reserved © 2007, Alcatel-Lucent

3FL12812ABAA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Appendices Appendices � 14

UA5.0 screenings [cont.]

� Switch to notes view!

Page 515: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Appendices � Page 15

All rights reserved © 2007, Alcatel-Lucent

3FL12812ABAA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Appendices Appendices � 15

UA5.0 screenings [cont.]

� Switch to notes view!

Page 516: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Appendices � Page 16

All rights reserved © 2007, Alcatel-Lucent

3FL12812ABAA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Appendices Appendices � 16

End of ModuleGlossary

Page 517: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Glossary � Page 1

All rights reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

Do not delete this graphic elements in here:

All rights reserved © 2007, Alcatel-Lucent

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

13Section 13Glossary

3FL12921AAAAWBZZA2 Edition 1

Page 518: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Glossary � Page 2

All rights reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Glossary Glossary � 2

Blank Page

This page is left blank intentionally

First editionEL ABED, Achrafe2007-08-2401

RemarksAuthorDateEdition

Document History

Page 519: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Glossary � Page 3

All rights reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Glossary Glossary � 3

Abbreviations and Acronyms

� Switch to notes view!#

16-QAM 16 – Quadrature Amplitude

Modulation

1xEV-DO 1x EVolution Data Only

1xEV-DV 1x EVolution Data and Voice

1xRTT 1 times 1.25MHz Radio Transmission

Technology

3GPP 3rd Generation Partnership Project

3xEV-DV 3x Evolution Data and Voice

A

AAL2 ATM Adaptation Layer type 2

AAL5 ATM Adaptation Layer type 5

ACK ACKnowledgment

AICH Acquisition Indicator CHannel

AM Acknowledged Mode

AMC Adaptive Modulation and Coding

AMD Acknowledged Mode Data

AMR Adaptive Multi-Rate

ARQ Automatic Repeat Query

AS Access Stratum

ASC Access Service Class

ATM Asynchronous Transfer Mode

B

BCCH Broadcast Control CHannel

BCH Broadcast CHannel

BER Bit Error Rate

BFN NodeB Frame Number

BLER BLock Error Rate

BMC Broadcast Multicast Control

BPSK Binary Phase Shift Keying

BTS Base Transceiver Station

C

CAC Call Admission Control

CC Chase Combining

CCCH Common Control CHannel

CCP Communication Control Port

CCPCH Common Control Physical CHannel

CCTrCH Coded Composite Transport CHannel

CDMA Code Division Multiple Access

CEM Channel Element Module

CFN Connection Frame Number

CID Channel IDentifier

CK Ciphering Key

CM Compressed Mode

CmCH-PI Common transport CHannel Priority

Indicator (SPI)

CP NodeB Control Port

CP Control Plane

CPCH Common Packet CHannel

CPICH Common PIlot CHannel

CQI Channel Quality Indicator

CRC Cyclic Redundancy Check

C-RNC Controlling-Radio Network Controller

C-RNTI Cell-Radio Network Temporary

Identity

CS Circuit Switch

CTCH Common Traffic CHannel

D

DCCH Dedicated Control CHannel

DCH Dedicated CHannel

DL Downlink

DPCCH Dedicated Physical Control CHannel

DPCH Dedicated Physical CHannel

DPDCH Dedicated Physical Data CHannel

D-RNC Drift-Radio Network Controller

DS Delay Sensitive

DS-CDMA Direct Sequence-Code Division

Multiple Access

DSCH Downlink Shared CHannel

DTCH Dedicated Traffic CHannel

DTX Discontinuous Transmission

E

E1 Standard European PCM link (2.048

Mbps)

EDGE Enhanced Data for Global Evolution

EGPRS EDGE GPRS

F

FACH Forward Access CHannel

FBI FeedBack Information

FDD Frequency Division Duplex

FDMA Frequency Division Multiple Access

FIFO First In First Out

FP Frame Protocol

G

GMM Global Mobility Management

GPRS General Packet Radio Service

GSM Global System for Mobile

communications

GTP GPRS Tunneling Protocol

H

H-ARQ Hybrid ARQ

HFN Hyper Frame Number

HO HandOver

H-RNTI HS-DSCH Radio Network Temporary

Identifier

HSDPA High Speed Downlink Packet Access

HS-DPCCH High Speed Dedicated Physical

Control CHannel

HS-DSCH High Speed Downlink Shared

CHannel

HS-PDSCH High Speed Physical Downlink

Shared CHannel

HS-SCCH High Speed Shared Control CHannel

Page 520: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Glossary � Page 4

All rights reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Glossary Glossary � 4

Abbreviations and Acronyms [cont.]

� Switch to notes view!I

IE Information Element

IK Integrity Key

IMA Inverse Multiplexing ATM

IMEI International Mobile Equipment

Identity

IMSI International Mobile Subscriber

Identity

IMT-2000 International Mobile

Telecommunication for year 2000

IP Internet Protocol

IR Incremental Redundancy

Iu Interconnection point between RNC

and 3G Core Network

Iub Interface between Node B and RNC

Iur Interface between two RNCs

K

Kbps Kilobit per second

kHz kiloHertz

KPI Key Performance Indicator

Ksps Kilo symbol per second

L

L1 Layer 1 (Physical Layer)

L2 Layer 2 (Data Link Layer)

L3 Layer 3 (Network Layer)

LA Location Area

LAC Location Area Code

LAI Location Area Identity

LAN Local Area Network

LSB Least Significant Bit

M

MAC Medium Access Control

Mbps Megabit per second

MCC Mobile Country Code

MCPA Multi Carrier Power Amplifier

Mcps Megachip per second

MHz MegaHertz

MIR Mix Incremental Redundancy

MM Mobility Management

MNC Mobile Network Code

MOC Managed Object Class

MOI Managed Object Instance

MOS Mean Opinion Score

MSB Most Significant Bit

N

NACK Negative ACKnowledgement

NAS Non Access Stratum

NBAP Node B Application Part

NDI New Data Indicator

NDS Non-Delay Sensitive

Node B Logical node responsible for radio

Tx/Rx to/from UE

NRZ Non Return to Zero

O

OAM Operation Administration and

Maintenance

OVSF Orthogonal Variable Spreading

Factor

P

PA Power Amplifier

PCCH Paging Control CHannel

P-CCPCH Primary-Common Control Physical

CHannel

PCH Paging CHannel

PCM Pulse Code Modulation

PCPCH Physical Common Control CHannel

PDP Packet Data Protocol

PDU Protocol Data Unit

PI Paging Indicator

PI Priority Indicator

PICH Paging Indicator CHannel

PIR Partial Incremental Redundancy

PLMN Public Land Mobile Network

PMM Packet Mobility Management

PN Pseudo Noise

PQ Priority Queue

PRACH Physical Random Access CHannel

PS Packet Switch

P-SCH Primary-Synchronization CHannel

PSK Phase Shift Keying

Q

QId Queue Identity

QoS Quality of Service

QPSK Quadrature Phase Shift Keying

R

R4 Release 4

R5 Release 5

RA Routing Area

RAB Radio Access Bearer

RAC Routing Area Code

RACH Random Access CHannel

RAN Radio Access Network

RANAP Radio Access Network Application

Part

RB Radio Bearer

RF Radio Frequency

RL Radio Link

RLC Radio Link Control

RM Rate Matching

RNC Radio Network Controller

RNS Radio network subsystem

Page 521: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Glossary � Page 5

All rights reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Glossary Glossary � 5

Abbreviations and Acronyms [cont.]

� Switch to notes view!RNSAP Radio Network Subsystem Application

Part

RNTI Radio Network Temporary Identity

RRC Radio Resource Control

RRM Radio Resource Management

RTT Radio Transmission Technology

RV Redundancy Version

RX Receiver / Reception

S

SA Service Area

SAP Service Access Point

SAW Stop And Wait

S-CCPCH Secondary-Common Control

Physical CHannel

SCH Synchronization CHannel

SCR Sustainable Cell Rate

SDU Service Data Unit

SF Spreading Factor

SFN System Frame Number

SHO Soft HandOver

SIM Subscriber Identity Module

SIR Signal to Interference Ratio

SM Session Management

SNR Signal to Noise Ratio

SPI Scheduling Priority Indicator (CmCH-

PI)

SRLR Synchronous Radio Link

Reconfiguration

S-RNC Serving-Radio Network Controller

S-SCH Secondary-Synchronization CHannel

STTD Space Time Transmit Diversity

T

TAF That's All Folks!

TB Transport Block

TBS Transport Block Size

TCP Transmission Control Protocol

TDD Time Division Duplex

TDM Time Division Multiplexing

TDMA Time Division Multiple Access

TF Transport Format

TFC Transport Format Combination

TFCI Transport Format Combination

Indicator

TFI Transport Format Indicator

TFO Tandem Free Operation

TFRC Transport Format and Resource

Combination

TFRI Transport Format and Resource

Indicator

TFS Transport Format Set

TPC Transmit Power Control

TrCH Transport CHannel

TrFO Transcoder Free Operation

TS Time Slot

TTI Transmission Time Interval

TX Transmitter / Transmission

U

UARFCN UMTS Absolute Radio Frequency

Channel Number

UDP User Datagram Protocol

UE User Equipment

UM Unacknowledged Mode

UMTS Universal Mobile Telecommunication

System

UP User Plane

URA UTRAN Registration Area

U-RNTI UTRAN-Radio Network Temporary

Identity

UTRAN Universal Terrestrial Radio Access

Network

Uu the radio interface between UTRAN

and UE

V

VCC Virtual Channel Connection

VoIP Voice over IP

W

W-CDMA Wideband-CDMA

Page 522: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Glossary � Page 6

All rights reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Glossary Glossary � 6

Abbreviations and Acronyms [cont.]

� Switch to notes view!

Page 523: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf

Glossary � Page 7

All rights reserved © 2007, Alcatel-Lucent

3FL12921AAAAWBZZA Edition 1

All rights reserved © 2007, Alcatel-Lucent

Alcatel-Lucent W-CDMA

UA5.0 Introduction to UTRAN QoS and Traffic Load

Monitoring

Glossary Glossary � 7

End of ModuleGlossary

Page 524: ALcatel _Lucent UTRAN 3G QoS Analysis and Monitoring.pdf