3gpp cause mapping to relevant

Nokia Siemens Networks WCDMA RAN, Rel. RU20, Operating Documentation, Issue 07

3GPP cause mapping to relevant counters

DN70229016

Issue 03Approval Date 2009-11-23

Confidential

2 DN70229016Issue 03


Id:0900d80580672964Confidential

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2009. All rights reserved

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-satzes.

DN70229016 3



Table of contentsThis document has 24 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 Introduction to 3GPP cause mapping for relevant counters . . . . . . . . . . 7

2 The Mapping Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.1 Events and errors in network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.2 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.3 3GPP messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.4 3GPP causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.5 Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Mapping structure visibility in the Excel file . . . . . . . . . . . . . . . . . . . . . . 10

4 Used definitions in the mapping structure . . . . . . . . . . . . . . . . . . . . . . . 114.1 Distinguished network events and errors. . . . . . . . . . . . . . . . . . . . . . . . 114.1.1 Network events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114.1.1.1 RRC events and subevents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114.1.1.2 RAB events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.1.1.3 Signalling (= Iu) connection events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.1.1.4 SRNS relocation events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.1.1.5 Inter-RNC HHO events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134.1.1.6 Inter-System HHO events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134.1.1.7 Pre-emption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134.1.2 Recognizable errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144.1.3 Error sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144.1.3.1 RAN functionality-related error sources . . . . . . . . . . . . . . . . . . . . . . . . . 154.1.3.2 RAN interface error sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154.1.3.3 UE-related . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154.1.4 Error reason . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154.2 Available counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164.2.1 Related to normal network events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164.2.2 Related to network errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174.2.2.1 Counter failure sources at RRC and/or RAB setup . . . . . . . . . . . . . . . . 174.2.2.2 Counter failure sources at RRC and/or RAB access . . . . . . . . . . . . . . . 174.2.2.3 Counter failure sources at RRC and/or RAB release. . . . . . . . . . . . . . . 174.3 Used 3GPP messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.3.1 RANAP (3GPP TS 25.413 UTRAN Iu interface Radio Access Network Ap-

plication Part (RANAP) signalling) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.3.2 RRC (3GPP TS 25.331 Radio Resource Control (RRC); Protocol specifica-

tion) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.4 Used 3GPP causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.4.1 Normal RANAP causes (3GPP TS 25.413). . . . . . . . . . . . . . . . . . . . . . 184.4.1.1 RANAP causes received by RNC from CN . . . . . . . . . . . . . . . . . . . . . . 184.4.1.2 RANAP causes sent by RNC to CN. . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.4.2 Abnormal RANAP causes (3GPP TS 25.413) . . . . . . . . . . . . . . . . . . . . 204.4.2.1 Failure indicating RANAP causes received by the RNC from CN . . . . . 20

4 DN70229016



4.4.2.2 Failure indicating RANAP causes sent by the RNC to CN . . . . . . . . . . . 204.4.3 Normal RRC causes (3GPP TS 25.331). . . . . . . . . . . . . . . . . . . . . . . . . 204.4.3.1 Normal RRC causes received by the RNC from the UE. . . . . . . . . . . . . 204.4.3.2 Normal RRC causes sent by RNC to UE . . . . . . . . . . . . . . . . . . . . . . . . 204.4.4 Abnormal RRC causes (3GPP TS 25.331) . . . . . . . . . . . . . . . . . . . . . . 204.4.4.1 Abnormal RRC causes received by the RNC from the UE . . . . . . . . . . . 204.4.4.2 Abnormal RRC causes sent by the RNC to the UE . . . . . . . . . . . . . . . . 204.5 Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225.1 Normal cases Excel file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225.1.1 Used causes in RANAP when a RAB has been successfully set up . . . 225.1.2 Updated counters when a RAB is pre-empted . . . . . . . . . . . . . . . . . . . . 225.1.3 Updated counters when an SRNS relocated (= UE not involved). . . . . . 225.2 Failure cases Excel file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235.2.1 Used 3GPP messages when a Radio Connection is found to be lost . . 235.2.2 Updated counters when there is a BTS resource shortage for a requested

RT RAB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

6 Locating the Excel file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

