Anda di halaman 1dari 422

Passing on and copying of this document, use and communication of its

contents not permitted without written authorization from Alcatel-Lucent

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TERMS OF USE AND LEGAL NOTICE
Alcatel-Lucent provides this training course to you subject to these Terms of Use and Legal Notice. Your use of this training
course and/or this site constitutes your acceptance of and agreement to these Terms of Use and Legal Notice. These Terms
of Use and Legal Notice, as well as the contents of this training course, may be updated or amended by Alcatel-Lucent from
time to time without prior notice to you. Your use of the Alcatel-Lucent training materials after such update or amendment
constitutes your acceptance of and agreement to said updated or amended Terms of Use and Legal Notice.

SAFETY WARNING
Alcatel-Lucent training materials can be for products or refer to products that have both lethal and dangerous voltages
present. Always observe all safety precautions and do not work on the equipment alone. The user is strongly advised not to
wear conductive jewelry while working on the products. Equipment referred to or used during this course may be
electrostatic sensitive. Please observe correct anti-static precautions.

PERMISSION TO USE CONTENT


The information, communications, scripts, photos, text, video, graphics, music, sounds, images and other materials provided
in this training course (collectively the "Content"), is intended for the lawful use of employees of Alcatel-Lucent and other
authorized participants in this Alcatel-Lucent training course. You are hereby granted a non-exclusive, non-transferable
permission to access and use the Content solely for your personal training and non-commercial use. This permission may be
terminated by Alcatel-Lucent at any time for any reason or no reason, with or without notice. You must immediately cease
use of the Content upon such termination.

COPYRIGHTS AND TRADEMARKS


The unauthorized copying, displaying or other use of any Content from this training course is a violation of the law and
Alcatel-Lucent’s corporate policies. The Content is protected in France, the U.S. and other countries by a variety of laws,
including but not limited to, copyright laws and treaty provisions, trademark laws, patent laws and other proprietary rights
laws (collectively, "IP Rights"). In addition to Alcatel-Lucent’s IP Rights in the Content, in part and in whole, Alcatel-Lucent,
and any of the third parties who have licensed and/or contributed to the Content, owns a copyright in the formatting and
presentation of the Content.
Alcatel-Lucent does not grant you any permission to use the Content other than the permission expressly stated in these
Terms of Use and Legal Notice. All other use of Content from this training course, including, but not limited to, modification,
publication, transmission, participation in the transfer or sale of, copying, reproduction, republishing, creation of derivative
works from, distribution, performance, display, incorporation into another training course or presentation, or in any other way
exploiting any of the Content, in whole or in part, for uses other than those expressly permitted herein is strictly prohibited
and shall not be made without Alcatel-Lucent’s prior written consent. All characters appearing in this training course are
fictitious. Any resemblance to real persons, living or dead, is purely coincidental.
There may be a number of proprietary logos, marks, trademarks, slogans and product designations found in the
Content. Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logos are trademarks of Alcatel-Lucent. All other trademarks
are the property of their respective owners. Alcatel-Lucent does not grant you a license to use any of the foregoing logos,
marks, trademarks, slogans and product designations in any fashion. Granting of the right to access and use the Content for
training purposes does not confer upon you any license under any of Alcatel-Lucent’s or any third party's IP Rights.

DISCLAIMER
ALCATEL-LUCENT DISCLAIMS ALL WARRANTIES REGARDING THE TRAINING COURSES OR THE CONTENT, EXPRESS OR
IMPLIED, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. THE ALCATEL-LUCENT WILL NOT BE RESPONSIBLE OR LIABLE FOR ANY INJURY, LOSS, CLAIM,
DAMAGE, OR ANY SPECIAL, EXEMPLARY, PUNITIVE, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES OF ANY KIND
(INCLUDING WITHOUT LIMITATION LOSS PROFITS OR LOSS SAVINGS), WHETHER BASED IN CONTRACT, TORT, STRICT
LIABILITY OR OTHERWISE, THAT ARISES OUT OF OR IS IN ANY WAY CONNECTED WITH (A) ANY USE OR MISUSE OF THE
CONTENT OR THE TRAINING COURSES BY YOU, OR (B) ANY FAILURE OR DELAY BY ALCATEL-LUCENT, ITS OFFICERS,
DIRECTORS, AGENTS OR EMPLOYEES IN CONNECTION WITH THE CONTENT OR THE TRAINING COURSES (INCLUDING,
WITHOUT LIMITATION, THE USE OF OR INABILITY TO USE ANY COMPONENT OF THE CONTENT OR TRAINING BY
YOU). SOME JURISDICTIONS LIMIT OR PROHIBIT SUCH EXCLUSION OF WARRANTIES OR LIMITATION OF LIABILITIES
AND SO THE FOREGOING EXCLUSION OF WARRANTIES OR LIMITATION OF LIABILITY MAY NOT APPLY TO YOU.

GOVERNING LAW
These Terms of Use and Legal Notice are governed by the laws of France. The operation and use of the training course is
governed by the laws of the country that governs your employment contract, if applicable. If any provision of these Terms of
Use and Legal Notice, or the application thereto to a person or circumstance, is held invalid or unenforceable by law, statute
or a court of competent jurisdiction, for any reason, then such provision shall be modified and/or superseded by a provision
that reflects the intent of the original provision as closely as possible. All other provisions of these Terms of Use and Legal
Notice shall remain in full force and effect. You may not assign these Terms of Use or any permission granted hereunder
without Alcatel-Lucent’s prior written consent. Nothing herein shall be deemed an employment agreement or an offer of
employment or an alteration in any way of a user’s terms of employment with or within Alcatel-Lucent.
Copyright © 2011 Alcatel-Lucent. All Rights Reserved

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


Welcome to UTRAN
UA08 9300 W-CDMA R99 QoS Analysis and Traffic Load Monitoring

1. R99 QoS Analysis


1. Radio Network Performance Overview
2. Monitor the Radio Network Performance
3. Monitoring and Troubleshooting Methods
4. Network Accessibility Monitoring
5. Retainability Monitoring
6. Mobility Monitoring
7. Network Quality Monitoring
2. Capacity and Traffic Load Monitoring
1. Capacity Monitoring
2. Traffic Monitoring
3. Abbreviations and Acronyms
1. Abbreviations and Acronyms

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


UTRAN
UA08 9300 W-CDMA R99 QoS Analysis and Traffic Load Monitoring

Upon completion of this course, you should be able to:

identify why, when, and how to do performance management


define counters, metrics, explain how to use metrics and describe the six metrics families
illustrate the call flows associated with each metric family, identify the counters and locate them in
the call flow procedure
analyze UTRAN QoS problems with KPIs: detect problems, identify them using metrics, propose
actions to solve them
monitor traffic load with KPIs

Your feedback is appreciated!


Please feel free to Email your comments to:

training.feedback@alcatel-lucent.com

Please include the following training reference in your email:


TMO18268_V2.0-SG Edition 1

Thank you!

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.1 Edition 1
Section 1 · Module 1 · Page 1
This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.1 Edition 1
Section 1 · Module 1 · Page 2
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.1 Edition 1
Section 1 · Module 1 · Page 3
This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.1 Edition 1
Section 1 · Module 1 · Page 4
Page

1 Define QoS inside the network 7


1.1 What is end user QoS over UMTS? 8
1.2 Mapping teleservices to QoS 10
1.3 UMTS traffic classes 11
1.4 Standard QoS bearer 12
1.5 What is QoS UTRAN in UMTS? 13

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.1 Edition 1
Section 1 · Module 1 · Page 5
This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.1 Edition 1
Section 1 · Module 1 · Page 6
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.1 Edition 1
Section 1 · Module 1 · Page 7
Expectations of end users regarding simultaneous access to different services, data transmission speed
(fast file transfer or fast display of web pages) led 3GPP to define criteria and parameters for managing
UMTS resources in an effective way while providing the QoS the end user expects.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.1 Edition 1
Section 1 · Module 1 · Page 8
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 minimizing 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 optimize the load

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.1 Edition 1
Section 1 · Module 1 · Page 9
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.1 Edition 1
Section 1 · Module 1 · Page 10
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 in the table with the following:
Stringent
Constrained
Less constrained
Not constrained

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.1 Edition 1
Section 1 · Module 1 · Page 11
The UMTS PLMN is responsible for providing transport of teleservice data across the UMTS network
according to the QoS required for each of the teleservices it is supporting. This means that both UTRAN and
UMTS Core Network domains must implement specific mechanisms to provide the required QoS. From a
UTRAN perspective, the RAB is the means by which data is transferred between UE and CN at the required
QoS. A RAB will be mapped on Radio Bearers and its Logical, Transport and Physical Channels which will be
defined with the parameters allowing to provide the required QoS of the RAB.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.1 Edition 1
Section 1 · Module 1 · Page 12
UTRAN QoS consists of a set of measurements providing the UMTS PLMN Operator with accurate
knowledge of the performance of the UTRAN sub-system. Of course the quality of service experienced by
the end user, also called Quality of Experience (QoE), is not only the consequence of the UTRAN QoS.
Indeed, the QoE is impacted by the UMTS Core Network QoS as well as the QoS of the PDN, the application
servers and user equipments in use for a specific teleservice.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.1 Edition 1
Section 1 · Module 1 · Page 13
To ensure simultaneous applications for a given user, the network should:
Allow multi RAB per user
Provide 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 (for HSxPA, see 9300 WCDMA UA07 HSxPA QoS Analysis
and Traffic Load Monitoring)
The usage of DiffServ within the RNC over IuPS interface to ensure higher priority for high bit rate
services
Many UTRAN internal mechanisms are in place to provide priorities of data delivery to specific
users and/or applications in order to increase the data bit rate when needed.
More service interactivity is achieved by:
Appropriate iRM and AO state transitions
As well as the usage of DiffServ within the RNC to provide higher priority for interactive services

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.1 Edition 1
Section 1 · Module 1 · Page 14
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.1 Edition 1
Section 1 · Module 1 · Page 15
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 1
This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 2
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.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 3
This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 4
Page

1 QoS counters definition 7


1.1 Introduction 8
1.2 Counters: definition 9
1.3 Collect performance data with ALU solution 10
1.4 Counter file storage 12
1.5 NPO introduction to UTRAN monitoring 13
2 Counter properties and analysis 14
2.1 Counter groups and families 15
2.1.1 RNC Counter families 16
2.1.2 Node B and MSS counter families 17
2.2 Cumulative counter type 18
2.2.1 Example 19
2.3 Value counter type 20
2.3.1 Example 21
2.4 Load counter type 22
2.4.1 Example 23
2.5 RNC C-Node counter object instances 25
2.6 RNC and “any cell” object instances for C-Node counters 26
2.6.1 Example: any cell counter of RNC acting as a DRNC 27
2.7 Reference cell object instance for C-Node counters 28
2.7.1 Example – Reference cell counter of RNC1 29
2.8 Neighboring RNC object instance for C-Node counters 30
2.8.1 Example – Neighboring RNC counter of RNC1 31
2.9 Remote Cell object instance for C-Node counters 32
2.9.1 Example – Remote Cell counter of RNC1 33
2.10 NPO aggregation per couple (Remote Cell, RNC) 34
2.11 NPO aggregation per cell 35
2.12 NPO aggregation per RNC 36
2.13 BTS counter object instances 37
2.14 MSS counter families and object instances 38
2.15 Counter Screenings 39
3 Metrics properties and analysis 40
3.1 Metrics definitions 41
3.2 Metrics generic formulas 42
4 Generating reports and analysis 43
4.1 RNC counter volume control 44
4.2 Indicator aggregation 45
4.3 Report definition 46
4.3.1 Generate a report on NPO 47
4.3.2 Key performance indicators 48
4.3.3 Network key performance indicators 49
4.3.4 Counter based KPIs 50
4.3.5 Methodological precautions 51
4.3.6 KPI value 52
4.3.7 Network element aggregation 53
4.3.8 With other indicators 54
4.3.9 With alarms 55
4.3.10 With parameters modification 56
5 Real time counters 57
5.1 Overview 58
5.2 Real time PM versus legacy PM 59
5.3 Real time performance monitoring application 60
5.4 Real time metrics 61
6 Call trace solution overview 62
6.1 Introduction 63

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 5
Page

6.2 Traces and tools 64


6.3 Call trace session types: trace a UE 66
6.4 Call trace session types: trace traffic in a group of cells 67
6.5 Call trace session types: trace common NBAP, mobility 68
6.6 Call trace session types: trace Iu interfaces 69
6.7 Configuring a call trace session 70
6.8 Real time call trace overview 72
6.9 Real time call trace preparation 73
6.10 Real time call trace monitoring 74
7 Performance monitoring tools 75
7.1 OAM performance management portfolio 76
7.2 WTA 78
7.3 WCT 83

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 6
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 7
All these factors contribute to NW Management OPEX Reduction.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 8
The terms “counter “and “measurement” are often equally used in the documentation to identify 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 and MSS are uploaded every 15 minutes.
BTS counters are uploaded every 15 minutes and/ or hours.
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 you 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, it is
necessary to check the influence of the traffic.
Weekly period
Monthly period

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 9
Observation counter binary files are transferred every 15- or 60-minute period to the WMS server where
they are converted into XML files and stored in a temporary directory.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 10
The NPO server permanently looks if some new observation counter files have been transferred into the
WMS server. It then transfers these files and stores the new counter values into the NPO Oracle® database.
It also computes the defined Stored Indicators and stores their values in the same database.
Any NPO user can display Stored and Calculated Indicators values from an NPO Client or a Citrix Client
accessing the NPO server through an intermediate HMI Server of Clients acting as a Citrix server too.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 11
The data is organized in the following Performance Server directories:
BTS Counters - /opt/nortel/data/utran/observation/stats/<YYYYMMDD>/NodeB-<neName>
RNC C-Node Counters - /opt/nortel/data/observation/stats/<YYYYMMDD>/RNCCN-<neName>
Passport Platform (Inteface Node) Counters
RNC I-Node - /opt/nortel/data/observation/stats/<YYYYMMDD>/INODE-<neName>

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 12
NPO will NOT support co-hosting of 2 technologies on the same NPO instance.
NPO will support co-hosting only via virtualization.
There is a unique product code for NPO: 9959.

Platform evolution:
NPO is now on HP®.
New multi-standard strategy based on virtualization.

WCT is the new option in NPO allowing statistical processing of WCDMA CFT and CTN call traces:
Continuously scan and load the WMS output.
It relies on the NPO platform:
Same graphical interface (analysis desktop)
Same export capabilities
Same administration

The WCT module is optional: its activation is not mandatory.

Available for deployment on UA07.1 & UA08.1 (NPO 4.1 R7 onward)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 13
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 14
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 15
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 16
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 17
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 18
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 19
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 20
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 21
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 22
Only VS.RadioLinkEstablishedPerCell .Avg, .Min, .Max are meaningful but .Cum and .Nbevt are also
computed for Aggregation of metrics.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 23
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 24
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 25
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 26
The call is handled by the serving RNC. When a UE attempts a voice call for example, some counters are
incremented on the FDDCell and the RNC layer. This was already available in UA06.0.

You should notice here that these new counters are pegged on the reception / transmission of the RNSAP
messages on the DRIFT RNC.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 27
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 28
Reference Cell Counters

The Reference Cell counter is incremented only on the primary cell if this primary cell is under the
Serving RNC.

The counter is incremented only once even if the UE has more than one cell in its active set, unlike the
Fddcell counter that will be incremented in all the cells in the active set.

In the example above, #2680 is a reference cell counter. When the event occurred, only the counter #2680
of the left cell in the serving RNC was incremented.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 29
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 30
Neighboring RNC counters

The Neighboring RNC counter is incremented in the serving RNC only if the primary cell is under the
Drift RNC.

The counter is incremented only once even if the UE has more than one cell in its active set, unlike the
Fddcell counter that will be incremented in all the cells in the active set.

In the example above, #2680 is a reference cell counter and #2681 is a Neighboring RNC counter. When
the event occurred, because the primary cell was under the Drift RNC, only the counter #2681 under the
serving RNC was incremented.

The same counter #2681 will be incremented regardless of the cell of the DRNC.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 31
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 32
This feature aims at having some of the Reference FddCell counters pegged when triggering events occur
on a RNC different from the controlling RNC.
In UA06, counters pegged at Reference FddCell level, always excluded the events that occured when a
given cell was the primary cell of the connection but the S-RNC was not the Controlling RNC (during SHO
via Iur).
So since UA07.1, this feature introduces a new counter location that is pegged by the SRNC. The new
location is referred to as the Remote UTRAN Cell (or RemoteUtranCell) location. This new location is the
equivalent of the Reference Cell location but for the cell that is controlled by the DRNC.

FEATURE VALUE
Increased accuracy of the cell level metrics during SHO via Iur.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 33
There can be three types of possible indicator analysis using the new Drnc Cell Counters.
Analysis per couple (RNC ⇔ remoteUtranCell)
The objective is to be able to monitor events that occurred on cell(s) located on another RNC for calls
served by the current RNC.

Example: events that occurred on cell 21 when calls were served by RNC 1.

The aggregation in this case can be done on all REMOTECELL3G cells of a given RNC. The aggregated value
is available on the RNC .The new aggregation path is equal to [ REMOTECELL3G , RNC].

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 34
Analysis per cell
The objective is to be able to monitor events that occurred on a cell both for calls served by its parent RNC
(in this case, the cell is a local cell) and for calls served by neighboring RNCs.

Example: events that occurred on cell 21 when calls were served by neighboring RNCs 1 and 3 and when
calls were served by RNC 2.
Indicator(Cell 21) = ΣC1(any RNC, remoteUtranCell 21) + ΣC2(RNC 2, Cell 21)

The new aggregation path is equal to [ REMOTECELL3G , REMOTECELL3G_ECELL(target), CELL3G, RNC].

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 35
Analysis per RNC (all the cells of the RNC)
The objective is to be able to monitor events that occurred on cells of an RNC for calls served by this RNC
or for calls served by neighboring RNCs .

Example: events that occurred on cells of RNC 2 when calls were served by neighboring RNCs 1 and 3 and
when calls were served by RNC 2.
Indicator(RNC 2) = ΣC1(any RNC, any remoteUtranCell below RNC2) + ΣC2(RNC 2,any local Cell)

The new aggregation path is equal to [ REMOTECELL3G , REMOTECELL3G_ECELL(target), CELL3G, RNC].

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 36
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 37
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 38
Main screenings:
1. Uplink Traffic Counter Screenings
2. Downlink Traffic Counter Screenings
3. DlRbSetId,UlRbSetId,TrafficClass derived screening per granted Rab
4. Target type of call for Radio Link Reconfiguration
5. Source Type of call release mapping
6. Derived AsConf Screening for PS DlAsConfId
7. Derived AsConf Screening for CS DlAsConfId
8. Derived AsConf Screening for DlAsConfId Avg Nbr Estab
9. Derived AsConf Screening for UlAsConfId Avg Nbr Estab
10. Type of call for dropped last radio link
11. Target Type of call setup mapping
12. Target type of call for Radio Bearer Reconfiguration
13. Traffic Class Combined UL and DL RbSetIds (COMB UL DL RBSET).

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 39
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 40
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.
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 follows:
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)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 41
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]

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 42
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 43
From UA06, the RNC starts to apply limits on the maximum number of configurable C-Node counters at cell
level. The limit values are:
RNC w/ PSFP1/CP3 or DCPS/CP4 4.75 Million Cell Counters
RNC w/ DCPS/CP4 9.5 Million Cell Counters
This value corresponds to approximately 3958 PM counter screenings at cell level for an RNC configured
with the maximum supported number of cells.
Objectives of the feature:
Maintain the RNC counter volume under controlled limits
Allow the operator to customize the counter lists:
Non required counters can be turned OFF
Allow the introduction of new RNC counters in future releases
To control the volume of active counters, the user can edit / modify the RNC counter list.
Counter List Management only applies for RNC C-Node families of counters.
The Counter List modification can be applied “On-line” without impact on service.
The modification of the list is assumed by the RNC for the third collection period after the change is
applied .
Maximum Volume of Counters Supported By the RNC
The RNC applies automatic defense mechanisms when the maximum supported volume of cell
counters is exceeded (only for C-Node families).
Note: In UA06, there were not enough RNC C-Node defined counters to set the limits to be exceeded.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 44
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 applied 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)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 45
A report consists of a set of metrics going from a high level view to a low level one (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 recommended 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) NEs according 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.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 46
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 47
Measure the performance of the complete network:
Analyzed according to 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.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 48
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 49
Will be developed in the next chapters

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 50
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 51
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 52
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 53
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 54
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 55
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 56
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 57
This feature is used to enhance the operational effectiveness of the Access solution. It is used in
conjunction with GPO (permanent) counters to permit the troubleshooting and real time monitoring of Part
of the Network.
The main use cases that can be addressed by this feature are:
Follow system behavior over a sub-set of cells during special events (max 120 cells/RNC).
Verify performance after a parameter change or a new site introduction.
Quickly verify RNC performance after a software/release upgrade.
This cannot be achieved through existing “permanent observation” counters.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 58
Granularity Period :
The readiness of the counter files on the Network Element (RNC or Node B). For GPOs, it is 15 minutes (for
the RNC & a part of the Node B) or 60 minutes for some Node B counters.
For the RTO, it is around 1-5 minutes. The RNC closes the counter files every 5 minutes.

End-to-End Latency :
The counters are then transferred to the main server and processed to generate an XML file. For GPO, the
FTP to the main server and the XML conversion needs 15 minutes then the FTP to NPO plus the processing
(Normalization, etc.) need 15 more minutes. This leads us to 30 minutes.
For the RTO, it takes a few minutes.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 59
Real Time Performance Monitoring Framework
Ability for user to visualize PM metrics variation in real time
User Selection:
Pre-defined list of metrics:
Call Attempts Total, CS & PS; Successful Call Setups Total, CS & PS
Call Setup Success Rate Total, CS & PS; Drop Calls Total, CS & PS
Drop Call Rate Total, CS & PS; Total Traffic, CS & PS (Erlang)
On max 120 cells per RNC
On some NEs
Granularity: 3 minutes
Display Latency: around 1 minute

Graphical User Interface


For configuration and activation
To display the collected results
Tabular Monitoring Dashboard
Graphical Display:
Time Graph/ Summary

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 60
The list of metrics to be monitored in real time is predefined, i.e. pre-configured by default in OAM/RTA,
and cannot be modified.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 61
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 62
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 63
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 64
There are several Call, Object and Protocol Trace possibilities:

Geographical Call Trace (CTg);


