Tedpmc

UTRAN
Performance Measurement Counter
UMTS Terrestrial Radio Access Network
TED:PMC
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03
Trademarks:
All designations used in this document can be trademarks, the use of which by third parties
for their own purposes could violate the rights of their owners.
Copyright (C) Siemens AG / NEC Corporation 2004, 2005.
Issued by:
Siemens AG, Communications, Hofmannstraße 51, 81359 München, Germany and
NEC Corporation, 7-1, Shiba 5-chome, Minato-ku, Tokyo, Japan
Technical modifications possible.

Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written
contract.
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03 Preface
PREFACE
This document is prepared as a standard edition that may include descriptions
not applying to your system.
This document consists of the following sections:
(1) Measurement Report File Format
(2) Common Information for RNC Measurements
(3) Procedure-Related Measurements
(4) Subsystem-Related Measurements
(5) RRC State Measurements
(6) Radio Measurements
(7) ATM Measurements
(8) Measurements Collected by the Node B
(9) QoS Measurements
(10) Abbreviation List
Description of the single measurement in this document, Sections 3 through 9,

follows the description which is also used in 3GPP TS32.104, annex C.
However, a new item “Administrative Object Class” has been added:
(a) Description
An explanation of the measurement operation.
(b) Collection Method

The form in which this measurement data is obtained:
• CC (Cumulative Counter)
This collection method counts every occurrence of the event
specified.
• Gauge (dynamic variable)
This collection method is used when data being measured can vary
up or down during the period of measurement. This measurement
provides the mean number of used resources, the usage rate of
resources, or the number of transmitted data.
(c) Condition
The condition which causes this measurement data to be updated. If it is
PR-1
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03 Preface
not possible to give a precise condition, then the conditional

circumstances leading to the update are stated.
(d) Measurement Result (measured value(s), units)

A description of expected result value(s) (e.g. a single integer value) and
its cause values.
(e) Measurement Type

A short form of the measurement name specified in the header, which is
used to identify the measurement type in the result files.
(f) Administrative Object Class

This field identifies the object class the measurement can be
administrative on, i.e., the managed object class (e.g. cell) the
measurement is related to in the scanner creation and deletion
commands. Each administrative object class is related to exactly one
scanner subclass. This document uses the following administrative
object classes:
• RNC:
• RNC
• CELL
• Node B:
• NODEB
Further administrative object classes may be defined for measurements
on the lower layers (outside the scope of this document).
(g) Measurement Object Class

This field identifies the measured object class, i.e., the class of objects,
which are related to the measurement in the measurement result file, and
which are written to the measObjInstId fields of this file. This document
uses the following measurement object classes:
• RNC:
• RNC
• PROCESSOR
• NODEB
• CELL
• ADJACENT CELL RELATION
• ADJACENT GSM CELL RELATION
• Node B:
• NODEB
• CELL
Further measurement object classes may be defined for measurements on
PR-2
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03 Preface
the lower layers (outside the scope of this document).

Note that the measurement object class can differ from the administrative
object class. E.g. a measurement rncUsageRatio can be enabled/disabled
on managedElement level (=administrative object class), while the single
result values of this document are related to single processor instances
(=measurement object class). In this example only all processor
instances or none of them can be measured. The scope of this difference
is to reduce the number of scanner subclasses which have to be defined.
For the ADJACENT CELL RELATIONSHIP, the instances of the
measured object class (measObjInstId fields) identify both cells of this
relationship,. “Automatic adaptation” is possible for these
measurements, e.g., if “number of outgoing handovers per adjacent cell”
is active and a new neighbor cell is created, this measurement will
automatically be enhanced by a further counter, indicating the relation to
the new cell.
(h) mtype value

This value is used to set up a performance measurement counter for
RNC.
(i) Performance Measurement (PM) count trigger

This indicates what makes PM counter start or when PM value is counted
up.
In case there is another counter except attempt, success and failure, it is
indicated as exceptional counter in Note. Thus, relationship among them
is as follows:
No. of attempts = No. of successes + No. of failures (+ No. of
exceptions)
PR-3
3 Pages
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03
Reason for Update
Summary:
Definitions of new measurement types are added.
Details:
Chapter/Section Reason for Update

Table 1-1 New "meanTypes" and "measObjInstId" are
added.
Table 1-2 "Type" descriptions are correted.
1.2.4.1 "Radio Link Fail Cause Type (Radio Link)" is
added and "Inter-system HHO Cause Type
(Inter-system Handovers)" is deleted. Wrong
cause names are corrcted.
Table 2-1 "hhoAllOut*" is added.
3 Wrong cause names are corrcted.
Issue History:
Issue Date of issue Reason for Update
Number
1 3/2004 First edition
2 8/2004 Short names and other mistakes are corrected.
3 1/2005 Definitions of new measurement types are
added.
DA 1
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03 Contents
CONTENTS
TITLE PAGE
1. Measurement Report File Format ............................. 1-1

1.1 File Naming....................................................................... 1-1
1.2 Measurement Report File Format ................................... 1-1
1.3 Suspect Flag................................................................... 1-42
2. Common Information for RNC Measurements .... 2-1

2.1 Encoding of “per cause” Measurements....................... 2-1
2.2 Adjacent Cell Measurements (ACMs)............................. 2-1
2.3 Active Link Set VS Most Recently Added Cell .............. 2-2
3. Procedure-Related Measurements .......................... 3-1

3.1 Paging ............................................................................... 3-1
3.2 RRC Connections............................................................. 3-6
3.3 Signaling Connections .................................................. 3-12
3.4 RAB Assignment............................................................ 3-14
3.5 Transport Channel Reconfiguration............................. 3-30
3.6 Physical Channel Reconfiguration............................... 3-33
3.7 Cell Updates ................................................................... 3-35
3.8 URA Updates .................................................................. 3-37
3.9 Radio Link Updates........................................................ 3-37
3.10 Soft Handovers............................................................... 3-42
3.11 UTRAN Hard Handovers................................................ 3-67
3.12 Inter-System Hard Handovers....................................... 3-79
3.13 Relocation....................................................................... 3-87
3.14 Iu Release ....................................................................... 3-91
3.15 Number of drifting UEs.................................................. 3-99
4. Subsystem-Related Measurements ......................... 4-1

4.1 RNC Internal Measurements ........................................... 4-1
4.2 Iub Interface Measurements............................................ 4-9
4.3 Blocking Measurements................................................ 4-12
4.4 Channel Measurements................................................. 4-14
4.5 UE Quantity Measurements .......................................... 4-21
5. RRC State Management................................................ 5-1
CL-1
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03 Contents
TITLE PAGE
5.1 Number of attempted transitions

from CELL_DCH state...................................................... 5-1
5.2 Number of unsuccessful transitions
from CELL_DCH state per failure cause ........................ 5-1
from CELL_FACH state ................................................... 5-4
from CELL_FACH state per failure cause...................... 5-4
from CELL_PCH state...................................................... 5-7
from CELL_PCH state per failure cause ........................ 5-7
from URA_PCH state ....................................................... 5-9
from URA_PCH state per failure cause.......................... 5-9
6. Radio Measurements ..................................................... 6-1

6.1 Received total wide band power..................................... 6-1
6.2 Transmitted carrier power............................................... 6-2
6.3 Number of used codes per spreading factor................. 6-3
6.4 Number of attempted code requests
per spreading factor ........................................................ 6-5
6.5 Number of successful code requests
per spreading factor ........................................................ 6-6
7. ATM Measurements ....................................................... 7-1

7.1 Ingress cells (for STM-1, E1) ........................................... 7-1
7.2 Egress cells (for STM-1, E1)............................................ 7-2
7.3 Ingress cells for VPC/VCC (for STM-1)........................... 7-3
7.4 Egress cells for VPC/VCC (for STM-1) ........................... 7-4
7.5 Cells discarded due to HEC violations (for E1) ............. 7-5
7.6 Discarded cells due to congestion (for STM-1) ............. 7-6
7.7 Cell loss ratio (for STM-1)................................................ 7-7
7.8 Congestion of VP (for STM-1) ......................................... 7-8
8. Measurements Collected by the Node B ............... 8-1

8.1 Node B CP (Call Processing) Usage Ratio .................... 8-1
8.2 Node B BB (Base Band) Usage Ratio............................. 8-1
8.3 Rest of Call Capacity ....................................................... 8-2
CL-2
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03 Contents
TITLE PAGE
8.4 SCCPCH Usage Ratio ...................................................... 8-2

8.5 PRACH Usage Ratio......................................................... 8-3
8.6 Number of Receiving Preambles .................................... 8-3
8.7 HEC Error Ratio................................................................ 8-4
8.8 HEC Error Number ........................................................... 8-4
8.9 Number of Faulty ATM Cells (PTI) .................................. 8-5
8.10 Number of Faulty ATM Cells (VCI).................................. 8-5
8.11 Total Number of Transmitted ATM Cells........................ 8-6
8.12 Total Number of Received ATM Cells ............................ 8-6
8.13 Ratio of Lost ATM Cells................................................... 8-6
9. QoS Measurements ........................................................ 9-1

9.1 QoS Measurement on the RNC ....................................... 9-1
9.2 QoS Measurements on the Node B ................................ 9-1
10. Abbreviation List ........................................................... 10-1
CL-3
3 Pages
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03
SECTION 1
Measurement Report
File Format
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03 Measurement Report File Format
1. Measurement Report File Format

The following explains a Radio Network Controller (RNC) measurement
report file format and its naming rule which basically complies with 3GPP
TS32.104.
1.1 File Naming

The RNC measurement report file name begins with “C” as follows:
• C20010319.1455-20010319.1500_13:87
The managedElementId (MEID) is set as Unique ID and described in

variable length decimal format. The MEID is followed by the RC
parameter which is described in variable length decimal format.
The MEID is set in file “sbs3gManagedElementID” which belongs to

directory “/RNC/config/” in Disk (DK).
1.2 Measurement Report File Format
1.2.1 Parameter description and mapping table

The rules of each Abstract Syntax Notation No.1 (ASN.1) tag are
described in the following table.
Table 1-1 Mapping of ASN.1 Measurement Report File Format Tag (1/8)
ASN.1 Tag Description
MeasDataCollection
measFileheader
measData
measFileFooter It is indicated as YYYYMMDDhhmmss.
Year=YYYY, Month=MM, Day=DD, Hour=hh, Minute=mm, Second=ss
Second field “ss” is always “00”.
fileFormatVersion 1.
senderName “managedElementId=123”
Field 123 is variable length decimal format.
senderType “RNC”
vendorName “SAG/NEC”
1-1
A50016-G5000-E202-3-7618
collectionBeginTime It is indicated as YYYYMMDDhhmmss.

nEld
nEUserName “RNC 3.5”
nEDistinguishedName “managedElementId=123”
Field 123 is variable length decimal format.
measInfo
measTimeStamp It is indicated as YYYYMMDDhhmmss.
granularityPeriod Length of granularity period is indicated.
It takes values of 300, 900, 1800, 3600, 21600, 43200, 86400 (given in
seconds).
measTypes (a) Cell measurements
Cell-Base type (A single integer value)
ex: “pchUsageRate”
Cell-Cause type (A single integer value for each cause)
ex: “rrcEstabAtt.#c”
Note: Field “#c” includes Cause parameters.
Cell-RAB_Type type (A single integer value for each RAB_Type)
ex: “rabEstabTypeAtt.#q”
Note: Field “#q” includes RAB type parameters.
Cell-CS/PS-Cause type (2 integer values (CS/PS) for each cause)
ex: “rabEstabTypeFail.#s-#c”
Note: Field “#s” includes CS/PS parameters.
Field “#c” includes Cause parameters.
Cell-Target type (A single integer value for each target state)
ex: “transFromCellDchAtt.#t”
Note: Field “#t” includes Target state parameters.
1-2
A50016-G5000-E202-3-7618
measTypes Cell-Target-Cause type

(A single integer value for each target state for each RRC Fail cause)
ex: “transFromCellDchFail.#t-#c”
Note: Field “#t” includes Target state parameters.
Cell-SF-DL/UL Type (A single integer value for each spreading factor)
ex: “uuCodeReqAtt.#f-#d”
Note: Field “#f” includes Spreading factor parameters.
Field “#d” includes DL/UL parameters.
Cell-RL type (A single integer value for each number of radio links)
ex: “uesPerActiveLinkSetSize.#r”
Note: Field “#r” includes Active Link Set size parameters.
Cell-MMM type (3 integer value (mean, min., max.))
ex: “uuTransmCarrierPwr.#m”
Note: Field “#m” includes Mean/Min./Max. parameters.
Cell-Bearer Service type (A single integer value for each bearer service)
ex: “bearServiceperCell.#b”
Note: Field “#b” includes Bearer Service parameters.
(b) Adjacent cell (outgoing) measurements
AdjCell-Base type (A single integer value)
ex: “shoMoveOutAtt”
AdjCell-Cause type (A single integer value for each cause)
ex: “shoMoveOutFail.#c”
(c) Adjacent cell (incoming) measurements
AdjCell_in-Cause type (A single integer value for each cause)
ex: “cellupdateInc.#c”
1-3
A50016-G5000-E202-3-7618
measTypes (d) Adjacent GSM cell measurements