DN70229016 5

3GPP cause mapping to relevant counters Summary of changes

Id:0900d8058067294bConfidential

Summary of changes Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Note that the issue numbering system is changing. For more information, see Guide to WCDMA RAN operating documentation.

Changes between issues 2-0 and 03Changes have been made to the following sections:

• RRC events and subevents (obsolete information has been removed) • RAB events (obsolete information has been removed) • Inter-System HHO events (obsolete information has been removed) • Counter failure sources at RRC and/or RAB release (transmission added to the list)

Changes between issues 2-0 and 1-1The following changes have been made to section Used definitions in the mapping structure due to changes in Inter System HHO between WCDMA and GAN:

• New specific RRC release case • New network sub events defined: incoming ISHO for GAN and outgoing ISHO

for GAN • New error reason: UE returns from GAN in failed outgoing ISHO

The following changes have been made to section Used definitions in the mapping structure due to changes in Directed retry to GSM for AMR calls:

• New specific RRC release case • Used cause for Directed Retry

The following change has been made to section Used definitions in the mapping struc-ture due to changes in RAB reconfiguration:

• Used cause for failed RAB reconfiguration

Editorial corrections have been made to the following sections:

• Introduction to 3GPP cause mapping for relevant counters • The Mapping Structure • Locating the Excel file

Changes between issues 1-1 and 1-0Editorial changes have been made.

6 DN70229016


Id:0900d8058067294bConfidential

Summary of changes

DN70229016 7

3GPP cause mapping to relevant counters Introduction to 3GPP cause mapping for relevant coun-ters

Id:0900d8058067294fConfidential

1 Introduction to 3GPP cause mapping for relevant countersThe scope of this document:

• What RAN network events should be monitored and therefore traceable through existing counters?

• What kind of RANAP and/or RRC signalling are behind the documented network events?

• What are the error source types? • Which 3GPP causes are (basically) used in signalling? • What is the relationship between Nokia Siemens Networks counters and 3GPP

causes?

All issues listed above are handled comprehensively in this document and followed up in the RNC Counter Mapping Excel file.

The following chapters include the descriptions:

• the descriptions of the mapping structure (The Mapping Structure) • the description of the visualisation used in the Excel file (Mapping structure visibility

in the Excel file) • the descriptions of used definitions for the mappings (Used definitions in the

mapping structure) • instructions for using the Excel file (Examples)

The location of the Excel file is given in Locating the Excel file..

8 DN70229016


Id:0900d805806157d5Confidential

The Mapping Structure

2 The Mapping StructureA mapping structure has been defined to provide a comprehensive way to see how the cause codes, counters and other relevant issues are linked to each other.

The structure begins with categorising the linked issues (events/counters/causes/mes-sages).

The issues that are closely linked to each other are included in the same category (for instance, Events and errors).

The mapping structure includes the following categories:

• events and errors in network • counters • 3GPP messages • 3GPP causes • notes

2.1 Events and errors in networkAll defined network events and error-related issues are based on the Nokia Siemens Networks view of relevant issues related to mapping between cause codes and coun-ters:

• Network events • Distinguished subevents related to Telecom in WCDMA RAN (for instance, RRC

setup request) • Network errors, error sources and error reasons

• Distinguished errors related to Telecom in WCDMA RAN (for instance, No resources to setup RRC)

• The defined error sources in WCDMA RAN (for instance, Admission Control) • The defined reason behind the errors (for instance, No air resources)The full list of used definitions is found in Distinguished network events and errors.

2.2 CountersAll given counters are related to Service Level Measurement.

The following groups of counters concerning RRC and RAB cases exist:

• Event phase RRC and RAB cases (for instance, RRC Setup) • Failure and Release causes (that is, the failure source, for instance, Admission

Control (AC)) • Counter examples: RRC Setup Complete, RRC Setup failure due to AC

There is not necessarily a separate failure counter for each defined failure source and/or reason.

This means that a counter can represent more than one defined failure source and/or reason.

The full list of used counters is found in Section Available counters.

The detailed counter definitions are found in RNC counters – RNW part.

The interface specific counters are found in RNC counters – RNW part.

DN70229016 9