Access Invoked Call Trace (CTb);
Real Time Call Trace (RTCT);
Neighboring Call Trace (CTn);
Object Trace (OT) – Cell, IuCS, IuPS, IuR, IuBC;
Protocol Trace (PTRACE).

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 65
Possibility to run all session types simultaneously
Tracing sessions may have a very significant impact on RNC resources (CPU and occupied disk space).
Up to UA05/UA05.1, the following restrictions apply (per RNC):
CTg and CTn trace sessions are mutually exclusive.
OT-Cell and CTn trace sessions are mutually exclusive.
In UA06 ,these restrictions were dropped.

In order to limit the impact on RNC capacity and performance, a new controlling mechanism is put in place:
A weight is associated to each tracing session created on the RNC.
For the CTg session, the weight depends on the configuration of the session (i.e. functions and sub-
functions associated and tracing mode chosen).
The RNC will be able to dynamically evaluate the total tracing weight value by summing the weights of
all the active sessions.
The capacity limitations of the CTg session (number of simultaneously traced calls per TMU) will be
automatically adjusted depending on the total CT weight.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 66
Periodic RRC Measurements in CTg and CTb
With the introduction of event-triggered mode for reporting the UE RRC measurements, some RF
environment measurements (such as the Cpich Ec/N0, Cpich RSCP) are not periodically reported by the UE
in CELL_DCH to the RNC. This information is sometimes useful for Network Monitoring and Remote
Optimization purposes.
Since UA05, the user can already configure the CTb and CTg sessions to include periodic RRC quality
measurements (DL RLC BLER).

The user is allowed to configure calls being traced by CTb and CTg to include the following new RRC
periodic measurements:
Intra-Frequency (providing the “CPICH Ec/N0” and “CPICH RSCP”)
UE Internal (providing “UE Transmitted Power” and “UE Rx-Tx Time Difference”).

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 67
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 68
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 69
Full Mobile Tracing is a UA08.1 feature.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 70
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 71
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 72
To start a real time call trace, you go to the NSP GUI and select Performance - Radio Access - Call
Trace Wizard for UMTS.
This is exactly the same procedure as the classical Call Trace session creation.

The Real Time Call Trace is performed only for Access session, i.e. CTb traces.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 73
To monitor the RT call Trace, a new function is added into NSP in OAM7.0. Select Performance - Radio
Access - Real Time Call Trace to monitor the call traces.

Only 2 CTb sessions can be monitored.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 74
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 75
System: activation, data collection, data mediation
NPO: counter based, performance reporting, added value modules

WTA 7.0 = Support of UA8.1: WTA supports the analysis of call traces:
Support of CTN traces
Support of CFT traces
Support of OT traces (OT-Cell ; OT-IuCS, OT-IuPS, OT-IUR, OT- IuBC)
Support of CTg traces
Support of CTb traces
Support of CTa traces

WCT is a new option in NPO allowing statistical processing of WCDMA CFT and CTN call traces
Continuously scan and load the WMS output

It relies on the NPO platform:


Same graphical interface (analysis desktop)
Same export capabilities
Same administration
Administrative evolution: there is a unique product code for NPO: 9959
9159 NPO, 9359 NPO no more used (except for already installed systems)

WQA, RFO: no longer supported

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 76
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 77
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 78
In the message explorer, messages from selected calls are displayed with some additional information.
Further, the IEs inside each message can be checked.
The filters are quite useful. You can use them for timeframe, protocol, network element, message
name, additional information, etc.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 79
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 80
For the periodic NBAP measurements requested in the WMS GUI, the Node B and RNC will initially exchange
Dedicated measurement init messages and then the RNC will periodically record the Dedicated
measurement reports sent by the Node B.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 81
For each UE measurement requested in the WMS, the RNC will generate a specific set of Measurement
Control messages to initiate the measurements and then will periodically record the Measurement
Report messages sent by the UE.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 82
WCT stands for WCDMA Call Traces. It replaces WQA.
WCT is an optional module of NPO that:
1. Collects and processes Call Trace data from WMS servers.
2. Generates PM counters related to the collected Call Trace data.
3. Provides a set of reports and views for analysis & troubleshooting .
Two types of traces are available:
1. CTn: for neighboring optimization
2. CFT: for call drop analysis
Call Trace processing works as follows:
1. CT session creation from WMS
2. CT activation on RNC
3. CT data collection from RNC to WMS
4. Data gathering from NPO
5. PM counters generation & database load on NPO
6. Use of CT data in the NPO Analysis Desktop (views, reports, etc.)

WCT consists of:


1. Two software components
1. One Controller
2. One or several LOLA (Loader & Aggregator)
2. A set of LOLA counter dictionaries
3. A set of NPO counter and indicator dictionaries
The controller pilots LOLA module(s) which is(are) in charge of collecting and processing the traces, and
generating the counters for NPO.
LOLA(s) is(are) configured thanks to dictionaries that contain the definitions of the counters to be
computed.
A set of counters and indicators dictionaries is also delivered in order to configure NPO with WCT counters.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 83
WCT decodes the CTg traces, reconstructs the calls and generates CTg Localization records that are
displayed in the cartography module.
Based on the PCMD cartography module, the WCT cartography module displays the CTg Localization
records and the topology of the network.
The study (analysis) editor allows the users to create their own studies but the WCT cartography module is
delivered with a set of predefined analyses dedicated to:
Drops coverage
Good Ec/No coverage
Bad Ec/No coverage
Good RSCP coverage
Bad RSCP coverage
Over shooters

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 84
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 85
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 86
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.2 Edition 1
Section 1 · Module 2 · Page 87
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 1
This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 2
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 3
This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 4
Page

1 Monitoring and troubleshooting process 7


1.1 Monitoring & troubleshooting methods 8
1.2 Criteria definition 9
1.3 Observation 10
1.4 Analysis 11
1.5 Correction 12
1.6 Validation 13
2 Define performance reports 14
2.1 High level: RNC and CELL dashboards 15
2.2 Low level: detailed monitoring and troubleshooting 16
2.3 Recommendations 18

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 5
This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 6
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 7
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 operation completion or usage of the resources.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 8
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 9
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 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 accumulated 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 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, etc.) and network stability status can help find and solve any bad
performances of the network.
Figures also have to be captured at the times the network is the most demanded: data for busy hour are
needed every day.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 10
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 has to be confirmed further investigation is necessary:
System check
Verify operation and maintenance reporting
Iub, Iu and Iur interface traces, and mobile traces.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 11
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 to help 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, etc.
Modifying the network configuration may be necessary.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 12
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.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 13
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 14
The RNC and CELL dashboard reports contain global views.
They can be used for a regular monitoring of the main KPIs to have a high level overview of the network
performance. All views of these two Global Reports called Dashboards belong to the same family (named
“DASHBOARD”).
Views are organized in several sub-family levels, sub-families at level1 corresponding to the main
monitoring domains such as accessibility or retainability. The sub-family2 level is used to separate CELL
level views and RNC level views. All dashboard views are used in Dashboard reports but some of them can
be used in detailed monitoring reports.
The indicators provided in these Dashboards are related to:
RRC connections setup
IU SCCP connections setup
Radio Access Bearers establishment
Call Drops
Mobility efficiency
Congestion detection
Quality
Traffic
The RNC dashboard report reflects the overall actual quality of network, and it leads to deeper
investigations at CELL level using additional indicators.
This deeper analysis will use both Detailed Monitoring reports and Troubleshooting reports.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 15
The Detailed Monitoring reports contain a lot of detailed views of indicators commonly used for detailed
performance analysis per monitoring domain like for a specific feature monitoring. These reports are often
used during UTRAN Release upgrades.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 16
The Detailed Monitoring reprots contain a lot of detailed views of indicators commonly used for detailed
performance analysis per monitoring domain like for a specific feature monitoring. These reports are often
used during UTRAN Release upgrades.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 17
The Sampling Indicator defined for call_drop_rate_CS indicator is the Number of CS calls established which
is computed from the counting of the number of Iu Release Complete messages sent by the RNC to the CN-
CS.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 18
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.3 Edition 1
Section 1 · Module 3 · Page 19
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 1
This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 2
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 3
This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 4
Page

1 Accessibility analysis 7
1.1 Accessibility call flow 8
1.2 Accessibility issue causes 9
2 RRC connection phase 10
2.1 RRC connection 11
2.2 RRC connection success: call flow 12
2.3 RRC connection success: counters 13
2.4 RRC connection preparation failure 14
2.5 RRC connection execution failure 15
2.6 RRC connection: counter tree 16
2.7 RRC connection success rate 17
2.8 RRC connection attempt during cell reselection 18
2.9 RRC connection success rate excluding UE repetitions 19
3 RRC troubleshooting 20
3.1 RRC accessibility analysis 21
3.2 RF conditions analysis 24
3.2.1 UE distance 26
3.2.2 UL radio load 27
3.2.3 UL cell load 28
3.3 RRM capacity analysis 29
3.4 Case analysis 30
3.4.1 Burst of RRC failures in an RNC 31
3.4.1.1 Burst of RRC failures at busy hours 32
3.4.2 Burst of RRC failures in a few cells 33
3.5 RRC burst of failures 34
4 Radio link management 35
4.1 Reminder 36
4.2 VS.radio link setup unsuccess 37
4.3 Radio link reconfiguration prepare 38
5 Iu SCCP troubleshooting analysis 40
5.1 Iu SCCP connection procedure 41
5.2 SCCP connection: success flow 43
5.3 SCCP connection: failure flow 44
5.4 SCCP connection: counter tree 45
5.5 Iu SCCP analysis (success rates initiated by the RNC) 46
5.6 Iu SCCP analysis method 47
5.7 Case study 48
5.7.1 Compare CS and PS Iu SCCP efficiency 49
5.7.2 Compare RNCs 50
6 Security mode troubleshooting analysis 51
6.1 Security mode success: flow 52
6.2 Security mode failure: RNC 53
6.3 Security mode failure: UE 54
6.4 Security mode command success ratio 55
6.5 Ciphering analysis 56
7 RAB establishment and troubleshooting analysis 57
7.1 RAB assignment success 58
7.2 VS.radio bearer establishment unsuccess 61
7.3 RAB assignment preparation failure 62
7.4 RAB assignment execution failure 63
7.5 RAB assignment: RNC counter 64
7.6 RB establishment: cell counter 65
7.7 RAB assignment success rate (RNC level) 66
7.8 RB to be setup success rate (CELL level) 67
7.9 RAB analysis: failure analysis 68

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 5
Page

8 Call setup success rate troubleshooting analysis 69


8.1 Exercise 70
8.2 Call setup success rate 71
8.3 Accessibility troubleshooting chart 72
8.4 Case study 73
8.5 Other formulas for CSSR CS 74

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 6
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 7
The main phases of call establishment which are taken into account in the network accessibility
measurement are:
the RRC connection setup,
the Iu SCCP connection establishment,
the RAB establishment procedures.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 8
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, etc.) and the
network elements for each report.
The output of this step comes with a set of deliverable reports to use for monitoring activities.
Hereafter are examples 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.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 9
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 10
The 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.
The RRC Connection is one of the functions of the 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 layer 2 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.
At the first NAS message from UE which needs to be sent to the CN, the UTRAN will set up an SCCP
connection with the CN in order to forward this NAS message either to the MSC or the SGSN according to
the service to be set up.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 11
This scenario is applied in case of RRC connection establishment in cell_DCH state (for CS call setup for
instance).

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 12
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 idle
mode ; 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 repetitions 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.
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 13
RRC.FailConnEstab #404: This measurement provides the number of RRC connection establishment
failures screened by establishment failure cause.
Screening:
Sub-Counter #1: unavailable dl code resources
Sub-Counter #2: unavailable dl power resources
Sub-Counter #3: RSSI
Sub-Counter #4: Cell Fach Unspecified CAC (excluding lack of context)
Sub-Counter #5: Overload
Sub-Counter #6: 3G to 2G Redirection for Emergency Calls
Sub-Counter #7: RRC context CAC, pegged when CAC fails (excluding FACH UEs)
Sub-Counter #8: Unavailable RRC context resource, pegged when the number of RRC contexts is
exhausted
Sub-Counter #9: Unavailable FACH context resource, pegged when the number of FACH contexts in
RNC_CALL is exhausted.
Sub-Counter #10: No answer from the Node B
Sub-Counter #11: Lack of C-RNTI
Sub-Counter #12: UE Ec/No lower than qQualityMiN
Sub-Counter #13: Repeated 'RRC Connection Request' received in a different cell from the preceding
attempt (during the N300*T300 window). To be pegged in the cell where the 'RRC Connection
Request' prior to reselection was received.
Sub-Counter #14: In case the Manual Overload Control at Node B granularity feature is activated, if
the number of RLSs in the Node B is exceeded, the thresholdEventA,RNC starts to reject 'RRC
Connection Request'until the number of RLSs in the Node B is less than thresholdEventB
Sub-Counter #15: SRNC receives a "Radio Link Setup Failure" message causing RRC Connection Reject
to be sent
Sub-Counter #16: 3G to 2G Redirection based on cell load
Notes:
Screening #5 corresponds to an RNC OVERLOAD problem
Screening #8 corresponds to a CAC failure due to RRC context resource shortage in the RNC
Screening #9 corresponds to the CAC failure on FACH when the maximum number of users on FACH
has been reached.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 14
RRC.FailConnEstab #404: This measurement provides the number of RRC connection establishment
failures screened by establishment failure cause.

Timeout screeners:

Sub-counter#0: TimeoutRepeat
Incremented when the RNC does not receive an RRC Connection Setup Complete before T352
expires (timeout).
Incremented when the RNC receives a new RRC Connection Request from the same UE within
N300xT300 in the same cell as the previous request.

Sub-counter #13: Reselect


Incremented when the RNC receives a new RRC Connection Request from the same UE within
N300xT300 in a different cell than the previous request (incremented on the cell where the
original RRC Connection request was received – before cell re-selection)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 15
In the UA07 release, RRC.FailConnEstab.Unspecified (#404.3) is replaced by a dedicated counter
RRC.FailConnEstab.Unspecified.Sum - #436.

In UA08.1, a new formula for KPI RRCConnectionFailures_RRC018_CR and


RRCConnectionReject_RRC029_CR is defined, where the sum of the RRC failures due to unspecified and
due to congestion is used, as such:
RRCConnectionFailures_RRC018_CR =UC431+UC436+UC404_0+UC404_14
& RRCConnectionReject_RRC029_CR= UC431+UC436
Where U436 counts all the RRC failures due to unspecified causes
U431 counts all the RRC failures due to congestion.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 16
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
,etc.)
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)

RRC.FailConnEstab - #404
Failed RRC Connection Establishments by Cause
Sub-Counter #6: 3G to 2G Redirection for Emergency Calls
Sub-Counter #16: 3G to 2G Redirection based on cell load

