Observation Counter Dictionary - KEEKLESkeekles.org/~bryan/cct/Parse data/ocd.pdf · Observation...

Wireless Service Provider Solutions

Observation Counter DictionaryPE/DCL/DD/0125 15.107/EN Standard July 2005411--9001--125

< 125 > : Observation Counter Dictionary

Wireless Service Provider Solutions

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

411--9001--125Document status: StandardDocument issue: 15.107/ENProduct release: GSM/BSS V15.1Date: July 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, 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.

Publication HistoryNortel Networks Confidential iii

Observation Counter DictionaryCopyright 2000--2005 Nortel Networks

PUBLICATION HISTORY

System release:GSM/BSS V15.1

July 2005

Issue 15.107/EN Standard

CR Q01166072: modified the Q3 name of C1720 to radioFrameUIReceived (fromabisTrauFrameUIReceived).

June 2005


Updated the descriptions of the counters pcuEdgeTdma15108s0 (15108/0) andpcuEdgeTdma15109s0 (15109/0) in section 2.9.

Updated for Feature Id 29485 V15.1.1 new counters introduction in V15.1 to avoidinterface disruption. The counters 1508, 1935, 1936, 1937, 1938, 1939, and 2096are all reserved for future use. See also the Publication History for April 2005 forIssue 15.103/EN Preliminary of this document.

Updated for Feature Id 28422 eMLPP support on a GSM network.

CR Q01157430: moved the counters 1086, 1087, and 1088 from section 2.4 tosection 2.2.

June 2005


CR Q01125865:

updated the formulas for the synthetic counters in section 2.6 (by adding thegreaterperc term where required).

reintroduced six synthetic counters in section 2.6 (8803, 8813, 9510, 9511, 9512,9600)

Removed information on BSC6000 due to EOL.

April 2005


Synchronized with 15.0.1 Standard.

Publication History Nortel Networks Confidentialiv

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

Standard 15.107/EN July 2005 Copyright 2000--2005 Nortel Networks

April 2005

Issue 15.103/EN Preliminary

CR Q01081655: updated inter--BSS handover Data Flow Diagram in section1.2.4.5, and inter--CELL intra--BSS Data Flow Diagram in section 1.2.4.4

V15.1.1 counters added, and their value is set to 0 in V15.1:

Feature Id 15347 Network synchronization: added counter 2096

Feature Id 22688AMRbased on traffic: added counters 1935, 1936, 1937, 1938,1939

Feature Id 29312 Paging capacity increase -- UI mode -- BSC 3000: addedcounter 1508

Added the following counters: 1828/0, 1828/1, 1829/0, 1934/0, 2002/0, 2002/1,2002/2, 2003/0

Integrated comments from V15.1 Draft review

Updated counter configuration list in section 1.4.1

Replaced transceiverZone/bts to bts/transceiverZone in object field of counterdescriptions

Index clean--up (phase 2)

March 2005

Issue 15.102/EN Draft

Synchronized with V15.1R Standard

Integrated late review comments from V15.0.1 Preliminary

Index clean--up (phase 1)

February 2005


Synchronized with V15.0.1 Preliminary

January 2005

Issue 15.100 /EN Draft

Feature Id 13913 ASCI Evolutions: updated counters 1193/8, 1722/0, 1722/1,2052/0, 2053/0

Publication HistoryNortel Networks Confidential v


Feature Id 25155 GPRS/EDGE Suspend and Resume:

added new counters 2066, 2067, 2068/0, 2068/1, 2071/0, 2071/1, 2072, 2073

added four new Data Flow Diagrams in new section 1.2.8 GPRS / EDGESuspend and Resume

Feature Id 25494 EDGE Features: updated counter 15076/0

Feature Id 22915 Extended UL TBF: updated counters 15123/0 and 15193/0

Feature Id 26186 PS Paging Duplication on BSC: updated counters 1506/0, 1507/0and 1507/4