3GPP cause mapping to relevant counters The Mapping Structure


2.3 3GPP messagesThe given messages are defined by 3GPP.

The messages are found in 3GPP TS 25.413 UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling and 3GPP TS 25.331 Radio Resource Control (RRC); Protocol specification.

The following are examples of messages found in this document and the Excel file:

• RANAP (for instance, RAB ASSIGNMENT REQUEST) • RRC (for instance, RRC CONNECTION REQUEST)

The full list of used messages is found in Section Used 3GPP Messages.

For detailed message definitions, see http://www.3gpp.org/.

2.4 3GPP causesThe given causes are defined by 3GPP.

The causes are found in the following:

• 3GPP TS 25.413 • 3GPP TS 25.331

The used causes are described in Used 3GPP Causes.

For all cause definitions, see http://www.3gpp.org/.

2.5 NotesIn this section, additional information is given related to 3GPP messages and/or causes related to a network event:

• For instance, if the WCDMA RAN is not using a message or a cause. • Cause notes: used when more than one cause is possible.

10 DN70229016



Mapping structure visibility in the Excel file

3 Mapping structure visibility in the Excel fileThe defined mapping structure in The Mapping Structure is visible in the Excel file through colored fields:

• Events and errors in the network (White) • Counters (Green) • 3GPP Messages (Red) • 3GPP Causes (Blue) • Cause Notes (Blue)

DN70229016 11

3GPP cause mapping to relevant counters Used definitions in the mapping structure


4 Used definitions in the mapping structureAll defined Network Events, Recognised Errors, Error Sources and Error Reasons are listed in this section.

All possible Service Level counters are listed in this section. The detailed counter struc-ture and definitions are found in RNC counters – RNW part.

All used 3GPP messages in the mapping structure are listed in this section.

Used 3GPP causes in the mapping structure are listed in this section when found rele-vant. All used 3GPP causes are found in the Excel sheet.

For more information on 3GPP causes, see http://www.3gpp.org/.

4.1 Distinguished network events and errors

4.1.1 Network eventsThere are different kind of triggers for each network event, which are listed between dif-ferent network events. For instance, both RRC and RAB setups can be started for incoming SRNS relocation.

4.1.1.1 RRC events and subevents

RRC Setup

• RRC Setup Request • RRC Connection Request • Incoming SRNS Relocation • Incoming Inter RNC HHO • Incoming Inter System HHO

• RRC Setup Complete • RRC redirection at setup • RRC redirection to GSM at setup

In RRC Setup, the redirection of the UE to another frequency or GSM is separated from the basic RRC Setup Complete.

If the needed RRC setup is related to an incoming ISHO from GSM or GAN, it is treated equally , that is, no separation in subevents is possible.

RRC Release

• Basic RRC Release • Iu connection release command (Relocation excluded) based release • Inter System HHO based release • Pre-emption based release

• Directed signalling connection re-establishment • Inter System HO to GAN

The basic RRC Release always happens simultaneously with the Iu connection release (excluding relocation), Inter System HHO or pre-emption.

In RRC Release, the directed signalling connection re-establishment and ISHO to GAN are separated from the basic RRC Release.

12 DN70229016



Used definitions in the mapping structure

4.1.1.2 RAB events

RAB setup

• RAB Setup Request • RAB Assignment Request • Incoming SRNS Relocation • Incoming Inter-RNC HHO • Incoming Inter-System HHO

• RAB Setup Complete

If the needed RAB (AMR) setup is related to an incoming ISHO from GSM or GAN, it is treated equally, that is, no separation in subevents is possible.

RAB release

• RAB Release Command by CN • RAB Assignment Request • Iu connection release command (Relocation excluded) based release • Outgoing SRNC Relocation based release • Outgoing Inter-RNC HHO based release • Outgoing Inter-System HHO based release • Pre-emption based release

• RAB Release Request by RNC • RAB Release Complete

In Iu Release, all the related RAB(s) are also released.

The outgoing SRNS relocation, Inter-RNC HHO and Inter-System HHO are treated as RAB release commands along with the basic Iu connection release command.

If the outgoing ISHO is related to GSM or GAN, it is treated equally, that is , no separa-tion in subevents is possible.