VS.RRC.ConnectionReAttempt - #439
With counter 0404, it gives a view of the failure and success rate of the 3G/2G redirection at RRC establishment request. If no GSM
cell verifies the selection criteria, the UE will re-attempt a new RACH after the "wait time" timer (UE timer) elapses. On this new
attempt, the RNC does not redirect the call to the 2G and attempts to establish the call on the FDD cell if the Rach comes before the
timer rrcCnxRepeatTime elapses.
The counter is incremented when the RNC does not redirect this new attempt. Repeated "RRC Connection Request" in the context
T300 and N300 from the same UE (same UE Id and format) on the same RNC shall be excluded. Note: rrcCnxRepeatTime is renamed
from emergencyCallRepeatTime
Sub-Counter #0: Emergency call redirection feature
Sub-Counter #1: Redirection based on cell load feature

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 17
Featured counters:
VS.RRC.AttConnEstab.LastperProc.Sum (#428)
VS.RRC.AttConnEstab.LastperProc (#433)

Feature value:
Total number of RRC connection establishment attempts. Repeated attempts from the same UE on the
same or a different cell - due to cell reselection - are excluded.
Align Observed Call Setup Success Rate KPIs with User Perception.

Triggering event
Incremented on the last 'RRC Connection Request' message for the same RRC Connection
Establishment procedure being received from the UE on the RNC.
The last 'RRC Connection Request' message is identified:
on emission of 'RRC Connection Complete' (successful case), or
at T300xN300 window expiry (unsuccessful case), or
in case of repetitions: including the same UE Id and same establishment cause as the previously
received 'RRC Connection Request' messages within the T300xN300 window on the same RNC.
The establishment cause for repeated attempts will remain unchanged.
Repeated RRC Connection Requests received on different cells - due to cell reselection - will be
considered.
Pegged against the cell, where RRC connection establishment succeeds or finally fails within the
T300xN300 window (last cell).

Screenings of both counters are the same as for #403 and #419 counters.

The new counters are to be used in conjunction with the existing counter RRC.SuccConnEstab (#403) -
Number of RRC successful connection establishments (incremented at the reception of an RRC Connection
Setup Complete from the UE).
Metric [Sum (#403) / #428] provides the RRC Connection Setup Success Rate according to User Perception.
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 18
RRC.SuccConnEstab - #403
Number of successful RRC connections
Sub-Counter #0: Originating Conversational call
Sub-Counter #1: Originating Streaming Call
Sub-Counter #2: Originating Interactive Call
Sub-Counter #3: Originating Background Call
Sub-Counter #4: Originating Subscribed Traffic Call
Sub-Counter #5: Terminating Conversational call
Sub-Counter #6: Terminating Streaming Call
Sub-Counter #7: Terminating Interactive Call
Sub-Counter #8: Terminating Background Call
Sub-Counter #9: Emergency Call
Sub-Counter #14: Originating High Priority Signaling
Sub-Counter #17: Terminating High Priority Signaling

RRC.FailConnEstab - #404
Failed RRC Connection Establishments by Cause
Sub-Counter #7: 3G to 2G Redirection for Emergency Calls
Sub-Counter #17: 3G to 2G Redirection based on cell load

VS.RRC.ConnectionReAttempt - #439
With counter 0404, it gives a view of the failure and success rate of the 3G/2G redirection at RRC
establishment request. If no GSM cell verifies the selection criteria, the UE will re-attempt a new RACH after
the "wait time" timer (UE timer) elapses. On this new attempt, the RNC does not redirect the call to the 2G
and attempts to establish the call on the FDD cell if the Rach comes before the timer rrcCnxRepeatTime
elapses.
The counter is incremented when the RNC does not redirect this new attempt. Repeated "RRC Connection
Request" in the context T300 and N300 from the same UE (same UE Id and format) on the same RNC shall
be excluded. Note: rrcCnxRepeatTime is renamed from emergencyCallRepeatTime
Sub-Counter #0: Emergency call redirection feature
Sub-Counter #1: Redirection based on cell load feature

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 19
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 20
In case of RRC failures, it’s not possible to differentiate simultaneously the failure cause and the service
cause. Two parallel analyses are necessary to correlate the failure cause with the failure service cause:
Failure case analysis: Distribution of the failure cause screenings
Establishment failure analysis: which RRC establishment causes (Originating / Terminating Traffic
Classes, conversational, I / B, etc.) failed
Problem Detection: RRC CSR lower than a given threshold
RRC accessibility troubleshooting:
RRC failure causes distribution
RRC establishment failure cases (per RRC request cause)
First Radio Link
Failure Establishment cause
RRC Cell inactivity

VS.RadioLinkFirstSetupFailure - #41
The number of failures on the first Radio-Link setup. This excludes Radio link setups for soft handover.
A set of sub-counters screened on:
• Sub-Counter #0: RadioLinkSetupFailure • Sub-Counter #1: Timeout • Sub-Counter #2: RRM
refusal
• Sub-Counter #3: IubLayerCongestion • Sub-Counter #4: NodeBCEMLackL1Rsrc
• Sub-Counter #5: LackCidOrUdpPortIub • Sub-Counter #6: LackBwthIub
• Sub-Counter #7: InodeRefusal • Sub-Counter #8: Multi-cell Operation Not Available
• Sub-Counter #9: TMU internal resources exhausted, e.g. context pool, timer pool, etc. exhausted

VS.RrcSleepyCellInactivity - #15
This measurement represents the number of minutes since the last RRC activity was detected for this cell.
The number of minutes is rounded down to the nearest multiple of minutes in a reporting period.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 21
Issue characterization:
Can it affect some/all services (CS, PS, etc.)
Some/all Network elements, Top N cells
Some/all periods of time, since when
Some failure causes
After some events (upgrade, feature activation, configuration changes)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 22
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: when the number of RRC contexts is exhausted
Sub-Counter #10: Unavailable FACH context resource: when the number of FACH contexts in
RNC_CALL is exhausted
Sub-Counter #11: No answer from the Node B
Sub-Counter #12: Lack of C-RNTI
Sub-Counter #13: UE Ec/No lower than qQualityMin
Sub-Counter #14: Repeated 'RRC Connection Request' received in a different cell from the preceding
attempt (during the N300*T300 window). To be pegged in the cell where the 'RRC Connection
Request' prior to reselection was received.
Sub-Counter #15: In case the Manual Overload Control at Node B granularity feature is activated, if
the number of RLSs in the Node B is exceeded, the thresholdEventA,RNC starts to reject 'RRC
Connection Request'until the number of RLSs in the Node B is less than thresholdEventB
Sub-Counter #16: SRNC receives a "Radio Link Setup Failure" message causing RRC Connection Reject
to be sent
Sub-Counter #17: 3G to 2G Redirection based on cell load

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 23
VS.IrmcacDistributionEcN0 - #1043: This counter provides the distribution of Ec/N0 measurements received
per range from UEs with 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

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 24
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

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 25
VS.DistPropDelayPerRange - #1041: Distribution of propagation delays, as expressed in the
3GPP25.433 Nbap RL Setup Request (when Propagation Delay IE is present)
A set of subcounters screened on: Propagation Delay in terms of chips
Sub-Counter #0: IE in [0..1] (Cell size < 468 m)
Sub-Counter #1: IE in [2] (468 m<= Cell size < 702 m)
Sub-Counter #2: IE in [3..4] (702 m <= Cell size < 1171 m)
Sub-Counter #3: IE in [5] (1171 m <= Cell size < 1405 m)
Sub-Counter #4: IE in [6..8] (1405 m <= Cell size < 2108 m)
Sub-Counter #5: IE in [9..16] (2108 m <= Cell size < 3982 m)
Sub-Counter #6: IE in [17..42] (3982 m <= Cell size < 10072 m)
Sub-Counter #7: IE in [43..255] (Cell size equal to or above 10072 m)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 26
VS.RadioWBandRxMainPwr (#10201):
min/ max/ linear average wideband received power per sector, per frequency, at the Rx main
channelizer (sampled every 100 ms)
VS.RadioWBandRxMainPwr (#10202):
min/ max/ linear average wideband received power per sector, per frequency, at the Rx diversity
channelizer (sampled every 100 ms)

The Node B estimates the total UL Radio Load as the linear average between the UL RX Signal Level
measure at bit Main and Diversity antennas. Then this UL Radio Load is sent to the RNC through an NBAP
Common Measurement Report message (UL RTWP value). This value is available thanks to #303 RNC
counter.
VS.UplinkRssi - #303:
min/ max/ average wideband received power per sector (UL RTWP), per frequency

According to typical values of Thermal Noise and Noise Factor of the Node B and Rx aerial chain, this
indicator should be not less than –112 dBm. The typical minimum value should be between –106 dBm and
–105 dBm.
As the maximum allowed RoT is driven by a parameter lower than 8dB, the maximum value of UL RSSI
should not be over –98 dBm = -106dBm + 8 dB
The value of this metric should be between -109 dBm and -102 dBm typically.

Max and Min values can also be considered for radio problem investigation.
Delta between Main and Div UL RSSI measurement is also to be considered.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 27
VS.CellULLoad (#10211)
The Node B computes this indicator from the estimation of the RoT which is equal to the difference
between the total UL RSSI and the RTWPref.
Then the UL Cell Load is UL Cell Load = 1 – 10-(RoT/10)

Noise Rise vs. UL load


20

18

16

14
Noise Rise (dB) = RoT

12

10

0
0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1
UL load (%)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 28
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
values.
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 8 kbps

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 29
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 30
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 31
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 32
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 33
RRC.AttConnEstab - #409
RRC.FailConnEstab - #404
RRC.SuccConnEstab - #403:
A set of sub-counters screened on: Cause for rrc establishment, from 3GPP TS 25.331
Sub-Counter #0: Originating Conversational call
Sub-Counter #1: Originating Streaming Call
Sub-Counter #2: Originating Interactive Call
Sub-Counter #3: Originating Background Call
Sub-Counter #4: Originating Subscribed Traffic Call
Sub-Counter #5: Terminating Conversational call
Sub-Counter #6: Terminating Streaming Call
Sub-Counter #7: Terminating Interactive Call
Sub-Counter #8: Terminating Background Call
Sub-Counter #9: Emergency Call
Sub-Counter #10: Inter-RAT cell re-selection
Sub-Counter #11: Inter-RAT cell change order
Sub-Counter #12: registration
Sub-Counter #13: Detach
Sub-Counter #14: Originating High Priority Signaling
Sub-Counter #15: Originating Low Priority Signaling
Sub-Counter #16: Call re-establishment
Sub-Counter #17: Terminating High Priority Signaling
Sub-Counter #18: Terminating Low Priority Signaling
Sub-Counter #19: Terminating - cause unknown
Sub-Counter #20: Spare 12

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 34
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 35
The related counters are pegged on reception of NBAP RL Setup Response/Failure related to the first radio
link of a call or rejection due to a lack of resources (RRM refusal).

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 36
Screening “NodeB (CEM) lack of L1 resources” was added in UA06. It gives the number of RL setups that
fail to be established due to lack of CEM resources. The advantage of this screening is that it will enable to
link the CEM unavailability to the user perceived call blocking.

In UA07.1.3.8 and UA07.1.3.9, this screening was also used for NODEB EDCH 2msTTI CAC failure, which
did not mean a real CEM unavailability because there was still room available for EDCH 10msTTI and the RL
could be reattempted immediately as 10msTTI.

From UA08.1.3 onwards, screening “NodeB (CEM) lack of L1 resources” recovers its UA06 and UA07 (pre-
UA07.1.3.8) meaning. The new screening “NotEnoughUserPlaneProcessingResources” becomes used for the
specific case of NODEB EDCH 2msTTI CAC Failure. This comment is also valid for the
VS_RadioLinkFirstSetupFailure counter.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 37
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 38
DESCRIPTION
Speech on a wider band (50 Hz-7 kHz) than the classical telephony band (0.3 kHz – 3.4 kHz)
First address Mobile-to-Mobile communications
Can be used for Mobile to IP Phone
VALUE
Speech much more natural than classical telephony
Differentiator with Fix & GSM Networks & competition
AMR12.2 Radio engineering reusable for a WB-AMR12.65
DEPENDENCIES
Iu User Plane Frame Protocol v2 is necessary on IuCs
TFO/TrFO must be supported by the Core Network

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 39
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 40
Help/reference: UMTS access counter list (see the “SCCP” RNC counter family).

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 41
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 42
VS.IuSccpCnxSuccess #548: This counter provides the number of successful SCCP connections at the
Iu interface, screened by CN domain and by peer entity having refused the connection.
Screening:
Sub-Counter #0: With CS core network (connection requested by the RNC)
Sub-Counter #1: With PS core network (connection requested by the RNC)
Sub-Counter #2: With CS core network (connection requested by the core network)
Sub-Counter #3: With PS core network (connection requested by the core network)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 43
VS.IuSccpCnxUnsuccess #502: This counter provides the number of failed SCCP connections at the Iu
interface, screened by CN domain and by peer entity having refused the connection.
Screening:
Sub-Counter #0: Fail Iu-cs connection req by RNC
Sub-Counter #1: Fail Iu-cs connection req by Core Network CS
Sub-Counter #2: Fail Iu-ps connection req by RNC
Sub-Counter #3: Fail Iu-ps connection req by Core Network PS

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 44
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 45
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 46
Problem description: failures in Iu SCCP connection phase. It can lead to accessibility failures.
Detection: the Iu SCCP Connection Success rate is less than 99%.
Issue characterization:
Iu CS or Iu PS issue?
Affecting all RNCs/only specific RNCs
Punctual degradation that disappears? Or degradation remains?
Some/all period of time, since when

The Iu SCCP analysis aims at identifying the period of the degradation of the Iu SCCP success rate and the
level of degradation: in all the RNCs in the PS and CS domains.
When the period and the network element level have determined correlation with alarms:
HW failures at SGSN
HW failures at MSC
HW failures at RNC
The main limitation of the SCCP connection metrics is that signaling is also considered as an action.
For RNC stability analysis, refer to the Stability Monitoring module.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 47
GQ01
GQ02
GQ03

OQ01
OQ02
OQ03
OQ04
KQ01
KQ02
15/10/06
14/10/06
13/10/06
12/10/06
11/10/06
10/10/06
09/10/06
08/10/06
07/10/06
06/10/06
05/10/06

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


04/10/06

Iu SCCP PS success rate (IuSCCP006)

TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1


03/10/06
02/10/06
01/10/06
30/09/06
29/09/06
28/09/06

Section 1 · Module 4 · Page 48


27/09/06
26/09/06
25/09/06
24/09/06
23/09/06
22/09/06
21/09/06
20/09/06
19/09/06
18/09/06
17/09/06
16/09/06
15/09/06
14/09/06
13/09/06
12/09/06
11/09/06
10/09/06
09/09/06
08/09/06
07/09/06
06/09/06
05/09/06
04/09/06
03/09/06
02/09/06
01/09/06
31/08/06
30/08/06
29/08/06
28/08/06
27/08/06
26/08/06
25/08/06
24/08/06
23/08/06
22/08/06
21/08/06

100.00%

99.00%

98.00%

97.00%

96.00%

95.00%
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 49
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 50
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 51
VS.SmcSuccess #701: This counter provides the number of successful RANAP Security Mode Command
procedures screened by the Core Network domain.
Screening:
0: SMC on Iu-CS
1: SMC on Iu-PS

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 52
VS.RejectedSmc #702: This counter provides the number of failed RANAP Security Mode Command
procedures (before sending the RRC SMC) screened by the Core Network domain.
Screening:
0: SMC on Iu-CS
1: SMC on Iu-PS

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 53
VS.FailedRrcSmc #703: This counter provides the number of failed RRC Security Mode Command
procedures screened by the Core Network domain.
Screening:
0: SMC on Iu-CS
1: SMC on Iu-PS

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 54
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 55
SMC: Security Mode Command

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 56
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 57
VS.RabEstablishmentRequestsPerRabType #1656
RANAP/RAB assignment request message to set up a new RAB

Sub-Counter #0: Other Dl, Ul, Traffic Class combinations


Sub-Counter #1: Dl and Ul are CS Speech, TC is Conversational
Sub-Counter #2: Dl and Ul are CSD 64, TC is Conversational
Sub-Counter #3: Dl and Ul are CS, TC is Streaming
Sub-Counter #4: Dl is any low rate PS I/B, Ul is any PS I/B, TC is Interative
Sub-Counter #5: Dl is any low rate PS I/B, Ul is any PS I/B, TC is Background
Sub-Counter #6: Dl is any high rate PS I/B, Ul is any PS I/B, TC is Interative
Sub-Counter #7: Dl is any high rate PS I/B, Ul is any PS I/B, TC is Background
Sub-Counter #8: Dl is any low rate Ps Str and Ul is any PS Str, TC is Streaming
Sub-Counter #9: Dl is any high rate Ps Str and Ul is any PS Str, TC is Streaming

#1620 VS.RabEstabPerReqRabTypeRefCell is the same counter but at Reference cell level.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 58
VS.RabEstablishmentSuccessPerRequestedRabType #1657: number of successful RAB
establishment per requested RAB type (to map the successes with the requests) (per RABid and not per
procedure). This counter should also be pegged for RAB successfully allocated for incoming relocations.
Screening: per requested RAB type (requested should be understood to be after RAB matching). The
screening is the same as for counter #1656.

#1665 VS.RabEstabSuccPerReqRabTypRefCell is the same counter but at Reference cell level.

VS.RabEstablishmentSuccessPerGrantedRabType #1658: number of successful RAB establishment


per granted RAB type (per RABid and not per procedure).
This counter should also be pegged for RAB successfully allocated for incoming relocations.
Screening: per granted RAB type (granted should be understood to be after iRM Table matching).
A set of sub-counters screened on: DlRbSetId,UlRbSetId,TrafficClass derived screening per granted RAB

Sub-Counter #0: Other Dl, Ul, Traffic Class combinations


Sub-Counter #1: Dl and Ul are CS Speech, TC is Conversational
Sub-Counter #2: Dl and Ul are CSD 64, TC is Conversational
Sub-Counter #3: Dl and Ul are CS, TC is Streaming
Sub-Counter #4: Dl is any low rate PS I/B, Ul is any PS I/B, TC is Interative
Sub-Counter #5: Dl is any low rate PS I/B, Ul is any PS I/B, TC is Background
Sub-Counter #6: Dl is any high rate PS I/B, Ul is any PS I/B, TC is Interative
Sub-Counter #7: Dl is any high rate PS I/B, Ul is any PS I/B, TC is Background
Sub-Counter #8: Dl is any low rate Ps Str and Ul is any PS Str, TC is Streaming
Sub-Counter #9: Dl is any high rate Ps Str and Ul is any PS Str, TC is Streaming

#1621 VS.RabEstabSuccPerGrantedRabTypeRefCell is the same counter but at Reference cell level.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 59
VS.RadioBearerSetupRequest #1652: number of Radio Bearer setup decisions (leading or not to a RB
Setup, i.e. Incremented even if CAC rejects the setup). The counter should be pegged multiple times for
multiple RBs to be set up in the same procedure. Incremented based on reference cell.

A set of sub-counters screened on: Target Type of call setup mapping

Sub-Counter #0: Other combinations


Sub-Counter #1: CS Speech NB or LR AMR
Sub-Counter #2: CS Speech WB AMR
Sub-Counter #3: CS Data
Sub-Counter #4: CS Streaming
Sub-Counter #5: PS Streaming < 64
Sub-Counter #6: PS Streaming 64
Sub-Counter #7: PS Streaming 128
Sub-Counter #8: PS Streaming 256
Sub-Counter #9: PS Streaming 384
Sub-Counter #10: PS I/B < 64
Sub-Counter #11: PS I/B 64
Sub-Counter #12: PS I/B 128
Sub-Counter #13: PS I/B 256
Sub-Counter #14: PS I/B 384
Sub-Counter #15: HSDPA/R99
Sub-Counter #16: PS I/B or PS Str HSDPA/E-DCH

VS.RadioBearerSetupSuccess #1650: number of Radio Bearer set up successfully. The counter should
be pegged multiple times for multiple RB successfully set up in the same procedure. Incremented on the
Reference cell of the call.

The screening is the same as for counter #1652.

Multi-RABs (CS + PS) are mainly used by smart phones:


Either the end user initiates or receives a speech call while a PS session is on-going
(background session or session triggered by the end user).
Or the phone initiates a PS session in background while the end user has an on-going
speech call.
The UTRAN Release UA08.1 introduces 3 new counters to monitor the multi-RAB establishment and
release:
VS_RABEstabCSWithPSPresent (U2706)
VS_RABEstabPSWithCSPresent (U2707)
VS_RABRelCSWithPSPresent (U2708)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 60
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 61
VS.RadioBearerEstablishmentUnsuccess #1629: number of radio bearer setups not successfully
established, with no RADIO_BEARER_SETUP_REQUEST sent (based on procedure count, not RBs).
Incremented based on reference cell. It mainly corresponds to CAC failure cases.
Screening: A set of detailed sub-counters is provided for troubleshooting purposes:
Sub-Counter #0: invalid RAB parameter value
Sub-Counter #1: unavailable dl code resources
Sub-Counter #2: unavailable dl power resources
Sub-Counter #3: Unspecified
Sub-Counter #4: RL failure or RLC error
Sub-Counter #5: Unused
Sub-Counter #6: CAC RNC Processing resources
Sub-Counter #7: NodeB (CEM) lack of L1 resources
Sub-Counter #8: Lack of transport identifier on the Iu
Sub-Counter #9: Lack of bandwidth on the Iu
Sub-Counter #10: Lack of transport identifier on the Iur
Sub-Counter #11: Lack of bandwidth on the Iur
Sub-Counter #12: Lack of transport identifier on the Iub
Sub-Counter #13: Lack of bandwidth on the IuB
Sub-Counter #14: Congestion Preemption Lower Priority
VS.RabAssignmentSetupUnsuccess #1662: number of RAB assignment unsuccessfully set up (per
RAB Id, and not per message). This counter should also be pegged when a RAB fails to be allocated for an
incoming relocation.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 62
VS.RadioBearerSetupUnsuccess #602: number of failed Radio Bearer establishments per cell. This
measurement provides the number of RB establishment procedure 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 an RRC RADIO BEARER SETUP FAILURE message.
#2 ---> Any other failure causing an RB setup procedure to be unsuccessful.
VS.RabAssignmentSetupUnsuccess #1662: number of RAB assignments unsuccessfully setup (per
RABid, and not per message). This counter should also be pegged when a RAB fails to be allocated for an
incoming relocation.
DlRbSetId,UlRbSetId,TrafficClass derived screening per requested RAB
Sub-Counter #0: Other Dl, Ul, Traffic Class combinations
Sub-Counter #1: Dl and Ul are CS Speech, TC is Conversational
Sub-Counter #2: Dl and Ul are CSD 64, TC is Conversational
Sub-Counter #3: Dl and Ul are CS, TC is Streaming
Sub-Counter #4: Dl is any low rate PS I/B, Ul is any PS I/B, TC is Interative
Sub-Counter #5: Dl is any low rate PS I/B, Ul is any PS I/B, TC is Background
Sub-Counter #6: Dl is any high rate PS I/B, Ul is any PS I/B, TC is Interative
Sub-Counter #7: Dl is any high rate PS I/B, Ul is any PS I/B, TC is Background
Sub-Counter #8: Dl is any low rate Ps Str and Ul is any PS Str, TC is Streaming
Sub-Counter #9: Dl is any high rate Ps Str and Ul is any PS Str, TC is Streaming
Sub-Counter #10: Dl and Ul are CS Speech HSPA, TC is Conversational
Sub-Counter #11: Dl and Ul are PS Conv HSPA, TC is Conversational
Sub-Counter #12: Dl and UL are PS I/B QCHAT HSPA, TC is Interactive

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 63
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 64
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 65
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 66
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 67
Issue characterization:

Can it affect some/all services (CS, PS, etc.)?

Some/all Network elements, Top N cells

Some/all periods of time, since when

Some failure causes

After some events (upgrade, feature activation, configuration changes)

Correlation between 2 parallel analyses:

RB failure analysis per cause of failure (#0631 and #602)

RB failure analysis per type of call setup (# 0691 and #0687)

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

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 68
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 69
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 70
The call setup 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 should be the complete formula but NPO considers the performance of the Security Mode
Command procedure apart.
Metrics update in UA08.1: CallSetupSuccessRate_CSSR005_R_Cs and
CallSetupSuccessRate_CSSR005_R_Ps:
CallSetupSuccessRate_CSSR005_R_Cs update formula with
RRCConnectionSuccessRate (RRC021_CR_Cs) instead of FirstRRCConnectionSuccessRate
(RRC013_CR_Cs)
CallSetupSuccessRate_CSSR005_R_Ps update formula with
RRCConnectionSuccessRate (RRC021_CR_Ps) instead of FirstRRCConnectionSuccessRate
(RRC013_CR_Ps) and account for new MRAB counters
UA07.1 Formula:
FirstRRCConnectionSuccessRate_RRC013_CR_Cs*IuSCCPSuccessRate_IuSCCP006_R_Cs*RABEstablishment
SuccessRatePerRequestedRAB_RAB0
1_R_Cs
UA08.1 Formula:
RRCConnectionSuccessRateExcRep_RRC021_ExcRep_CR_Cs*IuSCCPSuccessRate_IuSCCP006_R_Cs*RABEs
tablishmentSuccessRatePerRequestedRAB_RAB011_R_Cs
Rationale behind the change. With UA08.1, we consider the RRC Connection success rate excluding RRC
repetition requests, which is more accurate in computing the user perspective of RRC success rate, rather
than the UA07.1 formula which included RRC repetitions, that is to say showing more of a network
perspective for the RRC success rate, which is a bit more pessimistic.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 71
1. Check the sub-metrics which CSSR is made up of to identify from which one the decrease comes:
RRC Connection success rate
Global RAB assignment success ratio
Iu SCCP Success rate
In case of accessibility issues during SMC procedure, look into SMC metrics
Split the metric into PS/CS
2. Once the metric that has the problem identified, it’s time to move on to a detailed level.
The RNC from where the problem comes is identified.
Does the problem come from some specific fddcells or is it homogeneous? In this case, if the
degradation of performance is produced randomly, it may be produced by one specific UE. To detect
the kind of problem the mobile is causing, it is recommended (IMSI, IMEI, etc.) to put a CTg. The time
to put to CTg will depend on the trigger of an alarm based on fddcell RRC thresholds.
In this step, the specific time when the degradation occurs is identified.
3. Use specific troubleshooting reports per fddcell depending on at which step the problem occurs.
4. Check the radio part and the capacity or blocking depending on from which phase the problem comes.
5. Check the radio part and the capacity or blocking depending on from which phase the problem comes.
The following subjects are defined in the next chapters.
RF Audit – fddcell
BTS RF Power
OVSF Codes
BTS Channel elements
Iub Interface
RNC-TMU
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 72
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 73
The drawback of metric UCSSR005 is that this indicator does not provide the Call Setup performance at Cell
level. The two indicators UCSSR006 (CS) and UCSSR007 (PS) remove this limitation and include the
Authentication and Security & Integrity procedures in the formula. This formula will be a product of:
RRC Success rate excluding the repetitions
SRB retainability (including Authentication, Security & Integrity)
RAB Establishment success rate

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 74
Metrics difference: difference between CSSR005 and CSSR006 and CSSR007

Another possibility to monitor the Call Setup Success Rate at RNC and Cell levels is to use the baseline
Indicator CallSetupSuccessRateCS_CSSR006_R and CallSetupSuccessRateCS_CSSR006_C for CS,
CallSetupSuccessRatePS_CSSR007_R and CallSetupSuccessRatePS_CSSR007_C for PS. These indicators
provide a more exact way of monitoring for the CSSR. The main differences between both indicators and
CSSR005 are:
CallSetupSuccessRateCS_CSSR006_/ CallSetupSuccessRatePS_CSSR007 compute RRC
connection Success Rate without taking into consideration the UE repetitions for the RRC Connection
Requests on the same cell or on a different cell in case of cell reselection, whereas
CallSetupSuccessRate_CSSR005 computes the RRC Connection Success Rate for a given UE on a
given cell.

CallSetupSuccessRateCS_CSSR006/ CallSetupSuccessRatePS_CSSR007 considers the


Signaling Radio Bearer Retainability, which provides the probability of maintaining the RRC connection
after it has been established, whereas CallSetupSuccessRate_CSSR005_ doesn’t monitor this
probability.
When Computing the RAB establishment Success Rate, CallSetupSuccessRateCS_CSSR006/
CallSetupSuccessRatePS_CSSR007 deducts the total RAB establishment cancellations based on MSC
requests from the total of RAB establishment attempts to provide the accurate rate of attempted RAB
establishments, whereas CallSetupSuccessRate_CSSR005 considers the total requested RAB
establishments directly.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 75
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 76
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 77
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.4 Edition 1
Section 1 · Module 4 · Page 78
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 1
This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 2
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 3
This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 4
Page

1 Retainability analysis 7
1.1 Call drop: definition 8
1.2 Network retainability performance 9
1.3 Call drop: RL failure detected by RNC 10
1.4 Call drop: RLC unrecoverable error detected by UE 12
1.5 Call drops due to UTRAN generated reasons 13
1.6 IuReleaseRequest causes 14
1.6.1 User inactivity 15
1.6.2 Iu user plane failure 16
1.6.3 OAM intervention 17
1.6.4 Unspecified failure 18
1.6.5 Repeat integrity check failure 19
1.6.6 UE generated signaling connection release 20
1.6.7 Radio connection with UE lost 21
1.6.8 Abnormal condition timer relocation expiry 22
1.6.9 DL RLC error SRB 23
1.6.10 UL RLC error SRB 24
1.6.11 DL RLC error TRB 25
1.6.12 UL RLC error TRB 26
1.6.13 T360 expiry 27
1.6.14 Connection with Node B Lost 28
1.6.15 Release due to UTRAN generated reason 29
1.6.16 No remaining RAB 30
1.6.17 Failure in the radio interface procedure 31
1.6.18 No resource available 32
1.6.19 T305 expiry 33
1.6.20 Cell reselection fail 34
1.6.21 UTRAN page fail 35
1.6.22 Physical channel reestablishment fail 36
1.6.23 Relocation triggered 37
1.7 Call drop rate: RNC level 38
1.8 CS call drop rate: reference FDDCell level 39
1.9 PS call drop rate: reference FDDCell level 40
1.10 Part of call drop: radio connection lost with UE 41
1.11 Multi-RAB call drop reduction for smartphone 42
2 Retainability troubleshooting 45
2.1 Call drop rate analysis 46
2.2 Retainability issue causes 47
2.3 Compare Cs, PS and SRB drop rates 48
2.4 Compare drop cause 49
2.5 Typical radio problems in a W-CDMA network 51
2.5.1 Detection of bad radio conditions 52
2.5.2 Missing neighbor - Impact 53
2.5.3 Missing neighbor – Detection and solution 54
2.5.4 Isolated site - Impact 55
2.5.6 Isolated site - Detection and solution 56
2.5.7 Radio pollution - Impact 57
2.5.8 Radio pollution - Detection and solution 58

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 5
This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 6
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 7
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 RABs
related to a particular UE:
RAB Release request: triggered by the RNC, requesting the CN to release a particular RAB or a set of
RABs for a specific UE. RRC connection may still be active.
The Core network may trigger either 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. The RRC connection is also
released. The CN could respond with the 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 counted on the messages described above per Reference FDDCell and per
DlAsConfId or at least per CN domain (CS and PS).

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 8
In general, a call drop can be generated by the following reasons:
Radio issues (interference, deficient coverage, BLER, UE measurement control failures, UL
measurement report failures)
Lack of resources (channelization codes, DL power, transport)
Mobility issues (missing neighbors, HHO failure, SHO problems, slow handovers, primary cell
change)
Defence mechanisms (board or interface reset)
Failure during the RRC procedure (systematic negative answer from the UE)
Operation and Maintenance (network operations)
Software problems

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 9
VS.IuReleaseReqCs - #576
Number of RANAP/IU_RELEASE_REQUEST sent by RNC to Core Network CS
A set of sub-counters 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 cnx release
Sub-Counter #4: Radio cnx with UE lost
Sub-Counter #5: Abnormal condition with cause TRelocOveral 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 Expiry
Sub-Counter #10: Connection with Node B lost
Sub-Counter #11: Release due to UTRAN Generated Reason
Sub-Counter #12: No Remaining RAB
Sub-Counter #13: Failure in the Radio Interface Procedure
Sub-Counter #14: No Resource Available

VS.IuAbnormalReleaseRequestCs - #595
This measurement represents the number of Iu CS release requests due to abnormal conditions.
A set of sub-counters screened on: Derived AsConf Screening for CS DlAsConfId:
Sub-Counter #1: Signaling Only
Sub-Counter #2: CS speech NB or LR AMR
Sub-Counter #3: CS speech WB AMR
Sub-Counter #4: CS data
Sub-Counter #5: CS Streaming 57.6
Sub-Counter #6: CS Streaming 14.4
Sub-Counter #7: Any PS
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 10
VS.IuReleaseReqPs - #599

Counter #0599 Screenings


0 UserInactivity 6 RadioCnxUeLost 12 T360Expiry
1 IuUserPlaneFailure 7 13
AbnormalConditionTimerRelocExpiry ConnectionWithNodeBLost

2 OamIntervention 8 DlRLCErrSRB 14
ReleaseDueToUtranGenerat
edReason
3 UnspecifiedFailure 9 UlRLCErrSRB 15 NoRemainingRAB
4 RepeatedIntegrityCheckFailure 10 DlRLCErrTRB 16
FailureInTheRadioInterface
Procedure
5 11 UlRLCErrTRB 17 NoResourceAvailable
UeGeneratedSignallingConnectio
nRelease
18 T305Expiry 19 CellReselFail 20 UtranPageFail
21 PhyChnReestabFail 22 RelocationTriggered

VS.IuAbnormalReleaseRequestPs - #589
This measurement represents the Number of Iu Release Requests due to abnormal conditions sent
towards the PS domain, when the reference cell of these calls is located on the serving RNC.
A set of subcounters screened:
• Sub-Counter #0: Other type of Call • Sub-Counter #1: Signaling Only
• Sub-Counter #2: PS Streaming < 64 • Sub-Counter #3: PS Streaming 64
• Sub-Counter #4: PS Streaming 128 • Sub-Counter #5: PS Streaming 256
• Sub-Counter #6: PS Streaming 384 • Sub-Counter #7: TRB on cell FACH
• Sub-Counter #8: PS I/B < 64 • Sub-Counter #9: PS I/B 64
• Sub-Counter #10: PS I/B 128 • Sub-Counter #11: PS I/B 256
• Sub-Counter #12: PS I/B 384 • Sub-Counter #13: HSDPA
• Sub-Counter #14: xPCH • Sub-Counter #15: Any C
VS.RadioLinkDroppedLastRadioLink - #53
Number of dropped calls (on last radio-link release), for each cell controlled by the RNC.
A set of sub-counters screened on: Type of call for dropped last radio link
• Sub-Counter #0: Other Type of Call • Sub-Counter #1: SRB (DCH or cell FACH)
• Sub-Counter #2: CS speech NB or LR AMR • Sub-Counter #3: CS speech WB AMR
• Sub-Counter #4: CS data • Sub-Counter #5: Any CS Streaming
• Sub-Counter #6: Any PS I/B or PS Streaming • Sub-Counter #7: HSDPA DL/DCH UL
• Sub-Counter #8: PS I/B or PS Str HSDPA DL/E-DCH UL

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 11
VS.IuReleaseCompleteCs #594: the number of times the RNC sends an Iu release complete on the
Iu-CS interface to the MSC. It corresponds to all cases of an Iu release scenario, normal and abnormal.

A set of sub-counters screened on:

Sub-Counter #0: Other


Sub-Counter #1: Signaling Only
Sub-Counter #2: CS speech NB or LR AMR
Sub-Counter #3: CS speech WB AMR
Sub-Counter #4: CS data
Sub-Counter #5: CS Streaming 57.6
Sub-Counter #6: CS Streaming 14.4
Sub-Counter #7: Any PS

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 12
The normal cases are:
Release due to UE generated signaling connection release
User inactivity (in case of always-on)
Last Remaining RAB

All Other cases are considered as abnormal.


The abnormal cases currently covered are the following ones:
O&M intervention
Repeated integrity check failure
Radio connection lost
Relocation timeout (corresponding to timeout of TrelocoverallExpiry and TrelocCompleteExpiry)
Unspecified failure

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 13
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 14
This screening is incremented in case of inactivity of a PS user with an Interactive or Background service. It
is not associated with an undesired or abnormal behavior of the network, with a related negative impact on
customer perception, so it should not be interpreted as a dropped call.
A session is downgraded to idle mode if there has been no (or very little) user traffic for a certain period of
time. This state is also known as AO Step 3 and was previously referred to as Step 2. In this state, the
session has released all its radio resources, but the PDP context is still maintained by the core network.
The RANAP cause used is “User Inactivity (16)”, and this screening is systematically incremented whenever
the RNC sends a RANAP/IU_RELEASE_REQUEST message with this cause.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 15
The Iu UP layer in Transparent Mode is present in the Iu user plane for transferring data transparently over
the Iu interface and is intended for those RABs that do not require any particular feature from the Iu UP
protocol other than transfer of user data, such as Ps (the Iu UP protocol layer uses the services of a GTP-U
transport).
In opposition, the Support Mode of operation (used with AMR, for example) involves initialization, rate
control, time alignment and handling of error events. In case of Transparent Mode, the management of the
errors is performed by RANAP, which is the protocol responsible for the release of the resources in case of
failure in the Iu UP protocol, a scenario for which this screening is incremented.
The RANAP cause used is “Iu UP Failure (28)”, and this screening is systematically incremented whenever
the RNC sends a RANAP/IU_RELEASE_REQUEST message with this cause. This screening is not used for CS
RABs.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 16
This screening is incremented when an equipment or interface is locked, leading to the drop of the RABs
using these resources.
In case of Node B lock, Node B Soft Shutdown ensures a smooth shutdown of the Node B for maintenance
purposes through a gentle offload of the traffic, before the Node B is taken out of service. Once a shutdown
is triggered, the RNC bars the corresponding cells to prevent new call establishment and reduces their size
by decreasing progressively the CPICH power and maximum transmission power of each cell until the
maximum transmission power reaches the minimum DL power indicated by the Node B. This will cause
existing calls to handover to an adjacent cell (when possible) and prevents new calls from handing over to
the cell.
The RANAP cause used is “O&M Intervention (113)”, and this screening is systematically incremented
whenever the RNC sends a RANAP/IU_RELEASE_REQUEST message with this cause.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 17
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 18
This screening is incremented in case of security mode integrity activation, when a number of integrity
checks fail for successive RRC connection oriented messages. The number of integrity failures that lead to
Iu Release is determined by static parameter nIntegrityCheckFail (set to 2) in the MIB of the RNC.
Integrity protection is used to ensure that the content of a signaling message between the network and the
user has not been manipulated. It applies to RRC and NAS messages.
The RANAP cause used for Iu release is “Repeated Integrity Check Failure (37)”, and this screening is
systematically incremented whenever the RNC sends a RANAP/IU_RELEASE_REQUEST message with this
cause.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 19
Large values for this screening have been recurrently observed in networks with large penetration of
Blackberry phones, which re-establish the connection to the network for short data transfer sessions
(approximately 3.5 seconds). When the data transfer is finalized, the UE sends the
RRC/SIGNALLING_CONNECTION_RELEASE_REQUEST message to the RNC. This occurs periodically and
should not be considered as a dropped call.
The RANAP cause used for Iu release is “Release Due To UE Generated Signalling Connection Release
(40)”, and this screening is systematically incremented whenever the RNC sends a
RANAP/IU_RELEASE_REQUEST message with this cause.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 20
This scenario is related to dropped calls in areas with poor radio conditions. There are two main events that
can trigger an Iu Release Request with this cause: layer 3 timeouts or synchronization loss detected at
Radio Link Layer, either in uplink or downlink, for the solely remaining radio link serving the call.
For the dedicated channels, synchronization primitives are used to indicate the synchronization status of the
radio links. Layer 1 shall report in-sync/out-of-sync to layer 3, which in turn will evaluate the
synchronization status and will signal a Radio Link Failure if necessary. Loss of synchronization can be
detected in both UE and Node B.

It is worth noting that UA06 feature 33821 – RRC Connection Re-establishment allows the RNC, upon
detection of Radio Link Failure or RLC unrecoverable error (either from the Node B or the UE), to release
the old Node B resources and re-establish the call, following a Cell Update procedure triggered by the UE.
The RANAP cause used for Iu release is “Radio Connection With UE Lost (46)”. This screening is not
systematically incremented whenever the RNC sends a RANAP/IU_RELEASE_REQUEST message with this
cause, as this RANAP cause is also used in case of radio drop detected at RLC layer (RLC unrecoverable
error with UE in Cell_DCH or Cell_FACH).

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 21
The conditions for incrementing this screening concern an abnormal condition during the relocation
execution procedure, involved in 3G to 3G inter-frequency inter-RNC hard handover.
After concluding the relocation preparation phase, the RNC starts timer TRELOCOverall, defining a time
interval during which the RANAP/IU_RELEASE_COMMAND message with cause “Successful Relocation”
must be received, meaning that the handover has been completed. If the Iu release procedure is not
initiated towards the (source) RNC before timer expiration, the (source) RNC will trigger the abnormal Iu
release.
The RANAP cause used for Iu release is “TRELOCOverall Expiry (2)”, and this screening is systematically
incremented whenever the RNC sends a RANAP/IU_RELEASE_REQUEST message with this cause.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 22
This screening is incremented when a loss of RLC acknowledgements leads to an RLC unrecoverable error
for the SRB in downlink, resulting in a call drop. This is a consequence of the RLC reset procedure, initiated
when the transmission of an RLC PDU does not succeed within a certain time limit, to avoid RLC buffer
overflow.

With RLC Acknowledge Mode, there must be an acknowledgment of the RLC PDU transmitted. This mode of
operation provides error correction through a retransmission mechanism. If there is no answer to polling
after a defined timer expires (pollingTimer), the PDU is retransmitted up to a maximum number of times
(defined by maxDat) before the SDU is discarded with a reset PDU. For SRB3.4, maxDat is set to 40 and
polling timer is equal to 100 ms.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 23
This screening is equivalent to the previous one, although it is applicable when the RLC error is detected for
the SRB in uplink.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 24
This screening is incremented when a loss of RLC acknowledgements leads to a RLC unrecoverable error for
the TRB in downlink (detected by the RNC), resulting in a call drop. This may happen when the UE is in
Cell_FACH state or Cell_DCH state.

As in the SRB case (2 previous screenings), UA6 feature 33821 – RRC Connection Reestablishment allows
the RNC, upon detection of RLC unrecoverable error, to re-establish the call, following a Cell Update
procedure triggered by the UE. This is applicable when the RLC
error occurs with the UE in Cell_DCH state.
The RANAP cause used for Iu release is “Radio Connection With UE Lost (46)”. This screening is not
systematically incremented whenever the RNC sends a RANAP/IU_RELEASE_REQUEST message with this
cause, as this RANAP cause is also used in case of radio drop detected at
Radio Link layer (Radio Link Failure) and the other cases of RLC unrecoverable error (UE in Cell_DCH or
Cell_FACH).

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 25
This screening is equivalent to the previous one, although it is applicable when the RLC error is detected for
the TRB in uplink.

As in the SRB case (screenings #8 and #9), UA06 feature 33821 – RRC Connection Reestablishment allows
the RNC, upon detection of an RLC unrecoverable error, to re-establish the call, following a Cell Update
procedure triggered by the UE. This is applicable when the RLC error occurs with the UE in Cell_DCH state.
The RANAP cause used for Iu release is “Radio Connection With UE Lost (46)”. This screening is not
systematically incremented whenever the RNC sends a RANAP/IU_RELEASE_REQUEST message with this
cause, as this RANAP cause is also used in case of radio drop detected at Radio Link layer (Radio Link
Failure) and the other cases of RLC unrecoverable error (UE in Cell_DCH or Cell_FACH).

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 26
This screening is incremented if the RNC, after sending the RRC/RADIO_BEARER_RELEASE message, does
not receive the RRC/RADIO_BEARER_RELEASE_COMPLETE or RRC/RADIO_BEARER_RELEASE_FAILURE
before expiry of timer T360.
The RANAP cause used for Iu release is “Unspecified Failure (115)”. This screening is not systematically
incremented whenever the RNC sends a RANAP/IU_RELEASE_REQUEST message with this cause.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 27
This screening is intended to separate the losses in the radio part (covered by radio link failure and RLC
unrecoverable error scenarios) from the ones that occur due to a break of communication with the Node B,
in case of loss of AAL2, SSCOP, NBAP reset or RSI, other than the cases covered by screening “O&M
Intervention”.
The RANAP cause used is “Radio Connection With UE Lost (46)”, and this screening is not systematically
incremented whenever the RNC sends a RANAP/IU_RELEASE_REQUEST message with this cause, as this
screening is also used in case of radio link loss or RLC reset.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 28
This screening is incremented in case of breakdown during an RRC procedure, most notably failures when
reconfiguring a radio bearer – RB Bit Rate Adaptation, Always-On Step 1 downsize, etc – due to timer T361
expiry (RNC does not receive
RRC/RADIO_BEARER_RECONFIGURATION_COMPLETE or
RRC/RADIO_BEARER_RECONFIGURATION_FAILURE message after sending
RRC/RADIO_BEARER_RECONFIGURATION.
The RANAP cause used is “Release Due To Utran Generated Reason (15)”, and this screening is
systematically incremented whenever the RNC sends a RANAP/IU_RELEASE_REQUEST message with this
cause.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 29
This screening is incremented following an Iu Release Request as a response to a
RANAP/RAB_ASSIGNMENT_REQUEST message with RAB to release. As such, it should not be considered as
a dropped call.
The RANAP cause used is “No Remaining RAB (31)”, and this screening is systematically incremented
whenever the RNC sends a RANAP/IU_RELEASE_REQUEST message with this cause.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 30
This screening is incremented whenever a procedure involving the core network is not successful due to a
failure in a UTRAN related process, most commonly during RAB establishment when the setup of the radio
bearer fails or during the security mode procedure in case a RANAP/SECURITY_MODE_REJECT message is
sent by the RNC. The RANAP cause used is “Failure In The Radio Interface Procedure (14)”, and this
screening is systematically incremented whenever the RNC sends a RANAP/IU_RELEASE_REQUEST
message with this cause.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 31
This screening is incremented in case of lack of resources that prevents a successful outcome of a
procedure (power, codes, CE). The most common case seen is for Always-On upsizing, following traffic
resuming in DL.
The RANAP cause used is “No Resource Available (114)”, and this screening is systematically incremented
whenever the RNC sends a RANAP/IU_RELEASE_REQUEST message with this cause.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 32
This screening is incremented when the timerCellUpdateProcessingMargin in the RNC used to detect users
in Cell_FACH state which have lost coverage but whose resources are yet to be released.
While in Cell_FACH, the UE must periodically signal its location to the network. The periodicity is defined by
timer T305, which starts when the UE enters the Cell_FACH state at the reception of the
RRC/CELL_UPDATE_CONFIRM message and stops after a transition to another RRC state.
At expiry of T305, the UE transmits an RRC/CELL_UPDATE (cause “periodical cell update”) if the UE detects
“in service area” and timer T307 is not activated. Otherwise, if the UE detects “out of service area”, T307 is
started, if not active. At T307 expiry, the UE goes to idle mode and all resources are released. The RNC will
later release all the resources associated with this UE, as it won’t receive a periodic cell update after expiry
of timerCellUpdateProcessingMarge (in the same way, these resources will be equally released even if the
UE sends the RRC/CELL_UPDATE message, but it does not reach the RNC).
The RANAP cause used for Iu release is “Radio Connection With UE Lost (46)”. This screening is not
systematically incremented whenever the RNC sends a RANAP/IU_RELEASE_REQUEST message with this
cause.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 33
The pre-condition for incrementing this screening is the UE being in the Cell_FACH state and sending an
RRC/CELL_UPDATE message to the RNC with cause “cell reselection”. The RNC has new cell common
channel resources available and sends an RRC/CELL_UPDATE_CONFIRM message.
The screening is incremented if, after a number of repetitions of the RRC/CELL_UPDATE message (defined
by N362), there is still no response from the UE.
The RANAP cause used for Iu release is “Radio Connection With UE Lost (46)”. This screening is not
systematically incremented whenever the RNC sends a RANAP/IU_RELEASE_REQUEST message with this
cause.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 34
This screening is incremented when the UE is in Cell_PCH state and the number of Paging Type 1 retries is
decremented to zero.
The RANAP cause used for Iu release is “Radio Connection With UE Lost (46)”. This screening is not
systematically incremented whenever the RNC sends a RANAP/IU_RELEASE_REQUEST message with this
cause.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 35
The pre-condition for incrementing this screening is the UE being in URA_PCH state and sending a
RRC/CELL_UPDATE message to the RNC with cause “uplink data transmission”. The RNC has new cell
common channel resources available and sends a RRC/CELL_UPDATE_CONFIRM message to the UE.
The screening is pegged if the UE sends an RRC/CELL_UPDATE message with cause “radio link failure” in
response to the RRC/CELL_UPDATE_CONFIRM message sent by the RNC.
The RANAP cause used for Iu release is “Radio Connection With UE Lost (46)”. This screening is not
systematically incremented whenever the RNC sends a RANAP/IU_RELEASE_REQUEST message with this
cause.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 36
UA08.1 introduces a new screening U599_22
A Timer T361 should be stopped during 3G to 2G mobility with UE in Cell_FACH or Cell_PCH.
In case of T361 timeout, with IuReleaseReq sent to CN, while having “SRSN ctx request” received, in the
RNC, the drop cause “Radio Connection With UE Lost” is replaced by “Relocation Triggered” in the Iu
release request sent to the CN.
VS_IuReleaseReqPs_RelocationTriggered; U599_22 should be incremented in this case, whereas Counter
589 VS.IuAbnormalReleaseRequestPs should not be pegged in this case.

This Screening is pegged when the UE that has PDP is activated on 3G in either Cell_FACH or Cell_PCH
state. The 3G radio condition becomes bad whereas the 2G radio condition becomes good.
Due to traffic management, the RNC sends RRC Radio Bearer Reconfiguration to the UE.
Timer T361 starts.
Due to the degradation of 3G radio conditions, the UE never receives this RBreconf or the RNC never
receives RBreconf Complete.
As 3G is in bad radio conditions and 2G is good, the UE decides to move to 2G.
The UE sends to the 2G-SGSN a Routing Area Request with NSAPI(5) =Not PDP Inactive.
The PDP context in 3G is transferred in 2G using GTP and RANAP context transfer procedures.
3G-SGSN sends a RANAP/ SRNS data forward command to the RNC.
The RNC then releases Iu via Iu Release Request Cause Relocation Triggered.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 37
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 parameter setting.
VS.IuAbnormRelReqCsNrnc - #592
Number of Iu CS release requests due to abnormal conditions, when the reference FddCell of these calls is located on the drift RNC.
A set of subcounters screened on:
• Sub-Counter #0: Other • Sub-Counter #1: Signalling Only • Sub-Counter #2: CS speech NB or LR AMR
• Sub-Counter #3: CS speech WB AMR • Sub-Counter #4: CS data • Sub-Counter #5: CS Streaming 57.6
• Sub-Counter #6: CS Streaming 14.4 • Sub-Counter #7: Any PS
VS.IuAbnormRelReqPsNrnc - #588
Number of Iu PS release requests due to abnormal conditions, when the reference FddCell of these calls is located on the drift RNC.
A set of subcounters screened on:
• Sub-Counter #1: Signaling Only • Sub-Counter #2: PS Streaming < 64 • Sub-Counter #3: PS Streaming 64
• Sub-Counter #4: PS Streaming 128 • Sub-Counter #5: PS Streaming 256 • Sub-Counter #6: PS Streaming 384
• Sub-Counter #7: TRB on cell FACH • Sub-Counter #8: PS I/B < 64 • Sub-Counter #9: PS I/B 64
• Sub-Counter #10: PS I/B 128 • Sub-Counter #11: PS I/B 256 • Sub-Counter #12: PS I/B 384
• Sub-Counter #13: HSDPA • Sub-Counter #14: xPCH • Sub-Counter #15: Any CS
• Sub-Counter #0: Other type of Call
VS.RabEstablishmentSuccessPerGrantedRabType - #1658
Number of successful RAB establishment per granted RAB type (per RABid and not per procedure).
This counter should also be pegged for RABs successfully allocated for incoming relocations.
DlRbSetId,UlRbSetId,TrafficClass derived screening per granted Rab
• Sub-Counter #0: Other Dl, Ul, Traffic Class combinations
• Sub-Counter #1: Dl and Ul are CS Speech, TC is Conversational
• Sub-Counter #2: Dl and Ul are CSD 64, TC is Conversational
• Sub-Counter #3: Dl and Ul are CS, TC is Streaming
• Sub-Counter #4: Dl is any low rate PS I/B, Ul is any PS I/B, TC is Interative
• Sub-Counter #5: Dl is any low rate PS I/B, Ul is any PS I/B, TC is Background
• Sub-Counter #6: Dl is any high rate PS I/B, Ul is any PS I/B, TC is Interative
• Sub-Counter #7: Dl is any high rate PS I/B, Ul is any PS I/B, TC is Background
• Sub-Counter #8: Dl is any low rate Ps Str and Ul is any PS Str, TC is Streaming
• Sub-Counter #9: Dl is any high rate Ps Str and Ul is any PS Str, TC is Streaming

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 38
VS.IuReleaseCompleteCs - #594
Number of RANAP Iu Release Complete sent by RNC to CN on the Iu interface on the CS domain
Derived AsConf Screening for CS DlAsConfId
Sub-Counter #0: Other
Sub-Counter #1: Signaling Only
Sub-Counter #2: CS speech NB or LR AMR
Sub-Counter #3: CS speech WB AMR
Sub-Counter #4: CS data
Sub-Counter #5: CS Streaming 57.6
Sub-Counter #6: CS Streaming 14.4
Sub-Counter #7: Any PS

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 39
VS.RadioBearerReleaseSuccess - #1647
Number of Radio Bearers released successfully
Source Type of call release mapping
Sub-Counter #0: Other combinations
Sub-Counter #1: CS Speech NB or LR AMR
Sub-Counter #2: CS Speech WB AMR
Sub-Counter #3: CS Data
Sub-Counter #4: CS Streaming
Sub-Counter #5: PS Streaming < 64
Sub-Counter #6: PS Streaming 64
Sub-Counter #7: PS Streaming 128
Sub-Counter #8: PS Streaming 256
Sub-Counter #9: PS Streaming 384
Sub-Counter #10: PS I/B < 64
Sub-Counter #11: PS I/B 64
Sub-Counter #12: PS I/B 128
Sub-Counter #13: PS I/B 256
Sub-Counter #14: PS I/B 384
Sub-Counter #15: HSDPA/R99
Sub-Counter #16: PS I/B or PS Str HSDPA/E-DCH
Sub-Counter #17: TRB on cell FACH

VS.IuReleaseCommandPSWithRAB - #2703
Number of RANAP Iu Release Command messages received by RNC from PS CN, while at least one PS RAB
is still established for the user. Note: this deals with the fact that some CN implementations do not send a
RANAP RAB Assignment Request (No Remaining Rab) following a Pdp Context Deactivation and directly
send an Iu Release Command. This situation does not increment the counters we use in the PS Drop Rate
metrics.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 40
VS.IuReleaseReqCs - #576
Number of RANAP/IU_RELEASE_REQUEST sent by RNC to CoreNetwork CS

A 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 cnx release
Sub-Counter #4: Radio cnx with UE lost
Sub-Counter #5: Abnormal condition with cause TRelocOveral 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 Expiry
Sub-Counter #10: Connection with NodeB lost.
Sub-Counter #11: Release due to UTRAN Generated Reason
Sub-Counter #12: No Remaining RAB
Sub-Counter #13: Failure in the Radio Interface Procedure
Sub-Counter #14: No Resource Available

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 41
A UE in connected state may enter bad radio conditions and run the risk of losing the radio connection.

Since Smartphone’s introduction, it has been noticed that the multi-service RAB call drop rate is significantly
higher than voice-only call drop rate. It is concluded that in such radio conditions if a multi-service call is
(“changed” to) a voice-only call, the risk of call drop would be reduced.
This feature will introduce two major enhancements in the UA08.1 release:
Multi-Service RAB call drop reduction algorithm
Multi-Service RAB call drop reduction on DL TRB RLC error cause

“Vulnerable State” indicates when a UE entered radio conditions that make it liable to drop call. There are
downlink and/or uplink criteria to determine when a UE enters and exits the “Vulnerable State”. Such
criteria are usually performed by measurements.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 42
This chart shows how a UE enters and exits the Vulnerable State

“Vulnerable State” applies to a call with a CS RAB. For a mRAB call, when the CS RAB is released,
“Vulnerable State” is no longer applicable. The measurements are useless and should be released.
Since a single CS RAB shares the same treatment of “Vulnerable State” detection as CS + PS RAB(s), a
single CS RAB is treated as a special case of mRAB.

A call vulnerability to poor radio conditions may be triggered by either UL or DL measurements according to
configurable parameters.
Vulnerability thresholds are configurable per DL service, per UL service and per cell.
Only one measurement is implemented in UL and DL in UA08.1 for vulnerability detection:
The SIR Target measurement for UL (UPlane measurement) jointly with HFI ratio in case of an EDCH
call.
The TxCP measurement for DL (NBAP dedicated measurement): a UE enters the “Vulnerable State” if
either the uplink criteria or the downlink criteria are met. It exits the “Vulnerable State” if all previous
entry conditions are cleared.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 43
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 44
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 45
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 46
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 47
Problem Description
The call is not more active from the user perspective (CS) or degradation is perceived (PS). See the next
clarification between UTRAN and User perception of call drops:
When a CS RAB drops, the e2e CS call will also drop and this service loss is perceived by the user.
When a PS RAB drops, the PS e2e session is not automatically lost. If the SGSN has remaining data
in its buffers for the user, the UE is automatically paged and a new PS RAB may be established.
Then, the e2e throughput decreases due to the RAB re-establishment but there is no service (and
data) loss at user level.
The Network Retainability analysis aims at evaluating the call drop rate trends at network level and at
RNC level based on the RNC PANEL report .
The results should be provided per service (voice, video, PS) and per RNC to facilitate the
troubleshooting.
Problem Detection
The CS Call Drop Rate is higher than the pre-defined QoS Threshold.
The PS Call Drop Rate is higher than the pre-defined QoS Threshold.
Note that for each specific operator, the threshold needs to be adjusted according to the threshold
determination methodology or other methods statistically meaningful.
Note that the CDR is expected to be lower for networks having short voice call duration (less risk of
dropping). For network comparison or different user profile in different areas of the same operator, it can
be interesting to introduce the metric “Number of drops per hour of Voice calls”. For example, one
network can have the best Video Telephony call drop rate but the worst Video Telephony drops per hour
of call.
For PS retainability, the classical drop call metric can be somehow masked by PS call management
procedures and IRM Algorithms. To avoid this problem, another retainability metrics can be used:
Number of drops per minute.
PS DL Transfer before drop (Mbytes).

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 48
Problem Investigation: Use the above chart as a guideline for CS or PS call drop troubleshooting.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 49
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 50
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 51
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 52
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 53
SPU: Mean Sector per User

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 54
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 55
SPU: Mean Sector per User

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 56
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 57
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 58
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.5 Edition 1
Section 1 · Module 5 · Page 59
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 1
This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 2
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 3
This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 4
Page

1 Mobility overview 7
1.1 What to monitor? 8
2 SHO monitoring and troubleshooting 9
2.1 SHO overview 10
2.2 SHO preparation: softer HO-RL addition - Counters 11
2.3 SHO preparation: softer HO–RL addition - Metrics 13
2.4 SHO preparation: soft HO-RL addition - Counters 14
2.5 SHO preparation: soft HO-RL addition - metrics 16
2.6 SHO execution: active set update - counters 17
2.7 SHO execution: metrics 18
2.8 Monitor SPU metric 19
2.9 Correlate with other metrics 20
3 3G-2G HHO monitoring 21
3.1 3G-2G CS handover success: counters 22
3.2 3G-2G global CS HHO success rate 23
3.3 3G-2G CS handover preparation success: counters 24
3.4 3G-2G CS HO preparation success 25
3.5 3G-2G CS handover preparation failure: counters 26
3.6 3G-2G CS HO preparation failure rate 27
3.7 3G-2G CS handover execution success: counters 28
3.8 3G-2G CS HO execution success rate 29
3.9 3G-2G CS handover execution failure: counters 30
3.10 3G-2G CS handover: cell counter tree (rescue case) 31
3.11 3G-2G CS HO execution failure rate (reversion to 3G) 32
3.12 3G-2G CS HO execution failure rate (call drop) 33
4 3G-3G HHO monitoring 34
4.1 3G-3G HHO: interRNC no Iur - Preparation success - Counters 35
4.2 3G-3G HHO: interRNC no Iur - Preparation failure - Counters 36
4.3 3G-3G HHO: interRNC no Iur - Preparation success rate 37
4.4 3G-3G HHO: interRNC no Iur - Execution success - Counters 38
4.5 3G-3G HHO: interRNC no Iur - Execution success rate 39
4.6 3G-3G inter-freq HHO: intra+inter RNC with Iur - Success 40
4.7 3G-3G inter-freq HHO: intra+inter RNC with Iur - Rate 41
4.8 3G-3G inter-frequency HHO: IntraRNC - Success - Counters 42
4.9 3G-3G inter-frequency HHO: IntraRNC- Failure - Counters 43
4.10 3G-3G inter - Frequency HHO - IntraRNC - Failure rate 44
5 3G-2G HHO analysis & troubleshooting 45
5.1 CS 3G-2G mobility analysis & troubleshooting 46
5.2 3G-2G CS HHO preparation 47
5.3 3G-2G CS HHO execution 48
5.4 Actions to improve the preparation phase 50
5.5 Actions to improve the execution phase 51

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 5
This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 6
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 7
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 8
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 9
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 10
VS.RadioLinkAdditionRequest - #55
Number of internal events that would lead to a radio link addition request.
A set of sub-counters screened on: Target type of call for Radio Link Reconfiguration
Sub-Counter #0: Other
Sub-Counter #1: Signaling Only
Sub-Counter #2: CS speech
Sub-Counter #3: CS Speech + PS DCH
Sub-Counter #4: CS Speech + HSDPA
Sub-Counter #5: CS Speech + PS DCH + PS HSDPA
Sub-Counter #6: CS Speech + PS DCH + PS DCH
Sub-Counter #7: CS Data
Sub-Counter #8: CS data + PS DCH
Sub-Counter #9: Cs Data + PS HSDPA
Sub-Counter #10: CS streaming
Sub-Counter #11: PS DCH DL / DCH UL
Sub-Counter #12: PS HSDPA DL / E-DCH UL
Sub-Counter #13: PS HSDPA DL / DCH UL
Sub-Counter #14: PS HSDPA DL / DCH UL + E-DCH UL
Sub-Counter #15: PS DCH + PS DCH
Sub-Counter #16: PS DCH + PS HSDPA
VS.RadioLinkAdditionSuccess - #49
Number of radio links successfully added from an NBAP point of view, screened by Downlink Access Stratum configuration.
Screening: same as for #55
VS.RadioLinkAdditionUnsuccess - #39
Number of radio link reconfiguration preparation failures
Sub-Counter #0: RADIO_LINK_ADDITION_FAILURE (any other causes than the ones of screenings #4 & #7)
Sub-Counter #1: Timeout
Sub-Counter #2: Rrm refusal
Sub-Counter #3: INode refusal
Sub-Counter #4: NodeB (CEM) lack of L1 resources
Sub-Counter #5: Lack of Transport Identifier (CID or UDP Port) on the Iub
Sub-Counter #6: Lack of bandwidth on the Iub
Sub-Counter #7: Iub Layer Congestion

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 11
VS.RadioLinkAdditionUnsuccess #39
Number of unsuccessfull radio link setup

A set of sub-counters screened on:


Sub-Counter #0: RADIO_LINK_ADDITION_FAILURE (any other causes than the ones of screenings #4
& #7)
Sub-Counter #1: Timeout
Sub-Counter #2: RRM refusal
Sub-Counter #3: INode refusal
Sub-Counter #4: NodeB (CEM) lack of L1 resources
Sub-Counter #5: Lack of Transport Identifier (CID or UDP Port) on the Iub
Sub-Counter #6: Lack of bandwidth on the Iub
Sub-Counter #7: Iub Layer Congestion

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 12
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 13
VS.RadioLinkSetupRequest - #54
Number of internal events that would lead to a radio link setup request
A set of subcounters screened on: Target type of call for Radio Link Reconfiguration
Sub-Counter #0: Other
Sub-Counter #1: Signaling Only
Sub-Counter #2: CS speech
Sub-Counter #3: CS Speech + PS DCH
Sub-Counter #4: CS Speech + HSDPA
Sub-Counter #5: CS Speech + PS DCH + PS HSDPA
Sub-Counter #6: CS Speech + PS DCH + PS DCH
Sub-Counter #7: CS Data
Sub-Counter #8: CS data + PS DCH
Sub-Counter #9: Cs Data + PS HSDPA
Sub-Counter #10: CS streaming
Sub-Counter #11: PS DCH DL / DCH UL
ub-Counter #12: PS HSDPA DL / E-DCH UL
Sub-Counter #13: PS HSDPA DL / DCH UL
Sub-Counter #14: PS HSDPA DL / DCH UL + E-DCH UL
Sub-Counter #15: PS DCH + PS DCH
Sub-Counter #16: PS DCH + PS HSDPA
VS.RadioLinkSetupSuccess - #48
Number of radio links successfully set up from an NBAP point of view, screened by Downlink Access Stratum
configuration. Screening: same as for #54
VS.RadioLinkSetupUnsuccess - #38
Number of unsuccessful radio link setups
Sub-Counter #0: RADIO_LINK_SETUP_FAILURE
Sub-Counter #1: Timeout
Sub-Counter #2: Rrm refusal
Sub-Counter #3: Iub Layer Congestion
Sub-Counter #4: NodeB (CEM) lack of L1 resources
Sub-Counter #5: Lack of Transport Identifier (CID or UDP Port) on the Iub
Sub-Counter #6: Lack of bandwidth on the Iub
Sub-Counter #7: INode refusal
Sub-Counter #8: Multi-cell Operation Not Available
Sub-Counter #9: TMU internal resources exhausted, e.g. context pool, timer pool, etc. exhausted

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 14
VS.RadioLinkSetupUnsuccess - #38
Number of unsuccessful radio link setups
Sub-Counter #0: RADIO_LINK_SETUP_FAILURE
Sub-Counter #1: Timeout
Sub-Counter #2: Rrm refusal
Sub-Counter #3: Iub Layer Congestion
Sub-Counter #4: NodeB (CEM) lack of L1 resources
Sub-Counter #5: Lack of Transport Identifier (CID or UDP Port) on the Iub
Sub-Counter #6: Lack of bandwidth on the Iub
Sub-Counter #7: INode refusal
Sub-Counter #8: Multi-cell Operation Not Available
Sub-Counter #9: TMU internal resources exhausted, e.g. context pool, timer pool, etc. exhausted

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 15
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 16
VS.RrcActiveSetUpdateCompleteProcedure #415
This measurement provides the number of successful RRC Active Set Update procedures, for which the cell
is 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 an
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.
Screenings:
0: RRC ACTIVE SET UPDATE FAILURE reception
1: Time-out

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 17
VS.UeWithNRadioLinksEstCellsBts - #25
Distribution of the number of mobiles having N radio links in their Active Set
A set of sub-counters screened on: Number of radio links
Sub-Counter #0: 1 Radio Link
Sub-Counter #1: 2 RLs (Reference Cell + 1 RL on the same BTS)
Sub-Counter #2: 2 RLs (Reference Cell + 1 RL on another BTS)
Sub-Counter #3: 3 RLs (Reference Cell + 2 RLs on the same BTS)
Sub-Counter #4: 3 RLs (Reference Cell + 1 RL on the same BTS + 1 RL on another BTS)
Sub-Counter #5: 3 RLs (Reference Cell + 2 RLs on another BTS)
Sub-Counter #6: 4 RLs (Reference Cell + 2 RLs on the same BTS + 1 RL on another BTS)
Sub-Counter #7: 4 RLs (Reference Cell + 1 RL on the same BTS + 2 RLs on another BTS)
Sub-Counter #8: 4 RLs (Reference Cell + 3 RLs on another BTS)
Sub-Counter #9: 5 RLs (Reference Cell + 2 RLs on the same BTS + 2 RLs on another BTS)
Sub-Counter #10: 5 RLs (Reference Cell + 1 RL on the same BTS + 3 RLs on another BTS)
Sub-Counter #11: 5 RLs (Reference Cell + 4 RLs on another BTS)
Sub-Counter #12: 6 RLs or more (Reference Cell + 2 RLs on the same BTS + 3 or more RLs on
another BTS)
Sub-Counter #13: 6 RLs or more (Reference Cell + 1 RL on the same BTS + 4 or more RLs on another
BTS)
Sub-Counter #14: 6 RLs or more (Reference Cell + 5 or more RLs on another BTS)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 18
Issue characterization:
Can it affect some/all services (CS, PS, etc.)
Some/all Network elements, Top N cells
Some/all periods of time, since when
Some failure causes
After certain event (upgrade, feature activation, configuration changes in Iur, reparentings?)
(*) New counters

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 19
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 20
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 21
VS.3gto2gHoDetectionFromFddcell #164:
This measurement provides the number of RRM decisions for a 3G-to-2G handover performed by an 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.
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)
Sub-Counter #5: No resource available PS (CAC)

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 for some cause values.
Screening: per Iu Release Command cause
0: Normal end of communication (3GPP RANAP cause 83)
1: Successful relocation
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)

IRATHO.SuccOutCS - #1841
Successful outgoing CS 3G to 2G handover (CS Inter-RAT handover)
Sub-Counter #0: Rescue CS
Sub-Counter #1: Service CS
Sub-Counter #2: No resource available CS (CAC failure)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 22
VS.3gto2gOutHoSuccessNrnc - #168
Number of successful outgoing Hard Handovers from 3G to 2G when the reference cell is on the drift
RNC.
A set of sub-counters screened on: HO reason for which a 3G-to-2G Relocation was initiated.
Sub-Counter #0: rescue CS
Sub-Counter #1: rescue PS
Sub-Counter #2: No resource available CS (CAC failure)
Sub-Counter #3: No resource available PS (CAC failure)

VS.3gto2gHoDetectionFromFddcellNeighbRnc - #165
Number of RRM decisions for a 3G-to-2G handover performed by an RNC, screened by neighboring RNC
grouping reference cells from which the UEs have left the 3G network. This measurement considers both
CS and PS handovers.
A set of sub-counters screened on: Reason for initiating the 3G-to-2G HO
Sub-Counter #0: Rescue CS
Sub-Counter #1: Rescue PS
Sub-Counter #2: No resource available (CAC failure)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 23
#154 VS.RrcHoFromUtranCmdTrigByEcNo
Number of Inter-RAT handover from UTRAN command sent by RNC with a reference cell for which the RNC
is serving and the handover has been initiated because of Ec/No:
Sub-Counter #0: rescue CS

#156 VS.RrcHoFromUtranCmdTrigByRscp
Number of Inter-RAT handover from UTRAN command sent by RNC with a reference cell for which the RNC
is serving, and the handover has been initiated because of RSCP criteria:
Sub-Counter #0: rescue CS

#158 VS.RrcHoFromUtranCmdTrigRnc
Number of Inter-RAT handover from UTRAN command sent by RNC with a reference cell for which the RNC
is serving, and the handover has been initiated because of CAC failure events or Service events, NOT
because of Alarm radio condition.
Sub-Counter #0: service CS
Sub-Counter #1: No resource available (CAC failure)

#556 VS.IuRelocationRequired
A set of sub-counters screened on: Per type of core and type of relocation
Sub-Counter #0: 3G-3G CS, UE involved
Sub-Counter #1: 3G-3G PS, UE involved
Sub-Counter #2: 3G-2G CS
Sub-Counter #3: 3G-3G CS, UE not involved
Sub-Counter #4: 3G-3G PS, UE not involved

#557 VS.IuRelocationCommands
Same screenings as for #556

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 24
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 25
TRELOCprep = Timer RELOcation preparation

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 26
VS.IuRelocationCmdFailuresCs - #558 is a RNC counter
Number of relocation preparation failures on CS Iu interface
A set of sub-counters screened on: IU Relocation command failure causes
Sub-Counter #4: 3G to 2G UE involved. Relocation timeout. 'Trelocallocexpiry' (3GPP 25.413)
Sub-Counter #5: 3G to 2G UE involved. Relocation failure or relocation not supported in target system
Sub-Counter #6: 3G to 2G UE involved. 'Unable to Establish During Relocation' (3GPP 25.413)
Sub-Counter #7: 3G to 2G UE involved. Other relocation failure

IRATHO.FailRelocPrepOutCS - #1845 : is a Reference Cell counter


Failed relocation preparations for UMTS to GSM handover on the reference cell from the network point of
view per failure cause
Sub-Counter #0: Relocation Cancelled (10)
Sub-Counter #1: Requested Ciphering and/or Integrity Protection Algorithms not Supported (12)
Sub-Counter #2: Relocation Failure in Target CN/RNC or Target system (29)
Sub-Counter #3: Relocation not supported in Target RNC or Target System (44)
Sub-Counter #4: Relocation Target not allowed (50)
Sub-Counter #5: No Radio Resources Available in Target Cell (53)
Sub-Counter #6: Traffic Load in The Target Cell Higher Than in the Source Cell (57)
Sub-Counter #7: Abstract Syntax Error (Reject) (100)
Sub-Counter #8: O&M Intervention (113)
Sub-Counter #9: No Resource Available (114)
Sub-Counter #10: Unspecified Failure (115)
Sub-Counter #11: Expiry of the timer TRELOCprep

IRATHO.AttRelocPrepOutCS - #1839 : is a Reference Cell counter


Attempted relocation preparations for CS UMTS to GSM handover (CS inter-RAT Handover Attempt)

IRATHO.FailRelocPrepOutCS.Sum - #1843 : is a Reference Cell counter


Sum of all kinds of failed relocation preparations for UMTS to GSM handover on the reference cell from the
network point of view

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 27
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 28
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 29
VS.RrcHoFromUtranFailure - #160
Number of RRC HANDOVERs FROM UTRAN FAILURE messages (3G to 2G handover for CS or CS+PS)
received by an RNC, acting as serving RNC, for each cell controlled by this RNC.
A set of sub-counters screened on: HO reason for which the RRC / HANDOVER_FROM_UTRAN_COMMAND
message is sent:
Sub-Counter #0: rescue CS
Sub-Counter #1: service CS
Sub-Counter #2: No resource available (CAC failure)

VS.RrcHoFromUtranFailureNeighbRnc - #161
Number of RRC HANDOVER FROM UTRAN FAILURE (3G to 2G handover for CS or CS+PS) messages
received by an RNC acting as serving, for each neighboring RNC.
A set of sub-counters screened on: HO reason for which the RRC / HANDOVER_FROM_UTRAN_COMMAND
message is sent:
Sub-Counter #0: rescue CS
Sub-Counter #1: No resource available (CAC failure)

VS.IuReleaseReqCs - #576
Number of RANAP/IU_RELEASE_REQUEST sent by RNC to Core Network CS
Sub-Counter #5: Abnormal condition with cause TRelocOveral expiry

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 30
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 31
2G Synchronization failure and reversion to 3G
If the UE cannot synchronize with the 2G target network during the 3G-2G HHO execution phase, the UE
sends the HO from the UTRAN Failure message to the RNC to come back to the 3G network.
The CS 3G2G HHO Execution Failure Rate metric is proposed to evaluate the 2G target cell synchronization
failure.

Notes:
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)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 32
1. The number of calls lost during a 3G-2G HO is:
Number of HOs from UTRAN command sent to UE
Number of HOs from UTRAN failure received from UE
Number of HO successes 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.

Call lost:
If the RNC does not receive the HO from the UTRAN failure RRC message from the UE or the Iu release
command with the cause “successful 3g2g relocation” from the CN, there is failure on3G side (the call is
dropped during the 3G-2G HHO).
The CS 3G2G HHO Execution Failure Rate because of 3G Reason metric is proposed to evaluate the calls
dropped during the 3G-2G CS HHO.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 33
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 34
#556 VS.IuRelocationRequired
A set of sub-counters screened on: Per type of core and type of relocation
Sub-Counter #0: 3G-3G CS, UE involved
Sub-Counter #1: 3G-3G PS, UE involved
Sub-Counter #2: 3G-2G CS
Sub-Counter #3: 3G-3G CS, UE not involved
Sub-Counter #4: 3G-3G PS, UE not involved

#557 VS.IuRelocationCommands
Same screenings as for #556

VS.IuRelocationRequests - #535
Number of relocation requests at Iu interface
A set of sub-counters screened on: Per type of relocation and CN Domain
Sub-Counter #0: CS 3G-3G Relocation
Sub-Counter #1: PS 3G-3G Relocation
Sub-Counter #2: CS 2G-3G Relocation
Sub-Counter #3: CS 3G-3G Relocation, UE not involved
Sub-Counter #4: PS 3G-3G Relocation, UE not involved
Sub-Counter #5: PS 4G-3G Relocation, UE involved

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 35
VS.IuRelocationCmdFailuresCs - #558
Number of relocation preparation failures on CS Iu interface
A set of sub-counters screened on: IU Relocation command failure causes
Sub-Counter #0: 3G to 3G UE involved. Relocation timeout
Sub-Counter #1: 3G to 3G UE involved. Relocation failure in target system
Sub-Counter #2: 3G to 3G UE involved. Relocation unable to establish
Sub-Counter #3: 3G to 3G UE involved. Other relocation failure
Sub-Counter #4: 3G to 2G UE involved. Relocation timeout. 'Trelocallocexpiry' (3GPP 25.413)
Sub-Counter #5: 3G to 2G UE involved. Relocation failure or relocation not supported in target system
Sub-Counter #6: 3G to 2G UE involved. 'Unable to Establish During Relocation' (3GPP 25.413)
Sub-Counter #7: 3G to 2G UE involved. Other relocation failure
Sub-Counter #8: 3G to 3G UE not involved. Relocation timeout
Sub-Counter #9: 3G to 3G UE not involved. Other relocation failure

IuRelocationRequestFailuresPs - #537
Number of relocation request failures on PS Iu interface
Sub-Counter #0: 3G-3G UE involved. Relocation time out
Sub-Counter #1: 3G-3G UE involved. Relocation failure in target system
Sub-Counter #2: 3G-3G UE involved. Relocation unable to establish
Sub-Counter #3: 3G-3G UE involved. Other relocation failure
Sub-Counter #4: 3G-3G UE involved. RRC Context CAC. Pegged when CAC fails for then entering PS reloc.
Sub-Counter #5: 3G-3G UE involved. Unavailable IU CNX context resources. Pegged when the IU
connection contexts are exhausted for the entering PS reloc.
Sub-Counter #6: 3G-3G UE not involved. Relocation timeout (TRelocAlloc).
Sub-Counter #7: 3G-3G UE not involved. Relocation failure in target system.
Sub-Counter #8: 3G-3G UE not involved. Unavailable IU CNX context resources. Pegged when the IU
connection contexts are exhausted for the entering PS reloc.
Sub-Counter #9: 3G-3G UE not involved. Other relocation failure
Sub-Counter #10: 4G-3G UE involved. Relocation failure in target system
Sub-Counter #11: 4G-3G UE involved. Relocation unable to establish
Sub-Counter #12: 4G-3G UE involved. RAB matching failure
Sub-Counter #13: 4G-3G UE involved. Other relocation failure

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 36
Due to the counters implementation, the 3G-3G HHO preparation success rate is available at RNC level only for Source
side and at Cell level for Target side.

VS.IuRelocationRequestFailuresCs - #536
Number of relocation request failures on CS Iu interface
Sub-Counter #0: 3G-3G UE involved. Relocation timeout
Sub-Counter #1: 3G-3G UE involved. Relocation failure in target system
Sub-Counter #2: 3G-3G UE involved. Relocation unable to establish
Sub-Counter #3: 3G-3G UE involved. Other relocation failure
Sub-Counter #4: 2G-3G Relocation timeout
Sub-Counter #5: 2G-3G Relocation failure in target system
Sub-Counter #6: 2G-3G Relocation unable to establish
Sub-Counter #7: 2G-3G Other relocation failure
Sub-Counter #8:3G-3G UE involved. RRC Context CAC. Pegged when CAC fails for the entering CS
reloc.
Sub-Counter #9: 2G-3G RRC Context CAC. Pegged when CAC fails for the entering CS reloc.
Sub-Counter #10:3G-3G UE involved. Unavailable IU CNX context resources. Pegged when the IU
connection contexts are exhausted for the entering CS reloc.
Sub-Counter #11: 2G-3G Unavailable IU CNX context resources. Pegged when the IU connection
contexts are exhausted for the entering CS reloc.
Sub-Counter #12: 3G-3G UE not involved. Relocation timeout (TRelocAlloc).
Sub-Counter #13: 3G-3G UE not involved. Relocation failure in target system.
Sub-Counter #14: 3G-3G UE not involved. Other relocation failure.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 37
VS.IuRelocationCompletes - #569
Number of relocation completes at Iu interface
A set of sub-counters screened on: Per type of relocation and CN domain
Sub-Counter #0: 3G-3G CS
Sub-Counter #1: 3G-3G PS
Sub-Counter #2: 2G-3G CS
Sub-Counter #3: 4G-3G PS

VS.IuReleaseCommandCs - #505
Number of RANAP/IU_RELEASE_COMMAND messages received by RNC from CS domain.
Sub-Counter #9: Successful 3G-3G relocation

VS.IuReleaseCommandPsNRnc - #553
Number of RANAP/IU_RELEASE_COMMAND messages received by RNC on the IU-PS interface when the reference cell
is located on a Drift RNC.
Sub-Counter #9: Successful 3G-3G relocation

VS.IuReleaseCommandPs - #506
Number of RANAP/IU_RELEASE_COMMAND messages received by RNC from PS domain.
Sub-Counter #9: Successful 3G-3G relocation

VS.IuReleaseCommandCsNRnc - #552
Number of RANAP/IU_RELEASE_COMMAND messages received by RNC on the IU-CS interface when the reference cell
is located on a Drift RNC.
Sub-Counter #9: Successful 3G-3G relocation

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 38
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 39
VS.OutGoInterFreqHoAtt - #174
Number of hard handovers attempted from this cell to another inter-frequency cell located either in the
same RNC or in a neighboring RNC (a Iur link is set up towards the inter-frequency cell).
Sub-Counter #0: Rescue
Sub-Counter #1: Service
Sub-Counter #2: No resource available (CAC failure)

VS. IncomInterFreqHoAtt - #176


Number of hard handovers attempted to this cell from another inter-frequency cell located in the same RNC
(an Iur link is set up towards the inter-frequency cell).
same screenings as #174

VS.OutGoInterFreqHoSuc - #175
Number of successful hard handovers from this cell located on the serving RNC to another inter-frequency
cell located either in the same RNC or in a neighboring RNC (an Iur link is set up towards the inter-
frequency cell).
same screenings as #174

VS.IncomInterFreqHoSuc - #177
Number of successful hard handovers to this cell located on the serving RNC from another inter-frequency
cell located in the same RNC (an Iur link is set up towards the inter-frequency cell).
same screenings as #174

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 40
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 41
VS.IntraRncOutInterFreqHoAttempt - #170
Number of Intra-RNC outgoing Hard Handovers attempted from this cell to another cell using another
frequency in the same RNC
A set of sub-counters screened on: Reason for initiating the Intra-RNC HHO
Sub-Counter #0: HO without CM measurements
Sub-Counter #1: HO with CM measurements
Sub-Counter #2: HSDPA capable mobile to HSDPA layer
Sub-Counter #3: HSDPA capable mobile to non-HSDPA layer
Sub-Counter #4: Non-HSDPA capable mobile to non-HSDPA layer

VS.IntraRncIncInterFreqHoAttempt - #172
Number of Intra-RNC Hard Handovers attempted to this cell from another cell in the same RNC on a
different frequency.
A set of sub-counters screened on: Reason for initiating the Intra RNC HHO
Sub-Counter #0: HO with CM measurements Inter-Band
Sub-Counter #1: HO with CM measurements
Sub-Counter #2: HSDPA capable mobile to HSDPA layer
Sub-Counter #3: HSDPA capable mobile to non-HSDPA layer
Sub-Counter #4: Non-HSDPA capable mobile to non-HSDPA layer

Inter-freq inter-Band HHO are counted in sub-counters s0, intra-band in sub-counters s1.
Sub-counters s2, s3 and s4 are pegged when RRC Traffic Segmentation is performed.

Incremented for both CS and PS cases.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 42
VS.IntraRncOutInterFreqHoFail - #171
Number of Intra-RNC Hard Handovers attempted from this cell to another cell using another frequency in
the same RNC that failed to complete succesfully.
A set of sub-counters screened on: Failure reason for Intra RNC HHO
Sub-Counter #0: HO with CM measurement Inter-Band
Sub-Counter #1: HO with measurements Node B failure
Sub-Counter #2: HO with measurements Failure on RRC
Sub-Counter #3: HO with CM measurement Not enough resources
Sub-Counter #4: HO with CM measurement Node B failure
Sub-Counter #5: HO with CM measurement Failure on RRC

VS.IntraRncIncInterFreqHoFail - #173
Number of Intra-RNC Hard Handovers attempted to this cell from another using another frequency
in the same RNC that failed to complete succesfully.
A set of sub-counters screened on: Failure reason for Intra RNC HHO
Sub-Counter #0: HO with CM measurement Inter-Band
Sub-Counter #1: HO with measurements Node B failure
Sub-Counter #2: HO with measurements Failure on RRC
Sub-Counter #3: HO with CM measurement Not enough resources
Sub-Counter #4: HO with CM measurement Node B failure
Sub-Counter #5: HO with CM measurement Failure on RRC

Sub-counters s1 and s2 are always equal to zero.


Inter-freq intra-Band HHO failures are counted in sub-counters s3, s4 and s5.
Inter-freq inter-Band HHO failures are all counted in sub-counters s0.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 43
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 44
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 45
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 46
#558
VS.IuRelocationCmdFailuresCs
Sub-Counter #0: 3G to 3G UE involved. Relocation timeout
Sub-Counter #1: 3G to 3G UE involved. Relocation failure in target system
Sub-Counter #2: 3G to 3G UE involved. Relocation unable to establish
Sub-Counter #3: 3G to 3G UE involved. Other relocation failure
Sub-Counter #4: 3G to 2G UE involved. Relocation timeout. 'Trelocallocexpiry' (3GPP 25.413)
Sub-Counter #5: 3G to 2G UE involved. Relocation failure or relocation not supported in target system
Sub-Counter #6: 3G to 2G UE involved. 'Unable to Establish During Relocation' (3GPP 25.413)
Sub-Counter #7: 3G to 2G UE involved. Other relocation failure
Sub-Counter #8: 3G to 3G UE not involved. Relocation timeout
Sub-Counter #9: 3G to 3G UE not involved. Other relocation failure

#1845
IRATHO.FailRelocPrepOutCS
Sub-Counter #0: Relocation Cancelled (10)
Sub-Counter #1: Requested Ciphering and/or Integrity Protection Algorithms not Supported (12)
Sub-Counter #2: Relocation Failure in Target CN/RNC or Target system (29)
Sub-Counter #3: Relocation not supported in Target RNC or Target System (44)
Sub-Counter #4: Relocation Target not allowed (50)
Sub-Counter #5: No Radio Resources Available in Target Cell (53)
Sub-Counter #6: Traffic Load in The Target Cell Higher Than in the Source Cell (57)
Sub-Counter #7: Abstract Syntax Error (Reject) (100)
Sub-Counter #8: O&M Intervention (113)
Sub-Counter #9: No Resource Available (114)
Sub-Counter #10: Unspecified Failure (115)
Sub-Counter #11: Expiry of the timer TRELOCprep

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 47
The 1st step is to identify the days and the RNC’s with too bad Global CS 3G-2G HHO performances.
This analysis can be completed with CTg in the cell that are selected for investigation through counter
metrics and can be triggered for further investigations.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 48
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 49
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 50
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 51
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.6 Edition 1
Section 1 · Module 6 · Page 52
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 1
This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 2
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 3
This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 4
Page

1 Network quality overview 7


1.1 Introduction 8
2 Network quality monitoring 10
2.1 Quality monitoring & troubleshooting 11
2.2 BLER metrics 12
2.2.1 Uplink BLER per PS RB Bit rate 13
2.3 Throughput metrics 14
3 RF quality analysis 15
3.1 DL quality 16
3.2 DL level 18
3.3 UE distance 20
3.4 UL RSSI 21
3.5 UL cell load 23
3.6 RF conditions analysis 25
3.6.1 DL RF analysis 26
3.6.2 UL RF analysis 27

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 5
This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 6
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 7
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 8
When a degradation of quality has been identified, the next step is to define more precisely:
The affected service,
The affected network elements or cell zone (xCEM, iCEM, Frequency 1, Frequency 2, etc.),
The affected period of time,
The events occurred on the network (feature activation, parameters change, etc.).
In case of a quality issue, it could also be useful to check in parallel:
RF conditions,
IRM scheduling,
Always-on.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 9
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 10
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 11
VS.IuDlAmrFrmFqc - #1505
Number of AMR frames received on Iu by FQC
Sub-Counter #0: Frame good
Sub-Counter #1: Frame bad
Sub-Counter #2: Frame bad due to radio
VS.DdUlAmrABtGoodFrm - #1506
Number of AMR frames with Class A bits Transport Block received with CRCi = 0
Sub-Counter #0: 12.2
Sub-Counter #1: 10.2
Sub-Counter #2: 7.95
Sub-Counter #3: 7.4
Sub-Counter #4: 6.7
Sub-Counter #5: 5.9
Sub-Counter #6: 5.15
Sub-Counter #7: 4.75
VS.DdUlAmrABtBadFrm - #1507
Number of AMR frames with Class A bits Transport Block received with CRCi = 1
Same screening as for #1506
VS.DedicatedDownlinkPdusRlcReferenceCell - #1558
Number of RLC PDUs sent on downlink for the reference cell
• Sub-Counter #0: Other Dl
• Sub-Counter #1: Any SRB
• Sub-Counter #2: CS speech
• Sub-Counter #3: CS 64 conversational • Sub-Counter #4: CS streaming
• Sub-Counter #5: PS HSDPA • Sub-Counter #6: PS Str 128 • Sub-Counter #7: PS Str 256
• Sub-Counter #8: PS Str 384 • Sub-Counter #9: PS Str Other • Sub-Counter #10: PS I/B 8kbps
• Sub-Counter #11: PS I/B 16kbps • Sub-Counter #12: PS I/B 32kbps • Sub-Counter #13: PS I/B 64kbps
• Sub-Counter #14: PS I/B 128kbps • Sub-Counter #15: PS I/B 256kbps • Sub-Counter #16: PS I/B 384kbps
VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell - #1559
Number of downlink RLC PDUs retransmitted on dedicated channels on the reference cell. This counter is only pegged
for RLC AM bearer (so only for PS). This is incremented for the current RAB and any RLC PDU (Q01371476). Same
screening as for #1558 but s1, s2, s3 and s4 are always zero because the RLC TM mode is used.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 12
VS.DedicatedUplinkBadPdusRlcRefCell - #1542
Number of bad PDUs sent on Dedicated uplink for the reference cell.
Uplink Traffic Counter Screenings
Sub-Counter #0: Other Ul
Sub-Counter #1: Any SRB
Sub-Counter #2: CS speech
Sub-Counter #3: CS 64 conversational
Sub-Counter #4: CS streaming
Sub-Counter #5: PS Str 16
Sub-Counter #6: PS Str 64
Sub-Counter #7: PS Str Other
Sub-Counter #8: PS I/B 8kbps
Sub-Counter #9: PS I/B 16kbps
Sub-Counter #10: PS I/B 32kbps
Sub-Counter #11: PS I/B 64kbps
Sub-Counter #12: PS I/B 128kbps
Sub-Counter #13: PS I/B 384kbps
Sub-Counter #14: PS I/B HSUPA
Sub-Counter #15: PS Str HSUPA
VS.DedicatedUplinkPdusRlcReferenceCell - #1557
Number of RLC PDUs sent on uplink for the reference cell.
Reception by the RNC of an RLC PDU with correct CRCI on an uplink dedicated channel
Same screenings as for #1542

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 13
VS.DedicatedDownlinkKbytesRlc - #1544
Number of kbytes of SDU payload sent on dedicated downlink RLCs (from RLC counter:
DCH_DL_SDU_TRAFFIC)
VS.DlAsConfIdAvgNbrEstablished - #1666
indicates an average of the number of DlAsConfIds established per iRNC, based on time average
over a collection period

VS.DedicatedUplinkKbytesRlc - #1543 Similar to #1544 but for the Uplink

VS.UlAsConfIdAvgNbrEstablished - #1667 Similar to #1666 but for the Uplink

VS.DedicatedDownlinkKbytesRlcReferenceCell - #1556
Number of kbytes of SDU sent on downlink for the reference cell
VS.DedicatedDownlinkActivityRlcRefCell - #1566
Time that RAB is actively transmitting data in the downlink

VS.DedicatedUplinkKbytesRlcReferenceCell - #1555 Similar to #1556 but for the Uplink

VS.DedicatedUplinkActivityRlcRefCell - #1567 Similar to #1526 but for the Uplink

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 14
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 15
VS.IrmcacDistributionEcNO - #1043: This counter provides the distribution of Ec/N0 measurements
received per range from UEs with 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

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 16
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 17
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 sub-counters 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

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 18
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 19
VS.DistPropDelayPerRange - #1041: Distribution of propagation delays, as expressed in the
3GPP25.433 Nbap RL Setup Request (when Propagation Delay IE is present)
A set of sub-counters screened on: Propagation Delay in terms of chips
Sub-Counter #0: IE in [0..1] (Cell size < 468 m)
Sub-Counter #1: IE in [2] (468 m<= Cell size < 702 m)
Sub-Counter #2: IE in [3..4] (702 m <= Cell size < 1171m)
Sub-Counter #3: IE in [5] (1171 m <= Cell size < 1405 m)
Sub-Counter #4: IE in [6..8] (1405 m <= Cell size < 2108 m)
Sub-Counter #5: IE in [9..16] (2108 m <= Cell size < 3982 m)
Sub-Counter #6: IE in [17..42] (3982 m <= Cell size < 10072 m)
Sub-Counter #7: IE in [43..255] (Cell size equal to or above 10072 m)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 20
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)

The Node B estimates the total UL Radio Load as the linear average between the UL Rx Signal Level
measure at bit Main and Diversity antennae.
According to typical values of Thermal Noise and Noise Factor of the Node B and Rx aerial chain, this
indicator should be not less that –112 dBm. The typical minimum value should be between –106 dBm and –
105 dBm.
As the maximum allowed Rot is driven by a parameter lower than 8 dB, the maximum value of UL RSSI
should not be over –98 dBm = -106 dBm + 8 dB
The value of this metric should be between -109 dBm and -102 dBm typically.

Max and Min values can also be considered for radio problem investigation.
Delta between Main and Div UL RSSI measurement is also to be considered.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 21
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 22
VS.CellULLoad (#10211)
The Node B computes this indicator from the estimation of the RoT which is equal to the difference
between the total UL RSSI and the RTWPref.
Distribution according to load type:
Total load
eDCH/HSUPA load
Then the UL Cell Load is UL Cell Load = 1 – 10-(RoT/10)
Noise Rise vs. UL load
20

18

16

14
Noise Rise (dB) = RoT

12

10

0
0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1
UL load (%)
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 23
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 24
To evaluate the radio conditions when the calls are established, the following indicators could be correlated:
RRC Connection Success Rate = RRC.SuccConnEstab[RRCcause]/RRC.AttConnEstab[RRCcause]

The RRC performance of Terminating calls can be better than Originating since Paging decoding has been
performed beforehand.

Ratio of RRC Connection Setup repetitions = VS.RrcConnectionSetup/RRC.AttConnEstab


If there is a high repetition rate, it means that the call is being set up in bad radio conditions (lack or
coverage or interfered area).
Ratio of RRC Quick Repeat usage = (VS.RrcConnectionSetup.InitialWithQuickRepeat +
VS.RrcConnectionSetup.FirstRepetitionWithQuickRepeat) / VS.RrcConnectionSetup
If Quick Repeat sub-counter is pegged, it means that the call is being set up at bad Ec/Io.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 25
Two metrics have been tested in order to detect cells with DL radio issues. These metrics can be used
combined with accessibility or call drop ratio:
Percentage of bad Ec/No
Percentage of bad RSCP
These metrics provide good indications of potential "bad" area. Call drops and even call setup failures have
been correlated with bad RSCP or Ec/No levels.
These new metrics are strongly recommended for troubleshooting of call drop and accessibility. The
limitation is that if FET is activated, samples cannot be enough to get meaningful statistics, but those
metrics can be correlated with accessibility metrics that give an idea of radio issues: i.e. metrics related to
RRC phase like:
RRC Connection Success Rate (by RRC cause)
Ratio of RRC Connection Setup repetitions
Ratio of RRC Quick Repeat usage

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 26
Threshold Low RSSI
If the RSSI measurement is low, the Node B assumes that there is a low level of noise (global signal
received, noise + other users) and then the power in uplink requested to the mobile will be very low, and
this can lead to the mobile to never be able to reach the network.
All cells that are seen with an RSSI value constantly below -112 dBm are to be considered as suspect and
will require site visit.
According to 3GPP NBAP spec., the minimum value that can be reported by Node B to RNC on is -112 dBm.

Threshold high RSSI:


When there is no call on the cell, the high threshold is at -73 dBm, which corresponds to the dynamic range
requirement for the receiver (defined in 3GPP spec 25.104, section 7.3.1, Wide area BS). Above that level,
there is no guarantee that the BTS is able to demodulate an uplink signal (even if received with a high
Eb/N0).
However, this threshold is too high. The following is chosen:
RTWP = -108.2 dBm (Thermal Noise at 20°C) + 3.3 dB (Noise Factor) + 7 dB (80% uplink load) = -98
dBm
Assuming RTWP main = RTWP div if RTWP = -98 dBm => RTWP main= RTWP div = -98 dBm
5 dB (NF max. 3GPP)
3.3 dB NF (ALU BTS Rx Chain Noise Factor)

Corrective action:
The problem could come from the reception chain of the BTS (RF reception: antenna connectors, cabling,
DDM) or the radiating system (feeder, antenna or external interference).
The other possibility would be the problem is a hardware problem in the BTS digital part (TRM, CCM or
CEM).
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 27
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 1.7 Edition 1
Section 1 · Module 7 · Page 28
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 1
This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 2
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 3
This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 4
Page

1 Capacity monitoring 7
1.1 UTRAN capacity analysis strategy 8
1.2 Reactive capacity planning 9
1.3 UTRAN congestion detection principles 10
1.4 Blocking characterization 11
1.5 Capacity monitoring 12
1.6 Which resource can block? 13
1.7 Find a counter to detect blocking of a given resource 14
2 Capacity analysis 15
2.1 Principles 16
2.2 Blocking and load 17
3 Capacity troubleshooting 18
3.1 DL Tx power load 19
3.2 DL code load 20
3.3 UL radio load 21
3.4 CEM load 22
3.5 Iub load 23
3.6 RNC load 24
3.7 Bottleneck analysis: RB allocation procedure 26
3.8 Bottleneck analysis: per type of call 30
3.9 Solve capacity issue 31
3.10 Case study 32
4 Capacity licensing monitoring 33
4.1 Node B capacity licensing principles 34
4.2 Node B capacity licensing tokens 35
4.3 Capacity licensing counters: example 36
4.4 Capacity licensing counter screenings 37
4.5 CEM monitoring counter 38

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 5
This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 6
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 7
Reactive capacity planning
Bottleneck identification
Detection and characterization
Resolution by RF parameter or RF design tuning or by resource addition

Pro-active capacity planning


Analysis is triggered by disruptive scenarios in order to anticipate their impact:
New Software release and major feature activation (i.e., Cell FACH Step4).
New service introduction, new subscriber growth rate, new coverage, H/W densification.
Typically 4-6 times a year.
Capacity planning at UTRAN level taking into account detail node constraint in order to add the right
component at the right place.
Pre-sales dimensioning is mainly based on UTRAN dimension but post-sales capacity planning needs to be
synchronized based on actual and accurate capacity assets. Deviation must be calculated.
The training is referring to Reactive Capacity Planning.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 8
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 or special events 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.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 9
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 10
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 11
#1629 VS.RadioBearerEstablishmentUnsuccess:
Number of radio bearer setup not successfully established, with no RADIO_BEARER_SETUP_REQUEST sent.(based on
procedure count, not RBs). Incremented based on reference cell
#1652 VS.RadioBearerSetupRequest:
Number of Radio Bearer setup decisions (leading or not to an RB setup, i.e. Incremented even if CAC rejects the
setup). The counter should be pegged multiple times for multiple RBs to be set up in the same procedure. Incremented
based on reference cell.
VS.RadioLinkSetupUnsuccess - #38
Number of unsuccessful radio link setups
VS.RadioLinkSetupRequest - #54
Number of internal events that would lead to a radio link setup request
VS.RadioLinkAdditionUnsuccess - #39
Number of unsuccessful radio link additions
VS.RadioLinkAdditionRequest - #55
Number of internal events that would lead to a radio link addition request
VS.RadioLinkReconfigurationPrepareUnsuccess - #40
Number of radio link reconfiguration preparation failures
VS.RadioLinkReconfPrepReq - #56
Number of internal events that would lead a radio link reconfiguration prepare
RRC.FailConnEstab - #404
Failed RRC Connection Establishments by Cause
RRC.SuccConnEstab - #403
Number of rrc connections successful

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 12
Lp = Logical Processor (each CPU board of the RNC is monitored)
Ap = Adjunct Processor (each PMC CPU of each PS FP board of the RNC is monitored)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 13
The counter providing the number of radio bearer setups not successfully established can be used for
finding out the missing radio resource:
DL Tx Power: VS.RadioBearerEstablishmentUnsuccess.UnavailableDlPowerResources
DL Code: VS.RadioBearerEstablishmentUnsuccess.UnavailableDlCodeResources
UL RSSI: VS.RadioBearerEstablishmentUnsuccess.Unspecified
CEM processing: VS.RadioBearerEstablishmentUnsuccess.NodeBCEMLackofL1Resource
Iub Bandwidth: VS.RadioBearerEstablishmentUnsuccess.LackTransportIdIub
Iub cid: VS.RadioBearerEstablishmentUnsuccess.LackBwthIub
RNC processing: VS.RadioBearerEstablishmentUnsuccess.LackOfRncProcessingResources

As the UL RSSI capacity problem is counted in the global Unspecified sub-counter of RB Setup Unsuccess, it
is recommended to check:
the sub-counter #404 RRC.FailConnEstab. RSSI providing the number of RRC Connection Setup
Failures due to UL CAC on RSSI too high
The sub-counter #10213 VS.FailedAdmissionDueToULload.Cum providing the number of
times the RNC rejects a UL admission (SRB or TRB) for too high UL Load reasons

As the CEM capacity problem is counted in the dedicated sub-counter NodeBCEMLackofL1Resource of RB


Setup Unsuccess, it is no longer needed to check the counters giving the number of times a CEM Allocation
failed.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 14
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 15
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 16
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)
VS.CEMUsedDCH - #10301 (replaced the counter VS.CEMUsed - #10301)
min/max/avg of the ratio between the CEM capacity used and the total CEM capacity that was available at
the BTS startup, restricted to DCH.
A sampling event generated by the CCM CallP every 5 seconds that gets the current percentage of CEM
used (restricted to DCH: HSxPAs are excluded)
VS.ApCpuUtilizationAvg - #20202
This attribute indicates the processor average CPU utilization over the collection interval. This is calculated
using data sampled every 100 milliseconds.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 17
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 18
VS_IRMTimeCellRadioColorBlack - #1123
Load counter that tracks the percentage of time during a collection period that a particular cell is considered black by iRM
VS.IRMTimeCellRadioColorRed - #1124 (per Cell): Load counter that tracks the percentage of time during a collection period
that a particular cell is considered red by iRM
VS.IRMTimeCellRadioColorYellow - #1125 (per Cell): Load counter that tracks the percentage of time during a collection
period that a particular cell is considered yellow by iRM
VS.IRMTimeFreeDlCodesBySpreadingFactor - #1126 (per Cell): Load counter that tracks the average number of free DL
codes for each spreading factor
IrmPreemptionTimeCellColorCongestedBecauseOfPower - #1138 (per Cell): Load counter that tracks the percentage of
time during a collection period that a particular cell is considered congested by iRM because of power shortage
VS.PreemptNbPerCacFail - #1701 (per Cell): Number of times (per CAC failure) the preemption resource deallocation procedure
is required
• Sub-Counter #4: RNC DL power resources not available
VS.AvgTxPower - #1002 (per Cell): Average of Tx Power measurements received from that cell
VS.IrmcacPowerDist - #306 (per Cell): Number of seconds per range of power considered by the CAC algorithm for that cell. The
percentage is calculated as PowerReserved divided by MaxTxPower.
• Sub-Counter #0: 0 to 40 percent of total power • Sub-Counter #1: 40 to 70 percent of total power
• Sub-Counter #2: 70 to 80 percent of total power • Sub-Counter #3: 80 to 90 percent of total power
• Sub-Counter #4: 90 to 100 percent of total power
VS.DistDlTtlPwrRatio - #307 (per cell): 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
Same screenings as for #306
VS.DlTtlTxPwrR99Only - #308 (per Cell): DL TX power (of all codes not used for HS transmission) ratio P/Pmax received from
NBAP common measurement per cell.
• Sub-Counter #0: ratio greater or equal zero and less than 20 • Sub-Counter #1: ratio greater or equal to 20 and less than 40
• Sub-Counter #2: ratio greater or equal to 40 and less than 60 • Sub-Counter #3: ratio greater or equal to 60 and less than 80
• Sub-Counter #4: ratio greater or equal to 80 and less or equal to 100

VS.RadioTxCarrierPwr - #10205 (per BTSCell): min/max/linear average (software filtered) total transmitted power per sector
and per frequency at the Tx channelizer
• Sub-Counter #0: Operational Max Power • Sub-Counter #1: • Power used

VS.PAPowerCapacity - #10216 (per BTSEquipment): PA power capacity installed, licensed and used
• Sub-Counter #0: Number of events • Sub-Counter #1: Sum of HW installed values
• Sub-Counter #2: Sum of Licensing values • Sub-Counter #3: Sum of used values

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 19
VS.IRMTimeCellRadioColorRed - #1124 (per Cell): Load counter that tracks the percentage of time
during a collection period that a particular cell is considered red by Irm

VS.IRMTimeCellRadioColorYellow - #1125 (per Cell): Load counter that tracks the percentage of
time during a collection period that a particular cell is considered yellow by iRM

VS.IRMTimeFreeDlCodesBySpreadingFactor - #1126 (per Cell): Load counter that tracks the


average number of free DL codes for each spreading factor:

VS.IrmPreemptionTimeCellColorCongestedBecauseOfOvsfCodes - #1137 (per Cell): Load


counter that tracks the percentage of time during a collection period that a particular cell is considered
congested by iRM because of Code shortage

VS.PreemptNbPerCacFail - #1701 (per Cell): Number of times (per CAC failure) the preemption
resource deallocation procedure is required
Sub-Counter #3: RNC DL code resources not available

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 20
VS.IRMTimeULRadioLoadColorYellow - #1193 (per Cell): Percentage of time during a collection
period that the UL Radio Load color is yellow for the relating cell.

VS.IRMTimeULRadioLoadColorRed - #1194 (per Cell): Percentage of time during a collection period


that the UL Radio Load color is red for the relating cell.

VS_IRMTimeULRadioLoadColorBlack - #1200 (per cell)


Percentage of time during a collection period that the UL Radio Load color is black for the relating cell.

VS.UplinkRssi - #303 (per Cell): Uplink RSSI received from NBAP common measurement per cell.

VS.DistRssi - #1042 (per Cell): Uplink RSSI received from NBAP common measurement per cell. It
details the number of common measurements (here, UL RSSI level) according to their respective ranges
and during the reporting period.
Sub-Counter #0: -97.0dBm <= Measurement
Sub-Counter #1: -100.0dBm <= Measurement < -97.0 dBm
Sub-Counter #2: -103.0dBm <= Measurement < -100.0 dBm
Sub-Counter #3: -105.0dBm <= Measurement < -103.0 dBm
Sub-Counter #4: Measurement < -105 dBm

VS.CellULload - #10211 (per BTSCell): The mean UL Load value


Total load
eDCH/HSUPA load

VS.FailedAdmissionDueToULload (BTSCell) - #10213: Total number of failed UL admissions due to


excessive load in the cell

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 21
VS.QosDlCemLdClrRed - #1178 (per Cell): Load counter that tracks the percentage of time during a collection
period that a particular cell is considered red by CEM load because of CEM radio resource shortage in downlink
VS.QosUlCemLdClrRed - #1181 (per Cell): Load counter that tracks the percentage of time during a collection
period that a particular cell is considered red by CEM load because of CEM radio resource shortage in uplink
VS.QosDlCemLdClrYellow - #1177 (per Cell): Load counter that tracks the percentage of time during a collection
period that a particular cell is considered yellow by CEM load because of CEM radio resource shortage in downlink
VS.QosUlCemLdClrYellow - #1180 (per Cell): Load counter that tracks the percentage of time during a collection
period that a particular cell is considered yellow by CEM load because of CEM radio resource shortage in uplink
VS.QosDlCemLdCellPreemptClrCngstd - #1179 (per Cell): Load counter that tracks the percentage of time
during a collection period that a particular cell is considered congested by iRM because CEM shortage in downlink
VS.LocalCellGroupLoad - #10310 (per LocalCellGroup): number of Channel Elements (CEs) used for a local cell
group (restricted to DCH)
Free UL capacity • Used UL capacity
Free DL capacity • Used DL capacity
VS.R99CECapacity - #10317 (BTSEquipment): R99 CE capacity installed, licensed and used
Sub-Counter #0: Number of events
Sub-Counter #1: Sum of HW installed values
Sub-Counter #2: Sum of Licensing values
Sub-Counter #3: Sum of used values
Sub-Counter #4: Number of successes
Sub-Counter #5: Number of refusals or restrictions due to the license
Sub-Counter #6: Number of refusals due to the hardware capacity
VS.CEMUsedDCH - #10301 (BTSEquipment): min/max/avg of the ratio between the CEM capacity used and the
total CEM capacity that was available at the BTS startup, restricted to DCH.
Note: Formula used for CEMUsedDCH computation is changing according to BTS CEM configuration and
capacity licensing feature activation:
If Capacity Licensing is not active and only iCEM is handling R99 Traffic (r99MaxNumberCeXcem =
0), it represents the percentage of CEM processing capacity used. Based on internal DSP processing
usage, it is not linked to CE consumption (same formula as in previous releases).
If Capacity Licensing is active or in case of xCEM handling R99 Traffic (r99MaxNumberCeXcem ≠
0), the CEMUsedDch will be based on CE model (used vs. available CEs).

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 22
VS.IrmTimeDlIubTransportColorRed - #1182 (per Cell): Load counter that tracks the percentage of
time during a collection period that a particular cell is considered red by iRM because of Downlink Iub
transport resource shortage.

VS.IrmTimeDlIubTransportColorYellow - #1183 (per Cell): Load counter that tracks the percentage
of time during a collection period that a particular cell is considered yellow by iRM because of Downlink Iub
transport resource shortage.

VS.IrmPreemptionTimeDlIubTransportCongested - #1156 (per Cell): Load counter that tracks the


time during a collection period that a particular cell is considered Congested by iRM Preemption because of
Downlink Iub transport shortage.

VS.DistIubLoadAal2If - #1758 (per Iub AAL2If BP): Number of seconds per range of IuB load per
bandwidth pool based on real time traffic with granularity of 10 seconds.
Sub-Counter #0: 0-20% of total Bandwidth
Sub-Counter #1: 20-40% of total Bandwidth
Sub-Counter #2: 40-60% of total Bandwidth
Sub-Counter #3: 60-80% of total Bandwidth
Sub-Counter #4: 80-100% of total Bandwidth

VS.DistIbuLoadIpIf - #1765 (per Iub IpIf BP): Number of seconds per range of IuB load per
bandwidth pool based on real time traffic with granularity of 10 seconds.
Sub-Counter #0: 0-20% of total Bandwidth
Sub-Counter #1: 20-40% of total Bandwidth
Sub-Counter #2: 40-60% of total Bandwidth
Sub-Counter #3: 60-80% of total Bandwidth
Sub-Counter #4: 80-100% of total Bandwidth

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 23
VS.CpuUtilAvg - #20103 (per Lp): This attribute indicates an average processor utilization level over
the specified time period, timeInterval. This average is calculated based on one-minute CPU utilization
averages.

VS.CpuUtilAvgMin - #20104 (per Lp): This attribute indicates the minimum processor utilization level
over a specified time period, timeInterval. This is based on one-minute CPU utilization averages.

VS.CpuUtilAvgMax - #20105 (per Lp): This attribute indicates the maximum processor utilization level
over a specified time period, timeInterval. This is based on one minute CPU utilization averages.

VS.ApCpuUtilizationHistogram - #20201 (per Ap): This attribute indicates a histogram of Adjunct


Processor's CPU utilization. Every 100 milliseconds, the average CPU utilization for the previous 100
millisecond interval is used to select a bin from the vector and the bin is incremented.
Sub-Counter #0: less than 50%
Sub-Counter #1: greater or equal than 50% and less than 60%
Sub-Counter #2: greater or equal than 60% and less than 70%
Sub-Counter #3: greater or equal than 70% and less than 80%
Sub-Counter #4: greater or equal than 80% and less than 85%
Sub-Counter #5: greater or equal than 85% and less than 90%
Sub-Counter #6: greater or equal than 90% and less than 95%
Sub-Counter #7: greater or equal than 95% and less than 100%
Sub-Counter #8: equal to 100%

VS.ApCpuUtilizationAvg - #20202 (per Ap): This attribute indicates the processor average CPU
utilization over the collection interval. This is calculated using data sampled every 100 milliseconds.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 24
The maximum RNC capacity while maintaining an optimal QoS is reached when the average load of the
most loaded PMC type is the maximum as possible and RNC rejections due to overload are kept at the
minimum.
The committed capacity levels for the RNC correspond to specific engineering margins, which are presented
within this table. This does not mean that above this CPU load value the RNC will enter in overload, but it
corresponds to a margin taken to ensure the RNC will be able to handle some variations of traffic while
keeping a good Quality Of Service (QoS) for the end users.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 25
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 26
#1629 - VS.RadioBearerEstablishmentUnsuccess with the following screenings:
1 – “UnavailableDlCodeResources”
2 – “UnavailableDlPowerResources”
4 – “RlFailOrRlcErr”
6 – “LackOfRncProcessingResources”
9 – “LackTransportIdIu”
10 – “LackBwthIu”
11 – “LackTransportIdIur”
12 – “LackBwthIur”
13 – “LackTransportIdIub”
14 – “LackBwthIub”

#0040 - VS.RadioLinkReconfigurationPrepareUnsuccess with the following screenings:


0 – “RadioLinkReconfigurationFailure” (Reception of RL Reconfiguration Failure message)
1 – “TimeoutNbap”
4 – “NodeBCEMLackL1Rsrc”
5 – “LackCidOrUdpPortIub” (Lack of CID on the Iub)
6 – “LackBwthIub” (Lack of bandwidth on the Iub)
7 – “INodeRefusal” (other I-Node resource not available)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 27
CEM load can be monitored at Cell level
VS.CEMAllocDCH - #10318
Number of times allocation of CEM resources succeeded, and failed (due to no CEM resource available)
Success and fail of CEM allocations, DCH part
Sub-Counter #0: Allocation successes for DCH
Sub-Counter #1: Allocation fails for DCH
Sub-Counter #2: Allocation successes for HSDPA, DCH part
Sub-Counter #3: Allocation fails for HSDPA, DCH part
Sub-Counter #4: Allocation successes for eDCH, DCH part
Sub-Counter #5: Allocation fails for eDCH, DCH part

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 28
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 29
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 30
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 31
The Node B has 3 CEMs equipped in the BTSEquipment cabinet.
The Iub transport configuration of this Node B is shown below:

INVccGroup
VCC OAM VPi/VCi
VCC NodeBCP VPi/VCi
VCC CCP VPi/VCi
VCC DS traffic VPi/VCi/PathId/QoSId
VCC NDS traffic VPi/VCi/PathId/QoSId
VCC HSDPA traffic VPi/VCi/PathId/QoSId

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 32
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 33
This feature provides the technical base for “Pay-as-you-grow” commercial schemes. With a licensing
scheme in place, the operator can order HW with a reduced capacity and subsequently purchase licenses
for additional capacity
Node B capacity licenses are per OMC. The operator can distribute capacity between controlled BTSs via
licensing parameters.
The following Node B capacity aspects are managed since UA06 via this feature: CEM R99 capacity, CEM
HSDPA capacity, CEM HSUPA capacity, xTRM capacity, RRH capacity, PA power & RRH power.
Additional capacity licence is OMC wide and can be distributed between the controlled BTSs (intra-OMC);
there is no exchange of licenses between OMCs.
License file: it is a file describing the total capacity (temporary or permanent) allocated for all BTSs of a
given OMC. This file is protected by a digital signature.
HW Capacities: Customer can purchase independently HW and capacities (note that the following table
is provided as an example and not as an ALU commitment on the list of purchasable items or
“packs”):

iCEM xCEM
iCEM64 iCEM128
H/W H/W xCEM H/W
+ +
minimum minimum
CEM H/W capacity capacity + minimum capacity
R99 capacity Blocks of 16CE
HSDPA capacity Blocks of (8 HSDPA connections + 1.8 Mbit/s)
HSUPA capacity Blocks of (8 HSUPA connections + 480 kbit/s)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 34
The table above shows how the BTS resources are managed by Capacity Licensing parameters and
summarizes the units and capacity increase steps for each area.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 35
Capacity Licensing brings a new set of capacity counters allowing monitoring CEM blocking and usage in
parallel with the existing counters. These counters are per Node B (covering all resources of a given type).
CEM Counters
#10317 R99CECapacity – unit: Nb. of CEs
#10835 HsdpaUsersCapacity – unit: Nb. of users
#10836 HsdpaThroughputCapacity – unit: kbits/s
#10909 eDCHUsersCapacity – unit: Nb. of users
#10910 eDCHThroughputCapacity – unit: kbits/s

PA/RRH Counters
#10214 TRMSecondCarriersCapacity – unit: Nb. of carriers
#10215 RRHSecondCarriersCapacity – unit: Nb. of carriers
#10216 PAPowerCapacity – unit: Watt
#10217 RRHPowerCapacity – unit: Watt

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 36
Screenings 1, 2 and 3 correspond to HW capacity (installed, licensed and used).
Screenings 4, 5 and 6 refer to the outcome of the CEM allocation procedure.
Screening 0 is used for calculation of average values.

These counters can be used as a ratio between ScrX and Scr0 in order to get relevant information per
observation period.
Example: Number of HW installed R99 CEs during observation period will be equal to:
R99CECapacity.scr1 / R99CECapacity.scr0 (this should be constant if no new HW is added or removed –
same for scr2/scr0)

In case of throughput counters, the number of rejected CEM resource requests (Scr5 & Scr6) will be in fact
the number of active TTIs (2 ms for HSD and 10 ms for HSU) during which the scheduler restricted the
throughput because the license or HW throughput limit was reached.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 37
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 38
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.1 Edition 1
Section 2 · Module 1 · Page 39
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 1
This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 2
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 3
This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 4
Page

1 Traffic monitoring 7
1.1 Network traffic 8
1.2 Average number of calls per day – RNC metrics 9
1.3 Average number of calls per day – DL - cell metrics 10
1.4 Average number of calls per day – UL - cell metrics 11
1.5 Uplink/downlink CS traffic 12
1.6 Uplink/downlink PS traffic 13
1.7 Uplink/downlink PS traffic per QoS 16
2 User-perceived throughput counters 17
2.1 Goal 18
2.2 Principles 19
2.3 Characteristics 20
2.4 Algorithm for DL throughput calculation 21
2.5 Counters for R99 throughput 23

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 5
This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 6
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 7
The first step of network traffic monitoring consists in evaluating the evolution of DL and UL traffic based
on views available in the dashboard dictionary at RNC level and Cell level.
The analysis of these views gives the traffic volume for PS and CS calls.

In case of a traffic issue observed in these views for PS or CS calls, it will be necessary to define more
precisely:
the affected network elements,
the affected period of time,
the events occurred on the network.
It will also be necessary to give details about:
the affected type(s) of traffic,
the type of issue.
This can be done thanks to the detailed monitoring and KPI troubleshooting reports.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 8
VS.NumberOfRabEstablished - #1660
Average number of RABs established 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).
A set of sub-counters screened on: DlRbSetId,UlRbSetId,TrafficClass derived screening per granted Rab
0 Other Dl, Ul, Traffic Class combinations
1 Dl and Ul are CS Speech, TC is Conversational
2 Dl and Ul are CSD 64, TC is Conversational
3 Dl and Ul are CS, TC is Streaming
4 Dl is any low rate PS I/B, Ul is any PS I/B, TC is Interactive
5 Dl is any low rate PS I/B, Ul is any PS I/B, TC is Background
6 Dl is any high rate PS I/B, Ul is any PS I/B, TC is Interactive
7 Dl is any high rate PS I/B, Ul is any PS I/B, TC is Background
8 Dl is any low rate Ps Str and Ul is any PS Str, TC is Streaming
9 Dl is any high rate Ps Str and Ul is any PS Str, TC is Streaming

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 9
VS.DlAsConfIdAvgNbrEstablished - #1666
indicates an average of the number of DlAsConfIds established per iRNC, based on time average
over a collection period.
A set of sub-counters screened on: Derived AsConf Screening for DlAsConfId Avg Nbr Estab:
0 Other
1 Signaling Only
2 CS speech NB or LR AMR
3 CS speech WB AMR
4 CS data
5 CS Streaming 14.4
6 CS Streaming 57.6
7 PS Streaming 16
8 PS Streaming 64
9 PS Streaming 128
10 PS Streaming 256
11 PS Streaming 384
12 PS I/B 0
13 PS I/B 8
14 PS I/B 16
15 PS I/B 32
16 PS I/B 64
17 PS I/B 128
18 PS I/B 256
19 PS I/B 384
20 HSDPA
21 TRB on cell FACH

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 10
VS.UlAsConfIdAvgNbrEstablished - #1667
indicates an average of the number of UlAsConfIds established per iRNC, based on time average
over a collection period.
A set of sub-counters screened on: Derived AsConf Screening for UlAsConfId Avg Nbr Estab,
• Sub-Counter #0: Other
• Sub-Counter #1: Signaling Only • Sub-Counter #2: CS speech • Sub-Counter #3: CS data
• Sub-Counter #4: CS Str 57.6 • Sub-Counter #5: CS Str 14.4 • Sub-Counter #6: PS Str 16
• Sub-Counter #7: PS Str 32 • Sub-Counter #8: PS Str 64 • Sub-Counter #9: PS Str 128
• Sub-Counter #10: PS I/B 8 • Sub-Counter #11: PS I/B 16 • Sub-Counter #12: PS I/B 32
• Sub-Counter #13: PS I/B 64 • Sub-Counter #14: PS I/B 128 • Sub-Counter #15: PS I/B 384
• Sub-Counter #16: PS I/B or PS Str HSUPA • Sub-Counter #17: TRB on cell RACH

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 11
RNC level:
Total count of RLC payload on dedicated channels containing Packet Switched data (in kbytes):
VS.DedicatedDownlinkKbytesRlc #1544 for DL VS.DedicatedUplinkKbytesRlc #1543 for UL
Cell level:
Total count of RLC payload on dedicated channels containing Packet Switched data (in kbytes):
VS.DedicatedDownlinkKbytesRlcActiveCells #1554 for DL
VS.DedicatedUplinkKbytesRlcActiveCells #1553 for UL

Screenings for #1544 and #1554:


• Sub-Counter #0: Other Dl • Sub-Counter #1: Any SRB • Sub-Counter #2: CS speech
• Sub-Counter #3: CS 64 conversational • Sub-Counter #4: CS streaming • Sub-Counter #5: PS HSDPA
• Sub-Counter #6: PS Str 128 • Sub-Counter #7: PS Str 256 • Sub-Counter #8: PS Str 384
• Sub-Counter #9: PS Str Other • Sub-Counter #10: PS I/B 8kbps • Sub-Counter #11: PS I/B 16kbps
• Sub-Counter #12: PS I/B 32kbps • Sub-Counter #13: PS I/B 64kbps • Sub-Counter #14: PS I/B 128kbps
• Sub-Counter #15: PS I/B 256kbps • Sub-Counter #16: PS I/B 384kbps

Screenings for #1543 and #1553:


• Sub-Counter #0: Other Ul • Sub-Counter #1: Any SRB • Sub-Counter #2: CS speech
• Sub-Counter #3: CS 64 conversational • Sub-Counter #4: CS streaming • Sub-Counter #5: PS Str 16
• Sub-Counter #6: PS Str 64 • Sub-Counter #7: PS Str Other • Sub-Counter #8: PS I/B 8kbps
• Sub-Counter #9: PS I/B 16kbps • Sub-Counter #10: PS I/B 32kbps • Sub-Counter #11: PS I/B 64kbps
• Sub-Counter #12: PS I/B 128kbps • Sub-Counter #13: PS I/B 384kbps • Sub-Counter #14: PS I/B HSUPA
• Sub-Counter #15: PS Str HSUPA

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 12
RNC level:
Total count of RLC payload on dedicated channels containing Packet Switched data (in kbytes):
VS.DedicatedDownlinkKbytesRlc #1544 for DL VS.DedicatedUplinkKbytesRlc #1543 for UL
Cell level:
Total count of RLC payload on dedicated channels containing Packet Switched data (in kbytes):
VS.DedicatedDownlinkKbytesRlcActiveCells #1554 for DL
VS.DedicatedUplinkKbytesRlcActiveCells #1553 for UL

Screenings for #1544 and #1554:


• Sub-Counter #0: Other Dl • Sub-Counter #1: Any SRB • Sub-Counter #2: CS speech
• Sub-Counter #3: CS 64 conversational • Sub-Counter #4: CS streaming • Sub-Counter #5: PS HSDPA
• Sub-Counter #6: PS Str 128 • Sub-Counter #7: PS Str 256 • Sub-Counter #8: PS Str 384
• Sub-Counter #9: PS Str Other • Sub-Counter #10: PS I/B 8kbps • Sub-Counter #11: PS I/B 16kbps
• Sub-Counter #12: PS I/B 32kbps • Sub-Counter #13: PS I/B 64kbps • Sub-Counter #14: PS I/B 128kbps
• Sub-Counter #15: PS I/B 256kbps • Sub-Counter #16: PS I/B 384kbps

Screenings for #1543 and #1553:


• Sub-Counter #0: Other Ul • Sub-Counter #1: Any SRB • Sub-Counter #2: CS speech
• Sub-Counter #3: CS 64 conversational • Sub-Counter #4: CS streaming • Sub-Counter #5: PS Str 16
• Sub-Counter #6: PS Str 64 • Sub-Counter #7: PS Str Other • Sub-Counter #8: PS I/B 8kbps
• Sub-Counter #9: PS I/B 16kbps • Sub-Counter #10: PS I/B 32kbps • Sub-Counter #11: PS I/B 64kbps
• Sub-Counter #12: PS I/B 128kbps • Sub-Counter #13: PS I/B 384kbps • Sub-Counter #14: PS I/B HSUPA
• Sub-Counter #15: PS Str HSUPA

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 13
This view provides basic information on the traffic transmitted on the downlink for an RNC, measured in
terms of kbytes of the payload for the transmitted RLC SDUs. Since it includes data for CS and PS, it is
possible to have an indication on the main service in terms of carried traffic, as well as which fraction of PS
traffic is related to HSDPA.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 14
This view provides basic information on the traffic transmitted on the uplink for an RNC, measured in terms
of kbytes of the payload for the transmitted RLC SDUs. Since it includes data for CS and PS, it is possible to
have an indication on the main service in terms of carried traffic, as well as which fraction of PS traffic is
related to HSUPA.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 15
VS.DedicatedDownlinkKbytesRlc.QoS - #2225
Downlink volume based on SDU payload in kbytes sent on dedicated downlink RLCs
QoS per Transport Channel Format in DL
Sub-Counter #0: QoS class interactive on DCH
Sub-Counter #1: QoS class background on DCH
Sub-Counter #2: QoS class interactive on HSDSCH
Sub-Counter #3: QoS class background on HSDSCH

VS.DedicatedUplinkKbytesRlc.QoS - #2226
Uplink data volume based on SDU payload in kbytes received on dedicated uplink RLCs
QoS per Transport Channel Format in UL
Sub-Counter #0: QoS class interactive on DCH
Sub-Counter #1: QoS class background on DCH
Sub-Counter #2: QoS class interactive on EDCH
Sub-Counter #3: QoS class background on EDCH

The above counters were introduced in UA07.1.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 16
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 17
new

This feature allows the operator to monitor the PS data throughput for interactive/background services
on a 24/7 basis as it is experienced by the end user.

This information is useful to compare cell performance or to quantify performance degradation caused
by congestion situations in the network.

The performance counters provide guidance for network optimization activities which should lead to a
better quality of service for the end users.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 18
The User Perceived Throughput Counters feature introduces distribution counters for uplink and
downlink throughput for PS data transfers.

The calculation of the user perceived throughput requires that the RNC keeps track of the duration of
data transfers and the amount of acknowledged RLC SDU data transferred (transfer rate is computed
by dividing the data volume by transfer duration).

While a PS connection is active there can be multiple packet data bursts. The idle periods between
separate data transfers are excluded when determining the duration of the transfer to increase the
accuracy of the provided information.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 19
The feature introduces separate counters for R99 DCH and HSDPA (downlink) and R99 DCH and
EDCH (uplink).

The support of separate counters for HSDPA and EDCH requires that the throughput calculation and
counter pegging is done not only at service termination, but also when there is a radio configuration
change where the UE gets HSDPA or EDCH resources newly assigned or when the RNC releases HSDPA or
EDCH resources for the UE.

Only traffic for the interactive/background QoS class is taken into account for these counters.

The RLC header is excluded from throughput calculation.

The ranges of the distributions are user configurable through parameters (10 bins for R99 counters and
20 bins for HSDPA/EDCH counters)

Counters are pegged against the UE’s reference cell when the reference cell is controlled by the SRNC.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 20
The RNC has the ability to accumulate the amount of acknowledged RLC SDU data (variable
Payload_DL) and the duration of RLC activity (variable Duration_DL) from several data transfers while
the UE is in Cell_DCH state.
The duration of a single PS data transfer is defined by t1_DL and t2_DL
t1_DL can be the instant:
When the first RLC PDU is sent to a UE in Cell_DCH state.
When another RLC PDU is sent to a UE in Cell_DCH state after the data from a previous data transfer
has been added to Duration_DL and Payload_DL.
t2_DL can be the instant:
When the last remaining PDU has been acknowledged and there are no further RLC PDUs to be sent to
the UE.
When the RNC decides to peg the user perceived throughput counters while there is a still ongoing DL
data transfer.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 21
At t2_DL, the RNC checks whether duration of the transfer (t2_DL – t1_DL) was longer than the minimum
duration of a data transfer to be taken into account for the user perceived throughput calculation, defined
by parameter minDuration:
If larger, the RNC adds this amount of acknowledged RLC SDU data to the variable Payload_DL and
the time difference to the variable Duration_DL.
If shorter, the information related to this data transfer is not taken into account.
This check ensures that the inability to exactly measure the transfer time affects the accuracy of the
metric.
When another RLC PDU is sent to the UE after t2_DL, the RNC re-initializes t1_DL and handles the new
data transfer separately.
Triggers to calculate the user perceived throughput using the expression Payload_DL/Duration_DL and
peg counters VS.UserTP.R99DL and VS.UserTP.HSDPA are:
RLC layer for the UE is torn down (RLC drop or release)
UE with an I/B RAB leaves the Cell_DCH state
RNC reconfigures an I/B RAB from HSDPA to R99 or vice-versa
RNC starts an intra-RNC inter-frequency handover or an inter-RAT handover for a UE which has an I/B
RAB.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 22
COUNTER ID 2500
Name NT_User_tp_r99_dl_rlc_refcell
3GPP Name VS.UserTP.R99DL
Location Cell (Reference)
Unit event
Range 31 Bits
Type CUM
Scanner Type GPO
Family User Perceived Throughput
Distribution of the user perceived throughput for interactive/background traffic in a
Meaning,
UMTS cell when using R99 DL traffic channels in CELL_DCH. The data rate threshold
Description
of the screenings can be defined by the CM attribute PmUserTpConfig.dlR99Thd.
Pegged against the reference cell. For the calculation, the RNC accumulates the RLC
payload data which has been acknowledged by the UE while the UE has been in
CELL_DCH state using an R99 DL DCH and the duration of the data transfer. This
counter is pegged when: 1) a UE with an I/B RAB mapped to R99 DCH in DL is leaving
Triggering Event CELL_DCH state 2) the UE with a I/B RAB mapped to R99 DL DCH is reconfigured to
another frequency layer 3) there is a reconfiguration of the DL transport channel from
R99 DCH to HSDPA. 4) The RNC triggers: - an intra-RNC inter-frequency handover -
an inter-RAT handover or - a cell change order procedure for a UE which has an I/B
RAB mapped to R99 DCH in DL.
Screening
Data range R99 DL
Criteria
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 23
COUNTER ID 2501