GSMCell-Base type (A single integer value)
ex: “interRatHoOutRelocAtt”
GSMCell-Cause type (A single integer value for each cause)
ex: “interRatHoOutRelocFail.#c”
(e) RNC measurements
RNC-Base type (A single integer value)
ex: “dhtAllocAtt”
RNC-CS/PS type (2 integer values (CS/PS))
ex: “sigConnEstabreq.#s”
RNC-Cause type (A single integer value for each cause)
ex: “paging1Cn.#c”
RNC-MMM type (3 integer values (mean, min., max.)
ex: “dhtUsage.#m”
Note: Field “#m” includes Mean/Min./Max. parameters.
RNC-Reloc-Cause type
(2 integer values (UE involved/UE not involved) for each cause)
ex: “relocOutAtt.#u-#c”
Note: Field “#u” includes Relocation type parameters.
RNC-CS/PS-Cause type (2 integer values (CS/PS) for each cause)
ex: “rabRelUtranOriginRNC.#s-#c”
(f) RNC processor measurements
RNC-CP type (2 integer value (AP load/CP load)
ex: “rrcUsageRatio.#a”
Note: Field “#a” includes AP load/CP load parameters.
1-4
A50016-G5000-E202-3-7618
measTypes (g) Iub interface measurements

NodeB-CS/PS-DL/UL type
(4 integer values (CS downlink, CS uplink, PS downlink, PS uplink))
ex: “userThroughputDCIub.#s-#d”
Field “#d” includes DL/UL parameters.
(h) ATM measurements
ATM-Base type
ex: “lineIncomingCells”
(i) Adjacent RNC measurements
Adjacent RNC-Base type (A single integer value)
ex: “ShoAddDriftingUeSucc”
1-5
A50016-G5000-E202-3-7618
measObjInstld (a) Cell measurements

“cell=#c”
Note: Field “#c” is a cell ID (0 - 65535).
(b) Adjacent cell (outgoing) measurements
If the relation of observed cell and adjacent cell is inter-RNC relation,
“cell=#oc-rnc=#n, cell=#ac”.
Note: Field “#oc” is a cell ID of observed cell (0 - 65535).
Field “#n” is an RNC ID of observed cell (0 - 4095).
Field “#ac” is a cell ID of adjacent cell (0 - 65535).
If the relation of observed cell and adjacent cell is intra-RNC relation,
“cell=#oc-cell=#ac”.
If the information of the adjacent cell is not in office data, this cell is
included in additional counter. It is expressed as
“cell=#oc-Other”.
(c) Adjacent cell (incoming) measurements
If the relation of observed cell and adjacent cell is inter-RNC relation,
“rnc=#n,cell=#ac-cell=#oc”.
Note: Field “#n” is an RNC ID of observed cell (0 - 4095).
Field “#oc” is a cell ID of observed cell (0 - 65535).
If the relation of observed cell and adjacent cell is intra-RNC relation,
“cell=#ac-cell=#oc”.
Note: Field “#ac” is a cell ID of adjacent cell (0 - 65535).
Field “#oc” is a cell ID of observed cell (0 - 65535).
“Other-cell=#oc”.
1-6
A50016-G5000-E202-3-7618
measObjInstld (d) Adjacent GSM cell (outgoing) measurements

“cell=#oc-cgi=#m.#l.#i”
#cell=#oc-Other”.
Field “#m” is a PLMN ID of CGI ID (00000[0] - 99999[9]).
Field “#l” is an LAC ID of CGI ID (1 - 65535).
Field “#i” is a CI ID of CGI ID (0 - 65535).
(e) RNC measurements
“rnc”
(f) RNC processor measurements
“cp=#p”
Note: Field “#p” is a processor ID of RNC processor (0 - 63).
(g) Iub interface measurements
“nodeb=#no”
Note: Field “#no” is a Node B ID (0 - 1023).
(h) Adjacent RNC measurements
“rnc=#rno”
Note: Field “#rno” is an RNC ID of adjacent RNC (0 - 4095).
(i) ATM (Line) measurements
<STM-1>
“stm-1line=#p.#r.#s.#l”
<E1>
“e1line=#cg.#c.#cp.#dp.#lp”
Note: Field “#p” is a switch port number (0).
Field “#r” is INFM Row (1).
Field “#s” is a line slot number (0 - 31).
Field “#l” is a line number (0, 2, 4, 6).
Field “#cg” is a CMUX group number (0 - 93).
Field “#c” is a CMUX number within a group (0 -3).
Field “#cp” is a CMP card number (1, 3, 5, 7).
Field “#dp” is a DTI card number (0, 2, 4, 6).
Field “#lp” is a DTI line number (0 - 7).
1-7
A50016-G5000-E202-3-7618
measObjInstld (j) ATM (VP) measurements

<STM-1>
“stm-1vp=#p.#r.#s.#l.#vp”
Field “#vp” is an ID of Virtual Path (VP) (0 - 4095).
(k) ATM (VC) measurements
<STM-1>
“stm-1vp=#p.#r.#s.#l.#vp.#vc”
Field “#vp” is an ID of Virtual Path (VP) (0 - 4095).
Field “#vc” is an ID of Virtual Channel (VC) (0 - 65535).
measResults
suspectFlag
TimeStamp A time stamp, referring to the end of the granularity period.
It is indicated as YYYYMMDDhhmmss.
1-8
A50016-G5000-E202-3-7618
1.2.2 ASN.1 file format definition

The ASN.1 file format definition is shown below.
DEFINITIONS AUTOMATIC TAGS::= BEGIN

MeasDataCollection::= SEQUENCE
{
measFileHeader MeasFileHeader,
measData SEQUENCE OF MeasData,
measFileFooter MeasFileFooter
}
MeasFileHeader::= SEQUENCE
{
fileFormatVersionINTEGER,
senderName PrintableString (SIZE (0..400)),
senderType SenderType,
vendorName PrintableString (SIZE (0..32)),
collectionBeginTime TimeStamp,
...
}
SenderType::= PrintableString (SIZE (0..8))
TimeStamp::= GeneralizedTime
MeasData::= SEQUENCE
{
nEId NEId,
measInfo SEQUENCE OF MeasInfo
}
NEId::= SEQUENCE
{
nEUserName PrintableString (SIZE (0..64)),
nEDistinguishedName PrintableString (SIZE (0..400))
}
MeasInfo::= SEQUENCE
{
measTimeStamp TimeStamp,
granularityPeriod INTEGER,
measTypes SEQUENCE OF MeasType,
measValues SEQUENCE OF MeasValue
}
MeasType::= PrintableString (SIZE (1..32))
MeasValue::= SEQUENCE
{
measObjInstId MeasObjInstId,
measResults SEQUENCE OF MeasResult,
suspectFlag BOOLEAN DEFAULT FALSE
}
MeasObjInstId::= PrintableString (SIZE (1..64))
MeasResult::= CHOICE
{
iValue INTEGER,
rValue REAL,
noValue NULL,
...
}
MeasFileFooter::= TimeStamp
END
Fig. 1-1 Example of ASN.1 Format
1-9
A50016-G5000-E202-3-7618
1.2.3 Short names in string of measTypes tag

Table 1-2 Short Names of Measurement Types (1/12)
mtype Measurement Type Scanner Short

(ID) Type (Cause Type) Type Name
Procedure-Related Measurements
Paging
111 Number of CN originated RNC-Cause RNC paging1Cn
pagings type 1 per paging (Paging)
cause
158 Number of CN originated Cell-Cause Cell paging2Cn
pagings type 2 per paging (Paging)
cause
112 Number of UTRAN Cell-Cause Cell paging1CellUtran
originated pagings type 1 (Paging)
in CELL_PCH per paging
cause
14 Number of UTRAN RNC-Cause RNC paging1UraUtran
originated pagings type 1 (Paging)
in URA_PCH per paging
cause
113 Number of failed pagings Cell-Cause Cell pagingCellFail
in CELL_PCH per failure (RRC protocol
cause error)
15 Number of failed pagings RNC-Cause RNC pagingUraFail
in URA_PCH per failure (RRC protocol
cause error)
RRC Connections
1 Number of attempted RRC Cell-Cause Cell rrcEstabAtt
connection establishments (Establishment)
per establishment cause
2 Number of successful RRC Cell-Cause Cell rrcEstabSucc
connection establishments (Establishment)
per establishment cause
107 Number of failed RRC Cell-Cause Cell rrcEstabFail
connection establishments (Reject)
per failure cause
1-10
A50016-G5000-E202-3-7618

159 Number of attempted RRC Cell-Cause Cell rrcRelDcch

connection releases on (RRC release)
DCCH per release cause
160 Number of attempted RRC Cell-Cause Cell rrcRelCcch
connection releases on (RRC release)
CCCH per release cause
Signaling Connections
161 Number of attempted RNC-CS/PS RNC sigConnEstabReq
signaling connection
establishments
162 Number of signaling Cell-Base Cell sigConnRelReq
connection release requests
163 Number of signaling Cell-Base Cell sigConnRelNotif
connection releases
RAB Assignment
5 Number of attempted RAB Cell-RAB_Type Cell rabEstabTypeAtt
establishments per RAB
type
6 Number of successful Cell-RAB_Type Cell rabEstabTypeSucc
RAB establishments per
RAB type
109 Number of unsuccessful Cell-CS/PS- Cell rabEstabTypeFail
RAB establishments per Cause
failure cause (RAB fail)
110 Number of RAB releases Cell-CS/PS- Cell rabRel
per release cause Cause
(RAB release)
114 Number of UTRAN Cell-CS/PS- Cell rabRelUtranOrigin
initiated RAB releases per Cause
release cause (RAB release)
115 Number of CN initiated Cell-CS/PS- Cell rabRelCnOrigin
RAB releases per release Cause
cause (RAB release)
1-11
A50016-G5000-E202-3-7618

116 Number of UTRAN RNC-CS/PS- RNC rabRelUtranOriginRNC

initiated RAB releases per Cause
release cause RNC related (RAB release)
117 Number of CN initiated RNC-CS/PS- RNC rabRelCnOriginRNC
RAB releases per release Cause
cause RNC related (RAB release)
Transport Channel Reconfiguration
218 Number of attempted Cell-Base Cell traChReconfAtt
transport channel
reconfigurations
219 Number of successful Cell-Base Cell traChReconfSucc
transport channel
reconfigurations
220 Number of failed transport Cell-Base Cell traChReconfFail
channel reconfigurations (Channel Reconf
per failure cause Fail)
Physical Channel Reconfiguration
164 Number of attempted Cell-Base Cell phyChReconfAtt
physical channel
reconfigurations
165 Number of successful Cell-Base Cell phyChReconfSucc
physical channel
reconfigurations
166 Number of failed physical Cell-Base Cell phyChReconfFail
channel reconfigurations (Channel Reconf
per failure cause Fail)
Cell Updates
167 Number of cell updates per Cell-Cause Cell cellUpdate
update cause (Cell Update)
168 Number of incoming cell AdjCell_in- Cell cellUpdateInc
updates per update cause Cause
per adjacent cell pair (Cell Update)
URA Updates
1-12
A50016-G5000-E202-3-7618

169 Number of URA updates Cell-Cause Cell uraUpdate

per update cause (URA Update)
Radio Link Updates
105 Number of radio link Cell-Cause Cell radioLinkFail
failures per failure cause (Radio Link Fail)
103 Number of attempted radio Cell-Base Cell rlEstabAtt
link establishments
104 Number of successful Cell-Base Cell rlEstabSucc
radio link establishments
106 Number of unsuccessful Cell-Cause Cell rlEstabFail
radio link establishments (RL
per failure cause establishment
fail)
Soft Handovers
34 Number of attempted intra Cell-Cause Cell shoAddIntraNodeBAtt
Node B branch additions (SHO addition)
per addition cause
36 Number of successful intra Cell-Cause Cell shoAddIntraNodeBSucc
Node B branch additions (SHO addition)
per addition cause
35 Number of unsuccessful Cell-Cause Cell shoAddIntraNodeBFail
intra Node B branch (SHO Fail)
additions per failure cause
46 Number of attempted intra Cell-Cause Cell shoAddIntraRncAtt
RNC branch additions per (SHO addition)
addition cause
48 Number of successful intra Cell-Cause Cell shoAddIntraRncSucc
addition cause
47 Number of unsuccessful Cell-Cause Cell shoAddIntraRncFail
intra RNC branch (SHO Fail)
58 Number of attempted inter Cell-Cause Cell shoAddInterRncAtt
addition cause
1-13
A50016-G5000-E202-3-7618

59 Number of successful inter Cell-Cause Cell shoAddInterRncSucc

addition cause
60 Number of unsuccessful Cell-Cause Cell shoAddInterRncFail
inter RNC branch (SHO Fail)
38 Number of attempted Cell-Cause Cell shoDelAtt
branch deletions per (SHO deletion)
deletion cause
50 Number of successful Cell-Cause Cell shoDelSucc
branch deletions per (SHO deletion)
deletion cause
170 Number of attempted AdjCell-Base Cell shoMoveOutAtt
outgoing radio link
addition movements per
adjacent cell
171 Number of successful AdjCell-Base Cell shoMoveOutSucc
outgoing radio link
addition movements per
adjacent cell
172 Number of failed outgoing AdjCell-Base Cell shoMoveOutFail
radio link addition (SHO Fail)
movements per failure
cause per adjacent cell
UTRAN Hard Handovers
30 Number of attempted intra Cell-Base Cell hhoAllOutAtt1
Node B outgoing hard
handovers per handover
type
Number of attempted intra Cell-Base Cell hhoAllOutAtt2
RNC outgoing hard
type
Number of attempted inter Cell-Base Cell hhoAllOutAtt3
RNC outgoing hard
type
1-14
A50016-G5000-E202-3-7618

30 Number of attempted inter Cell-Base Cell hhoAllOutAtt4

RAT outgoing hard
type
31 Number of successful intra Cell-Base Cell hhoAllOutSucc1
Node B outgoing hard
type
Number of successful intra Cell-Base Cell hhoAllOutSucc2
RNC outgoing hard
type
Number of successful inter Cell-Base Cell hhoAllOutSucc3
RNC outgoing hard
type
Number of successful inter Cell-Base Cell hhoAllOutSucc4
RAT outgoing hard
type
32 Number of unsuccessful Cell-Cause Cell hhoAllOutFail1
intra Node B outgoing hard (HHO Fail)
type per failure cause
Number of unsuccessful Cell-Cause Cell hhoAllOutFail2
intra RNC outgoing hard (HHO Fail)
inter RNC outgoing hard (HHO Fail)
inter RAT outgoing hard (Inter-System
handovers per handover HHO Fail)
65 Number of attempted intra Cell-Base Cell IntraRNCHhoAttInc
RNC incoming hard
handovers
1-15
A50016-G5000-E202-3-7618

66 Number of successful intra Cell-Base Cell IntraRNCHhoSuccInc

RNC incoming hard
handovers
67 Number of unsuccessful Cell-Cause Cell IntraRNCHhoFailInc
intra RNC incoming hard (HHO Fail)
handovers
27 Number of attempted AdjaCell-Base Cell HhoOutAttACM
outgoing hard handovers
per adjacent cell pair
28 Number of successful AdjaCell-Base Cell HhoOutSuccACM
outgoing hard handovers
per adjacent cell pair
29 Number of unsuccessful AdjaCell-Cause Cell HhoOutFailACM
outgoing hard handovers (HHO Fail)
per adjacent cell per failure
cause
Inter-System Hard Handovers
173 Number of attempted GSMCell-Base Cell interRatHoOutRelocAtt
relocation preparations for
outgoing inter-system
handovers per adjacent cell
pair per handover cause
174 Number of unsuccessful GSMCell-Cause Cell interRatHoOutRelocFail
relocation preparations for (Relocation Fail)
pair per failure cause
179 Number of successful Cell-Base Cell interRatHoSuccInc
incoming CS inter RAT
handovers
175 Number of attempted GSMCell-Base Cell interRatHoOutAtt
pair
177 Number of successful GSMCell-Base Cell interRatHoOutSucc
pair
1-16
A50016-G5000-E202-3-7618

176 Number of unsuccessful GSMCell-Cause Cell interRatHoOutFail

outgoing inter-system (Inter-system
handovers per adjacent cell HHO Fail)
pair
Relocation
180 Number of attempted RNC-Reloc- RNC relocOutAtt
outgoing relocation Cause
preparations per relocation (Relocation)
cause per relocation type
181 Number of unsuccessful RNC-Cause RNC relocOutFail
outgoing relocation (Relocation Fail)
preparations per failure
cause
182 Number of successful RNC-Reloc- RNC relocOutSucc
outgoing relocation Cause
preparations per relocation (Relocation)
cause per relocation type
183 Number of attempted RNC-Cause RNC relocIncAtt
incoming relocations per (Relocation)
relocation cause
184 Number of successful RNC-Cause RNC relocIncSucc
incoming relocations per (Relocation)
relocation cause
Iu Release
185 Number of Iu release Cell-CS/PS- Cell iuRelReq
requests per release cause Cause (Release
Request)
195 Number of Iu release RNC-CS/PS- RNC iuRelReqRNC
requests per release cause Cause (Release
RNC related Request)
186 Number of Iu release Cell-CS/PS- Cell iuRelCmd
commands per release Cause (Release
cause Command)
196 Number of Iu release RNC-CS/PS- RNC iuRelCmdRNC
commands per release Cause (Release
cause RNC related Command)
Number of drifting UEs
1-17
A50016-G5000-E202-3-7618

17 Number of drifting UEs AdjRNC-Base adjacent ShoAddDriftingUeSucc

RNC
Subsystem-Related Measurements
RNC Internal Measurements
20 RNC processor load RNC-CP RNC rncUsageRatio
23 DHT usage RNC-MMM RNC dhtUsage
187 DHT busy time RNC-Base RNC dhtBusyTime
24 DHT busy rate RNC-Base RNC dhtBusyRate
21 Number of attempted DHT RNC-Base RNC dhtAllocAtt
allocations
22 Number of successful RNC-Base RNC dhtAllocSucc
DHT allocations
188 PRLC usage RNC-MMM RNC prlcUsage
189 PRLC busy time RNC-Base RNC prlcBusyTime
76 PRLC busy rate RNC-Base RNC prlcBusyRate
190 Number of attempted RNC-Base RNC prlcAllocAtt
PRLC allocations
191 Number of successful RNC-Base RNC prlcAllocSucc
PRLC allocations
Iub Interface Measurements
140 Mean user data throughput Node B-CS/PS- Node B userThroughputDCIub
(uplink/downlink) on DL/UL
dedicated channels per
Node B
141 FACH traffic load in kbps Cell-Base Cell fachTrafficPs
per cell
Blocking Measurements
150 Number of rejections by Cell-Cause Cell acRejections
admission control per (Admission
cause Control)
1-18
A50016-G5000-E202-3-7618

151 Number of times Cell-Cause Cell ccTrigger

congestion control is (Congestion
activated per congestion Control)
cause
Channel Measurements
79 PCH usage rate Cell-Base Cell pchUsageRate
198 PCH discard rate Cell-Base Cell pchDiscardRate
199 FACH usage rate Cell-Base Cell fachUsageRate
200 FACH discard rate Cell-Base Cell fachDiscardRate
UE Quantity Measurements
205 Number of UEs per active Cell-RL Cell uesPerActiveLinkSetSize
link set size
152 Mean number of bearer Cell-Bearer Cell bearServiceperCell
services per cell related Service
RRC State Management
121 Number of attempted Cell-Target Cell transFromCellDchAtt
transitions from
CELL_DCH state
122 Number of unsuccessful Cell-Target- Cell transFromCellDchFail
transitions from Cause
CELL_DCH state per (RRC State Fail)
failure cause
123 Number of attempted Cell-Target Cell transFromCellFachAtt
transitions from
CELL_FACH state
124 Number of unsuccessful Cell-Target- Cell transFromCellFachFail
transitions from Cause
CELL_FACH state per (RRC State Fail)
failure cause
127 Number of attempted Cell-Base Cell transFromCellPchAtt
transitions from
CELL_PCH state
1-19
A50016-G5000-E202-3-7618

128 Number of unsuccessful Cell-Cause Cell transFromCellPchFail

transitions from (RRC State Fail)
CELL_PCH state per
failure cause
133 Number of attempted RNC-Base RNC transFromUraPchAtt
transitions from
URA_PCH state
134 Number of unsuccessful RNC-Cause RNC transFromUraPchFail
transitions from (RRC State Fail)
URA_PCH state per
failure cause
Radio Measurements
206 Received total wide band Cell-MMM Cell uuRecTotalWbPwr
power
99 Transmitted carrier power Cell-MMM Cell uuTransmCarrierPwr
82 Number of used codes per Cell-SF-DL/UL Cell uuCodesUsed
spreading factor
102 Number of attempted code Cell-SF-DL/UL Cell uuCodeReqAtt
requests per spreading
factor
221 Number of successful code Cell-SF-DL/UL Cell uuCodeReqSucc
requests per spreading
factor
ATM-Related Measurements
ATM Measurements
207 Ingress cells (for STM-1, ATM-Base Line lineIncomingCells
E1)
208 Egress cells (for STM-1, ATM-Base Line lineOutgoingCells
E1)
209 Ingress cells for VPC/VCC ATM-Base VP/VC vpvcIncomingCells
(for STM-1)
210 Egress cells for VPC/VCC ATM-Base VP/VC vpvcOutgoingCells
(for STM-1)
211 Cells discarded due to ATM-Base Line discardedCellsHecViolation
HEC violations (for E1)
1-20
A50016-G5000-E202-3-7618

212 Discarded cells due to ATM-Base Line discardedCellsCongestion

congestion (for STM-1)
216 Cell loss ratio (for STM-1) ATM-Base VP cellLossRatio
217 Congestion of VP ATM-Base VP congestionOfVP
(for STM-1)
1-21
A50016-G5000-E202-3-7618
1.2.4 Parameters in string of measTypes tag
1.2.4.1 Cause parameters

Cause values to be reported should be identical to the one defined in the
referenced protocol specification (3GPP).
Note: “Other” is used when the causes other than specified in the
following tables occur.
Table 1-3 Paging Cause Type
ID Description
3,0,0 Terminating conversational call

3,0,1 Terminating streaming call
3.0,2 Terminating interactive call
3,0,3 Terminating background call
3,0,4 Terminating high priority signaling
3,0,5 Terminating low priority signaling
3,0,6 Terminating - cause unknown
Other Other causes
Note: For the causes of “paging1CellUtran” and

“paging1UraUtran”, only “3,0,6” and “Other”apply from
the table above.
Table 1-4 RRC Protocol Error Cause Type
ID Description
3,3,1 ASN.1 violation or encoding error

3,3,2 Message type non-existent or not implemented
3.3,3 Message not compatible with receiver state
3,3,4 Information element value not comprehended
3,3,5 Conditional information element error
3,3,6 Message extension not comprehended
NoReply No reply
Other Other causes
1-22
A50016-G5000-E202-3-7618
Table 1-5 Establishment Cause Type (RRC Establishments)
ID Description
3,0,0 Originating conversational call

3,0,1 Originating streaming call
3.0,2 Originating interactive call
3,0,3 Originating background call
3,0,4 Originating subscribed traffic call
3,0,5 Terminating conversational call
3,0,6 Terminating streaming call
3,0,7 Terminating interactive call
3,0,8 Terminating background call
3.0,9 Emergency call
3,0,10 Inter-RAT cell re-selection
3,0,11 Inter-RAT cell change order
3,0,12 Registration
3,0,13 Detach
3.0,14 Originating high priority signaling
3,0,15 Originating low priority signaling
3,0,16 Cell re-establishment
3,0,17 Terminating high priority signaling
3,0,18 Terminating low priority signaling
3,0,19 Terminating - cause unknown
Other Other causes
1-23
A50016-G5000-E202-3-7618
Table 1-6 Reject Cause Type (RRC Connection Establishment Failure)
ID Description
3,0,0 Congestion
3,0,1 Unspecified
NoReply No reply
Other Other causes
Table 1-7 RRC Release Cause Type (RRC Release)
ID Description
3,0,0 Normal event

3,0,1 Unspecified
3.0,2 Pre-emptive release
3,0,3 Congestion
3,0,4 Re-establishment reject
3,0,5 Directed signaling connection re-establishment
3,0,6 User inactivity
Other Other causes
1-24
A50016-G5000-E202-3-7618
Table 1-8 RAB Fail Cause Type (RAB Establishment Failure)
ID Description
2,4,6 Relocation triggered

2,4,8 Unable to establish during relocation
2,4,12 Requested ciphering and/or integrity protection algorithms not supported
2,4,14 Failure in the radio interface procedure
2,4,18 Requested traffic class not available
2,4,19 Invalid RAB parameters value
2,4,21 Requested guaranteed bit rate not available
2,4,23 Invalid RAB parameters combination
2,4,24 Condition violation for SDU parameters
2,4,30 Invalid RAB ID
2,4,32 Interaction with other procedure
2,4,35 Requested guaranteed bit rate for DL not available
2,4,36 Requested guaranteed bit rate for UL not available
2,4,39 Request superseded
2,4,45 Directed Retry
2,5,66 Iu transport connection failed to establish
2,7,97 Transfer syntax error
2,7,98 Semantic error
2,7,99 Message not compatible with receiver state
2,7,100 Abstract syntax error (Reject)
2,7,101 Abstract syntax error (Ignore and notify)
2,7,102 Abstract syntax error (Falsely constructed message)
2,8,114 No resource available
2,8,115 Unspecified failure
Other Other causes
1-25
A50016-G5000-E202-3-7618
Table 1-9 RAB Release Cause Type (RAB Releases)
ID Description
2,4,14 Failure in the Radio Interface Procedure

2,4,15 Release due to UTRAN generated reason
2,4,28 Iu UP failure
2,4,37 Repeated integrity checking failure
2,4,40 Release due to UE generated signaling connection release
2,4,45 Directed retry
2,4,46 Radio Connection With UE Lost
2,6,83 Normal release
2,8,113 O&M intervention
Other Other causes
Note: For the causes of “rabRel”, “2,4,14”, “2,4,40”, “2,4,45”

and “2,4,46” do not apply from the table above.
1-26
A50016-G5000-E202-3-7618
Table 1-10 Channel Reconf Fail Cause Type (Transport Channel Reconf/Physical Channel
Reconf)
ID Description
3,2,1 Configuration unsupported

3,2,2 Physical channel failure
3,2,3 Incompatible simultaneous reconfiguration
3,2,4 Compressed mode runtime error
3,2,5 Protocol error
3,2,6 Cell update occurred
3,2,7 Invalid configuration
3,2,8 Configuration incomplete
3,2,9 Unsupported measurement
NoReply No reply
Other Other causes
Table 1-11 Cell Update Cause Type
ID Description
3,0,0 Cell re-selection

3,0,1 Periodical cell update
3,0,2 Uplink data transmission
3,0,3 Paging response
3,0,4 Re-entered service area
3,0,5 Radio link failure
3,0,6 RLC unrecoverable error
Other Other causes
Note: For the causes of “cellUpdateInc”, only “3,0,0” and

“3,0,4”apply from the table above.
1-27
A50016-G5000-E202-3-7618
Table 1-12 URA Update Cause Type
ID Description
3,0,0 Change of URA

3,0,1 Periodic URA update
Other Other causes
Table 1-13 Radio Link Fail Cause Type (Radio Link)
ID Description
4,4,10 Synchronization failure

4,4,17 Invalid CM settings
4,5,0 Transport resource unavailable
4,8,0 Control processing overload
4,8,1 HW failure
Other Other causes
Table 1-14 Radio Link Fail Cause Type (Radio Link Establishment) (1/2)
ID Description
4,4,0 Unknown C-ID

4,4,1 Cell not available
4,4,2 Power level not supported
4,4,3 DL radio resources not available
4,4,4 UL radio resources not available
4,4,5 RL already activated/allocated
4,4,6 Node B resources unavailable
4,4,9 Requested configuration not supported
4,4,14 Unspecified
4,4,19 Number of DL codes not supported
1-28
A50016-G5000-E202-3-7618
Table 1-14 Radio Link Fail Cause Type (Radio Link Establishment) (2/2)
ID Description
4,4,22 UL SF not supported

4,4,23 DL SF not supported
4,4,25 Dedicated transport channel type not supported
4,4,28 CM not supported
4,4,31 Number of UL codes not supported
4,5,0 Transport resource unavailable
4,5,1 Unspecified
4,8,1 HW failure
4,8,3 Not enough user plane processing resources
4,8,4 Unspecified
NoReply No reply
Other Other causes
Table 1-15 SHO Addition Cause Type (Soft HO Branch Additions)
ID Description
1,9,1 CPICH comparison (1A)

1,9,2 CPICH comparison (1A’)
1,9,4 CPICH comparison (1C)
Other Other causes
1-29
A50016-G5000-E202-3-7618
Table 1-16 SHO Fail Cause Type (Soft HO Branch Additions) (1/2)
ID Description
6,4,0 Unknown C-Id

6,4,1 Cell not available
6,4,2 Power level not supported
6,4,3 DL radio resource not available
6,4,4 UL radio resource not available
6,4,5 RL already activated/allocated
6,4,6 Node B resources unavailable
6,4,7 Combining resources not available
6,4,8 Requested configuration not supported
6,4,9 Unspecified (radio network layer cause)
6,4,10 Measurement temporarily not available
6,4,12 Reconfiguration CFN not elapsed
6,4,13 Number of DL codes not supported
6,4,14 Combining not supported
6,4,15 UL SF not supported
6,4,16 DL SF not supported
6,4,17 Dedicated transport channel type not supported
6,4,18 CM not supported
6,4,19 UL scrambling code already in use
6,4,20 Transaction not supported by destination Node B
6,4,21 Number of UL codes not supported
6,5,0 Transport resources unavailable
6,5,1 Unspecified (Transport layer cause)
6,7,0 Transfer syntax error
6,7,1 Abstract syntax error (Reject)
6,7,2 Abstract syntax error (Ignore and notify)
1-30
A50016-G5000-E202-3-7618
Table 1-16 SHO Fail Cause Type (Soft HO Branch Additions) (2/2)
ID Description
6,7,3 Message not compatible with receiver state

6,7,4 Semantic error
6,7,5 Unspecified (Protocol cause)
6,7,6 Abstract syntax error (Falsely constructed message)
6,8,1 HW failure
6,8,3 Not enough user plane processing resources
6,8,4 Unspecified (Miscellaneous cause)
3,2,3 Incomplete simultaneous reconfiguration
3,2,9 Unsupported measurement
NoReply No reply
Other Other causes
Table 1-17 SHO Deletion Cause Type (Soft HO Branch Deletions)
ID Description
1,9,3 CPICH comparison (1B)

1,9,4 CPICH comparison (1C)
Other Other causes
1-31
A50016-G5000-E202-3-7618
Table 1-18 HHO Fail Cause Type (HHO - General)
ID Description

NoReply No reply
Other Other causes
Table 1-19 Inter-system HHO Fail Cause Type (Inter-system Handovers)
ID Description
3,1,1 Configuration unacceptable

3,1,4 Inter-RAT protocol error
3,2,1 Configuration unacceptable
Other Other causes
1-32
A50016-G5000-E202-3-7618
Table 1-20 Relocation Cause Type (Relocations)
ID Description
2,4,41 Resource optimization relocation

2,4,43 Relocation desirable for radio reasons
Other Other causes
Table 1-21 Relocation Fail Cause Type (Relocations)
ID Description
2,4,7 TRELOCalloc expiry

2,4,9 Unknown target RNC
2,4,10 Relocation cancelled
2,4,29 Relocation failure in target CN/RNC or target system
2,4,44 Relocation not supported in target RNC or target system
Other Other causes
Table 1-22 Release Request Cause Type (Iu Release Request)
ID Description

2,4,46 Radio connection with UE lost
Other Other causes
1-33
A50016-G5000-E202-3-7618
Table 1-23 Release Command Cause Type (Iu Release Command)
ID Description
2,4,10 Relocation canceled

2,4,11 Successful relocation
2,4,31 No remaining RAB
2,4,46 Radio connection with UE lost
2,6,83 Normal release
Other Other causes
Table 1-24 Rejection Cause Type (Admission Control)
ID Description
1,9,5 Call restriction

1,9,6 Maximum uplink load failure
1,9,7 Maximum downlink load failure
1,9,8 Code allocation failure
1,9,9 Congestion Control
Other Other causes
1-34
A50016-G5000-E202-3-7618
Table 1-25 Congestion Control Cause Type
ID Description
1,9,10 Uplink received total wide band power

1,9,11 Downlink received total wide band power
Other Other causes
Table 1-26 RRC State Fail Cause Type (RRC State Transitions)
ID Description

NoReply No reply
Other Other causes
1.2.4.2 CS/PS parameter

The number of IDs for CS/PS parameter is static.
1-35
A50016-G5000-E202-3-7618
Table 1-27 CS/PS Parameter
ID Description
0 CS
1 PS
1.2.4.3 DL/UL parameter

The number of IDs for DL/UL parameter is static.
Table 1-28 DL/UL Parameter
ID Description
0 DL
1 UL (Note)
Note: When mtyp=82, 102, or 221, this parameter is not output to

the RNC measurement report files.
1-36
A50016-G5000-E202-3-7618
1.2.4.4 RAB type parameters

The number of IDs for RAB type parameter is static.
Table 1-29 RAB Type Parameter
ID Description
0 FACH
1 CS AMR speech 12.2 /12.2
2 CS conversational UDI 64/64
4 CS conversational UDI 28.8 /28.8
5 PS conversational UDI 8/8
6 PS conversational 16/16
7 CS streaming 57.6/57.6
10 PS streaming 16/64
15 PS interactive/background 64/64
Other Other causes
1-37
A50016-G5000-E202-3-7618
1.2.4.5 Handover type parameters

The number of IDs for handover parameter is static.
Table 1-30 Handover Type Parameter
ID Description
0 Intra cell (Not supported) (Note)

1 Intra-Node B
2 Inter-Node B, Intra-RNC
3 Inter-RNC
4 Outgoing inter-RAT (Inter-system)
Note: This parameter is not output to the RNC measurement report

files.
1.2.4.6 Mean/Min./Max. parameters

The number of IDs for Mean/Min./Max. parameter is static.
Table 1-31 Mean/Min./Max. Type Parameter
ID Description
0 Mean
1 Minimum
2 Maximum
1.2.4.7 Target state parameters

Table 1-32 Target State Parameter
ID Description
0 CELL_DCH (Note 1)
1 CELL_FACH (Note 2)
2 CELL_PCH
3 URA_PCH
Notes:
1 For measurements of “transFromCellDchAtt” and
1-38
A50016-G5000-E202-3-7618
“transFromCellDchSucc”, this parameter is not output to the

RNC measurement report files.
2 For measurements of “transFromCellFachAtt” and
“transFromCellFachSucc”, this parameter is not output to the
RNC measurement report files.
1.2.4.8 Spreading factor parameters

The number of IDs for spreading factor parameter is static.
Table 1-33 Spreading Factor Parameter
ID Description
0 SF4
1 SF8
2 SF16
3 SF32
4 SF64
5 SF128
6 SF256
7 SF512
1.2.4.9 Relocation parameter

The number of IDs for relocation parameter is static.
Table 1-34 Relocation Parameter
ID Description
0 UE not involved
1 UE involved (Not supported) (Note)
Note: This parameter is not output to the RNC measurement report

files.
1-39
A50016-G5000-E202-3-7618
1.2.4.10 AP load / CP load parameter

The number of IDs for AP load / CP load parameter is static.
Table 1-35 AP Load / CP Load Parameter
ID Description
0 AP load
1 CP load
1.2.4.11 Active link set size parameter

The number of IDs for active link set size parameter is static.
Table 1-36 Active Link Set Size Parameter
ID Description
1 Active link set size = 1

1.2.4.12 Bearer service parameters

The number of IDs for bearer service parameter is static.
Table 1-37 Bearer Service Parameter (1/2)
ID Description
0 SRB 3.4/3.4
1 SRB 13.6/13.6
2 PS interactive/background in CELL_FACH state
3 PS interactive/background in CELL_PCH state
4 CS AMR speech 12.2
7 CS conversational UDI 28.8/28.8
1-40
A50016-G5000-E202-3-7618
Table 1-37 Bearer Service Parameter (2/2)
ID Description
1-41
A50016-G5000-E202-3-7618
1.3 Suspect Flag

In case collected traffic data cannot guarantee their own rightness, it is
necessary to notify maintenance personnel that a suspect flag is on. When
it is possible that right data could not be collected within a measurement
period, the suspect flag is set on and kept until next data collection request.
Causes to set the suspect flag, i.e., cases that collected data cannot be
guaranteed, are shown below:
(1) When command is input
(2) When system restart is generated
(3) When system clock is changed
(4) While objective equipment is faulty
(5) Due to measurement item cause
(6) Due to Performance Measurement (PM) inside cause
1.3.1 When command is input

• cre pmc
In case the command is input within a measurement period, the
suspect flag is set to all measurement objects of a scanner that is set
by the command.
• mod pmc
(1) Measurement interval:
The suspect flag is set to all measurement objects of an
objective scanner.
(2) Measurement object:
The suspect flag is set to the measurement object.
• lock pmc
suspect flag is set to all measurement objects of an objective
scanner.
• ulock pmc
suspect flag is set to all measurement objects of an objective
scanner.
1-42
A50016-G5000-E202-3-7618
1.3.2 When system restart is generated

At the first measurement interval within system restart Phase 1 or more,
the suspect flag is set to all measurement objects of all scanners.
1.3.3 When system clock is changed

When the system clock is adjusted more than 1 percent of the
measurement interval, the suspect flag is set to all measurement objects of
all scanners.
1-43
A50016-G5000-E202-3-7618
1.3.4 While objective equipment is faulty
1.3.4.1 Equipment related to Node B

When Node B related equipment detects its own fault, the cell state
monitored is changed from “enable” to “disable”, the suspect flag is set to
measurement object cells of all scanners related to the Node B.
Even if the cell state monitored is changed from “not existing/disable” to

“enable” within a measurement period after the suspect flag was on, the
suspect flag is not set off because the rightness of data collected in faulty
state cannot be guaranteed; thus the suspect flag will be set off in the next
interval.
1.3.4.2 Equipment related to ATM

(1) DTI
• In case an objective DTI line is the state except “USE”, the
suspect flag is set to the measurement object.
Even if the objective DTI line is changed to “USE” within a
measurement period after the suspect flag was on, the suspect
flag is not set off because the rightness of data collected in
faulty state cannot be guaranteed; thus the suspect flag will be
set off in the next interval.
• In case of signal error from forward line (also including
measurement start request interval to forward line)
(2) STM-1
In case an objective STM-1 line is the state except “USE”, the
suspect flag is set to the measurement object.
Even if the objective STM-1 line is changed to “USE” within a
measurement period after the suspect flag was on, the suspect flag
is not set off because the rightness of data collected in faulty state
cannot be guaranteed; thus the suspect flag will be set off in the
next interval.
(3) VP
In case an objective VCI is the state except “USE”, the suspect flag
is set to the measurement object.
Even if the objective VCI is changed to “USE” within a
measurement period after the suspect flag was on, the suspect flag
is not set off because the rightness of data collected in faulty state
cannot be guaranteed; thus the suspect flag will be set off in the
next interval.
1-44
A50016-G5000-E202-3-7618
1.3.5 Due to measurement item cause

Some measurement items have their own causes to set the suspect flag.
The table below shows suspect flag cause inherent in measurement item.
Table 1-38 Measurement Item Cause (1/2)
mtype sctyp
(Measurement (Scanner Type) Cause
Type)
In case the total number of line seizure requests proceeds

21 RNC 0xffffffff at a measurement interval of an objective scanner,
the suspect flag is set to the measurement object.
In case the total number of line seizure successes proceeds
In case the total number of lines in use proceeds 0xffffffff at a
23 RNC measurement interval of an objective scanner, the suspect flag
In case the total number of line seizure successes proceeds
1-45
A50016-G5000-E202-3-7618
Table 1-38 Measurement Item Cause (2/2)
mtype sctyp
(Measurement (Scanner Type) Cause
Type)
In case the total number of PCH signals sent to a

measurement object proceeds 0xffffffff at a measurement
79 CELL
interval of an objective scanner, the suspect flag is set to the
measurement object.
In case a measurement value of a measurement object
99 CELL proceeds 0xffffffff at a measurement interval of an objective
scanner, the suspect flag is set to the measurement object.
In case the total number of discarded PagingRecord messages
to a measurement object proceeds 0xffffffff at a measurement
measurement object.
198 CELL
In case the total number of received PagingRecord messages
to a measurement object proceeds 0xffffffff at a measurement
measurement object.
In case the total number of FACH Transaction Bearers (TBs)
sent to a measurement object proceeds 0xffffffff at a
199 CELL
measurement interval of an objective scanner, the suspect flag
In case the total number of discarded FACH TBs to a
measurement object proceeds 0xffffffff at a measurement
measurement object.
200 CELL
In case the total number of discarded FACH TBs + FACH
TBs sent to a measurement object proceeds 0xffffffff at a
measurement interval of an objective scanner, the suspect flag
In case a measurement value of a measurement object
206 CELL proceeds 0xffffffff at a measurement interval of an objective
scanner, the suspect flag is set to the measurement object.
1-46
A50016-G5000-E202-3-7618
1.3.6 Due to PM inside cause

Due to PM software cause, the suspect flag is set to all measurement
objects of all scanners. For example,
(1) System cause (inter-processor communication failure)
(2) Program error (system call NG)
1.3.7 Limitation of PM file size

The limitation of PM file size occupying disk area in the RNC is up to 500
MB. However, PM files are frequently created and will be increased soon.
To operate PM counters better, take note of the following points:
• When files are increasing up to 500 MB, delete unnecessary files

immediately.
• Set necessary PM counters efficiently.
1-47
47 Pages
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03
SECTION 2
Common Information for
RNC Measurements
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03 Common Information for RNC Measurements
2. Common Information for RNC

Measurements
2.1 Encoding of “per cause” Measurements

Radio Network Controller (RNC) measurements, which are collected “per
cause” (mainly those described in the chapter “Procedure-related
Measurements”), consider the following issues:
• The preferred encoding rule for “per cause” measurements in the

measurement result file is to concatenate an integer value to the
shortname, e.g. MeasType = “rrcEstabFail.1”. The integer value is
identical to the one defined in the referred protocol specification
(e.g. Radio Resource Control (RRC), Radio Access Network
Application Part (RANAP)).
• If non-receipt of an expected confirmation message is one of the

(failure) causes, the related counter is described concatenation of
“.NoReply” to the shortname, e.g. MeasType =
“rrcEstabFail.NoReply”.
• The summarized value of all counter values is identical to the total

number of events, which occurred for the condition of this
measurement (i.e. for every event related to the selected object, e.g.
cell, the one and only counter is increased).
2.2 Adjacent Cell Measurements (ACMs)

All ACMs are measurements, which are related to a dedicated cell (“center
cell”) from administrative point of view, but focused on all single relations
to neighbor UTRAN or GERAN cells (“adjacent cells”).
The purpose of ACMs is to
• observe the mobility of User Equipment (UE),
• localize hot spots in handover/movement failures.
Administration of ACMs is done by a normal cell scanner, i.e., the

operator can select the center cell only.
After activation of this scanner, the RNC collects the results of all (max.
64) adjacent cell relations from/to the center cell separately.
The adjacent cell relationship is described in the measObjInstId field of the

measurement result file by the following syntax:
• “Incoming” measurements: “<adjacent cell>-<center cell>”
2-1
A50016-G5000-E202-3-7618
• “Outgoing” measurements: “<center cell>-<adjacent cell>”
Adjacent cells belonging to a different Radio Network System (RNS) are

described by the UMTS Cell Id (rncld + cellId).
Adjacent GSM cells are described by the Cell Global Id (CGI), as defined
in GSM recommendations.
In addition, a further subcounter may be added for each cause, which

summarizes all handover/movements between the center cell and unknown
originating/target cells:
• “Incoming” measurements: “others-<center cell>”
• “Outgoing” measurements: “<center cell>-others”
2.3 Active Link Set VS Most Recently Added Cell

Some measurements are not really related to one dedicated cell, but to an
active link set, which in case of soft handover comprises more than one
cell.
There are two different approaches for these measurements:
(a) “All cells” approach:

Measurement is considered for every cell of the active link set.
(b) “Newest cell” approach:

Measurement is considered for the most recently added cell of the
active link set only.
The following table shows which approach is used for which

measurement:
2-2
A50016-G5000-E202-3-7618
Table 2-1 Relationship between Measurements and Approaches
Measurement All Cells Newest Cell
rrcRelDcch X
sigConnRel* X
rabEstabType* X
rabRel X
rabRelUTRANOrigin X
rabRelCNOrigin X
traChReconf* X
phyChReconf* X
cellUpdateInc X
shoMoveOut* X
hhoAllOut* X
interRatHoOut* X
iuRel* X
uesPerActiveLinkSetSize X
transFromCellDch* X
HhoOut***ACM X
bearServiceperCell X
Note: Trigger events sent from CP to O&M post-processing always

carry the complete active link set, independent of the table above.
2-3
3 Pages
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03
SECTION 3
Procedure-Related Measurements
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03 Procedure-Related Measurements
3. Procedure-Related Measurements
3.1 Paging
3.1.1 Number of CN originated pagings type 1 per paging cause

(a) This measurement provides the number of CN originated paging
type 1. For each paging cause a separate subcounter is defined.
(b) CC.
(c) Transmission of an RRC-message PAGAING TYPE 1 message

sent by the UTRAN to the UE. For each paging record the
appropriate counter is increased. Paging causes are defined within
3GPP TS25.331.
(d) An integer value for each paging cause.

• 3,0,0
Terminating conversational call
• 3,0,1
Terminating streaming call
• 3,0,2
Terminating interactive call
• 3,0,3
Terminating background call
• 3,0,4
Terminating high priority signaling
• 3,0,5
Terminating low priority signaling
• 3,0,6
Terminating - cause unknown
• Other
Other causes
(e) paging1Cn
(f) Administratable per RNC.
(g) RNC measurement function.
(h) 111
(i) When RRC PAGING TYPE1 is sent (CN)
3-1
A50016-G5000-E202-3-7618
3.1.2 Number of CN originated pagings type 2 per paging cause

(a) This measurement provides the number of RNC originated paging
type 2 for each cell. For each paging cause a separate subcounter is
defined.
(b) CC.

sent by the UTRAN to the UE. If the UE is in soft handover, the
appropriate counter is increased for every connected cell. Paging
causes are defined within 3GPP TS25.331.

• 3,0,0
• 3,0,1
• 3,0,2
• 3,0,3
• 3,0,4
• 3,0,5
• 3,0,6
• Other
Other causes
(e) paging2Cn
(f) Administratable per Cell.
(g) Cell measurement function.
(h) 158
(i) When RRC PAGING TYPE2 is sent (CN)
3-2
A50016-G5000-E202-3-7618
3.1.3 Number of UTRAN originated pagings type 1 in CELL_PCH per

paging cause
type 1 in CELL_PCH state for each cell. For each paging cause a
separate subcounter is defined.
(b) CC.

sent by the UTRAN to the UE in CELL_PCH state. Paging causes
are defined within 3GPP TS25.331.

• 3,0,6
• Other
Other causes
(e) paging1CellUtran
(h) 112
(i) When RRC PAGING TYPE1 is sent (Cell_PCH State)
3.1.4 Number of UTRAN originated pagings type 1 in URA_PCH per

paging cause
type 1 in URA_PCH state for each cell. For each paging cause a
(b) CC.

sent by the UTRAN to the UE. Paging causes are defined within
3GPP TS25.331.

• 3,0,6
• Other
3-3
A50016-G5000-E202-3-7618
Other causes
(e) paging1UraUtran
(h) 14
(i) When RRC PAGING TYPE1 is sent (URA_PCH State)
3.1.5 Number of failed pagings in CELL_PCH per failure cause

(a) This measurement provides the failed pagings in CELL_PCH state
for each cell. For each failure cause a separate subcounter is
defined.
(b) CC.
(c) Possible paging failure causes are the following:

(1) Timeout in the RNC while waiting for the UE to respond on
the PAGING TYPE 1 message in CELL_PCH state, e.g.,
during Cell Update procedure.
(2) Receipt of an RRC STATUS in response to a PAGING TYPE
1 message, indicating a protocol error. Causes are defined
within the Information Element “Protocol Error Information,”
as described in 3GPP TS25.331.
(d) An integer value for each failure cause.

• 3,3,1
ASN.1 violation or encoding error
• 3,3,2
Message type non-existent or not implemented
• 3,3,3
Message not compatible with receiver state
• 3,3,4
Information element value not comprehended
• 3,3,5
Conditional information element error
• 3,3,6
Message extension not comprehended
• NoReply
No reply
3-4
A50016-G5000-E202-3-7618
• Other
Other causes
(e) pagingCellFail
(h) 113
(i) When one of the following conditions is satisfied:

• When RRC STATUS is received (Cell_PCH State)
• When SUEPageCellUpdate Timer expires
3.1.6 Number of failed pagings in URA_PCH per failure cause

(a) This measurement provides the failed pagings in URA_PCH state.
For each failure cause a separate subcounter is defined.
(b) CC.
(c) Possible paging failure causes are the following:

(1) Timeout in the RNC while waiting for the UE to respond on
the PAGING TYPE 1 message, e.g., during Cell Update
procedure.
(2) Receipt of an RRC STATUS in response to a PAGING TYPE
1 message, indicating a protocol error. Causes are defined
within the Information Element “Protocol Error Information,”
as described in 3GPP TS25.331.

• 3,3,1
ASN.1 violation or encoding error
• 3,3,2
Message type non-existent or not implemented
• 3,3,3
• 3,3,4
Information element value not comprehended
• 3,3,5
Conditional information element error
• 3,3,6
Message extension not comprehended
3-5
A50016-G5000-E202-3-7618
• NoReply
No reply
• Other
Other causes
(e) pagingUraFail
(h) 15

• When RRC STATUS is received (URA_PCH State)
• When SUEPageCellUpdate Timer expires
3.2 RRC Connections
3.2.1 Number of attempted RRC connection establishments per

establishment cause
(a) This measurement provides the number of attempted RRC
connection establishment procedures for each cell. For each
establishment cause a separate subcounter is defined.
(b) CC.
(c) Receipt of an RRC CONNECTION REQUEST message sent by

the UE to the UTRAN. Establishment causes are defined within
3GPP TS25.331.
(d) An integer value for each establishment cause.

• 3,0,0
Originating Conversational Call
• 3,0,1
Originating streaming call
• 3,0,2
Originating interactive call
• 3,0,3
Originating background call
• 3,0,4
Originating subscribed traffic call
3-6
A50016-G5000-E202-3-7618
• 3,0,5
• 3,0,6
• 3,0,7
• 3,0,8
• 3,0,9
Emergency call
• 3,0,10
Inter-RAT cell re-selection
• 3,0,11
Inter-RAT cell change order
• 3,0,12
Registration
• 3,0,13
Detach
• 3,0,14
Originating high priority signaling
• 3,0,15
Originating low priority signaling
• 3,0,16
Call Re-establishment
• 3,0,17
• 3,0,18
• 3,0,19
• Other
Other causes
(e) rrcEstabAtt
(h) 1
3-7
A50016-G5000-E202-3-7618
(i) When RRC CONNECTION REQUEST is received
3.2.2 Number of successful RRC connection establishments per

establishment cause
(a) This measurement provides the number of successful RRC
connection establishment procedures for each cell. The same
causes are distinguished as in the previous measurement “number
of attempted RRC connection establishment procedures per
establishment cause.
(b) CC.
(c) Receipt of an RRC CONNECTION SETUP COMPLETE message

sent by the UE to the UTRAN.
The establishment causes are defined within 3GPP TS25.331.
(d) An integer value for each establishment cause.

• 3,0,0
Originating Conversational Call
• 3,0,1
Originating streaming call
• 3,0,2
Originating interactive call
• 3,0,3
Originating background call
• 3,0,4
Originating subscribed traffic call
• 3,0,5
• 3,0,6
• 3,0,7
• 3,0,8
• 3,0,9
Emergency call
• 3,0,10
Inter-RAT cell re-selection
• 3,0,11
3-8
A50016-G5000-E202-3-7618
Inter-RAT cell change order

• 3,0,12
Registration
• 3,0,13
Detach
• 3,0,14
Originating high priority signaling
• 3,0,15
Originating low priority signaling
• 3,0,16
Call Re-establishment
• 3,0,17
• 3,0,18
• 3,0,19
• Other
Other causes
(e) rrcEstabSucc
(h) 2
(i) When RRC CONNECTION SETUP COMPLETE is received
3.2.3 Number of failed RRC connection establishments per failure

cause
(a) This measurement provides the number of RRC establishment
failures for each cell. For each failure cause a separate subcounter
is defined.
(b) CC.
(c) The measurement counts the number of RRC establishment

attempts which have not evolved into an RRC establishment.
Establishment failure causes are the rejection causes of RRC
CONNECTION REJECT, listed in 3GPP TS25.331, plus an
expected RRC CONNECTION SETUP COMPLETE receipt by
3-9
A50016-G5000-E202-3-7618
the RNC which has not happened.

• 3,0,0
Congestion
• 3,0,1
Unspecified
• NoReply
No reply
• Other
Other causes
(e) rrcEstabFail
(h) 107

• When RRC CONNECTION REJECT is sent
• When RRC CONNECTION SETUP COMPLETE wait timer
expires
3.2.4 Number of attempted RRC connection releases on DCCH per

release cause
(a) The measurement provides the number of attempted RRC
connection releases on DCCH recorded by the RNC for each cell.
For each release cause a separate subcounter is defined.
(b) CC.
(c) RRC CONNECTION RELEASE message sent from the UTRAN

to the UE related to an RRC connection release. Only release
messages sent on DCCH are considered. The release causes are
defined within the RRC connection release message specified in
3GPP TS25.331.
(d) An integer value for each release cause.

• 3,0,0
Normal event
• 3,0,1
3-10
A50016-G5000-E202-3-7618
Unspecified
• 3,0,2
Pre-emptive release
• 3,0,3
Congestion
• 3,0,4
Re-establishment reject
• 3,0,5
Directed signaling connection re-establishment
• 3,0,6
User inactivity
• Other
Other causes
(e) rrcRelDcch
(h) 159
(i) When RRC CONNECTION RELEASE (DCCH) is sent
3.2.5 Number of attempted RRC connection releases on CCCH per

release cause
(a) The measurement provides the number of attempted RRC
connection releases on CCCH recorded by the RNC for each cell.
For each release cause a separate subcounter is defined.
(b) CC.
(c) RRC CONNECTION RELEASE message sent from the UTRAN

to the UE related to an RRC connection release. Only release
messages sent on CCCH are considered. The release causes are
defined within the RRC connection release message specified in
3GPP TS25.331.
(d) An integer value for each release cause.

• 3,0,0
Normal event
• 3,0,1
Unspecified
3-11
A50016-G5000-E202-3-7618
• 3,0,2
Pre-emptive release
• 3,0,3
Congestion
• 3,0,4
Re-establishment reject
• 3,0,5
Directed signaling connection re-establishment
• 3,0,6
User inactivity
• Other
Other causes
(e) rrcRelCcch
(h) 160
(i) When RRC CONNECTION RELEASE (CCCH) is sent
3.3 Signaling Connections
3.3.1 Number of attempted signaling connection establishments

(a) This measurement provides the number of requests by RNC to
establish an Iu control plane connection between the RNC and a
CN. CS and PS connections are separated.
(b) CC.
(c) Sending of a RANAP-message INITIAL UE MESSAGE sent by

the RNC to the CN. This is sent by the RNC on receipt of an RRC
Initial Direct Transfer message from the UE.
(d) An integer value for each CS and PS.

• 0
CS
• 1
PS
(e) sigConnEstabReq
3-12
A50016-G5000-E202-3-7618
(h) 161
(i) When RANAP INITIAL UE MESSAGE is sent
3.3.2 Number of signaling connection release requests

(a) The measurement provides the number of attempted signaling
connection release request procedures for each cell.
(b) CC.
(c) Receipt of a SIGNALING CONNECTION RELEASE REQUEST

message sent by the UE to the UTRAN.
(d) An integer value.
(e) sigConnRelReq
(h) 162
(i) When RRC SIGNALING CONNECTION RELEASE REQUEST

is received
3.3.3 Number of signaling connection releases

(a) The measurement provides the number of signaling connection
release procedures for each cell.
(b) CC.
(c) Transmission of a SIGNALING CONNECTION RELEASE

message sent by the UTRAN to the UE.
(e) sigConnRelNotif
(h) 163
3-13
A50016-G5000-E202-3-7618
(i) When RRC SIGNALING CONNECTION RELEASE is sent
3.4 RAB Assignment
3.4.1 Number of attempted RAB establishments per RAB type

(a) This measurement provides the number of attempted RAB
establishments for each cell. Separate subcounters are defined for
the different RAB types.
(b) CC.
(c) Receipt of a RANAP-message RAB ASSIGNMENT REQUEST

sent by the CN to the UTRAN, with a “RAB to be set up.” For the
RAB to be established, the relevant counter is increased.
In case the RAB ASSIGNMENT REQUEST message is received
when an active link set already exists, the newest cell approach
shall apply (Refer to Active Link Set VS Most Recently Added
Cell).
(d) An integer value for each attempting RAB type rate.

• 0
FACH
• 1
CS AMR speech 12.2/12.2 Kbps
• 2
CS Conversational UDI 64/64 Kbps
• 3
• 4
CS Conversational UDI 28.8/28.8 Kbps
• 5
PS Conversational 8/8 Kbps
• 6
• 7
CS Streaming 57.6/57.6 Kbps
• 8
• 9
• 10
3-14
A50016-G5000-E202-3-7618
PS Streaming 16/64 Kbps

• 11
• 12
• 13
• 14
• 15
PS Interactive/Background 64/64 Kbps
• 16
• 17
• 18
• 19
• Other
Other
(e) rabEstabTypeAtt
(h) 5
(i) When RANAP RAB ASSIGNMENT REQUEST (SETUP) is

received
3.4.2 Number of successful RAB establishments per RAB type

(a) This measurement provides the number of successful RAB
the different RAB types.
(b) CC.
(c) Transmission of a RANAP-message RAB ASSIGNMENT

RESPONSE sent by the UTRAN to the CN, with a “RAB to be set
up.” For the successfully established RAB, the relevant counter is
3-15
A50016-G5000-E202-3-7618
increased.
In case the RAB ASSIGNMENT RESPONSE message is
transmitted when an active link set already exists, the newest cell
approach shall apply (Refer to Active Link Set VS Most Recently
Added Cell).
(d) An integer value for each RNC RAB type assigned.

• 0
FACH
• 1
CS AMR speech 12.2/12.2 Kbps
• 2
• 3
• 4
• 5
• 6
• 7
• 8
• 9
• 10
• 11
• 12
• 13
• 14
• 15
• 16
3-16
A50016-G5000-E202-3-7618

• 17
• 18
• 19
• Other
Other
(e) rabEstabTypeSucc
(h) 6
(i) When RANAP RAB ASSIGNMENT RESPONSE (SETUP) is

sent
3.4.3 Number of unsuccessful RAB establishments per failure

cause
(a) This measurement provides the number of unsuccessful RAB
the different failure causes and for separation of CS and PS.
(b) CC.
(c) Transmission of a RANAP-message RAB ASSIGNMENT

RESPONSE sent by the UTRAN to the CN, with “RAB failed to
set up.” For the RAB, which could not be established, the relevant
counter is increased according to the failure cause. Failure causes
are defined in 3GPP TS25.413.
In case the RAB ASSIGNMENT RESPONSE message is
transmitted when an active link set already exists, the newest cell
approach shall apply (Refer to Active Link Set VS Most Recently
Added Cell).
(d) An integer value for each combination out of failure cause and CS/
PS.
• 0-2,4,6
CS - Relocation triggered
• 0-2,4,8
3-17
A50016-G5000-E202-3-7618
CS - Unable to establish during relocation

• 0-2,4,12
CS - Requested ciphering and/or integrity protection
algorithms not supported
• 0-2,4,14
CS - Failure in the radio interface procedure
• 0-2,4,18
CS - Requested traffic class not available
• 0-2,4,19
CS - Invalid RAB parameters value
• 0-2,4,21
CS - Requested guaranteed bit rate not available
• 0-2,4,23
CS - Invalid RAB parameters combination
• 0-2,4,24
CS - Condition violation for SDU parameters
• 0-2,4,30
CS - Invalid RAB ID
• 0-2,4,32
CS - Interaction with other procedure
• 0-2,4,35
CS - Requested guaranteed bit rate for DL not supported
• 0-2,4,36
CS - Requested guaranteed bit rate for UL not supported
• 0-2,4,39
CS - Request superseded
• 0-2,4,45
CS - Directed retry
• 0-2,5,66
CS - Iu transport connection failed to establish
• 0-2,7,97
CS - Transfer syntax error
• 0-2,7,98
CS - Semantic error
• 0-2,7,99
CS - Message not compatible with receiver state
• 0-2,7,100
CS - Abstract syntax error (reject)
• 0-2,7,101
3-18
A50016-G5000-E202-3-7618
CS - Abstract syntax error (ignore and notify)

• 0-2,7,102
CS - Abstract syntax error (falsely constructed message)
• 0-2,8,114
CS - No resource available
• 0-2,8,115
CS - Unspecified failure
• 0-Other
CS - Other causes
• 1-2,4,6
PS - Relocation triggered
• 1-2,4,8
PS - Unable to establish during relocation
• 1-2,4,12
PS - Requested ciphering and/or integrity protection
algorithms not supported
• 1-2,4,14
PS - Failure in the radio interface procedure
• 1-2,4,18
PS - Requested traffic class not available
• 1-2,4,19
PS - Invalid RAB parameters value
• 1-2,4,21
PS - Requested guaranteed bit rate not available
• 1-2,4,23
PS - Invalid RAB parameters combination
• 1-2,4,24
PS - Condition violation for SDU parameters
• 1-2,4,30
PS - Invalid RAB ID
• 1-2,4,32
PS - Interaction with other procedure
• 1-2,4,35
PS - Requested guaranteed bit rate for DL not supported
• 1-2,4,36
PS - Requested guaranteed bit rate for UL not supported
• 1-2,4,39
PS - Request superseded
• 1-2,4,45
3-19
A50016-G5000-E202-3-7618
PS - Directed retry
• 1-2,5,66
PS - Iu transport connection failed to establish
• 1-2,7,97
PS - Transfer syntax error
• 1-2,7,98
PS - Semantic error
• 1-2,7,99
PS - Message not compatible with receiver state
• 1-2,7,100
PS - Abstract syntax error (reject)
• 1-2,7,101
PS - Abstract syntax error (ignore and notify)
• 1-2,7,102
PS - Abstract syntax error (falsely constructed message)
• 1-2,8,114
PS - No resource available
• 1-2,8,115
PS - Unspecified failure
• 1-Other
PS - Other causes
(e) rabEstabTypeFail
(h) 109
(i) When RANAP RAB ASSIGNMENT RESPONSE (SETUP

failure) is sent
Note: When an internal NG occurs, it is counted by iuRelReq. The
cause is Release due to UTRAN Generated Reason.
3.4.4 Number of RAB releases per release cause

(a) This measurement provides the number of RAB releases for each
cell. Separate subcounters are defined for the different release
causes and for separation of CS and PS.
(b) CC.
3-20
A50016-G5000-E202-3-7618
(c) Receipt of a RANAP-message RAB ASSIGNMENT REQUEST

or RAB RELEASE REQUEST sent by the UTRAN to the CN,
with “RABs to be released.” For each RAB to be released, the
relevant counter is increased according to the release cause.
Release causes are defined in 3GPP TS25.413.
The UTRAN sends RAB RELEASE REQUEST, to which the CN
may reply with either IU RELEASE COMMAND or RAB
ASSIGNMENT COMMAND or RAB ASSIGNMENT REQUEST
with “RABs to release.” In the specified way, the event of a RAB
release may be counted twice.
(d) An integer value for each combination out of failure cause and CS/
PS.
• 0-2,4,15
CS - Release due to UTRAN generated reason
• 0-2,4,16
CS - User inactivity
• 0-2,4,28
CS - Iu UP failure
• 0-2,4,37
CS - Repeated integrity checking failure
• 0-2,6,83
CS - Normal release
• 0-2,8,113
CS - O&M intervention
• 0-2,8,115
• 0-Other
CS - Other causes
• 1-2,4,15
PS - Release due to UTRAN generated reason
• 1-2,4,16
PS - User inactivity
• 1-2,4,28
PS - Iu UP failure
• 1-2,4,37
PS - Repeated integrity checking failure
• 1-2,6,83
PS - Normal release
• 1-2,8,113
PS - O&M intervention
3-21
A50016-G5000-E202-3-7618
• 1-2,8,115
• 1-Other
PS - Other causes
(e) rabRel
(h) 110

• When RANAP RAB ASSIGNMENT REQUEST (RELEASE)
is received
• When RANAP RAB RELEASE REQUEST is sent
3.4.5 Number of UTRAN initiated RAB releases per release cause

(a) This measurement provides the number of UTRAN initiated RAB
releases for each cell. Separate subcounters are defined for the
different release causes and for separation of CS and PS.
(b) CC.
(c) The measurement is based on two different events:

(1) Transmission of a RANAP message RAB RELEASE
REQUEST sent by the UTRAN to the CN, with “RABs to be
released”.
(2) Transmission of a RANAP message IU RELEASE
REQUEST sent by the UTRAN to the CN involving release of
RABs.
For each RAB to be released, the relevant counter is increased
according to the release cause. Release causes are defined in 3GPP
TS25.413.
When there is no applicable cell, then the RNC measurement
function will be applied.
(d) An integer value for each combination out of release cause and CS/
PS.
• 0-2,4,14
CS - Failure in the Radio Interface Procedure
• 0-2,4,15
3-22
A50016-G5000-E202-3-7618
• 0-2,4,16
• 0-2,4,28
CS - Iu UP failure
• 0-2,4,37
• 0-2,4,40
CS - Release due to UE generated signaling connection release
• 0-2,4,45
CS - Directed retry
• 0-2,4,46
CS - Radio Connection With UE Lost
• 0-2,6,83
CS - Normal release
• 0-2,8,113
• 0-2,8,115
• 0-Other
CS - Other causes
• 1-2,4,14
PS - Failure in the Radio Interface Procedure
• 1-2,4,15
• 1-2,4,16
• 1-2,4,28
PS - Iu UP failure
• 1-2,4,37
• 1-2,4,40
PS - Release due to UE generated signaling connection release
• 1-2,4,45
PS - Directed retry
• 1-2,4,46
PS - Radio Connection With UE Lost
• 1-2,6,83
PS - Normal release
• 1-2,8,113
3-23
A50016-G5000-E202-3-7618
• 1-2,8,115
• 1-Other
PS - Other causes
(e) rabRelUtranOrigin
(h) 114

• When a RANAP RAB RELEASE REQUEST is sent
• When a RANAP IU RELEASE REQUEST is sent
3.4.6 Number of CN initiated RAB releases per release cause

(a) This measurement provides the number of CN initiated RAB
releases for each cell. Separate subcounters are defined for the
different release causes and for separation of CS and PS.
(b) CC.
(c) The measurement is based on two different events:

(1) Receipt of a RANAP message RAB ASSIGNMENT
REQUEST sent by the CN to the UTRAN, with “RABs to
release”.
(2) Receipt of a RANAP message IU RELEASE COMMAND
sent by the CN to the UTRAN involving release of RABs.
TS25.413.
When there is no applicable cell, then the RNC measurement
function will be applied.
Note: The CN initiated RAB release counter will also be
incremented in case that UTRAN requested the RAB release
before.
PS.
• 0-2,4,14
3-24
A50016-G5000-E202-3-7618
• 0-2,4,15
• 0-2,4,16
• 0-2,4,28
CS - Iu UP failure
• 0-2,4,37
• 0-2,4,40
• 0-2,4,45
CS - Directed retry
• 0-2,4,46
• 0-2,6,83
CS - Normal release
• 0-2,8,113
• 0-2,8,115
• 0-Other
CS - Other causes
• 1-2,4,14
• 1-2,4,15
• 1-2,4,16
• 1-2,4,28
PS - Iu UP failure
• 1-2,4,37
• 1-2,4,40
• 1-2,4,45
PS - Directed retry
• 1-2,4,46
• 1-2,6,83
3-25
A50016-G5000-E202-3-7618
PS - Normal release
• 1-2,8,113
• 1-2,8,115
• 1-Other
PS - Other causes
(e) rabRelCnOrigin
(h) 115

• When RANAP RAB ASSIGNMENT REQUEST is received
• When RANAP IU RELEASE COMMAND is received
3.4.7 Number of UTRAN initiated RAB releases per release cause

RNC related
(a) This measurement provides the number of UTRAN initiated RAB
releases per RNC whenever the connected cell belongs to a foreign
RNC (DRNC). Separate subcounters are defined for the different
release causes and for separation of CS and PS.
(b) CC.
(c) The measurement is based on transmission of a RANAP message

IU RELEASE REQUEST sent by the UTRAN to the CN involving
release of RABs.
TS25.413.
Within this RNC related counter all events shall be recorded where
the cell belongs to a foreign RNC.
PS.
• 0-2,4,14
• 0-2,4,15
3-26
A50016-G5000-E202-3-7618
• 0-2,4,16
• 0-2,4,28
CS - Iu UP failure
• 0-2,4,37
• 0-2,4,40
• 0-2,4,45
CS - Directed retry
• 0-2,4,46
• 0-2,6,83
CS - Normal release
• 0-2,8,113
• 0-2,8,115
• 0-Other
CS - Other causes
• 1-2,4,14
• 1-2,4,15
• 1-2,4,16
• 1-2,4,28
PS - Iu UP failure
• 1-2,4,37
• 1-2,4,40
• 1-2,4,45
PS - Directed retry
• 1-2,4,46
• 1-2,6,83
PS - Normal release
• 1-2,8,113
3-27
A50016-G5000-E202-3-7618
• 1-2,8,115
• 1-Other
PS - Other causes
(e) rabRelUtranOriginRNC
(h) 116
(i) When a RANAP IU RELEASE REQUEST is sent
3.4.8 Number of CN initiated RAB releases per release cause RNC

related
(a) This measurement provides the number of CN initiated RAB
releases per RNC whenever the concerned cell belongs to a foreign
RNC (DRNC). Separate subcounters are defined for the different
release causes and for separation of CS and PS.
(b) CC.
(c) The measurement is based on transmission of a RANAP message

IU RELEASE COMMAND sent by the CN to the UTRAN
involving release of RABs.
TS25.413.
Note: The CN initiated RAB release counter will also be
incremented in case that UTRAN requested the RAB release
before.
PS.
• 0-2,4,14
• 0-2,4,15
• 0-2,4,16
3-28
A50016-G5000-E202-3-7618
• 0-2,4,28
CS - Iu UP failure
• 0-2,4,37
• 0-2,4,40
• 0-2,4,45
CS - Directed retry
• 0-2,4,46
• 0-2,6,83
CS - Normal release
• 0-2,8,113
• 0-2,8,115
• 0-Other
CS - Other causes
• 1-2,4,14
• 1-2,4,15
• 1-2,4,16
• 1-2,4,28
PS - Iu UP failure
• 1-2,4,37
• 1-2,4,40
• 1-2,4,45
PS - Directed retry
• 1-2,4,46
• 1-2,6,83
PS - Normal release
• 1-2,8,113
3-29
A50016-G5000-E202-3-7618
• 1-2,8,115
• 1-Other
PS - Other causes
(e) rabRelCnOriginRNC
(h) 117
(i) When RANAP IU RELEASE COMMAND is received
3.5 Transport Channel Reconfiguration
3.5.1 Number of attempted transport channel reconfigurations

(a) This measurement provides the number of attempted transport
channel reconfiguration procedures for each cell.
(b) CC.
(c) Transmission of a TRANSPORT CHANNEL

RECONFIGURATION message sent by the UTRAN to the UE.
(e) traChReconfAtt
(h) 218
(i) When RRC TRANSPORT CHANNEL RECONFIGURATION is

sent
3.5.2 Number of successful transport channel reconfigurations

(a) This measurement provides the number of successful transport
(b) CC.
(c) Receipt of a TRANSPORT CHANNEL RECONFIGURATION
3-30
A50016-G5000-E202-3-7618
COMPLETE message sent by the UE to the UTRAN.
(e) traChReconfSucc
(h) 219
(i) When RRC TRANSPORT CHANNEL RECONFIGURATION is

received
3.5.3 Number of failed transport channel reconfigurations per

failure cause
(a) This measurement provides the number of unsuccessful transport
channel reconfiguration procedures for each cell. For each failure
cause a separate subcounter is defined.
(b) CC.
(c) Receipt of a TRANSPORT CHANNEL RECONFIGURATION

FAILURE message sent by the UE to the UTRAN. Failure causes
This message can be received as a reply to cell update confirm as
well.

• 3,2,1
Configuration unsupported
• 3,2,2
Physical channel failure
• 3,2,3
Incompatible simultaneous reconfiguration
• 3,2,4
Compressed mode runtime error
• 3,2,5
Protocol error
• 3,2,6
Cell update occurred
• 3,2,7
Invalid configuration
3-31
A50016-G5000-E202-3-7618
• 3,2,8
Configuration incomplete
• 3,2,9
Unsupported measurement
• NoReply
No reply
• Other
Other causes
(e) traChReconfFail
(h) 220

• When RRC TRANSPORT CHANNEL
RECONFIGURATION FAILURE is received
• When RRC TRANSPORT CHANNEL
RECONFIGURATION COMPLETE wait timer expires
3-32
A50016-G5000-E202-3-7618
3.6 Physical Channel Reconfiguration
3.6.1 Number of attempted physical channel reconfigurations

(a) This measurement provides the number of attempted physical
(b) CC.
(c) Transmission of a PHYSICAL CHANNEL

RECONFIGURATION message sent by the UTRAN to the UE.
(e) phyChReconfAtt
(h) 164
(i) When RRC PHYSICAL CHANNEL RECONFIGURATION is

sent
3.6.2 Number of successful physical channel reconfigurations

(a) This measurement provides the number of successful physical
(b) CC.
(c) Receipt of a PHYSICAL CHANNEL RECONFIGURATION

COMPLETE message sent by the UE to the UTRAN.
(e) phyChReconfSucc
(h) 165
(i) When RRC PHYSICAL CHANNEL RECONFIGURATION

COMPLETE is received
3-33
A50016-G5000-E202-3-7618
3.6.3 Number of failed physical channel reconfigurations per failure

cause
(a) This measurement provides the number of unsuccessful physical
channel reconfiguration procedures for each cell. For each failure
(b) CC.
(c) Receipt of a PHYSICAL CHANNEL RECONFIGURATION

FAILURE message sent by the UE to the UTRAN. Failure causes
This message can be received as a reply to cell update confirm as
well.

• 3,2,1
• 3,2,2
• 3,2,3
• 3,2,4
• 3,2,5
Protocol error
• 3,2,6
• 3,2,7
• 3,2,8
• 3,2,9
• NoReply
No reply
• Other
Other causes
(e) phyChReconfFail
3-34
A50016-G5000-E202-3-7618
(h) 166

• When RRC PHYSICAL CHANNEL RECONFIGURATION
FAILURE is received
• When RRC PHYSICAL CHANNEL RECONFIGURATION
COMPLETE wait timer expires
3.7 Cell Updates
3.7.1 Number of cell updates per update cause

(a) This measurement provides the number of cell update procedures
for each cell. For each update cause a separate subcounter is
defined.
(b) CC.
(c) Receipt of a CELL UPDATE message sent by the UE to the

UTRAN. Update causes are defined within 3GPP TS25.331.
(d) An integer value for each update cause.

• 3,0,0
Cell re-selection
• 3,0,1
Periodical cell update
• 3,0,2
Uplink data transmission
• 3,0,3
Paging response
• 3,0,4
Re-entered service data
• 3,0,5
Radio link failure
• 3,0,6
RLC unrecoverable error
• Other
Other causes
(e) cellUpdate
3-35
A50016-G5000-E202-3-7618
(h) 167
(i) When RRC CELL UPDATE is received
3.7.2 Number of incoming cell updates per update cause per

adjacent cell pair
(a) This measurement provides the number of cell update procedures,
which are related to the incoming movement of a UE from an
adjacent cell. For each adjacent cell relationship, separate
subcounters are defined.
(b) CC.
(c) Receipt of a CELL UPDATE message sent by the UE to the

UTRAN, which is related to the incoming movement of a UE.
Only the update causes “cell reselection” and “re-entering service
area,” defined within 3GPP TS.25.331, are considered for this
movement-specific measurement.
If on the following situations, the event will be counted.
(1) Cell update cause: cell reselection or re-entered service area
(2) Newest cell of the active set is different from the cell reported
in the CELL UPDATE RRC message.
(3) The cell reported belongs to the RNC in which the scanner is
created.
The pair will be the “cell reported in the CELL UPDATE RRC
message” as center cell and the “newest cell of the active set” as
adjacent cell. If the “newest cell of the active set” could not be
determined as ADJACENT in some cases, they will be counted as
“other” cells.
The measurement will be done for “center cell - adjacent cell”.
However, the result will be indicated vice versa since this
measurement is to count the “incoming” cell updates.
(i.e. “other - cell=x”, “cell=y - cell=x”. The center cell is “cell=x”
and “cell=y” is adjacent to it.)
Note: The center cell is the cell in which the cell update has
occurred.
(d) An integer value for each combination out of originating cell and
movement-specific update cause. The number of originating cells
may vary dynamically, e.g., if a new neighbor cell is created.
• 3,0,0
3-36
A50016-G5000-E202-3-7618
Cell re-selection
• 3,0,4
Re-entered service data
(e) cellUpdateInc
(g) ADJACENT CELL RELATION measurement function.
(h) 168
(i) When RRC CELL UPDATE is received
3.8 URA Updates
3.8.1 Number of URA updates per update cause

(a) This measurement provides the number of URA updates for each
cell. For each update cause a separate subcounter is defined.
(b) CC.
(c) Receipt of a URA UPDATE message sent by the UE to the

UTRAN. Update causes are defined within 3GPP TS25.331.
(d) An integer value for each update cause.

• 3,0,0
Change of URA
• 3,0,1
Periodic URA update
• Other
Other causes
(e) uraUpdate
(h) 169
(i) When RRC URA UPDATE is received
3.9 Radio Link Updates
3-37
A50016-G5000-E202-3-7618
3.9.1 Number of radio link failures per failure cause

(a) This measurement provides the number of radio link failures. For
each failure cause a separate subcounter is defined.
(b) CC.
(c) Receipt of a RADIO LINK FAILURE message (NBAP or

RNSAP) sent by the Node B or the Drift RNC to the Serving RNC.
This measurement does not affect the Drift RNC.

• 4,4,10
Synchronization failure
• 4,4,17
Invalid CM settings
• 4,5,0
Transport resource unavailable
• 4,8,0
Control processing overload
• 4,8,1
HW failure
• 4,8,2
O&M intervention
• Other
Other causes
(e) radioLinkFail
(h) 105
(i) When RL FAILURE INDICATION is received
3.9.2 Number of attempted radio link establishments

(a) This measurement provides the number of attempted radio link
establishments for each cell.
(b) CC.
(c) This measurement is based on two different events:
3-38
A50016-G5000-E202-3-7618
(1) Transmission of a RADIO LINK SETUP REQUEST message

(NBAP) by the RNC to the Node B.
(2) Transmission of a RADIO LINK ADDITION REQUEST
message (NBAP) by the RNC to the Node B.
Only messages on the Iub interface shall be triggered initiated
from the CRNC.
When in case (1) or in case (2) more than one radio link shall be
established, each existing radio link information element shall be
considered separately. Refer to 3GPP TS25.433.
(e) rlEstabAtt
(h) 103

• When a RADIO LINK SETUP REQUEST is sent
• When a RADIO LINK ADDITION REQUEST is sent
3.9.3 Number of successful radio link establishments

(a) This measurement provides the number of successful radio link
establishments for each cell.
(b) CC.
(c) This measurement is based on two different events:

(1) Receipt of a RADIO LINK SETUP RESPONSE message
(NBAP) sent by the Node B to the RNC.
(2) Receipt of a RADIO LINK ADDITION RESPONSE message
(NBAP) sent by the Node B to the RNC.
Only messages on the Iub interface shall be triggered receipt by the
CRNC.
When in case (1) or in case (2) more than one radio link have been
established, each successful added radio link information element
shall be considered separately. Refer to 3GPP TS25.433.
(e) rlEstabSucc
3-39
A50016-G5000-E202-3-7618
(h) 104

• When a RADIO LINK SETUP RESPONSE is received
• When a RADIO LINK ADDITION RESPONSE is received
3.9.4 Number of unsuccessful radio link establishments per failure

cause
(a) This measurement provides the number of unsuccessful radio link
establishments for each cell. For each failure cause a separate
subcounter is defined.
(b) CC.
(c) This measurement is based on three different events:

(1) Receipt of a RADIO LINK SETUP FAILURE message
(NBAP) sent by the Node B to the RNC in response to a
RADIO LINK SETUP REQUEST message.
(2) Receipt of a RADIO LINK ADDITION FAILURE message
(NBAP) sent by the Node B to the RNC in response to a
RADIO LINK ADDITION REQUEST message.
(3) Non-receipt of the NBAP messages RADIO LINK SETUP
RESPONSE or RADIO LINK ADDITION RESPONSE
(expiration of the appropriate timer) in response to a RADIO
LINK SETUP REQUEST or RADIO LINK ADDITION
REQUEST sent from the RNC to the Node B, indicating the
attempt of a radio link setup or radio link addition.
Only trigger conditions related to the CRNC shall be considered.
When the failure is related to more than one radio link, each failed
attempt to establish a radio link shall be considered separately.
Failure causes are defined within 3GPP TS25.433.

• 4,4,0
Unknown C-ID
• 4,4,1
Cell not available
• 4,4,2
Power level not supported
• 4,4,3
DL radio resources not available
3-40
A50016-G5000-E202-3-7618
• 4,4,4
UL radio resources not available
• 4,4,5
RL already activated/allocated
• 4,4,6
Node B resources unavailable
• 4,4,9
Requested configuration not supported
• 4,4,14
Unspecified (Radio layer network cause)
• 4,4,17
Invalid CM settings
• 4,4,19
Number of DL codes not supported
• 4,4,22
UL SF not supported
• 4,4,23
DL SF not supported
• 4,4,25
Dedicated transport channel type not supported
• 4,4,28
CM not supported
• 4,4,31
Number of UL codes not supported
• 4,5,0
Transport resource unavailable
• 4,5,1
Unspecified (Transport layer network cause)
• 4,7,3
Protocol error
• 4,8,0
• 4,8,1
HW failure
• 4,8,2
O&M intervention
• 4,8,3
Not enough user plane processing resources
• 4,8,4
3-41
A50016-G5000-E202-3-7618
Unspecified (Miscellaneous cause)

• NoReply
No reply
• Other
Other causes
(e) rlEstabFail
(h) 106

• When a RADIO LINK SETUP FAILURE is received
• When a RADIO LINK ADDITION FAILURE is received
• When a RADIO LINK SETUP RESPONSE or a RADIO
LINK ADDITION RESPONSE is not received
3.10 Soft Handovers
3.10.1 Number of attempted intra Node B branch additions per

addition cause
(a) This measurement provides the number of attempted intra Node B
radio link additions for each cell. For each addition cause a
(b) CC.
(c) Decision in the RNC to add a new diversity branch (intra Node B)
for a UE for handover reasons. The appropriate counter is
increased for the cell, which shall be added to the active link set.
Addition causes separate different soft handover algorithms, which
are implemented (e.g. comparison or load control strategies).
From the data provided by Call Processing, the following
discriminations are done.
(1) Examination of the RNC ID of the cell, which is added to the
active set. (This cell will be described as “added cell”
hereafter.) If it does not indicate the ID of SRNC, the event
will not be counted in PM.
(2) Examination of the RNC ID and Node B IDs of the newest
cell of the active set and “added cell”.
If the RNC IDs of these cells differ, this branch addition
3-42
A50016-G5000-E202-3-7618
movement is determined as “inter RNC branch additions”

(mtype:58).
If the RNC IDs of these cells are the same but the Node B IDs
are different, it is determined as “intra RNC branch additions”
(mtype:46).
If both these IDs are the same, it is determined as “intra Node
B branch additions” (mtype: 34).
Note: The cell which will be counted are the “added cells”.
Also, they will be counted per cause.
(d) An integer value for each addition cause.

• 1,9,1
CPICH comparison (1A)
• 1,9,2
CPICH comparison (1A’)
• 1,9,4
CPICH comparison (1C)
• Other
Other causes
(e) shoAddIntraNodeBAtt
(h) 34
(i) When a branch is added (after RRC MEASUREMENT REPORT

is received and before NBAP RL SETUP/ADDITION REQUEST
is sent)
3.10.2 Number of successful intra Node B branch additions per

addition cause
(a) This measurement provides the number of successful intra Node B
(b) CC.
(c) Receipt of an RRC-message ACTIVE SET UPDATE COMPLETE

sent from the UE to the UTRAN, indicating the success of an intra
Node B branch addition procedure. The appropriate counter is
increased for the cell, which has been added to the active link set.
3-43
A50016-G5000-E202-3-7618

(mtype:59).
(mtype:48).

• 1,9,1
• 1,9,2
• 1,9,4
• Other
Other causes
(e) shoAddIntraNodeBSucc
(h) 36
(i) When RRC ACTIVE SET UPDATE COMPLETE is received in

case of Branch Addition at handover
3.10.3 Number of unsuccessful intra Node B branch additions per

failure cause
3-44
A50016-G5000-E202-3-7618
(a) This measurement provides the number of unsuccessful intra Node

B radio link additions for each cell. For each failure cause a
(b) CC.
(c) Failure during procedure to add a new diversity branch (intra Node
B) for a UE for handover reasons. The appropriate counter is
increased for the cell, which has been tried to be added to the
active link set. Failure causes shall strictly separate between
failures during Radio Link Setup procedure (UTRAN side) and
failures during Active Set Update procedure (UE side).
(mtype:60).
(mtype:47).

• 6,4,0
Unknown C-Id
• 6,4,1
Cell not available
• 6,4,2
• 6,4,3
• 6,4,4
• 6,4,5
3-45
A50016-G5000-E202-3-7618
• 6,4,6
• 6,4,7
Combining resources not available
• 6,4,8
• 6,4,9
Unspecified (radio network layer cause)
• 6,4,10
Measurement temporarily not available
• 6,4,11
Invalid CM settings
• 6,4,12
Reconfiguration CFN not elapsed
• 6,4,13
• 6,4,14
Combining not supported
• 6,4,15
UL SF not supported
• 6,4,16
DL SF not supported
• 6,4,17
• 6,4,18
CM not supported
• 6,4,19
UL scrambling code already in use
• 6,4,20
Transaction not supported by destination Node B
• 6,4,21
• 6,5,0
Transport resources unavailable
• 6,5,1
Unspecified (transport layer cause)
• 6,7,0
Transfer syntax error
• 6,7,1
3-46
A50016-G5000-E202-3-7618
Abstract syntax error (reject)

• 6,7,2
Abstract syntax error (ignore and notify)
• 6,7,3
• 6,7,4
Semantic error
• 6,7,5
Unspecified (protocol cause)
• 6,7,6
Abstract syntax error (falsely constructed message)
• 6,8,0
• 6,8,1
HW failure
• 6,8,2
O&M intervention
• 6,8,3
• 6,8,4
Unspecified (miscellaneous cause)
• 3,2,1
• 3,2,2
• 3,2,3
• 3,2,4
• 3,2,5
Protocol error
• 3,2,6
• 3,2,7
• 3,2,8
• 3,2,9
3-47
A50016-G5000-E202-3-7618
• NoReply
No reply
• Other
Other causes
(e) shoAddIntraNodeBFail
(h) 35

• When RRC ACTIVE SET UPDATE FAILURE is received in
• RL establishment NG on NBAP
Notes:
1 When DHT SyncNG occurs, it is counted by branchAddFail
(Cause is Other) or by iuRelReq (Cause is Release due to
UTRAN Generated Reason).
2 When ALCAP establishment NG occurs, it is counted by
iuRelReq. The Cause is Release due to UTRAN Generated
Reason.
3 When an internal NG occurs, it is counted by iuRelReq. The
Cause is Release due to UTRAN Generated Reason.
3.10.4 Number of attempted intra RNC branch additions per addition

cause
(a) This measurement provides the number of attempted intra RNC
(b) CC.
(c) Decision in the RNC to add a new diversity branch (intra RNC) for
a UE for handover reasons. The appropriate counter is increased
for the cell, which shall be added to the active link set. Addition
causes separate different soft handover algorithms, which are
implemented (e.g. comparison or load control strategies).
3-48
A50016-G5000-E202-3-7618

(mtype: 58).
(mtype: 46).

• 1,9,1
• 1,9,2
• 1,9,4
• Other
Other causes
(e) shoAddIntraRncAtt
(h) 46

is sent)
3-49
A50016-G5000-E202-3-7618
3.10.5 Number of successful intra RNC branch additions per addition

cause
(a) This measurement provides the number of successful intra RNC
(b) CC.

sent from the UE to the UTRAN, indicating the success of an intra
RNC branch addition procedure. The appropriate counter is
(mtype:59).
(mtype:48).

• 1,9,1
• 1,9,2
• 1,9,4
• Other
Other causes
3-50
A50016-G5000-E202-3-7618
(e) shoAddIntraRncSucc
(h) 48

3.10.6 Number of unsuccessful intra RNC branch additions per

failure cause
(a) This measurement provides the number of unsuccessful intra RNC
radio link additions for each cell. For each failure cause a separate
(b) CC.
(c) Failure during procedure to add a new diversity branch (intra

RNC) for a UE for handover reasons. The appropriate counter is
(mtype:60).
(mtype:47).
3-51
A50016-G5000-E202-3-7618
• 6,4,0
Unknown C-Id
• 6,4,1
Cell not available
• 6,4,2
• 6,4,3
• 6,4,4
• 6,4,5
• 6,4,6
• 6,4,7
• 6,4,8
• 6,4,9
• 6,4,10
• 6,4,11
Invalid CM settings
• 6,4,12
• 6,4,13
• 6,4,14
• 6,4,15
UL SF not supported
• 6,4,16
DL SF not supported
• 6,4,17
• 6,4,18
CM not supported
• 6,4,19
3-52
A50016-G5000-E202-3-7618

• 6,4,20
• 6,4,21
• 6,5,0
• 6,5,1
• 6,7,0
• 6,7,1
• 6,7,2
• 6,7,3
• 6,7,4
Semantic error
• 6,7,5
• 6,7,6
• 6,8,0
• 6,8,1
HW failure
• 6,8,2
O&M intervention
• 6,8,3
• 6,8,4
• 3,2,1
• 3,2,2
• 3,2,3
3-53
A50016-G5000-E202-3-7618
• 3,2,4
• 3,2,5
Protocol error
• 3,2,6
• 3,2,7
• 3,2,8
• 3,2,9
• NoReply
No reply
• Other
Other causes
(e) shoAddIntraRncFail
(h) 47
(i) When RRC ACTIVE SET UPDATE FAILURE is received in case

of Branch Addition at handover
3.10.7 Number of attempted inter RNC branch additions per addition

cause
(a) This measurement provides the number of attempted inter RNC
(b) CC.
(c) Decision in the RNC to add a new diversity branch (inter RNC) for
a UE for handover reasons. The appropriate counter is increased
for the cell, which shall be added to the active link set. Addition
causes separate different soft handover algorithms, which are
implemented (e.g. comparison or load control strategies).
3-54
A50016-G5000-E202-3-7618

(mtype: 58).
(mtype: 46).

• 1,9,1
• 1,9,2
• 1,9,4
• Other
Other causes
(e) shoAddInterRncAtt
(h) 58

is sent)
3.10.8 Number of successful inter RNC branch additions per addition