4.1.1.3 Signalling (= Iu) connection events

Iu connection setup

• Iu Connection Setup Request • Iu Connection Setup Complete

Currently there are no counters in Service Level Measurement related to Iu connection setup.

Iu connection release

• Iu Connection Release Command by CN • Iu Connection Release Request by RNC

If there are RAB(s) for asked Iu connections (relocation excluded) to be released, the RAB(s) are asked to be released as well.

4.1.1.4 SRNS relocation events

SRNS relocation start

• SRNS Relocation Start in Source RNC

DN70229016 13



• SRNS Relocation Start in Target RNC

SRNS relocation complete

• SRNS Relocation Complete in Source RNC • SRNS Relocation Complete in Target RNC

In 3GPP, SRNS Relocation means 'UE not involved' Relocation.

On how SRNS relocation triggers RRC/RAB setup or on release events, see Section Examples.

4.1.1.5 Inter-RNC HHO events

Inter-RNC HHO start

• Inter-RNC HHO Start in Source RNC • Inter-RNC HHO Start in Target RNC

Inter-RNC HHO complete

• Inter-RNC HHO Complete in Source RNC • Inter-RNC HHO Complete in Target RNC

In 3GPP, Inter-RNC HHO means 'UE involved' Relocation.

For information on how Inter-RNC HHO triggers RRC/RAB setup or on release events, see Section Examples.

4.1.1.6 Inter-System HHO events

Inter-System HHO start

• Outgoing Inter-System HHO Start in RAN • Incoming Inter-System HHO Start in RAN

Inter System HHO complete

• Outgoing Inter-System HHO Complete in RAN • Incoming Inter-System HHO Complete in RAN

In Inter-System HHO, the events are handled from RAN perspective, that is BSS/BSC part is not included.

If the incoming ISHO is related to GSM or GAN, it is treated equally, that is, no separa-tion in subevents is possible.

For information on how Inter-System HHO triggers RRC/RAB setup or on release events, see Section Examples.

4.1.1.7 Pre-emption • Pre-emption Start

Currently there are no counters in Service Level Measurement related to Pre-emption Start.

• Pre-emption Complete

14 DN70229016




4.1.2 Recognizable errorsNote that there are errors that can be 'normal' events from the network point of view. These 'normal' events from the network point of view mean that an UE error causes a release of resources. The UE-related errors are also found in this chapter but they are used in network based Key Performance Indicators (KPIs) as normal releases. For more information, see Section Changes in Key Performance Indicators in WCDMA RAN Key Performance Indicators.

Setup phase errors

• RRC Resource Shortage • No resources for RRC in network

• RAB Resource Shortage • No resources for RT RAB in network • No resources for NRT RAB in network

• RRC Setup Errors • RRC setup failure because of network error • RRC setup failure because of UE error

• RAB Setup errors • Requested RAB not supported by RAN • Requested RAB not supported by UE • RAB RT setup failure because of network error • RAB RT setup failure because of UE error • RAB NRT setup failure because of network error • RAB NRT setup failure because of UE error

Release phase errors

• RRC Release errors • RRC release because of network error • RRC release because of UE error

• RAB Release errors • RAB RT release because of network error • RAB RT release because of UE error • RAB NRT release because of network error • RAB NRT release because of UE error

4.1.3 Error sourcesFor more information, see the following Functional Area Descriptions:

• Section Admission control overview in WCDMA RAN RRM Admission Control • Section Call setup and release in RNC Call Setup and Release • Section Handover control in WCDMA RAN RRM Handover Control • Section Packet Data Transfer States in RNC Packet Data Transfer States • Section Introduction to the packet scheduler functionality in WCDMA RAN RRM

Packet Scheduler • Section Power control in Power Control in WCDMA RAN • Section WCDMA radio resource management in WCDMA RAN Radio Resource

Management Overview

DN70229016 15



• Section Description of SRNS relocation in SRNS Relocation • Section RAS05.1 transmission and transport features overview in RAS05.1 Trans-

mission and Transport Features

4.1.3.1 RAN functionality-related error sourcesThe following RAN functionality-related error sources are available:

