NOKIA_2G_BSS Network Doctor User Guide

NOKIA NMS/2000 FOR MANAGING CELLULAR NETWORKS

BSS NETWORK DOCTOR

User's Guide

Document number/Issue

NTC TAN 0935/2.3 en

Copyright © Nokia Telecommunications Oy

1

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia Telecommunications' customers only for the purposes of the agreement under which the document is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia Telecommunications. Telecommunications. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Telecommunications welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this document concerning the suitability, suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia Telecommunications and the customer. However, Nokia Telecommunications has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Telecommunications will, if necessary, explain issues which may not be covered by the document. Nokia Telecommunications' Telecommunications' liability for any errors in the document is limited to the documentary correction of errors. Nokia Telecommunications WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the information in it. This document and the product it describes are considered protected by copyright according to the applicable laws. NOKIA logo is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective companies, and they are mentioned for identification pur poses only. Copyright © Nokia Telecommunications Telecommunications Oy 1999. All rights reserved.

No. of pages 201/JRi

Edited by

Author

Approved by

J Rissanen 18 August 1999


R Roppo 18 August 1999

Previous issue (2.2) approved 5 March 1999

Copyright © Nokia Telecommunic Telecommunications ations Oy 1999. All rights reserved. reserved.


NTC TAN 0935/2.3 en

Copyright © Nokia Telecommunications Telecommunications Oy

2

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia Telecommunications' customers only for the purposes of the agreement under which the document is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia Telecommunications. Telecommunications. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Telecommunications welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this document concerning the suitability, suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia Telecommunications and the customer. However, Nokia Telecommunications has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Telecommunications will, if necessary, explain issues which may not be covered by the document. Nokia Telecommunications' Telecommunications' liability for any errors in the document is limited to the documentary correction of errors. Nokia Telecommunications WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the information in it. This document and the product it describes are considered protected by copyright according to the applicable laws. NOKIA logo is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective companies, and they are mentioned for identification pur poses only. Copyright © Nokia Telecommunications Telecommunications Oy 1999. All rights reserved.

No. of pages 201/JRi

Edited by

Author

Approved by



R Roppo 18 August 1999

Previous issue (2.2) approved 5 March 1999

Copyright © Nokia Telecommunic Telecommunications ations Oy 1999. All rights reserved. reserved.


NTC TAN 0935/2.3 en


2

TABLE OF CONTENTS 1

WHAT WHAT IS NEW. NEW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.1 1.2 1.3

2

ABOU ABOUT T THI THIS S MAN MANUA UAL L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.1 2.2 2.3

2.4

3

10 10 11 11 12 12 12 13

Prereq Prerequis uisite itess for for the Effect Effective ive Analys Analysis is of of the Networ Network k . . . . . . . . . . . . . . 16 Monito Monitorin ring g the the Quali Quality ty of of a Cellu Cellular lar Netw Network. ork. . . . . . . . . . . . . . . . . . . . . . 17 Report Reporting ing Proced Procedure uress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.3. 3.3.1 1 Perfo Perform rman ance ce Indi Indica cato torr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

USIN USING G BSS BSS NETW NETWOR ORK K DOC DOCTO TOR R . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 4.1

5

What What You You Need Need to to Know Know Firs First. t. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where Where to to Find Find More. More. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typogr Typograp aphic hic Conven Conventio tions ns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3. 2.3.1 1 Text Text Sty Style less . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3. 2.3.2 2 Comm Comman and d Lin Linee Con Conve vent ntio ions ns . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terms Terms and and conc concept eptss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4. 2.4.1 1 Abbr Abbrev evia iati tion onss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4. 2.4.2 2 Term Termss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INTR INTROD ODUC UCTI TIO ON TO TO BS BSS NET NETW WORK ORK DOC DOCTO TOR R . . . . . . . . . . . . . . 16 3.1 3.2 3.3

4

In This This Functi Functiona onalit lity y Note Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 In the the Previo Previous us Functi Functiona onality lity Note Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Suppor Supported ted Functi Functions ons.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Naviga Navigatin ting g with with Repo Reports rts,, Formu Formulas las and Counte Counters rs . . . . . . . . . . . . . . . . . . . 21

USER USER INTE INTERF RFAC ACE E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.1 5.2

5.3 5.4

Report Report Layo Layout. ut. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Focusi Focusing ng your your Report Report Sele Selecti ction on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.2. 5.2.1 1 BTS BTS Are Areaa Sel Selec ectio tion n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.2. 5.2.2 2 Area Area Sele Select ctio ion n Bas Based ed on a Mai Maint nten enan ance ce Regi Region on (MR) (MR) . . . . . . . . 25 5.2. 5.2.3 3 Area Area Sele Select ctio ion n bas based ed on a BSC BSC . . . . . . . . . . . . . . . . . . . . . . . . . . 26 5.2. 5.2.4 4 Time Time Peri Period od Sele Select ctio ion n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 User User Log. Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Report Report Menu Menuss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 5.4. 5.4.1 1 Faul Faultt Mana Manage geme ment nt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 5.4. 5.4.2 2 Conf Config igur urat atio ion n Man Manag agem emen entt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 5.4.2. 5.4.2.1 1 Find Find Cell Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 5.4.2. 5.4.2.2 2 Checks Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 5.4.2. 5.4.2.3 3 Adjace Adjacenci ncies es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 5.4.2. 5.4.2.4 4 Named Named Para Paramet meter er Set Set Audi Audit. t. . . . . . . . . . . . . . . . . . . . . . 31 5.4.2. 5.4.2.5 5 Netwo Network rk Enti Entitie tiess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 5.4.2. 5.4.2.6 6 Freque Frequenci ncies es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 5.4.2. 5.4.2.7 7 Cell Cell Cove Coverag rage. e. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 5.4. 5.4.3 3 Perfo Perform rman ance ce Mana Manage geme ment nt BSS BSS . . . . . . . . . . . . . . . . . . . . . . . . . . 32 5.4.3. 5.4.3.1 1 PM Admi Adminis nistra tratio tion n . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32


NTC TAN 0935/2.3 en


3

5.4. 5.4.4 4

6

32 33 33 33 34 34 35 35 35 35

ACTI ACTION ONS S TO TO TAK TAKE E BEF BEFOR ORE E USI USING NG TH THE E REP REPOR ORT TS . . . . . . . . . 37 6.1

6.2 6.3

6.4 6.5 6.6

6.7 6.8

7

5.4.3. 5.4.3.2 2 SDCCH SDCCH and and TCH TCH Acce Access, ss, Availa vailabil bility ity . . . . . . . . . . . . . 5.4.3. 5.4.3.3 3 Hando Handove verr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.3. 5.4.3.4 4 Drop Drop Call Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.3. 5.4.3.5 5 Traf Traffic fic and and Load. Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.3. 5.4.3.6 6 Interf Interfere erence nce,, Quali Quality ty and and Link Link Balanc Balancee . . . . . . . . . . . . . 5.4.3. 5.4.3.7 7 IUO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.3. 5.4.3.8 8 Call Call Succe Success ss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.3. 5.4.3.9 9 BSS Transmi ransmissi ssion on Ava Availa ilabil bility ity and and Qual Quality ity . . . . . . . . . 5.4.3.10 5.4.3.10 Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Benc Benchm hmar ark k and and Anal Analys ysis is . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Checki Checking ng the the PLMN PLMN Object. Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 6.1. 6.1.1 1 PLMN PLMN Obje Object ct Name Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 6.1. 6.1.2 2 PLMN PLMN Obj Objec ectt Inst Instan ance ce.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Checki Checking ng a BTS BTS Objec Objectt Insta Instance nce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Estima Estimatin ting g the the Load Load on on the the NMS/2 NMS/2000 000 . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 6.3. 6.3.1 1 Load Load on the the NMS NMS/2 /200 000 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 6.3. 6.3.2 2 Activ Activee Mea Measu sure reme ment ntss in the the BSC BSC . . . . . . . . . . . . . . . . . . . . . . . . 38 6.3.2. 6.3.2.1 1 How How to Chec Check k Which Which Measur Measureme ements nts Are Activ Activee . . . . . 39 6.3.2.2 6.3.2.2 How to See See What What Measure Measurements ments Send Data to the Database. Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 6.3.2. 6.3.2.3 3 How How to See See Whic Which h BSCs BSCs Send Send Data Data to the Databa Database se . . 42 6.3.2. 6.3.2.4 4 How How to Set the Measur Measureme ements nts . . . . . . . . . . . . . . . . . . . . 42 6.3. 6.3.3 3 Meas Measur urem emen entt Flow Flow from from a BSC BSC.. . . . . . . . . . . . . . . . . . . . . . . . . . 46 Checki Checking ng Observ Observati ations ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Checki Checking ng Bloc Blocked ked or Filte Filtered red Alarms Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Checki Checking ng the the Main Mainten tenanc ancee Regio Region n Assig Assignme nments. nts. . . . . . . . . . . . . . . . . . . . 49 6.6. 6.6.1 1 Usin Using g the the Main Mainte tena nanc ncee Reg Regio ions ns for for Repo Reporti rting ng . . . . . . . . . . . . . . 49 6.6. 6.6.2 2 Comm Common on Mista Mistake kess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 6.6. 6.6.3 3 How How to to See See the the MR MR Div Divis isio ion n . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 6.6. 6.6.4 4 How How to Find Find Erro Errors rs in in Ass Assig ignm nmen ents. ts. . . . . . . . . . . . . . . . . . . . . . . 52 Settin Setting g the the Histo History ry Wind Windows ows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Settin Setting g up the Base Base Stati Station on Grou Groups ps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 6.8. 6.8.1 1 Defin Definin ing g Gro Group upss by by BSS BSS Netw Networ ork k Doc Docto torr Gro Group up Mana Manage geme ment nt . 54 6.8. 6.8.2 2 Defin Definin ing g Gro Group upss by by Wor Worki king ng Set Set Mana Manage gerr . . . . . . . . . . . . . . . . . 54

CONS CONSIS ISTE TENC NCY Y CHE CHECK CKS S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8

Adjace Adjacenci ncies es to to Non-e Non-exis xistin ting g Cells Cells.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adjace Adjacency ncy Discre Discrepan pancie ciess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-sy Non-symme mmetri trical cal Adjac Adjacenc encies ies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Same Same or or Adjac Adjacent ent Frequ Frequenc encies ies in the the Adja Adjacen centt Cells Cells . . . . . . . . . . . . . . . . Handov Handover er Sync Synchro hronis nisati ation on Betw Between een Adjac Adjacent ent Cells Cells . . . . . . . . . . . . . . . . . Adjace Adjacent nt Cell Cell Doubl Doublee Frequ Frequenc ency y Chec Check k . . . .. . . .. . . .. . . .. . . .. . . .. . Non-un Non-uniqu iquee CI and and LAC LAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Base Stati Station on Audi Auditt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.8. 7.8.1 1 Area Area Leve Levell Coun Counts ts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.8. 7.8.2 2 BTS BTS Lev Level el Dev Devia iati tion onss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


NTC TAN 0935/2.3 en


56 56 58 58 59 61 62 62 62 64

4

7.9 Checki Checking ng the Adjac Adjacenc ency y Plan Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 7.10 Checking Checking the the Frequen Frequency cy Plan. Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 7.11 Checking Checking the Adminis Administrativ trativee States States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

8

QUAL QUALIT ITY Y OF OF THE THE RADI RADIO O NET NETWO WORK RK PLAN PLAN . . . . . . . . . . . . . . . . 75 8.1

8.2

8.3

8.4

9

CELL CELL DIME DIMENS NSIO IONI NING NG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 9.1 9.2 9.3

9.4

9.5

9.6

10

SDCCH SDCCH Drop Drop Ratio Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 8.1. 8.1.1 1 SDCC SDCCH H Dro Drop p Rat Ratio io on on Are Areaa Lev Level el . . . . . . . . . . . . . . . . . . . . . . . 76 8.1. 8.1.2 2 SDCC SDCCH H Dro Drop p Rat Ratio io on on BTS BTS Hit Hit Lis List. t. . . . . . . . . . . . . . . . . . . . . . 77 8.1. 8.1.3 3 SDCC SDCCH H Dro Drop p Rat Ratio io on BTS BTS Lev Level el . . . . . . . . . . . . . . . . . . . . . . . 78 TCH Drop Drop Call Call Rati Ratio o . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 8.2. 8.2.1 1 TCH TCH Dro Drop p Cal Calll Rat Ratio io on Area Area Leve Levell . . . . . . . . . . . . . . . . . . . . . . 79 8.2. 8.2.2 2 TCH TCH Dro Drop p Cal Calll Rat Ratio io on BSC BSC Lev Level el . . . . . . . . . . . . . . . . . . . . . . 81 8.2. 8.2.3 3 TCH TCH Dro Drop p Cal Calll Rat Ratio io on BTS BTS Hit Hit List List . . . . . . . . . . . . . . . . . . . . 82 8.2. 8.2.4 4 TCH TCH Dro Drop p Cal Calll Rat Ratio io on on BTS BTS Leve Levell . . . . . . . . . . . . . . . . . . . . . . 83 8.2. 8.2.5 5 TCH TCH Obs Obser erva vati tion on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Handov Handover er Fail Failure ure Ratio Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 8.3. 8.3.1 1 Hand Handov over er Fai Failu lure re Ratio Ratio on BTS BTS Are Areaa Lev Level el . . . . . . . . . . . . . . . . 85 8.3. 8.3.2 2 Hand Handov over er Fai Failu lure re Ratio Ratio on BTS BTS Hit Hit Lis Listt Leve Levell . . . . . . . . . . . . . . 88 8.3. 8.3.3 3 Hand Handov over er Fai Failu lure re Ratio Ratio on Adja Adjace cenc ncy y Hit Hit Lis Listt Leve Levell . . . . . . . . . 89 8.3. 8.3.4 4 Hand Handov over er Failu Failure re Ratio Ratio on BTS BTS Lev Level el . . . . . . . . . . . . . . . . . . . . 89 Locati Location on Upda Update te Succ Success ess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 8.4. 8.4.1 1 Loca Locatio tion n Upd Updat atee Suc Succe cess ss on BSC BSC Lev Level el . . . . . . . . . . . . . . . . . . . 93

Findin Finding g the the Exist Existing ing Dimens Dimension ioning ing Proble Problems ms in in the the Netwo Network rk . . . . . . . . . 94 Findin Finding g the the Futur Futuree Dime Dimensi nsioni oning ng Prob Problem lemss in the Networ Network k . . . . . . . . . . . 94 SDCCH SDCCH Cong Congest estion ion and Blocki Blocking. ng. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 9.3. 9.3.1 1 SDCC SDCCH H Con Conge gest stio ion n and and Bloc Blocki king ng on Area Area Leve Level. l. . . . . . . . . . . . 94 9.3. 9.3.2 2 SDCC SDCCH H Con Conge gest stio ion n and and Bloc Blocki king ng on BTS BTS Hit Hit List List . . . . . . . . . . 95 9.3. 9.3.3 3 SDCC SDCCH H Con Conge gest stio ion n and and Bloc Blocki king ng on BTS BTS Lev Level el . . . . . . . . . . . . 96 TCH Conges Congestio tion n and and Block Blocking ing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 9.4. 9.4.1 1 TCH TCH Con Conge gest stio ion n on on Are Areaa Lev Level el.. . . . . . . . . . . . . . . . . . . . . . . . . . 98 9.4. 9.4.2 2 TCH TCH Con Conge gest stio ion n and and Bloc Blocki king ng on BTS BTS Hit Hit Lis Listt . . . . . . . . . . . . . 99 9.4. 9.4.3 3 TCH TCH Con Conge gest stio ion n and and Bloc Blocki king ng on BTS BTS Lev Level el.. . . . . . . . . . . . . . 101 101 Traffic. Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 9.5. 9.5.1 1 Hour Hourly ly Tra Traff ffic ic on on BSC BSC Leve Level. l. . . . . . . . . . . . . . . . . . . . . . . . . . . 102 102 9.5. 9.5.2 2 Traf Traffi ficc on on Are Areaa Lev Level. el. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 103 9.5. 9.5.3 3 Traf Traffi ficc on on BTS BTS Hit Hit Lis Listt Lev Level el . . . . . . . . . . . . . . . . . . . . . . . . . . 105 105 9.5. 9.5.4 4 Traf Traffi ficc on on BTS BTS Leve Levell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 106 Miscel Miscellan laneo eous. us. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

CALL CALL SUCCE SUCCESS. SS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 112 10.1 Traffic Traffic Channel Channel Access Access and Succes Successs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

11

TRAN TRANSM SMIS ISSI SION ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 115

12

NETW NETWOR ORK K ELE ELEME MENT NT AVAI AVAILA LABI BILI LITY TY . . . . . . . . . . . . . . . . . . . . 121 121 12.1 Availabilit Availability y of Transc Transceiver eiverss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121


NTC TAN 0935/2.3 en


5

12.1.1 12.1.1 Availa Availabil bility ity of Tran Transc sceiv eivers ers on BSC BSC Leve Levell . . . . . . . . . . . . . . . . 121 12.2 Availabilit Availability y of Timesl Timeslots ots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 12.2.1 12.2.1 Availa Availabil bility ity of SDCC SDCCH H and and TCH TCH on on Area Area Leve Levell . . . . . . . . . . . 122 12.2.2 12.2.2 Availa Availabil bility ity of Time Time Slots Slots on on BTS BTS Hit Hit List List . . . . . . . . . . . . . . . . 122 12.2.3 12.2.3 Availa Availabil bility ity of SDCC SDCCH H and and TCH TCH on on BTS BTS Level. Level. . . . . . . . . . . . 123 12.3 BSC Units. Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

13

INTE INTERF RFER EREN ENCE CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 125 13.1 Uplink Uplink Interfere Interference nce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.1.1 13.1.1 Uplink Uplink Interf Interfere erenc ncee on Area Area Leve Levell . . . . . . . . . . . . . . . . . . . . . . 13.1.2 13.1.2 Uplink Uplink Interf Interfere erenc ncee on BTS Hit List List . . . . . . . . . . . . . . . . . . . . . 13.1.3 13.1.3 UL Inte Interfe rferen rence ce on on BTS BTS Level Level.. . . . . . . . . . . . . . . . . . . . . . . . . . 13.2 Interferen Interference ce from from the Same or Adjacen Adjacentt Frequenc Frequencies ies . . . . . . . . . . . . . . .

14

125 125 126 129 130

INTE INTELL LLIG IGEN ENT T UND UNDER ERLA LAYY-OV OVER ERLA LAY Y . . . . . . . . . . . . . . . . . . . . 132 132 14.1 Intelligen Intelligentt UnderlayUnderlay-Overl Overlay ay on Area Level Level . . . . . . . . . . . . . . . . . . . . . . 132 14.2 Intelligen Intelligentt UnderlayUnderlay-Overl Overlay ay on BTS Level Level . . . . . . . . . . . . . . . . . . . . . . 133

15

NETW NETWOR ORK K CON CONFIG FIGURA URATI TION ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 141 15.1 15.2 15.3 15.4 15.5 15.5 15.6

16

141 143 145 147 147 148

ALAR ALARMS MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 152 16.1 16.2 16.3 16.4 16.5 16.5

17

Network Network Configura Configuration tion Summa Summary ry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC Option Option Statistics. Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Network Entities. Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC and and BCF BCF Software Software Deploymen Deployment. t. . . . . . . . . . . . . . . . . . . . . . . . . . . . BCF Harwar Harwaree Type Type Deplo Deployme yment nt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequencie Frequenciess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alarm Types Types and Counts Counts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm statistics. statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm Statistics Statistics per per Cell Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Active Active BCCH BCCH Missing Missing Alarms. Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Alarm Alarm Sum Sum Time Time by Cell Cellss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

152 154 155 155 155

LOCAT LO CATING ING NETW NETWOR ORK K ELE ELEME MENT NTS S . . . . . . . . . . . . . . . . . . . . . . . 157 157 17.1 17.2 17.2 17.3 17.4 17.4 17.5 17.5

All Base Base Station Station Sites per Mainte Maintenanc nancee Region Region . . . . . . . . . . . . . . . . . . . All cell cellss with with LAC LAC and and CI CI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BS Sites Sites Having Having the Given Given Chara Character cter String String in the Name. . . . . . . . . . . . Cells Cells Havin Having g the Given Given CI and and LAC LAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cells Cells Havin Having g an Adja Adjace cent nt Cell Cell with with the the Given Given CI CI and LAC . . . . . . . . . .

157 157 157 158 158

18

NAME NAMED D SETS SETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 160

19

OTHE OT HER R MEA MEASU SURAB RABLE LE QUAL QUALIT ITIE IES S . . . . . . . . . . . . . . . . . . . . . . . 162 162 19.1 Uplink Uplink and Downlink Downlink Quality Quality and and Level Level . . . . . . . . . . . . . . . . . . . . . . . . . 19.1.1 19.1.1 Uplink Uplink and and Downl Downlink ink Quality Quality on Area Area Level Level . . . . . . . . . . . . . . 19.1.1.1 19.1.1.1 Reports Reports Based Based on RX RX Quality Quality . . . . . . . . . . . . . . . . . . . 19.1.1.2 19.1.1.2 Reports Reports Based Based on on RX-lev RX-level el Statistic Statisticss . . . . . . . . . . . . . 19.1.2 19.1.2 Uplink Uplink and and Down Downlin link k Qual Quality ity on TRX Hit List List . . . . . . . . . . . .


NTC TAN 0935/2.3 en


162 162 162 163 164 6

19.2

19.3 19.4

19.5

19.6

19.7 19.8

20

19.1.2.1 19.1.2.1 Reports Reports Based Based on RX RX Quality Quality . . . . . . . . . . . . . . . . . . . 164 19.1.2.2 19.1.2.2 Reports Reports Based Based on on RX-lev RX-level el Statistic Statisticss . . . . . . . . . . . . . 164 19.1.3 19.1.3 Uplink Uplink and and Downl Downlink ink Quality Quality on BTS BTS Lev Level el . . . . . . . . . . . . . . 165 19.1.3.1 19.1.3.1 Reports Reports Based Based on RX RX Quality Quality . . . . . . . . . . . . . . . . . . . 165 19.1.3.2 19.1.3.2 Reports Reports Based Based on RX RX level level Statist Statistics. ics. . . . . . . . . . . . . . 166 Link Balance Balance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 19.2.1 19.2.1 Link Link Balan Balance ce on Area Area Level Level . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 19.2.2 19.2.2 Link Link Balan Balance ce on on BTS BTS Hit List List . . . . . . . . . . . . . . . . . . . . . . . . . . 169 19.2.3 19.2.3 Link Link Balan Balance ce on on BTS BTS Leve Level. l. . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 MS Speed Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Cell Cover Coverage. age. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 19.4.1 19.4.1 Domina Dominant nt Dist Distanc ancee Rang Rangee on on BTS BTS List. List. . . . . . . . . . . . . . . . . . . 173 19.4.2 19.4.2 Distan Distance ce Ranges Ranges on BTS Hit List List . . . . . . . . . . . . . . . . . . . . . . . 174 19.4.3 19.4.3 Distan Distance ce Rang Rangee Distr Distribu ibutio tion n on BTS Level. Level. . . . . . . . . . . . . . . . 175 Handover Handover Cause Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 19.5.1 19.5.1 Handov Handover er Caus Causee on Area Area Leve Levell . . . . . . . . . . . . . . . . . . . . . . . . . 176 19.5.2 19.5.2 Handov Handover er Caus Causee on BTS Hit List List . . . . . . . . . . . . . . . . . . . . . . . 176 19.5.3 19.5.3 Handov Handover er Caus Cause, e, BTS BTS Leve Levell . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 BSC Clear Clear Codes Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 19.6.1 19.6.1 BSC Clear Clear Code Codess on on Netwo Network rk Leve Levell . . . . . . . . . . . . . . . . . . . . . 179 19.6.2 19.6.2 BSC Clear Clear Code Codess on on BSC BSC Level Level . . . . . . . . . . . . . . . . . . . . . . . . 182 Troublesho Troubleshooting oting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Dual Band. Band. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

BENCH BE NCHMAR MARK K AND AND ANAL ANALYS YSIS IS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 188 20.1 20.2 20.3 20.4 20.4 20.5 20.6 20.7

Performanc Performancee statistic statisticss (benchma (benchmark) rk) (200) (200) . . . . . . . . . . . . . . . . . . . . . . . . 188 Network Network benchma benchmark rk statistic statisticss (204). (204). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Performanc Performancee profiles profiles for area, area, 24-hour/1 24-hour/10-day 0-day breakdown breakdownss (207) (207) . . . . . 189 Quality Quality surve survey y (800) (800) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Cell docto doctorr (213) (213) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Cell analy analyser ser (216) (216) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Base station station site check check (221) (221) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

INDEX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194


NTC TAN 0935/2.3 en


7

What is new

1

WHAT IS NEW

1.1

In This Functionality Note As a result of the changes made between BSS Network Doctor software versions 10.4.(x) and 10.5, the following changes have been made into this document: New reports

The following reports have been added: •

Benchmark and Analysis menu -

Quality survey (800)

Updated reports

The following reports have been updated, meaning that some of the counters and formulas used for generating the report data have changed. •

1.2 1.2

063, 063, 073, 073, 163, 163, 199, 199, 200, 200, 204, 204, 208, 208, 250, 250, 403, 403, 404, 404, 407 407

In th thee Pre Previ viou ouss Fun Funct ctio ion nalit ality y Not Notee As a result of the changes made between BSS Network Doctor software versions 10.2 and 10.4.(x), the following changes were made into this document: New menus

In the main menu, the following new submenus were added: •

Benchmark and Analysis This menu contains all the reports that were formerly under the Performance Management BSS/Doctors menu, as well as some reports from the Performance Management BSS/Other menu.

•

User Log This menu contains reports for monitoring user log data.

New reports

The following reports were added: •

Perfo Perform rman ance ce Man Manag agem emen entt BSS/ BSS/In Inte terfe rfere renc nce, e, Qua Quali lity ty and and Lin Link k Bala Balanc ncee menu -

Cells by do domina inant lin link k ba balance (1 (198)

-

Link balance of an area (199)


NTC TAN 0935/2.3 en


8

What is new

•

Performance Management BSS/IUO menu -

IUO measurement data per BTS (404)

-

C/I statistics (407)

The following new submenu has been added in the main menu: •

User log, containing reports: -

Log statistics (512)

-

Network Doctor use statistics (513)

Shortcuts to generating reports

Each submenu contains a shortcut for running any of the BSS Network Doctor reports. In this way you can flexibly have access to any of them regardless of which menu you are currently viewing. Enter the report ID after m) for viewing a model report and after r) for generating an actual report from the database. User log

BSS Network Doctor provides you with reports for monitoring the user log data from the use of this application. These log reports are common to both BSS and NSS Network Doctor application

1.3

Supported Functions There may be some minor differences between the formulas presented here and the formulas that BSS Network Doctor is using. This version of BSS Network Doctor makes full use of the new S6 functions.


NTC TAN 0935/2.3 en


9

About This Manual

2

ABOUT THIS MANUAL This document explains the functional usage of the BSS Network Doctor software, the emphasis being on the practical tasks. The document does not introduce all reports available in BSS Network Doctor but focuses on the most useful ones. The information contained in this document relates to Nokia NMS release T10 and to release S6 of the Nokia BSC software. This document should not be used with any other versions of the Nokia NMS/2000 or Nokia BSC software. The formulas used in the reports can be subject to changes without notice. This document is intended for the network operators of the Nokia NMS/2000. This chapter covers the following topics:

2.1

•

What you need to know first

•

Where to find more

•

Typographic conventions

•

Terms and concepts

What You Need to Know First This document assumes that you are familiar with the following areas:

2.2

•

The concepts of the Nokia NMS/2000 and GSM networks in general

•

The usage of the UNIX operating system and file system navigation

•

The system administration tasks of the UNIX operating system. An overview of the responsibilities of the system administrator can be found in the HP-UX System Administration Concepts.

•

A text processing utility, such as vi or dtpad. These text processors are used for editing certain configuration files.

Where to Find More When you perform the user’s tasks described in this document, you may need to refer to other documentation for further information. Below is a list of manuals that you will find useful, as well as a brief description of the manual’s contents. BSS Network Doctor Documentation

•

BSS Network Doctor, Feature Overview, TAN 0932, for a brief overview on the application


NTC TAN 0935/2.3 en


10

About This Manual

•

BSS Network Doctor, System Administrator’s Guide, TAN 0934, for administrator’s tasks related to running BSS Network Doctor

•

BSS Network Doctor Formulas, Reference Guide, TAN 0936, for counter formulas.

Other Nokia Documents

2.3

•

Performance Management Basic Operating Principles and Procedures, TAN 0726, for a description of the formulas used in the Measurement Data Post-processing in PC application.

•

Database Description for BSC Measurements, TAN 0422, for information on NMS database counters.

•

Call related DX causes in BSC, Functional description, CAN 26095, for an explanation of phases and list of causes. You need this if you try to analyse TCH and SDCCH observations.

•

Working Set Manager Help, TAN 0873, for the creation of working sets as a measurement scope that suits your needs.

Typographic Conventions The following tables present the typographic conventions which have been used in this manual to describe different actions and restrictions.

2.3.1

Text Styles

The following table presents the typefaces and fonts and their indications. Style

Explanation

Initial Upper-case Lettering

Application names

Italiced text

Emphasis State, status or mode

Courier

File and directory names Names of database tables Parameters User names System output User input

UPPER-CASE LETTERING

Keys on the keyboard (ALT, TAB, CTRL etc.)

Bold text

User interface components


NTC TAN 0935/2.3 en


11

About This Manual

Style

Explanation

Initial Upper-case Lettering in Italics

Referenced documents

Variable user input

Referenced sections and chapters within a document

Table 1. Text styles in this document.

2.3.2

Command Line Conventions

The following UNIX command line prompts are used to indicate which user should enter the command(s). Note that you should not include the prompt in the command. Prompt

As which user

#

As the root user

omc>%

As the omc user

&

As any user

Table 2. Command line conventions.

2.4

Terms and concepts The lists below presents the terms and abbreviations used in this document.

2.4.1

Abbreviations

Abbreviation

Explanation

BAL

BCCH Allocation List

BCCH

Broadcast Control Channel

BCF

Base Control Function

BSC

Base Station Controller

BSS

Base Station Subsystem

BTS

Base Transceiver Station

CI

Cell Identity

DL

Downlink

HO

Handover

HOC

Handover Control

HLR

Home Location Register

IUO

Intelligent Underlay Overlay


NTC TAN 0935/2.3 en


12

About This Manual

Abbreviation

Explanation

LAC

Location Area Code

MML

Man-machine Language

MR

Maintenance Region

MS

Mobile Station

MSC

Mobile Services Switching Centre

OMC

Operation and Maintenance Centre

OSI

Open System Interconnection

PLMN

Public Land Mobile Network

PM

Performance Management

POC

Power Control

RACH

Random Access Control Channel

SDCCH

Stand Alone Dedicated Control Channel

SMS

Short Message Service

SQL

Standard Query Language

TCH

Traffic Channel

TRX

Transceiver

TSL

Time Slot

UL

Uplink

Table 3. Abbreviations.

2.4.2

Terms

The lists below presents the abbreviations and terms used in this document. Term

Explanation

BCCH allocation list

A managed object (MO) representing a set of frequencies in a broadcast control channel (BCCH) allocation.

Broadcast Control Channel (BCCH)

A channel from a base station to a mobile station (MS) used for transmission of messages to all mobile stations located in the cell coverage area

BTS group

A predefined set of BTSs which can be created and handled for definition by BSS Network Doctor.


NTC TAN 0935/2.3 en


13

About This Manual

Term

Explanation

Cell Identity (CI)

A number which identifies a cell to the networks within a location area (LA).

Cell BTS sector/omni

Cell and BTS mean the same. One cell can comprise a sector of sectorised Base Station site or the whole cell in case of an omni Base Station.

Clear code

Code that describes why the call set-up or the call itself has been disconnected.

Day

The counting of data per day is based on the period_start_time field in the measurement tables. This field always tells the starting hour of the measurement period. Under one day there are hours from 00 to 23.

Key Performance Indicator

The performance of the network is calculated from the NMS/2000 based on the Network Element counter information. Sometimes the plain counter as such describes an important performance aspect (number of calls, for example) of the network but sometimes a formula of counters is needed (e.g. drop call ratio).

Maintenance Region

Each object in the NMS/2000 database belongs to one and only one Maintenance Region (MR).

Measurement data

Data that includes both measurements and observations. Synonym for performance data.

Measurement report

A report of a specified measurement type that is generated after every output period.

NMS/2000

A product of Nokia Telecommunications for the operation and maintenance of cellular networks.

Performance data

See measurement data.

Reporting interval

The result output period of measurements, which the user can set. For MSC measurements the reporting interval is 5, 15, or 60 minutes, and for BSC measurements 15, 30 or 60 minutes, or 6, 12 or 24 hours.

SQL*Plus

An interactive program for accessing the database.


NTC TAN 0935/2.3 en


14

About This Manual

Term

Explanation

Stand-alone dedicated control channel (SDCCH)

A control channel (CCH) used for roaming, authentication, encryption activation and call control.

Time slot (TSL)

A time slot in the time division multiple access (TDMA) frame in the GSM radio interface.

Top-level User Interface

A graphical user interface (UI) in the Nokia NMS/2000 Workstation based on windowing.

Table 4. Terms used in this document.

For any other terms, refer to Glossary, TAN 0717.


NTC TAN 0935/2.3 en


15

Introduction to BSS Network Doctor

3

INTRODUCTION TO BSS NETWORK DOCTOR BSS Network Doctor is a reporting package which provides effective tools to cover all functional areas of the NMS/2000: Configuration Management, Fault Management, and Performance Management (PM), with special focus on the needs of network planning, operation and maintenance. Self-documented reports with front page description and column headers guarantee that the basic information is always where it is needed. To install BSS Network Doctor, follow the instructions given in the BSS Network Doctor, System Administrator’s Guide. BSS Network Doctor offers a menu-based user interface where the user can move up and down the menu hierarchy. See Chapter 5, User Interface, for a list of all available reports. BSS Network Doctor should not be used in an uncontrolled fashion, for example, by many NMS users simultaneously, because it increases the load on the system resources. To reduce the excessive use of BSS Network Doctor, ensure that BSS Network Doctor reports are available to all people who need the information. The results can be stored in a commonly known directory accessible to all necessary people, or distributed via mail or the Intranet. Well-planned and controlled reporting reduces the load on the NMS/2000 by letting users get necessary data quickly without accessing the Top-level User Interface. The reports also allow for the study of the data off-line in a file or printout. All basic measurements support a 60-minute reporting interval. If you need certain reports continuosly, schedule the reports and execute them automatically. For instructions on automatic running, refer to BSS Network Doctor System Administrator’s Guide.

3.1

Prerequisites for the Effective Analysis of the Network To analyse your network as efficiently as possible, ensure that: NMS/2000 configuration is optimal

•

The NMS/2000 is correctly configured to collect the alarm and measurement data (this is normally done during commissioning)

•

The correct measurements are activated in the Network Elements

•

The transfer of measurement result files from the BSS to the NMS/2000 succeeds.

When the NMS/2000 and the Network Elements are correctly configured, the NMS/2000 can provide very valuable, continuous, network-wide information


NTC TAN 0935/2.3 en


16


about the status of the network. Nokia provides a variety of services for network operations. Correct scopes are used when running the reports

•

For the scope of the BTS area, BSS Network Doctor provides you with the following parameters: -

Maintenance Region

-

BTS group

-

BSC

-

LAC

-

A single BTS, all BTSs or all IUO BTSs

-

BSC SW Version

-

Frequency band (of dual band)

-

BCF type (Base Station generation)

-

Working Set (manual, with BTSs or with BCFs) This is a new feature that allows you to limit your selection to a selfdefined working set created by Working Set Manager, one of Nokia’s NMS desktop applications.

•

For the selection of the time period, you can define the following parameters: -

Today

-

Absolute date

-

Relative date (ending on the current hour)

-

Relative date (ending the previous midnight)

Reports are distributed to the correct persons

When the reports from the NMS/2000 are available to users, the next problem you may have is that the resources to fix the problems are missing, not well defined, or that no training has been given.

3.2

Monitoring the Quality of a Cellular Network BSS Network Doctor provides you with a selection of reports to monitor the technical quality of a cellular network. This manual shows model reports of the more frequently used ones. The reports are discussed under the following headings:


NTC TAN 0935/2.3 en


17


3.3

•

Consistency Checks, Chapter 7

•

Quality of the Radio Network Plan (coverage, parameter optimisation), Chapter 8

•

Cell Dimensioning (capacity), Chapter 9

•

Call Success, Chapter 10

•

Transmission (availability, capacity), Chapter 11

•

Network Element Availability, Chapter 12

•

Interference, Chapter 13

•

Intelligent Underlay-overlay, Chapter 14

•

Network Configuration, Chapter 15

•

Alarms, Chapter 16

•

Locating Network Elements, Chapter 17

•

Named Sets, Chapter 18

•

Other Measurable Qualities, Chapter 19

•

Benchmark and Analysis, Chapter 20

Reporting Procedures The reports as such are tools. The operational procedures define how much value the reports bring. One important generic basic procedure related to the report counters can be described as follows.

3.3.1

Performance Indicator

Network performance can be evaluated based on performance indicators such as TCH drop call ratio. Performance indicators are mapped directly to either a counter or a formula of several counters. Drop call ratio, for example, is currently a formula of several counters. Performance indicators should be: •

Monitored on both the network and the area level for seeing the trends. An example of a report that covers both the network and the area level is Performance statistics (benchmark) (200) which collects some of the most interesting indicators into the same report and shows the daily totals. If you wish to see the average or component values, you can use the report Network benchmark statistics (204).

•

Monitored on BTS level across the area to spot the BTSs potential with problems. Often they are referred to as BTS Hit Lists or Top n Lists.


NTC TAN 0935/2.3 en


18


An example of a report at this level is Cells having high TCH drop call ratio (163) which helps to spot the BTSs which display a high drop-out ratio performance indicator “TCH drop-out ratio”. •

Analysed for a specific BTS, when the BTS has been found on the Hit List. Performance indicators can be used for analysing a specific cell during a certain time period. This can be done using Cell analyser (216) to see the average and busy hour values and 10-day/24-hour profiles of the most important indicators ending on the selected day. Cell doctor (213) is used to see the details of the BTS on a per-hour basis for all counters. These reports provide you with data on the alarms and parameters of the cell as well.

If the information provided by the different counters is not adequate for sorting out the problem, then the following level of actions depends on the quality of the problem. For instance, the TCH drop calls may be investigated using the TCH observations. The NMS/2000 database contains a very large number of counters which all are elementary performance indicators. For practical purposes, however, they can be hard to interpret. BSS Network Doctor offers reporting facilities on both the area and BTS level for the most important performance indicators that often are referred to as Key Performance Indicators. For more information, see Performance Management Basic Operating Principles and Procedures.


NTC TAN 0935/2.3 en


19

Using BSS Network Doctor

4

USING BSS NETWORK DOCTOR Before you use BSS Network Doctor, ensure that the measurement flow from the measurement network elements in the investigated area is functioning. You may also want to check that the network is logically divided into suitable areas so that the division serves the purpose of reporting. When enough consistent statistical data is available, you may run the reports and analyse the results, and then take any necessary actions based on the results. After this, you should verify the impact of actions by a new run of reports and a new analysis. This cycle of running reports, analysing them and modifying the network on the basis of the actions, continues through the whole lifespan of the network. Only the pace and scope of the key performance indicators may change from time to time.

 

     

  

  

       

 

  

 

 

   

  

  

   

Figure 1. General Work Process

Top-level reports are a good place to start the analysis. They display the basic quality indicators for a BTS area over a period of time as t otal values as well as by profile presentation. Save the first reports and use them as comparison material for later evaluation of the impact of the actions taken.


NTC TAN 0935/2.3 en


20


Normally, your first action is to clean up the adjacency discrepancies and to check the parameter settings and the UL interference situation. After the basic clean-up, you can start spotting other problems. If there is no traffic yet in the network (as usual before the network is launched), you can use the NMS/2000 statistics mostly on alarms, configuration queries and UL interference analysis. If the network is running, start locating the cells having potential problems and to troubleshoot them. If the network is new, the problems more commonly lie in an installation or equipment fault. Correcting these problems may require visits on the sites, but you can draw conclusions or get some indication of the nature of the problem from the cell statistics. When you have sorted out problems due to faulty equipment or faulty configuration, the remaining problematic cells may have problems with the radio network plan. You may have to tune the cell parameters or check the plan in general for the frequencies used or the environment.

4.1

Navigating with Reports, Formulas and Counters The data in the BSS Network Doctor reports is derived from counter formulas as well as directly from the NMS database counters themselves. In the reports you can find IDs referring to the used formulas and counters at the beginning of the reports in the report description, or often also in the column headers of the tables.


NTC TAN 0935/2.3 en


21


                                                      

  

                                                  

 

 

                  

             

                                                                       

Figure 2. Interrelationship between BSS Network Doctor reports and the formulas and counters used in them.

To see the actual formulas, refer to BSS Network Doctor Formulas Reference Guide, TAN 0936, and if interested in the counters, see Database Description for BSC Measurements, TAN 0422.


NTC TAN 0935/2.3 en


22

User Interface

5

USER INTERFACE This chapter describes the BSS Network Doctor user interface and lists the reports in the order they appear on the menus. BSS Network Doctor offers a menu-based user interface where the user can move up and down the menu hierarchy. All reports are listed in the submenus. You can also run the reports directly from the main menu option Run a report by identification number. The reports produce an output file which opens in the dtpad editor window. You can then modify, if necessary, and save the report using the editor commands. BSS Network Doctor also provides model reports. To display a model report, select Display a model report by identification number from the main menu. As a model report does not cause any load on the database server, it is a good idea to learn about the BSS Network Doctor reports by viewing model reports first. Note:

As each submenu contains a shortcut for running any of the BSS Network Doctor reports, you can flexibly have access to any of them regardless of which menu you are viewing. Enter the report ID after: •

m) for viewing a model report

•

r) for generating an actual report from the database


NTC TAN 0935/2.3 en


23

User Interface

                 

   

                     



     

   

                    

 

    

  

          

                    

    

                                     

                                  

Figure 3. BSS Network Doctor User Interface

5.1

Report Layout BSS Network Doctor reports are self-explanatory standard-size (56 lines per page and 80 characters per line) textual reports presented in a table format. Each report starts with a front page containing a description which helps you understand what the report is used for. One of the benefits of BSS Network Doctor is that the output is a plain ASCII file in a readable and printable format and can thus be easily transferred and handled. For example, to be able to view the ASCII text file in MS Word, open the file in Word and change the font to Courier New, 8 pt.


NTC TAN 0935/2.3 en


24

User Interface

5.2

Focusing your Report Selection Before a report is generated, BSS Network Doctor will prompt you to make your selections for generating the report limited to certain network elements and periods of time. The common selections are: •

BTS area

•

Area selection based on a BSC

•

Area selection based on a maintenance region

•

Time criteria

In addition to these, with some individual reports also other types of selections will be prompted for.

5.2.1

BTS Area Selection

You can select BTSs based on the following options: RET (default) = Maintenance Region 1

= BTS Group

2

= BSC

3

= LAC

4

= Single BTS

5

= All BTSs

6

= All IUO BTSs

7

= BSC SW Version

8

= Frequency Band (of dualband)

9

= BCF Type (Base Station generation)

10

= Working Set (manual, with BTSs)

11

= Working Set (manual, with BCFs)

Avoid causing extra load on NMS/2000, use small area if applicable. Please select option (RET = MR)

:

Example 1. BTS area selection menu.

5.2.2

Area Selection Based on a Maintenance Region (MR)

Maintenance Region

Ident

-------------------- -----GSM1800

1

globalScope

2

ESPOO/SALO

3

TAMPERE

5 99

Please enter MR Ident (RET = all, q = exit) :


NTC TAN 0935/2.3 en


25

User Interface

Example 2. Area selection based on a maintenance region (MR) menu.

5.2.3

Area Selection based on a BSC

BSC Name

BSC id

-------------------- -----BSC1KUTOJA

50264

BSC2UPS1

50265

BSC3TRE

50266

Foreign BSC

0

Please enter BSC id (RET = all BSC, q = exit) :

Example 3. Area selection based on a BSC menu.

5.2.4

Time Period Selection

You can select the measurement period based on the following options: RET (default) = Today

(from 00:00 to current Hour)

1

= Absolute date

(user defined)

2

= Relative date

(end current hour)

3

= Relative date

(end yesterday midnight)

Please select option (RET = Today)

:

Example 4. Time period selection menu.

5.3

User Log BSS Network Doctor provides you with reports for monitoring the user log data from the use of this application. These reports are common to both BSS and NSS Network Doctor. The Log statistics (512) report gives basic information about the BSS Network Doctor log file. OS User

Host

Package

Report

Start Time

Name

Name

Version

No

yyyy-mm-dd hh:mm

Exec Time (s)

---------- ---------- ---------- ---------- ------------------ --------neva

teh


NTC TAN 0935/2.3 en

nea

nea

v.1.18.41

120

1997-12-22 15:53

3

603

1997-12-22 15:56

2

998

1997-12-22 15:56

2

v.1.18.41B 120

1997-12-18 15:09

1

120

1997-12-18 15:09

0

014

1997-12-18 16:00

5

020

1997-12-18 16:02

76

021

1997-12-18 16:03

17

021

1997-12-18 16:12

16

022

1997-12-18 16:16

10

023

1997-12-18 16:18

148

024

1997-12-18 16:20

147

25

1997-12-18 16:23

2


26

User Interface

027

1997-12-18 16:24

2

Example 5. Report 512: Log statistics

The Network Doctor use statistics (513) report shows how many times a report has been used and its average execution time. How many times a report has been used and its average execution time

Average

Execution

Report

Used

Time

Number

Times

sec

------ ------ --------061

2

8.50

070

2

3.50

071

3

18.00

072

8

44.75

074

1

12.00

075

1

20.00

080

1

11.00

081

1

4.00

082

1

6.00

092

1

5.00

125

2

24.00

127

2

92.50

135

2

19.00

138

1

61.00

181

4

1019.50

196

3

34.67

204

2

85.50

216

4

67.75

232

14

7.14

512

19

5.11

513

2

2.50

625

1

8.00

73

8

28.13

999

5

2.60 How many times a user has run a report

User

Report

Used

Number

Times

---------- ------ -----user1

user2


NTC TAN 0935/2.3 en

071

1

072

1

080

1

081

1

082

1

127

1

135

2

138

1

216

3

232

12

512

6

73

4

061

1

092

1

127

1

196

1


27

User Interface

204

1

232

2

512

8

513

2

999

2

Example 6. Report 513: Network Doctor use statistics

5.4

Report Menus The list below highlights the types of reports that BSS Network Doctor user interface provides for the collection of performance data from the telecommunications network. Note:

To avoid unnecessary load on the system, you should run a model report first by its ID to get an example of the type of report produced by BSS Network Doctor. •

Fault Management

•

Configuration Management

•

-

Find cell

-

Checks

-

Adjacencies

-

Named parameter set audit

-

Network entities

-

Frequencies

-

Cell coverage

Performance Management BSS -

PM administration

-

SDCCH and TCH access, availability

-

Handover

-

Drop call

-

Traffic and load

-

Interference and quality

-

IUO


NTC TAN 0935/2.3 en


28

User Interface

-

Call success

-

BSS transmission availability and quality

-

Other

•

Benchmark and analysis

•

User log

The following subsections describe briefly the contents of the different report types. The reports are listed as they appear on the menu, giving also the threedigit identification number in brackets.

5.4.1

Fault Management

The reports on the Fault Management menu are used to analyse the stability of the network. For example, to analyse the stability first on t he network level, use Alarm types and counts (034), and if interested in the frequency of interesting alarms, use the report BSC alarm breakdown (030). The reports available from this menu are: •

Alarm statistics (020)

•

Alarm types and counts (034)

•

Alarm types and counts for BSC (035)

•

Alarm statistics by cells (023)

•

Active BCCH missing (2567) alarms (024)

•

Alarm sum time by cells (025)

•

Cell outage breakdown over 10 days (027)

•

BSC Alarm breakdown (030)

5.4.2

Configuration Management

The reports on the Configuration Management menu give provide you with data on the network configuration.

5.4.2.1

Find Cell

The reports on the Find Cell menu allow you to find specific data on various network elements. The reports on this menu are: •

All base station sites (BCF) per Maintenance Region (041)

•

All radio network ordered by BSC, BCF, BTS (042)

•

All BTSs with LAC and CI (043)


NTC TAN 0935/2.3 en


29

User Interface

•

Find BS sites having the given character string in the name (044)

•

Find cells having the given CI and LAC (045)

•

Find cells having an adjacent cell with the given CI and LAC (046)

•

Find cells having the given frequency (047)

•

Find locked BCFs, BTSs, TRXs and channels (050)

5.4.2.2

Checks

The NMS/2000 contains a lot of data which must be consistent. For example, if the adjacent cell contains parameters which have to be the same as in the target cell, use the report Adjacency discrepancies (060) to check this. The reports in this menu are: •

Adjacencies to non-existing or foreign cells (065)

•

Adjacency discrepancies (060)

•

Non-symmetrical adjacencies (061)

•

Frequency check of adjacent cells (062)

•

Adjacent cell double frequencies (069)

•

Non-unique CI and LAC (066)

•

Handover synchronisation (067)

•

BTS parameter survey (068)

•

BTS audit (063)

•

Maintenance region audit (064)

5.4.2.3

Adjacencies

When checking the implementation of the network plan, adjacency is one of the reported items. Sometimes there are, for example, too many or too few adjacencies defined or accidentally implemented in the plan. The adjacency reports are: •

BTSs with maximum number of adjacencies (070)

•

BTSs with minimum number of adjacencies (071)

•

Defined, undefined and used adjacencies of a cell (072)

•

Undefined adjacent cells (073)

•

Adjacencies of cells (074)


NTC TAN 0935/2.3 en


30

User Interface

•

BTSs with maximum number of adjacencies to different Location Areas (075)

5.4.2.4

Named Parameter Set Audit

Named parameter sets can be used for defining new or alternative parameter plans to check the usage. The Named Parameter Set Audit menu contains the following items: •

Number of named parameter sets per object type (080)

•

Named sets used (081)

•

Allocation of a named set (082)

5.4.2.5

Network Entities

The reports on the Network Entities menu provide you with object summary data on various network element types. BSC option statistics (089), for example, shows the optional features that are used in the BSCs of the selected BTS area. The information in it is retrieved from the NMS/2000 database that is updated only by the Upload command in the Top-level User Interface. •

Network configuration summary (090)

•

Maintenance regions (091)

•

BSCs (092)

•

MSCs (093)

•

HLRs (094)

•

Base station sites of a maintenance region (095)

•

Location Areas (096)

•

PLMNs (097)

•

BCF software and hardware type statistics (099)

•

BSC option statistics (089)

5.4.2.6

Frequencies

The frequency plan is one of the basic network settings. Since the plan is often inserted via the NMS/2000 manually, errors may easily occur. You can check the plan manually using the report Frequency plan (111). •

Occurrence of frequencies (110)

•

Frequency plan (111)


NTC TAN 0935/2.3 en


31

User Interface

5.4.2.7

Cell Coverage

Cell coverage reports are based on Timing Advance measurement and provide data according to distance ranges and power classes. •

Cells by dominant distance range (231)

•

Distance range distribution per cell (232)

5.4.3

Performance Management BSS

The reports on this menu provide you with PM data on various levels.

5.4.3.1

PM Administration

The PM Administration menu reports contain data related to measurements, for example, are the measurements active and do they send data to the database. •

Active measurements and observations (120)

•

Last BSS measurement record times (127)

•

First and last measurement record times for each BSC (121)

•

Objects with active observations (123)

•

Records for a measurement type, over BTS area (122)

•

Records for a measurement type, over BSC (126)

•

TCH and SDCCH observation records (124)

•

Cells having undefined adjacent measurement results (125)

5.4.3.2

SDCCH and TCH Access, Availability

There are many aspects how the dimensioning of the network can affect the quality of the network. The most severe situation occurs when the user does not have access to the system. With the help of these reports you can monitor the BTS area level. •

Cells having RACH rejections (134)

•

Cells having SDCCH congestion (130)

•

Cells having TCH congestion (135)

•

Cells having high TCH raw blocking (138)

•

Cells having unavailable radio time slots (139)

•

Unavailability classification per BSC (131)


NTC TAN 0935/2.3 en


32

User Interface

•

Cells having SMS establishment failures (132)

5.4.3.3

Handover

Handover (HO) is one of the basic features of the GSM network. The HO failure ratio is therefore a key quality indicator. With the help of these reports you can monitor the BTS area level. •

Cells having high HO failure ratio (150)

•

Cells having high HO attempts/call ratio (157)

•

Adjacencies having high HO failure ratio (153)

•

HO attempt cause distribution by cells (154)

5.4.3.4

Drop Call

The drop call ratio is one of the key features indicating the quality of SDCCH and TCH. With the help of these reports you can monitor the BTS area level. •

TCH drop call statistics by days across area (160)

•

TCH drop call statistics per day in each BSC (162)

•

Cells having high TCH drop call ratio (163)

•

Transcoder failures (164)

•

SDCCH drop ratio per cell (166)

•

Cells having high drop call count in handovers (167)

5.4.3.5

Traffic and Load

The reports on this menu provide you with data on the traffic and load. •

TCH traffic (Erlang) per hour for each BSC (180)

•

Daily TCH traffic profile for a BTS (181)

•

Busy hour traffic for all BTSs (182)

•

Low traffic cell check-up (183)

•

BSC unit load per hour for each BSC (184)

•

Cells having maximum TCH traffic (185)

•

Cells having maximum paging traffic (186)

•

Cell location updates (187)

•

Cells having highest RACH load (188)


NTC TAN 0935/2.3 en


33

User Interface

•

Cells sorted by SDCCH or TCH holding time (189)

•

Cells having most delete indications (202)

•

Call distribution per LA (222)

5.4.3.6

Interference, Quality and Link Balance

Link Quality is one of the quality indicators in the GSM network that can be affected by interference, for example. Link Balance is one of the central concepts used in planning the GSM network. Interference:

•

Cells having UL interference, 24-hour/10-day breakdowns (190)

Quality:

•

UL and DL quality and UL interference per TRX, 24-hour/10-day breakdowns (196)

•

UL and DL quality per TRX (197)

Link balance:

•

Cells by DL and UL level balance (195)

•

Cells by dominant link balance range (198)

•

Cells having bad link balance (191)

•

Link balance per cell (208)

•

Link balance of an area (199)

5.4.3.7

IUO

The reports in this menu provide you with data on traffic absorption and intelligent underlay-overlay counters on the BTS level. •

Cells by average traffic absorption to super TRXs (401)

•

KPI statistics for IUO cells (403)

•

Cells by busy hour traffic absorption to super TRXs (402)

•

IUO counters of a cell (400)

•

Adjacent cells with the same or adjacent frequency, IUO super TRX excluded (405)

•

C/I statistics (407)

•

IUO measurement data per BTS (404)


NTC TAN 0935/2.3 en


34

User Interface

5.4.3.8

Call Success

The reports in this menu provide you with data on call success. •

Cells by call success ratio (250)

•

Call success profiles of a cell (251)

5.4.3.9

BSS Transmission Availability and Quality

The reports of this menu provide you with statistics about the availability and quality of BSS transmission, giving profiles for DMR, DN2 and TRU with data on the duration of errored seconds, for example. •

Transmission statistics (518)

•

DMR profile (515)

•

DN2 profile (516)

•

TRU profile (517)

5.4.3.10 Other •

Clear code statistics (220)

•

Location update success ratio per BSC (203)

5.4.4

Benchmark and Analysis

Benchmark

Performance indicators need to be monitored on network and area level for seeing the trends. An example of a report from these network levels is Performance statistics (benchmark) (200) which collects some of the most interesting indicators into the same report showing the daily totals. If you wish to see the averages you can use the report Network benchmark statistics (204). •

Performance statistics (benchmark) (200)

•

Network benchmark statistics (204)

•

Performance profiles for area, 24-hour/10-day breakdowns (207)

•

Quality survey (800)

Analysis

•

BSC doctor (212) This report is used for investigating BSC performance management data and problems which can occur in the BSC. Performance needs to be analysed for a specific BTS when the BTS has been found on the Hit List.


NTC TAN 0935/2.3 en


35

User Interface

•

Cell analyser (216) You can use this report to see the average and busy hour values and 10-day/ 24-hour profiles of the most important indicators ending on the selected day. Cell analyser offers versatile information about the parameters, key performance indicators, consistencies and alarms for analysing a single BTS.

•

Base station site check (221) This report allows you to make a quick health check of all cells under the selected BCF. It displays a set of KPIs together with information on alarms, configuration and the administrative state.

•

Cell doctor (213) This report is used to see the details of a BTS on a periodical basis for all counters and also the alarms and parameters across the selected period.

•

Availability per BSC unit (215) This report shows for each unit of each BSC the total disconnection time and the total number of restarts over a given period of time.

•

SDCCH and TCH and BSC out HO observation statistics (217) Depending on the dominating failure class (e.g. Abis) it may be necessary to set the cell under observation. With this report, the observation data can be quickly analysed. This report helps to see the actual point of the failure in the message flow as defined by phase and cause.


NTC TAN 0935/2.3 en


36

Actions to Take before Using the Reports

6

ACTIONS TO TAKE BEFORE USING THE REPORTS Before the reports can give reliable and comparable results, you have to check the NMS/2000 for some basic things.

6.1

Checking the PLMN Object Start with checking which PLMN object name and instance you use in the BSS Network Doctor reports.

6.1.1

PLMN Object Name

The PLMN object name is used in the BSS Network Doctor report headers. In the NMS/2000 database there may be more than two PLMN objects. BSS Network Doctor is not protected against this and so may show the name of another PLMN. To fix this, just rename both PLMN objects using Network Editor. Note that you need system administrator’s rights to run Network Editor.

6.1.2

PLMN Object Instance

A PLMN object instance may be defined as a character string, for example, ‘PLMN’. This could be fatal to some BSS Network Doctor reports, resulting in the error “invalid number”. To fix this, use Network Editor to give the PLMN object instance a numeric value.

6.2

Checking a BTS Object Instance Normally a BTS object instance is identified by a number (1...128). A BSC accepts only numbers for the BTS object instance. In the NMS/2000, however, it is possible to give a character string for the BTS object instance (foreign cells often have the CI and LAC separated by a space as the identification code) and it does not cause any error if not sent to the network. However, for some of the BSS Network Doctor reports this feature is fatal, resulting in the error “invalid number”. To fix this problem: 1.

Delete the BTS with characters in the object instance or

2.

Change the object instance ID to a number. This is possible only in SQL*Plus and should be done by the system administrator only or

3.

Set up the BTS groups and/or Maintenance Regions so that the odd BTS identification codes are isolated into their own group or MR.


NTC TAN 0935/2.3 en


37


6.3

Estimating the Load on the NMS/2000 This section contains the following topics: •

load on the NMS/2000

•

active measurements in BSCs

•

measurement flow from a BSC

6.3.1

Load on the NMS/2000

This section gives you some basic information on how you should use the measurements to fully benefit from the data the reports provide. Note:

The load caused by receiving measurements and by inserting them in the database can be considerable and can affect the proper functioning of the NMS/ 2000. Experience from the field has shown that there is no forcing need to use the 15 min or 30 min reporting intervals. The 60 min interval in the network analysis is sufficient for practical needs. If the operator chooses to use the 15 min period, it should be clearly understood that this solution requires four times more capacity than the 60 min period does. There should always be a very good reason behind the decision to go for 15 min or 30 min periods. The BSS Network Doctor reporting package is designed to work on the 60 min or longer reporting intervals. If a shorter than the 60 min period is used, some reports do not show correct values. Note:

A precise way to calculate how much data a measurement set will produce is to use the Nokia NMS Excel spreadsheet. The spreadsheet gives the amout of data but not the load on the NMS/2000. This is why the tool is applicable if the measurement set is going to be changed and you want to see what is the net impact on the overall data volume.

6.3.2

Active Measurements in the BSC

BSS Network Doctor provides a variety of reports for investigating the active measurements in a BSC.


NTC TAN 0935/2.3 en


38


6.3.2.1

How to Check Which Measurements Are Active

To check which measurements are active in the BSCs (in the NMS/2000’s view) you may use the BSS Network Doctor report Active measurements and observations (120). In this report you can easily see the overall situation as per the NMS/2000 database. The problem you may encounter is that you cannot always fully rely on that the NMS/2000 database is up to date, and you must first upload all measurements from the BSCs. This situation does not cause any loss of measurements because it is ultimately the situation in the BSCs that counts. The problem may follow if the MML has been used to start measurements. Thus it is better to use only the Top-level User Interface for managing the measurements. = =

ACTIVE MEASUREMENTS AND OBSERVATIONS

= =

Network:

PLMN

= =============================================================================== This report displays the active measurements in the BSCs. RP

= Reporting period, i.e. how often data is sent to the NMS/2000

M T W T F S S = weekdays when the measurement is executed P1S

= Start of period 1

P1E

= End of period 1

To gain maximum benefit of the NMS reports it would necessary to run the following measurements with the 60 min reporting period, 24 hours a day. ** Traffic, Handover, Resource Access, Resource Availability, Power Control With other measurements you may use a longer reporting period as best suits your needs, 12 hours, for example. Note: This situation is seen from the NMS/2000 database. There are cases when the measurement is active in a BSC even though the NMS/2000 sees it as inactive. To be sure about the measurement status you should read them from the network as well as check them against MML output. Note: The reporting period is a critical property with regard to load on the NMS/2000. Short reporting periods should be used only if necessary. ===============================================================================

BSC NAME : BSC1

LAST

Period (min)

MTWTFSS

P1S

P1E

START

EDITED

DATE

BY

MEASUREMENT TYPE

------ -------- ---- ---- -------- ------ ----------------------------------60

1111111

0 2400 19971013 dcssys BSC Clear Code ( SERLEV ) Meas

60

1111111

0 2400 19980302 omc

60

1111111

0 2400 19971013 dcssys Handover Measurement

60

1111111

0 2400 19971204 mikasi Ho Adj. Cell Measurement

60

1111111

0 2400 19971204 omc

Internal Handover Observation

60

1111111

0 2400 19971217 omc

Link Balance Measurement

60

1111111

0 2400 19970825 mikasi Load Measurement


NTC TAN 0935/2.3 en

BSC Clear Code (PM) Meas


39


60

1111111

0 2400 19971204 omc

OSI Measurement

0 2400 19971204 omc

Outgoing Handover Observation

60

1111111

60

1111111

60

1111111

0 2400 19971204 netmon Resource Access Measurement

60

1111111

0 2400 19971202 omc

Resource Availability Meas.

60

1111111

0 2400 19971204 omc

Resource Availability per BSC

60

1111111

0 2400 19971205 omc

Rx Level Measurement

60

1111111

0 2400 19971205 omc

Rx Quality Measurement

60

1111111

0 2345 19971222 gsmsys SDCCH Observation

60

1111111

0 2400 19971217 omc

Timing Advance Measurement

60

1111111

0 2400 19971204 omc

Traffic Measurement

60

1111111

0 2400 19971205 test03 Underlay-Overl ay Measurement

500 2400 19970825 dcssys Power Control Measurement

Example 7. Report 120: Active measurements and observations

6.3.2.2

How to See What Measurements Send Data to the Database

To check which measurements really are active you have to analyse the PM tables to see what measurements have sent data. To do this, use the report Last BSS measurement record times (127). = =

LAST BSS MEASUREMENT RECORD TIMES

= =

Network:

PLMN

= =============================================================================== This report shows the date and time of last measurements available in the NMS/2000 database for each measurement type. ===============================================================================

. BSC level .

Availability (of units) ............p_nb sc_avail

no records

.

Load .............. ................ ..p_nbsc_load

1998_05-06 16:00

.

Clear codes ............... ............p_nb sc_cc

1998_05-06 16:00

.

Clear codes PM ............... ......p_nbsc_cc _pm

1998_05-06 16:00

.

OSI 1 ................ ............... p_nbsc_osi1

1998_05-06 16:00

.

OSI 2 ................ ............... p_nbsc_osi2

1998_05-06 16:00

.

OSI 3 ................ ............... p_nbsc_osi3

1998_05-06 16:00

.

OSI 4 ................ ............... p_nbsc_osi4

1998_05-06 16:00

.

TRX availability ............... p_nbsc_trx_avail

1998_05-06 16:00

. BTS level .

Traffic .............. ............p_n bsc_traffic

1998_05-06 16:00

.

Resource availability ..........p_nbs c_res_avail

1998_05-06 16:00

.

Handover ............... ...............p _nbsc_ho

1998_05-06 16:00

.

Undefined adj. cell........p_n bsc_undef_adj_c ell

no records

.

Link balance .............. ..p_nbsc_link_ba lance

1998_05-06 16:00 *

.

Timing advance .............p_ nbsc_timing_adv anc

1998_05-06 16:00 *

.

SERLEV ............... ............p_n bsc_service

1998_05-06 16:00

.

MS Speed ............... .........p_nbsc_ ms_speed

no records

*

.

Dual Band .............. ........p_nbsc_d ual_band

no records

*

.

C/I Ratio .............. .........p_nbsc_ ci_ratio

no records

*

. TRX level


NTC TAN 0935/2.3 en


40


.

Resource access .............. .p_nbsc_res_acc ess

1998_05-06 16:00

.

Power control......... ..............p _nbsc_power

1998_05-06 16:00

.

Rx quality ................ .......p_nbsc_rx _qual

1998_05-06 16:00 *

.

Rx level statistics ........p_nbsc_ rx_statistics

1998_05-06 16:00 *

.

Underlay-overl ay ............... .p_nbsc_underlay

1998_05-06 16:00 *

.

Hot Spot ............... .........p_nbsc_ hot_spot

no records

*

. Adjacency level .

HO adj. cell .............. ........p_nbsc_h o_adj

1998_05-06 16:00 *

. Transmission object level .

DMR ............... ................ ...p_nbsc_dmr

no records

.

DN2 ............... ................ ...p_nbsc_dn2

no records

.

TRU ............... ...............p _nbsc_tru_bie

no records

*) Optional BSC feature

Example 8. Report 127: Last BSS measurement record times

In the Records for a measurement type, over BSC (126) report the number of records, minimum reporting period and maximum reporting period are reported for every hour having measurement results for the selected measurement type. Day

Hour

yyyymmdd hh:mm

Min

Max

prd

prd

RECORDS

-------- ----- ----- ----- ---------19980506 19:05

60

60

12

20:05

60

60

12

21:05

60

60

12

22:05

60

60

12

23:05

60

60

12

19980507 00:05

60

60

12

01:05

60

60

12

02:05

60

60

12

03:05

60

60

12

04:05

60

60

12

05:05

60

60

12

06:05

60

60

12

07:05

60

60

12

08:05

60

60

12

09:05

60

60

12

10:05

60

60

12

11:05

60

60

12

12:05

60

60

12

13:05

60

60

12

14:05

60

60

12

15:05

60

60

12

16:05

60

60

12

17:05

60

60

12

18:05

60

60

12

19:05

60

60

12

20:05

60

60

12

21:05

60

60

12

22:05

60

60

12

23:05

60

60

12

Example 9. Report 126: Records for a measurement type, over BSC


NTC TAN 0935/2.3 en


41


6.3.2.3

How to See Which BSCs Send Data to the Database

To see which BSCs really send data to the database, use the report First and last measurement record times for each BSC (121). In this report you have to select the measurement type. Normally you may use the traffic measurement. = =

FIRST AND LAST BSS MEASUREMENT RECORD TIMES FOR EACH BSC

= =

Network:

=

Table selection:

PLMN 16

= =============================================================================== The date and time of the first and last measurements available in the NMS/2000 database are reported for the selected

measurement type by BSCs.

First record (start time)

Start time of the first measurement record.

Last record (start time)

Start time of the last measurement record.

Period duration max.

Maximum duration of a period.

Period duration min.

Minimum duration of a period.

Note: Depending on the selected table, the run time can be long. ===============================================================================

Records in SERLEV ( p_nbsc_service ) Period BSC name

First record

Last record

(start time)

(start time)

Period

duration duration max.

min.

-------------------- ----------------- ----------------- -------- -------BSC1

1998-05-17 00:00

1998-06-16 09:00

60

60

BSC2

1998-05-28 10:00

1998-06-16 09:00

60

60

BSC3

1998-05-17 00:00

1998-06-16 09:00

60

60

Example 10. Report 121: First and last measurement record times for each BSC

6.3.2.4

How to Set the Measurements

The basic measurements (traffic, resource availability, resource access, handover, power control) should: •

be run every day for 24 hours (or, for example, from 05 to 24 h if the operator agrees)

•

use the 60 min reporting interval.

With other measurements, use a longer period, 12 hours for example, as needed and as is reasonable in terms of the capacity of the NMS/2000. Remember that even though it is easy to change the measurement period, you will always lose


NTC TAN 0935/2.3 en


42


the data from the period during which you stop the measurement (the period can be changed only when the measurement is stopped). The BSS measurements used in the BSS Network Doctor reports are the following: Measurement type

Object resolution

Availability

Database table

- in starting

Remark

- in reporting

NMS/2000/ BSC release

Traffic

- BSC

standard

p_nbsc_traffic

- cell

T1/S1 ->

Resource availability

- BSC

standard

p_nbsc_res_avail

- cell

T1/S1 ->

Resource access

- BSC

standard

p_nbsc_res_access

- TRX

T1/S1 ->

Handover

- BSC

standard

p_nbsc_ho

- cell

T1/S1 ->

Power control

- BSC

standard

p_nbsc_power

- TRX (since S6)

T1/S1 ->

Load

- BSC

standard

p_nbsc_load

- BSC/ processor unit

T1/S1 ->

Availability

- BSC

standard

p_nbsc_avail

- BSC/ processor unit

T1/S1 ->

Undefined adjacent cell (*

- BSC

standard

p_nbsc_undef_adj_cell

- cell / non-adjacent frequency

T3/S2 ->

Records generated for every measurement period.


Records generated for every measurement period if accesses.

Records generated only for cells having handovers.

0 values in many counters during the periods without events.




NTC TAN 0935/2.3 en


43


Measurement type

Object resolution

Availability

Database table

- in starting

Remark

- in reporting


Clear codes

- BSC

standard

p_nbsc_cc

- BSC

T3/S2 ->

BSC clear codes

- BSC

standard

p_nbsc_cc_pm

- BSC

T4/S3 ->

RX quality

- BSC

optional

p_nbsc_rx_qual

- TRX

T4/S3 ->

Handover adjacent cell

- BSC

optional

p_nbsc_ho_adj

- adjacency

T4/S3 ->

Underlay-overlay statistics

- BSC

optional

p_nbsc_underlay

- TRX

T6/S4 ->

RX-level statistics

- BSC

optional

p_nbsc_rx_statistics

- TRX

T6/S4 ->

- BSC

optional

- BTS

T6/S4 ->

Timing advance

- BSC

optional

p_nbsc_timing_advance

- BTS

T6/S4 ->

Records generated for every measurement period if traffic.


Records generated only for TRX having TCH call samples.

Records generated for every measurement period if HOs. All handovers are counted (SDCCH-SDCCH, SDCCHTCH or TCH-TCH).


Records generated only for TRX having TCH call samples. Link balance per classmark p_nbsc_link_balance

0 and -1 values in many counters during the periods without MS power measurements.


NTC TAN 0935/2.3 en


44


Measurement type

Object resolution

Availability

Database table

- in starting

Remark

- in reporting


Resource availability per BSC

- BSC

standard

- BSC

T6/S4 ->

BSC clear code

- BSC

standard

p_nbsc_service

- BTS

T6/S4 ->

MS Speed

- BSC

optional

p_nbsc_ms_speed

- BTS

T10/S6 ->

Dual Band

- BSC

optional

p_nbsc_dual_band

- BTS

T10/S6 ->

C/I Ratio

- BTS

optional

p_nbsc_ci_ratio

- BTS

T10/S6 ->

DMR

- BSC

standard

p_nbsc_dmr

- DMR

T10/S6 ->

DN2

- BSC

standard

p_nbsc_dn2

- DN2 port

T10/S6 ->

TRU

- BSC

standard

p_nbsc_tru_bie

- TRU direction

T10/S6 ->

p_nbsc_trx_avail



Records generated for every measurement period if traffic. BTS DF3 of B10 is needed.

Records generated for every measurement period. Missing data possible for individual units in the NMS/ 2000 if remote operation cleared measurement in the unit.

See DMR.

See DMR. Table 5. BSS Measurements.


NTC TAN 0935/2.3 en


45


Note:

Measurements that are optional BSC features must must be activated by BSC MML before they can be set and started from the NMS/2000. For example, to activate Rx Quality/ HO Adjacent Cell, give command ZWOF:10-28:1; . *) If other than the neighbouring cell frequency is measured, you have to set on not only the measurement but to create a BCCH allocation list in the BSC and the BTSs assigned to it. The Undefined Adjacent Cell measurement as such may be active but it reports only the neighbouring cell frequencies with strange base station identity codes until the BTSs have been assigned assigned to a BAL. Once Once it is assigned to a BAL, BAL, all frequencies of a BAL are reported. The BAL assignment should not be used globally in the network. Only one welldefined small area (group of BTSs) at a time should be defined to use a BAL in BTSs. This is because the usage of a BAL loads MSs. In general the undefined adjacent cell measurement also produces a lot of data to the NMS/2000. Also, typically there are not enough people to analyse the result for larger areas. Be careful with the usage of BALs and undefined adjacent cell measurement. In practice, the use of a double BAL is possible if there are not many frequencies in the network (less than 32 - for example, in GSM networks this is possible). If there are many frequencies as in a DCS network, then the double BAL is not applicable for this purpose.

6. 3 . 3

Measurement Flow from a BSC

To check that the measurement flow from the BSCs is functioning, use the report Records for a measurement type, over BTS area (122). = =

RECORDS FOR A MEASUREMENT TYPE, OVER BTS AREA

= =

Network:

PLMN

=

Area:

MR - all MRs

=

Measurement name:

HO adj. cell

=

Measurement table:

p_nbsc_ho_adj

= =============================================================================== The number of records, minimum reporting period and maximum reporting period are reported for every hour having measurement results for the selected measurement type. The hour and minutes shown is the beginning time of the measurement period. Note: Running this report takes a while. Patience please. ===============================================================================


NTC TAN 0935/2.3 en


46


Day

Hour

Min

Max

prd

prd

yyyymmdd hh:mm (min) (min)

RECORDS

-------- ----- ----- ----- ---------19980420 08:04

60

60

3

09:04

60

60

5

10:04

60

60

9

11:04

60

60

12

12:04

60

60

6

13:04

60

60

4

14:04

60

60

4

15:04

60

60

8

20:04

60

60

2

19980421 09:04

60

60

4

10:04

60

60

5

11:04

60

60

6

13:04

60

60

4

14:04

60

60

6

15:04

60

60

4

16:04

60

60

6

17:04

60

60

8

19:04

60

60

4

20:04

60

60

1

21:04

60

60

2

19980422 08:04

60

60

2

09:04

60

60

6

Example 11. Report 122: Records for a measurement type, over BTS area

If the 60 min period is used and the number of records for a measurement period differs from the number of BTSs in the area which has active measurements, the system administrator should be alerted to check why the measurements are not transferred. Note that if traffic is very low, some measurements, such as handover, do not generate any records for those measurement periods in which no handovers have occurred. A BSC can buffer measurements and alarms for several hours, if the links between the NMS/2000 and the BSC are down , but the situation should be corrected as soon as possible to avoid an emergency later.

6.4

Checking Observations The Objects with active observations (123) report displays the active observations in the BSCs. Note that this situation is seen from the NMS/2000 database. There could be cases when the observation is active in BSC even though the NMS/2000 sees it inactive. To be sure about the measurement status, read them from the network and check them against the MML output. The observations may produce a huge amount of data and are therefore a very critical property as regards the load on the NMS/2000. Use the observations only when needed for troubleshooting and remember to stop them.


NTC TAN 0935/2.3 en


47


LAST

OBJECT

RP MTWTFSS

P1S

START

EDITED

P1E

DATE

BY

OBSERVATION TYPE

-------------------- -- -------- ---- -------- ------ -------------------BSC:BSC1KUTOJA

60 1111111

BCF:KUTOJA001

0 19971204 omc

Internal Handover Ob

2400

servation

BTS:KUTOJA1001 BTS:1 TRX:--TSL:---

BSC:BSC1KUTOJA

60 1111111

BCF:KUTOJA001

0 19971204 omc


2400

servation

BTS: BTS:1 TRX:--TSL:---

BSC:BSC1KUTOJA

60 1111111

BCF:SUOSAA004

0 19971204 omc


2400

servation


BSC:BSC1KUTOJA

60 1111111

BCF:KILO007

0 19971204 omc


2400

servation


Example 12. Report 123: Objects with active observations

The TCH and SDCCH observation records (124) report shows all BTSs and TRXs per observation type that have records in the database. SDCCH observation records are available for: Nbr of BSC

BCF

BTS

records

------------- --------------- --------------- ------BSCXXX

Site A

Cell 1234

17

BSCYYY

Site X

Cell 7890

17

TCH observation records are available for: Nbr of BSC

BCF

BTS

TSL records

------------- --------------- --------------- --- ------BSCXXX

Site A

Cell 1234

1

17

Example 13. Report 124: TCH and SDCCH observation records


NTC TAN 0935/2.3 en


48


6.5 6.5

Chec Checki king ng Bloc Block ked or Fi Filter ltered ed Alarm larmss In order to follow the alarm situation in the network, it is essential that all alarms are sent to the NMS/2000. You can block the alarms in the DX 200 network elements (BSC, MSC, HLR, NMS/2000 FE) with MML. The information on which alarms are blocked is not stored in the NMS/2000 database. You should check periodically which alarms are blocked in the network elements by using a remote MML and by verifying the situation against the alarm and blocking filtering plan. In the NMS/2000 T10 release there is a feature called Alarm Filtering and Acknowledging. This feature allows you to discard, for example, the alarms from the BTSs which are not yet in the operational state but in integration and testing. The usage of the feature needs to be under good control so that the alarms are not filtered out any longer than is necessary.

6.6 6.6

Chec Checki king ng th thee Mai Maint nten enan ance ce Regi Region on Assi Assign gnme ment ntss 6.6. 6.6.1 1

Usin Using g th thee Mai Maint nten enan ance ce Regi Region onss for for Repo Report rtiing

Maintenance Region (MR) is an internal concept of the NMS/2000. The Maintenance Region itself is created in the NMS/2000 database as an object under the PLMN object using Network Editor. When other objects are created in the NMS/2000 database using Network Editor, it is possible to assign each object to one and only one of the existing Maintenance Regions.

 

 

 

 

    

 

 

Figure 4. Assignment of Objects to a Maintenance Region.

It is a good idea to have a separate MR for those BSs which are not yet integrated, as then the integrated BS may belong to the same MR or one of various other MRs (for example, a MR per town) and it is easy to generate reports which are not disturbed by tasks related to installation and integration. This works particularly well in the pre-launch phase.


NTC TAN 0935/2.3 en


49


6.6.2

Common Mistakes

It often happens that in the beginning of network operations, the division of the network into Maintenance Regions is not well planned and all objects are assigned to one and the same MR, or are not assigned to any MR. Later, when the network grows and reporting practices are created, you may find that a MR can be effectively used for creating separate reports for various parts of the network. You can use Network Editor to create the MR assignments of objects.

6.6.3

How to See the MR Division

To see how the MRs are used, run the report Network configuration summary (090). = =

NETWORK CONFIGURATION SUMMARY

= =

Network:

PLMN

= =============================================================================== This report shows - NSS network entity sums for each MR and sum over the network - BSS network entity sums for each MR and sum over the network sorted by . the number of BTSs, for used and not used BCFs, BTSs, TRXs, CHNs .

BSC TOT: total nbr of BSCs

.

TC TOT : total nbr of transcoders

.

PCM TOT: total nbr of PCMs

.

BCF UNL: nbr of unlocked BCFs

. .

LCK: nbr of locked BCFs BTS

.

USD: nbr of used BTSs (BTS and BCF unlocked)

. .

NUS: nbr of non-used BTSs (BTS or BCF locked) TRX

.

USD: nbr of used TRXs (TRX, BTS and BCF unlocked)

.

NUS: nbr of non-used TRXs (TRX or BTS or BCF locked)

.

CHN

.

USD: nbr of used Channels (CHN, TRX, BTS and BCF unlocked)

.

NUS: nbr of non-used Channels (CHN or TRX or BTS or BCF locked)

.

ADJ TOT: total nbr of adjacencies

- BSS network entity sums for each MR and sum over network sorted by . the number of BTS, for locked and unlocked BCF, BTS, TRX, CHN . . . . . . . .

BCF UNL: nbr of unlocked BCFs LCK: nbr of locked BCFs BTS UNL: nbr of unlocked BTSs LCK: nbr of locked BTSs TRX UNL: nbr of unlocked TRXs LCK: nbr of locked TRXs CHN UNL: nbr of unlocked Channels of TRX (includes signalling chns) LCK: nbr of locked Channels

- Averages of entities per higher object (used CHN,TRX,BTS counts applied) - Statistics on used channel types


NTC TAN 0935/2.3 en


50


NOTE: Running this report takes a while. Patience please.

------------------------------------------------------------------------------OMC, NSS Network Entity Summaries per Maintenance Region (Only objects that exist in the network are counted) ------------------------------------------------------------------------------OMC Maint.Region

OMC

OMC

FE

WS

HLR

MSC

tot

tot

tot

tot

tot

------------- ---- ---- ---- ---- ---non assign Global Scope

1 1

4

1

1

NonIntegrNW ---sum

---- ----

1

1

2

------------------------------------------------------------------------------BSS Network Entity Summaries per Maintenance Region ------------------------------------------------------------------------------ADJ Maint.Region

TC BSC

PCM

BCF

BTS

tot tot

tot

usd nus

usd

TRX nus

usd

CHN nus

usd

tot nus

in nw

------------- ---- --- ---- ---- --- ----- ---- ----- ---- ------ ----- -----NonIntegrNW

1

Global Scope

6

125

145

10

7

non assign

1

1

8

317

3

455

3

3640

24

3500

21

1

22

1

176

8

191

---- --- ---- ---- --- ----- ---- ----- ---- ------ ----- -----sum

6

135

152

1

338

5

477

5

3816

40

3691

usd = used (the object and all objects above are unlocked) nus = not used (the object or any object(s) above is locked) ------------------------------------------------------------------------------BSS Network Entity Summaries per Maintenance Region, Directly Locked and Unlocked BCF, BTS, TRX, CHN counts ------------------------------------------------------------------------------BCF Maint. Region

unl

BTS lck

unl

TRX lck

unl

CHN lck

unl

lck

------------- ----- ---- ----- ---- ----- ---- ------ ---non assign Global Scope

7

1

145

21

1

23

184

317

3

458

3664

1

1

8

NonIntegrNW

----- ---- ----- ---- ----- ---- ------ ---sum

152

1

338

5

482

3856

Note: These counts do not take into consid eration the state of the above objects. ------------------------------------------------------------------------------Transmission Element Summaries per Maintenance Region -------------------------------------------------------------------------------


NTC TAN 0935/2.3 en


51


Maint. Region

DMR

DN2

TRU

tot

tot

tot

------------- ---- ---- ---non assign NonIntegrNW Global Scope

5

4

10

---- ---- ---sum

5

4

20

------------------------------------------------------------------------------BSS Network Entity Averages per Maintenance Region ------------------------------------------------------------------------------avg

avg

avg

avg

avg

avg

avg

avg

avg

PCM

TC

BCF

BTS

TRX

BTS

TRX

TRX

ADJ

per

per

per

per

per

per

per

per

per

Maint. Region BSC

BSC

BSC

BSC

BSC

BCF

BCF

BTS

BTS

------------- ------ ----- ------ ------ ------ ----- ------ ---- -------non assign

2.8

NonIntegrNW

--

Global Scope

20.8

24.2

53.3

76.3

2.2

2.9 -3.2

1.0

8.7

1.0 1.4

10.9

Note: Only those objects are counted which are in use. ------------------------------------------------------------------------------Channel statistics for channels which are in use in the entire network, i.e. which are unlocked and the above TRX, BTS and BCF are unlocked. ------------------------------------------------------------------------------Channel

Channel

type

count

-------- ------MBCCH

135

MBCCHC

203

SDCCH TCHF

137 3341

Example 14. Report 090: Network configuration summary

6.6.4

How to Find Errors in Assignments

To find errors, you can verify that all objects under a BSC belong to the same MR as the BSC itself by running the report Maintenance region audit (064). The report shows you all deviations from this rule. Note that in some BSCs the rule may not be valid - the operator wants to organise the BSs under one BSC to different MRs. Also, often there is a 'Foreign BSC' which does not belong to any MR. This BSC is just a virtual BSC which is needed for handling the foreign BTSs that are needed to handle adjacencies to cells in another OMC (other vendor's OMC or another Nokia NMS/2000). An easy way to see how the BSC-BCF-BTS objects are assigned to MRs is to run the report All radio network ordered by BSC, BCF, BTS (042).


NTC TAN 0935/2.3 en


52


6.7

Setting the History Windows The size of the NMS/2000 database is limited by the size of the available disk space, and you must compromise when deciding which information is worth storing the longest. For setting up the history window in a NMS/2000, consult your System Administrator for creating an appropriate ‘do-delete.sql’ script and adding that to Cron job. The following table gives you an idea about storing lengths which have proven practical. Type of data

Storing period

Measurements

10 days In reports like UL Interference (190) it is necessary to see more than one week’s data in order to find out the repetition patterns.

Observations

3 days The observations are typically used for troubleshooting and do not need a long history.

As any user

The results are not used much because they do not contain the most interesting counters.

Alarms

10 days Mostly the alarm information is used on the spot but in some troubleshooting cases even a period of several weeks may prove useful. In the NMS/2000 release T10 the feature PM Thresholds allows you to generate alarms based on counters and these may be interesting to analyse.

Table 6. Example of History Windows in the NMS/2000 Database.

For long-term storage, the NMS/2000 provides the Network Data Warehouse feature.

6.8

Setting up the Base Station Groups If the division of the network into Maintenance Regions, BSSs and LAs does not fulfil the needs and a different grouping is temporarily needed, you can create and use the BTS groups when running the reports. Most of the BSS Network Doctor reports offer an option to select the BTS group.


NTC TAN 0935/2.3 en


53


6.8.1

Defining Groups by BSS Network Doctor Group Management

BSS Network Doctor provides a tool for creating and handling a table for the definition of BTS groups. A predefined set of BTSs is called a BTS group. Any BTS can belong to one or more groups. If the needed BTS group does not exist, refer to BSS Network Doctor, System Administrator’s Guide, for detailed instructions on how to create it. Once you have created the BTS group, you can use it when running the reports by choosing ‘BTS group’ option in BTS Area Selection. Since T10 this method is no longer the only way to create groups. A more sophisticated, generic and easy-to-use way is explained in the next section.

6.8.2

Defining Groups by Working Set Manager

With the Working Set Manager application in the NMS/2000 Top-level User Interface under the Utils → NMS Desktop menu, it is possible to create working sets that can contain any managed objects. Once you have created a working set and it contains BTSs, you can use it when running the BSS Network Doctor reports by choosing Working Set (manual, with BTSs) or Working Set (manual, with BCFs ) option in BTS Area Selection. Since Working Set Manager has been a standard feature of the NMS/2000 since T10, we recommend you to use that feature instead of the internal BTS grouping feature in BSS Network Doctor that requires better coordination when managing the groups. To see how to create working sets with the Working Set Manager, refer to Working Set Manager Help.


NTC TAN 0935/2.3 en


54

Consistency Checks

7

CONSISTENCY CHECKS The NMS/2000 database contains a lot of data which has to be consistent. If you use the NMS/2000 Top-level User Interface, the consistency needs to be checked in some cases. Discrepancies may occur in the following cases: •

Changes made using remote MML The Top-level User Interface may sometimes prove slow for making major changes in the network. Therefore you can use a remote MML to make big changes in the network configuration and a PC to run command files in the network elements. In fact, the PC is used as a service terminal and it also uses MML. In those situations, the BSC may not succeed in updating all the changes to the NMS/2000 database reliably.

•

Errors in the Radio Network Plan

Sometimes the radio network plan itself includes discrepancies. •

Errors in data insertion into the database

Sometimes errors are accidentally caused when inserting the data. Before you run the check on the reports, it is a good idea to upload radio network data from the network to make sure that the NMS/2000 database matches the situation in the network. In a large network, uploading takes quite a long time but if there is a suitable view containing all BTS sites, it can initiated for the whole network, and the task runs automatically. BSS Network Doctor supports the following types of checks: •

Adjacencies to non-existing cells

•

Adjacency discrepancies

•

Non-symmetrical adjacencies

•

Same or adjacent frequencies in the adjacent cells

•

Handover synchronisation between adjacent cells

•

Adjacent cell double frequency check

•

BTS audit

•

Checking the adjacency plan

•

Checking the frequency plan

•

Checking the administrative states


NTC TAN 0935/2.3 en


55

Consistency Checks

7.1

Adjacencies to Non-existing Cells Adjacencies may be created for cells which are under another OMC and therefore the cell itself is not found in the database. Sometimes an adjacency linked to a non-existing cell is a mistake. The report for checking this is Adjacencies to non-existing or foreign cells (065). = =

ADJACENCIES TO NON-EXISTING OR FOREIGN CELLS

= =

Network:

PLMN

=

Area:

IUO

=

Sorting key:

source BSC name, source BTS id

= =============================================================================== Normally every adjacency should be towards an existing cell. In this report all adjacencies are checked so that the adjacent cell (c_bts:ci, lac) really is found in the NMS/2000 database in the c_bts table. Discrepancies are reported. Instructions: Remove the incorrect adjacencies by the Top-level User Interface after comparing the report to the plan. Note that if the adjacent cell exists in another NMS/2000, no correction is needed. Note: Running this report takes a few minutes. Patience please. =============================================================================== Adjacencies to non-existing cells Source

Source

BSC (BTS id)

BCF/BTS

ADJ.CELL ADJ.CELL LAC

CI

--------------- -------------------- -------- -------BSC88(40)

Snow street

2165

BSC88(40)

Snow street

2165

BSC88(81)

Dirt street

25030

BSC74(2)

West centre

25145

1100

26026

1100

26027

1100

26027

1100

26026

Example 15. Report 065: Adjacencies to non-existing or foreign cells

Use the Top-level User Interface to remove any unnecessary adjacencies.

7.2

Adjacency Discrepancies There are a few parameters of the adjacency object which have to be the same as in the target cell. The report for checking this is Adjacency discrepancies (060).


NTC TAN 0935/2.3 en


56

Consistency Checks

= =

ADJACENCY DISCREPANCIES

= =

Network:

=

Area:

PLMN BSC: CITY

=

Sorting key:


= =============================================================================== This report lists the discrepancies of various parameters between the source cell adjacency parameters and target cell parameters. Impact of discrepancies: Any difference between two identical parameters of target BTS and the same parameter of adjacency usually results in handover failures between the source and the target BTSs. The first of each pair of lines indicates the adjacency of a source cell. The second line indicates the target cell. Parameters in the first line show the values in the adjacency (ADJ) of a source cell. Parameters in the second line (TGT) show the values in the target cell. The checked parameters are: Location Area Code (LAC), Cell Identity (CI), Frequency (FREQ), Maximum power of MS (MSTX), Network Colour Code (NCC) and Base Station Colour Code (BCC). These should be the same in the adjacent and the target cell. In case there is any kind of discrepancy indicated by the report, do the following: 1) upload adjacency data from the network for the blaimed BTSs. 2) run this check again 3) if discrepancies are still found, check and correct them via MML. =============================================================================== Adjacency discrepancies in Xxxx network LAC ===

CI ===

FREQ MSTX NCC BCC ===

==== === ===

Source BSC (BTSid) Source BCF/BTS

ADJ

ADJ

ADJ

ADJ

ADJ ADJ

Target BSC (BTSid

TGT

TGT

TGT

TGT

TGT TGT

Target BCF/BTS

------------------ ---------------------------- ------ ------ ---- ---- --- --BHHI1(58)

Site 22 / 1122

1100

1107

118

39

4

4

BTKE1(28)

Site 33 /1133

1100

1107

118

33

4

4

BHHI1(82)

Site 23 / 1141

1100

1107

118

39

4

4

BTKE1(28)

Site 44 /1107

1100

1107

118

33

4

4

Example 16. Report 060: Adjacency discrepancies

You should also check every discrepancy with MML commands. Use the Toplevel User Interface to resend or read the incorrect adjacencies from the network depending on which values are correct.


NTC TAN 0935/2.3 en


57

Consistency Checks

7.3

Non-symmetrical Adjacencies Normally all adjacencies are bidirectional or symmetrical. Non-symmetrical adjacencies are sometimes created by mistake. To find such adjacencies, run the report Non-symmetrical adjacencies (061). = =

NON-SYMMETRICAL ADJACENCIES

= =

Network:

PLMN

=

Area:

Group X

=

Sorting key:


= =============================================================================== This report shows all missing adjacencies assuming that all adjacencies should be symmetrical (bidirectional). The missing adjacencies are sorted

by BSCs and cell names.

The Maintenance region is checked for source cells. Instructions:

The missing adjacencies have to be checked with network

.

planners.

Running the report may take a moment. Patience please. =============================================================================== Nonsymmetrical adjacencies in PLMN network from cell

to cell

cell/bcf name

cell/bcf name

bsc name - bts id (ci,lac)

=x=>

bsc name - bts id (ci,lac)

----------------------------------- ---- ----------------------------------OKL-1/OKL

=x=> SiteA-1/SiteA

TownXX_BSC8-46 (22141,2901) OKL-2/OKL

TownXX_BSC8-31 (20461,2901) =x=> SiteA-1/SiteA

TownXX_BSC8-47 (22142,2901)

TownXX_BSC8-31 (20461,2901)

Example 17. Report 061: Non-symmetrical adjacencies

7.4

Same or Adjacent Frequencies in the Adjacent Cells Normally the adjacent cells should not have the same frequency as the source cell, or the adjacent frequency. This is necessary in order to avoid interference. To find any such occurrences, run the report Frequency check of adjacent cells (062). = =

FREQUENCY CHECK OF ADJACENT CELLS

= =

Network:

PLMN

=

Area:

Group: XX

=

Search selection:

only same adjacencies

=

Sorting key:


=


NTC TAN 0935/2.3 en


58

Consistency Checks

=============================================================================== This report displays all adjacencies where a cell and its adjacent cell have the same frequency (f) or adjacent (f-1 or f+1) frequency. The Maintenance region is checked for source cells. For each pair of frequencies also the administrative state (S) of objects (BCF, BTS, TRX) and the use of TRX (BCCH or TCH) is shown. Decoding of states (S): N= No state U= Unlocked S= Shutting down L= Locked Adjacent cells should never have same BCCH and BSIC. same frequencies should not be used in adjacent cells. Also the f-1 or f+1 situation should be avoided if possible. Note: If TRX is a BCCH TRX, the output power is maximal all the time. Note: Running this report for a large area takes a while. Patience please. =============================================================================== Adjacency frequency check in PLMN network Source

Source

Target

Target

******

******

******

******

(S)TRX_id(use)

BSC

(S)TRX_id(use)

BSC

(S)BTS_name

BTS id (CI,LAC)

(S)BTS_name

BTS id (CI,LAC)

(S)BCF

freq, NCC, BCC

(S)BCF_name

freq, NCC, BCC

-------------------- ---------------- -------------------- ---------------(U)1(BCCH)

Town X_BSC0

(U)1(BCCH)

Town X_BSC1

(U)Forest site-1

4 (20111,2901)

(U)Site F-1

55 (20381,2902)

(U)Forest site

56,4,5

(U)Site F

56,4,0

(U)1(BCCH)

Town X_BSC0

(U)1(BCCH)

Town X_BSC0

(U)Forest site-1

4 (20111,2901)

(U)West Harbours -1

13 (20151,2901)

(U)Forest site

56,4,5

(U)West Harbours

55,4,4

Example 18. Report 062: Frequency check of adjacent cells

A similar report, Adjacent cells with the same or adjacent frequency, IUO super TRX excluded (405) is available separately for IUO cells, too.

7.5

Handover Synchronisation Between Adjacent Cells Normally all adjacencies between cells in the same BTS site are synchronous for HO and adjacencies between cells in different BTSs should be non-synchronous for HO. If the adjacent cell is in the same BTS site but is not synchronous, the load on BTS processing is increased because the MS needs to request: •

the BTS timing advance

•

power level for the handover.


NTC TAN 0935/2.3 en


59

Consistency Checks

This is not serious, but can be avoided. If the adjacent cell is not in the same BTS site but adjacency is synchronous, calls will fail. For handover synchronisation between adjacent cells, run the report Handover synchronisation (067). = =

HANDOVER SYNCHRONISATION

= =

Network:

=

Maintenance Region: Ghost Town

PLMN

=

BTS group:

group selection bypassed

=

Sorting key:


= =============================================================================== Normally all adjacent cells in the same site are synchronous for HO. This report lists all adjacencies - which are in the same BS site but are not synchronous .

This is not serious but increases the load on BTS processing

- which are not in the same BS site but are synchronous .

This is serious and may result in call failures

Input parameters: Maintenance Region, BTS group, Sorting key Instructions: To correct the error, use the Top-level User Interface > Configuration Management or BSC MLL (command ZEAM:BTS=xx:LAC=yy,CI=zz:SYNC=aa;) =============================================================================== Adjacencies between cells in the same BS but not synchronous Source

Source

Target

Target

Target

*************** *************** *************** *************** ****** BSC (BTS id)

BCF

BSC (BTS id)

BTS

BCF

CI

BTS

LAC

SYN

--------------- --------------- --------------- --------------- ------ --BSC111

Phantom st

BSC111

Phantom st

30102

(11)

3358

(12)

30102

15000

BSC111

Phantom st

BSC111

Phantom st

(12)

30102

(11)

3358

3358

No

No

15000

Adjacencies between cells in the different BS but synchronous Source

Source

Target

Target

Target

*************** *************** *************** *************** ****** BSC (BTS id)

BCF

BSC (BTS id)

BTS

BCF

CI

BTS

LAC

SYN

--------------- --------------- --------------- --------------- ------ --BSC14

Spirit st

BSC14

Tomb st

6394

(26)

6260

(27)

6394

2000

BSC14

Tomb st

BSC14

Spirit st

6260

(27)

6394

(26)

6260

2000

BSC15

Graveyard st 1

BSC15

Graveyard st 2

6289


NTC TAN 0935/2.3 en


Yes

Yes

Yes

60

Consistency Checks

(64)

6282

(65)

6289

1700

Example 19. Report 067: Handover synchronisation

To correct the error, open an MML session to the BSC in question and enter: ZEAM:BTS=xx:LAC=yy,CI=zz:SYNC=aa;

7.6

Adjacent Cell Double Frequency Check If two cells are neighbours of one and the same cell, they are obviously not located far from each other. If these cells have the same frequency, interference may occur. To see if there are any such incidents, run the report Adjacent cell double frequencies (069). = =

ADJACENT CELL DOUBLE FREQUENCIES

=

Network:

=

Maintenance Region: all MRs

=

BTS group:

PLMN Test cells

= =============================================================================== This report lists all cells having adjacent cells with the same frequency. This is a potential source of interference. Note: Every occurrence is listed twice. Input parameters: BTS area Instructions:

The reported pairs of target cells have to be checked

.

with network planners.

Running report takes a moment. Patience please. =============================================================================== Target1

Target2

Source

Source

BSC (BTS id)

BSC (BTS id)

BSC

BCF

BCF

BCF

(BTS id)

BTS

BTS

BTS

Freq

------------ ---------------- ------------------ ------------------ ----BSC53

Cave hill

BSC53(41)

BSC53(10)

(47)

1100

Harbour

Gardens

3104

1187

BSC53

Cave hill

BSC53(10)

BSC53(41)

(47)

1100

Gardens

Harbour

1187

105

105

3104

Example 20. Report 069: Adjacent cell double frequencies

Let a network planner first check if the reported cases can be a problem. A correction needs a new frequency for one of the cells and may so easily lead into the need for a new plan over the area.


NTC TAN 0935/2.3 en


61

Consistency Checks

7.7

Non-unique CI and LAC Normally the CI-LAC pair should be unique throughout the entire network. Run report Non-unique CI and LAC (066) to see all those CI-LAC pairs that are used more than once. BTS name LAC

CI BSC name (BTSid)

BCF name (BCF id)

(int_id)

------- ------- ---------------------- ------------------- --------------1200

3257 BSC41(81)

Green Hill(16)

3257 (42525)

BSC41(57)

Rapids(56)

3257 (77188)

Example 21. Report 066: Non-unique CI and LAC

7.8

Base Station Audit Most of the BCFs, BTSs, HOCs, POCs and even some adjacency parameters have the same value network-wide. It is up to the network planning to define the standard parameters. Before you run these reports, upload the data from the network. This will ensure that the data the data in the NMS/2000 database is valid.

7.8.1

Area Level Counts

The report BTS parameter survey (068) gives you a good overview of the default settings in the network or part of it. Because the output of this report is long, the model presented here is shortened. = =

BTS PARAMETER SURVEY

= =

Network:

PLMN

=

Selected area:

BSC - BSC_SSSSS

= =============================================================================== This report shows the usage of the parameters in the network or part of it. Instructions: Use the report 063 to find out the parameter differences on the BTS level. NOTE: This report does not include any parameters that enable handover. =============================================================================== ******************************************************************************* BSC Parameters *******************************************************************************


NTC TAN 0935/2.3 en


62

Consistency Checks

No of Preferred Cells (NPC)

COUNT

--------------------------------------------------

----------

1

1

GSM macrocell threshold (GMAC)

COUNT

--------------------------------------------------

----------

4

1

(SHORTENED)

******************************************************************************* BTS Identification Parameters ******************************************************************************* Network Colour Code (NCC)

COUNT

--------------------------------------------------

----------

0

42

5

33

BTS Colour Code (BCC)

COUNT

--------------------------------------------------

----------

3

15

0

14

1

10

2

9

4

9

5

9

6

6

7

3

Mobile Country Code (MCC)

COUNT

--------------------------------------------------

----------

XXX

75

(SHORTENED)

******************************************************************************* Cell Access Parameters ******************************************************************************* Cell Barred (BAR)

COUNT

--------------------------------------------------

----------

No

75

Call Reestablishment Allowed (RE) --------------------------------------------------

COUNT ----------

Yes

71

No

4

Emergency Call Restricted (EC)

COUNT

--------------------------------------------------

----------

No

75

Power Offset (PO)

COUNT

--------------------------------------------------

----------

0

75

ncc_0 ncc_1 ncc_2 ncc_3 ncc_4 ncc_5 ncc_6 ncc_7

COUNT

----- ----- ----- ----- ----- ----- ----- ----- ---------*

*

71

*

3

*


NTC TAN 0935/2.3 en

1


63

Consistency Checks

Note : '*' means the plmn is permitted.

AC0

AC1

AC2

AC3

AC4

AC5

AC6

AC7

COUNT

----- ----- ----- ----- ----- ----- ----- ----- ---------*

*

AC8

AC9

* AC10

* AC11

* AC12

* AC13

* AC14

* AC15

75 COUNT

----- ----- ----- ----- ----- ----- ----- ----- ---------*

*

*

*

*

*

*

*

75

Note : '*' means the access class is allowed. (The report continues here; all parameters covered)

Example 22. Report 068: BTS parameter survey

7.8.2

BTS Level Deviations

The report BTS audit (063) is network dependent because the band (GSM900, GSM1800, GSM1900) specific default values are defined in the database. These default values should be modified according to the network to receive the shortest output. To work with this report: 1.

Select the cell which has correct parameters for the band used and run the report. Discuss the output with the network planning engineers to agree on the default values.

2.

Change the settings in the NMS/2000 database using the Top-level User Interface according to the radio network plan.

3.

Select a BTS area and run the report again to reveal the deviations.

As the output of the report is long, only an extract of it is shown here. = =

BTS AUDIT

= =

Network:

PLMN

=

Area:

BSC - BSC_1

=

Band:

GSM900

=

Parameter set : All

= =============================================================================== The checking is done against the defaults listed below. All discrepancies are reported. The comparison is made against the defaults stored in the NMS/2000 database. If the defaults are not yet generated, they are inserted by this script. There is one default set for each of the three possible bands: GSM900, GSM1800, GSM1900. The defaults can be modified by using GUI. Instructions: 1) Run this report against a cell that you would like to use as default.


NTC TAN 0935/2.3 en


64

Consistency Checks

Then you will see how the defaults differ from the model cell. 2) Correct the defaults by using GUI 3) Run over larger area of cells NOTE: The checking will take long time if large area selected. Patience please. =============================================================================== ******************* BSC PARAMETER AUDIT ******************* =============================================================================== = "No of Preferred Cells" checking =============================================================================== No of Preferred Cells specifies the number of preferred cells the BSC should include in a Handover Required Message sent to the MSC. Defaults:

1 (GSM900),

Name in BSC:

NPC

Name in NMS dbase:

no_of_pref_cells

Name in NMS GUI:

No of PrefCells

1 (GSM1800),

1 (GSM1900)

=============================================================================== = "GSM macrocell threshold" checking =============================================================================== Defaults:

4 (GSM900),

4 (GSM1800),

Name in BSC:

GMAC

Name in NMS dbase:

gsm_macrocell_th reshold

Name in NMS GUI:

GSM Macrocell Threshold

4 (GSM1900)

=============================================================================== = "GSM microcell threshold" checking =============================================================================== Defaults:

5 (GSM900),

5 (GSM1800),

Name in BSC:

GMIC

Name in NMS dbase:

gsm_microcell_th reshold

Name in NMS GUI:

GSM Microcell Threshold

5 (GSM1900)

=============================================================================== = TRXs WITH NON ALLOWED FREQ. IN THE NETWORK (freq. >

1023 )

=============================================================================== Every operator has only a limited number of frequencies in use. Having accidetally a cell with frequency out of this band will interfere the other operators. Wrong

frequencies:

=============================================================================== = TRXs WITH NON ALLOWED FREQ. IN THE NETWORK (freq. <

1 )

=============================================================================== Every operator has only a limited number of frequencies in use. Having accidetally a cell with frequency out of this band will interfere the other operators. Wrong

frequencies:

Example 23. Report 063: BTS audit


NTC TAN 0935/2.3 en


65

Consistency Checks

7.9

Checking the Adjacency Plan To check that the adjacency plan is implemented correctly in the NMS/2000, run the report Adjacencies of cells (074) and compare the plan and the report manually. This is, however, a time-consuming job because a typical cell has on average 5 to 10 adjacencies. As this report produces a very long output, it should not be run unnecessarily for a large area. = =

ADJACENCIES OF CELLS

= =

Network:

PLMN

=

Area:

BSC - BSC3NYK

=

Sorting:

BSC name, BTS id, frequency

= =============================================================================== For each adjacency the following parameters are output. LAC

Location Area Code of the target cell.

CI

Cell Identification of the target cell.

BCC

Base Station Colour Code of the target cell.

FREQ

BCCH frequency of the target cell.

===============================================================================

BSC name

BCF name

Adj. BCF name

(BTS id)

BTS name

Adj. BTS name

Band

Adj. BTS band

LAC

CI

BCC

FREQ

---------- --------------- --------------- ------ ------ ---- ----BSC3NYK

HATANP001

HATANP001

(1)

HATANP3001

HATANP30002

GSM1800

GSM1800 HATANP001

HATANP30003

GSM1800

BSC3NYK

HERMIA004

HERMIA003

(10)

HER3AD3010

HER3CG3007

GSM1800

GSM900 HERMIA003

HER3CG3008

GSM900

3

30002

0

594

3

30003

0

596

3

30007

4

28

3

30008

4

82

Example 24. Report 074: Adjacencies of cells

Sometimes there are too many or too few adjacencies defined in the plan. Adjacencies can also be accidentally implemented. Adjacency problems can be easily detected by running the report BTSs with maximum number of adjacencies (070), BSC (BTS id)


NTC TAN 0935/2.3 en

Adjacency BCF

BTS


Count

66

Consistency Checks

-------------------- --------------- --------------- --------BSC33(15)

Linnanmaki

3127

28

BSC33(14)

Linnanmaki

2166

27

BSC33(48)

Haukkavuori

2124

26

Example 25. Report 070: BTSs with maximum number of adjacencies

or the report BTSs with minimum number of adjacencies (071). BSC (BTS id)

Adjacency BCF

BTS

Count

-------------------- --------------- --------------- --------XXX_BSC_1(35)

204

XDDG1

5

XXX_BSC_1(40)

212

XDDG1

5

XXX_BSC_1(41)

216

XDDG1

5

XXX_BSC_1(50)

306

IDDG1

5

XXX_BSC_1(44)

304

IDDG1

6

Example 26. Report 071: BTSs with minimum number of adjacencies

You may check the adjacency plan also with the help of the Undefined Adjacent Cell measurement. You can see the defined and undefined adjacencies of a particular cell with the help of the report Defined, undefined and used adjacencies of a cell (072). = =

DEFINED, UNDEFINED AND USED ADJACENCIES OF A CELL

= =

Network:

PLMN

=

BSC:

BSC1

=

BTS id, BTS name:

(11) PORT1011

=

BTS CI:

=

BTS LAC:

=

Period:

10011 1 from 19980504 to 19980504

= =============================================================================== This report shows the defined adjacencies (from the NMS/2000 database) and undefined adjacencies as seen and reported by a BSC. =============================================================================== = = =

UNDEFINED ADJACENT CELLS OF BTS BSC1

bts id:11

name:PORT1011

from 19980504 to 19980504

=============================================================================== NOTE: This measurement is an optional feature in the BSC. NCC

13003

Nework Colour Code of undef.adj.cell .

BCC

13003

Base Sation Colour Code of undef.adj.cell .

BCCH

13003

BCCH carrier number (ARFN)

BA CHGD

13000

BA changed during the period.

AVG DL SIG STR

13001

Average DL signal strength received from

.

undefined cell.

=============================================================================== -


NTC TAN 0935/2.3 en


67

Consistency Checks

=============================================================================== = =

BTS ADJACENCIES

= =

BSC:

BSC1

=

BTS id:

11

=

BTS name:

PORT1011

=

Period:

from 19980504 to 19980504

= =============================================================================== BSC

OMC Name

Description

===

========

===========

LAC

LAC

Location Area Code of the target cell.

CI

CellID

Cell Identification of the target cell.

FREQ

BCCH Freq

BCCH frequency of the target cell.

BCC

BSIC

Base Station Colour Code of the target cell.

NCC

BSIC

Network Colour Code of the target cell.

SYNC

Synchronized

Indicates if synchronizatio n used.

PRI

HO priority level

Relative Priority level of the target cell.

SL

Rx Lev Min Cell

Mininimum signal level to make HO to the

Ms Tx Pwr Max Cell

Maximum transmit power MS can use in the

. PMAX

target cell.

.

target cell.

PMRG

HO Margin PBGT

Power Budget HO margin.

QMRG

HO Margin Qual

Prevents repetitive HOs. Used when bad

HO Margin Level

Prevents repetitive HOs. Used when low

HO Level Umbrella

Value of this param. is used instead of

Enable HO Margin Lev Qual

Indicates if Ho Margin Level and HO Margin

HO Load Factor

The relative priority of the adjacent cell

. LMRG

quality causes HO.

. AUCL

signal level causes HO.

. MRGS

RxLevMinCell if adj.cell is umbrella cell

. OF

Qual are considered in HO process.

.

is decreased in case the cell is considered

.

overloaded.

POPT

MS pwr optimization

Indicates whether the RF power level the MS

.

uses in the new cell after HO is optimized

.

(related to optional feature 140 in BSC)

LEV

UL level

Indicates the desired UL level after HO when

.

level is optimized optimized

.

(related to optional feature 140 in BSC)

CHAIN Chained adj. cell

Indicates whether an adjacent cell is defined

. TRHO

as a chained cell. Threshold target level

Defines minimum signal level when a handover

.

caused by traffic reason is allowed to an

.

adjacent cell.

FMT

Fast moving threshold

. ACL

Threshold to compared with the indentificatio n in the adjacent cell.

Adjacent cell layer

. .

Adj. cell layer in relation to serving cell. NU = Not Used, SL = Same Layer, UL = Upper Layer, LL = Lower Layer

USED

'*' = adjacency has been used (1 or more attempts)

.

'-' = adjacency not used (0 attempts or no Ho adj.

.

cell measurment not available)

===============================================================================

Outgoing adjacencies ******************** C


NTC TAN 0935/2.3 en


68

Consistency Checks

TO:

S

P A

M

P

H T

U

BTS

LAC

Y

P

PMRG

M U

R

O

L A R

F

A

S

BCF

CI

NCC

N

R

S LMRG

A C

G

O

P

E I H

M

C

E

BSC (BTS)

FREQ BCC

C

I

L QMRG

X L

S

F

T

V N 0

T

L

D

--------------- ---- ---- - -- ---- ---- --- --- - -- ---- ---- - ---- -- -- PORT1012

1

7

PORT007

1001

1

BSC1

2

(12)

604

PORT1013

1

7

PORT007

1001

1

3

(13)

599

KKALLI1015

1

7

PORTNKALLIO008

1001

2

BSC1

5

(15)

592 1

7

1001

1

6

30 n/a N

0 -110 -110 N NU

0

NU -

30 n/a N

0 -110 -110 N NU

0

NU *

30 n/a N

0 -110 -110 N NU

0

NU -

30 n/a Y

1 -110 -110 N NU

0

NU -

F

A

0

N

3 -110

6 0

N

3 -110

6 0 0

PORTNKALLIO008

597

6

0

KKALLI1016

(16)

3 -110

0

BSC1

BSC1

N

N

3 -100

6 3 0

Incoming adjacencies ******************** C FROM:

S Y

P

PMRG

P A

M

P

H T

M U

R

O

L A R

U

BTS

LAC

S

BCF

CI

NCC

N

R

S LMRG

A C

G

O

P

E I H

M

C

E

BSC

FREQ BCC

C

I

L QMRG

X L

S

F

T

V N 0

T

L

D

--------------- ---- ---- - -- ---- ---- --- --- - -- ---- ---- - ---- -- -- PORT1012

1

7

PORT007

1001

1

BSC1

2

N

3 -110

6

30 n/a N

0 -110 -110 N NU

0

NU -

30 n/a N

0 -110 -110 N NU

0

NU -

30 n/a N

0 -110 -110 N NU

0

NU -

30 n/a Y

1 -110 -110 N NU

0

NU -

0 0

594 PORT1013

1

7

PORT007

1001

1

BSC1

3

N

3 -110

6 0 0

594 KKALLI1015

1

7

PORTNKALLIO008

1001

1

BSC1

5

N

3 -110

6 0 0

594 KKALLI1016

1

7

PORTNKALLIO008

1001

1

BSC1

6

N

3 -100

6 3 0

594 =============================================================================== = =

HANDOVER ADJACENT CELL

= =

BSC:

=

BTS id:

11

=

BTS name:

PORT1011

=

Period:

from 19980504 to 19980504


NTC TAN 0935/2.3 en

BSC1


69

Consistency Checks

= =============================================================================== NOTE: This measurement is an optional feature in the BSC. NOTE: The CI, LAC reported are as seen by BSC. Check that the cells listed .

are in the adjacenies. If not then upload data from nw and rerun this

.

report. If not corrected turn to OMC support engineers.

LAC

15000

Location Area Code

CI

15000

Cell Identifier

HO => Att

15001

Outgoing HO attempts

HO => Fail (%)

hfr_58

Outgoing HO failure ratio of non blocked attempts

HO => Blck (%)

blck_19

Outgoing HO blocking

(S6)

HO <= Att

15003

Incoming HO attempts

HO <= Fail (%)

hfr_59

Incoming HO failure ratio of non blocked attempts

HO <= Blck (%)

blck_20

Incoming HO blocking (S6)

=============================================================================== Source

Target

******

******

BTS NAME

HO=> HO=>

BCF NAME

HO=> **** ****

BSC NAME

***** Fail Blck

(BTS)

Att

(%)

(%)

<=HO <=HO Target BTS NAME <=HO **** **** ****** BCF NAME ***** Fail Blck LAC Att

(%)

(%) CI

BSC NAME (BTS)

--------------- ------ ---- ---- ------ ---- ---- ------ ---------------PORT1011

7

0

0

8

0

PORT007

0 1 10013

PORT1013 PORT007

BSC1

BSC1

(11)

(13 )

Example 27. Report 072: Defined, undefined and used adjacencies of a cell

To see the results of undefined adjacent cells measurement for all BTSs in an area, run the report Undefined adjacent cells (073). = =

UNDEFINED ADJACENT CELLS

= =

Network:

PLMN

=

Area:

All BTSs selected

=

Period:

from 19990217 to 19990217

= =============================================================================== This report gives all undefined adjacent cells (cells measured but not being defined as neighbours) for all BTSs in the selected area. You can use this information to check the network plan for adjacencies. NCC

/c13003

Nework Colour Code of undef.adj.cell .

BCC

/c13003

Base Station Colour Code of undef.adj.cell.

BCCH

/c13003

BCCH carrier number (ARFN)

AVG DL SIG STR

/c13001

Average DL signal strength received from

/c13002

Nbr of samples for calculating the average

. SAMPLES .

undefined cell. DL signal stregth.

Note: Undefined cells measurement is an optional feature in the BSC. Note: Running this report takes a while. Patience please.


NTC TAN 0935/2.3 en


70

Consistency Checks

=============================================================================== BSC Name BTS Name

BCCH

NCC

BCC AVG DL SIG STRENGTH

SAMPLES DD HH

--------------- ----- ---- ---- ----------------------- ---------- -- -BSC2UPS1

599

7

1 from -96dBm to -95dBm

9 17 11

592

7


67 17 11

1UPS2004

BSC2UPS1 1UPS2005

from -102dBm to -101dBm

BSC2UPS1

41 17 12


111 17 13


558 17 14

592

7


8 17 14

599

7


35 17 12


2 17 14

1UPS2006

BSC2UPS1

78

6

2 less than -110dBm

2 17 14

PERTTG2023

Example 28. Report 073: Undefined adjacent cells

For the BTSs with maximum number of adjacencies between LAs (075) report no measurement is used but the data is retrieved from CM tables. Note that adjacencies between LAs can cause numerous location updates. BTSs with max nbr of adjacencies to different LA Nbr of adjacencies to cells in different BSC (BTS id)

BCF

BTS

Location Area

------------------ --------------- --------------- -------------------BSC_XXXXX(36)

078A

ABCWW

13

BSC_XXXXX(33)

111

CDCMM

9

BSC_XXXXX(25)

215

XOUWW

8

BSC_XXXXX(26)

209

XBRWW

8

BSC_XXXXX(18)

040

SWWMM

7

BSC_XXXXX(52)

339

IWIWW

7

BSC_XXXXX(54)

207

XNOWW

7

BSC_XXXXX(44)

304

ISHWW

7

BSC_XXXXX(31)

111

CDCWW

7

BSC_XXXXX(2)

028

TTTQQ

7

BSC_XXXXX(23)

214

XTAWW

7

BSC_XXXXX(24)

208

XTOWW

6

BSC_XXXXX(7)

030

LKPWW

6

BSC_XXXXX(59)

337

ISAWW

6

Example 29. Report 075: BTSs with maximum number of adjacencies between LAs


NTC TAN 0935/2.3 en


71

Consistency Checks

7.10 Checking the Frequency Plan The frequency plan is the basic setting of the network. Since the plan is very often inserted manually via the NMS/2000, errors may easily occur. To check the plan manually, use the report Frequency plan (111). = =

FREQUENCY PLAN

= =

Network:

PLMN

=

Area:

All BTSs selected

=

Sorting key:

freq, bcc

= =============================================================================== This report shows the BTS configurations of a Maintenance Region for frequenci es. Decoding of states: N = No state U = Unlocked S = Shutting down L = Locked TRX use: BCCH = BCCH used in TRX TCH

= BCCH not used in TRX

Hopping

If Rf hopping is used then just the MA list id is shown and

.

MA list can be found in the end of the report

Running this report takes a while. Patience please. =============================================================================== Frequency plan. All BTSs selected BCF BTS BSC name

BTS name

TRX

TRX

BTS id

BCF name

id

Freq

TRX BCC

NCC use

TRX states Hopping

-------------- ---------------- ---- ----- ---- ---- ---- ------ ---------BSC3

RER3CG3007

(7)

RERMIA003

BSC3

RER3CG3008

(8)

RERMIA003

BSC3

FATANP3001

(1)

FATANP001

BSC1

DANDPD1019

(19)

DANDPD010

2

1

4

7 TCH

UUL

None

4

124

4

7 TCH

UUL

None

2

592

0

7 BCCH UUU

Baseband

2

592

1

7 BCCH UUU

Rf (14)

Carrier frequencies of the MA list id for RF hopping MA list id

Frequency

---------- ---------


NTC TAN 0935/2.3 en


72

Consistency Checks

14

601 769 778

Example 30. Report 111: Frequency plan

7.11 Checking the Administrative States The administrative state of a radio network element (BCF, BTS, TRX, Channel) can be unlocked, locked or in the process of shutting down. It would be wise to regularly check that only elements which are planned to be locked, are actually locked. This is easy to do by running the report Find locked BCFs, BTSs, TRXs and channels (050). = =

FIND LOCKED BCFs, BTSs, TRXs AND CHANNELS

= =

Network:

PLMN

=

Maintenance Region: TownXX

= =============================================================================== This report lists - all locked BCFs - all locked BTSs - all locked TRXs - all locked channels Decoding of states: N= No state U= Unlocked S= Shutting down L= Locked TRX use: BCCH = BCCH used in TRX TCH


Input parameters: none =============================================================================== Locked BCFs BCF BSC name

BCF name

nbr

--------------- --------------- --TownXX_BSC9

Site xxcc

12 Locked BTSs (BCF unlocked) BCF/BTS BCF BTS

BSC name

BCF name

BTS name

states

id

id

--------------- --------------- --------------- ------- --- --TownXX_BSC5

SiteAAD

SiteAAD-3

UL

16

48

SiteBBN

SiteBBN-3

UL

9

27

Locked TRXs (BCF and BTS unlocked)


NTC TAN 0935/2.3 en


73

Consistency Checks

BSC name

BCF/BTS/ BCF name

BTS name

TRX

BCF BTS TRX TRX

states

id

id

id

use

--------------- --------------- --------------- -------- --- --- --- ---TownXX_BSC0

SiteRRTT

SiteRRTT-

UUL

21

61

1

TCH

OMNI

Note that the Maintenance Region is verified using the BTS object not TRX object or Channel object.

Example 31. Report 050: Find locked BCFs, BTSs, TRXs and channels


NTC TAN 0935/2.3 en


74

Quality of the Radio Network Plan

8

QUALITY OF THE RADIO NETWORK PLAN The quality of the radio network plan indicates the ability of the network to perform during normal load. To check how well your radio network plan functions, use the following indicators: •

SDCCH drop call ratio (or SDCCH success ratio)

•

TCH drop call ratio (or TCH success ratio)

•

HO failure ratio

When these measurements are run for the first time from the NMS/2000, they do not only cover the problems related to radio network planning but also the problems resulting from mistakes in the deployment of the plan into the network. Normally the first step is to correct those mistakes before going on to search for the possible errors in the radio network plan itself. Trying to spot and correct the mistakes made in the implementation can be a very time-consuming job. To see the daily values for the quality of the radio network plan on the BTS area level, run the report Performance statistics (benchmark) (200). Only part of the report is shown here. SDCCH

SDCCH

SDCCH

TCH

TCH

access access success success

access

access

access success success

probab probab

probab

probab

probab

(%) Day MMDD

SDCCH ratio

ratio

TCH

TCH ratio

TCH ratio

(%)

(%)

(%)

(%)

(%)

(%)

(%)

(%)

csf_1 csf_1a

csf_2a

csf_2f

csf_3j

csf_3i

csf_3k

csf_4o

csf_4p

--- ---- ------ ------ ------- ------- ------- ------- ------- ------- ------tue 1124

99.21

99.21

98.31

95.24

99.88

99.88

99.93

97.22

97.50

mon 1123

99.72

99.72

98.39

95.33

99.95

99.95

99.99

97.40

97.68

sun 1122

99.82

99.82

98.34

95.67

99.98

99.98

99.99

97.45

97.70

sat 1121

99.83

99.83

98.43

95.61

99.95

99.95

99.99

97.40

97.67

fri 1120

99.83

99.83

98.43

95.25

99.93

99.93

99.98

97.39

97.68

Avg

Day MMDD

TCH

HO/

TCH

call

AG

Call

time

Calls

Usage

lgth

block

bids

(hr)

(%)

(%)

(sec)

(%)

trf_39 trf_24c trf_13d

trf_3 trf_2b blck_13

--- ---- --------- ------- ------- ------- ------ ------tue 1124

129685

1934

313.43

8.52

54

0.000

mon 1123

140622

2093

315.64

8.83

54

0.000

sun 1122

122719

1837

230.91

7.75

54

0.000

sat 1121

130532

1953

231.29

8.26

54

0.000

fri 1120

134422

1994

230.00

8.41

53

0.000

Example 32. Daily values as shown in report 200, Performance statistics (benchmark).

If you need averages only, use the report Network benchmark statistics (204).


NTC TAN 0935/2.3 en


75


CALL SUCCESS FACTORS ==================== SDCCH access probability .

(before FCS) ................ ............./c sf_1

99.64 %

.

(after FCS) .............. .............../ csf_1a

99.64 %

SDCCH success ratio .

(SDCCH fail based, incl.LU) ............./ csf_2a

98.62 %

.

(SDCCH to TCH based) ............... ...../csf_2f

96.05 %

TCH access probability .

(before DR and queuing) ............... ../csf_3j

98.24 %

.

(before DR) .............. .............../ csf_3i

98.24 %

.

(real) .............. ............... ...../csf_3k

98.24 %

TCH success ratio .

(before re-est.) .............. ........../csf_4 o

97.61 %

.

(after re-est) .............. ............/cs f_4p

97.96 %

Note: See the formula descriptions for the accuracy limitations. Note: For a cell level list, run the report 250.

Example 33. Averages as shown in report 204, Network benchmark statistics.

8.1

SDCCH Drop Ratio Note that in SDCCH drops, most Abis failures are usually ghost RACH accesses.

8.1.1

SDCCH Drop Ratio on Area Level

For SDCCH drop ratio, run the report Performance statistics (benchmark) (200), and if interested in the averages and components, use the report Network benchmark statistics (204). SDCCH failures ============== SDCCH seizures .............. ................ ./trf_54 SDCCH drop ratio ............... ............../s dr_1a

1299149 6.14 %

. SDCCH_RADIO_FA IL.............. .............../ c1003

16729

(

1.29 %)

. SDCCH_A_IF_FAI L_CALL.......... .............../ c1078

338

(

0.03 %)

. SDCCH_ABIS_FAI L_CALL.......... .............../ c1075

62639

(

4.82 %)

. SDCCH_USER_ACT ................ .............../ c1037

4

(

0.00 %)

. SDCCH_BCSU_RES ET.............. .............../ c1038

0

(

0.00 %)

. SDCCH_NETW_ACT ................ .............../ c1039

0

(

0.00 %)

. SDCCH_BTS_FAIL ................ .............../ c1036

0

(

0.00 %)

. SDCCH_LAPD_FAI L............... .............../ c1035

0

(

0.00 %)

. SDCCH_RF_OLD_H O........(HO drop)........... ../c1004

0

(

0.00 %)

. SDCCH_ABIS_FAI L_OLD....(HO drop)........... ../c1076

0

(

0.00 %)

. SDCCH_A_IF_FAI L_OLD....(HO drop)........... ../c1079

0

(

0.00 %)

Note: For cell level list run the report 166.

Example 34. Averages and components of SDCCH failures as shown in report 204, Network benchmark statistics.


NTC TAN 0935/2.3 en


76


8.1.2

SDCCH Drop Ratio on BTS Hit List

For SDCCH drop ratios per cell, run the report SDCCH drop ratio per cell (166). = =

SDCCH DROP RATIO PER CELL

= =

Network:

PLMN

=

Area:

BTS GRP - LUCKY_PLACE

=

Period:

from 19970201 to 19970201

=

Threshold:

>=

1 % drop ratio

= ===============================================================================

The detailed report gives the following figures sorted out by drop-out ratio for all cells: Drops

/sdr_1

ratio SDCCH drops/SDCCH seizure attempts

SDCCH Bids

/c1000

SDCCH seizure attempts

SDCCH Ghosts

/c3030

Rejected ghost seizures.

.

The real amount of ghosts is about 8/3*counter303 0

.

in GSM ph.1!

Ghost (%)

/sdr_3

.

Ghost rejected before SDCCH seizure due to illegal establishment cause.

SDCCH Drop ratio (in ratio to SDCCH bids): Rf (%) call

/c1003

Drops due to Radio failure during call

Rf (%) old

/c1004

Drops due to Radio failure in HO

A bis (%) call

/c1075

Drops due to 'Abis' failure during call

.

(e.g. Ghosts having legal establishment cause)

A bis (%) old

/c1076

Drops due to 'Abis' failure in HO

Aif (%) call

/c1078

Drops due to 'Aif' failure during call

Aif (%) old

/c1079

Drops due to 'Aif' failure in HO

Lapd (%)

/c1035

Drops due to Lapd problems

BTS (%)

/c1036

Drops due to BTS problems

User (%)

/c1037

Drops due to user actions

BCSU (%)

/c1038

Drops due to BCSU reset

Cnfg act (%)

/c1039

Drops due to radio network configuration

Measurement used: p_nbsc_traffic, p_nbsc_res_access Note: This report covers calls in the SDCCH phase. Note: Phantom seizures having a legal establishment cause are included in the .

the number of SDCCH attempts and the failure ratio for calls is therefore

.

worse than in reality. Especially in the low traffic cells the SDCCH

.

failure ratio gets high due to the phantoms. The number of rejected

.

phantom seizures are shown separately.

Note: SDCCH seizures are not only calls but also LUs, SMSs, Imsi detaches etc. Note: Running this report takes a while. Patience please. =============================================================================== SDDCH drops per cell from 19970201 to 19970201


NTC TAN 0935/2.3 en


77


A Rf

bis

Aif

(%)

(%)

(%)

SDCCH

BTS

****

****

****

Lapd

Usr

Cfg

BCF

call

call

call

BTS

BCSU

act

BSC (BTSid)

old

old

old

(%)

(%)

(%)

Drops ******* total Bids (%) Ghosts /sdr_1 Ghost(%)

------------------ ------ ------ ------ ------ ------ ------ ------ --------Sect1

3.4

7.6

0.1

0.0

0.0

030

0.0

0.0

0.0

0.0

0.0

0.0

11

3010 21

ABC_BSC_1 (7)

1%

Sect2

2.0

4.3

0.1

0.0

0.0

030

0.0

0.0

0.0

0.0

0.0

0.0

6

4090 0

ABC_BSC_1 (8)

0%

Sect3

2.1

3.8

0.2

0.0

0.0

030

0.0

0.0

0.0

0.0

0.0

0.0

6

5317 1

ABC_BSC_1 (9)

0%

Example 35. Report 166: SDCCH drop ratio per cell

8.1.3

SDCCH Drop Ratio on BTS Level

For SDCCH drop ratios on the BTS level, run the report Cell analyser (216). SDCCH DROP RATIO ............... .........../sdr_ 1a .

2.47 %

4.02 %

SDCCH drop ratio components:

.

SDCCH_RADIO_FAI L....../c1003

1.19 %

2.30 %

.

SDCCH_A_IF_FAIL _CALL../c1078

0.27 %

0.57 %

.

SDCCH_ABIS_FAIL _CALL../c1075

1.01 %

1.15 %

.

SDCCH_USER_ACT. ......./c1037

0.00 %

0.00 %

.

SDCCH_BCSU_RESE T....../c1038

0.00 %

0.00 %

.

SDCCH_NETW_ACT. ......./c1039

0.00 %

0.00 %

.

SDCCH_BTS_FAIL. ......./c1036

0.00 %

0.00 %

.

SDCCH_LAPD_FAIL ......./c1035

0.00 %

0.00 %

.

SDCCH_RF_OLD_HO ......./c1004

0.00 %

0.00 %

.

SDCCH_ABIS_FAIL _OLD.../c1076

0.00 %

0.00 %

.

SDCCH_A_IF_FAIL _OLD.../c1079

0.00 %

0.00 %

************************************************************************ SDCCH Success Ratio, based on SDCCH failures (csf_2a) ABC_BSC_1

bts:55 ITAG1

bcf:336

************************************************************************ Hints: For the BTS level hit list, run report 250.

Hr

tue

wed

thu

fri

sat

sun

mon

tue

wed

thu

fri

19

20

21

22

23

24

25

26

27

28

29

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

-- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----00

100

100

100

100

01

100

02

100

100

100

100

100

100

03 04 05 06


NTC TAN 0935/2.3 en

100


78


07

100

100

08

100

100

100

100

100

100

100

100

09

100

100

100

100

100

100

100

100

100

100

10

100

97

100

100

100

100

100

92

100

100

11

100

100

100

100

100

100

100

93

98

100

12

100

93

100

98

97

98

100

94

100

100

13

99

99

100

99

100

100

99

97

98

100

14

98

92

97

100

100

100

98

100

100

100

15

100

98

100

100

100

98

96

100

98

95

16

100

96

100

98

100

98

97

98

100

100

17

100

98

98

99

96

98

98

100

100

100

18

99

96

98

99

100

100

99

97

100

99

19

100

100

99

97

96

97

97

99

97

97

20

100

99

99

99

100

98

99

100

100

97

21

100

100

98

99

100

100

100

100

97

99

22

100

100

100

100

100

100

100

100

100

94

100

100

100

100

100

100

100

100

100

23

100

100

Example 36. BTS level data on SDCCH drop ratio as shown in report 216, Cell analyser.

8.2

TCH Drop Call Ratio 8.2.1

TCH Drop Call Ratio on Area Level

For daily averages of TCH drop call ratio on area level, use the report Performance statistics (benchmark) (200). See also TCH success ratio and TCH drop ratio above. For averages and components, run the report Network benchmark statistics (204). TCH failures ============ TCH drop call ratio (before re-establismen t)../dcr_3g

2.39 %

. TCH_RADIO_FAIL ................ .............../ c1013

3265

(

1.19 %)

. TCH_ABIS_FAIL_ CALL............ .............../ c1084

612

(

0.22 %)

. TCH_A_IF_FAIL_ CALL............ .............../ c1087

66

(

0.02 %)

. TCH_TR_FAIL... ................ .............../ c1029

155

(

0.06 %)

. TCH_USER_ACT.. ................ .............../ c1048

7

(

0.00 %)

. TCH_BCSU_RESET ................ .............../ c1049

0

(

0.00 %)

. TCH_NETW_ACT.. ................ .............../ c1050

0

(

0.00 %)

. TCH_ACT_FAIL_C ALL............. .............../ c1081

2

(

0.00 %)

. TCH_BTS_FAIL.. ................ .............../ c1047

1

(

0.00 %)

. TCH_LAPD_FAIL. ................ .............../ c1046

5

(

0.00 %)

. TCH_RF_OLD_HO. ......(HO drop)......... ......./c1014

2048

(

0.75 %)

. TCH_ABIS_FAIL_ OLD...(HO drop)......... ......./c1085

25

(

0.01 %)

. TCH_A_IF_FAIL_ OLD...(HO drop)......... ......./c1088

373

(

0.14 %)

. TCH_TR_FAIL_OL D.....(HO drop)......... ......./c1030

2

(

0.00 %)

TCH drop call ratio (after re-establisment ).../dcr_3f

2.04 %


Example 37. Averages and components of TCH failures as shown in report 204, Network benchmark statistics.


NTC TAN 0935/2.3 en


79


For the division of the dropped calls into categories and their daily values, run the report TCH drop call statistics by days across area (160). = =

TCH DROP CALL STATISTICS BY DAYS ACROSS AREA

= =

Network:

PLMN

=

Area:

BSC - BSC_1

=

Period:

from 19970829 to 19970829

= =============================================================================== NC

/c1009

DR

/dr_4+dr_5

TCH seizures for normal new call. Calls started as Directed Retry handover.

.

The sum of DR in and intra-cell sdcch-tch ho.

CR

/c3020

Number of call re-establishment s.

FCS

/c1099

TCH seizures due to FACCH call setup.

Different drop ratios in %(in ratio to sum of calls and re-establishments): Rf call

/c1013

Radio failures during call

Rf old

/c1014

Radio failures on old channel failure in HO

Tr call

/c1029

Transcoder failure during call

Tr old

/c1030

Transcoder failures on old channel during HO

Abis call

/c1084

Abis failures during call.

Abis old

/c1085

Abis failures on old channel during TCH HO.

Aif call

/c1084

A interface failures during call.

Aif old

/c1085

A interface failures on old channel during TCH HO.

Lapd

/c1046

Lapd failures

BTS

/c1047

Transaction failures due to BTS problems.

User

/c1048

Transaction failures due to user actions.

BCSU

/c1049

Transaction failures due to BCSU reset.

Cnfg

/c1050

Transaction failures due to radio network

.

configuration actions.

Act

/c1081

DCR

/dcr_3c Ratio of the TCH call drops to started calls,

Channel activation failures during call.

.

(call re-est. is not compensated)

DCR

/dcr_3f Ratio of the TCH call drops to started calls,

.

(call re-est. is compensated)

Measurement used: p_nbsc_traffic, p_nbsc_ho Note: This report covers the calls after a successful TCH seizure attempt. Note: The rounding causes that the drop call ratio does not necessarily exactly .

match the sum of composite drop call ratios.

Note: Running this report takes a while. Patience please. =============================================================================== Drop call statistics

Bids ******

MMDD

Rf

Abis

Tr

Aif

(%)

(%)

NC

(%)

(%)

(%)

(%)

****

****

DCR(%)

DR

***** ***** ***** ***** Lapd

User

******

CR

call

call

call

call

BTS

Cnfg

dcr_3c

FCS

old

old

old

old

BCSU

Act

dcr_3f

---- --------- ----- ----- ----- ----- ----- ----- -----0829

263918

1.4

0.3

0.0

0.0

0.0

0.0

2.3

836

0.4

0.0

0.0

0.2

0.0

0.0

1.9


NTC TAN 0935/2.3 en


80


1102

0.0

0.0

84

Example 38. Report 160: TCH drop call statistics by days across area

8.2.2

TCH Drop Call Ratio on BSC Level

Transcoder failures are often BSC-specific. The report TCH drop call statistics per day in each BSC (162) helps to reveal the BSC dependency. = =

TCH DROP CALL STATISTICS BY DAYS IN EACH BSC

= =

Network:

PLMN

=

Period:

from 19970829 to 19970829

= =============================================================================== NC

/c1009

DR

/dr_4+dr_5

.

TCH seizures for normal new call. Calls started as Directed Retry handover. The sum of DR in and intra cell sdcch-tch ho.

CR

/c3020

Number of call re-establishme nts.

FCS

/c1099

TCH seizures due to FACCH call setup.

Different drop ratios in % (in ratio to sum of calls and re-establishments): Rf call

/c1013

Radio failures during call

Rf old

/c1014

Radio failures on old channel failure in HO

Tr call

/c1029

Transcoder failure during call

Tr old

/c1030

Transcoder failures on old channel during HO

Abis call

/c1084

Abis failures during call.

Abis old

/c1085

Abis failures on old channel during TCH HO.

Aif call

/c1084

A interface failures during call.

Aif old

/c1085

A interface failures on old channel during TCH HO.

Lapd

/c1046

Lapd failures

BTS

/c1047

Transaction failures due to BTS problems.

User

/c1048

Transaction failures due to user actions.

BCSU

/c1049

Transaction failures due to BCSU reset.

Cnfg

/c1050

Transaction failures due to radio network

Act

/c1081

Channel activation failures during call.

DCR

/dcr_3c

Ratio of the TCH call drops to started calls,

/dcr_3f

Ratio of the TCH call drops to started calls,

.

configuration actions.

.

(call re-est. is not compensated)

DCR .

(call re-est. is compensated)

Measurement used: p_nbsc_traffic, p_nbsc_ho Note: This report covers the calls after a successful TCH seizure attempt. Note: The rounding causes that the drop call ratio does not necessarily exactly .

match the sum of composite drop call ratios.

Note: Running this report takes a while. Patience please. =============================================================================== Drop call statistics by BSCs BSC : XYZ_BSC_1


NTC TAN 0935/2.3 en


81


Bids *****

MMDD

Rf

Abis

Tr

Aif

(%)

NC

(%)

(%)

(%)

(%)

***** ***** DCR(%)

DR

***** ***** ***** ***** Lapd

User

******

CR

call

call

call

call

BTS

Cnfg

dcr_3c

old

old

old

old

BCSU

Act

dcr_3f

FCS

(%)

---- -------- ----- ----- ----- ----- ----- ----- -----0829

263918

1.4

0.3

0.0

0.0

0.0

0.0

2.3

836

0.4

0.0

0.0

0.2

0.0

0.0

1.9

0.0

0.0

1102 84

Drop call statistics by BSCs BSC : XYZ_BSC_2

Bids *****

Rf

Abis

Tr

Aif

(%)

NC

(%)

(%)

(%)

(%)

***** ***** DCR(%)

DR

***** ***** ***** ***** Lapd

CR MMDD

FCS

(%) User

******

call

call

call

call

BTS

Cnfg

dcr_3c

old

old

old

old

BCSU

Act

dcr_3f

---- -------- ----- ----- ----- ----- ----- ----- -----0829

272120

1.3

0.3

0.1

0.0

0.0

0.0

2.2

1165

0.5

0.0

0.0

0.1

0.0

0.0

1.9

0.0

0.0

964 27

Example 39. Report 162: TCH drop call statistics per day in each BSC

8.2.3

TCH Drop Call Ratio on BTS Hit List

For TCH drop call ratios on BTS hit lists, run the report Cells having high TCH drop call ratio (163). = =

CELLS HAVING HIGH TCH DROP CALLS PER ERLANG

= =

Network:

PLMN

=

Area:

BSC - BSC444

=

Period:

from 19981125 to 19981125

=

Formula:

DROP CALLS PER ERLANG (dcr_10)

=

Threshold: DROP CALLS PER ERLANG >=

=

Threshold: Nbr of TCH seizures (HO+call) >=

=

Sorted by: DROP CALLS PER ERLANG

1 10

= =============================================================================== The report gives the following figures sorted out by the selected column for all cells meeting the thresholds: Different drop ratio in % (---- means 0 divisor): Rf call

/c1013

Radio failures

Rf old

/c1014

Radio failures on the old channel in HO

Tc fail

/c1029

Transcoder failures.

Tc old

/c1030

Transcoder failures of the old channel in HO

Abis call

/c1084

Abis failures.

Abis old

/c1085

Abis failures on the old channel in HO

Aif call

/c1087

A if failures.


NTC TAN 0935/2.3 en


82


Aif old

/c1088

A if failures on the old channel in HO

Lapd

/c1046

Lapd failures.

BTS

/c1047

BTS failures.

Usr

/c1048

Failures due to user actions.

BCSU

/c1049

Failures due to BCSU reset.

Cfg

/c1050

Failures due to radio network

.

configuration action.

Act

/c1081

Failures due to channel activation nack

Call

/c1009

Successful TCH seizures for call

DR

/dr_4+dr_5

.

Calls started as Directed Retry handover. It is the sum of DR in and intra cell sdcch-tch ho.

FCS

/c1099

TCH seizures due to FACCH call setup

T-T HO

TCH seizures in MSC and BSC controlled TCH-TCH

.

handovers

Drop Ratio

/dcr_3c Drops per bids (bids = calls + DR in + FCS)

Drop Ratio

/dcr_4c Drops per bids (bids = calls + DR in + FCS + T-T HO)

Drop Ratio

/dcr_4d Drops per bids

.

(bids = calls + DR in + FCS + net TCH HO in)

Drop Ratio

/dcr_10a (Drops-re_esta blishments) per Erlang hour.

Measurements used: Traffic, Handover, Res. Access, Res. Avail. Note: This report covers the calls after a successful TCH seizure attempt. Note: Running this report takes a while. Patience please. =============================================================================== TCH DROP CALLS PER ERLANG (dcr_10) per cell between 19981125 and 19981125

Bids

BTS BCF BSC (BTSid)

****

Rf

Tr

Abis

Aif

(%)

(%)

Call

(%)

(%)

(%)

(%)

****

****

Drop

DR in

*****

*****

*****

*****

Lapd

User

Ratio

FCS

call

call

call

call

BTS

Cnfg

(%)

T-T HO

old

old

old

old

BCSU

Act dcr_10

----------------- ------ ------ ------ ------ ------ ----- ----- -----Site A Sector 1 BSC444 (12)

3788

1.4

0.0

0.4

0.0

0.0

0.0

0

1.9

0.0

0.0

0.2

0.0

0.0

0.0

0.0

0

3.4

6121

Site B

10085

1.3

0.1

0.4

0.0

0.0

0.0

Sector 2

0

0.8

0.0

0.1

0.8

0.0

0.0

BSC444 (1)

0

0.0

0.0

3.0

7575

Example 40. Report 163: Cells having high TCH drop call ratio

8.2.4

TCH Drop Call Ratio on BTS Level

To receive the average over a period, the busy hour and 10-day/24-hour breakdown, run the report Cell analyser (216). .

Whole

SDCCH

.

period

busy hour


NTC TAN 0935/2.3 en


83


.

average

average

.

=======

=========

TCH drop out ratio ................ ......../dcr_4c

0.46 %

0.00 %

.

Drop call ratio components:

.

TCH_RADIO_FAIL. ......./c1013

0.46 %

0.00 %

.

TCH_ABIS_FAIL_C ALL..../c1084

0.00 %

0.00 %

.

TCH_A_IF_FAIL_C ALL..../c1087

0.00 %

0.00 %

.

TCH_TR_FAIL.... ......./c1029

0.00 %

0.00 %

.

TCH_LAPD_FAIL.. ......./c1046

0.00 %

0.00 %

.

TCH_BTS_FAIL... ......./c1047

0.00 %

0.00 %

.

TCH_USER_ACT... ......./c1048

0.00 %

0.00 %

.

TCH_BCSU_RESET. ......./c1049

0.00 %

0.00 %

.

TCH_NETW_ACT... ......./c1050

0.00 %

0.00 %

.

TCH_ACT_FAIL_CA LL...../c1081

0.00 %

0.00 %

.

TCH_RF_OLD_HO.. ......./c1014

0.00 %

0.00 %

.

TCH_ABIS_FAIL_O LD...../c1085

0.00 %

0.00 %

.

TCH_A_IF_FAIL_O LD...../c1088

0.00 %

0.00 %

.

TCH_TR_FAIL_OLD ......./c1030

0.00 %

0.00 %

************************************************************************ Dropout ratio (%) ABC_BSC_1

(dcr_4c)

bts:55 ITAG1

bcf:336

************************************************************************ Hints: For the BTS level hit list, run report 163. tue Hr

wed

thu

fri

sat

sun

mon

tue

wed

thu

fri

19

20

21

22

23

24

25

26

27

28

29

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

-- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----07

0

08

0 0

10

0

0

0

0

0

0

0

5

11

0

7

0

0

0

0

0

0

0

0

12

0

0

0

0

0

0

0

0

0

0

13

0

0

0

0

0

0

0

0

1

0

14

0

0

0

2

0

0

0

0

4

0

15

0

0

0

0

0

3

0

0

0

2

16

0

0

0

2

0

0

2

0

0

0

17

0

0

0

0

0

0

0

0

5

0

18

0

0

0

0

0

0

0

0

0

0

19

0

0

0

2

0

0

0

0

0

20

0

0

0

0

0

0

0

2

0

0

21

0

0

0

0

0

0

0

0

0

1

22

0

0

0

0

0

0

0

0

0

0

23

0

0

0

09

0

0

0

Example 41. Averages of TCH drop call ratio over a period of time in report 216, Cell analyser.

8.2.5

TCH Observation

Depending on the dominating failure class (Abis, for example), it may be necessary to set the cell under observation. You can quickly analyse the


NTC TAN 0935/2.3 en


84


observation data by using the report TCH, SDCCH and BSC out HO observation statistics (217). This report helps you identify the actual point of failure in the message flow as defined by the phase and cause. BSC/BCF/BTS

Cause BTS

TRX

nbr

nbr Phase OUT

Cause

OUT

OUT

count

--------------- ---- ---- ------------------------- ------ ------BSC_WWWWW

49

1 Ciphering

317

3

Ciphering

320

23

MM signalling

317

1

MM signalling

320

1

MM signalling

334

7

MM signalling

084 PR1WW

602

8

Release

10

1587

Release

42

46

Release

43

45

Release

45

390

Release

320

37

Release

335

2

SMS establishing SDCCH

317

1

SMS establishing SDCCH

334

5

paging/initial MS

321

103

Example 42. Report 217: TCH, SDCCH and BSC out HO observation statistics

8.3

Handover Failure Ratio BSS Network Doctor provides a variety of reports to monitor handover failure ratio at various network levels.

8.3.1

Handover Failure Ratio on BTS Area Level

For daily averages of handover failure ratios on a BTS area, use the report Performance statistics (benchmark) (200).

Day MMDD

TCH

TCH

TCH

HO

HO

TCH

HO

seiz

seiz

HO

block

qd

nonqd

req

(%)

(%)

(%)

ho_14b

blck_11c

que_2

que_8

--- ---- --------- --- -------- ------- ------tue 1124

468413 ==>

13.21

0.00

86.79

mon 1123

446152 ==>

0.50

0.00

99.50

sun 1122

284705 ==>

0.46

0.00

99.54

sat 1121

303455 ==>

0.50

0.00

99.50

fri 1120

310049 ==>

0.26

0.00

99.74

=============================================================================== =


NTC TAN 0935/2.3 en

Network Performance Statistics, Handover


85


=============================================================================== HO STATISTICS: (S-S = SDCCH-SDCCH, S-T = SDCCH-TCH, T-T=TCH-TCH) MSC CONTROLLED OUTGOING HO SUCCESS BY HO TYPES ============================================== S-S

S-S

S-T

S-T

T-T

T-T

att

succ

att

succ

att

succ

c4052

hsr_3

(%) Day MMDD

c4054

hsr_1

(%) c4050

(%)

hsr_2

--- ---- ------- ------- -------- ------- -------- ------tue 1124

0

0.00

16

0.00

39779

92.16

mon 1123

0

0.00

15

0.00

47040

93.56

sun 1122

0

0.00

7

0.00

36832

93.19

sat 1121

0

0.00

11

0.00

39428

93.42

fri 1120

0

0.00

19

0.00

38736

93.80

BSC CONTROLLED OUTGOING HO SUCCESS BY HO TYPES ============================================== S-S

S-S

S-T

S-T

T-T

T-T

att

succ

att

succ

att

succ

c4069

hsr_4

c4077

hsr_5

c4067

hsr_6

(%) Day MMDD

(%)

(%)

--- ---- ------- ------- -------- ------- -------- ------tue 1124

0

0.00

125

47.20

127493

82.82

mon 1123

0

0.00

47

97.87

112703

96.52

sun 1122

0

0.00

13

100.00

76475

95.91

sat 1121

0

0.00

45

100.00

80022

95.93

fri 1120

0

0.00

74

97.30

83160

96.04

INTRA CELL HO SUCCESS BY HO TYPES ================================= S-S

S-S

S-T

S-T

T-T

T-T

att

succ

att

succ

att

succ

(%) Day MMDD

c4078

hsr_7

(%) c4077

(%)

hsr_8

c4076

hsr_9

--- ---- ------- ------- -------- ------- -------- ------tue 1124

0

0.00

0

0.00

264515

95.68

mon 1123

0

0.00

0

0.00

285610

97.82

sun 1122

0

0.00

0

0.00

168863

97.66

sat 1121

0

0.00

0

0.00

180855

97.54

fri 1120

0

0.00

0

0.00

185465

97.98

MSC CONTROLED HO FAILURES =========================

Wrong Aif Not Block HO (%)

Day MMDD

Return Call

End HO circ

Adj cell

allwd

to old clear

End HO BSS

type

err

(%)

(%)

(%)

(%)

(%)

(%)

(%)

att hfr_28 hfr_29 hfr_30 hfr_31 hfr_32 hfr_33 hfr_34 hfr_35

--- ---- -------- ------ ------ ------ ------ ------ ------ ------ -----tue 1124

39795

1.42

0.04

5.08

0.78

0.55

0.00

0.00

0.00

mon 1123

47055

0.91

0.03

4.31

0.66

0.55

0.00

0.00

0.00

sun 1122

36839

0.71

0.02

4.94

0.72

0.43

0.00

0.00

0.00

sat 1121

39439

0.82

0.03

4.61

0.63

0.50

0.01

0.00

0.00

fri 1120

38755

0.46

0.05

4.53

0.64

0.56

0.00

0.00

0.00

BSC CONTROLED HO FAILURES =========================


NTC TAN 0935/2.3 en


86



Day MMDD

Return Call

End HO circ

Drop

allwd

to old clear

End HO BSS

type

call

(%)

(%)

(%)

(%)

(%)

(%)

(%)


--- ---- -------- ------ ------ ------ ------ ------ ------ ------ -----tue 1124

127618

14.09

0.01

2.80

0.04

0.28

0.00

0.00

0.28

mon 1123

112750

0.02

0.01

3.06

0.05

0.34

0.00

0.00

0.34

sun 1122

76488

0.01

0.02

3.61

0.04

0.40

0.00

0.00

0.40

sat 1121

80067

0.04

0.02

3.55

0.06

0.40

0.00

0.00

0.40

fri 1120

83234

0.05

0.02

3.49

0.03

0.37

0.00

0.00

0.36

INTRA CELL HO FAILURES ======================


Day MMDD

Return Call

MS

BSS

circ

Drop

allwd

to old clear

lost

probl

type

call

(%)

(%)

(%)

(%)

(%)

(%)

(%)


--- ---- -------- ------ ------ ------ ------ ------ ------ ------ -----tue 1124

264515

2.87

0.00

0.94

0.13

0.34

0.00

0.00

0.34

mon 1123

285610

0.77

0.00

0.94

0.15

0.32

0.00

0.00

0.32

sun 1122

168863

0.76

0.00

1.03

0.15

0.39

0.00

0.00

0.39

sat 1121

180855

0.80

0.00

1.12

0.13

0.40

0.00

0.00

0.40

fri 1120

185465

0.40

0.00

1.03

0.15

0.43

0.00

0.00

0.43

Example 43. Daily averages of handover failure ratio in report 200, Performance statistics (benchmark).

For handover averages and components, use the report Network benchmark statistics (204). HANDOVERS ========= Total HO failure ............... .............../ hfr_2

9.69 %

. HO failure due to blocking ................ ./hfr_55

7.56 %

Outgoing MSC ctrl HO attempts ............... .../ho_9

75409

.

Successes ............... ................ ../c4004

70846

(

93.95 %)

.

Failures .............. ............... ..../hof_6a

4563

(

6.05 %)

.

MSC ctrl ho not allowed ............... ../c4037

1

(

0.00 %)

.

Blocked ............... ................ ../c4055

163

(

0.22 %)

.

Return to old ............... ............/c4 006

3555

(

4.71 %)

.

End of HO

426

(

0.56 %)

.

End of HO BSS ............... ............/c4 008

6

(

0.01 %)

.

Call clear ............... .............../ c4041

412

(

0.55 %)

.

Wrong Aif circuit type ................ ../c4102

0

(

0.00 %)

.

Adjacent cell error .............. ......./c4100

0

(

0.00 %)

.

Drop calls ( counter planned in S7) .............

............... .............../ c4007

Outgoing BSC ctrl HO attempts ............... ../ho_11

191362

.

Successes ............... ................ ../c4014

181112

(

94.64 %)

.

Failures .............. ............... ..../hof_8a

10250

(

5.36 %)

.

BSC ctrl ho not allowed ............... ../c4038

24

(

0.01 %)

.

Blocked ............... ................ ../c4072

2762

(

1.44 %)


NTC TAN 0935/2.3 en


87


.

Return to old ............... ............/c4 015

6677

(

3.49 %)

.

End of HO

.

............... .............../ c4016

713

(

0.37 %)

End of HO BSS ............... ............/c4 017

3

(

0.00 %)

. .

Call clear ............... .............../ c4042

71

(

0.04 %)


0

(

0.00 %)

.

Drop calls .............. ................ ../c4084

703

(

0.37 %)

Intra cell

HO attempts ................ ......./ho_24

635736

.

Successes ............... ................ ../ho_27

563123

(

88.58 %)

.

Failures .............. ............... ...../hof_9

72613

(

11.42 %)

.

Intra cell ho not allowed .............../ c4036

11

(

0.00 %)

.

Blocked ............... ................ ../c4019

65290

(

10.27 %)

.

Return to old ............... ............/c4 022

4936

(

0.78 %)

.

MS lost .(drop call)......... ............/c4 020

1614

(

0.25 %)

.

Radio chn.act.failure .............. ...../c4021

29

(

0.00 %)

.

Call clear ............... .............../ c4039

713

(

0.11 %)

.


0

(

0.00 %)

.

Drop calls .............. ................ ../c4085

1620

(

0.25 %)

UL quality......... ................ ............/c4 023

36546

(

4.05 %)

UL level........... ................ ............/c4 024

49809

(

5.52 %)

DL quality......... ................ ............/c4 025

16425

(

1.82 %)

DL level........... ................ ............/c4 026

25563

(

2.83 %)

Distance ............... ................ ......./c4027

0

(

0.00 %)

MSC invocation (traffic reason) .............../ c4028

0

(

0.00 %)

UL interference ................ .............../ c4029

26546

(

2.94 %)

DL interference ................ .............../ c4030

73166

(

8.11 %)

Note: For cell level list run the report 150. Note: For adjacency level list run the report 153. Causes:

Umbrella ............... ................ ......./c4031

0

(

0.00 %)

Pbdgt ................ ............... ........../c4032

147075

(

16.30 %)

OMC (forced by user) .............. ............/c4 033

0

(

0.00 %)

Directed retry .............. ................ ../c4079

0

(

0.00 %)

Pre-emption ............... ............... ...../c4086

0

(

0.00 %)

Rapid field drop ............... .............../ c4087

0

(

0.00 %)

Low distance .............. ............... ...../c4088

0

(

0.00 %)

Bad CI ............... ............... ........../c4089

65618

(

7.27 %)

Good CI .............. ............... ........../c4090

461759

(

51.16 %)

Slow moving MS .............. ................ ../c4091

0

(

0.00 %)

MS slow speed ............... ................ ../c4105

0

(

0.00 %)

MS high speed ............... ................ ../c4106

0

(

0.00 %)


Example 44. Handover averages and components as shown in report 204, Network benchmark statistics.

8.3.2

Handover Failure Ratio on BTS Hit List Level

Use the report Cells having high HO failure ratio (150) if only the standard measurements are available. It can be difficult to pinpoint the adjacency that is causing the failures.


NTC TAN 0935/2.3 en


88


BTS HO failure rate between 19971115 and 19971119 sorted by total HO fail % Tot BTS

HO

BCF

Type

Att

Fail Blck NotA FRet Drop

BSC (BTSid)

%

%

%

%

Fail

%

%

----------------- ------------------------------------------ -----XXXXXXX1

MSC i:

606

0.0

0.0

-

-

-

XXXXXXX

MSC o:

540

BSC11(31)

BSC i:

19633

0.1

0.0

0.1

0.0

-

3.3

2.8

-

-

0.0

2.9

2.1

0.0

0.6

0.0

69.3 69.0

0.0

0.0

0.0 -

BSC o:

20631

Cell :

164985

XXXXXXXXXXX2

MSC i:

7202

0.3

0.2

-

-

XXXXXXXXXXX

MSC o:

10275

1.4

0.0

1.1

0.2

-

BSC11(26)

BSC i:

16948

2.2

1.7

-

-

0.1

0.8

0.2

0.0

0.5

0.0

66.5 66.3

0.0

0.0

0.1

BSC o:

16625

Cell :

164327

75.6

71.2

Example 45. Report 150: Cells having high HO failure ratio

8.3.3

Handover Failure Ratio on Adjacency Hit List Level

The Adjacencies having high HO failure ratio (153) report is based on the optional BSC measurement HO Adjacent Cell. You can use the thresholds to focus on problematic adjacencies only. Adjacencies with HO failures between 19980629 and 19980629 Source

Target

******

******

BTS NAME

HO=> HO=> <=HO HO=>

Target BTS NAME

BCF NAME

HO=>

**** **** **** **** <=HO

****** BCF NAME

BSC NAME (BTS)

****

Blck Fail Fail Blck ****

LAC

BSC NAME (BTS)

BAND

Att

CI

BAND

(%)

(%)

(%)

(%) Att

------------------ ------ ---- ---- ---- ---- ------ ------ -----------------SANDPG1017

48

50

4

4

50

SANDPG009

52 1 10019

SANDPD1019 SANDPD010

BSC1KUTOJA (17)

BSC1KUTOJA (19)

gsm900

gsm1800

SANDPD1019

52

SANDPD010

50

4

4

50

48 1 10017

SANDPG1017 SANDPG009

BSC1KUTOJA (19)

BSC1KUTOJA (17)

gsm1800

gsm900

Example 46. Report 153: Adjacencies having high HO failure ratio

8.3.4

Handover Failure Ratio on BTS Level

For handover failure ratios on the BTS level, run the report Cell analyser (216).


NTC TAN 0935/2.3 en


89


= = =

Cell HO performance. ABC_BSC_1

bts id:55

name:ITAG1

from 19970829 to 19970829

=============================================================================== .

Whole

TCH

.

period

busy hour

.

average

average

.

=======

=========

HO failure ratio ............... ............/hfr _1

1.27 %

0.00 %

HANDOVER ATTEMPTS SDCCH-SDCCH... ............... .............../ ho_18

0.0

0.0

. MSC controlled outgoing....... ............/c40 54

0.00 %

0.00 %

. MSC controlled incoming....... ............/c40 48

0.00 %

0.00 %

. BSC controlled outgoing....... ............/c40 69

0.00 %

0.00 %

. BSC controlled incoming....... ............/c40 61

0.00 %

0.00 %

. Intra cell.......... ............... ......./c4078

0.00 %

0.00 %

SDCCH-TCH..... ............... .............../ ho_17

0.0

0.0


0.00 %

0.00 %


0.00 %

0.00 %


0.00 %

0.00


0.00 %

0.00 %

. Intra cell.......... ............... ......./c4077

0.00 %

0.00 %

TCH-TCH....... ............... .............../ ho_16

12.1

35.0


2.69 %

3.00 %


2.08 %

1.00 %


3.08 %

2.00 %


4.08 %

6.00 %

. Intra cell.......... ............... ......./c4076

0.15 %

0.00 %

. MSC controlled outgoing....... ......../100-hsr _1

0.00 %

0.00 %

. MSC controlled incoming....... ......./100-hsr_ 10

0.00 %

0.00 %

. BSC controlled outgoing....... ......../100-hsr _4

0.00 %

0.00 %

. BSC controlled incoming....... ......./100-hsr_ 13

0.00 %

0.00 %

. Intra cell.......... ............... .../100-hsr_7

0.00 %

0.00 %


0.00 %

0.00 %


0.00 %

0.00 %


0.00 %

0.00 %


0.00 %

0.00 %

. Intra cell.......... ............... .../100-hsr_8

0.00 %

0.00 %


0.00 %

0.00 %


0.00 %

0.00 %


0.00 %

0.00 %


3.77 %

0.00 %

. Intra cell.......... ............... .../100-hsr_9

0.00 %

0.00 %

HANDOVER FAILURE RATIOS: . SDCCH-SDCCH

SDCCH-TCH

. TCH-TCH

HANDOVER FAILURES: ================== .


NTC TAN 0935/2.3 en

Whole


TCH

90


.

period

busy hour

.

average

average

.

=======

=========

Outgoing MSC ctrl HO attempts ............... /ho_9

2.7

3.0

.

Successes ............... .........../100- hfr_5

100.00 %

100.00 %

.

Failures .............. ............... ../hfr_5

0.00 %

0.00 %

.

MSC ctrl ho not allowed ............../ c4037

0.00 %

0.00 %

.

Blocked ............... .............../ c4055

0.00 %

0.00 %

.

Return to old ............... ........./c4006

0.00 %

0.00 %

.

End of HO

............... ............/c40 07

0.00 %

0.00 %

.

End of HO BSS ............... ........./c4008

0.00 %

0.00 %

.

Call clear ............... ............/c40 41

0.00 %

0.00 %

.

Wrong Aif circuit type .............../ c4102

0.00 %

0.00 %

.

Adjacent cell error .............. ..../c4100

0.00 %

0.00 %

.

Drop calls .............. .....(planned in S7)

Outgoing BSC ctrl HO attempts ............../ ho_11

3.1

2.0

.

Successes ............... .........../100- hfr_7

100.00 %

100.00 %

.

Failures .............. ............... ../hfr_7

0.00 %

0.00 %

.

BSC ctrl ho not allowed ............../ c4038

0.00 %

0.00 %

.

Blocked ............... .............../ c4072

0.00 %

0.00 %

.

Return to old ............... ........./c4015

0.00 %

0.00 %

.

End of HO

............... ............/c40 16

0.00 %

0.00 %

.

End of HO BSS ............... ........./c4017

0.00 %

0.00 %

.

Call clear ............... ............/c40 42

0.00 %

0.00 %

.


0.00 %

0.00 %

.

Drop calls .............. .............../ c4084

0.00 %

0.00 %

Incoming MSC ctrl HO attempts ............../ ho_35

2.1

1.0

.

Successes ............... ............../h sr_17

100.00 %

100.00 %

.

Failures .............. ............/10 0-hsr_17

0.00 %

0.00 %

.

Blocked ............... .............../ c4001

0.00 %

0.00 %

.

Connection failure ............... ..../c4002

0.00 %

0.00 %

.

Radio chn. act. failure ............../ c4003

0.00 %

0.00 %

.

End of HO ................ ............/c40 80

0.00 %

0.00 %

.


0.00 %

0.00 %

Incoming BSC ctrl HO attempts ............../ ho_10

4.1

6.0

.

Successes ............... ............../h sr_16

96.23 %

100.00 %

.

Failures .............. ............/10 0-hsr_16

3.77 %

0.00 %

.

Blocked ............... .............../ c4011

0.00 %

0.00 %

.

Connection failure ............... ..../c4012

3.77 %

0.00 %

.

Radio chn. act. failure ............../ c4013

0.00 %

0.00 %

.

End of HO ................ ............/c40 81

0.00 %

0.00 %

.


0.00 %

0.00 %

0.2

0.0

Intra cell HO attempts .............. ......./ho_24 .

Successes ............... .........../100- hfr_3

100.00 %

0.00 %

.

Failures .............. ............... ../hfr_3

0.00 %

0.00 %

.

Intra cell ho not allowed ............/c40 36

0.00 %

0.00 %

.

Blocked ............... .............../ c4019

0.00 %

0.00 %

.

Return to old ............... ........./c4022

0.00 %

0.00 %

.

MS lost .(drop call)......... ........./c4020

0.00 %

0.00 %

.

Radio chn.act.failure .............. ../c4021

0.00 %

0.00 %

.

Call clear ............... ............/c40 39

0.00 %

0.00 %

.

Drop calls .............. .............../ c4085

0.00 %

0.00 %

HANDOVER CAUSES:


NTC TAN 0935/2.3 en


91


================ .

Whole

TCH

.

period

busy hour

.

average

average

.

=======

=========

. Number of all ho attempts .............. ...../ho_13

5.92

5.00

. Cause: .

UL quality ............... ................ /c4023

0.00 %

0.00 %

.

DL quality ............... ................ /c4025

1.30 %

0.00 %

.

UL level ............... ............... .../c4024

6.50 %

0.00 %

.

DL level ............... ............... .../c4026

0.00 %

0.00 %

.

UL interference ................ ........../c402 9

0.00 %

0.00 %

.

DL interference ................ ........../c402 9

2.60 %

0.00 %

.

Distance ............... ............... .../c4027

0.00 %

0.00 %

.

MSC invocation .............. ............./c4 028

0.00 %

0.00 %

.

Umbrella ............... ............... .../c4031

0.00 %

0.00 %

.

Power budget ................ ............./c4 032

89.66 %

100.00 %

.

OMC ............... ............... ......../c4033

0.00 %

0.00 %

.

Channel administration .............. ...../c4034

0.00 %

0.00 %

.

Traffic ................ ............... .../c4035

0.00 %

0.00 %

.

Directed retry .............. ............./c4 079

0.00 %

0.00 %

.

Pre-emption .............. ................ /c4086

0.00 %

0.00 %

.

Field drop ............... ................ /c4087

0.00 %

0.00 %

.

Low distance ................ ............./c4 088

0.00 %

0.00 %

.

Bad C/I ................ ............... .../c4089

0.00 %

0.00 %

.

Good C/I ............... ............... .../c4090

0.00 %

0.00 %

.

Slow Moving MS............ ................ /c4091

0.00 %

0.00 %

Example 47. BTS level handover failure ratios as shown in report 216, Cell analyser.

The report also shows the worst cases of failing adjacencies: Adjacencies with HO failure ratio > 10% Source

Target

******

Target ******

BTS NAME

HO=> HO=>

<=HO <=HO ****** BTS NAME

BCF NAME

**** ****

**** **** LAC

BSC NAME (BTS) Fail % Att Fail % Att CI

BCF NAME BSC NAME (BTS)

-------------- - ------ ---- ------ ---- ------ ---------------Red Creek-1

30

20

4

25 2901

Red Creek

20462

TownXX_BSC (16) Red Creek-1

Hall -2 Hall TownXX_BSC(32 )

67

36

17

12 2901

Red Creek

20463

TownXX_BSC (16)

Hall -3 Hall TownXX_BSC(33 )

Example 48. The worst cases of failing adjacencies in report 216, Cell analyser.

The usage of all adjacencies and failures are seen also in report 213, Cell doctor: Source

Target

******

******

BTS NAME


NTC TAN 0935/2.3 en

HO=> HO=>

<=HO <=HO Target BTS NAME


92


BCF NAME

HO=> **** ****

BSC NAME

***** Blck Fail

(BTS)

Att

(%)

<=HO **** **** ****** BCF NAME ***** Blck Fail LAC

(%)

Att

(%)

BSC NAME

(%) CI

(BTS)

--------------- ------ ---- ---- ------ ---- ---- ------ ---------------KUTOJA1002

3

0

0

1

0

KUTOJA001

0 1 10001

KUTOJA1001 KUTOJA001

BSC1KUTOJA

BSC1KUTOJA

(2)

(1

)

Example 49. Adjacencies and failures as shown in report 213, Cell doctor.

8.4

Location Update Success 8.4.1

Location Update Success on BSC Level

Location update uses SDCCH and thus SDCCH success is an important contributor to LU success. If you need to focus on LU success separately, run report Location update success ratio per BSC (203). = =

LOCATION UPDATE SUCCESS RATIO PER BSC

= =

Network:

PLMN

=

Period:

from 19970828 to 19970828

= =============================================================================== LU attempts

c3019

Successful location update seizures.

LU success ratio

lsr_2

Successful location update ratio.

Measurement used: p_nbsc_cc_pm =============================================================================== LU success BSC

ratio LU attempts

(%)

--------------- ----------- ---------NYC_BSC_1

333374

99.1

NYC_BSC_2

250703

98.9

NYC_BSC_3

195385

99.0

NYC_BSC_4

162084

98.8

NYC_BSC_5

152805

98.6

NYC_BSC_6

194406

98.7

Example 50. Report 203: Location update success ratio per BSC


NTC TAN 0935/2.3 en


93

Cell Dimensioning

9

CELL DIMENSIONING There are many ways in which cell dimensioning can affect the quality of the network. The most severe case is that the user does not have access to the system.

9.1

Finding the Existing Dimensioning Problems in the Network The following measurements help pinpoint problems in dimensioning: •

SDCCH congestion and blocking

•

TCH congestion and blocking

Congestion means a situation when all resources are in use. Blocking is the situation when all resources are in use and new seizure attempts are rejected.

9.2

Finding the Future Dimensioning Problems in the Network It is possible to estimate the growth of traffic in each cell so that the possible congestion is forecast months in advance. In some cases traffic increases steadily and it is possible to detect that the cell in question will have to be redimensioned. Sometimes the traffic increase occurs suddenly due to some event, new building, traffic jam or an accident. Currently the BSS Network Doctor reports do not support the extrapolation of traffic.

9.3

SDCCH Congestion and Blocking SDCCH congestion is a situation when all SDCCHs are in use simultaneously. BSS Network Doctor reports display the total time that the SDCCHs were in use simultaneously. SDCCH blocking is a situation when all SDCCH channels are in use and a new seizure attempt is rejected due to the lack of resources. BSS Network Doctor reports display the percentage of rejected seizures out of all seizures.

9.3.1

SDCCH Congestion and Blocking on Area Level

For SDCCH congestion and blocking, BSS Network Doctor provides two reports: •


•


SDCCH requests ..............S DCCH requests...... ............/c1 000


NTC TAN 0935/2.3 en


4337854

94

Cell Dimensioning

. HO in............ ................ ............/c1 006

0

(

0.00 %)

. blocked .............. ................ ...../blck_15

10762

(

0.25 %)

. To FCS ............... ................ ......./c1099

341

(

0.01 %)

. ghosts and other fails (and IMSI detach) ...../sd_1

629948

(

14.52 %)

. LU .............. ................ ............/c3 019

1573348

(

36.27 %)

. MTC ................ ............... ........../c3013

489520

(

11.28 %)

. MOC ................ ............... ........../c3012

1622072

(

37.39 %)

. call re-establishmen t.............. ........../c3020

9608

(

0.22 %)

. emergency call ............... .............../ c3021

2255

(

0.05 %)

Example 51. SDCCH congestion and blocking as shown in report 204, Network benchmark statistics.

Day MMDD

SDCCH

SDCCH

SDCCH

SDCCH

SDCCH

SDCCH

avail

congst

seiz

HO seiz

assign

block

(%)

(%)

(%)

trf_33 blck_5a

trf_38

(%)

(min)

att

(%)

ava_4

cngt_2

c1000

trf_32

To FCS

--- ---- ------- ------- --------- --- ------- ------- ------- ------wed 0422

100.00

0.0

407 ==>

0.00

100.00

0.00

0.00

Example 52. SDCCH congestion and blocking as shown in report 200, Performance statistics (benchmark).

9.3.2

SDCCH Congestion and Blocking on BTS Hit List

The report Cells having SDCCH congestion (130) shows BTSs and periods when congestion time has exceeded the given threshold. = =

CELLS HAVING SDCCH CONGESTION

= =

Network:

=

Area:

PLMN BSC - BSC_SSSSS

=

Period:

from 19970128 to 19970201

=

Threshold:

congestion >= 2

seconds

= =============================================================================== This report shows each measurement period having SDCCH congestion over a given threshold. Aver avail SDCCH

/ava_3

Average available SDCCH

SDCCH cong (sec)

/cngt_2

Time congestion on SDCCH

SDCCH blck (% )

/blck_5

Blocking on SDCCH, before FCS

SDCCH blck (% )

/blck_5a

Blocking on SDCCH, after FCS

SDCCH req

/c1000

SDCCH seizure attempts

Measurement used: p_nbsc_res_avail, p_nbsc_traffic Hints: . .

- SDCCH congestion may be caused by excessive nbr of LUs which may occur easily if LAs are not planned well.

Running this report takes a few minutes. Patience please.


NTC TAN 0935/2.3 en


95

Cell Dimensioning

=============================================================================== BTS having SDCCH congestion between 19970128 and 19970201

SDCCH

blck(%) Period

Period

Aver

SDCCH *******

BSC

BCF name

start

start

avail SDCCH

(BTS id)

BTS name

day

hour

SDCCH

cong blck_5

req (sec) blck_5a

--------------- --------------- ---------- ------ ----- ----- ----- ------BSC_SSSSS

102

(46)

AEIWW

BSC_SSSSS

110A

(52)

AMBWW

1997-01-29 15:00

4.0

28

6

10.71 10.71

1997-01-30 17:00

4.0

123

2

0.00 0.00

20:00

4.0

99

4

1.01 1.01

BSC_SSSSS

099

(42)

AZBMM

BSC_SSSSS

101C

(63)

BK1MM

1997-01-30 10:00

4.0

104

2

0.96 0.96

1997-01-30 16:00

8.0

50

3

4.00 0.00

18:00

8.0

69

3

0.00 0.00

1997-01-31 15:00

8.0

36

3

2.78 2.78

BSC_SSSSS

051

(14)

BN2QQ

1997-01-30 22:00

4.0

94

2

2.13 2.13

1997-02-01 06:00

4.0

18

4

11.11 11.11

17:00

4.0

80

3

1.25 1.25

Example 53. Report 130: Cells having SDCCH congestion

9.3.3

SDCCH Congestion and Blocking on BTS Level

For SDCCH congestion and blocking on BTS level, use the report Cell analyser (216). .

Whole

SDCCH

.

period

busy hour

.

average

average

.

=======

=========

. SDCCH requests .............. .............../ c1000

45.5

114.0

. SDCCH requests BLOCKED ............... ../blck_5a

0.00 %

0.00 %

. SDCCH seizures for calls and LU ........../c10 07

100.00 %

100.00 %


NTC TAN 0935/2.3 en


96

Cell Dimensioning

. SDCCH seizures for handovers ............./ c1006

0.00 %

0.00 %

************************************************************************ SDCCH congestion (seconds) ABC_BSC_1

(cngt_2)

bts:55 ITAG1

bcf:336

************************************************************************

Hr

tue

wed

thu

fri

sat

sun

mon

tue

wed

thu

19

20

21

22

23

24

25

26

27

28

fri 29

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

-- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----00

0

0

0

0

0

0

0

0

01

0

0

0

0

0

0

02

0

0

0

0

0

03

0

0

0

0

04

0

0

0

0

05

0

0

0

06

0

0

0

07

0

0

08

0

0

09

0

10

0

11 12

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

13

0

0

0

0

0

0

0

0

0

0

14

0

0

0

0

0

0

0

0

0

0

15

0

0

0

0

0

0

0

0

0

0

16

0

0

0

0

0

0

0

0

0

0

17

0

0

0

0

0

0

0

0

0

0

18

0

0

0

0

0

0

0

0

0

0

19

0

0

0

0

0

0

0

0

0

0

20

0

0

0

0

0

0

0

0

0

0

21

0

0

0

0

0

0

0

0

0

0

22 23

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

************************************************************************ SDCCH blocking % (blck_5) ABC_BSC_1

bts:55 ITAG1

bcf:336

************************************************************************ tue Hr

wed

thu

fri

sat

sun

mon

tue

wed

thu

fri

19

20

21

22

23

24

25

26

27

28

29

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

-- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----00

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

01

0.0

0.0

0.0

0.0

0.0

0.0

02

0.0

0.0

0.0

0.0

0.0

03

0.0

0.0

0.0

0.0

04

0.0

0.0

0.0

0.0

05

0.0

0.0

0.0

06

0.0

0.0

0.0

07

0.0

0.0

08

0.0

0.0

09

0.0

10 11

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

12

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

13

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

14

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

15

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

16

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0


NTC TAN 0935/2.3 en


0.0

0.0

97

Cell Dimensioning

17

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

18

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

19

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

20

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

21

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

22 23

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

Example 54. BTS level data on SDCCH congestion and blocking in report 216, Cell analyser.

9.4

TCH Congestion and Blocking TCH congestion is a situation in which all TCHs are in use simultaneously. BSS Network Doctor reports display the total time that the TCHs were in use simultaneously. TCH blocking is a situation when all TCH channels are in use and a new seizure attempt is rejected due to lack of resources. BSS Network Doctor reports display the percentage of rejected seizures out of all seizures. Blocking can be reduced by using the optional BSC features Directed Retry and Queuing.

9.4.1

TCH Congestion on Area Level

For TCH congestion on the area level, use reports: •


•


TCH requests for new calls (trf_18a): . DR handover to other cell .

succ .............. ................ ......../dr_3

0

(

0.00 %)

.

unsucc ............... ............... ....../dr_7

0

(

0.00 %)

. DR handover intracell (IUO opt.) .

succ .............. ................ ......./c4074

0

(

0.00 %)

.

unsucc ............... ............... ....../dr_8

0

(

0.00 %)

0

(

0.00 %)

. To queue ................ ............... ...../c1016 .

From queue to DR ............... ............/xx1

(counter planned in S8)

.

Unserved queued .............. ............/c1 024

0

(

0.00 %)

. TCH normal seizures (queued or not) ........./c1009

274053

(

98.24 %)

. Blocked calls ................ .../blck_9b (blck_8c)

4904

(

1.76 %)

Example 55. Area level data on TCH congestion in report 204, Network benchmark statistics.

Day MMDD

TCH

Succ

TCH

TCH

TCH

TCH

TCH

call

DR

call

seiz

seiz

avail

congst

req

out

block

qd

non qd

(%)

(min)

(%)

(%)

(%)

(%)

ava_1

cngt_2

dr_6 blck_8c

que_1

trf_18a

que_7

--- ---- ------- -------- --------- --- ------- ------- ------- ------tue 1124

95.48

6.37

129776 ==>

0.05

0.07

0.00

99.88

mon 1123

99.99

0.05

140641 ==>

0.03

0.01

0.00

99.95


NTC TAN 0935/2.3 en


98

Cell Dimensioning

sun 1122

99.98

0.04

122734 ==>

0.01

0.01

0.00

99.98

sat 1121

99.70

0.08

130547 ==>

0.03

0.01

0.00

99.95

fri 1120

100.00

0.00

134450 ==>

0.05

0.02

0.00

99.93

Example 56. Area level data on TCH congestion as shown in report 200, Performance statistics (benchmark).

9.4.2

TCH Congestion and Blocking on BTS Hit List

For peak TCH congestion values per cell, run the report Cells having TCH congestion (135). = =

CELLS HAVING TCH CONGESTION

= =

Network:

PLMN

=

Area:

BSC - AAA_BSC_1

=

Period:

from 19970201 to 19970201

=

Threshold:

1

sec

= =============================================================================== This report shows each measurement period having TCH congestion over a given threshold. Aver avail TCH

/ava_2a

Average available TCH

SDCCH cong (sec)

/cngt_1

Time congestion on TCH

TCH raw blck (%)

/blck_1

Blocking on TCH

Measurement used: p_nbsc_res_avail, p_nbsc_traffic Running this report takes a few minutes. Patience please. =============================================================================== Cells having TCH congestion between 19970201 and 19970201 TCH Period

Period

BSC

BCF name

start

start

(BTS id)

BTS name

day

hour

Aver avail

raw Cong

blck

TCH (sec)

(%)

--------------- --------------------- ---------- ------ ----- ----- ------AAA_BSC_1

0823

(30)

DVabc

AAA_BSC_1

311

(50)

INAbb

1997-02-01 16:00

7.0

5

0.00

1997-02-01 13:00

7.0

11

0.00

14:00

7.0

104

2.02

20:00

7.0

4

0.00

Example 57. Report 135: Cells having TCH congestion

For TCH blocking, raw and call blocking, run the report Cells having high TCH raw blocking (138).


NTC TAN 0935/2.3 en


99

Cell Dimensioning

= =

CELLS HAVING HIGH TCH RAW BLOCKING

= =

Network:

=

Area:

PLMN BSC - BSC_XXXXX

=

Period:

from 19970201 to 19970202

=

Threshold:

blck_1 >= 2

=

Sorted by:

blck_1

= =============================================================================== This reports lists all cellS that have 2 % or more TCH assigns rejected because of lacking resources. For each cell: TCH Call Req

/c1026

TCH call request

New Call

/c1009

TCH call seizures for normal call

DR Out

/dr_3

Successful Directed Retry to another cell

TCH Call Block

/blck_8b TCH Call Block

TCH Raw Block

/blck_1

TCH Raw Block

Ave Avail TCH

/ava_2

Average available TCH

Note: Check the number of available TCHs. If it differs from the normal value, most probably there is a fault in question, and it should be solved first. Measurement used: p_nbsc_traffic, p_nbsc_res_avail, p_nbsc_ho Instructions: The reported cells may need extension or troubleshooting. Use reports Cell analyser (216) or Cell doctor (213) to check the pattern. Note: Running this report can take long time if the selected area is large. Patience please. ===============================================================================

Cells Having High TCH Raw Blocking between 19970201 and 19970202 TCH TCH BSC

BCF Name

Call

New Cal

(BTS id)

BTS Name

req

DR Out

TCH

Call

Raw

Ave

Block

Block

Avail

%

%

TCH

------------- ----------------- ------- ------- -------- -------- -------BSC_XXXXX

SSCQQ

(5)

029

1640

1640

8.714

Example 58. Report 138: Cells having high TCH raw blocking

For the call blocking ( blck_8a) peak hour value and average, run the report Busy hour traffic for all BTSs (182). TCH PEAK

TCH

HOUR

TRAFF

(mmddhh) (Erl)

call

SDCCH

SDCCH

block

TRAFF

block

(%)

(mErl)

(%)

*****

*****

*****

*****

*****

BSC name

BCF name

TCH

BH

BH

BH

BH

(BTS id)

BTS name

SDCCH

AVE

AVE

AVE

AVE


NTC TAN 0935/2.3 en


100

Cell Dimensioning

------------- -------------------- -------- ------- -------- --------- -------ABC_BSC_1

030

020116

3.6

0.0

374.3

0.0

(8)

SITE2

020117

1.2

0.0

138.2

0.0

ABC_BSC_1

030

020119

3.2

0.0

374.3

1.2

(9)

SITE3

020117

1.4

0.0

156.2

0.2

ABC_BSC_1

030

020121

2.4

0.0

238.9

0.0

(7)

SITE1

020119

0.8

0.0

95.5

0.9

Example 59. Report 182: Busy hour traffic for all BTSs

9.4.3

TCH Congestion and Blocking on BTS Level

For TCH congestion and blocking on the BTS level, run the report Cell analyser (216). .

Whole

SDCCH

.

period

busy hour

.

average

average

.

=======

=========

TCH requests for FACCH call setup ........../c10 43

0.0

0.0

. BLOCKED .............. ................ ../blck_14

0.00 %

0.00 %

. TCH seizures........ ............... ./100-blck_14

100.00 %

100.00 %

TCH requests for new call .............. ..../c1026

23.9

85.0

. BLOCKED TCH call requests .............. /blck_8b

0.00 %

0.00 %

. Succ. Directed Retry to other cell........./dr _5

0.00 %

0.00 %

. Succ. Directed Retry intracell .........../c40 74

0.00 %

0.00 %

. Succ. TCH seizures for call, queued ....../que_1

0.00 %

0.00 %

. Succ. TCH seizures for call, nonqueued .../que_7

100.00 %

100.00 %

TCH requests for handovers ............... ./ho_14a

3.4

7.0

. Succ. TCH seizures for HO, queued ......../que_2

0.00 %

0.00 %

. Succ. TCH seizures for HO, nonqueued ...../que_8

100.00 %

100.00 %

. BLOCKED handovers ............... ....../blck_11a

0.00 %

0.00 %

SMS establishments. ................ ..............

0.3

2.0

. Succesfull SMS establishments ............/c30 26

100.00 %

100.00 %

. Unsuccesfull SMS establishments ........../c30 27

0.00 %

0.00 %

TCH usage .............. ................ ..../trf_3

5.4 %

21.27 %

TCH congestion time ............... ......../cngt_1

0.0 s

0.0 s

Peak busy TCH (max).......... ............../t rf_19

6.0

6.0

TCH traffic ............... ........(Erl).. /trf_12a

0.4

1.5

************************************************************************ TCH call blocking percentage (blck_8b) ABC_BSC_1

bts:55 ITAG1

bcf:336

************************************************************************ Blank hours are either missing data or no TCH call requests. Hints: For the BTS level hit list, run report 250. tue


NTC TAN 0935/2.3 en

wed

thu

fri

sat

sun

mon

tue

wed


thu

fri

101

Cell Dimensioning

Hr

19

20

21

22

23

24

25

26

27

28

29

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

-- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----00

0.0

0.0

0.0

01

0.0

07

0.0

08

0.0

09

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

10

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

11

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

12

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

13

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

14

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

15

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

16

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

17

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

18

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

19

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

20

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

21

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

22 23

0.0

0.0

Example 60. BTS level data on TCH congestion and blocking as shown in report 216, Cell analyser.

For the hourly congestion values, see the report Cell doctor (213).

9.5

Traffic BSS Network Doctor provides a variety of reports to monitor traffic in the network on various levels.

9. 5 . 1

Hourly Traffic on BSC Level

To see the traffic on the BSC level per hour, run the t he report TCH traffic (Erlang) per hour for each BSC (180). = =

TCH TRAFFIC (ERLANG) PER HOUR FOR EACH BSC

= =

Network:

PLMN

=

Period:

from 19971119 to 19971119

= =============================================================================== For each BSC report: Traffic

/trf_1a

BSC traffic in Erlang

Congesction

/cngt_1

Congestion time in seconds

Avail TCHs

/ava_5

Number of available TCHs

Measurement used: p_nbsc_res_avail =============================================================================== Erlangs per hour for BSCs


NTC TAN 0935/2.3 en


102

Cell Dimensioning

Object:

BSC1-77206 Traffic

Start hour

Number of

(Erlang)

Congestion (sec)

Avail TCHs

BTSs

---------------------- ---------- ----------------- ---------- --------09:00 -

232.84

12585.61

468.81

27

10:00 -

262.84

18408.84

462.44

27

16:00 -

267.23

20266.14

462.00

27

17:00 -

265.29

20372.23

458.41

27

Erlangs per hour for BSCs Object:

BSC11-77504 Traffic

Start hour

Number of

(Erlang)

Congestion (sec)

Avail TCHs

BTSs

---------------------- ---------- ----------------- ---------- --------09:00 -

462.25

1445.70

1110.00

40

10:00 -

601.02

5378.39

1105.73

40

16:00 -

655.01

12118.43

1100.82

40

17:00 -

635.09

12995.63

1095.00

40

Example 61. Report 180: TCH traffic (Erlang) per hour for each BSC

9. 5 . 2

Traffic on Area Level

For daily sums of traffic, use the report Performance statistics (benchmark) (200). Avg

Day MMDD

TCH

HO/

TCH

Call

time

Calls

bids

(hr)

(%)

trf_39 trf_24c trf_13d

call

AG

Usage

lgth

block

(%)

(sec)

(%)

trf_3 trf_2b blck_13

--- ---- --------- ------- ------- ------- ------ ------tue 1124

129685

1934

313.43

8.52

54

0.000

mon 1123

140622

2093

315.64

8.83

54

0.000

sun 1122

122719

1837

230.91

7.75

54

0.000

sat 1121

130532

1953

231.29

8.26

54

0.000

fri 1120

134422

1994

230.00

8.41

53

0.000

Day MMDD

HO

HO

TCH

TCH

fail

blck

drop

drop

(%)

(%)

(%)

(%)

hfr_2

hfr_55

dcr_3g

dcr_3f

--- ---- ------- ------- ------- ------tue 1124

8.46

6.05

2.78

2.50

mon 1123

2.97

0.60

2.60

2.32

sun 1122

3.40

0.55

2.55

2.30

sat 1121

3.43

0.60

2.60

2.33

fri 1120

3.08

0.31

2.61

2.32

Example 62. Daily sums of traffic in report 200, Performance statistics (benchmark).

The Call distribution per LA (222) report shows for each location area:


NTC TAN 0935/2.3 en


103

Cell Dimensioning

•

The The ccou ount nt of of TCH TCH and and SDCC SDCCH H sei seizu zure ress for for term termin inat atin ing g and and orig origin inat atin ing g normal call setup

•

The share (%) of calls

•

The count of sent pagings Calls LAC

TCH

TCH

SDCCH

MTC

MOC

MOC

SDCCH in LA MTC

%

Paging

Pgn

Sent

Succ

*1000

(%)

------ -------- -------- ------ ------ ------ ------- ----

1

4951

262

0

0

97.0

10

52.1

2

0

7

0

0

0.1

0

0.0

3

30

87

0

0

2.2

0

55.2

65533

35

2

0

0

0.7

0

32.7

Total number of calls in the whole PLMN during given period =

5374

Example 63. Report 222: Call distribution per LA

You can select to run the report over the whole given period or over the traffic busy period of each location area. For traffic on hourly level, run the report Performance profiles for area, 24-hour/10-day breakdowns (207). TCH traffic until 19970716 formula:trf_1 , unit: Erl sun Hr

mon

tue

wed

thu

fri

sat

sun

mon

tue

wed

06

07

08

09

10

11

12

13

14

15

16

JUL

JUL

JUL

JUL

JUL

JUL

JUL

JUL

JUL

JUL

JUL

-- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----00

22

22

21

23

20

27

23

23

24

20

26

01

15

10

10

12

10

15

12

14

10

10

13

02

9

4

4

5

7

7

7

11

4

3

6

03

5

3

1

2

1

4

6

2

2

2

04

3

2

2

1

1

2

2

4

1

0

2

05

2

1

1

1

1

1

1

1

1

1

2

06

2

4

4

5

4

4

2

2

3

5

5

07

4

13

14

15

14

14

8

4

13

15

19

08

9

31

33

31

36

34

17

13

32

39

31

09

21

52

61

57

58

55

34

22

48

59

56

10

33

52

61

60

62

60

46

39

50

58

60

11

47

53

63

66

71

61

56

47

57

65

12

46

52

61

57

65

61

62

48

52

58

13

44

38

47

53

52

51

54

43

40

47

14

46

51

57

55

62

57

51

44

46

52

15

44

55

59

59

68

66

53

37

51

58

16

43

60

61

62

66

69

53

40

56

61

17

44

62

71

69

70

69

50

43

60

65

18

59

81

82

87

93

84

60

53

81

84

19

67

91

92

99

96

89

75

67

80

81

20

75

119

131

140

127

127

82

78

120

117

21

76

128

142

136

131

127

77

74

126

131

22

64

86

90

83

87

77

58

59

87

91


NTC TAN 0935/2.3 en


104

Cell Dimensioning

23

39

42

48

44

51

38

40

39

42

45

Example 64. Hourly area-level traffic in report 207, Performance profiles for area, 24-hour/10-day breakdowns.

9. 5 . 3

Traffic on BTS Hit List Level

The data on busy hours by BTS for SDCCH and TCH traffic is provided by the report Busy hour traffic for all BTSs (182). By following the busy hour traffic trend you can estimate possible future congestion. TCH PEAK

TCH

HOUR

TRAFF

(mmddhh) (Erl)

call

SDCCH

SDCCH

block

TRAFF

block

(%)

(mErl)

(%)

*****

*****

*****

*****

*****

BSC name

BCF name

TCH

BH

BH

BH

BH

(BTS id)

BTS name

SDCCH

AVE

AVE

AVE

AVE

------------- -------------------- -------- ------- -------- --------- -------ABC_BSC_1

030

020116

3.6

0.0

374.3

0.0

(8)

SITE2

020117

1.2

0.0

138.2

0.0

ABC_BSC_1

030

020119

3.2

0.0

374.3

1.2

(9)

SITE3

020117

1.4

0.0

156.2

0.2

ABC_BSC_1

030

020121

2.4

0.0

238.9

0.0

(7)

SITE1

020119

0.8

0.0

95.5

0.9

Example 65. Report 182: Busy hour traffic for all BTSs

For summarised and average traffic, see the report Cells having maximum TCH traffic (185). This report also shows the values for call blocking and TCH HO blocking. = =

CELLS HAVING MAXIMUM TCH TRAFFIC

= =

Network:

=

Area:

PLMN MR - all MRs

=

Period:

from 19970201 to 19970202

= =============================================================================== The following data is shown per cell sorted out by traffic: Traffic sum

/trf_1

Sum of average busy TCH.

.

(Equal to Erlang if 60 min meas. period used)

Traffic ave

/trf_12b

Average Traffic.

Congestion

/cngt_1

TCH congestion.

Ave avl TCH

/ava_2a

Average available TCH.

Ave call blck

/blck_8b

Average TCH call blocking

Ave HO blck

/blck_11a

Average TCH handover blocking

Measurement used: p_nbsc_traffic, p_nbsc_res_avail, p_nbsc_ho Note: Running this report takes a few minutes. Patience please.


NTC TAN 0935/2.3 en


105

Cell Dimensioning

===============================================================================

Cell TCH Traffic between 19970201 and 19970202 Traffic

Ave

*******

Ave

Ave

Call

HO

BSC

BCF Name

Sum

Cong

avl

blck

blck

(BTS id)

BTS Name

Ave

(sec)

TCH

(%)

(%)

------------- ----------------- -------- --------- ------ ------ -----BSC_SSSSS

106C

86.1

(51)

ELAMM

BSC_XXXXX

078A

(36)

ABCWW

BSC_ZZZZZ

056

(55)

CM1WW

BSC_SSSSS

082

(35)

TP1QQ

BSC_SSSSS

067

(30)

JC1MM

2947.8

7.0

0.0

0.1

0.0

14.0

0.0

0.0

560.1

7.0

0.0

0.0

0.0

14.0

0.0

0.0

950.9

7.0

0.0

0.0

2.0 62.2 1.4 58.6 1.3 54.0 1.2 53.5 1.2

Example 66. Report 185: Cells having maximum TCH traffic

9.5.4

Traffic on BTS Level

For averages over the whole period, the busy hour and hourly breakdown, run the report Cell analyser (216). ************************************************************************ Peak busy TCH (trf_19) ABC_BSC_1

bts:55 ITAG1

bcf:336

************************************************************************ Blank hours are missing data.

Hr

tue

wed

thu

fri

sat

sun

mon

tue

wed

thu

fri

19

20

21

22

23

24

25

26

27

28

29

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

-- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----00

1

0

1

1

0

0

0

0

01

0

0

0

1

0

0

02

0

0

0

0

0

03

0

0

0

0

04

0

0

0

0

05

0

0

0

06

0

0

0

07

0

0

08

0

0

09

1

10

2

11 12

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

1

0

0

0

0

0

0

0

0

1

2

1

1

1

0

0

1

1

1

0

1

2

2

2

1

2

3

2

1

1

2

2

2

1

3

2

2

4

1

2

3

4

3

4

3

3

3

3

3

4

3

4

3

4

13

4

4

4

3

3

3

4

4

4

4

14

4

3

3

3

4

3

2

4

3

4


NTC TAN 0935/2.3 en


0

0

106

Cell Dimensioning

15

4

3

2

4

2

3

3

4

2

4

16

3

3

3

4

2

3

3

3

3

3

17

3

5

3

3

2

3

4

5

4

3

18

3

3

4

4

3

2

4

4

5

3

19

2

3

4

4

2

3

3

4

3

3

20

2

3

4

5

3

5

3

4

2

6

21

3

2

3

4

2

3

2

2

1

5

22 23

1

2

1

2

2

1

1

2

1

3

1

0

0

1

1

0

0

1

0

2

0

************************************************************************ TCH traffic (Erlang) ABC_BSC_1

(trf_12a)

bts:55 ITAG1

bcf:336

************************************************************************ Blank hours are missing data. Hints: For the BTS level hit list, run report 185.

Hr

tue

wed

thu

fri

sat

sun

mon

tue

wed

thu

fri

19

20

21

22

23

24

25

26

27

28

29

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

-- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----00

0.0

0.0

0.2

0.3

0.0

0.0

0.0

0.0

01

0.0

0.0

0.0

0.0

0.0

0.0

02

0.0

0.0

0.0

0.0

0.0

03

0.0

0.0

0.0

0.0

04

0.0

0.0

0.0

0.0

05

0.0

0.0

0.0

06

0.0

0.0

0.0

07

0.0

0.0

08

0.0

0.0

09

0.1

10

0.1

11 12

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.1

0.0

0.0

0.1

0.0

0.0

0.0

0.0

0.1

0.0

0.0

0.2

0.3

0.2

0.0

0.2

0.5

0.2

0.0

0.1

0.1

0.2

0.1

0.1

0.4

0.2

0.6

0.3

0.1

0.1

0.4

0.6

0.9

0.6

0.6

0.6

0.7

0.5

0.4

0.6

0.6

0.9

0.3

1.1

13

1.0

0.3

0.4

1.1

0.3

0.6

0.7

0.8

1.0

0.9

14

0.4

0.8

0.2

0.8

0.5

0.4

0.3

0.6

0.5

0.6

15

0.7

0.3

0.3

0.9

0.2

0.4

0.3

0.7

0.4

0.6

16

0.5

0.3

0.6

0.5

0.1

0.7

0.6

1.1

0.5

0.7

17

0.5

0.9

0.5

0.8

0.1

0.8

0.7

1.1

0.6

0.4

18

0.6

0.6

0.4

0.8

0.3

0.6

0.5

0.9

1.1

0.8

19

0.3

0.7

0.8

0.9

0.2

0.6

0.5

0.8

0.8

0.6

20

0.1

0.6

0.7

1.3

0.2

0.7

0.4

0.6

0.5

1.5

21

0.4

0.2

0.5

1.0

0.2

0.5

0.3

0.3

0.1

1.0

22 23

0.0

0.0

0.0

0.1

0.0

0.5

0.3

0.0

0.1

0.0

0.0

0.2

0.1

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.0

Example 67. BTS level data on traffic averages over the whole period in report 216, Cell analyser.

The Daily traffic profile for a BTS (181) report shows for each hour of the given time period: •

Average and peak number of busy TCH

•

Congestion time of SDCCH and TCH

•

TCH seizures for a normal call and handovers


NTC TAN 0935/2.3 en


107

Cell Dimensioning

•

TCH seizure attempts for calls and handovers failing due to congestion

•

Number of attempted and successfully directed new calls from the SDCCH of the selected cell to the TCH of another cell Daily traffic profile for BTS- 5 xxxxxxxx2

of BSC1

from 19971119 to 19971119 SDCCH

TCH

cong

cong

Ave Peak busy busy DD HH

TCH

TCH

time

time

(sec)

(sec)

DR Blocked Calls

Calls

DR

Blocked

out

out

HOs

att

succ

HOs

-- -- ------ ---- ------- ------- ------- ------- ------- ------- ----- ----19 09

2.31

6

.0

80.0

151

0

325

2

0

0

10

3.95

6

.3

660.6

189

23

805

108

35

15

16

4.11

6

.0

769.5

214

16

916

134

26

12

17

3.55

6

.2

919.0

156

70

747

155

90

26

Example 68. Report 181: Daily traffic profile for a BTS

9.6

Miscellaneous The BSC unit load for each BSC (184) report shows for every processor unit of all BSCs: •

Average load

•

Minimum and maximum peak load

•

Time when the maximum peak load of a unit occurs Unit load % per day for BSCs from 19970201 to 19970202

Object:

BSC_XXXXX-88888

Unit name and index

Avg load

Min Peak

Max Peak

Peak hour

(%)

load (%)

load (%)

(yyyymmddhh)

------------------------- --------- --------- --------- -----------BCSU-0

0.87

6.00

8.00

1997020221

BCSU-1

1.08

4.00

6.00

1997020111

BCSU-2

0.06

2.00

3.00

1997020111

BCSU-3

0.34

3.00

4.00

1997020111

BCSU-4

0.74

5.00

7.00

1997020216

BCSU-5

0.00

2.00

2.00

1997020104

BCSU-6

0.79

4.00

5.00

1997020112

MB-0

1.00

2.00

2.00

1997020100

MCMU-0

1.01

30.00

30.00

1997020117

MCMU-1

0.61

31.00

32.00

1997020114

OMU-0

1.10

78.00

79.00

1997020114

Example 69. Report 184: BSC unit load for each BSC

In the Cells having maximum paging traffic (186) report the cells are reported in the order of the number of paging messages sent. For each cell the following values are counted: Document number/Issue

NTC TAN 0935/2.3 en


108

Cell Dimensioning

•

Number of paging messages sent

•

Average PCH load

•

Number of terminated calls

•

Minimimum paging buffer space on PCH

•

Average of the minimums of paging buffers. BTS paging traffic between 19970201 and 19970202 Ave Paging

Ave

BSC

BCF name

msgs

PCH

(BTS id)

BTS name

sent

load

Min

of min

Term page buf page buf calls

space

space

--------------- ------------------ --------- ------ -------- -------- -------BSC_XXXXX

040

(16)

SWWWW

BSC_XXXXX

040

(17)

SWWQQ

BSC_XXXXX

046

(19)

PPPWW

BSC_XXXXX

046

(20)

PPPQQ

60365

64

371

62

63.0

60365

16

130

14

15.0

60365

64

261

62

63.1

60365

64

243

62

63.2

Example 70. Report 186: Cells having maximum paging traffic

In the Cell location updates (187) report the BTSs are reported in the order of average LU counts (Avg LU). A high LU amount can cause SDCCH blocking. One possible reason is an MS moving across the LA border in idle mode. A high number of handovers from other location areas may also mean that there is a high number of idle MSs moving from those areas. Location updates per cell between 19980904 and 19980914 SDCCH bl % Avg LU BSC Name

BCF Name

SDCCH us % Avg MTC

LUP (h)

Adj across

(BTS id)

BTS Name

SDCCH av % Avg MOC

HYS (dB) HOs across

----------- --------------- ---------- -------- -------- ---------BSC1KUTOJA

SANDPG009

(17)

SANDPG1017

0.00

5

3.0

6

0.07

0.4

4.0

40

100.00

1.1

BSC2UPS1

3UPS001

0.00

4

0.5

1

(1)

3UPS2001

0.04

0.1

4.0

39

99.99

0.5

BSC3TRE

HERMIA005

0.00

0

0.5

0

(15)

HER3AP3015

0.00

0.0

4.0

0


NTC TAN 0935/2.3 en


109

Cell Dimensioning

100.00

0.0

Example 71. Report 187: Cell location updates

In the Cells having peak RACH load (188) report the BTSs are reported in the order of peak RACH load counts. An extremely high RACH load can indicate a cell with fatal problems. In that case use the Cell analyser (216) report to check the cell. Rach load (%) between 19970201 and 19970202 BSC

BCF Name

RACH load

(BTS id)

BTS Name

(%)

------------- ------------------------------ --------BSC_XXXXX

304

(44)

ISHWW

BSC_XXXXX

078A

(36)

ABCWW

BSC_XXXXX

111

(31)

CDCWW

BSC_XXXXX

028

(2)

TTTQQ

BSC_XXXXX

111

(33)

CDCMM

3

1

1

1

1

Example 72. Report 188: Cells having peak RACH load

The Cells sorted by SDCCH or TCH holding time (189) report shows for each cell the average SDCCH and FTCH holding time. BTS having shortest

holding time

between 19970201 and 19970202 Average SDCCH Average FTCH BSC Name

BCF Name

(BTS id)

BTS Name

holding time holding time (sec)

(sec)

--------------- ------------------ ------------- -----------BSC_XXXXX

200

(37)

XMAWW

BSC_XXXXX

201

(47)

XRAQQ

BSC_XXXXX

207

(54)

XNOWW

BSC_XXXXX

204

(35)

XSOWW

BSC_XXXXX

206

(34)

XNEWW


NTC TAN 0935/2.3 en

1.1

14.8

1.9

9.6

2.1

28.8

2.1

25.9

2.2

20.0


110

Cell Dimensioning

Example 73. Report 189: Cells sorted by SDCCH or TCH holding time


NTC TAN 0935/2.3 en


111

Call Success

10

CALL SUCCESS In this chapter call success is handled under the following headings: •

Traffic channel access and success

•

SMS establishment failures

•

RACH rejections

•

High HO attempts/call ratio

•

Transcoder failures

•

High drop call count in handovers

10.1 Traffic Channel Access and Success The overall call success is the product of the following factors: •

SDCCH access

•

SDCCH success

•

TCH access

•

TCH success

This is an alternative way to analyse the network instead of focusing the contributors separately (SDCCH blocking, SDCCH drops, TCH blocking, TCH drop calls). BSS Network Doctor provides reports for analysing the call success on all levels from BTS area to a single BTS. The Network benchmark statistics (204) report shows the area level values for the call success factors as an average. CALL SUCCESS FACTORS ==================== SDCCH access probability .

(before FCS) ................ ............./c sf_1

12.72 %

.

(after FCS) .............. .............../ csf_1a

12.72 %

SDCCH success ratio .

(SDCCH fail based, incl.LU) ............./ csf_2a

98.91 %

.

(SDCCH to TCH based) ............... ...../csf_2f

91.14 %

TCH access probability .

(before DR and queuing) ............... ../csf_3j

100.00 %

.

(before DR) .............. .............../ csf_3i

100.00 %

.

(real) .............. ............... ...../csf_3k

100.00 %

TCH success ratio


NTC TAN 0935/2.3 en


112

Call Success

.

(before re-est.) .............. ........../csf_4 o

96.86 %

.

(after re-est) .............. ............/cs f_4p

96.86 %

Example 74. Call success factors in report 204, Network benchmark statistics

The Performance statistics (benchmark) (200) report shows the area level values for the call success factors as daily values. SDCCH

SDCCH

SDCCH

TCH

TCH

access access success success

access

access

access success success

probab probab

probab

probab

probab

(%) Day MMDD

SDCCH ratio

ratio

TCH

TCH

TCH

ratio

ratio

(%)

(%)

(%)

(%)

(%)

(%)

(%)

(%)

csf_1 csf_1a

csf_2a

csf_2f

csf_3j

csf_3i

csf_3k

csf_4o

csf_4p

--- ---- ------ ------ ------- ------- ------- ------- ------- ------- ------tue 1124

99.21

99.21

98.31

95.24

99.88

99.88

99.93

97.22

97.50

mon 1123

99.72

99.72

98.39

95.33

99.95

99.95

99.99

97.40

97.68

sun 1122

99.82

99.82

98.34

95.67

99.98

99.98

99.99

97.45

97.70

sat 1121

99.83

99.83

98.43

95.61

99.95

99.95

99.99

97.40

97.67

fri 1120

99.83

99.83

98.43

95.25

99.93

99.93

99.98

97.39

97.68

Example 75. Call success factors as daily values in report 200, Performance statistics (benchmark)

The Performance profiles for area, 24-hour/10-day breakdowns (207) report shows the area level values on hourly level. SDCCH Success Ratio (%) until 19970716 formula: csf_2a, unit: %

Hr

sun

mon

tue

wed

thu

fri

sat

sun

mon

tue

wed

06

07

08

09

10

11

12

13

14

15

16

JUL

JUL

JUL

JUL

JUL

JUL

JUL

JUL

JUL

JUL

JUL

-- ------ ------ ------ ------ ------ ------ ------ ------ ------ ------ -----00

96.6

97.0

97.2

96.8

96.7

96.4

97.6

96.4

97.5

96.5

97.1

01

97.5

97.3

97.2

97.5

96.9

96.8

97.4

96.7

97.5

97.7

97.4

02

96.7

97.7

98.1

97.7

97.5

97.9

97.4

95.9

97.9

97.9

98.2

98.0

97.4

98.4

98.6

97.9

98.4

98.1

98.0

98.3

97.2

98.3

03

96.8

97.7

98.5

98.1

98.1

04

97.7

98.0

97.8

98.4

98.4

TCH Success ratio until 19970716 formula: csf_4p (after re-establishment), unit: %

Hr

sun

mon

tue

wed

thu

fri

sat

sun

mon

tue

wed

06

07

08

09

10

11

12

13

14

15

16

JUL

JUL

JUL

JUL

JUL

JUL

JUL

JUL

JUL

JUL

JUL

-- ------ ------ ------ ------ ------ ------ ------ ------ ------ ------ -----00

96.1

95.2

94.8

94.1

94.1

94.6

95.5

93.2

95.6

93.4

95.2

01

95.4

95.3

92.2

95.2

93.4

96.0

94.7

94.4

95.3

96.3

94.2

02

96.4

93.0

93.9

93.3

92.4

98.4

95.0

96.0

95.4

88.2

93.8

03

94.2

95.1

98.2

94.8

93.9

93.6

95.9

93.8

98.3

94.2

04

96.4

96.2

92.2

100.0

97.3

91.3

94.9

92.0

85.0

98.8

96.0

Example 76. Area-level success ratios on hourly level in report 207, Performance profiles for area, 24-hour/10-day breakdowns


NTC TAN 0935/2.3 en


113

Call Success

The Cells by call success ratio (250) report shows the BTS level values for the call success factors as an average. Call Success Ratio per Cell between 19990318 and 19990318 Ave avail BSC (BTS id)

******

BCF NAME

SDCCH

BTS NAME

TCH

SDCCH

SDCCH

TCH

TCH

access success

access success

Call

SDCCH

probab

ratio

probab

ratio

success

seiz

csf_1a

csf_2a

csf_3k

csf_4q

ratio

----------------- ------- ------- ------- ------- ------- ------- --- ------BSC1KUTOJA (18)

5.50

SANDPG009

3.00

132

100.00

96.90

100.00

96.28 ==>

93.29

132

100.00

99.24

100.00

99.48 ==>

98.72

SANDPG1018 BSC1KUTOJA (20)

5.50

SANDPD010

7.00

SANDPD1020

Example 77. Report 250: Cells by call success ratio

The Call success profiles of a cell (251) report shows the overall call success ratio as a result of access probability and success ratio of the SDCCH and TCH channels for a single cell. Call Success Ratio of SLCG2 between 19970201 and 19970201 SDCCH

Day yyyymmdd

SDCCH

TCH

TCH

access success

access success

probab

probab

ratio

Call

ratio

success

/csf_1a /csf_2a /csf_3d /csf_4q

ratio

--- --------- ------- ------- ------- ------- --- ------sat 19970201

100.00

96.78

100.00

98.80 ==>

95.61

Example 78. Report 251: Call success profiles of a cell


NTC TAN 0935/2.3 en


114

Transmission

11

TRANSMISSION The quality of the transmission can be measured as a count of different transmission alarms. Usable alarms in this respect are the TRX alarm 7705, LAPD Link Failure and BTS alarm 2567, BCCH Missing. The former describes the situation when the signalling link between a BSC and BTS has been disturbed. The latter, again, describes the situation when the cell has been down, although it is not known whether it results from transmission or something else. To see the occurrences of TRX alarm 7705 per day and per BTS, run the report BSC alarm breakdown (030). = =

BSC ALARM BREAKDOWN

= =

Network:

=

Maintenance Region: GSM1800

=

Alarm id:

= = =

PLMN 9047

Alarm txt:

ALARMS FROM NETWORK ELEMENT NOT ARRIVING

Period:

10 days ending on 19980421

= =============================================================================== Alarms (id given by user) received from the network are presented for all BSCs over 10 days. - alarm id - the last day of a 10-day period =============================================================================== Breakdown for alarm sat BSC

sun

mon

tue

wed

9047

thu

fri

sat

sun

mon

tue

11

12

13

14

15

16

17

18

19

20

21

APR

APR

APR

APR

APR

APR

APR

APR

APR

APR

APR

------------------ ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---BSC1KUTOJA BSC2UPS1

2 5

1

5

BSC3TRE

8

6

9

1

14 1

3

2

1

---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---sum

5

1

5

9

6

11

15

3

2

1

Example 79. Report 030: BSC alarm breakdown

If the LAPD link is down long enough, the entire BTS may lose service, and the BCCH Missing alarm is generated by the BSC. To see the BCCH Missing alarm (=cell outage) occurrences per day and per BTS, run the report Cell outage breakdown over 10 days (027). =


NTC TAN 0935/2.3 en


115

Transmission

=

CELL OUTAGE BREAKDOWN OVER 10 DAYS

= =

Network:

PLMN

=

Area:

All BTSs selected

=

Period:

10 days until

19981130

= =============================================================================== The BCCH missing alarms (2567 until S7, 7767 since S7) received from the area during the given period are presented for all BTS over a period of 10 days. The number in the table means the number of occurrences of 'BCCH missing' alarms (i.e. start of cell outage) during the day. Note that the BCCH missing alarm means that the cell has been down. =============================================================================== Cell Outage Breakdown BTS name BCF name BSC name (BTS id)

fri

sat

sun

mon

tue

wed

thu

fri

sat

sun

mon

20

21

22

23

24

25

26

27

28

29

30

NOV

NOV

NOV

NOV

NOV

NOV

NOV

NOV

NOV

NOV

NOV

-------------------- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---3UPS2001

3

3UPS001 BSC2UPS1(1) 3UPS2002

3

3UPS001 BSC2UPS1(2) ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---sum

6

Example 80. Report 027: Cell outage breakdown over 10 days

To see summary info on transmission availability and quality, run the report Transmission statistics (518). = =

TRANSMISSION STATISTICS

= =

Network:

PLMN

=

BSC:

all BSC

=

Period:

from 19980610 to 19980610

= =============================================================================== =============================================================================== = =

DMR

= =============================================================================== Avail (%)

/ava_6

Err sec

/c62002 The total duration of the errored seconds.

Severe Err sec

/c62003 The total duration of the severely errored seconds.

Degr min

/c62004 The total duration of the degraded minutes.

RF in min lev

/c62005 Incoming RF level min.

RF in max lev

/c62006 Incoming RF level max.


NTC TAN 0935/2.3 en

Availability


116

Transmission

Spec

Specification used.

Measurement used: p_nbsc_dmr =============================================================================== BSC1KUTOJA-

DMR

from 19980610 to 19980610 RF in Avail DMR DMR index name

Severe

RF in

min

max

(%)

Err

Err

Degr

lev

lev

ava_6

sec

sec

min

(dBm)

(dBm) Spec

----- ---------- ------- ------ ------ ------ ------ ------ ----------1001 KUT-SUOS

100.00

0

0

0

38

37 G.821

1002 SUOS-KUT

100.00

0

0

0

33

33 G.821

0.00

0

0

0

99

99 G.821

1003 SUOS-LAAJA

BSC2UPS1-

DMR

from 19980610 to 19980610 RF in Avail DMR DMR index name

Severe

RF in

min

max

(%)

Err

Err

Degr

lev

lev

ava_6

sec

sec

min

(dBm)

(dBm) Spec

----- ---------- ------- ------ ------ ------ ------ ------ ----------1

100.00

3

3

0

33

36 G.821

=============================================================================== = =

DN2

= =============================================================================== Port Avail (%)

Port of DN2 /ava_7 Availability

Err sec


Err sec severe


Degr min


Measurement used: p_nbsc_dn2 =============================================================================== BSC1KUTOJA - DN2 from 19980610 to 19980610 Avail DN2 DN2 index name

DIR

Severe

(%)

Err

Err

ava_7

sec

sec

Degr min Spec

----- ---------- ---------- ------- ------ ------ ------ ----------1 DN2_1


NTC TAN 0935/2.3 en

1

100.00

0

0

0 G.821

2

100.00

0

0

0 G.821

3

100.00

0

0

0 G.821

4

100.00

0

0

0 G.821

5

100.00

0

0

0 G.821

7

100.00

0

0

0 G.821

8

100.00

0

0

0 G.821

9

100.00

0

0

0 G.821

10

100.00

0

0

0 G.821

11

100.00

0

0

0 G.821


117

Transmission

3 DN2_3

12

100.00

0

0

0 G.821

14

100.00

0

0

0 G.821

19

100.00

0

0

0 G.821

20

100.00

0

0

0 G.821

1

100.00

0

0

0 G.821

2

100.00

0

0

0 G.821

=============================================================================== = =

TRU

= =============================================================================== Dir

Direction

Avail (%)

/ava_8 Availability

Err sec


Err sec severe


Degr min


Spec

Specification used.

Measurement used: p_nbsc_tru_bie Note: TRU should be ugraded at least to firmware version 02B to make measurment work. =============================================================================== BSC1

- TRU

from 19980610 to 19980610 Avail Host BCF name

TRU index Dir

Severe

(%)

Err

Err

ava_7

sec

sec

Degr min Spec

------------- ----- --- ------- ------ ------ ------ ----------KILO007

1

1

100.00

0

0

0 G.826

2

100.00

0

0

0 G.826

3

0.00

0

0

0 G.826

KILONKALLI

1

1

100.00

0

0

0 G.826

SANDPG009

1

1

100.00

1

0

1 G.826

2

100.00

0

0

0 G.826

3

0.00

0

0

0 G.826

BSC2

- TRU

from 19980610 to 19980610 Avail Host BCF name

TRU index Dir

Severe

(%)

Err

Err

ava_7

sec

sec

Degr min Spec

------------- ----- --- ------- ------ ------ ------ ----------MAKKYL006

HIPPOS009

SANKUD010

1

1

1

1

100.00

0

0

0 G.826

2

0.00

0

0

0 G.826

3

0.00

0

0

0 G.826

1

100.00

3

0

0 G.826

2

0.00

0

0

0 G.826

3

0.00

0

0

0 G.826

0

100.00

0

0

0 G.821

BSC3

- TRU

from 19980610 to 19980610 Avail Host BCF


NTC TAN 0935/2.3 en

TRU

(%)

Severe Err

Err

Degr


118

Transmission

name

index Dir

ava_7

sec

sec

min Spec

------------- ----- --- ------- ------ ------ ------ ----------HATANP001

1

HERMIA002

1

1

100.00

0

0

0 G.826

2

0.00

0

0

0 G.826

3

0.00

0

0

0 G.826

1

100.00

0

0

0 G.826

2

100.00

0

0

0 G.826

3

0.00

0

0

0 G.826

Example 81. Report 518: Transmission statistics

To see more detailed profiles of each transmission object, run the following profile reports. •

To see the availability and quality of radio relay equipment, run the report DMR profile (515). DMR Profiles BSC1 from 19980610 to 19980610

Avail DMR DMR index name

dd hh

RF in

RF in

min

max

Severe

(%)

Err

Err

Degr

lev

ava_6

sec

sec

min

(dBm)

lev (dBm) SPEC

----- ---------- -- -- ------- ------ ----- - ------ ------ ------ ----1001 KUT-S1

10 00 01

1002 SUOS-K2

1003 SUOS-L2

10 03

100.00

0

100.00

0

0 0

0

38

37 G.821

0

39

37 G.821

0

34

33 G.821

04

100.00

0

0

0

34

33 G.821

05

100.00

0

0

0

34

33 G.821

0

0

99

99 G.821

10 03

100.00

0

0.00

0

0

04

0.00

0

0

0

99

99 G.821

05

0.00

0

0

0

99

99 G.821

06

0.00

0

0

0

99

99 G.821

07

0.00

0

0

0

99

99 G.821

Example 82. Report 515: DMR profile

•

To see the availability and quality of dynamic node equipment, run the report DN2 profile (516). DN2 Profiles BSC1KUTOJA from 19980610 to 19980610 Avail DN2 DN2 index name

(%) dd hh Port

ava_7

Err Err

sec

sec severe

Degr min SPEC

----- ---------- -- -- ---- ------- ------ ------ ------ ----1 DN2_1


NTC TAN 0935/2.3 en

10 00

1

100.00

0

0

0 G.821

2

100.00

0

0

0 G.821

3

100.00

0

0

0 G.821

4

100.00

0

0

0 G.821

5

100.00

0

0

0 G.821

7

100.00

0

0

0 G.821

8

100.00

0

0

0 G.821

9

100.00

0

0

0 G.821

10

100.00

0

0

0 G.821


119

Transmission

11

100.00

0

0

0 G.821

12

100.00

0

0

0 G.821

14

100.00

0

0

0 G.821

19

100.00

0

0

0 G.821

20

100.00

0

0

0 G.821

01

1

100.00

0

0

0 G.821

2

100.00

0

0

0 G.821

3

100.00

0

0

0 G.821

4

100.00

0

0

0 G.821

Example 83. Report 516: DN2 profile

•

To see the availability and quality of top rack unit equipment, run the report TRU profile (517). TRU Profiles BSC1KUTOJA from 19980610 to 19980610 Avail Host BCF name

TRU

(%)

index dd hh Dir

ava_8

Err Err

sec

sec severe

Degr min Spec

------------- ----- -- -- --- ------- ------ ------ ---- -- ----KILO007

1 10 00

01

02

03

1

100.00

0

0

0 G.826

2

100.00

0

0

0 G.826

3

0.00

0

0

0 G.826

1

100.00

0

0

0 G.826

3

0.00

0

0

0 G.826

2

100.00

0

0

0 G.826

1

100.00

0

0

0 G.826

2

100.00

0

0

0 G.826

3

0.00

0

0

0 G.826

1

100.00

0

0

0 G.826

3

0.00

0

0

0 G.826

2

100.00

0

0

0 G.826

Example 84. Report 517: TRU profile


NTC TAN 0935/2.3 en


120

Network Element Availability

12

NETWORK ELEMENT AVAILABILITY The quality of the network elements can be measured as their availability, which in turn is basically affected by actions taken by the user and by faults.

12.1 Availability of Transceivers 12.1.1

Availability of Transceivers on BSC Level

For the availability of TRXs on the BSC level, run the report Unavailability classification per BSC (131). = =

UNAVAILABILITY CLASSIFICATION PER BSC

= =

Network:

=

Period:

PLMN from 19970201 to 19970203

= =============================================================================== This report shows for each BSC in the network: Unava. due to user (%)

/uav_4

Share of unavailability caused by user.

Unava. due to int. (%)

/uav_5

-"- caused by internal reasons.

Unava. due to ext. (%)

/uav_6

-"- caused by external reasons.

Unava. TRX time due to user (min) /uav_7

TRX unavailability time caused by user.

Unava. TRX time due to int. (min) /uav_8

-"- caused by internal reasons.

Unava. TRX time due to ext. (min) /uav_9

-"- caused by external reasons.

Measurement used: p_nbsc_res_avail =============================================================================== Unava.

Unava.

TRX time

TRX time

due to

due to

Unava.

Unava.

Unava. TRX time

due to

due to

due to

user int.cause ext.cause BSC

Unava.

(%)

(%)

(%)

due to

user int.cause ext.cause (min)

(min)

(min)

--------------- ------- --------- --------- -------- --------- --------XXXXXXXX1

4.81

47.64

47.55

85

842

840

XXXXXXXX2

96.89

0.01

3.10

8642

1

276

XXXXXXXX3

50.00

20.00

30.00

3

1

2

XXXXXXXX4

99.27

0.19

0.54

8857

17

48

XXXXXXXX5

89.40

1.79

8.82

4455

89

439

XXXXXXXX6

53.40

36.13

10.47

68

46

13

Example 85. Report 131: Unavailability classification per BSC

12.2 Availability of Timeslots BSS Network Doctor provides some reports which can be used to check the availability of timeslots. However, on the cell level it is difficult to distinguish whether the unavailability is due to the user or to a fault. On the cell level, examining the alarms is the only means to try to separate these two cases to some extent.


NTC TAN 0935/2.3 en


121


12.2.1

Availability of SDCCH and TCH on Area Level

To find about the availability of SDCCH and TCH on the area level, run the report Performance statistics (benchmark) (200). SDCCH

SDCCH

SDCCH

SDCCH

SDCCH

SDCCH

SDCCH

avail

congst

usage

seiz

HO seiz

assign

block

(min)

(%)

att

(%)

(%)

(%)

(%)

cngt_2 trf_7b

c1000

trf_32

trf_33 blck_5a

trf_38

(%) Day MMDD

ava_4

To FCS

--- ---- ------- ------- ------ --------- --- ------- ------- ------- ------tue 1124

96.56

7.9

3.4

893231 ==>

0.00

99.21

0.79

0.00

mon 1123

99.99

5.3

3.8

961803 ==>

0.00

99.72

0.28

0.00

sun 1122

99.98

4.6

3.8

939784 ==>

0.00

99.82

0.18

0.00

sat 1121

99.58

4.5

3.7

944330 ==>

0.00

99.83

0.17

0.00

fri 1120

100.00

3.5

3.7

947822 ==>

0.00

99.83

0.17

0.00

Day MMDD

TCH

Succ

TCH

TCH

TCH

TCH

TCH

call

DR

call

seiz

seiz

avail

congst

req

out

block

qd

non qd

(%)

(%)

(%)

dr_6 blck_8c

que_1

(%)

(min)

ava_1

cngt_2

trf_18a

(%) que_7

--- ---- ------- -------- --------- --- ------- ------- ------- ------tue 1124

95.48

6.37

129776 ==>

0.05

0.07

0.00

99.88

mon 1123

99.99

0.05

140641 ==>

0.03

0.01

0.00

99.95

sun 1122

99.98

0.04

122734 ==>

0.01

0.01

0.00

99.98

sat 1121

99.70

0.08

130547 ==>

0.03

0.01

0.00

99.95

fri 1120

100.00

0.00

134450 ==>

0.05

0.02

0.00

99.93

Example 86. Area level data on SDCCH and TCH availability in report 200, Performance statistics (benchmark).

12.2.2

Availability of Time Slots on BTS Hit List

For the availability of time slots on a BTS Hit List, run the report Cells having unavailable radio time slots (139). Cells having unavailable TSL between 19980915 and 19980915 Ave BSC (BTS id)

Ave

Ave

Non

Ave

Ave

Non

Non

BCF Name

Avail

Avail

Avail

Avail

Avail

BTS Name

SDCCH

HTCH

FTCH

TCH

TSL Hours

--------------- --------------- ------- ------- ------- ------- ------- ----GFXBSC01

Site AAA

(13)

Cell A

GFXBSC01

Site AAA

(14)

Cell B

GFXBSC01

Site XXX

(46)

Cell A

0.0

0.0

7.0

8.0

8.0

24

0.0

0.0

7.0

8.0

8.0

24

0.0

0.0

7.0

8.0

8.0

24

Example 87. Report 139: Cells having unavailable radio time slots


NTC TAN 0935/2.3 en


122


12.2.3

Availability of SDCCH and TCH on BTS Level

To find about the availability of SDCCH and TCH on the BTS level, run the report Cell analyser (216). .

Whole

TCH

.

period

Busy hour

.

=======

=========

TCH === Available TCH ............... ............../a va_2a

7.00

7.00

Unavailable TCH ................ .........../uav_ 5

0.00

0.00

. TCH AVAILABILITY ............... .........../ava_ 1a

******

******

100.00 %

100.00 %

.

Whole

SDCCH

.

period

Busy hour

.

=======

=========

SDCCH ===== Available SDCCH ................ .........../ava_ 3a

4.00

4.00

Unavailable SDCCH .............. .........../uav_ 4

0.00

0.00

. SDCCH AVAILABILITY ................ ......../ava_4

******

******

100.00 %

100.00 %

Example 88. BTS level data on SDCCH and TCH availability in report 216, Cell analyser.

12.3 BSC Units The Availability per BSC unit (215) report shows for each unit of each BSC the total disconnection time and the total number of restarts over the given time period. Unit availability for BSCs from 19970201 to 19970202 Object: Unit name

BSC_XXXXX-88888 Dconn time

Dconn time dup

Unit restarts

Unit restarts dup

---------- ----------------- ----------------- -------------- ----------------BCSU-0

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

BCSU-1

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

BCSU-2

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

BCSU-3

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

BCSU-4

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

BCSU-5

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

BCSU-6

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

CLAB-0

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

CLAB-1

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

CLS-0

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

CLS-1

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

ET-32

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

ET-33

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

ET-34

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0


NTC TAN 0935/2.3 en


123


ET-35 ET-36

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

45 hr 32 m 49 s

0 hr

0 m

0 s

0

0

ET-37

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

ET-38

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

ET-39

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

ET-40

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

ET-41

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

ET-42

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

ET-43

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

ET-44

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

ET-45

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

ET-46

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

45 hr 32 m 49 s

0 hr

0 m

0 s

0

0

ET-47 ET-48 ET-49

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

ET-50

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

ET-51

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

MB-0

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

MB-1

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

MCMU-0

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

MCMU-1

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

OMU-0

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

SBUS-0

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

SBUS-1

0 hr

0 m

0 s

0 hr

0 m

0 s

0

0

Example 89. Report 215: Availability per BSC unit


NTC TAN 0935/2.3 en


124

Interference

13

INTERFERENCE

13.1 Uplink Interference The uplink interference is reported by the BSCs as counters showing the average number of time slots in bands 1 to 5. Usually band 1 is defined (boundaries are defined in cell parameters) so that the time slots located outside it can be said to have interference.

13.1.1

Uplink Interference on Area Level

For boundary settings and daily averages for each band, use the report Performance statistics (benchmark) (200). =============================================================================== =

UPLINK INTERFERENCE STATISITICS

=============================================================================== The UL interference is measured based on the levels in idle FTCH. The measurement reports the average number of idle FTCH in different bands which are defined by boundaries. Boundaries are set as BTS parameters. ------------------ boundary B00 (value fixed: -110dBm) band 1 -------------- ---- boundary B01 (value eg.:

-105dBm, critical)

band 2 -------------- ---- boundary B02 (value e.g.:

-100dBm)

band 3 -------------- ---- boundary B03 (value e.g.:

-95dBm)

band 4 ------------------ boundary B04 (value e.g.: -90dBm) band 5 ------------------ boundary B05 (value fixed: -47dBm) The boundaries used in the selected BTS area are reported below:

THRS BOUNDARY1 (BO0) - fixed

BTS COUNT

----------------------------------------

---------

-110.0 dBm

39

THRS BOUNDARY1 (BO1)

BTS COUNT

----------------------------------------

---------

-105.0 dBm

39


BTS COUNT

----------------------------------------

---------

-100.0 dBm

39


BTS COUNT

----------------------------------------

---------

-95.0 dBm

39


BTS COUNT

----------------------------------------

---------

-90.0 dBm


NTC TAN 0935/2.3 en

39


125

Interference

THRS BOUNDARY5 (BO5) - fixed

BTS COUNT

----------------------------------------

---------

-47.0 dBm

39

The percentual distribution of idle FTCH in the selected area:

idle FTCH idle FTCH idle FTCH idle FTCH idle FTCH in band 1 in band 2 in band 3 in band 4 in band 5 Day MMDD

(%)

(%)

(%)

(%)

(%)

--- ---- --------- --------- --------- --------- --------tue 1124

97.1

1.9

0.7

0.2

0.1

mon 1123

97.0

2.0

0.7

0.2

0.1

sun 1122

97.8

1.5

0.5

0.2

0.1

sat 1121

97.6

1.5

0.5

0.2

0.1

fri 1120

97.4

1.8

0.5

0.2

0.1

Note: For a cell level list run report 190.

Example 90. Area level data on uplink interference in report 200, Performance statistics (benchmark).

13.1.2

Uplink Interference on BTS Hit List

The report Cells having UL interference, 24-hour/10-day breakdowns (190) lists the cells having uplink interference and shows the BTS breakdown table for the time-out of band 1 per cell and the hour for cells having hours with interference. For this report it is important that you define the boundary for band 1 correctly. You can see the boundaries in the breakdown matrices produced for each cell. The report works especially well when there are not yet many TRXs in the BTSs. = =

CELLS HAVING UL INTERFERENCE, 24-HOUR/10-DAY BREAKDOWNS

= =

Network:

=

Area:

BSC - BSC_ZZZZZ

=

Period:

averaged from 19970201 to 19970202

= =

PLMN

breakdown for 10 last days Interference limit:

3 %

= =============================================================================== FIRST REPORT The first report shows the cells with interference, averaged across BTS, and hour for the period given. The last column shows as a percentage the time that the cell has been out of band 1 (class 0). For example, 3 % or more on the timeout of band 1 is considered interference. Instead of using the default 3 %, the users can define their own limit. Note that boundary 1 setting will effect the result. FTCH 'n' indicates the average number of idle full TCH in band 'n' (1-5). If there is no interference (uplink), all idle TCHs should be in band 1. The bands are defined in cell parameters by setting the boundaries in interference averaging parameter set.


NTC TAN 0935/2.3 en


126

Interference

------------------ boundary 0 (value fixed: -110dBm) band 1 (FTCH 1) -------------- ---- boundary 1 (value eg.:

-105dBm, critical for the report)

band 2 (FTCH 2) -------------- ---- boundary 2 (value e.g.:

-100dBm)

band 3 (FTCH 3) -------------- ---- boundary 3 (value e.g.:

-95dBm)

band 4 (FTCH 4) ------------------ boundary 4 (value e.g.: -90dBm) band 5 (FTCH 5) ------------------ boundary 5 (value fixed: -47dBm) SECOND REPORT The second report shows the breakdown of interference, over 24 hours of each of the last ten days. The values per hour mean the percentage of time slots out of band 1. The higher the value, the worse the interference. A blank value stands for missing PM data; it does not mean that there is not any interference. Used counter formula: itf_1 Measurement used: p_nbsc_res_avail Instructions: - Check the 10-day/24-hour breakdown charts to find out what the pattern is. - If you suspect that the interference is from the BS itself (constant 100% interference e.g. in all sectors) you may set the power to minimum for a while (this means that calls cannot be made!) and check from the BSC MML with ZERO command if the interference level has gone down in idle time slots. Then put the power back to the initial level. - After you have found the cells with obvious UL interference, you may use the Undefined Adjacent Cell measurement (possibly with the idle state BA list to define what are the strongest frequencies in the band which are not adjacent cells. - It is also a good idea to check if the cell is not reported by report 062, which could mean that there is interference coming from one's own adjacent cell. - For more details on the cell run report 216, Cell analyser. - You may also run the report 216 to get more details about the cell. Note: Since T10/S6 Power Control measurement has had a TRX level counter for the average interference band. Use report 196 to see the interference on TRX level. Note: Running this report is heavy and takes time. Patience please. =============================================================================== Cells with UL interference averaged from 19970201 to 19970202 AVE

AVE

AVE

AVE

AVE

PERIOD IDLE

IDLE

IDLE

IDLE

IDLE

TIME

START

FTCH

FTCH

FTCH

FTCH

FTCH

OUT

BSC Name

BCF Name

TIME

BAND

BAND

BAND

BAND

BAND

BAND

(BTS ID)

BTS Name

(hh)

1

2

3

4

5

1 (%)

------------- ---------------- ------ ----- ----- ----- ----- ----- ----BSC_ZZZZZ

PPWMM

69

073


NTC TAN 0935/2.3 en

03

6.7

0.0

0.0

0.3

0.1

5

07

6.7

0.0

0.0

0.1

0.1

3

08

6.5

0.1

0.2

0.1

0.1

7

09

5.5

0.6

0.4

0.2

0.2

19

10

5.7

0.1

0.2

0.5

0.4

17

11

6.7

0.0

0.1

0.1

0.1

4


127

Interference

BSC_ZZZZZ

GMCWW

70

081

BSC_ZZZZZ

GMCQQ

71

081

12

6.1

0.3

0.2

0.3

0.1

11

13

5.7

0.2

0.2

0.5

0.2

16

14

5.8

0.2

0.1

0.2

0.4

15

15

5.4

0.2

0.3

0.6

0.2

21

16

5.6

0.1

0.3

0.4

0.3

15

17

5.8

0.1

0.1

0.5

0.3

14

18

6.2

0.0

0.1

0.2

0.3

9

19

6.6

0.0

0.0

0.2

0.1

5

20

6.6

0.1

0.2

0.1

0.0

5

18

13.5

0.1

0.2

0.2

0.1

4

00

7.7

5.8

0.0

0.0

0.0

43

01

7.8

5.9

0.0

0.0

0.0

43

02

7.9

5.9

0.0

0.0

0.0

43

03

7.9

5.9

0.0

0.0

0.0

43

04

8.0

6.0

0.0

0.0

0.0

43

05

8.0

6.0

0.0

0.0

0.0

43

06

8.0

6.0

0.0

0.0

0.0

43

07

8.0

6.0

0.0

0.0

0.0

43

08

7.9

5.9

0.0

0.0

0.0

43

UL interference per hour on 19970202 and 10 days back

BSC_ZZZZZ:073:PPWWW boundaries: -110,-108,-105,-10 0,-90,-47 (dBm)

Hr

thu

fri

sat

sun

mon

tue

wed

thu

fri

sat

sun

23

24

25

26

27

28

29

30

31

01

02

JAN

JAN

JAN

JAN

JAN

JAN

JAN

JAN

JAN

FEB

FEB

-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---00

0

0

0

0

0

0

0

0

0

6

11

01

0

0

0

0

0

0

0

0

0

9

50

02

0

0

0

0

0

0

0

0

0

25

15

03

0

0

0

0

0

0

0

0

0

11

28

04

0

0

0

0

0

0

0

0

1

0

36

05

0

0

0

0

0

0

3

0

3

0

20

06

0

0

0

0

4

0

0

4

0

0

9

07

0

0

0

0

14

0

1

3

0

0

14

08

0

0

0

0

0

0

0

28

0

0

11

09

0

0

0

0

1

0

6

55

8

3

40

10

0

0

0

0

6

3

21

1

1

0

1

11

0

0

1

0

2

0

4

6

0

0

12

0

0

0

0

0

0

0

2

0

0

13

0

0

0

0

3

0

0

2

0

0

0

14

0

0

1

0

0

1

0

1

0

0

0

15

0

0

2

0

2

0

0

10

0

0

0

16

0

0

0

0

3

2

0

0

1

0

0

17

0

0

0

0

1

3

4

4

6

0

0

18

0

0

0

0

1

7

1

0

1

0

0

19

0

0

0

0

0

0

0

1

1

0

0

20

0

0

0

1

0

0

0

0

1

0

0

21

0

0

0

0

0

0

3

0

0

0

0

22

0

0

0

0

0

0

1

0

25

0

23

0

0

0

0

0

0

0

5

0

6 23

UL interference per hour on 19970202 and 10 days back

BSC_ZZZZZ:081:GMCWW boundaries: -110,-108,-105,-10 0,-90,-47 (dBm) thu

fri


NTC TAN 0935/2.3 en

sat

sun

mon

tue

wed

thu

fri

sat

sun


128

Interference

Hr

23

24

25

26

27

28

29

30

31

01

02

JAN

JAN

JAN

JAN

JAN

JAN

JAN

JAN

JAN

FEB

FEB

-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---00

0

0

0

0

1

1

0

0

0

0

0

01

0

0

0

0

0

0

0

0

0

0

0

02

0

0

0

0

0

0

0

0

0

0

0

03

0

0

0

0

0

0

0

0

0

0

0

04

0

0

0

0

0

0

0

0

0

0

0

05

0

0

0

0

0

0

0

0

0

0

0

06

0

0

0

0

0

0

0

0

0

0

0

07

0

0

0

0

0

0

0

0

0

0

0

08

0

0

0

0

0

1

1

0

0

0

1

09

0

0

0

0

1

1

1

2

1

1

1

10

1

0

0

0

1

1

2

2

1

2

1

11

0

0

0

0

0

2

1

2

2

1

12

0

0

0

1

1

2

2

1

1

13

0

0

0

0

1

1

1

1

2

2

4

14

1

0

0

0

1

1

2

2

2

2

1

15

0

0

1

0

1

1

3

2

1

2

1

16

1

0

0

0

1

1

1

2

2

2

1

17

0

0

0

0

1

2

3

3

1

2

1

18

0

0

0

0

1

0

2

1

3

6

1

19

0

0

0

1

1

1

1

1

2

1

1

20

0

0

0

1

0

1

2

1

1

1

1

21

0

0

0

1

1

2

3

1

1

2

1

22

0

1

0

1

2

1

3

1

2

3

1

23

0

1

0

2

1

2

1

0

1

0

Example 91. Report 190: Cells having UL interference, 24-hour/10-day breakdowns

In this example the report shows two cells with interference. One of them has not suffered from any interference until during the last few days, whereas the other one has suffered from it all the time. There are some gaps in the matrices which indicate missing data. This means that the data transfer from a BSC to the NMS/2000 database has not been 100 per cent reliable or that measurements are not set to run every hour.

13.1.3

UL Interference on BTS Level

For averages, boundaries and hourly breakdown, run the report Cell analyser (216). = = =

Cell UL interference ABC_BSC_1

bts id:55

name:ITAG1

from 19970829 to 19970829

=============================================================================== .

Whole

TCH

.

period

busy hour

.

average

average

.

=======

=========

UL interference (time out band 1) ........../itf _1


NTC TAN 0935/2.3 en


0.00 %

0.00 %

129

Interference

.

time in band 1 ( -110dBm <= B1 <=

-108dBm )

100.00 %

100.00 %

.

time in band 2 ( -108dBm <

B2 <=

-105dBm )

0.00 %

0.00 %

.


B3 <=

-100dBm )

0.00 %

0.00 %

.


B4 <=

-90dBm )

0.00 %

0.00 %

.

time in band 5 (

B5 <=

-47dBm )

0.00 %

0.00 %

-90dBm <

TRX level interference (from Power Control measurment) ====================== Avg

Intf

TRX id

TRX

band

freq (itf_4)

--- ----- ------1

0

1.0

************************************************************************ Average band of TCH interference (itf_4) ABC_BSC_1

bts:55 ITAG1

bcf:336

************************************************************************ Reported as band number 1...5, 1 means lowest. Band boundaries are defined in cell parameters (Interference Averaging parameters).

thu Hr

fri

sat

sun

mon

tue

wed

thu

fri

sat

sun

07

08

09

10

11

12

13

14

15

16

17

MAY

MAY

MAY

MAY

MAY

MAY

MAY

MAY

MAY

MAY

MAY

-- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----00

1

1

1

1

1

1

1

1

1

1

1

01

1

1

1

1

1

1

1

1

1

1

1

02

1

1

1

1

1

1

1

1

1

1

1

03

1

1

1

1

1

1

1

1

1

1

1

04

1

1

1

1

1

1

1

1

1

1

1

05

1

1

1

1

1

1

1

1

1

1

1

06

1

1

1

1

1

1

1

1

1

1

1

07

1

1

1

1

1

1

1

1

1

1

1

08

1

1

1

1

1

1

1

1

1

1

1

09

1

1

1

1

1

1

1

1

1

1

1

10

1

1

1

1

1

1

1

1

1

1

1

11

1

1

1

1

1

1

1

1

1

1

1

12

1

1

1

1

1

1

1

1

1

1

1

13

1

1

1

1

1

1

1

1

1

1

1

14

1

1

1

1

1

1

1

1

1

1

1

15

1

1

1

1

1

1

1

1

1

1

1

16

1

1

1

1

1

1

1

1

1

1

1

17

1

1

1

1

1

1

1

1

1

1

1

18

1

1

1

1

1

1

1

1

1

1

1

19

1

1

1

1

1

1

1

1

1

1

1

20

1

1

1

1

1

1

1

1

1

1

1

21

1

1

1

1

1

1

1

1

1

1

1

22

1

1

1

1

1

1

1

1

1

1

1

23

1

1

1

1

1

1

1

1

1

1

1

Example 92. BTS level data on UL interference in report 216, Cell analyser.

13.2 Interference from the Same or Adjacent Frequencies In urban areas the tight frequency reuse and difficulty to estimate the propagation of the radio waves may cause unexpected interference of the same or adjacent frequencies. Document number/Issue

NTC TAN 0935/2.3 en


130

Interference

To check a cell for the possible interference, use the Undefined Adjacent Cell measurement together with or without the Double BA List feature. If the Double BA List feature is available as an option in the BSC, it is possible to monitor the frequencies which are not adjacent cell frequencies. Proceed as follows: 1.

Create a BAL with the suspected frequencies and assign them to the cell.

2.

Activate the Undefined Adjacent Cell measurement in the BSC.

The BSC will now report all detected frequencies which were on the BAL and which are not the frequencies of the defined adjacent cells. If the Double BA List feature is not available, the Undefined Adjacent Cell measurements give frequencies which are the same as in the neighbouring list only that their BSIC differs from that of the adjacent cell definition. Thus, you can find out the interfering frequencies only if they are the same as in the neighbouring list. To see the results, run the report: •

Defined, undefined and used adjacencies of a cell (072) which also shows for the selected BTS the frequencies reported by the Undefined Adjacent Cell measurement.

•

Undefined adjacent cells (073) for the frequencies detected as undefined for all cells. Note that this report may be heavy to run.

•

Cells having undefined adjacent measurement results (125) to find out which cells have records in the Undefined Adjacent Cell measurement table.


NTC TAN 0935/2.3 en


131

Intelligent Underlay-Overlay

14

INTELLIGENT UNDERLAY-OVERLAY BSS Network Doctor provides two reports for monitoring intelligent underlayoverlay (IUO) occurrences on area and BTS level.

14.1 Intelligent Underlay-Overlay on Area Level For averages on the area level, run the report Cells by average traffic absorption to super TRXs (401). = =

CELLS BY AVERAGE TRAFFIC ABSORPTION TO SUPER TRXs

= =

Network:

PLMN

=

Area:

MR - all MRs

=

Period:

from 19970115 to 19970430

=

Sorted by:

Traffic absorption to super TRXs

= =============================================================================== Measurement used: p_nbsc_underlay Input parameters: maintenence region, BTS group, time period, sorting Running this report takes a while. Patience please. =============================================================================== IUO: Cells by Traffic Absorbtion to Super TRXs. Average. between 19970115 and 19970430 sorted by Traffic absorption to super TRXs Traffic BSC

BTS NAME

(BTS id)

BCF NAME

Traffic Absorbtion on

Usage of

on super

on all

super TRXs super TRXs

TRXs

TRXs

(%)

(%)

/trf_9a /trf_10a

/trf_8

/trf_29

------------- ----------------- -------- -------- -------------- ---------BSC_SSSSS

ROCQQ

(127)

ROC

0.02

0.02

100.00

.37

Example 93. Report 401: Cells by average traffic absorption to super TRXs

For busy hour traffic on the area level, run the report Cells by busy hour traffic absorption to super TRXs (402). =

CELLS BY BUSY HOUR TRAFFIC ABSORPTION TO SUPER TRXs

= =

Network:

PLMN

=

Area:

BSC - BSC_SSSSS

=

Period:

from 19970115 to 19970430

=

Sorted by:

Traffic absorption to super TRXs

= =============================================================================== The absolute busy hour by traffic is defined for each cell and for this hour the absorption of the traffic to super TRXs is calculated.


NTC TAN 0935/2.3 en


132


Measurement used: p_nbsc_underlay Note: Running this report takes some minutes. Patience please. =============================================================================== IUO: Cells by Traffic Absorbtion to Super TRXs. Busy Hour. between

19960927 and

19960927

sorted by Usage of super TRXs Peak hour

Traffic

Traffic Absorb.on

Usage of

on all on super super TRX super TRX

BSC

BTS NAME

YYYY

TRX

TRX

(%)

(%)

(BTS id)

BCF NAME

MMDDHH /trf_10a

/trf_9a

/trf_8

/trf_29

------------- ----------------- ------ -------- -------- --------- --------BSC33

8032

1996

(86)

Site aaa

092714

BSC33

25004

1996

(108)

Site bb

092715

BSC33

25109

1996

(109)

Site ccc

092715

4.16

3.38

81.32

29.70

2.54

1.89

74.45

19.14

2.20

1.43

65.15

15.19

Example 94. Report 402: Cells by busy hour traffic absorption to super TRXs

14.2 Intelligent Underlay-Overlay on BTS Level For IUO counters on the BTS level, run the report IUO counters of a cell (400). = =

IUO COUNTERS OF A CELL

= =

Network:

PLMN

=

BSC:

BSC12

=

BCF:

(19)

XXXXXXXXXXXXX

=

BTS:

(19)

XXXXXXXXXXXXX1

=

Period:

from 19971119 to 19971119

= =============================================================================== This report shows counter information about IUO for one cell. Measurement used: p_nbsc_traffic, p_nbsc_underlay, p_nbsc_rx_qual, p_nbsc_ho, p_nbsc_res_avail =============================================================================== =

IUO Configuration. BTS

=

BSC12

bts id:19

name:XXXXXXXXXXX XX1

=============================================================================== HOC Super reuse estimation method

(METH): Not used

Interfering cell averaging window size (SIZE): 10 Interfering cell number of zero result (ZERO): 2 All interfering cells averaged Super reuse good C/I threshold threshold px


NTC TAN 0935/2.3 en

(AVER): No (GCI): 17 dB (GPX): 8


133


threshold nx Super reuse bad

(GNX): 10

C/I threshold

(BCI): 10 dB

threshold px

(BPX): 2

threshold nx

(BNX): 6

Minimum bsic decode time

(TIM): 10 SACCH periods

Enable TCH assignment super IUO

(ETA): 0 SACCH periods

Min interval between IUO HO req

(MIR): 10

Min interval between unsucc IUO HO

(MIO): 20

=============================================================================== =

IUO Configuration. TRX

=

BSC12

bts id:19


=============================================================================== BSC:

OMC Name:

Description:

----

---------

----------

FRT

Frequency Type

Type of the radio frequency of the tranceiver.

LAC

LAC

Location Area Code of the interfering cell.

CI

CI

Cell Identification of the interfering cell.

L

Level Adjustment

Level adjustment of the interfering cell.

W

C/I Weight

C/I Weight of the interfering cell.

T

C/I Type

C/I Type of the interfering cell.

TRX : 1 FRT

: regular

LAC1 :

0

CI1 :

0

L1 :

0

W1 :

0

T1 :

0

LAC2 :

0

CI2 :

0

L2 :

0

W2 :

0

T2 :

0

LAC3 :

0

CI3 :

0

L3 :

0

W3 :

0

T3 :

0

LAC4 :

0

CI4 :

0

L4 :

0

W4 :

0

T4 :

0

LAC5 :

0

CI5 :

0

L5 :

0

W5 :

0

T5 :

0

LAC6 :

0

CI6 :

0

L6 :

0

W6 :

0

T6 :

0

=============================================================================== =

IUO performance. Regular and Super layers.

=

BSC12

=

bts id:19


from 19971119 to 19971119

=============================================================================== Cell layer statistics: .

Average

Busy hour

.

=======

=========

Cell traffic .............. ...........(erl )

6.31

7.16

/trf_9

Super TRX traffic .............. ......(erl)

3.29

3.61

Traffic absorption on super ............(% )

52.10

50.43

/trf_10

TCH seizure length on regular........ .(sec)

7.45

7.72

/trf_15

TCH seizure length on super.......... .(sec)

21.04

21.14

/trf_14

/trf_8

.

. TCH raw blocking on regular ............(% )

0.00

0.00

/blck_7

TCH raw blocking on super .............. (%)

7.48

10.09

/blck_6

. HO att from regular to super.

Total:

2340

HO fail from regular to super ..........(%)

1.67

/ho_2

--

/hfr_13

--

/hfr_14

.

return......... ...

.

MS lost.......... .

5.13 %

--

/hfr_15

.

other.......... ...

20.51 %

--

/hfr_16

HO att from super to regular.


NTC TAN 0935/2.3 en

Total:

74.36 %

--

863


/ho_3

134


HO fail from super to regular ..........(%)

2.32

--

/hfr_12

.

return......... ...

75.00 %

--

/hfr_17

.

MS lost.......... .

15.00 %

--

/hfr_18

.

other.......... ...

10.00 %

--

/hfr_19

Return from super to regular ...........(%)

39.65

40.83

.

DL quality....... .

25.81 %

19.28 % /ho_4

/ho_1

.

DL interference.. .

56.98 %

64.66 % /ho_5

.

UL interference.. .

11.40 %

10.44 % /ho_6

.

bad C/I...........

5.81 %

5.62 % /ho_7

=============================================================================== =

IUO performance. TRXs.

=

BSC12

=

bts id:19


from 19971119 to 19971119

=============================================================================== Average TRX statistics: Ave TCH Ave traf TRX

TRX Cell

(Erl)

id Freq Layer

seiz

UL

UL

DL

length interf

Qual5

Qual5

(sec)

(%)

(%)

(%)

/trf_16 /trf_17 /itf_3

/ulq_2

/dlq_2

--- ---- ------- ------- ------- ------ ------- ------1

49 regular

2.5

7

71 regular

0.6

5

78 super

3.3

7.3

17.1

89.44

87.31

7.9

12.0

93.55

82.23

21.0

26.1

98.53

98.45

Busy Hour TRX statistics (BH = 1997111910 ): Ave TCH Ave traf TRX

UL

UL

DL

length interf

Qual5

Qual5

(%)

(%)

(%)

/trf_16 /trf_17 /itf_3

/ulq_2

/dlq_2

TRX Cell

(Erl)

id Freq Layer

seiz (sec)

--- ---- ------- ------- ------- ------ ------- ------1

49 regular

2.9

7

71 regular

0.7

5

78 super

3.6

7.8

18.1

89.78

88.69

7.2

13.7

92.73

85.45

21.1

27.0

98.29

98.50

=============================================================================== =

Traffic / Underlay Overlay

=

BSC12

=

bts id:19


from 19971119 to 19971119

=============================================================================== TCH req UO

1090

TCH requests for underlay-overla y procedure.

TCH seiz UO

1091

TCH seizures for underlay-overla y procedure.

TCH rej UO

1092

TCH seizures for underlay-overla y procedure rejected

.

due to lack of resources. This is between the regular

.

and super layers to both directions.

DD HH

TCH

TCH

TCH

req

seiz

rej

UO

UO

UO

-- -- ----- ----- ----19 09

575

575

0

10

932

863

69

16

988

909

79


NTC TAN 0935/2.3 en


135


17

791

757

34

=============================================================================== =

Handover / Underlay Overlay

=

BSC12

=

bts id:19


from 19971119 to 19971119

=============================================================================== Cause bad CI

4089

HO attempts due to bad C/I ratio on super reuse freq.

Cause good CI

4090

HO attempts due to good C/I ratio on super reuse freq.

HO

HO

cause

cause

DD HH bad CI good CI -- -- ------ ------19 09

11

399

10

14

663

16

19

714

17

8

559

=============================================================================== =

Underlay Overlay (part 1)

=

BSC12

=

bts id:19


from 19971119 to 19971119

=============================================================================== TCH req

52003

Number of TCH requests (call or HO on regular cell,

52004

Number of successful TCH seizures

TCH rej

52005

TCH seizures rejected due to lack of resources

TCH traf

52028/52029 Average nbr of busy TCH (=traffic)

TCH fail

52006

TCH failures during call or HO

TCH rf

52007

TCH failures due to radio failures

.

HO in super-reuse)

TCH seiz

HO inhib. itf. too high .

52040

Number of times when HO to super-reuse candidate is

.

inhibited because the estimated C/I ratio is too low.

.

The sampling period is 0,48s.

HO inhib. qual. too low .

52041

Number of times when HO to super-reuse candidate is

.

inhibited because of bad quality experience on

.

super-reuse frequency. The sampling period is 0,48s.

FTCH

itf b1-b5

.

Counters 52008/52009,520 10/52011,52012/ 52013,52014/5201 5,52016/52017.

.

Average nbr of idle FTCH in interference band 1 to band 5 (uplink)

.

Note that when there are no measurement results BSC records the time

.

to band 5 to be on the safe side.

Cell id c1-c10 .

Counters 52030,52032,520 34,52036,52038, 52064,52066,5206 8,52070,52072.

.

Cell id of interfering cell 1 to 5

Lac c1-c10 .

Counters 52030,52032,520 34,52036,52038, 52064,52066,5206 8,52070,52072.

.

Cell LAC of interfering cell 1 to 5

HO inhib. itf high c1-c10 .

Counters 52031,52033,520 35,52037,52039, 52065,52067,5206 9,52071,52073.

.

Number of times when HO to super-reuse candidate is inhibited

.

because the directly measured C/I ratio is too low

.

and the source of interference is cell cX. The sampling period is 0,48 s.


NTC TAN 0935/2.3 en


136


TCH

TCH

*****

***** HO

HO HO

inhib.

req

fail

inhib inhib FTCH

seiz

rf

itf.

rej TRX DD HH traf

qual. itf

too

too

high

low

itf Cell i

Lac high

****** ****** ****** ***** b1-b5 c1-c10 c1-c10 c1-c10

--- -- -- ------ ----- ----- ----- ------ ------ ------ -----1 19 09

10

16

949

10

938

6

3.6

0

0

0

0.5

0

0

0

0

0.1

0

0

0

1.8

0.0

0

0

0

0.0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

2.6

0

0

0

1347

11

1315

3

0

0

0

0

0.5

0

0

0

0

0.1

0

0

0

2.9

0.0

0

0

0

0.0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

2.6

0

0

0

1419

10

1399

12

0

0

0.5

0

0

0

0

0.1

0

0

0

2.8

0.0

0

0

0

0.0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

=============================================================================== =

Underlay Overlay (part 2).

=

HO counters for super TRXs.

=

BSC12

=

bts id:19


from 19971119 to 19971119

=============================================================================== NOTE: Counters are shown only for super TRXs. HO R->S

Handovers from reqular frequency to super

************** .

att

52048

HO attempts.

.

suc

52049

Successfull HO attempts.

.

rej

52050

Rejected HO attempts due to lack of resources.

HO fail R->S

Failures in handovers from reqular frequency to super

******************* .

return

52052

Returns to old channel.

. MS lost

52053

MS is lost.

.

52051

Other failures.

other


NTC TAN 0935/2.3 en


137


HO S->R

Handovers from super to reqular frequencies

************ .

att

52042

HO attempts.

.

suc

52043


.

rej

52044


HO fail S->R

Failures in handovers from super to reqular frequencies

***************** .

return

52046


. MS lost

52047

MS is lost.

.

52045

Other failures.

other

HO att S->R

Handover attempts from this super-reuse TRX.

********************** . DL Qual

52060

Due to downlink quality

.

DL itf

52061

Due to downlink interference

.

UL itf

52062

Due to downlink interference

.

bad CI

52063

Due to bad C/I ratio

HO in super f.gr.

Handovers in super-reuse frequency group

***************** .

att

52054

HO attempts.

.

suc

52055


.

rej

52056


HO fail in super f.gr. Failures in handovers in super-reuse frequency group ********************** .

return

52058


. MS lost

52059

MS is lost.

.

52057

Other failures.

other

HO

HO fail

in

in

HO

HO fail HO

HO fail HO att

R->S

R->S

S->R

S->R

S->R

f.gr. f.gr.

*****

*****

*****

*****

*****

***** *****

att

return

att

return

DL Qual att

succ

MS lost succ

MS lost DL itf

succ

MS lost

rej

other

other

rej

other

rej

super super

UL itf

TRX DD HH

return

bad CI

--- -- -- ------- ------- ------ ------- ------- ----- ------5 19 09

405

0

166

2

31

15

0

401

4

163

0

118

15

0

0

0

0

1

16

0

0

11 10

660

2

243

5

48

23

0

578

7

236

2

161

21

0

67

6

0

0

26

2

0

14

Example 95. Report 400: IUO counters of a cell

For each cell of the selected BTS area, the KPI statistics for IUO cells (403) report shows the following Key Performance Indicators:


NTC TAN 0935/2.3 en


138


•

Total traffic of all and super TRXs

•

Absorption of traffic to super TRXs

•

TCH drop ratio

•

Handover failure ratio

•

TCH raw blocking

•

Average TCH seizure length on regular and super TRX

•

TCH blocking on regular and super TRX

•

Ratio of downlink quality caused returns to all returns from super TRX

•

Ratio of downlink returns caused by interference to all returns from super TRX

•

Ratio of uplink returns caused by interference to all super TRXs

The report is sorted by traffic absorption to super TRXs. Note that this report is not of standard width.

                       

    

                                      

       

       

       

       

       

        

                          

Figure 5. Report 403: KPI statistics for IUO cells

The IUO measurement data per BTS (404) report shows per BTS the date of the oldest and latest data record and the average duration of the measurement period.

BSC name

BCF name

BTS name

Oldest

Avg

BTS Newest

Period

id data

(min) Layers

-------------- -------------- -------------- ---- ---------- ------ ---------BSC555

WHOU1

WHOU1

1 21.11.98

60 REG, SUP

26.11.98

Example 96. Report 404: IUO measurement data per BTS

The Adjacent cells with the same or adjacent frequency, IUO super TRX excluded (405) report displays all adjacencies where a cell and its adjacent cell have the same frequency or adjacent frequency on a regular TRX. This report is basically similar to report 062 but it is modified for IUO cells and excludes super TRXs in the check. Adjacent cells with same or adjacent frequency check in PLMN network


NTC TAN 0935/2.3 en


139


Source

Source

Target

Target

******

******

******

******

(S)TRX_id(use)

BSC

(S)TRX_id(use)

BSC

(S)BTS_name

BTS id (CI,LAC)

(S)BTS_name

BTS id (CI,LAC)

(S)BCF

freq, NCC, BCC

(S)BCF_name

freq, NCC, BCC

-------------------- ---------------- -------------------- ---------------(U)1(BCCH)

BSC12

(U)3(BCCH)

BSC12

(U)XXXXXXXXXX1

1 (1016,4270)

(U)YYYYYYYYYYY YY2

23 (1129,4270)

(U)XXXXXXXXXX1

56,5,4

(U)YYYYYYYYYYYYY

56,5,6

(U)6(TCH)

BSC12

(U)9(TCH)

BSC12

(U)YYYYYYYYYYY 1

4 (1034,4270)

(U)YYYYYYYYYYY2

38 (1386,4270)

(U)YYYYYYYYYYY1

83,5,3

(U)YYYYYYYYYYY1

83,6,5

Example 97. Report 405: Adjacent cells with the same or adjacent frequency, IUO super TRX excluded

The C/I statistics (407) report is based on the C/I Ratio measurement, which is an optional BSC feature. It collects data on every call ongoing in the test cell and its interfering cells. The measurement can be activated only for one BTS in one BSC. Interfering cells can consist of either all adjacent cells or 6 given cells. When a MS is in the test cell, the DL C/I ratio is the ratio of DL signal level of the test cell to that of each interfering cell. When the MS is in the interfering cell, the DL C/I ratio is the ratio of DL signal level of the interfering cell to t hat of the test cell. C/I Statistics Test Cell

BSC=BSC2UPS1, BCF=1UPS002, BTS=1UPS2005, BTS id=5 LAC=2, CI=20005 from 19980622 to 19980622 Test C/I Intf C/I in band

Interfering Cell Upp

in band

TCH

(%)

hold

Sig

BSIC (%)

lev

deco ******** ******** time

**************

Low

BSC

Lmts Lmts adjt time DL

DL

(sec)

BCF

**** **** **** **** UL

UL

******

BTS (BTSid)

Min

Min

Min

Min

Estim

Estim

Test

(LAC,CI)

Max

Max

Max

Max

Worst

Intf

---------------- ---- ---- ---- ---- -------- -------- -------BSC2UPS1

0

10

0

0

24.3

13.6

4390

3UPS001

0

10

0

0

27.2

4.3

2295

3UPS2001 (1)

0.0

0.0

(2,20001)

0.0

BSC2UPS1

0

10

0

0

0.6

0.0

4390

3UPS001

0

10

0

0

0

2.6

0.0

3UPS2002 (2)

0.0

0.0

(2,20002)

0.0

Example 98. Report 407: C/I statistics


NTC TAN 0935/2.3 en


140

Network Configuration

15

NETWORK CONFIGURATION

15.1 Network Configuration Summary To obtain an overall picture of the network under the NMS/2000 run the report Network configuration summary (090). To see how the MRs are used, run the report Network configuration summary (090). = =

NETWORK CONFIGURATION SUMMARY

= =

Network:

PLMN

= =============================================================================== This report shows - NSS network entity sums for each MR and sum over the network - BSS network entity sums for each MR and sum over the network sorted by . the number of BTSs, for used and not used BCFs, BTSs, TRXs, CHNs .

BSC TOT: total nbr of BSCs

.

TC TOT : total nbr of transcoders

.

PCM TOT: total nbr of PCMs

.

BCF UNL: nbr of unlocked BCFs

. .

LCK: nbr of locked BCFs BTS

.

USD: nbr of used BTSs (BTS and BCF unlocked)

. .

NUS: nbr of non-used BTSs (BTS or BCF locked) TRX

.

USD: nbr of used TRXs (TRX, BTS and BCF unlocked)

.

NUS: nbr of non-used TRXs (TRX or BTS or BCF locked)

. . . .

CHN USD: nbr of used Channels (CHN, TRX, BTS and BCF unlocked) NUS: nbr of non-used Channels (CHN or TRX or BTS or BCF locked) ADJ TOT: total nbr of adjacencies

- BSS network entity sums for each MR and sum over network sorted by . the number of BTS, for locked and unlocked BCF, BTS, TRX, CHN . . . . . . . .

BCF UNL: nbr of unlocked BCFs LCK: nbr of locked BCFs BTS UNL: nbr of unlocked BTSs LCK: nbr of locked BTSs TRX UNL: nbr of unlocked TRXs LCK: nbr of locked TRXs CHN UNL: nbr of unlocked Channels of TRX (includes signalling chns) LCK: nbr of locked Channels

- Averages of entities per higher object (used CHN,TRX,BTS counts applied) - Statistics on used channel types NOTE: Running this report takes a while. Patience please.


NTC TAN 0935/2.3 en


141


------------------------------------------------------------------------------OMC, NSS Network Entity Summaries per Maintenance Region (Only objects that exist in the network are counted) ------------------------------------------------------------------------------OMC Maint.Region

OMC

OMC

FE

WS

HLR

MSC

tot

tot

tot

tot

tot

------------- ---- ---- ---- ---- ---non assign Global Scope

1 1

4

1

1

NonIntegrNW ---sum

---- ----

1

1

2

------------------------------------------------------------------------------BSS Network Entity Summaries per Maintenance Region ------------------------------------------------------------------------------ADJ Maint.Region

TC BSC

PCM

BCF

BTS

tot tot

tot

usd nus

usd

TRX nus

usd

CHN nus

usd

tot nus

in nw

------------- ---- --- ---- ---- --- ----- ---- ----- ---- ------ ----- -----NonIntegrNW

1

Global Scope

6

125

145

10

7

non assign

1

1

8

317

3

455

3

3640

24

3500

21

1

22

1

176

8

191

---- --- ---- ---- --- ----- ---- ----- ---- ------ ----- -----sum

6

135

152

1

338

5

477

5

3816

40

3691

usd = used (the object and all objects above are unlocked) nus = not used (the object or any object(s) above is locked) ------------------------------------------------------------------------------BSS Network Entity Summaries per Maintenance Region, Directly Locked and Unlocked BCF, BTS, TRX, CHN counts ------------------------------------------------------------------------------BCF Maint. Region

unl

BTS lck

unl

TRX lck

unl

CHN lck

unl

lck

------------- ----- ---- ----- ---- ----- ---- ------ ---non assign Global Scope

7

1

145

21

1

23

184

317

3

458

3664

1

1

8

NonIntegrNW

----- ---- ----- ---- ----- ---- ------ ---sum

152

1

338

5

482

3856

Note: These counts do not take into consid eration the state of the above objects. ------------------------------------------------------------------------------Transmission Element Summaries per Maintenance Region -------------------------------------------------------------------------------

Maint. Region

DMR

DN2

TRU

tot

tot

tot

------------- ---- ---- ---non assign


NTC TAN 0935/2.3 en


142


NonIntegrNW Global Scope

5

4

10

---- ---- ---sum

5

4

20

------------------------------------------------------------------------------BSS Network Entity Averages per Maintenance Region ------------------------------------------------------------------------------avg

avg

avg

avg

avg

avg

avg

avg

avg

PCM

TC

BCF

BTS

TRX

BTS

TRX

TRX

ADJ

per

per

per

per

per

per

per

per

per

Maint. Region BSC

BSC

BSC

BSC

BSC

BCF

BCF

BTS

BTS

------------- ------ ----- ------ ------ ------ ----- ------ ---- -------non assign

2.8

NonIntegrNW

--

Global Scope

20.8

24.2

53.3

76.3

2.2

2.9 -3.2

1.0

8.7

1.0 1.4

10.9

Note: Only those objects are counted which are in use. ------------------------------------------------------------------------------Channel statistics for channels which are in use in the entire network, i.e. which are unlocked and the above TRX, BTS and BCF are unlocked. ------------------------------------------------------------------------------Channel

Channel

type

count

-------- ------MBCCH

135

MBCCHC

203

SDCCH TCHF

137 3341

Example 99. Report 090: Network configuration summary

15.2 BSC Option Statistics The BSC option statistics (089) report shows the optional features that are used in the BSCs of the selected BTS area. = =

BSC OPTION STATISTICS

= =

Network:

PLMN

=

Area:

All BTSs selected

=

Sort by:

BSC option, BSC name

= = =============================================================================== All the BSCs in the selected area are reported.

Note: Only options used in the BSC are listed. Info rmation is updated to NMS/2000 database only at upload. Later (at the earliest in T11) the data will be updated automatically. ===============================================================================


NTC TAN 0935/2.3 en


143


BSC Option used

BSC Name

----------------------------------------

--------------------

C2 Cell Reselection

NWX_BSC_1

NWX_BSC_2

NWX_BSC_3

Chained Cells

NWX_BSC_1

NWX_BSC_2

NWX_BSC_3

Directed Retry

NWX_BSC_1

NWX_BSC_2

NWX_BSC_3

Double BCCH Allocation List

NWX_BSC_1

NWX_BSC_2

NWX_BSC_3

FACCH Call Setup

NWX_BSC_1

NWX_BSC_2

NWX_BSC_3

Fast Moving MS Handling

NWX_BSC_1

NWX_BSC_2

NWX_BSC_3

HO Adjacent Cell Measurements

NWX_BSC_1

NWX_BSC_2

NWX_BSC_3

Intelligent Underlay Overlay

NWX_BSC_1

NWX_BSC_2

NWX_BSC_3

Optimization MS Power Level In HO

NWX_BSC_1

NWX_BSC_2

NWX_BSC_3

Remote Degradation of BTS Service

NWX_BSC_1

NWX_BSC_2

NWX_BSC_3

Remote Inter of BTS Ser and Ver Nbrs

NWX_BSC_1

NWX_BSC_2

NWX_BSC_3

Rnos Usage

NWX_BSC_1

NWX_BSC_2

NWX_BSC_3

Rx Qual Statistics

NWX_BSC_1

NWX_BSC_2

NWX_BSC_3

SDCCH Handover

NWX_BSC_1

NWX_BSC_2

NWX_BSC_3

Underlay-Overlay Statistics

NWX_BSC_1

NWX_BSC_2


NTC TAN 0935/2.3 en


144


NWX_BSC_3

Example 100. Report 089: BSC option statistics

15.3 Network Entities The Maintenance regions (091) report lists all Maintenance Regions in the network and the number of objects in them. ID Maintenance Region

Int id

OBJECTS

--- ---------------------- ------ ---------1

South

2

NonIntegrNW

East

3

11922

13765

15

Example 101. Report 091: Maintenance regions

The BSCs (092) report displays all BSCs in the network and the number of BTSs, LAPDs and PCMs under them. Only the BTSs and TRXs having an actual parameter set (i.e. those that exist in the network) are counted. BSCs which are assigned to a Maintenance Region: Count Maint. Region

Name

C_NBR

Count

Count

INT

of

of

of

ID

LAPD

PCM

BTS

Count of BSC TRX

SW

----------------- ------------- ----- ------- ------ ------ ------ ------ --CITY AA

ADBSC01

32318

6

147

23

45

91 S4

CITY AA

ADBSC02

37240

277

150

32

50

104 S4

CITY AA

ADBSC03

37243

276

158

28

48

104 S4

CITY AA

ADBSC05

37122

18107

154

23

45

92 S4

CITY AA

ADBSC06

38837

28152

89

21

37

76 S4

CITY AA

RRBSC01

37251

25026

72

14

24

58 S4

CITY AA

VABSC01

37312

25027

107

19

46

94 S4

CITY AA

VABSC02

38444

72026

139

25

59

114 S4

CITY BB

ALBSC01

37585

9370

115

19

48

94 S4

CITY BB

EWBSC01

38351

3091

148

23

42

102 S4

CITY BB

EWBSC02

37458

20838

104

21

38

76 S4

CITY BB

ADBSC04

37785

7371

160

25

51

101 S4

CITY BB

ADBSC07

53244

81487

104

21

39

87 S4

CITY BB

ADBSC08

53456

91880

113

27

52

92 S4

CITY BB

TRSC01

37447

32222

137

15

37

73 S4

CITY BB

TRSC02

53504

94897

68

11

27

53 S4

CITY BB

PCBSC02

53336

92148

68

12

39

55 S4

PCBSS01

PCBSC01

33026

934

113

16

42

73 S4

------ ------ ------ -----sum

2146

375

769

1539

Count

Count

Count

BSCs which are not assigned to any Maintenance Region: Count Maint. Region

Name

C_NBR

INT

of

of

of

ID

LAPD

PCM

BTS

of BSC TRX

SW

----------------- ------------- ----- ------- ------ ------ ------ ------ --Undefined

Foreign BSC

0

19232

0

0

86

98 S2

------ ------ ------ ------


NTC TAN 0935/2.3 en


145


sum

0

0

86

98

Example 102. Report 092: BSCs

The MSCs (093) report lists all MSCs in the network. ID

MSC Name

Int id

------ ----------------- -----33333

MSC_MMMMM

7

34624

MC9

10841

Example 103. Report 093: MSCs

The HLRs (094) report lists all HLRs in the network. ID

HLR Name

Int id

------ ----------------- -----30971

HLR-City A

7

Example 104. Report 094: HLRs

The Base station sites of a maintenance region (095) report lists all base station sites (BCF objects) of the selected maintenance region in alphabetical order. The host BSC is shown as well as the number of BTSs (sectors) in each base station. Note that the number of BTSs counts only those BTSs which exist in the network, not those which exist in the database only. Nbr BCF BCF name

id

of BTS Host BSC

in nw

------------------------------ --- --------------- -----A Site

5

BSC3

2

B site

128 BSC1

3

C Site

112 BSC2

1

Example 105. Report 095: Base station sites of a maintenance region

In the Location areas (096) report the identifiers of all Location Area Codes (LAC) used in the network are presented with the number of cells (BTS) under each LA. You may need this information when dimensioning the paging resources. Location Number Area

of

Code

BTSs

-------- -----1

108

2

103

3

153

4

53


NTC TAN 0935/2.3 en


146


Example 106. Report 096: Location areas

The PLMNs (097) report lists all PLMNs created in the NMS/2000 database and the number of objects in them. Note that normally there should be only one PLMN in the database. If there is more than one, the network name in the report headers may not appear correctly. Child

Child

PLMN object PLMN id PLMN name

object

Int id class

name

-------- --------------------- - -------- ---------- -------------------PLMN

PLMN

1 BSC

BSC1 BSC11

Maint.Reg. City A OMC

OMC

Example 107. Report 097: PLMNs

15.4 BSC and BCF Software Deployment To see the occurrences of different BSC software releases in a BTS area, run report 200 or 204. BCF Software package used (only default package is counted)

COUNT

----------------------------------------

----------

BTSSWB100

13

BTS_S301

39

Note: For full BCF software deployment list run report 099.

BSC software version used

COUNT

----------------------------------------

----------

S6

49

Note: For full BSC software deployment list run report 092.

Example 108. BCF and BSC software deployment in report 204, Network benchmark statistics.

15.5 BCF Harware Type Deployment To see the occurrences of different BCF hardware releases in a BTS area, run report 200 or 204. Amount of BCF HW Type

BCFs in use

------------------------------ ----------DE21/DF12 (Nokia 2nd gen.)

13

DE34/DF34 (Nokia Talk-family)

10


NTC TAN 0935/2.3 en


147


Example 109. Occurrences of different BCF hardware releases in a BTS area in report 204, Network benchmark statistics.

To see the deployment of different BCF harware types in a BTS area, run the report BCF software and harware type statistics (099). = =

BCF SOFTWARE AND HARDWARE TYPE STATISTICS

= =

Network:

PLMN

=

Area:

BSC - BSCabc

=

Sort by:

Package ID,BSC,BCF

= = =============================================================================== All the BCFs in the selected area are reported. BCF HW type description: BCF Type

Product names

---------

-------------------

DE21/DF12

Nokia 2nd generation

DE34/DF34

Nokia Talk-family

DE45/DF45

Nokia PrimeSite

Note : Only the default software package for BCF are listed. ===============================================================================

Package ID

BSC Name

BCF Name

Status

BCF Type

-------------------- --------------- --------------- ------------ ---------BTSSWDF2_0_1

BSC11

TEST

NEW

DE34/DF34

DF2_1_1

BSC11

Site aaa

BACK-UP

DE34/DF34

BSC11

Site bbb

BACK-UP

DE34/DF34

BSC11

Site ccc

BACK-UP

DE34/DF34

Example 110. Report 099: BCF software and hardware type statistics

15.6 Frequencies To see the occurrences of frequencies in a BTS area, run the report Occurrence of frequencies (110). = =

OCCURRENCE OF FREQUENCIES

= =

Network:

PLMN

=

Area:

BSC - BSC1

= =============================================================================== The number of occurrences of each frequency is reported. Only frequencies of TRXs existing in the network are counted.


NTC TAN 0935/2.3 en


148


=============================================================================== Nbr of Frequency occurences --------- ---------48

1

49

1

50

1

51

2

52

3

53

1

54

3

55

2

56

2

58

5

59

1

60

2

Example 111. Report 110: Occurrence of frequencies

The frequency plan is the basic setting of the network. Since the plan is very often inserted manually via the NMS/2000, errors may easily occur. To see the frequency plan of a BTS area, run the report Frequency Plan (111). = =

FREQUENCY PLAN

= =

Network:

=

Area:

PLMN All BTSs selected

=

Sorting key:

freq, bcc

= =============================================================================== This report shows the BTS configurations of a Maintenance Region for frequenci es. Decoding of states: N = No state U = Unlocked S = Shutting down L = Locked TRX use: BCCH = BCCH used in TRX TCH


Hopping

If Rf hopping is used then just the MA list id is shown and

.

MA list can be found in the end of the report

Running this report takes a while. Patience please. =============================================================================== Frequency plan. All BTSs selected BCF BTS BSC name

BTS name

TRX

TRX

BTS id

BCF name

id

Freq

TRX BCC

NCC use

TRX states Hopping

-------------- ---------------- ---- ----- ---- ---- ---- ------ ----------


NTC TAN 0935/2.3 en


149


BSC3

RER3CG3007

(7)

RERMIA003

BSC3

RER3CG3008

(8)

RERMIA003

BSC3

FATANP3001

(1)

FATANP001

BSC1

DANDPD1019

(19)

DANDPD010

2

1

4

7 TCH

UUL

None

4

124

4

7 TCH

UUL

None

2

592

0

7 BCCH UUU

Baseband

2

592

1

7 BCCH UUU

Rf (14)

Carrier frequencies of the MA list id for RF hopping MA list id

Frequency

---------- --------14

601 769 778

Example 112. Report 111: Frequency plan

To see where a particular frequency is used, run the report Find cells having the given frequency (047). = =

FIND CELLS HAVING THE GIVEN FREQUENCY

= =

Network:

PLMN

=

Frequency:

80

= =============================================================================== This report displays all cells which have the given frequency. Input parameters: frequency ===============================================================================

Mon Jul 22

page

1

CELLS WITH FREQUENCY 80 BSC name (BCF id) BCF name

(BTS id) BTS name

TRX

admin.state

NCC

admin.s type

BCC

Channel Channel adm.st.

-------------------- -------------------- ------- ------- ------BSC20

(32) Site AAA-1

6

(11) Site AAA

NCC:4

unlckd

unlckd

unlckd


NTC TAN 0935/2.3 en

BCC:6

TCHF

unlckd

TCHF

unlckd

TCHF

unlckd

TCHF

unlckd

TCHF

unlckd

TCHF

unlckd

TCHF

unlckd


150


TCHF

unlckd

Example 113. Report 047: Find cells having the given frequency


NTC TAN 0935/2.3 en


151

Alarms

16

ALARMS This chapter introduces part of the alarm reports provided by BSS Network Doctor.

16.1 Alarm Types and Counts To analyse the stability of the network first on the network level, use the report Alarm types and counts (034). Types and counts of alarms between 19970201 and 19970202 in PLMN network

Amount

Object Urg

Alarm

class

ident Alarm name

cl

of alarms

------ --- ------ -------------------------------------------------- -----BSC

***

2616 IMMEDIATE USER ACTIONS REQUIRED

**

2250 FAILURE IN D-CHANNEL ACTIVATION OR RESTORATION

64

2733 NO FREE RING DISK FILE

52

2692 INCORRECT WORKING STATE

BTS

W ***

*

14

2567 BCCH MISSING

42

2535 BTS WITH NO TRANSACTIONS

46

7937 UNIT TEMPERATURE DANGEROUSLY HIGH

2 2

7946 DIVERSITY BRANCH LNA OUT OF ORDER IN ANTENNA FILT

2

2968 CH CONGESTION IN BTS ABOVE DEFINED THRESHOLD

1

7711 WORKING TRAFFIC CHANNEL RATIO BELOW THRESHOLD 7208 LOCAL BLOCK

W

1

7944 MAIN BRANCH LNA OUT OF ORDER IN ANTENNA FILTER UN

7712 WORKING SDCCH CHANNEL RATIO BELOW THRESHOLD

TRX

5

7710 OBJECT ADMINISTRATION STATE CHANGED

2467 FAILURE IN SENDING SYSTEM INFORMATION TO BTS SITE **

2

7710 OBJECT ADMINISTRATION STATE CHANGED

13 4 1

36

7708 TRX RESTARTED

34

***

7842 NO BCCH TRANSMISSION ACTIVATED

27

**

2967 CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD

*


NTC TAN 0935/2.3 en

194

7529 RECEIVER FAULT

66

7538 SIGNALLING ERROR IN ABIS INTERFACE

41

7900 NO CONNECTION TO TRX

13

7508 RADIO TIMESLOT FAILURE IN TRX

11

7535 RECEIVING FAULT IN BASEBAND MODULE

9

7517 FAILURE IN LOCAL TEST DATA IN FREQUENCY HOPPING

6

7540 AIR INTERFACE DUMB

3

2739 MEAN HOLDING TIME ABOVE DEFINED THRESHOLD

2

2964 EXCESSIVE TCH INTERFERENCE

1

7705 LAPD LINK FAILURE


34

152

Alarms

7208 LOCAL BLOCK

8

Example 114. Report 034: Alarm types and counts

This report tells you which are the most frequent alarms in the network. Some of the alarms may then be analysed further. On the BSC level, Alarm types and counts for BSC (035) checks the NMS/ 2000 database for different types of alarms and lists the alarm urgency class, amount of alarm, alarming object, alarm id and alarm name for each alarm type within the given period and selected BSC(s). The list is sorted by urgency class and number of alarms. Types and counts of alarms between 19980613 and 19980623 in all BSC

Amount

Urg cl

of Object alarms class

Alarm ident Alarm name

--- ------ ------ ------ -------------------------------------------------W

61 BSC 40 BSC

1072 SIGNALLING LINK OUT OF SERVICE

12 BTS

7710 OBJECT ADMINISTRATIVE STATE CHANGED

9 TRX

1565 MEAN HOLDING TIME BELOW DEFINED THRESHOLD

9 TRX

1567 CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD

9 TRX

7708 TRX RESTARTED

8 BTS

1568 CH CONGESTION IN BTS ABOVE DEFINED THRESHOLD

7 LAPD

1254 UNSOLICITED DATA LINK RE-ESTABLISHMENT

6 BCF

7710 OBJECT ADMINISTRATIVE STATE CHANGED

2 BCF

7721 COMMUNICATION FAILURE WITH BCF

1 BSC

***

**

422 TIME UPDATED

9 OSI FORCED CONNECTION CLEARING

1 BSC

1078 PROCESS EXCEPTION

1 BSC

1007 RESTARTED PROGRAM BLOCK

20 BTS

2567 BCCH MISSING

4 TRX

7842 NO BCCH TRANSMISSION ACTIVATED

2 TRX

7900 NO CONNECTION TO TRX

2 TRX

7942 TX ANTENNA FAULTY

1 TRX

7210 BCF/OMU: NO RESPONSE FROM THE UNIT

1 TRX

7723 FAILURE IN SENDING SYSTEM INFORMATION TO BTS SITE

25 TRX

2739 MEAN HOLDING TIME ABOVE DEFINED THRESHOLD

17 TRX

7538 SIGNALLING ERROR IN ABIS INTERFACE

9 DN2

2972 DYNAMIC NODE INTERFACE UNIT FAULT

7 BCF

8075 S ALARM RECEIVED

6 TRX

7941 TX ANTENNA PERFORMANCE DEGRADED

5 TRX

7139 TRX/CU: NO PARAMETERS GIVEN TO UNIT

4 BSC

9122 RECEIVING MEASUREMENT DATA FROM A NETWORK ELEMENT

2 BSC

2250 FAILURE IN D-CHANNEL ACTIVATION OR RESTORATION

2 BSC

2384 MEMORY USAGE OVERFLOW

2 TRX

7317 TRX/XUPx: POWER SUPPLY OUTPUT FAILURE

2 BCF

7991 POWER SUPPLY FAULT

2 BCF

8112 FREQUENCY ERROR

2 BCF

8153 FAULT IN TRANSMITTER

2 BCF

8128 FAULT IN EQUIPMENT

2 BCF

8066 ALARM INDICATION SIGNAL (AIS) RECEIVED

2 TRX

7316 TRX/XUPx: POWER SUPPLY MAINS FAILURE

1 BSC

2075 COMMUNICATION FAILURE BETWEEN SIGNALLING TERMINAL

1 TRX

7530 TX OUTPUT POWER LEVEL DECREASED


NTC TAN 0935/2.3 en


153

Alarms

1 TRX

7533 TX ANTENNA OR COMBINER CONNECTION FAULTY

1 BCF

8099 BIT ERROR RATE (BER) > 10E-3

1 BCF

8081 LOSS OF FRAME ALIGNMENT

1 BCF

8080 RBUS FRAME ERROR

1 BCF

8059 INCORRECT INCOMING SIGNAL LEVEL

1 BCF

2730 CONFIGURATION OF BCF FAILED

1 TRX

7524 TX FREQUENCY TUNER OUT OF ORDER

Example 115. Report 035: Alarm types and counts for BSC

Sometimes you may come across a situation when, for example, a BTS alarm appears under the BSC object in these statistics. The reason for this is that the object sending the alarm does not exist in the NMS/2000. To study the frequency of interesting alarms, use the report BSC alarm breakdown (030).

16.2 Alarm statistics To obtain an overall picture of the alarm flow from Network Elements, run the report Alarm statistics (020). Alarm statistics by alarm severity classes in PLMN network for all MRs

Alarm Severity

tue

wed

thu

fri

sat

sun

mon

tue

wed

thu

16

17

18

19

20

21

22

23

24

25

JUN

JUN

JUN

JUN

JUN

JUN

JUN

JUN

JUN

JUN

-------- ------ ------ ------ ------ ------ ------ ------ ------ ------ -----*** ** * W

12

3

3

1

223

262

262

198

122

7

28

36

16

41

1193

1283

1231

749

660

4

2

4

10

81

142

148

130

146

42

60

99

61

53

656

1343

1469

1084

763

------ ------ ------ ------ ------ ------ ------ ------ ------ -----sum

1423

1585

1532

966

824

779

1549

1718

1279

972

Alarm statistics by source network entity in PLMN network for all MRs

Network Entity

tue

wed

thu

fri

sat

sun

mon

tue

wed

thu

16

17

18

19

20

21

22

23

24

25

JUN

JUN

JUN

JUN

JUN

JUN

JUN

JUN

JUN

JUN

-------- ------ ------ ------ ------ ------ ------ ------ ------ ------ -----BS BSC

9

51

39

18

26

13

40

36

24

4

13

19

11

11

4

11

11

11

13

141

DN2

7

7

HLR

854

894

916

449

361

352

969

1061

749

444

MSC

379

418

398

314

313

314

415

506

395

301

168

196

168

174

120

89

114

104

98

75

OMC

------ ------ ------ ------ ------ ------ ------ ------ ------ -----sum

1423

1585

1532

966

824

779

1549

1718

1279

972

Example 116. Report 020: Alarm statistics


NTC TAN 0935/2.3 en


154

Alarms

16.3 Alarm Statistics per Cell The Alarm statistics per cell (023) report lists the occurrences of a selected alarm over a selected period of time, showing in detail when, for how long and where it occurred. Alarm

7712 Statistics from 19980416 to 19980420 ALM HOLD BTS /

START

START

END

END

DATE

TIME

DATE

TIME

TIME BCF / (sec) BSC

----------- -------- ----------- -------- -------- -------------------1998-APR-16 23:23:29 1998-APR-17 04:40:47

19038 HIPPOS2017

HIPPOS009

BSC2UPS1

1998-APR-16 23:23:28 1998-APR-17 04:40:47

19039 MAKKYL2012

MAKKYL006

BSC2UPS1

1998-APR-16 23:23:24 1998-APR-17 04:40:46

19042 5KOM2009

5KOM005

BSC2UPS1

1998-APR-16 23:23:21 1998-APR-17 04:40:46

19045 3UPS2003

3UPS001

BSC2UPS1

Example 117. Report 023: Alarm statistics per cell

16.4 Active BCCH Missing Alarms The 'BCCH missing' alarm stands for cell outage. In the Active BCCH missing alarms (024) report these alarms are listed per BTS in chronological order. START

START

END

BCF NAME /

BSC

DATE

TIME

DATE

BTS NAME

NAME

----------- -------- ------ -------------------- ------------1998-NOV-30 11:17:11

hold

1998-NOV-17 13:41:11

HIOMO015

BSC2

HIOMO013 hold

HIOMO015

BSC2

HIOMO013

Example 118. Report 024: Active BCCH missing alarms

16.5 BTS Alarm Sum Time by Cells The BTS alarm sum time by cells (025) report shows the sum time of the selected alarm, which is calculated for each BTS (cell) in minutes over the given period.


NTC TAN 0935/2.3 en


155

Alarms

Note:

Only the alarms that are started during the selected period are shown.

Statistics of Alarm

2567

Time

BTS name

BSC name

Total

Sum

BCF Name

(BTS id)

Occurance

(min)

------------------------- --------------- --------- ---------SANKUD2021

BSC2UPS1

SANKUD010

(21)

KUTOJA1001

BSC1KUTOJA

KUTOJA001

(1)

4

5535.55

16

99.78

1

0.65

1

0.62

1

0.62

(report model cut here) SANDPG1018

BSC1KUTOJA

SANDPG009

(18)

HER3AD3010

BSC3TRE

HERMIA004

(10)

HER3AD3011

BSC3TRE

HERMIA004

(11) --------- ----------

avg

5

252.40

sum

112

6057.52

Example 119. Report 025: BTS alarm sum time by cells


NTC TAN 0935/2.3 en


156

Locating Network Elements

17

LOCATING NETWORK ELEMENTS The reports introduced in this chapter allow you to find specific data on various network elements.

17.1 All Base Station Sites per Maintenance Region The All base station sites per maintenance region (041) report lists all base station sites of the selected maintenance region in alphabetical order. The number of cells (BTSs) in each base station is counted for all existing BTSs in the network (i.e. which have as the parameter set name). Nbr of BTS MR name

BCF name

BSC (BCF id)

in network

---------- --------------- -------------------- ---------Global Sco 002

BSC_WWWWW

(1)

3

Global Sco 003

BSC_SSSSS

(1)

3

Global Sco 004

BSC_WWWWW

(2)

3

----------

sum

9

Example 120. Report 041: All base station sites per maintenance region

17.2 All cells with LAC and CI The All cells with LAC and CI (043) report lists the CIs, LACs and names of all cells in the selected Maintenance Region sorted according to CI and LAC. The search is done only for the cells which have as the parameter set name, i.e. those that exist in the network. Cells with LAC and CI BTS LAC CELL ID NAME

BCF NAME

------ ------- ------------------------------ -----------------------------2

20001 3PRT2001

3PRT001

20002 3PRT2002

3PRT001

20003 3PRT2003

3PRT001

20004 1PRT2004

1PRT002

20005 1PRT2005

1PRT002

20006 1PRT2006

1PRT002

20009 5MRG2009

5MRG005

20010 5MRG2010

5MRG005

Example 121. Report 043: All cells with LAC and CI

17.3 BS Sites Having the Given Character String in the Name The Find BS sites having the given character string in the name (044) report displays all BCFs or BTSs which have the given string in the name.


NTC TAN 0935/2.3 en


157


Note:

The search string is case sensitive and the search is done based on the BCF name.

Cells with 12 string in BCFs name BSC name

(BTS id) BTS name

(TRX id)

(BCF id) BCF name

NCC

freq.

BCF adm.st.

BTS adm.st.

BCC

PCM/TSL

adm.state

Ch.type adm.st.

/SUBTSL

-------------------- -------------------- ---------- ------- ---------- ------BSC_XXXXX

(40) XLAWW

(1)

(31) 212

NCC:0

ARFN:21

unlckd

unlckd

BCC:0

MBCCHC

unlckd

44/1/0

TCHF

unlckd

44/1/1

TCHF

unlckd

44/1/2

TCHF

unlckd

44/1/3

TCHF

unlckd

44/2/0

TCHF

unlckd

44/2/1

TCHF

unlckd

44/2/2

TCHF

unlckd

44/2/3

MBCCH

unlckd

52/13/0

unlckd

BSC_XXXXX

(61) TSCWW

(1)

(37) 128

NCC:5

ARFN:9

unlckd

unlckd

BCC:7

unlckd

Example 122. Report 044: Find BS sites having the given character string in the name

17.4 Cells Having the Given CI and LAC The Find cells having the given CI and LAC (045) report displays all cells (BTSs) which have the given Cell Identity and Loaction Area Code. BSC

BCF name (BCF if)

BTS name (BTS id)

LAC

CI

------------ -------------------- -------------------- ---------- ---------XXX_BSC_3

088B (2)

F9992 (2)

1

882

Example 123. Report 045: Find cells having the given CI and LAC

17.5 Cells Having an Adjacent Cell with the Given CI and LAC The Find cells having an adjacent cell with the given CI and LAC (046) lists the data from all BTSs in a network. FIND CELLS HAVING AN ADJACENT CELL WITH THE GIVEN CI AND LAC BSC

BCF BTS

LAC

CI

INT_ID

------------ --- -------------------- ----- ----- -----XXX_BSC_1

5

15-XXEG3

1

383

2036

XXX_BSC_3

18

53-XX1G2

2

372

2256


NTC TAN 0935/2.3 en


158


XXX_BSC_3

1

1-FXXG1

1

881

308

XXX_BSC_3

3

3-FXXG3

1

883

314

XXX_BSC_3

24

72-XXCG3

1

813

6919

XXX_BSC_3

16

46-LXXG1

1

341

5419

XXX_BSC_3

16

48-LXXG3

1

343

5425

XXX_BSC_3

33

99-QXXG1

1

351

10569

XXX_BSC_3

34

102-QXXG2

1

352

10572

XXX_BSC_3

35

105-QXXG3

1

353

10575

Example 124. Report 046: Find cells having an adjacent cell with the given CI and LAC


NTC TAN 0935/2.3 en


159

Named Sets

18

NAMED SETS The Number of named parameter sets (080) report shows the number of named sets for BTS objects. Actual, Lastomc, Default, Backup and Clipboard sets are not counted. If the number is high (thousands in the whole network), it should be studied if the sets are really needed. The next step is to study the names. BSC

BCF

BTS

POC

HOC

LAPD

TRX

CHN

SET

SET

SET

SET

SET

SET

SET

SET

COUNT

COUNT

COUNT

COUNT

COUNT

COUNT

COUNT

COUNT

------ ------ ------ ------ ------ ------ ------ -----4

95

3214

1247

1576

0

517

4032

Example 125. Report 080: Number of named parameter sets

The Named sets used (081) report shows all named sets used in a Maintenance Region or network. Actual, Lastomc, Default and Clipboard sets are not presented because they are usual. The next step is to study how a particular name is allocated in the network. BSC NAMED SETS ============== SET NAMES -------------------BACKUP DEFAULT Default

BTS NAMED SETS ============== SET NAMES -------------------056 06 094 10 100 101 101A 101B 101C

Example 126. Report 081: Named sets used

The Allocation of a named set (082) report shows the allocation of the given named set on the area. BSC NAMED SETS ==============


NTC TAN 0935/2.3 en


160

Named Sets

no rows selected

BCF NAMED SETS ============== no rows selected

BTS NAMED SETS ============== SET_NAME

NAME

BCF NAME

BTS

-------------------- --------------- --- --------------- --24

XXX_BSC_2

6

PXXC1

16

24

XXX_BSC_2

6

PXXC2

17

24

XXX_BSC_2

6

PXXC3

18

3 rows selected.

HOC NAMED SETS ============== SET_NAME

NAME

BCF NAME

BTS

-------------------- -------------------- --- -------------------- --24

XXX_BSC_2

6

PXXC3

18

24

XXX_BSC_2

6

PXXC2

17

24

XXX_BSC_2

6

PXXC1

16

NAME

BCF NAME

3 rows selected.

POC NAMED SETS ============== SET_NAME

BTS

-------------------- -------------------- --- -------------------- --24

XXX_BSC_2

6

PXXC3

18

24

XXX_BSC_2

6

PXXC2

17

24

XXX_BSC_2

6

PXXC1

16

3 rows selected.

TRX NAMED SETS ============== SET_NAME

NAME

BCF NAME

BTS TRX

-------------------- --------------- --- --------------- --- --24

XXX_BSC_2

6

PXXC1

16

1

24

XXX_BSC_2

6

PXXC1

16

2

24

XXX_BSC_2

6

PXXC3

18

5

24

XXX_BSC_2

6

PXXC3

18

6

24

XXX_BSC_2

6

PXXC2

17

3

24

XXX_BSC_2

6

PXXC2

17

4

Example 127. Report 082: Allocation of a named set


NTC TAN 0935/2.3 en


161

Other Measurable Qualities

19

OTHER MEASURABLE QUALITIES There are numerous measurable features which you can use to analyse the problems in the network. In the following, some of the most frequently used ones are presented: •

uplink and downlink quality and level

•

link balance

•

cell coverage (distance ranges)

•

handover cause

•

BSC clear codes

•

troubleshooting

19.1 Uplink and Downlink Quality and Level BSS Network Doctor provides several optional reports to monitor UL and DL occurrences at various network levels.

19.1.1

Uplink and Downlink Quality on Area Level

For daily distribution of UL and DL quality to classes 0-7, choose the report Performance statistics (benchmark) (200).

19.1.1.1 Reports Based on RX Quality =

UL, DL QUALITY ANALYSIS

=============================================================================== Uplink quality cumulative distribution (%) : Day MMDD

Qual0

Qual1

Qual2

Qual3

Qual4

Qual5

Qual6

Qual7

--- ---- ------- ------- ------- ------- ------- ------- ------- ------sat 0201

88.84

90.49

92.32

94.33

96.17

97.40

98.73

100.00

fri 0131

89.95

91.47

93.14

95.02

96.69

97.75

98.88

100.00

thu 0130

89.32

90.87

92.62

94.56

96.32

97.53

98.80

100.00

wed 0129

89.68

91.18

92.85

94.73

96.46

97.61

98.84

100.00

tue 0128

89.37

90.95

92.74

94.71

96.40

97.58

98.82

100.00

Qual5

Qual6

Qual7

Downlink quality cumulative distribution (%) : Day MMDD

Qual0

Qual1

Qual2

Qual3

Qual4

--- ---- ------- ------- ------- ------- ------- ------- ------- ------sat 0201

90.53

92.72

94.68

96.31

97.67

98.69

99.41

100.00

fri 0131

91.20

93.31

95.23

96.80

98.04

98.92

99.55

100.00

thu 0130

91.35

93.39

95.24

96.77

97.99

98.88

99.51

100.00

wed 0129

91.51

93.49

95.27

96.76

97.95

98.84

99.49

100.00

tue 0128

91.00

93.11

95.02

96.57

97.82

98.76

99.44

100.00


NTC TAN 0935/2.3 en


162


Example 128. Area level data on UL and DL quality in report 200, Performance statistics (benchmark).

For the average distribution of UL and DL quality, run the report Network benchmark statistics (204). Cumulative uplink quality distribution (ulq_2) : Qual0

Qual1

Qual2

Qual3

Qual4

Qual5

Qual6

Qual7

------- ------- ------- ------- ------- ------- ------- ------88.77

91.04

93.05

94.92

96.59

97.92

99.00

100.00

Qual6

Qual7

Cumulative downlink quality distribution (dlq_2) : Qual0

Qual1

Qual2

Qual3

Qual4

Qual5

------- ------- ------- ------- ------- ------- ------- ------81.64

85.40

89.37

92.72

95.49

97.58

98.98

100.00

Example 129. Average distribution of UL and DL quality in report 204, Network benchmark statistics.

19.1.1.2 Reports Based on RX-level Statistics For the average distribution of UL and DL quality versus RX level range, run the report Network benchmark statistics (204). =

UL, DL QUALITY/LEVEL DISTRIBUTION

= =============================================================================== Note: The used measurement 'Rx Level Statistics' is an optional BSC feature. Uplink quality/level distribution: Note: For TRX level list run the report 197. Class

Share

upper

UL

UL

UL

UL

UL

UL

UL

UL

in

range

q0

q1

q2

q3

q4

q5

q6

q7

range

(dBm)

(%)

(%)

(%)

(%)

(%)

(%)

(%)

(%)

(%)

------ ------- ------- ------- ------- ------- ------- ------- ------- -------100

1.28

0.24

0.31

0.30

0.31

0.32

0.49

0.66

3.92

-95

3.10

0.29

0.28

0.23

0.22

0.21

0.33

0.15

4.80

-90

7.01

0.35

0.31

0.27

0.27

0.25

0.31

0.13

8.91

-80

40.91

0.66

0.59

0.64

0.64

0.50

0.42

0.19

44.54

-70

25.16

0.17

0.18

0.25

0.28

0.19

0.11

0.08

26.42

> -48

11.12

0.02

0.03

0.07

0.07

0.04

0.02

0.02

11.40

------- ------- ------- ------- ------- ------- ------- ------- ------sum

88.59

1.73

1.70

1.76

1.79

1.51

1.69

1.23

100.00

Downlink quality/level distribution: Note: For TRX level list run the report 197. Class

Share

upper

DL

DL

DL

DL

DL

DL

DL

DL

in

range

q0

q1

q2

q3

q4

q5

q6

q7

range

(dBm)

(%)

(%)

(%)

(%)

(%)

(%)

(%)

(%)

(%)

------ ------- ------- ------- ------- ------- ------- ------- ------- -------


NTC TAN 0935/2.3 en


163


-100

0.46

0.06

0.07

0.09

0.10

0.12

0.10

0.08

1.07

-95

1.03

0.11

0.11

0.13

0.12

0.09

0.06

0.05

1.70

-90

3.27

0.21

0.23

0.22

0.19

0.15

0.10

0.07

4.44

-80

32.42

1.00

0.98

0.84

0.65

0.46

0.30

0.23

36.89

-70

22.02

0.82

0.82

0.73

0.53

0.35

0.21

0.19

25.68

28.00

0.62

0.56

0.46

0.28

0.14

0.08

0.09

30.23

> -48

------- ------- ------- ------- ------- ------- ------- ------- ------sum

87.21

2.82

2.78

2.47

1.87

1.31

0.85

0.71

100.00

Example 130. Average distribution of UL and DL quality versus RX level range in the Network benchmark statistics (204) report.

19.1.2

Uplink and Downlink Quality on TRX Hit List

19.1.2.1 Reports Based on RX Quality The report UL and DL quality and UL interference per TRX, 24-hour/10day breakdowns (196) is based on the optional BSC measurement RX Quality. UL, DL Quality and Inteference per TRX (Part 1) between 19980530 and 19980608 sorted by bsc_name,bcf_name, bts_name asc q 0 q 1 q 2 q 3 q 4 q 5 q 6 q 7 (%) (%) (%) (%) (%) (%) (%) (%) *** *** *** *** *** *** *** *** BSC Name

BCF Name

UL

UL

UL

UL

UL

UL

UL

UL

Call min Intrf

(BTS) TRX

BTS Name

DL

DL

DL

DL

DL

DL

DL

DL

Call dif Freq

------------- ------------- --- --- --- --- --- --- --- --- -------- ----LINDA

LINDA

73

77

82

87

92

95

99 100

4051

1.1

(1) trx:1

Cid 5001

85

87

90

93

95

98

99 100

1

chgd

LINDA

LINDA

99 100 100 100 100 100 100 100

149

1.0

(30) trx:1

Cid 5030

77

84

90

94

97

99 100 100

4

48

LINDA

LINDA

74

81

88

93

97

98

99 100

2246

1.0

(66) trx:1

Cid 5066

87

90

93

95

96

97

99 100

1

chgd

Example 131. Report 196: UL and DL quality and UL interference per TRX, 24hour/10-day breakdowns

19.1.2.2 Reports Based on RX-level Statistics The report UL and DL quality per TRX (197) is based on the optional BSC measurement RX Level Statistics. UL, DL quality per TRX between 19970201 and 19970202 %in

%in

%in

%in

%in

%in

%in

%in

q 0

q 1

q 2

q 3

q 4

q 5

q 6

q 7

***

***

***

***

***

***

***

***

Call

BSC Name

BCF Name

UL

UL

UL

UL

UL

UL

UL

UL

time

(BTS) TRX

BTS Name

DL

DL

DL

DL

DL

DL

DL

DL

(min)

------------- --------------- ---- ---- ---- ---- ---- ---- ---- ---- -------


NTC TAN 0935/2.3 en


164


BSC_XXXXX

206

72

72

73

74

76

77

80

100

(34) trx:1

XNEWW

94

95

97

98

99

99

100

100

BSC_XXXXX

202

72

72

73

75

77

78

83

100

(49) trx:3

XCTQQ

95

96

97

97

99

99

100

100

BSC_XXXXX

215

74

75

76

78

79

81

84

100

(25) trx:1

XOUWW

95

95

96

97

98

99

100

100

13

14

22

Example 132. Report 197: UL and DL quality per TRX

19.1.3

Uplink and Downlink Quality on BTS Level

On the BTS level, choose from BSS Network Doctor the report you need according to what type of measurement they are based on.

19.1.3.1 Reports Based on RX Quality For worst values and TRX specific values, run the report Cell analyser (216). =

Cell DL, UL quality

=

BSC_WWWWW

=

bts id:70

name:TPFWW

from 19970201 to 19970202

=============================================================================== Note: The used measurement 'Rx Quality' is an optional BSC feature. .

Whole

.

period

.

average

.

=======

. DL call samples in q0-q5, worst value.(TRX level)

na %

UL call samples in q0-q5, worst value.(TRX level)

na %

UL q0-5 UL q0-5 TRX

(%)

DL q01-5 DL q0-5

(%)

(%)

(%) Traffic

id Busy Hour average Busy Hour average

(%)

--- --------- ------- --------- ------- ------1

96.5

99.2

94.0

99.8

100.0

Example 133. Worst and TRX specific values of UL and DL quality on the basis of RX quality in report 216, Cell analyser.

This report shows also the hourly breakdown of UL and DL cumulative quality q0-q5. DL call samples in q0-q5 (%) ABC_BSC_1

bcf:336

(dlq_2) bts:55 ITAG1

trx:1

************************************************************************ Blank hours are missing data (only hours with TCH samples are reported to OMC).

-1 = dividor was zero and ratio could not be counted

Hints: For a BTS level hit list, run report 196.


NTC TAN 0935/2.3 en


165


tue Hr

wed

thu

fri

sat

sun

mon

tue

wed

thu

fri

19

20

21

22

23

24

25

26

27

28

29

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

AUG

-- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----00

100

0

100

100

0

01

100

02

0

06

0

07

100

0

0

0

100

0

0 0

0 100

0

0

0

100

09

100

100

100

100

0

100

100

100

100

100

10

100

100

100

100

100

100

100

100

100

100

11

100

100

100

100

100

100

100

100

100

100

12

100

100

100

100

100

100

100

100

100

100

13

100

100

100

100

100

100

100

100

100

100

14

100

100

100

100

100

100

100

100

100

100

15

100

100

100

100

100

100

100

100

100

100

16

100

100

100

100

100

100

100

100

100

100

17

100

100

100

100

100

100

100

100

100

100

18

100

100

100

100

100

100

100

100

100

100

19

100

100

100

100

100

100

100

100

100

100

20

100

100

100

100

100

100

100

100

100

100

21

100

98

100

100

100

100

100

100

100

100

22

100

100

100

100

100

100

100

100

100

100

0

100

100

0

0

100

0

100

0

23

100

100

100

08

Example 134. Cumulative UL and DL quality on the basis of RX quality in report 216, Cell analyser.

For UL and DL quality distribution per hour, run the report Cell doctor (213). %in

%in

%in

%in

%in

%in

%in

%in

Call

q0

q0_1 q0_2 q0_3 q0_4 q0_5 q0_6 q0_7 smpls

***

***

***

***

***

***

***

***

***

UL

UL

UL

UL

UL

UL

UL

UL

UL

TRX dd hh DL

DL

DL

DL

DL

DL

DL

DL

DL

--- -- -- ---- ---- ---- ---- ---- ---- ---- ---- -----5 01 18

19

20

21

96

97

98

99

99

99

100

100

2907

91

95

97

98

99

99

100

100

2907

97

97

98

98

99

99

99

100

4298

96

97

99

99

100

100

100

100

4298

96

97

97

98

98

99

99

100

2214

96

98

98

99

99

99

100

100

2214

95

96

97

99

99

100

100

100

3985

95

97

99

100

100

100

100

100

3985

Example 135. Hourly distribution of UL and DL quality in report 213, Cell doctor.

19.1.3.2 Reports Based on RX level Statistics BSC measurements based on RX level statistics are provided by the report Cell analyser (216).


NTC TAN 0935/2.3 en


166


=

Cell DL, UL quality/level distribution

=

BSC_WWWWW

=

bts id:70

name:TPFWW

from 19970201 to 19970202

=============================================================================== Note: The used measurement 'Rx Level Statistics' is an optional BSC feature. Uplink quality/level distribution

Class upper

UL

UL

UL

UL

UL

UL

UL

UL

TRX range

q0

q1

q2

q3

q4

q5

q6

q7

id (dBm)

(%)

(%)

(%)

(%)

(%)

(%)

(%)

(%)

---- ------ ----- ----- ----- ----- ----- ----- ----- ----

1 -100

9.1

1.4

1.8

1.8

1.7

1.5

1.5

1.6

-95

13.5

0.5

0.4

0.4

0.3

0.2

0.2

0.1

-90

21.2

0.2

0.2

0.3

0.2

0.1

0.0

0.0

-80

39.2

0.1

0.1

0.3

0.2

0.1

0.0

0.0

-70

1.7

0.0

0.0

0.0

0.0

0.0

0.0

0.0

0.2

0.0

0.0

0.0

0.0

0.0

0.0

0.0

> -48 ****

----- ----- ----- ----- ----- ----- ----- -----

sum

84.9

2.2

2.5

2.7

2.4

1.8

1.8

1.7

Downlink quality/level distribution

Class upper

DL

DL

DL

DL

DL

DL

DL

DL

TRX range

q0

q1

q2

q3

q4

q5

q6

q7

id (dBm)

(%)

(%)

(%)

(%)

(%)

(%)

(%)

(%)

---- ------ ----- ----- ----- ----- ----- ----- ----- ----

1 -100 -95

0.7

0.2

0.3

0.3

0.5

0.6

0.8

0.8

3.6

0.5

0.6

0.8

0.9

1.1

1.3

0.8

-90

8.4

1.0

1.2

1.6

1.6

1.6

1.1

0.6

-80

28.7

1.5

1.4

1.4

1.0

0.7

0.3

0.1

-70

23.5

0.3

0.2

0.2

0.1

0.1

0.0

0.0

9.4

0.0

0.0

0.0

0.0

0.0

0.0

0.0

> -48 **** sum

----- ----- ----- ----- ----- ----- ----- ----74.3

3.6

3.7

4.3

4.1

4.1

3.5

2.4

Example 136. BSC measurements based on RX-level statistics in report 216, Cell analyser.

For UL and DL quality distribution per hour, run the report Cell doctor (213). Uplink quality/level distribution Call Class time upper TRX

(min) range

id DD HR trf_32b (Bm)

UL

UL

UL

UL

UL

UL

UL

UL

q0

q1

q2

q3

q4

q5

q6

q7

(%)

(%)

(%)

(%)

(%)

(%)

(%)

(%)

---- -- -- ------- ----- ---- ---- ---- ---- ---- ---- ---- ---3 04 09

2 -100

0

0

0

0

0

0

0

0

-95

3

0

0

0

0

0

0

0

-90

25

0

0

0

0

0

0

0

-80

71

0

0

0

0

0

0

0

-70

0

0

0

0

0

0

0

0

> -48

0

0

0

0

0

0

0

0

Downlink quality/level distribution


NTC TAN 0935/2.3 en


167


Call Class time upper

DL

DL

DL

DL

DL

DL

DL

DL

(min) range

q0

q1

q2

q3

q4

q5

q6

q7

id DD HR trf_32b (dBm)

(%)

(%)

(%)

(%)

(%)

(%)

(%)

(%)

TRX

---- -- -- ------- ----- ---- ---- ---- ---- ---- ---- ---- ---3 04 09

2 -100 -95

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0 0

-90

0

0

0

0

0

0

0

-80

76

0

4

12

6

0

0

0

-70

0

0

0

0

0

0

0

0

> -48

0

0

0

0

0

0

0

0

Example 137. Hourly distribution of UL and DL quality in report 213, Cell doctor.

19.2 Link Balance Link balance is an important quality factor. A common target is to reach +-3 dB and at least +-5 dB. When analysing the results, note that the BCCH TRX is always on full power and that it affects the results on the BTS level, thus making them difficult to interpret.

19.2.1

Link Balance on Area Level

To obtain the percentage of measurement samples per balance class/power limit class, run the report Cells by DL and UL level balance (195). Although not very accurate, it offers an option if the Link Balance measurement is not available. Cells by signal level balance between 19980205 and 19980205 ave

BSC Name

BCF Name

(BTS ID)

BTS Name

ave

MS

BS

pwr

pwr

attn

attn

UL

(dB)

str

(dB)

ave

ave average DL

level

str balance

----------- --------------- ------ ------ ------ ------ ------BSC3TRE

REHMIA003

7

REH3CG3007

BSC3TRE

KATANP001

3

KATANP30003

12.2

19.6

27.5

29.0

1.6

2.6

7.9

18.5

19.1

0.6

Example 138. Link balance in report 195, Cells by DL and UL level balance

The Link balance of an area (199) report is based on the link balance measurement. MS Link balance Samples (dB)

BS

Max

Normal limited limited

power

(%)

(%)

(%)

(%)

---------- --------------- ------ ------- ------- -----31878057 -20 to -15

0

0

0

0

-14 to -10

1

0

0

0

-09 to -06

2

1

0

1


NTC TAN 0935/2.3 en


168


-05 to -03

2

1

0

1

-02 to -01

2

0

0

1

0

2

1

0

1

01 to 02

5

2

0

2

03 to 05

4

2

0

3

06 to 09

6

5

1

8

10 to 14

5

5

3

13

15 to 20

3

2

6

8

Example 139. Report 199: Link balance of an area

19.2.2

Link Balance on BTS Hit List

The report Cells by DL and UL level balance (195) is based on Power Control measurement. Although not very accurate, it offers an option if the Link Balance measurement is not available. The report Cells having bad link balance (191) is based on the Link Balance measurement. It provides you with a list to find the cells from an acceptable balance range. = =

CELLS HAVING BAD LINK BALANCE (DL, UL)

= =

Network:

PLMN

=

Area:

BTS GRP - XXXXXXXXGRP

=

Period:

from 19970201 to 19970202

=

Acceptance range:

-5dB ... 5dB

=

Presence threshold:

100 %

=

Sorting:

Share in BS limit

= =============================================================================== For each cell the share (%) of samples in the given range is counted. This report shows the cel ls having less than the given % of samp les in the range. Samples in acc. range

/lb_2

.

Percentage of samples in the acceptable balance range

Normal

/lb_3

.

Share of path balance measurements when MS power < MS TX PWR MAX and

.

BS power < BS TX PWR MAX (normal)

MS limited

/lb_4

Share of samples when MS full power

.

MS power = min(MS TX PWR MAX, MS MAX PEAK POWER)

.

and BS power < BS TX PWR MAX

BS limited

/lb_5

.

Share of samples when BS full power MS power < MS TX PWR MAX and

.

BS power = BS TX PWR MAX

Max power

/lb_6

Share of sample when MS and BS full power

.

MS power = min(MS TX PWR MAX, MS MAX PEAK POWER)

.

and BS power = BS TX PWR MAX

Measurement used: p_nbsc_link_balance Note: Running this report takes a while. Patience please. =============================================================================== Cells having less or equal to 100 % of samples in acppetance range


NTC TAN 0935/2.3 en


169


between 19970201 and 19970202

Samples in

BSC Name

BCF Name

(BTS id)

BTS Name

MS

BS

max

acc. range normal limited limited power (%)

(%)

(%)

(%)

(%)

--------------- ------------------ ---------- ------ ------- ------- ----BSC_XXXXX

030

(7)

LKPWW

BSC_XXXXX

030

(9)

LKPMM

BSC_XXXXX

030

(8)

LKPQQ

20

0

0

53

47

17

0

0

55

45

12

0

0

61

39

Example 140. Report 191: Cells having bad link balance

The report Link balance per cell (208) is based on Power Control measurement. = =

LINK BALANCE PER TRX

= =

Network:

=

Area:

PLMN All BTSs selected

=

Period:

from 19981117 to 19981117

=

Sorted by:

DL path loss

=

Combiner loss (single TRX cells):

-2.1

=

Combiner loss (multi TRX cells) :

-5.2

=

BTS RX diversity gain:

0

=

Threshold for balance :

9.0

= =============================================================================== This report counts the power loss balance between UL and DL for each TRX of each cell of the selected area. In this report it is assumed that the max BS power is 44.7 dBm. For each TRX the following data is displayed.: DL loss factors: **************** .

BS power (dBm)

.

combiner loss (dBm)

/pwr_2

(max.power is 44.7)

Depends on network. Given by user for single TRX

. .

Average BS power level and multi TRX cases.

DL sig st (dBm)

DL path loss

/lev_1

(dBm)

Average DL signal strength measured by MS. Counted based on the factors above.

.

(BS power - combiner loss - DL sig st)

UL loss factors: **************** .

MS power (dBm)

/pwr_1b

Average MS power level.

.

UL sig str (dBm)

/lev_2

Average UL signal strength measured by BTS.

UL path loss (dBm)

Counted based on the factors above.

.

(MS power - UL sig st)

Balance (dBm)

The difference between DL and UL path losses.


NTC TAN 0935/2.3 en


170


Measurement periods without traffic are excluded in calculation. Measurement used: p_nbsc_power Running this report takes a few minutes. Patience please. ===============================================================================

Link balance per TRX between 19981117 and 19981117 in PLMN network DL loss factors

UL loss factors

***************

***************

BCF

BCFtype BS power

DL MS power

UL

BTS

BTS id

combiner loss

path

path Balance

BSC

TRX id

DL sig str

loss UL sig str

loss

DL-UL

-------------- ------- --------------- ------ --------------- ------ ------SANKUD010

DE21

44.7

SANKUD2021

21

BSC2UPS1

3

KILO007

DF12

44.7

KILO1012

12

-5.2

BSC1KUTOJA

3

152.6

30.0

140.0

12.6

140.0

9.5

-2.1 -110.0

-110.0 149.5

-110.0

30.0 -110.0

Example 141. Report 208: Link balance per cell

19.2.3

Link Balance on BTS Level

For information on link balance breakdown on the BTS level over a period of time, run the report Cell analyser (216). MS power levels path balance (dB)

BS

Max


MS

power

(%)

(%)

(%)

(%)

--------------- ------ ------- ------- ------20 to -15

0

0

0

0

-14 to -10

0

0

0

0

-09 to -06

0

0

0

0

-05 to -03

0

0

0

0

-02 to -01

0

0

0

0

0

0

0

0

0

01 to 02

0

0

0

0

03 to 05

0

0

0

0

06 to 09

0

0

1

2

10 to 14

0

0

4

7

15 to 20

0

0

78

9

Example 142. BTS level data on link balance as shown in report 216, Cell analyser.

The report Cell doctor (213) provides the best time resolution, but normally, due to the load on the network, the measurement period is set t o 24 or 12 hours, and so the resolution is not any better than that of the Cell analyser (216) report.


NTC TAN 0935/2.3 en


171


MS power levels path balance

MS

dd hh (dB)

BS

Max


power

-- -- --------------- ------ ------- ------- -----01 00 -20 to -15

0

0

0

0

-14 to -10

0

0

0

0

-09 to -06

0

0

1

0

-05 to -03

0

0

0

0

-02 to -01

0

0

1

0

0

0

0

1

0

01 to 02

0

0

2

0

03 to 05

0

0

5

1

06 to 09

0

0

13

2

Example 143. BTS level data on link balance as shown in report 213, Cell doctor.

In the Cells by dominant link balance range (198) report the cells are listed according to the dominant path balance range, i.e the range having biggest share of the path balance measurement samples. Cells by dominant Path Balance range MS pwr lev Share in path bal BSC (BTS id)

BTS/BCF NAME

(dB)

range (%)

--------------- ------------------ ---------- -------BSC41

84

(6)

Brown Hill

BSC41

15168

(63)

Newcastle

BSC41

116

(49)

Arrow head

BSC44

259

(52)

Museum

10 to 14

51

10 to 14

52

15 to 20

80

15 to 20

53

Example 144. Report 198: Cells by dominant link balance range

19.3 MS Speed MS Speed reports are based on the MS Speed measurement which is an optional BSC feature. In Cell Analyser (216), the summary of MS Speed is shown for one BTS. = = =

MS SPEED BSC2UPS1

bts id:4

name:1UPS2004

from 19980714 to 19980714

=============================================================================== Note: - The used measurement 'MS SPEED' is an optional BSC feature. - BTS version DF3.0 or B10 needed.


NTC TAN 0935/2.3 en


172


- Speed class limits can be modified by MML command ZEGI (S6) and EEQ (S7). - Speed classes are average values in this report. If limits have been changed . decimal values may be displayed. Speed

Speed

Speed

Speed

Speed

Speed

class 1

class 1

class 2

class 2

class 3

class 3

(km/h)

samples

(km/h)

samples

(km/h)

samples

--------- ----------- --------- ----------- --------- ----------0...20

83.74%

21...60

16.26%

61...512

0%

Example 145. MS speed in report 216, Cell Analyser.

In Cell Doctor (213), the MS Speed per measurement period is shown for one BTS. =

BTS -

=

BSC2UPS1

=

MS SPEED bts id:4

name:1UPS2004

from 19980714 to 19980714

=============================================================================== Note: - The used measurement 'MS SPEED' is an optional BSC feature. - BTS version DF3.0 or B10 needed. - Speed class limits can be modified by MML command ZEGI (S6) and EEQ (S7).

Speed

Speed

Speed

Speed

Speed

class 1

class 1

class 2

class 2

class 3

DD HR (km/h)

samples

(km/h)

samples

Speed class 3

(km/h)

samples

-- -- --------- ----------- --------- ----------- --------- ----------14 09 0...20 17 0...20

230(93%) 21...60 0(0%)

21...60

17(7%) 0(0%)

61...512 61...512

0(0%) 0(0%)

18 0...20

20(53%) 21...60

18(47%) 61...512

0(0%)

21 0...20

23(56%) 21...60

18(44%) 61...512

0(0%)

Example 146. MS speed per measurement period in report 213, Cell doctor.

19.4 Cell Coverage Cell coverage reports are based on the Timing Advance measurement.

19.4.1

Dominant Distance Range on BTS List

In the report Cells by dominant distance range (231), BTSs are listed according to the distance range where most of the measurement samples are. = =

CELLS BY DOMINANT DISTANCE RANGE

= =

Network:

=

Maintenance Region: CAPITAL

=

BTS group:

group selection bypassed

=

Period:

from

=

Threshold :

=

Order by :

=


NTC TAN 0935/2.3 en

PLMN

19960711 to

19960711

90 % of samples Distance Range upper limit, share in range


173


= =============================================================================== In this report the cells are listed according to the dominant distance range, i.e. the range having the biggest share of the measurement samples. The Distance Range is based on Timing Advance. Share in range (%)

Percentage of path balance measurements

Measurement used: Timing Advance Input parameters: time period, maint.region, bts group Instructions:

Use the Cell analyser (216) report to study the details.

Note: Running this report takes a while. Patience please. =============================================================================== Cells by dominant Distance Range Distance Distance

BSC (BTS id)

BTS/BCF NAME

range

range

lower

upper

Share in

limit

limit

range

(km)

(km)

(%)

--------------- ------------------ -------- -------- -------BSC44

360

(45)

Site GGG

BSC42

15104

(16)

Site HHH

BSC42

293

(94)

Site JJJ

0.000

0.550

100

0.000

0.550

100

0.000

0.550

100

Example 147. Report 231: Cells by dominant distance range

19.4.2

Distance Ranges on BTS Hit List

The report Distance range distribution per cell (232) offers a detailed distribution of occurrences to distance ranges and power classes. The output is typically very long and therefore you should run it for a limited area only. BSC:ABC_BSC_3

BTS:LKGG1 (108)

BCF:005A (36)

Distance upper range (km)

Share in min

max

ave

range power

power

power

(%) (dBm)

(dBm)

(dBm)

-------- --------- ------- ------- ------1.100

59.48

13

33

25

2.200

18.92

13

33

27

3.300

6.72

19

33

29

4.400

4.03

25

33

24

5.500

4.39

27

33

23 26

8.250

3.93

31

241

11.000

0.02

33

33

5

16.500

0.16

33

33

11

22.000

2.24

33

33

18


NTC TAN 0935/2.3 en


174


34.650

0.11

BSC:ABC_BSC_3

33

33

BTS:LKGG2 (111)

11 BCF:005B (37)

Distance upper range

Share in min

max

ave

range power

power

power

(%) (dBm)

(dBm)

(dBm)

(km)

-------- --------- ------- ------- ------1.100

45.45

13

33

26

2.200

6.62

17

33

24

3.300

7.69

15

33

25

4.400

3.33

29

33

18

5.500

5.03

33

33

11

8.250

18.65

23

33

26

11.000

2.59

31

33

19

16.500

10.50

29

33

10

22.000

0.13

33

33

7

34.650

0.00

--

--

--

BSC:ABC_BSC_3

BTS:WTCG2 (92)

BCF:109 (31)

Example 148. Report 232: Distance range distribution per cell

19.4.3

Distance Range Distribution on BTS Level

The report Cell analyser (216) provides you with the distribution of measurements in distance ranges and power classes. Distance upper

min

max

ave

range

Freq of Share

power

power

power

(km)

reports (%)

(dBm)

(dBm)

(dBm)

-------- -------- ------ ------ ------ -----1.100

17478

39.4

13

33

25

2.200

3061

6.9

17

33

31

3.300

12007

27.1

13

33

32

4.400

11548

26.0

13

33

32

5.500

247

0.6

31

33

31

8.250

0

0.0

-1

0

0

11.000

0

0.0

-1

0

0

16.500

0

0.0

-1

0

0

22.000

0

0.0

-1

0

0

34.650

0

0.0

-1

0

0

Example 149. Distance range distribution on the BTS level as shown in report 216, Cell analyser.

The report Cell doctor (213) shows you the percentage distribution of measurements in distance ranges and power classes in chronological order. Normally the measurement is set for the 24-hour or 12-hour reporting interval due to heavy load on the NMS/2000 and therefore the t ime resolution is usually only slightly better than in the report Cell analyser (216).

19.5 Handover Cause BSS Network Doctor provides a set of reports for investigating handover cause at various network levels. Document number/Issue

NTC TAN 0935/2.3 en


175


19.5.1

Handover Cause on Area Level

For handover causes on the area level, run the report Network benchmark statistics (204). Causes: UL quality......... ................ ............/c4 023

36546

(

4.05 %)

UL level........... ................ ............/c4 024

49809

(

5.52 %)

DL quality......... ................ ............/c4 025

16425

(

1.82 %)

DL level........... ................ ............/c4 026

25563

(

2.83 %)

Distance ............... ................ ......./c4027

0

(

0.00 %)

MSC invocation (traffic reason) .............../ c4028

0

(

0.00 %)

UL interference ................ .............../ c4029

26546

(

2.94 %)

DL interference ................ .............../ c4030

73166

(

8.11 %)

Umbrella ............... ................ ......./c4031

0

(

0.00 %)

Pbdgt ................ ............... ........../c4032

147075

(

16.30 %)

OMC (forced by user) .............. ............/c4 033

0

(

0.00 %)

Directed retry .............. ................ ../c4079

0

(

0.00 %)

Pre-emption ............... ............... ...../c4086

0

(

0.00 %)

Rapid field drop ............... .............../ c4087

0

(

0.00 %)

Low distance .............. ............... ...../c4088

0

(

0.00 %)

Bad CI ............... ............... ........../c4089

65618

(

7.27 %)

Good CI .............. ............... ........../c4090

461759

(

51.16 %)

Slow moving MS .............. ................ ../c4091

0

(

0.00 %)

MS slow speed ............... ................ ../c4105

0

(

0.00 %)

MS high speed ............... ................ ../c4106

0

(

0.00 %)


Example 150. Area level data on handover causes in report 204, Network benchmark statistics.

19.5.2

Handover Cause on BTS Hit List

For handover causes on the BTS Hit List, run the report HO attempt cause distribution by cells (154). = =

HO ATTEMPT CAUSE DISTRIBUTION BY CELLS

= =

Network:

PLMN

=

Area:

All BTSs selected

=

Period:

from 19980520 to 19980520

=

Sorting:

by Nbr of HO

=

Special terms:

= =============================================================================== The cells are listed in the order of selected cause. In all columns the value of zero means that no handovers have occurred. Percentage distribution of HO attempts by causes are shown for each cell: UL qua

/c4023

Uplink quality

UL lev

/c4024

Uplink level

DL qua

/c4025

Downlink quality

DL lev

/c4026

Downlink level

Dis

/c4027

Distance


NTC TAN 0935/2.3 en


176


MSC inv

/c4028

MSC invocation (traffic reason)

UL itf

/c4029

Uplink interference

DL itf

/c4030

Downlink interference

Umbr

/c4031

Umbrella

Pbgt

/c4032

Power Budget

OMC

/c4033

Operation and maintenance (forced by user)

DR

/c4079

Direct retry

Pre emp

/c4086

Pre-emption (S3)

Fld drp

/c4087

Radpid field drop (S4)

Low dis

/c4088

Low distance (S4)

Bad CI

/c4089

Bad C/I ratio (S4)

Good CI

/c4090

Good C/I ratio (S4)

Slow Mov MS

/c4091

Slow Moving MS (S5)

MS slow spee

/c4105

Slow speed of MS (S6)

MS high spee

/c4106

High speed of MS (S6)

Nbr of HO att

/ho_13b

Number of HO attemps

The numbers are counter references used in Nokia documents. Measurement used: p_nbsc_ho

=============================================================================== Cells by HO cause between 19980520 and 19980520

BTS NAME

UL

DL

***

***

MS Dist

CI

qua

qua

***

lev

lev

high MSC

Pre

Fld

spee

***

Slow ***

Bad

Mov

slow

BCF NAME

itf

itf

low

Umbr PBGT DR

emp

drp

Good MS

high Nbr of

BSC (BTS id)

(%)

(%)

(%)

OMC( (%)

(%)

(%)

(%)

(%)

(%)

(%)

HO att

---------------- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- -----HER3CG3007 HERMIA003 BSC3(7) HER3CG3008 HERMIA003 BSC3(8) SANDPD1019 SANDPD010 BSC1(19)

1

19

0

0

26

11

0

0

1

16

24

0

0

0

0

0

0

0

532

0

0

1

19

0

0

18

22

0

0

2

10

28

0

0

0

0

0

0

0

523

0

0

6

13

0

0

59

7

0

0

2

9

3

0

0

0

0

0

0

0

316

0

0

Example 151. Report 154: HO attempt cause distribution by cells

19.5.3

Handover Cause, BTS Level

To obtain the averages for handover causes over the whole period and the busy hour and for the share of each cause, run the report Cell analyser (216). HANDOVER CAUSES: ================ .

Whole

TCH

.

period

busy hour

.

average

average

.

=======

=========


NTC TAN 0935/2.3 en


177


. Number of all ho attempts .............. ...../ho_13

5.92

5.00

. Cause: .

UL quality ............... ................ /c4023

0.00 %

0.00 %

.

DL quality ............... ................ /c4025

1.30 %

0.00 %

.

UL level ............... ............... .../c4024

6.50 %

0.00 %

.

DL level ............... ............... .../c4026

0.00 %

0.00 %

.

UL interference ................ ........../c402 9

0.00 %

0.00 %

.

DL interference ................ ........../c402 9

2.60 %

0.00 %

.

Distance ............... ............... .../c4027

0.00 %

0.00 %

.

MSC invocation (traffic reason .........../c4 028

0.00 %

0.00 %

.

Umbrella ............... ............... .../c4031

0.00 %

0.00 %

.

Power budget ................ ............./c4 032

89.66 %

100.00 %

.

OMC (forced by user) ................ ...../c4033

0.00 %

0.00 %

.

Directed retry .............. ............./c4 079

0.00 %

0.00 %

.

Pre-emption .............. ................ /c4086

0.00 %

0.00 %

.

Field drop ............... ................ /c4087

0.00 %

0.00 %

.

Low distance ................ ............./c4 088

0.00 %

0.00 %

.

Bad C/I ................ ............... .../c4089

0.00 %

0.00 %

.

Good C/I ............... ............... .../c4090

0.00 %

0.00 %

.

Slow Moving MS............ ................ /c4091

0.00 %

0.00 %

.

MS slow speed........... ............... .../c4105

0.00 %

0.00 %

.

MS high speed........... ............... .../c4106

0.00 %

0.00 %

Example 152. BTS level data on handover cause in report 216, Cell analyser.

For hourly handover cause counts, run the report Cell doctor (213). =

BTS -

=

HO MEASUREMENT

HANDOVER CAUSE

=

BSC1

=

bts id:2

name:SITE_A1002

from 19980504 to 19980504

=============================================================================== UL qua

4023

Uplink quality

DL qua

4025

Downlink quality

UL lev

4024

Uplink level

DL lev

4026

Downlink level

Dis

4027

Distance

MSC inv

4028

MSC invocation (traffic reason)

UL if

4029

Uplink interference

DL if

4030

Downlink interference

Um

4031

Umbrella

Pb

4032

Power Budget

OM

4033

Operation and maintenance (forced by user)

Ch ad

4034

Channel administration (NOT USED)

Tf

4035

Traffic (NOT USED)

DR

4079

Direct retry (old cell side)

Pre-empt

4086

Pre-emption (old cell side)

dd hh

UL

DL

UL

qua

qua

lev

DL lev Dis

MSC

UL

DL

inv

if

if

Ch Um

Pb

OM

ad

Pre Tf

DR empt

-- -- ----- ---- ---- ---- --- ---- ----- ----- --- ----- --- --- --- ---- ---04 12

0

0

0

0

0

0

0

0

0

1

0

0

0

0

0

=============================================================================== = =


NTC TAN 0935/2.3 en

BTS -

HO MEASUREMENT

HANDOVER CAUSE (CONT.) AND OTHER HO COUNTERS


178


=

BSC1

=

bts id:2

name:SITE_A1002

from 19980504 to 19980504

=============================================================================== Field drop

4087

Rapid field drop

Low dist

4088

Low distance

Bad CI

4089

Bad C/I ratio on super-reuse frequency

Good CI

4090

Good C/I ratio on super-reuse frequency

Slow MS

4091

Handover due to the slow moving MS in Macro. (S5)

MS slow speed

4105

Handover due to the MS slow speed. (S6)

MS high speed

4106

Handover due to the MS high speed. (S6)

Adj ID Error

4100

Adjacent cell ID error when there is wrong

.

.

BSS radio network configuration database. (S5)

SCP

4099

Handover attemps cause by the changing of

.

dd hh

A-interfaces circuit type. (S5)

Field

Low

Bad

drop

dist

CI

Good Slow CI

MS

MS

Adj

slow

high

ID

MS speed speed Error

SCP

-- -- ----- ----- ----- ----- ---- ----- ----- ----- ---04 12

0

0

0

0

0

0

0

0

0

Example 153. Hourly handover cause counts in report 213, Cell doctor.

19.6 BSC Clear Codes Clear code measurements take place on the BSC level.

19.6.1

BSC Clear Codes on Network Level

For BSC clear codes on the Network level, run the report Clear code statistics (220). = =

CLEAR CODE STATISTICS

= =

Network:

PLMN

=

BSC:

all BSC

=

Period:

from 19970819 to 19970830

= =============================================================================== This report displays for the selected BSC - The number of calls per a clear code counter - The number of calls per phase and clear code. Running this report takes a moment. Wait please. =============================================================================== = =

Clear Codes from 19970819 to 19970830

=============================================================================== This report gives the sums for each clear code over the network. Please refer to the NMS/2000 database description if the counter description is missing.


NTC TAN 0935/2.3 en


179


Measurement used: p_nbsc_cc, p_nbsc_cc_pm ===============================================================================

Counter Description

Nbr of

Share

calls

%

------- ------------------------------ ---------- -------1 3 Internal inter HO failures 4 Internal intra HO failures

0.000 0.018

11856

0.007

5 Call failures

557481

0.340

6 Setup failures

488470

0.298

7 Dropped calls

110702

0.067

8 TCH fails 11 Ext.HO source succ.

614018

0.374

1206294

0.735

12 Ext.HO target succ.

1206090

0.735

13 Int. inter HO succ.

7908879

4.819

14 Int. intra HO succ.

27 29808

1323225

0.806

15 Call succ

27172019

16.556

16 Setup succ

27096737

16.511

9058877

5.520

18 TCH seizures

21901001

13.345

25 Location update attempts

12134240

7.394

26 Location updates

11998525

7.311

17 Conversation started

28 FACCH emerg.call 35 Emergency call attempts 36 Re-establishment attempts

2

0.000

5498

0.003

40057

0.024

37 Answers to paging attempts

3451560

2.103

38 MO speech call attempts

8717360

5.312

39 Other procedure attempts

2266508

1.381

41 Basic emerg.call

4883

0.003

43 Basic answer to paging

3324202

2.026

44 Basic MO speech call

8385665

5.110

2984

0.002

2265780

1.381

461

0.000

45 Basic MO data call 46 Basic other procedure 47 59 Inc. ext. HO directed retry 60 Inc.ext.HO, unexpected 74 Ext.inc.HO, DR 75 Ext.inc.HO unexpected 81 Ext.outg.HO, DL Rx lev

1971

0.001

1187546

0.724

2004

0.001

1204086

0.734

151545

0.092

82 Ext.outg.HO, UL Rx lev

248105

0.151

83 Ext.outg.HO, DL Rx qual

185222

0.113

84 Ext.outg.HO, UL Rx qual

83021

0.051

85 Ext.outg HO, DL interference

95709

0.058

86 Ext.outg.HO, UL interference

12159

0.007

426189

0.260

289

0.000

17

0.000

91 Ext.outg.HO, DR

1955

0.001

95

2083

0.001

101 Int HO DL Rx Lev succ

941854

0.574

102 Int HO UL Rx Lev succ

1473756

0.898

103 Int HO DL Rx Qual succ

787665

0.480

104 Int HO UL Rx Qual succ

424677

0.259

Nbr of

Share

calls

%

88 Ext.outg.HO, pbgt 89 Ext.outg.HO, umbrella 90 Ext.outg.HO, forced

Counter Description

------- ------------------------------ ---------- --------


NTC TAN 0935/2.3 en


180


105 Int HO DL Interf succ

505831

0.308

106 Int HO UL Interf succ 108 Int HO PBGT succ

88461

0.054

3191118

1.944

35500

0.022

166

0.000

109 Int HO Umbrella succ 110 Int HO Forced succ 111 Int HO DR succ

18786

0.011

115

2329

0.001

117

382776

0.233

118

55960

0.034

121 Int HO DL interference succ

595457

0.363

122 Int HO UL interference succ

594824

0.362

124

5149

0.003

125

102789

0.063

126

24958

0.015

=============================================================================== =

Phases and Clear Codes

=

from 19970819 to 19970830

=============================================================================== This report gives the sums for pair of phase and clear code over the network. Measurement used: p_nbsc_cc Call Phase

Call phase (see Appendix E of NMS dbase description)

Clear code id

BSC clear code identification

Measurement needed: p_nbsc_cc. ===============================================================================

Call Call

Clear

phase phase

Code

code descr

id

Count

----- ------------------------- ----- --------1 Paging/initial MS

2 MM-signalling


NTC TAN 0935/2.3 en

0

1

2

2

4

2

7

2

12

11

14

110

17

18

21

911307

40

32976

42

2

44

676

48

35810

52

29

0

14

2

15

3

74

4

4

7

2

17

42061

18

4110

20

48708

21

7

27

21

34

52929

36

404


181


39

3 Basic asignment

4

42

1

43

34

50

6

86

207

87

66177

88

468

89

5

135

9

141

11

185

1

2

1

3

2

4

1

6

56796

7

2

12

13

14

28

17

42

18

67

20

35

21

22180

Example 154. Report 220: Clear code statistics

19.6.2

BSC Clear Codes on BSC Level

The BSC doctor (212) report is similar to the report above.

19.7 Troubleshooting Normally the troubleshooting is initiated by an alarm which then can be used for diagnostics. Yet, there are many abnormal situations which do not trigger an alarm. To spot the BTSs suspected, BSS Network Doctor provides a variety of BTS hit list reports. Following is a list of some of the more important ones: •

Cells by call success ratio (250)

to change the focus from SDCCH to TCH and from access to success using different sorting keys. See Call Success for a model. •

Cells having high TCH drop call ratio (163)

to spot TCH drop problems and to see directly the distribution to failure types. For a model report, see Quality of the Radio Network Plan. •

UL and DL quality and UL interference per TRX, 24-hour/10-day breakdowns (196) and UL and DL quality per TRX (197)

to spot problems in UL or DL quality per TRX. See Reports Based on RX Quality for model reports.


NTC TAN 0935/2.3 en


182


•

Cells having UL interference, 24-hour/10-day breakdowns (190)

For a model report, see Transmission. •

Adjacencies having high HO failure ratio (153)

A model report is shown under Handover Failure Ratio on Adjacency Hit List Level. •

SDCCH drop ratio per cell (166)

to spot SDCCH drop problems and to see directly the distribution to failure types. For a model report, see Quality of the Radio Network Plan. •

Cells having most delete indications (202)

to spot access grant (AG) buffer overflow. You can also use the following reports: •

Cells having SMS establishment failures (132)

•

Cells having RACH rejections (134)

•

Cells having high HO attempts/call ratio (157)

•

Transcoder failures (164)

•

Cells having high drop call count in handovers (167)

•

Low traffic cell check-up (183)

In the Low traffic cell check-up (183) report the cells are analysed to find out the number of hours when the following condition is fulfilled: •

(SDCCH_SEIZ_ATT=0) OR

•

(SDCCH_ASSIGN=0) OR

•

(TCH_HO_SEIZ=0 AND TCH_NORM_SEIZ>0) OR

•

(TCH_NORM_SEIZ=0 AND TCH_HO_SEIZ>0)

The condition means that the hour is counted if there are no SDCCH seizure attempts or assignments or there are only HO bids or only call bids. If there are many hours reported for a cell and the bid amounts are high in the column with non-zero value, the case should be investigated using BSS Network Doctor, for example. A barred cell, for instance, gives zeros for all supervised counters. Low traffic cells between 19970201 and 19970202 in PLMN network

Hours SDCCH

BSC Name


NTC TAN 0935/2.3 en

BCF Name

seiz

TCH SDCCH

TCH


norm

TCH

with BCF

HO cond. ADM

183


(BTS id)

BTS Name

att assign

req

seiz

seiz

true ST

----------------- --------------- ------ ------ ------ ------ ------ ----- ---BSC_XXXXX

200

(37)

XMAWW

BSC_XXXXX

201

(47)

XRAQQ

27

27

15

15

0

40 U

1

1

125

1

124

40 U

Example 155. Report 183: Low traffic cell check-up

The Transcoder failures (164) report shows the sums of failures counted over the given time period. TC

TC

flrs

flrs

in HO

in HO

on

TCH

TCH

BSC

BTS name

BTS

on

norm

HO

(BTS id)

BCF name

NBR flrs old TCH new TCH

seiz

seiz

TC

------------- ----------------------- ---- ---- ------- ------- ------ -----BSC_XXXXX

TTTMM

(3)

028

BSC_XXXXX

QQQWW

(10)

032

BSC_XXXXX

PPPWW

(19)

046

BSC_XXXXX

SSCMM

(6)

029

BSC_XXXXX

DVPWW

(60)

086A

3

1

0

0

430

432

10

1

0

0

1239

800

19

1

0

0

1082

950

6

1

0

0

873

1098

60

1

0

0

871

715

Example 156. Report 164: Transcoder failures

The Cells having RACH rejections (134) report gives the following figures sorted by the selected column for all cells meeting the thresholds: •

Rejected due to distance

•

Illegal establishment cause Cells having RACH rejections between 19970829 and 19970829

BTS BCF BSC (BTSid)

Illegal

Rejected

est. cause due to distance

--------------- ---------- --------------SLCG1

0

12

0

4

028 XSD_BSC_1 (1) SLCG2 028 XSD_BSC_1 (2)


NTC TAN 0935/2.3 en


184


SLCG3

0

4

028 XSD_BSC_1 (3)

Example 157. Report 134: Cells having RACH rejections

The Cells having high HO attempts/call ratio (157) report shows for each cell: •

HO/calls ratio (%)

•

Number of handovers

•

Number of calls Cells having highest HO attempts/call ratio between 19970201 and 19970202

HO/Calls

BSC

BCF Name

Number of Number of Ratio

(BTS id)

BTS name

Handovers

Calls (%)

--------------- ------------------ --------- --------- -------BSC_XXXXX

XRAQQ

(47)

201

BSC_XXXXX

CTNWW

(29)

218

BSC_XXXXX

PPPWW

(45)

108A

BSC_XXXXX

PPPQQ

(48)

108B

BSC_XXXXX

SSCMM

(6)

029

BSC_XXXXX

CDCMM

(33)

111

BSC_XXXXX

ABCMM

(42)

078C

BSC_XXXXX

TTTWW

(1)

028

BSC_XXXXX

ZZZWW

(13)

038

BSC_XXXXX

TTTMM

(3)

028

149

29

513.8

183

107

171.0

907

599

151.4

920

720

127.8

1098

873

125.8

125

105

119.0

1083

939

115.3

1304

1250

104.3

523

510

102.5

432

430

100.5

Example 158. Report 157: Cells having high HO attempts/call ratio

The Cells having high drop call count in handovers (167) report lists all cells having drop calls in handovers more than the given threshold. The distribution of drop calls is given for each cell.


NTC TAN 0935/2.3 en


185


Cells having high drop call count in intra BSC handovers between 19970201 and 19970202 Intra BSC

BTS NAME

HO

BSC i

BSC o

BCF NAME

att

HO DC

HO DC

Total

cell intra BSC HO DC

HO DC

----------- ------------------------ ------- ------- ------- ------- --------BSC_XXXXX

SSCQQ

(5)

029

BSC_XXXXX

SSCWW

(4)

029

BSC_XXXXX

SSCMM

(6)

029

BSC_XXXXX

LKPWW

(7)

030

BSC_XXXXX

LKPMM

(9)

030

2142

8

17

2

27

1888

9

9

0

18

2051

9

5

3

17

1754

9

5

0

14

2593

5

7

2

14

Example 159. Report 167: Cells having high drop call count in handovers

The Cells having SMS establishment failures (132) report shows cells having SMS establishment failures over a given period. Cells having SMS establishment failures between 19970201 and 19970210 Nbr of SMS flr BSC

BCF name

SMS est.

BTS id

BTS name

attempts

%

SMS flr

Tot

% SMS flr

on TCH on SDCCH

%

--------------- --------------------- -------- ------- -------- ------BSC_EAST1 (7) BSC_EAST1 (8) BSC_EAST1 (9)

LKPWW

236

.00

3.13

1.69

398

.90

.00

.50

505

.41

.00

.20

030 LKPQQ 030 LKPMM 030

Example 160. Report 132: Cells having SMS establishment failures

19.8 Dual Band For the average distribution of single and dual band MS users, run the report Network Benchmark statistics (204). TCH dual band ============= All % is in ratio to total sum. Seizures by single band MS ............... .....c59002


NTC TAN 0935/2.3 en


na

(

na %)

186


Seizures by dual band MS ............... .......c59003

na

(

na %)

Call time by single band MS (minutes)..... ./trf_43/60

na

(

na %)

Call time by dual band MS (minutes)..... .../trf_44/60

na

(

na %)

All % is in ratio to total sum.

Example 161. Distribution of single and dual band MS users in report 204, Network Benchmark statistics

For the detailed BTS profile, run the report Cell Doctor (213). TCH single band subsc

DD HR

TCH dual band

TCH

subsc single

TCH dual

hold

hold

band

band

time

time

subsc

subsc

(sec) (sec)

seiz

seiz

-- -- ------ ------ ------ -----04 10

271

0

1

0

04 11

54

0

3

0

04 12

1352

0

2

0

04 13

37

0

3

0

04 15

135

0

5

0

Example 162. Single/dual band profile in report 213, Cell doctor.


NTC TAN 0935/2.3 en


187


20

BENCHMARK AND ANALYSIS BSS Network Doctor provides several reports that give a cross-section of key performance indicators from a large number of measurement counters and formulas: •


•


•

Performance profiles for area, 24-hour/10-day breakdowns (207)

•

Cell doctor (213)

•

Cell analyser (216)

•

Base station site check (221)

Sample extracts of these reports are shown in connection with individual performance indicators all over this document. Warning:

Because of the load caused on the NMS/2000 we recommend you not to run these reports for a large area when the user load on the NMS/2000 is high. It is a good idea to set the reports run from cronjob for periodic generation.

20.1 Performance statistics (benchmark) (200) You can select this report to show data from the following areas: •

object information

•

basic parameter settings

•

daily performance statistics

•

adjancency check

This report is meant primarily for the area level. If you use it on the BTS level, some formulas may not be exactly correct. Use report 216 for BTS. Note that the values for the last day may not be full 24-hour values as for the rest of the days. Note:

You should always check that the data you are analysing is consistent.


NTC TAN 0935/2.3 en


188


20.2 Network benchmark statistics (204) This report provides versatile information about the selected BTS area. •

objects

•

key parameters

•

Key Performance Indicators

This report is meant primarily for the area level. If you use it on the BTS level, some formulas may not be exactly correct. Use report 216 for BTS. Rx Quality and Rx Level measurements are usually run with a measurement period longer than 60 minutes. Therefore applying Busy Period over them may not succeed and no results are shown.

20.3 Performance profiles for area, 24-hour/10-day breakdowns (207) This report provides 10-day profiles of the indicators listed below. •

SDCCH availability

•

SDCCH usage

•

TCH availability

•

TCH usage

•

TCH traffic

•

SDCCH access probability

•

SDCCH success ratio

•

TCH access probability

•

TCH success ratio

20.4 Quality survey (800) This report provides a set of KPIs that usually are used for network follow-up. You can find a more detailed set of KPIs in the benchmark report 204. Number of cells......... ................ ...............:

41

Call attempts (c1009)........ ................ ..........:

274053

Handover attempts (ho_13e)...... ................ .......:

902507

TRAFFIC ======= Average TCH traffic/cell (averaged trf_1) .............:


NTC TAN 0935/2.3 en


3.78 Erl

189


Average SDCCH traffic/cell (averaged trf_12b)........ ..:

0.68 Erl

RESOURCE AVAILABILITY ===================== TCH availability (ava_1a)....... ................ .......:

91.42 %

SDCCH availability (ava_4)......... ............... .....:

89.90 %

CALL SUCCESS RATE ================= TCH Success Rate (csf_4p)....... ................ .......:

97.96 %

SDCCH Success Rate (csf_2f)........ ............... .....:

96.05 %

QUALITY ======= Uplink quality (class 0 - 5)............ ...............:

97.08 %

Downlink quality (class 0 - 5)............ .............:

98.44 %

BLOCKING ======== TCH Blocking (blck_8c)..... ............... .............:

1.76 %

.

Number of cells with blocking <= 2%............ .....:

37

.

Number of cells with blocking 2 - 5%.............. ..:

2

.

Number of cells with blocking 5 - 10%............. ..:

2

.

Number of cells with blocking > 10%............ .....:

SDCCH Blocking (blck_5a)..... ................ ..........:

0 0.36 %

HANDOVERS ========= Unsuccessful handovers due to lack of resources (hfr_55):

7.56 %

Failed handovers (hfr_54a)...... ................ ........:

2.30 %

TCH DROPPED CALLS ================= Dropped call rate (dcr_3f)...... ................ ........:

2.04 %

Example 163. Report 800: Quality survey

20.5 Cell doctor (213) This report is used to see the details of a BTS on a periodical basis for all counters and also the alarms and parameters across the selected period. Use this information to correlate the events and to make the diagnosis.

20.6 Cell analyser (216) This report shows detailed and versatile information about a cell in relation to its behaviour. This is the prime report for troubleshooting a cell. The output can be limited to a part of the report: 1.

Configuration of the BTS


NTC TAN 0935/2.3 en


190


2.

Performance of the BTS

3.

The following 10-day/24-hour charts are produced for the selected BTS:

4.

•

RACH load (rach_3)

•

SDCCH to TCH access success ratio (csf_2g)

•

Average available TCH (ava_2a)

•

Peak busy TCH (trf_19)

•

TCH traffic (trf_12a)

•

TCH call blocking (blck_8b)

•

SDCCH congestion (cngt_2)

•

BTS UL (idle TCH) Interference (itf_1)

•

TRX Interference (itf_4)

•

UL calls in q0-q5 (ulq_2)

•

DL calls in q0-q5 (dlq_2)

•

TCH drop-out ratio (dcr_4c)

•

HO+call seizures on TCH

•

HO seizures on TCH

•

Call seizures on TCH

•

Paging capacity

The following checks are executed for the selected BTS: •

Adjacencies to cells with different LAC (LU affecting)

•

Non-symmetrical adjacencies (drop call affecting)

•

Adjacency discrepancies (HO failure affecting)

•

Adjacency synchronisation

•

Adjacencies with HO failure ratio % exceeding 10%

20.7 Base station site check (221) This report allows you to make a quick health check of all cells under the selected BCF. It displays a set of KPIs together with information on alarms, configuration and the administrative state. bts_1


NTC TAN 0935/2.3 en

bts_2

bts_3


191


------------------------------ --------------- --------------- --------------BTS name .............

KILO1011

BTS id ...............

(11)

KILO1012 (12)

KILO1013 (13)

FACCH call setups...../c1043

0

0

0

Normal Calls........../c10 09

275

82

29

Call Time............./tr f_32

543 min

120 min

42 min

Handovers: . TCH-TCH Out Succ..../ho_46

41

34

23

. TCH-TCH In Succ...../ho_47

38

37

23

. TCH-TCH Cell Succ.../c4073

0

0

0

. DR Out Succ........./dr_3

0

0

0

. DR In Succ........../dr_4

0

0

0

Call Success: . SDCCH Access......../cs f_1a

100.0 %

100.0 %

100.0 %

. SDCCH Success......./cs f_2a

99.9 %

100.0 %

100.0 %

. TCH Access........../cs f_3k

100.0 %

100.0 %

100.0 %

. TCH Success........./cs f_4r

99.7 %

100.0 %

100.0 %

0.0 %

0.0 %

0.0 %

UL Interference...... ./itf_1

BCF Alarms **********

Alarm

Alarm

id Alarm name (severity)

count

----- ---------------------------------------- ----8066 ALARM INDICATION SIGNAL (AIS) RECEIVED (

2

**) 8099 BIT ERROR RATE (BER) > 10E-3 (**)

4

8112 FREQUENCY ERROR (**)

1

8179 FAR-END ALARM (*)

10

BTS and TRX Alarms ****************** Alarm BTS name (id)

obj

Alarm id Alarm name (severity)

Alarm count

--------------- ------- ----- ---------------------------------------- ----KILO1011 (11)

KILO1012 (12)

KILO1013 (13)


NTC TAN 0935/2.3 en

TRX (1)

7538 SIGNALLING ERROR IN ABIS INTERFACE (**)

2

TRX (2)


2

TRX (3)


2

TRX (4)


2

TRX (5)


2

TRX (6)


2


192


TRX quality and traffic ***********************

TRX BTS name (BTS id)

UL

DL

Call

Avg

q0-5

q0-5

time

Interf

TRX (%)

id

freq ulq_2

(%)

(min)

band

dlq_2

trf_32a

itf_4

-------------------- ---------- ----- ------ ------ --------- -----KILO1011 (11) KILO1012 (12) KILO1013 (13)

1

594

99.8

100.0

231

1.0

2

773

99.8

100.0

304

1.0

3

771

99.6

100.0

52

1.0

4

604

99.9

99.8

65

1.0

5

775

99.9

100.0

27

1.0

6

599

99.8

100.0

14

1.0

Configuration data ****************** BCF state: . Administrative state...... Unlocked . Alarm state............... No active alm BCF software running: . Package name ............. BTS_S301 . Status ................... BACK-UP

BTS

State

Alarms

BCC Barring

--------------- ---------- --------------- ---- --------------KILO1011

Unlocked

No active alm

1 Not barred

KILO1012

Unlocked

No active alm

1 Not barred

KILO1013

Unlocked

No active alm

1 Not barred

BTS (TRX)

State

Alarms

CHN FRQ id

CHN

CHN

state

type

--------------- ---------- --------------- ----- ----- ---------- -------KILO1011 (1)

KILO1011 (2)

Unlocked

Unlocked

No active alm

No active alm

594 0

Unlocked

MBCCH

1

Unlocked

SDCCB

2

Unlocked

TCHF

3

Unlocked

TCHF

4

Unlocked

TCHF

5

Unlocked

TCHF

6

Unlocked

TCHF

7

Unlocked

TCHF

773 0

Unlocked

TCHF

1

Unlocked

TCHF

2

Unlocked

TCHF

3

Unlocked

TCHF

4

Unlocked

TCHF

5

Unlocked

TCHF

6

Unlocked

TCHF

7

Unlocked

TCHF

Example 164. Report 221: Base station site check


NTC TAN 0935/2.3 en


193

INDEX Numerics

B

10-day/24-hour profiles 19 Cell analyser (216) 36 for a Maintenance Region (207) 35 60-minute reporting interval 16, 38

BCCH allocation list 13, 46 before using the reports 37 benchmark and analysis 35, 188 BSC clear codes 179 BSC level alarm types and counts 153 availability of transceivers 121 clear code measurements 179 hourly traffic 102 location update success 93 TCH drop call ratio 81 BSS measurements 43 BSS Network Doctor 10 reducing excessive use 16 report menus 28 using 20 BSS transmission availability and quality 35 BTS group 13, 37, 53 BTS hit lists availability of time slots 122 distance ranges 174 handover cause 176 handover failure ratio 88 link balance 169 reports 182 SDCCH congestion and blocking 95 SDCCH drop ratio 77 TCH congestion and blocking 99 TCH drop call ratio 82 traffic 105 uplink interference 126 BTS object instance 37 busy hour handover cause on BTS level 177 handover failure ratio on BTS level 90 IUO counters on BTS level 134 IUO traffic on area level 132 report 182 100 report 216, Cell analyser 36 SDCCH and TCH availability 123 SDCCH and TCH traffic 105 SDCCH congestion and blocking 96 TCH congestion and blocking 101 TCH drop call ratio on BTS level 83 traffic on BTS level 106

A

abbreviations 12 Abis failures 76 active measurements in the BSC 38 active observations 47 adjacency discrepancies 56 alarm filtering and acknowledging 49 alarms 152 2567, BCCH Missing 115 7705, LAPD Link Failure 115 setting the history windows 53 area level call success 112 handover cause 176 handover failure ratio 85 intelligent underlay-overlay 132 link balance 168 parameter counts 62 report 200, Performance statistics (benchmark) 75, 79, 85, 188 report 204, Network benchmark statistics 189 SDCCH and TCH availability 122 SDCCH congestion and blocking 94 SDCCH drop ratio 76 TCH congestion 98 TCH drop call ratio 79 traffic 103 uplink and downlink quality 162 uplink interference 125 availability SDCCH and TCH 122 time slots 121 transceivers 121 transmission objects 119 averages report 204, Network benchmark statistics 35, 75


NTC TAN 0935/2.3 en


194

uplink interference on BTS level 129 C

call success 35, 112, 182, 192 cell coverage 173 cell dimensioning 94 checking active measurements 39 adjacency plan 66 administrative states 73 blocked or filtered alarms 49 BTS object instance 37 data consistency 55 frequency plan 72 maintenance region assignments 49 parameter consistency 30 PLMN object instance 37 PLMN object name 37 CI 12, 14, 37 clear codes 14, 40, 44, 45, 179 configuration management 16, 29 adjacencies 30 cell coverage 32 checks 30 find cell 29 frequencies 31 named parameter set audit 31 network entities 31 congestion and blocking SDCCH 94 TCH 98 counter formulas 21 counters finding from reports 21 IUO 133 performance indicators 18 uplink interference 125

daily values report 200, Performance statistics (benchmark) 35, 75 data storing periods 53 database counters 21 database tables 43 defining groups by BSS Network Doctor Group Management 54 by Working Set Manager 54 distance ranges 173

NTC TAN 0935/2.3 en

E

erlang 102, 107 F

fault management 16, 29, 115 finding errors in assignments 52 formulas and counters 21 formulas finding from reports 21 performance indicators 14 frequency plan 31 further information 10 G

ghost RACH accesses 76 H

handover 33 causes 175 failure ratio 33, 85, 88 hourly cause counts 178 measurements 43 synchronisation between adjacent cells 59 history windows 53 I

D


documentation BSS Network Doctor 10 other Nokia documents 11 double BA list 131 drop call ratio 18 dtpad 10, 23 DX 200 network elements 49

identification number 23 identification numbers 020 29, 154 023 29, 155 024 29, 155 025 29, 155 027 29, 115 030 29, 115, 154 034 29, 152 035 29, 153 041 29, 157 042 29, 52


195

043 29, 044 30, 045 30, 046 30, 047 30, 050 30, 060 30, 061 30, 062 30, 063 30, 064 30, 065 30, 066 30, 067 30, 068 30, 069 30, 070 30, 071 30, 072 30, 073 30, 074 30, 075 31, 080 31, 081 31, 082 31, 089 31, 090 31, 091 31, 092 31, 093 31, 094 31, 095 31, 096 31, 097 31, 099 31, 110 31, 111 31, 120 32, 121 32, 122 32, 123 32, 124 32, 125 32, 126 32, 127 32, 130 32, 131 32, 132 33, 134 32, 135 32, 138 32, 139 32,

157 157 158 158 150 73 56 58 58 64 52 56 62 60 62 61 66 67 67, 131 70, 131 66 71 160 160 160 143 50, 141 145 145 146 146 146 146 147 148 148 72 39 42 46 47 48 131 41 40 95 121 186 184 99 99 122


NTC TAN 0935/2.3 en

150 33, 88 153 33, 89, 183 154 33, 176 157 33, 185 160 33, 80 162 33, 81 163 19, 33, 82, 182 164 33, 184 166 33, 77, 183 167 33, 185 180 33, 102 181 33, 107 182 33, 100, 105 183 33, 183 184 33, 108 185 33, 105 186 33, 108 187 33, 109 188 33, 110 189 34, 110 190 34, 126, 183 191 34, 169 195 34, 168 196 34, 164, 182 197 34, 164, 182 198 8, 34, 172 199 8, 34, 168 200 18, 35, 75, 76, 79, 85, 94, 98, 103, 122, 125, 162, 188 202 34, 183 203 35, 93 204 18, 35, 76, 79, 87, 94, 98, 163, 176, 188, 189 207 35, 104, 113, 188, 189 208 34, 170 212 35, 182 213 19, 36, 102, 166, 167, 171, 175, 178, 188, 190 215 36, 123 216 19, 36, 78, 83, 89, 96, 101, 106, 123, 129, 165, 166, 171, 175, 177, 188, 190 217 36, 85 220 35, 179 221 36, 188, 191 222 34, 103 231 32, 173 232 32, 174 250 35, 182 251 35, 114 400 34, 133 401 34, 132


196

402 34, 132 403 34, 138 404 9, 34, 139 405 34, 59, 139 407 9, 34, 140 515 35, 119 516 35, 119 517 35, 120 518 35, 116 800 8, 35, 189 interference 34, 125 from the same or adjacent frequencies 130 uplink 125 invalid number 37 IUO 34, 132 K

key performance indicators 19, 188 L

undefined adjacent cell 46, 131 MML 39, 49, 55 model reports 23, 28 monitoring cellular network quality 17 intelligent underlay-overlay 132 scopes of 18 N

named sets 160 network configuration 141 network level report 034, Alarm types and counts 152 report 220, Clear code statistics 179 NMS/2000 configuration 16 database 19, 37, 39, 42, 49, 53, 55, 129 load on 38 statistics 21 Nokia NMS release T10 10 O

LAC 13, 37 link balance 34 area level 168 breakdown on the BTS level 171 BTS hit list 169 link quality 34 locating network elements 157

object resolution 43 observations active 39 checking 47 setting the history windows 53 P

M

maintenance region 17, 49 measurement types 43 measurements BSC clear codes 179 C/I ratio 140 flow from a BSC 46 handover adjacent cell 89 how to check which are active 39 how to check which send data to the database 40 how to set 42 link balance 169 MS speed 172 power control 169 Rx level statistics 164 Rx quality 164 Rx quality and Rx level 189 setting the history windows 53 timing advance 173 Document number/Issue

NTC TAN 0935/2.3 en

performance indicators 18 performance management 16 call success 35 drop call 33 handover 33 interference 34 IUO 34 link balance 34 link quality 34 PM administration 32 SDCCH and TCH access 32 traffic and load 33 PLMN 13 PLMN object 37, 49 prerequisites for effective analysis of the network 16 for user knowledge 10


197

R

RACH 13, 76 radio network plan 21, 55 quality 75 report actions to take before using 37 automatic running of 16 format 24 front page description 16 identification numbers 23 models 23 output 24 scopes 17 report names Active BCCH missing (2567) alarms (024) 29 Active BCCH missing alarms (024) 155 Active measurements and observations (120) 32, 39 Adjacencies having high HO failure ratio (153) 33, 89, 183 Adjacencies of cells (074) 30, 66 Adjacencies to non-existing or foreign cells (065) 30, 56 Adjacency discrepancies (060) 30, 56 Adjacent cell double frequencies (069) 30, 61 Adjacent cells with the same or adjacent frequency, IUO super TRX excluded (405) 34, 59, 139 Alarm statistics (020) 29, 154 Alarm statistics by cells (023) 29 Alarm statistics per cell (023) 155 Alarm sum time by cells (025) 29 Alarm types and counts (034) 29, 152 Alarm types and counts for BSC (035) 29, 153 All base station sites (BCF) per Maintenance Region (041) 29 All base station sites per maintenance region (041) 157 All BTSs with LAC and CI (043) 29 All cells with LAC and CI (043) 157 All radio network ordered by BSC, BCF, BTS (042) 29, 52 Allocation of a named set (082) 31, 160 Availability per BSC unit (215) 36, 123 Base station site check (221) 36, 188, 191 Base station sites of a maintenance region (095) 31, 146 BCF software and hardware type statistics


NTC TAN 0935/2.3 en

(099) 31 BCF software and harware type statistics (099) 148 BSC alarm breakdown (030) 29, 115, 154 BSC doctor (212) 35, 182 BSC option statistics (089) 31, 143 BSC unit load for each BSC (184) 108 BSC unit load per hour for each BSC (184) 33 BSCs (092) 31, 145 BTS alarm sum time by cells (025) 155 BTS audit (063) 30, 64 BTS parameter survey (068) 30, 62 BTSs having undefined adjacent measurement results (125) 131 BTSs with maximum number of adjacencies (070) 30, 66 BTSs with maximum number of adjacencies between LAs (075) 71 BTSs with maximum number of adjacencies to different Location Areas (075) 31 BTSs with minimum number of adjacencies (071) 30, 67 Busy hour traffic for all BTSs (182) 33, 100, 105 C/I statistics (407) 9, 34, 140 Call distribution per LA (222) 34, 103 Call success profiles of a cell (251) 35, 114 Cell analyser (216) 19, 36, 78, 83, 89, 96, 101, 106, 123, 129, 165, 166, 171, 175, 177, 188, 190 Cell doctor (213) 19, 36, 102, 166, 167, 171, 175, 178, 188, 190 Cell location updates (187) 33, 109 Cell outage breakdown over 10 days (027) 29, 115 Cells by average traffic absorption to super TRXs (401) 34, 132 Cells by busy hour traffic absorption to super TRXs (402) 34, 132 Cells by call success ratio (250) 35, 182 Cells by DL and UL level balance (195) 34, 168 Cells by dominant distance range (231) 32, 173 Cells by dominant link balance (198) 8 Cells by dominant link balance range (198) 34, 172 Cells having bad link balance (191) 34, 169


198

Cells having high drop call count in handovers (167) 33, 185 Cells having high HO attempts/call ratio (157) 33, 185 Cells having high HO failure ratio (150) 33, 88 Cells having high TCH drop call ratio (163) 19, 33, 82, 182 Cells having high TCH raw blocking (138) 32, 99 Cells having highest RACH load (188) 33 Cells having maximum paging traffic (186) 33, 108 Cells having maximum TCH traffic (185) 33, 105 Cells having most delete indications (202) 34, 183 Cells having peak RACH load (188) 110 Cells having RACH rejections (134) 32, 184 Cells having SDCCH congestion (130) 32, 95 Cells having SMS establishment failures (132) 33, 186 Cells having TCH congestion (135) 32, 99 Cells having UL interference, 24-hour/10day breakdowns (190) 34, 126, 183 Cells having unavailable radio time slots (139) 32, 122 Cells having undefined adjacent measurement results (125) 32 Cells sorted by SDCCH or TCH holding time (189) 34, 110 Clear code statistics (220) 35, 179 Daily TCH traffic profile for a BTS (181) 33 Daily traffic profile for a BTS (181) 107 Defined, undefined and used adjacencies of a cell (072) 30, 67, 131 Distance range distribution per cell (232) 32, 174 DMR profile (515) 35, 119 DN2 profile (516) 35, 119 Drop call statistics per day in each BSC (162) 81 Find BS sites having the given character string in the name (044) 30, 157 Find cells having an adjacent cell with the given CI and LAC (046) 30, 158 Find cells having the given CI and LAC (045) 30, 158


NTC TAN 0935/2.3 en

Find cells having the given frequency (047) 30, 150 Find locked BCFs, BTSs, TRXs and channels (050) 73 Find locked TRXs, BTSs, BCFs and channels (050) 30 First and last measurement record times for each BSC (121) 32, 42 Frequency check of adjacent cells (062) 30, 58 Frequency plan (111) 31, 72 Handover attempt cause distribution by cells (154) 33, 176 Handover synchronisation (067) 30, 60 HLRs (094) 31, 146 IUO counters of a cell (400) 34, 133 IUO measurement data per BTS (404) 9, 34, 139 KPI statistics for IUO cells (403) 34, 138 Last BSS measurement record times (127) 32, 40 Link balance of an area (199) 8, 34, 168 Link balance per cell (208) 34, 170 Location Areas (096) 31 Location areas (096) 146 Location update success ratio per BSC (203) 35, 93 Low traffic cell check-up (183) 33, 183 Maintenance region audit (064) 30, 52 Maintenance regions (091) 31, 145 MSCs (093) 31, 146 Named sets used (081) 31, 160 Network benchmark statistics (204) 18, 35, 76, 79, 87, 94, 98, 163, 176, 188, 189 Network configuration summary (090) 31, 50, 141 Network performance statistics (200) 125 Non-symmetrical adjacencies (061) 30, 58 Non-unique CI and LAC (066) 30, 62 Number of named parameter sets (080) 160 Number of named parameter sets per object type (080) 31 Objects with active observations (123) 32, 47 Occurrence of frequencies (110) 31, 148 Performance profiles for area, 24-hour/10day breakdowns (207) 35, 104, 113, 188, 189 Performance statistics (benchmark) (200)


199

18, 35, 75, 76, 79, 85, 94, 98, 103, 122, 162, 188 PLMNs (097) 31, 147 Quality survey (800) 8, 35, 189 Records for a measurement type, over BSC (126) 32, 41 Records for a measurement type, over BTS area (122) 32, 46 SDCCH and TCH and BSC out HO observation statistics (217) 36 SDCCH drop ratio per cell (166) 33, 77, 183 TCH and SDCCH observation records (124) 32, 48 TCH drop call statistics by days across area (160) 33, 80 TCH drop call statistics per day in each BSC (162) 33, 81, 82 TCH traffic (erlang) per hour for each BSC (180) 33, 102 TCH, SDCCH observation statistics (217) 85 Transcoder failures (164) 33, 184 Transmission statistics (518) 35, 116 TRU profile (517) 35, 120 UL and DL quality and UL interference per TRX, 24-hour/10-day breakdowns (196) 34, 164, 182 UL and DL quality per TRX (197) 34, 164, 182 Unavailability classification per BSC (131) 32, 121 Undefined adjacent cells (073) 30, 70, 131 reporting intervals 14, 38 12 hours 42 15 or 30 minutes 38 60 minutes 42 reporting procedures 18 reports menus 28 new 8 running models by identification numbers 28 updated 8 RX-level statistics 166 S

SDCCH 13 congestion and blocking 94 drop ratio 76


NTC TAN 0935/2.3 en

SDCCH and TCH access 32 setting base station groups 53 history windows 53 measurements 42 SMS 13 SMS establishment failures 186 SQL*Plus 14, 37 T

TCH 13 congestion and blocking 98 drop call ratio 18, 79 terms and concepts 12, 13 text styles 11 time periods selection of 17 time slots 15, 121, 125 top n lists 18 Top-level User Interface 16, 39, 55 traffic 43, 94 BTS level 106 busy hours 100, 105 daily sums of 103 summarised and average 105 TCH traffic per hour (erlang) 103 traffic absorption 34 traffic and load 33 transcoder failures 81 transmission 115 troubleshooting 182 typographic conventions command line 12 text styles 11 U

UL and DL quality hourly distribution 166 UL interference 21, 53, 126 V

vi 10 W

what you need to know first 10 where to find more 10 working set 11, 17, 54


200

NOKIA_2G_BSS Network Doctor User Guide

Recommend Documents