cause
(a) This measurement provides the number of successful inter RNC
3-55
A50016-G5000-E202-3-7618
(b) CC.

sent from the UE to the UTRAN, indicating the success of an inter
RNC branch addition procedure. The appropriate counter is
(mtype:59).
(mtype:48).

• 1,9,1
• 1,9,2
• 1,9,4
• Other
Other causes
(e) shoAddInterRncSucc
(h) 59
3-56
A50016-G5000-E202-3-7618

3.10.9 Number of unsuccessful inter RNC branch additions per

failure cause
(a) This measurement provides the number of unsuccessful inter RNC
radio link additions for each cell. For each failure cause a separate
(b) CC.
(c) Failure during procedure to add a new diversity branch (inter

RNC) for a UE for handover reasons. The appropriate counter is
(mtype:60).
(mtype:47).

• 6,4,0
Unknown C-Id
• 6,4,1
Cell not available
• 6,4,2
3-57
A50016-G5000-E202-3-7618
• 6,4,3
• 6,4,4
• 6,4,5
• 6,4,6
• 6,4,7
• 6,4,8
• 6,4,9
• 6,4,10
• 6,4,11
Invalid CM settings
• 6,4,12
• 6,4,13
• 6,4,14
• 6,4,15
UL SF not supported
• 6,4,16
DL SF not supported
• 6,4,17
• 6,4,18
CM not supported
• 6,4,19
• 6,4,20
• 6,4,21
• 6,5,0
3-58
A50016-G5000-E202-3-7618

