411 9001 125.15

Wireless Service Provider Solutions
Observation Counter Dictionary

PE/DCL/DD/0125 15.154/EN Standard May 2006
411--9001--125
Copyright © 2000--2006 Nortel Networks
< 125 > : Observation Counter Dictionary

Document number: PE/DCL/DD/0125
411--9001--125
Document status: Standard
Document issue: 15.154/EN
Product release: GSM/BSS V15.1.1
Date: May 2006
Copyright © 2000--2006 Nortel Networks, All Rights Reserved
Originated in France
NORTEL CONFIDENTIAL:
The information contained in this document is the property of Nortel Networks. Except as specifically authorized in
writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential and
shall protect same in whole or in part from disclosure and dissemination to third parties and use for evaluation,
operation and maintenance purposes only.
You may not reproduce, represent, or download through any means, the information contained herein in any way or in
any form without prior written consent of Nortel Networks.
The following are trademarks of Nortel Networks: *NORTEL , the NORTEL corporate logo, the NORTEL Globemark,
UNIFIED NETWORKS, S2000, S4000, S8000. GSM is a trademark of France Telecom.
All other brand and product names are trademarks or registered trademarks of their respective holders.
Copyright © 2000--2006 Nortel Networks
Nortel Confidential Publication History iii
PUBLICATION HISTORY
System release:GSM/BSS V15.1.1
May 2006
Issue 15.154/EN Standard
Updated Chapter 4 Type and Class of counters to present counters by families
Removed information on BSC 12000 due to EOL (End Of Life)
Replaced all occurrences of BSC 2G with BSC 12000HC
Updated synthetic counters locators
February 2006
Updated definition of counter 1988 (section 5.3.2)
Updated the Q3 name of counter 3005/2 in table from section 4.1.16
November 2005
Updated dataflow diagram on intra--bts handover (section 2.4.3)
Updated synthetic counter 8707 (missing screenings are added to the formula)
Described toggling counters (section 3.7)
October 2005
Issue 15.151/EN Preliminary
Incorporated review comments
CR Q01206364: corrected the Q3 name of C2045 hoRequestOutgoingInterBss8W
and C2051 hoRequestOutgoingInterBssSdcch8W
Updated the definition of counters 1835 and 1809/0
Copyright © 2000--2006 Nortel Networks Observation Counter Dictionary

iv Publication History Nortel Confidential
July 2005
Issue 15.150/EN Draft
Updated the definitions of counter 2066, 2068, 1508, 15108/0 and 15109/0
Added a note to counter 3001/2, 3005/2
Removed the obsolete note on counters 1935, 1936, 1937, 1938, 1939 (Feature Id
22688 AMR based on traffic), and 2096 (Feature Id 15347 Network
synchronization)
Updated for CR Q01121801--02: modified the BSC 2G V15 memory threshold on
counter number (section 1.1.5)
Editorial update:
restructured Chapter 1 (created Chapter 2 on Data Flow Diagrams (DFD))
updated appendices
System release:GSM/BSS V15.1
July 2005
CR Q01166072: modified the Q3 name of C1720 to radioFrameUIReceived (from
abisTrauFrameUIReceived).
June 2005
Updated the descriptions of the counters pcuEdgeTdma15108s0 (15108/0) and
pcuEdgeTdma15109s0 (15109/0) in section 5.9.
Updated for Feature Id 29485 V15.1.1 new counters introduction in V15.1 to avoid
interface disruption. The counters 1508, 1935, 1936, 1937, 1938, 1939, and 2096
are all reserved for future use. See also the Publication History for April 2005 for
Issue 15.103/EN Preliminary of this document.
Updated for Feature Id 28422 eMLPP support on a GSM network.
CR Q01157430: moved the counters 1086, 1087, and 1088 from section 5.4 to
section 5.2.
PE/DCL/DD/0125 Standard 15.154/EN May 2006 Copyright © 2000--2006 Nortel Networks

411--9001--125
Nortel Confidential Publication History v
June 2005
CR Q01125865:
updated the formulas for the synthetic counters in section 5.6 (by adding the
greaterperc term where required).
reintroduced six synthetic counters in section 2.6 (8803, 8813, 9510, 9511, 9512,
9600)
Removed information on BSC6000 due to EOL.
April 2005
Synchronized with 15.0.1 Standard.
April 2005
CR Q01081655: updated inter--BSS handover Data Flow Diagram in section
1.2.4.5, and inter--CELL intra--BSS Data Flow Diagram in section 1.2.4.4
V15.1.1 counters added, and their value is set to 0 in V15.1:
Feature Id 15347 Network synchronization: added counter 2096
Feature Id 22688 AMR based on traffic: added counters 1935, 1936, 1937, 1938,
1939
Feature Id 29479 Paging capacity increase - UI mode - BSC 3000: added
counter 1508
Added the following counters: 1828/0, 1828/1, 1829/0, 1934/0, 2002/0, 2002/1,
2002/2, 2003/0
Integrated comments from V15.1 Draft review
Updated counter configuration list in section 4.2.1
Replaced transceiverZone/bts to bts/transceiverZone in object field of counter
descriptions
Index clean--up (phase 2)

vi Publication History Nortel Confidential
March 2005
Synchronized with V15.1R Standard
Integrated late review comments from V15.0.1 Preliminary
Index clean--up (phase 1)
February 2005
Synchronized with V15.0.1 Preliminary
January 2005
Issue 15.100 /EN Draft
Feature Id 13913 ASCI Evolutions: updated counters 1193/8, 1722/0, 1722/1,
2052/0, 2053/0
Feature Id 25155 GPRS/EDGE Suspend and Resume:
added new counters 2066, 2067, 2068/0, 2068/1, 2071/0, 2071/1, 2072, 2073
added four new Data Flow Diagrams in new section 1.2.8 GPRS / EDGE
Suspend and Resume
Feature Id 25494 EDGE Features: updated counter 15076/0
Feature Id 22915 Extended UL TBF: updated counters 15123/0 and 15193/0
Feature Id 26186 PS Paging Duplication on BSC: updated counters 1506/0, 1507/0
and 1507/4
Feature Id 26257 Paging Load Distribution on several LAPD: updated counters
15073/0 and 15073/1
Replaced occurrences of “BSC e3” by “BSC 3000” and “TCU e3” by “TCU 3000”
(throughout the guide)
Looked for occurrences of End--Of--Life products (BTS S4000 Indoor 1900, BTS
S4000 Outdoor 1900, BTS S4000 Smart 1900, BTS S2000 Indoor 1900 and BTS
S2000E Outdoor 1900), but there was none.

411--9001--125
Nortel Confidential Publication History vii
SYSTEM RELEASE: GSM/BSS V15.1R
January 2005
Issue 15.53/EN
CR Q00590181: added counters 1507/5 and 1803/5 in sections 1.3.16, 2.2, 2.3.1,
Update for Customer Readiness after internal review
November 2004
Issue 15.52/EN
Synchronized with V15.0 Standard
Feature Id 20571: DFD in section 1.2.10 for ASCI deleted. DFDs for main call
scenarios replace the previous ones.
counter name updates in section 4.2.1
Dictionary presentation moved from end of section 1 to beginning of section 2.
Updated locators for counters 1821 to 1827
August 2004
Issue 15.51/EN
Feature Id 20571: added section 1.2.10 for ASCI. Added counter 1193/8 in several
places.
Feature Id 23003: added section 2.2.2 for OTDI. updated counters 1722/0, 1722/1,
1723, 1724 and 1725
Feature Id 23717: added section 3.7 for Mobility Class Sensitivity Counters
Feature Id 24462: added Data Flow Diagram in section 1.2.10
Feature Id 26310: updated section 3.2.1. Added section 3.2.3
Feature Id 26479: added section 3.5 for BSCcounterlist size
CR Q00814652: added counters 1821 to 1827 in section 5.2
CR Q00934254: updated counters 1812, 1813, 1057, 1700, 1810, 1611, 1746 in
section 5.2
Updated Appendix for V15.1R counter evolutions
Reorganized Appendix for V15.x evolutions

viii Publication History Nortel Confidential
SYSTEM RELEASE: GSM/BSS V15.0

October 2004
Issue 15.25/EN Standard -- CR Q00956244 remove Counters 3002, 3003, 3006, and
3007 for customer clarification.
Misc cleanups
September 2004
August 2004
CR Q00964502 -- updated counters 1164/28 and 1164/32.
Removed parens from three counter locator names so WorldView will work.
August 2004
CR Q00956890 - updated counter 1803/4.
CR Q00956244 -- updated notes (Stating not implemented for v14.3 or v15) on
counters 3002, 3003, 3006, and 3007.
August 2004
CR Q00953889 -- removed counter 1163/29.
July 2004
CR Q00955246 - removed the string “Tch” from the counter names for counters
1065/1, 1066/1, 1067/1, and 1068/1.
Preparation for Helmsman release
July 2004
CR Q00941508 - multiple changes and additions from comments CR.

411--9001--125
Nortel Confidential Publication History ix
July 2004

CR Q00937150--02 - Incorporated CR comments to correct Formulas and updated
counters in Section 1 tables.
CR Q00940952 -- Incorporated CR comments for counter number 15193/0.
CR Q00862422 - Added counters 3004/1 and 3004/2 in Chapters 1 and 2. Also
placed them into the appropriate tables.
Added counters 1138/2/3/8 in Chapters 1, 2, and Appendix A for Feature 27215
July 2004

Reviewer remarks - adding counters to Appendix tables.
June 2004

CR Q00903347 - rename counters 1768/0, /1, 1769/0, /1, 1772/0, /1, and 1773/0,
/1, by replacing the word “cell” with “BSS”.
Correcting locator tags, missing counters, and spelling errors from source and last
load.
CR Q00918747 -- Removed counter 1052/0, 1052/1, and 1052/2, replaced with
counter 1611/0 and 1611/1.
June 2004

From reviewers remarks:
Removed para 1.5.4.1 ORT & IPO synthetic counters and table. “IPO synthetic
counters no more exist since V11... if same chapter already exist for V14 NTPs, it
is a mistake”.

x Publication History Nortel Confidential
May 2004
Incorporated Counter name changes 1772/0, 1772/1, and 1773/0, 1773/1 received
from email remarks.
Incorporated Counter definitions 15132/0 thru 15189/0 received from email
remarks.
Incorporated CR Q00873161 updated counters 1611/3, 1612/0, and 1612/1.
Added Feature 26797 - Directed Retry Counters
CR Q00184739--05 -- Counter 1721 name changed from
Erroneous_Frame_Number to ECU_Activation.
April 2004
Incorporated SME review comments.
March 2004
For CR Q00836666, deleted counters 3000/1, 3001/1, 3004/2 and 3005/1.
March 2004
Update for review comments.
For CR Q00835972--01, deleted 1835 counters cardSynthLoadBscb<x> and
cardSynthLoadTscb<x>.
March 2004
For CR Q00835972--01, deleted information concerning the 1835
cardSynthLoadBscb<x>Moy/Max counters.
For CR Q00792758, changed the description of SDCCH and changed the functions
of counter numbers 1609/2 and 1611/2.
For CR Q00841812
Modified features:
15015 GPRS TBF establishment improvement: one phase access
New features:
20219 EDGE link adaptation

411--9001--125
Nortel Confidential Publication History xi
January 2004
For CR Q00707442--01, incorporated minor changes.
December 2003
Modified features:
19174 EDGE Dynamic ABIS and AGPRS backhaul
20231 EDGE Traffic Management
22463 WPS BSS2G and E3 queuing mechanism enhancement
22464 WPS BSS2G and E3 access class barring with class periodic rotation
22465 WPS BSS2G and E3 public access bandwidth protection
SYSTEM RELEASE: GSM/BSS V14.3
October 2003
August 2003
Added AMR V14 counters in appendix A.
Added new BSC 2G V14 counters and BSCe3 V14 counters in Appendix A.
Checked the AMR and e3 counters.
Added the following e3 counter description: 3002, 3003, 3006, 3007, 1507/0,
1507/1, 1507/2, 1507/3, 1507/4.
Added the following AMR counter description: 1197/2, 1197/3, 1780/1, 1780/2,
1906/0, 1917/1, 1929/1.
Modified the following counter description: 1780/0, 1917/0, 1929/0.
Added the following V14.3 counter description: 1816/0, 1817/0, 1818/0, 1819/0,
1820/0.
Modified the name of the following counters: 1803/0, 1803/1, 1803/2, 1803/3,
1803/4,

xii Publication History Nortel Confidential
Checked the S12000 introduction impact on this NTP.

Taken into account:
CR Q00685162
CR Q00686958
CR Q00184739
CR Q00185002
CR Q00182988
April 2003
Taken into account:
internal comments
CR Q00548005 (correction, counters 15028/1 and 15030/1)
CR Q00566940 (correction, Annex of the document)
CR Q00581808 (counters 15005/0 and 15005/1)
CR Q00581804 (counters 15005/0 and 15005/1)
CR Q00614305 (counters 1606, 1607, 1608, 1701, 1609, 1611, 1613, 1700)
January 2003
Taken into account:
CR Q00411337
CR Q00548005
CR Q00500889
CR Q00470148
CR Q00431517
CR Q00431468
CR Q00389797
CR Q00252063
CR Q00252054
CR Q00208602
CR Q00583446
CR Q00582009
CR Q00566940

411--9001--125
Nortel Confidential Publication History xiii
December 2002

Update for V14.3 system release (BSS)
IPO counters in paragraph 1.5.4.1 have been removed
Mentions to instrument panel in paragraph 1.7.1 and 1.7.3 have been removed
ORT has been changed in IPO for the counter no. 9600 in paragraph A3.1
November 2002

Update for V14.3 system release (BSS)
The following features have been taken into account:
BSC e3 counters (22526)
AR 1209--6 BSC e3 observation counters (22673)
The following modifications have been made to the manual:
chapter 1 “Introduction”:
• The following counters have been added:
– all 19xx counters (refer to paragraph 1.5.2, 1.5.3 and 1.5.4.1--Raw
permanent counters settable by the operator (AMR),
Chapter 2 “Counters Description”:
• The following counters have been added:
– all 19xx counters (refer to paragraph 2.2.2--Raw permanent BSS counters
(AMR).
SYSTEM RELEASE: GSM/BSS V13
October 2002

The following modifications have been made to the manual
Added screenings to the counter 1104 (1104/0 and 1104/1)
Added screenings to the counter 1106 (1106/2 and 1104/3)

xiv Publication History Nortel Confidential
August 2002
Minor editorial update
The following modifications have been made to the manual:
Chapter 1 “Introduction”
• Modified the following PCUSN Data Flow Diagrams (paragraph 1.2.9):
– BVC flow control and MS flow control mechanisms
– Discard of LLC PDUs
– Establishment of an UL TBF in two phases access with first phase in
CCCH
– Establishment of an UL TBF during DL TBF
– Normal UL TBF release
– Abnormal release of an UL TBF due to non progression of V(Q)
– Abnormal release of an UL TBF due to non progression of V(Q) during full
duplex transfer in the case that the DL TBF is also released
– Non response from the mobile station after N3101 scheduled blocks
(means with USF set in downlink)
– Non response from the mobile station after N3101 scheduled blocks
(means with USF set in downlink) during full duplex transfer, in the case
that the DL TBF is also released
– Non response from the mobile after UP_NASSIGNMAX Packet Uplink
Assignment messages
– Non progression from the mobile after UP_NASSIGNMAX Packet
Uplink Assignment messages during full duplex transfer, in the case that
the DL TBF is also released
– Non response from the mobile after N3103 Packet Uplink Ack/Nack sent
with FAI=1
– Non response from the mobile after N3103 Packet Uplink Ack/Nack sent
with FAI=1 during full transfer, in the case that the DL TBF is also released
– Paging procedure initiated by the network for downlink packet transfer
towards a MS in standby state
– Downlink establishment towards a mobile in Ready State and Packet Idle
Mode
– Establishment with Packet Downlink Assignment and Packet Timeslot
Reconfigure

411--9001--125
Nortel Confidential Publication History xv
– Normal DL TBF Release

– Abnormal release of an DL TBF due to non progression of V(A)
– Abnormal release of an DL TBF due to non progression of V(A) during full
duplex transfer, in the case that the UL TBF is also released
– Non response from the mobile after N3105 downlink data with S/P=1
– Non response from the mobile after N3105 downlink data with S/P=1
during full duplex transfer, in the case that the UL TBF is also released
– Non response from the mobile after DN_NASSIGNMAX Packet
Downlink Assignment messages
– Non response from the mobile after DN_NASSIGNMAX Packet
Downlink Assignment messages during full duplex transfer, in the case
that the DL TBF is also released
– Non response from the mobile after NN0002 downlink data blocks sent
with FBI=1 and S/P=1
– Non response from the mobile after NN0002 downlink data blocks sent
with FBI=1 and S/P=1 during full duplex transfer, in the case that the UL
TBF is also released
– Preemption of radio timeslots
– Cell reselection from cell A to cell B and establishment of a new uplink
TBF in cell B
• Created new paragraph 1--6 “Raw Permanent PCUSN Observation Counters”
Chapter 2 “Counter Description”:
• The following counters have been modified:
– 1056 tchAveragedAvailableMoy/Max/Cum/Ech
– 1068 hoSuccessOutgoingInterBss
– 1078 hoSuccessOutgoingFirstInter
– 1700 tchAveragedAvailableTrZoneMoy/Max/Cum/Ech
– 15028/1 upMultiSlotRequest1
– 15030/1 dwMultiSlotRequest1

xvi Publication History Nortel Confidential
– 15031/1 FirstDlUnitDataFrame
– 15031/2 dlTBFAllocFailure
– 15031/3 dlTBFRadioFailure
– 15032/3 ulsecondPhaseAllocFailure
– 15034/0 PDANWithUlReq
– 15036/0 ulsecondPhaseRadioFailure
– 15041/0 upUserdatablocks
– 15043/0 RequestedRetransmittedDataBlocksDN
– 15058/4 dnPipebetween22and33kbps
– 15061/0 upPipeless11kbps
June 2002
March 2002
Changed to Standard - minor editorial update
August 2001
V13.1 release update after internal review
The following changes were made in individual chapters:

About this document
• updated Paragraph “Applicability”
• updated Paragraph “How this document is organized”
• updated Paragraph 1.1.1.1 “Observation types”
• removed Paragraph 1.4 “Instrument panel observation counters(V10)”
• removed Paragraph 1.5.2 “PCM links”
• removed Paragraph 1.5.3 “Handovers”
• updated Paragraph 1.6.2.1 “Raw permanent counters settable by the operator”

411--9001--125
Nortel Confidential Publication History xvii
• created new Paragraph 1.6.3 “Correspondence between BSC 2G and BSC e3

Counters”
• updated Paragraph 1.7.2.1 “Counter numbering”
• updated Paragraph 1.7.3 “Counter definition”
Chapter 2 “Counter description”
• removed Paragraph 2.2 “Raw instrument panel counters”
• removed Paragraph 2.4.3 “Temporary PCM observation”
• removed Paragraph 2.4.4 “Temporary Handover observation ”
• removed Paragraph 2.6 “Synthetic instrument panel (IPO and ORT)
counters”
• updated the Function and Event fields of the counters 15057/0 to 15057/4
• updated the Function and Event fields of the counters 15058/0 and 15058/1
• created the new counters 15075/0 to 15075/4, and 15076/0 to 15076/1
July 2001

• updated Paragraph 1.1.1.1 “Observation types” with completion of the V13
release column
• created Paragraph 1.2.2.3 “Abnormal Completions” with integration of the
following data flow diagrams (DFDs):
– no available resource (SDCCH)
– negative response from the BTS
– no response to CHANNEL ACTIVATE
– timer 3101 expiry
– incorrect first L3 message
– traffic with the MSC closed
– CONNECTION FAILURE indication
– ERROR INDICATION
– rejection from the MSC
• updated Paragraph 1.2.7.4 with integration of the counters 3000/n to 3008/n
• renamed Paragraph 1.6.1 “Raw counter configuration” by “Raw counter
configuration (BSC 2G)”

xviii Publication History Nortel Confidential
• created Paragraph 1.6.2 “Raw counter configuration (BSC e3)” with

integration of the counters 3000/n to 3008/n
• created Paragraph 2.3 “Raw permanent BSS counters (BSC e3) with
description of the following counters:
– 3000/n to 3008/n
Appendix A “V13 Release Counters”
• created Paragraph A.1 “V13 release counters”
• created Paragraph A.1.1 “New V13 counters” with integration of the counters
3000/n to 3008/n
System release: GSM/BSS V12
July 2001
• integrated the following data flow diagrams (DFDs):
– Immediate assignment: paging (normal completion), Paragraph 1.2.2.2
– Dedicated channel assignment: mode modify, Paragraph 1.2.3.2

– Intra-- bts handover (normal completion), Paragraph 1.2.4.3
– Inter--bss handover (normal completion), Paragraph 1.2.4.5
– Direct retry handover, Paragraph 1.2.4.6
– Radio channel release (DEACTIVATE SACCH ACK received before
RELEASE INDICATION), Paragraph 1.2.5.1
– Radio channel release (RELEASE INDICATION received before
DEACTIVATE SACCH ACK), Paragraph 1.2.5.1
– Connection clearing required by the BSC (normal completion),
Paragraph 1.2.5.2
– SMS service, Paragraph 1.2.6
• Answer to the Service Request:
– HB10400 (SR 30361193): renamed counter
“sccpResourceFailureBscFailure” by “sccpResourceFailureBscRefusal”

411--9001--125
Nortel Confidential Publication History xix
• updated Paragraph 2.8.2:

– removed all the fields (Q3 name, Object, Function, Event, etc.) of PCU
counters reserved for the manufacturer
– updated the Event field of the counter 15032/0
– renumbered the counter 15044 by 15044/0
– updated the Function and Event fields of the counter 15048/1
– changed the counter 15052 by 15052/0
– updated the Function field of counters 15054/0 to 15054/4
– changed the title of the counter 15058/0
– updated the Note field of the counter 15066/0
May 2001
• created Paragraph 1.3.3 “PDTCH resources”
• integrated the following data flow diagrams (DFDs):
– immediate assignment (normal completion), Paragraph 1.2.2.1
– queuing in the assignment procedure (successful completion),
Paragraph 1.2.2.3
– dedicated channel assignment (normal completion), Paragraph 1.2.3.1
– dedicated channel assignment (no resource available), Paragraph 1.2.3.3
– inter--cell intra--bss handover (normal completion with communication on
TRAFFIC phase), Paragraph 1.2.4.4
– connection clearing required by the MSC (normal completion),
Paragraph 1.2.5.2
– GPRS procedure (normal completion), Paragraph 1.2.7.1
– GPRS procedure (no resource available for PDTCH preemption),
Paragraph 1.2.7.2
– GPRS procedure (negative acknowledgement by the PCU after the BSC
attempted to preempt a PDTCH to make a TCH channel),
Paragraph 1.2.7.3
• updated existing “Dataflows” fields and created new ones

xx Publication History Nortel Confidential
April 2001
• created Paragraph 1.2.7 “GPRS” and added three data flow diagrams (DFDs):
– GPRS procedure (normal completion)
– GPRS procedure (no resource available for PDTCH preemption)
– GPRS procedure (negative acknowledgement by the PCU after a PDTCH
preemption)
– gave the list of the 193 counters impacted by the circuit/packet aspect
• created new DFDs:
– dedicated channel assignment (no resource available)
– queuing in the assignment procedure (normal completion)
• updated existing DFDs:
– immediate assignment (normal completion)
– dedicated channel assignment (normal completion)
– intercell handover (normal completion)
– connection clearing required by the MSC (normal completion)
• Answer to Service Requests:
– NK10370: corrected counter number for counters 15053/0
nbSamplesUpQuality and 15053/1 nbSamplesDnQuality
– NK10371: corrected counter number for counters 15058/2
dnTbfImmediateAssignment and 15058/1 upTbfImmAssigRejectNoPdch
– NK10231: updated definition of counter 1057
– EE10113: updated definition of counter 1057
– NK10245: added DFDs for the following counters: 1039, 1052, 1057,
1609, 1611, 1812, 1813, 1814, 1815
– NK10200: updated definition of counters 1812 and 1813
– SR 30349641 (master SR 30318353): updated definition of counter 1812
– HK10522: updated definition of counters 1609/0, 1609/2, 1611/0, 1611/2
– ER10013: updated definition of counter 1700
• updated the definition of all the counters concerned by TCH/FR and
preempted PDTCH
• updated the availability date of PCUSN counters (Paragraph 2.8)

411--9001--125
Nortel Confidential Publication History xxi
March 2001
• updated the description of the triggering event of C15029/1, C15029/2,
C15029/3, C15029/4, C15031/1, C15031/2, C15031/3, C15031/4
• updated the description of the function of C15039, C15040/0, C15042/0,
C15042/2, C15044
January 2001
– SR 30330395 (30430423): removed C15057/5 lossOfComNT1001
– SR EE00526 (30340254): added to
C9500 bscSdcchAveragedUsedMoy/Max/Ech/Cum and to
C9501 bscTchFrAveragedUsedMoy/Max/Ech/Cum, Paragraph 2.5
• completed the description of PCUSN counters, Paragraph 2.8
• added data flow diagrams to the description of counters C1812, C1813,
C1814, and C1815, Paragraph 2.1
September 2000
– EE00525 C1839/n and C1840/n location is not on bts object, but on
adjacentCellHandOver object
• completed the description of C1161/5, and C1629/0
• added three synthetic GSM--R specific counters: C8912, C8913, and C8919
June 2000

xxii Publication History Nortel Confidential

Updated 10 counters (1028, 1029, 1030, 1031, 1163/16, 1163/17, 1164/16,
1164/17, 1604, 1605)
Answer to Service Requests:
• HT90289: added counter 1730
• EE90235: added counters 8723, 8724, 8725, 8736
• 30092371: noted that counters 1766/0, 1766/1, 1767/0 and 1767/1 are V11
specific counters
• 30112359: updated counters 1803/0 to 1803/4
• 30114015: added counter 1841/1
• 30124292: counter 1106 became counter 1106/0 and counter 1106/1
• 30125561: added counter 1700 in ORT list
• 30127417: counters 1600 and 1603, 1623 and 1624, 1625 and 1626 created
for transceiverZone object
• 30127418: counters 1057 and 1060 are created for transceiverZone object
• 30135126: added counter 8040 (synthetic permanent)
March 2000
V12.4 release update
• added GPRS counters
• added counters related to feature TF995 “Automatic cell tiering”
January 2000
Creation:
Chapter 1 “Introduction” contains the former Chapter 4 “BSS observation
principles” which was removed from Manual < 07 >.
Chapter 2 “Counter description” contains the former Chapter 5 “Dictionary of
observation counters” which was removed from Manual < 07 >.

411--9001--125
Nortel Confidential Table of contents xxiii
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-- 1
2 Observation counter incrementation and DFDs . . . . . . . . . . . . . . 2--1

2.1 Radio resource allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--1
2.1.1 SDCCH allocation request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--1
2.1.2 TCH allocation request in primo-allocation . . . . . . . . . . . . . . . . . . . . . . . . 2--2
2.1.3 TCH allocation request for traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--3
2.2 Call setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--4
2.2.1 Immediate assignment procedure (normal completion) . . . . . . . . . . . . . 2--5
2.2.2 Immediate assignment procedure with OTDI (normal completion) . . . . 2--9
2.2.3 Paging procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--10
2.2.4 Immediate assignment procedure (failure cases) . . . . . . . . . . . . . . . . . . 2--13
2.3 Dedicated channel assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--38
2.3.1 Nominal procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--38
2.3.2 MODE MODIFY procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--45
2.3.3 No resource available and queuing not activated . . . . . . . . . . . . . . . . . . 2--47
2.3.4 Queuing procedure (successful completion) . . . . . . . . . . . . . . . . . . . . . . . 2--49
2.4 Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--56
2.4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--56
2.4.2 Accounting principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--58
2.4.3 Intra-bts handover procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--59
2.4.4 Inter cell intra--bss handover procedure (normal completion) . . . . . . . . 2--65
2.4.5 Inter-bss handover procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--72
2.4.6 Directed retry handover procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--80
2.5 Resource release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--82
2.5.1 Radio channel release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--82
2.5.2 Connection release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--89
2.6 SMS service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--103
2.7 GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--107
2.7.1 Nominal procedure (in the case of Mobile Originating Call) . . . . . . . . . . 2--107
2.7.2 GPRS procedure: no resource available for a PDTCH preemption . . . 2--116
2.7.3 GPRS procedure: negative acknowledgement by the PCU
for a PDTCH preemption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--119
2.7.4 Counter behavior when GPRS is activated . . . . . . . . . . . . . . . . . . . . . . . . 2--123
2.8 GPRS/EDGE Suspend and Resume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--133
2.8.1 GPRS/EDGE Suspend procedure with RAU message
(nominal procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--134

xxiv Table of contents Nortel Confidential
2.8.2 GPRS/EDGE Suspend procedure with RAU message (failure case) . . 2--136
2.8.3 GPRS/EDGE Suspend procedure with Resume message
(nominal procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--138
(failure case) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--139
2.9 BSC equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--142
2.9.1 CPUE overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--142
2.10 PCUSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--143
2.10.1 Flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--143
2.10.2 LLC Discarded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--144
2.10.3 UL TBF Establishment: Normal Completion . . . . . . . . . . . . . . . . . . . . . . . 2--146
2.10.4 UL TBF Establishment: UL TBF Establishment during DL transfer . . . 2--148
2.10.5 UL TBF Release: Normal Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--150
2.10.6 Abnormal OL TBF Release: lossOfComNN0002 . . . . . . . . . . . . . . . . . . . 2--152
2.10.7 Abnormal UL TBF Release (FULL Duplex): LossOfComNN0002 . . . . . 2--154
2.10.8 Abnormal UL TBF Release: N3101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--156
2.10.9 Abnormal UL TBF Release (FULL Duplex): N3101 . . . . . . . . . . . . . . . . . 2--158
2.10.10 Abnormal UL TBF Release: UP_NASSIGNMAX . . . . . . . . . . . . . . . . . . . 2--160
2.10.11 Abnormal UL TBF Release (FULL Duplex): UP_NASSIGNMAX . . . . . 2--163
2.10.12 Abnormal UL TBF Release: N3103 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--166
2.10.13 Abnormal UL TBF Release (FULL Duplex): N3103 . . . . . . . . . . . . . . . . . 2--168
2.10.14 DL TBF Establishment: MS in Standby State . . . . . . . . . . . . . . . . . . . . . . 2--170
2.10.15 DL TBF Establishment: MS in Ready State . . . . . . . . . . . . . . . . . . . . . . . 2--173
2.10.16 DL TBF Establishment during UL transfer . . . . . . . . . . . . . . . . . . . . . . . . 2--175
2.10.17 DL TBF Release: Normal Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--176
2.10.18 Abnormal DL TBF Release: lossOfComNN0002 . . . . . . . . . . . . . . . . . . . 2--178
2.10.19 Abnormal DL TBF Release (FULL Duplex): lossOfComNN0002 . . . . . 2--180
2.10.20 Abnormal DL TBF Release: N3105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--183
2.10.21 Abnormal DL TBF Release (FULL Duplex): N3105 . . . . . . . . . . . . . . . . . 2--185
2.10.22 Abnormal DL TBF Release: DN_NASSIGNMAX . . . . . . . . . . . . . . . . . . . 2--188
2.10.23 Abnormal DL TBF Release (FULL Duplex): DN_NASSIGNMAX . . . . . 2--190
2.10.24 Abnormal DL TBF Release: No final PDAN . . . . . . . . . . . . . . . . . . . . . . . 2--193
2.10.25 Abnormal DL TBF Release (FULL Duplex): No final PDAN . . . . . . . . . . 2--195
2.10.26 Preemption of radio timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--198
2.10.27 Cell update: Packet Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--200
2.11 Advanced Speech Call Items (ASCI) (GSM--R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--203
3 BSS Observation management principles . . . . . . . . . . . . . . . . . . . . 3--1

3.1 Observation types (OGS, OFS, ORT, ODIAG, temporary) . . . . . . . . . . . . . . . . . . . . 3--1
3.2 Observation management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--2
3.2.1 Observed entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--2

411--9001--125
Nortel Confidential Table of contents xxv
3.2.2 Observation domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--2

3.2.3 Observations and alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--2
3.3 Observation counter types (totalizer, value, load) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--3
3.3.1 Cumulative counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--3
3.3.2 Value counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--4
3.3.3 Load counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--5
3.4 Customized counter names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--6
3.5 Maximum number of counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--6
3.5.1 Number of counter Ids per observation type . . . . . . . . . . . . . . . . . . . . . . . 3--6
3.5.2 Use of BSC memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--7
3.5.3 DRAM limitation on BSC 12000HC V15 . . . . . . . . . . . . . . . . . . . . . . . . . . 3--7
3.6 Observation classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--11
3.7 Mobility Class Sensitivity Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--11
4 Type and class of counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--1

4.1 Permanent bsc observation counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--1
4.1.1 Abis Level 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--2
4.1.2 Abis Level 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--8
4.1.3 A interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--8
4.1.4 AMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--9
4.1.5 AMR on TrZone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--12
4.1.6 ASCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--15
4.1.7 BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--17
4.1.8 BSC 3G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--18
4.1.9 BSC -- Load of processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--20
4.1.10 CCCH Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--23
4.1.11 Channel mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--25
4.1.12 Dedicated channel assignement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--26
4.1.13 Directed retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--27
4.1.14 EDGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--27
4.1.15 Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--28
4.1.16 Global handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--29
4.1.17 GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--31
4.1.18 GPRS on TrZone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--32
4.1.19 Inter--bss handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--34
4.1.20 Interferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--35

xxvi Table of contents Nortel Confidential
4.1.21 Intra--bss handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--36

4.1.22 Intra--cell handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--38
4.1.23 Layer One Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--38
4.1.24 Layer One Management on TrZone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--39
4.1.25 Neighbor cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--40
4.1.26 OMC interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--41
4.1.27 PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--42
4.1.28 Releases of communications in signalling phase . . . . . . . . . . . . . . . . . . . 4--42
4.1.29 Releases of communications in traffic phase . . . . . . . . . . . . . . . . . . . . . . 4--43
4.1.30 SDCCH allocations on TrZone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--44
4.1.31 SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--45
4.1.32 TCH allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--46
4.1.33 TCH allocations on TrZone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--48
4.1.34 WPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--50
4.2 Raw permanent BSS counters configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--53
4.2.1 Raw counters configuration (all BSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--53
4.2.2 Correspondence between BSC 12000HC and BSC 3000 counters . . . 4--82
4.3 Synthetic permanent BSS counters configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--84
4.4 Temporary observation counters (BSC 12000HC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--88
4.4.1 Temporary Abis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--88
4.4.2 Temporary interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--89
4.4.3 Temporary SS7 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--89
4.5 Manager counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--90
4.5.1 Manager cpu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--90
4.5.2 Manager database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--90
4.5.3 Manager disk usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--90
4.5.4 Manager X25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--92
4.6 Md counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--93
4.6.1 FMD--R disk usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--93
4.6.2 FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--95
4.6.3 MD--R activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--95
4.6.4 MD--R cpu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--96
4.6.5 MD--R database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--97
4.6.6 MD--R X25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--97
4.7 Raw Permanent PCUSN Observation Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--98
4.7.1 PCUSN Observation Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--98

411--9001--125
Nortel Confidential Table of contents xxvii
4.7.2 PCUSN Observation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--100

4.7.3 PCUSN counter families . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--107
4.7.4 Throughput Counters and Satisfaction Rate Counters . . . . . . . . . . . . . . 4--116
5 Counter description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-- 1

5.1 Dictionary presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--1
5.1.1 Dictionary contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--1
5.1.2 Observation counter references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--1
5.1.3 Counter definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--2
5.1.4 Basic definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--4
5.2 Raw permanent BSS counters (BSC 12000HC) (from 1084 to 1835) . . . . . . . . . . 5--7
5.3 Raw permanent BSS counters (BSC 3000, AMR) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--29
5.3.1 Raw permanent BSS counters (BSC 3000) (from 1065/1 to 3008/3) . . 5--29
5.3.2 Raw permanent BSS counters (AMR) (from 1197/2 to 1988/0) . . . . . . . 5--54
5.4 Raw permanent BSS counters (common to BSC 12000HC, BSC 3000, and AMR) (from 1026 to
2068/1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--103
5.5 Raw temporary counters (ODIAG excluded) (from 5000 to 5610) . . . . . . . . . . . . . . 5--461
5.5.1 Temporary Interference observation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--461
5.5.2 Temporary SS7 link observation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--461
5.5.3 Temporary Abis interface observation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--464
5.6 Synthetic permanent BSS counters (from 8000 to 9600) . . . . . . . . . . . . . . . . . . . . . 5--473
5.6.1 Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--473
5.6.2 Synthetic permanent BSS counters by counter number . . . . . . . . . . . . . 5--473
5.6.3 Other synthetic permanent BSS counters . . . . . . . . . . . . . . . . . . . . . . . . . 5--533
5.6.4 Synthetic permanent PCU counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--541
5.7 Raw permanent md counters (from 9940 to 10050) . . . . . . . . . . . . . . . . . . . . . . . . . . 5--544
5.7.1 SYBASE counters (from 9940 to 10050) . . . . . . . . . . . . . . . . . . . . . . . . . . 5--544
5.7.2 SCSE counters (from 9970 to 9974) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--548
5.7.3 UNIX counters (from 9984 to 10046) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--549
5.7.4 Q3 counters (from 10000 to 10038) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--554
5.8 Raw permanent manager counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--567
5.8.1 SYBASE counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--567
5.8.2 X.25 counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--571
5.8.3 UNIX counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5--572
5.9 Raw permanent PCUSN counters (from 15001 to 15195) . . . . . . . . . . . . . . . . . . . . 5--576
Appendix A V15 Release counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--1

xxviii Table of contents Nortel Confidential
A.1 Delta between V15.1 and V15.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--2

A.2 Delta between V15.1R and V15.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--2
A.2.1 BSS counters added since V15.1R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--2
A.2.2 BSS counters removed since V15.1R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--3
A.3 Delta between V15.0 and V15.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--6
A.3.1 PCUSN counters added since V15.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--6
A.3.2 BSS counters added since V15.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--12
A.3.3 BSS counters removed since V15.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--14
A.4 Delta between V15.0.1 and V15.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--17
A.4.1 BSS counters added since V15.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--17
A.4.2 BSS counters removed since V15.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--19

411--9001--125
Nortel Confidential List of figures xxix
Figure 1--1 Guidelines for locating a BSS observation counter . . . . . . . . . . . . . . . . . . . . . . 1--1

Figure 4--1 Observation Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--99

xxx List of tables Nortel Confidential
Table 3--1 BSC memory threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--6

Table 3--2 Toggling counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--21

411--9001--125
Nortel Confidential About this document 0--1
ABOUT THIS DOCUMENT

This Observation Counter Dictionary is a reference guide describing all GSM BSS
network observation counters managed through the OMC--R.
Applicability
This document applies to the V15.1.1 system release.
This document is part of the BSS Nortel Networks Technical Publications (NTPs).
It is closely associated with the following manuals:
The BSS Operating Principles manual (NTP < 07 >) describes general operating
principles and explains the mechanisms that enable Man-Machine interface
commands.
The BSS Parameter Dictionary (NTP < 124 >) contains all the parameters used
in OMC--R commands.
The OMC--R User Manual (NTPs < 128 >, < 129 > and < 130 >) is a
user-oriented guide to performing Human-Machine interface commands.
The BSS Operating Procedures Manual (NTP < 34 >) describes various
procedures that help users operate or reconfigure a BSS.
Precautionary message
The following message:
CAUTION
GSM--R specific
Indicates that specific equipment and specific software (such as
specific software in the BSC) dedicated to Railway application is
used and that the feature is therefore not available for all standard
GSM users.
Some GSM--R specific counters listed in this dictionary contain “(GSM--R V12)”
in the “Feature” field because they were introduced in V12.
Audience
This document is intended for:
OMC--R administrators
OMC--R maintenance attendants
GSM network engineers
users who want to know more about OMC--R

0--2 About this document Nortel Confidential
Prerequisites
Users must be familiar with networking principles.
They must also be familiar with the following manuals :
< 00 > : BSS Product Documentation Overview
< 01 > : BSS Overview
< 06 > : OMC--R Architecture and Reference Manual
< 07 > : BSS Operating Principles
< 32 > : OMC--R Preventive and Corrective Maintenance Manual
< 34 > : BSS Operating procedures
< 124 > : BSS Parameter Dictionary
< 128 > : OMC--R User Manual -- Volume 1 of 3: Object and Fault menus
< 129 > : OMC--R User Manual - Volume 2 of 3: Configuration, Performance,
and Maintenance menus
< 130 > : OMC--R User Manual - Volume 3 of 3: Security, Administration,
SMS--CB, and Help menus
How this document is organized

This document is organized into three main chapters:
Chapter 1 “Introduction” contains general information on observation counters.
Chapter 2 “Observation counter incrementation principles and data flow
diagrams (DFD) explains the precise incrementation conditions of many
counters.
Chapter 5 “Counter description” describes all the observation counters listed by
families, and explains their use.
Appendix A “V15 release counters” contains new, modified and deleted V15
release observation counters.
Vocabulary conventions
The glossary is presented in Manual < 00 >.

411--9001--125
Nortel Confidential Introduction 1--1
1 INTRODUCTION
Figure 1--1 provides the user with guidelines for locating a BSS observation counter
in the dictionary of counters, starting from different points.
Starting point
The type and class of The number of the

the counter are known counter is known
(for example: (for example: 1055)
permanent/handover)
The Q3 name of the
counter is known
(for example: assign-
Failure)
See the index of

See Chapter 4
counters at the end
of the manual
Search for the counter in the Dictionary of counters

(numerical lists in Chapter 5)
Figure 1--1 Guidelines for locating a BSS observation counter

1--2 Introduction Nortel Confidential
PAGE INTENTIONALLY LEFT BLANK

411--9001--125
Nortel Confidential Observation counter incrementation and DFD 2--1
2 OBSERVATION COUNTER INCREMENTATION AND

DFD
This chapter describes the principles of Observation counter incrementation and
Data Flow Diagrams (DFDs).
2.1 Radio resource allocation
2.1.1 SDCCH allocation request
SDCCH allocation request
sdcchAllocated
SDCCH resource Yes
sdcchAveragedUsed
available allSdcchAllocatedTime (possibly)
No
No handover in--progress tchFrAllocated (cause = Overflow)

Yes
and TCH resource tchFrAveragedUsed (cause = Overflow)
available allTchFrAllocatedTime (possibly)
No
sdcchRessourceFailure

2--2 Observation counter incrementation and DFD Nortel Confidential
2.1.2 TCH allocation request in primo-allocation
TCH allocation request in primo--allocation
tchFrAllocated (cause = Primo--allocation)

TCH resource Yes
tchFrAveragedUsed (cause = Primo--allocation)
available
allTchFrAllocatedTime (possibly)
No
SDCCH resource sdcchAllocated

Yes
available sdcchAveragedUsed
allSdcchAllocatedTime (possibly)
No
tchFrRessourceFailure

411--9001--125
2.1.3 TCH allocation request for traffic
Attempt of allocation
of a TCH
TCH resource Yes tchFr/HrAllocated (cause = TCH channel)

available tchFr/HrAveragedUsed (cause = TCH channel)
No
Request can be queued Yes

tchAverageQueueLength (cause highest priority or internal
priority)
No
Each time a queueing
request is served
tchFr/HrAllocated (cause = TCH
tchFr/HrResourceFailure (set from a queue channel)
to the TCH pool) tchFr/HrAveragedUsed (cause =
TCH channel)
tchAverageQueueLength (cause =
highest priority or internal priority)
tchQueueingDuration
tchQueueingExpiration (cause =
highest priority or internal priority)
Each time a queueing tchAverageQueueLength (cause =
request is extracted highest priority or internal priority)
from a queue on timer tchQueueingDuration
expiration

2.2 Call setup

Call setup is initiated by the mobiles (Mobile Originating Call setup) or the MSC
(Mobile Terminating Call setup).
In the second case, a paging procedure precedes the immediate assignment
procedure.

411--9001--125
2.2.1 Immediate assignment procedure (normal completion)

Data Flow Diagram: immediate assignment procedure (normal completion)
MS BTS BSC MSC

CHANNEL_REQUEST CHANNEL_REQUIRED
1748
1702
1191/n (1)
1730 (1)
1606
1607
1744 (2)
1746 (2)
1609/2 (2)
1611/2 (2)
CHANNEL_ACTIVATE
Set timer TchnAck
1629/0
CHANNEL_ACTIVATE_ACK
IMMEDIATE_ASSIGNMENT Reset timer TchnAck

_COMMAND
IMMEDIATE_ASSIGNMENT Set timer T3101
1749
SABM(CM_SERVICE REQUEST) 1192/n
ESTABLISH_INDICATION Reset timer T3101
1750
CONNECTION_REQUEST
1193/n
(L3_INFORMATION
1195 or 1196
CM_SERVICE_REQUEST)
1108
1502
CONNECTION_CONFIRM
1105
START_MEASUREMENT_REQUEST 1104/0
START_MEASUREMENT_REQ_ACK
DTAP (CM_SERVICE_ACCEPT)
1107
DTAP (CM_SERVICE_ACCEPT) 1501
CM_SERVICE_ACCEPT
ALERTING
DTAP (ALERTING)
DTAP (ALERTING)
1108
1500

(1) The following counters are incremented depending on the cause value in the
CHANNEL REQUIRED message:
1191 cause 000
1191/1 and 1730 for cause 001
1191/2 for cause 010
1191/4 and 1730 for cause 100
(2) If no SDCCH is available, the BSC may try to allocate a TCH in signaling mode.
In this case, the following counters are incremented: 1744, 1746, 1609/2, 1611/2
List of the counters incremented during this procedure:
Counter Counter name Function

number
1104/0 sccpAllocated number of SCCP connections for

SSN BSSMAP in the BSC
1105 sccpAveragedUsedMoy/Max/ average number of SCCP

Cum/Ech connections established
1107 aInputMessage number of BSSAP messages

received by the BSC
1108 aOutputMessage number of BSSAP messages sent by

the BSC
1191/n channelRequestCauseXxx number of channel allocation

[n= 0 to 7] requests: Cause xxx
1192/n immediateAssignmentSuccess number of successful immediate

[n= 0 to 7] CauseXxx assignments: Cause xxx
1193/n estabIndicSignallingCauseXxx number of ESTABLISH INDICATION

[n= 0 to 3] messages in establishment phase
received for mobile originating calls:
Cause Xxx
1195 estabIndicSigPhaseI number of ESTABLISH INDICATION

messages in establishment phase
received for Phase I mobiles
1196 estabIndicSigPhaseII number of ESTABLISH INDICATION

received for Phase II mobiles

411--9001--125

number
1500 aTransparentUp number of DTAP messages sent by

the BSC to the MSC
1501 aTransparentDown number of DTAP messages received
1502 aNonTransparentUp number of BSSMAP messages sent

by the BSC
1606 sdcchAllocatedTrZone number of SDCCH allocated in the

zone (concentric cell)
1607 sdcchAveragedUsedTrZoneMoy/ average number of SDCCHs used in

Max/Cum/Ech the inner or outer zone of the cell
1609/2 tchFrAllocatedOverflowAllocati number of TCH/FR allocated in the

onTrZone inner or outer zone of the cell
because of SDCCH unavailability
1611/2 tchFrAveragedUsedOverflowAlloc average and maximum number of

ationTrZone TCH/FR used in the inner or outer
Moy/Max/Cum/Ech zone of the cell because of SDCCH
unavailability
1629/0 channelActivateSignallingFull number of Full Rate channels

Rate activated for signaling
1702 channelRequestExtended number of receipt of CHANNEL

REQUIRED message with a timing
advance greater than 63
1730 pagingResponse number of responses to paging

requests in the cell
1744 tchFrAllocated number of TCH/FR or preempted

PDTCH allocated in the cell
or
or number of TCH/FR or preempted
tchFrAllocatedTrZone PDTCH allocated in the inner
or outer zone of the concentric cell
1746 tchFrAveragedUsedMoy/Max/ average number of TCH/FR or

Cum/Ech preempted PDTCH used in the cell
or or
tchFrAveragedUsedTrZoneMoy/M average number of TCH/FR or
ax/Cum/Ech preempted PDTCH used in the inner
or outer zone of the cell
1748 channelRequest number of channel allocation

requests


number
1749 immediateAssignmentSuccess number of successful immediate

assignments
1750 estabIndicSignalling number of ESTABLISH INDICATION

received

411--9001--125
2.2.2 Immediate assignment procedure with OTDI (normal completion)
This procedure used to establish group calls (VCS or VGCS) includes Originator
To Dispatcher Information (OTDI) in the setup message.
MS BTS BSC MSC

CHANNEL_REQUEST CHANNEL_REQUIRED
1748
1702
1191/n (1)
1730 (1)
1606
1607
1744 (2)
1746 (2)
1609/2 (2)
1611/2 (2)
CHANNEL_ACTIVATE
Set timer TchnAck
1629/0
IMMEDIATE_ASSIGNMENT Reset timer TchnAck

_COMMAND
IMMEDIATE_ASSIGNMENT Set timer T3101
1749
SABM(immediate_setup2(call ID, 1192/n
OTDI)) est_ind(immediate_setup2(call Id, Reset timer T3101
OTDI))
1750
CONNECTION_REQUEST
1193/n (immediate_setup2, call Id,
1195 or 1196 OTDI)
1108
1502
1722 CONNECTION_CONFIRM
1105
START_MEASUREMENT_REQUEST 1104/0
1107
DTAP (CM_SERVICE_ACCEPT) 1501
CM_SERVICE_ACCEPT
ALERTING
DTAP (ALERTING)
DTAP (ALERTING)
1108
1500

2.2.3 Paging procedure
Data Flow Diagram: immediate assignment: paging procedure (normal

completion)
MS BTS BSC MSC

PAGING_REQUEST
PAGING_COMMAND 1107
PAGING_COMMAND 1503
CHANNEL_REQUIRED
CHANNEL_REQUIRED
1748
1702
1191/n (1)
1730 (1)
1606
1607
1744 (2)
1746 (2)
1609/2 (2)
1611/2 (2)
CHANNEL_ACTIVATE
Set timer TchnAck
1629/0
Reset timer TchnAck
IMMEDIATE_ASSIGNMENT_COMMAND
IMMEDIAT_ASSIGNMENT Set timer T3101
1749
SABM (PAGING_RESPONSE) 1192/n
ESTABLISH_INDICATION
Reset timer T3101
1750
1193/n CONNECTION_REQUEST
1195 or 1196 (PAGING_RESPONSE)
1108
1502 CONNECTION_CONFIRM
1105
START_MEASUREMENT_REQUEST 1104
DTAP (SETUP)
1107
DTAP (SETUP)
SETUP 1501
ALERTING
DTAP (ALARTING)
DTAP (ALARTING)
1108
1500

411--9001--125
1191/1 and 1730 for cause 001
1191/4 and 1730 for cause 100
In this case, the following counters are incremented:
1744, 1746, 1609/2, 1611/2

number
1105 sccpAveragedUsedMoy/Max/C average number of SCCP
um/Ech connections established
received by the BSC
the BSC
Cause Xxx
the BSC to the MSC


number
by the BSC
1503 aNonTransparentDown number of BSSMAP messages
received by the BSC from the MSC
1607 sdcchAveragedUsedTrZoneMoy average number of SDCCHs used in
/Max/Cum/Ech the inner or outer zone of the cell
1611/2 TchFrAveragedUsedOverflowAll average and maximum number of
ocationTrZone TCH/FR used in the inner or outer
unavailability
1744 tchFrAllocated number of TCH/Fr or preempted
or or
tchFrAllocatedTrZone number of TCH/FR or preempted
PDTCH allocated in the inner or outer
zone of the concentric cell
or or
tchFrAveragedUsedTrZoneMoy/ average number of TCH/FR or
Max/Cum/Ech preempted PDTCH used in the inner
requests
assignments
received

411--9001--125
2.2.4 Immediate assignment procedure (failure cases)
2.2.4.1 No resource available (SDCCH)
MS BTS BSC MSC

CHANNEL_REQUEST
CHANNEL_REQUIRED
1748
1191/0
1608
1751
1611/1 (1)
(IMMEDIATE_ASSIGNMENT_REJECT)
IMMEDIATE_ASSIGNMENT_REJECT

number
1161/1 immediateAssignmentRejectRad number of immediate assignments
ioRes rejected for lack of radio resources
1191/0 channelRequestCause000 number of channel allocation
requests: Cause 000
1608 sdcchResourceFailureTrZone number of SDCCH allocation failures
due to lack of SDCCH in the inner and
outer zone of the cell
1748 channelRequest number of channel allocation requests
1751 immediateAssignmentReject number of immediate assignments
rejected

2.2.4.2 Negative reponse from the BTS

Data Flow Diagram: immediate assignment failure procedure: negative response
from BTS
MS BTS BSC MSC

CHANNEL_REQUEST
CHANNEL_REQUIRED
1748
1702
1191/n (1)
1730 (1)
1606
1607
1744 (2)
1746 (2)
1609/2 (2)
CHANNEL_ACTIVATE 1611/2 (2)
Set timer T3101 Set timer TchnAck
1629/0
ACTIVATE_NEGATIVE_ACK
DEACTIVATE_SACCH
Reset timer T3101 Reset timer TchnAck
1606
1607
DEACTIVATE_ACK
1751
1161/2
1191/1 and 1730 for cause 001
1191/4 and 1730 for cause 100
1744, 1746, 1609/2, 1611/2

411--9001--125

number
1161/2 immediateAssignmentReject number of immediate assignments
ChanActNack rejected because a CHANNEL
ACTIVATE NACK message is received
1191/n channelRequestCauseXxx number of channel allocation requests:
[n= 0 to 7] Cause xxx
1606 sdcchAllocatedTrZone number of SDCCH allocation in the
inner and outer zone of the cell
1607 sdcchAverageUsedTrZoneM average and maximum number of
oy/Max/Cum/Ech SDCCHs used in the inner or outer
zone of the cell
1609/2 tchFrAllocatedOverflowAllo number of TCH/FR allocated in the
cationTrZone inner or outer zone of the cell because
of SDCCH unavailability
1611/2 tchFrAveragedUsedOverflowAl average and maximum number of
locationTrZone TCH/FR used in the inner or outer zone
Moy/Max/Cum/Ech of the cell because of SDCCH
unavailability, obtained through internal
sampling
1629/0 channelActivateSignallingF number of Full Rate channels (SDCCH
ullRate or TCH/FR) activated for signaling in
the cell
1744 tchFrAllocated number of TCH/FR allocated in the cell
or
or number of TCH/FR allocated in the
tchFrAllocatedTrZone inner or outer zone of the concentric cell
1746 tchFrAveragedUsedMoy/Ma average number of TCH/FR used in the
x/Cum/Ech inner or outer zone of the concentric cell
rejected

2.2.4.3 No response to CHANNEL ACTIVATE
Data Flow Diagram: immediate assignment failure procedure: no response to

CHANNEL ACTIVATE
MS BTS BSC MSC

CHANNEL_REQUEST
CHANNEL_REQUIRED
1748
1702
1191/n (1)
1730 (1)
1606
1607
1744 (2)
1746 (2)
1609/2 (2)
1611/2 (2)
CHANNEL_ACTIVATE
Set timer TchnAck
Set timer T3101
1629/0
1607
1751
Reset timer TchnAck
Reset timer T3101 1161/3
1191/1 and 1730 for cause 001
1191/4 and 1730 for cause 100
1744, 1746, 1609/2, 1611/2

411--9001--125

number
ChanActTimmack rejected because of TimmAck
time--out elapse
1607 sdcchAverageUsedTrZoneM average and maximum number of
zone of the cell
1609/2 tchFrAllocatedOverflowAlloc number of TCH/FR allocated in the
ationTrZone inner or outer zone of the cell
1611/2 tchFrAveragedUsedOverflowAll average and maximum number of
unavailability, obtained through
internal sampling
1629/0 channelActivateSignallingFul number of Full Rate channels
lRate activated for signaling
1744 tchFrAllocated number of TCH/FR allocated in the
cell
or or
tchFrAllocatedTrZone number of TCH/FR allocated in the
inner or outer zone of the concentric
cell
1746 tchFrAveragedUsedMoy/Ma average number of TCH/FR used in
x/Cum/Ech the inner or outer zone of the
concentric cell
rejected

2.2.4.4 Incorrect first L3 message

Data Flow Diagram: immediate assignment failure procedure: timer T3101 expiry
MS BTS BSC MSC

CHANNEL_REQUEST
CHANNEL_REQUIRED
1748
1702
1191/n (1)
1730 (1)
1606
1607
1744 (2)
1746 (2)
1609/2 (2)
1611/2 (2)
CHANNEL_ACTIVATE
Set timer T3101 Set timer TchnAck
1629/0
(IMMEDIATE_ASSIGNMENT)
Reset timer TchnAck
Timer T3101 expired
1749
IMMEDIATE_ASSIGNMENT 1192/n
RF_CHANNEL_RELEASE
Set timer TrfAck
RF_CHANNEL_RELEASE_ACK
Reset timer TrfAck
1607 (--1)
1191/1 and 1730 for cause 001
1191/4 and 1730 for cause 100
1744, 1746, 1609/2, 1611/2

411--9001--125

number
1161/3 immediateAssignmentRejectCh number of immediate assignments
anActTimmack rejected because of TimmAck
time--out elapse
1191/n channelRequestCausexxx number of channel allocation
1192/n immediateAssignmentSuccess number of immediate assignments
[n= 0 to 7] Causexxx with cause xxx satisfied
1607 sdcchAverageUsedTrZoneMoy/ average and maximum number of
Max/Cum/Ech SDCCHs used in the inner or outer
zone of the cell
1611/2 tchFrAveragedUsedOverflowAll average and maximum number of
internal sampling
cell
or or
cell
1746 tchFrAveragedUsedMoy/Max/ average number of TCH/FR used in
Cum/Ech the inner or outer zone of the
concentric cell
requests
1749 immediateAssignmentSuccess number of immediate assignments
satisfied

2.2.4.5 Timer 3101 expiry
Data Flow Diagram: immediate assignment failure procedure: incorrect first L3

message
MS BTS BSC MSC

CHANNEL_REQUEST
CHANNEL_REQUIRED
1748
1702
1191/n (1)
1730 (1)
1606
1607
1744 (2)
1746 (2)
1609/2 (2)
1611/2 (2)
Set timer TchnAck CHANNEL_ACTIVATE
Set timer T3101
1629/0
Reset timer TchnAck
1749
IMMEDIATE_ASSIGNMENT 1192/n
SABM
CHANNEL_RELEASE
Reset timer T3101
CHANNEL_RELEASE
DEACTIVATE_SACCH
Set timer TdeacAck
1753 Reset timer TdeacAck

1778 Set timer T3109
DISC 1163/4 Reset timer T3109

DEACTIVATE_ACK
UA Set timer T3111
RELEASE_INDICATION
Timer T3111 expires
RF_CHANNEL_RELEASE
Set timer TrfAck
Reset timer TrfAck
1607 (--1)

411--9001--125
(1) The following counters are incremented or decremented depending on the cause
value in the CHANNEL REQUIRED message:
1191/1 and 1730 for cause 001
1191/4 and 1730 for cause 100
1744, 1746, 1609/2, 1611/2
List of the counters incremented or decremented during this procedure:

number
1163/4 signallingReleaseBtsIncFirstL3 number of communications in
signaling phase release because of
incorrect First L3 message when a
cell is associated with the
communication
1191/n channelRequestCausexxx number of channel allocation
1192/n immediateAssignmentSuccess number of immediate assignments
[n= 0 to 7] Causexxx with cause xxx satisfied
1607 sdcchAverageUsedTrZoneMoy/ average and maximum number of
Max/Cum/Ech SDCCHs used in the inner or outer
zone of the cell
1609/2 tchFrAllocatedOverflowAllocatio number of TCH/FR allocated in the
nTrZone inner or outer zone of the cell
1611/2 tchFrAveragedUsedOverflowAllo average and maximum number of
cationTrZone TCH/FR used in the inner or outer
internal sampling
1629/0 channelActivateSignallingFullRate number of Full Rate channels
activated for signaling


number
cell
or or
cell
1746 tchFrAveragedUsedMoy/Max/C average number of TCH/FR used in
um/Ech the inner or outer zone of the
concentric cell
requests
1749 immediateAssignmentSuccess number of immediate assignments
satisfied
1753 signallingReleaseBts number of releases while the
communication is in “signaling
phase” and a cell associated to the
communication
1778 signallingAbnormalReleaseCell number of abnormal releases while
the communication is in “signaling
communication

411--9001--125
2.2.4.6 Traffic with the MSC close
Data Flow Diagram: immediate assignment failure procedure: traffic with the MSC
closed
MS BTS BSC MSC

CHANNEL_REQUEST
CHANNEL_REQUIRED
1748
1191/0
1751
1611/0 (1)

number
TraffMsc rejected because the traffic with the
MSC is interrupted
1191/0 channelRequestCause000 number of channel allocation
requests: Cause 000
1608 sdcchResourceFailureTrZon number of SDCCH allocation failures
e due to lack of SDCCH in the inner and
rejected

2.2.4.7 CONNECTION FAILURE indication
Data Flow Diagram: immediate assignment failure procedure: connection failure

indication
MS BTS BSC MSC

CHANNEL_REQUEST
CHANNEL_REQUIRED
1748
1702
1191/n (1)
1730 (1)
1606
1607
1744 (2)
1746 (2)
1609/2 (2)
1611/2
CHANNEL_ACTIVATE (2)
Set timer T3101
Set timer TchnAck
1629/0
Reset timer TchnAck IMMEDIATE_ASSIGNMENT_COMMAND

IMMEDIATE_ASSIGNMENT
1749
SABM 1192/n
(CM_SERVICE_REQUEST) ESTABLISH_INDICATION
(CM_SERVICE_REQUEST)
Reset timer T3101
1750
CONNECTION_REQUEST
1193/n
(L3_INFORMATION
1195 or 1196
CM_SERVICE_REQUEST)
1108
1502
START_MEASUREMENT_REQUEST
Set timer TchnAck
CONNECTION_CONFIRM
1105
Reset timer Tmea CONNECTION_FAILURE 1104
DEACTIVATE_SACCH
1753
1778
1044
1045
STOP_MEASUREMENT_REQUEST
CLEAR_REQUEST
1108
1502
DEACTIVATE_ACK
Set timer TdeacAck
STOP_MEASUREMENT_ACK

411--9001--125
MS BTS BSC MSC
Reset timer TdeacAck CLEAR_COMMAND
Set timer T3109 1107

1503
CLEAR_COMPLETE
Timer T3109 expires
1108
1502
RF_CHANNEL_RELEASE
Set timer TrfAck
RF_CHANNEL_RELEASE_ACK Reset timer TrfAck
1607 (--1) DISCONNECTED_INDICATION

1105 (--1)
1191/1 and 1730 for cause 001
1191/4 and 1730 for cause 100
1744, 1746, 1609/2, 1611/2


number
1044 signallingPhaseDurationMoy/M average and maximum seizure of
ax/Cum/Ech signaling channels expressed in
milliseconds, calculated on all
allocations lasting more than 25
milliseconds
1045 signallingPhaseDurationHighM average and maximum seizure of
oy/Max/Cum/Ech signaling channels expressed in
allocations in the cell
received by the BSC
1108 aOutputMessage number of BSSAP messages sent
by the BSC
Cause Xxx
by the BSC
1503 aNonTransparentDown number of BSSMAP messages sent
by the MSC

411--9001--125

number
1611/2 tchFrAveragedUsedOverflowAllocati average and maximum number of
onTrZoneMoy/Max/Cum/Ech TCH/FR used in the inner or outer
zone of the cell because of SDCCH
unavailability
1629/0 channelActivateSignallingFullR number of Full Rate channels
ate activated for signaling
or
or number of TCH/FR or preempted
tchFrAllocatedTrZone PDTCH allocated in the inner or
outer zone of the concentric cell
or
average number of TCH/FR or
preempted PDTCH used in the inner
or or outer zone of the cell
tchFrAveragedUsedTrZoneMoy/
Max/Cum/Ech
1748 ChannelRequest number of channel allocation
requests
1749 ImmediateAssignmentSuccess number of successful immediate
assignments
1750 EstabIndicSignalling number of ESTABLISH INDICATION
received
communication
the communication is in “signaling
communication

2.2.4.8 ERROR indication (connection failure)
MS BTS BSC MSC

CHANNEL_REQUEST
CHANNEL_REQUIRED
1748
1702
1191/n (1)
1730 (1)
1606
1607
1744 (2)
1746 (2)
1609/2 (2)
1611/2 (2)
CHANNEL_ACTIVATE
Set timer TchnAck Set timer T3101
1629/0
Reset timer TchnAck (IMMEDIATE_ASSIGNMENT)
1749
SABM 1192/n
Reset timer T3101
1750
1195 or 1196 (L3_INFORMATION
CM_SERVICE_REQUEST)
1108
1502
Set timer Tmea START_MEASUREMENT_REQ_ACK
CONNECTION_CONFIRM
Reset timer Tmea 1105 (3)

ERROR_INDICATION 1104
RELEASE_REQUEST
Start timer Tend
1753
1778
1163/18
1044
1045
Reset timer Tend
CLEAR_REQUEST
Set timer TrelREQ
1108
1502

411--9001--125
MS BTS BSC MSC

1601
1602
1603
1622
1623
1624
1625
1626
1805 (3)
Set timer TclrCMD 1806 (3)
1807 (3)
1808 (3)
CLEAR_COMMAND
Reset timer TclrCMD
1107
1503
CLEAR_COMPLETE
Reset timer TrelREQ
1108
1502
RELEASE_CONFIRM
Set timer TdeacAck
DEACTIVATE_SACCH
Reset timer TdeacAck
DEACTIVATE_ACK
Set timer T3109
RF_CHANNEL_RELEASE
Timer T3109 expires
Set timer TrfAck
1607 (--1) Reset timerr TrfAck

DISCONNECTED_INDICATION
1105 (--1)
1191/1 and 1730 for cause 001
1191/4 and 1730 for cause 100

1744, 1746, 1609/2, 1611/2
(3) ASCI counters are optional since they are related to the GSM--R functionality.

number
milliseconds
received by the BSC
by the BSC
1163/18 signallingReleaseBtsErrorIndDm number of communications in
signaling phase released because of
DM frames received in established
multiframe mode when a cell is
associated to the communication
Cause Xxx
by the BSC

411--9001--125

number
by the MSC
1601 downlinkPowerCtrlMaxSdcchM duration of maximum downlink power
oy/Max/Cum/Ech use on busy SDCCHs
1602 uplinkPowerCtrlMaxSdcchMoy/ duration of maximum uplink power
Max/Cum/Ech use on busy SDCCHs
1603 connectionDurationSdcchMoy/ connection duration of SDCCHs
Max/Cum/Ech (concentric cell)
or or
connectionDurationSdcchTrZone connection duration of SDCCHs
Moy/Max/Cum/Ech (non--concentric cell)
1606 sdcchAllocatedTrZone number of SDCCHs allocated in the
inner or outer zone of the cell
1607 sdcchAveragedUsedTrZoneMo average number of SDCCHs used in
y/Max/Cum/Ech the inner or outer zone of the cell
unavailability
1622 msLostMeasurements number of MS measurement
messages not received by the cell
or or
msLostMeasurementsTrZone number of MS measurement
messages not received by the inner
1623 rxLevDownLink sum of downlink signal strength
measurements received on the cell
or or
rxLevDownLinkTrZone sum of downlink signal strength
measurements received on the inner
1624 rxLevUpLink sum of uplink signal strength
or or
rxLevUpLinkTrZone sum of uplink signal strength
1625 rxQualDownLink sum of downlink signal quality
measurements on the cell
or or
rxQualDownLinkTrZone sum of downlink signal quality
measurements on the inner or outer
zone of the cell


number
1626 rxQualUpLink sum of uplink signal quality
or or
rxQualUpLinkTrZone sum of uplink signal quality
zone of the cell
or or
PDTCH allocated in the inner or
or or
tchFrAveragedUsedTrZoneMo average number of TCH/FR or
y/Max/Cum/Ech preempted PDTCH used in the inner
requests
assignments
received
communication is in ”signalling
communication
the communication is in ”signalling
communication
1805 msPowerIncControl number of MS increment power
controls ordered by the Layer 1
management
1806 msPowerDecControl number of MS decrement power
management
1807 bsPowerIncControl number of BS increment power
management
1808 bsPowerDecControl number of BS decrement power
management

411--9001--125
2.2.4.9 Rejection from the MSC
Data Flow Diagram: immediate assignment failure procedure: rejection from the
MSC
MS BTS BSC MSC

CHANNEL_REQUEST
CHANNEL_REQUIRED
1748
1702
1191/n (1)
1730 (1)
1606
1607
1744 (2)
1746 (2)
1609/2 (2)
1611/2 (2)
CHANNEL_ACTIVATE
Set timer TchnAck
1629/0
Set timer T3101
Reset timer TchnAck IMMEDIATE_ASSIGNMENT_COMMAND
1749
SABM 1192/n
Reset timer T3101
1750
1195 or 1196 (L3_INFORMATION
CM_SERVICE_REQUEST)
1108
1502
Set timer Tmea START_MEASUREMENT_REQ_ACK
CONNECTION_CONFIRM
Reset timer Tmea 1105

DATAREQ [05 22] 1104

MS BTS BSC MSC

CLEAR_COMMAND
Reset timer TclrCMD
1107
1503
1753 (3)
1163/20
1044
1045
CLEAR_COMPLETE
1108
1502
CHANNEL_RELEASE
DEACTIVATE_SACCH
Set timer TdeacAck
DEACTIVATE_ACK
Reset timer TdeacAck
Set timer Tend
Reset timer Tend Set timer T3109
RELEASE_INDICATION
Reset timer T3109
RF_CHANNEL_RELEASE
Set timer T3111 Set timer TrfAck
Timer T3111 expires Reset timer TrfAck
1607 (--1)
DISCONNECTED_INDICATION
1105 (--1)
1191/1 and 1730 for cause 001
1191/4 and 1730 for cause 100

411--9001--125
1744, 1746, 1609/2, 1611/2
(3) DTAP service is now open

number
milliseconds
received by the BSC
by the BSC
1163/20 signallingReleaseBtsClearCom number of communications in
mand signaling phase released because of
CLEAR COMMAND received when a
cell is associated to the
communication
Cause Xxx


number
by the BSC
by the MSC
1602 uplinkPowerCtrlMaxSdcchMoy/ duration of maximum uplink power
Max/Cum/Ech use on busy SDCCHs
1603 connectionDurationSdcchMoy/ connection duration of SDCCHs
Max/Cum/Ech (concentric cell)
or or
connectionDurationSdcchTrZo connection duration of SDCCHs
neMoy/Max/Cum/Ech (non--concentric cell)
1606 sdcchAllocatedTrZone number of SDCCHs allocated in the
unavailability
or or
or or
or or

411--9001--125

number
or or
zone of the cell
or or
zone of the cell
or or
or or
Max/Cum/Ech preempted PDTCH used in the inner
requests
assignments
received
communication

2.3 Dedicated channel assignment

Dedicated channel assignment procedures are used to modify previous radio
channel assignments.
2.3.1 Nominal procedure

This procedure is used to modify a channel type (change from SDCCH to TCH or
change of transmission mode) or to process handover requests.
Data Flow Diagram: dedicated channel assignment procedure (a MS switching
from an SDCCH to a TCH for service).

411--9001--125
MS BTS BSC MSC

ASSIGNMENT_REQUEST
1107
1503
1841/0
1744
1746
1609/0
CONN_STATE_REQ 1611/0 (1)
1812
1094
1095
CONN_STATE_REQ_ACK
CHANNEL_ACTIVATE
Set timer TchnAck
1197/0 or 1197/1
or 1709 and 1705/n (2)
or 1710 and 1707/n
Reset timer TchnAck
ASSIGNMENT_COMMAND
Set timer T3107
ASSIGNMENT_COMMAND
1049
1715 (3)
1601
1602
1603
1622
1623
1624
1625
1626
1805
1806
SABM 1807
1808 (4)
UA ESTABLISH_INDICATION
ASSIGNMENT_COMPLETE ASSIGNMENT_COMPLETE Reset timer T3107

1050 ASSIGNMENT_COMPLETE
1716 (5)
1108
START_MEASUREMENT_ACK
RF_CHANNEL RELEASE
Set timer TrfAck
1044
1045
RF_CHANNEL RELEASE_ACK
Reset timer TrfAck
1607(--1) (4)
1717
1718
1719
1720
1721

(1) When a TCH resource is successfully allocated internally in the BSC software,
the following counters are incremented:
1609/0 tchFrAllocatedTchAllocation (number of TCH/FR allocated for traffic in
the inner or outer zone of the cell)
1611/0 tchFrAveragedUsedTchAllocationMoy/Max/Cum/Ech (average number
of TCH/FR used for traffic in the inner or outer zone of the cell)
1812 allocatedCircuitTsMoy/Max/Cum/Ech (number of TS allocations for
traffic on circuit mode in the cell or
allocatedCircuitTsTrZoneMoy/Max/Cum/Ech (number of TS allocations for
traffic on circuit mode in the inner or the outer of the cell
(2) The counter incremented depends on the channel mode used (speech or data):
either 1197/0 (FR) or 1197/1 (EFR) for speech
or 1709 and 1705/n (n=0 to 6) for transparent data
or 1710 and 1707/n (n=0 to 2) for non--transparent data
(3) When the ASSIGNMENT_COMMAND message is received, 1049
attemptedTchFrSeizures (number of TCH/FR assignment requests) is incremented
and, if the MS is the dualband type, 1715 attempted TchFrSeizuresMsDualdb is also
incremented.
(4) When the STOP_MEASUREMENT message for the SDCCH channel is
received, if the BTS reports measurement counters, the BSC increments 1601,
1602, 1603, 1622, 1623, 1624, 1625, 1626, 1804, 1805, 1806, 1807 and 1808.
(5) The old (SDCCH) channel is released. 1050 successfulTchFrSeizures is
incremented and, if the MS is the dualband type, 1716
successfulTchFrSeizuresMsDualb is also incremented.
(6) When the old (SDCCH) channel has been released, 1607 counting the average
number of SDCCH used in the inner or outer zone of the cell is decremented.
List of counters incremented or decremented during this procedure:

number
1044 signallingPhaseDurationMoy/Max/ average time of a signaling chan-

Cum/Ech nel seizure
1045 signallingPhaseDurationHighMoy/ average time of a signaling chan-

Max/Cum/Ech nel seizure > 25s
1049 attempedTchFrSeizures number of TCH/FR assignment

requests
1050 successfulTchFrSeizures number of TCH/FR successfully

assigned

411--9001--125

number
1094 tcAllocated number of terrestrial circuits allo-

cated
1095 tcAveragedUsedMoy/Max/Cum//Ech average number of terrestrial cir-

cuits used

received by the BSC
1108 aOutputMessage number of BSSAP messages

sent by the BSC
1197/0 channelActivateSpeechFullRate number of channels activated for

speech: Full Rate algorithm
1197/1 channelActivateSpeechEnhanced- number of channels activated for

FullRate speech: Enhanced Full Rate
algorithm
1502 aNonTransparentUp number of BSSMAP messages

sent by the BSC

received by the BSC
1601 downlinkPowerCtrlMaxSdcchMoy/Max/ duration of maximum downlink

Cum/Ech power use on busy SDCCHs
1602 uplinkPowerCtrlMaxSdcchMoy/Max/ duration of maximum uplink

Cum/Ech power use on busy SDCCHs
1603 connectionDurationSdcchMoy/Max/ connection duration of SDCCHs

Cum/Ech (concentric cell)
or or
connectionDurationSdcchTrZoneMoy/ connection duration of SDCCHs
Max/Cum/Ech (non--concentric cell)
1607 sdcchAveragedUsedTrZoneMoy/ average number of SDCCHs

Max/Cum/Ech used in the inner or outer zone of
the cell
1609/0 tchFrAllocatedTchAllocationTrZone number of TCH/FR or preempted

PDTCH allocated for traffic in the
inner of outer zone of the cell
1611/0 tchFrAveragedUsedTchAllocation- average number of TCH/FR or

TrZoneMoy/Max/Cum/Ech preempted PDTCH used for traf-
fic in the inner or outer zone of
the cell


number

messages not received (non--
or concentric cell)
msLostMeasurementsTrZone or
number of MS measurement
messages not received (concen-
tric cell)

measurements received (non--
concentric cell)
or or
measurements received (concen-
tric cell)

measurements received (non--
concentric cell)
or or
measurements received (concen-
tric cell)

measurements (concentric cell)
or
sum of downlink signal quality
or measurements (non--concentric
rxQualDownLinkTrZone cell)
1626 rxQualUpLink sum of uplink signal quality mea-

surements (non--concentric cell)
or or
rxQualUpLinkTrZone sum of uplink signal quality mea-
surements (concentric cell)
1629/0 channelActivateSignallingFullRate number of Full--Rate channels

activated for signaling
1629/1 channelActivateSignallingEnhanced- number of Enhanced--Full--Rate

FullRate channels activated for signaling
1705/n channelActivateTchFrDataTx (x = 16 number of TCH/FR activation for

(n = 0 to 6) to 14400 b/s) transparent data service with a
transmission rate = x
1707/n channelActivateTchFrDataNTx number of TCH/FR activation for

(n = 0 to 2) (x = 6 to 14500 b/s) non transparent data service with
a transmission rate = x

411--9001--125

number
1710 channelActivateTchFrNDa- number of channel activation for

taNTHscsd non transparent data service on
TCH/FR
1715 attemptedTchFrSeizuresMsDualb number of attempts of assigna-

tion of a TCH/FR for dualband
mobiles
1716 successfulTchFrSeizuresMsDualb number of successful TCH/FR

assignations for dualband
mobiles
1717 abisTrauFrameDlReceived number of frames TRAU donw-

link received
1718 abisTrauFrameDlCorrected number of frames TRAU donw-

link corrected
1719 abisTrauFrameDlMuted number of frames TRAU donw-

link that can not be corrected
1720 radioFrameUlReceived number of radio frames uplink

received
1721 ECU_Activation number of erroneous frames

(ECU may be activated or not)

or or
1746 tchFrAveragedUsedMoy/Max/Cum/ average number of TCH/FR or

Ech preempted PDTCH used in the
cell
or or
Max/Cum/Ech preempted PDTCH used in the


number
1812 allocatedCircuitTsMoy number of TS allocations for traf-

fic in circuit mode in the cell
or or
allocatedCircuitTsTrZoneMoy number of TS allocations for
traffic in circuit mode in the inner
or the outer zone of the concen-
tric cell
1841/0 assignRequestSdcchToTchChannel number of assignment request

messages received: modification
from an SDCCH channel to a
TCH channel

411--9001--125
2.3.2 MODE MODIFY procedure

This procedure is used to modify the coding/decoding/transcoding mode on the
dedicated cell channels used for sending speech or data.
It is also used when the MS initiates a call re--establishment request. In this case,
the BSC allocates a TCH for signaling and may use this particular procedure to
accomplish the transition from signaling to speech mode rather than the general
procedure which is much longer.
MS BTS BSC MSC

ASSIGNMENT_REQUEST
1107 (1)
1503
1841/1
1094
1095
MODE_MODIFY_REQUEST
1197/n (2) Set timer TmodAck

1709
1705/n
1710
1707/n
MODE_MODIFY_REQUEST_ACK
Reset timer TmodAck
CHANNEL_MODE_MODIFY
CHANNEL_MODE_MODIFY Set timer TmodMS
CHANNEL_MODE_MODIFY_ACK
CHANNEL_MODE_MODIFY
Reset timer TmodMS
1044
1045 ASSIGNMENT_COMPLETE
1108 (3)
1502
(1) Downlink DTAP service is suspended.

-- Either 1197/0 (FR) or 1197/1 (EFR) for speech
-- 1709 and 1705/n (n = 0 to 6) for transparent data
-- 1710 and 1705/n (n = 0 to 6) for non transparent data
(3) Downlink DTAP service is resumed.


number
1044 signallingPhaseDurationMoy/ average time of a signaling channel
Max/Cum/Ech seizure
1045 signallingPhaseDurationHighM average time of a signaling channel
oy/Max/Cum/Ech seizure > 25s
1094 tcAllocated number of terrestrial circuits allocated
1095 tcAveragedUsedMoy/Max/C average number of terrestrial circuits
um//Ech used
received by the BSC
the BSC
1197/0 channelActivateSpeechFullR number of channels activated for
ate speech: Full Rate algorithm
by the BSC
received by the BSC
1841/0 assignRequestSdcchToTchC number of assignment request
hannel messages received: modification from
an SDCCH channel to a TCH channel

411--9001--125
2.3.3 No resource available and queuing not activated

The terrestrial circuit allocation is engaged before the radio resource allocation. If
the radio resource allocation fails because of radio resource shortage, the
TCH--FR--RESOURCE--FAILURE observation point is incremented.
The cause value is one of the following:
“BSS not equipped”
“requested terrestrial resource unavailable”
“terrestrial resource already allocated”
“no radio resource available”
Data Flow Diagram: dedicated channel assignment procedure (no resource
available and queuing not activated).
MS BTS BSC MSC

ASSIGNMENT_REQUEST
1107 (1)
1503
1841/0
1094 (2)
1095
1613
1842/0 (3)
1095 (--1) (4)
ASSIGNMENT_FAILURE
1108
1502 (5)

(2) The Terrestrial Circuit is allocated before sending a request to allocator.
(3) The request for a radio resource is rejected.
(4) The Terrestrial Circuit is deallocated before sending an ASSIGNMENT_FAILURE
message.

number
1095 tcAveragedUsedMoy/Max/ average number of terrestrial circuits

Cum//Ech used


number
1107 aInputMessage number of BSSAP messages received

by the BSC

the BSC
1502 aNonTransparentUp number of BSSMAP messages sent by

the BSC

received by the BSC
1613 tchFrResourceFailureTrZone number of TCH/FR and preemptable

PDTCH allocation failures in the inner
1841/0 assignRequestSdcchToTch- number of assignment request mes-

Channel sages received: modification from an
SDCCH channel to a TCH channel
1842/0 assignFailureSdcchToTch- number of emission of ASSIGNMENT

Channel FAILURE messages on the A interface:
modification from an SDCCH channel
to a TCH channel or a preempted
PDTCH

411--9001--125
2.3.4 Queuing procedure (successful completion)

Data Flow Diagram: queuing of the assignment procedure (successful completion).
MS BTS BSC MSC

ASSIGNMENT_REQUEST
1107 (1)
1503
1841/0
1616/N
(2)
QUEUEING
1108 (3)
1502 Set timer T11
1616/n(--1)
1618/n(--1)
1744
1746
1609/0
1611/0
1812
1094
1095
CONNECTION_STATE_REQUEST Reset timer T11
Set timer Tcnx
CONN_STATE_REQ_ASK Reset timer Tcnx (4)

CHANNEL_ACTIVATE
Set timer TchnAck
1197/0 or 1197/1
or 1709 and 1705/n (5)
or 1710 and 1707/n
CHANNEL_ACTIVATE_ASK Reset timer TchnAck

ASSIGNMENT_COMMAND
ASSIGNMENT_COMMAND
1049 (6)
1715
Set timer T3107

MS BTS BSC MSC
STOP_MEASUREMENT_REQ_ACK
Reset timer T3107
1601 (7)
1602
1603
1622
1623
1624
1625
1626
1805 (8)
1806 (8)
1807 (8)
SABM 1808 (8)
UA
ASSIGNMENT_COMPLETE
ASSIGNMENT_COMPLETE
1050 (9) ASSIGNMENT_COMPLETE

1716
1108
1502
Set timer Tmea
(10)
Reset timer Tmea
RF_CHANNEL RELEASE
Set timer TrfAck
1044
1045
RF_CHANNEL RELEASE_ACK
1607 (--1)
RF_CHANNEL RELEASE_ACK Reset timer TrfAck
1607 (--1)
1717
1718
1719
1720
1721

(2) There are no TCH resources available. Downlink DTAP service is resumed.
(3) When a TCH resource is successfully allocated internally in the BSC software,
the queued request is serviced and the following counters are incremented:
1094 tcAllocated (number of terrestrial circuits allocated)
1095 tcAveragedUsedMoy/Max/Cum//Ech (average number of terrestrial
circuits used)

411--9001--125
1609/0 chFrAllocatedTchAllocationTrZone (number of TCH/FR allocated for

traffic in the inner of outer zone of the cell)
1611/0 tchFrAveragedUsedTchAllocationTrZoneMoy/Max/Cum/Ech (average
number of TCH/FR used for traffic in the inner or outer zone of the cell)
1616/n
or 1710 and 1707/n (n=0 to 2) for non transparent data
(6) When the ASSIGNMENT_COMMAND message is received, 1049
attemptedTchFrSeizures (number of TCH/FR assignment requests) is incremented
and, if the MS is the dualband type, 1715 attemptedTchFrSeizuresMsDualb is also
incremented.
received, if the BTS reports measurement counters, the BSC increments 1601,
1602, 1603, 1622, 1623, 1624, 1625, 1626, 1805, 1806, 1807 and 1808.
(8) The old (SDCCH) channel is released. 1050 successfulTchFrSeizures is
incremented and, if the MS is the dualband type, 1716
successfulTchFrSeizuresMsDualb is also incremented.

number

Max/Cum/Ech seizure
1045 signallingPhaseDurationHigh- average time of a signaling channel

Moy/Max/Cum/Ech seizure > 25s


number
1049 attempedTchFrSeizures number of TCH/FR assignment

requests

assigned

Cum//Ech used

by the BSC

the BSC
1197/0 channelActivateSpeechFull- number of channels activated for

Rate speech: Full Rate algorithm
1197/1 channelActivateSpeechEn- number of channels activated for

hancedFullRate speech: Enhanced Full Rate algorithm

the BSC

received by the BSC
1601 downlinkPowerCtrlMaxSdc- duration of maximum downlink power

chMoy/Max/Cum/Ech use on busy SDCCHs
1602 uplinkPowerCtrlMaxSdcchMoy/ duration of maximum uplink power use

Max/Cum/Ech on busy SDCCHs
1603 connectionDuration- connection duration of SDCCHs

SdcchMoy/Max/Cum/Ech (concentric cell)
or or
connectionDurationSdcchTrZo- connection duration of SDCCHs
neMoy/Max/Cum/Ech (non--concentric cell)
1607 sdcchAveragedUsedTrZone- average number of SDCCHs used in

Moy/Max/Cum/Ech the inner or outer zone of the concen-
tric cell
1609/0 tchFrAllocatedTchAllocation- number of TCH/FR or preempted

TrZone PDTCH allocated for traffic in the inner
of outer zone of the cell

411--9001--125

number
1611/0 tchFrAveragedUsedTchAlloca- average number of TCH/FR or pre-

tionTrZoneMoy/Max/Cum/Ech empted PDTCH used for traffic in the
1616/n tchAveragedQueueLength- number of queued TCH requests with

[n= 0 to 1] HighPriorityMoy/Max/Cum/ the highest priority
Ech for n=0 and
and number of queued TCH requests with
tchAveragedQueueLengthO- an internal priority different than the
therPriorityMoy/Max/Cum/Ech highest one
for n=1
1622 msLostMeasurements number of MS measurement messages

not received (non--concentric cell)
or or
msLostMeasurementsTrZone number of MS measurement messages
not received (concentric cell)
1623 rxLevDownLink sum of downlink signal strength mea-

surements received (non--concentric
cell)
or or
rxLevDownLinkTrZone sum of downlink signal strength mea-
surements received (concentric cell)
1624 rxLevUpLink sum of uplink signal strength measure-

ments received (non--concentric cell)
or or
rxLevUpLinkTrZone sum of uplink signal strength measure-
ments received (concentric cell)
1625 rxQualDownLink sum of downlink signal quality mea-

surements (concentric cell)
or or
rxQualDownLinkTrZone sum of downlink signal quality mea-
surements (non--concentric cell)
1626 rxQualUpLink sum of uplink signal quality measure-

ments (non--concentric cell)
or or
rxQualUpLinkTrZone sum of uplink signal quality measure-
ments (concentric cell)
1705/n channelActivateTchFrDataTx (x number of TCH/FR activation for trans-

(n = 0 to 6) = 16 to 14400 b/s) parent data service with a transmission
rate = x
1707/n channelActivateTchFrDa- number of TCH/FR activation for non

(n = 0 to 2) taNTx (x = 6 to 14500 b/s) transparent data service with a trans-
mission rate = x


number
1710 channelActivateTchFrNDa- number of channel activation for non

taNTHscsd transparent data service on TCH/FR
1715 attemptedTchFrSeizu- number of attempts of assignation of a

resMsDualb TCH/FR for dualband mobiles
1716 successfulTchFrSeizu- number of successful TCH/FR assigna-

resMsDualb tions for dualband mobiles
1717 abisTrauFrameDlReceived number of frames TRAU downlink

received
1718 abisTrauFrameDlCorrected number of frames TRAU downlink cor-

rected
1719 abisTrauFrameDlMuted number of frames TRAU downlink that

can not be corrected
1720 radioFrameUlReceived number of radio frames uplink received
1721 ECU_Activation number of erroneous frames (ECU may

be activated or not)

or or
zone of the cell
1746 tchFrAveragedUsedMoy/Max/ average number of TCH/FR or pre-

Cum/Ech empted PDTCH used in the cell
or or
tchFrAveragedUsedTrZone- average number of TCH/FR or pre-
Moy/Max/Cum/Ech empted PDTCH used in the zone (con-
centric cell)
1805 msPowerIncControl number of MS increment power con-

trols ordered by the Layer 1 manage-
ment
1806 msPowerDecControl number of MS decrement power con-

ment
1807 bsPowerIncControl number of BS increment power con-

ment

411--9001--125

number
1808 bsPowerDecControl number of BS decrement power con-

ment
1812 allocatedCircuitTsMoy/Max/ number of TS allocations for traffic in

Cum/Ech circuit mode in the cell
or or
allocatedCircuitTsTrZoneMoy/ number of TS allocations for traffic in
Max/Cum/Ech circuit mode in the inner or the outer
1841/0 assignRequestSdcchToTch- number of assignment request mes-

Channel sages received: modification from an
SDCCH channel to a TCH channel

2.4 Handovers
2.4.1 Overview
Each handover procedure performed in a cell requires two phases, a selection phase
and an execution phase.
selection phase: choice of the target cell (outgoing handover) or radio channel
(incoming or intra-bts handover)
execution phase: switchover from one radio channel to another
The execution phase is not started unless the selection phase is successfully
completed as shown in the following diagram.
handover Yes: execution Yes: handover

SELECTION EXECUTION
request request successful
No No
call interrupted
SELECTION_FAILURE EXECUTION_FAILURE
The ratios between the following counters are used to evaluate the efficiency of the
procedures implemented in the BSS:
Number of handovers required (hoRequiredXxx)
Number of handover requests (hoRequestXxx)
Number of handovers executed (hoExecutionXxx)
Number of successful handovers (hoSuccessXxx)
The procedures call on the following counters in problem cases:
permanent bsc observation:
• hoIndicationNotTreatedTchoke
• hoIndicationNotTreatedTmtBtwHo
• hoUnsuccessReestIntraBts on TCH or SDCCH
• hoUnsuccessReestOutgoingIntraBss on TCH or SDCCH

411--9001--125
• hoUnsuccessReestIncomingIntraBss on TCH or SDCCH

• hoUnsuccessOutgoingIntraBssNAttempt on TCH or SDCCH
• hoUnsuccessReestOutgoingInterBss on TCH or SDCCH
• hoUnsuccessOutgoingInterBssNAttempt on TCH or SDCCH
temporary “handover” observation:
• hoIntraBtsUnsuccessXxx on TCH or SDCCH
• hoIntraBtsFailureXxx on TCH or SDCCH
• hoOutIntraUnsuccessXxx on TCH or SDCCH
• hoOutIntraFailureXxx on TCH or SDCCH
• hoInIntraUnsuccessXxx on TCH or SDCCH
• hoInIntraFailureXxx on TCH or SDCCH
• hoOutInterUnsuccessXxx on TCH or SDCCH
• hoOutInterFailureXxx on TCH or SDCCH
• hoInInterUnsuccessXxx on TCH or SDCCH
• hoInInterFailureXxx on TCH or SDCCH

2.4.2 Accounting principles

To synchronize accounting, all the counters concerned by the same handover
request are incremented at the end of the procedure, except for the counters used to
tally repeated requests and refusals, which are stepped up in real time.
The following diagram is an example of an outgoing handover requested by cell N
in BSS 1 that is refused by the first cell in the list (cell A in BSS 1) and executed
successfully in the second cell (cell B in BSS 2). It shows the counters that are
updated by the handover procedure.
request
cell N BSS 1 cell A BSS 1 refused
hoRequiredXxx cell N
hoRequestOutgoingIntra cell N
hoRequestIncomingIntra cell N
hoOutIntraFailureXxx cell N
hoInIntraFailureXxx cell A
request
cell N BSS 1 cell B BSS 2 accepted
EXECUTION
successful
hoRequiredXxx cell N
hoRequestOutgoingInter cell N
hoRequestIncomingInter cell B
hoExecutionOutgoingInter cell N
hoExecutionIncomingInter cell B
hoSuccessOutgoingInter cell N
hoSuccessIncomingInter cell B

411--9001--125
2.4.3 Intra-bts handover procedure

In the intra-bts handover procedure, a dedicated channel is assigned in response to
a modify radio channel request sent by Level 1 (Layer 1 Management).
Data Flow Diagram : intra--cell handover procedure (normal completion with
communication on TRAFFIC phase)
MS BTS BSC MSC

HANDOVER_INDICATION
1776
1138/n
1744
1746
1609/0 (1)
1611/0 (1)
1812 (1)
CHANNEL_ACTIVATE
Set timer TchnAck
1197/0 ou 1197/1
ou 1709 et 1705/n (2)
ou 1710 et 1707/n
Reset timer TchnAck
ASSIGNMENT_COMMAND
ASSIGNMENT_COMMAND
STOP_MEASUREMENT_REQUEST Set timer T3107
1198 (3)
1199
1600
1622
1623
1624
1625
1626
1805 (4)
1806 (4)
1807 (4)
1808 (4)
1809/n (4)
UA
ESTABLISHED_INDICATION

MS BTS BSC MSC
ASSIGNMENT_COMPLETE
Reset timer T3107
1083 or
1798 or
1802/n
RF_CHANNEL RELEASE
Set timer TrfAck HANDOVER_PERFORMED
1108
1502 1081 or 1796
1082 or 1797
Reset timer TrfAck
1812 (--1) (4)
1746 (--1)
1611 (--1)
(1) A TCH resource is successfully allocated internally in the BSC software on the
target cell. Then the following counters are incremented:
1609/0 tchFrAllocatedTchAllocationTrZone (number of TCH/FR allocated for

411--9001--125
1709 and 1705/n (n=0 to 6) for transparent data
1710 and 1707/n (n=0 to 2) for non transparent data
(3) When the STOP_MEASUREMENT message for the TCH channel is received,
if the BTS reports measurement counters, the BSC increments 1198, 1199, 1600,
1622, 1623, 1624, 1625, 1626, 1805, 1806, 1807, 1808 and 1809/n
(4) When the deallocation of TCH is successfully performed in the originating cell,
the following counters are decremented:
1746 tchFrAveragedUsedMoy/Max/Cum/Ech (average number of TCH/FR
used in the cell) or tchFrAveragedUsedTrZoneMoy/Max/Cum/Ech (average
number of TCH/FR used in the inner or outer zone of the cell)

number
1081 hoRequestIntraBts number of intra--bts handovers on
TCH requested in the cell
1082 hoExecutionIntraBts number of attempts to execute
intra--bts handovers on TCH in the
cell
1083 hoSuccessIntraBts number of successful intra--bts
handovers on TCH in the cell
by the BSC to the MSC
1138/n hoRequiredTchXxx number of handovers on TCH
[n=0 to 16] required: CauseXxx
1197/1 channelActivateSpeechEnhanc number of channels activated for
edFullRate speech: Enhanced Full Rate
algorithm
1198 downlinkPowerCtrlMaxTchMoy/M duration of maximum downlink
ax/Cum/Ech power use on busy TCHs
1199 uplinkPowerCtrlMaxTchMoy/Ma duration of maximum uplink power
x/Cum/Ech use on busy TCHs


number
sent by the BSC to the MSC
1600 connectionDurationTchMoy/Ma average duration and maximum
x/Cum/Ech duration of TCH/FR or preempted
PDTCH connections in the cell
or or
connectionDurationTchTrZoneMo average duration and maximum
y/Max/Cum/Ech duration of TCH/FR or preempted
PDTCH connections in the inner or
1609/0 tchFrAllocatedTchAllocationTrZ number of TCH/FR or preempted
one PDTCH allocated for traffic in the
1611/0 tchFrAveragedUsedTchAllocatio average number of TCH/FR FR or
nTrZoneMoy/Max/Cum/Ech preempted PDTCH used for traffic
in the inner or outer zone of the cell
or or
measurements performed by the
MS on the cell
or or
MS on the inner or outer zone of
the cell
BTS on the cell
or or
BTS on the inner or outer zone of
the cell
MS on the cell
or or
the cell

411--9001--125

number
BTS on the cell
or or
the cell
1705/n channelActivateTchFrDataTx number of TCH/FR activation for
[n = 0 to (x = 16 to 14400 b/s) transparent data service with a
6] transmission rate = x
[n = 0 to (x = 6 to 14500 b/s) non transparent data service with a
1709 channelActTchFrDataT number of channel activation for
transparent data service on
TCH/FR
1710 channelActTchFrDataNT number of channel activation for
non transparent data service on
TCH/FR
or or
or or
Max/Cum/Ech preempted PDTCH used in the
1776 hoRequiredTch number of handovers on TCH
required
1796 hoRequestIntraBtsMsDualb number of intra--bts handovers on
TCH requested in the cell by
dualband mobiles
1797 hoExecutionIntraBtsMsDualb number of attempts to execute
intra--bts handovers on TCH in the
cell by dualband mobiles
1798 hoSuccessIntraBtsMsDualb number of successful intra--bts
handovers on TCH in the cell for
dualband mobiles


number
1802/0 hoSuccessTieringTchLargeToS Number of tiering handover
mallPattern successes
1802/1 hoSuccessTieringTchSmallToLa
rgePattern
management
management
management
management
1809/n timingAdvanceAverage average timing advance value for
[n= 0 to 1] [for n=0] the communication in the cell or
or average timing advance value for
timingAdvanceAverageTrZone the communication in the inner or
[for n=0] outer zone of the cell or
or maximum timing advance value for
timingAdvanceMaximum the communication in the cell or
[for n=1] maximum timing advance value for
or the communication in the inner or
timingAdvanceMaximumTrZone outer zone of the cell
[for n=1]
1812 allocatedCircuitTsMoy/Max/ number of TS allocations for traffic
Cum/Ech in circuit mode in the cell
or or
allocatedCircuitTsTrZoneMoy/ number of TS allocations for traffic
Max/Cum/Ech in circuit mode in the inner or the

411--9001--125
2.4.4 Inter cell intra--bss handover procedure (normal completion)
An intra-bss handover request is initiated by the BSC. The MSC is informed of the
change by a HANDOVER PERFORMED message at the end of the procedure.
Dataflows: inter--cell intra BSC handover procedure (normal completion with

communication on TRAFFIC phase).
MS BTS1 BTS2 BSC MSC
ASSIGNMENT_REQUEST
1776
1138/n
1744
1746
1609/0 (1)
1611/0 (1)
1812 (1)
CHANNEL_ACTIVATE
Set timer TchnAck
1197/0 or 1197/1
or 1709 and 1705/n (2)
or 1710 and 1707/n
Reset timer TchnAck
HANDOVER_COMMAND Set timer T3103
HANDOVER_COMMAND
1198 (1)
1199
1600
1622
1623
1624
1625
1626
1805 (4)
1806 (4)
1807 (4)
1808 (4)
1806/n (4)
HANDOVER_ACCESS
HANDOVER_DETECT
SABM
UA
HANDOVER_COMPLETE

MS BTS1 BTS2 BSC MSC
HANDOVER_COMPLETE Reset timer T3103

HANDOVER_PERFORMED
1780
1067
1781
1073
1065
1071
1075
1069
1200
1839/n (4)
1840/n (4)
1077
1793, 1794, 1795 and
1208, 1789, 1209 or
START_MEASUREMENT_REQUEST 1783, 1790, 1786 or
1784, 1791, 1787 or
1785, 1792, 1788
RF_CHANNEL_RELEASE
Set timer TrfAck
1108
1502
Reset timer TrfAck
1812 (--1) (5)

1746 (--1)
1611 (--1)
(1) A TCH resource is successfully allocated internally in the BSC software on the
target cell. Then the following counters are incremented:
1609/0 tchFrAllocatedTchAllocationTrZone (number of TCH/FR allocated for

411--9001--125

or 1710 and 1707/n (n=0 to 2) for non transparent data
1622, 1623, 1624, 1625, 1626, 1805, 1806, 1807, 1808 and 1809/n
number of TCH/FR used in the inner or outer zone of the cell)

number
1065 hoExecutionOutgoingIntraBss number of attempts to execute outgo-

ing intra--bss handovers on TCH
1067 hoSuccessOutgoingIntraBss number of successful outgoing intra--

bss handovers on TCH
1069 hoRequestIncomingIntraBss number of successful incoming intra--

bss handovers on TCH requested
1071 hoExecutionIncomingIntraBss number of successful incoming intra--

bss handovers on TCH execution
attempts
1073 hoSuccessfulIncomingIntraBss number of successful incoming intra--

bss handovers on TCH


number
1075 hoRequestOutgoingIntraBss number of successful outgoing intra--

bss handovers on TCH requested
1077 hoSuccessOutgoingFirstIntra number of successful outgoing intra--

bss handovers on TCH after first
attempt

the BSC to the MSC

1197/0 channelActivateSpeechFull- number of channels activated for

Rate speech: Full Rate algorithm
1197/1 channelActivateSpeechEn- number of channels activated for

hancedFullRate speech: Enhanced Full Rate algorithm
1198 downlinkPowerCtrlMaxTchMoy/ duration of maximum downlink power

Max/Cum/Ech use on busy TCHs
1199 uplinkPowerCtrlMaxTchMoy/ duration of maximum uplink power

1200 hoNcellsExecution number of handovers on TCH exe-

cuted
1208 hoRequestOutgoingMbandE- number of outgoing requested by

bandMsDualb dualband mobiles from the main fre-
quency band to the second frequency
band of the network
1209 hoSuccessOutgoingMbandE- number of successful outgoing hand-

bandMsDualb overs for dualband mobiles from the
main frequency band to the second
frequency band of the network

1600 connectionDurationTchMoy/ average duration and maximum dura-

Max/Cum/Ech tion of TCH/FR or preempted PDTCH
connections in the cell
or or
connectionDurationTchTrZone- average duration and maximum dura-
Moy/Max/Cum/Ech tion of TCH/FR or preempted PDTCH
connections in the inner or outer zone
of the cell

411--9001--125

number

TrZone PDTCH allocated for traffic in the
1611/0 tchFrAveragedUsedTchAllocation- average number of TCH/FR or pre-

TrZoneMoy/Max/Cum/Ech empted PDTCH used for traffic in the
1622 msLostMeasurements number of MS measurement mes-

sages not received by the cell
or or
msLostMeasurementsTrZone number of MS measurement mes-
sages not received by the inner or

surements performed by the MS on
the cell
or or
the inner or outer zone of the cell
1624 rxLevUpLink sum of uplink signal strength mea-

surements performed by the BTS on
the cell
or or
rxLevUpLinkTrZone sum of uplink signal strength mea-
surements performed by the BTS on
1625 rxQualDownLink sum of downlink signal quality mea-

the cell
or or
rxQualDownLinkTrZone sum of downlink signal quality mea-

ments performed by the BTS on the
cell
or or
ments performed by the BTS on the
1705/n channelActivateTchFrDataTx number of TCH/FR activation for

[n = 0 to 6] (x = 16 to 14400 b/s) transparent data service with a trans-
mission rate = x


number
1707/n channelActivateTchFrDataNTx number of TCH/FR activation for non

[n = 0 to 2] (x = 6 to 14500 b/s) transparent data service with a trans-
mission rate = x
1710 channelActivateTchFrNDa- number of channel activation for non

taNTHscsd transparent data service on TCH/FR

or or
zone of the cell

or or
Moy/Max/Cum/Ech empted PDTCH used in the inner or

required
1780 hoSuccessOutgoingTch number of successful outgoing hand-

overs from the cell
1781 hoSuccessfulIncomingTch number of successful incoming hand-

overs in the cell
1783 hoRequestOutgoingMbandM- number of outgoing handovers

bandMsDualb requested by dualband mobiles from
the main frequency band to the same
1784 hoRequestOutgoingEbandE- number of outgoing handovers

the second frequency band to the
same frequency band of the network
1785 hoRequestOutgoingEbandM- number of outgoing handovers

the second frequency band to the
main frequency band of the network
1786 hoSuccessOutgoingMbandM- number of successful outgoing hand-

main frequency to the same frequency
band of the network

411--9001--125

number
1787 hoSuccessOutgoingEbandE- number of successful outgoing hand-

second frequency band to the same
1788 hoSuccessOutgoingEbandM- number of successful outgoing hand-

second frequency band to the main
1789 hoExecutionOutgoingMbandE- number of outgoing handovers execu-

bandMsDualb tions by dualband mobiles for the
main frequency band to the second
1790 hoExecutionOutgoingMbandM- number of outgoing handovers execu-

bandMsDualb tions by dualband mobiles for the
main frequency band to the same fre-
quency band of the network
1791 hoExecutionOutgoingEbandE- number of outgoing handovers execu-

bandMsDualb tions by dualband mobiles for the sec-
ond frequency band to the same fre-
1792 hoExecutionOutgoingEbandM- number of outgoing handovers execu-

bandMsDualb tions by dualband mobiles for the sec-
ond frequency band to the main fre-
1793 hoRequestIncomingIn- number of incoming intra--bss hand-

traBssTchMsDualb overs on TCH requested by dualband
mobiles
1794 hoExecutionIncomingIn- number of incoming intra--bss hand-

traBssTchMsDualb overs on TCH execution attempts for
dualband mobiles
1795 hoSuccessIncomingIn- number of successful incoming intra--

traBssTchMsDualb bss handovers on TCH for dualband
mobiles
1805 msPowerIncControl number of MS increment power con-

ment
1806 msPowerDecControl number of MS decrement power con-

ment


number
1807 bsPowerIncControl number of BS increment power con-

ment
1808 bsPowerDecControl number of BS decrement power con-

ment
1809/n timingAdvanceAverage for n=0 average timing advance value for the
[n= 0 to 1] or communication in the cell or
timingAdvanceAverageTrZone average timing advance value for the
for n=0 communication in the inner or outer
zone of the cell
timingAdvanceMaximum for maximum timing advance value for
n=1 the communication in the cell or
timingAdvanceMaximumTr- the communication in the inner or
Zone for n=1 outer zone of the cell

or or
allocatedCircuitTsTrZoneMoy/ number of TS allocations for traffic in
Max/Cum/Ech circuit mode in the inner or the outer
1839/n hoNcellsRequestOutgoingXxx number of outgoing intra--bss or inter--

[n=o to 9] bss handover attempts from a central
cell to a neighboring one: Xxx
1840/n hoNcellsSuccessOutgoingXxx number of outgoing intra--bss or inter--

[n=o to 9] bss handover successes from a cen-
tral cell to a neighboring one: Xxx
2.4.5 Inter-bss handover procedure
Data Flow Diagram : inter BSS intra MSC handover procedure (normal completion
with communication on TRAFFIC phase)
The downlink DTAP messages sent by MSC to the target BSC between sending
HANDOVER REQUEST and receiving HANDOVER COMPLETE are ignored.
The uplink DTAP service is not inhibited on the channel being used until the channel
is released.

411--9001--125
MS BTS1 BSC1 MSC BSC2 BTS2

HANDOVER_
INDICATION
1776
1138/n
HANDOVER_ CONNECTION_
REQUIRED INDICATION_
(HANDOVER_
REQUEST)
1108 Set timer T7
1502 CONNECTION_
RESPONSE
1105
1104
1107
1503 CHANNEL_ACTIVATE
Set timer TchnAck
1744
1746 1197/0 or 1197/1
1609/0 or 1709 and 1705/n (1)
1611/0 or 1710 and 1707/n
1812
1094 CHANNEL_ACTIVATE_
1095 ACK
Reset timer
TchnAck
Set timer T3107
HO_REQ_ACK
(HANDOVER_
COMMAND)
HANDOVER_
HO_REQ_ACK COMMAND
(HANDOVER_ Set timer T8
COMMAND)
HANDOVER_
Reset timer T7
COMMAND
1107
1503 (2)
STOP_MEAS_
REQUEST
STOP_MEAS_
REQ_ACK
1198 (3)
1199
1600
1622
1623
1624
1625
1626
1805 (4)
1806 (4)
1807 (4)
1808 (4)
1809/n (4)


HANDOVER_
ACCESS
PHYSICAL_
INFORMATION
HANDOVER_
DETECT
SABM
ESTABLISH_
INDICATION
UA
START_MEAS_
REQUEST
START_MEAS_
REQ_ACK
1108
1500
HANDOVER_ 1107
COMPLETE 1501
HANDOVER_
COMPLETE
Reset timer T3107

1781
HANDOVER_ 1074
COMPLETE 1072
1070
1108
1502

411--9001--125

CLEAR_
COMMAND
Reset timer T8
1107
1503
1754
1164/20
1095 (--1)
CLEAR_
COMPLETE
1108
1502
1780
1068
1066
1076
1200
1839/N
1840/N
1078
RF_CHANNEL_
RELEASE
Set timer TrfAck
RF_CHANNEL_
RELEASE_ACK
Reset timer TrfAck 1812 (5)
1746 (5)
1611 (5)
DISCONNECT_
INDICATION
1105 (--1)
1709 and 1705/n (n=0 to 6) for transparent data
1710 and 1707/n (n=0 to 2) for non transparent data
(2) DTAP is suspended.
1622, 1623, 1624, 1625, 1626, 1805, 1806, 1807, 1808 and 1809/n


number of TCH/FR used in the inner or outer zone of the
cell )

number
1066 hoExecutionOutgoingInterBss number of attempts to execute
outgoing inter--bss handovers on
TCH
1068 hoSuccessOutgoingInterBss number of successful outgoing
inter--bss handovers on TCH except
those after the first attempt
1070 hoRequestIncomingInterBss number of incoming inter--bss
handover requests on TCH
1072 hoExecutionIncomingInterBss number of attempts to execute
incoming inter--bss handovers on
TCH
1074 hoSuccessfulIncomingInterBss number of successful incoming
inter--bss handovers on TCH
1076 hoRequestOutgoingInterBss number of outgoing inter--bss
handover requests on TCH
1078 hoSuccessOutgoingFirstInter number of successful outgoing
inter--bss handovers on TCH to the
first cell from the list of eligible cells
1094 tcAllocated number of terrestrial circuit
allocations in the BSC
1095 tcAveragedUsedMoy/Max/Cum average and maximum number of
/Ech terrestrial circuits allocated in the
BSC
1105 sccpAverageUsedMoy/Max/Cu average and maximum number of
m//Ech SCCP connections established in
the BSC
received by the BSC

411--9001--125

number
1197/1 channelActivateSpeechEnhanc number of channels activated for
edFullRate speech: Enhanced Full Rate
algorithm
1198 downlinkPowerCtrlMaxTchMoy/Ma duration of maximum downlink
x/Cum/Ech power use on busy TCHs
1199 uplinkPowerCtrlMaxTchMoy/M duration of maximum uplink power
ax/Cum/Ech use on busy TCHs
1200 hoNcellsExecution number of handovers on TCH
executed
the BSC to the MSC
1501 aTransparentDown number of DTAP messages sent by
the MSC to the BSC
by the MSC to the BSC
1600 connectionDurationTchMoy/Ma average duration and maximum
x/Cum/Ech duration of TCH/FR or preempted
or or
average duration and maximum
duration of TCH/FR or preempted
1609/0 tchFrAllocatedTchAllocationTrZ number of TCH/FR or preempted
one PDTCH allocated for traffic in the
1611/0 tchFrAveragedUsedTchAllocatio average number of TCH/FR FR or
nTrZoneMoy/Max/Cum/Ech preempted PDTCH used for traffic in
MS on the cell
or or
the cell


number
BTS on the cell
or or
the cell
MS on the cell
or or
the cell
BTS on the cell
or or
the cell
1705/n channelActivateTchFrDataTx (x number of TCH/FR activation for
[n = 0 to = 16 to 14400 b/s) transparent data service with a
[n = 0 to (x = 6 to 14500 b/s) non transparent data service with a
1709 channelActTchFrDataT number of channel activation for
transparent data service on TCH/FR
1710 channelActTchFrDataNT number of channel activation for
non transparent data service on
TCH/FR
or or
or or
tchFrAveragedUsedTrZoneMoy/M average number of TCH/FR or
ax/Cum/Ech preempted PDTCH used in the inner

411--9001--125

number
1776 hoRequiredTch number of handovers on TCH required
1780 hoSuccessOutgoingTch number of successful outgoing
handovers from the cell
1781 hoSuccessfulIncomingTch number of successful incoming
handovers in the cell
management
management
management
management
1809/n timingAdvanceAverage [for average timing advance value for
[n= 0 to 1] n=0] the communication in the cell or
or average timing advance value for
timingAdvanceAverageTrZone the communication in the inner or
[for n=0] outer zone of the cell or
timingAdvanceMaximum [for the communication in the cell or
n=1] maximum timing advance value for
timingAdvanceMaximumTrZon outer zone of the cell
e [for n=1]
1812 allocatedCircuitTsMoy/Max/Cu number of TS allocations for traffic
m/Ech in circuit mode in the cell
or or
allocatedCircuitTsTrZoneMoy/Ma number of TS allocations for traffic
x/Cum/Ech in circuit mode in the inner or the
1839/n hoNcellsRequestOutgoingXxx number of outgoing intra--bss or
[n=o to 9] inter--bss handover attempts from a
central cell to a neighboring one:
Cause Xxx
1840/n hoNcellsSuccessOutgoingXxx number of outgoing intra--bss or
[n=o to 9] inter--bss handover successes from
a central cell to a neighboring one:
Cause Xxx

2.4.6 Directed retry handover procedure

The following diagram describes the case where the BSC asks the BTS for a list of
neighbor cells. It does not describe directed retry handovers in microcells.
Data Flow Diagram: directed retry handover procedure (successful completion with
communication on SIGNALLING phase)
MS BTS BSC MSC

ASSIGNMENT_REQUEST
1107 (1)
1503
1841/0
1616/n
QUEUEING
1108
1502
1094 Set timer T11
1095 (2)
Set timer Tcnx CONNECTION_STATE_REQUEST

(3) Reset timer T11
CONN_STATE_REQ_ACK
Reset timer Tcnx
HANDOVER_INDICATION
(4)
1776
1138/n (5)

(2) There are no TCH resources available. Downlink DTAP service is resumed.
(3) The message CONNECTION_STATE_REQUEST is sending with e request type value equal to
0x00 = Directed retry.
(4) The HANDOVER_INDICATION message is sending by the BTS with and hanover cause value
equal to Directed retry (0=x0A).
(5) After that, the process is identical to an handover intra--BSS or inter--BSS following the preferred
cell list sending by the L1M BTS.

number
1094 tcAllocated number of terrestrial circuit allocations
in the BSC
1095 tcAveragedUsedMoy/Max/C average and maximum number of
um//Ech terrestrial circuits allocated in the BSC

411--9001--125

number
received by the BSC
the BSC
1138/n hoRequiredTchCauseXxx number of handovers on TCH
[n= 0 to 16] required: CauseXxx
1616/n tchAveragedQueueLengthHi number of queued TCH requests with
[n= 0 to 1] ghPriorityMoy/ the highest priority in the cell
Max/Cum/Ech [for n=0] number of queued TCH requests with
an internal priority different than the
tchAveragedQueueLengthOt highest one
herPriorityMoy/Max/Cum/Ec
h [for n=1]
required
1841/0 assignRequestSdcchToTchC number of assignment request
hannel messages received: modification from
an SDCCH channel to a TCH channel

2.5 Resource release
2.5.1 Radio channel release

The BSC supports several radio channel release procedures.
The following procedure performs a “clean” break on the currently used dedicated
channel and uses timers T3111 and T3109.
T3109 is only used when the DEACTIVATE SACCH ACK message is received
before the RELEASE INDICATION message.

411--9001--125
2.5.1.1 DEACTIVATE SACCH ACK received before RELEASE INDICATION
Data Flow Diagram: Radio channel release procedure (release indication first with
MS BTS BSC MSC

CHANNEL_RELEASE
CHANNEL_RELEASE
DEACTIVATE_SACCH
Set timer TDeacAck
DISC
1095 (--1)
RELEASE_INDICATION
UA
1198
1199
1600
1622
1623
1624
1625
1626
1805 (1)
1806 (1)
1807 (1)
1808 (1)
1809/n (1)
DEACTIVATE_ACK Reset timer TDeacAck
timer T3111
RF_CHANNEL_RELEASE
Timer T3111 expires
Set timer TrfAck
Reset timer TrfAck
1607 (--1) DISCONNECT_INDICATION
1105 (--1)


number
1095 tcAverageUsedMoy/Max/Cu average number of terrestrial circuits
m/Ech used
1105 SccpAverageUsedMoy/Max/ average number of SCCP
Cum/Ech connections established
1600 connectionDurationTchMoy/M average duration and maximum
ax/Cum/Ech duration of TCH/FR or preempted
or or
connectionDurationTchTrZone average duration and maximum
Moy/Max/Cum/Ech duration of TCH/FR or preempted
1607 sdcchAllocatedUsedTrZoneM average number of SDCCHs used in
oy/Max/Cum/Ech the inner or outer zone of the cell
1622 msLostMeasurements number of MS measurements
or or
msLostMeasurementsTrZon number of MS measurements
e messages not received by the inner
of the outer zone of the cell
measurements performed by the MS
in the cell
or or
or in the cell
rxLevUpLinkTrZone or
sum of downlink signal strength
or in the cell
rxQualDownLinkTrZone or
sum of downlink signal quality

411--9001--125

number
in the cell
or or
controls ordered by the L1M
1809/n timingAdvanceAverage [for average timing advance value for the
[n=0 to 1] n=0] communication in the cell or
or average timing advance value for the
timingAdvanceAverageTrZo communication in the inner or outer
ne [for n=0] zone of the cell
or or
timingAdvanceMaximum [for maximum timing advance value for
n=1] the communication in the cell or
timingAdvanceMaximumTrZ the communication in the inner or
one [for n=1] outer zone of the cell

2.5.1.2 RELEASE INDICATION received before DEACTIVATE SACCH ACK
Data Flow Diagram: Radio channel release procedure (deactivate SACCH Ack with
MS BTS BSC MSC

CHANNEL_RELEASE
CHANNEL_RELEASE
DEACTIVATE_SACCH
Set timer TDeacAck
DISC
UA
1601
1602
1603
1622
1623
1624
1625
1626
1805 (1)
1806 (1)
1807 (1)
1808 (1)
1809/n (1)
DEACTIVATE_ACK Reset timer TDeacAck
timer T3109
RELEASE_INDICATION Reset timer T3109

timer T3111
RF_CHANNEL_RELEASE Timer T3111 expires

Set timer TrfAck
RF_CHANNEL_RELEASE_ACK Reset timer TrfAck
1105 (--1)

411--9001--125

number
1105 SccpAverageUsedMoy/Max/Cum average number of SCCP
/Ech connections established
1601 downlinkPowerCtrlMaxSdcchMoy/ duration of maximum downlink
Max/Cum/Ech power use on busy SDCCHs
1602 uplinkPowerCtrlMaxSdcchMoy/M duration of maximum uplink power
ax/Cum/Ech use on busy SDCCHs
1603 connectionDurationSdcchTrZoneMoy/ connection duration of SDCCHs
Max/Cum/Ech
1607 sdcchAllocatedUsedTrZoneMoy/M average number of SDCCHs used
ax/Cum/Ech in the inner or outer zone of the
cell
1622 msLostMeasurements number of MS measurements
or or
msLostMeasurementsTrZone number of MS measurements
messages not received by the
inner of the outer zone of the cell
MS in the cell
or or
MS in the inner or outer zone of
the cell
MS in the cell
or or
rxLevUpLinkTrZone sum of downlink signal strength
the cell
MS in the cell
or or
the cell


number
MS in the cell
or or
the cell
1809/n timingAdvanceAverage [for average timing advance value for
[n=0 to 1] n=0] the communication in the cell
or or
timingAdvanceAverageTrZone average timing advance value for
[for n=0] the communication in the inner or
timingAdvanceMaximum [for outer zone of the cell
or the communication in the cell
timingAdvanceMaximumTrZone or
[for n=1] maximum timing advance value for
the communication in the inner or

411--9001--125
2.5.2 Connection release
The procedures use the following counters: tcAveragedUsed and

sccpAveragedUsed.
2.5.2.1 Release requested by the MSC (Communication on TRAFFIC phase)
MS BTS BSC MSC

CLEAR_COMMAND
1107
1503
1753
1164/20 CLEAR_COMPLETE
1095 (--1)
1108
CHANNEL_ACTIVATE 1502
CHANNEL_RELEASE
DEACTIVATE_SACCH
Set timer TDeacAck
STOP_MEASUREMENT
1198 (1)
1199
1600
1622
1624
1625
1626
1805
1806
1807
1808
1809/n
DEACTIVATE_SACCH_ACK
Set timer TDeacAck
RELEASE_INDICATION
Set timer TrfAck
DISC
UA Reset timer TrfAck

RF_CHANNEL_RELEASE
timer T3111
Reset timer T3111
1812 (2) DISCONNECT_INDICATION
1746 (3)
1611/0 (4) 1105 (5)

if the BTS reports measurement counters, the BSC increments counters 1198, 1499,
1600, 1622, 1623, 1624, 1625, 1626, 1805, 1806, 1807 and 1809/n
(2) 1812 is decremented.
(3)When the deallocation of TCH happens, 1746 is decremented.
(5)When the release of SCCP connection happens, 1105 is decremented.

number

Cum//Ech used
1105 sccpAveragedUsedMoy/Max/ average number of SCCP connections

Cum/Ech established
1108 aOutputMessage number of BSSAP messages sent by the

BSC to the MSC
1164/20 trafficReleaseClearCommand number of communications in traffic

phase released: CLEAR COMMAND
message received
1198 downlinkPowerCtrlMaxTchMoy/ duration of maximum downlink power use

Max/Cum/Ech on busy TCHs
1199 uplinkPowerCtrlMaxTchMoy/ duration of maximum uplink power use


the BSC to the MSC
1600 connectionDurationTchMoy/ average duration and maximum duration

Max/Cum/Ech of TCH/FR or preempted PDTCH con-
nections in the cell
or or
connectionDurationTchTrZone- average duration and maximum duration
Moy/Max/Cum/Ech of TCH/FR or preempted PDTCH con-
nections in the inner or outer zone of the
cell
1611/0 tchFrAveragedUsedTchAlloca- average number of TCH/FR or pre-

tionTrZoneMoy/ empted PDTCH used for traffic in the
Max/Cum/Ech inner of outer zone of the cell

411--9001--125

number

or or

surements received (non--concentric cell)
or or

or or
1625 rxQualDownLink sum of downlink signal quality measure-

or or
rxQualDownLinkTrZone sum of downlink signal quality measure-

or or
1746 tchFrAveragedUsedMoy/Max/ average number of TCH/FR used in the

Cum/Ech cell
or or
tchFrAveragedUsedTrZone- average number of TCH/FR used in the
Moy/Max/Cum/Ech inner or outer zone of the cell
1754 trafficRelease number of releases while the commu-

nication is in traffic phase
1805 msPowerIncControl number of MS increment power controls

ordered by the Layer 1 management
1806 msPowerDecControl number of MS decrement power controls

1807 bsPowerIncControl number of BS increment power controls

1808 bsPowerDecControl number of BS decrement power controls



number
1809/n timingAdvanceAverage for average timing advance value for the

[n= 0 to 1] n=0 communication in the cell
or or
timingAdvanceAverageTr- average timing advance value for the
Zone for n=0 communication in the inner or outer zone
timingAdvanceMaximum for of the cell
n=1 maximum timing advance value for the
or communication in the cell or
timingAdvanceMaximumTr- maximum timing advance value for the
Zone for n=1 communication in the inner or outer zone
of the cell
1812 allocatedCircuitTsMoy/Max/ Number of TS allocations for traffic in cir-

Cum/Ech cuit mode in the cell
or or
allocatedCircuitTsTrZoneMoy/ number of TS allocations for traffic in cir-
Max/Cum/Ech cuit mode in the inner or the outer zone
of the concentric cell

411--9001--125
2.5.2.2 Release requested by the MSC (Communication on SIGNALLING phase)
MS BTS BSC MSC

CLEAR_COMMAND
1107
1503
1753
1163/20 CLEAR_COMPLETE
1108
1502
CHANNEL_RELEASE
CHANNEL_RELEASE 1044
1045
DEACTIVATE_SACCH
Set timer TchncAck
STOP_MEASUREMENT
1601 (1)
1602
1603
1622
1623
1624
1625
1626
1805
1806
1807
1808
DISC Reset timer TchnAck
RELEASE_INDICATION
UA timer T3111
RF_CHANNEL_RELEASE Reset timer T3111

Set timer TrfAck
Reset timer TrfAck
DISCONNECT_INDICATION
1607 (--1)
1105 (--1)
(1)When the STOP_MEASUREMENT message for the SDCCH channel is

received, if the BTS reports measurement counters, the BSC increments counters
1601, 1602, 1603, 1622, 1623, 1624, 1625, 1626, 1805, 1806, 1807 and 1808.


number
1044 signallingPhaseDurationMoy/ average time of a signaling channel sei-

Max/Cum/Ech zure
1045 signallingPhaseDurationHigh- average time of a signaling channel sei-

Moy/Max/Cum/Ech zure > 25s
1105 sccpAveragedUsedMoy/Max/ average number of SCCP connections

Cum/Ech established

BSC to the MSC
1163/20 signallingReleaseBtsClear- number of communications in signalling

Command phase released: CLEAR COMMAND
received

the BSC to the MSC
1503 aNonTransparentDown number of BSSMAP messages received

by the BSC from the MSC
1601 downlinkPowerCtrlMaxSdc- duration of maximum downlink power use

chMoy/Max/Cum/Ech on busy SDCCHs
1602 uplinkPowerCtrlMaxSdcchMoy/ duration of maximum uplink power use

Max/Cum/Ech on busy SDCCHs
1603 connectionDurationSdcchMoy/ connection duration of SDCCHs (concen-

Max/Cum/Ech tric cell)
or or
connectionDurationSdcchTrZo- connection duration of SDCCHs (non--
neMoy/Max/Cum/Ech concentric cell)
1607 sdcchAveragedUsedTrZone- average number of SDCCHs used in the


or or

411--9001--125

number

surements received (non--concentric cell)
or or

or or

or or

or or
1753 signallingReleaseBts number of releases while the commu-

nication is in “signalling phase” and a cell





2.5.2.3 Release requested by the BSC (Communication on TRAFFIC phase)
MS BTS BSC MSC

CLEAR_REQUEST
Set timer TclrCMD
CLEAR_COMMAND
Reset timer TclrCMD
1107
1503
1753
1164/20
1095 (--1)
CLEAR_COMPLETE
1108
CHANNEL_RELEASE
DEACTIVATE_SACCH
Set timer TDeacAck
STOP_MEASUREMENT
DISC
UA 1198 (1)
1199
1600
1622
1623
1624
1625
1626
1805
1806
1807
1808
1809/n
Reset timer TDeacAck
RELEASE_INDICATION
Set timer T3111
RF_CHANNEL_RELEASE Reset timer T3111

Set timer TrAck
RF_CHANNEL_RELEASE_ACK Reset timer TrAck

1812 (2) DISCONNECT_INDICATION
1746 (3)
1611/0 (4) 1105 (5)

411--9001--125
if the BTS report measurement counters, the BSC increments counters 1198, 1199,
1600, 1622, 1623, 1624, 1625, 1626, 1805, 1806, 1807 , 1808 and 1809/n
(3) When the deallocation of TCH happens, 1746 is decremented.
(5) When the release of SCCP connection happens, 1105 is decremented.

number
1095 tcAveragedUsedMoy/Max/C average number of terrestrial circuits
um//Ech used
1105 sccpAveragedUsedMoy/Max average number of SCCP
/Cum/Ech connections established
received
the BSC to the MSC
1164/20 trafficReleaseClearComman number of communications in traffic
d phase released: CLEAR COMMAND
message received
1600 connectionDurationTchMoy/M connection duration of TCH/FR or
ax/Cum/Ech preempted PDTCH in the cell
or or
connectionDurationTchTrZone connection duration of TCH/FR or
Moy/Max/ preempted PDTCH in the inner of
Cum/Ech outer zone of the cell
1611/0 tchFrAveragedUsedTchAllocati average number of TCH/FR or
onTrZoneMoy/Max/Cum/Ech preempted PDTCH used for traffic in
the inner of outer zone of the cell
or or
msLostMeasurementsTrZon number of MS measurement
e messages not received by the inner or


number
or or
or or
or or
zone of the cell
or or
zone of the cell
1746 tchFrAveragedUsedMoy/Ma average number of TCH/FR or
x/Cum/Ech preempted PDTCH used in the cell
or or
tchFrAveragedUsedTrZoneM average number of TCH/FR or
oy/Max/Cum/Ech preempted used in the inner or outer
zone of the cell
1754 trafficRelease number of releases while the
communication is in traffic phase
management
management
management
management

411--9001--125

number
1809/n timingAdvanceAverage [for average timing advance value for the
[n= 0 to 1] n=0] communication in the cell or
or average timing advance value for the
timingAdvanceAverageTrZo communication in the inner or outer
ne [for n=0] zone of the cell or
timingAdvanceMaximum [for the communication in the cell or
timingAdvanceMaximumTrZ outer zone of the cell
one [for n=1]
or or
allocatedCircuitTsTrZoneMo number of TS allocations for traffic in
y/Max/Cum/Ech circuit mode in the inner or the outer

2.5.2.4 Release requested by the BSC (Communication on SIGNALLING phase)
MS BTS BSC MSC

CLEAR_REQUEST
Set timer TclrCMD
1108
1502
CLEAR_COMMAND
Reset timer TclrCMD
1107
1503
1753
1163/20
CLEAR_COMPLETE
1108
1044
DEACTIVATE_SACCH
Set timer TchnAck
STOP_MEASUREMENT
DISC
UA
1601 (1)
1602
1603
1622
1623
1624
1625
1626
1805
1806
1807
1808
Reset timer TchnAck
RELEASE_INDICATION
Set timer T3111
RF_CHANNEL RELEASE Reset timer T3111

Set timer TrAck
RF_CHANNEL_RELEASE_ACK Reset timer TrAck

1105 (--1)

received, if the BTS reports measurement counters, the BSC increments counters
1601, 1602, 1603, 1622, 1623, 1624, 1625, 1626, 1805, 1806, 1807 and 1808.

411--9001--125

number
Max/Cum/Ech seizure
1045 signallingPhaseDurationHighM average time of a signaling channel
oy/Max/Cum/Ech seizure > 25s
received
the BSC to the MSC
1163/20 signallingReleaseBtsClearC number of communications in
ommand signalling phase released: CLEAR
COMMAND received
received by the BSC from the MSC
1602 uplinkPowerCtrlMaxSdcchMo duration of maximum uplink power
y/Max/Cum/Ech use on busy SDCCHs
1603 connectionDurationSdcchMo connection duration of SDCCHs in the
y/Max/Cum/Ech cell
or or
connectionDurationSdcchTr connection duration of SDCCHs in the
ZoneMoy/Max/ inner or the outer zone of the cell
Cum/Ech
1607 sdcchAveragedUsedTrZone average number of SDCCHs used in
Moy/Max/Cum the inner or outer zone of the cell
/Ech
or or
msLostMeasurementsTrZon number of MS measurement
e messages not received by the inner or
or or


number
or or
or or
zone of the cell
or or
zone of the cell
communication is in “signalling phase”
and a cell associated to the
communication
management
management
management
management

411--9001--125
2.6 SMS service

The SMS service uses a SAPI 3 session that is opened when the mobile is stable on
a SDCCH or TCH using a SAPI 0 session.
A communicating mobile can send a request to open a SAPI 3 session at any time.
The initial setup procedure described in the following diagram is exactly the same
as the immediate assignment procedure, but, in this case, the ESTABLISH
INDICATION message contains the information “short message”.

2.6.1 SMS established by the MS
MS BTS BSC MSC

CHANNEL_REQUIRED
CHANNEL_REQUIRED
1748
1191/n
1746
1606
1607
CHANNEL_ACTIVATE
Set timer TchnAck
1629
Reset timer TchnAck
CHANNEL_ACTIVATE
Set timer T3111
IMMEDIAT_ASSIGN
1749
SABM 1192/n
UA Reset timer T3111
1750
1193/n
1196 CONNECTION_REQUEST
1108
CONNECTION_CONFIRM
START_MEASUREMENT_REQUEST_ACK
DTAP
(CM_SERVICE_ACCEPT)
1107
1501
CM_SERVICE_ACCEPT
SABM (SAPI 3)
ESTABLISH_INDICATION (SAPI 3)
UA
1621 DTAP (CP_DATA)
DTAP (CP_DATA)
1107
1501

number
1104/0 sccpAlloccated number of SCCP connections for

411--9001--125

number
received
the BSC to the MSC
[n= 0 to 7] requests: Cause Xxx
1192/n immediateAssignmentSucce number of successful immediate
[n= 0 to 7] ssCauseXxx assignments:
Cause Xxx
1193/n estabIndicSignallingCauseX number of ESTABLISH INDICATION
[n= 0 to 3] xx messages in establishment phase
Cause Xxx
1196 estabIndicSigPhase2 number of ESTABLISH INDICATION
by the BSC
1607 sdcchAllocatedUsedTrZoneM average and maximum number of
zone of the cell
1621 sapi3SessionEstablishment number of sessions established for
SMS to satisfy a short message
broadcast request in the cell
1749 immediateAssignmentSucce number of successful immediate
ss assignments
received

2.6.1.1 SMS established by the MSC

number
received
sent by the BSC to the MSC
1621 sapi3SessionEstablishment number of sessions established
for SMS to satisfy a short
message broadcast request in
the cell

411--9001--125
2.7 GPRS
2.7.1 Nominal procedure (in the case of Mobile Originating Call)
The GPRS procedure described in the following diagram is the normal completion
of the preemption on PDTCH (in the case of Mobile Originating Call).
MS BTS BSC PCU MSC
CHANNEL_REQUIRED
1748
1702
1191/n
1730
1606
1607
1744
1746
1609/2
1611/2
CHANNEL_ACTIVATE
Set timer TchnAck
1629/0
Reset timer TchnAck
IMMEDIATE_ASSIGNMENT_CMD
Set timer T3101
IMMEDIATE_ASSIGN
1749
SABM 1192/n
ESTABLISH_INDICATION Reset timer T3101
UA 1750
1193/n
1195 or 1196
CONNECTION REQUEST (L3 INFORMATION)
1108
1502
CONNECTION_CONFIRM
1105
1104/0
DTAP (AUTHENTIFICATION_REQUIRED)
DATP (AUTH_REQUIRED)
AUTH_REQUIRED 1107
1501
AUTH_RESPONSE
DTAP (AUTH_RESPONSE) DTAP (AUTHENTIFICATION_RESPONSE)
1108
1500

MS BTS BSC PCU MSC
SETUP
SETUP
SETUP
1108
1500 DTAP (CALL_PROCEEDING)
1107
1501
DTAP (CALL_PROCEEDING)
CALL_PROCEEDING
DTAP (ALERTING)
ALERTING
DTAP (ALERTING)
1107
1501
ASSIGNMENT_REQUEST
1107
1503
1841/0
1094
1095
1744
1746
1609/0
1611/0 TDMA_TS_STATUS
TDMA_TS_STATUS_ACK
(1)
1814
1813
CONN_STATE_REQ 1812
CONN_STATE_REQ_ACK

411--9001--125
MS BTS BSC PCU MSC

CHANNEL_ACTIVATE
Set timer TchnAck
1197/0 or 1197/1
or 1709 and 1705/n (2)
or 1710 and 1707/n
Reset timer TchnAck
ASSIGNMENT_COMMAND
Set timer T3107
1049
1715
ASSIGNMENT_COMMAND
1601
1602
1603
1622
1623
1624
1625
1626
1805
1806
1807
SABM 1808
UA
1195 or 1196
ASSIGNMENT_COMPLETE
Reset timer T3107
ASSIGNMENT_COMPLETE 1050 ASSIGNMENT_COMPLETE
1716
1502
RF_CHANNEL_RELEASE
1044
1045
RE_CHANNEL_RELEASE_ACK
1607 (--1)
1717
1718
1719
1720
1721 ALERT
CONNECT
CONNECT_ACK

MS BTS BSC PCU MSC

CALL
DISCONNECT
RELEASE
RELEASE_COMPLETE
CLEAR_COMMAND
1107
1503
1754
1164/20
1095 (--1)
CLEAR_COMPLETE
1502
CHANNEL_RELEASE
DEACTIVATE_SACCH Set timer TDeacAck

STOP_MEASUREMENT_REQUEST 1198
DISC 1199
STOP_MEASUREMENT_REQ_ACK 1600
UA 1622
1623
1624
1625
1626
1805 (3)
1806 (3)
1807 (3)
1808 (3)
1809/n (3)
Reset timer TDeacAck
RELEASE_INDICATION
RF_CHANNEL_RELEASE Set timer TrfAck
Reset timer TrfAck
1812 (--1)
1746 DISCONNECT_INDICATION
1611 1105 (--1)
TDMA_TS_STATUS
TDMA_TS_STATUS
1813 (--1)
(1) Before sending the TDMA TS STATUS message, the BSC performs the
switching connection between Abis and Agprs interface.

411--9001--125
or 1710 and 1707/n (n=0 to 2) for non--transparent data

number
Max/Cum/Ech zure
1049 attempedTchFrSeizures number of TCH/FR assignment requests
assigned
1094 tcAllocated number of terrestrial links allocated
1095 tcAverageUsedMoy/Max/ average number of terrestrial circuits
Cum/Ech used
1104/0 sccpAlloccated number of SCCP connections for SSN
BSSMAP in the BSC
1105 sccpAverageUsedMoy/Max/ average number of SCCP connections
Cum/Ech established
1107 aInputMessage number of BSSAP messages received by
the BSC
BSC to the MSC
1164/20 trafficReleaseClearCommand number of communications in traffic
phase released: CLEAR COMMAND
message received
1191/n channelRequestCauseXxx number of channel allocation requests:
[n= 0 to 7] Cause Xxx
1192/n immediateAssignmentSuc- number of successful immediate assign-
[n= 0 to 7] cessCauseXxx ments: Cause Xxx
1193/n estabIndicSignallingCau- number of ESTABLISH INDICATION
[n= 0 to 3] seXxx messages in establishment phase
Cause Xxx


number
1197/0 channelActivateSpeechFull- number of channels activated for speech:
Rate Full Rate algorithm
1197/1 channelActivateSpeechFull- number of channels activated for speech:
Rate Enhanced Full Rate algorithm
1198 downlinkPowerCtrlMaxTch- duration of maximum downlink power use
Moy/Max/Cum/Ech on busy TCHs
1199 uplinkPowerCtrlMaxTchMoy/ duration of maximum uplink power use
1500 aTransparentUp number of DTAP messages sent by the
BSC to the MSC
1501 aTransparentDown number of DTAP messages received by
the BSC
the BSC to the MSC
1600 connectionDurationTchMoy/ average duration and maximum duration
Max/Cum/Ech of TCH/FR or preempted PDTCH con-
nections in the cell
or or
connectionDurationTchTrZo- average duration and maximum duration
neMoy/Max/Cum/ of TCH/FR or preempted PDTCH con-
Ech nections in the inner or outer zone of the
cell
1602 uplinkPowerCtrlMaxSdc- duration of maximum uplink power use
SdcchTrZoneMoy/Max/Cum/
Ech
1606 sdcchAllocatedTrZone number of SDCCH allocated in the inner
1607 sdcchAllocatedUsedTrZone- average number of SDCCHs used in the
1609/2 tchFrAllocatedOverflowAl- number of TCH/FR allocated in the inner
locationTrZone or outer zone of the cell because of
SDCCH unavailability
1611/2 tchFrAveragedUsedOverflo- average and maximum number of TCH/
wAllocationTrZoneMoy/Max/ FR used in the inner or outer zone of the
Cum/Ech cell because of SDCCH unavailability

411--9001--125

number
1622 msLostMeasurements number of MS measurements messages
not received by the cell
or or
msLostMeasurementsTrZone number of MS measurements messages
not received by the inner or outer zone of
the cell
surements performed by the MS in the
cell
or or
ments performed by the MS in the cell
or or
ments performed by the MS in the inner
or or
rxQualDownLinkTrZone sum of uplink signal strength measure-
ments performed in the inner or outer
zone of the cell
or or
ments performed in the inner or outer
zone of the cell
1629/0 channelActivateSignallingFull- number of Full--Rate channels activated
Rate for signaling
1702 channelRequestExtended number of channels requested with a tim-
ing advance greater than 63
1705/n channelActivateTchFrDatax (x number of TCH/FR activation for trans-
[n = 0 to 6] = 16 to 14400 b/s) parent data service with a transmission
rate = x
1707/n channelActivateTchFrNDatax number of TCH/FR activation for non
[n = 0 to 2 (x = 6 to 14500 b/s) transparent data service with a transmis-
sion rate = x
1709 channelActivateTchFrData number of channel activation for trans-
parent data service on TCH/FR
1710 channelActivateTchFrNData number of channel activation for non
transparent data service on TCH/FR


number
1715 attemptedTchFrSeizu- number of attempts of assignation of a
resMsDualb TCH/FR or preempted PDTCH for dual-
band mobiles
1716 successfulTchFrSeizu- number of successful TCH/FR or pre-
resMsDualb empted PDTCH assignations for dual-
band mobiles
1717 abisTrauFrameDlReceived number of frames TRAU downlink
received
1718 abisTrauFrameDlCorrected number of frames TRAU downlink cor-
rected
1719 abisTrauFrameDlMuted number of frames TRAU downlink that
can not be corrected
1720 radioFrameUlReceived number of radio frames uplink received
1721 ECU_Activation number of erroneous frames (ECU may
be activated or not)
1730 pagingResponse number of responses to paging requests
in the cell
or or
zone of the cell
or or
1749 immediateAssignmentSuc- number of successful immediate assign-
cess ments
received
1754 trafficRelease number of releases while the commu-
nication is in traffic phase
ordered by the L1M
ordered by the L1M
ordered by the L1M

411--9001--125

number
ordered by the L1M
1809/n timingAdvanceMaximum maximum timing advance value for the
[n= 0 to 1] communication in the cell
or or
timingAdvanceMaximumTr- maximum timing advance value for the
Zone communication in the inner or outer zone
of the cell
1812 allocatedCircuitTsMoy number of TS allocations for traffic in cir-

cuit mode in the cell
or or
allocatedCircuitTsTrZoneMoy number of TS allocations for traffic in cir-
cuit mode in the inner or the outer zone
of the concentric cell
1813 allocatedPacketTsMoy/Max/ number of TS allocations for packet
Cum/Ech mode in the cell
or or
allocatedPacketTsTrZone- number of TS allocations for packet
Moy/Max/Cum/Ech mode in the inner or the outer zone of the
cell
1814 gprsPreemption number of GPRS preemption successes
1841/0 assignRequestSdcchToTch- number of assignment request messages
Channel received: modification from an SDCCH to
a TCH channel

2.7.2 GPRS procedure: no resource available for a PDTCH preemption
Data Flow Diagram: GPRS procedure (no available resource for a PDTCH
preemption)
MS BTS BSC PCU MSC

ASSIGNMENT_REQUEST
1107
1503
1841/0
1094
1095
1744
1744
1746
1609/0
1611/0
TDMA_TS_STATUS
TDMA_TS_STATUS_ACK
1613
(1)
1815
1746 (--1)
1611/0 (--1)
1842/0
1095 (--1)
ASSIGNMENT_FAILURE
1108
1502

411--9001--125
(1) : The internal counter 1057, allTchFrAllocatedTimeMoy/Max/Cum/Ech

(average and maximum duration during which all TCH/FR resources and PDTCH
resources configured as preemptable are used in the cell) is incremented after a
preemption nack. Two cases are to be considered:
In a cell with no resource PDTCH configured :
• When all TCH--FR resources are used, the measurement is started (when the
allocator sends an ASSIGNMENT FAILURE message)
• When a TCH--FR resource is free, the measurement is stopped and the timer
1057 is incremented by the value of the measurement
In a cell with PDTCH resources configured (all TCH--FR resources are used and
there is a PDTCH pre--emptable):
• A new request for a TCH/FR is received by the BSC => a GPRS preemption
procedure is launched and the PCU sends a TDMA_TS_STATUS_NACK.
.At this time, the measurement is started.
• The measurement is stopped as soon a resource is released or as soon the timer
GprsPreemptionProtection elapses. The counter 1057 is incremented by the
value of the measurement.

number
Cum/Ech used
BSC to the MSC
the BSC to the MSC
TrZone PDTCH allocated for traffic in the inner of
1611/0 tchFrAveragedUsedTchAl- average number of TCH/FR or pre-
locationTrZoneMoy/Max/ empted PDTCH used for traffic in the
Cum/Ech inner or outer zone of the cell
1613 tchFrRessourceFailureTrZone number of TCH/FR or preempted
PDTCH allocation failures in the inner or


number
or or
zone of the cell
or or
Moy/Max/Cum/Ech empted PDTCH used in the zone (con-
centric cell)
1815 gprsPreemptionNack number of GPRS preemption failures
(requests non acknowledged by the
PCU)
a TCH channel
modification from an SDCCH channel to
a TCH channel

411--9001--125
2.7.3 GPRS procedure: negative acknowledgement by the PCU

for a PDTCH preemption
MS BTS BSC PCU MSC
ASSIGNMENT_REQUEST
1107
1503
1841/0
1094
1095
1744
1746
1609/0
1611/0 TDMA_TS_STATUS
TDMA_TS_STATUS_ACK (1)
1613
1815
1746 (--1)
1611/0 (--1)
ASSIGNMENT_FAILURE
1842/0
1095 (--1)
1108
1502
CLEAR_COMMAND
1107
1503
1753
1163/20
CLEAR_COMPLETE
1108
1502
1044
1045
CHANNEL_RELEASE
CHANNEL_RELEASE
DEACTIVATE_SACCH

MS BTS BSC PCU MSC
DISC
UA
1601
1602
1603
1623
1624
1625
1626
1805 (2)
1806 (2)
1807 (2)
1808 (2)
1809/n (2)
REACTIVATE_ACK
RELEASE_INDICATION
DEACTIVATE_SACCH
1607 (--1)
(1) When the BSC receives the TDMA TS STATUS NACK message with the error
cause, it aborts the current allocation procedure.

411--9001--125

number

Max/Cum/Ech zure


Cum/Ech used
1105 SccpAverageUsedMoy/Max/ average number of SCCP connections

Cum/Ech established

BSC to the MSC
1163/20 signallingReleaseBtsClear- number of communications in signaling

Command phase released: sequencing error

the BSC to the MSC


1602 uplinkPowerCtrlMaxSdc- duration of maximum uplink power use


SdcchTrZoneMoy/Max/Cum/
Ech
1607 sdcchAllocatedUsedTrZone- average number of SDCCHs used in the


TrZone PDTCH allocated for traffic in the inner of
1611/0 tchFrAveragedUsedTchAl- average number of TCH/FR or pre-

locationTrZoneMoy/Max/ empted PDTCH used for traffic in the
Cum/Ech inner or outer zone of the cell


number
1613 tchFrRessourceFailureTrZone number of TCH/FR allocation failures in

the zone (concentric cell)
1622 msLostMeasurements number of MS measurements messages

not received by the cell
or or
msLostMeasurementsTrZone number of MS measurements messages
not received by the inner of the outer
zone of the cell

or cell
rxLevDownLinkTrZone or
sum of downlink signal strength mea-

or or
rxLevUpLinkTrZone sum of downlink signal strength mea-

or or

or or

or or
zone of the cell

411--9001--125

number

or or
1753 signallingReleaseBts number of releases while the commu-

nication is in “signaling phase” and a cell

ordered by the L1M

ordered by the L1M

ordered by the L1M

ordered by the L1M
1815 gprsPreemptionNack number of GPRS preemption failures

(requests non acknowledged by the
PCU)

a TCH channel

modification from an SDCCH channel to
a TCH channel
2.7.4 Counter behavior when GPRS is activated

The following counter definition table lists the BTS and BSC counters taking into
account the type of radio channel resource (TCH or pre--empted PDTCH). Their
behavior is not influenced by GPRS activation.
The behavior of the other counters not listed in this table does not depend on channel
type (TCH full rate or pre--empted PDTCH).
As a consequence, GPRS has no impact on the other counters (for example
those for the handover). Their behavior is strictly the same with or without
GPRS activation.
Note: GPRS activation means enabling GPRS calls when GPRS is configured.

The counter definition table is made of five columns:

Counter: identifier of the counter
CCT: Circuit Calls on TCH Channel
• Concerns all circuit calls which will get a TCH traffic channel.
• Writing “y” means that those calls, at some point, will concern this counter.
Example: RACH access for Originating call will deserve a “y” because the
originating circuit call using a configured TCH Channel will have a RACH
that will be counted in counter C1027.
CCP: Circuit calls on PDTCH pre--empted.
• Concerns all circuit calls which will pre--empt a PDTCH Channel (to make a
TCH).
• Writing ”y” means that those calls, at some point, will concern this counter.
Example: RACH access for Originating call will deserve a “y” because the
originating circuit call using a reconfigured PDTCH Channel will have a
RACH that will be counted in counter C1027.
CP: Com Packet. Those necessarily take place on PDTCH channel.
Example: there will be a RACH access for those calls (“y” for RACH counters)
but no SDCCH assignment (“n” for SDCCH counters).
Note: contains comments, when necessary
Counter CCT CCP CP Note

1026 y y y This counter is computed at the BTS level; no distinction is made
between RACH dedicated to Circuit Calls or Packet Calls
between RACH dedicated to Circuit Calls or Packet Calls
between Paging dedicated to Circuit Calls or Packet Calls.
between RACH dedicated to Circuit Calls or Packet Calls.
1044 y y n The object identifier is used to set a mdCounterIdArray field.

411--9001--125

1057 y y n Number of milliseconds during which all the available TCH_FR
resources and pre--emptable PDTCH resources are used. This
counter starts measurement on allocation of all the available
TCH full rate and pre--emptable PDTCH resources of the CELL,
and stops as soon as a resource is free. As a result, its behav-
ior depends on the setting of gprsPreemption parameter at
the OMC--R side.
1084 y y y The object identifier is used to set a mdCounterIdArray field.
1086 n n y The object identifier is used to set a mdCounterIdArray field.
1104/0 y y n The object identifier is used to set a mdCounterIdArray field.



411--9001--125

1300 y y y OMC--R management
1400 y y y This counter gives the Real load of the processor. Note that the
load of a given BSC processor is impacted by GPRS messages
treated by this processor.
1504 y n n GSMR & GPRS can not be activated at the same time;
1505 y n n GSMR & GPRS can not be activated at the same time;


1609/n y y n Number of full rate TCH allocations. This counter includes
TCH/FR channel and preempted PDTCH for screenings 0 and 3.
1610 y y n Number of half rate TCH allocations.
1611 /n y y n Average and maximum number of full rate TCH or preempted
PDTCH allocations for screenings 0 and 3.
1619 y n n Measurement of interference is performed when in Idle mode;
before the pre--emption, the PDTCH is assigned to the PCU and
thus considered as used from the BSS side. During the pre--emp-
tion, the PDTCH is re--configured as TCH_FR and then assigned
to a Circuit Call. As a result, measurement of interferences
involves configured (static) TCH_FR only.
1700 y y n Number of available TS for circuit calls. Used resources are
counted as available. This counter is related to TCH_FR chan-
nel, pre--emptable PDTCH and PDTCH not allocated to
PCUSN.
1705 y y n This counter is related to TCH_FR & pre--empted PDTCH chan-
nel type (Circuit Call).
nel type (Circuit Call).

411--9001--125

1714 y n n Measurement of the duration of the overload situation in the cell:
_ when the number of free TCHs (this number does not take
into account pre--emptable PDTCH) is lower than a minimum
threshold,
_ or when the number of queued TCH requests is greater than a
threshold.
nel type (Voice Call); it gives the number of successful TCH
assignations for a dualband mobile.
1722 y n n GSMR & GPRS can not be activated at the same time.
1748 The object identifier is used to set a mdCounterIdArray field.


1800 y n n GSMR & GPRS cannot be activated at the same time.
1801 y y n

411--9001--125

1803/n y y n The object identifier is used to set a mdCounterIdArray field.
1812 y y n This counter gives the number of channels (TCH FR or PDTCH
pre--empted) allocated to circuit traffic. Type: load.
1813 y y n This counter gives the number of PDTCH channels given to the
PCU equipment. Type: load.
1814 n y n This counter gives the number of PDTCH pre--emption success.
1815 n y n This counter gives the number of PDTCH pre--emption failure,
i.e. not acknowledged by the PCU.
1834 y y y This counter is computed at the BSC level; In case of rejection,
no distinction is made between Channel Request message dedi-
cated to Circuit Calls or Packet Calls.
2001 n y y The object identifier is used to set a mdCounterIdArray field.


3000/n y y n Each counter has a value between 0 and 100.; the value 100
represents a 100% load.
3001/n y y n Each counter has a value between 0 and 100.; the value 100
represents a 100% load.
3004/n y y n Each counter has a value between 0 and 100 (the value 100
represents a 100% usage of the memory).
3005/n y y n Each counter has a value between 0 and 100 (the value 100
represents a 100% usage of the memory).
3008/n y y n The object identifier is used to set a mdCounterIdArray field.

411--9001--125
2.8 GPRS/EDGE Suspend and Resume

Two procedures are defined to suspend and resume the GPRS service during a CS
call:
Suspend/Resume, resume being done with Routing Area Update (RAU)
message (since V12). Refer to the two data flow diagrams presenting the nominal
case (Paragraph 2.8.1) and the failure case (Paragraph 2.8.2).
Suspend/Resume, resume being done with the Resume message (since V15:
Feature 25155: GPRS/EDGE Suspend and Resume).
• The procedure has to be activated using the “suspendResumeActivation” flag.
When it is de--activated or not supported, the first procedure is used instead.
• Every class B MS which is GPRS attached must suspend its GPRS service
when it enters dedicated mode (dedicated mode includes Circuit Calls and
also Location Area Update, SMS, etc.). When leaving dedicated mode, the
network can resume the GPRS service itself, thus avoiding the MS to send an
RAU to the PS domain, and thus saving PDTCH resources and CPU
occupancy in the PCUSN.
• Refer to the two data flow diagrams presenting the nominal case (Paragraph
2.8.3) and the failure case (Paragraph 2.8.4).

2.8.1 GPRS/EDGE Suspend procedure with RAU message

(nominal procedure)

number
2066 suspendRequest Number of GPRS suspension request

messages received by the BSC.

411--9001--125

number
2071/0 agprsSuspendRequestProcedures Number of PCU MS suspend

messages sent by the BSC to the
PCU. In case of multiple messages
relative to the same communication,
this counter is incremented only one
time per communication.
2071/1 agprsSuspendRequestMessages Number of PCU MS suspend

this counter is incremented every time
the message is sent on the Agprs.

2.8.2 GPRS/EDGE Suspend procedure with RAU message (failure case)

number


411--9001--125

number
2071/0 agprsSuspendRequestProce- Number of PCU MS suspend messages

dures sent by the BSC to the PCU. In case of
multiple messages relative to the same
communication, this counter is
incremented only one time per
communication.
2071/1 agprsSuspendRequestMes- Number of PCU MS suspend messages

sages sent by the BSC to the PCU. In case of
incremented every time the message is
sent on the Agprs.
2072 agprsSuspendNack Number of PCU MS suspend nack

received by the BSC from the PCU.


(nominal procedure)

411--9001--125

number

2067 resumeSuccess Number of successful resume

procedures.
2071/0 agprsSuspendRequestProce- Number of PCU MS suspend messages

dures sent by the BSC to the PCU. In case of
incremented only one time per
communication.
2071/1 agprsSuspendRequestMes- Number of PCU MS suspend messages

sages sent by the BSC to the PCU. In case of
incremented every time the message is
sent on the Agprs.
2073 agprsResumeRequest Number of PCU MS resume messages

sent by the BSC to the PCU.

(failure case)


411--9001--125

number
2066 suspendRequest Number of GPRS suspension

request messages received by the
BSC.
2068/0 resumeFailureAfterHOInterRA Number of times the BSC does not

perform a GPRS resume procedure
after a successful GPRS
suspension. The GPRS attached
MS has performed an inter RA
handover (intra--BSC).
2068/1 resumeFailureAfterHOInterBSC Number of times the BSC does not

perform a GPRS resume procedure
after a successful GPRS
suspension. The GPRS Attached
MS has performed an inter BSC
handover.
2071/0 agprsSuspendRequestProcedures Number of PCU MS suspend

this counter is incremented only one
time per communication.
2071/1 agprsSuspendRequestMessages Number of PCU MS suspend

this counter is incremented every
time the message is sent on the
Agprs.
2073 agprsResumeRequest Number of PCU MS resume

PCU.
2074 agprsResumeNack Number of PCU MS resume Nack

messages received by the BSC
from the PCU.

2.9 BSC equipment
2.9.1 CPUE overload

The process that detects CPUE processor overloads in the BSC is built around a
counter that tallies the accumulated cost of transaction processing for calls handled
by the BSC.
Call regulation is triggered when the counter crosses a given threshold value, and
is gradually applied as the BSC starts to refuse new calls according to four defined
priority levels.

411--9001--125
2.10 PCUSN
2.10.1 Flow control

The flow control procedure is initiated by the BSS. The flow control parameters
allow the SGSN to locally control its transmission output in the SGSN to BSS
direction. The SGSN shall perform flow control on each BVC (BVC flow control
mechanism) and on each MS (MS flow control mechanism).
Data Flow Diagram: BVC flow control and MS flow control mechanisms
MS PCUSN SGSN
LLC_DL_FRAME_MS1
15004/0
15005/0
LLC_DL_FRAME_MS2
15004/0
15005/0
LLC_DL_FRAME_MS3
15004/0
15005/0
BVC_FLOW_CONTROL_REQUESTS
15010/0
BVC_FLOW_CONTROL_ACK
LLC_DL_FRAME_MS4
15004/0
15005/0
LLC_DL_FRAME_MS4
15004/0
15005/0
LLC_DL_FRAME_MS4
15004/0
15005/0
MS4_FLOW_CONTROL_REQUESTS
15010/1
MS4_FLOW_CONTROL_ACK

List of counters incremented during this procedure:
Counter Counter name Function GPRS/

number EDGE
15004/0 pduDataDn number BSSGP DL--UNITDATA G/E

PDU received by the BVC
(SGSN-->PCU)
15005/0 octetsDataDn cumulative size (in bytes) of all the G/E

BSSGP DL--UNITDATA PDU
received by the BVC
(SGSN-->PCU). The size does not
include the FR and NS header
15010/0 bvcFlowControlReque number of BSSGP G/E

sts FLOW--CONTROL--BVC PDU
sent by the BVC (PCU-->SGSN)
15010/1 msFlowControlReque number of BSSGP G/E

sts FLOW--CONTROL--MS PDU sent
by the BVC (PCU-->SGSN)
2.10.2 LLC Discarded
This procedure is used by the BSS to indicated that a number of buffered

LLC--PDUs in a cell for an MS have been deleted inside the BSS.
Data Flow Diagram: Discard of LLC PDUs
MS PCUSN SGSN
LLC_DL_FRAME_MS1
15004/0
15005/0
LLC_DL_FRAME_MS1
15004/0
15005/0
LLC_DL_FRAME_MS1
15004/0
15005/0
BSSGP_DISCARDED_PDU
15012/0
15012/1

411--9001--125

number EDGE

(SGSN-->PCU)

received by the BVC
15012/0 llcDiscardedPdu Number of BSSGP G/E

LLC--DISCARDED PDU sent for
the BVC (PCU-->SGSN)
15012/1 llcDiscardedOctets Cumulative size (in bytes) of all G/E

the bytes discarded by the
BSSGP DISCARDED PDU sent
for the BVC ( the number of bytes
discarded is specified in the field
“number of octets affected”)

2.10.3 UL TBF Establishment: Normal Completion
The UL TBF establishment procedure is used by the mobile station to establish a

TBF to support the transfer of LLC PDUs in the direction from the MS to the
network.
Data Flow Diagram: Establishment of an UL TBF in two phases access with first
phase in CCCH
MS PCUSN SGSN
CHANNEL_REQUEST
15059/0
15058/0
PACKET_RESOURCE_REQUEST
15056/1
15047/0
PACKET_UPLINK_ASSIGNMENT
15047/1
PACKET_CONTROL_ACK
15047/0

number EDGE
15047/0 controlBlocksUp Cumulative number of RLC/MAC G

control blocks received in uplink
by the PCU on this TDMA. This
means all the valid RLC/MAC
control blocks received on the
Agprs and related to UL or DL
TBF.
15047/1 controlBlocksDn Cumulative number of RLC/MAC G

control blocks different from
Packet Downlink Dummy Control
Block sent by the PCU

411--9001--125

number EDGE
15056/1 packetResourceRequ Cumulative number of Packet G/E

est Resource Request messages
received by the PCU in this cell for
the second phase of an uplink
establishment
15058/0 upTbfImmediateAssig Cumulative number of Immediate G/E

nment Assignment Uplink messages sent
by the PCU to establish an UL
TBF in this cell. In the case of
CCCH management of the BTS,
this counter corresponds to the
cumulative values periodically
received from the BTS in the
CCCH information
15059/0 channelRequestCcch Cumulative number of RACH G/E

(Channel Request) received by
the PCU in this cell

2.10.4 UL TBF Establishment: UL TBF Establishment during DL transfer

The mobile station may request establishment of an uplink TBF during a downlink
TBF by including a Channel Request Description information element in the Packet
Downlink Ack/Nack message.
Data Flow Diagram: Establishment of an UL TBF during DL TBF
MS PCUSN SGSN
DL_DATA_BLOCK
15046/1
DL_DATA_BLOCK (POLLING)
15046/1
PACKET_DOWNLINK_ACK/NACK (1)
15049/1
15047/0
15034/0
PACKET_TIMESLOT_RECONFIG
15047/1
PACKET_CONTROL_ACK
15047/0
DL_DATA_BLOCK
15046/1
UL_DATA_BLOCK
15046/0
(1) Channel Request Description

411--9001--125

number EDGE
15034/0 PDANWithUlReq Cumulative number of Packet G/E

Downlink Ack/Nack messages,
with the Channel Request
Description included
15046/0 dataBlocksUp Cumulative number of RLC data G

blocks received by the PCU on
this TDMA. This means all the
valid RLC data blocks received on
the Agprs, including the
retransmitted and out of sequence
frames.
15046/1 dataBlocksDn Cumulative number of RLC blocks G

sent by the PCU on this TDMA.

TBF.

15049/1 packetAckNackDn Cumulative number of Packet G

Downlink Ack/Nack messages
received by the PCU on this
TDMA.

2.10.5 UL TBF Release: Normal Completion

The normal UL TBF release procedure occurs when the mobile station sends a RLC
data block with CV=0 while the BSS has correctly received all the UL RLC data
blocks.
Data Flow Diagram: Normal UL TBF release
MS PCUSN SGSN
UL_DATA_BLOCK (1)
15046/0
PACKET_UPLINK_ACK/NACK
15047/1
UL_DATA_BLOCK
15046/0
PACKET_UPLINK_ACK/NACK (2)
15047/1
PACKET_CONTROL_ACK
15033/0
15055/0
15047/0
(1) CV= 0
(2) FAI = 1

number EDGE
15033/0 upTbfReleases Cumulative number of UL TBF G/E

released in the cell (related to half
duplex or full duplex transfers).
This counter counts the normal
and abnormal releases due to loss
of communications, OAM event,
TS sharing event.

frames.

411--9001--125

number EDGE

TBF.

15055/0 tbfNormalReleaseUp Cumulative number of normal G/E

releases of UL TBFs (related to
half duplex or full duplex transfer).

2.10.6 Abnormal OL TBF Release: lossOfComNN0002

This abnormal release occurs when there is no progression of the received window
(no progression of V(Q) in UL).
Data Flow Diagram: Abnormal release of an UL TBF due to non progression of
V(Q)
MS PCUSN SGSN
UL_DATA_BLOCK
15046/0
PACKET_UPLINK_ACK/NACK (V(Q))
NN0002++
15047/1
UL_DATA_BLOCK
15046/0
UL_DATA_BLOCK
15046/0
NN0002++
15047/1
UL_DATA_BLOCK
15046/0
UL_DATA_BLOCK
15046/0
NN0002++
15047/1
UL_DATA_BLOCK
15046/0
UL_DATA_BLOCK
15046/0
NN0002++=NN0002Max
15057/0
15033/0
15047/1

411--9001--125

number EDGE

TS sharing event.

frames.

15057/0 lossOfComNN002Max Number of abnormal releases due G/E

to non progression of V(Q) in
uplink and V(A) in downlink. This
means the number of abnormal
releases with a mobile in uplink
TBF or downlink TBF because the
received or transmitted window
does not progress

2.10.7 Abnormal UL TBF Release (FULL Duplex): LossOfComNN0002

This abnormal release occurs when there is no progression of the received window
(non progression of V(Q) in UL).
Data Flow Diagram: Abnormal release of an UL TBF due to non progression of
V(Q) during full duplex transfer, in the case that DL TBF is also released.
MS PCUSN SGSN
DL_DATA_BLOCK
15046/1
UL_DATA_BLOCK
15046/0
NN0002++
15047/1
UL_DATA_BLOCK
15046/0
DL_DATA_BLOCK
15046/1
UL_DATA_BLOCK
15046/0
NN0002++
15047/1
UL_DATA_BLOCK
15046/0
DL_DATA_BLOCK
15046/1
UL_DATA_BLOCK
NN0002++
15046/0
15057/0 NN0002++=NN0002Max
15057/3
15033/0
15033/1
15047/1

411--9001--125

number EDGE

TS sharing event.
15033/1 dnTbfReleases Cumulative number of DL TBF G/E

TS sharing event.

frames.



does not progress
15057/3 lossOfComT3195 Number of downlink TBF G/E

abnormal releases due to non
response from the mobile during
the establishment procedure or
packet transfer

2.10.8 Abnormal UL TBF Release: N3101
This abnormal release occurs when the mobile station does not respond to USF.
Data Flow Diagram: Non response from the mobile station after N3101 scheduled
blocks (means with USF set in downlink)
MS PCUSN SGSN
DL_DATA_BLOCK (USF)
15046/1
UL_DATA_BLOCK
N3101++
DL_DATA_BLOCK (USF)
15046/1
UL_DATA_BLOCK
N3101++
DL_DATA_BLOCK (USF)
15046/1
UL_DATA_BLOCK
N3101++=N3101Max
15033/0
15057/1
15057/2

number EDGE

TS sharing event.


411--9001--125

number EDGE
15057/1 lossOfComT3169 Number of uplink TBF abnormal G/E

releases due to non response
from the mobile during the
establishment procedure or packet
transfer. In the case of full duplex
transfer, this also counts the
uplink TBF releases consecutive
to downlink TBF abnormal
release.
15057/2 lossOfComNT0001 Number of uplink TBF abnormal G/E

from the mobile to USF and
assignment messages

2.10.9 Abnormal UL TBF Release (FULL Duplex): N3101

This abnormal release occurs when the mobile station does not respond to USF.
Data Flow Diagram: Non response from the mobile station after N3101 scheduled
blocks (means with USF set in downlink) during full duplex transfer, in the case that
DL TBF is also released
MS PCUSN SGSN
DL_DATA_BLOCK
15046/1
UL_DATA_BLOCK
15046/0
DL_DATA_BLOCK
15046/1
UL_DATA_BLOCK
N3101++
UL_DATA_BLOCK
N3101++
UL_DATA_BLOCK
N3101++=N3101Max
15033/0
15057/1
15057/2
15057/3
15033/1

411--9001--125

number EDGE

TS sharing event

TS sharing event

frames

sent by the PCU on this TDMA

to downlink TBF abnormal release

assignment messages

packet transfer

2.10.10 Abnormal UL TBF Release: UP_NASSIGNMAX

This abnormal release occurs when the mobile station does not acknowledge uplink
assignment messages.
Data Flow Diagram: Non response from the mobile after UP_NASSIGNMAX
Packet Uplink Assignment messages
MS PCUSN SGSN
CHANNEL_REQUEST (RACH)
15059/0
15058/0
15056/1
15047/0
PACKET_UPLINK_ASSIGNMENT (POLLING)
15047/1
PACKET_CONTROL_ACK
Up_Nassign++
15047/1
PACKET_CONTROL_ACK
Up_Nassign++
15047/1
PACKET_CONTROL_ACK
Up_Nassign++
15047/1
PACKET_CONTROL_ACK
Up_Nassign++
15047/1
PACKET_CONTROL_ACK
Up_Nassign++=Up_NassignMax
15033/0
15057/1
15057/2
15036/0

411--9001--125

number EDGE

TS sharing event
15036/0 ulsecondPhaseRadio Cumulative number of abnormal G/E

Failure releases during second phase
uplink establishment (half duplex
transfer), due to radio link
problems

TBF


establishment

release.

assignment messages


number EDGE

by the PCU to establish and UL
TBF in the cell. In the case of
CCCH management at the BTS,
CCCH information.


411--9001--125
2.10.11 Abnormal UL TBF Release (FULL Duplex): UP_NASSIGNMAX
This abnormal release occurs when the mobile station does not acknowledge uplink
assignment messages.
Data Flow Diagram: No response from the mobile after UP_NASSIGNMAX

Packet Uplink Assignment messages during full duplex transfer, in the case that the
DL TBF is also released
MS PCUSN SGSN
DL_DATA_BLOCK
15046/1
15046/1
15047/0
15034/0
15047/1
PACKET_CONTROL_ACK
Up_Nassign++
15047/1
PACKET_CONTROL_ACK
Up_Nassign++
15047/1
PACKET_CONTROL_ACK
Up_Nassign++
15047/1
PACKET_CONTROL_ACK
Up_Nassign++
15047/1
PACKET_CONTROL_ACK
Up_Nassign++=Up_NassignMax
15033/0
15057/1
15057/2
15033/1
15057/3
(1) Channel Request Description


number EDGE

TS sharing event.

TS sharing event.
15034/0 PDANWithUlReq Cumulative number of Packet G/E

Downlink Ack/Nack messages,
with the Channel Request
Description included
15046/1 dataBlocksDn Cumulative number of RLC data G

blocks sent by the PCU on this
TDMA.

control blocks in uplink by the
PCU on this TDMA. This means
all the valid RLC/MAC control
blocks received on the Agprs and
related to UL or DL TBF.

Block sent by the PCU on this
TDMA

release.

411--9001--125

number EDGE

assignment messages

packet transfer

2.10.12 Abnormal UL TBF Release: N3103

This abnormal release occurs when the mobile station does not acknowledge the last
packet uplink ack/nack (with FAI=1).
Data Flow Diagram: Non response from the mobile after N3103 Packet Uplink
Ack/Nack sent with FAI=1
MS PCUSN SGSN
UL_DATA_BLOCK (1)
15046/0
15047/1
UL_DATA_BLOCK
15046/0
PACKET_UPLINK_ACK/NACK (FAI=1)
15047/1
PACKET__CONTROL_ACK
N3103++
15047/1
PACKET__CONTROL_ACK
N3103++
15047/1
PACKET__CONTROL_ACK
N3103++
15047/1
PACKET__CONTROL_ACK
N3103++=N3103Max
15033/0
15057/1
(1) CV= 0
(2) V(Q) <> V(R)

411--9001--125

number EDGE

TS sharing event.

frames.


release.

2.10.13 Abnormal UL TBF Release (FULL Duplex): N3103

packet uplink ack/nack (with FAI=1).
Data Flow Diagram: Non response from the mobile after N3103 Packet Uplink
Ack/Nack sent with FAI=1 during full transfer, in the case that the DL TBF is also
released
MS PCUSN SGSN
DL_DATA_BLOCK
15046/1
UL_DATA_BLOCK (1)
15046/0
15047/1
UL_DATA_BLOCK
15046/0
DL_DATA_BLOCK
15046/1
15047/1
PACKET_CONTROL_ACK
N3103++
15047/1
PACKET_CONTROL_ACK
N3103++
15047/1
PACKET_CONTROL_ACK
N3103++
15047/1
PACKET_CONTROL_ACK
N3103++=N3103Max
15033/0
15057/1
15057/3
15033/1
(1) CV= 0
(2) V(Q) <> V(R)

411--9001--125

number EDGE

TS sharing event.

TS sharing event.

frames.



release.

packet transfer

2.10.14 DL TBF Establishment: MS in Standby State
MS PCUSN SGSN
PAGING
CHANNEL_REQUEST (RACH)
15059/0
15058/0
15056/1
15047/0
15047/1
PACKET_CONTROL_ACK
15047/1
UL_DATA_BLOCK (PAGING RESPONSE)
15046/0 LLC_UL_FRAME
PACKET_TIMESLOT_RECONFIG (1) 15004/1

15005/1
15047/1
PACKET_CONTROL_ACK
15047/0
15047/1
PACKET_CONTROL_ACK
15047/1
DL_DATA_BLOCK
15046/1 LLC_DL_FRAME
15004/0
15005/0
15031/1
(1) Downlink pre--establishment
(2) FAI = 1

411--9001--125
For a mobile station in Standby State, the network may initiate the paging procedure
for downlink packet transfer in order to obtain the mobile station cell location for
the downlink packet transfer. The mobile station performs a page response by
sending and LLC PDU to the network.

number EDGE

(SGSN-->PCU)
15004/1 pduDataUp number BSSGP UL--UNITDATA G/E

PDU sent by the BVC
(PCU-->SGSN)

received by the BVC
15005/1 octetsDataUp cumulative size (in bytes) of all the G/E

received by the BVC
(PCU-->SGSN). The size does not
15031/1 FirstDlUnitDataFrame Cumulative number of G/E

pre--established downlink TBF
without reception of a
DL--UNITDATA for this TBF.
15046/0 dataBlocksUp Cumulative size (in bytes) of all G

the BSSGP UL--UNITDATA PDU
sent by the BVC (PCU-->SGSN).
The size does not include the FR
and NS header

TDMA



number EDGE


establishment.
15058/0 upTbfImmediateAssig Cumulative number of immedate G/E

by the PCU to establish an UL
CCCH information.


411--9001--125
2.10.15 DL TBF Establishment: MS in Ready State

The network may initiate the establishment of a downlink TBF to support the
transfer of LLC PDUs in the direction from the network to the mobile station.
Data Flow Diagram: Downlink establishment towards a mobile in Ready State and
Packet Idle Mode
MS PCUSN SGSN
LLC_DL_FRAME
IMMEDIATE_ASSIGNMENT 15004/0
15005/0
15058/2 15031/1
DL_DATA_BLOCK (1)
15046/1
PACKET_POLLING_REQUEST
15047/1
PACKET_CONTROL_ACK
15047/0
PACKET_POWER_CONTROL_TIMING_
ADVANCE
15047/1
PACKET_DOWNLINK_ACK/NACK
15047/0
PACKET_DOWNLINK_ASSIGNMENT
15047/1
PACKET_CONTROL_ACK
15047/0
DL_DATA_BLOCK
15046/1
DL_DATA_BLOCK
15046/1
(1) Fast Downlink Assignment


number EDGE

(SGSN-->PCU)
15005/0 octetsDataDn Cumulative size (in bytes) of all G/E

the BSSGP DL--UNITDATA PDU
received by the BVC


TDMA.


15058/2 dnTbfImmediateAssig Cumulative number of Immediate G/E

nment Assignment Downlink messages
sent by the PCU to establish a DL
TBF

411--9001--125
2.10.16 DL TBF Establishment during UL transfer

During uplink TBF, the network may initiate a downlink TBF by sending a Packet
Downlink Assignment message or a Packet Timeslot Reconfigure, to the mobile
station.
Data Flow Diagram: Establishment with Packet Downlink Assignment and Packet
Timeslot Reconfigure
Note: To assign DL resources which need modification of the UL resources, a
Packet Timeslot Reconfigure message is sent:
MS PCUSN SGSN
UL_DATA_BLOCK
15046/1
UL_DATA_BLOCK
15046/1 LLC_DL_FRAME
PACKET_TIMESLOT_RECONFIGURE 15004/0
15005/0
15047/1 15031/1
PACKET_CONTROL_ACK
15047/0
DL_DATA_BLOCK
15046/1

number EDGE

(SGSN-->PCU)

received by the BVC



number EDGE

TDMA.


2.10.17 DL TBF Release: Normal Completion

The network initiates release of a downlink TBF by sending an RLC data block with
the Final Block Indicator (FBI) set to the value of 1 and with a valid RRBP field.
If the mobile station has correctly received all the RLC data blocks of the TBF, it
shall send a Packet Downlink Ack/Nack with Final Ack Indicator (FAI) set to the
value of 1.
Data Flow Diagram: Normal DL TBF Release
MS PCUSN SGSN
DL_DATA_BLOCK
15046/1
DL_DATA_BLOCK (1)
15046/1
15033/1
15047/0
15055/1
(1) FBI=1, Polling

(2) FAI=1

411--9001--125

number EDGE

TS sharing event.

TDMA.

15055/1 tbfNormalReleaseDn Cumulative number of normal G/E

releases of DL TBFs (related to
half duplex or full duplex transfer).

2.10.18 Abnormal DL TBF Release: lossOfComNN0002

This abnormal release occurs when there is no progression of the transmit window
(non progression of V(A) in DL)
Data Flow Diagram: Abnormal release of an DL TBF due to non progression of
V(A)
MS PCUSN SGSN
15046/1
PACKET_DOWNLINK_ACK/NACK (V(A))
N0002++
15047/0
DL_DATA_BLOCK
15046/1
DL_DATA_BLOCK
15046/1
15046/1
N0002++
15047/0
DL_DATA_BLOCK
15046/1
DL_DATA_BLOCK
15046/1
15046/1
N0002++=NN0002Max
15047/0
15057/0
15033/1

411--9001--125

number EDGE

TS sharing event.

TDMA.


does not progress

2.10.19 Abnormal DL TBF Release (FULL Duplex): lossOfComNN0002

This abnormal release occurs when there is no progression of the transmit window
(non progression of V(A) in DL).
Data Flow Diagram: Abnormal release of an DL TBF due to non progression of
V(A) during full duplex transfer, in the case that the UL TBF is also released
MS PCUSN SGSN
UL_DATA_BLOCK
15046/0
15046/1
N0002++
15047/0
DL_DATA_BLOCK
15046/1
DL_DATA_BLOCK
15046/1
UL_DATA_BLOCK
15046/0
15046/1
N0002++
15047/0
DL_DATA_BLOCK
15046/1
DL_DATA_BLOCK
15046/1
15046/1
N0002++=NN0002Max
15047/0
15057/0
15057/1
15033/1
15033/0

411--9001--125

number EDGE

TS sharing event.

TS sharing event.

frames.

TDMA.



number EDGE

does not progress

release.

411--9001--125
2.10.20 Abnormal DL TBF Release: N3105

This abnormal release occurs when the mobile station does not send a Packet
Downlink Ack Nack after N3105 downlink data block sent with S/P=1.
Data Flow Diagram: Non response from the mobile after N3105 downlink data with
S/P=1
MS PCUSN SGSN
15046/1
15047/0
DL_DATA_BLOCK
15046/1
15046/1
N3105++
15046/1
N3105++
15046/1
N3105++
15046/1
N3105++=N3105Max
15033/1
15057/3


number EDGE

TS sharing event.



packet transfer

411--9001--125
2.10.21 Abnormal DL TBF Release (FULL Duplex): N3105

This abnormal release occurs when the mobile station does not send a Packet
Downlink Ack Nack after N3105 downlink data block sent with S/P=1, during full
duplex transfer, in the case that the UL TBF is also released.
MS PCUSN SGSN
UL_DATA_BLOCK
15046/0
15046/1
15047/0
DL_DATA_BLOCK
15046/1
UL_DATA_BLOCK
15046/0
15046/1
N3105++
15046/1
N3105++
15046/1
N3105++
15046/1
N3105++=N3105Max
15033/1
15057/3
15057/1
15033/0


number EDGE

TS sharing event.

TS sharing event.

frames.

TDMA.


411--9001--125

number EDGE

release.

packet transfer

2.10.22 Abnormal DL TBF Release: DN_NASSIGNMAX

This abnormal release occurs when the mobile station does not acknowledge
downlink assignment messages.
Data Flow Diagram: Non response from the mobile after DN_NASSIGNMAX
Packet Downlink Assignment messages.
MS PCUSN SGSN
(POLLING)
15047/1
PACKET_CONTROL_ACK
Dn_Nassign++
(POLLING)
15047/1
PACKET_CONTROL_ACK
Dn_Nassign++
(POLLING)
15047/1
PACKET_CONTROL_ACK
Dn_Nassign++
(POLLING)
15047/1
PACKET_CONTROL_ACK
Dn_Nassign++
(POLLING)
15047/1
PACKET_CONTROL_ACK
Dn_Nassign++=Dn_NassignMax
15033/1
15057/3

411--9001--125

number EDGE

TS sharing event.


packet transfer

2.10.23 Abnormal DL TBF Release (FULL Duplex): DN_NASSIGNMAX
This abnormal release occurs when the mobile station does not acknowledge
downlink assignment messages.
Data Flow Diagram: Non response from the mobile after DN_NASSIGNMAX
Packet Downlink Assignment messages during full duplex transfer, in the case that
the DL TBF is also released.
MS PCUSN SGSN
UL_DATA_BLOCK
15046/0
PACKET_UPLINK_ACK/NACK
15049/0
(POLLING)
15047/1
PACKET_CONTROL_ACK
Dn_Nassign++
(POLLING)
15047/1
PACKET_CONTROL_ACK
Dn_Nassign++
(POLLING)
15047/1
PACKET_CONTROL_ACK
Dn_Nassign++
(POLLING)
15047/1
PACKET_CONTROL_ACK
Dn_Nassign++
(POLLING)
15047/1
PACKET_CONTROL_ACK
Dn_Nassign++=Dn_NassignMax
15033/1
15057/3
15057/1
15033/0

411--9001--125

number EDGE

TS sharing event.

TS sharing event.

frames.

TDMA
15049/0 packetAckNackUp Cumulative number of Packet G

Uplink Ack/Nack messages sent
by the PCU on this TDMA


number EDGE
15057/1 lossOfComT3169 Number of uplink TBF abnormal G

release.
15057/3 lossOfComT3195 Number of downlink TBF G

packet transfer

411--9001--125
2.10.24 Abnormal DL TBF Release: No final PDAN

downlink data block (sent with FBI=1 and S/P=1)
Data Flow Diagram: Non response from the mobile after NN0002 downlink data
blocks sent with FBI=1 and S/P=1
MS PCUSN SGSN
DL_DATA_BLOCK (1)
15046/1
NN0002++
DL_DATA_BLOCK (1)
15046/1
NN0002++
DL_DATA_BLOCK (1)
15046/1
NN0002++
DL_DATA_BLOCK (1)
15046/1
NN0002++=NN0002Max
15057/4
15057/0
15033/1
(1) FBI=1, Polling


number EDGE

TS sharing event.

TDMA.

does not progress

abnormal releases which occur
during the release of a downlink
TBF (while the PCU is waiting for
the last acknowledgement coming
from the mobile).

411--9001--125
2.10.25 Abnormal DL TBF Release (FULL Duplex): No final PDAN
downlink data block (sent with FBI=1 and S/P=1).
Data Flow Diagram: there is no response from the mobile after NN0002 downlink
data blocks sent with FBI=1 and S/P=1 during full duplex transfer, in the case that
the UL TBF is also released.
MS PCUSN SGSN
UL_DATA_BLOCK
15046/0
DL_DATA_BLOCK (1)
15046/1
NN0002++
UL_DATA_BLOCK
15046/0
DL_DATA_BLOCK (1)
15046/1
NN0002++
UL_DATA_BLOCK
15046/0
DL_DATA_BLOCK (1)
15046/1
NN0002++
DL_DATA_BLOCK (1)
15046/1
NN0002++=NN0002Max
15057/3
15057/4
15057/1
15033/1
15033/0
(1) FBI=1, Polling


number EDGE

TS sharing event.

TS sharing event.

frames.

TDMA.

release.

411--9001--125

number EDGE

packet transfer

abnormal releases which occur
during the release of a downlink
TBF (while the PCU is waiting for
the last acknowledgement coming
from the mobile).

2.10.26 Preemption of radio timeslots

The preemption procedure is used by the BSC to preempt some radio timeslots to
the PCU to allow dynamic sharing between GSM and GPRS on the air interface.
MS1 MS2 BSC PCUSN SGSN

UL_DATA_BLOCK
15046/0
CHANNEL_
REQUEST
PCU_TDMA_TS_STATUS
PCU_TDMA_TS_STATUS_
NACK
1815
PCU_TDMA_TS_STATUS
PACKET_PDTCH_RELEASE
PCU_TDMA_TS_STATUS_
ACK
1814 BVC_FLOW_CONTROL_
REQUESTS
15010/0
BVC_FLOW_CONTROL_ACK

411--9001--125

number EDGE
1814 gprsPreemption Number of PDTCH preemption G

successes
1815 gprsPreemptionNack Number of PDTCH preemption G

failures (requests “nacked” by the
PCU)
15010/0 bvcFlowControlReque Number of BSSGP G/E

sts FLOW--CONTROL--BVC PDU
sent by the BVC (PCU -->SGSN).

frames.

2.10.27 Cell update: Packet Transfer

The cell reselection occurs when a mobile goes from one cell to another. During
packet transfer and from a PCU point of view, this corresponds to a release of TBF
in one cell and the establishment of a new TBF in the other cell. Note that the cell
update is controlled by the mobile station.
Data Flow Diagram: Cell reselection from cell A to cell B and establishment of a
new uplink TBF in cell B
BTS_A BTS_B PCUSN SGSN

UL_DATA_BLOCK
15046/0
CHANNEL_REQUEST
15059/0
DL_DATA_BLOCK
15046/1
15058/0
15056/1
15047/0
15047/1
PACKET_CONTROL_ACK
15047/0
UL_DATA_BLOCK
15046/0 LLC_UL_FRAME
15004/1
15005/1
FLUSH_LL_BTS--A
15014/0
FLUSH_LL_ACK

411--9001--125

number EDGE
15004/1 pduDataDn Number of BSSGP G/E

UL--UNITDATA PDU sent by the
BVC (PCU-->SGSN).
15005/1 octetsDataUp cumulative size (in bytes) of all the G/E

received by the BVC
(PCU-->SGSN). The size does not
15014/0 msFlushLLRequest Number of BSSGP FLUSH--LL G/E

PDU received by the BVCI0 for all
MS in the cell associated to the
BVC (the BVC is indicated in the
message by the field BVCI (old)).

frames.

TDMA.


TDMA

establishment.


number EDGE

by the PCU to establish and UL
CCCH information.


411--9001--125
2.11 Advanced Speech Call Items (ASCI) (GSM--R)

ASCI provides advanced features such as VBS (Voice Broadcast Service), VGCS
(Voice Group Call Service) and eMLPP (enhanced MultiLevel Precedence &
Pre--emption).
Data Flow Diagram: Standard call setup (VBS and VGCS)
MS BTS BSC MSC
From the VBS or VGCS

originator
channel_request
channel_required
channel_activate (SDCCH)
channel_activate_ack
imm_ass imm_ass_command
2036 (8W)
SABM(CM_serv_req [VBS or VGCS])

est_ind(CM_serv_req [VBS or VGCS])
UA SCCP_CR(CM_serv_req [VBS or VGCS])
1722
SCCP_CC
CM_serv_acc
setup(broadcast call Id)
channel_activate (TCH) assignment_req
assignment_command
SABM est_ind
UA
assignment_comp
assignment_comp
2037 (8W) RF_channel_release(SDCCH)
RF_channel_release_ack

MS BTS BSC MSC
For each BSC in the GCA

Call Controlling SCCP connection setup:
SCCP_CR(VGCS/VBS_setup)
SCCP_CC
VGCS/VBS_setup_ack
For each cell in the GCA

Resource Controlling SCCP conn. setup:
SCCP_CR(VGCS/VBS_ass_req)
channel_activate
SCCP_CC
VGCS/VBS_ass_result
notification_command
notification/NCH
(cyclic notification process)
uplink_busy Call establishment indication

(only in case of VGCS)
connect (to the VBS or VGCS call
initiator)

411--9001--125
Data Flow Diagram: Standard call termination (the originator releases the VBS/
VGCS call)
MS BTS BSC MSC
VBS or VGCS call originator
termination_request
termination
clear_command
channel_release
deactivate_SACCH
deactivate_SACCH_ack
DISC
Release_indication
2053 (8W)
RF_channel_release(SDCCH)
clear_complete
SCCP_RLSD
For each cell in the GCA Resource controlling cnx
Notification_command clear_command
UI(channel_release) Channel_release clear_complete
UI(channel_release) SCCP_RLSD
UI(channel_release)
Deactivate_SACCH
Deactivate_SACCH_ack
RF_channel_release
For each BSC in the GCA Call controlling cnx

SCCP_RLSD


411--9001--125
Nortel Confidential BSS Observation management principles 3--1
3 BSS OBSERVATION MANAGEMENT PRINCIPLES

This chapter contains:
a brief reminder of the principles underlying BSS observations (detailed in
NTP < 007 >)
a description of the structure and contents of the BSS observation counters, with
their accounting algorithms
the list of observation classes
3.1 Observation types (OGS, OFS, ORT, ODIAG, temporary)

BSS observations covers the following:
BSS permanent observation
• General statistic observation (OGS) (a preview of the report is visible in the
performance window at the OMC--R)
• Fast statistic observation (OFS) (visible in the Report window at the OMC--R)
• Real time observation (ORT) (a preview of the report is visible in the
Performance window of the OMC--R)
• Diagnostic observation (ODIAG)
Temporary Observation
• Interference temporary observation
• Abis Interface temporary observation
• SS7 link temporary observation
The BSS observations apply to the following BSC types:
BSC type
Observation type BSC BSC 3000
12000HC
OGS X X
OFS X X
ORT X X
Temporary Interference X
Temporary Abis Interface X
Temporary SS7 Link X
ODIAG X X

3--2 BSS Observation management principles Nortel Confidential
3.2 Observation management

BSS observations are activated by creating mdScanner objects whose
mdGranularityPeriod attribute defines the periods at which the observation
counters are read and transferred to the OMC--R agent.
When a BSS observation is activated, all the related counters start counting. When
the observation is deactivated, the counters stop counting; they are no longer
collected.
3.2.1 Observed entities

The observed entities are shared between three main groups:
Radio resources, including radio channels, serving cells, and neighbor cells
Data links, including A and Abis interfaces
Equipment, including BSC equipment, PCUSN equipment, PCM links, and
BSS/OMC--R link
3.2.2 Observation domains

The evaluation of network performance based on the results of radio entity
observation covers four domains:
traffic load
quality of service
resource availability
network configuration control
3.2.3 Observations and alarms

Observations can have an associated threshold.
Performance management can generate an alarm when a threshold is crossed on a
given observation. This mechanism applies to:
BSS GSM observations
BSS PCU (GPRS) observations (synthetic counters)

411--9001--125
3.3 Observation counter types (totalizer, value, load)

Each observation counter has a header containing the following three fields:
COUNTER TYPE
COUNTER IDENTIFIER
SCREENING CRITERIA
COUNTER TYPE identifies the type of the counter:

totalizer (refer to Paragraph 3.3.1)
value (refer to Paragraph 3.3.2)
load (refer to Paragraph 3.3.3)
COUNTER IDENTIFIER identifies the observation counter. This identifier is related
to the counting function.
SCREENING CRITERIA is used when an event occurs which can be expanded to give
more information, and a counter is required to be maintained for each sub--class of
information.
3.3.1 Cumulative counters

This type of counter provides a raw count. It contains an additional field:
CUMULATED VALUE
The accounting algorithm is as follows:

initialization: CUMULATED VALUE = 0
event: add N to CUMULATED VALUE
collect:
• read CUMULATED VALUE
• reset CUMULATED VALUE = 0

3.3.2 Value counters

This type of counter provides average values from raw counts obtained by internal
sampling (the time interval between two events is variable and is not accessible to
users). It can also provide a maximum value.
It contains three additional fields:
CUMULATED VALUE
NUMBER OF SAMPLES
MAX VALUE (if required)

initialization:
• CUMULATED VALUE = 0
• NUMBER OF SAMPLES = 0
• MAX value = reference threshold (if required)
event:
• add N to CUMULATED VALUE
• add 1 to NUMBER OF SAMPLES
• if N > MAX VALUE, then MAX VALUE = N (if required)
collect:
• read NUMBER OF SAMPLES
• read MAX VALUE
• reset NUMBER OF SAMPLES = 0
• reset MAX VALUE = reference threshold

411--9001--125
3.3.3 Load counters

This type of counter provides average values from raw counts obtained by internal
sampling (the time interval between two events is variable and is not accessible to
users). It can also provide a maximum value.
It contains four additional fields:
CUMULATED VALUE
NUMBER OF SAMPLES
MAX VALUE (if required)
MIN/MAX FLAG

initialization:
• CUMULATED VALUE = 0
• NUMBER OF SAMPLES = 0
• MIN or MAX FLAG = 1
• EXTERNAL SAMPLING PERIOD = T1
event:
• add or subtract 1 to/from VALUE (depending on maximum or minimum
count)
on external sampling period T1 elapse:
• add 1 to NUMBER OF SAMPLES
collect:
• read NUMBER OF SAMPLES
• read MAX VALUE
• reset NUMBER OF SAMPLES = 0
• reset MAX VALUE = reference threshold

3.4 Customized counter names

On top of its Q3 name, you can assign a customized name to any observation counter
at the SDO level. This customized name is defined at the SDO level and is kept
through SDO upgrades.
All counters added to the SDO counter list during an upgrade can get a customized
name at upgrade time. The upgrade procedure gets customized names from a
dedicated configuration file (/SDO/base/install/config/sdo_cntrs_list_FT.cfg)
provided by Nortel.
This file is a set of lines (one per Q3 name to customize) sharing the same format:
<counter Q3 name> # ”<counter id> <counter subid> <occurrence id> <type of
counter>”
To enable this feature:
1 Click the Data Format tab on the SDO MMI
2 Set the “Counter name” field to ”custom”
3.5 Maximum number of counters

A BSC can make a limited number of observations. Refer to the following table to
know about this limitations per BSC type and version.
BSC type BSC Number of distinct BSC memory threshold

version counters Ids observed
V12 200 900 (see Paragraph 3.5.2)
BSC 2G
V15 350 (see Paragraph 3.5.3)
V14.3 300 1500 (see Paragraph 3.5.2)
BSC 3000
V15 350 1500 (see Paragraph 3.5.2)
Table 3--1 BSC memory threshold
Two major constraints must be taken into account when running observations:
the number of counter Ids per observation type
a threshold related to the use of BSC memory
3.5.1 Number of counter Ids per observation type

For each observation type (ORT, OFS, OGS, ODIAG), a maximum number of
distinct counter Ids (screenings are ignored) is allowed.

411--9001--125
3.5.2 Use of BSC memory

To ensure correct performance, BSC memory use must not exceed a limit given by
the following formula:
CELL_OFS + CELL_OGS + (NEIGH_OGS + NEIGH_OFS)*nb_neigh +
(TDMAcla_OGS + TDMAcla_OFS)*nb_TDMA_classes < BSC memory
THRESHOLD
If BSC memory use is greater than this threshold, a warning message will ask you
to remove some counters in the bsc counter list.
Name Meaning
CELL_OFS number of counter screenings (couple id:subid) per cell
on OFS observation
CELL_OGS number of counter screenings (couple id:subid) per cell
on OGS observation
NEIGH_OFS number of counter screenings (couple id:subid) per
neighboring cell on OFS observation
NEIGH_OGS number of counter screenings (couple id:subid) per
neighboring cell on OGS observation
nb_neigh number of neighboring cells per cell (=32)
TDMAcla_OFS number of counter screenings (couple id:subid) per
tdma on OFS observation
TDMAcla_OGS number of counter screenings (couple id:subid) per
tdma on OGS observation
nb_TDMA_classes 2
BSC memory for BSC 12000HC V12 and BSC 3000 (V14 and V15),
THRESHOLD refer to the values given in Table 3--1
3.5.3 DRAM limitation on BSC 12000HC V15

There is a limitation due to the DRAM available per CPU for observation. The
limitation is based on the formula below.
2 * (Cumulative + Value + Load) < THRESHOLD
where:
Cumulative = cumulative_size * [(nb_cell_bsc * CUM_CELL) + (nb_odiag *
CUM_CELL_ODIAG) + (nb_cell_cg * nb_tdma_classes *
CUM_TDMA_class) + (nb_odiag * nb_tdma_classes *
CUM_TDMA_class_ODIAG) + (nb_cell_bsc * nb_neighb * CUM_NEIGHB)
+ (nb_odiag * nb_neighb * CUM_NEIGHB_ODIAG) + (nb_cell_cg * nb_ccch
* CUM_CCCH) + (nb_odiag * nb_ccch * CUM_CCCH_ODIAG)]

Value = value_size * [(nb_cell_bsc * VAL_CELL) + (nb_odiag *

VAL_CELL_ODIAG) + (nb_cell_cg * nb_tdma_classes * VAL_TDMA_class)
+ (nb_odiag * nb_tdma_classes * VAL_TDMA_class_ODIAG) + (nb_cell_bsc
* nb_neighb * VAL_NEIGHB) + (nb_odiag * nb_neighb *
VAL_NEIGHB_ODIAG) + (nb_cell_cg * nb_ccch * VAL_CCCH) + (nb_odiag
* nb_ccch * VAL_CCCH_ODIAG)]
Load = load_size * [(nb_cell_bsc * LOAD_CELL) + (nb_odiag *
LOAD_CELL_ODIAG) + (nb_cell_cg * nb_tdma_classes *
LOAD_TDMA_class) + (nb_odiag * nb_tdma_classes *
LOAD_TDMA_class_ODIAG) + (nb_cell_bsc * nb_neighb *
LOAD_NEIGHB) + (nb_odiag * nb_neighb * LOAD_NEIGHB_ODIAG) +
(nb_cell_cg * nb_ccch * LOAD_CCCH) + (nb_odiag * nb_ccch *
LOAD_CCCH_ODIAG)]
Threshold = 1.5 Mbytes
flip/flop mecanism explains the multiplication by 2
Name Meaning
CUM_CELL number of screenings (couple id:subid) of
cumulative counters belonging to CELL
location and OFS, OGS and ORT
observations
CUM_CELL_ODIAG number of screenings (couple id:subid) of
cumulative counters belonging to CELL
location and ODIAG observation
VAL_CELL number of screenings (couple id:subid) of
value counters belonging to CELL location
and OFS, OGS and ORT observations
VAL_CELL_ODIAG number of screenings (couple id:subid) of
value counters belonging to CELL location
and ODIAG observation
LOAD_CELL number of screenings (couple id:subid) of
load counter belonging to CELL location and
OFS, OGS and ORT observations
LOAD_CELL_ODIAG number of screenings (couple id:subid) of
load counter belonging to CELL location and
ODIAG observation
CUM_TDMA_class number of screenings (couple id:subid) of
cumulative counters belonging to TDMA
class location and OFS, OGS and ORT
observations

411--9001--125
CUM_TDMA_class_ODIAG number of screenings (couple id:subid) of

cumulative counters belonging to
TDMAclass location and ODIAGobservation
VAL_TDMA_class number of screenings (couple id:subid) of
value counters belonging to TDMA class
observations
VAL_TDMA_class_ODIAG number of screenings (couple id:subid) of
value counters belonging to TDMA class
LOAD_TDMA_class number of screenings (couple id:subid) of
load counter belonging to TDMA class
observations
LOAD_TDMA_class_ODIAG number of screenings (couple id:subid) of
load counter belonging to TDMA class
CUM_NEIGHB number of screenings (couple id:subid) of
NEIGHBOURING CELL location and OFS,
OGS and ORT observations
CUM_NEIGHB_ODIAG number of screenings (couple id:subid) of
NEIGHBOURING CELL location and
ODIAG observation
VAL_NEIGHB number of screenings (couple id:subid) of
value counters belonging to
VAL_NEIGHB_ODIAG number of screenings (couple id:subid) of
value counters belonging to
ODIAG observation
LOAD_NEIGHB number of screenings (couple id:subid) of
load counters belonging to
LOAD_NEIGHB_ODIAG number of screenings (couple id:subid) of
load counters belonging to
ODIAG observation

CUM_CCCH number of screenings (couple id:subid) of

cumulative counters belonging to CCCH
observations
CUM_CCCH_ODIAG number of screenings (couple id:subid) of
cumulative counters belonging to CCCH
VAL_CCCH number of screenings (couple id:subid) of
value counters belonging to CCCH location
VAL_CCCH_ODIAG number of screenings (couple id:subid) of
value counters belonging to CCCH location
LOAD_CCCH number of screenings (couple id:subid) of
load counters belonging to CCCH location
LOAD_CCCH_ODIAG number of screenings (couple id:subid) of
load counters belonging to CCCH location
nb_neighb number of neighbouring cells per cell = 32
nb_tdma_classes number of TDMA classes per cell = 2
nb_ccch number of CCCH per cell = 4
nb_odiag number of odiag cells per cellgroup = 4
nb_cell_cg number of cells per cellgroup = 120
nb_cell_bsc number of cells per BSC = 160
cumulative_size size of a cumulative screening = 4
load_size size of a load screening = 17
value_size size of a value screening = 12

411--9001--125
3.6 Observation classes

BSS observation counters are classified as follows (in alphabetical order):
A interface
Abis interface
allocation (of radio resources)
assignment (of dedicated channels)
ASCI (GSM--R feature)
BSC equipment
BSS/OMC--R link
handover
interference
Layer 1 management (L1M)
monitoring (of common control channels)
PCM link
release (of resources)
setup (of calls)
SMS service
3.7 Mobility Class Sensitivity Counters
CAUTION
GSM--R specific
“Toggling” counters provide the operator with statistics indexed by the MS power
class (2 W or 8 W or 2 W + 8 W).
The QoS is measured by type of application:
train control with 8 W mobiles, and with a high QoS
shunt with 2 W mobiles, and with a lower QoS
The operator can toggle between ignoring/taking into account the power class
criterium at the OMC-R. The incrementation of “toggling” counters depends on the
value of the msPowerClassToggle parameter (settable by the operator on the bts
object at the OMC--R). The default value of the msPowerClassToggle parameter is
“2W + 8W”. The operator can set it either to “2W” or to “8W”.

To get significant measures, it is recommended to:

1 stop observation counters.
2 toggle the power class criterium.
3 start observation counters again.
Note: A synthetic counter can be used as a “toggling” counter only if all the
counters that are part of the formula are “toggling” counters themselves.
Hence, if one counter is not a “toggling” counter, then the synthetic counter
is valid only if the msPowerClassToggle parameter is set to “2W + 8W”.
The list of toggling counters is provided in Table 3--2:

counter Q3 name object
1044/0 signallingPhaseDurationCum/Ech/Max/Moy bts
1045/0 signallingPhaseDurationHighCum/Ech/Max/ bts
Moy
1049/0 attemptedTchFrSeizures bts
1050/0 successfulTchFrSeizures bts
1055/0 assignFailure bts
1065/0 hoExecutionOutgoingIntraBss bts
1065/1 hoExecutionOutgoingIntraBssDirectedRetry bts
1066/0 hoExecutionOutgoingInterBss bts
1066/1 hoExecutionOutgoingInterBssDirectedRetry bts
1067/0 hoSuccessOutgoingIntraBss bts
1067/1 hoSuccessOutgoingIntraBssDirectedRetry bts
1068/0 hoSuccessOutgoingInterBss bts
1068/1 hoSuccessOutgoingInterBssDirectedRetry bts
1069/0 hoRequestIncomingIntraBss bts
1070/0 hoRequestIncomingInterBss bts
1071/0 hoExecutionIncomingIntraBss bts
1072/0 hoExecutionIncomingInterBss bts
1073/0 hoSuccessIncomingIntraBss bts
1074/0 hoSuccessIncomingInterBss bts
1075/0 hoRequestOutgoingIntraBss bts
1076/0 hoRequestOutgoingInterBss bts
1077/0 hoSuccessOutgoingFirstIntra bts

411--9001--125
1078/0 hoSuccessOutgoingFirstInter bts

1081/0 hoRequestIntraBts bts
1082/0 hoExecutionIntraBts bts
1083/0 hoSuccessIntraBts bts
1134/0 hoUnsuccessReestIntraBtsTch bts
1135/0 hoUnsuccessReestOutgoingIntraBssTch bts
1136/0 hoUnsuccessReestOutgoingInterBssTch bts
1137/0 hoUnsuccessReestIncomingIntraBssTch bts
1138/0 hoRequiredTchUplinkStrength bts
1138/1 hoRequiredTchDownlinkStrength bts
1138/2 hoRequiredTchUplinkQuality bts
1138/3 hoRequiredTchDownlinkQuality bts
1138/4 hoRequiredTchDistance bts
1138/5 hoRequiredTchPowerBudgetQuality bts
1138/6 hoRequiredTchCapture bts
1138/7 hoRequiredTchIntraBtsOm bts
1138/8 hoRequiredTchIntraBtsUplink bts
1138/9 hoRequiredTchIntraBtsDownlink bts
1138/10 hoRequiredTchDirectedRetry bts
1138/11 hoRequiredTchTdmaClass0 bts
1138/12 hoRequiredTchTdmaClass1 bts
1138/13 hoRequiredTchInterBtsOm bts
1138/14 hoRequiredTchTraffic bts
1138/15 hoRequiredTchTieringLargeToSmallPattern bts
1138/16 hoRequiredTchTieringSmallToLargePattern bts
1139/0 hoRequiredSdcchUplinkStrength bts
1139/1 hoRequiredSdcchDownlinkStrength bts
1139/2 hoRequiredSdcchUplinkQuality bts
1139/3 hoRequiredSdcchDownlinkQuality bts
1139/4 hoRequiredSdcchDistance bts
1139/5 hoRequiredSdcchPowerBudget bts
1139/6 hoRequiredSdcchCapture bts
1139/8 hoRequiredSdcchIntraBtsUplink bts

1139/9 hoRequiredSdcchIntraBtsDownlink bts

1139/13 hoRequiredSdcchInterBtsOm bts
1140/0 hoExecutionOutgoingIntraBssSdcch bts
1141/0 hoExecutionOutgoingInterBssSdcch bts
1142/0 hoSuccessOutgoingIntraBssSdcch bts
1143/0 hoSuccessOutgoingInterBssSdcch bts
1144/0 hoRequestIncomingIntraBssSdcch bts
1145/0 hoRequestIncomingInterBssSdcch bts
1146/0 hoExecutionIncomingIntraBssSdcch bts
1147/0 hoExecutionIncomingInterBssSdcch bts
1148/0 hoSuccessIncomingIntraBssSdcch bts
1149/0 hoSuccessIncomingInterBssSdcch bts
1150/0 hoRequestOutgoingIntraBssSdcch bts
1151/0 hoRequestOutgoingInterBssSdcch bts
1152/0 hoSuccessOutgoingFirstIntraSdcch bts
1153/0 hoSuccessOutgoingFirstInterSdcch bts
1154/0 hoRequestIntraBtsSdcch bts
1155/0 hoExecutionIntraBtsSdcch bts
1156/0 hoSuccessIntraBtsSdcch bts
1157/0 hoUnsuccessReestIntraBtsSdcch bts
1158/0 hoUnsuccessReestOutgoingIntraBssSdcch bts
1159/0 hoUnsuccessReestOutgoingInterBssSdcch bts
1160/0 hoUnsuccessReestIncomingIntraBssSdcch bts
1162/0 signallingReleaseNoBtsSccpDiscInd bsc
1162/1 signallingReleaseNoBtsReset bsc
1162/3 signallingReleaseNoBtsSccpDataRefusal bsc
1162/26 signallingReleaseNoBtsTsccRel bsc
1162/27 signallingReleaseNoBtsBadDataInd bsc
1162/28 signallingReleaseNoBtsOthers bsc
1163/0 signallingReleaseBtsSccpDiscInd bts
1163/1 signallingReleaseBtsReset bts
1163/2 signallingReleaseBtsResetCirc bts
1163/3 signallingReleaseBtsSccpDataRefusal bts

411--9001--125
1163/4 signallingReleaseBtsIncFirstL3 bts

1163/5 signallingReleaseBtsT3101 bts
1163/6 signallingReleaseBtsT3107CircDown bts
1163/7 signallingReleaseBtsOmTsRemoval bts
1163/8 signallingReleaseBtsTsRemovalEqptFail bts
1163/9 signallingReleaseBtsOmCicRemoval bts
1163/10 signallingReleaseBtsCicRemovalEqptFail bts
1163/11 signallingReleaseBtsOmRadioChanBloc bts
1163/12 signallingReleaseBtsCallClearing bts
1163/13 signallingReleaseBtsCnxFailRadioIntFail bts
1163/14 signallingReleaseBtsCnxFailRadioLinkFail bts
1163/16 signallingReleaseBtsReleaseInd bts
1163/17 signallingReleaseBtsErrorIndT200 bts
1163/18 signallingReleaseBtsErrorIndDm bts
1163/19 signallingReleaseBtsErrorIndSeq bts
1163/20 signallingReleaseBtsClearCommand bts
1163/21 signallingReleaseBtsRfResInd bts
1163/22 signallingReleaseBtsSwitchOver bts
1163/23 signallingReleaseBtsTmodMs bts
1163/28 signallingReleaseBtsOthers bts
1163/29 signallingReleaseBtsOverload bts
1163/32 signallingReleaseBtsCnxFailRemTransFail bts
1163/33 signallingReleaseBtsTdmaRemovalEdgeOpt bts
1164/6 trafficReleaseT3107CircDown bts
1164/12 trafficReleaseCallClearing bts
1164/13 trafficReleaseCnxFailRadioIntFail bts
1164/14 trafficReleaseCnxFailRadioLinkFail bts
1164/16 trafficReleaseReleaseInd bts
1164/17 trafficReleaseErrorIndT200 bts
1164/18 trafficReleaseErrorIndDm bts

1164/19 trafficReleaseErrorIndSeq bts

1164/23 trafficReleaseTmodMs bts
1164/24 trafficReleaseT3103 bts
1164/25 trafficReleaseT8 bts
1164/28 trafficReleaseOthers bts
1164/32 trafficReleaseCnxFailRemTransFail bts
1165/0 hoIndicationNotTreatedTchoke bts
1167/0 hoUnsuccessOutgoingIntraBssNAttemptTch bts
1168/0 hoUnsuccessOutgoingIntraBssNAttemptSdcch bts
1169/0 hoUnsuccessOutgoingInterBssNAttemptTch bts
1170/0 hoUnsuccessOutgoingInterBssNAttemptSdcch bts
1193/0 estabIndicSignallingPagingRes bts
1193/1 estabIndicSignallingLocUpdate bts
1193/2 estabIndicSignallingReEstab bts
1193/3 estabIndicSignallingImsiDetach bts
1193/4 estabIndicSignallingMoc bts
1193/5 estabIndicSignallingEmergency bts
1193/6 estabIndicSignallingShortMsg bts
1193/7 estabIndicSignallingSuppService bts
1193/8 estabIndicSignallingNotifResp bts
1195/0 estabIndicSigPhase1 bts
1196/0 estabIndicSigPhase2 bts
1200/0 hoNcellsExecution adjacentCellHandOver
1202/0 hoNcellsExecutionSdcch adjacentCellHandOver
1204/0 hoNcellsUnsuccessTchChlR adjacentCellHandOver
1204/1 hoNcellsUnsuccessTchTimer adjacentCellHandOver
1204/2 hoNcellsUnsuccessTchOther adjacentCellHandOver
1205/0 hoNcellsUnsuccessSdcchChlR adjacentCellHandOver
1205/1 hoNcellsUnsuccessSdcchTimer adjacentCellHandOver
1205/2 hoNcellsUnsuccessSdcchOther adjacentCellHandOver
1208/0 hoRequestOutgoingMbandEbandMsDualb bts
1209/0 hoSuccessOutgoingMbandEbandMsDualb bts
1620/0 directedRetryUnsuccessNoBts bts

411--9001--125
1621/0 sapi3SessionEstablishment bts

1705/0 channelActivateTchFrDataT16 bts
1707/0 channelActivateTchFrDataNT6000 bts
1709/0 channelActTchFrDataT bts
1710/0 channelActTchFrDataNT bts
1715/0 attemptedTchFrSeizuresMsDualb bts
1716/0 successfulTchFrSeizuresMsDualb bts
1750/0 estabIndicSignalling bts
1753/0 signallingReleaseBts bts
1756/0 hoFailureIntraBtsTchRadioLack bts
1756/1 hoFailureIntraBtsTchChannelActivateNack bts
1756/2 hoFailureIntraBtsTchTchnAckTimerExp bts
1757/0 hoFailureIntraBtsSdcchRadioLack bts
1757/1 hoFailureIntraBtsSdcchChannelActivateNack bts
1757/2 hoFailureIntraBtsSdcchTchnAckTimerExp bts
1758/0 hoFailureIncomingIntraBssTchRadioLack bts
1758/1 hoFailureIncomingIntraBssTchHoNotAllowed bts
1758/2 hoFailureIncomingIntraBssTchChannelActivate- bts
Nack
1758/3 hoFailureIncomingIntraBssTchTchnAckTimer- bts
Exp
1758/4 hoFailureIncomingIntraBssTchIncompatible bts
1759/0 hoFailureIncomingIntraBssSdcchRadioLack bts
1759/1 hoFailureIncomingIntraBssSdcchHoNotAllowed bts
1759/2 hoFailureIncomingIntraBssSdcchChannelActi- bts
vateNack

1759/3 hoFailureIncomingIntraBssSdcchTchnAckTim- bts

erExp
1760/0 hoFailureIncomingInterBssTchRadioLack bts
1760/1 hoFailureIncomingInterBssTchTerrestLack bts
1760/2 hoFailureIncomingInterBssTchHoNotAllowed bts
1760/3 hoFailureIncomingInterBssTchChannelActivate- bts
Nack
1760/4 hoFailureIncomingInterBssTchTchnAckTimer- bts
Exp
1760/5 hoFailureIncomingInterBssTchCICIncompatible bts
1761/0 hoFailureIncomingInterBssSdcchRadioLack bts
1761/1 hoFailureIncomingInterBssSdcchTerrestLack bts
1761/2 hoFailureIncomingInterBssSdcchHoNotAllowed bts
1761/3 hoFailureIncomingInterBssSdcchChannelActi- bts
vateNack
1761/4 hoFailureIncomingInterBssSdcchTchnAckTim- bts
erExp
1762/0 hoFailureOutgoingIntraBssTchRadioLack bts
1762/1 hoFailureOutgoingIntraBssTchHoNotAllowed bts
1762/2 hoFailureOutgoingIntraBssTchChannelActivate- bts
Nack
1762/3 hoFailureOutgoingIntraBssTchTchnAckTimer- bts
Exp
1762/4 hoFailureOutgoingIntraBssTchIncompatible bts
1763/0 hoFailureOutgoingIntraBssSdcchRadioLack bts
1763/1 hoFailureOutgoingIntraBssSdcchHoNotAllowed bts
1763/2 hoFailureOutgoingIntraBssSdcchChannelActi- bts
vateNack
1763/3 hoFailureOutgoingIntraBssSdcchTchnAckTim- bts
erExp
1764/0 hoFailureOutgoingInterBssTchRadioLack bts
1764/1 hoFailureOutgoingInterBssTchTerrestLack bts
1764/2 hoFailureOutgoingInterBssTchHoNotAllowed bts
1764/3 hoFailureOutgoingInterBssTchT7TimerExp bts
1764/4 hoFailureOutgoingInterBssTchOtherCases bts

411--9001--125
1764/5 hoFailureOutgoingInterBssTchIncompatible bts

1765/0 hoFailureOutgoingInterBssSdcchRadioLack bts
1765/1 hoFailureOutgoingInterBssSdcchTerrestLack bts
1765/2 hoFailureOutgoingInterBssSdcchHoNotAllowed bts
1765/3 hoFailureOutgoingInterBssSdcchT7TimerExp bts
1765/4 hoFailureOutgoingInterBssSdcchOtherCase bts
1768/0 hoUnsuccessOutgoingIntraCellTchReturnOld- bts
Channel
1768/1 hoUnsuccessOutgoingIntraCellTchT3103Time- bts
rExp
1769/0 hoUnsuccessOutgoingIntraCellSdcchReturnOld- bts
Channel
1769/1 hoUnsuccessOutgoingIntra- bts
CellSdcchT3103TimerExp
1770/0 hoUnsuccessOutgoingInterCellTchReturnOld- bts
Channel
1770/1 hoUnsuccessOutgoingInterCellTchT3103Time- bts
rExp
1770/2 hoUnsuccessOutgoingInterCellTchOtherCases bts
1771/0 hoUnsuccessOutgoingInterCellSdcchReturnOld- bts
Channel
1771/1 hoUnsuccessOutgoingInter- bts
1771/2 hoUnsuccessOutgoingInterCellSdcchOtherCases bts
1772/0 hoUnsuccessIncomingIntraCellTchReturnOld- bts
Channel
1772/1 hoUnsuccessIncomingIntraCellTchT3103Time- bts
rExp
1773/0 hoUnsuccessIncomingIntraCellSdcchReturnOld- bts
Channel
1773/1 hoUnsuccessIncomingIntra- bts
1774/0 hoUnsuccessIncomingInterBssTchTimerExp bts
1774/1 hoUnsuccessIncomingInterBssTchOtherCases bts
1775/0 hoUnsuccessIncomingInterBssSdcchTimerExp bts
1775/1 hoUnsuccessIncomingInterBssSdcchOtherCases bts

1776/0 hoRequiredTch bts

1777/0 hoRequiredSdcch bts
1778/0 signallingAbnormalReleaseCell bts
1780/0 hoSuccessOutgoingTch bts
1781/0 hoSuccessIncomingTch bts
1782/0 hoBtsRejected bts
1783/0 hoRequestOutgoingMbandMbandMsDualb bts
1784/0 hoRequestOutgoingEbandEbandMsDualb bts
1785/0 hoRequestOutgoingEbandMbandMsDualb bts
1786/0 hoSuccessOutgoingMbandMbandMsDualb bts
1787/0 hoSuccessOutgoingEbandEbandMsDualb bts
1788/0 hoSuccessOutgoingEbandMbandMsDualb bts
1789/0 hoExecutionOutgoingMbandEbandMsDualb bts
1790/0 hoExecutionOutgoingMbandMbandMsDualb bts
1791/0 hoExecutionOutgoingEbandEbandMsDualb bts
1792/0 hoExecutionOutgoingEbandMbandMsDualb bts
1793/0 hoRequestIncomingIntraBssTchMsDualb bts
1794/0 hoExecutionIncomingIntraBssTchMsDualb bts
1795/0 hoSuccessIncomingIntraBssTchMsDualb bts
1796/0 hoRequestIntraBtsMsDualb bts
1797/0 hoExecutionIntraBtsMsDualb bts
1798/0 hoSuccessIntraBtsMsDualb bts
1801/0 hoFailureTieringTchNorrLargeToSmallPattern bts
1801/1 hoFailureTieringTchNorrSmallToLargePattern bts
1802/0 hoSuccessTieringTchLargeToSmallPattern bts
1802/1 hoSuccessTieringTchSmallToLargePattern bts
1839/0 hoNcellsRequestOutgoingUplinkStrength adjacentCellHandOver
1839/1 hoNcellsRequestOutgoingDownlinkStrength adjacentCellHandOver
1839/2 hoNcellsRequestOutgoingUplinkQuality adjacentCellHandOver
1839/3 hoNcellsRequestOutgoingDownlinkQuality adjacentCellHandOver
1839/4 hoNcellsRequestOutgoingDistance adjacentCellHandOver
1839/5 hoNcellsRequestOutgoingPowerBudget adjacentCellHandOver
1839/6 hoNcellsRequestOutgoingDirectedRetry adjacentCellHandOver

411--9001--125
1839/7 hoNcellsRequestOutgoingInterCellOM adjacentCellHandOver

1839/8 hoNcellsRequestOutgoingTraffic adjacentCellHandOver
1839/9 hoNcellsRequestOutgoingOther adjacentCellHandOver
1840/0 hoNcellsSuccessOutgoingUplinkStrength adjacentCellHandOver
1840/1 hoNcellsSuccessOutgoingDownlinkStrength adjacentCellHandOver
1840/2 hoNcellsSuccessOutgoingUplinkQuality adjacentCellHandOver
1840/3 hoNcellsSuccessOutgoingDownlinkQuality adjacentCellHandOver
1840/4 hoNcellsSuccessOutgoingDistance adjacentCellHandOver
1840/5 hoNcellsSuccessOutgoingPowerBudget adjacentCellHandOver
1840/6 hoNcellsSuccessOutgoingDirectedRetry adjacentCellHandOver
1840/7 hoNcellsSuccessOutgoingInterCellOM adjacentCellHandOver
1840/8 hoNcellsSuccessOutgoingTraffic adjacentCellHandOver
1840/9 hoNcellsSuccessOutgoingOther adjacentCellHandOver
1841/0 assignRequestSdcchToTchChannel bts
1841/1 assignRequestOthers bts
1842/1 assignRequestAintOthers bts
1842/0 assignRequestAintSdcchToTchChannel bts
1799/0 assignToOtherBandOrZone bts
1139/7 hoRequiredSdcchIntraBtsOm bts
1139/14 hoRequiredSdcchTraffic bts
Table 3--2 Toggling counters


411--9001--125
Nortel Confidential Type and class of counters 4--1
4 TYPE AND CLASS OF COUNTERS

This chapter contains:
raw permanent BSS observation counters, grouped by counter family (see
Paragraph 4.1)
four observation types (ORT, OFS, OGS, and ODIAG) available with permanent
observation counters (see Paragraph 4.2)
synthetic permanent BSS counters (see Paragraph 4.3)
temporary observation counters appearing in V12 BSS observation reports (see
Paragraph 4.4) and BSC V15 2G
manager counters
md counters
raw permanent PCUSN counters (see Paragraph 4.7)
4.1 Permanent bsc observation counters

This section lists all the families of counters that consist of permanent BSC
observation counters. Lists of counters are provided for the following counter
families.
Abis Level 1
Abis Level 2
A interface
AMR
AMR on TrZone
ASCI
BSC
BSC 3G
BSC - Load of processor
CCCH Monitoring
Channel mode
Dedicated channel assignment
Directed retry
EDGE
Establishment
Global handovers

4--2 Type and class of counters Nortel Confidential
GPRS
GPRS on TrZone
Inter--bss handovers
Interferences
Intra--bss handovers
Intra--cell handovers
Layer One Management
Layer One Management on TrZone
Neighbor cells
OMC interface
PCM
Releases of communications in signalling phase
Releases of communications in traffic phase
SDCCH allocations on TrZone
SMS
TCH allocations
TCH allocations on TrZone
WPS
The permanent general observation covers the following counter classes:
general statistic observation (OGS) counters
fast statistic observation (OFS) counters
real time observation (ORT) counters
diagnostic observation (ODIAG) counters
4.1.1 Abis Level 1

Counter No. Q3 Name Type
1084/0 abisLevel1ErrorsBadFrame00 totalizer

411--9001--125



1084/3 abisLevel1ErrorsCrcError00 totalizer

411--9001--125



1084/4 abisLevel1ErrorsLostAlign00 totalizer

411--9001--125



4.1.2 Abis Level 2

1717/0 abisTrauFrameDlReceived totalizer
1718/0 abisTrauFrameCorrected totalizer
1719/0 abisTrauFrameMuted totalizer
1720/0 radioFrameUlReceived totalizer
1721/0 ecuActivation totalizer
4.1.3 A interface
1094/0 tcAllocated totalizer
1095/0 tcAveragedUsedMoy load
1095/0 tcAveragedUsedMax load
1095/0 tcAveragedUsedCum load
1095/0 tcAveragedUsedEch load
1104/0 sccpAllocated totalizer
1104/1 sccpAllocatedLcs totalizer
1105/0 sccpAveragedUsedMoy load
1105/0 sccpAveragedUsedMax load
1105/0 sccpAveragedUsedCum load
1105/0 sccpAveragedUsedEch load
1106/0 sccpRessourceFailure totalizer
1106/1 sccpRessourceFailureBscRefusal totalizer

411--9001--125
1106/2 sccpRessourceFailureLcs totalizer

1106/3 sccpRessourceFailureBscRefusalLcs totalizer
1107/0 aInputMessage totalizer
1108/0 aOutputMessage totalizer
1109/0 aMessageErrors totalizer
1172/0 dataNtRateFbTcbResLack totalizer
1172/1 dataNtRateFbTcbConfNotAllowed totalizer
1500/0 aTransparentUp totalizer
1501/0 aTransparentDown totalizer
1502/0 aNonTransparentUp totalizer
1503/0 aNonTransparentDown totalizer
4.1.4 AMR
1903/0 amrFrTchSuccessfullyAssigned totalizer
1903/1 amrHrTchSuccessfullyAssigned totalizer
1904/0 amrFrTchAssignFailure totalizer
1904/1 amrHrTchAssignFailure totalizer
1906/0 downlinkPowerCtrlMaxTchAmrFrCum value
1906/0 downlinkPowerCtrlMaxTchAmrFrEch value
1906/0 downlinkPowerCtrlMaxTchAmrFrMoy value
1906/0 downlinkPowerCtrlMaxTchAmrFrMax value
1907/0 uplinkPowerCtrlMaxTchAmrFrCum value
1907/0 uplinkPowerCtrlMaxTchAmrFrEch value
1907/0 uplinkPowerCtrlMaxTchAmrFrMoy value
1907/0 uplinkPowerCtrlMaxTchAmrFrMax value
1912/0 msPowerIncControlAmrFr totalizer
1913/0 msPowerDecControlAmrFr totalizer
1914/0 bsPowerIncControlAmrFr totalizer
1915/0 bsPowerDecControlAmrFr totalizer
1917/0 timingAdvanceAmrFrAvg totalizer
1917/1 timingAdvanceAmrFrMax totalizer
1918/0 downlinkPowerCtrlMaxTchAmrHrCum value

1918/0 downlinkPowerCtrlMaxTchAmrHrEch value

1918/0 downlinkPowerCtrlMaxTchAmrHrMoy value
1918/0 downlinkPowerCtrlMaxTchAmrHrMax value
1919/0 uplinkPowerCtrlMaxTchAmrHrCum value
1919/0 uplinkPowerCtrlMaxTchAmrHrEch value
1919/0 uplinkPowerCtrlMaxTchAmrHrMoy value
1919/0 uplinkPowerCtrlMaxTchAmrHrMax value
1924/0 msPowerIncControlAmrHr totalizer
1925/0 msPowerDecControlAmrHr totalizer
1926/0 bsPowerIncControlAmrHr totalizer
1927/0 bsPowerDecControlAmrHr totalizer
1929/0 timingAdvanceAmrHrAvg totalizer
1929/1 timingAdvanceAmrHrMax totalizer
1932/0 qualityHoFiltered totalizer
1933/0 capacityHoFiltered totalizer
1934/0 amrFrTchStdAveragedUsedCellMoy load
1934/0 amrFrTchStdAveragedUsedCellMax load
1934/0 amrFrTchStdAveragedUsedCellCum load
1934/0 amrFrTchStdAveragedUsedCellEch load
1935/0 amrHrModeDuration totalizer
1936/0 amrCellLoadStateModification totalizer
1937/0 amrFilteredBusyTchRatioCum value
1937/0 amrFilteredBusyTchRatioEch value
1937/0 amrFilteredBusyTchRatioMoy value
1937/0 amrFilteredBusyTchRatioMax value
1938/0 amrCellLoadStateUnderevaluated totalizer
1939/0 amrCellLoadStateOverevaluated totalizer
1950/0 intracellAmrFrUpHoRequiredTch totalizer
1950/1 intracellAmrFrDownHoRequiredTch totalizer
1950/2 amrQualityFrUpHoRequiredTch totalizer
1950/3 amrQualityFrDownHoRequiredTch totalizer
1950/4 capacityFrToHrHoRequiredTch totalizer
1951/0 alarmAmrHrToFrUpHoRequiredTch totalizer

411--9001--125
1951/1 alarmAmrHrToFrDownHoRequiredTch totalizer

1951/2 amrQualityHrUpHoRequiredTch totalizer
1951/3 amrQualityHrDownHoRequiredTch totalizer
1952/0 amrFrHoRequestOutgoingTch totalizer
1952/1 amrHrHoRequestOutgoingTch totalizer
1953/0 amrFrHoRequestIntraCellTch totalizer
1953/1 amrFrToHrHoRequestIntraCellTch totalizer
1953/2 amrHrToFrHoRequestIntraCellTch totalizer
1954/0 amrFrHoExecutionIntraCellTch totalizer
1954/1 amrFrToHrHoExecutionIntraCellTch totalizer
1954/2 amrHrToFrHoExecutionIntraCellTch totalizer
1955/0 amrFrHoSuccessIntraCellTch totalizer
1955/1 amrFrToHrHoSuccessIntraCellTch totalizer
1955/2 amrHrToFrHoSuccessIntraCellTch totalizer
1956/0 hoNCellsExecutionTchAmrHr totalizer
1957/0 hoNCellsExecutionTchAmrFr totalizer
1958/0 hoNCellsUnsuccessTchAmrHrHandoverFailure totalizer
1958/1 hoNCellsUnsuccessTchAmrHrTimerExpiration totalizer
1958/2 hoNCellsUnsuccessTchAmrHrClearCommand totalizer
1959/0 hoNCellsUnsuccessTchAmrFrHandoverFailure totalizer
1959/1 hoNCellsUnsuccessTchAmrFrTimerExpiration totalizer
1959/2 hoNCellsUnsuccessTchAmrFrClearCommand totalizer
1960/0 trafficReleaseAmrFrLapdmCause totalizer
1960/1 trafficReleaseAmrFrRadioCause totalizer
1960/2 trafficReleaseAmrFrOthersCause totalizer
1961/0 trafficReleaseAmrHrLapdmCause totalizer
1961/1 trafficReleaseAmrHrRadioCause totalizer
1961/2 trafficReleaseAmrHrOthersCause totalizer
1963/0 hoNCellsRequestOutgoingAmrHr totalizer
1964/0 hoNCellsRequestOutgoingAmrFr totalizer
1983/0 amrUplinkNoDataFrames totalizer
1983/1 amrDownlinkNoDataFrames totalizer
1988/0 amrReversalPhaseFailure totalizer

4.1.5 AMR on TrZone

1900/0 amrFrTchAllocated totalizer
1900/0 amrFrTchAllocatedTrZone totalizer
1901/0 amrFrTchStdAveragedUsedMoy load
1901/0 amrFrTchStdAveragedUsedMax load
1901/0 amrFrTchStdAveragedUsedCum load
1901/0 amrFrTchStdAveragedUsedEch load
1901/0 amrFrTchStdAveragedUsedTrZoneMoy load
1901/0 amrFrTchStdAveragedUsedTrZoneMax load
1901/0 amrFrTchStdAveragedUsedTrZoneCum load
1901/0 amrFrTchStdAveragedUsedTrZoneEch load
1902/0 amrFrTchConnectionDurationCum value
1902/0 amrFrTchConnectionDurationEch value
1902/0 amrFrTchConnectionDurationMoy value
1902/0 amrFrTchConnectionDurationMax value
1902/0 amrFrTchConnectionDurationTrZoneCum value
1902/0 amrFrTchConnectionDurationTrZoneEch value
1902/0 amrFrTchConnectionDurationTrZoneMoy value
1902/0 amrFrTchConnectionDurationTrZoneMax value
1902/1 amrHrTchConnectionDurationCum value
1902/1 amrHrTchConnectionDurationEch value
1902/1 amrHrTchConnectionDurationMoy value
1902/1 amrHrTchConnectionDurationMax value
1902/1 amrHrTchConnectionDurationTrZoneCum value
1902/1 amrHrTchConnectionDurationTrZoneEch value
1902/1 amrHrTchConnectionDurationTrZoneMoy value
1902/1 amrHrTchConnectionDurationTrZoneMax value
1905/0 CIUplinkFr totalizer
1905/0 CIUplinkFrTrZone totalizer
1908/0 RxLevDownlinkAmrFr totalizer
1908/0 RxLevDownlinkAmrFrTrZone totalizer
1909/0 RxLevUplinkAmrFr totalizer

411--9001--125
1909/0 RxLevUplinkAmrFrTrZone totalizer

1910/0 RxQualDownlinkAmrFr totalizer
1910/0 RxQualDownlinkAmrFrTrZone totalizer
1911/0 RxQualUplinkAmrFr totalizer
1911/0 RxQualUplinkAmrFrTrZone totalizer
1916/0 CIUplinkAmrFr totalizer
1916/0 CIUplinkAmrFrTrZone totalizer
1920/0 RxLevDownlinkAmrHr totalizer
1920/0 RxLevDownlinkAmrHrTrZone totalizer
1921/0 RxLevUplinkAmrHr totalizer
1921/0 RxLevUplinkAmrHrTrZone totalizer
1922/0 RxQualDownlinkAmrHr totalizer
1922/0 RxQualDownlinkAmrHrTrZone totalizer
1923/0 RxQualUplinkAmrHr totalizer
1923/0 RxQualUplinkAmrHrTrZone totalizer
1928/0 CIUplinkAmrHr totalizer
1928/0 CIUplinkAmrHrTrZone totalizer
1930/0 msLostMeasurementsAmrFr totalizer
1930/0 msLostMeasurementsAmrFrTrZone totalizer
1931/0 msLostMeasurementsAmrHr totalizer
1931/0 msLostMeasurementsAmrHrTrZone totalizer
1975/0 amrFrUplinkCodec475 totalizer
1975/0 amrFrUplinkCodec475TrZone totalizer
1976/0 amrHrUplinkCodec475 totalizer
1976/0 amrHrUplinkCodec475TrZone totalizer


1977/0 amrFrDownlinkCodec475 totalizer
1977/0 amrFrDownlinkCodec475TrZone totalizer
1978/0 amrHrDownlinkCodec475 totalizer
1978/0 amrHrDownlinkCodec475TrZone totalizer
1979/0 amrFrBadSpeechFramesCodec475 totalizer
1979/0 amrFrBadSpeechFramesCodec475TrZone totalizer
1980/0 amrFrValidSpeechFramesCodec475 totalizer
1980/0 amrFrValidSpeechFramesCodec475TrZone totalizer
1981/0 amrHrBadSpeechFramesCodec475 totalizer

411--9001--125
1981/0 amrHrBadSpeechFramesCodec475TrZone totalizer

1982/0 amrHrValidSpeechFramesCodec475 totalizer
1982/0 amrHrValidSpeechFramesCodec475TrZone totalizer
1984/0 incAmrFrUpModif totalizer
1984/0 incAmrFrUpModifTrZone totalizer
1984/1 decAmrFrUpModif totalizer
1984/1 decAmrFrUpModifTrZone totalizer
1985/0 incAmrFrDownModif totalizer
1985/0 incAmrFrDownModifTrZone totalizer
1985/1 decAmrFrDownModif totalizer
1985/1 decAmrFrDownModifTrZone totalizer
1986/0 incAmrHrUpModif totalizer
1986/0 incAmrHrUpModifTrZone totalizer
1986/1 decAmrHrUpModif totalizer
1986/1 decAmrHrUpModifTrZone totalizer
1987/0 incAmrHrDownModif totalizer
1987/0 incAmrHrDownModifTrZone totalizer
1987/1 decAmrHrDownModif totalizer
1987/1 decAmrHrDownModifTrZone totalizer
4.1.6 ASCI
1193/8 estabIndicSignallingPiggybacked totalizer
1504/0 vgcsAccessGrant totalizer
1505/0 vgcsMscReject totalizer

1506/2 aintOverLoadRejectedOpVbsVgcsSetup totalizer

1506/3 aintOverLoadRejectedOpVbsVgcsAssignment totalizer
1722/0 asciCallInitiationVbs totalizer
1722/1 asciCallInitiationVgcs totalizer
1723/0 asciInbandPaging totalizer
1724/0 asciInbandNotification totalizer
1725/0 asciPreemptionPerformed totalizer
1800/0 asciTalkerHandoverVbs totalizer
1800/1 asciTalkerHandoverVgcs totalizer
2035/0 msClassSensitivityToggle totalizer
2036/0 attemptedTchFrSeizures8W totalizer
2037/0 successfulTchFrSeizures8W totalizer
2038/0 hoSuccessOutgoingIntraBss8W totalizer
2039/0 hoSuccessOutgoingInterBss8W totalizer
2040/0 hoRequestIncomingIntraBss8W totalizer
2041/0 hoRequestIncomingInterBss8W totalizer
2042/0 hoSuccessIncomingIntraBss8W totalizer
2043/0 hoSuccessIncomingInterBss8W totalizer
2044/0 hoRequestOutgoingIntraBss8W totalizer
2045/0 hoRequestOutgoingInterBss8W totalizer
2046/0 hoRequestIntraBts8W totalizer
2047/0 hoSuccessIntraBts8W totalizer
2048/0 hoSuccessOutgoingIntraBssSdcch8W totalizer
2049/0 hoSuccessOutgoingInterBssSdcch8W totalizer
2050/0 hoRequestOutgoingIntraBssSdcch8W totalizer
2051/0 hoRequestOutgoingInterBssSdcch8W totalizer
2052/0 signallingReleaseBts8w totalizer
2052/1 signallingReleaseBtsT3107CircDown8W totalizer
2053/0 trafficRelease8W totalizer
2054/0 estabIndicSignallingEmergency8W totalizer
2055/0 estabIndicSigPhase28W totalizer
2056/0 hoUnsuccessOutgoingIntraCellTchReturnOldChannel8W totalizer
2056/1 hoUnsuccessOutgoingIntraCellTchT3103TimerExp8W totalizer

411--9001--125
2057/0 hoUnsuccessOutgoingInterCellTchReturnOldChannel8W totalizer

2057/1 hoUnsuccessOutgoingInterCellTchT3103TimerExp8W totalizer
2058/0 signallingAbnormalReleaseCell8W totalizer
2059/0 trafficAbnormalRelease8W totalizer
2060/0 uplinkFreeUplinkReply totalizer
2061/0 listenerDetectionExpiry totalizer
4.1.7 BSC
1121/0 chainStandByUpdate totalizer
1122/0 chainStandByResponse totalizer
1506/0 aintOverloadRejectedOpPageReq totalizer
1506/1 aintOverloadRejectedOpIncomingExtHoReq totalizer
1506/4 aintOverLoadRejectedOpPerformLocationReq totalizer
1803/0 cgOverloadRejectedOpPageReqCg0 totalizer
1803/1 cgOverloadRejectedOpChannelReqCg0 totalizer
1803/2 cgOverloadRejectedOpEstablishIndCg0 totalizer
1803/3 cgOverloadRejectedOpHoReqCg0 totalizer
1803/4 cgOverloadRejectedOpPageReqBtsCg0 totalizer
1803/5 cgOverloadRejectedOpSmsCbCg0 totalizer
1834/0 lapdOverloadRejectedOpSicd0 totalizer


4.1.8 BSC 3G
1507/0 e3OverloadRejectedOpPagingReq totalizer
1507/1 e3OverloadRejectedOpChannelReq totalizer
1507/2 e3OverloadRejectedOpEstablishInd totalizer
1507/3 e3OverloadRejectedOpHoReq totalizer
1507/4 e3OverloadRejectedOpPagingReqReject totalizer
1507/5 e3OverloadRejectedOpSmsCb totalizer
1508/0 pagingFilteredByBsc totalizer
3000/0 prLoadCne3OmuSbcMoy load
3000/0 prLoadCne3OmuSbcMax load
3000/0 prLoadCne3OmuSbcCum load
3000/0 prLoadCne3OmuSbcEch load
3001/0 prLoadCne3TmuSbcMoy load
3001/0 prLoadCne3TmuSbcMax load
3001/0 prLoadCne3TmuSbcCum load
3001/0 prLoadCne3TmuSbcEch load
3001/2 prLoadCne3TmuPmcMoy load
3001/2 prLoadCne3TmuPmcMax load
3001/2 prLoadCne3TmuPmcCum load
3001/2 prLoadCne3TmuPmcEch load
3004/0 e3PrMemCnOmuSbcMemCum value
3004/0 e3PrMemCnOmuSbcMemEch value

411--9001--125
3004/0 e3PrMemCnOmuSbcMemMoy value

3004/0 e3PrMemCnOmuSbcMemMax value
3004/1 e3PrMemCnOmuSbcSwapCum value
3004/1 e3PrMemCnOmuSbcSwapEch value
3004/1 e3PrMemCnOmuSbcSwapMoy value
3004/1 e3PrMemCnOmuSbcSwapMax value
3005/0 e3PrMemCnTmuSbcCum value
3005/0 e3PrMemCnTmuSbcEch value
3005/0 e3PrMemCnTmuSbcMoy value
3005/0 e3PrMemCnTmuSbcMax value
3005/2 e3PrMemCnTmuPmcCum value
3005/2 e3PrMemCnTmuPmcEch value
3005/2 e3PrMemCnTmuPmcMoy value
3005/2 e3PrMemCnTmuPmcMax value
3008/0 e3PrDiskCnOmuLdWCum value
3008/0 e3PrDiskCnOmuLdWEch value
3008/0 e3PrDiskCnOmuLdWMoy value
3008/0 e3PrDiskCnOmuLdWMax value
3008/1 e3PrDiskCnOmuLdRCum value
3008/1 e3PrDiskCnOmuLdREch value
3008/1 e3PrDiskCnOmuLdRMoy value
3008/1 e3PrDiskCnOmuLdRMax value
3008/2 e3PrDiskCnOmuMdWCum value
3008/2 e3PrDiskCnOmuMdWEch value
3008/2 e3PrDiskCnOmuMdWMoy value
3008/2 e3PrDiskCnOmuMdWMax value
3008/3 e3PrDiskCnOmuMdRCum value
3008/3 e3PrDiskCnOmuMdREch value
3008/3 e3PrDiskCnOmuMdRMoy value
3008/3 e3PrDiskCnOmuMdRMax value

4.1.9 BSC - Load of processor

1400/0 prLoadCpumMoy load
1400/0 prLoadCpumMax load
1400/0 prLoadCpumCum load
1400/0 prLoadCpumEch load
1400/0 prLoadCpueMoy load
1400/0 prLoadCpueMax load
1400/0 prLoadCpueCum load
1400/0 prLoadCpueEch load
1400/0 prLoadCpue1Moy load
1400/0 prLoadCpue1Max load
1400/0 prLoadCpue1Cum load
1400/0 prLoadCpue1Ech load
1400/0 prLoadCpue2Moy load
1400/0 prLoadCpue2Max load
1400/0 prLoadCpue2Cum load
1400/0 prLoadCpue2Ech load
1400/0 prLoadSicd0Moy load
1400/0 prLoadSicd0Max load
1400/0 prLoadSicd0Cum load
1400/0 prLoadSicd0Ech load

411--9001--125

1835/0 cardSynthLoadCpumMoy load
1835/0 cardSynthLoadCpumMax load
1835/0 cardSynthLoadCpumCum load
1835/0 cardSynthLoadCpumEch load
1835/0 cardSynthLoadCpue0Moy load
1835/0 cardSynthLoadCpue0Max load
1835/0 cardSynthLoadCpue0Cum load
1835/0 cardSynthLoadCpue0Ech load


1835/0 cardSynthLoadSicd0Moy load
1835/0 cardSynthLoadSicd0Max load
1835/0 cardSynthLoadSicd0Cum load
1835/0 cardSynthLoadSicd0Ech load

411--9001--125

4.1.10 CCCH Monitoring

1026/0 rachBusyCount totalizer
1026/0 rachBusyCountTs2 totalizer
1027/0 rachAccessCount totalizer
1027/0 rachAccessCountTs2 totalizer
1028/0 pchNoWait totalizer
1028/0 pchNoWaitTs2 totalizer
1029/0 pchOneWait totalizer
1029/0 pchOneWaitTs2 totalizer


1030/0 pchTwoWait totalizer
1030/0 pchTwoWaitTs2 totalizer
1031/0 pchMoreWait totalizer
1031/0 pchMoreWaitTs2 totalizer
1033/0 rachNonDecodedAvLevelCum value
1033/0 rachNonDecodedAvLevelEch value
1033/0 rachNonDecodedAvLevelMoy value
1033/0 rachNonDecodedAvLevelMax value
1033/0 rachNonDecodedAvLevelTs2Cum value
1033/0 rachNonDecodedAvLevelTs2Ech value
1033/0 rachNonDecodedAvLevelTs2Moy value
1033/0 rachNonDecodedAvLevelTs2Max value
1604/0 pchAveragedQueueLengthMoy load
1604/0 pchAveragedQueueLengthMax load
1604/0 pchAveragedQueueLengthCum load
1604/0 pchAveragedQueueLengthEch load
1604/0 pchAveragedQueueLengthTs2Moy load
1604/0 pchAveragedQueueLengthTs2Max load
1604/0 pchAveragedQueueLengthTs2Cum load
1604/0 pchAveragedQueueLengthTs2Ech load

411--9001--125

1605/0 pchQueuePagesDiscarded totalizer
1605/0 pchQueuePagesDiscardedTs2 totalizer
4.1.11 Channel mode

1044/0 signallingPhaseDurationCum value
1044/0 signallingPhaseDurationEch value
1044/0 signallingPhaseDurationMoy value
1044/0 signallingPhaseDurationMax value
1045/0 signallingPhaseDurationHighCum value
1045/0 signallingPhaseDurationHighEch value
1045/0 signallingPhaseDurationHighMoy value
1045/0 signallingPhaseDurationHighMax value
1197/0 channelActivateSpeechFullRate totalizer
1197/1 channelActivateSpeechEnhancedFullRate totalizer
1197/2 channelActivateSpeechAmrHr totalizer
1197/3 channelActivateSpeechAmrFr totalizer
1206/0 speechAlgoFallBack totalizer
1206/1 amrFrSpeechAlgoFallBack totalizer
1629/0 channelActivateSignallingFullRate totalizer
1629/1 channelActivateSignallingHalfRate totalizer
1705/0 channelActivateTchFrDataT16 totalizer


1706/0 channelActivateTchHrDataT16 totalizer
1707/0 channelActivateTchFrDataNT6000 totalizer
1708/0 channelActivateTchHrDataNT6000 totalizer
1709/0 channelActTchFrDataT totalizer
1710/0 channelActTchFrDataNT totalizer
1711/0 channelActTchHrDataT totalizer
1712/0 channelActTchHrDataNT totalizer
4.1.12 Dedicated channel assignement

1049/0 attemptedTchFrSeizures totalizer
1050/0 successfulTchFrSeizures totalizer
1055/0 assignFailure totalizer
1715/0 attemptedTchFrSeizuresMsDualb totalizer
1716/0 successfulTchFrSeizuresMsDualb totalizer
1799/0 assignToOtherBandOrZone totalizer
1841/0 assignRequestSdcchToTchChannel totalizer
1841/1 assignRequestOthers totalizer
1842/0 assignRequestAintSdcchToTchChannel totalizer
1842/1 assignRequestAintOthers totalizer

411--9001--125
4.1.13 Directed retry

1620/0 directedRetryUnsuccessNoBts totalizer
4.1.14 EDGE
1163/33 signallingReleaseCellTbcEdge totalizer
1164/33 trafficReleaseTbcEdge totalizer
2000/0 totalNumberOfEdgeTsMoy load
2000/0 totalNumberOfEdgeTsMax load
2000/0 totalNumberOfEdgeTsCum load
2000/0 totalNumberOfEdgeTsEch load
2000/0 totalNumberOfEdgeTsTrZoneMoy load
2000/0 totalNumberOfEdgeTsTrZoneMax load
2000/0 totalNumberOfEdgeTsTrZoneCum load
2000/0 totalNumberOfEdgeTsTrZoneEch load
2000/1 allocatedEdgeTsMoy load
2000/1 allocatedEdgeTsMax load
2000/1 allocatedEdgeTsCum load
2000/1 allocatedEdgeTsEch load
2000/1 allocatedEdgeTsTrZoneMoy load
2000/1 allocatedEdgeTsTrZoneMax load
2000/1 allocatedEdgeTsTrZoneCum load
2000/1 allocatedEdgeTsTrZoneEch load
2000/2 preemptedEdgeTsMoy load
2000/2 preemptedEdgeTsMax load
2000/2 preemptedEdgeTsCum load
2000/2 preemptedEdgeTsEch load
2000/2 preemptedEdgeTsTrZoneMoy load
2000/2 preemptedEdgeTsTrZoneMax load
2000/2 preemptedEdgeTsTrZoneCum load
2000/2 preemptedEdgeTsTrZoneEch load
2001/0 allocatedAbisJokerTSEdgeMoy load

2001/0 allocatedAbisJokerTSEdgeMax load

2001/0 allocatedAbisJokerTSEdgeCum load
2001/0 allocatedAbisJokerTSEdgeEch load
2001/0 allocatedAbisJokerTSEdgeTrZoneMoy load
2001/0 allocatedAbisJokerTSEdgeTrZoneMax load
2001/0 allocatedAbisJokerTSEdgeTrZoneCum load
2001/0 allocatedAbisJokerTSEdgeTrZoneEch load
2002/0 totalNumberOfEdgeTsCellMoy load
2002/0 totalNumberOfEdgeTsCellMax load
2002/0 totalNumberOfEdgeTsCellCum load
2002/0 totalNumberOfEdgeTsCellEch load
2002/1 allocatedEdgeTsCellMoy load
2002/1 allocatedEdgeTsCellMax load
2002/1 allocatedEdgeTsCellCum load
2002/1 allocatedEdgeTsCellEch load
2002/2 preemptedEdgeTsCellMoy load
2002/2 preemptedEdgeTsCellMax load
2002/2 preemptedEdgeTsCellCum load
2002/2 preemptedEdgeTsCellEch load
2003/0 allocatedAbisJokerTsCellMoy load
2003/0 allocatedAbisJokerTsCellMax load
2003/0 allocatedAbisJokerTsCellCum load
2003/0 allocatedAbisJokerTsCellEch load
4.1.15 Establishment
1191/0 channelRequestCause000 totalizer

411--9001--125

1192/0 immediateAssignmentSuccessCause000 totalizer
1193/0 estabIndicSignallingPagingRes totalizer
1193/1 estabIndicSignallingLocUpdate totalizer
1193/2 estabIndicSignallingReEstab totalizer
1193/3 estabIndicSignallingImsiDetach totalizer
1193/4 estabIndicSignallingMoc totalizer
1193/5 estabIndicSignallingEmergency totalizer
1193/6 estabIndicSignallingShortMsg totalizer
1193/7 estabIndicSignallingSuppService totalizer
1195/0 estabIndicSigPhase1 totalizer
1196/0 estabIndicSigPhase2 totalizer
1207/0 immediateAssignmentMultiband totalizer
1702/0 channelRequestExtended totalizer
1730/0 pagingResponse totalizer
1748/0 channelRequest totalizer
1749/0 immediateAssignmentSuccess totalizer
1750/0 estabIndicSignalling totalizer
4.1.16 Global handovers

1138/0 hoRequiredTchUplinkStrength totalizer
1138/1 hoRequiredTchDownlinkStrength totalizer
1138/10 hoRequiredTchDirectedRetry totalizer
1138/11 hoRequiredTchTdmaClass0 totalizer
1138/12 hoRequiredTchTdmaClass1 totalizer

1138/13 hoRequiredTchInterBtsOm totalizer

1138/14 hoRequiredTchTraffic totalizer
1138/15 hoRequiredTchTieringLargeToSmallPattern totalizer
1138/16 hoRequiredTchTieringSmallToLargePattern totalizer
1138/2 hoRequiredTchUplinkQuality totalizer
1138/3 hoRequiredTchDownlinkQuality totalizer
1138/4 hoRequiredTchDistance totalizer
1138/5 hoRequiredTchPowerBudgetQuality totalizer
1138/6 hoRequiredTchCapture totalizer
1138/7 hoRequiredTchIntraBtsOm totalizer
1138/8 hoRequiredTchIntraBtsUplink totalizer
1138/9 hoRequiredTchIntraBtsDownlink totalizer
1139/0 hoRequiredSdcchUplinkStrength totalizer
1139/1 hoRequiredSdcchDownlinkStrength totalizer
1139/13 hoRequiredSdcchInterBtsOm totalizer
1139/14 hoRequiredSdcchTraffic totalizer
1139/2 hoRequiredSdcchUplinkQuality totalizer
1139/3 hoRequiredSdcchDownlinkQuality totalizer
1139/4 hoRequiredSdcchDistance totalizer
1139/5 hoRequiredSdcchPowerBudget totalizer
1139/6 hoRequiredSdcchCapture totalizer
1139/7 hoRequiredSdcchIntraBtsOm totalizer
1139/8 hoRequiredSdcchIntraBtsUplink totalizer
1139/9 hoRequiredSdcchIntraBtsDownlink totalizer
1165/0 hoIndicationNotTreatedTchoke totalizer
1208/0 hoRequestOutgoingMbandEbandMsDualb totalizer
1209/0 hoSuccessOutgoingMbandEbandMsDualb totalizer
1776/0 hoRequiredTch totalizer
1777/0 hoRequiredSdcch totalizer
1780/0 hoSuccessOutgoingTch totalizer
1780/1 amrFrHoSuccessOutgoingTch totalizer
1780/2 amrHrHoSuccessOutgoingTch totalizer
1781/0 hoSuccessIncomingTch totalizer

411--9001--125
1782/0 hoBtsRejected totalizer

1783/0 hoRequestOutgoingMbandMbandMsDualb totalizer
1784/0 hoRequestOutgoingEbandEbandMsDualb totalizer
1785/0 hoRequestOutgoingEbandMbandMsDualb totalizer
1786/0 hoSuccessOutgoingMbandMbandMsDualb totalizer
1787/0 hoSuccessOutgoingEbandEbandMsDualb totalizer
1788/0 hoSuccessOutgoingEbandMbandMsDualb totalizer
1789/0 hoExecutionOutgoingMbandEbandMsDualb totalizer
1790/0 hoExecutionOutgoingMbandMbandMsDualb totalizer
1791/0 hoExecutionOutgoingEbandEbandMsDualb totalizer
1792/0 hoExecutionOutgoingEbandMbandMsDualb totalizer
4.1.17 GPRS
1086/0 gprsRachRejectedSicd0 totalizer
1087/0 gprsImmAssRejectedSicd0 totalizer


1088/0 gprsPagingRejectedSicd0 totalizer
1814/0 gprsPreemption totalizer
1815/0 gprsPreemptionNack totalizer
1821/0 allocatedCircuitTsCellMoy load
1821/0 allocatedCircuitTsCellMax load
1821/0 allocatedCircuitTsCellCum load
1821/0 allocatedCircuitTsCellEch load
1822/0 allocatedPacketTsCellMoy load
1822/0 allocatedPacketTsCellMax load
1822/0 allocatedPacketTsCellCum load
1822/0 allocatedPacketTsCellEch load
1822/1 totalNumberOfPacketTsCellMoy load
1822/1 totalNumberOfPacketTsCellMax load
1822/1 totalNumberOfPacketTsCellCum load
1822/1 totalNumberOfPacketTsCellEch load
1822/2 totalNumberOfPacketTsUsedForCircuitCellMoy load
1822/2 totalNumberOfPacketTsUsedForCircuitCellMax load
1822/2 totalNumberOfPacketTsUsedForCircuitCellCum load
1822/2 totalNumberOfPacketTsUsedForCircuitCellEch load
4.1.18 GPRS on TrZone

1812/0 allocatedCircuitTsMoy load

411--9001--125
1812/0 allocatedCircuitTsMax load

1812/0 allocatedCircuitTsCum load
1812/0 allocatedCircuitTsEch load
1812/0 allocatedCircuitTsTrZoneMoy load
1812/0 allocatedCircuitTsTrZoneMax load
1812/0 allocatedCircuitTsTrZoneCum load
1812/0 allocatedCircuitTsTrZoneEch load
1813/0 allocatedPacketTsMoy load
1813/0 allocatedPacketTsMax load
1813/0 allocatedPacketTsCum load
1813/0 allocatedPacketTsEch load
1813/0 allocatedPacketTsTrZoneMoy load
1813/0 allocatedPacketTsTrZoneMax load
1813/0 allocatedPacketTsTrZoneCum load
1813/0 allocatedPacketTsTrZoneEch load
1813/1 totalNumberOfPacketTsMoy load
1813/1 totalNumberOfPacketTsMax load
1813/1 totalNumberOfPacketTsCum load
1813/1 totalNumberOfPacketTsEch load
1813/1 totalNumberOfPacketTsTrZoneMoy load
1813/1 totalNumberOfPacketTsTrZoneMax load
1813/1 totalNumberOfPacketTsTrZoneCum load
1813/1 totalNumberOfPacketTsTrZoneEch load
1813/2 totalNumberOfPacketTsUsedForCircuitMoy load
1813/2 totalNumberOfPacketTsUsedForCircuitMax load
1813/2 totalNumberOfPacketTsUsedForCircuitCum load
1813/2 totalNumberOfPacketTsUsedForCircuitEch load
1813/2 totalNumberOfPacketTsUsedForCircuitTrZoneMoy load
1813/2 totalNumberOfPacketTsUsedForCircuitTrZoneMax load
1813/2 totalNumberOfPacketTsUsedForCircuitTrZoneCum load
1813/2 totalNumberOfPacketTsUsedForCircuitTrZoneEch load

4.1.19 Inter-- bss handovers

1066/0 hoExecutionOutgoingInterBss totalizer
1066/1 hoExecutionOutgoingInterBssForDirectedRetry totalizer
1068/0 hoSuccessOutgoingInterBss totalizer
1068/1 hoSuccessOutgoingInterBssForDirectedRetry totalizer
1070/0 hoRequestIncomingInterBss totalizer
1072/0 hoExecutionIncomingInterBss totalizer
1074/0 hoSuccessIncomingInterBss totalizer
1076/0 hoRequestOutgoingInterBss totalizer
1078/0 hoSuccessOutgoingFirstInter totalizer
1136/0 hoUnsuccessReestOutgoingInterBssTch totalizer
1141/0 hoExecutionOutgoingInterBssSdcch totalizer
1143/0 hoSuccessOutgoingInterBssSdcch totalizer
1145/0 hoRequestIncomingInterBssSdcch totalizer
1147/0 hoExecutionIncomingInterBssSdcch totalizer
1149/0 hoSuccessIncomingInterBssSdcch totalizer
1151/0 hoRequestOutgoingInterBssSdcch totalizer
1153/0 hoSuccessOutgoingFirstInterSdcch totalizer
1159/0 hoUnsuccessReestOutgoingInterBssSdcch totalizer
1169/0 hoUnsuccessOutgoingInterBssNAttemptTch totalizer
1170/0 hoUnsuccessOutgoingInterBssNAttemptSdcch totalizer
1760/0 hoFailureIncomingInterBssTchRadioLack totalizer
1760/1 hoFailureIncomingInterBssTchTerrestLack totalizer
1760/2 hoFailureIncomingInterBssTchHoNotAllowed totalizer
1760/3 hoFailureIncomingInterBssTchChannelActivateNack totalizer
1760/4 hoFailureIncomingInterBssTchTchnAckTimerExp totalizer
1760/5 hoFailureIncomingInterBssTchCICIncompatible totalizer
1761/0 hoFailureIncomingInterBssSdcchRadioLack totalizer
1761/1 hoFailureIncomingInterBssSdcchTerrestLack totalizer
1761/2 hoFailureIncomingInterBssSdcchHoNotAllowed totalizer
1761/3 hoFailureIncomingInterBssSdcchChannelActivateNack totalizer
1761/4 hoFailureIncomingInterBssSdcchTchnAckTimerExp totalizer

411--9001--125
1764/0 hoFailureOutgoingInterBssTchRadioLack totalizer

1764/1 hoFailureOutgoingInterBssTchTerrestLack totalizer
1764/2 hoFailureOutgoingInterBssTchHoNotAllowed totalizer
1764/3 hoFailureOutgoingInterBssTchT7TimerExp totalizer
1764/4 hoFailureOutgoingInterBssTchOtherCases totalizer
1764/5 hoFailureOutgoingInterBssTchIncompatible totalizer
1765/0 hoFailureOutgoingInterBssSdcchRadioLack totalizer
1765/1 hoFailureOutgoingInterBssSdcchTerrestLack totalizer
1765/2 hoFailureOutgoingInterBssSdcchHoNotAllowed totalizer
1765/3 hoFailureOutgoingInterBssSdcchT7TimerExp totalizer
1765/4 hoFailureOutgoingInterBssSdcchOtherCase totalizer
1770/0 hoUnsuccessOutgoingInterCellTchReturnOldChannel totalizer
1770/1 hoUnsuccessOutgoingInterCellTchT3103TimerExp totalizer
1770/2 hoUnsuccessOutgoingInterCellTchOtherCases totalizer
1771/0 hoUnsuccessOutgoingInterCellSdcchReturnOldChannel totalizer
1771/1 hoUnsuccessOutgoingInterCellSdcchT3103TimerExp totalizer
1771/2 hoUnsuccessOutgoingInterCellSdcchOtherCases totalizer
1774/0 hoUnsuccessIncomingInterBssTchTimerExp totalizer
1774/1 hoUnsuccessIncomingInterBssTchOtherCases totalizer
1775/0 hoUnsuccessIncomingInterBssSdcchTimerExp totalizer
1775/1 hoUnsuccessIncomingInterBssSdcchOtherCases totalizer
4.1.20 Interferences
1619/0 channelAveragedIdlePerInterfBand0Cum value
1619/0 channelAveragedIdlePerInterfBand0Ech value

1619/0 channelAveragedIdlePerInterfBand0Moy value
1619/0 channelAveragedIdlePerInterfBand0Max value


4.1.21 Intra-- bss handovers

1065/0 hoExecutionOutgoingIntraBss totalizer
1065/1 hoExecutionOutgoingIntraBssForDirectedRetry totalizer
1067/0 hoSuccessOutgoingIntraBss totalizer
1067/1 hoSuccessOutgoingIntraBssForDirectedRetry totalizer
1069/0 hoRequestIncomingIntraBss totalizer
1071/0 hoExecutionIncomingIntraBss totalizer
1073/0 hoSuccessIncomingIntraBss totalizer
1075/0 hoRequestOutgoingIntraBss totalizer
1077/0 hoSuccessOutgoingFirstIntra totalizer
1135/0 hoUnsuccessReestOutgoingIntraBssTch totalizer
1137/0 hoUnsuccessReestIncomingIntraBssTch totalizer
1140/0 hoExecutionOutgoingIntraBssSdcch totalizer
1142/0 hoSuccessOutgoingIntraBssSdcch totalizer
1144/0 hoRequestIncomingIntraBssSdcch totalizer
1146/0 hoExecutionIncomingIntraBssSdcch totalizer
1148/0 hoSuccessIncomingIntraBssSdcch totalizer
1150/0 hoRequestOutgoingIntraBssSdcch totalizer
1152/0 hoSuccessOutgoingFirstIntraSdcch totalizer

411--9001--125
1158/0 hoUnsuccessReestOutgoingIntraBssSdcch totalizer

1160/0 hoUnsuccessReestIncomingIntraBssSdcch totalizer
1167/0 hoUnsuccessOutgoingIntraBssNAttemptTch totalizer
1168/0 hoUnsuccessOutgoingIntraBssNAttemptSdcch totalizer
1758/0 hoFailureIncomingIntraBssTchRadioLack totalizer
1758/1 hoFailureIncomingIntraBssTchHoNotAllowed totalizer
1758/2 hoFailureIncomingIntraBssTchChannelActivateNack totalizer
1758/3 hoFailureIncomingIntraBssTchTchnAckTimerExp totalizer
1758/4 hoFailureIncomingIntraBssTchIncompatible totalizer
1759/0 hoFailureIncomingIntraBssSdcchRadioLack totalizer
1759/1 hoFailureIncomingIntraBssSdcchHoNotAllowed totalizer
1759/2 hoFailureIncomingIntraBssSdcchChannelActivateNack totalizer
1759/3 hoFailureIncomingIntraBssSdcchTchnAckTimerExp totalizer
1762/0 hoFailureOutgoingIntraBssTchRadioLack totalizer
1762/1 hoFailureOutgoingIntraBssTchHoNotAllowed totalizer
1762/2 hoFailureOutgoingIntraBssTchChannelActivateNack totalizer
1762/3 hoFailureOutgoingIntraBssTchTchnAckTimerExp totalizer
1762/4 hoFailureOutgoingIntraBssTchIncompatible totalizer
1763/0 hoFailureOutgoingIntraBssSdcchRadioLack totalizer
1763/1 hoFailureOutgoingIntraBssSdcchHoNotAllowed totalizer
1763/2 hoFailureOutgoingIntraBssSdcchChannelActivateNack totalizer
1763/3 hoFailureOutgoingIntraBssSdcchTchnAckTimerExp totalizer
1768/0 hoUnsuccessOutgoingIntraCellTchReturnOldChannel totalizer
1768/1 hoUnsuccessOutgoingIntraCellTchT3103TimerExp totalizer
1769/0 hoUnsuccessOutgoingIntraCellSdcchReturnOldChannel totalizer
1769/1 hoUnsuccessOutgoingIntraCellSdcchT3103TimerExp totalizer
1772/0 hoUnsuccessIncomingIntraCellTchReturnOldChannel totalizer
1772/1 hoUnsuccessIncomingIntraCellTchT3103TimerExp totalizer
1773/0 hoUnsuccessIncomingIntraCellSdcchReturnOldChannel totalizer
1773/1 hoUnsuccessIncomingIntraCellSdcchT3103TimerExp totalizer
1793/0 hoRequestIncomingIntraBssTchMsDualb totalizer
1794/0 hoExecutionIncomingIntraBssTchMsDualb totalizer
1795/0 hoSuccessIncomingIntraBssTchMsDualb totalizer

4.1.22 Intra--cell handovers

1081/0 hoRequestIntraBts totalizer
1082/0 hoExecutionIntraBts totalizer
1083/0 hoSuccessIntraBts totalizer
1134/0 hoUnsuccessReestIntraBtsTch totalizer
1154/0 hoRequestIntraBtsSdcch totalizer
1155/0 hoExecutionIntraBtsSdcch totalizer
1156/0 hoSuccessIntraBtsSdcch totalizer
1157/0 hoUnsuccessReestIntraBtsSdcch totalizer
1756/0 hoFailureIntraBtsTchRadioLack totalizer
1756/1 hoFailureIntraBtsTchChannelActivateNack totalizer
1756/2 hoFailureIntraBtsTchTchnAckTimerExp totalizer
1757/0 hoFailureIntraBtsSdcchRadioLack totalizer
1757/1 hoFailureIntraBtsSdcchChannelActivateNack totalizer
1757/2 hoFailureIntraBtsSdcchTchnAckTimerExp totalizer
1796/0 hoRequestIntraBtsMsDualb totalizer
1797/0 hoExecutionIntraBtsMsDualb totalizer
1798/0 hoSuccessIntraBtsMsDualb totalizer
1801/0 hoFailureTieringTchNorrLargeToSmallPattern totalizer
1801/1 hoFailureTieringTchNorrSmallToLargePattern totalizer
1802/0 hoSuccessTieringTchLargeToSmallPattern totalizer
1802/1 hoSuccessTieringTchSmallToLargePattern totalizer
4.1.23 Layer One Management

1198/0 downlinkPowerCtrlMaxTchCum value
1198/0 downlinkPowerCtrlMaxTchEch value
1198/0 downlinkPowerCtrlMaxTchMoy value
1198/0 downlinkPowerCtrlMaxTchMax value
1199/0 uplinkPowerCtrlMaxTchCum value
1199/0 uplinkPowerCtrlMaxTchEch value
1199/0 uplinkPowerCtrlMaxTchMoy value

411--9001--125
1199/0 uplinkPowerCtrlMaxTchMax value

1601/0 downlinkPowerCtrlMaxSdcchCum value
1601/0 downlinkPowerCtrlMaxSdcchEch value
1601/0 downlinkPowerCtrlMaxSdcchMoy value
1601/0 downlinkPowerCtrlMaxSdcchMax value
1602/0 uplinkPowerCtrlMaxSdcchCum value
1602/0 uplinkPowerCtrlMaxSdcchEch value
1602/0 uplinkPowerCtrlMaxSdcchMoy value
1602/0 uplinkPowerCtrlMaxSdcchMax value
1805/0 msPowerIncControl totalizer
1806/0 msPowerDecControl totalizer
1807/0 bsPowerIncControl totalizer
1808/0 bsPowerDecControl totalizer
1816/0 pathBalanceCum value
1816/0 pathBalanceEch value
1816/0 pathBalanceMoy value
1816/0 pathBalanceMax value
1817/0 burstToTransmit totalizer
1818/0 burstTransmitted totalizer
1819/0 burstToTransmitReqPwr totalizer
1820/0 STPMAttenuation totalizer
2025/0 downgradedL1mModeOnClassmark totalizer
4.1.24 Layer One Management on TrZone

1600/0 connectionDurationTchCum value
1600/0 connectionDurationTchEch value
1600/0 connectionDurationTchMoy value
1600/0 connectionDurationTchMax value
1600/0 connectionDurationTchTrZoneCum value
1600/0 connectionDurationTchTrZoneEch value
1600/0 connectionDurationTchTrZoneMoy value
1600/0 connectionDurationTchTrZoneMax value

1603/0 connectionDurationSdcchCum value

1603/0 connectionDurationSdcchEch value
1603/0 connectionDurationSdcchMoy value
1603/0 connectionDurationSdcchMax value
1603/0 connectionDurationSdcchTrZoneCum value
1603/0 connectionDurationSdcchTrZoneEch value
1603/0 connectionDurationSdcchTrZoneMoy value
1603/0 connectionDurationSdcchTrZoneMax value
1622/0 msLostMeasurements totalizer
1622/0 msLostMeasurementsTrZone totalizer
1623/0 rxLevDownLink totalizer
1623/0 rxLevDownLinkTrZone totalizer
1624/0 rxLevUpLink totalizer
1624/0 rxLevUpLinkTrZone totalizer
1625/0 rxQualDownLink totalizer

1625/0 rxQualDownLinkTrZone totalizer
1626/0 rxQualUpLink totalizer
1626/0 rxQualUpLinkTrZone totalizer
1809/0 timingAdvanceAverage totalizer
1809/0 timingAdvanceAverageTrZone totalizer
1809/1 timingAdvanceMaximum totalizer
1809/1 timingAdvanceMaximumTrZone totalizer
4.1.25 Neighbor cells

1200/0 hoNcellsExecution totalizer
1202/0 hoNcellsExecutionSdcch totalizer
1204/0 hoNcellsUnsuccessTchChlR totalizer
1204/1 hoNcellsUnsuccessTchTimer totalizer
1204/2 hoNcellsUnsuccessTchOther totalizer
1205/0 hoNcellsUnsuccessSdcchChlR totalizer
1205/1 hoNcellsUnsuccessSdcchTimer totalizer

411--9001--125
1205/2 hoNcellsUnsuccessSdcchOther totalizer

1839/0 hoNcellsRequestOutgoingUplinkStrength totalizer
1839/1 hoNcellsRequestOutgoingDownlinkStrength totalizer
1839/2 hoNcellsRequestOutgoingUplinkQuality totalizer
1839/3 hoNcellsRequestOutgoingDownlinkQuality totalizer
1839/4 hoNcellsRequestOutgoingDistance totalizer
1839/5 hoNcellsRequestOutgoingPowerBudget totalizer
1839/6 hoNcellsRequestOutgoingDirectedRetry totalizer
1839/7 hoNcellsRequestOutgoingInterCellOM totalizer
1839/8 hoNcellsRequestOutgoingTraffic totalizer
1839/9 hoNcellsRequestOutgoingOther totalizer
1840/0 hoNcellsSuccessOutgoingUplinkStrength totalizer
1840/1 hoNcellsSuccessOutgoingDownlinkStrength totalizer
1840/2 hoNcellsSuccessOutgoingUplinkQuality totalizer
1840/3 hoNcellsSuccessOutgoingDownlinkQuality totalizer
1840/4 hoNcellsSuccessOutgoingDistance totalizer
1840/5 hoNcellsSuccessOutgoingPowerBudget totalizer
1840/6 hoNcellsSuccessOutgoingDirectedRetry totalizer
1840/7 hoNcellsSuccessOutgoingInterCellOM totalizer
1840/8 hoNcellsSuccessOutgoingTraffic totalizer
1840/9 hoNcellsSuccessOutgoingOther totalizer
4.1.26 OMC interface

1115/0 omcLinkSwitchOver totalizer
1300/0 omcOutputIFrame totalizer
1301/0 omcInputIFrame totalizer
1302/0 omcOutputRepeatedIFrame totalizer
1303/0 omcInputRepeatedIFrame totalizer
1304/0 omcOutputRnrFrame totalizer
1305/0 omcInputRnrFrame totalizer

4.1.27 PCM
1114/0 pcmUnavailabilityCum value
1114/0 pcmUnavailabilityEch value
1114/0 pcmUnavailabilityMoy value
1114/0 pcmUnavailabilityMax value
1755/0 pcmFaultExternal totalizer
1755/1 pcmFaultInternal totalizer
1755/2 pcmFaultDDTIBoard totalizer
1755/3 pcmFaultOutOfService totalizer
4.1.28 Releases of communications in signalling phase

1161/0 immediateAssignmentRejectTraffMsc totalizer
1161/1 immediateAssignmentRejectRadioRes totalizer
1161/2 immediateAssignmentRejectChanActNack totalizer
1161/3 immediateAssignmentRejectChanActTimmack totalizer
1161/5 immediateAssignmentRejectOverload totalizer
1161/6 immediateAssignmentRejectTimingAdv totalizer
1161/7 immediateAssignmentRejectOthers totalizer
1162/0 signallingReleaseNoBtsSccpDiscInd totalizer
1162/1 signallingReleaseNoBtsReset totalizer
1162/26 signallingReleaseNoBtsTsccRel totalizer
1162/27 signallingReleaseNoBtsBadDataInd totalizer
1162/28 signallingReleaseNoBtsOthers totalizer
1162/3 signallingReleaseNoBtsSccpDataRefusal totalizer
1163/0 signallingReleaseBtsSccpDiscInd totalizer
1163/1 signallingReleaseBtsReset totalizer
1163/10 signallingReleaseBtsCicRemovalEqptFail totalizer
1163/11 signallingReleaseBtsOmRadioChanBloc totalizer
1163/12 signallingReleaseBtsCallClearing totalizer
1163/13 signallingReleaseBtsCnxFailRadioIntFail totalizer
1163/14 signallingReleaseBtsCnxFailRadioLinkFail totalizer

411--9001--125
1163/16 signallingReleaseBtsReleaseInd totalizer

1163/17 signallingReleaseBtsErrorIndT200 totalizer
1163/18 signallingReleaseBtsErrorIndDm totalizer
1163/19 signallingReleaseBtsErrorIndSeq totalizer
1163/2 signallingReleaseBtsResetCirc totalizer
1163/20 signallingReleaseBtsClearCommand totalizer
1163/21 signallingReleaseBtsRfResInd totalizer
1163/22 signallingReleaseBtsSwitchOver totalizer
1163/23 signallingReleaseBtsTmodMs totalizer
1163/24 signallingReleaseBtsT3103 totalizer
1163/28 signallingReleaseBtsOthers totalizer
1163/3 signallingReleaseBtsSccpDataRefusal totalizer
1163/32 signallingReleaseBtsCnxFailRemTransFail totalizer
1163/4 signallingReleaseBtsIncFirstL3 totalizer
1163/6 signallingReleaseBtsT3107CircDown totalizer
1163/7 signallingReleaseBtsOmTsRemoval totalizer
1163/8 signallingReleaseBtsTsRemovalEqptFail totalizer
1163/9 signallingReleaseBtsOmCicRemoval totalizer
1751/0 immediateAssignmentReject totalizer
1752/0 signallingReleaseNoBts totalizer
1753/0 signallingReleaseBts totalizer
1778/0 signallingAbnormalReleaseCell totalizer
1804/0 deleteIndication totalizer
4.1.29 Releases of communications in traffic phase

1164/0 trafficReleaseSccpDiscInd totalizer
1164/1 trafficReleaseReset totalizer
1164/10 trafficReleaseCicRemovalEqptFail totalizer
1164/11 trafficReleaseOmRadioChanBloc totalizer

1164/12 trafficReleaseCallClearing totalizer

1164/13 trafficReleaseCnxFailRadioIntFail totalizer
1164/14 trafficReleaseCnxFailRadioLinkFail totalizer
1164/16 trafficReleaseReleaseInd totalizer
1164/17 trafficReleaseErrorIndT200 totalizer
1164/18 trafficReleaseErrorIndDm totalizer
1164/19 trafficReleaseErrorIndSeq totalizer
1164/2 trafficReleaseResetCirc totalizer
1164/20 trafficReleaseClearCommand totalizer
1164/21 trafficReleaseRfResInd totalizer
1164/23 trafficReleaseTmodMs totalizer
1164/24 trafficReleaseT3103 totalizer
1164/25 trafficReleaseT8 totalizer
1164/28 trafficReleaseOthers totalizer
1164/3 trafficReleaseSccpDataRefusal totalizer
1164/31 trafficReleaseSysInfoFail totalizer
1164/32 trafficReleaseCnxFailRemTransFail totalizer
1164/6 trafficReleaseT3107CircDown totalizer
1164/7 trafficReleaseOmTsRemoval totalizer
1164/8 trafficReleaseTsRemovalEqptFail totalizer
1164/9 trafficReleaseOmCicRemoval totalizer
1754/0 trafficRelease totalizer
1779/0 trafficAbnormalRelease totalizer
4.1.30 SDCCH allocations on TrZone

1060/0 allSdcchAllocatedTimeCum value
1060/0 allSdcchAllocatedTimeEch value
1060/0 allSdcchAllocatedTimeMoy value
1060/0 allSdcchAllocatedTimeMax value
1060/0 allSdcchAllocatedTimeTrZoneCum value
1060/0 allSdcchAllocatedTimeTrZoneEch value
1060/0 allSdcchAllocatedTimeTrZoneMoy value

411--9001--125
1060/0 allSdcchAllocatedTimeTrZoneMax value

1606/0 sdcchAllocated totalizer
1606/0 sdcchAllocatedTrZone totalizer
1607/0 sdcchAveragedUsedMoy load
1607/0 sdcchAveragedUsedMax load
1607/0 sdcchAveragedUsedCum load
1607/0 sdcchAveragedUsedEch load
1607/0 sdcchAveragedUsedTrZoneMoy load
1607/0 sdcchAveragedUsedTrZoneMax load
1607/0 sdcchAveragedUsedTrZoneCum load
1607/0 sdcchAveragedUsedTrZoneEch load
1608/0 sdcchRessourceFailure totalizer
1608/0 sdcchRessourceFailureTrZone totalizer
1701/0 sdcchAveragedAvailableMoy load
1701/0 sdcchAveragedAvailableMax load
1701/0 sdcchAveragedAvailableCum load
1701/0 sdcchAveragedAvailableEch load
1701/0 sdcchAveragedAvailableTrZoneMoy load
1701/0 sdcchAveragedAvailableTrZoneMax load
1701/0 sdcchAveragedAvailableTrZoneCum load
1701/0 sdcchAveragedAvailableTrZoneEch load
1811/0 sdcchAverageConfiguratedMoy load
1811/0 sdcchAverageConfiguratedMax load
1811/0 sdcchAverageConfiguratedCum load
1811/0 sdcchAverageConfiguratedEch load
1811/0 sdcchAverageConfiguratedTrZoneMoy load
1811/0 sdcchAverageConfiguratedTrZoneMax load
1811/0 sdcchAverageConfiguratedTrZoneCum load
1811/0 sdcchAverageConfiguratedTrZoneEch load
4.1.31 SMS
1621/0 sapi3SessionEstablishment totalizer

4.1.32 TCH allocations

1616/0 tchAveragedQueueLengthHighPriorityMoy load
1616/0 tchAveragedQueueLengthHighPriorityMax load
1616/0 tchAveragedQueueLengthHighPriorityCum load
1616/0 tchAveragedQueueLengthHighPriorityEch load
1616/1 tchAveragedQueueLengthOtherPriorityMoy load
1616/1 tchAveragedQueueLengthOtherPriorityMax load
1616/1 tchAveragedQueueLengthOtherPriorityCum load
1616/1 tchAveragedQueueLengthOtherPriorityEch load
1617/0 tchQueuingExpirationHighPriority totalizer
1617/1 tchQueuingExpirationOtherPriority totalizer
1618/0 tchQueuingDurationHighPriorityCum value
1618/0 tchQueuingDurationHighPriorityEch value
1618/0 tchQueuingDurationHighPriorityMoy value
1618/0 tchQueuingDurationHighPriorityMax value
1618/1 tchQueuingDurationOtherPriorityCum value
1618/1 tchQueuingDurationOtherPriorityEch value
1618/1 tchQueuingDurationOtherPriorityMoy value
1618/1 tchQueuingDurationOtherPriorityMax value
1714/0 btsOverloadDurationCum value
1714/0 btsOverloadDurationEch value
1714/0 btsOverloadDurationMoy value
1714/0 btsOverloadDurationMax value
1726/0 dataNtRateFbTchResLack totalizer
1726/1 dataNtRateFbTchConfNotAllowed totalizer
1823/0 allTchFrAllocatedTimeCellCum value
1823/0 allTchFrAllocatedTimeCellEch value
1823/0 allTchFrAllocatedTimeCellMoy value
1823/0 allTchFrAllocatedTimeCellMax value
1824/0 tchFrAveragedUsedTchAllocationCellMoy load
1824/0 tchFrAveragedUsedTchAllocationCellMax load
1824/0 tchFrAveragedUsedTchAllocationCellCum load

411--9001--125
1824/0 tchFrAveragedUsedTchAllocationCellEch load

1824/1 tchFrAveragedUsedPrimoAllocationCellMoy load
1824/1 tchFrAveragedUsedPrimoAllocationCellMax load
1824/1 tchFrAveragedUsedPrimoAllocationCellCum load
1824/1 tchFrAveragedUsedPrimoAllocationCellEch load
1824/2 tchFrAveragedUsedOverflowAllocationCellMoy load
1824/2 tchFrAveragedUsedOverflowAllocationCellMax load
1824/2 tchFrAveragedUsedOverflowAllocationCellCum load
1824/2 tchFrAveragedUsedOverflowAllocationCellEch load
1825/0 tchFrAveragedAvailableCellMoy load
1825/0 tchFrAveragedAvailableCellMax load
1825/0 tchFrAveragedAvailableCellCum load
1825/0 tchFrAveragedAvailableCellEch load
1826/0 tchFrAveragedUsedCellMoy load
1826/0 tchFrAveragedUsedCellMax load
1826/0 tchFrAveragedUsedCellCum load
1826/0 tchFrAveragedUsedCellEch load
1827/0 tchFrAverageConfiguratedCellMoy load
1827/0 tchFrAverageConfiguratedCellMax load
1827/0 tchFrAverageConfiguratedCellCum load
1827/0 tchFrAverageConfiguratedCellEch load
1828/0 tchHrAveragedUsedCellMoy load
1828/0 tchHrAveragedUsedCellMax load
1828/0 tchHrAveragedUsedCellCum load
1828/0 tchHrAveragedUsedCellEch load
1828/1 tchHrAveragedUsedWpsCellMoy load
1828/1 tchHrAveragedUsedWpsCellMax load
1828/1 tchHrAveragedUsedWpsCellCum load
1828/1 tchHrAveragedUsedWpsCellEch load
1829/0 tchHrAveragedUsedNscCellMoy load
1829/0 tchHrAveragedUsedNscCellMax load
1829/0 tchHrAveragedUsedNscCellCum load
1829/0 tchHrAveragedUsedNscCellEch load

4.1.33 TCH allocations on TrZone

1057/0 allTchFrAllocatedTimeCum value
1057/0 allTchFrAllocatedTimeEch value
1057/0 allTchFrAllocatedTimeMoy value
1057/0 allTchFrAllocatedTimeMax value
1057/0 allTchFrAllocatedTimeTrZoneCum value
1057/0 allTchFrAllocatedTimeTrZoneEch value
1057/0 allTchFrAllocatedTimeTrZoneMoy value
1057/0 allTchFrAllocatedTimeTrZoneMax value
1609/0 tchFrAllocatedTchAllocation totalizer
1609/0 tchFrAllocatedTchAllocationTrZone totalizer
1609/1 tchFrAllocatedPrimoAllocation totalizer
1609/1 tchFrAllocatedPrimoAllocationTrZone totalizer
1609/2 tchFrAllocatedOverflowAllocation totalizer
1609/2 tchFrAllocatedOverflowAllocationTrZone totalizer
1610/0 tchHrAllocatedTchAllocation totalizer
1610/0 tchHrAllocatedTchAllocationTrZone totalizer
1611/0 tchFrAveragedUsedTchAllocationMoy load
1611/0 tchFrAveragedUsedTchAllocationMax load
1611/0 tchFrAveragedUsedTchAllocationCum load
1611/0 tchFrAveragedUsedTchAllocationEch load
1611/0 tchFrAveragedUsedTchAllocationTrZoneMoy load
1611/0 tchFrAveragedUsedTchAllocationTrZoneMax load
1611/0 tchFrAveragedUsedTchAllocationTrZoneCum load
1611/0 tchFrAveragedUsedTchAllocationTrZoneEch load
1611/1 tchFrAveragedUsedPrimoAllocationMoy load
1611/1 tchFrAveragedUsedPrimoAllocationMax load
1611/1 tchFrAveragedUsedPrimoAllocationCum load
1611/1 tchFrAveragedUsedPrimoAllocationEch load
1611/1 tchFrAveragedUsedPrimoAllocationTrZoneMoy load
1611/1 tchFrAveragedUsedPrimoAllocationTrZoneMax load
1611/1 tchFrAveragedUsedPrimoAllocationTrZoneCum load

411--9001--125
1611/1 tchFrAveragedUsedPrimoAllocationTrZoneEch load

1611/2 tchFrAveragedUsedOverflowAllocationMoy load
1611/2 tchFrAveragedUsedOverflowAllocationMax load
1611/2 tchFrAveragedUsedOverflowAllocationCum load
1611/2 tchFrAveragedUsedOverflowAllocationEch load
1611/2 tchFrAveragedUsedOverflowAllocationTrZoneMoy load
1611/2 tchFrAveragedUsedOverflowAllocationTrZoneMax load
1611/2 tchFrAveragedUsedOverflowAllocationTrZoneCum load
1611/2 tchFrAveragedUsedOverflowAllocationTrZoneEch load
1612/0 tchHrAveragedUsedTchAllocationMoy load
1612/0 tchHrAveragedUsedTchAllocationMax load
1612/0 tchHrAveragedUsedTchAllocationCum load
1612/0 tchHrAveragedUsedTchAllocationEch load
1612/0 tchHrAveragedUsedTchAllocationTrZoneMoy load
1612/0 tchHrAveragedUsedTchAllocationTrZoneMax load
1612/0 tchHrAveragedUsedTchAllocationTrZoneCum load
1612/0 tchHrAveragedUsedTchAllocationTrZoneEch load
1613/0 tchFrRessourceFailure totalizer
1613/0 tchFrRessourceFailureTrZone totalizer
1614/0 tchHrRessourceFailure totalizer
1614/0 tchHrRessourceFailureTrZone totalizer
1700/0 tchFrAveragedAvailableMoy load
1700/0 tchFrAveragedAvailableMax load
1700/0 tchFrAveragedAvailableCum load
1700/0 tchFrAveragedAvailableEch load
1700/0 tchFrAveragedAvailableTrZoneMoy load
1700/0 tchFrAveragedAvailableTrZoneMax load
1700/0 tchFrAveragedAvailableTrZoneCum load
1700/0 tchFrAveragedAvailableTrZoneEch load
1744/0 tchFrAllocated totalizer
1744/0 tchFrAllocatedTrZone totalizer
1745/0 tchHrAllocated totalizer
1745/0 tchHrAllocatedTrZone totalizer

1746/0 tchFrAveragedUsedMoy load

1746/0 tchFrAveragedUsedMax load
1746/0 tchFrAveragedUsedCum load
1746/0 tchFrAveragedUsedEch load
1746/0 tchFrAveragedUsedTrZoneMoy load
1746/0 tchFrAveragedUsedTrZoneMax load
1746/0 tchFrAveragedUsedTrZoneCum load
1746/0 tchFrAveragedUsedTrZoneEch load
1747/0 tchHrAveragedUsedMoy load
1747/0 tchHrAveragedUsedMax load
1747/0 tchHrAveragedUsedCum load
1747/0 tchHrAveragedUsedEch load
1747/0 tchHrAveragedUsedTrZoneMoy load
1747/0 tchHrAveragedUsedTrZoneMax load
1747/0 tchHrAveragedUsedTrZoneCum load
1747/0 tchHrAveragedUsedTrZoneEch load
1810/0 tchFrAverageConfiguratedMoy load
1810/0 tchFrAverageConfiguratedMax load
1810/0 tchFrAverageConfiguratedCum load
1810/0 tchFrAverageConfiguratedEch load
1810/0 tchFrAverageConfiguratedTrZoneMoy load
1810/0 tchFrAverageConfiguratedTrZoneMax load
1810/0 tchFrAverageConfiguratedTrZoneCum load
1810/0 tchFrAverageConfiguratedTrZoneEch load
2096/0 saicTchSuccessfullyAssigned totalizer
2096/0 saicTchSuccessfullyAssignedTrZone totalizer
4.1.34 WPS
1609/3 tchFrAllocatedWps totalizer
1609/3 tchFrAllocatedWpsTrZone totalizer
1610/1 tchHrAllocatedWps totalizer
1610/1 tchHrAllocatedWpsTrZone totalizer

411--9001--125
1611/3 tchFrAveragedUsedWpsMoy load

1611/3 tchFrAveragedUsedWpsMax load
1611/3 tchFrAveragedUsedWpsCum load
1611/3 tchFrAveragedUsedWpsEch load
1611/3 tchFrAveragedUsedWpsTrZoneMoy load
1611/3 tchFrAveragedUsedWpsTrZoneMax load
1611/3 tchFrAveragedUsedWpsTrZoneCum load
1611/3 tchFrAveragedUsedWpsTrZoneEch load
1612/1 tchHrAveragedUsedWpsMoy load
1612/1 tchHrAveragedUsedWpsMax load
1612/1 tchHrAveragedUsedWpsCum load
1612/1 tchHrAveragedUsedWpsEch load
1612/1 tchHrAveragedUsedWpsTrZoneMoy load
1612/1 tchHrAveragedUsedWpsTrZoneMax load
1612/1 tchHrAveragedUsedWpsTrZoneCum load
1612/1 tchHrAveragedUsedWpsTrZoneEch load
1824/3 tchFrAveragedUsedWpsCellMoy load
1824/3 tchFrAveragedUsedWpsCellMax load
1824/3 tchFrAveragedUsedWpsCellCum load
1824/3 tchFrAveragedUsedWpsCellEch load
2010/0 WQUEUED1 totalizer
2011/0 WQOVFL1 totalizer
2012/0 WQTOUT1 totalizer


2013/0 wpsAccessBarringDurationClass0to9 totalizer
2013/1 wpsAccessBarringDurationClass11 totalizer
2014/0 WPUBWPSQ totalizer
2015/0 WQABAND totalizer
2016/0 WQUEDHO totalizer

411--9001--125
4.2 Raw permanent BSS counters configuration

The permanent general observations can be configured in the four following
observation types:
the real time permanent observation (ORT)
This observation enables the detection in real time of incidents through the
network and observation of fast variations of the traffic load.
the fast statistic permanent observation (OFS)
This observation enables the carrying out of periodic statistics. It can be
configured to collect ovservations every 15, 30, 45, or 60 minutes.
the general statistic permanent observation (OGS)
This observation enables the carrying out of daily statistics.
the diagnostic permanent observation (ODIAG)
This observation enables the investigation of bad functioning, or the verification
and the control of the network (after reorganization). This observation reports
counters that are associated to specific cells of the network. BSC counters may be
associated to this observation
4.2.1 Raw counters configuration (all BSC)

The following table gives the V15.1 default configuration of the counters in the dif-
ferent observation types (ORT, ODIAG, OFS, and OGS). The meaning of “Y”, “N”
and “--” is the following:
“Y” means that the counter is in the default counter list for the specified
observation type;
”N” means that a counter is not configurable for the specified observation type
”--” means that a counter is not set by default, but can be configured for this
observation type (except ORT).
counter Q3 counter name ORT ODIAG OFS OGS
number
1026/0 rachBusyCount/Ts2/Ts4/Ts6 - Y Y -
1027/0 rachAccessCount/Ts2/Ts4/Ts6 - Y Y -
1028/0 pchNoWait/Ts2/Ts4/Ts6 - Y Y -
1029/0 pchOneWait/Ts2/Ts4/Ts6 - Y Y -
1030/0 pchTwoWait/Ts2/Ts4/Ts6 - Y Y -
1031/0 pchMoreWait/Ts2/Ts4/Ts6 - Y Y -
1033/0 rachNonDecodedAvLevel[Cum,Ech,Moy,Max] - Y Y -


number
1033/0 rachNonDecodedAvLevelTs2[Cum,Ech,Moy,Max] - Y Y -
1044/0 signallingPhaseDuration[Cum,Ech,Moy,Max] - Y Y -
1045/0 signallingPhaseDurationHigh[Cum,Ech,Moy,Max] - Y Y -
1049/0 attemptedTchFrSeizures - Y Y -
1050/0 successfulTchFrSeizures - Y Y -
1055/0 assignFailure - Y Y -
1057/0 allTchFrAllocatedTime[Cum,Ech,Moy,Max] - Y Y -
1057/0 allTchFrAllocatedTimeTrZone[Cum,Ech,Moy,Max] - Y Y -
1060/0 allSdcchAllocatedTime[Cum,Ech,Moy,Max] - Y Y -
1060/0 allSdcchAllocatedTimeTrZone[Cum,Ech,Moy,Max] - Y Y -
1065/0 hoExecutionOutgoingIntraBss - Y Y -
1065/1 hoExecutionOutgoingIntraBssForDirectedRetry - Y Y -
1066/0 hoExecutionOutgoingInterBss - Y Y -
1066/1 hoExecutionOutgoingInterBssForDirectedRetry - Y Y -
1067/0 hoSuccessOutgoingIntraBss - Y Y -
1067/1 hoSuccessOutgoingIntraBssForDirectedRetry - Y Y -
1068/0 hoSuccessOutgoingInterBss - Y Y -
1068/1 hoSuccessOutgoingInterBssForDirectedRetry - Y Y -
1069/0 hoRequestIncomingIntraBss Y Y Y -
1070/0 hoRequestIncomingInterBss Y Y Y -
1071/0 hoExecutionIncomingIntraBss - Y Y -
1072/0 hoExecutionIncomingInterBss - Y Y -
1073/0 hoSuccessIncomingIntraBss - Y Y -
1074/0 hoSuccessIncomingInterBss - Y Y -
1075/0 hoRequestOutgoingIntraBss - Y Y -
1076/0 hoRequestOutgoingInterBss - Y Y -
1077/0 hoSuccessOutgoingFirstIntra - Y Y -
1078/0 hoSuccessOutgoingFirstInter - Y Y -
1081/0 hoRequestIntraBts - Y Y -

411--9001--125

number
1082/0 hoExecutionIntraBts - Y Y -
1083/0 hoSuccessIntraBts - Y Y -
1084/0 abisLevel1ErrorsBadFrame[00..17] N N Y N
1084/3 abisLevel1ErrorsCrcError[00..07] N N Y N
1084/4 abisLevel1ErrorsLostAlign[00..07] N N Y N


number
1086/0 gprsRachRejectedSicd[0..9] - - - -
1087/0 gprsImmAssRejectedSicd[0..9] - - - -
1088/0 gprsPagingRejectedSicd[0..9] - - - -
1094/0 tcAllocated - Y Y -
1095/0 tcAveragedUsed[Moy,Max,Cum,Ech] Y Y Y Y
1104/0 sccpAllocated - Y Y -
1104/1 sccpAllocatedLcs - Y Y -
1105/0 sccpAveragedUsed[Moy,Max,Cum,Ech] Y Y Y -
1106/0 sccpRessourceFailure - Y Y -
1106/1 sccpRessourceFailureBscRefusal - Y Y -
1106/2 sccpRessourceFailureLcs - Y Y -
1106/3 sccpRessourceFailureBscRefusalLcs - Y Y -
1107/0 aInputMessage Y Y Y -
1108/0 aOutputMessage Y Y Y -
1109/0 aMessageErrors - Y Y -
1114/0 pcmUnavailability[Cum,Ech,Moy,Max] - Y Y -
1115/0 omcLinkSwitchOver - Y Y -
1121/0 chainStandByUpdate N N N Y
1122/0 chainStandByResponse N N N Y
1134/0 hoUnsuccessReestIntraBtsTch - Y Y -
1135/0 hoUnsuccessReestOutgoingIntraBssTch - Y Y -
1136/0 hoUnsuccessReestOutgoingInterBssTch - Y Y -
1137/0 hoUnsuccessReestIncomingIntraBssTch - Y Y -
1138/0 hoRequiredTchUplinkStrength - Y Y -
1138/1 hoRequiredTchDownlinkStrength - Y Y -
1138/10 hoRequiredTchDirectedRetry - Y Y -
1138/11 hoRequiredTchTdmaClass0 - Y Y -
1138/12 hoRequiredTchTdmaClass1 - Y Y -
1138/13 hoRequiredTchInterBtsOm - Y Y -
1138/14 hoRequiredTchTraffic - Y Y -
1138/15 hoRequiredTchTieringLargeToSmallPattern - Y Y -

411--9001--125

number
1138/16 hoRequiredTchTieringSmallToLargePattern - Y Y -
1138/2 hoRequiredTchUplinkQuality - Y Y -
1138/3 hoRequiredTchDownlinkQuality - Y Y -
1138/4 hoRequiredTchDistance - Y Y -
1138/5 hoRequiredTchPowerBudgetQuality - Y Y -
1138/6 hoRequiredTchCapture - Y Y -
1138/7 hoRequiredTchIntraBtsOm - Y Y -
1138/8 hoRequiredTchIntraBtsUplink - Y Y -
1138/9 hoRequiredTchIntraBtsDownlink - Y Y -
1139/0 hoRequiredSdcchUplinkStrength - Y - Y
1139/1 hoRequiredSdcchDownlinkStrength - Y - Y
1139/13 hoRequiredSdcchInterBtsOm - Y - Y
1139/14 hoRequiredSdcchTraffic - Y - Y
1139/2 hoRequiredSdcchUplinkQuality - Y - Y
1139/3 hoRequiredSdcchDownlinkQuality - Y - Y
1139/4 hoRequiredSdcchDistance - Y - Y
1139/5 hoRequiredSdcchPowerBudget - Y - Y
1139/6 hoRequiredSdcchCapture - Y - Y
1139/7 hoRequiredSdcchIntraBtsOm - Y - Y
1139/8 hoRequiredSdcchIntraBtsUplink - Y - Y
1139/9 hoRequiredSdcchIntraBtsDownlink - Y - Y
1140/0 hoExecutionOutgoingIntraBssSdcch - Y - Y
1141/0 hoExecutionOutgoingInterBssSdcch - Y - Y
1142/0 hoSuccessOutgoingIntraBssSdcch - Y - Y
1143/0 hoSuccessOutgoingInterBssSdcch - Y - Y
1144/0 hoRequestIncomingIntraBssSdcch - Y - Y
1145/0 hoRequestIncomingInterBssSdcch - Y - Y
1146/0 hoExecutionIncomingIntraBssSdcch - Y - Y
1147/0 hoExecutionIncomingInterBssSdcch - Y - Y
1148/0 hoSuccessIncomingIntraBssSdcch - Y - Y
1149/0 hoSuccessIncomingInterBssSdcch - Y - Y


number
1150/0 hoRequestOutgoingIntraBssSdcch - Y - Y
1151/0 hoRequestOutgoingInterBssSdcch - Y - Y
1152/0 hoSuccessOutgoingFirstIntraSdcch - Y - Y
1153/0 hoSuccessOutgoingFirstInterSdcch - Y - Y
1154/0 hoRequestIntraBtsSdcch - Y - Y
1155/0 hoExecutionIntraBtsSdcch - Y - Y
1156/0 hoSuccessIntraBtsSdcch - Y - Y
1157/0 hoUnsuccessReestIntraBtsSdcch - Y - Y
1158/0 hoUnsuccessReestOutgoingIntraBssSdcch - Y - Y
1159/0 hoUnsuccessReestOutgoingInterBssSdcch - Y - Y
1160/0 hoUnsuccessReestIncomingIntraBssSdcch - Y - Y
1161/0 immediateAssignmentRejectTraffMsc - Y Y -
1161/1 immediateAssignmentRejectRadioRes - Y Y -
1161/2 immediateAssignmentRejectChanActNack - Y Y -
1161/3 immediateAssignmentRejectChanActTimmack - Y Y -
1161/5 immediateAssignmentRejectOverload - Y Y -
1161/6 immediateAssignmentRejectTimingAdv - Y Y -
1161/7 immediateAssignmentRejectOthers - Y Y -
1162/0 signallingReleaseNoBtsSccpDiscInd - Y Y -
1162/1 signallingReleaseNoBtsReset - Y Y -
1162/26 signallingReleaseNoBtsTsccRel - Y Y -
1162/27 signallingReleaseNoBtsBadDataInd - Y Y -
1162/28 signallingReleaseNoBtsOthers - Y Y -
1162/3 signallingReleaseNoBtsSccpDataRefusal - Y Y -
1163/0 signallingReleaseBtsSccpDiscInd - Y Y -
1163/1 signallingReleaseBtsReset - Y Y -
1163/10 signallingReleaseBtsCicRemovalEqptFail - Y Y -
1163/11 signallingReleaseBtsOmRadioChanBloc - Y Y -
1163/12 signallingReleaseBtsCallClearing - Y Y -
1163/13 signallingReleaseBtsCnxFailRadioIntFail - Y Y -
1163/14 signallingReleaseBtsCnxFailRadioLinkFail - Y Y -

411--9001--125

number
1163/16 signallingReleaseBtsReleaseInd - Y Y -
1163/17 signallingReleaseBtsErrorIndT200 - Y Y -
1163/18 signallingReleaseBtsErrorIndDm - Y Y -
1163/19 signallingReleaseBtsErrorIndSeq - Y Y -
1163/2 signallingReleaseBtsResetCirc - Y Y -
1163/20 signallingReleaseBtsClearCommand - Y Y -
1163/21 signallingReleaseBtsRfResInd - Y Y -
1163/22 signallingReleaseBtsSwitchOver - Y Y -
1163/23 signallingReleaseBtsTmodMs - Y Y -
1163/24 signallingReleaseBtsT3103 - Y Y -
1163/28 signallingReleaseBtsOthers - Y Y -
1163/3 signallingReleaseBtsSccpDataRefusal - Y Y -
1163/32 signallingReleaseBtsCnxFailRemTransFail - Y Y -
1163/33 signallingReleaseCellTbcEdge - Y Y -
1163/4 signallingReleaseBtsIncFirstL3 - Y Y -
1163/6 signallingReleaseBtsT3107CircDown - Y Y -
1163/7 signallingReleaseBtsOmTsRemoval - Y Y -
1163/8 signallingReleaseBtsTsRemovalEqptFail - Y Y -
1163/9 signallingReleaseBtsOmCicRemoval - Y Y -
1164/0 trafficReleaseSccpDiscInd - Y Y -
1164/1 trafficReleaseReset - Y Y -
1164/10 trafficReleaseCicRemovalEqptFail - Y Y -
1164/11 trafficReleaseOmRadioChanBloc - Y Y -
1164/12 trafficReleaseCallClearing - Y Y -
1164/13 trafficReleaseCnxFailRadioIntFail - Y Y -
1164/14 trafficReleaseCnxFailRadioLinkFail - Y Y -
1164/16 trafficReleaseReleaseInd - Y Y -
1164/17 trafficReleaseErrorIndT200 - Y Y -


number
1164/18 trafficReleaseErrorIndDm - Y Y -
1164/19 trafficReleaseErrorIndSeq - Y Y -
1164/2 trafficReleaseResetCirc - Y Y -
1164/20 trafficReleaseClearCommand - Y Y -
1164/21 trafficReleaseRfResInd - Y Y -
1164/23 trafficReleaseTmodMs - Y Y -
1164/24 trafficReleaseT3103 - Y Y -
1164/25 trafficReleaseT8 - Y Y -
1164/28 trafficReleaseOthers - Y Y -
1164/3 trafficReleaseSccpDataRefusal - Y Y -
1164/31 trafficReleaseSysInfoFail - Y Y -
1164/32 trafficReleaseCnxFailRemTransFail - Y Y -
1164/33 trafficReleaseTbcEdge - Y Y -
1164/6 trafficReleaseT3107CircDown - Y Y -
1164/7 trafficReleaseOmTsRemoval - Y Y -
1164/8 trafficReleaseTsRemovalEqptFail - Y Y -
1164/9 trafficReleaseOmCicRemoval - Y Y -
1165/0 hoIndicationNotTreatedTchoke - Y Y -
1167/0 hoUnsuccessOutgoingIntraBssNAttemptTch - Y Y -
1168/0 hoUnsuccessOutgoingIntraBssNAttemptSdcch - Y - Y
1169/0 hoUnsuccessOutgoingInterBssNAttemptTch - Y Y -
1170/0 hoUnsuccessOutgoingInterBssNAttemptSdcch - Y - Y
1172/0 dataNtRateFbTcbResLack - Y Y -
1172/1 dataNtRateFbTcbConfNotAllowed - Y Y -
1191/0 channelRequestCause[000...111] - Y Y -
1192/0 immediateAssignmentSuccessCause[000..111] - Y Y -
1193/0 estabIndicSignallingPagingRes - Y Y -
1193/1 estabIndicSignallingLocUpdate - Y Y -
1193/2 estabIndicSignallingReEstab - Y Y -
1193/3 estabIndicSignallingImsiDetach - Y Y -
1193/4 estabIndicSignallingMoc - Y Y -

411--9001--125

number
1193/5 estabIndicSignallingEmergency - Y Y -
1193/6 estabIndicSignallingShortMsg - Y Y -
1193/7 estabIndicSignallingSuppService - Y Y -
1193/8 estabIndicSignallingPiggybacked - Y Y -
1195/0 estabIndicSigPhase1 - Y Y -
1196/0 estabIndicSigPhase2 - Y Y -
1197/0 channelActivateSpeechFullRate - Y Y -
1197/1 channelActivateSpeechEnhancedFullRate - Y Y -
1197/2 channelActivateSpeechAmrHr - Y Y -
1197/3 channelActivateSpeechAmrFr - Y Y -
1198/0 downlinkPowerCtrlMaxTch[Cum,Ech,Moy,Max] - Y Y -
1199/0 uplinkPowerCtrlMaxTch[Cum,Ech,Moy,Max] - Y Y -
1200/0 hoNcellsExecution - Y Y -
1202/0 hoNcellsExecutionSdcch - Y - Y
1204/0 hoNcellsUnsuccessTchChlR - Y Y -
1204/1 hoNcellsUnsuccessTchTimer - Y Y -
1204/2 hoNcellsUnsuccessTchOther - Y Y -
1205/0 hoNcellsUnsuccessSdcchChlR - Y - Y
1205/1 hoNcellsUnsuccessSdcchTimer - Y - Y
1205/2 hoNcellsUnsuccessSdcchOther - Y - Y
1206/0 speechAlgoFallBack - Y Y -
1206/1 amrFrSpeechAlgoFallBack - Y Y -
1207/0 immediateAssignmentMultiband - Y Y -
1208/0 hoRequestOutgoingMbandEbandMsDualb - Y Y -
1209/0 hoSuccessOutgoingMbandEbandMsDualb - Y Y -
1300/0 omcOutputIFrame N N N Y
1301/0 omcInputIFrame N N N Y
1302/0 omcOutputRepeatedIFrame N N N Y
1303/0 omcInputRepeatedIFrame N N N Y
1304/0 omcOutputRnrFrame N N N Y
1305/0 omcInputRnrFrame N N N Y


number
1400/0 prLoadCpue[Moy,Max,Cum,Ech] N N Y N
1400/0 prLoadCpue1[Moy,Max,Cum,Ech] N N Y N
1400/0 prLoadCpue2[Moy,Max,Cum,Ech] N N Y N
1400/0 prLoadCpum[Moy,Max,Cum,Ech] N N Y N
1400/0 prLoadSicd0[Moy,Max,Cum,Ech] N N Y N
1500/0 aTransparentUp - Y Y -
1501/0 aTransparentDown - Y Y -
1502/0 aNonTransparentUp - Y Y -
1503/0 aNonTransparentDown - Y Y -
1504/0 vgcsAccessGrant - - - -
1505/0 vgcsMscReject - - - -
1506/0 aintOverloadRejectedOpPageReq - Y Y -
1506/1 aintOverloadRejectedOpIncomingExtHoReq - Y Y -
1506/2 aintOverLoadRejectedOpVbsVgcsSetup - Y Y -
1506/3 aintOverLoadRejectedOpVbsVgcsAssignment - Y Y -
1506/4 aintOverLoadRejectedOpPerformLocationReq - Y Y -
1507/0 e3OverloadRejectedOpPagingReq - Y Y -
1507/1 e3OverloadRejectedOpChannelReq - Y Y -
1507/2 e3OverloadRejectedOpEstablishInd - Y Y -
1507/3 e3OverloadRejectedOpHoReq - Y Y -
1507/4 e3OverloadRejectedOpPagingReqReject - Y Y -
1507/5 e3OverloadRejectedOpSmsCb - Y Y -

411--9001--125

number
1508/0 pagingFilteredByBsc - Y Y -
1600/0 connectionDurationTch[Cum,Ech,Moy,Max] - Y Y -
1600/0 connectionDurationTchTrZone[Cum,Ech,Moy,Max] - Y Y -
1601/0 downlinkPowerCtrlMaxSdcch[Cum,Ech,Moy,Max] - Y Y -
1602/0 uplinkPowerCtrlMaxSdcch[Cum,Ech,Moy,Max] - Y Y -
1603/0 connectionDurationSdcch[Cum,Ech,Moy,Max] - Y Y -
1603/0 connectionDurationSdcchTrZone[Cum,Ech,Moy,Max] - Y Y -
1604/0 pchAveragedQueueLength[Moy,Max,Cum,Ech] - Y Y -
1604/0 pchAveragedQueueLengthTs2[Moy,Max,Cum,Ech] - Y Y -
1605/0 pchQueuePagesDiscarded - Y Y -
1605/0 pchQueuePagesDiscardedTs2 - Y Y -
1606/0 sdcchAllocated - Y Y -
1606/0 sdcchAllocatedTrZone - Y Y -
1607/0 sdcchAveragedUsed[Moy,Max,Cum,Ech] Y Y Y -
1607/0 sdcchAveragedUsedTrZone[Moy,Max,Cum,Ech] Y Y Y -
1608/0 sdcchRessourceFailure - Y Y -
1608/0 sdcchRessourceFailureTrZone - Y Y -
1609/0 tchFrAllocatedTchAllocation - Y Y -
1609/0 tchFrAllocatedTchAllocationTrZone - Y Y -
1609/1 tchFrAllocatedPrimoAllocation - Y Y -
1609/1 tchFrAllocatedPrimoAllocationTrZone - Y Y -
1609/2 tchFrAllocatedOverflowAllocation - Y Y -
1609/2 tchFrAllocatedOverflowAllocationTrZone - Y Y -
1609/3 tchFrAllocatedWps - Y Y -
1609/3 tchFrAllocatedWpsTrZone - Y Y -
1610/0 tchHrAllocatedTchAllocation - Y Y -
1610/0 tchHrAllocatedTchAllocationTrZone - Y Y -


number
1610/1 tchHrAllocatedWps - Y Y -
1610/1 tchHrAllocatedWpsTrZone - Y Y -
1611/0 tchFrAveragedUsedTchAllocation[Moy,Max,Cum,Ech] - Y Y -
1611/0 tchFrAveragedUsedTchAllocation- - Y Y -
TrZone[Moy,Max,Cum,Ech]
1611/1 tchFrAveragedUsedPrimoAlloca- - Y Y -
tion[Moy,Max,Cum,Ech]
1611/1 tchFrAveragedUsedPrimoAllocation- - Y Y -
1611/2 tchFrAveragedUsedOverflowAlloca- - Y Y -
tion[Moy,Max,Cum,Ech]
1611/2 tchFrAveragedUsedOverflowAllocation- - Y Y -
1611/3 tchFrAveragedUsedWps[Moy,Max,Cum,Ech] - Y Y -
1611/3 tchFrAveragedUsedWpsTrZone[Moy,Max,Cum,Ech] - Y Y -
1612/0 tchHrAveragedUsedTchAllocation[Moy,Max,Cum,Ech] - - Y -
1612/0 tchHrAveragedUsedTchAllocation- - - Y -
1612/1 tchHrAveragedUsedWps[Moy,Max,Cum,Ech] - - Y -
1612/1 tchHrAveragedUsedWpsTrZone[Moy,Max,Cum,Ech] - - Y -
1613/0 tchFrRessourceFailure - Y Y -
1613/0 tchFrRessourceFailureTrZone - Y Y -
1614/0 tchHrRessourceFailure - - Y -
1614/0 tchHrRessourceFailureTrZone - - Y -
1616/0 tchAveragedQueueLengthHighPrior- - Y Y -
ity[Moy,Max,Cum,Ech]
1616/1 tchAveragedQueueLengthOtherPrior- - Y Y -
ity[Moy,Max,Cum,Ech]
1617/0 tchQueuingExpirationHighPriority - Y Y -
1617/1 tchQueuingExpirationOtherPriority - Y Y -
1618/0 tchQueuingDurationHighPriority[Cum,Ech,Moy,Max] - Y Y -
1618/1 tchQueuingDurationOtherPriority[Cum,Ech,Moy,Max] - Y Y -
1619/0 channelAveragedIdlePerInterf- - Y Y -
Band0[Cum,Ech,Moy,Max]

411--9001--125

number
1620/0 directedRetryUnsuccessNoBts - Y Y -
1621/0 sapi3SessionEstablishment - Y Y -
1622/0 msLostMeasurements - Y Y -
1622/0 msLostMeasurementsTrZone - Y Y -
1623/0 rxLevDownLink - Y Y -
1623/0 rxLevDownLinkTrZone - Y Y -
1624/0 rxLevUpLink - Y Y -
1624/0 rxLevUpLinkTrZone - Y Y -
1625/0 rxQualDownLink - Y Y -
1625/0 rxQualDownLinkTrZone - Y Y -
1626/0 rxQualUpLink - Y Y -
1626/0 rxQualUpLinkTrZone - Y Y -
1629/0 channelActivateSignallingFullRate - Y Y -
1629/1 channelActivateSignallingHalfRate - Y Y -
1700/0 tchFrAveragedAvailable[Moy,Max,Cum,Ech] Y Y Y -
1700/0 tchFrAveragedAvailableTrZone[Moy,Max,Cum,Ech] Y Y Y -
1701/0 sdcchAveragedAvailable[Moy,Max,Cum,Ech] - Y Y -
1701/0 sdcchAveragedAvailableTrZone[Moy,Max,Cum,Ech] - Y Y -
1702/0 channelRequestExtended - Y Y -
1705/0 channelActivateTchFrDataT16 - Y Y -


number
1706/0 channelActivateTchHrDataT16 - - - -
1707/0 channelActivateTchFrDataNT6000 - Y Y -
1708/0 channelActivateTchHrDataNT6000 - - - -
1709/0 channelActTchFrDataT - - - -
1710/0 channelActTchFrDataNT - - - -
1711/0 channelActTchHrDataT - - - -
1712/0 channelActTchHrDataNT - - - -
1714/0 btsOverloadDuration[Cum,Ech,Moy,Max] - Y Y -
1715/0 attemptedTchFrSeizuresMsDualb - Y Y -
1716/0 successfulTchFrSeizuresMsDualb - Y Y -
1717/0 abisTrauFrameDlReceived - Y Y -
1718/0 abisTrauFrameCorrected - Y Y -
1719/0 abisTrauFrameMuted - Y Y -
1720/0 radioFrameUlReceived - Y Y -
1721/0 ecuActivation - Y Y -
1722/0 asciCallInitiationVbs - - - -
1722/1 asciCallInitiationVgcs - - - -
1723/0 asciInbandPaging - - - -
1724/0 asciInbandNotification - - - -
1725/0 asciPreemptionPerformed - - - -
1726/0 dataNtRateFbTchResLack - Y Y -
1726/1 dataNtRateFbTchConfNotAllowed - Y Y -
1730/0 pagingResponse Y - - -

411--9001--125

number
1744/0 tchFrAllocated - - - -
1744/0 tchFrAllocatedTrZone - - - -
1745/0 tchHrAllocated - - - -
1745/0 tchHrAllocatedTrZone - - - -
1746/0 tchFrAveragedUsed[Moy,Max,Cum,Ech] Y - - -
1746/0 tchFrAveragedUsedTrZone[Moy,Max,Cum,Ech] Y - - -
1747/0 tchHrAveragedUsed[Moy,Max,Cum,Ech] - - - -
1747/0 tchHrAveragedUsedTrZone[Moy,Max,Cum,Ech] - - - -
1748/0 channelRequest - - - -
1749/0 immediateAssignmentSuccess - - - -
1750/0 estabIndicSignalling Y - - -
1751/0 immediateAssignmentReject - - - -
1752/0 signallingReleaseNoBts - - - -
1753/0 signallingReleaseBts - - - -
1754/0 trafficRelease - - - -
1755/0 pcmFaultExternal - Y - -
1755/1 pcmFaultInternal - Y - -
1755/2 pcmFaultDDTIBoard - Y - -
1755/3 pcmFaultOutOfService - Y - -
1756/0 hoFailureIntraBtsTchRadioLack - Y - -
1756/1 hoFailureIntraBtsTchChannelActivateNack - Y - -
1756/2 hoFailureIntraBtsTchTchnAckTimerExp - Y - -
1757/0 hoFailureIntraBtsSdcchRadioLack - Y - -
1757/1 hoFailureIntraBtsSdcchChannelActivateNack - Y - -
1757/2 hoFailureIntraBtsSdcchTchnAckTimerExp - Y - -
1758/0 hoFailureIncomingIntraBssTchRadioLack - Y - -
1758/1 hoFailureIncomingIntraBssTchHoNotAllowed - Y - -
1758/2 hoFailureIncomingIntraBssTchChannelActivateNack - Y - -
1758/3 hoFailureIncomingIntraBssTchTchnAckTimerExp - Y - -
1758/4 hoFailureIncomingIntraBssTchIncompatible - Y - -
1759/0 hoFailureIncomingIntraBssSdcchRadioLack - Y - -


number
1759/1 hoFailureIncomingIntraBssSdcchHoNotAllowed - Y - -
1759/2 hoFailureIncomingIntraBssSdcchChannelActivateNack - Y - -
1759/3 hoFailureIncomingIntraBssSdcchTchnAckTimerExp - Y - -
1760/0 hoFailureIncomingInterBssTchRadioLack - Y - -
1760/1 hoFailureIncomingInterBssTchTerrestLack - Y - -
1760/2 hoFailureIncomingInterBssTchHoNotAllowed - Y - -
1760/3 hoFailureIncomingInterBssTchChannelActivateNack - Y - -
1760/4 hoFailureIncomingInterBssTchTchnAckTimerExp - Y - -
1760/5 hoFailureIncomingInterBssTchCICIncompatible - Y - -
1761/0 hoFailureIncomingInterBssSdcchRadioLack - Y - -
1761/1 hoFailureIncomingInterBssSdcchTerrestLack - Y - -
1761/2 hoFailureIncomingInterBssSdcchHoNotAllowed - Y - -
1761/3 hoFailureIncomingInterBssSdcchChannelActivateNack - Y - -
1761/4 hoFailureIncomingInterBssSdcchTchnAckTimerExp - Y - -
1762/0 hoFailureOutgoingIntraBssTchRadioLack - Y - -
1762/1 hoFailureOutgoingIntraBssTchHoNotAllowed - Y - -
1762/2 hoFailureOutgoingIntraBssTchChannelActivateNack - Y - -
1762/3 hoFailureOutgoingIntraBssTchTchnAckTimerExp - Y - -
1762/4 hoFailureOutgoingIntraBssTchIncompatible - Y - -
1763/0 hoFailureOutgoingIntraBssSdcchRadioLack - Y - -
1763/1 hoFailureOutgoingIntraBssSdcchHoNotAllowed - Y - -
1763/2 hoFailureOutgoingIntraBssSdcchChannelActivateNack - Y - -
1763/3 hoFailureOutgoingIntraBssSdcchTchnAckTimerExp - Y - -
1764/0 hoFailureOutgoingInterBssTchRadioLack - Y - -
1764/1 hoFailureOutgoingInterBssTchTerrestLack - Y - -
1764/2 hoFailureOutgoingInterBssTchHoNotAllowed - Y - -
1764/3 hoFailureOutgoingInterBssTchT7TimerExp - Y - -
1764/4 hoFailureOutgoingInterBssTchOtherCases - Y - -
1764/5 hoFailureOutgoingInterBssTchIncompatible - Y - -
1765/0 hoFailureOutgoingInterBssSdcchRadioLack - Y - -
1765/1 hoFailureOutgoingInterBssSdcchTerrestLack - Y - -

411--9001--125

number
1765/2 hoFailureOutgoingInterBssSdcchHoNotAllowed - Y - -
1765/3 hoFailureOutgoingInterBssSdcchT7TimerExp - Y - -
1765/4 hoFailureOutgoingInterBssSdcchOtherCase - Y - -
1768/0 hoUnsuccessOutgoingIntraCellTchReturnOldChannel - Y - -
1768/1 hoUnsuccessOutgoingIntraCellTchT3103TimerExp - Y - -
1769/0 hoUnsuccessOutgoingIntraCellSdcchReturnOldChannel - Y - -
1769/1 hoUnsuccessOutgoingIntraCellSdcchT3103TimerExp - Y - -
1770/0 hoUnsuccessOutgoingInterCellTchReturnOldChannel - Y - -
1770/1 hoUnsuccessOutgoingInterCellTchT3103TimerExp - Y - -
1770/2 hoUnsuccessOutgoingInterCellTchOtherCases - Y - -
1771/0 hoUnsuccessOutgoingInterCellSdcchReturnOldChannel - Y - -
1771/1 hoUnsuccessOutgoingInterCellSdcchT3103TimerExp - Y - -
1771/2 hoUnsuccessOutgoingInterCellSdcchOtherCases - Y - -
1772/0 hoUnsuccessIncomingIntraCellTchReturnOldChannel - Y - -
1772/1 hoUnsuccessIncomingIntraCellTchT3103TimerExp - Y - -
1773/0 hoUnsuccessIncomingIntraCellSdcchReturnOldChannel - Y - -
1773/1 hoUnsuccessIncomingIntraCellSdcchT3103TimerExp - Y - -
1774/0 hoUnsuccessIncomingInterBssTchTimerExp - Y - -
1774/1 hoUnsuccessIncomingInterBssTchOtherCases - Y - -
1775/0 hoUnsuccessIncomingInterBssSdcchTimerExp - Y - -
1775/1 hoUnsuccessIncomingInterBssSdcchOtherCases - Y - -
1776/0 hoRequiredTch - - Y -
1777/0 hoRequiredSdcch - - - -
1778/0 signallingAbnormalReleaseCell - Y Y -
1779/0 trafficAbnormalRelease - Y Y -
1780/0 hoSuccessOutgoingTch Y - Y -
1780/1 amrFrHoSuccessOutgoingTch Y - Y -
1780/2 amrHrHoSuccessOutgoingTch Y - Y -
1781/0 hoSuccessIncomingTch Y - Y -
1782/0 hoBtsRejected - Y Y -
1783/0 hoRequestOutgoingMbandMbandMsDualb - Y Y -


number
1784/0 hoRequestOutgoingEbandEbandMsDualb - Y Y -
1785/0 hoRequestOutgoingEbandMbandMsDualb - Y Y -
1786/0 hoSuccessOutgoingMbandMbandMsDualb - Y Y -
1787/0 hoSuccessOutgoingEbandEbandMsDualb - Y Y -
1788/0 hoSuccessOutgoingEbandMbandMsDualb - Y Y -
1789/0 hoExecutionOutgoingMbandEbandMsDualb - Y Y -
1790/0 hoExecutionOutgoingMbandMbandMsDualb - Y Y -
1791/0 hoExecutionOutgoingEbandEbandMsDualb - Y Y -
1792/0 hoExecutionOutgoingEbandMbandMsDualb - Y Y -
1793/0 hoRequestIncomingIntraBssTchMsDualb - Y Y -
1794/0 hoExecutionIncomingIntraBssTchMsDualb - Y Y -
1795/0 hoSuccessIncomingIntraBssTchMsDualb - Y Y -
1796/0 hoRequestIntraBtsMsDualb - Y Y -
1797/0 hoExecutionIntraBtsMsDualb - Y Y -
1798/0 hoSuccessIntraBtsMsDualb - Y Y -
1799/0 assignToOtherBandOrZone - Y Y -
1800/0 asciTalkerHandoverVbs - - - -
1800/1 asciTalkerHandoverVgcs - - - -
1801/0 hoFailureTieringTchNorrLargeToSmallPattern - Y Y -
1801/1 hoFailureTieringTchNorrSmallToLargePattern - Y Y -
1802/0 hoSuccessTieringTchLargeToSmallPattern - Y Y -
1802/1 hoSuccessTieringTchSmallToLargePattern - Y Y -
1803/0 cgOverloadRejectedOpPageReqCg0 - Y Y -
1803/1 cgOverloadRejectedOpChannelReqCg0 - Y Y -
1803/2 cgOverloadRejectedOpEstablishIndCg0 - Y Y -

411--9001--125

number
1803/3 cgOverloadRejectedOpHoReqCg0 - Y Y -
1803/4 cgOverloadRejectedOpPageReqBtsCg0 - Y Y -
1803/5 cgOverloadRejectedOpSmsCbCg0 - Y Y -
1804/0 deleteIndication - Y Y -
1805/0 msPowerIncControl - Y Y -
1806/0 msPowerDecControl - Y Y -
1807/0 bsPowerIncControl - Y Y -
1808/0 bsPowerDecControl - Y Y -
1809/0 timingAdvanceAverage - Y Y -
1809/0 timingAdvanceAverageTrZone - Y Y -
1809/1 timingAdvanceMaximum - Y Y -
1809/1 timingAdvanceMaximumTrZone - Y Y -
1810/0 tchFrAverageConfigurated[Moy,Max,Cum,Ech] - Y Y -
1810/0 tchFrAverageConfiguratedTrZone[Moy,Max,Cum,Ech] - Y Y -
1811/0 sdcchAverageConfigurated[Moy,Max,Cum,Ech] - Y Y -
1811/0 sdcchAverageConfiguratedTrZone[Moy,Max,Cum,Ech] - Y Y -
1812/0 allocatedCircuitTs[Moy,Max,Cum,Ech] - Y Y -
1812/0 allocatedCircuitTsTrZone[Moy,Max,Cum,Ech] - Y Y -
1813/0 allocatedPacketTs[Moy,Max,Cum,Ech] - Y Y -
1813/0 allocatedPacketTsTrZone[Moy,Max,Cum,Ech] - Y Y -
1813/1 totalNumberOfPacketTs[Moy,Max,Cum,Ech] - Y Y -
1813/1 totalNumberOfPacketTsTrZone[Moy,Max,Cum,Ech] - Y Y -
1813/2 totalNumberOfPacketTsUsedForCir- - Y Y -
cuit[Moy,Max,Cum,Ech]
1813/2 totalNumberOfPacketTsUsedForCircuitTr- - Y Y -
Zone[Moy,Max,Cum,Ech]


number
1814/0 gprsPreemption - Y Y -
1815/0 gprsPreemptionNack - Y Y -
1816/0 pathBalance[Cum,Ech,Moy,Max] - Y Y -
1817/0 burstToTransmit - - - Y
1818/0 burstTransmitted - - - Y
1819/0 burstToTransmitReqPwr - - - Y
1820/0 STPMAttenuation - - - Y
1821/0 allocatedCircuitTsCell[Moy,Max,Cum,Ech] - Y Y -
1822/0 allocatedPacketTsCell[Moy,Max,Cum,Ech] - Y Y -
1822/1 totalNumberOfPacketTsCell[Moy,Max,Cum,Ech] - Y Y -
1822/2 totalNumberOfPacketTsUsedForCircuit- - Y Y -
Cell[Moy,Max,Cum,Ech]
1823/0 allTchFrAllocatedTimeCell[Cum,Ech,Moy,Max] - Y Y -
1824/0 tchFrAveragedUsedTchAllocation- - Y Y -
1824/1 tchFrAveragedUsedPrimoAllocation- - Y Y -
1824/2 tchFrAveragedUsedOverflowAllocation- - Y Y -
1824/3 tchFrAveragedUsedWpsCell[Moy,Max,Cum,Ech] - Y Y -
1825/0 tchFrAveragedAvailableCell[Moy,Max,Cum,Ech] Y Y Y -
1826/0 tchFrAveragedUsedCell[Moy,Max,Cum,Ech] Y - - -
1827/0 tchFrAverageConfiguratedCell[Moy,Max,Cum,Ech] - Y Y -
1828/0 tchHrAveragedUsedCell[Moy,Max,Cum,Ech] - - Y -
1828/1 tchHrAveragedUsedWpsCell[Moy,Max,Cum,Ech] - - Y -
1829/0 tchHrAveragedUsedNscCell[Moy,Max,Cum,Ech] - - - -
1834/0 lapdOverloadRejectedOpSicd0 N N Y N

411--9001--125

number
1835/0 cardSynthLoadCpue0[Moy,Max,Cum,Ech] N N Y N
1835/0 cardSynthLoadCpum[Moy,Max,Cum,Ech] N N Y N
1835/0 cardSynthLoadSicd[0..9][Moy,Max,Cum,Ech] N N Y N
1839/0 hoNcellsRequestOutgoingUplinkStrength N Y N N
1839/1 hoNcellsRequestOutgoingDownlinkStrength N Y N N
1839/2 hoNcellsRequestOutgoingUplinkQuality N Y N N
1839/3 hoNcellsRequestOutgoingDownlinkQuality N Y N N
1839/4 hoNcellsRequestOutgoingDistance N Y N N
1839/5 hoNcellsRequestOutgoingPowerBudget N Y N N
1839/6 hoNcellsRequestOutgoingDirectedRetry N Y N N
1839/7 hoNcellsRequestOutgoingInterCellOM N Y N N
1839/8 hoNcellsRequestOutgoingTraffic N Y N N
1839/9 hoNcellsRequestOutgoingOther N Y N N
1840/0 hoNcellsSuccessOutgoingUplinkStrength N Y N N
1840/1 hoNcellsSuccessOutgoingDownlinkStrength N Y N N
1840/2 hoNcellsSuccessOutgoingUplinkQuality N Y N N
1840/3 hoNcellsSuccessOutgoingDownlinkQuality N Y N N
1840/4 hoNcellsSuccessOutgoingDistance N Y N N
1840/5 hoNcellsSuccessOutgoingPowerBudget N Y N N
1840/6 hoNcellsSuccessOutgoingDirectedRetry N Y N N
1840/7 hoNcellsSuccessOutgoingInterCellOM N Y N N
1840/8 hoNcellsSuccessOutgoingTraffic N Y N N
1840/9 hoNcellsSuccessOutgoingOther N Y N N
1841/0 assignRequestSdcchToTchChannel - Y Y -
1841/1 assignRequestOthers - Y Y -


number
1842/0 assignRequestAintSdcchToTchChannel - Y Y -
1842/1 assignRequestAintOthers - Y Y -
1900/0 amrFrTchAllocated - - Y -
1900/0 amrFrTchAllocatedTrZone - - Y -
1901/0 amrFrTchStdAveragedUsed[Moy,Max,Cum,Ech] - - Y -
1901/0 amrFrTchStdAveragedUsedTrZone[Moy,Max,Cum,Ech] - - Y -
1902/0 amrFrTchConnectionDuration[Cum,Ech,Moy,Max] - - Y -
1902/0 amrFrTchConnectionDuration- - - Y -
TrZone[Cum,Ech,Moy,Max]
1902/1 amrHrTchConnectionDuration[Cum,Ech,Moy,Max] - - Y -
1902/1 amrHrTchConnectionDuration- - - Y -
TrZone[Cum,Ech,Moy,Max]
1903/0 amrFrTchSuccessfullyAssigned - - Y -
1903/1 amrHrTchSuccessfullyAssigned - - Y -
1904/0 amrFrTchAssignFailure - - Y -
1904/1 amrHrTchAssignFailure - - Y -
1905/0 CIUplinkFr - - Y -
1905/0 CIUplinkFrTrZone - - Y -
1906/0 downlinkPowerCtrlMaxTchAmrFr[Cum,Ech,Moy,Max] - - Y -
1907/0 uplinkPowerCtrlMaxTchAmrFr[Cum,Ech,Moy,Max] - - Y -
1908/0 RxLevDownlinkAmrFr - - Y -
1908/0 RxLevDownlinkAmrFrTrZone - - Y -
1909/0 RxLevUplinkAmrFr - - Y -
1909/0 RxLevUplinkAmrFrTrZone - - Y -
1910/0 RxQualDownlinkAmrFr - - Y -
1910/0 RxQualDownlinkAmrFrTrZone - - Y -
1911/0 RxQualUplinkAmrFr - - Y -
1911/0 RxQualUplinkAmrFrTrZone - - Y -
1912/0 msPowerIncControlAmrFr - - Y -
1913/0 msPowerDecControlAmrFr - - Y -
1914/0 bsPowerIncControlAmrFr - - Y -
1915/0 bsPowerDecControlAmrFr - - Y -

411--9001--125

number
1916/0 CIUplinkAmrFr - - Y -
1916/0 CIUplinkAmrFrTrZone - - Y -
1917/0 timingAdvanceAmrFrAvg - - Y -
1917/1 timingAdvanceAmrFrMax - - Y -
1918/0 downlinkPowerCtrlMaxTchAmrHr[Cum,Ech,Moy,Max] - - Y -
1919/0 uplinkPowerCtrlMaxTchAmrHr[Cum,Ech,Moy,Max] - - Y -
1920/0 RxLevDownlinkAmrHr - - Y -
1920/0 RxLevDownlinkAmrHrTrZone - - Y -
1921/0 RxLevUplinkAmrHr - - Y -
1921/0 RxLevUplinkAmrHrTrZone - - Y -
1922/0 RxQualDownlinkAmrHr - - Y -
1922/0 RxQualDownlinkAmrHrTrZone - - Y -
1923/0 RxQualUplinkAmrHr - - Y -
1923/0 RxQualUplinkAmrHrTrZone - - Y -
1924/0 msPowerIncControlAmrHr - - Y -
1925/0 msPowerDecControlAmrHr - - Y -
1926/0 bsPowerIncControlAmrHr - - Y -
1927/0 bsPowerDecControlAmrHr - - Y -
1928/0 CIUplinkAmrHr - - Y -
1928/0 CIUplinkAmrHrTrZone - - Y -
1929/0 timingAdvanceAmrHrAvg - - Y -
1929/1 timingAdvanceAmrHrMax - - Y -
1930/0 msLostMeasurementsAmrFr - - Y -
1930/0 msLostMeasurementsAmrFrTrZone - - Y -
1931/0 msLostMeasurementsAmrHr - - Y -
1931/0 msLostMeasurementsAmrHrTrZone - - Y -
1932/0 qualityHoFiltered - - Y -
1933/0 capacityHoFiltered - - Y -
1934/0 amrFrTchStdAveragedUsedCell[Moy,Max,Cum,Ech] - - Y -
1935/0 amrHrModeDuration - - Y -
1936/0 amrCellLoadStateModification - - Y -


number
1937/0 amrFilteredBusyTchRatio[Moy,Max,Cum,Ech] - - Y -
1938/0 amrCellLoadStateUnderevaluated - - Y -
1939/0 amrCellLoadStateOverevaluated - - Y -
1950/0 intracellAmrFrUpHoRequiredTch - - Y -
1950/1 intracellAmrFrDownHoRequiredTch - - Y -
1950/2 amrQualityFrUpHoRequiredTch - - Y -
1950/3 amrQualityFrDownHoRequiredTch - - Y -
1950/4 capacityFrToHrHoRequiredTch - - Y -
1951/0 alarmAmrHrToFrUpHoRequiredTch - - Y -
1951/1 alarmAmrHrToFrDownHoRequiredTch - - Y -
1951/2 amrQualityHrUpHoRequiredTch - - Y -
1951/3 amrQualityHrDownHoRequiredTch - - Y -
1952/0 amrFrHoRequestOutgoingTch - - Y -
1952/1 amrHrHoRequestOutgoingTch - - Y -
1953/0 amrFrHoRequestIntraCellTch - - Y -
1953/1 amrFrToHrHoRequestIntraCellTch - - Y -
1953/2 amrHrToFrHoRequestIntraCellTch - - Y -
1954/0 amrFrHoExecutionIntraCellTch - - Y -
1954/1 amrFrToHrHoExecutionIntraCellTch - - Y -
1954/2 amrHrToFrHoExecutionIntraCellTch - - Y -
1955/0 amrFrHoSuccessIntraCellTch - - Y -
1955/1 amrFrToHrHoSuccessIntraCellTch - - Y -
1955/2 amrHrToFrHoSuccessIntraCellTch - - Y -
1956/0 hoNCellsExecutionTchAmrHr - - Y -
1957/0 hoNCellsExecutionTchAmrFr - - Y -
1958/0 hoNCellsUnsuccessTchAmrHrHandoverFailure - - Y -
1958/1 hoNCellsUnsuccessTchAmrHrTimerExpiration - - Y -
1958/2 hoNCellsUnsuccessTchAmrHrClearCommand - - Y -
1959/0 hoNCellsUnsuccessTchAmrFrHandoverFailure - - Y -
1959/1 hoNCellsUnsuccessTchAmrFrTimerExpiration - - Y -
1959/2 hoNCellsUnsuccessTchAmrFrClearCommand - - Y -

411--9001--125

number
1960/0 trafficReleaseAmrFrLapdmCause - - Y -
1960/1 trafficReleaseAmrFrRadioCause - - Y -
1960/2 trafficReleaseAmrFrOthersCause - - Y -
1961/0 trafficReleaseAmrHrLapdmCause - - Y -
1961/1 trafficReleaseAmrHrRadioCause - - Y -
1961/2 trafficReleaseAmrHrOthersCause - - Y -
1963/0 hoNCellsRequestOutgoingAmrHr - - Y -
1964/0 hoNCellsRequestOutgoingAmrFr - - Y -
1975/0 amrFrUplinkCodec475 - - - Y
1975/0 amrFrUplinkCodec475TrZone - - - Y
1976/0 amrHrUplinkCodec475 - - - Y
1976/0 amrHrUplinkCodec475TrZone - - - Y
1977/0 amrFrDownlinkCodec475 - - - Y
1977/0 amrFrDownlinkCodec475TrZone - - - Y
1978/0 amrHrDownlinkCodec475 - - - Y


number
1978/0 amrHrDownlinkCodec475TrZone - - - Y
1979/0 amrFrBadSpeechFramesCodec475 - - - Y
1979/0 amrFrBadSpeechFramesCodec475TrZone - - - Y
1980/0 amrFrValidSpeechFramesCodec475 - - - Y
1980/0 amrFrValidSpeechFramesCodec475TrZone - - - Y
1981/0 amrHrBadSpeechFramesCodec475 - - - Y
1981/0 amrHrBadSpeechFramesCodec475TrZone - - - Y
1982/0 amrHrValidSpeechFramesCodec475 - - - Y
1982/0 amrHrValidSpeechFramesCodec475TrZone - - - Y

411--9001--125

number
1983/0 amrUplinkNoDataFrames - - - Y
1983/1 amrDownlinkNoDataFrames - - - Y
1984/0 incAmrFrUpModif - - - Y
1984/0 incAmrFrUpModifTrZone - - - Y
1984/1 decAmrFrUpModif - - - Y
1984/1 decAmrFrUpModifTrZone - - - Y
1985/0 incAmrFrDownModif - - - Y
1985/0 incAmrFrDownModifTrZone - - - Y
1985/1 decAmrFrDownModif - - - Y
1985/1 decAmrFrDownModifTrZone - - - Y
1986/0 incAmrHrUpModif - - - Y
1986/0 incAmrHrUpModifTrZone - - - Y
1986/1 decAmrHrUpModif - - - Y
1986/1 decAmrHrUpModifTrZone - - - Y
1987/0 incAmrHrDownModif - - - Y
1987/0 incAmrHrDownModifTrZone - - - Y
1987/1 decAmrHrDownModif - - - Y
1987/1 decAmrHrDownModifTrZone - - - Y
1988/0 amrReversalPhaseFailure - - - Y
2000/0 totalNumberOfEdgeTs[Moy,Max,Cum,Ech] - Y Y -
2000/0 totalNumberOfEdgeTsTrZone[Moy,Max,Cum,Ech] - Y Y -
2000/1 allocatedEdgeTs[Moy,Max,Cum,Ech] - Y Y -
2000/1 allocatedEdgeTsTrZone[Moy,Max,Cum,Ech] - Y Y -
2000/2 preemptedEdgeTs[Moy,Max,Cum,Ech] - Y Y -
2000/2 preemptedEdgeTsTrZone[Moy,Max,Cum,Ech] - Y Y -
2001/0 allocatedAbisJokerTSEdge[Moy,Max,Cum,Ech] - - Y Y
2001/0 allocatedAbisJokerTSEdgeTrZone[Moy,Max,Cum,Ech] - - Y Y
2002/0 totalNumberOfEdgeTsCell[Moy,Max,Cum,Ech] - Y Y -
2002/1 allocatedEdgeTsCell[Moy,Max,Cum,Ech] - Y Y -


number
2002/2 preemptedEdgeTsCell[Moy,Max,Cum,Ech] - Y Y -
2003/0 allocatedAbisJokerTsCell[Moy,Max,Cum,Ech] - - Y Y
2010/0 WQUEUED1 - Y Y -
2010/1 WQUEUED2 - Y Y -
2010/2 WQUEUED3 - Y Y -
2010/3 WQUEUED4 - Y Y -
2010/4 WQUEUED5 - Y Y -
2011/0 WQOVFL1 - Y Y -
2011/1 WQOVFL2 - Y Y -
2011/2 WQOVFL3 - Y Y -
2011/3 WQOVFL4 - Y Y -
2011/4 WQOVFL5 - Y Y -
2012/0 WQTOUT1 - Y Y -
2012/1 WQTOUT2 - Y Y -
2012/2 WQTOUT3 - Y Y -
2012/3 WQTOUT4 - Y Y -
2012/4 WQTOUT5 - Y Y -
2013/0 wpsAccessBarringDurationClass0to9 - Y Y -
2013/1 wpsAccessBarringDurationClass11 - Y Y -
2014/0 WPUBWPSQ - Y Y -
2015/0 WQABAND - Y Y -
2016/0 WQUEDHO - Y Y -
2025/0 downgradedL1mModeOnClassmark - Y Y -
2035/0 msClassSensitivityToggle - - - -
2036/0 attemptedTchFrSeizures8W - - - -
2037/0 successfulTchFrSeizures8W - - - -
2038/0 hoSuccessOutgoingIntraBss8W - - - -

411--9001--125

number
2039/0 hoSuccessOutgoingInterBss8W - - - -
2040/0 hoRequestIncomingIntraBss8W - - - -
2041/0 hoRequestIncomingInterBss8W - - - -
2042/0 hoSuccessIncomingIntraBss8W - - - -
2043/0 hoSuccessIncomingInterBss8W - - - -
2044/0 hoRequestOutgoingIntraBss8W - - - -
2045/0 hoRequestOutgoingInterBss8W - - - -
2046/0 hoRequestIntraBts8W - - - -
2047/0 hoSuccessIntraBts8W - - - -
2048/0 hoSuccessOutgoingIntraBssSdcch8W - - - -
2049/0 hoSuccessOutgoingInterBssSdcch8W - - - -
2050/0 hoRequestOutgoingIntraBssSdcch8W - - - -
2051/0 hoRequestOutgoingInterBssSdcch8W - - - -
2052/0 signallingReleaseBts8w - - - -
2052/1 signallingReleaseBtsT3107CircDown8W - - - -
2053/0 trafficRelease8W - - - -
2054/0 estabIndicSignallingEmergency8W - - - -
2055/0 estabIndicSigPhase28W - - - -
2056/0 hoUnsuccessOutgoingIntraCellTchReturnOldChan- - - - -
nel8W
2056/1 hoUnsuccessOutgoingIntraCellTchT3103TimerExp8W - - - -
2057/0 hoUnsuccessOutgoingInterCellTchReturnOldChan- - - - -
nel8W
2057/1 hoUnsuccessOutgoingInterCellTchT3103TimerExp8W - - - -
2058/0 signallingAbnormalReleaseCell8W - - - -
2059/0 trafficAbnormalRelease8W - - - -
2060/0 uplinkFreeUplinkReply - - - -
2061/0 listenerDetectionExpiry - - - -
2066/0 suspendRequest - - Y -
2067/0 resumeSuccess - - Y -
2068/0 resumeFailureAfterHOInterRA - - Y -
2068/1 resumeFailureAfterHOInterBSC - - Y -


number
2071/0 agprsSuspendRequestProcedures - - Y -
2071/1 agprsSuspendRequestMessages - - Y -
2072/0 agprsSuspendNack - - Y -
2073/0 agprsResumeRequest - - Y -
2074/0 agprsResumeNack - - Y -
2096/0 saicTchSuccessfullyAssigned - Y Y -
2096/0 saicTchSuccessfullyAssignedTrZone - Y Y -
3000/0 prLoadCne3OmuSbc[Moy,Max,Cum,Ech] - Y Y -
3001/0 prLoadCne3TmuSbc[Moy,Max,Cum,Ech] - Y Y -
3001/2 prLoadCne3TmuPmc[Moy,Max,Cum,Ech] - Y Y -
3004/0 e3PrMemCnOmuSbcMem[Cum,Ech,Moy,Max] - Y Y -
3004/1 e3PrMemCnOmuSbcSwap[Cum,Ech,Moy,Max] - Y Y -
3005/0 e3PrMemCnTmuSbc[Cum,Ech,Moy,Max] - Y Y -
3005/2 e3PrMemCnTmuPmc[Cum,Ech,Moy,Max] - Y Y -
3008/0 e3PrDiskCnOmuLdW[Cum,Ech,Moy,Max] - Y Y -
3008/1 e3PrDiskCnOmuLdR[Cum,Ech,Moy,Max] - Y Y -
3008/2 e3PrDiskCnOmuMdW[Cum,Ech,Moy,Max] - Y Y -
3008/3 e3PrDiskCnOmuMdR[Cum,Ech,Moy,Max] - Y Y -
4.2.2 Correspondence between BSC 12000HC and BSC 3000 counters
BSC 3000 Counter name BSC Counter name

12000HC
Counter
number Counter
number
3000/0 prLoadCne3OmuSbcMoyMax/Cum/Ech 1400 prLoadCpumMoy/Max/Cum/Ech

prLoadCpueMoy/Max/Cum/Ech
prLoadCpue1Moy/Max/Cum/Ech
prLoadCpue2Moy/Max/Cum/Ech
prLoadSicdMoy/Max/Cum/Ech
3001/0 prLoadCne3TmuSbcMoyMax/Cum/Ech 1400 prLoadCpumMoy/Max/Cum/Ech-
prLoadCpueMoy/Max/Cum/Ech-
3001/2 prLoadCne3TmuPmcMoy/Max/Cum/Ech prLoadCpue1Moy/Max/Cum/Ech-
prLoadCpue2Moy/Max/Cum/Ech-
prLoadSicdMoy/Max/Cum/Ech

411--9001--125
BSC 3000 Counter name BSC Counter name

12000HC
Counter
number Counter
number
3004/0 e3PrMemCnOmuSbcMemMoy/Max/Cum
/Ech
3004/1 e3PrMemCnOmuSbcSwapMoy/Max/Cu
m/Ech
3005/0 e3PrMemCnTmuSbcMoy/Max/Cum/Ech
3005/2 e3PrMemCnTmuPmcMoy/Max/Cum/Ech
3008 /0 e3PrDiskCnOmuLdWMoy/Max/Cum/Ech
3008/1 e3PrDiskCnOmuLdRMoy/Max/Cum/Ech
3008/2 e3PrDiskCnOmuMdWMoy/Max/Cum/Ech
3008/3 e3PrDiskCnOmuMdRMoy/Max/Cum/Ech

4.3 Synthetic permanent BSS counters configuration
4.3.1 OFS & OGS synthetic counters in standard configuration
Counter number Counter name OFS OGS

8000 hoOutTchGlobalFaiLRate X
8001 hoOutSdcchGlobalFailRate X
8002 hoOutTchRequestRatio X
8003 hoOutSdcchRequestRatio X
8004 hoOutTchSelectionFailRate X
8005 hoOutSdcchSelectionFailRate X
8006 hoOutTchExecutionFailRate X
8007 hoOutSdcchExecutionFailRate X
8008 hoInTchSelectionFailRate X
8009 hoInSdcchSelectionFailRate X
8010 hoInTchExecutionFailRate X
8011 hoInSdcchExecutionFailRate X
8012 hoOutTchFirstAttemptSuccessRatio X
8013 hoOutSdcchFirstAttemptSuccessRatio X
8016 allEstabIndicSignalling X
8017 t3107ExpAssign X
8018 t3107ExpIntraBtsHoSdcch X
8019 t3107expIntraBtsHoTch X
8020 t3103ExpTch X
8021 t3103ExpSdcch X
8037 attemptedTchFrSeizureNotInclHo X
8039 attemptedTchFrSeizureInclHo X
8040 allocationFailureTchFrSeizureInclHo X
8044 clearRequestTraffic X
8050 relativeTimeDLPowerCtrlMaxTch X
8051 relativeTimeULPowerCtrlMaxTch X
8052 relativeTimeDLPowerCtrlMaxSdcch X
8053 relativeTimeULPowerCtrlMaxSdcch X
8104 requestedHandoverForDualBandMSToSecond X
VersusMainBand
8105 immAssignDualBandMSRate X
8500 hoOutTchMaxFailRate X
8501 hoOutSdcchMaxFailRate X
8502 hoOutTchRequestMaxRatio X
8503 hoOutSdcchRequestMaxRatio X

411--9001--125

8504 hoOutTchSelectionFailMaxRate X
8505 hoOutSdcchSelectionFailMaxRate X
8506 hoOutExecutionFailMaxRate X
8507 hoOutSdcchExecutionFailMaxRate X
8508 hoInTchSelectionFailMaxRate X
8509 hoInSdcchSelectionFailMaxRate X
8510 hoInTchExecutionFailMaxRate X
8511 hoInSdcchExecutionFailMaxRate X
8512 hoOutTchFirstAttemptSuccessMinRatio X
8513 hoOutSdcchFirstAttemptSuccessMinRatio X
8550 hoOutTchBscGlobalFailRate X
8551 hoOutSdcchBscGlobalFailRate X
8552 hoOutTchRequestBscRatio X
8553 hoOutSdcchrequestBscRatio X
8554 hoOutTchSelectionBscFailRate X
8555 hoOutSdcchSelectionBscFailRate X
8856 hoOutTchExecutionBscFailRate X
8557 hoOutSdcchExecutionBscFailRate X
8558 hoInInterTchSelectionBscFailRate X
8559 hoInInterSdcchSelectionBscFailRate X
8560 hoInInterTchExecutionBscFailRate X
8561 hoInInterSdcchExecutionBscFailRate X
8562 hoInIntraTchExecutionBscFailRate X
8563 hoInIntraSdcchExecutionBscFailRate X
8564 hoOutInterTchExecutionBscFailRate X
8565 hoOutInterSdcchExecutionBscFailRate X
8566 hoOutFirstSuccessTchRatio X
8567 hoOutFirstSuccessSdcchRatio X
8568 aMessageErroneousRate X
8569 sccpResourceFailureRatio X
8600 bscSdcchAveragedUsedMoy X
8601 bscTchFrAveragedUsedOverflowAllocationMoy X
8602 bscTchAveragedUsedPrimoAllocationMoy X
8603 bscTchFrAveragedUsedTchAllocationMoy X
8604 bscPagingResponse X
8605 bscOtherThanPaging X
8606 hoOutExecutionBscTch X
8607 hoOutExecutionBscSdcch X


8608 hoInExecutionBscTch X
8609 hoInExecutionBscSdcch X
8610 bscSdcchAllocated X
8611 bscTchFrAllocatedOverflowAllocation X
8612 bscTchFrAllocatedPrimoAllocation X
8613 bscTchFrAllocatedAllocation X
8623 averageDLRxLev X
8624 averageULRxLev X
8625 averageDLRxQual X
8626 averageULRxQual X
8628 dlMutedAbisTrauFrameRate X
8637 bscAttemptedTchFrSeizureNotInclHo X
8639 bscAttemptedTchFrSeizureInclHo X
8640 bscAllocationFailureTchFrSeizureInclHo X
8644 bscClearRequestTraffic X
8700 pcminseconds X
8701 allTchinseconds X
8702 allSdcchinseconds X
8706 cellSdcchResourceFailureRatio X
8707 cellTchResourceFailureRatio X
8713 signallingReleaseRatio X
8714 callDropTrafficRatio X
8726 rachBusyCountCell X
8727 rachAccessCountCell X
8728 pchNoWaitCell X
8729 pchOneWaitCell X
8730 pchTwoWaitCell X
8731 pchMoreWaitCell X
8733 rachNonDecodedAvLevelCell X
8734 pchAveragedQueueLengthCell X
8735 pchQueuePagesDiscardedCell X
8760 cpue0LoadRatio X
8761 cpue1LoadRatio X
8803 tchOccupancy X
8813 faultyTrxNoBcch X

411--9001--125
4.3.1.1 OFS & OGS synthetic counters proposal

8110 hoIntraBtsFailRateTchTieringLargeToSmallPattern X
8111 hoIntraBtsFailRateTchTieringSmallToLargePattern X
8629 pcmErrCorrEfficiency X
8757 tdmaClassTchResourceFailureRatio X

4.4 Temporary observation counters (BSC 12000HC)

This section lists the temporary observation counters, grouped by counter family.
Temporary observation counters belong to the following families:
Temporary Abis interface (see Paragraph
Temporary interference
Temporary SS7 link
Temporary observation counters are BSC 12000HC only.
4.4.1 Temporary Abis interface

0/0 abisOutputUiFrame totalizer
1/0 ss7OutputMsu totalizer
1/0 abisInputUiFrame totalizer
10/0 abisCongestionTimeCum value
10/0 abisCongestionTimeEch value
10/0 abisCongestionTimeMoy value
10/0 abisCongestionTimeMax value
2/0 ss7Level2ErrorNegAckRec totalizer
2/0 abisOutputIFrame totalizer
3/0 ss7Level3ErrorDelay totalizer
3/0 abisInputIFrame totalizer
4/0 abisOutputUiByte totalizer
5/0 abisInputUiByte totalizer
6/0 abisOutputIByte totalizer
7/0 abisInputIByte totalizer
8/0 abisLevel2ErrorRxSup1 totalizer
8/1 abisLevel2ErrorRxDm1 totalizer
8/10 abisLevel2ErrorRxFrmr totalizer
8/11 abisLevel2ErrorRxNoImpl totalizer
8/12 abisLevel2ErrorBadLg totalizer
8/2 abisLevel2ErrorRxUa1 totalizer
8/3 abisLevel2ErrorRxUa0 totalizer
8/4 abisLevel2ErrorRxDm0 totalizer

411--9001--125
8/5 abisLevel2ErrorRxSabme totalizer

8/6 abisLevel2ErrorTxNSabme totalizer
8/7 abisLevel2ErrorTxNDisc totalizer
8/8 abisLevel2ErrorReqOutState totalizer
8/9 abisLevel2ErrorBadRxNr totalizer
9/0 abisUnavailabilityTimeCum value
9/0 abisUnavailabilityTimeEch value
9/0 abisUnavailabilityTimeMoy value
9/0 abisUnavailabilityTimeMax value
4.4.2 Temporary interference

0/0 channelIdleLevelCum value
0/0 channelIdleLevelEch value
0/0 channelIdleLevelMoy value
0/0 channelIdleLevelMax value
4.4.3 Temporary SS7 link

0/0 ss7InputMsu totalizer
2/1 ss7Level2ErrorNegAckTrans totalizer
2/2 ss7Level2ErrorMsuCongest totalizer
2/3 ss7Level2ErrorSuErr totalizer
3/1 ss7Level3ErrorHighErrRate totalizer
3/3 ss7Level3ErrorDistOutServ totalizer

4.5 Manager counters

This section lists manager counters, grouped by counter families. Manager counters
belong to the following families:
Manager cpu
Manager database
Manager disk usage
Manager X25
4.5.1 Manager cpu

60000/0 omcUnixCpu0UsedCum value
60000/0 omcUnixCpu0UsedEch value
60000/0 omcUnixCpu0Used value
60001/0 omcUnixCpu1UsedCum value
60001/0 omcUnixCpu1UsedEch value
60001/0 omcUnixCpu1Used value
4.5.2 Manager database

60012/0 omcSybaseTotalError totalizer
60013/0 omcSybaseTotalRead totalizer
60014/0 omcSybaseTotalWrite totalizer
60015/0 omcSybaseCpuBusy totalizer
60016/0 omcSybaseIoBusy totalizer
60017/0 omcSybaseIdle totalizer
60018/0 omcSybasePacketIn totalizer
60019/0 omcSybasePacketOut totalizer
60020/0 omcSybasePacketErr totalizer
4.5.3 Manager disk usage

0/0 traceDatabaseSeg0UsedCum value
0/0 traceDatabaseSeg0UsedEch value

411--9001--125
0/0 traceDatabaseSeg0Used value

0/0 traceDatabaseSeg1UsedCum value
0/0 traceDatabaseSeg1UsedEch value
0/0 traceDatabaseSeg1Used value
60002/0 omcUnixSwapCum value
60002/0 omcUnixSwapEch value
60002/0 omcUnixSwap value
60004/0 omcUnixRootPartitionCum value
60004/0 omcUnixRootPartitionEch value
60004/0 omcUnixRootPartition value
60005/0 omcUnixTmpPartitionCum value
60005/0 omcUnixTmpPartitionEch value
60005/0 omcUnixTmpPartition value
60007/0 omcUnixObsPartitionCum value
60007/0 omcUnixObsPartitionEch value
60007/0 omcUnixObsPartition value
60037/0 omcUnixBasePartitionCum value
60037/0 omcUnixBasePartitionEch value
60037/0 omcUnixBasePartition value
60038/0 omcUnixDataPartitionCum value
60038/0 omcUnixDataPartitionEch value
60038/0 omcUnixDataPartition value
60039/0 omcDatabaseUsedCum value
60039/0 omcDatabaseUsedEch value
60039/0 omcDatabaseUsed value
60040/0 fmOmcDatabaseUsedCum value
60040/0 fmOmcDatabaseUsedEch value
60040/0 fmOmcDatabaseUsed value
60041/0 omcUnixMapsPartitionCum value
60041/0 omcUnixMapsPartitionEch value
60041/0 omcUnixMapsPartition value
60042/0 omcUnixHomePartitionCum value
60042/0 omcUnixHomePartitionEch value

60042/0 omcUnixHomePartition value

60043/0 omcUnixOptPartitionCum value
60043/0 omcUnixOptPartitionEch value
60043/0 omcUnixOptPartition value
60044/0 omcUnixUsrPartitionCum value
60044/0 omcUnixUsrPartitionEch value
60044/0 omcUnixUsrPartition value
60045/0 omcUnixVarPartitionCum value
60045/0 omcUnixVarPartitionEch value
60045/0 omcUnixVarPartition value
60046/0 omcUnixOmcPartitionCum value
60046/0 omcUnixOmcPartitionEch value
60046/0 omcUnixOmcPartition value
60047/0 omcUnixWholeOmcPartitionCum value
60047/0 omcUnixWholeOmcPartitionEch value
60047/0 omcUnixWholeOmcPartition value
60048/0 omcUnixWholeCmnPartitionCum value
60048/0 omcUnixWholeCmnPartitionEch value
60048/0 omcUnixWholeCmnPartition value
60049/0 omcUnixWholeMdPartitionCum value
60049/0 omcUnixWholeMdPartitionEch value
60049/0 omcUnixWholeMdPartition value
4.5.4 Manager X25

60021/0 omcX25PacketInPort0 totalizer
60022/0 omcX25PacketOutPort0 totalizer
60023/0 omcX25CrcErrorsPort0 totalizer
60024/0 omcX25AbortsPort0 totalizer

411--9001--125

4.6 Md counters
This section lists the md counters, grouped by counter family. Md counters belong
to the following families:
FMD--R disk usage
FTAM
MD--R activity
MD--R cpu
MD--R database
MD--R X25
4.6.1 FMD-- R disk usage

143/0 unixMdrBasePartitionNMCSrvCum value
143/0 unixMdrBasePartitionNMCSrvEch value
143/0 unixMdrBasePartitionNMCSrv value
144/0 unixMdrDataPartitionNMCSrvCum value
144/0 unixMdrDataPartitionNMCSrvEch value
144/0 unixMdrDataPartitionNMCSrv value
145/0 unixCmnBasePartitionNMCSrvCum value
145/0 unixCmnBasePartitionNMCSrvEch value
145/0 unixCmnBasePartitionNMCSrv value
146/0 unixCmnDataPartitionNMCSrvCum value
146/0 unixCmnDataPartitionNMCSrvEch value
146/0 unixCmnDataPartitionNMCSrv value

147/0 cmDatabaseUsedCum value

147/0 cmDatabaseUsedEch value
147/0 cmDatabaseUsed value
148/0 fmDatabaseUsedCum value
148/0 fmDatabaseUsedEch value
148/0 fmDatabaseUsed value
149/0 fmLogUsedCum value
149/0 fmLogUsedEch value
149/0 fmLogUsed value
150/0 cmLogUsedCum value
150/0 cmLogUsedEch value
150/0 cmLogUsed value
151/0 unixMdScsePartitionNMCSrvCum value
151/0 unixMdScsePartitionNMCSrvEch value
151/0 unixMdScsePartitionNMCSrv value
152/0 unixMdRestoredPartitionNMCSrvCum value
152/0 unixMdRestoredPartitionNMCSrvEch value
152/0 unixMdRestoredPartitionNMCSrv value
88/0 unixSwapNMCSrvCum value
88/0 unixSwapNMCSrvEch value
88/0 unixSwapNMCSrv value
90/0 unixRootPartitionNMCSrvCum value
90/0 unixRootPartitionNMCSrvEch value
90/0 unixRootPartitionNMCSrv value
91/0 unixTmpPartitionNMCSrvCum value
91/0 unixTmpPartitionNMCSrvEch value
91/0 unixTmpPartitionNMCSrv value
93/0 unixObsPartitionCum value
93/0 unixObsPartitionEch value
93/0 unixObsPartition value
94/0 unixNotifPartitionCum value
94/0 unixNotifPartitionEch value
94/0 unixNotifPartition value

411--9001--125
97/0 unixTracePartitionCum value

97/0 unixTracePartitionEch value
97/0 unixTracePartition value
98/0 unixSsnPartitionCum value
98/0 unixSsnPartitionEch value
98/0 unixSsnPartition value
4.6.2 FTAM
129/0 ftamFtiGet totalizer
130/0 ftamFtiGetConf totalizer
131/0 ftamFtiPut totalizer
132/0 ftamFtiPutConf totalizer
133/0 ftamFtiDelete totalizer
134/0 ftamFtiDeleteConf totalizer
135/0 ftamFtiDir totalizer
136/0 ftamFtiDirConf totalizer
137/0 ftamFtiRename totalizer
138/0 ftamFtiRenameConf totalizer
4.6.3 MD-- R activity

100/0 ommdGetRequest totalizer
101/0 ommdGetConf totalizer
102/0 ommdCreRequest totalizer
103/0 ommdCreConf totalizer
104/0 ommdSetRequest totalizer
105/0 ommdSetConf totalizer
106/0 ommdDelRequest totalizer
107/0 ommdDelConf totalizer
108/0 ommdActRequest totalizer
109/0 ommdActConf totalizer
110/0 ommdCancelGetRequest totalizer

111/0 ommdCancelGetConf totalizer

112/0 omnetGetRequest totalizer
113/0 omnetGetConf totalizer
114/0 omnetCreRequest totalizer
115/0 omnetCreConf totalizer
116/0 omnetSetRequest totalizer
117/0 omnetSetConf totalizer
118/0 omnetDelRequest totalizer
119/0 omnetDelConf totalizer
120/0 omnetActRequest totalizer
121/0 omnetActConf totalizer
122/0 omnetCancelGetRequest totalizer
123/0 omnetCancelGetConf totalizer
124/0 notifsReceived totalizer
125/0 notifsSentOnce totalizer
126/0 notifsTransmitAgainOnce totalizer
127/0 notifsTransmitAgainTwiceAndMore totalizer
128/0 notifsReachMaxTransmit totalizer
70/0 scseTgeOut totalizer
71/0 scseRgeIn totalizer
72/0 scseFailConnect totalizer
73/0 scseTotTgeRefused totalizer
74/0 scseTotAssocFree totalizer
4.6.4 MD-- R cpu

84/0 unixCpu0UsedNMCSrvCum value
84/0 unixCpu0UsedNMCSrvEch value
84/0 unixCpu0UsedNMCSrv value
85/0 unixCpu1UsedNMCSrvCum value
85/0 unixCpu1UsedNMCSrvEch value
85/0 unixCpu1UsedNMCSrv value

411--9001--125
4.6.5 MD-- R database

40/0 sybaseTotalError totalizer
41/0 sybaseTotalRead totalizer
42/0 sybaseTotalWrite totalizer
43/0 sybaseCpuBusy totalizer
44/0 sybaseIoBusy totalizer
45/0 sybaseIdle totalizer
46/0 sybasePacketIn totalizer
47/0 sybasePacketOut totalizer
48/0 sybasePacketErr totalizer
4.6.6 MD--R X25

60/0 x25FrameInPort0NMCSrv totalizer
61/0 x25FrameOutPort0NMCSrv totalizer
62/0 x25CrcErrorPort0NMCSrv totalizer
63/0 x25AbortRcvPort0NMCSrv totalizer

4.7 Raw Permanent PCUSN Observation Counters

This section contains the following information:
PCUSN observation classes
4.7.1 PCUSN Observation Classes

The PCUSN produces observation counters for:
the network elements depending on the BSCs it is connected to
its own depending elements (logicalProcessor, pBlock, and framer).
The counters are not displayed on the Man--Machine Interface but are only sent to
the OMC--R Data Server (SDO).
The observed object classes found in the PCUSN observation records storing the
PCUSN related data are the following:
logicalProcessor (new class)
pBlock (new class)
framer (new class)
The observed object classes found in the PCUSN observation records storing the
BSS related data are the following:
bts
ccch (new class)
pcmCircuit
transceiver
These observed object classes of the PCUSN can be seen in the figure below:

411--9001--125
network
bsc pcusn
pcmCircuit btsSiteManager logicalProcessor framer
bts pModule
adjacentCellHandover transceiver pBlock
transceiverZone ccch
Legend: Classes that are already observed by the BSS observation.

Classes that produce observation counters for the PCUSN observation.
Figure 4--1 Observation Classes

4.7.2 PCUSN Observation Types

There are two types of PCUSN Observation types: OFS and ORT.
OFS counters are accessible by SDO (OMC--R data server)
ORT counters are accessible by the Command Console (CAS) of the PCUSN
OAM Plugin. ORT counters are cumulative and return to zero when the SPM is
reset.
The following table shows a list of the PCUSN OFS counters. The column on the
left shows the counter number. The next two columns show the class and name of
these counters as they appear in the CAS Interface. The final two columns show the
class and name of these counters as they appear in SDO output. In some cases, the
class and name of these types of counters can differ.
Name (CDL Component, CDL Attribute) Name (Id/SubId, Type,
Class)
Counter name
CDL CDL Attribute Id/SubId Type Class SDO name Created GPRS
Comp. in /
release EDGE
PcmLink octetsDn 15001/0 CUM PCM idem CDL Attribute V12.4C G/E
PcmLink octetsUp 15001/1 CUM PCM idem CDL Attribute V12.4C G/E
Bvc pduDataDn 15004/0 CUM CELL idem CDL Attribute V12.4C G/E
Bvc pduDataUp 15004/1 CUM CELL idem CDL Attribute V12.4C G/E
Bvc octetsDataDn 15005/0 CUM CELL idem CDL Attribute V12.4C G/E
Bvc octetsDataUp 15005/1 CUM CELL idem CDL Attribute V12.4C G/E
Bvc bvcBlockRequests 15007/0 CUM CELL octetDiscarded V14.2/3 G/E
Bvc maxSizeDataDn 15007/1 CUM CELL pcuDlThroughputCum V15.0 G
Bvc maxSizeDataUp 15007/1 NBS CELL pcuDlThroughputNbs V15.0 G
Bvc maxSizeDataUp 15007/1 AVG CELL AvgDlThroughput V14.2/3 G
Bvc bvct1TimeOuts 15008/0 MAX CELL MaxDlThroughput V14.2/3 G/E
Bvc bvcFlowControlRequests 15010/0 CUM CELL idem CDL Attribute V12.4C G/E
Bvc msFlowControlRequests 15010/1 CUM CELL idem CDL Attribute V12.4C G/E
Bvc llcDiscardedPdu 15012/0 CUM CELL idem CDL Attribute V12.4C G/E
Bvc llcDiscardedOctets 15012/1 CUM CELL idem CDL Attribute V12.4C G/E
Bvc msFlushLLRequest 15014/0 CUM CELL idem CDL Attribute V12.4C G/E
Lapd iFramesUp 15023/0 CUM LAPD CsPagingOnCcch V14.2/3 G/E
Lapd iFramesDn 15023/1 CUM LAPD PsPagingOnCcch V14.2/3 G/E
Lapd uiFramesUp 15024/0 CUM LAPD CsPagingOnPacch V14.2/3 G/E
CgiCell upMultiSlotRequests 15028/1 CUM CELL upMultiSlotRequest1 V12.4D G/E
CgiCell upMultiSlotAllocations 15029/1 CUM CELL upTbfGoldSatisfactMore90pCent V14.2/3 G/E
CgiCell upMultiSlotAllocations 15029/2 CUM CELL upTbfGoldSatisfactBet5090pCent V14.2/3 G/E

411--9001--125
Comp. in /
release EDGE
CgiCell upMultiSlotAllocations 15029/3 CUM CELL upTbfGoldSatisfactLess50pCent V14.2/3 G/E
CgiCell upMultiSlotAllocations 15029/4 CUM CELL upTbfGoldRejectedForMinTput V14.2/3 G/E
CgiCell dnMultiSlotRequests 15030/1 CUM CELL dwMultiSlotRequest1 V12.4D G/E
CgiCell dnMultiSlotAllocations 15031/1 CUM CELL FirstDlUnitDataFrame V12.4D G/E
CgiCell dnMultiSlotAllocations 15031/2 CUM CELL dlTBFAllocFailure V12.4D G/E
CgiCell dnMultiSlotAllocations 15031/3 CUM CELL dlTBFRadioFailure V12.4D G/E
CgiCell dnMultiSlotAllocations 15031/4 CUM CELL upTbfSilverSatisfactMore90pCent V14.2/3 G/E
CgiCell fullDuplexTbfEstablishment 15032/0 CUM CELL idem CDL Attribute V12.4C G/E
CgiCell closeEndedUpTbfEstablishment 15032/3 CUM CELL ulsecondPhaseAllocFailure V12.4D G/E
CgiCell upTbfReleases 15033/0 CUM CELL idem CDL Attribute V12.4C G/E
CgiCell dnTbfReleases 15033/1 CUM CELL idem CDL Attribute V12.4C G/E
CgiCell cumulativeTimeUpTbf 15034/0 CUM CELL PDANWithUlReq V12.4D G/E
CgiCell cumulativeTimeDnTbf 15034/1 CUM CELL upTbfSilverSatisfactBet5090pCent V14.2/3 G/E
CgiCell allocatedBlocksUpTbf 15036/0 CUM CELL ulsecondPhaseRadioFailure V12.4D G/E
Tdma localBusy 15038/0 CUM TDMA idem CDL Attribute V12.4C G/E
Tdma configuredTimeslots 15039/0 CUM TDMA cumulativeDnRxLev V14.2/3 G
Tdma cumulativeUpActiveTimeslots 15041/0 CUM TDMA upUserdatablocks V12.4D G
Tdma cumulativeUpTbfPerTimeslots 15043/0 CUM TDMA RequestedRetransmittedData- V12.4D G
BlocksDN
Tdma llcPacketsUp 15045/0 CUM TDMA idem CDL Attribute V12.4C G/E
Tdma llcPacketsDn 15045/1 CUM TDMA idem CDL Attribute V12.4C G/E
Tdma dataBlocksUp 15046/0 CUM TDMA idem CDL Attribute V12.4C G
Tdma dataBlocksDn 15046/1 CUM TDMA idem CDL Attribute V12.4C G
Tdma controlBlocksUp 15047/0 CUM TDMA idem CDL Attribute V12.4C G
Tdma controlBlocksDn 15047/1 CUM TDMA idem CDL Attribute V12.4C G
Tdma invalidBlocksUp 15048/0 CUM TDMA idem CDL Attribute V12.4C G
Tdma invalidProtocolErrorBlocksUp 15048/1 CUM TDMA idem CDL Attribute V12.4C G
Tdma outOfSequenceBlocksUp 15048/2 CUM TDMA idem CDL Attribute V12.4C G
Tdma packetAckNackUp 15049/0 CUM TDMA idem CDL Attribute V12.4C G
Tdma packetAckNackDn 15049/1 CUM TDMA idem CDL Attribute V12.4C G
Tdma totalRetransmissionRequested 15050/0 CUM TDMA idem CDL Attribute V12.4C G
Tdma cumulativeUpRxQual 15051/0 CUM TDMA idem CDL Attribute V12.4C G
Tdma cumulativeDnRxQual 15051/1 CUM TDMA idem CDL Attribute V14.2/3 G
Tdma cumulativeUpRxLev 15052/0 CUM TDMA idem CDL Attribute V14.2/3 G
Tdma nbSamplesUpQuality 15053/0 CUM TDMA idem CDL Attribute V14.2/3 G
Tdma nbSamplesDnQuality 15053/1 CUM TDMA idem CDL Attribute V14.2/3 G
Tdma retransmittedDataBlocksDn 15054/0 CUM TDMA idem CDL Attribute V12.4C G

Comp. in /
release EDGE
Tdma tbfNormalReleaseUp 15055/0 CUM TDMA idem CDL Attribute V12.4C G/E
Tdma tbfNormalReleaseDn 15055/1 CUM TDMA idem CDL Attribute V12.4C G/E
Tdma noPacketResourceReq 15056/0 CUM TDMA idem CDL Attribute V12.4C G/E
Ccch packetResourceRequest 15056/1 CUM CCCH idem CDL Attribute V12.4C G/E
Tdma lossOfComNN002Max 15057/0 CUM TDMA idem CDL Attribute V12.4C G/E
Tdma lossOfComT3169 15057/1 CUM TDMA idem CDL Attribute V12.4C G/E
Tdma lossOfComNT0001 15057/2 CUM TDMA idem CDL Attribute V12.4C G/E
Ccch upTbfImmediateAssignment 15058/0 CUM CCCH idem CDL Attribute V12.4C G/E
Ccch upTbfImmAssigRejectNoPdch 15058/1 CUM CCCH idem CDL Attribute V14.2/3 G/E
Ccch dnTbfImmediateAssignment 15058/2 CUM CCCH idem CDL Attribute V12.4C G/E
Ccch upTbfImmAssigRejectNoTs 15058/3 CUM CCCH dnPipebetween11and22kbps V12.4D G
Ccch upTbfImmAssigRejectNoTbf 15058/4 CUM CCCH dnPipebetween22and33kbps V12.4D G
Ccch channelRequest 15059/0 CUM CCCH channelRequestCcch V12.4C G/E
Ccch deleteIndicationUp 15060/0 CUM CCCH dnPipeGreater33kbps V12.4D G
Ccch deleteIndicationDn 15060/1 CUM CCCH upTbfSilverRejectedForMinTput V14.2/3 G/E
Ccch packetUpAssignment 15061/0 CUM CCCH upPipeless11kbps V12.4D G
Ccch packetDnAssignment 15061/1 CUM CCCH upTbfBronzeSatisfact- V14.2/3 G/E
More90pCent
Ccch upTbfPacketAccessRejectNoPdch 15062/0 CUM CCCH upPipeGreater11kbps V12.4D G
Ccch upTbfPacketAccessRejectNoTs 15062/1 CUM CCCH dnPipeLess11kbps V12.4D G
Ccch upTbfPacketAccessRejectNoTbf 15062/2 CUM CCCH upTbfSilverSatisfactLess50pCent V14.2/3 G/E
Ccch dnTbfPacketAccessRejectNoPdch 15062/3 CUM CCCH upTbfBronzeSatisfact- V14.2/3 G/E
Bet5090pCent
Ccch dnTbfPacketAccessRejectNoTs 15062/4 CUM CCCH upTbfBronzeSatisfactLess50pCent V14.2/3 G/E
Ccch dnTbfPacketAccessRejectNoTbf 15062/5 CUM CCCH upTbfBronzeRejectedForMinTput V14.2/3 G/E
PBlock cpuPBlockUtilAvg 15063/0 AVG PBLK idem CDL Attribute V12.4D G/E
PBlock cpuPBlockUtilMax 15063/2 MAX PBLK idem CDL Attribute V12.4D G/E
Lp cpuUtilAvg 15066/0 AVG LP idem CDL Attribute V12.4C G/E
Lp cpuUtilAvgMin 15066/0 MIN LP idem CDL Attribute V12.4C G/E
Lp cpuUtilAvgMax 15066/0 MAX LP idem CDL Attribute V12.4C G/E
Lp memoryCapacity 15067/0 CUM LP memoryCapacityFastRam V12.4C G/E
Lp memoryCapacity 15067/1 CUM LP memoryCapacityNormalRam V12.4C G/E
Lp memoryCapacity 15067/2 CUM LP memoryCapacitySharedRam V12.4C G/E
Lp memoryUsageAvg 15068/0 AVG LP memoryUsageAvgFastRam V12.4C G/E
Lp memoryUsageAvgMin 15068/0 MIN LP memoryUsageAvgMinFastRam V12.4C G/E
Lp memoryUsageAvgMax 15068/0 MAX LP memoryUsageAvgMaxFastRam V12.4C G/E
Lp memoryUsageAvg 15068/1 AVG LP memoryUsageAvgNormalRam V12.4C G/E
Lp memoryUsageAvgMin 15068/1 MIN LP memoryUsageAvgMinNormalRam V12.4C G/E

411--9001--125
Comp. in /
release EDGE
Lp memoryUsageAvgMax 15068/1 MAX LP memoryUsageAvgMaxNormal- V12.4C G/E
Ram
Lp memoryUsageAvg 15068/2 AVG LP memoryUsageAvgSharedRam V12.4C G/E
Lp memoryUsageAvgMin 15068/2 MIN LP memoryUsageAvgMinSharedRam V12.4C G/E
Lp memoryUsageAvgMax 15068/2 MAX LP memoryUsageAvgMaxSharedRam V12.4C G/E
Lp sharedMsgBlockCapacity 15069/0 CUM LP idem CDL Attribute V12.4C G/E
Lp sharedMsgBlockUsageAvg 15069/1 AVG LP idem CDL Attribute V12.4C G/E
Lp sharedMsgBlockUsageAvgMin 15069/1 MIN LP idem CDL Attribute V12.4C G/E
Lp sharedMsgBlockUsageAvgMax 15069/1 MAX LP idem CDL Attribute V12.4C G/E
Lp localMsgBlockCapacity 15069/2 CUM LP idem CDL Attribute V12.4C G/E
Lp localMsgBlockUsageAvg 15069/3 AVG LP idem CDL Attribute V12.4C G/E
Lp localMsgBlockUsageMin 15069/3 MIN LP idem CDL Attribute V12.4C G/E
Lp localMsgBlockUsageMax 15069/3 MAX LP idem CDL Attribute V12.4C G/E
Framer rxBytes 15070/0 CUM FRAMR idem CDL Attribute V12.4C G/E
Framer txBytes 15070/1 CUM FRAMR idem CDL Attribute V12.4C G/E
Framer rxFrames 15071/0 CUM FRAMR idem CDL Attribute V12.4C G/E
Framer txFrames 15071/1 CUM FRAMR idem CDL Attribute V12.4C G/E
Framer rxTotalLinkUtil 15072/0 CUM FRAMR idem CDL Attribute V12.4C G/E
PcmLink psPaging 15073/0 CUM PCM idem CDL Attribute V14.2/3 G/E
PcmLink csPaging 15073/1 CUM PCM idem CDL Attribute V14.2/3 G/E
CgiCell dyAgprsNbModif 15075/0 CUM CELL idem CDL Attribute V14.2/3 G/E
CgiCell nonAckUpTbfEstablishment 15075/1 CUM CELL pcuDyAgprsNbTimeslotsCum V15.0 G/E
CgiCell ackUpTbfEstablishment 15075/1 NBS CELL pcuDyAgprsNbTimeslotsNbs V15.0 G/E
CgiCell ackUpTbfEstablishment 15075/1 AVG CELL dyAgprsAvgNbTimeslots V15.0 G/E
CgiCell dyAgprsMinNbTimeslots 15075/2 MIN CELL idem CDL Attribute V14.2/3 G/E
CgiCell dyAgprsMaxNbTimeslots 15075/3 MAX CELL idem CDL Attribute V14.2/3 G/E
CgiCell nonAckDnTbfEstablishment 15076/0 CUM CELL pcuDyAgprsLoadCriterionCum V15.0 G/E
CgiCell ackDnTbfEstablishment 15076/0 NBS CELL pcuDyAgprsLoadCriterionNbs V15.0 G/E
CgiCell ackDnTbfEstablishment 15076/0 AVG CELL dyAgprsAvgLoadCriterion V14.2/3 G/E
CgiCell dyAgprsMaxLoadCriterion 15076/1 MAX CELL idem CDL Attribute V14.2/3 G/E
CgiCell dnTbfGoldSatisfactMore90pCent 15077/0 CUM CELL idem CDL Attribute V14.2/3 G/E
CgiCell dnTbfGoldSatisfactBet5090pCent 15077/1 CUM CELL idem CDL Attribute V14.2/3 G/E
CgiCell dnTbfGoldSatisfactLess50pCent 15077/2 CUM CELL idem CDL Attribute V14.2/3 G/E
CgiCell dnTbfGoldRejectedForMinTput 15077/3 CUM CELL idem CDL Attribute V14.2/3 G/E
CgiCell dnTbfSilverSatisfactMore90pCent 15078/0 CUM CELL idem CDL Attribute V14.2/3 G/E
CgiCell dnTbfSilverSatisfactBet5090pCent 15078/1 CUM CELL idem CDL Attribute V14.2/3 G/E
CgiCell dnTbfSilverSatisfactLess50pCent 15078/2 CUM CELL idem CDL Attribute V14.2/3 G/E
CgiCell dnTbfSilverRejectedForMinTput 15078/3 CUM CELL idem CDL Attribute V14.2/3 G/E
CgiCell dnTbfBronzeSatisfactMore90pCent 15079/0 CUM CELL idem CDL Attribute V14.2/3 G/E
CgiCell dnTbfBronzeSatisfactBet5090pCent 15079/1 CUM CELL idem CDL Attribute V14.2/3 G/E

Comp. in /
release EDGE
CgiCell dnTbfBronzeSatisfactLess50pCent 15079/2 CUM CELL idem CDL Attribute V14.2/3 G/E
CgiCell dnTbfBronzeRejectedForMinTput 15079/3 CUM CELL idem CDL Attribute V14.2/3 G/E
Tdma pcuEdgeTdma15100s0 15100/0 CUM TDMA idem CDL Attribute V15.0 E
Tdma pcuEdgeDataBlocksReceivedUp 15101/0 CUM TDMA idem CDL Attribute V15.0 E
Tdma pcuEdgeDnCum8PskMeanBep 15102/0 CUM TDMA idem CDL Attribute V15.0 E
Tdma pcuEdgeDnNbs8PskMeanBep 15102/0 NBS TDMA idem CDL Attribute V15.0 E
Tdma pcuEdgeDnNbs8PskMeanBep 15102/0 AVG TDMA pcuEdgeDnAvg8PskMeanBep V15.0 E
Tdma pcuEdgeDnCumGmskMeanBep 15103/0 CUM TDMA idem CDL Attribute V15.0 E
Tdma pcuEdgeDnNbsGmskMeanBep 15103/0 NBS TDMA idem CDL Attribute V15.0 E
Tdma pcuEdgeDnNbsGmskMeanBep 15103/0 AVG TDMA pcuEdgeDnAvgGmskMeanBep V15.0 E
Tdma pcuEdgeUpCumMeanBep 15104/0 CUM TDMA idem CDL Attribute V15.0 E
Tdma pcuEdgeUpNbsMeanBep 15104/0 NBS TDMA idem CDL Attribute V15.0 E
Tdma pcuEdgeUpNbsMeanBep 15104/0 AVG TDMA pcuEdgeUpAvgMeanBep V15.0 E
Tdma pcuEdgeTdma15108s0 15108/0 CUM TDMA idem CDL Attribute V15.0 G/E
Tdma pcuEdgeTdma15109s0 15109/0 CUM TDMA idem CDL Attribute V15.0 G/E
CgiCell pcuAgprsMainNbofBlocksDn 15110/0 CUM CELL idem CDL Attribute V15.0 G/E
CgiCell pcuEdgeDowngradedTbf 15111/0 CUM CELL idem CDL Attribute V15.0 E
CgiCell pcuEdgeDowngradedTbf 15111/0 NBS CELL pcuEdgeDowngradedTbfNbs V15.0 E
CgiCell pcuEdgeDowngradedTbf 15111/0 AVG CELL pcuEdgeDowngradedTbfAvg V15.0 E
CgiCell pcuEdgeUpCumUsefulDataPerCell 15112/0 CUM CELL idem CDL Attribute V15.0 E
CgiCell pcuEdgeUpCumUsefulDataPerCell 15112/0 NBS CELL pcuEdgeUpNbsUsefulDataPerCell V15.0 E
CgiCell pcuEdgeUpCumUsefulDataPerCell 15112/0 AVG CELL pcuEdgeUpAvgUsefulDataPerCell V15.0 E
CgiCell pcuEdgeDnCumUsefulDataPerCell 15113/0 CUM CELL idem CDL Attribute V15.0 E
CgiCell pcuEdgeDnCumUsefulDataPerCell 15113/0 NBS CELL pcuEdgeDnNbsUsefulDataPerCell V15.0 E
CgiCell pcuEdgeDnCumUsefulDataPerCell 15113/0 AVG CELL pcuEdgeDnAvgUsefulDataPerCell V15.0 E
CgiCell pcuEdgeCell15114s0 15114/0 CUM CELL idem CDL Attribute V15.0 E
CgiCell pcuDynAgprsJokerCumNbTimeslot 15118/0 CUM CELL idem CDL Attribute V15.0 G/E
CgiCell pcuDynAgprsJokerCumNbTimeslot 15118/0 NBS CELL pcuDynAgprsJokerNbsNbTimes- V15.0 G/E
lot
CgiCell pcuDynAgprsJokerCumNbTimeslot 15118/0 AVG CELL pcuDynAgprsJokerAvgNbTimes- V15.0 G/E
lot
CgiCell pcuDynAgprsJokerMinNbTimeslot 15118/0 MIN CELL idem CDL Attribute V15.0 G/E
CgiCell pcuDynAgprsJokerMaxNbTimeslot 15118/0 MAX CELL idem CDL Attribute V15.0 G/E
CgiCell pcuAgprsJokerNbofBlocksDn 15119/0 CUM CELL idem CDL Attribute V15.0 G/E

411--9001--125
Comp. in /
release EDGE
CgiCell pcuEdgeTbfEstReq 15122/0 CUM CELL idem CDL Attribute V15.0 E
CgiCell pcuEdgeUpUsefulDataDurationPerCell 15123/0 CUM CELL idem CDL Attribute V15.0 E
CgiCell pcuEdgeDnUsefulDataDurationPerCell 15124/0 CUM CELL idem CDL Attribute V15.0 E
CgiCell pcuAgprsMainNbofBlocksUp 15127/0 CUM CELL idem CDL Attribute V15.0 G/E
CgiCell pcuAgprsJokerNbofBlocksUp 15128/0 CUM CELL idem CDL Attribute V15.0 G/E
Tdma pcuLackAbisJokerTSCum 15129/0 CUM TDMA idem CDL Attribute V15.0 G/E
Tdma pcuLackAbisJokerTSNbs 15129/0 NBS TDMA idem CDL Attribute V15.0 G/E
Tdma pcuLackAbisJokerTSNbs 15129/0 AVG TDMA pcuLackAbisJokerTSAvg V15.0 G/E
Tdma pcuEdgeDnTransmittedMcs2 15132/0 CUM TDMA idem CDL Attribute V15.0 E
Tdma pcuEdgeMcs2RequestRetransData- 15142/0 CUM TDMA idem CDL Attribute V15.0 E
BlockDn
BlockDn
BlockDn
BlockDn
BlockDn
BlockDn
BlockDn
Tdma pcuEdgeLADnTargetedTransmit- 15152/0 CUM TDMA idem CDL Attribute V15.0 E
tedMcs2
tedMcs3
tedMcs5
tedMcs6
tedMcs7

Comp. in /
release EDGE
tedMcs8
tedMcs9
Tdma pcuEdgeUpTransmittedMcs2 15162/0 CUM TDMA idem CDL Attribute V15.0 E
BlockUp
BlockUp
BlockUp
BlockUp
BlockUp
BlockUp
BlockUp
Tdma pcuEdgeLAUpTargetedTransmit- 15182/0 CUM TDMA idem CDL Attribute V15.0 E
tedMcs2
tedMcs3
tedMcs5
tedMcs6
tedMcs7
tedMcs8
tedMcs9
Ccch pcuChannelRequestOnePhase 15190/0 CUM CCCH idem CDL Attribute V15.0 G/E
Ccch pcuUpTbfImmediateAssignmentOne- 15191/0 CUM CCCH idem CDL Attribute V15.0 G/E
Phase
Ccch pcuContentionFailureOnePhase 15192/0 CUM CCCH idem CDL Attribute V15.0 G/E
CgiCell pcuUpThroughputCum 15193/0 CUM CELL idem CDL Attribute V15.0 G
CgiCell pcuUpThroughputNbs 15193/0 NBS CELL idem CDL Attribute V15.0 G

411--9001--125
Comp. in /
release EDGE
15193/0 AVG CELL pcuUpThroughputAvg V15.0 G
CgiCell pcuUpPipeGreater22kbps 15194/0 CUM CELL idem CDL Attribute V15.0 G
CgiCell pcuDnPreEstWithLLCFrameTrans- 15195/0 CUM CELL idem CDL Attribute V15.0 G/E
mitted
4.7.3 PCUSN counter families

This sections lists all the counter families that consist of PCUSN counters, and lists
the counters that belong to each family.
PCUSN counters belong to the following families:
EDGE on PCU
GPRS EDGE
GPRS on PCU
4.7.3.1 EDGE on PCU

15100/0 pcuEdgeTdma15100s0 totalizer
15101/0 pcuEdgeDataBlocksReceivedUp totalizer
15102/0 pcuEdgeDnCum8PskMeanBep load
15102/0 pcuEdgeDnNbs8PskMeanBep load
15102/0 pcuEdgeDnAvg8PskMeanBep load
15103/0 pcuEdgeDnCumGmskMeanBep load
15103/0 pcuEdgeDnNbsGmskMeanBep load
15103/0 pcuEdgeDnAvgGmskMeanBep load
15104/0 pcuEdgeUpCumMeanBep load
15104/0 pcuEdgeUpNbsMeanBep load
15104/0 pcuEdgeUpAvgMeanBep load
15111/0 pcuEdgeDowngradedTbf load

15111/0 pcuEdgeDowngradedTbfNbs load

15111/0 pcuEdgeDowngradedTbfAvg load
15112/0 pcuEdgeUpCumUsefulDataPerCell load
15112/0 pcuEdgeUpNbsUsefulDataPerCell load
15112/0 pcuEdgeUpAvgUsefulDataPerCell load
15113/0 pcuEdgeDnCumUsefulDataPerCell load
15113/0 pcuEdgeDnNbsUsefulDataPerCell load
15113/0 pcuEdgeDnAvgUsefulDataPerCell load
15114/0 pcuEdgeCell15114s0 totalizer
15122/0 pcuEdgeTbfEstReq totalizer
15123/0 pcuEdgeUpUsefulDataDurationPerCell totalizer
15124/0 pcuEdgeDnUsefulDataDurationPerCell totalizer
15132/0 pcuEdgeDnTransmittedMcs2 totalizer
15142/0 pcuEdgeMcs2RequestRetransDataBlockDn totalizer

411--9001--125
15152/0 pcuEdgeLADnTargetedTransmittedMcs2 totalizer

15162/0 pcuEdgeUpTransmittedMcs2 totalizer
15172/0 pcuEdgeMcs2RequestRetransDataBlockUp totalizer
15182/0 pcuEdgeLAUpTargetedTransmittedMcs2 totalizer

4.7.3.2 GPRS EDGE

15001/0 octetsDn totalizer
15001/1 octetsUp totalizer
15004/0 pduDataDn totalizer
15004/1 pduDataUp totalizer
15005/0 octetsDataDn totalizer
15005/1 octetsDataUp totalizer
15007/0 octetDiscarded totalizer
15008/0 MaxDlThroughput totalizer
15010/0 bvcFlowControlRequests totalizer
15010/1 msFlowControlRequests totalizer
15012/0 llcDiscardedPdu totalizer
15012/1 llcDiscardedOctets totalizer
15014/0 msFlushLLRequest totalizer
15023/0 CsPagingOnCcch totalizer
15023/1 PsPagingOnCcch totalizer
15024/0 CsPagingOnPacch totalizer
15028/1 upMultiSlotRequest1 totalizer
15029/1 upTbfGoldSatisfactMore90pCent totalizer
15029/2 upTbfGoldSatisfactBet5090pCent totalizer
15029/3 upTbfGoldSatisfactLess50pCent totalizer
15029/4 upTbfGoldRejectedForMinTput totalizer
15030/1 dwMultiSlotRequest1 totalizer
15031/1 FirstDlUnitDataFrame totalizer
15031/2 dlTBFAllocFailure totalizer
15031/3 dlTBFRadioFailure totalizer

411--9001--125
15031/4 upTbfSilverSatisfactMore90pCent totalizer

15032/0 fullDuplexTbfEstablishment totalizer
15032/3 ulsecondPhaseAllocFailure totalizer
15033/0 upTbfReleases totalizer
15033/1 dnTbfReleases totalizer
15034/0 PDANWithUlReq totalizer
15034/1 upTbfSilverSatisfactBet5090pCent totalizer
15036/0 ulsecondPhaseRadioFailure totalizer
15038/0 localBusy totalizer
15045/0 llcPacketsUp totalizer
15045/1 llcPacketsDn totalizer
15055/0 tbfNormalReleaseUp totalizer
15055/1 tbfNormalReleaseDn totalizer
15056/0 noPacketResourceReq totalizer
15056/1 packetResourceRequest totalizer
15057/0 lossOfComNN002Max totalizer
15057/1 lossOfComT3169 totalizer
15057/2 lossOfComNT0001 totalizer
15058/0 upTbfImmediateAssignment totalizer
15058/1 upTbfImmAssigRejectNoPdch totalizer
15058/2 dnTbfImmediateAssignment totalizer
15059/0 channelRequestCcch totalizer
15060/1 upTbfSilverRejectedForMinTput totalizer
15061/1 upTbfBronzeSatisfactMore90pCent totalizer
15062/2 upTbfSilverSatisfactLess50pCent totalizer
15062/3 upTbfBronzeSatisfactBet5090pCent totalizer
15062/4 upTbfBronzeSatisfactLess50pCent totalizer
15062/5 upTbfBronzeRejectedForMinTput totalizer
15063/0 cpuPBlockUtilCum load
15063/0 cpuPBlockUtilNbs load
15063/0 cpuPBlockUtilAvg load

15063/2 cpuPBlockUtilMax totalizer

15066/0 cpuUtilAvgMin load
15066/0 cpuUtilAvgMax load
15066/0 cpuUtilCum load
15066/0 cpuUtilNbs load
15066/0 cpuUtilAvg load
15067/0 memoryCapacityFastRam totalizer
15067/1 memoryCapacityNormalRam totalizer
15067/2 memoryCapacitySharedRam totalizer
15068/0 memoryUsageAvgMinFastRam load
15068/0 memoryUsageAvgMaxFastRam load
15068/0 memoryUsageFastRamCum load
15068/0 memoryUsageFastRamNbs load
15068/0 memoryUsageAvgFastRam load
15068/1 memoryUsageAvgMinNormalRam load
15068/1 memoryUsageAvgMaxNormalRam load
15068/1 memoryUsageNormalRamCum load
15068/1 memoryUsageNormalRamNbs load
15068/1 memoryUsageAvgNormalRam load
15068/2 memoryUsageAvgMinSharedRam load
15068/2 memoryUsageAvgMaxSharedRam load
15068/2 memoryUsageSharedRamCum load
15068/2 memoryUsageSharedRamNbs load
15068/2 memoryUsageAvgSharedRam load
15069/0 sharedMsgBlockCapacity totalizer
15069/1 sharedMsgBlockUsageAvgMin load
15069/1 sharedMsgBlockUsageAvgMax load
15069/1 sharedMsgBlockUsageCum load
15069/1 sharedMsgBlockUsageNbs load
15069/1 sharedMsgBlockUsageAvg load
15069/2 localMsgBlockCapacity totalizer
15069/3 localMsgBlockUsageMin load
15069/3 localMsgBlockUsageMax load

411--9001--125
15069/3 localMsgBlockUsageCum load

15069/3 localMsgBlockUsageNbs load
15069/3 localMsgBlockUsageAvg load
15070/0 rxBytes totalizer
15070/1 txBytes totalizer
15071/0 rxFrames totalizer
15071/1 txFrames totalizer
15072/0 rxTotalLinkUtil totalizer
15073/0 psPaging totalizer
15073/1 csPaging totalizer
15075/0 dyAgprsNbModif totalizer
15075/1 pcuDyAgprsNbTimeslotsCum load
15075/1 pcuDyAgprsNbTimeslotsNbs load
15075/1 dyAgprsAvgNbTimeslots load
15075/2 dyAgprsMinNbTimeslots totalizer
15075/3 dyAgprsMaxNbTimeslots totalizer
15076/0 pcuDyAgprsLoadCriterionCum load
15076/0 pcuDyAgprsLoadCriterionNbs load
15076/0 dyAgprsAvgLoadCriterion load
15076/1 dyAgprsMaxLoadCriterion totalizer
15077/0 dnTbfGoldSatisfactMore90pCent totalizer
15077/1 dnTbfGoldSatisfactBet5090pCent totalizer
15077/2 dnTbfGoldSatisfactLess50pCent totalizer
15077/3 dnTbfGoldRejectedForMinTput totalizer
15078/0 dnTbfSilverSatisfactMore90pCent totalizer
15078/1 dnTbfSilverSatisfactBet5090pCent totalizer
15078/2 dnTbfSilverSatisfactLess50pCent totalizer
15078/3 dnTbfSilverRejectedForMinTput totalizer
15079/0 dnTbfBronzeSatisfactMore90pCent totalizer
15079/1 dnTbfBronzeSatisfactBet5090pCent totalizer
15079/2 dnTbfBronzeSatisfactLess50pCent totalizer
15079/3 dnTbfBronzeRejectedForMinTput totalizer
15110/0 pcuAgprsMainNbofBlocksDn totalizer

15118/0 pcuDynAgprsJokerCumNbTimeslot totalizer

15118/0 pcuDynAgprsJokerNbsNbTimeslot totalizer
15118/0 pcuDynAgprsJokerAvgNbTimeslot totalizer
15118/0 pcuDynAgprsJokerMinNbTimeslot totalizer
15118/0 pcuDynAgprsJokerMaxNbTimeslot totalizer
15119/0 pcuAgprsJokerNbofBlocksDn totalizer
15127/0 pcuAgprsMainNbofBlocksUp totalizer
15128/0 pcuAgprsJokerNbofBlocksUp totalizer
15129/0 pcuLackAbisJokerTSCum load
15129/0 pcuLackAbisJokerTSNbs load
15129/0 pcuLackAbisJokerTSAvg load
15190/0 pcuChannelRequestOnePhase totalizer
15191/0 pcuUpTbfImmediateAssignmentOnePhase totalizer
15192/0 pcuContentionFailureOnePhase totalizer
15195/0 pcuDnPreEstWithLLCFrameTransmitted totalizer
2066/0 suspendRequest totalizer
2067/0 resumeSuccess totalizer
2068/0 resumeFailureAfterHOInterRA totalizer
2068/1 resumeFailureAfterHOInterBSC totalizer
2071/0 agprsSuspendRequestProcedures totalizer
2071/1 agprsSuspendRequestMessages totalizer
2072/0 agprsSuspendNack totalizer
2073/0 agprsResumeRequest totalizer
2074/0 agprsResumeNack totalizer

411--9001--125
4.7.3.3 GPRS on PCU

15007/1 pcuDlThroughputCum load
15007/1 pcuDlThroughputNbs load
15007/1 AvgDlThroughput load
15039/0 cumulativeDnRxLev totalizer
15041/0 upUserdatablocks totalizer
15043/0 RequestedRetransmittedDataBlocksDN totalizer
15046/0 dataBlocksUp totalizer
15046/1 dataBlocksDn totalizer
15047/0 controlBlocksUp totalizer
15047/1 controlBlocksDn totalizer
15048/0 invalidBlocksUp totalizer
15048/1 invalidProtocolErrorBlocksUp totalizer
15048/2 outOfSequenceBlocksUp totalizer
15049/0 packetAckNackUp totalizer
15049/1 packetAckNackDn totalizer
15050/0 totalRetransmissionRequested totalizer
15051/0 cumulativeUpRxQual totalizer
15051/1 cumulativeDnRxQual totalizer
15052/0 cumulativeUpRxLev totalizer
15053/0 nbSamplesUpQuality totalizer
15053/1 nbSamplesDnQuality totalizer
15054/0 retransmittedDataBlocksDn totalizer
15058/3 dnPipebetween11and22kbps totalizer
15058/4 dnPipebetween22and33kbps totalizer
15060/0 dnPipeGreater33kbps totalizer
15061/0 upPipeless11kbps totalizer
15062/0 upPipeGreater11kbps totalizer
15062/1 dnPipeLess11kbps totalizer
15193/0 pcuUpThroughputCum load
15193/0 pcuUpThroughputNbs load

15193/0 pcuUpThroughputAvg load

15194/0 pcuUpPipeGreater22kbps totalizer
4.7.4 Throughput Counters and Satisfaction Rate Counters

This following is a list of these counters:
Counter No. Q3 name

15077/0 dnTbfGoldSatisfactMore90pCent
15077/1 dnTbfGoldSatisfactBet5090pCent
15077/2 dnTbfGoldSatisfactLess50pCent
15078/0 dnTbfSilverSatisfactMore90pCent
15078/1 dnTbfSilverSatisfactBet5090pCent
15078/2 dnTbfSilverSatisfactLess50pCent
15079/0 dnTbfBronzeSatisfactMore90pCent
15079/1 dnTbfBronzeSatisfactBet5090pCent
15079/2 dnTbfBronzeSatisfactMore90pCent
15029/1 upTbfGoldSatisfactMore90pCent
15029/2 upTbfGoldSatisfactBet5090pCent
15029/3 upTbfGoldSatisfactLess50pCent
15031/4 upTbfSilverSatisfactMore90pCent
15034/1 upTbfSilverSatisfactBet5090pCent
15062/2 upTbfSilverSatisfactLess50pCent
15061/1 upTbfBronzeSatisfactMore90pCent
15062/3 upTbfBronzeSatisfactBet5090pCent
15062/4 upTbfBronzeSatisfactMore90pCent
15079/2 dnTbfBronzeSatisfactLess50pCent
15058/3 dnPipeBetween11and22kbps
15058/4 dnPipebetween22and33kbps
15060/0 dnPipeGreater33kbps
15061/0 upPipeless11kbps
15062/0 upPipeGreater11kbps
15062/1 dnPipeLess11kbps
In the following paragraphs:

<direction> takes place for up and dn (i.e uplink or downlink)
<ServiceClass> takes place for Gold, Silver or Bronze.

411--9001--125
The following downlink throughput counters:

dnPipeLess11kbps
dnPipeBetween11and22kbps
dnPipeBetween22and33kbps
dnPipeGreater33kbps
provide altogether a downlink throughput histogram in the realted cell.
Each one represents the cumulative number of times a throughput between the
specified limits is reached in dowlnlink direction by a MS in the cell.
The following uplink throughput counters:
upPipeLess11kbps
upPipeGreater11kbps
provide altogether an uplink throughput histogram in the related cell.
Each one represents the cumulative number of times a throughput between the
sepcified limits is reached in uplink direction by a MS in the cell.
The following <direction> satisfaction rate counters:
<direction>Tbf<ServiceClass>SatisfactLess50pCent
<direction>Tbf<ServiceClass>SatisfactBet5090pCent
<direction>Tbf<ServiceClass>SatisfactMore90pCent
provide altogether a <direction> satisfaction rate histogram for the <ServiceClass>
in the related cell.
Each one represent the cumulative number of times a satisfaction rate between the
specified limits is reached in <direction> by a <ServiceClass> MS in the cell.
Note: With the introduction of ”Extended Uplink TBF”, an uplink TBF is
composed of active and inactive period.
The following throughput counters are incremented only during active
periods: upPipeLess11kbps, upPipeGreater11kbps, upPipeGreater22kbps.
The following satisfaction rate counters are incremented only during active
periods: upTbfGold/ Silver/ BronzeSatisfactLess50/ Bet5090/
More90pCent

The throughput counters and the satisfaction rate counters are computed as follow.
For each pipe (set of radio resources allocated to a MS), the following counters are
defined :
dnNbDataBytes: cumulative number of bytes in downlink RLC data block
received on the pipe
dnVerboseTime: cumulative time the PCU is ready to transmit downlink RLC
data blocks on the pipe (this excludes for instance MS reaction times after a
resource assignment, keep alive duration, ...)
upNbDataBytes: cumulative number of bytes in uplink RLC data blocks
transmitted on the pipe
upVerboseTime: cumulative time the PCU is ready to receive uplink RLC data
blocks on the pipe (this excludes for instance MS reaction times after a resource
assignment)
On pipe closure (and if <direction>VerboseTime is not null), for both directions the
following actions are done:
Compute the throughput as follow:
• <direction>Throughput=<direction>NbDataByte <direction>VerboseTime
· Increments the right <direction> throughput counter corresponding to the limits
including the <direction>Throughput value
· Compute the satisfaction rate as follow:
• <direction>SatisfactionRate=<direction>Throughput/<direction>PeakThro
ughput
· Increments the right <direction> satisfaction rate counter corresponding to the
limits including the <direction>SatisfactionRate value
A pipe closure occurs in the following cases:
at a normal or abnormal release of a half duplex transfer
at an abonormal release of a full duplex transfer
at transitions from half to full duplex transfer, in this case a new pipe is created
at allocation of new resources (after a TS pre--emption for instance), in this case a
new pipe is created
Note that the pipe is not necessary closed at transitions from full to half duplex
transfer.

411--9001--125
4.7.4.1 Example of how Throughput Monitoring Counters work

To facilitate understanding of this type of counter, the following is an example of
how this counter works.
Configuration
MS Side:
Mobile 3+1 with the following traffic profile parameters:
Delay Class: class 1
Reliability Class: Unacknowledged GTP and LLC; acknowledged RLC,
protected data
Peak Throughput: Up to 2,000 octets
Precedence Class: High Priority
Mean Throughput: 500 octet/h
Radio Priority: priority level 4
Network Side:
1 Cell with at least 4 configured Pdtch for the mobile originated ping.
1 Cell with 2 configured Pdtch for the network originated ping
Mobile Originated Ping
Test Method:
Mobile is in stand--by mode.
Perform one ping from the client (size 100 octets).
Test Results:
Mobile establishes an uplink TBF with the parameters negotioated with the SGSN
(UL traffic profile), the ping request is transmitted over the Gb interface.
Before the ping response, downlink TBF is established (Downlink
Pre--establishment) with the default traffic profile parameters (Radio Priority 2,
peak bit = 0 best effort).
Finally the ping response is transmitted through the downlink TBF previously
established and both TBF end.
Counter Incrementations:
UpPipeGreater11kbps +1
DnPipeGreater33kbps +1
Note: If the UL traffic profile parameters used for the establishment of the uplink
TBF are different from the PCU default traffic profile parameters used for
Downlink Pre--establishment, the incrementations are as follows:
• UpPipeGreater11kbps +2 (instead of upPipeGreater11kbps +1)

Network Originated Ping
Test Method:
Mobile is in stand--by mode.

Perform one ping from the network to the client (size = 100 octets).
Test Results:
SGSN sends a Paging Command which is broadcast over the whole routing area.
It triggers an uplink TBF establishment from the mobile with the signalling profile
parameters (UL signaling profile). The mobile is then located thanks to the empty
LLC frame transmitted to the SGSN.
PCU establishes a downlink TBF that will allow to transmit the ping request to the
client: the profile parameters received from SGSN (DL traffic profile) are then used.
Once the ping request has been received by the client, an uplink TBF is established
to transmit the ping response: the profile parameters received from the MS (UL
traffic profile) are used. Finally both TBF end.
Note: The traffic profile used to establish the downlink TBF depends on the
SGSN implementation.
Counter Incrementations:
1st Case: DL traffic profile ¸ UL traffic profile and DL traffic profile ¸ UL
signaling profile:
• UpPipeGreater11kbps +3
• dnPipeBetween22and33kbps +2
2nd Case: DL traffic profile = UL traffic profile and DL traffic profile ¸ UL
signaling profile:
3rd Case: DL traffic profile ¸ UL traffic profile and DL traffic profile = UL
signaling profile:

411--9001--125
Nortel Confidential Counter description 5--1
5 COUNTER DESCRIPTION
5.1 Dictionary presentation
5.1.1 Dictionary contents

The Dictionary of counters describes each of the observation counters contained in
permanent (BSS, md, and manager) and temporary observation reports.
It includes the synthetic counters defined by the network operator in agreement with
the manufacturer, which supplement the counters displayed in permanent bsc
observation reports.
The first paragraph presents the observation counters and defines the main terms
used in the Dictionary of counters.
The following paragraphs of the Dictionary describes the counters on a per
type/family basis, and in ascending numerical order:
type = raw or synthetic
family = permanent BSS, temporary, permanent md, or permanent manager
The last paragraph presents the counter differences between the BSS releases
handled by the V15 OMC--R.
5.1.2 Observation counter references
5.1.2.1 Counter numbering

On the OMC--R, each observation counter is referenced by a number that
unambiguously identifies it in the type/family to which it belongs:
• 1nxx . . . . . . . . . . . . . raw permanent BSS counter
• 2nxx . . . . . . . . . . . . . raw permanent BSS counter
• 3nxx . . . . . . . . . . . . . raw permanent BSS counter (BSC 3000)
• 8nxx . . . . . . . . . . . . . synthetic permanent BSS counter
• 99xx, 100xx . . . . . . . raw permanent md counter
• 150xx . . . . . . . . . . . . raw permanent PCUSN counter up to V14
• 151xx . . . . . . . . . . . . raw permanent PCUSN counter for V15.0
Reminder
By definition, a raw counter contains raw measurements taken by the observed
entity whereas a synthetic counter contains the processed results calculated by the
OMC--R from raw measurements.
BSS temporary, permanent md, and permanent manager observations only use raw
counters.

5--2 Counter description Nortel Confidential
5.1.3 Counter definition
The following fields describe each counter: Number, Title, Name Q3, Feature,
Object, Function, Formula (synthetic counter), Event (raw counter), Type, Class
(raw permanent bsc counters), Source, Precise incrementation conditions,
Exception conditions, Dataflows.
Note: These fields contain the following information:
Number: counter number = nnxx or nnxx/c. It is unique on the OMC--R and is

the absolute counter definition.
The suffix “/c” identifies the associated cause number when the counter is
identified by cause.
Title: counter name. It explains the counter in plain language and summarizes its
exact function.
A counter whose name begins with Number tallies a number of events in a
defined observation period, a counter whose name begins with Rate displays a
percentage, a counter whose name begins with Ratio does not contain unit
values.
Name Q3: name of the counter mediated on the NMC/MD--R interface
Feature: new field introduced since V12, to give the name of the feature that
requested the creation of the counter
Object: geographic counter coverage. A counter occurrence is defined by the
related object occurrence:
• BSS counter: adjacentCellHandOver, bsc, bts, btsSiteManager, channel,
pcmCircuit, signallingLink, transceiverZone, omu, tmu
• MD counter: active OMC--R agent server
• OMC counter: active OMC--R manager and connected workstation servers
Function: functional description of the counter
Formula: mathematical formula used to calculate synthetic permanent bsc
counters according to the elementary counters they contain.
The counter titles and numbers included in the calculation are indicated:
• sum_cell = total of all BSS cells
• max_cell = calculated maximum in BSS cells
• min_cell = calculated minimum in BSS cells
Event: event affecting the counter value(s)

411--9001--125
Type: type of the counter (raw/synthetic) and type of the observation

(permanent/temporary):
• raw: counter reading collected by a BTS, a BSC, or the OMC--R agent, and
forwarded to the OMC--R manager, or counter reading directly processed by
the OMC--R manager. The only possible calculations are the averages of same
counter occurrence values.
• synthetic: counter processed by the OMC--R manager using several
occurrences of the same counter or several BSS (raw or synthetic) counters.
• permanent: observation counter displayed in response to a permanent
observation report request.
• temporary: observation counter displayed in response to a temporary
observation request.
Class: class of a permanent BSS observation counter. The following classes are
defined:
• A interface
• Abis interface
• ASCI (GSM--R functions)
• assignment (of dedicated channels)
• BSC equipment
• BSS/OMC--R link
• GPRS
• GPRS / EDGE Suspend and Resume
• handover
• interference
• L1M (Layer 1 Management)
• monitoring (of common control channels)
• PCM link
• release (of resources)
• setup (of calls)
• sms (SMS--CB service)

Source: responsible subsystem. There are four possible origins:

• detected by the BTS, recorded by the BSC: The event responsible for
increasing the counter value is detected by the BTS and the information is
forwarded to the BSC as a message on the Abis interface. The BSC
dynamically manages the list of counter occurrences received on the interface
during the observation period.
In case of an Abis interface break (by locking or defective equipment (Abis
PCM, site, cell)), no message is forwarded to the BSC and no counter value is
collected. If the interface break covers the entire observation period, the
counters are empty in the CCCH array in permanent bsc observation reports.
• recorded by the BSC: The events that modify the counter values are detected
by the BSC. The BSC manages the counter and the OMC--R stores it.
• calculated by the OMC: (permanent bsc and instrument panel observations):
The OMC--R calculates the counter value from one or more raw counters
received from the BSC in response to a report request. The OMC--R does not
store the counter.
• calculated by the OMC--R agent (permanent md observation): The events that
modify the counter value are detected by the OMC--R agent. The OMC--R
manages and stores the counter.
• calculated by the OMC--R manager (permanent manager observation): The
events that modify the counter value are detected by the OMC--R manager or a
connected workstation. The OMC--R manages and stores the counter.
Precise incrementation conditions: new field introduced since V12, to explain
when and why the counter is triggered
Exception conditions: new field introduced since V12, to explain when and why
the counter is NOT triggered
Dataflows: new field introduced since V12, to show graphically when the
counter is triggered
Note: optional field containing comments
5.1.4 Basic definitions

The following definitions apply to the terms used in the Dictionary of Counters.
5.1.4.1 Resources
Allocation
Resource allocation is a purely software function that consists of reserving a

resource for future use and must not be confused with ACTIVATION which is a
process involving a physical action (radio transmission, data transfer).

411--9001--125
Message sequencing situates resource allocation in time:

an SDCCH is allocated on receipt of the Abis CHANNEL REQUIRED message
and before sending the Abis CHANNEL ACTIVATE message.
a TCH is allocated before sending the Abis CHANNEL ACTIVATE message in
ASSIGNMENT, INTERNAL, and EXTERNAL HANDOVER procedures.
a CIC is allocated immediately before the TCH, that is before the Abis
CHANNEL ACTIVATE message is sent in ASSIGNMENT and incoming
EXTERNAL HANDOVER procedures.
Deallocation
Resource deallocation is a purely software function that consists of releasing a

resource after use and must not be confused with DEACTIVATION which is a
process involving a physical action.
Message sequencing situates resource de--allocation in time:
an SDCCH is deallocated on receipt of the Abis RF CHAN RELEASE ACK
message or when the “Trfack” timer expires.
a TCH is deallocated on receipt of the Abis RF CHAN RELEASE ACK message
or when the “Trfack” timer expires.
a CIC is deallocated immediately after the TCH, that is on receipt of the Abis RF
CHAN RELEASE ACK message or when the “Trfack” timer expires.
5.1.4.2 SCCP connections
SCCP connection setup
An SCCP connection is set up on the following:

on BSC request, on receipt of a CONNECTION CONFIRM message on the A
interface
on MSC request, by sending a CONNECTION CONFIRM message on the A
interface
SCCP connection refusal
An SCCP connection is refused on receipt of a CONNECTION REFUSED message

from the SCCP layer.
SCCP connection break or release
An SCCP connection is released on the following:

on BSC request, on receipt of a RELEASE ACK message
on MSC request, by sending a RELEASE ACK message

5.1.4.3 Handover
Handover required
The handover decision algorithm sends an internal message containing an ordered

list of potential cells able to satisfy handover needs. Several requests may be sent
for the same handover.
Handover requests
A handover request is a purely software process which consists of examining the

cells able to satisfy handover needs.
Executed handover
A handover is executed after the HANDOVER COMMAND message is sent on the

Abis interface.
Successful handover
A handover is successful if the HANDOVER COMPLETE message is received on

the Abis interface.

411--9001--125
5.2 Raw permanent BSS counters (BSC 12000HC) (from 1084

to 1835)
l
1084/0 Number of LAPD Level 1 errors: Erroneous frame received
Name Q3 : abisLevel1ErrorsBadFrame<xx>
Object : bsc
Location :
Name Q3 Location
abisLevel1ErrorsBadFrame<xx> LAPD--<xx>
Function : number of “errored frame” errors detected by Level 1
Event : number of incorrect frames received
Type : raw permanent
Class : Abis interface
Source : recorded by the BSC
Precise
incrementation conditions :
When GPRS is activated, this counter is concerned by the following
calls:
CCT: Circuit calls on TCH channel
CCP: Circuit Calls on PDTCH preempted to make a TCH channel
CP: Com packet on PDTCH channel
l
1084/3 Number of LAPD Level 1 errors: CRC error
Name Q3 : abisLevel1ErrorsCrcError<xx>
Object : bsc
Location :
Name Q3 Location
abisLevel1ErrorsCrcError<xx> LAPD--<xx>
Function : number of “CRC error” errors detected by Level 1
Event : receipt of an indication that the frame is received with a wrong CRC

Precise
calls:
l
1084/4 Number of LAPD Level 1 errors: Loss of alignment
Name Q3 : abisLevel1ErrorsLostAlign<xx>
Object : bsc
Location :
Name Q3 Location
abisLevel1ErrorsLostAlign<xx> LAPD--<xx>
Function : number of “loss of frame alignment” errors detected by Level 1
Event : receipt of an indication that the alignment is lost
Precise
calls:
l
1086 Number of GPRS RACHs rejected due to SICD<x> board
overload
Name Q3 : gprsRachRejectedSicd<x>.....for x = 0 to 9
Object : bsc
Location :
Name Q3 Location
gprsRachRejectedSicd<x> SICD--<x>
Function : Number of GPRS RACHs rejected due to SICD<x> board overload

411--9001--125
Event : rejection of a GPRS RACH message

Class : equipment
Feature : GPRS (SV407 - V12)
Precise
When GPRS is activated, this counter is concerned by CP calls only
(Com packet on PDTCH channel)
It is not concerned by CCT (Circuit calls on TCH channel) or CCP
(Circuit Calls on PDTCH preempted to make a TCH channel).
l
1087 Number of GPRS IMMEDIATE ASSIGNMENT messages
rejected due to SICD<x> board overload
Name Q3 : gprsImmAssRejectedSicd<x>.....for x = 0 to 9
Object : bsc
Location :
Name Q3 Location
gprsImmAssRejectedSicd<x> SICD--<x>
Function : Number of GPRS IMMEDIATE ASSIGNMENT messages rejected

due to SICD<x> board overload
Event : rejection of a GPRS IMMEDIATE ASSIGNMENT message
Class : equipment
Precise

l
1088 Number of GPRS PAGING messages rejected due to SICD<x>
board overload
Name Q3 : gprsPagingRejectedSicd<x>.....for x = 0 to 9
Object : bsc
Location :
Name Q3 Location
gprsPagingRejectedSicd<x> SICD--<x>
Function : Number of GPRS PAGING messages rejected due to SICD<x> board

overload
Event : rejection of a GPRS PAGING message
Class : equipment
Precise
l
1114 Average time of PCM unavailability
Name Q3 : pcmUnavailabilityMoy . . Average PCM unavailability time
pcmUnavailabilityMax . . Max PCM unavailability time
pcmUnavailabilityCum . . Total PCM unavailability time
pcmUnavailabilityEch . . . Number of samples
Object : pcmCircuit
Function : average (= total time divided by number of samples) and maximum
time of BSS external PCM unavailability in the observation period,
expressed in milliseconds
Event : PCM operational state changes (operationalState attribute):
leave “enabled” state: set timer

411--9001--125
change to “enabled” state:

• stop and read timer
• store its peak value
• add the value read to the previous total time of unavailability in
the observation period
• step up by one the number of samples
Class : PCM link
Precise
calls:
l
1115 Number of link changeovers
Name Q3 : omcLinkSwitchOver
Object : bsc
Function : number of BSS/OMC--R link switchovers
Event : loss of Level 2 on the BSS/OMC--R link
Class : BSS/OMC--R link
Precise
calls:

l
1121 Number of passive chain update messages
Name Q3 : chainStandByUpdate
Object : bsc
Function : number of messages sent from the active to the BSC passive chain
Event : transmission of a message to the BSC passive chain
Class : BSC equipment
Precise
calls:
l
1122 Number of passive chain response messages
Name Q3 : chainStandByResponse
Object : bsc
Function : number of response messages sent from the passive to the BSC active
chain
Event : reception of a response message from the BSC passive chain
Precise
calls:

411--9001--125
l
1300 Number of I frames sent
Name Q3 : omcOutputIFrame
Object : bsc
Function : number of I (Information) frames sent by the BSC (local X.25
Level 2) to the OMC--R agent (remote X.25 Level 2)
Event : transmission of an I frame on the X.25 link by the BSC
Precise
calls:
No distinction is made between RACH dedicated to Circuit Call or
Packet Calls.
Note : V12 counter
l
1301 Number of I frames received
Name Q3 : omcInputIFrame
Object : bsc
Function : number of I (Information) frames received by the BSC (local X.25
Level 2)
Event : receipt of an I frame on the X.25 link by the BSC

Precise
calls:
Packet Calls.
l
1302 Number of repeated I frames sent
Name Q3 : omcOutputRepeatedIFrame
Object : bsc
Function : number of repeated I (Information) frames sent by the BSC (local
X.25 Level 2) to the OMC--R agent (remote X.25 Level 2)
Event : transmission of a repeated I frame on the X.25 link by the BSC
Precise
calls:
Packet Calls.
l
1303 Number of repeated I frames received
Name Q3 : omcInputRepeatedIFrame
Object : bsc
Function : number of repeated I (Information) frames received by the BSC (local
X.25 Level 2)
Event : receipt of a repeated I frame on the X.25 link by the BSC

411--9001--125
Precise
calls:
Packet Calls.
l
1304 Number of RNR frames sent
Name Q3 : omcOutputRnrFrame
Object : bsc
Function : number of RNR (Received Non Ready) frames sent by the BSC (local
X.25 Level 2) to the OMC--R agent (remote X.25 Level 2)
Event : transmission of a RNR frame on the X.25 link by the BSC
Precise
calls:
Packet Calls.
l
1305 Number of RNR frames received
Name Q3 : omcInputRnrFrame
Object : bsc
Function : number of RNR (Received Non Ready) frames received by the BSC
(local X.25 Level 2)
Event : receipt of a RNR frame on the X.25 link by the BSC

Precise
calls:
Packet Calls.
l
1400 Average load of CPUM board
Name Q3 : prLoadCpumMoy
prLoadCpumMax . . . . . . . . . . . . . . Maximum load of the CPUM
board
prLoadCpumCum . . . . . . . . . . . . . Total load of the CPUM board
prLoadCpumEch . . . . . . . . . . . . . . Number of samples
Object : bsc
Location :
Name Q3 Location
prLoadCpumMoy/Max/Cum/Ech CPUM--0
Function : average load (= total load / number of samples) expressed in percent

and maximum load of the CPUM processor in the BSC for the
observation period
Event : detection of the CPUM processor activity:
activation of the “NULL” task: start timer
activation of another task:
• add it to the total number for the observation period
Class : equipment

411--9001--125
Precise
calls:
This counter gives the real load of the processor. And the load of a
BSC processor is impacted by GPRS messages treated by this
processor.
l
1400 Average load of CPUE x board
Name Q3 : prLoadCpueMoy
prLoadCpue1Moy
prLoadCpue2Moy
prLoadCpueMax . . . . . . . . Maximum load of the CPUE 0 board
prLoadCpue1Max . . . . . . . Maximum load of the CPUE 1 board
prLoadCpue2Max . . . . . . . Maximum load of the CPUE 2 board
prLoadCpueCum . . . . . . . . Total load of the CPUE 0 board
prLoadCpue1Cum . . . . . . . Total load of the CPUE 1 board
prLoadCpue2Cum . . . . . . . Total load of the CPUE 2 board
prLoadCpueEch . . . . . . . . . Number of samples
prLoadCpue1Ech . . . . . . . . Number of samples
prLoadCpue2Ech . . . . . . . . Number of samples
Object : bsc
Location :
Name Q3 Location
prLoadCpueMoy/Max/Cum/Ech CPUE--0
prLoadCpue1Moy/Max/Cum/Ech CPUE--1
prLoadCpue2Moy/Max/Cum/Ech CPUE--2

and maximum load of the CPUE x processor in the BSC for the
observation period

Event : detection of the CPUE x processor activity:

Class : equipment
Precise
calls:
processor.
l
1400 Average load of SICD<x> board
Name Q3 : prLoadSicd<x>Moy
prLoadSicd<x>Max . . . . . . . . . . . . Maximum load of the SICD<x>
board
prLoadSicd<x>Cum . . . . . . . . . . . Total load of the SICD<x>
board
prLoadSicd<x>Ech . . . . . . . . . . . . Number of samples
Object : bsc
Location :
Name Q3 Location
prLoadSicd<x>Moy/Max/Cum/Ech SICD--<x>

and maximum load of the SICD<x> processor in the BSC for the
observation period

411--9001--125
Event : detection of the SICD<x> processor activity:

Class : equipment
Precise
calls:
processor.
1755/0 Number of faults relating to the PCM with cause external PCM
fault
Name Q3 : pcmFaultExternal
Object : pcmCircuit
Function : number of faults relating to PCM
Event : external PCM fault
Class : PCM link

l
1755/1 Number of faults relating to the PCM with cause internal fault
Name Q3 : pcmFaultInternal
Object : pcmCircuit
Event : internal PCM fault
Class : PCM link
l
1755/2 Number of faults relating to the PCM with cause DDTI/SLTI
board fault
Name Q3 : pcmFaultDDTIBoard
Object : pcmCircuit
Event : DDTI/SLTI board fault
Class : PCM link
l
1755/3 Number of faults relating to the PCM with cause taken out of
service for an O&M reason
Name Q3 : pcmFaultOutOfService
Object : pcmCircuit
Event : taken out of service for an O&M reason
Class : PCM link

411--9001--125
l
1803/0 Number of rejected calls on paging requests due to overload
Name Q3 : cgOverloadRejectedOpPageReqCg0
cgOverloadRejectedOpPageReqCg1
cgOverloadRejectedOpPageReqCg2
Object : bsc
Location :
Q3 Name Location
cgOverloadRejectedOpPageReqCg0 CPUE--0
Function : Number of rejected calls on paging requests due to overload

Event : receipt of a paging request message when at least one board
concerning the paging request is in overload situation
Class : equipment
Precise
calls:
But it is not concerned by CP calls (Com packet on PDTCH channel).
Feature : Overload defense mechanism based on real load (FM877-- V12)
Note : cgOverloadRejectedOpPageReqCg2 is not significant since the
overload on paging requests is only measured on BIFP boards (cpue0
and cpue1).

l
1803/1 Number of rejected calls on channel requests due to overload
Name Q3 : cgOverloadRejectedOpChannelReqCg0
cgOverloadRejectedOpChannelReqCg1
cgOverloadRejectedOpChannelReqCg2
Object : bsc
Location :
Q3 Name Location
cgOverloadRejectedOpChannelReqCg0 CPUE--0
Function : Number of rejected calls on channel requests due to overload

Event : receipt of a channel request message when at least one board
concerning the channel request is in overload situation
Class : equipment
Precise
calls:
Note : cgOverloadRejectedOpChannelReqcg2 is not significant since the
overload on channel requests is only measured on BIFP boards (cpue0
and cpue1).

411--9001--125
l
1803/2 Number of rejected calls on establish indication due to overload
Name Q3 : cgOverloadRejectedOpEstablishIndCg0
cgOverloadRejectedOpEstablishIndCg1
cgOverloadRejectedOpEstablishIndCg2
Object : bsc
Location :
Q3 Name Location
cgOverloadRejectedOpEstablishIndCg0 CPUE--0
Function : Number of rejected calls on establish indication due to overload

Event : receipt of a n establish indication message when at least one board
concerning the establish indication is in overload situation
Class : equipment
Precise
calls:
Note : cgOverloadRejectedOpEstablishIndCg2 is not significant since
the overload on establish indication is only measured on BIFP boards
(cpue0 and cpue1).

3
1803/3 Number of rejected calls on handover requests due to overload
Name Q3 : cgOverloadRejectedOpHoReqCg0
cgOverloadRejectedOpHoReqCg1
cgOverloadRejectedOpHoReqCg2
Object : bsc
Location :
Q3 Name Location
cgOverloadRejectedOpHoReqCg0 CPUE--0
Function : Number of rejected calls on handover request due to overload

Event : receipt of an handover request message when at least one board
concerning the handover request is in overload situation
Class : equipment
Precise
calls:
Object : cgOverloadRejectedOpHoReqCg2 is not significant since the
overload on handover requests is only measured on BIFP boards
(cpue0 and cpue1).

411--9001--125
3
1803/4 Number of rejections on paging requests due to an
overloaded cell
Name Q3 : cgOverloadRejectedOpPageReqBtsCg0
cgOverloadRejectedOpPageReqBtsCg1
cgOverloadRejectedOpPageReqBtsCg2
Object : bsc
Location :
Q3 Name Location
cgOverloadRejectedOpPageReqBtsCg0 CPUE--0
Function : Number of rejections on paging requests due to overloaded cell

Event : receipt of a paging request rejection caused by an overloaded cell
when at least one board concerning the paging request is in overload
situation
Class : equipment
Precise
calls:
CCP: Circuit Calls on PDTCH preempted to make a TCH channel,
but it is not concerned by CP calls (Com packet on PDTCH channel).
Object : For a same originating paging request message, this counter will be
raised as many times as there are overloaded target cells.

3
1803/5 number of rejected sms--cb messages due to overload situation
Name Q3 : cgOverloadRejectedOpSmsCbCg0
cgOverloadRejectedOpSmsCbCg1
cgOverloadRejectedOpSmsCbCg2
Object : bsc
Location :
Q3 Name Location
cgOverloadRejectedOpSmsCbCg0 CPUE--0
Function : Number of rejected sms--cb messages due to overloaded cell

Event : receipt of a sms--cb message rejection caused by an overloaded cell
when at least one board concerning the sms--cb message is in overload
situation
Class : equipment
Precise
calls:
Feature : CR Q00590181
Note : V15.1R counter

411--9001--125
l
1834 Number of rejected calls on paging requests due to SICD<x>
board overload
Name Q3 : lapdOverloadRejectedOpSicd<x>.....for x = 0 to 9
Object : bsc
Location :
Name Q3 Location
lapdOverloadRejectedOpSicd<x> SICD--<x>
Function : Number of channel requests rejected due to SICD<x> board overload
Event : receipt of a channel request message
Class : equipment
Precise
calls:
In case of rejection, no distinction is made between CHANNEL
REQUESTS messages dedicated to Circuit Call or Packet Calls.
l
1835 Synthetic load on CPUM, CPUE<x>, SICD<y> board
Name Q3 : cardSynthLoadCpumMoy
cardSynthLoadCpumMax
cardSynthLoadCpumCum
cardSynthLoadCpumEch
cardSynthLoadCpue<x>Moy.....for x = 0 to 2
cardSynthLoadCpue<x>Max
cardSynthLoadCpue<x>Cum
cardSynthLoadCpue<x>Ech
cardSynthLoadSicd<y>Moy.....for y = 0 to 9
cardSynthLoadSicd<y>Max
cardSynthLoadSicd<y>Cum
cardSynthLoadSicd<y>Ech
Object : bsc

Location :
Name Q3 Location
cardSynthLoadCpumMoy/Max/Cum/Ech CPUM--0
cardSynthLoadCpue<x>Moy/Max/Cum/Ech CPUE--<x>
cardSynthLoadSicd<y>Moy/Max/Cum/Ech SICD--<y>
Function : synthetic load on CPUM, CPUE[x], SICD[y] board expressed in %

Use MdWarning to generate an alarm showing when a CPUE board
capacity reaches 40% and clears itself when it falls below 35%. Use
the following criteria:
DetectionFunction = outOfRangeCounter
monitoredObjectClass = bsc
monitoredObjectInstance = [bsc no.]
alarmPriority = critical
startAlarmThreshold = 40
endAlarmThreshold = 35
counterId = CardSynthLoadCpue0Moy
To know more about MdWarning usage, refer to NTP 128 section 4.4.
Event : the synthetic load is generated every second
Class : equipment
Precise
calls:
Note: This counter is only read when the SICD board is in service.

411--9001--125
5.3 Raw permanent BSS counters (BSC 3000, AMR)
5.3.1 Raw permanent BSS counters (BSC 3000) (from 1065/1 to 3008/3)
l
1065/1 Number of outgoing intra BSS handover execution attempts
from the cell for directed retry reason
Name Q3 : hoExecutionOutgoingIntraBssForDirectedRetry
Object : bts
Function : Number of outgoing intra BSS handover execution attempts from the
cell for directed retry reason
Event : Transmission of HANDOVER_COMMAND message (ABIS
message)
Class : handover
Precise
calls:
Data flows : Refer to Chapter 2
DFD “inter--cell intra BSC handover procedure (normal
completion with communication on TRAFFIC phase)”
DFD “Intra cell handover procedure (normal completion with
communication on TRAFFIC phase)”
DFD “Inter BSS intra MSC handover procedure (normal

l
1066/1 Number of outgoing inter BSS handover execution attempts from
the cell for directed retry reason
Name Q3 : hoExecutionOutgoingInterBssForDirectedRetry
Object : bts
Function : Number of outgoing inter BSS handover execution attempts from the
cell for directed retry reason
Event : Receipt of HANDOVER_COMMAND message from the MSC
Class : handover
Precise
calls:
l
1067/1 Number of successful outgoing intra BSS handover from the cell
for directed retry reason
Name Q3 : hoSuccessOutgoingIntraBssForDirectedRetry
Object : bts
Function : Number of successful outgoing intra BSS handover from the cell for
directed retry reason
Event : Receipt of HANDOVER_COMPLETE message from the mobile
Class : handover

411--9001--125
Precise
calls:
l
1068/1 Number of successful outgoing inter BSS handover from the cell
for directed retry reason
Name Q3 : hoSuccessOutgoingInterBssForDirectedRetry
Object : bts
Function : Number of successful outgoing inter BSS handover from the cell for
directed retry reason
Event : Receipt of CLEAR_COMMAND message from the MSC with the
handover cause set to “handover successful”
Class : handover
Precise
calls:
Note : For the number of successful outgoing inter handovers on TCH after
first attempt see counter 1078.

l
1164/33 Number of releases while the communication is in “traffic” phase.
Name Q3 : trafficReleaseTbcEdge
Object : bts
Function : number of releases while the communication is in “traffic” phase
Event : TDMA removal due to a EDGE TRX/TDMA optimization
Class : release
Precise
calls:
l
1206/1 Number of handovers or assignments in which the initial request
in EFR speech algorithm is degraded into FR speech algorithm
for AMR calls
Name Q3 : amrFrSpeechAlgoFallBack
Object : bsc
Function : Number of handovers or assignments in which the initial request in
EFR speech algorithm is degraded into FR speech algorithm for AMR
calls
Event : This counter is incremented on the reception of an
ASSIGN_REQUEST or an HANDOVER_REQUEST with a CIC
incompatible with the speech coding algorithm. In the case where the
BSC has got CIC bearing EFR and other CIC not bearing EFR and if
all CIC bearing EFR are already allocated
Class : assignment
Note : V14 counter

411--9001--125
l
1507/0 Number of rejected paging requests due to overload situation
Name Q3 : e3OverloadRejectedOpPagingReq
Object : bsc
Function : number of rejected paging requests due to overload situation (this
counter is incremented if the local card is overloaded or the operation
family named paging request is overloaded)
Event : receipt of a paging request when at least one card concerning this
operation is in an overload situation
Precise
CS--Paging and PS--Paging messages dropped in case of overload are
counted by this counter.
Class : equipment
Note : V14 counter
l
1507/1 Number of rejected channel requests due to overload situation
Name Q3 : e3OverloadRejectedOpChannelReq
Object : bsc
Function : number of rejected channel requests due to overload situation
Event : receipt of a channel request when at least one card concerning this
operation is in an overload situation
Class : equipment
Note : V14 counter
l
1507/2 Number of rejected establish indication messages due to overload
situation
Name Q3 : e3OverloadRejectedOpEstablishInd
Object : bsc
Function : number of rejected establish indication messages due to overload
situation

Event : receipt of an establish indication message when at least one card

concerning this operation is in an overload situation
Class : equipment
Note : V14 counter
l
1507/3 Number of rejected handover requests due to overload situation
Name Q3 : e3OverloadRejectedOpHoReq
Object : bsc
Function : number of rejected handover requests due to overload situation
Event : receipt of a handover request when at least one card concerning this
operation is in an overload situation (receipt of a handover indication
message or attempt of outgoing internal or external handovers,
incoming external handover request, local directed retry)
Class : equipment
Note : V14 counter
l
1507/4 Number of rejected paging request rejections caused by an
overloaded cell
Name Q3 : e3OverloadRejectedOpPagingReqReject
Object : bsc
Function : number of rejected paging request rejections caused by an overloaded
cell
Event : receipt of a paging request rejection caused by an overloaded cell
when at least one card concerning this operation is in an overload
situation (for the same originating paging request message, this
counter will be increased each time the target cell is overloaded)

411--9001--125
Precise
CS--Paging and PS--Paging messages dropped in case of overload are
counted by this counter.
Class : equipment
Note : V14 counter
l
1507/5 number of rejected sms--cb messages due to overload situation.
Name Q3 : e3OverloadRejectedOpSmsCb
Object : bsc
Function : number of rejected sms--cb message caused by an overloaded cell
Event : receipt of a sms--cb message rejection caused by an overloaded cell
when at least one card concerning this operation is in an overload
situation (for the same originating sms--cb message, this counter will
be increased each time the target cell is overloaded)
Class : equipment
l
1508/0 number of paging requests filtered by the BSC 3000
Name Q3 : pagingFilteredByBsc
Object : bsc
Function : Number of paging requests filtered by the A interface filter in the BSC
3000 independently of the overload condition (which lead to peg the
1506 and 1507 counters). Only paging for Circuit Service are
concerned.
Event : paging request message is filtered by the A interface filter in the BSC
Feature : 29479 Paging capacity increase - UI mode-- BSC 3000

l
1610/1 Number of half rate TCH allocations
Name Q3 : tchHrAllocatedWps
tchHrAllocatedWpsTrZone
Object : bts/transceiverZone
Function : Cumulative number of half rate TCH allocations.
Event : Allocation of a half rate TCH (including PDTCH) for a WPS call.
Feature : WPS BSS2G and 3000 public access bandwidth protection (22465)
l
1612/1 Average and maximum number of half rate Primo allocations
Name Q3 : tchHrAveragedUsedWpsTrZoneMoy
tchHrAveragedUsedWpsTrZoneMax
tchHrAveragedUsedWpsTrZoneEch
tchHrAveragedUsedWpsTrZoneCum
Function : Average and maximum number of WPS half rate TCH (including
PDTCH) allocations
Event : Allocation/de--allocation of a half rate TCH
Class : allocation
Feature : 3000 public access bandwidth protection (22465)
Precise
When GPRS is activated, this counter is concerned by CCT (Circuit
calls on TCH channel), but not by CCP (Circuit Calls on PDTCH
preempted to make a TCH channel). This is because this counter is
related to configured (static) TCH/FR channel. This counter is
pegged on the traffic channel allocation for a WPS call if the WPS
Management flag is enabled. This counter is pegged on the traffic
channel de--allocation for a call initiated as a WPS call.

411--9001--125
1780/1 Number of successful outgoing classic handovers from the cell

Name Q3 : amrFrHoSuccessOutgoingTch
Object : bts
Function : number of successful outgoing intra–bss or inter–bss handovers on
TCH using AMR full rate
Event : receipt of HANDOVER COMPLETE message from the MS
(intra–bss handover) or receipt of CLEAR COMMAND message
from the MSC with a handover cause “handover successful”
(inter–bss handover)
Class : handover

Name Q3 : amrHrHoSuccessOutgoingTch
Object : bts
TCH using AMR half rate
Class : handover


l
1816/0 Path balance for all the communications on TCH full rate
channel or preempted PDTCH on the BCCH TDMA
Name Q3 : pathBalanceCum
pathBalanceEch
pathBalanceMoy
pathBalanceMax
Object : bts
Function : Averaging value of the path balance for all the communications on
TCH full rate channel or preempted PDTCH on the BCCH TDMA
Event : Data are received by the BSC from the BTS in STOP
MEASUREMENT ACK messages. For each communication, the
BTS gives the number of measurements and the cumulated value.
Class : cell
Note : V14 counter
l
1817/0 Average, maximum, mimium, and total number of half rate
TCH allocations
Name Q3 : burstToTransmit
Object : bts
Function :
Event : allocation/de--allocation of a half rate TCH.
Class : setup

411--9001--125
l
2000/0 Number of PDTCH available and preempted for EDGE services
Name Q3 : totalNumberOfEdgeTsCum
totalNumberOfEdgeTsTrZoneCum
totalNumberOfEdgeTsEch
totalNumberOfEdgeTsTrZoneEch
totalNumberOfEdgeTsMax
totalNumberOfEdgeTsTrZoneMax
totalNumberOfEdgeTsMoy
totalNumberOfEdgeTsTrZoneMoy
Function : Maximum, average, and cumulative number of available PDTCH for
EDGE (all configured PDTCH not pre--empted for circuit calls and
available for EDGE)
Event : PDTCH configuration or preemption/release of the EDGE channel by
the BSC.
Type : LOAD
Feature : 19174 (EDGE dynamic Abis and Agprs backhaul)
Source : TBD
Note : V15 counter
l
Name Q3 : allocatedEdgeTsMoy
allocatedEdgeTsMax
allocatedEdgeTsCum
allocatedEdgeTsEch
allocatedEdgeTsTrZoneMoy
allocatedEdgeTsTrZoneMax
allocatedEdgeTsTrZoneCum
allocatedEdgeTsTrZoneEch
EDGE allocated to the PCU
the BSC.
Type : LOAD
Source : TBD
Note : V15 counter

l
Name Q3 : preemptedEdgeTsCum
preemptedEdgeTsTrZoneCum
preemptedEdgeTsMax
preemptedEdgeTsTrZoneMax
preemptedEdgeTsMoy
preemptedEdgeTsTrZoneMoy
preemptedEdgeTsEch
preemptedEdgeTsTrZoneEch
Function : Minimum, maximum, average, and cumulative number of available
PDTCH for EDGE services preempted by circuit calls
the BSC.
Type : LOAD
Source : TBD
Note : V15 counter
l
2001 Number of joker DS0 TS allocated on the Abis interface.
Name Q3 : allocatedAbisJokerTSEdgeCum
allocatedAbisJokerTSEdgeTrZoneCum
allocatedAbisJokerTSEdgeEch
allocatedAbisJokerTSEdgeTrZoneEch
allocatedAbisJokerTSEdgeMax
allocatedAbisJokerTSEdgeTrZoneMax
allocatedAbisJokerTSEdgeMoy
allocatedAbisJokerTSEdgeTrZoneMoy
allocatedAbisJokerTS
Function : Minimum, maximum, average, and cumulative number of joker DS0
TS allocated on the Abis interface
Event : Joker (dis) configuration at TDMA configuration (or removal).
Type : LOAD
Source : TBD
Note : V15 counter

411--9001--125
l
Name Q3 : totalNumberOfEdgeTsCellMoy
totalNumberOfEdgeTsCellMax
totalNumberOfEdgeTsCellCum
totalNumberOfEdgeTsCellEch
Object : bts
EDGE (all configured PDTCH not pre--empted for circuit calls and
available for EDGE)
the BSC.
Type : LOAD
Note : V15 counter
l
Name Q3 : allocatedEdgeTsCellMoy
allocatedEdgeTsCellMax
allocatedEdgeTsCellCum
allocatedEdgeTsCellEch
Object : bts
EDGE allocated to the PCU
the BSC.
Type : LOAD
Note : V15 counter

l
Name Q3 : preemptedEdgeTsCellMoy
preemptedEdgeTsCellMax
preemptedEdgeTsCellCum
preemptedEdgeTsCellEch
Object : bts
PDTCH for EDGE services preempted by circuit calls
the BSC.
Type : LOAD
Note : V15 counter
2003 Number of joker DS0 TS allocated on the Abis interface.

Name Q3 : allocatedAbisJokerTsCellMoy
allocatedAbisJokerTsCellMax
allocatedAbisJokerTsCellCum
allocatedAbisJokerTsCellEch
Object : bts
Function : Minimum, maximum, average, and cumulative number of joker DS0
TS allocated on the Abis interface
Event : Joker (dis) configuration at TDMA configuration (or removal).
Type : LOAD
Note : V15 counter

411--9001--125
2071/0 Number of PCU MS suspend procedures triggered by the BSC to

the PCU
Name Q3 : agprsSuspendRequestProcedures
Object : bsc
Function : Number of PCU MS suspend procedures triggered by the BSC to the
PCU.
Event : The BSC sends a PCU MS suspend request.
Class : GPRS/EDGE
Feature : 25155 GPRS / EDGE Suspend and Resume
Precise
The counter is increased even if the Suspend/Resume feature is
NOT activated.
In case of multiple messages relative to the same communication,
this counter is incremented only one time per communication.
GPRS / EDGE Suspend procedure with RAU message (nominal
procedure)
GPRS / EDGE Suspend procedure with RAU message (failure
case)
GPRS / EDGE Suspend procedure with Resume message (nominal
procedure)
GPRS / EDGE Suspend procedure with Resume message (failure
case)
Note : V15 counter
2071/1 Number of PCU MS suspend messages sent by the BSC to the

PCU
Name Q3 : agprsSuspendRequestMessages
Object : bsc
Function : Number of PCU MS suspend messages sent by the BSC to the PCU.
Event : The BSC sends a PCU MS suspend request.
Class : GPRS/EDGE


Precise
The counter is increased even if the Suspend/Resume feature is
NOT activated.
this counter is incremented every time the message is sent on the
Agprs.
procedure)
case)
procedure)
case)
Note : V15 counter
2072 Number of PCU MS suspend nack received by the BSC from the
PCU
Name Q3 : agprsSuspendNack
Object : bsc
Function : Number of PCU MS suspend nack received by the BSC from the
PCU.
Event : The BSC receives a suspend nack for a communication.
Class : GPRS/EDGE
Precise
the counter is incremented only one time per communication.
case)
Note : V15 counter

411--9001--125
2073 number of PCU MS resume messages sent by the BSC to the PCU
Name Q3 : agprsResumeRequest
Object : bsc
Function : Number of PCU MS resume messages sent by the BSC to the PCU.
Event : The BSC sends a resume message for a communication.
Class : GPRS/EDGE
procedure)
case)
Note : V15 counter
2074 Number of PCU MS resume nack received by the BSC from the
PCU
Name Q3 : agprsResumeNack
Object : bsc
Function : Number of PCU MS resume nack received by the BSC from the PCU.
Event : The BSC receives a resume nack for a communication.
Class : GPRS/EDGE
case)
Note : V15 counter

2096 number of successful TCH allocations (including preempted

PDTCH) to SAIC mobiles
Name Q3 : saicTchSuccessfullyAssigned
saicTchSuccessfullyAssignedTrZone
Function : Number of successful TCH allocations (including preempted
PDTCH) to SAIC mobiles.
Event : Allocation of a TCH or a preempted PDTCH to a SAIC mobile.
Class : TCH allocations
Source : recorded by BSC
Feature : 15347 Network Synchronisation
3000/0 load of a OMU processor inside the Control Node of the sys-
tem: SBC
Name Q3 : prLoadCne3OmuSbcMoy
prLoadCne3OmuSbcMax
prLoadCne3OmuSbcCum
prLoadCne3OmuSbcEch
Object : omu
Function : Load of a given OMU processor inside the Control Node of the system
Event : Core system internal counting
Precise
calls:
CCT: Circuit Calls on TCH channels
CP: Com Packets on PDTCH channel
Note : Each counter has a value between 0 and 100 (the value 100 represents
a 100% load).

411--9001--125
3001/0 Load of a given TMU processor inside the Control Node of the
system: SBC
Name Q3 : prLoadCne3TmuSbcMoy
prLoadCne3TmuSbcMax
prLoadCne3TmuSbcCum
prLoadCne3TmuSbcEch
Object : tmu
Function : Load of a given TMU processor inside the Control Node of the system
Precise
calls:
Note : V13.1 counter
Each counter has a value between 0 and 100 (the value 100 represents
a 100% load).
3001/2 Load of a given TMU processor inside the Control Node of the
system: PMC
Name Q3 : prLoadCne3TmuPmcMoy
prLoadCne3TmuPmcMax
prLoadCne3TmuPmcCum
prLoadCne3TmuPmcEch
Object : tmu
Function : Load of a given TMU processor inside the Control Node of the
system: PMC

Precise
calls:
This counter has a value between 0 and 100 (the value 100 represents
a 100% load).
The PMC may be an option. In this case it has no significant value and
the result will be a succession “***…***” at the OMC level.
If the BSC 3000 is equipped with TMU2 boards, the PMC screening
value of counter 3001/2 is not significant either (because the PMC is
a TMU1 board processor)
3004/0 Memory usage on OMU processor inside the Control Node of

the system: SBC_MEM
Name Q3 : e3PrMemCnOmuSbcMemMoy
e3PrMemCnOmuSbcMemMax
e3PrMemCnOmuSbcMemCum
e3PrMemCnOmuSbcMemEch
Object : omu
Function : Memory usage on OMU processor inside the Control Node of the
system: SBC_MEM (DRAM usage)
Precise
calls:
a 100% load).

411--9001--125
3004/1 Memory usage on OMU processor inside the Control Node of

the system: SBC_SWAP
Name Q3 : e3PrMemCnOmuSbcSwapMoy
e3PrMemCnOmuSbcSwapMax
e3PrMemCnOmuSbcSwapCum
e3PrMemCnOmuSbcSwapEch
Object : bsc
Function : Memory usage on OMU processor inside the Control Node of the
system: SBC_SWAP (disk usage for swap)
Precise
calls:
a 100% load).
3005/0 Memory usage on TMU processor inside the Control Node of

the system: SBC
Name Q3 : e3PrMemCnTmuSbcMoy
e3PrMemCnTmuSbcMax
e3PrMemCnTmuSbcCum
e3PrMemCnTmuSbcEch
Object : tmu
Function : Memory usage on TMU processor inside the Control Node of the
system: SBC

Precise
calls:
a 100% load).
3005/2 Memory usage on TMU processor inside the Control Node of

the system: PMC
Name Q3 : e3PrMemCnTmuPmcMoy
e3PrMemCnTmuPmcMax
e3PrMemCnTmuPmcCum
e3PrMemCnTmuPmcEch
Object : tmu
Function : Memory usage on TMU processor inside the Control Node of the
system: SBC
Precise
calls:
a 100% load).
The PMC may be an option. In this case it has no significant value and
the result will be a succession “***…***” at the OMC level.
If the BSC 3000 is equipped with TMU2 boards, the PMC screening
value of counter 3005/2 is not significant either (because the PMC is
a TMU1 board processor)

411--9001--125
3008/0 Disk usage on OMU processor inside the Control Node of the
system: local disk access for write operation
Name Q3 : e3PrDiskCnOmuLdWMoy
e3PrDiskCnOmuLdWMax
e3PrDiskCnOmuLdWCum
e3PrDiskCnOmuLdWEch
Object : omu
Function : Disk usage on OMU processor inside the Control Node of the system:
disk access on local disk for write operation (Kbyte/s)
Precise
calls:
system: local disk access for read operation
Name Q3 : e3PrDiskCnOmuLdRMoy
e3PrDiskCnOmuLdRMax
e3PrDiskCnOmuLdRCum
e3PrDiskCnOmuLdREch
Object : omu
disk access on local disk for read operation (Kbyte/s)

Precise
calls:
system: mirror disk access for write operation
Name Q3 : e3PrDiskCnOmuMdWMoy
e3PrDiskCnOmuMdWMax
e3PrDiskCnOmuMdWCum
e3PrDiskCnOmuMdWEch
Object : omu
disk access on mirror disk for write operation (Kbyte/s)
Precise
calls:

411--9001--125
system: mirror disk access for read operation
Name Q3 : e3PrDiskCnOmuMdRMoy
e3PrDiskCnOmuMdRMax
e3PrDiskCnOmuMdRCum
e3PrDiskCnOmuMdREch
Object : omu
disk access on mirror disk for read operation (Kbyte/s)
Precise
calls:

5.3.2 Raw permanent BSS counters (AMR) (from 1197/2 to 1988/0)

l
1197/2 Number of channels activated for speech: AMR Half Rate
Algorithm
Name Q3 : channelActivateSpeechAmrHr
Object : bts
Function : number of speech channels using the AMR Half-Rate algorithm,
activated in the cell for the observation period
Event : transmission of CHANNEL ACTIVATE or MODE MODIFY with
CHANNEL MODE = “speech”
Class : assignment
Precise
calls:
DFD “GPRS procedure - preemption on PDTCH (normal
completion in the case of Mobile Originating Call)”
DFD “dedicated channel assignment procedure (normal
completion)”
DFD “queuing of the assignment procedure (normal completion)
DFD “Direct retry handover procedure”

411--9001--125
l
1197/3 Number of channels activated for speech: AMR Full Rate
Algorithm
Name Q3 : channelActivateSpeechAmrFr
Object : bts
Function : number of speech channels using the AMR Full-Rate algorithm,
Class : assignment
Precise
calls:
completion)”

l
1900/0 Number of AMR full rate TCH allocations
Name Q3 : amrFrTchAllocated
amrFrTchAllocatedTrZone
Function : number of AMR full rate TCH allocations
Event : This counter is incremented when a AMR full rate TCH is allocated
Note : V14 counter
l
1901/0 Average and Maximum number of AMR full rate TCH
allocations
Name Q3 : amrFrTchStdAveragedUsedMoy
amrFrTchStdAveragedUsedMax
amrFrTchStdAveragedUsedCum
amrFrTchStdAveragedUsedEch
amrFrTchStdAveragedUsedTrZoneMoy
amrFrTchStdAveragedUsedTrZoneMax
amrFrTchStdAveragedUsedTrZoneCum
amrFrTchStdAveragedUsedTrZoneEch
Function : Average and Maximum number of AMR full rate TCH allocations
Event : This counter is incremented when an AMR full rate TCH is allocated
or de--allocated
Note : V14 counter

411--9001--125
l
1902/0 Duration of the AMR full rate TCH connections
Name Q3 : amrFrTchConnectionDurationMoy
amrFrTchConnectionDurationTrZoneMoy
amrFrTchConnectionDurationMax
amrFrTchConnectionDurationTrZoneMax
amrFrTchConnectionDurationCum
amrFrTchConnectionDurationTrZoneCum
amrFrTchConnectionDurationEch
amrFrTchConnectionDurationTrZoneEch
Function : Duration of the AMR full rate TCH connections. This counter starts at
the beginning of transmission of SACCH blocks, and stops at the end
of SACCH blocks transmission.
Event : This counter is triggered when data is received by the BSC from the
BTS in STOP MEASUREMENT ACK messages
Note : V14 counter
l
1902/1 Duration of the AMR half rate TCH connections
Name Q3 : amrHrTchConnectionDurationMoy
amrHrTchConnectionDurationTrZoneMoy
amrHrTchConnectionDurationMax
amrHrTchConnectionDurationTrZoneMax
amrHrTchConnectionDurationCum
amrHrTchConnectionDurationTrZoneCum
amrHrTchConnectionDurationEch
amrHrTchConnectionDurationTrZoneEch
Function : Duration of the AMR half rate TCH connections. This counter starts
at the beginning of transmission of SACCH blocks, and stops at the
end of SACCH blocks transmission.
Note : V14 counter

l
1903/0 Number of Successful AMR full rate TCH assignations for any
kind of mobile
Name Q3 : amrFrTchSuccessfullyAssigned
Object : bts
Function : Number of Successful AMR full rate TCH assignations for any kind
of mobile
Event : See function
Note : V14 counter
l
1903/1 Number of Successful AMR half rate TCH assignations for any
kind of mobile
Name Q3 : amrHrTchSuccessfullyAssigned
Object : bts
Function : Number of Successful AMR half rate TCH assignations for any kind
of mobile
Note : V14 counter
l
1904/0 Number of Failures of the Dedicated Channel Assignment
Procedure for AMR full rate TCH
Name Q3 : amrFrTchAssignFailure
Object : bts
Function : Number of Failures of the Dedicated Channel Assignment Procedure
for AMR full rate TCH
Event : This counter is triggered on reception of an Assign_Fail message on
AMR TCH from the mobile
Note : V14 counter

411--9001--125
l
1904/1 Number of Failures of the Dedicated Channel Assignment
Procedure for AMR half rate TCH
Name Q3 : amrHrTchAssignFailure
Object : bts
Function : Number of Failures of the Dedicated Channel Assignment Procedure
for AMR half rate TCH
Event : This counter is triggered on reception of an Assign_Fail message on
AMR TCH from the mobile
Note : V14 counter
l
1905 Total of the uplink C/I received from the L1m, for a non AMR
channel
Name Q3 : CIUplinkFr
CIUplinkFrTrZone
Function : Total of the uplink C/I received from the L1m, for a non AMR channel
(i.e. classic TCH and SDCCH)
Note : V14 counter

l
1906 Amount of time the downlink power control was running at the
maximum level for the busy full rate AMR TCHs
Name Q3 : downlinkPowerCtrlMaxTchAmrFrCum
downlinkPowerCtrlMaxTchAmrFrEch
downlinkPowerCtrlMaxTchAmrFrMax
downlinkPowerCtrlMaxTchAmrFrMoy
Object : bts
Function : Minimum, maximum, average, and cumulative amount of time the
downlink power control was running at the maximum level for the
busy full rate AMR TCHs
Note : V14 counter
l
1907 Amount of time the uplink power control was running at the
maximum level for the busy full rate AMR TCHs
Name Q3 : uplinkPowerCtrlMaxTchAmrFrCum
uplinkPowerCtrlMaxTchAmrFrEch
uplinkPowerCtrlMaxTchAmrFrMax
uplinkPowerCtrlMaxTchAmrFrMoy
Object : bts
Function : Minimum, maximum, average, and cumulative amount of time the
uplink power control was running at the maximum level for the busy
full rate AMR TCHs
Note : V14 counter

411--9001--125
l
1908 Number of downlink RXLEV received from the L1m for AMR
full rate TCH
Name Q3 : RxLevDownlinkAmrFr
RxLevDownlinkAmrFrTrZone
Function : Number of downlink RXLEV received from the L1m for AMR full
rate TCH
Note : V14 counter
l
1909 Number of uplink RXLEV received from the L1m for AMR full
rate TCH
Name Q3 : RxLevUplinkAmrFr
RxLevUplinkAmrFrTrZone
Function : Number of uplink RXLEV received from the L1m for AMR full rate
TCH
Note : V14 counter

l
1910 Number of downlink RXQUAL received from the L1m for AMR
full rate TCH
Name Q3 : RxQualDownlinkAmrFr
RxQualDownlinkAmrFrTrZone
Function : Number of downlink RXQUAL received from the L1m for AMR full
rate TCH
Note : V14 counter
l
1911 Number of uplink RXQUAL received from the L1m for AMR full
rate TCH
Name Q3 : RxQualUplinkAmrFr
RxQualUplinkAmrFrTrZone
Function : Number of uplink RXQUAL received from the L1m for AMR full
rate TCH
Note : V14 counter

411--9001--125
l
1912 Number of MS increment power control ordered by the L1m for
AMR full rate TCH
Name Q3 : msPowerIncControlAmrFr
Object : bts
Function : Number of MS increment power control ordered by the L1m for AMR
full rate TCH
Note : V14 counter
l
1913 Number of MS decrement power control ordered by the L1m for
AMR full rate TCH
Name Q3 : msPowerDecControlAmrFr
Object : bts
Function : Number of MS decrement power control ordered by the L1m for
AMR full rate TCH
Note : V14 counter
l
1914 Number of BS increment power control ordered by the L1m for
AMR full rate TCH
Name Q3 : bsPowerIncControlAmrFr
Object : bts
Function : Number of BS increment power control ordered by the L1m for AMR
full rate TCH
Note : V14 counter

l
1915 Number of BS decrement power control ordered by the L1m for
AMR full rate TCH
Name Q3 : bsPowerDecControlAmrFr
Object : bts
Function : Number of BS decrement power control ordered by the L1m for AMR
full rate TCH
Note : V14 counter
l
1916 Total of the uplink C/I received from the L1m, for AMR full rate
calls
Name Q3 : CIUplinkAmrFr
CIUplinkAmrFrTrZone
Function : Total of the uplink C/I received from the L1m, for AMR full rate calls
Event : This counter is triggered upon reception of uplink C/I from the L1m
Note : V14 counter
l
1917/0 Average timing advance values for AMR full rate calls in the cell
Name Q3 : timingAdvanceAmrFrAvg
Object : bts
Function : Average timing advance values for AMR full rate calls in the cell
Event : This counter is triggered upon reception of a STOP
MEASUREMENT ACK message from the BTS. The value given by
the BTS is the average timing advance per communication
Note : V14 counter

411--9001--125
l
1917/1 Maximum timing advance values for AMR full rate calls in the
cell
Name Q3 : timingAdvanceAmrFrMax
Object : bts
Function : Maximum timing advance values for AMR full rate calls in the cell
the BTS is the maximum timing advance per communication
Note : V14 counter
l
1918/0 Amount of time the downlink power control was running at the
maximum level for the busy half rate AMR TCHs
Name Q3 : downlinkPowerCtrlMaxTchAmrHrCum
downlinkPowerCtrlMaxTchAmrHrEch
downlinkPowerCtrlMaxTchAmrHrMax
downlinkPowerCtrlMaxTchAmrHrMoy
Object : bts
Function : Amount of time the downlink power control was running at the
Note : V14 counter
l
1919/0 Amount of time the uplink power control was running at the
Name Q3 : uplinkPowerCtrlMaxTchAmrHrCum
uplinkPowerCtrlMaxTchAmrHrEch
uplinkPowerCtrlMaxTchAmrHrMax
uplinkPowerCtrlMaxTchAmrHrMoy
Object : bts
Function : Amount of time the uplink power control was running at the

Note : V14 counter
l
1920/0 Number of downlink RXLEV received from the L1m for AMR
half rate TCH
Name Q3 : RxLevDownlinkAmrHr
RxLevDownlinkAmrHrTrZone
Function : Number of downlink RXLEV received from the L1m for AMR half
rate TCH
Note : V14 counter
l
1921/0 Number of uplink RXLEV received from the L1m for AMR half
rate TCH
Name Q3 : RxLevUplinkAmrHr
RxLevUplinkAmrHrTrZone
Function : Number of uplink RXLEV received from the L1m for AMR half rate
TCH
Note : V14 counter

411--9001--125
l
1922/0 Number of downlink RXQUAL received from the L1m for AMR
half rate TCH
Name Q3 : RxQualDownlinkAmrHr
RxQualDownlinkAmrHrTrZone
Function : Number of downlink RXQUAL received from the L1m for AMR half
rate TCH
Note : V14 counter
l
1923/0 Number of uplink RXQUAL received from the L1m for AMR
half rate TCH
Name Q3 : RxQualUplinkAmrHr
RxQualUplinkAmrHrTrZone
Function : Number of uplink RXQUAL received from the L1m for AMR half
rate TCH
Note : V14 counter
l
1924/0 Number of MS increment power control ordered by the L1m for
AMR half rate TCH
Name Q3 : msPowerIncControlAmrHr
Object : bts
Function : Number of MS increment power control ordered by the L1m for AMR
half rate TCH

Note : V14 counter
l
1925/0 Number of MS decrement power control ordered by the L1m for
AMR half rate TCH
Name Q3 : msPowerDecControlAmrHr
Object : bts
Function : Number of MS decrement power control ordered by the L1m for
AMR half rate TCH
Note : V14 counter
l
1926/0 Number of BS increment power control ordered by the L1m for
AMR half rate TCH
Name Q3 : bsPowerIncControlAmrHr
Object : bts
Function : Number of BS increment power control ordered by the L1m for AMR
half rate TCH
Note : V14 counter
l
1927/0 Number of BS decrement power control ordered by the L1m for
AMR half rate TCH
Name Q3 : bsPowerDecControlAmrHr
Object : bts
Function : Number of BS decrement power control ordered by the L1m for AMR
half rate TCH

411--9001--125
Note : V14 counter
l
1928/0 Total of the uplink C/I received from the L1m, for AMR half rate
calls
Name Q3 : CIUplinkAmrHr
CIUplinkAmrHrTrZone
Function : Total of the uplink C/I received from the L1m, for AMR half rate calls
Event : This counter is triggered upon reception of uplink C/I from the L1m
Note : V14 counter
l
1929/0 Average timing advance values for AMR half rate calls in the cell
Name Q3 : timingAdvanceAmrHrAvg
Object : bts
Function : Average timing advance values for AMR half rate calls in the cell
the BTS is the average timing advance per communication
Note : V14 counter
l
1929/1 Maximum timing advance values for AMR half rate calls in the
cell
Name Q3 : timingAdvanceAmrHrMax
Object : bts
Function : Maximum timing advance values for AMR half rate calls in the cell


the BTS is the maximum timing advance per communication
Note : V14 counter
l
1930/0 Number of MS measurement messages not received by the BTS
for a AMR full rate call
Name Q3 : msLostMeasurementsAmrFr
msLostMeasurementsAmrFrTrZone
Function : Number of MS measurement messages not received by the BTS for a
AMR full rate call
Note : V14 counter
l
1931/0 Number of MS measurement messages not received by the BTS
for a AMR half rate call
Name Q3 : msLostMeasurementsAmrHr
msLostMeasurementsAmrHrTrZone
Function : Number of MS measurement messages not received by the BTS for a
AMR half rate call
Note : V14 counter
l
1932/0 Number of quality intracell handovers filtered
Name Q3 : qualityHoFiltered
Object : bts
Function : Number of quality intracell handovers filtered

411--9001--125
Note : V14 counter
l
1933/0 Number of capacity intracell handovers filtered
Name Q3 : capacityHoFiltered
Object : bts
Function : Number of capacity intracell handovers filtered
Note : V14 counter
l
1934/0 Average and Maximum number of AMR full rate TCH
allocations
Name Q3 : amrFrTchStdAveragedUsedCellMoy
amrFrTchStdAveragedUsedCellMax
amrFrTchStdAveragedUsedCellCum
amrFrTchStdAveragedUsedCellEch
Object : bts
Function : Average and Maximum number of AMR full rate TCH allocations
Event : This counter is incremented when an AMR full rate TCH is allocated
or de--allocated
1935/0 number of periods of 10 s where the cell load is greater than 0

Name Q3 : amrHrModeDuration
Object : bts
Function : number of periods of 10 s where the cell load state is greater than 0
Event : Cell load evaluation
Feature : 22688 AMR based on traffic

1936/0 number of cell load state change

Name Q3 : amrCellLoadStateModification
Object : bts
Function : number of cell load state change
1937/0 Average and maximum value of the filtered busy TCH ratio
Name Q3 : amrFilteredBusyTchRatioMoy
amrFilteredBusyTchRatioMax
amrFilteredBusyTchRatioCum
amrFilteredBusyTchRatioEch
Object : bts
Function : Average and maximum value of the filtered busy TCH ratio in %
Filtered_TCH_ration = a * (busy_TCH_TS /
available_TCH_TS)+ (1--a) * Filtered_TCH_ration-- 1
Filtered_TCH_ratio0 = 0
Filtered_TCH_ration is the busy TCH ratio managed by the cell at
second n
a is the filter coefficient (filteredTrafficCoefficient parameter)
busy_TCH_TS is the number of TCH TS allocated to a FR or a HR
TCH call (in case of multi--zones cell, traffic of both zones is taken
into account)
available_TCH_TS is the number of TCH TS configurated and
available in the cell (in case of multi--zones cell, traffic of both zones
is taken into account)

411--9001--125
1938/0 AMR cell load underevaluated

Name Q3 : amrCellLoadStateUnderevaluated
Object : bts
Function : number of periods of 10 s where the busy TCH ratio is greater than the
hRCellLoadStart parameter and the cell load state not equal to the
maximum
1939/0 AMR cell load overevaluated

Name Q3 : amrCellLoadStateOverevaluated
Object : bts
Function : number of periods of 10 s where the busy TCH ratio is smaller than the
hRCellLoadEnd parameter and the cell load state not equal to the
minimum
l
1950/0 Number of Intracell AMR full rate uplink required handovers in
the cell
Name Q3 : intracellAmrFrUpHoRequiredTch
Object : bts
Function : Number of Intracell AMR full rate uplink required handovers in the
cell

Event : This counter is triggered on reception of:

HANDOVER INDICATION (except when this message shall be
ignored)
Directed retry attempt: reception of a CONNECTION REQUEST
ACK message or autonomously in case of directed retry from a
micro--cell
CONNECTION REQUEST ACK with an eligible cells list after
Tchoke expires
Note : V14 counter
l
1950/1 Number of Intracell AMR full rate downlink required handovers
in the cell
Name Q3 : intracellAmrFrDownHoRequiredTch
Object : bts
Function : Number of Intracell AMR full rate downlink required handovers in
the cell
ignored)
micro--cell
Tchoke expires
Note : V14 counter
l
1950/2 Number of AMR Quality full rate uplink required handovers in
the cell
Name Q3 : amrQualityFrUpHoRequiredTch
Object : bts
Function : Number of AMR Quality full rate uplink required handovers in the
cell

411--9001--125

ignored)
micro--cell
Tchoke expires
Note : V14 counter
l
1950/3 Number of AMR Quality full rate downlink required handovers
in the cell
Name Q3 : amrQualityFrDownHoRequiredTch
Object : bts
Function : Number of AMR Quality full rate downlink required handovers in the
cell
ignored)
micro--cell
Tchoke expires
Note : V14 counter
l
1950/4 Number of the capacity of full rate to half rate required
Name Q3 : capacityFrToHrHoRequiredTch
Object : bts
Function : Number of the capacity of full rate to half rate required handovers in
the cell


ignored)
micro--cell
Tchoke expires
Note : V14 counter
l
1951/0 Number of half rate to full rate alarms in AMR uplink required
Name Q3 : alarmAmrHrToFrUpHoRequiredTch
Object : bts
Function : Number of half rate to full rate alarms in AMR uplink required
ignored)
micro--cell
Tchoke expires
Note : V14 counter
l
1951/1 Number of half rate to full rate alarms in AMR downlink
required handovers in the cell
Name Q3 : alarmAmrHrToFrDownHoRequiredTch
Object : bts
Function : Number of half rate to full rate alarms in AMR downlink required

411--9001--125

ignored)
micro--cell
Tchoke expires
Note : V14 counter
l
1951/2 Number of AMR Quality half rate uplink required handovers in
the cell
Name Q3 : amrQualityHrUpHoRequiredTch
Object : bts
Function : Number of AMR Quality half rate uplink required handovers in the
cell
ignored)
micro--cell
Tchoke expires
Note : V14 counter
l
1951/3 Number of AMR Quality half rate downlink required handovers
in the cell
Name Q3 : amrQualityHrDownHoRequiredTch
Object : bts
Function : Number of AMR Quality half rate downlink required handovers in the
cell


ignored)
micro--cell
Tchoke expires
Note : V14 counter
l
1952/0 Number of outgoing handovers (intra/inter_bss) requests by a
full rate AMR MS
Name Q3 : amrFrHoRequestOutgoingTch
Object : bts
Function : Number of outgoing handovers (intra/inter_bss) requests by a full rate
AMR MS
Note : V14 counter
l
1952/1 Number of outgoing handovers (intra/inter_bss) requests by a
half rate AMR MS
Name Q3 : amrHrHoRequestOutgoingTch
Object : bts
Function : Number of outgoing handovers (intra/inter_bss) requests by a half
rate AMR MS
Note : V14 counter

411--9001--125
l
1953/0 Number of Intracell full rate handover requests for the cell, by an
AMR mobile
Name Q3 : amrFrHoRequestIntraCellTch
Object : bts
Function : Number of Intracell full rate handover requests for the cell, by an
AMR mobile. This counter is incremented at the end of the handover
(success, selection failure, execution, failure or end of call)
Event : This counter is triggered upon an attempt of selection in the cell
Note : V14 counter
l
1953/1 Number of Intracell full rate to half rate handover requests for
the cell, by an AMR mobile
Name Q3 : amrFrToHrHoRequestIntraCellTch
Object : bts
Function : Number of Intracell full rate to half rate handover requests for the cell,
by an AMR mobile. This counter is incremented at the end of the
handover (success, selection failure, execution, failure or end of call)
Note : V14 counter
l
1953/2 Number of Intracell half rate to full rate handover requests for
Name Q3 : amrHrToFrHoRequestIntraCellTch
Object : bts
Function : Number of Intracell half rate to full rate handover requests for the cell,
by an AMR mobile. This counter is incremented at the end of the
Note : V14 counter

l
1954/0 Number of Intracell full rate handover executions for the cell, by
an AMR mobile
Name Q3 : amrFrHoExecutionIntraCellTch
Object : bts
Function : Number of Intracell full rate handover executions for the cell, by an
AMR mobile. This counter is incremented at the end of the handover
(success, selection failure, execution, failure or end of call)
Event : This counter is triggered upon the transmission of
ASSIGN_COMMAND message
Note : V14 counter
l
1954/1 Number of Intracell full rate to half rate handover executions for
Name Q3 : amrFrToHrHoExecutionIntraCellTch
Object : bts
Function : Number of Intracell full rate to half rate handover executions for the
cell, by an AMR mobile. This counter is incremented at the end of the
Note : V14 counter
l
1954/2 Number of Intracell half rate to full rate handover executions for
Name Q3 : amrHrToFrHoExecutionIntraCellTch
Object : bts
Function : Number of Intracell half rate to full rate handover executions for the
cell, by an AMR mobile. This counter is incremented at the end of the

411--9001--125

Note : V14 counter
l
1955/0 Number of successful Intracell full rate handovers for the cell, by
an AMR mobile
Name Q3 : amrFrHoSuccessIntraCellTch
Object : bts
Function : Number of successful Intracell full rate handovers for the cell, by an
AMR mobile.
ASSIGN_COMPLETE message from the mobile
Note : V14 counter
l
1955/1 Number of successful Intracell full rate to half rate handovers for
Name Q3 : amrFrToHrHoSuccessIntraCellTch
Object : bts
Function : Number of successful Intracell full rate to half rate handovers for the
cell, by an AMR mobile.
Note : V14 counter
l
1955/2 Number of successful Intracell half rate to full rate handovers for
Name Q3 : amrHrToFrHoSuccessIntraCellTch
Object : bts
Function : Number of successful Intracell half rate to full rate handovers for the
cell, by an AMR mobile.


Note : V14 counter
l
1956/0 Number of attempts of half rate AMR handover from a central
cell to a neighboring one
Name Q3 : hoNCellsExecutionTchAmrHr
Object : adjacentCellHandOver
Function : Number of attempts of half rate AMR handover from a central cell to a
neighboring one
Event : This counter is triggered upon reception of the HANDOVER
COMMAND message from the MSC (inter BSC handover), or
transmission of ABIS HANDOVER COMMAND message (intra
BSC handover)
Note : V14 counter
l
1957/0 Number of attempts of full rate ARM handover from a central
Name Q3 : hoNCellsExecutionTchAmrFr
Function : Number of attempts of full rate ARM handover from a central cell to a
neighboring one
COMMAND message from the MSC (inter BSC handover), or
transmission of ABIS HANDOVER COMMAND message (intra
BSC handover)
Note : V14 counter

411--9001--125
l
1958/0 Number of unsuccessful half rate AMR handovers from a central
cell to a neighboring one caused by the mobile returning to the old
channel
Name Q3 : hoNCellsUnsuccessTchAmrHrHandoverFailure
Function : Number of unsuccessful half rate AMR handovers from a central cell
to a neighboring one caused by the mobile returning to the old channel
FAILURE message before T3103 timer expiration
Note : V14 counter
l
cell to a neighboring one caused by the expiration of the T3103
timer
Name Q3 : hoNCellsUnsuccessTchAmrHrTimerExpiration
to a neighboring one caused by the expiration of the T3103 mobile
Event : This counter is triggered upon the expiration of the T3103 timer. This
is relevant for intra BSS and inter BSS handovers
Note : V14 counter
l
cell to a neighboring one caused by other causes
Name Q3 : hoNCellsUnsuccessTchAmrHrClearCommand
to a neighboring one caused by other causes (i.e. not caused by those
mentioned in counters 1958/0 or 1958/1)

Event : This counter is triggered upon reception of the CLEAR COMMAND

message with a cause set to another value than “Handover Successful”
or “Call Control”, relevant for inter BSS handovers
Note : V14 counter
l
1959/0 Number of unsuccessful full rate AMR handovers from a central
cell to a neighboring one caused by the mobile returning to the old
channel
Name Q3 : hoNCellsUnsuccessTchAmrFrHandoverFailure
Function : Number of unsuccessful full rate AMR handovers from a central cell
to a neighboring one caused by the mobile returning to the old channel
FAILURE message before T3103 timer expiration
Note : V14 counter
l
cell to a neighboring one caused by the expiration of the T3103
timer
Name Q3 : hoNCellsUnsuccessTchAmrFrTimerExpiration
to a neighboring one caused by the expiration of the T3103 mobile
Event : This counter is triggered upon the expiration of the T3103 timer. This
is relevant for intra BSS and inter BSS handovers
Note : V14 counter

411--9001--125
l
cell to a neighboring one caused by other causes
Name Q3 : hoNCellsUnsuccessTchAmrFrClearCommand
to a neighboring one caused by other causes (i.e. not caused by those
mentioned in counters 1959/0 or 1959/1)
Event : This counter is triggered upon reception of the CLEAR COMMAND
message with a cause set to another value than “Handover Successful”
or “Call Control”, relevant for inter BSS handovers
Note : V14 counter
l
1960/0 Number of releases for full rate AMR mobile caused by Lapdm
Name Q3 : trafficReleaseAmrFrLapdmCause
Object : bts
Function : Number of releases for full rate AMR mobile caused by Lapdm
Event : See Function
Note : V14 counter
l
1960/1 Number of releases for full rate AMR mobile caused the radio
Name Q3 : trafficReleaseAmrFrRadioCause
Object : bts
Function : Number of releases for full rate AMR mobile caused by the radio
Note : V14 counter

l
1960/2 Number of releases for full rate AMR mobile caused by other
causes
Name Q3 : trafficReleaseAmrFrOthersCause
Object : bts
Function : Number of releases for full rate AMR mobile caused by other causes
(i.e. not caused by those mentioned in counters 1960/0 or 1960/1)
Note : V14 counter
l
1961/0 Number of releases for half rate AMR mobile caused by Lapdm
Name Q3 : trafficReleaseAmrHrLapdmCause
Object : bts
Function : Number of releases for half rate AMR mobile caused by Lapdm
Note : V14 counter
l
1961/1 Number of releases for half rate AMR mobile caused the radio
Name Q3 : trafficReleaseAmrHrRadioCause
Object : bts
Function : Number of releases for half rate AMR mobile caused by the radio
Note : V14 counter
l
1961/2 Number of releases for half rate AMR mobile caused by other
causes
Name Q3 : trafficReleaseAmrHrOthersCause
Object : bts
Function : Number of releases for half rate AMR mobile caused by other causes
(i.e. not caused by those mentioned in counters 1961/0 or 1961/1)

411--9001--125

Note : V14 counter
l
1963/0 Number of half rate AMR handovers requested from a central
Name Q3 : hoNCellsRequestOutgoingAmrHr
Function : Number of half rate AMR handovers requested from a central cell to a
neighboring one
Event : Attempt to select a target cell in the list of eligible cells on
transmission of HANDOVER REQUIRED on the A interface (inter
BSC handover) or attempt to select a target cell in the list of eligible
cells provided by the handover algorithm (intra BSC handover).
Note : V14 counter
l
1964/0 Number of full rate AMR handovers requested from a central cell
to a neighboring one
Name Q3 : hoNCellsRequestOutgoingAmrFr
Function : Number of full rate AMR handovers requested from a central cell to a
neighboring one
Event : Attempt to select a target cell in the list of eligible cells on
transmission of HANDOVER REQUIRED on the A interface (inter
BSC handover) or attempt to select a target cell in the list of eligible
cells provided by the handover algorithm (intra BSC handover).
Note : V14 counter

l
1975/0 Number of 40ms periods during which Codec 4.75 has been
applied on the uplink for full rate AMR
Name Q3 : amrFrUplinkCodec475
amrFrUplinkCodec475TrZone
Function : Number of 40ms periods during which Codec 4.75 has been applied
on the uplink for full rate AMR
Note : V14 counter
l
Function : Number of 40ms periods during which Codec 5.9 has been applied on
the uplink for full rate AMR
Note : V14 counter
l
the uplink for full rate AMR

411--9001--125
Note : V14 counter
l
Name Q3 : : amrFrUplinkCodec102
on the uplink for full rate AMR
Note : V14 counter
l
applied on the uplink for half rate AMR
Name Q3 : amrHrUplinkCodec475
amrHrUplinkCodec475TrZone
on the uplink for half rate AMR
Note : V14 counter

l
the uplink for half rate AMR
Note : V14 counter
l
the uplink for half rate AMR
Note : V14 counter
l
applied on the downlink for full rate AMR
Name Q3 : amrFrDownlinkCodec475
amrFrDownlinkCodec475TrZone
on the downlink for full rate AMR

411--9001--125
Note : V14 counter
l
the downlink for full rate AMR
Note : V14 counter
l
the downlink for full rate AMR
Note : V14 counter

l
on the downlink for full rate AMR
Note : V14 counter
l
applied on the downlink for half rate AMR
Name Q3 : amrHrDownlinkCodec475
amrHrDownlinkCodec475TrZone
on the downlink for half rate AMR
Note : V14 counter
l
the downlink for half rate AMR

411--9001--125
Note : V14 counter
l
the downlink for half rate AMR
Note : V14 counter
l
1979/0 Number of bad speech frames (BFI KO) received at the BTS level
for full rate AMR at Codec 4.75
Name Q3 : amrFrBadSpeechFramesCodec475
amrFrBadSpeechFramesCodec475TrZone
Function : Number of bad speech frames (BFI KO) received at the BTS level for
full rate AMR at Codec 4.75
Note : V14 counter

l
Note : V14 counter
l
Note : V14 counter
l

411--9001--125
Note : V14 counter
l
1980/0 Received speech frames AMR FR at Codec 4.75
Name Q3 : amrFrValidSpeechFramesCodec475
amrFrValidSpeechFramesCodec475TrZone
Function : Number of correct and bad speech frames received at the BTS level
Note : V14 counter
l
Note : V14 counter
l

Note : V14 counter
l
Note : V14 counter
l
for half rate AMR at Codec 4.75
Name Q3 : amrHrBadSpeechFramesCodec475
amrHrBadSpeechFramesCodec475TrZone
half rate AMR at Codec 4.75
Note : V14 counter
l

411--9001--125
Note : V14 counter
l
Note : V14 counter
l
1982/0 Received speech frames AMR HR at Codec 4.75
Name Q3 : amrHrValidSpeechFramesCodec475
amrHrValidSpeechFramesCodec475TrZone
Note : V14 counter
l

Note : V14 counter
l
Note : V14 counter
l
1983/0 Number of no data frames received or sent on the Abis interface
on the uplink for AMR calls
Name Q3 : amrUplinkNoDataFrames
Object : bts
Function : Number of no data frames received or sent on the Abis interface on the
uplink for AMR calls
Note : V14 counter
l
1983/1 Number of no data frames received or sent on the Abis interface
on the downlink for AMR calls
Name Q3 : amrDownlinkNoDataFrames
Object : bts
Function : Number of no data frames received or sent on the Abis interface on the
downlink for AMR calls

411--9001--125
Note : V14 counter
l
1984/0 Number of Codec increment modifications for full rate AMR in
uplink
Name Q3 : incAmrFrUpModif
incAmrFrUpModifTrZone
Function : Number of Codec increment modifications for full rate AMR in
uplink
Note : V14 counter
l
1984/1 Number of Codec decrement modifications for full rate AMR in
uplink
Name Q3 : decAmrFrUpModif
decAmrFrUpModifTrZone
Function : Number of Codec decrement modifications for full rate AMR in
uplink
Note : V14 counter

l
1985/0 Number of Codec increment modifications for full rate AMR in
downlink
Name Q3 : incAmrFrDownModif
incAmrFrDownModifTrZone
Function : Number of Codec increment modifications for full rate AMR in
downlink
Note : V14 counter
l
1985/1 Number of Codec decrement modifications for full rate AMR in
downlink
Name Q3 : decAmrFrDownModif
decAmrFrDownModifTrZone
Function : Number of Codec decrement modifications for full rate AMR in
downlink
Note : V14 counter
l
1986/0 Number of Codec increment modifications for half rate AMR in
uplink
Name Q3 : incAmrHrUpModif
incAmrHrUpModifTrZone
Function : Number of Codec increment modifications for half rate AMR in
uplink

411--9001--125
Note : V14 counter
l
1986/1 Number of Codec decrement modifications for half rate AMR in
uplink
Name Q3 : decAmrHrUpModif
decAmrHrUpModifTrZone
Function : Number of Codec decrement modifications for half rate AMR in
uplink
Note : V14 counter
l
1987/0 Number of Codec increment modifications for half rate AMR in
downlink
Name Q3 : incAmrHrDownModif
incAmrHrDownModifTrZone
Function : Number of Codec increment modifications for half rate AMR in
downlink
Note : V14 counter

l
1987/1 Number of Codec decrement modifications for half rate AMR in
downlink
Name Q3 : decAmrHrDownModif
decAmrHrDownModifTrZone
Function : Number of Codec decrement modifications for half rate AMR in
downlink
Note : V14 counter
l
1988/0 Number of RATSCCH procedure failures for AMR Calls (FR
and HR)
Name Q3 : amrReversalPhaseFailure
Object : bts
Function : number of RATSCCH procedure failures for AMR Calls (FR and
HR). The RATSCCH procedure fails when there is no respose from
the MS after 2 repetitions or negative response received from the MS.
Note : V14 counter

411--9001--125
5.4 Raw permanent BSS counters (common to BSC 12000HC,

BSC 3000, and AMR) (from 1026 to 2068/1)
l
1026 Number of decoded RACH access from the mobiles
Name Q3 : rachBusyCount
rachBusyCountTs2
rachBusyCountTs4
rachBusyCountTs6
Object : bts
Location :
Name Q3 Location
rachBusyCount CCCH--0
rachBusyCount2 CCCH--2
Function : number of RACH bursts received by the BTS that have been decoded;
this internal BTS counter is sent to the BSC in
CCCH_LOAD_INDICATION message.
Event : receipt of a RACH burst decoded by the BTS; receipt of a
CCCH_LOAD_INDICATION message by the BSC.
Class : monitoring
Source : detected by the BTS, recorded by the BSC
Feature : Extended CCCH (TF184 - V12)
Precise
calls:
No distinction is made between RACH dedicated to Circuit Calls or
Packet Calls.
Note : Counter multiplexed on TSs 0, 2, 4 and 6 for Extended CCCH feature.

l
1027 Number of decoded RACH access forwarded to the BSC
Name Q3 : rachAccessCount
rachAccessCountTs2
rachAccessCountTs4
rachAccessCountTs6
Object : bts
Location :
Name Q3 Location
rachAccessCount CCCH--0
rachAccessCount2 CCCH--2
Function : number of RACH bursts that have been decoded and forwarded to the
BSC; this internal BTS counter is sent to the BSC in
Event : transmission of CHANNEL REQUEST to the BSC; receipt of a
CCCH_LOAD_INDICATION message from the BTS
Class : monitoring
Precise
calls:
Packet Calls.

411--9001--125
l
1028 Number of paging messages sent without delay
Name Q3 : pchNoWait
pchNoWaitTs2
pchNoWaitTs4
pchNoWaitTs6
Object : bts
Location :
Name Q3 Location
pchNoWait CCCH--0
pchNoWait2 CCCH--2
pchNoWait4 CCCH--4
pchNoWait6 CCCH--6
Function : number of paging requests which have got a free TS immediately; this
internal BTS counter is sent to the BSC in a
Event : immediate transmission of a PAGING_REQUEST to the MS; receipt
of a CCCH_LOAD_INDICATION message from the BTS.
Class : monitoring

Precise
The counter C1028 is related to the Abis paging and also to the paging
that is being sent on radio interface for the first time (the bts paging
repetition is not counted).
The counter C1028 counts the paging messages that have found a free
PCH on the first paging slot occurrence.
That means that C1028 paging messages have waited less than
NoOfMultiframesBetweenPaging multiframes.
calls:
Packet Calls.
Data flows : The following data flow presents the Layer 3 messages related to the
paging:
MSC BSC BTS MS
Paging Cmd
PAGING_REQUEST1
+C1028
PAGING_REQUEST2
Est Ind
PAGING_REQUEST3
The BTS repeats NbOfRepeat times all the paging messages coming
from the MSC but the counter C1028 is incremented for the fresh
paging only.
The counter C1028 will be incremented when a free PCH on the first
paging is available.

411--9001--125
l
1029 Number of paging messages sent with one slot delay
Name Q3 : pchOneWait
pchOneWaitTs2
pchOneWaitTs4
pchOneWaitTs6
Object : bts
Location :
Name Q3 Location
pchOneWait CCCH--0
pchOneWait2 CCCH--2
pchOneWait4 CCCH--4
pchOneWait6 CCCH--6
Function : number of paging requests which had to wait once before finding a
free TS; this internal BTS counter is sent to the BSC in a
Event : transmission of a PAGING_REQUEST to the MS after one wait;
receipt of a CCCH_LOAD_INDICATION message from the BTS.
Class : monitoring
Precise
PCH on the second paging slot occurrence. It means that C1029
paging messages have waited more than
NbOfMultiframesBetweenPaging multiframes and less than 2x
NbOfMultiframesBetweenPaging multiframes.
For example:
If NbOfMultiframesBetweenPaging = 8 (8 multiframes of 240ms
between the same paging group), C1029 paging messages have
waited between 1x8x240 ms (about 2 sec) and 2x8x240 ms (about 4
sec).


calls:
Packet Calls.
Data flows : The following dataflow presents the Layer 3 messages related to the
paging:
MSC BSC BTS MS
Paging Cmd
(1 ST PAGING SLOT OCCUR-
RENCE IS BUSY)
PAGING_REQUEST1
+C1029
PAGING_REQUEST2
Est Ind
PAGING_REQUEST3
paging only.
The fresh paging message has to wait for the next paging group slot as
the first paging group presented was busy.

411--9001--125
l
1030 Number of paging messages sent with two slots delay
Name Q3 : pchTwoWait
pchTwoWaitTs2
pchTwoWaitTs4
pchTwoWaitTs6
Object : bts
Location :
Name Q3 Location
pchTwoWait CCCH--0
pchTwoWait2 CCCH--2
pchTwoWait4 CCCH--4
pchTwoWait6 CCCH--6
Function : number of paging requests which had to wait twice before finding a
Event : transmission of a PAGING_REQUEST to the MS after two waits;
receipt of a CCCH_LOAD_INDICATION message from the BTS.
Class : monitoring
Precise
PCH on the third paging group occurrence because the 2 previous
ones were busy. It means that the counter C1030 fresh paging
messages from the MSC have waited more than
2xNbOfMultiframesBetweenPaging multiframes and less than
3xNbOfMultiframesBetweenPaging multiframe to get its free PCH.


calls:
Packet Calls.
paging:
MSC BSC BTS MS
Paging Cmd (1 ST AND 2 ND PAGING SLOT OCCUR-

RENCES ARE BUSY)
PAGING_REQUEST1
+C1030
PAGING_REQUEST2
Est Ind
PAGING_REQUEST3
paging only.
the first and second paging groups presented were busy.
l
1031 Number of paging messages sent with more than two slots delay
Name Q3 : pchMoreWait
pchMoreWaitTs2
pchMoreWaitTs4
pchMoreWaitTs6
Object : bts

411--9001--125
Location :
Name Q3 Location
pchMoreWait CCCH--0
pchMoreWait2 CCCH--2
Function : number of paging requests which had to wait twice before finding a
Event : transmission of a PAGING_REQUEST to the MS; receipt of a
CCCH_LOAD_INDICATION message from the BTS.
Class : monitoring
Precise
The counter C1031 counts the paging messages that need to wait
more than 2 paging group slots. It means that the counter C1031 fresh
paging messages from the MSC have waited for more than
3xNbOfMultiframesBetweenPaging multiframes.
calls:
Packet Calls.

paging:
MSC BSC BTS MS
Paging Cmd
(1 ST, 2 ND, AND 3 RD PAGING SLOT
OCCURRENCES ARE BUSY)
PAGING_REQUEST1
+C1031
PAGING_REQUEST2
Est Ind
PAGING_REQUEST3
paging only.
the first, second, and third paging groups presented were busy.
l
1033 Average level of non-decoded RACH access
Name Q3 : rachNonDecodedAvLevelMoy
rachNonDecodedAvLevelTs2Moy
rachNonDecodedAvLevelMax = Max RACH access level
rachNonDecodedAvLevelTs2Max = Max RACH access level
rachNonDecodedAvLevelCum = Total RACH access level
rachNonDecodedAvLevelTs2Cum = Total RACH access level
rachNonDecodedAvLevelEch = Number of samples
rachNonDecodedAvLevelTs2Ech = Number of samples
Object : bts

411--9001--125
Location :
Name Q3 Location
rachNonDecodedAvLevelMoy/Max/Cum/Ech CCCH--0
rachNonDecodedAvLevelTs2Moy/Max/Cum/Ech CCCH--2
Function : average (= total level divided by number of samples) and maximum

level of RACH bursts not decoded (dBm); this internal BTS counter is
sent to the BSC in a CCCH_LOAD_INDICATION message.
Event : receipt of a RACH burst that the BTS cannot decode
Class : monitoring
Precise
calls:
Packet Calls.
l
1044 Average time of a signaling channel seizure
Name Q3 : signallingPhaseDurationMoy . . . . . Average time of seizure
signallingPhaseDurationMax . . . . . Maximum time of seizure
signallingPhaseDurationCum . . . . Total time of seizure
signallingPhaseDurationEch . . . . . Number of samples
Object : bts
Function : average (= total seizure divided by number of samples) and maximum
seizure of signaling channels expressed in milliseconds, calculated on
all allocations in the cell

Event : signaling channel allocation on reception of CONNECTION

CONFIRM (first establishment in the BSS) or HANDOVER
COMPLETE (incoming inter handover in signaling phase) /
deallocation on reception of ASSIGN COMPLETE or when the call is
released
allocation: start timer
deallocation:
• add measured value to the total number of allocation durations
for the observation period
Class : assignment
Precise
calls:
DFD “GPRS procedure (no available resource for a PDTCH
preemption)”
DFD “GPRS procedure (negative acknowledgement by the PCU
for a PDTCH preemption)”
completion)”
DFD “connection clearing required by the MSC procedure
(normal completion with communication on SIGNALLING
phase)”
DFD “Dedicated channel assignment modify procedure (normal
completion)”
DFD “Connection clearing required by the BSC procedure
(communication on SIGNALING phase)”

411--9001--125
l
1045 Average time of a signaling channel seizure > 25 s
Name Q3 : signallingPhaseDurationHighMoy . Average time of seizure > 25 s
signallingPhaseDurationHighMax . Max time of seizure > 25 s
signallingPhaseDurationHighCum Total time of seizure > 25 s
signallingPhaseDurationHighEch . Number of samples
Object : bts
Function : average (= total seizure divided by number of samples) and maximum
seizure of signaling channels expressed in milliseconds, calculated on
all allocations lasting more than 25 seconds
Event : signaling channel allocation on reception of CONNECTION
CONFIRM (first establishment in the BSS) or HANDOVER
COMPLETE (incoming inter handover in signaling phase) /
deallocation on reception of ASSIGN COMPLETE or when the call is
released
allocation: start timer
deallocation: stop and read timer. When the value read is greater
than 25 seconds, do the following:
• add measured value to the total number of allocations lasting
more than 25 seconds for the observation period
Class : assignment
Precise
calls:


completion)
completion)”
DFD “queuing of the assignment procedure (normal completion)”
phase)”
completion)”
l
1049 Number of TCH/FR or preempted PDTCH assignment requests
Name Q3 : attemptedTchFrSeizures
Object : bts
Function : number of TCH/FR or preempted PDTCH assignment requests in the
observation period
Event : transmission of ASSIGNMENT COMMAND to the mobile
Class : assignment
Precise
calls:
completion)”

411--9001--125
l
1050 Number of TCH/FR or a preempted PDTCH successfully
assigned
Name Q3 : successfulTchFrSeizures
Object : bts
Function : number of TCH/FR or a preempted PDTCH assignments in the
observation period
Event : receipt of ASSIGNMENT COMPLETE message by the BSC
Class : assignment
Precise
calls:
completion)”
l
1055 Number of ASSIGN FAILURE messages received on TCH
Name Q3 : assignFailure
Object : bts
Function : number of ASSIGNMENT FAILURE messages sent by the cell
Event : receipt of an ASSIGNMENT FAILURE messages sent on TCH or
preempted PDTCH from the MS
Class : assignment

Precise
calls:
l
1057 Average duration to allocate all TCH/FR and preempted PDTCH
resources
Name Q3 : allTchFrAllocatedTimeMoy . . . . . . Average allocation duration
allTchFrAllocatedTimeMax . . . . . . Maximum allocation duration
allTchFrAllocatedTimeCum . . . . . Total allocation duration
allTchFrAllocatedTimeEch . . . . . . Number of samples
allTchFrAllocatedTimeTrZoneMoy Average allocation duration
allTchFrAllocatedTimeTrZoneMax Maximum allocation duration
allTchFrAllocatedTimeTrZoneCum Total allocation duration
allTchFrAllocatedTimeTrZoneEch Number of samples
Function : average (= total duration divided by number of samples) and

maximum duration during which all available TCH/FR resources and
PDTCH resources configured as preemptable are used in the cell for
the observation period, expressed in milliseconds
Event :
Starts measurement on allocation of ALL the available TCH/FR
and preemptable PDTCH resources of the cell.
Stops as soon as a resource is free.
As a result, the counter behavior depends on the setting of
gprsPreemption parameter on the OMC--R side.
In case of preemption not acknowledged by the PCU, the counter
starts immediately and stops as soon as a resource is released, or as
soon as the timer GprsPreemptionProtection elapses.
Class : allocation
Source : calculated by the OMC--R agent

411--9001--125
Precise
calls:
When new counter 1823 is received, its value is copied in counter
1057.
Note : A blocked resource is neither considered as used nor available.
l
1060/0 Average allocation duration of all SDCCH resources
Name Q3 : allSdcchAllocatedTimeMoy . . . . . Average allocation duration
allSdcchAllocatedTimeMax . . . . . . Maximum allocation duration
allSdcchAllocatedTimeCum . . . . . Total allocation duration
allSdcchAllocatedTimeEch . . . . . . Number of samples
allSdcchAllocatedTimeTrZoneMoy Average allocation duration
allSdcchAllocatedTimeTrZoneMax Maximum allocation duration
allSdcchAllocatedTimeTrZoneCum Total allocation duration
allSdcchAllocatedTimeTrZoneEch Number of samples
Function : average (= total duration divided by number of samples) and
maximum allocation duration of all available SDCCHs used in the
cell for the observation period, expressed in milliseconds
Event : Start and stop events are the following:
starts when the last available SDCCH resource in the cell is
allocated
stops as soon as a SDCCH resource is freed
Class : allocation
Precise
calls:

l
1065/0 Number of outgoing intra--bss handovers on TCH executed
Name Q3 : hoExecutionOutgoingIntraBss
Object : bts
Function : number of attempts to execute outgoing intra-bss handovers on TCH
Event : transmission of HANDOVER COMMAND to the serving cell
Class : handover
Precise
calls:
1066/0 Number of outgoing inter--bss handovers on TCH executed

Name Q3 : hoExecutionOutgoingInterBss
Object : bts
Function : number of attempts to execute outgoing inter-bss handovers on TCH
Event : reception of HANDOVER COMMAND from the MSC
Class : handover
Precise
calls:

411--9001--125

l
1067/0 Number of successful outgoing intra--bss handovers on TCH
Name Q3 : hoSuccessOutgoingIntraBss
Object : bts
Function : number of successful outgoing intra-bss handovers on TCH
Event : receipt of HANDOVER COMPLETE from the target cell
Class : handover
Precise
calls:

l
1068/0 Number of successful outgoing inter--bss handovers on TCH
except those after first attempt
Name Q3 : hoSuccessOutgoingInterBss
Object : bts
Function : number of successful outgoing inter-bss handovers on TCH except
those after first attempt
Event : receipt of CLEAR COMMAND from the MSC with cause “Handover
Successful”
Class : handover
Precise
calls:
Note : For the number of successful outgoing inter handovers on TCH after
first attempt see counter 1078.
l
1069 Number of incoming intra--bss handovers on TCH requested
Name Q3 : hoRequestIncomingIntraBss
Object : bts
Function : number of incoming intra-bss handover requests on TCH in the cell
for any kind of the mobile
Event : attempt to select a target cell in the list of eligible cells on transmission
of HANDOVER REQUIRED on the A interface
Class : handover

411--9001--125
Precise
calls:
Note : the counter is incremented at the end of the handover (success,
selection failure, execution failure or end of call)
l
1070 Number of incoming inter--bss handovers on TCH requested
Name Q3 : hoRequestIncomingInterBss
Object : bts
Function : number of incoming inter-bss handover requests on TCH in the cell
Event : receipt of HANDOVER REQUEST from the MSC on the A interface
Class : handover
Precise
calls:

l
1071 Number of incoming intra--bss handovers on TCH execution
attempts
Name Q3 : hoExecutionIncomingIntraBss
Object : bts
Function : number of attempts to execute incoming intra-bss handovers on TCH
in the cell for any kind of the mobile
Class : handover
Precise
calls:
selection failure execution failure or end of call)
l
1072 Number of incoming inter--bss handovers on TCH executed
Name Q3 : hoExecutionIncomingInterBss
Object : bts
Function : number of attempts to execute incoming inter-bss handovers on TCH
Event : transmission of HANDOVER REQUEST ACKNOWLEDGE from
the target BSS to the MSC
Class : handover

411--9001--125
Precise
calls:
l
1073 Number of successful incoming intra--bss handovers on TCH
Name Q3 : hoSuccessIncomingIntraBss
Object : bts
Function : number of successful incoming intra-bss handovers on TCH in the
cell
Class : handover
Precise
calls:
l
1074 Number of successful incoming inter--bss handovers on TCH
Name Q3 : hoSuccessIncomingInterBss
Object : bts
Function : number of successful incoming inter-bss handovers on TCH


Class : handover
Precise
calls:
l
1075 Number of outgoing intra--bss handovers on TCH requested
Name Q3 : hoRequestOutgoingIntraBss
Object : bts
Function : number of outgoing intra-bss handover requests on TCH
Event : attempt to select a target cell in the list of eligible cells provided by the
handover algorithm
Class : handover
Precise
calls:

411--9001--125
l
1076 Number of outgoing inter--bss handovers on TCH requested
Name Q3 : hoRequestOutgoingInterBss
Object : bts
Function : number of outgoing inter-bss handover requests on TCH in the cell
Event : attempt to select a target cell in the list of eligible cells on transmission
of HANDOVER REQUIRED on the A interface
Class : handover
Precise
calls:
l
1077 Number of successful outgoing intra--bss handovers on TCH
after first attempt
Name Q3 : hoSuccessOutgoingFirstIntra
Object : bts
Function : number of successful outgoing intra-bss handovers on TCH to the first
cell from the list of eligible cells
Class : handover
Precise
calls:


Note : the list is reorganized by the BSC Ho decision according to the cell
priority feature (TF716). It may not be the same order as the one
received from the L1M.
l
1078 Number of successful outgoing inter--bss handovers on TCH after
first attempt
Name Q3 : hoSuccessOutgoingFirstInter
Object : bts
Function : number of successful outgoing inter-bss handovers on TCH to the first
cell from the list of eligible cells
Event : receipt of CLEAR COMMAND from the MSC with cause “Handover
Successful”
Class : handover
Precise
calls:
Note : the list is reorganized by the BSC Ho decision according to the cell
received from the L1M.

411--9001--125
l
1081 Number of intra-bts handovers on TCH requested
Name Q3 : hoRequestIntraBts
Object : bts
Function : number of intra-bts handovers on TCH requested in the cell
Event : transmission of HANDOVER INDICATION
Class : handover
Precise
calls:
l
1082 Number of intra-bts handovers on TCH executed
Name Q3 : hoExecutionIntraBts
Object : bts
Function : number of attempts to execute intra-bts handovers on TCH in the cell
Event : transmission of ASSIGN COMMAND to the cell during the intra-bts
handover procedure
Class : handover
Precise
calls:

l
1083 Number of successful intra-bts handovers on TCH
Name Q3 : hoSuccessIntraBts
Object : bts
Function : number of successful intra-bts handovers on TCH in the cell
Event : receipt of ASSIGN COMPLETE from the cell during the intra-bts
handover procedure
Class : handover
Note : This counter is the sum of the 1073 and 1077 counters.
Precise
calls:
l
1094 Number of terrestrial circuits allocated
Name Q3 : tcAllocated
Object : bsc
Function : number of terrestrial circuit allocations (CIC) in the BSC
Event : allocation of a terrestrial circuit
Class : A interface
Precise
calls:

411--9001--125

DFD “GPRS procedure (no resource available for a PDTCH
preemption)”
completion)”
DFD “dedicated channel assignment procedure (no resource
available and queuing not activated)”
completion)”
1095 Average number of terrestrial circuits used

Name Q3 : tcAveragedUsedMoy . . . . Average terrestrial circuits allocated
tcAveragedUsedMax . . . . Max terrestrial circuits allocated
tcAveragedUsedCum . . . . Total terrestrial circuits allocated
tcAveragedUsedEch . . . . . Number of samples
Object : bsc
Function : average (= total number divided by number of samples) and
maximum number of terrestrial circuits (CIC) allocated in the BSC,
obtained through internal sampling
Event : terrestrial circuit allocation/deallocation, internal sampling time-out
elapse:
allocation: step up by one the instantaneous value of terrestrial
circuits allocated
deallocation: step down by one the instantaneous value of
terrestrial circuits allocated
sampling time-out elapse:
• read the instantaneous value of circuits allocated
• add it to the total of allocated circuits for the observation period
Class : A interface

Precise
calls:
preemption)”
completion)”
phase)”
completion)”
DFD “Radio channel release RELEASE INDICATION procedure
(normal completion)”
(communication on TRAFFIC phase)”
l
1104/0 Number of SCCP connections established for SSN BSSMAP
Name Q3 : sccpAllocated
Object : bsc
Function : number of SCCP connections for SSN BSSMAP in the BSC
Event : successful SCCP connection request
Class : A interface

411--9001--125
Precise
This counter is concerned by the following calls:
completion)”
DFD “Immediate assignment procedure (normal completion)”
DFD “Immediate assignment paging procedure (normal
completion)”
completion)”
DFD “SMS procedure (SMS established by the MS)”
l
1104/1 Number of SCCP connections established for SSN LCS
Name Q3 : sccpAllocatedLcs
Object : bsc
Function : number of SCCP connections for SSN LCS in the BSC
Event : successful SCCP connection request
Class : A interface
Precise
This counter is concerned by the location procedure beginning, for
BSS hybrid solution.

l
1105 Average number of SCCP connections established
Name Q3 : sccpAveragedUsedMoy . . Average SCCP connections established
sccpAveragedUsedMax . . Max SCCP connections established
sccpAveragedUsedCum . . Total SCCP connections established
sccpAveragedUsedEch . . . Number of samples
Object : bsc
maximum number of SCCP connections established in the BSC,
obtained through internal sampling.
Event : SCCP connection establishment/release, internal sampling time-out
elapse:
establishment: step up by one the instantaneous value of SCCP
connections established
release: step down by one the instantaneous value of SCCP
connections established
• read the instantaneous value of SCCP connections established
• add it to the total number of SCCP connections established for
Class : A interface
Precise
calls:

411--9001--125

(normal completion with communication on TRAFFIC phase)”
phase)”
completion)”
completion)”
DFD “Radio channel release DEACTIVATE SACCH ACK
procedure (normal completion)”
l
1106/0 Number of SCCP connections refused by the MSC or the local
SCCP layer
Name Q3 : sccpRessourceFailure
Object : bsc
Function : number of SCCP connection establishments refused by the MSC or
the local SCCP layer
Event : SCCP connection establishment refusal due to the following causes:
BSC request refused by local SCCP layer
BSC request refused by the MSC
Class : A interface

Precise
calls:
l
1106/1 Number of SCCP connections refused by the BSC
Name Q3 : sccpRessourceFailureBscRefusal
Object : bsc
Function : number of SCCP connection establishments refused
Event : SCCP connection establishment refusal due to the following causes:
MSC request refused by the BSC
Class : A interface
Precise
calls:
l
1106/2 Number of SCCP connections with SSN LCS, refused by the
MSC or the local SCCP layer
Name Q3 : sccpRessourceFailureLcs
Object : bsc
Function : number of SCCP connections with SSN LCS, refused by the MSC or
the local SCCP layer
Event : SCCP connection establishment (with SSN LCS) refusal due to the
following causes:
BSC request refused by local SCCP layer
BSC request refused by the MSC
Class : A interface

411--9001--125
Precise
l
1106/3 Number of SCCP connections with SSN LCS, refused by the BSC
Name Q3 : sccpRessourceFailureBscRefusalLcs
Object : bsc
Function : number of SCCP connections with SSN LCS refused by the BSC
Event : SCCP connection establishment (with SSN LCS) refusal due to the
following causes:
MSC request refused by the BSC
Class : A interface
Precise
l
1107 Number of BSSAP messages received
Name Q3 : aInputMessage
Object : bsc
Function : number of BSSAP messages received by the BSC
Event : receipt of SCCP CONNECTION REQUEST, or SCCP DATA
REQUEST, or SCCP UNIT DATA REQUEST message
Class : A interface
Precise
calls:


completion)”
preemption)”
completion)”
DFD “dedicated channel assignment procedure (no Resource
phase)”
completion)”
DFD “SMS procedure (SMS established by the MSC)”
l
1108 Number of BSSAP messages sent
Name Q3 : aOutputMessage
Object : bsc
Function : number of BSSAP messages sent by the BSC
Event : transmission of SCCP CONNECTION REQUEST, or SCCP DATA
REQUEST, or SCCP UNIT DATA REQUEST message
Class : A interface

411--9001--125
Precise
calls:
completion)”
preemption)”
completion)”
phase)”
completion)”

l
1109 Number of erroneous BSSAP messages received
Name Q3 : aMessageErrors
Object : bsc
Function : number of errored BSSAP messages received by the BSC at
application level
Event : receipt of SCCP CONNECTION INDICATION, or SCCP DATA
INDICATION, or SCCP UNIT DATA INDICATION, with incorrect
format
Class : A interface
Precise
calls:
l
1134 Number of unsuccessful intra-bts handovers on TCH for which
the communication has been re--established on starting channel
Name Q3 : hoUnsuccessReestIntraBtsTch
Object : bts
Function : number of unsuccessful intra-bts handovers on TCH for which the
communication has been re--established on starting channel
Event : receipt of ASSIGN FAILURE before T3107 time-out elapse
Class : handover

411--9001--125
Precise
calls:
l
1135 Number of unsuccessful outgoing intra--bss handovers on TCH
for which the communication has been re--established on starting
channel
Name Q3 : hoUnsuccessReestOutgoingIntraBssTch
Object : bts
Function : number of unsuccessful outgoing intra-bss handovers for which the
Event : receipt of HANDOVER FAILURE before T3103 time-out elapse
Class : handover
Precise
calls:
l
1136 Number of unsuccessful outgoing inter--bss handovers on TCH
for which the communication has been re--established on starting
channel
Name Q3 : hoUnsuccessReestOutgoingInterBssTch
Object : bts
Function : number of unsuccessful outgoing inter-bss handovers on TCH for
which the communication has been re--established on starting channel


(T3103 < bssMapT8) with transmission to the MSC
Class : handover
Precise
calls:
l
1137 Number of unsuccessful incoming intra--bss handovers on TCH
with reestablishment in the serving cell
Name Q3 : hoUnsuccessReestIncomingIntraBssTch
Object : bts
Function : number of unsuccessful incoming intra-bss handovers on TCH with
call reestablishment in the cell
Event : receipt of HANDOVER FAILURE
Class : handover
Precise
calls:
l
1138/0 Number of handovers on TCH required: Loss of Uplink power
Name Q3 : hoRequiredTchUplinkStrength
Object : bts
Function : number of handovers on TCH required because of loss of Uplink
power (MS-to-BTS direction)

411--9001--125
Event : receipt of HANDOVER INDICATION (internal message) with

cause “uplink signal strength” from the L1M
Class : handover
Precise
calls:
l
1138/1 Number of handovers on TCH required: Loss of Downlink power
Name Q3 : hoRequiredTchDownlinkStrength
Object : bts
Function : number of handovers on TCH required because of loss of Downlink
power (BTS-to-MS direction)
Event : receipt of HANDOVER INDICATION (internal message) with cause
“downlink signal strength” from the L1M
Class : handover
Precise
calls:


l
1138/2 Number of handovers on TCH required: Loss of Uplink quality
Name Q3 : hoRequiredTchUplinkQuality
Object : bts
Function : number of handovers on TCH required because of loss of Uplink
quality (MS-to-BTS direction)
“uplink signal quality” from the L1M
Class : handover
Precise
calls:
l
1138/3 Number of handovers on TCH required: Loss of Downlink
quality
Name Q3 : hoRequiredTchDownlinkQuality
Object : bts
Function : number of handovers on TCH required because of loss of Downlink
quality (BTS-to-MS direction)

411--9001--125

“downlink signal quality” from the L1M
Class : handover
Precise
calls:
l
1138/4 Number of handovers on TCH required: Distance
Name Q3 : hoRequiredTchDistance
Object : bts
Function : number of handovers on TCH required because of distance
“distance” from the L1M
Class : handover
Precise
calls:


l
1138/5 Number of handovers on TCH required: Power budget
Name Q3 : hoRequiredTchPowerBudgetQuality
Object : bts
Function : number of handovers on TCH required because of power budget
“power budget” from the L1M
Class : handover
Precise
calls:
l
1138/6 Number of handovers on TCH required: Microcell capture
Name Q3 : hoRequiredTchCapture
Object : bts
Function : number of handovers on TCH required because of microcell capture

411--9001--125

“microcell capture” from the L1M
Class : handover
Precise
calls:
l
1138/7 Number of intra-bts handovers on TCH required: TRX out of
service O&M
Name Q3 : hoRequiredTchIntraBtsOm
Object : bts
Function : number of intra-bts handovers on TCH required because of a
TRX/DRX taken out of service (O&M action)
Event : receipt of HANDOVER INDICATION (internal message) with
cause “TRX out of service” from the L1M
Class : handover
Precise
calls:


l
1138/8 Number of intra-bts handovers on TCH required: Loss of Uplink
quality
Name Q3 : hoRequiredTchIntraBtsUplink
Object : bts
Function : number of intra-bts handovers on TCH required because of loss of
Uplink quality (MS-to-BTS direction)
Class : handover
Precise
calls:

411--9001--125
l
1138/9 Number of intra-bts handovers on TCH required: Loss of
Downlink quality
Name Q3 : hoRequiredTchIntraBtsDownlink
Object : bts
Function : number of intra-bts handovers on TCH required because of loss of
Downlink quality (BTS-to-MS direction)
Class : handover
Precise
calls:
l
1138/10 Number of directed retry handovers on TCH required
Name Q3 : hoRequiredTchDirectedRetry
Object : bts
Function : number of directed retry handovers on TCH required
Event : receipt of HANDOVER INDICATION (internal message) attempt of
directed retry: receipt of CONNECTION REQUEST ACK message
or autonomously in case of directed retry from a micro--cell receipt of
a CONNECTION REQUEST ACK with an eligible cells list, after
Tchoke expiry
Class : handover

Precise
calls:
l
1138/11 intra--cell handover into a class 0 TDMA for downlink power
level or distance, for a multi--class cell (concentric cell...) (only for
HO_REQUIRED_TCH)
Name Q3 : hoRequiredTchTdmaClass0
Object : bts (concentric cell)
Function : TDMA_class_0: intra--cell handover into a class 0 TDMA for
downlink power level or distance, for a multi--class cell (concentric
cell...) (only for HO_REQUIRED_TCH)
downlink power level or distance reason from the L1M
Class : handover
Precise
calls:

411--9001--125

l
1138/12 Number of intra-bts handovers on TCH required (concentric
cell): Class 1 TDMA
Name Q3 : hoRequiredTchTdmaClass1
Object : bts (concentric cell)
Function : number of intra-bts handovers on TCH from the outer zone to the
inner zone required in the serving cell
downlink power level or distance reason from the L1M
Class : handover
Precise
calls:
l
1138/13 Number of handovers on TCH required: Forced handover O&M
Name Q3 : hoRequiredTchInterBtsOm
Object : bts
Function : number of handovers on TCH forced towards the neighbor cells of the
serving cell


“forced handover” from the L1M
Class : handover
Precise
calls:
l
1138/14 Number of handovers on TCH required: Traffic
Name Q3 : hoRequiredTchTraffic
Object : bts
Function : number of handovers on TCH forced towards the neighbor cells of the
serving cell
“traffic” from the L1M
Class : handover
Precise
calls:

411--9001--125

Feature : Handover for traffic reasons (TF132 - V12)
l
1138/15 Number of handovers on TCH required: Tiering handover from
large pattern to small pattern
Name Q3 : hoRequiredTchTieringLargeToSmallPattern
Object : bts
Function : number of tiering handovers on TCH from large pattern to small
pattern (non--hopping channel to hopping channel)
“tiering handover from large pattern to small pattern” from the L1M
Class : handover
Precise
calls:
Feature : Cell Tiering (TF995 - V12)

l
1138/16 Number of handovers on TCH required: Tiering handover from
small pattern to large pattern
Name Q3 : hoRequiredTchTieringSmallToLargePattern
Object : bts
Function : number of tiering handovers on TCH from small pattern to large
pattern (hopping channel to non--hopping channel)
“tiering handover from large small to large pattern” from the L1M
Class : handover
Precise
calls:
l
1139/0 Number of handovers on SDCCH required: Loss of Uplink power
Name Q3 : hoRequiredSdcchUplinkStrength
Object : bts
Function : number of handovers on SDCCH required because of loss of Uplink
power (MS-to-BTS direction)
“uplink signal strength” from the L1M
Class : handover

411--9001--125
Precise
calls:
l
1139/1 Number of handovers on SDCCH required: Loss of Downlink
power
Name Q3 : hoRequiredSdcchDownlinkStrength
Object : bts
Function : number of handovers on SDCCH required because of loss of
Downlink power (BTS-to-MS direction)
“downlink signal strength” from the L1M
Class : handover
Precise
calls:
l
1139/2 Number of handovers on SDCCH required: Loss of Uplink
quality
Name Q3 : hoRequiredSdcchUplinkQuality
Object : bts
Function : number of handovers on SDCCH required because of loss of Uplink
quality (MS-to-BTS direction)
Class : handover

Precise
calls:
l
1139/3 Number of handovers on SDCCH required: Loss of Downlink
quality
Name Q3 : hoRequiredSdcchDownlinkQuality
Object : bts
Function : number of handovers on SDCCH required because of loss of
Class : handover
Precise
calls:
l
1139/4 Number of handovers on SDCCH required: Distance
Name Q3 : hoRequiredSdcchDistance
Object : bts
Function : number of handovers on SDCCH required because of distance
“distance” from the L1M
Class : handover

411--9001--125
Precise
calls:
l
1139/5 Number of handovers on SDCCH required: Power budget
Name Q3 : hoRequiredSdcchPowerBudget
Object : bts
Function : number of handovers on SDCCH required because of power budget
“power budget” from the L1M
Class : handover
Precise
calls:
l
1139/6 Number of handovers on SDCCH required: Microcell capture
Name Q3 : hoRequiredSdcchCapture
Object : bts
Function : number of handovers on SDCCH required because of microcell
capture
“microcell capture” from the L1M
Class : handover

Precise
calls:
l
1139/7 Number of intra-bts handovers on SDCCH required: TRX out of
service O&M
Name Q3 : hoRequiredSdcchIntraBtsOm
Object : bts
Function : number of intra-bts handovers on SDCCH required because of a
TRX/DRX taken out of service (O&M action)
“TRX out of service” from the L1M
Class : handover
Precise
calls:
l
1139/8 Number of intra-bts handovers on SDCCH required: Loss of
Uplink quality
Name Q3 : hoRequiredSdcchIntraBtsUplink
Object : bts
Function : number of intra-bts handovers on SDCCH required because of loss of
Uplink quality (MS-to-BTS direction)
Class : handover

411--9001--125
Precise
calls:
l
1139/9 Number of intra-bts handovers on SDCCH required: Loss of
Downlink quality
Name Q3 : hoRequiredSdcchIntraBtsDownlink
Object : bts
Function : number of intra-bts handovers on SDCCH required because of loss of
Class : handover
Precise
calls:
l
1139/13 Number of handovers on SDCCH required: Forced handover
O&M
Name Q3 : hoRequiredSdcchInterBtsOm
Object : bts
Function : number of handovers on SDCCH forced towards the neighbor cells of
the serving cell
“forced handover” from the L1M
Class : handover

Precise
calls:
l
1139/14 Number of handovers on SDCCH required: Traffic
Name Q3 : hoRequiredSdcchTraffic
Object : bts
Function : number of handovers on SDCCH forced towards the neighbor cells of
the serving cell
“traffic” from the L1M
Class : handover
Precise
calls:
l
1140 Number of outgoing intra--bss handovers on SDCCH executed
Name Q3 : hoExecutionOutgoingIntraBssSdcch
Object : bts
Function : number of attempts to execute outgoing intra-bss handovers on
SDCCH
Class : handover

411--9001--125
Precise
calls:
l
1141 Number of outgoing inter handovers on SDCCH executed
Name Q3 : hoExecutionOutgoingInterBssSdcch
Object : bts
Function : number of attempts to execute outgoing inter-bss handovers on
SDCCH
Event : receipt of HANDOVER COMMAND from the MSC
Class : handover
Precise
calls:
l
1142 Number of successful outgoing intra--bss handovers on SDCCH
Name Q3 : hoSuccessOutgoingIntraBssSdcch
Object : bts
Function : number of successful attempts to execute outgoing intra-bss
handovers on SDCCH
Class : handover

Precise
calls:
l
1143 Number of successful outgoing inter--bss handovers on SDCCH
Name Q3 : hoSuccessOutgoingInterBssSdcch
Object : bts
Function : number of successful outgoing inter-bss handovers on SDCCH
Event : receipt of CLEAR COMMAND with cause “ Handover Successful ”
from the MSC
Class : handover
Precise
calls:
l
1144 Number of incoming intra--bss handovers on SDCCH requested
Name Q3 : hoRequestIncomingIntraBssSdcch
Object : bts
Function : number of incoming intra-bss handovers on SDCCH requested in the
cell for any kind of the mobile
Event : attempt to select the cell as the serving cell
Class : handover

411--9001--125
Precise
calls:
l
1145 Number of incoming inter--bss handovers on SDCCH requested
Name Q3 : hoRequestIncomingInterBssSdcch
Object : bts
Function : number of incoming inter-bss handovers on SDCCH requested
Event : receipt of HANDOVER REQUEST from the MSC on the A interface
Class : handover
Precise
calls:
l
1146 Number of incoming intra--bss handovers on SDCCH execution
attempt
Name Q3 : hoExecutionIncomingIntraBssSdcch
Object : bts
Function : number of attempts to execute incoming intra-bss handovers on
SDCCH in the cell for any kind of the mobile
Class : handover

Precise
calls:
l
1147 Number of incoming inter--bss handovers on SDCCH executed
Name Q3 : hoExecutionIncomingInterBssSdcch
Object : bts
Function : number of attempts to execute incoming inter-bss handovers on
SDCCH
Event : transmission of HANDOVER REQUEST ACKNOWLEDGE from
the target BSS to the MSC
Class : handover
Precise
calls:
l
1148 Number of successful incoming intra--bss handovers on SDCCH
Name Q3 : hoSuccessIncomingIntraBssSdcch
Object : bts
Function : number of successful incoming intra-bss handovers on SDCCH in the
cell
Class : handover

411--9001--125
Precise
calls:
l
1149 Number of successful incoming inter--bss handovers on SDCCH
Name Q3 : hoSuccessIncomingInterBssSdcch
Object : bts
Function : number of successful incoming inter-bss handovers on SDCCH
Class : handover
Precise
calls:
l
1150 Number of outgoing intra--bss handovers on SDCCH requested
Name Q3 : hoRequestOutgoingIntraBssSdcch
Object : bts
Function : number of outgoing intra-bss handovers on SDCCH requested
Event : attempt to select a target cell from the list of eligible cells sent by the
handover algorithm
Class : handover

Precise
calls:
l
1151 Number of outgoing inter--bss handovers on SDCCH requested
Name Q3 : hoRequestOutgoingInterBssSdcch
Object : bts
Function : number of outgoing inter-bss handovers on SDCCH requested
Event : attempt to select a cell in the list of eligible cells on transmission of
HANDOVER REQUIRED on the A interface
Class : handover
Precise
calls:
l
1152 Number of successful outgoing intra--bss handovers on SDCCH
after first attempt
Name Q3 : hoSuccessOutgoingFirstIntraSdcch
Object : bts
Function : number of successful outgoing intra-bss handovers on SDCCH to the
Class : handover

411--9001--125
Precise
calls:
Note : the list is reorganized by the BSC Ho decision according tot he cell
received from the L1M
l
1153 Number of successful outgoing inter--bss handovers on SDCCH
after first attempt
Name Q3 : hoSuccessOutgoingFirstInterSdcch
Object : bts
Function : number of successful outgoing inter-bss handovers on SDCCH to the
Event : receipt of CLEAR COMMAND with cause “Handover Successful”
from the MSC
Class : handover
Precise
calls:
Note : the list is reorganized by the BSC Ho decision according tot he cell
received from the L1M
l
1154 Number of intra-bts handovers on SDCCH requested
Name Q3 : hoRequestIntraBtsSdcch
Object : bts
Function : number of intra-bts handovers on SDCCH requested in the cell

Event : attempt to select the cell to accommodate an intra-bts handover

Class : handover
Precise
calls:
l
1155 Number of intra-bts handovers on SDCCH executed
Name Q3 : hoExecutionIntraBtsSdcch
Object : bts
Function : number of attempts to execute intra-bts handovers on SDCCH in the
cell
Event : transmission of ASSIGN COMMAND to the cell during the intra-bts
handover procedure
Class : handover
Precise
calls:
l
1156 Number of successful intra-bts handovers on SDCCH
Name Q3 : hoSuccessIntraBtsSdcch
Object : bts
Function : number of successful intra-bts handovers on SDCCH in the cell

411--9001--125
Event : receipt of ASSIGN COMPLETE from the cell during the intra-bts
handover procedure
Class : handover
Precise
calls:
l
1157 Number of unsuccessful intra-bts handovers on SDCCH for
which the communication has been re--established on starting
channel
Name Q3 : hoUnsuccessReestIntraBtsSdcch
Object : bts
Function : number of unsuccessful intra-bts handovers on SDCCH for which the
Event : receipt of ASSIGN FAILURE before T3107 time-out elapse
Class : handover
Precise
calls:

l
1158 Number of unsuccessful outgoing intra--bss handovers on
SDCCH for which the communication has been re--established
on starting channel
Name Q3 : hoUnsuccessReestOutgoingIntraBssSdcch
Object : bts
Function : number of unsuccessful outgoing intra-bss handovers on SDCCH for
Class : handover
Precise
calls:
l
1159 Number of unsuccessful outgoing inter--bss handovers on
on starting channel
Name Q3 : hoUnsuccessReestOutgoingInterBssSdcch
Object : bts
Function : number of unsuccessful outgoing inter-bss handovers on SDCCH for
(T3103 < bssMapT8) with transmission to the MSC
Class : handover

411--9001--125
Precise
calls:
l
1160 Number of unsuccessful incoming intra--bss handovers on
on starting channel
Name Q3 : hoUnsuccessReestIncomingIntraBssSdcch
Object : bts
Function : number of unsuccessful incoming intra-bss handovers on SDCCH for
Event : receipt of HANDOVER FAILURE
Class : handover
Precise
calls:
l
1161/0 Number of immediate assignments rejected: Traffic with MSC
interrupted
Name Q3 : immediateAssignmentRejectTraffMsc
Object : bts
Function : number of immediate assignments rejected because the traffic with
the MSC is interrupted
Event : transmission of IMMEDIATE ASSIGN REJECT to a mobile on
transmission or receipt of RESET by the MSC
Class : release

Precise
calls:
l
1161/1 Number of immediate assignments rejected: Lack of radio
resource
Name Q3 : immediateAssignmentRejectRadioRes
Object : bts
Function : number of immediate assignments rejected for lack of radio resources
Event : transmission of IMMEDIATE ASSIGN REJECT to a mobile due to a
lack of radio resource
Class : release
Precise
calls:
l
1161/2 Number of immediate assignments rejected: CHANNEL
ACTIVATE NACK received
Name Q3 : immediateAssignmentRejectChanActNack
Object : bts
Function : number of immediate assignments rejected because a CHANNEL
ACTIVATE NACK message is received
receipt of CHANNEL ACTIVATE NACK from the BTS
Class : release

411--9001--125
Precise
calls:
l
1161/3 Number of immediate assignments rejected: Time-out elapse
Name Q3 : immediateAssignmentRejectChanActTimmack
Object : bts
Function : number of immediate assignments rejected because of TimmAck
time-out elapse
TchnAck time-out elapse
Class : release
Precise
calls:
l
1161/5 Number of immediate assignments rejected: Traffic overload
Name Q3 : immediateAssignmentRejectOverload
Object : bts
Function : number of immediate assignments rejected for overload reasons
Event : transmission of IMMEDIATE ASSIGN REJECT to a mobile because
a call originating from a mobile (MOC) or a Mobile Terminating Call
(MTC) is blocked by the BSC for traffic management general
overload
Class : release

Precise
calls:
l
1161/6 Number of immediate assignments rejected: Excessive timing
advance
Name Q3 : immediateAssignmentRejectTimingAdv
Object : bts
Function : number of immediate assignments rejected for distance reasons
Event : receipt of CHANNEL REQUIRED with a timing advance value
above the O&M threshold (no IMMEDIATE ASSIGN REJECT is
sent to the mobile)
Class : release
Precise
calls:
l
1161/7 Number of immediate assignments rejected: Other cases
Name Q3 : immediateAssignmentRejectOthers
Object : bts
Function : number of immediate assignments rejected for other reasons
Event : transmission of IMMEDIATE ASSIGN REJECT to a mobile for
another reason
Class : release

411--9001--125
Precise
calls:
l
1162/0 Number of SCCP releases before HANDOVER REQUEST
acknowledging: SCCP disconnection
Name Q3 : signallingReleaseNoBtsSccpDiscInd
Object : bsc
Function : number of communications in signaling phase released before
HANDOVER REQUEST ACKNOWLEDGE is received in the
incoming handover procedure, because of SCCP disconnection
Event : receipt of SCCP DISCONNECTION INDICATION from the MSC
Class : release
Precise
calls:
Note : This counter is only incremented in case of incoming external
handovers.
l
acknowledging: Reset
Name Q3 : signallingReleaseNoBtsReset
Object : bsc
incoming handover procedure, because of reset

Event : receipt of RESET from the MSC

Class : release
Precise
calls:
handovers.
l
acknowledging: SCCP DATA REFUSAL received
Name Q3 : signallingReleaseNoBtsSccpDataRefusal
Object : bsc
incoming handover procedure, because of SCCP data refusal
Event : receipt of SCCP DATA REFUSAL from the MSC
Class : release
Precise
calls:
handovers.

411--9001--125
l
acknowledging: TsccRel elapse
Name Q3 : signallingReleaseNoBtsTsccRel
Object : bsc
incoming handover procedure, because of TsccRel time-out elapse
Event : TsccRel time-out elapse
Class : release
Precise
calls:
handovers.
l
acknowledging: Incorrect DATA INDICATION received
Name Q3 : signallingReleaseNoBtsBadDataInd
Object : bsc
incoming handover procedure, because of incorrect DATA
INDICATION message received
Event : receipt of DATA INDICATION other than HANDOVER REQUEST
after receipt of SCCP CONNECTION INDICATION
Class : release

Precise
calls:
handovers.
l
acknowledging: Other cases
Name Q3 : signallingReleaseNoBtsOthers
Object : bsc
incoming handover procedure for other reasons
Event : call in signaling phase released for another reason
Class : release
Precise
calls:
handovers.
l
1163/0 Number of communications in signaling phase released: SCCP
disconnection
Name Q3 : signallingReleaseBtsSccpDiscInd
Object : bts
Function : number of communications in signaling phase released because of
SCCP disconnection when a cell is associated with the
communication

411--9001--125

Class : release
Precise
calls:
l
1163/1 Number of communications in signaling phase released: Reset
Name Q3 : signallingReleaseBtsReset
Object : bts
reset when a cell is associated with the communication
Class : release
Precise
calls:
l
1163/2 Number of communications in signaling phase released: Reset
circuit downlink
Name Q3 : signallingReleaseBtsResetCirc
Object : bts
reset circuit in the Downlink direction when a cell is associated with
the communication

Event : receipt of RESET CIRCUIT DOWNLINK from the MSC

Class : release
Precise
calls:
l
1163/3 Number of communications in signaling phase released: SCCP
DATA REFUSAL received
Name Q3 : signallingReleaseBtsSccpDataRefusal
Object : bts
SCCP data refusal when a cell is associated with the communication
Class : release
Precise
calls:
l
1163/4 Number of communications in signaling phase released:
Incorrect First L3 Msg
Name Q3 : signallingReleaseBtsIncFirstL3
Object : bts
incorrect First L3 message when a cell is associated with the
communication

411--9001--125
Event : incorrect syntax of a First L3 message or message different from CM

SERVING REQUEST, PAGING RESPONSE, LOCATION
UPDATING REQUEST, CM REESTABLISHMENT REQUEST, or
IMSI DETACH
Class : release
Precise
calls:
l
1163/5 Number of communications in signaling phase released: T3101
elapse
Name Q3 : signallingReleaseBtsT3101
Object : bts
T3101 time-out elapse when a cell is associated with the
communication
Event : T3101 time-out elapse before ESTABLISH INDICATION is
received in the immediate assignment procedure
Class : release
Precise
calls:

l
elapse
Name Q3 : signallingReleaseBtsT3107CircDown
Object : bts
T3107 time-out elapse when a cell is associated with the
communication
Event : T3107 time-out elapse before ESTABLISH INDICATION is
received in the dedicated channel assignment or intra-bts handover on
SDCCH procedure
Class : release
Precise
calls:
l
1163/7 Number of communications in signaling phase released: Ts out of
service (O&M)
Name Q3 : signallingReleaseBtsOmTsRemoval
Object : bts
Function : number of communications in signaling phase released because the
associated with the call is taken out of service
Event : radio time slot withdrawal due to the cell being taken out of service
Class : release

411--9001--125
Precise
calls:
l
1163/8 Number of communications in signaling phase released: Ts out of
service (faulty equipment)
Name Q3 : signallingReleaseBtsTsRemovalEqptFail
Object : bts
Function : number of communications in signaling phase released because of a
faulty equipment when a cell is associated with the call
Event : radio time slot withdrawal due to a faulty equipment (PCM, etc.)
Class : release
Precise
calls:
l
1163/9 Number of communications in signaling phase released: CIC out
of service (O&M)
Name Q3 : signallingReleaseBtsOmCicRemoval
Object : bts
Function : number of communications in signaling phase released because a
terrestrial circuit is taken out of service when a cell is associated with
the communication
Event : CIC withdrawal due to the terrestrial circuit being taken out of service
Class : release

Precise
calls:
l
1163/10 Number of communications in signaling phase released: CIC out
of service (faulty equipment)
Name Q3 : signallingReleaseBtsCicRemovalEqptFail
Object : bts
faulty equipment when a cell is associated with the communication
Event : CIC withdrawal due to a faulty equipment (PCM, etc.)
Class : release
Precise
calls:
l
1163/11 Number of communications in signaling phase released: Radio
channel blocked (O&M)
Name Q3 : signallingReleaseBtsOmRadioChanBloc
Object : bts
radio channel blocking when a cell is associated with the
communication
Event : radio channel blocking by O&M action
Class : release

411--9001--125
Precise
calls:
l
1163/12 Number of communications in signaling phase released: CALL
CLEARING received
Name Q3 : signallingReleaseBtsCallClearing
Object : bts
call clearing when a cell is associated with the communication
Event : receipt of CALL CLEARING because the maximum authorized
distance is exceeded
Class : release
Precise
calls:
l
interface failure
Name Q3 : signallingReleaseBtsCnxFailRadioIntFail
Object : bts
radio interface failures when a cell is associated with the
communication

Event : receipt of CONNECTION FAILURE INDICATION with Abis cause

“radio interface failure”
Class : release
Precise
calls:
l
link failure
Name Q3 : signallingReleaseBtsCnxFailRadioLinkFail
Object : bts
radio link failures when a cell is associated with the communication
“radio link failure”
Class : release
Precise
calls:

411--9001--125

RELEASE INDICATION received
Name Q3 : signallingReleaseBtsReleaseInd
Object : bts

RELEASE INDICATION received when a cell is associated with the
communication
Event : receipt of RELEASE INDICATION from the BTS
Class : release
Precise
This counter is incremented when the BSC receives a RELEASE
INDICATION on a channel and the channel is not in a release phase.
That means that on A interface, no disconnection has been started (no
CLEAR COMMAND received nor SCCP disconnection).
The RELEASE INDICATION message sent by the BTS is due to the
reception of a DISC frame (LAPDm message) by the BTS from the
mobile (MS).
In the Nortel Networks implementation:
At the BTS level, each time a LAPDm DISC frame is received by the
BTS, a message RELEASE INDICATION is sent by the BTS to the
BSC, unless the link layer is in idle mode (as indicated in
recommendation 08.58).
At the BSC level, in normal release scenario, the counter 1163/16 is
not incremented. In all other cases, the counter 1163/16 is
incremented.
So, the counter C1163/16 takes into account each RELEASE
INDICATION message sent on the SDCCH channel from the BTS
when the BSC is in a state where it has not send to this BTS a RR
CHANNEL RELEASE (triggered by the reception of BSSMAP
CLEAR COMMAND from the MSC).

Precise
calls:
Exception conditions : channel in a release phase
Data flows : The following data flow presents the links between signalling
messages exchanged at CM level (between the MSC and the MS),
when the release is initiated by the MS:
MS BSS NSS
CC DISCONNECT
CC RELEASE
CC RELEASE COMPLETE

411--9001--125
As a comparison, the following data flow presents the links between

signalling messages exchanged at RR level (between the BSS and the
mobile) in normal release scenario:
MS BTS BSC MSC
BSSMAP CLEAR COMMAND

RR CHANNEL RELEASE
DESACTIVATE SACCH
DESACTIVATE SACCH ACK
DISK
RELEASE INDICATION
UA
RF CHANNEL RELEASE
BSSMAP CLEAR COMPLETE
RF CHANNEL RELEASE ACKNOWLEDGE
SCCP RELEASED
SCCP RELEASE COMPLETED
l
elapse
Name Q3 : signallingReleaseBtsErrorIndT200
Object : bts
T200 time-out elapse in the cell associated with the communication
Event : receipt of ERROR INDICATION: T200 elapsed (N200 + 1) times
Class : release

Precise
This counter is related to the Layer2 LAPDm protocol (error
detection + repetition protocol between the BTS and the mobile
(MS)).
When a Layer 2 frame is not acknowledged by the MS before T200
expiration, the BTS sends an Error indication message to the BSC.
After (N200+1) Error indication consecutive messages received for
a call in signaling phase, the BSC increments by one the counter
1163/17.
calls:
Data flows : The dataflow below presents an example of Layer 2 LAPDm
exchange. The Level3 messages (measurements reports in SD,
EstInd, SMS, Cyphering, SMS....) are encapsuled in the Layer 2.
MS BTS BSC
SABM
UA
frame1
Ack frame1
frame2
Error indication
T200 expiration
frame2
Error indication
T200 expiration
frame2
Error indication
T200 expiration N200 + 1 error indication + C1163/17
The Layer 2 exchange begins with a exchange of an SABM (Set

Asynchronous Balanced mode) and UA (Unnumbered
Acknowledge) frames.

411--9001--125
The frame1 is acknowledged so it has being received correctly by the

MS and the BTS has received the acknowledgement of that.
The frame2 is not acknowledged either because the MS was not being
able to decode it or because the BTS could not receive the
acknowledgment.
The counter C1163/17 is usually linked to radio bad quality (UL
or DL).
l
1163/18 Number of communications in signaling phase released: DM
error
Name Q3 : signallingReleaseBtsErrorIndDm
Object : bts
DM frames received in established multiframe mode when a cell is
associated with the communication
Event : receipt of ERROR INDICATION: DM frame received in established
multiframe mode
Class : release
Precise
calls:

Sequencing error
Name Q3 : signallingReleaseBtsErrorIndSeq
Object : bts
sequencing errors when a cell is associated with the communication
Event : receipt of ERROR INDICATION: sequencing error
Class : release

Precise
calls:
l
1163/20 Number of communications in signaling phase released: CLEAR
COMMAND received
Name Q3 : signallingReleaseBtsClearCommand
Object : bts
CLEAR COMMAND received when a cell is associated with the
communication
Event : receipt of CLEAR COMMAND from the MSC on normal end of call
or outgoing inter-bss handover
Class : release
Precise
calls:
DFD “Connection clearing required by the MSC procedure
(communication on SIGNALLING phase)”

411--9001--125
l
1163/21 Number of communications in signaling phase released: RF
RESOURCE INDICATION received
Name Q3 : signallingReleaseBtsRfResInd
Object : bts
Function : number of communications in signaling phase released because of RF
RESOURCE INDICATION received when a cell is associated with
the communication
Event : receipt of three RF RESOURCE INDICATION messages
Class : release
Precise
calls:
l
1163/22 Number of communications in signaling phase released: BSC
chain switchover
Name Q3 : signallingReleaseBtsSwitchOver
Object : bts
BSC chain switchovers when a cell is associated with the
communication
Event : BSC chain switchover on receipt of ESTABLISH INDICATION
Class : release
Precise
calls:

l
1163/23 Number of communications in signaling phase released: Double
TmodMs elapse
Name Q3 : signallingReleaseBtsTmodMs
Object : bts
double TmodMs time-out elapse in the CHANNEL MODE MODIFY
procedure when a cell is associated with the communication
Event : double TmodMs time-out elapse
Class : release
Precise
calls:
l
elapse
Object : bts
T3103 time-out elapse in the handover procedure when a cell is
Event : T3103 time-out elapse
Class : release
Precise
calls:

411--9001--125
l
elapse
Object : bts
Function : number of communications in signaling phase released because of T8
time-out elapse in the inter-bss handover procedure when a cell is
Class : release
Precise
calls:
l
1163/28 Number of communications in signaling phase released: Other
cases
Name Q3 : signallingReleaseBtsOthers
Object : bts
Function : number of communications in signaling phase released for other
reasons when a cell is associated with the communication
Event : communication in signaling phase released for another reason
Class : release
Precise
calls:

l
elapse
Object : bts
T11 time-out elapse in the queuing procedure when a cell is associated
with the communication
Event : T11 time-out elapse during the queuing procedure
Class : release
Precise
calls:
l
1163/32 Number of communications in signaling phase released: TCU
failure
Name Q3 : signallingReleaseBtsCnxFailRemTransFail
Object : bts
TCU failure when a cell is associated with the communication
Event : receipt of CONNECTION FAILURE INDICATION with cause
“remote transcoder failure”
Class : release
Precise
calls:

411--9001--125
l
1163/33 Number of releases while the communication is in “signalling”
phase and cell associated to the communication.
Name Q3 : signallingReleaseCellTbcEdge
Object : bts
Function : Number of releases while the communication is in “signalling” phase
and cell associated to the communication.
Event : TDMA removal due to a EDGE TRX/TDMA optimization
Class : release
Precise
calls:
l
1164/0 Number of communications in traffic phase released: SCCP
disconnection
Name Q3 : trafficReleaseSccpDiscInd
Object : bts
Function : number of communications in traffic phase released because of SCCP
disconnection
Class : release
Precise
calls:

l
1164/1 Number of communications in traffic phase released: Reset from
the MSC
Name Q3 : trafficReleaseReset
Object : bts
Function : number of communications in traffic phase released because of reset
from the MSC
Class : release
Precise
calls:
l
1164/2 Number of communications in traffic phase released: Reset
circuit downlink
Name Q3 : trafficReleaseResetCirc
Object : bts
Function : number of communications in traffic phase released because of reset
circuit in the Downlink direction
Event : receipt of RESET CIRCUIT DOWNLINK from the MSC
Class : release
Precise
calls:

411--9001--125
l
1164/3 Number of communications in traffic phase released: SCCP
DATA REFUSAL received
Name Q3 : trafficReleaseSccpDataRefusal
Object : bts
Function : number of communications in traffic phase released because of SCCP
data refusal
Class : release
Precise
calls:
l
1164/6 Number of communications in traffic phase released: T3107
elapse
Name Q3 : trafficReleaseT3107CircDown
Object : bts
Function : number of communications in traffic phase released because of T3107
time-out elapse
Event : T3107 time-out elapse in the traffic establishment procedure
Class : release
Precise
calls:

l
1164/7 Number of communications in traffic phase released: Ts out of
service (O&M)
Name Q3 : trafficReleaseOmTsRemoval
Object : bts
Function : number of communications in traffic phase released because of the
cell being taken out of service
Event : radio time slot withdrawal due to the cell being taken out of service
Class : release
Precise
calls:
l
1164/8 Number of communications in traffic phase released: Ts out of
Name Q3 : trafficReleaseTsRemovalEqptFail
Object : bts
Function : number of communications in traffic phase released because of a
faulty equipment
Event : radio time slot withdrawal due to a faulty equipment (PCM, etc.)
Class : release
Precise
calls:

411--9001--125
l
1164/9 Number of communications in traffic phase released: CIC out of
service (O&M)
Name Q3 : trafficReleaseOmCicRemoval
Object : bts
Function : number of communications in traffic phase released because of a
terrestrial circuit being taken out of service
Event : CIC withdrawal due to the terrestrial circuit being taken out of service
Class : release
Precise
calls:
l
1164/10 Number of communications in traffic phase released: CIC out of
Name Q3 : trafficReleaseCicRemovalEqptFail
Object : bts
Function : To list the number of communications in traffic phase released
because of a faulty equipment. Creating a synthetic counter to work
on a ration, not on absolute values.
Event : CIC withdrawal due to a faulty equipment (PCM, etc.)
Class : release
Precise
calls:

l
1164/11 Number of communications in traffic phase released: Radio
channel blocked (O&M)
Name Q3 : trafficReleaseOmRadioChanBloc
Object : bts
Function : number of communications in traffic phase released because of radio
channel blocking
Event : radio channel blocking by O&M action
Class : release
Precise
calls:
l
1164/12 Number of communications in traffic phase released: CALL
CLEARING received
Name Q3 : trafficReleaseCallClearing
Object : bts
Function : number of communications in traffic phase released because of call
clearing
Event : receipt of a call clearing request
Class : release
Precise
calls:

411--9001--125
l
1164/13 Number of communications in traffic phase released: Radio
interface failure
Name Q3 : trafficReleaseCnxFailRadioIntFail
Object : bts
interface failures
“radio interface failure”
Class : release
Precise
calls:
l
1164/14 Number of communications in traffic phase released: Radio link
failure
Name Q3 : trafficReleaseCnxFailRadioLinkFail
Object : bts
link failures
“radio link failure”
Class : release
Precise
calls:

l
1164/16 Number of communications in traffic phase released: RELEASE
INDICATION received
Name Q3 : trafficReleaseReleaseInd
Object : bts
Function : number of communications in traffic phase released because of
RELEASE INDICATION received
Event : receipt of RELEASE INDICATION from the BTS
Class : release
Precise
This counter is incremented when the BSC receives a RELEASE
INDICATION on a channel and the channel is not in a release phase.
That means that on A interface, no disconnection has been started (no
CLEAR COMMAND received nor SCCP disconnection).
The RELEASE INDICATION message sent by the BTS is due to the
reception of a DISC frame (LAPDm message) by the BTS from the
mobile (MS).
In the Nortel Networks implementation:
At the BTS level, each time a LAPDm DISC frame is received by the
BTS, a message RELEASE INDICATION is sent by the BTS to the
BSC, unless the link layer is in idle mode (as indicated in
recommendation 08.58).
At the BSC level, in normal release scenario, the counter 1164/16 is
not incremented. In all other cases, the counter 1164/16 is
incremented.
So, the counter C1164/16 takes into account each RELEASE
INDICATION message sent on the TCH channel from the BTS when
the BSC is in a state where it has not send to this BTS a RR
CHANNEL RELEASE (triggered by the reception of BSSMAP
CLEAR COMMAND from the MSC).
calls:

411--9001--125
Data flows : The following data flow presents the links between signalling
messages exchanged at CM level (between the MSC and the MS),
when the release is initiated by the MS:
MS BSS NSS
CC DISCONNECT
CC RELEASE
CC RELEASE COMPLETE
As a comparison, the following data flow presents the links between

signalling messages exchanged at RR level (between the BSS and the
mobile) in normal release scenario:
MS BTS BSC MSC
BSSMAP CLEAR COMMAND

RR CHANNEL RELEASE
DESACTIVATE SACCH
DESACTIVATE SACCH ACK
DISK
RELEASE INDICATION
UA
RF CHANNEL RELEASE
BSSMAP CLEAR COMPLETE
RF CHANNEL RELEASE ACKNOWLEDGE
SCCP RELEASED
SCCP RELEASE COMPLETED

l
1164/17 Number of communications in traffic phase released: T200 elapse
Name Q3 : trafficReleaseErrorIndT200
Object : bts
time-out elapse
Event : receipt of ERROR INDICATION: T200 elapsed (N200 + 1) times
Class : release
Precise
This counter is related to the Layer2 LAPDm protocol (error
detection + repetition protocol between the BTS and the mobile
(MS)).
When a Layer 2 frame is not acknowledged by the MS before T200
expiration, the BTS sends an Error indication message to the BSC.
After (N200+1) Error indication consecutive messages received for
a call in traffic phase, the BSC increments by one the counter
1164/17.
calls:

411--9001--125
Data flows : The dataflow below presents an example of Layer 2 LADm exchange.
The Level3 messages (measurements reports in SD, EstInd, SMS,
Cyphering, SMS....) are encapsuled in the Layer 2.
MS BTS BSC
SABM
UA
frame1
Ack frame1
frame2
Error indication
T200 expiration
frame2
Error indication
T200 expiration
frame2
Error indication
T200 expiration N200 + 1 error indication + C1164/17
The Layer 2 exchange begins with a exchange of an SABM (Set

Asynchronous Balanced mode) and UA (Unnumbered
Acknowledge) frames.
The frame1 is acknowledged so it has being received correctly by the
MS and the BTS has received the acknowledgement of that.
The frame2 is not acknowledged either because the MS was not being
able to decode it or because the BTS could not receive the
acknowledgment.
The counter C1164/17 is usually linked to radio bad quality (UL or
DL).
1164/18 Number of communications in traffic phase released: DM error

Name Q3 : trafficReleaseErrorIndDm
Object : bts
Function : number of communications in traffic phase released because of DM
frames received in established multiframe mode

Event : receipt of ERROR INDICATION: DM frame received in established

multiframe mode
Class : release
Precise
calls:
l
1164/19 Number of communications in traffic phase released: Sequencing
error
Name Q3 : trafficReleaseErrorIndSeq
Object : bts
sequencing errors
Event : receipt of ERROR INDICATION: sequencing error
Class : release
Precise
calls:
l
1164/20 Number of communications in traffic phase released: CLEAR
COMMAND received
Name Q3 : trafficReleaseClearCommand
Object : bts
CLEAR COMMAND received

411--9001--125
Event : receipt of CLEAR COMMAND from the MSC on normal end of call
or outgoing inter-bss handover
Class : release
Precise
calls:
DFD “Connection clearing required by the MSC procedure
l
1164/21 Number of communications in traffic phase released: RF
Name Q3 : trafficReleaseRfResInd
Object : bts
Function : number of communications in traffic phase released because of RF
Event : receipt of three RF RESOURCE INDICATION messages
Class : release
Precise
calls:

l
1164/23 Number of communications in traffic phase released: TmodMs
elapse
Name Q3 : trafficReleaseTmodMs
Object : bts
TmodMs time-out elapse
Event : double TmodMs time-out elapse in the CHANNEL MODE MODIFY
procedure
Class : release
Precise
calls:
l
1164/24 Number of communications in traffic phase released: T3103
elapse
Name Q3 : trafficReleaseT3103
Object : bts
time-out elapse
Event : T3103 time-out elapse in the handover procedure
Class : release
Precise
calls:

411--9001--125
l
1164/25 Number of communications in traffic phase released: T8 elapse
Name Q3 : trafficReleaseT8
Object : bts
time-out elapse
Event : T8 time-out elapse in the inter-bss handover procedure
Class : release
Precise
calls:
l
1164/28 Number of communications in traffic phase released: Other cases
Name Q3 : trafficReleaseOthers
Object : bts
because of lack of Ater uplink TRAU frame synchronization. These
counters are the indications of a loss of frame synchronization either
because of a loopback on the transmission line, or poor quality of the
backhaul facilities.
Event : Receipt of a Release Indication message from the TCU with cause set
to ”Synchro frame error “.
Class : release
Source : recorded by the BSC. Counter 1164/28 increments on the uplink
(BTS-->TCU) when the TCU detects the fault.
Precise


calls:
Mechanism of Counter
This is managed by the TCU 3000; A TRAU can be in one of two
states, Idle or Active, and is considered to be synchronized, depending
on its state, when:
State = Idle : Receiving PCM idle pattern (010101)

State = Active: Receiving an uplink TRAU frame
supported by this TRAU.
Fault detection mechanism at the call establishment: This mechanism

is triggered when an idle TRAU, which is ”synchronized” on a PCM
idle pattern, looses this synchronization. At the loss of synchronization
detection, the TRAU starts the ”begin_com_ater_sync” timer. This
timer is stopped in following cases:
The PCM idle pattern is detected. In this case the TRAU

returns to the idle state.
An uplink TRAU frame supported by this TRAU is
received.
In case of ”begin_com_ater_sync” timer expiry, the fault is notified to

the BSC and the call is released. (The timer is set to 6 seconds.)
For Circuit data calls only, there is a similar mechanism to supervise

the A interface using timer begin_com_a_sync which is set to 30Sec.
This timer is stopped at reception of a V110 frame from the MSC
Fault detection mechanism on an established call: During the call, if a

loss of synchronization is detected on the uplink ATER interface, then
the ”in_com_ater_sync” timer is started. This timer is stopped in the
following cases:
The PCM idle pattern is detected. In this case the TRAU
returns to the idle state.
An uplink TRAU frame supported by this TRAU is
received.

411--9001--125
In case of ”in_com_ater_sync” timer expiry, the fault is notified to the

BSC and the call is released. (The timer is set to 6 seconds.)
For Circuit data calls only, there is a similar mechanism to supervise

the A interface using timer begin_com_a_sync which is set to 30Sec.
This timer is stopped at reception of a V110 frame from the MSC.
Release mechanism: At the fault detection, the TCU 3000 sends to the
BSC a Release Indication message (cause= ”Synchro trame error”). At
reception of this message, the BSC:
Releases the communication to quickly stop the billing

thanks to a Clear Request An interface message [R2] with standard
cause: ”equipment failure” and all radio resources are released.
Increments the C1164/28 counters to in order to provide a
threshold detection mechanism.
NOTE: Counter 1164/28 can also incremented in following cases:
TRM fault,
PCM A or ATER fault,
Lock of PCM A or ATER.
Detection process :
BSC 3000 Notifications:
On the BSC 3000, an anomaly is recorded for each kind of call drop:
5620 for calls dropped by the TCU (recorded once per 20
drops)
5621 for calls dropped by the BTS (recorded once per
100 drops)
To check for these errors, retrieve from the BSC the fault files located
in /OMU/share/fault (with the .txt extension) for the relevant days.
Please contact GNTS to get these files and analyze them.
BSC 3000/ TCU 3000 Notifications:
Counters also exist on the BSC 3000/TCU 3000 which can be used to detect
scenarios where calls are being abnormally dropped.

8713 (callDropTrafficRadio) provides the ratio of the number of

communications abnormally released within the signalling phase in the cell.
8714 (signallingReleaseRatio) provides the ratio of the number of
communications abnormally released within the traffic phase in the cell.
To ensure OMC--R notification when calls are being abnormally dropped, use the
following procedures.
How to trigger alarms using synthetic counters
1. On the active server under omc login, save the original synthetic counter formulae
configuration file to the default browsed with Synthetic Counters Editor location
by applying the following command:
(omc)% cp -p /OMC/data/custo_config/config/bss_operator_formulas.cfg
/OMC/data/custo_config/obs/synthetic/
Note: This command is used for safety reasons. It avoids overwriting any
synthetic counters that were previously created.
2. Set the formula with synthetic counter editor:

a) On a station, statx, SDO or PCUOAM (not on the server) : in the
“MmiGraphic” window select the “Performance menu” and then the
“Synthetic counter editor item”
b) Browse through the available configuration files and select the previously
saved bss_operator_formulas.cfg
c) On the right part of synthetic counter editor, write the synthetic counter
formula with threshold. Use the following syntax:
<Desired name> <counter class> <threshold> = <formula>
This translates to the syntax below, which is used to set up Synthetic Counters.
<Desired Name> bts [:on,Threshold_Alarm_Cleared,Threshold_Alarm_Raised]=<Formula>
Note: It is the responsibility of the operator to estimate appropriate threshold

values for the variables Threshold_Alarm_Cleared and
Threshold_Alarm_Raised.
d) Check the syntax by clicking on the “check syntax button”

e) Save the file by clicking on the “File menu” and then “Save as”
f) Dispatch the file on all the stations by clicking on the “Check menu” and
then “Apply”
Note: On the server make sure that the file has been dispatched to the:
dir/OMC/config/obs/synthetic/custom

411--9001--125
3. Check raw counters used in the synthetic counter formula (on the server). List the
raw counters used in the synthetic counter formula.
a) Select the concerned bsc, click on the mouse right button, and choose
“display”
b) On the list proposed choose bsc counter list 2 for OFS (fast statistic
counter)
c) In the Mmi window displayed or in sessionlog result, check that all raw
counters are present
4. Make PM tasks calculate values of synthetic counter (on the server).
a) Select “Performance menu”, item “load formula”, and choose
“Observation type: faststatistics” and then “apply”
5. Control results:
a) Check that observation files are generated (on the server) under:
/MD/obs/os_ftam/<currentday>/<bsc number>
b) Control that alarms are raised (use alarm Criteria to generate alarms)
To modify the alarm criteria
By default, FN 31200 is defined as major and only comes as a Notification. To create

critical alarm criteria for the FN 31200 notification, use the following procedure:
1. Select “Alarm Criteria Manager” under menu “Fault” of the Mmi GUI.
2. Choose “Object/create” in Alarm Criteria Manager Window.
3. Set Alarm Criteria Id to a value greater than 100000
4. Set critical for:
• day intervention
• night intervention
• particular intervention
5. In Object Instance:
• Set Exploration type object instance
• Click on “addItem” and then “Modify”
• Set:
– bsc all
– btsSm all
– bts all
• Click on “Apply”

6. Set CriteriaEventtype to alarmNotification
7. If OMC--R is V14.3 then:
• Set startAlarm filter to faultNumber = 31200
• Set endAlarm filter to perceived severity = CLEARED
If OMC--R is v15.0 then:

• Set startAlarm filter to faultNumber = 31200 & (!perceived severity =
CLEARED)
• Set endAlarm filter to perceived severity = 31200 & perceived severity =
CLEARED
8. Click on “Apply”
How to make the Alarm Criteria active
1. Select “OMC--R object” in Mmi

2. Click on right button choose “Display/set”
3. Select “Mode/Set”
4. Change alarm criteria from day configuration to night configuration, then click
on “Apply”
5. Change alarm criteria from night configuration to day configuration, then click
on “Apply”
Examples
Example 1: For C 1164/28 Counter Thresholds
The following rules must be applied:

Threshold_Alarm_Cleared < Threshold_Alarm_Raised
MiscellaneousDrops_1164_28 bts [:on,20,50] = trafficReleaseOthers;
MiscellaneousDrops_1164_32 bts [:on,20,50] =

trafficReleaseCnxFailRemTransFail;
The above Syntax will raise an Alarm if the Counter Value is more than or equal to
50 and will Clear the alarm if the Counter Value is less than or equal to 20.
In this example a major alarm is raised if counter 1164/28
(trafficReleaseCnxFailRemTrans) value is greater than 50:

411--9001--125
**** Notification : 4148196 ********** SEVERITY : major*************************

received on 10/02/03 17:09:07
Type : qualityOfServiceAlarm
Instance : bsc 9 | btsSiteManager 2 | bts 0
Description : bsce3_RPIS | S2000_50310_bsc_23 | G50310_2
TaskId : 751
- Information on fault -------------------------
Probable cause : (51) thresholdCrossed
Fault number : (31200) COUNTER EXCEEDING UPPER THRESHOLD
- Other information ----------------------------
: high threshold value : 50.000000
mdScannerType : fast Statistic
mdGranularityPeriod : 60 min
current counter value : 55.000000
counterId : MiscellaneousDrops_1164_28 ------ Desired name given by
operator
mdScanInitiationTime : 10/02/03 16:54:02*****************************************
Example 2: For callDropTrafficRatio v12 Counter (C 8704) and signallingReleaseRatio

v12 counter (C8713).

0 < [Threshold_Alarm_Cleared, Threshold_Alarm_Raised] < 1
Abnormal_traffic_release_Ratio bts [:on,0.1,0.2] = (callDropTrafficRatio);
Abnormal_signalling_release_Ratio bts [:on,0.1,0.2] =(signallingReleaseRatio);
The above syntax implements a counter arbitrarily called

Abnormal_traffic_release_Ratio of counter class bts. This counter will raise a
notification alarm if the synthetic countercallDropTrafficRatio exceeds 0.2 (20%)
and will clear the notification alarm when the threshold drops below 0.1 (10%).

Notification : 3889842 ********** SEVERITY : major ******************

received on 02/12/04 10:45:31
Type : qualityOfService
AlarmInstance : bsc 96 | btsSiteManager 14 | bts 0
Description : bsce3_RPIS2 | S4000_Oudoor_O3_pcs_34357 | CELL_0
TaskId : 751
mdScannerType : general Statistic
counterId: Abnormal_release_traffic_Ratio ------ Desired name given by operator
mdScanInitiationTime : 02/12/04 10:30:00
Example 3: For Abnormal_traffic_release_Ratio including AMR/HR and Cell Tiering

(v14/V15).

Abnormal_traffic_release_Ratio_V14_V15 bts [:on,0.1,0.2] =

trafficAbnormalRelease /(successfulTchFrSeizures +
amrHrTchSuccessfullyAssigned - hoSuccessIntraBts -
hoSuccessTieringTchLargeToSmallPattern -
hoSuccessTieringTchSmallToLargePattern + hoSuccessIncomingIntraBss +
hoSuccessIncomingInterBss);

411--9001--125
Common Causes:
Failing PCM or Timeslot in the path between the BTS and TCU.
Trap of DSP that manages the call (TRM board): Check if you
have any 2032 fault on TRM of your BSC.
Synchronization of BSC/TCU with the MSC clock: Check the
synchronization of BSC 3000/TCU/MSC
- V15.0 using a ”display dynamic data” on BSC 3000 and on
TCU 3000 objects.
- Prior to V15.0, using notifications 2019.
ATER PCMs are crossed. Often seen in cases where 1164/28 is

incremented: Check that the ATER PCMs are not crossed.
Note: in the vast majority of cases an increase in counters 1164/28 and

1164/32 is due to PCM quality issues.
Isolation and Diagnosis:
The problem could be caused by the ABIS or ATER PCM, (or the BSC), and
may affect an entire PCM or, one or more individual Timeslots. Each
64Kbps ABIS PCM timeslot is divided into four 16Kbps sub--channels.
Therefore each TDMA, consisting of 8 channels, uses two adjacent ABIS
64Kbps TS.
The mapping of Radio Channels to ABIS Timeslot is:
ABIS
X X X X Y Y Y Y
Timeslot
Channel 3 4 5 6 7 0 1 2
Therefore: A failure of one 64Kbps timeslot will affect four radio channels.
Suggested actions to isolate failing PCM component :

1. Please contact Nortel Technical Support to decode the BSC
3000 logs in order to determine which PCMs, Timeslots and Channels are
affected.:
a. Look for reoccurring instances of the same PCM and/or
Timeslot.
b. Verify if most commonly failing PCM is an ATER or ABIS

PCM.
c. For the failing PCM, check which 16Kbps sub--channels are
impacted: Is it all 4 sub--channels associated with one
timeslot, or only 1 or 2 sub--channels?
2. Check for any PCM related notifications for the PCM’s found in
step 1, treat these symptoms first then verify if counters are still incremented
3. Confirm failing path:
a. Try to swap PCMs, or lock one PCM at a time.
b. Try to lock impacted Radio Channels.
c. Determine if the counters are still incremented.
4. If either the ATER or ABIS PCM pass through intermediate

equipment such as a DACS:
a. Check the DACS board that manages the PCM and the DACS
configuration.
b. The DACS (and many other types of transmission equipment)
will often have counters indicating errors, errored seconds,
BPV’s, slips, or Frame errors. Use these to localize the source of
the problem. Note that, depending on the type of DACS, it may
re--frame the signal, which would tend to ”mask” alarms and
some types of errors (slips, notably).
c. All transmission facilities should be configured to use
appropriate zero--code suppression (i.e., B8ZS for DS1
facilities).
5. Using suitable test equipment, perform end--to--end quality test
of failing PCM.( i.e. BERT test etc). Ensuring that all Timeslots
are checked.
6. If the failing PCM’s are associated with the same LSA perform
a SWACT of the associated IEM.
NOTES:
If layer 1 does not detect a fault, (for example a looped PCM) and there is no
LAPD carried on the failing timeslot(s), then there may be no other
indication of a PCM problem other than the counters 1164/28 and 1164/32.
A call dropped by the TCU could also lead to the BTS detecting a problem
and incrementing 1164/32, therefore it is not unusual to see both counters
incrementing.
Due to the fact that the call is dropped after 6 secs it can be difficult to

411--9001--125
identify a failing PCM/TS in real--time.

l
1164/31 Number of communications in traffic phase released: SYS INFO
problem
Name Q3 : trafficReleaseSysInfoFail
Object : bts
because the SYS INFO procedure is aborted following a BSC chain
switchover.
Event : SYS INFO procedure aborted following a BSC chain switchover
Class : release
Precise
calls:
l
1164/32 Number of communications in traffic phase released: TCU
failure
Name Q3 : trafficReleaseCnxFailRemTransFail
Object : bts
because of lack of Abis downlink TRAU frame synchronization.
Creating a synthetic counter to work on a ration, not on absolute
values. These counters are the indications of a loss of frame
synchronization either because of a loopback on the transmission line,
or poor quality of the backhaul facilities.
Event : receipt of CONNECTION FAILURE INDICATION with cause
“remote transcoder failure”
Class : release
Source : recorded by the BSC. Counter 1164/32 increments on the downlink
(TCU-->BTS) when the BTS detects the fault.

Precise
calls:
Mechanism of Counter
The BTS is synchronized when the following frames are received on
the ABIS PCM:
Correct speech frames (FS, EFR, FR and HR AMR,
circuit data, PEC frames)
SID, idle speech, idle data.
The BTS loses or does not find its frame synchronization in the
following cases:
Frames without any correct synchronization pattern since

V12.4C release,
PCM idle frames (01010101) since V14.2 and V14.3.
If the BTS loses its frame synchronization during a communication,

or does not find its frame synchronization at the beginning of a
communication, it starts a timer Tsync (1Sec).
If the frame synchronization is obtained before the Tsync expires, no

signalization occurs.
If timer Tsync expires, a confirmation timer is started:

speech case: circuitSynchroTimer = 5 Sec.
circuit data case: circuitSynchroTimer = 15 Sec.
If the frame synchronization is obtained before the

circuitSynchroTimer expires, no signalization occurs.
If timer circuitSynchroTimer expires before frame synchronization is
obtained, the BTS sends a ’Connection Failure Indication’ RSL
message with the cause: remote transcoder failure (this cause is a
standard cause, described in GSM 05.58, which is used in some scarce
cases for transcoder failure, but most often for backhaul error
detection).
When the BSC receives this message it will:
Release the call with a Clear Request: An interface

411--9001--125
message with standard cause: ’equipment failure’

Set a new internal TCH flag ”circuit failure detection
release” to true
Put the TCH into the pool of worst interference level,
whatever its level before the allocation, and increment the cell
counter: Traffic_Release C1164/32
Detection process :
BSC 3000 Notifications:
On the BSC 3000, an anomaly is recorded for each kind of call drop:
5620 for calls dropped by the TCU (recorded once per 20 drops)
5621 for calls dropped by the BTS (recorded once per 100
drops)
To check for these errors, retrieve from the BSC the fault files located in
/OMU/share/fault (with the .txt extension) for the relevant days. Please
contact GNTS to get these files and analyze them.
Common Causes:
Failing PCM or Timeslot in the path between the TCU and the
BTS.
Note: in the vast majority of cases an increase in counters 1164/28 and

1164/32 is due to PCM quality issues.
Isolation and Diagnosis:
The problem could be caused by the ABIS or ATER PCM, (or the BSC), and
may affect an entire PCM or, one or more individual Timeslots. Each
64Kbps ABIS PCM timeslot is divided into four 16Kbps sub--channels.
Therefore each TDMA, consisting of 8 channels, uses two adjacent ABIS
64Kbps TS.
The mapping of Radio Channels to ABIS Timeslot is:
ABIS
X X X X Y Y Y Y
Timeslot
Channel 3 4 5 6 7 0 1 2
Therefore: A failure of one 64Kbps timeslot will affect four radio channels.

Suggested actions to isolate failing PCM component :

1. Please contact Nortel Technical Support to decode the BSC
3000 logs in order to determine which PCMs, Timeslots and Channels are
affected.:
a. Look for reoccurring instances of the same PCM and/or
Timeslot.
b. Verify if most commonly failing PCM is an ATER or ABIS
PCM.
c. For the failing PCM, check which 16Kbps sub--channels are
impacted: Is it all 4 sub--channels associated with one
timeslot, or only 1 or 2 sub--channels?
2. Check for any PCM related notifications for the PCM’s found in
step 1, treat these symptoms first then verify if counters are still incremented
3. Confirm failing path:
a. Try to swap PCMs, or lock one PCM at a time.
b. Try to lock impacted Radio Channels.
c. Determine if the counters are still incremented.
4. If either the ATER or ABIS PCM pass through intermediate

equipment such as a DACS:
a. Check the DACS board that manages the PCM and the DACS
configuration.
b. The DACS (and many other types of transmission equipment)
will often have counters indicating errors, errored seconds,
BPV’s, slips, or Frame errors. Use these to localize the source of
the problem. Note that, depending on the type of DACS, it may
re--frame the signal, which would tend to ”mask” alarms and
some types of errors (slips, notably).
c. All transmission facilities should be configured to use
appropriate zero--code suppression (i.e., B8ZS for DS1
facilities).
5. Using suitable test equipment, perform end--to--end quality test
of failing PCM.( i.e. BERT test etc). Ensuring that all Timeslots
are checked.
6. If the failing PCM’s are associated with the same LSA perform
a SWACT of the associated IEM.
NOTES:
If layer 1 does not detect a fault, (for example a looped PCM) and there is no

411--9001--125
LAPD carried on the failing timeslot(s), then there may be no other

indication of a PCM problem other than the counters 1164/28 and 1164/32.
A call dropped by the TCU could also lead to the BTS detecting a problem
and incrementing 1164/32, therefore it is not unusual to see both counters
incrementing.
Due to the fact that the call is dropped after 6 secs it can be difficult to
identify a failing PCM/TS in real--time.
BSC 3000/ TCU 3000 NOTIFICATIONS:
Counters also exist on the BSC 3000/TCU 3000 which can be used to detect
scenarios where calls are being abnormally dropped.
8713 (callDropTrafficRadio) provides the ratio of the number of
communications abnormally released within the signalling phase in the cell.
8714 (signallingReleaseRatio) provides the ratio of the number of
communications abnormally released within the traffic phase in the cell.
To ensure OMC--R notification when calls are being abnormally dropped, use the
following procedures.
How to trigger alarms using synthetic counters
1. On the active server under omc login, save the original synthetic counter formulae
configuration file to the default browsed with Synthetic Counters Editor location
by applying the following command:
(omc)% cp -p /OMC/data/custo_config/config/bss_operator_formulas.cfg
/OMC/data/custo_config/obs/synthetic/
Note: This command is used for safety reasons. It avoids overwriting any
synthetic counters that were previously created.
2. Set the formula with synthetic counter editor:

a) On a station, statx, SDO or PCUOAM (Not on the Server) : in the
“MmiGraphic” window select the “Performance menu” and then the
“Synthetic counter editor item”
b) Browse through the available configuration files and select the previously
saved bss_operator_formulas.cfg
c) On the right part of synthetic counter editor, write the synthetic counter
formula with threshold. Use the following syntax:
<Desired name> <counter class> <threshold> = <formula>

This translates to the syntax below, which is used to set up Synthetic Counters.
<Desired Name> bts [:on,Threshold_Alarm_Cleared,Threshold_Alarm_Raised]=<Formula>
Note: It is the responsibility of the operator to estimate appropriate threshold

values for the variables Threshold_Alarm_Cleared and
Threshold_Alarm_Raised.
d) Check the syntax by clicking on the “check syntax button”

e) Save the file by clicking on the “File menu” and then “Save as”
f) Dispatch the file on all the stations by clicking on the “Check menu” and
then “Apply”
Note: On the server make sure that the file has been dispatched to the
dir/OMC/config/obs/synthetic/custom
3. Check the raw counters used in the synthetic counter formula (on the server). List
the raw counters used in the synthetic counter formula.
a) Select the concerned bsc, click on the mouse right button, and choose
“display”
b) On the list proposed choose bsc counter list 2 for OFS (fast statistic
counter)
c) In the Mmi window displayed or in sessionlog result, check that all raw
counters are present
4. Make PM tasks calculate values of synthetic counter (on the server).
a) Select “Performance menu”, item “load formula”, and choose
“Observation type: faststatistics” and then “apply”
5. Control results:
a) Check that observation files are generated (on the server) under:
/MD/obs/os_ftam/<currentday>/<bsc number>
b) Control that alarms are raised (use alarm Criteria to generate alarms)
To modify the alarm criteria
By default, FN 31200 is defined as major and only comes as a Notification. To create

critical alarm criteria for the FN 31200 notification, use the following procedure:
1. Select “Alarm Criteria Manager” under menu “Fault” of the Mmi GUI.
2. Choose “Object/create” in Alarm Criteria Manager Window.
3. Set Alarm Criteria Id to a value greater than 100000
4. Set critical for:

411--9001--125
• day intervention
• night intervention
• particular intervention
5. In Object Instance:
• Set Exploration type object instance
• Click on “addItem” and then “Modify”
• Set:
– bsc all
– btsSm all
– bts all
6. Set CriteriaEventtype to alarmNotification
7. If OMC--R is V14.3 then:
• Set startAlarm filter to faultNumber = 31200
• Set endAlarm filter to perceived severity = CLEARED
If OMC--R is v15.0 then:
• Set startAlarm filter to faultNumber = 31200 & (!perceived severity =
CLEARED)
• Set endAlarm filter to perceived severity = 31200 & perceived severity =
CLEARED
8. Click on “Apply”
How to make the Alarm Criteria active
1. Select “OMC--R object” in Mmi
2. Click on right button choose “Display/set”
3. Select “Mode/Set”
4. Change alarm criteria from day configuration to night configuration, then click
on “Apply”
5. Change alarm criteria from night configuration to day configuration, then click
on “Apply”
Examples
Example 1: For 1164/32 Counter Thresholds


MiscellaneousDrops_1164_28 bts [:on,20,50] = trafficReleaseOthers;
MiscellaneousDrops_1164_32 bts [:on,20,50] =

trafficReleaseCnxFailRemTransFail;
The above Syntax will raise an Alarm if the Counter Value is more than or equal to
50 and will Clear the alarm if the Counter Value is less than or equal to 20.
In this example a major alarm is raised if counter 1164/32

(trafficReleaseCnxFailRemTrans) value is greater than 50:
**** Notification : 4148196 ********** SEVERITY : major***********************

received on 10/02/03 17:09:07
Description : bsce3_RPIS | S2000_50310_bsc_23 | G50310_2
TaskId : 751
mdScannerType : fast Statistic
counterId : MiscellaneousDrops_1164_32 ------ Desired name given by
operator
mdScanInitiationTime : 10/02/03 16:54:02***************************************
Example 2: For CallDropTrafficRatio v12 Counter (c 8704) and signallingReleaseRatio

v12 counter (C8713).

Abnormal_traffic_release_Ratio bts [:on,0.1,0.2] = (callDropTrafficRatio);
Abnormal_signalling_release_Ratio bts [:on,0.1,0.2] =(signallingReleaseRatio);
The above syntax implements a counter arbitrarily called

Abnormal_traffic_release_Ratio of counter class bts. This counter will raise a
notification alarm if the synthetic countercallDropTrafficRatio exceeds 0.2 (20%)
and will clear the notification alarm when the threshold drops below 0.1 (10%).

411--9001--125
Notification : 3889842 ********** SEVERITY : major ******************

received on 02/12/04 10:45:31
Description : bsce3_RPIS2 | S4000_Oudoor_O3_pcs_34357 | CELL_0
TaskId : 751
mdScannerType : general Statistic
counterId: Abnormal_release_traffic_Ratio ------ Desired name given by operator
mdScanInitiationTime : 02/12/04 10:30:00
Example 3: For Abnormal_traffic_release_Ratio including AMR/HR and Cell Tiering

(v14/V15).

Abnormal_traffic_release_Ratio_V14_V15 bts [:on,0.1,0.2] =

trafficAbnormalRelease /(successfulTchFrSeizures +
amrHrTchSuccessfullyAssigned - hoSuccessIntraBts -
hoSuccessTieringTchLargeToSmallPattern -
hoSuccessTieringTchSmallToLargePattern + hoSuccessIncomingIntraBss +
hoSuccessIncomingInterBss);

l
1165 Number of handover requests not processed: Tchoke in-progress
Name Q3 : hoIndicationNotTreatedTchoke
Object : bts
Function : number of handover requests not processed by the BSC because of
Tchoke timer active
Event : receipt of HANDOVER INDICATION while the Tchoke timer is
running
Class : handover
Precise
calls:
l
1167 Number of unsuccessful outgoing intra handovers on TCH to a
non-heading cell without reestablishment in the serving cell
Name Q3 : hoUnsuccessOutgoingIntraBssNAttemptTch
Object : bts
Function : number of unsuccessful outgoing intra-bss handovers on TCH
towards a cell that is not heading the list of eligible cells without
reestablishment in the current serving cell
Event : receipt of HANDOVER FAILURE on T3103 time-out elapse
Class : handover

411--9001--125
Precise
calls:
Note : the list is reorganized by the BSC since Ho decision function. It may
not be the same order as the one received from the L1M
l
1168 Number of unsuccessful outgoing intra handovers on SDCCH to
a non-heading cell without reestablishment in the serving cell
Name Q3 : hoUnsuccessOutgoingIntraBssNAttemptSdcch
Object : bts
Function : number of unsuccessful outgoing intra-bss handovers on SDCCH
Event : receipt of HANDOVER FAILURE on T3103 time-out elapse
Class : handover
Precise
calls:
l
1169 Number of unsuccessful outgoing inter handovers on TCH to a
non-heading cell without reestablishment in the serving cell
Name Q3 : hoUnsuccessOutgoingInterBssNAttemptTch
Object : bts
Function : number of unsuccessful outgoing inter-bss handovers on TCH

Event : T3103 time-out elapse or receipt of CLEAR COMMAND with a

cause different from “Handover successful” or “Call Control”
Class : handover
Precise
calls:
l
1170 Number of unsuccessful outgoing inter handovers on SDCCH to
a non-heading cell without reestablishment in the serving cell
Name Q3 : hoUnsuccessOutgoingInterBssNAttemptSdcch
Object : bts
Function : number of unsuccessful outgoing inter-bss handovers on SDCCH
Event : T3103 time-out elapse or receipt of CLEAR COMMAND with a
cause different from “Handover successful” or “Call Control”
Class : handover
Precise
calls:

411--9001--125
l
1172/0 Number of fallbacks from a data rate to other data rates for TCB
lack of resources cause
Name Q3 : dataNtRateFbTcbResLack
Object : bsc
Function : number of fallbacks from a data rate to other data rates for TCB lack
of resources cause
Event : response from terrestrial allocator
Class : A interface
Precise
calls:
l
1172/1 Number of fallbacks from a data rate to other data rates for non
allowed TCB configuration cause
Name Q3 : dataNtRateFbTcbConfNotAllowed
Object : bsc
Function : number of fallbacks from a data rate to other data rates for non
allowed TCB configuration cause
Event : configuration mismatch
Class : A interface
Precise
calls:

l
1191/0 Number of channel allocation requests: Cause 000
Name Q3 : channelRequestCause000
Object : bts
Function : number of channel allocation requests in the cell with cause 000
Event : receipt of CHANNEL REQUIRED:
Phase I = all other cases
Phase II = location update request (0000), other procedures using
an SDCCH (0001)
Class : setup
Precise
calls:
completion)”
l
Object : bts
Phase I = nonsignificant
Phase II = reply to a paging request
Class : setup

411--9001--125
Precise
calls:
completion)”
l
Object : bts
Phase II = transmission of speech (0100) or data (0101) on a
TCH/FR by a mobile
Class : setup
Precise
calls:
completion)”

l
Object : bts
Phase II = call reestablishment on a TCH/FR
Class : setup
Precise
calls:
completion)”
l
Object : bts
Event : receipt of CHANNEL REQUIRED for a reply to a paging request
Class : setup

411--9001--125
Precise
calls:
completion)”
l
Object : bts
Event : receipt of CHANNEL REQUIRED for an emergency call
Class : setup
Precise
calls:
completion)”

l
Object : bts
Event : receipt of CHANNEL REQUIRED for a call reestablishment
Class : setup
Precise
calls:
completion)”
l
Object : bts
Event : receipt of CHANNEL REQUIRED with the following cause:
Phase I = any services requested by the mobile (MOC, SMS, SS)
Phase II = MOC (Mobile Originating Call) service on TCH/FR
Class : setup

411--9001--125
Precise
calls:
completion)”
1192/0 Number of successful immediate assignments: Cause 000

Name Q3 : immediateAssignmentSuccessCause000
Object : bts
Function : number of immediate assignments with cause 000 satisfied
Event : transmission of IMMEDIATE ASSIGNMENT on receipt of
CHANNEL REQUEST with the following cause:
Phase I = all other cases
Phase II = location update request (0000), other procedures using
an SDCCH (0001)
Class : setup
Precise
calls:


DFD “GPRS procedure preemption on PDTCH (normal
completion)”
l
Object : bts
Event : transmission of IMMEDIATE ASSIGNMENT with the following
cause:
Phase II = reply to a paging request
Class : setup
Precise
calls:
completion)”

411--9001--125
l
Object : bts
cause:
Phase II = transmission of speech (0100) or data (0101) on a
TCH/FR by a mobile
Class : setup
Precise
calls:
completion)”
l
Object : bts


cause:
Phase II = call reestablishment on a TCH/FR
Class : setup
Precise
calls:
completion)”
l
Object : bts
CHANNEL REQUEST with cause “paging request”
Class : setup

411--9001--125
Precise
calls:
completion)”
l
Object : bts
CHANNEL REQUEST with cause “emergency call”
Class : setup
Precise
calls:


completion)”
l
Object : bts
CHANNEL REQUEST with cause “call reestablishment”
Class : setup
Precise
calls:
completion)”

411--9001--125
l
Object : bts
CHANNEL REQUEST with the following cause:
Phase I = all services requested by the mobile (MOC, SMS, SS)
Phase II = MOC (Mobile Originating Call) service on TCH/FR
Class : setup
Precise
calls:
completion)”
l
1193/0 Number of ESTABLISH INDICATION messages in
establishment phase received for paging requests
Name Q3 : estabIndicSignallingPagingRes
Object : bts
Function : number of ESTABLISH INDICATION messages received on
SDCCH or TCH if no SDCCH is available, for replies to paging
requests

Event : receipt of ESTABLISH INDICATION for a reply to a paging request

Class : setup
Precise
calls:
completion)”
completion)”
l
establishment phase received for location updates
Name Q3 : estabIndicSignallingLocUpdate
Object : bts
SDCCH or TCH if no SDCCH is available, for location update
requests
Event : receipt of ESTABLISH INDICATION for a location update request
Class : setup
Precise
calls:

411--9001--125

completion)”
completion)”
l
establishment phase received for call reestablishments
Name Q3 : estabIndicSignallingReEstab
Object : bts
SDCCH or TCH in primo-allocations, for call reestablishments
Event : receipt of ESTABLISH INDICATION for a call reestablishment
Class : setup
Precise
calls:
completion)”
completion)”

l
establishment phase received for IMSI detachments
Name Q3 : estabIndicSignallingImsiDetach
Object : bts
SDCCH or TCH if no SDCCH is available, for IMSI detachments
Event : receipt of ESTABLISH INDICATION for an IMSI detach request
Class : setup
Precise
calls:
completion)”
completion)”
l
establishment phase received for mobile originating calls
Name Q3 : estabIndicSignallingMoc
Object : bts
SDCCH or TCH if no SDCCH is available, for mobile originating
calls
Event : receipt of ESTABLISH INDICATION for a mobile originating call
Class : setup

411--9001--125
Precise
calls:
completion)”
completion)”
l
establishment phase received for urgent calls
Name Q3 : estabIndicSignallingEmergency
Object : bts
SDCCH or TCH if no SDCCH is available, for emergency calls
Event : receipt of ESTABLISH INDICATION for an emergency call
Class : setup
Precise
calls:


completion)”
completion)”
l
establishment phase received for short messages
Name Q3 : estabIndicSignallingShortMsg
Object : bts
Function : on SDCCH or TCH if no SDCCH is available, for short messages
Event : receipt of ESTABLISH INDICATION for a short message
Class : setup
Precise
calls:
completion)”
completion)”

411--9001--125
l
establishment phase received for other services
Name Q3 : estabIndicSignallingSuppService
Object : bts
SDCCH or TCH if no SDCCH is available, for supplementary service
Event : receipt of ESTABLISH INDICATION for a supplementary service
Class : setup
Precise
calls:
completion)”
completion)”

establishment phase with notification message piggybacked
Name Q3 : estabIndicSignallingPiggybacked
Object : bts
Function : number of notification response messages piggybacked in the
ESTABLISHMENT_INDICATION message.
Event : receipt of ESTABLISHMENT_INDICATION message with a
notification response message piggybacked.
Class : ASCI (GSM--R)

Feature : 13913 ASCI Evolutions

Precise
calls:
Note : V15 counter
l
1195 Number of ESTABLISH INDICATION messages in
establishment phase received for Phase I mobiles
Name Q3 : estabIndicSigPhase1
Object : bts
SDCCH, or TCH in primo-allocations, or TCH if no SDCCH is
available, for Phase I mobiles
Event : receipt of ESTABLISH INDICATION for a Phase I mobile
Class : setup
Precise
calls:
completion)”
completion)”

411--9001--125
l
1196 Number of ESTABLISH INDICATION messages in
establishment phase received for Phase II mobiles
Name Q3 : estabIndicSigPhase2
Object : bts
SDCCH, or TCH in primo-allocations, or TCH if no SDCCH is
available, for Phase II mobiles
Event : receipt of ESTABLISH INDICATION for a Phase II mobile
Class : setup
Precise
calls:
completion)”
l
1197/0 Number of channels activated for speech: Full Rate Algorithm
Name Q3 : channelActivateSpeechFullRate
Object : bts
Function : number of speech channels using the Full-Rate algorithm, activated in
the cell for the observation period
Class : assignment

Precise
calls:
completion)”
l
1197/1 Number of channels activated for speech: Enhanced Full Rate
Algorithm
Name Q3 : channelActivateSpeechEnhancedFullRate
Object : bts
Function : number of speech channels using the Enhanced Full-Rate algorithm,
Class : assignment
Precise
calls:

411--9001--125

completion)”
l
1198 Duration of maximum Downlink power use on busy TCH/FRs or
preempted PDTCHs
Name Q3 : downlinkPowerCtrlMaxTchMoy
downlinkPowerCtrlMaxTchMax Maximum duration
downlinkPowerCtrlMaxTchCum Total duration
downlinkPowerCtrlMaxTchEch Number of samples
Object : bts
Function : average duration ( = total duration divided by the number of samples)
and maximum duration of maximum Downlink power use on the cell
TCH/FRs or preempted PDTCHs in the observation period
Event : start/end of maximum TCH Downlink power use:
start: start timer
end:
• add it to the total of maximum Downlink power use durations
on TCH/FRs or preempted PDTCHs in the observation period
Class : L1M

Precise
calls:
l
1199 Duration of maximum Uplink power use on busy TCH/FRs or
preempted PDTCHs
Name Q3 : uplinkPowerCtrlMaxTchMoy
uplinkPowerCtrlMaxTchMax . . . . Maximum duration
uplinkPowerCtrlMaxTchCum . . . . Total duration
uplinkPowerCtrlMaxTchEch . . . . . Number of samples
Object : bts
and maximum duration of maximum Uplink power use on the cell
TCH/FRs or preempted PDTCHs for the observation period
Event : start/end of maximum TCH Uplink power use:
start: start timer

411--9001--125
end:
• add it to the total of maximum Uplink power use durations on
TCH/FRs or preempted PDTCHs in the observation period
Class : L1M
Precise
calls:
l
1200 Number of handovers on TCH executed
Name Q3 : hoNcellsExecution
Function : number of attempts to execute handovers on TCH from a serving cell
to its neighbors

Event : receipt of HANDOVER COMMAND from the MSC (inter-bss

handover) or transmission of Abis HANDOVER COMMAND to the
serving cell (intra-bss handover)
Class : handover
DFD “Inter--cell intra BSC handovers procedure (normal
l
1202 Number of handovers on SDCCH executed
Name Q3 : hoNcellsExecutionSdcch
Function : number of attempts to execute handovers on SDCCH from a serving
cell to its neighbors
Event : receipt of HANDOVER COMMAND from the MSC (inter-bss
handover) or transmission of Abis HANDOVER COMMAND to the
serving cell (intra-bss handover)
Class : handover
l
1204/0 Number of unsuccessful outgoing handovers on TCH: Back to old
channel
Name Q3 : hoNcellsUnsuccessTchChlR
Function : number of unsuccessful outgoing intra- and inter-bss handovers on
TCH with the mobile returning to the old channel
Event : receipt of HANDOVER FAILURE before T3103 time-out elapse (the
serving cell is unable to transfer the mobile to the new channel)
Class : handover

411--9001--125
l
1204/1 Number of unsuccessful outgoing handovers on TCH: Time-out
elapse
Name Q3 : hoNcellsUnsuccessTchTimer
TCH because of T3103 time-out elapse
Class : handover
l
1204/2 Number of unsuccessful outgoing handovers on TCH: Other
cases
Name Q3 : hoNcellsUnsuccessTchOther
TCH because of other reasons
Event : receipt of CLEAR COMMAND from the MSC with a cause different
from “Handover successful” or “Call Control”
Class : handover
l
1205/0 Number of unsuccessful outgoing handovers on SDCCH: Back to
old channel
Name Q3 : hoNcellsUnsuccessSdcchChlR
SDCCH with the mobile returning to the old channel
Event : receipt of HANDOVER FAILURE before T3103 time-out elapse (the
serving cell is unable to transfer the mobile to the new channel)
Class : handover

l
1205/1 Number of unsuccessful outgoing handovers on SDCCH:
Time-out elapse
Name Q3 : hoNcellsUnsuccessSdcchTimer
SDCCH because of T3103 time-out elapse
Class : handover
l
1205/2 Number of unsuccessful outgoing handovers on SDCCH: Other
cases
Name Q3 : hoNcellsUnsuccessSdcchOther
SDCCH for other reasons
Event : receipt of CLEAR_COMMAND with a cause different from
“Handover successful” or “Call Control” coming from the MSC
Class : handover
l
1206/0 Number of handovers and assignment for which the initial
request in EFR speech algorithm is degraded into FR speech
algorithm
Name Q3 : speechAlgoFallBack
Object : bsc
Function : number of handovers and assignment for which the initial request in
EFR speech algorithm is degraded into FR speech algorithm only in
case of the BSC has a CIC bearing EFR and other CICs not bearing
EFR and if all CICs bearing EFR are already allocated

411--9001--125
Event : receipt of ASSIGN REQUEST or HANDOVER REQUEST with a

CIC and a speech coding algorithm incompatible
Class : assignment
Precise
calls:
Note : This counter is only incremented if Enhanced Full Rate is allowed in
the network.
l
1207 Number of immediate assignments for multiband mobiles
Name Q3 : immediateAssignmentMultiband
Object : bts
Function : number of call establishments for multiband mobiles (external
incoming handover requests are not included)
Event : receipt of the first CLASSMARK_CHANGE message from a mobile
with classmark 3 multiband data, when
Early_Classmark_Sending_Controlled is “true”
Class : assignation
Precise
calls:

l
1208 Number of outgoing handovers requested by dualband mobiles
from the main frequency band to the second frequency band of
the network
Name Q3 : hoRequestOutgoingMbandEbandMsDualb (V12)
hoRequestOutgoingMultiband (V10 & V11)
Object : bts
Function : number of outgoing, intra-bss or inter-bss handovers, on TCH,
requested from the main frequency band to the second frequency
band of the network
Event : attempt to select a cell that belongs to the second frequency band in
the list of eligible cells
Class : handover
Precise
calls:
Note : The target resource is in the second frequency band whereas the
originated resource is in the main frequency band of the network.
l
1209 Number of successful outgoing handovers for dualband mobiles
from the main frequency band to the second frequency band of
the network
Name Q3 : hoSuccessOutgoingMbandEbandMsDualb (V12)
hoSuccessOutgoingMultiband (V10 & V11)
Object : bts
Function : number of successful outgoing, intra-bss or inter-bss handovers, on
TCH, from the main frequency band to the second frequency band of
the network

411--9001--125
Event : receipt of CLEAR COMMAND with cause “handover successful”

(inter-bss handover) or receipt of HANDOVER COMPLETE from
the MS (intra-bss handover)
Class : handover
Precise
calls:
l
1500 Number of DTAP messages sent
Name Q3 : aTransparentUp
Object : bsc
Function : number of transparent messages sent by the BSC to the MSC
Event : transmission of SCCP DATA REQUEST
Class : A interface
Precise
calls:


DFD “immediate assignment procedure (normal completion)”
completion)”
l
1501 Number of DTAP messages received
Name Q3 : aTransparentDown
Object : bsc
Function : number of transparent messages sent by the MSC to the BSC
Event : receipt of SCCP CONNECTION CONFIRM or SCCP DATA
INDICATION
Class : A interface
Precise
calls:
completion)”

411--9001--125
l
1502 Number of BSSMAP messages sent
Name Q3 : aNonTransparentUp
Object : bsc
Function : number of non transparent messages sent by the BSC to the MSC
Event : transmission of SCCP CONNECTION REQUEST, SCCP DATA
REQUEST, or SCCP UNIT DATA REQUEST
Class : A interface
Precise
calls:
preemption)”
DFD “immediate assignment procedure (normal completion)
completion)”
phase)”
completion)”


completion)”
l
1503 Number of BSSMAP messages received
Name Q3 : aNonTransparentDown
Object : bsc
Function : number of non transparent messages sent by the MSC to the BSC
Event : receipt of SCCP_CONNECTION_ INDICATION,
SCCP_DATA_INDICATION, SCCP_CONNECTION_CONFIRM
, or SCCP_UNIT_DATA_INDICATION
Class : A interface
Precise
calls:
preemption)”
completion)”

411--9001--125

phase)”
completion)”
completion)”
l
1504 Number of BSC acceptations of VGCS talking requests issued by
the BTS
Name Q3 : vgcsAccessGrant
Object : bsc
Function : number of BSC acceptations of VGCS talking requests issued by the
BTS
Event : transmission of a UPLINK_REQUEST message towards the MSC
Class : asci
Feature : GSM--R (V12)
Precise
This counter is concerned by CCT (Circuit Calls on TCH channels)
but not by CCP (Circuit Calls on PDTCH preempted to make a TCH
channel) or by CP (Com packet on PDTCH channel), merely because
GPRS and GSM--R cannot be activated at the same time.
l
1505 Number of MSC refusals on VGCS talking requests issued by the
BSC
Name Q3 : vgcsMscReject
Object : bsc
Function : number of MSC refusals on VGCS talking requests issued by the BSC

Event : receipt of an UPLINK_REJECT_COMMAND message from the

MSC
Class : asci
Precise
l
1506/0 Number of rejected paging requests due to overload situation
Name Q3 : aintOverloadRejectedOpPageReq
Object : bsc
Function : number of rejected paging requests due to overload situation
Event : receipt of a paging request, an external incoming handover request, a
VBS/VGCS setup request, a VBS/VGCS assignment request or a
perform location request when at least one SS7 TMU, interface Node,
or local TMU is in overload situation
Class : equipment
Precise
calls:
The counter is available in both BSC 12000HC and BSC 3000:
On a BSC 12000HC, the counter is related to CS--Paging messages
dropped in case of overload.
On a BSC 3000, the counter is related to CS--Paging and
PS--Paging messages dropped in case of overload.

411--9001--125
l
1506/1 Number of rejected incoming external handover requests due to
overload situation
Name Q3 : aintOverloadRejectedOpIncomingExtHoReq
Object : bsc
Function : number of rejected external handover requests due to overload
situation
Event : receipt of an incoming external handover request when at least one
SS7 TMU, interface Node, or local TMU board is in overload
situation
Class : equipment
Precise
calls:
l
1506/2 Number of rejected VBS/VGCS setup requests.
Name Q3 : aintOverLoadRejectedOpVbsVgcsSetup
Object : bsc
Function : number of rejected VBS/VGCS setup requests due to overload
situation
Event : receipt of a VBS/VGCS setup request when at least one SS7 TMU,
interface Node, or local TMU board is in overload situation
Class : equipment

Precise
calls:
l
1506/3 number of rejected VBS/VGCS assignment requests
Name Q3 : aintOverLoadRejectedOpVbsVgcsAssignment
Object : bsc
Function : number of rejected VBS/VGCS assignment requests.
Event : receipt of a VBS/VGCS assignment request when at least one SS7
TMU, interface Node, or local TMU board is in overload situation
Class : equipment
l
1506/4 number of perform location requests due to overload situation
Name Q3 : aintOverLoadRejectedOpPerformLocationReq
Object : bsc
Function : number of perform location requests requests.
Event : receipt of a perform location request when at least one SS7 TMU,
interface Node, or local TMU board is in overload situation
Class : equipment
Feature : CRe Q00590141

411--9001--125
l
1600 Connection duration of TCH/FRs or preempted PDTCH
Name Q3 : connectionDurationTchMoy
connectionDurationTchMax . . . . . Maximum connection duration
connectionDurationTchCum . . . . . Total connection duration
connectionDurationTchEch . . . . . . Number of samples
connectionDurationTchTrZoneMoy
connectionDurationTchTrZoneMax Maximum connection duration
connectionDurationTchTrZoneCum Total connection duration
connectionDurationTchTrZoneEch Number of samples
and maximum duration of TCH/FR or preempted PDTCH
connections in the inner or the outer zone of the cell, for the
observation period, expressed in ms
Event : TCH/FR or preempted PDTCH connection/disconnection
connection: start timer
disconnection:
• add it to the total of maximum TCH/FR or preempted PDTCH
connection durations in the observation period
Class : L1M
Note : This counter starts at the beginning of transmission of the SACCH
blocks on TCH/FR or preempted PDTCH, and stops at the end of
SACCH blocks transmission.
Precise
calls:


l
1601 Duration of maximum Downlink power use on busy SDCCHs
Name Q3 : downlinkPowerCtrlMaxSdcchMoy
downlinkPowerCtrlMaxSdcchMax Maximum duration
downlinkPowerCtrlMaxSdcchCum Total duration
downlinkPowerCtrlMaxSdcchEch . Number of samples
Object : bts
and maximum duration of maximum Downlink power use on the cell
SDCCHs for the observation period
Event : start/end of maximum SDCCH Downlink power use:
start: start timer
end:
• add it to the total of maximum Downlink power use durations
on SDCCHs in the observation period
Class : L1M

411--9001--125
Precise
calls:
completion)”
phase)”
l
1602 Duration of maximum Uplink power use on busy SDCCHs
Name Q3 : uplinkPowerCtrlMaxSdcchMoy
uplinkPowerCtrlMaxSdcchMax . . Maximum duration
uplinkPowerCtrlMaxSdcchCum . . Total duration
uplinkPowerCtrlMaxSdcchEch . . . Number of samples
Object : bts
and maximum duration of maximum Uplink power use on the cell
SDCCHs for the observation period
Event : start/end of maximum SDCCH Uplink power use:
start: start timer
end:

• add it to the total of maximum Uplink power use durations on

SDCCHs in the observation period
Class : L1M
Precise
calls:
completion)”
phase)”
l
1603 Connection duration of SDCCHs
Name Q3 : connectionDurationSdcchMoy
connectionDurationSdcchMax . . . . Maximum connection duration
connectionDurationSdcchCum . . . Total connection duration
connectionDurationSdcchEch . . . . Number of samples
and maximum duration of SDCCH connections in the cell for the
observation period, expressed in multiples of 470 ms

411--9001--125
Event : SDCCH connection/disconnection

disconnection:
• add it to the total of maximum SDCCH connection durations in
Class : L1M
Precise
calls:
completion)”
phase)”
Note : This counter starts at the beginning of transmission of SACCH blocks
on TCH, and stops at the end of SACCH blocks transmission.

l
1603/0 Connection duration of SDCCHs
Name Q3 : connectionDurationSdcchTrZoneMoy
connectionDurationSdcchTrZoneMax Maximum connection
duration
connectionDurationSdcchTrZoneCum Total connection duration
connectionDurationSdcchTrZoneEch Number of samples
and maximum duration of SDCCH connections in the inner or the
outer zone of the cell, for the observation period, expressed in
multiples of 470 ms
Event : SDCCH connection/disconnection
disconnection:
• add it to the total of maximum SDCCH connection durations in
Class : L1M
Precise
calls:
completion)”

411--9001--125

phase)”
Note : This counter starts at the beginning of transmission of SACCH blocks
on TCH, and stops at the end of SACCH blocks transmission.
l
1604 Average number of messages waiting in queue for transmission
on PCH-AGCH
Name Q3 : pchAveragedQueueLengthMoy
pchAveragedQueueLengthTs2Moy
pchAveragedQueueLengthMax . . . Max queued messages
pchAveragedQueueLengthTs2Max Max queued messages
pchAveragedQueueLengthCum . . . Total queued messages
pchAveragedQueueLengthTs2Cum Total queued messages
pchAveragedQueueLengthEch . . . Number of samples
pchAveragedQueueLengthTs2Ech . Number of samples
Object : bts

Location :
Name Q3 Location
pchAveragedQueueLengthMoy/Max/Cum/Ech CCCH--0
pchAveragedQueueLengthTs2Moy/Max/Cum/Ech CCCH--2
Function : average number ( = total number divided by the number of samples)

and maximum number of messages queued before being transmitted
on PCH-AGCH in the observation period; this internal BTS counter is
sent to the BSC in a CCCH_LOAD_INDICATION message
Event : message queuing, message transmission, internal sampling time-out
elapse:
queuing: step up by one the number of messages waiting for
transmission on PCH-AGCH
transmission: step down by one the number of messages waiting
for transmission on PCH-AGCH
• read the instantaneous value of the number of messages queued
• add it to the total number of messages queued for the
observation period
Class : monitoring

411--9001--125
Precise
Paging + Immediate Assignment
Queue size (120 PCHs for an S8000 BTS)
The queue is increased by a variable flow of Immediate Assignment

and all Paging messages (fresh and repeated) and served by a constant
flow of CCCH resources (3 blocks in case of BCCH combined and 9
blocks in case of not combined BCCH).
The priority order in the queue is Immediate Assignment never sent,
Fresh Paging, Repeated Paging, Immediate Assignment already sent.
The 1604 counter is related to the size of the queue of these Paging
messages queued before being transmitted on PCH--AGCH in the
observation period.
Precise
calls:
Packet Calls.
l
1605 Number of paging messages queued up not transmitted
Name Q3 : pchQueuePagesDiscarded
pchQueuePagesDiscardedTs2
Object : bts

Location :
Name Q3 Location
pchQueuePagesDiscarded CCCH--0
pchQueuePagesDiscarded2 CCCH--2
Function : number of paging messages removed from the paging queue before
being transmitted on PCH in the observation period
Event : receipt of a paging message queuing request that leads to remove the
latest request from the queue (the maximum number of paging
messages that can be queued is reached); receipt of a
CCCH_LOAD_INDICATION message from the BTS
Class : monitoring
Precise
Paging + Immediate Assignment
CCCH channel POOL

Queue size (120 PCHs for an S8000)
The queue is increased by a variable flow of Immediate Assignment

and all Paging messages (fresh and repeated) and served by a constant
flow of CCCH resources (3 blocks in case of BCCH combined and 9
blocks in case of not combined BCCH).
The priority order in the queue is Immediate Assignment never sent,
Fresh Paging, Repeated Paging, Immediate Assignment already sent.
The 1605 counter is related to Paging messages that are removed
from the queue because the maximum size of the queue is reached or
because the retransDuration timer (maximum time of a Paging
message in the queue) expiration.

411--9001--125
Precise
calls:
Packet Calls.
l
1606 Number of SDCCHs allocated in the zone (concentric cell)
Name Q3 : sdcchAllocated
sdcchAllocatedTrZone
Function : number of SDCCH allocations in the zone
Counter value calculation:
counter value that appears in the “Transceiver zone report”:
number of SDCCH allocations for the transceiver zone
counter value that appears in the “BTS report”: number of SDCCH
allocations for the entire cell (cell = sum of the cell transceiver
zones)
For a monozone network, the zone is the entire cell
Event : allocation of an SDCCH in the zone (transceiver zone or entire cell)
Class : allocation
Precise
calls:
completion)”

1607 Average number of SDCCHs used in the zone (concentric cell)

Name Q3 : sdcchAveragedUsedTrZoneMoy
sdcchAveragedUsedTrZoneMax . . Max SDCCH allocated
sdcchAveragedUsedTrZoneCum . . Total SDCCH allocated
sdcchAveragedUsedTrZoneEch . . . Number of samples
sdcchAveragedUsedMoy
sdcchAveragedUsedMax
sdcchAveragedUsedCum
sdcchAveragedUsedEch

maximum number of SDCCHs used in the zone
number of SDCCH used for the transceiver zone
used for the entire cell (cell = sum of the cell transceiver zones)
Event : SDCCH allocation/deallocation in a zone, internal sampling time-out

elapse:
allocation: step up by one the instantaneous value of the number of
SDCCHs used in the zone
deallocation: step down by one the instantaneous value of the
number of SDCCHs used in the zone
• read the instantaneous value of the number of SDCCHs used in
the zone
• add it to the total number of SDCCH allocations in the zone for
Class : allocation

411--9001--125
Precise
calls:
completion)”
phase)”
completion)”

l
1608 Number of SDCCH allocation failures in the zone (concentric
cell)
Name Q3 : sdcchRessourceFailure
sdcchRessourceFailureTrZone
Function : number of SDCCH allocation failures due to a lack of SDCCH in the
zone
number of SDCCH allocation failures for the transceiver zone
allocation failures for the entire cell (cell = sum of the cell
transceiver zones)
Event : SDCCH allocation refusal with cause “out of stock”
Class : allocation
Precise
calls:

411--9001--125
l
1609/0 Number of TCH/FR or preempted PDTCH allocated for traffic
in the zone (concentric cell)
Name Q3 : tchFrAllocatedTchAllocationTrZone
tchFrAllocatedTchAllocation
Function : number of TCH/FR or preempted PDTCH allocated in the zone for
traffic
number of TCH/FR or preempted PDTCH allocated the
trasnceiver zone
counter value that appears in the “BTS report”: number of TCH/FR
or preempted PDTCH allocated for the entire cell (cell = sum of the
cell transceiver zones)
Event : TCH/FR or preempted PDTCH allocation in the zone for traffic
Class : allocation
Precise
calls:


preemption)”
completion)”
l
1609/1 Number of TCH/FR allocated for call reestablishments in the
zone (concentric cell) (primo-allocation)
Name Q3 : tchFrAllocatedPrimoAllocationTrZone
tchFrAllocatedPrimoAllocation
Function : number of TCH/FR allocated in the zone for call reestablishment
number of TCH/FR allocated for the transceiver zone for call
reestablishment
allocated for the entire cell (cell = sum of the cell transceiver zones)
for call reestablishment
Event : TCH/FR allocation in the zone for call reestablishment
Class : allocation

411--9001--125
Precise
preempted to make a TCH channel) or CP (Com packet on PDTCH
channel).
This is because this counter is related to configured (static) TCH/FR
channel only, and does not take into account preempted PDTCH.
l
1609/2 Number of TCH/FR allocated because of SDCCH unavailability
Name Q3 : tchFrAllocatedOverflowAllocationTrZone
tchFrAllocatedOverflowAllocation
Function : number of TCH/FR allocated in the zone because of SDCCH
unavailability Counter value calculation:
number of TCH/FR allocated for the transceiver zone
allocated for the entire cell (cell = sum of the cell transceiver zones)
Event : TCH/FR allocation in the zone because of SDCCH unavailability
Class : allocation
Precise
calls:
completion)”

l
1609/3 Number of WPS full rate TCH allocations
Name Q3 : tchFrAllocatedWps
tchFrAllocatedWpsTrZone
Function : Number of WPS full rate TCH (including PDTCH) allocations
Event : Allocation of a full rate TCH
Class : allocation
l
1610/0 Number of half rate TCH allocations in Transciever Zone
Name Q3 : tchHrAllocatedTchAllocation
tchHrAllocatedTchAllocationTrZone
Function : Cumulative number of half rate TCH allocations.
Event : Allocation of a half rate TCH (including PDTCH) for a WPS call.

411--9001--125
l
1611/0 Average number of TCH/FR or preempted PDTCH used for
traffic in the zone (concentric cell)
Name Q3 : tchFrAveragedUsedTchAllocationMoy
tchFrAveragedUsedTchAllocationEch
tchFrAveragedUsedTchAllocationCum
tchFrAveragedUsedTchAllocationMax
tchFrAveragedUsedTchAllocationTrZoneMoy
tchFrAveragedUsedTchAllocationTrZoneMax
tchFrAveragedUsedTchAllocationTrZoneCum
tchFrAveragedUsedTchAllocationTrZoneEch
maximum number of TCH/FR or preempted PDTCH used for traffic
in the zone of the cell, obtained through internal sampling
number of TCH/FR or preempted PDTCH used for traffic for the
transceiver zone
or preempted PDTCH used for traffic for the entire cell
Event : TCH/FR or preempted PDTCH allocation/deallocation for traffic in a
zone, internal sampling time-out elapse:
TCH/FR or preempted PDTCH used for traffic in the zone
number of TCH/FR or preempted PDTCH used for traffic in the
zone
• read the instantaneous value of the number of TCH/FR or
preempted PDTCH used for traffic in the zone
• add it to the total number of TCH/FR or preempted PDTCH
allocations for traffic in the zone for the observation period
Class : allocation

Precise
calls:
1611.
preemption)”
completion)”

411--9001--125
l
1611/1 Average number of TCH/FR used for call reestablishments in the
Name Q3 : tchFrAveragedUsedPrimoAllocationMoy
tchFrAveragedUsedPrimoAllocationMax
tchFrAveragedUsedPrimoAllocationCum
tchFrAveragedUsedPrimoAllocationEch
tchFrAveragedUsedPrimoAllocationTrZoneMoy
tchFrAveragedUsedPrimoAllocationTrZoneMax
tchFrAveragedUsedPrimoAllocationTrZoneCum
tchFrAveragedUsedPrimoAllocationTrZoneEch
maximum number of TCH/FR used for call reestablishments in the
zone, obtained through internal sampling
number of TCH/FR used for call reestablisment for the transceiver
zone
used for call reestablishment for the entire cell
Event : TCH/FR allocation/deallocation for call reestablishment in a zone,
internal sampling time-out elapse:
TCH/FR used for call reestablishment in the zone
number of TCH/FR used for call reestablishment in the zone
• read the instantaneous value of the number of TCH/FR used for
call reestablishment in the zone
• add it to the total number of TCH/FR allocations for call
reestablishment in the zone for the observation period
Class : allocation

Precise
channel).
l
1611/2 Average number of TCH/FR used because of SDCCH
unavailability in the zone (concentric cell)
Name Q3 : tchFrAveragedUsedOverflowAllocationMoy
tchFrAveragedUsedOverflowAllocationMax
tchFrAveragedUsedOverflowAllocationCum
tchFrAveragedUsedOverflowAllocationEch
tchFrAveragedUsedOverflowAllocationTrZoneMoy
tchFrAveragedUsedOverflowAllocationTrZoneMax
tchFrAveragedUsedOverflowAllocationTrZoneCum
tchFrAveragedUsedOverflowAllocationTrZoneEch
maximum number of TCH/FR used because of SDCCH
unavailability in the zone, obtained through internal sampling
number of TCH/FR used because of SDCCH unavailability the
transceiver zone
counter value that appears in the “BTS report”: number of
TCH/FR because of SDCCH unavailabillity for the entire cell

411--9001--125
Event : TCH/FR allocation/deallocation in the zone because of SDCCH

unavailability, internal sampling time-out elapse:
TCH/FR used in the zone because of SDCCH unavailability
number of TCH/FR used in the zone because of SDCCH
unavailability
• read the instantaneous value of the number of TCH/FR used in
the zone because of SDCCH unavailability
• add it to the total number of TCH/FR allocations in the zone
because of SDCCH unavailability for the observation period
Class : allocation
l
1611/3 Average and maximum number of WPS full rate TCH allocations
Name Q3 : tchFrAveragedUsedWpsCum
tchFrAveragedUsedWpsEch
tchFrAveragedUsedWpsMax
tchFrAveragedUsedWpsMoy
tchFrAveragedUsedWpsTrZoneCum
tchFrAveragedUsedWpsTrZoneEch
tchFrAveragedUsedWpsTrZoneMax
tchFrAveragedUsedWpsTrZoneMoy
Function : Average and maximum number of WPS full rate TCH (including
PDTCH) allocations
Event : Allocation/de--allocation of a full rate TCH
Class : allocation

Precise
preempted to make a TCH channel).
channel. This counter is pegged on the traffic channel allocation for a
WPS call if the WPS Management flag is enabled. This counter is
pegged on the traffic channel de--allocation for a call inititiated as a
WPS call.

completion)”
l
1612/0 Average and maximum number of half rate TCH allocations
Name Q3 : tchHrAveragedUsedTchAllocationCum
tchHrAveragedUsedTchAllocationEch
tchHrAveragedUsedTchAllocationMax
tchHrAveragedUsedTchAllocationMoy
tchHrAveragedUsedTchAllocationTrZoneCum
tchHrAveragedUsedTchAllocationTrZoneEch
tchHrAveragedUsedTchAllocationTrZoneMax
tchHrAveragedUsedTchAllocationTrZoneMoy
Function : Average and maximum number of half rate TCH (including PDTCH)
allocations
Class : allocation

411--9001--125
l
1613 Number of TCH/FR and preemptable PDTCH allocation failures
Name Q3 : tchFrRessourceFailure
tchFrRessourceFailureTrZone
Function : number of allocation failures due to a lack of TCH/FR and
preemptable PDTCH in the zone, and due to a lack of free entries in
the queue
number of TCH/FR and preemptable PDTCH allocation failures
for the transceiver zone
and preemptable PDTCH allocation failures for the entire cell
Event : TCH/FR and preemptable PDTCH allocation refusal in the zone with
cause “out of stock”
Class : allocation
Note : This counter is also incremented if there are free TCHs, that are
reserved for allocation requests with the maximum priority
(allocPriorityThreshold attribute).
Also see C1039 counter for summation count at bts level.
Precise
calls:
preemption)”

l
1614 Number of TCH/HR and preemptable PDTCH allocation
failures in the zone (concentric cell)
Name Q3 : tchHrRessourceFailure
tchHrRessourceFailureTrZone
Function : number of failures caused by the lack of half rate TCH in a tdma_class
of the cell and a lack of free entries in the queue.
Event : Immediate refusal of allocation or refusal of queuing a TCH request.
Type : totalization
Class : TDMA
Note : The object identifier is used to set a mdCounterIdArray field.
l
1616/0 Average number of TCHs with highest priority queued up
Name Q3 : tchAveragedQueueLengthHighPriorityMoy
tchAveragedQueueLengthHighPriorityMax
tchAveragedQueueLengthHighPriorityCum
tchAveragedQueueLengthHighPriorityEch
Object : bts
maximum number of TCH allocation requests with maximum
priority queued for the cell, obtained through internal sampling
Event : TCH allocation request queued with cause “out of stock”, TCH
allocation, internal sampling time-out elapse:
queuing: step up by one the instantaneous value of the number of
TCHs with maximum priority queued
allocation: step down by one the instantaneous value of the number
of TCHs with maximum priority queued
• read the instantaneous value of the number of TCHs with
maximum priority queued
• add it to the total number of TCH allocation requests with
maximum priority queued for the observation period
Class : allocation

411--9001--125
Precise
calls:
l
1616/1 Average number of TCHs without highest priority queued up
Name Q3 : tchAveragedQueueLengthOtherPriorityMoy
tchAveragedQueueLengthOtherPriorityMax
tchAveragedQueueLengthOtherPriorityCum
tchAveragedQueueLengthOtherPriorityEch
Object : bts
maximum number of TCH allocation requests with non-maximum
priority queued for the cell, obtained through internal sampling
Event : TCH allocation request queued with cause “out of stock”, TCH
allocation, internal sampling time-out elapse:
queuing: step up by one the instantaneous value of the number of
TCHs with non-maximum priority queued
allocation: step down by one the instantaneous value of the number
of TCHs with non-maximum priority queued
• read the instantaneous value of the number of TCHs with
non-maximum priority queued
• add it to the total number of TCH allocation requests with
non-maximum priority queued for the observation period
Class : allocation

Precise
calls:
l
1617/0 Number of TCH allocation requests with highest priority queued
up unsatisfied
Name Q3 : tchQueuingExpirationHighPriority
Object : bts
Function : number of TCH allocation requests with maximum priority queued
and unsatisfied because of time-out elapse
Event : time-out elapse of a TCH allocation request with maximum priority
queued
Class : allocation
Precise
calls:
l
1617/1 Number of TCH allocation requests without highest priority
queued up unsatisfied
Name Q3 : tchQueuingExpirationOtherPriority
Object : bts
Function : number of TCH allocation requests with non-maximum priority
queued and unsatisfied because of time-out elapse

411--9001--125
Event : time-out elapse of a TCH allocation request with non-maximum

priority queued
Class : allocation
Precise
calls:
l
1618/0 Average waiting time of TCH allocation requests with highest
priority
Name Q3 : tchQueuingDurationHighPriorityMoy
tchQueuingDurationHighPriorityMax . . . . . . . Max wait durations
tchQueuingDurationHighPriorityCum . . . . . . Total wait durations
tchQueuingDurationHighPriorityEch . . . . . . . Number of samples
Object : bts
Function : average waiting duration ( = total duration divided by the number of
samples) and maximum waiting duration of TCH allocation requests
with maximum priority in the cell, obtained through internal
sampling. Counts both requests which are served, aborted or extracted
on timer expiration
Event : TCH allocation request with maximum priority queued, allocated,
removed from the queue, sampling time-out elapse:
queuing: start timer
allocation/removal: stop timer
• read timer
• add it to the total of waiting durations of TCH allocation
requests with maximum priority in the observation period
Class : allocation

Precise
calls:
l
1618/1 Average waiting time of TCH allocation requests without highest
priority
Name Q3 : tchQueuingDurationOtherPriorityMoy
tchQueuingDurationOtherPriorityMax . . . . . . Max wait durations
tchQueuingDurationOtherPriorityCum . . . . . . Total wait durations
tchQueuingDurationOtherPriorityEch . . . . . . . Number of samples
Object : bts
Function : average waiting duration ( = total duration divided by the number of
samples) and maximum waiting duration of TCH allocation requests
with non-maximum priority in the cell, obtained through internal
sampling. Counts both requests which are served, aborted or extracted
on timer expiration
Event : TCH allocation request with non-maximum priority queued,
allocated, removed from the queue, sampling time-out elapse:
queuing: start timer
allocation/removal: stop timer
• read timer
• add it to the total of waiting durations of TCH allocation
requests with non-maximum priority in the observation period
Class : allocation

411--9001--125
Precise
calls:
l
1619/0 Average number of free channels in interference band No.0
Name Q3 : channelAveragedIdlePerInterfBand0Moy
channelAveragedIdlePerInterfBand0Max . . . . Max in Band No.0
channelAveragedIdlePerInterfBand0Cum . . . . Total in Band No.0
channelAveragedIdlePerInterfBand0Ech . . . . . Number of samples
Object : bts
maximum number of radio idle channels in Interference band No.0,
Event : SDCCH or TCH allocation/deallocation, sampling time-out elapse
Class : interference
Precise
Measurement of interference is performed when in Idle mode. Before
the preemption, the PDTCH is assigned to the PCU and thus
considered as used from the BSS side. During the preemption, the
PDTCH is re--configured as TCH/FR and then assigned to a Circuit
Call. As a result, measurement of interferences involves configured
(static) TCH/FR only.
Note : In case of concentric cells (2 TDMAs in one cell):
The maximum value is the maximum number of radio channels in
the interference band of the TDMA which supports the greater
number of channels.
The cumulative value, which is relative to one TDMA, is therefore
the sum of numbers of radio channels in the interference band
divided by the number of TDMAs in the cell (i.e. 2).

l
Object : bts
Precise
number of channels.
l
Object : bts

411--9001--125

Precise

number of channels.

Object : bts


Precise
number of channels.
l
Object : bts

411--9001--125
Precise
number of channels.
l
1620 Number of unsuccessful “directed retry” handovers because the
list of eligible cells is empty
Name Q3 : directedRetryUnsuccessNoBts
Object : bts
Function : number of unsuccessful directed retry handovers because the list of
eligible cells is empty
Event : no reception of HANDOVER INDICATION with cause “directed
retry” after receipt of CONNECTION STATE RESPONSE from the
BTS (with an empty list of eligible cells and in the directed retry
handover procedure) and before the end of queuing phase
Class : handover
Precise
calls:

l
1621 Number of SAPI 3 session establishments for SMS
Name Q3 : sapi3SessionEstablishment
Object : bts
Function : number of SAPI sessions established to satisfy a short message
broadcast request in the cell
Event : receipt of one of the following messages from the BTS:
ESTABLISH INDICATION on SAPI3 (establishment requested
by a mobile)
ESTABLISH CONFIRM on transmission of ESTABLISH
REQUEST with SAPI3 value (receipt of a DTAP message on
SAPI3 from the MSC when no SAPI3 session is in-progress)
Class : SMS service
Precise
calls:
l
1622 Number of MS measurement messages not received
Name Q3 : msLostMeasurements
msLostMeasurementsTrZone
Function : number of mobile measurement messages not received by the inner or
the outer zone of the cell
Event : BSC receipt of STOP MEASUREMENT ACK with no measurement
message from a mobile
Class : L1M

411--9001--125
Precise
calls:
completion)”
phase)”

1623 Sum of Downlink signal strength measurements

Name Q3 : rxLevDownLink
rxLevDownLinkTrZone
Function : sum of the downlink signal strength measurements performed by the

mobiles on the inner or outer zone of the cell in the observation period,
expressed in GSM values [0 to 63]
Event : BSC receipt of STOP MEASUREMENT ACK from the BTS
Class : L1M
Precise
calls:

completion)”
phase)”

411--9001--125
l
1624 Sum of Uplink signal strength measurements
Name Q3 : rxLevUpLink
Function : sum of the uplink signal strength measurements performed by the
BTS on the cell in the observation period, expressed in GSM values
[0 to 63]
Class : L1M
Precise
calls:
completion)”
phase)”


l
1624 Sum of Uplink signal strength measurements
Name Q3 : rxLevUpLinkTrZone
Object : transceiver Zone
Function : sum of the uplink signal strength measurements performed by the
BTS on the inner or the outer zone of the cell in the observation period,
expressed in GSM values [0 to 63]
Class : L1M
Precise
calls:
completion)”

411--9001--125

phase)”
l
1625 Sum of Downlink signal quality measurements
Name Q3 : rxQualDownLink
Function : sum of the downlink signal quality measurements performed by the
mobiles on the cell in the observation period, expressed in 100xBER
Class : L1M
Precise
calls:
completion)”


phase)”
l
1625 Sum of Downlink signal quality measurements
Name Q3 : rxQualDownLinkTrZone
Function : sum of the downlink signal quality measurements performed by the
mobiles on the inner or the outer zone of the cell in the observation
period, expressed in 100xBER
Class : L1M
Precise
calls:

411--9001--125

completion)”
phase)”
Note : V12 counter
l
1626 Sum of Uplink signal quality measurements
Name Q3 : rxQualUpLink
Function : sum of the uplink signal quality measurements performed by the BTS
on the cell in the observation period, expressed in 100xBER
Class : L1M

Precise
calls:
completion)”
phase)”
(communication on SIGNALLING phase)”
l
1626 Sum of Uplink signal quality measurements
Name Q3 : rxQualUpLinkTrZone
Object : transceiverZone
Function : sum of the uplink signal quality measurements performed by the BTS
on the inner or the outer zone of the cell in the observation period,
expressed in 100xBER

411--9001--125

Class : L1M
Precise
calls:
completion)”
phase)”

l
1629/0 Number of Full-Rate channels activated for signaling
Name Q3 : channelActivateSignallingFullRate
Object : bts
Function : number of full-rate channels (SDCCH or TCH/FR) activated for
signaling in the cell
Event : transmission of CHANNEL ACTIVATE with CHANNEL
MODE = “signalling”
Class : assignment
Precise
calls:
completion in the case of Mobile Oritinating Calls)”
completion)”
l
1629/1 Number of Half-Rate channels activated for signaling
Name Q3 : channelActivateSignallingHalfRate
Object : bts
Function : number of half-rate channels (TCH/HR) activated for signaling in the
cell
Event : transmission of CHANNEL ACTIVATE with CHANNEL
MODE = “signalling”
Class : assignment

411--9001--125
Precise
calls:
completion in the case of Mobile Oritinating Calls)”
completion)”

l
1700 Average number of TCH/FR and preemptable PDTCH available
in multizone cell
Name Q3 : tchFrAveragedAvailable
tchFrAveragedAvailableMoy
tchFrAveragedAvailableMax
tchFrAveragedAvailableCum
tchFrAveragedAvailableEch
tchFrAveragedAvailableTrZoneMoy
tchFrAveragedAvailableTrZoneMax Max TCH/FR available
tchFrAveragedAvailableTrZoneCumTotal TCH/FR available
tchFrAveragedAvailableTrZoneEch Number of samples
maximum number of available radio TS for circuit calls, on a TDMA
class basis. Used resources are:
radio TS used for circuit call only
radio TS shared between circuit services and packet data services
number of TCH/FR and preemptable PDTCH available for the
transceiver zone
and preemptable PDTCH available for the entire cell
Formula : due to the minNbrGprsTS parameter defined on a cell basis, the exact
implementation of this counter is as follows:
Outer zone:
if the number of PDTCH in the cell is less than minNbrGprsTS, then
C1700_oz = Number_of_TCH_oz + Number_of_PDTCH_oz –
Number_of_PDTCH_cell
else
minNbrGprsTS
Inner zone:
C1700_iz = Number_of_TCH_iz + Number_of_PDTCH_iz
Where oz = outer zone and iz = inner zone

411--9001--125
Event : TDMA frame allocation/deallocation in the zone, radio channel

blocking, SYS INFO 5 and 6 acknowledgement not received, internal
available TCH/FR and preemptable PDTCH in the zone
deallocation/blocking/non-acknowledgement: step down by one
the instantaneous value of the number of available TCH/FR in the
zone
• read the instantaneous value of the number of available
TCH/FR and preempted PDTCH in the zone
• add it to the total number of available TCH/FR and preempted
PDTCH in the zone for the observation period
Class : allocation
Source : calculated by OMC--R agent
Precise
calls:
To sum it up, this counter is related to TCH/FR channel, preemptable
PDTCH and PDTCH not allocated to PCUSN.
1700.
Note : In order to guarantee a minimum of GPRS bandwidth, the operator
can set at the OMC--R level, the number of PDTCH which can not be
used by circuit call (minNbrGprsTS parameter; for more details
please refer to NTP < 124 >)

l
1701 Average number of SDCCH available in the zone (concentric cell)
Name Q3 : sdcchAveragedAvailableMoy
sdcchAveragedAvailableMax . . . . . Max available SDCCHs
sdcchAveragedAvailableCum . . . . Total available SDCCHs
sdcchAveragedAvailableEch . . . . . Number of samples
sdcchAveragedAvailableTrZoneMoy
sdcchAveragedAvailableTrZoneMax . . . . Max SDCCH available
sdcchAveragedAvailableTrZoneCum . . . Total SDCCH available
sdcchAveragedAvailableTrZoneEch . . . . Number of samples
maximum number of available SDCCHs -- allocated or available
obtained by internal sampling
number of SDCCH averaged available for the transceiver zone
averaged available for the entire cell (cell = sum of the cell
transceiver zones)
Event : SDCCH allocation/deallocation in the zone (transceiver zone or
entire cell), radio channel blocking, SYS INFO 5 and 6
acknowledgement not received, internal sampling time-out elapse:
available SDCCHs in the zone (transceiver zone or entire cell)
deallocation/blocking/non-acknowledgement: step down by one
the instantaneous value of the number of available SDCCHs in the
zone (transceiver zone or entire cell)
• read the instantaneous value of the number of available
SDCCHs in the zone
• add it to the total number of available SDCCHs in the zone for
Class : allocation

411--9001--125
Precise
calls:
l
1702 Number of channel allocation requests for mobiles over 35 km
(extended mode)
Name Q3 : channelRequestExtended
Object : bts
Function : number of channel allocation requests in the cell because of timing
Event : receipt of CHANNEL REQUEST containing a timing advance value
greater than 63
Class : setup
Precise
calls:
completion)”

l
1705/0 Number of TCH/FR activation for transparent data service with
a 1200/75 b/s transmission rate
Name Q3 : channelActivateTchFrDataT16
Object : bts
Function : number of full–rate channels activated for transparent data service
messages in the cell with a 1200/75 b/s transmission rate
CHANNEL MODE = “data” for a transparent service on a full--rate
TCH with a 1200/75 b/s transmission rate
Class : assignment
Precise
calls:
To sum it up, this counter is related to TCH/FR and preempted
PDTCH channels (circuit calls).
completion)”

411--9001--125
l
a 600 b/s transmission rate
Object : bts
messages in the cell with a 600 b/s transmission rate
TCH with a 600 b/s transmission rate
Class : assignment
Precise
calls:
completion)”

l
Object : bts
Class : assignment
Precise
calls:
completion)”

411--9001--125
l
Object : bts
Class : assignment
Precise
calls:
completion)”

l
Object : bts
Class : assignment
Precise
calls:
completion)”

411--9001--125
l
Object : bts
Class : assignment
Precise
calls:
completion)”

l
Object : bts
Class : assignment
Precise
calls:
completion)”

411--9001--125
l
1706/0 Number of channel activation for transparent data service on
half rate TCH
Name Q3 : channelActivateTchHrDataT16
Object : bts
Function : Number of channel activation for transparent data service on half rate
TCH.
Event : transmission of a CHANNEL_ACTIVATE message or of a
MODE_MODIFY message with a CHANNEL MODE record set to
“data” for a transparent service on a half rate TCH.
Class : assignment
Precise
calls:
completion)”

l
half rate TCH with a 600 b/s transmission rate.
Object : bts
TCH with a 600 b/s transmission rate.
Class : assignment
Precise
calls:
completion)”

411--9001--125
l
half rate TCH with a 1200 b/s transmission rate.
Object : bts
Class : assignment
Precise
calls:
completion)”

l
half rate TCH with a 2400 b/s transmission rate
Object : bts
Class : assignment
Precise
calls:
completion)”

411--9001--125
l
half rate TCH with a 4800 b/s transmission rate
Object : bts
Class : assignment
Precise
calls:
completion)”

l
1707/0 Number of TCH/FR activation for non--transparent data service
with a 6000 b/s transmission rate
Name Q3 : channelActivateTchFrDataNT6000
Object : bts
Function : number of full–rate channels activated for non--transparent data
service messages in the cell with a 6000 b/s transmission rate
CHANNEL MODE = “data” for a non--transparent service on a
full--rate TCH with a 6000 b/s transmission rate
Class : assignment
Precise
calls:
completion)”

411--9001--125
l
Object : bts
Class : assignment
Precise
calls:
completion)”

l
Object : bts
Class : assignment
Precise
calls:
completion)”

411--9001--125
l
1708/0 Number of channel activation for non transparent data service on
half rate TCH.
Name Q3 : channelActivateTchHrDataNT6000
Object : bts
Function : Cumulative number of channel activation for non transparent data
service on half rate TCH.
Event : Transmission of a CHANNEL_ACTIVATE message or of a
MODE_MODIFY message with a
CHANNEL MODE record set to data for a non transparent
service on a half rate TCH.
Type : CUM
Source : TBD
l
1709 Number of TCH/FR activation for transparent data service
Name Q3 : channelActTchFrDataT
Object : bts
messages in the cell
TCH
Class : assignment
completion)”

l
1710 Number of TCH/FR activation for non--transparent data service
Name Q3 : channelActTchFrDataNT
Object : bts
service messages in the cell
full--rate TCH
Class : assignment
completion)”
l
1711/0 Number of TCH/HR activation for transparent data service
Name Q3 : channelActTchHrDataT
Object : bts
Function : number of half–rate channels activated for transparent data service
CHANNEL MODE = “data” for atransparent service on a full--rate
TCH
Class : assignment

411--9001--125

completion)”
l
1712/0 Number of TCH/HR activation for transparent data service
Name Q3 : channelActTchHrDataNT
Object : bts
Function : number of half–rate channels activated for transparent data service
CHANNEL MODE = “data” for atransparent service on a full--rate
TCH
Class : assignment
completion)”

l
1714 Duration of the overload situation
Name Q3 : btsOverloadDurationMoy
btsOverloadDurationMax
btsOverloadDurationCum
btsOverloadDurationEch
Object : bts
Function : duration of the overload situation: the number of free TCHs in the cell
is lower than the minimum threshold, or the number of queued TCH
requests is greater than the threshold.
Note that the number of free TCHs does not take preemptable PDTCH
into account.
Event : allocation/de--allocation of a TCH, queueing of a TCH request,
liberation of a queued TCH request, block/unblock of a TCH, or
TDMA attribution/removal
Class : allocation
Precise
calls:
But it is not concerned by CCP (Circuit Calls on PDTCH preempted
to make a TCH channel) or CP calls (Com packet on PDTCH
channel).
l
1715 Number of attempts of assignation of a TCH/FR or a preempted
PDTCH for dualband mobiles
Name Q3 : attemptedTchFrSeizuresMsDualb
Object : bts
Function : number of attempts of assignation of a TCH/FR or a preempted
PDTCH for dualband mobiles
Event : transmission of ASSIGNMENT COMMAND to the mobile
Class : assignment

411--9001--125
Feature : Dualband cell management (TF875 - V12)

Precise
calls:
completion)”
l
1716 Number of successful TCH/FR or a preempted PDTCH
assignations for dualband mobiles
Name Q3 : successfulTchFrSeizuresMsDualb
Object : bts
Function : number of successful TCH/FR or a preempted PDTCH assignations
for dualband mobiles
Event : receipt of ASSIGNMENT COMPLETE message by the BSC
Class : assignment
Precise
calls:


completion)”
l
1717 Number of frames TRAU downlink received
Name Q3 : abisTrauFrameDlReceived
Object : bts
Function : number of frames TRAU downlink received
Event : receipt of a RF channel release ack message
Feature : PCM error correction (FM660 - V12)
Precise
calls:
completion)”
l
1718 Number of frames TRAU downlink corrected
Name Q3 : abisTrauFrameCorrected
Object : bts
Function : number of frames TRAU downlink corrected

411--9001--125

Precise
calls:
completion)”
l
1719 Number of frames TRAU downlink that cannot be corrected
Name Q3 : abisTrauFrameMuted
Object : bts
Function : number of frames TRAU downlink that cannot be corrected
Precise
calls:


completion)”
l
1720 Number of radio frames uplink received
Name Q3 : radioFrameUlReceived
Object : bts
Function : number of radio frames uplink received
Precise
calls:
completion)”
Note: FER monitoring only concerns the speech frames (Full Rate and Enhanced
Full Rate) and does not depend on the ECU activation status.
l
1721/0 Number of erroneous frames
Name Q3 : ecuActivation
Object : bts
Function : number of erroneous frames

411--9001--125

Precise
calls:
completion)”
Note: FER monitoring only concerns the speech frames (Full Rate and Enhanced
Full Rate) and does not depend on the ECU activation status.
l
1722/0 Number of VBS (Voice Broadcast Service) call initiations
Name Q3 : asciCallInitiationVbs
Object : bts
Function : number of VBS (Voice Broadcast Service) call initiations
Event : receipt of a CM SERVICE REQUEST, IMMEDIATE_SETUP,
IMMEDIATE_SETUP2 or HO_REQUEST message
Class : asci
Feature : GSM--R
Precise

l
1722/1 Number of VGCS (Voice Group Call Service) call initiations
Name Q3 : asciCallInitiationVgcs
Object : bts
Function : number of VGCS (Voice Group Call Service) call initiations
Event : receipt of a CM SERVICE REQUEST, IMMEDIATE_SETUP,
IMMEDIATE_SETUP2, or HO_REQUEST message
Class : asci
Feature : GSM--R
Precise
l
1723 Number of inband pagings taken into account
Name Q3 : asciInbandPaging
Object : bts
Function : number of inband pagings taken into account
Event : receipt of a PAGING message if:
eMLPP present
eMLPP precedence > O&M threshold
VBS call in progress
Class : asci
Feature : GSM--R
Precise
Note : If several calls are in progress, only one counter update is performed.

411--9001--125
l
1724 Number of inband notifications taken into account
Name Q3 : asciInbandNotification
Object : bts
Function : number of inband notifications taken into account
Event : receipt of a VBS_ASSIGNMENT_REQUEST message if:
eMLPP present
eMLPP precedence > O&M threshold
call in progress
Class : asci
Feature : GSM--R
Precise
Note : If several calls are in progress, only one counter update is performed.
l
1725 Number of preemptions performed on a call in progress in the cell
Name Q3 : asciPreemptionPerformed
Object : bts
Function : number of preemptions performed on a call in progress in the cell
Event : preemption of a call (i.e. conditions on GSM priority satisfied)
Class : asci
Feature : GSM--R
Precise

l
1726/0 Number of fallbacks from a required data rate to another data
rate with cause lack of resources
Name Q3 : dataNtRateFbTchResLack
Object : bts
Function : number of fallbacks from a required data rate to another data rate with
cause lack of resources
Event : configuration mismatch or response from radio allocator
Class : allocation
Precise
calls:
l
1726/1 Number of fallbacks from a required data rate to another data
rate with cause configuration not allowed
Name Q3 : dataNtRateFbTchConfNotAllowed
Object : bts
Function : number of fallbacks from a required data rate to another data rate with
cause configuration not allowed
Event : configuration mismatch or response from radio allocator
Class : allocation
Precise
calls:

411--9001--125
l
1730 Number of signaling channels allocated for replies to paging
Name Q3 : pagingResponse
Object : bts
Function : number of signaling channel allocation requests for “reply to paging
request” in the cell (cause = xx001 or xx100)
Event : receipt of CHANNEL REQUEST with cause “reply to paging
request”
Class : establishment
Precise
calls:
completion)”
l
1744 Number of TCH/FR or preempted PDTCH allocated in the cell
Name Q3 : tchFrAllocated
Function : number of TCH/FR or preempted PDTCH allocated in the cell
Event : TCH/FR or preempted PDTCH allocation in the cell
Class : allocation


preemption)”
completion)”
completion)”
l
1744 Number of TCH/FR or preempted PDTCH allocated in the cell
Name Q3 : tchFrAllocatedTrZone
Function : number of TCH/FR or preempted PDTCH allocated in the inner or the
Event : TCH/FR or preempted PDTCH allocation in the cell
Class : allocation

411--9001--125

preemption)”
completion)”
completion)”
l
1745/0 Number of Half--rate TCH allocations in the cell
Name Q3 : tchHrAllocated
tchHrAllocatedNsc
tchHrAllocatedTrZone
Function : number of half--rate TCH allocations in the cell
Event : allocation of a half rate TCH
Class : allocation

l
1746 Average number of TCH/FR or preempted PDTCH used in the
concentric cell and zone
Name Q3 : tchFrAveragedUsedMoy
tchFrAveragedUsedMax
tchFrAveragedUsedCum
tchFrAveragedUsedEch
tchFrAveragedUsedTrZoneMax
tchFrAveragedUsedTrZoneMoy
tchFrAveragedUsedTrZoneCum
tchFrAveragedUsedTrZoneEch
maximum number of TCH/FR or preempted PDTCH used in the inner
or outer zone of the cell, obtained through internal sampling.
Event : TCH/FR or preempted PDTCH allocation/deallocation:
TCH/FR or preempted PDTCH used in the cell or zone.
number of TCH/FR or preempted PDTCH used in the cell or zone.
Class : allocation
Precise
1746.
preemption)”
completion)”

411--9001--125

completion)”
l
1747/0 Average, maximum, mimium, and total number of half rate
TCH allocations
Name Q3 : tchHrAveragedUsedCum
tchHrAveragedUsedEch
tchHrAveragedUsedMax
tchHrAveragedUsedMoy
tchHrAveragedUsedTrZoneCum
tchHrAveragedUsedTrZoneEch
tchHrAveragedUsedTrZoneMax
tchHrAveragedUsedTrZoneMoy
Function : average and maximum number of half rate TCH allocations.
Event : allocation/de--allocation of a half rate TCH.
Class : setup
l
1748 Number of channel allocation requests
Name Q3 : channelRequest
Object : bts
Function : number of channel allocation requests in the cell
Event : receipt of CHANNEL REQUIRED
Class : setup


completion)”
l
1749 Number of successful immediate assignments
Name Q3 : immediateAssignmentSuccess
Object : bts
Function : number of immediate assignments
CHANNEL REQUEST
Class : setup
completion)”
1750 Number of ESTABLISH INDICATION messages in establish-

ment phase received
Name Q3 : estabIndicSignalling
estabIndicSignallingEmerency8w
estabIndicSignallingPiggybacked
Object : bts
SDCCH or TCH if no SDCCH is available
Event : receipt of ESTABLISH INDICATION
Class : setup

411--9001--125

completion)”
l
1751 Number of immediate assignments rejected
Name Q3 : immediateAssignmentReject
Object : bts
Function : number of immediate assignments rejected
Event : transmission of IMMEDIATE ASSIGN REJECT to the mobile
Class : release
l
1752 Number of releases while the communication is in “signalling
phase” and no cell yet associated to the communication
Name Q3 : signallingReleaseNoBts
Object : bsc
Function : number of releases while the communication is in “signalling phase”
and no cell yet associated to the communication
Event : All the event causes of 1162/n counters
Class : release
1753 Number of releases while the communication is in “signalling

phase” and a cell associated to the communication
Name Q3 : signallingReleaseBts
Object : bts
Function : number of releases while the communication is in “signalling phase”
and a cell associated to the communication


Class : release
phase)”
l
1754 Number of releases while the communication is in traffic “phase”
Name Q3 : trafficRelease
Object : bts
Function : number releases while the communications is in “traffic” phase
Class : release

411--9001--125
l
1756/0 Number of refusals to accept an intra--cell handover in the cell on
TCH with cause lack of radio resources
Name Q3 : hoFailureIntraBtsTchRadioLack
Object : bts
Object : number of refusals to accept an intra--cell handover on TCH in the cell
with cause lack of radio resources
Event : lack of radio resources
Class : handover
l
1756/1 Number of refusals to accept an intra--cell handover on TCH in
the cell with cause receipt from the BTS of a CHANNEL ACTI-
VATE NACK message
Name Q3 : hoFailureIntraBtsTchChannelActivateNack
Object : bts
Function : number of refusals to accept an intra--cell handover on TCH in the cell
with cause receipt from the BTS of CHANNEL ACTIVATE NACK
message
Event : receipt from the BTS of a CHANNEL ACTIVATE NACK message
Class : handover
l
the cell with cause expiration of TchnAck timer
Name Q3 : hoFailureIntraBtsTchTchnAckTimerExp
Object : bts
Function : number of refusals to accept an intra--cell handover on TCH in the cell
with cause expiration of TchnAck timer
Event : expiration of TchnAck timer
Class : handover

l
1757/0 Number of refusals to accept an intra--cell handover in the cell on
SDCCH with cause lack of radio resources
Name Q3 : hoFailureIntraBtsSdcchRadioLack
Object : bts
Function : number of refusals to accept an intra--cell handover on SDCCH in the
cell with cause lack of radio resources
Class : handover
l
1757/1 Number of refusals to accept an intra--cell handover on SDCCH
in the cell with cause receipt from the BTS of a CHANNEL
ACTIVATE NACK message
Name Q3 : hoFailureIntraBtsSdcchChannelActivateNack
Object : bts
cell with cause receipt from the BTS of CHANNEL ACTIVATE
NACK message
Class : handover
l
the cell with cause expiration of TchnAck timer
Name Q3 : hoFailureIntraBtsSdcchTchnAckTimerExp
Object : bts
cell with cause expiration of TchnAck timer
Class : handover

411--9001--125
l
1758/0 Number of incoming intra BSS handover requests, on TCH with
cause lack of radio resources, which have been refused
Name Q3 : hoFailureIncomingIntraBssTchRadioLack
Object : bts
Function : number of incoming intra BSS handover requests, on TCH with cause
lack of radio resources, which have been refused
Class : handover
l
cause incoming handover not allowed in the cell, which have been
refused
Name Q3 : hoFailureIncomingIntraBssTchHoNotAllowed
Object : bts
incoming handover not allowed in the cell, which have been refused
Event : incoming handover not allowed in the cell
Class : handover
l
cause receipt from the BTS of a CHANNEL ACTIVATE NACK
message, which have been refused
Name Q3 : hoFailureIncomingIntraBssTchChannelActivateNack
Object : bts
receipt from the BTS of a CHANNEL ACTIVATE NACK message,
which have been refused
Class : handover

l
cause expiration of TchnAck timer, which have been refused
Name Q3 : hoFailureIncomingIntraBssTchTchnAckTimerExp
Object : bts
expiration of TchnAck timer, which have been refused
Class : handover
l
cause target cell and speech coding algorithm incompatible OR
target cell and channel mode incompatible AND no possible
fallback
Name Q3 : hoFailureIncomingIntraBssTchIncompatible
Object : bts
target cell and speech coding algorithm incompatible OR target cell
and channel mode incompatible AND no possible fallback
Event : target cell and speech coding algorithm incompatible OR target cell
Class : handover
Note: Incompatibility for target cell can be hardware (14K5 or HSCSD) or
configuration (EFR & 14K5 & HSCSD).
l
1759/0 Number of incoming intra BSS handover requests, on SDCCH
with cause lack of radio resources, which have been refused
Name Q3 : hoFailureIncomingIntraBssSdcchRadioLack
Object : bts
Function : number of incoming intra BSS handover requests, on SDCCH with

411--9001--125

Class : handover
l
with cause incoming handover not allowed in the cell, which have
been refused
Name Q3 : hoFailureIncomingIntraBssSdcchHoNotAllowed
Object : bts
refused
Class : handover
l
with cause receipt from the BTS of a CHANNEL ACTIVATE
NACK message, which have been refused
Name Q3 : hoFailureIncomingIntraBssSdcchChannelActivateNack
Object : bts
Class : handover

l
with cause expiration of TchnAck timer, which have been refused
Name Q3 : hoFailureIncomingIntraBssSdcchTchnAckTimerExp
Object : bts
Class : handover
l
1760/0 Number of incoming inter BSS handover requests, on TCH with
Name Q3 : hoFailureIncomingInterBssTchRadioLack
Object : bts
Function : number of incoming inter BSS handover requests, on TCH with cause
Class : handover
l
cause lack of terrestrial resources, which have been refused
Name Q3 : hoFailureIncomingInterBssTchTerrestLack
Object : bts
lack of terrestrial resources, which have been refused
Event : lack of terrestrial resources
Class : handover

411--9001--125
l
refused
Name Q3 : hoFailureIncomingInterBssTchHoNotAllowed
Object : bts
Class : handover
l
Name Q3 : hoFailureIncomingInterBssTchChannelActivateNack
Object : bts
Class : handover
l
Name Q3 : hoFailureIncomingInterBssTchTchnAckTimerExp
Object : bts
Class : handover

l
cause CIC and speech coding algorithm incompatible OR target
cell and speech coding algorithm incompatible OR CIC and
channel mode incompatible OR target cell and channel mode
incompatible AND no possible fallback
Name Q3 : hoFailureIncomingInterBssTchCICIncompatible
Object : bts
CIC and speech coding algorithm incompatible OR target cell and
speech coding algorithm incompatible OR CIC and channel mode
incompatible OR target cell and channel mode incompatible AND no
possible fallback
Event : CIC and speech coding algorithm incompatible OR target cell and
possible fallback
Class : handover
Note : Incompatibility for CIC can be hardware or configuration.
Incompatibility for target cell can be hardware or configuration.
l
1761/0 Number of incoming inter BSS handover requests, on SDCCH
Name Q3 : hoFailureIncomingInterBssSdcchRadioLack
Object : bts
Function : number of incoming inter BSS handover requests, on SDCCH with
Class : handover

411--9001--125
l
with cause lack of terrestrial resources, which have been refused
Name Q3 : hoFailureIncomingInterBssSdcchTerrestLack
Object : bts
Class : handover
l
been refused
Name Q3 : hoFailureIncomingInterBssSdcchHoNotAllowed
Object : bts
refused
Class : handover
l
Name Q3 : hoFailureIncomingInterBssSdcchChannelActivateNack
Object : bts
Class : handover

l
Name Q3 : hoFailureIncomingInterBssSdcchTchnAckTimerExp
Object : bts
Class : handover
l
1762/0 Number of outgoing intra BSS handover requests, on TCH with
Name Q3 : hoFailureOutgoingIntraBssTchRadioLack
Object : bts
Function : number of outgoing intra BSS handover requests, on TCH with cause
Class : handover
l
refused
Name Q3 : hoFailureOutgoingIntraBssTchHoNotAllowed
Object : bts
Class : handover

411--9001--125
l
1762/2 Number of outgoing intra BSS handover requests, on TCH
Name Q3 : hoFailureOutgoingIntraBssTchChannelActivateNack
Object : bts
Class : handover
l
Name Q3 : hoFailureOutgoingIntraBssTchTchnAckTimerExp
Object : bts
Class : handover

l
Name Q3 : hoFailureOutgoingIntraBssTchIncompatible
Object : bts
target cell and speech coding algorithm incompatible OR target cell
and channel mode incompatible AND no possible fallback, which
have been refused
Event : target cell and speech coding algorithm incompatible OR target cell
Class : handover
Note : Incompatibility for target cell can be hardware or configuration
l
1763/0 Number of outgoing intra BSS handover requests, on SDCCH
Name Q3 : hoFailureOutgoingIntraBssSdcchRadioLack
Object : bts
Function : number of outgoing intra BSS handover requests, on SDCCH with
Class : handover

411--9001--125
l
been refused
Name Q3 : hoFailureOutgoingIntraBssSdcchHoNotAllowed
Object : bts
refused
Class : handover
l
Name Q3 : hoFailureOutgoingIntraBssSdcchChannelActivateNack
Object : bts
Class : handover
l
Name Q3 : hoFailureOutgoingIntraBssSdcchTchnAckTimerExp
Object : bts
Class : handover

l
1764/0 Number of outgoing inter BSS handover requests, on TCH with
Name Q3 : hoFailureOutgoingInterBssTchRadioLack
Object : bts
Function : number of outgoing inter BSS handover requests, on TCH with cause
Class : handover
l
Name Q3 : hoFailureOutgoingInterBssTchTerrestLack
Object : bts
lack of terrestrial resources, which have been refused
Class : handover
l
refused
Name Q3 : hoFailureOutgoingInterBssTchHoNotAllowed
Object : bts
Class : handover

411--9001--125
l
cause T7 timer expiration, which have been refused
Name Q3 : hoFailureOutgoingInterBssTchT7TimerExp
Object : bts
T7 timer expiration, which have been refused
Event : T7 timer expiration
Class : handover
l
cause “every other cases”, which have been refused
Name Q3 : hoFailureOutgoingInterBssTchOtherCases
Object : bts
“every other cases”, which have been refused
Event : “every other cases”
Class : handover
l
cause CIC and speech coding algorithm incompatible OR target
cell and speech coding algorithm incompatible OR CIC and
channel mode incompatible OR target cell and channel mode
incompatible AND no possible fallback, which have been
refused
Name Q3 : hoFailureOutgoingInterBssTchIncompatible
Object : bts
CIC and speech coding algorithm incompatible OR target cell and
possible fallback, which have been refused


Class : handover
Note : Incompatibility for CIC or target cell can be hardware or
configuration.
l
1765/0 Number of outgoing inter BSS handover requests, on SDCCH
Name Q3 : hoFailureOutgoingInterBssSdcchRadioLack
Object : bts
Function : number of outgoing inter BSS handover requests, on SDCCH with
Class : handover
l
with cause lack of terrestrial resources, which have been refused
Name Q3 : hoFailureOutgoingInterBssSdcchTerrestLack
Object : bts
Class : handover

411--9001--125
l
with cause incoming handover not allowed in the cell, which
have been refused
Name Q3 : hoFailureOutgoingInterBssSdcchHoNotAllowed
Object : bts
refused
Class : handover
l
with cause T7 timer expiration, which have been refused
Name Q3 : hoFailureOutgoingInterBssSdcchT7TimerExp
Object : bts
cause T7 timer expiration, which have been refused
Class : handover
l
with cause “every other cases”, which have been refused
Name Q3 : hoFailureOutgoingInterBssSdcchOtherCase
Object : bts
cause “every other cases”, which have been refused.
Class : handover

l
1768/0 Number of failures to execute intra_bss handover from the cell
on TCH.
Name Q3 : hoUnsuccessOutgoingIntraCellTchReturnOldChannel
Object : bts
Function : number of failures to execute intra_bss handover from the cell caused
by a mobile that returns to the old channel (HANDOVER FAILURE
before T3103 timer expiration).
Event : mobile returns to the old channel (HANDOVER FAILURE before
T3103 timer expiration)
Class : handover
l
on TCH.
Name Q3 : hoUnsuccessOutgoingIntraCellTchT3103TimerExp
Object : bts
by T3103 timer expiration.
Class : handover
l
1769/0 Number of failures to execute intra_bss handover from the cell on
SDCCH.
Name Q3 : hoUnsuccessOutgoingIntraCellSdcchReturnOldChannel
Object : bts
by a mobile that returns to the old channel (HANDOVER FAILURE
before T3103 timer expiration).
Class : handover

411--9001--125
l
on SDCCH.
Name Q3 : hoUnsuccessOutgoingIntraCellSdcchT3103TimerExp
Object : bts
by T3103 timer expiration.
Class : handover
l
1770/0 Number of refusals to accept an outgoing inter--cell handover on
TCH in the cell with cause mobile returns to the old channel
Name Q3 : hoUnsuccessOutgoingInterCellTchReturnOldChannel
Object : bts
Function : number of refusals to accept an outgoing inter--cell handover on TCH
in the cell with cause mobile returns to the old channel
Event : mobile returns to the old channel
Class : handover
l
TCH in the cell with cause T3103 timer expiration
Name Q3 : hoUnsuccessOutgoingInterCellTchT3103TimerExp
hoUnsuccessOutgoingInterCellTchT3107TimerExp8w
Object : bts
in the cell with cause T3103 timer expiration
Class : handover

l
TCH in the cell with cause “every other cases”
Name Q3 : hoUnsuccessOutgoingInterCellTchOtherCases
Object : bts
in the cell with cause “every other cases”
Class : handover
l
SDCCH in the cell with cause mobile returns to the old channel
Name Q3 : hoUnsuccessOutgoingInterCellSdcchReturnOldChannel
Object : bts
Function : number of refusals to accept an outgoing inter--cell handover on
SDCCH in the cell with cause mobile returns to the old channel
Class : handover
l
SDCCH in the cell with cause T3103 timer expiration
Name Q3 : hoUnsuccessOutgoingInterCellSdcchT3103TimerExp
Object : bts
SDCCH in the cell with cause T3103 timer expiration
Class : handover

411--9001--125
l
SDCCH in the cell with cause “every other cases”
Name Q3 : hoUnsuccessOutgoingInterCellSdcchOtherCases
Object : bts
Class : handover
l
1772/0 Number of failures to execute intra_bss handover to the cell on
TCH.
Name Q3 : hoUnsuccessIncomingIntraCellTchReturnOldChannel
Object : bts
Function : number of failures to execute intra_bss handover to the cell on TCH
caused by a mobile that returns to the old channel (HANDOVER
FAILURE before T3103 timer expiration).
Class : handover
l
TCH.
Name Q3 : hoUnsuccessIncomingIntraCellTchT3103TimerExp
Object : bts
Function : number of failures to execute intra_bss handover to the cell on TCH
caused by T3103 timer expiration.
Class : handover

l
SDCCH.
Name Q3 : hoUnsuccessIncomingIntraCellSdcchReturnOldChannel
Object : bts
Function : number of failures to execute intra_bss handover to the cell on
SDCCH caused by a mobile that returns to the old channel
(HANDOVER FAILURE before T3103 timer expiration).
Class : handover
l
SDCCH.
Name Q3 : hoUnsuccessIncomingIntraCellSdcchT3103TimerExp
Object : bts
Function : number of failures to execute intra_bss handover to the cell on
SDCCH caused by T3103 timer expiration.
Class : handover
l
1774/0 Number of refusals to accept an incoming inter--bss handover on
TCH in the cell with cause timer expiration
Name Q3 : hoUnsuccessIncomingInterBssTchTimerExp
Object : bts
Function : number of refusals to accept an incoming inter--bss handover on TCH
in the cell with cause timer expiration
Event : timer expiration (expiration of ThndCom timer before receipt of
ABIS HANDOVER COMPLETE from the MSC or receipt of
CLEAR COMMAND message from the MSC)
Class : handover

411--9001--125
l
TCH in the cell with cause “every other cases”
Name Q3 : hoUnsuccessIncomingInterBssTchOtherCases
Object : bts
Function : number of refusals to accept an incoming inter--bss handover on TCH
in the cell with cause “every other cases”
Event : “every other cases” (receipt of a CLEAR COMMAND message with
a cause set to a different value than “handover successful” or “Call
control”
Class : handover
l
SDCCH in the cell with cause timer expiration
Name Q3 : hoUnsuccessIncomingInterBssSdcchTimerExp
Object : bts
Function : number of refusals to accept an incoming inter--bss handover on
SDCCH in the cell with cause timer expiration
Event : timer expiration (expiration of ThndCom timer before receipt of
ABIS HANDOVER COMPLETE from the MSC or receipt of
CLEAR COMMAND message from the MSC)
Class : handover
l
Name Q3 : hoUnsuccessIncomingInterBssSdcchOtherCases
Object : bts
Function : number of refusals to accept an incoming inter--bss handover on

Event : “every other cases” (receipt of a CLEAR COMMAND message with

a cause set to a different value than “handover successful” or “Call
control”
Class : handover
l
1776 Number of handovers on TCH required
Name Q3 : hoRequiredTch
Object : bts
Function : number of handovers on TCH required
Tchoke expiry
Class : handover
l
1777 Number of handovers on SDCCH required
Name Q3 : hoRequiredSdcch
Object : bts
Function : number of handovers on SDCCH required

411--9001--125

Tchoke expiry
Class : handover
l
1778 Number of abnormal releases while the communication is in “sig-
nalling phase” and a cell associated to the communication
Name Q3 : signallingAbnormalReleaseCell
Object : bts
Function : number of abnormal releases while the communication is in
“signalling phase” and a cell associated to the communication
Event : All the event causes of 1163/n counters except those of 1163/5 and
1163/24 counters
Class : release
Precise
calls:
l
1779 Number of abnormal releases while the communication is in
“traffic phase”
Name Q3 : trafficAbnormalRelease
Object : bts
Function : number abnormal releases while the communications is in “traffic
phase”

Event : All the event causes of 1164/n counters except the one of 1164/20
counter
Class : release
Precise
calls:

Name Q3 : hoSuccessOutgoingTch
Object : bts
TCH using only classic handovers and no AMR handovers
Class : handover
1781 Number of successful incoming handovers in the cell

Name Q3 : hoSuccessIncomingTch
Object : bts
Function : number of successful incoming intra–bss or inter–bss handovers on
TCH

411--9001--125

(intra–bss and inter--bss handover)
Class : handover
l
1782 Number of handover requirements which are not treated by the
BSC because the ping--pong handover configuration is not
allowed
Name Q3 : hoBtsRejected
Object : bts
Function : number of handover requirements which are not treated by the BSC
because the ping--pong handover configuration is not allowed
Event : receipt of HANDOVER INDICATION message from the BTS
Class : handover
Precise
calls:
Feature : General protection against ping--pong handovers (TF821 - V12)
Note : A non essential handover to a cell from which the mobile has already
been rejected due to alarm reason is not treated.
This counter is incremented only for ping--pong handover
functionality.

l
from the main frequency band to the same frequency band of the
network
Name Q3 : hoRequestOutgoingMbandMbandMsDualb
Object : bts
requested from the main frequency band to the same frequency band
of the network
Event : attempt to select a resource of an eligible cell
Class : handover
Precise
calls:
Note : The originated and target resources are in the main frequency band of
the network.
l
from the second frequency band to the same frequency band of
the network
Name Q3 : hoRequestOutgoingEbandEbandMsDualb
Object : bts
requested from the second frequency band to the same frequency
band of the network

411--9001--125

Class : handover
Precise
calls:
Note : The originated and target resources are in the second frequency band
of the network.
l
from the second frequency band to the main frequency band of
the network
Name Q3 : hoRequestOutgoingEbandMbandMsDualb
Object : bts
requested from the second frequency band the main frequency band of
the network
Class : handover

Precise
calls:
Note : The target resource is in the main frequency band of the network
whereas the originated resource is in the second frequency band.
l
from the main frequency band to the same frequency band of the
network
Name Q3 : hoSuccessOutgoingMbandMbandMsDualb
Object : bts
TCH, from the main frequency band to the same frequency band of
the network
Class : handover
Precise
calls:

411--9001--125

l
from the second frequency band to the same frequency band of
the network
Name Q3 : hoSuccessOutgoingEbandEbandMsDualb
Object : bts
TCH, from the second frequency band to the same frequency band of
the network
Class : handover
Precise
calls:

l
from the second frequency band to the main frequency band of
the network
Name Q3 : hoSuccessOutgoingEbandMbandMsDualb
Object : bts
TCH, from the second frequency band to the main frequency band of
the network
Class : handover
Precise
calls:
l
1789 Number of outgoing handover executions by dualband mobiles
for the cell from the main frequency band to the second
Name Q3 : hoExecutionOutgoingMbandEbandMsDualb
Object : bts
Function : number of outgoing handover (intra-bss or inter-bss) executions by
dualband mobiles for the cell, from the main frequency band to the
second frequency band of the network

411--9001--125
Event : transmission of ASSIGN COMMAND message

Class : handover
Precise
calls:
l
for the cell from the main frequency band to the same frequency
band of the network
Name Q3 : hoExecutionOutgoingMbandMbandMsDualb
Object : bts
dualband mobiles for the cell, from the main frequency band to the
Class : handover
Precise
calls:


l
for the cell from the second frequency band to the same
Name Q3 : hoExecutionOutgoingEbandEbandMsDualb
Object : bts
dualband mobiles for the cell, from the second frequency band to the
Class : handover
Precise
calls:

411--9001--125
l
for the cell from the second frequency band to the main
Name Q3 : hoExecutionOutgoingEbandMbandMsDualb
Object : bts
dualband mobiles for the cell, from the second frequency band to the
main frequency band of the network
Class : handover
Precise
calls:
l
1793 Number of incoming intra BSS handovers on TCH requested by
dualband mobiles
Name Q3 : hoRequestIncomingIntraBssTchMsDualb
Object : bts
Function : number of incoming intra BSS handover requests on TCH in the cell
for dualband mobiles

Event : attempt to select the cell as a serving cell

Class : handover
Precise
calls:
Note : The counter is incremented at the end of the handover.
l
1794 Number of incoming intra BSS handovers on TCH execution
attempts for dualband mobiles
Name Q3 : hoExecutionIncomingIntraBssTchMsDualb
Object : bts
Function : number of attempts to execute incoming intra BSS handovers on TCH
in the cell for dualband mobiles
Event : transmission of HANDOVER COMMAND message to the serving
cell
Class : handover
Precise
calls:

411--9001--125

Note : This counter is incremented at the end of the handover and on TCH
only.
l
1795 Number of successful incoming intra BSS handovers on TCH for
dualband mobiles
Name Q3 : hoSuccessIncomingIntraBssTchMsDualb
Object : bts
Function : number of successful incoming intra BSS handovers on TCH in the
cell for dualband mobiles
Event : receipt of HANDOVER COMPLETE from mobile
Class : handover
Precise
calls:

l
1796 Number of intra-bts handovers on TCH requested by dualband
mobiles
Name Q3 : hoRequestIntraBtsMsDualb
Object : bts
Function : number of intra-bts handovers on TCH requested in the cell by
dualband mobiles
Event : attempt to select a TCH in the cell
Class : handover
Precise
calls:
Note : This counter is incremented at the end of the handover.
l
1797 Number of intra-bts handovers on TCH executed for dualband
mobiles
Name Q3 : hoExecutionIntraBtsMsDualb
Object : bts
Function : number of attempts to execute intra-bts handovers on TCH in the cell
by dualband mobiles
Class : handover
Precise
calls:

411--9001--125
l
1798 Number of successful intra-bts handovers on TCH for dualband
mobiles
Name Q3 : hoSuccessIntraBtsMsDualb
Object : bts
Function : number of successful intra-bts handovers on TCH in the cell for
dualband mobiles
Event : receipt of ASSIGN COMPLETE from the mobile
Class : handover
Precise
calls:
l
1799 Number of direct allocations of TCHs in the second band (or
zone) of a dualband (or concentric or dual--coupling) cell
Name Q3 : assignToOtherBandOrZone
Object : bts
Function : number of direct allocations of TCHs in the second band (or zone) of a
dualband (or concentric or dual--coupling) cell
Event : receipt of an ASSIGN COMPLETE message on TCH or preempted
PDTCH from the mobile
Class : assignment

Precise
calls:
l
1800/0 Number of handovers performed on the talker side of a VBS call
in the cell
Name Q3 : asciTalkerHandoverVbs
Object : bts
Function : number of handovers performed on the talker side of a VBS call in the
cell
Event : receipt of HO_COMPLETE, CLEAR_COMMAND,
ASSIGN_COMPLETE messages
Class : asci
Precise
l
1800/1 Number of handovers performed on the talker side of a VGCS
call in the cell
Name Q3 : asciTalkerHandoverVgcs
Object : bts
Function : number of handovers performed on the talker side of a VGCS call in
the cell

411--9001--125
Event : receipt of HO_COMPLETE, CLEAR_COMMAND,

ASSIGN_COMPLETE messages
Class : asci
Precise
l
1801/0 Number of tiering handover failures due to lack of radio
resources: Handover from large pattern to small pattern
Name Q3 : hoFailureTieringTchNorrLargeToSmallPattern
Object : bts
Function : Number of tiering handover failures due to lack of radio resources
Event : handover from large pattern to small pattern (non--hopping channel to
hopping channel)
Class : equipment
Precise
calls:
Note : V12 counter
l
1801/1 Number of tiering handover failures due to lack of radio
resources: Handover from small pattern to large pattern
Name Q3 : hoFailureTieringTchNorrSmallToLargePattern
Object : bts
Function : Number of tiering handover failures due to lack of radio resources

Event : handover from small pattern to large pattern (hopping channel to

non--hopping channel)
Class : equipment
Precise
calls:
l
1802/0 Number of tiering handover successes: Handover from large
pattern to small pattern
Name Q3 : hoSuccessTieringTchLargeToSmallPattern
Object : bts
Function : Number of tiering handover successes
Event : handover from large pattern to small pattern (non--hopping channel to
hopping channel)
Class : equipment
Precise
calls:
l
1802/1 Number of tiering handover successes: Handover from small
pattern to large pattern
Name Q3 : hoSuccessTieringTchSmallToLargePattern
Object : bts
Function : Number of tiering handover successes

411--9001--125
Event : handover from small pattern to large pattern (hopping channel to

non--hopping channel)
Class : equipment
Precise
calls:
l
1804 Number of delete indication messages received
Name Q3 : deleteIndication
Object : bts
Function : number of delete indication messages received. A delete indication is
sent each time there is too much queued immediate assignment
messages.
Event : receipt of a DELETE INDICATION message from the BTS
Class : asci
l
1805 Number of MS increment power controls ordered by the Layer
One Management
Name Q3 : msPowerIncControl
Object : bts
Function : number of MS increment power controls ordered by the Layer One
Management
Event : receipt of a STOP MEASUREMENT ACK message from the BTS
Class : asci


Precise
(normal completion)
l
1806 Number of MS decrement power controls ordered by the Layer
One Management
Name Q3 : msPowerDecControl
Object : bts
Function : number of MS decrement power controls ordered by the Layer One
Management

411--9001--125

Class : asci
Precise
(normal completion)
l
1807 Number of BS increment power controls ordered by the Layer
One Management
Name Q3 : bsPowerIncControl
Object : bts
Function : number of BS increment power controls ordered by the Layer One
Management


Class : asci
Precise
(normal completion)
l
1808 Number of BS decrement power controls ordered by the Layer
One Management
Name Q3 : bsPowerDecControl
Object : bts
Function : number of BS decrement power controls ordered by the Layer One
Management

411--9001--125

Class : asci
Precise
(normal completion)

l
1809/0 Average timing advance value for the communications in the cell
Name Q3 : timingAdvanceAverage
timingAdvanceAverageTrZone
Function : average timing advance value for the communications in the the cell
(only for communications on TCH channel)
Class : asci
Precise
phase)”
(normal completion)
Note : The value given by the BTS is the average timing advance per
communication (this value is multiplied by the C1600 value:
connectionDurationTch)

411--9001--125
l
1809/1 Maximum timing advance value for the communications in the
cell
Name Q3 : timingAdvanceMaximum
timingAdvanceMaximumTrZone
Function : maximum timing advance value for the communications in the inner
or the outer zone of the cell (only for communications on TCH
channel)
Class : asci
Precise
phase)”


(normal completion)
Note : The value given by the BTS is the maximum timing advance per
communication (the maximum value for all the communications in
the transceiverZone of cell)
l
1810 Average and maximum numbers of configurated TCH full rate
resource
Name Q3 : tchFrAverageConfigurated
tchFrAverageConfiguratedMoy
tchFrAverageConfiguratedMax
tchFrAverageConfiguratedCum
tchFrAverageConfiguratedEch
tchFrAverageConfiguratedTrZoneMoy
tchFrAverageConfiguratedTrZoneMax
tchFrAverageConfiguratedTrZoneCum
tchFrAverageConfiguratedTrZoneEch
Function : average and maximum numbers of configurated TCH full rate
resource (resource configured by the OMC; it can be available or
unavailable). Preemptable PDTCHs are not taken into account.
Event : receipt of a TGE from the OMC modifying the number of TCH
resources in the cell
Class : asci
Precise
1810.
Note : This resource configured by the OMC may be available or not.

411--9001--125
l
1811 Average and maximum numbers of configurated SDCCH
resource
Name Q3 : sdcchAverageConfiguratedMoy
sdcchAverageConfiguratedMax
sdcchAverageConfiguratedCum
sdcchAverageConfiguratedEch
sdcchAverageConfiguratedTrZoneMoy
sdcchAverageConfiguratedTrZoneMax
sdcchAverageConfiguratedTrZoneCum
sdcchAverageConfiguratedTrZoneEch
Function : average and maximum numbers of configurated SDCCH resource
(= resource configured by the OMC; it can be available or
unavailable)
Event : receipt of a TGE from the OMC modifying the number of SDCCH
resources in the inner or the outer zone of the cell
Class : asci
Note : This resource configured by the OMC may be available or not.

l
1812 Number of activated and non activated circuit TS for traffic in
circuit mode in the inner or the outer zone of the cell
Name Q3 : allocatedCircuitTsMoy
allocatedCircuitTsMax
allocatedCircuitTsCum
allocatedCircuitTsEch
allocatedCircuitTsTrZoneCum
allocatedCircuitTsTrZoneMax
allocatedCircuitTsTrZoneMoy
allocatedCircuitTsTrZoneEch
Function : Minimum, maximum, average, and cumulative number of activated
and non activated circuit TS (all TCHs and PDTCHs activated for
traffic in circuit mode) in the inner or outer zone of the cell
Event : allocation of a TCH or a PDTCH for traffic in circuit mode
Class : GPRS
Feature : GPRS (TF1121 and TF1128 - V12)
Precise
calls:
1812.

411--9001--125

phase)”
l
1813/0 Number of TS allocations for packet mode in the cell
Name Q3 : allocatedPacketTsMoy
allocatedPacketTsMax
allocatedPacketTsCum
allocatedPacketTsEch
allocatedPacketTsTrZoneCum
allocatedPacketTsTrZoneEch
allocatedPacketTsTrZoneMax
allocatedPacketTsTrZoneMoy
PDTCH for GPRS (= all configured PDTCHs not preempted for
traffic in circuit mode)
Event : PDTCH configuration or preemption / release of the GPRS channel
by the BSC
Class : GPRS

Feature : GPRS (TF1121 and TF1128 - V12)

Precise
1813.
completion)”
preemption)” which shows that c1813 is decremented when no
resource is available to perform a PDTCH preemption
Counts the preemption on PDTCHs not mapped on AGPRS; as
when available PDTCHs are used for circut calls.
This counter gives the number of PDTCH channels given to the
PCU equipment.
l
1813/1 Number of PDTCH configured on the cell
Name Q3 : totalNumberOfPacketTsMoy
totalNumberOfPacketTsMax
totalNumberOfPacketTsCum
totalNumberOfPacketTsEch
totalNumberOfPacketTsTrZoneMoy
totalNumberOfPacketTsTrZoneMax
totalNumberOfPacketTsTrZoneCum
totalNumberOfPacketTsTrZoneEch
Function : Minimum, maximum, average, and cumulative number of PDTCH
configured on the cell (total number of available PDTCH)
Event : TDMA configuration/deconfiguration
Class : GPRS
Feature : GPRS (PM1367)

411--9001--125

completion)”
resource is available to perform a PDTCH preemption
when available PDTCHs are used for circuit calls.
PCU equipment.
Note : V14 Counter
l
1813/2 Number of PDTCH preempted
Name Q3 : totalNumberOfPacketTsUsedForCircuitMoy
totalNumberOfPacketTsUsedForCircuitMax
totalNumberOfPacketTsUsedForCircuitCum
totalNumberOfPacketTsUsedForCircuitEch
totalNumberOfPacketTsUsedForCircuitTrZoneMoy
totalNumberOfPacketTsUsedForCircuitTrZoneMax
totalNumberOfPacketTsUsedForCircuitTrZoneCum
totalNumberOfPacketTsUsedForCircuitTrZoneEch
preempted (number of available PDTCH used for circuit PDTCH)
Event : Channel activation and RF channel release of a PDTCH
Class : GPRS
Feature : GPRS (PM136F)
completion)”
resource is available to perform a PDTCH preemption.FDF
when available PDTCHs are used for circuit calls.
PCU equipment.
Note : V14 Counter

l
1814 Number of GPRS preemption successes
Name Q3 : gprsPreemption
Object : bts
Function : number of PDTCH preemption successes
Event : successful preemption of a PDTCH in circuit mode
Class : GPRS
Feature : GPRS (TF1121 - V12)
Precise
When GPRS is activated, this counter is concerned by CCP only
preemption)”
l
1815 Number of GPRS preemption failures (requests nacked by the
PCU)
Name Q3 : gprsPreemptionNack
Object : bts
Function : number of PDTCH preemption failures (requests nacked by the PCU)
Event : receipt of a refusal message from the PCU to release its PDTCH
channel
Class : GPRS
Feature : GPRS (TF1121 - V12)
Precise
When GPRS is activated, this counter is concerned by CCP only

411--9001--125

1821 Number of activated and non activated circuit TS for traffic in

circuit mode in the inner or the outer zone of the cell
Name Q3 : allocatedCircuitTsCellMoy,
allocatedCircuitTsCellMax,
allocatedCircuitTsCellCum,
allocatedCircuitTsCellEch.
Object : bts
Function : Minimum, maximum, average, and cumulative number of activated
and non activated circuit TS (all TCHs and PDTCHs activated for
traffic in circuit mode) in the inner or outer zone of the cell
Event : allocation of a TCH or a PDTCH for traffic in circuit mode
Class : GPRS
Precise
calls:
1822/0 Number of TS allocations for packet mode in the cell

Name Q3 : allocatedPacketTsCellMoy,
allocatedPacketTsCellMax,
allocatedPacketTsCellCum,
allocatedPacketTsCellEch,
Object : bts
PDTCH for GPRS (= all configured PDTCHs not preempted for
traffic in circuit mode)

Event : PDTCH configuration or preemption / release of the GPRS channel

by the BSC
Class : GPRS
1822/1 Number of PDTCH configured on the cell

Name Q3 : totalNumberOfPacketTsCellMoy,
totalNumberOfPacketTsCellMax,
totalNumberOfPacketTsCellCum,
totalNumberOfPacketTsCellEch
Object : bts
configured on the cell (total number of available PDTCH)
Event : TDMA configuration/deconfiguration
Class : GPRS
1822/2 Number of PDTCH preempted

Name Q3 : totalNumberOfPacketTsUsedForCircuitCellMoy,
totalNumberOfPacketTsUsedForCircuitCellMax,
totalNumberOfPacketTsUsedForCircuitCellCum,
totalNumberOfPacketTsUsedForCircuitCellEch
Object : bts
preempted (number of available PDTCH used for circuit PDTCH)
Event : Channel activation and RF channel release of a PDTCH
Class : GPRS

411--9001--125
1823 Average duration to allocate all TCH/FR and preempted PDTCH

resources
Name Q3 : allTchFrAllocatedTimeCellMoy,
allTchFrAllocatedTimeCellMax,
allTchFrAllocatedTimeCellCum,
allTchFrAllocatedTimeCellEch,
Object : bts
Function : Number of milliseconds during which all the available TCH_FR
resources and pre--emptable PDTCH resources are used. A blocked
resource is neither considered as used nor available. This counter has
the same definition as the counter 1057, only the location is different.
Event : starts measurement on allocation of all the available TCH full rate and
pre--emptable PDTCH resources of the CELL and stops as soon as a
resource is free. In case we got a pre--emption nack, the counter starts
immediately and stops as soon a resource is released or as soon as the
timer GprsPreemptionProtection elapses.
Class : GPRS
Precise
calls:
1824/0 Average number of TCH/FR or preempted PDTCH used for

traffic in the zone (concentric cell)
Name Q3 : tchFrAveragedUsedTchAllocationCellMoy,
tchFrAveragedUsedTchAllocationCellMax
tchFrAveragedUsedTchAllocationCellCum
tchFrAveragedUsedTchAllocationCellEch
Object : bts
Function : average and maximum number of full rate TCH allocations or
preempted PDTCH (for screening 0 and 3). This counter has the same
definition as the counter 1611, only the location is different.

Event : allocation/de--allocation of a full rate TCH or preempted PDTCH.

Class : GPRS
Precise
calls:
1824/1 Average number of TCH/FR used for call reestablishments in the

Name Q3 : tchFrAveragedUsedPrimoAllocationCellMoy,
tchFrAveragedUsedPrimoAllocationCellMax,
tchFrAveragedUsedPrimoAllocationCellCum,
tchFrAveragedUsedPrimoAllocationCellEch.
Object : bts
Event : allocation in primo--allocation (call re--establishment). Only for a
TCH full rate channel.
Class : GPRS
Precise
channel).

411--9001--125
1824/2 Average number of TCH/FR used because of SDCCH

unavailability in the zone (concentric cell)
Name Q3 : tchFrAveragedUsedOverflowAllocationCellMoy,
tchFrAveragedUsedOverflowAllocationCellMax,
tchFrAveragedUsedOverflowAllocationCellCum,
tchFrAveragedUsedOverflowAllocationCellEch.
Object : bts
Event : allocation for a SDCCH on overflowing (lack of SDCCH resources).
For a TCH full rate channel
Class : GPRS
1824/3 Average and maximum number of WPS full rate TCH allocations
Name Q3 : tchFrAveragedUsedWpsCellMoy,
tchFrAveragedUsedWpsCellMax,
tchFrAveragedUsedWpsCellCum,
tchFrAveragedUsedWpsCellEch.
Object : bts
Event : allocation of a TCH channel or a preempted PDTCH for a WPS call.
Class : GPRS
Precise
incrementation conditions : When GPRS is activated, this counter is
concerned by CCT (Circuit calls on TCH channel), but not by CCP (Circuit Calls on
PDTCH preempted to make a TCH channel). This is because this counter is related
to configured (static) TCH/FR channel. This counter is pegged on the traffic channel
allocation for a WPS call if the WPS Management flag is enabled. This counter is
pegged on the traffic channel de--allocation for a call inititiated as a WPS call.


1825 Average number of TCH/FR and preemptable PDTCH available

in multizone cell
radio TS used for circuit call only
radio TS shared between circuit services and packet data services
if the number of PDTCH in the cell is less than minNbrGprsTS, then
Number_of_PDTCH_cell
else
minNbrGprsTS
C1700_iz = Number_of_TCH_iz + Number_of_PDTCH_iz
Where oz = outer zone and iz = inner zone
Name Q3 : tchFrAveragedAvailableCellMoy,
tchFrAveragedAvailableCellMax,
tchFrAveragedAvailableCellCum,
tchFrAveragedAvailableCellEch.
Object : bts
Function : Number of available TS for circuit calls. Used resources are counted
as available. This counter is related to TCH_FR channel,
pre--emptable PDTCH and PDTCH not allocated to PCUSN. This
counter has the same definition as the counter 1700, only the location
is different.
Event : attribution/removal of TDMA (faults and O&M interventions), no
reception of SYS INFO 5 and 6 acknowledgment, or lack of radio
channels.
Class : GPRS

411--9001--125
Precise
calls:
To sum it up, this counter is related to TCH/FR channel, preemptable
PDTCH and PDTCH not allocated to PCUSN.
1826 Average number of TCH/FR or preempted PDTCH used in the

concentric cell and zone
Name Q3 : tchFrAveragedUsedCellMoy,
tchFrAveragedUsedCellMax,
tchFrAveragedUsedCellCum,
tchFrAveragedUsedCellEch.
Object : bts
Function : average and maximum number of full rate TCH allocations and
preempted PDTCH. This counter has the same definition as the
counter 1746, only the location is different.
Event : allocation/de--allocation of a full rate TCH or a preempted PDTCH.
Class : GPRS
1827 Average and maximum numbers of configurated TCH full rate

resource
Name Q3 : tchFrAverageConfiguratedCellMoy,
tchFrAverageConfiguratedCellMax,
tchFrAverageConfiguratedCellCum,
tchFrAverageConfiguratedCellEch
Object : bts
Function : average and maximum number of configurated TCH full rate resource
(= resource configured by the OMC. It can be available or
unavailable). This counter has the same definition as the counter
1810, only the location is different. Preemptable PDTCH are not
taken into account.

Event : Reception of a TGE from the OMC modifying the number of TCH
resources in the cell.
Class : GPRS
Precise
l
1828/0 Allocation of a half rate TCH or a preempted PDTCH
Name Q3 : tchHrAveragedUsedCellMoy
tchHrAveragedUsedCellMax
tchHrAveragedUsedCellCum
tchHrAveragedUsedCellEch
Object : bts
allocations
Class : allocation
l
1828/1 Allocation of a half rate TCH or a preempted PDTCH for a WPS
call
Name Q3 : tchHrAveragedUsedWpsCellMoy
tchHrAveragedUsedWpsCellMax
tchHrAveragedUsedWpsCellCum
tchHrAveragedUsedWpsCellEch
Object : bts
allocations
Class : allocation

411--9001--125

Precise
the WPS property of a call is lost after an handover. Consequently, for
a WPS call, after an handover, the screening 1828/0 is updated
instead of the screening 1828/1
l
1829 Average, maximum, mimium, and total number of half rate TCH
allocations
Name Q3 : tchHrAveragedUsedNscCellCum
tchHrAveragedUsedNscCellEch
tchHrAveragedUsedNscCellMax
tchHrAveragedUsedNscCellMoy
Object : bts
Function : average and maximum number of half rate TCH allocations.
Event : allocation/de--allocation of a half rate TCH
Class : setup
l
1839/0 Number of outgoing intra--bss or inter--bss handover attempts
from a central cell to a neighboring one: Loss of Uplink power
Name Q3 : hoNcellsRequestOutgoingUplinkStrength
Function : number of outgoing intra--bss or inter--bss handover attempts from a
central cell to a neighboring one because of Loss of Uplink power
Event : attempt of selection of an eligible cell resource
Class : asci


Object : This counter only applies on TCH channel.
l
from a central cell to a neighboring one: Loss of Downlink power
Name Q3 : hoNcellsRequestOutgoingDownlinkStrength
central cell to a neighboring one because of Loss of Downlink power
Class : asci
l
from a central cell to a neighboring one: Loss of Uplink quality
Name Q3 : hoNcellsRequestOutgoingUplinkQuality
central cell to a neighboring one because of Loss of Uplink quality
Class : asci

411--9001--125

l
from a central cell to a neighboring one: Loss of Downlink
quality
Name Q3 : hoNcellsRequestOutgoingDownlinkQuality
central cell to a neighboring one because of Loss of Downlink quality
Class : asci
l
from a central cell to a neighboring one: Distance
Name Q3 : hoNcellsRequestOutgoingDistance
central cell to a neighboring one because of distance
Class : asci


l
from a central cell to a neighboring one: Power Budget
Name Q3 : hoNcellsRequestOutgoingPowerBudget
central cell to a neighboring one because of power budget
Class : asci
l
from a central cell to a neighboring one: Directed retry
Name Q3 : hoNcellsRequestOutgoingDirectedRetry
central cell to a neighboring one because of directed retry
Class : asci

411--9001--125

l
from a central cell to a neighboring one: Forced handover O&M
Name Q3 : hoNcellsRequestOutgoingInterCellOM
central cell to a neighboring one with cause “forced handover” from
the L1M
Class : asci
l
from a central cell to a neighboring one: Traffic
Name Q3 : hoNcellsRequestOutgoingTraffic
central cell to a neighboring one with cause “traffic” from the L1M
Class : asci


l
from a central cell to a neighboring one: Other causes
Name Q3 : hoNcellsRequestOutgoingOther
central cell to a neighboring one for other causes
Class : asci
l
1840/0 Number of outgoing intra--bss or inter--bss handover successes
from a central cell to a neighboring one: Loss of Uplink power
Name Q3 : hoNcellsSuccessOutgoingUplinkStrength
Function : number of outgoing intra--bss or inter--bss handover successes from a
central cell to a neighboring one because of Loss of Uplink power
Event : receipt of a CLEAR COMMAND message from the MSC with a
cause set to “handover successful” (inter--bss handovers) or receipt of
a HANDOVER COMPLETE message (intra--bss handovers)
Class : asci

411--9001--125

l
from a central cell to a neighboring one: Loss of Downlink power
Name Q3 : hoNcellsSuccessOutgoingDownlinkStrength
central cell to a neighboring one because of Loss of Downlink power
Class : asci
l
from a central cell to a neighboring one: Loss of Uplink quality
Name Q3 : hoNcellsSuccessOutgoingUplinkQuality
central cell to a neighboring one because of Loss of Uplink quality
Class : asci


l
from a central cell to a neighboring one: Loss of Downlink
quality
Name Q3 : hoNcellsSuccessOutgoingDownlinkQuality
central cell to a neighboring one because of Loss of Downlink quality
Class : asci
l
Name Q3 : hoNcellsSuccessOutgoingDistance
central cell to a neighboring one because of distance

411--9001--125

Class : asci
l
Name Q3 : hoNcellsSuccessOutgoingPowerBudget
central cell to a neighboring one because of power budget
Class : asci

l
from a central cell to a neighboring one: Directed retry
Name Q3 : hoNcellsSuccessOutgoingDirectedRetry
central cell to a neighboring one because of directed retry
Class : asci
l
from a central cell to a neighboring one: Forced handover O&M
Name Q3 : hoNcellsSuccessOutgoingInterCellOM
central cell to a neighboring one with cause “forced handover” from
the L1M
Class : asci

411--9001--125

l
from a central cell to a neighboring one: Traffic
Name Q3 : hoNcellsSuccessOutgoingTraffic
central cell to a neighboring one with cause “traffic” from the L1M
Class : asci
l
from a central cell to a neighboring one: Other causes
Name Q3 : hoNcellsSuccessOutgoingOther
central cell to a neighboring one for other causes
Class : asci


l
1841/0 Number of assignment request messages received: modification
from a SDCCH channel to a TCH or a preempted PDTCH
channel
Name Q3 : assignRequestSdcchToTchChannel
Object : bts
Function : number of assignment request messages received because of a
modification from a SDCCH channel to a TCH or a preempted
PDTCH channel
Event : receipt of a ASSIGNMENT REQUEST message from the MSC
because of a modification from a SDCCH channel to a TCH or a
preempted PDTCH channel
Class : assignment
Precise
calls:
preemption)”

411--9001--125

completion)”
completion)”
l
1841/1 Number of assignment request messages received: Cause other
than modification from a SDCCH channel to a TCH or a
Name Q3 : assignRequestOthers
Object : bts
Function : number of assignment request messages received because of a cause
other than a modification from a SDCCH channel to a TCH or a
Event : receipt of a ASSIGNMENT REQUEST message from the MSC
because of a cause other a modification from a SDCCH channel to a
TCH or a preempted PDTCH channel
Class : assignment
Precise
calls:
completion)”

l
1842/0 Number of emission of ASSIGNMENT FAILURE messages on
the A interface: Modification from an SDCCH channel to a TCH
or a preempted PDTCH channel
Name Q3 : assignRequestAintSdcchToTchChannel
Object : bts
Function : number of ASSIGNMENT FAILURE messages sent on the
A interface because of a modification from a SDCCH channel to a
Event : sending of an ASSIGNMENT FAILURE message to the MSC
because of a modification from a SDCCH channel to a TCH or a
Class : assignment
Precise
calls:
preemption)”
l
1842/1 Number of emission of ASSIGNMENT FAILURE messages on
the A interface: Cause other than modification from a SDCCH
channel to a TCH or a preempted PDTCH channel
Name Q3 : assignRequestAintOthers
Object : bts
Function : number of ASSIGNMENT FAILURE messages sent on the
A interface because of a cause other than a modification from a
SDCCH channel to a TCH or a preempted PDTCH channel

411--9001--125
Event : sending of an ASSIGNMENT FAILURE message to the MSC

because of a cause other a modification from a SDCCH channel to a
Class : assignment
Precise
calls:
l
2010/0 Total number of priority 1 queued WPS requests on a priority
level basis
Name Q3 : WQUEUED1
Object : bts
Function : Total number of priority 1 queued WPS requests on a priority level
basis.
Event : WPS global flag is activated
Feature : WPS BSS2G and 3000 queuing mechanism enhancement (22463)
Note : V15 counter
l
level basis
Name Q3 : WQUEUED2
Object : bts
basis.


Note : V15 counter
l
level basis
Name Q3 : WQUEUED3
Object : bts
basis.
Note : V15 counter
l
level basis
Name Q3 : WQUEUED4
Object : bts
basis.
Note : V15 counter
l
level basis
Name Q3 : WQUEUED5
Object : bts
basis.

411--9001--125

Note : V15 counter
l
2011/0 Total number of priority 1 WPS requests dropped or not allowed
Name Q3 : WQOVFL1
Object : bts
Function : Total number of priority 1 WPS requests dropped or not allowed.
Note : V15 counter
l
Name Q3 : WQOVFL2
Object : bts
Note : V15 counter
l
Name Q3 : WQOVFL3
Object : bts


Note : V15 counter
l
Name Q3 : WQOVFL4
Object : bts
Note : V15 counter
l
Name Q3 : WQOVFL5
Object : bts
Note : V15 counter
l
2012/0 Total number of priority 1 WPS requests dropped when the time
spent by WPS request exceeds the maximum queue timer.
Name Q3 : WQTOUT1
Object : bts
Function : Total number of priority 1 WPS requests dropped when the time spent
by WPS request exceeds the maximum queue timer.

411--9001--125

Note : V15 counter
Name Q3 : WQTOUT2
Object : bts
Note : V15 counter
l
Name Q3 : WQTOUT3
Object : bts
Note : V15 counter
l
Name Q3 : WQTOUT4
Object : bts


Note : V15 counter
l
Name Q3 : WQTOUT5
Object : bts
Note : V15 counter
l
2013/0 Duration that access class 0 to 9 has been barred during cell
congestion.
Name Q3 : wpsAccessBarringDurationClass0to9
Object : bts
Function : An access class is barred during cell congestion. Barred access classes
in the notAllowedAccessClasses parameter exclude the counter
triggering. Number of times access classes number 0 to 9 are barred.
Correlation with accessClassCongestion parameter (removing
classes 11 to 15) gives the number of minutes a given access class
between 0 to 9 barred
Event : At each rotation of access classes (every 1 minute).
Feature : WPS BSS2G and 3000 access class barring with class periodic
rotation. (22464)
Note : V15 counter

411--9001--125
l
2013/1 Duration that access class 11 has been barred during cell
congestion.
Name Q3 : wpsAccessBarringDurationClass11
Object : bts
triggering. Number of minutes the access class number 11 has been
barred.
rotation. (22464)
Note : V15 counter
l
congestion.
Object : bts
barred.
rotation. (22464)
Note : V15 counter

l
congestion.
Object : bts
barred.
rotation. (22464)
Note : V15 counter
l
congestion.
Object : bts
barred.
rotation. (22464)
Note : V15 counter

411--9001--125
l
congestion.
Object : bts
barred.
rotation. (22464)
Note : V15 counter
l
2014 Average and maximum number of WPS half rate TCH
allocations
Name Q3 : WPUBWPSQ
Object : bts
Function : Average and maximum number of WPS half rate TCH (including
PDTCH) allocations
Event : TCHA traffic channel becomes free and is allocated to a public call
while a WPS request is queued.
Note : V15 counter
l
2015 Total number of WPS requests removed from the queue
Name Q3 : WQABAND
Object : bts
Function : total number of WPS requests removed from the queue because of:
-- loss of radio contact with the MS Object Instance cell|
-- Clear command cause “call control” received from the MSC while
the WPS request is queued and no clear request previously sent

Event : WPS call is released while in queuing phase

Note : V15 counter
l
2016 Total number of WPS request removed from the queue
Name Q3 : WQUEDHO
Object : bts
Function : total number of WPS requests removed from the queue because of :
- successful intercell handover (SDCCH to TCH)
-- successful directed retry
Event : Successful handover in the target cell leads to release the resources in
the serving cell.
Note : V15 counter
l
2025/0 Number of times the BTS detects a bad content in the start
measurement or in the classmark change request messages
Name Q3 : downgradedL1mModeOnClassmark
Object : bts
Function : Number of times the BTS detects a bad content in the start
measurement or in the classmark change request messages
Event : Receipt of a STOP MEASUREMENT ACK message from the BTS.
Note : V15 counter

411--9001--125
l
2035/0 Value of the msPowerClassToggle parameter
Name Q3 : msClassSensitivityToggle
Object : bts
Function : A msPowerClassToggle parameter is defined at the OMC--R level in
order to report MS 2W, MS 8W or MS 2W + 8W (no check on the
power class).
A list of ”toggling counters” is defined for which the BSC must take
into account the msPowerClassToggle.
Value of the msPowerClassToggle parameter :
0 : MS 2W
1 : MS 8W
2 : MS 2+8W
Event : At T2 expiration
Note : V15 counter
l
2036/0 Number of attempts of assignation of a TCH full rate or a
preempted PDTCH for MS 8W.
Name Q3 : attemptedTchFrSeizures8W
Object : bts
Function : number of attempts of assignation of a TCH full rate or a preempted
PDTCH for MS 8W
Event : transmission of an ASSIGN_COMMAND message to a MS 8W.
Note : V15 counter
l
2037/0 Number of successful TCH full rate or preempted PDTCH
assignations for MS 8W.
Name Q3 : successfulTchFrSeizures8W
Object : bts
Function : number of successful TCH full rate or preempted PDTCH
assignations for MS 8W

Event : receipt from a MS 8W of an ASSIGN_COMPLETE message

Note : V15 counter
l
2038/0 Number of successful outgoing intra_bss handovers from the cell
for MS 8W
Name Q3 : hoSuccessOutgoingIntraBss8W
Object : bts
Function : number of successful outgoing intra_bss handovers from the cell for
MS 8W
Event : receipt of a HANDOVER_COMPLETE message from a MS 8W
Note : V15 counter
l
2039/0 Number of successful outgoing inter_bss handovers from the cell
for MS 8W
Name Q3 : hoSuccessOutgoingInterBss8W
Object : bts
Function : Number of successful outgoing inter_bss handovers from the cell for
MS 8W
Event : receipt of a CLEAR COMMAND message from the MSC with
handover cause set to hand_over successful
Note : V15 counter
l
2040 Number of incoming intra_bss handover requests received by the
cell, for MS 8W
Name Q3 : hoRequestIncomingIntraBss8W
Object : bts
Function : Number of incoming intra_bss handover requests received by the cell,
for MS 8W. The counter is incremented at the end of the handover
(success, selection failure, execution failure or end of call).

411--9001--125
Event : attempt to select a cell as an host cell

Note : V15 counter
l
2041 Number of incoming inter_bss handover requests received by the
cell, for MS 8W
Name Q3 : hoRequestIncomingInterBss8W
Object : bts
Function : Number of incoming inter_bss handover requests received by the cell,
for MS 8W. The counter is incremented at the end of the handover
(success, selection failure, execution failure or end of call).
Event : receipt of an HANDOVER REQUEST message from the MSC
Note : V15 counter
l
2042 Number of successful incoming intra_bss handovers received by
the cell, for MS 8W only
Name Q3 : hoSuccessIncomingIntraBss8W
Object : bts
Function : Number of successful incoming intra_bss handovers received by the
cell, for MS 8W only
Note : V15 counter
l
2043 Number of successful incoming inter_bss handovers received by
the cell, for MS 8W only
Name Q3 : hoSuccessIncomingInterBss8W
Object : bts
Function : Number of successful incoming inter_bss handovers received by the
cell, for MS 8W only


Note : V15 counter
l
2044 Number of outgoing intra_bss handover requests from the cell
Name Q3 : hoRequestOutgoingIntraBss8W
Object : bts
Function : Number of outgoing intra_bss handover requests from the cell. The
counter is incremented at the end of the handover (success, selection
failure, execution failure or end of call) for MS 8W only.
Event : attempt of selection of one of the cells of the list of the eligible cells
Note : V15 counter
l
2045 Number of outgoing inter_bss handover requests from the cell
Name Q3 : hoRequestOutgoingInterBss8W
Object : bts
Function : Number of outgoing inter_bss handover requests from the cell. The
Note : V15 counter
2046 Number of intra_cell handover requests for the cell, by MS 8W

only
Name Q3 : hoRequestIntraBts8W
Object : bts
Function : Number of intra_cell handover requests for the cell, by MS 8W only.
The counter is incremented at the end of the handover (success,
selection failure, execution failure or end of call).

411--9001--125
Event : attempt of selection in the cell

Note : V15 counter
2047 Number of successful intra_cell handovers for the cell, for MS 8W

Name Q3 : hoSuccessIntraBts8W
Object : bts
Function : Number of successful intra_cell handovers for the cell, for MS 8W
Event : receipt of ASSIGN_COMPLETE message from a MS 8W
Note : V15 counter
l
2048 Number of successful outgoing intra_bss handovers from the cell
for MS 8W
Name Q3 : hoSuccessOutgoingIntraBssSdcch8W
Object : bts
Function : Number of successful outgoing intra_bss handovers from the cell for
MS 8W
Note : V15 counter
l
2049 Number of successful outgoing inter_bss handovers from the cell
for MS 8W
Name Q3 : hoSuccessOutgoingInterBssSdcch8W
Object : bts
Function : Number of successful outgoing inter_bss handovers from the cell for
MS 8W
Note : V15 counter

l
2050 Number of successful outgoing inter_bss handovers from the cell
for MS 8W only
Name Q3 : hoRequestOutgoingIntraBssSdcch8W
Object : bts
Function : number of outgoing intra_bss handover requests from the cell. The
Note : V15 counter
l
2051 Number of outgoing inter_bss handover requests from the cell
Name Q3 : hoRequestOutgoingInterBssSdcch8W
Object : bts
Function : Number of outgoing inter_bss handover requests from the cell. The
Note : V15 counter
l
2052/0 Number of releases while the communication is in signalling
phase and cell associated to the communication, for MS 8W only
Name Q3 : signallingReleaseBts8w
Object : bts
Function : Number of releases while the communication is in signalling phase
and cell associated to the communication, for MS 8W only

411--9001--125
Event : receipt of a SCCP DISCONNECTION INDICATION message from

the MSC
Note : V15 counter
Note : Counter 2052/0 is the sum of the following counters for MS 8W only:
1163/13, 1163/14, 1163/16, 1163/17, 1163/18, 1163/19
l
2052/1 Number of releases while the communication is in “signalling”
phase and cell associated to the communication, for MS 8W only
Name Q3 : signallingReleaseBtsT3107CircDown8W
Object : bts
Function : Number of releases while the communication is in “signalling” phase
and cell associated to the communication, for MS 8W only
Event : Expiration of T3107 timer before receipt of ESTABLISHMENT
INDICATION message, during a Dedicated Channel Assignment
procedure or a handover Intracell on SDCCH procedure. (a CLEAR
REQUEST message is sent)
Note : V15 counter
2053 Number of releases while the communication is in traffic phase,

for MS 8W only
Name Q3 : trafficRelease8W
Object : bts
Function : Number of releases while the communication is in traffic phase,
for MS 8W only
Event : receipt of a SCCP DISCONNECTION INDICATION message from
the MSC.
Note : V15 counter
Note : Counter 2053 is the sum of the following counters for MS 8W only:
1164/13, 1164/14, 1164/16, 1164/17, 1164/18, 1164/18

l
2054 Number of receipts of an ESTABLISHMENT_INDICATION
message in call establishment phase (on SDCCH, or on TCH in
primo allocation (call re--establishment) or on overflowing), for
MS 8W only
Name Q3 : estabIndicSignallingEmergency8W
Object : bts
Function : Number of receipts of an ESTABLISHMENT_INDICATION
message in call establishment phase (on SDCCH, or on TCH in primo
allocation (call re--establishment) or on overflowing), for MS 8W
only
Event : receipt of a CM SERVICE REQUEST first L3 information message,
with a service type set to emergency call establishment
Note : V15 counter
2055 Number of receipt of an ESTABLISHMENT_INDICATION

message in call establishment phase (on SDCCH, or on TCH in
primo allocation (call re--establishment) or on overflowing) for a
phase II MS 8W
Name Q3 : estabIndicSigPhase28W
Object : bts
Function : Number of receipt of an ESTABLISHMENT_INDICATION
message in call establishment phase (on SDCCH, or on TCH in primo
allocation (call re--establishment) or on overflowing) for a phase II
MS 8W
Event : receipt of an ESTABLISHMENT_INDICATION message in call
establishment phase (on SDCCH, or on TCH in primo allocation (call
re--establishment) or on overflowing) for a phase II MS 8W
Note : V15 counter

411--9001--125
l
2056/0 Number of failures to execute intra--bss handover from the cell
for MS 8W only
Name Q3 : hoUnsuccessOutgoingIntraCellTchReturnOldChannel8W
Object : bts
Function : number of failures to execute intra--bss handover from the cell for
MS 8W only
Event : a MS 8W returns to the old channel (HANDOVER FAILURE) before
Class : handover
l
2056/1 Number of failures to execute intra--bss handover from the cell
for MS 8W only
Name Q3 : hoUnsuccessOutgoingIntraCellTchT3103TimerExp8W
Object : bts
Function : number of failures to execute intra--bss handover from the cell for
MS 8W only.
Event : expiration of T3103 timer
Class : handover
l
TCH in the cell with cause mobile returns to the old channel
Name Q3 : hoUnsuccessOutgoingInterCellTchReturnOldChannel8W
Object : bts
in the cell with cause mobile returns to the old channel
Class : handover

l
TCH in the cell with cause T3103 (respectively T3107) timer
expiration for V12 (respectively V11)
Name Q3 : hoUnsuccessOutgoingInterCellTchT3103TimerExp8W
Object : bts
in the cell with cause T3103 (respectively T3107) timer expiration for
V12 (respectively V11)
Event : expiration of the T3103 timer
Class : handover
l
2058/0 Number of abnormal releases while the communication is in
“signalling” phase and cell associated to the communication, for
MS 8W only.
Name Q3 : signallingAbnormalReleaseCell8W
Object : bts
Function : number of abnormal releases while the communication is in
“signalling” phase and cell associated to the communication, for MS
8W only.
Event : All the previous screening except Expiration of T3101 timer before
receipt of ESTABLISHMENT INDICATION message, during an
Immediate Assignment procedure and “Receipt of a
CLEAR_COMMAND message from the MSC” (considered as
normal release).
Class : handover
l
2059 Number of abnormal releases while the communication is in
“traffic” phase, for MS 8W only.
Name Q3 : trafficAbnormalRelease8W
Object : bts
Function : number of abnormal releases while the communication is in “traffic”
phase, for MS 8W only.

411--9001--125
Event : All the previous screening except “Receipt of a

CLEAR_COMMAND message from the MSC” (considered as
normal release).
Class : handover
l
2060 Number of uplink free messages sent by the BSC indicating in the
uplink request access that the MS shall perform the uplink reply
procedure.
Name Q3 : uplinkFreeUplinkReply
Object : bts
Function : Cumulative number of uplink free messages sent by the BSC
indicating in the uplink request access that the MS shall perform the
uplink reply procedure.
Event : Whenever the BSC sends an uplink free message indicating in the
uplink request access that the MS shall perform the uplink reply
procedure.
Note : V15 counter

l
2061 At expiration of the listener detection timer, the group call
channel is released in the cell
Name Q3 : listenerDetectionExpiry
Object : bts
Function : At expiration of the listener detection timer, the group call channel is
released in the cell.
Event : at expiration of the listener detection timer
Note : V15 counter

411--9001--125
2066 Number of GPRS suspension request messages received by the BSC

Name Q3 : suspendRequest
Object : bts
Function : Number of GPRS suspension request messages received by the BSC
Event : The counter is incremented when the BSC releases the
communication.
Class : GPRS/EDGE
Precise
The counter is increased in the cell where the communication is
released.
In case of inter--BSC Handover (resp. inter--RA Handover), this
counter is incremented only on the initial BSC (resp. initial RA), in
the last cell of the initial BSC (resp. initial RA).
This counter is incremented even if the GPRSResumption field is
not present.
This counter is incremented even if the Suspend/Resume feature is
NOT activated.
In case of successive inter--BSC or inter--RA HO, the counter is
increased only once, in the last cell of the initial BSC or RA.
procedure)
case)
procedure)
case)
Note : V15 counter

2067 Number of successful resume procedures

Name Q3 : resumeSuccess
Object : bts
Function : Number of successful resume procedures.
Event : The counter is increased when the BSC releases the communication
AND if the Channel Release has the “GPRS Resumption” bit set to
“1” (resumption of GPRS services successfully acknowledged).
Class : GPRS/EDGE
Precise
The counter is incremented in the cell where the communication is
released.
procedure)
Note : V15 counter

411--9001--125
2068/0 Number of times the BSC does not perform a GPRS Resume proc.
Name Q3 : resumeFailureAfterHOInterRA
Object : bts
Function : Number of times the BSC does not perform a GPRS resume procedure
after a successful GPRS suspension. The GPRS attached MS has
performed an inter--RA handover (intra--BSC).
Event : The counter is increased when the BSC sends the RF Channel Release
on the initial RA after the HO Complete.
Class : GPRS/EDGE
Precise
The counter is increased in the cell of the initial RA where the RF
Channel Release is sent.
The counter is not incremented when the communication was not
successfully suspended.
In case of successive inter--RA HO, the counter is increased only
once, in the last cell of the initial RA.
case)
Note : V15 counter

2068/1 Number of times the BSC does not perform a GPRS Resume proc.
Name Q3 : resumeFailureAfterHOInterBSC
Object : bts
Function : Number of times the BSC does not perform a GPRS resume procedure
after a successful GPRS suspension. The GPRS attached MS has
performed an inter--BSC handover.
Event : The BSC sends the RF Channel Release on the initial BSC after the
HO complete.
Class : GPRS/EDGE
Precise
The counter is increased in the cell of the initial BSC where the RF
Channel Release is sent.
The counter is not incremented when the communication was not
successfully suspended.
In case of successive inter--BSC HO, the counter is increased only
once, in the last cell of the initial BSC.
case)
Note : V15 counter

411--9001--125
5.5 Raw temporary counters (ODIAG excluded) (from 5000 to

5610)
5.5.1 Temporary Interference observation
ll
5000 Average interference level on idle channels
Name Q3 : channelIdleLevelMoy
channelIdleLevelMax
channelIdleLevelCum
channelIdleLevelEch = Number of samples
Object : channel (dedicated radio channel)
Function : interference class [0 to 4] on a radio channel (= average level of
measured values on SDCCH or TCH) when it is free and number of
free logical channels carried by the radio channel during the
observation period
Event : receipt of RF RESOURCE INDICATION message
Type : raw temporary
Note : A PDTCH channel is not taken into account
5.5.2 Temporary SS7 link observation

l
5100/0 Number of MSU frames received on Level 2
Name Q3 : ss7InputMsu
Object : signallingLink
Function : number of MSU (Message Signal Unit) frames received by the BSC
Event : transmission by MTP2 to MTP3 of an MSU frame received from the
remote MTP2
ll
5101/0 Number of MSU frames sent on Level 2
Name Q3 : ss7OutputMsu
Function : number of MSU (Message Signal Unit) frames sent by the BSC
Event : receipt by MTP2 from MTP3 of an MSU frame for transmission

ll
5102/0 Number of SS7 Level 2 errors: Negative ACK received
Name Q3 : ss7Level2ErrorNegAckRec
Function : number of errors detected by Level 2 due to receipt of negative
acknowledgement of frames
Event : receipt by the BSC link of a request for retransmission on the SS7 link
from the remote MTP2
l
5102/1 Number of SS7 Level 2 errors: Negative ACK sent
Name Q3 : ss7Level2ErrorNegAckTrans
Function : number of errors detected by Level 2 due to transmission of negative
acknowledgement of frames
Event : transmission by the BSC of a request for retransmission on the SS7
link to the remote MTP2
ll
5102/2 Number of SS7 Level 2 errors: MSU rejected for congestion
Name Q3 : ss7Level2ErrorMsuCongest
Function : number of MSU frames rejected by MTP2 because of lack of internal
memory
Event : rejection of an MSU frame by MTP2 because of lack of internal
memory

411--9001--125
ll
5102/3 Number of SS7 Level 2 errors: SU error
Name Q3 : ss7Level2ErrorSuErr
Function : number of errors detected by Level 2 because of errored SU
Event : receipt by the MTP2 of one of the following:
a frame with a false CRC
a frame too short (length equal or inferior to 2 bytes)
16 bytes in “OCM” byte counting mode
ll
5103/0 Number of SS7 Level 3 errors: ACK delay exceeded
Name Q3 : ss7Level3ErrorDelay
Function : number of errors detected by Level 3 because of lengthy delay in
acknowledgement messages
Event : Level 3 bssMapT7 time-out elapse
ll
5103/1 Number of SS7 Level 3 errors: High error rate
Name Q3 : ss7Level3ErrorHighErrRate
Function : number of errors detected by monitoring the error rate of SS7 frames
Event : detection by MTP2 of an excessive error rate, according to the
definition of the CCITT Q703 recommendation (Paragraph 10,
page 67)

5.5.3 Temporary Abis interface observation

l
5600/0 Number of IU frames sent on sapi RSL
Name Q3 : abisOutputUiFrame
Object : bts
Function : number of UI (Unnumbered Information) frames sent to the cell
TDMA frames on RSL SAPI
Event : transmission of a UI frame on a RSL by the BSC
l
5601/0 Number of UI frames received on sapi RSL
Name Q3 : abisInputUiFrame
Object : bts
Function : number of UI (Unnumbered Information) frames received from the
cell TDMA frames on RSL SAPI
Event : receipt of a UI frame on a RSL by the BSC
l
5602/0 Number of I frames sent on sapi RSL
Name Q3 : abisOutputIFrame
Object : bts
Function : number of I (Information) frames sent to the cell TDMA frames on
RSL SAPI
Event : transmission of an I frame on a RSL by the BSC

411--9001--125
l
5603/0 Number of I frames received on sapi RSL
Name Q3 : abisInputIFrame
Object : bts
Function : number of I (Information) frames received from the cell TDMA
frames on RSL SAPI
Event : reception of an I frame on a RSL by the BSC
l
5604/0 Number of UI bytes received on sapi RSL
Name Q3 : abisOutputUiByte
Object : bts
Function : number of UI (Unnumbered Information) bytes sent to the cell
Event : transmission of a UI frame on a RSL by the BSC
l
5605/0 Number of UI bytes sent on sapi RSL
Name Q3 : abisInputUiByte
Object : bts
Function : number of UI (Unnumbered Information) bytes received from the cell
Event : receipt of a UI frame on a RSL by the BSC
l
5606/0 Number of I bytes sent on sapi RSL
Name Q3 : abisOutputIByte
Object : bts
Function : number of I (Information) bytes sent to the cell TDMA frames on RSL
SAPI
Event : transmission of an I frame on a RSL by the BSC

l
5607/0 Number of I bytes received on sapi RSL
Name Q3 : abisInputIByte
Object : bts
Function : number of I (Information) bytes received from the cell TDMA frames
on RSL SAPI
Event : receipt of an I frame on a RSL by the BSC
l
5608/0 Number of Abis Level 2 errors: SUP received with PF 1
Name Q3 : abisLevel2ErrorRxSup1
Object : bts
Function : number of SUP (supervision) frames with the final bit set to 1 received
in established multiframe mode
Event : receipt of a SUP frame with the final bit set to 1 in established
multiframe mode by the BSC
l
5608/1 Number of Abis Level 2 errors: DM received with PF 1
Name Q3 : abisLevel2ErrorRxDm1
Object : bts
Function : number of DM (Disconnected Mode) frames with the final bit set to 1
received in established multiframe mode
Event : receipt of a DM frame with the final bit set to 1 in established
multiframe mode by the BSC

411--9001--125
l
5608/2 Number of Abis Level 2 errors: UA received with PF 1
Name Q3 : abisLevel2ErrorRxUa1
Object : bts
Function : number of UA (Unnumbered Acknowledge) frames with the final bit
set to 1 received in one of the states listed below
Event : receipt by the BSC of a UA frame with the final bit set to 1 in one of the
following states:
a TEI is allocated
the multiframe mode is established
a multiframe mode time-out is running
l
5608/3 Number of Abis Level 2 errors: UA received with PF 0
Name Q3 : abisLevel2ErrorRxUa0
Object : bts
Function : number of UA (Unnumbered Acknowledge) frames with the final bit
set to 0 received in one of the states listed below
Event : receipt by the BSC of a UA frame with the final bit set to 0 in one of the
following states:
a TEI is allocated
waiting for establishment
waiting for clear

l
5608/4 Number of Abis Level 2 errors: DM received with PF 0
Name Q3 : abisLevel2ErrorRxDm0
Object : bts
Function : number of DM (Disconnected Mode) frames with the final bit set to 0
received in one of the states listed below
Event : receipt by the BSC of a DM frame with the final bit set to 0 in one of
the following states:
l
5608/5 Number of Abis Level 2 errors: SABME received
Name Q3 : abisLevel2ErrorRxSabme
Object : bts
Function : number of SABME (Set in Asynchronous Balance Mode Extended)
frames received in one of the states listed below
Event : receipt by the BSC of a SABME frame in one of the following states:
l
5608/6 Number of Abis Level 2 errors: SABME retransmitted
Name Q3 : abisLevel2ErrorTxNSabme
Object : bts
Function : number of SABME frames unsuccessfully retransmitted N150 times
during an establishment period
Event : N150 unsuccessful retransmissions of an SABME frame during an
establishment period

411--9001--125
l
5608/7 Number of Abis Level 2 errors: DISC retransmitted
Name Q3 : abisLevel2ErrorTxNDisc
Object : bts
Function : number of DISC (Disconnect) frames unsuccessfully retransmitted
N150 times during a clearing period
Event : N150 unsuccessful retransmissions of a DISC frame during a clearing
period
l
5608/8 Number of Abis Level 2 errors: I frame with PF 1 retransmitted
Name Q3 : abisLevel2ErrorReqOutState
Object : bts
Function : number of I frames with final bit set to 1 (state request) retransmitted
while a multiframe mode time-out is running
Event : receipt by the BSC of an I frame with final bit set to 1 (state request)
retransmitted while a multiframe mode time-out is running
l
5608/9 Number of Abis Level 2 errors: Wrong NR received
Name Q3 : abisLevel2ErrorBadRxNr
Object : bts
Function : number of errored NR (Not Ready) frames received in one of the
states listed below
Event : receipt by the BSC of an errored NR frame in one of the following
states:

l
5608/10 Number of Abis Level 2 errors: FRMR received
Name Q3 : abisLevel2ErrorRxFrmr
Object : bts
Function : number of FRMR (frame reject) frames received in one of the states
listed below
Event : receipt by the BSC of an FRMR frame in one of the following states:
l
5608/11 Number of Abis Level 2 errors: Unknown frame
Name Q3 : abisLevel2ErrorRxNoImpl
Object : bts
Function : number of unknown frames with final bit set to 0 received in one of the
states listed below
Event : receipt by the BSC of an unknown frame with final bit set to 0 in one of
the following states:
a TEI is allocated
waiting for clear

411--9001--125
l
5608/12 Number of Abis Level 2 errors: Wrong length
Name Q3 : abisLevel2ErrorBadLg
Object : bts
Function : number of wrong length frames received in one of the states listed
below
Event : receipt by the BSC of a wrong length frame in one of the following
states:
a TEI is allocated
waiting for clear
l
5609 Duration of Abis resource unavailability
Name Q3 : abisUnavailabilityTimeMoy
abisUnavailabilityTimeMax . . . . . . Maximum unavailability
duration
abisUnavailabilityTimeCum . . . . . Total unavailability duration
abisUnavailabilityTimeEch . . . . . . Number of samples
Object : bts
Function : average unavailability duration (= total duration divided by the
number of samples) and maximum unavailability duration of the RSL
LAPD links used by the cell TRX/DRXs, expressed in milliseconds
Event : LAPD link unavailability/availability, internal sampling time-out
elapse:
unavailability: start timer
availability: stop timer
• read the instantaneous value of LAPD unavailability duration
• add it to the total duration of LAPD unavailability in the
observation period

l
5610 Duration of Abis resource congestion
Name Q3 : abisCongestionTimeMoy
abisCongestionTimeMax . . . . . . . . Maximum congestion duration
abisCongestionTimeCum . . . . . . . . Total congestion duration
abisCongestionTimeEch . . . . . . . . Number of samples
Object : bts
Function : average congestion duration (= total duration divided by the number
of samples) and maximum congestion duration of the RSL LAPD
links used by the cell TRX/DRXs, expressed in milliseconds
Event : LAPD link congestion/non-congestion, internal sampling time-out
elapse:
congestion: start timer
non-congestion: stop timer
• read the instantaneous value of LAPD congestion duration
• add it to the total duration of LAPD congestion in the
observation period

411--9001--125
5.6 Synthetic permanent BSS counters (from 8000 to 9600)
5.6.1 Constants
The following named constants are defined for use in synthetic counters:
signif1bts (its value is 10)
signif1bsc (its value is 20)
5.6.2 Synthetic permanent BSS counters by counter number
This section contains counter definitions for synthetic BSS counters that have a
defined counter number at the OMC--R. In this section, counters are arranged in
numerical order.
l
8000 Global failure rate of outgoing handovers on TCH
Name Q3 : hoOutTchGlobalFailRate
hoOutTchGlobalFailRateV11
Object : bts
Function : global failure rate, in selection and execution, of outgoing intra-bss,
inter-bss, and intra-bts handovers on TCH in the cell
Formula :
successful outgoing intra handovers on TCH +
successful outgoing inter handovers on TCH +
successful intra-bts handovers on TCH
(1 - ---------------------------------------------)
handovers on TCH required (by cause)
*
greaterperc(hoReq, signif1bts)
=
(1067 + 1068 + 1083)
(1 - --------------------------------------)
∑(1138/i), i = each-possible-screening
*
greaterperc(∑(1138/i), 10)
Type : synthetic permanent

Source : calculated by the OMC when the user asks for an observation report

l
8001 Global failure rate of outgoing handovers on SDCCH
Name Q3 : hoOutSdcchGlobalFailRate
hoOutSdcchGlobalFailRateV11
Object : bts
inter-bss, and intra-bts handovers required on SDCCH in the cell
Formula :
successful outgoing intra handovers on SDCCH +
successful outgoing inter handovers on SDCCH +
successful intra-bts handovers on SDCCH
(1 - ----------------------------------------------)
handovers on SDCCH required (by cause)
*
greaterperc(hoReqSdcch, signif1bts)
=
(1142 + 1143 + 1156)
(1 - ---------------------------------------)
*

l
8002 Ratio of outgoing handover requests on TCH
Name Q3 : hoOutTchRequestRatio
hoOutTchRequestRatioV11
Object : bts
Function : ratio of outgoing intra-bss, inter-bss, and intra-bts handovers
requested to handovers required on TCH in the cell

411--9001--125
Formula :
outgoing intra handovers on TCH requested +
outgoing inter handovers on TCH requested +
intra-bts handovers on TCH requested
(-------------------------------------------)
handovers on TCH required (by cause)
*
greaterperc(hoReq, signif1bts)
=
(1075 + 1076 + 1081)
(----------------------------------------)
*

l
8003 Ratio of outgoing handover requests on SDCCH
Name Q3 : hoOutSdcchRequestRatio
hoOutSdcchRequestRatioV11
Object : bts
requested to handovers required on SDCCH in the cell
Formula :
outgoing intra handovers on SDCCH requested +
outgoing inter handovers on SDCCH requested +
intra-bts handovers on SDCCH requested
(---------------------------------------------)
handovers on SDCCH required (by cause)
*
greaterperc(hoReqSdcch, signif1bts)
=
(1150 + 1151 + 1154)
(-----------------------------------------)
*


l
8004 Selection failure rate of outgoing handovers on TCH
Name Q3 : hoOutTchSelectionFailRate
Object : bts
Function : selection failure rate of outgoing intra-bss, inter-bss, and intra-bts
Formula : V12
outgoing intra-bss handovers on TCH executed +

outgoing inter-bss handovers on TCH executed +
intra-bts handovers on TCH executed
(1 - ----------------------------------------------)
outgoing intra-bss handovers on TCH requested +
outgoing inter-bss handovers on TCH requested +
*
greaterperc(HoRequestOutgoing, signif1bts)
=
(1065 + 1066 + 1082)
(1 - ---------------------)
〈 1075 + 1076 + 1081)
*
greaterperc((1075 + 1076 + 1081), 10)


411--9001--125
l
8005 Selection failure rate of outgoing handovers on SDCCH
Name Q3 : hoOutSdcchSelectionFailRate
Object : bts
handovers on SDCCH in the cell
Formula : V12
outgoing intra handovers on SDCCH executed +

outgoing inter handovers on SDCCH executed +
intra-bts handovers on SDCCH executed
(1 - ----------------------------------------------)
outgoing intra handovers on SDCCH required +
outgoing inter handovers on SDCCH required +
intra-bts handovers on SDCCH required
*
greaterperc(hoRequestOutgoingSdcch, signif1bts)
=
(1140 + 1141 + 1155)
(1 - ---------------------)
1150 + 1151 + 1154
*
greaterperc((1150 + 1151 + 1154), 10)

l
8006 Execution failure rate of outgoing handovers on TCH
Name Q3 : hoOutTchExecutionFailRate
Object : bts
Function : execution failure rate of outgoing intra-bss, inter-bss, and intra-bts
Formula :
successful outgoing intra handovers on TCH +
successful intra-bts handovers on TCH
(1 - --------------------------------------------)
outgoing intra handovers on TCH executed +
outgoing inter handovers on TCH executed +
*
greaterperc(hoExecutionOutgoing, signif1bts)

=
(1067 + 1068 + 1083)
(1 - --------------------)
(1065 + 1066 + 1082)
*
greaterperc((1065 + 1066 + 1082), 10)

l
8007 Execution failure rate of outgoing handovers on SDCCH
Name Q3 : hoOutSdcchExecutionFailRate
Object : bts
Function : execution failure rate of outgoing intra-bss, inter-bss, and intra-bts
handovers on SDCCH in the cell
Formula :
successful outgoing intra handovers on SDCCH +
successful intra-bts handovers on SDCCH
(1 - ----------------------------------------------)
*
greaterperc(hoExecutionOutgoingSdcch, signif1bts)
=
(1142 + 1143 + 1156)
(1 - --------------------)
(1140 + 1141 + 1155)
*
greaterperc((1140 + 1141 + 1155), 10)


411--9001--125
l
8008 Selection failure rate of incoming handovers on TCH
Name Q3 : hoInTchSelectionFailRate
Object : bts
Function : selection failure rate of incoming intra- and inter-bss handovers on
TCH in the cell
Formula :
incoming intra handovers on TCH executed +
incoming inter handovers on TCH executed
(1 - -------------------------------------------)
incoming intra handovers on TCH requested +
incoming inter handovers on TCH requested
*
greaterperc(hoRequestIncoming, signif1bts)
=
(1071 + 1072)
(1 - -------------)
(1069 + 1070)
*
greaterperc((1069 + 1070), 10)


l
8009 Selection failure rate of incoming handovers on SDCCH
Name Q3 : hoInSdcchSelectionFailRate
Object : bts
Function : selection failure rate of incoming intra- and inter-bss handovers on
SDCCH in the cell
Formula :
incoming intra handovers on SDCCH executed +
incoming inter handovers on SDCCH executed
(1 - ---------------------------------------------)
incoming intra handovers on SDCCH requested +
incoming inter handovers on SDCCH requested
*
greaterperc(hoExecutionIncomingSdcch, signif1bts)
=
(1146 + 1047)
(1 - -------------)
(1144 + 1145)
*
greaterperc((1144 + 1145), 10)
l
8010 Execution failure rate of incoming handovers on TCH
Name Q3 : hoInTchExecutionFailRate
Object : bts
Function : execution failure rate of incoming intra- and inter-bss handovers on
TCH in the cell
Formula :
successful incoming intra handovers on TCH +
successful incoming inter handovers on TCH
(1 - --------------------------------------------)
incoming intra handovers on TCH executed +
incoming inter handovers on TCH executed
*
greaterperc(hoExecutionIncoming, signif1bts)
=
(1073 + 1074)
(1 - -------------) * greaterperc((1071 + 1072), 10)
(1071 + 1072)

411--9001--125
l
8011 Execution failure rate of incoming handovers on SDCCH
Name Q3 : hoInSdcchExecutionFailRate
Object : bts
Function : execution failure rate of incoming intra- and inter-bss handovers on
SDCCH in the cell
Formula :
successful incoming intra handovers on SDCCH +
successful incoming inter handovers on SDCCH
(1 - ----------------------------------------------)
incoming intra handovers on SDCCH executed +
incoming inter handovers on SDCCH executed
*
greaterperc(hoSuccessIncomingSdcch, signif1bts)
=
(1148 + 1149)
(1 - -------------) * greaterperc((1146 + 1147), 10)
(1146 + 1147)
l
8012 Ratio of successful outgoing handovers on TCH after first
attempt
Name Q3 : hoOutTchFirstAttemptSuccessRatio
Object : bts
Function : ratio of successful outgoing intra- and inter-bss handovers to the first
cell in the list of eligible cells to successful outgoing handovers on
TCH in the cell
Formula :
successful outgoing (intra + inter)
handovers on TCH after first attempt
(-----------------------------------------------------)
successful outgoing (intra + inter) handovers on TCH
*
greaterperc(hoSuccessOutgoingIntraBss
+hoSuccessOutgoingInterBss, signif1bts)
(1077 + 1078)
= (-------------) * greaterperc((1067 + 1068), 10)
(1067 + 1068)

l
8013 Ratio of successful outgoing handovers on SDCCH after first
attempt
Name Q3 : hoOutSdcchFirstAttemptSuccessRatio
Object : bts
Function : ratio of successful outgoing intra- and inter-bss handovers to the first
cell in the list of eligible cells to successful outgoing handovers on
SDCCH in the cell
Formula :
successful outgoing (intra + inter)
handovers on SDCCH after first attempt
(-------------------------------------------------------)
successful outgoing (intra + inter) handovers on SDCCH
*
greaterperc(hoSuccessOutgoingIntraBssSdcch
+hoSuccessOutgoingInterBssSdcch, signif1bts)
(1152 + 1153)
(-------------) * greaterperc((1142 + 1143), 10)
(1142 + 1143)

l
8016 Total number of establishment indications received for call
initialization
Name Q3 : AllEstabIndicSignalling
Object : bts
Function : number of establishment indications received for call initialization
Formula :
IMMEDIATE ASSIGNMENT messages transmitted on SDCCH
= [∑(1193/i)], i = each-possible-screening


411--9001--125
l
8017 Number of t3107 time-out elapse: Changing from SDCCH to
TCH or preempted PDTCH
Name Q3 : t3107ExpAssign
Object : bts
Function : number of mobiles lost during a change from SDCCH to TCH or
preempted PDTCH because of T3107 time-out elapse
Formula :
TCH/FR or preempted PDTCH assignment requests -
TCH/FR successfully assigned -
ASSIGN FAILURE messages received -
intra-bts handovers on TCH executed +
successful intra-bts handovers on TCH +
unsuccessful intra-bts handovers on TCH with
reestablishment in the serving cell
= 1049 - (1050 + 1055)- (1082 - (1083 + 1134))

l
8018 Number of t3107 time-out elapse: Intra-bts handover on SDCCH
Name Q3 : t3107ExpIntraBtsHoSdcch
Object : bts
Function : number of mobiles lost during intra-bts handovers on SDCCH
because of T3107 time-out elapse
Formula :
intra-bts handovers on SDCCH executed -
successful intra-bts handovers on SDCCH -
unsuccessful intra-bts handovers on SDCCH
= 1155 - (1156 + 1157)


l
8019 Number of t3107 time-out elapse: Intra-bts handover on TCH
Name Q3 : t3107ExpIntraBtsHoTch
Object : bts
Function : number of mobiles lost during intra-bts handovers on TCH because of
T3107 time-out elapse
Formula :
intra-bts handovers on TCH executed -
successful intra-bts handovers on TCH -
unsuccessful intra-bts handovers on TCH
= 1082 - (1083 + 1134)

l
8020 Number of t3103 time-out elapse: Handover on TCH
Name Q3 : t3103ExpTch
Object : bts
Function : number of mobiles lost during a handover on TCH because of T3103
time-out elapse. This counter also tallies --for rare cases-- the receipt of
CLEAR COMMAND during an inter-bss handover with a cause
different from “handover successful” or “call control”
Formula :
outgoing intra handovers on TCH executed -
successful outgoing intra handovers on TCH -
unsuccessful outgoing intra handovers on TCH
+
outgoing inter handovers on TCH executed -
successful outgoing inter handovers on TCH -
unsuccessful outgoing inter handovers on TCH
= 1065 - (1067 + 1135) +
1066 - (1068 + 1136)


411--9001--125
l
8021 Number of t3103 time-out elapse: Handover on SDCCH
Name Q3 : t3103ExpSdcch
Object : bts
Function : number of mobiles lost during a handover on SDCCH because of
T3103 time-out elapse. This counter also tallies - for rare cases-- the
receipt of CLEAR COMMAND during an inter-bss handover with a
cause different from “handover successful” or “call control”
Formula :
outgoing intra handovers on SDCCH executed -
successful outgoing intra handovers on SDCCH -
unsuccessful outgoing intra handovers on SDCCH
+
outgoing inter handovers on SDCCH executed -
successful outgoing inter handovers on SDCCH -
unsuccessful outgoing inter handovers on SDCCH
= 1140 - (1142 + 1158) +

1141 - (1143 + 1159)

8037 Total TCH seizure attempts (not including handovers) at cell level
Name Q3 : attemptedTchFrSeizureNotInclHo
Object : bts
Function : number of TCH seizure attempts not including handovers = Mobile
originating call attempt(s) + Mobile terminating call attempt(s) +
Re--establishment attempt(s) + Directed Retry attempt(s)
Formula : (1609/0 + 1609/1 + 1613) - (1069 + 1070 + 1081)
Note : V11 counter
In V12, 1841/0 counter is more accurate.

8039 Total TCH seizure attempts (including handovers) at cell level

Name Q3 : attemptedTchFrSeizureInclHo
Object : bts
Function : number of TCH seizure attempts including handovers = Mobile
originating call attempt(s) + Mobile terminating call attempt(s) +
Re--establishment attempt(s) + Directed Retry attempt(s) + Incoming
intra--bss handover(s) + incoming inter--bss handover(s)
Formula : 1841/0 + 1069 +1070
Note : V12 counter
l
8040 TCH allocation failures at cell level
Name Q3 : allocationFailureTchFrSeizureInclHo
Object : bts
Function : number of TCH allocation failures including handovers = Mobile
originating call failure(s) + Mobile terminating call failure(s) +
Re--establishment failure(s) + Directed Retry failure(s) + incoming
intra--bss (inter--bts) handover TCH allocation failure(s) + incoming
inter--bss handover TCH allocation failure(s)
Formula : 1842/0 + 1758/0 + 1760/0
Note : V12 counter
l
8044 Clear request at cell level
Name Q3 : clearRequestTraffic
Object : bts
Function : number of call dropped by a CLEAR REQUEST after TCH
assignment complete
Function : Σ 1164/i -- (1164/0 + 1164/1 + 1164/3 + 1164/20 +1164/28 + 1164/31)
Note : V12 counter

411--9001--125
l
8050 Ratio of maximum Downlink power use on TCHs
Name Q3 : relativeTimeDLPowerCtrlMaxTch
Object : bts
Function : ratio of maximum Downlink power use duration on busy TCHs to
TCH connection duration in the cell
Formula :
duration of maximum Downlink power use on busy TCHs
---------------------------------------------------
connection duration of TCHs
1198Cum
= -------
1600Cum
with 1600Cum = ∑(1600) on all transceiverZones

Note : V11-- counter
l
8051 Ratio of maximum Uplink power use on TCHs
Name Q3 : relativeTimeULPowerCtrlMaxTch
Object : bts
Function : ratio of maximum Uplink power use duration on busy TCHs to TCH
connection duration in the cell
Formula :
duration of maximum Uplink power use on busy TCHs
-------------------------------------------------
connection duration of TCHs
1199Cum
= -------
1600Cum


l
8052 Ratio of maximum Downlink power use on SDCCHs
Name Q3 : relativeTimeDLPowerCtrlMaxSdcch
Object : bts
Function : ratio of maximum Downlink power use duration on busy SDCCHs to
SDCCH connection durations in the cell
Formula :
duration of maximum Downlink power use on busy SDCCHs
-----------------------------------------------------
connection duration of SDCCHs
1601Cum
= -------
1603Cum

l
8053 Ratio of maximum Uplink power use on SDCCHs
Name Q3 : relativeTimeULPowerCtrlMaxSdcch
Object : bts
Function : ratio of maximum Uplink power use duration on busy SDCCHs to
SDCCH connection durations in the cell
Formula :
duration of maximum Uplink power use on busy SDCCHs
---------------------------------------------------
connection duration of all SDCCHs
1602Cum
= -------
1603Cum


411--9001--125
l
8104 Ratio of number of requested handovers by dualband MSs to
second frequency band to the number of requested handover for
dualband MS to main frequency band
Name Q3 : requestedHandoverForDualBandMSToSecondVersusMainBand
Object : bts
Function : ratio of number of requested handovers by dualband MSs to second
frequency band to the number of requested handover by dualband
MSs to main frequency band
Formula :
outgoing handovers requested by dualband MSs from
main to second frequency band +
second to same frequency band
---------------------------------------------------
main to same frequency band +
second to main frequency band
1208 + 1784
= ------------
1783 + 1785

Note : V12 counter
l
8105 Ratio of number of establishments of dualband MSs to number of
establishments of phase 1 & 2 MSs
Name Q3 : immAssignDualBandMSRate
Object : bts
Function : ratio of number of establishments of dualband MSs to number of
establishments of phase 1 & 2 MSs

Formula :
immediate assignments for dualband MS
--------------------------------------
ESTABLISH INDICATION messages in
establishment phase received (by cause)
=
1207
--------------------------------------
Note : V12 counter
l
8110 Failure rate of cell tiering from large pattern to small pattern
Name Q3 : hoIntraBtsFailRateTchTieringLargeToSmallPattern
Object : bts
Function : failure rate in selection and execution of intra--bts handovers in the
cell for cell tiering from large pattern to small pattern
Formula :
1802/0
1 - -----------
1138/15
Note : V12 counter
l
8111 Failure rate of cell tiering from small pattern to large pattern
Name Q3 : hoIntraBtsFailRateTchTieringSmallToLargePattern
Object : bts
Function : failure rate in selection and execution of intra--bts handovers in the
cell for cell tiering from small pattern to large pattern
Formula :
1802/1
1 - -----------
1138/16

411--9001--125

Note : V12 counter
l
8500 Maximum global failure rate of outgoing handovers on TCH
Name Q3 : hoOutTchMaxFailRate
hoOutTchMaxFailRateV11
Object : bsc
Function : maximum global failure rate, in selection and execution, of outgoing
intra-bss, inter-bss, and intra-bts handovers on TCH in the BSS
Formula :
max_cell(global failure rate of
outgoing handovers on TCH)
= max_cell(8000)

l
8501 Maximum global failure rate of outgoing handovers on SDCCH
Name Q3 : hoOutSdcchMaxFailRate
hoOutSdcchMaxFailRateV11
Object : bsc
Function : maximum global failure rate, in selection and execution, of outgoing
intra-bss, inter-bss, and intra-bts handovers on SDCCH in the BSS
Formula :
max_cell(global failure rate of
outgoing handovers on SDCCH)
= max_cell(8001)


l
8502 Maximum ratio of outgoing handover requests on TCH
Name Q3 : hoOutTchRequestMaxRatio
hoOutTchRequestMaxRatioV11
Object : bsc
Function : maximum ratio of outgoing intra-bss, inter-bss, and intra-bts
handover requests to handovers on TCH required in the BSS
Formula :
max_cell(ratio of outgoing handover requests on TCH)
= max_cell(8002)

l
8503 Maximum ratio of outgoing handover requests on SDCCH
Name Q3 : hoOutSdcchRequestMaxRatio
hoOutSdcchRequestMaxRatioV11
Object : bsc
Function : maximum ratio of outgoing intra-bss, inter-bss, and intra-bts
handover requests to handovers on SDCCH required in the BSS
Formula :
max_cell(ratio of outgoing handover requests on SDCCH)
= max_cell(8003)


411--9001--125
l
8504 Maximum selection failure rate of outgoing handovers on TCH
Name Q3 : hoOutTchSelectionFailMaxRate
Object : bsc
Function : maximum selection failure rate of outgoing intra-bss, inter-bss, and
intra-bts handovers on TCH in the BSS
Formula :
max_cell(selection failure rate of
= max_cell(8004)

l
8505 Maximum selection failure rate of outgoing handovers on
SDCCH
Name Q3 : hoOutSdcchSelectionFailMaxRate
Object : bsc
Function : maximum selection failure rate of outgoing intra-bss, inter-bss, and
intra-bts handovers on SDCCH in the BSS
Formula :
= max_cell(8005)


l
8506 Maximum execution failure rate of outgoing handovers on TCH
Name Q3 : hoOutTchExecutionFailMaxRate
Object : bsc
Function : maximum execution failure rate of outgoing intra-bss, inter-bss, and
intra-bts handovers on TCH in the BSS
Formula :
max_cell(execution failure rate of
= max_cell(8006)

l
8507 Maximum execution failure rate of outgoing handovers on
SDCCH
Name Q3 : hoOutSdcchExecutionFailMaxRate
Object : bsc
Function : maximum execution failure rate of outgoing intra-bss, inter-bss, and
intra-bts handovers on SDCCH in the BSS
Formula :
= max_cell(8007)


411--9001--125
l
8508 Maximum selection failure rate of incoming handovers on TCH
Name Q3 : hoInTchSelectionFailMaxRate
Object : bsc
Function : maximum selection failure rate of incoming intra- and inter-bss
handovers on TCH in the BSS
Formula :
incoming handovers on TCH)
= max_cell(8008)

l
8509 Maximum selection failure rate of incoming handovers on
SDCCH
Name Q3 : hoInSdcchSelectionFailMaxRate
Object : bsc
Function : maximum selection failure rate of incoming intra- and inter-bss
handovers on SDCCH in the BSS
Formula :
incoming handovers on SDCCH)
= max_cell(8009)


l
8510 Maximum execution failure rate of incoming handovers on TCH
Name Q3 : hoInTchExecutionFailMaxRate
Object : bsc
Function : maximum execution failure rate of incoming intra- and inter-bss
Formula :
incoming handovers on TCH)
= max_cell(8010)

l
8511 Maximum execution failure rate of incoming handovers on
SDCCH
Name Q3 : hoInSdcchExecutionFailMaxRate
Object : bsc
Function : maximum execution failure rate of incoming intra- and inter-bss
Formula :
incoming handovers on SDCCH)
= max_cell(8011)


411--9001--125
l
8512 Minimum ratio of successful outgoing handovers on TCH after
first attempt
Name Q3 : hoOutTchFirstAttemptSuccessMinRatio
Object : bsc
Function : minimum ratio of successful outgoing intra- and inter-bss handovers
after first attempt on TCH in the BSS
Formula :
min_cell(ratio of successful outgoing
handovers on TCH after first attempt)
= min_cell(8012)

l
8513 Minimum ratio of successful outgoing handovers on SDCCH
after first attempt
Name Q3 : hoOutSdcchFirstAttemptSuccessMinRatio
Object : bsc
Function : minimum ratio of successful outgoing intra- and inter-bss handovers
after first attempt on SDCCH in the BSS
Formula :
min_cell (ratio of successful outgoing
handovers on SDCCH after first attempt)
= min_cell (8013)


l
8550 BSC global failure rate of outgoing handovers on TCH
Name Q3 : hoOutTchBscGlobalFailRate
hoOutTchBscGlobalFailRateV11
Object : bsc
inter-bss, and intra-bts handovers on TCH in the BSS
Formula :
sum_cell (successful outgoing
intra + inter + intra-bts
handovers on TCH)
(1 - ----------------------------------------------)
sum_cell(handovers on TCH required (by cause))
*
greaterperc(sum(hoReq), signif1bsc)
=
sum_cell(1067 + 1068 + 1083)
(1 - -------------------------------------------------)
sum_cell(∑(1138/i)), i = each-possible-screening
*
greaterperc(sum_cell(∑(1138/i)), 20)

l
8551 BSC global failure rate of outgoing handovers on SDCCH
Name Q3 : hoOutSdcchBscGlobalFailRate
hoOutSdcchBscGlobalFailRateV11
Object : bsc
inter-bss, and intra-bts handovers on SDCCH in the BSS

411--9001--125
Formula :
sum_cell (successful outgoing
intra + inter + intra-bts
handovers on SDCCH)
(1 - ------------------------------------------------)
sum_cell(handovers on SDCCH required (by cause))
*
greaterperc(sum(hoReqSdcch), signif1bsc)
=
sum_cell(1142 + 1143 +1156)
(1 - -------------------------------------------------)
*
greaterperc(sum_cell(∑(1139/i), 20)

l
8552 BSC ratio of outgoing handover requests on TCH
Name Q3 : hoOutTchRequestBscRatio
hoOutTchRequestBscRatioV11
Object : bsc
requested to handovers on TCH required in the BSS
Formula :
sum_cell
(outgoing intra handovers on TCH requested +
outgoing inter handovers on TCH requested +
intra-bts handovers on TCH requested)
(-----------------------------------------------)
sum_cell(handovers on TCH required (by cause))
*
greaterperc(sum(hoReq), signif1bsc)
=
sum_cell(1075 + 1076 + 1081)
(------------------------------------------------)
*
greaterperc(sum_cell(∑(1138/i), 20)


l
8553 BSC ratio of outgoing handover requests on SDCCH
Name Q3 : hoOutSdcchRequestBscRatio
hoOutSdcchRequestBscRatioV11
Object : bsc
requested to handovers on SDCCH in the BSS
Formula :
sum_cell
(outgoing intra handovers on SDCCH requested +
outgoing inter handovers on SDCCH requested +
intra-bts handovers on SDCCH requested)
(--------------------------------------------------)
sum_cell(handovers on SDCCH required (by cause))
*
greaterperc(sum(hoReqSdcch), signif1bsc)
=
sum_cell(1150 + 1151 + 1154)
(--------------------------------------------------)
*
greaterperc(sum_cell(∑(1139/i)), 20)


411--9001--125
l
8554 BSC selection failure rate of outgoing handovers on TCH
Name Q3 : hoOutTchSelectionBscFailRate
Object : bsc
Formula : V12
outgoing intra-bss handovers on TCH executed +

outgoing inter-bss handovers on TCH executed +
(1 - -----------------------------------------------)
outgoing intra-bss handovers on TCH requested +
outgoing inter-bss handovers on TCH requested +
*
greaterperc(sum(hoRequestOutgoing), signif1bsc)
=
sum_cell(1065 + 1066 + 1082)
(1 - -------------------------------)
sum_cell (1075 + 1076 + 1081)
*
greaterperc(sum_cell (1075 + 1076 + 1081), 20)

l
8555 BSC selection failure rate of outgoing handovers on SDCCH
Name Q3 : hoOutSdcchSelectionBscFailRate
Object : bsc

Formula : V12

(1 - ---------------------------------------------)
outgoing intra handovers on SDCCH required +
outgoing inter handovers on SDCCH required +
intra-bts handovers on SDCCH required
*
greaterperc(sum(hoRequestOutgoingSdcch), signif1bsc)
=
sum_cell(1140 + 1141 + 1155)
(1 - -----------------------------)
sum_cell(1150 + 1151 + 1154)
*
greaterperc(sum_cell(1150 + 1151 + 1154), 20)

l
8556 BSC execution failure rate of outgoing handovers on TCH
Name Q3 : hoOutTchExecutionBscFailRate
Object : bsc
Function : execution failure rate of outgoing intra-bss, intra-bss, and intra-bts
Formula :
sum_cell
(successful outgoing intra handovers on TCH +
successful intra-bts handovers on TCH)
(1 - ------------------------------------------------)
sum_cell
(outgoing intra handovers on TCH executed +
intra-bts handovers on TCH executed)
*
greaterperc(sum(hoExecutionOutgoing), signif1bsc)

411--9001--125
=
sum_cell(1067 +1068 +1083)
(1 - --------------------------)
sum_cell(1065 +1066 +1082)
*
greaterperc(sum_cell(1065 +1066 +1082), 20)

l
8557 BSC execution failure rate of outgoing handovers on SDCCH
Name Q3 : hoOutSdcchExecutionBscFailRate
Object : bsc
Function : execution failure rate of outgoing intra-bss, intra-bss, and intra-bts
Formula :
sum_cell
(successful outgoing intra handovers on SDCCH +
successful intra-bts handovers on SDCCH)
(1 - -------------------------------------------------)
sum_cell
(outgoing intra handovers on SDCCH executed +
intra-bts handovers on SDCCH executed)
*
greaterperc(sum(hoExecutionOutgoingSdcch), signif1bsc)
=
sum_cell(1142 + 1143 + 1156)
(1 - ----------------------------)
sum_cell(1140 + 1141 + 1155)
*
greaterperc(sum_cell(1140 + 1141 + 1155), 20)


l
8558 BSC selection failure rate of incoming inter handovers on TCH
Name Q3 : hoInInterTchSelectionBscFailRate
Object : bsc
Function : selection failure rate of incoming inter-bss handovers on TCH in the
BSS
Formula :
sum_cell(incoming inter-bss HOs on TCH executed)
(1 - -------------------------------------------------)
sum_cell(incoming inter-bss HOs on TCH requested)
*
greaterperc(sum(hoRequestIncomingInterBss), signif1bsc)
=
sum_cell(1072)
(1 - --------------)
sum_cell(1070)
*
greaterperc(sum_cell(1070), 20)

l
8559 BSC selection failure rate of incoming inter handovers on
SDCCH
Name Q3 : hoInInterSdcchSelectionBscFailRate
Object : bsc
Function : selection failure rate of incoming inter-bss handovers on SDCCH in
the BSS
Formula :
sum_cell(incoming inter-bss HOs on SDCCH executed)
(1 - --------------------------------------------------)
sum_cell(incoming inter-bss HOs on SDCCH requested)
*
greaterperc(sum(hoRequestIncomingInterBssSdcch),
signif1bsc)
=
sum_cell(1147)
(1 - --------------) * greaterperc(sum_cell(1145), 20)
sum_cell(1145)


411--9001--125
l
8560 BSC execution failure rate of incoming inter handovers on TCH
Name Q3 : hoInInterTchExecutionBscFailRate
Object : bsc
Function : execution failure rate of incoming inter-bss handovers on TCH in the
BSS
Formula :
sum_cell(successful incoming inter-bss HOs on TCH)
(1 - -------------------------------------------------)
sum_cell(incoming inter-bss HOs on TCH executed)
*
greaterperc(sum(hoExecutionIncomingInterBss), signif1bsc)
=
sum_cell(1074)
sum_cell(1072)

l
8561 BSC execution failure rate of incoming inter handovers on
SDCCH
Name Q3 : hoInInterSdcchExecutionBscFailRate
Object : bsc
Function : execution failure rate of incoming inter-bss handovers on SDCCH in
the BSS
Formula :
sum_cell(successful incoming inter-bss HOs on SDCCH)
(1 - ----------------------------------------------------)
sum_cell(incoming inter-bss HOs on SDCCH executed)
*
greaterperc(sum(hoExecutionIncomingInterBssSdcch),
signif1bsc)
=
sum_cell(1149)
sum_cell(1147)


l
8562 BSC execution failure rate of incoming intra handovers on TCH
Name Q3 : hoInIntraTchExecutionBscFailRate
Object : bsc
Function : execution failure rate of incoming intra-bss handovers on TCH in the
BSS
Formula :
sum_cell(successful incoming intra-bss HOs on TCH)
(1 - --------------------------------------------------)
sum_cell(incoming intra-bss HOs on TCH executed)
*
greaterperc(sum(hoExecutionIncomingIntraBss), signif1bsc)
=
sum_cell(1073)
sum_cell(1071)

l
8563 BSC execution failure rate of incoming intra handovers on
SDCCH
Name Q3 : hoInIntraSdcchExecutionBscFailRate
Object : bsc
Function : execution failure rate of incoming intra-bss handovers on SDCCH in
the BSS
Formula :
sum_cell(successful incoming intra-bss HOs on SDCCH)
(1 - ----------------------------------------------------)
sum_cell(incoming intra-bss HOs on SDCCH executed)
*
greaterperc(sum(hoExecutionIncomingIntraBssSdcch),
signif1bsc)
=
sum_cell(1148)
sum_cell(1146)


411--9001--125
l
8564 BSC execution failure rate of outgoing inter handovers on TCH
Name Q3 : hoOutInterTchExecutionBscFailRate
Object : bsc
Function : execution failure rate of outgoing inter-bss handovers on TCH in the
BSS
Formula :
sum_cell(successful outgoing inter-bss HOs on TCH)
(1 - --------------------------------------------------)
sum_cell(outgoing inter-bss HOs on TCH executed)
*
greaterperc(sum(hoExecutionOutgoingInterBss), signif1bsc)
=
sum_cell(1068)
sum_cell(1066)

l
8565 BSC execution failure rate of outgoing inter handovers on
SDCCH
Name Q3 : hoOutInterSdcchExecutionBscFailRate
Object : bsc
Function : execution failure rate of outgoing inter-bss handovers on SDCCH in
the BSS
Formula :
sum_cell(successful outgoing inter-bss HOs on SDCCH)
(1 - ---------------------------------------------------)
sum_cell(outgoing inter-bss HOs on SDCCH executed)
*
greaterperc(sum(hoExecutionOutgoingInterBssSdcch),
signif1bsc)
=
sum_cell(1143)
sum_cell(1141)


l
8566 BSC ratio of successful outgoing handovers on TCH after first
attempt
Name Q3 : hoOutFirstSuccessTchRatio
Object : bsc
Function : ratio of successful outgoing intra- and inter-bss handovers after first
attempt to successful handovers on TCH in the BSS
Formula :
sum_cell (successful outgoing (intra + inter)
handovers on TCH after first attempt)
(-----------------------------------------------)
handovers on TCH)
*
greaterperc(sum(hoSuccessOutgoingIntraBss)
+sum(hoSuccessOutgoingInterBss), signif1bsc)
=
sum_cell(1077 + 1078)
(--------------------)
sum_cell(1067 + 1068)
*
greaterperc(sum_cell(1067 + 1068), 20)


411--9001--125
l
8567 BSC ratio of successful outgoing handovers on SDCCH after first
attempt
Name Q3 : hoOutFirstSuccessSdcchRatio
Object : bsc
Function : ratio of successful outgoing intra- and inter-bss handovers after first
attempt to successful handovers on SDCCH in the BSS
Formula :
handovers on SDCCH after first attempt)
(--------------------------------------------------)
handovers on SDCCH)
*
greaterperc(sum(hoSuccessOutgoingIntraBssSdcch)
+sum(hoSuccessOutgoingInterBssSdcch), signif1bsc)
=
sum_cell(1152 + 1153)
(---------------------)
sum_cell(1142 + 1143)
*
greaterperc(sum_cell(1142 + 1143), 20)
l
8568 Rate of erroneous messages on the A interface
Name Q3 : aMessageErroneousRate
Object : bsc
Function : rate of erroneous messages on the A interface (applicative level)
Formula :
number of erroneous BSSAP messages received
----------------------------------------------
number of erroneous BSSAP messages received +
number of BSSAP messages received
=
1109
-------------
(1109 + 1107)

l
8569 Ratio of SCCP failure
Name Q3 : sccpResourceFailureRatio
Object : bsc
Function : ratio of the number of SCCP connection refusals (by BSC or MSC) to
the number of SCCP connections allocated (refer to the following
formula)
Formula :
sccpResourceFailureRatio bsc
=
((sccpRessourceFailure+sccpRessourceFailureBscRefusal) /
(sccpAllocated+sccpRessourceFailure+sccpRessourceFailure
BscRefusal))
*
greaterperc (sccpAllocated+sccpRessourceFailure+sccp
RessourceFailureBscRefusal,signif1bsc)
1106/0 + 1106/1
= (-----------------------)
1104/0 + 1106/0 + 1106/1
*
greaterperc((1104/0 + 1106/0 + 1106/1), 20)

l
8600 Average number of SDCCHs used in the BSS
Name Q3 : bscSdcchAveragedUsedMoy
bscSdcchAveragedUsedMax
Object : bsc
Function : average number or maximum number of SDCCHs allocated in all
cells controlled by the BSC
Formula :
sum_cell(average number of SDCCHs used)
= sum_cell(1607)
with 1607 = ∑(1607) on all transceiverZones


411--9001--125
l
8601 Average number of TCH/FR used in the BSS because of SDCCH
unavailability
Name Q3 : bscTchFrAveragedUsedOverflowAllocationMoy
Object : bsc
Function : average number of TCH/FR allocated because of SDCCH
unavailability in all cells controlled by the BSC
Formula :
sum_cell(average number of TCH/FR used)
= sum_cell(1611/2)
with 1611/2= ∑(1611/2) on all transceiverZones

8602 Average number of TCH/FR used in the BSS for call

reestablishments
Name Q3 : bscTchFrAveragedUsedPrimoAllocationMoy
Object : bsc
Function : Average number of TCH/FR used for call re--establishments (primo
allocation) in all cells controlled by the BSC
Formula : sum(tchFrAveragedUsedPrimoAllocationMoy)
= sum(1611/1)
Class : synthetic permanent
l
8602 Average number of TCH/FR used in the BSS for call
reestablishments
Name Q3 : TchFrAveragedUsedPrimoAllocation
Object : bsc
Function : average number of TCH/FR allocated for call reestablishments in all
cells controlled by the BSC

Formula :
= sum_cell(1611/1)
with 1611/1 = ∑(1611/1) on all transceiverZones

l
8603 Average number of TCH/FR used in the BSS for traffic
Name Q3 : bscTchFrAveragedUsedTchAllocationMoy
Object : bsc
Function : average number of TCHs allocated for traffic in all cells controlled by
the BSC
Formula :
= sum_cell(1611/0)

l
8604 Number of signaling channels allocated in the BSS for replies to
paging
Name Q3 : bscPagingResponse
Object : bsc
Function : number of signalling channel allocation requests with cause “reply to
paging request” in all cells controlled by the BSC
Formula :
sum_cell (number of signalling channel requests for
replies to paging)
= sum_cell (1191/1 + 1191/4)


411--9001--125
l
8605 Number of signaling channels allocated in the BSS for access
other than paging
Name Q3 : bscOtherThanPaging
Object : bsc
Function : number of signalling channel allocation requests with cause different
from “reply to paging request” in all cells controlled by the BSC
Formula :
sum_cell
(number of signalling channel requests for non
urgent calls = other services + call
reestablishments + urgent calls))
= sum_cell (1191/0 + 1191/2 + 1191/3 + 1191/5 + 1191/6
+ 1191/7)
l
8606 Number of outgoing handovers on TCH executed in the BSS
Name Q3 : hoOutExecutionBscTch
Object : bsc
Function : number of attempts to execute outgoing intra- and inter-bss handovers
on TCH in all cells controlled by the BSC
Formula :
sum_cell
(outgoing intra handovers on TCH executed +
intra-bts handovers on TCH executed)
= sum_cell(1065 + 1066 + 1082)

l
8607 Number of outgoing handovers on SDCCH executed in the BSS
Name Q3 : hoOutExecutionBscSdcch
Object : bsc
Function : number of attempts to execute outgoing intra- and inter-bss handovers
on SDCCH in all cells controlled by the BSC

Formula :
sum_cell
(outgoing intra handovers on SDCCH executed +
intra-bts handovers on SDCCH executed)
= sum_cell(1140 + 1141 + 1155)

l
8608 Number of incoming handovers on TCH executed in the BSS
Name Q3 : hoInExecutionBscTch
Object : bsc
Function : number of attempts to execute incoming intra- and inter-bss
handovers on TCH in all cells controlled by the BSC
Formula :
sum_cell
(incoming intra handovers on TCH executed +
incoming inter handovers on TCH executed)
= sum_cell(1071 + 1072)
l
8609 Number of incoming handovers on SDCCH executed in the BSS
Name Q3 : hoInExecutionBscSdcch
Object : bsc
Function : number of attempts to execute incoming intra- and inter-bss
handovers on SDCCH in all cells controlled by the BSC
Formula :
sum_cell
(incoming intra handovers on SDCCH executed
incoming inter handovers on SDCCH executed)
= sum_cell(1146 + 1147)

411--9001--125
l
8610 Total number of SDCCHs allocated in the BSS
Name Q3 : bscSdcchAllocated
Object : bsc
Function : total number of SDCCH allocations in the BSS
Formula :
sum_cell(number of SDCCHs allocated)
= sum_cell(1606)

l
8611 Total number of TCH/FR allocated in the BSS because of SDCCH
unavailability
Name Q3 : bscTchFrAllocatedOverflowAllocation
Object : bsc
Function : total number of TCH allocations because of SDCCH unavailability in
all cells controlled by the BSS
Formula :
sum_cell (number of TCH/FR allocated)
= sum_cell(1609/2)

l
8612 Total number of TCH/FR allocated in the BSS for call
reestablishments
Name Q3 : bscTchFrAllocatedPrimoAllocation
Object : bsc
Function : total number of TCH allocations for call reestablishments in all cells
controlled by the BSC

Formula :
sum_cell(number of TCH/FR allocated)
for call reestablishments
= sum_cell(1609/1)
l
8613 Total number of TCH/FR allocated in the BSS for traffic
Name Q3 : bscTchFrAllocatedTchAllocation
Object : bsc
Function : total number of TCH allocations for traffic in all cells controlled by
the BSC
Formula :
sum_cell(number of TCH/FR allocated) for traffic
= sum_cell(1609/0)
l
8623 Average downlink RxLev in dBm
Name Q3 : averageDLRxLev
Object : bts
Function : average downlink RxLev for the cell, in dBm
Formula :
1623/0/Cum/Cell
------------------------------------------------- - 110
1600/0/Cum/Cell/480 + 1603/0/Cum/Cell/470 - 1622/0/Cum/Cell
= -110 +(rxLevDownlink /
(connectionDurationTchCum / 480
+ connectionDurationSdcchCum / 470
- msLostMeasurements) )

411--9001--125
l
8624 Average uplink RxLev in dBm
Name Q3 : averageULRxLev
Object : bts
Function : average uplink RxLev for the cell, in dBm
Formula :
1624/0/Cum/Cell
----------------------------------------------- - 110
1600/0/Cum/Cell/480 + 1603/0/Cum/Cell/470
= -110 + (rxLevUplink /
(connectionDurationTchCum / 480
+ connectionDurationSdcchCum / 470) )

l
8625 Average downlink RxQual in BER
Name Q3 : averageDLRxQual
Object : bts
Function : average downlink RxQual for the cell, in BER
Formula :
1625/0/Cum/Cell
----------------------------------------------------- / 110
1600/0/Cum/Cell/480 + 1603/0/Cum/Cell/470 - 1622/0/Cum/Cell
= (rxQualDownlink / (connectionDurationTchCum / 480

+ connectionDurationSdcchCum / 470
- msLostMeasurements) /100))


l
8626 Average uplink RxQual in BER
Name Q3 : averageULRxQual
Object : bts
Function : average uplink RxQual for the cell, in BER
Formula :
1626/0/Cum/Cell
----------------------------------------------- / 110
1600/0/Cum/Cell/480 + 1603/0/Cum/Cell/470
= (rxQualUplink / (connectionDurationTchCum / 480

+ connectionDurationSdcchCum / 470) / 100)
l
8628 Quality of downlink Abis TRAU frame
Name Q3 : dlMutedAbisTrauFrameRate
Object : bts
Function : ratio of the number of downlink Abis TRAU frame muted or
corrected to the number of downlink Abis TRAU frame received
Formula :
(abisTrauFrameCorrected + abisTrauFrameMuted)/
abisTrauFrameDlReceived)
*
greaterperc(abisTrauFrameD1Received, 10000)
=
1718 + 1719
(------------) * greaterperc(1717, 10000)
1717
Note : V12 counter
l
8629 Correction rate of downlink Abis TRAU frame
Name Q3 : pcmErrCorrEfficiency
Object : bts
Function : ratio of the number of downlink Abis TRAU frames corrected to the
number of downlink Abis TRAU frames received

411--9001--125
Formula :
1718
--------
1717
Note : V12 counter
l
8637 Total TCH seizure attempts (not including handovers) at BSC
level
Name Q3 : bscAttemptedTchFrSeizureNotInclHo
Object : bsc
Function : number of TCH seizure attempts not including handovers
Formula : Σ 1841/0
Note : V12 counter
l
8639 Total TCH seizure attempts (including handovers) at bsc level
Name Q3 : bscAttemptedTchFrSeizureInclHo
Object : bsc
Function : number of TCH seizure attempts including handovers
Formula : Σ 8039
Note : V12 counter
l
8640 TCH allocation failures at bsc level
Name Q3 : bscAllocationFailureTchFrSeizureInclHo
Object : bsc
Function : number of TCH allocation failures including handovers
Formula : Σ 8040
Note : V12 counter

l
8644 G14 consolidated at bsc level
Name Q3 : bscClearRequestTraffic
Object : bsc
Function : number of calls dropped by a CLEAR_REQUEST after TCH
assignment completed
Formula : Σ 8044
Note : V12 counter
l
8700 PCM unavailability in the BSS in seconds
Name Q3 : pcminsecondsMoy
pcminsecondsMax
pcminsecondsCum
pcminsecondsEch
Object : bsc
Function : PCM unavailability in the BSS, expressed in seconds
Formula :
average time of PCM availability
--------------------------------
1000
= c1114 divided by 1000

l
8701 Duration of TCH saturation in seconds
Name Q3 : allTchinsecondsCum
allTchinsecondsMax
allTchinsecondsMoy
allTchinsecondsEch
Object : bts
Function : average duration to allocate all TCH/FR resources and PDTCH
resources configured as preemptable in the cell

411--9001--125
Formula :
average duration to allocate all TCH/FR resources
and PDTCH resources configured as preemptable
-------------------------------------------------
1000

with 1057 = ∑ (1057) on all transceiverZones

l
8702 Duration of SDCCH saturation in seconds
Name Q3 : allSdcchinseconds
allSdcchinsecondsCum
allSdcchinsecondsEch
allSdcchinsecondsMax
allSdcchinsecondsMoy
Object : bts
Function : average allocation duration of all SDCCH resources in the cell
Formula :
average duration of all SDCCH resource allocations
--------------------------------------------------
1000



l
8706 Ratio of SDCCH resource failures in the cell
Name Q3 : cellSdcchResourceFailureRatio
Object : bts
Function : ratio of the number of SDCCH allocation failures in the cell to the
number of SDCCH allocation attempts
Formula :
C1608
(---------------------) * greaterperc(1606, 20)
1606 + 1608 + 1609/2

with 1609/2 = ∑ (1609/2) on all transceiverZones

Note : V12 counter
l
8707 Ratio of TCH resource failures in the cell
Name Q3 : cellTchResourceFailureRatio
Object : bts
Function : ratio of the number of TCH allocation failures in the cell to the number
of TCH or preempted PDTCH allocation attempts
Formula :
1613 + 1163/30
(--------------------------------) * greaterperc(1609/0, 20)
1613 + 1163/30 + 1609/0 + 1609/1 + 1609/2 + 1609/3


Note : V12 counter

411--9001--125
l
8713 Ratio of the number of communications abnormally released in
signalling phase in the cell
Name Q3 : signallingReleaseRatio
Object : bts
Function : ratio of the number true communications released in signalling phase
in the cell, except release by standard CLEAR_COMMAND or on
phantom requests, to the number of communications established in a
signalling channel (initial call establishment or successful incoming
handover on SDCCH)
Formula :
∑(1163/i), i for each possible cause (i#5,6,20)
(-----------------------------------------------)
1195 + 1196
*
greaterperc(estabIndicSig, 20)
1778 - 1163/6
= (---------------) * greaterperc((1195 + 1196), 20)
1195 + 1196

Note : V12 counter
l
8714 Ratio of the number of communications abnormally released in
traffic phase in the cell
Name Q3 : callDropTrafficRatio
Object : bts
Function : ratio of the number of communications released in traffic phase in the
cell, except release by standard CLEAR_COMMAND, to the number
of communications established in a traffic channel (initial TCH or
preempted PDTCH seizures or successful incoming handover on
TCH)

Formula :
∑(1164/i), i for each possible cause
(--------------------------------------)
1050 - 1083 + 1073 + 1074
*
greaterperc(successfulTchFrSeizures, 20)
1779
= (--------------------------)
1050 - 1083 + 1073 + 1074
*
greaterperc(1050, 20)

Note : V12 counter
l
8726 Number of decoded random accesses received by the BTS from
the MS for all the cells
Name Q3 : rachBusyCountCell
Object : bts
Function : sum for each CCCH occurrence of decoded random accesses received
by the BTS from the MS
Formula :
∑(1026), for each CCCH occurence
=rachBusyCount + rachBusyCount2
+ rachBusyCount4 + rachBusyCount6

Note : V12 counter
l
8727 Number of random accesses transmitted to the BSC for all the
cells
Name Q3 : rachAccessCountCell
Object : bts
Function : sum for each CCH occurrence of transmitted random accesses

411--9001--125
Formula :
∑(1027), for each CCCH occurrence
Note : V12 counter
l
8728 Number of paging requests immediately served for all the cells
Name Q3 : pchNoWaitCell
Object : bts
Function : sum for each CCCH occurrence of immediately served pagings
Formula :
Note : V12 counter
l
8729 Number of paging requests served after one wait for all the cells
Name Q3 : pchOneWaitCell
Object : bts
Function : sum for each CCCH occurrence of served pagings after one wait
Formula :
Note : V12 counter
l
8730 Number of paging requests served after two waits for all the cells
Name Q3 : pchTwoWaitCell
Object : bts
Function : sum for each CCCH occurrence of served pagings after two waits
Formula :
Note : V12 counter

l
8731 Number of paging requests served after more than two waits for
all the cells
Name Q3 : pchMoreWaitCell
Object : bts
Function : sum for each CCCH occurrence of served pagings after more than two
waits
Formula :

Note : V12 counter
l
8733 Average (maximum) level on non decoded RACHs for all the cells
Name Q3 : rachNonDecodedAvLevelCellMax
rachNonDecodedAvLevelCellMoy
Object : bts
Function : average (maximum) level on non decoded RACHs on all CCCH
occurrences
Formula :
∑(1033cum)/ ∑(1033ech), for each CCCH occurence
= MAX (1033max), for each CCCH occurrence

Note : V12 counter
l
8734 Average number of waiting messages in PAGCH queue for all the
cells
Name Q3 : pchAveragedQueueLengthCell
pchAveragedQueueLengthCellCum
pchAveragedQueueLengthCellEch
pchAveragedQueueLengthCellMax
pchAveragedQueueLengthCellMoy
Object : bts
Function : average on all CCCH occurrences of number of waiting messages in
PAGCH

411--9001--125
Formula :
∑(1604cum)/ ∑(1604ech), for each CCCH occurence
= MAX (1604max), for each CCCH occurrence

Note : V12 counter
l
8735 Number of pagings discarded in the PAGCH queue for all the
cells
Name Q3 : pchQueuePagesDiscardedCell
Object : bts
Function : sum for each CCCH occurrence of discarded pagings
Formula :

Note : V12 counter
l
8757 Ratio of TCH or preempted PDTCH resource failures in the
TDMA class
Note : This counter is not implemented on the OMC--R.
Name Q3 : tdmaClassTchResourceFailureRatio
Object : transceiverZone
Function : ratio of the number of TCH or preempted PDTCH allocation failures
in the TDMA class
Formula :
1613
----------------------
1613 + 1609/0 + 1609/1

Note : V12 counter

l
8760 Ratio between BIFP0 load and BIFP load average
Name Q3 : cpue0LoadRatio
Object : bts
Function : ratio between BIFP0 load and BIFP load average
Formula :
1835Moy (cpue0)
------------------------------------
1835Moy (cpue0) + 1835Moy (cpue1)
Note : V12 counter
l
8761 Ratio between BIFP1 load and BIFP load average
Name Q3 : cpue1LoadRatio
Object : bts
Function : ratio between BIFP1 load and BIFP load average
Formula :
1835Moy (cpue1)
------------------------------------
1835Moy (cpue0) + 1835Moy (cpue1)
Note : V12 counter
8803 AlltchFrAllocated
Name Q3 : tchOccupancy
Object : bts
Function : ratio of average number of tch used to the average of tch available
Formula :
AlltchFrAveragedUsedMoy
------------------------------------
tchFrAveragedAvailableMoy
Note : V12 counter

411--9001--125
8813 Bad virtual timeslot

Name Q3 : faultyTrxNoBcch
Object : bts
Function : number of non supporting BCCH tdma faulty TRX not detected by
standard hardware supervision. Threshold for the alert : 6.9
Formula :
(failedTchFrSeizures * tchFrAveragedAvailableMoy)
*
greaterperc(attemptedTchFrSeizures,tchFrAveragedAvailableMoy)
Note : V12 counter
9504 : hoExecutionOutgoing
Name Q3 : hoExecutionOutgoing
Object : bts
Function : number of attempts to execute outgoing intra and inter--bss handovers
on TCH in all cells controlled by the BSC
Formula : hoExecutionOutgoingIntraBss
+ hoExecutionOutgoingInterBss
+ hoExecutionIntraBts
= 1065/0 + 1066/0 + 1082/0
9505 : hoExecutionOutgoingSdcch
Name Q3 : hoExecutionOutgoingSdcch
Object : bts
Function : Total number of outgoing handovers on TCH executed in the BSS on
SDCCH

Formula : hoExecutionOutgoingIntraBssSdcch
+ hoExecutionOutgoingInterBssSdcch
+ hoExecutionIntraBtsSdcch
= 1140/0 + 1141/0 + 1155/0
9506 : hoExecutionIncoming
Name Q3 : hoExecutionIncoming
Object : bts
Function : number of attempts to execute incoming intra-- and inter--bss
handovers on TCH in all cells controlled by the BSC
Formula : (1 -- (hoExecutionIncoming / hoRequestIncoming))
* greaterperc(hoRequestIncoming, signif1bts)
9507 : hoExecutionIncomingSdcch
Name Q3 : hoExecutionIncomingSdcch
Object : bts
Function : number of attempts to execute incoming intra-- and inter--bss
handovers on SDCCH in all cells controlled by the BSC
Formula : hoExecutionIncomingIntraBssSdcch
+ hoExecutionIncomingInterBssSdcch
= 1146/0 + 1147/0
9510 Number of signalling channels allocated in the BSS for access

Name Q3 : bscEstabIndicSignalling
Object : bsc
Function : number of signaling channel allocation requests in all cells controlled
by the BSC

411--9001--125
Formula : sum (estabIndicSignalling)
Type : synthetic instrument panel

Source : calculated by the OMC--R on observation message receiving
Note : V11+ counter
9511 Number of outgoing handovers on TCH executed with success in the

BSS
Name Q3 : bscHoSuccessOutgoingTch
Object : bsc
Function : number of successful outgoing intra & inter--bss handovers on TCH in
all cells controlled by the BSC
Formula : sum (hoSuccessOutgoingTch)

Note : V11+ counter
9512 Number of incoming handovers on TCH executed with success in the

BSS
Name Q3 : bscHoSuccessIncomingTch
Object : bsc
Function : number of successful incoming intra & inter--bss handovers on TCH
in all cells controlled by the BSC
Formula : sum (hoSuccessIncomingTch)

Note : V11+ counter
9600 Cell load

Name Q3 : btsLoad
Object : bts
Function : ratio of average number of TCH and preempted PDTCH allocations
to the average number of available TCHs and preempted PDTCH

Formula :
sum (tchFrAveragedUsedMoy)
------------------------------------
sum (tchFrAveragedAvailableTrZoneMoy)
Note : V12 counter

411--9001--125
5.6.3 Other synthetic permanent BSS counters

This section lists synthetic permanent BSS counters that are defined by Q3 name
only. Counters in this section are arranged in alphabetical order.
Name Q3 : AllrachNonDecodedAvLevelCum/Ech
Object : bts
Function : Average level of non--decoded RACH access summed over all time
slots
Formula : rachNonDecodedAvLevelCum
+ rachNonDecodedAvLevelTs2Cum
+ rachNonDecodedAvLevelTs4Cum
+ rachNonDecodedAvLevelTs6Cum;
= sum(1033/0)
where the sum is calculated over all time slots (CUM only)
Name Q3 : AlltchFrAllocated
Object : bts
Function : Number of TCH/FR or preempted PDTCH allocated for traffic in the
Formula : tchFrAllocatedTchAllocation
+ tchFrAllocatedPrimoAllocation
+ tchFrAllocatedOverflowAllocation
+ tchFrAllocatedWps
= 1609/0 + 1609/1 + 1609/2 + 1609/3

Name Q3 : AlltchFrAveragedUsedMoy
Object : bts
Function : Average number of TCH/FR or pre--empted PDTCH used for traffic
Formula : tchFrAveragedUsedTchAllocationMoy
+ tchFrAveragedUsedPrimoAllocationMoy
+ tchFrAveragedUsedOverflowAllocationMoy
= 1611/0 + 1611/1 + 1611/2
(MOY values only)
Name Q3 : connectionDurationCum
Object : bts
Function : Cumulative connection duration as derived from the total duration of
TCH/FR (or pre--empted PDTCH) and SDCCH
Formula : (connectionDurationTchCum / 480 - 1)
+ (connectionDurationSdcchCum / 470 -- 1)
1600/0 1603/0
= (-- - - - - - - - 1) + (-- - - - - - - - 1)
480 470
Note : The value provided by this counter is expressed as a number of 480 ms
(or 470 ms) periods.
Name Q3 : estabIndicSig
Object : bts
Function : Number of ESTABLISH INDICATION messages in establishment
phase received (both phase 1 and phase 2)
Formula : estabIndicSigPhase1 + estabIndicSigPhase2
= 1195/0 + 1196/0

411--9001--125
Name Q3 : failedTchFrSeizures
Object : bts
Function : Ratio of the number unsuccessful TCH/FR seizures to the number of
all TCH/FR seizures attempted
Formula : 1 -- (successfulTchFrSeizures
/ attemptedTchFrSeizures)
1716/0
= 1 - -------
1049/0
Name Q3 : hoReq
Object : bts
Function : Total number of handovers on TCH required: all causes
Formula : hoRequiredTchUplinkStrength
+ hoRequiredTchDownlinkStrength
+ hoRequiredTchUplinkQuality
+ hoRequiredTchDownlinkQuality
+ hoRequiredTchDistance
+ hoRequiredTchPowerBudgetQuality
+ hoRequiredTchCapture
+ hoRequiredTchIntraBtsOm
+ hoRequiredTchIntraBtsUplink
+ hoRequiredTchIntraBtsDownlink
+ hoRequiredTchDirectedRetry
+ hoRequiredTchTdmaClass0
+ hoRequiredTchInterBtsOm
+ hoRequiredTchTraffic
+ hoRequiredTchTieringLargeToSmallPattern
+ hoRequiredTchTieringSmallToLargePattern
= sum(1138/n)
where 0 < n < 16

Name Q3 : hoReqV11
Object : bts
Function : Total number of handovers on TCH required. This formula does not
take into account the addition of screenings 1138/14, 1138/15, or
1138/16.
Formula : hoRequiredTchUplinkStrength
+ hoRequiredTchDownlinkStrength
+ hoRequiredTchUplinkQuality
+ hoRequiredTchDownlinkQuality
+ hoRequiredTchDistance
+ hoRequiredTchPowerBudgetQuality
+ hoRequiredTchCapture
+ hoRequiredTchIntraBtsOm
+ hoRequiredTchIntraBtsUplink
+ hoRequiredTchIntraBtsDownlink
+ hoRequiredTchDirectedRetry
+ hoRequiredTchInterBtsOm
= sum(1138/n)
where 0 < n < 13
Name Q3 : hoReqSdcch
Object : bts
Function : Total number of handovers required on SDCCH: all causes

411--9001--125
Formula : hoRequiredSdcchUplinkStrength
+ hoRequiredSdcchDownlinkStrength
+ hoRequiredSdcchUplinkQuality
+ hoRequiredSdcchDownlinkQuality
+ hoRequiredSdcchDistance
+ hoRequiredSdcchPowerBudget
+ hoRequiredSdcchCapture
+ hoRequiredSdcchIntraBtsOm
+ hoRequiredSdcchInterBtsOm
+ hoRequiredSdcchIntraBtsUplink
+ hoRequiredSdcchIntraBtsDownLink
+ hoRequiredSdcchTraffic
= 1139/0 + 1139/1 + 1139/2 + 1139/3 +
1139/4 + 1139/5 + 1139/6 + 1139/7 +
1139/13 + 1139/8 + 1139/9 + 1139/14
Name Q3 : hoReqSdcchV11
Object : bts
Function : Total number of handovers required on SDCCH. This formula does
not take into account the introduction of the screening 1139/14.
Formula : hoRequiredSdcchUplinkStrength
+ hoRequiredSdcchDownlinkStrength
+ hoRequiredSdcchUplinkQuality
+ hoRequiredSdcchDownlinkQuality
+ hoRequiredSdcchDistance
+ hoRequiredSdcchPowerBudget
+ hoRequiredSdcchCapture
+ hoRequiredSdcchIntraBtsOm
+ hoRequiredSdcchInterBtsOm
+ hoRequiredSdcchIntraBtsUplink
+ hoRequiredSdcchIntraBtsDownLink
= 1139/0 + 1139/1 + 1139/2 + 1139/3 +
1139/4 + 1139/5 + 1139/6 + 1139/7 + 1139/13
+ 1139/8 + 1139/9

Name Q3 : hoRequestIncoming
Object : bts
Function : Number of incoming intra-- and inter--BSS handovers on TCH
requested
Formula : hoRequestIncomingIntraBss
+ hoRequestIncomingInterBss
= 1069/0 + 1070/0
Name Q3 : hoRequestIncomingSdcch
Object : bts
Function : Number of incoming intra-- and inter--BSS handovers on SDCCH
requested
Formula : hoRequestIncomingIntraBssSdcch
+ hoRequestIncomingInterBssSdcch
= 1144/0 + 1145/0
Name Q3 : hoRequestOutgoing
Object : bts
Function : Number of outgoing intra-- and inter--BSS handovers on TCH
requested
Formula : hoRequestOutgoingIntraBss
+ hoRequestOutgoingInterBss
+ hoRequestIntraBts
= 1075/0 + 1076/0 + 1081/0

411--9001--125
Name Q3 : hoRequestOutgoingSdcch
Object : bts
Function : Number of outgoing intra-- and inter--BSS handovers requested on
SDCCH
Formula : hoRequestOutgoingIntraBssSdcch
+ hoRequestOutgoingInterBssSdcch
+ hoRequestIntraBtsSdcch
= 1150/0 + 1151/0 + 1154/0
Name Q3 : hoSuccessIncoming
Object : bts
Function : Ratio of successful incoming handovers on TCH relative to all
handover execution attempts on TCH.
Formula : (1 -- (hoSuccessIncoming / hoExecutionIncoming))
* greaterperc(hoExecutionIncoming, signif1bts)
Name Q3 : hoSuccessIncomingSdcch
Object : bts
Function : Ratio of successful incoming SDCCH handovers relative to all
incoming handover execution attempts on SDCCH
Formula : hoSuccessIncomingIntraBssSdcch
+ hoSuccessIncomingInterBssSdcch
= 1148/0 + 1149/0
Name Q3 : hoSuccessOutgoing
Object : bts
Function : Ratio of successful outgoing handovers on TCH relative to all
handover execution attempts on TCH

Formula : hoSuccessOutgoingIntraBss
+ hoSuccessOutgoingInterBss
+ hoSuccessIntraBts
= 1067/0 + 1068/0 + 1083/0
Name Q3 : hoSuccessOutgoingFirst
Object : bts
Function : Number of successful outgoing inter-- and intra--BSS handovers on
TCH after first attempt
Formula : hoSuccessOutgoingFirstIntra
+ hoSuccessOutgoingFirstInter
= 1077/0 + 1078/0
Name Q3 : hoSuccessOutgoingFirstSdcch
Object : bts
Function : Number of successful outgoing intra-- and inter--BSS handovers on
SDCCH after first attempt
Formula : hoSuccessOutgoingFirstIntraSdcch
+ hoSuccessOutgoingFirstInterSdcch
= 1152/0 + 1153/0
Name Q3 : hoSuccessOutgoingSdcch
Object : bts
Function : Ratio of successful outgoing handovers on SDCCH, relative
to all outgoing handover execution attempts on SDCCH
Formula : hoSuccessOutgoingIntraBssSdcch
+ hoSuccessOutgoingInterBssSdcch
+ hoSuccessIntraBtsSdcch
= 1142/0 + 1143/0 + 1156/0

411--9001--125
5.6.4 Synthetic permanent PCU counters

This section contains definitions of synthetic permanent counters calculated at the
OMC from data collected at the PCUSN. Counters in this section are listed in
alphabetical order by Q3 name.
Name Q3 : contentionFailureRatioOnePhaseAccess
Object : ccch
Function : Ratio of the number of failures of the contention resolution procedure
in case to the cumulative number of Immediate Assignment Uplink
messages sent by the PCU in the case of one phase access, scaled to the
cumulative number of one phase access RACH (Channel Request)
received by the PCU
Formula : (pcuContentionFailureOnePhase
/ pcuUpTbfImmediateAssignmentOnePhase) *
100
* greater (pcuChannelRequestOnePhase,
100
* greater (pcuUpTbfImmediateAssignmentOnePhase, 0)
15192/0
= ------ - - - - * 100
15191/0
* greater (15190/0, 100)
* greater (15191/0, 0)
Name Q3 : gprsFailureRatioOnePhaseAccess
Object : ccch
Function : Ratio of the number of Immediate Assignment Uplink messages sent
by the PCU to establish a one phase access UL TBF relative to the
cumulative number of one phase access RACH (Channel Request)
received by the PCU

Formula : (1 - (pcuUpTbfImmediateAssignmentOnePhase
/ pcuChannelRequestOnePhase) ) * 100
* greater (pcuChannelRequestOnePhase, 100)
* greater (pcuUpTbfImmedaiteAssignmentOnePhase, 0)
15191/0
= (1 ------------ - ) * 100
15190/0
* greater (15190/0, 100)
* greater (15191/0, 0)

Name Q3 : gprsFailureRatioTwoPhaseAccess
Object : ccch
Function : The ratio of the total number of PACKET RESOURCE REQUEST
messages received by the PCU from the MS in the second phase of the
2--phase access uplink TBF establishment, relative to the number of
IMMEDIATE ASSIGNMENT messages sent in the first phase of
two--phase assignment
Formula : (1 - (packetResourceRequest
/ tpaImmediateAssignment)) * 100
* greater (tpaImmedaiteAssignment, 100)
15056/1
= ( 1 -- ------ - - - - - - - - - - - - - ) * 100
15058/0 -- 15191/0
* greater ((15058/0 - 15191/0,) 100)

Name Q3 : tpaImmediateAssignment
Object : ccch
Function : The number of IMMEDIATE ASSIGNMENT messages sent in the
first phase of two--phase assignment

411--9001--125
Formula : upTbfImmediateAssignment
- pcuUpTbfImmediateAssignmentOnePhase
= 15058/0 -- 15191/0

5.7 Raw permanent md counters (from 9940 to 10050)
5.7.1 SYBASE counters (from 9940 to 10050)
These totalizer counters are provided by the SYBASE OMC--R agent server. They
are read by the OMC--R agent self-observation task at the end of each
mdGranularityPeriod.
ll
9940 Total number of SYBASE errors
Name Q3 : sybaseTotalError
Object : SYBASE agent server
Function : number of anomalies detected by the SYBASE server during disk
read/write operations in the observation period
Source : SYBASE server, calculated by the OMC--R agent
ll
9941 Total number of SYBASE read operations
Name Q3 : sybaseTotalRead
Function : number of disk read operations performed by the SYBASE server in
ll
9942 Total number of SYBASE write operations
Name Q3 : sybaseTotalWrite
Function : number of disk write operations performed by the SYBASE server in

411--9001--125
ll
9943 CPU time used by the SYBASE server (1/10 s)
Name Q3 : sybaseCpuBusy
Function : CPU time used by the SYBASE server in the observation period,
expressed in 1/10th of a second
ll
9944 I/O time used by the SYBASE server (1/10 s)
Name Q3 : sybaseIoBusy
Function : time spent by the SYBASE server in input/output operations during
the observation period, expressed in 1/10th of a second
ll
9945 SYBASE server idle time (s)
Name Q3 : sybaseIdle
Function : time of SYBASE server unoccupancy in the observation period,
expressed in seconds
ll
9946 Number of packets received by the SYBASE server
Name Q3 : sybasePacketIn
Function : number of data packets received by the SYBASE server in the
observation period

ll
9947 Number of packets sent by the SYBASE server
Name Q3 : sybasePacketOut
Function : number of data packets sent by the SYBASE server in the observation
period
ll
9948 Number of erroneous packets sent or received by the SYBASE
server
Name Q3 : sybasePacketErr
Function : number of anomalies detected by the SYBASE server when sending
or receiving data packets in the observation period
ll
10047 Average filling rate of configuration database cm_db
Name Q3 : cmDatabaseUsed
cmDatabaseUsedCum . . . . . . . . . . Total filling rate
cmDatabaseUsedEch . . . . . . . . . . . Number of samples
Object : active OMC--R agent server
Function : average rate (= total rate divided by the number of samples) of
configuration “cm_db” database used, calculated at the end of the
observation period, expressed in %

411--9001--125
ll
10048 Average filling rate of fault database fm_db
Name Q3 : fmDatabaseUsed
fmDatabaseUsedCum . . . . . . . . . . Total filling rate
fmDatabaseUsedEch . . . . . . . . . . . Number of samples
Function : average rate (= total rate divided by the number of samples) of fault
“fm_db” database used, calculated at the end of the observation
period, expressed in %
ll
10049 Average filling rate of configuration log cm_db
Name Q3 : cmLogUsed
cmLogUsedCum . . . . . . . . . . . . . . Total filling rate
cmLogUsedEch . . . . . . . . . . . . . . . Number of samples
configuration “cm_db” log used, calculated at the end of the
ll
10050 Average filling rate of fault log fm_db
Name Q3 : fmLogUsed
fmLogUsedCum . . . . . . . . . . . . . . . Total filling rate
fmLogUsedEch . . . . . . . . . . . . . . . Number of samples
Function : average rate (= total rate divided by the number of samples) of fault
“fm_db” log used, calculated at the end of the observation period,
expressed in %

5.7.2 SCSE counters (from 9970 to 9974)

These totalizer counters are provided by the SCSE service. They are read by the
OMC--R agent self-observation task at the end of each mdGranularityPeriod.
ll
9970 Number of TGE sent
Name Q3 : scseTgeOut
Function : number of global operation transactions (TGE) sent by the server to
the BSC in the observation period
Source : SCSE service, calculated by the OMC--R agent
ll
9971 Number of RGE received
Name Q3 : scseRgeIn
Function : number of global operation replies (RGE) sent by the BSC to the
server in the observation period
ll
9972 Number of BSS/OMC--R link failures
Name Q3 : scseFailConnect
Function : number of BSS/OMC--R link failures detected in the observation
period
ll
9973 Total number of TGE reservations refused
Name Q3 : scseTotTgeRefused
Function : number of TGE reservations refused by the server in the observation
period

411--9001--125
ll
9974 Total number of association release requests sent by the BSC
Name Q3 : scseTotAssocFree
Function : number of association release requests sent by the BSC in the
observation period
5.7.3 UNIX counters (from 9984 to 10046)

These totalizer and value counters are provided by the SUNOS system. They are
read by the OMC--R agent self-observation task at the end of each
ll
9984 Average load of NMC server CPU 0
Name Q3 : unixCpu0UsedNMCSrv
unixCpu0UsedNMCSrvCum . . . . . Total load of NMC server CPU
0
unixCpu0UsedNMCSrvEch . . . . . . Number of samples
Function : average load (= total load divided by the number of samples) of the
server CPU 0 in the observation period, expressed in %
Source : SUNOS system, calculated by the OMC--R agent
ll
9985 Average load of NMC server CPU 1
Name Q3 : unixCpu1UsedNMCSrv
unixCpu1UsedNMCSrvCum . . . . . Total load of NMC server CPU
1
unixCpu1UsedNMCSrvEch . . . . . . Number of samples

ll
9988 Average filling rate of NMC server SWAP area
Name Q3 : unixSwapNMCSrv
unixSwapNMCSrvCum . . . . . . . . . Total filling rate of SWAP area
unixSwapNMCSrvEch . . . . . . . . . . Number of samples
Function : average rate (= total rate divided by the number of samples) of swap
memory used in the server, calculated at the end of the observation
ll
9990 Average filling rate of NMC server “/” partition
Name Q3 : unixRootPartitionNMCSrv
unixRootPartitionNMCSrvCum . . Total partition filling rate
unixRootPartitionNMCSrvEch . . . Number of samples
Function : average rate (= total rate divided by the number of samples) of disk
root partition used in the server, calculated at the end of the
ll
9991 Average filling rate of NMC server “/tmp” partition
Name Q3 : unixTmpPartitionNMCSrv
unixTmpPartitionNMCSrvCum . . Total partition filling rate
unixTmpPartitionNMCSrvEch . . . Number of samples
“/tmp” partition used in the server, calculated at the end of the

411--9001--125
ll
9993 Average filling rate of “/MD/obs” partition
Name Q3 : unixObsPartition
unixObsPartitionCum . . . . . . . . . . Total partition filling rate
unixObsPartitionEch . . . . . . . . . . . Number of samples
“/MD/obs” partition used in the server, calculated at the end of the
ll
9994 Average filling rate of “/MD/notif” partition
Name Q3 : unixNotifPartition
unixNotifPartitionCum . . . . . . . . . Total partition filling rate
unixNotifPartitionEch . . . . . . . . . . Number of samples
“/MD/notif” partition used in the server, calculated at the end of the
ll
9995 Average filling rate of “/MD/restored/obs” partition
Name Q3 : unixRestoredObsPartition
unixRestoredObsPartitionCum . . . Total partition filling rate
unixRestoredObsPartitionEch . . . . Number of samples
“/MD/restored/obs” partition used in the server, calculated at the end
of the observation period, expressed in %

ll
9996 Average filling rate of “/MD/restored/notif” partition
Name Q3 : unixRestoredNotifPartition
unixRestoredNotifPartitionCum . . Total partition filling rate
unixRestoredNotifPartitionEch . . . Number of samples
“/MD/restored/notif” partition used in the server, calculated at the end
of the observation period, expressed in %
ll
9997 Average filling rate of “/MD/trace_function” partition
Name Q3 : unixTracePartition
unixTracePartitionCum . . . . . . . . . Total partition filling rate
unixTracePartitionEch . . . . . . . . . . Number of samples
“/MD/trace_function” partition used in the server, calculated at the
end of the observation period, expressed in %
ll
9998 Average filling rate of “/MD/data/ssn” partition
Name Q3 : unixDataSsnPartition
unixDataSsnPartitionCum . . . . . . . Total partition filling rate
unixDataSsnPartitionEch . . . . . . . . Number of samples
“/MD/data/ssn” partition used in the server, calculated at the end of
the observation period, expressed in %

411--9001--125
ll
9999 Average filling rate of “/MD/restored/trace_function” partition
Name Q3 : unixRestoredTracePartition
unixRestoredTracePartitionCum . . Total partition filling rate
unixRestoredTracePartitionEch . . . Number of samples
“/MD/restored/trace_function” partition used in the server, calculated
at the end of the observation period, expressed in %
ll
10043 Average filling rate of NMC server “/MD/base” partition
Name Q3 : unixMdrBasePartitionNMCSrv
unixMdrBasePartitionNMCSrvCum . . . . . Total partition filling rate
unixMdrBasePartitionNMCSrvEch . . . . . . Number of samples
“/MD/base” partition used in the server, calculated at the end of the
ll
10044 Average filling rate of NMC server “/MD/data” partition
Name Q3 : unixMdrDataPartitionNMCSrv
unixMdrDataPartitionNMCSrvCum . . . . . Total partition filling rate
unixMdrDataPartitionNMCSrvEch . . . . . . Number of samples
“/MD/data” partition used in the server, calculated at the end of the

ll
10045 Average filling rate of NMC server “/CMN/base” partition
Name Q3 : unixCmnBasePartitionNMCSrv
unixCmnBasePartitionNMCSrvCum . . . . Total partition filling rate
unixCmnBasePartitionNMCSrvEch . . . . . . Number of samples
“/CMN/base” partition used in the server, calculated at the end of the
ll
10046 Average filling rate of NMC server “/CMN/data” partition
Name Q3 : unixCmnDataPartitionNMCSrv
unixCmnDataPartitionNMCSrvCum . . . . Total partition filling rate
unixCmnDataPartitionNMCSrvEch . . . . . . Number of samples
“/CMN/data” partition used in the server, calculated at the end of the
5.7.4 Q3 counters (from 10000 to 10038)

These totalizer counters are provided by the CMIS and FTAM services. They are
read by the OMC--R agent self-observation task at the end of each
5.7.4.1 Request on md subtree counters

ll
10000 Number of CMIS GET requests received for the md subtree
Name Q3 : ommdGetRequest
Function : number of CMIS GET requests about md subtree objects received in
Event : receipt of a CMIS GET request about an md subtree object
Source : CMIS service, calculated by the OMC--R agent

411--9001--125
ll
10001 Number of CMIS GET confirmations sent for the md subtree
Name Q3 : ommdGetConf
Function : number of CMIS GET confirmations about md subtree objects sent in
Event : transmission of a CMIS GET confirmation about an md subtree object
ll
10002 Number of CMIS CREATE requests received for the md subtree
Name Q3 : ommdCreRequest
Function : number of CMIS CREATE requests about md subtree objects
received in the observation period
Event : receipt of a CMIS CREATE request about an md subtree object
ll
10003 Number of CMIS CREATE confirmations sent for the md
subtree
Name Q3 : ommdCreConf
Function : number of CMIS CREATE confirmations about md subtree objects
sent in the observation period
Event : transmission of a CMIS CREATE confirmation about an md subtree
object

ll
10004 Number of CMIS SET requests received for the md subtree
Name Q3 : ommdSetRequest
Function : number of CMIS SET requests about md subtree objects received in
Event : receipt of a CMIS SET request about an md subtree object
ll
10005 Number of CMIS SET confirmations sent for the md subtree
Name Q3 : ommdSetConf
Function : number of CMIS SET confirmations about md subtree objects sent in
Event : transmission of a CMIS SET confirmation about an md subtree object
ll
10006 Number of CMIS DELETE requests received for the md subtree
Name Q3 : ommdDelRequest
Function : number of CMIS DELETE requests about md subtree objects
Event : receipt of a CMIS DELETE request about an md subtree object

411--9001--125
ll
10007 Number of CMIS DELETE confirmations sent for the md
subtree
Name Q3 : ommdDelConf
Function : number of CMIS DELETE confirmations about md subtree objects
Event : transmission of a CMIS DELETE confirmation about an md subtree
object
ll
10008 Number of CMIS ACTION requests received for the md subtree
Name Q3 : ommdActRequest
Function : number of CMIS ACTION requests about md subtree objects
Event : receipt of a CMIS ACTION request about an md subtree object
ll
10009 Number of CMIS ACTION confirmations sent for the md subtree
Name Q3 : ommdActConf
Function : number of CMIS ACTION confirmations about md subtree objects
Event : transmission of a CMIS ACTION confirmation about an md subtree
object

ll
10010 Number of CMIS CANCEL GET requests received for the md
subtree
Name Q3 : ommdCancelGetRequest
Function : number of CMIS CANCEL GET requests about md subtree objects
Event : receipt of a CMIS CANCEL GET request about an md subtree object
ll
10011 Number of CMIS CANCEL GET confirmations sent for the md
subtree
Name Q3 : ommdCancelGetConf
Function : number of CMIS CANCEL GET confirmations about md subtree
objects sent in the observation period
Event : transmission of a CMIS CANCEL GET confirmation about an md
subtree object
5.7.4.2 Request on network counters
ll
10012 Number of CMIS GET requests received for the network subtree
Name Q3 : omnetGetRequest
Function : number of CMIS GET requests about network subtree objects
Event : receipt of a CMIS GET request about a network subtree object

411--9001--125
ll
10013 Number of CMIS GET confirmations sent for the network
subtree
Name Q3 : omnetGetConf
Function : number of CMIS GET confirmations about network subtree objects
Event : transmission of a CMIS GET confirmation about a network subtree
object
ll
10014 Number of CMIS CREATE requests received for the network
subtree
Name Q3 : omnetCreRequest
Function : number of CMIS CREATE requests about network subtree objects
Event : receipt of a CMIS CREATE request about a network subtree object
ll
10015 Number of CMIS CREATE confirmations sent for the network
subtree
Name Q3 : omnetCreConf
Function : number of CMIS CREATE confirmations about network subtree
Event : transmission of a CMIS CREATE confirmation about a network
subtree object

l
10016 Number of CMIS SET requests received for the network subtree
Name Q3 : omnetSetRequest
Function : number of CMIS SET requests about network subtree objects
Event : receipt of a CMIS SET request about a network subtree object
ll
10017 Number of CMIS SET confirmations sent for the network
subtree
Name Q3 : omnetSetConf
Function : number of CMIS SET confirmations about network subtree objects
Event : transmission of a CMIS SET confirmation about a network subtree
object
ll
10018 Number of CMIS DELETE requests received for the network
subtree
Name Q3 : omnetDelRequest
Function : number of CMIS DELETE requests about network subtree objects
Event : receipt of a CMIS DELETE request about a network subtree object

411--9001--125
ll
10019 Number of CMIS DELETE confirmations sent for the network
subtree
Name Q3 : omnetDelConf
Function : number of CMIS DELETE confirmations about network subtree
Event : transmission of a CMIS DELETE confirmation about a network
subtree object
ll
10020 Number of CMIS ACTION requests received for the network
subtree
Name Q3 : omnetActRequest
Function : number of CMIS ACTION requests about network subtree objects
Event : receipt of a CMIS ACTION request about a network subtree object
ll
10021 Number of CMIS ACTION confirmations sent for the network
subtree
Name Q3 : omnetActConf
Function : number of CMIS ACTION confirmations about network subtree
Event : transmission of a CMIS ACTION confirmation about a network
subtree object

ll
10022 Number of CMIS CANCEL GET requests received for the
network subtree
Name Q3 : omnetCancelGetRequest
Function : number of CMIS CANCEL GET requests about network subtree
objects received in the observation period
Event : receipt of a CMIS CANCEL GET request about a network subtree
object
ll
10023 Number of CMIS CANCEL GET confirmations sent for the
network subtree
Name Q3 : omnetCancelGetConf
Function : number of CMIS CANCEL GET confirmations about network
subtree objects sent in the observation period
Event : transmission of a CMIS CANCEL GET confirmation about a network
subtree object
5.7.4.3 Q3 notification counters
ll
10024 Number of notifications received
Name Q3 : notifsReceived
Function : number of notifications received by the secured notification server of
the OMC--R agent in the observation period
Event : receipt of a notification by the secured notification server

411--9001--125
ll
10025 Number of notifications sent for the first time
Name Q3 : notifsSentOnce
Function : number of notifications transmitted a first time to the managers in the
observation period
Event : first transmission of a notification to the managers
ll
10026 Number of notifications sent a second time
Name Q3 : notifsTransmitAgainOnce
Function : number of notifications transmitted a second time to the managers in
Event : second transmission of a notification to the managers
ll
10027 Number of notifications sent more than two times
Name Q3 : notifsTransmitAgainTwiceAndMore
Function : number of notifications transmitted more than two times to the
managers in the observation period
Event : more than two transmissions of a notification to the managers
ll
10028 Number of notifications that were not sent to all managers
Name Q3 : notifsReachMaxTransmit
Function : number of notifications that cannot be transmitted to all the managers
in the observation period
Event : stop transmitting a same notification to the managers

5.7.4.4 FTAM counters
ll
10029 Number of FTAM GET transfer requests
Name Q3 : ftamFtiGet
Function : number of FTAM GET transfers requested in the observation period
Event : start of an FTAM GET transfer
Source : FTAM service, calculated by the OMC--R agent
ll
10030 Number of successful FTAM GET transfers
Name Q3 : ftamFtiGetConf
Function : number of successful FTAM GET transfers in the observation period
Event : normal completion of an FTAM GET transfer
ll
10031 Number of FTAM PUT transfer requests
Name Q3 : ftamFtiPut
Function : number of FTAM PUT transfers requested in the observation period
Event : start of an FTAM PUT transfer
ll
10032 Number of successful FTAM PUT transfers
Name Q3 : ftamFtiPutConf
Function : number of successful FTAM PUT transfers in the observation period
Event : normal completion of an FTAM PUT transfer

411--9001--125
ll
10033 Number of FTAM DELETE requests
Name Q3 : ftamFtiDelete
Function : number of FTAM DELETE requests in the observation period
Event : transmission of an FTAM DELETE request
ll
10034 Number of successful FTAM DELETE requests
Name Q3 : ftamFtiDeleteConf
Function : number of successful FTAM DELETE requests in the observation
period
Event : normal completion of an FTAM DELETE request
ll
10035 Number of FTAM DIR transfer requests
Name Q3 : ftamFtiDir
Function : number of FTAM DIR transfers requested in the observation period
Event : start of an FTAM DIR transfer
ll
10036 Number of successful FTAM DIR transfers
Name Q3 : ftamFtiDirConf
Function : number of successful FTAM DIR transfers in the observation period
Event : normal completion of an FTAM DIR transfer

ll
10037 Number of FTAM RENAME requests
Name Q3 : ftamFtiRename
Function : number of FTAM RENAME requests in the observation period
Event : transmission of an FTAM RENAME request
ll
10038 Number of successful FTAM RENAME requests
Name Q3 : ftamFtiRenameConf
Function : number of successful FTAM RENAME requests in the observation
period
Event : normal completion of an FTAM RENAME request

411--9001--125
5.8 Raw permanent manager counters
5.8.1 SYBASE counters
These totalizer counters are provided by the SYBASE server. They are read by the
OMC--R manager self-observation task at the end of each observation period (static
configuration data).
ll
Total number of SYBASE errors
Name : omcSybaseTotalError
Object : SYBASE server (OMC--R manager and connected workstations)
Function : number of anomalies detected by the SYBASE server during disk
read/write operations in the observation period
Source : SYBASE server, calculated by the OMC--R manager
ll
Total number of SYBASE read operations
Name : omcSybaseTotalRead
Function : number of disk read operations performed by the SYBASE server in
ll
Total number of SYBASE write operations
Name : omcSybaseTotalWrite
Function : number of disk write operations performed by the SYBASE server in

ll
CPU time used by the SYBASE server (1/10 s)
Name : omcSybaseCpuBusy
Function : CPU time used by the SYBASE server in the observation period,
expressed in 1/10th of a second
ll
I/O time used by the SYBASE server (1/10 s)
Name : omcSybaseIoBusy
Function : time spent by the SYBASE server in input/output operations during
the observation period, expressed in 1/10th of a second
ll
SYBASE server idle time (s)
Name : omcSybaseIdle
Function : time of SYBASE server unoccupancy in the observation period,
expressed in seconds
ll
Number of packets received by the SYBASE server
Name : omcSybasePacketIn
Function : number of data packets received by the SYBASE server in the
observation period

411--9001--125
ll
Number of packets sent by the SYBASE server
Name : omcSybasePacketOut
Function : number of data packets sent by the SYBASE server in the observation
period
ll
Number of erroneous packets sent or received by the SYBASE server
Name : omcSybasePacketErr
Function : number of anomalies detected by the SYBASE server when sending
or receiving data packets in the observation period
ll
Average filling rate of omc_db database
Name : omcDatabaseUsed
omcDatabaseUsedCum . . . . . . . . . Total filling rate
omcDatabaseUsedEch . . . . . . . . . . Number of samples
Object : active OMC--R manager server
“cm_db” database used, calculated at the end of the observation
Source : SUNOS system, calculated by the OMC--R manager
ll
Average filling rate of segment 0 of trace_db database
Name : traceDatabaseSeg0Used
traceDatabaseSeg0UsedCum . . . . . Total filling rate
traceDatabaseSeg0UsedEch . . . . . . Number of samples


“trace_db” database segment 0 used, calculated at the end of the
ll
Average filling rate of segment 1 of trace_db database
Name : traceDatabaseSeg1Used
traceDatabaseSeg1UsedCum . . . . . Total filling rate
traceDatabaseSeg1UsedEch . . . . . . Number of samples
“trace_db” database segment 1 used, calculated at the end of the
ll
Average filling rate of rst_trace_db database
Name : rsttraceDatabaseUsed
rsttraceDatabaseUsedCum . . . . . . . Total filling rate
rsttraceDatabaseUsedEch . . . . . . . . Number of samples
“rsttrace_db” database used, calculated at the end of the observation

411--9001--125
5.8.2 X.25 counters

These totalizer counters are provided by the X.25--2 layer. They are read by the
OMC--R manager self-observation task at the end of each observation period (static
configuration data).
ll
Number of X25-2 packets received on port x
Name : omcX25PacketInPort0
omcX25PacketInPort1
omcX25PacketInPort2
omcX25PacketInPort3
Object : active server ( OMC--R manager and connected workstations)
Function : number of X.25--2 packets received on the X.25 port x in the
observation period
Source : X.25--2 layer, calculated by the OMC--R manager
l
Number of X25-2 packets sent on port x
Name : omcX25PacketOutPort0
omcX25PacketOutPort1
Object : active server (OMC--R manager and connected workstations)
Function : number of X.25--2 packets transmitted on the X.25 port x in the
observation period
l
Number of X25-2 packets received with CRC error on port x
Name : omcX25CrcErrorsPort0
omcX25CrcErrorsPort1
Function : number of frames with CRC errors received on the X.25 port 0 or 1 in
Event : checksum error detected on receipt of a frame on the X.25 port

l
Number of abort requests received on port x
Name : omcX25AbortsPort0
omcX25AbortsPort1
omcX25AbortsPort2
omcX25AbortsPort3
Function : number of aborted frames received on the X.25 port 0 or 1 in the
observation period
Event : receipt 8 consecutive times on the X.25 port of a frame that does not
comply with HDLC frame numbering
5.8.3 UNIX counters

These totalizer and value counters are provided by the SUNOS system. They are
read by the OMC--R manager self-observation task at the end of each observation
period (static configuration data).
ll
Average load of CPU 0
Name : omcUnixCpu0Used
omcUnixCpu0UsedCum . . . . . . . . Total load of CPU 0
omcUnixCpu0UsedEch . . . . . . . . . Number of samples
l
Average load of CPU 1
Name : omcUnixCpu1Used
omcUnixCpu1UsedCum . . . . . . . . Total load of CPU 1
omcUnixCpu1UsedEch . . . . . . . . . Number of samples

411--9001--125
ll
Average filling rate of SWAP area
Name : omcUnixSwap
omcUnixSwapCum . . . . . . . . . . . . Total filling rate of SWAP area
omcUnixSwapEch . . . . . . . . . . . . . Number of samples
Function : average rate (= total rate divided by the number of samples) of swap
memory used in the server, calculated at the end of the observation
ll
Average filling rate of “/” partition
Name : omcUnixRootPartition
omcUnixRootPartitionCum . . . . . . Total partition filling rate
omcUnixRootPartitionEch . . . . . . . Number of samples
root partition used, calculated at the end of the observation period,
expressed in %
ll
Average filling rate of “/tmp” partition
Name : omcUnixTmpPartition
omcUnixTmpPartitionCum . . . . . . Total partition filling rate
omcUnixTmpPartitionEch . . . . . . . Number of samples
“/tmp” partition used, calculated at the end of the observation period,
expressed in %

ll
Average filling rate of “/OMC/obs” partition
Name : omcUnixObsPartition
omcUnixObsPartitionCum . . . . . . . Total partition filling rate
omcUnixObsPartitionEch . . . . . . . Number of samples
“/OMC/obs” partition used, calculated at the end of the observation
ll
Average filling rate of “/OMC/mail” partition
Name : omcUnixMailPartition
omcUnixMailPartitionCum . . . . . . Total partition filling rate
omcUnixMailPartitionEch . . . . . . . Number of samples
“/OMC/mail” partition used, calculated at the end of the observation
ll
Average filling rate of “/OMC/base” partition
Name : omcUnixBasePartition
omcUnixBasePartitionCum . . . . . . Total partition filling rate
omcUnixBasePartitionEch . . . . . . . Number of samples
“/OMC/base” partition used, calculated at the end of the observation

411--9001--125
ll
Average filling rate of “/OMC/data” partition
Name : omcUnixDataPartition
omcUnixDataPartitionCum . . . . . . Total partition filling rate
omcUnixDataPartitionEch . . . . . . . Number of samples
“/OMC/data” partition used, calculated at the end of the observation

5.9 Raw permanent PCUSN counters (from 15001 to 15195)

l
15001/0 Number of bytes received by all the BVCs associated to this PCM
link in an Element (SPM card)
Name Q3 : octetsDn
Value range : [0 to 4294967295]
Object : pcm
Function : Cumulative size (in bytes) of all the BSSGP PDU received on all the
BVCs of a SPM card (including the BVCI0). The size does not include
the FR and NS header.
Event : Receiving of a DL BSSGP PDU, by any BVC, from the SGSN
Source : recorded by the PCU
Note : V12.4b and c counter
l
15001/1 Number of bytes sent by all the BVCs associated to this PCM link
in an Element (SPM card)
Name Q3 : octetsUp
Value range : [0 to 4294967295]
Object : pcmLink
Function : Cumulative size (in bytes) of all the BSSGP PDU sent on all the BVCs
of a SPM card (including the BVCI0). The size does not include the
FR and NS header.
Event : Sending of an UL BSSGP PDU, in any BVC, to the SGSN

411--9001--125
l
15004/0 Number of UNIT--DATA PDUs received downlink by the BVC
Name Q3 : pduDataDn
Value range : [0 to 4294967295]
Object : bts
Function : Number of BSSGP DL--UNITDATA PDU received by the BVC
(SGSN-->PCU).
Event : Receiving of a DL--UNITDATA PDU
l
15004/1 Number of UNIT--DATA PDUs sent uplink by the BVC
Name Q3 : pduDataUp
Value range : [0 to 4294967295]
Object : bts
Function : Number of BSSGP UL--UNITDATA PDU sent by the BVC
(PCU-->SGSN).
Event : Sending of a UL--UNITDATA PDU
l
15005/0 Number of bytes received by the BVC in DL--UNIT--DATA PDUs
Name Q3 : octetsDataDn
Value range : [0 to 4294967295]
Object : bts
Function : Cumulative size (in bytes) of all the LLC PDU in the BSSGP
DL--UNITDATA PDU received by the BVC (SGSN-->PCU).
Event : Receiving of a DL--UNITDATA PDU
DFD “PCUSN: Flow Control”
DFD “PCUSN: LLC Discarded”

l
15005/1 Number of bytes sent by the BVC in the UL--UNIT--DATA PDUs
Name Q3 : octetsDataUp
Value range : [0 to 4294967295]
Object : bts
Function : Cumulative size (in bytes) of all the BSSGP UL--UNITDATA PDU
sent by the BVC (PCU-->SGSN). The size does not include the FR,
NS, and BSSGP header sizes.
Event : Sending of a UL--UNITDATA PDU
l
15007/0 Number of times octets discarded because the number of received
PDUs exceeds the bucket size
Name Q3 : octetDiscarded
Value range : 0 to 65535
Object : bts
Function : Number of octets discarded, because the number of received PDUs
exceeds the bucket size
Event : This counter is incremented after the deletion of a PDU at the PCU
level
Feature : GPRS
Note : V14 counter
l
15007/1 Cumulative size and time of all the GPRS RLC data blocks sent for
the first time on a pipe
Name Q3 : pcuDlThroughputCum
Function : Cumulated size in bytes of all the GPRS RLC data blocks sent for the
first time (i.e. fresh block) on a pipe.
For cumulative time:
T0 = Time of the first block sent in downlink for that mobile
T1 = Time of the last FRESH or NACKED block
T2 = Time of the PDAN which acknowledge all the downlink blocks
(or PCA in unacknowledged mode). Note that if the PDAN is never
received, T1 corresponds to the release of the DL TBF (in that case the
PCU computes T1 - T0 + 1).

411--9001--125
Event : The event for the cumulative size function is a GPRS RLC data block
is sent for the first time (i.e. fresh block) on a pipe by a GPRS DL TBF.
For the cumulative time function, T2 which increments the counter
with the result of T1--T0+1=T2--T0--(RTD + RRBP) +1
Name Q3 : pcuD1ThroughputNbs
Function : Cumulated time in multiple of 20 ms where the MS is in GPRS DL
data transfer.
T0 = Time of the first FRESH block sent to the mobile
T1 = Time of the last FRESH or NACK block sent to the mobile
Each time the last temporary FRESH or NACK block is sent, the PCU
stores the time T1, when the last PDAN (which acknowledged all the
DL blocks or PCA in unacknowledged block) is received the PCU
increments the counter with T1--T0+1 (by using the last T1 value
stored in memory).
Event : A GPRS RLC data block is sent for the first time (i.e. fresh block) on a
pipe by a GPRS DL TBF.
Name Q3 : AvgDlThroughput
Function : To allow the computation of the AvgDlThroughput counter, the
PCUOAM will receive 2 PCU counters from the PCUSN, { Bvc,
maxSizeDataDn } and { Bvc, maxSizeDataUp } and will transform
them to pcuDlThroughputCum (15007/1 CUM CELL) and
pcuDlThroughputNbs (15007/1 NBS CELL).
The current transformation { Bvc, bvcUnBlockRequests } =>
AvgDlThroughput (15007/1 AVG CELL), performed by the
PCUOAM, will have to be removed. The SDO will create itself
AvgDlThroughput (15007/1 AVG CELL).
Event : A GPRS RLC data block is sent for the first time (i.e. fresh block) on a
pipe by a GPRS DL TBF.
Note : There are three counters with an irregular sampling:
AvgDlThroughput (15007/1 AVG CELL), dyAgprsAvgNbTimeslots
(15075/1 AVG CELL), dyAgprsAvgLoadCriterion (15076/0 AVG
CELL). After modification, these counters will have the same SDO
names; there is no interface rupture.
Object : bts
Unit : bytes

Feature : GPRS TBF establishment improvement - one phase access (15015)

Note : V15.0
Note : When only one block is sent (i.e. T1=T0) the counter is incremented
by 1.
Note : As an implementation choice, T1 can be used as the trigger instead of
T2.
RTD = 9 blocks in synchronous TRAU and 5 blocks in asynchronous
TRAU.
RRBP is equal to 3 blocks.
Object : bts
Function : Counter performs two functions: cumulative size in bytes and
cumulative time in multiples of 20 ms where the MS is in GPRS DL
data transfer. For cumulative time:
T2 = Time of the PDAN which acknowledge all the downlink blocks
(or PCA in unacknowledged mode). Note that if the PDAN is never
received, T1 corresponds to the release of the DL TBF (in that case the
PCU computes T1--T0).
Event : The event for the cumulative size function is a GPRS RLC data block
is sent for the first time (i.e. fresh block) on a pipe by a GPRS DL TBF.
For the cumulative time function, T2 which increments the counter
with the result of T1--T0+1=T2--T0--(RTD + RRBP) +1
Unit : bytes
Note : V15.0
Note : When only one block is sent (i.e. T1=T0) the counter is incremented
by 1.
Note : As an implementation choice, T1 can be used as the trigger instead of
T2.
RTD = 9 blocks in synchronous TRAU and 5 blocks in asynchronous
TRAU.
RRBP is equal to 3 blocks.

411--9001--125
l
15008/0 Maximum value of Downlink radio throughput calculated by the
flow control algorithm. (No longer relevant at the PCU level; it is
always set to 0.)
Name Q3 : MaxDlThroughput
Object : bts
Function : This counter is not relevant at the PCU level anymore; it is always set
to 0.
Event : This counter is incremented after the emission of 3 Kbytes on the
radio
Unit : 100 Bits per second
Feature : GPRS
Note : The lie factor is a feature that is used to exaggerate the leak rate when
the bucket is near starvation, and to minimize the leak rate when the
bucket is almost full. This counter calculates the true maximum value
of the downlink radio throughput without using the lie factor
l
15010/0 Number of FLOW--CONTROL--BVC PDUs sent by the BVC
Name Q3 : bvcFlowControlRequests
Value range : [0 to 65535]
Object : bts
Function : Number of BSSGP FLOW--CONTROL--BVC PDU sent by the BVC
(PCU-->SGSN).
Event : Sending of a FLOW--CONTROL--BVC PDU

l
15010/1 Number of FLOW--CONTROL--MS PDUs sent by the BVC
Name Q3 : msFlowControlRequests
Object : bts
Function : Number of BSSGP FLOW--CONTROL--MS PDU sent by the BVC
(PCU-->SGSN).
Event : Sending of a FLOW--CONTROL--MS PDU
l
15012/0 Number of LLC--DISCARDED PDUs sent by the BVC
Name Q3 : llcDiscardedPdu
Object : bts
Function : Number of BSSGP LLC--DISCARDED PDU sent for the BVC
(PCU-->SGSN).
Event : Sending of a LLC--DISCARDED PDU
l
15012/1 Cumulative amount of the all the bytes discarded in the BVC
Name Q3 : llcDiscardedOctets
Value range : [0 to 4294967295]
Object : bts
Function : Cumulative amount of the all the bytes discarded in the BVC (i.e.
number of bytes discarded from the bucket if not empty)
Event : This counter is triggered by the:
sending of a BSSGP LLC DISCARDED PDU to the SGSN
sending of a BSSGP RADIO STATUS to the SGSN
reception of a BSSGP FLUSH--LL from the SGSN

411--9001--125

DFD “PCUSN: LLC Discarded”
Note : The number of octets is related to the LLC PDU received in the DL
UNITDATA PDU.
l
15014/0 Flush--LL PDUs relative to the BVC sent from the SGSN to the
PCU
Name Q3 : msFlushLLRequest
Object : bts
Function : Number of BSSGP FLUSH--LL PDU received by the BVCI0 for all
MS in the cell associated to the BVC (the BVC is indicated in the
message by the field BVCI (old)).
Event : Receiving of a FLUSH--LL PDU
l
15023/0 Total Number of CS Paging messages sent by the PCU to the BSC
on this LAPD link
Name Q3 : CsPagingOnCcch
Object : pcmCircuit
Function : Total Number of CS Paging messages sent by the PCU to the BSC on
this LAPD link
Event : This counter is incremented after the sending of a CS Paging message
to the BSC on the LAPD link
Feature : GPRS
Note : V14 counter
Reserved for future use

l
15023/1 Total Number of PS Paging messages sent by the PCU to the BTS on
this LAPD link
Name : PsPagingOnCCCH
Object : pcmCircuit
Function : Total Number of PS Paging messages sent by the PCU to the BTS on
this LAPD link
Event : This counter is incremented after the sending of a PS Paging message
to the BTS on the LAPD link
Feature : GPRS
Note : V14 counter
l
15024/0 Total Number of CS Paging messages sent by the PCU to the MS on
PACCH
Name Q3 : CsPagingOnPACCH
Object : pcmCircuit
Function : Total Number of CS Paging messages sent by the PCU to the MS on
PACCH (on this SPM card)
Event : This counter is incremented after the sending of a CS Paging message
to the MS on PACCH
Feature : GPRS
Note : V14 counter
l
15028/1 Cumulative number of uplink and/or downlink radio resource
assignments for a mobile whose multislot class requires 1 uplink
timeslot
Name Q3 : upMultiSlotRequest1
Value range : [0 to 4294967295]
Object : bts
Function : Cumulative number of uplink and/or downlink radio resource
assignments on PACCH for a mobile whose multislot class requires 1
uplink timeslot

411--9001--125
Event : End of the packet transfer for the MS, if the MSC is known.
Precise
The counter is not incremented if the multislot class is unknown.
The counter is incremented in case of normal or abnormal
termination.
Feature : GPRS
Note : V12.4d counter
Note : I/F PCU--PCUOAM: The counter upMultiSlotRequest is of type
vector using Index from 1 to 4.
Note : An EDGE--capable MS can have a different MCS in EDGE and in
GPRS. If the EDGE MS is allocated in EDGE mode, the EDGE MCS
will be considered for this counter. If the EDGE MS is allocated in
GPRS mode, the GPRS MCS will be considered for this counter.
assignments on PACCH for a mobile whose multislot class requires
up to 2 uplink timeslots. If more than 4 timeslots are allocated in
uplink, the counter upMultislotRequest4 is incremented.
Index 0 is formatted in the Passport spooled statistic record but its
corresponding value must not be interpreted.
Index 2 corresponds to upMultiSlotRequests (2)
Precise
termination.

Feature : GPRS

Note : The counter is not incremented until the multislot class is known
(during uplink one phase access the MSC is unknown).

l
assignments on PACCH for a mobile whose multislot class
requires up to 3 uplink timeslots
Value range : [0 to 4294967295]
Object : bts

up to 3 uplink timeslots. If more than 4 timeslots are allocated in
uplink, the counter upMultislotRequest4 is incremented.

Precise
termination.

411--9001--125
Feature : GPRS

Note : The counter is not incremented until the multislot class is known
(during uplink one phase access the MSC is unknown).

l
requires up to 4 and more than 4 uplink timeslots
Value range : [0 to 4294967295]
Object : bts

up to 4 and more than 4 uplink timeslots. If more than 4 timeslots are
allocated in uplink, the counter upMultislotRequest4 is incremented.

Precise
termination.

Feature : GPRS
Note : If more than 4 timeslots are allocated in uplink, the counter
upMultislotRequest4 is incremented.
Note : A EDGE capable MS can have a different MCS in EDGE and in
l
15029/1 Cumulative number of gold users’ uplink allocations with a
satisfaction rate equal or better than 90%
Name Q3 : upTbfGoldSatisfactMore90pCent
Object : bts
Function : Cumulative number of gold users uplink allocations with a
satisfaction rate equal or better than 90 %. Refer to Section 4.7
Event : Modification of an allocation belonging to a gold user. Refer to
Section 4.7
Feature : GPRS
Note : V14 counter
l
satisfaction rate equal or more than 50% and strictly less than
90%
Name Q3 : upTbfGoldSatisfactBet5090pCent
Object : bts
Function : Cumulative number of gold users’ uplink allocations with a
satisfaction rate equal or more than 50% and strictly less than 90%
Refer to Section 4.7
Section 4.7

411--9001--125
Feature : GPRS
Note : V14 counter
l
satisfaction rate strictly less than 50%
Name Q3 : upTbfGoldSatisfactLess50pCent
Object : bts
Function : Cumulative number of gold users’ uplink allocations with a
satisfaction rate strictly less than 50%. Refer to Section 4.7
Section 4.7
Feature : GPRS
Note : V14 counter
l
15029/4 Cumulative number of gold users’ uplink allocations rejected due
to the admittance control
Name Q3 : upTbfGoldRejectedForMinTput
Object : bts
Function : Cumulative number of gold users’ uplink allocations rejected due to
the admittance control
Event : This counter is incremented after the rejection of a new allocation to a
gold user due to admittance control
Feature : GPRS
Note : V14 counter

l
assignments for a mobile whose multislot class requires 1
downlink timeslot
Name Q3 : dnMultiSlotRequest1
Value range : [0 to 4294967295]
Object : bts
up to 1 downlink timeslot.
If more than 4 timeslots are allocated in downlink, the counter
dnMultiSlotRequest4 is incremented.
Note : Index 0 is formatted in the Passport spooled statistic record but its
Index 2 corresponds to dnMultiSlotRequests2
Precise
termination.
Feature : GPRS
Note : On I/F PCU--PCUOAM, the counter dnMultiSlotRequests is of type
Note : EGPRS: An EDGE capable MS can have a different MCS in EDGE
and in GPRS. If the EDGE MS is allocated in EDGE mode, the EDGE
MCS will be considered for this counter. If the EDGE MS is allocated
in GPRS mode, the GPRS MCS will be considered for this counter.

411--9001--125
l
requires up to 2 downlink timeslots
Value range : [0 to 4294967295]
Object : bts
up to 2 downlink timeslot.
If more than 4 timeslots are allocated in downlink, the counter
dnMultiSlotRequest4 is incremented.
Precise
termination.
Feature : GPRS

l
requires up to 3 downlink timeslots
Value range : [0 to 4294967295]
Object : bts
up to 3 downlink timeslots
Precise
termination.
Feature : GPRS
Note : Note on EGPRS: An EDGE capable MS can have a different MCS in
EDGE and in GPRS. If the EDGE MS is allocated in EDGE mode, the
EDGE MCS will be considered for this counter. If the EDGE MS is
allocated in GPRS mode, the GPRS MCS will be considered for this
counter.

411--9001--125
l
requires up to 4 and more than 4 downlink timeslots
Value range : [0 to 4294967295]
Object : bts
up to 4 and more than 4 downlink timeslots
Precise
termination.
Feature : GPRS
l
15031/1 First Downlink Unit Data Frame
Name Q3 : FirstDlUnitDataFrame
Value range : [0 to 4294967295]
Object : bts
Function : Cumulative number of pre--established downlink TBF without
reception of DL--UNITDATA for this TBF.

Event : Release of a pre--established downlink TBF without reception of a

DL--UNITATA for this TBF.
Feature : GPRS
Data flows : Refer to Chapter 2:
DFD “PCUSN: DL TBF Establishment: MS in Standby State”
l
15031/2 Number of downlink allocation failures
Name Q3 : dlTBFAllocFailure
Value range : [0 to 4294967295]
Object : bts
Function : Cumulative number of downlink TBF establishment failures (half
and full duplex transfer), due to lack of radio resources.
Event : Reception of DL--UNITDATA(with a new TLLI), if the number of
MS in transfer is greater or equal to NB_MAX (SPM capacity
limitation set by Nortel Controlled Feature). The PCU tries to
establish the downlink TBF every 5 sec. up to 3 times, so with the
same DL--UNITDATA, the PCU may increment the counter up to 4
times.
Feature : GPRS
Note : This counter is also incremented in case of failure of
DL--Preestablishment.
l
15031/3 Number of downlink radio link failures
Name Q3 : dlTBFRadioFailure
Value range : [0 to 4294967295]
Object : bts
Function : Cumulative number of downlink TBF establishment failures (half
and full duplex), due to radio link failure

411--9001--125
Event : This counter is incremented when an acknowledgement from the MS

is not received for:
Packet Polling Request (after 6 transmissions from the PCU)
First Packet Downlink Assignment (after 6 transmissions from the
PCU)
Packet Timeslot Reconfigure for the establishment of a downlink
TBF (after 6 transmissions from the PCU)
Class : GPRS
Feature : GPRS
Note : I/F PCU--PCUOAM: The counter dnMultiSlotAllocations is of type
Index 3 corresponds to this counter.
l
15031/4 Cumulative number of silver users’ uplink allocations with a
Name Q3 : upTbfSilverSatisfactMore90pCent
Object : bts
Function : Cumulative number of silver users’ uplink allocations with a
satisfaction rate equal or better than 90%. Refer to Section 4.7
Section 4.7
Feature : GPRS
Note : V14 counter
l
15032/0 Total number of full duplex temporary block flow (TBF)
established
Name Q3 : fullDuplexTbfEstablishment
Value range : [0 to 4294967295]
Object : bts
Function : Cumulative number of attempts to establish a full duplex transfer in
the cell (UL TBF establishment on DL TBF and vice versa).The full
duplex establishment may fail but the counter is incremented anyway.

Event : Sending of a message for the establishment of a full duplex transfer

(the message can be a Packet Timeslot Reconfiguration, a Packet
Uplink Assignment or a Packet Downlink Assignment)
l
15032/3 Number of second phase uplink allocation failures
Name Q3 : ulsecondphaseallocFailure
Value range : [0 to 4294967295]
Object : bts
Function : Cumulative number of rejected uplink establishment requests on
PACCH (half and full duplex), due to lack of radio resources
Event : This counter is incremented after the reception of a Packet Resource
Request or Packet Downlink Ack/Nack with Uplink Request, if the
PCU cannot allocate enough resources to this mobile. Reception of a
first Packet Resource Request (with a new TLLI), if the number of MS
in transfer is greater or equal to NB_MAX_MS (SPM capacity
limitation set by Nortel Controlled Feature).
Feature : GPRS

411--9001--125
l
15033/0 Number of uplink TBFs released
Name Q3 : upTbfReleases
Value range : [0 to 4294967295]
Object : bts
Function : Cumulative number of UL TBF released in the cell (related to half
duplex or full duplex transfers). This counter counts the normal and
abnormal releases due to loss of communication, OAM event, TS
sharing event.
Event : Release of an UL TBF (related to half duplex or full duplex transfer
and due to normal or abnormal release). No reception of the first PRR.
Resources requested for establishing the uplink TBF rejected by
allocator (because no radio resources available, admission control).
Reception of a first Packet Resource Request (with a new TLLI), if the
number of MS in transfer is greater or equal to the value specified by
the SPM capacity limitation. One phase access contention resolution
fails.

l
15033/1 Number of downlink TBFs released
Name Q3 : dnTbfReleases
Value range : [0 to 4294967295]
Object : bts
Function : Cumulative number of DL TBF released in the cell (related to half
duplex or full duplex transfers). This counter counts the normal and
abnormal releases due to loss of communication, OAM event, TS
sharing event.
Event : Release of a UL TBF (related to half duplex or full duplex transfer and
due to normal or abnormal release). Resources requested for
establishing the downlink TBF rejected by allocator (because no radio
resources available, Admission Control) Reception of
DL--UNITDATA (with a new TLLI), if the number of MS in transfer
is greater or equal to NB_MAXMS (SPM capacity limitation set by
Nortel Controlled feature). The PCU tries to establish the downlink
TBF every 5 sec. up to 3 times, so with the same DL--UNITDATA the
PCU may increment the counter up to 4 times.
l
15034/0 Number of Packet Downlink Ack/Nack with Uplink Request
Name Q3 : PDANWithUlReq
cumulativeTimeUpTbf
Value range : [0 to 4294967295]
Object : bts
Function : Cumulative number of Packet Downlink Ack/Nack messages, with
the Channel Request Description included
Event : This counter is incremented when a Packet Downlink Ack/Nack
message is received, with the Channel Request Description included
Feature : GPRS
DFD “PCUSN: Abnormal UL TBF Release (Full Duplex):
UP_NASSIGNMAX”
DFD “PCUSN: UL TBF Establishment during DL transfer”

411--9001--125
l
Name Q3 : upTbfSilverSatisfactBet5090pCent
Object : bts
Function : Cumulative number of silver users uplink allocations with a
satisfaction rate equal or more than 50 and strictly less than 90 %.
Refer to section 4.7
Event : Pipe modification. Refer to section 4.7
Feature : GPRS
Note : V14 counter
l
15036/0 Number of second phase uplink radio link failures
Name Q3 : ulsecondPhaseRadioFailure
Value range : [0 to 4294967295]
Object : bts
Function : Cumulative number of abnormal releases during second phase uplink
TBF establishment (half and full duplex transfer)
Event : This counter is incremented in the following cases:
Non--reception of 6 consecutive non--acknowledgements of the
first Packet Uplink Assignment.
Non--reception of 6 consecutive non--acknowledgments of the
Packet Timeslot Reconfigure sent for the establishment of an
uplink TBF on downlink TBF.
Feature : GPRS
l
15038/0 Total number of RLC data blocks sent by the PCU in astalled
window condidtion
Name Q3 : localBusy
Value range : [0 to 4294967295]
Object : transceiver
Function : Cumulative number RLC data blocks sent by the PCU in a stalled
window condition during a downlink transfer on this TDMA.

Event : This counter is incremented on the sending of an RLC data block

(PENDING_ACK) when the transmit window is stalled.
Note : Only the PENDING_ACK blocks are counted.
l
15039/0 Cumulative value “C” received by the PCU in the message Packet
Downlink Ack/Nack
Name Q3 : cumulativeDnRxLev
configuredTimeslots
Function : Cumulative value “C” received by the PCU in the message Packet
Downlink Ack/Nack
Event : This counter is incremented after the reception of a Packet Downlink
Ack/Nack by a TBF on this TDMA containing the Channel Quality
Report set by the mobile
Feature : GPRS
Note : V14 counter
l
15041/0 Number of user uplink data blocks
Name Q3 : upUserdatablocks
cumulativeUpActiveTimeslots
Value range : [0 to 4294967295]
Function : Cumulative number of blocks received for the first time at the PCUSN
level
Event : This counter is incremented after an RLC data block is received in the
Receive window, which has not been already received by the PCU.
Feature : GPRS

411--9001--125
l
15043/0 Number of retransmitted data blocks by the PCUSN due to
negative acknowledgement
Name Q3 : RequestedRetransmittedDataBlocksDN
Value range : [0 to 4294967295]
Function : Cumulative number of downlink data blocks retransmitted by the
PCUSN due to negative acknowledgement from the mobile. All
blocks resent due to the Keep Alive feature and Preventive
Retransmission are not counted in this case.
Event : Retransmission of data blocks in NACKed state.
Feature : GPRS
Note : The cdl name of the corresponding operational counter is
dnActiveTimeslots.
l
15045/0 Total number of LLC packets reassembled and transmitted to the
LLC Relay
Name Q3 : llcPacketsUp
Value range : [0 to 4294967295]
Function : Cumulative number of UL LLC frames reassembled by the PCU on
this TDMA.
Event : Reassembly of LLC frames
l
15045/1 Total number of LLC packets segmented into RLC data blocks
Name Q3 : llcPacketsDn
Value range : [0 to 4294967295]
Function : Cumulative number of LLC DL frames segmented by the PCU in
RLC data blocks on this TDMA.

Event : Segmentation of LLC frames

l
15046/0 Total number of uplink RLC data blocks received
Name Q3 : dataBlocksUp
Value range : [0 to 4294967295]
Function : Cumulative number of RLC data blocks received by the PCU on this
TDMA
Event : This counter is incremented when a TBF is in progress and on
reception of a TRAU frame (without BFI) containing and RLC/MAC
block including:
a valid RLC data block in sequence received for the first time
a valid RLC data block in sequence already received
a valid RLC data block out of sequence
an invalid RLC data block

411--9001--125

DFD “PCUSN: Normal UL TBF Release”
DFD “PCUSN: Abnormal UL TBF Release: lossOfComNN0002”
DFD “PCUSN: Abnormal UL TBF Release (FULL Duplex):
lossOfComNN0002”
DFD “PCUSN: Abnormal UL TBF Release: N3101”
N3101”
N3103”
DFD “PCUSN: DL TBF Establishment: MS in StandBy State”
DFD “PCUSN: Abnormal DL TBF Release (FULL Duplex):
lossOfComNN0002”
N3105”
DN_NASSIGNMAX”
DFD “PCUSN: Abnormal DL TBF Release (FULL Duplex): No
Final PDAN”
DFD “PCUSN: Preemption”
DFD “PCUSN: Cell Update: Packet Transfer”
Note : The term valid/invalid is linked to the protocol integrity. This means
that the block has been correctly received on the radio by the BTS, and
after decoding by the PCU the block is declared valid/invalid
according to the header contents.
l
15046/1 Total number of downlink RLC data blocks transmitted
Name Q3 : dataBlocksDn
Value range : [0 to 4294967295]
Function : Cumulative number of RLC data blocks sent by the PCU on this
TDMA.
Event : Sending of a DL RLC data block

l
15047/0 Total number of uplink RLC control blocks received
Name Q3 : controlBlocksUp
Value range : [0 to 4294967295]
Function : Cumulative number of RLC/MAC control blocks received in uplink
by the PCU on this TDMA.
reception of a TRAU frame (without BFI) containing:
an RLC/MAC block including a valid RLC/MAC control block
an RLC/MAC block including an invalid RLC/MAC control block
a valid Stealing Frame (PCA 4--burst access mode)
an invalid Stealing Frame (PCA 4--burst access mode)
DFD “PCUSN: UL TBF Establishment”
DFD “PCUSN: Normal UL TBF Release”
DFD “PCUSN: Abnormal UL TBF Release:
UP_NASSIGNMAX”
UP_NASSIGNMAX”
DFD “PCUSN: DL TBF Establisment: MS in StandBy State”
DFD “PCUSN: DL TBF Establisment: MS in Ready State”
DFD “PCUSN: Normal DL TBF Release”
DFD “PCUSN: Abnormal DL TBF Release: lossOfComNN0002”
lossOfComNN0002”
DFD “PCUSN: Abnormal DL TBF Release: N3105”
N3105”
DFD “PCUSN: Abnormal DL TBF Release:
DN_NASSIGNMAX”
DFD “PCUSN: Cell Update: Packet Transfer”
after decoding by the PCU the block is declared valid/invalid
according to the header contents

411--9001--125
l
15047/1 Total number of downlink RLC control blocks transmitted
Name Q3 : controlBlocksDn
Value range : [0 to 4294967295]
Function : Cumulative number of RLC/MAC control block sent by the PCU on
this TDMA.
Event : Sending of a DL RLC control block by a GPRS UL or DL TBF on this
TDMA.
Note : This counter does not count the Downlink Dummy Control blocks
sent by the PCU.
l
15048/0 Total number of uplink invalid radio blocks received
Name Q3 : invalidBlocksUp
Value range : [0 to 4294967295]
Function : Cumulative number of RLC/MAC blocks received with BFI (Bad
Frame Indicator set by the BTS when no correct block has been
decoded on the radio) by the PCU on this TDMA
reception of a TRAU frame with BFI
l
15048/1 Total number of invalid RLC/MAC blocks triggering a protocol
error
Name Q3 : invalidProtocolErrorBlocksUp
Value range : [0 to 4294967295]
Function : Cumulative number of invalid RLC/MAC blocks triggering a
protocol error, received by the PCU on this TDMA


N3101”
UP_NASSIGNMAX”
Note : During the one phase access contention resolution, the counter will be
incremented upon receipt of UL RLC data block without TLLI.
after decoding by the PCU, the block is declared valid/invalid
Note : The counter is not incremented if the RLC/MAC block is received
after the release of the uplink TBF
l
15048/2 Total number of uplink data blocks received with Block Sequence
Number ouside the received window
Name Q3 : outOfSequenceBlocksUp
Value range : [0 to 4294967295]
Function : Cumulative number of UL RLC data blocks received of out sequence
by the PCU on this TDMA.
Event : Receipt of an RLC/MAC block received out of sequence
after decoding by the PCU, the block is declared valid/invalid
l
15049/0 Total number of PACKET UPLINK ACK/NACK messages
Name Q3 : packetAckNackUp
Value range : [0 to 4294967295]
Function : Cumulative number of PACKET UPLINK ACK/NACK messages

411--9001--125
Event : Sending of a PACKET UPLINK ACK/NACK message

l
15049/1 Total number of PACKET DOWNLINK ACK/NACK messages
Name Q3 : packetAckNackDn
Value range : [0 to 4294967295]
Function : Cumulative number of PACKET DOWNLINK ACK/NACK
messages received by the PCU on this TDMA.
Ack/Nack by a GPRS DL TBF on this TDMA.
Note : The counter is not incremented if the Packet Downlink Ack/Nack is
received after the release of the downlink TBF (specially up to RTD
after the release of the downlink TBF)
l
15050/0 Total number of RLC/MAC block retransmission requests
Name Q3 : totalRetransmissionRequested
Value range : [0 to 4294967295]
Function : Cumulative number of UL RLC data blocks badly received by the
PCU on this TDMA and where it requested a retransmission.
Event : Sending of a Packet Uplink Ack/Nack requesting for the
retransmission of UL RCL data blocks

l
15051/0 Cumulative uplink rxQual value
Name Q3 : cumulativeUpRxQual
Value range : [0 to 4294967295]
Function : Cumulative value “upRxQual” received by the PCU in each valid
RLC/MAC block on this TDMA. The PCU uses the “assumed value”
X 100 (refer to 3GPP 05.08)
Event : Receipt of a valid TRAU frame by a GPRS UL TBF on this TDMA
(valid means without BFI). Note that the counter is not incremented
upon receipt of a stealing frame.
The average is calculated by dividing this counter value by the
nbSamples value.
The counter is not incremented if the RLC/MAC block is received
after the release of the uplink TBF (specially up to RTD after an
abnormal release).
l
15051/1 Cumulative value “RxQual” in Channel Quality Report received
by the PCU in the message Packet Downlink Ack/Nack
Name Q3 : cumulativeDnRxQual
Function : Cumulative value “RxQual” in Channel Quality Report received by
the PCU in the message Packet Downlink Ack/Nack
Ack/Nack by a TBF on this TDMA containing the Channel Quality
Feature : GPRS
Note : V14 counter

411--9001--125
l
15052/0 Cumulative value “upRxLev” received by the PCU in each valid
RLC/MAC block on this TDMA
Name Q3 : cumulativeUpRxLev
Function : Cumulative value “upRxLev” received by the PCU in each valid
RLC/MAC block on this TDMA
Event : Receipt of a valid TRAU frame by a GPRS UL TBF on this TDMA
(valid means without BFI).
Event : This counter is incremented after the reception of a valid RLC/MAC
block by a TBF on this TDMA (valid means without BFI)
Feature : GPRS
Note : V14 counter
Note : The counter is not incremented if the RLC/MAC block is received
abnormal release).
Note : The counter is not incremented upon receipt of a stealing frame.
l
15053/0 Number of sampling for uplink rxQual and uplink rxLev
cumulative values
Name Q3 : nbSamplesUpQuality
Object : tranceiver
Function : Cumulative number of valid RLC/MAC blocks received by the PCU
on this TDMA
Event : Receipt of a valid TRAU frame (and different from a stealing frame)
by a TBF on this TDMA (valid means without BFI)
Feature : GPRS
Note : V14 counter
The counter is not incremented if the RLC/MAC block is received
abnormal release)

l
15053/1 Cumulative number of Packet Downlink Ack/Nack messages
received by the PCU on this TDMA, containing the Channel
Quality Report
Name Q3 : nbSamplesDnQuality
Function : Cumulative number of Packet Downlink Ack/Nack messages
received by the PCU on this TDMA, containing the Channel Quality
Report
Ack/Nack by a TBF on this TDMA, containing the Channel Quality
Feature : GPRS
Note : V14 counter
l
15054/0 Total number of data blocks retransmitted downlink
Name Q3 : retransmittedDataBlocksDn
Value range : [0 to 4294967295]
Function : Cumulative number of RLC data blocks retransmitted by the PCU on
this TDMA. This number includes all the transmission causes (round
trip delay, preventive retransmission, etc.)
Event : Retransmission of a DL RLC data block
l
15055/0 Total number of uplink TBFs terminated normally
Name Q3 : tbfNormalReleaseUp
Value range : [0 to 4294967295]
Function : Cumulative number of normal releases of UL TBFs (related to half
duplex or full duplex transfer).

411--9001--125
Event : Normal release of a UL TBF

l
15055/1 Total number of downlink TBFs terminated normally
Name Q3 : tbfNormalReleaseDn
Value range : [0 to 4294967295]
Function : Cumulative number of normal releases of DL TBFs (related to half
duplex or full duplex transfer).
Event : Normal release of a DL TBF
Note : This counter is not relevant in case of CCCH management at BTS.
l
15056/0 Number of TBF abnormal releases due to non receipt of Packet
Resource Request
Name Q3 : noPacketResourceReq
Value range : [0 to 4294967295]
Function : Cumulative number of time the PCU has allocated a block for a PRR
(in an IMMEDIATE ASSIGN UL message) and has not received the
PRR from the mobile on this TDMA.
Event : Non receipt of a PRR in the block allocated for this purpose in the
immediate assignment

l
15056/1 Total number of PACKET RESOURCE REQUEST messages
received by the PCU from the MS in the second phase of the
2--phase access uplink TBF establishment
Name Q3 : packetResourceRequest
Value range : [0 to 4294967295]
Object : ccch
Function : Cumulative number of PACKET RESOURCE REQUEST messages
received by the PCU in this cell for the second phase of an uplink
establishment.
Event : Receipt of a PRR related to the second phase of an UL TBF
establishment
l
15057/0 Number of TBF abnormal releases due to V(Q) and V(A) non
progression
Name Q3 : lossOfComNN002Max
Value range : [0 to 4294967295]
Function : Number of abnormal releases due to non progression of V(Q) in
uplink and V(A) in downlink. This means the number of abnormal
releases with a mobile in uplink TBF or downlink TBF because the
received or transmitted window doesn’t progression.
Event : Trigger
For uplink TBF, NN002 consecutive Packet Uplink Ack/Nack is
sent to the mobile without evolution of V(Q).
For downlink TBF, NN002 consecutive Packet Downlink
Ack/Nack (or EGPRS Packet Downlink Ack/Nack) is received
from the mobile without evolution of V(A).

411--9001--125

Note : Note that this counter is not incremented when the PCU performs
preemptive retransmission while all the blocks have been
acknowledged (in that case the PCU may receive several PDAN
without evolution of V(A)).
In half duplex transfer (UL or DL): when this counter is
incremented the counter lossOfComT3169 (UL) or
lossOfComT3195 (DL) is not incremented.
In full duplex transfer: if the UL TBF is released due to a cause
lossOfComNN002Max then the counters lossOfComNN002Max
and lossOfComT3195 (DL) are incremented, and the counter
lossOfComT3169 is not incremented.
In full duplex transfer: if the DL TBF is released due to a cause
lossOfComNN002Max then the counters lossOfComNN002Max
and lossOfComT3169 (UL) are incremented, and the counter
lossOfComT3195 is not incremented.
l
15057/1 Number of TBF abnormal releases due to timer T3169 expiry
Name Q3 : lossOfComT3169
Value range : [0 to 4294967295]
Function : Number of uplink TBF abnormal releases due to non response from
the mobile during the establishment procedure or packet transfer. In
the case of full duplex transfer, this also counts the uplink TBF
releases consecutive to downlink TBF abnormal release.
Event : Trigger
No valid blocks received in UL from the mobile after N3101
scheduled blocks (means with USF set in downlink)
No Packet Control Ack received from the mobile after N3103
Packet Uplink Ack/Nack sent with FAI=1
No Packet Control Ack received from the mobile after
UP_NASSIGNMAX (value=6) Packet Uplink Assignment
messages (i.e. Packet Uplink Assignment or Packet Timeslot
Reconfigure or Packet Uplink Ack/Nack with assignment)
All the full duplex abnormal releases except loss of com. related to
lossOfComNN002Max cause in uplink


Note : In case of full duplex transfer, this also counts the uplink TBF releases
consecutive to the following downlink TBF abnormal releases:
NN002 consecutive Packet Downlink Ack/Nack (or EGPRS
Packet Downlink Ack/Nack) received from the mobile without
evolution of V(A).
No Packet Downlink Ack/Nack (or EGPRS Packet Downlink
Ack/Nack) received from the mobile after N3105 downlink data
blocks sent with S/P=1.
DL_NASSIGNMAX (value 6) downlink assignment messages
(i.e Packet Downlink Assignment or Packet Timeslot
Reconfigure).
No final Packet Downlink Ack/Nack (or EGPRS Packet Downlink
Ack/Nack) received from the mobile after NN002 data blocks sent
with S/P=1 (or ES/P=1 or ES/P=3 in EDGE) and FBI=1.
This counter is not incremented when a uplink TBF is released due
to a cause lossOfComNN002Max
l
15057/2 Number of TBF abnormal releases due to timer NT0001 expiry
Name Q3 : lossOfComNT0001
Value range : [0 to 4294967295]

Function : Number of uplink TBF abnormal releases due to non response from
the mobile to USF and assignment messages
Event : Trigger
UP_NASSIGNMAX (value=6) uplink assignment messages (i.e.
Packet Uplink Assignment or Packet Timeslot Reconfigure or
Packet Uplink Ack/Nack with assignment)

411--9001--125

N3101”
UP_NASSIGNMAX”
UP_NASSOGNMAX”
Note : V12.4b,c and d counter
This counter is a subset of lossOfComT3169
This counter is incremented when there is no response from the
MS to an uplink assignment message in PCU or FD
l
Value range : [0 to 4294967295]
Function : Number of downlink TBF abnormal releases due to non response
from the mobile during the establishment procedure or packet
transfer. In the case of full duplex transfer, this also counts the
downlink TBF releases consecutive to uplink TBF abnormal release.
Event : Trigger
No Packet Downlink Ack/Nack (or EGPRS Packet Downlink
Ack/Nack) received from the mobile after N3105 downlink data
blocks sent with S/P=1
DL_NASSIGNMAX (value 6) downlink assignment messages
(i.e. Packet Downlink Assignment or Packet Timeslot
Reconfigure)


Note : In the case of full duplex transfer, this also counts the downlink TBF
releases consecutive to uplink TBF abnormal releases.
NN002 consecutive Packet Uplink Ack/Nack sent to the mobile
without evolution of V(Q).
No Packet Control Ack received from the mobile after N3103
Packet Uplink Ack/Nack sent with FAI=1
UP_NASSIGNMAX (value=6) uplink assignment messages (i.e.
Packet Uplink Assignment or Packet Timeslot Reconfigure or
Packet Uplink Ack/Nack with assignment)
This counter is not incremented when a downlink TBF is released
due to a cause lossOfComNN002Max.
l
Value range : [0 to 4294967295]
Function : Number of downlink TBF abnormal releases which occur during the
release of a downlink TBF (while the PCU is waiting for the last
acknowledgement coming from the mobile).
Event : No final Packet Downlink Ack/Nack (or EGPRS Packet Downlink
Ack/Nack) received from the mobile after NN002 data blocks sent
with S/P=1 (or ES/P=1 or ES/P=3 in EDGE) and FBI=1
This counter is a subset of lossOfComT3195

411--9001--125
l
15058/0 Total number of IMMEDIATE ASSIGNMENT messages
generated by the PCU to the MS in the first phase of the 2--phase
access uplink TBF establishment
Name Q3 : upTbfImmediateAssignment
Value range : [0 to 4294967295]
Object : ccch
Function : Cumulative number of IMMEDIATE ASSIGNMENT UPLINK
messages sent by the PCU to establish an UL TBF in this cell. In the
case of CCCH management at the BTS, this counter corresponds to
the cumulative values periodically received from the BTS in the
CCCH information message.
Event : Sending of an IMMEDIATE ASSIGNMENT UPLINK message if
managed by the PCU or receipt of a CCCH information message if
managed by the CCCH at the BTS.
l
15058/1 Total number of UL and DL TBF establishment rejected because
the number of MS in transfer is greater or equal ro
NB_MAX_MS
Name Q3 : upTbfImmAssigRejectNoPdch
Value range : [0 to 4294967295]
Object : ccch
Function : Cumulative number of UL and DL TBF establishment rejected
because the number of MS in transfer is greater than or equal to the
value specified by SPM capacity limitation (set by Nortel Controlled
Feature).
SPM capacity limitation is either defined by a max number of MS
reached or by CPU overload.

Event : Reception of a first Packet Resource Request (with a new TLLI), if the
number of MS in transfer is greater than or equal to the value specified
by SPM capacity limitation
Reception of DL--UNITDATA (with a new TLLI), if the number of
MS in transfer is greater or equal to the value specified by the SPM
capacity limitation (set by Nortel Controlled Feature). The PCU will
re--try to establish the downlink TBF every 5 sec up to 3 times, so with
the same DLUNITDATA the PCU may increment the counter up to 4
times.
Note : V14 counter
The PCU will re--try to establish the downlink TBF every 5 sec up to 3
times, so with the same DL--UNITDATA the PCU may increment the
counter up to 4 times.
l
15058/2 Total number of IMMEDIATE ASSIGNMENT messages sent for
a downlink TBF establishment from the PCU to the MS
Name Q3 : dnTbfImmediateAssignment
Value range : [0 to 4294967295]
Object : ccch
Function : Cumulative number of IMMEDIATE ASSIGNMENT DOWNLINK
messages sent by the PCU to establish a DL TBF.
Event : Sending of an IMMEDIATE ASSIGNMENT DOWNLINK message
l
15058/3 Number of times a downlink bandwidth, between 1 and 2
timeslots, has been allocated for some mobiles in the cell
Name Q3 : dnPipeBetween11and22kbps
Object : ccch
Function : Refer to Paragraph 4.7
Event : Refer to Paragraph 4.7
Feature : GPRS

411--9001--125
l
15058/4 Number of times a downlink bandwidth, between 2 and 3
timeslots, has been allocated for some mobiles in the cell
Name Q3 : dnPipebetween22and33kbps
Object : ccch
Feature : GPRS
l
15059/0 Total number of RACH (Channel Request) messages received in
Name Q3 : channelRequestCcch
Value range : [0 to 4294967295]
Object : ccch
Function : Cumulative number of RACH (Channel Request) received by the
PCU or BTS (in case of CCCH at BTS) in this cell.
In case of CCCH at BTS, this counter corresponds to the cumulative
values periodically received from the BTS in the CCCH information
message (field Number of RACH, for single block and one phase
access.)
Event : Receipt of a Channel Request Message if managed by PCU.
Receipt of a CCCH information message in case of CCCH at BTS.
Note : When the CCCH at BTS and the one phase access features are
activated, the one phase access RACH are forwarded to the PCU by
the BTS and the field (RACH for one phase access) in the CCCH
information is not incremented by the BTS.
Note : When CCCH at BTS and one phase access features are activated,
one phase access RACH are forwarded to the PCU by the BTS,
the field ”RACH for one phase access” in CCCH information is
not incremented by the BTS.

l
15060/0 Number of times a downlink bandwidth, of more than 3 timeslots,
has been allocated for some mobiles in the cell
Name Q3 : dnPipeGreater33kbps
Object : ccch
Feature : GPRS
l
15060/1 Cumulative number of silver users’ uplink allocations rejected due
to the admittance control
Name Q3 : upTbfSilverRejectedForMinTput
Object : CCCH
Function : Cumulative number of silver users’ uplink allocations rejected due to
the admittance control
silver user due to admittance control
Feature : GPRS
l
15061/0 Number of times an uplink bandwidth, of less than 1 timeslot, has
been allocated for some mobiles in the cell
Name Q3 : upPipeless11kbps
Object : ccch
Feature : GPRS

411--9001--125
l
15061/1 Cumulative number of bronze users’ uplink allocations with a
Name Q3 : upTbfBronzeSatisfactMore90pCent
Object : CCCH
Feature : GPRS
Note : V14 counter
l
15062/0 Number of times an uplink bandwidth, of more than 1 timeslot,
Name Q3 : upPipeGreater11kbps
Object : ccch
Function : Cumulative number of times a throughput equal or greater than 11
kbps and strictly less than 22 kbps is reached in uplink direction by a
MS in the cell.
This downlink throughput counter provides a downlink
throughput histogram in the related cell. It represents the
cumulative number of times a throughput between the specified
limits is reached in downlink direction by an MS in the cell.
This uplink throughput counter provides an uplink throughput
histogram in the related cell. Each one represents the cumulative
number of times a throughput between the specified limits is
reached in uplink direction by an MS in the cell.
Feature : GPRS
Note : This throughput counters is computed using the number of bytes sent
or received in a pipe (GPRS), and is adapted to the CS used during the
transfer.
Note : Description updated due to introduction of counter
pcuUpPipeGreater22kbps

l
15062/1 Number of times a downlink bandwidth, of less than 1 timeslot,
Name Q3 : dnPipeLess11kbps
Object : ccch
Feature : GPRS
l
Name Q3 : upTbfSilverSatisfactLess50pCent
Object : CCCH
Feature : GPRS
Note : V14 counter
l
Name Q3 : upTbfBronzeSatisfactBet5090pCent
Object : CCCH
Feature : GPRS
Note : V14 counter

411--9001--125
l
Name Q3 : upTbfBronzeSatisfactLess50pCent
Object : CCCH
Feature : GPRS
Note : V14 counter
l
15062/5 Cumulative number of bronze users’ uplink allocations rejected
due to the admittance control
Name Q3 : upTbfBronzeRejectedForMinTput
Object : CCCH
Function : Cumulative number of bronze user’s uplink allocations rejected due
to the admittance control.
bronze user due to admittance control.
Feature : GPRS
Note : V14 counter
l
15063/0 Average MPC load
Name Q3 : cpuPBlockUtilAvg
Value range : [0 to 100%]
Object : pBlock
Function : This counter indicates the average CPU load (range 0 to 100%). The
average CPU load is the percentage of time the application has
something to since the last reset of this counter. Note that both the
spooled and operational counters are reset when either the spooled
counters are retrieved or when the operational counters are reset by
the operator.

Feature : GPRS
l
15063/2 Max MPC load
Name Q3 : cpuPBlockUtilMax
Value range : [0 to 100%]
Object : pBlock
Function : This counter indicates the maximum CPU load (range 0 to 100%).
Every “durationPeriod” (50 ms +/-- 8 ms (random)) the CPU load is
computed (percentage of time the application has something to do
during the “durationPeriod”). The maximum CPU load is the
maximum value of these computed CPU loads since the last reset of
this counter. Note that both the spooled and the operational counters
are reset when either the spooled counters are retrieved or when the
operational counters are reset by the operator.
Feature : GPRS
l
15066/0 Average CPU load
Name Q3 : cpuUtilAvg
Value range : [0 to 100] %
Object : logicalProcessor
Function : This counter indicates an average processor utilization level over a the
specified collection interval. This average is calculated based on one
minute CPU utilization averages.
Event : Refer to “function”

411--9001--125
l
15066/1 Minimum CPU load
Name Q3 : cpuUtilAvgMin
Function : This counter indicates the minimum processor utilization level over a
specified collection interval. The computing is based on one minute
CPU utilization averages.
l
15066/2 Maximum CPU load
Name Q3 : cpuUtilAvgMax
Function : This counter indicates the maximum processor utilization level over a
specified collection interval. This is based on one minute CPU
utilization averages.
l
15067/0 Fast RAM memory capacity
Name Q3 : memoryCapacityFastRam
Value range : [0 to 2147483647]
Function : This counter indicates the processor’s memory capacity (in kilobytes)
for fast ram memory.


l
15067/1 Normal RAM memory capacity
Name Q3 : memoryCapacityNormalRam
Value range : [0 to 2147483647]
for normal ram memory.
l
15067/2 Shared RAM memory capacity
Name Q3 : memoryCapacitySharedRam
Value range : [0 to 2147483647]
for shared ram memory.

411--9001--125
l
15068/0 Average, maximum, and minimum Fast RAM utilization
Name Q3 : memoryUsageAvgFastRam
memoryUsageAvgMaxFastRam
memoryUsageAvgMinFastRam
Value range : [0 to 2147483647]
Function : This attribute indicates the processors memory utilization (in
kilobytes) for fast ram memory in the specified collection interval.
This is calculated using 15 second samples.
l
15068/1 Average, maximum, and minimum Normal RAM utilization
Name Q3 : memoryUsageAvgNormalRam
memoryUsageAvgMaxNormalRam
memoryUsageAvgMinNormalRam
Value range : [0 to 2147483647]
Function : This attribute indicates the processor’s memory utilization (in
kilobytes) for normal ram memory in the specified collection interval.

l
15068/2 Average, maximum, and minimum Shared RAM utilization
Name Q3 : memoryUsageAvgSharedRam
memoryUsageAvgMaxSharedRam
memoryUsageAvgMinSharedRam
Value range : [0 to 2147483647]
Function : This attribute indicates the processor’s memory utilization (in
kilobytes) for shared ram memory in the specified collection interval.
l
15069/0 Memory capacity of the processor card’s shared message blocks
Name Q3 : sharedMsgBlockCapacity
Value range : [0 to 2147483647]
Function : This attribute indicates the processor’s shared message block memory
capacity (in kilobytes).
l
15069/1 Average, maximum, and minimum utilization of the processor
card’s shared message blocks
Name Q3 : sharedMsgBlockUsageAvg
sharedMsgBlockUsageAvgMax
sharedMsgBlockUsageAvgMin
Value range : [0 to 2147483647]
Function : This attribute indicates the processor’s shared message block memory
utilization (in kilobytes) over a specified collection interval. This is
calculated using 15 second samples.

411--9001--125

l
15069/2 Memory capacity of the processor card’s local message blocks
Name Q3 : localMsgBlockCapacity
Value range : [0 to 2147483647]
Function : This attribute indicates the processor’s local message block memory
capacity (in kilobytes). These message blocks are used for local
messaging on the card.
l
15069/3 Average, maximum, and minimum utilization of the processor
card’s local message blocks
Name Q3 : localMsgBlockUsageAvg
localMsgBlockUsageMax
localMsgBlockUsageMin
Value range : [0 to 2147483647]
Function : This counter indicates the processor’s memory utilization (in
kilobytes) of message blocks used for local messaging on the card,
calculated over a specified collection interval. This is calculated using
15 second samples.
Note : Calculations using 15 second sample applies to
localMsgBlockUsageAvg only.

l
15070/0 Number of bytes received on the link by the Framer
Name Q3 : rxBytes
Value range : [long integer]
Object : framer
Function : Number of bytes received on the link by the Framer in the last
collection interval.
l
15070/1 Number of bytes transmitted to the link by the Framer
Name Q3 : txBytes
Object : framer
Function : This counter provides the number of bytes transmitted to the link by
the Framer in the last collection interval. This value could be zero if
the application sends the frames directly to the link.
l
15071/0 Number of frames received on the link interface by the Framer
Name Q3 : rxFrames
Object : framer
Function : This counter provides the number of frames received on the link
interface by the Framer in the last collection interval.

411--9001--125
l
15071/1 Number of frames transmitted to the link interface by the
Framer
Name Q3 : txFrames
Object : framer
Function : This counter provides the number of frames transmitted to the link
interface by the Framer in the last collection interval. This value could
be zero if the application sends the frames directly to the link.
l
15072 Average total link utilization, based on the computation of the
total number of bytes received on the link
Name Q3 : rxTotalLinkUtil
Object : framer
Function : This counter provides the average total link utilization computed
based on the total number of bytes received on the link in the last
collection interval.

l
15073/0 Cumulative number of BSSGP PAGING PS PDU received on the
SPM and related to this PCM link
Name Q3 : psPaging
Object : pcmCircuit
Function : Cumulative number of BSSGP PAGING PS PDU received on the
SPM and related to this PCM link (received either on BVCI0 or BVCI
PTP).
The PS PAGING received on BVCI0 and broadcast by the frame
relay to the SPM cards are only counted on the master SPM which
manages the message (note that when the feature “paging load
distribution” is deactivated all the psPaging are counted on the
master SPM).
The PS PAGING received on BVCI PTP are counted on the
corresponding SPM which manages the message.
Event : This counter is incremented upon reception of a BSSGP PS PAGING
PDU, by any BVC, from the SGSN.
Feature : GPRS -- 26257 Paging load distribution on several LAPD
Note : V14 counter
l
15073/1 Cumulative number of BSSGP PAGING CS PDU received on the
SPM and related to this PCM link
Name Q3 : csPaging
Object : pcmCircuit
Function : Cumulative number of BSSGP PAGING CS PDU received on the
SPM and related to this PCM link (received either on BVCI0 or BVCI
PTP).
The CS PAGING received on BVCI0 and broadcast by the frame
relay to the SPM cards are only counted on the SPM which
manages the message (note that when the feature “paging load
distribution” is deactivated all the csPaging are counted on the
master SPM).
The CS PAGING received on BVCI PTP are counted on the
corresponding SPM which manages the message.
Event : This counter is incremented upon reception of a BSSGP CS PAGING
PDU, by any BVC, from the SGSN.

411--9001--125
Feature : GPRS - 26257 Paging load distribution on several LAPD

Note : V14 counter
15075/0 Number of modification of Agprs timeslots allocated in the cell

Name Q3 : dyAgprsNbModif
Value range : [0 to 4294967295]
Object : bts
Function : Cumulative number of requested modifications of the number of
allocated Agprs timeslots in the cell.
Event : This counter is incremented after the sending of a PCU AGPRS TS
SHARING message by the PCU to the BSC (this message contains the
identification of the least and the most loaded cell, so for each
message sent by the PCU, the corresponding counter is incremented in
the least and the most loaded cell).
Note : V14 counter

15075/1 Average, cumulative, sampling number of requested

modifications of the number of allocated Agprs TS in the
corresponding cell.
Name Q3 : dyAgprsAvgNbTimeslot
Function : The AVG value is now computed at SDO level by using the
corresponding CUM and NBS counters.
Name Q3 : pcuDyAgprsNbTimeslotsCum
Function : Number of iteration samples for pcuDyAgprsNbTimeslotsCum
Name Q3 : pcuDyAgprsNbTimeslotsNbs
Function : Cumulative number of Agprs timeslots allocated in the cell by the
BSC.
This corresponds to the formula: sum (dyAgprsNbTs). The value
dyAgprsNbTs is the number of Agprs TS allocated in the cell at the
th sample.
Object : bts
Function : Cumulative number of Agprs timeslots allocated in the cell by the
BSC.
This corresponds to the formula: sum (dyAgprsNbTs). The value
dyAgprsNbTs is the number of Agprs TS allocated in the cell at the
th sample.
Note: When the cell is set as the most or least loaded cell several times in
a row (to exchange jYeser TS following main TS), the load
criterion is not computed each time. In that case the counter is not
incremented.

411--9001--125
Event : updated after every cell load calculation

Note : V15 counter
Note : Note on EGPRS: This counter is based on 16kbps TS on the Agprs
(this means both joker and main channels). When the cell is set as the
most or less loaded cell several times in a row (to exchange joker TS
following main TS), the load criterion is not computed again, thus the
counter is not incremented.
Note : To allow the computation of the dyAgprsAvgNbTimeslots counter,
the PCUOAM will receive 2 PCU counters from the PCUSN, [Cell,
nonAckUpTbfEstablishment] and [Cell, ackUpTbfEstablishment]
and will transform them to pcuDyAgprsNbTimeslotsCum (15075/1
CUM CELL) and pcuDyAgprsNbTimeslotsNbs (15075/1 NBS
CELL).
The current transformation [Cell, dyAgprsAvgNbTimeslots] =>
dyAgprsAvgNbTimeslots (15075/1 AVG CELL), performed by the
PCUOAM, will have to be removed. The SDO will create itself
dyAgprsAvgNbTimeslots (15075/1 AVG CELL).
15075/2 Minimum number of Agprs timeslots allocated to the cell by

the BSC
Name Q3 : dyAgprsMinNbTimeslots
Value range : [0 to 4294967295]
Object : bts
Function : This correspond to the formula: min (dyAgprsNbTimes). The
value dyAgprsNbTimes is the number of Agprs TS allocated in the
cell at the th sample.
Note: Note on EGPRS: This counter is based on 16kbps TS on the Agprs
(this means both joker and main channels).
Event : Receipt of a PCU TDMA TS STATUS or PCU CELL STATUS

message from the BSC indicating the number of Agprs timeslots
allocated to the cell. This is updated after every cell load calculation.
Note : V14 counter
Note : Note on EGPRS: When the cell is set as the most or less loaded cell
several times in a raw (to exchange joker TS following main TS), the
load criterion is not computed again, thus the counter is not
incremented.

15075/3 Maximum number of Agprs timeslots allocated to the cell by

the BSC
Name Q3 : dyAgprsMaxNbTimeslots
Value range : [0 to 4294967295]
Object : bts
Function : This correspond to the formula: max (dyAgprsNbTimes). The
value dyAgprsNbTimes is the number of Agprs TS allocated in the
cell at the th sample.
Note: EGPRS: This counter is based on 16kbps TS on the Agprs (this
means both joker and main channels).
Event : Receipt of a TDMA TS STATUS REQ or PCU CELL STATUS
message from the BSC indicating the number of Agprs timeslots
allocated to the cell. This is updated after every cell load calculation.
Note : EGPRS: When the cell is set as the most or less loaded cell several
times in a raw (to exchange joker TS following main TS), the load
criterion is not computed again, thus the counter is not incremented.
Note : V14 counter
15076/0 Cumulative and sampling number of iteration samples for

pcuDyAgprsLoadCriterionCum
Name Q3 : pcuDyAgprsLoadCriterionCum
Value range : [0 to 4294967295]
Object : bts
Function : Average value of Agprs load criterion for the related cell.
The average value is calculated since the last reset PCU.
Formula = sum(Ln) see section Principles/Arbitration of
TF1262: Dynamic Agprs
Remark: When Ln = +∝ the counter is not incremented.
Note: For EGPRS the load criterion takes into account the main plus
joker TS. When the cell is set as the most or less loaded cell several
criterion is not computed again, thus the counter is not
incremented.
Note: This counter is updated at every cell load calculation.

Note : EGPRS:

411--9001--125
Event : The PCUOAM receives 2 PCU counters from the PCUSN

transforming them to a CUM Cell and a NBS Cell. These counters are
exposed to the SDO interface. This is updated at every cell load
calculation.
Name Q3 : pcuDyAgprsLoadCriterionNbs
Function : Number of iteration samples for pcuDyAgprsLoadCriterionCum
Note: For EGPRS the load criterion takes into account the main plus
joker TS. When the cell is set as the most or less loaded cell several
criterion is not computed again, thus the counter is not
incremented.
Note: This counter is updated at every cell load calculation.
Name Q3 : ackDnTbfEstablishment
Function : This AVG value is now computed at SDO level by using the
corresponding CUM and NBS counters.
Number of iteration samples for pcuDyAgprsLoadCriterionCum.
Note : To allow the computation of the dyAgprsAvgLoadCriterion counter,
the PCUOAM will receive 2 PCU counters from the PCUSN, { Cell,
nonAckDnTbfEstablishment } and { Cell, ackDnTbfEstablishment }
PCUSN GPRS Counters and Operational Attributes
PE/PCU/DD/0031 03.08/ EN Standard 21/Sept/2004 Page 136/154
and will transform them to pcuDyAgprsLoadCriterionCum (15076/0
CUM CELL) and create a NBS counter
pcuDyAgprsLoadCriterionNbs (15076/0 NBS CELL).
The current transformation { Cell, dyAgprsAvgLoadCriterion } =>
dyAgprsAvgLoadCriterion (15076/0 AVG CELL), performed by the
PCUOAM, will have to be removed.
Note : The SDO will create itself dyAgprsAvgLoadCriterion (15076/0 AVG
CELL).
Precise
When the cell is set as the most or least loaded cell several times in a
row (to exchange jYeser TS following main TS), the load criterion
is not computed each time. In that case the counter is not
incremented.
The load criterion is modified to take into account the number of
main plus jokers available.

Feature : GPRS (TF1262: Dynamic Agprs)

Note : V14 counter
The value 4294967295 means load = +∝
Note : The operator must to perform a reset of the counter.
Then display the counter (at the end of the test to have final values).
15076/1 Maximum value of Agprs load criterion

Name Q3 : dyAgprsMaxLoadCriterion
Value range : [0 to 4294967295]
Object : bts
Function : Maximum value of Agprs load criterion for the related cell.
Note: When the cell is set as the most or least loaded cell several times in
a row (to exchange jYeser TS following main TS), the load
criterion is not computed each time. In that case the counter is not
incremented.
Event : Updated after every calculation of cell loading.
Cn= AgprsFilterCoefficient * C + (1-- AgprsFilterCoefficient) * Cn--1
C= ∑PeakThroughputi * QoSi
i= allmobilesinthecell
Feature : GPRS (TF1262: Dynamic Agprs)
Note : When Ln = +? the counter is not incremented.
Note : V14 counter
The value 4294967295 means load = +∝
The counter is updated at most every second if the dynamic Agprs
is enabled at PCU level.
If the dynamic Agprs is deactivated at OMC--R cell level (i.e.
AgprsFilterCoefficient is equal to 0), the PCU takes the default
value of this parameter (10) in order to calculate the cell loading.
Note : The operator has to perform a reset of the counter.
Then display the counter (at the end of the test to have final values).
l
15077/0 Cumulative number of gold users’ downlink allocations with a
Name Q3 : dnTbfGoldSatisfactMore90pCent
Object : bts

411--9001--125

Feature : GPRS
Note : V14 counter
l
Name Q3 : dnTbfGoldSatisfactBet5090pCent
Object : bts
Feature : GPRS
Note : V14 counter
l
Name Q3 : dnTbfGoldSatisfactLess50pCent
Object : bts
Feature : GPRS
Note : V14 counter
l
15077/3 Cumulative number of gold users’ downlink allocations rejected
Name Q3 : dnTbfGoldRejectedForMinTput
Object : bts
Function : Cumulative number of gold users’ downlink allocations rejected due


gold user due to admittance control.
Feature : GPRS
Note : V14 counter
Note : Reject counters with minimum throughput for gold, silver, and bronze
by indicating that these counters are not incremented in case of
l
15078/0 Cumulative number of silver users’ downlink allocations with a
Name Q3 : dnTbfSilverSatisfactMore90pCent
Object : bts
Feature : GPRS
Note : V14 counter
l
Name Q3 : dnTbfSilverSatisfactBet5090pCent
Object : bts
Feature : GPRS
Note : V14 counter
l
Name Q3 : dnTbfSilverSatisfactLess50pCent
Object : bts

411--9001--125

Feature : GPRS
Note : V14 counter
l
15078/3 Cumulative number of silver users’ downlink allocations rejected
Name Q3 : dnTbfSilverRejectedForMinTput
Object : bts
Function : Cumulative number of silver users’ downlink allocations rejected due
silver user due to admittance control.
Feature : GPRS
Note : V14 counter
l
15079/0 Cumulative number of bronze users’ downlink allocations with a
Name Q3 : dnTbfBronzeSatisfactMore90pCent
Object : bts
Feature : GPRS
Note : V14 counter

l
Name Q3 : dnTbfBronzeSatisfactBet5090pCent
Object : bts
Feature : GPRS
Note : V14 counter
l
Name Q3 : dnTbfBronzeSatisfactLess50pCent
Object : bts
Feature : GPRS
Note : V14 counter
l
15079/3 Cumulative number of bronze users’ downlink allocations rejected
Name Q3 : dnTbfBronzeRejectedForMinTput
Object : bts
Function : Cumulative number of bronze users’ downlink allocations rejected
due to the admittance control.
bronze user due to admittance control.

411--9001--125
Feature : GPRS
Note : V14 counter
l
15100/0 Spare counter, 0 by default
Name Q3 : pcuEdgeTdma15100s0
Object : TDMA
Function : NA
Event : NA
Feature : EDGE traffic management
l
15101/0 Cumulative number of EGPRS RLC data blocks received by
the PCU on a TDMA.
Name Q3 : pcuEdgeDataBlocksReceivedUp
Object : TDMA
Function : Cumulative number of EGPRS RLC data blocks received by the PCU
on this TDMA.
Event : Reception of an EGPRS UL TBF in progress of a TRAU frame
without BFI
- a valid RLC data block in sequence received for the first time
-- a valid RLC data block in sequence already received
- a valid RLC data block out of sequence
-- an invalid RLC data block
Feature : GPRS
Note : In case of receipt of an EGPRS Header Stealing Frame, this counter is
not incremented.

l
15102/0 Average, cumulative, and sampling number of 8PSK_BEP
(assumed value) derived from the 8PSK_MEAN_BEP received
from an MS in this TDMA in the EGPRS BEP Link Quality
Measurements (8PSK_MEAN_BEP).
Name Q3 : pcuEdgeDnAvg8PskMeanBep
pcuEdgeDnCum8PskMeanBep
Function : Cumulative value of the 8PSK_BEP (assumed value) derived from
the 8PSK_MEAN_BEP received from a MS in this TDMA in the
EGPRS BEP Link Quality Measurements (8PSK_MEAN_BEP).
Measurement result: BEP in % * 100
Note : MEAN_BEP is calculated and filtered in a linear scale but mapped to
a logarithmic scale for reporting as defined in 3GPP 05.08, so for the
processing of the average value, the log10 (actual BEP) is used (the
value is between 0.60 and 3.60).
Note : The MEAN_BEP is used to derive the BEP (assumed value) reported
in the counter.
Event : Reception of an EGPRS Packet Downlink Ack/Nack by a EGPRS DL
TBF on this TDMA, containing a 8PSK_MEAN_BEP value set in the
EGPRS BEP link quality measurements.
Note : The EGPRS BEP link quality measurement is optional and may not be
reported by MS (the counter is not incremented).
Note : The 8PSK_MEAN_BEP may not be included in the EGPRS BEP link
quality measurements (the counter is not incremented).
Name Q3 : pcuEdgeDnNbs8PskMeanBep
Function : Number of values of the 8PSK_MEAN_BEP received from an MS in
this TDMA in the EGPRS BEP Link Quality Measurements
(8PSK_MEAN_BEP).
Event : Reception of an EGPRS Packet Downlink Ack/Nack by a EGPRS DL
TBF on this TDMA, containing a 8PSK_MEAN_BEP value set in the
EGPRS BEP link quality measurements.
Object : TDMA

411--9001--125
l
15103/0 Average, cumulative, and sampling number of GMSK_BEP
(assumed value) derived from the GMSK_MEAN_BEP received
from an MS in this TDMA in the EGPRS BEP Link Quality
Measurements (GMSK_MEAN_BEP).
Name Q3 : pcuEdgeDnAvgGmskMeanBep
pcuEdgeDnCumGmskMeanBep
Object : TDMA
Function : This counter has 3 possible functions and can be used to determine the
average or cumulative value, or the sampling number of the
GMSK_BEP derived from the GMSK_MEAN_BEP received from a
MS in this TDMA in the EGPRS BEP Link Quality Measurements
(GMSK_MEAN_BEP).
a logarithmic scale for reporting as defined in 3GPP 05.08, so for the
processing of the average value, the log10 (actual BEP) is used (the
value is between 0.60 and 3.60).
Note : The MEAN_BEP is used to derive the BEP (assumed value)
reported in the counter.
Event : Reception of an EGPRS Packet Downlink Ack/Nack by an EGPRS
DL TBF on this TDMA, containing a GSMK_MEAN_BEP value set
in the EGPRS BEP link quality measurements.
Note : The EGPRS BEP link quality measurement is optional and may not be
reported by MS (the counter is not incremented).
Note : The GMSK_MEAN_BEP may not be included in the EGPRS BEP
link quality measurements (the counter is not incremented).
Name Q3 : pcuEdgeDnNbsGmskMeanBep
Function : Number of values of the GMSK_MEAN_BEP received from an MS
in this TDMA in the EGPRS BEP Link Quality Measurements
(GMSK_MEAN_BEP).
Event : Reception of an EGPRS Packet Downlink Ack/Nack by an EGPRS
DL TBF on this TDMA, containing a GSMK_MEAN_BEP value set
in the EGPRS BEP link quality measurements.
Object : TDMA


15104/0 Average, cumulative, and smpling number of BEP (assumed value)

received by the PCU in each EGPRS RLC data block on this TDMA
Name Q3 : pcuEdgeUpAvgMeanBep
pcuEdgeUpCumMeanBep
Function : Cumulative value of the BEP (assumed value) received by the PCU in
each EGPRS RLC data block on this TDMA.
Upon receipt of an EGPRS RLC/MAC block by a EGPRS TBF on this
TDMA, the Mean--BEP is used to derive the assumed BER. This
assumed BEP is cumulated in the pcuEdgeUpCumMeanBep counter.
Measurement result: BEP in % * 100
a logarithmic scale for reporting as defined in TRAU Frame I/F, so for
the processing of the average value, the log10 (actual BEP) is used
(value between 0.60 and 3.60).
Note : The MEAN_BEP is used to derive the BEP (assumed value) reported
in the counter.
Event : Receipt of a TRAU frame without BFI by an EDGE UL TBF on this
TDMA.
Name Q3 : pcuEdgeUpNbsMeanBep
Function : Number of MEAN_BEP values received by the PCU in each EGPRS
RLC data block on this TDMA.
Note : All frames received in an EGPRS TBF are taken into account except
the one with BFI.
Object : TDMA
Event : Receipt of a TRAU frame without BFI by an EDGE UL TBF on this
TDMA.
Feature : GPRS
Note : All frames received in an EGPRS TBF are taken into account except
the one with BFI.

411--9001--125
l
Object : TDMA
Function : NA
Event : NA
Feature : GPRS TBF establishment improvement -- one phase access (15015)
Note : V15 counter
l
15106/0 Spare coumter, 0 by default
Object : TDMA
Function : NA
Event : NA
Note : V15 counter
l
Object : TDMA
Function : NA
Event : NA
Note : V15 counter

l
15108/0 Cumulated number of radio blocks sent by the PCU
Object : TDMA
Function : Cumulated number of radio blocks sent by the PCU on this TDMA for
downlink pipes in verbose state (data blocks + control blocks)
Event : Downlink pipe closure
Note : V15 counter
See also the Note for counter pcuEdgeTdma15109s0 below.

l
15109/0 Cumulated number of radio blocks that could have been sent by the
PCU
Object : TDMA
Function : Cumulated number of radio blocks that could have been sent by the
PCU on this TDMA for downlink pipe in verbose state (data blocks +
control blocks) if the mobiles had had 100% of the bandwidth during
their verbose time.
Event : Downlink pipe closure
Note : V15 counter
The counters pcuEdgeTdma15108s0 and pcuEdgeTdma15109s0 are

used in quantifying the satisfaction of the radio allocation versus the
multislot class of the mobile. If a mobile receives a downlink
bandwidth equal to the maximum bandwidth that it could have used
according to its multislot class, its satisfaction rate is 100%:
avg_mobile_sat_rate = pcuDnBlocksSent (pcuEdgeTdma15108s0) /

pcuDnBlocksVerbose (pcuEdgeTdma15109s0)
For example, if pcuDnBlocksVerbose = 18 and pcuDnBlocksSent =

12, then avg_mobile_sat_rate = 12/18 = 66% satisfaction rate.

411--9001--125
l
15110/0 Total number of TRAU data blocks and control blocks (GPRS or
EGPRS) snet on the Agprs Main channels in the DL direction
Name Q3 : pcuAgprsMainNbofBlocksDn
Object : bts
Function : Total number of TRAU EDGE data blocks sent on the Agprs Main
channels in the DL direction.
Event : This counter is incremented after a TRAU data block or control block
sent on the Agprs Main Channel by a GPRS or EGPRS TBF.
Feature : Data backhaul evolution (19174)
Note : V15 counter
l
15111/0 Average, cumulative, and sampling number of EGPRS TBF
downgraded in GPRS
Name Q3 : pcuEdgeDowngradedTbfAvg
pcuEdgeDowngradedTbf
pcuEdgeDowngradedTbfNbs
Object : bts
Function : These counters are used to determine the average or cumulative value,
or the sampling number of EGPRS TBF downgraded in GPRS.
Event : In the UL direction, when a Packet Resource Request including an
EDGE request is received by PCU.
In the DL direction, when a first DL unit data including an EDGE
request is received for a MS with no ongoing TBF (note that the
counter is incremented for each attempt to establish the DL TBF).
In those cases, and if the PCU allocates the MS on a GPRS TDMA, the
counter is incremented.


Note : V15 counter
Note : 1. The counter is not incremented during a Full--Duplex establishment
where the first TBF was already downgraded.
2. The counter is not incremented if EDGE is not activated in the cell
(through the flag EGPRSServices).
3. The counter is not incremented if the value specified by the SPM
capacity limitation is reached. Note also that the value of this counter
cannot be linked the value of counters upTbfReleases and
dnTbfReleases.
4. The counter is also increased if the allocation on the GPRS TDMA
fails (due to lack of GPRS resources) after the degradation from
EDGE to GPRS).
l
15112/0 Average, cumulative, and sampling size in bytes of all the RLC
EDGE data blocks received for the first time (i.e. fresh block) on a
pipe
Name Q3 : pcuEdgeUpAvgUsefulDataPerCell
pcuEdgeUpCumUsefulDataPerCell
pcuEdgeUpNbsUsefulDataPerCell
Object : bts
Function : These counters are used to determine the average, cumulative, or
sampling size in bytes of all the RLC EDGE data blocks received for
the first time on a pipe.
The pcuEdgeUpAvgUsefulDataPerCell represents the average
throughput at RLC level and cell level for every EGPRS transfer.
– pcuEdgeUpAvgUsefulDataPerCell = ratio between
pcuEdgeUpCumUsefulDataPerCell and
– pcuEdgeUpCumUsefulDataPerCell = Cumulated size in bytes of
all the EGPRS data blocks received for the first time (i.e. fresh
block) on a pipe.
– pcuEdgeUpNbsUsefulDataPerCell = Cumulated time in multiples
of 20 ms where the MS is in EGPRS UL data transfer.
T0 = Time of the first valid TRAU frame received in uplink for that
mobile (i.e. without BFI)
T1 = Time of the reception of the last block with CV=0 (when all the
blocks have been correctly received). The counter is equal to
T1--T0+1

411--9001--125
Event : An RLC EDGE data block is received for the first time (i.e. fresh
block) on a pipe by a EGPRS UL TBF.
Precise
If there is loss of communication, the duration counters are not
incremented.
pcuEdgeUpAvgUsefulDataPerCell = ratio between
pcuEdgeUpCumUsefulDataPerCell = Cumulated size in bytes of

block) on a pipe.
pcuEdgeUpNbsUsefulDataPerCell = Cumulated time in multiples

T1 = Time of the reception of the last block with CV=0 (when all
the blocks have been correctly received). The counter is equal to
T1--T0+1
Feature : EDGE traffic management (20231) - one phase access (15015)
Note : V15 counter
Note : If there is loss of communication, the duration counters are not
incremented.

l
EDGE data blocks sent for the first time (i.e. fresh block)
Name Q3 : pcuEdgeDnAvgUsefulDataPerCell
pcuEdgeDnCumUsefulDataPerCell
pcuEdgeDnNbsUsefulDataPerCell
Object : bts
Function : This counter has 3 possible functions and can be used to determine the
average, cumulative, or sampling size in bytes of all the RLC EDGE
data blocks sent for the first time on a pipe.
– pcuEdgeUpAvgUsefulDataPerCell = ratio between
– pcuEdgeUpCumUsefulDataPerCell = Cumulated size in bytes of
block) on a pipe.
– pcuEdgeUpNbsUsefulDataPerCell = Cumulated time in multiples
T1 = Time of the reception of the last block with CV=0 (when all the
blocks have been correctly received). The counter is equal to
T1--T0+1
Event : An RLC EDGE data block is sent for the first time (i.e. fresh block) on
a pipe by a EGPRS DL TBF.
Note : V15 counter
4
Name Q3 : pcuEdgeCell15114s0
Object : bts
Function : NA

411--9001--125
Event : NA
Note : V15 counter

Object : bts
Function : NA
Event : NA
Note : V15 counter
l
Object : bts
Function : NA
Event : NA
Note : V15 counter
l
Object : bts
Function : Spare counter, 0 by default.
Event : NA


Note : V15 counter
l
15118/0 Cumulative, minimum, maximum, average, and sampling number
of Agprs Joker timeslots allocated to the cell by the BSC
Name Q3 : pcuDynAgprsJokerNbsNbTimeslot
Function : Sampling number of Agprs Joker TS allocated to the cell by the BSC.
This correspond to the formula: sum (dyAgprsNbJokerTs). The
value dyAgprsNbJokerTs is the number of 16 kbps Agprs joker TS
allocated in the cell at the th sample.
Tune the Agprs Joker according to the percent of EDGE mobile in the
network, radio conditions of the cell, and the target QoS offered by the
operator.
Event : Updated after every cell load calculation
Name Q3 : pcuDynAgprsJokerCumNbTimeslot
Function : Cumulative number of Agprs Joker TS allocated to the cell by the
BSC.
operator.
See PcuSnGprsCounters_V03[1].08, Chapters 7.3 and 8.
Name Q3 : pcuDynAgprsJokerMinNbTimeslot
Function : Minimum number of Agprs Joker TS allocated to the cell by the BSC.
operator.

411--9001--125

Name Q3 : pcuDynAgprsJokerMaxNbTimeslot
Function : Maximum number of Agprs Joker TS allocated to the cell by the BSC.
operator.
Name Q3 : pcuDynAgprsJokerAvgNbTimeslot
Function : Average number of Agprs Joker TS allocated to the cell by the BSC.
operator.
Object : bts
Note : V15 counter
Note : EGPRS: When the cell is set as the most or less loaded cell several
criterion is not computed again, thus the counter is not incremented.
l
15119/0 Number of TRAU EDGE data blocks sent on the Agprs Joker
channels in the DL direction
Name Q3 : pcuAgprsJokerNbofBlocksDn
Object : bts
Function : Total number of TRAU data blocks (GPRS or EGPRS) sent on the
Agprs Joker channels in the DL direction.

Event : This counter is incremented after a TRAU data block is sent on the
Agprs Joker Channel by a GPRS or EGPRS DL TBF.
Note : V15 counter
l
Object : bts
Function : NA
Event : NA
Note : V15 counter
l
Object : bts
Function : NA
Event : NA
Note : V15 counter

411--9001--125
l
15122/0 Number of EGPRS TBF establishment requests.
Name Q3 : pcuEdgeTbfEstReq
Object : bts
Function : Cumulative number of EGPRS TBF establishment requests.
Event : In the UL direction, when a Packet Resource Request including an
EDGE request is received by PCU.
In the DL direction, when a first DL unit data including an EDGE
request is received for an MS with no on--going TBF (note that the
counter is incremented for each attempt to establish the DL TBF).
Precise
The counter is incremented for each attempt to establish the DL
TBF.
The counter is not incremented during a full duplex TBF
establishment.
The counter is not incremented if EDGE is not activated in the cell
The counter is not incremented when The value specified by the
SPM capacity limitation is reached.
Note : V15 counter
Note : The counter is not incremented during a Full--Duplex establishment.
Note : The counter is not incremented if EDGE is not activated in the cell
Note : Note also that the value of this counter cannot be linked the value of
counters upTbfReleases and dnTbfReleases.
l
15123/0 Cumulated time in multiple of 20ms where the MS is in EDGE UL
data transfer.
Name Q3 : pcuEdgeUpUsefulDataDurationPerCell
Object : bts
Function : Cumulative time in multiples of 20 ms where the MS is in EDGE UL
data transfer.

Event : At T1 the counter is incremented with T1--T0+1

Precise
This counter is incremented if EDGE is activated in the cell.
the blocks have been correctly received)
The counter is equal to T1--T0+1
Feature : EDGE traffic management (20231) - one phase access (15015) -
Extended UL TBF (22915)
Note : V15 counter
Note : In case of loss of communication the duration counters are not
incremented.
l
15124/0 Cumulated time in multiple of 20ms where the MS is in EDGE DL
data transfer
Name Q3 : pcuEdgeDnUsefulDataDurationPerCell
Object : bts
Function : Cumulated time in multiple of 20ms where the MS is in EDGE DL
data transfer.
Event : At T1 the counter is incremented with T1--T0+1
Note : V15 counter
l
Object : bts
Function : NA

411--9001--125
Event : NA
Note : V15 counter
l
Object : bts
Function : NA
Event : NA
Note : V15 counter
l
15127/0 Total number of TRAU EDGE data blocks sent on the Agprs Main
channels in the UL direction
Name Q3 : pcuAgprsMainNbofBlocksUp
Object : bts
Function : Number of TRAU data blocks or control blocks (GPRS or EGPRS)
received on the Agprs Main TS in the UL direction.
This counter is equal to:
up data block EDGE + up control block EDGE + invalid block up
EDGE + up data block GPRS + up control block GPRS + up invalid
block up GPRS
Note : A TRAU frame is invalid if:
It is received with a BFI (Bad Frame Indicator set by the BTS when
no correct block has been decoded on the radio).
Then when a TRAU frame is valid, the contents can be invalid
(depending on the type of the frame).
Note : A stealing frame is invalid if:
One of its fields (class, type, length, ta, rach info) is erroneous.
the access burst type (8 or 11 bits format) used is inconsistent with
the Access Burst Type parameter received in message CELL
AVAILABLE or CELL BROADCAST INFO MODIFY.

Event : This counter is incremented after a TRAU data block or control block
is received on the Agprs Main TS by a GPRS or EGPRS TBF.
Note : V15 counter
Note : The UL blocks (data or control) are counted when allocated to that
mobile (by USF, polling).
The first PRR are also counted (with or without CCCH@BTS).
l
15128/0 Total number of TRAU EDGE data blocks sent on the Agprs Joker
channels in the UL direction
Name Q3 : pcuAgprsJokerNbofBlocksUp
Object : bts
Function : Total number of TRAU EDGE data blocks (GPRS or EGPRS)
received on the Agprs Joker TS in the UL direction.
Note : Unexpected blocks are NOT counted.
Event : This counter is incremented after a TRAU data block is received on
the Agprs Joker TS by a GPRS or EGPRS UL TBF.
Feature : Data backhaul evolution (19174).
Note : V15 counter
l
15129/0 Number of periods of 20ms when missing jokers in the DL direction
to reach the MCS targeted by the Link Adaptation
Name Q3 : pcuLackAbisJokerTSNbs
Function : Number of periods of 20 ms when there was missing Abis Jokers TS in
the DL direction to reach the MCS targeted by the Link Adaptation.

411--9001--125
Event : During a 20 ms period, if pcuLackAbisJokerTSCum is incremented,

then the counter is incremented by 1 unit.
Name Q3 : pcuLackAbisJokerTSCum
Function : Number of lack Abis Jokers TS in the DL direction to reach the MCS
targeted by the Link Adaptation.
Every 20ms, the PCU internally computes the missing Jokers on a
given TDMA.
The internal DL--JokerMissing counter is cumulated on all the TS
of the TDMA; it corresponds to the number of Agprs jokers TS
missing to reach the MCS targeted by the LA.
The counter lack of Abis Joker is then computed from this internal
counter with the following metric:
- Number of lack of Abis joker TS = DL--JokerMissing - (Max
number of Joker TS and Current Number of Joker TS).
Max number of Joker TS is known at the TDMA configuration in the
TDMA--TS--STATUS message and corresponds to the max number of
Agprs joker TS which can be connected on a TDMA according to the
BTS type (so linked to max on Abis).
Current Number of Joker TS is known at the TDMA configuration in
the TDMA--TS--STATUS message and corresponds to the current
number of Agprs joker TS connected.
There is no control in the PCU between these two fields, so if “Current
Number of Joker TS: is greater than “Max number of Joker TS“ then
Number of Lack of Abis joker TS is equal to DL--JokerMissing.
Note : If (and only if) the “Number of lack of Abis joker TS” is positive, the
counter pcuLackAbisJokerTSCum is increased of “Number of lack of
Abis joker TS”.
Event : During a 20 ms period, if some Abis Joker TS are missing in DL on the
TDMA. See also, PE/DAS/DD/0006, 20231 - EDGE Feature
Name Q3 : pcuLackAbisJokerTSAvg
Function : The average number of missing Abis Joker TS are automatically
computed at the SDO (OMC--R level). It is the result of dividing the
number of pcuLackAbisJokerTSCum by the number of
pcuLackAbisJokerTSNbs at the end of the observation period..
Object : TDMA
Note : V15 counter

l
15132/0 Number of 1/2 EDGE RLC Data Blocks transmitted in MCS2 by
PCU in the DL direction
Name Q3 : pcuEdgeDnTransmittedMcs2
Object : TDMA
Function : Number of 1/2 EDGE RLC Data Blocks that are transmitted in MCS2
by PCU in the DL direction.
Event : An EDGE DL RLC Data Block sent by PCU in MCS2 (for the first
time (i.e. fresh block) or restransmitted).
Precise
The counter is only incremented by 1 unit when the MCS2 data
block is a re--segmented data block (this means it is half a RLC data
block).
When one EDGE DL radio block is sent by the PCU in the DL
direction using MCS2, the counter is incremented by 2 units (1
RLC data block per radio block).
Note : V15 counter
l
Object : TDMA
Function : Number of 1/2 EDGE RLC Data Blocks transmitted in MCS3 by PCU
in the DL direction.
Event : An EDGE DL radio data block sent by PCU in MCS3 (for the first
Precise
block is a re-- - segmented data block (this means it is half a RLC
data block).
direction using MCS3, the counter is incremented by 2 units (1
RLC data block per radio block).

411--9001--125

Note : V15 counter
Note : The counter is only incremented by 1 unit when the MCS3 data block
is a re--segmented data block.
l
Object : TDMA
Function : Number of 1/2 EDGE RLC Data Blocks transmitted in MCS5 by
PCU in the DL direction.
Precise
direction using MCS5, the counter is incremented by 2 units (1 RLC
data block per radio data block).
Note : V15 counter
l
Object : TDMA
Function : Number of 1/2 EDGE RLC Data Blocks transmitted in MCS6 by

Precise
data block per radio data block).
Note : V15 counter
l
Object : bts
Precise
data blocks per radio data block).
Note : V15 counter
l
Object : TDMA

411--9001--125
Precise
Note : V15 counter
l
Object : TDMA
Precise
Note : V15 counter

l
15142/0 Number of 1/2 EDGE radio data blocks that were commanded by
the Link Adaptation in MCS2 AND sent in MCS2 by PCU in the DL
direction AND NACK by the MS.
Name Q3 : pcuEdgeMcs2RequestRetransDataBlockDn
Object : TDMA
Function : When an E--GPRS PACKET DOWNLINK ACK/NACK is received
by PCU, the list of NACK blocks to be repeated is updated. The
counter is incremented by 2 units for each of these repeated blocks that
were targeted in MCS2 in the previous transmission.
Event : An EDGE Radio Data Block targeted by LA in MCS2 and sent in
MCS2 (for the first time (i.e. fresh block) or retransmitted) is NACK
by MS in PDAN.
Unit : 1/2 EDGE radio data block
Feature : EDGE link adaptation (20219)
Note : 1 to 7 applicable to pcuEdgeMcs9RequestRetransDataBlockDn
(15149) also apply to this counter.
l
Object : TDMA
Event : An EDGE DL radio data block targeted by LA in MCS3 and sent in
by MS in PDAN.
Note : V15 counter

411--9001--125
Note: 1 to 7 applicable to pcuEdgeMcs9RequestRetransDataBlockDn (15149)

also apply to this counter.
l
Object : TDMA
by MS in PDAN.
Note : V15 counter
l
Object : TDMA
by MS in PDAN.


Note : V15 counter
l
Object : TDMA
Event : An EDGE DL RLC Data Block targeted by LA in MCS7 and sent in
by MS in PDAN.
Note : V15 counter
l
Object : TDMA

411--9001--125

by MS in PDAN.
Note : V15 counter
l
Object : TDMA
by MS in PDAN.


Note : V15 counter
Note : 1. The counter (related to 8PSK modulation) is NOT incremented
when the LA decision has been downgraded in GMSK because of a
GPRS MS in the UL direction (case GMSK--Only in DL for the
downgraded blocks).
2. The counter is NOT incremented when the LA decision has been
downgraded because of a lack of Joker TS on the backhaul.
downgraded to best fit the data to be transmitted.
4. The counter is NOT incremented during preventive retransmission
periods (this means when at least a PENDING_ACK block is sent in
the radio block).
5. The counter is NOT incremented during Keep Alive periods.
6. The counter is NOT incremented until a valid measure is received
from the MS.
7. If the block was previously NACK and repeated by PCU less than a
RTD before, the block is not repeated by PCU and the counter is NOT
incremented. More details on the ARQ algorithm can be found in
PE/DAS/DD/0015, 20189--EDGE ARQ W. Mgt. & Comp. Bitmap.
8. In the special case where the previous transmission was in MCS7, 8,
or 9, and only half of the block is acknowledged (i.e. only 1 BSN is
correct above 2), the counter is incremented by 1 unit.
l
15152/0 Number of 1/2 EDGE radio data blocks that are commanded by the
Link Adaptation in MCS2 AND sent in MCS2 by PCU in the DL
direction.
Name Q3 : pcuEdgeLADnTargetedTransmittedMcs2
Object : TDMA
Function : When one EDGE radio data block is sent by PCU in the DL direction
using the MCS2, commanded by the nominal Link Adaptation tables,
the counter is incremented by 2 units.
MCS2 (for the first time (i.e. fresh block) or retransmitted).

411--9001--125

Note : V15 counter
Note: Notes 1 to 6 applicable to pcuEdgeLADnTargetedTransmittedMcs9
(15159/0) also apply to this counter
l
direction.
Object : TDMA
Note : V15 counter
Note : Notes 1 to 6 applicable to pcuEdgeLADnTargetedTransmittedMcs9
(15159/0) also apply to this counter.
l
direction.
Object : TDMA


Note : V15 counter
l
direction.
Object : TDMA
Note : V15 counter
l
direction.
Object : TDMA

411--9001--125

Note : V15 counter
l
direction.
Object : TDMA
Note : V15 counter
l
direction.
Object : TDMA


Note : V15 counter
downgraded blocks).
downgraded to best fit the data to be transmitted.
4. The counter is NOT incremented during preventive retransmission
periods (this means when at least a PENDING_ACK block is sent in
the radio block).
5. The counter is NOT incremented during Keep Alive periods.
from the MS.
l
15162/0 Number of 1/2 EDGE RLC Data Blocks that are transmitted in
MCS2 by MS in the UL direction.
Name Q3 : pcuEdgeUpTransmittedMcs2
Object : TDMA
by MS in the UL direction.

411--9001--125
Event : Reception of an EDGE UL radio data block in MCS2 (with frame

validity bit set to 0 or 1). The counter is not incremented when a BFI is
received.
Precise
The counter is incremented by 2 units (1RLC data block per radio
data block) when any of the following is received by the PCU in the
UL direction using MCS2:
EDGE radio data block (with frame validity bits = 0 or 1)
“EGPRS--Header”
TRAU data frame with frame validity set to 0
Feature : 20219 (EDGE link adaptation)
Note : V15 counter
downgraded blocks).
is a re--segmented data block (Split Block Indicator in RLC/MAC
header equal to 0x10 or 0X11).
l1/2
Object : TDMA


received.
Precise
EGPRS--Header
block is a re--segmented data block (Split Block Indicator in
RLC/MAC header equal to 0x10 or 0X11).
Note : V15 counter
is a re--segmented data block (Split Block Indicator in RLC/MAC
header equal to 0x10 or 0X11).
l
Object : TDMA

411--9001--125

validity bit set to 0 or 1). Reception of a TRAU frame
“EGPRS--Header” MCS5. The counter is not incremented when a BFI
is received.
Precise
data
block) when any of the following is received by the PCU in the UL
direction using MCS5:
EGPRS--Header
Note : V15 counter
Note : The counter is NOT incremented when a BFI is received.
l
MS in the UL direction.
Object : TDMA
Function : Number of 1/2 EDGE RLC Data Blocks transmitted in MCS6 by MS
in the UL direction.
received.
Precise
EDGE UL radio data block (with frame validity bits = 0 or 1)
“EGPRS--Header”


Note : V15 counter
l
Object : TDMA
Event : The counter is incremented by 4 units. The counter is not incremented
when a BFI is received.
Precise
The counter is incremented by 4 units (2 RLC data blocks per radio
Semi--frame
EGPRS--Header
Note : pcuEdgeUpTransmittedMcs7 (15167, CUM, TDMA) is incremented
by 4 (note also that the counter would have been incremented if only
the header had been received by the PCU).
Note : V15 counter
l
Object : TDMA

411--9001--125
Event : The counter is incremented by 4 units. The counter is not incremented

when a BFI is received.
Precise
Semi--frame
EGPRS--Header
Note : V15 counter
l
Object : TDMA
validity bits set to 0 or 1)
Reception of a TRAU frame “EGPRS--Header” MCS9.
Reception of a TRAU Semi--Frame MCS9H.
The counter is NOT incremented when a BFI is received.
Precise
“Semi--frame”
“EGPRS--Header”


Note : V15 counter
l
15172/0 Number of 1/2 EDGE Radio Data Blocks that were commanded by
the Link Adaptation in MCS2 AND sent in MCS2 by MS in the UL
direction AND badly received by BTS.
Name Q3 : pcuEdgeMcs2RequestRetransDataBlockUp
Object : TDMA
Function : When an USF is scheduled for a MS in the DL direction, the PCU
internally associates that block with the MCS commanded by the link
Adaptation in the UL direction. When a block is badly received by
PCU and if this Radio Data Block was targeted in MCS2, the counter
is incremented by 2 units.
Event : Block badly received by PCU while targeted in MCS2 by link
adaptation.
Note : V15 counter
Note : Notes 1 to 6 applicable to
pcuEdgeMcs9RequestRetransDataBlockUp (15179/0) also apply to
this counter.
l
Object : TDMA

411--9001--125

adaptation.
Source : 11recorded by the PCU
Note : V15 counter
Note : In some cases the PCU receives a semi--block with either FV bits
equal to 0 or both FV bits are equal to 0.
Note : 1. The counter (related to GMSK or 8PSK modulation) is NOT
incremented when the LA decision has been downgraded in GMSK
because the MS is not supporting 8PSK in the UL direction (case
GSMK Only in UL).
3. The counter is NOT incremented when the MS has downgraded the
MCS of the last block to best fit the data to be transmitted.
4. When MCS is modified by PCU in PUAN (or PUASS or PTR), the
PCU assumes the MCS is taken into account after the same reaction
time as for the TBF allocations. The counter is NOT incremented until
the modification is acknowledged by the mobile (by a PCA or by UL
data received on the new allocated timeslots). This mechanism allows
avoiding changing the MCS on the very first UL samples that are not
filtered yet.
from the BTS.
this counter.
l
Object : TDMA


adaptation.
Note : V15 counter
this counter.
l
Object : TDMA
adaptation.
Note : V15 counter
this counter.

411--9001--125
l
Object : TDMA
internally associates that block with the MCS commanded by the Link
Adaptation in the UL direction. When a Block is badly received by
PCU (E--GPRS Header with cause ”Bad CRC on the radio” or a
Semi--frame or a TRAU Data frame with Frame Validity set to ’0’ on
both BSN), and if this Radio Data Block was targeted in MCS7, the
counter is incremented by 2 units.
When a Block is partially received (”Semi--frame with cause 1st or
2nd block lost or a TRAU Data frame with one of the 2 Frame Validity
set to ’0’), and if this Radio Data Block was targeted in MCS7, the
counter is incremented by 1 unit.
adaptation.
Note : V15 counter
this counter.

l
Object : TDMA
adaptation.
Note : V15 counter
this counter.

411--9001--125
l
Object : TDMA
Function : Number of 1/2 EDGE Radio Data Blocks that were commanded by
When an USF is scheduled for a MS in the DL direction, the PCU
adaptation.


Note : V15 counter
GSMK Only in UL).
filtered yet.
from the BTS.
6: In the special case of E--GPRS Header with cause “Backhaul
Limitation”, the counter is NOT incremented.
7: In the special case of “Semiblocks” with cause “No block lost” or
the two Frame Validity bits are equal to 1, the counter is NOT
incremented.
l
Link Adaptation in MCS2 AND sent in MCS2 by MS in the UL
direction.
Name Q3 : pcuEdgeLAUpTargetedTransmittedMcs2
Object : TDMA
Adaptation in the UL direction. When a data block (with frame
validity bits = 0 or 1) or a “Semi--Frame” or an “EGPRS--Header” or a
TRAU Data frame with Frame Validity set to ’0’ is received by PCU,
and if the MCS is equal to the MCS commanded by LA, the counter is
increased by 2 units.

411--9001--125
Event : Transmission by the MS of a data block in MCS2 when MCS2 is the

coding scheme commanded by the LA.
Note : V15 counter
Note: Notes 1 to 5 on pcuEdgeLAUpTargetedTransmittedMcs9 (15189/0) also
apply to this counter.
l
direction.
Object : TDMA
validity bits = 0 or 1) or a ”Semi--Frame” or an “EGPRS--Header” or a
Note : V15 counter

l
direction.
Object : TDMA
validity bits = 0 or 1) or a ”Semi--Frame” or an ”EGPRS--Header” or a
Note : V15 counter
Note : Notes 1 to 5 on pcuEdgeLAUpTargetedTransmittedMcs9 (15189/0)
l
direction.
Object : TDMA

411--9001--125

Note : V15 counter
l
direction.
Object : TDMA
validity bits = 0 or 1) or a ”Semi--Frame” or an “EGPRS--Header” or a
Note : V15 counter

l
direction.
Object : TDMA
Note : V15 counter
l
direction.
Object : TDMA
validity bits = 0 or 1) or a ”Semi--Frame” or an ”EGPRS--Header” or a

411--9001--125

Note : V15 counter
GSMK Only in UL).
filtered yet.
from the BTS.
l
15190/0 Cumulative number of “one phase access” RACH (Channel
Request) received by the PCU in this cell.
Name Q3 : pcuChannelRequestOnePhase
Object : CCCH
Function : Cumulative number of “one phase Channel Request” received at the
PCU level.
This counter is only incremented when the PCU receives a channel
request one phase.
Event : Receipt of a Channel Request message, one phase by PCU.


Note : V15 counter
Note : When the CCCH at BTS and the one phase access features are
activated, the one phase access RACH are forwarded to the PCU by
the BTS.
When the CCCH at BTS is not activated all the RACH (one phase, two
phase) are forwarded to the PCU by the BTS.
Note : This counter has a one phase access feature (in case of CCCH at BTS).
l
15191/0 Cumulative number of “Immediate Assignment Uplink” messages
sent by the PCU to establish a one phase access UL TBF in this cell.
Name Q3 : pcuUpTbfImmediateAssignmentOnePhase
Object : CCCH
Function : Cumulative number of “Immediate Assignment Uplink” messages
sent by the PCU to establish a one phase access UL TBF in this cell.
Event : Sending of an Immediate Assignment Uplink message for the
establishment of a one phase access UL TBF, by the PCU.
Note : V15 counter
l
15192/0 Cumulative number of failures of the contention resolution
procedure in case of one phase access.
Name Q3 : pcuContentionFailureOnePhase
Object : CCCH
Function : Cumulative number of failures of the contention resolution procedure
in case of one phase access.
Event : Non reception of an uplink RLC data block with a TLLI after
“C_one_phase” attempts (that is, TRAU frame with BFI or RLC data
block without TLLI).
Non reception of a PCA after 6 repetitions of the Packet Uplink
Ack/Nack containing the TLLI.

411--9001--125

Note : V15 counter
l
GPRS data blocks received for the first time on a pipe (i.e. fresh
block)
Name Q3 : pcuUpThroughputAvg
Function : Average time in multiple of 20 ms where the MS is in GPRS UL data
transfer.
Event : A RLC GPRS data block is received for the first time (that is fresh
block) on a pipe by a GPRS UL TBF.
Name Q3 : pcuUpThroughputNbs
Function : Cumulated time in multiple of 20 ms where the MS is in GPRS UL
data transfer.
the blocks have been correctly received). The counter is equal to
T1--T0+1
The pcuUpThroughputAvg represents the average throughput at
RLC level and cell level for every GPRS transfer.
pcuUpThroughputAvg = ratio between pcuUpThroughputCum
and pcuUpThroughputNbs
pcuUpThroughputCum = Cumulated size in bytes of all the GPRS
data blocks received for the first time (i.e. fresh block) on a pipe.
pcuUpThroughputNbs = Cumulated time in multiples of 20 ms
where the MS is in GPRS UL data transfer.
Name Q3 : pcuUpThroughputCum
Function : Cumulated size in bytes of all the RLC GPRS data blocks received for
the first time (i.e. fresh block) on a pipe.
Value range : 0..4294967295
Object : bts

Feature : GPRS TBF establishment improvement - one phase access (15015) --

Extended UL TBF (22915)
Note : V15 counter
Note : If there is loss of communication, the duration counters are not
incremented.
l
15194/0 Number of times a throughput equal or greater than 22 kbps is
reached in uplink direction by a MS in the cell.
Name Q3 : pcuUpPipeGreater22kbps
Value range : 0..4294967295
Object : bts
Function : Number of times a throughput equal or greater than 22 kbps is reached
in uplink direction by a MS in the cell.
Event : Pipe closure for a GPRS TBF
Note : V 15 counter
l
15195/0 Number of DL TBF pre--established and effectively used for the
transmission of a DL--UNITDATA received from the SGSN.
Name Q3 : pcuDnPreEstWithLLCFrameTransmitted
Value range : 0..4294967295
Object : bts
Function : Number of DL TBF pre--established and effectively used for the
transmission of a DL--UNITDATA received from the SGSN.
Event : DL TBF pre--established and used for the transmission of a
DL--UNITDATA.
Note : V 15 counter

411--9001--125
Nortel Confidential V15 Release counters 6--1
APPENDIX A V15 RELEASE COUNTERS

This appendix contains the changes (counters added or removed) between the different V15
releases:
changes between V15.1 and V15.1.1 (see Paragraph A.1)
changes between V15.1R and V15.1.1 (see Paragraph A.2)
changes between V15.0 and V15.1.1 (see Paragraph A.3)
changes between V15.0.1 and V15.1.1 (see Paragraph A.4)

6--2 V15 Release counters Nortel Confidential
A.1 Delta between V15.1 and V15.1.1

None (no counter added nor removed between V15.1 and 15.1.1).
A.2 Delta between V15.1R and V15.1.1
A.2.1 BSS counters added since V15.1R

In the leftmost column, “BSS releases” indicates whether a counter is available for a given
BSS or PCUSN release (e.g. “v12 v14 v15”)
BSS Releases Q3 Name Counter

Number
-- -- - v15 suspendRequest 2066 0
-- -- - v15 resumeSuccess 2067 0
-- -- - v15 resumeFailureAfterHOInterRA 2068 0
-- -- - v15 resumeFailureAfterHOInterBSC 2068 1
-- -- - v15 agprsSuspendRequestProcedures 2071 0
-- -- - v15 agprsSuspendRequestMessages 2071 1
-- -- - v15 agprsSuspendNack 2072 0
-- -- - v15 agprsResumeRequest 2073 0
-- -- - v15 agprsResumeNack 2074 0
-- -- - v15 tchHrAveragedUsedCellMoy /Max/Cum/Ech 1828 0
-- -- - v15 tchHrAveragedUsedWpsCellMoy /Max/Cum/Ech 1828 1
-- -- - v15 tchHrAveragedUsedNscCellMoy /Max/Cum/Ech 1829 0
-- -- - v15 amrFrTchStdAveragedUsedCellMoy /Max/Cum/Ech 1934 0
-- -- - v15 totalNumberOfEdgeTsCellMoy /Max/Cum/Ech 2002 0
-- -- - v15 allocatedEdgeTsCellMoy /Max/Cum/Ech 2002 1
-- -- - v15 preemptedEdgeTsCellMoy /Max/Cum/Ech 2002 2
-- -- - v15 allocatedAbisJokerTsCellMoy /Max/Cum/Ech 2003 0
-- -- - v15 amrHrModeDuration 1935 0
-- -- - v15 amrCellLoadStateModification 1936 0
-- -- - v15 amrFilteredBusyTchRatioMoy /Max/Cum/Ech 1937 0
-- -- - v15 amrCellLoadStateUnderevaluated 1938 0
-- -- - v15 amrCellLoadStateOverevaluated 1939 0

411--9001--125

Number
saicTchSuccessfullyAssigned 2096 0
-- -- v14 v15 pagingFilteredByBsc 1508 0
A.2.2 BSS counters removed since V15.1R

Number
v12 -- v14 v15 signallingReleaseBtsOverload 1163 29
v12 -- v14 -- tchHrAllocatedPrimoAllocation 1610 1
v12 -- v14 -- tchHrAllocatedOverflowAllocation 1610 2
v12 -- v14 -- tchHrAveragedUsedPrimoAllocationMoy 1612 1
/Max/Cum/Ech
v12 -- v14 -- tchHrAveragedUsedOverflowAllocationMoy 1612 2
/Max/Cum/Ech
v12 -- v14 -- tchHrAllocatedPrimoAllocationTrZone 1610 1
v12 -- v14 -- tchHrAllocatedOverflowAllocationTrZone 1610 2
v12 -- v14 -- tchHrAveragedUsedPrimoAllocationTrZoneMoy 1612 1
/Max/Cum/Ech
v12 -- v14 -- tchHrAveragedUsedOverflowAllocationTrZoneMoy 1612 2
/Max/Cum/Ech
v12 -- v14 -- channelActivationHscsd1Tch 1727 0
v12 -- v14 -- channelActivateTchFrDataTHscsd 1728 0
v12 -- v14 -- channelActivateTchFrDataNtHscsd 1729 0
v12 -- v14 -- cardSynthLoadBscbN [N = 0 to 11] 1835 0
Moy/Max/Cum/Ech
cardSynthLoadTscbN [N = 0 to 1]
Moy/Max/Cum/Ech
-- -- v14 v15 prLoadCne3OmuTmMoy /Max/Cum/Ech 3000 1
-- -- v14 v15 prLoadCne3TmuTmMoy /Max/Cum/Ech 3001 1


Number
- -- v14 v15 prLoadCne3CC1Moy /Max/Cum/Ech 3002 0
- - v14 v15 e3PrLoadSpmMoy /Max/Cum/Ech 3003 0
- - v14 v15 e3PrMemCnOmuSbcTmMoy /Max/Cum/Ech 3004 2
- - v14 v15 e3PrMemCnTmuTmMoy /Max/Cum/Ech 3005 1
- - v14 v15 e3PrMemSpmMoy /Max/Cum/Ech 3007 0
- - v14 v15 e3PcmG826EsMoy /Max/Cum/Ech 3009 0
- - v14 v15 e3PcmG826SesMoy /Max/Cum/Ech 3009 1
- - v14 v15 e3PcmG826BbeMoy /Max/Cum/Ech 3009 2
- - v14 v15 e3PcmG826UasMoy /Max/Cum/Ech 3009 3
- - v14 v15 e3AbisAccLevel1ErrorsCh1PcmNb 3100 0
- - v14 v15 e3AbisAccLevel1ErrorsCh1TsNb 3100 1
- - v14 v15 e3AbisAccLevel1ErrorsCh1Nefr 3100 2
- - v14 v15 e3AbisAccLevel1ErrorsCh1Ncrce 3100 3
- - v14 v15 e3AbisAccLevel1ErrorsCh1Nlfa 3100 4

411--9001--125

Number
-- -- v14 v15 e3AbisAccLevel1ErrorsCh5Nefr 3104 2
-- -- v14 v15 e3AbisAccLevel1ErrorsCh5Ncrce 3104 3
-- -- v14 v15 e3AbisAccLevel1ErrorsCh5Nlfa 3104 4
-- -- v14 v15 e3AbisAccLevel1ErrorsCh6PcmNb 3105 0
-- -- v14 v15 e3AbisAccLevel1ErrorsCh6TsNb 3105 1
-- -- v14 v15 e3prMemCnCC1Moy /Max/Cum/Ech 3006 0
v12 -- v14 v15 hoRequestIncomingInterBssTchCtm 1070 1
v12 -- v14 v15 speechAlgoFallBackCtm 1206 2
v12 -- v14 v15 assignRequestCtm 1841 2

A.3 Delta between V15.0 and V15.1.1
A.3.1 PCUSN counters added since V15.0

This table gives the list of mandatory spooled counters. Note that the counters in italic are
created at the PCUOAM or SDO level and are not provided by PCUSN.
Counters Function
15007/0 Number of octets discarded, because the number of received PDUs exceeds
the bucket size
15007/1 Cumulated size in bytes of all the GPRS RLC data blocks sent for the first
time (i.e. fresh block) on a pipe
15007/1 Cumulated time in multiple of 20ms where the MS is in GPRS DL data
transfer.
TO = Time of the first block sent in downlink for that mobile
T2 = Time of the PDAN which acknowledged all the downlink blocks
The counter is equal to T1--T0+1=T2-- T0--(RTD + RRBP)+1
15075/1 Cumulative number of Agprs timeslots allocated in the cell by the BSC.
This correspond to the formula: sum (dyAgprsNbTs). The value
dyAgprsNbTs is the number of Agprs TS allocated in the cell at the th
sample.
15075/1 Number of iteration samples for pcuDyAgprsNbTimeslotsCum.
15075/1 This counter is no more relevant at the PCU level; it is always set to 0.
15076/0 Cumulative value of Agprs load criterion for the related cell.
The average value is calculated since the last reset PCU.
15076/0 Number of iteration samples for pcuDyAgprsLoadCriterionCum.
15076/0 This counter is no more relevant at the PCU level; it is always set to 0.
15100/0 Number of iteration samples for pcuDyAgprsNbTimeslotsCum
15101/0 Cumulative number of EGPRS RLC data blocks received by the PCU on this
TDMA.
15102/0 Cumulative value of the 8PSK_BEP derived from the 8PSK_MEAN_BEP
received from a MS in this TDMA in the EGPRS BEP Link Quality
Measurements (8PSK_MEAN_BEP).
15102/0 Number of values of the 8PSK_MEAN_BEP received from a MS in this
TDMA in the EGPRS BEP Link Quality Measurements (8PSK_MEAN_BEP).
15103/0 Cumulative value of the GMSK_BEP derived from the
GMSK_MEAN_BEP received from a MS in this TDMA in
the EGPRS BEP Link Quality Measurements
(GMSK_MEAN_BEP).
15103/0 Number of values of the GMSK_MEAN_BEP received from a MS in this
TDMA in the EGPRS BEP Link Quality Measurements
(GMSK_MEAN_BEP).

411--9001--125
Counters Function
15104/0 Cumulated value of the assumed BEP received by the PCU in
each EGPRS RLC data block on this TDMA.
15104/0 Number of MEAN_BEP values received by the PCU in each EGPRS RLC
data block on this TDMA.
15105/0 Spare counter, 0 by default.
15110/0 Total number of TRAU EDGE data blocks sent on the Agprs Main channels in
the DL direction.
15111/0 Number of EGPRS TBF downgraded in GPRS.
15112/0 Accumulative size in octets of all the RLC EDGE data blocks received for the
first time on a pipe.
15113/0 Accumulated size in octets of all the RLC EDGE data blocks
sent for the first time on a pipe.
15118/0 Cumulative number of Agprs Joker TS allocated to the cell by the BSC.
15118/0 Minimum number of Agprs Joker TS allocated to the cell by the BSC.
15118/0 Maximum number of Agprs Joker TS allocated to the cell by the BSC.
15119/0 Number of iteration samples for pcuDyAgprsNbTimeslotsCum|Cumulative
number of TRAU data blocks sent to th Agprs Joker Channel
number of EGPRS TBF establishment requests.
number of times in multiples of 20ms where the pipes for UL EGPRS TBF
are in “verbose” state.
15124/0 Number of iteration samples for pcuDyAgprsNbTimeslotsCum|Accumulative
times in multiples of 20ms where the pipes for DL EGPRS TBF are in
“verbose” state.

Counters Function
15127/0 Number of iteration samples for pcuDyAgprsNbTimeslotsCum|Total number
of TRAU EDGE data blocks sent on the Agprs Main channels in the UL
direction.
15128/0 Number of iteration samples for pcuDyAgprsNbTimeslotsCum|Total number
of TRAU EDGE data blocks sent on the Agprs Joker channels in the UL
direction.
15129/0 Number of period of 20ms when there were missing Agprs Jokers TS in the
DL direction to reach the MCS targeted by the Link Adaptation.
15129/0 Number of Missing Agprs Jokers TS in the DL direction to reach the MCS
targeted by the Link adaptation.
number of EDGE RLC Data Blocks transmitted in MCS2 by PCU in the DL
direction.
direction.
direction.
direction.
direction.
direction.
direction.
direction.
direction.
direction.

411--9001--125
Counters Function
direction.
direction.
direction.
direction.
15152/0 Number of 1/2 EDGE radio data blocks that are commanded by the Link
Adaptation in MCS2 AND sent in MCS2 by PCU in the DL direction.
15153/0 Number of 1/2 EDGE radio data blocks that are commanded by the Link
Adaptation in MCS3 AND sent in MCS3 by PCU in the DL direction.
direction.
direction.
direction.
direction.
direction.
number of EDGE RLC Data Blocks that are transmitted in MCS2 by MS in
the UL direction.
the UL direction.
the UL direction.

Counters Function
number of EDGE RLC Data Blocks transmitted in MCS6 by MS in the UL
direction.
direction.
15168/0 Number of iteration samples for pcuDyAgprsNbTimeslotsCum
Cumulative number of EDGE RLC Data Blocks transmitted in MCS8 by MS
direction.
15172/0 Number of 1/2 EDGE radio data blocks that were commanded by the Link
Adaptation in MCS2 AND sent in MCS2 by MS in the UL direction AND badly
received by BTS.
received by BTS.
received by BTS.
received by BTS.
received by BTS.
received by BTS.
received by BTS.
direction.
direction.
direction.

411--9001--125
Counters Function
direction.
direction.
direction.
direction.
number of “one phase Channel Request” received at the PCU level.
number of “Immediate Assignment Uplink” messages sent by the PCU to
establish a one phase access UL TBF in this cell.
number of failures of the contention resolution procedure in case of one
phase access.
15193/0 Cumulated size in bytes of all the RLC GPRS data blocks received for the
first time (i.e. fresh block) on a pipe.
15193/0 Cumulated time in multiples of 20ms where the MS is in GPRS UL data
transfer.
15194/0 Cumulative number of times a throughput equal or greater than 22 kbps is
reached in uplink direction by a MS in the cell.
15195/0 Cumulative number of DL TBF pre--established and effectively used for the
transmission of a DL--UNIDATA received from the SGSN.

A.3.2 BSS counters added since V15.0


Number
-- -- - v15 aintOverLoadRejectedOpPerformLocationReq 1506 4
-- -- - v15 e3OverloadRejectedOpSmsCb 1507 5
-- -- - v15 cgOverloadRejectedOpSmsCbCg0 /1/2 1803 5
-- -- - v15 allocatedCircuitTsCellMoy /Max/Cum/Ech 1821 0
-- -- - v15 allocatedPacketTsCellMoy /Max/Cum/Ech 1822 0
-- -- - v15 totalNumberOfPacketTsCellMoy /Max/Cum/Ech 1822 1
-- -- - v15 totalNumberOfPacketTsUsedForCircuitCellMoy 1822 2
/Max/Cum/Ech
-- -- - v15 allTchFrAllocatedTimeCellMoy /Max/Cum/Ech 1823 0
-- -- - v15 tchFrAveragedUsedTchAllocationCellMoy 1824 0
/Max/Cum/Ech
-- -- - v15 tchFrAveragedUsedPrimoAllocationCellMoy 1824 1
/Max/Cum/Ech
-- -- - v15 tchFrAveragedUsedOverflowAllocationCellMoy 1824 2
/Max/Cum/Ech
-- -- - v15 tchFrAveragedUsedWpsCellMoy /Max/Cum/Ech 1824 3
-- -- - v15 tchFrAveragedAvailableCellMoy /Max/Cum/Ech 1825 0
-- -- - v15 tchFrAveragedUsedCellMoy /Max/Cum/Ech 1826 0
-- -- - v15 tchFrAverageConfiguratedCellMoy /Max/Cum/Ech 1827 0
-- -- - v15 suspendRequest 2066 0
-- -- - v15 resumeSuccess 2067 0
-- -- - v15 resumeFailureAfterHOInterRA 2068 0
-- -- - v15 resumeFailureAfterHOInterBSC 2068 1
-- -- - v15 agprsSuspendRequestProcedures 2071 0
-- -- - v15 agprsSuspendRequestMessages 2071 1
-- -- - v15 agprsSuspendNack 2072 0
-- -- - v15 agprsResumeRequest 2073 0

411--9001--125

Number
- - - v15 tchHrAveragedUsedWpsCellMoy /Max/Cum/Ech 1828 1
- - - v15 tchHrAveragedUsedNscCellMoy /Max/Cum/Ech 1829 0
- - - v15 amrFrTchStdAveragedUsedCellMoy /Max/Cum/Ech 1934 0
- - - v15 totalNumberOfEdgeTsCellMoy /Max/Cum/Ech 2002 0
- - - v15 allocatedEdgeTsCellMoy /Max/Cum/Ech 2002 1
- - - v15 preemptedEdgeTsCellMoy /Max/Cum/Ech 2002 2
- - - v15 allocatedAbisJokerTsCellMoy /Max/Cum/Ech 2003 0
- - - v15 amrHrModeDuration 1935 0
- - - v15 amrCellLoadStateModification 1936 0
- - - v15 amrFilteredBusyTchRatioMoy /Max/Cum/Ech 1937 0
- - - v15 amrCellLoadStateUnderevaluated 1938 0
- - - v15 amrCellLoadStateOverevaluated 1939 0
-- -- v14 v15 pagingFilteredByBsc 1508 0

A.3.3 BSS counters removed since V15.0

Number
v12 -- v14 v15 signallingReleaseBtsOverload 1163 29
v12 -- v14 -- tchHrAveragedUsedPrimoAllocationMoy 1612 1
/Max/Cum/Ech
v12 -- v14 -- tchHrAveragedUsedOverflowAllocationMoy 1612 2
/Max/Cum/Ech
v12 -- v14 -- tchHrAveragedUsedPrimoAllocationTrZoneMoy 1612 1
/Max/Cum/Ech
v12 -- v14 -- tchHrAveragedUsedOverflowAllocationTrZoneMoy 1612 2
/Max/Cum/Ech
v12 -- v14 -- channelActivateTchFrDataTHscsd 1728 0
v12 -- v14 -- channelActivateTchFrDataNtHscsd 1729 0
v12 -- v14 -- cardSynthLoadBscbN [N = 0 to 11] 1835 0
Moy/Max/Cum/Ech
cardSynthLoadTscbN [N = 0 to 1]
Moy/Max/Cum/Ech
- -- v14 v15 prLoadCne3OmuTmMoy /Max/Cum/Ech 3000 1
- - v14 v15 prLoadCne3TmuTmMoy /Max/Cum/Ech 3001 1
- -- v14 v15 prLoadCne3CC1Moy /Max/Cum/Ech 3002 0
- - v14 v15 e3PrLoadSpmMoy /Max/Cum/Ech 3003 0
- - v14 v15 e3PrMemCnOmuSbcTmMoy /Max/Cum/Ech 3004 2
- - v14 v15 e3PrMemCnTmuTmMoy /Max/Cum/Ech 3005 1
- - v14 v15 e3PrMemSpmMoy /Max/Cum/Ech 3007 0
- - v14 v15 e3PcmG826EsMoy /Max/Cum/Ech 3009 0

411--9001--125

Number
-- -- v14 v15 e3PcmG826SesMoy /Max/Cum/Ech 3009 1
-- -- v14 v15 e3PcmG826BbeMoy /Max/Cum/Ech 3009 2
-- -- v14 v15 e3PcmG826UasMoy /Max/Cum/Ech 3009 3


Number
- - v14 v15 e3prMemCnCC1Moy /Max/Cum/Ech 3006 0

411--9001--125
A.4 Delta between V15.0.1 and V15.1.1
A.4.1 BSS counters added since V15.0.1


Number
- - - v15 aintOverLoadRejectedOpPerformLocationReq 1506 4
- - - v15 e3OverloadRejectedOpSmsCb 1507 5
- - - v15 cgOverloadRejectedOpSmsCbCg0 /1/2 1803 5
- - - v15 allocatedCircuitTsCellMoy /Max/Cum/Ech 1821 0
- - - v15 allocatedPacketTsCellMoy /Max/Cum/Ech 1822 0
- - - v15 totalNumberOfPacketTsCellMoy /Max/Cum/Ech 1822 1
- - - v15 totalNumberOfPacketTsUsedForCircuitCellMoy 1822 2
/Max/Cum/Ech
- - - v15 allTchFrAllocatedTimeCellMoy /Max/Cum/Ech 1823 0
- - - v15 tchFrAveragedUsedTchAllocationCellMoy 1824 0
/Max/Cum/Ech
- - - v15 tchFrAveragedUsedPrimoAllocationCellMoy 1824 1
/Max/Cum/Ech
- - - v15 tchFrAveragedUsedOverflowAllocationCellMoy 1824 2
/Max/Cum/Ech
- - - v15 tchFrAveragedUsedWpsCellMoy /Max/Cum/Ech 1824 3
- - - v15 tchFrAveragedAvailableCellMoy /Max/Cum/Ech 1825 0
- - - v15 tchFrAveragedUsedCellMoy /Max/Cum/Ech 1826 0
- - - v15 tchFrAverageConfiguratedCellMoy /Max/Cum/Ech 1827 0
- - - v15 suspendRequest 2066 0
- - - v15 resumeSuccess 2067 0
- - - v15 resumeFailureAfterHOInterRA 2068 0
- - - v15 resumeFailureAfterHOInterBSC 2068 1
- - - v15 agprsSuspendRequestProcedures 2071 0
- - - v15 agprsSuspendRequestMessages 2071 1
- - - v15 agprsSuspendNack 2072 0
- - - v15 agprsResumeRequest 2073 0


Number
-- -- - v15 tchHrAveragedUsedWpsCellMoy /Max/Cum/Ech 1828 1
-- -- - v15 tchHrAveragedUsedNscCellMoy /Max/Cum/Ech 1829 0
-- -- - v15 amrFrTchStdAveragedUsedCellMoy /Max/Cum/Ech 1934 0
-- -- - v15 totalNumberOfEdgeTsCellMoy /Max/Cum/Ech 2002 0
-- -- - v15 allocatedEdgeTsCellMoy /Max/Cum/Ech 2002 1
-- -- - v15 preemptedEdgeTsCellMoy /Max/Cum/Ech 2002 2
-- -- - v15 allocatedAbisJokerTsCellMoy /Max/Cum/Ech 2003 0
-- -- - v15 amrHrModeDuration 1935 0
-- -- - v15 amrCellLoadStateModification 1936 0
-- -- - v15 amrFilteredBusyTchRatioMoy /Max/Cum/Ech 1937 0
-- -- - v15 amrCellLoadStateUnderevaluated 1938 0
-- -- - v15 amrCellLoadStateOverevaluated 1939 0
- - v14 v15 pagingFilteredByBsc 1508 0

411--9001--125
A.4.2 BSS counters removed since V15.0.1

Number
-- -- v14 v15 e3PcmG826EsMoy /Max/Cum/Ech 3009 0
-- -- v14 v15 e3PcmG826SesMoy /Max/Cum/Ech 3009 1
-- -- v14 v15 e3PcmG826BbeMoy /Max/Cum/Ech 3009 2
-- -- v14 v15 e3PcmG826UasMoy /Max/Cum/Ech 3009 3


Number
- - v14 v15 e3prMemCnCC1Moy /Max/Cum/Ech 3006 0

411--9001--125
Nortel Confidential Index i
A
abisCongestionTimeMoy/Max/Cum/Ech, 5--472
abisInputIByte, 5--466
abisInputIFrame, 5--465
abisInputUiByte, 5--465
abisInputUiFrame, 5--464
abisLevel1ErrorsBadFrame, 5--7
abisLevel1ErrorsCrcError, 5--7
abisLevel1ErrorsLostAlign, 5--8
abisLevel2ErrorBadLg, 5--471
abisLevel2ErrorBadRxNr, 5--469
abisLevel2ErrorReqOutState, 5--469
abisLevel2ErrorRxDm0, 5--468
abisLevel2ErrorRxDm1, 5--466
abisLevel2ErrorRxFrmr, 5--470
abisLevel2ErrorRxNoImpl, 5--470
abisLevel2ErrorRxSabme, 5--468
abisLevel2ErrorRxSup1, 5--466
abisLevel2ErrorRxUa0, 5--467
abisLevel2ErrorRxUa1, 5--467
abisLevel2ErrorTxNDisc, 5--469
abisLevel2ErrorTxNSabme, 5--468
abisOutputIByte, 5--465
abisOutputIFrame, 5--464
abisOutputUiByte, 5--465
abisOutputUiFrame, 5--464
abisTrauFrameCorrected, 5--342
abisTrauFrameDlReceived, 5--342
abisTrauFrameMuted, 5--343
abisUnavailabilityTimeCum, 5--471
abisUnavailabilityTimeEch, 5--471
abisUnavailabilityTimeMax, 5--471
abisUnavailabilityTimeMoy, 5--471
ackDnTbfEstablishment, 5--637
agprsResumeNack, 5--45
agprsResumeRequest, 5--45
agprsSuspendNack, 5--44
agprsSuspendRequestMessages, 5--43
agprsSuspendRequestProcedures, 5--43

ii Index Nortel Confidential
aInputMessage, raw permanent, 5--137

aintOverloadRejectedOpIncomingExtHoReq, 5--269
aintOverloadRejectedOpPageReq, 5--268
aintOverLoadRejectedOpPerformLocationReq, 5--270
aintOverloadRejectedOpVbsVgcsAssignment, 5--270
aintOverLoadRejectedOpVbsVgcsSetup, 5--269
alarmAmrHrToFrDownHoRequiredTch, 5--76
alarmAmrHrToFrUpHoRequiredTch, 5--76
allEstabIndicSignalling, 5--482
allocatedAbisJokerTsCellMoyMoy/Max/Cum/Ech, 5--42
allocatedAbisJokerTSEdgeMoy/Max/Cum/Ech, 5--40
allocatedAbisJokerTSEdgeTrZoneMoy/Max/Cum/Ech, 5--40
allocatedCircuitTsMoy/Max/Cum/Ech, 5--408
allocatedCircuitTsCellMoy/Max/Cum/Ech, 5--413
allocatedCircuitTsTrZoneMoy/Max/Cum/Ech, 5--408
allocatedEdgeTsMoy/Max/Cum/Ech, 5--39
allocatedEdgeTsCellMoy/Max/Cum/Ech, 5--41
allocatedEdgeTsTrZoneMoy/Max/Cum/Ech, 5--39
allocatedPacketsTsTrZoneMoy/Max/Cum/Ech, 5--409
allocatedPacketTsMoy/Max/Cum/Ech, 5--409
allocatedPacketTsCellMoy/Max/Cum/Ech, 5--413
allocatedPacketTsTrZoneMoy/Max/Cum/Ech, 5--410
allocationFailureTchFrSeizureInclHo, 5--486
allSdcchAllocatedTimeMoy/Max/Cum/Ech, 5--119
allSdcchAllocatedTimeTrZoneMoy/Max/Cum/Ech, 5--119
allSdcchinseconds, 5--521
allSdcchinsecondsCum, 5--521
allSdcchinsecondsEch, 5--521
allSdcchinsecondsMax, 5--521
allSdcchinsecondsMoy, 5--521
allTchFrAllocatedTimeCellMoy/Max/Cum/Ech, 5--415
allTchFrAllocatedTimeMoy/Max/Cum/Ech, 5--118
allTchFrAllocatedTimeTrZoneMoy/Max/Cum/Ech, 5--118
allTchinsecondsCum, 5--520
allTchinsecondsEch, 5--520
allTchinsecondsMax, 5--520
allTchinsecondsMoy, 5--520
aMessageErroneousRate, 5--509
aMessageErrors, 5--140
amrCellLoadStateModification, 5--72

411--9001--125
Nortel Confidential Index iii
amrCellLoadStateOverevaluated, 5--73
amrCellLoadStateUnderevaluated, 5--73
amrDownlinkNoDataFrames, 5--98
amrFilteredBusyTchRatioMoy/Max/Cum/Ech, 5--72
amrFrBadSpeechFramesCodec102, 5--94
amrFrBadSpeechFramesCodec102TrZone, 5--94
amrFrDownlinkCodec102, 5--92
amrFrDownlinkCodec102TrZone, 5--92
amrFrHoExecutionIntraCellTch, 5--80
amrFrHoRequestIntraCellTch, 5--79
amrFrHoRequestOutgoingTch, 5--78
amrFrHoSuccessIntraCellTch, 5--81
amrFrHoSuccessOutgoingTch, 5--37
amrFrSpeechAlgoFallBack, 5--32
amrFrTchAllocated, 5--56
amrFrTchAllocatedTrZone, 5--56
amrFrTchAssignFailure, 5--58
amrFrTchConnectionDurationMoy/Max/Cum/Ech, 5--57
amrFrTchConnectionDurationTrZoneMoy/Max/Cum/Ech, 5--57
amrFrTchStdAveragedUsedMoy/Max/Cum/Ech, 5--56
amrFrTchStdAveragedUsedCellMoy/Max/Cum/Ech, 5--71
amrFrTchStdAveragedUsedTrZoneMoy/Max/Cum/Ech, 5--56
amrFrTchSuccessfullyAssigned, 5--58
amrFrToHrHoExecutionIntraCellTch, 5--80
amrFrToHrHoRequestIntraCellTch, 5--79
amrFrToHrHoSuccessIntraCellTch, 5--81
amrFrUplinkCodec102, 5--89
amrFrUplinkCodec102TrZone, 5--89

iv Index Nortel Confidential
amrFrValidSpeechFramesCodec102, 5--96
amrFrValidSpeechFramesCodec102TrZone, 5--96
amrHrBadSpeechFramesCodec475, 5--96
amrHrBadSpeechFramesCodec475TrZone, 5--96
amrHrDownlinkCodec475, 5--92
amrHrDownlinkCodec475TrZone, 5--92
amrHrHoRequestOutgoingTch, 5--78
amrHrHoSuccessOutgoingTch, 5--37
amrHrModeDuration, 5--71
amrHrTchAssignFailure, 5--59
amrHrTchConnectionDurationMoy/Max/Cum/Ech, 5--57
amrHrTchConnectionDurationTrZoneMoy/Max/Cum/Ech, 5--57
amrHrTchSuccessfullyAssigned, 5--58
amrHrToFrHoExecutionIntraCellTch, 5--80
amrHrToFrHoRequestIntraCellTch, 5--79
amrHrToFrHoSuccessIntraCellTch, 5--81
amrHrUplinkCodec475, 5--89
amrHrUplinkCodec475TrZone, 5--89

411--9001--125
Nortel Confidential Index v
amrHrValidSpeechFramesCodec475, 5--97
amrHrValidSpeechFramesCodec475TrZone, 5--97
amrQualityFrDownHoRequiredTch, 5--75
amrQualityFrUpHoRequiredTch, 5--74
amrQualityHrDownHoRequiredTch, 5--77
amrQualityHrUpHoRequiredTch, 5--77
amrReversalPhaseFailure, 5--102
amrUplinkNoDataFrames, 5--98
aNonTransparentDown, 5--266
aNonTransparentUp, 5--265
aOutputMessage, raw permanent, 5--138
asciCallInitiationVbs, 5--345
asciCallInitiationVgcs, 5--346
asciInbandNotification, 5--347
asciInbandPaging, 5--346
asciPreemptionPerformed, 5--347
asciTalkerHandoverVbs, 5--396
asciTalkerHandoverVgcs, 5--396
assignFailure, 5--117
assignRequestAintOthers, 5--434
assignRequestAintSdcchToTchChannel, 5--434
assignRequestOthers, 5--433
assignRequestSdcchToTchChannel, 5--432
assignToOtherBandOrZone, 5--395, 5--457, 5--458
aTransparentDown, 5--264
aTransparentUp, 5--263
attemptedTchFrSeizureInclHo, 5--486
attemptedTchFrSeizureNotInclHo, 5--485
attemptedTchFrSeizures, 5--116
attemptedTchFrSeizures8W, 5--445
attemptedTchFrSeizuresMsDualb, 5--340
averageDLRxLev, 5--516
averageDLRxQual, 5--517
averageULRxLev, 5--517

vi Index Nortel Confidential
averageULRxQual, 5--518
B
bscAllocationFailureTchFrSeizureInclHo, 5--519
bscAttemptedTchFrSeizureInclHo, 5--519
bscAttemptedTchFrSeizureNotInclHo, 5--519
bscClearRequestTraffic, 5--520
bscHoExecutionIncomingSdcch, 5--530, 5--531
bscOtherThanPaging, 5--513
bscPagingResponse, synthetic permanent, 5--512
bscSdcchAllocated, 5--515
bscSdcchAveragedUsedMax, synthetic permanent bsc, 5--510
bscSdcchAveragedUsedMoy, synthetic permanent bsc, 5--510
bscTchFrAllocatedOverflowAllocation, 5--515
bscTchFrAllocatedPrimoAllocation, 5--515
bscTchFrAllocatedTchAllocation, 5--516
bscTchFrAveragedUsedOverflowAllocationMoy, 5--511
bscTchFrAveragedUsedPrimoAllocationMoy, 5--511
bscTchFrAveragedUsedTchAllocationMoy, 5--512
bsPowerDecControl, 5--402
bsPowerDecControlAmrFr, 5--64
bsPowerDecControlAmrHr, 5--68
bsPowerIncControl, 5--401
bsPowerIncControlAmrFr, 5--63
bsPowerIncControlAmrHr, 5--68
btsOverloadDuration, 5--340
burstToTransmit, 5--38
bvcFlowControlRequests, 5--581
C
callDropTrafficRatio, 5--523
capacityFrToHrHoRequiredTch, 5--75
capacityHoFiltered, 5--71
cardSynthLoadCpue0Moy/Max/Cum/Ech, 5--27
cardSynthLoadCpumMoy/Max/Cum/Ech, 5--27
cardSynthLoadSicdxMoy/Max/Cum/Ech, 5--27

411--9001--125
Nortel Confidential Index vii
cellLoadTch, 5--531
cellSdcchResourceFailureRatio, 5--522
cellTchResourceFailureRatio, 5--522
cgOverloadRejectedOpChannelReqCg0/1/2, 5--22
cgOverloadRejectedOpEstablishIndCg0/1/2, 5--23
cgOverloadRejectedOpPageReqBtsCg0/1/2, 5--25
cgOverloadRejectedOpPageReqCg0/1/2, 5--21
cgOverloadRejectedOpHoReqCg0/1/2, 5--24
chainStandbyResponse, 5--12
chainStandbyUpdate, 5--12
channelActivateSignallingFullRate, 5--316
channelActivateSpeechAmrFr, 5--55
channelActivateSpeechAmrHr, 5--54
channelActivateSpeechEnhancedFullRate, 5--254
channelActivateSpeechFullRate, 5--253
channelActivateTchFrDataNT12000, 5--335
channelActivateTchFrDataT1200, 5--324
channelActivateTchHrDataNT6000, 5--337
channelActivateTchHrDataT16, 5--329
channelActivateTchHrDataT2400, 5--332
ChannelActivateTchHrDataT4800, 5--333
channelActivateTchHrDataT600, 5--330, 5--331
channelActTchFrDataNT, 5--338
channelActTchFrDataT, 5--337
channelActTchHrDataNT, 5--339
channelActTchHrDataT, 5--338
channelAveragedIdlePerInterfBand0, 5--301
channelIdleLevelCum, 5--461

viii Index Nortel Confidential
channelIdleLevelEch, 5--461
channelIdleLevelMax, 5--461
channelIdleLevelMoy, 5--461
channelRequest, 5--353
channelRequestCause000, 5--234
channelRequestCcch, 5--619
channelRequestExtended, 5--321
CIUplinkAmrFr, 5--64
CIUplinkAmrFrTrZone, 5--64
CIUplinkAmrHr, 5--69
CIUplinkAmrHrTrZone, 5--69
CIUplinkFr, 5--59
CIUplinkFrTrZone, 5--59
clearRequestTraffic, 5--486
cmDatabaseUsed, 5--546
cmDatabaseUsedCum, 5--546
cmDatabaseUsedEch, 5--546
cmLogUsed, 5--547
cmLogUsedCum, 5--547
cmLogUsedEch, 5--547
connectionDurationSdcch, 5--274
connectionDurationSdcchTrZoneCum, 5--276
connectionDurationSdcchTrZoneEch, 5--276
connectionDurationSdcchTrZoneMax, 5--276
connectionDurationSdcchTrZoneMoy, 5--276
connectionDurationTchTrZoneCum, 5--271
connectionDurationTchTrZoneEch, 5--271
connectionDurationTchTrZoneMax, 5--271
connectionDurationTchTrZoneMoy, 5--271
controlBlocksDn, 5--605
controlBlocksUp, 5--604
cpue0LoadRatio, 5--528
cpue1LoadRatio, 5--528

411--9001--125
Nortel Confidential Index ix
cpuPBlockUtilAvg, 5--623
cpuPBlockUtilMax, 5--624
cpuUtilAvg, 5--624
cpuUtilAvgMax, 5--625
cpuUtilAvgMin, 5--625
csPaging, 5--632
CsPagingOnCcch, 5--583
CsPagingOnPACCH, 5--584
configuredTimeslots, 5--600
cumulativeDnRxLev, 5--600
cumulativeDnRxQual, 5--608
cumulativeTimeDnTbf, 5--599
cumulativeTimeUpTbf, 5--598
cumulativeUpActiveTimeslots, 5--600
cumulativeUpRxLev, 5--609
cumulativeUpRxQual, 5--608
D
dataBlocksDn, 5--603
dataBlocksUp, 5--602
dataNtRateFbTcbConfNotAllowed, 5--233
dataNtRateFbTcbResLack, 5--233
dataNtRateFbTchConfNotAllowed, 5--348
dataNtRateFbTchResLack, 5--348
decAmrFrDownModif, 5--100
decAmrFrDownModifTrZone, 5--100
decAmrFrUpModif, 5--99
decAmrFrUpModifTrZone, 5--99
decAmrHrDownModif, 5--102
decAmrHrDownModifTrZone, 5--102
decAmrHrUpModif, 5--101
decAmrHrUpModifTrZone, 5--101
deleteIndication, 5--399
directedRetryUnsuccessNoBts, 5--305
dlMutedAbisTrauFrameRate, 5--518
dnMultiSlotAllocations1, 5--593

x Index Nortel Confidential
dnMultiSlotRequest1, 5--590
dnPipeBetween11and22kbps, 5--618
dnPipebetween22and33kbps, 5--619
dnPipeGreater33kbps, 5--620
dnPipeLess11kbps, 5--622
dnTbfBronzeRejectedForMinTput, 5--642
dnTbfBronzeSatisfactBet5090pCent, 5--642
dnTbfBronzeSatisfactLess50pCent, 5--642
dnTbfBronzeSatisfactMore90pCent, 5--641
dnTbfGoldRejectedForMinTput, 5--639
dnTbfGoldSatisfactBet5090pCent, 5--639
dnTbfGoldSatisfactLess50pCent, 5--639
dnTbfGoldSatisfactMore90pCent, 5--638
dnTbfImmediateAssignment, 5--618
dnTbfReleases, 5--598
dnTbfSilverRejectedForMinTput, 5--641
dnTbfSilverSatisfactBet5090pCent, 5--640
dnTbfSilverSatisfactLess50pCent, 5--640
dnTbfSilverSatisfactMore90pCent, 5--640
downgradedL1mModeOnClassmark, 5--444
downlinkPowerCtrlMaxSdcchCum, 5--272
downlinkPowerCtrlMaxSdcchEch, 5--272
downlinkPowerCtrlMaxSdcchMax, 5--272
downlinkPowerCtrlMaxSdcchMoy, 5--272
downlinkPowerCtrlMaxTchMoy/Max/Cum/Ech, 5--255
downlinkPowerCtrlMaxTchAmrFrMoy/Max/Cum/Ech, 5--60
downlinkPowerCtrlMaxTchAmrHrMoy/Max/Cum/Ech, 5--65
dyAgprsAvgLoadCriterionCum, 5--636
dyAgprsMaxLoadCriterion, 5--638
dyAgprsMaxNbTimeslots, 5--636
dyAgprsMinNbTimeslots, 5--635
dyAgprsNbModif, 5--633
E
e3OverloadRejectedOpChannelReq, 5--33
e3OverloadRejectedOpEstablishInd, 5--33

411--9001--125
Nortel Confidential Index xi
e3OverloadRejectedOpHoReq, 5--34
e3OverloadRejectedOpPagingReq, 5--33
e3OverloadRejectedOpPagingReqReject, 5--34
e3OverloadRejectedOpSmsCb, 5--35
e3PrDiskCnOmuLdRMoy/Max/Cum/Ech, 5--51
e3PrDiskCnOmuLdWMoy/Max/Cum/Ech, 5--51
e3PrDiskCnOmuMdRMoy/Max/Cum/Ech, 5--53
e3PrDiskCnOmuMdWMoy/Max/Cum/Ecch, 5--52
e3PrMemCnOmuSbcMemMoy/Max/Cum/Ech, 5--48
e3PrMemCnOmuSbcSwapMoy/Max/Cum/Ech, 5--49
e3PrMemCnTmuPmcMoy/Max/Cum/Ech, 5--50
e3PrMemCnTmuSbcMoy/Max/Cum/Ech, 5--49
ecuActivation, 5--344
estabIndicSignalling, 5--354
estabIndicSignallingEmergency, 5--249
estabIndicSignallingEmergency8W, 5--452
estabIndicSignallingEmergency8w, 5--354
estabIndicSignallingImsiDetach, 5--248
estabIndicSignallingLocUpdate, 5--246
estabIndicSignallingMoc, 5--248
estabIndicSignallingPagingRes, 5--245
estabIndicSignallingPiggybacked, 5--354
estabIndicSignallingReEstab, 5--247
estabIndicSignallingShortMsg, 5--250
estabIndicSignallingSuppService, 5--251
estabIndicSigPhase1, 5--252
estabIndicSigPhase2, 5--253
estabIndicSigPhase28W, 5--452
F
faultyTrxNoBcch, 5--529
fmDatabaseUsed, 5--547
fmDatabaseUsedCum, 5--547
fmDatabaseUsedEch, 5--547
fmLogUsed, 5--547
fmLogUsedCum, 5--547
fmLogUsedEch, 5--547
ftamFtiDelete, 5--565
ftamFtiDeleteConf, 5--565

xii Index Nortel Confidential
ftamFtiDir, 5--565
ftamFtiDirConf, 5--565
ftamFtiGet, 5--564
ftamFtiGetConf, 5--564
ftamFtiPut, 5--564
ftamFtiPutConf, 5--564
ftamFtiRename, 5--566
ftamFtiRenameConf, 5--566
fullDuplexTbfEstablishment, 5--595
G
gprsImmAssRejectedSicd, 5--9
gprsPagingRejectedSicd, 5--10
gprsPreemption, 5--412
gprsPreemptionNack, 5--412
gprsRachRejectedSicd, 5--8
H
hoBtsRejected, 5--383
hoExecutionIncoming, 5--530
hoExecutionIncomingInterBss, raw permanent, 5--124
hoExecutionIncomingInterBssSdcch, raw permanent, 5--164
hoExecutionIncomingIntraBss, raw permanent, 5--124
hoExecutionIncomingIntraBssSdcch, raw permanent, 5--163
hoExecutionIncomingIntraBssTchMsDualb, 5--392
hoExecutionIncomingSdcch, 5--530
hoExecutionIntraBts, raw permanent, 5--129
hoExecutionIntraBtsMsDualb, 5--394
hoExecutionIntraBtsSdcch, raw permanent, 5--168
hoExecutionOutgoing, 5--529
hoExecutionOutgoingEbandEbandMsDualb, 5--390
hoExecutionOutgoingEbandMbandMsDualb, 5--391
hoExecutionOutgoingInterBss, raw permanent, 5--120
hoExecutionOutgoingInterBssForDirectedRetry, raw permanent, 5--30
hoExecutionOutgoingInterBssSdcch, raw permanent, 5--161
hoExecutionOutgoingIntraBss, raw permanent, 5--120
hoExecutionOutgoingIntraBssForDirectedRetry, raw permanent, 5--29
hoExecutionOutgoingIntraBssSdcch, raw permanent, 5--160

411--9001--125
Nortel Confidential Index xiii
hoExecutionOutgoingMbandEbandMsDualb, 5--388
hoExecutionOutgoingMbandMbandMsDualb, 5--389
hoExecutionOutgoingSdcch, 5--529
hoFailureIncomingInterBssSdcchChannelActivateNack, 5--365
hoFailureIncomingInterBssSdcchHoNotAllowed, 5--365
hoFailureIncomingInterBssSdcchRadioLack, 5--364
hoFailureIncomingInterBssSdcchTchnAckTimerExp, 5--366
hoFailureIncomingInterBssSdcchTerrestLack, 5--365
hoFailureIncomingInterBssTchChannelActivateNack, 5--363
hoFailureIncomingInterBssTchCICIncompatible, 5--364
hoFailureIncomingInterBssTchHoNotAllowed, 5--363
hoFailureIncomingInterBssTchRadioLack, 5--362
hoFailureIncomingInterBssTchTchnAckTimerExp, 5--363
hoFailureIncomingInterBssTchTerrestLack, 5--362
hoFailureIncomingIntraBssSdcchChannelActivateNack, 5--361
hoFailureIncomingIntraBssSdcchHoNotAllowed, 5--361
hoFailureIncomingIntraBssSdcchRadioLack, 5--360
hoFailureIncomingIntraBssSdcchTchnAckTimerExp, 5--362
hoFailureIncomingIntraBssTchChannelActivateNack, 5--359
hoFailureIncomingIntraBssTchHoNotAllowed, 5--359
hoFailureIncomingIntraBssTchIncompatible, 5--360
hoFailureIncomingIntraBssTchRadioLack, 5--359
hoFailureIncomingIntraBssTchTchnAckTimerExp, 5--360
hoFailureIntraBtsSdcchChannelActivateNack, 5--358
hoFailureIntraBtsSdcchRadioLack, 5--358
hoFailureIntraBtsSdcchTchnAckTimerExp, 5--358
hoFailureIntraBtsTchChannelActivateNack, 5--357
hoFailureIntraBtsTchRadioLack, 5--357
hoFailureIntraBtsTchTchnAckTimerExp, 5--357
hoFailureOutgoingInterBssSdcchHoNotAllowed, 5--373
hoFailureOutgoingInterBssSdcchOtherCases, 5--373
hoFailureOutgoingInterBssSdcchRadioLack, 5--372
hoFailureOutgoingInterBssSdcchT7TimerExp, 5--373
hoFailureOutgoingInterBssSdcchTerrestLack, 5--372
hoFailureOutgoingInterBssTchHoNotAllowed, 5--370
hoFailureOutgoingInterBssTchIncompatible, 5--371
hoFailureOutgoingInterBssTchOtherCases, 5--371
hoFailureOutgoingInterBssTchRadioLack, 5--370
hoFailureOutgoingInterBssTchT7TimerExp, 5--371
hoFailureOutgoingInterBssTchTerrestLack, 5--370

xiv Index Nortel Confidential
hoFailureOutgoingIntraBssSdcchChannelActivateNack, 5--369
hoFailureOutgoingIntraBssSdcchHoNotAllowed, 5--369
hoFailureOutgoingIntraBssSdcchRadioLack, 5--368
hoFailureOutgoingIntraBssSdcchTchnAckTimerExp, 5--369
hoFailureOutgoingIntraBssTchChannelActivateNack, 5--367
hoFailureOutgoingIntraBssTchHoNotAllowed, 5--366
hoFailureOutgoingIntraBssTchIncompatible, 5--368
hoFailureOutgoingIntraBssTchRadioLack, 5--366
hoFailureOutgoingIntraBssTchTchnAckTimerExp, 5--367
hoFailureTieringTchNorrLargeToSmallPattern, 5--397
hoFailureTieringTchNorrSmallToLargePattern, 5--397
hoIndicationNotTreatedTchoke, 5--230
hoInExecutionBscSdcch, 5--514
hoInExecutionBscTch, 5--514
hoInInterSdcchExecutionBscFailRate, 5--505
hoInInterSdcchSelectionBscFailRate, 5--504
hoInInterTchExecutionBscFailRate, 5--505
hoInInterTchSelectionBscFailRate, 5--504
hoInIntraSdcchExecutionBscFailRate, 5--506
hoInIntraTchExecutionBscFailRate, 5--506
hoInSdcchExecutionFailMaxRate, 5--496
hoInSdcchExecutionFailRate, 5--481
hoInSdcchSelectionFailMaxRate, 5--495
hoInSdcchSelectionFailRate, 5--480
hoInTchExecutionFailMaxRate, 5--496
hoInTchExecutionFailRate, 5--480
hoInTchSelectionFailMaxRate, 5--495
hoInTchSelectionFailRate, 5--479
hoIntraBtsFailRateTchTieringLargeToSmallPattern, 5--490
hoIntraBtsFailRateTchTieringSmallToLargePattern, 5--490
hoNcellsExecution, 5--257
hoNcellsExecutionSdcch, 5--258
hoNCellsExecutionTchAmrFr, 5--82
hoNCellsExecutionTchAmrHr, 5--82
hoNCellsRequestOutgoingAmrFr, 5--87
hoNCellsRequestOutgoingAmrHr, 5--87
hoNcellsRequestOutgoingDirectedRetry, 5--424
hoNcellsRequestOutgoingDistance, 5--423
hoNcellsRequestOutgoingDownlinkQuality, 5--423
hoNcellsRequestOutgoingDownlinkStrength, 5--422

411--9001--125
Nortel Confidential Index xv
hoNcellsRequestOutgoingInterCellOM, 5--425
hoNcellsRequestOutgoingOther, 5--426
hoNcellsRequestOutgoingPowerBudget, 5--424
hoNCellsRequestOutgoingTraffic, 5--425
hoNcellsRequestOutgoingUplinkQuality, 5--422
hoNcellsRequestOutgoingUplinkStrength, 5--421
hoNcellsSuccessOutgoingDirectedRetry, 5--430
hoNcellsSuccessOutgoingDistance, 5--428
hoNcellsSuccessOutgoingDownlinkQuality, 5--428
hoNcellsSuccessOutgoingDownlinkStrength, 5--427
hoNcellsSuccessOutgoingInterCellOM, 5--430
hoNcellsSuccessOutgoingOther, 5--431
hoNcellsSuccessOutgoingPowerBudget, 5--429
hoNcellsSuccessOutgoingTraffic, 5--431
hoNcellsSuccessOutgoingUplinkQuality, 5--427
hoNcellsSuccessOutgoingUplinkStrength, 5--426
hoNcellsUnsuccessSdcchChlR, 5--259
hoNcellsUnsuccessSdcchOther, 5--260
hoNcellsUnsuccessSdcchTimer, 5--260
hoNCellsUnsuccessTchAmrFrClearCommand, 5--85
hoNCellsUnsuccessTchAmrFrHandoverFailure, 5--84
hoNCellsUnsuccessTchAmrFrTimerExpiration, 5--84
hoNCellsUnsuccessTchAmrHrClearCommand, 5--83
hoNCellsUnsuccessTchAmrHrHandoverFailure, 5--83
hoNCellsUnsuccessTchAmrHrTimerExpiration, 5--83
hoNcellsUnsuccessTchChlR, 5--258
hoNcellsUnsuccessTchOther, 5--259
hoNcellsUnsuccessTchTimer, 5--259
hoOutExecutionBscSdcch, 5--513
hoOutExecutionBscTch, 5--513
hoOutFirstSuccessSdcchRatio, 5--509
hoOutFirstSuccessTchRatio, 5--508
hoOutInterSdcchExecutionBscFailRate, 5--507
hoOutInterTchExecutionBscFailRate, 5--507
hoOutSdcchBscGlobalFailRate, 5--498
hoOutSdcchBscGlobalFailRateV11, 5--498
hoOutSdcchExecutionBscFailRate, 5--503
hoOutSdcchExecutionFailMaxRate, 5--494
hoOutSdcchExecutionFailRate, 5--478
hoOutSdcchFirstAttemptSuccessMinRatio, 5--497

xvi Index Nortel Confidential
hoOutSdcchFirstAttemptSuccessRatio, 5--482
hoOutSdcchGlobalFailRate, 5--474
hoOutSdcchGlobalFailRateV11, 5--474
hoOutSdcchMaxFailRate, 5--491
hoOutSdcchMaxFailRateV11, 5--491
hoOutSdcchRequestBscRatio, 5--500
hoOutSdcchRequestBscRatioV11, 5--500
hoOutSdcchRequestMaxRatio, 5--492
hoOutSdcchRequestMaxRatioV11, 5--492
hoOutSdcchRequestRatio, 5--475
hoOutSdcchRequestRatioV11, 5--475
hoOutSdcchSelectionBscFailRate, 5--501
hoOutSdcchSelectionFailMaxRate, 5--493
hoOutSdcchSelectionFailRate, 5--477
hoOutTchBscGlobalFailRate, 5--498
hoOutTchBscGlobalFailRateV11, 5--498
hoOutTchExecutionBscFailRate, 5--502
hoOutTchExecutionFailMaxRate, 5--494
hoOutTchExecutionFailRate, 5--477
hoOutTchFirstAttemptSuccessMinRatio, 5--497
hoOutTchFirstAttemptSuccessRatio, 5--481
hoOutTchGlobalFailRate, 5--473
hoOutTchGlobalFailRateV11, 5--473
hoOutTchMaxFailRate, 5--491
hoOutTchMaxFailRateV11, 5--491
hoOutTchRequestBscRatio, 5--499
hoOutTchRequestBscRatioV11, 5--499
hoOutTchRequestMaxRatio, 5--492
hoOutTchRequestMaxRatioV11, 5--492
hoOutTchRequestRatio, 5--474
hoOutTchRequestRatioV11, 5--474
hoOutTchSelectionBscFailRate, 5--501
hoOutTchSelectionFailMaxRate, 5--493
hoOutTchSelectionFailRate, 5--476
hoRequestIncomingInterBss, raw permanent, 5--123
hoRequestIncomingInterBss8W, 5--447
hoRequestIncomingInterBssSdcch, raw permanent, 5--163
hoRequestIncomingIntraBss, raw permanent, 5--122
hoRequestIncomingIntraBss8W, 5--446
hoRequestIncomingIntraBssSdcch, raw permanent, 5--162

411--9001--125
Nortel Confidential Index xvii
hoRequestIncomingIntraBssTchMsDualb, 5--391
hoRequestIntraBts, raw permanent, 5--129
hoRequestIntraBts8W, 5--448
hoRequestIntraBtsMsDualb, 5--394
hoRequestIntraBtsSdcch, raw permanent, 5--167
hoRequestOutgoingEbandEbandMsDualb, 5--384
hoRequestOutgoingEbandMbandMsDualb, 5--385
hoRequestOutgoingInterBss, raw permanent, 5--127
hoRequestOutgoingInterBss8W, 5--448
hoRequestOutgoingInterBssSdcch, raw permanent, 5--166
hoRequestOutgoingInterBssSdcch8W, 5--450
hoRequestOutgoingIntraBss, raw permanent, 5--126
hoRequestOutgoingIntraBss8W, 5--448
hoRequestOutgoingIntraBssSdcch, raw permanent, 5--165
hoRequestOutgoingIntraBssSdcch8W, 5--450
hoRequestOutgoingMbandEbandMsDualb, 5--262
hoRequestOutgoingMbandMbandMsDualb, 5--384
hoRequestOutgoingMultiband, 5--262
hoRequiredSdcch, 5--380
hoRequiredSdcchCapture, raw permanent, 5--157
hoRequiredSdcchDistance, raw permanent, 5--156
hoRequiredSdcchDownlinkQuality, raw permanent, 5--156
hoRequiredSdcchDownlinkStrength, raw permanent, 5--155
hoRequiredSdcchInterBtsOm, raw permanent, 5--159
hoRequiredSdcchIntraBtsDownlink, raw permanent, 5--159
hoRequiredSdcchIntraBtsOm, raw permanent, 5--158
hoRequiredSdcchIntraBtsUplink, raw permanent, 5--158
hoRequiredSdcchPowerBudget, raw permanent, 5--157
hoRequiredSdcchTraffic, 5--160
hoRequiredSdcchUplinkQuality, raw permanent, 5--155
hoRequiredSdcchUplinkStrength, raw permanent, 5--154
hoRequiredTch, 5--380
hoRequiredTchCapture, raw permanent, 5--146
hoRequiredTchDirectedRetry, raw permanent, 5--149
hoRequiredTchDistance, raw permanent, 5--145
hoRequiredTchDownlinkQuality, raw permanent, 5--144
hoRequiredTchDownlinkStrength, raw permanent, 5--143
hoRequiredTchInterBtsOm, raw permanent, 5--151
hoRequiredTchIntraBtsDownlink, raw permanent, 5--149
hoRequiredTchIntraBtsOm, raw permanent, 5--147

xviii Index Nortel Confidential
hoRequiredTchIntraBtsUplink, raw permanent, 5--148

hoRequiredTchPowerBudgetQuality, raw permanent, 5--146
hoRequiredTchTdmaClass0, raw permanent, 5--150
hoRequiredTchTdmaClass1, raw permanent, 5--151
hoRequiredTchTieringLargeToSmallPattern, 5--153
hoRequiredTchTieringSmallToLargePattern, 5--154
hoRequiredTchTraffic, 5--152
hoRequiredTchUplinkQuality, raw permanent, 5--144
hoRequiredTchUplinkStrength, raw permanent, 5--142
hoSuccessIncomingInterBss, raw permanent, 5--125
hoSuccessIncomingInterBss8W, 5--447
hoSuccessIncomingInterBssSdcch, raw permanent, 5--165
hoSuccessIncomingIntraBss, raw permanent, 5--125
hoSuccessIncomingIntraBss8W, 5--447
hoSuccessIncomingIntraBssSdcch, raw permanent, 5--164
hoSuccessIncomingIntraBssTchMsDualb, 5--393
hoSuccessIncomingTch, 5--382
hoSuccessIntraBts, raw permanent, 5--130
hoSuccessIntraBts8W, 5--449
hoSuccessIntraBtsMsDualb, 5--395
hoSuccessIntraBtsSdcch, raw permanent, 5--168
hoSuccessOoutgoingIntraBssSdcch8W, 5--449
hoSuccessOutgoingEbandEbandMsDualb, 5--387
hoSuccessOutgoingEbandMbandMsDualb, 5--388
hoSuccessOutgoingFirstInter, 5--128
hoSuccessOutgoingFirstInterSdcch, 5--167
hoSuccessOutgoingFirstIntra, 5--127
hoSuccessOutgoingFirstIntraSdcch, 5--166
hoSuccessOutgoingInterBss, raw permanent, 5--122
hoSuccessOutgoingInterBss8W, 5--446
hoSuccessOutgoingInterBssForDirectedRetry, raw permanent, 5--31
hoSuccessOutgoingInterBssSdcch, raw permanent, 5--162
hoSuccessOutgoingIntraBss, raw permanent, 5--121
hoSuccessOutgoingIntraBss8W, 5--446
hoSuccessOutgoingIntraBssSdcch8W, 5--449
hoSuccessOutgoingIntraBssForDirectedRetry, raw permanent, 5--30
hoSuccessOutgoingIntraBssSdcch, raw permanent, 5--161
hoSuccessOutgoingMbandEbandMsDualb, 5--262
hoSuccessOutgoingMbandMbandMsDualb, 5--386
hoSuccessOutgoingMultiband, 5--262

411--9001--125
Nortel Confidential Index xix
hoSuccessOutgoingTch, 5--382
hoSuccessTieringTchLargeToSmallPattern, 5--398
hoSuccessTieringTchSmallToLargePattern, 5--398
hoUnsuccessIncomingInterBssSdcchOtherCases, 5--379
hoUnsuccessIncomingInterBssSdcchTimerExp, 5--379
hoUnsuccessIncomingInterBssTchOtherCases, 5--379
hoUnsuccessIncomingInterBssTchTimerExp, 5--378
hoUnsuccessIncomingIntraCellSdcchReturnOldChannel, 5--378
hoUnsuccessIncomingIntraCellSdcchT3103TimerExp, 5--378
hoUnsuccessIncomingIntraCellTchReturnOldChannel, 5--377
hoUnsuccessIncomingIntraCellTchT3103TimerExp, 5--377
hoUnsuccessOutgoingInterBssNAttemptSdcch, 5--232
hoUnsuccessOutgoingInterBssNAttemptTch, 5--231
hoUnsuccessOutgoingInterCellSdcchOtherCases, 5--377
hoUnsuccessOutgoingInterCellSdcchReturnOldChannel, 5--376
hoUnsuccessOutgoingInterCellSdcchT3103TimerExp, 5--376
hoUnsuccessOutgoingInterCellTchOtherCases, 5--376
hoUnsuccessOutgoingInterCellTchReturnOldChannel, 5--375
hoUnsuccessOutgoingInterCellTchReturnOldChannel8W, 5--453
hoUnsuccessOutgoingInterCellTchT3103TimerExp8w, 5--454
hoUnsuccessOutgoingInterCellTchT3107TimerExp, 5--375
hoUnsuccessOutgoingInterCellTchT3107TimerExp8w, 5--375
hoUnsuccessOutgoingIntraBssNAttemptSdcch, 5--231
hoUnsuccessOutgoingIntraBssNAttemptTch, 5--230
hoUnsuccessOutgoingIntraCellSdcchReturnOldChannel, 5--374
hoUnsuccessOutgoingIntraCellSdcchT3103TimerExp, 5--375
hoUnsuccessOutgoingIntraCellTchReturnOldChannel, 5--374
hoUnsuccessOutgoingIntraCellTchReturnOldChannel8W, 5--453
hoUnsuccessOutgoingIntraCellTchT3103TimerExp, 5--374
hoUnsuccessOutgoingIntraCellTchT3107TimerExp8w, 5--453
hoUnsuccessReestIncomingIntraBssSdcch, 5--171
hoUnsuccessReestIncomingIntraBssTch, 5--142
hoUnsuccessReestIntraBtsSdcch, 5--169
hoUnsuccessReestIntraBtsTch, 5--140
hoUnsuccessReestOutgoingInterBssSdcch, 5--170
hoUnsuccessReestOutgoingInterBssTch, 5--141
hoUnsuccessReestOutgoingIntraBssSdcch, 5--170
hoUnsuccessReestOutgoingIntraBssTch, 5--141
I
immAssignDualBandMSRate, 5--489

xx Index Nortel Confidential
immediateAssignmentMultiband, 5--261
immediateAssignmentReject, 5--355
immediateAssignmentRejectChanActNack, 5--172
immediateAssignmentRejectChanActTimmack, 5--173
immediateAssignmentRejectOthers, 5--174
immediateAssignmentRejectOverload, 5--173
immediateAssignmentRejectRadioRes, 5--172
immediateAssignmentRejectTimingAdv, 5--174
immediateAssignmentRejectTraffMsc, 5--171
immediateAssignmentSuccess, 5--354
immediateAssignmentSuccessCause000, 5--239
incAmrFrDownModif, 5--100
incAmrFrDownModifTrZone, 5--100
incAmrFrUpModif, 5--99
incAmrFrUpModifTrZone, 5--99
incAmrHrDownModif, 5--101
incAmrHrDownModifTrZone, 5--101
incAmrHrUpModif, 5--100
incAmrHrUpModifTrZone, 5--100
intracellAmrFrDownHoRequiredTch, 5--74
intracellAmrFrUpHoRequiredTch, 5--73
invalidBlocksUp, 5--605
invalidProtocolErrorBlocksUp, 5--605
L
lapdOverloadRejectedOpSicd0, 5--27
listenerDetectionExpiry, 5--456
llcDiscardedOctets, 5--582
llcDiscardedPdu, 5--582
llcPacketsDn, 5--601
llcPacketsUp, 5--601
localBusy, 5--599

411--9001--125
Nortel Confidential Index xxi
localMsgBlockCapacity, 5--629
localMsgBlockUsageAvg, 5--629
localMsgBlockUsageMax, 5--629
localMsgBlockUsageMin, 5--629
lossOfComNN002Max, 5--612
lossOfComNT0001, 5--614
lossOfComT3169, 5--613
M
MaxDlThroughput, 5--581
memoryCapacityFastRam, 5--625
memoryCapacityNormalRam, 5--626
memoryCapacitySharedRam, 5--626
memoryUsageAvgFastRam, 5--627
memoryUsageAvgMaxFastRam, 5--627
memoryUsageAvgMaxNormalRam, 5--627
memoryUsageAvgMaxSharedRam, 5--628
memoryUsageAvgMinFastRam, 5--627
memoryUsageAvgMinNormalRam, 5--627
memoryUsageAvgMinSharedRam, 5--628
memoryUsageAvgNormalRam, 5--627
memoryUsageAvgSharedRam, 5--628
msClassSensitivityToggle, 5--445
msFlowControlRequests, 5--582
msFlushLLRequest, 5--583
msLostMeasurements, 5--306
msLostMeasurementsAmrFr, 5--70
msLostMeasurementsAmrFrTrZone, 5--70
msLostMeasurementsAmrHr, 5--70
msLostMeasurementsAmrHrTrZone, 5--70
msLostMeasurementsTrZone, 5--306
msPowerDecControl, 5--400
msPowerDecControlAmrFr, 5--63
msPowerDecControlAmrHr, 5--68
msPowerIncControl, 5--399
msPowerIncControlAmrFr, 5--63
msPowerIncControlAmrHr, 5--67

xxii Index Nortel Confidential
N
nbSamplesDnQuality, 5--610
nbSamplesUpQuality, 5--609
noPacketResourceReq, 5--611
notifsReachMaxTransmit, 5--563
notifsReceived, 5--562
notifsSentOnce, 5--563
notifsTransmitAgainOnce, 5--563
notifsTransmitAgainTwiceAndMore, 5--563
O
octetDiscarded, 5--578
octetsDataDn, 5--577
octetsDataUp, 5--578
octetsDn, 5--576
octetsUp, 5--576
omcDatabaseUsed, 5--569
omcDatabaseUsedCum, 5--569
omcDatabaseUsedEch, 5--569
omcInputIFrame, 5--13
omcInputRepeatedIFrame, 5--14
omcInputRnrFrame, 5--15
omcLinkSwitchOver, 5--11
omcOutputIFrame, 5--13
omcOutputRepeatedIFrame, 5--14
omcOutputRnrFrame, 5--15
omcSybaseCpuBusy, 5--568
omcSybaseIdle, 5--568
omcSybaseIoBusy, 5--568
omcSybasePacketErr, 5--569
omcSybasePacketIn, 5--568
omcSybasePacketOut, 5--569
omcSybaseTotalError, 5--567
omcSybaseTotalRead, 5--567
omcSybaseTotalWrite, 5--567
omcUnixBasePartition, 5--574
omcUnixBasePartitionCum, 5--574
omcUnixBasePartitionEch, 5--574

411--9001--125
Nortel Confidential Index xxiii
omcUnixCpu0Used, 5--572
omcUnixCpu0UsedCum, 5--572
omcUnixCpu1Used, 5--572
omcUnixCpu1UsedCum, 5--572
omcUnixCpu1UsedEch, 5--572
omcUnixDataPartition, 5--575
omcUnixDataPartitionCum, 5--575
omcUnixDataPartitionEch, 5--575
omcUnixMailPartition, 5--574
omcUnixMailPartitionCum, 5--574
omcUnixMailPartitionEch, 5--574
omcUnixObsPartition, 5--574
omcUnixObsPartitionCum, 5--574
omcUnixRootPartition, 5--573
omcUnixRootPartitionCum, 5--573
omcUnixRootPartitionEch, 5--573
omcUnixSwap, 5--573
omcUnixSwapCum, 5--573
omcUnixSwapEch, 5--573
omcUnixTmpPartition, 5--573
omcUnixTmpPartitionCum, 5--573
omcUnixTmpPartitionEch, 5--573
omcX25AbortsPort0, 5--572
omcX25CrcErrorsPort0, 5--571
omcX25PacketInPort0, 5--571
omcX25PacketOutPort0, 5--571
ommdActConf, 5--557
ommdActRequest, 5--557

xxiv Index Nortel Confidential
ommdCancelGetConf, 5--558
ommdCancelGetRequest, 5--558
ommdCreConf, 5--555
ommdCreRequest, 5--555
ommdDelConf, 5--557
ommdDelRequest, 5--556
ommdGetConf, 5--555
ommdGetRequest, 5--554
ommdSetConf, 5--556
ommdSetRequest, 5--556
omnetActConf, 5--561
omnetActRequest, 5--561
omnetCancelGetConf, 5--562
omnetCancelGetRequest, 5--562
omnetCreConf, 5--559
omnetCreRequest, 5--559
omnetDelConf, 5--561
omnetDelRequest, 5--560
omnetGetConf, 5--559
omnetGetRequest, 5--558
omnetSetConf, 5--560
omnetSetRequest, 5--560
outOfSequenceBlocksUp, 5--606
P
packetAckNackDn, 5--607
packetAckNackUp, 5--606
packetResourceRequest, 5--612
pagingFilteredByBsc, 5--35
pagingResponse, raw instrument panel, 5--349
pathBalanceMoy/Max/Cum/Ech, 5--38
pchAveragedQueueLength, 5--277
pchAveragedQueueLengthCell, 5--526
pchAveragedQueueLengthCellCum, 5--526
pchAveragedQueueLengthCellEch, 5--526
pchAveragedQueueLengthCellMax, 5--526
pchAveragedQueueLengthCellMoy, 5--526
pchAveragedQueueLengthEch, 5--277
pchAveragedQueueLengthMax, 5--277

411--9001--125
Nortel Confidential Index xxv
pchAveragedQueueLengthTs2Ech, 5--277
pchAveragedQueueLengthTs2Moy, 5--277
pchAveragedQueueLengthTs4Cum, 5--277
pchAveragedQueueLengthTs6Cum, 5--277
pchMoreWait/Ts2/Ts4/Ts6, 5--110
pchMoreWaitCell, 5--526
pchNoWait/Ts2/Ts4/Ts6, 5--105
pchNoWaitCell, 5--525
pchOneWait/Ts2/Ts4/Ts6, 5--107
pchOneWaitCell, 5--525
pchQueuePagesDiscarded, 5--279
pchQueuePagesDiscardedCell, 5--527
pchQueuePagesDiscardedTs2, 5--279
pchTwoWait/Ts2/Ts4/Ts6, 5--109
pchTwoWaitCell, 5--525
pcmErrCorrEfficiency, 5--518
pcmFaultDDTIBoard, 5--20
pcmFaultExternal, 5--19
pcmFaultInternal, 5--20
pcmFaultOutOfService, 5--20
pcminsecondsMoy/Max/Cum/Ech, 5--520
pcmUnavailabilityMoy/Max/Cum/Ech, 5--10
pcuAgprsJokerNbofBlocksDn, 5--655
pcuAgprsJokerNbofBlocksUp, 5--660
pcuAgprsMainNbofBlocksDn, 5--649
pcuAgprsMainNbofBlocksUp, 5--659
pcuChannelRequestOnePhase, 5--691
pcuContentionFailureOnePhase, 5--692, 5--694
pcuDlThroughput, 5--579
pcuDlThroughputCum, 5--578
pcuDlThroughputNbs, 5--579
pcuDyAgprsLoadCriterionNbs, 5--637
pcuDyAgprsNbTimeslots, 5--634
pcuDyAgprsNbTimeslotsCun, 5--634

xxvi Index Nortel Confidential
pcuDyAgprsNbTimeslotsNbs, 5--634
pcuDynAgprsJokerAvgNbTimeslot, 5--655
pcuDynAgprsJokerCumNbTimeslot, 5--654
pcuDynAgprsJokerMaxNbTimeslot, 5--655
pcuDynAgprsJokerMinNbTimeslot, 5--654
pcuEdgeCell15114s0, 5--652
pcuEdgeDataBlocksReceivedUp, 5--643
pcuEdgeDnAvg8PskMeanBep, 5--644
pcuEdgeDnAvgUsefulDataPerCell, 5--652
pcuEdgeDnCum8PskMeanBep, 5--644
pcuEdgeDnAvgGmskMeanBep, 5--645
pcuEdgeDnCumGmskMeanBep, 5--645
pcuEdgeDnCumUsefulDataPerCell, 5--652
pcuEdgeDnNbs8PskMeanBep, 5--644
pcuEdgeDnNbsGmskMeanBep, 5--645
pcuEdgeDnNbsUsefulDataPerCell, 5--652
pcuEdgeDnTransmittedMcs2, 5--662
pcuEdgeDnUsefulDataDurationPerCell, 5--658
pcuEdgeDowngradedTbf, 5--649
pcuEdgeDowngradedTbfAvg, 5--649
pcuEdgeDowngradedTbfNbs, 5--649
pcuEdgeLADnTargetedTransmittedMcs2, 5--670

411--9001--125
Nortel Confidential Index xxvii
pcuEdgeLAUpTargetedTransmittedMcs2, 5--686
pcuEdgeMcs2RequestRetransDataBlockDn, 5--666
pcuEdgeMcs2RequestRetransDataBlockUp, 5--680
pcuEdgeTbfEstReq, 5--657
pcuEdgeTdma15100s0, 5--643
pcuEdgeUpAvgMeanBep, 5--646
pcuEdgeUpAvgUsefulDataPerCell, 5--650
pcuEdgeUpCumMeanBep, 5--646
pcuEdgeUpCumUsefulDataPerCell, 5--650
pcuEdgeUpNbsMeanBep, 5--646
pcuEdgeUpNbsUsefulDataPerCell, 5--650
pcuEdgeUpTransmittedMcs2, 5--674

xxviii Index Nortel Confidential
pcuEdgeUpUsefulDataDurationPerCell, 5--657
pcuLackAbisJokerTSAvg, 5--660
pcuLackAbisJokerTSCum, 5--660
pcuLackAbisJokerTSNbs, 5--660
pcuUpPipeGreater22kbps, 5--694
pcuUpTbfImmediateAssignmentOnePhase, 5--692
pcuUpThroughputAvg, 5--693
pcuUpThroughputCum, 5--693
pcuUpThroughputNbs, 5--693
pduDataDn, 5--577
pduDataUp, 5--577
preemptedEdgeTsMoy/Max/Cum/Ech, 5--40
preemptedEdgeTsCellMoy/Max/Cum/Ech, 5--42
preemptedEdgeTsTrZoneMoy/Max/Cum/Ech, 5--40
prLoadCne3OmuSbcMoy/Max/Cum/Ech, 5--46
prLoadCne3TmuPmcMoy/Max/Cum/Ech, 5--47
prLoadCne3TmuSbcMoy/Max/Cum/Ech, 5--47
prLoadCpueMoy/Max/Cum/Ech, 5--17
prLoadCpue1Moy/Max/Cum/Ech, 5--17
prLoadCpue2Moy/Max/Cum/Ech, 5--17
prLoadCpumMoy/Max/Cum/Ech, 5--16
prLoadSicd[x], 5--18
psPaging, 5--632
PsPagingOnCCCH, 5--584
Q
qualityHoFiltered, 5--70
R
rachAccessCount/Ts2/Ts4/Ts6, 5--104
rachAccessCountCell, 5--524
rachBusyCount/Ts2/Ts4/Ts6, 5--103
rachBusyCountCell, 5--524
rachNonDecodedAvLevelMoy/Max/Cum/Ech, 5--112
rachNonDecodedAvLevelCell, 5--526
rachNonDecodedAvLevelCum, 5--112

411--9001--125
Nortel Confidential Index xxix
rachNonDecodedAvLevelEch, 5--112
rachNonDecodedAvLevelMax, 5--112
rachNonDecodedAvLevelTs2, 5--112
rachNonDecodedAvLevelTs2Cum, 5--112
rachNonDecodedAvLevelTs2Ech, 5--112
rachNonDecodedAvLevelTs2Max, 5--112
rachNonDecodedAvLevelTs4Max, 5--112
radioFrameUlReceived, 5--344
rafficRelease8W, 5--451
relativeTimeDLPowerCtrlMaxSdcch, 5--488
relativeTimeDLPowerCtrlMaxTch, 5--487
relativeTimeULPowerCtrlMaxSdcch, 5--488
relativeTimeULPowerCtrlMaxTch, 5--487
requestedHandoverForDualBandMSToSecondVersusMainBand, 5--489
RequestedRetransmittedDataBlocksDN, 5--601
resumeFailureAfterHOInterBSC, 5--459, 5--460
retransmittedDataBlocksDn, 5--610
rsttraceDatabaseUsed, 5--570
rsttraceDatabaseUsedCum, 5--570
rsttraceDatabaseUsedEch, 5--570
rxBytes, 5--630
rxFrames, 5--630
rxLevDownLink, 5--308
RxLevDownlinkAmrFr, 5--61
RxLevDownlinkAmrFrTrZone, 5--61
RxLevDownlinkAmrHr, 5--66
RxLevDownlinkAmrHrTrZone, 5--66
rxLevDownLinkTrZone, 5--308
rxLevUpLink, 5--309
RxLevUplinkAmrFr, 5--61
RxLevUplinkAmrFrTrZone, 5--61
RxLevUplinkAmrHr, 5--66
RxLevUplinkAmrHrTrZone, 5--66
rxLevUpLinkTrZone, 5--310

xxx Index Nortel Confidential
rxQualDownLink, 5--311
RxQualDownlinkAmrFr, 5--62
RxQualDownlinkAmrFrTrZone, 5--62
RxQualDownlinkAmrHr, 5--67
RxQualDownlinkAmrHrTrZone, 5--67
rxQualDownLinkTrZone, 5--312
rxQualUpLink, 5--313
RxQualUplinkAmrFr, 5--62
RxQualUplinkAmrFrTrZone, 5--62
RxQualUplinkAmrHr, 5--67
RxQualUplinkAmrHrTrZone, 5--67
rxQualUpLinkTrZone, 5--314
rxTotalLinkUtil, 5--631
S
saicTchSuccessfullyAssigned, 5--46
saicTchSuccessfullyAssignedTrZone, 5--46
sapi3SessionEstablishment, 5--306
sccpAllocated, 5--132
sccpAllocatedLcs, 5--133
sccpAveragedUsed, raw permanent, 5--134
sccpResourceFailureRatio, 5--510
sccpRessourceFailure, 5--135
sccpRessourceFailureBscRefusal, 5--136
sccpRessourceFailureBscRefusalLcs, 5--137
sccpRessourceFailureLcs, 5--136
scseFailConnect, 5--548
scseRgeIn, 5--548
scseTgeOut, 5--548
scseTotAssocFree, 5--549
scseTotTgeRefused, 5--548
sdcchAllocated, 5--281
sdcchAllocatedTrZone, 5--281
sdcchAverageConfiguratedCum, 5--407
sdcchAverageConfiguratedEch, 5--407
sdcchAverageConfiguratedMax, 5--407
sdcchAverageConfiguratedMoy, 5--407
sdcchAverageConfiguratedTrZoneCum, 5--407
sdcchAverageConfiguratedTrZoneEch, 5--407

411--9001--125
Nortel Confidential Index xxxi
sdcchAverageConfiguratedTrZoneMax, 5--407
sdcchAverageConfiguratedTrZoneMoy, 5--407
sdcchAveragedAvailableCum, 5--320
sdcchAveragedAvailableEch, 5--320
sdcchAveragedAvailableMax, 5--320
sdcchAveragedAvailableMoy, 5--320
sdcchAveragedAvailableTrZone, 5--320
sdcchAveragedAvailableTrZoneCum, 5--320
sdcchAveragedAvailableTrZoneEch, 5--320
sdcchAveragedAvailableTrZoneMax, 5--320
sdcchAveragedUsedCum, 5--282
sdcchAveragedUsedEch, 5--282
sdcchAveragedUsedMax, 5--282
sdcchAveragedUsedMoy, 5--282
sdcchAveragedUsedTrZoneCum, 5--282
sdcchAveragedUsedTrZoneEch, 5--282
sdcchAveragedUsedTrZoneMax, 5--282
sdcchAveragedUsedTrZoneMoy, 5--282
sdcchRessourceFailure, 5--284
sdcchRessourceFailureTrZone, 5--284
sharedMsgBlockCapacity, 5--628
sharedMsgBlockUsageAvg, 5--628
sharedMsgBlockUsageAvgMax, 5--628
sharedMsgBlockUsageAvgMin, 5--628
signallingAbnormalReleaseCell, 5--381
signallingPhaseDurationHighMoy/Max/Cum/Ech, 5--115
signallingPhaseDurationMoy/Max/Cum/Ech, 5--113
signallingReleaseBts, 5--355
signallingReleaseBts8W, 5--450
signallingReleaseBtsCallClearing, 5--185
signallingReleaseBtsCicRemovalEqptFail, 5--184
signallingReleaseBtsClearCommand, 5--192
signallingReleaseBtsCnxFailRadioIntFail, 5--185
signallingReleaseBtsCnxFailRadioLinkFail, 5--186
signallingReleaseBtsCnxFailRemTransFail, 5--196
signallingReleaseBtsErrorIndDm, 5--191
signallingReleaseBtsErrorIndSeq, 5--191
signallingReleaseBtsErrorIndT200, 5--189
signallingReleaseBtsIncFirstL3, 5--180
signallingReleaseBtsOmCicRemoval, 5--183

xxxii Index Nortel Confidential
signallingReleaseBtsOmRadioChanBloc, 5--184
signallingReleaseBtsOmTsRemoval, 5--182
signallingReleaseBtsOthers, 5--195
signallingReleaseBtsReleaseInd, 5--187
signallingReleaseBtsReset, 5--179
signallingReleaseBtsResetCirc, 5--179
signallingReleaseBtsRfResInd, 5--193
signallingReleaseBtsSccpDataRefusal, 5--180
signallingReleaseBtsSccpDiscInd, 5--178
signallingReleaseBtsSwitchOver, 5--193
signallingReleaseBtsT11, 5--196
signallingReleaseBtsT3107CircDown, 5--182
signallingReleaseBtsT3107CircDown8W, 5--451
signallingReleaseBtsTmodMs, 5--194
signallingReleaseBtsTsRemovalEqptFail, 5--183
signallingReleaseCellTbcEdge, 5--197
signallingReleaseNoBts, 5--355
signallingReleaseNoBtsBadDataInd, 5--177
signallingReleaseNoBtsOthers, 5--178
signallingReleaseNoBtsReset, 5--175
signallingReleaseNoBtsSccpDataRefusal, 5--176
signallingReleaseNoBtsSccpDiscInd, 5--175
signallingReleaseNoBtsTsccRel, 5--177
signallingReleaseRatio, 5--523
speechAlgoFallBack, 5--260
ss7InputMsu, 5--461
ss7Level2ErrorMsuCongest, 5--462
ss7Level2ErrorNegAckRec, 5--462
ss7Level2ErrorNegAckTrans, 5--462
ss7Level2ErrorSuErr, 5--463
ss7Level3ErrorDelay, 5--463
ss7Level3ErrorHighErrRate, 5--463
ss7OutputMsu, 5--461
successfulTchFrSeizures, 5--117
successfulTchFrSeizures8W, 5--445
successfulTchFrSeizuresMsDualb, 5--341
sybaseCpuBusy, 5--545

411--9001--125
Nortel Confidential Index xxxiii
sybaseIdle, 5--545
sybaseIoBusy, 5--545
sybasePacketErr, 5--546
sybasePacketIn, 5--545
sybasePacketOut, 5--546
sybaseTotalError, 5--544
sybaseTotalRead, 5--544
sybaseTotalWrite, 5--544
T
t3103ExpSdcch, 5--485
t3103ExpTch, 5--484
t3107ExpAssign, 5--483
t3107ExpIntraBtsHoSdcch, 5--483
t3107ExpIntraBtsHoTch, 5--484
tbfNormalReleaseDn, 5--611
tbfNormalReleaseUp, 5--610
tcAllocated, 5--130
tcAveragedUsed, raw permanent, 5--131
tchAveragedQueueLengthHighPriorityCum, 5--296
tchAveragedQueueLengthHighPriorityEch, 5--296
tchAveragedQueueLengthHighPriorityMax, 5--296
tchAveragedQueueLengthHighPriorityMoy, 5--296
tchAveragedQueueLengthOtherPriority, 5--297
tchFrAllocated, 5--349
tchFrAllocatedOverflowAllocation, 5--287
tchFrAllocatedOverflowAllocationTrZone, 5--287
tchFrAllocatedPrimoAllocation, 5--286
tchFrAllocatedPrimoAllocationTrZone, 5--286
tchFrAllocatedTchAllocation, 5--285
tchFrAllocatedTchAllocationTrZone, 5--285
tchFrAllocatedTrZone, 5--350
tchFrAllocatedWps, 5--288
tchFrAllocatedWpsTrZone, 5--288
tchFrAverageConfigurated, 5--406
tchFrAverageConfiguratedCellMoy/Max/Cum/Ech, 5--419
tchFrAverageConfiguratedCum, 5--406
tchFrAverageConfiguratedEch, 5--406
tchFrAverageConfiguratedMax, 5--406

xxxiv Index Nortel Confidential
tchFrAverageConfiguratedMoy, 5--406
tchFrAverageConfiguratedTrZoneCum, 5--406
tchFrAverageConfiguratedTrZoneEch, 5--406
tchFrAverageConfiguratedTrZoneMax, 5--406
tchFrAverageConfiguratedTrZoneMoy, 5--406
tchFrAveragedAvailable, 5--318
tchFrAveragedAvailableCellMoy/Max/Cum/Ech, 5--418
tchFrAveragedAvailableCum, 5--318
tchFrAveragedAvailableEch, 5--318
tchFrAveragedAvailableMax, 5--318
tchFrAveragedAvailableMoy, 5--318
tchFrAveragedAvailableTrZoneCum, 5--318
tchFrAveragedAvailableTrZoneEch, 5--318
tchFrAveragedAvailableTrZoneMax, 5--318
tchFrAveragedAvailableTrZoneMoy, 5--318
tchFrAveragedUsedAllocationMax, 5--291
tchFrAveragedUsedCellMoy/Max/Cum/Ech, 5--419
tchFrAveragedUsedCum, 5--352
tchFrAveragedUsedEch, 5--352
tchFrAveragedUsedMax, 5--352
tchFrAveragedUsedMoy, 5--352
tchFrAveragedUsedNsc, 5--352
tchFrAveragedUsedOverflowAllocationCellMoy/Max/Cum/Ech, 5--417
tchFrAveragedUsedOverflowAllocationCum, 5--292
tchFrAveragedUsedOverflowAllocationEch, 5--292
tchFrAveragedUsedOverflowAllocationMax, 5--292
tchFrAveragedUsedOverflowAllocationMoy, 5--292
tchFrAveragedUsedOverflowAllocationTrZoneCum, 5--292
tchFrAveragedUsedOverflowAllocationTrZoneEch, 5--292
tchFrAveragedUsedOverflowAllocationTrZoneMax, 5--292
tchFrAveragedUsedOverflowAllocationTrZoneMoy, 5--292
tchFrAveragedUsedPrimoAllocation, 5--511
tchFrAveragedUsedPrimoAllocationCellMoy/Max/Cum/Ech, 5--416
tchFrAveragedUsedPrimoAllocationMoy, 5--291
tchFrAveragedUsedPrimoAllocationTrZoneCum, 5--291
tchFrAveragedUsedPrimoAllocationTrZoneEch, 5--291
tchFrAveragedUsedPrimoAllocationTrZoneMax, 5--291
tchFrAveragedUsedPrimoAllocationTrZoneMoy, 5--291
tchFrAveragedUsedTchAllocationCellMoy/Max/Cum/Ech, 5--415
tchFrAveragedUsedTchAllocationMoy/Max/Cum/Ech, 5--289

411--9001--125
Nortel Confidential Index xxxv
tchFrAveragedUsedTchAllocationTrZoneMoy/Max/Cum/Ech, 5--289
tchFrAveragedUsedTrZoneCum, 5--352
tchFrAveragedUsedTrZoneEch, 5--352
tchFrAveragedUsedTrZoneMax, 5--352
tchFrAveragedUsedTrZoneMoy, 5--352
tchFrAveragedUsedWpsCellMoy/Max/Cum/Ech, 5--417
tchFrAveragedUsedWpsMoy/Max/Cum/Ech, 5--293
tchFrAveragedUsedWpsTrZoneMoy/Max/Cum/Ech, 5--293
tchFrRessourceFailure, 5--295
tchFrRessourceFailureTrZone, 5--295
tchHrAllocated, 5--351
tchHrAllocatedNsc, 5--351
tchHrAllocatedTchAllocation, 5--288
tchHrAllocatedTchAllocationTrZone, 5--288
tchHrAllocatedTrZone, 5--351
tchHrAllocatedWps, 5--36
tchHrAllocatedWpsTrZone, 5--36
tchHrAveragedUsedCellMoy/Max/Cum/Ech, 5--420
tchHrAveragedUsedMoy/Max/Cum/Ech, 5--353
tchHrAveragedUsedNscCellMoy/Max/Cum/Ech, 5--421
tchHrAveragedUsedTchAllocationMoy/Max/Cum/Ech, 5--294
tchHrAveragedUsedTchAllocationTrZoneMoy/Max/Cum/Ech, 5--294
tchHrAveragedUsedTrZoneMoy/Max/Cum/Ech, 5--353
tchHrAveragedUsedWpsCellMoy/Max/Cum/Ech, 5--420
tchHrAveragedUsedWpsTrZoneMoy/Max/Cum/Ech, 5--36
tchHrRessourceFailure, 5--296
tchHrRessourceFailureTrZone, 5--296
tchOccupancy, 5--533
tchQueuingDurationHighPriority, 5--299
tchQueuingDurationOtherPriority, 5--300
tchQueuingExpirationHighPriority, 5--298
tchQueuingExpirationOtherPriority, 5--298
tdmaClassTchResourceFailureRatio, 5--527
timingAdvanceAmrFrAvg, 5--64
timingAdvanceAmrFrMax, 5--65
timingAdvanceAmrHrAvg, 5--69
timingAdvanceAmrHrMax, 5--69
timingAdvanceAverage, 5--404
timingAdvanceAverageTrZone, 5--404
timingAdvanceMaximum, 5--405

xxxvi Index Nortel Confidential
timingAdvanceMaximumTrZone, 5--405
totalNumberOfEdgeTsMoy/Max/Cum/Ech, 5--39
totalNumberOfEdgeTsCellMoy/Max/Cum/Ech, 5--41
totalNumberOfEdgeTsTrZoneMoy/Max/Cum/Ech, 5--39
totalNumberOfPacketTsMoy/Max/Cum/Ech, 5--410
totalNumberOfPacketTsCellMoy/Max/Cum/Ech, 5--414
totalNumberOfPacketTsUsedForCircuitMoy/Max/Cum/Ech, 5--411
totalNumberOfPacketTsUsedForCircuitCellMoy/Max/Cum/Ech, 5--414
totalNumberOfPacketTsUsedForCircuitTrZoneMoy/Max/Cum/Ech, 5--411
totalRetransmissionRequested, 5--607
traceDatabaseSeg0Used, 5--569
traceDatabaseSeg0UsedCum, 5--569
traceDatabaseSeg0UsedEch, 5--569
traceDatabaseSeg1Used, 5--570
traceDatabaseSeg1UsedCum, 5--570
traceDatabaseSeg1UsedEch, 5--570
trafficAbnormalRelease, 5--381
trafficAbnormalRelease8w, 5--454
trafficRelease, 5--356
trafficReleaseAmrFrLapdmCause, 5--85
trafficReleaseAmrFrOthersCause, 5--86
trafficReleaseAmrFrRadioCause, 5--85
trafficReleaseAmrHrLapdmCause, 5--86
trafficReleaseAmrHrOthersCause, 5--86
trafficReleaseAmrHrRadioCause, 5--86
trafficReleaseCallClearing, 5--202
trafficReleaseCicRemovalEqptFail, 5--201
trafficReleaseClearCommand, 5--208
trafficReleaseCnxFailRadioIntFail, 5--203
trafficReleaseCnxFailRadioLinkFail, 5--203
trafficReleaseCnxFailRemTransFail, 5--221
trafficReleaseErrorIndDm, 5--207
trafficReleaseErrorIndSeq, 5--208
trafficReleaseErrorIndT200, 5--206
trafficReleaseOmCicRemoval, 5--201
trafficReleaseOmRadioChanBloc, 5--202
trafficReleaseOmTsRemoval, 5--200
trafficReleaseOthers, 5--211
trafficReleaseReleaseInd, 5--204
trafficReleaseReset, 5--198

411--9001--125
Nortel Confidential Index xxxvii
trafficReleaseResetCirc, 5--198
trafficReleaseRfResInd, 5--209
trafficReleaseSccpDataRefusal, 5--199
trafficReleaseSccpDiscInd, 5--197
trafficReleaseSysInfoFail, 5--221
trafficReleaseT3103, 5--210
trafficReleaseT3107CircDown, 5--199
trafficReleaseT8, 5--211
trafficReleaseTbcEdge, 5--32
trafficReleaseTmodMs, 5--210
trafficReleaseTsRemovalEqptFail, 5--200
txBytes, 5--630
txFrames, 5--631
U
ulsecondPhaseAllocFailure, 5--596
ulsecondPhaseRadioFailure, 5--599
unixCmnBasePartitionNMCSrv, 5--554
unixCmnBasePartitionNMCSrvCum, 5--554
unixCmnBasePartitionNMCSrvEch, 5--554
unixCmnDataPartitionNMCSrv, 5--554
unixCmnDataPartitionNMCSrvCum, 5--554
unixCmnDataPartitionNMCSrvEch, 5--554
unixCpu0UsedNMCSrv, 5--549
unixCpu0UsedNMCSrvCum, 5--549
unixCpu0UsedNMCSrvEch, 5--549
unixCpu1UsedNMCSrv, 5--549
unixCpu1UsedNMCSrvCum, 5--549
unixCpu1UsedNMCSrvEch, 5--549
unixDataSsnPartition, 5--552
unixDataSsnPartitionCum, 5--552
unixDataSsnPartitionEch, 5--552
unixMdrBasePartitionNMCSrv, 5--553
unixMdrBasePartitionNMCSrvCum, 5--553
unixMdrBasePartitionNMCSrvEch, 5--553
unixMdrDataPartitionNMCSrv, 5--553
unixMdrDataPartitionNMCSrvCum, 5--553
unixMdrDataPartitionNMCSrvEch, 5--553
unixNotifPartition, 5--551

xxxviii Index Nortel Confidential
unixNotifPartitionCum, 5--551
unixNotifPartitionEch, 5--551
unixObsPartition, 5--551
unixObsPartitionCum, 5--551
unixObsPartitionEch, 5--551
unixRestoredNotifPartition, 5--552
unixRestoredNotifPartitionCum, 5--552
unixRestoredNotifPartitionEch, 5--552
unixRestoredObsPartition, 5--551
unixRestoredObsPartitionCum, 5--551
unixRestoredObsPartitionEch, 5--551
unixRestoredTracePartition, 5--553
unixRestoredTracePartitionCum, 5--553
unixRestoredTracePartitionEch, 5--553
unixRootPartitionNMCSrv, 5--550
unixRootPartitionNMCSrvCum, 5--550
unixRootPartitionNMCSrvEch, 5--550
unixSwapNMCSrv, 5--550
unixSwapNMCSrvCum, 5--550
unixSwapNMCSrvEch, 5--550
unixTmpPartitionNMCSrv, 5--550
unixTmpPartitionNMCSrvCum, 5--550
unixTmpPartitionNMCSrvEch, 5--550
unixTracePartition, 5--552
unixTracePartitionCum, 5--552
unixTracePartitionEch, 5--552
uplinkPowerCtrlMaxSdcchCum, 5--273
uplinkPowerCtrlMaxSdcchEch, 5--273
uplinkPowerCtrlMaxSdcchMax, 5--273
uplinkPowerCtrlMaxSdcchMoy, 5--273
uplinkPowerCtrlMaxTchAmrFrMoy/Max/Cum/Ech, 5--60
uplinkPowerCtrlMaxTchAmrHrMoy/Max/Cum/Ech, 5--65
uplinkPowerCtrlMaxTchCum, 5--256
uplinkPowerCtrlMaxTchEch, 5--256
uplinkPowerCtrlMaxTchMax, 5--256
uplinkPowerCtrlMaxTchMoy, 5--256
upMultiSlotRequest1, 5--584
upPipeGreater11kbps, 5--621

411--9001--125
Nortel Confidential Index xxxix
upPipeless11kbps, 5--620
upTbfBronzeRejectedForMinTput, 5--623
upTbfBronzeSatisfactBet5090pCent, 5--622
upTbfBronzeSatisfactLess50pCent, 5--623
upTbfBronzeSatisfactMore90pCent, 5--621
upTbfGoldRejectedForMinTput, 5--589
upTbfGoldSatisfactBet5090pCent, 5--588
upTbfGoldSatisfactLess50pCent, 5--589
upTbfGoldSatisfactMore90pCent, 5--588
upTbfImmAssigRejectNoPdch, 5--617
upTbfImmediateAssignment, 5--617
upTbfReleases, 5--597
upTbfSilverRejectedForMinTput, 5--620
upTbfSilverSatisfactLess50pCent, 5--622
upUserdatablocks, 5--600
V
vgcsAccessGrant, 5--267
vgcsMscReject, 5--267
W
wpsAccessBarringDurationClass0to9, 5--440, 5--441, 5--442, 5--443
wpsAccessBarringDurationClass11, 5--441
WPUBWPSQ, 5--443
WQABAND, 5--443
WQOVFL1, 5--437
WQOVFL2, 5--437
WQOVFL3, 5--437
WQOVFL4, 5--438
WQOVFL5, 5--438
WQTOUT1, 5--438, 5--439, 5--440
WQTOUT2, 5--439
WQTOUT3, 5--439
WQTOUT4, 5--439

xl Index Nortel Confidential
WQTOUT5, 5--440
WQUEDHO, 5--444, 5--455
WQUEUED1, 5--435, 5--436
WQUEUED2, 5--435
WQUEUED3, 5--436
WQUEUED4, 5--436
WQUEUED5, 5--436

411--9001--125
Copyright © 2000--2006 Nortel Networks, All Rights Reserved
NORTEL CONFIDENTIAL:
The information contained in this document is the property of Nortel For more information, please contact:
Networks. Except as specifically authorized in writing by Nortel
Networks, the holder of this document shall keep the information For all countries, except USA:
contained herein confidential and shall protect same in whole or in part
NORTEL
from disclosure and dissemination to third parties and use for evaluation,
operation and maintenance purposes only. Documentation Department
Parc d’activité de Magny--Chateaufort
You may not reproduce, represent, or download through any means, the CHATEAUFORT
information contained herein in any way or in any form without prior 78928 YVELINES CEDEX 9
written consent of Nortel Networks. FRANCE
The following are trademarks of Nortel Networks: *NORTEL , the Email : umts--gsm.ntp@nortel.com
NORTEL corporate logo, the NORTEL Globemark, UNIFIED Fax : (33) (1) 39--44--50--29
NETWORKS, S2000, S4000, S8000.
GSM is a trademark of France Telecom. In the USA:
All other brand and product names are trademarks or registered
NORTEL
trademarks of their respective holders.
Global Knowledge Services
Publication Reference
PE/DCL/DD/0125 411--9001--125 2221 Lakeside Boulevard
15.154/EN Richardson TX 75082
May 2006 USA
Originated in France Tel: 1--800--4 NORTEL
1--(800)--466--7838 or (972) 684--5935
Internet Address:
http://www.nortel.com

411 9001 125.15

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

411 9001 125.15

Transféré par

Droits d'auteur :

Formats disponibles

Wireless Service Provider Solutions

Observation Counter Dictionary

Wireless Service Provider Solutions

Copyright © 2000--2006 Nortel Networks, All Rights Reserved

System release:GSM/BSS V15.1.1

Copyright © 2000--2006 Nortel Networks Observation Counter Dictionary

System release:GSM/BSS V15.1

PE/DCL/DD/0125 Standard 15.154/EN May 2006 Copyright © 2000--2006 Nortel Networks

Copyright © 2000--2006 Nortel Networks Observation Counter Dictionary

PE/DCL/DD/0125 Standard 15.154/EN May 2006 Copyright © 2000--2006 Nortel Networks

SYSTEM RELEASE: GSM/BSS V15.1R

Copyright © 2000--2006 Nortel Networks Observation Counter Dictionary

SYSTEM RELEASE: GSM/BSS V15.0

PE/DCL/DD/0125 Standard 15.154/EN May 2006 Copyright © 2000--2006 Nortel Networks

Issue 15.15/EN Preliminary

Issue 15.11/EN Preliminary

Issue 15.10/EN Preliminary

Issue 15.08/EN Preliminary

Copyright © 2000--2006 Nortel Networks Observation Counter Dictionary

PE/DCL/DD/0125 Standard 15.154/EN May 2006 Copyright © 2000--2006 Nortel Networks

SYSTEM RELEASE: GSM/BSS V14.3

Copyright © 2000--2006 Nortel Networks Observation Counter Dictionary

Checked the S12000 introduction impact on this NTP.

PE/DCL/DD/0125 Standard 15.154/EN May 2006 Copyright © 2000--2006 Nortel Networks

Issue 14.06/EN Preliminary

Issue 14.04/EN Preliminary

SYSTEM RELEASE: GSM/BSS V13

Issue 13.07/EN Standard

Copyright © 2000--2006 Nortel Networks Observation Counter Dictionary

PE/DCL/DD/0125 Standard 15.154/EN May 2006 Copyright © 2000--2006 Nortel Networks

– Normal DL TBF Release

Copyright © 2000--2006 Nortel Networks Observation Counter Dictionary

Issue 13.02/EN Preliminary

V13.1 release update after internal review

The following changes were made in individual chapters:

PE/DCL/DD/0125 Standard 15.154/EN May 2006 Copyright © 2000--2006 Nortel Networks

• created new Paragraph 1.6.3 “Correspondence between BSC 2G and BSC e3

The following changes were made in individual chapters:

Copyright © 2000--2006 Nortel Networks Observation Counter Dictionary

• created Paragraph 1.6.2 “Raw counter configuration (BSC e3)” with

System release: GSM/BSS V12

– Dedicated channel assignment: mode modify, Paragraph 1.2.3.2

PE/DCL/DD/0125 Standard 15.154/EN May 2006 Copyright © 2000--2006 Nortel Networks

• updated Paragraph 2.8.2:

Copyright © 2000--2006 Nortel Networks Observation Counter Dictionary

PE/DCL/DD/0125 Standard 15.154/EN May 2006 Copyright © 2000--2006 Nortel Networks

Copyright © 2000--2006 Nortel Networks Observation Counter Dictionary

V12.4 release update after internal review

PE/DCL/DD/0125 Standard 15.154/EN May 2006 Copyright © 2000--2006 Nortel Networks

2 Observation counter incrementation and DFDs . . . . . . . . . . . . . . 2--1

Copyright © 2000--2006 Nortel Networks Observation Counter Dictionary

3 BSS Observation management principles . . . . . . . . . . . . . . . . . . . . 3--1

PE/DCL/DD/0125 Standard 15.154/EN May 2006 Copyright © 2000--2006 Nortel Networks

3.2.2 Observation domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--2

4 Type and class of counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--1

Copyright © 2000--2006 Nortel Networks Observation Counter Dictionary

4.1.21 Intra--bss handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--36

PE/DCL/DD/0125 Standard 15.154/EN May 2006 Copyright © 2000--2006 Nortel Networks

4.7.2 PCUSN Observation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--100

5 Counter description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-- 1

Appendix A V15 Release counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6--1

Copyright © 2000--2006 Nortel Networks Observation Counter Dictionary