Name NT_User_tp_r99_ul_rlc_refcell
3GPP Name VS.UserTP.R99UL
Location Cell (Reference)
Unit event
Range 31 Bits
Type CUM
Scanner Type GPO
Family User Perceived Throughput
Distribution of the user perceived throughput for interactive/background traffic in a
Meaning,
UMTS cell when using R99 UL traffic channels in CELL_DCH. The data rate threshold
Description
of the screenings can be defined by the CM attribute PmUserTpConfig.ulR99Thd.
Pegged against the reference cell. For the calculation, the RNC accumulates the RLC
payload data which has been acknowledged by the UE while the UE has been in
CELL_DCH state using a R99 UL DCH and the duration of the data transfer. This
counter is pegged when: 1) a UE with an I/B RAB mapped to R99 DCH in UL is
Triggering Event leaving CELL_DCH state 2) the UE with a I/B RAB mapped to R99 UL DCH is
reconfigured to another frequency layer 3) there is a reconfiguration of the UL
transport channel from R99 DCH to EDCH. 4) The RNC triggers: - an intra-RNC inter-
frequency handover - an inter-RAT handover or - a cell change order procedure for a
UE which has an I/B RAB mapped to R99 DCH in UL.
Screening
Data Rate Range R99 UL
Criteria

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 24
Screening Data Rate Range DL R99 Data Rate Range UL R99