• 6,5,1
• 6,7,0
• 6,7,1
• 6,7,2
• 6,7,3
• 6,7,4
Semantic error
• 6,7,5
• 6,7,6
• 6,8,0
• 6,8,1
HW failure
• 6,8,2
O&M intervention
• 6,8,3
• 6,8,4
• 3,2,1
• 3,2,2
• 3,2,3
• 3,2,4
• 3,2,5
Protocol error
• 3,2,6
3-59
A50016-G5000-E202-3-7618
• 3,2,7
• 3,2,8
• 3,2,9
• NoReply
No reply
• Other
Other causes
(e) shoAddInterRncFail
(h) 60

3.10.10Number of attempted branch deletions per deletion cause

deletions for each cell. For each deletion cause a separate
(b) CC.
(c) Decision in the RNC to delete a diversity branch for a UE for

handover reasons. The appropriate counter is increased for the cell,
which shall be removed from the active link set.
(d) An integer value for each deletion cause.

The value counted only if the cell to be deleted from the active set
belongs to SRNC.
• 1,9,3
CPICH comparison (1B)
• 1,9,4
• Other
Other causes
(e) shoDelAtt
3-60
A50016-G5000-E202-3-7618
(h) 38
(i) When a branch is deleted (after RRC MEASUREMENT REPORT

is received and before NBAP RL SET UPDATE is sent)
3.10.11Number of successful branch deletions per deletion cause

