411-9001-125.15.54_OBS

Wireless Service Provider Solutions

Observation Counter DictionaryPE/DCL/DD/0125 15.54/EN Standard March 2005411--9001--125

Copyright © 2000--2005 Nortel Networks

< 125 > : Observation Counter Dictionary

Wireless Service Provider Solutions

Observation Counter DictionaryDocument number: PE/DCL/DD/0125

411--9001--125Document status: StandardDocument issue: 15.54/ENProduct release: GSM/BSS V15.1RDate: March 2005

Copyright © 2000--2005 Nortel Networks, All Rights Reserved

Originated in France

NORTEL NETWORKS CONFIDENTIAL:

The information contained in this document is the property of Nortel Networks. Except as specifically authorized inwriting by Nortel Networks, the holder of this document shall keep the information contained herein confidential andshall 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 inany form without prior written consent of Nortel Networks.

The following are trademarks of Nortel Networks: *NORTEL NETWORKS, the NORTEL NETWORKS corporate logo,the NORTEL Globemark, UNIFIED NETWORKS, BSC6000, 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--2005 Nortel Networks

Publication HistoryNortel Networks Confidential iii

Observation Counter DictionaryCopyright © 2000--2005 Nortel Networks

PUBLICATION HISTORY

SYSTEM RELEASE: GSM/BSS V15.1R

March 2005

Issue 15.54/EN Standard

Feature Id 26319 Customized SDOCounter List &Upgrade: added section 1.1.2.3.

Update after internal review

January 2005

Issue 15.53/EN Preliminary

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


Synchronized with V15.0 Standard

Feature Id 20571: DFD in section 1.2.10 for ASCI deleted. DFDs for main callscenarios replace the previous ones.

counter name updates in section 1.5.2.2

Dictionnary presentation moved from end of section 1 to beginning of section 2.

Updated locators for counters 1821 to 1827

August 2004


Feature Id 20571: Added counter 1193/8 in several places.

Feature Id 24462: updated Data Flow Diagram in section 1.2.10

CR Q00814652: added counters 1821 to 1827 in section 2.2

CR Q00934254: updated counters 1812, 1813, 1057, 1700, 1810, 1611, 1746 insection 2.2

Updated Appendix for V15.1R counter evolutions

Publication History Nortel Networks Confidentialiv

PE/DCL/DD/0125411--9001--125

Standard 15.54/EN March 2005 Copyright © 2000--2005 Nortel Networks

Reorganized Appendix for V15.x evolutions

July 2004

Issue 15.50/EN Draft

Feature Id 20571: added section 1.2.10 for ASCI.

Feature Id 23003: added section 1.2.2.2 for OTDI. updated counters 1722/0,1722/1, 1723, 1724 and 1725

Feature Id 23717: added section 1.1.4 for Mobility Class Sensitivity Counters

Feature Id 24462: added Data Flow Diagram in section 1.2.10

Feature Id 26310: updated section 1.1.1.3. Added section 1.1.1.5

Feature Id 26479: added section 1.1.2.3 for BSCcounterlist size

SYSTEM RELEASE: GSM/BSS V15.0

October 2004

Issue 15.25/ENStandard -- CRQ00956244 removeCounters 3002, 3003, 3006, and3007 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


Publication HistoryNortel Networks Confidential v


CR Q00956890 -- updated counter 1803/4.


CR Q00956244 -- updated notes (Stating not implemented for v14.3 or v15) oncounters 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 counters1065/1, 1066/1, 1067/1, and 1068/1.


Preparation for Helmsman release

July 2004


CR Q00941508 -- multiple changes and additions from comments CR.

July 2004


CRQ00937150--02 -- Incorporated CR comments to correct Formulas and updatedcounters 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. Alsoplaced them into the appropriate tables.


Added counters 1138/2/3/8 in Chapters 1, 2, and Appendix A for Feature 27215

Publication History Nortel Networks Confidentialvi

PE/DCL/DD/0125411--9001--125


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

CR Q00918747 -- Removed counter 1052/0, 1052/1, and 1052/2, replaced withcounter 1611/0 and 1611/1.

June 2004


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

May 2004


Incorporated Counter name changes 1772/0, 1772/1, and 1773/0, 1773/1 receivedfrom email remarks.

Incorporated Counter definitions 15132/0 thru 15189/0 received from emailremarks.

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 fromErroneous_Frame_Number to ECU_Activation.

April 2004


Publication HistoryNortel Networks Confidential vii


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> andcardSynthLoadTscb<x>.

March 2004


For CR Q00835972--01, deleted information concerning the 1835cardSynthLoadBscb<x>Moy/Max counters.

For CRQ00792758, changed the description of SDCCH and changed the functionsof 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

January 2004


For CR Q00707442--01, incorporated minor changes.

December 2003

Issue 15.01/EN DraftModified 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

Publication History Nortel Networks Confidentialviii

PE/DCL/DD/0125411--9001--125


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,

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)

Publication HistoryNortel Networks Confidential ix


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

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)

Publication History Nortel Networks Confidentialx

PE/DCL/DD/0125411--9001--125


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--Rawpermanent 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)

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 inCCCH

– Establishment of an UL TBF during DL TBF

– Normal UL TBF release

Publication HistoryNortel Networks Confidential xi


– Abnormal release of an UL TBF due to non progression of V(Q)

– Abnormal releaseof anULTBFdue to nonprogression ofV(Q) during fullduplex 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 casethat the DL TBF is also released

– Non response from the mobile after UP_NASSIGNMAX Packet UplinkAssignment messages

– Non progression from the mobile after UP_NASSIGNMAX PacketUplink Assignment messages during full duplex transfer, in the case thatthe DL TBF is also released

– Non response from the mobile after N3103 Packet Uplink Ack/Nack sentwith FAI=1

– Non response from the mobile after N3103 Packet Uplink Ack/Nack sentwith FAI=1 during full transfer, in the case that theDLTBF is also released

– Paging procedure initiated by the network for downlink packet transfertowards a MS in standby state

– Downlink establishment towards a mobile in Ready State and Packet IdleMode

– Establishment with Packet Downlink Assignment and Packet TimeslotReconfigure

– Normal DL TBF Release

– Abnormal release of an DL TBF due to non progression of V(A)

– Abnormal releaseof anDLTBFdue to nonprogression ofV(A) during fullduplex 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=1during full duplex transfer, in the case that the UL TBF is also released

– Non response from the mobile after DN_NASSIGNMAX PacketDownlink Assignment messages

– Non response from the mobile after DN_NASSIGNMAX PacketDownlink Assignment messages during full duplex transfer, in the casethat the DL TBF is also released

– Non response from the mobile after NN0002 downlink data blocks sentwith FBI=1 and S/P=1

Publication History Nortel Networks Confidentialxii

PE/DCL/DD/0125411--9001--125


– Non response from the mobile after NN0002 downlink data blocks sentwith FBI=1 and S/P=1 during full duplex transfer, in the case that the ULTBF is also released

– Preemption of radio timeslots

– Cell reselection from cell A to cell B and establishment of a new uplinkTBF in cell B

• Created newparagraph 1--6 “RawPermanent PCUSNObservationCounters”

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




– 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


Publication HistoryNortel Networks Confidential xiii


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”

• updatedParagraph 1.6.2.1 “Rawpermanent counters settable by theoperator”

• created new Paragraph 1.6.3 “Correspondence between BSC 2G and BSC e3Counters”

• 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


Publication History Nortel Networks Confidentialxiv

PE/DCL/DD/0125411--9001--125




• updated Paragraph 1.1.1.1 “Observation types” with completion of the V13release column

• created Paragraph 1.2.2.3 “Abnormal Completions” with integration of thefollowing 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 counterconfiguration (BSC 2G)”

• created Paragraph 1.6.2 “Raw counter configuration (BSC e3)” withintegration of the counters 3000/n to 3008/n


• created Paragraph 2.3 “Raw permanent BSS counters (BSC e3) withdescription of the following counters:

– 3000/n to 3008/n

Appendix A “V13 Release Counters”

• created Paragraph A.1 “V13 release counters”

• created ParagraphA.1.1 “NewV13 counters”with integration of the counters3000/n to 3008/n

Publication HistoryNortel Networks Confidential xv


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 beforeRELEASE INDICATION), Paragraph 1.2.5.1

– Radio channel release (RELEASE INDICATION received beforeDEACTIVATE 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”

• updated Paragraph 2.8.2:

– removed all the fields (Q3 name, Object, Function, Event, etc.) of PCUcounters 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

Publication History Nortel Networks Confidentialxvi

PE/DCL/DD/0125411--9001--125


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 onTRAFFIC 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 BSCattempted to preempt a PDTCH to make a TCH channel),Paragraph 1.2.7.3


• updated existing “Dataflows” fields and created new ones

April 2001




• created Paragraph 1.2.7 “GPRS” and added three data flowdiagrams (DFDs):

– GPRS procedure (normal completion)

– GPRS procedure (no resource available for PDTCH preemption)

– GPRS procedure (negative acknowledgement by the PCU after a PDTCHpreemption)

– gave the list of the 193 counters impacted by the circuit/packet aspect

Publication HistoryNortel Networks Confidential xvii


• 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/0nbSamplesUpQuality and 15053/1 nbSamplesDnQuality

– NK10371: corrected counter number for counters 15058/2dnTbfImmediateAssignment and 15058/1upTbfImmAssigRejectNoPdch

– 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 andpreempted PDTCH

• updated the availability date of PCUSN counters (Paragraph 2.8)

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

Publication History Nortel Networks Confidentialxviii

PE/DCL/DD/0125411--9001--125


January 2001





– SR 30330395 (30430423): removed C15057/5 lossOfComNT1001

– SR EE00526 (30340254): added toC9500 bscSdcchAveragedUsedMoy/Max/Ech/Cum and toC9501 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 onadjacentCellHandOver object

• completed the description of C1161/5, and C1629/0

• added three synthetic GSM--R specific counters: C8912, C8913, and C8919

June 2000




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 V11specific counters

Publication HistoryNortel Networks Confidential xix


• 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 createdfor 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 observationprinciples” which was removed from Manual < 07 >.

Chapter 2 “Counter description” contains the former Chapter 5 “Dictionary ofobservation counters” which was removed from Manual < 07 >.

Table of contents Nortel Networks Confidentialxx

PE/DCL/DD/0125411--9001--125


About this document 0--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Applicability 0--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Precautionary message 0--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Audience 0--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Prerequisites 0--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How this document is organized 0--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Vocabulary conventions 0--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 Introduction 1--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 BSS observations 1--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1.1 Observation management principles 1--3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1.2 Observation counters 1--4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1.3 Observation classes 1--9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1.4 Mobility Class Sensitivity Counters 1--9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 Observation counter incrementation principles and data flow diagram (DFD) 1--10. . . .

1.2.1 Radio resource allocation 1--10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.2 Call setup 1--12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.3 Dedicated channel assignment 1--49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.4 Handovers 1--66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.5 Resource release 1--93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.6 SMS service 1--113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.7 GPRS 1--117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.8 BSC equipment 1--142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.9 PCUSN 1--143. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.10 Advanced Speech Call Items (GSM--R) 1--201. . . . . . . . . . . . . . . . . . . . . . . . . .

1.3 Permanent bsc observation counters 1--205. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.1 Counter classes 1--205. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.2 Common control channel monitoring 1--205. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.3 Radio resource allocation 1--205. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.4 Interferences 1--208. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.5 Call setup 1--210. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.6 Dedicated channel assignment 1--210. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.7 Directed retry handovers 1--212. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.8 Handovers 1--212. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.9 Radio resource release 1--217. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.10 SMS service 1--220. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of contentsNortel Networks Confidential xxi


1.3.11 Layer 1 management 1--221. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.12 A interface 1--221. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.13 Abis interface 1--222. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.14 BSS/OMC--R link 1--222. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.15 PCM links 1--222. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.16 BSC equipment 1--223. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.17 GPRS 1--224. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.18 ASCI (GSM--R V12, V15) 1--226. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.19 Counter configuration 1--227. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4 Temporary observation counters 1--228. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4.1 SS7 links 1--228. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4.2 Abis interface 1--229. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.5 BSS Permanent observation counters configuration 1--230. . . . . . . . . . . . . . . . . . . . . . . . .

1.5.1 Raw counters configuration (all BSC) 1--230. . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.5.2 Correspondence between BSC2G and BSC e3 counters 1--255. . . . . . . . . . .

1.5.3 Synthetic counters configuration 1--256. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.6 Raw Permanent PCUSN Observation Counters 1--260. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.6.1 PCUSN Observation Classes 1--260. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.6.2 PCUSN Observation Types 1--262. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.6.3 Throughput Counters and Satisfaction Rate Counters 1--269. . . . . . . . . . . . . .

2 Counter description 2--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.1 Dictionary presentation 2--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.1 Dictionary contents 2--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.2 Observation counter references 2--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.3 Counter definition 2--2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.4 Basic definitions 2--4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2 Raw permanent BSS counters (BSC 2G) 2--6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3 Raw permanent BSS counters (BSC e3, AMR) 2--353. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.1 Raw permanent BSS counters (BSC e3) 2--353. . . . . . . . . . . . . . . . . . . . . . . . .

2.3.2 Raw permanent BSS counters (AMR) 2--368. . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4 Raw temporary counters (odiag excluded) 2--432. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.1 Temporary Interference observation 2--432. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.2 Temporary SS7 link observation 2--432. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.3 Temporary Abis interface observation 2--435. . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5 Synthetic permanent BSS counters 2--444. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.6 Raw permanent md counters 2--494. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.6.1 SYBASE counters 2--494. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of contents Nortel Networks Confidentialxxii

PE/DCL/DD/0125411--9001--125


2.6.2 SCSE counters 2--498. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.6.3 UNIX counters 2--499. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.6.4 Q3 counters 2--504. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.7 Raw permanent manager counters 2--517. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.7.1 SYBASE counters 2--517. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.7.2 X.25 counters 2--521. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.7.3 UNIX counters 2--522. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.8 Raw permanent PCUSN counters 2--526. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix A Release counters 3--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of figuresNortel Networks Confidential xxiii


Figure 1--1 Guidelines for locating a BSS observation counter 1--2. . . . . . . . . . . . . . . . . . . . . .

Figure 1--2 Observation Classes 1--261. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

About this documentNortel Networks Confidential 0--1


ABOUT THIS DOCUMENTThis Observation Counter Dictionary is a reference guide describing all GSMBSSnetwork observation counters managed through the OMC--R.

Applicability

This document applies to theGSM850, GSM900, GSM1800, andGSM1900 digitalwireless systems.

The present edition of the dictionary applies to V15.1R BSS operations by default.

In the V15.1R release, the OMC--R manages V15, V14.3, and V12 BSSs withBSC/TCU 2G. The user is informed when it is necessary to refer to specificsubsystem features.

TheV15.1R software release does not support BSCe3 and TCUe3 and theirassociated features are not available in this release

The Observation Counter Dictionary is part of the BSS NTP Suite. It is closelyassociated with the following manuals:

TheBSSOperating Principlesmanual (NTP < 07 >) describes general operatingprinciples and explains the mechanisms that enable Man-Machine interfacecommands.

The BSS Parameter Dictionary (NTP < 124 >) contains all the parameters usedin OMC--R commands.

The OMC--R User Manual (NTPs < 128 >, < 129 > and < 130 >) is auser-oriented guide to performing Human-Machine interface commands.

The BSS Operating Procedures Manual (NTP < 34 >) describes variousprocedures that help users operate or reconfigure a BSS.

Precautionary message

The following message:

CAUTIONGSM--R specific

Indicates that specific equipment and specific software (such asspecific software in the BSC) dedicated to Railway application isused and that the feature is therefore not available for all standardGSM users.

GSM--R specific counters listed in this dictionary contain “(GSM--R V12)” in the“Feature” field.

About this document Nortel Networks Confidential0--2

PE/DCL/DD/0125411--9001--125


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

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 two main chapters:

Chapter 1 “Introduction” contains general information on observation counters.

Chapter 2 “Counter description” describes all the observation counters listed byfamilies, and explains their use.

Appendix A “V15 release counters” highlights the differences between V15,V14, V13, and V12 release observation counters.

Vocabulary conventions

The glossary is presented in Manual < 00 >.

IntroductionNortel Networks Confidential 1--1


1 INTRODUCTIONThis chapter contains the following information:

After a brief reminder of the principles underlying BSS observations detailed inNTP < 07 >, the structure and contents of the BSS observation counters, withtheir accounting algorithms, are described and the observation classes defined(see Paragraph 1.1).

Then the various diagrams illustrate the principles underlying counterincrements based on the traffic management procedures executed by the BSC(see Paragraph 1.2).

The following paragraphs list:

• the raw permanent BSS observation counters (see Paragraph 1.3)

• temporary observation counters appearing in V12 BSS observation reports(see Paragraph 1.4) and BSC V15 2G

Counters are listed according to their class and are identified by their number andQ3 name. The type is also indicated.

The four observation types (ORT, OFS, OGS, and ODIAG) available withpermanent observation counters are described in Paragraph 1.5.

The structure of the Dictionary is presented in Paragraph 2.1.

The following figure provides the user with guidelines for locating a BSSobservation counter in the dictionary of counters, starting from different points.

Introduction Nortel Networks Confidential1--2

PE/DCL/DD/0125411--9001--125


Starting point

See Paragraphs1.3 to 1.5

See the index ofcounters at the end

of the manual

The type and class ofthe counter are known

(for example:permanent/handover)

The Q3 name of thecounter is known

(for example: assign-Failure)

The number of thecounter is known(for example: 1055)

Search for the counter in the Dictionary of counters(numerical lists in Chapter 2)

Figure 1--1 Guidelines for locating a BSS observation counter



1.1 BSS observations

1.1.1 Observation management principles

1.1.1.1 Observation types

BSS observations covers the following:

BSS permanent observation

• General statistic observation (OGS) (a preview of the report is visible in theperformance window at the OMC--R)

• Fast statistic observation (OFS) (visible in theReport windowat theOMC--R)

• Real time observation (ORT) (a preview of the report is visible in thePerformance 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:

Observation typeBSC type

Observation typeBSC 2G BSC e3

OGS X X

OFS X X

ORT X X

Temporary Interference X

Temporary Abis Interface X

Temporary SS7 Link XODIAG X X

1.1.1.2 Observation management

BSS observations are activated by creating mdScanner objects whosemdGranularityPeriod attribute defines the periods at which the observationcounters are read and transferred to the OMC--R agent.

When a BSS observation is activated, all the related counters start counting. Whenthe observation is deactivated, the counters stop counting; they are no longercollected.


PE/DCL/DD/0125411--9001--125


1.1.1.3 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, andBSS/OMC--R link

1.1.1.4 Observation domains

The evaluation of network performance based on the results of radio entityobservation covers four domains:

traffic load

quality of service

resource availability

network configuration control

1.1.1.5 Observations and alarms

Observations can have an associated threshold.

Performance management can generate an alarm when a threshold is crossed on agiven observation. This mechanism applies to:

BSS GSM observations

BSS PCU (GPRS) observations

1.1.2 Observation counters

1.1.2.1 Counter types

There are three types of observation counter:

totalizer

value

load



1.1.2.2 Counter contents

Header

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, value, load)

COUNTER IDENTIFIER identifies the observation counter. This identifier is relatedto the counting function

SCREENINGCRITERIA is used when an event occurs which can be expanded to givemore information, and a counter is required to be maintained for each sub--class ofinformation.

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

Value counters

This type of counter provides average values from raw counts obtained by internalsampling (the time interval between two events is variable and is not accessible tousers). It can also provide a maximum value.

It contains three additional fields:

CUMULATED VALUE

NUMBER OF SAMPLES

MAX VALUE (if required)


PE/DCL/DD/0125411--9001--125



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

Load counters

This type of counter provides average values from raw counts obtained by internalsampling (the time interval between two events is variable and is not accessible tousers). 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 minimumcount)

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

1.1.2.3 Counter names

On top of itsQ3 name, you can assign a customizedname to any observation counterat the SDO level. This customized name is defined at the SDO level and is keptthrough SDO upgrades.

All counters added to the SDO counter list during an upgrade can get a customizedname at upgrade time. The upgrade procedure gets customized names from adedicated 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> <occurence id> <type ofcounter>”

To enable this feature:

1 Click the Data Format tab on the SDO MMI

2 Set the ”Counter name” field to ”custom”

1.1.2.4 Number of counters

A BSC can make a limited number of observations. Refer to the following table toknow about this limitations per BSC type and version.

BSC type BSC version Number of distinctcounters Ids observed

BSC memory threshold

BSC 2GV12 200 900

BSC 2GV15 350 1000


PE/DCL/DD/0125411--9001--125


BSC type BSC memory thresholdNumber of distinctcounters Ids observed

BSC version

BSC e3V14.3 300 1500

BSC e3V15 350 1500

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.

Number of counter Ids per observation type

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

Use of BSC memory

To ensure correct performance, BSC memory use must not exceed a limit given bythe following formula:

CELL_OFS + CELL_OGS + (NEIGH_OGS + NEIGH_OFS)*nb_neigh +(TDMAcla_OGS + TDMAcla_OFS)*nb_TDMA_classes < THRESHOLD

If BSC memory use is greater than this threshold, a warning message will ask youto remove some counters in the bsc counter list.

Name Meaning

CELL_OFS number of counter screenings (couple id:subid) per cellon OFS observation

CELL_OGS number of counter screenings (couple id:subid) per cellon OGS observation

NEIGH_OFS number of counter screenings (couple id:subid) perneighboring cell on OFS observation

NEIGH_OGS number of counter screenings (couple id:subid) perneighboring cell on OGS observation

nb_neigh number of neighboring cells per cell (=32)

TDMAcla_OFS number of counter screenings (couple id:subid) pertdma on OFS observation

TDMAcla_OGS number of counter screenings (couple id:subid) pertdma on OGS observation

nb_TDMA_classes 2

THRESHOLD 1000 for a BSC2G

1500 for a BSCe3



1.1.3 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

1.1.4 Mobility Class Sensitivity CountersOn some counters, this facility provides the operator with statistics indexed by theMS power class (2 W, 8 W or 2 W and 8 W). This measure the QoS by type ofapplication (train control, shunt). The operator can toggle between ignoring/takinginto account the power class criterium at the OMC-R. To get significant measures,it is recommended to:

3 stop observation counters.

4 toggle the power class criterion.

5 start observation counters again.


PE/DCL/DD/0125411--9001--125


1.2 Observation counter incrementation principles and dataflow diagram (DFD)

1.2.1 Radio resource allocation

1.2.1.1 SDCCH allocation request

SDCCH allocation request

SDCCH resource

No

No handover in--progressand TCH resource

No

sdcchRessourceFailure

Yes sdcchAllocatedsdcchAveragedUsedallSdcchAllocatedTime (possibly)

Yes tchFrAllocated (cause = Overflow)tchFrAveragedUsed (cause = Overflow)allTchFrAllocatedTime (possibly)

available

available

1.2.1.2 TCH allocation request in primo-allocation

TCH allocation request in primo--allocation

TCH resource

No

SDCCH resource

No

tchFrRessourceFailure

Yes

Yes

tchFrAllocated (cause = Primo--allocation)tchFrAveragedUsed (cause = Primo--allocation)allTchFrAllocatedTime (possibly)

sdcchAllocatedsdcchAveragedUsedallSdcchAllocatedTime (possibly)

available

available



1.2.1.3 TCH allocation request for traffic

Attempt of allocation

TCH resourceavailable

No

Yes tchFr/HrAllocated (cause = TCH channel)tchFr/HrAveragedUsed (cause = TCH channel)allTchFrAllocatedTime (possibly)

of a TCH

Request can be queued

No

tchFr/HrResourceFailure

Yes tchAverageQueueLength (cause highest priority or internalpriority)

Each time a queueingrequest is served(set from a queueto the TCH pool)

tchFr/HrAllocated (cause = TCHchannel)

tchFr/HrAveragedUsed (cause =TCH channel)

allTchFrAllocatedTime (possibly)

tchQueueingDuration

tchAverageQueueLength (cause =highest priority or internal priority)

tchQueueingExpiration (cause =highest priority or internal priority)tchAverageQueueLength (cause =highest priority or internal priority)tchQueueingDuration

Each time a queueingrequest is extractedfrom a queue on timer

expiration


PE/DCL/DD/0125411--9001--125


1.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 assignmentprocedure.



1.2.2.1 Immediate assignment procedure (normal completion)

Data Flow Diagram: immediate assignment procedure (normal completion)

Set timer TchnAck

Reset timer TchnAck

Set timer T3101

Reset timer T3101

MS BTS BSC MSCCHANNEL_REQUEST CHANNEL_REQUIRED

174817021191/n (1)1730 (1)160616071744 (2)1746 (2)1609/2 (2)1611/2 (2)

CHANNEL_ACTIVATE

17491192/n

1629/0CHANNEL_ACTIVATE_ACK

IMMEDIATE_ASSIGNMENT_COMMAND

ESTABLISH_INDICATION

17501193/n1195 or 1196

11081502

IMMEDIATE_ASSIGNMENT

SABM(CM_SERVICE REQUEST)

CONNECTION_REQUEST(L3_INFORMATION

CM_SERVICE_REQUEST)

CONNECTION_CONFIRM

11051104/0START_MEASUREMENT_REQUEST

START_MEASUREMENT_REQ_ACK

DTAP (CM_SERVICE_ACCEPT)

11071501DTAP (CM_SERVICE_ACCEPT)

CM_SERVICE_ACCEPT

ALERTINGDTAP (ALERTING)

DTAP (ALERTING)

11081500

(1) The following counters are incremented depending on the cause value in theCHANNEL REQUIRED message:

1191 cause 000


PE/DCL/DD/0125411--9001--125


1191/1 and 1730 for cause 001

1191/2 for cause 010


1191/4 and 1730 for cause 100




(2) Since V9 releases, the following modifications have been performed:

1606 instead of 1034




(3) If no SDCCH is available, the BSCmay try to allocate a TCH in signalingmode.In this case, the following counters are incremented:

1744, 1746, 1609/2, 1611/2

List of the counters incremented during this procedure:

Counternumber

Counter name Function

1104/0 sccpAllocated number of SCCP connections forSSN BSSMAP in the BSC

1105 sccpAveragedUsedMoy/Max/Cum/Ech

average number of SCCPconnections established

1107 aInputMessage number of BSSAP messagesreceived by the BSC

1108 aOutputMessage number of BSSAP messages sent bythe BSC

1191/n[n= 0 to 7]

channelRequestCauseXxx number of channel allocationrequests: Cause xxx

1192/n[n= 0 to 7]

immediateAssignmentSuccessCauseXxx

number of successful immediateassignments: Cause xxx

1193/n[n= 0 to 3]

estabIndicSignallingCauseXxx

number of ESTABLISH INDICATIONmessages in establishment phasereceived for mobile originating calls:Cause Xxx

1195 estabIndicSigPhaseI number of ESTABLISH INDICATIONmessages in establishment phasereceived for Phase I mobiles



Counternumber

FunctionCounter name

1196 estabIndicSigPhaseII number of ESTABLISH INDICATIONmessages in establishment phasereceived for Phase II mobiles

1500 aTransparentUp number of DTAP messages sent bythe BSC to the MSC

1501 aTransparentDown number of DTAP messages received

1502 aNonTransparentUp number of BSSMAP messages sentby the BSC

1606 sdcchAllocatedTrZone number of SDCCH allocated in thezone (concentric cell)

1607 sdcchAveragedUsedTrZoneMoy/Max/Cum/Ech

average number of SDCCHs used inthe inner or outer zone of the cell

1609/2 tchFrAllocatedOverflowAllocationTrZone

number of TCH/FR allocated in theinner or outer zone of the cellbecause of SDCCH unavailability

1611/2 tchFrAveragedUsedOverflowAllocationTrZoneMoy/Max/Cum/Ech

average and maximum number ofTCH/FR used in the inner or outerzone of the cell because of SDCCHunavailability

1629/0 channelActivateSignallingFullRate

number of Full Rate channelsactivated for signaling

1702 channelRequestExtended number of receipt of CHANNELREQUIRED message with a timingadvance greater than 63

1730 pagingResponse number of responses to pagingrequests in the cell

1744 tchFrAllocated

ortchFrAllocatedTrZone

number of TCH/FR or preemptedPDTCH allocated in the cellornumber of TCH/FR or preemptedPDTCH allocated in the inneror outer zone of the concentric cell

1746 tchFrAveragedUsedMoy/Max/Cum/EchortchFrAveragedUsedTrZoneMoy/Max/Cum/Ech

average number of TCH/FR orpreempted PDTCH used in the celloraverage number of TCH/FR orpreempted PDTCH used in the inneror outer zone of the cell


PE/DCL/DD/0125411--9001--125


Counternumber


1748 channelRequest number of channel allocation requests

1749 immediateAssignmentSuccess

number of successful immediateassignments

1750 estabIndicSignalling number of ESTABLISH INDICATIONmessages in establishment phasereceived

1.2.2.2 Immediate assignment procedure with OTDI (normal completion)

This procedure used to establish group calls (VCS or VGCS) includes OriginatorTo Dispatcher Information (OTDI) in the setup message.



Set timer TchnAck

Reset timer TchnAck

Set timer T3101

Reset timer T3101

MS BTS BSC MSCCHANNEL_REQUEST CHANNEL_REQUIRED

174817021191/n (1)1730 (1)160616071744 (2)1746 (2)1609/2 (2)1611/2 (2)

CHANNEL_ACTIVATE

17491192/n



est_ind(immediate_setup2(call Id,OTDI))

17501193/n1195 or 1196

110815021722


SABM(immediate_setup2(call ID,OTDI))

CONNECTION_REQUEST(immediate_setup2, call Id,

OTDI)

CONNECTION_CONFIRM

11051104/0START_MEASUREMENT_REQUEST


DTAP (CM_SERVICE_ACCEPT)


CM_SERVICE_ACCEPT

ALERTINGDTAP (ALERTING)

DTAP (ALERTING)

11081500


PE/DCL/DD/0125411--9001--125


1.2.2.3 Paging procedure

Data Flow Diagram: immediate assignment: paging procedure (normalcompletion)

MS BTS BSC MSCPAGING_REQUEST

11081502

CONNECTION_REQUEST(PAGING_RESPONSE)

Set timer TchnAck

Reset timer TchnAck

PAGING_COMMAND

Set timer T3101

Reset timer T3101

CHANNEL_REQUIRED

CHANNEL_ACTIVATE

1629/0

CHANNEL_ACTIVATE_ACK


17491192/n

11071503PAGING_COMMAND

CHANNEL_REQUIRED174817021191/n (1)1730 (1)160616071744 (2)1746 (2)1609/2 (2)1611/2 (2)

IMMEDIAT_ASSIGNMENT

SABM (PAGING_RESPONSE)ESTABLISH_INDICATION

CONNECTION_CONFIRM

11051104START_MEASUREMENT_REQUEST


DTAP (SETUP)

11071501DTAP (SETUP)

DTAP (ALARTING)

SETUP

ALERTING

DTAP (ALARTING)

11081500

17501193/n1195 or 1196





1191/1 and 1730 for cause 001



1191/4 and 1730 for cause 100










1744, 1746, 1609/2, 1611/2


Counternumber







1191/n[n= 0 to 7]


1192/n[n= 0 to 7]



1193/n[n= 0 to 3]




PE/DCL/DD/0125411--9001--125


Counternumber





1501 aTransparentDown number of DTAP messages received


1503 aNonTransparentDown number of BSSMAP messagesreceived by the BSC from the MSC






1611/2 TchFrAveragedUsedOverflowAllocationTrZoneMoy/Max/Cum/Ech






1744 tchFrAllocated


number of TCH/Fr or preemptedPDTCH allocated in the cellornumber of TCH/FR or preemptedPDTCH allocated in the inner or outerzone of the concentric cell






Counternumber





1.2.2.4 Abnormal completions

No resource available (SDCCH)

Data Flow Diagram: immediate assignment failure procedure: no resourceavailable (SDCCH)

MS BTS BSC MSC

IMMEDIATE_ASSIGNMENT_COMMAND(IMMEDIATE_ASSIGNMENT_REJECT)

CHANNEL_REQUIREDCHANNEL_REQUEST

17481191/0160817511611/1 (1)

IMMEDIATE_ASSIGNMENT_REJECT


Counternumber


1161/1 immediateAssignmentRejectRadioRes

number of immediate assignmentsrejected for lack of radio resources

1191/0 channelRequestCause000 number of channel allocationrequests: Cause 000

1608 sdcchResourceFailureTrZone

number of SDCCH allocation failuresdue to lack of SDCCH in the inner andouter zone of the cell


1751 immediateAssignmentReject number of immediate assignmentsrejected


PE/DCL/DD/0125411--9001--125


Negative reponse from the BTS

Data Flow Diagram: immediate assignment failure procedure: negative responsefrom BTS

MS BTS BSC MSC

Set timer TchnAck

Reset timer TchnAck

DEACTIVATE_ACK

CHANNEL_REQUEST

174817021191/n (1)1730 (1)160616071744 (2)1746 (2)1609/2 (2)1611/2 (2)


DEACTIVATE_SACCH

16061607

ACTIVATE_NEGATIVE_ACK

CHANNEL_REQUIRED

CHANNEL_ACTIVATE

1629/0

17511161/2


Set timer T3101

Reset timer T3101



1191/1 and 1730 for cause 001



1191/4 and 1730 for cause 100












1744, 1746, 1609/2, 1611/2


Counternumber


1161/2 immediateAssignmentRejectChanActNack

number of immediate assignmentsrejected because a CHANNELACTIVATE NACK message isreceived

1191/n[n= 0 to 7]


1606 sdcchAllocatedTrZone number of SDCCH allocation in theinner and outer zone of the cell

1607 sdcchAverageUsedTrZoneMoy/Max/Cum/Ech

average and maximum number ofSDCCHs used in the inner or outerzone of the cell




average and maximum number ofTCH/FR used in the inner or outerzone of the cell because of SDCCHunavailability, obtained throughinternal sampling


number of Full Rate channels(SDCCH or TCH/FR) activated forsignaling in the cell



1744 tchFrAllocated


number of TCH/FR allocated in thecellornumber of TCH/FR allocated in theinneror outer zone of the concentric cell


PE/DCL/DD/0125411--9001--125


Counternumber


1746 tchFrAveragedUsedMoy/Max/Cum/Ech

average number of TCH/FR used inthe inner or outer zone of theconcentric cell



No response to CHANNEL ACTIVATE

Data Flow Diagram: immediate assignment failure procedure: no response toCHANNEL ACTIVATE

MS BTS BSC MSC

Set timer TchnAck

Reset timer TchnAck

CHANNEL_REQUEST

174817021191/n (1)1730 (1)160616071744 (2)1746 (2)1609/2 (2)1611/2 (2)


CHANNEL_REQUIRED

CHANNEL_ACTIVATE

1629/0


Set timer T3101

Reset timer T3101

1607

1751

1161/3



1191/1 and 1730 for cause 001





1191/4 and 1730 for cause 100










1744, 1746, 1609/2, 1611/2(1) Since V9 releases, the following modificationshave been performed:






Counternumber


1161/3 immediateAssignmentRejectChanActTimmack

number of immediate assignmentsrejected because of TimmAcktime--out elapse

1191/n[n= 0 to 7]










PE/DCL/DD/0125411--9001--125


Counternumber





1744 tchFrAllocated


number of TCH/FR allocated in thecellornumber of TCH/FR allocated in theinner or outer zone of the concentriccell







Incorrect first L3 message

Data Flow Diagram: immediate assignment failure procedure: timer T3101 expiry

MS BTS BSC MSC

Set timer TchnAck

Reset timer TchnAck

CHANNEL_REQUIRED

CHANNEL_ACTIVATE

1629/0ACTIVATE_NEGATIVE_ACK

IMMEDIATE_ASSIGNMENT_COMMAND(IMMEDIATE_ASSIGNMENT)

17491192/n

CHANNEL_REQUEST

174817021191/n (1)1730 (1)160616071744 (2)1746 (2)1609/2 (2)1611/2 (2)


Set timer T3101

Timer T3101 expired

RF_CHANNEL_RELEASE

RF_CHANNEL_RELEASE_ACK

Set timer TrfAck

Reset timer TrfAck

1607 (--1)



1191/1 and 1730 for cause 001



1191/4 and 1730 for cause 100





PE/DCL/DD/0125411--9001--125














Counternumber


1161/3 immediateAssignmentRejectChanActTimmack

number of immediate assignmentsrejected because of TimmAcktime--out elapse

1191/n[n= 0 to 7]

channelRequestCausexxx number of channel allocationrequests: Cause xxx

1192/n[n= 0 to 7]

immediateAssignmentSuccessCausexxx

number of immediate assignmentswith cause xxx satisfied













Counternumber


1744 tchFrAllocated







number of immediate assignmentssatisfied


PE/DCL/DD/0125411--9001--125


Timer 3101 expiry

Data Flow Diagram: immediate assignment failure procedure: incorrect first L3message

MS BTS BSC MSC

Set timer T3101

Reset timer T3101

CHANNEL_REQUIRED

CHANNEL_ACTIVATE

1629/0

ACTIVATE_NEGATIVE_ACK


17491192/n

CHANNEL_REQUEST

174817021191/n (1)1730 (1)160616071744 (2)1746 (2)1609/2 (2)1611/2 (2)


RF_CHANNEL_RELEASE


1607 (--1)

Set timer TchnAck

Reset timer TchnAck

SABMESTABLISH_INDICATION

CHANNEL_RELEASE

DEACTIVATE_SACCHSet timer TdeacAck

Reset timer TdeacAck1753

1778 Set timer T3109

Reset timer T31091163/4

Set timer T3111

Timer T3111 expires

DEACTIVATE_ACK

RELEASE_INDICATION

Set timer TrfAck

Reset timer TrfAck

CHANNEL_RELEASE

DISC

UA



(1) The following counters are incremented or decremented depending on the causevalue in the CHANNEL REQUIRED message:


1191/1 and 1730 for cause 001



1191/4 and 1730 for cause 100















List of the counters incremented or decremented during this procedure:

Counternumber


1163/4 signallingReleaseBtsIncFirstL3

number of communications insignaling phase release because ofincorrect First L3 message when acell is associated with thecommunication

1191/n[n= 0 to 7]

channelRequestCausexxx number of channel allocationrequests: Cause xxx

1192/n[n= 0 to 7]

immediateAssignmentSuccessCausexxx

number of immediate assignmentswith cause xxx satisfied


PE/DCL/DD/0125411--9001--125


Counternumber












1744 tchFrAllocated







number of immediate assignmentssatisfied

1753 signallingReleaseBts number of releases while thecommunication is in “signaling phase”and a cell associated to thecommunication

1778 signallingAbnormalReleaseCell

number of abnormal releases whilethe communication is in “signalingphase” and a cell associated to thecommunication

Traffic with the MSC close

Data FlowDiagram: immediate assignment failure procedure: trafficwith theMSCclosed



MS BTS BSC MSC


CHANNEL_REQUIREDCHANNEL_REQUEST

17481191/017511611/0 (1)



Counternumber


1161/0 immediateAssignmentRejectTraffMsc

number of immediate assignmentsrejected because the traffic with theMSC is interrupted

1191/0 channelRequestCause000 number of channel allocationrequests: Cause 000

1608 sdcchResourceFailureTrZone

number of SDCCH allocation failuresdue to lack of SDCCH in the inner andouter zone of the cell




PE/DCL/DD/0125411--9001--125


CONNECTION FAILURE indication

Data Flow Diagram: immediate assignment failure procedure: connection failureindication

MS BTS BSC MSC

11081502


CM_SERVICE_REQUEST)

Set timer T3101

Reset timer T3101

Set timer TdeacAck

CHANNEL_REQUIRED

CHANNEL_ACTIVATE



17491192/n

CHANNEL_REQUEST

174817021191/n (1)1730 (1)1606 (2)1607 (2)1744 (2)1746 (2)1609/2 (2)1611/2 (2)


SABM(CM_SERVICE_REQUEST) ESTABLISH_INDICATION

(CM_SERVICE_REQUEST)

17501193/n1195 or 1196

CONNECTION_CONFIRM

11051104

START_MEASUREMENT_REQUEST


DEACTIVATE_SACCH

CONNECTION_FAILURE

CLEAR_REQUEST

Set timer TchnAck

Reset timer TchnAck

1753177810441045

STOP_MEASUREMENT_REQUEST

11081502

Reset timer Tmea

DEACTIVATE_ACK

STOP_MEASUREMENT_ACK

Set timer TchnAck



MS BTS BSC MSC

1607 (--1)

Set timer TrfAck

Reset timer TrfAck

RF_CHANNEL_RELEASE


CLEAR_COMMAND

11071503

CLEAR_COMPLETE

Set timer T3109

Timer T3109 expires11081502

1105 (--1)

DISCONNECTED_INDICATION

Reset timer TdeacAck



1191/1 and 1730 for cause 001



1191/4 and 1730 for cause 100










1744, 1746, 1609/2, 1611/2


PE/DCL/DD/0125411--9001--125



Counternumber


1044 signallingPhaseDurationMoy/Max/Cum/Ech

average and maximum seizure ofsignaling channels expressed inmilliseconds, calculated on allallocations lasting more than 25milliseconds

1045 signallingPhaseDurationHighMoy/Max/Cum/Ech

average and maximum seizure ofsignaling channels expressed inmilliseconds, calculated on allallocations in the cell






1191/n[n= 0 to 7]


1192/n[n= 0 to 7]



1193/n[n= 0 to 3]






1503 aNonTransparentDown number of BSSMAP messages sentby the MSC








Counternumber








1744 tchFrAllocated




ortchFrAveragedUsedTrZoneMoy/Max/Cum/Ech


1748 ChannelRequest number of channel allocation requests

1749 ImmediateAssignmentSuccess


1750 EstabIndicSignalling number of ESTABLISH INDICATIONmessages in establishment phasereceived



number of abnormal releases whilethe communication is in “signalingphase” and a cell associated to thecommunication

ERROR indication

Data Flow Diagram: immediate assignment failure procedure: connection failureindication


PE/DCL/DD/0125411--9001--125


MS BTS BSC MSC

11081502


CM_SERVICE_REQUEST)

Set timer T3101

Reset timer T3101

Start timer Tend

Reset timer Tend

CHANNEL_REQUIRED

CHANNEL_ACTIVATE



17491192/n

CHANNEL_REQUEST

174817021191/n (1)1730 (1)1606 (2)1607 (2)1744 (2)1746 (2)1609/2 (3)1611/2 (3)




17501193/n1195 or 1196

CONNECTION_CONFIRM

11051104



RELEASE_REQUEST

ERROR_INDICATION

CLEAR_REQUEST

Set timer TchnAck

Reset timer TchnAck

175317781163/1810441045


11081502

Reset timer Tmea

Set timer Tmea

(4)

Set timer TrelREQ



MS BTS BSC MSC

1607 (--1)

Set timer TdeacAck


RF_CHANNEL_RELEASE


CLEAR_COMMAND

11071503

CLEAR_COMPLETE

Set timer T3109

Timer T3109 expires

11081502

1105 (--1)DISCONNECTED_INDICATION

RELEASE_CONFIRM

STOP_MEASUREMENT_ACK160116021603162216231624162516261805 (4)1806 (4)1807 (4)1808 (4)

Set timer TclrCMD

Reset timer TclrCMD

Set timer TrfAck

Reset timerr TrfAck

DEACTIVATE_SACCH

DEACTIVATE_ACK

Reset timer TrelREQ



1191/1 and 1730 for cause 001



1191/4 and 1730 for cause 100





PE/DCL/DD/0125411--9001--125








1744, 1746, 1609/2, 1611/2


(4) ASCI counters are optional since they are related to the GSM--R functionality.


Counternumber











1163/18 signallingReleaseBtsErrorIndDm

number of communications insignaling phase released because ofDM frames received in establishedmultiframe mode when a cell isassociated to the communication

1191/n[n= 0 to 7]


1192/n[n= 0 to 7]



1193/n[n= 0 to 3]





Counternumber






1601 downlinkPowerCtrlMaxSdcchMoy/Max/Cum/Ech

duration of maximum downlink poweruse on busy SDCCHs

1602 uplinkPowerCtrlMaxSdcchMoy/Max/Cum/Ech

duration of maximum uplink poweruse on busy SDCCHs

1603 connectionDurationSdcchMoy/Max/Cum/EchorconnectionDurationSdcchTrZoneMoy/Max/Cum/Ech

connection duration of SDCCHs(concentric cell)orconnection duration of SDCCHs(non--concentric cell)

1606 sdcchAllocatedTrZone number of SDCCHs allocated in theinner or outer zone of the cell







1622 msLostMeasurements

ormsLostMeasurementsTrZone

number of MS measurementmessages not received by the cellornumber of MS measurementmessages not received by the inner orouter zone of the cell

1623 rxLevDownLink

orrxLevDownLinkTrZone

sum of downlink signal strengthmeasurements received on the cellorsum of downlink signal strengthmeasurements received on the inneror outer zone of the cell


PE/DCL/DD/0125411--9001--125


Counternumber


1624 rxLevUpLink

orrxLevUpLinkTrZone

sum of uplink signal strengthmeasurements received on the cellorsum of uplink signal strengthmeasurements received on the inneror outer zone of the cell

1625 rxQualDownLink

orrxQualDownLinkTrZone

sum of downlink signal qualitymeasurements on the cellorsum of downlink signal qualitymeasurements on the inner or outerzone of the cell

1626 rxQualUpLink

orrxQualUpLinkTrZone

sum of uplink signal qualitymeasurements on the cellorsum of uplink signal qualitymeasurements on the inner or outerzone of the cell

1744 tchFrAllocated









1753 signallingReleaseBts number of releases while thecommunication is in ”signalling phase”and a cell associated to thecommunication


number of abnormal releases whilethe communication is in ”signallingphase” and a cell associated to thecommunication



Counternumber


1805 msPowerIncControl number of MS increment powercontrols ordered by the Layer 1management

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

1807 bsPowerIncControl number of BS increment powercontrols ordered by the Layer 1management

1808 bsPowerDecControl number of BS decrement powercontrols ordered by the Layer 1management


PE/DCL/DD/0125411--9001--125


Rejection from the MSC

Data Flow Diagram: immediate assignment failure procedure: rejection from theMSC

MS BTS BSC MSC

11081502


CM_SERVICE_REQUEST)

Set timer T3101

Reset timer T3101

CHANNEL_REQUIRED

CHANNEL_ACTIVATE



17491192/n

CHANNEL_REQUEST

174817021191/n (1)1730 (1)160616071744 (2)1746 (2)1609/2 (2)1611/2 (2)




17501193/n1195 or 1196

CONNECTION_CONFIRM

11051104



DATAREQ [05 22]

Set timer TchnAck

Reset timer TchnAck

Reset timer Tmea

Set timer Tmea



MS BTS BSC MSC

1607 (--1)

Set timer TdeacAck


RF_CHANNEL_RELEASE


CLEAR_COMMAND

CLEAR_COMPLETE

Set timer Tend

Timer T3111 expires

11081502

1105 (--1)DISCONNECTED_INDICATION

RELEASE_INDICATION


Reset timer TclrCMD

Set timer TrfAck

Reset timer TrfAck

DEACTIVATE_ACK

Reset timer Tend

1107150317531163/2010441045

(3)

CHANNEL_RELEASE

DEACTIVATE_SACCH


Set timer T3109

Reset timer T3109

Set timer T3111



1191/1 and 1730 for cause 001



1191/4 and 1730 for cause 100





PE/DCL/DD/0125411--9001--125








1744, 1746, 1609/2, 1611/2

(4) DTAP service is now open



Counternumber











1163/20 signallingReleaseBtsClearCommand

number of communications insignaling phase released because ofCLEAR COMMAND received when acell is associated to thecommunication

1191/n[n= 0 to 7]


1192/n[n= 0 to 7]



1193/n[n= 0 to 3]





Counternumber












1606 sdcchAllocatedTrZone number of SDCCHs allocated in theinner or outer zone of the cell










1623 rxLevDownLink




PE/DCL/DD/0125411--9001--125


Counternumber


1624 rxLevUpLink

orrxLevUpLinkTrZone


1625 rxQualDownLink



1626 rxQualUpLink



1744 tchFrAllocated












1.2.3 Dedicated channel assignment

Dedicated channel assignment procedures are used to modify previous radiochannel assignments.

1.2.3.1 Nominal procedure

This procedure is used to modify a channel type (change from SDCCH to TCH orchange of transmission mode) or to process handover requests.

Data Flow Diagram: dedicated channel assignment procedure (a MS switchingfrom an SDCCH to a TCH for service).


PE/DCL/DD/0125411--9001--125


MS BTS BSC MSC

ASSIGNMENT_COMMAND

CONN_STATE_REQ_ACK

110715031841/0174417461609/01611/0 (1)1812

CONN_STATE_REQ

10941095


ASSIGNMENT_COMMAND

10491715 (3)

ASSIGNMENT_REQUEST

SABM



UA

ASSIGNMENT_COMPLETE


Set timer TchnAck

Reset timer TchnAck

Set timer T3107

Reset timer T3107

CHANNEL_ACTIVATE

1197/0 or 1197/1or 1709 and 1705/n (2)or 1710 and 1707/n

160116021603162216231624162516261805180618071808 (4)

ASSIGNMENT_COMPLETE

10501716 (5)

ASSIGNMENT_COMPLETE

11081502START_MEASUREMENT_REQUEST

START_MEASUREMENT_ACK

RF_CHANNEL RELEASE

10441045

RF_CHANNEL RELEASE_ACK

1607(--1) (4)17171718171917201721

Set timer TrfAck

Reset timer TrfAck



(1) When a TCH resource is successfully allocated internally in the BSC software,the following counters are incremented:

1609/0 tchFrAllocatedTchAllocation (number ofTCH/FRallocated for traffic inthe inner or outer zone of the cell)

1611/0 tchFrAveragedUsedTchAllocationMoy/Max/Cum/Ech (average numberof TCH/FR used for traffic in the inner or outer zone of the cell)

1812 allocatedCircuitTsMoy/Max/Cum/Ech (number of TS allocations fortraffic on circuit mode in the cell orallocatedCircuitTsTrZoneMoy/Max/Cum/Ech (number of TS allocations fortraffic 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, 1049attemptedTchFrSeizures (number of TCH/FR assignment requests) is incrementedand, if theMS is the dualband type, 1715 attemptedTchFrSeizuresMsDualdb is alsoincremented.

(4) When the STOP_MEASUREMENT message for the SDCCH channel isreceived, 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 isincremented and, if the MS is the dualband type, 1716successfulTchFrSeizuresMsDualb is also incremented.

(6) When the old (SDCCH) channel has been released, 1607 counting the averagenumber of SDCCH used in the inner or outer zone of the cell is decremented.

List of counters incremented or decremented during this procedure:

Counternumber



average time of a signaling chan-nel seizure


average time of a signaling chan-nel seizure > 25s

1049 attempedTchFrSeizures number of TCH/FR assignmentrequests

1050 successfulTchFrSeizures number of TCH/FR successfullyassigned


PE/DCL/DD/0125411--9001--125


Counternumber


1094 tcAllocated number of terrestrial circuits allo-cated

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


1108 aOutputMessage number of BSSAP messagessent by the BSC

1197/0 channelActivateSpeechFullRate number of channels activated forspeech: Full Rate algorithm

1197/1 channelActivateSpeechEnhanced-FullRate

number of channels activated forspeech: Enhanced Full Ratealgorithm

1502 aNonTransparentUp number of BSSMAP messagessent by the BSC

1503 aNonTransparentDown number of BSSMAP messagesreceived by the BSC


duration of maximum downlinkpower use on busy SDCCHs


duration of maximum uplinkpower use on busy SDCCHs




average number of SDCCHsused in the inner or outer zone ofthe cell

1609/0 tchFrAllocatedTchAllocationTrZone number of TCH/FR or preemptedPDTCH allocated for traffic in theinner of outer zone of the cell

1611/0 tchFrAveragedUsedTchAllocation-TrZoneMoy/Max/Cum/Ech

average number of TCH/FR orpreempted PDTCH used for traf-fic in the inner or outer zone ofthe cell



Counternumber




number of MS measurementmessages not received (non--concentric cell)ornumber of MS measurementmessages not received (concen-tric cell)

1623 rxLevDownLink


sum of downlink signal strengthmeasurements received (non--concentric cell)orsum of downlink signal strengthmeasurements received (concen-tric cell)

1624 rxLevUpLink

orrxLevUpLinkTrZone

sum of uplink signal strengthmeasurements received (non--concentric cell)orsum of uplink signal strengthmeasurements received (concen-tric cell)

1625 rxQualDownLink


sum of downlink signal qualitymeasurements (concentric cell)orsum of downlink signal qualitymeasurements (non--concentriccell)

1626 rxQualUpLink


sum of uplink signal quality mea-surements (non--concentric cell)orsum of uplink signal quality mea-surements (concentric cell)

1629/0 channelActivateSignallingFullRate number of Full--Rate channelsactivated for signaling

1629/1 channelActivateSignallingEnhanced-FullRate

number of Enhanced--Full--Ratechannels activated for signaling

1705/n(n = 0 to 6)

channelActivateTchFrDataTx (x = 16to 14400 b/s)

number of TCH/FR activation fortransparent data service with atransmission rate = x

1707/n(n = 0 to 2)

channelActivateTchFrDataNTx(x = 6 to 14500 b/s)

number of TCH/FR activation fornon transparent data service witha transmission rate = x


PE/DCL/DD/0125411--9001--125


Counternumber


1709 channelActivateTchFrDataTHscsd number of channel activation fortransparent data service onTCH/FR

1710 channelActivateTchFrNDa-taNTHscsd

number of channel activation fornon transparent data service onTCH/FR

1715 attemptedTchFrSeizuresMsDualb number of attempts of assigna-tion of a TCH/FR for dualbandmobiles

1716 successfulTchFrSeizuresMsDualb number of successful TCH/FRassignations for dualbandmobiles

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 abisTrauFrameUlReceived number of frames TRAU uplinkreceived

1721 ECU_Activation number of erroneous frames(ECU may be activated or not)

1744 tchFrAllocated


number of TCH/FR or preemptedPDTCH allocated in the cellornumber of TCH/FR or preemptedPDTCH allocated in the inner orouter zone of the concentric cell


ortchFrAveragedUsedTrZoneMoy/Max/Cum/Ech

average number of TCH/FR orpreempted PDTCH used in thecelloraverage number of TCH/FR orpreempted PDTCH used in theinner or outer zone of the cell



Counternumber


1812 allocatedCircuitTsMoy

orallocatedCircuitTsTrZoneMoy

number of TS allocations for traf-fic in circuit mode in the cellornumber of TS allocations fortraffic in circuit mode in the inneror the outer zone of the concen-tric cell

1841/0 assignRequestSdcchToTchChannel number of assignement requestmessages received: modificationfrom an SDCCH channel to aTCH channel

1.2.3.2 MODE MODIFY procedure

This procedure is used to modify the coding/decoding/transcoding mode on thededicated 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 toaccomplish the transition from signaling to speech mode rather than the generalprocedure which is much longer.


PE/DCL/DD/0125411--9001--125


MS BTS BSC MSCASSIGNMENT_REQUEST

Set timer TmodAck

Reset timer TmodAck

Set timer TmodMS

CHANNEL_MODE_MODIFYReset timer TmodMS

CHANNEL_MODE_MODIFY

CHANNEL_MODE_MODIFY_ACK

ASSIGNMENT_COMPLETE

11081502

110715031841/110941095

(1)

MODE_MODIFY_REQUEST

CHANNEL_MODE_MODIFY

1197/n (2)17091705/n17101707/n

10441045

MODE_MODIFY_REQUEST_ACK

(3)

(1) Downlink DTAP service is suspended.(2) The counter incremented depends on the channel mode used (speech or data):

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




Counternumber



average time of a signaling channelseizure


average time of a signaling channelseizure > 25s

1094 tcAllocated number of terrestrial circuits allocated

1095 tcAveragedUsedMoy/Max/Cum//Ech

average number of terrestrial circuitsused



1197/0 channelActivateSpeechFullRate

number of channels activated forspeech: Full Rate algorithm



1841/0 assignRequestSdcchToTchChannel

number of assignement requestmessages received: modification froman SDCCH channel to a TCH channel

1.2.3.3 No resource available and queuing not activated

The terrestrial circuit allocation is engaged before the radio resource allocation. Ifthe radio resource allocation fails because of radio resource shortage, theTCH--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”


PE/DCL/DD/0125411--9001--125


Data Flow Diagram: dedicated channel assignment procedure (no resourceavailable and queuing not activated).


1107 (1)15031841/01094 (2)109516131842/0 (3)1095 (--1) (4)

ASSIGNMENT_FAILURE

11081502 (5)

(1) Downlink DTAP service is suspended.

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



Counternumber





1107 aInputMessage number of BSSAP messages receivedby the BSC


1502 aNonTransparentUp number of BSSMAP messages sent bythe BSC




Counternumber


1613 tchFrResourceFailureTrZone number of TCH/FR and preemptablePDTCH allocation failures in the inneror outer zone of the cell

1841/0 assignRequestSdcchToTch-Channel

number of assignment request mes-sages received: modification from anSDCCH channel to a TCH channel

1842/0 assignFailureSdcchToTch-Channel

number of emission of ASSIGNEMENTFAILURE messages on the A interface:modification from an SDCCH channelto a TCH channel or a preemptedPDTCH


PE/DCL/DD/0125411--9001--125


1.2.3.4 Queuing procedure (successful completion)

Data FlowDiagram: queuing of the assignment procedure (successful completion).


11071503

1841/01616/N

QUEUEING1108 (3)15021616/n(--1)1618/n(--1)174417461609/01611/0181210941095

(1)

(2)

Set timer T11

Reset timer T11CONNECTION_STATE_REQUESTSet timer Tcnx

Reset timer TcnxCONN_STATE_REQ_ASK

CHANNEL_ACTIVATESet timer TchnAck

Reset timer TchnAck

1197/0 or 1197/1or 1709 and 1705/n (5)or 1710 and 1707/n

CHANNEL_ACTIVATE_ASK

ASSIGNMENT_COMMAND

1049 (6)1715

ASSIGNMENT_COMMAND

STOP_MEASUREMENT_REQUESTSet timer T3107

(4)



MS BTS BSC MSC

1601 (7)16021603162216231624162516261805 (8)1806 (8)1807 (8)1808 (8)

STOP_MEASUREMENT_REQ_ACK

SABM

UA

ASSIGNMENT_COMPLETE


ASSIGNMENT_COMPLETE

1050 (9)1716

ASSIGNMENT_COMPLETE

11081502



RF_CHANNEL RELEASE

10441045


1607 (--1)

Set timer Tmea

Reset timer Tmea

Reset timer T3107


1607 (--1)17171718171917201721

Set timer TrfAck

Reset timer TrfAck

(10)


(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 terrestrialcircuits used)


PE/DCL/DD/0125411--9001--125


1609/0 chFrAllocatedTchAllocationTrZone (number of TCH/FR allocated fortraffic in the inner of outer zone of the cell)

1611/0 tchFrAveragedUsedTchAllocationTrZoneMoy/Max/Cum/Ech (averagenumber 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, 1049attemptedTchFrSeizures (number of TCH/FR assignment requests) is incrementedand, if the MS is the dualband type, 1715 attemptedTchFrSeizuresMsDualb is alsoincremented.

(7) When the STOP_MEASUREMENT message for the SDCCH channel isreceived, 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 isincremented and, if the MS is the dualband type, 1716successfulTchFrSeizuresMsDualb is also incremented.




Counternumber




1045 signallingPhaseDurationHigh-Moy/Max/Cum/Ech




Counternumber


1049 attempedTchFrSeizures number of TCH/FR assignmentrequests





1107 aInputMessage number of BSSAP messages receivedby the BSC


1197/0 channelActivateSpeechFull-Rate


1197/1 channelActivateSpeechEn-hancedFullRate

number of channels activated forspeech: Enhanced Full Rate algorithm

1502 aNonTransparentUp number of BSSMAP messages sent bythe BSC


1601 downlinkPowerCtrlMaxSdc-chMoy/Max/Cum/Ech



duration of maximum uplink power useon busy SDCCHs

1603 connectionDuration-SdcchMoy/Max/Cum/EchorconnectionDurationSdcchTrZo-neMoy/Max/Cum/Ech


1607 sdcchAveragedUsedTrZone-Moy/Max/Cum/Ech

average number of SDCCHs used inthe inner or outer zone of the concen-tric cell

1609/0 tchFrAllocatedTchAllocation-TrZone

number of TCH/FR or preemptedPDTCH allocated for traffic in the innerof outer zone of the cell


PE/DCL/DD/0125411--9001--125


Counternumber


1611/0 tchFrAveragedUsedTchAlloca-tionTrZoneMoy/Max/Cum/Ech

average number of TCH/FR or pre-empted PDTCH used for traffic in theinner or outer zone of the cell

1616/n[n= 0 to 1]

tchAveragedQueueLength-HighPriorityMoy/Max/Cum/Ech for n=0andtchAveragedQueueLengthO-therPriorityMoy/Max/Cum/Echfor n=1

number of queued TCH requests withthe highest priorityandnumber of queued TCH requests withan internal priority different than thehighest one



number of MS measurement messagesnot received (non--concentric cell)ornumber of MS measurement messagesnot received (concentric cell)

1623 rxLevDownLink


sum of downlink signal strength mea-surements received (non--concentriccell)orsum of downlink signal strength mea-surements received (concentric cell)

1624 rxLevUpLink

orrxLevUpLinkTrZone

sum of uplink signal strength measure-ments received (non--concentric cell)orsum of uplink signal strength measure-ments received (concentric cell)

1625 rxQualDownLink


sum of downlink signal quality mea-surements (concentric cell)orsum of downlink signal quality mea-surements (non--concentric cell)

1626 rxQualUpLink


sum of uplink signal quality measure-ments (non--concentric cell)orsum of uplink signal quality measure-ments (concentric cell)

1705/n(n = 0 to 6)

channelActivateTchFrDataTx (x= 16 to 14400 b/s)

number of TCH/FR activation for trans-parent data service with a transmissionrate = x

1707/n(n = 0 to 2)

channelActivateTchFrDa-taNTx (x = 6 to 14500 b/s)

number of TCH/FR activation for nontransparent data service with a trans-mission rate = x



Counternumber


1709 channelActivateTchFrDa-taTHscsd

number of channel activation for trans-parent data service on TCH/FR


number of channel activation for nontransparent data service on TCH/FR

1715 attemptedTchFrSeizu-resMsDualb

number of attempts of assignation of aTCH/FR for dualband mobiles

1716 successfulTchFrSeizu-resMsDualb

number of successful TCH/FR assigna-tions for dualband mobiles

1717 abisTrauFrameDlReceived number of frames TRAU downlinkreceived

1718 abisTrauFrameDlCorrected number of frames TRAU downlink cor-rected

1719 abisTrauFrameDlMuted number of frames TRAU downlink thatcan not be corrected

1720 abisTrauFrameUlReceived number of frames TRAU uplinkreceived

1721 ECU_Activation number of erroneous frames (ECU maybe activated or not)

1744 tchFrAllocated


number of TCH/FR or preemptedPDTCH allocated in the cellornumber of TCH/FR or preemptedPDTCH allocated in the inner or outerzone of the cell

1746 tchFrAveragedUsedMoy/Max/Cum/EchortchFrAveragedUsedTrZone-Moy/Max/Cum/Ech

average number of TCH/FR or pre-empted PDTCH used in the celloraverage number of TCH/FR or pre-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-trols ordered by the Layer 1 manage-ment


PE/DCL/DD/0125411--9001--125


Counternumber


1807 bsPowerIncControl number of BS increment power con-trols ordered by the Layer 1 manage-ment

1808 bsPowerDecControl number of BS decrement power con-trols ordered by the Layer 1 manage-ment

1812 allocatedCircuitTsMoy/Max/Cum/EchorallocatedCircuitTsTrZoneMoy/Max/Cum/Ech

number of TS allocations for traffic incircuit mode in the cellornumber of TS allocations for traffic incircuit mode in the inner or the outerzone of the concentric cell


number of assignment request mes-sages received: modification from anSDCCH channel to a TCH channel

1.2.4 Handovers

1.2.4.1 Overview

Each handover procedure performed in a cell requires two phases, a selection phaseand 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 successfullycompleted as shown in the following diagram.

handoverSELECTION

No

call interrupted

SELECTION_FAILURE

Yes: execution

request request EXECUTIONYes: handover

EXECUTION_FAILURE

No

successful



The ratios between the following counters are used to evaluate the efficiency of theprocedures 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

• 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


PE/DCL/DD/0125411--9001--125


1.2.4.2 Accounting principles

To synchronize accounting, all the counters concerned by the same handoverrequest are incremented at the end of the procedure, except for the counters used totally repeated requests and refusals, which are stepped up in real time.

The following diagram is an example of an outgoing handover requested by cell Nin BSS 1 that is refused by the first cell in the list (cell A in BSS 1) and executedsuccessfully in the second cell (cell B in BSS 2). It shows the counters that areupdated by the handover procedure.

requestcell A BSS 1cell N BSS 1

hoRequestOutgoingIntra cell NhoRequestIncomingIntra cell NhoOutIntraFailureXxx cell NhoInIntraFailureXxx cell A

refused

EXECUTION

successful

hoRequiredXxx cell NhoRequestOutgoingInter cell NhoRequestIncomingInter cell BhoExecutionOutgoingInter cell NhoExecutionIncomingInter cell BhoSuccessOutgoingInter cell NhoSuccessIncomingInter cell B

acceptedrequest

cell B BSS 2cell N BSS 1

hoRequiredXxx cell N



1.2.4.3 Intra-bts handover procedure

In the intra-bts handover procedure, a dedicated channel is assigned in response toa modify radio channel request sent by Level 1 (Layer 1 Management).

Data Flow Diagram : intra--cell handover procedure (normal completion withcommunication on TRAFFIC phase)

MS BTS BSC MSC

HANDOVER_COMPLETE

HANDOVER_PERFORMED

1780106717811073106510711075106912001839/n (4)1840/n (4)10771793, 1794, 1795 and1208, 1789, 1209 or1783, 1790, 1786 or1784, 1791, 1787 or1785, 1792, 1788



RF_CHANNEL RELEASE


Reset timer T3107

11081502

1812 (--1) (5)1746 (--1)1611 (--1)

Set timer TrfAck

Reset timer TrfAck

(1) A TCH resource is successfully allocated internally in the BSC software on thetarget cell. Then the following counters are incremented:

1609/0 tchFrAllocatedTchAllocationTrZone (number of TCH/FR allocated fortraffic in the inner of outer zone of the cell)



PE/DCL/DD/0125411--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_MEASUREMENTmessage 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


(5)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/FRused in the cell) or tchFrAveragedUsedTrZoneMoy/Max/Cum/Ech (averagenumber of TCH/FR used in the inner or outer zone of the cell)



Counternumber


1065 hoExecutionOutgoingIntraBss number of attempts to executeoutgoing intra--bss handovers onTCH

1067 hoSuccessOutgoingIntraBss number of successful outgoingintra--bss handovers on TCH

1069 hoRequestIncomingIntraBss number of incoming intra--bsshandover requests on TCH

1071 hoExecutionIncomingIntraBss number of attempts to executeincoming intra--bss handovers onTCH

1073 hoSuccessfulIncomingIntraBss

number of successful incomingintra--bss handovers on TCH

1075 hoRequestOutgoingIntraBss number of outgoing intra--bsshandover requests on TCH



Counternumber


1077 hoSuccessOutgoingFirstIntra number of successful outgoingintra--bss handovers on TCH to thefirst cell from the list of eligible cells

1108 aOutputMessage number of BSSAP messages sentby the BSC to the MSC

1138/n[n=0 to 16]

hoRequiredTchXxx number of handovers on TCHrequired: CauseXxx



1197/1 channelActivateSpeechEnhancedFullRate

number of channels activated forspeech: Enhanced Full Ratealgorithm

1198 downlinkPowerCtrlMaxTchMoy/Max/Cum/Ech

duration of maximum downlink poweruse on busy TCHs

1199 uplinkPowerCtrlMaxTchMoy/Max/Cum/Ech

duration of maximum uplink poweruse on busy TCHs

1200 hoNcellsExecution number of handovers on TCHexecuted

1208 hoRequestOutgoingMbandEbandMsDualb

number of outgoing requested bydualband mobiles from the mainfrequency band to the secondfrequency band of the network

1209 hoSuccessOutgoingMbandEbandMsDualb

number of successful outgoinghandovers for dualband mobilesfrom the main frequency band to thesecond frequency band of thenetwork

1502 aNonTransparentUp number of BSSMAP messages sentby the BSC to the MSC

1600 connectionDurationTchMoy/Max/Cum/Ech

orconnectionDurationTchTrZoneMoy/Max/Cum/Ech

average duration and maximumduration of TCH/FR or preemptedPDTCH connections in the celloraverage duration and maximumduration of TCH/FR or preemptedPDTCH connections in the inner orouter zone of the cell

1609/0 tchFrAllocatedTchAllocationTrZone

number of TCH/FR or preemptedPDTCH allocated for traffic in theinner of outer zone of the cell

1611/0 tchFrAveragedUsedTchAllocationTrZoneMoy/Max/Cum/Ech

average number of TCH/FR FR orpreempted PDTCH used for traffic inthe inner or outer zone of the cell


PE/DCL/DD/0125411--9001--125


Counternumber




number of MS measurementmessages not received by the cellornumber of MS measurementmessages not received by the inneror outer zone of the cell

1623 rxLevDownLink


sum of downlink signal strengthmeasurements performed by the MSon the cellorsum of downlink signal strengthmeasurements performed by the MSon the inner or outer zone of the cell

1624 rxLevUpLink

orrxLevUpLinkTrZone

sum of uplink signal strengthmeasurements performed by theBTS on the cellorsum of uplink signal strengthmeasurements performed by theBTS on the inner or outer zone ofthe cell

1625 rxQualDownLink


sum of downlink signal qualitymeasurements performed by the MSon the cellorsum of downlink signal qualitymeasurements performed by the MSon the inner or outer zone of the cell

1626 rxQualUpLink


sum of uplink signal qualitymeasurements performed by theBTS on the cellorsum of uplink signal qualitymeasurements performed by theBTS on the inner or outer zone ofthe cell

1705/n[n = 0 to 6]

channelActivateTchFrDataTx(x = 16 to 14400 b/s)


1707/n[n = 0 to 2]

channelActivateTchFrDataNTx (x = 6 to 14500 b/s)

number of TCH/FR activation for nontransparent data service with atransmission rate = x

1709 channelActTchFrDataT number of channel activation fortransparent data service on TCH/FR

1710 channelActTchFrDataNT number of channel activation for nontransparent data service on TCH/FR



Counternumber


1744 tchFrAllocated


number of TCH/FR or preemptedPDTCH allocated in the cellornumber of TCH/FR or preemptedPDTCH allocated in the inner orouter zone of the cell


average number of TCH/FR orpreempted PDTCH used in the celloraverage number of TCH/FR oepreempted PDTCH used in the inneror outer zone of the cell

1776 hoRequiredTch number of handovers on TCHrequired

1780 hoSuccessOutgoingTch number of successful outgoinghandovers from the cell

1781 hoSuccessfulIncomingTch number of successful incominghandovers in the cell

1783 hoRequestOutgoingMbandMbandMsDualb

number of outgoing handoversrequested by dualband mobiles fromthe main frequency band to thesame frequency band of the network

1784 hoRequestOutgoingEbandEbandMsDualb

number of outgoing handoversrequested by dualband mobiles fromthe second frequency band to thesame frequency band of the network

1785 hoRequestOutgoingEbandMbandMsDualb

number of outgoing handoversrequested by dualband mobiles fromthe second frequency band to themain frequency band of the network

1786 hoSuccessOutgoingMbandMbandMsDualb

number of successful outgoinghandovers for dualband mobiles fromthe main frequency to the samefrequency band of the network

1787 hoSuccessOutgoingEbandEbandMsDualb

number of successful outgoinghandovers for dualband mobiles fromthe second frequency band to thesame frequency band of the network

1788 hoSuccessOutgoingEbandMbandMsDualb

number of successful outgoinghandovers for dualband mobiles fromthe second frequency band to themain frequency band of the network


PE/DCL/DD/0125411--9001--125


Counternumber


1789 hoExecutionOutgoingMbandEbandMsDualb

number of outgoing handoversexecutions by dualband mobiles forthe main frequency band to thesecond frequency band of thenetwork

1790 hoExecutionOutgoingMbandMbandMsDualb

number of outgoing handoversexecutions by dualband mobiles forthe main frequency band to thesame frequency band of the network

1791 hoExecutionOutgoingEbandEbandMsDualb

number of outgoing handoversexecutions by dualband mobiles forthe second frequency band to thesame frequency band of the network

1792 hoExecutionOutgoingEbandMbandMsDualb

number of outgoing handoversexecutions by dualband mobiles forthe second frequency band to themain frequency band of the network

1793 hoRequestIncomingIntraBssTchMsDualb

number of incoming intra--bsshandovers on TCH requested bydualband mobiles

1794 hoExecutionIncomingIntraBssTchMsDualb

number of incoming intra--bsshandovers on TCH executionattempts for dualband mobiles

1795 hoSuccessIncomingIntraBssTchMsDualb

number of successful incomingintra--bss handovers on TCH fordualband mobiles







Counternumber


1809/n[n= 0 to 1]

timingAdvanceAverage [forn=0]ortimingAdvanceAverageTrZone [for n=0]ortimingAdvanceMaximum [forn=1]ortimingAdvanceMaximumTrZone [for n=1]

average timing advance value for thecommunication in the cell oraverage timing advance value for thecommunication in the inner or outerzone of the cell ormaximum timing advance value forthe communication in the cell ormaximum timing advance value forthe communication in the inner orouter zone of the cell


number of TS allocations for traffic incircuit mode in the cellornumber of TS allocations for trafficin circuit mode in the inner or theouter zone of the concentric cell

1839/n[n=o to 9]

hoNcellsRequestOutgoingXxx number of outgoing intra--bss orinter--bss handover attempts from acentral cell to a neighboring one:Cause Xxx

1840/n[n=o to 9]

hoNcellsSuccessOutgoingXxx number of outgoing intra--bss orinter--bss handover successes froma central cell to a neighboring one:Cause Xxx

1.2.4.4 Inter cell intra--bss handover procedure (normal completion)

An intra-bss handover request is initiated by the BSC. TheMSC is informed of thechange by a HANDOVER PERFORMED message at the end of the procedure.

Dataflows: inter--cell intra BSC handover procedure (normal completion withcommunication on TRAFFIC phase).


PE/DCL/DD/0125411--9001--125


HANDOVER_COMMAND


ASSIGNMENT_REQUEST

MS BTS1 BTS2 BSC MSC

UA

HANDOVER_ACCESS

SABM

HANDOVER_COMPLETE

1198 (1)11991600162216231624162516261805 (4)1806 (4)1807 (4)1808 (4)1806/n (4)



HANDOVER_COMMAND

CHANNEL_ACTIVATE

17761138/n174417461609/0 (1)1611/0 (1)1812 (1)

1197/0 or 1197/1or 1709 and 1705/n (2)or 1710 and 1707/n

Set timer TchnAck

Reset timer TchnAck

Set timer T3103

HANDOVER_DETECT




MS BTS1 BTS2 BSC MSC

11081502

Reset timer T3103

Set timer TrfAck

Reset timer TrfAck



HANDOVER_COMPLETE


RF_CHANNEL_RELEASE

1812 (--1) (5)1746 (--1)1611 (--1)

1780106717811073106510711075106912001839/n (4)1840/n (4)10771793, 1794, 1795 and1208, 1789, 1209 or1783, 1790, 1786 or1784, 1791, 1787 or1785, 1792, 1788

(1) A TCH resource is successfully allocated internally in the BSC software on thetarget cell. Then the following counters are incremented:

1609/0 tchFrAllocatedTchAllocationTrZone (number of TCH/FR allocated fortraffic in the inner of outer zone of the cell)



PE/DCL/DD/0125411--9001--125






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





1746 tchFrAveragedUsedMoy/Max/Cum/Ech (average number of TCH/FRused in the cell) or tchFrAveragedUsedTrZoneMoy/Max/Cum/Ech (averagenumber of TCH/FR used in the inner or outer zone of the cell)



Counternumber


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 executionattempts

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



Counternumber


1075 hoRequestOutgoingIntraBss number of successful outgoing intra--bss handovers on TCH requested

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

1108 aOutputMessage number of BSSAP messages sent bythe BSC to the MSC

1138/n[n=0 to 16]




1197/1 channelActivateSpeechEn-hancedFullRate






1200 hoNcellsExecution number of handovers on TCH exe-cuted

1208 hoRequestOutgoingMbandE-bandMsDualb

number of outgoing requested bydualband mobiles from the main fre-quency band to the second frequencyband of the network

1209 hoSuccessOutgoingMbandE-bandMsDualb

number of successful outgoing hand-overs for dualband mobiles from themain frequency band to the secondfrequency band of the network



orconnectionDurationTchTrZone-Moy/Max/Cum/Ech

average duration and maximum dura-tion of TCH/FR or preempted PDTCHconnections in the celloraverage duration and maximum dura-tion of TCH/FR or preempted PDTCHconnections in the inner or outer zoneof the cell


PE/DCL/DD/0125411--9001--125


Counternumber




1611/0 tchFrAveragedUsedTchAllocation-TrZoneMoy/Max/Cum/Ech




number of MS measurement mes-sages not received by the cellornumber of MS measurement mes-sages not received by the inner orouter zone of the cell

1623 rxLevDownLink


sum of downlink signal strength mea-surements performed by the MS onthe cellorsum of downlink signal strength mea-surements performed by the MS onthe inner or outer zone of the cell

1624 rxLevUpLink

orrxLevUpLinkTrZone

sum of uplink signal strength mea-surements performed by the BTS onthe cellorsum of uplink signal strength mea-surements performed by the BTS onthe inner or outer zone of the cell

1625 rxQualDownLink


sum of downlink signal quality mea-surements performed by the MS onthe cellorsum of downlink signal quality mea-surements performed by the MS onthe inner or outer zone of the cell

1626 rxQualUpLink


sum of uplink signal quality measure-ments performed by the BTS on thecellorsum of uplink signal quality measure-ments performed by the BTS on theinner or outer zone of the cell

1705/n[n = 0 to 6]

channelActivateTchFrDataTx (x= 16 to 14400 b/s)

number of TCH/FR activation fortransparent data service with a trans-mission rate = x



Counternumber


1707/n[n = 0 to 2]

channelActivateTchFrDataNTx(x = 6 to 14500 b/s)

number of TCH/FR activation for nontransparent data service with a trans-mission rate = x

1709 channelActivateTchFrDa-taTHscsd

number of channel activation fortransparent data service on TCH/FR


number of channel activation for nontransparent data service on TCH/FR

1744 tchFrAllocated




average number of TCH/FR or pre-empted PDTCH used in the celloraverage number of TCH/FR or pre-empted PDTCH used in the inner orouter zone of the cell


1780 hoSuccessOutgoingTch number of successful outgoing hand-overs from the cell

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

1783 hoRequestOutgoingMbandM-bandMsDualb

number of outgoing handoversrequested by dualband mobiles fromthe main frequency band to the samefrequency band of the network

1784 hoRequestOutgoingEbandE-bandMsDualb

number of outgoing handoversrequested by dualband mobiles fromthe second frequency band to thesame frequency band of the network

1785 hoRequestOutgoingEbandM-bandMsDualb

number of outgoing handoversrequested by dualband mobiles fromthe second frequency band to themain frequency band of the network


PE/DCL/DD/0125411--9001--125


Counternumber


1786 hoSuccessOutgoingMbandM-bandMsDualb

number of successful outgoing hand-overs for dualband mobiles from themain frequency to the same frequencyband of the network

1787 hoSuccessOutgoingEbandE-bandMsDualb

number of successful outgoing hand-overs for dualband mobiles from thesecond frequency band to the samefrequency band of the network

1788 hoSuccessOutgoingEbandM-bandMsDualb

number of successful outgoing hand-overs for dualband mobiles from thesecond frequency band to the mainfrequency band of the network

1789 hoExecutionOutgoingMbandE-bandMsDualb

number of outgoing handovers execu-tions by dualband mobiles for themain frequency band to the secondfrequency band of the network

1790 hoExecutionOutgoingMbandM-bandMsDualb

number of outgoing handovers execu-tions by dualband mobiles for themain frequency band to the same fre-quency band of the network

1791 hoExecutionOutgoingEbandE-bandMsDualb

number of outgoing handovers execu-tions by dualband mobiles for the sec-ond frequency band to the same fre-quency band of the network

1792 hoExecutionOutgoingEbandM-bandMsDualb

number of outgoing handovers execu-tions by dualband mobiles for the sec-ond frequency band to the main fre-quency band of the network

1793 hoRequestIncomingIn-traBssTchMsDualb

number of incoming intra--bss hand-overs on TCH requested by dualbandmobiles

1794 hoExecutionIncomingIn-traBssTchMsDualb

number of incoming intra--bss hand-overs on TCH execution attempts fordualband mobiles

1795 hoSuccessIncomingIn-traBssTchMsDualb

number of successful incoming intra--bss handovers on TCH for dualbandmobiles

1805 msPowerIncControl number of MS increment power con-trols ordered by the Layer 1 manage-ment



Counternumber


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

1807 bsPowerIncControl number of BS increment power con-trols ordered by the Layer 1 manage-ment

1808 bsPowerDecControl number of BS decrement power con-trols ordered by the Layer 1 manage-ment

1809/n[n= 0 to 1]

timingAdvanceAverage for n=0ortimingAdvanceAverageTrZonefor n=0

timingAdvanceMaximum forn=1ortimingAdvanceMaximumTr-Zone for n=1

average timing advance value for thecommunication in the cell oraverage timing advance value for thecommunication in the inner or outerzone of the cellmaximum timing advance value forthe communication in the cell ormaximum timing advance value forthe communication in the inner orouter zone of the cell



1839/n[n=o to 9]

hoNcellsRequestOutgoingXxx number of outgoing intra--bss or inter--bss handover attempts from a centralcell to a neighboring one: Xxx

1840/n[n=o to 9]

hoNcellsSuccessOutgoingXxx number of outgoing intra--bss or inter--bss handover successes from a cen-tral cell to a neighboring one: Xxx

1.2.4.5 Inter-bss handover procedure

Data FlowDiagram : inter BSS intraMSC handover procedure (normal completionwith communication on TRAFFIC phase)


PE/DCL/DD/0125411--9001--125


MS BTS1 BSC1 MSC

1198 (3)11991600162216231624162516261805 (4)1806 (4)1807 (4)1808 (4)1809/n (4)

HANDOVER_INDICATION

1197/0 or 1197/1or 1709 and 1705/n (1)or 1710 and 1707/n

BTS2 BSC2

17761138/n

HANDOVER_REQUIRED

Set timer T7

CONNECTION_INDICATION_(HANDOVER_REQUEST)

Set timer TchnAckCHANNEL_ACTIVATE


Set timer T3107

Reset timerTchnAck

HO_REQ_ACK(HANDOVER_COMMAND)

Set timer T8

HANDOVER_COMMAND

Reset timer T7

HO_REQ_ACK(HANDOVER_COMMAND)

HANDOVER_COMMAND

STOP_MEAS_REQUEST

STOP_MEAS_REQ_ACK

1105110411071503174417461609/01611/0181210941095

11081502 CONNECTION_

RESPONSE

11071503 (2)



MS BTS1 BSC1 MSCHANDOVER_ACCESS

BTS2 BSC2


Reset timer T3107

HANDOVER_DETECT

11081502

PHYSICAL_INFORMATION

HANDOVER_DETECT

SABM

UA

START_MEAS_REQUEST

START_MEAS_REQ_ACK

1108150011071501

HANDOVER_PERFORMED

HANDOVER_COMPLETE

HANDOVER_COMPLETE

11081502

1781107410721070


PE/DCL/DD/0125411--9001--125


MS BTS1 BSC1 MSC

1812 (5)1746 (5)1611 (5)

BTS2 BSC2

1107150317541164/201095 (--1)

CLEAR_COMPLETE

Set timer TrfAck

Reset timer T8

DISCONNECT_INDICATION

RF_CHANNEL_RELEASE


11081502178010681066107612001839/N1840/N1078

CLEAR_COMMAND

1105 (--1)

Reset timer TrfAck



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.







1746 tchFrAveragedUsedMoy/Max/Cum/Ech (average number of TCH/FRused in the cell) or tchFrAveragedUsedTrZoneMoy/Max/Cum/Ech (averagenumber of TCH/FR used in the inner or outer zone of thecell )



Counternumber


1066 hoExecutionOutgoingInterBss

number of attempts to executeoutgoing inter--bss handovers on TCH

1068 hoSuccessOutgoingInterBss number of successful outgoinginter--bss handovers on TCH exceptthose after the first attempt

1070 hoRequestIncomingInterBss number of incoming inter--bsshandover requests on TCH

1072 hoExecutionIncomingInterBss

number of attempts to executeincoming inter--bss handovers onTCH

1074 hoSuccessfulIncomingInterBss

number of successful incominginter--bss handovers on TCH

1076 hoRequestOutgoingInterBss number of outgoing inter--bsshandover requests on TCH

1078 hoSuccessOutgoingFirstInter

number of successful outgoinginter--bss handovers on TCH to thefirst cell from the list of eligible cells

1094 tcAllocated number of terrestrial circuit allocationsin the BSC


average and maximum number ofterrestrial circuits allocated in the BSC


1105 sccpAverageUsedMoy/Max/Cum//Ech

average and maximum number ofSCCP connections established in theBSC


1138/n[n=0 to 16]



PE/DCL/DD/0125411--9001--125


Counternumber




1197/1 channelActivateSpeechEnhancedFullRate






1200 hoNcellsExecution number of handovers on TCHexecuted


1501 aTransparentDown number of DTAP messages sent bythe MSC to the BSC

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


or


1609/0 tchFrAllocatedTchAllocationTrZone



average number of TCH/FR FR orpreempted PDTCH used for traffic inthe inner or outer zone of the cell

1623 rxLevDownLink


sum of downlink signal strengthmeasurements performed by the MSon the cellorsum of downlink signal strengthmeasurements performed by the MSon the inner or outer zone of the cell

1624 rxLevUpLink

orrxLevUpLinkTrZone

sum of uplink signal strengthmeasurements performed by the BTSon the cellorsum of uplink signal strengthmeasurements performed by the BTSon the inner or outer zone of the cell



Counternumber


1625 rxQualDownLink


sum of downlink signal qualitymeasurements performed by the MSon the cellorsum of downlink signal qualitymeasurements performed by the MSon the inner or outer zone of the cell

1626 rxQualUpLink


sum of uplink signal qualitymeasurements performed by the BTSon the cellorsum of uplink signal qualitymeasurements performed by the BTSon the inner or outer zone of the cell

1705/n[n = 0 to 6]

channelActivateTchFrDataTx(x = 16 to 14400 b/s)


1707/n[n = 0 to 2]

channelActivateTchFrDataNTx (x = 6 to 14500 b/s)

number of TCH/FR activation for nontransparent data service with atransmission rate = x

1709 channelActTchFrDataT number of channel activation fortransparent data service on TCH/FR

1710 channelActTchFrDataNT number of channel activation for nontransparent data service on TCH/FR

1744 tchFrAllocated




average number of TCH/FR orpreempted PDTCH used in the celloraverage number of TCH/FR oepreempted PDTCH used in the inneror outer zone of the cell


1780 hoSuccessOutgoingTch number of successful outgoinghandovers from the cell

1781 hoSuccessfulIncomingTch number of successful incominghandovers in the cell



PE/DCL/DD/0125411--9001--125


Counternumber





1809/n[n= 0 to 1]





1839/n[n=o to 9]

hoNcellsRequestOutgoingXxx

number of outgoing intra--bss orinter--bss handover attempts from acentral cell to a neighboring one:Cause Xxx

1840/n[n=o to 9]

hoNcellsSuccessOutgoingXxx

number of outgoing intra--bss orinter--bss handover successes from acentral cell to a neighboring one:Cause Xxx

The downlink DTAP messages sent by MSC to the target BSC between sendingHANDOVER REQUEST and receiving HANDOVER COMPLETE are ignored.

The uplinkDTAP service is not inhibited on the channel being useduntil the channelis released.

1.2.4.6 Directed retry handover procedure

The following diagram describes the case where the BSC asks the BTS for a list ofneighbor cells. It does not describe directed retry handovers in microcells.

DataFlowDiagram: directed retry handover procedure (successful completionwithcommunication on SIGNALLING phase)



MS BTS BSC MSC

ASSIGNMENT_REQUEST

Set timer T11

Reset timer T11Set timer Tcnx

Reset timer Tcnx

HANDOVER_INDICATION

QUEUEING

110715031841/01616/n

(1)

CONNECTION_STATE_REQUEST

17761138/n


(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 to0x00 = Directed retry.

(4) The HANDOVER_INDICATION message is sending by the BTS with and hanover cause valueequal to Directed retry (0=x0A).

(5) After that, the process is identical to an handover intra--BSS or inter--BSS following the preferredcell list sending by the L1M BTS.

CONN_STATE_REQ_ACK

(4)

1108150210941095 (2)

(3)

(5)


Counternumber


1094 tcAllocated number of terrestrial circuit allocationsin the BSC


average and maximum number ofterrestrial circuits allocated in the BSC



1138/n[n= 0 to 16]

hoRequiredTchCauseXxx number of handovers on TCHrequired: CauseXxx


PE/DCL/DD/0125411--9001--125


Counternumber


1616/n[n= 0 to 1]

tchAveragedQueueLengthHighPriorityMoy/Max/Cum/Ech [for n=0]

tchAveragedQueueLengthOtherPriorityMoy/Max/Cum/Ech [for n=1]

number of queued TCH requests withthe highest priority in the cellnumber of queued TCH requests withan internal priority different than thehighest one


1841/0 assignRequestSdcchToTchChannel

number of assignment requestmessages received: modification froman SDCCH channel to a TCH channel



1.2.5 Resource release

1.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 dedicatedchannel and uses timers T3111 and T3109.

T3109 is only used when the DEACTIVATE SACCH ACK message is receivedbefore the RELEASE INDICATION message.


PE/DCL/DD/0125411--9001--125


DEACTIVATE SACCH ACK received before RELEASE INDICATION

Data Flow Diagram: Radio channel release procedure (release indication first withcommunication on TRAFFIC phase)

Set timer TDeacAck

Reset timer TDeacAck

MS BTS BSC MSC

CHANNEL_RELEASE

DEACTIVATE_SACCH



119811991600162216231624162516261805 (1)1806 (1)1807 (1)1808 (1)1809/n (1)

CHANNEL_RELEASE

1105 (--1)

1607 (--1)

timer T3111

Timer T3111 expires

DEACTIVATE_ACK

Set timer TrfAck

Reset timer TrfAck

RF_CHANNEL_RELEASE


DISC

UA



1095 (--1)

RELEASE_INDICATION




Counternumber


1095 tcAverageUsedMoy/Max/Cum/Ech


1105 SccpAverageUsedMoy/Max/Cum/Ech







orconnectionDurationTchTrZoneMoy/Max/Cum/Ech


1607 sdcchAllocatedUsedTrZoneMoy/Max/Cum/Ech




number of MS measurementsmessages not received by the cellornumber of MS measurementsmessages not received by the innerof the outer zone of the cell

1623 rxLevDownLink


sum of downlink signal strengthmeasurements performed by the MSin the cellorsum of downlink signal strengthmeasurements performed by the MSin the inner or outer zone of the cell

1624 rxLevUpLink

orrxLevUpLinkTrZone

sum of uplink signal strengthmeasurements performed by the MSin the cellorsum of downlink signal strengthmeasurements performed by the MSin the inner or outer zone of the cell

1625 rxQualDownLink


sum of downlink signal qualitymeasurements performed by the MSin the cellorsum of downlink signal qualitymeasurements performed by the MSin the inner or outer zone of the cell


PE/DCL/DD/0125411--9001--125


Counternumber


1626 rxQualUpLink


sum of uplink signal qualitymeasurements performed by the MSin the cellorsum of uplink signal qualitymeasurements performed by the MSin the inner or outer zone of the cell

1805 msPowerIncControl number of MS increment powercontrols ordered by the L1M

1806 msPowerDecControl number of MS decrement powercontrols ordered by the L1M

1807 bsPowerIncControl number of BS increment powercontrols ordered by the L1M

1808 bsPowerDecControl number of BS decrement powercontrols ordered by the L1M

1809/n[n=0 to 1]


average timing advance value for thecommunication in the cell oraverage timing advance value for thecommunication in the inner or outerzone of the cellormaximum timing advance value forthe communication in the cell ormaximum timing advance value forthe communication in the inner orouter zone of the cell



RELEASE INDICATION received before DEACTIVATE SACCH ACK

Data FlowDiagram:Radio channel releaseprocedure (deactivateSACCHAckwithcommunication on TRAFFIC phase)

Set timer TDeacAck


MS BTS BSC MSC

CHANNEL_RELEASE

DEACTIVATE_SACCH



160116021603162216231624162516261805 (1)1806 (1)1807 (1)1808 (1)1809/n (1)

CHANNEL_RELEASE

1105 (--1)

1607 (--1)

timer T3109

Reset timer T3109

DEACTIVATE_ACK

timer T3111

Timer T3111 expiresSet timer TrfAck

Reset timer TrfAck

RELEASE_INDICATION

RF_CHANNEL_RELEASE


DISC

UA




PE/DCL/DD/0125411--9001--125



Counternumber





duration of maximum downlinkpower use on busy SDCCHs



1603 connectionDurationSdcchTrZoneMoy/Max/Cum/Ech

connection duration of SDCCHs


average number of SDCCHs usedin the inner or outer zone of thecell



number of MS measurementsmessages not received by the cellornumber of MS measurementsmessages not received by theinner of the outer zone of the cell

1623 rxLevDownLink


sum of downlink signal strengthmeasurements performed by theMS in the cellorsum of downlink signal strengthmeasurements performed by theMS in the inner or outer zone ofthe cell

1624 rxLevUpLink

orrxLevUpLinkTrZone

sum of uplink signal strengthmeasurements performed by theMS in the cellorsum of downlink signal strengthmeasurements performed by theMS in the inner or outer zone ofthe cell

1625 rxQualDownLink


sum of downlink signal qualitymeasurements performed by theMS in the cellorsum of downlink signal qualitymeasurements performed by theMS in the inner or outer zone ofthe cell



Counternumber


1626 rxQualUpLink


sum of uplink signal qualitymeasurements performed by theMS in the cellorsum of uplink signal qualitymeasurements performed by theMS in the inner or outer zone ofthe cell

1805 msPowerIncControl number of MS increment powercontrols ordered by the L1M

1806 msPowerDecControl number of MS decrement powercontrols ordered by the L1M

1807 bsPowerIncControl number of BS increment powercontrols ordered by the L1M

1808 bsPowerDecControl number of BS decrement powercontrols ordered by the L1M

1809/n[n=0 to 1]

timingAdvanceAverage [forn=0]ortimingAdvanceAverageTrZone[for n=0]timingAdvanceMaximum [forn=1]ortimingAdvanceMaximumTrZone[for n=1]

average timing advance value forthe communication in the celloraverage timing advance value forthe communication in the inner orouter zone of the cellmaximum timing advance value forthe communication in the cellormaximum timing advance value forthe communication in the inner orouter zone of the cell

1.2.5.2 Connection release

The procedures use the following counters:

tcAveragedUsed

sccpAveragedUsed


PE/DCL/DD/0125411--9001--125


Release requested by the MSC

Data Flow Diagram: connection clearing required by the MSC procedure.

Communication on TRAFFIC phase

Set timer TrfAck

timer T3111

Set timer TDeacAck

Set timer TDeacAck

MS BTS BSC MSC

1107150317531164/201095 (--1)

CHANNEL_ACTIVATE

DEACTIVATE_SACCH

STOP_MEASUREMENT


1198 (1)1199160016221624162516261805180618071808

1809/n

CHANNEL_RELEASE

DEACTIVATE_SACCH_ACK

RELEASE_INDICATION


11081502

RF_CHANNEL_RELEASE

DISC

UA


CLEAR_COMPLETE

1105 (5)

CLEAR_COMMAND

1812 (2)1746 (3)1611/0 (4)

Reset timer T3111

Reset timer TrfAck



(1) When the STOP_MEASUREMENTmessage for the TCH channel is received,if theBTS reportsmeasurement counters, theBSC 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.


Counternumber





average number of SCCP connectionsestablished

1107 aInputMessage number of BSSAP messages received

1108 aOutputMessage number of BSSAP messages sent by theBSC to the MSC

1164/20 trafficReleaseClearCommand number of communications in trafficphase released: CLEAR COMMANDmessage received


duration of maximum downlink power useon busy TCHs


duration of maximum uplink power useon busy TCHs

1502 aNonTransparentUp number of BSSMAP messages sent bythe BSC to the MSC


orconnectionDurationTchTrZone-Moy/Max/Cum/Ech

average duration and maximum durationof TCH/FR or preempted PDTCH con-nections in the celloraverage duration and maximum durationof TCH/FR or preempted PDTCH con-nections in the inner or outer zone of thecell

1611/0 tchFrAveragedUsedTchAlloca-tionTrZoneMoy/Max/Cum/Ech

average number of TCH/FR or pre-empted PDTCH used for traffic in theinner of outer zone of the cell


PE/DCL/DD/0125411--9001--125


Counternumber





1623 rxLevDownLink


sum of downlink signal strength mea-surements received (non--concentric cell)orsum of downlink signal strength mea-surements received (concentric cell)

1624 rxLevUpLink

orrxLevUpLinkTrZone


1625 rxQualDownLink


sum of downlink signal quality measure-ments (concentric cell)orsum of downlink signal quality measure-ments (non--concentric cell)

1626 rxQualUpLink




average number of TCH/FR used in thecelloraverage number of TCH/FR used in theinner 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 controlsordered by the Layer 1 management

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

1807 bsPowerIncControl number of BS increment power controlsordered by the Layer 1 management

1808 bsPowerDecControl number of BS decrement power controlsordered by the Layer 1 management



Counternumber


1809/n[n= 0 to 1]

timingAdvanceAverage forn=0ortimingAdvanceAverageTr-Zone for n=0timingAdvanceMaximum forn=1ortimingAdvanceMaximumTr-Zone for n=1

average timing advance value for thecommunication in the celloraverage timing advance value for thecommunication in the inner or outer zoneof the cellmaximum timing advance value for thecommunication in the cell ormaximum timing advance value for thecommunication in the inner or outer zoneof the cell


Number of TS allocations for traffic in cir-cuit mode in the cellornumber of TS allocations for traffic in cir-cuit mode in the inner or the outer zoneof the concentric cell


PE/DCL/DD/0125411--9001--125


Communication on SIGNALLING phase

Set timer TchncAck

Reset timer TchnAck

MS BTS BSC MSC

1107150317531163/20

CHANNEL_RELEASE

DEACTIVATE_SACCH

STOP_MEASUREMENT


1601 (1)16021603162216231624162516261805180618071808

CHANNEL_RELEASE


RELEASE_INDICATION


1108150210441045

RF_CHANNEL_RELEASE

DISC

UA


CLEAR_COMPLETE

1105 (--1)

CLEAR_COMMAND

1607 (--1)

Set timer TrfAck

timer T3111

Reset timer T3111

Reset timer TrfAck

(1)When the STOP_MEASUREMENT message for the SDCCH channel isreceived, if the BTS reports measurement counters, the BSC increments counters1601, 1602, 1603, 1622, 1623, 1624, 1625, 1626, 1805, 1806, 1807 and 1808.




Counternumber



average time of a signaling channel sei-zure


average time of a signaling channel sei-zure > 25s





1163/20 signallingReleaseBtsClear-Command

number of communications in signallingphase released: CLEAR COMMANDreceived


1503 aNonTransparentDown number of BSSMAP messages receivedby the BSC from the MSC


duration of maximum downlink power useon busy SDCCHs



1603 connectionDurationSdcchMoy/Max/Cum/EchorconnectionDurationSdcchTrZo-neMoy/Max/Cum/Ech

connection duration of SDCCHs (concen-tric cell)orconnection duration of SDCCHs (non--concentric cell)

1607 sdcchAveragedUsedTrZone-Moy/Max/Cum/Ech

average number of SDCCHs used in theinner or outer zone of the cell





PE/DCL/DD/0125411--9001--125


Counternumber


1623 rxLevDownLink


sum of downlink signal strength mea-surements received (non--concentric cell)orsum of downlink signal strength mea-surements received (concentric cell)

1624 rxLevUpLink

orrxLevUpLinkTrZone


1625 rxQualDownLink


sum of downlink signal quality measure-ments (concentric cell)orsum of downlink signal quality measure-ments (non--concentric cell)

1626 rxQualUpLink



1753 signallingReleaseBts number of releases while the commu-nication is in “signalling phase” and a cellassociated to the communication

1805 msPowerIncControl number of MS increment power controlsordered by the Layer 1 management

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

1807 bsPowerIncControl number of BS increment power controlsordered by the Layer 1 management

1808 bsPowerDecControl number of BS decrement power controlsordered by the Layer 1 management



Release requested by the BSC

Data Flow Diagram: connection clearing required by the BSC procedure

Communication on TRAFFIC phase

MS BTS BSC MSC

1198 (1)119916001622162316241625162618051806180718081809/n

CLEAR_REQUEST

DISC

CHANNEL_RELEASE

RELEASE_INDICATION

11081502


CHANNEL_RELEASE

Set timer TclrCMD

Reset timer TclrCMD

UA


1107150317531164/201095 (--1)

CLEAR_COMMAND

CLEAR_COMPLETE

DEACTIVATE_SACCH

STOP_MEASUREMENTSet timer TDeacAck


RF_CHANNEL_RELEASE


Set timer T3111

Reset timer T3111

Set timer TrAck

Reset timer TrAck

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



PE/DCL/DD/0125411--9001--125


(1) When the STOP_MEASUREMENTmessage for the TCH channel is received,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.


Counternumber






1107 aInputMessage number of BSSAP messagesreceived


1164/20 trafficReleaseClearCommand

number of communications in trafficphase released: CLEAR COMMANDmessage received






1600 connectionDurationTchMoy/Max/Cum/EchorconnectionDurationTchTrZoneMoy/Max/Cum/Ech

connection duration of TCH/FR orpreempted PDTCH in the cellorconnection duration of TCH/FR orpreempted PDTCH in the inner ofouter zone of the cell


average number of TCH/FR orpreempted PDTCH used for traffic inthe inner of outer zone of the cell






Counternumber


1623 rxLevDownLink



1624 rxLevUpLink

orrxLevUpLinkTrZone


1625 rxQualDownLink



1626 rxQualUpLink




average number of TCH/FR orpreempted PDTCH used in the celloraverage number of TCH/FR orpreempted used in the inner or outerzone of the cell

1754 trafficRelease number of releases while thecommunication is in traffic phase






PE/DCL/DD/0125411--9001--125


Counternumber


1809/n[n= 0 to 1]







Communication on SIGNALLING phase

MS BTS BSC MSC


CLEAR_REQUEST

CHANNEL_RELEASE


RF_CHANNEL RELEASE


Reset timer TclrCMD

1607 (--1)

1601 (1)16021603162216231624162516261805180618071808

Set timer TclrCMD

CLEAR_COMMAND

CLEAR_COMPLETE

1108150210441045

Set timer TchnAckDEACTIVATE_SACCH

STOP_MEASUREMENT

Reset timer TchnAck

RELEASE_INDICATIONSet timer T3111

Reset timer T3111


1105 (--1)

DISC

CHANNEL_RELEASE

UA

11081502

1107150317531163/20

Set timer TrAck

Reset timer TrAck

(1) When the STOP_MEASUREMENT message for the SDCCH channel isreceived, if the BTS reports measurement counters, the BSC increments counters

1601, 1602, 1603, 1622, 1623, 1624, 1625, 1626, 1805, 1806, 1807 and 1808.


PE/DCL/DD/0125411--9001--125



Counternumber










1163/20 signallingReleaseBtsClearCommand

number of communications insignalling phase released: CLEARCOMMAND received


1503 aNonTransparentDown number of BSSMAP messagesreceived by the BSC from the MSC






connection duration of SDCCHs in thecellorconnection duration of SDCCHs in theinner or the outer zone of the cell






1623 rxLevDownLink





Counternumber


1624 rxLevUpLink

orrxLevUpLinkTrZone


1625 rxQualDownLink



1626 rxQualUpLink



1753 signallingReleaseBts number of releases while thecommunication is in “signalling phase”and a cell associated to thecommunication





1.2.6 SMS service

The SMS service uses a SAPI 3 session that is opened when the mobile is stable ona 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 sameas the immediate assignment procedure, but, in this case, the ESTABLISHINDICATION message contains the information “short message”.


PE/DCL/DD/0125411--9001--125


Data Flow Diagram : SMS procedure

SMS established by the MS

MS BTS BSC MSC

SABM (SAPI 3)

IMMEDIAT_ASSIGN

11081502

START_MEASUREMENT_REQUEST_ACK

CHANNEL_ACTIVATESet timer TchnAck

Reset timer TchnAck

UA

CHANNEL_REQUIRED

17481191/n174616061607

CONNECTION_CONFIRM

CONNECTION_REQUEST



CHANNEL_REQUIRED

1629

CHANNEL_ACTIVATE

SABM(CM_SERVICE_REQUEST)

17491192/n

ESTABLISH_INDICATION(CM_SERVICE_REQUEST)

17501193/n1196

Set timer T3111

Reset timer T3111

DTAP(CM_SERVICE_ACCEPT)


CM_SERVICE_ACCEPT

UA

ESTABLISH_INDICATION (SAPI 3)

1621 DTAP (CP_DATA)

11071501

DTAP (CP_DATA)


Counternumber


1104/0 sccpAlloccated number of SCCP connections forSSN BSSMAP in the BSC





Counternumber




1191/n[n= 0 to 7]

channelRequestCauseXxx number of channel allocationrequests: Cause Xxx

1192/n[n= 0 to 7]


number of successful immediateassignments:Cause Xxx

1193/n[n= 0 to 3]



1196 estabIndicSigPhase2 number of ESTABLISH INDICATIONmessages in establishment phasereceived for Phase II mobiles

1500 aTransparentDown number of DTAP messages receivedby the BSC



1606 sdcchAllocatedTrZone number of SDCCH allocated in theinner or outer zone of the cell



1621 sapi3SessionEstablishment number of sessions established forSMS to satisfy a short messagebroadcast request in the cell








PE/DCL/DD/0125411--9001--125


SMS established by the MSC


Counternumber



1501 aNonTransparentUp number of BSSMAP messagessent by the BSC to the MSC

1621 sapi3SessionEstablishment number of sessions establishedfor SMS to satisfy a shortmessage broadcast request inthe cell



1.2.7 GPRS

1.2.7.1 Nominal procedure (in the case of Mobile Originating Call)

The GPRS procedure described in the following diagram is the normal completionof the preemption on PDTCH (in the case of Mobile Originating Call).

CHANNEL_REQUIRED174817021191/n173016061607174417461609/21611/2

MS BTS BSC PCU

CHANNEL_ACTIVATE


17501193/n

1195 or 1196

MSC

CONNECTION REQUEST (L3 INFORMATION)

Set timer TchnAck

Reset timer TchnAck

Set timer T3101

Reset timer T3101

IMMEDIATE_ASSIGNMENT_CMD


1629/0

17491192/n

11081502

IMMEDIATE_ASSIGN

SABM(CM_SERVICE_REQUEST)

UA

CONNECTION_CONFIRM

DTAP (AUTHENTIFICATION_REQUIRED)

DTAP (AUTHENTIFICATION_RESPONSE)

11051104/0

11071501

11081500


DATP (AUTH_REQUIRED)

DTAP (AUTH_RESPONSE)


AUTH_RESPONSE

AUTH_REQUIRED


PE/DCL/DD/0125411--9001--125


SETUP

MS BTS BSC PCU

DTAP (CALL_PROCEEDING)

MSC

DTAP (ALERTING)

11081500

11071503

1841/01094109517441746

1609/01611/0

CALL_PROCEEDING

SETUP

TDMA_TS_STATUS

TDMA_TS_STATUS_ACK

181418131812CONN_STATE_REQ

CONN_STATE_REQ_ACK

ALERTING

SETUP

DTAP (CALL_PROCEEDING)

11071501

11071501

DTAP (ALERTING)

ASSIGNMENT_REQUEST

(1)



CHANNEL_ACTIVATE

10491715

MS BTS BSC PCU

ASSIGNMENT_COMMAND


MSC

ASSIGNMENT_COMPLETE

Set timer TchnAck

Reset timer TchnAck

Set timer T3107

Reset timer T3107

UA

SABM

ASSIGNMENT_COMMAND

ASSIGNMENT_COMPLETE



RE_CHANNEL_RELEASE_ACK


ASSIGNMENT_COMPLETE


RF_CHANNEL_RELEASE


CONNECT_ACK

CONNECT

ALERT

160116021603162216231624162516261805180618071808

1195 or 1196

10501716

11081502

10441045

1607 (--1)17171718171917201721

1197/0 or 1197/1or 1709 and 1705/n (2)or 1710 and 1707/n


PE/DCL/DD/0125411--9001--125


MS BTS BSC PCU MSC


Set timer TDeacAck


UA

DISC

CHANNEL_RELEASE

CLEAR_COMMAND

RF_CHANNEL_RELEASE



CHANNEL_RELEASE

RELEASE

DISCONNECT

CALL

1107150317541164/201095 (--1)

RELEASE_COMPLETE

CLEAR_COMPLETE

DEACTIVATE_SACCH

119811991600162216231624162516261805 (3)1806 (3)1807 (3)1808 (3)1809/n (3)


Set timer TrfAck

Reset timer TrfAck

RELEASE_INDICATION


1812 (--1)17461611 1105 (--1)

TDMA_TS_STATUS

TDMA_TS_STATUS

1813 (--1)

11081502

(1) Before sending the TDMA TS STATUS message, the BSC performs theswitching connection between Abis and Agprs interface.






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



Counternumber






1049 attempedTchFrSeizures number of TCH/FR assignment requests


1094 tcAllocated number of terrestrial links allocated



1104/0 sccpAlloccated number of SCCP connections for SSNBSSMAP in the BSC

1105 sccpAverageUsedMoy/Max/Cum/Ech


1107 aInputMessage number of BSSAP messages received bythe BSC


1164/20 trafficReleaseClearCommand number of communications in trafficphase released: CLEAR COMMANDmessage received

1191/n[n= 0 to 7]

channelRequestCauseXxx number of channel allocation requests:Cause Xxx

1192/n[n= 0 to 7]

immediateAssignmentSuc-cessCauseXxx

number of successful immediate assign-ments: Cause Xxx

1193/n[n= 0 to 3]

estabIndicSignallingCau-seXxx


1195 estabIndicSigPhase1 number of ESTABLISH INDICATIONmessages in establishment phasereceived for Phase I mobiles

1196 estabIndicSigPhase2 number of ESTABLISH INDICATIONmessages in establishment phasereceived for Phase II mobiles


PE/DCL/DD/0125411--9001--125


Counternumber



number of channels activated for speech:Full Rate algorithm


number of channels activated for speech:Enhanced Full Rate algorithm

1198 downlinkPowerCtrlMaxTch-Moy/Max/Cum/Ech

duration of maximum downlink power useon busy TCHs


duration of maximum uplink power useon busy TCHs

1500 aTransparentUp number of DTAP messages sent by theBSC to the MSC

1501 aTransparentDown number of DTAP messages received bythe BSC




orconnectionDurationTchTrZo-neMoy/Max/Cum/Ech

average duration and maximum durationof TCH/FR or preempted PDTCH con-nections in the celloraverage duration and maximum durationof TCH/FR or preempted PDTCH con-nections in the inner or outer zone of thecell



1602 uplinkPowerCtrlMaxSdc-chMoy/Max/Cum/Ech


1603 connectionDuration-SdcchTrZoneMoy/Max/Cum/Ech


1606 sdcchAllocatedTrZone number of SDCCH allocated in the inneror outer zone of the cell

1607 sdcchAllocatedUsedTrZone-Moy/Max/Cum/Ech


1609/2 tchFrAllocatedOverflowAl-locationTrZone

number of TCH/FR allocated in the inneror outer zone of the cell because ofSDCCH unavailability

1611/2 tchFrAveragedUsedOverflo-wAllocationTrZoneMoy/Max/Cum/Ech

average and maximum number of TCH/FR used in the inner or outer zone of thecell because of SDCCH unavailability



Counternumber




number of MS measurements messagesnot received by the cellornumber of MS measurements messagesnot received by the inner or outer zone ofthe cell

1623 rxLevDownLink


sum of downlink signal strength mea-surements performed by the MS in thecellorsum of downlink signal strength mea-surements performed by the MS in theinner or outer zone of the cell

1624 rxLevUpLink

orrxLevUpLinkTrZone

sum of uplink signal strength measure-ments performed by the MS in the cellorsum of uplink signal strength measure-ments performed by the MS in the inneror outer zone of the cell

1625 rxQualDownLink


sum of downlink signal quality measure-ments performed by the MS in the cellorsum of uplink signal strength measure-ments performed in the inner or outerzone of the cell

1626 rxQualUpLink


sum of uplink signal quality measure-ments performed by the MS in the cellorsum of uplink signal quality measure-ments performed in the inner or outerzone of the cell

1629/0 channelActivateSignallingFull-Rate

number of Full--Rate channels activatedfor signaling

1702 channelRequestExtended number of channels requested with a tim-ing advance greater than 63

1705/n[n = 0 to 6]

channelActivateTchFrDatax (x= 16 to 14400 b/s)

number of TCH/FR activation for trans-parent data service with a transmissionrate = x

1707/n[n = 0 to 2

channelActivateTchFrNDatax(x = 6 to 14500 b/s)

number of TCH/FR activation for nontransparent 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 nontransparent data service on TCH/FR


PE/DCL/DD/0125411--9001--125


Counternumber


1715 attemptedTchFrSeizu-resMsDualb

number of attempts of assignation of aTCH/FR or preempted PDTCH for dual-band mobiles

1716 successfulTchFrSeizu-resMsDualb

number of successful TCH/FR or pre-empted PDTCH assignations for dual-band mobiles

1717 abisTrauFrameDlReceived number of frames TRAU downlinkreceived

1718 abisTrauFrameDlCorrected number of frames TRAU downlink cor-rected

1719 abisTrauFrameDlMuted number of frames TRAU downlink thatcan not be corrected

1720 abisTrauFrameUlReceived number of frames TRAU uplink received

1721 ECU_Activation number of erroneous frames (ECU maybe activated or not)

1730 pagingResponse number of responses to paging requestsin the cell

1744 tchFrAllocated






1749 immediateAssignmentSuc-cess

number of successful immediate assign-ments


1754 trafficRelease number of releases while the commu-nication is in traffic phase

1805 msPowerIncControl number of MS increment power controlsordered by the L1M

1806 msPowerDecControl number of MS decrement power controlsordered by the L1M

1807 bsPowerIncControl number of BS increment power controlsordered by the L1M



Counternumber


1808 bsPowerDecControl number of BS decrement power controlsordered by the L1M

1809/n[n= 0 to 1]

timingAdvanceMaximum

ortimingAdvanceMaximumTr-Zone

maximum timing advance value for thecommunication in the cellormaximum timing advance value for thecommunication inthe inner or outer zoneof the cell

1812 allocatedCircuitTsMoy

orallocatedCircuitTsTrZoneMoy

number of TS allocations for traffic in cir-cuit mode in the cellornumber of TS allocations for traffic in cir-cuit mode in the inner or the outer zoneof the concentric cell

1813 allocatedPacketTsMoy/Max/Cum/EchorallocatedPacketTsTrZone-Moy/Max/Cum/Ech

number of TS allocations for packetmode in the cellornumber of TS allocations for packetmode in the inner or the outer zone of thecell

1814 gprsPreemption number of GPRS preemption successes


number of assignment request messagesreceived: modification from an SDCCH toa TCH channel


PE/DCL/DD/0125411--9001--125


1.2.7.2 GPRS procedure: no resource available for a PDTCH preemption

Data Flow Diagram: GPRS procedure (no available resource for a PDTCHpreemption)

ASSIGNMENT_REQUEST110715031841/0109410951744174417461609/01611/0

MS BTS BSC PCU

TDMA_TS_STATUS

TDMA_TS_STATUS_ACK16131815

1746 (--1)1611/0 (--1)

1842/01095 (--1)

11081502

MSC

ASSIGMENT_FAILURE

(1)



(1) : The internal counter 1057, allTchFrAllocatedTimeMoy/Max/Cum/Ech(average and maximum duration during which all TCH/FR resources and PDTCHresources configured as preemptable are used in the cell) is incremented after apreemption 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 theallocator sends an ASSIGNMENT FAILURE message)

• When a TCH--FR resource is free, the measurement is stopped and the timer1057 is incremented by the value of the measurement

In a cell with PDTCH resources configured (all TCH--FR resources are used andthere is a PDTCH pre--emptable):

• A new request for a TCH/FR is received by the BSC => a GPRS preemptionprocedure is launched and the PCU sends a TDMA_TS_STATUS_NACK..At this time, the measurement is started.

• Themeasurement is stopped as soon a resource is released or as soon the timerGprsPreemptionProtection elapses. The counter 1057 is incremented by thevalue of the measurement.


Counternumber










number of TCH/FR or preemptedPDTCH allocated for traffic in the inner ofouter zone of the cell

1611/0 tchFrAveragedUsedTchAl-locationTrZoneMoy/Max/Cum/Ech


1613 tchFrRessourceFailureTrZone number of TCH/FR or preemptedPDTCH allocation failures in the inner orouter zone of the cell


PE/DCL/DD/0125411--9001--125


Counternumber


1744 tchFrAllocated




average number of TCH/FR or pre-empted PDTCH used in the celloraverage number of TCH/FR or pre-empted PDTCH used in the zone (con-centric cell)

1815 gprsPreemptionNack number of GPRS preemption failures(requests non acknowledged by thePCU)




number of emission of ASSIGNMENTFAILURE messages on the A interface:modification from an SDCCH channel toa TCH channel



1.2.7.3 GPRS procedure: negative acknowledgement by the PCU for a PDTCH preemption

CHANNEL_RELEASE

TDMA_TS_STATUS_ACK

TDMA_TS_STATUS

ASSIGNMENT_REQUEST

CLEAR_COMMAND

CLEAR_COMPLETE

MS BTS BSC PCU

11071503

1841/01094109517441746

1609/01611/0

161318151746 (--1)1611/0 (--1)1842/01095 (--1)

MSC

11081502

1107150317531163/20

1108150210441045

ASSIGNMENT_FAILURE

CHANNEL_RELEASE

DEACTIVATE_SACCH

(1)


PE/DCL/DD/0125411--9001--125


UA

MS BTS BSC PCU

1601160216031623162416251626

1805 (2)1806 (2)1807 (2)1808 (2)1809/n (2)

MSC

REACTIVATE_ACK

DEACTIVATE_SACCH

DISC

1105 (--1)

1607 (--1)

RELEASE_INDICATION





(1) When the BSC receives the TDMATS STATUS NACKmessage with the errorcause, it aborts the current allocation procedure.





Counternumber













1163/20 signallingReleaseBtsClear-Command

number of communications in signalingphase released: sequencing error





1602 uplinkPowerCtrlMaxSdc-chMoy/Max/Cum/Ech


1603 connectionDuration-SdcchTrZoneMoy/Max/Cum/Ech


1607 sdcchAllocatedUsedTrZone-Moy/Max/Cum/Ech



number of TCH/FR or preemptedPDTCH allocated for traffic in the inner ofouter zone of the cell

1611/0 tchFrAveragedUsedTchAl-locationTrZoneMoy/Max/Cum/Ech



PE/DCL/DD/0125411--9001--125


Counternumber


1613 tchFrRessourceFailureTrZone number of TCH/FR allocation failures inthe zone (concentric cell)



number of MS measurements messagesnot received by the cellornumber of MS measurements messagesnot received by the inner of the outerzone of the cell

1623 rxLevDownLink


sum of downlink signal strength mea-surements performed by the MS in thecellorsum of downlink signal strength mea-surements performed by the MS in theinner or outer zone of the cell

1624 rxLevUpLink

orrxLevUpLinkTrZone

sum of uplink signal strength measure-ments performed by the MS in the cellorsum of downlink signal strength mea-surements performed by the MS in theinner or outer zone of the cell

1625 rxQualDownLink


sum of downlink signal quality measure-ments performed by the MS in the cellorsum of downlink signal quality measure-ments performed by the MS in the inneror outer zone of the cell

1626 rxQualUpLink


sum of uplink signal quality measure-ments performed by the MS in the cellorsum of uplink signal quality measure-ments performed by the MS in the inneror outer zone of the cell

1744 tchFrAllocated





Counternumber




1753 signallingReleaseBts number of releases while the commu-nication is in “signaling phase” and a cellassociated to the communication

1805 msPowerIncControl number of MS increment power controlsordered by the L1M

1806 msPowerDecControl number of MS decrement power controlsordered by the L1M

1807 bsPowerIncControl number of BS increment power controlsordered by the L1M

1808 bsPowerDecControl number of BS decrement power controlsordered by the L1M

1815 gprsPreemptionNack number of GPRS preemption failures(requests non acknowledged by thePCU)




number of emission of ASSIGNMENTFAILURE messages on the A interface:modification from an SDCCH channel toa TCH channel

1.2.7.4 Counter behavior when GPRS is activated

The following counter definition table lists the BTS and BSC counters taking intoaccount the type of radio channel resource (TCH or pre--empted PDTCH). Theirbehavior is not influenced by GPRS activation.

The behavior of the other counters not listed in this table does not depend onchanneltype (TCH full rate or pre--empted PDTCH).

As a consequence, GPRS has no impact on the other counters (for examplethose for the handover). Their behavior is strictly the same with or withoutGPRS activation.

Note: GPRS activation means enabling GPRS calls when GPRS is configured.


PE/DCL/DD/0125411--9001--125


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 theoriginating circuit call using a configured TCH Channel will have a RACHthat 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 aTCH).

• Writing ”y” means that those calls, at some point, will concern this counter.

Example: RACH access for Originating call will deserve a “y” because theoriginating circuit call using a reconfigured PDTCH Channel will have aRACH 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 madebetween RACH dedicated to Circuit Calls or Packet Calls

1027 y y y This counter is computed at the BTS level; no distinction is madebetween RACH dedicated to Circuit Calls or Packet Calls

1028 y y y This counter is computed at the BTS level; no distinction is madebetween Paging dedicated to Circuit Calls or Packet Calls.




1033 y y y This counter is computed at the BTS level; no distinction is madebetween RACH dedicated to Circuit Calls or Packet Calls.

1044 y y n The object identifier is used to set a mdCounterIdArray field.






NoteCPCCPCCTCounter


1057 y y n Number of milliseconds during which all the available TCH_FRresources and pre--emptable PDTCH resources are used. Thiscounter starts measurement on allocation of all the availableTCH 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 atthe 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.










PE/DCL/DD/0125411--9001--125


NoteCPCCPCCTCounter










































NoteCPCCPCCTCounter
















1300 y y y OMC--R management






1400 y y y This counter gives the Real load of the processor. Note that theload of a given BSC processor is impacted by GPRS messagestreated by this processor.





1504 y n n GSM--R & GPRS can not be activated at the same time;

1505 y n n GSM--R & GPRS can not be activated at the same time;










PE/DCL/DD/0125411--9001--125


NoteCPCCPCCTCounter




1609/n y y n Number of full rate TCH allocations. This counter includesTCH/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 preemptedPDTCH 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 andthus considered as used from the BSS side. During the pre--emp-tion, the PDTCH is re--configured as TCH_FR and then assignedto a Circuit Call. As a result, measurement of interferencesinvolves configured (static) TCH_FR only.









1700 y y n Number of available TS for circuit calls. Used resources arecounted as available. This counter is related to TCH_FR chan-nel, pre--emptable PDTCH and PDTCH not allocated toPCUSN.



1705 y y n This counter is related to TCH_FR & pre--empted PDTCH chan-nel type (Circuit Call).


1707 y y n This counter is related to TCH_FR & pre--empted PDTCH chan-nel type (Circuit Call).






NoteCPCCPCCTCounter



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 takeinto account pre--emptable PDTCH) is lower than a minimumthreshold,_ or when the number of queued TCH requests is greater than athreshold.


1716 y y n This counter is related to TCH_FR & pre--empted PDTCH chan-nel type (Voice Call); it gives the number of successful TCHassignations for a dualband mobile.






1722 y n n GSM--R & GPRS can not be activated at the same time.










1748 The object identifier is used to set a mdCounterIdArray field.















PE/DCL/DD/0125411--9001--125


NoteCPCCPCCTCounter





































1800 y n n GSM--R & GPRS cannot be activated at the same time.

1801 y y n




NoteCPCCPCCTCounter

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 PDTCHpre--empted) allocated to circuit traffic. Type: load.

1813 y y n This counter gives the number of PDTCH channels given to thePCU 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.















PE/DCL/DD/0125411--9001--125


NoteCPCCPCCTCounter













3000/n y y n Each counter has a value between 0 and 100.; the value 100represents a 100% load.

3001/n y y n Each counter has a value between 0 and 100.; the value 100represents a 100% load.

3004/n y y n Each counter has a value between 0 and 100 (the value 100represents a 100% usage of the memory).

3005/n y y n Each counter has a value between 0 and 100 (the value 100represents a 100% usage of the memory).

3008/n y y n The object identifier is used to set a mdCounterIdArray field.

1.2.8 BSC equipment

1.2.8.1 CPUE overload

The process that detects CPUE processor overloads in the BSC is built around acounter that tallies the accumulated cost of transaction processing for calls handledby the BSC.

Call regulation is triggered when the counter crosses a given threshold value, andis gradually applied as the BSC starts to refuse new calls according to four definedpriority levels.

Nortel Networks Confidential 1--143


1.2.9 PCUSN

1.2.9.1 Flow Control

The flow control procedure is initiated by the BSS. The flow control parametersallow the SGSN to locally control its transmission output in the SGSN to BSSdirection. The SGSN shall perform flow control on each BVC (BVC flow controlmechanism) 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/015005/0

LLC_DL_FRAME_MS2

15004/015005/0

LLC_DL_FRAME_MS3

15004/015005/0

BVC_FLOW_CONTROL_REQUESTS

15010/0BVC_FLOW_CONTROL_ACK

LLC_DL_FRAME_MS4

15004/015005/0

LLC_DL_FRAME_MS4

15004/015005/0

LLC_DL_FRAME_MS4

15004/015005/0

MS4_FLOW_CONTROL_REQUESTS

15010/1MS4_FLOW_CONTROL_ACK

List of Counters incremented during this procedure:

Nortel Networks Confidential1--144

PE/DCL/DD/0125411--9001--125


Counternumber

Counter name Function GPRS/EDGE

15004/0 pduDataDn number BSSGP DL--UNITDATAPDU received by the BVC(SGSN-->PCU)

G/E

15005/0 octetsDataDn cumulative size (in bytes) of all theBSSGP DL--UNITDATA PDUreceived by the BVC(SGSN-->PCU). The size does notinclude the FR and NS header

G/E

15010/0 bvcFlowControlRequests

number of BSSGPFLOW--CONTROL--BVC PDUsent by the BVC (PCU-->SGSN)

G/E

15010/1 msFlowControlRequests

number of BSSGPFLOW--CONTROL--MS PDU sentby the BVC (PCU-->SGSN)

G/E

1.2.9.2 LLC Discarded

This procedure is used by the BSS to indicated that a number of bufferedLLC--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/015005/0

LLC_DL_FRAME_MS1

15004/015005/0

LLC_DL_FRAME_MS1

15004/015005/0

BSSGP_DISCARDED_PDU

15012/015012/1




Counternumber



G/E


G/E

15012/0 llcDiscardedPdu Number of BSSGPLLC--DISCARDED PDU sent forthe BVC (PCU-->SGSN)

G/E

15012/1 llcDiscardedOctets Cumulative size (in bytes) of allthe bytes discarded by theBSSGP DISCARDED PDU sentfor the BVC ( the number of bytesdiscarded is specified in the field“number of octets affected)

G/E

1.2.9.3 UL TBF Establishment: Normal Completion

The UL TBF establishment procedure is used by the mobile station to establish aTBF to support the transfer of LLC PDUs in the direction from the MS to thenetwork.


PE/DCL/DD/0125411--9001--125


Data Flow Diagram: Establishment of an UL TBF in two phases access with firstphase in CCCH

MS PCUSN SGSN


CHANNEL_REQUEST

15059/0

15058/0

PACKET_RESOURCE_REQUEST

15056/115047/0

PACKET_UPLINK_ASSIGNMENT

15047/1

PACKET_CONTROL_ACK

15047/0


Counternumber


15047/0 controlBlocksUp Cumulative number of RLC/MACcontrol blocks received in uplinkby the PCU on this TDMA. Thismeans all the valid RLC/MACcontrol blocks received on theAgprs and related to UL or DLTBF.

G

15047/1 controlBlocksDn Cumulative number of RLC/MACcontrol blocks different fromPacket Downlink Dummy ControlBlock sent by the PCU

G

15056/1 packetResourceRequest

Cumulative number of PacketResource Request messagesreceived by the PCU in this cell forthe second phase of an uplinkestablishment

G/E



Counternumber

GPRS/EDGE


15058/0 upTbfImmediateAssignment

Cumulative number of ImmediateAssignment Uplink messages sentby the PCU to establish an ULTBF in this cell. In the case ofCCCH management of the BTS,this counter corresponds to thecumulative values periodicallyreceived from the BTS in theCCCH information

G/E

15059/0 channelRequestCcch Cumulative number of RACH(Channel Request) received bythe PCU in this cell

G/E

1.2.9.4 UL TBF Establishment: UL TBF Establishment during DL transfer

The mobile station may request establishment of an uplink TBF during a downlinkTBF by including aChannel Request Description information element in the PacketDownlink Ack/Nack message.


PE/DCL/DD/0125411--9001--125


Data Flow Diagram: Establishment of an UL TBF during DL TBF

MS PCUSN SGSN

DL_DATA_BLOCK (POLLING)

DL_DATA_BLOCK

15046/1

15046/1

PACKET_DOWNLINK_ACK/NACK (1)

15049/115047/015034/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


Counternumber


15034/0 PDANWithUlReq Cumulative number of PacketDownlink Ack/Nack messages,with the Channel RequestDescription included

G/E

15046/0 dataBlocksUp Cumulative number of RLC datablocks received by the PCU onthis TDMA. This means all thevalid RLC data blocks received onthe Agprs, including theretransmitted and out of sequenceframes.

G

15046/1 dataBlocksDn Cumulative number of RLC blockssent by the PCU on this TDMA.

G



Counternumber

GPRS/EDGE



G


G

15049/1 packetAckNackDn Cumulative number of PacketDownlink Ack/Nack messagesreceived by the PCU on thisTDMA.

G

1.2.9.5 UL TBF Release: Normal Completion

The normal UL TBF release procedure occurswhen themobile station sends aRLCdata block with CV=0 while the BSS has correctly received all the UL RLC datablocks.


PE/DCL/DD/0125411--9001--125


Data Flow Diagram: Normal UL TBF release

MS PCUSN SGSN

PACKET_UPLINK_ACK/NACK

UL_DATA_BLOCK (1)

15046/0

15047/1

UL_DATA_BLOCK

15046/0

PACKET_UPLINK_ACK/NACK (2)

15047/1

PACKET_CONTROL_ACK

15033/015055/015047/0

(1) CV= 0(2) FAI = 1


Counternumber


15033/0 upTbfReleases Cumulative number of UL TBFreleased in the cell (related to halfduplex or full duplex transfers).This counter counts the normaland abnormal releases due to lossof communications, OAM event,TS sharing event.

G/E


G



Counternumber

GPRS/EDGE



G


G

15055/0 tbfNormalReleaseUp Cumulative number of normalreleases of UL TBFs (related tohalf duplex or full duplex transfer).

G/E

1.2.9.6 Abnormal UL TBF Release: lossOfComNN0002

This abnormal release occurs when there is no progression of the received window(no progression of V(Q) in UL).


PE/DCL/DD/0125411--9001--125


Data Flow Diagram: Abnormal release of an UL TBF due to non progression ofV(Q)

MS PCUSN SGSN

PACKET_UPLINK_ACK/NACK (V(Q))

UL_DATA_BLOCK

15046/0

15047/1

UL_DATA_BLOCK

15046/0


15047/1

UL_DATA_BLOCK

15046/0

UL_DATA_BLOCK

15046/0

UL_DATA_BLOCK

15046/0


15047/1

UL_DATA_BLOCK

15046/0

UL_DATA_BLOCK

15046/0


15057/015033/015047/1

NN0002++

NN0002++

NN0002++=NN0002Max

NN0002++




Counternumber



G/E


G


G

15057/0 lossOfComNN002Max Number of abnormal releases dueto non progression of V(Q) inuplink and V(A) in downlink. Thismeans the number of abnormalreleases with a mobile in uplinkTBF or downlink TBF because thereceived or transmitted windowdoes not progress

G/E

1.2.9.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).


PE/DCL/DD/0125411--9001--125


Data Flow Diagram: Abnormal release of an UL TBF due to non progression ofV(Q) during full duplex transfer, in the case that DL TBF is also released.

MS PCUSN SGSN

DL_DATA_BLOCK

UL_DATA_BLOCK

15046/0

15046/1

UL_DATA_BLOCK

15046/0


15047/1

UL_DATA_BLOCK

15046/0

DL_DATA_BLOCK

15046/1


15047/1

UL_DATA_BLOCK

15046/0

DL_DATA_BLOCK

15046/1

UL_DATA_BLOCK

15046/0


15057/015057/315033/015033/115047/1

NN0002++

NN0002++

NN0002++

NN0002++=NN0002Max




Counternumber



G/E

15033/1 dnTbfReleases Cumulative number of DL TBFreleased in the cell (related to halfduplex or full duplex transfers).This counter counts the normaland abnormal releases due to lossof communications, OAM event,TS sharing event.

G/E


G


G


G


G/E

15057/3 lossOfComT3195 Number of downlink TBFabnormal releases due to nonresponse from the mobile duringthe establishment procedure orpacket transfer

G/E

1.2.9.8 Abnormal UL TBF Release: N3101

This abnormal release occurs when the mobile station does not respond to USF.


PE/DCL/DD/0125411--9001--125


Data Flow Diagram: Non response from the mobile station after N3101 scheduledblocks (means with USF set in downlink)

MS PCUSN SGSN

DL_DATA_BLOCK (USF)

15046/1

UL_DATA_BLOCKN3101++

UL_DATA_BLOCK

15033/015057/115057/2

N3101++=N3101Max

DL_DATA_BLOCK (USF)

15046/1

DL_DATA_BLOCK (USF)

15046/1



Counternumber



G/E


G



Counternumber

GPRS/EDGE


15057/1 lossOfComT3169 Number of uplink TBF abnormalreleases due to non responsefrom the mobile during theestablishment procedure or packettransfer. In the case of full duplextransfer, this also counts theuplink TBF releases consecutiveto downlink TBF abnormalrelease.

G/E

15057/2 lossOfComNT0001 Number of uplink TBF abnormalreleases due to non responsefrom the mobile to USF andassignment messages

G/E

1.2.9.9 Abnormal UL TBF Release (FULL Duplex): N3101

This abnormal release occurs when the mobile station does not respond to USF.


PE/DCL/DD/0125411--9001--125


Data Flow Diagram: Non response from the mobile station after N3101 scheduledblocks (meanswithUSF set in downlink) during full duplex transfer, in the case thatDL TBF is also released

MS PCUSN SGSN

DL_DATA_BLOCK

15046/1

DL_DATA_BLOCK

15046/1


UL_DATA_BLOCK

15033/015057/115057/215057/315033/1

N3101++=N3101Max

UL_DATA_BLOCK

15046/0



Counternumber


15033/0 upTbfReleases Cumulative number of UL TBFreleased in the cell (related to halfduplex or full duplex transfers).This counter counts the normaland abnormal releases due to lossof communications, OAM event,TS sharing event

G/E

15033/1 dnTbfReleases Cumulative number of DL TBFreleased in the cell (related to halfduplex or full duplex transfers).This counter counts the normaland abnormal releases due to lossof communications, OAM event,TS sharing event

G/E



Counternumber

GPRS/EDGE


15046/0 dataBlocksUp Cumulative number of RLC datablocks received by the PCU onthis TDMA. This means all thevalid RLC data blocks received onthe Agprs, including theretransmitted and out of sequenceframes

G

15046/1 dataBlocksDn Cumulative number of RLC blockssent by the PCU on this TDMA

G

15057/1 lossOfComT3169 Number of uplink TBF abnormalreleases due to non responsefrom the mobile during theestablishment procedure or packettransfer. In the case of full duplextransfer, this also counts theuplink TBF releases consecutiveto downlink TBF abnormal release

G/E


G/E


G/E

1.2.9.10 Abnormal UL TBF Release: UP_NASSIGNMAX

This abnormal release occurs when themobile station does not acknowledge uplinkassignment messages.


PE/DCL/DD/0125411--9001--125


Data Flow Diagram: Non response from the mobile after UP_NASSIGNMAXPacket Uplink Assignment messages

MS PCUSN SGSN

CHANNEL_REQUEST (RACH)

15059/0

PACKET_UPLINK_ASSIGNMENT (POLLING)

15047/1

Up_Nassign++


15058/0


15056/115047/0

PACKET_CONTROL_ACK


15047/1PACKET_CONTROL_ACK





15033/015057/115057/215036/0

Up_Nassign++

Up_Nassign++

Up_Nassign++=Up_NassignMax



Up_Nassign++




Counternumber


15033/0 upTbfReleases Cumulative number of UL TBFreleased in the cell (related to halfduplex or full duplex transfers).This counter counts the normaland abnormal releases due to lossof communications, OAM event,TS sharing event

G/E

15036/0 ulsecondPhaseRadioFailure

Cumulative number of abnormalreleases during second phaseuplink establishment (half duplextransfer), due to radio linkproblems

G/E

15047/0 controlBlocksUp Cumulative number of RLC/MACcontrol blocks received in uplinkby the PCU on this TDMA. Thismeans all the valid RLC/MACcontrol blocks received on theAgprs and related to UL or DLTBF

G


G


Cumulative number of PacketResource Request messagesreceived by the PCU in this cell forthe second phase of an uplinkestablishment

G/E


G/E


G/E


PE/DCL/DD/0125411--9001--125


Counternumber

GPRS/EDGE



Cumulative number of ImmediateAssignment Uplink messages sentby the PCU to establish and ULTBF in the cell. In the case ofCCCH management at the BTS,this counter corresponds to thecumulative values periodicallyreceived from the BTS in theCCCH information.

G/E


G/E

1.2.9.11 Abnormal UL TBF Release (FULL Duplex): UP_NASSIGNMAX

This abnormal release occurs when themobile station does not acknowledge uplinkassignment messages.



Data Flow Diagram: No response from the mobile after UP_NASSIGNMAXPacket Uplink Assignment messages during full duplex transfer, in the case that theDL TBF is also released

MS PCUSN SGSN

DL_DATA_BLOCK

15046/1


15047/1

Up_Nassign++


15046/1

PACKET_CONTROL_ACK







15033/015057/115057/215033/115057/3

Up_Nassign++

Up_Nassign++

Up_Nassign++=Up_NassignMax


15047/1

PACKET_CONTROL_ACKUp_Nassign++


15047/015034/0

(1) Channel Request Description



PE/DCL/DD/0125411--9001--125


Counternumber



G/E


G/E

15034/0 PDANWithUlReq Cumulative number of PacketDownlink Ack/Nack messages,with the Channel RequestDescription included

G/E

15046/1 dataBlocksDn Cumulative number of RLC datablocks sent by the PCU on thisTDMA.

G

15047/0 controlBlocksUp Cumulative number of RLC/MACcontrol blocks in uplink by thePCU on this TDMA. This meansall the valid RLC/MAC controlblocks received on the Agprs andrelated to UL or DL TBF.

G

15047/1 controlBlocksDn Cumulative number of RLC/MACcontrol blocks different fromPacket Downlink Dummy ControlBlock sent by the PCU on thisTDMA

G


G/E



Counternumber

GPRS/EDGE



G/E


G/E

1.2.9.12 Abnormal UL TBF Release: N3103

This abnormal release occurswhen themobile station does not acknowledge the lastpacket uplink ack/nack (with FAI=1).


PE/DCL/DD/0125411--9001--125


Data Flow Diagram: Non response from the mobile after N3103 Packet UplinkAck/Nack sent with FAI=1

MS PCUSN SGSN

UL_DATA_BLOCK (1)

15046/0

PACKET_UPLINK_ACK/NACK (FAI=1)

15047/1

N3103++PACKET__CONTROL_ACK


15047/1PACKET__CONTROL_ACK


15047/1PACKET__CONTROL_ACK

15033/015057/1

N3103++

N3103++=N3103Max


15047/1

PACKET__CONTROL_ACKN3103++


15047/1

UL_DATA_BLOCK

15046/0

(1) CV= 0(2) V(Q) <> V(R)




Counternumber



G/E


G


G


G/E

1.2.9.13 Abnormal UL TBF Release (FULL Duplex): N3103

This abnormal release occurswhen themobile station does not acknowledge the lastpacket uplink ack/nack (with FAI=1).


PE/DCL/DD/0125411--9001--125


Data Flow Diagram: Non response from the mobile after N3103 Packet UplinkAck/Nack sent with FAI=1 during full transfer, in the case that the DL TBF is alsoreleased

MS PCUSN SGSN

DL_DATA_BLOCK

15046/1


15047/1

N3103++PACKET_CONTROL_ACK


15047/1

PACKET_CONTROL_ACK



15033/015057/115057/315033/1

N3103++

N3103++=N3103Max



N3103++


15047/1

UL_DATA_BLOCK

15046/0

UL_DATA_BLOCK (1)

15046/0

DL_DATA_BLOCK

15046/1

(1) CV= 0(2) V(Q) <> V(R)




Counternumber



G/E


G/E


G


G


G


G/E


G/E


PE/DCL/DD/0125411--9001--125


1.2.9.14 DL TBF Establishment: MS in StandBy State

For amobile station in Standby State, the networkmay initiate the pagingprocedurefor downlink packet transfer in order to obtain the mobile station cell location forthe downlink packet transfer. The mobile station performs a page response bysending and LLC PDU to the network.



Data FlowDiagram: Paging procedure initiated by the network for downlink packettransfer towards a MS in standby state

MS PCUSN SGSN

CHANNEL_REQUEST (RACH)

15059/0


15047/1


15058/0


15056/115047/0

PAGING

PACKET_CONTROL_ACK

15047/1

UL_DATA_BLOCK (PAGING RESPONSE)

15046/0

PACKET_TIMESLOT_RECONFIG (1)

15047/1

PACKET_CONTROL_ACK

15047/0

LLC_UL_FRAME

15004/115005/1


15047/1

PACKET_CONTROL_ACK

15047/1

DL_DATA_BLOCK

15046/1 LLC_DL_FRAME

15004/015005/015031/1

(1) Downlink pre--establishment(2) FAI = 1



PE/DCL/DD/0125411--9001--125


Counternumber



G/E

15004/1 pduDataUp number BSSGP UL--UNITDATAPDU sent by the BVC(PCU-->SGSN)

G/E


G/E

15005/1 octetsDataUp cumulative size (in bytes) of all theBSSGP DL--UNITDATA PDUreceived by the BVC(PCU-->SGSN). The size does notinclude the FR and NS header

G/E

15031/1 FirstDlUnitDataFrame Cumulative number ofpre--established downlink TBFwithout reception of aDL--UNITDATA for this TBF.

G/E

15046/0 dataBlocksUp Cumulative size (in bytes) of allthe BSSGP UL--UNITDATA PDUsent by the BVC (PCU-->SGSN).The size does not include the FRand NS header

G

15046/1 dataBlocksDn Cumulative number of RLC datablocks sent by the PCU on thisTDMA

G


G


G



Counternumber

GPRS/EDGE



Cumulative number of PacketResource Request messagesreceived by the PCU in this cell forthe second phase of an uplinkestablishment.

G/E


Cumulative number of immedateAssignment Uplink messages sentby the PCU to establish an ULTBF in the cell. In the case ofCCCH management at the BTS,this counter corresponds to thecumulative values periodicallyreceived from the BTS in theCCCH information.

G/E


G/E

1.2.9.15 DL TBF Establishment: MS in Ready State

The network may initiate the establishment of a downlink TBF to support thetransfer of LLC PDUs in the direction from the network to the mobile station.


PE/DCL/DD/0125411--9001--125


Data Flow Diagram: Downlink establishment towards a mobile in Ready State andPacket Idle Mode

MS PCUSN SGSN


15058/2

PACKET_POLLING_REQUEST

15047/1

PACKET_POWER_CONTROL_TIMING_ADVANCE

15047/1

PACKET_CONTROL_ACK

DL_DATA_BLOCK

15046/1

DL_DATA_BLOCK

15046/1

PACKET_DOWNLINK_ASSIGNMENT

15047/1

PACKET_CONTROL_ACK

15047/0

LLC_DL_FRAME

15004/015005/015031/1

DL_DATA_BLOCK (1)

15046/1

15047/0

PACKET_DOWNLINK_ACK/NACK

15047/0

(1) Fast Downlink Assignment




Counternumber



G/E

15005/0 octetsDataDn Cumulative size (in bytes) of allthe BSSGP DL--UNITDATA PDUreceived by the BVC(SGSN-->PCU). The size does notinclude the FR and NS header

G/E


G/E


G


G


G

15058/2 dnTbfImmediateAssignment

Cumulative number of ImmediateAssignment Downlink messagessent by the PCU to establish a DLTBF

G/E

1.2.9.16 DL TBF Establishment during UL transfer

During uplink TBF, the network may initiate a downlink TBF by sending a PacketDownlink Assignment message or a Packet Timeslot Reconfigure, to the mobilestation.

Data Flow Diagram: Establishment with Packet Downlink Assignment and PacketTimeslot Reconfigure


PE/DCL/DD/0125411--9001--125


Note: To assign DL resources which need modification of the UL resources, aPacket Timeslot Reconfigure message is sent:

MS PCUSN SGSN

PACKET_TIMESLOT_RECONFIGURE

UL_DATA_BLOCK

15046/1

15047/1

PACKET_CONTROL_ACK

15047/0

DL_DATA_BLOCK

15046/1

UL_DATA_BLOCK

15046/1 LLC_DL_FRAME

15004/015005/015031/1


Counternumber



G/E


G/E


G/E


G



Counternumber

GPRS/EDGE



G


G

1.2.9.17 DL TBF Release: Normal Completion

The network initiates release of a downlinkTBF by sending an RLCdata blockwiththe 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, itshall send a Packet Downlink Ack/Nack with Final Ack Indicator (FAI) set to thevalue of 1.

Data Flow Diagram: Normal DL TBF Release

MS PCUSN SGSN

DL_DATA_BLOCK

15046/1


15033/115047/015055/1

DL_DATA_BLOCK (1)

15046/1

(1) FBI=1, Polling(2) FAI=1



PE/DCL/DD/0125411--9001--125


Counternumber



G/E


G


G

15055/1 tbfNormalReleaseDn Cumulative number of normalreleases of DL TBFs (related tohalf duplex or full duplex transfer).

G/E

1.2.9.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 ofV(A)

MS PCUSN SGSN


15046/1

PACKET_DOWNLINK_ACK/NACK (V(A))

15047/015057/015033/1

DL_DATA_BLOCK

15046/1


15047/0

DL_DATA_BLOCK

15046/1


15046/1


15047/0

DL_DATA_BLOCK

15046/1

DL_DATA_BLOCK

15046/1


15046/1

N0002++

N0002++

N0002++=NN0002Max



PE/DCL/DD/0125411--9001--125


Counternumber



G/E


G


G


G/E

1.2.9.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 ofV(A) during full duplex transfer, in the case that the UL TBF is also released

MS PCUSN SGSN

UL_DATA_BLOCK

15046/0


15047/015057/015057/115033/115033/0

DL_DATA_BLOCK

15046/1


15047/0

DL_DATA_BLOCK

15046/1


15046/1


15047/0

DL_DATA_BLOCK

15046/1

DL_DATA_BLOCK

15046/1


15046/1

N0002++

N0002++

N0002++=NN0002Max


15046/1

UL_DATA_BLOCK

15046/0



PE/DCL/DD/0125411--9001--125


Counternumber



G/E


G/E


G


G


G



Counternumber

GPRS/EDGE



G/E


G/E

1.2.9.20 Abnormal DL TBF Release: N3105

This abnormal release occurs when the mobile station does not send a PacketDownlink Ack Nack after N3105 downlink data block sent with S/P=1.


PE/DCL/DD/0125411--9001--125


Data FlowDiagram:Non response from themobile after N3105 downlink datawithS/P=1

MS PCUSN SGSN


15046/1

15033/115057/3

DL_DATA_BLOCK

15046/1


15047/0


15046/1


15046/1

N3105++PACKET_DOWNLINK_ACK/NACK


15046/1




15046/1

N3105++=N3105MaxPACKET_DOWNLINK_ACK/NACK




Counternumber



G/E


G


G


G/E

1.2.9.21 Abnormal DL TBF Release (FULL Duplex): N3105

This abnormal release occurs when the mobile station does not send a PacketDownlink Ack Nack after N3105 downlink data block sent with S/P=1.


PE/DCL/DD/0125411--9001--125


Data FlowDiagram:Non response from themobile after N3105 downlink datawithS/P=1 during full duplex transfer, in the case that the UL TBF is also released.

MS PCUSN SGSN


15046/1

15033/115057/315057/115033/0

DL_DATA_BLOCK

15046/1


15047/0


15046/1


15046/1



15046/1




15046/1

N3105++=N3105MaxPACKET_DOWNLINK_ACK/NACK

UL_DATA_BLOCK

15046/0

UL_DATA_BLOCK

15046/0




Counternumber



G/E


G/E


G


G


G


G/E


G/E


PE/DCL/DD/0125411--9001--125


1.2.9.22 Abnormal DL TBF Release: DN_NASSIGNMAX

This abnormal release occurs when the mobile station does not acknowledgedownlink assignment messages.

Data Flow Diagram: Non response from the mobile after DN_NASSIGNMAXPacket Downlink Assignment messages.

MS PCUSN SGSN

PACKET_DOWNLINK_ASSIGNMENT(POLLING)

15047/1

Dn_Nassign++PACKET_CONTROL_ACK




15047/1

PACKET_CONTROL_ACK



15033/115057/3

Dn_Nassign++

Dn_Nassign++

Dn_Nassign++=Dn_NassignMax



Dn_Nassign++




Counternumber



G/E


G


G/E

1.2.9.23 Abnormal DL TBF Release (FULL Duplex): DN_NASSIGNMAX

This abnormal release occurs when the mobile station does not acknowledgedownlink assignment messages.


PE/DCL/DD/0125411--9001--125


Data Flow Diagram: Non response from the mobile after DN_NASSIGNMAXPacket Downlink Assignment messages during full duplex transfer, in the case thatthe DL TBF is also released.

MS PCUSN SGSN

PACKET_TIMESLOT_RECONFIG(POLLING)

15047/1

Dn_Nassign++

PACKET_UPLINK_ACK/NACK

15049/0

UL_DATA_BLOCK

15046/0

PACKET_CONTROL_ACK


15047/1

PACKET_CONTROL_ACK





15033/115057/315057/115033/0

Dn_Nassign++

Dn_Nassign++

Dn_Nassign++=Dn_NassignMax



Dn_Nassign++




Counternumber



G/E


G/E


G


G

15049/0 packetAckNackUp Cumulative number of PacketUplink Ack/Nack messages sentby the PCU on this TDMA

G


PE/DCL/DD/0125411--9001--125


Counternumber

GPRS/EDGE



G


G

1.2.9.24 Abnormal DL TBF Release: No Final PDAN

This abnormal release occurswhen themobile station does not acknowledge the lastdownlink data block (sent with FBI=1 and S/P=1)



Data Flow Diagram: Non response from the mobile after NN0002 downlink datablocks sent with FBI=1 and S/P=1

MS PCUSN SGSN

NN0002++

DL_DATA_BLOCK (1)

15046/1


NN0002++

DL_DATA_BLOCK (1)

15046/1


NN0002++

DL_DATA_BLOCK (1)

15046/1


NN0002++=NN0002Max

DL_DATA_BLOCK (1)

15046/1


15057/415057/015033/1

(1) FBI=1, Polling


Counternumber



G/E


G


PE/DCL/DD/0125411--9001--125


Counternumber

GPRS/EDGE



G/E

15057/4 lossOfComT3191 Number of downlink TBFabnormal releases which occurduring the release of a downlinkTBF (while the PCU is waiting forthe last acknowledgement comingfrom the mobile).

G/E

1.2.9.25 Abnormal DL TBF Release (FULL Duplex): No Final PDAN

This abnormal release occurswhen themobile station does not acknowledge the lastdownlink data block (sent with FBI=1 and S/P=1)

Data Flow Diagram: Non response from the mobile after NN0002 downlink datablocks sent with FBI=1 and S/P=1 during full duplex transfer, in the case that theUL TBF is also released.



MS PCUSN SGSN

NN0002++

DL_DATA_BLOCK (1)

15046/1


NN0002++=NN0002Max

DL_DATA_BLOCK (1)

15046/1


15057/315057/415057/115033/115033/0

UL_DATA_BLOCK

15046/0

NN0002++

DL_DATA_BLOCK (1)

15046/1


UL_DATA_BLOCK

15046/0

NN0002++

DL_DATA_BLOCK (1)

15046/1


UL_DATA_BLOCK

15046/0

(1) FBI=1, Polling



PE/DCL/DD/0125411--9001--125


Counternumber



G/E


G/E


G


G


G/E


G/E

15057/4 lossOfComT3191 Number of downlink TBFabnormal releases which occurduring the release of a downlinkTBF (while the PCU is waiting forthe last acknowledgement comingfrom the mobile).

G/E



1.2.9.26 Preemption

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

Data Flow Diagram: Preemption of radio timeslots.

MS1 PCUSN SGSNMS2 BSC

PCU_TDMA_TS_STATUS_NACK

UL_DATA_BLOCK

15046/0

PACKET_PDTCH_RELEASE

PCU_TDMA_TS_STATUS

CHANNEL_REQUEST

BVC_FLOW_CONTROL_REQUESTS

PCU_TDMA_TS_STATUS



BVC_FLOW_CONTROL_ACK

15010/0

PCU_TDMA_TS_STATUS_ACK

1814

1815



PE/DCL/DD/0125411--9001--125


Counternumber


1814 gprsPreemption Number of PDTCH preemptionsuccesses

G

1815 gprsPreemptionNack Number of PDTCH preemptionfailures (requests “nacked by thePCU)

G

15010/0 bvcFlowControlRequests

Number of BSSGPFLOW--CONTROL--BVC PDUsent by the BVC (PCU -->SGSN).

G/E


G

1.2.9.27 Cell Update: Packet Transfer

The cell reselection occurs when a mobile goes from one cell to another. Duringpacket transfer and from a PCU point of view, this corresponds to a release of TBFin one cell and the establishment of a new TBF in the other cell. Note that the cellupdate is controlled by the mobile station.



Data Flow Diagram: Cell reselection from cell A to cell B and establishment of anew uplink TBF in cell B

BTS_A PCUSN SGSN


15056/115047/0

BTS_B

UL_DATA_BLOCK

15046/0

CHANNEL_REQUEST

15059/0

DL_DATA_BLOCK

15046/1


15058/0


15047/1

PACKET_CONTROL_ACK

UL_DATA_BLOCK

FLUSH_LL_ACK

FLUSH_LL_BTS--A

15014/0

15047/0

15046/0 LLC_UL_FRAME

15004/115005/1



PE/DCL/DD/0125411--9001--125


Counternumber


15004/1 pduDataDn Number of BSSGPUL--UNITDATA PDU sent by theBVC (PCU-->SGSN).

G/E

15005/1 octetsDataUp cumulative size (in bytes) of all theBSSGP DL--UNITDATA PDUreceived by the BVC(PCU-->SGSN). The size does notinclude the FR and NS header

G/E

15014/0 msFlushLLRequest Number of BSSGP FLUSH--LLPDU received by the BVCI0 for allMS in the cell associated to theBVC (the BVC is indicated in themessage by the field BVCI (old)).

G/E


G


G


G


G


Cumulative number of PacketResource Request messagesreceived by the PCU in this cell forthe second phase of an uplinkestablishment.

G/E



Counternumber

GPRS/EDGE



Cumulative number of ImmediateAssignment Uplink messages sentby the PCU to establish and ULTBF in the cell. In the case ofCCCH management at the BTS,this counter corresponds to thecumulative values periodicallyreceived from the BTS in theCCCH information.

G/E


G/E

1.2.10 Advanced Speech Call Items (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)


PE/DCL/DD/0125411--9001--125


MS BTS BSC MSC

channel_required

channel_activate (SDCCH)

imm_ass

SCCP_CR(CM_serv_req [VBS or VGCS])

From the VBS or VGCSoriginator

RF_channel_release(SDCCH)

channel_request

channel_activate_ack

imm_ass_command

SABM(CM_serv_req [VBS or VGCS])est_ind(CM_serv_req [VBS or VGCS])

SCCP_CC

CM_serv_acc

setup(broadcast call Id)

assignment_reqchannel_activate (TCH)

channel_activate_ack

UA

assignment_command

SABM est_ind

UA

assignment_compassignment_comp

RF_channel_release_ack

1722

2037 (8W)

2036 (8W)



MS BTS BSC MSC

connect (to the VBS or VGCS callinitiator)

notification/NCH

channel_activate

channel_activate_ackSCCP_CC

For each cell in the GCA

Resource Controlling SCCP conn. setup:SCCP_CR(VGCS/VBS_ass_req)

VGCS/VBS_ass_result

notification_command

(cyclic notification process)

uplink_busy

(only in case of VGCS)

Call establishment indication

For each BSC in the GCA

Call Controlling SCCP connection setup:SCCP_CR(VGCS/VBS_setup)

SCCP_CC

VGCS/VBS_setup_ack


PE/DCL/DD/0125411--9001--125


Data Flow Diagram: Standard call termination (the originator releases the VBS/VGCS call)

MS BTS BSC MSC

VBS or VGCS call originator

RF_channel_release(SDCCH)

termination_request

channel_release

termination

clear_command

DISC

clear_complete

deactivate_SACCH


For each cell in the GCA

deactivate_SACCH_ack

Release_indication

SCCP_RLSD

Resource controlling cnx

clear_command

clear_complete

SCCP_RLSD

Notification_command

Channel_releaseUI(channel_release)

UI(channel_release)

UI(channel_release)

Deactivate_SACCH

Deactivate_SACCH_ack

RF_channel_release


For each BSC in the GCA Call controlling cnx

SCCP_RLSD

2053 (8W)



1.3 Permanent bsc observation counters

1.3.1 Counter classes

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

1.3.2 Common control channel monitoring

These counters are collected on the bts object and appear in an observation reporton bts level.

1.3.2.1 RACH access

Counter No. Q3 name Type1026 rachBusyCount totalizer

1027 rachAccessCount totalizer

1033 rachNonDecodedAvLevel value

1.3.2.2 Paging requests

Counter No. Q3 name Type1028 pchNoWait totalizer

1029 pchOneWait totalizer

1030 pchTwoWait totalizer

1031 pchMoreWait totalizer

1604 pchAveragedQueueLength load

1605 pchQueuePagesDiscardedTs2/Ts4/Ts6 totalizer

1.3.3 Radio resource allocation

These counters are collected on the bts object (non–concentric cell) or thetransceiverZone object (concentric cell), and appear in an observation report on btslevel (non–concentric cell) or transceiverZone level (concentric cell).


PE/DCL/DD/0125411--9001--125


1.3.3.1 SDCCH resources

Counter No. Q3 name Type1060or1060

allSdcchAllocatedTime

allSdcchAllocatedTimeTrZone

value

1606or1606

sdcchAllocated

sdcchAllocatedTrZone

totalizer

1607or1607

sdcchAveragedUsed

sdcchAveragedUsedTrZone

load

1608or1608

sdcchRessourceFailure

sdcchRessourceFailureTrZone

totalizer

1701or1701

sdcchAveragedAvailable

sdcchAveragedAvailableTrZone

load

1811 sdcchAverageConfigurated load

1.3.3.2 TCH resources

Counter No. Q3 name Type1609/n

or1609/n

tchFrAllocatedTchAllocationtchFrAllocatedPrimoAllocationtchFrAllocatedOverflowAllocationtchFrAllocatedWpsortchFrAllocatedTchAllocationTrZonetchFrAllocatedPrimoAllocationTrZonetchFrAllocatedOverflowAllocationTrZonetchFrAllocatedWpsTrZone

totalizer

1610 /n tchHrAllocatedtchHrAllocatedWps

totalizer

1611/n

or1611/n

tchFrAveragedUsedTchAllocationtchFrAveragedUsedPrimoAllocationtchFrAveragedUsedOverflowAllocationtchFrAveragedUsedWpsortchFrAveragedUsedTchAllocationTrZonetchFrAveragedUsedPrimoAllocationTrZonetchFrAveragedUsedOverflowAllocationTrZonetchFrAveragedUsedWpsTrZone

load



Counter No. TypeQ3 name1612 /n

or1612 /n

tchHrAveragedUsedTchAllocationtchHrAveragedUsedPrimoAllocationtchHrAveragedUsedOverflowAllocationortchHrAveragedUsedTchAllocationTrZonetchHrAveragedUsedPrimoAllocationTrZonetchHrAveragedUsedOverflowAllocationTrZone

load

1613or1613

tchFrResourceFailureortchFrResourceFailureTrZone

totalizer

1614or1614

tchHrResourceFailureortchHrResourceFailureTrZone

totalizer

1616/n tchAveragedQueueLengthHighPrioritytchAveragedQueueLengthOtherPriority

load

1617/n tchQueuingExpirationHighPrioritytchQueuingExpirationOtherPriority

totalizer

1618/n tchQueuingDurationHighPrioritytchQueuingDurationOtherPriority

value

1700or1700

tchFrAveragedAvailableortchFrAveragedAvailableTrZone

load

1714 (V12) cellOverloadDuration value

1726/n (V12) dataNtRateFbTchResLackdataNtRateFbTchConfNotAllowed

totalizer

1744or1744

tchFrAllocatedortchFrAllocatedTrZone

totalizer

1745 tchHrAllocatedNsc totalizer

1746or1746

tchFrAveragedUsedortchFrAveragedUsedTrZone

load

1747 tchHrAveragedUsedNsc load

1810 tchFrAverageConfigurated load

1823 allTchFrAllocatedTimeCellMoy/Max/Cum/Ech value

1824/n tchFrAveragedUsedTchAllocationCellMoy/Max/Cum/EchtchFrAveragedUsedPrimoAllocationCellMoy/Max/Cum/EchtchFrAveragedUsedOverflowAllocationCellMoy/Max/Cum/EchtchFrAveragedUsedWpsCellMoy/Max/Cum/Ech

load

1825 tchFrAveragedAvailableCellMoy/Max/Cum/Ech load


PE/DCL/DD/0125411--9001--125


Counter No. TypeQ3 name

1826 tchFrAveragedUsedCellMoy/Max/Cum/Ech load

1827 tchFrAverageConfiguratedCellMoy/Max/Cum/Ech load

1.3.3.3 PDTCH resources

Counter No. Q3 name Type

1049 attemptedTchFrSeizures raw permanent

1050 successfulTchFrSeizures raw permanent

1057 allTchAllocatedTime value

1609/01609/2

tchFrAllocatedTchAllocationTrZonetchFrAllocatedOverflowAllocationTrZone

raw permanentraw permanent

1611/0

1611/2

tchFrAveragedTchAllocationTrZoneMoy/Max/Cum/EchtchFrAveragedUsedOverflowAllocationTrZone-Moy/Max/Cum/Ech

raw permanent

raw permanent

1613 tchFrResourceFailureTrZone raw permanent

1700 tchFrAveragedAvailableTrZoneMoy/Max/Cum/Ech

raw permanent

1715 attemptedTchFrSeizuresMsDualb raw permanent

1716 successfulTchFrSeizuresMsDualb raw permanent

1744 tchFrAllocatedtchFrAllocatedTrZone


1746 tchFrAveragedUsedMoy/Max/Cum/EchtchFrAveragedUsedTrZoneMoy/Max/Cum/Ech


1812 allocatedCircuitTsMoy/Max/Cum/EchallocatedCircuitTsTrZoneMoy/Max /Cum/Ech


1813 allocatedPacketTsMoy/Max/Cum/EchallocatedPacketTsTrZoneMoy/Max /Cum/Ech


1814 gprsPreemption raw permanent

1.3.4 Interferences




Counter No. Q3 name Type1619/n channelAveragedIdlePerInterfBand0/Max/Moy/Cu

m/EchchannelAveragedIdlePerInterfBand1/Max/Moy/Cum/EchchannelAveragedIdlePerInterfBand2/Max/Moy/Cum/EchchannelAveragedIdlePerInterfBand3/Max/Moy/Cum/EchchannelAveragedIdlePerInterfBand4/Max/Moy/Cum/Ech

value


PE/DCL/DD/0125411--9001--125


1.3.5 Call setup


Counter No. Q3 name Type1191/n channelRequestCause000

channelRequestCause001channelRequestCause010channelRequestCause011channelRequestCause100channelRequestCause101channelRequestCause110channelRequestCause111

totalizer

1192/n immediateAssignmentSuccessCause000immediateAssignmentSuccessCause001immediateAssignmentSuccessCause010immediateAssignmentSuccessCause011immediateAssignmentSuccessCause100immediateAssignmentSuccessCause101immediateAssignmentSuccessCause110immediateAssignmentSuccessCause111

totalizer

1193/n estabIndicSignallingPagingResestabIndicSignallingLocUpdateestabIndicSignallingReEstabestabIndicSignallingImsiDetachestabIndicSignallingMocestabIndicSignallingEmergencyestabIndicSignallingShortMsgestabIndicSignallingSuppService

totalizer

1195 estabIndicSigPhase1 totalizer

1196 estabIndicSigPhase2 totalizer1207 immediateAssignmentMultiband totalizer

1702 channelRequestExtended value1730 pagingResponse totalizer1748 channelRequest totalizer

1749 immediateAssignmentSuccess totalizer1750 estabIndicSignalling totalizer

1.3.6 Dedicated channel assignment


1.3.6.1 Assignment

Counter No. Q3 name Type1049 attemptedTchFrSeizures totalizer



1715 (V12 andV14)

attemptedTchFrSeizuresMsDualb totalizer

1050 successfulTchFrSeizures totalizer1716 (V12 andV14)

successfulTchFrSeizuresMsDualb totalizer

1055 assignFailure totalizer1799 (V12 andV14)

assignToOtherBandOrZone totalizer

1841/0 (V12and V14)

assignRequestSdcchToTchChannel totalizer

1841/1 (V12and V14)

assignRequestOthers totalizer

1842/0 (V12and V14)

assignFailureSdcchToTchChannel totalizer

1841/1 (V12and V14)

assignFailureOthers totalizer

1.3.6.2 Activation

Counter No. Q3 name Type

1044 signallingPhaseDuration value1045 signallingPhaseDurationHigh value1206 speechAlgoFallBack totalizer

1629/0 channelActivateSignallingFullRate totalizer1197/01197/1

channelActivateSpeechFullRatechannelActivateSpeechEnhancedFullRate

totalizer

1705/n channelActivateTchFrDataT16channelActivateTchFrDataT600channelActivateTchFrDataT1200channelActivateTchFrDataT2400channelActivateTchFrDataT4800channelActivateTchFrDataT9600channelActivateTchFrDataT14400

totalizer

1706/n channelActivateTchHrDataT16channelActivateTchHrDataT600channelActivateTchHrDataT1200channelActivateTchHrDataT2400channelActivateTchHrDataT4800

totalizer

1707/n channelActivateTchFrDataNT6000channelActivateTchFrDataNT12000channelActivateTchFrDataNT14500

totalizer

1708 channelActivateTchHrDataNT6000 totalizer1709 channelActTchFrDataT totalizer

1710 channelActTchFrDataNT totalizer1711 channelActivateTchHrDataT totalizer1712 channelActivateTchHrDataNT totalizer


PE/DCL/DD/0125411--9001--125


1.3.7 Directed retry handovers

This counter is collected on the bts object and appears in an observation report onbts level.

Counter No. Q3 name Type1620 directedRetryUnsuccessNoBts totalizer

1.3.8 Handovers

1.3.8.1 Handover requirements


Counter No. Q3 name Type1138/01138/11138/21138/31138/41138/51138/61138/71138/81138/91138/101138/111138/121138/131138/14 (V12, V14)1138/151138/164

hoRequiredTchUplinkStrengthhoRequiredTchDownlinkStrengthhoRequiredTchUplinkQualityhoRequiredTchDownlinkQualityhoRequiredTchDistancehoRequiredTchPowerBudgetQualityhoRequiredTchCapturehoRequiredTchIntraBtsOmhoRequiredTchIntraBtsUplinkhoRequiredTchIntraBtsDownlinkhoRequiredTchDirectedRetryhoRequiredTchTdmaClass0hoRequiredTchTdmaClass1hoRequiredTchInterBtsOmhoRequiredTchTraffichoRequiredTchTieringLargeToSmallPatternhoRequiredTchTieringSmallToLargePattern

totalizer

1139/01139/11139/21139/31139/41139/51139/61139/71139/81139/91139/131139/14 (V12, V14)1139/151139/16

hoRequiredSdcchUplinkStrengthhoRequiredSdcchDownlinkStrengthhoRequiredSdcchUplinkQualityhoRequiredSdcchDownlinkQualityhoRequiredSdcchDistancehoRequiredSdcchPowerBudgethoRequiredSdcchCapturehoRequiredSdcchIntraBtsOmhoRequiredSdcchIntraBtsUplinkhoRequiredSdcchIntraBtsDownlinkhoRequiredSdcchInterBtsOmhoRequiredSdcchTraffichoRequiredSdcchTieringLargeToSmallPatternhoRequiredSdcchTieringSmallToLargePattern

totalizer

1776 hoRequiredTch totalizer



Counter No. TypeQ3 name1777 hoRequiredSdcch totalizer

1165 hoIndicationNotTreatedTchoke totalizer1782 (V12, V14) hoBtsRejected totalizer

1208 hoRequestOutgoingMbandEbandMsDualb totalizer1783 (V12, V14) hoRequestOugoingMbandMbandMsDualb totalizer1784 (V12, V14) hoRequestOugoingEbandEbandMsDualb totalizer

1785 (V12, V14) hoRequestOugoingEbandMbandMsDualb totalizer1789 (V12, V14) hoExecutionOutgoingMbandEbandMsDualb totalizer

1790 (V12, V14) hoExecutionOutgoingMbandMbandMsDualb totalizer1791 (V12, V14) hoExecutionOutgoingEbandEbandMsDualb totalizer1792 (V12, V14) hoExecutionOutgoingEbandMbandMsDualb totalizer

1209 hoSuccessOutgoingMbandEbandMsDualb totalizer1786 (V12, V14) hoSuccessOutgoingMbandMbandMsDualb totalizer

1787 (V12, V14) hoSuccessOutgoingEbandEbandMsDualb totalizer1788 (V12) hoSuccessOutgoingEbandMbandMsDualb totalizer1780/01780/11780/2

hoSuccessOutgoingTchamrFrhoSuccessOutgoingTchamrHrhoSuccessOutgoingTch

totalizer

1781 hoSuccessIncomingTch totalizer

1.3.8.2 Intra–bts handovers


Counter No. Q3 name Type10811154

hoRequestIntraBtshoRequestIntraBtsSdcch

totalizer

1796 (V12) hoRequestIntraBtsMsDualb totalizer10821155

hoExecutionIntraBtshoExecutionIntraBtsSdcch

totalizer

1797 (V12) hoExecutionIntraBtsMsDualb totalizer

10831156

hoSuccessIntraBtshoSuccessIntraBtsSdcch

totalizer

1798 (V12) hoSuccessIntraBtsMsDualb totalizer

11341157

hoUnsuccessReestIntraBtsTchhoUnsuccessReestIntraBtsSdcch

totalizer

1756/n hoFailureIntraBtsTchRadioLackhoFailureIntraBtsTchChannelActivateNackhoFailureIntraBtsTchTchnAckTimerExp

totalizer

1757/n hoFailureIntraBtsSdcchRadioLackhoFailureIntraBtsSdcchChannelActivateNackhoFailureIntraBtsSdcchTchnAckTimerExp

totalizer


PE/DCL/DD/0125411--9001--125


Counter No. TypeQ3 name1802/n hoSuccessTieringTchLargeToSmallPattern

hoSuccessTieringTchSmallToLargePatterntotalizer

1801/n hoFailureTieringTchNorrLargeToSmallPatternhoFailureTieringTchNorrSmallToLargePattern

totalizer

1.3.8.3 Intra–bss handovers



hoExecutionOutgoingIntraBsshoExecutionOutgoingIntraBssSdcch

totalizer

10671142

hoSuccessOutgoingIntraBsshoSuccessOutgoingIntraBssSdcch

totalizer

10691144

hoRequestIncomingIntraBsshoRequestIncomingIntraBssSdcch

totalizer

10711146

hoExecutionIncomingIntraBsshoExecutionIncomingIntraBssSdcch

totalizer

10731148

hoSuccessIncomingIntraBsshoSuccessIncomingIntraBssSdcch

totalizer

10751150

hoRequestOutgoingIntraBsshoRequestOutgoingIntraBssSdcch

totalizer

10771152

hoSuccessOutgoingFirstIntrahoSuccessOutgoingFirstIntraSdcch

totalizer

11351158

hoUnsuccessReestOutgoingIntraBssTchhoUnsuccessReestOutgoingIntraBssSdcch

totalizer

11371160

hoUnsuccessReestIncomingIntraBssTchhoUnsuccessReestIncomingIntraBssSdcch

totalizer

11671168

hoUnsuccessOutgoingIntraBssNAttemptTchhoUnsuccessOutgoingIntraBssNAttemptSdcch

totalizer

1758/01758/11758/21758/31758/4 (V12)

hoFailureIncomingIntraBssTchRadioLackhoFailureIncomingIntraBssTchHoNotAllowedhoFailureIncomingIntraBssTchChannelActivateNackhoFailureIncomingIntraBssTchTchnAckTimerExphoFailureIncomingIntraBssTchIncompatible

totalizer

1759/01759/11759/21759/3

hoFailureIncomingIntraBssSdcchRadioLackhoFailureIncomingIntraBssSdcchHoNotAllowedhoFailureIncomingIntraBssSdcchChannelActivateNackhoFailureIncomingIntraBssSdcchTchnAckTimerExp

totalizer

1762/01762/11762/21762/31762/4 (V12)

hoFailureOutgoingIntraBssTchRadioLackhoFailureOutgoingIntraBssTchHoNotAllowedhoFailureOutgoingIntraBssTchChannelActivateNackhoFailureOutgoingIntraBssTchTchnAckTimerExphoFailureOutgoingIntraBssTchIncompatible

totalizer



Counter No. TypeQ3 name1763/01763/11763/21763/3

hoFailureOutgoingIntraBssSdcchRadioLackhoFailureOutgoingIntraBssSdcchHoNotAllowedhoFailureOutgoingIntraBssSdcchChannelActivateNackhoFailureOutgoingIntraBssSdcchTchnAckTimerExp

totalizer

1768/n hoUnsuccessOutgoingIntraBssTchReturnOldChannelhoUnsuccessOutgoingIntraBssTchT3107TimerExp

1769/n hoUnsuccessOutgoingIntraBssSdcchReturnOldChannelhoUnsuccessOutgoingIntraBssSdcchT3107TimerExp

1772/n hoUnsuccessIncomingIntraBssTchReturnOldChannelhoUnsuccessIncomingIntraBssTchT3103TimerExp

totalizer

1773/n hoUnsuccessIncomingIntraBssSdcchReturnOldChannelhoUnsuccessIncomingIntraBssSdcchT3103TimerExp

totalizer

1793 (V12) hoRequestIncomingIntraBssTchMsDualb totalizer

1794 (V12) hoExecutionIncomingIntraBssTchMsDualb totalizer1795 (V12) hoSuccessIncomingIntraBssTchMsDualb totalizer

1759/01759/11759/21759/3

hoFailureIncomingIntraBssSdcchRadioLackhoFailureIncomingIntraBssSdcchHoNotAllowedhoFailureIncomingIntraBssSdcchChannelActivateNackhoFailureIncomingIntraBssSdcchTchnAckTimerExp

totalizer

1.3.8.4 Inter–bss handovers



hoExecutionOutgoingInterBsshoExecutionOutgoingInterBssSdcch

totalizer

10681143

hoSuccessOutgoingInterBsshoSuccessOutgoingInterBssSdcch

totalizer

10701145

hoRequestIncomingInterBsshoRequestIncomingInterBssSdcch

totalizer

10721147

hoExecutionIncomingInterBsshoExecutionIncomingInterBssSdcch

totalizer

10741149

hoSuccessIncomingInterBsshoSuccessIncomingInterBssSdcch

totalizer

10761151

hoRequestOutgoingInterBsshoRequestOutgoingInterBssSdcch

totalizer

10781153

hoSuccessOutgoingFirstInterhoSuccessOutgoingFirstInterSdcch

totalizer

11361159

hoUnsuccessReestOutgoingInterBssTchhoUnsuccessReestOutgoingInterBssSdcch

totalizer

11691170

hoUnsuccessOutgoingInterBssNAttemptTchhoUnsuccessOutgoingInterBssNAttemptSdcch

totalizer


PE/DCL/DD/0125411--9001--125


Counter No. TypeQ3 name1760/01760/11760/21760/31760/41760/5

hoFailureIncomingInterBssTchRadioLackhoFailureIncomingInterBssTchTerrestLackhoFailureIncomingInterBssTchHoNotAllowedhoFailureIncomingInterBssTchChannelActivateNackhoFailureIncomingInterBssTchTchnAckTimerExphoFailureIncomingInterBssTchCICIncompatible

totalizer

1761/01761/11761/21761/31761/4

hoFailureIncomingInterBssSdcchRadioLackhoFailureIncomingInterBssSdcchTerrestLackhoFailureIncomingInterBssSdcchHoNotAllowedhoFailureIncomingInterBssSdcchChannelActivateNackhoFailureIncomingInterBssSdcchTchnAckTimerExp

totalizer

1764/01764/11764/21764/31764/41764/5 (V12)

hoFailureOutgoingInterBssTchRadioLackhoFailureOutgoingInterBssTchTerrestLackhoFailureOutgoingInterBssTchHoNotAllowedhoFailureOutgoingInterBssTchT7TimerExphoFailureOutgoingInterBssTchOtherCaseshoFailureOutgoingInterBssTchIncompatible

totalizer

1765/01765/11765/21765/31765/4

hoFailureOutgoingInterBssSdcchRadioLackhoFailureOutgoingInterBssSdcchTerrestLackhoFailureOutgoingInterBssSdcchHoNotAllowedhoFailureOutgoingInterBssSdcchT7TimerExphoFailureOutgoingInterBssSdcchOtherCase

totalizer

1770/n hoUnsuccessOutgoingInterCellTchReturnOldChannelhoUnsuccessOutgoingInterCellTchT3107TimerExphoUnsuccessOutgoingInterCellTchOtherCases

totalizer

1771/n hoUnsuccessOutgoingInterCellSdcchReturnOldChannelhoUnsuccessOutgoingInterCellSdcchT3107TimerExphoUnsuccessOutgoingInterCellSdcchOtherCases

totalizer

1774/n hoUnsuccessIncomingInterBssTchTimerExphoUnsuccessIncomingInterBssTchOtherCases

totalizer

1775/n hoUnsuccessIncomingInterBssSdcchTimerExphoUnsuccessIncomingInterBssSdcchOtherCases

totalizer

1.3.8.5 Handovers in neighbor cells

These counters are collected on the adjacentCellHandOver object and appear in anobservation report on adjacentCell level (one occurence per neighbor cell).


hoNcellsExecutionhoNcellsExecutionSdcch

totalizer

1204/n hoNcellsUnsuccessTchChlRhoNcellsUnsuccessTchTimerhoNcellsUnsuccessTchOther

totalizer

1205/n hoNcellsUnsuccessSdcchChlRhoNcellsUnsuccessSdcchTimerhoNcellsUnsuccessSdcchOther

totalizer



Counter No. TypeQ3 name1839/n hoNcellsRequestOutgoingUplinkStrength

hoNcellsRequestOutgoingDownlinkStrengthhoNcellsRequestOutgoingUplinkQualityhoNcellsRequestOutgoingDownlinkQualityhoNcellsRequestOutgoingDistancehoNcellsRequestOutgoingPowerBudgethoNcellsRequestOutgoingDirectedRetryhoNcellsRequestOutgoingInterCellOMhoNcellsRequestOutgoingTraffichoNcellsRequestOutgoingOther

1840/n hoNcellsSuccessOutgoingUplinkStrengthhoNcellsSuccessOutgoingDownlinkStrengthhoNcellsSuccessOutgoingUplinkQualityhoNcellsSuccessOutgoingDownlinkQualityhoNcellsSuccessOutgoingDistancehoNcellsSuccessOutgoingPowerBudgethoNcellsSuccessOutgoingDirectedRetryhoNcellsSuccessOutgoingInterCellOMhoNcellsSuccessOutgoingTraffichoNcellsSuccessOutgoingOther

1.3.9 Radio resource release

1.3.9.1 Release in signaling phase

These counters are collected on the bts object or the bsc object.

Counters collected on the bts object appear in an observation report on bts level.Counters collected on the bsc object appear in an observation report on bsc level.


PE/DCL/DD/0125411--9001--125


Counters on bts level

Counter No. Q3 name Type1161/01161/11161/21161/31161/51161/61161/7

immediateAssignmentRejectTraffMscimmediateAssignmentRejectRadioResimmediateAssignmentRejectChanActNackimmediateAssignmentRejectChanActTimmackimmediateAssignmentRejectOverloadimmediateAssignmentRejectTimingAdvimmediateAssignmentRejectOthers

totalizer

1163/01163/11163/21163/31163/41163/51163/61163/71163/81163/91163/101163/111163/121163/131163/141163/161163/171163/181163/191163/201163/211163/221163/231163/241163/251163/281163/301163/321163/33

signallingReleaseBtsSccpDiscIndsignallingReleaseBtsResetsignallingReleaseBtsResetCircsignallingReleaseBtsSccpDataRefusalsignallingReleaseBtsIncFirstL3signallingReleaseBtsT3101signallingReleaseBtsT3107CircDownsignallingReleaseBtsOmTsRemovalsignallingReleaseBtsTsRemovalEqptFailsignallingReleaseBtsOmCicRemovalsignallingReleaseBtsCicRemovalEqptFailsignallingReleaseBtsOmRadioChanBlocsignallingReleaseBtsCallClearingsignallingReleaseBtsCnxFailRadioIntFailsignallingReleaseBtsCnxFailRadioLinkFailsignallingReleaseBtsReleaseIndsignallingReleaseBtsErrorIndT200signallingReleaseBtsErrorIndDmsignallingReleaseBtsErrorIndSeqsignallingReleaseBtsClearCommandsignallingReleaseBtsRfResIndsignallingReleaseBtsSwitchOversignallingReleaseBtsTmodMssignallingReleaseBtsT3103signallingReleaseBtsT8signallingReleaseBtsOtherssignallingReleaseBtsT11signallingReleaseBtsCnxFailRemTransFailsignallingReleaseCellTbcEdge

totalizer

1751 immediateAssignmentReject totalizer1753 signallingReleaseBts totalizer

1778 signallingAbnormalReleaseCell totalizer1804 deleteIndication totalizer



Counters on bsc level

Counter No. Q3 name Type1162/01162/11162/31162/261162/271162/28

signallingreleaseNoBtsSccpDiscIndsignallingreleaseNoBtsResetsignallingreleaseNoBtsSccpDataRefusalsignallingreleaseNoBtsTsccRelsignallingreleaseNoBtsBadDataIndsignallingreleaseNoBtsSccpOthers

1752 signallingReleaseNoBts totalizer


PE/DCL/DD/0125411--9001--125


1.3.9.2 Release in traffic phase


Counter No. Q3 name Type1164/01164/11164/21164/31164/61164/71164/8116491164/101164/111164/121164/131164/141164/161164171164/181164/191164/201164/211164/231164/241164/251164/281164/311164/321164/33

trafficReleaseSccpDiscIndtrafficReleaseResettrafficReleaseResetCirctrafficReleaseBtsSccpDataRefusaltrafficReleaseT3107CircDowntrafficReleaseOmTsRemovaltrafficReleaseTsRemovalEqptFailtrafficReleaseOmCicRemovaltrafficReleaseCicRemovalEqptFailtrafficReleaseOmRadioChanBloctrafficReleaseCallClearingtrafficReleaseCnxFailRadioIntFailtrafficReleaseCnxFailRadioLinkFailtrafficReleaseReleaseIndtrafficReleaseErrorIndT200trafficReleaseErrorIndDmtrafficReleaseErrorIndSeqtrafficReleaseClearCommandtrafficReleaseRfResIndtrafficReleaseTmodMstrafficReleaseT3103trafficReleaseT8trafficReleaseOtherstrafficReleaseSysInfoFailtrafficReleaseCnxFailRemTransFailtrafficReleaseTbcEdge

totalizer

1754 trafficRelease totalizer

1779 trafficAbnormalRelease totalizer

1.3.10 SMS service

This counter is collected on the bts object and appears in an observation report onbts level.

Counter No. Q3 name Type1621 sapi3SessionEstablishment totalizer



1.3.11 Layer 1 management



downlinkPowerCtrlMaxTchdownlinkPowerCtrlMaxSdcch

value

11991602

uplinkPowerCtrlMaxTchuplinkPowerCtrlMaxSdcch

value

16001603

connectionDurationTchconnectionDurationSdcch

value

1622 msLostMeasurements totalizer

16231625

rxLevDownLinkrxQualDownLink

totalizer

16241626

rxLevUpLinkrxQualUpLink

totalizer

18051806

msPowerIncControlmsPowerDecControl

totalizer

18071808

bsPowerIncControlbsPowerDecControl

totalizer

1809/01809/1or1809/01809/1

timingAdvanceAveragetimingAdvanceMaximum

timingAdvanceAverageTrZonetimingAdvanceMaximumTrZone

totalizer

1816 pathBalance value2025 downgradedL1mModeOnClassmark totalizer

1.3.12 A interface

These counters are collected on the bsc object and appear in an observation reporton bsc level.


aInputMessageaOutputMessage

totalizer

1109 aMessageErrors totalizer1104/01104/1

sccpAllocatedsccpAllocatedLcs

totalizer

1105 sccpAveragedUsed load1106/01106/1 (V12,14)1106/2 (V12,14)1106/3 (V12,14)

sccpRessourceFailuresccpRessourceFailureBscRefusalsccpRessourceFailureLcssccpRessourceFailureBscRefusalLcs

totalizer

15001501

aTransparentUpaTransparentDown

totalizer


PE/DCL/DD/0125411--9001--125


15021503

aNonTransparentUpaNonTransparentDown

totalizer

1094 tcAllocated totalizer1095 tcAveragedUsed load

1172/0 (V12,14)1172/1 (V12,14)

dataNtRateFbTcbResLackdataNtRateFbTcbConfNotAllowed

totalizer

1.3.13 Abis interface

These counters are collected on the lapdLink object and appear in an observationreport on bsc level (one occurrence per LAPD link).

Counter No. Q3 name Type1084/01084/31084/4

abisLevel1ErrorsBadFrameabisLevel1ErrorsCrcErrorabisLevel1ErrorsLostAlign

totalizer

1717 (V12, V14) abisTrauFrameDIReceived totalizer1718 (V12, V14) abisTrauFrameCorrected totalizer

1719 (V12, V14) abisTrauFrameMuted totalizer1720 (V12, V14) radioFrameUIReceived totalizer1721 (V12, V14) ECU_Activation totalizer

1.3.14 BSS/OMC--R link

These counters are collected on the bsc object and appear in an observation reporton bsc level (one occurrence per external X.25 link).


omcOutputIFrameomcOutputRepeatedIFrameomcOutputRnrFrame

totalizer

130113031305

omcInputIFrameomcInputRepeatedIFrameomcInputRnrFrame

totalizer

1115 omcLinkSwitchOver totalizer

1.3.15 PCM links

These counters are collected on the pcmCircuit object and appears in an observationreport on bsc level (one occurrence per external PCM).

Counter No. Q3 name Type1114 pcmUnavailability value1755/n pcmFaultExternal

pcmFaultInternalpcmFaultDDTIBoardpcmFaultOutOfService

totalizer



1.3.16 BSC equipment

These counters are collected on the bsc object and appear in an observation reporton bsc level.

Counter No. Q3 name Type1121 chainStandbyUpdate totalizer

1122 chainStandbyResponse totalizer1400 prLoadCpue<x>

prLoadCpumprLoadSicd<x>

load

1506/n (V12,V15)

aintOverloadRejectedOpPageReqaintOverloadRejectedOpIncomingExtHoReq

totalizer

1803/n (V12,V15)

cgOverloadRejectedOpPageReqCg<x>cgOverloadRejectedOpChannelReqCg<x>cgOverloadRejectedOpEstablishIndCg<x>cgOverloadRejectedOpHoReqCg<x>cgOverloadRejectedOpPageReqBtsCg<x>cgOverloadRejectedOpSmsCbCg<x>

totalizer

1834 (V12,V15)

lapdOverloadRejectedOpSicd<x> totalizer

1835 (V12,V15)

cardSynthLoadCpumcardSynthLoadCpue<x>cardSynthLoadSicd<x>

value

3000/0 (V13)

3000/1 (V13)

prLoadCne3OmuSbcMoyprLoadCne3OmuSbcMaxprLoadCne3OmuSbcCumprLoadCne3OmuSbcEch

prLoadCne3OmuTmMoyprLoadCne3OmuTmMaxprLoadCne3OmuTmCumprLoadCne3OmuTmEch

Load

3001/0 (V13)

3001/1 (V13)

3001/2 (V13)

prLoadCne3TmuSbcMoyprLoadCne3TmuSbcMaxprLoadCne3TmuSbcCumprLoadCne3TmuSbcEch

prLoadCne3TmuTmMoyprLoadCne3TmuTmMaxprLoadCne3TmuTmCumprLoadCne3TmuTmEch

prLoadCne3TmuPmcMoyprLoadCne3TmuPmcMaxprLoadCne3TmuPmcCumprLoadCne3TmuPmcEch

Load


PE/DCL/DD/0125411--9001--125


Counter No. TypeQ3 name3004/0 (V14)

3004/1 (V14)

e3PrMemCnOmuSbcMemMoye3PrMemCnOmuSbcMemMaxe3PrMemCnOmuSbcMemCume3PrMemCnOmuSbcMemEch

e3PrMemCnOmuSbcSwapMoye3PrMemCnOmuSbcSwapMaxe3PrMemCnOmuSbcSwapCume3PrMemCnOmuSbcSwapEch

Value

3005/0 (V13)

3005/1 (V13)

3005/2 (V13)

e3PrMemCnTmuSbcMoye3PrMemCnTmuSbcMaxe3PrMemCnTmuSbcCume3PrMemCnTmuSbcEch

e3PrMemCnTmuTmMoye3PrMemCnTmuTmMaxe3PrMemCnTmuTmCume3PrMemCnTmuTmEch

e3PrMemCnTmuPcmMoye3PrMemCnTmuPcmMaxe3PrMemCnTmuPcmCume3PrMemCnTmuPcmEch

Value

3008 /0 (V14)

3008/1 (V14)

3008/2 (V14)

3008/3 (V14)

e3PrDiskCnOmuLdWMoye3PrDiskCnOmuLdWMaxe3PrDiskCnOmuLdWCume3PrDiskCnOmuLdWEch

e3PrDiskCnOmuLdRMoye3PrDiskCnOmuLdRMaxe3PrDiskCnOmuLdRCume3PrDiskCnOmuLdREch

e3PrDiskCnOmuMdWMoye3PrDiskCnOmuMdWMaxe3PrDiskCnOmuMdWCume3PrDiskCnOmuMdWEch

e3PrDiskCnOmuMdRMoye3PrDiskCnOmuMdRMaxe3PrDiskCnOmuMdRCume3PrDiskCnOmuMdREch

Value

1.3.17 GPRS

Counter No. Q3 name Type1086 gprsRachRejectedSicd<x> totalizer1087 gprsImmAssRejectedSicd<x> totalizer1088 gprsPagingRejectedSicd<x> totalizer



1812 allocatedCircuitTsMoy/Max/Cum/EchallocatedCircuitTsTrZoneMoy/Max/Cum/Ech

load

1813 allocatedPacketTsMoy/Max/Cum/EchallocatedPacketTsTrZoneMoy/Max/Cum/Ech

totalizer

1814 gprsPreemption totalizer

1815 gprsPreemptionNack totalizer

1821 allocatedCircuitTsMoy/Max/Cum/Ech load

1822/n allocatedPacketTsCellMoy/Max/Cum/EchtotalNumberOfPacketTsCellMoy/Max/Cum/EchtotalNumberOfPacketTsUsedForCircuitCellMoy/Max/Cum/Ech

load


PE/DCL/DD/0125411--9001--125


1.3.18 ASCI (GSM--R V12, V15)

Counter No. Q3 name Type1722 /01722/1

asciCallInitiationVbsasciCallInitiationVgcs

totalizer

1800/01800/1

asciTalkerHandoverVbsasciTalkerHandoverVgcs

totalizer

1723 asciInbandPaging totalizer

1724 asciInbandNotification totalizer1725 asciPreemptionPerformed totalizer1504 vgcsAccessGrant totalizer

1505 vgcsMscReject totalizer1804 deleteIndication totalizer

1805 msPowerIncControl totalizer1806 msPowerDecControl totalizer1807 bsPowerInControl totalizer

1808 bsPowerDecControl totalizer1809/01809/1

timingAdvanceMoytimingAdvanceMax

totalizer

1810 tchFrAverageConfigurated load1811 sdcchAverageConfigurated totalizer1839/01839/11839/21839/31839/41839/51839/61839/71839/81839/9

hoNCellsRequestOutgoingUplinkStrengthhoNCellsRequestOutgoingDownlinkStrengthhoNCellsRequestOutgoingUplinkQualityhoNCellsRequestOutgoingDownlinkQualityhoNCellsRequestOutgoingDistancehoNCellsRequestOutgoingPowerBudgetQualityhoNCellsRequestOutgoingDirectedRetryhoNCellsRequestOutgoingInterBtsOmhoNCellsRequestOutgoingTraffichoNCellsRequestOutgoingOthers

totalizer

184001840/11840/21840/31840/41840/51840/61840/71840/81840/9

hoNCellsSuccessOutgoingUplinkStrengthhoNCellsSuccessOutgoingDownlinkStrengthhoNCellsSuccessOutgoingUplinkQualityhoNCellsSuccessOutgoingDownlinkQualityhoNCellsSuccessOutgoingDistancehoNCellsSuccessOutgoingPowerBudgetQualityhoNCellsSuccessOutgoingDirectedRetryhoNCellsSuccessOutgoingInterBtsOmhoNCellsSuccessOutgoingTraffichoNCellsSuccessOutgoingOthers

totalizer

2035 msClassSensitivityToggle totalizer

2036 attemptedTchFrSeizures8W totalizer2037 successfulTchFrSeizures8W totalizer20382048

hoSuccessOutgoingIntraBss8WhoSuccessOutgoingIntraBssSdcch8W

totalizer



20392049

hoSuccessOutgoingInterBss8WhoSuccessOutgoingInterBssSdcch8W

totalizer

2040 hoRequestIncomingIntraBss8W totalizer2041 hoRequestIncomingInterBss8W totalizer

2042 hoSuccessIncomingIntraBss8W totalizer2043 hoSuccessIncomingInterBss8W totalizer20442050

hoRequestOutgoingIntraBss8WhoRequestOutgoingIntraBssSdcch8W

totalizer

20452051

hoSuccessOutgoingInterBssSdcch8WhoRequestOutgoingInterBss8W

totalizer

2046 hoRequestIntraBts8W totalizer

2047 hoSuccessIntraBts8W totalizer2052/02052/1

signallingReleaseBts8wsignallingReleaseBtsT3107CircDown8W

totalizer

2053 trafficRelease8W totalizer

2054 estabIndicSignallingEmergency8W totalizer2055 estabIndicSigPhase28W totalizer

2056/02056/1

hoUnsuccessOutgoingIntraCellTchReturnOldChannel8WhoUnsuccessOutgoingIntraCellTchT3103TimerExp8W

totalizer

2057/02057/1

hoUnsuccessOutgoingInterCellTchReturnOldChannel8WhoUnsuccessOutgoingInterCellTchT3103TimerExp8W

totalizer

2058 signallingAbnormalReleaseCell8W totalizer

2059 trafficAbnormalRelease8W totalizer2060 uplinkFreeUplinkReply totalizer

2061 listenerDetectionExpiry totalizer

1.3.19 Counter configuration

Paragraph 1.5 gives the V15 default configuration of the permanent generalobservation counters in the different observation types OGS, OFS, ORT, andODIAG.


PE/DCL/DD/0125411--9001--125


1.4 Temporary observation counters

Temporary observation counters are BSC 2G only.

1.4.1 SS7 links

These counters are collected on the signallingLink object (one occurrence per SS7link defined in a given BSS).

Counter No. Q3 name Type5100/05101/0

ss7OutputMsuss7InputMsu

totalizer

5102/n ss7Level2ErrorNegAckRecss7Level2ErrorNegAckTransss7Level2ErrorMsuCongestss7Level2ErrorSuErr

totalizer

5103/n ss7Level3ErrorDelayss7Level3ErrorHighErrRatess7Level3ErrorDistOutServ

totalizer



1.4.2 Abis interface

These counters are collected on the bts object and the dependent transceiver objects.

Counters on transceiver level

Counter No. Q3 name Type5600/05601/0

abisOutputUiFrameabisInputUiFrame

totalizer

5602/05603/0

abisOutputIFrameabisInputIFrame

totalizer

5604/05605/0

abisOutputUiByteabisInputUiByte

totalizer

5606/05607/0

abisOutputIByteabisInputIByte

totalizer

Counters on bts level

Counter No. Q3 name Type5608/n abisLevel2ErrorRxSup1

abisLevel2ErrorRxDm1abisLevel2ErrorRxUa1abisLevel2ErrorRxUa0abisLevel2ErrorRxDm0abisLevel2ErrorRxSabmeabisLevel2ErrorTxNSabmeabisLevel2ErrorTxNDiscabisLevel2ErrorReqOutStateabisLevel2ErrorBadRxNrabisLevel2ErrorRxFrmrabisLevel2ErrorRxNoImplabisLevel2ErrorBadLg

totalizer

5609 abisUnavailabilityTime value

5610 abisCongestionTime value


PE/DCL/DD/0125411--9001--125


1.5 BSS Permanent observation counters configuration

The permanent general observations can be configured in the four followingobservation types:

the real time permanent observation (ORT)

This observation enables the detection in real time of incidents through thenetwork 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 beconfigured to collect observations 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 verificationand the control of the network (after reorganization). This observation reportscounters that are associated to specific cells of thenetwork. BSCcountersmaybeassociated to this observation

1.5.1 Raw counters configuration (all BSC)

The following table gives the V15.1R default configuration of the counters in thedifferent 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 specifiedobservation 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 thisobservation type (except ORT).

counternumber

Q3 counter name ORT ODIAG OFS OGS

1026/0 rachBusyCount -- Y Y --

1026/0 rachBusyCountTs2 -- Y Y --



1027/0 rachAccessCount -- Y Y --

1027/0 rachAccessCountTs2 -- Y Y --




counternumber

OGSOFSODIAGORTQ3 counter name


1028/0 pchNoWait -- Y Y --

1028/0 pchNoWaitTs2 -- Y Y --



1029/0 pchOneWait -- Y Y --

1029/0 pchOneWaitTs2 -- Y Y --



1030/0 pchTwoWait -- Y Y --

1030/0 pchTwoWaitTs2 -- Y Y --



1031/0 pchMoreWait -- Y Y --

1031/0 pchMoreWaitTs2 -- Y Y --



1033/0 rachNonDecodedAvLevel[Cum,Ech,Moy,Max] -- Y Y --

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


PE/DCL/DD/0125411--9001--125


counternumber


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

1070/1 hoRequestIncomingInterBssTchCtm -- 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 --

1082/0 hoExecutionIntraBts -- Y Y --

1083/0 hoSuccessIntraBts -- Y Y --

1084/0 abisLevel1ErrorsBadFrame<xx> N N Y N

1084/3 abisLevel1ErrorsCrcError<xx> N N Y N

1084/4 abisLevel1ErrorsLostAlign<xx> N N Y N

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



counternumber


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

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


PE/DCL/DD/0125411--9001--125


counternumber


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

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



counternumber


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

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


PE/DCL/DD/0125411--9001--125


counternumber


1164/17 trafficReleaseErrorIndT200 -- Y Y --

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 channelRequestCause000 -- Y Y --








1192/0 immediateAssignmentSuccessCause000 -- Y Y --




counternumber








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

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

1206/2 speechAlgoFallBackCtm -- Y Y --

1207/0 immediateAssignmentMultiband -- Y Y --


PE/DCL/DD/0125411--9001--125


counternumber


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

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 prLoadSicd<x>[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 --

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

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



counternumber


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

1610/0 tchHrAllocatedTchAllocationTrZone -- -- Y --

1610/1 tchHrAllocatedPrimoAllocation -- -- Y --

1610/1 tchHrAllocatedPrimoAllocationTrZone -- -- Y --

1610/1 tchHrAllocatedWps -- Y Y --

1610/1 tchHrAllocatedWpsTrZone -- Y Y --

1610/2 tchHrAllocatedOverflowAllocation -- -- Y --

1610/2 tchHrAllocatedOverflowAllocationTrZone -- -- Y --

1611/0 tchFrAveragedUsedTchAllocation[Moy,Max,Cum,Ech] -- Y Y --

1611/0 tchFrAveragedUsedTchAllocationTrZone[Moy,Max,Cum,Ech] -- Y Y --

1611/1 tchFrAveragedUsedPrimoAllocation[Moy,Max,Cum,Ech] -- Y Y --

1611/1 tchFrAveragedUsedPrimoAllocationTrZone[Moy,Max,Cum,Ech] -- Y Y --

1611/2 tchFrAveragedUsedOverflowAllocation[Moy,Max,Cum,Ech] -- Y Y --

1611/2 tchFrAveragedUsedOverflowAllocationTr-Zone[Moy,Max,Cum,Ech]

-- Y Y --


PE/DCL/DD/0125411--9001--125


counternumber


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 tchHrAveragedUsedTchAllocationTrZone[Moy,Max,Cum,Ech] -- -- Y --

1612/1 tchHrAveragedUsedPrimoAllocation[Moy,Max,Cum,Ech] -- -- Y --

1612/1 tchHrAveragedUsedPrimoAllocationTrZone[Moy,Max,Cum,Ech] -- -- Y --

1612/1 tchHrAveragedUsedWps[Moy,Max,Cum,Ech] -- -- Y --

1612/1 tchHrAveragedUsedWpsTrZone[Moy,Max,Cum,Ech] -- -- Y --

1612/2 tchHrAveragedUsedOverflowAllocation[Moy,Max,Cum,Ech] -- -- Y --

1612/2 tchHrAveragedUsedOverflowAllocationTr-Zone[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 tchAveragedQueueLengthHighPriority[Moy,Max,Cum,Ech] -- Y Y --

1616/1 tchAveragedQueueLengthOtherPriority[Moy,Max,Cum,Ech] -- Y Y --

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/<x> channelAveragedIdlePerInterfBand<x>[Cum,Ech,Moy,Max] -- Y Y --

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



counternumber


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







1707/0 channelActivateTchFrDataNT6000 -- Y Y --



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

1726/0 dataNtRateFbTchResLack -- Y Y --

1726/1 dataNtRateFbTchConfNotAllowed -- Y Y --

1730/0 pagingResponse Y -- -- --

1746/0 tchFrAveragedUsed[Moy,Max,Cum,Ech] Y -- -- --

1746/0 tchFrAveragedUsedTrZone[Moy,Max,Cum,Ech] Y -- -- --

1750/0 estabIndicSignalling Y -- -- --

1755/0 pcmFaultExternal -- Y -- --

1755/1 pcmFaultInternal -- Y -- --

1755/2 pcmFaultDDTIBoard -- Y -- --

1755/3 pcmFaultOutOfService -- Y -- --

1756/0 hoFailureIntraBtsTchRadioLack -- Y -- --

1756/1 hoFailureIntraBtsTchChannelActivateNack -- Y -- --


PE/DCL/DD/0125411--9001--125


counternumber


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

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



counternumber


1764/2 hoFailureOutgoingInterBssTchHoNotAllowed -- Y -- --

1764/3 hoFailureOutgoingInterBssTchT7TimerExp -- Y -- --

1764/4 hoFailureOutgoingInterBssTchOtherCases -- Y -- --

1764/5 hoFailureOutgoingInterBssTchIncompatible -- Y -- --

1765/0 hoFailureOutgoingInterBssSdcchRadioLack -- Y -- --

1765/1 hoFailureOutgoingInterBssSdcchTerrestLack -- Y -- --

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

1778/0 signallingAbnormalReleaseCell -- Y Y --

1779/0 trafficAbnormalRelease -- Y Y --

1780/0 hoSuccessOutgoingTch Y -- Y --

1780/1 amrFrHoSuccessOutgoingTch -- -- Y --

1780/2 amrHrHoSuccessOutgoingTch -- -- Y --

1781/0 hoSuccessIncomingTch Y -- -- --

1782/0 hoBtsRejected -- Y Y --


PE/DCL/DD/0125411--9001--125


counternumber


1783/0 hoRequestOutgoingMbandMbandMsDualb -- Y Y --

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

1801/0 hoFailureTieringTchNorrLargeToSmallPattern -- Y Y --

1801/1 hoFailureTieringTchNorrSmallToLargePattern -- Y Y --

1802/0 hoSuccessTieringTchLargeToSmallPattern -- Y Y --

1802/1 hoSuccessTieringTchSmallToLargePattern -- Y Y --

1803/0 cgOverloadRejectedOpPageReqCg<x> -- Y Y --

1803/1 cgOverloadRejectedOpChannelReqCg<x> -- Y Y --

1803/2 cgOverloadRejectedOpEstablishIndCg<x> -- Y Y --

1803/3 cgOverloadRejectedOpHoReqCg<x> -- Y Y --

1803/4 cgOverloadRejectedOpPageReqBtsCg<x> -- Y Y --

1803/5 cgOverloadRejectedOpSmsCbCg<x> -- 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 --



counternumber


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

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 totalNumberOfPacketTsUsedForCircuit[Moy,Max,Cum,Ech] -- Y Y --

1813/2 totalNumberOfPacketTsUsedForCircuit-TrZone[Moy,Max,Cum,Ech]

-- 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 totalNumberOfPacketTsUsedForCircuitCell[Moy,Max,Cum,Ech] -- Y Y --

1823/0 allTchFrAllocatedTimeCell[Cum,Ech,Moy,Max] -- Y Y --

1824/0 tchFrAveragedUsedTchAllocationCell[Moy,Max,Cum,Ech] -- Y Y --

1824/1 tchFrAveragedUsedPrimoAllocationCell[Moy,Max,Cum,Ech] -- Y Y --

1824/2 tchFrAveragedUsedOverflowAllocationCell[Moy,Max,Cum,Ech] -- 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 --

1834/0 lapdOverloadRejectedOpSicd<x> N N Y N

1835/0 cardSynthLoadCpue<x>[Moy,Max,Cum,Ech] N N Y N

1835/0 cardSynthLoadCpum[Moy,Max,Cum,Ech] N N Y N

1835/0 cardSynthLoadSicd<x>[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


PE/DCL/DD/0125411--9001--125


counternumber


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

1841/2 assignRequestCtm -- Y Y --

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 amrFrTchConnectionDurationTrZone[Cum,Ech,Moy,Max] -- -- Y --

1902/1 amrHrTchConnectionDuration[Cum,Ech,Moy,Max] -- -- Y --

1902/1 amrHrTchConnectionDurationTrZone[Cum,Ech,Moy,Max] -- -- Y --

1903/0 amrFrTchSuccessfullyAssigned -- -- Y --

1903/1 amrHrTchSuccessfullyAssigned -- -- Y --

1904/0 amrFrTchAssignFailure -- -- Y --

1904/1 amrHrTchAssignFailure -- -- Y --

1905/0 CIUplinkFr -- -- Y --



counternumber


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

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


PE/DCL/DD/0125411--9001--125


counternumber


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

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



counternumber


1959/2 hoNCellsUnsuccessTchAmrFrClearCommand -- -- Y --

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

1978/0 amrHrDownlinkCodec475TrZone -- -- -- Y




PE/DCL/DD/0125411--9001--125


counternumber




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





1983/0 amrUplinkNoDataFrames -- -- -- Y

1983/1 amrDownlinkNoDataFrames -- -- -- Y

1984/0 incAmrFrUpModif -- -- -- Y

1984/0 incAmrFrUpModifTrZone -- -- -- Y

1984/1 decAmrFrUpModif -- -- -- Y



counternumber


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

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


PE/DCL/DD/0125411--9001--125


counternumber


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

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

3009/0 e3PcmG826Es[Cum,Ech,Moy,Max] -- Y Y --

3009/1 e3PcmG826Ses[Cum,Ech,Moy,Max] -- Y Y --

3009/2 e3PcmG826Bbe[Cum,Ech,Moy,Max] -- Y Y --

3009/3 e3PcmG826Uas[Cum,Ech,Moy,Max] -- Y Y --

3010/0 e3PcmEventsFas N Y N N

3010/1 e3PcmEventsCrc N Y N N

3010/2 e3PcmEventsEbit N Y N N

3010/3 e3PcmEventsBpv N Y N N

3010/4 e3PcmEventsSlip N Y N N

3011/0 e3PcmAlarmsLos N Y N N

3011/1 e3PcmAlarmsAis N Y N N

3011/2 e3PcmAlarmsLfa N Y N N



counternumber


3011/3 e3PcmAlarmsCrc N Y N N

3011/4 e3PcmAlarmsFe N Y N N

3011/5 e3PcmAlarmsRai N Y N N

3012/0 e3AbisRslLevel2UseIfr N Y N N

3012/1 e3AbisRslLevel2UseIft N Y N N

3012/10 e3AbisRslLevel2UseSft N Y N N

3012/2 e3AbisRslLevel2UseUifr N Y N N

3012/3 e3AbisRslLevel2UseUift N Y N N

3012/4 e3AbisRslLevel2UseIbr N Y N N

3012/5 e3AbisRslLevel2UseIbt N Y N N

3012/6 e3AbisRslLevel2UseUibr N Y N N

3012/7 e3AbisRslLevel2UseUibt N Y N N

3012/8 e3AbisRslLevel2UseIfrt N Y N N

3012/9 e3AbisRslLevel2UseSfr N Y N N

3013/0 e3AbisRslLevel2ErrorsMdlErrorA N Y N N

3013/1 e3AbisRslLevel2ErrorsMdlErrorB N Y N N

3013/10 e3AbisRslLevel2ErrorsMdlErrorK N Y N N

3013/11 e3AbisRslLevel2ErrorsMdlErrorL N Y N N

3013/12 e3AbisRslLevel2ErrorsMdlErrorN N Y N N

3013/2 e3AbisRslLevel2ErrorsMdlErrorC N Y N N

3013/3 e3AbisRslLevel2ErrorsMdlErrorD N Y N N

3013/4 e3AbisRslLevel2ErrorsMdlErrorE N Y N N

3013/5 e3AbisRslLevel2ErrorsMdlErrorF N Y N N

3013/6 e3AbisRslLevel2ErrorsMdlErrorG N Y N N

3013/7 e3AbisRslLevel2ErrorsMdlErrorH N Y N N

3013/8 e3AbisRslLevel2ErrorsMdlErrorI N Y N N

3013/9 e3AbisRslLevel2ErrorsMdlErrorJ N Y N N

3014/0 e3AbisRslLevel2UnavaibilityTime[Cum,Ech,Moy,Max] N Y N N

3015/0 e3AbisRslLevel2CongestionTime[Cum,Ech,Moy,Max] N Y N N

3016/0 e3Ss7SlUseMsuFramesRcv N Y N N

3016/1 e3Ss7SlUseMsuFramesTrs N Y N N

3016/2 e3Ss7SlUseSifSioBytesRcv N Y N N

3016/2 e3Ss7SlUseSifSioBytesTrs N Y N N

3017/0 e3Ss7SlAvaibilityDurLnkInIsState[Cum,Ech,Moy,Max] N Y N N

3017/1 e3Ss7SlAvaibilityDurSlUa[Cum,Ech,Moy,Max] N Y N N


PE/DCL/DD/0125411--9001--125


counternumber


3018/0 e3Ss7Level2ErrorsSlErrorA N Y N N

3018/1 e3Ss7Level2ErrorsSlErrorB N Y N N

3018/2 e3Ss7Level2ErrorsSlErrorC N Y N N

3018/3 e3Ss7Level2ErrorsSlErrorD N Y N N

3018/4 e3Ss7Level2ErrorsSlErrorE N Y N N

3018/5 e3Ss7Level2ErrorsSlErrorF N Y N N

3018/6 e3Ss7Level2ErrorsSlErrorG N Y N N

3019/0 e3Ss7Level3Errors N Y N N

3020/0 e3ChannelIdleLevel[Cum,Ech,Moy,Max] N Y N N

3100/0 e3AbisAccLevel1ErrorsCh1PcmNb -- Y -- --

3100/1 e3AbisAccLevel1ErrorsCh1TsNb -- Y -- --

3100/2 e3AbisAccLevel1ErrorsCh1Nefr -- Y -- --

3100/3 e3AbisAccLevel1ErrorsCh1Ncrce -- Y -- --

3100/4 e3AbisAccLevel1ErrorsCh1Nlfa -- Y -- --
























counternumber






1.5.2 Correspondence between BSC2G and BSC e3 counters

BSC e3

Counternumber

Counter name BSC 2G

Counternumber

Counter name

3000/0 prLoadCne3OmuSbcMoyMax/Cum/Ech 1400 prLoadCpumMoy/Max/Cum/EchprLoadCpueMoy/Max/Cum/EchprLoadCpue1Moy/Max/Cum/EchprLoadCpue2Moy/Max/Cum/EchprLoadSicdMoy/Max/Cum/Ech

3001/0

3001/2

prLoadCne3TmuSbcMoyMax/Cum/Ech

prLoadCne3TmuPmcMoy/Max/Cum/Ech

1400 prLoadCpumMoy/Max/Cum/Ech-prLoadCpueMoy/Max/Cum/Ech-prLoadCpue1Moy/Max/Cum/Ech-prLoadCpue2Moy/Max/Cum/Ech-prLoadSicdMoy/Max/Cum/Ech

3004/0

3004/1

e3PrMemCnOmuSbcMemMoy/Max/Cum/Eche3PrMemCnOmuSbcSwapMoy/Max/Cum/Ech

3005/03005/2

e3PrMemCnTmuSbcMoy/Max/Cum/Eche3PrMemCnTmuPmcMoy/Max/Cum/Ech

3008 /03008/13008/23008/3

e3PrDiskCnOmuLdWMoy/Max/Cum/Eche3PrDiskCnOmuLdRMoy/Max/Cum/Eche3PrDiskCnOmuMdWMoy/Max/Cum/Eche3PrDiskCnOmuMdRMoy/Max/Cum/Ech


PE/DCL/DD/0125411--9001--125


1.5.3 Synthetic counters configuration

1.5.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 requestedHandoverForDualBandMSToSecondVersusMainBand

X

8105 immAssignDualBandMSRate X

8500 hoOutTchMaxFailRate X

8501 hoOutSdcchMaxFailRate X

8502 hoOutTchRequestMaxRatio X

8503 hoOutSdcchRequestMaxRatio X



Counter number OGSOFSCounter name

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


PE/DCL/DD/0125411--9001--125


Counter number OGSOFSCounter name

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



1.5.3.2 OFS &OGS synthetic counters proposal

Counter number Counter name OFS OGS

8110 hoIntraBtsFailRateTchTieringLargeToSmallPattern X

8111 hoIntraBtsFailRateTchTieringSmallToLargePattern X

8629 pcmErrCorrEfficiency X

8757 tdmaClassTchResourceFailureRatio X


PE/DCL/DD/0125411--9001--125


1.6 Raw Permanent PCUSN Observation Counters

1.6.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 tothe OMC--R Data Server (SDO).

The observed object classes found in the PCUSN observation records storing thePCUSN 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 theBSS 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:



network

bsc

pcmCircuit btsSiteManager

bts

transceiveradjacentCellHandover

ccchtransceiverZone

pcusn

logicalProcessor framer

pModule

pBlock

Legend: Classes that are already observed by the BSS observation.

Classes that produce observation counters for the PCUSN observation.

Figure 1--2 Observation Classes


PE/DCL/DD/0125411--9001--125


1.6.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 PCUSNOAMPlug--in. ORT counters are cumulative and return to zero when the SPM isreset.

The following table shows a list of the PCUSN OFS counters. The column on theleft shows the counter number. The next two columns show the class and name ofthese counters as they appear in the CAS Interface. The final two columns show theclass and name of these counters as they appear in SDO output. In some cases, theclass and name of these types of counters can differ.

Name (CDL Component, CDL Attribute)

Counter name

Name (Id/SubId, Type,Class)

CDLComp.

CDL Attribute Id/SubId Type Class SDO name Createdin

release

GPRS/

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 / E

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



CDLComp.

GPRS/

EDGE

Createdin

release

SDO nameClassTypeId/SubIdCDL Attribute

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

V12.4D G

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


PE/DCL/DD/0125411--9001--125


CDLComp.

GPRS/

EDGE

Createdin

release


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

V14.2/3 G / E

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

V14.2/3 G / E

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



CDLComp.

GPRS/

EDGE

Createdin

release


Lp memoryUsageAvgMax 15068/1 MAX LP memoryUsageAvgMaxNormal-Ram

V12.4C G / E

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


PE/DCL/DD/0125411--9001--125


CDLComp.

GPRS/

EDGE

Createdin

release


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






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

V15.0 G / E

CgiCell pcuDynAgprsJokerCumNbTimeslot 15118/0 AVG CELL pcuDynAgprsJokerAvgNbTimes-lot

V15.0 G / E

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



CDLComp.

GPRS/

EDGE

Createdin

release




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

15142/0 CUM TDMA idem CDL Attribute V15.0 E













Tdma pcuEdgeLADnTargetedTransmit-tedMcs2











PE/DCL/DD/0125411--9001--125


CDLComp.

GPRS/

EDGE

Createdin

release






Tdma pcuEdgeUpTransmittedMcs2 15162/0 CUM TDMA idem CDL Attribute V15.0 E







Tdma pcuEdgeMcs2RequestRetransData-BlockUp














Tdma pcuEdgeLAUpTargetedTransmit-tedMcs2














Ccch pcuChannelRequestOnePhase 15190/0 CUM CCCH idem CDL Attribute V15.0 G / E

Ccch pcuUpTbfImmediateAssignmentOne-Phase

15191/0 CUM CCCH idem CDL Attribute V15.0 G / E

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



CDLComp.

GPRS/

EDGE

Createdin

release


15193/0 AVG CELL pcuUpThroughputAvg V15.0 G

CgiCell pcuUpPipeGreater22kbps 15194/0 CUM CELL idem CDL Attribute V15.0 G

CgiCell pcuDnPreEstWithLLCFrameTrans-mitted

15195/0 CUM CELL idem CDL Attribute V15.0 G / E

1.6.3 Throughput Counters and Satisfaction Rate Counters

This following is a list of these counters:

Counter No. Q3 name15077/0 dnTbfGoldSatisfactMore90pCent15077/1 dnTbfGoldSatisfactBet5090pCent15077/2 dnTbfGoldSatisfactLess50pCent

15078/0 dnTbfSilverSatisfactMore90pCent15078/1 dnTbfSilverSatisfactBet5090pCent

15078/2 dnTbfSilverSatisfactLess50pCent15079/0 dnTbfBronzeSatisfactMore90pCent15079/1 dnTbfBronzeSatisfactBet5090pCent

15079/2 dnTbfBronzeSatisfactMore90pCent15029/1 upTbfGoldSatisfactMore90pCent

15029/2 upTbfGoldSatisfactBet5090pCent15029/3 upTbfGoldSatisfactLess50pCent15031/4 upTbfSilverSatisfactMore90pCent

15034/1 upTbfSilverSatisfactBet5090pCent15062/2 upTbfSilverSatisfactLess50pCent

15061/1 upTbfBronzeSatisfactMore90pCent15062/3 upTbfBronzeSatisfactBet5090pCent15062/4 upTbfBronzeSatisfactMore90pCent

15079/2 dnTbfBronzeSatisfactLess50pCent15058/3 dnPipeBetween11and22kbps

15058/4 dnPipebetween22and33kbps15060/0 dnPipeGreater33kbps15061/0 upPipeless11kbps

15062/0 upPipeGreater11kbps15062/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.

The following downlink throughput counters:


PE/DCL/DD/0125411--9001--125


· 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 thespecified 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 thesepcified 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 thespecified limits is reached in <direction> by a <ServiceClass> MS in the cell.

The throughput counters and the satisfaction rate counters are computed as follow.For each pipe (set of radio resources allocated to aMS), the following counters aredefined :

dnNbDataBytes: cumulative number of bytes in downlink RLC data blockreceived on the pipe

dnVerboseTime: cumulative time the PCU is ready to transmit downlink RLCdata blocks on the pipe (this excludes for instance MS reaction times after aresource assignment, keep alive duration, ...)

upNbDataBytes: cumulative number of bytes in uplink RLC data blockstransmitted on the pipe

upVerboseTime: cumulative time the PCU is ready to receive uplink RLC datablocks on the pipe (this excludes for instance MS reaction times after a resourceassignment)



On pipe closure (and if <direction>VerboseTime is not null), for both directions thefollowing actions are done:

Compute the throughput as follow:

• <direction>Throughput=<direction>NbDataByte <direction>VerboseTime

· Increments the right <direction> throughput counter corresponding to the limitsincluding the <direction>Throughput value

· Compute the satisfaction rate as follow:

• <direction>SatisfactionRate=<direction>Throughput/<direction>PeakThroughput

· Increments the right <direction> satisfaction rate counter corresponding to thelimits 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 anew pipe is created

Note that the pipe is not necessary closed at transitions from full to half duplextransfer.

1.6.3.1 Example of how Throughput Monitoring Counters work

To facilitate understanding of this type of counter, the following is an example ofhow 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


PE/DCL/DD/0125411--9001--125


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 negotiated with the SGSN(UL traffic profile), the ping request is transmitted over the Gb interface.

Before the ping response, downlink TBF is established (DownlinkPre--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 previouslyestablished and both TBF end.

Counter Incrementations:

UpPipeGreater11kbps +1

DnPipeGreater33kbps +1

Note: If the UL traffic profile parameters used for the establishment of the uplinkTBF are different from the PCU default traffic profile parameters used forDownlink 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 profileparameters (UL signaling profile). The mobile is then located thanks to the emptyLLC frame transmitted to the SGSN.



PCU establishes a downlink TBF that will allow to transmit the ping request to theclient: theprofile parameters received fromSGSN (DL traffic profile) are thenused.

Once the ping request has been received by the client, an uplink TBF is establishedto transmit the ping response: the profile parameters received from the MS (ULtraffic profile) are used. Finally both TBF end.

Note: The traffic profile used to establish the downlink TBF depends on theSGSN implementation.

Counter Incrementations:

1st Case: DL traffic profile¸ UL traffic profile and DL traffic profile ¸ ULsignaling profile:

• UpPipeGreater11kbps +3

• dnPipeBetween22and33kbps +2

2nd Case: DL traffic profile = UL traffic profile and DL traffic profile¸ ULsignaling profile:



3rd Case: DL traffic profile ¸ UL traffic profile and DL traffic profile = ULsignaling profile:




PE/DCL/DD/0125411--9001--125


PAGE INTENTIONALLY LEFT BLANK

Counter descriptionNortel Networks Confidential 2--1


2 COUNTER DESCRIPTION

2.1 Dictionary presentation

2.1.1 Dictionary contents

The Dictionary of counters describes each of the observation counters contained inpermanent (BSS, md, and manager) and temporary observation reports.

It includes the synthetic counters defined by the network operator in agreementwiththe manufacturer, which supplement the counters displayed in permanent bscobservation reports.

The first paragraph presents the observation counters and defines the main termsused in the Dictionary of counters.

The following paragraphs of the Dictionary describes the counters on a pertype/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 releaseshandled by the V15 OMC--R.

2.1.2 Observation counter references

2.1.2.1 Counter numbering

On the OMC--R, each observation counter is referenced by a number thatunambiguously 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 e3). . . . . . . . . . . . .

• 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 observedentity whereas a synthetic counter contains the processed results calculated by theOMC--R from raw measurements.

BSS temporary, permanent md, and permanent manager observations only use rawcounters.

Counter description Nortel Networks Confidential2--2

PE/DCL/DD/0125411--9001--125


2.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 isthe absolute counter definition.

The suffix “/c” identifies the associated cause number when the counter isidentified by cause.

Title: counter name. It explains the counter in plain language and summarizes itsexact function.

A counter whose name begins with Number tallies a number of events in adefined observation period, a counter whose name begins with Rate displays apercentage, a counter whose name begins with Ratio does not contain unitvalues.

Name Q3: name of the counter mediated on the NMC/MD--R interface

Feature: new field introduced since V14, to give the name of the feature thatrequested the creation of the counter

Object: geographic counter coverage. A counter occurrence is defined by therelated object occurrence:

• BSS counter: adjacentCellHandOver, bsc, bts, btsSiteManager, channel,pcmCircuit, signallingLink, transceiverZone

• 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 bsccounters 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)



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, andforwarded to the OMC--R manager, or counter reading directly processed bytheOMC--Rmanager. The only possible calculations are the averages of samecounter occurrence values.

• synthetic: counter processed by the OMC--R manager using severaloccurrences of the same counter or several BSS (raw or synthetic) counters.

• permanent: observation counter displayed in response to a permanentobservation report request.

• temporary: observation counter displayed in response to a temporaryobservation request.

Class: class of a permanent BSS observation counter. The following classes aredefined:

• A interface

• Abis interface

• ASCI (GSM--R functions)

• assignment (of dedicated channels)

• BSC equipment

• BSS/OMC--R link

• GPRS

• 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 forincreasing the counter value is detected by the BTS and the information isforwarded to the BSC as a message on the Abis interface. The BSCdynamicallymanages the list of counter occurrences received on the interfaceduring the observation period.

In case of an Abis interface break (by locking or defective equipment (AbisPCM, site, cell)), nomessage is forwarded to the BSC and no counter value iscollected. If the interface break covers the entire observation period, thecounters are empty in the CCCH array in permanent bsc observation reports.


PE/DCL/DD/0125411--9001--125


• recorded by the BSC: The events that modify the counter values are detectedby 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 countersreceived from the BSC in response to a report request. The OMC--R does notstore the counter.

• calculated by theOMC--R agent (permanentmd observation): The events thatmodify the counter value are detected by the OMC--R agent. The OMC--Rmanages and stores the counter.

• calculated by the OMC--R manager (permanent manager observation): Theevents thatmodify the counter value are detected by theOMC--Rmanager or aconnected workstation. The OMC--R manages and stores the counter.

Precise incrementation conditions: new field introduced since V14, to explainwhen and why the counter is triggered

Exception conditions: new field introduced sinceV14, to explainwhen andwhythe counter is NOT triggered

Dataflows: new field introduced since V14, to show graphically when thecounter is triggered

Note: optional field containing comments

2.1.4 Basic definitions

The following definitions apply to the terms used in the Dictionary of Counters.

2.1.4.1 Resources

Allocation

Resource allocation is a purely software function that consists of reserving aresource for future use and must not be confused with ACTIVATION which is aprocess involving a physical action (radio transmission, data transfer).

Message sequencing situates resource allocation in time:

an SDCCH is allocated on receipt of the Abis CHANNEL REQUIREDmessageand before sending the Abis CHANNEL ACTIVATE message.

a TCH is allocated before sending the Abis CHANNEL ACTIVATE message inASSIGNMENT, INTERNAL, and EXTERNAL HANDOVER procedures.

a CIC is allocated immediately before the TCH, that is before the AbisCHANNEL ACTIVATE message is sent in ASSIGNMENT and incomingEXTERNAL HANDOVER procedures.

Deallocation

Resource deallocation is a purely software function that consists of releasing aresource after use and must not be confused with DEACTIVATION which is aprocess involving a physical action.



Message sequencing situates resource de--allocation in time:

an SDCCH is deallocated on receipt of the Abis RF CHAN RELEASE ACKmessage or when the “Trfack” timer expires.

a TCH is deallocated on receipt of the AbisRF CHANRELEASEACKmessageor when the “Trfack” timer expires.

a CIC is deallocated immediately after the TCH, that is on receipt of the Abis RFCHAN RELEASE ACK message or when the “Trfack” timer expires.

2.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 Ainterface

on MSC request, by sending a CONNECTION CONFIRM message on the Ainterface

SCCP connection refusal

AnSCCP connection is refusedon receipt of aCONNECTIONREFUSEDmessagefrom 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

2.1.4.3 Handover

Handover required

The handover decision algorithm sends an internal message containing an orderedlist of potential cells able to satisfy handover needs. Several requests may be sentfor the same handover.

Handover requests

A handover request is a purely software process which consists of examining thecells able to satisfy handover needs.

Executed handover

Ahandover is executed after the HANDOVERCOMMANDmessage is sent on theAbis interface.

Successful handover

A handover is successful if the HANDOVERCOMPLETE message is received onthe Abis interface.


PE/DCL/DD/0125411--9001--125


2.2 Raw permanent BSS counters (BSC 2G)

l1026 Number of decoded RACH access from the mobiles

Name Q3 : rachBusyCountrachBusyCountTs2rachBusyCountTs4rachBusyCountTs6

Object : bts

Location :

Name Q3 Location

rachBusyCount CCCH--0

rachBusyCount2 CCCH--2



Function : number of RACH bursts received by the BTS that have been decode;this internal BTS counter is sent to the BSC inCCCH_LOAD_INDICATION message.

Event : receipt of a RACH burst decoded by the BTS; receipt of aCCCH_LOAD_INDICATION message by the BSC.

Type : raw permanent

Class : monitoring

Source : detected by the BTS, recorded by the BSC

Feature : Extended CCCH (TF184 -- V12)

Preciseincrementation conditions :

When GPRS is activated, this counter is concerned by the followingcalls:

CCT: Circuit calls on TCH channelCCP: Circuit Calls on PDTCH preempted to make a TCH channelCP: Com packet on PDTCH channel

No distinction is made between RACH dedicated to Circuit Calls orPacket Calls.

Note : Countermultiplexed onTSs 0, 2, 4 and 6 for Extended CCCH feature.



l1027 Number of decoded RACH access forwarded to the BSC

Name Q3 : rachAccessCountrachAccessCountTs2rachAccessCountTs4rachAccessCountTs6

Object : bts

Location :

Name Q3 Location

rachAccessCount CCCH--0

rachAccessCount2 CCCH--2



Function : number of RACH bursts that have been decoded and forwarded to theBSC; this internal BTS counter is sent to the BSC inCCCH_LOAD_INDICATION message.

Event : transmission of CHANNEL REQUEST to the BSC; receipt of aCCCH_LOAD_INDICATION message from the BTS


Class : monitoring





CCT: Circuit calls on TCH channel

CCP: Circuit Calls on PDTCH preempted to make a TCH channelCP: Com packet on PDTCH channel




PE/DCL/DD/0125411--9001--125


l1028 Number of paging messages sent without delay

Name Q3 : pchNoWaitpchNoWaitTs2pchNoWaitTs4pchNoWaitTs6

Object : bts

Location :

Name Q3 Location

pchNoWait CCCH--0

pchNoWait2 CCCH--2

pchNoWait4 CCCH--4

pchNoWait6 CCCH--6

Function : number of paging requestswhich have got a free TS immediately; thisinternal BTS counter is sent to the BSC in aCCCH_LOAD_INDICATION message.

Event : immediat transmission of a PAGING_REQUEST to the MS; receiptof a CCCH_LOAD_INDICATION message from the BTS.


Class : monitoring






The counter C1028 is related to theAbis paging and also to thepagingthat is being sent on radio interface for the first time (the bts pagingrepetition is not counted).

The counter C1028 counts the pagingmessages that have found a freePCH on the first paging slot occurrence.That means that C1028 paging messages have waited less thanNoOfMultiframesBetweenPaging multiframes.



CCP: Circuit Calls on PDTCH preempted to make a TCH channel

CP: Com packet on PDTCH channel


Data flows : The following data flow presents the Layer 3 messages related to thepaging:

MSC BSC BTS MS

Paging Cmd

+C1028

PAGING_REQUEST1

Est Ind

PAGING_REQUEST2

PAGING_REQUEST3

The BTS repeatsNbOfRepeat times all the paging messages comingfrom the MSC but the counter C1028 is incremented for the freshpaging only.

The counter C1028 will be incremented when a free PCH on the firstpaging is available.


PE/DCL/DD/0125411--9001--125


l1029 Number of paging messages sent with one slot delay

Name Q3 : pchOneWaitpchOneWaitTs2pchOneWaitTs4pchOneWaitTs6

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 afree TS; this internal BTS counter is sent to the BSC in aCCCH_LOAD_INDICATION message.

Event : transmission of a PAGING_REQUEST to the MS after one wait;receipt of a CCCH_LOAD_INDICATION message from the BTS.


Class : monitoring




The counter C1029 is related to theAbis paging and also to thepagingthat is being sent on radio interface for the first time (the bts pagingrepetition is not counted).The counter C1029 counts the pagingmessages that have found a freePCH on the second paging slot occurrence. It means that C1029paging messages have waited more thanNbOfMultiframesBetweenPaging multiframes and less than 2xNbOfMultiframesBetweenPaging multiframes.For example:If NbOfMultiframesBetweenPaging = 8 (8 multiframes of 240msbetween the same paging group), C1029 paging messages havewaited between 1x8x240 ms (about 2 sec) and 2x8x240 ms (about 4sec).






Data flows : The following dataflow presents the Layer 3 messages related to thepaging:

MSC BSC BTS MS

Paging Cmd

+C1029PAGING_REQUEST1

Est Ind

PAGING_REQUEST2

PAGING_REQUEST3

(1ST PAGING SLOT OCCUR-ENCE IS BUSY)


The fresh pagingmessage has towait for thenext paginggroup slot asthe first paging group presented was busy.

l1030 Number of paging messages sent with two slots delay

Name Q3 : pchTwoWaitpchTwoWaitTs2pchTwoWaitTs4pchTwoWaitTs6

Object : bts


PE/DCL/DD/0125411--9001--125


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 afree TS; this internal BTS counter is sent to the BSC in aCCCH_LOAD_INDICATION message.

Event : transmission of a PAGING_REQUEST to the MS after two waits;receipt of a CCCH_LOAD_INDICATION message from the BTS.


Class : monitoring





The counter C1030 counts the pagingmessages that have found a freePCH on the third paging group occurrence because the 2 previousones were busy. It means that the counter C1030 fresh pagingmessages from the MSC have waited more than2xNbOfMultiframesBetweenPaging multiframes and less than3xNbOfMultiframesBetweenPagingmultiframe to get its freePCH.




CP: Com packet on PDTCH channel





MSC BSC BTS MS

Paging Cmd


Est Ind

PAGING_REQUEST2

PAGING_REQUEST3

(1ST AND 2ND PAGING SLOT OCCUR-RENCES ARE BUSY)


The fresh pagingmessage has towait for thenext paginggroup slot asthe first and second paging groups presented were busy.

l1031 Number of paging messages sent with more than two slots delay

Name Q3 : pchMoreWaitpchMoreWaitTs2pchMoreWaitTs4pchMoreWaitTs6

Object : bts

Location :

Name Q3 Location

pchMoreWait CCCH--0

pchMoreWait2 CCCH--2



Function : number of paging requests which had to wait twice before finding afree TS; this internal BTS counter is sent to the BSC in aCCCH_LOAD_INDICATION message.


PE/DCL/DD/0125411--9001--125


Event : transmission of a PAGING_REQUEST to the MS; receipt of aCCCH_LOAD_INDICATION message from the BTS.


Class : monitoring





The counter C1031 counts the paging messages that need to waitmore than 2 paginggroup slots. It means that the counter C1031 freshpaging messages from the MSC have waited for more than3xNbOfMultiframesBetweenPaging multiframes.






MSC BSC BTS MS

Paging Cmd


Est Ind

PAGING_REQUEST2

PAGING_REQUEST3

(1ST, 2ND, AND 3RD PAGING SLOTOCCURRENCES ARE BUSY)



The BTS repeatsNbOfRepeat times all the paging messages comingfrom the MSC but the counter C1031 is incremented for the freshpaging only.The fresh pagingmessage has towait for thenext paginggroup slot asthe first, second, and third paging groups presented were busy.

l1033 Average level of non-decoded RACH access

Name Q3 : rachNonDecodedAvLevelMoyrachNonDecodedAvLevelTs2MoyrachNonDecodedAvLevelTs4MoyrachNonDecodedAvLevelTs6MoyrachNonDecodedAvLevelMax = Max RACH access levelrachNonDecodedAvLevelTs2Max = Max RACH access levelrachNonDecodedAvLevelTs4Max = Max RACH access levelrachNonDecodedAvLevelTs6Max = Max RACH access levelrachNonDecodedAvLevelCum = Total RACH access levelrachNonDecodedAvLevelTs2Cum = Total RACH access levelrachNonDecodedAvLevelTs4Cum = Total RACH access levelrachNonDecodedAvLevelTs6Cum = Total RACH access levelrachNonDecodedAvLevelEch = Number of samplesrachNonDecodedAvLevelTs2Ech = Number of samplesrachNonDecodedAvLevelTs4Ech = Number of samplesrachNonDecodedAvLevelTs6Ech = Number of samples

Object : bts

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 maximumlevel of RACHbursts not decoded (dBm); this internal BTS counter issent to the BSC in a CCCH_LOAD_INDICATION message.

Event : receipt of a RACH burst that the BTS cannot decode


Class : monitoring



PE/DCL/DD/0125411--9001--125








l1044 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) andmaximumseizure of signaling channels expressed inmilliseconds, calculated onall allocations in the cell

Event : signaling channel allocation on reception of CONNECTIONCONFIRM (first establishment in the BSS) or HANDOVERCOMPLETE (incoming inter handover in signaling phase) /deallocationon reception ofASSIGNCOMPLETEorwhen the call isreleased

allocation: start timerdeallocation:• stop and read timer• store its peak value• add measured value to the total number of allocation durationsfor the observation period

• step up by one the number of samples




Class : assignment

Source : recorded by the BSC



CCT: Circuit calls on TCH channelCCP: Circuit Calls on PDTCH preempted to make a TCH channel

But it is not concerned byCP calls (Com packet on PDTCHchannel).

Data flows : Refer to Chapter 1

DFD “GPRS procedure (no available resource for a PDTCHpreemption)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Dedicated channel assignment modify procedure (normalcompletion)”DFD “Direct retry handover procedure”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”

l1045 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 ssignallingPhaseDurationHighEch Number of samples.

Object : bts

Function : average (= total seizure divided by number of samples) andmaximumseizure of signaling channels expressed inmilliseconds, calculated onall allocations lasting more than 25 seconds


PE/DCL/DD/0125411--9001--125


Event : signaling channel allocation on reception of CONNECTIONCONFIRM (first establishment in the BSS) or HANDOVERCOMPLETE (incoming inter handover in signaling phase) /deallocationon reception ofASSIGNCOMPLETEorwhen the call isreleased

allocation: start timer

deallocation: stop and read timer. When the value read is greaterthan 25 seconds, do the following:

• store its peak value• add measured value to the total number of allocations lastingmore than 25 seconds for the observation period



Class : assignment







DFD “GPRS procedure -- preemption on PDTCH (normalcompletion)

DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”

DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Dedicated channel assignment modify procedure (normalcompletion)”DFD “Direct retry handover procedure”

DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”



l1049 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 theobservation period

Event : transmission of ASSIGNMENT COMMAND to the mobile


Class : assignment







DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”

l1050 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 theobservation period

Event : receipt of ASSIGNMENT COMPLETE message by the BSC


Class : assignment



PE/DCL/DD/0125411--9001--125






Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “Direct retry handover procedure”

l1055 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 orpreempted PDTCH from the MS


Class : assignment








l1057 Average duration to allocate all TCH/FRandpreemptedPDTCH

resources

Name Q3 : allTchFrAllocatedTimeMoy Average allocation duration. . . . . .allTchFrAllocatedTimeMax Maximum allocation duration. . . . . .allTchFrAllocatedTimeCum Total allocation duration. . . . .allTchFrAllocatedTimeEch Number of samples. . . . . .allTchFrAllocatedTimeTrZoneMoy Average allocation durationallTchFrAllocatedTimeTrZoneMax Maximum allocation durationallTchFrAllocatedTimeTrZoneCum Total allocation durationallTchFrAllocatedTimeTrZoneEch Number of samples

Object : transceiverZone/bts

Function : average (= total duration divided by number of samples) andmaximumduration during which all available TCH/FR resources andPDTCH resources configured as preemptable are used in the cell forthe observation period, expressed in milliseconds

Event :Starts measurement on allocation of ALL the available TCH/FRand preemptable PDTCH resources of the cell.Stops as soon as a resource is free.As a result, the counter behavior depends on the setting ofgprsPreemption parameter on the OMC--R side.In case of preemption not acknowledged by the PCU, the counterstarts immediately and stops as soon as a resource is released, or assoon as the timer GprsPreemptionProtection elapses.


Class : allocation

Source : calculated by the OMC--R agent





When new counter 1823 is received, its value is copied in counter1057.

Note : A blocked resource is neither considered as used nor available.


PE/DCL/DD/0125411--9001--125


l1060/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 durationallSdcchAllocatedTimeTrZoneMax Maximum allocation durationallSdcchAllocatedTimeTrZoneCum Total allocation durationallSdcchAllocatedTimeTrZoneEch Number of samples


Function : average (= total duration divided by number of samples) andmaximum allocation duration of all available SDCCHs used in thecell 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 isallocatedstops as soon as a SDCCH resource is freed


Class : allocation



When GPRS is activated, this counter is concerned by the followingcalls:CCT: Circuit calls on TCH channelCCP: Circuit Calls on PDTCH preempted to make a TCH channel


l1065/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







Data flows : Refer to Chapter 1DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”

l1065/1 Number of outgoing intra BSS handover execution attempts

from the cell for directed retry reasonName Q3 : hoExecutionOutgoingIntraBssForDirectedRetryObject : bts

Function : Number of outgoing intra BSS handover execution attempts from thecell for directed retry reason

Event : Transmission of HANDOVER_COMMAND message (ABISmessage)


Class : handover





Data flows : Refer to Chapter 1DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”


PE/DCL/DD/0125411--9001--125


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





Data flows : Refer to Chapter 1DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”

l1066/1 Number of outgoing interBSShandover execution attempts from

the cell for directed retry reason

Name Q3 : hoExecutionOutgoingInterBssForDirectedRetry

Object : bts

Function : Number of outgoing inter BSS handover execution attempts from thecell for directed retry reason

Event : Receipt of HANDOVER_COMMAND message from the MSC


Class : handover








l1067/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





Data flows : Refer to Chapter 1DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”

l1067/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 fordirected retry reason

Event : Receipt of HANDOVER_COMPLETE message from the mobile


Class : handover



PE/DCL/DD/0125411--9001--125






l1068/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 exceptthose after first attempt

Event : receipt of CLEARCOMMANDfrom theMSCwith cause “HandoverSuccessful”


Class : handover






Note : For the number of successful outgoing inter handovers on TCH afterfirst attempt see counter 1078.



l1068/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 fordirected retry reason

Event : Receipt of CLEAR_COMMAND message from the MSC with thehandover cause set to “handover successful”


Class : handover







DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”

Note : For the number of successful outgoing inter handovers on TCH afterfirst attempt see counter 1078.

l1069 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 cellfor any kind of the mobile

Event : attempt to select a target cell in the list of eligible cells on transmissionof HANDOVER REQUIRED on the A interface


Class : handover



PE/DCL/DD/0125411--9001--125







Note : the counter is incremented at the end of the handover (success,selection failure, execution failure or end of call)

l1070 Number of incoming inter--bss handovers on TCH requested

Name Q3 : hoRequestIncomingInterBsshoRequestIncomingInterBssTchCtm

Object : bts

Function : number of incoming inter-bss handover requests on TCH in the cell

Event : receipt of HANDOVERREQUEST from theMSC on the A interface


Class : handover










l1071 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 TCHin the cell for any kind of the mobile



Class : handover






Note : the counter is incremented at the end of the handover (success,selection failure execution failure or end of call)

l1072 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 fromthe target BSS to the MSC


Class : handover



PE/DCL/DD/0125411--9001--125






l1073 Number of successful incoming intra--bss handovers on TCHName Q3 : hoSuccessIncomingIntraBssObject : bts

Function : number of successful incoming intra-bss handovers on TCH in thecell



Class : handover






l1074 Number of successful incoming inter--bss handovers on TCHName Q3 : hoSuccessIncomingInterBss

Object : btsFunction : number of successful incoming inter-bss handovers on TCH





Class : handover






l1075 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 thehandover algorithm


Class : handover








PE/DCL/DD/0125411--9001--125


l1076 Number of outgoing inter--bss handovers on TCH requestedName 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 transmissionof HANDOVER REQUIRED on the A interface


Class : handover






l1077 Number of successful outgoing intra--bss handovers on TCH

after first attemptName Q3 : hoSuccessOutgoingFirstIntra

Object : bts

Function : number of successful outgoing intra-bss handoversonTCHto the firstcell from the list of eligible cells



Class : handover








DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”

DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”


Note : the list is reorganized by the BSC Ho decision according to the cellpriority feature (TF716). It may not be the same order as the onereceived from the L1M.

l1078 Number of successful outgoing inter--bss handoversonTCHafter

first attempt

Name Q3 : hoSuccessOutgoingFirstInter

Object : bts

Function : number of successful outgoing inter-bss handoversonTCHto the firstcell from the list of eligible cells

Event : receipt of CLEARCOMMANDfrom theMSCwith cause “HandoverSuccessful”


Class : handover





CCP: Circuit Calls on PDTCH preempted to make a TCH channelBut it is not concerned byCP calls (Com packet on PDTCHchannel).



Note : the list is reorganized by the BSC Ho decision according to the cellpriority feature (TF716). It may not be the same order as the onereceived from the L1M.


PE/DCL/DD/0125411--9001--125


l1081 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






l1082 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 ASSIGNCOMMAND to the cell during the intra-btshandover procedure


Class : handover








l1083 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-btshandover procedure


Class : handover


Note : This counter is the sum of the 1073 and 1077 counters.





l1084/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


Class : Abis interface



PE/DCL/DD/0125411--9001--125



When GPRS is activated, this counter is concerned by the followingcalls:CCT: Circuit calls on TCH channelCCP: Circuit Calls on PDTCH preempted to make a TCH channelCP: Com packet on PDTCH channel

l1084/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






l1084/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






l1086 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

Event : rejection of a GPRS RACH message


Class : equipment


Feature : GPRS (SV407 -- V12)


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

l1087 Number of GPRS IMMEDIATE ASSIGNMENT messages

rejected due to SICD<x> board overloadName Q3 : gprsImmAssRejectedSicd<x>.....for x = 0 to 9

Object : bsc gprsImmAssRejectedSicd0


PE/DCL/DD/0125411--9001--125


Location :

Name Q3 Location

gprsImmAssRejectedSicd<x> SICD--<x>

Function : Number of GPRS IMMEDIATE ASSIGNMENT messages rejecteddue to SICD<x> board overload

Event : rejection of a GPRS IMMEDIATE ASSIGNMENT message


Class : equipment



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


l1088 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 PAGINGmessages rejected due to SICD<x>boardoverload

Event : rejection of a GPRS PAGING message


Class : equipment





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


l1094 Number of terrestrial circuits allocatedName Q3 : tcAllocated

Object : bsc

Function : number of terrestrial circuit allocations (CIC) in the BSC

Event : allocation of a terrestrial circuit


Class : A interface





Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (no resource available for a PDTCHpreemption)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “dedicated channel assignment procedure (no resourceavailable and queuing not activated)”DFD “queuing of the assignment procedure (normal completion)”DFD “Dedicated channel assignment modify procedure (normalcompletion)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”


PE/DCL/DD/0125411--9001--125


1095 Average number of terrestrial circuits used

Name Q3 : tcAveragedUsedMoy Average terrestrial circuits. . . . . . . . . . .allocatedtcAveragedUsedMax Max terrestrial circuits. . . . . . . . . . .allocatedtcAveragedUsedCum Total terrestrial circuits. . . . . . . . . . .allocatedtcAveragedUsedEch Number of samples. . . . . . . . . . . .

Object : bsc

Function : average (= total number divided by number of samples) andmaximum number of terrestrial circuits (CIC) allocated in the BSC,obtained through internal sampling

Event : terrestrial circuit allocation/deallocation, internal sampling time-outelapse:

allocation: step up by one the instantaneous value of terrestrialcircuits allocated

deallocation: step down by one the instantaneous value ofterrestrial circuits allocated

sampling time-out elapse:

• read the instantaneous value of circuits allocated

• store its peak value

• add it to the total of allocated circuits for the observation period



Class : A interface










DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (no resource available for a PDTCHpreemption)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Dedicated channel assignment modify procedure (normalcompletion)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”DFD “Radio channel release RELEASE INDICATION procedure(normal completion)”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”

l1104/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



This counter is concerned by the following calls:




PE/DCL/DD/0125411--9001--125


Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion)”DFD “Immediate assignment procedure (normal completion)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “Dedicated channel assignment modify procedure (normalcompletion)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”DFD “SMS procedure (SMS established by the MS)”

l1104/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



This counter is concerned by the location procedure beginning, forBSS hybrid solution.

l1105 Average number of SCCP connections established

Name Q3 : sccpAveragedUsedMoy Average SCCP connections. . . . . . . . .establishedsccpAveragedUsedMax Max SCCP connections. . . . . . . . .establishedsccpAveragedUsedCum Total SCCP connections. . . . . . . . .establishedsccpAveragedUsedEch Number of samples. . . . . . . . . .

Object : bsc

Function : average (= total number divided by number of samples) andmaximum number of SCCP connections established in the BSC,obtained through internal sampling.



Event : SCCP connection establishment/release, internal sampling time-outelapse:establishment: step up by one the instantaneous value of SCCPconnections establishedrelease: step down by one the instantaneous value of SCCPconnections establishedsampling time-out elapse:• read the instantaneous value of SCCP connections established• store its peak value• add it to the total number of SCCP connections established forthe observation period



Class : A interface





Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “Immediate assignment procedure (normal completion)”DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “Dedicated channel assignment modify procedure (normalcompletion)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Radio channel release DEACTIVATE SACCH ACKprocedure (normal completion)”DFD “Radio channel release RELEASE INDICATION procedure(normal completion)”


PE/DCL/DD/0125411--9001--125


DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”DFD “SMS procedure (SMS established by the MS)”

l1106/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 orthe local SCCP layer

Event : SCCP connection establishment refusal due to the following causes:BSC request refused by local SCCP layerBSC request refused by the MSC


Class : A interface






l1106/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







l1106/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 orthe local SCCP layer

Event : SCCP connection establishment (with SSN LCS) refusal due to thefollowing causes:BSC request refused by local SCCP layerBSC request refused by the MSC


Class : A interface




l1106/3 Number of SCCP connectionswith SSNLCS, refused by theBSC

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 thefollowing causes:

MSC request refused by the BSC


Class : A interface



PE/DCL/DD/0125411--9001--125




l1107 Number of BSSAP messages receivedName Q3 : aInputMessage

Object : bsc

Function : number of BSSAP messages received by the BSC

Event : receipt of SCCP CONNECTION REQUEST, or SCCP DATAREQUEST, or SCCP UNIT DATA REQUEST message


Class : A interface





Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion)”DFD “GPRS procedure (no available resource for a PDTCHpreemption)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “Immediate assignment procedure (normal completion)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “dedicated channel assignment procedure (no Resourceavailable and queuing not activated)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”



DFD “Immediate assignment paging procedure (normalcompletion)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”DFD “SMS procedure (SMS established by the MS)”DFD “SMS procedure (SMS established by the MSC)”

l1108 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 DATAREQUEST, or SCCP UNIT DATA REQUEST message


Class : A interface






Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion)”DFD “GPRS procedure (no available resource for a PDTCHpreemption)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “Immediate assignment procedure (normal completion)”DFD “dedicated channel assignment procedure (normalcompletion)”


PE/DCL/DD/0125411--9001--125


DFD “dedicated channel assignment procedure (no Resourceavailable and queuing not activated)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”DFD “SMS procedure (SMS established by the MS)”

l1109 Number of erroneous BSSAP messages received

Name Q3 : aMessageErrors

Object : bsc

Function : number of errored BSSAP messages received by the BSC atapplication level

Event : receipt of SCCP CONNECTION INDICATION, or SCCP DATAINDICATION, or SCCP UNIT DATA INDICATION, with incorrectformat


Class : A interface








l1114 Average time of PCM unavailability

Name Q3 : pcmUnavailabilityMoy Average PCM unavailability. . . . . . . . .timepcmUnavailabilityMax 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 maximumtime of BSS external PCM unavailability in the observation period,expressed in milliseconds

Event : PCM operational state changes (operationalState attribute):

leave “enabled” state: set timerchange to “enabled” state:• stop and read timer• store its peak value• add the value read to the previous total time of unavailability inthe observation period



Class : PCM link





l1115 Number of link changeovers

Name Q3 : omcLinkSwitchOver

Object : bsc

Function : number of BSS/OMC--R link switchovers


PE/DCL/DD/0125411--9001--125


Event : loss of Level 2 on the BSS/OMC--R link


Class : BSS/OMC--R link




l1121 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




l1122 Number of passive chain response messagesName Q3 : chainStandByResponse

Object : bsc

Function : number of responsemessages sent from the passive to the BSC activechain

Event : reception of a response message from the BSC passive chain








l1134 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 thecommunication has been re--established on starting channel

Event : receipt of ASSIGN FAILURE before T3107 time-out elapse


Class : handover





l1135 Number of unsuccessful outgoing intra--bss handovers on TCH

forwhich the communicationhasbeen re--established on startingchannel

Name Q3 : hoUnsuccessReestOutgoingIntraBssTch

Object : bts

Function : number of unsuccessful outgoing intra-bss handovers for which thecommunication has been re--established on starting channel

Event : receipt of HANDOVER FAILURE before T3103 time-out elapse


Class : handover



PE/DCL/DD/0125411--9001--125





l1136 Number of unsuccessful outgoing inter--bss handovers on TCH

forwhich the communicationhasbeen re--established on startingchannel

Name Q3 : hoUnsuccessReestOutgoingInterBssTch

Object : bts

Function : number of unsuccessful outgoing inter-bss handovers on TCH forwhich the communication has been re--established on starting channel

Event : receipt of HANDOVER FAILURE before T3103 time-out elapse(T3103 < bssMapT8) with transmission to the MSC


Class : handover





l1137 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 withcall reestablishment in the cell

Event : receipt of HANDOVER FAILURE


Class : handover







l1138/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 Uplinkpower (MS-to-BTS direction)

Event : receipt of HANDOVER INDICATION (internal message) withcause “uplink signal strength” from the L1M


Class : handover






l1138/1 Number of handovers onTCHrequired: Loss of Downlink power

Name Q3 : hoRequiredTchDownlinkStrength

Object : bts

Function : number of handovers on TCH required because of loss of Downlinkpower (BTS-to-MS direction)


PE/DCL/DD/0125411--9001--125


Event : receipt of HANDOVER INDICATION (internalmessage) with cause“downlink signal strength” from the L1M


Class : handover






l1138/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 Uplinkquality (MS-to-BTS direction)

Event : receipt of HANDOVER INDICATION (internalmessage) with cause“uplink signal quality” from the L1M


Class : handover








l1138/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 Downlinkquality (BTS-to-MS direction)

Event : receipt of HANDOVER INDICATION (internalmessage) with cause“downlink signal quality” from the L1M


Class : handover






l1138/4 Number of handovers on TCH required: Distance

Name Q3 : hoRequiredTchDistance

Object : bts

Function : number of handovers on TCH required because of distance


PE/DCL/DD/0125411--9001--125


Event : receipt of HANDOVER INDICATION (internalmessage) with cause“distance” from the L1M


Class : handover







l1138/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

Event : receipt of HANDOVER INDICATION (internalmessage) with cause“power budget” from the L1M


Class : handover









l1138/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

Event : receipt of HANDOVER INDICATION (internalmessage) with cause“microcell capture” from the L1M


Class : handover






l1138/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 aTRX/DRX taken out of service (O&M action)


PE/DCL/DD/0125411--9001--125


Event : receipt of HANDOVER INDICATION (internal message) withcause “TRX out of service” from the L1M


Class : handover






l1138/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 ofUplink quality (MS-to-BTS direction)



Class : handover








l1138/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 ofDownlink quality (BTS-to-MS direction)



Class : handover






l1138/10 Number of directed retry handovers on TCH required

Name Q3 : hoRequiredTchDirectedRetry

Object : bts

Function : number of directed retry handovers on TCH required


PE/DCL/DD/0125411--9001--125


Event : receipt of HANDOVER INDICATION (internal message) attempt ofdirected retry: receipt of CONNECTION REQUEST ACK messageor autonomously in case of directed retry from amicro--cell receipt ofa CONNECTION REQUEST ACK with an eligible cells list, afterTchoke expiry


Class : handover







l1138/11 intra--cell handover into a class 0 TDMA for downlink power

level ordistance, foramulti--class cell (concentric cell...) (only forHO_REQUIRED_TCH)

Name Q3 : hoRequiredTchTdmaClass0

Object : bts (concentric cell)

Function : TDMA_class_0: intra--cell handover into a class 0 TDMA fordownlink power level or distance, for a multi--class cell (concentriccell...) (only for HO_REQUIRED_TCH)

Event : receipt of HANDOVER INDICATION (internalmessage) with causedownlink power level or distance reason from the L1M


Class : handover








l1138/12 Number of intra-bts handovers on TCH required (concentric

cell): Class 1 TDMAName 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

Event : receipt of HANDOVER INDICATION (internalmessage) with causedownlink power level or distance reason from the L1M


Class : handover







PE/DCL/DD/0125411--9001--125


l1138/13 Number of handovers on TCH required: Forced handoverO&M

Name Q3 : hoRequiredTchInterBtsOm

Object : bts

Function : number of handovers onTCH forced towards the neighbor cells of theserving cell

Event : receipt of HANDOVER INDICATION (internalmessage) with cause“forced handover” from the L1M


Class : handover







l1138/14 Number of handovers on TCH required: Traffic

Name Q3 : hoRequiredTchTraffic

Object : bts

Function : number of handovers onTCH forced towards the neighbor cells of theserving cell

Event : receipt of HANDOVER INDICATION (internalmessage) with cause“traffic” from the L1M


Class : handover












Feature : Handover for traffic reasons (TF132 -- V12)

l1138/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 smallpattern (non--hopping channel to hopping channel)

Event : receipt of HANDOVER INDICATION (internalmessage) with cause“tiering handover from large pattern to small pattern” from the L1M


Class : handover







PE/DCL/DD/0125411--9001--125






Feature : Cell Tiering (TF995 -- V12)

l1138/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 largepattern (hopping channel to non--hopping channel)

Event : receipt of HANDOVER INDICATION (internalmessage) with cause“tiering handover from large small to large pattern” from the L1M


Class : handover













l1139/0 Number of handoverson SDCCHrequired: LossofUplinkpower

Name Q3 : hoRequiredSdcchUplinkStrength

Object : bts

Function : number of handovers on SDCCH required because of loss of Uplinkpower (MS-to-BTS direction)

Event : receipt of HANDOVER INDICATION (internalmessage) with cause“uplink signal strength” from the L1M


Class : handover





l1139/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 ofDownlink power (BTS-to-MS direction)

Event : receipt of HANDOVER INDICATION (internalmessage) with cause“downlink signal strength” from the L1M


Class : handover






PE/DCL/DD/0125411--9001--125


l1139/2 Number of handovers on SDCCH required: Loss of Uplink

qualityName Q3 : hoRequiredSdcchUplinkQuality

Object : bts

Function : number of handovers on SDCCH required because of loss of Uplinkquality (MS-to-BTS direction)



Class : handover





l1139/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 ofDownlink quality (BTS-to-MS direction)



Class : handover







l1139/4 Number of handovers on SDCCH required: Distance

Name Q3 : hoRequiredSdcchDistance

Object : bts

Function : number of handovers on SDCCH required because of distance

Event : receipt of HANDOVER INDICATION (internalmessage) with cause“distance” from the L1M


Class : handover






l1139/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

Event : receipt of HANDOVER INDICATION (internalmessage) with cause“power budget” from the L1M


Class : handover







PE/DCL/DD/0125411--9001--125


l1139/6 Number of handovers on SDCCH required: Microcell capture

Name Q3 : hoRequiredSdcchCapture

Object : bts

Function : number of handovers on SDCCH required because of microcellcapture

Event : receipt of HANDOVER INDICATION (internalmessage) with cause“microcell capture” from the L1M


Class : handover





l1139/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 aTRX/DRX taken out of service (O&M action)

Event : receipt of HANDOVER INDICATION (internalmessage) with cause“TRX out of service” from the L1M


Class : handover







l1139/8 Number of intra-bts handovers on SDCCH required: Loss of

Uplink qualityName Q3 : hoRequiredSdcchIntraBtsUplink

Object : bts

Function : number of intra-bts handovers on SDCCH required because of loss ofUplink quality (MS-to-BTS direction)



Class : handover





l1139/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 ofDownlink quality (BTS-to-MS direction)



Class : handover






PE/DCL/DD/0125411--9001--125


l1139/13 Number of handovers on SDCCH required: Forced handover

O&MName Q3 : hoRequiredSdcchInterBtsOm

Object : bts

Function : number of handovers on SDCCH forced towards the neighbor cells ofthe serving cell

Event : receipt of HANDOVER INDICATION (internalmessage) with cause“forced handover” from the L1M


Class : handover





l1139/14 Number of handovers on SDCCH required: TrafficName Q3 : hoRequiredSdcchTraffic

Object : bts

Function : number of handovers on SDCCH forced towards the neighbor cells ofthe serving cell

Event : receipt of HANDOVER INDICATION (internalmessage) with cause“traffic” from the L1M


Class : handover








l1140 Number of outgoing intra--bss handovers on SDCCH executed

Name Q3 : hoExecutionOutgoingIntraBssSdcch

Object : bts

Function : number of attempts to execute outgoing intra-bss handovers onSDCCH



Class : handover






l1141 Number of outgoing inter handovers on SDCCH executed

Name Q3 : hoExecutionOutgoingInterBssSdcch

Object : bts

Function : number of attempts to execute outgoing inter-bss handovers onSDCCH

Event : receipt of HANDOVER COMMAND from the MSC


Class : handover







PE/DCL/DD/0125411--9001--125


l1142 Number of successful outgoing intra--bss handovers on SDCCH

Name Q3 : hoSuccessOutgoingIntraBssSdcch

Object : bts

Function : number of successful attempts to execute outgoing intra-bsshandovers on SDCCH



Class : handover






l1143 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 CLEARCOMMANDwith cause “ Handover Successful ”from the MSC


Class : handover








l1144 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 thecell for any kind of the mobile

Event : attempt to select the cell as the serving cell


Class : handover







l1145 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 HANDOVERREQUEST from theMSC on the A interface


Class : handover







PE/DCL/DD/0125411--9001--125


l1146 Number of incoming intra--bss handovers on SDCCH execution

attemptName Q3 : hoExecutionIncomingIntraBssSdcch

Object : bts

Function : number of attempts to execute incoming intra-bss handovers onSDCCH in the cell for any kind of the mobile



Class : handover






l1147 Number of incoming inter--bss handovers on SDCCH executedName Q3 : hoExecutionIncomingInterBssSdcch

Object : bts

Function : number of attempts to execute incoming inter-bss handovers onSDCCH

Event : transmission of HANDOVER REQUEST ACKNOWLEDGE fromthe target BSS to the MSC


Class : handover







l1148 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 thecell



Class : handover






l1149 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







PE/DCL/DD/0125411--9001--125


l1150 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 thehandover algorithm


Class : handover






l1151 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 ofHANDOVER REQUIRED on the A interface


Class : handover








l1152 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 thefirst cell from the list of eligible cells



Class : handover






Note : the list is reorganized by the BSC Ho decision according tot he cellpriority feature (TF716). It may not be the same order as the onereceived from the L1M

l1153 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 thefirst cell from the list of eligible cells

Event : receipt of CLEAR COMMAND with cause “Handover Successful”from the MSC


Class : handover



PE/DCL/DD/0125411--9001--125





Note : the list is reorganized by the BSC Ho decision according tot he cellpriority feature (TF716). It may not be the same order as the onereceived from the L1M

l1154 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 accomodate an intra-bts handover


Class : handover





l1155 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 thecell

Event : transmission of ASSIGNCOMMAND to the cell during the intra-btshandover procedure


Class : handover







l1156 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

Event : receipt of ASSIGN COMPLETE from the cell during the intra-btshandover procedure


Class : handover






l1157 Number of unsuccessful intra-bts handovers on SDCCH for

which the communication has been re--established on startingchannel

Name Q3 : hoUnsuccessReestIntraBtsSdcch

Object : bts

Function : number of unsuccessful intra-bts handovers on SDCCH for which thecommunication has been re--established on starting channel

Event : receipt of ASSIGN FAILURE before T3107 time-out elapse


Class : handover



PE/DCL/DD/0125411--9001--125






l1158 Number of unsuccessful outgoing intra--bss handovers on

SDCCH for which the communication has been re--establishedon starting channel

Name Q3 : hoUnsuccessReestOutgoingIntraBssSdcch

Object : bts

Function : number of unsuccessful outgoing intra-bss handovers on SDCCH forwhich the communication has been re--established on starting channel

Event : receipt of HANDOVER FAILURE before T3103 time-out elapse


Class : handover






l1159 Number of unsuccessful outgoing inter--bss handovers on


Name Q3 : hoUnsuccessReestOutgoingInterBssSdcch

Object : bts

Function : number of unsuccessful outgoing inter-bss handovers on SDCCH forwhich the communication has been re--established on starting channel



Event : receipt of HANDOVER FAILURE before T3103 time-out elapse(T3103 < bssMapT8) with transmission to the MSC


Class : handover





l1160 Number of unsuccessful incoming intra--bss handovers on


Name Q3 : hoUnsuccessReestIncomingIntraBssSdcch

Object : bts

Function : number of unsuccessful incoming intra-bsshandovers onSDCCH forwhich the communication has been re--established on starting channel

Event : receipt of HANDOVER FAILURE


Class : handover





l1161/0 Number of immediate assignments rejected: Traffic with MSC

interruptedName Q3 : immediateAssignmentRejectTraffMsc

Object : bts

Function : number of immediate assignments rejected because the traffic withthe MSC is interrupted


PE/DCL/DD/0125411--9001--125


Event : transmission of IMMEDIATE ASSIGN REJECT to a mobile ontransmission or receipt of RESET by the MSC


Class : release





l1161/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 IMMEDIATEASSIGNREJECT to amobile due to alack of radio resource


Class : release





l1161/2 Number of immediate assignments rejected: CHANNEL

ACTIVATE NACK received

Name Q3 : immediateAssignmentRejectChanActNack

Object : bts

Function : number of immediate assignments rejected because a CHANNELACTIVATE NACK message is received



Event : transmission of IMMEDIATE ASSIGN REJECT to a mobile onreceipt of CHANNEL ACTIVATE NACK from the BTS


Class : release






l1161/3 Number of immediate assignments rejected: Time-out elapse

Name Q3 : immediateAssignmentRejectChanActTimmack

Object : bts

Function : number of immediate assignments rejected because of TimmAcktime-out elapse

Event : transmission of IMMEDIATE ASSIGN REJECT to a mobile onTchnAck time-out elapse


Class : release






l1161/5 Number of immediate assignments rejected: Traffic overload

Name Q3 : immediateAssignmentRejectOverload

Object : bts

Function : number of immediate assignments rejected for overload reasons


PE/DCL/DD/0125411--9001--125


Event : transmission of IMMEDIATEASSIGNREJECT to amobile becausea call originating from amobile (MOC) or aMobile Terminating Call(MTC) is blocked by the BSC for traffic management generaloverload


Class : release





l1161/6 Number of immediate assignments rejected: Excessive timing

advanceName Q3 : immediateAssignmentRejectTimingAdv

Object : bts

Function : number of immediate assignments rejected for distance reasons

Event : receipt of CHANNEL REQUIRED with a timing advance valueabove the O&M threshold (no IMMEDIATE ASSIGN REJECT issent to the mobile)


Class : release





l1161/7 Number of immediate assignments rejected: Other casesName Q3 : immediateAssignmentRejectOthers

Object : bts

Function : number of immediate assignments rejected for other reasons



Event : transmission of IMMEDIATE ASSIGN REJECT to a mobile foranother reason


Class : release






l1162/0 Number of SCCP releases before HANDOVER REQUEST

acknowledging: SCCP disconnection

Name Q3 : signallingReleaseNoBtsSccpDiscInd

Object : bsc

Function : number of communications in signaling phase released beforeHANDOVER REQUEST ACKNOWLEDGE is received in theincoming handover procedure, because of SCCP disconnection

Event : receipt of SCCP DISCONNECTION INDICATION from the MSC


Class : release






Note : This counter is only incremented in case of incoming externalhandovers.


PE/DCL/DD/0125411--9001--125



acknowledging: Reset

Name Q3 : signallingReleaseNoBtsReset

Object : bsc

Function : number of communications in signaling phase released beforeHANDOVER REQUEST ACKNOWLEDGE is received in theincoming handover procedure, because of reset

Event : receipt of RESET from the MSC


Class : release








acknowledging: SCCP DATA REFUSAL received

Name Q3 : signallingReleaseNoBtsSccpDataRefusal

Object : bsc

Function : number of communications in signaling phase released beforeHANDOVER REQUEST ACKNOWLEDGE is received in theincoming handover procedure, because of SCCP data refusal

Event : receipt of SCCP DATA REFUSAL from the MSC


Class : release









acknowledging: TsccRel elapseName Q3 : signallingReleaseNoBtsTsccRel

Object : bscFunction : number of communications in signaling phase released before

HANDOVER REQUEST ACKNOWLEDGE is received in theincoming handover procedure, because of TsccRel time-out elapse

Event : TsccRel time-out elapse


Class : releaseSource : recorded by the BSC






acknowledging: Incorrect DATA INDICATION receivedName Q3 : signallingReleaseNoBtsBadDataInd

Object : bscFunction : number of communications in signaling phase released before

HANDOVER REQUEST ACKNOWLEDGE is received in theincoming handover procedure, because of incorrect DATAINDICATION message received


PE/DCL/DD/0125411--9001--125


Event : receipt of DATA INDICATION other than HANDOVERREQUESTafter receipt of SCCP CONNECTION INDICATION


Class : release








acknowledging: Other cases

Name Q3 : signallingReleaseNoBtsOthers

Object : bsc

Function : number of communications in signaling phase released beforeHANDOVER REQUEST ACKNOWLEDGE is received in theincoming handover procedure for other reasons

Event : call in signaling phase released for another reason


Class : release









l1163/0 Number of communications in signaling phase released: SCCP

disconnection

Name Q3 : signallingReleaseBtsSccpDiscInd

Object : bts

Function : number of communications in signaling phase released because ofSCCP disconnection when a cell is associated with thecommunication



Class : release





l1163/1 Number of communications in signaling phase released: Reset

Name Q3 : signallingReleaseBtsReset

Object : bts

Function : number of communications in signaling phase released because ofreset when a cell is associated with the communication



Class : release






PE/DCL/DD/0125411--9001--125


l1163/2 Number of communications in signaling phase released: Reset

circuit downlink

Name Q3 : signallingReleaseBtsResetCirc

Object : bts

Function : number of communications in signaling phase released because ofreset circuit in the Downlink direction when a cell is associated withthe communication

Event : receipt of RESET CIRCUIT DOWNLINK from the MSC


Class : release





l1163/3 Number of communications in signaling phase released: SCCP

DATA REFUSAL received

Name Q3 : signallingReleaseBtsSccpDataRefusal

Object : bts

Function : number of communications in signaling phase released because ofSCCP data refusal when a cell is associated with the communication



Class : release







l1163/4 Number of communications in signaling phase released:

Incorrect First L3 Msg

Name Q3 : signallingReleaseBtsIncFirstL3

Object : bts

Function : number of communications in signaling phase released because ofincorrect First L3 message when a cell is associated with thecommunication

Event : incorrect syntax of a First L3 message or message different from CMSERVING REQUEST, PAGING RESPONSE, LOCATIONUPDATINGREQUEST, CMREESTABLISHMENT REQUEST, orIMSI DETACH


Class : release






l1163/5 Number of communications in signaling phase released: T3101

elapse

Name Q3 : signallingReleaseBtsT3101

Object : bts

Function : number of communications in signaling phase released because ofT3101 time-out elapse when a cell is associated with thecommunication

Event : T3101 time-out elapse before ESTABLISH INDICATION isreceived in the immediate assignment procedure


Class : release



PE/DCL/DD/0125411--9001--125







elapse

Name Q3 : signallingReleaseBtsT3107CircDown

Object : bts

Function : number of communications in signaling phase released because ofT3107 time-out elapse when a cell is associated with thecommunication

Event : T3107 time-out elapse before ESTABLISH INDICATION isreceived in the dedicated channel assignment or intra-bts handover onSDCCH procedure


Class : release






l1163/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 theassociated with the call is taken out of service



Event : radio time slot withdrawal due to the cell being taken out of service


Class : release





l1163/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 afaulty equipment when a cell is associated with the call

Event : radio time slot withdrawal due to a faulty equipment (PCM, etc.)


Class : release





l1163/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 aterrestrial circuit is taken out of service when a cell is associated withthe communication


PE/DCL/DD/0125411--9001--125


Event : CICwithdrawal due to the terrestrial circuit being taken out of service


Class : release





l1163/10 Number of communications in signaling phase released: CIC out

of service (faulty equipment)

Name Q3 : signallingReleaseBtsCicRemovalEqptFail

Object : bts

Function : number of communications in signaling phase released because of afaulty equipment when a cell is associated with the communication

Event : CIC withdrawal due to a faulty equipment (PCM, etc.)


Class : release





l1163/11 Number of communications in signaling phase released: Radio

channel blocked (O&M)

Name Q3 : signallingReleaseBtsOmRadioChanBloc

Object : bts

Function : number of communications in signaling phase released because ofradio channel blocking when a cell is associated with thecommunication



Event : radio channel blocking by O&M action


Class : release





l1163/12 Number of communications in signaling phase released: CALL

CLEARING receivedName Q3 : signallingReleaseBtsCallClearing

Object : bts

Function : number of communications in signaling phase released because ofcall clearing when a cell is associated with the communication

Event : receipt of CALL CLEARING because the maximum authorizeddistance is exceeded


Class : release






interface failureName Q3 : signallingReleaseBtsCnxFailRadioIntFail

Object : bts

Function : number of communications in signaling phase released because ofradio interface failures when a cell is associated with thecommunication


PE/DCL/DD/0125411--9001--125


Event : receipt of CONNECTIONFAILURE INDICATIONwith Abis cause“radio interface failure”


Class : release







link failure

Name Q3 : signallingReleaseBtsCnxFailRadioLinkFail

Object : bts

Function : number of communications in signaling phase released because ofradio link failures when a cell is associated with the communication

Event : receipt of CONNECTIONFAILURE INDICATIONwith Abis cause“radio link failure”


Class : release








1163/16 Number of communications in signaling phase released:RELEASE INDICATION received

Name Q3 : signallingReleaseBtsReleaseInd

Object : bts

Function : number of communications in signaling phase released because ofRELEASE INDICATION received when a cell is associated with thecommunication

Event : receipt of RELEASE INDICATION from the BTS


Class : release



This counter is incremented when the BSC receives a RELEASEINDICATION on a channel and the channel is not in a release phase.

Thatmeans that onA interface, no disconnection has been started (noCLEAR COMMAND received nor SCCP disconnection).

The RELEASE INDICATIONmessage sent by the BTS is due to thereception of a DISC frame (LAPDm message) by the BTS from themobile (MS).

In the Nortel Networks implementation:

At the BTS level, each time a LAPDmDISC frame is received by theBTS, a message RELEASE INDICATION is sent by the BTS to theBSC, unless the link layer is in idle mode (as indicated inrecommendation 08.58).

At the BSC level, in normal release scenario, the counter 1163/16 isnot incremented. In all other cases, the counter 1163/16 isincremented.

So, the counter C1163/16 takes into account each RELEASEINDICATION message sent on the SDCCH channel from the BTSwhen the BSC is in a state where it has not send to this BTS a RRCHANNEL RELEASE (triggered by the reception of BSSMAPCLEAR COMMAND from the MSC).


PE/DCL/DD/0125411--9001--125






Exception conditions : channel in a release phase

Data flows : The following data flow presents the links between signallingmessages 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 betweensignallingmessages exchanged at RR level (between theBSS and themobile) in normal release scenario:

MS BTS BSC MSC

BSSMAP CLEAR COMMANDRR 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


elapse

Name Q3 : signallingReleaseBtsErrorIndT200

Object : bts

Function : number of communications in signaling phase released because ofT200 time-out elapse in the cell associated with the communication

Event : receipt of ERROR INDICATION: T200 elapsed (N200 + 1) times


Class : release



PE/DCL/DD/0125411--9001--125



This counter is related to the Layer2 LAPDm protocol (errordetection + repetition protocol between the BTS and the mobile(MS)).

When a Layer 2 frame is not acknowledged by the MS before T200expiration, the BTS sends an Error indicationmessage to the BSC.After (N200+1)Error indication consecutivemessages received fora call in signaling phase, the BSC increments by one the counter1163/17.




Data flows : The dataflow below presents an example of Layer 2 LAPDmexchange. 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

frame2

frame2

Error indicationN200 + 1 error indication + C1163/17T200 expiration

Error indicationT200 expiration


The Layer 2 exchange begins with a exchange of an SABM (SetAsynchronous Balanced mode) and UA (UnnumberedAcknowledge) frames.



The frame1 is acknowledged so it has being received correctly by theMS and the BTS has received the acknowledgement of that.The frame2 is not acknowledged either because theMSwas not beingable to decode it or because the BTS could not receive theacknowledgment.The counter C1163/17 is usually linked to radio bad quality (ULor DL).

l1163/18 Number of communications in signaling phase released: DM

errorName Q3 : signallingReleaseBtsErrorIndDm

Object : bts

Function : number of communications in signaling phase released because ofDM frames received in established multiframe mode when a cell isassociated with the communication

Event : receipt of ERROR INDICATION: DM frame received in establishedmultiframe mode


Class : release





1163/19 Number of communications in signaling phase released:Sequencing error

Name Q3 : signallingReleaseBtsErrorIndSeq

Object : bts

Function : number of communications in signaling phase released because ofsequencing errors when a cell is associated with the communication

Event : receipt of ERROR INDICATION: sequencing error


Class : release



PE/DCL/DD/0125411--9001--125






l1163/20 Number of communications in signaling phase released: CLEAR

COMMAND received

Name Q3 : signallingReleaseBtsClearCommand

Object : bts

Function : number of communications in signaling phase released because ofCLEAR COMMAND received when a cell is associated with thecommunication

Event : receipt of CLEARCOMMAND from theMSC on normal end of callor outgoing inter-bss handover


Class : release









DFD “Connection clearing required by the MSC procedure(communication on SIGNALLING phase)”




l1163/21 Number of communications in signaling phase released: RF

RESOURCE INDICATION receivedName Q3 : signallingReleaseBtsRfResInd

Object : bts

Function : number of communications in signaling phase released because of RFRESOURCE INDICATION received when a cell is associated withthe communication

Event : receipt of three RF RESOURCE INDICATION messages


Class : release





l1163/22 Number of communications in signaling phase released: BSC

chain switchover

Name Q3 : signallingReleaseBtsSwitchOver

Object : bts

Function : number of communications in signaling phase released because ofBSC chain switchovers when a cell is associated with thecommunication

Event : BSC chain switchover on receipt of ESTABLISH INDICATION


Class : release






PE/DCL/DD/0125411--9001--125


l1163/23 Number of communications in signaling phase released: Double

TmodMs elapse

Name Q3 : signallingReleaseBtsTmodMs

Object : bts

Function : number of communications in signaling phase released because ofdouble TmodMs time-out elapse in theCHANNELMODEMODIFYprocedure when a cell is associated with the communication

Event : double TmodMs time-out elapse


Class : release







elapse


Object : bts

Function : number of communications in signaling phase released because ofT3103 time-out elapse in the handover procedure when a cell isassociated with the communication

Event : T3103 time-out elapse


Class : release








elapse


Object : bts

Function : number of communications in signaling phase released because of T8time-out elapse in the inter-bss handover procedure when a cell isassociated with the communication



Class : release





l1163/28 Number of communications in signaling phase released: Other

cases

Name Q3 : signallingReleaseBtsOthers

Object : bts

Function : number of communications in signaling phase released for otherreasons when a cell is associated with the communication

Event : communication in signaling phase released for another reason


Class : release



PE/DCL/DD/0125411--9001--125






elapseName Q3 : signallingReleaseBtsT11

Object : bts

Function : number of communications in signaling phase released because ofT11 time-out elapse in the queuing procedurewhen acell is associatedwith the communication

Event : T11 time-out elapse during the queuing procedure


Class : release





l1163/32 Number of communications in signaling phase released: TCU

failureName Q3 : signallingReleaseBtsCnxFailRemTransFail

Object : bts

Function : number of communications in signaling phase released because of aTCU failure when a cell is associated with the communication

Event : receipt of CONNECTION FAILURE INDICATION with cause“remote transcoder failure”


Class : release







l1163/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” phaseand cell associated to the communication.

Event : TDMA removal due to a EDGE TRX/TDMA optimization


Class : release






l1164/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 SCCPdisconnection



Class : release



PE/DCL/DD/0125411--9001--125





l1164/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 resetfrom the MSC



Class : release






l1164/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 resetcircuit in the Downlink direction

Event : receipt of RESET CIRCUIT DOWNLINK from the MSC


Class : release







l1164/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 SCCPdata refusal



Class : release






l1164/6 Number of communications in traffic phase released: T3107

elapse

Name Q3 : trafficReleaseT3107CircDown

Object : bts

Function : number of communications in traffic phase releasedbecause ofT3107time-out elapse

Event : T3107 time-out elapse in the traffic establishment procedure


Class : release



PE/DCL/DD/0125411--9001--125





l1164/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 thecell being taken out of service

Event : radio time slot withdrawal due to the cell being taken out of service


Class : release






l1164/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 afaulty equipment

Event : radio time slot withdrawal due to a faulty equipment (PCM, etc.)


Class : release







l1164/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 aterrestrial circuit being taken out of service

Event : CICwithdrawal due to the terrestrial circuit being taken out of service


Class : release





l1164/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 releasedbecause of a faulty equipment. Creating a synthetic counter to workon a ration, not on absolute values.

Event : CIC withdrawal due to a faulty equipment (PCM, etc.)


Class : release



PE/DCL/DD/0125411--9001--125





l1164/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 radiochannel blocking

Event : radio channel blocking by O&M action


Class : release






l1164/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 callclearing

Event : receipt of a call clearing request


Class : release







l1164/13 Number of communications in traffic phase released: Radio

interface failureName Q3 : trafficReleaseCnxFailRadioIntFail

Object : bts

Function : number of communications in traffic phase released because of radiointerface failures

Event : receipt of CONNECTIONFAILURE INDICATIONwith Abis cause“radio interface failure”


Class : release





l1164/14 Number of communications in traffic phase released: Radio link

failureName Q3 : trafficReleaseCnxFailRadioLinkFail

Object : bts

Function : number of communications in traffic phase released because of radiolink failures

Event : receipt of CONNECTIONFAILURE INDICATIONwith Abis cause“radio link failure”


Class : release



PE/DCL/DD/0125411--9001--125






l1164/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 ofRELEASE INDICATION received

Event : receipt of RELEASE INDICATION from the BTS


Class : release



This counter is incremented when the BSC receives a RELEASEINDICATION on a channel and the channel is not in a release phase.

Thatmeans that onA interface, no disconnection has been started (noCLEAR COMMAND received nor SCCP disconnection).

The RELEASE INDICATIONmessage sent by the BTS is due to thereception of a DISC frame (LAPDm message) by the BTS from themobile (MS).

In the Nortel Networks implementation:

At the BTS level, each time a LAPDmDISC frame is received by theBTS, a message RELEASE INDICATION is sent by the BTS to theBSC, unless the link layer is in idle mode (as indicated inrecommendation 08.58).



At the BSC level, in normal release scenario, the counter 1164/16 isnot incremented. In all other cases, the counter 1164/16 isincremented.

So, the counter C1164/16 takes into account each RELEASEINDICATIONmessage sent on the TCHchannel from the BTSwhenthe BSC is in a state where it has not send to this BTS a RRCHANNEL RELEASE (triggered by the reception of BSSMAPCLEAR COMMAND from the MSC).




Data flows : The following data flow presents the links between signallingmessages 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 betweensignallingmessages exchanged at RR level (between theBSS and themobile) in normal release scenario:


PE/DCL/DD/0125411--9001--125


MS BTS BSC MSC

BSSMAP CLEAR COMMANDRR 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

l1164/17 Number of communications in traffic phase released: T200elapse

Name Q3 : trafficReleaseErrorIndT200

Object : bts

Function : number of communications in traffic phase released because of T200time-out elapse

Event : receipt of ERROR INDICATION: T200 elapsed (N200 + 1) times


Class : release



This counter is related to the Layer2 LAPDm protocol (errordetection + repetition protocol between the BTS and the mobile(MS)).



When a Layer 2 frame is not acknowledged by the MS before T200expiration, the BTS sends an Error indicationmessage to the BSC.After (N200+1)Error indication consecutivemessages received fora call in traffic phase, the BSC increments by one the counter1164/17.




Data flows : The dataflowbelowpresents an exampleof Layer 2 LADmexchange.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

frame2

frame2

Error indicationN200 + 1 error indication + C1164/17T200 expiration



The Layer 2 exchange begins with a exchange of an SABM (SetAsynchronous Balanced mode) and UA (UnnumberedAcknowledge) frames.

The frame1 is acknowledged so it has being received correctly by theMS and the BTS has received the acknowledgement of that.The frame2 is not acknowledged either because theMSwas not beingable to decode it or because the BTS could not receive theacknowledgment.

The counter C1164/17 is usually linked to radio bad quality (UL orDL).


PE/DCL/DD/0125411--9001--125


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 DMframes received in established multiframe mode

Event : receipt of ERROR INDICATION: DM frame received in establishedmultiframe mode


Class : release






l1164/19 Number of communications in trafficphase released: Sequencing

error

Name Q3 : trafficReleaseErrorIndSeq

Object : bts

Function : number of communications in traffic phase released because ofsequencing errors

Event : receipt of ERROR INDICATION: sequencing error


Class : release







l1164/20 Number of communications in traffic phase released: CLEAR

COMMAND receivedName Q3 : trafficReleaseClearCommand

Object : bts

Function : number of communications in traffic phase released because ofCLEAR COMMAND received

Event : receipt of CLEARCOMMAND from theMSC on normal end of callor outgoing inter-bss handover


Class : release





Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “Connection clearing required by the MSC procedure(communication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”

l1164/21 Number of communications in traffic phase released: RF

RESOURCE INDICATION receivedName Q3 : trafficReleaseRfResInd

Object : bts

Function : number of communications in traffic phase released because of RFRESOURCE INDICATION received

Event : receipt of three RF RESOURCE INDICATION messages


Class : releaseSource : recorded by the BSC


PE/DCL/DD/0125411--9001--125





l1164/23 Number of communications in traffic phase released: TmodMs

elapse

Name Q3 : trafficReleaseTmodMs

Object : bts

Function : number of communications in traffic phase released because ofTmodMs time-out elapse

Event : double TmodMs time-out elapse in theCHANNELMODEMODIFYprocedure


Class : release





l1164/24 Number of communications in traffic phase released: T3103

elapse

Name Q3 : trafficReleaseT3103

Object : bts

Function : number of communications in traffic phase releasedbecause ofT3103time-out elapse

Event : T3103 time-out elapse in the handover procedure


Class : release








l1164/25 Number of communications in traffic phase released: T8 elapse

Name Q3 : trafficReleaseT8

Object : bts

Function : number of communications in traffic phase released because of T8time-out elapse

Event : T8 time-out elapse in the inter-bss handover procedure


Class : release






l1164/28 Number of communications in traffic phase released:Other cases

Name Q3 : trafficReleaseOthers

Object : bts

Function : To list the number of communications in traffic phase releasedbecause of lack of Ater uplink TRAU frame synchronization. Thesecounters are the indications of a loss of frame synchronization eitherbecause of a loopback on the transmission line, or poor quality of thebackhaul facilities.


PE/DCL/DD/0125411--9001--125


Event : Receipt of a Release Indicationmessage from the TCUwith cause setto ”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.





Mechanism of Counter

This is managed by the TCUe3; A TRAU can be in one of two states,Idle or Active, and is considered to be synchronized, depending on itsstate, 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 mechanismis triggered when an idle TRAU, which is ”synchronized” on a PCMidlepattern, looses this synchronization.At the loss of synchronizationdetection, the TRAU starts the ”begin_com_ater_sync” timer. Thistimer is stopped in following cases:

The PCM idle pattern is detected. In this case the TRAUreturns to the idle state.

An uplink TRAU frame supported by this TRAU isreceived.

In case of ”begin_com_ater_sync” timer expiry, the fault is notified tothe BSC and the call is released. (The timer is set to 6 seconds.)

For Circuit data calls only, there is a similar mechanism to supervisethe 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 aloss of synchronization is detected on the uplink ATER interface, thenthe ”in_com_ater_sync” timer is started. This timer is stopped in thefollowing cases:

The PCM idle pattern is detected. In this case the TRAUreturns to the idle state.

An uplink TRAU frame supported by this TRAU isreceived.

In case of ”in_com_ater_sync” timer expiry, the fault is notified to theBSC and the call is released. (The timer is set to 6 seconds.)

For Circuit data calls only, there is a similar mechanism to supervisethe 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 e3 sends to theBSCaRelease Indicationmessage (cause= ”Synchro trame error”).Atreception of this message, the BSC:

Releases the communication to quickly stop the billingthanks to a Clear Request An interface message [R2] with standardcause: ”equipment failure” and all radio resources are released.

Increments the C1164/28 counters to in order to provide athreshold 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 :

BSCe3 Notifications:On the BSCe3, an anomaly is recorded for each kind of call drop:

5620 for calls dropped by theTCU (recorded once per 20drops)

5621 for calls dropped by the BTS (recorded once per100 drops)


PE/DCL/DD/0125411--9001--125


To check for these errors, retrieve from theBSC the fault files locatedin /OMU/share/fault (with the .txt extension) for the relevant days.Please contact GNTS to get these files and analyze them.

Common Causes:

Failing PCMor Timeslot in the path between theBTS andTCU.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 BSCE3/TCU/MSC-- V15.0 using a ”display dynamic data” on BSCe3 and onTCUe3 objects.-- Prior to V15.0, using notifications 2019.

ATER PCMs are crossed. Often seen in cases where 1164/28 isincremented: Check that the ATER PCMs are not crossed.

Note: in the vast majority of cases an increase in counters 1164/28 and1164/32 is due to PCM quality issues.

Isolation and Diagnosis:

The problem could be caused by theABIS orATERPCM, (or theBSC), andmay affect an entire PCM or, one or more individual Timeslots. Each64Kbps ABIS PCM timeslot is divided into four 16Kbps sub--channels.Therefore each TDMA, consisting of 8 channels, uses two adjacent ABIS64Kbps TS.

The mapping of Radio Channels to ABIS Timeslot is:

ABISTimeslot X X X X Y Y Y Y

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 BSCe3



logs in order to determine which PCMs, Timeslots and Channels areaffected.:

a. Look for reoccurring instances of the same PCM and/orTimeslot.

b. Verify if most commonly failing PCM is an ATER or ABISPCM.

c. For the failing PCM, check which 16Kbps sub--channels areimpacted: Is it all 4 sub--channels associated with onetimeslot, or only 1 or 2 sub--channels?

2. Check for any PCMrelated notifications for thePCM’s found instep 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 intermediateequipment such as a DACS:

a. Check the DACS board that manages the PCM and the DACSconfiguration.

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 sourceofthe problem. Note that, depending on the type of DACS, it mayre--frame the signal, which would tend to ”mask” alarms andsome types of errors (slips, notably).

c. All transmission facilities should be configured to useappropriate zero--code suppression (i.e., B8ZS for DS1facilities).

5. Using suitable test equipment, perform end--to--end quality testof failing PCM.( i.e. BERT test etc). Ensuring that all Timeslotsare checked.

6. If the failing PCM’s are associated with the same LSA performa SWACT of the associated IEM.

NOTES:

If layer 1 does not detect a fault, (for example a looped PCM) and there is noLAPD carried on the failing timeslot(s), then there may be no otherindication 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


PE/DCL/DD/0125411--9001--125


and incrementing 1164/32, therefore it is not unusual to see both countersincrementing.

Due to the fact that the call is dropped after 6 secs it can be difficult toidentify a failing PCM/TS in real--time.

l1164/31 Number of communications in traffic phase released: SYS INFO

problem

Name Q3 : trafficReleaseSysInfoFail

Object : bts

Function : To list the number of communications in traffic phase releasedbecause the SYS INFO procedure is aborted following a BSC chainswitchover.

Event : SYS INFO procedure aborted following a BSC chain switchover


Class : release






l1164/32 Number of communications in traffic phase released: TCU

failure

Name Q3 : trafficReleaseCnxFailRemTransFail

Object : bts

Function : To list the number of communications in traffic phase releasedbecause of lack of Abis downlink TRAU frame synchronization.Creating a synthetic counter to work on a ration, not on absolutevalues. These counters are the indications of a loss of framesynchronization 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.





Mechanism of Counter

The BTS is synchronized when the following frames are received onthe 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 thefollowing cases:

Frameswithout any correct synchronization pattern sinceV12.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 acommunication, it starts a timer Tsync (1Sec).

If the frame synchronization is obtained before the Tsync expires, nosignalization 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 thecircuitSynchroTimer expires, no signalization occurs.


PE/DCL/DD/0125411--9001--125


If timer circuitSynchroTimer expires before frame synchronization isobtained, the BTS sends a ’Connection Failure Indication’ RSLmessage with the cause: remote transcoder failure (this cause is astandard cause, described inGSM05.58, which is used in some scarcecases for transcoder failure, but most often for backhaul errordetection).

When the BSC receives this message it will:Release the call with a Clear Request: An interface

message with standard cause: ’equipment failure’Set a new internal TCH flag ”circuit failure detection

release” to truePut the TCH into the pool of worst interference level,

whatever its level before the allocation, and increment the cellcounter: Traffic_Release C1164/32

Detection process :

BSCe3 Notifications:On the BSCe3, an anomaly is recorded for each kind of call drop:

5620 for calls dropped by theTCU (recorded once per 20drops)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. Pleasecontact GNTS to get these files and analyze them.

Common Causes:

Failing PCM or Timeslot in the path between the TCU and theBTS.

Note: in the vast majority of cases an increase in counters 1164/28 and1164/32 is due to PCM quality issues.

Isolation and Diagnosis:

The problem could be caused by theABIS orATERPCM, (or theBSC), andmay affect an entire PCM or, one or more individual Timeslots. Each64Kbps 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:

ABISTimeslot X X X X Y Y Y Y

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 BSCe3logs in order to determine which PCMs, Timeslots and Channels areaffected.:

a. Look for reoccurring instances of the same PCM and/orTimeslot.

b. Verify if most commonly failing PCM is an ATER or ABISPCM.

c. For the failing PCM, check which 16Kbps sub--channels areimpacted: Is it all 4 sub--channels associated with onetimeslot, or only 1 or 2 sub--channels?

2. Check for any PCMrelated notifications for thePCM’s found instep 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 intermediateequipment such as a DACS:

a. Check the DACS board that manages the PCM and the DACSconfiguration.

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 sourceofthe problem. Note that, depending on the type of DACS, it mayre--frame the signal, which would tend to ”mask” alarms andsome types of errors (slips, notably).

c. All transmission facilities should be configured to useappropriate zero--code suppression (i.e., B8ZS for DS1


PE/DCL/DD/0125411--9001--125


facilities).5. Using suitable test equipment, perform end--to--end quality test

of failing PCM.( i.e. BERT test etc). Ensuring that all Timeslotsare checked.

6. If the failing PCM’s are associated with the same LSA performa SWACT of the associated IEM.

NOTES:

If layer 1 does not detect a fault, (for example a looped PCM) and there is noLAPD carried on the failing timeslot(s), then there may be no otherindication 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 problemand incrementing 1164/32, therefore it is not unusual to see both countersincrementing.

Due to the fact that the call is dropped after 6 secs it can be difficult toidentify a failing PCM/TS in real--time.

l1164/33 Numberof releaseswhile 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








l1165 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 ofTchoke timer active

Event : receipt of HANDOVER INDICATION while the Tchoke timer isrunning


Class : handover







Name Q3 : hoIndicationNotTreatedTmtBtwHo

l1167 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 TCHtowards a cell that is not heading the list of eligible cells withoutreestablishment in the current serving cell

Event : receipt of HANDOVER FAILURE on T3103 time-out elapse


Class : handover



PE/DCL/DD/0125411--9001--125





Note : the list is reorganized by the BSC since Ho decision function. It maynot be the same order as the one received from the L1M

l1168 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 SDCCHtowards a cell that is not heading the list of eligible cells withoutreestablishment in the current serving cell

Event : receipt of HANDOVER FAILURE on T3103 time-out elapse


Class : handover






l1169 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 TCHtowards a cell that is not heading the list of eligible cells withoutreestablishment in the current serving cell



Event : T3103 time-out elapse or receipt of CLEAR COMMAND with acause different from “Handover successful” or “Call Control”


Class : handover







l1170 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 SDCCHtowards a cell that is not heading the list of eligible cells withoutreestablishment in the current serving cell

Event : T3103 time-out elapse or receipt of CLEAR COMMAND with acause different from “Handover successful” or “Call Control”


Class : handover








PE/DCL/DD/0125411--9001--125


l

1172/0 Number of fallbacks from a data rate to other data rates for TCBlack of resources cause

Name Q3 : dataNtRateFbTcbResLack

Object : bsc

Function : number of fallbacks from a data rate to other data rates for TCB lackof resources cause

Event : response from terrestrial allocator


Class : A interface





l

1172/1 Number of fallbacks from a data rate to other data rates for nonallowed TCB configuration cause

Name Q3 : dataNtRateFbTcbConfNotAllowed

Object : bsc

Function : number of fallbacks from a data rate to other data rates for nonallowed TCB configuration cause

Event : configuration mismatch


Class : A interface







l1191/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 casesPhase II = location update request (0000), other procedures usingan SDCCH (0001)


Class : setup





Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “Immediate assignment procedure (normal completion)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “SMS procedure (SMS established by the MS)”



Object : bts


Event : receipt of CHANNEL REQUIRED:Phase I = nonsignificantPhase II = reply to a paging request


Class : setup



PE/DCL/DD/0125411--9001--125






l1191/2 Number of channel allocation requests: Cause 010Name Q3 : channelRequestCause010

Object : btsFunction : number of channel allocation requests in the cell with cause 010Event : receipt of CHANNEL REQUIRED:

Phase I = nonsignificantPhase II = transmission of speech (0100) or data (0101) on aTCH/FR by a mobile


Class : setupSource : recorded by the BSCPreciseincrementation conditions :








Object : bts


Event : receipt of CHANNEL REQUIRED:Phase I = nonsignificantPhase II = call reestablishment on a TCH/FR


Class : setup









Object : bts


Event : receipt of CHANNEL REQUIRED for a reply to a paging request


Class : setup



PE/DCL/DD/0125411--9001--125









Object : bts


Event : receipt of CHANNEL REQUIRED for an emergency call


Class : setup











Object : bts


Event : receipt of CHANNEL REQUIRED for a call reestablishment


Class : setup







DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “Immediate assignment procedure (normal completion)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “SMS procedure (SMS established by the MS)”



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



PE/DCL/DD/0125411--9001--125







DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”

DFD “Immediate assignment procedure (normal completion)”

DFD “Immediate assignment paging procedure (normalcompletion)”

DFD “SMS procedure (SMS established by the MS)”

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 ofCHANNEL REQUEST with the following cause:

Phase I = all other cases

Phase II = location update request (0000), other procedures usingan SDCCH (0001)


Class : setup








Data flows : Refer to Chapter 1DFD “Immediate assignment procedure (normal completion)”DFD “GPRS procedure preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “SMS procedure (SMS established by the MS)”

l1192/1 Number of successful immediate assignments: Cause 001


Object : bts


Event : transmission of IMMEDIATE ASSIGNMENT with the followingcause:

Phase I = nonsignificantPhase II = reply to a paging request


Class : setup








PE/DCL/DD/0125411--9001--125




Object : bts



Phase I = nonsignificant

Phase II = transmission of speech (0100) or data (0101) on aTCH/FR by a mobile


Class : setup








DFD “GPRS procedure preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”






Object : bts





Phase I = nonsignificant

Phase II = call reestablishment on a TCH/FR


Class : setup














Object : bts


Event : transmission of IMMEDIATE ASSIGNMENT on receipt ofCHANNEL REQUEST with cause “paging request”


Class : setup



PE/DCL/DD/0125411--9001--125















Object : bts


Event : transmission of IMMEDIATE ASSIGNMENT on receipt ofCHANNEL REQUEST with cause “emergency call”


Class : setup

















Object : bts


Event : transmission of IMMEDIATE ASSIGNMENT on receipt ofCHANNEL REQUEST with cause “call reestablishment”


Class : setup













PE/DCL/DD/0125411--9001--125




Object : bts


Event : transmission of IMMEDIATE ASSIGNMENT on receipt ofCHANNEL 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







l1193/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 onSDCCH or TCH if no SDCCH is available, for replies to pagingrequests



Event : receipt of ESTABLISH INDICATION for a reply to a paging request


Class : setup





Data flows : Refer to Chapter 1DFD “Immediate assignment procedure (normal completion)”DFD “GPRS procedure preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “Dedicated channel assignment modify procedure (normalcompletion)”


establishment phase received for location updates

Name Q3 : estabIndicSignallingLocUpdate

Object : bts

Function : number of ESTABLISH INDICATION messages received onSDCCH or TCH if no SDCCH is available, for location updaterequests

Event : receipt of ESTABLISH INDICATION for a location update request


Class : setup






PE/DCL/DD/0125411--9001--125






DFD “Dedicated channel assignment modify procedure (normalcompletion)”


establishment phase received for call reestablishments

Name Q3 : estabIndicSignallingReEstab

Object : bts

Function : number of ESTABLISH INDICATION messages received onSDCCH or TCH in primo-allocations, for call reestablishments

Event : receipt of ESTABLISH INDICATION for a call reestablishment


Class : setup














establishment phase received for IMSI detachments

Name Q3 : estabIndicSignallingImsiDetach

Object : bts

Function : number of ESTABLISH INDICATION messages received onSDCCH or TCH if no SDCCH is available, for IMSI detachments

Event : receipt of ESTABLISH INDICATION for an IMSI detach request


Class : setup







establishment phase received for mobile originating calls

Name Q3 : estabIndicSignallingMoc

Object : bts

Function : number of ESTABLISH INDICATION messages received onSDCCH or TCH if no SDCCH is available, for mobile originatingcalls

Event : receipt of ESTABLISH INDICATION for a mobile originating call


Class : setup



PE/DCL/DD/0125411--9001--125













establishment phase received for urgent calls

Name Q3 : estabIndicSignallingEmergency

Object : bts

Function : number of ESTABLISH INDICATION messages received onSDCCH or TCH if no SDCCH is available, for emergency calls

Event : receipt of ESTABLISH INDICATION for an emergency call


Class : setup











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








PE/DCL/DD/0125411--9001--125



establishment phase received for other services

Name Q3 : estabIndicSignallingSuppService

Object : bts

Function : number of ESTABLISH INDICATION messages received onSDCCHor TCH if no SDCCH is available, for supplementary service

Event : receipt of ESTABLISH INDICATION for a supplementary service


Class : setup







1193/8 Number of ESTABLISH INDICATION messages inestablishment phase with notification message piggybacked

Name Q3 : estabIndicSignallingPiggybacked

Object : bts

Function : number of notification response messages piggybacked in theESTABLISHMENT_INDICATION message.

Event : receipt of ESTABLISHMENT_INDICATION message with anotification response message piggybacked.


Class : setup









l1195 Number of ESTABLISH INDICATION messages in

establishment phase received for Phase I mobiles

Name Q3 : estabIndicSigPhase1

Object : bts

Function : number of ESTABLISH INDICATION messages received onSDCCH, or TCH in primo-allocations, or TCH if no SDCCH isavailable, for Phase I mobiles

Event : receipt of ESTABLISH INDICATION for a Phase I mobile


Class : setup






Data flows : Refer to Chapter 1DFD “Immediate assignment procedure (normal completion)”DFD “GPRS procedure preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “Dedicated channel assignment modify procedure (normalcompletion)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”


PE/DCL/DD/0125411--9001--125


l1196 Number of ESTABLISH INDICATION messages in

establishment phase received for Phase II mobiles

Name Q3 : estabIndicSigPhase2

Object : bts

Function : number of ESTABLISH INDICATION messages received onSDCCH, or TCH in primo-allocations, or TCH if no SDCCH isavailable, for Phase II mobiles

Event : receipt of ESTABLISH INDICATION for a Phase II mobile


Class : setup






l1197/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 inthe cell for the observation period

Event : transmission of CHANNEL ACTIVATE or MODE MODIFY withCHANNEL MODE = “speech”


Class : assignment







Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”

l1197/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,activated in the cell for the observation period



Class : assignment






PE/DCL/DD/0125411--9001--125




DFD “dedicated channel assignment procedure (normalcompletion)”

DFD “queuing of the assignment procedure (normal completion)




DFD “Direct retry handover procedure”

l1198 Duration ofmaximumDownlink power use on busy TCH/FRs or

preempted PDTCHs

Name Q3 : downlinkPowerCtrlMaxTchMoydownlinkPowerCtrlMaxTchMax Maximum durationdownlinkPowerCtrlMaxTchCum Total durationdownlinkPowerCtrlMaxTchEch Number of samples

Object : bts

Function : average duration ( = total duration divided by the number of samples)and maximum duration of maximumDownlink power use on the cellTCH/FRs or preempted PDTCHs in the observation period

Event : start/end of maximum TCH Downlink power use:

start: start timer

end:

• stop and read timer


• add it to the total of maximum Downlink power use durationson TCH/FRs or preempted PDTCHs in the observation period



Class : L1M








Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “queuing of the assignment procedure (normal completion)DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”

l1199 Duration of maximum Uplink power use on busy TCH/FRs or

preempted PDTCHs

Name Q3 : uplinkPowerCtrlMaxTchMoyuplinkPowerCtrlMaxTchMax Maximum duration. . . .uplinkPowerCtrlMaxTchCum Total duration. . . .uplinkPowerCtrlMaxTchEch Number of samples. . . . .

Object : bts

Function : average duration ( = total duration divided by the number of samples)and maximum duration of maximum Uplink power use on the cellTCH/FRs or preempted PDTCHs for the observation period

Event : start/end of maximum TCH Uplink power use:

start: start timer


PE/DCL/DD/0125411--9001--125


end:• stop and read timer• store its peak value• add it to the total of maximum Uplink power use durations onTCH/FRs or preempted PDTCHs in the observation period



Class : L1M






Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “queuing of the assignment procedure (normal completion)DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Radio channel release RELEASE INDICATION procedure(normal completion)”DFD “Radio channel release RELEASE INDICATION procedure(normal completion)”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”

l1200 Number of handovers on TCH executed

Name Q3 : hoNcellsExecution

Object : adjacentCellHandOver

Function : number of attempts to execute handovers on TCH from a serving cellto its neighbors



Event : receipt of HANDOVER COMMAND from the MSC (inter-bsshandover) or transmission of Abis HANDOVERCOMMAND to theserving cell (intra-bss handover)


Class : handover


Data flows : Refer to Chapter 1DFD “Inter--cell intra BSC handovers procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”

l1202 Number of handovers on SDCCH executed

Name Q3 : hoNcellsExecutionSdcch


Function : number of attempts to execute handovers on SDCCH from a servingcell to its neighbors

Event : receipt of HANDOVER COMMAND from the MSC (inter-bsshandover) or transmission of Abis HANDOVERCOMMAND to theserving cell (intra-bss handover)


Class : handover


l1204/0 Number of unsuccessful outgoing handoversonTCH:Back toold

channel

Name Q3 : hoNcellsUnsuccessTchChlR


Function : number of unsuccessful outgoing intra- and inter-bss handovers onTCH with the mobile returning to the old channel

Event : receipt of HANDOVERFAILUREbefore T3103 time-out elapse (theserving cell is unable to transfer the mobile to the new channel)


Class : handover



PE/DCL/DD/0125411--9001--125


l1204/1 Number of unsuccessful outgoing handovers on TCH: Time-out

elapse

Name Q3 : hoNcellsUnsuccessTchTimer


Function : number of unsuccessful outgoing intra- and inter-bss handovers onTCH because of T3103 time-out elapse



Class : handover


l1204/2 Number of unsuccessful outgoing handovers on TCH: Other

cases

Name Q3 : hoNcellsUnsuccessTchOther


Function : number of unsuccessful outgoing intra- and inter-bss handovers onTCH because of other reasons

Event : receipt of CLEARCOMMAND from theMSCwith a cause differentfrom “Handover successful” or “Call Control”


Class : handover


l1205/0 Number of unsuccessful outgoing handovers on SDCCH: Back to

old channel

Name Q3 : hoNcellsUnsuccessSdcchChlR


Function : number of unsuccessful outgoing intra- and inter-bss handovers onSDCCH with the mobile returning to the old channel

Event : receipt of HANDOVERFAILUREbefore T3103 time-out elapse (theserving cell is unable to transfer the mobile to the new channel)


Class : handover




l1205/1 Number of unsuccessful outgoing handovers on SDCCH:

Time-out elapse

Name Q3 : hoNcellsUnsuccessSdcchTimer


Function : number of unsuccessful outgoing intra- and inter-bss handovers onSDCCH because of T3103 time-out elapse



Class : handover


l1205/2 Number of unsuccessful outgoing handovers on SDCCH: Other

cases

Name Q3 : hoNcellsUnsuccessSdcchOther


Function : number of unsuccessful outgoing intra- and inter-bss handovers onSDCCH for other reasons

Event : receipt of CLEAR_COMMAND with a cause different from“Handover successful” or “Call Control” coming from the MSC


Class : handover


l1206/0 Number of handovers and assignment for which the initial

request in EFR speech algorithm is degraded into FR speechalgorithm

Name Q3 : speechAlgoFallBack

Object : bsc

Function : number of handovers and assignment for which the initial request inEFR speech algorithm is degraded into FR speech algorithm only incase of the BSC has a CIC bearing EFR and other CICs not bearingEFR and if all CICs bearing EFR are already allocated


PE/DCL/DD/0125411--9001--125


Event : receipt of ASSIGN REQUEST or HANDOVER REQUEST with aCIC and a speech coding algorithm incompatible


Class : assignment






Note : This counter is only incremented if Enhanced Full Rate is allowed inthe network.

l1206/1 Number of handovers or assignments in which the initial request

in EFR speech algorithm is degraded into FR speech algorithmfor AMR calls

Name Q3 : amrFrSpeechAlgoFallBack

Object : bsc

Function : Number of handovers or assignments in which the initial request inEFR speech algorithm is degraded into FR speech algorithm forAMRcalls



Event : This counter is incremented on the reception of anASSIGN_REQUEST or an HANDOVER_REQUEST with a CICincompatible with the speech coding algorithm. In the case where theBSC has got CIC bearing EFR and other CIC not bearing EFR and ifall CIC bearing EFR are already allocated


Class : assignment


Note : V14 counter

Name Q3 : speechAlgoFallBackCtm

l1207 Number of immediate assignments for multiband mobiles

Name Q3 : immediateAssignmentMultiband

Object : bts

Function : number of call establishments for multiband mobiles (externalincoming handover requests are not included)

Event : receipt of the first CLASSMARK_CHANGEmessage from amobilewith classmark 3 multiband data, whenEarly_Classmark_Sending_Controlled is “true”


Class : assignation







PE/DCL/DD/0125411--9001--125


l1208 Number of outgoing handovers requested by dualband mobiles

from the main frequency band to the second frequency band ofthe 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 frequencyband of the network

Event : attempt to select a cell that belongs to the second frequency band inthe list of eligible cells


Class : handover





Data flows : Refer to Chapter 1DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”

Note : The target resource is in the second frequency band whereas theoriginated resource is in the main frequency band of the network.

l1209 Number of successful outgoing handovers for dualband mobiles

from the main frequency band to the second frequency band ofthe network

Name Q3 : hoSuccessOutgoingMbandEbandMsDualb (V12)hoSuccessOutgoingMultiband (V10 & V11)

Object : bts

Function : number of successful outgoing, intra-bss or inter-bss handovers, onTCH, from the main frequency band to the second frequency band ofthe network



Event : receipt of CLEAR COMMAND with cause “handover successful”(inter-bss handover) or receipt of HANDOVER COMPLETE fromthe MS (intra-bss handover)


Class : handover







l1300 Number of I frames sent

Name Q3 : omcOutputIFrame

Object : bsc

Function : number of I (Information) frames sent by the BSC (local X.25Level 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






No distinction is made between RACH dedicated to Circuit Call orPacket Calls.


PE/DCL/DD/0125411--9001--125


l1301 Number of I frames receivedName Q3 : omcInputIFrame

Object : bsc

Function : number of I (Information) frames received by the BSC (local X.25Level 2)

Event : receipt of an I frame on the X.25 link by the BSC







l1302 Number of repeated I frames sentName Q3 : omcOutputRepeatedIFrame

Object : bsc

Function : number of repeated I (Information) frames sent by the BSC (localX.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









l1303 Number of repeated I frames receivedName Q3 : omcInputRepeatedIFrame

Object : bsc

Function : number of repeated I (Information) frames received by theBSC(localX.25 Level 2)

Event : receipt of a repeated I frame on the X.25 link by the BSC







l1304 Number of RNR frames sentName Q3 : omcOutputRnrFrame

Object : bsc

Function : number of RNR (Received NonReady) frames sent by the BSC (localX.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








PE/DCL/DD/0125411--9001--125


l1305 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








l1400 Average load of CPUM board

Name Q3 : prLoadCpumMoyprLoadCpumMax Maximum load of the CPUM. . . . . . . . . . . . . .boardprLoadCpumCum 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 percentand maximum load of the CPUM processor in the BSC for theobservation period



Event : detection of the CPUM processor activity:

activation of the “NULL” task: start timeractivation of another task:• stop and read timer• store its peak value• add it to the total number for the observation period• step up by one the number of samples


Class : equipment





This counter gives the real load of the processor. And the load of aBSC processor is impacted by GPRS messages treated by thisprocessor.

l1400 Average load of CPUE x board

Name Q3 : prLoadCpueMoyprLoadCpue1MoyprLoadCpue2MoyprLoadCpueMax Maximum load of the CPUE 0. . . . . . . . . . . . . .boardprLoadCpue1Max Maximum load of the CPUE 1. . . . . . . . . . . . .boardprLoadCpue2Max Maximum load of the CPUE 2. . . . . . . . . . . . .boardprLoadCpueCum 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


PE/DCL/DD/0125411--9001--125


Location :

Name Q3 Location

prLoadCpueMoy/Max/Cum/Ech CPUE--0

prLoadCpue1Moy/Max/Cum/Ech CPUE--1

prLoadCpue2Moy/Max/Cum/Ech CPUE--2

Function : average load (= total load / number of samples) expressed in percentand maximum load of the CPUE x processor in the BSC for theobservation period

Event : detection of the CPUE x processor activity:activation of the “NULL” task: start timeractivation of another task:• stop and read timer• store its peak value• add it to the total number for the observation period• step up by one the number of samples


Class : equipment





l1400 Average load of SICD<x> board

Name Q3 : prLoadSicd<x>MoyprLoadSicd<x>Max Maximum load of the SICD<x>. . . . . . . . . . . .boardprLoadSicd<x>Cum Total load of the SICD<x>. . . . . . . . . . .boardprLoadSicd<x>Ech Number of samples. . . . . . . . . . . .

Object : bsc



Location :

Name Q3 Location

prLoadSicd<x>Moy/Max/Cum/Ech SICD--<x>

Function : average load (= total load / number of samples) expressed in percentand maximum load of the SICD<x> processor in the BSC for theobservation period

Event : detection of the SICD<x> processor activity:activation of the “NULL” task: start timeractivation of another task:• stop and read timer• store its peak value• add it to the total number for the observation period• step up by one the number of samples


Class : equipment






l1500 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



PE/DCL/DD/0125411--9001--125









DFD “immediate assignment procedure (normal completion)”




l1501 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 DATAINDICATION


Class : A interface









Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “Immediate assignment procedure (normal completion)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “SMS procedure (SMS established by the MS)”DFD “SMS procedure (SMS established by the MSC)”

l1502 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 DATAREQUEST, or SCCP UNIT DATA REQUEST


Class : A interface





Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (no available resource for a PDTCHpreemption)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “immediate assignment procedure (normal completion)DFD “dedicated channel assignment procedure (normalcompletion)”DFD “dedicated channel assignment procedure (no Resourceavailable and queuing not activated)”


PE/DCL/DD/0125411--9001--125


DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “Dedicated channel assignment modify procedure (normalcompletion)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”DFD “SMS procedure (SMS established by the MS)”

l1503 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








Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (no available resource for a PDTCHpreemption)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “immediate assignment procedure (normal completion)DFD “dedicated channel assignment procedure (normalcompletion)”DFD “dedicated channel assignment procedure (no Resourceavailable and queuing not activated)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “Dedicated channel assignment modify procedure (normalcompletion)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”

l1504 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 theBTS

Event : transmission of a UPLINK_REQUEST message towards the MSC


Class : asci


Feature : GSM--R (V12)


PE/DCL/DD/0125411--9001--125



This counter is concerned by CCT (Circuit Calls on TCH channels)but not by CCP (Circuit Calls on PDTCH preempted to make a TCHchannel) or byCP (Compacket on PDTCHchannel), merely becauseGPRS and GSM--R cannot be activated at the same time.

l1505 Number ofMSC refusals on VGCS talking requests issued by the

BSC

Name Q3 : vgcsMscReject

Object : bsc

Function : number ofMSC refusals onVGCS talking requests issued by theBSC

Event : receipt of an UPLINK_REJECT_COMMAND message from theMSC


Class : asci





l1506/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 when at least one SS7 TMU, interfaceNode, or local TMU is in overload situation


Class : equipment


Feature : Overload defense mechanism based on real load (FM877-- V12)







l1506/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 overloadsituation

Event : receipt of an incoming external handover request when at least oneSS7 TMU, interface Node, or local TMU board is in overloadsituation


Class : equipment







l1506/2 Number of rejected VBS/VGCS setup requests.

Name Q3 : aintOverLoadRejectedOpVbsVgcsSetup

Object : bsc

Function : number of rejected VBS/VGCS setup requests due to overloadsituation


PE/DCL/DD/0125411--9001--125


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







l1506/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 SS7TMU, interface Node, or local TMU board is in overload situation


Class : equipment



l1506/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

Note : V15.1R counter

l1600 Connection duration of TCH/FRs or preempted PDTCH

Name Q3 : connectionDurationTchMoyconnectionDurationTchMax Maximum connection duration. . . . .connectionDurationTchCum Total connection duration. . . . .connectionDurationTchEch Number of samples. . . . . .connectionDurationTchTrZoneMoyconnectionDurationTchTrZoneMax Maximum connection durationconnectionDurationTchTrZoneCum Total connection durationconnectionDurationTchTrZoneEch Number of samples


Function : average duration ( = total duration divided by the number of samples)and maximum duration of TCH/FR or preempted PDTCHconnections in the inner or the outer zone of the cell, for theobservation period, expressed in multiples of 480 ms

Event : TCH/FR or preempted PDTCH connection/disconnection

connection: start timerdisconnection:• stop and read timer• store its peak value• add it to the total of maximum TCH/FR or preempted PDTCHconnection durations in the observation period



Class : L1M


Note : This counter starts at the beginning of transmission of the SACCHblocks on TCH/FR or preempted PDTCH, and stops at the end ofSACCH blocks transmission.





PE/DCL/DD/0125411--9001--125





DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”



DFD “Radio channel release RELEASE INDICATION procedure(normal completion)”

DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”

l1601 Duration of maximum Downlink power use on busy SDCCHs

Name Q3 : downlinkPowerCtrlMaxSdcchMoydownlinkPowerCtrlMaxSdcchMax Maximum durationdownlinkPowerCtrlMaxSdcchCum Total durationdownlinkPowerCtrlMaxSdcchEch Number of samples.

Object : bts

Function : average duration ( = total duration divided by the number of samples)and maximum duration of maximumDownlink power use on the cellSDCCHs 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 durationson SDCCHs in the observation period



Class : L1M









DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Direct retry handover procedure”DFD “Radio channel release DEACTIVATE SACCH ACKprocedure (normal completion)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”

l1602 Duration of maximum Uplink power use on busy SDCCHs

Name Q3 : uplinkPowerCtrlMaxSdcchMoyuplinkPowerCtrlMaxSdcchMax Maximum duration. .uplinkPowerCtrlMaxSdcchCum Total duration. .uplinkPowerCtrlMaxSdcchEch Number of samples. . .

Object : bts

Function : average duration ( = total duration divided by the number of samples)and maximum duration of maximum Uplink power use on the cellSDCCHs for the observation period

Event : start/end of maximum SDCCH Uplink power use:

start: start timerend:• stop and read timer• store its peak value


PE/DCL/DD/0125411--9001--125


• add it to the total of maximum Uplink power use durations onSDCCHs in the observation period



Class : L1M






Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Direct retry handover procedure”DFD “Radio channel release DEACTIVATE SACCH ACKprocedure (normal completion)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”

l1603 Connection duration of SDCCHs

Name Q3 : connectionDurationSdcchMoyconnectionDurationSdcchMax Maximum connection duration. . . .connectionDurationSdcchCum Total connection duration. . .connectionDurationSdcchEch Number of samples. . . .

Object : bts

Function : average duration ( = total duration divided by the number of samples)and maximum duration of SDCCH connections in the cell for theobservation period, expressed in multiples of 470 ms



Event : SDCCH connection/disconnection

connection: start timer

disconnection:



• add it to the total of maximum SDCCH connection durations inthe observation period



Class : L1M










DFD “queuing of the assignment procedure (normal completion)”

DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”


DFD “Radio channel release DEACTIVATE SACCH ACKprocedure (normal completion)”


Note : This counter starts at the beginning of transmission of SACCHblockson TCH, and stops at the end of SACCH blocks transmission.


PE/DCL/DD/0125411--9001--125


l1603/0 Connection duration of SDCCHs

Name Q3 : connectionDurationSdcchTrZoneMoyconnectionDurationSdcchTrZoneMax Maximum. . . . . . .connection durationconnectionDurationSdcchTrZoneCum Total connection. . . . . .durationconnectionDurationSdcchTrZoneEch Number of samples. . . . . . .


Function : average duration ( = total duration divided by the number of samples)and maximum duration of SDCCH connections in the inner or theouter zone of the cell, for the observation period, expressed inmultiples of 470 ms

Event : SDCCH connection/disconnection

connection: start timerdisconnection:• stop and read timer• store its peak value• add it to the total of maximum SDCCH connection durations inthe observation period



Class : L1M






Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”



DFD “queuing of the assignment procedure (normal completion)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Direct retry handover procedure”DFD “Radio channel release DEACTIVATE SACCH ACKprocedure (normal completion)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”

Note : This counter starts at the beginning of transmission of SACCHblockson TCH, and stops at the end of SACCH blocks transmission.

l1604 Average number of messages waiting in queue for transmission

on PCH-AGCH

Name Q3 : pchAveragedQueueLengthMoypchAveragedQueueLengthTs2MoypchAveragedQueueLengthTs4MoypchAveragedQueueLengthTs6MoypchAveragedQueueLengthMax Max queued messages. . .pchAveragedQueueLengthTs2Max Max queued messagespchAveragedQueueLengthTs4Max Max queued messagespchAveragedQueueLengthTs6Max Max queued messagespchAveragedQueueLengthCum Total queued messages. . .pchAveragedQueueLengthTs2Cum Total queued messagespchAveragedQueueLengthTs4Cum Total queued messagespchAveragedQueueLengthTs6Cum Total queued messagespchAveragedQueueLengthEch Number of samples. . .pchAveragedQueueLengthTs2Ech Number of samples.pchAveragedQueueLengthTs4Ech Number of samples.pchAveragedQueueLengthTs6Ech Number of samples.

Object : bts


PE/DCL/DD/0125411--9001--125


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 transmittedon PCH-AGCH in the observation period; this internalBTS counter issent to the BSC in a CCCH_LOAD_INDICATION message

Event : message queuing, message transmission, internal sampling time-outelapse:

queuing: step up by one the number of messages waiting fortransmission on PCH-AGCHtransmission: step down by one the number of messages waitingfor transmission on PCH-AGCHsampling time-out elapse:• read the instantaneous value of the number of messages queued• store its peak value• add it to the total number of messages queued for theobservation period



Class : monitoring






Paging + Immediate Assignment

Queue size (120 PCHs for an S8000 BTS)

The queue is increased by a variable flow of Immediate Assignmentand all Pagingmessages (fresh and repeated) and servedby aconstantflow of CCCH resources (3 blocks in case of BCCH combined and 9blocks in case of not combined BCCH).The priority order in the queue is Immediate Assignment never sent,Fresh Paging, Repeated Paging, ImmediateAssignment already sent.

The 1604 counter is related to the size of the queue of these Pagingmessages queued before being transmitted on PCH--AGCH in theobservation period.






l1605 Number of paging messages queued up not transmitted

Name Q3 : pchQueuePagesDiscardedpchQueuePagesDiscardedTs2pchQueuePagesDiscardedTs4pchQueuePagesDiscardedTs6

Object : bts


PE/DCL/DD/0125411--9001--125


Location :

Name Q3 Location

pchQueuePagesDiscarded CCCH--0

pchQueuePagesDiscarded2 CCCH--2



Function : number of paging messages removed from the paging queue beforebeing transmitted on PCH in the observation period

Event : receipt of a paging message queuing request that leads to remove thelatest request from the queue (the maximum number of pagingmessages that can be queued is reached); receipt of aCCCH_LOAD_INDICATION message from the BTS


Class : monitoring




CCCH channel POOL

Paging + Immediate Assignment

Queue size (120 PCHs for an S8000)

The queue is increased by a variable flow of Immediate Assignmentand all Pagingmessages (fresh and repeated) and servedby aconstantflow of CCCH resources (3 blocks in case of BCCH combined and 9blocks in case of not combined BCCH).The priority order in the queue is Immediate Assignment never sent,Fresh Paging, Repeated Paging, ImmediateAssignment already sent.The 1605 counter is related to Paging messages that are removedfrom the queue because the maximum size of the queue is reached orbecause the retransDuration timer (maximum time of a Pagingmessage in the queue) expiration.






l1606 Number of SDCCHs allocated in the zone (concentric cell)Name Q3 : sdcchAllocated

sdcchAllocatedTrZone

Object : transceiverZone/btsFunction : 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 zonecounter value that appears in the “BTS report”: number of SDCCHallocations for the entire cell (cell = sum of the cell transceiverzones)

For a monozone network, the zone is the entire cell

Event : allocation of an SDCCH in the zone (transceiver zone or entire cell)


Class : allocationSource : recorded by the BSCPreciseincrementation conditions :



Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “immediate assignment procedure (normal completion)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “SMS procedure (SMS established by the MS)”


PE/DCL/DD/0125411--9001--125


1607 Average number of SDCCHs used in the zone (concentric cell)

Name Q3 : sdcchAveragedUsedTrZoneMoysdcchAveragedUsedTrZoneMax Max SDCCH allocated. .sdcchAveragedUsedTrZoneCum Total SDCCH allocated. .sdcchAveragedUsedTrZoneEch Number of samples. . .sdcchAveragedUsedMoysdcchAveragedUsedMaxsdcchAveragedUsedCumsdcchAveragedUsedEch


Function : average (= total number divided by number of samples) andmaximum number of SDCCHs used in the zone

Counter value calculation:

counter value that appears in the “Transceiver zone report”:number of SDCCH used for the transceiver zone

counter value that appears in the “BTS report”: number of SDCCHused for the entire cell (cell = sum of the cell transceiver zones)


Event : SDCCH allocation/deallocation in a zone, internal sampling time-outelapse:

allocation: step up by one the instantaneous value of the number ofSDCCHs used in the zone

deallocation: step down by one the instantaneous value of thenumber of SDCCHs used in the zone


• read the instantaneous value of the number of SDCCHs used inthe zone


• add it to the total number of SDCCH allocations in the zone forthe observation period



Class : allocation








Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “immediate assignment procedure (normal completion)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “Radio channel release DEACTIVATE SACCH ACKprocedure (normal completion)”DFD “Radio channel release RELEASE INDICATION procedure(normal completion)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”DFD “SMS procedure (SMS established by the MS)”


PE/DCL/DD/0125411--9001--125


l1608 Number of SDCCH allocation failures in the zone (concentric

cell)

Name Q3 : sdcchRessourceFailuresdcchRessourceFailureTrZone


Function : number of SDCCH allocation failures due to a lack of SDCCH in thezone


counter value that appears in the “Transceiver zone report”:number of SDCCH allocation failures for the transceiver zonecounter value that appears in the “BTS report”: number of SDCCHallocation failures for the entire cell (cell = sum of the celltransceiver zones)


Event : SDCCH allocation refusal with cause “out of stock”


Class : allocation








l1609/0 Number of TCH/FR or preempted PDTCH allocated for traffic

in the zone (concentric cell)

Name Q3 : tchFrAllocatedTchAllocationTrZonetchFrAllocatedTchAllocation


Function : number of TCH/FR or preempted PDTCH allocated in the zone fortraffic


counter value that appears in the “Transceiver zone report”:number of TCH/FR or preempted PDTCH allocated thetrasnceiver zonecounter value that appears in the “BTS report”: number ofTCH/FRor preempted PDTCHallocated for the entire cell (cell = sumof thecell transceiver zones)


Event : TCH/FR or preempted PDTCH allocation in the zone for traffic


Class : allocation







PE/DCL/DD/0125411--9001--125


Data flows : Refer to Chapter 1DFD “GPRS procedure (no resource available for a PDTCHpreemption)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”

l1609/1 Number of TCH/FR allocated for call reestablishments in the

zone (concentric cell) (primo-allocation)

Name Q3 : tchFrAllocatedPrimoAllocationTrZonetchFrAllocatedPrimoAllocation


Function : number of TCH/FR allocated in the zone for call reestablishment


counter value that appears in the “Transceiver zone report”:number of TCH/FR allocated for the transceiver zone for callreestablishmentcounter value that appears in the “BTS report”: number ofTCH/FRallocated for the entire cell (cell = sumof the cell transceiver zones)for call reestablishment


Event : TCH/FR allocation in the zone for call reestablishment


Class : allocation





When GPRS is activated, this counter is concerned by CCT (Circuitcalls on TCH channel), but not by CCP (Circuit Calls on PDTCHpreempted to make a TCH channel) or CP (Com packet on PDTCHchannel).This is because this counter is related to configured (static) TCH/FRchannel only, and does not take into account preempted PDTCH.

Data flows : Refer to Chapter 1DFD “Immediate assignment procedure (normal completion)”

l1609/2 Number of TCH/FR allocated because of SDCCH unavailability


Name Q3 : tchFrAllocatedOverflowAllocationTrZonetchFrAllocatedOverflowAllocation


Function : number of TCH/FR allocated in the zone because of SDCCHunavailability Counter value calculation:

counter value that appears in the “Transceiver zone report”:number of TCH/FR allocated for the transceiver zonecounter value that appears in the “BTS report”: number ofTCH/FRallocated for the entire cell (cell = sumof the cell transceiver zones)


Event : TCH/FR allocation in the zone because of SDCCH unavailability


Class : allocation






Data flows : Refer to Chapter 1DFD “immediate assignment procedure (normal completion)”DFD “Immediate assignment paging procedure (normalcompletion)”


PE/DCL/DD/0125411--9001--125


l1609/3 Number of WPS full rate TCH allocations

Name Q3 : tchFrAllocatedWpstchFrAllocatedWpsTrZone


Function : Number of WPS full rate TCH (including PDTCH) allocations

Event : Allocation of a full rate TCH


Class : allocation

Feature : WPS BSS2G and E3 public access bandwidth protection (22465)


l1610/0 Number of half rate TCH allocations in Transciever Zone

Name Q3 : tchHrAllocatedTchAllocationtchHrAllocatedTchAllocationTrZone


Function : Cumulative number of half rate TCH allocations.

Event : Allocation of a half rate TCH (including PDTCH) for a WPS call.




l1610/1 Number of half rate TCH allocations

Name Q3 : tchHrAllocatedWpstchHrAllocatedWpsTrZonetchHrAllocatedPrimoAllocationtchHrAllocatedPrimoAllocationTrZone


Function : Cumulative number of half rate TCH allocations.

Event : Allocation of a half rate TCH (including PDTCH) for a WPS call.






l1611/0 Average number of TCH/FR or preempted PDTCH used for

traffic in the zone (concentric cell)

Name Q3 : tchFrAveragedUsedTchAllocationMoytchFrAveragedUsedTchAllocationEchtchFrAveragedUsedTchAllocationCumtchFrAveragedUsedTchAllocationMaxtchFrAveragedUsedTchAllocationTrZoneMoytchFrAveragedUsedTchAllocationTrZoneMaxtchFrAveragedUsedTchAllocationTrZoneCumtchFrAveragedUsedTchAllocationTrZoneEch


Function : average (= total number divided by number of samples) andmaximum number of TCH/FR or preempted PDTCH used for trafficin the zone of the cell, obtained through internal sampling


counter value that appears in the “Transceiver zone report”:number of TCH/FR or preempted PDTCH used for traffic for thetransceiver zonecounter value that appears in the “BTS report”: number ofTCH/FRor preempted PDTCH used for traffic for the entire cell


Event : TCH/FR or preempted PDTCHallocation/deallocation for traffic in azone, internal sampling time-out elapse:

allocation: step up by one the instantaneous value of the number ofTCH/FR or preempted PDTCH used for traffic in the zonedeallocation: step down by one the instantaneous value of thenumber of TCH/FR or preempted PDTCH used for traffic in thezonesampling time-out elapse:• read the instantaneous value of the number of TCH/FR orpreempted PDTCH used for traffic in the zone

• store its peak value• add it to the total number of TCH/FR or preempted PDTCHallocations for traffic in the zone for the observation period



Class : allocation



PE/DCL/DD/0125411--9001--125







Data flows : Refer to Chapter 1DFD “GPRS procedure (no resource available for a PDTCHpreemption)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”



l1611/1 Average number of TCH/FRused for call reestablishments in the

zone (concentric cell) (primo-allocation)

Name Q3 : tchFrAveragedUsedPrimoAllocationMoytchFrAveragedUsedPrimoAllocationMaxtchFrAveragedUsedPrimoAllocationCumtchFrAveragedUsedPrimoAllocationEchtchFrAveragedUsedPrimoAllocationTrZoneMoytchFrAveragedUsedPrimoAllocationTrZoneMaxtchFrAveragedUsedPrimoAllocationTrZoneCumtchFrAveragedUsedPrimoAllocationTrZoneEch


Function : average (= total number divided by number of samples) andmaximum number of TCH/FR used for call reestablishments in thezone, obtained through internal sampling


counter value that appears in the “Transceiver zone report”:number of TCH/FR used for call reestablisment for the transceiverzonecounter value that appears in the “BTS report”: number ofTCH/FRused for call reestablishment for the entire cell


Event : TCH/FR allocation/deallocation for call reestablishment in a zone,internal sampling time-out elapse:

allocation: step up by one the instantaneous value of the number ofTCH/FR used for call reestablishment in the zonedeallocation: step down by one the instantaneous value of thenumber of TCH/FR used for call reestablishment in the zonesampling time-out elapse:• read the instantaneous value of the number of TCH/FR used forcall reestablishment in the zone

• store its peak value• add it to the total number of TCH/FR allocations for callreestablishment in the zone for the observation period



Class : allocation



PE/DCL/DD/0125411--9001--125



When GPRS is activated, this counter is concerned by CCT (Circuitcalls on TCH channel), but not by CCP (Circuit Calls on PDTCHpreempted to make a TCH channel) or CP (Com packet on PDTCHchannel).

This is because this counter is related to configured (static) TCH/FRchannel only, and does not take into account preempted PDTCH.

Data flows : Refer to Chapter 1DFD “Immediate assignment procedure (normal completion)”

l1611/2 Average number of TCH/FR used because of SDCCH

unavailability in the zone (concentric cell)

Name Q3 : tchFrAveragedUsedOverflowAllocationMoytchFrAveragedUsedOverflowAllocationMaxtchFrAveragedUsedOverflowAllocationCumtchFrAveragedUsedOverflowAllocationEchtchFrAveragedUsedOverflowAllocationTrZoneMoytchFrAveragedUsedOverflowAllocationTrZoneMaxtchFrAveragedUsedOverflowAllocationTrZoneCumtchFrAveragedUsedOverflowAllocationTrZoneEch


Function : average (= total number divided by number of samples) andmaximum number of TCH/FR used because of SDCCHunavailability in the zone, obtained through internal sampling


counter value that appears in the “Transceiver zone report”:number of TCH/FR used because of SDCCH unavailability thetransceiver zonecounter value that appears in the “BTS report”: number ofTCH/FR because of SDCCH unavailabillity for the entire cell




Event : TCH/FR allocation/deallocation in the zone because of SDCCHunavailability, internal sampling time-out elapse:

allocation: step up by one the instantaneous value of the number ofTCH/FR used in the zone because of SDCCH unavailabilitydeallocation: step down by one the instantaneous value of thenumber of TCH/FR used in the zone because of SDCCHunavailabilitysampling time-out elapse:• read the instantaneous value of the number of TCH/FR used inthe zone because of SDCCH unavailability

• store its peak value• add it to the total number of TCH/FR allocations in the zonebecause of SDCCH unavailability for the observation period



Class : allocation


l1611/3 Average andmaximumnumber ofWPS full rateTCHallocations

Name Q3 : tchFrAveragedUsedWpsCumtchFrAveragedUsedWpsEchtchFrAveragedUsedWpsMaxtchFrAveragedUsedWpsMoytchFrAveragedUsedWpsTrZoneCumtchFrAveragedUsedWpsTrZoneEchtchFrAveragedUsedWpsTrZoneMaxtchFrAveragedUsedWpsTrZoneMoy


Function : Average and maximum number of WPS full rate TCH (includingPDTCH) allocations

Event : Allocation/de--allocation of a full rate TCH


Class : allocation





PE/DCL/DD/0125411--9001--125



When GPRS is activated, this counter is concerned by CCT (Circuitcalls on TCH channel), but not by CCP (Circuit Calls on PDTCHpreempted to make a TCH channel).

This is because this counter is related to configured (static) TCH/FRchannel. This counter is pegged on the traffic channel allocation for aWPS call if the WPS Management flag is enabled. This counter ispegged on the traffic channel de--allocation for a call inititiated as aWPS call.





l

1612/0 Average and maximum number of half rate TCH allocations

Name Q3 : tchHrAveragedUsedTchAllocationCumtchHrAveragedUsedTchAllocationEchtchHrAveragedUsedTchAllocationMaxtchHrAveragedUsedTchAllocationMoytchHrAveragedUsedTchAllocationTrZoneCumtchHrAveragedUsedTchAllocationTrZoneEchtchHrAveragedUsedTchAllocationTrZoneMaxtchHrAveragedUsedTchAllocationTrZoneMoy


Function : Average andmaximum number of half rate TCH (including PDTCH)allocations

Event : Allocation/de--allocation of a half rate TCH


Class : allocation

Feature : E3 public access bandwidth protection (22465)




l1612/1 Average and maximum number of half rate Primo allocations

Name Q3 : tchHrAveragedUsedWpsMoytchHrAveragedUsedWpsMaxtchHrAveragedUsedWpsEchtchHrAveragedUsedWpsCumtchHrAveragedUsedWpsTrZoneMoytchHrAveragedUsedWpsTrZoneMaxtchHrAveragedUsedWpsTrZoneEchtchHrAveragedUsedWpsTrZoneCumtchHrAveragedUsedPrimoAllocationCum (do not use. Not increm.)tchHrAveragedUsedPrimoAllocationEch (do not use. Not increm.)tchHrAveragedUsedPrimoAllocationMax (do not use. Not increm.)tchHrAveragedUsedPrimoAllocationMoy (do not use. Not increm.)tchHrAveragedUsedPrimoAllocationTrZoneCum (do not use. Notincrem.)tchHrAveragedUsedPrimoAllocationTrZoneEch (do not use. Notincrem.)tchHrAveragedUsedPrimoAllocationTrZoneMax (do not use. Notincrem.)tchHrAveragedUsedPrimoAllocationTrZoneMoy (do not use. Notincrem.)


Function : Average and maximum number of WPS half rate TCH (includingPDTCH) allocations



Class : allocation



Preciseincrementation conditions : When GPRS is activated, this counter isconcerned byCCT (Circuit calls onTCH channel), but not by CCP (Circuit Calls onPDTCH preempted to make a TCH channel). This is because this counter is relatedto configured (static) TCH/FRchannel. This counter is pegged on the traffic channelallocation for a WPS call if the WPS Management flag is enabled. This counter ispegged on the traffic channel de--allocation for a call inititiated as a WPS call.


PE/DCL/DD/0125411--9001--125


l1613 Number of TCH/FRandpreemptable PDTCHallocation failures


Name Q3 : tchFrRessourceFailuretchFrRessourceFailureTrZone


Function : number of allocation failures due to a lack of TCH/FR andpreemptable PDTCH in the zone, and due to a lack of free entries inthe queueCounter value calculation:counter value that appears in the “Transceiver zone report”:number of TCH/FR and preemptable PDTCH allocation failuresfor the transceiver zonecounter value that appears in the “BTS report”: number ofTCH/FRand preemptable PDTCH allocation failures for the entire cell


Event : TCH/FR and preemptable PDTCH allocation refusal in the zonewithcause “out of stock”


Class : allocation


Note : This counter is also incremented if there are free TCHs, that arereserved for allocation requests with the maximum priority(allocPriorityThreshold attribute).Also see C1039 counter for summation count at bts level.




Data flows : Refer to Chapter 1DFD “GPRS procedure (no available resource for a PDTCHpreemption)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (no resourceavailable and queuing not activated)”



l1614 Number of TCH/HR and preemptable PDTCH allocation

failures in the zone (concentric cell)

Name Q3 : tchHrRessourceFailuretchHrRessourceFailureTrZone


Function : number of failures caused by the lack of half rate TCH in a tdma_classof 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.


PE/DCL/DD/0125411--9001--125


l1616/0 Average number of TCHs with highest priority queued up

Name Q3 : tchAveragedQueueLengthHighPriorityMoytchAveragedQueueLengthHighPriorityMaxtchAveragedQueueLengthHighPriorityCumtchAveragedQueueLengthHighPriorityEch

Object : bts

Function : average (= total number divided by number of samples) andmaximum number of TCH allocation requests with maximumpriority queued for the cell, obtained through internal sampling

Event : TCH allocation request queued with cause “out of stock”, TCHallocation, internal sampling time-out elapse:

queuing: step up by one the instantaneous value of the number ofTCHs with maximum priority queuedallocation: step down by one the instantaneous value of thenumberof TCHs with maximum priority queuedsampling time-out elapse:• read the instantaneous value of the number of TCHs withmaximum priority queued

• store its peak value• add it to the total number of TCH allocation requests withmaximum priority queued for the observation period



Class : allocation






Data flows : Refer to Chapter 1DFD “queuing of the assignment procedure (normal completion)”DFD “Direct retry handover procedure”



l1616/1 Average number of TCHs without highest priority queued up

Name Q3 : tchAveragedQueueLengthOtherPriorityMoytchAveragedQueueLengthOtherPriorityMaxtchAveragedQueueLengthOtherPriorityCumtchAveragedQueueLengthOtherPriorityEch

Object : bts

Function : average (= total number divided by number of samples) andmaximum number of TCH allocation requests with non-maximumpriority queued for the cell, obtained through internal sampling

Event : TCH allocation request queued with cause “out of stock”, TCHallocation, internal sampling time-out elapse:

queuing: step up by one the instantaneous value of the number ofTCHs with non-maximum priority queued

allocation: step down by one the instantaneous value of thenumberof TCHs with non-maximum priority queued


• read the instantaneous value of the number of TCHs withnon-maximum priority queued


• add it to the total number of TCH allocation requests withnon-maximum priority queued for the observation period



Class : allocation







DFD “queuing of the assignment procedure (normal completion)”DFD “Direct retry handover procedure”


PE/DCL/DD/0125411--9001--125


l1617/0 Number of TCH allocation requests with highest priority queued

up unsatisfiedName Q3 : tchQueuingExpirationHighPriority

Object : bts

Function : number of TCH allocation requests with maximum priority queuedand unsatisfied because of time-out elapse

Event : time-out elapse of a TCH allocation request with maximum priorityqueued


Class : allocation





l1617/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 priorityqueued and unsatisfied because of time-out elapse

Event : time-out elapse of a TCH allocation request with non-maximumpriority queued


Class : allocation







l1618/0 Average waiting time of TCH allocation requests with highest

priority

Name Q3 : tchQueuingDurationHighPriorityMoytchQueuingDurationHighPriorityMax Max wait durations. . . . . . .tchQueuingDurationHighPriorityCum Total wait durations. . . . . .tchQueuingDurationHighPriorityEch Number of samples. . . . . . .

Object : bts

Function : average waiting duration ( = total duration divided by the number ofsamples) and maximum waiting duration of TCH allocation requestswith maximum priority in the cell, obtained through internalsampling. Counts both requestswhich are served, aborted or extractedon 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 timersampling time-out elapse:• read timer

• store its peak value• add it to the total of waiting durations of TCH allocationrequests with maximum priority in the observation period



Class : allocation









PE/DCL/DD/0125411--9001--125


l1618/1 Average waiting time of TCH allocation requests without highest

priority

Name Q3 : tchQueuingDurationOtherPriorityMoytchQueuingDurationOtherPriorityMax Max wait durations. . . . . .tchQueuingDurationOtherPriorityCum Total wait durations. . . . . .tchQueuingDurationOtherPriorityEch Number of samples. . . . . . .

Object : bts

Function : average waiting duration ( = total duration divided by the number ofsamples) and maximum waiting duration of TCH allocation requestswith non-maximum priority in the cell, obtained through internalsampling. Counts both requestswhich are served, aborted or extractedon 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 timersampling time-out elapse:• read timer

• store its peak value• add it to the total of waiting durations of TCH allocationrequests with non-maximum priority in the observation period



Class : allocation










l1619/0 Average number of free channels in interference band No.0

Name Q3 : channelAveragedIdlePerInterfBand0MoychannelAveragedIdlePerInterfBand0Max Max in Band No.0. . . .channelAveragedIdlePerInterfBand0Cum Total in Band No.0. . . .channelAveragedIdlePerInterfBand0Ech Number of samples. . . . .

Object : bts

Function : average (= total number divided by number of samples) andmaximum number of radio idle channels in Interference band No.0,obtained through internal sampling

Event : SDCCH or TCH allocation/deallocation, sampling time-out elapse


Class : interference



Measurement of interference is performedwhen in Idlemode.Beforethe preemption, the PDTCH is assigned to the PCU and thusconsidered as used from the BSS side. During the preemption, thePDTCH is re--configured as TCH/FR and then assigned to a CircuitCall. 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 inthe interference band of the TDMA which supports the greaternumber of channels.The cumulative value, which is relative to oneTDMA, is thereforethe sum of numbers of radio channels in the interference banddivided by the number of TDMAs in the cell (i.e. 2).



Object : bts



PE/DCL/DD/0125411--9001--125








Note : In case of concentric cells (2 TDMAs in one cell):

The maximum value is the maximum number of radio channels inthe interference band of the TDMA which supports the greaternumber of channels.

The cumulative value, which is relative to oneTDMA, is thereforethe sum of numbers of radio channels in the interference banddivided by the number of TDMAs in the cell (i.e. 2).

l

1619/2 Average number of free channels in interference band No.2


Object : bts











The maximum value is the maximum number of radio channels inthe interference band of the TDMA which supports the greaternumber of channels.The cumulative value, which is relative to oneTDMA, is thereforethe sum of numbers of radio channels in the interference banddivided by the number of TDMAs in the cell (i.e. 2).

1619/3 Average number of free channels in interference band No.3


Object : bts









PE/DCL/DD/0125411--9001--125







Object : bts













l1620 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 ofeligible cells is empty

Event : no reception of HANDOVER INDICATION with cause “directedretry” after receipt of CONNECTION STATE RESPONSE from theBTS (with an empty list of eligible cells and in the directed retryhandover procedure) and before the end of queuing phase


Class : handover






l1621 Number of SAPI 3 session establishments for SMS

Name Q3 : sapi3SessionEstablishment

Object : bts

Function : number of SAPI sessions established to satisfy a short messagebroadcast request in the cell

Event : receipt of one of the following messages from the BTS:

ESTABLISH INDICATION on SAPI3 (establishment requestedby a mobile)ESTABLISH CONFIRM on transmission of ESTABLISHREQUEST with SAPI3 value (receipt of a DTAP message onSAPI3 from the MSC when no SAPI3 session is in-progress)


Class : SMS service



PE/DCL/DD/0125411--9001--125






Data flows : Refer to Chapter 1DFD “SMS procedure (SMS established by the MS)”DFD “SMS procedure (SMS established by the MSC)”

l1622 Number of MS measurement messages not received

Name Q3 : msLostMeasurementsmsLostMeasurementsTrZone


Function : number ofmobilemeasurementmessages not received by the inner orthe outer zone of the cell

Event : BSC receipt of STOPMEASUREMENTACKwith nomeasurementmessage from a mobile


Class : L1M






Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”



DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”DFD “Radio channel release DEACTIVATE SACCH ACKprocedure (normal completion)”DFD “Radio channel release RELEASE INDICATION procedure(normal completion)”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”

1623 Sum of Downlink signal strength measurements

Name Q3 : rxLevDownLinkrxLevDownLinkTrZone


Function : sum of the downlink signal strength measurements performed by themobiles on the inner or outer zoneof the cell in the observationperiod,expressed in GSM values [0 to 63]

Event : BSC receipt of STOP MEASUREMENT ACK from the BTS


Class : L1M







PE/DCL/DD/0125411--9001--125


Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”

l1624 Sum of Uplink signal strength measurements

Name Q3 : rxLevUpLink


Function : sum of the uplink signal strength measurements performed by theBTS on the cell in the observation period, expressed in GSM values[0 to 63]



Class : L1M








Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”DFD “Radio channel release DEACTIVATE SACCH ACKprocedure (normal completion)”DFD “Radio channel release RELEASE INDICATION procedure(normal completion)”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”

l1624 Sum of Uplink signal strength measurements

Name Q3 : rxLevUpLinkTrZone

Object : transceiver Zone

Function : sum of the uplink signal strength measurements performed by theBTSon the inner or theouter zoneof the cell in the observationperiod,expressed in GSM values [0 to 63]



Class : L1M



PE/DCL/DD/0125411--9001--125





Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”DFD “Radio channel release DEACTIVATE SACCH ACKprocedure (normal completion)”DFD “Radio channel release RELEASE INDICATION procedure(normal completion)”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”

l1625 Sum of Downlink signal quality measurements

Name Q3 : rxQualDownLink


Function : sum of the downlink signal quality measurements performed by themobiles on the cell in the observation period, expressed in 100xBER





Class : L1M







DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”DFD “Radio channel release DEACTIVATE SACCH ACKprocedure (normal completion)”DFD “Radio channel release RELEASE INDICATION procedure(normal completion)”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”


PE/DCL/DD/0125411--9001--125


l1625 Sum of Downlink signal quality measurements

Name Q3 : rxQualDownLinkTrZone


Function : sum of the downlink signal quality measurements performed by themobiles on the inner or the outer zone of the cell in the observationperiod, expressed in 100xBER



Class : L1M






Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”



DFD “Radio channel release DEACTIVATE SACCH ACKprocedure (normal completion)”DFD “Radio channel release RELEASE INDICATION procedure(normal completion)”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”

l1626 Sum of Uplink signal quality measurements

Name Q3 : rxQualUpLink


Function : sum of the uplink signal quality measurements performed by theBTSon the cell in the observation period, expressed in 100xBER



Class : L1M





Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”


PE/DCL/DD/0125411--9001--125


DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”DFD “Radio channel release DEACTIVATE SACCH ACKprocedure (normal completion)”DFD “Radio channel release RELEASE INDICATION procedure(normal completion)”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALLING phase)”

l1626 Sum of Uplink signal quality measurementsName Q3 : rxQualUpLinkTrZoneObject : transceiverZoneFunction : sum of the uplink signal quality measurements performed by theBTS

on the inner or the outer zone of the cell in the observation period,expressed in 100xBER



Class : L1MSource : recorded by the BSCPreciseincrementation conditions :



Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”



DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”






DFD “Radio channel release RELEASE INDICATION procedure(normal completion)”

DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”


l1629/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 forsignaling in the cell

Event : transmission of CHANNEL ACTIVATE with CHANNELMODE = “signalling”


Class : assignment







PE/DCL/DD/0125411--9001--125


Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Oritinating Calls)”DFD “Immediate assignment procedure (normal completion)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “SMS procedure (SMS established by the MS)”

l1629/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 thecell

Event : transmission of CHANNEL ACTIVATE with CHANNELMODE = “signalling”


Class : assignment






Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Oritinating Calls)”DFD “Immediate assignment procedure (normal completion)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “SMS procedure (SMS established by the MS)”



l1700 Average number of TCH/FR and preemptable PDTCHavailable

in multizone cell

Name Q3 : tchFrAveragedAvailabletchFrAveragedAvailableMoytchFrAveragedAvailableMaxtchFrAveragedAvailableCumtchFrAveragedAvailableEchtchFrAveragedAvailableTrZoneMoytchFrAveragedAvailableTrZoneMaxMax TCH/FR availabletchFrAveragedAvailableTrZoneCumTotal TCH/FR availabletchFrAveragedAvailableTrZoneEch Number of samples


Function : average (= total number divided by number of samples) andmaximum number of available radio TS for circuit calls, on a TDMAclass basis. Used resources are:

radio TS used for circuit call only

radio TS shared between circuit services and packet data services


counter value that appears in the “Transceiver zone report”:number of TCH/FR and preemptable PDTCH available for thetransceiver zone

counter value that appears in the “BTS report”: number ofTCH/FRand preemptable PDTCH available for the entire cell


Formula : due to theminNbrGprsTS parameter defined on a cell basis, the exactimplementation 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

C1700_oz = Number_of_TCH_oz + Number_of_PDTCH_oz –minNbrGprsTS

Inner zone:

C1700_iz = Number_of_TCH_iz + Number_of_PDTCH_iz

Where oz = outer zone and iz = inner zone


PE/DCL/DD/0125411--9001--125


Event : TDMA frame allocation/deallocation in the zone, radio channelblocking, SYS INFO5 and 6 acknowledgement not received, internalsampling time-out elapse:

allocation: step up by one the instantaneous value of the number ofavailable TCH/FR and preemptable PDTCH in the zonedeallocation/blocking/non-acknowledgement: step down by onethe instantaneous value of the number of available TCH/FR in thezonesampling time-out elapse:• read the instantaneous value of the number of availableTCH/FR and preempted PDTCH in the zone

• store its peak value• add it to the total number of available TCH/FR and preemptedPDTCH in the zone for the observation period



Class : allocation

Source : calculated by OMC--R agent





To sum it up, this counter is related to TCH/FR channel, preemptablePDTCH and PDTCH not allocated to PCUSN.


Note : In order to guarantee a minimum of GPRS bandwidth, the operatorcan set at the OMC--R level, the number of PDTCHwhich can not beused by circuit call (minNbrGprsTS parameter; for more detailsplease refer to NTP < 124 >)



l1701 Average number of SDCCHavailable in the zone (concentric cell)

Name Q3 : sdcchAveragedAvailableMoysdcchAveragedAvailableMax Max available SDCCHs. . . . .sdcchAveragedAvailableCum Total available SDCCHs. . . .sdcchAveragedAvailableEch Number of samples. . . . .sdcchAveragedAvailableTrZoneMoysdcchAveragedAvailableTrZoneMax Max SDCCH available. . . .sdcchAveragedAvailableTrZoneCum Total SDCCH available. . .sdcchAveragedAvailableTrZoneEch Number of samples. . . .


Function : average (= total number divided by number of samples) andmaximum number of available SDCCHs -- allocated or availableobtained by internal sampling


counter value that appears in the “Transceiver zone report”:number of SDCCH averaged available for the transceiver zonecounter value that appears in the “BTS report”: number of SDCCHaveraged available for the entire cell (cell = sum of the celltransceiver zones)


Event : SDCCH allocation/deallocation in the zone (transceiver zone orentire cell), radio channel blocking, SYS INFO 5 and 6acknowledgement not received, internal sampling time-out elapse:

allocation: step up by one the instantaneous value of the number ofavailable SDCCHs in the zone (transceiver zone or entire cell)deallocation/blocking/non-acknowledgement: step down by onethe instantaneous value of the number of available SDCCHs in thezone (transceiver zone or entire cell)sampling time-out elapse:• read the instantaneous value of the number of availableSDCCHs in the zone

• store its peak value• add it to the total number of available SDCCHs in the zone forthe observation period



Class : allocation



PE/DCL/DD/0125411--9001--125






l1702 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 timingadvance greater than 63

Event : receipt of CHANNEL REQUEST containing a timing advance valuegreater than 63


Class : setup






Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “immediate assignment procedure (normal completion)”DFD “Immediate assignment paging procedure (normalcompletion)”



l1705/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 servicemessages in the cell with a 1200/75 b/s transmission rate

Event : transmission of CHANNEL ACTIVATE or MODE MODIFY withCHANNEL MODE = “data” for a transparent service on a full--rateTCH with a 1200/75 b/s transmission rate


Class : assignment






To sum it up, this counter is related to TCH/FR and preemptedPDTCH channels (circuit calls).








DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”


PE/DCL/DD/0125411--9001--125



a 600 b/s transmission rate


Object : bts

Function : number of full–rate channels activated for transparent data servicemessages in the cell with a 600 b/s transmission rate

Event : transmission of CHANNEL ACTIVATE or MODE MODIFY withCHANNEL MODE = “data” for a transparent service on a full--rateTCH with a 600 b/s transmission rate


Class : assignment




















Object : bts




Class : assignment
















PE/DCL/DD/0125411--9001--125





Object : bts




Class : assignment




















Object : bts




Class : assignment
















PE/DCL/DD/0125411--9001--125





Object : bts




Class : assignment




















Object : bts




Class : assignment
















PE/DCL/DD/0125411--9001--125


l1706/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 rateTCH.

Event : transmission of a CHANNEL_ACTIVATE message or of aMODE_MODIFY message with a CHANNEL MODE record set to“data” for a transparent service on a half rate TCH.


Class : assignment


















half rate TCH with a 600 b/s transmission rate.


Object : bts

Function : Number of channel activation for transparent data service on half rateTCH with a 600 b/s transmission rate.



Class : assignment
















PE/DCL/DD/0125411--9001--125



half rate TCH with a 1200 b/s transmission rate.


Object : bts




Class : assignment


















half rate TCH with a 2400 b/s transmission rate


Object : bts




Class : assignment
















PE/DCL/DD/0125411--9001--125



half rate TCH with a 4800 b/s transmission rate


Object : bts




Class : assignment

















l1707/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 dataservice messages in the cell with a 6000 b/s transmission rate

Event : transmission of CHANNEL ACTIVATE or MODE MODIFY withCHANNEL MODE = “data” for a non--transparent service on afull--rate TCH with a 6000 b/s transmission rate


Class : assignment
















PE/DCL/DD/0125411--9001--125





Object : bts




Class : assignment




















Object : bts




Class : assignment
















PE/DCL/DD/0125411--9001--125


l1709 Number of TCH/FR activation for transparent data serviceName Q3 : channelActTchFrDataT

Object : bts

Function : number of full–rate channels activated for transparent data servicemessages in the cell

Event : transmission of CHANNEL ACTIVATE or MODE MODIFY withCHANNEL MODE = “data” for a transparent service on a full--rateTCH


Class : assignment


Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”

l1710 Number of TCH/FR activation for non--transparent data serviceName Q3 : channelActTchFrDataNT

channelActivateTchFrDataNtHscsdchannelActivateTchFrDataTHscsd

Object : bts

Function : number of full–rate channels activated for non--transparent dataservice messages in the cell

Event : transmission of CHANNEL ACTIVATE or MODE MODIFY withCHANNEL MODE = “data” for a non--transparent service on afull--rate TCH


Class : assignment





l1711/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 servicemessages in the cell

Event : transmission of CHANNEL ACTIVATE or MODE MODIFY withCHANNEL MODE = “data” for atransparent service on a full--rateTCH


Class : assignment




PE/DCL/DD/0125411--9001--125


l1712/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 servicemessages in the cell

Event : transmission of CHANNEL ACTIVATE or MODE MODIFY withCHANNEL MODE = “data” for atransparent service on a full--rateTCH


Class : assignment



l1714 Duration of the overload situation

Name Q3 : btsOverloadDurationMoybtsOverloadDurationMaxbtsOverloadDurationCumbtsOverloadDurationEch

Object : bts

Function : duration of the overload situation: the number of free TCHs in the cellis lower than the minimum threshold, or the number of queued TCHrequests is greater than the threshold.Note that the number of free TCHsdoes not take preemptablePDTCHinto account.



Event : allocation/de--allocation of a TCH, queueing of a TCH request,liberation of a queued TCH request, block/unblock of a TCH, orTDMA attribution/removal


Class : allocation





CCT: Circuit calls on TCH channelBut it is not concerned byCCP (Circuit Calls on PDTCH preemptedto make a TCH channel) or CP calls (Com packet on PDTCHchannel).

l1715 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 preemptedPDTCH for dualband mobiles

Event : transmission of ASSIGNMENT COMMAND to the mobile


Class : assignment


Feature : Dualband cell management (TF875 -- V12)






PE/DCL/DD/0125411--9001--125



DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “immediate assignment procedure (normal completion)”


l1716 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 assignationsfor dualband mobiles

Event : receipt of ASSIGNMENT COMPLETE message by the BSC


Class : assignment









DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “immediate assignment procedure (normal completion)”DFD “Direct retry handover procedure”



l1717 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)






DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “immediate assignment procedure (normal completion)”

l1718 Number of frames TRAU downlink corrected

Name Q3 : abisTrauFrameCorrected

Object : bts

Function : number of frames TRAU downlink corrected







PE/DCL/DD/0125411--9001--125






Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “immediate assignment procedure (normal completion)”

l1719 Number of frames TRAU downlink that cannot be corrected

Name Q3 : abisTrauFrameMuted

Object : bts

Function : number of frames TRAU downlink that cannot be corrected













l1720 Number of radio frames uplink received

Name Q3 : radioFrameUlReceived

Object : bts

Function : number of radio frames uplink received











Note : FER monitoring only concerns the speech frames (Full Rate andEnhanced Full Rate) and does not depend on the ECU activationstatus.

l1721/0 Number of erroneous frames

Name Q3 : ecuActivation

Object : bts

Function : number of erroneous frames






PE/DCL/DD/0125411--9001--125











Note : FER monitoring only concerns the speech frames (Full Rate andEnhanced Full Rate) and does not depend on the ECU activationstatus.

l1722/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, orHO_REQUEST message


Class : asci


Feature : GSM--R





l1722/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, orHO_REQUEST message


Class : asci


Feature : GSM--R



l1723 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 presenteMLPP precedence > O&M thresholdVBS call in progress


Class : asci


Feature : GSM--R



Note : If several calls are in progress, only one counter update is performed.


PE/DCL/DD/0125411--9001--125


l1724 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 presenteMLPP precedence > O&M thresholdcall in progress


Class : asci


Feature : GSM--R



Note : If several calls are in progress, only one counter update is performed.

l1725 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





l1726/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 ratewithcause lack of resources

Event : configuration mismatch or response from radio allocator


Class : allocation






l1726/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 ratewithcause configuration not allowed

Event : configuration mismatch or response from radio allocator


Class : allocation







PE/DCL/DD/0125411--9001--125


l1730 Number of signaling channels allocated for replies to paging

Name Q3 : pagingResponse

Object : bts

Function : number of signaling channel allocation requests for “reply to pagingrequest” in the cell (cause = xx001 or xx100)

Event : receipt of CHANNEL REQUEST with cause “reply to pagingrequest”


Class : establishment









l1744 Number of TCH/FR or preempted PDTCH allocated in the cell

Name Q3 : tchFrAllocated

Object : bts

Function : number of TCH/FR or preempted PDTCH allocated in the cell

Event : TCH/FR or preempted PDTCH allocation in the cell


Class : allocation




Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (no available resource for a PDTCHpreemption)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “immediate assignment procedure (normal completion)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”

l1744 Number of TCH/FR or preempted PDTCH allocated in the cell

Name Q3 : tchFrAllocatedTrZone


Function : number of TCH/FRor preempted PDTCHallocated in the inner or theouter zone of the cell

Event : TCH/FR or preempted PDTCH allocation in the cell


Class : allocation



PE/DCL/DD/0125411--9001--125


Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (no available resource for a PDTCHpreemption)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “immediate assignment procedure (normal completion)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”

l

1745/0 Number of Half--rate TCH allocations in the cell

Name Q3 : tchHrAllocatedtchHrAllocatedNsctchHrAllocatedTrZone


Function : number of half--rate TCH allocations in the cell

Event : allocation of a half rate TCH


Class : allocation




l1746 Average number of TCH/FR or preempted PDTCH used in the

concentric cell and zone

Name Q3 : tchFrAveragedUsedMoytchFrAveragedUsedMaxtchFrAveragedUsedCumtchFrAveragedUsedEchtchFrAveragedUsedTrZoneMaxtchFrAveragedUsedTrZoneMoytchFrAveragedUsedTrZoneCumtchFrAveragedUsedTrZoneEch


Function : average (= total number divided by number of samples) andmaximumnumber of TCH/FRor preemptedPDTCHused in the inneror outer zone of the cell, obtained through internal sampling.

Event : TCH/FR or preempted PDTCH allocation/deallocation:

allocation: step up by one the instantaneous value of the number ofTCH/FR or preempted PDTCH used in the cell or zone.deallocation: step down by one the instantaneous value of thenumber of TCH/FR or preempted PDTCH used in the cell or zone.


Class : allocation




Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (no available resource for a PDTCHpreemption)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”


PE/DCL/DD/0125411--9001--125


DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “immediate assignment procedure (normal completion)”DFD “Immediate assignment paging procedure (normalcompletion)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”

l1747/0 Average, maximum, mimium, and total number of half rate

TCH allocations

Name Q3 : tchHrAveragedUsedCumtchHrAveragedUsedEchtchHrAveragedUsedMaxtchHrAveragedUsedMoytchHrAveragedUsedTrZoneCumtchHrAveragedUsedTrZoneEchtchHrAveragedUsedTrZoneMaxtchHrAveragedUsedTrZoneMoy


Function : average and maximum number of half rate TCH allocations.

Event : allocation/de--allocation of a half rate TCH.


Class : setup


l1748 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





l1749 Number of successful immediate assignments

Name Q3 : immediateAssignmentSuccess

Object : bts

Function : number of immediate assignments

Event : transmission of IMMEDIATE ASSIGNMENT on receipt ofCHANNEL REQUEST


Class : setup



1750 Number of ESTABLISH INDICATION messages in establish-ment phase received

Name Q3 : estabIndicSignallingestabIndicSignallingEmerency8westabIndicSignallingPiggybacked

Object : bts

Function : number of ESTABLISH INDICATION messages received onSDCCH or TCH if no SDCCH is available

Event : receipt of ESTABLISH INDICATION


Class : setup



PE/DCL/DD/0125411--9001--125



l1751 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


l1752 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 “signallingphase” 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


Data flows : Refer to Chapter 1DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”

l1754 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


Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”

1755/0 Number of faults relating to the PCM with cause external PCMfault

Name Q3 : pcmFaultExternal

Object : pcmCircuit

Function : number of faults relating to PCM


PE/DCL/DD/0125411--9001--125


Event : external PCM fault


Class : PCM link


l1755/1 Number of faults relating to the PCM with cause internal fault

Name Q3 : pcmFaultInternal

Object : pcmCircuit


Event : internal PCM fault


Class : PCM link


l1755/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


l1755/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




l1756/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 cellwith cause lack of radio resources

Event : lack of radio resources


Class : handover


l1756/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 cellwith cause receipt from the BTS of CHANNEL ACTIVATE NACKmessage

Event : receipt from the BTS of a CHANNEL ACTIVATE NACK message


Class : handover



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 cellwith cause expiration of TchnAck timer

Event : expiration of TchnAck timer


Class : handover



PE/DCL/DD/0125411--9001--125


l1757/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 thecell with cause lack of radio resources



Class : handover


l1757/1 Number of refusals to accept an intra--cell handover on SDCCH

in the cell with cause receipt from the BTS of a CHANNELACTIVATE NACK message

Name Q3 : hoFailureIntraBtsSdcchChannelActivateNack

Object : bts

Function : number of refusals to accept an intra--cell handover on SDCCH in thecell with cause receipt from the BTS of CHANNEL ACTIVATENACK message



Class : handover



the cell with cause expiration of TchnAck timer

Name Q3 : hoFailureIntraBtsSdcchTchnAckTimerExp

Object : bts

Function : number of refusals to accept an intra--cell handover on SDCCH in thecell with cause expiration of TchnAck timer



Class : handover




l1758/0 Number of incoming intra BSS handover requests, on TCHwith

cause lack of radio resources, which have been refused

Name Q3 : hoFailureIncomingIntraBssTchRadioLack

Object : bts

Function : number of incoming intraBSS handover requests, on TCHwith causelack of radio resources, which have been refused



Class : handover



cause incominghandovernot allowed in the cell,which havebeenrefused

Name Q3 : hoFailureIncomingIntraBssTchHoNotAllowed

Object : bts

Function : number of incoming intraBSS handover requests, on TCHwith causeincoming handover not allowed in the cell, which have been refused

Event : incoming handover not allowed in the cell


Class : handover



cause receipt from the BTS of a CHANNEL ACTIVATE NACKmessage, which have been refused

Name Q3 : hoFailureIncomingIntraBssTchChannelActivateNack

Object : bts

Function : number of incoming intraBSS handover requests, on TCHwith causereceipt from the BTS of a CHANNEL ACTIVATE NACKmessage,which have been refused



Class : handover



PE/DCL/DD/0125411--9001--125



cause expiration of TchnAck timer, which have been refused

Name Q3 : hoFailureIncomingIntraBssTchTchnAckTimerExp

Object : bts

Function : number of incoming intraBSS handover requests, on TCHwith causeexpiration of TchnAck timer, which have been refused



Class : handover


l1758/4 Number of incoming intra BSS handover requests, on TCH with

cause target cell and speech coding algorithm incompatible ORtarget cell and channel mode incompatible AND no possiblefallback

Name Q3 : hoFailureIncomingIntraBssTchIncompatible

Object : bts

Function : number of incoming intraBSShandover requests, onTCHwith causetarget cell and speech coding algorithm incompatible OR target celland channel mode incompatible AND no possible fallback

Event : target cell and speech coding algorithm incompatible OR target celland channel mode incompatible AND no possible fallback


Class : handover


Note : Incompatibility for target cell can be hardware (14K5 or HSCSD) orconfiguration (EFR & 14K5 & HSCSD).

l1759/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 withcause lack of radio resources, which have been refused





Class : handover



with cause incoming handover not allowed in the cell, whichhavebeen refused

Name Q3 : hoFailureIncomingIntraBssSdcchHoNotAllowed

Object : bts

Function : number of incoming intra BSS handover requests, on SDCCH withcause incoming handover not allowed in the cell, which have beenrefused



Class : handover



PE/DCL/DD/0125411--9001--125



with cause receipt from the BTS of a CHANNEL ACTIVATENACK message, which have been refused

Name Q3 : hoFailureIncomingIntraBssSdcchChannelActivateNack

Object : bts

Function : number of incoming intra BSS handover requests, on SDCCH withcause receipt from the BTS of a CHANNEL ACTIVATE NACKmessage, which have been refused



Class : handover



with cause expiration of TchnAck timer, which have been refused

Name Q3 : hoFailureIncomingIntraBssSdcchTchnAckTimerExp

Object : bts

Function : number of incoming intra BSS handover requests, on SDCCH withcause expiration of TchnAck timer, which have been refused



Class : handover


l1760/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 TCHwith causelack of radio resources, which have been refused



Class : handover





cause lack of terrestrial resources, which have been refused

Name Q3 : hoFailureIncomingInterBssTchTerrestLack

Object : bts

Function : number of incoming inter BSS handover requests, on TCHwith causelack of terrestrial resources, which have been refused

Event : lack of terrestrial resources


Class : handover




Name Q3 : hoFailureIncomingInterBssTchHoNotAllowed

Object : bts

Function : number of incoming inter BSS handover requests, on TCHwith causeincoming handover not allowed in the cell, which have been refused



Class : handover



cause receipt from the BTS of a CHANNEL ACTIVATE NACKmessage, which have been refused

Name Q3 : hoFailureIncomingInterBssTchChannelActivateNack

Object : bts

Function : number of incoming inter BSS handover requests, on TCHwith causereceipt from the BTS of a CHANNEL ACTIVATE NACKmessage,which have been refused



Class : handover



PE/DCL/DD/0125411--9001--125




Name Q3 : hoFailureIncomingInterBssTchTchnAckTimerExp

Object : bts

Function : number of incoming inter BSS handover requests, on TCHwith causeexpiration of TchnAck timer, which have been refused



Class : handover



cause CIC and speech coding algorithm incompatible OR targetcell and speech coding algorithm incompatible OR CIC andchannel mode incompatible OR target cell and channel modeincompatible AND no possible fallback

Name Q3 : hoFailureIncomingInterBssTchCICIncompatible

Object : bts

Function : number of incoming inter BSS handover requests, on TCHwith causeCIC and speech coding algorithm incompatible OR target cell andspeech coding algorithm incompatible OR CIC and channel modeincompatible OR target cell and channel mode incompatible AND nopossible fallback

Event : CIC and speech coding algorithm incompatible OR target cell andspeech coding algorithm incompatible OR CIC and channel modeincompatible OR target cell and channel mode incompatible AND nopossible fallback


Class : handover


Note : Incompatibility for CIC can be hardware or configuration.

Incompatibility for target cell can be hardware or configuration.



l1761/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 withcause lack of radio resources, which have been refused



Class : handover



with cause lack of terrestrial resources, which have been refused

Name Q3 : hoFailureIncomingInterBssSdcchTerrestLack

Object : bts

Function : number of incoming inter BSS handover requests, on SDCCH withcause lack of terrestrial resources, which have been refused



Class : handover




Name Q3 : hoFailureIncomingInterBssSdcchHoNotAllowed

Object : bts

Function : number of incoming inter BSS handover requests, on SDCCH withcause incoming handover not allowed in the cell, which have beenrefused



Class : handover



PE/DCL/DD/0125411--9001--125




Name Q3 : hoFailureIncomingInterBssSdcchChannelActivateNack

Object : bts

Function : number of incoming inter BSS handover requests, on SDCCH withcause receipt from the BTS of a CHANNEL ACTIVATE NACKmessage, which have been refused



Class : handover




Name Q3 : hoFailureIncomingInterBssSdcchTchnAckTimerExp

Object : bts

Function : number of incoming inter BSS handover requests, on SDCCH withcause expiration of TchnAck timer, which have been refused



Class : handover


l1762/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 TCHwith causelack of radio resources, which have been refused



Class : handover






Name Q3 : hoFailureOutgoingIntraBssTchHoNotAllowed

Object : bts

Function : number of outgoing intra BSS handover requests, on TCHwith causeincoming handover not allowed in the cell, which have been refused



Class : handover


l1762/2 Number of outgoing intra BSS handover requests, on TCH


Name Q3 : hoFailureOutgoingIntraBssTchChannelActivateNack

Object : bts

Function : number of outgoing intra BSS handover requests, on TCHwith causereceipt from the BTS of a CHANNEL ACTIVATE NACKmessage,which have been refused



Class : handover




Name Q3 : hoFailureOutgoingIntraBssTchTchnAckTimerExp

Object : bts

Function : number of outgoing intra BSS handover requests, on TCHwith causeexpiration of TchnAck timer, which have been refused



Class : handover



PE/DCL/DD/0125411--9001--125




Name Q3 : hoFailureOutgoingIntraBssTchIncompatible

Object : bts

Function : number of outgoing intra BSS handover requests, on TCHwith causetarget cell and speech coding algorithm incompatible OR target celland channel mode incompatible AND no possible fallback, whichhave been refused

Event : target cell and speech coding algorithm incompatible OR target celland channel mode incompatible AND no possible fallback


Class : handover


Note : Incompatibility for target cell can be hardware or configuration

l1763/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 withcause lack of radio resources, which have been refused



Class : handover




Name Q3 : hoFailureOutgoingIntraBssSdcchHoNotAllowed

Object : bts

Function : number of outgoing intra BSS handover requests, on SDCCH withcause incoming handover not allowed in the cell, which have beenrefused





Class : handover




Name Q3 : hoFailureOutgoingIntraBssSdcchChannelActivateNack

Object : bts

Function : number of outgoing intra BSS handover requests, on SDCCH withcause receipt from the BTS of a CHANNEL ACTIVATE NACKmessage, which have been refused



Class : handover




Name Q3 : hoFailureOutgoingIntraBssSdcchTchnAckTimerExp

Object : bts

Function : number of outgoing intra BSS handover requests, on SDCCH withcause expiration of TchnAck timer, which have been refused



Class : handover


l1764/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 TCHwith causelack of radio resources, which have been refused


PE/DCL/DD/0125411--9001--125




Class : handover



cause lack of terrestrial resources, which have been refused

Name Q3 : hoFailureOutgoingInterBssTchTerrestLack

Object : bts

Function : number of outgoing inter BSS handover requests, on TCHwith causelack of terrestrial resources, which have been refused



Class : handover




Name Q3 : hoFailureOutgoingInterBssTchHoNotAllowed

Object : bts

Function : number of outgoing inter BSS handover requests, on TCHwith causeincoming handover not allowed in the cell, which have been refused



Class : handover



cause T7 timer expiration, which have been refused

Name Q3 : hoFailureOutgoingInterBssTchT7TimerExp

Object : bts

Function : number of outgoing inter BSS handover requests, on TCHwith causeT7 timer expiration, which have been refused



Event : T7 timer expiration


Class : handover



cause “every other cases”, which have been refused

Name Q3 : hoFailureOutgoingInterBssTchOtherCases

Object : bts

Function : number of outgoing inter BSS handover requests, on TCHwith cause“every other cases”, which have been refused

Event : “every other cases”


Class : handover



cause CIC and speech coding algorithm incompatible OR targetcell and speech coding algorithm incompatible OR CIC andchannel mode incompatible OR target cell and channel modeincompatible AND no possible fallback, which have beenrefused

Name Q3 : hoFailureOutgoingInterBssTchIncompatible

Object : bts

Function : number of outgoing inter BSS handover requests, on TCHwith causeCIC and speech coding algorithm incompatible OR target cell andspeech coding algorithm incompatible OR CIC and channel modeincompatible OR target cell and channel mode incompatible AND nopossible fallback, which have been refused



Class : handover


Note : Incompatibility for CIC or target cell can be hardware orconfiguration.


PE/DCL/DD/0125411--9001--125


l1765/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 withcause lack of radio resources, which have been refused



Class : handover



with cause lack of terrestrial resources, which have been refused

Name Q3 : hoFailureOutgoingInterBssSdcchTerrestLack

Object : bts

Function : number of outgoing inter BSS handover requests, on SDCCH withcause lack of terrestrial resources, which have been refused



Class : handover



with cause incoming handover not allowed in the cell, whichhave been refused

Name Q3 : hoFailureOutgoingInterBssSdcchHoNotAllowed

Object : bts

Function : number of outgoing inter BSS handover requests, on SDCCH withcause incoming handover not allowed in the cell, which have beenrefused



Class : handover





with cause T7 timer expiration, which have been refused

Name Q3 : hoFailureOutgoingInterBssSdcchT7TimerExp

Object : bts

Function : number of outgoing inter BSS handover requests, on SDCCH withcause T7 timer expiration, which have been refused



Class : handover



with cause “every other cases”, which have been refused

Name Q3 : hoFailureOutgoingInterBssSdcchOtherCase

Object : bts

Function : number of outgoing inter BSS handover requests, on SDCCH withcause “every other cases”, which have been refused.



Class : handover


l1768/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 causedby a mobile that returns to the old channel (HANDOVER FAILUREbefore T3103 timer expiration).

Event : mobile returns to the old channel (HANDOVER FAILURE beforeT3103 timer expiration)


Class : handover



PE/DCL/DD/0125411--9001--125



on TCH.

Name Q3 : hoUnsuccessOutgoingIntraCellTchT3103TimerExp

Object : bts

Function : number of failures to execute intra_bss handover from the cell causedby T3103 timer expiration.



Class : handover


l1769/0 Number of failures to execute intra_bss handover from the cell on

SDCCH.

Name Q3 : hoUnsuccessOutgoingIntraCellSdcchReturnOldChannel

Object : bts

Function : number of failures to execute intra_bss handover from the cell causedby a mobile that returns to the old channel (HANDOVER FAILUREbefore T3103 timer expiration).



Class : handover



on SDCCH.

Name Q3 : hoUnsuccessOutgoingIntraCellSdcchT3103TimerExp

Object : bts

Function : number of failures to execute intra_bss handover from the cell causedby T3103 timer expiration.



Class : handover




l1770/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 TCHin the cell with cause mobile returns to the old channel

Event : mobile returns to the old channel


Class : handover



TCH in the cell with cause T3103 timer expiration

Name Q3 : hoUnsuccessOutgoingInterCellTchT3103TimerExphoUnsuccessOutgoingInterCellTchT3107TimerExp8w

Object : bts

Function : number of refusals to accept an outgoing inter--cell handover on TCHin the cell with cause T3103 timer expiration



Class : handover



TCH in the cell with cause “every other cases”

Name Q3 : hoUnsuccessOutgoingInterCellTchOtherCases

Object : bts

Function : number of refusals to accept an outgoing inter--cell handover on TCHin the cell with cause “every other cases”



Class : handover



PE/DCL/DD/0125411--9001--125



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 onSDCCH in the cell with cause mobile returns to the old channel



Class : handover



SDCCH in the cell with cause T3103 timer expiration

Name Q3 : hoUnsuccessOutgoingInterCellSdcchT3103TimerExp

Object : bts

Function : number of refusals to accept an outgoing inter--cell handover onSDCCH in the cell with cause T3103 timer expiration



Class : handover



SDCCH in the cell with cause “every other cases”

Name Q3 : hoUnsuccessOutgoingInterCellSdcchOtherCases

Object : bts

Function : number of refusals to accept an outgoing inter--cell handover onSDCCH in the cell with cause “every other cases”



Class : handover




l1772/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 TCHcaused by a mobile that returns to the old channel (HANDOVERFAILURE before T3103 timer expiration).



Class : handover



TCH.Name Q3 : hoUnsuccessIncomingIntraCellTchT3103TimerExp

Object : bts

Function : number of failures to execute intra_bss handover to the cell on TCHcaused by T3103 timer expiration.



Class : handover



SDCCH.

Name Q3 : hoUnsuccessIncomingIntraCellSdcchReturnOldChannel

Object : bts

Function : number of failures to execute intra_bss handover to the cell onSDCCH caused by a mobile that returns to the old channel(HANDOVER FAILURE before T3103 timer expiration).



Class : handover



PE/DCL/DD/0125411--9001--125



SDCCH.Name Q3 : hoUnsuccessIncomingIntraCellSdcchT3103TimerExp

Object : bts

Function : number of failures to execute intra_bss handover to the cell onSDCCH caused by T3103 timer expiration.



Class : handover


l1774/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 TCHin the cell with cause timer expiration

Event : timer expiration (expiration of ThndCom timer before receipt ofABIS HANDOVER COMPLETE from the MSC or receipt ofCLEAR COMMAND message from the MSC)


Class : handover



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 TCHin the cell with cause “every other cases”

Event : “every other cases” (receipt of a CLEARCOMMANDmessage witha cause set to a different value than “handover successful” or “Callcontrol”


Class : handover





SDCCH in the cell with cause timer expiration

Name Q3 : hoUnsuccessIncomingInterBssSdcchTimerExp

Object : bts

Function : number of refusals to accept an incoming inter--bss handover onSDCCH in the cell with cause timer expiration

Event : timer expiration (expiration of ThndCom timer before receipt ofABIS HANDOVER COMPLETE from the MSC or receipt ofCLEAR COMMAND message from the MSC)


Class : handover



SDCCH in the cell with cause “every other cases”

Name Q3 : hoUnsuccessIncomingInterBssSdcchOtherCases

Object : bts

Function : number of refusals to accept an incoming inter--bss handover onSDCCH in the cell with cause “every other cases”

Event : “every other cases” (receipt of a CLEARCOMMANDmessage witha cause set to a different value than “handover successful” or “Callcontrol”


Class : handover


l1776 Number of handovers on TCH required

Name Q3 : hoRequiredTch

Object : bts

Function : number of handovers on TCH required


PE/DCL/DD/0125411--9001--125




Class : handover



DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”

l1777 Number of handovers on SDCCH required

Name Q3 : hoRequiredSdcch

Object : bts

Function : number of handovers on SDCCH required



Class : handover


l1778 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 and1163/24 counters


Class : release





l1779 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 “trafficphase”

Event : All the event causes of 1164/n counters except the one of 1164/20counter


Class : release





1780/0 Number of successful outgoing classic handovers from the cell

Name Q3 : hoSuccessOutgoingTch

Object : bts

Function : number of successful outgoing intra–bss or inter–bss handovers onTCH using only classic handovers and no AMR handovers


PE/DCL/DD/0125411--9001--125


Event : receipt of HANDOVER COMPLETE message from the MS(intra–bss handover) or receipt of CLEAR COMMAND messagefrom the MSC with a handover cause “handover successful”(inter–bss handover)


Class : handover







Name Q3 : amrFrHoSuccessOutgoingTch

Object : bts

Function : number of successful outgoing intra–bss or inter–bss handovers onTCH using AMR full rate



Class : handover









Name Q3 : amrHrHoSuccessOutgoingTch

Object : bts

Function : number of successful outgoing intra–bss or inter–bss handovers onTCH using AMR half rate



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 onTCH

Event : receipt of HANDOVER COMPLETE message from the MS(intra–bss and inter--bss handover)


Class : handover




PE/DCL/DD/0125411--9001--125


l1782 Number of handover requirements which are not treated by the

BSC because the ping--pong handover configuration is notallowed

Name Q3 : hoBtsRejected

Object : bts

Function : number of handover requirements which are not treated by the BSCbecause the ping--pong handover configuration is not allowed

Event : receipt of HANDOVER INDICATION message from the BTS


Class : handover





Feature : General protection against ping--pong handovers (TF821 -- V12)

Note : A non essential handover to a cell from which the mobile has alreadybeen rejected due to alarm reason is not treated.This counter is incremented only for ping--pong handoverfunctionality.


from themain frequency band to the same frequency band of thenetwork

Name Q3 : hoRequestOutgoingMbandMbandMsDualb

Object : bts

Function : number of outgoing, intra-bss or inter-bss handovers, on TCH,requested from the main frequency band to the same frequency bandof the network

Event : attempt to select a resource of an eligible cell


Class : handover










Note : The originated and target resources are in the main frequency band ofthe network.


from the second frequency band to the same frequency band ofthe network

Name Q3 : hoRequestOutgoingEbandEbandMsDualb

Object : bts

Function : number of outgoing, intra-bss or inter-bss handovers, on TCH,requested from the second frequency band to the same frequencyband of the network



Class : handover







PE/DCL/DD/0125411--9001--125




Note : The originated and target resources are in the second frequency bandof the network.


from the second frequency band to the main frequency band ofthe network

Name Q3 : hoRequestOutgoingEbandMbandMsDualb

Object : bts

Function : number of outgoing, intra-bss or inter-bss handovers, on TCH,requested from the second frequency band themain frequency bandofthe network



Class : handover










Note : The target resource is in the main frequency band of the networkwhereas the originated resource is in the second frequency band.


from themain frequency band to the same frequency band of thenetwork

Name Q3 : hoSuccessOutgoingMbandMbandMsDualb

Object : bts

Function : number of successful outgoing, intra-bss or inter-bss handovers, onTCH, from the main frequency band to the same frequency band ofthe network



Class : handover








PE/DCL/DD/0125411--9001--125



from the second frequency band to the same frequency band ofthe network

Name Q3 : hoSuccessOutgoingEbandEbandMsDualb

Object : bts

Function : number of successful outgoing, intra-bss or inter-bss handovers, onTCH, from the second frequency band to the same frequency band ofthe network



Class : handover








from the second frequency band to the main frequency band ofthe network

Name Q3 : hoSuccessOutgoingEbandMbandMsDualb

Object : bts

Function : number of successful outgoing, intra-bss or inter-bss handovers, onTCH, from the second frequency band to the main frequency band ofthe network





Class : handover











l1789 Number of outgoing handover executions by dualband mobiles

for the cell from the main frequency band to the secondfrequency band of the network

Name Q3 : hoExecutionOutgoingMbandEbandMsDualb

Object : bts

Function : number of outgoing handover (intra-bss or inter-bss) executions bydualband mobiles for the cell, from the main frequency band to thesecond frequency band of the network

Event : transmission of ASSIGN COMMAND message


Class : handover



PE/DCL/DD/0125411--9001--125










for the cell from themain frequency band to the same frequencyband of the network

Name Q3 : hoExecutionOutgoingMbandMbandMsDualb

Object : bts

Function : number of outgoing handover (intra-bss or inter-bss) executions bydualband mobiles for the cell, from the main frequency band to thesame frequency band of the network



Class : handover














for the cell from the second frequency band to the samefrequency band of the network

Name Q3 : hoExecutionOutgoingEbandEbandMsDualb

Object : bts

Function : number of outgoing handover (intra-bss or inter-bss) executions bydualband mobiles for the cell, from the second frequency band to thesame frequency band of the network



Class : handover












PE/DCL/DD/0125411--9001--125



for the cell from the second frequency band to the mainfrequency band of the network

Name Q3 : hoExecutionOutgoingEbandMbandMsDualb

Object : bts

Function : number of outgoing handover (intra-bss or inter-bss) executions bydualband mobiles for the cell, from the second frequency band to themain frequency band of the network



Class : handover









l1793 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 cellfor dualband mobiles



Event : attempt to select the cell as a serving cellType : raw permanent

Class : handover

Source : recorded by the BSCPreciseincrementation conditions :



Feature : Dualband cell management (TF875 -- V12)Data flows : Refer to Chapter 1


Note : The counter is incremented at the end of the handover.

l1794 Number of incoming intra BSS handovers on TCH execution

attempts for dualband mobilesName Q3 : hoExecutionIncomingIntraBssTchMsDualbObject : bts

Function : number of attempts to execute incoming intraBSShandovers onTCHin the cell for dualband mobiles

Event : transmission of HANDOVER COMMAND message to the servingcell


Class : handoverSource : recorded by the BSC





PE/DCL/DD/0125411--9001--125




Note : This counter is incremented at the end of the handover and on TCHonly.

l1795 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 thecell for dualband mobiles

Event : receipt of HANDOVER COMPLETE from mobile


Class : handover










l1796 Number of intra-bts handovers on TCH requested by dualband

mobilesName Q3 : hoRequestIntraBtsMsDualb

Object : bts

Function : number of intra-bts handovers on TCH requested in the cell bydualband mobiles

Event : attempt to select a TCH in the cell


Class : handover






Note : This counter is incremented at the end of the handover.

l1797 Number of intra-bts handovers on TCH executed for dualband

mobilesName Q3 : hoExecutionIntraBtsMsDualb

Object : bts

Function : number of attempts to execute intra-bts handovers on TCH in the cellby dualband mobiles



Class : handover






PE/DCL/DD/0125411--9001--125



l1798 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 fordualband mobiles

Event : receipt of ASSIGN COMPLETE from the mobile


Class : handover







l1799 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 adualband (or concentric or dual--coupling) cell

Event : receipt of an ASSIGN COMPLETE message on TCH or preemptedPDTCH from the mobile


Class : assignment









l1800/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 thecell

Event : receipt of HO_COMPLETE, CLEAR_COMMAND,ASSIGN_COMPLETE messages


Class : asci





l1800/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 inthe cell


PE/DCL/DD/0125411--9001--125


Event : receipt of HO_COMPLETE, CLEAR_COMMAND,ASSIGN_COMPLETE messages


Class : asci





l1801/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 tohopping channel)


Class : equipment






l1801/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 tonon--hopping channel)


Class : equipment






l1802/0 Number of tiering handover successes: Handover from large

pattern to small patternName Q3 : hoSuccessTieringTchLargeToSmallPatternObject : bts

Function : Number of tiering handover successes

Event : handover from large pattern to small pattern (non--hopping channel tohopping channel)


Class : equipment






l1802/1 Number of tiering handover successes: Handover from small

pattern to large patternName Q3 : hoSuccessTieringTchSmallToLargePattern

Object : btsFunction : Number of tiering handover successes


PE/DCL/DD/0125411--9001--125


Event : handover from small pattern to large pattern (hopping channel tonon--hopping channel)


Class : equipment







l1803/0 Number of rejected calls on paging requests due to overload

Name Q3 : cgOverloadRejectedOpPageReqCg0cgOverloadRejectedOpPageReqCg1cgOverloadRejectedOpPageReqCg2

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 boardconcerning the paging request is in overload situation


Class : equipment









Note : cgOverloadRejectedOpPageReqCg2 is not significant since theoverload on paging requests is onlymeasured on BIFP boards (cpue0and cpue1).

l1803/1 Number of rejected calls on channel requests due to overload

Name Q3 : cgOverloadRejectedOpChannelReqCg0cgOverloadRejectedOpChannelReqCg1cgOverloadRejectedOpChannelReqCg2

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 boardconcerning the channel request is in overload situation


Class : equipment







PE/DCL/DD/0125411--9001--125



Note : cgOverloadRejectedOpChannelReqcg2 is not significant since theoverload on channel requests is onlymeasured onBIFP boards (cpue0and cpue1).

l1803/2 Number of rejected calls on establish indication due to overload

Name Q3 : cgOverloadRejectedOpEstablishIndCg0cgOverloadRejectedOpEstablishIndCg1cgOverloadRejectedOpEstablishIndCg2

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 boardconcerning the establish indication is in overload situation


Class : equipment







Note : cgOverloadRejectedOpEstablishIndCg2 is not significant sincethe overload on establish indication is only measured on BIFP boards(cpue0 and cpue1).



31803/3 Number of rejected calls on handover requests due to overload

Name Q3 : cgOverloadRejectedOpHoReqCg0cgOverloadRejectedOpHoReqCg1cgOverloadRejectedOpHoReqCg2

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 boardconcerning the handover request is in overload situation


Class : equipment







Note : cgOverloadRejectedOpHoReqCg2 is not significant since theoverload on handover requests is only measured on BIFP boards(cpue0 and cpue1).

31803/4 Number of rejections on paging requests due to an

overloaded cell

Name Q3 : cgOverloadRejectedOpPageReqBtsCg0cgOverloadRejectedOpPageReqBtsCg1cgOverloadRejectedOpPageReqBtsCg2

Object : bsc


PE/DCL/DD/0125411--9001--125


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 cellwhen at least one board concerning the paging request is in overloadsituation


Class : equipment




CCT: Circuit calls on TCH channelCCP: Circuit Calls on PDTCHpreempted tomake aTCHchannel,

but it is not concerned by CP calls (Com packet on PDTCHchannel).


Note : For a same originating paging request message, this counter will beraised as many times as there are overloaded target cells.

1803/5 number of rejected sms--cb messages due to overload situation

Name Q3 : cgOverloadRejectedOpSmsCbCg0cgOverloadRejectedOpSmsCbCg1cgOverloadRejectedOpSmsCbCg2

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 cellwhen at least one board concerning the sms--cbmessage is in overloadsituation


Class : equipment






Feature : CR Q00590181


l1804 Number of delete indication messages received

Name Q3 : deleteIndication

Object : bts

Function : number of delete indication messages received. A delete indication issent each time there is too much queued immediate assignmentmessages.

Event : receipt of a DELETE INDICATION message from the BTS


Class : asci



l1805 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 OneManagement


PE/DCL/DD/0125411--9001--125


Event : receipt of a STOP MEASUREMENT ACK message from the BTS


Class : asciSource : recorded by the BSC




Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “queuing of the assignment procedure (normal completion)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”DFD “Radio channel release DEACTIVATE SACCH ACKprocedure (normal completion)”DFD “Radio channel release RELEASE INDICATION procedure(normal completion)DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”

l1806 Number of MS decrement power controls ordered by the Layer

One ManagementName Q3 : msPowerDecControlObject : bts

Function : number of MS decrement power controls ordered by the Layer OneManagement










l1807 Number of BS increment power controls ordered by the Layer

One ManagementName Q3 : bsPowerIncControlObject : bts

Function : number of BS increment power controls ordered by the Layer OneManagement


PE/DCL/DD/0125411--9001--125









l1808 Number of BS decrement power controls ordered by the Layer

One ManagementName Q3 : bsPowerDecControlObject : bts

Function : number of BS decrement power controls ordered by the Layer OneManagement





Class : asciSource : recorded by the BSCFeature : GSM--R (V12)




l1809/0 Average timing advance value for the communications in the cellName Q3 : timingAdvanceAverage

timingAdvanceAverageTrZone


Function : average timing advance value for the communications in the the cell(only for communications on TCH channel)


PE/DCL/DD/0125411--9001--125




Class : asci





Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Radio channel release DEACTIVATE SACCH ACKprocedure (normal completion)”DFD “Radio channel release RELEASE INDICATION procedure(normal completion)DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”

Note : The value given by the BTS is the average timing advance percommunication (this value is multiplexed by the C1600 value:connectionDurationTch)



l1809/1 Maximum timing advance value for the communications in the

cell

Name Q3 : timingAdvanceMaximumtimingAdvanceMaximumTrZone


Function : maximum timing advance value for the communications in the inneror the outer zone of the cell (only for communications on TCHchannel)



Class : asci














PE/DCL/DD/0125411--9001--125


DFD “Radio channel release RELEASE INDICATION procedure(normal completion)DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”

Note : The value given by the BTS is the maximum timing advance percommunication (the maximum value for all the communications inthe transceiverZone of cell)

l1810 Average and maximum numbers of configurated TCH full rate

resource

Name Q3 : tchFrAverageConfiguratedtchFrAverageConfiguratedMoytchFrAverageConfiguratedMaxtchFrAverageConfiguratedCumtchFrAverageConfiguratedEchtchFrAverageConfiguratedTrZoneMoytchFrAverageConfiguratedTrZoneMaxtchFrAverageConfiguratedTrZoneCumtchFrAverageConfiguratedTrZoneEch


Function : average and maximum numbers of configurated TCH full rateresource (resource configured by the OMC; it can be available orunavailable). Preemptable PDTCHs are not taken into account.

Event : receipt of a TGE from the OMC modifying the number of TCHresources in the cell


Class : asci






Note : This resource configured by the OMC may be available or not.



l1811 Average and maximum numbers of configurated SDCCH

resource

Name Q3 : sdcchAverageConfiguratedMoysdcchAverageConfiguratedMaxsdcchAverageConfiguratedCumsdcchAverageConfiguratedEchsdcchAverageConfiguratedTrZoneMoysdcchAverageConfiguratedTrZoneMaxsdcchAverageConfiguratedTrZoneCumsdcchAverageConfiguratedTrZoneEch


Function : average and maximum numbers of configurated SDCCH resource(= resource configured by the OMC; it can be available orunavailable)

Event : receipt of a TGE from the OMC modifying the number of SDCCHresources in the inner or the outer zone of the cell


Class : asci





Note : This resource configured by the OMC may be available or not.


PE/DCL/DD/0125411--9001--125


l1812 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 : allocatedCircuitTsallocatedCircuitTsMoyallocatedCircuitTsMaxallocatedCircuitTsCumallocatedCircuitTsEchallocatedCircuitTsTrZoneCumallocatedCircuitTsTrZoneMaxallocatedCircuitTsTrZoneMoyallocatedCircuitTsTrZoneEch


Function : Minimum, maximum, average, and cumulative number of activatedand non activated circuit TS (all TCHs and PDTCHs activated fortraffic 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)








Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “queuing of the assignment procedure (normal completion)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on SIGNALLINGphase)”DFD “immediate assignment procedure (normal completion)”DFD “Intra cell handover procedure (normal completion withcommunication on TRAFFIC phase)”DFD “Inter BSS intra MSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “Direct retry handover procedure”DFD “Connection clearing required by the BSC procedure(communication on TRAFFIC phase)”DFD “Connection clearing required by the BSC procedure(communication on SIGNALING phase)”

l1813/0 Number of TS allocations for packet mode in the cellName Q3 : allocatedPacketTs

allocatedPacketTsMoyallocatedPacketTsMaxallocatedPacketTsCumallocatedPacketTsEchallocatedPacketTsTrZoneCumallocatedPacketTsTrZoneEchallocatedPacketTsTrZoneMaxallocatedPacketTsTrZoneMoy


Function : Minimum, maximum, average, and cumulative number of availablePDTCH for GPRS (= all configured PDTCHs not preempted fortraffic in circuit mode)

Event : PDTCH configuration or preemption / release of the GPRS channelby the BSC


Class : GPRS



PE/DCL/DD/0125411--9001--125


Feature : GPRS (TF1121 and TF1128 -- V12)



Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion)”DFD “GPRS procedure (no available resource for a PDTCHpreemption)” which shows that c1813 is decremented when noresource is available to perform a PDTCH preemptionCounts the preemption on PDTCHs not mapped on AGPRS; aswhen available PDTCHs are used for circut calls.This counter gives the number of PDTCH channels given to thePCU equipment.

l1813/1 Number of PDTCH configured on the cell

Name Q3 : totalNumberOfPacketTsCumtotalNumberOfPacketTsMaxtotalNumberOfPacketTsMoytotalNumberOfPacketTsEchtotalNumberOfPacketTsTrZoneMoytotalNumberOfPacketTsTrZoneMaxtotalNumberOfPacketTsTrZoneCumtotalNumberOfPacketTsTrZoneEch


Function : Minimum, maximum, average, and cumulative number of PDTCHconfigured on the cell (total number of available PDTCH)

Event : TDMA configuration/deconfiguration


Class : GPRS


Feature : GPRS (PM1367)



Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion)”DFD “GPRS procedure (no available resource for a PDTCHpreemption)” which shows that c1813 is decremented when noresource is available to perform a PDTCH preemptionCounts the preemption on PDTCHs not mapped on AGPRS; aswhen available PDTCHs are used for circuit calls.This counter gives the number of PDTCH channels given to thePCU equipment.

Note : V14 Counter

l1813/2 Number of PDTCH preempted

Name Q3 : totalNumberOfPacketTsUsedForCircuitMoytotalNumberOfPacketTsUsedForCircuitTrZoneMoytotalNumberOfPacketTsUsedForCircuitMaxtotalNumberOfPacketTsUsedForCircuitTrZoneMaxtotalNumberOfPacketTsUsedForCircuitCumtotalNumberOfPacketTsUsedForCircuitTrZoneCumtotalNumberOfPacketTsUsedForCircuitEchtotalNumberOfPacketTsUsedForCircuitTrZoneEch


Function : Minimum, maximum, average, and cumulative number of PDTCHpreempted (number of available PDTCH used for circuit PDTCH)

Event : Channel activation and RF channel release of a PDTCH


Class : GPRS


Feature : GPRS (PM136F)

Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion)”DFD “GPRS procedure (no available resource for a PDTCHpreemption)” which shows that c1813 is decremented when noresource is available to perform a PDTCH preemption.FDFCounts the preemption on PDTCHs not mapped on AGPRS; aswhen available PDTCHs are used for circuit calls.This counter gives the number of PDTCH channels given to thePCU equipment.

Note : V14 Counter


PE/DCL/DD/0125411--9001--125


l1814 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)


When GPRS is activated, this counter is concerned by CCP only(Circuit Calls on PDTCH preempted to make a TCH channel).

Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (no resource available for a PDTCHpreemption)”

l1815 Number of GPRS preemption failures (requests nacked by the

PCU)

Name Q3 : gprsPreemptionNack

Object : bts

Function : number of PDTCHpreemption failures (requests nacked by the PCU)

Event : receipt of a refusal message from the PCU to release its PDTCHchannel


Class : GPRS


Feature : GPRS (TF1121 -- V12)


When GPRS is activated, this counter is concerned by CCP only(Circuit Calls on PDTCH preempted to make a TCH channel).



Data flows : Refer to Chapter 1DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”

l1816/0 Path balance for all the communications on TCH full rate

channel or preempted PDTCH on the BCCH TDMA

Name Q3 : pathBalanceCumpathBalanceEchpathBalanceMoypathBalanceMax

Object : bts

Function : Averaging value of the path balance for all the communications onTCH full rate channel or preempted PDTCH on the BCCH TDMA

Event : Data are received by the BSC from the BTS in STOPMEASUREMENT ACK messages. For each communication, theBTS gives the number of measurements and the cumulated value.


Class : cell


Note : V14 counter

1821 Number of activated and non activated circuit TS for traffic incircuit 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 activatedand non activated circuit TS (all TCHs and PDTCHs activated fortraffic 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



PE/DCL/DD/0125411--9001--125







1822/0 Number of TS allocations for packet mode in the cell

Name Q3 : allocatedPacketTsCellMoy,allocatedPacketTsCellMax,allocatedPacketTsCellCum,allocatedPacketTsCellEch,

Object : bts

Function : Minimum, maximum, average, and cumulative number of availablePDTCH for GPRS (= all configured PDTCHs not preempted fortraffic in circuit mode)

Event : PDTCH configuration or preemption / release of the GPRS channelby the BSC


Class : GPRS



1822/1 Number of PDTCH configured on the cell

Name Q3 : totalNumberOfPacketTsCellMoy,totalNumberOfPacketTsCellMax,totalNumberOfPacketTsCellCum,totalNumberOfPacketTsCellEch

Object : bts

Function : Minimum, maximum, average, and cumulative number of PDTCHconfigured 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

Function : Minimum, maximum, average, and cumulative number of PDTCHpreempted (number of available PDTCH used for circuit PDTCH)

Event : Channel activation and RF channel release of a PDTCH


Class : GPRS


1823 Average duration to allocate all TCH/FRandpreemptedPDTCHresources

Name Q3 : allTchFrAllocatedTimeCellMoy,allTchFrAllocatedTimeCellMax,allTchFrAllocatedTimeCellCum,allTchFrAllocatedTimeCellEch,

Object : bts

Function : Number of milliseconds during which all the available TCH_FRresources and pre--emptable PDTCH resources are used. A blockedresource is neither considered as used nor available. This counter hasthe same definition as the counter 1057, only the location is different.

Event : startsmeasurement on allocation of all the available TCH full rate andpre--emptable PDTCH resources of the CELL and stops as soon as aresource is free. In case we got a pre--emption nack, the counter startsimmediately and stops as soon a resource is released or as soon as thetimer GprsPreemptionProtection elapses.


Class : GPRS


PE/DCL/DD/0125411--9001--125






1824/0 Average number of TCH/FR or preempted PDTCH used fortraffic in the zone (concentric cell)Counter value calculation:


Name Q3 : tchFrAveragedUsedTchAllocationCellMoy,tchFrAveragedUsedTchAllocationCellMaxtchFrAveragedUsedTchAllocationCellCumtchFrAveragedUsedTchAllocationCellEch

Object : bts

Function : average and maximum number of full rate TCH allocations orpreempted PDTCH (for screening 0 and 3). This counter has the samedefinition as the counter 1611, only the location is different.

Event : allocation/de--allocation of a full rate TCH or preempted PDTCH.


Class : GPRS









1824/1 Average number of TCH/FRused for call reestablishments in thezone (concentric cell) (primo-allocation)Counter value calculation:For a monozone network, the zone is the entire cell

Name Q3 : tchFrAveragedUsedPrimoAllocationCellMoy,tchFrAveragedUsedPrimoAllocationCellMax,tchFrAveragedUsedPrimoAllocationCellCum,tchFrAveragedUsedPrimoAllocationCellEch.

Object : bts


Event : allocation in �primo--allocation� (call re--establishment). Only for aTCH full rate channel.


Class : GPRS


When GPRS is activated, this counter is concerned by CCT (Circuitcalls on TCH channel), but not by CCP (Circuit Calls on PDTCHpreempted to make a TCH channel) or CP (Com packet on PDTCHchannel).This is because this counter is related to configured (static) TCH/FRchannel only, and does not take into account preempted PDTCH.


1824/2 Average number of TCH/FR used because of SDCCHunavailability in the zone (concentric cell)Counter value calculation:For a monozone network, the zone is the entire cell

Name Q3 : tchFrAveragedUsedOverflowAllocationCellMoy,tchFrAveragedUsedOverflowAllocationCellMax,tchFrAveragedUsedOverflowAllocationCellCum,tchFrAveragedUsedOverflowAllocationCellEch.

Object : bts



PE/DCL/DD/0125411--9001--125


Event : allocation for a SDCCH on overflowing (lack of SDCCH resources).For a TCH full rate channel


Class : GPRS


1824/3 Average andmaximumnumber ofWPS full rateTCHallocations

Name Q3 : tchFrAveragedUsedWpsCellMoy,tchFrAveragedUsedWpsCellMax,tchFrAveragedUsedWpsCellCum,tchFrAveragedUsedWpsCellEch.

Object : bts


Event : allocation of a TCH channel or a preempted PDTCH for a WPS call.


Class : GPRS

Preciseincrementation conditions : When GPRS is activated, this counter isconcerned byCCT (Circuit calls onTCH channel), but not by CCP (Circuit Calls onPDTCH preempted to make a TCH channel). This is because this counter is relatedto configured (static) TCH/FRchannel. This counter is pegged on the traffic channelallocation for a WPS call if the WPS Management flag is enabled. This counter ispegged on the traffic channel de--allocation for a call inititiated as a WPS call.





1825 Average number of TCH/FR and preemptable PDTCHavailablein multizone cellradio TS used for circuit call onlyradio TS shared between circuit services and packet data services

Counter value calculation:For a monozone network, the zone is the entire cellif the number of PDTCH in the cell is less than minNbrGprsTS, thenC1700_oz = Number_of_TCH_oz + Number_of_PDTCH_oz –Number_of_PDTCH_cellelseC1700_oz = Number_of_TCH_oz + Number_of_PDTCH_oz –minNbrGprsTSC1700_iz = Number_of_TCH_iz + Number_of_PDTCH_izWhere 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 countedas available. This counter is related to TCH_FR channel,pre--emptable PDTCH and PDTCH not allocated to PCUSN. Thiscounter has the same definition as the counter 1700, only the locationis different.

Event : attribution/removal of TDMA (faults and O&M interventions), noreception of SYS INFO 5 and 6 acknowledgment, or lack of radiochannels.


Class : GPRS



But it is not concerned byCP calls (Com packet on PDTCHchannel).To sum it up, this counter is related to TCH/FR channel, preemptablePDTCH and PDTCH not allocated to PCUSN.


PE/DCL/DD/0125411--9001--125


1826 Average number of TCH/FR or preempted PDTCH used in theconcentric cell and zone

Name Q3 : tchFrAveragedUsedCellMoy,tchFrAveragedUsedCellMax,tchFrAveragedUsedCellCum,tchFrAveragedUsedCellEch.

Object : bts

Function : average and maximum number of full rate TCH allocations andpreempted PDTCH. This counter has the same definition as thecounter 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 rateresource

Name Q3 : tchFrAverageConfiguratedCellMoy,tchFrAverageConfiguratedCellMax,tchFrAverageConfiguratedCellCum,tchFrAverageConfiguratedCellEch

Object : bts

Function : average andmaximumnumber of configurated TCHfull rate resource(= resource configured by the OMC. It can be available orunavailable). This counter has the same definition as the counter1810, only the location is different. Preemptable PDTCH are nottaken into account.

Event : Reception of a TGE from the OMC modifying the number of TCHresources in the cell.


Class : GPRS






l1834 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






In case of rejection, no distinction is made between CHANNELREQUESTS messages dedicated to Circuit Call or Packet Calls.


PE/DCL/DD/0125411--9001--125


l1835 Synthetic load on CPUM, CPUE<x>, SICD<y> board

Name Q3 : cardSynthLoadCpumMoycardSynthLoadCpumMaxcardSynthLoadCpumCumcardSynthLoadCpumEchcardSynthLoadCpue<x>Moy.....for x = 0 to 2cardSynthLoadCpue<x>MaxcardSynthLoadCpue<x>CumcardSynthLoadCpue<x>EchcardSynthLoadSicd<y>Moy.....for y = 0 to 9cardSynthLoadSicd<y>MaxcardSynthLoadSicd<y>CumcardSynthLoadSicd<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 %

Event : the synthetic load is generated every second


Class : equipment






Note : This counter is only read when the SICD board is in service.



l1839/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 acentral cell to a neighboring one because of Loss of Uplink power

Event : attempt of selection of an eligible cell resource


Class : asci




Note : This counter only applies on TCH channel.


from a central cell to a neighboring one: Loss of Downlink power

Name Q3 : hoNcellsRequestOutgoingDownlinkStrength


Function : number of outgoing intra--bss or inter--bss handover attempts from acentral cell to a neighboring one because of Loss of Downlink power



Class : asci






PE/DCL/DD/0125411--9001--125



from a central cell to a neighboring one: Loss of Uplink quality

Name Q3 : hoNcellsRequestOutgoingUplinkQuality


Function : number of outgoing intra--bss or inter--bss handover attempts from acentral cell to a neighboring one because of Loss of Uplink quality



Class : asci






from a central cell to a neighboring one: Loss of Downlinkquality

Name Q3 : hoNcellsRequestOutgoingDownlinkQuality


Function : number of outgoing intra--bss or inter--bss handover attempts from acentral cell to a neighboring one because of Loss of Downlink quality



Class : asci








from a central cell to a neighboring one: Distance

Name Q3 : hoNcellsRequestOutgoingDistance


Function : number of outgoing intra--bss or inter--bss handover attempts from acentral cell to a neighboring one because of distance



Class : asci






from a central cell to a neighboring one: Power Budget

Name Q3 : hoNcellsRequestOutgoingPowerBudget


Function : number of outgoing intra--bss or inter--bss handover attempts from acentral cell to a neighboring one because of power budget



Class : asci




PE/DCL/DD/0125411--9001--125





from a central cell to a neighboring one: Directed retry

Name Q3 : hoNcellsRequestOutgoingDirectedRetry


Function : number of outgoing intra--bss or inter--bss handover attempts from acentral cell to a neighboring one because of directed retry



Class : asci






from a central cell to a neighboring one: Forced handoverO&M

Name Q3 : hoNcellsRequestOutgoingInterCellOM


Function : number of outgoing intra--bss or inter--bss handover attempts from acentral cell to a neighboring one with cause “forced handover” fromthe L1M



Class : asci








from a central cell to a neighboring one: Traffic

Name Q3 : hoNcellsRequestOutgoingTraffic


Function : number of outgoing intra--bss or inter--bss handover attempts from acentral cell to a neighboring one with cause “traffic” from the L1M



Class : asci






from a central cell to a neighboring one: Other causes

Name Q3 : hoNcellsRequestOutgoingOther


Function : number of outgoing intra--bss or inter--bss handover attempts from acentral cell to a neighboring one for other causes



Class : asci




PE/DCL/DD/0125411--9001--125




l1840/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 acentral cell to a neighboring one because of Loss of Uplink power

Event : receipt of a CLEAR COMMAND message from the MSC with acause set to “handover successful” (inter--bss handovers) or receipt ofa HANDOVER COMPLETE message (intra--bss handovers)


Class : asci






from a central cell to a neighboring one: Loss of Downlink power

Name Q3 : hoNcellsSuccessOutgoingDownlinkStrength


Function : number of outgoing intra--bss or inter--bss handover successes from acentral cell to a neighboring one because of Loss of Downlink power



Class : asci








from a central cell to a neighboring one: Loss of Uplink quality

Name Q3 : hoNcellsSuccessOutgoingUplinkQuality


Function : number of outgoing intra--bss or inter--bss handover successes from acentral cell to a neighboring one because of Loss of Uplink quality



Class : asci






from a central cell to a neighboring one: Loss of Downlinkquality

Name Q3 : hoNcellsSuccessOutgoingDownlinkQuality


Function : number of outgoing intra--bss or inter--bss handover successes from acentral cell to a neighboring one because of Loss of Downlink quality


PE/DCL/DD/0125411--9001--125




Class : asci









Name Q3 : hoNcellsSuccessOutgoingDistance


Function : number of outgoing intra--bss or inter--bss handover attempts from acentral cell to a neighboring one because of distance



Class : asci











Name Q3 : hoNcellsSuccessOutgoingPowerBudget


Function : number of outgoing intra--bss or inter--bss handover successes from acentral cell to a neighboring one because of power budget



Class : asci






from a central cell to a neighboring one: Directed retry

Name Q3 : hoNcellsSuccessOutgoingDirectedRetry


Function : number of outgoing intra--bss or inter--bss handover successes from acentral cell to a neighboring one because of directed retry



Class : asci




PE/DCL/DD/0125411--9001--125





from a central cell to a neighboring one: Forced handoverO&M

Name Q3 : hoNcellsSuccessOutgoingInterCellOM


Function : number of outgoing intra--bss or inter--bss handover successes from acentral cell to a neighboring one with cause “forced handover” fromthe L1M



Class : asci






from a central cell to a neighboring one: Traffic

Name Q3 : hoNcellsSuccessOutgoingTraffic


Function : number of outgoing intra--bss or inter--bss handover successes from acentral cell to a neighboring one with cause “traffic” from the L1M



Class : asci








from a central cell to a neighboring one: Other causes

Name Q3 : hoNcellsSuccessOutgoingOther


Function : number of outgoing intra--bss or inter--bss handover successes from acentral cell to a neighboring one for other causes



Class : asci





l1841/0 Number of assignment request messages received: modification

from a SDCCH channel to a TCH or a preempted PDTCHchannel

Name Q3 : assignRequestSdcchToTchChannel

Object : bts

Function : number of assignment request messages received because of amodification from a SDCCH channel to a TCH or a preemptedPDTCH channel


PE/DCL/DD/0125411--9001--125


Event : receipt of a ASSIGNMENT REQUEST message from the MSCbecause of a modification from a SDCCH channel to a TCH or apreempted PDTCH channel


Class : assignment

Source : recorded by the BSCPreciseincrementation conditions :



Data flows : Refer to Chapter 1DFD “GPRS procedure -- preemption on PDTCH (normalcompletion in the case of Mobile Originating Call)”DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “GPRS procedure (no resource available for a PDTCHpreemption)”DFD “dedicated channel assignment procedure (no resourceavailable and queuing not activated)”DFD “dedicated channel assignment procedure (normalcompletion)”DFD “queuing of the assignment procedure (normal completion)”DFD “inter--cell intra BSC handover procedure (normalcompletion with communication on TRAFFIC phase)”DFD “connection clearing required by the MSC procedure(normal completion with communication on TRAFFIC phase)”DFD “Dedicated channel assignment modify procedure (normalcompletion)”DFD “Direct retry handover procedure”

l1841/1 Number of assignment request messages received: Cause other

than modification from a SDCCH channel to a TCH or apreempted PDTCH channel

Name Q3 : assignRequestOthers

Object : btsFunction : number of assignment request messages received because of a cause

other than a modification from a SDCCH channel to a TCH or apreempted PDTCH channel



Event : receipt of a ASSIGNMENT REQUEST message from the MSCbecause of a cause other a modification from a SDCCH channel to aTCH or a preempted PDTCH channel


Class : assignment





Data flows : Refer to Chapter 1DFD “Dedicated channel assignment modify procedure (normalcompletion)”DFD “Direct retry handover procedure”

l1842/0 Number of emission of ASSIGNMENT FAILURE messages on

theA interface:Modification from anSDCCH channel to aTCHor a preempted PDTCH channel

Name Q3 : assignRequestAintSdcchToTchChannel

Object : bts

Function : number of ASSIGNMENT FAILURE messages sent on theA interface because of a modification from a SDCCH channel to aTCH or a preempted PDTCH channel

Event : sending of an ASSIGNMENT FAILURE message to the MSCbecause of a modification from a SDCCH channel to a TCH or apreempted PDTCH channel


Class : assignment






PE/DCL/DD/0125411--9001--125


Data flows : Refer to Chapter 1DFD “GPRS procedure (negative acknowledgement by the PCUfor a PDTCH preemption)”DFD “GPRS procedure (no resource available for a PDTCHpreemption)”DFD “dedicated channel assignment procedure (no resourceavailable and queuing not activated)”

l1842/1 Number of emission of ASSIGNMENT FAILURE messages on

the A interface: Cause other than modification from a SDCCHchannel to a TCH or a preempted PDTCH channel

Name Q3 : assignRequestAintOthers

Object : bts

Function : number of ASSIGNMENT FAILURE messages sent on theA interface because of a cause other than a modification from aSDCCH channel to a TCH or a preempted PDTCH channel

Event : sending of an ASSIGNMENT FAILURE message to the MSCbecause of a cause other a modification from a SDCCH channel to aTCH or a preempted PDTCH channel


Class : assignment








2.3 Raw permanent BSS counters (BSC e3, AMR)

2.3.1 Raw permanent BSS counters (BSC e3)

l1507/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 (thiscounter is incremented if the local card is overloaded or the operationfamily named paging request is overloaded)

Event : receipt of a paging request when at least one card concerning thisoperation is in an overload situation


Class : equipment


Note : V14 counter

l1507/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 thisoperation is in an overload situation


Class : equipment


Note : V14 counter

l1507/2 Number of rejected establish indicationmessages due to overload

situation

Name Q3 : e3OverloadRejectedOpEstablishInd

Object : bsc

Function : number of rejected establish indication messages due to overloadsituation


PE/DCL/DD/0125411--9001--125


Event : receipt of an establish indication message when at least one cardconcerning this operation is in an overload situation


Class : equipment


Note : V14 counter

l1507/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 thisoperation is in an overload situation (receipt of a handover indicationmessage or attempt of outgoing internal or external handovers,incoming external handover request, local directed retry)


Class : equipment


Note : V14 counter

l1507/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 overloadedcell

Event : receipt of a paging request rejection caused by an overloaded cellwhen at least one card concerning this operation is in an overloadsituation (for the same originating paging request message, thiscounter will be increased each time the target cell is overloaded)


Class : equipment


Note : V14 counter



l1507/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 cellwhen at least one card concerning this operation is in an overloadsituation (for the same originating sms--cb message, this counter willbe increased each time the target cell is overloaded)


Class : equipment



l1612/0 Average and maximum number of half rate TCH allocationsName Q3 : tchHrAveragedUsed

Object : TDMA class and bts

Function : Average andmaximum number of half rate TCH (including PDTCH)allocations



Class : allocation



l1708/0 Number of channel activation fornon transparent data serviceon

half rate TCH.Name Q3 : channelActivateTchHrDataNT6000

Object : bts

Function : Cumulative number of channel activation for non transparent dataservice on half rate TCH.

Event : Transmission of a CHANNEL_ACTIVATE message or of aMODE_MODIFY message with aCHANNEL MODE record set to �data� for a non transparentservice on a half rate TCH.

Type : CUM

Source : TBD


PE/DCL/DD/0125411--9001--125



TCH allocations

Name Q3 : tchHrAveragedUsedNsc

Object : bts

Function : average and maximum number of half rate TCH allocations.



Class : setup


Note : V11+ counter


TCH allocations

Name Q3 : burstToTransmit

Object : bts

Function :



Class : setup


l2000/0 Number of PDTCH available and preempted for EDGE services

Name Q3 : totalNumberOfEdgeTsCumtotalNumberOfEdgeTsTrZoneCumtotalNumberOfEdgeTsEchtotalNumberOfEdgeTsTrZoneEchtotalNumberOfEdgeTsMaxtotalNumberOfEdgeTsTrZoneMaxtotalNumberOfEdgeTsMoytotalNumberOfEdgeTsTrZoneMoy


Function : Minimum, maximum, average, and cumulative number of availablePDTCHforEDGE (all configuredPDTCHnot pre--empted for circuitcalls and available for EDGE)



Event : PDTCH configuration or preeemption/release of the EDGE channelby the BSC.

Type : LOAD

Feature : 19174 (EDGE dynamic Abis and Agprs backhaul)

Source : TBD

Note : V15 counter


Name Q3 : allocatedEdgeTsMoyallocatedEdgeTsMaxallocatedEdgeTsCumallocatedEdgeTsEchallocatedEdgeTsTrZoneMoyallocatedEdgeTsTrZoneMaxallocatedEdgeTsTrZoneCumallocatedEdgeTsTrZoneEch


Function : Minimum, maximum, average, and cumulative number of availablePDTCH for EDGE allocated to the PCU


Type : LOAD


Source : TBD

Note : V15 counter


Name Q3 : preemptedEdgeTsCumpreemptedEdgeTsTrZoneCumpreemptedEdgeTsMaxpreemptedEdgeTsTrZoneMaxpreemptedEdgeTsMoypreemptedEdgeTsTrZoneMoypreemptedEdgeTsEchpreemptedEdgeTsTrZoneEch


Function : Minimum, maximum, average, and cumulative number of availablePDTCH for EDGE services preempted by circuit calls


PE/DCL/DD/0125411--9001--125



Type : LOAD


Source : TBD

Note : V15 counter

l2001 Number of joker DS0 TS allocated on the Abis interface.

Name Q3 : allocatedAbisJokerTSEdgeCumallocatedAbisJokerTSEdgeTrZoneCumallocatedAbisJokerTSEdgeEchallocatedAbisJokerTSEdgeTrZoneEchallocatedAbisJokerTSEdgeMaxallocatedAbisJokerTSEdgeTrZoneMaxallocatedAbisJokerTSEdgeMoyallocatedAbisJokerTSEdgeTrZoneMoyallocatedAbisJokerTS


Function : Minimum, maximum, average, and cumulative number of joker DS0TS allocated on the Abis interface

Event : Joker (dis) configuration at TDMA configuration (or removal).

Type : LOAD


Source : TBD

Note : V15 counter

l2025/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 startmeasurement or in the classmark change request messages

Event : Receipt of a STOP MEASUREMENT ACK message from the BTS.


Source : recorded by BSC

Note : V15 counter



l2035/0 Value of the msPowerClassToggle parameter

Name Q3 : msClassSensitivityToggle

Object : bts

Function : A msPowerClassToggle parameter is defined at the OMC--R level inorder to report MS 2W, MS 8W or MS 2W + 8W (no check on thepower class).A list of ”toggling counters” is defined for which the BSC must takeinto account the msPowerClassToggle.Value of the msPowerClassToggle parameter :0 : MS 2W1 : MS 8W2 : MS 2+8W

Event : At T2 expiration



Note : V15 counter

l2036/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 preemptedPDTCH for MS 8W

Event : transmission of an ASSIGN_COMMAND message to a MS 8W.



Note : V15 counter

l2037/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 PDTCHassignations for MS 8W


PE/DCL/DD/0125411--9001--125


Event : receipt from a MS 8W of an ASSIGN_COMPLETE message



Note : V15 counter

l2038/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 forMS 8W

Event : receipt of a HANDOVER_COMPLETE message from a MS 8W



Note : V15 counter

l2039/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 forMS 8W

Event : receipt of a CLEAR COMMAND message from the MSC withhandover cause set to �hand_over successful



Note : V15 counter

3000/0 load of a OMU processor inside the Control Node of the sys-tem: SBC

Name Q3 : prLoadCne3OmuSbcMoyprLoadCne3OmuSbcMaxprLoadCne3OmuSbcCumprLoadCne3OmuSbcEch

Object : bsc

Function : Load of a givenOMUprocessor inside theControl Nodeof the system



Event : Core system internal counting






CCT: Circuit Calls on TCH channelsCCP: Circuit Calls on PDTCH preempted to make a TCH channelCP: Com Packets on PDTCH channel

Note : Each counter has a value between 0 and 100 (the value 100 representsa 100% load).

3001/0 Load of a given TMU processor inside the Control Node of thesystem: SBC

Name Q3 : prLoadCne3TmuSbcMoyprLoadCne3TmuSbcMaxprLoadCne3TmuSbcCumprLoadCne3TmuSbcEch

Object : bsc

Function : Load of a givenTMUprocessor inside theControl Node of the system








Note : V13.1 counterEach counter has a value between 0 and 100 (the value 100 representsa 100% load).


PE/DCL/DD/0125411--9001--125


3001/2 Load of a given TMU processor inside the Control Node of thesystem: PMC

Name Q3 : prLoadCne3TmuPmcMoyprLoadCne3TmuPmcMaxprLoadCne3TmuPmcCumprLoadCne3TmuPmcEch

Object : bsc

Function : Load of a given TMU processor inside the Control Node of thesystem: PMC








Note : V13.1 counterThis counter has a value between 0 and 100 (the value 100 representsa 100% load).The PMCmay be an option. In this case it is not significant value andthe result will be a succession “***…***” at the OMC level.

3004/0 Memory usage on OMU processor inside the Control Node ofthe system: SBC_MEM

Name Q3 : e3PrMemCnOmuSbcMemMoye3PrMemCnOmuSbcMemMaxe3PrMemCnOmuSbcMemCume3PrMemCnOmuSbcMemEch

Object : bsc

Function : Memory usage on OMU processor inside the Control Node of thesystem: SBC_MEM (DRAM usage)








When GPRS is activated, this counter is concerned by the followingcalls:CCT: Circuit Calls on TCH channelsCCP: Circuit Calls on PDTCH preempted to make a TCH channelCP: Com Packets on PDTCH channel

Note : V13.1 counterThis counter has a value between 0 and 100 (the value 100 representsa 100% load).

3004/1 Memory usage on OMU processor inside the Control Node ofthe system: SBC_SWAP

Name Q3 : e3PrMemCnOmuSbcSwapMoye3PrMemCnOmuSbcSwapMaxe3PrMemCnOmuSbcSwapCume3PrMemCnOmuSbcSwapEch

Object : bsc

Function : Memory usage on OMU processor inside the Control Node of thesystem: SBC_SWAP (disk usage for swap)









PE/DCL/DD/0125411--9001--125


3005/0 Memory usage on TMU processor inside the Control Node ofthe system: SBC

Name Q3 : e3PrMemCnTmuSbcMoye3PrMemCnTmuSbcMaxe3PrMemCnTmuSbcCume3PrMemCnTmuSbcEch

Object : bsc

Function : Memory usage on TMU processor inside the Control Node of thesystem: SBC








3005/2 Memory usage on TMU processor inside the Control Node ofthe system: PMC

Name Q3 : e3PrMemCnTmuPmcMoye3PrMemCnTmuPmcMaxe3PrMemCnTmuPmcCume3PrMemCnTmuPmcEch

Object : bsc

Function : Memory usage on TMU processor inside the Control Node of thesystem: SBC









CCT: Circuit Calls on TCH channels

CCP: Circuit Calls on PDTCH preempted to make a TCH channelCP: Com Packets on PDTCH channel

Note : V13.1 counter

This counter has a value between 0 and 100 (the value 100 representsa 100% load).

The PMCmay be an option. In this case it is not significant value andthe result will be a succession “***…***” at the OMC level.

3008/0 Disk usage on OMU processor inside the Control Node of thesystem: local disk access for write operation

Name Q3 : e3PrDiskCnOmuLdWMoye3PrDiskCnOmuLdWMaxe3PrDiskCnOmuLdWCume3PrDiskCnOmuLdWEch

Object : bsc

Function : Disk usage onOMUprocessor inside the Control Node of the system:disk access on local disk for write operation (Kbyte/s)







CCT: Circuit Calls on TCH channels

CCP: Circuit Calls on PDTCH preempted to make a TCH channelCP: Com Packets on PDTCH channel



PE/DCL/DD/0125411--9001--125


3008/1 Disk usage on OMU processor inside the Control Node of thesystem: local disk access for read operation

Name Q3 : e3PrDiskCnOmuLdRMoye3PrDiskCnOmuLdRMaxe3PrDiskCnOmuLdRCume3PrDiskCnOmuLdREch

Object : bsc

Function : Disk usage onOMUprocessor inside the Control Node of the system:disk access on local disk for read operation (Kbyte/s)









3008/2 Disk usage on OMU processor inside the Control Node of thesystem: mirror disk access for write operation

Name Q3 : e3PrDiskCnOmuMdWMoye3PrDiskCnOmuMdWMaxe3PrDiskCnOmuMdWCume3PrDiskCnOmuMdWEch

Object : bsc

Function : Disk usage onOMUprocessor inside the Control Node of the system:disk access on mirror disk for write operation (Kbyte/s)











3008/3 Disk usage on OMU processor inside the Control Node of thesystem: mirror disk access for read operation

Name Q3 : e3PrDiskCnOmuMdRMoye3PrDiskCnOmuMdRMaxe3PrDiskCnOmuMdRCume3PrDiskCnOmuMdREch

Object : bsc

Function : Disk usage onOMUprocessor inside the Control Node of the system:disk access on mirror disk for read operation (Kbyte/s)










PE/DCL/DD/0125411--9001--125


2.3.2 Raw permanent BSS counters (AMR)

l1197/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



Class : assignment









l1197/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,activated in the cell for the observation period



Class : assignment






l1900/0 Number of AMR full rate TCH allocations

Name Q3 : amrFrTchAllocatedamrFrTchAllocatedTrZone


Function : number of AMR full rate TCH allocations


PE/DCL/DD/0125411--9001--125


Event : This counter is incremented when a AMR full rate TCH is allocated



Note : V14 counter

l1901/0 Average and Maximum number of AMR full rate TCH

allocations

Name Q3 : amrFrTchStdAveragedUsedMoyamrFrTchStdAveragedUsedTrZoneMoyamrFrTchStdAveragedUsedMaxamrFrTchStdAveragedUsedTrZoneMaxamrFrTchStdAveragedUsedCumamrFrTchStdAveragedUsedTrZoneCumamrFrTchStdAveragedUsedEchamrFrTchStdAveragedUsedTrZoneEchamrFrTchStdAveragedUsed


Function : Average and Maximum number of AMR full rate TCH allocations

Event : This counter is incremented when an AMR full rate TCH is allocatedor de--allocated



Note : V14 counter

l1902/0 Duration of the AMR full rate TCH connections

Name Q3 : amrFrTchConnectionDurationMoyamrFrTchConnectionDurationTrZoneMoyamrFrTchConnectionDurationMaxamrFrTchConnectionDurationTrZoneMaxamrFrTchConnectionDurationCumamrFrTchConnectionDurationTrZoneCumamrFrTchConnectionDurationEchamrFrTchConnectionDurationTrZoneEch


Function : Duration of theAMRfull rate TCHconnections. This counter starts atthe beginning of transmission of SACCH blocks, and stops at the endof SACCH blocks transmission.



Event : This counter is triggered when data is received by the BSC from theBTS in STOP MEASUREMENT ACK messages



Note : V14 counter

l1902/1 Duration of the AMR half rate TCH connections

Name Q3 : amrHrTchConnectionDurationMoyamrHrTchConnectionDurationTrZoneMoyamrHrTchConnectionDurationMaxamrHrTchConnectionDurationTrZoneMaxamrHrTchConnectionDurationCumamrHrTchConnectionDurationTrZoneCumamrHrTchConnectionDurationEchamrHrTchConnectionDurationTrZoneEch


Function : Duration of the AMR half rate TCH connections. This counter startsat the beginning of transmission of SACCH blocks, and stops at theend of SACCH blocks transmission.




Note : V14 counter

l1903/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 kindof mobile

Event : See function



Note : V14 counter


PE/DCL/DD/0125411--9001--125


l1903/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 kindof mobile




Note : V14 counter

l1904/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 Procedurefor AMR full rate TCH

Event : This counter is triggered on reception of an Assign_Fail message onAMR TCH from the mobile



Note : V14 counter

l1904/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 Procedurefor AMR half rate TCH

Event : This counter is triggered on reception of an Assign_Fail message onAMR TCH from the mobile



Note : V14 counter



l1905 Total of the uplink C/I received from the L1m, for a non AMR

channel

Name Q3 : CIUplinkFrCIUplinkFrTrZone


Function : Total of theuplinkC/I received from theL1m, for anonAMRchannel(i.e. classic TCH and SDCCH)




Note : V14 counter

l1906 Amount of time the downlink power control was running at the

maximum level for the busy full rate AMR TCHs

Name Q3 : downlinkPowerCtrlMaxTchAmrFrCumdownlinkPowerCtrlMaxTchAmrFrEchdownlinkPowerCtrlMaxTchAmrFrMaxdownlinkPowerCtrlMaxTchAmrFrMoy

Object : bts

Function : Minimum, maximum, average, and cumulative amount of time thedownlink power control was running at the maximum level for thebusy full rate AMR TCHs




Note : V14 counter


PE/DCL/DD/0125411--9001--125


l1907 Amount of time the uplink power control was running at the

maximum level for the busy full rate AMR TCHs

Name Q3 : uplinkPowerCtrlMaxTchAmrFrCumuplinkPowerCtrlMaxTchAmrFrEchuplinkPowerCtrlMaxTchAmrFrMaxuplinkPowerCtrlMaxTchAmrFrMoy

Object : bts

Function : Minimum, maximum, average, and cumulative amount of time theuplink power control was running at the maximum level for the busyfull rate AMR TCHs




Note : V14 counter

l1908 Number of downlink RXLEV received from the L1m for AMR

full rate TCH

Name Q3 : RxLevDownlinkAmrFrRxLevDownlinkAmrFrTrZone


Function : Number of downlink RXLEV received from the L1m for AMR fullrate TCH




Note : V14 counter

l1909 Number of uplink RXLEV received from the L1m for AMR full

rate TCH

Name Q3 : RxLevUplinkAmrFrRxLevUplinkAmrFrTrZone


Function : Number of uplink RXLEV received from the L1m for AMR full rateTCH





Source : recorded by the BSCNote : V14 counter

l1910 Number of downlink RXQUAL received from the L1m forAMR

full rate TCHName Q3 : RxQualDownlinkAmrFr

RxQualDownlinkAmrFrTrZone

Object : transceiverZone/btsFunction : Number of downlink RXQUAL received from the L1m for AMR full

rate TCH




l1911 Number of uplinkRXQUALreceived fromtheL1mforAMRfull

rate TCHName Q3 : RxQualUplinkAmrFr

RxQualUplinkAmrFrTrZone

Object : transceiverZone/btsFunction : Number of uplink RXQUAL received from the L1m for AMR full

rate TCH




l1912 Number of MS increment power control ordered by the L1m for

AMR full rate TCHName Q3 : msPowerIncControlAmrFrObject : btsFunction : Number ofMS increment power control orderedby theL1m forAMR

full rate TCH


PE/DCL/DD/0125411--9001--125





Note : V14 counter

l1913 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 forAMR full rate TCH




Note : V14 counter

l1914 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 theL1m forAMRfull rate TCH




Note : V14 counter

l1915 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 orderedby theL1m forAMRfull rate TCH






Note : V14 counter

l1916 Total of the uplink C/I received from the L1m, for AMR full rate

calls

Name Q3 : CIUplinkAmrFrCIUplinkAmrFrTrZone


Function : Total of the uplink C/I received from the L1m, for AMRfull rate calls

Event : This counter is triggered upon reception of uplink C/I from the L1m



Note : V14 counter

l1917/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 STOPMEASUREMENT ACKmessage from the BTS. The value given bythe BTS is the average timing advance per communication



Note : V14 counter

l1917/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


PE/DCL/DD/0125411--9001--125


Event : This counter is triggered upon reception of a STOPMEASUREMENT ACKmessage from the BTS. The value given bythe BTS is the maximum timing advance per communication



Note : V14 counter

l1918/0 Amount of time the downlink power control was running at the

maximum level for the busy half rate AMR TCHs

Name Q3 : downlinkPowerCtrlMaxTchAmrHrCumdownlinkPowerCtrlMaxTchAmrHrEchdownlinkPowerCtrlMaxTchAmrHrMaxdownlinkPowerCtrlMaxTchAmrHrMoy

Object : bts

Function : Amount of time the downlink power control was running at themaximum level for the busy half rate AMR TCHs




Note : V14 counter

l1919/0 Amount of time the uplink power control was running at the

maximum level for the busy half rate AMR TCHs

Name Q3 : uplinkPowerCtrlMaxTchAmrHrCumuplinkPowerCtrlMaxTchAmrHrEchuplinkPowerCtrlMaxTchAmrHrMaxuplinkPowerCtrlMaxTchAmrHrMoy

Object : bts

Function : Amount of time the uplink power control was running at themaximum level for the busy half rate AMR TCHs




Note : V14 counter



l1920/0 Number of downlink RXLEV received from the L1m for AMR

half rate TCH

Name Q3 : RxLevDownlinkAmrHrRxLevDownlinkAmrHrTrZone


Function : Number of downlink RXLEV received from the L1m for AMR halfrate TCH




Note : V14 counter

l1921/0 Number of uplink RXLEV received from the L1m for AMR half

rate TCH

Name Q3 : RxLevUplinkAmrHrRxLevUplinkAmrHrTrZone


Function : Number of uplink RXLEV received from the L1m for AMR half rateTCH




Note : V14 counter

l1922/0 Number of downlink RXQUAL received from the L1m forAMR

half rate TCH

Name Q3 : RxQualDownlinkAmrHrRxQualDownlinkAmrHrTrZone


Function : Number of downlinkRXQUAL received from the L1m for AMRhalfrate TCH


PE/DCL/DD/0125411--9001--125





Note : V14 counter

l1923/0 Number of uplink RXQUAL received from the L1m for AMR

half rate TCH

Name Q3 : RxQualUplinkAmrHrRxQualUplinkAmrHrTrZone


Function : Number of uplink RXQUAL received from the L1m for AMR halfrate TCH




Note : V14 counter

l1924/0 Number of MS increment power control ordered by the L1m for

AMR half rate TCHName Q3 : msPowerIncControlAmrHr

Object : bts

Function : Number ofMS increment power control orderedby theL1m forAMRhalf rate TCH




Note : V14 counter

l1925/0 Number of MS decrement power control ordered by the L1m for

AMR half rate TCHName Q3 : msPowerDecControlAmrHr

Object : bts

Function : Number of MS decrement power control ordered by the L1m forAMR half rate TCH






Note : V14 counter

l1926/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 theL1m forAMRhalf rate TCH




Note : V14 counter

l1927/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 orderedby theL1m forAMRhalf rate TCH




Note : V14 counter

l1928/0 Total of the uplink C/I received from the L1m, for AMR half rate

calls

Name Q3 : CIUplinkAmrHrCIUplinkAmrHrTrZone


Function : Total of the uplinkC/I received from theL1m, for AMRhalf rate calls


PE/DCL/DD/0125411--9001--125


Event : This counter is triggered upon reception of uplink C/I from the L1m



Note : V14 counter

l1929/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

Event : This counter is triggered upon reception of a STOPMEASUREMENT ACKmessage from the BTS. The value given bythe BTS is the average timing advance per communication



Note : V14 counter

l1929/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

Event : This counter is triggered upon reception of a STOPMEASUREMENT ACKmessage from the BTS. The value given bythe BTS is the maximum timing advance per communication



Note : V14 counter

l1930/0 Number of MS measurement messages not received by the BTS

for a AMR full rate call

Name Q3 : msLostMeasurementsAmrFrmsLostMeasurementsAmrFrTrZone


Function : Number ofMSmeasurement messages not received by the BTS for aAMR full rate call






Note : V14 counter

l1931/0 Number of MS measurement messages not received by the BTS

for a AMR half rate call

Name Q3 : msLostMeasurementsAmrHrmsLostMeasurementsAmrHrTrZone


Function : Number ofMSmeasurement messages not received by the BTS for aAMR half rate call




Note : V14 counter

l1932/0 Number of quality intracell handovers filtered

Name Q3 : qualityHoFiltered

Object : bts

Function : Number of quality intracell handovers filtered




Note : V14 counter

l1933/0 Number of capacity intracell handovers filtered

Name Q3 : capacityHoFiltered

Object : bts

Function : Number of capacity intracell handovers filtered


PE/DCL/DD/0125411--9001--125





Note : V14 counter

l1950/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 thecell

Event : This counter is triggered on reception of:HANDOVER INDICATION (except when this message shall beignored)Directed retry attempt: reception of a CONNECTIONREQUESTACK message or autonomously in case of directed retry from amicro--cellCONNECTION REQUEST ACK with an eligible cells list afterTchoke expires



Note : V14 counter

l1950/1 Number of Intracell AMRfull rate downlink required handovers

in the cell

Name Q3 : intracellAmrFrDownHoRequiredTch

Object : bts

Function : Number of Intracell AMR full rate downlink required handovers inthe cell






Note : V14 counter

l1950/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 thecell




Note : V14 counter

l1950/3 Number of AMRQuality full rate downlink required handovers

in the cell

Name Q3 : amrQualityFrDownHoRequiredTch

Object : bts

Function : Number ofAMRQuality full rate downlink required handovers in thecell


PE/DCL/DD/0125411--9001--125





Note : V14 counter

l1950/4 Number of the capacity of full rate to half rate required

handovers in the cell

Name Q3 : capacityFrToHrHoRequiredTch

Object : bts

Function : Number of the capacity of full rate to half rate required handovers inthe cell




Note : V14 counter

l1951/0 Number of half rate to full rate alarms in AMR uplink required

handovers in the cell

Name Q3 : alarmAmrHrToFrUpHoRequiredTch

Object : bts

Function : Number of half rate to full rate alarms in AMR uplink requiredhandovers in the cell






Note : V14 counter

l1951/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 requiredhandovers in the cell




Note : V14 counter

l1951/2 Number of AMRQuality half rate uplink required handovers in

the cell

Name Q3 : amrQualityHrUpHoRequiredTch

Object : bts

Function : Number of AMR Quality half rate uplink required handovers in thecell


PE/DCL/DD/0125411--9001--125





Note : V14 counter

l1951/3 Number of AMRQuality half rate downlink required handovers

in the cell

Name Q3 : amrQualityHrDownHoRequiredTch

Object : bts

Function : Number ofAMRQuality half rate downlink requiredhandovers in thecell




Note : V14 counter

l1952/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 rateAMR MS






Note : V14 counter

l1952/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 halfrate AMR MS




Note : V14 counter

l1953/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 anAMRmobile. 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

l1953/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 thehandover (success, selection failure, execution, failure or end of call)


PE/DCL/DD/0125411--9001--125





Note : V14 counter

l1953/2 Number of Intracell half rate to full rate handover requests for

the cell, by an AMR mobileName 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 thehandover (success, selection failure, execution, failure or end of call)




Note : V14 counter

l1954/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 anAMRmobile. 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 ofASSIGN_COMMAND message



Note : V14 counter

l1954/1 Number of Intracell full rate to half rate handover executions for

the cell, by an AMR mobileName Q3 : amrFrToHrHoExecutionIntraCellTch

Object : bts

Function : Number of Intracell full rate to half rate handover executions for thecell, by an AMRmobile. This counter is incremented at the end of thehandover (success, selection failure, execution, failure or end of call)






Note : V14 counter

l1954/2 Number of Intracell half rate to full rate handover executions for

the cell, by an AMR mobile

Name Q3 : amrHrToFrHoExecutionIntraCellTch

Object : bts

Function : Number of Intracell half rate to full rate handover executions for thecell, by an AMRmobile. This counter is incremented at the end of thehandover (success, selection failure, execution, failure or end of call)




Note : V14 counter

l1955/0 Number of successful Intracell full rate handovers for the cell, by

an AMR mobileName Q3 : amrFrHoSuccessIntraCellTch

Object : bsc

Function : Number of successful Intracell full rate handovers for the cell, by anAMR mobile.

Event : This counter is triggered upon the transmission ofASSIGN_COMPLETE message from the mobile



Note : V14 counter

l1955/1 Number of successful Intracell full rate to half rate handovers for

the cell, by an AMR mobileName Q3 : amrFrToHrHoSuccessIntraCellTch

Object : bsc

Function : Number of successful Intracell full rate to half rate handovers for thecell, by an AMR mobile.


PE/DCL/DD/0125411--9001--125





l1955/2 Number of successful Intracell half rate to full rate handovers for

the cell, by an AMR mobileName Q3 : amrHrToFrHoSuccessIntraCellTchObject : bscFunction : Number of successful Intracell half rate to full rate handovers for the

cell, by an AMR mobile.




l1956/0 Number of attempts of half rate AMR handover from a central

cell to a neighboring oneName Q3 : hoNCellsExecutionTchAmrHrObject : adjacentCellHandOverFunction : Number of attempts of half rateAMRhandover froma central cell to a

neighboring one

Event : This counter is triggered upon reception of the HANDOVERCOMMAND message from the MSC (inter BSC handover), ortransmission of ABIS HANDOVER COMMAND message (intraBSC handover)



l1957/0 Number of attempts of full rate ARM handover from a central

cell to a neighboring oneName Q3 : hoNCellsExecutionTchAmrFrObject : adjacentCellHandOverFunction : Number of attempts of full rate ARMhandover from a central cell to a

neighboring one



Event : This counter is triggered upon reception of the HANDOVERCOMMAND message from the MSC (inter BSC handover), ortransmission of ABIS HANDOVER COMMAND message (intraBSC handover)



Note : V14 counter

l1958/0 Number of unsuccessful half rate AMRhandovers from a central

cell to a neighboring one caused by themobile returning to theoldchannel

Name Q3 : hoNCellsUnsuccessTchAmrHrHandoverFailure


Function : Number of unsuccessful half rate AMR handovers from a central cellto a neighboring one caused by themobile returning to the old channel

Event : This counter is triggered upon reception of the HANDOVERFAILURE message before T3103 timer expiration



Note : V14 counter


cell to a neighboring one caused by the expiration of the T3103timer

Name Q3 : hoNCellsUnsuccessTchAmrHrTimerExpiration


Function : Number of unsuccessful half rate AMR handovers from a central cellto a neighboring one caused by the expiration of the T3103 mobile

Event : This counter is triggered upon the expiration of the T3103 timer. Thisis relevant for intra BSS and inter BSS handovers



Note : V14 counter


PE/DCL/DD/0125411--9001--125



cell to a neighboring one caused by other causes

Name Q3 : hoNCellsUnsuccessTchAmrHrClearCommand


Function : Number of unsuccessful half rate AMR handovers from a central cellto a neighboring one caused by other causes (i.e. not caused by thosementioned in counters 1958/0 or 1958/1)

Event : This counter is triggered upon reception of the CLEARCOMMANDmessagewith a cause set to another value than “Handover Successful”or “Call Control”, relevant for inter BSS handovers



Note : V14 counter

l1959/0 Number of unsuccessful full rate AMR handovers from a central

cell to a neighboring one caused by themobile returning to theoldchannel

Name Q3 : hoNCellsUnsuccessTchAmrFrHandoverFailure


Function : Number of unsuccessful full rate AMR handovers from a central cellto a neighboring one caused by themobile returning to the old channel

Event : This counter is triggered upon reception of the HANDOVERFAILURE message before T3103 timer expiration



Note : V14 counter


cell to a neighboring one caused by the expiration of the T3103timer

Name Q3 : hoNCellsUnsuccessTchAmrFrTimerExpiration


Function : Number of unsuccessful full rate AMR handovers from a central cellto a neighboring one caused by the expiration of the T3103 mobile



Event : This counter is triggered upon the expiration of the T3103 timer. Thisis relevant for intra BSS and inter BSS handovers



Note : V14 counter


cell to a neighboring one caused by other causes

Name Q3 : hoNCellsUnsuccessTchAmrFrClearCommand


Function : Number of unsuccessful full rate AMR handovers from a central cellto a neighboring one caused by other causes (i.e. not caused by thosementioned in counters 1959/0 or 1959/1)

Event : This counter is triggered upon reception of the CLEARCOMMANDmessagewith a cause set to another value than “Handover Successful”or “Call Control”, relevant for inter BSS handovers



Note : V14 counter

l1960/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

l1960/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


PE/DCL/DD/0125411--9001--125





Note : V14 counter

l1960/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 AMRmobile caused by other causes(i.e. not caused by those mentioned in counters 1960/0 or 1960/1)




Note : V14 counter

l1961/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

l1961/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



l1961/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 AMRmobile caused by other causes(i.e. not caused by those mentioned in counters 1961/0 or 1961/1)




Note : V14 counter

l1963/0 Number of half rate AMR handovers requested from a central

cell to a neighboring one

Name Q3 : hoNCellsRequestOutgoingAmrHr


Function : Number of half rateAMRhandovers requested from a central cell to aneighboring one

Event : Attemp to select a target cell in the list of eligible cells on transmissionof HANDOVER REQUIRED on the A interface (inter BSChandover) or attempt to select a target cell in the list of eligible cellsprovided by the handover algorithm (intra BSC handover).



Note : V14 counter

l1964/0 Number of full rateAMRhandovers requested froma central cell

to a neighboring one

Name Q3 : hoNCellsRequestOutgoingAmrFr


Function : Number of full rate AMRhandovers requested from a central cell to aneighboring one


PE/DCL/DD/0125411--9001--125


Event : Attemp to select a target cell in the list of eligible cells on transmissionof HANDOVER REQUIRED on the A interface (inter BSChandover) or attempt to select a target cell in the list of eligible cellsprovided by the handover algorithm (intra BSC handover).



Note : V14 counter

l1975/0 Number of 40ms periods during which Codec 4.75 has been

applied on the uplink for full rate AMR

Name Q3 : amrFrUplinkCodec475amrFrUplinkCodec475TrZone


Function : Number of 40ms periods during which Codec 4.75 has been appliedon the uplink for full rate AMR




Note : V14 counter





Function : Number of 40ms periods during which Codec 5.9 has been applied onthe uplink for full rate AMR




Note : V14 counter







Function : Number of 40ms periods during which Codec 6.7 has been applied onthe uplink for full rate AMR




Note : V14 counter



Name Q3 : : amrFrUplinkCodec102amrFrUplinkCodec102TrZone


Function : Number of 40ms periods during which Codec 10.2 has been appliedon the uplink for full rate AMR




Note : V14 counter


applied on the uplink for half rate AMR

Name Q3 : amrHrUplinkCodec475amrHrUplinkCodec475TrZone


Function : Number of 40ms periods during which Codec 4.75 has been appliedon the uplink for half rate AMR


PE/DCL/DD/0125411--9001--125





Note : V14 counter





Function : Number of 40ms periods during which Codec 5.9 has been applied onthe uplink for half rate AMR




Note : V14 counter





Function : Number of 40ms periods during which Codec 6.7 has been applied onthe uplink for half rate AMR




Note : V14 counter




applied on the downlink for full rate AMR

Name Q3 : amrFrDownlinkCodec475amrFrDownlinkCodec475TrZone


Function : Number of 40ms periods during which Codec 4.75 has been appliedon the downlink for full rate AMR




Note : V14 counter





Function : Number of 40ms periods during which Codec 5.9 has been applied onthe downlink for full rate AMR




Note : V14 counter





Function : Number of 40ms periods during which Codec 6.7 has been applied onthe downlink for full rate AMR


PE/DCL/DD/0125411--9001--125





Note : V14 counter





Function : Number of 40ms periods during which Codec 10.2 has been appliedon the downlink for full rate AMR




Note : V14 counter


applied on the downlink for half rate AMR

Name Q3 : amrHrDownlinkCodec475amrHrDownlinkCodec475TrZone


Function : Number of 40ms periods during which Codec 4.75 has been appliedon the downlink for half rate AMR




Note : V14 counter







Function : Number of 40ms periods during which Codec 5.9 has been applied onthe downlink for half rate AMR




Note : V14 counter





Function : Number of 40ms periods during which Codec 6.7 has been applied onthe downlink for half rate AMR




Note : V14 counter

l1979/0 Number of bad speech frames (BFIKO) received at the BTS level

for full rate AMR at Codec 4.75

Name Q3 : amrFrBadSpeechFramesCodec475amrFrBadSpeechFramesCodec475TrZone


Function : Number of bad speech frames (BFI KO) received at the BTS level forfull rate AMR at Codec 4.75


PE/DCL/DD/0125411--9001--125





Note : V14 counter









Note : V14 counter









Note : V14 counter




for full rate AMR at Codec 10.2Name Q3 : amrFrBadSpeechFramesCodec102

amrFrBadSpeechFramesCodec102TrZone






Note : V14 counter

l1980/0 Received speech frames AMR FR at Codec 4.75Name Q3 : amrFrValidSpeechFramesCodec475

amrFrValidSpeechFramesCodec475TrZone


Function : Number of correct and bad speech frames received at the BTS levelfor full rate AMR at Codec 4.75




Note : V14 counter








Note : V14 counter


PE/DCL/DD/0125411--9001--125


l1980/2 Received speech frames AMR FR at Codec 6.7

Name Q3 : amrFrValidSpeechFramesCodec67amrFrValidSpeechFramesCodec67TrZone






Note : V14 counter








Note : V14 counter


for half rate AMR at Codec 4.75Name Q3 : amrHrBadSpeechFramesCodec475

amrHrBadSpeechFramesCodec475TrZone


Function : Number of bad speech frames (BFI KO) received at the BTS level forhalf rate AMR at Codec 4.75




Note : V14 counter




for half rate AMR at Codec 5.9

Name Q3 : amrHrBadSpeechFramesCodec59amrHrBadSpeechFramesCodec59TrZone






Note : V14 counter


for half rate AMR at Codec 6.7

Name Q3 : amrHrBadSpeechFramesCodec67amrHrBadSpeechFramesCodec67TrZone






Note : V14 counter

l1982/0 Received speech frames AMR HR at Codec 4.75

Name Q3 : amrHrValidSpeechFramesCodec475amrHrValidSpeechFramesCodec475TrZone


Function : Number of correct and bad speech frames received at the BTS levelfor half rate AMR at Codec 4.75


PE/DCL/DD/0125411--9001--125





Note : V14 counter








Note : V14 counter








Note : V14 counter

l1983/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 theAbis interface on theuplink for AMR calls






l1983/1 Number of no data frames received or sent on the Abis interface

on the downlink for AMR callsName Q3 : amrDownlinkNoDataFramesObject : btsFunction : Number of no data frames received or sent on theAbis interface on the

downlink for AMR calls




l1984/0 Number of Codec increment modifications for full rate AMR in

uplinkName Q3 : incAmrFrUpModif

incAmrFrUpModifTrZone

Object : transceiverZone/btsFunction : Number of Codec increment modifications for full rate AMR in

uplink




l1984/1 Number of Codec decrement modifications for full rate AMR in

uplinkName Q3 : decAmrFrUpModif

decAmrFrUpModifTrZone

Object : transceiverZone/btsFunction : Number of Codec decrement modifications for full rate AMR in

uplink


PE/DCL/DD/0125411--9001--125





Note : V14 counter

l1985/0 Number of Codec increment modifications for full rate AMR in

downlink

Name Q3 : incAmrFrDownModifincAmrFrDownModifTrZone


Function : Number of Codec increment modifications for full rate AMR indownlink




Note : V14 counter

l1985/1 Number of Codec decrement modifications for full rate AMR in

downlink

Name Q3 : decAmrFrDownModifdecAmrFrDownModifTrZone


Function : Number of Codec decrement modifications for full rate AMR indownlink




Note : V14 counter



l1986/0 Number of Codec increment modifications for half rate AMR in

uplink

Name Q3 : incAmrHrUpModifincAmrHrUpModifTrZone


Function : Number of Codec increment modifications for half rate AMR inuplink




Note : V14 counter

l1986/1 Number of Codec decrement modifications for half rate AMR in

uplink

Name Q3 : decAmrHrUpModifdecAmrHrUpModifTrZone


Function : Number of Codec decrement modifications for half rate AMR inuplink




Note : V14 counter

l1987/0 Number of Codec increment modifications for half rate AMR in

downlink

Name Q3 : incAmrHrDownModifincAmrHrDownModifTrZone


Function : Number of Codec increment modifications for half rate AMR indownlink


PE/DCL/DD/0125411--9001--125





Note : V14 counter

l1987/1 Number of Codec decrement modifications for half rate AMR in

downlink

Name Q3 : decAmrHrDownModifdecAmrHrDownModifTrZone


Function : Number of Codec decrement modifications for half rate AMR indownlink




Note : V14 counter

l1988/0 Number of CMI/CMR inversqtion phase procedure failure for

AMR callsName Q3 : amrReversalPhaseFailure

Object : bts

Function : Number of CMI/CMR inversqtion phase procedure failure for AMRcalls




Note : V14 counter

l2010/0 Total number of priority 1 queued WPS requests on a priority

level basisName Q3 : WQUEUED1

Object : bts

Function : Total number of priority 1 queued WPS requests on a priority levelbasis.



Event : WPS global flag is activated



Feature : WPS BSS2G and E3 queuing mechanism enhancement (22463)

Note : V15 counter


level basis

Name Q3 : WQUEUED2

Object : bts






Note : V15 counter


level basis

Name Q3 : WQUEUED3

Object : bts






Note : V15 counter


level basis

Name Q3 : WQUEUED4

Object : bts



PE/DCL/DD/0125411--9001--125






Note : V15 counter


level basis

Name Q3 : WQUEUED5

Object : bts






Note : V15 counter

l2011/0 Total number of priority 1WPS 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


Name Q3 : WQOVFL2

Object : bts








Note : V15 counter


Name Q3 : WQOVFL3

Object : bts






Note : V15 counter


Name Q3 : WQOVFL4

Object : bts






Note : V15 counter


Name Q3 : WQOVFL5

Object : bts





PE/DCL/DD/0125411--9001--125




Note : V15 counter

l2012/0 Total number of priority 1WPS requests droppedwhen the time

spent by WPS request exceeds the maximum queue timer.

Name Q3 : WQTOUT1

Object : bts

Function : Total number of priority 1WPS requests droppedwhen the time spentby WPS request exceeds the maximum queue timer.





Note : V15 counter

2012/1 Total number of priority 2WPS requests droppedwhen the timespent by WPS request exceeds the maximum queue timer.

Name Q3 : WQTOUT2

Object : bts






Note : V15 counter



Name Q3 : WQTOUT3

Object : bts








Note : V15 counter



Name Q3 : WQTOUT4

Object : bts






Note : V15 counter



Name Q3 : WQTOUT5

Object : bts






Note : V15 counter


PE/DCL/DD/0125411--9001--125


l2013/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 classesin the notAllowedAccessClasses parameter exclude the countertriggering. Number of times access classes number 0 to 9 are barred.Correlation with accessClassCongestion parameter (removingclasses 11 to 15) gives the number of minutes a given access classbetween 0 to 9 barred

Event : At each rotation of access classes (every 1 minute).


Feature : WPSBSS2G and E3 access class barring with class periodic rotation.(22464)


Note : V15 counter

l2013/1 Duration that access class 11 has been barred during cell

congestion.

Name Q3 : wpsAccessBarringDurationClass11

Object : bts

Function : An access class is barred during cell congestion. Barred access classesin the notAllowedAccessClasses parameter exclude the countertriggering. Number of minutes the access class number 11 has beenbarred.





Note : V15 counter




congestion.


Object : bts






Note : V15 counter


congestion.


Object : bts






Note : V15 counter


PE/DCL/DD/0125411--9001--125



congestion.


Object : bts






Note : V15 counter


congestion.


Object : bts






Note : V15 counter

l2014 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 (includingPDTCH) allocations



Event : TCHA traffic channel becomes free and is allocated to a public callwhile a WPS request is queued.




Note : V15 counter

l2015 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 theMSCwhilethe WPS request is queued and no clear request previously sent

Event : WPS call is released while in queuing phase



Note : V15 counter

l2016 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 inthe serving cell.




Note : V15 counter


PE/DCL/DD/0125411--9001--125


l2040 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 receivedby 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 : attempt to select a cell as an host cell



Note : V15 counter

l2041 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 receivedby 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

l2042 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 thecell, for MS 8W only




Note : V15 counter



l2043 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 thecell, for MS 8W only




Note : V15 counter

l2044 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. Thecounter is incremented at the end of the handover (success, selectionfailure, 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

l2045 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. Thecounter is incremented at the end of the handover (success, selectionfailure, execution failure or end of call) for MS 8W only.




Note : V15 counter


PE/DCL/DD/0125411--9001--125


2046 Number of intra_cell handover requests for the cell, by MS 8Wonly

Name Q3 : hoRequestIntraBts8W

Object : bts

Function : Number of intra_cell handover requests for the cell, byMS 8W only.The counter is incremented at the end of the handover (success,selection failure, execution failure or end of call).

Event : attempt of selection in the cell



Note : V15 counter

2047 Numberof successful intra_cell handovers for the cell, forMS8W

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

l2048 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 forMS 8W




Note : V15 counter



l2049 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 forMS 8W




Note : V15 counter

l2050 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. Thecounter is incremented at the end of the handover (success, selectionfailure, execution failure or end of call) for MS 8W only.




Note : V15 counter

l2051 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. Thecounter is incremented at the end of the handover (success, selectionfailure, execution failure or end of call) for MS 8W only.




Note : V15 counter


PE/DCL/DD/0125411--9001--125


l2052/0 Number of releases while the communication is in signalling

phase and cell associated to the communication, forMS 8W only

Name Q3 : signallingReleaseBts8w

Object : bts

Function : Number of releases while the communication is in signalling phaseand cell associated to the communication, for MS 8W only

Event : receipt of a SCCP DISCONNECTION INDICATION message fromthe MSC



Note : V15 counter

l2052/1 Number of releases while the communication is in “signalling”

phase and cell associated to the communication, forMS 8W only

Name Q3 : signallingReleaseBtsT3107CircDown8W

Object : bts

Function : Number of releases while the communication is in “signalling” phaseand cell associated to the communication, for MS 8W only

Event : Expiration of T3107 timer before receipt of ESTABLISHMENTINDICATION message, during a Dedicated Channel Assignmentprocedure or a handover Intracell on SDCCH procedure. (a CLEARREQUEST 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 fromthe MSC.



Note : V15 counter

l2054 Number of receipts of an ESTABLISHMENT_INDICATION

message in call establishment phase (on SDCCH, or on TCH inprimo allocation (call re--establishment) or on overflowing), forMS 8W only

Name Q3 : estabIndicSignallingEmergency8W

Object : bts

Function : Number of receipts of an ESTABLISHMENT_INDICATIONmessage in call establishment phase (on SDCCH, or onTCH in primoallocation (call re--establishment) or on overflowing), for MS 8Wonly

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_INDICATIONmessage in call establishment phase (on SDCCH, or on TCH inprimo allocation (call re--establishment) or on overflowing) for aphase II MS 8W

Name Q3 : estabIndicSigPhase28W

Object : bts

Function : Number of receipt of an ESTABLISHMENT_INDICATIONmessage in call establishment phase (on SDCCH, or onTCH in primoallocation (call re--establishment) or on overflowing) for a phase IIMS 8W

Event : receipt of an ESTABLISHMENT_INDICATION message in callestablishment phase (on SDCCH, or on TCH in primo allocation (callre--establishment) or on overflowing) for a phase II MS 8W



Note : V15 counter


PE/DCL/DD/0125411--9001--125


l2056/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 forMS 8W only

Event : aMS8W returns to the old channel (HANDOVERFAILURE) beforeT3103 timer expiration)


Class : handover


l2056/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 forMS 8W only.

Event : expiration of T3103 timer


Class : handover



TCH in the cell with cause mobile returns to the old channel

Name Q3 : hoUnsuccessOutgoingInterCellTchReturnOldChannel8W

Object : bts

Function : number of refusals to accept an outgoing inter--cell handover on TCHin the cell with cause mobile returns to the old channel



Class : handover





TCH in the cell with cause T3103 (respectively T3107) timerexpiration for V12 (respectively V11)

Name Q3 : hoUnsuccessOutgoingInterCellTchT3103TimerExp8W

Object : bts

Function : number of refusals to accept an outgoing inter--cell handover on TCHin the cell with causeT3103 (respectively T3107) timer expiration forV12 (respectively V11)

Event : expiration of the T3103 timer


Class : handover


l2058/0 Number of abnormal releases while the communication is in

“signalling” phase and cell associated to the communication, forMS 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 MS8W only.

Event : All the previous screening except �Expiration of T3101 timer beforereceipt of ESTABLISHMENT INDICATION message, during anImmediate Assignment procedure and “Receipt of aCLEAR_COMMAND message from the MSC” (considered asnormal release).


Class : handover


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


PE/DCL/DD/0125411--9001--125


Event : All the previous screening except “Receipt of aCLEAR_COMMAND message from the MSC” (considered asnormal release).


Class : handover


l2060 Number of uplink freemessages sent by the BSC indicating in the

uplink request access that the MS shall perform the uplink replyprocedure.

Name Q3 : uplinkFreeUplinkReply

Object : bts

Function : Cumulative number of uplink free messages sent by the BSCindicating in the uplink request access that the MS shall perform theuplink reply procedure.

Event : Whenever the BSC sends an uplink free message indicating in theuplink request access that the MS shall perform the uplink replyprocedure.



Note : V15 counter



l2061 At expiration of the listener detection timer, the group call

channel is released in the cell

Name Q3 : listenerDetectionExpiry

Object : cell

Function : At expiration of the listener detection timer, the group call channel isreleased in the cell.

Event : at expiration of the listener detection timer



Note : V15 counter



Note : V15 counter


PE/DCL/DD/0125411--9001--125


2.4 Raw temporary counters (odiag excluded)

2.4.1 Temporary Interference observation

ll5000 Average interference level on idle channels

Name Q3 : channelIdleLevelMoychannelIdleLevelMaxchannelIdleLevelCumchannelIdleLevelEch = Number of samples

Object : channel (dedicated radio channel)

Function : interference class [0 to 4] on a radio channel (= average level ofmeasured values on SDCCH or TCH) when it is free and number offree logical channels carried by the radio channel during theobservation period

Event : receipt of RF RESOURCE INDICATION message

Type : raw temporary


Note : A PDTCH channel is not taken into account

2.4.2 Temporary SS7 link observation

l5100/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 theremote MTP2



ll5101/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





ll5102/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 negativeacknowledgement of frames

Event : receipt by theBSC link of a request for retransmission on the SS7 linkfrom the remote MTP2


Source : ecorded by the BSC

l5102/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 negativeacknowledgement of frames

Event : transmission by the BSC of a request for retransmission on the SS7link to the remote MTP2



ll5102/2 Number of SS7 Level 2 errors: MSU rejected for congestion

Name Q3 : ss7Level2ErrorMsuCongest


Function : number of MSU frames rejected byMTP2 because of lack of internalmemory

Event : rejection of an MSU frame by MTP2 because of lack of internalmemory




PE/DCL/DD/0125411--9001--125


ll5102/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



ll5103/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 inacknowledgement messages

Event : Level 3 bssMapT7 time-out elapse



ll5103/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 thedefinition of the CCITT Q703 recommendation (Paragraph 10,page 67)





2.4.3 Temporary Abis interface observation

l5600/0 Number of IU frames sent on sapi RSL

Name Q3 : abisOutputUiFrame

Object : bts

Function : number of UI (Unnumbered Information) frames sent to the cellTDMA frames on RSL SAPI

Event : transmission of a UI frame on a RSL by the BSC



l5601/0 Number of UI frames received on sapi RSL

Name Q3 : abisInputUiFrame

Object : bts

Function : number of UI (Unnumbered Information) frames received from thecell TDMA frames on RSL SAPI

Event : receipt of a UI frame on a RSL by the BSC



l5602/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 onRSL SAPI

Event : transmission of an I frame on a RSL by the BSC




PE/DCL/DD/0125411--9001--125


l5603/0 Number of I frames received on sapi RSLName Q3 : abisInputIFrame

Object : bts

Function : number of I (Information) frames received from the cell TDMAframes on RSL SAPI

Event : reception of an I frame on a RSL by the BSC



l5604/0 Number of UI bytes received on sapi RSLName Q3 : abisOutputUiByte

Object : bts

Function : number of UI (Unnumbered Information) bytes sent to the cellTDMA frames on RSL SAPI

Event : transmission of a UI frame on a RSL by the BSC



l5605/0 Number of UI bytes sent on sapi RSLName Q3 : abisInputUiByte

Object : bts

Function : number ofUI (Unnumbered Information) bytes received from the cellTDMA frames on RSL SAPI

Event : receipt of a UI frame on a RSL by the BSC



l5606/0 Number of I bytes sent on sapi RSLName Q3 : abisOutputIByte

Object : bts

Function : number of I (Information) bytes sent to the cell TDMAframes onRSLSAPI

Event : transmission of an I frame on a RSL by the BSC





l5607/0 Number of I bytes received on sapi RSL

Name Q3 : abisInputIByte

Object : bts

Function : number of I (Information) bytes received from the cell TDMAframeson RSL SAPI

Event : receipt of an I frame on a RSL by the BSC



l5608/0 Number of Abis Level 2 errors: SUP received with PF 1

Name Q3 : abisLevel2ErrorRxSup1

Object : bts

Function : number of SUP (supervision) frameswith the final bit set to 1 receivedin established multiframe mode

Event : receipt of a SUP frame with the final bit set to 1 in establishedmultiframe mode by the BSC



l5608/1 Number of Abis Level 2 errors: DM received with PF 1

Name Q3 : abisLevel2ErrorRxDm1

Object : bts

Function : number of DM (DisconnectedMode) frameswith the final bit set to 1received in established multiframe mode

Event : receipt of a DM frame with the final bit set to 1 in establishedmultiframe mode by the BSC




PE/DCL/DD/0125411--9001--125


l5608/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 bitset to 1 received in one of the states listed below

Event : receipt by theBSCof aUA framewith the final bit set to 1 in one of thefollowing states:

a TEI is allocatedthe multiframe mode is establisheda multiframe mode time-out is running



l5608/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 bitset to 0 received in one of the states listed below

Event : receipt by theBSCof aUA framewith the final bit set to 0 in one of thefollowing states:

a TEI is allocatedthe multiframe mode is establisheda multiframe mode time-out is runningwaiting for establishmentwaiting for clear





l5608/4 Number of Abis Level 2 errors: DM received with PF 0

Name Q3 : abisLevel2ErrorRxDm0

Object : bts

Function : number of DM (DisconnectedMode) frameswith the final bit set to 0received 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 ofthe following states:

the multiframe mode is establisheda multiframe mode time-out is running



l5608/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:the multiframe mode is establisheda multiframe mode time-out is running



l5608/6 Number of Abis Level 2 errors: SABME retransmitted

Name Q3 : abisLevel2ErrorTxNSabme

Object : bts

Function : number of SABME frames unsuccessfully retransmitted N150 timesduring an establishment period

Event : N150 unsuccessful retransmissions of an SABME frame during anestablishment period




PE/DCL/DD/0125411--9001--125


l5608/7 Number of Abis Level 2 errors: DISC retransmitted

Name Q3 : abisLevel2ErrorTxNDisc

Object : bts

Function : number of DISC (Disconnect) frames unsuccessfully retransmittedN150 times during a clearing period

Event : N150 unsuccessful retransmissions of aDISC frame during a clearingperiod



l5608/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) retransmittedwhile 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



l5608/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 thestates listed below

Event : receipt by the BSC of an errored NR frame in one of the followingstates:

the multiframe mode is established

a multiframe mode time-out is running





l5608/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 stateslisted below

Event : receipt by the BSC of an FRMR frame in one of the following states:the multiframe mode is establisheda multiframe mode time-out is running



l5608/11 Number of Abis Level 2 errors: Unknown frame

Name Q3 : abisLevel2ErrorRxNoImpl

Object : bts

Function : number of unknown frameswith final bit set to 0 received inone of thestates listed below

Event : receipt by theBSCof anunknown framewith final bit set to 0 in oneofthe following states:

a TEI is allocatedthe multiframe mode is establisheda multiframe mode time-out is runningwaiting for establishmentwaiting for clear




PE/DCL/DD/0125411--9001--125


l5608/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 listedbelow

Event : receipt by the BSC of a wrong length frame in one of the followingstates:a TEI is allocatedthe multiframe mode is establisheda multiframe mode time-out is runningwaiting for establishmentwaiting for clear



l5609 Duration of Abis resource unavailability

Name Q3 : abisUnavailabilityTimeMoyabisUnavailabilityTimeMax Maximum unavailability. . . . . .durationabisUnavailabilityTimeCum Total unavailability duration. . . . .abisUnavailabilityTimeEch Number of samples. . . . . .

Object : bts

Function : average unavailability duration (= total duration divided by thenumber of samples) andmaximumunavailability duration of theRSLLAPD links used by the cell TRX/DRXs, expressed in milliseconds

Event : LAPD link unavailability/availability, internal sampling time-outelapse:unavailability: start timeravailability: stop timersampling time-out elapse:• read the instantaneous value of LAPD unavailability duration• store its peak value• add it to the total duration of LAPD unavailability in theobservation period






l5610 Duration of Abis resource congestion

Name Q3 : abisCongestionTimeMoyabisCongestionTimeMax Maximum congestion duration. . . . . . . .abisCongestionTimeCum Total congestion duration. . . . . . . .abisCongestionTimeEch Number of samples. . . . . . . .

Object : bts

Function : average congestion duration (= total duration divided by the numberof samples) and maximum congestion duration of the RSL LAPDlinks used by the cell TRX/DRXs, expressed in milliseconds

Event : LAPD link congestion/non-congestion, internal sampling time-outelapse:

congestion: start timernon-congestion: stop timersampling time-out elapse:• read the instantaneous value of LAPD congestion duration• store its peak value• add it to the total duration of LAPD congestion in theobservation period





PE/DCL/DD/0125411--9001--125


2.5 Synthetic permanent BSS counters

l8000 Global failure rate of outgoing handovers on TCH

Name Q3 : hoOutTchGlobalFailRatehoOutTchGlobalFailRateV11

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)

=(1067 + 1068 + 1083)

1 - ----------------------------------∑(1138/i), i = 0 to 14

Type : synthetic permanent

Source : calculated by the OMC when the user asks for an observation report

l8001 Global failure rate of outgoing handovers on SDCCH

Name Q3 : hoOutSdcchGlobalFailRatehoOutSdcchGlobalFailRateV11

Object : bts

Function : global failure rate, in selection and execution, of outgoing intra-bss,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)

=(1142 + 1143 + 1156)

1 - -----------------------------------------∑(1139/i), i = 0 to 14 \ {10,11,12}





l8002 Ratio of outgoing handover requests on TCH

Name Q3 : hoOutTchRequestRatiohoOutTchRequestRatioV11

Object : bts

Function : ratio of outgoing intra-bss, inter-bss, and intra-bts handoversrequested to handovers required on TCH in the cell

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)

=(1075 + 1076 + 1081)

----------------------------------∑(1138/i), i = 0 to 14



l8003 Ratio of outgoing handover requests on SDCCH

Name Q3 : hoOutSdcchRequestRatiohoOutSdcchRequestRatioV11

Object : bts

Function : ratio of outgoing intra-bss, inter-bss, and intra-bts handoversrequested 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)

=(1150 + 1151 + 1154)

------------------------------------------∑(1139/i), i = 0 to 14 \ {10,11,12}




PE/DCL/DD/0125411--9001--125


l8004 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-btshandovers on TCH in the cell

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 +intra-bts handovers on TCH requested

=(1065 + 1066 + 1082)

1 -- ------------------------------------------⟨ 1075 + 1076 + 1081)





l8005 Selection failure rate of outgoing handovers on SDCCH

Name Q3 : hoOutSdcchSelectionFailRate

Object : bts

Function : selection failure rate of outgoing intra-bss, inter-bss, and intra-btshandovers on SDCCH in the cell

Formula : V12outgoing 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

=(1140 + 1141 + 1155)

1 -- ----------------------------------------------------------------------------------1150 + 1151 + 1154



l8006 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-btshandovers 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 - --------------------------------------------outgoing intra handovers on TCH executed +outgoing inter handovers on TCH executed +intra-bts handovers on TCH executed

=(1067 + 1068 + 1083)

1 - --------------------(1065 + 1066 + 1082)




PE/DCL/DD/0125411--9001--125


l8007 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-btshandovers 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 - ----------------------------------------------outgoing intra handovers on SDCCH executed +outgoing inter handovers on SDCCH executed +intra-bts handovers on SDCCH executed

=(1142 + 1143 + 1156)

1 - --------------------(1140 + 1141 + 1155)



l8008 Selection failure rate of incoming handovers on TCH

Name Q3 : hoInTchSelectionFailRate

Object : bts

Function : selection failure rate of incoming intra- and inter-bss handovers onTCH 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

=(1071 + 1072)

1 - -------------(1069 + 1070)





l8009 Selection failure rate of incoming handovers on SDCCH

Name Q3 : hoInSdcchSelectionFailRate

Object : bts

Function : selection failure rate of incoming intra- and inter-bss handovers onSDCCH 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

=(1146 + 1047)

1 - -------------(1144 + 1145)



l8010 Execution failure rate of incoming handovers on TCH

Name Q3 : hoInTchExecutionFailRate

Object : bts

Function : execution failure rate of incoming intra- and inter-bss handovers onTCH 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

=(1073 + 1074)

1 - -------------(1071 + 1072)




PE/DCL/DD/0125411--9001--125


l8011 Execution failure rate of incoming handovers on SDCCH

Name Q3 : hoInSdcchExecutionFailRate

Object : bts

Function : execution failure rate of incoming intra- and inter-bss handovers onSDCCH 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

=(1148 + 1149)

1 - -------------(1146 + 1147)



l8012 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 firstcell in the list of eligible cells to successful outgoing handovers onTCH in the cell

Formula :successful outgoing (intra + inter)handovers on TCH after first attempt

-------------------------------------------------------successful outgoing (intra + inter) handovers on TCH

(1077 + 1078)= ---------------

(1067 + 1068)





l8013 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 firstcell in the list of eligible cells to successful outgoing handovers onSDCCH in the cell

Formula :successful outgoing (intra + inter)handovers on SDCCH after first attempt

--------------------------------------------------------successful outgoing (intra + inter) handovers on SDCCH

=

(1152 + 1153)-------------(1142 + 1143)



l8016 Total number of establishment indications received for call

initializationName Q3 : allEstabIndicSignalling

Object : bts

Function : number of establishment indications received for call initialization

Formula :IMMEDIATE ASSIGNMENT messages transmitted on SDCCH

= [∑(1193/i)], i = 0 to 7



l8017 Number of t3107 time-out elapse: Changing from SDCCH to

TCH or preempted PDTCHName Q3 : t3107ExpAssign

Object : bts

Function : number of mobiles lost during a change from SDCCH to TCH orpreempted PDTCH because of T3107 time-out elapse


PE/DCL/DD/0125411--9001--125


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



l8018 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 SDCCHbecause 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)



l8019 Number of t3107 time-out elapse: Intra-bts handover on TCH

Name Q3 : t3107ExpIntraBtsHoTch

Object : bts

Function : number ofmobiles lost during intra-bts handovers onTCH because ofT3107 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)





l8020 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 T3103time-out elapse. This counter also tallies --for rare cases-- the receipt ofCLEAR COMMAND during an inter-bss handover with a causedifferent 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)



l8021 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 ofT3103 time-out elapse. This counter also tallies --for rare cases-- thereceipt of CLEAR COMMAND during an inter-bss handover with acause 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)




PE/DCL/DD/0125411--9001--125


8037 Total TCHseizureattempts (not including handovers) at cell levelName Q3 : attemptedTchFrSeizureNotInclHo

Object : bts

Function : number of TCH seizure attempts not including handovers = Mobileoriginating 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 counterIn V12, 1841/0 counter is more accurate.

8039 Total TCH seizure attempts (including handovers) at cell levelName Q3 : attemptedTchFrSeizureInclHo

Object : bts

Function : number of TCH seizure attempts including handovers = Mobileoriginating call attempt(s) + Mobile terminating call attempt(s) +Re--establishment attempt(s) +Directed Retry attempt(s) + Incomingintra--bss handover(s) + incoming inter--bss handover(s)

Formula : 1841/0 + 1069 +1070



Note : V12 counter

l8040 TCH allocation failures at cell levelName Q3 : allocationFailureTchFrSeizureInclHo

Object : bts

Function : number of TCH allocation failures including handovers = Mobileoriginating call failure(s) + Mobile terminating call failure(s) +Re--establishment failure(s) + Directed Retry failure(s) + incomingintra--bss (inter--bts) handover TCH allocation failure(s) + incominginter--bss handover TCH allocation failure(s)

Formula : 1842/0 + 1758/0 + 1760/0



Note : V12 counter



l8044 Clear request at cell level

Name Q3 : clearRequestTraffic

Object : bts

Function : number of call dropped by a CLEAR REQUEST after TCHassignment complete

Function : Σ 1164/i -- (1164/0 + 1164/1 + 1164/3 + 1164/20 +1164/28 + 1164/31)



Note : V12 counter

l8050 Ratio of maximum Downlink power use on TCHs

Name Q3 : relativeTimeDLPowerCtrlMaxTch

Object : bts

Function : ratio of maximum Downlink power use duration on busy TCHs toTCH 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

l8051 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 TCHconnection duration in the cell


PE/DCL/DD/0125411--9001--125


Formula :duration of maximum Uplink power use on busy TCHs-------------------------------------------------

connection duration of TCHs

1199Cum= -------1600Cum





l8052 Ratio of maximum Downlink power use on SDCCHs

Name Q3 : relativeTimeDLPowerCtrlMaxSdcch

Object : bts

Function : ratio of maximumDownlink power use duration on busy SDCCHs toSDCCH connection durations in the cell

Formula :duration of maximum Downlink power use on busy SDCCHs-----------------------------------------------------


1601Cum= -------1603Cum







l8053 Ratio of maximum Uplink power use on SDCCHs

Name Q3 : relativeTimeULPowerCtrlMaxSdcch

Object : bts

Function : ratio of maximum Uplink power use duration on busy SDCCHs toSDCCH connection durations in the cell

Formula :duration of maximum Uplink power use on busy SDCCHs---------------------------------------------------

connection duration of all SDCCHs

1602Cum= -------1603Cum





l8104 Ratio of number of requested handovers by dualband MSs to

second frequency band to the number of requested handover fordualband MS to main frequency band

Name Q3 : requestedHandoverForDualBandMSToSecondVersusMainBand

Object : bts

Function : ratio of number of requested handovers by dualband MSs to secondfrequency band to the number of requested handover by dualbandMSs to main frequency band


PE/DCL/DD/0125411--9001--125


Formula :outgoing handovers requested by dualband MSs from

main to second frequency band +outgoing handovers requested by dualband MSs from

second to same frequency band

---------------------------------------------------outgoing handovers requested by dualband MSs from

main to same frequency band +outgoing handovers requested by dualband MSs from

second to main frequency band

1208 + 1784= ------------1783 + 1785



Note : V12 counter

l8105 Ratio of number of establishments of dualbandMSs to numberof

establishments of phase 1 & 2 MSsName Q3 : immAssignDualBandMSRate

Object : bts

Function : ratio of number of establishments of dualband MSs to number ofestablishments of phase 1 & 2 MSs

Formula :immediate assignments for dualband MS

---------------------------------------------------ESTABLISH INDICATION messages inestablishement phase received (by cause)

=1207

-------------------------∑(1193/i), i = 0 to 7



Note : V12 counter

l8110 Failure rate of cell tiering from large pattern to small patternName Q3 : hoIntraBtsFailRateTchTieringLargeToSmallPattern

Object : bts

Function : failure rate in selection and execution of intra--bts handovers in thecell for cell tiering from large pattern to small pattern



Formula :1802/0

1 - -----------1138/15




Note : V12 counter

l8111 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 thecell for cell tiering from small pattern to large pattern

Formula :1802/1

1 - -----------1138/16




Note : V12 counter

l8500 Maximum global failure rate of outgoing handovers on TCH

Name Q3 : hoOutTchMaxFailRatehoOutTchMaxFailRateV11

Object : bsc

Function : maximum global failure rate, in selection and execution, of outgoingintra-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)





PE/DCL/DD/0125411--9001--125


l8501 Maximum global failure rate of outgoing handovers on SDCCH

Name Q3 : hoOutSdcchMaxFailRatehoOutSdcchMaxFailRateV11

Object : bsc

Function : maximum global failure rate, in selection and execution, of outgoingintra-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)




l8502 Maximum ratio of outgoing handover requests on TCH

Name Q3 : hoOutTchRequestMaxRatiohoOutTchRequestMaxRatioV11

Object : bsc

Function : maximum ratio of outgoing intra-bss, inter-bss, and intra-btshandover requests to handovers on TCH required in the BSS

Formula :max_cell(ratio of outgoing handover requests on TCH)

= max_cell(8002)




l8503 Maximum ratio of outgoing handover requests on SDCCH

Name Q3 : hoOutSdcchRequestMaxRatiohoOutSdcchRequestMaxRatioV11

Object : bsc

Function : maximum ratio of outgoing intra-bss, inter-bss, and intra-btshandover requests to handovers on SDCCH required in the BSS



Formula :max_cell(ratio of outgoing handover requests on SDCCH)

= max_cell(8003)




l8504 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, andintra-bts handovers on TCH in the BSS

Formula :max_cell(selection failure rate of


= max_cell(8004)




l8505 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, andintra-bts handovers on SDCCH in the BSS



= max_cell(8005)





PE/DCL/DD/0125411--9001--125


l8506 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, andintra-bts handovers on TCH in the BSS

Formula :max_cell(execution failure rate of


= max_cell(8006)




l8507 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, andintra-bts handovers on SDCCH in the BSS



= max_cell(8007)




l8508 Maximum selection failure rate of incoming handovers on TCH

Name Q3 : hoInTchSelectionFailMaxRate

Object : bsc

Function : maximum selection failure rate of incoming intra- and inter-bsshandovers on TCH in the BSS




incoming handovers on TCH)

= max_cell(8008)




l8509 Maximum selection failure rate of incoming handovers on

SDCCH

Name Q3 : hoInSdcchSelectionFailMaxRate

Object : bsc

Function : maximum selection failure rate of incoming intra- and inter-bsshandovers on SDCCH in the BSS


incoming handovers on SDCCH)

= max_cell(8009)




l8510 Maximum execution failure rate of incoming handovers on TCH

Name Q3 : hoInTchExecutionFailMaxRate

Object : bsc

Function : maximum execution failure rate of incoming intra- and inter-bsshandovers on TCH in the BSS


incoming handovers on TCH)

= max_cell(8010)





PE/DCL/DD/0125411--9001--125


l8511 Maximum execution failure rate of incoming handovers on

SDCCH

Name Q3 : hoInSdcchExecutionFailMaxRate

Object : bsc

Function : maximum execution failure rate of incoming intra- and inter-bsshandovers on SDCCH in the BSS


incoming handovers on SDCCH)

= max_cell(8011)




l8512 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 handoversafter first attempt on TCH in the BSS

Formula :min_cell(ratio of successful outgoing

handovers on TCH after first attempt)

= min_cell(8012)




l8513 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 handoversafter first attempt on SDCCH in the BSS



Formula :min_cell (ratio of successful outgoing

handovers on SDCCH after first attempt)

= min_cell (8013)




l8550 BSC global failure rate of outgoing handovers on TCH

Name Q3 : hoOutTchBscGlobalFailRatehoOutTchBscGlobalFailRateV11

Object : bsc

Function : global failure rate, in selection and execution, of outgoing intra-bss,inter-bss, and intra-bts handovers on TCH in the BSS

Formula :sum_cell (successful outgoing

intra + inter + intra-btshandovers on TCH)

1 - ----------------------------------------------sum_cell(handovers on TCH required (by cause))

=sum_cell(1067 + 1068 + 1083)

1 - --------------------------------------------sum_cell(∑(1138/i)), i = 0 to 14



l8551 BSC global failure rate of outgoing handovers on SDCCH

Name Q3 : hoOutSdcchBscGlobalFailRatehoOutSdcchBscGlobalFailRateV11

Object : bsc

Function : global failure rate, in selection and execution, of outgoing intra-bss,inter-bss, and intra-bts handovers on SDCCH in the BSS


PE/DCL/DD/0125411--9001--125


Formula :sum_cell (successful outgoing

intra + inter + intra-btshandovers on SDCCH)

1 - ------------------------------------------------sum_cell(handovers on SDCCH required (by cause))

=sum_cell(1142 + 1143 +1156)

1 - ---------------------------------------------------sum_cell(∑(1139/i)), i = 0 to 14 \ {10,11,12}



l8552 BSC ratio of outgoing handover requests on TCH

Name Q3 : hoOutTchRequestBscRatiohoOutTchRequestBscRatioV11

Object : bsc

Function : ratio of outgoing intra-bss, inter-bss, and intra-bts handoversrequested 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)

1 - -----------------------------------------------sum_cell(handovers on TCH required (by cause))

=sum_cell(1075 + 1076 + 1081)

1 - --------------------------------------------sum_cell(∑(1138/i)), i = 0 to 14



l8553 BSC ratio of outgoing handover requests on SDCCH

Name Q3 : hoOutSdcchRequestBscRatiohoOutSdcchRequestBscRatioV11

Object : bsc

Function : ratio of outgoing intra-bss, inter-bss, and intra-bts handoversrequested 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)

1 - -------------------------------------------------sum_cell(handovers on SDCCH required (by cause))

=sum_cell(1150 + 1151 + 1154)

1 - ----------------------------------------------------sum_cell(∑(1139/i)), i = 0 to 14 \ {10,11,12}



l8554 BSC selection failure rate of outgoing handovers on TCH

Name Q3 : hoOutTchSelectionBscFailRate

Object : bsc

Function : selection failure rate of outgoing intra-bss, inter-bss, and intra-btshandovers on TCH in the BSS

Formula : V12outgoing 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 +intra-bts handovers on TCH requested

=(1065 + 1066 + 1082)

1 -- --------------------------------------------------------------------1075+ 1076 + 1081



l8555 BSC selection failure rate of outgoing handovers on SDCCH

Name Q3 : hoOutSdcchSelectionBscFailRate

Object : bsc

Function : selection failure rate of outgoing intra-bss, inter-bss, and intra-btshandovers on SDCCH in the BSS


PE/DCL/DD/0125411--9001--125


Formula : V12outgoing 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

=(1140 + 1141 + 1155)

1 -- ----------------------------------------------------------------------------------1150 + 1151 + 1154



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-btshandovers on TCH in the BSS

Formula :

sum_cell(successful outgoing intra handovers on TCH +successful outgoing inter handovers on TCH +successful intra-bts handovers on TCH)

1 - ------------------------------------------------sum_cell

(outgoing intra handovers on TCH executed +outgoing inter handovers on TCH executed +intra-bts handovers on TCH executed)

=sum_cell(1067 +1068 +1083)

1 - --------------------------sum_cell(1065 +1066 +1082)





l8557 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-btshandovers on SDCCH in the BSS

Formula :sum_cell

(successful outgoing intra handovers on SDCCH +successful outgoing inter handovers on SDCCH +successful intra-bts handovers on SDCCH)

1 - --------------------------------------------------sum_cell

(outgoing intra handovers on SDCCH executed +outgoing inter handovers on SDCCH executed +intra-bts handovers on SDCCH executed)

=sum_cell(1142 + 1143 + 1156)

1 - ----------------------------sum_cell(1140 + 1141 + 1155)



l8558 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 theBSS

Formula :sum_cell(incoming inter handovers on TCH executed)

1 - ---------------------------------------------------sum_cell(incoming inter handovers on TCH requested)

=sum_cell(1072)

1 - --------------sum_cell(1070)




PE/DCL/DD/0125411--9001--125


l8559 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 inthe BSS

Formula :sum_cell(incoming inter handovers on SDCCH executed)

1 - -----------------------------------------------------sum_cell(incoming inter handovers on SDCCH requested)

=sum_cell(1147)

1 - --------------sum_cell(1145)



l8560 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 theBSS

Formula :sum_cell(successful incoming inter handovers on TCH)

1 - ----------------------------------------------------sum_cell(incoming inter handovers on TCH executed)

=sum_cell(1074)

1 - --------------sum_cell(1072)





l8561 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 inthe BSS

Formula :sum_cell(successful incoming inter handovers on SDCCH)

1 - ------------------------------------------------------sum_cell(incoming inter handovers on SDCCH executed)

=sum_cell(1149)

1 - --------------sum_cell(1147)



l8562 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 theBSS

Formula :sum_cell(successful incoming intra handovers on TCH)

1 - ----------------------------------------------------sum_cell(incoming intra handovers on TCH executed)

=sum_cell(1073)

1 - --------------sum_cell(1071)




PE/DCL/DD/0125411--9001--125


l8563 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 inthe BSS

Formula :sum_cell(successful incoming intra handovers on SDCCH)

1 - ------------------------------------------------------sum_cell(incoming intra handovers on SDCCH executed)

=sum_cell(1148)

1 - --------------sum_cell(1146)



l8564 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 theBSS

Formula :sum_cell(successful outgoing inter handovers on TCH)

1 - ----------------------------------------------------sum_cell(outgoing inter handovers on TCH executed)

=sum_cell(1068)

1 - --------------sum_cell(1066)





l8565 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 inthe BSS

Formula :sum_cell(successful outgoing inter handovers on SDCCH)

1 - ------------------------------------------------------sum_cell(outgoing inter handovers on SDCCH executed)

=sum_cell(1143)

1 - --------------sum_cell(1141)



l8566 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 firstattempt to successful handovers on TCH in the BSS

Formula :sum_cell (successful outgoing (intra + inter)

handovers on TCH after first attempt)-----------------------------------------------sum_cell (successful outgoing (intra + inter)

handovers on TCH)

=sum_cell(1077 + 1078)---------------------sum_cell(1067 + 1068)




PE/DCL/DD/0125411--9001--125


l8567 BSC ratio of successful outgoing handovers on SDCCHafter first

attempt

Name Q3 : hoOutFirstSuccessSdcchRatio

Object : bsc

Function : ratio of successful outgoing intra- and inter-bss handovers after firstattempt to successful handovers on SDCCH in the BSS

Formula :sum_cell (successful outgoing (intra + inter)

handovers on SDCCH after first attempt)-------------------------------------------------sum_cell (successful outgoing (intra + inter)

handovers on SDCCH)

=sum_cell(1152 + 1153)---------------------sum_cell(1142 + 1143)



l8568 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)






l8569 Ratio of SCCP failure

Name Q3 : sccpResourceFailureRatio

Object : bsc

Function : ratio of the number of SCCP connection refusals (by BSC orMSC) tothe number of SCCP connections allocated (refer to the followingformula)

Formula :sccpResourceFailureRatio bsc=((sccpRessourceFailure+sccpRessourceFailureBscRefusal) /(sccpAllocated+sccpRessourceFailure+sccpRessourceFailureBscRefusal))

*greaterperc (sccpAllocated+sccpRessourceFailure+sccpRessourceFailureBscRefusal,signif1bsc)

1106/0 + 1106/1 greaterperc(1104/0= ------------------------- * +1106/0+1106/1,1104/0 + 1106/0 + 1106/1 signif1bsc)



l8600 Average number of SDCCHs used in the BSS

Name Q3 : bscSdcchAveragedUsedMoybscSdcchAveragedUsedMax

Object : bsc

Function : average number or maximum number of SDCCHs allocated in allcells controlled by the BSC

Formula :sum_cell(average number of SDCCHs used)

= sum_cell(1607)with 1607 = ∑(1607) on all transceiverZones





PE/DCL/DD/0125411--9001--125


l8601 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 SDCCHunavailability 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




l8602 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 allcells controlled by the BSC


= sum_cell(1611/1)with 1611/1 = ∑(1611/1) on all transceiverZones




l8603 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 bythe BSC








l8604 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 topaging 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)




l8605 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 differentfrom “reply to paging request” in all cells controlled by the BSC


PE/DCL/DD/0125411--9001--125


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)




l8606 Number of outgoing handovers on TCH executed in the BSS

Name Q3 : hoOutExecutionBscTch

Object : bsc

Function : number of attempts to executeoutgoing intra- and inter-bsshandoverson TCH in all cells controlled by the BSC

Formula :sum_cell

(outgoing intra handovers on TCH executed +outgoing inter handovers on TCH executed +intra-bts handovers on TCH executed)

= sum_cell(1065 + 1066 + 1082)




l8607 Number of outgoing handovers on SDCCH executed in the BSS

Name Q3 : hoOutExecutionBscSdcch

Object : bsc

Function : number of attempts to executeoutgoing intra- and inter-bsshandoverson SDCCH in all cells controlled by the BSC



Formula :sum_cell

(outgoing intra handovers on SDCCH executed +outgoing inter handovers on SDCCH executed +intra-bts handovers on SDCCH executed)

= sum_cell(1140 + 1141 + 1155)




l8608 Number of incoming handovers on TCH executed in the BSSName Q3 : hoInExecutionBscTch

Object : bscFunction : 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)

Type : synthetic permanentSource : calculated by the OMC when the user asks for an observation report


l8609 Number of incoming handovers on SDCCH executed in the BSSName Q3 : hoInExecutionBscSdcchObject : bsc

Function : number of attempts to execute incoming intra- and inter-bsshandovers on SDCCH in all cells controlled by the BSC

Formula :sum_cell

(incoming intra handovers on SDCCH executedincoming inter handovers on SDCCH executed)

= sum_cell(1146 + 1147)





PE/DCL/DD/0125411--9001--125


l8610 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)with 1606 = ∑(1606) on all transceiverZones




l8611 Total numberof TCH/FRallocated in theBSSbecause of SDCCH

unavailability

Name Q3 : bscTchFrAllocatedOverflowAllocation

Object : bsc

Function : total number of TCH allocations because of SDCCH unavaibility inall cells controlled by the BSS

Formula :sum_cell (number of TCH/FR allocated)because of SDCCH unavailibity





l8612 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 cellscontrolled by the BSC



Formula :sum_cell(number of TCH/FR allocated)for call reestablishments





l8613 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 bythe BSC

Formula :sum_cell(number of TCH/FR allocated) for traffic





l8623 Average downlink RxLev in dBm

Name Q3 : averageDLRxLev

Object : bts

Function : average downlink RxLev for the cell, in dBm

Formula :1623/0/Cum/Cell

------------------------------------------------- - 1101600/0/Cum/Cell/480 + 1603/0/Cum/Cell/470 - 1622/0/Cum/Cell

= -110 +(rxLevDownlink /(connectionDurationTchCum / 480+ connectionDurationSdcchCum / 470

- msLostMeasurements) )





PE/DCL/DD/0125411--9001--125


l8624 Average uplink RxLev in dBm

Name Q3 : averageULRxLev

Object : bts

Function : average uplink RxLev for the cell, in dBm


----------------------------------------------- - 1101600/0/Cum/Cell/480 + 1603/0/Cum/Cell/470

= -110 + (rxLevUplink /(connectionDurationTchCum / 480+ connectionDurationSdcchCum / 470) )




l8625 Average downlink RxQual in BER

Name Q3 : averageDLRxQual

Object : bts

Function : average downlink RxQual for the cell, in BER


----------------------------------------------------- / 1101600/0/Cum/Cell/480 + 1603/0/Cum/Cell/470 - 1622/0/Cum/Cell

= (rxQualDownlink / (connectionDurationTchCum / 480+ connectionDurationSdcchCum / 470- msLostMeasurements) /100))




l8626 Average uplink RxQual in BER

Name Q3 : averageULRxQual

Object : bts

Function : average uplink RxQual for the cell, in BER




----------------------------------------------- / 1101600/0/Cum/Cell/480 + 1603/0/Cum/Cell/470

= (rxQualUplink / (connectionDurationTchCum / 480+ connectionDurationSdcchCum / 470) / 100)




l8628 Quality of downlink Abis TRAU frame

Name Q3 : dlMutedAbisTrauFrameRate

Object : bts

Function : ratio of the number of downlink Abis TRAU frame muted orcorrected to the number of downlink Abis TRAU frame received

Formula :1718 + 1719

-------------------------1717

=(abisTrauFrameCorrected + abisTrauFrameMuted)/

abisTrauFrameDlReceived)



Note : V12 counter

l8629 Correction rate of downlink Abis TRAU frame

Name Q3 : pcmErrCorrEfficiency

Object : bts

Function : ratio of the number of downlink Abis TRAU frames corrected to thenumber of downlink Abis TRAU frames received

Formula :1718

--------1717



Note : V12 counter


PE/DCL/DD/0125411--9001--125


l8637 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

l8639 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

l8640 TCH allocation failures at bsc level

Name Q3 : bscAllocationFailureTchFrSeizureInclHo

Object : bsc

Function : number of TCH allocation failures including handovers

Formula : Σ 8040



Note : V12 counter

l8644 G14 consolidated at bsc level

Name Q3 : bscClearRequestTraffic

Object : bsc

Function : number of calls dropped by a CLEAR_REQUEST after TCHassignment completed



Formula : Σ 8044



Note : V12 counter

l8700 PCM unavailability in the BSS in seconds

Name Q3 : pcminsecondsCumpcminsecondsMaxpcminsecondsMoypcminsecondsEch

Object : bsc

Function : PCM unavailability in the BSS, expressed in seconds

Formula :average time of PCM availability--------------------------------

1000

= c1114 divided by 1000




l8701 Duration of TCH saturation in seconds

Name Q3 : allTchinsecondsCumallTchinsecondsMaxallTchinsecondsMoyallTchinsecondsEch

Object : bts

Function : average duration to allocate all TCH/FR resources and PDTCHresources configured as preemptable in the cell


PE/DCL/DD/0125411--9001--125


Formula :average duration to allocate all TCH/FR resources

and PDTCH resources configured as preemptable-------------------------------------------------

1000

= c1057 divided by 1000with 1057 = ∑ (1057) on all transceiverZones




l8702 Duration of SDCCH saturation in seconds

Name Q3 : allSdcchinsecondsallSdcchinsecondsCumallSdcchinsecondsEchallSdcchinsecondsMaxallSdcchinsecondsMoy

Object : bts

Function : average allocation duration of all SDCCH resources in the cell

Formula :average duration of all SDCCH resource allocations--------------------------------------------------

1000

= c1060 divided by 1000with 1060 = ∑ (1060) on all transceiverZones




l8706 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 thenumber of SDCCH allocation attempts



Formula :C1608

-------------------------1606 + 1608 + 1609/2

with 1608 = ∑ (1608) on all transceiverZoneswith 1606 = ∑ (1606) on all transceiverZoneswith 1609/2 = ∑ (1609/2) on all transceiverZones



Note : V12 counter

l8707 Ratio of TCH resource failures in the cell

Name Q3 : cellTchResourceFailureRatio

Object : bts

Function : ratio of thenumber ofTCHallocation failures in the cell to thenumberof TCH or preempted PDTCH allocation attempts

Formula :1613 + 1163/30

-----------------------------------------1613 + 1163/30 + 1609/2 + 1609/1

with 1613 = ∑(1613) on all transceiverZoneswith 1609/1 = ∑(1609/1) on all transceiverZoneswith 1609/2 = ∑(1609/2) on all transceiverZones



Note : V12 counter

l8713 Ratio of the number of communications abnormaly released in

signalling phase in the cell

Name Q3 : signallingReleaseRatio

Object : bts

Function : ratio of the number true communications released in signalling phasein the cell, except release by standard CLEAR_COMMAND or onphantom requests, to the number of communications established in asignalling channel (initial call establishment or successful incominghandover on SDCCH


PE/DCL/DD/0125411--9001--125


Formula :∑(1163/i), i for each possible cause

-----------------------------------------1195 + 1196

bdr1778 - 1163/6

= --------------------1195 + 1196



Note : V12 counter

l8714 Ratio of the number of communications abnormaly released in

traffic phase in the cell

Name Q3 : callDropTrafficRatio

Object : bts

Function : ratio of the number of communications released in traffic phase in thecell, except release by standard CLEAR_COMMAND, to the numberof communications established in a traffic channel (initial TCH orpreempted PDTCH seizures or successful incoming handover onTCH)

Formula :∑(1164/i), i for each possible cause

-----------------------------------------1050 - 1083 + 1073 + 1074

bdr1779

= -----------------------------------------1050 - 1083 + 1073 + 1074



Note : V12 counter

l8726 Number of decoded ramdom accesses received by the BTS from

the MS for all the cells

Name Q3 : rachBusyCountCell

Object : bts

Function : sum for each CCCH occurence of decoded random accesses receivedby the BTS from the MS



Formula :∑(1026), for each CCCH occurence=rachBusyCount + rachBusyCount2+ rachBusyCount4 + rachBusyCount6



Note : V12 counter

l8727 Number of ramdom accesses transmitted to the BSC for all the

cells

Name Q3 : rachAccessCountCell

Object : bts

Function : sum for each CCH occurrence of transmitted random accesses

Formula :∑(1027), for each CCCH occurence



Note : V12 counter

l8728 Number of paging requests immediately served for all the cells

Name Q3 : pchNoWaitCell

Object : bts

Function : sum for each CCCH occurence of immediately served pagings




Note : V12 counter

l8729 Number of paging requests served after one wait for all the cells

Name Q3 : pchOneWaitCell

Object : bts

Function : sum for each CCCH occurence of served pagings after one wait


PE/DCL/DD/0125411--9001--125





Note : V12 counter

l8730 Number of paging requests served after two waits for all the cells

Name Q3 : pchTwoWaitCell

Object : bts

Function : sum for each CCCH occurence of served pagings after two waits




Note : V12 counter

l8731 Number of paging requests served after more than two waits for

all the cells

Name Q3 : pchMoreWaitCell

Object : bts

Function : sum for each CCCH occurence of served pagings after more than twowaits




Note : V12 counter

l8733 Average level on non decoded RACHs for all the cells

Name Q3 : rachNonDecodedAvLevelCell

Object : bts

Function : average on all CCCH occurrences of level on non decoded RACHs



Formula :∑(1033cum)/ ∑(1033ech), for each CCCH occurence= MAX (1033max), for each CCCH occurence



Note : V12 counter

l8734 Average number of waitingmessages in PAGCHqueue for all the

cells

Name Q3 : pchAveragedQueueLengthCellpchAveragedQueueLengthCellCumpchAveragedQueueLengthCellEchpchAveragedQueueLengthCellMaxpchAveragedQueueLengthCellMoy

Object : bts

Function : average on all CCCH occurrences of number of waiting messages inPAGCH

Formula :∑(1604cum)/ ∑(1604ech), for each CCCH occurence= MAX (1604max), for each CCCH occurence



Note : V12 counter

l8735 Number of pagings discarded in the PAGCH queue for all the

cells

Name Q3 : pchQueuePagesDiscardedCell

Object : bts

Function : sum for each CCCH occurence of discarded pagings




Note : V12 counter


PE/DCL/DD/0125411--9001--125


l8757 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 failuresin the TDMA class

Formula :1613

----------------------1613 + 1609/0 + 1609/1



Note : V12 counter

l8760 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

l8761 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


PE/DCL/DD/0125411--9001--125


2.6 Raw permanent md counters

2.6.1 SYBASE counters

These totalizer counters are provided by the SYBASE OMC6R agent server. Theyare read by the OMC--R agent self-observation task at the end of eachmdGranularityPeriod.

ll9940 Total number of SYBASE errors

Name Q3 : sybaseTotalError

Object : SYBASE agent server

Function : number of anomalies detected by the SYBASE server during diskread/write operations in the observation period


Source : SYBASE server, calculated by the OMC--R agent

ll9941 Total number of SYBASE read operations

Name Q3 : sybaseTotalRead


Function : number of disk read operations performed by the SYBASE server inthe observation period



ll9942 Total number of SYBASE write operations

Name Q3 : sybaseTotalWrite


Function : number of disk write operations performed by the SYBASE server inthe observation period





ll9943 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



ll9944 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 duringthe observation period, expressed in 1/10th of a second



ll9945 SYBASE server idle time (s)

Name Q3 : sybaseIdle


Function : time of SYBASE server unoccupancy in the observation period,expressed in seconds



ll9946 Number of packets received by the SYBASE server

Name Q3 : sybasePacketIn


Function : number of data packets received by the SYBASE server in theobservation period




PE/DCL/DD/0125411--9001--125


ll9947 Number of packets sent by the SYBASE server

Name Q3 : sybasePacketOut


Function : number of data packets sent by the SYBASE server in the observationperiod



ll9948 Number of erroneous packets sent or received by the SYBASE

server

Name Q3 : sybasePacketErr


Function : number of anomalies detected by the SYBASE server when sendingor receiving data packets in the observation period



ll10047 Average filling rate of configuration database cm_db

Name Q3 : cmDatabaseUsedcmDatabaseUsedCum Total filling rate. . . . . . . . . .cmDatabaseUsedEch Number of samples. . . . . . . . . . .

Object : active OMC--R agent server

Function : average rate (= total rate divided by the number of samples) ofconfiguration “cm_db” database used, calculated at the end of theobservation period, expressed in %





ll10048 Average filling rate of fault database fm_db

Name Q3 : fmDatabaseUsedfmDatabaseUsedCum 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 observationperiod, expressed in %



ll10049 Average filling rate of configuration log cm_db

Name Q3 : cmLogUsedcmLogUsedCum Total filling rate. . . . . . . . . . . . . .cmLogUsedEch Number of samples. . . . . . . . . . . . . . .


Function : average rate (= total rate divided by the number of samples) ofconfiguration “cm_db” log used, calculated at the end of theobservation period, expressed in %



ll10050 Average filling rate of fault log fm_db

Name Q3 : fmLogUsedfmLogUsedCum 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 %




PE/DCL/DD/0125411--9001--125


2.6.2 SCSE counters

These totalizer counters are provided by the SCSE service. They are read by theOMC--R agent self-observation task at the end of each mdGranularityPeriod.

ll9970 Number of TGE sent

Name Q3 : scseTgeOut


Function : number of global operation transactions (TGE) sent by the server tothe BSC in the observation period


Source : SCSE service, calculated by the OMC--R agent

ll9971 Number of RGE received

Name Q3 : scseRgeIn


Function : number of global operation replies (RGE) sent by the BSC to theserver in the observation period



ll9972 Number of BSS/OMC--R link failures

Name Q3 : scseFailConnect


Function : number of BSS/OMC--R link failures detected in the observationperiod



ll9973 Total number of TGE reservations refused

Name Q3 : scseTotTgeRefused


Function : number of TGE reservations refused by the server in the observationperiod





ll9974 Total number of association release requests sent by the BSC

Name Q3 : scseTotAssocFree


Function : number of association release requests sent by the BSC in theobservation period



2.6.3 UNIX counters

These totalizer and value counters are provided by the SUNOS system. They areread by the OMC--R agent self-observation task at the end of eachmdGranularityPeriod.

ll9984 Average load of NMC server CPU 0

Name Q3 : unixCpu0UsedNMCSrvunixCpu0UsedNMCSrvCum Total load of NMC server CPU. . . . .0unixCpu0UsedNMCSrvEch Number of samples. . . . . .


Function : average load (= total load divided by the number of samples) of theserver CPU 0 in the observation period, expressed in %


Source : SUNOS system, calculated by the OMC--R agent

ll9985 Average load of NMC server CPU 1

Name Q3 : unixCpu1UsedNMCSrvunixCpu1UsedNMCSrvCum Total load of NMC server CPU. . . . .1unixCpu1UsedNMCSrvEch Number of samples. . . . . .






PE/DCL/DD/0125411--9001--125


ll9988 Average filling rate of NMC server SWAP area

Name Q3 : unixSwapNMCSrvunixSwapNMCSrvCum Total filling rate of SWAP area. . . . . . . . .unixSwapNMCSrvEch Number of samples. . . . . . . . . .


Function : average rate (= total rate divided by the number of samples) of swapmemory used in the server, calculated at the end of the observationperiod, expressed in %



ll9990 Average filling rate of NMC server “/” partition

Name Q3 : unixRootPartitionNMCSrvunixRootPartitionNMCSrvCum Total partition filling rate. .unixRootPartitionNMCSrvEch Number of samples. . .


Function : average rate (= total rate divided by the number of samples) of diskroot partition used in the server, calculated at the end of theobservation period, expressed in %



ll9991 Average filling rate of NMC server “/tmp” partition

Name Q3 : unixTmpPartitionNMCSrvunixTmpPartitionNMCSrvCum Total partition filling rate. .unixTmpPartitionNMCSrvEch Number of samples. . .


Function : average rate (= total rate divided by the number of samples) of disk“/tmp” partition used in the server, calculated at the end of theobservation period, expressed in %





ll9993 Average filling rate of “/MD/obs” partition

Name Q3 : unixObsPartitionunixObsPartitionCum Total partition filling rate. . . . . . . . . .unixObsPartitionEch Number of samples. . . . . . . . . . .


Function : average rate (= total rate divided by the number of samples) of disk“/MD/obs” partition used in the server, calculated at the end of theobservation period, expressed in %



ll9994 Average filling rate of “/MD/notif” partition

Name Q3 : unixNotifPartitionunixNotifPartitionCum Total partition filling rate. . . . . . . . .unixNotifPartitionEch Number of samples. . . . . . . . . .


Function : average rate (= total rate divided by the number of samples) of disk“/MD/notif” partition used in the server, calculated at the end of theobservation period, expressed in %



ll9995 Average filling rate of “/MD/restored/obs” partition

Name Q3 : unixRestoredObsPartitionunixRestoredObsPartitionCum Total partition filling rate. . .unixRestoredObsPartitionEch Number of samples. . . .


Function : average rate (= total rate divided by the number of samples) of disk“/MD/restored/obs” partition used in the server, calculated at the endof the observation period, expressed in %




PE/DCL/DD/0125411--9001--125


ll9996 Average filling rate of “/MD/restored/notif” partition

Name Q3 : unixRestoredNotifPartitionunixRestoredNotifPartitionCum Total partition filling rate. .unixRestoredNotifPartitionEch Number of samples. . .


Function : average rate (= total rate divided by the number of samples) of disk“/MD/restored/notif” partition used in the server, calculated at the endof the observation period, expressed in %



ll9997 Average filling rate of “/MD/trace_function” partition

Name Q3 : unixTracePartitionunixTracePartitionCum Total partition filling rate. . . . . . . . .unixTracePartitionEch Number of samples. . . . . . . . . .


Function : average rate (= total rate divided by the number of samples) of disk“/MD/trace_function” partition used in the server, calculated at theend of the observation period, expressed in %



ll9998 Average filling rate of “/MD/data/ssn” partition

Name Q3 : unixDataSsnPartitionunixDataSsnPartitionCum Total partition filling rate. . . . . . .unixDataSsnPartitionEch Number of samples. . . . . . . .


Function : average rate (= total rate divided by the number of samples) of disk“/MD/data/ssn” partition used in the server, calculated at the end ofthe observation period, expressed in %





ll9999 Average filling rate of “/MD/restored/trace_function” partition

Name Q3 : unixRestoredTracePartitionunixRestoredTracePartitionCum Total partition filling rate. .unixRestoredTracePartitionEch Number of samples. . .


Function : average rate (= total rate divided by the number of samples) of disk“/MD/restored/trace_function” partition used in the server, calculatedat the end of the observation period, expressed in %



ll10043 Average filling rate of NMC server “/MD/base” partition

Name Q3 : unixMdrBasePartitionNMCSrvunixMdrBasePartitionNMCSrvCum . . . . . Total partition filling rateunixMdrBasePartitionNMCSrvEch . . . . . . Number of samples


Function : average rate (= total rate divided by the number of samples) of disk“/MD/base” partition used in the server, calculated at the end of theobservation period, expressed in %



ll10044 Average filling rate of NMC server “/MD/data” partition

Name Q3 : unixMdrDataPartitionNMCSrvunixMdrDataPartitionNMCSrvCum . . . . . Total partition filling rateunixMdrDataPartitionNMCSrvEch . . . . . . Number of samples


Function : average rate (= total rate divided by the number of samples) of disk“/MD/data” partition used in the server, calculated at the end of theobservation period, expressed in %




PE/DCL/DD/0125411--9001--125


ll10045 Average filling rate of NMC server “/CMN/base” partition

Name Q3 : unixCmnBasePartitionNMCSrvunixCmnBasePartitionNMCSrvCum . . . . Total partition filling rateunixCmnBasePartitionNMCSrvEch . . . . . . Number of samples


Function : average rate (= total rate divided by the number of samples) of disk“/CMN/base” partition used in the server, calculated at the end of theobservation period, expressed in %



ll10046 Average filling rate of NMC server “/CMN/data” partition

Name Q3 : unixCmnDataPartitionNMCSrvunixCmnDataPartitionNMCSrvCum . . . . Total partition filling rateunixCmnDataPartitionNMCSrvEch . . . . . . Number of samples


Function : average rate (= total rate divided by the number of samples) of disk“/CMN/data” partition used in the server, calculated at the end of theobservation period, expressed in %



2.6.4 Q3 counters

These totalizer counters are provided by the CMIS and FTAM services. They areread by the OMC--R agent self-observation task at the end of eachmdGranularityPeriod.

2.6.4.1 Request on md subtree counters

ll10000 Number of CMIS GET requests received for the md subtree

Name Q3 : ommdGetRequest


Function : number of CMIS GET requests about md subtree objects received inthe observation period

Event : receipt of a CMIS GET request about an md subtree object


Source : CMIS service, calculated by the OMC--R agent



ll10001 Number of CMIS GET confirmations sent for the md subtree

Name Q3 : ommdGetConf


Function : number of CMISGET confirmations aboutmd subtree objects sent inthe observation period

Event : transmission of aCMISGET confirmation about anmd subtreeobject



ll10002 Number of CMIS CREATE requests received for the md subtree

Name Q3 : ommdCreRequest


Function : number of CMIS CREATE requests about md subtree objectsreceived in the observation period

Event : receipt of a CMIS CREATE request about an md subtree object



ll10003 Number of CMIS CREATE confirmations sent for the md

subtree

Name Q3 : ommdCreConf


Function : number of CMIS CREATE confirmations about md subtree objectssent in the observation period

Event : transmission of a CMIS CREATE confirmation about an md subtreeobject




PE/DCL/DD/0125411--9001--125


ll10004 Number of CMIS SET requests received for the md subtree

Name Q3 : ommdSetRequest


Function : number of CMIS SET requests about md subtree objects received inthe observation period

Event : receipt of a CMIS SET request about an md subtree object



ll10005 Number of CMIS SET confirmations sent for the md subtree

Name Q3 : ommdSetConf


Function : number of CMIS SET confirmations about md subtree objects sent inthe observation period

Event : transmission of aCMISSET confirmation about anmd subtree object



ll10006 Number of CMIS DELETE requests received for the md subtree

Name Q3 : ommdDelRequest


Function : number of CMIS DELETE requests about md subtree objectsreceived in the observation period

Event : receipt of a CMIS DELETE request about an md subtree object





ll10007 Number of CMIS DELETE confirmations sent for the md

subtree

Name Q3 : ommdDelConf


Function : number of CMIS DELETE confirmations about md subtree objectssent in the observation period

Event : transmission of a CMIS DELETE confirmation about an md subtreeobject



ll10008 Number of CMIS ACTION requests received for the md subtree

Name Q3 : ommdActRequest


Function : number of CMIS ACTION requests about md subtree objectsreceived in the observation period

Event : receipt of a CMIS ACTION request about an md subtree object



ll10009 NumberofCMISACTIONconfirmations sent for themdsubtree

Name Q3 : ommdActConf


Function : number of CMIS ACTION confirmations about md subtree objectssent in the observation period

Event : transmission of a CMIS ACTION confirmation about an md subtreeobject




PE/DCL/DD/0125411--9001--125


ll10010 Number of CMIS CANCEL GET requests received for the md

subtree

Name Q3 : ommdCancelGetRequest


Function : number of CMIS CANCEL GET requests about md subtree objectsreceived in the observation period

Event : receipt of a CMIS CANCELGET request about anmd subtree object



ll10011 Number of CMIS CANCEL GET confirmations sent for the md

subtree

Name Q3 : ommdCancelGetConf


Function : number of CMIS CANCEL GET confirmations about md subtreeobjects sent in the observation period

Event : transmission of a CMIS CANCEL GET confirmation about an mdsubtree object



2.6.4.2 Request on network counters

ll10012 Number of CMISGET requests received for the network subtree

Name Q3 : omnetGetRequest


Function : number of CMIS GET requests about network subtree objectsreceived in the observation period

Event : receipt of a CMIS GET request about a network subtree object





ll10013 Number of CMIS GET confirmations sent for the network

subtree

Name Q3 : omnetGetConf


Function : number of CMIS GET confirmations about network subtree objectssent in the observation period

Event : transmission of a CMIS GET confirmation about a network subtreeobject



ll10014 Number of CMIS CREATE requests received for the network

subtree

Name Q3 : omnetCreRequest


Function : number of CMIS CREATE requests about network subtree objectsreceived in the observation period

Event : receipt of a CMIS CREATE request about a network subtree object



ll10015 Number of CMIS CREATE confirmations sent for the network

subtree

Name Q3 : omnetCreConf


Function : number of CMIS CREATE confirmations about network subtreeobjects sent in the observation period

Event : transmission of a CMIS CREATE confirmation about a networksubtree object




PE/DCL/DD/0125411--9001--125


l10016 Number of CMIS SET requests received for the network subtree

Name Q3 : omnetSetRequest


Function : number of CMIS SET requests about network subtree objectsreceived in the observation period

Event : receipt of a CMIS SET request about a network subtree object



ll10017 Number of CMIS SET confirmations sent for the network

subtree

Name Q3 : omnetSetConf


Function : number of CMIS SET confirmations about network subtree objectssent in the observation period

Event : transmission of a CMIS SET confirmation about a network subtreeobject



ll10018 Number of CMIS DELETE requests received for the network

subtree

Name Q3 : omnetDelRequest


Function : number of CMIS DELETE requests about network subtree objectsreceived in the observation period

Event : receipt of a CMIS DELETE request about a network subtree object





ll10019 Number of CMIS DELETE confirmations sent for the network

subtree

Name Q3 : omnetDelConf


Function : number of CMIS DELETE confirmations about network subtreeobjects sent in the observation period

Event : transmission of a CMIS DELETE confirmation about a networksubtree object



ll10020 Number of CMIS ACTION requests received for the network

subtree

Name Q3 : omnetActRequest


Function : number of CMIS ACTION requests about network subtree objectsreceived in the observation period

Event : receipt of a CMIS ACTION request about a network subtree object



ll10021 Number of CMIS ACTION confirmations sent for the network

subtree

Name Q3 : omnetActConf


Function : number of CMIS ACTION confirmations about network subtreeobjects sent in the observation period

Event : transmission of a CMIS ACTION confirmation about a networksubtree object




PE/DCL/DD/0125411--9001--125


ll10022 Number of CMIS CANCEL GET requests received for the

network subtree

Name Q3 : omnetCancelGetRequest


Function : number of CMIS CANCEL GET requests about network subtreeobjects received in the observation period

Event : receipt of a CMIS CANCEL GET request about a network subtreeobject



ll10023 Number of CMIS CANCEL GET confirmations sent for the

network subtree

Name Q3 : omnetCancelGetConf


Function : number of CMIS CANCEL GET confirmations about networksubtree objects sent in the observation period

Event : transmissionof aCMISCANCELGET confirmation about anetworksubtree object



2.6.4.3 Q3 notification counters

ll10024 Number of notifications received

Name Q3 : notifsReceived


Function : number of notifications received by the secured notification server ofthe OMC--R agent in the observation period

Event : receipt of a notification by the secured notification server





ll10025 Number of notifications sent for the first timeName Q3 : notifsSentOnce


Function : number of notifications transmitted a first time to themanagers in theobservation period

Event : first transmission of a notification to the managers



ll10026 Number of notifications sent a second timeName Q3 : notifsTransmitAgainOnce


Function : number of notifications transmitted a second time to the managers inthe observation period

Event : second transmission of a notification to the managers



ll10027 Number of notifications sent more than two timesName Q3 : notifsTransmitAgainTwiceAndMore


Function : number of notifications transmitted more than two times to themanagers in the observation period

Event : more than two transmissions of a notification to the managers



ll10028 Number of notifications that were not sent to all managers

Name Q3 : notifsReachMaxTransmit


Function : number of notifications that cannot be transmitted to all themanagersin the observation period

Event : stop transmitting a same notification to the managers




PE/DCL/DD/0125411--9001--125


2.6.4.4 FTAM counters

ll10029 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

ll10030 Number of successful FTAM GET transfers

Name Q3 : ftamFtiGetConf


Function : number of successful FTAMGET transfers in the observation period

Event : normal completion of an FTAM GET transfer



ll10031 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



ll10032 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





ll10033 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



ll10034 Number of successful FTAM DELETE requests

Name Q3 : ftamFtiDeleteConf


Function : number of successful FTAM DELETE requests in the observationperiod

Event : normal completion of an FTAM DELETE request



ll10035 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



ll10036 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




PE/DCL/DD/0125411--9001--125


ll10037 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



ll10038 Number of successful FTAM RENAME requests

Name Q3 : ftamFtiRenameConf


Function : number of successful FTAM RENAME requests in the observationperiod

Event : normal completion of an FTAM RENAME request





2.7 Raw permanent manager counters

2.7.1 SYBASE counters

These totalizer counters are provided by the SYBASE server. They are read by theOMC--Rmanager self-observation task at the end of each observation period (staticconfiguration data).

llTotal 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 diskread/write operations in the observation period


Source : SYBASE server, calculated by the OMC--R manager

llTotal number of SYBASE read operations

Name : omcSybaseTotalRead


Function : number of disk read operations performed by the SYBASE server inthe observation period



llTotal number of SYBASE write operations

Name : omcSybaseTotalWrite


Function : number of disk write operations performed by the SYBASE server inthe observation period




PE/DCL/DD/0125411--9001--125


llCPU 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



llI/O time used by the SYBASE server (1/10 s)

Name : omcSybaseIoBusy


Function : time spent by the SYBASE server in input/output operations duringthe observation period, expressed in 1/10th of a second



llSYBASE server idle time (s)

Name : omcSybaseIdle


Function : time of SYBASE server unoccupancy in the observation period,expressed in seconds



llNumber of packets received by the SYBASE server

Name : omcSybasePacketIn


Function : number of data packets received by the SYBASE server in theobservation period





llNumber of packets sent by the SYBASE server

Name : omcSybasePacketOut


Function : number of data packets sent by the SYBASE server in the observationperiod



llNumber of erroneous packets sent or received by the SYBASE server

Name : omcSybasePacketErr


Function : number of anomalies detected by the SYBASE server when sendingor receiving data packets in the observation period



llAverage filling rate of omc_db database

Name : omcDatabaseUsedomcDatabaseUsedCum Total filling rate. . . . . . . . .omcDatabaseUsedEch Number of samples. . . . . . . . . .

Object : active OMC--R manager server

Function : average rate (= total rate divided by the number of samples) of“cm_db” database used, calculated at the end of the observationperiod, expressed in %


Source : SUNOS system, calculated by the OMC--R manager

llAverage filling rate of segment 0 of trace_db database

Name : traceDatabaseSeg0UsedtraceDatabaseSeg0UsedCum Total filling rate. . . . .traceDatabaseSeg0UsedEch Number of samples. . . . . .



PE/DCL/DD/0125411--9001--125


Function : average rate (= total rate divided by the number of samples) of“trace_db” database segment 0 used, calculated at the end of theobservation period, expressed in %



llAverage filling rate of segment 1 of trace_db database

Name : traceDatabaseSeg1UsedtraceDatabaseSeg1UsedCum Total filling rate. . . . .traceDatabaseSeg1UsedEch Number of samples. . . . . .


Function : average rate (= total rate divided by the number of samples) of“trace_db” database segment 1 used, calculated at the end of theobservation period, expressed in %



llAverage filling rate of rst_trace_db database

Name : rsttraceDatabaseUsedrsttraceDatabaseUsedCum Total filling rate. . . . . . .rsttraceDatabaseUsedEch Number of samples. . . . . . . .


Function : average rate (= total rate divided by the number of samples) of“rsttrace_db” database used, calculated at the end of the observationperiod, expressed in %





2.7.2 X.25 counters

These totalizer counters are provided by the X.25--2 layer. They are read by theOMC--Rmanager self-observation task at the end of each observation period (staticconfiguration data).

llNumber of X25-2 packets received on port xName : omcX25PacketInPort0

omcX25PacketInPort1omcX25PacketInPort2omcX25PacketInPort3

Object : active server ( OMC--R manager and connected workstations)

Function : number of X.25--2 packets received on the X.25 port x in theobservation period


Source : X.25--2 layer, calculated by the OMC--R manager

lNumber of X25-2 packets sent on port xName : omcX25PacketOutPort0

omcX25PacketOutPort1omcX25PacketOutPort2omcX25PacketOutPort3

Object : active server (OMC--R manager and connected workstations)

Function : number of X.25--2 packets transmitted on the X.25 port x in theobservation period



lNumber of X25-2 packets received with CRC error on port xName : omcX25CrcErrorsPort0

omcX25CrcErrorsPort1omcX25CrcErrorsPort2omcX25CrcErrorsPort3


Function : number of frameswith CRC errors received on the X.25 port 0 or 1 inthe observation period

Event : checksum error detected on receipt of a frame on the X.25 port




PE/DCL/DD/0125411--9001--125


lNumber of abort requests received on port x

Name : omcX25AbortsPort0omcX25AbortsPort1omcX25AbortsPort2omcX25AbortsPort3


Function : number of aborted frames received on the X.25 port 0 or 1 in theobservation period

Event : receipt 8 consecutive times on the X.25 port of a frame that does notcomply with HDLC frame numbering



2.7.3 UNIX counters

These totalizer and value counters are provided by the SUNOS system. They areread by the OMC--R manager self-observation task at the end of each observationperiod (static configuration data).

llAverage load of CPU 0

Name : omcUnixCpu0UsedomcUnixCpu0UsedCum Total load of CPU 0. . . . . . . .omcUnixCpu0UsedEch Number of samples. . . . . . . . .





lAverage load of CPU 1

Name : omcUnixCpu1UsedomcUnixCpu1UsedCum Total load of CPU 1. . . . . . . .omcUnixCpu1UsedEch Number of samples. . . . . . . . .







llAverage filling rate of SWAP area

Name : omcUnixSwapomcUnixSwapCum Total filling rate of SWAP area. . . . . . . . . . . .omcUnixSwapEch Number of samples. . . . . . . . . . . . .


Function : average rate (= total rate divided by the number of samples) of swapmemory used in the server, calculated at the end of the observationperiod, expressed in %



llAverage filling rate of “/” partition

Name : omcUnixRootPartitionomcUnixRootPartitionCum Total partition filling rate. . . . . .omcUnixRootPartitionEch Number of samples. . . . . . .


Function : average rate (= total rate divided by the number of samples) of diskroot partition used, calculated at the end of the observation period,expressed in %



llAverage filling rate of “/tmp” partition

Name : omcUnixTmpPartitionomcUnixTmpPartitionCum Total partition filling rate. . . . . .omcUnixTmpPartitionEch Number of samples. . . . . . .


Function : average rate (= total rate divided by the number of samples) of disk“/tmp” partition used, calculated at the end of the observation period,expressed in %




PE/DCL/DD/0125411--9001--125


llAverage filling rate of “/OMC/obs” partition

Name : omcUnixObsPartitionomcUnixObsPartitionCum Total partition filling rate. . . . . . .omcUnixObsPartitionEch Number of samples. . . . . . .


Function : average rate (= total rate divided by the number of samples) of disk“/OMC/obs” partition used, calculated at the end of the observationperiod, expressed in %



llAverage filling rate of “/OMC/mail” partition

Name : omcUnixMailPartitionomcUnixMailPartitionCum Total partition filling rate. . . . . .omcUnixMailPartitionEch Number of samples. . . . . . .


Function : average rate (= total rate divided by the number of samples) of disk“/OMC/mail” partition used, calculated at the end of the observationperiod, expressed in %



llAverage filling rate of “/OMC/base” partition

Name : omcUnixBasePartitionomcUnixBasePartitionCum Total partition filling rate. . . . . .omcUnixBasePartitionEch Number of samples. . . . . . .


Function : average rate (= total rate divided by the number of samples) of disk“/OMC/base” partition used, calculated at the end of the observationperiod, expressed in %





llAverage filling rate of “/OMC/data” partition

Name : omcUnixDataPartitionomcUnixDataPartitionCum Total partition filling rate. . . . . .omcUnixDataPartitionEch Number of samples. . . . . . .


Function : average rate (= total rate divided by the number of samples) of disk“/OMC/data” partition used, calculated at the end of the observationperiod, expressed in %




PE/DCL/DD/0125411--9001--125


2.8 Raw permanent PCUSN counters

l15001/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 theBVCsof a SPMcard (including theBVCI0). The sizedoes not includethe 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

l15001/1 Number of bytes sent by all the BVCsassociated to this PCMlink

in an Element (SPM card)

Name Q3 : octetsUp

Value range : [0 to 4294967295]

Object : pcmLink

Function : Cumulative size (in bytes) of all theBSSGPPDUsent on all theBVCsof a SPM card (including the BVCI0). The size does not include theFR and NS header.

Event : Sending of an UL BSSGP PDU, in any BVC, to the SGSN






l15004/0 Number of UNIT--DATA PDUs received downlink by the BVCName 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




l15004/1 Number of UNIT--DATA PDUs sent uplink by the BVCName 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




l15005/0 Number of bytes received by the BVC in DL--UNIT--DATAPDUsName Q3 : octetsDataDn

Value range : [0 to 4294967295]

Object : bts

Function : Cumulative size (in bytes) of all the LLC PDU in the BSSGPDL--UNITDATA PDU received by the BVC (SGSN-->PCU).

Event : Receiving of a DL--UNITDATA PDU



Data flows : Refer to Chapter 1DFD “PCUSN: Flow Control”DFD “PCUSN: LLC Discarded”



PE/DCL/DD/0125411--9001--125


l15005/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 PDUsent by the BVC (PCU-->SGSN). The size does not include the FR,NS, and BSSGP header sizes.

Event : Sending of a UL--UNITDATA PDU




l15007/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 PDUsexceeds the bucket size

Event : This counter is incremented after the deletion of a PDU at the PCUlevel


Feature : GPRS

Note : V14 counter



l15007/1 Cumulative size and time of all theGPRSRLCdata blocks sent for

the first time on a pipe

Name Q3 : pcuDlThroughputCumpcuD1ThroughputNbs


Object : bts

Function : Counter performs two functions: cumulative size in bytes andcumulative time in multiples of 20 ms where the MS is in GPRS DLdata transfer. For cumulative time:T0 = Time of the first block sent in downlink for that mobileT1 = Time of the last FRESH or NACKED blockT2 = Time of the PDAN which acknowledge all the downlink blocks(or PCA in unacknowledged mode). Note that if the PDAN is neverreceived, T1 corresponds to the release of theDLTBF (in that case thePCU computes T1--T0).

Event : The event for the cumulative size function is a GPRSRLC data blockis sent for the first time (i.e. fresh block) on a pipeby aGPRSDLTBF.For the cumulative time function, T2 which increments the counterwith the result of T1--T0+1=T2--T0--(RTD + RRBP) +1

Unit : bytes


Feature : GPRS TBF establishment improvememt -- one phase access (15015)

Note : V15.0

Note : When only one block is sent (i.e. T1=T0) the counter is incrementedby 1.

Note : As an implementation choice, T1 can be used as the trigger instead ofT2.RTD = 9 blocks in synchronous TRAU and 5 blocks in asynchronousTRAU.RRBP is equal to 3 blocks.


PE/DCL/DD/0125411--9001--125


l15008/0 Maximum value of Downlink radio throughput calculated by the

flow control algorithm. (No longer relevant at the PCU level; it isalways set to 0.)

Name Q3 : MaxDlThroughput


Object : bts

Function : According toCREQ00613503, this counter is not relevant at the PCUlevel anymore; it is always set to 0.

Event : This counter is incremented after the emission of 3 Kbytes on theradio

Unit : 100 Bits per second


Feature : GPRS

Note : The lie factor is a feature that is used to exaggerate the leak rate whenthe bucket is near starvation, and to minimize the leak rate when thebucket is almost full. This counter calculates the true maximum valueof the downlink radio throughput without using the lie factor

l15010/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--BVCPDU sent by the BVC(PCU-->SGSN).

Event : Sending of a FLOW--CONTROL--BVC PDU






l15010/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




l15012/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




l15012/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 SGSNsending of a BSSGP RADIO STATUS to the SGSNreception of a BSSGP FLUSH--LL from the SGSN



PE/DCL/DD/0125411--9001--125



Data flows : Refer to Chapter 1DFD “PCUSN: LLC Discarded”


Note : The number of octlets is related to the LLC PDU received in the DLUNITDATA PDU.

l15014/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 allMS in the cell associated to the BVC (the BVC is indicated in themessage by the field BVCI (old)).

Event : Receiving of a FLUSH--LL PDU




l15023/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 onthis LAPD link

Event : This counter is incremented after the sending of a CS Pagingmessageto the BSC on the LAPD link


Feature : GPRS

Note : V14 counterReserved for future use

Note : This counter is in restriction in v15.0.



l15023/1 TotalNumber of PSPagingmessages sent by thePCU to theBTSon

this LAPD link

Name : PsPagingOnCCCH


Object : pcmCircuit

Function : Total Number of PS Paging messages sent by the PCU to the BTS onthis LAPD link

Event : This counter is incremented after the sending of a PS Pagingmessageto the BTS on the LAPD link


Feature : GPRS



l15024/0 Total Number of CS Pagingmessages sent by thePCU to theMSon

PACCH

Name Q3 : CsPagingOnPACCH


Object : pcmCircuit

Function : Total Number of CS Paging messages sent by the PCU to the MS onPACCH (on this SPM card)

Event : This counter is incremented after the sending of a CS Pagingmessageto the MS on PACCH


Feature : GPRS




PE/DCL/DD/0125411--9001--125


l15028/1 Cumulative number of uplink and/or downlink radio resource

assignments for a mobile whose multislot class requires 1 uplinktimeslot

Name Q3 : upMultiSlotRequest1

Value range : [0 to 4294967295]

Object : bts

Function : Cumulative number of uplink and/or downlink radio resourceassignments on PACCH for a mobile whose multislot class requires 1uplink timeslot

Event : This counter is incremented after the sending of:

Packet Timeslot ReconfigurePacket Downlink AssignmentPacket Uplink Assignment


Feature : GPRS

Note : V12.4d counter


assignments on PACCH for a mobile whose multislot classrequires up to 2 uplink timeslots


Value range : [0 to 4294967295]

Object : bts

Function : Cumulative number of uplink and/or downlink radio resourceassignments on PACCH for a mobile whose multislot class requiresup to 2 uplink timeslots




Feature : GPRS





assignments on PACCH for a mobile whose multislot classrequires up to 3 uplink timeslots


Value range : [0 to 4294967295]

Object : bts

Function : Cumulative number of uplink and/or downlink radio resourceassignments on PACCH for a mobile whose multislot class requiresup to 3 uplink timeslots




Feature : GPRS



assignments on PACCH for a mobile whose multislot classrequires up to 4 and more than 4 uplink timeslots


Value range : [0 to 4294967295]

Object : bts

Function : Cumulative number of uplink and/or downlink radio resourceassignments on PACCH for a mobile whose multislot class requiresup to 4 and more than 4 uplink timeslots




Feature : GPRS



PE/DCL/DD/0125411--9001--125


l15029/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 asatisfaction rate equal or better than 90 %. Refer to Section 1.6

Event : Modification of an allocation belonging to a gold user. Refer toSection 1.6


Feature : GPRS

Note : V14 counter


satisfaction rate equal or more than 50% and strictly less than90%

Name Q3 : upTbfGoldSatisfactBet5090pCent


Object : bts

Function : Cumulative number of gold users’ uplink allocations with asatisfaction rate equal or more than 50% and strictly less than 90%Refer to Section 1.6



Feature : GPRS

Note : V14 counter


satisfaction rate strictly less than 50%

Name Q3 : upTbfGoldSatisfactLess50pCent


Object : bts

Function : Cumulative number of gold users’ uplink allocations with asatisfaction rate strictly less than 50%. Refer to Section 1.6





Feature : GPRS

Note : V14 counter

l15029/4 Cumulativenumberof goldusers’ uplinkallocations rejecteddue

to the admittance control

Name Q3 : upTbfGoldRejectedForMinTput


Object : bts

Function : Cumulative number of gold users’ uplink allocations rejected due tothe admittance control

Event : This counter is incremented after the rejection of a new allocation to agold user due to admittance control


Feature : GPRS

Note : V14 counter


assignments for a mobile whose multislot class requires 1downlink timeslot

Name Q3 : dnMultiSlotRequest1

Value range : [0 to 4294967295]

Object : bts

Function : Cumulative number of uplink and/or downlink radio resourceassignments on PACCH for a mobile whose multislot class requires 1downlink timeslot

Event : This counter is incremented after the sending of:Packet Timeslot ReconfigurePacket Downlink AssignmentPacket Uplink Assignment


Feature : GPRS



PE/DCL/DD/0125411--9001--125



assignments on PACCH for a mobile whose multislot classrequires up to 2 downlink timeslots


Value range : [0 to 4294967295]

Object : bts

Function : Cumulative number of uplink and/or downlink radio resourceassignments on PACCH for a mobile whose multislot class requiresup to 2 downlink timeslots




Feature : GPRS



assignments on PACCH for a mobile whose multislot classrequires up to 3 downlink timeslots


Value range : [0 to 4294967295]

Object : bts

Function : Cumulative number of uplink and/or downlink radio resourceassignments on PACCH for a mobile whose multislot class requiresup to 3 downlink timeslots


Packet Timeslot ReconfigurePacket Downlink AssignmentPacket Uplink Asssignment


Feature : GPRS





assignments on PACCH for a mobile whose multislot classrequires up to 4 and more than 4 downlink timeslots


Value range : [0 to 4294967295]

Object : bts

Function : Cumulative number of uplink and/or downlink radio resourceassignments on PACCH for a mobile whose multislot class requiresup to 4 and more than 4 downlink timeslots


Packet Timeslot Reconfigure

Packet Downlink Assignment

Packet Uplink Assignment


Feature : GPRS


l15031/1 First Downlink Unit Data Frame

Name Q3 : FirstDlUnitDataFramednMultiSlotAllocations1

Value range : [0 to 4294967295]

Object : bts

Function : Cumulative number of pre--established downlink TBF withoutreception of DL--UNITDATA for this TBF.

Event : Relase of a pre--established downlink TBF without reception of aDL--UNITATA for this TBF.


Feature : GPRS

Data flows : Refer to Chapter 1:

DFD “PCUSN: DL TBF Establishment: MS in Standby State”



PE/DCL/DD/0125411--9001--125


l15031/2 Number of downlink allocation failures

Name Q3 : dlTBFAllocFailurednMultiSlotAllocations2

Value range : [0 to 4294967295]

Object : bts

Function : Cumulative number of downlink TBF establishment failures (halfand full duplex transfer), due to lack of radio resources.

Event : Reception of DL--UNITDATA(with a new TLLI), if the number ofMS in transfer is greater or equal to NB_MAX (SPM capacitylimitation set by Nortel Controlled Feature). The PCU tries toestablish the dowmlink TBF every 5 sec. up to 3 times, so with thesame DL--UNITDATA, the PCU may increment the counter up to 4times.


Feature : GPRS


Note : This counter is also incremented in case of failure ofDL--Preestablishment.

l15031/3 Number of downlink radio link failures

Name Q3 : dlTBFRadioFailurednMultiSlotAllocations3

Value range : [0 to 4294967295]

Object : bts

Function : Cumulative number of downlink TBF establishment failures (halfand full duplex), due to radio link failure

Event : This counter is incremented when an acknowledgement from theMSis not received for:

Packet Polling Request (after 5 transmissions from the PCU)First Packet Downlink Assignment (after 5 transmissions from thePCU)Packet Timeslot Reconfigure for the establishment of a downlinkTBF (after 5 transmissions from the PCU)

Class : GPRS




Feature : GPRSNote : V12.4d counter

l15031/4 Cumulative number of silver users’ uplink allocations with a

satisfaction rate equal or better than 90%Name Q3 : upTbfSilverSatisfactMore90pCent

dnMultiSlotAllocations4


Object : btsFunction : Cumulative number of silver users’ uplink allocations with a

satisfaction rate equal or better than 90%. Refer to Section 1.6


Source : recorded by the PCUFeature : GPRS

Note : V14 counter

l15032/0 Total number of full duplex temporary block flow (TBF)

establishedName Q3 : fullDuplexTbfEstablishmentValue range : [0 to 4294967295]

Object : btsFunction : Cumulative number of attempts to establish a full duplex transfer in

the cell (UL TBF establishment on DL TBF and vice versa).The fullduplex establishmentmay 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 PacketUplink Assignment or a Packet Downlink Assignment)

Source : recorded by the PCUFeature : GPRS (SV407 -- V12)Note : V12.4b and c counter

l15032/3 Number of second phase uplink allocation failuresName Q3 : ulsecondPhaseAllocFailureValue range : [0 to 4294967295]

Object : btsFunction : Cumulative number of rejected uplink establishment requests on

PACCH (half and full duplex), due to lack of radio resources


PE/DCL/DD/0125411--9001--125


Event : This counter is incremented after the reception of a Packet ResourceRequest or Packet Downlink Ack/Nack with Uplink Request, if thePCU cannot allocate enough resources to this mobile. Reception of afirst PacketResourceRequest (with anewTLLI), if thenumber ofMSin transfer is greater or equal to NB_MAX_MS (SPM capacitylimitation set by Nortel Controlled Feature).


Feature : GPRS


l15033/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 halfduplex or full duplex transfers). This counter counts the normal andabnormal releases due to loss of communication, OAM event, TSsharing event.

Event : Release of an UL TBF (related to half duplex or full duplex transferand due to normal or abnormal release). No reception of the first PRR.Resources requested for establishing the uplink TBF






l15033/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 halfduplex or full duplex transfers). This counter counts the normal andabnormal releases due to loss of communication, OAM event, TSsharing event.

Event : Release of aULTBF (related to half duplex or full duplex transfer anddue to normal or abnormal release). Resources requested forestablishing the downlinkTBF rejectedby allocator (because no radioresources available, Admission Control) Reception ofDL--UNITDATA (with a new TLLI), if the number of MS in teansferis greater or equal to NB_MAXMS (SPM capacity limitation set byNortel Controlled feature). The PCU tries to establish the downlinkTBF every 5 sec. up to 3 times, so with the same DL--UNITDATA thePCU may increment the counter up to 4 times.




l15034/0 Number of Packet Downlink Ack/Nack with Uplink Request

Name Q3 : PDANWithUlReqcumulativeTimeUpTbf

Value range : [0 to 4294967295]

Object : bts

Function : Cumulative number of Packet Downlink Ack/Nack messages, withthe Channel Request Description included

Event : This counter is incremented when a Packet Downlink Ack/Nackmessage is received, with the Channel Request Description included


Feature : GPRS

Data flows : Refer to Chapter 1DFD “PCUSN: Abnormal UL TBF Release (Full Duplex):UP_NASSIGNMAX”DFD “PCUSN: UL TBF Establishment during DL transfer”



PE/DCL/DD/0125411--9001--125



satisfaction rate equal ormore than 50%and strictly less than 90%

Name Q3 : upTbfSilverSatisfactBet5090pCentcumulativeTimeDnTbf


Object : bts

Function : Cumulative number of silver users uplink allocations with asatisfaction rate equal or more than 50 and strictly less than 90 %.Refer to section 1.6

Event : Pipe modification. Refer to section 1.6


Feature : GPRS

Note : V14 counter

l15036/0 Number of second phase uplink radio link failures

Name Q3 : ulsecondPhaseRadioFailureallocatedBlocksUpTbf

Value range : [0 to 4294967295]

Object : bts

Function : Cumulative number of abnormal releases during second phase uplinkestablishment (half and full duplex transfer)

Event : This counter is incremented in the following cases:

Non--reception of 5 consecutive non--acknowledgements of thefirst Packet Uplink Assignment

Reception of 20 consecutive TRAU frames with BFI set to 1,without receiving any valid RLC data block

Non--reception of 5 consecutive non--acknowledgments of thePacket Timeslot Reconfigure sent for the establishment of anuplink TBF on downlink TBF


Feature : GPRS




l15038/0 Total number of RLC data blocks sent by the PCU in astalledwindow condidtion

Name Q3 : localBusy

Value range : [0 to 4294967295]

Object : transceiver

Function : Cumulative number RLC data blocks sent by the PCU in a stalledwindow condition during a downlink transfer on this TDMA.

Event : This counter is incremented on the sending of an RLC data blockwhen the transmit window is stalled.




l15039/0 Cumulative value “C” received by the PCU in the message Packet

Downlink Ack/Nack

Name Q3 : cumulativeDnRxLevconfiguredTimeslots



Function : Cumulative value “C” received by the PCU in the message PacketDownlink Ack/Nack

Event : This counter is incremented after the reception of a Packet DownlinkAck/Nack by a TBF on this TDMA containing the Channel QualityReport set by the mobile


Feature : GPRS

Note : V14 counter

l15041/0 Number of user uplink data blocks

Name Q3 : upUserdatablockscumulativeUpActiveTimeslots

Value range : [0 to 4294967295]


Function : Cumulative number of blocks received for the first timeat thePCUSNlevel


PE/DCL/DD/0125411--9001--125


Event : This counter is incremented after anRLC data block is revieved in theReceive window, which has not been already received by the PCU.


Feature : GPRS


l15043/0 Number of retransmitted data blocks due to negative

acknowledgement

Name Q3 : RequestedRetransmittedDataBlocksDNcumulativeUpTbfPerTimeslots

Value range : [0 to 4294967295]


Function : Cumulative number of downlink data blocks retransmitted by thePCUSN due to negative acknowledgement from the mobile. Allblocks resent due to the Keep Alive feature and PreventiveRetransmission are not counted in this case.

Event : Retransmission of data blocks in NACKed state.


Feature : GPRS


l15045/0 Total number of LLCpackets 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 onthis TDMA.

Event : Reassembly of LLC frames






l15045/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 inRLC data blocks on this TDMA.

Event : Segmentation of LLC frames




l15046/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 thisTDMA

Event : This counter is incremented when a TBF is in progress and onreception of a TRAU frame (without BFI) containing and RLC/MACblock including:

a valid RLC data block in sequence received for the first timea valid RLC data block in sequence already receiveda valid RLC data block out of sequencean invalid RLC data block




PE/DCL/DD/0125411--9001--125


Data flows : Refer to Chapter 1DFD “PCUSN: UL TBF Establishment during DL transfer”DFD “PCUSN: Normal UL TBF Release”DFD “PCUSN:Abnormal ULTBFRelease: lossOfComNN0002”DFD “PCUSN: Abnormal UL TBF Release (FULL Duplex):lossOfComNN0002”DFD “PCUSN: Abnormal UL TBF Release: N3101”DFD “PCUSN: Abnormal UL TBF Release (FULL Duplex):N3101”DFD “PCUSN: Abnormal UL TBF Release: N3103”DFD “PCUSN: Abnormal UL TBF Release (FULL Duplex):N3103”DFD “PCUSN: DL TBF Establishment: MS in StandBy State”DFD “PCUSN: Abnormal DL TBF Release (FULL Duplex):lossOfComNN0002”DFD “PCUSN: Abnormal DL TBF Release (FULL Duplex):N3105”DFD “PCUSN: Abnormal DL TBF Release (FULL Duplex):DN_NASSIGNMAX”DFD “PCUSN: Abnormal DL TBF Release (FULL Duplex): NoFinal PDAN”DFD “PCUSN: Preemption”DFD “PCUSN: Cell Update: Packet Transfer”

Note : The term valid/invalid is linked to the protocol integrity. This meansthat the block has been correctly received on the radio by theBTS, andafter decoding by the PCU the block is declared valid/invalidaccording to the header contents.

l15046/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 thisTDMA.

Event : Sending of a DL RLC data block






l15047/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 uplinkby the PCU on this TDMA.

Event : This counter is incremented when a TBF is in progress and onreception of a TRAU frame (without BFI) containing:an RLC/MAC block including a valid RLC/MAC control blockanRLC/MACblock including an invalidRLC/MAC control blocka valid Stealing Frame (PCA 4--burst access mode)an invalid Stealing Frame (PCA 4--burst access mode)



Data flows : Refer to Chapter 1DFD “PCUSN: UL TBF Establishment”DFD “PCUSN: UL TBF Establishment during DL transfer”DFD “PCUSN: Normal UL TBF Release”DFD “PCUSN: Abnormal UL TBF Release:UP_NASSIGNMAX”DFD “PCUSN: Abnormal UL TBF Release (FULL Duplex):UP_NASSIGNMAX”DFD “PCUSN: Abnormal UL TBF Release: N3103”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 DLTBFRelease: lossOfComNN0002”DFD “PCUSN: Abnormal DL TBF Release (FULL Duplex):lossOfComNN0002”DFD “PCUSN: Abnormal DL TBF Release: N3105”DFD “PCUSN: Abnormal DL TBF Release (FULL Duplex):N3105”DFD “PCUSN: Abnormal DL TBF Release:DN_NASSIGNMAX”DFD “PCUSN: Cell Update: Packet Transfer”

Note : The term valid/invalid is linked to the protocol integrity. This meansthat the block has been correctly received on the radio by theBTS, andafter decoding by the PCU the block is declared valid/invalidaccording to the header contents


PE/DCL/DD/0125411--9001--125


l15047/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 onthis TDMA.

Event : Sending of a DL RLC control block




l15048/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 (BadFrame Indicator set by the BTS when no correct block has beendecoded on the radio) by the PCU on this TDMA

Event : This counter is incremented when a TBF is in progress and onreception of a TRAU frame with BFI




l15048/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 aprotocol error, received by the PCU on this TDMA



Event : This counter is triggered when a TBF is in progress and on receptionof a TRAU frame (without BFI) containing:an invalid Stealing Frame (PCA 4--burst access mode)anRLC/MACblock including an invalidRLC/MAC control blockan RLC/MAC block including an invalid RLC/MAC data block



Data flows : Refer to Chapter 1DFD “PCUSN: Abnormal UL TBF Release: N3101”DFD “PCUSN: Abnormal UL TBF Release (FULL Duplex):N3101”DFD “PCUSN: Abnormal UL TBF Release:UP_NASSIGNMAX”

Note : The term valid/invalid is linked to the protocol integrity. This meansthat the block has been correctly received on the radio by theBTS, andafter decoding by the PCU, the block is declared valid/invalidaccording to the header contents.

l15048/2 Total number of uplink data blocks receivedwith 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 sequenceby the PCU on this TDMA.

Event : Receipt of an RLC/MAC block received out of sequence




l15049/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 messagessent by the PCU on this TDMA.


PE/DCL/DD/0125411--9001--125


Event : Sending of a PACKET UPLINK ACK/NACK message




l15049/1 Total number of PACKET DOWNLINK ACK/NACK messages

Name Q3 : packetAckNackDn

Value range : [0 to 4294967295]


Function : Cumulative number of PACKET DOWNLINK ACK/NACKmessages received by the PCU on this TDMA.

Event : This counter is incremented after the reception of a PACKETDOWNLINK ACK/NACK message




l15050/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 thePCU on this TDMA and where it requested a retransmission.

Event : Sending of a Packet Uplink Ack/Nack resquesting for theretransmission of UL RCL data blocks




l15051/0 Cumulative uplink rxQual value

Name Q3 : cumulativeUpRxQual

Value range : [0 to 4294967295]


Function : Cumulative value “upRxQual” received by the PCU in each validRLC/MACblock 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 incrementedupon receipt of a stealing frame.



Note : V12.4b and c counterThe average is calculated by dividing this counter value by thenbSamples value.The counter is not incremented if the RLC/MAC block is receivedafter the release of the uplink TBF (specially up to RTD after anabnormal release).

l15051/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 bythe PCU in the message Packet Downlink Ack/Nack

Event : This counter is incremented after the reception of a Packet DownlinkAck/Nack by a TBF on this TDMA containing the Channel QualityReport set by the mobile


Feature : GPRS

Note : V14 counter

l15052/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 validRLC/MAC block on this TDMA

Event : This counter is incremented after the reception of a valid RLC/MACblock by a TBF on this TDMA (valid means without BFI)



PE/DCL/DD/0125411--9001--125


Feature : GPRS

Note : V14 counter

l15053/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 PCUon 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 counterThe counter is not incremented if the RLC/MAC block is receivedafter the release of the uplink TBF (specially up to RTD after anabnormal release)

l15053/1 Cumulative number of Packet Downlink Ack/Nack messages

received by the PCU on this TDMA, containing the ChannelQuality Report

Name Q3 : nbSamplesDnQuality


Object : tranceiver

Function : Cumulative number of Packet Downlink Ack/Nack messagesreceived by the PCU on this TDMA, containing the Channel QualityReport

Event : This counter is incremented after the reception of a Packet DownlinkAck/Nack by a TBF on this TDMA, containing the Channel QualityReport set by the mobile


Feature : GPRS

Note : V14 counter



l15054/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 onthis TDMA. This number includes all the transmission causes (roundtrip delay, preventive retransmission, keep alive, etc.)

Event : Retransmission of a DL RLC data block




l15055/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 halfduplex or full duplex transfer).

Event : Normal release of a UL TBF




l15055/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 halfduplex or full duplex transfer).

Event : Normal release of a DL TBF





PE/DCL/DD/0125411--9001--125


l15056/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 thePRR from the mobile on this TDMA.

Event : Non receipt of a PRR in the block allocated for this purpose in theimmediate assignment




l15056/1 Total number of PACKET RESOURCE REQUEST messages

received by the PCU from the MS in the second phase of the2--phase access uplink TBF establishment

Name Q3 : packetResourceRequest

Value range : [0 to 4294967295]

Object : ccch

Function : Cumulative number of PACKET RESOURCE REQUEST messagesreceived by the PCU in this cell for the second phase of an uplinkestablishment.

Event : Receipt of a PRR related to the second phase of an UL TBFestablishment






l15057/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) inuplink and V(A) in downlink. This means the number of abnormalreleases with a mobile in uplink TBF or downlink TBF because thereceived or transmitted window doesn’t progression.

Event :For uplink TBF, NN002 consecutive Packet Uplink Ack/Nack issent to the mobile without evolution of V(Q).For downlink TBF, NN002 consecutive Packet DownlinkAck/Nack is received from the mobile without evolution of V(A).



Note : V12.4b and c counterIn half duplex transfer (UL or DL): when this counter isincremented the counter lossOfComT3169 (UL) orlossOfComT3195 (DL) is not incremented.In full duplex transfer: if the UL TBF is released due to a causelossOfComNN002Max then the counters lossOfComNN002Maxand lossOfComT3195 (DL) are incremented, and the counterlossOfComT3169 is not incremented.In full duplex transfer: if the DL TBF is released due to a causelossOfComNN002Max then the counters lossOfComNN002Maxand lossOfComT3169 (UL) are incremented, and the counterlossOfComT3195 is not incremented.

l15057/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 fromthe mobile during the establishment procedure or packet transfer. Inthe case of full duplex transfer, this also counts the uplink TBFreleases consecutive to downlink TBF abnormal release.


PE/DCL/DD/0125411--9001--125


Event :No valid blocks received in UL from the mobile after N3101scheduled blocks (means with USF set in downlink)No Packet Control Ack received from the mobile after N3103Packet Uplink Ack/Nack sent with FAI=1No Packet Control Ack received from the mobile afterUP_NASSIGNMAX (value=5) Packet Uplink AssignmentAll the full duplex abnormal releases except loss of com. related tolossOfComNN002Max cause in uplink



Note : V12.4b and c counterThis counter is not incremented when a uplink TBF is released dueto a cause lossOfComNN002Max

l15057/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 fromthe mobile to USF and assignment messages

Event :No valid blocks received in UL from the mobile after N3101scheduled blocks (means with USF set in downlink)No Packet Control Ack received from the mobile afterUP_NASSIGNMAX (value=5) uplink assignment messages (i.e.Packet Uplink Assignment or Packet Timeslot Reconfigure orPacket Uplink Ack/Nack with assignment)






DFD “PCUSN: Abnormal UL TBF Release: N3101”

DFD “PCUSN: Abnormal UL TBF Release (FULL Duplex):N3101”

DFD “PCUSN: Abnormal UL TBF Release:UP_NASSIGNMAX”

DFD “PCUSN: Abnormal UL TBF Release (FULL Duplex):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 theMS to an uplink assignment message in PCU or FD



Value range : [0 to 4294967295]


Function : Number of downlink TBF abnormal releases due to non responsefrom the mobile during the establishment procedure or packettransfer. In the case of full duplex transfer, this also counts thedownlink TBF releases consecutive to uplink TBF abnormal release.

Event :

No Packet Downlink Ack/Nack received from the mobile afterN3105 downlink data blocks sent with FBI=1

No Packet Control Ack received from the mobile afterUP_NASSIGNMAX (value 5) Packet Downlink Assignment

No final Packet Downlink Ack/Nack received from the mobileafter NN002 data blocks sent with S/P=1 and FBI=1

All the full duplex abnormal releases except loss of com. related tolossOfComNN002Max cause in downlink




This counter is not incremented when a downlink TBF is releaseddue to a cause lossOfComNN002Max.


PE/DCL/DD/0125411--9001--125




Value range : [0 to 4294967295]


Function : Number of downlink TBF abnormal releases which occur during therelease of a downlink TBF (while the PCU is waiting for the lastacknowledgement coming from the mobile).

Event : No final Packet Downlink Ack/Nack received from the mobile afterNN002 data blocks sent with S/P=1 and FBI=1




This counter is a subset of lossOfComT3195

l15058/0 Total number of IMMEDIATE ASSIGNMENT messages

generated by the PCU to theMS in the first phase of the 2--phaseaccess uplink TBF establishment

Name Q3 : upTbfImmediateAssignment

Value range : [0 to 4294967295]

Object : ccch

Function : Cumulative number of IMMEDIATE ASSIGNMENT UPLINKmessages sent by the PCU to establish an UL TBF in this cell. In thecase of CCCH management at the BTS, this counter corresponds tothe cumulative values periodically received from the BTS in theCCCH information message.

Event : Sending of an IMMEDIATE ASSIGNMENT UPLINK message ifmanaged by the PCU or receipt of a CCCH information message ifmanaged by the CCCH at the BTS.






l15058/1 Total number of UL and DLTBF establishment rejected because

the number of MS in transfer is greater or equal roNB_MAX_MS

Name Q3 : upTbfImmAssigRejectNoPdch

Value range : [0 to 4294967295]

Object : ccch

Function : Cumulative number of UL and DL TBF establishment rejectedbecause the number of MS in transfer is greater than or equal to thevalue specified by SPM capacity limitation (set by Nortel ControlledFeature).

SPM capacity limitation is either defined by a max number of MSreached or by CPU overload.

Event : Reception of a first Packet ResourceRequest (with a newTLLI), if thenumber ofMS in transfer is greater than or equal to the value specifiedby SPM capacity limitation

Reception of DL--UNITDATA (with a new TLLI), if the number ofMS in transfer is greater than or equal to the value specified by SPMcapacity limitation.


Note : V14 counterThe PCUwill re--try to establish the downlinkTBF every5 secup to3times, sowith the sameDL--UNITDATA the PCUmay increment thecounter up to 4 times.

l15058/2 Total numberof IMMEDIATEASSIGNMENT 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 DOWNLINKmessages sent by the PCU to establish a DL TBF.

Event : Sending of an IMMEDIATEASSIGNMENT DOWNLINKmessage





PE/DCL/DD/0125411--9001--125


l15058/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 1.6

Event : Refer to Paragraph 1.6


Feature : GPRS


l15058/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


l15059/0 Total number of RACH (Channel Request) messages received in

the PCU in this cell

Name Q3 : channelRequestCcch

Value range : [0 to 4294967295]

Object : ccch

Function : Cumulative number of RACH (Channel Request) received by thePCU or BTS (in case of CCCH at BTS) in this cell.

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 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 isnot incremented by the BTS.

l15060/0 Number of times adownlink bandwidth, ofmore than 3 timeslots,

has been allocated for some mobiles in the cell

Name Q3 : dnPipeGreater33kbpsdeleteIndicationUp

Object : ccch




Feature : GPRS


l15060/1 Cumulative number of silver users’ uplink allocations rejected due

to the admittance control

Name Q3 : upTbfSilverRejectedForMinTputdeleteIndicationdeleteIndicationDndeleteIndicationUp


Object : CCCH

Function : Cumulative number of silver users’ uplink allocations rejected due tothe admittance control

Event : This counter is incremented after the rejection of a new allocation to asilver user due to admittance control


Feature : GPRS


l15061/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



PE/DCL/DD/0125411--9001--125




Feature : GPRS


l15061/1 Cumulative number of bronze users’ uplink allocations with a


Name Q3 : upTbfBronzeSatisfactMore90pCent


Object : CCCH




Feature : GPRS

Note : V14 counter

l15062/0 Number of times an uplink bandwidth, of more than 1 timeslot,


Name Q3 : upPipeGreater11kbpsdnTbfPacketAccessRejectNoPdch

Object : ccch




Feature : GPRS


l15062/1 Number of times a downlink bandwidth, of less than 1 timeslot,


Name Q3 : dnPipeLess11kbpsdnTbfPacketAccessRejectNoTs

Object : ccch






Feature : GPRS




Name Q3 : upTbfSilverSatisfactLess50pCentdnTbfPacketAccessRejectNoTbf


Object : CCCH




Feature : GPRS

Note : V14 counter



Name Q3 : upTbfBronzeSatisfactBet5090pCent


Object : CCCH




Feature : GPRS

Note : V14 counter



Name Q3 : upTbfBronzeSatisfactLess50pCent


Object : CCCH



PE/DCL/DD/0125411--9001--125




Feature : GPRS

Note : V14 counter

l15062/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 dueto the admittance control.

Event : This counter is incremented after the rejection of a new allocation to abronze user due to admisttance control.


Feature : GPRS

Note : V14 counter

l15063/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%). Theaverage CPU load is the percentage of time the application hassomething to since the last reset of this counter. Note that both thespooled and operational counters are reset when either the spooledcounters are retrieved or when the operational counters are reset bythe operator.


Feature : GPRS




l15063/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 iscomputed (percentage of time the application has something to doduring the “durationPeriod”). The maximum CPU load is themaximum value of these computed CPU loads since the last reset ofthis counter. Note that both the spooled and the operational countersare reset when either the spooled counters are retrieved or when theoperational counters are reset by the operator.


Feature : GPRS


l15066/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 thespecified collection interval. This average is calculated based on oneminute CPU utilization averages.

Event : Refer to “function”





PE/DCL/DD/0125411--9001--125


l15066/1 Minimum CPU load

Name Q3 : cpuUtilAvgMin



Function : This counter indicates the minimum processor utilization level over aspecified collection interval. The computing is based on one minuteCPU utilization averages.





l15066/2 Maximum CPU load

Name Q3 : cpuUtilAvgMax



Function : This counter indicates themaximumprocessor utilization level over aspecified collection interval. This is based on one minute CPUutilization averages.





l15067/0 Fast RAM memory capacity

Name Q3 : memoryCapacityFastRam

Value range : [0 to 2147483647]


Function : This counter indicates the processor’smemory capacity (in kilobytes)for fast ram memory.







l15067/1 Normal RAM memory capacity

Name Q3 : memoryCapacityNormalRam

Value range : [0 to 2147483647]


Function : This counter indicates the processor’smemory capacity (in kilobytes)for normal ram memory.





l15067/2 Shared RAM memory capacity

Name Q3 : memoryCapacitySharedRam

Value range : [0 to 2147483647]


Function : This counter indicates the processor’smemory capacity (in kilobytes)for shared ram memory.






PE/DCL/DD/0125411--9001--125


l15068/0 Average, maximum, and minimum Fast RAM utilization

Name Q3 : memoryUsageAvgFastRammemoryUsageAvgMaxFastRammemoryUsageAvgMinFastRam

Value range : [0 to 2147483647]


Function : This counter indicates the processor’s memory utilization (inkilobytes) for fast ram memory in the specified collection interval.This is calculated using 15 second samples.





l15068/1 Average, maximum, and minimum Normal RAM utilization

Name Q3 : memoryUsageAvgNormalRammemoryUsageAvgMaxNormalRammemoryUsageAvgMinNormalRam

Value range : [0 to 2147483647]


Function : This counter indicates the processor’s memory utilization (inkilobytes) for normal rammemory in the specified collection interval.This is calculated using 15 second samples.







l15068/2 Average, maximum, and minimum Shared RAM utilization

Name Q3 : memoryUsageAvgSharedRammemoryUsageAvgMaxSharedRammemoryUsageAvgMinSharedRam

Value range : [0 to 2147483647]


Function : This counter indicates the processor’s memory utilization (inkilobytes) for shared rammemory in the specified collection interval.This is calculated using 15 second samples.





l15069/0 Memory capacity of the processor card’s shared message blocks

Name Q3 : sharedMsgBlockCapacity

Value range : [0 to 2147483647]


Function : This counter indicates the processor’s shared message blockmemorycapacity (in kilobytes).





l15069/1 Average, maximum, and minimum utilization of the processor

card’s shared message blocks

Name Q3 : sharedMsgBlockUsageAvgsharedMsgBlockUsageAvgMaxsharedMsgBlockUsageAvgMin

Value range : [0 to 2147483647]


Function : This counter indicates the processor’s shared message blockmemoryutilization (in kilobytes) over a specified collection interval. This iscalculated using 15 second samples.


PE/DCL/DD/0125411--9001--125






l15069/2 Memory capacity of the processor card’s local message blocks

Name Q3 : localMsgBlockCapacity

Value range : [0 to 2147483647]


Function : This counter indicates the processor’s local message block memorycapacity (in kilobytes). These message blocks are used for localmessaging on the card.





l15069/3 Average, maximum, and minimum utilization of the processor

card’s local message blocks

Name Q3 : localMsgBlockUsageAvglocalMsgBlockUsageMaxlocalMsgBlockUsageMin

Value range : [0 to 2147483647]


Function : This counter indicates the processor’s memory utilization (inkilobytes) of message blocks used for local messaging on the card,calculated over a specified collection interval. This is calculatedusing15 second samples.







l15070/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 lastcollection interval.





l15070/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 bythe Framer in the last collection interval. This value could be zero ifthe application sends the frames directly to the link.





l15071/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 linkinterface by the Framer in the last collection interval.






PE/DCL/DD/0125411--9001--125


l15071/1 Number of frames transmitted to the link interface by the

FramerName Q3 : txFrames


Object : framer

Function : This counter provides the number of frames transmitted to the linkinterface by the Framer in the last collection interval. This value couldbe zero if the application sends the frames directly to the link.


Source : recorded by the PCUFeature : GPRS (SV407 -- V12)


l15072 Average total link utilization, based on the computation of the

total number of bytes received on the linkName Q3 : rxTotalLinkUtil


Object : framer

Function : This counter provides the average total link utilization computedbased on the total number of bytes received on the link in the lastcollection interval.





l15073/0 Cumulative number of BSSGP PAGING PS PDU received on the

SPM and related to this PCM linkName Q3 : psPaging


Object : pcmCircuit

Function : Cumulative number of BSSGP PAGING PS PDU received on theSPMand related to this PCM link (received either onBVCI0 or BVCIPTP). The PS PAGING received on BVCI0 and broadcast by theframe relay to the SPM cards are only counted on the master SPM.The PS PAGING received on BVCI PTP are counted on thecorresponding SPM.



Event : This counter is incremented upon reception of a BSSGP PS PAGINGPDU, by any BVC, from the SGSN.


Feature : GPRS

Note : V14 counter

l15073/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 theSPMand related to this PCM link (received either onBVCI0 or BVCIPTP). The CS PAGING received on BVCI0 and broadcast by theframe relay to the SPM cards are only counted on the master SPM.The CS PAGING received on BVCI PTP are counted on thecorresponding SPM.

Event : This counter is incremented upon reception of a BSSGP CS PAGINGPDU, by any BVC, from the SGSN.


Feature : GPRS

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 ofallocated Agprs timeslots in the cell.

Event : This counter is incremented after the sending of a PCU AGPRS TSSHARINGmessage by the PCUto theBSC (thismessage contains theidentification of the least and the most loaded cell, so for eachmessage sent by thePCU, the corresponding counter is incremented inthe least and the most loaded cell).


Note : V14 counter


PE/DCL/DD/0125411--9001--125


15075/1 Average, cumulative, sampling number of requestedmodifications of the number of allocated Agprs TS in thecorresponding cell.

Name Q3 : dyAgprsAvgNbTimeslotpcuDyAgprsNbTimeslotsCumpcuDyAgprsNbTimeslotsNbs


Object : bts

Function : Cumulative number of Agprs timeslots allocated in the cell by theBSC.This corresponds to the formula: sum (dyAgprsNbTs<i>). The valuedyAgprsNbTs<i> is the number ofAgprsTS allocated in the cell at the<i>th sample.

Note: When the cell is set as themost or least loaded cell several times ina row (to exchange jYeser TS following main TS), the loadcriterion is not computed each time. In that case the counter is notincremented.

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)

Note : Note on EGPRS: When the cell is set as the most or least loaded cellseveral times in a row, the load criterion is not computed each time. Inthat case the counter is not incremented.

15075/2 Minimum number of Agprs timeslots allocated to the cell bythe BSC

Name Q3 : dyAgprsMinNbTimeslots

Value range : [0 to 4294967295]

Object : bts

Function : Minimum number of Agprs timeslots allocated to the cell by the BSC




Event : Receipt of a PCU TDMA TS STATUS or PCU CELL STATUSmessage from the BSC indicating the number of Agprs timeslotsallocated to the cell.


Note : V14 counter

15075/3 Maximum number of Agprs timeslots allocated to the cell bythe BSC

Name Q3 : dyAgprsMaxNbTimeslots

Value range : [0 to 4294967295]

Object : bts

Function : Maximumnumber ofAgprs timeslots allocated to the cell by theBSC.


Event : Receipt of a TDMA TS STATUS REQ or PCU CELL STATUSmessage from the BSC indicating the number of Agprs timeslotsallocated to the cell.


Note : V14 counter

15076/0 Cumulative and sampling number of iteration samples forpcuDyAgprsLoadCriterionCum

Name Q3 : pcuDyAgprsLoadCriterionCumpcuDyAgprsLoadCriterionNbsackDnTbfEstablishment

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.



PE/DCL/DD/0125411--9001--125


Event : The PCUOAM receives 2 PCU counters from the PCUSNtransforming them to a CUNCell and aNBS Cell. These counters areexposed to the SDO interface.


Feature : GPRS (TF1262: Dynamic Agprs)

Note : When Ln = +? the counter is not incremented.

Note : V14 counterThe 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.


Event : Updated after every calculation of cell loading.

Source : recorded by the PCUCn= AgprsFilterCoefficient * C + (1-- AgprsFilterCoefficient) * Cn--1C= ∑PeakThroughputi * QoSi

i= allmobilesinthecell

Feature : GPRS (TF1262: Dynamic Agprs)

Note : When Ln = +? the counter is not incremented.

Note : V14 counterThe value 4294967295 means load = +∝The counter is updated at most every second if the dynamic Agprsis 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 defaultvalue 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).



l15077/0 Cumulative number of gold users’ downlink allocations with a


Name Q3 : dnTbfGoldSatisfactMore90pCent


Object : bts




Feature : GPRS

Note : V14 counter



Name Q3 : dnTbfGoldSatisfactBet5090pCent


Object : bts




Feature : GPRS

Note : V14 counter



Name Q3 : dnTbfGoldSatisfactLess50pCent


Object : bts




Feature : GPRS

Note : V14 counter


PE/DCL/DD/0125411--9001--125


l15077/3 Cumulative number of gold users’ downlink allocations rejected


Name Q3 : dnTbfGoldRejectedForMinTput


Object : bts

Function : Cumulative number of gold users’ downlink allocations rejected dueto the admittance control.

Event : This counter is incremented after the rejection of a new allocation to agold user due to admittance control.


Feature : GPRS

Note : V14 counter

Note : Reject counterswithminimum throughput for gold, silver, andbronzeby indicating that these counters are not incremented in case ofDL--Preestablishment.

l15078/0 Cumulative number of silver users’ downlink allocations with a


Name Q3 : dnTbfSilverSatisfactMore90pCent


Object : bts




Feature : GPRS

Note : V14 counter



Name Q3 : dnTbfSilverSatisfactBet5090pCent


Object : bts






Feature : GPRS

Note : V14 counter



Name Q3 : dnTbfSilverSatisfactLess50pCent


Object : bts




Feature : GPRS

Note : V14 counter

l15078/3 Cumulative number of silver users’ downlink allocations rejected


Name Q3 : dnTbfSilverRejectedForMinTput


Object : bts

Function : Cumulative number of silver users’ downlink allocations rejected dueto the admittance control.

Event : This counter is incremented after the rejection of a new allocation to asilver user due to admittance control.


Feature : GPRS

Note : V14 counter



PE/DCL/DD/0125411--9001--125


l15079/0 Cumulative number of bronze users’ downlink allocations with a


Name Q3 : dnTbfBronzeSatisfactMore90pCent


Object : bts




Feature : GPRS

Note : V14 counter



Name Q3 : dnTbfBronzeSatisfactBet5090pCent


Object : bts




Feature : GPRS

Note : V14 counter



Name Q3 : dnTbfBronzeSatisfactLess50pCent


Object : bts




Feature : GPRS

Note : V14 counter



l15079/3 Cumulative number of bronze users’ downlink allocations rejected


Name Q3 : dnTbfBronzeRejectedForMinTput


Object : bts

Function : Cumulative number of bronze users’ downlink allocations rejecteddue to the admittance control.

Event : This counter is incremented after the rejection of a new allocation to abronze user due to admittance control.


Feature : GPRS

Note : V14 counter


l15100/0 Spare counter, 0 by default

Name Q3 : pcuEdgeTdma15100s0


Object : TDMA

Function : NA

Event : NA


Feature : EDGE traffic management

Note : V15 counter

l15101/0 Cumulative number of EGPRS RLC data blocks received by

the PCU on a TDMA.

Name Q3 : pcuEdgeDataBlocksReceivedUp


Object : TDMA

Function : Cumulative number of EGPRSRLC data blocks received by the PCUon this TDMA.


PE/DCL/DD/0125411--9001--125


Event : Reception of an EGPRS UL TBF in progress of a TRAU framewithout 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 anEGPRSHeader Stealing Frame, this counter isnot incremented.

l15102/0 Average, cumulative, and sampling number of 8PSK_BEP

(assumed value) derived from the 8PSK_MEAN_BEP receivedfrom an MS in this TDMA in the EGPRS BEP Link QualityMeasurements (8PSK_MEAN_BEP).

Name Q3 : pcuEdgeDnAvg8PskMeanBeppcuEdgeDnCum8PskMeanBeppcuEdgeDnNbs8PskMeanBep


Object : TDMA

Function : This counter has 3 possible functions and can be used to determine theaverage or cumulative value, or the sampling number of the8PSK_BEP derived from the 8PSK_MEAN_BEP received from aMS in this TDMA in the EGPRS BEP Link Quality Measurements(8PSK_MEAN_BEP).

Event : Reception of an EGPRS Packet Downlink Ack/Nack by an EGPRSDL TBF on this TDMA, containing an 8PSK_MEAN_BEP value setin the EGPRS BEP link quality measurements.


Feature : GPRS TBF establishment improvement -- one phase access (15015)

Note : V15 counter

Note : 1 :MEAN_BEP is calculated and filtered in a linear scale butmappedto a logarithmic scale for reporting as defined in 3GPP 05.08, so forthe processing of the average value, the log10(actual BEP) is used(valuebetween0.60 and 3.60 as defined in 3GPP05.08 chapter 8.2.5).

Note : 2 : The MEAN_BEP is used to derive the actual BEP reported in the



counter. The correspondence is provided below.

MEAN_BEP 0 log10(mean(BEP)) > 0.6MEAN_BEP 1 0.6 > log10(mean(BEP)) > 0.64MEAN_BEP 2 0.64 > log10(mean(BEP)) > 0.68MEAN_BEP 3 0.68 > log10(mean(BEP)) > 0.72MEAN_BEP 4 0.72 > log10(mean(BEP)) > 0.76MEAN_BEP 5 0.76 > log10(mean(BEP)) > 0.80MEAN_BEP 6 0.80 > log10(mean(BEP)) > 0.84MEAN_BEP 7 0.84 > log10(mean(BEP)) > 0.88MEAN_BEP 8 0.88 > log10(mean(BEP)) > 0.92MEAN_BEP 9 0.92 > log10(mean(BEP)) > 0.96MEAN_BEP 10 0.96 > log10(mean(BEP)) > 1.00MEAN_BEP 11 1.00 > log10(mean(BEP)) > 1.04MEAN_BEP 12 1.04 > log10(mean(BEP)) > 1.08MEAN_BEP 13 1.08 > log10(mean(BEP)) > 1.12MEAN_BEP 14 1.12 > log10(mean(BEP)) > 1.16MEAN_BEP 15 1.16 > log10(mean(BEP)) > 1.20MEAN_BEP 16 1.20 > log10(mean(BEP)) > 1.36MEAN_BEP 17 1.36 > log10(mean(BEP)) > 1.52MEAN_BEP 18 1.52 > log10(mean(BEP)) > 1.68MEAN_BEP 19 1.68 > log10(mean(BEP)) > 1.84MEAN_BEP 20 1.84 > log10(mean(BEP)) > 2.00MEAN_BEP 21 2.00 > log10(mean(BEP)) > 2.16MEAN_BEP 22 2.16 > log10(mean(BEP)) > 2.32MEAN_BEP 23 2.32 > log10(mean(BEP)) > 2.48MEAN_BEP 24 2.48 > log10(mean(BEP)) > 2.64MEAN_BEP 25 2.64 > log10(mean(BEP)) > 2.80MEAN_BEP 26 2.80 > log10(mean(BEP)) > 2.96MEAN_BEP 27 2.96 > log10(mean(BEP)) > 3.12MEAN_BEP 28 3.12 > log10(mean(BEP)) > 3.28MEAN_BEP 29 3.28 > log10(mean(BEP)) > 3.44MEAN_BEP 30 3.44 > log10(mean(BEP)) > 3.60MEAN_BEP 31 3.60 > log10(mean(BEP))


PE/DCL/DD/0125411--9001--125


l15103/0 Average, cumulative, and sampling number of GMSK_BEP

(assumed value) derived from the GMSK_MEAN_BEP receivedfrom an MS in this TDMA in the EGPRS BEP Link QualityMeasurements (GMSK_MEAN_BEP).

Name Q3 : pcuEdgeDnAvgGmskMeanBeppcuEdgeDnCumGmskMeanBeppcuEdgeDnNbsGmskMeanBep


Object : TDMA

Function : This counter has 3 possible functions and can be used to determine theaverage or cumulative value, or the sampling number of theGMSK_BEP derived from the GMSK_MEAN_BEP received from aMS in this TDMA in the EGPRS BEP Link Quality Measurements(GMSK_MEAN_BEP).

Event : Reception of an EGPRS Packet Downlink Ack/Nack by an EGPRSDL TBF on this TDMA, containing aGSMK_MEAN_BEP value setin the EGPRS BEP link quality measurements.



Note : V15 counter

Note : 1 :MEAN_BEP is calculated and filtered in a linear scale butmappedto a logarithmic scale for reporting as defined in 3GPP 05.08, so forthe processing of the average value, the log10(actual BEP) is used(valuebetween0.60 and 3.60 as defined in 3GPP05.08 chapter 8.2.5).

Note : 2 : TheMEAN_BEP is used to derive the actual BEP reported in thecounter. The correspondence is provided below.

MEAN_BEP 0 log10(mean(BEP)) > 0.6MEAN_BEP 1 0.6 > log10(mean(BEP)) > 0.7MEAN_BEP 2 0.7 > log10(mean(BEP)) > 0.8MEAN_BEP 3 0.8 > log10(mean(BEP)) > 0.9MEAN_BEP 4 0.9 > log10(mean(BEP)) > 1.0MEAN_BEP 5 1.0 > log10(mean(BEP)) > 1.1MEAN_BEP 6 1.1 > log10(mean(BEP)) > 1.2MEAN_BEP 7 1.2 > log10(mean(BEP)) > 1.3MEAN_BEP 8 1.3 > log10(mean(BEP)) > 1.4MEAN_BEP 9 1.4 > log10(mean(BEP)) > 1.5



MEAN_BEP 10 1.5 >log10(mean(BEP)) > 1.6






















PE/DCL/DD/0125411--9001--125


MEAN_BEP 31 3.60 >log10(mean(BEP))

15104/0 Average, cumulative, and smpling number of BEP (assumed value)receivedby thePCUin eachEGPRSRLCdata blockon thisTDMA

Name Q3 : pcuEdgeUpAvgMeanBeppcuEdgeUpCumMeanBeppcuEdgeUpNbsMeanBep


Object : TDMA

Function : This counter has 3 possible functions and can be used to determine theaverage or cumulative value, or the sampling number of the assumedBEP received by the PCU in each EGPRS RLC data block on thisTDMA.

Event : Receipt of a TRAU frame without BFI by an EDGE TBF on thisTDMA. Upon receipt of an EGPRS RLC/MAC block by a EGPRSTBF on this TDMA, the Mean--BEP is used to derived the assumedBER. This assumed BEP is cumulated in thepcuEdgeUpCumMeanBep counter.


Feature : GPRS

Note : V15 counter

Note : All frames received in an EGPRS TBF are taken intoaccount except the one with BFI. In the special case wherethe MS started the UL TBF on another TDMA, the Mean--BEP for this TBF are ignored until the PACKET CONTROLACK is received on the initial TDMA.

Note : 1 : MEAN_BEP is calculated and filtered in a linearscale but mapped to a logarithmic scale for reporting asdefined in TRAU Frame I/F, so for the processing of theaverage value, the log10(actual BEP) is used (value between0.60 and 3.60)

Note : 2 : The MEAN_BEP is used to derive the actual BEPreported in the counter. The correspondence is provided below.

MEAN_BEP 0 log10(mean(BEP)) > 0.6MEAN_BEP 1 0.6 > log10(mean(BEP)) > 0.64



MEAN_BEP 2 0.64 > log10(mean(BEP)) > 0.68MEAN_BEP 3 0.68 > log10(mean(BEP)) > 0.72MEAN_BEP 4 0.72 > log10(mean(BEP)) > 0.76MEAN_BEP 5 0.76 > log10(mean(BEP)) > 0.80MEAN_BEP 6 0.80 > log10(mean(BEP)) > 0.84MEAN_BEP 7 0.84 > log10(mean(BEP)) > 0.88MEAN_BEP 8 0.88 > log10(mean(BEP)) > 0.92MEAN_BEP 9 0.92 > log10(mean(BEP)) > 0.96MEAN_BEP 10 0.96 > log10(mean(BEP)) > 1.00MEAN_BEP 11 1.00 > log10(mean(BEP)) > 1.04MEAN_BEP 12 1.04 > log10(mean(BEP)) > 1.08MEAN_BEP 13 1.08 > log10(mean(BEP)) > 1.12MEAN_BEP 14 1.12 > log10(mean(BEP)) > 1.16MEAN_BEP 15 1.16 > log10(mean(BEP)) > 1.20MEAN_BEP 16 1.20 > log10(mean(BEP)) > 1.36MEAN_BEP 17 1.36 > log10(mean(BEP)) > 1.52MEAN_BEP 18 1.52 > log10(mean(BEP)) > 1.68MEAN_BEP 19 1.68 > log10(mean(BEP)) > 1.84MEAN_BEP 20 1.84 > log10(mean(BEP)) > 2.00MEAN_BEP 21 2.00 > log10(mean(BEP)) > 2.16MEAN_BEP 22 2.16 > log10(mean(BEP)) > 2.32MEAN_BEP 23 2.32 > log10(mean(BEP)) > 2.48MEAN_BEP 24 2.48 > log10(mean(BEP)) > 2.64MEAN_BEP 25 2.64 > log10(mean(BEP)) > 2.80MEAN_BEP 26 2.80 > log10(mean(BEP)) > 2.96MEAN_BEP 27 2.96 > log10(mean(BEP)) > 3.12MEAN_BEP 28 3.12 > log10(mean(BEP)) > 3.28MEAN_BEP 29 3.28 > log10(mean(BEP)) > 3.44MEAN_BEP 30 3.44 > log10(mean(BEP)) > 3.60MEAN_BEP 31 3.60 > log10(mean(BEP))


Name Q3 : pcuEdgeTdma15105s0


Object : TDMA

Function : NA

Event : NA



Note : V15 counter


PE/DCL/DD/0125411--9001--125


l15106/0 Spare coumter, 0 by defaultName Q3 : pcuEdgeTdma15106s0


Object : TDMA

Function : NA

Event : NASource : recorded by the PCU


Note : V15 counter

l15107/0 Spare counter, 0 by defaultName Q3 : pcuEdgeTdma15107s0Value range : 0 to 4294967295

Object : TDMA

Function : NAEvent : NA


Feature : GPRS TBF establishment improvement -- one phase access (15015)Note : V15 counter

l15108/0 Spare counter, 0 by defaultName Q3 : pcuEdgeTdma15108s0Value range : 0 to 4294967295

Object : TDMA



Feature : GPRS TBF establishment improvement -- one phase access (15015)Note : V15 counter

l15109/0 Spare counter, 0 by defaultName Q3 : pcuEdgeTdma15109s0


Object : TDMAFunction : Spare counter, 0 by default.



Event : NA



Note : V15 counter

l15110/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 Mainchannels in the DL direction.

Event : This counter is incremented after a TRAUdata block or control blocksent on the Agprs Main Channel by a GPRS or EGPRS DL TBF.


Feature : Data backhaul evolution (19174)

Note : V15 counter

l15111/0 Average, cumulative, and sampling number of EGPRS TBF

downgraded in GPRS

Name Q3 : pcuEdgeDowngradedTbfAvgpcuEdgeDowngradedTbfpcuEdgeDowngradedTbfNbs


Object : bts

Function : This counter has 3 possible functions and can be used to determine theaverage or cumulative value, or the sampling number of EGPRSTBFdowngraded in GPRS.

Event : In the UL direction, when a Packet Resource Request including anEDGE request is received by PCU, or inDLdirection, whena firstDLunit data including an EDGE request for aMS with no on--going TBF(note that the counter ic incremented for each attempt to establish theDL TBF).In those cases, and if the PCUallocates theMSon aGPRSTDMA, thecounter is incremented.



PE/DCL/DD/0125411--9001--125



Note : V15 counter

l15112/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 apipe

Name Q3 : pcuEdgeUpAvgUsefulDataPerCellpcuEdgeUpCumUsefulDataPerCellpcuEdgeUpNbsUsefulDataPerCell


Object : bts

Function : This counter has 3 possible functions and can be used to determine theaverage, cumulative, or sampling size in bytes of all the RLC EDGEdata blocks received for the first time on a pipe.

Event : An RLC EDGE data block is received for the first time (i.e. freshblock) on a pipe by a EGPRS UL TBF.


Feature : EDGE traffic management (20231) -- one phase access (15015)

Note : V15 counter


EDGE data blocks sent for the first time (i.e. fresh block)

Name Q3 : pcuEdgeDnAvgUsefulDataPerCellpcuEdgeDnCumUsefulDataPerCellpcuEdgeDnNbsUsefulDataPerCell


Object : bts

Function : This counter has 3 possible functions and can be used to determine theaverage, cumulative, or sampling size in bytes of all the RLC EDGEdata blocks sent for the first time on a pipe.

Event : AnRLCEDGEdata block is sent for the first time (i.e. fresh block) ona pipe by a EGPRS DL TBF.



Note : V15 counter



415114/0 Spare counter, 0 by defaultName Q3 : pcuEdgeCell15114s0


Object : bts

Function : NA

Event : NASource : recorded by the PCU


Note : V15 counter

15115/0 Spare counter, 0 by defaultName Q3 : pcuEdgeCell15115s0Value range : 0 to 4294967295

Object : bts



Feature : EDGE traffic management (20231) -- one phase access (15015)Note : V15 counter

l15116/0 Spare counter, 0 by defaultName Q3 : pcuEdgeCell15116s0Value range : 0 to 4294967295

Object : bts



Feature : EDGE traffic management (20231) -- one phase access (15015)Note : V15 counter

l15117/0 Spare counter, 0 by defaultName Q3 : pcuEdgeCell15117s0


Object : btsFunction : Spare counter, 0 by default.


PE/DCL/DD/0125411--9001--125


Event : NA



Note : V15 counter

l15118/0 Cumulative, minimum, maximum, average, and sampling number

of Agprs Joker timeslots allocated to the cell by the BSCName Q3 : pcuDynAgprsJokerCumNbTimeslot

pcuDynAgprsJokerMinNbTimeslotpcuDynAgprsJokerMaxNbTimeslotpcuDynAgprsJokerAvgNbTimeslotpcuDynAgprsJokerNbsNbTimeslot


Object : bts

Function : This counter has 5 possible functions and can be used to determine thecumulative, minimum, maximum, average, and sampling number ofAgprs Joker timeslots allocated to the cell by the BSC.Tune the Agprs Joker according to the percent of EDGEmobile in thenetwork, radio conditions of the cell,and the target QoS offered by theoperator.

Event : Updated after every cell load calculation



Note : V15 counter

Note : When the cell is set as the most or less loaded cell several times in araw, the load criterion is not computed, thus the counter is notincremented.

l15119/0 Number of TRAU EDGE data blocks sent on the Agprs Joker

channels in the DL directionName Q3 : pcuAgprsJokerNbofBlocksDn


Object : bts

Function : Cumulative number of TRAU data blocks sent to th Agprs JokerChannel

Event : This counter is incremented after A TRAU data block is sent on theAgprs Joker Channel.





Note : V15 counter


Name Q3 : pcuEdgeCell15120s0


Object : bts

Function : NA

Event : NA



Note : V15 counter




Object : bts

Function : NA

Event : NA



Note : V15 counter

l15122/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 anEDGE request is received by PCU.In the DL direction, when a first DL unit data including an EDGErequest is received for a MS with no on--going TBF (note that thecounter is incremented for each attempt to establish the DL TBF).



PE/DCL/DD/0125411--9001--125



Note : V15 counter

l15123/0 Accumulated times in multiples of 20ms where the pipes for UL

EGPRS TBF are in “verbose” state

Name Q3 : pcuEdgeUpUsefulDataDurationPerCell


Object : bts

Function : Cumulative number of times inmultiples of 20mswhere the pipes forUL EGPRS TBF are in “verbose” state.

Event : This counter is incremented if EDGE is activated in the cell.



Note : V15 counter

l15124/0 Cumulated times in multiples of 20ms where the pipes for DL

EGPRS TBF are in “verbose” state.

Name Q3 : pcuEdgeDnUsefulDataDurationPerCell


Object : bts

Function : Accumulative times in multiples of 20ms where the pipes for DLEGPRS TBF are in “verbose” state.

Event : This counter is incremented if EDGE is activated in the cell.



Note : V15 counter




Object : bts

Function : NA

Event : NA





Note : V15 counter




Object : bts

Function : NA

Event : NA



Note : V15 counter

l15127/0 Total number of TRAU EDGE data blocks sent on the Agprs Main

channels in the UL direction

Name Q3 : pcuAgprsMainNbofBlocksUp


Object : bts

Function : Total number of TRAU EDGE data blocks sent on the Agprs Mainchannels in the UL direction.

Event : This counter is incremented after a TRAU data block is sent on theAgprs Joker Channel.



Note : V15 counter

l15128/0 Total number of TRAUEDGE 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 sent on the Agprs Jokerchannels in the UL direction.


PE/DCL/DD/0125411--9001--125


– Unexpected blocks are NOT counted.



Feature : Data backhaul evolution (19174).

Note : V15 counter

l15129/0 Number of periods of 20mswhenmissing jokers in theDLdirection

to reach the MCS targeted by the Link Adaptation

Name Q3 : pcuLackAbisJokerTSNbspcuLackAbisJokerTSAvgpcuLackAbisJokerTSCum


Object : TDMA

Function : Number of periods of 20ms when there are missing jokers in the DLdirection to reach the MCS targeted by the Link Adaptation.




Note : V15 counter

Note : Max number of Joker TS is known at the TDMA configuration in theTDMA--TS--STATUS message.

Note : ThecurrentNumber of JokerTS isknown at the TDMAconfigurationin the TDMA--TS--STATUSmessage. If the “Number of lack of Abisjoker TS” is positive, the counter pcuEdgeLackAbisJokerTSCum isincreased by “Number of lack of Abis joker TS”.

l15132/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 transmitted in MCS2 byPCU in the DL direction.



Event : An EDGE DL RLC Data Block sent by PCU in MCS2 (for the firsttime (i.e. fresh block) or restransmitted).



Note : V15 counter





Object : TDMA

Function : Number of 1/2 EDGERLCDataBlocks transmitted inMCS3 byPCUin the DL direction.

Event : An EDGE DL radio data block sent by PCU in MCS3 (for the firsttime (i.e. fresh block) or restransmitted).



Note : V15 counter





Object : TDMA





Note : V15 counter


PE/DCL/DD/0125411--9001--125






Object : TDMA





Note : V15 counter





Object : bts





Note : V15 counter


PCU in the DL direction.



Object : TDMA







Note : V15 counter





Object : TDMA





Note : V15 counter



Name Q3 : pcuEdgeMcs2RequestRetransDataBlockDn


Object : TDMA


Event : An EDGE DL RLC Data Block targeted by LA in MCS2 and sent inMCS2 (for the first time (i.e. fresh block) or retransmitted) is NACKby MS in PDAN.


Feature : EDGE link adaptation (20219)

Note : V15 couunter


PE/DCL/DD/0125411--9001--125






Object : TDMA





Note : V15 couunter


PCU in the DL direction.



Object : TDMA





Note : V15 couunter





Object : TDMA







Note : V15 couunter





Object : TDMA





Note : V15 couunter





Object : TDMA





Note : V15 couunter


PE/DCL/DD/0125411--9001--125






Object : TDMA





Note : V15 couunter

l15152/0 Number of 1/2EDGERLCData Blocks that are commanded by the

Link Adaptation in MCS2 and sent in MCS2 by PCU in the DLdirection

Name Q3 : pcuEdgeLADnTargetedTransmittedMcs2


Object : TDMA


Event : An EDGE DL RLC Data Block targeted by LA in MCS2 and sent inMCS2 (for the first time (i.e. fresh block) or retransmitted).



Note : V15 counter


Link Adaptation in MCS3 AND sent in MCS3 by PCU in the DLdirection



Object : TDMA







Note : V15 counter


Link Adaptation in MCS5 AND sent in MCS5 by PCU in the DLdirection.



Object : TDMA


Event : An EDGE DL RLC Data Block targeted by LA in MCS5 ad sent inMCS5 (for the first time (i.e. fresh block) or retransmitted).

Event : Note that pcuEdgeLAUpTargetedTransmittedMcs5 (15155, CUM,TDMA) is NOT incremented, because the MCS used by the mobiledoesn�t match the MCS commanded by the LA (associated to thedownlink block with USF1).



Note : V15 counter





Object : TDMA





PE/DCL/DD/0125411--9001--125



Note : V15 counter

l15157/0 Number of 1/2 EDGERLCData blocks that are commanded by the

Link Adaptation in MCS7 and sent in MCS7 by PCU in the DLdirection.



Object : TDMA


Event : An EDGE DL radio data block targeted by LA in MCS7 and sent inMCS7 (for the first time (i.e. fresh block) or retransmitted).



Note : V15 counter


Link Adaptation in MCS8 and sent in MCS8 by PCU in the DLdirection.



Object : TDMA





Note : V15 counter



l15159/0 Number of 1/2 EDGE radio data blocks that are commanded by the




Object : TDMA





Note : V15 counter

l15162/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

Function : Number of 1/2 EDGERLCData Blocks that are transmitted inMCS2by MS in the UL direction.

Event : Reception of an EDGE UL radio data block in MCS2 (with framevalidity bit set to 0 or 1).


Feature : 20219 (EDGE link adaptation)

Note : V15 counter

l1/215163/0 Number of 1/2 EDGE RLC Data Blocks that are transmitted in




Object : TDMA



PE/DCL/DD/0125411--9001--125





Note : V15 counter

l15165/0 Number of 1/2 EDGE RLC Data Blocks that are transmitted in




Object : TDMA





Note : V15 counter


MS in the UL direction.



Object : TDMA

Function : Number of 1/2 EDGE RLCData Blocks transmitted in MCS6 byMSin the UL direction.When PCU receives in the UL direction usingMCS6, one EDGE ULradio data block (with frame validity bits = 0 or 1), an“EGPRS--Header”, or a TRAUData framewith FrameValidity set to“0”, the counter is incremented by 2 units (1RLC data block per radiodata block).

Event : Reception of an EDGE UL radio data block in MCS6 (with framevalidity bit set to 0 or 1).Reception of a TRAU frame “EGPRS--Header“ MCS6.

The counter is NOT incremented when a BFI is received.





Note : V15 counter





Object : TDMA

Function : Number of 1/2 EDGE RLCData Blocks transmitted in MCS7 byMSin the UL direction.

Event : The counter is incremented by 4 units. The counter is not incrementedwhen a BFI is received.

Note : pcuEdgeUpTransmittedMcs7 (15167, CUM, TDMA) is incrementedby 4 (note also that the counter would have been incremented if onlythe header had been received by the PCU).



Note : V15 counter





Object : TDMA


Event : The counter is incremented by 4 units. The counter is not incrementedwhen a BFI is received.



Note : V15 counter


PE/DCL/DD/0125411--9001--125






Object : TDMA

Function : Number of 1/2 EDGE RLCData Blocks transmitted in MCS9 byMSin the UL direction.When PCU receives, in the UL direction usingMCS9, one EDGEULradio data block (with frame validity bits = 0 or 1), a “Semi--Frame”,an “EGPRS--Header”, or a TRAUData framewith FrameValidity setto “0”, the counter is incremented by 4 units (2 RLC data blocks perradio data block).

Event : Reception of an EDGE UL radio data block in MCS9 (with framevalidity 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.



Note : V15 counter

l15172/0 Number of 1/2 EDGERadio Data Blocks that were commanded by

the Link Adaptation inMCS2AND sent inMCS2 byMS in theULdirection AND badly received by BTS.

Name Q3 : pcuEdgeMcs2RequestRetransDataBlockUp


Object : TDMA

Function : Number of 1/2 EDGE Radio Data Blocks that were commanded bythe Link Adaptation in MCS2 AND sent in MCS2 by MS in the ULdirection AND badly received by BTS.

Event : Block badly received by PCU while targeted in MCS2 by linkadaptation.





Note : V15 counter

Note : In some cases the PCU recieves a semi--block with either FV bitsequal to 0 or both FV bits are equal to 0.

Note : 1. The counter (related to GMSK or 8PSK modulation) is NOTincremented when the LA decision has been downgraded in GMSKbecause the MS is not supporting 8PSK in the UL direction (caseGSMK Only in UL).2. The counter is NOT incremented when the LA decision has beendowngraded because of a lack of Joker TS on the backhaul.3. Thecounter isNOT incrementedwhen theMShas downgraded theMCS of the last block to best fit the data to be transmitted.4. WhenMCS ismodified by PCU in PUAN (or PUASS or PTR), thePCU assumes the MCS is taken into account after the same reactiontime as for the TBFallocations. Thecounter isNOT incrementeduntilthe modification is acknowledged by the mobile (by a PCA or by ULdata received on the new allocated timeslots). Thismechanism allowsavoiding changing the MCS on the very first UL samples that are notfiltered yet.5. The counter is NOT incremented until a valid measure is receivedfrom the BTS.6. In the special case of E--GPRS Header with cause ”BackhaulLimitation”, the counter is NOT incremented.7.In the special case of ”Semi--blocks” with cause ”No block lost” orthe two Frame Validity bits are equal to 1, the counter is NOTincremented.





Object : TDMA



Source : 11recorded by the PCU


PE/DCL/DD/0125411--9001--125



Note : V15 counter

Note : In some cases the PCU recieves a semi--block with either FV bitsequal to 0 or both FV bits are equal to 0.

Note : 1. The counter (related to GMSK or 8PSK modulation) is NOTincremented when the LA decision has been downgraded in GMSKbecause the MS is not supporting 8PSK in the UL direction (caseGSMK Only in UL).2. The counter is NOT incremented when the LA decision has beendowngraded because of a lack of Joker TS on the backhaul.3. Thecounter isNOT incrementedwhen theMShas downgraded theMCS of the last block to best fit the data to be transmitted.4. WhenMCS ismodified by PCU in PUAN (or PUASS or PTR), thePCU assumes the MCS is taken into account after the same reactiontime as for the TBFallocations. Thecounter isNOT incrementeduntilthe modification is acknowledged by the mobile (by a PCA or by ULdata received on the new allocated timeslots). Thismechanism allowsavoiding changing the MCS on the very first UL samples that are notfiltered yet.5. The counter is NOT incremented until a valid measure is receivedfrom the BTS.





Object : TDMA







Note : V15 counter

Note : In some cases the PCU recieves a semi--block with either FV bitsequal to 0 or both FV bits equal to 0.






Object : TDMA





PE/DCL/DD/0125411--9001--125



Note : V15 counter







Object : TDMA







Note : V15 counter







Object : TDMA





PE/DCL/DD/0125411--9001--125



Note : V15 counter









Object : TDMA

Function : Number of 1/2 EDGE Radio Data Blocks that were commanded bythe Link Adaptation in MCS9 AND sent in MCS9 by MS in the ULdirection AND badly received by BTS.When an USF is scheduled for a MS in the DL direction, the PCUinternally associates that blockwith theMCS commandedby theLinkAdaptation in the UL direction. When a Block is badly received byPCU (E--GPRS Header with cause ”Bad CRC on the radio” or aSemi--frame or a TRAUData frame with Frame Validity set to ’0’ onboth BSN), and if this Radio Data Block was targeted in MCS9, thecounter is incremented by 2 units.When a Block is partially received (”Semi--frame with cause 1st or2nd block lost or a TRAUData framewith one of the 2 FrameValidityset to ’0’), and if this Radio Data Block was targeted in MCS9, thecounter is incremented by 1 unit.




Note : V15 counter


l15182/0 Number of 1/2 EDGE Radio Data Blocks that are commanded by

the LinkAdaptation inMCS2AND sent inMCS2 byMS in theULdirection

Name Q3 : pcuEdgeLAUpTargetedTransmittedMcs2


Object : TDMA



PE/DCL/DD/0125411--9001--125


Event : Transmission by the MS of a data block in MCS2 when MCS2 is thecoding scheme commanded by the LA.



Note : V15 counter





Object : TDMA





Note : V15 counter





Object : TDMA


Event : Transmission by the MS of a data block in MCS5 when MCS5 is thecoding scheme commanded by the LA.Note that pcuEdgeLAUpTargetedTransmittedMcs5 (15155, CUM,TDMA) is NOT incremented, because the MCS used by the mobiledoesn�t match the MCS commanded by the LA (associated to thedownlink block with USF1).





Note : V15 counter





Object : TDMA





Note : V15 counter





Object : TDMA





Note : V15 counter


PE/DCL/DD/0125411--9001--125




Name Q3 : pcuEdgeLAUpTargetedTransmittedMcs8Value range : 0 to 4294967295

Object : TDMA



Source : recorded by the PCUFeature : EDGE link adaptation (20219)

Note : V15 counter





Object : TDMA




Feature : EDGE link adaptation (20219)Note : V15 counter

l15190/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 thePCU level.This counter is only incremented when the PCU receives a channelrequest one phase.



Event : Receipt of a Channel Request message, by PCU.



Note : V15 counter

Note : This counter has a one phase access feature (in case of CCCH atBTS).

l15191/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” messagessent by the PCU to establish a one phase access UL TBF in this cell.

Event : Sending of an Immediate Assignment Uplink message for theestablishment of a one phase access UL TBF, by the PCU.



Note : V15 counter

l15192/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 procedurein 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 framewith BFI or RLC datablock without TLLI).Non reception of a PCA after 5 repetitions of the Packet UplinkAck/Nack containing the TLLI.



Note : V15 counter


PE/DCL/DD/0125411--9001--125



GPRS data blocks received for the first time on a pipe (i.e. freshblock)

Name Q3 : pcuUpThroughputAvgpcuUpThroughputCumpcuUpThroughputNbs

Value range : 0..4294967295

Object : bts

Function : This counter has 3 possible functions anc can be used to determine theaverage, cumulative, and sampling size in bytes of all the RLCGPRSdata blocks received for the first time on a pipe.

The pcuUpThroughputAvg represents the average throughput atRLC level and cell level for every GPRS transfer.pcuUpThroughputAvg = ratio between pcuUpThroughputCum andpcuUpThroughputNbspcuUpThroughputCum = Cumulated size in bytes of all the GPRSdata blocks received for the first time (i.e. fresh block) on a pipe.pcuUpThroughputNbs = Cumulated time in multiples of 20 mswhere the MS is in GPRS UL data transfer.pcuUpThroughputNbs = Cumulated time in multiples of 20 mswhere the MS is in GPRS UL data transfer.

T0 = Time of the first block sent in downlink with the USF for thatmobileT1 = Time of the last block sent in downlink with the USF for thatmobile (related to T2 here after)T2 = Time of the reception of the last block with CV=0 (when all theblock have been correctly received). The counter is equal toT1--T0+1=T2--T0--RTD

Event : T2 which increments the counter with the result ofT1--T0+1=T2--T0--RTD



Note : V 15 counter

Note : RTD = 9 blocks in synchronous TRAU and 5 blocks in asynchronousTRAU

Note : When only one block is received (i.e. T1=T0) the counter isincremented by 1.



l15194/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 reachedin uplink direction by a MS in the cell.

Event : Pipe closure for a GPRS TBF



Note : V 15 counter

l15195/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 thetransmission of a DL--UNITDATA received from the SGSN.

Event : DL TBF pre--established and used for the transmission of aDL--UNITDATA.



Note : V 15 counter

Release countersNortel Networks Confidential 3--1


APPENDIX A RELEASE COUNTERSTo get an up--to--date list of observation counter modifications from previous releases to thecurrent release, refer to the following document:PE/OMC/DD/000297 V16.03/EN ”SIE SDO : Observation Counter Identification Map”

This document shows the following counter modifications:

new counters

deleted counters

counters renamed

IndexNortel Networks Confidential i


AabisCongestionTimeCum, 2--443

abisCongestionTimeEch, 2--443

abisCongestionTimeMax, 2--443

abisCongestionTimeMoy, 2--443

abisInputIByte, 2--437

abisInputIFrame, 2--436

abisInputUiByte, 2--436

abisInputUiFrame, 2--435

abisLevel1ErrorsBadFrame, 2--35

abisLevel1ErrorsCrcError, 2--36

abisLevel1ErrorsLostAlign, 2--36

abisLevel2ErrorBadLg, 2--442

abisLevel2ErrorBadRxNr, 2--440

abisLevel2ErrorReqOutState, 2--440

abisLevel2ErrorRxDm0, 2--439

abisLevel2ErrorRxDm1, 2--437

abisLevel2ErrorRxFrmr, 2--441

abisLevel2ErrorRxNoImpl, 2--441

abisLevel2ErrorRxSabme, 2--439

abisLevel2ErrorRxSup1, 2--437

abisLevel2ErrorRxUa0, 2--438

abisLevel2ErrorRxUa1, 2--438

abisLevel2ErrorTxNDisc, 2--440

abisLevel2ErrorTxNSabme, 2--439

abisOutputIByte, 2--436

abisOutputIFrame, 2--435

abisOutputUiByte, 2--436

abisOutputUiFrame, 2--435

abisTrauFrameCorrected, 2--251

abisTrauFrameDlReceived, 2--251

abisTrauFrameMuted, 2--252

abisUnavailabilityTimeCum, 2--442

abisUnavailabilityTimeEch, 2--442

abisUnavailabilityTimeMax, 2--442

abisUnavailabilityTimeMoy, 2--442

ackDnTbfEstablishment, 2--577

aInputMessage, raw permanent, 2--46

aintOverloadRejectedOpIncomingExtHoReq, 2--177

Index Nortel Networks Confidentialii

PE/DCL/DD/0125411--9001--125


aintOverloadRejectedOpPageReq, 2--176

aintOverLoadRejectedOpPerformLocationReq, 2--178

aintOverloadRejectedOpVbsVgcsAssignment, 2--178

aintOverLoadRejectedOpVbsVgcsSetup, 2--177

alarmAmrHrToFrDownHoRequiredTch, 2--387

alarmAmrHrToFrUpHoRequiredTch, 2--386

allEstabIndicSignalling, 2--451

allocatedAbisJokerTS, 2--358

allocatedAbisJokerTSEdgeCum, 2--358

allocatedAbisJokerTSEdgeEch, 2--358

allocatedAbisJokerTSEdgeMax, 2--358

allocatedAbisJokerTSEdgeMoy, 2--358

allocatedAbisJokerTSEdgeTrZoneCum, 2--358

allocatedAbisJokerTSEdgeTrZoneEch, 2--358

allocatedAbisJokerTSEdgeTrZoneMax, 2--358

allocatedAbisJokerTSEdgeTrZoneMoy, 2--358

allocatedBlocksUpTbf, 2--544

allocatedCircuitTs, 2--324

allocatedCircuitTsCellCum, 2--329

allocatedCircuitTsCellEch, 2--329

allocatedCircuitTsCellMax, 2--329

allocatedCircuitTsCellMoy, 2--329

allocatedCircuitTsCum, 2--324, 2--331

allocatedCircuitTsEch, 2--324

allocatedCircuitTsMax, 2--324

allocatedCircuitTsMoy, 2--324

allocatedCircuitTsTrZoneCum, 2--324

allocatedCircuitTsTrZoneEch, 2--324

allocatedCircuitTsTrZoneMax, 2--324

allocatedCircuitTsTrZoneMoy, 2--324

allocatedEdgeTsMoy/Max/Cum/Ech, 2--357

allocatedEdgeTsTrZoneMoy/Max/Cum/Ech, 2--357

allocatedPacketsTsTrZoneCum, 2--325

allocatedPacketsTsTrZoneEch, 2--325

allocatedPacketsTsTrZoneMax, 2--325

allocatedPacketsTsTrZoneMoy, 2--325

allocatedPacketTs, 2--325, 2--327

allocatedPacketTsCellCum, 2--330

allocatedPacketTsCellEch, 2--330

allocatedPacketTsCellMax, 2--330

IndexNortel Networks Confidential iii


allocatedPacketTsCellMoy, 2--330

allocatedPacketTsCum, 2--325, 2--326, 2--327

allocatedPacketTsEch, 2--325, 2--326, 2--327

allocatedPacketTsMax, 2--325, 2--326, 2--327

allocatedPacketTsMoy, 2--325, 2--326, 2--327

allocatedPacketTsTrZoneCum, 2--326, 2--327

allocatedPacketTsTrZoneEch, 2--326, 2--327

allocatedPacketTsTrZoneMax, 2--326, 2--327

allocatedPacketTsTrZoneMoy, 2--326, 2--327

allocationFailureTchFrSeizureInclHo, 2--454

allSdcchAllocatedTimeMoy/Max/Cum/Ech, 2--22

allSdcchAllocatedTimeTrZoneMoy/Max/Cum/Ech, 2--22

allSdcchinseconds, 2--486

allSdcchinsecondsCum, 2--486

allSdcchinsecondsEch, 2--486

allSdcchinsecondsMax, 2--486

allSdcchinsecondsMoy, 2--486

allTchFrAllocatedTimeCellCum, 2--331

allTchFrAllocatedTimeCellEch, 2--331

allTchFrAllocatedTimeCellMax, 2--331

allTchFrAllocatedTimeCellMoy, 2--331

allTchFrAllocatedTimeCum, 2--21

allTchFrAllocatedTimeEch, 2--21

allTchFrAllocatedTimeMax, 2--21

allTchFrAllocatedTimeMoy, 2--21

allTchFrAllocatedTimeTrZoneCum, 2--21

allTchFrAllocatedTimeTrZoneEch, 2--21

allTchFrAllocatedTimeTrZoneMax, 2--21

allTchFrAllocatedTimeTrZoneMoy, 2--21

allTchinsecondsCum, 2--485

allTchinsecondsEch, 2--485

allTchinsecondsMax, 2--485

allTchinsecondsMoy, 2--485

aMessageErroneousRate, 2--474

aMessageErrors, 2--48

amrDownlinkNoDataFrames, 2--409

amrFrBadSpeechFramesCodec102, 2--405

amrFrBadSpeechFramesCodec102TrZone, 2--405



Index Nortel Networks Confidentialiv

PE/DCL/DD/0125411--9001--125






amrFrDownlinkCodec102, 2--402

amrFrDownlinkCodec102TrZone, 2--402







amrFrHoExecutionIntraCellTch, 2--390

amrFrHoRequestIntraCellTch, 2--389

amrFrHoRequestOutgoingTch, 2--388

amrFrHoSuccessIntraCellTch, 2--391

amrFrHoSuccessOutgoingTch, 2--292

amrFrTchAllocated, 2--369

amrFrTchAllocatedTrZone, 2--369

amrFrTchAssignFailure, 2--372

amrFrTchConnectionDurationCum, 2--370

amrFrTchConnectionDurationEch, 2--370

amrFrTchConnectionDurationMax, 2--370

amrFrTchConnectionDurationMoy, 2--370

amrFrTchConnectionDurationTrZoneCum, 2--370

amrFrTchConnectionDurationTrZoneEch, 2--370

amrFrTchConnectionDurationTrZoneMax, 2--370

amrFrTchConnectionDurationTrZoneMoy, 2--370

amrFrTchStdAveragedUsed, 2--370

amrFrTchStdAveragedUsedCum, 2--370

amrFrTchStdAveragedUsedEch, 2--370

amrFrTchStdAveragedUsedMax, 2--370

amrFrTchStdAveragedUsedMoy, 2--370

amrFrTchStdAveragedUsedTrZoneCum, 2--370

amrFrTchStdAveragedUsedTrZoneEch, 2--370

amrFrTchStdAveragedUsedTrZoneMax, 2--370

amrFrTchStdAveragedUsedTrZoneMoy, 2--370

amrFrTchSuccessfullyAssigned, 2--371

amrFrToHrHoExecutionIntraCellTch, 2--390

amrFrToHrHoRequestIntraCellTch, 2--389

IndexNortel Networks Confidential v


amrFrToHrHoSuccessIntraCellTch, 2--391

amrFrUplinkCodec102, 2--399

amrFrUplinkCodec102TrZone, 2--399







amrFrValidSpeechFramesCodec102, 2--406

amrFrValidSpeechFramesCodec102TrZone, 2--406







amrHrBadSpeechFramesCodec475, 2--406

amrHrBadSpeechFramesCodec475TrZone, 2--406





amrHrDownlinkCodec475, 2--402

amrHrDownlinkCodec475TrZone, 2--402





amrHrHoRequestOutgoingTch, 2--389

amrHrHoSuccessOutgoingTch, 2--293

amrHrTchAssignFailure, 2--372

amrHrTchConnectionDurationCum, 2--371

amrHrTchConnectionDurationEch, 2--371

amrHrTchConnectionDurationMax, 2--371

amrHrTchConnectionDurationMoy, 2--371

amrHrTchConnectionDurationTrZoneCum, 2--371

amrHrTchConnectionDurationTrZoneEch, 2--371

amrHrTchConnectionDurationTrZoneMax, 2--371

amrHrTchConnectionDurationTrZoneMoy, 2--371

Index Nortel Networks Confidentialvi

PE/DCL/DD/0125411--9001--125


amrHrTchSuccessfullyAssigned, 2--372

amrHrToFrHoExecutionIntraCellTch, 2--391

amrHrToFrHoRequestIntraCellTch, 2--390

amrHrToFrHoSuccessIntraCellTch, 2--392

amrHrUplinkCodec475, 2--399

amrHrUplinkCodec475TrZone, 2--399





amrHrValidSpeechFramesCodec475, 2--407

amrHrValidSpeechFramesCodec475TrZone, 2--407





amrQualityFrDownHoRequiredTch, 2--385

amrQualityFrUpHoRequiredTch, 2--385

amrQualityHrDownHoRequiredTch, 2--388

amrQualityHrUpHoRequiredTch, 2--387

amrReversalPhaseFailure, 2--412

amrUplinkNoDataFrames, 2--408

aNonTransparentDown, 2--174

aNonTransparentUp, 2--173

aOutputMessage, raw permanent, 2--47

asciCallInitiationVbs, 2--254

asciCallInitiationVgcs, 2--255

asciInbandNotification, 2--256

asciInbandPaging, 2--255

asciPreemptionPerformed, 2--256

asciTalkerHandoverVbs, 2--307

asciTalkerHandoverVgcs, 2--307

assignFailure, 2--20

assignRequestAintOthers, 2--352

assignRequestAintSdcchToTchChannel, 2--351

assignRequestOthers, 2--350

assignRequestSdcchToTchChannel, 2--349

assignToOtherBandOrZone, 2--306

aTransparentDown, 2--172

aTransparentUp, 2--171

IndexNortel Networks Confidential vii


attemptedTchFrSeizureInclHo, 2--454

attemptedTchFrSeizureNotInclHo, 2--454

attemptedTchFrSeizures, 2--19

attemptedTchFrSeizures8W, 2--359

attemptedTchFrSeizuresMsDualb, 2--249

averageDLRxLev, 2--481

averageDLRxQual, 2--482

averageULRxLev, 2--482

averageULRxQual, 2--482

BbscAllocationFailureTchFrSeizureInclHo, 2--484

bscAttemptedTchFrSeizureInclHo, 2--484

bscAttemptedTchFrSeizureNotInclHo, 2--484

bscClearRequestTraffic, 2--484

bscOtherThanPaging, 2--477

bscPagingResponse, synthetic permanent, 2--477

bscSdcchAllocated, 2--480

bscSdcchAveragedUsedMax, synthetic permanent bsc, 2--475

bscSdcchAveragedUsedMoy, synthetic permanent bsc, 2--475

bscTchFrAllocatedOverflowAllocation, 2--480

bscTchFrAllocatedPrimoAllocation, 2--480

bscTchFrAllocatedTchAllocation, 2--481

bscTchFrAveragedUsedOverflowAllocationMoy, 2--476

bscTchFrAveragedUsedTchAllocationMoy, 2--476

bsPowerDecControl, 2--318

bsPowerDecControlAmrFr, 2--376

bsPowerDecControlAmrHr, 2--381

bsPowerIncControl, 2--317

bsPowerIncControlAmrFr, 2--376

bsPowerIncControlAmrHr, 2--381

btsOverloadDuration, 2--248

burstToTransmit, 2--356

bvcFlowControlRequests, 2--530

CcallDropTrafficRatio, 2--488

capacityFrToHrHoRequiredTch, 2--386

Index Nortel Networks Confidentialviii

PE/DCL/DD/0125411--9001--125


capacityHoFiltered, 2--383

cardSynthLoadCpue0, 2--338

cardSynthLoadCpum, 2--338

cardSynthLoadSicd0, 2--338

cellSdcchResourceFailureRatio, 2--486

cellTchResourceFailureRatio, 2--487

cgOverloadRejectedOpChannelReqCg, 2--311

cgOverloadRejectedOpChannelReqCg1, 2--311

cgOverloadRejectedOpChannelReqCg2, 2--311

cgOverloadRejectedOpEstablishIndCg, 2--312

cgOverloadRejectedOpPageReqBtsCg, 2--313

cgOverloadRejectedOpPageReqCg, 2--310

cgOverloadRejectedOpHoReqcg, 2--313

chainStandbyResponse, 2--50

chainStandbyUpdate, 2--50

channelActivateSignallingFullRate, 2--225, 2--226

channelActivateSpeechAmrFr, 2--369

channelActivateSpeechAmrHr, 2--368

channelActivateSpeechEnhancedFullRate, 2--155

channelActivateSpeechFullRate, 2--154

channelActivateTchFrDataNT12000, 2--244



channelActivateTchFrDataNtHscsd, 2--246

channelActivateTchFrDataT1200, 2--233







channelActivateTchFrDataTHscsd, 2--246

channelActivateTchHrDataNT6000, 2--355

channelActivateTchHrDataT16, 2--238

channelActivateTchHrDataT2400, 2--241

ChannelActivateTchHrDataT4800, 2--242

channelActivateTchHrDataT600, 2--239, 2--240

channelActTchFrDataNT, 2--246

channelActTchFrDataT, 2--246

channelActTchHrDataNT, 2--248

IndexNortel Networks Confidential ix


channelActTchHrDataT, 2--247

channelAveragedIdlePerInterfBand0, 2--211





channelIdleLevelCum, 2--432

channelIdleLevelEch, 2--432

channelIdleLevelMax, 2--432

channelIdleLevelMoy, 2--432

channelRequest, 2--262

channelRequestCause000, 2--135








channelRequestCcch, 2--562

channelRequestExtended, 2--230

CIUplinkAmrFr, 2--377

CIUplinkAmrFrTrZone, 2--377

CIUplinkAmrHrTrZone, 2--381

CIUplinkFr, 2--373

CIUplinkFrTrZone, 2--373

clearRequestTraffic, 2--455

cmDatabaseUsed, 2--496

cmDatabaseUsedCum, 2--496

cmDatabaseUsedEch, 2--496

cmLogUsed, 2--497

cmLogUsedCum, 2--497

cmLogUsedEch, 2--497

connectionDurationSdcch, 2--182

connectionDurationSdcchCum, 2--182

connectionDurationSdcchEch, 2--182

connectionDurationSdcchMax, 2--182

connectionDurationSdcchTrZoneCum, 2--184

connectionDurationSdcchTrZoneEch, 2--184

connectionDurationSdcchTrZoneMax, 2--184

Index Nortel Networks Confidentialx

PE/DCL/DD/0125411--9001--125


connectionDurationSdcchTrZoneMoy, 2--184

connectionDurationTchTrZoneCum, 2--179

connectionDurationTchTrZoneEch, 2--179

connectionDurationTchTrZoneMax, 2--179

connectionDurationTchTrZoneMoy, 2--179

controlBlocksDn, 2--550

controlBlocksUp, 2--549

cpue0LoadRatio, 2--492

cpue1LoadRatio, 2--492

cpuPBlockUtilAvg, 2--566

cpuPBlockUtilMax, 2--567

cpuUtilAvg, 2--567

cpuUtilAvgMax, 2--568

cpuUtilAvgMin, 2--568

csPaging, 2--575

CsPagingOnCcch, 2--532

CsPagingOnPACCH, 2--533

configuredTimeslots, 2--545

cumulativeDnRxLev, 2--545

cumulativeDnRxQual, 2--553

cumulativeTimeDnTbf, 2--544

cumulativeTimeUpTbf, 2--543

cumulativeUpActiveTimeslots, 2--545

cumulativeUpRxLev, 2--553

cumulativeUpRxQual, 2--552

cumulativeUpTbfPerTimeslots, 2--546

DdataBlocksDn, 2--548

dataBlocksUp, 2--547

dataNtRateFbTcbConfNotAllowed, 2--134

dataNtRateFbTcbResLack, 2--134

dataNtRateFbTchConfNotAllowed, 2--257

dataNtRateFbTchResLack, 2--257

decAmrFrDownModif, 2--410

decAmrFrDownModifTrZone, 2--410

decAmrFrUpModif, 2--409

decAmrFrUpModifTrZone, 2--409

decAmrHrDownModif, 2--412

IndexNortel Networks Confidential xi


decAmrHrDownModifTrZone, 2--412

decAmrHrUpModif, 2--411

decAmrHrUpModifTrZone, 2--411

deleteIndication, 2--315, 2--563

deleteIndicationDn, 2--563

deleteIndicationUp, 2--563

directedRetryUnsuccessNoBts, 2--215

dlMutedAbisTrauFrameRate, 2--483

dnMultiSlotAllocations1, 2--539




dnMultiSlotRequest1, 2--537




dnPipeBetween11and22kbps, 2--562

dnPipebetween22and33kbps, 2--562

dnPipeGreater33kbps, 2--563

dnPipeLess11kbps, 2--564

dnTbfBronzeRejectedForMinTput, 2--583

dnTbfBronzeSatisfactBet5090pCent, 2--582

dnTbfBronzeSatisfactLess50pCent, 2--582

dnTbfBronzeSatisfactMore90pCent, 2--582

dnTbfGoldRejectedForMinTput, 2--580

dnTbfGoldSatisfactBet5090pCent, 2--579

dnTbfGoldSatisfactLess50pCent, 2--579

dnTbfGoldSatisfactMore90pCent, 2--579

dnTbfImmediateAssignment, 2--561

dnTbfPacketAccessRejectNoPdch, 2--564

dnTbfPacketAccessRejectNoTbf, 2--565

dnTbfPacketAccessRejectNoTs, 2--564

dnTbfReleases, 2--543

dnTbfSilverRejectedForMinTput, 2--581

dnTbfSilverSatisfactBet5090pCent, 2--580

dnTbfSilverSatisfactLess50pCent, 2--581

dnTbfSilverSatisfactMore90pCent, 2--580

downgradedL1mModeOnClassmark, 2--358

downlinkPowerCtrlMaxSdcchCum, 2--180

downlinkPowerCtrlMaxSdcchEch, 2--180

Index Nortel Networks Confidentialxii

PE/DCL/DD/0125411--9001--125


downlinkPowerCtrlMaxSdcchMax, 2--180

downlinkPowerCtrlMaxSdcchMoy, 2--180

downlinkPowerCtrlMaxTchAmrFrCum, 2--373

downlinkPowerCtrlMaxTchAmrFrEch, 2--373

downlinkPowerCtrlMaxTchAmrFrMax, 2--373

downlinkPowerCtrlMaxTchAmrFrMoy, 2--373

downlinkPowerCtrlMaxTchAmrHrCum, 2--378

downlinkPowerCtrlMaxTchAmrHrEch, 2--378

downlinkPowerCtrlMaxTchAmrHrMax, 2--378

downlinkPowerCtrlMaxTchAmrHrMoy, 2--378

downlinkPowerCtrlMaxTchCum, 2--156

downlinkPowerCtrlMaxTchEch, 2--156

downlinkPowerCtrlMaxTchMax, 2--156

downlinkPowerCtrlMaxTchMoy, 2--156

dyAgprsAvgLoadCriterionCum, 2--577

dyAgprsMaxLoadCriterion, 2--578

dyAgprsMaxNbTimeslots, 2--577

dyAgprsMinNbTimeslots, 2--576

dyAgprsNbModif, 2--575

Ee3OverloadRejectedOpChannelReq, 2--353

e3OverloadRejectedOpEstablishInd, 2--353

e3OverloadRejectedOpHoReq, 2--354

e3OverloadRejectedOpPagingReq, 2--353

e3OverloadRejectedOpPagingReqReject, 2--354

e3OverloadRejectedOpSmsCb, 2--355

e3PrDiskCnOmuLdRCum, 2--366

e3PrDiskCnOmuLdREch, 2--366

e3PrDiskCnOmuLdRMax, 2--366

e3PrDiskCnOmuLdRMoy, 2--366

e3PrDiskCnOmuLdWCum, 2--365

e3PrDiskCnOmuLdWEch, 2--365

e3PrDiskCnOmuLdWMax, 2--365

e3PrDiskCnOmuLdWMoy, 2--365

e3PrDiskCnOmuMdRCum, 2--367

e3PrDiskCnOmuMdREch, 2--367

e3PrDiskCnOmuMdRMax, 2--367

e3PrDiskCnOmuMdRMoy, 2--367

IndexNortel Networks Confidential xiii


e3PrDiskCnOmuMdWCum, 2--366

e3PrDiskCnOmuMdWEch, 2--366

e3PrDiskCnOmuMdWMax, 2--366

e3PrDiskCnOmuMdWMoy, 2--366

e3PrMemCnOmuSbcMemCum, 2--362

e3PrMemCnOmuSbcMemEch, 2--362

e3PrMemCnOmuSbcMemMax, 2--362

e3PrMemCnOmuSbcMemMoy, 2--362

e3PrMemCnOmuSbcSwapCum, 2--363

e3PrMemCnOmuSbcSwapEch, 2--363

e3PrMemCnOmuSbcSwapMax, 2--363

e3PrMemCnOmuSbcSwapMoy, 2--363

e3PrMemCnTmuPmcCum, 2--364

e3PrMemCnTmuPmcEch, 2--364

e3PrMemCnTmuPmcMax, 2--364

e3PrMemCnTmuPmcMoy, 2--364

e3PrMemCnTmuSbcCum, 2--364

e3PrMemCnTmuSbcEch, 2--364

e3PrMemCnTmuSbcMax, 2--364

e3PrMemCnTmuSbcMoy, 2--364

ecuActivation, 2--253

estabIndicSignalling, 2--263

estabIndicSignallingEmergency, 2--150

estabIndicSignallingEmergency8W, 2--427

estabIndicSignallingEmergency8w, 2--263

estabIndicSignallingImsiDetach, 2--149

estabIndicSignallingLocUpdate, 2--147

estabIndicSignallingMoc, 2--149

estabIndicSignallingPagingRes, 2--146

estabIndicSignallingPiggybacked, 2--263

estabIndicSignallingReEstab, 2--148

estabIndicSignallingShortMsg, 2--151

estabIndicSignallingSuppService, 2--152

estabIndicSigPhase1, 2--153

estabIndicSigPhase2, 2--154

estabIndicSigPhase28W, 2--427

FfmDatabaseUsed, 2--497

Index Nortel Networks Confidentialxiv

PE/DCL/DD/0125411--9001--125


fmDatabaseUsedCum, 2--497

fmDatabaseUsedEch, 2--497

fmLogUsed, 2--497

fmLogUsedCum, 2--497

fmLogUsedEch, 2--497

ftamFtiDelete, 2--515

ftamFtiDeleteConf, 2--515

ftamFtiDir, 2--515

ftamFtiDirConf, 2--515

ftamFtiGet, 2--514

ftamFtiGetConf, 2--514

ftamFtiPut, 2--514

ftamFtiPutConf, 2--514

ftamFtiRename, 2--516

ftamFtiRenameConf, 2--516

fullDuplexTbfEstablishment, 2--541

GgprsImmAssRejectedSicd, 2--37

gprsPagingRejectedSicd, 2--38

gprsPreemption, 2--328

gprsPreemptionNack, 2--328

gprsRachRejectedSicd, 2--37

HhoBtsRejected, 2--294

hoExecutionIncomingInterBss, raw permanent, 2--29

hoExecutionIncomingInterBssSdcch, raw permanent, 2--74

hoExecutionIncomingIntraBss, raw permanent, 2--29

hoExecutionIncomingIntraBssSdcch, raw permanent, 2--74

hoExecutionIncomingIntraBssTchMsDualb, 2--303

hoExecutionIntraBts, raw permanent, 2--34

hoExecutionIntraBtsMsDualb, 2--305

hoExecutionIntraBtsSdcch, raw permanent, 2--78

hoExecutionOutgoingEbandEbandMsDualb, 2--301

hoExecutionOutgoingEbandMbandMsDualb, 2--302

hoExecutionOutgoingInterBss, raw permanent, 2--24

hoExecutionOutgoingInterBssForDirectedRetry, raw permanent, 2--24

IndexNortel Networks Confidential xv


hoExecutionOutgoingInterBssSdcch, raw permanent, 2--71

hoExecutionOutgoingIntraBss, raw permanent, 2--22

hoExecutionOutgoingIntraBssForDirectedRetry, raw permanent, 2--23

hoExecutionOutgoingIntraBssSdcch, raw permanent, 2--71

hoExecutionOutgoingMbandEbandMsDualb, 2--299

hoExecutionOutgoingMbandMbandMsDualb, 2--300

hoFailureIncomingInterBssSdcchChannelActivateNack, 2--276

hoFailureIncomingInterBssSdcchHoNotAllowed, 2--275

hoFailureIncomingInterBssSdcchRadioLack, 2--275

hoFailureIncomingInterBssSdcchTchnAckTimerExp, 2--276

hoFailureIncomingInterBssSdcchTerrestLack, 2--275

hoFailureIncomingInterBssTchChannelActivateNack, 2--273

hoFailureIncomingInterBssTchCICIncompatible, 2--274

hoFailureIncomingInterBssTchHoNotAllowed, 2--273

hoFailureIncomingInterBssTchRadioLack, 2--272

hoFailureIncomingInterBssTchTchnAckTimerExp, 2--274

hoFailureIncomingInterBssTchTerrestLack, 2--273

hoFailureIncomingIntraBssSdcchChannelActivateNack, 2--272

hoFailureIncomingIntraBssSdcchHoNotAllowed, 2--271

hoFailureIncomingIntraBssSdcchRadioLack, 2--270

hoFailureIncomingIntraBssSdcchTchnAckTimerExp, 2--272

hoFailureIncomingIntraBssTchChannelActivateNack, 2--269

hoFailureIncomingIntraBssTchHoNotAllowed, 2--269

hoFailureIncomingIntraBssTchIncompatible, 2--270

hoFailureIncomingIntraBssTchRadioLack, 2--269

hoFailureIncomingIntraBssTchTchnAckTimerExp, 2--270

hoFailureIntraBtsSdcchChannelActivateNack, 2--268

hoFailureIntraBtsSdcchRadioLack, 2--268

hoFailureIntraBtsSdcchTchnAckTimerExp, 2--268

hoFailureIntraBtsTchChannelActivateNack, 2--267

hoFailureIntraBtsTchRadioLack, 2--267

hoFailureIntraBtsTchTchnAckTimerExp, 2--267

hoFailureOutgoingInterBssSdcchHoNotAllowed, 2--282

hoFailureOutgoingInterBssSdcchOtherCases, 2--283

hoFailureOutgoingInterBssSdcchRadioLack, 2--282

hoFailureOutgoingInterBssSdcchT7TimerExp, 2--283

hoFailureOutgoingInterBssSdcchTerrestLack, 2--282

hoFailureOutgoingInterBssTchHoNotAllowed, 2--280

hoFailureOutgoingInterBssTchIncompatible, 2--281

hoFailureOutgoingInterBssTchOtherCases, 2--281

Index Nortel Networks Confidentialxvi

PE/DCL/DD/0125411--9001--125


hoFailureOutgoingInterBssTchRadioLack, 2--279

hoFailureOutgoingInterBssTchT7TimerExp, 2--280

hoFailureOutgoingInterBssTchTerrestLack, 2--280

hoFailureOutgoingIntraBssSdcchChannelActivateNack, 2--279

hoFailureOutgoingIntraBssSdcchHoNotAllowed, 2--278

hoFailureOutgoingIntraBssSdcchRadioLack, 2--278

hoFailureOutgoingIntraBssSdcchTchnAckTimerExp, 2--279

hoFailureOutgoingIntraBssTchChannelActivateNack, 2--277

hoFailureOutgoingIntraBssTchHoNotAllowed, 2--277

hoFailureOutgoingIntraBssTchIncompatible, 2--278

hoFailureOutgoingIntraBssTchRadioLack, 2--276

hoFailureOutgoingIntraBssTchTchnAckTimerExp, 2--277

hoFailureTieringTchNorrLargeToSmallPattern, 2--308

hoFailureTieringTchNorrSmallToLargePattern, 2--308

hoIndicationNotTreatedTchoke, 2--131

hoInExecutionBscSdcch, 2--479

hoInExecutionBscTch, 2--479

hoInInterSdcchExecutionBscFailRate, 2--471

hoInInterSdcchSelectionBscFailRate, 2--470

hoInInterTchExecutionBscFailRate, 2--470

hoInInterTchSelectionBscFailRate, 2--469

hoInIntraSdcchExecutionBscFailRate, 2--472

hoInIntraTchExecutionBscFailRate, 2--471

hoInSdcchExecutionFailMaxRate, 2--464

hoInSdcchExecutionFailRate, 2--450

hoInSdcchSelectionFailMaxRate, 2--463

hoInSdcchSelectionFailRate, 2--449

hoInTchExecutionFailMaxRate, 2--463

hoInTchExecutionFailRate, 2--449

hoInTchSelectionFailMaxRate, 2--462

hoInTchSelectionFailRate, 2--448

hoIntraBtsFailRateTchTieringLargeToSmallPattern, 2--458

hoIntraBtsFailRateTchTieringSmallToLargePattern, 2--459

hoNcellsExecution, 2--158

hoNcellsExecutionSdcch, 2--159

hoNCellsExecutionTchAmrFr, 2--392

hoNCellsExecutionTchAmrHr, 2--392

hoNCellsRequestOutgoingAmrFr, 2--397

hoNCellsRequestOutgoingAmrHr, 2--397

hoNcellsRequestOutgoingDirectedRetry, 2--342

IndexNortel Networks Confidential xvii


hoNcellsRequestOutgoingDistance, 2--341

hoNcellsRequestOutgoingDownlinkQuality, 2--340

hoNcellsRequestOutgoingDownlinkStrength, 2--339

hoNcellsRequestOutgoingInterCellOM, 2--342

hoNcellsRequestOutgoingOther, 2--343

hoNcellsRequestOutgoingPowerBudget, 2--341

hoNCellsRequestOutgoingTraffic, 2--343

hoNcellsRequestOutgoingUplinkQuality, 2--340

hoNcellsRequestOutgoingUplinkStrength, 2--339

hoNcellsSuccessOutgoingDirectedRetry, 2--347

hoNcellsSuccessOutgoingDistance, 2--346

hoNcellsSuccessOutgoingDownlinkQuality, 2--345

hoNcellsSuccessOutgoingDownlinkStrength, 2--344

hoNcellsSuccessOutgoingInterCellOM, 2--348

hoNcellsSuccessOutgoingOther, 2--349

hoNcellsSuccessOutgoingPowerBudget, 2--347

hoNcellsSuccessOutgoingTraffic, 2--348

hoNcellsSuccessOutgoingUplinkQuality, 2--345

hoNcellsSuccessOutgoingUplinkStrength, 2--344

hoNcellsUnsuccessSdcchChlR, 2--160

hoNcellsUnsuccessSdcchOther, 2--161

hoNcellsUnsuccessSdcchTimer, 2--161

hoNCellsUnsuccessTchAmrFrClearCommand, 2--395

hoNCellsUnsuccessTchAmrFrHandoverFailure, 2--394

hoNCellsUnsuccessTchAmrFrTimerExpiration, 2--394

hoNCellsUnsuccessTchAmrHrClearCommand, 2--394

hoNCellsUnsuccessTchAmrHrHandoverFailure, 2--393

hoNCellsUnsuccessTchAmrHrTimerExpiration, 2--393

hoNcellsUnsuccessTchChlR, 2--159

hoNcellsUnsuccessTchOther, 2--160

hoNcellsUnsuccessTchTimer, 2--160

hoOutExecutionBscSdcch, 2--478

hoOutExecutionBscTch, 2--478

hoOutFirstSuccessSdcchRatio, 2--474

hoOutFirstSuccessTchRatio, 2--473

hoOutInterSdcchExecutionBscFailRate, 2--473

hoOutInterTchExecutionBscFailRate, 2--472

hoOutSdcchBscGlobalFailRate, 2--465

hoOutSdcchBscGlobalFailRateV11, 2--465

hoOutSdcchExecutionBscFailRate, 2--469

Index Nortel Networks Confidentialxviii

PE/DCL/DD/0125411--9001--125


hoOutSdcchExecutionFailMaxRate, 2--462

hoOutSdcchExecutionFailRate, 2--448

hoOutSdcchFirstAttemptSuccessMinRatio, 2--464

hoOutSdcchFirstAttemptSuccessRatio, 2--451

hoOutSdcchGlobalFailRate, 2--444

hoOutSdcchGlobalFailRateV11, 2--444

hoOutSdcchMaxFailRate, 2--460

hoOutSdcchMaxFailRateV11, 2--460

hoOutSdcchRequestBscRatio, 2--466

hoOutSdcchRequestBscRatioV11, 2--466

hoOutSdcchRequestMaxRatio, 2--460

hoOutSdcchRequestMaxRatioV11, 2--460

hoOutSdcchRequestRatio, 2--445

hoOutSdcchRequestRatioV11, 2--445

hoOutSdcchSelectionBscFailRate, 2--467

hoOutSdcchSelectionFailMaxRate, 2--461

hoOutSdcchSelectionFailRate, 2--447

hoOutTchBscGlobalFailRate, 2--465

hoOutTchBscGlobalFailRateV11, 2--465

hoOutTchExecutionBscFailRate, 2--468

hoOutTchExecutionFailMaxRate, 2--462

hoOutTchExecutionFailRate, 2--447

hoOutTchFirstAttemptSuccessMinRatio, 2--464

hoOutTchFirstAttemptSuccessRatio, 2--450

hoOutTchGlobalFailRate, 2--444

hoOutTchGlobalFailRateV11, 2--444

hoOutTchMaxFailRate, 2--459

hoOutTchMaxFailRateV11, 2--459

hoOutTchRequestBscRatio, 2--466

hoOutTchRequestBscRatioV11, 2--466

hoOutTchRequestMaxRatio, 2--460

hoOutTchRequestMaxRatioV11, 2--460

hoOutTchRequestRatio, 2--445

hoOutTchRequestRatioV11, 2--445

hoOutTchSelectionBscFailRate, 2--467

hoOutTchSelectionFailMaxRate, 2--461

hoOutTchSelectionFailRate, 2--446

hoRequestIncomingInterBss, raw permanent, 2--28

hoRequestIncomingInterBss8W, 2--422

hoRequestIncomingInterBssSdcch, raw permanent, 2--73

IndexNortel Networks Confidential xix


hoRequestIncomingInterBssTchCtm, raw permanent, 2--28

hoRequestIncomingIntraBss, raw permanent, 2--27

hoRequestIncomingIntraBss8W, 2--422

hoRequestIncomingIntraBssSdcch, raw permanent, 2--73

hoRequestIncomingIntraBssTchMsDualb, 2--302

hoRequestIntraBts, raw permanent, 2--34

hoRequestIntraBts8W, 2--424

hoRequestIntraBtsMsDualb, 2--305

hoRequestIntraBtsSdcch, raw permanent, 2--78

hoRequestOutgoingEbandEbandMsDualb, 2--295

hoRequestOutgoingEbandMbandMsDualb, 2--296

hoRequestOutgoingInterBss, raw permanent, 2--32

hoRequestOutgoingInterBss8W, 2--423

hoRequestOutgoingInterBssSdcch, raw permanent, 2--76

hoRequestOutgoingInterBssSdcch8W, 2--425

hoRequestOutgoingIntraBss, raw permanent, 2--31

hoRequestOutgoingIntraBss8W, 2--423

hoRequestOutgoingIntraBssSdcch, raw permanent, 2--76

hoRequestOutgoingIntraBssSdcch8W, 2--425

hoRequestOutgoingMbandEbandMsDualb, 2--164

hoRequestOutgoingMbandMbandMsDualb, 2--294

hoRequestOutgoingMultiband, 2--164

hoRequiredSdcch, 2--290

hoRequiredSdcchCapture, raw permanent, 2--68

hoRequiredSdcchDistance, raw permanent, 2--67

hoRequiredSdcchDownlinkQuality, raw permanent, 2--66

hoRequiredSdcchDownlinkStrength, raw permanent, 2--65

hoRequiredSdcchInterBtsOm, raw permanent, 2--70

hoRequiredSdcchIntraBtsDownlink, raw permanent, 2--69

hoRequiredSdcchIntraBtsOm, raw permanent, 2--68

hoRequiredSdcchIntraBtsUplink, raw permanent, 2--69

hoRequiredSdcchPowerBudget, raw permanent, 2--67

hoRequiredSdcchTraffic, 2--70

hoRequiredSdcchUplinkQuality, raw permanent, 2--66

hoRequiredSdcchUplinkStrength, raw permanent, 2--65

hoRequiredTch, 2--289

hoRequiredTchCapture, raw permanent, 2--57

hoRequiredTchDirectedRetry, raw permanent, 2--59

hoRequiredTchDistance, raw permanent, 2--55

hoRequiredTchDownlinkQuality, raw permanent, 2--55

Index Nortel Networks Confidentialxx

PE/DCL/DD/0125411--9001--125


hoRequiredTchDownlinkStrength, raw permanent, 2--53

hoRequiredTchInterBtsOm, raw permanent, 2--62

hoRequiredTchIntraBtsDownlink, raw permanent, 2--59

hoRequiredTchIntraBtsOm, raw permanent, 2--57

hoRequiredTchIntraBtsUplink, raw permanent, 2--58

hoRequiredTchPowerBudgetQuality, raw permanent, 2--56

hoRequiredTchTdmaClass0, raw permanent, 2--60

hoRequiredTchTdmaClass1, raw permanent, 2--61

hoRequiredTchTieringLargeToSmallPattern, 2--63

hoRequiredTchTieringSmallToLargePattern, 2--64

hoRequiredTchTraffic, 2--62

hoRequiredTchUplinkQuality, raw permanent, 2--54

hoRequiredTchUplinkStrength, raw permanent, 2--53

hoSuccessIncomingInterBss, raw permanent, 2--30

hoSuccessIncomingInterBss8W, 2--423

hoSuccessIncomingInterBssSdcch, raw permanent, 2--75

hoSuccessIncomingIntraBss, raw permanent, 2--30

hoSuccessIncomingIntraBss8W, 2--422

hoSuccessIncomingIntraBssSdcch, raw permanent, 2--75

hoSuccessIncomingIntraBssTchMsDualb, 2--304

hoSuccessIncomingTch, 2--293

hoSuccessIntraBts, raw permanent, 2--35

hoSuccessIntraBts8W, 2--424

hoSuccessIntraBtsMsDualb, 2--306

hoSuccessIntraBtsSdcch, raw permanent, 2--79

hoSuccessOoutgoingIntraBssSdcch8W, 2--424

hoSuccessOutgoingEbandEbandMsDualb, 2--298

hoSuccessOutgoingEbandMbandMsDualb, 2--298

hoSuccessOutgoingFirstInter, 2--33

hoSuccessOutgoingFirstInterSdcch, 2--77

hoSuccessOutgoingFirstIntra, 2--32

hoSuccessOutgoingFirstIntraSdcch, 2--77

hoSuccessOutgoingInterBss, raw permanent, 2--26

hoSuccessOutgoingInterBss8W, 2--360

hoSuccessOutgoingInterBssForDirectedRetry, raw permanent, 2--27

hoSuccessOutgoingInterBssSdcch, raw permanent, 2--72

hoSuccessOutgoingIntraBss, raw permanent, 2--25

hoSuccessOutgoingIntraBss8W, 2--360

hoSuccessOutgoingIntraBssSdcch8W, 2--425

hoSuccessOutgoingIntraBssForDirectedRetry, raw permanent, 2--25

IndexNortel Networks Confidential xxi


hoSuccessOutgoingIntraBssSdcch, raw permanent, 2--72

hoSuccessOutgoingMbandEbandMsDualb, 2--164

hoSuccessOutgoingMbandMbandMsDualb, 2--297

hoSuccessOutgoingMultiband, 2--164

hoSuccessOutgoingTch, 2--291

hoSuccessTieringTchLargeToSmallPattern, 2--309

hoSuccessTieringTchSmallToLargePattern, 2--309

hoUnsuccessIncomingInterBssSdcchOtherCases, 2--289

hoUnsuccessIncomingInterBssSdcchTimerExp, 2--289

hoUnsuccessIncomingInterBssTchOtherCases, 2--288

hoUnsuccessIncomingInterBssTchTimerExp, 2--288

hoUnsuccessIncomingIntraCellSdcchReturnOldChannel, 2--287

hoUnsuccessIncomingIntraCellSdcchT3103TimerExp, 2--288

hoUnsuccessIncomingIntraCellTchReturnOldChannel, 2--287

hoUnsuccessIncomingIntraCellTchT3103TimerExp, 2--287

hoUnsuccessOutgoingInterBssNAttemptSdcch, 2--133

hoUnsuccessOutgoingInterBssNAttemptTch, 2--132

hoUnsuccessOutgoingInterCellSdcchOtherCases, 2--286

hoUnsuccessOutgoingInterCellSdcchReturnOldChannel, 2--286

hoUnsuccessOutgoingInterCellSdcchT3103TimerExp, 2--286

hoUnsuccessOutgoingInterCellTchOtherCases, 2--285

hoUnsuccessOutgoingInterCellTchReturnOldChannel, 2--285

hoUnsuccessOutgoingInterCellTchReturnOldChannel8W, 2--428

hoUnsuccessOutgoingInterCellTchT3103TimerExp8w, 2--429

hoUnsuccessOutgoingInterCellTchT3107TimerExp, 2--285

hoUnsuccessOutgoingInterCellTchT3107TimerExp8w, 2--285

hoUnsuccessOutgoingIntraBssNAttemptSdcch, 2--132

hoUnsuccessOutgoingIntraBssNAttemptTch, 2--131

hoUnsuccessOutgoingIntraCellSdcchReturnOldChannel, 2--284

hoUnsuccessOutgoingIntraCellSdcchT3103TimerExp, 2--284

hoUnsuccessOutgoingIntraCellTchReturnOldChannel, 2--283

hoUnsuccessOutgoingIntraCellTchReturnOldChannel8W, 2--428

hoUnsuccessOutgoingIntraCellTchT3103TimerExp, 2--284

hoUnsuccessOutgoingIntraCellTchT3107TimerExp8w, 2--428

hoUnsuccessReestIncomingIntraBssSdcch, 2--81

hoUnsuccessReestIncomingIntraBssTch, 2--52

hoUnsuccessReestIntraBtsSdcch, 2--79

hoUnsuccessReestIntraBtsTch, 2--51

hoUnsuccessReestOutgoingInterBssSdcch, 2--80

hoUnsuccessReestOutgoingInterBssTch, 2--52

Index Nortel Networks Confidentialxxii

PE/DCL/DD/0125411--9001--125


hoUnsuccessReestOutgoingIntraBssSdcch, 2--80

hoUnsuccessReestOutgoingIntraBssTch, 2--51

IimmAssignDualBandMSRate, 2--458

immediateAssignmentMultiband, 2--163

immediateAssignmentReject, 2--264

immediateAssignmentRejectChanActNack, 2--82

immediateAssignmentRejectChanActTimmack, 2--83

immediateAssignmentRejectOthers, 2--84

immediateAssignmentRejectOverload, 2--83

immediateAssignmentRejectRadioRes, 2--82

immediateAssignmentRejectTimingAdv, 2--84

immediateAssignmentRejectTraffMsc, 2--81

immediateAssignmentSuccess, 2--263

immediateAssignmentSuccessCause000, 2--140








incAmrFrDownModif, 2--410

incAmrFrDownModifTrZone, 2--410

incAmrFrUpModif, 2--409

incAmrFrUpModifTrZone, 2--409

incAmrHrDownModif, 2--411

incAmrHrDownModifTrZone, 2--411

incAmrHrUpModif, 2--411

incAmrHrUpModifTrZone, 2--411

intracellAmrFrDownHoRequiredTch, 2--384

intracellAmrFrUpHoRequiredTch, 2--384

invalidBlocksUp, 2--550

invalidProtocolErrorBlocksUp, 2--550

LlapdOverloadRejectedOpSicd0, 2--337

IndexNortel Networks Confidential xxiii


listenerDetectionExpiry, 2--431

llcDiscardedOctets, 2--531

llcDiscardedPdu, 2--531

llcPacketsDn, 2--547

llcPacketsUp, 2--546

localBusy, 2--545

localMsgBlockCapacity, 2--572

localMsgBlockUsageAvg, 2--572

localMsgBlockUsageMax, 2--572

localMsgBlockUsageMin, 2--572

lossOfComNN002Max, 2--557

lossOfComNT0001, 2--558

lossOfComT3169, 2--557



MMaxDlThroughput, 2--530

memoryCapacityFastRam, 2--568

memoryCapacityNormalRam, 2--569

memoryCapacitySharedRam, 2--569

memoryUsageAvgFastRam, 2--570

memoryUsageAvgMaxFastRam, 2--570

memoryUsageAvgMaxNormalRam, 2--570

memoryUsageAvgMaxSharedRam, 2--571

memoryUsageAvgMinFastRam, 2--570

memoryUsageAvgMinNormalRam, 2--570

memoryUsageAvgMinSharedRam, 2--571

memoryUsageAvgNormalRam, 2--570

memoryUsageAvgSharedRam, 2--571

msClassSensitivityToggle, 2--359

msFlowControlRequests, 2--531

msFlushLLRequest, 2--532

msLostMeasurements, 2--216

msLostMeasurementsAmrFr, 2--382

msLostMeasurementsAmrFrTrZone, 2--382

msLostMeasurementsAmrHr, 2--383

msLostMeasurementsAmrHrTrZone, 2--383

msLostMeasurementsTrZone, 2--216

Index Nortel Networks Confidentialxxiv

PE/DCL/DD/0125411--9001--125


msPowerDecControl, 2--316

msPowerDecControlAmrFr, 2--376

msPowerDecControlAmrHr, 2--380

msPowerIncControl, 2--315

msPowerIncControlAmrFr, 2--375

msPowerIncControlAmrHr, 2--380

NnbSamplesDnQuality, 2--554

nbSamplesUpQuality, 2--554

noPacketResourceReq, 2--556

notifsReachMaxTransmit, 2--513

notifsReceived, 2--512

notifsSentOnce, 2--513

notifsTransmitAgainOnce, 2--513

notifsTransmitAgainTwiceAndMore, 2--513

OoctetDiscarded, 2--528

octetsDataDn, 2--527

octetsDataUp, 2--528

octetsDn, 2--526

octetsUp, 2--526

omcDatabaseUsed, 2--519

omcDatabaseUsedCum, 2--519

omcDatabaseUsedEch, 2--519

omcInputIFrame, 2--166

omcInputRepeatedIFrame, 2--167

omcInputRnrFrame, 2--168

omcLinkSwitchOver, 2--49

omcOutputIFrame, 2--165

omcOutputRepeatedIFrame, 2--166

omcOutputRnrFrame, 2--167

omcSybaseCpuBusy, 2--518

omcSybaseIdle, 2--518

omcSybaseIoBusy, 2--518

omcSybasePacketErr, 2--519

omcSybasePacketIn, 2--518

IndexNortel Networks Confidential xxv


omcSybasePacketOut, 2--519

omcSybaseTotalError, 2--517

omcSybaseTotalRead, 2--517

omcSybaseTotalWrite, 2--517

omcUnixBasePartition, 2--524

omcUnixBasePartitionCum, 2--524

omcUnixBasePartitionEch, 2--524

omcUnixCpu0Used, 2--522

omcUnixCpu0UsedCum, 2--522

omcUnixCpu1Used, 2--522

omcUnixCpu1UsedCum, 2--522

omcUnixCpu1UsedEch, 2--522

omcUnixDataPartition, 2--525

omcUnixDataPartitionCum, 2--525

omcUnixDataPartitionEch, 2--525

omcUnixMailPartition, 2--524

omcUnixMailPartitionCum, 2--524

omcUnixMailPartitionEch, 2--524

omcUnixObsPartition, 2--524

omcUnixObsPartitionCum, 2--524

omcUnixRootPartition, 2--523

omcUnixRootPartitionCum, 2--523

omcUnixRootPartitionEch, 2--523

omcUnixSwap, 2--523

omcUnixSwapCum, 2--523

omcUnixSwapEch, 2--523

omcUnixTmpPartition, 2--523

omcUnixTmpPartitionCum, 2--523

omcUnixTmpPartitionEch, 2--523

omcX25AbortsPort0, 2--522




omcX25CrcErrorsPort0, 2--521




omcX25PacketInPort0, 2--521



Index Nortel Networks Confidentialxxvi

PE/DCL/DD/0125411--9001--125



omcX25PacketOutPort0, 2--521




ommdActConf, 2--507

ommdActRequest, 2--507

ommdCancelGetConf, 2--508

ommdCancelGetRequest, 2--508

ommdCreConf, 2--505

ommdCreRequest, 2--505

ommdDelConf, 2--507

ommdDelRequest, 2--506

ommdGetConf, 2--505

ommdGetRequest, 2--504

ommdSetConf, 2--506

ommdSetRequest, 2--506

omnetActConf, 2--511

omnetActRequest, 2--511

omnetCancelGetConf, 2--512

omnetCancelGetRequest, 2--512

omnetCreConf, 2--509

omnetCreRequest, 2--509

omnetDelConf, 2--511

omnetDelRequest, 2--510

omnetGetConf, 2--509

omnetGetRequest, 2--508

omnetSetConf, 2--510

omnetSetRequest, 2--510

outOfSequenceBlocksUp, 2--551

PpacketAckNackDn, 2--552

packetAckNackUp, 2--551

packetResourceRequest, 2--556

pagingResponse, raw instrument panel, 2--258

pathBalanceCum, 2--329

pathBalanceEch, 2--329

pathBalanceMax, 2--329

IndexNortel Networks Confidential xxvii


pathBalanceMoy, 2--329

pchAveragedQueueLength, 2--185

pchAveragedQueueLengthCell, 2--491

pchAveragedQueueLengthCellCum, 2--491

pchAveragedQueueLengthCellEch, 2--491

pchAveragedQueueLengthCellMax, 2--491

pchAveragedQueueLengthCellMoy, 2--491

pchAveragedQueueLengthEch, 2--185

pchAveragedQueueLengthMax, 2--185

pchAveragedQueueLengthTs2Ech, 2--185

pchAveragedQueueLengthTs2Moy, 2--185

pchAveragedQueueLengthTs4Cum, 2--185



pchAveragedQueueLengthTs6Cum, 2--185



pchMoreWait, 2--13

pchMoreWaitCell, 2--490

pchMoreWaitTs2, 2--13



pchNoWait, 2--8

pchNoWaitCell, 2--489

pchNoWaitTs2, 2--8

pchNoWaitTs4, 2--8

pchNoWaitTs6, 2--8

pchOneWait, 2--10

pchOneWaitCell, 2--489

pchOneWaitTs2, 2--10



pchQueuePagesDiscarded, 2--187

pchQueuePagesDiscardedCell, 2--491

pchQueuePagesDiscardedTs2, 2--187



pchTwoWait, 2--11

pchTwoWaitCell, 2--490

pchTwoWaitTs2, 2--11

Index Nortel Networks Confidentialxxviii

PE/DCL/DD/0125411--9001--125




pcmErrCorrEfficiency, 2--483

pcmFaultDDTIBoard, 2--266

pcmFaultExternal, 2--265

pcmFaultInternal, 2--266

pcmFaultOutOfService, 2--266

pcminsecondsCum, 2--485

pcminsecondsEch, 2--485

pcminsecondsMax, 2--485

pcminsecondsMoy, 2--485

pcmUnavailabilityCum, 2--49

pcmUnavailabilityEch, 2--49

pcmUnavailabilityMax, 2--49

pcmUnavailabilityMoy, 2--49

pcuAgprsJokerNbofBlocksDn, 2--594

pcuAgprsJokerNbofBlocksUp, 2--597

pcuAgprsMainNbofBlocksDn, 2--591

pcuAgprsMainNbofBlocksUp, 2--597

pcuChannelRequestOnePhase, 2--620

pcuContentionFailureOnePhase, 2--621, 2--623

pcuDlThroughputCum, 2--529

pcuDyAgprsLoadCriterionNbs, 2--577

pcuDyAgprsNbTimeslots, 2--576

pcuDyAgprsNbTimeslotsCun, 2--576

pcuDyAgprsNbTimeslotsNbs, 2--576

pcuDynAgprsJokerAvgNbTimeslot, 2--594

pcuDynAgprsJokerCumNbTimeslot, 2--594

pcuDynAgprsJokerMaxNbTimeslot, 2--594

pcuDynAgprsJokerMinNbTimeslot, 2--594

pcuDynAgprsJokerNbsNbTimeslot, 2--594

pcuEdgeCell15114s0, 2--593








pcuEdgeDataBlocksReceivedUp, 2--583

IndexNortel Networks Confidential xxix


pcuEdgeDnAvg8PskMeanBep, 2--584

pcuEdgeDnAvgUsefulDataPerCell, 2--592

pcuEdgeDnCum8PskMeanBep, 2--584

pcuEdgeDnAvgGmskMeanBep, 2--586

pcuEdgeDnCumGmskMeanBep, 2--586

pcuEdgeDnNbsGmskMeanBep, 2--586

pcuEdgeDnCumUsefulDataPerCell, 2--592

pcuEdgeDnNbs8PskMeanBep, 2--584

pcuEdgeDnNbsUsefulDataPerCell, 2--592

pcuEdgeDnTransmittedMcs2, 2--598







pcuEdgeDnUsefulDataDurationPerCell, 2--596

pcuEdgeDowngradedTbf, 2--591

pcuEdgeDowngradedTbfAvg, 2--591

pcuEdgeDowngradedTbfNbs, 2--591

pcuEdgeLADnTargetedTransmittedMcs2, 2--604







pcuEdgeLAUpTargetedTransmittedMcs2, 2--617







pcuEdgeMcs2RequestRetransDataBlockDn, 2--601

pcuEdgeMcs2RequestRetransDataBlockUp, 2--610





Index Nortel Networks Confidentialxxx

PE/DCL/DD/0125411--9001--125










pcuEdgeTbfEstReq, 2--595

pcuEdgeTdma15100s0, 2--583






pcuEdgeUpAvgMeanBep, 2--588

pcuEdgeUpAvgUsefulDataPerCell, 2--592

pcuEdgeUpCumMeanBep, 2--588

pcuEdgeUpCumUsefulDataPerCell, 2--592

pcuEdgeUpNbsMeanBep, 2--588

pcuEdgeUpNbsUsefulDataPerCell, 2--592

pcuEdgeUpTransmittedMcs2, 2--607







pcuEdgeUpUsefulDataDurationPerCell, 2--596

pcuLackAbisJokerTSAvg, 2--598

pcuLackAbisJokerTSCum, 2--598

pcuLackAbisJokerTSNbs, 2--598

pcuUpPipeGreater22kbps, 2--623

pcuUpTbfImmediateAssignmentOnePhase, 2--621

pcuUpThroughputAvg, 2--622

pcuUpThroughputCum, 2--622

pcuUpThroughputNbs, 2--622

pduDataDn, 2--527

pduDataUp, 2--527

preemptedEdgeTsCum, 2--357

IndexNortel Networks Confidential xxxi


preemptedEdgeTsEch, 2--357

preemptedEdgeTsMax, 2--357

preemptedEdgeTsMoy, 2--357

preemptedEdgeTsTrZoneCum, 2--357

preemptedEdgeTsTrZoneEch, 2--357

preemptedEdgeTsTrZoneMax, 2--357

preemptedEdgeTsTrZoneMoy, 2--357

prLoadCne3OmuSbcMoy/Max/Cum/Ech, 2--360

prLoadCne3TmuPmcCum, 2--362

prLoadCne3TmuPmcEch, 2--362

prLoadCne3TmuPmcMax, 2--362

prLoadCne3TmuPmcMoy, 2--362

prLoadCne3TmuSbcCum, 2--361

prLoadCne3TmuSbcEch, 2--361

prLoadCne3TmuSbcMax, 2--361

prLoadCne3TmuSbcMoy, 2--361

prLoadCpue1Cum, 2--169

prLoadCpue1Max, 2--169

prLoadCpue1Moy, 2--169

prLoadCpue2Cum, 2--169

prLoadCpue2Ech, 2--169

prLoadCpue2Max, 2--169

prLoadCpue2Moy, 2--169

prLoadCpueCum, 2--169

prLoadCpueEch, 2--169

prLoadCpueMax, 2--169

prLoadCpueMoy, 2--169

prLoadCpumCum, 2--168

prLoadCpumEch, 2--168

prLoadCpumMax, 2--168

prLoadCpumMoy, 2--168

prLoadSicd[x], 2--170

psPaging, 2--574

PsPagingOnCCCH, 2--533

QqualityHoFiltered, 2--383

RrachAccessCount, 2--7

Index Nortel Networks Confidentialxxxii

PE/DCL/DD/0125411--9001--125


rachAccessCountCell, 2--489

rachAccessCountTs2, 2--7



rachBusyCount, 2--6

rachBusyCountCell, 2--488

rachBusyCountTs2, 2--6



rachNonDecodedAvLevelCell, 2--490

rachNonDecodedAvLevelCum, 2--15

rachNonDecodedAvLevelEch, 2--15

rachNonDecodedAvLevelMax, 2--15

rachNonDecodedAvLevelMoy, 2--15

rachNonDecodedAvLevelTs2, 2--15

rachNonDecodedAvLevelTs2Cum, 2--15

rachNonDecodedAvLevelTs2Ech, 2--15

rachNonDecodedAvLevelTs2Max, 2--15




rachNonDecodedAvLevelTs4Max, 2--15




radioFrameUlReceived, 2--253

rafficRelease8W, 2--426

relativeTimeDLPowerCtrlMaxSdcch, 2--456

relativeTimeDLPowerCtrlMaxTch, 2--455

relativeTimeULPowerCtrlMaxSdcch, 2--457

relativeTimeULPowerCtrlMaxTch, 2--455

requestedHandoverForDualBandMSToSecondVersusMainBand, 2--457

RequestedRetransmittedDataBlocksDN, 2--546

retransmittedDataBlocksDn, 2--555

rsttraceDatabaseUsed, 2--520

rsttraceDatabaseUsedCum, 2--520

rsttraceDatabaseUsedEch, 2--520

rxBytes, 2--573

rxFrames, 2--573

rxLevDownLink, 2--217

IndexNortel Networks Confidential xxxiii


RxLevDownlinkAmrFr, 2--374

RxLevDownlinkAmrFrTrZone, 2--374

RxLevDownlinkAmrHr, 2--379

RxLevDownlinkAmrHrTrZone, 2--379

rxLevDownLinkTrZone, 2--217

rxLevUpLink, 2--218

RxLevUplinkAmrFr, 2--374

RxLevUplinkAmrFrTrZone, 2--374

RxLevUplinkAmrHr, 2--379

RxLevUplinkAmrHrTrZone, 2--379

rxLevUpLinkTrZone, 2--219

rxQualDownLink, 2--220

RxQualDownlinkAmrFr, 2--375

RxQualDownlinkAmrFrTrZone, 2--375

RxQualDownlinkAmrHr, 2--379

RxQualDownlinkAmrHrTrZone, 2--379

rxQualDownLinkTrZone, 2--222

rxQualUpLink, 2--223

RxQualUplinkAmrFr, 2--375

RxQualUplinkAmrFrTrZone, 2--375

RxQualUplinkAmrHr, 2--380

RxQualUplinkAmrHrTrZone, 2--380

rxQualUpLinkTrZone, 2--224

rxTotalLinkUtil, 2--574

Ssapi3SessionEstablishment, 2--215

sccpAllocated, 2--41

sccpAllocatedLcs, 2--42

sccpAveragedUsed, raw permanent, 2--42

sccpResourceFailureRatio, 2--475

sccpRessourceFailure, 2--44

sccpRessourceFailureBscRefusal, 2--44

sccpRessourceFailureBscRefusalLcs, 2--45

sccpRessourceFailureLcs, 2--45

scseFailConnect, 2--498

scseRgeIn, 2--498

scseTgeOut, 2--498

scseTotAssocFree, 2--499

Index Nortel Networks Confidentialxxxiv

PE/DCL/DD/0125411--9001--125


scseTotTgeRefused, 2--498

sdcchAllocated, 2--189

sdcchAllocatedTrZone, 2--189

sdcchAverageConfiguratedCum, 2--323

sdcchAverageConfiguratedEch, 2--323

sdcchAverageConfiguratedMax, 2--323

sdcchAverageConfiguratedMoy, 2--323

sdcchAverageConfiguratedTrZoneCum, 2--323

sdcchAverageConfiguratedTrZoneEch, 2--323

sdcchAverageConfiguratedTrZoneMax, 2--323

sdcchAverageConfiguratedTrZoneMoy, 2--323

sdcchAveragedAvailableCum, 2--229

sdcchAveragedAvailableEch, 2--229

sdcchAveragedAvailableMax, 2--229

sdcchAveragedAvailableMoy, 2--229

sdcchAveragedAvailableTrZone, 2--229

sdcchAveragedAvailableTrZoneCum, 2--229

sdcchAveragedAvailableTrZoneEch, 2--229

sdcchAveragedAvailableTrZoneMax, 2--229

sdcchAveragedUsedCum, 2--190

sdcchAveragedUsedEch, 2--190

sdcchAveragedUsedMax, 2--190

sdcchAveragedUsedMoy, 2--190

sdcchAveragedUsedTrZoneCum, 2--190

sdcchAveragedUsedTrZoneEch, 2--190

sdcchAveragedUsedTrZoneMax, 2--190

sdcchAveragedUsedTrZoneMoy, 2--190

sdcchRessourceFailure, 2--192

sdcchRessourceFailureTrZone, 2--192

sharedMsgBlockCapacity, 2--571

sharedMsgBlockUsageAvg, 2--571

sharedMsgBlockUsageAvgMax, 2--571

sharedMsgBlockUsageAvgMin, 2--571

signallingAbnormalReleaseCell, 2--290

signallingPhaseDurationHigh, 2--17

signallingPhaseDurationHighCum, 2--17

signallingPhaseDurationHighEch, 2--17

signallingPhaseDurationHighMax, 2--17

signallingPhaseDurationHighMoy, 2--17

signallingPhaseDurationMoy/Max/Cum/Ech, 2--16

IndexNortel Networks Confidential xxxv


signallingReleaseBts, 2--264

signallingReleaseBts8W, 2--426

signallingReleaseBtsCallClearing, 2--95

signallingReleaseBtsCicRemovalEqptFail, 2--94

signallingReleaseBtsClearCommand, 2--102

signallingReleaseBtsCnxFailRadioIntFail, 2--95

signallingReleaseBtsCnxFailRadioLinkFail, 2--96

signallingReleaseBtsCnxFailRemTransFail, 2--106

signallingReleaseBtsErrorIndDm, 2--101

signallingReleaseBtsErrorIndSeq, 2--101

signallingReleaseBtsErrorIndT200, 2--99

signallingReleaseBtsIncFirstL3, 2--91

signallingReleaseBtsOmCicRemoval, 2--93

signallingReleaseBtsOmRadioChanBloc, 2--94

signallingReleaseBtsOmTsRemoval, 2--92

signallingReleaseBtsOthers, 2--105

signallingReleaseBtsReleaseInd, 2--97

signallingReleaseBtsReset, 2--89

signallingReleaseBtsResetCirc, 2--90

signallingReleaseBtsRfResInd, 2--103

signallingReleaseBtsSccpDataRefusal, 2--90

signallingReleaseBtsSccpDiscInd, 2--89

signallingReleaseBtsSwitchOver, 2--103

signallingReleaseBtsT11, 2--106



signallingReleaseBtsT3107CircDown, 2--92

signallingReleaseBtsT3107CircDown8W, 2--426


signallingReleaseBtsTmodMs, 2--104

signallingReleaseBtsTsRemovalEqptFail, 2--93

signallingReleaseCellTbcEdge, 2--107

signallingReleaseNoBts, 2--264

signallingReleaseNoBtsBadDataInd, 2--87

signallingReleaseNoBtsOthers, 2--88

signallingReleaseNoBtsReset, 2--86

signallingReleaseNoBtsSccpDataRefusal, 2--86

signallingReleaseNoBtsSccpDiscInd, 2--85

signallingReleaseNoBtsTsccRel, 2--87

signallingReleaseRatio, 2--487

Index Nortel Networks Confidentialxxxvi

PE/DCL/DD/0125411--9001--125


speechAlgoFallBack, 2--161, 2--162

ss7InputMsu, 2--432

ss7Level2ErrorMsuCongest, 2--433

ss7Level2ErrorNegAckRec, 2--433

ss7Level2ErrorNegAckTrans, 2--433

ss7Level2ErrorSuErr, 2--434

ss7Level3ErrorDelay, 2--434

ss7Level3ErrorHighErrRate, 2--434

ss7OutputMsu, 2--432

successfulTchFrSeizures, 2--19

successfulTchFrSeizures8W, 2--359

successfulTchFrSeizuresMsDualb, 2--250

sybaseCpuBusy, 2--495

sybaseIdle, 2--495

sybaseIoBusy, 2--495

sybasePacketErr, 2--496

sybasePacketIn, 2--495

sybasePacketOut, 2--496

sybaseTotalError, 2--494

sybaseTotalRead, 2--494

sybaseTotalWrite, 2--494

Tt3103ExpSdcch, 2--453

t3103ExpTch, 2--453

t3107ExpAssign, 2--451

t3107ExpIntraBtsHoSdcch, 2--452

t3107ExpIntraBtsHoTch, 2--452

tbfNormalReleaseDn, 2--555

tbfNormalReleaseUp, 2--555

tcAllocated, 2--39

tcAveragedUsed, raw permanent, 2--40

tchAveragedQueueLengthHighPriorityCum, 2--206

tchAveragedQueueLengthHighPriorityEch, 2--206

tchAveragedQueueLengthHighPriorityMax, 2--206

tchAveragedQueueLengthHighPriorityMoy, 2--206

tchAveragedQueueLengthOtherPriority, 2--207

tchFrAllocated, 2--258

tchFrAllocatedOverflowAllocation, 2--195

IndexNortel Networks Confidential xxxvii


tchFrAllocatedOverflowAllocationTrZone, 2--195

tchFrAllocatedPrimoAllocation, 2--194

tchFrAllocatedPrimoAllocationTrZone, 2--194

tchFrAllocatedTchAllocation, 2--193

tchFrAllocatedTchAllocationTrZone, 2--193

tchFrAllocatedTrZone, 2--259

tchFrAllocatedWps, 2--196

tchFrAllocatedWpsTrZone, 2--196

tchFrAverageConfigurated, 2--322

tchFrAverageConfiguratedCellCum, 2--336

tchFrAverageConfiguratedCellEch, 2--336

tchFrAverageConfiguratedCellMax, 2--336

tchFrAverageConfiguratedCellMoy, 2--336

tchFrAverageConfiguratedCum, 2--322

tchFrAverageConfiguratedEch, 2--322

tchFrAverageConfiguratedMax, 2--322

tchFrAverageConfiguratedMoy, 2--322

tchFrAverageConfiguratedTrZoneCum, 2--322

tchFrAverageConfiguratedTrZoneEch, 2--322

tchFrAverageConfiguratedTrZoneMax, 2--322

tchFrAverageConfiguratedTrZoneMoy, 2--322

tchFrAveragedAvailable, 2--227

tchFrAveragedAvailableCellCum, 2--335

tchFrAveragedAvailableCellEch, 2--335

tchFrAveragedAvailableCellMax, 2--335

tchFrAveragedAvailableCellMoy, 2--335

tchFrAveragedAvailableCum, 2--227

tchFrAveragedAvailableEch, 2--227

tchFrAveragedAvailableMax, 2--227

tchFrAveragedAvailableMoy, 2--227

tchFrAveragedAvailableTrZoneCum, 2--227

tchFrAveragedAvailableTrZoneEch, 2--227

tchFrAveragedAvailableTrZoneMax, 2--227

tchFrAveragedAvailableTrZoneMoy, 2--227

tchFrAveragedUsed, 2--197

tchFrAveragedUsedAllocationMax, 2--199

tchFrAveragedUsedCellCum, 2--336

tchFrAveragedUsedCellEch, 2--336

tchFrAveragedUsedCellMax, 2--336

tchFrAveragedUsedCellMoy, 2--336

Index Nortel Networks Confidentialxxxviii

PE/DCL/DD/0125411--9001--125


tchFrAveragedUsedCum, 2--261

tchFrAveragedUsedEch, 2--261

tchFrAveragedUsedMax, 2--261

tchFrAveragedUsedMoy, 2--261

tchFrAveragedUsedNsc, 2--261

tchFrAveragedUsedOverflowAllocationCellCum, 2--333

tchFrAveragedUsedOverflowAllocationCellEch, 2--333

tchFrAveragedUsedOverflowAllocationCellMax, 2--333

tchFrAveragedUsedOverflowAllocationCellMoy, 2--333

tchFrAveragedUsedOverflowAllocationCum, 2--200

tchFrAveragedUsedOverflowAllocationEch, 2--200

tchFrAveragedUsedOverflowAllocationMax, 2--200

tchFrAveragedUsedOverflowAllocationMoy, 2--200

tchFrAveragedUsedOverflowAllocationTrZoneCum, 2--200

tchFrAveragedUsedOverflowAllocationTrZoneEch, 2--200

tchFrAveragedUsedOverflowAllocationTrZoneMax, 2--200

tchFrAveragedUsedOverflowAllocationTrZoneMoy, 2--200

tchFrAveragedUsedPrimoAllocation, 2--476

tchFrAveragedUsedPrimoAllocationCellCum, 2--333

tchFrAveragedUsedPrimoAllocationCellEch, 2--333

tchFrAveragedUsedPrimoAllocationCellMax, 2--333

tchFrAveragedUsedPrimoAllocationCellMoy, 2--333

tchFrAveragedUsedPrimoAllocationMoy, 2--199

tchFrAveragedUsedPrimoAllocationTrZoneCum, 2--199

tchFrAveragedUsedPrimoAllocationTrZoneEch, 2--199

tchFrAveragedUsedPrimoAllocationTrZoneMax, 2--199

tchFrAveragedUsedPrimoAllocationTrZoneMoy, 2--199

tchFrAveragedUsedTchAllocationCellCum, 2--332

tchFrAveragedUsedTchAllocationCellEch, 2--332

tchFrAveragedUsedTchAllocationCellMax, 2--332

tchFrAveragedUsedTchAllocationCellMoy, 2--332

tchFrAveragedUsedTchAllocationCum, 2--197

tchFrAveragedUsedTchAllocationEch, 2--197

tchFrAveragedUsedTchAllocationMax, 2--197

tchFrAveragedUsedTchAllocationTrZoneCum, 2--197

tchFrAveragedUsedTchAllocationTrZoneEch, 2--197

tchFrAveragedUsedTchAllocationTrZoneMax, 2--197

tchFrAveragedUsedTchAllocationTrZoneMoy, 2--197

tchFrAveragedUsedTrZoneCum, 2--261

tchFrAveragedUsedTrZoneEch, 2--261

IndexNortel Networks Confidential xxxix


tchFrAveragedUsedTrZoneMax, 2--261

tchFrAveragedUsedTrZoneMoy, 2--261

tchFrAveragedUsedWpsCellCum, 2--334

tchFrAveragedUsedWpsCellEch, 2--334

tchFrAveragedUsedWpsCellMax, 2--334

tchFrAveragedUsedWpsCellMoy, 2--334

tchFrAveragedUsedWpsCum, 2--201

tchFrAveragedUsedWpsEch, 2--201

tchFrAveragedUsedWpsMax, 2--201

tchFrAveragedUsedWpsMoy, 2--201

tchFrAveragedUsedWpsTrZoneCum, 2--201

tchFrAveragedUsedWpsTrZoneEch, 2--201

tchFrAveragedUsedWpsTrZoneMax, 2--201

tchFrAveragedUsedWpsTrZoneMoy, 2--201

tchFrRessourceFailure, 2--204

tchFrRessourceFailureTrZone, 2--204

tchHrAllocated, 2--260

tchHrAllocatedNsc, 2--260

tchHrAllocatedPrimoAllocation, 2--196

tchHrAllocatedPrimoAllocationTrZone, 2--196

tchHrAllocatedTchAllocation, 2--196

tchHrAllocatedTchAllocationTrZone, 2--196

tchHrAllocatedTrZone, 2--260

tchHrAllocatedWps, 2--196

tchHrAllocatedWpsTrZone, 2--196

tchHrAveragedUsed, 2--355

tchHrAveragedUsedCum, 2--262

tchHrAveragedUsedEch, 2--262

tchHrAveragedUsedMax, 2--262

tchHrAveragedUsedMoy, 2--262

tchHrAveragedUsedNsc, 2--356

tchHrAveragedUsedPrimoAllocationCum, 2--203Ech, 2--203Max, 2--203Moy, 2--203

tchHrAveragedUsedPrimoAllocationTrZoneCum, 2--203Ech, 2--203Max, 2--203Moy, 2--203

Index Nortel Networks Confidentialxl

PE/DCL/DD/0125411--9001--125


tchHrAveragedUsedTchAllocationCum, 2--202

tchHrAveragedUsedTrZoneCum, 2--262

tchHrAveragedUsedTrZoneEch, 2--262

tchHrAveragedUsedTrZoneMax, 2--262

tchHrAveragedUsedTrZoneMoy, 2--262

tchHrAveragedUsedWpsCum, 2--203Ech, 2--203Max, 2--203Moy, 2--203

tchHrAveragedUsedWpsMax, 2--202

tchHrAveragedUsedWpsMoy, 2--202

tchHrAveragedUsedWpsTrZoneCum, 2--203Ech, 2--203Max, 2--203Moy, 2--203

tchHrAveragedUsedWpsTrZoneEch, 2--202

tchHrAveragedUsedWpsTrZoneMax, 2--202

tchHrAveragedUsedWpsTrZoneMoy, 2--202

tchHrRessourceFailure, 2--205

tchHrRessourceFailureTrZone, 2--205

tchQueuingDurationHighPriority, 2--209

tchQueuingDurationOtherPriority, 2--210

tchQueuingExpirationHighPriority, 2--208

tchQueuingExpirationOtherPriority, 2--208

tdmaClassTchResourceFailureRatio, 2--492

timingAdvanceAmrFrAvg, 2--377

timingAdvanceAmrFrMax, 2--377

timingAdvanceAmrHrAvg, 2--382

timingAdvanceAmrHrMax, 2--382

timingAdvanceAverage, 2--319

timingAdvanceAverageTrZone, 2--319

timingAdvanceMaximum, 2--321

timingAdvanceMaximumTrZone, 2--321

totalNumberOfEdgeTsCum, 2--356

totalNumberOfEdgeTsEch, 2--356

totalNumberOfEdgeTsMax, 2--356

totalNumberOfEdgeTsMoy, 2--356

totalNumberOfEdgeTsTrZoneCum, 2--356

totalNumberOfEdgeTsTrZoneEch, 2--356

IndexNortel Networks Confidential xli


totalNumberOfEdgeTsTrZoneMax, 2--356

totalNumberOfEdgeTsTrZoneMoy, 2--356

totalNumberOfPacketTsCellCum, 2--330

totalNumberOfPacketTsCellEch, 2--330

totalNumberOfPacketTsCellMax, 2--330

totalNumberOfPacketTsCellMoy, 2--330

totalNumberOfPacketTsMoy, 2--326

totalNumberOfPacketTsUsedForCircuitCellCum, 2--331

totalNumberOfPacketTsUsedForCircuitCellMax, 2--331

totalNumberOfPacketTsUsedForCircuitCellMoy, 2--331

totalRetransmissionRequested, 2--552

traceDatabaseSeg0Used, 2--519

traceDatabaseSeg0UsedCum, 2--519

traceDatabaseSeg0UsedEch, 2--519

traceDatabaseSeg1Used, 2--520

traceDatabaseSeg1UsedCum, 2--520

traceDatabaseSeg1UsedEch, 2--520

trafficAbnormalRelease, 2--291

trafficAbnormalRelease8w, 2--429

trafficRelease, 2--265

trafficReleaseAmrFrLapdmCause, 2--395

trafficReleaseAmrFrOthersCause, 2--396

trafficReleaseAmrFrRadioCause, 2--395

trafficReleaseAmrHrLapdmCause, 2--396

trafficReleaseAmrHrOthersCause, 2--397

trafficReleaseAmrHrRadioCause, 2--396

trafficReleaseCallClearing, 2--112

trafficReleaseCicRemovalEqptFail, 2--111

trafficReleaseClearCommand, 2--119

trafficReleaseCnxFailRadioIntFail, 2--113

trafficReleaseCnxFailRadioLinkFail, 2--113

trafficReleaseCnxFailRemTransFail, 2--126

trafficReleaseErrorIndDm, 2--118

trafficReleaseErrorIndSeq, 2--118

trafficReleaseErrorIndT200, 2--116

trafficReleaseOmCicRemoval, 2--111

trafficReleaseOmRadioChanBloc, 2--112

trafficReleaseOmTsRemoval, 2--110

trafficReleaseOthers, 2--121

trafficReleaseReleaseInd, 2--114

Index Nortel Networks Confidentialxlii

PE/DCL/DD/0125411--9001--125


trafficReleaseReset, 2--108

trafficReleaseResetCirc, 2--108

trafficReleaseRfResInd, 2--119

trafficReleaseSccpDataRefusal, 2--109

trafficReleaseSccpDiscInd, 2--107

trafficReleaseSysInfoFail, 2--126

trafficReleaseT3103, 2--120

trafficReleaseT3107CircDown, 2--109

trafficReleaseT8, 2--121

trafficReleaseTbcEdge, 2--130

trafficReleaseTmodMs, 2--120

trafficReleaseTsRemovalEqptFail, 2--110

txBytes, 2--573

txFrames, 2--574

UulsecondPhaseAllocFailure, 2--541

ulsecondPhaseRadioFailure, 2--544

unixCmnBasePartitionNMCSrv, 2--504

unixCmnBasePartitionNMCSrvCum, 2--504

unixCmnBasePartitionNMCSrvEch, 2--504

unixCmnDataPartitionNMCSrv, 2--504

unixCmnDataPartitionNMCSrvCum, 2--504

unixCmnDataPartitionNMCSrvEch, 2--504

unixCpu0UsedNMCSrv, 2--499

unixCpu0UsedNMCSrvCum, 2--499

unixCpu0UsedNMCSrvEch, 2--499

unixCpu1UsedNMCSrv, 2--499

unixCpu1UsedNMCSrvCum, 2--499

unixCpu1UsedNMCSrvEch, 2--499

unixDataSsnPartition, 2--502

unixDataSsnPartitionCum, 2--502

unixDataSsnPartitionEch, 2--502

unixMdrBasePartitionNMCSrv, 2--503

unixMdrBasePartitionNMCSrvCum, 2--503

unixMdrBasePartitionNMCSrvEch, 2--503

unixMdrDataPartitionNMCSrv, 2--503

unixMdrDataPartitionNMCSrvCum, 2--503

unixMdrDataPartitionNMCSrvEch, 2--503

IndexNortel Networks Confidential xliii


unixNotifPartition, 2--501

unixNotifPartitionCum, 2--501

unixNotifPartitionEch, 2--501

unixObsPartition, 2--501

unixObsPartitionCum, 2--501

unixObsPartitionEch, 2--501

unixRestoredNotifPartition, 2--502

unixRestoredNotifPartitionCum, 2--502

unixRestoredNotifPartitionEch, 2--502

unixRestoredObsPartition, 2--501

unixRestoredObsPartitionCum, 2--501

unixRestoredObsPartitionEch, 2--501

unixRestoredTracePartition, 2--503

unixRestoredTracePartitionCum, 2--503

unixRestoredTracePartitionEch, 2--503

unixRootPartitionNMCSrv, 2--500

unixRootPartitionNMCSrvCum, 2--500

unixRootPartitionNMCSrvEch, 2--500

unixSwapNMCSrv, 2--500

unixSwapNMCSrvCum, 2--500

unixSwapNMCSrvEch, 2--500

unixTmpPartitionNMCSrv, 2--500

unixTmpPartitionNMCSrvCum, 2--500

unixTmpPartitionNMCSrvEch, 2--500

unixTracePartition, 2--502

unixTracePartitionCum, 2--502

unixTracePartitionEch, 2--502

uplinkPowerCtrlMaxSdcchCum, 2--181

uplinkPowerCtrlMaxSdcchEch, 2--181

uplinkPowerCtrlMaxSdcchMax, 2--181

uplinkPowerCtrlMaxSdcchMoy, 2--181

uplinkPowerCtrlMaxTchAmrFrCum, 2--374

uplinkPowerCtrlMaxTchAmrFrEch, 2--374

uplinkPowerCtrlMaxTchAmrFrMax, 2--374

uplinkPowerCtrlMaxTchAmrFrMoy, 2--374

uplinkPowerCtrlMaxTchAmrHrCum, 2--378

uplinkPowerCtrlMaxTchAmrHrEch, 2--378

uplinkPowerCtrlMaxTchAmrHrMax, 2--378

uplinkPowerCtrlMaxTchAmrHrMoy, 2--378

uplinkPowerCtrlMaxTchCum, 2--157

Index Nortel Networks Confidentialxliv

PE/DCL/DD/0125411--9001--125


uplinkPowerCtrlMaxTchEch, 2--157

uplinkPowerCtrlMaxTchMax, 2--157

uplinkPowerCtrlMaxTchMoy, 2--157

upMultiSlotRequest1, 2--534




upPipeGreater11kbps, 2--564

upPipeless11kbps, 2--563

upTbfBronzeRejectedForMinTput, 2--566

upTbfBronzeSatisfactBet5090pCent, 2--565

upTbfBronzeSatisfactLess50pCent, 2--565

upTbfBronzeSatisfactMore90pCent, 2--564

upTbfGoldRejectedForMinTput, 2--537

upTbfGoldSatisfactBet5090pCent, 2--536

upTbfGoldSatisfactLess50pCent, 2--536

upTbfGoldSatisfactMore90pCent, 2--536

upTbfImmAssigRejectNoPdch, 2--561

upTbfImmediateAssignment, 2--560

upTbfReleases, 2--542

upTbfSilverRejectedForMinTput, 2--563

upTbfSilverSatisfactLess50pCent, 2--565

upUserdatablocks, 2--545

VvgcsAccessGrant, 2--175

vgcsMscReject, 2--176

WwpsAccessBarringDurationClass0to9, 2--418, 2--419, 2--420

wpsAccessBarringDurationClass11, 2--418





WPUBWPSQ, 2--420

WQABAND, 2--421

WQOVFL1, 2--414

IndexNortel Networks Confidential xlv


WQOVFL2, 2--414

WQOVFL3, 2--415

WQOVFL4, 2--415

WQOVFL5, 2--415

WQTOUT1, 2--416, 2--417

WQTOUT2, 2--416

WQTOUT3, 2--416

WQTOUT4, 2--417

WQTOUT5, 2--417

WQUEDHO, 2--421, 2--430

WQUEUED1, 2--412, 2--413

WQUEUED2, 2--413

WQUEUED3, 2--413

WQUEUED4, 2--413

WQUEUED5, 2--414

Wireless Service Provider SolutionsObservation Counter Dictionary

Copyright © 2000--2005 Nortel Networks, All Rights Reserved

NORTEL NETWORKS CONFIDENTIAL:

The information contained in this document is the property of NortelNetworks. Except as specifically authorized in writing by NortelNetworks, the holder of this document shall keep the informationcontained herein confidential and shall protect same in whole or in partfrom 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, theinformation contained herein in any way or in any form without priorwritten consent of Nortel Networks.

The following are trademarks of Nortel Networks: *NORTELNETWORKS, the NORTEL NETWORKS corporate logo, the NORTELGlobemark, UNIFIED NETWORKS, BSC6000, S2000, S4000, S8000.GSM is a trademark of France Telecom.All other brand and product names are trademarks or registeredtrademarks of their respective holders.

Publication ReferencePE/DCL/DD/0125 411--9001--12515.54/ENMarch 2005Originated in France

For more information, please contact:

For all countries, except USA:

Documentation DepartmentParc d’activité de Magny--ChateaufortCHATEAUFORT78928 YVELINES CEDEX 9FRANCEEmail : [email protected] : (33) (1) 39--44--50--29

In the USA:

2221 Lakeside BoulevardRichardson TX 75082USATel: 1--800--4 NORTEL1--800--466--7838 or (972) 684--5935

Internet Address:

http://www.nortelnetworks.com

Date post:	21-Apr-2015
Category:	Documents
Upload:	wilson-orellana
View:	44 times
Download:	0 times

411-9001-125.15.54_OBS

Documents