• Handover Control • Admission Control • Resource Manager • BTS • Connection Admission Control • Radio Link Control • Medium Access Control • Outer Loop Power Control • ATM Traffic Management • Connection Management

4.1.3.2 RAN interface error sourcesThe following RAN interface error sources are available:

• Radio (that is Uu) • RRC • RANAP (that is Iu) • RNSAP (that is Iur) • NBAP (that is Iub)

4.1.3.3 UE-relatedThe following UE-related error source is available:

• UE

4.1.4 Error reason • Conflicting cell parameters prevent setup • No radio capacity • Directed retry • No spreading codes • No Channel Elements • No AAL type 2 capacity • Failure in creating L2RLC entity • Failure in creating L2 MAC dedicated entity • Failure in creating L2 Outer Loop Power Control entity • No AAL type 2 termination points • No RNTI • Not supported service • Requested RAB reconfiguration not possible

16 DN70229016




• UE not capable to support requested service • Iu tunnel endpoint reservation failure • Failure in reconfiguring L2 RLC entity for data PDU transportation • Failure in reconfiguring L2 MAC dedicated entity for data transportation • Failure in reconfiguring L2 OLPC dedicated entity for data transportation • Initial synchronisation failure • UE does not respond to RRC SETUP • UE responds with wrong parameters • RL synchronisation failure • UE responds RB RECONFIGURATION FAILURE • Relocation failed • Relocation cancelled • UE does not confirm that it has received needed mobility information • No resources to execute Relocation in Target RNC • Relocation failed • UE does not confirm that it has received needed mobility information • Inter-RNC HHO failed • Inter-RNC HHO cancelled • UE does not confirm that it has reconfigured physical or transport channel • No resources to execute Inter-RNC HHO in Target RNC • Inter-RNC HHO failed • UE does not confirm that it has reconfigured physical or transport channel • Inter-System HHO failed • Inter-System HHO to GAN failed • Inter-System HHO cancelled • UE Returns from GSM • UE Returns from GAN • Inter-System HHO failed • Inter-System HHO cancelled

There is also an error reason Not possible. This means that in the particular setup or release phase, error cannot occur for the listed error source.

For example, at NRT RAB setup, the transport resources are not reserved and thus the CAC or ATM Transport Management parts of the RNC cannot be error sources/reasons for failed NRT RAB setup.

4.2 Available countersNote that these are not the only counters that can be used. There are many interface-specific counters also available. Therefore not everything is visible through the Service Level counters, only the most important ones.

For more information, see RNC counters – RNW part.

4.2.1 Related to normal network events • RRC Setup Attempt • RAB Setup Attempt • RRC Access Complete

DN70229016 17



• RAB Access Complete • RRC Active Complete • RAB Active Complete • RRC Active Release because of pre-emption • RAB Active Release because of pre-emption • RRC Active Release because of SRNS Relocation • RAB Active Release because of SRNS Relocation • Incoming or Outgoing relocation • Incoming or Outgoing Inter RNC HHO • Incoming or Outgoing Inter System HHO

• Separate counters for GAN

4.2.2 Related to network errors • RRC setup failure • RAB setup failure • RRC access failure • RAB access failure • RRC active failure • RAB active failure • Relocation failure • Inter RNC HHO failure • Inter System HHO failure

• Separate counters for GAN

4.2.2.1 Counter failure sources at RRC and/or RAB setup • Handover Control • Admission Control • BTS • Transmission • RNC Internal • Frozen BTS

4.2.2.2 Counter failure sources at RRC and/or RAB access • Synchronisation failure • UE

4.2.2.3 Counter failure sources at RRC and/or RAB release • Radio interface • Iub • RNC Internal • Iur • Iu • UE

18 DN70229016




• Transmission

4.3 Used 3GPP messagesThe listed messages are defined by 3GPP: http://www.3gpp.org/.

4.3.1 RANAP (3GPP TS 25.413 UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling) • RAB Assignment Request • RAB Assignment Response • RAB Release Request • Iu Release Command • Iu Release Complete • Iu Release Request • Relocation Required • Relocation Request • Relocation Complete