0 rate <= dlR99Thd[0] rate <= dlR99Thd[0]


dlR99Thd[0] < rate ≤
1 ulR99Thd[0] < rate ≤ ulR99Thd[1]
dlR99Thd[1]
dlR99Thd[1] < rate ≤
2 ulR99Thd[1] < rate ≤ ulR99Thd[2]
dlR99Thd[2]
dlR99Thd[2] < rate ≤
3 ulR99Thd[2] < rate ≤ ulR99Thd[3]
dlR99Thd[3]
dlR99Thd[3] < rate ≤
4 ulR99Thd[3] < rate ≤ ulR99Thd[4]
dlR99Thd[4]
dlR99Thd[4] < rate ≤ ulR99Thd[4] < rate ≤ ulR99Thd[5]
5
dlR99Thd[5]
dlR99Thd[5] < rate ≤ ulR99Thd[5] < rate ≤ ulR99Thd[6]
6
dlR99Thd[6]
dlR99Thd[6] < rate ≤ ulR99Thd[6] < rate ≤ ulR99Thd[7]
7
dlR99Thd[7]
dlR99Thd[7] < rate ≤ ulR99Thd[7] < rate ≤ ulR99Thd[8]
8
dlR99Thd[8]

9 dlR99Thd[8] < rate ulR99Thd[8] < rate

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 25
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 26
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 27
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 2.2 Edition 1
Section 2 · Module 2 · Page 28
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 3.1 Edition 1
Section 3 · Module 1 · Page 1
This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 3.1 Edition 1
Section 3 · Module 1 · Page 2
# FDD Frequency Division Duplex
3GPP 3rd Generation Partnership Project FTP File Transfer Protocol