Feature Id 26257 Paging Load Distribution on several LAPD: updated counters15073/0 and 15073/1

Replaced occurrences of BSC e3 by BSC 3000 and TCU e3 by TCU 3000(throughout the guide)

Looked for occurrences of End--Of--Life products (BTS S4000 Indoor 1900, BTSS4000 Outdoor 1900, BTS S4000 Smart 1900, BTS S2000 Indoor 1900 and BTSS2000E Outdoor 1900), but there was none.

SYSTEM RELEASE: GSM/BSS V15.1R

January 2005

Issue 15.53/EN

CR Q00590181: added counters 1507/5 and 1803/5 in sections 1.3.16, 2.2, 2.3.1,

Update for Customer Readiness after internal review

November 2004

Issue 15.52/EN

Synchronized with V15.0 Standard

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

counter name updates in section 1.4.1

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

Updated locators for counters 1821 to 1827

August 2004

Issue 15.51/EN

Publication History Nortel Networks Confidentialvi

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


Feature Id 20571: added section 1.2.11 for ASCI. Added counter 1193/8 in severalplaces.

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

Feature Id 26310: updated section 1.1.1.3. Added section 1.1.1.5

Feature Id 26479: added section 1.1.2.4 for BSCcounterlist size

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

Reorganized Appendix for V15.x evolutions

Publication HistoryNortel Networks Confidential vii


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


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.

Publication History Nortel Networks Confidentialviii

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


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

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.

Publication HistoryNortel Networks Confidential ix


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


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

March 2004


For CR Q00835972--01, deleted information concerning the 1835cardSynthLoadBscbMoy/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

Publication History Nortel Networks Confidentialx

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


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

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,

Publication HistoryNortel Networks Confidential xi


Checked the S12000 introduction impact on this NTP.

Taken into account:

CR Q00685162

CR Q00686958

CR Q00184739

CR Q00185002

CR Q00182988

April 2003


Taken into account:

internal comments

CR Q00548005 (correction, counters 15028/1 and 15030/1)

CR Q00566940 (correction, Annex of the document)

CR Q00581808 (counters 15005/0 and 15005/1)

CR Q00581804 (counters 15005/0 and 15005/1)

CR Q00614305 (counters 1606, 1607, 1608, 1701, 1609, 1611, 1613, 1700)

January 2003


Taken into account:

CR Q00411337

CR Q00548005

CR Q00500889

CR Q00470148

CR Q00431517

CR Q00431468

CR Q00389797

CR Q00252063

CR Q00252054

CR Q00208602

CR Q00583446

CR Q00582009

CR Q00566940

Publication History Nortel Networks Confidentialxii

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


December 2002


Update for V14.3 system release (BSS)

IPO counters in paragraph 1.5.4.1 have been removed

Mentions to instrument panel in paragraph 1.7.1 and 1.7.3 have been removed

ORT has been changed in IPO for the counter no. 9600 in paragraph A3.1

November 2002


Update for V14.3 system release (BSS)

The following features have been taken into account:

BSC e3 counters (22526)

AR 1209--6 BSC e3 observation counters (22673)

The following modifications have been made to the manual:

chapter 1 Introduction:

The following counters have been added:

all 19xx counters (refer to paragraph 1.5.2, 1.5.3 and 1.5.4.1--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


Publication HistoryNortel Networks Confidential xiii


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

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

Publication History Nortel Networks Confidentialxiv

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


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

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

Publication HistoryNortel Networks Confidential xv


15031/2 dlTBFAllocFailure

15031/3 dlTBFRadioFailure

15032/3 ulsecondPhaseAllocFailure

15034/0 PDANWithUlReq

15036/0 ulsecondPhaseRadioFailure

15041/0 upUserdatablocks

15043/0 RequestedRetransmittedDataBlocksDN

15058/4 dnPipebetween22and33kbps

15061/0 upPipeless11kbps

June 2002


March 2002


Changed to Standard -- minor editorial update

August 2001


V13.1 release update after internal review

The following changes were made in individual chapters:

About this document

updated Paragraph Applicability

updated Paragraph How this document is organized


updated Paragraph 1.1.1.1 Observation types

removed Paragraph 1.4 Instrument panel observation counters(V10)

removed Paragraph 1.5.2 PCM links

removed Paragraph 1.5.3 Handovers

updatedParagraph 1.6.2.1 Rawpermanent counters settable by theoperator

created new Paragraph 1.6.3 Correspondence between BSC 2G and BSC e3Counters

Publication History Nortel Networks Confidentialxvi

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


updated Paragraph 1.7.2.1 Counter numbering

updated Paragraph 1.7.3 Counter definition

Chapter 2 Counter description

removed Paragraph 2.2 Raw instrument panel counters

removed Paragraph 2.4.3 Temporary PCM observation

removed Paragraph 2.4.4 Temporary Handover observation

removed Paragraph 2.6 Synthetic instrument panel (IPO and ORT)counters

updated the Function and Event fields of the counters 15057/0 to 15057/4

updated the Function and Event fields of the counters 15058/0 and 15058/1

created the new counters 15075/0 to 15075/4, and 15076/0 to 15076/1

July 2001




updated Paragraph 1.1.1.1 Observation types with completion of the 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

Publication HistoryNortel Networks Confidential xvii



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 counterswith integration of the counters3000/n to 3008/n

System release: GSM/BSS V12

July 2001




integrated the following data flow diagrams (DFDs):

Immediate assignment: paging (normal completion), Paragraph 1.2.2.2 Dedicated channel assignment: mode modify, Paragraph 1.2.3.2 Intra--bts handover (normal completion), Paragraph 1.2.4.3

Inter--bss handover (normal completion), Paragraph 1.2.4.5

Direct retry handover, Paragraph 1.2.4.6

Radio channel release (DEACTIVATE SACCH ACK received 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 countersccpResourceFailureBscFailure by sccpResourceFailureBscRefusal

updated Paragraph 2.8.2:

Publication History Nortel Networks Confidentialxviii

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


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

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

Publication HistoryNortel Networks Confidential xix


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

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

Publication History Nortel Networks Confidentialxx

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


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

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

Publication HistoryNortel Networks Confidential xxi


June 2000




Updated 10 counters (1028, 1029, 1030, 1031, 1163/16, 1163/17, 1164/16,1164/17, 1604, 1605)


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

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

Publication History Nortel Networks Confidentialxxii

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


PAGE INTENTIONALLY LEFT BLANK

Table of contentsNortel Networks Confidential xxiii


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 GPRS/EDGE Suspend and Resume 1--142. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.9 BSC equipment 1--152. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.10 PCUSN 1--153. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.11 Advanced Speech Call Items (GSM--R) 1--211. . . . . . . . . . . . . . . . . . . . . . . . . .

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

1.3.1 Counter classes 1--215. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

1.3.3 Radio resource allocation 1--215. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.4 Interferences 1--218. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.5 Call setup 1--220. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.6 Dedicated channel assignment 1--220. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.7 Directed retry handovers 1--222. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.8 Handovers 1--223. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.9 Radio resource release 1--228. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of contents Nortel Networks Confidentialxxiv

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


1.3.10 SMS service 1--231. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.11 Layer 1 management 1--232. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.12 A interface 1--232. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.13 Abis interface 1--233. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

1.3.15 PCM links 1--233. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.16 BSC equipment 1--234. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.17 GPRS 1--235. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.18 GPRS / EDGE Suspend and Resume 1--237. . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.19 ASCI (GSM--R V12, V15) 1--237. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4 Raw permanent BSS counters configuration 1--239. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4.1 Raw counters configuration (all BSC) 1--239. . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4.2 Correspondence between BSC2G and BSC 3000 counters 1--268. . . . . . . . .

1.5 Synthetic permanent BSS counters configuration 1--270. . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.6 Temporary observation counters (BSC 2G) 1--274. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.6.1 SS7 links 1--274. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.6.2 Abis interface 1--275. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.7 Raw Permanent PCUSN Observation Counters 1--276. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.7.1 PCUSN Observation Classes 1--276. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.7.2 PCUSN Observation Types 1--278. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.7.3 Throughput Counters and Satisfaction Rate Counters 1--285. . . . . . . . . . . . . .

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

2.3 Raw permanent BSS counters (BSC 3000, AMR) 2--28. . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.1 Raw permanent BSS counters (BSC 3000) 2--28. . . . . . . . . . . . . . . . . . . . . . .

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

2.4 Raw permanent BSS counters (common to BSC 2G, BSC 3000, and AMR) 2--102. . . .

2.5 Raw temporary counters (odiag excluded) 2--460. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.1 Temporary Interference observation 2--460. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.2 Temporary SS7 link observation 2--460. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of contentsNortel Networks Confidential xxv


2.5.3 Temporary Abis interface observation 2--463. . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.6 Synthetic permanent BSS counters 2--472. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.7 Raw permanent md counters 2--529. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.7.1 SYBASE counters 2--529. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.7.2 SCSE counters 2--533. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.7.3 UNIX counters 2--534. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.7.4 Q3 counters 2--539. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.8 Raw permanent manager counters 2--552. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.8.1 SYBASE counters 2--552. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.8.2 X.25 counters 2--556. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.8.3 UNIX counters 2--557. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.9 Raw permanent PCUSN counters 2--561. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

List of figures Nortel Networks Confidentialxxvi

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


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

Figure 1--2 Observation Classes 1--277. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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 the V15.1 BSS system release.

This document is part of the BSS Nortel Networks Technical Publications (NTPs).

It is closely associated 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.

Some GSM--R specific counters listed in this dictionary contain (GSM--R V12)in the Feature field because they were introduced in V12.

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.6) 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.4.

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

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 3000

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 (synthetic counters)

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: #

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 3000V14.3 300 1500

BSC 3000V15 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 < BSC memoryTHRESHOLD

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



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

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 0011191/2 for cause 0101191/3 for cause 0111191/4 and 1730 for cause 1001191/5 for cause 1011191/6 for cause 1101191/7 for cause 111

(2) Since V9 releases, the following modifications have been performed:1606 instead of 10341607 instead of 10351609 instead of 10511611 instead of 1052

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

11071501DTAP (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

START_MEASUREMENT_REQ_ACKDTAP (SETUP)

11071501DTAP (SETUP)

DTAP (ALARTING)

SETUP

ALERTINGDTAP (ALARTING)

11081500

17501193/n1195 or 1196




1191/0 for cause 000

1191/1 and 1730 for cause 001



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


Counternumber


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]


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


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


Counternumber


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

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

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

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



1611/2 TchFrAveragedUsedOverflowAllocationTrZoneMoy/Max/Cum/Ech

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





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

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




Counternumber



number of successful immediateassignments

1750 estabIndicSignalling number of ESTABLISH INDICATIONmessages in establishment phasereceived

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

1748 channelRequest number of channel allocation requests1751 immediateAssignmentReject number of immediate assignments

rejected


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


rejected

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




1751 immediateAssignmentReject number of immediate assignmentsrejected



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/0ACTIVATE_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 phaseand 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


rejected


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


CONNECTION FAILURE indication

Data Flow Diagram: immediate assignment failure procedure: connection failureindication

MS BTS BSC MSC

11081502

CONNECTION_REQUEST(L3_INFORMATION

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

(1) The following counters are incremented depending on the cause value in theCHANNEL REQUIR

Observation Counter Dictionary - KEEKLESkeekles.org/~bryan/cct/Parse data/ocd.pdf · Observation...

Documents

Transcript of Observation Counter Dictionary - KEEKLESkeekles.org/~bryan/cct/Parse data/ocd.pdf · Observation...