4.3.2 RRC (3GPP TS 25.331 Radio Resource Control (RRC); Protocol specification) • RRC Connection Request • RRC Setup • RRC Setup Complete • Radio Bearer Setup Complete • Radio Bearer Reconfiguration Complete • Physical Channel Reconfiguration • Transport Channel Reconfiguration • UTRAN Mobility Information • Physical Channel Reconfiguration Confirm • Transport Channel reconfiguration Confirm • UTRAN Mobility Information Confirm • RRC Connection Release

4.4 Used 3GPP causesThe listed causes are defined by 3GPP: http://www.3gpp.org/.

4.4.1 Normal RANAP causes (3GPP TS 25.413)

4.4.1.1 RANAP causes received by RNC from CNNormal Release (83) The CN indicates that a RAB and/or the whole Iu connection can

be released as it is not needed anymore for the UE.

Successful Relocation (11) The CN indicates that the Iu connection can be released as the UE has moved under the additional SRNC.

DN70229016 19



Time Critical Relocation (17) The CN indicates that an Iu connection needs to be established to the RNC, which now becomes the additional SRNC.

This cause is used in Inter-RNC HHO and Inter-System HHO except service- or load-based requests.

Resource Optimisation Relocation (41) The CN indicates that an Iu connection needs to be established to the RNC which now becomes the additional SRNC.

This cause is used in Load reason based Inter-RNC and Inter-System HHO.

Relocation desirable for radio reasons (43) The CN indicates that an Iu connection needs to be established towards the RNC which now becomes the addi-tional SRNC.

This cause is used in basic SRNS relocation and Service reason based Inter-RNC and Inter-System HHO.

g For basic RAB Assignment request, there are no causes used, that is there is no cause field in the related RANAP messages.

4.4.1.2 RANAP causes sent by RNC to CNRAB pre-empted (1) The RNC indicates that an RT RAB needs to be pre-empted.

User Inactivity (16) The RNC indicates that an Iu Connection needs to be released.

Release because of UE generated signalling connection release (40) The RNC indi-cates that an Iu Connection needs to be released.

This means that the UE requests the Iu connection to be released because it does not need it anymore.

Network Optimisation (116) The RNC indicates that an Iu Connection needs to be released.

This means that:

• the operator has either configured the network so that release is needed, for instance, taken CELL_PCH out of use

• or the UE does not support needed network functionality, for instance, CELL_PCH state

Time Critical Relocation (17) The RNC indicates that an Iu connection needs to be established towards an additional RNC which now becomes the addi-tional SRNC or BSS.

This cause is used in Inter-RNC HHO and Inter-System HHO except service- or load-based requests.

Resource Optimisation Relocation (41) The RNC indicates that an Iu connection needs to be established towards an additional RNC, which now becomes the additional SRNC or BSS.

This cause is used in Load reason based Inter-RNC and Inter-System HHO.

Relocation desirable for radio reasons (43) The RNC indicates that an Iu connection needs to be established towards an additional RNC which now becomes the additional SRNC or BSS.

20 DN70229016




This cause is used in basic SRNS relocation and Service reason based Inter-RNC and Inter-System HHO.

g All the above cases are treated as normal releases from the RAN perspective.

g For successful Iu Connection Release, RAB Release or Relocation there are no causes used, that is there is no cause field in the related RANAP messages.

4.4.2 Abnormal RANAP causes (3GPP TS 25.413)

4.4.2.1 Failure indicating RANAP causes received by the RNC from CNIt includes all other causes except the listed request and success causes listed before.

For details, see the Excel file.

4.4.2.2 Failure indicating RANAP causes sent by the RNC to CNIt includes all other causes except the listed request and success causes listed before.


4.4.3 Normal RRC causes (3GPP TS 25.331)

4.4.3.1 Normal RRC causes received by the RNC from the UERRC Request causes as defined by 3GPP TS 25.331

4.4.3.2 Normal RRC causes sent by RNC to UE normal event The RNC indicates to the UE that the RRC must be released.

user inactivity The RNC indicates to the UE that the RRC must be released.

pre-emptive release The RNC indicates to the UE that the RRC must be released.