deletions for each cell. For each deletion cause a separate
(b) CC.

sent from the UE to the UTRAN, indicating the success of a
branch deletion procedure for handover reasons. The appropriate
counter is increased for the cell, which has been removed from the
active link set.
Decision in the RNC to delete a diversity branch for a UE for
handover reasons. The appropriate counter is increased for the cell,
which shall be removed from the active link set.
(d) An integer value for each deletion cause.

The value counted only if the cell to be deleted from the active set
belongs to SRNC.
• 1,9,3
CPICH comparison (1B)
• 1,9,4
• Other
Other causes
(e) shoDelSucc
(h) 50
(i) After RRC ACTIVE SET UPDATE COMPLETE is received in

case of Branch Deletion at handover
3-61
A50016-G5000-E202-3-7618
3.10.12Number of attempted outgoing radio link addition movements

per adjacent cell
additions for each adjacent cell relation.
(b) CC.
(c) Decision in the RNC to add a new diversity branch for a UE for
handover reasons. If more than one link is attempted to be added to
the active link set simultaneously, every attempted link addition is
counted separately.
This measurement is counted for each cell pair.
The cell pair for this measurement is the newest cell of the active
set as “center cell” and the “added cell” as “adjacent cell”. Only
the events in which the “center cell” belongs to SRNC can be
counted.
Note: If the “added cell” cannot be distinguished as ADJACENT
to “center cell”, it will be counted as “other” cell.
(i.e. “cell=a - cell=b”, “cell=a - rnc=c, cell=d”, “cell=a -
other”. The center cell is “cell=a” and if “cell=b” and
“rnc=c, cell=d” are adjacent to it.)
They are not counted per cause.
(d) An integer value for each target cell. The number of target cells
(e) shoMoveOutAtt
(h) 170

is sent)
3.10.13Number of successful outgoing radio link addition

movements per adjacent cell
additions for each adjacent cell relation.
(b) CC.
3-62
A50016-G5000-E202-3-7618
sent from the UE to the UTRAN, indicating the success of a

branch addition procedure. If more than one link has been added to
the active link set simultaneously, every radio link addition is
counted separately.
counted.
They are not counted per cause.
(d) An integer value for each target cell. The number of target cells
(e) shoMoveOutSucc
(h) 171

3.10.14Number of failed outgoing radio link addition movements per

failure cause per adjacent cell
(a) This measurement provides the number of unsuccessful
consecutive radio link additions for each adjacent cell relation. For
each failure cause a separate subcounter is defined.
(b) CC.
(c) Failure during procedure to add a new diversity branch (intra Node
B or inter Node B) for a UE for handover reasons. If more than one
link has been tried to be added to the active link set simultaneously,
every radio link addition is counted separately.
counted.
3-63
A50016-G5000-E202-3-7618

They are counted per cause.
(d) An integer value for each combination out of failure cause and
target cell. The number of target cells may vary dynamically, e.g.,
if a new neighbor cell is created.
• 6,4,0
Unknown C-Id
• 6,4,1
Cell not available
• 6,4,2
• 6,4,3
• 6,4,4
• 6,4,5
• 6,4,6
• 6,4,7
• 6,4,8
• 6,4,9
• 6,4,10
• 6,4,11
Invalid CM settings
• 6,4,12
• 6,4,13
• 6,4,14
3-64
A50016-G5000-E202-3-7618
• 6,4,15
UL SF not supported
• 6,4,16
DL SF not supported
• 6,4,17
• 6,4,18
CM not supported
• 6,4,19
• 6,4,20
• 6,4,21
• 6,5,0
• 6,5,1
• 6,7,0
• 6,7,1
• 6,7,2
• 6,7,3
• 6,7,4
Semantic error
• 6,7,5
• 6,7,6
• 6,8,0
• 6,8,1
HW failure
• 6,8,2
O&M intervention
• 6,8,3
3-65
A50016-G5000-E202-3-7618

• 6,8,4
• 3,2,1
• 3,2,2
• 3,2,3
• 3,2,4
• 3,2,5
Protocol error
• 3,2,6
• 3,2,7
• 3,2,8
• 3,2,9
• NoReply
No reply
• Other
Other causes
(e) shoMoveOutFail
(h) 172

3-66
A50016-G5000-E202-3-7618
3.11 UTRAN Hard Handovers
3.11.1 Outgoing intra Node B hard handover
3.11.1.1 Number of all attempted outgoing hard handovers per

handover type
(a) This measurement provides the number of attempted outgoing
hard handovers for each cell. For each type of hard handover a
(b) CC.
(c) Transmission of an RRC message PHYSICAL CHANNEL

RECONFIGURATION sent from the UTRAN to the UE,
indicating the attempt of inter-frequency handover.
(d) An integer value for each hard handover type.
(e) hhoAllOutAtt1
(h) 30
(i) When a PHYSICAL CHANNEL RECONFIGURATION is sent
3.11.1.2 Number of all successful outgoing hard handovers per

handover type
(a) This measurement provides the number of successful outgoing
(b) CC.
(c) Receipt of an RRC message PHYSICAL CHANNEL

RECONFIGURATION COMPLETE sent from the UE to the
UTRAN, indicating the successful inter-frequency handover.
(e) hhoAllOutSucc1
3-67
A50016-G5000-E202-3-7618
(h) 31
(i) When a PHYSICAL CHANNEL RECONFIGURATION

3.11.1.3 Number of all unsuccessful outgoing hard handovers per

handover type per failure cause
(a) This measurement provides the number of unsuccessful outgoing
hard handovers for each cell. For each handover type and each
failure cause, a separate subcounter is defined.
(b) CC.
(c) Either of the following events occurs:

(1) Receipt of an RRC message PHYSICAL CHANNEL
RECONFIGURATION FAILURE sent from the UE to the
UTRAN, indicating a failed inter-frequency handover.
(2) Non-receipt of the RRC message PHYSICAL CHANNEL
RECONFIGURATION COMPLETE (expiration of the
appropriate timer) in response to a PHYSICAL CHANNEL
indicating the attempt of an inter-frequency handover.
handover type.
The hard handover failure causes are as follows:
• 3,2,1
• 3,2,2
• 3,2,3
• 3,2,4
• 3,2,5
Protocol error
• 3,2,6
• 3,2,7
3-68
A50016-G5000-E202-3-7618
• 3,2,8
• NoReply
No reply
• Other
Other causes
(e) hhoAllOutFail1
(h) 32

• When an RRC PHYSICAL CHANNEL
RECONFIGURATION FAILURE is received at hard handover
Note: When RL establishment NG occurs, it is counted by
branchAddFail. The Cause is a content on NBAP:
RLAddFail.
3.11.2 Outgoing inter Node B/intra RNC hard handover

handover type
(b) CC.

(e) hhoAllOutAtt2
3-69
A50016-G5000-E202-3-7618
(h) 30

handover type
(b) CC.

(e) hhoAllOutSucc2
(h) 31


(b) CC.

3-70
A50016-G5000-E202-3-7618
handover type.
• 3,2,1
• 3,2,2
• 3,2,3
• 3,2,4
• 3,2,5
Protocol error
• 3,2,6
• 3,2,7
• 3,2,8
• NoReply
No reply
• Other
Other causes
(e) hhoAllOutFail2
(h) 32

RLAddFail.
3-71
A50016-G5000-E202-3-7618
3.11.3 Outgoing inter RNC hard handover via Iur

handover type
(b) CC.

(e) hhoAllOutAtt3
(h) 30

handover type
(b) CC.

(e) hhoAllOutSucc3
3-72
A50016-G5000-E202-3-7618
(h) 31


(b) CC.

handover type.
• 3,2,1
• 3,2,2
• 3,2,3
• 3,2,4
• 3,2,5
Protocol error
• 3,2,6
• 3,2,7
• 3,2,8
3-73
A50016-G5000-E202-3-7618
• NoReply
No reply
• Other
Other causes
(e) hhoAllOutFail3
(h) 32

RLAddFail.
3.11.4 Incoming intra RNC hard handover
3.11.4.1 Number of attempted intra RNC incoming hard handovers

(a) This measurement provides the number of attempted incoming
intra RNC hard handovers for each cell.
(b) CC.
(c) There is no separate trigger condition for attempted incoming hard

handovers. Incoming hard handover attempts shall be derived in
O&M BE from the outgoing hard handover attempts where the
information of the target cell is provided.
(d) A single integer value.
(e) IntraRNCHhoAttInc
(h) 65
(i) None.
3-74
A50016-G5000-E202-3-7618
3.11.4.2 Number of successful intra RNC incoming hard handovers

(a) This measurement provides the number of successful incoming
(b) CC.
(c) There is no separate trigger condition for successful incoming hard

handovers. Successful hard handover shall be derived in O&M BE
from the successful outgoing hard handover where the information
of the target cell is provided.
(e) IntraRNCHhoSuccInc
(h) 66
(i) None.
3.11.4.3 Number of unsuccessful intra RNC incoming hard

handovers
(a) This measurement provides the number of unsuccessful incoming
(b) CC.
(c) There is no separate trigger condition for unsuccessful incoming

hard handovers since it may be not possible to measure it from the
perspective of the target cell. Incoming unsuccessful hard
handover shall be derived in O&M BE from the unsuccessful
outgoing hard handover where the information of the target cell is
provided.
(d) An integer value for each hard handover failure cause.

• 3,2,1
• 3,2,2
• 3,2,3
3-75
A50016-G5000-E202-3-7618
• 3,2,4
• 3,2,5
Protocol error
• 3,2,6
• 3,2,7
• 3,2,8
• NoReply
No reply
• Other
Other causes
(e) IntraRNCHhoFailInc
(h) 67
(i) None.
3.11.5 Outgoing UTRAN hard handover per adjacent cell pair
3.11.5.1 Number of attempted outgoing hard handovers per adjacent

cell pair
hard handovers for each cell relationship.
(b) CC.
(c) Transmission of an RRC message PHYSICAL CHANNEL

indicating the attempt of an outgoing hard handover.
(d) An integer value for each target cell relation. The number of target
cells may vary dynamically, e.g., if a new neighbor cell is created.
(e) HhoOutAttACM
3-76
A50016-G5000-E202-3-7618
(h) 27
(i) When a PHYSICAL CHANNEL RECONFIGURATION is sent.
3.11.5.2 Number of successful outgoing hard handovers per adjacent

cell pair
hard handovers for each cell relationship.
(b) CC.

UTRAN, indicating a successful outgoing hard handover.
(d) An integer value for each target cell relation. The number of target
cells may vary dynamically, e.g., if a new neighbor cell is created.
(e) HhoOutSuccACM
(h) 28

COMPLETE is received.
3.11.5.3 Number of unsuccessful outgoing hard handovers per

adjacent cell per failure cause
hard handovers with reconnection to the originating cell for each
cell relationship. For each failure cause a separate subcounter is
defined.
(b) CC.

UTRAN, indicating a failed outgoing hard handover.
3-77
A50016-G5000-E202-3-7618
appropriate timer) in response to the corresponding RRC

Reconfiguration-, Setup- or Release procedure sent from the
UTRAN to the UE, indicating the attempt of an outgoing hard
handover.
target cell. The number of target cells may vary dynamically, e.g.,
if a new neighbor cell is created.
• 3,2,1
• 3,2,2
• 3,2,3
• 3,2,4
• 3,2,5
Protocol error
• 3,2,6
• 3,2,7
• 3,2,8
• NoReply
No reply
• Other
Other causes
(e) HhoOutFailACM
(h) 29

3-78
A50016-G5000-E202-3-7618
3.12 Inter-System Hard Handovers
3.12.1 Relocation preparations for inter-system handovers
3.12.1.1 Number of attempted relocation preparations for outgoing

inter-system handovers per adjacent cell pair per handover
cause
(a) This measurement provides the number of attempted relocation
preparations for outgoing inter-system handover procedures for
each adjacent GSM cell relation.
(b) CC.
(c) Transmission of a RANAP-message RELOCATION REQUIRED

sent by the UTRAN to the CN, indicating the attempt of inter-
system handover.
Causes are defined within 3GPP TS25.413.
(d) An integer value for each target GSM cell. The number of target
GSM cells may vary dynamically, e.g., if a new neighbor cell is
created.
(e) interRatHoOutRelocAtt
(g) ADJACENT GSM CELL RELATION measurement function.
(h) 173
(i) When RANAP RELOCATION REQUIRED is sent at inter-system

handover only
3.12.1.2 Number of unsuccessful relocation preparations for

outgoing inter-system handovers per adjacent cell pair per
failure cause
(a) This measurement provides the number of unsuccessful relocation
preparations for outgoing inter-system handovers for each adjacent
GSM cell relation. For each failure cause a separate subcounter is
defined.
(b) CC.
(c) One of the following events occurs:
3-79
A50016-G5000-E202-3-7618
(1) Receipt of a RANAP-message RELOCATION

PREPARATION FAILURE sent from the CN to the UTRAN
in response to a RANAP-message RELOCATION
REQUIRED sent by the UTRAN to the CN, indicating the
attempt of an inter-system handover. Failure causes are
defined within 3GPP TS25.413.
(2) Timeout after a RANAP-message RELOCATION
REQUIRED has been sent by the UTRAN to the CN,
indicating the attempt of an inter-system handover.
target GSM cell. The number of target GSM cells may vary
dynamically, e.g., if a new neighbor cell is created.
• 2,4,7
TRELOCalloc expiry
• 2,4,9
Unknown target RNC
• 2,4,10
Relocation cancelled
• 2,4,29
Relocation failure in target CN/RNC or target system
• 2,4,44
Relocation not supported in target RNC or target system
• Other
Other causes
(e) interRatHoOutRelocFail
(h) 174
(i) When RANAP RELOCATION PREPARATION FAILURE is

received
3.12.2 Outgoing inter RAT hard handover

handover type
3-80
A50016-G5000-E202-3-7618
(b) CC.
(c) This measurement is based on the following different types:

(1) Transmission of an RRC message HANDOVER FROM
UTRAN COMMAND sent from the UTRAN to the UE,
indicating the attempt of inter-system handover.
(2) Transmission of an RRC message CELL CHANGE ORDER
FROM UTRAN sent from the serving RNC to the UE,
indicating an attempted outgoing PS inter RAT handover.
(e) hhoAllOutAtt4
(h) 30

• When an RRC HANDOVER FROM UTRAN COMMAND is
sent.
• When an RRC CELL CHANGE ORDER FROM UTRAN is
sent.

handover type
hard handovers for each cell. For each type of hard handover and
each cause of initiating the handover, a separate subcounter is
defined.
(b) CC.
(c) This measurement is based on the following different events:

(1) Receipt of a RANAP message IU RELEASE COMMAND,
sent by the CN to the serving RNC, indicating a successful
inter RAT handover.
(2) Receipt of a RANAP message SRNS CONTEXT REQUEST
sent from the PS CN to the serving RNC, indicating a
successful outgoing UE controlled PS inter RAT handover.
Note: From signaling flow and from RANAP message type used
3-81
A50016-G5000-E202-3-7618
for trigger condition the target system cannot be

distinguished. Thus, the outgoing PS handover may be an
inter UTRAN handover or an inter RAT handover.
(e) hhoAllOutSucc4
(h) 31

• When a RANAP IU RELEASE COMMAND is received.
• When a RANAP SRNS CONTEXT REQUEST is received.

(b) CC.

(1) Receipt of an RRC message HANDOVER FROM UTRAN
FAILURE sent from the UE to the UTRAN, indicating a
failed inter-frequency handover.
(2) Receipt of the RRC message CELL CHANGE ORDER
FROM UTRAN FAILURE sent from the UE to the serving
RNC, indicating an unsuccessful PS inter RAT handover.
Failure causes are defined within 3GPP TS25.331.
handover type.
• 3,1,1
Configuration unacceptable
• 3,1,2
• 3,1,3
Protocol error
3-82
A50016-G5000-E202-3-7618
• 3,1,4
Inter-RAT protocol error
• 3,2,1
• 3,2,2
• 3,2,5
Protocol error
• Other
Other causes
(e) hhoAllOutFail4
(h) 32

• When an RRC HANDOVER FROM UTRAN FAILURE is
received.
• When an RRC CELL CHANGE ORDER FROM UTRAN
FAILURE is received.
3.12.3 Incoming circuit switched inter RAT handover
3.12.3.1 Number of successful incoming CS inter RAT handovers