A G
AALn ATM Adaptation Layer type n GGSN Gateway GPRS Support Node
AMR Adaptive Multi-Rate GP Granularity Period
ATM Asynchronous Transfer Mode GPO General Permanent Observation
GPS Global Positioning System
B GSM Global System for Mobile
BER Bit Error Ratio Communications
BH Busy Hour GTP GPRS Tuneling Protocol
BLER Block Error Ratio GTP-U GTP for transfer of user data in separated
BP Bandwidth Pool tunnels for each PDP context
BSS Base Station Subsystem GUI Graphical User Interface
BTS Base Transceiver Station
H
C HHO Hard Handover
CAC Call Admission Control HMI Human-Machine Interface
CC Cumulative Counter HO Handover
CCCH Common Control CHannel (GPRS) HSDPA High Speed Downlink Packet Access
CCM Core Control Module HSUPA High Speed Uplink Packet Access
CDR Call Drop Rate HW Hardware
CEM Channel Element Module
CI Cell Identity I
CID Channel Identifier IE Information Element
CN Core Network IMA Inverse Multiplexing for ATM
CP Control Processor IMEI International Mobile Equipment Identity
CPICH Common PIlot CHannel IMSI International Mobile Subscriber Identity
CPU Central Processing Unit IP Internet Protocol
C-RNTI Cell - Radio Network Temporary Identifier Iu Interconnection point between RNC
CS Circuit Switching and 3G Core Network
CSCN Circuit-Switched Core Network Iub Interface between Node B and RNC
CSSR Call Setup Success Rate Iur Interface between two RNCs
CT Call Trace
CV Counter Value K
Kbps Kilobit per second
D kHz kiloHertz
dB decibel KPI Key Performance Indicator
dBm decibel referenced to a milliwatt
DCCH Dedicated Control Channel L
DCH Dedicated Channel LAC Location Area Code
DCPS Dual Core Packet Server LAN Local Area Network
DDM Dual Duplexer Module LAU Location Area Update
DER Discrete Event Registration LOLA Loader & Aggregator
DL Downlink LTE Long-Term Evolution
DPCCH Dedicated Physical Control Channel
DPDCH Dedicated Physical Data Channel M
DRNC Drift RNC MCPA Multi Carrier Power Amplifier
DTD Document Type Definition MHz MegaHertz
MIB Management Information database
E MO Mobile Originated
Ec/No Ratio of energy per modulating bit to the MPLS MultiProtocol Label Switching
noise spectral density MSC Mobile services Switching Center
E-DCH Enhanced Dedicated Channel
N
F NAS Non Access
FACH Forward Access Channel NB NarrowBand

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 3.1 Edition 1
Section 3 · Module 1 · Page 3
NBAP Node B Application Part RTCT Real Time Call Trace
NE Network Element RTO Real Time Observation
NPO Network Performance Optimizer RTWP Received Total Wideband Power
NSP Network Services Platform RX Reception