directed signalling connection re-establishment The RNC indicates to the UE that the RRC must be released. This means that an RRC Connected UE (not in CELL_DCH) has moved under another RNC than SRNC and makes a Cell Update. If the SRNS Relocation is not possible, the RRC connec-tion needs to be released under the current SRNC and re-directed to the additional SRNC.

4.4.4 Abnormal RRC causes (3GPP TS 25.331)

4.4.4.1 Abnormal RRC causes received by the RNC from the UERRC Request causes as defined by 3GPP TS 25.331

4.4.4.2 Abnormal RRC causes sent by the RNC to the UEIt includes all other causes except the listed request and success causes listed before.

DN70229016 21




4.5 NotesAs the same cause can be used for more than one network event and/or one error source, these causes must be noted.

For example, the No Resource Available (114) cause is used for more than an error source:

• … • 114 = used when no SF codes are available for the needed Radio Bearer. • 114 = used when no Channel Elements are available for the needed Radio Bearer. • …

There can also be notes indicating that the used cause is perhaps not a descriptive one. The reason for this is found in the cause description.

Example:

• The Unspecified (115) cause is used. The Transport layer (66 and 67) causes in 3GPP 25.413 cannot be used here.

All these details are found in the corresponding field in the Excel file.

22 DN70229016


Id:0900d805806157deConfidential

Examples

5 ExamplesThis section gives - through examples - instructions on how to use the Excel file for finding more information.

5.1 Normal cases Excel file

5.1.1 Used causes in RANAP when a RAB has been successfully set up1. Network Event Column: Select RAB Setup2. Network Subevent Column: Select RAB Setup Complete

Result: See 'RANAP cause' Column => None

5.1.2 Updated counters when a RAB is pre-empted1. Network Event Column: Select Pre-emption2. Network Subevent Column: Select Pre-emption

Result: See 'Service Level Counter' Column => Active Release because of Pre-emption. Depending on the case, the RRC can also be released when the RAB is pre-empted.

5.1.3 Updated counters when an SRNS relocated (= UE not involved)The counters are updated if the RNC is the source RNC (= current SRNC) or Target RNC (= next SRNC).

Source RNC counter updates

1. Network Event Column: Select Relocation start2. Network Subevent Column: Select Relocation start in Source RNC

Result: See 'Service Level Counter' Column => None

1. Network Event Column: Select Relocation complete2. Network Subevent Column: Select Relocation complete in Source RNC

Result: See 'Service Level Counter' Column => Active Release because of SRNS Relo-cation

Target RNC counter updates

1. Network Event Column: Select Relocation start2. Network Subevent Column: Select Relocation start in Target RNC

Result: See 'Service Level Counter' column => • RRC counter: Incoming relocation because of SRNS Relocation • RAB Counters for Setup

3. Network Event Column: Select Relocation complete4. Network Subevent Column: Select Relocation complete in Target RNC

Result: See 'Service Level Counter' Column => None

DN70229016 23

3GPP cause mapping to relevant counters Examples

Id:0900d805806157deConfidential

5.2 Failure cases Excel file

5.2.1 Used 3GPP messages when a Radio Connection is found to be lost1. Network Event Column: Select RRC release, RAB release2. Network Subevent Column: Select RRC release because of network error3. Error Source Column: Select Radio Interface

Result: See 'RANAP messages' and 'RRC messages' columns => • RANAP message: Iu Release Request • RRC message: RRC Connection Release

5.2.2 Updated counters when there is a BTS resource shortage for a requested RT RAB1. Network Event Column: Select RAB setup2. Network Subevent Column: Select No resources for RT RAB in network3. Error Source Column: Select BTS

Result: See 'Service Level Counter' Column => 'BTS'

The counters are RAB-specific, for instance, when using the AMR RAB, the counter is RAB Setup Failures because of BTS for CS Voice (M1001C81). This is explained in RNC counters – RNW part.

24 DN70229016


Id:0900d805806157e1Confidential

Locating the Excel file

6 Locating the Excel fileThis documentation delivery contains the following RN4.0 3GPP Counters document in Excel format: 3GPP Cause Mapping to Relevant Counters - Embedded Excel sheet. It can be found through Nokia Online Services (NOLS) Documentation Center.

3gpp cause mapping to relevant

Documents