(a) This measurement provides the number of successful incoming CS
inter RAT handovers.
(b) CC.
(c) Receipt of an RRC message HANDOVER TO UTRAN

COMPLETE sent from the UE to the target RNC, indicating a
successful inter RAT handover. Refer to 3GGP TS25.331.
(e) interRatHoSuccInc
3-83
A50016-G5000-E202-3-7618
(h) 179
(i) When an RRC HANDOVER TO UTRAN COMPLETE is

received.
3.12.4 Outgoing inter RAT handovers adjacent cell related
3.12.4.1 Number of attempted outgoing inter-RAT handovers per

adjacent cell pair
inter-RAT handovers commands for each adjacent GSM cell
relation. The relocation preparation for allocation of resources in
GSM has successfully been executed before.
(b) CC.

(1) Transmission of an RRC message HANDOVER FROM
UTRAN COMMAND sent from the UTRAN to the UE.
(2) Transmission of an RRC message CELL CHANGE ORDER
FROM UTRAN sent from the serving RNC to the UE,
indicating an attempted outgoing PS inter RAT handover.
created.
(e) interRatHoOutAtt
(h) 175

• When an RRC HANDOVER FROM UTRAN COMMAND is
sent.
• When an RRC CELL CHANGE ORDER FROM UTRAN is
sent.
3.12.4.2 Number of successful outgoing inter-RAT handovers per

adjacent cell pair
3-84
A50016-G5000-E202-3-7618
inter-RAT handovers for each adjacent GSM cell relation.
(b) CC.

(1) Receipt of a RANAP message IU RELEASE COMMAND,
sent by the CN to the UTRAN indicating a successful inter-
system handover.
(2) Receipt of a RANAP message SRNS CONTEXT REQUEST
sent from the PS CN to the serving RNC, indicating a
successful outgoing UE controlled PS inter RAT handover.
Note: From signaling flow and from RANAP message type used
for trigger condition the target system cannot be
distinguished. Thus, the outgoing PS handover may be an
inter UTRAN handover or an inter RAT handover.
created.
(e) interRatHoOutSucc
(h) 177

• When a RANAP IU RELEASE COMMAND is received.
• When a RANAP SRNS CONTEXT REQUEST is received.
3.12.4.3 Number of unsuccessful outgoing inter-RAT handovers per

adjacent cell pair
inter-RAT handovers with failure during the radio link handover
for each adjacent GSM cell relation. For each failure cause a
(b) CC.

(1) Receipt of an RRC message HANDOVER FROM UTRAN
FAILURE sent from the UE to the UTRAN in response to an
RRC message HANDOVER FROM UTRAN COMMAND.
3-85
A50016-G5000-E202-3-7618
(2) Receipt of an RRC message CELL CHANGE ORDER FROM

UTRAN FAILURE sent from the UE to the serving RNC,
indicating an unsuccessful PS inter RAT handover. Failure
causes are defined within 3GPP TS25.331.
target GSM cell. The number of target GSM cells may vary
dynamically, e.g., if a new neighbor cell is created.
• 3,1,1
• 3,1,2
• 3,1,3
Protocol error
• 3,1,4
Inter-RAT protocol error
• 3,2,1
• 3,2,2
• 3,2,5
Protocol error
• Other
Other causes
(e) interRatHoOutFail
(h) 176

• When an RRC HANDOVER FROM UTRAN FAILURE is
received.
• When an RRC CELL CHANGE ORDER FROM UTRAN
FAILURE is received.
3-86
A50016-G5000-E202-3-7618
3.13 Relocation
3.13.1 Number of attempted outgoing relocation preparations per

relocation cause per relocation type
(a) This measurement provides the number of attempted SRNS
relocation preparations on the Source RNC side. For each
relocation cause and both relocation types, a separate subcounter is
defined.
(b) CC.
(c) Transmission of a RANAP-message RELOCATION REQUIRED

sent by the Source RNC to the CN.
Relocation causes (e.g. “Time critical relocation,” “Resource
optimization relocation,” “Relocation desirable for radio reasons,”
“Directed retry”) are described in the IE “Cause” of the RANAP-
message RELOCATION REQUIRED; see 3GPP TS25.413.
Relocation Types (“UE involved” and “UE not involved”) are
described in the IE “Relocation Type” of the RANAP-message
RELOCATION; see 3GPP TS25.413.
If the Source RNC is connected to both MSC and SGSN, either of
RELOCATION REQUIRED messages may be considered.
(d) An integer value for each supported combination out of relocation

cause and relocation type.
• 0-2,4,41
UE not involved - Resource optimization relocation
• 0-2,4,43
UE not involved - Relocation desirable for radio reasons
• 0-2,4,45
UE not involved - Directed retry
• 0-Other
UE not involved - Other causes
(e) relocOutAtt
(h) 180
(i) When RANAP RELOCATION REQUIRED is sent
3-87
A50016-G5000-E202-3-7618
3.13.2 Number of unsuccessful outgoing relocation preparations per

failure cause
(a) This measurement provides the number of unsuccessful SRNS
relocation preparations on the Source RNC side. For each failure
(b) CC.
(c) Receipt of a RANAP-message RELOCATION PREPARATION

FAILURE sent by the CN to the Source RNC.
Failure causes (e.g. “TRELOCalloc expiry,” “Resource failure in
target CN/RNC or target system,” “Relocation not supported in
target RNC or target system”) are described in the IE “Cause” of
the RANAP-message RELOCATION FAILURE; see 3GPP
TS25.413.
PREPARATION FAILURE messages may be considered.

• 2,4,7
TRELOCalloc expiry
• 2,4,9
Unknown target RNC
• 2,4,10
Relocation cancelled
• 2,4,29
Relocation failure in target CN/RNC or target system
• 2,4,44
Relocation not supported in target RNC or target system
• Other
Other causes
(e) relocOutFail
(h) 181
(i) When RANAP RELOCATION PREPARATION FAILURE is

received
Note: When T_RelocPrep timer expires, it is counted by iuRelReq.
The Cause is T_RelocPrep_expiry.
3-88
A50016-G5000-E202-3-7618
3.13.3 Number of successful outgoing relocation preparations per

relocation cause per relocation type
(a) This measurement provides the number of successful SRNS
relocation preparations on the Source RNC side. For each
relocation cause and both relocation types “UE involved” and “UE
not involved,” a separate subcounter is defined.
(b) CC.
(c) Receipt of a RANAP-message RELOCATION COMMAND sent

by the CN to the Source RNC.
Relocation causes and relocation types are defined within 3GPP
TS25.413.
RELOCATION COMMAND messages may be considered.
(d) An integer value for each supported combination of relocation

cause and relocation type.
• 0-2,4,41
UE not involved - Resource optimization relocation
• 0-2,4,43
UE not involved - Relocation desirable for radio reasons
• 0-2,4,45
UE not involved - Directed retry
• 0-Other
UE not involved - Other causes
(e) relocOutSucc
(h) 182
(i) When RANAP RELOCATION COMMAND is received
3.13.4 Number of attempted incoming relocations per relocation

cause
(a) This measurement provides the number of attempted SRNS
relocation procedures on the Target RNC side. For each relocation
(b) CC.
3-89
A50016-G5000-E202-3-7618
(c) Receipt of a RANAP-message RELOCATION REQUEST sent by

the CN to the Target RNC.
Relocation causes (e.g. “Time critical relocation,” “Resource
optimization relocation,” “Relocation desirable for radio reasons,”
“Directed retry”) are described in the IE “Cause” of the RANAP-
message RELOCATION REQUEST; see 3GPP TS25.413.
If the Target RNC is connected to both MSC and SGSN, either of
RELOCATION REQUEST messages may be considered.
(d) An integer value for each relocation cause.

• 2,4,41
Resource optimization relocation
• 2,4,43
Relocation desirable for radio reasons
• 2,4,45
Directed retry
• Other
Other causes
(e) relocIncAtt
(h) 183
(i) When RANAP RELOCATION REQUEST is received
3.13.5 Number of successful incoming relocations per relocation

cause
(a) This measurement provides the number of successful SRNS
relocation procedures on the Target RNC side. For each relocation
(b) CC.
(c) Transmission of a RANAP-message RELOCATION REQUEST

ACKNOWLEDGE sent by the Target RNC to the CN.
Relocation causes are defined within 3GPP TS25.413.
If the Target RNC is connected to both MSC and SGSN, either of
RELOCATION REQUEST ACKNOWLEDGE messages may be
considered.
(d) An integer value for each relocation cause.
3-90
A50016-G5000-E202-3-7618
• 2,4,41
Resource optimization relocation
• 2,4,43
Relocation desirable for radio reasons
• 2,4,45
Directed retry
• Other
Other causes
(e) relocIncSucc
(h) 184
(i) When RANAP RELOCATION REQUEST ACKNOWLEDGE is

sent
3.14 Iu Release
3.14.1 Number of Iu release requests per release cause

(a) This measurement provides the number of UTRAN-initiated Iu
connection releases for each cell. Separate subcounters are defined
for different release causes and for separation of CS and PS.
(b) CC.
(c) Transmission of a RANAP-message IU RELEASE REQUEST

sent by the UTRAN to the CN. Causes are defined within 3GPP
TS25.413 and shall be separated for CS and PS. If the RNC is
connected to both MSC and SGSN, both IU RELEASE
REQUEST messages may be considered. If the affected UE is in
soft handover, only the appropriate counter of the most recently
added cell of the active set shall be increased.
Prerequisite for the cell measurement function is that the cell
context is retained from the MRC until the IU RELEASE
COMMAND message is received. Namely, whenever the RNC
receives the RADIO LINK FAILURE INDICATION message and
the failing RL is the last RL of the RLS, the cell ID shall be
retained for PM counter purpose until the IU RELEASE
COMMAND is received from the CN.
PS.
3-91
A50016-G5000-E202-3-7618
• 0-2,4,14
• 0-2,4,15
• 0-2,4,16
• 0-2,4,28
CS - Iu UP failure
• 0-2,4,37
• 0-2,4,40
• 0-2,4,45
CS - Directed retry
• 0-2,4,46
CS - Radio connection with UE lost
• 0-2,8,113
• 0-Other
CS - Other causes
• 1-2,4,14
• 1-2,4,15
• 1-2,4,16
• 1-2,4,28
PS - Iu UP failure
• 1-2,4,37
• 1-2,4,40
• 1-2,4,45
PS - Directed retry
• 1-2,4,46
PS - Radio connection with UE lost
• 1-2,8,113
• 1-Other
3-92
A50016-G5000-E202-3-7618
PS - Other causes
(e) iuRelReq
(h) 185
(i) When RANAP IU RELEASE REQUEST is sent
3.14.2 Number of Iu release requests per release cause RNC related

(a) This measurement provides the number of UTRAN-initiated Iu
connection releases occurred within a foreign RNC (DRNC).
Separate subcounters are defined for different release causes and
for separation of CS and PS.
(b) CC.
(c) Transmission of a RANAP-message IU RELEASE REQUEST

sent by the UTRAN to the CN. Causes are defined within 3GPP
TS25.413 and shall be separated for CS and PS. If the RNC is
connected to both MSC and SGSN, both IU RELEASE
REQUEST messages may be considered. If the affected UE is in
soft handover, only the appropriate counter of the most recently
added cell of the active set shall be increased.
PS.
• 0-2,4,14
• 0-2,4,15
• 0-2,4,16
• 0-2,4,28
CS - Iu UP failure
• 0-2,4,37
• 0-2,4,40
3-93
A50016-G5000-E202-3-7618
• 0-2,4,45
CS - Directed retry
• 0-2,4,46
• 0-2,8,113
• 0-Other
CS - Other causes
• 1-2,4,14
• 1-2,4,15
• 1-2,4,16
• 1-2,4,28
PS - Iu UP failure
• 1-2,4,37
• 1-2,4,40
• 1-2,4,45
PS - Directed retry
• 1-2,4,46
• 1-2,8,113
• 1-Other
PS - Other causes
(e) iuRelReqRNC
(h) 195
(i) When a RANAP IU RELEASE REQUEST is sent.
3-94
A50016-G5000-E202-3-7618
3.14.3 Number of Iu release commands per release cause

(a) This measurement provides the number of CN-initiated Iu
connection releases for each cell. Separate subcounters are defined
for different release causes and for separation of CS and PS.
(b) CC.
(c) Receipt of a RANAP-message IU RELEASE COMMAND sent by

the CN to the UTRAN. Causes are defined within 3GPP TS25.413
and shall be separated for CS and PS. If the affected UE is in soft
handover, only the appropriate counter of the most recently added
cell of the active set shall be increased.
Prerequisite for the cell measurement function is that the cell
context is retained from the MRC until the IU RELEASE
COMMAND message is received. Namely, whenever the RNC
receives the RADIO LINK FAILURE INDICATION message and
the failing RL is the last RL of the RLS, the Cell ID shall be
retained for PM counter purpose until the IU RELEASE
COMMAND is received from the CN.
(d) A single integer value for each combination out of release cause
and CS/PS.
• 0-2,4,10
CS - Relocation cancelled
• 0-2,4,11
CS - Successful relocation
• 0-2,4,14
• 0-2,4,15
• 0-2,4,16
• 0-2,4,28
CS - Iu UP failure
• 0-2,4,31
CS - No remaining RAB
• 0-2,4,37
• 0-2,4,40
• 0-2,4,45
CS - Directed retry
3-95
A50016-G5000-E202-3-7618
• 0-2,4,46
• 0-2,6,83
CS - Normal release
• 0-2,8,113
• 0-2,8,115
• 0-Other
CS - Other causes
• 1-2,4,10
PS - Relocation cancelled
• 1-2,4,11
PS - Successful relocation
• 1-2,4,14
• 1-2,4,15
• 1-2,4,16
• 1-2,4,28
PS - Iu UP failure
• 1-2,4,31
PS - No remaining RAB
• 1-2,4,37
• 1-2,4,40
• 1-2,4,45
PS - Directed retry
• 1-2,4,46
• 1-2,6,83
PS - Normal release
• 1-2,8,113
• 1-2,8,115
• 1-Other
3-96
A50016-G5000-E202-3-7618
PS - Other causes
(e) iuRelCmd
(h) 186
(i) When a RANAP IU RELEASE COMMAND is received.
3.14.4 Number of Iu release commands per release cause RNC

related
(a) This measurement provides the number of CN-initiated Iu
connection releases occurred within a foreign RNC (DRNC).
Separate subcounters are defined for different release causes and
for separation of CS and PS.
(b) CC.
(c) Receipt of a RANAP-message IU RELEASE COMMAND sent by

the CN to the UTRAN. Causes are defined within 3GPP TS25.413
and shall be separated for CS and PS. If the affected UE is in soft
handover, only the appropriate counter of the most recently added
cell of the active set shall be increased.
PS.
• 0-2,4,10
CS - Relocation cancelled
• 0-2,4,11
CS - Successful relocation
• 0-2,4,14
• 0-2,4,15
• 0-2,4,16
• 0-2,4,28
CS - Iu UP failure
• 0-2,4,31
3-97
A50016-G5000-E202-3-7618
CS - No remaining RAB
• 0-2,4,37
• 0-2,4,40
• 0-2,4,45
CS - Directed retry
• 0-2,4,46
• 0-2,6,83
CS - Normal release
• 0-2,8,113
• 0-2,8,115
• 0-Other
CS - Other causes
• 1-2,4,10
PS - Relocation cancelled
• 1-2,4,11
PS - Successful relocation
• 1-2,4,14
• 1-2,4,15
• 1-2,4,16
• 1-2,4,28
PS - Iu UP failure
• 1-2,4,31
PS - No remaining RAB
• 1-2,4,37
• 1-2,4,40
• 1-2,4,45
PS - Directed retry
• 1-2,4,46
3-98
A50016-G5000-E202-3-7618
• 1-2,6,83
PS - Normal release
• 1-2,8,113
• 1-2,8,115
• 1-Other
PS - Other causes
(e) iuRelCmdRNC
(h) 196
(i) When a RANAP IU RELEASE COMMAND is received.
3.15 Number of drifting UEs

inter RNC radio link additions. For each branch addition belonging
to a cell in a DRNC, the counter is incremented.
(b) CC.
(c) Receipt of an RRC message ACTIVE SET UPDATE COMPLETE

sent from the UE to the UTRAN, indicating the success of an
outgoing inter RNC branch addition procedure. Namely, on
determination of the branch addition type the counter is
incremented in case the RNC ID of the added cell is different the
RNC ID of the recording RNC (SRNC).
(d) An integer value for each Branch addition per adjacent RNC. The
number of adjacent RNCs may vary dynamically, e.g., if a new
neighbor RNC is created.
(e) ShoAddDriftingUeSucc
(g) ADJACENT RNC RELATION measurement function.
(h) 17
(i) When an RRC ACTIVE SET UPDATE COMPLETE is received.
3-99
99 Pages
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03
SECTION 4
Subsystem-Related Measurements
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03 Subsystem-Related Measurements
4. Subsystem-Related Measurements
4.1 RNC Internal Measurements
4.1.1 RNC processor load

(a) This measurement provides the mean load of the RNC processors
during the complete granularity period for O&M applications (AP)
and call processing (CP).
(b) Gauge.
(c) AP usage ratio and CP usage ratio are measured periodically every
10 seconds for each processor of the RNC. At the end of the
granularity period, the mean values are provided.
• Mean value for CP usage ratio = the total of CP usage ratio
which is measured in the granularity period / the number of
times that CP usage ratio is measured in the granularity period
• Mean value for AP usage ratio = the total of AP usage ratio
which is measured in the granularity period / the number of
times that AP usage ratio is measured in the granularity period
(d) Six integer values (unit: percent) in total because 2 values (AP/CP)
are given to 3 processors.
• 0
AP load
• 1
CP load
(e) rncUsageRatio
(g) Processor measurement function.
(h) 20
(i) Based on CP usage ratio per 10 seconds, an average value is

calculated within a measurement period
4.1.2 DHT usage

(a) This measurement provides the DHT usage.
(b) Gauge.
4-1
A50016-G5000-E202-3-7618
(c) The usage of DHTs is measured every 10 seconds. At the end of

the granularity period, the mean, minimum and maximum value
are provided.
• Mean value = the total number of used DHTs* which is
measured in the granularity period / the number of times that
the number of used DHTs* is measured in the granularity
period
• Minimum value = the minimum number in the number of used
DHTs* which is measured in the granularity period
• Maximum value = the maximum number in the number of
used DHTs* which is measured in the granularity period
*The DHT trunks are the unit of the resource which is required
every call and are accommodated in DHT card. The number of
DHT trunks which are in the condition that the circuit has been
hunt and the resource has been secured of all DHT cards in RNC is
counted as the number of used DHTs. As the DHT trunk role, in
case of downlink (to UE from RNC), the same data is sent to more
than one branch.
Note: The number of used DHTs changes by the bandwidth. It does
not change by “soft handover ratio” and “packet average
ratio”.
Also, DHT usage ratio can be calculated every 10 seconds
by the following calculation method.
DHT usage ratio = (the number of used DHTs / the number
of existing DHTs**) X 100 (%).
**The number of existing DHTs does not contain the
number of blocked DHTs and faulty DHTs.
(d) Three integer values for mean, minimum, maximum value.

• 0
Mean
• 1
Minimum
• 2
Maximum
(e) dhtUsage
(h) 23
(i) Based on the number of lines in use obtained from line resources
per 10 seconds, average, minimum and maximum values are
4-2
A50016-G5000-E202-3-7618
calculated within a pmcCommand measurement period.
4.1.3 DHT busy time

(a) This measurement provides the time all DHTs are busy.
(b) Gauge.
(c) The usage of DHTs is measured every 10 seconds. Every time the
amount of available resources is smaller than the resource that
would be required for a further maximum-size bearer, the counter
is increased by the length of the interval.
When the number of used DHTs is equal to the number of existing
DHTs*, the 10 seconds are counted as DHT busy time.
*The number of existing DHTs does not contain the number of
blocked DHTs and faulty DHTs.
(e) dhtBusyTime
(h) 187
(i) In case the number of accommodated lines and the number of lines
in use that are obtained from line resources per 10 seconds are
same, all lines are in use. Thus, if once this case occurs, it is
calculated as 10 seconds. Namely, in case this case occurs 5 times
within a pmcCommand measurement period, the measurement
result is 50 seconds.
4.1.4 DHT busy rate

(a) This measurement provides the rate of DHT allocation requests,
which have been rejected due to overload.
(b) Gauge.
(c) This measurement is calculated out of the number of DHT

allocation requests, which have been rejected due to overload and
the number of all DHT allocation requests.
• Calculation method
DHT busy rate = (the number of failed DHT allocations* / the
number of attempted DHT allocations) X 100 (%)
*Number of failed DHT allocations = Number of attempted
4-3
A50016-G5000-E202-3-7618
DHT allocations - Number of successful DHT allocations

• Failed DHT allocation
It cannot be possible that DHT allocation fails, though the
maximum DHT usage is lower than 100%.
(d) An integer value (unit: percent).
(e) dhtBusyRate
(h) 24
(i) No. of line seizure failures (attempts - successes) / No. of line

seizure requests
This formula can give a measurement result because unless
available trunks are all in use, DHT allocation cannot fail.
4.1.5 Number of attempted DHT allocations

(a) This measurement provides the number of attempted DHT
allocations.
(b) CC.
(c) This measurement type counts the number of times that DHT
resource allocation is required.
The requirement of DHT resource allocation contains “the
requirement of the resource allocation for ordinary call”, “the
requirement of the resource allocation for maintenance call”, “the
test reservation for ordinary test call” and “the test reservation for
maintenance test call”.
(e) dhtAllocAtt
(h) 21
(i) Based on the number of line seizure requests per 10 seconds, the
total is obtained within a pmcCommand period.
4-4
A50016-G5000-E202-3-7618
4.1.6 Number of successful DHT allocations

(a) This measurement provides the number of successful DHT
allocations.
(b) CC.
(c) This measurement type counts the number of times that DHT
resource allocation succeeds.
(e) dhtAllocSucc
(h) 22
(i) Based on the number of line seizure successes per 10 seconds, the
total sum is calculated within a pmcCommand period.
4.1.7 PRLC usage

(a) This measurement provides the PRLC usage.
(b) Gauge.
(c) The usage of PRLCs is measured every 10 seconds. At the end of

the granularity period, the mean, minimum and maximum value
are provided.
• Mean value = the total number of used PRLCs* which is
measured in the granularity period / the number of times that
the number of used PRLCs* is measured in the granularity
period
• Minimum value = the minimum number in the number of used
PRLCs* which is measured in the granularity period
• Maximum value = the maximum number in the number of
used PRLCs* which is measured in the granularity period
*The PRLC trunks are the unit of the resource which is required
every call and are accommodated in PRLC card. The number of
PRLC trunks which are in the condition that the circuit has been
hunt and the resource has been secured of all PRLC cards in RNC
is counted as the number of used PRLCs. The PRLC trunk is used
in case of PS call and terminates Layer 2 protocol (RLC) between
UE and RNC. It terminates Node IP, UDP and GTP-U protocols.
Note: The number of used PRLCs changes by the bandwidth. It
4-5
A50016-G5000-E202-3-7618
does not change by “soft handover ratio” and “packet

average ratio”.
Also, PRLC usage ratio can be calculated every 10 seconds
by the following calculation method.
PRLC usage ratio = (the number of used PRLCs / the
number of existing PRLCs**) X 100 (%).
**The number of existing PRLCs does not contain the
number of blocked PRLCs and faulty PRLCs.
(d) Three integer values for mean, minimum, maximum value.

• 0
Mean
• 1
Minimum
• 2
Maximum
(e) prlcUsage
(h) 188
(i) Based on the number of lines in use obtained from line resources
per 10 seconds, average, minimum and maximum values are
calculated within a pmcCommand period.
4.1.8 PRLC busy time

(a) This measurement provides the time all PRLCs are busy.
(b) Gauge.
(c) The usage of PRLCs is measured every 10 seconds. Every time the
amount of available resources is smaller than the resource that
would be required for a further maximum-size bearer, the counter
is increased by the length of the interval.
When the number of used PRLCs is equal to the number of
existing PRLCs*, the 10 seconds are counted as PRLC busy time.
*The number of existing PRLCs does not contain the number of
blocked PRLCs and faulty PRLCs.
(e) prlcBusyTime
4-6
A50016-G5000-E202-3-7618
(h) 189
(i) In case the number of accommodated lines and the number of lines
in use that are obtained from line resources per 10 seconds are
same, all lines are in use. Thus, if once this case occurs, it is
calculated as 10 seconds. Namely, in case this case occurs 5 times
within a pmcCommand measurement period, the measurement
result is 50 seconds.
4.1.9 PRLC busy rate

(a) This measurement provides the rate of PRLC allocation requests,
which have been rejected due to overload.
(b) Gauge.
(c) This measurement is calculated out of the number of PRLC