O S
OAM Operation Administration and SABP Service Area Broadcast Protocol
Maintenance SCCP Signaling Connection Control Part
O&M Operation and Maintenance SCCPCH Secondary – Common Control Physical
OMC Operation and Maintenance Center Channel
OPEX Operational EXpenditures SDU Service Data Unit
OT Object Trace SGSN Serving GPRS Support Node (GPRS)
OVSF Orthogonal Variable Spreading Factor SHO Soft HandOver
SI Status Indicator
P SIR Signal-to-Interference Ratio
PC Protocol Converter SMC Security Mode Command
PCM Pulse Code Modula tion SMS Short Message Service
PDN Packet Data Network SPU Mean Sector Per User
PDP Packet Data Protocol SRB Signaling Radio Bearer
PDU Packet Data Unit S-RNC Serving-Radio Network Controller
PLMN Public Land Mobile Network SRNS Serving Radio Network Subsystem
PM Performance Management SSCOP Service Specific Connection Oriented
PMC PCI Mezzanine Card Protocol
PRACH Packet Random Access Channel (GPRS) STM Synchronous Transport Module
PS Packet Switching SW Software
PSFP Packet Server Functional Processor
P-TMSI Packet Temporary Mobile Subscriber T
Identity TC Traffic Class
PVC Permanent Virtual Connection TFO Tandem Free Operation
TMA Tower Mounted Amplifier
Q TMSI Temporary Mobile Subscriber Identity
QoE Quality of Experience TMU Traffic Management Unit
QoS Quality of Service TRB Traffic Radio Bearer
TrFO Transcoder Free Operation
R TRM Transmit/Receive Module
RAB Radio Access Bearer TTI Transmission Time Interval
RACH Random Access CHannel Tx Transmission
RANAP Radio Access Network Application
Part U
RAT Radio Access Technology UDP User Datagram Protocol
RAU Remote Antenna Unit UE User Equipment
RB Radio Bearer UL Uplink
RF Radio Frequency UMTS Universal Mobile Telecommunication
RFO Radio Frequency Optimizer System
RL Radio Link UTRAN Universal Terrestrial Radio Access
RLC Radio Link Control Network
RLS Radio Link Set
RNC Radio Network Controller V
RNS Radio Network Subsystem VCC Virtual Channel Connection
RNSAP Radio Network Subsystem Application VCI Virtual Channel Identifier
Part VoIP Voice over IP
RoT Raise over Thermal noise VPI Virtual Path Identifier
RRC Radio Resource Control VPN Virtual Private Network
RRH Remote Radio Head
RRM Radio Resources Management W
RSCP Received Signal Code Power WB Wideband
RSSI Received Signal Strength Indicator WCDMA Wideband Code Division Multiple Access

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 3.1 Edition 1
Section 3 · Module 1 · Page 4
WCT WCDMA Call Trace
WMS Wireless Management System
WPS Wireless Provisioning System
WQA Wireless Quality Analyzer
WTA Wireless Telephony Applications

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.


TMO18268_V2.0-SG-UA08-Ed1 Module 3.1 Edition 1
Section 3 · Module 1 · Page 5
Copyright © 2012 Alcatel-Lucent. All Rights Reserved.
TMO18268_V2.0-SG-UA08-Ed1 Module 3.1 Edition 1
Section 3 · Module 1 · Page 6
All Rights Reserved © Alcatel-Lucent @@YEAR
@@COURSENAME - Page 1
All rights reserved © Alcatel-Lucent
Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent

All Rights Reserved © Alcatel-Lucent @@YEAR


@@COURSENAME - Page 2