allocation requests, which have been rejected due to overload and
the number of all PRLC allocation requests.
PRLC busy rate = (the number of failed PRLC allocations* /
the number of attempted PRLC allocations) X 100 (%)
*Number of failed PRLC allocations = Number of attempted
PRLC allocations - Number of successful PRLC allocations
• Failed PRLC allocation
It cannot be possible that PRLC allocation fails, though the
maximum PRLC usage is lower than 100%.
(e) prlcBusyRate
(h) 76
(i) No. of line seizure failures (attempts - successes) / No. of line

seizure requests
This formula can give a measurement result because unless
available trunks are all in use, DHT allocation cannot fail.
4-7
A50016-G5000-E202-3-7618
4.1.10 Number of attempted PRLC allocations

(a) This measurement provides the number of attempted PRLC
allocations.
(b) CC.
(c) Attempt to allocate resources of a PRLC.

The requirement of PRLC resource allocation contains “the
requirement of the resource allocation for PS call”.
(e) prlcAllocAtt
(h) 190
(i) Based on the number of line seizure requests per 10 seconds, the
total is obtained within a pmcCommand period.
4.1.11 Number of successful PRLC allocations

(a) This measurement provides the number of successful PRLC
allocations.
(b) CC.
(c) This measurement type counts the number of times that PRLC
resource allocation succeeds.
(e) prlcAllocSucc
(h) 191
(i) Based on the number of line seizure successes per 10 seconds, the
total sum is calculated within a pmcCommand period.
4-8
A50016-G5000-E202-3-7618
4.2 Iub Interface Measurements
4.2.1 Mean user data throughput (uplink/downlink) on dedicated

channels per Node B
(a) This measurement provides the mean user data throughput on all
dedicated channels per Node B. Separate subcounters are defined
for UL and DL direction and separation of CS and PS.
(b) Gauge.
(c) The counters are updated by transmission/reception of RLC PDUs

on dedicated channels towards/from Node B.
The measurement of the mean user data rate determines the
number of transmitted/received octets per RLC PDU block in the
granularity period and divides it by the length of the granularity
period.
Remark, that padding data are included and that therefore not the
pure user traffic is provided.
Note: Throughput measurements can be activated for up to 50
Node Bs at a time.
(d) An integer value for each combination of UL and DL direction and

CS/PS per Node B in bytes per second.
• 0-0
CS - Downlink
• 0-1
CS - Uplink
• 1-0
PS - Downlink
• 1-1
PS - Uplink
(e) userThroughputDCIub
(f) Administratable per Node B.
(g) Node B measurement function.
(h) 140
(i) The number of octets on RLC PDU transmitted/received towards/

from Node B per second.
A value measured by firmware per 5 minutes is notified to PM
counter for next 5 minutes, i.e., the value is output as PM data to
4-9
A50016-G5000-E202-3-7618
Hard Disk 5 minutes later. For example,
peri=5
n:00 n:05 n:10 n:15 n:20
x
y
z
x: Period while firmware is measuring

y: Period when PM counter is notified from firmware
z: Period when measured value is output as PM data to Hard Disk
4-10
A50016-G5000-E202-3-7618
4.2.2 FACH traffic load in kbps per cell

(a) This measurement provides the accumulated (user data) payload in
kbps (without signaling traffic) sent on FACH.
(b) Gauge.
(c) The counter is updated on transmission of RLC PDUs on FACH

channel(s) per cell.
(d) An integer value per FACH per cell
(e) fachTrafficPs
(h) 141
(i) A value measured by firmware per 1 minute is notified to PM

counter for next 1 minute, i.e., the value is output as PM data to
Hard Disk 1 minute later. For example,
peri=5
n:00 n:01 n:02 n:03 n:04 n:05 n:06 n:07 n:08 n:09 n:10
x1 x2 x3 x4 x5 x6 x7 x8 x9 xA
y1 y2 y3 y4 y5 y6 y7 y8 y9 yA
z1 z2
x1 - xA : Period while firmware is measuring

y1 - yA : Period when PM counter is notified from firmware
z1 : Period when the sum of measured values x1 to x4 are output
as PM data to Hard Disk
4-11
A50016-G5000-E202-3-7618
4.3 Blocking Measurements
4.3.1 Admission control
4.3.1.1 Number of rejections by admission control per cause

(a) This measurement provides the number of times admission control
rejects the RAB establishment request. For each rejection cause a
(b) CC.
(c) Condition for this measurement is the rejection of a radio bearer

establishment request due to the causes listed below. This shall
apply whenever admission control is called, be it for a RAB
assignment request from the CN, Branch addition procedure, Hard
handover procedure, RRC connection re-establishment, CTS,
BRA, or relocation request. As consequence the establishment
request for the new radio bearer will be rejected.
Note that even AC rejects a CTS or BRA, the service is provided
as operated before.
(d) A single integer value for each admission control rejection cause.
• 1,9,5
Cell restriction
• 1,9,6
Maximum uplink load
• 1,9,7
Maximum downlink load
• 1,9,8
Code allocation failure
• 1,9,9
Congestion control is ongoing
• Other
Other causes
(e) acRejections
(f) Administratable per cell.
(h) 150
(i) The number of octets on RLC PDU transmitted/received towards/
4-12
A50016-G5000-E202-3-7618
from Node B per second.
4.3.2 Congestion control
4.3.2.1 Number of times congestion control is activated per

congestion cause
(a) This measurement provides the number of times congestion
control is activated. For each cause a separate subcounter is
defined.
(b) CC.
(c) Congestion control is activated on exceeding

• the upper threshold of the uplink received total wide band
power or
• the upper threshold of the downlink transmitted carrier power.
Condition to trigger congestion control is the receipt of an event-
triggered common measurement report over Iub indicating the
threshold exceeding.
(d) A single integer value for each congestion cause.

• 1,9,10
Uplink received total wide band power
• 1,9,11
Downlink received total wide band power
• Other
Other causes
(e) ccTrigger
(f) Administratable per cell.
(h) 151
(i) None.
4-13
A50016-G5000-E202-3-7618
4.4 Channel Measurements
4.4.1 PCH usage rate

(a) This measurement provides the usage rate on PCH.
(b) Gauge.
(c) This measurement is calculated by the ratio out of the number of

sent messages on the PCH to the maximum capacity of the PCH.
PCH usage rate = (the number of sent data on the PCH / the
maximum capacity of the PCH*) X 100 (%)
*The maximum capacity of the PCH = the number of PCH TB
multiplex X (the sampling period /TTI)
(e) pchUsageRate
(h) 79
(i) No. of PCH Transaction Blocks (TBs) sent / Max. No. of PCH TBs
sendable:
• No. of PCH TBs sent is notified from firmware per 1 min.
• Max. No. of PCH TBs sendable is obtained from office data.
A value measured by firmware per 1 minute is notified to PM
peri=5
n:00 n:01 n:02 n:03 n:04 n:05 n:06 n:07 n:08 n:09 n:10
x1 x2 x3 x4 x5 x6 x7 x8 x9 xA
y1 y2 y3 y4 y5 y6 y7 y8 y9 yA
z1 z2

4-14
A50016-G5000-E202-3-7618
4.4.2 PCH discard rate

(a) This measurement provides the discard rate on PCH.
(b) Gauge.

discarded messages on the PCH to the number of all messages sent
on the PCH.
MHC cards in RNC only measure each number value of the
following:
PCH discard rate = Number of discarded paging record* / Number
of received paging records
*Number of discarded paging record:
PCH TrCH is being sent in specific time interval.
When MHC cannot insert the paging record to PCH frame in
appropriate time because of No insert area, MHC counts this
paging record as discarded paging record.
(e) pchDiscardRate
(h) 198
(i) No. of discarded paging records / No. of received paging records:

Nos. are respectively notified from firmware per 1 min.
4-15
A50016-G5000-E202-3-7618
peri=5
n:00 n:01 n:02 n:03 n:04 n:05 n:06 n:07 n:08 n:09 n:10
x1 x2 x3 x4 x5 x6 x7 x8 x9 xA
y1 y2 y3 y4 y5 y6 y7 y8 y9 yA
z1 z2

4-16
A50016-G5000-E202-3-7618
4.4.3 FACH usage rate

(a) This measurement provides the traffic load on FACH.
(b) Gauge.
(c) This measurement is calculated by the radio out of the number of

sent messages on the FACH to the maximum capacity of the
FACH.
There are two FACH links in a cell: one is for User Data, the other
for Control Data.
FACH usage rate = [(the number of sent data on the FACH Link 1 /
the maximum capacity of the FACH* Link 1) + (the number of
sent data on the FACH Link 2 / the maximum capacity of the
FACH* Link 2)] / 2 X 100 (%)
*The maximum capacity of the FACH = the number of FACH TB
multiplex X (the sampling period / TTI)
(e) fachUsageRate
(h) 199
(i) No. of FACH Transaction Blocks (TBs) sent / Max. No. of FACH
TBs sendable:
• No. of FACH TBs sent is notified from firmware per 1 min.
• Max. No. of FACH TBs sendable is obtained from office data.
4-17
A50016-G5000-E202-3-7618
peri=5
n:00 n:01 n:02 n:03 n:04 n:05 n:06 n:07 n:08 n:09 n:10
x1 x2 x3 x4 x5 x6 x7 x8 x9 xA
y1 y2 y3 y4 y5 y6 y7 y8 y9 yA
z1 z2

4-18
A50016-G5000-E202-3-7618
4.4.4 FACH discard rate

(a) This measurement provides the discard rate of FACH.
(b) Gauge.

discarded messages on the FACH to the number of all messages
sent on the FACH.
MHC cards in RNC only measure each number value of the
following:
FACH discard rate = Number of discarded FACH TBs* / (Number
of sent FACH TBs + Number of discarded FACH TBs)
*Number of discarded FACH TBs:
MHC has memory buffers to save the sent data (TB).
When MHC fails to save the data since the buffer has been full,
MHC counts this data (TB) as discarded FACH TBs.
(e) fachDiscardRate
(h) 200
(i) No. of discarded FACH TBs / (No. of FACH TBs sent + No. of
discarded FACH TBs):
Nos. are respectively notified from firmware per 1 min.
4-19
A50016-G5000-E202-3-7618
peri=5
n:00 n:01 n:02 n:03 n:04 n:05 n:06 n:07 n:08 n:09 n:10
x1 x2 x3 x4 x5 x6 x7 x8 x9 xA
y1 y2 y3 y4 y5 y6 y7 y8 y9 yA
z1 z2

4-20
A50016-G5000-E202-3-7618
4.5 UE Quantity Measurements
4.5.1 Number of UEs per active link set size

(a) This measurement provides the number of UEs for every active
link set size. This measurement is available for FDD cells.
Clarification: “Active link set size” describes the number of radio
links in the active link set.
(b) Gauge.
(c) The calculation of this measurement is implementation-specific.

Due to the high complexity, there might be some inaccuracy for
this measurement.
• Dynamical updates
Whenever a radio link setup/addition for a UE is performed
(for any reason), the counter corresponding to the previous size
of the active set for each cell will be decremented. At the same
time, the counter corresponding to the new size of the active
set for each cell will be incremented. These counters are
measured in local area of the memory at all time. (These data
will be described as “Saved Data” hereafter.)
When the measurement of these counters are requested, the
following calculations take place for each counter:
• (A)
The “Saved Data” are referred every 10 seconds and the
sum of them (for each counter) are taken during the GP. (=
total number of UEs which is measured within the GP.)
• (B)
Number of times the data had been added = the GP / 10
seconds
At the end of GP, the following value is reported.
• (C)
Number of UEs per active link set size = (A)/(B)
• Initialization
The “Saved Data” will be initialized on Phase 2, 2.5 and 3
Restart. Therefore, the counting starts from 0 right after the
Phase 2, 2.5 and 3 Restart.
On Phase 1 Restart, these data are maintained. However, it has
to be recognized that in some circumstances, these data have
discrepancy in counters. (This happens when there are unstable
calls on Phase 1 Restart.)
4-21
A50016-G5000-E202-3-7618
(d) An integer value for the number of radio links in the active link set.
• 1
Active link set size = 1
• 2
• 3
(e) uesPerActiveLinkSetSize
(h) 205

• When active set size goes from 0 to 1
• When RRC connection is established
• When CELL_FACH is changed to CELL_DCH
• When incoming relocation succeeds
• When RRC connection is released
• When CELL_DCH is changed to CELL_FACH
• When outgoing relocation succeeds (from CELL_DCH state if
applicable)
• When outgoing inter-system handover succeeds (from
CELL_DCH if applicable)
• When a hard handover branch is added
• When a hard handover branch is deleted
4.5.2 Mean number of bearer services per cell related

(a) This measurement provides the mean number of bearer services
per cell related.
(b) Gauge.
(c) For determination of the mean number of bearer services the

corresponding counters are updated on the following conditions:
• When a bearer service is set up, which means the RANAP
message RAB ASSIGNMENT RESPONSE was sent toward
CN. Update of the counter shall be related to the assigned
bearer service, not to the required service.
4-22
A50016-G5000-E202-3-7618
• When a bearer service was released triggered by the RANAP

messages RAB ASSIGNMENT REQUEST indicating RABs
to be released was received from CN or when RAB RELEASE
REQUEST was sent toward CN. Remark, that all cells of the
active link set have to be considered. The same applies if the
RAB is released per IU RELEASE COMMAND/REQUEST
message.
• In case of Branch addition the bearer service shall be
considered within the added cell.
• In case of successful hard handover the corresponding counter
shall be decremented within the originating cell(s) and
incremented within the target cell(s). Of course only the
counter in the originating cell or the target cell is considered in
case of outgoing respectively incoming inter-system
handovers.
• In case of channel type switching an existing bearer type is
decremented and the counter corresponding to the new bearer
type is incremented.
• In case of Bit Rate Adaptations adaptations.
This measurement determines in intervals of 10 or 20 seconds the
number of bearer services currently busy. At the end of the
granularity period the arithmetic mean value of the samples is
calculated.
In order to have system-internally only integer values, the actual
value shall be multiplied by 1000. Before inserting these values
into OMC-database they are divided by 10 and sounded to the next
integer. For an appropriate display with 2 digits after the decimal
point these values fetched from the OMC-database have to be
divided by 100.
(d) An integer value for each bearer service.

• 0
SRB 3.4/3.4 Kbps
• 1
SRB13.6/13.6 Kbps
• 2
PS Interactive/Background in Cell_FACH state
• 3
PS Interactive/Background in Cell_PCH state
• 4
CS AMR speech 12.2 Kbps
• 5
• 6
4-23
A50016-G5000-E202-3-7618

• 7
• 8
• 9
• 10
• 11
• 12
• 13
• 14
• 15
• 16
• 17
• 18
• 19
• 20
• 21
• 22
• 23
• 24
• 25
4-24
A50016-G5000-E202-3-7618
• 26
• 27
• 28
• 29
• 30
• 31
(e) bearServiceperCell
(h) 152
4-25
25 Pages
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03
SECTION 5
RRC State Management
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03 RRC State Management
5. RRC State Management
5.1 Number of attempted transitions from CELL_DCH state

(a) This measurement provides the number of attempted switches
from CELL_DCH to another state for each cell.
(b) CC.
(c) Conditions for transition from CELL_DCH to any other state are
described in 3GPP TS25.331.
(d) An integer value for each target state out of CELL_FACH,

CELL_PCH, URA_PCH.
• 1
CELL_FACH
• 2
CELL_PCH
• 3
URA_PCH
(e) transFromCellDchAtt
(h) 121

• When CELL_DCH is changed to FACH
• When MeasurementReport(e4b) is received and when traffic
fall report is received from PRLC firmware
5.2 Number of unsuccessful transitions from CELL_DCH state per

failure cause
(a) This measurement provides the number of unsuccessful switches
from CELL_DCH to another state for each cell per cause.
(b) CC.
(c) Conditions for transition from CELL_DCH to any other state are
5-1
A50016-G5000-E202-3-7618
(d) An integer value for each failure cause and each target state out of
CELL_FACH, CELL_PCH, URA_PCH, for which the state
transition can fail.
• 1-3,2,1
CELL_FACH - Configuration unsupported
• 1-3,2,2
CELL_FACH - Physical channel failure
• 1-3,2,3
CELL_FACH - Incompatible simultaneous reconfiguration
• 1-3,2,4
CELL_FACH - Compressed mode runtime error
• 1-3,2,5
CELL_FACH - Protocol error
• 1-3,2,6
CELL_FACH - Cell update occurred
• 1-3,2,7
CELL_FACH - Invalid configuration
• 1-3,2,8
CELL_FACH - Configuration incomplete
• 1-NoReply
CELL_FACH - No reply
• 1-Other
CELL_FACH - Other causes
• 2-3,2,1
CELL_PCH - Configuration unsupported
• 2-3,2,2
CELL_PCH - Physical channel failure
• 2-3,2,3
CELL_PCH - Incompatible simultaneous reconfiguration
• 2-3,2,4
CELL_PCH - Compressed mode runtime error
• 2-3,2,5
CELL_PCH - Protocol error
• 2-3,2,6
CELL_PCH - Cell update occurred
• 2-3,2,7
CELL_PCH - Invalid configuration
• 2-3,2,8
CELL_PCH - Configuration incomplete
5-2
A50016-G5000-E202-3-7618
• 2-NoReply
CELL_PCH - No reply
• 2-Other
CELL_PCH - Other causes
• 3-3,2,1
URA_PCH - Configuration unsupported
• 3-3,2,2
URA_PCH - Physical channel failure
• 3-3,2,3
URA_PCH - Incompatible simultaneous reconfiguration
• 3-3,2,4
URA_PCH - Compressed mode runtime error
• 3-3,2,5
URA_PCH - Protocol error
• 3-3,2,6
URA_PCH - Cell update occurred
• 3-3,2,7
URA_PCH - Invalid configuration
• 3-3,2,8
URA_PCH - Configuration incomplete
• 3-NoReply
URA_PCH - No reply
• 3-Other
URA_PCH - Other causes
(e) transFromCellDchFail
(h) 122

• When CELL_DCH to FACH transition fails
• When RNSAP: ULDirectTransfer is received from the other
RNC after PhysicalCHReconf was sent
• When PhysicalCHReconfFailure is received
• When NG is received from PRLC firmware
• When NG is received from M2C firmware
• When rollback to DCH is completed after DtoC failure
5-3
A50016-G5000-E202-3-7618
• WhenRRC_Status is received
• When RRC abnormal message is received
• When software inside error occurs
5.3 Number of attempted transitions from CELL_FACH state

from CELL_FACH to another state for each cell.
(b) CC.
(c) Conditions for transition from CELL_FACH to any other state are
(d) An integer value for each target state out of CELL_DCH.

• 0
CELL_DCH
• 2
CELL_PCH
• 3
URA_PCH
(e) transFromCellFachAtt
(h) 123

• When CellUpdate or PhysicalCHReconfComp wait timer
expires
• When MeasurementReport(e4b) is received or when traffic rise
report is received from PRLC firmware
• When RABAssignmentReq(Setup) is received in
CELL_FACH state
• When a monitor report on no communication is received from
both PRLC and M2C firmware
5.4 Number of unsuccessful transitions from CELL_FACH state per

failure cause
from CELL_FACH to another state for each cell per cause.
5-4
A50016-G5000-E202-3-7618
(b) CC.
(c) Conditions for transition from CELL_FACH to any other state are
(d) An integer value for each failure cause and each target state out of
CELL_DCH which the state transition can fail.
• 0-3,2,1
CELL_DCH - Configuration unsupported
• 0-3,2,2
CELL_DCH - Physical channel failure
• 0-3,2,3
CELL_DCH - Incompatible simultaneous reconfiguration
• 0-3,2,4
CELL_DCH - Compressed mode runtime error
• 0-3,2,5
CELL_DCH - Protocol error
• 0-3,2,6
CELL_DCH - Cell update occurred
• 0-3,2,7
CELL_DCH - Invalid configuration
• 0-3,2,8
CELL_DCH - Configuration incomplete
• 0-NoReply
CELL_DCH - No reply
• 0-Other
CELL_DCH - Other causes
• 2-3,2,1
CELL_PCH - Configuration unsupported
• 2-3,2,2
CELL_PCH - Physical channel failure
• 2-3,2,3
CELL_PCH - Incompatible simultaneous reconfiguration
• 2-3,2,4
CELL_PCH - Compressed mode runtime error
• 2-3,2,5
CELL_PCH - Protocol error
• 2-3,2,6
CELL_PCH - Cell update occurred
• 2-3,2,7
5-5
A50016-G5000-E202-3-7618
CELL_PCH - Invalid configuration

• 2-3,2,8
CELL_PCH - Configuration incomplete
• 2-NoReply
CELL_PCH - No reply
• 2-Other
CELL_PCH - Other causes
• 3-3,2,1
URA_PCH - Configuration unsupported
• 3-3,2,2
URA_PCH - Physical channel failure
• 3-3,2,3
URA_PCH - Incompatible simultaneous reconfiguration
• 3-3,2,4
URA_PCH - Compressed mode runtime error
• 3-3,2,5
URA_PCH - Protocol error
• 3-3,2,6
URA_PCH - Cell update occurred
• 3-3,2,7
URA_PCH - Invalid configuration
• 3-3,2,8
URA_PCH - Configuration incomplete
• 3-NoReply
URA_PCH - No reply
• 3-Other
URA_PCH - Other causes
(e) transFromCellFachFail
(h) 124

• When CELL_FACH to another state transition fails
• When DCH resource seizure NG occurs by Admission Control
• When TransCHReconfComp wait timer expires
• When TransCHReconfFailure is received
5-6
A50016-G5000-E202-3-7618
• When PhysicalCHReconfComp wait timer expires

• When PhysicalCHReconfFailure is received
• When RRC_Status is received
5.5 Number of attempted transitions from CELL_PCH state

from CELL_PCH to CELL_FACH state for each cell.
Note: Due to modifications in the RRC State Model, direct
transitions from CELL_PCH to URA_PCH are possible.
(b) CC.
(c) Conditions for transition from CELL_PCH to CELL_FACH are

(e) transFromCellPchAtt
(h) 127

• When CELL_PCH is changed to another state
• When CellUpdate(UplinkDataTransmission) is received
• When CellUpdate(PagingResponse) is received
• When CellUpdate(CellReselection) messages more than the
number preset in office are received on CELL_PCH
5.6 Number of unsuccessful transitions from CELL_PCH state per

failure cause
from CELL_PCH to CELL_FACH state for each cell per cause.
Note: Due to modifications in the RRC State Model, direct
transitions from CELL_PCH to URA_PCH are possible.
(b) CC.
5-7
A50016-G5000-E202-3-7618
(c) Conditions for transition from CELL_PCH to CELL_FACH are


• 3,2,1
• 3,2,2
• 3,2,3
• 3,2,4
• 3,2,5
Protocol error
• 3,2,6
• 3,2,7
• 3,2,8
• NoReply
No reply
• Other
Other causes
(e) transFromCellPchFail
(h) 128

• When CELL_PCH to another state transition fails
• When UTRAN MOBILITY INFORMATION CONFIRM
cannot be received
5-8
A50016-G5000-E202-3-7618
5.7 Number of attempted transitions from URA_PCH state

from URA_PCH to CELL_FACH state.
(b) CC.
(c) Conditions for transition from URA_PCH to CELL_FACH are

(e) transFromUraPchAtt
(h) 133

• When URA PCH is changed to another state
• When CellUpdate(UplinkDataTransmission) is received
• When CellUpdate(PagingResponse) is received
5.8 Number of unsuccessful transitions from URA_PCH state per

failure cause
from URA_PCH to CELL_FACH state.
(b) CC.
(c) Conditions for transition from URA_PCH to CELL_FACH are


• 3,2,1
• 3,2,2
• 3,2,3
• 3,2,4
5-9
A50016-G5000-E202-3-7618
• 3,2,5
Protocol error
• 3,2,6
• 3,2,7
• 3,2,8
• NoReply
No reply
• Other
Other causes
(e) transFromUraPchFail
(h) 134

• When URA PCH to another state transition fails
• When UTRAN MOBILITY INFORMATION CONFIRM
cannot be received
5-10
10 Pages
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03
SECTION 6
Radio Measurements
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03 Radio Measurements
6. Radio Measurements
6.1 Received total wide band power

(a) This measurement collects the mean, minimum and maximum
received total wide band power value, which is described in 3GPP
TS25.215.
(b) Gauge.
(c) The current received total wide band power value is extracted from
the NBAP common measurement report at regular intervals. From
all single measurements during the granularity period, the mean
value is calculated and the minimum and maximum values are
selected.
When an NBAP COMMON MEASUREMENT REPORT
message is received, Received total wide band power / Transmitted
carrier power for the details of how the information is reported.
During the GP, the following calculations are performed:
• (A)
Sum of the data reported from Call Processing during the
GP.
• (B)
The number of times that the data of “Received total wide
band power” is reported from Call Processing within the
GP.
• (C)
Comparison of the received data and stored data find the
minimum and maximum values. The smaller value is
maintained for minimum and the larger value is maintained
for maximum.
• (D)
Mean value = (A)/(B)
• (E)
Minimum value:
The minimum value of the “Received total wide band
power” measured during the GP. Calculation (C) calculates
the value.
• (F)
Maximum value:
6-1
A50016-G5000-E202-3-7618
The maximum value of the “Received total wide band

power” measured during the GP. Calculation (C) calculates
the value.
(d) Three integer values for mean, minimum and maximum value.
• 0
Mean
• 1
Minimum
• 2
Maximum
(e) uuRecTotalWbPwr
(h) 206
(i) When NBAP COMMON MEASUREMENT REPORT is received
6.2 Transmitted carrier power

(a) This measurement collects the mean, minimum and maximum
transmitted carrier power value, which is described in 3GPP
TS25.215.
(b) Gauge.
(c) The current value of transmitted carrier power value is extracted

from the NBAP common measurement report at regular intervals.
From all single measurements during the granularity period, the
mean value is calculated and the minimum and maximum values
are selected.
When an NBAP COMMON MEASUREMENT REPORT
message is received, Received total wide band power / Transmitted
carrier power for the details of how the information is reported.
During the GP, the following calculations are performed:
• (A)
Sum of the data reported from Call Processing during the
GP.
• (B)
The number of times that the data of “Transmitted carrier
6-2
A50016-G5000-E202-3-7618
power” is reported from Call Processing within the GP.

• (C)
Comparison of the received data and stored data find the
minimum and maximum values. The smaller value is
maintained for minimum and the larger value is maintained
for maximum.
• (D)
Mean value = (A)/(B)
• (E)
Minimum value:
The minimum value of the “Transmitted carrier power”
measured during the GP. Calculation (C) calculates the
value.
• (F)
Maximum value:
The maximum value of the “Transmitted carrier power”
measured during the GP. Calculation (C) calculates the
value.
(d) Three integer values for mean, minimum and maximum value.
• 0
Mean
• 1
Minimum
• 2
Maximum
(e) uuTransmCarrierPwr
(h) 99
(i) When NBAP COMMON MEASUREMENT REPORT is received
6.3 Number of used codes per spreading factor

(a) This measurement provides the mean number of used DL
channelization codes for each code type spreading factor.
(b) Gauge.
6-3
A50016-G5000-E202-3-7618
(c) The calculation of this measurement is implementation-specific.

• Dynamical updates
When the code management algorithm in MRC successfully
allocates (hunts) a new code in the code tree, the appropriate
counter will be incremented. On the other hand, if the code
management algorithm in MRC releases (frees / makes
available) a code in the code tree, the appropriate counter will
be decremented. These counters are measured in local area of
the memory at all time. (These data will be described as
“Saved Data” hereafter.)
When the measurement of these counters are requested, the
following calculations take place for each counter:
• (A)
The “Saved Data” are referred every 10 seconds and the
sum of them (for each counter) are taken during the GP. (=
total number of UEs which is measured within the GP.)
• (B)
Number of times the data had been added = the GP / 5
minutes
• (C)
Number of used codes = (A)/(B)
• Initialization
The “Saved Data” will be initialized on Phase 2, 2.5 and 3
Restart. Therefore, the counting starts from 0 right after the
Phase 2, 2.5 and 3 Restart.
On Phase 1 Restart, these data are maintained. However, it has
to be recognized that in some circumstances, these data have
discrepancy in counters. (This happens when there are unstable
calls on Phase 1 Restart.)
(d) An integer value for each supported DL factor.

• 0-0
SF4 - Downlink
• 1-0
SF8 - Downlink
• 2-0
SF16 - Downlink
• 3-0
SF32 - Downlink
• 4-0
6-4
A50016-G5000-E202-3-7618
SF64 - Downlink
• 5-0
SF128 - Downlink
• 6-0
SF256 - Downlink
• 7-0
SF512 - Downlink
(e) uuCodesUsed
(h) 82

• After (++) RRC CONNECTION REQUEST was received and
before NBAP RL SETUP REQUEST is sent
• After (++) RANAP RAB ASSIGNMENT REQUEST was
received and before NBAP RL RECONFIGURATION
PREPARE is sent
• After (--) NBAP RL RECONFIGURATION COMMIT was
sent
• After (--) NBAP RL RECONFIGURATION CANCEL was
sent
6.4 Number of attempted code requests per spreading factor

(a) This measurement collects the number of attempted code requests
for each DL spreading factor.
(b) CC.
(c) Attempt to allocate a channelization code.

On every attempted code request, the appropriate counter for the
used DL spreading factor is increased.
(d) An integer value for each supported DL spreading factor.

• 0-0
SF4 - Downlink
• 1-0
SF8 - Downlink
• 2-0
6-5
A50016-G5000-E202-3-7618
SF16 - Downlink
• 3-0
SF32 - Downlink
• 4-0
SF64 - Downlink
• 5-0
SF128 - Downlink
• 6-0
SF256 - Downlink
• 7-0
SF512 - Downlink
(e) uuCodeReqAtt
(h) 102

• RRC CONNECTION REQUEST was received and a
channelization code allocation was attempted
• RANAP RAB ASSIGNMENT REQUEST was received and a
• QAAL2(Iu) ESTABLISH RESPONSE was received and a
• RRC MEASUREMENT REPORT was received and a
6.5 Number of successful code requests per spreading factor

(a) This measurement collects the number of successful code requests
for each DL spreading factor.
(b) CC.
(c) Successful allocation of a channelization code.

On every attempted code request, the appropriate counter for the
used DL spreading factor is increased.
(d) An integer value for each supported DL spreading factor.

• 0-0
SF4 - Downlink
6-6
A50016-G5000-E202-3-7618
• 1-0
SF8 - Downlink
• 2-0
SF16 - Downlink
• 3-0
SF32 - Downlink
• 4-0
SF64 - Downlink
• 5-0
SF128 - Downlink
• 6-0
SF256 - Downlink
• 7-0
SF512 - Downlink
(e) uuCodeReqSucc
(h) 221

• RRC CONNECTION REQUEST was received and a
channelization code was successfully allocated
• RANAP RAB ASSIGNMENT REQUEST was received and a
• QAAL2(Iu) ESTABLISH RESPONSE was received and a
• RRC MEASUREMENT REPORT was received and a
6-7
7 Pages
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03
SECTION 7
ATM Measurements
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03 ATM Measurements
7. ATM Measurements
7.1 Ingress cells (for STM-1, E1)

(a) For STM-1, This measurement type counts the number of all ATM
cells (except idle cells) which come into TINF from STM-1 line.
For E-1, This measurement type counts the number of all ATM
cells (except idle cells) which come into DTI from E-1 line.
(b) CC.
(c) Same as (a).
(e) lineIncomingCells
(f) Administratable per Line.
(g) ATM Line measurement function.
(h) 207
(i) When the number of incoming cells is notified from firmware per
line every 5 minutes within a pmcCommand period
peri=5
n:00 n:05 n:10 n:15 n:20
x
y
z

7-1
A50016-G5000-E202-3-7618
7.2 Egress cells (for STM-1, E1)

(a) For STM-1, This measurement type counts the number of all ATM
cells (except idle cells) which go out from TINF to STM-1 line.
For E-1, This measurement type counts the number of all ATM
cells (except idle cells) which go out from DTI to E-1 line.
(b) CC.
(c) Same as (a).
(e) lineOutgoingCells
(h) 208
(i) When the number of outgoing cells is notified from firmware per
line every 5 minutes within a pmcCommand period
peri=5
n:00 n:05 n:10 n:15 n:20
x
y
z

7-2
A50016-G5000-E202-3-7618
7.3 Ingress cells for VPC/VCC (for STM-1)

(a) This measurement type counts the number of all ATM cells (except
idle cells) which come into TINF from STM-1 VP/VC.
(b) CC.
(c) Same as (a).
(e) vpvcIncomingCells
(f) Administratable per VP/VC.
(g) ATM VP/VC measurement function.
(h) 209
(i) When the number of incoming cells is notified from firmware per
VP/VC every 5 minutes within a pmcCommand period
peri=5
n:00 n:05 n:10 n:15 n:20
x
y
z

7-3
A50016-G5000-E202-3-7618
7.4 Egress cells for VPC/VCC (for STM-1)

(a) This measurement type counts the number of all ATM cells (except
idle cells) which go out from TINF to STM-1 VP/VC.
(b) CC.
(c) Same as (a).
(e) vpvcOutgoingCells
(f) Administratable per VP/VC.
(g) ATM VP/VC measurement function.
(h) 210
(i) When the number of outgoing cells is notified from firmware per
VP/VC every 5 minutes within a pmcCommand period
peri=5
n:00 n:05 n:10 n:15 n:20
x
y
z

7-4
A50016-G5000-E202-3-7618
7.5 Cells discarded due to HEC violations (for E1)

(a) This measurement type counts the number of all ATM cells
(including idle cells) which are discarded due to an invalid header
pattern in ATM cells which come into DTI from E1 line.
(b) CC.
(c) Same as (a).
(e) discardedCellsHecViolation
(h) 211
(i) When the number of cells discarded by HeaderErr is notified from

firmware per line every 5 minute within a pmcCommand period
peri=5
n:00 n:05 n:10 n:15 n:20
x
y
z

7-5
A50016-G5000-E202-3-7618
7.6 Discarded cells due to congestion (for STM-1)

(a) This measurement type counts the number of all ATM cells
(including idle cells) which are discarded because buffer overflow
occurs due to congestion in ATM cells which come into TINF from
STM-1 line.
(b) CC.
(c) Same as (a).
(e) discardedCellsCongestion
(h) 212
(i) When the number of cells discarded by buffer overflow due to

congestion is notified from firmware per line every 5 minutes
within a pmcCommand period
peri=5
n:00 n:05 n:10 n:15 n:20
x
y
z

7-6
A50016-G5000-E202-3-7618
7.7 Cell loss ratio (for STM-1)

(a) This measurement type is the ratio of the number of discarded
ATM cells (except idle cells) due to congestion to the number of all
ATM cells (except idle cells) which come into TINF from STM-1
VP.
(b) Gauge.
(c) Cell loss ratio = (Discarded cells due to congestion for VPC
[ingress] / Ingress cells for VPC) X 100 (%)
(e) cellLossRatio
(f) Administratable per VP.
(g) ATM VP measurement function.
(h) 216
(i) Incoming discarded cell ratio is measured per VP within a

pmcCommand period.
peri=5
n:00 n:05 n:10 n:15 n:20
x
y
z

7-7
A50016-G5000-E202-3-7618
7.8 Congestion of VP (for STM-1)

(a) This measurement type is the ratio of the number of all ATM cells
(except idle cells) which go out from TINF to STM-1 VP to
maximum capacity of Egress cells.
(b) Gauge.
(c) Congestion of VP = (Egress cells of VPC / Maximum capacity of

Egress cells for VPC*) X 100 (%)
*Maximum capacity of Egress cells for VPC = maximum
bandwidth for VPC [egress] X granularity period
Note: “Congestion of VP” does not really measure “congestion”,
but it measures the “VP usage ratio” instead.
(e) congestionOfVP
(f) Administratable per VP.
(g) ATM VP measurement function.
(h) 217
(i) Outgoing discarded cell ratio is measured per VP within a

pmcCommand period.
peri=5
n:00 n:05 n:10 n:15 n:20
x
y
z

7-8
8 Pages
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03
SECTION 8
Measurements Collected by the Node B
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03 Measurements Collected by the Node B
8. Measurements Collected by the

Node B
8.1 Node B CP (Call Processing) Usage Ratio

(a) Node B PF1:
This measurement provides the mean call processing load of the
Node B during the complete granularity period.
Node B PF2:
This measurement provides the mean load of the Node B CC (Core
Control) processor; this includes both CP load and O&M load.
(b) Gauge.
(c) The scanner obtains a CPU usage ratio (Rn) for a specific
measurement period from “macroNodeBFDDE” per 10 seconds
and accumulates the obtained values. After the GP, the result is
obtained by the calculation below:
Result = (R1+R2+...+Rn) / n*
*n is the number of times that Rn is obtained and is equal to the
granularity period / 10 seconds in principle.
(e) cpUsageRatio (Node B PF1); ccProcessorLoad (Node B PF2)
8.2 Node B BB (Base Band) Usage Ratio

(a) This measurement provides the mean base band load of the Node
B during the complete granularity period.
In other words, this measurement indicates how many CHC card
resources (i.e. BB resources) are used for the communications.
(b) Gauge.
(c) Calculation is different between Node B PF1 and Node B PF2:

• Node B PF1
Result = (A) / (A+B) X 100 (%)
A = no. of all used CHC resources for Dedicated CH (UL=DL)
B = no. of all available CHC resources (UL=DL)
8-1
A50016-G5000-E202-3-7618
• Node B PF2
Result = (1- current CEs / initial CEs) X 100 (%)
current CEs: sum of available downlink - CEs at all CHs
initial CEs: sum of all initially available downlink CEs at all
CHs
(e) bbUsageRatio
8.3 Rest of Call Capacity

(a) This measurement provides the rest of BB resource which can
support traffic calls.
(b) Gauge.
(c) The scanner obtains the number of circuits (Cn) for a specific
measurement period from “macroNodeBFDDE” per 10 seconds
and accumulates the obtained values. Note that, however, Cn is a
value cumulating 10 values measured at the 1-second sampling
cycle by PF. After the GP, the result is obtained by the calculation
below:
Result = (C1+C2+...+Cn) / (n X 10)
(e) restOfCallCapacity
8.4 SCCPCH Usage Ratio

(a) This measurement provides the SCCPCH usage ratio.
(b) Gauge.
(c) The scanner obtains the total number of sending cells (Tn) and the
number of frames in use (Un) for a specific measurement period
from “localCellE” per 10 seconds and accumulates the obtained
values. After the GP, the result is obtained by the calculation
below:
8-2
A50016-G5000-E202-3-7618
There may be some SCCPCHs per local cell. In this case,

“localCellE” accumulates all the SCCPCH measurement values
and sends it to the scanner.
Result = (U1+U2+...+Un) / (T1+T2+...+Tn) X 100 (%)
(e) sccpchUsageRatio
8.5 PRACH Usage Ratio

(a) This measurement provides the PRACH usage ratio.
(b) Gauge.
(c) The scanner obtains the total number of receiving cells (Tn) and
the number of bits in use (Un) for a specific measurement period
from “localCellE” per 10 seconds and accumulates the obtained
values. After the GP, the result is obtained by the calculation
below:
There may be some PRACHs per local cell. In this case,
“localCellE” accumulates all the PRACH measurement values and
sends it to the scanner.
Result = (U1+U2+...+Un) / (T1+T2+...+Tn) X 100 (%)
(e) prachUsageRatio
8.6 Number of Receiving Preambles

(a) This measurement provides the number of preambles received on
the specified PRACH.
(b) CC.
(c) The scanner obtains the number of receiving preambles (Pn) for a
specific measurement period from “localCellE” per 10 seconds
and accumulates the obtained values. After the GP, the result is
obtained by the calculation below:
8-3
A50016-G5000-E202-3-7618
There may be some PRACHs per local cell. In this case,

“localCellE” accumulates all the PRACH measurement values and
sends it to the scanner.
Result = P1+P2+...+P3
(e) numberOfReceivingPreambles
8.7 HEC Error Ratio

(a) This measurement provides the ratio of lost ATM cells received
from RNC because of HEC (Header Error Control) error.
(b) Gauge.
the number of HEC error cells (En) for a specific measurement
period from “physLine” per 10 seconds and accumulates the
obtained values. After the GP, the result is obtained by the
calculation below:
Result = (E1+E2+...+En) / (T1+T2+...+Tn) X 100 (%)
(e) hecErrorRatio (Node PF1 only)
8.8 HEC Error Number

(a) This measurement provides the number of lost ATM cells received
from RNC because of HEC error.
(b) CC.
the number of HEC error cells (En) for a specific measurement
period from “physLine” per 10 seconds and accumulates the
calculation below:
Result = E1+E2+...+En
8-4
A50016-G5000-E202-3-7618
(e) hecErrorNumber (Node PF1 only)
8.9 Number of Faulty ATM Cells (PTI)

(a) This measurement provides the number of invalid PTIs (Protocol
Type Identifiers) of the headers of ATM cells received from RNC.
(b) CC.
(c) The scanner obtains the number of ATM Cell Protocol Error [PTI]
(Pn) occurrences from “vpc” per 10 seconds and accumulates the
calculation below:
Result = P1+P2+...+Pn
(e) atmCellProtocolErrorPti (PF1 Node B only)
8.10 Number of Faulty ATM Cells (VCI)

(a) This measurement provides the number of invalid VCIs (Virtual
Channel Identifiers) of the headers ATM cells received from RNC.
(b) CC.
(c) The scanner obtains the number of ATM Cell Protocol Error [VCI]
(Vn) occurrences from “vpc” per 10 seconds and accumulates the
calculation below:
Result = V1+V2+...+Vn
(e) atmCellProtocolErrorVci (Node PF1 only)
8-5
A50016-G5000-E202-3-7618
8.11 Total Number of Transmitted ATM Cells

(a) This measurement provides the total number of ATM cells sent to
RNC.
(b) CC.
(c) The scanner obtains the total number of sending cells (Tn)
occurrences from “vpc” per 10 seconds and accumulates the
calculation below:
Result = T1+T2+...+Tn
(e) totalNumberOfTransmitCell (Node PF1 only)
8.12 Total Number of Received ATM Cells

(a) This measurement provides the total number of ATM cells
received from RNC.
(b) CC.
(c) The scanner obtains the total number of receiving cells (Rn)
occurrences from “vpc” per 10 seconds and accumulates the
calculation below:
Result = R1+R2+...+Rn
(e) totalNumberOfReceivingCell (Node PF1 only)
8.13 Ratio of Lost ATM Cells

(a) This measurement provides the ratio of lost ATM cells to cells sent
to the Iub (RNC).
(b) Gauge.
8-6
A50016-G5000-E202-3-7618
(c) The scanner obtains the total number of sending cells (Tn) and the
number of discarded cells (Dn) for a specific measurement period
from “vcc” per 10 seconds and accumulates the obtained values.
After the GP, the result is obtained by the calculation below:
Result = (D1+D2+...+Dn) / (T1+T2+...+Tn) X 100 (%)
(e) cellLossRatioInTransmission (Node PF1 only)
8-7
7 Pages
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03
SECTION 9
QoS Measurements
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03 QoS Measurements
9. QoS Measurements
9.1 QoS Measurement on the RNC

Observed types are always described in terms of ratios, with a theoretical
range between 0 and 100 percent. These ratios are always defined as
“negative indicators:” the appropriate alarm is generated when the ratio
exceeds the configured threshold; the alarm is cleared when the ratio falls
down under this threshold.
The following observed measurement is defined for RNC:
Table 9-1 Observed Measurement Defined for RNC
Observed Type Scanner MOC Observed MOC Comment
cpuUsageRatio rncScanner managedElement QoS Alarm is generated when the mean

CPU usage ratio of a single processor
exceeds the threshold.
The Additional Text field of the QoS
Alarm contains the load of every single
CPU.
9.2 QoS Measurements on the Node B

The following observed measurements are defined for Node B:
Table 9-2 Observed Measurements Defined for Node B
Observed Type Scanner MOC Observed MOC Comment
cpUsageRatio nbScanner managedElement -

bbUsageRatio nbScanner managedElement -
sccpchUsageRatio nbScanner cell -
prachUsageRatio nbScanner cell -
hecErrorRatio nbScanner physLine 1st platform only
cellLossRatio nbScanner vcc 1st platform only
9-1
1 Page
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03
SECTION 10
Abbreviation List
A50016-G5000-E202-3-7618
ND-57347-704 (E)-03 Abbreviation List
10. Abbreviation List
Abbreviation Meaning
3GPP Third Generation Partnership Project

ACM Adjacent Cell Measurement
ALCAP Access Link Control Application Part
AP Application
ASN.1 Abstract Syntax Notation No.1
ATM Asynchronous Transfer Mode
BB Base Band
CC Cumulative Counters
CCCH Common Control Channel
CE Channel Element
CFN Connection Frame Number
CGI Cell Global ID
CH Channel
CHC Channel Coding Card
CN Core Network
CM Configuration Management
CP Call Processing
CPICH Common Pilot Channel
CPU Central Processor Unit
CS Circuit Switched
DCCH Dedicated Control Channel
DCH Dedicated Channel
DHT Diversity Handover Trunk
DK Disk
DL Downlink
DTI Digital Transmission Interface
10-1
A50016-G5000-E202-3-7618
E1 European PDH Signal, Level1 (PCM30)

EDGE Enhanced Data Rates for GSM Evolution
FACH Forward Link Access Channel
FDD Frequency Division Duplex
GERAN GSM/EDGE Radio Access Network
GSM Global System for Mobile Communications
GTP GPRS Tunneling Protocol
HEC Header Error Correction
HHO Hard Handover
HW Hardware
IP Internet Protocol
M2C Mobile Layer 2 Controller
MEID managedElementId
MHC MAC Header Handling Controller
MMM Mean, Minimum, Maximum (values)
MOC Managed Object Class
MSC Mobile-services Switching Center
NBAP Node B Application Part
O&M Operation and Maintenance
PCH Paging Channel
PF Platform
PM Performance Management
PRACH Physical Random Access Channel
PRLC Packet for Radio Link Control
PS Packet Switched
PTI Protocol Type Identifier
QoS Quality of Service
RAB Radio Access Bearer
10-2
A50016-G5000-E202-3-7618
RANAP Radio Access Network Application Part

RAT Radio Access Technology
RL Radio Link
RLC Radio Link Control
RNC Radio Network Controller
RNS Radio Network System
RRC Radio Resource Control
RC Radio Commander
SCCPCH Secondary Common Control Physical Channel
SF Spreading Factor
SDU Signaling Data Unit (or service data unit)
SHO Soft Handover
SGSN Serving GPRS Support Node
SRNC Source RNC
STM-1 Synchronous Transfer Mode 1
TB Transaction Bearer
TINF Trunk Interface
TrCH Transport Channel
UDP User Datagram Protocol
UE User Equipment
UL Uplink
UMTS Universal Mobile Telecommunications System
URA UTRAN Registration Area
UTRAN UMTS Terrestrial Radio Access Network
VC Virtual Channel
VCC Virtual Channel Connection
VCI Virtual Channel Identifier
VP Virtual Path
10-3
A50016-G5000-E202-3-7618
VPC Virtual Path Connection
10-4
4 Pages

Tedpmc

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Tedpmc

Încărcat de

Drepturi de autor:

Formate disponibile

UTRAN

Performance Measurement Counter

UMTS Terrestrial Radio Access Network

Copyright (C) Siemens AG / NEC Corporation 2004, 2005.

Technical modifications possible.

This document consists of the following sections:

(1) Measurement Report File Format

(2) Common Information for RNC Measurements

(3) Procedure-Related Measurements

(4) Subsystem-Related Measurements

(5) RRC State Measurements

(6) Radio Measurements

(7) ATM Measurements

(8) Measurements Collected by the Node B

(9) QoS Measurements

(10) Abbreviation List

Description of the single measurement in this document, Sections 3 through 9,

(b) Collection Method

not possible to give a precise condition, then the conditional

(d) Measurement Result (measured value(s), units)

(e) Measurement Type

(f) Administrative Object Class

(g) Measurement Object Class

the lower layers (outside the scope of this document).

(h) mtype value

(i) Performance Measurement (PM) count trigger

Reason for Update

Definitions of new measurement types are added.

Chapter/Section Reason for Update

1. Measurement Report File Format ............................. 1-1

2. Common Information for RNC Measurements .... 2-1

3. Procedure-Related Measurements .......................... 3-1

4. Subsystem-Related Measurements ......................... 4-1

5. RRC State Management................................................ 5-1

5.1 Number of attempted transitions

6. Radio Measurements ..................................................... 6-1

7. ATM Measurements ....................................................... 7-1

8. Measurements Collected by the Node B ............... 8-1

8.4 SCCPCH Usage Ratio ...................................................... 8-2

9. QoS Measurements ........................................................ 9-1

10. Abbreviation List ........................................................... 10-1

1. Measurement Report File Format

1.1 File Naming

The managedElementId (MEID) is set as Unique ID and described in

The MEID is set in file “sbs3gManagedElementID” which belongs to

1.2 Measurement Report File Format

1.2.1 Parameter description and mapping table

ASN.1 Tag Description

ASN.1 Tag Description

collectionBeginTime It is indicated as YYYYMMDDhhmmss.

ASN.1 Tag Description

measTypes Cell-Target-Cause type

ASN.1 Tag Description

measTypes (d) Adjacent GSM cell measurements

ASN.1 Tag Description

measTypes (g) Iub interface measurements

ASN.1 Tag Description

measObjInstld (a) Cell measurements

ASN.1 Tag Description

measObjInstld (d) Adjacent GSM cell (outgoing) measurements

ASN.1 Tag Description

measObjInstld (j) ATM (VP) measurements