NSS NetDoc

NSS Network Doctor

DN98614198 © Nokia Networks Oy 1 (134)Issue 1-1 en Nokia Proprietary and Confidential

NSS Network Doctor

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for theuse of Nokia Networks' customers only for the purposes of the agreement under which thedocument is submitted, and no part of it may be reproduced or transmitted in any form ormeans without the prior written permission of Nokia Networks. The document has beenprepared to be used by professional and properly trained personnel, and the customerassumes full responsibility when using it. Nokia Networks welcomes customer comments aspart of the process of continuous development and improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, orperformance of the mentioned hardware or software products cannot be considered bindingbut shall be defined in the agreement made between Nokia Networks and the customer.However, Nokia Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaNetworks will, if necessary, explain issues which may not be covered by the document.

Nokia Networks' liability for any errors in the document is limited to the documentary correctionof errors. Nokia Networks WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS INTHIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL(INCLUDING MONETARY LOSSES), that might arise from the use of this document or theinformation in it.

This document and the product it describes are considered protected by copyright according tothe applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this document may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright © Nokia Networks Oy 2001. All rights reserved.

2 (134) © Nokia Networks Oy DN98614198Nokia Proprietary and Confidential Issue 1-1en

Contents

Contents 3

List of tables 7

List of figures 8

1 About this manual 131.1 What you need to know first 131.2 Where to find more 141.3 Typographic conventions 141.3.1 Text styles 141.3.2 Command line conventions 151.4 Terms and concepts 161.4.1 Abbreviations 161.4.2 Terms 16

2 Introduction to NSS Network Doctor 192.1 Prerequisites for the effective analysis of the network 192.2 Monitoring the quality of a cellular network 202.3 Reporting procedures 202.4 Performance indicator 21

3 Using NSS Network Doctor 233.1 Navigating with reports, measurement tables, formulas and counters 24

4 User interface 274.1 Report layout 294.2 Focusing your report selection 294.3 User log 304.4 NMS database administration 314.5 Report menus 324.5.1 MSC Statistics 324.5.1.1 Administration of MSC Measurements 324.5.1.2 Load and Availability 334.5.1.3 MSC Clear Codes 334.5.1.4 Handover 334.5.1.5 VLR 334.5.1.6 Announcement 334.5.1.7 Traffic and Success 344.5.1.8 Signalling 344.5.1.9 Data Calls 354.5.1.10 Other MSC Reports 354.5.2 HLR Statistics 354.5.2.1 Administration of HLR measurements 354.5.2.2 Load and Availability 354.5.2.3 Authentication Centre 354.5.2.4 Other HLR Reports 364.5.3 NMS Database Administration 36


NSS Network Doctor

4.5.4 User Log 36

5 Actions to take before using the reports 375.1 Load on the NMS/2000 375.2 MSC & HLR measurements check-up 385.3 Setting the history windows 39

6 MSC reports 416.1 Administration of MSC measurements 416.1.1 How to see which MSC measurements send data to the database 416.1.2 How to see what network elements send data to the database 436.1.3 Measurement flow 436.2 Load and availability 446.2.1 MSC CPU and MB load (605) 446.2.2 MSC CPU and MB load profiles (614) 466.2.3 MSC availability (638) 476.2.4 MSC profiles for rejected calls (637) 486.3 Signalling 496.3.1 SS7 link load (511) 496.3.2 X25 load profile (624) 506.3.3 MAP statistics (514) 516.3.4 MTP signalling link availability (655) 516.3.5 MTP signalling link utilisation (656) 536.3.6 MTP signalling link performance (657) 556.3.7 MTP signalling point status (659) 566.3.8 MTP signalling link set and route set availability (660) 576.3.9 MTP user parts signalling traffic (662) 596.3.10 SCCP signalling point performance (664) 606.3.11 SCCP subsystem performance (665) 636.3.12 SCCP single meters (666) 656.3.13 SCCP local subsystem availability (667) 676.3.14 TCAP performance (658) 676.3.15 TCAP transactions (672) 706.3.16 PCM statistics (668) 706.3.17 LAPD error counters (669) 776.3.18 LAPD utilisation (670) 786.3.19 LAPD traffic (671) 796.4 Clear codes 806.4.1 MSC call clear codes (014) 806.4.2 MSC call clear codes, shares and change (015) 816.4.3 Clear code set per MSC (617) 826.4.4 Clear codes of destinations (626) 836.4.5 Signalling clear codes (625) 846.4.6 Trafficability statistics (622) 856.4.7 GSM observations analysis (218) 866.5 Data Calls 876.5.1 MSC call clear codes of data calls (527) 876.5.2 Data call clear code groups by number destination (528) 886.5.3 Data service unit statistics (529) 896.5.4 GBS data service statistics (530) 916.6 Handovers 93


6.6.1 Handover failure ratio (633) 936.6.2 Handover failure ratio for adjacencies (636) 946.6.3 Handover observation statistics (619) 956.7 Visitor location register 966.7.1 VLR failure profiles (632) 966.7.2 VLR subscriber profiles per LA (635) 966.7.3 VLR authentication profile (646) 976.7.4 VLR authentication statistics (650) 986.8 Announcement 996.8.1 Announcement channel statistics (621) 996.8.2 Integrated announcement device statistics (628) 1006.9 Traffic and success 1006.9.1 Traffic category statistics (620) 1006.9.2 Cell measurement statistics (627) 1026.9.3 Control unit statistics (616) 1026.10 Destinations 1036.10.1 Destinations having high failure ratio (609) 1036.10.2 Destination to destination success (613) 1056.10.3 Busy hour traffic of destinations (618) 1066.11 Circuit groups 1076.11.1 Circuit group statistics (602) 1076.11.2 Circuit group profile (649) 1086.11.3 Circuit group to destination (645) 1096.12 Subscriber facility usage 1106.12.1 Subscriber facility usage (603) 1106.13 MSC benchmark 1116.13.1 MSC network benchmark (600) 1116.14 Security 1156.14.1 MSC security counters (634) 1156.15 Echo cancellation units 1166.15.1 ECU routine test statistics (647) 1166.16 Circuit supervision 1176.16.1 Circuit supervision (648) 1176.17 IN services 1186.17.1 Gapped IN services (652) 118

7 HLR reports 1197.1 Administration of HLR measurements 1197.1.1 How to see which measurements send data to the database 1197.1.2 How to see what network elements send data to the database 1207.1.3 Measurement flow 1217.2 Load and availability 1217.2.1 HLR CPU and MB load (606) 1217.2.2 HLR CPU and MB load profiles (615) 1227.2.3 HLR availability profiles (641) 1237.3 Authentication centre 1247.3.1 AUC triplet transfer profiles (643) 1247.4 HLR service 1257.4.1 HLR basic service statistics (630) 1257.4.2 HLR supplementary service statistics (631) 1267.5 VLR subscribers 127


NSS Network Doctor

7.5.1 Subscriber profiles in VLRs (640) 1277.6 HLR security counters 1287.6.1 HLR security counters (651) 1287.7 HLR usage 1287.7.1 HLR usage statistics (629) 1287.7.2 HLR profiles (639) 1297.8 Equipment identity register 1307.8.1 EIR profile (644) 1307.8.2 EIR requests by IMEI (654) 131

Index 133


List of tables

Table 1. Text styles in this document 15

Table 2. Command line conventions 15

Table 3. Abbreviations 16

Table 4. Terms used in this document 17

Table 5. Example of history windows in the NMS/2000 database 39


NSS Network Doctor

List of figures

Figure 1. General work process 24

Figure 2. Interrelationship between reports, measurement tables, formulas andcounters 25

Figure 3. NSS Network Doctor user interface 29

Figure 4. Report 512: Log statistics 30

Figure 5. Report 513: Network Doctor use statistics 31

Figure 6. Report 607: Last MSC measurement record times 43

Figure 7. Report 601: First and last NSS measurement record times for eachMSC 43

Figure 8. Report 608: Records for a MSC measurement type 44

Figure 9. Report 605: MSC CPU and MB load 46

Figure 10. Report 614: MSC CPU and MB load profiles 47

Figure 11. Report 638: MSC availability 48

Figure 12. Report 637: MSC profiles for rejected calls 49

Figure 13. Report 511: SS7 link load 49

Figure 14. Report 624: X25 load profile 50

Figure 15. Report 514: MAP statistics, MML-based 51

Figure 16. Report 655: MTP signalling link availability 53

Figure 17. Report 656: MTP signalling link utilisation 55

Figure 18. Report 657: MTP signalling link performance 56

Figure 19. Report 659: MTP signalling point status 57

Figure 20. Report 660: MTP signalling link set and route set availability 59

Figure 21. Report 662: MTP user parts signalling traffic 60

Figure 22. Report 664: SCCP signalling point performance 63

Figure 23. Report 665: SCCP subsystem performance 65

Figure 24. Report 666: SCCP single meters 67

Figure 25. Report 667: SCCP local subsystem availability 67

Figure 26. Report 658: TCAP performance 70

Figure 27. Report 672: TCAP transactions 70

Figure 28. Report 668: PCM statistics 77


Figure 29. Report 669: LAPD error counters 78

Figure 30. Report 670: LAPD utilisation 79

Figure 31. Report 671: LAPD traffic 79

Figure 32. Report 014: MSC call clear codes 81

Figure 33. Report 015: MSC call clear codes, shares and change 82

Figure 34. Report 617: Clear code set per MSC 83

Figure 35. Report 626: Clear codes of destinations 84

Figure 36. Report 625: Signalling clear codes 85

Figure 37. Report 622: Trafficability statistics 86

Figure 38. Report 218: GSM observations analysis 87

Figure 39. Report 527: Data call clear codes 88

Figure 40. Report 528: Data call clear codes by destination 89

Figure 41. Report 529: Data service unit statistics 91

Figure 42. Report 530: GBS data service statistics 93

Figure 43. Report 633: Handover Failure Ratio 94

Figure 44. Report 636: Handover failure ratio for adjacencies 94

Figure 45. Report 619: Handover observation statistics 95

Figure 46. Report 632: VLR failure profiles 96

Figure 47. Report 635: VLR subscriber profiles per LA 97

Figure 48. Report 646: VLR authentication profile 98

Figure 49. Report 650: VLR authentication statistics 99

Figure 50. Report 621: Announcement channel statistics 99

Figure 51. Report 628: Integrated announcement device statistics 100

Figure 52. Report 620: Traffic category statistics 101

Figure 53. Report 627: Cell measurement statistics 102

Figure 54. Report 616: Control unit statistics 103

Figure 55. Report 609: Destinations having high failure ratio 105

Figure 56. Report 613: Destination to destination success 106

Figure 57. Report 618: Busy hour traffic of destinations 107

Figure 58. Report 602: Circuit group statistics 108

Figure 59. Report 649: Circuit group profile 109


NSS Network Doctor

Figure 60. Report 645: Circuit group to destination 110

Figure 61. Report 603: Subscriber facility usage 111

Figure 62. Report 600: MSC network benchmark 115

Figure 63. Report 634: MSC security counters 116

Figure 64. Report 647: ECU routine test statistics 117

Figure 65. Report 648: Circuit supervision 118

Figure 66. Report 652, Gapped IN services 118

Figure 67. Report 623: Last HLR measurement record times 120

Figure 68. Report 610: First and last NSS measurement record times for eachHLR 120

Figure 69. Report 611: Records for a HLR measurement 121

Figure 70. Report 606: HLR CPU and MB load 122

Figure 71. Report 615: HLR CPU and MB load profiles 123

Figure 72. Report 641: HLR availability profiles 123

Figure 73. Report 643: AUC triplet transfer profiles 125

Figure 74. Report 630: HLR basic service statistics 126

Figure 75. Report 631: HLR supplementary service statistics 127

Figure 76. Report 640: Subscriber profiles in VLRs 128

Figure 77. Report 651: HLR security counters 128

Figure 78. Report 629: HLR usage statistics 129

Figure 79. Report 639: HLR profiles 130

Figure 80. Report 644: EIR profile 131

Figure 81. Report 654: EIR requests by IMEI 132


Summary of changes

In this Functionality Note (FN T1694 for version 12.1 in T12)

As a result of the changes made between NSS Network Doctor software versions12.0 and 12.1, the following changes have been made into this document:

New reports:

MSC Statistics -> Data Calls menu

1. MSC call clear codes of data calls (527)

2. Data call clear code groups by number destination (528)

3. Data service unit statistics (529)

4. GBS data service statistics (530)

Updated reports:

• MSC network benchmark (600):

New M10 categories have been added and data call information is nowtaken from the traffic category measurement. New formulas have beencreated.

• Circuit group statistics (602)

A field for the minimum number of free circuits has been added.

• Last MSC measurement record times (607)

Added four new tables for data call measurements.

• Traffic category statistics (620)

New M10 categories have been added and some slight changes have beenmade to the report format.

• HLR usage statistics (629)

The average number of subscribers is obtained from the p_hlr_vlr table.

• VLR authentication profile (646)

Several new fields have been added. The report layout has changed.

• Circuit group profile (649)

A field for the minimum number of free circuits has been added.


NSS Network Doctor

In the previous Functionality Note (FN T1565 for version 12.0 in T12)

As a result of the changes made between NSS Network Doctor software versions11.1 and 11.2, the following changes have been made into this document:

New reports

• TCAP transactions (672) in the MSC Statistics -> Signalling menu.

Supported functions

There may be some minor differences between the formulas presented here andthe formulas that NSS Network Doctor is using.

This version of NSS Network Doctor makes full use of the new M8 functions.


About this manual

1 About this manualThis document explains the functional usage of the NSS Network Doctorsoftware, the emphasis being on the practical tasks. This document introduces allreports available in NSS Network Doctor by showing extracts of model reports.

The information contained in this document relates to Nokia NMS release T12and to release M10 of the Nokia MSC software. This document should not beused with any other versions of the Nokia NMS/2000 or Nokia MSC 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:

• What you need to know first

• Where to find more

• Typographic conventions

• Terms and concepts

1.1 What you need to know first

This document assumes that you are familiar with the following areas:

• 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. Anoverview of the responsibilities of the system administrator can be foundin the HP-UX System Administration Concepts.

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


NSS Network Doctor

1.2 Where to find more

When you perform the user’s tasks described in this document, you may need torefer to other documentation for further information. Below is a list of manualsthat you will find useful, as well as a brief description of the manual’s contents.

NSS Network Doctor documentation

• NSS Network Doctor, Feature Overview, DN00308755, for a briefoverview on the application

• NSS Network Doctor, System Administrator’s Guide, DN98619372, foradministrator’s tasks related to running NSS Network Doctor

• NSS Network Doctor Formulas, Reference Guide, DN98619509, forcounter formulas.

• Changes in NSS Network Doctor, DN0128043, for detailed information onthe changes in MSC releases and on how that is reflected in the NMS/2000database and NSS Network Doctor.

Other Nokia documents

• Performance Management Basic Operating Principles and Procedures,DN9784605, for a description of the formulas used in the MeasurementData Post-processing in PC application.

• Database Description for MSC/HLR Measurements, DN98619478, forinformation on NMS database counters.

• Traffic Measurement Report Formats, DN9817208.

• Clear Code List, DN987436.

1.3 Typographic conventions

The following tables present the typographic conventions which have been usedin this manual to describe different actions and restrictions.

1.3.1 Text styles

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


About this manual

1.3.2 Command line conventions

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

Table 1. Text styles in this document

Style Explanation

Initial Upper-caseLettering

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

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

Bold text User interface components

Initial Upper-caseLettering in Italics

Referenced documents

Referenced sections and chapters within a document

<bracketed text> Variable user input

Table 2. Command line conventions

Prompt As which user

# As the root user

omc>% As the omc user

& As any user


NSS Network Doctor

1.4 Terms and concepts

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

1.4.1 Abbreviations

1.4.2 Terms

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

Table 3. Abbreviations

Abbreviation Explanation

AUC Authentication Centre

BCF Base Control Function

BSC Base Station Controller

BSS Base Station Subsystem

BTS Base Transceiver Station

CI Cell Identity

CPU Central Processor Unit

HO Handover

HLR Home Location Register

LAC Location Area Code

MML Man-machine Language

MB Message Bus

MS Mobile Station

MSC Mobile Services Switching Centre

NSS Network Subsystem

OSI Open System Interconnection

PLMN Public Land Mobile Network

PM Performance Management

SQL Standard Query Language

TSL Timeslot


About this manual

Table 4. Terms used in this document

Term Explanation

Cell Identity (CI) A number which identifies a cell to thenetworks within a location area (LA).

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

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

Key Performance Indicator The performance of the network is calculatedfrom the NMS/2000 based on the NetworkElement counter information. Sometimes theplain counter as such describes an importantperformance aspect (number of calls, forexample) of the network but sometimes aformula of counters is needed (e.g. drop callratio).

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

Measurement data Data that includes both measurements andobservations. Synonym for performance data.

Measurement report A report of a specified measurement type thatis generated after every output period.

NMS/2000 A product of Nokia Networks for the operationand maintenance of cellular networks.

Performance data See measurement data.

Reporting interval The result output period of measurementswhich the user can set. The period is set asone of the measurement parameters usingMML.

SQL*Plus An interactive program for accessing thedatabase.

Timeslot (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 NokiaNMS/2000 Workstation based on windowing.


NSS Network Doctor

For other terms, refer to Glossary, DN9763965.


Introduction to NSS Network Doctor

2 Introduction to NSS Network DoctorNSS Network Doctor is a reporting package which provides effective easy-to-usetools to cover the NSS Performance Management (PM) functions of the NMS/2000.

Self-documented reports with front page description and column headersguarantee that the basic information is always where it is needed.

To install NSS Network Doctor, follow the instructions given in the NSS NetworkDoctor, System Administrator’s Guide.

NSS Network Doctor offers a menu-based user interface where the user can moveup and down the menu hierarchy. See chapter 4 (User Interface) for a list of allavailable reports.

If you need certain reports regularly, schedule the reports and execute themautomatically. For instructions on automatic running, refer to NSS NetworkDoctor, System Administrator’s Guide.

2.1 Prerequisites for the effective analysis of thenetwork

To analyse your network as efficiently as possible, ensure that:

The measurements are available

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

• The correct measurements are activated in the network elements

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

When the NMS/2000 and the network elements are correctly configured, theNMS/2000 can provide very valuable, continuous, network-wide informationabout the status of the network.


NSS Network Doctor

A suitable time parameter is chosen when running the reports

• Today

• Absolute date

• Relative date (ending on the current hour)

• Relative date (ending the previous midnight)

The correct measurement scope is chosen

• One MSC or HLR

• All MSCs or HLRs

Reports are distributed to the correct persons

When the reports from the NMS/2000 are available to users, the next trouble youmay have is that the resources to fix the network problems are missing, not welldefined, or that no training has been given. To find solutions for this, Nokiaprovides you with a variety of training courses and productivity services.

2.2 Monitoring the quality of a cellular network

NSS Network Doctor provides you with a selection of reports to monitor thetechnical quality of a network subsystem. Models for MSC reports and HLRreports are shown separately.

2.3 Reporting procedures

The reports as such are important tools as they offer visibility to key information.The operational procedures define how much value the reports bring.

NSS Network Doctor should not be used in an uncontrolled fashion, for example,by all NMS users simultaneously, because it increases - as any data retrieving orprocessing application - the load on the system resources. To reduce excessiveunplanned interactive use of NSS Network Doctor, ensure that the mostfrequently needed reports are available to all people who need the information.The reports can be stored in a commonly known directory accessible to allnecessary people, or distributed via mail or the Intranet.

Well-planned and controlled reporting reduces the load on the NMS/2000 byletting users get necessary data quickly without accessing the Top-level UserInterface. The reports also allow for the study of the data off-line in a file orprintout.


Introduction to NSS Network Doctor

2.4 Performance indicator

Network performance can be evaluated based on performance indicators.Performance indicators are mapped directly to either a counter or a formula thatis composed of several counters. The MSC network benchmark (600) report,for example, collects some of the most interesting indicators into one and thesame report.

The NMS/2000 database contains a very large number of counters which all areelementary performance indicators. For practical purposes, however, they can behard to interpret. NSS Network Doctor offers reporting facilities for the mostimportant performance indicators that often are referred to as Key PerformanceIndicators.


NSS Network Doctor


Using NSS Network Doctor

3 Using NSS Network DoctorBefore you use NSS Network Doctor, ensure that the measurement flow from thenetwork elements in the investigated area is functioning.

When enough consistent statistical data is available, you may run the reports andanalyse the results, and then take any necessary actions based on the results. Afterthis, you should verify the impact of actions by a new run of reports and a newanalysis. This cycle of running reports, analysing them and modifying thenetwork on the basis of the analysis, continues through the whole lifespan of thenetwork. Only the pace and scope of the key performance indicators may changefrom time to time.


NSS Network Doctor

Figure 1. General work process

Top-level reports are a good place to start the analysis. They display the basicquality indicators for a MSC over a period of time. Save the reports and use themas comparison material for later evaluation of the impact of the actions taken.

3.1 Navigating with reports, measurement tables,formulas and counters

The data in the NSS Network Doctor reports is derived from formulas composedof a number of counters as well as directly from the NMS database counterswhich you can find in the performance measurement tables. In some reports youcan find IDs of the pattern "Mxxx" (x = digit) referring to the used formulas. Inthe headers of each report the used measurement table is referred to.


Using NSS Network Doctor

Figure 2. Interrelationship between reports, measurement tables,formulas and counters

To see the actual formulas, refer to NSS Network Doctor Formulas User’s Guide,and if interested in the counters, see Database Description for MSC/HLRMeasurements.


NSS Network Doctor


User interface

Note

4 User interfaceThis chapter describes the NSS Network Doctor user interface and lists thereports in the order they appear on the submenus.

NSS Network Doctor offers a menu-based user interface where the user can moveup and down the menu hierarchy.

All reports are listed in the submenus. You can also run the reports directly fromthe main menu option Run a report by identification number.

The reports produce an output file which opens in the editor window ( dtpad inT12). You can then modify and save the report using the editor commands.

NSS Network Doctor also provides model reports. To display a model report,select Display a model report by identification number from themain menu.

As a model report does not cause any load on the database server, it is a good ideato learn about the NSS Network Doctor reports by viewing model reports first.

As each submenu contains a shortcut for running any of the NSS Network Doctorreports, you can flexibly have access to any of them regardless of which menu youare viewing. Enter the report ID after:

• m) for viewing a model report

• r) for generating an actual report from the database


NSS Network Doctor


User interface

Note

Figure 3. NSS Network Doctor user interface

4.1 Report layout

NSS Network Doctor reports are self-explanatory standard-size (56 lines per pageand 80 characters per line) textual reports presented usually in a table format.Each report starts with a front page containing a description which helps youunderstand what the report is used for.

In some reports, instead of numerical data, a counter value may occasionally beshown as string "#####". This means that the number of digits coming from thedatabase to this counter field is too large to fit in. However, in all those cases thefigure is abnormally large and has no practical meaning or is of no importance.

One of the benefits of NSS Network Doctor is that the output is a plain ASCIIfile in a readable and printable format and can thus be easily transferred andhandled. For example, to be able to view the ASCII text file in MS Word, openthe file in Word and change the font to Courier New, 8 pt.

4.2 Focusing your report selection

After you have started to run a report, NSS Network Doctor will in most casesprompt you for some of the following options before the actual report isgenerated:

• period of time

- Today- Absolute date- Relative date (ending on the current hour)- Relative date (ending the previous midnight)

• measurement scope

- One MSC or HLR- All MSCs or HLRs

In connection with some individual reports you may need to select thresholds (tomake the report shorter) or define the sorting. A reference to the measurementtable used by the report appears on the description part of the report.


NSS Network Doctor

4.3 User log

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

The Log statistics (512) report gives basic information about the NSSNetwork Doctor log file.

OS User Host Package Report Start Time Exec TimeName Name Version No yyyy-mm-dd hh:mm (s)---------- ---------- ---------- ---------- ------------------ ---------neva 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 2teh nea 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

Figure 4. Report 512: Log statistics

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

How many times a report has been used and its average execution time

Average ExecutionReport Times TimeNumber Used (sec)------ ------ ---------120 1 17122 4 4127 1 59163 2 11196 1 27200 2 84204 17 48207 1 58212 5 22213 3 16218 6 3252 10 3512 1 6515 8 3516 5 9517 25 12519 11 55

How many times a user has run a report

Report Times


User interface

Host DB User User Number Used------------ ---------- ---------- ------ ------nea OMC neva 120 1 122 4 163 2 196 1 200 1 204 4 213 3 218 1 252 3 512 1 515 5 516 5 517 25 519 6 whe 200 1 204 13 207 1 212 5 252 7 Unknown vsalline 127 1 218 5 515 3 522 7 523 12 524 1

Figure 5. Report 513: Network Doctor use statistics

4.4 NMS database administration

This main menu selection contains reports related to administering your database.The options are:

1. Show tables and views created by Network Doctor

2. Database user creation (520)

We recommend you to create a separate username in Oracle for runningNSS Network Doctor. As a database user you will have adequate but notextensive user rights. The package contains the script ndp520mx.sql,which makes the creation easy and secure.

For instructions on creating a new database user, see NSS Network DoctorSystem Administrator’s Guide, DN98619372.


NSS Network Doctor

Note

4.5 Report menus

The list below highlights the types of reports that NSS Network Doctor providesfor the collection of performance data from the telecommunications network.

If you are just learning the contents of the reports, you may run a model reportfirst by its ID to get an example of the type of report produced by NSS NetworkDoctor. This reduces the load on the system.

• MSC Statistics

- Administration of MSC Measurements- Load and Availability- MSC Clear Codes- Handover- VLR- Announcement- Traffic and Success- Signalling- Data Calls- Other MSC Reports

• HLR Statistics

- Administration of HLR Measurements- Load and Availability- Authentication Centre- Other HLR Reports

• User Log

4.5.1 MSC Statistics

This menu contains reports derived from MSC measurements.

4.5.1.1 Administration of MSC Measurements

1. Last MSC measurement record times (607)

2. First and last NSS measurement record times for each MSC (601)

3. Records for a MSC measurement (608)


User interface

4.5.1.2 Load and Availability

1. MSC CPU and MB load (605)

2. MSC CPU and MB load profiles (614)

3. MSC availability (638)

4. MSC profiles for rejected calls (637)

5. X25 load profile (624)

6. SS7 link load (511)

4.5.1.3 MSC Clear Codes

1. MSC call clear codes (014)

2. MSC call clear codes, shares and change (015)

3. Clear code set per MSC (617)

4. Clear codes of destinations (626)

5. Signalling clear codes (625)

6. Trafficability statistics (622)

7. GSM observations analysis (218)

4.5.1.4 Handover

1. Handover failure ratio (633)

2. Handover failure ratio for adjacencies (636)

3. Handover observation statistics (619)

4.5.1.5 VLR

1. VLR failure profiles (632)

2. VLR subscriber profiles per LA (635)

3. VLR authentication profile (646)

4. VLR authentication statistics (650)

4.5.1.6 Announcement

1. Announcement channel statistics (621)

2. Integrated announcement device statistics (628)


NSS Network Doctor

4.5.1.7 Traffic and Success

1. Traffic category statistics (620)

2. Cell measurement statistics (627)

3. Control unit statistics (616)

4. Destinations having high failure ratio (609)

5. Destination to destination success (613)

6. Busy hour traffic of destinations (618)

7. Circuit group statistics (602)

8. Circuit group profile (649)

9. Circuit group to destination (645)

10. Subscriber facility usage (603)

11. MAP statistics (514)

4.5.1.8 Signalling

1. MTP signalling link availability (655)

2. MTP signalling link utilisation (656)

3. MTP signalling link performance (657)

4. MTP signalling point status (659)

5. MTP signalling link set and route set availability (660)

6. not in use

7. MTP user parts signalling traffic (662)

8. not in use

9. SCCP signalling point performance (664)

10. SCCP subsystem performance (665)

11. SCCP single meters (666)

12. SCCP local subsystem availability (667)

13. TCAP performance (658)

14. TCAP transactions (672)

15. PCM statistics (668)


User interface

16. LAPD error counters (669)

17. LAPD utilisation (670)

18. LAPD traffic (671)

4.5.1.9 Data Calls

1. MSC call clear codes of data calls (527)

2. Data call clear code groups by number destination (528)

3. Data service unit statistics (529)

4. GBS data service statistics (530)

4.5.1.10 Other MSC Reports

1. MSC network benchmark (600)

2. MSC security counters (634)

3. ECU routine test statistics (647)

4. Circuit supervision (648)

5. Gapped IN services (652)

4.5.2 HLR Statistics

This menu contains reports derived from HLR measurements.

4.5.2.1 Administration of HLR measurements

1. Last HLR measurement record times (623)

2. First and last NSS measurement record times for each HLR (610)

3. Records for a HLR measurement (611)

4.5.2.2 Load and Availability

1. HLR CPU and MB load (606)

2. HLR CPU and MB load profiles (615)

3. HLR availability profiles (641)

4.5.2.3 Authentication Centre

1. AUC triplet transfer profiles (643)


NSS Network Doctor

4.5.2.4 Other HLR Reports

1. HLR supplementary service statistics (631)

2. Subscriber profiles in VLRs (640)

3. HLR security counters (651)

4. HLR usage statistics (629)

5. HLR profiles (639)

6. HLR basic service statistics (630)

7. EIR profile (644)

8. EIR requests by IMEI (654)

4.5.3 NMS Database Administration

1. Show tables and views created by Network Doctor

2. Database user creation (520)

4.5.4 User Log

1. Log statistics (512)

2. Network Doctor use statistics (513)


Actions to take before using the reports

Note

5 Actions to take before using the reportsBefore the reports can give reliable and comparable results, you have to check theNMS/2000 for the following basic issues:

• load on the NMS/2000

• MSC & HLR measurements check-up

• setting the History Windows

5.1 Load on the NMS/2000

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

The load caused by receiving measurements and by inserting them in the databasecan be considerable, and can affect the proper functioning of the NMS/2000.

Many of the NSS measurements allow you to use very short measurementperiods, for example, 5 minutes. The 60 min interval in the network analysis isoften sufficient for practical needs. Experience from the field has shown that thereis no forcing need to constantly use shorter reporting intervals.

Whenever possible, it is a good idea to start new measurements at full hours. Bydoing so it is easier to compare the counters in different measurements.


NSS Network Doctor

Note

If you choose to use a short period, you must bear in mind that this solutionrequires more capacity and therefore there should always be a very good reasonbehind the decision to go for short periods. If you want to change themeasurement period, you must stop the measurement, and you will lose the datafrom the current period.

A precise way to calculate how much data a measurement set will produce is touse the Nokia NMS Excel spreadsheet that is available on request from NokiaCustomer Services. The spreadsheet gives the amount of data but not the load onthe NMS/2000. This is why the tool is applicable if the measurement set is goingto be changed and you want to see what is the net impact on the overall datavolume.

5.2 MSC & HLR measurements check-up

NSS Network Doctor provides a variety of reports for investigating the activemeasurements in a MSC.

To check which measurements are active and send data to NMS/2000

• For MSC measurements, run the report:

Last MSC measurement record times (607), see Section 6.1.1

• For HLR measurements, run the report:

Last HLR measurement record times (623), see Section 7.1.1

To check which network elements send data to the database

• For MSCs, run the report:

First and last NSS measurement record times for each MSC (601), seeSection 6.1.2

• For HLRs, run the report:

First and last NSS measurement record times for each HLR (610), seeSection 7.1.2


Actions to take before using the reports

To check that the measurement flow is functioning

• For MSCs, run the report:

Records for a MSC measurement (608), see Section 6.1.3

• For HLRs, run the report:

Records for a HLR measurement (611), see Section 7.1.3

5.3 Setting the history windows

The size of the NMS/2000 database is limited by the size of the available diskspace, and you must compromise when deciding which information is worthstoring the longest.

The following table gives you an idea about storing lengths which have provenpractical.

For long-term storage, Nokia provides the Network Data Warehouse product.

Table 5. Example of history windows in the NMS/2000 database

Type of data Storing period

Measurements 10 days

In some reports it is necessary to see morethan one week’s data in order to find out therepetition patterns.

Observations 3 days

The observations are typically used fortroubleshooting and do not need a long history.


NSS Network Doctor


MSC reports

6 MSC reportsThis chapter describes the NSS Network Doctor reports derived from MSCmeasurements. The reports are presented roughly in the order they appear on themenu of the NSS Network Doctor user interface.

6.1 Administration of MSC measurements

NSS Network Doctor provides a variety of reports for investigating the activemeasurements in MSCs.

6.1.1 How to see which MSC measurements send data to the database

To check which measurements are active in MSCs and send data you have toanalyse the PM tables. To do this use the report Last MSC measurementrecord times (607).

================================================================================= LAST MSC MEASUREMENT RECORD TIMES== Network: PLMN= MSC: All MSCs================================================================================

The date and time of last measurements available in the NMS databaseare reported for each measurement type.The measurement groups and their MML command classes (Zxx) are shown.

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

-

TRAFFIC (ZTM, ZT2). Circuit Group...........................p_msc_cg 2001-02-16 07:15. Destination ............................p_msc_nd 2001-02-16 10:00. Control Unit ...........................p_msc_ce 2001-02-16 10:00. Cell (global) ........................p_msc_cell 2001-02-16 10:00. Cell (cell specific) ............p_msc_cell_cell 2001-02-16 10:00. Traffic Category .......................p_msc_tc 2001-02-16 09:46. Announcement Channel ..................p_msc_ann 2001-02-16 09:50. Integrated Announcement Device ....p_msc_int_ann 2001-02-16 09:49. Circuit Group to Destination ..........p_msc_ctd no records. Destination to Destination ............p_msc_dtd no records


NSS Network Doctor

. Data service unit.............p_msc_data_service no records

. GBS Data service.............p_msc_gbs_data_aiur no records

GSM (ZTP). Handover (global) ......................p_msc_ho 2001-02-16 10:00. Handover (cell) ...................p_msc_ho_cell 2001-02-16 10:00. Handover (adj. cell) ................p_msc_ho_nc 2001-02-16 10:00. VLR ...................................p_msc_vlr 2001-02-16 10:00. VLR, Location Area .................p_msc_vlr_la no records. AC in the VLR ......................p_msc_ac_vlr 2001-02-16 10:00. AC in the VLR, Detailed HLR part .p_msc_ac_count no records

LOAD OBSERVATION (ZTL). Load .................................p_msc_load 2001-02-16 10:14. Rejected Calls ........................p_msc_rej 2001-02-16 10:12

OSI (ZOO). OSI, Level 1 .........................p_msc_osi1 no records. OSI, Level 2 .........................p_msc_osi2 no records. OSI, Level 3 .........................p_msc_osi3 no records. OSI, Level 4 .........................p_msc_osi4 no records

SIGNALLING (ZOS). MTP link availability ......p_msc_mtp_link_avail 2001-02-16 10:00. MTP link performance..p_msc_mtp_link_performance 2001-02-16 10:00. MTP link utilisation ........p_msc_mtp_link_util 2001-02-16 10:00. MTP SP status ...............p_msc_mtp_sp_status 2001-02-16 10:00. MTP link/route ....p_msc_mtp_sp_link_route_avail 2001-02-16 10:00. MTP SP traffic .............p_msc_mtp_sp_traffic 2001-02-16 10:00. MTP usr traffic ...p_msc_mtp_signal_traffic_user 2001-02-16 10:00. MTP matrix traffic..p_msc_mtp_signal_traffic_mtx 2001-02-16 10:00. SCCP SP ...........................p_msc_sccp_sp 2001-02-16 10:00. SCCP subsystem ...................p_msc_sccp_sub 2001-02-16 10:00. SCCP subsystem avail..p_msc_sccp_sub_local_avail 2001-02-16 10:00. SCCP single meters ......p_msc_sccp_single_meter 2001-02-16 10:00. TCAP performance .........p_msc_tcap_performance 2001-02-16 10:00. TCAP transactions ........p_msc_tcap_transaction 2001-02-16 10:00. LAPD traffic .................p_msc_lapd_traffic 2001-02-15 11:30. LAPD utilisation ................p_msc_lapd_util 2001-02-15 11:30. LAPD error counter .............p_msc_lapd_error 2001-02-15 11:30

CIRCUIT SUPERVISION (ZTE). Circuit Seizure Supervision .......p_msc_cir_sup 2001-02-13 15:49. PCM Statistics ...................p_msc_pcm_stat no records

SECURITY (ZIR). Security ........................p_msc_secur_rep 2001-02-16 12:00. Security Counters ...........p_msc_secur_counter 2001-02-16 12:00

ECU (ZUE). ECU routine Testing .........p_msc_routine_test 2001-02-15 13:00. ECU routine Testing Detailed .p_msc_routine_unit 2001-02-15 13:00

FIELD REPORTING (ZTU). Availability ........................p_msc_avail 2001-02-16 00:00. Trafficability .............p_msc_trafficability no records. Clear Codes of Calls .............p_msc_cc_calls 2001-02-16 00:00. Clear Codes of Data Calls..........p_msc_data_cc 2001-02-16 10:05. Clear Codes of Destinations .......p_msc_cc_dest 2001-02-13 16:43. Clear Code Groups of Destin.....p_msc_ccgrp_dest no records. CC Grp of Dest. in Data Calls.p_msc_data_cc_dest 2001-02-16 10:03. Subscriber Facilities ............p_msc_subs_fac 2001-02-16 00:10. IN-service Gapping .................p_msc_in_gap 2001-02-16 07:15


MSC reports

. Signalling Specific CC ..........p_msc_signal_cc 2001-02-16 10:07

. Circ.Gr.Sign. Specific CC ....p_msc_signal_ccgrp 2001-02-16 10:07

Figure 6. Report 607: Last MSC measurement record times

6.1.2 How to see what network elements send data to the database

To check which MSCs send data to the database, use the report First andlast NSS measurement record times for each MSC (601). In this reportyou have to select the measurement type.

================================================================================= FIRST AND LAST NSS MEASUREMENT RECORD TIMES FOR EACH MSC== Network: PLMN= Measurement table: p_msc_cg================================================================================

The date and time of first and last measurements available in the NMS databaseare reported for the selected measurement type by MSCs.

First meas.pd. (stop time) Stop time of the first measurement period.Last meas.pd. (stop time) Stop time of the last measurement period.Period duration max. Maximum duration of period.Period duration min. Minimum duration of period.Period Period

Note: If the size of selected table is large, the run time can be very long.

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

Records in Circuit Group (p_msc_cg)

Period Period First meas.pd. Last meas.pd. duration durationMSC name (stop time) (stop time) max. min.-------------------- ----------------- ----------------- -------- --------MSC1KUTOJA 1998-05-26 00:22 1998-06-24 15:45 60 60

Figure 7. Report 601: First and last NSS measurement record times foreach MSC

6.1.3 Measurement flow

To check that the measurement flow from the MSC is functioning, use the reportRecords for a MSC measurement (608).

================================================================================= RECORDS FOR A MSC MEASUREMENT== Network: PLMN= BSC: all MSCs


NSS Network Doctor

= Measurement table: p_msc_cg================================================================================

The number of records, minimum reporting period and maximum reportingperiod are reported for every hour having measurement results for theselected measurement type.

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

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

Min Max prd prdDay Hour (min) (min) RECORDS-------- ---- ----- ----- ----------19970113 0103 60 60 21 0203 60 60 21 0303 60 60 21

Figure 8. Report 608: Records for a MSC measurement type

6.2 Load and availability

6.2.1 MSC CPU and MB load (605)

To check that the load of CPUs does not exceed the recommended thresholds inMSC, run the report MSC CPU and MB load (605).

================================================================================= MSC CPU AND MB LOAD== Network: PLMN= MSC: all MSC= Period: from 19981122 to 19981124= Time aggregation: whole period= Threshold: Only average load >= 0 % shown================================================================================

As a basic rule the following applies:If the average load is over 70% (or 50% for Message Bus), there can be losttraffic. These hours are highlighted with "!!!" in the Obs column.

For hunting the heavy load hours choose the Time aggregation ’hourly’ andThreshold ’50 %’.For generic report choose the Time aggregation ’average’ andThreshold ’0 %’.

Note: For MB there is no peak load available.

Measurement used: p_msc_load, 60min measurement period recommended

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


MSC reports

CPU and MB load % MSC1 from 19981122 to 19981124

Avg Load Peak LoadObj.name rate % rate % Obs------------ -------- --------- ---BDCU-0 1.0 12.0BDCU-1 1.0 12.0BSU-0 11.4 33.0BSU-1 11.9 36.0BSU-2 9.8 30.0BSU-3 15.4 44.0BSU-4 6.7 23.0CCM-0 8.9 53.0CCM-1 1.0 15.0CCSU-0 8.0 28.0CCSU-1 6.0 22.0CCSU-2 7.8 28.0CCSU-3 7.1 24.0CCSU-4 9.1 28.0CCSU-5 2.8 15.0CCSU-6 10.1 30.0CHU-0 3.8 18.0CHU-1 6.0 42.0CM-0 4.8 28.0CM-1 4.1 18.0M-0 2.6 14.0M-1 2.0 13.0MB 10.6 0.0OMU-0 7.3 81.0OMU-1 2.0 15.0STU-0 4.9 21.0STU-1 5.0 21.0VLRU-0-0 11.6 37.0VLRU-0-1 10.2 32.0VLRU-1-0 11.1 45.0VLRU-1-1 10.6 44.0VLRU-2-0 11.6 37.0VLRU-2-1 10.2 31.0VLRU-3-0 11.3 36.0VLRU-3-1 9.9 32.0

CPU and MB load % MSC2 from 19981122 to 19981124

Avg Load Peak LoadObj.name rate % rate % Obs------------ -------- --------- ---BDCU-0 1.0 13.0BDCU-1 1.2 15.0BSU-0 6.8 23.0BSU-1 1.0 12.0BSU-2 6.8 25.0BSU-3 12.7 35.0BSU-4 13.6 39.0BSU-5 12.8 34.0CASU-0 2.0 15.0CASU-1 2.6 16.0CCM-0 1.0 14.0CCM-1 1.0 13.0CCSU-0 10.1 32.0CCSU-1 8.9 27.0CCSU-2 4.6 20.0CCSU-3 8.1 27.0CCSU-4 8.9 28.0CCSU-5 1.0 12.0CCSU-6 9.4 28.0


NSS Network Doctor

CCSU-7 10.9 32.0CCSU-8 8.2 25.0CHU-0 2.7 15.0CHU-1 4.0 37.0CM-0 3.6 16.0CM-1 4.1 19.0CMU-0 2.5 15.0CMU-1 1.5 12.0IWCU-0 1.0 11.0IWCU-1 1.6 13.0M-0 1.5 12.0M-1 2.0 13.0MB 9.7 0.0OMU-0 9.3 64.0OMU-1 2.0 15.0STU-0 3.7 19.0STU-1 3.4 17.0VLRU-0-0 11.3 40.0VLRU-0-1 12.7 43.0VLRU-1-0 11.3 39.0VLRU-1-1 12.5 42.0VLRU-2-0 11.3 35.0VLRU-2-1 12.7 41.0VLRU-3-0 11.2 41.0VLRU-3-1 12.6 42.0

Figure 9. Report 605: MSC CPU and MB load

For HLR, a corresponding report HLR CPU and MB load (606) is provided.

6.2.2 MSC CPU and MB load profiles (614)

To check that the load of CPUs is not even approaching the recommendedthresholds, run the report MSC CPU and MB load profiles (614).

================================================================================= MSC CPU AND MB LOAD PROFILES== Network: PLMN= Period: from 19971118 to 19971119= Threshold: Avg load >= 30 %================================================================================

As a basic rule the following applies:If the average load is over 70% (or 50% for Message Bus),there can be lost traffic.These hours are highlighted with "!!!" .

Note: For MB there is no peak load available, and the peak load time of MBshown is based on the start time of the measurement.

Measurement used: p_msc_load

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

CPU and MB load % for MSC from 19971118 to 19971119


MSC reports

Peak Load Peak Load day time Peak Load Avg LoadMSC Obj.name yyyy-mm-dd hh:mm rate % rate % Obs------------- -------- ------------ --------- --------- -------- ---MSC1 MB 1997-11-18 08:22 0.0 40.9 09:22 0.0 53.4 !!! 10:22 0.0 55.9 !!! 11:22 0.0 48.9 12:22 0.0 40.7 13:22 0.0 51.0 !!! 14:22 0.0 54.9 !!! 15:22 0.0 57.6 !!! 17:26 26.0 53.8 !!! 18:26 22.0 44.1 19:26 20.0 38.8 20:26 20.0 38.1 1997-11-19 08:26 23.0 40.1 09:26 23.0 52.4 !!! 10:26 26.0 55.7 !!! 11:26 27.0 46.9 12:26 22.0 40.2 13:26 24.0 50.5 !!! 14:26 24.0 55.2 !!! 15:26 26.0 56.7 !!! 16:26 27.0 58.8 !!! 17:26 24.0 54.8 !!! 18:26 21.0 44.3

Figure 10. Report 614: MSC CPU and MB load profiles

For HLR, a corresponding report HLR CPU and MB load profiles (615) isprovided.

6.2.3 MSC availability (638)

================================================================================= MSC AVAILABILITY== Network: PLMN= MSC: MSC1= Period: from 19980119 to 19980119================================================================================

Discon time Time when the unit was not in woex or spex state.Discon time duplex Time when none of the duplicated units were in woex. or spex.Unit restrt Unit restarts.Adm restrt Administrative restarts.Pros restrt Processor restarts.Prepros restrt Restarts of subordinate preprocessors.Duplex restrt Simultaneous restarts of duplicated units.

Measurement used: p_msc_availNOTE: Only units having restarts or disconnection time are reported.NOTE: -1 values mean that the value is not calculated by MSC.

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


NSS Network Doctor

Availability for MSC1 from 19980119 to 19980119

Discon Discon Day Hour Unit time time Admin Pros Prepros DuplexUnit yyyy-mm-dd hh:mm restrt (sec) duplex restrt restrt restrt restrt---------- ---------- ----- ------ ------ ------- ------ ------ ------- -------VLRU-1-0 1998-01-19 00:00 5 6 0 0 0 0 0VLRU-1-1 1998-01-19 00:00 2 8 0 0 0 0 0

Figure 11. Report 638: MSC availability

For HLR, a corresponding report HLR availability profiles (641) isprovided.

6.2.4 MSC profiles for rejected calls (637)

================================================================================= MSC PROFILES FOR REJECTED CALLS== Network: PLMN= MSC: all MSCs= Period: from 19971101 to 19971119================================================================================

The MSC overload mechanism is controlled with PRFILE parameters(class 12, parameters 53-56).

Fmly Process family nameRej calls Rejected calls of window access controlRej calls % Ratio of rejected calls (%)Queue max lgth Maximum length of queueCust wait trh Nbr of customers whose waiting time is greater than threshold.Rej. inc low Incoming calls rejected due to lower limit in message buffer.Rej. inc up Incoming calls rejected due to upper limit in message buffer.Rej. out up Outgoing calls rejected due to upper limit in message buffer.

NOTE: Only those measurement periods when there have been rejected calls are. reported.

Measurement used: p_msc_rejMeasurement start: ZTLS:R; (with load observation ZTLS:B;)

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

Rejected calls for MSC1 from 19971101 to 19971119

Rej. Queue Cust Rej. Rej. Rej. Day Hour Rej. calls max wait inc inc outObject Fmly yyyy-mm-dd hh:mm calls % lgth trh low up up---------- ---- ---------- ----- ------ ------ ----- ----- ----- ----- -----BSU-3 1997-11-19 16:26 24 0.0 na na na na naBSU-5 14:26 32 0.0 na na na na naBSU-6 15:26 30 0.0 na na na na naEXCHG. 14:26 32 0.0 na na na na 0


MSC reports

Note

EXCHG. 15:26 30 0.0 na na na na 0EXCHG. 16:26 24 0.0 na na na na 0

Figure 12. Report 637: MSC profiles for rejected calls

6.3 Signalling

Of these reports, 511 and 624 are under the MSC Statistics... → Load andAvailability... menu and 514 under the MSC Statistics... →Traffic and Success... menu.

6.3.1 SS7 link load (511)

To check that the load of SS7s is not approaching the recommended thresholds,run the report SS7 link load (511).

This report is run through MML based on ZOLU command outputpostprocessing, and therefore cannot be run by its ID number or by auto scriptgeneration.

The load is usually checked on the Busy Hour. To find out about earlier BusyHour, run the MSC network benchmark (600) report.

DX 200 MSC2 1998-01-19 16:32:34

SIGNALLING LINK UTILIZATION

ACTIVE UNITMETERS OF LAST PERIOD: 16:00:00 - 16:30:00 (30 MIN)Note: If RX or TX traffic is over 0.2 Erl, new links should be added.===============================================================================

Traf TrafLINK RX TXNbr (Erl) (Erl)==== ==== ====1 0.09 0.052 0.09 0.053 0.09 0.054 0.09 0.055 0.09 0.056 0.09 0.057 0.09 0.0510 0.08 0.0511 0.08 0.05

Figure 13. Report 511: SS7 link load


NSS Network Doctor

Note

6.3.2 X25 load profile (624)

The X25 link load is calculated from OSI4 measurement using the X25 loadprofile (624) report.

This report is valid only for X25 channels, but all channels that are defined in themeasurement are shown. The report assumes that the measurement period is 60minutes.

================================================================================= X25 LOAD PROFILE== Network: PLMN= MSC: all MSCs= Period: from 19980327 to 19980327================================================================================

For X.25 connections the maximum capacity is 64kbit/s

An example to set the OSI measurement on for layer 4, channels 4 and 5:1) create.... ZOOC:name:4,0&5:ALL,00-00-24-00,602) start..... ZOOS:name

Note: This report is valid only for X25 channels but all channels. that are defined in the measurement are shown.Note: This report assumes that the measurement period is 60 min!

Measurements used: p_msc_osi4

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

-

OSI4 X25 load profile - MSC1

OSI Load chn Period start BYTES CAPACITY (%)------ ------------ ---------- ---------- ------ 2 199803262300 0 28800000 0.0 199803270000 436 28800000 0.0 199803270100 379 28800000 0.0 199803270200 403 28800000 0.0 199803270300 0 28800000 0.0 199803270400 436 28800000 0.0 199803270500 379 28800000 0.0

Figure 14. Report 624: X25 load profile


MSC reports

6.3.3 MAP statistics (514)

This report is MML based, and therefore cannot be run by its ID number or byauto script generation. The report shows MAP statistics extracted by the ZOXL:S;command from all MSCs.

For short term MAP statistics, enter:

omc> % ZOXS:S:SDAY=1998-01-29,STIME=12-00,EDAY=1998-02-28,ETIME=12-00;

For long term MAP statistics, enter:

omc> % ZOXS:L:SDAY=1998-01-29,STIME=12-00,EDAY=1998-02-28,ETIME=12-00;

For details on the cases you are interested in, enter:

omc> % ZOXL:S:<SOURCE>:<DESTINATION>:MSISDN=<ISDN NUMBER>::ALL;

DX 200 MSC1 1998-01-22 15:45:11

MAP OPERATION CODE REPORT

METER TYPE: SHORT SOURCE: MSC DESTINATION: HLR

START TIME 1998-01-22 00:00:00 END TIME 9999-12-31 24:00:00LAST SAMPLE TIME 1998-01-22 15:00:00

NETWORK ISDN NUMBER : 86 49NETWORK IMSI NUMBER : -

MAP STATISTIC GENERAL DATA OUTGOING INCOMING--------------------------------------------------------------------MISSING DATA : 0.0 % 0.0 %SUM OF STARTED OPERATIONS : 519053 1302SUM OF SUCCEEDED OPERATION : 381294 1302SUM OF FAILED OPERATIONS : 137759 0

Figure 15. Report 514: MAP statistics, MML-based

6.3.4 MTP signalling link availability (655)

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


NSS Network Doctor

= MTP SIGNALLING LINK AVAILABILITY== Network: PLMN= MSC: all MSC= Period: from 19990923 to 19990923= Time aggregation: whole period================================================================================

Part 1: Unavailability duration per reason:

Sign link Signalling linkall Duration of signalling link unavail. for any reasonlink Duration of signalling link unavail. due to link failureblock Duration of signalling link unavail. due to local blockingcpu Duration of signalling link unavail. due to remote processor. outagelocal mng Duration of signalling link unavail. due to local management. actionsremote mng Duration of signalling link unavail. due to remote management. actions

Part 2:

Sign link Signalling linklocal busy Duration of local busy (number of SIB’s)local co Local manual changeovers and changeovers due to system. recovery actionsremote co Remote initiative changeoversstart remote cpu Start of remote processor outagestop remote cpu Stop of remote processor outagelocal mng inhib Local management inhibitlocal mng unhib Local management uninhibit

Measurement used: p_msc_mtp_link_avail

=============================================================================== Part 1: MTP signalling link availability for MSC1KUTOJA from 19990923 to 19990923 Unavailability duration per reason

local remote Sign all link block cpu mng mng link (hh:mi) (hh:mi) (hh:mi) (hh:mi) (hh:mi) (hh:mi)----- -------- -------- -------- -------- -------- -------- 0 0:00 0:00 0:00 0:00 0:00 0:00 1 0:00 0:00 0:00 0:00 0:00 0:00 10 0:00 0:00 0:00 0:00 0:00 0:00 11 0:00 0:00 0:00 0:00 0:00 0:00 20 0:00 0:00 0:00 0:00 0:00 0:00 21 0:00 0:00 0:00 0:00 0:00 0:00 30 0:00 0:00 0:00 0:00 0:00 0:00 31 0:00 0:00 0:00 0:00 0:00 0:00 40 0:00 0:00 0:00 0:00 0:00 0:00 50 24:00 0:00 0:00 0:00 0:00 0:00 79 0:00 0:00 0:00 0:00 0:00 0:00 81 0:00 0:00 0:00 0:00 0:00 0:00 109 0:00 0:00 0:00 0:00 0:00 0:00 110 0:00 0:00 0:00 0:00 0:00 0:00 142 0:00 0:00 0:00 0:00 0:00 0:00 143 24:00 24:00 0:00 0:00 0:00 0:00 144 24:00 0:00 0:00 0:00 0:00 0:00 145 0:00 0:00 0:00 0:00 0:00 0:00 146 24:00 0:00 0:00 0:00 0:00 0:00 158 0:00 0:00 0:00 0:00 0:00 0:00 159 0:00 0:00 0:00 0:00 0:00 0:00

Part 2: MTP signalling link availability for MSC1KUTOJA from 19990923 to 19990923


MSC reports

start stop local local Sign local local remote remote remote mng mng link busy co co cpu cpu inhib unhib----- ----- ----- ------ ------ ------ ----- ----- 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 10 0 0 0 0 0 0 0 11 0 0 0 0 0 0 0 20 0 0 0 0 0 0 0 21 0 0 0 0 0 0 0 30 0 0 0 0 0 0 0 31 0 0 0 0 0 0 0 40 0 0 0 0 0 0 0 50 0 0 0 0 0 0 0 79 0 0 0 0 0 0 0 81 0 0 0 0 0 0 0 109 0 0 0 0 0 0 0 110 0 0 0 0 0 0 0 142 0 0 0 0 0 0 0 143 0 0 0 0 0 0 0 144 0 0 0 0 0 0 0 145 0 0 0 0 0 0 0 146 0 0 0 0 0 0 0 158 0 0 0 0 0 0 0 159 0 0 0 5 0 0 0

Figure 16. Report 655: MTP signalling link availability

6.3.5 MTP signalling link utilisation (656)

================================================================================= MTP SIGNALLING LINK UTILISATION== Network: PLMN= HLR: all MSCs= Period: from 20001103 to 20001107= Time aggregation: whole period================================================================================

Part 1: Signalling link congestion levels

sign link Signalling link

Signalling link congestion levels set by the MML:cong1 level 1cong2 level 2cong3 level 3

Duration Duration of congestionMSU disc The number of message signal units (MSU) discarded due to. signalling link congestionMSU loss The number of congestion events resulting in loss of MSUs30m peak (Erl) Peak load in Erlangs measured in 30 min periods during. the reporting period5m peak (Erl) Peak load in Erlangs measured in 5 min periods during. the reporting period

Part 2:

SIF SIO trans The number of SIF and SIO octets transmitted


NSS Network Doctor

SIF SIO recv The number of SIF and SIO octets receivedmsg trans The number of message signal units transmittedmsg recv The number of message signal units receivedretr The number of octets retransmittedbit rate kbit/s The bit rate of the signalling link

Measurement used: p_msc_mtp_link_util

=============================================================================== Part 1: MTP signalling link utilisation for MSC1 from 20001103 to 20001107 Signaling link congestion levels

Level 30m peak 5m peak ****** (Erl) (Erl) cong1 ******** ******** sign cong2 duration IN IN link cong3 (hh:mi:ss) MSU disc MSU loss OUT OUT----- ------ ------------ --------- -------- -------- -------- 0 0 0:00:00 0 0 0.000 0.001 0 0:00:00 0 0 0.000 0.001 0 0:00:00 0 0

1 0 0:00:00 0 0 0.000 0.001 0 0:00:00 0 0 0.000 0.001 0 0:00:00 0 0

2 0 0:00:00 0 0 0.000 0.001 0 0:00:00 0 0 0.000 0.001 0 0:00:00 0 0

3 0 0:00:00 0 0 0.000 0.001 0 0:00:00 0 0 0.000 0.001

0 0:00:00 0 0

31 0 0:00:00 0 0 0.000 0.000 0 0:00:00 0 0 0.000 0.000 0 0:00:00 0 0

40 0 0:00:00 0 0 0.001 0.002 0 0:00:00 0 0 0.001 0.001 0 0:00:00 0 0

109 0 0:00:00 0 0 0.001 0.002 0 0:00:00 0 0 0.001 0.003 0 0:00:00 0 0

110 0 0:00:00 0 0 0.001 0.002 0 0:00:00 0 0 0.001 0.003 0 0:00:00 0 0

144 0 0:00:00 0 0 0.001 0.003 0 0:00:00 0 0 0.001 0.002

0 0:00:00 0 0

Part 2: MTP signalling link utilisation for MSC1 from 20001103 to 20001107

SIF SIF bit sign SIO SIO msg msg rate link trans recv trans recv retr kbit/s------ ----------- ----------- --------- --------- ------ ------ 0 254142 306489 12008 12053 0 64 1 254940 304342 12004 12034 0 64 2 254190 306746 12006 12032 0 64 3 255360 306149 12008 12036 0 64 31 216274 231762 13659 13683 0 64 40 261166 293543 12002 13659 0 64


MSC reports

109 643458 621217 30045 30212 0 64 110 652451 612054 29989 29806 0 64 144 604431 604001 30234 30005 0 64

Figure 17. Report 656: MTP signalling link utilisation

6.3.6 MTP signalling link performance (657)

================================================================================= MTP SIGNALLING LINK PERFORMANCE== Network: PLMN= MSC: all MSCs= Period: from 19990923 to 19990923= Time aggregation: whole period================================================================================

Part 1:Failures per reason:all flrs failures, all reasonsabn abnormal FIBR/BSNRack excessive delayerror rate excessive error ratecong excessive durationalign Signalling alignment or proving failure

Part 2:service duration Duration of signaling link in the in-servicesign unit The number of signal units received in errorneg ack The number of negative acknowledgements receivedauto co Automatic changeoverauto cb Automatic changebacklink rest Signalling link restoration

Measurement used: p_msc_mtp_link_performance

=============================================================================== Part 1: MTP signalling link performance for MSC1KUTOJA from 19990923 to 19990923 Failures per reason

Sign all error link flrs abn ack rate cong align----- ----- ----- ----- ----- ----- ----- 0 0 0 0 0 0 0 1 0 0 0 0 0 0 10 0 0 0 0 0 0 11 0 0 0 0 0 0 20 0 0 0 0 0 0 21 0 0 0 0 0 0 30 0 0 0 0 0 0 31 1 0 0 1 0 0 40 0 0 0 0 0 0 50 0 0 0 0 0 0 79 0 0 0 0 0 0 81 0 0 0 0 0 0 109 0 0 0 0 0 0 110 0 0 0 0 0 0 142 0 0 0 0 0 0 143 0 0 0 0 0 7920


NSS Network Doctor

144 0 0 0 0 0 0 145 0 0 0 0 0 0 146 0 0 0 0 0 0 158 0 0 0 0 0 0 159 0 0 0 0 0 0 Part 2:MTP signalling link performance for MSC1KUTOJA from 19990923 to 19990923

service Sign duration sign neg auto auto link link (hh:mi) unit ack co cb rest----- -------- ----- ----- ----- ----- ----- 0 24:00 1 0 0 0 0 1 24:00 1 0 0 0 0 10 24:00 0 0 0 0 0 11 23:31 0 0 1 1 1 20 24:00 0 0 0 0 0 21 23:31 0 0 1 1 1 30 24:00 12 0 0 0 0 31 23:30 72 0 2 2 2 40 24:00 0 0 0 0 0 50 0:00 0 0 0 0 0 79 23:31 0 0 1 1 1 81 23:59 1 0 0 0 0 109 23:59 0 0 0 0 0 110 24:00 0 0 0 0 0 142 23:59 0 0 0 0 0 143 0:00 671 0 0 0 0 144 0:00 0 0 0 0 0 145 24:00 60 0 0 0 0 146 0:00 0 0 0 0 0 158 24:00 2823 0 0 0 0 159 23:59 1413 0 5 5 5

Figure 18. Report 657: MTP signalling link performance

6.3.7 MTP signalling point status (659)

================================================================================= MTP SIGNALLING POINT STATUS== Network: PLMN= MSC: all MSCs= Period: from 20001104 to 20001108= Time aggregation: whole period================================================================================

Report description:

net Networksign point Signalling pointduration adjacent Duration of inaccessibility of adjacent signalling pointadj inacc Adjacent signalling point inaccessiblemsg The number of transfer controlled messages receivedMSU DISC ROUT Tran The number of message signal units discarded due to. Rec routing data error (transmitted/received)MSU STP spc opc stp Unauthorised STP MSU count for inhibited SPC/OPC/STPUPU MSG Tra Rec Transmitted/Received UPU (User Part Unavailable) messages

Measurement used: p_msc_mtp_sp_status


MSC reports

=============================================================================== MTP signalling point status for MSC1 from 20001104 to 20001108

MSU MSU DISC STP UPU ROUT spc MSG sign duration adj Tran opc Tranet point adjacent inac msg Rec stp Rec----- ------- ------------ ---- ---- ---- ---- ----NA0 90 61:30:00 0 0 0 0 0 0 0 0 0

1024 0:00:00 0 0 0 0 0 0 0 0 0

2040 0:00:00 0 0 0 0 0 0 0 0 0

16256 0:00:00 0 0 0 0 0 0 0 0 0

16257 0:00:00 0 0 0 0 0 0 0 0 0

16260 61:30:00 0 0 0 0 0 0 0 0 0

16261 0:00:00 0 0 0 0 0 0 0 0 0

16262 0:00:00 0 0 0 0 0 0 0 0 0

16263 0:00:00 0 0 0 0 0 0 0 0 0

16264 0:00:00 0 0 0 0 0 0 0 0 0

16266 61:30:00 0 0 0 0 0 0 0 0 0

Figure 19. Report 659: MTP signalling point status

6.3.8 MTP signalling link set and route set availability (660)

================================================================================= SIGNALLING LINK SET AND ROUTE SET AVAILABILITY== Network: PLMN


NSS Network Doctor

= MSC: all MSCs= Period: from 19990923 to 19990923= Time aggregation: whole period================================================================================

Report description:

net Networksign point Signalling pointlink set unavail duration Duration of unavailability of signalling link setlink set fail start Start of signalling link set failurelink set fail stop Stop of signalling link set failuretrans block Transmission of transfer prohibited message started. due to signalling link failuretrans allow Transmission of transfer allowed message started. due to signalling link failureunavail route Unavailability of signalling route due to transfer. prohibited message receivedunavail set Unavailability of signalling route setunavail duration route Duration of the unavailability of signalling route. transfer prohibited message receivedunavail|duration route set Dur. of the unavailability of signalling route set

Measurement used: p_msc_mtp_sp_link_route_avail

=============================================================================== Signalling link set and route set availability for MSC1KUTOJA from 19990923 to 19990923

link set unavail fail trans unavail duration link set ******** ***** ******* ******** sign unavail start block route routenet point duration stop allow set route set----- ------- ------------ -------- ------ ------- ------------NA0 90 24:00:00 0 0 0 0:00:00 0 0 0 24:00:00

1024 0:00:00 0 0 0 0:00:00 0 0 0 0:00:00

16256 0:00:00 0 0 0 0:00:00 0 0 0 0:00:00

16257 0:00:00 0 0 0 0:00:00 0 0 0 0:00:00

16261 0:00:00 0 0 0 0:00:00 0 0 0 0:00:00

16262 0:00:00 0 0 0 0:00:00 0 0 0 0:00:00

16263 0:00:00 0 0 0 0:00:00 0 0 0 0:00:00

16264 0:00:00 0 0 0 0:00:00 0 0 0 0:00:00

16265 0:00:00 0 0 0 0:00:00 0 0 0 0:00:00

16266 24:00:00 0 0 0 0:00:00 0 0 0 24:00:00

16273 0:00:08 5 5 0 0:00:00 5 5 5 0:00:08


MSC reports

16274 0:00:00 0 0 0 0:00:00 0 0 0 0:00:00

16275 0:00:00 0 0 0 0:00:00 0 0 0 0:00:00

16298 24:00:00 0 0 0 0:00:00 0 0 0 24:00:00

NA1 1280 0:00:00 0 0 0 0:00:00 0 0 0 0:00:00

Signalling link set and route set availability for MSC1KUTOJA from 19990923 to 19990923

link set unavail fail trans unavail duration link set ******** ***** ******* ******** sign unavail start block route routenet point duration stop allow set route set----- ------- ------------ -------- ------ ------- ------------NA1 12160 0:00:00 0 0 0 0:00:00 0 0 0 0:00:00

Figure 20. Report 660: MTP signalling link set and route set availability

6.3.9 MTP user parts signalling traffic (662)

================================================================================= MTP USER PARTS SIGNALLING TRAFFIC== Network: PLMN= MSC: all MSC= Period: from 19990923 to 19990923= Time aggregation: whole period================================================================================

Report description:

net NetworkSIO Service information octetuser part User partSIF SIO recv The number of received SIF and SIO octets with a given SIOSIF SIO trans The number of transmitted SIF and SIO octets with a given SIO

Measurement used: p_msc_mtp_signal_traffic_user

=============================================================================== MTP signalling link traffic report of user parts for MSC1KUTOJA from 19990923 to 19990923

SIF SIF user SIO SIOnet SIO part recv trans----- --------- ----- ---------- ----------NA0 128 SNM 112 108 129 SNT 574320 574320 130 SNTA 0 0 131 SCCP 45805659 45353706 133 ISUP 41078 32471


NSS Network Doctor

NA1 192 SNM 0 0 193 SNT 36705 36705 194 SNTA 0 0 195 SCCP 0 0 196 TUP 0 0 197 ISUP 0 0 198 DUP0 0 0 199 DUP1 0 0 200 IND8 0 0 201 IND9 0 0 202 INDA 0 0 203 INDB 0 0 204 INDC 0 0 205 INDD 0 0 206 INDE 0 0 207 INDF 0 0

Figure 21. Report 662: MTP user parts signalling traffic

6.3.10 SCCP signalling point performance (664)

================================================================================= SCCP SIGNALLING POINT PERFORMANCE== Network: PLMN= MSC: all MSCs= Period: from 20001021 to 20001109= Time aggregation: whole period================================================================================

This report contains measurement data of the signaling points.

Part 1: SCCP signalling point performance. Failures per reason

NW NetworkGT1 fail Routing error - no translation of GT type 1.GT2 fail Routing error - no translation of GT type 2.GT3 fail Routing error - no translation of GT type 3.GT4 fail Routing error - no translation of GT type 4.GT unkno Routing error - no translation of unknown GT type.GT trans Routing error - no translation of spesific GT.

Part 2: SCCP signalling point performance. Failures per reason

Net fail Routing error - due to a failure in the network.Net overl Routing error - due to the network overload.Sub overl Routing error - due to the subsystem overload.Sub Fail Routing error - due to a failure in the subsystem.Uneq user Routing error - unequipped user.Unkn reas Routing error - unknown reason.Syn err Observed syntax errors.

Part 3: SCCP signalling point performance. Messages

UDT trans UDT messages sent.UDT rec UDT messages received.UDTS trans UDTS messages sent.


MSC reports

UDTS rec UDTS messages received.XUDT trans XUDT messages sent.XUDT rec XUDT messages received.XUDTS trans XUDTS messages sent.XUDTS rec XUDTS messages received.

Part 4: SCCP signalling point performance. Messages

CR trans CR messages sent to MTP plus ISDN-UP embedded CRs.CR rec CR messages received fron MTP plus ISDN-UP embedded CRs.CREF trans CREF messages sent to MTP.CREF rec CREF messages received fron MTP.RSR trans RSR messages sent to MTP.RSRT rec RSR messages received fron MTP.ERR trans ERR messages sent to MTP.ERR rec ESR messages received fron MTP.

Part 5: SCCP signalling point performance. Failures, timers, resets and releases

Fail Rel Comp cl 2 Failure of release complete supervision for DPC (class 2)Fail Rel Comp cl 3 Failure of release complete supervision for DPC (class 3)Timer (iar) Expi cl 2 Timer T(iar) expiry for DPC (class 2)Timer (iar) Expi cl 3 Timer T(iar) expiry for DPC (class 3)Prov Ini Reset Provider initiated reset of a connection to DPCProv Ini Rel Provider initiated release of a connection to DPC

Part 6: SCCP signalling point performance. Subsystem messages

SCCP SubSys Cong Received SCCP/Subsystem congested messagesSubSys Prohi Received Subsystem prohibited messagesSubSys Allow Received Subsystem allowed messages

Measurement used: p_msc_sccp_sp, p_msc_sccp_sp_sub

Note: Activation and timer setting by MML ZOSM.===============================================================================

Part 1: SCCP signalling point performance for MSC1 from 20001021 to 20001109 Failures per reason

Sign GT1 GT2 GT3 GT4 GT GT point NW fail fail fail fail unkno trans------ ----- ------ ------ ------ ------ ------ ------ 0 NA0 0 0 0 0 0 0 NA1 0 0 0 0 0 0 1024 NA0 0 0 0 0 0 4 1280 NA1 0 0 0 0 0 0 16256 NA0 0 0 0 0 0 0 16260 NA0 0 0 0 0 0 0 16262 NA0 0 0 0 0 0 0 16264 NA0 0 0 0 0 0 0 16267 NA0 0 0 0 0 0 0 16274 NA0 0 0 0 0 0 0 16315 NA0 0 0 0 0 0 0 Part 2:SCCP signalling point performance for MSC1 from 20001021 to 20001109 Failures per reason


NSS Network Doctor

Sign Net Net Sub Sub Uneq Unkn Syn point fail overl overl Fail user reas err------ ------ ------ ------ ------ ------ ------ ------ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1024 0 0 0 0 0 0 0 1280 0 0 0 0 0 0 0 16256 0 0 0 0 0 0 0 16260 20 0 0 0 0 0 0 16262 0 0 0 0 0 0 0 16264 0 0 0 0 0 0 0 16267 0 0 0 0 0 0 0 16274 13 0 0 79 0 0 0 16315 0 0 0 0 0 0 0 Part 3:SCCP signalling point performance for MSC1 from 20001021 to 20001109 Messages

Sign UDT UDT UDTS UDTS XUDT XUDT XUDTS XUDTS point trans rec trans rec trans rec trans rec------ -------- ------- ------- ----- ----- ----- ----- ----- 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1024 21 3803 0 0 0 0 0 0 1280 0 0 0 0 0 0 0 0 16256 0 0 0 0 0 0 0 0 16260 0 0 0 0 0 0 0 0 16262 375 2 0 0 0 0 0 0 16264 3979 80 0 0 0 0 0 0 16267 4877 12 0 0 0 0 0 0 16274 46 28 0 0 0 0 0 0 16315 324 471 0 0 0 0 0 0 Part 4:SCCP signalling point performance for MSC1 from 20001021 to 20001109

Sign CR CR CREF CREF RSR RSRT ERR ERR point trans rec trans rec trans rec trans rec------ ------ ------ ------ ------ ------ ------ ------ ------ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1024 0 0 0 0 0 0 0 0 1280 0 0 0 0 0 0 0 0 16256 0 0 0 0 0 0 0 0 16260 0 0 0 0 0 0 0 0 16262 15 9491 58 0 0 0 0 0 16264 0 39753 1821 0 0 0 0 0 16267 0 30533 566 0 0 0 0 0 16274 0 138 2 0 0 0 0 0 16315 0 0 0 0 0 0 0 0 Part 5:SCCP signalling point performance for MSC1 from 20001021 to 20001109

Fail Fail Timer Timer Rel Rel (iar) (iar) Prov Prov Sign Comp Comp Expi Expi Ini Ini point cl 2 cl 3 cl 2 cl 3 Reset Rel------ ------ ------ ------ ------ ------ ------ 0 0 0 0 0 0 0 0 0 0 0 0 0 1024 0 0 0 0 0 0 1280 0 0 0 0 0 0 16256 0 0 0 0 0 0 16260 0 0 0 0 0 0 16262 0 0 0 0 0 0 16264 0 0 0 0 0 0 16267 0 0 0 0 0 0 16274 0 0 0 0 0 0 16315 0 0 0 0 0 0


MSC reports

Part 6:SCCP signalling point performance for MSC1 from 20001021 to 20001109

SCCP Sign SubSystem SubSys SubSys SubSys point Number Cong Prohi Allow------ --------- -------- -------- -------- 1024 1 0 0 0 1280 1 0 0 0 16256 1 0 0 0 16260 1 0 0 0 16262 1 0 0 0 16264 1 0 0 0 16267 1 0 0 0 16274 1 0 0 0 16315 1 0 0 0

Figure 22. Report 664: SCCP signalling point performance

6.3.11 SCCP subsystem performance (665)

================================================================================= SCCP SUBSYSTEM PERFORMANCE== Network: PLMN= MSC: all MSCs= Period: from 20001022 to 20001110= Time aggregation: whole period================================================================================

This report contains measurement data of the SCCP subsystems.

Part 1: SCCP subsystem performance.

Sub sys SubsystemSub name Subsystem name.NW Network

To local All messages related to a local subsystem.To redun All messages transmitted to the redundant subsystem.Too large msg Too large messages for segmentation.Trans class0/class1 All transmitted messages in protocols class 0 / class 1.Rec class0/class1 All received messages in protocols class 0 / class 1.


CSM acc loc Acceptance of a coordinated state modification (CSM). request by a local subsystemCSM acc rem Acceptance of a CSM request by a remote subsys.CSM rej loc Rejection of a CSM request by a local subsys.CSM rej rem Rejection of a CSM request by a remote subsys.To local wiout GT Msg. to a local subsys. that don’t require GT translation.From local wiout GT Msg. from a local subsys. that doesn’t require GT transl.To local with GT Msg. addressed to a local subsys. that requires GT transl.From local with GT Msg. from a local subsys. that requires GT transl.


DT1 rec DT1 messages received from MTP per sink SSN.


NSS Network Doctor

DT1 trans DT1 messages sent to MTP per source SSN.DT2 recs DT2 messages received from MTP per sink SSN.DT2 trans DT2 messages sent to MTP per source SSN.ED rec ED messages received from MTP per sink SSN.ED trans ED messages sent to MTP per source SSN.


Last Prohi Start Last start time when of local subsystem becomes prohibitedLast Prohi Stop Last stop time when of local subsystem becomes available

Measurement used: p_msc_sccp_sub


Part 1: SCCP subsystem performance for MSC1 from 20001022 to 20001110

Too Trans Rec Sub Sub To To large class0 class0 sys name NW local redun msg class1 class1------ ----- ---- ------- ------- ------- ------- ------- 1 SCMG NA0 15 0 0 148 15 0 0

NA1 0 0 0 0 0 0 0

7 MAPV NA0 17105 0 0 16930 17105 0 0

NA1 0 0 0 0 0 0 0

8 MAPM NA0 10514 0 0 9527 7333 0 3115

NA1 0 0 0 0 0 0 0

12 INAP NA0 24 0 0 0 0 27 24

149 MAPS NA0 0 0 0 0 0 0 0

192 BSSAS NA0 401 0 0 295 401 0 0

254 BSSAP NA0 361158 0 0 8097 213 0 0

Part 2:SCCP subsystem performance for MSC1 from 20001022 to 20001110

To From To From CSM CSM CSM CSM local local local local Sub Sub acc acc rej rej wout wout with with sys name NW loc rem loc rem GT GT GT GT------ ----- ---- --- --- --- --- ------- ------- ------ ------ 1 SCMG NA0 0 0 0 0 15 183 0 0 NA1 0 0 0 0 0 0 0 0 7 MAPV NA0 0 0 0 0 0 0 17105 16930


MSC reports

NA1 0 0 0 0 0 0 0 0 8 MAPM NA0 0 0 0 0 0 0 10514 9527 NA1 0 0 0 0 0 0 0 0 12 INAP NA0 0 0 0 0 0 0 24 27 149 MAPS NA0 0 0 0 0 0 0 0 0 192 BSSAS NA0 0 0 0 0 0 291 401 4 254 BSSAP NA0 0 0 0 0 361158 439185 0 0


Sub Sub DT1 DT1 DT2 DT2 ED ED sys name NW rec trans rec trans rec trans------ ----- ---- ------- ------- ------- ------- ------- ------- 1 SCMG NA0 0 0 0 0 0 0 NA1 0 0 0 0 0 0 7 MAPV NA0 0 0 0 0 0 0 NA1 0 0 0 0 0 0 8 MAPM NA0 0 0 0 0 0 0 NA1 0 0 0 0 0 0 12 INAP NA0 0 0 0 0 0 0 149 MAPS NA0 0 0 0 0 0 0 192 BSSAS NA0 0 0 0 0 0 0 254 BSSAP NA0 283976 278907 0 0 0 0


Last Last Sub Sub Prohi Prohi sys name NW Start Stop------ ----- ---- ------ ------ 1 SCMG NA0 00:00 00:00 NA1 00:00 00:00 7 MAPV NA0 00:00 00:00 NA1 00:00 00:00 8 MAPM NA0 00:00 00:00 NA1 00:00 00:00 12 INAP NA0 00:00 00:00 149 MAPS NA0 00:00 00:00 192 BSSAS NA0 00:00 00:00 254 BSSAP NA0 00:00 00:00

Figure 23. Report 665: SCCP subsystem performance

6.3.12 SCCP single meters (666)

================================================================================= SCCP SINGLE METERS== Network: PLMN= MSC: all MSCs= Period: from 20001025 to 20001113= Time aggregation: whole period================================================================================

This report contains measurement data of the SCCP single meters.

Part 1: Processed SCCP messages

To local To a local subsystem.


NSS Network Doctor

From local From a local subsystem.STP STP messages.SCCP user User independent.SCCP total Total.

Part 2: Messages requiring GT translation

GT to local To a local subsystem.GT fr local From a local subsystem.GT STP STP messages.GT tot al Total.

Part 3: Reassembly errors

Timer T(reass) expires Timer T(reass) expires for segmented messageSegment out of sequence Received XUDT segment out of sequenceNo ReAss space Reassembly failures due lack of reassembly resourcesReAss failed Failed reassemblies of segmented messages

Part 4: Segmentation errors and hop counter violations

Segment not supported Attempts to send XUDT to denied destinationSegment failed Amount of failed message segmentationsHop counter violation Discarded SCCP messages because of hop counter is zero. (circular route)

Measurement used: p_msc_sccp_sub_single_meters


Part1: SCCP single meters for MSC1 from 20001025 to 20001113 Processed SCCP messages

To From SCCP SCCP local local STP user total--------- --------- --------- --------- --------- 296147 355210 736 4527 656620

Part2: SCCP single meters for MSC1 from 20001025 to 20001113 Messages requiring GT translation

GT to GT fr GT GT local local STP total--------- --------- --------- --------- 22432 21158 736 44326

Part3: SCCP single meters for MSC1 from 20001025 to 20001113 Reassembly errors

Timer Segment No T(reass) out of ReAss ReAss expires sequence space failed--------- --------- --------- --------- 0 0 0 0

Part4: SCCP single meters for MSC1 from 20001025 to 20001113


MSC reports

Segmentation errors and hop counter violations

Segment Hop not Segment countersupported failed violation--------- --------- --------- 0 0 0

Figure 24. Report 666: SCCP single meters

6.3.13 SCCP local subsystem availability (667)

================================================================================= SCCP LOCAL SUBSYSTEM AVAILABILITY== Network: testi-PLMN= MSC: MSC_1= Period: from 19990930 to 19990930= Time aggregation: whole period================================================================================

This report contains measurement data of the SCCP local subsystem availability:

NW NetworkSCCP fail Start of unavailability of a local SCCP due to failure.SCCP busy Start of unavail. of a local SCCP due to maintenance busy.SCCP cong Start of unavailability of a local SCCP due to congestion.SCCP stop Stop of unavailability of a local SCCPSCCP unava Duration of the unavailability of a local SCCP.

Measurement used: p_msc_sccp_sub_local_avail

Note: Activation and timer setting by MML ZOSM.=============================================================================== SCCP local subsystem availability for MSC_1 from 19990930 to 19990930

SCCP SCCP SCCP SCCP SCCP unavaNW fail busy cong stop hh:mi----- ------- ------- ------- ------- ---------NA0 0 0 0 0 0:00

Figure 25. Report 667: SCCP local subsystem availability

6.3.14 TCAP performance (658)

================================================================================= TCAP PERFORMANCE== Network: PLMN= MSC: all MSCs= Period: from 20001106 to 20001115= Time aggregation: whole period


NSS Network Doctor

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

Part 1 : Protocol errors in transaction portion, abort sent/received

Msg type Unregocnised message typeTa incor Incorrect transaction portionBad frmt Badly formated transaction portionId unrgn Unidentified transaction identifierResource limit Resource limitation

Part 2 : Protocol errors in comp. portion, reject sent/received

Unrgn Unrecognized componentMistypd Mistyped componentBad strctd Badly structured componentUnrecog Unidentified componentUnrecog lnk id Unidentified linked idUnrecog invoke id Unidentified invoke idReturn rsl expctd Return result expectedUnrecog invk id Unidentified invoke idRet err expctd Return error expected

Part 3 : TC user generated problems, reject sent/received

Duplic invk id Duplicate invoke idUnknown opertn Unknown operationMistypd param Mistyped parameterResourc limit Resource limitInitng release Initiating releaseLinked resp unexpd Linked response unexpectedLinked oper unexpd Linked operation unexpected

Part 4 : TC user generated problems (continues)

Unrecog error Unrecognized errorUnexpd error Unexpected errorMistpd prmRR Mistyped parameter RRMistpd prmRE Mistyped parameter RE

Part 5 : Utilization meters, messages sent/received

UNIDIRE UNIDIRECTIONAL messagesBEGIN BEGIN messagesCONTINU CONTINU messagesEND END messagesABORT ABORT messagesTC msg Total number of TC messagesTC tot Total number of TC components

Part 6 : Miscellaneous cancellations, rejects, aborts, errors

User cancel class1 User cancellations of class 1 operationsMsg disc Messages discarded by the TC (incorrect/unexpected)Prov abort rece Received TC-P-ABORT -messagesRece rejec oper Received operation rejectsTraAct port err Errors detected in transaction portion of the TC

Measurement used: p_msc_tcap_performance

Note: Activation and timer setting by MML ZOSM.=============================================================================== Part 1: TCAP performance for MSC1 from 20001106 to 20001115 Protocol errors, abort sent/received

ResourceMsg type Ta incor Bad frmt Id unrgn limit


MSC reports

**** **** **** **** ****rcvd rcvd rcvd rcvd rcvdtrans trans trans trans trans-------- -------- -------- -------- -------- 0 0 0 0 0 0 0 0 0 0

Part 2: TCAP report for MSC1 from 20001106 to 20001115 Protocol errors in comp.portion, reject sent/received

Bad Unrecog Unrecog Ret rsl Unrecog Ret errUnrgn Mistypd strctd lnk id invk id expctd invk id expctd**** **** **** **** **** **** **** ****rcvd rcvd rcvd rcvd rcvd rcvd rcvd rcvdtrans trans trans trans trans trans trans trans------- ------- ------- ------- ------- ------- ------- ------- 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Part 3: TCAP performance for MSC1 from 20001106 to 20001115 TC user generated problem, reject sent/received

Linked LinkedDuplic Unknown Mistypd Resourc Initng resp operinvk id opertn param limit release unexpd unexpd**** **** **** **** **** **** ****rcvd rcvd rcvd rcvd rcvd rcvd rcvdtrans trans trans trans trans trans trans------- ------- ------- ------- ------- ------- ------- 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Part 4: TCAP performance for MSC1 from 20001106 to 20001115 TC user generated problem (continues)

Unrecog Unexp Misty Mistyerror error prmRR prmRE**** **** **** ****rcvd rcvd rcvd rcvdtrans trans trans trans------- ----- ----- ----- 0 0 0 0 0 0 0 0

Part 5: TCAP performance for MSC1 from 20001106 to 20001115 Utilization meters, messages sent/received

UNIDIR BEGIN CONTINU END ABORT TC msg TC tot****** ****** ****** ****** ***** ****** ******rcvd rcvd rcvd rcvd rcvd rcvd rcvdtrans trans trans trans trans trans trans------ ------- ------- ------- ----- ------- ------- 0 126 52 226 1 405 328 0 242 55 74 7 378 366

Part 6: TCAP performance for MSC1 from 20001106 to 20001115 Miscellaneous cancellations, rejects, aborts, errors

User Prov Rece TraAct cancel Msg abort rejec portion class1 discard rece oper err


NSS Network Doctor

------- ------- ------- ------- ------- 0 0 0 0 0

Figure 26. Report 658: TCAP performance

6.3.15 TCAP transactions (672)

================================================================================= TCAP TRANSACTIONS== Network: PLMN= MSC: all MSCs= Period: from 20001111 to 20001120= Time aggregation: whole period================================================================================

New TraAct Number of new transactionsOpen TraAct Average number of open transaction IDsMean durat Mean duration of transactionsMax open Average number of maximum open transaction IDs

Measurement used: p_msc_tcap_transaction

Note: Activation and timer setting by MML ZOSM.=============================================================================== TCAP transactions for MSC1 from 20001111 to 20001120

Sub Sub New Open Mean MaxNW sys name TraAct TraAct durat open---- ------ ----- ------- ------- ------- -------NA0 7 MAPV 0 0 0 0NA0 8 MAPM 1 1 48 1NA0 12 INAP 0 0 0 0NA1 7 MAPV 0 0 0 0NA1 8 MAPM 0 0 0 0

Figure 27. Report 672: TCAP transactions

6.3.16 PCM statistics (668)

ndp668mx.mdl================================================================================= PCM STATISTICS== Network: PLMN= MSC: all MSCs= Period: from 19990922 to 19990922= Time aggregation: whole period================================================================================

Part 1: disturbances


MSC reports

Type ET typeInd ET indexlimit1 upper/lower Disturbance counter 1 limit upper/lowerlimit2 upper/lower Disturbance counter 2 limit upper/lowerlimit3 upper/lower Disturbance counter 3 limit upper/lowerlimit4 lower Disturbance counter 4 limit lowerSIG error Signal missing counter 1, 2, 3, and 4Frame align lost Frame alignment lost counter 1, 2, 3, and 4AIS recv AIS received counter 1, 2, 3, and 4Remote alarm Remote end alarm counter 1, 2, 3, and 4

Part 2: frame alignment signal errors

limit1 upper/lower Frame alignment lost limits: stat limit 1 upper/lowerlimit2 upper/lower Frame alignment lost limits: stat limit 2 upper/lowerlimit3 upper/lower Frame alignment lost limits: stat limit 3 upper/lowerlimit4 lower Frame alignment lost limits: stat limit 4 lowerFrame align lost Frame alignment lost counter 1, 2, 3, and 4

Part 3: slips

Negative Counter value for negative slipsPositive Counter value for positive slips

Part 4: CRC

local Total time that the CRC statistics has been onremote Total time that the CRC statistics has been on at the. remote end

Part 5: Others

deg min Degraded minuteserr sec Errored secondserr free Error free secondsser err Seriously errored seconds

Measurement used: p_msc_pcm_stat

=============================================================================== PCM statistics for MSC1KUTOJA from 19990922 to 19990922 Part 1: disturbances

limit1 limit2 limit3 limit4 ****** ****** ****** ****** Frame upper upper upper SIG align AIS RemoteType Ind lower lower lower lower err lost recv alarm---- ---- ------ ------ ------ ------ ----- ----- ----- ------- 20 64 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

65 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

66 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

67 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0


NSS Network Doctor

0 0 0 9985

68 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

69 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

70 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

71 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

72 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

PCM statistics for MSC1KUTOJA from 19990922 to 19990922 Part 1: disturbances


74 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

75 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

76 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

77 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

78 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

79 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0


MSC reports

0 0 0 0 0 0 0 9985

80 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

81 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985



85 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

86 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

88 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

90 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

104 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

105 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

107 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

108 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

PCM statistics for MSC1KUTOJA


NSS Network Doctor

from 19990922 to 19990922 Part 1: disturbances


110 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

136 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

137 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

138 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

139 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

142 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

143 50 1000 0 0 0 2 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

144 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985



146 50 1000 0 0 0 0 0


MSC reports

10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

158 50 1000 0 0 0 0 0 10 200 0 0 0 0 0 0 0 0 0 0 0 0 0 9985

159 50 1000 0 0 2 0 0 10 200 0 0 2 0 0 0 0 0 0 0 0 2 0 9985

PCM statistics for MSC1KUTOJA from 19990922 to 19990922 Part 3: slips

Type Ind Negative Positive---- ---- -------------- -------------- 20 64 0 0 65 0 0 66 0 0 67 0 16777216 68 0 973078528 69 0 989855744 70 0 989855744 71 0 989855744 72 0 973078528 73 0 0 74 0 0 75 0 0 76 0 16777216 77 0 989855744 78 0 0 79 0 0 80 0 0 81 0 16777216 82 0 0 85 656080896 0 86 656080896 0 88 656080896 0 90 656080896 0 104 0 0 105 656080896 0 107 656080896 0 108 656080896 0 109 656080896 0 110 656080896 0 136 0 989855744 137 0 0 138 0 0 139 0 0 142 0 0 143 0 973078528 144 0 16777216 145 656080896 0 146 0 0 158 656080896 0 159 0 989855744 PCM statistics for MSC1KUTOJA from 19990922 to 19990922 Part 4: CRC

Type Ind local remote---- ---- -------------- -------------- 20 85 0:00:00:00 0:00:00:00 86 0:00:00:00 0:00:00:00


NSS Network Doctor

88 0:00:00:00 0:00:00:00 90 0:00:00:00 0:00:00:00 105 0:00:00:00 0:00:00:00 107 0:00:00:00 0:00:00:00 108 0:00:00:00 0:00:00:00 109 0:00:00:00 0:00:00:00 110 0:00:00:00 0:00:00:00 145 0:00:00:00 0:00:00:00 158 0:00:00:00 0:00:00:00 PCM statistics for MSC1KUTOJA from 19990922 to 19990922 Part 5: others

local remote ***** ****** avail time unavail time deg min deg min ********** ************ err sec err sec local local err free err freeType Ind remote remote ser err ser err---- ---- --------------- --------------- -------- -------- 20 85 0:00:00:00 0:00:00:00 0 0 0:00:00:00 0:00:00:00 0 0 0 0 0 0

86 0:00:00:00 0:00:00:00 0 0 0:00:00:00 0:00:00:00 0 0 0 0 0 0

88 0:00:00:00 0:00:00:00 0 0 0:00:00:00 0:00:00:00 0 0 0 0 0 0

90 0:00:00:00 0:00:00:00 0 0 0:00:00:00 0:00:00:00 0 0 0 0 0 0

105 0:00:00:00 0:00:00:00 0 0 0:00:00:00 0:00:00:00 0 0 0 0 0 0

107 0:00:00:00 0:00:00:00 0 0 0:00:00:00 0:00:00:00 0 0 0 0 0 0

108 0:00:00:00 0:00:00:00 0 0 0:00:00:00 0:00:00:00 0 0 0 0 0 0

109 0:00:00:00 0:00:00:00 0 0 0:00:00:00 0:00:00:00 0 0 0 0 0 0

110 0:00:00:00 0:00:00:00 0 0 0:00:00:00 0:00:00:00 0 0 0 0 PCM statistics for MSC1KUTOJA from 19990922 to 19990922 Part 5: others

local remote


MSC reports

***** ****** avail time unavail time deg min deg min ********** ************ err sec err sec local local err free err freeType Ind remote remote ser err ser err---- ---- --------------- --------------- -------- -------- 0 0

20 145 0:00:00:00 0:00:00:00 0 0 0:00:00:00 0:00:00:00 0 0 0 0 0 0

158 0:00:00:00 0:00:00:00 0 0 0:00:00:00 0:00:00:00 0 0 0 0 0 0

Figure 28. Report 668: PCM statistics

6.3.17 LAPD error counters (669)

================================================================================= LAPD ERROR COUNTERS== Network: testi-PLMN= MSC: all MSC= Period: from 19990929 to 19990929= Time aggregation: whole period================================================================================

Report description:

Chn D channelType Channel type (pri or sec)RR F1 Receipt of unsolicited RR/RNR/REJ, F=1 (cntr A)DM F1 Receipt of unsolicited DM, F=1 (cntr B)UA F1 Receipt of unsolicited UA, F=1 (cntr C)UA F0 Receipt of unsolicited UA, F=0 (cntr D)DM F0 Receipt of unsolicited DM, F=0 (cntr E)peer re-est Peer initiated re-establishment (cntr F)SABME Unsuccessful retransmission of SABME (cntr G)DISC Unsuccessful retransmission of DISC (cntr H)STAT Unsuccessful retransmission of status inquiry (cntr I)NR fail NR error (cntr J)FRMR Receipt of FRMR response (cntr K)Frame Receipt of non_implemented frame (cntr L)I field Receipt of I field not permitted (cntr M)Size Receipt of frame with wrong size (cntr N)N201 error N201 error (cntr O)

Measurement used: p_msc_lapd_error

=============================================================================== LAPD error counters for MSC_1 from 19990929 to 19990929

RR F1 DM F1 SABME FRMR UA F1 DISC Frame UA F0 peer STAT NR I field N201


NSS Network Doctor

Chn Type DM F0 re-est NR fail Size error---- ---- ----- ------ ----- ----- ------- ------ 80 PRI 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

81 PRI 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Figure 29. Report 669: LAPD error counters

6.3.18 LAPD utilisation (670)

================================================================================= LAPD UTILISATION== Network: PLMN= MSC: all MSC= Period: from 19990929 to 19990929= Time aggregation: whole period================================================================================

Report description:

Chn D channelType Channel type (pri or sec)DL DATA Req The number of DL-DATA-REQUESTSDL DATA Ind The number of DL-DATA-INDICATIONSDL DATA UNIT Req The number of DL-DATA-UNIT-REQUESTSDL DATA UNIT Ind The number of DL-DATA-UNIT-INDICATIONSErrors CRC CRC errorsErrors frame Frame errorsDeleted DL DATA REQ Deleted DL-DATA-REQUESTSDeleted I frames Deleted I frames in the windowT200 exp T200 expiriesDMC ovflw DMC message buffer overflowsClck mis Clock signal missing messages

Measurement used: p_msc_lapd_util

=============================================================================== LAPD utilisation for MSC_1 from 19990929 to 19990929

DL DATA DL DATA UNIT Errors Deleted ******* ******* ****** ******* T200 exp Req Req CRC DL DATA REQ DNC oflw Chn Type Ind Ind frame I frames Clck mis---- ---- ------- ------- ------- ----------- -------- 80 PRI 89 0 0 0 0 89 0 0 0 0 0

81 PRI 199 0 0 0 0


MSC reports

178 0 0 0 0 0

Figure 30. Report 670: LAPD utilisation

6.3.19 LAPD traffic (671)

================================================================================= LAPD TRAFFIC== Network: PLMN= MSC: all MSC= Period: from 19990929 to 19990929= Time aggregation: whole period================================================================================

Report description:

Chn D channelType Channel type (pri or sec)I frames trans Transmitted I framesI frames received Received I framesUI frames trans Transmitted UI framesUI frames received Received UI framesI octets trans Transmitted I frame octetsI octets received Received I frame octetsUI octets trans Transmitted UI frame octetsUI octets received Received UI frame octetsTotal octets trans Transmitted total octet countTotal octets received Received total octet count

Measurement used: p_msc_lapd_traffic

=============================================================================== LAPD traffic report for MSC_1 from 19990929 to 19990929

Total I frames UI frames I octets UI octets octets ********* ********* ********* ********* ********* trans trans trans trans trans Chn Type received received received received received---- ---- --------- --------- --------- --------- --------- 80 PRI 89 0 1336 0 36616 89 0 1041 0 36321

81 PRI 199 0 3544 0 38612 178 0 2842 0 37994

Figure 31. Report 671: LAPD traffic


NSS Network Doctor

6.4 Clear codes

6.4.1 MSC call clear codes (014)

================================================================================= MSC CALL CLEAR CODES== Network: PLMN= Period: from 19981120 to 19981120= Sorted by: by clear code id================================================================================

This report shows MSC clear code statistics for each MSC, and for all MSCsif there are more than one MSC in the network.

For Clear Code descriptions, see ’Clear Code List CAG27903, Operating Manual’

CC Id Clear code identification numberCC Name Clear code nameSignal Share (%) of particular CC occurred in the signalling phase.Ring Share (%) of particular CC occurred in the ringing phase.Speech Share (%) of particular CC occurred in the speech phase.Share of all CC Share (%) of all calculated clear codes

Measurement used: p_msc_cc_calls

Running the report takes a moment. Patience please.

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

MSC Clear Code of Calls between 19981120 and 19981120 MSC_A

CC ShareId Signal Ring Speech of all CC(H) CC Name Occurences (%) (%) (%) (%)---- ------------------------------ ---------- ------ ------ ------ ---------0 NORMAL END OF THE CALL 630399 0.0 0.7 99.3 58.210 ABSENT SUBSCRIBER 67817 100.0 0.0 0.0 6.3102 CALL RECORD REL DURING CA 229 0.9 55.0 44.1 0.012 NO PAGING RESPONSE 27831 100.0 0.0 0.0 2.615 NORMAL UNSPECIFIED 23 17.4 78.3 4.3 0.0202 CLEAR REQUEST RECEIVED 3 0.0 33.3 66.7 0.0203 B CHANNEL UNACCEPTABLE 1 100.0 0.0 0.0 0.0205 RADIO IF CONGESTION 21447 100.0 0.0 0.0 2.0206 CALL REJECTED 1715 7.4 91.8 0.8 0.2208 MS RE-ESTABLISHMENT FAIL 1466 0.7 90.0 9.3 0.1300 OUTGOING CALLS BARRED 98 100.0 0.0 0.0 0.0301 OPER RESTR IN OUT DIRECT 36 100.0 0.0 0.0 0.0304 B-LINE OUT OF SERVICE 5261 100.0 0.0 0.0 0.5306 B-CALLS RESTRICTED 78 100.0 0.0 0.0 0.0307 B-NUMBER UNUSED 2829 100.0 0.0 0.0 0.330A A ONHOOK DURING SET UP 63725 100.0 0.0 0.0 5.930B A ONHOOK DUR_WAIT ANSWER 126215 0.0 99.9 0.0 11.730C B ONHOOK TIME OUT 445 0.0 0.2 99.8 0.0312 TELE SERV NOT PROV 471 100.0 0.0 0.0 0.0314 UNIDENTIFIED SUBSCRIBER 33 100.0 0.0 0.0 0.0318 TERMINAL SWITCH OFF 6187 9.6 37.2 53.3 0.6405 ERR REQUE FROM COPROCESS 41 97.6 0.0 2.4 0.0407 ERR ANSWER FROM CO-PROC 112 100.0 0.0 0.0 0.05 B-SUBSCRIBER BUSY 34682 73.1 26.9 0.0 3.26 B ANSWER TIME OUT 10885 0.0 100.0 0.0 1.0


MSC reports

Note

603 NO RESPONSE FROM CO-PROC 57 0.0 96.5 3.5 0.07 CALL WAITING TIME OUT 1358 0.0 100.0 0.0 0.170A FORCED CLEAR OF A CALL 20 65.0 5.0 30.0 0.070E CONFIGURATION ERROR 62 100.0 0.0 0.0 0.080D OUT CIRCUIT OUT OF ORDER 242 100.0 0.0 0.0 0.080E IN CIRCUIT OUT OF ORDER 532 100.0 0.0 0.0 0.080F CIRCUIT CONGESTION 108 100.0 0.0 0.0 0.0811 NETWORK FAILURE 770 100.0 0.0 0.0 0.1812 MAP FAILURE 571 100.0 0.0 0.0 0.1813 SWITCHING EQUI CONGESTION 492 100.0 0.0 0.0 0.0814 CIRCUIT GROUP CONGESTION 2081 94.3 5.7 0.0 0.2815 B ACCESS BARRED 47 100.0 0.0 0.0 0.0816 CALL UNSUC SEND INFO TONE 115 100.0 0.0 0.0 0.0817 N-UNALLOCATED NUMBER 2545 100.0 0.0 0.0 0.2

Figure 32. Report 014: MSC call clear codes

6.4.2 MSC call clear codes, shares and change (015)

If you have not run this measurement earlier, there is no data on this in the NMSdatabase, and running this report would cause an error. You must first run themeasurement by some other means.

================================================================================= MSC CALL CLEAR CODES, SHARES AND CHANGE== Network: PLMN= CC set: all clear codes= Threshold: change >= 0 % or <= - 0 %= Period: from 19981120 to 19981125================================================================================

This report shows MSC clear code statistics for MSCs (either as a total sum orper MSC). The report is arranged by the ’Avg Share out of all CC’.


CC Id Clear code identification numberCC Name Clear code nameSign Share (%) of CC occurred in the signalling phase. Whole period.Ring Share (%) of CC occurred in the ringing phase. Whole period.Spch Share (%) of CC occurred in the speech phase. Whole period.Delta The difference between first and last day %.



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

MSC Clear Code of Calls between 19981120 and 19981125 all MSCs, all clear codes


NSS Network Doctor

First Last Avg day day Share Share ShareCC out of out of out ofId Sign Ring Spch all CC all CC all CC Delta(H) CC Name (%) (%) (%) (%) (%) (%) (%)---- ------------------------------ ---- ---- ---- ------ ------ ------ -----0 NORMAL END OF THE CALL 0 1 99 58.0 57.9 58.3 0.330B A ONHOOK DUR_WAIT ANSWER 0 100 0 11.8 11.8 11.8 0.030A A ONHOOK DURING SET UP 100 0 0 6.4 6.5 6.4 -0.110 ABSENT SUBSCRIBER 100 0 0 5.3 5.1 4.9 -0.25 B-SUBSCRIBER BUSY 70 30 0 3.6 3.6 3.6 -0.0

Figure 33. Report 015: MSC call clear codes, shares and change

6.4.3 Clear code set per MSC (617)

================================================================================= CLEAR CODE SET PER MSC== Network: PLMN= Period: from 19980901 to 19981108================================================================================

The percentage share of some potential useful clear codes is calculatedfor each MSC over the given time interval.

Nrm End cc000 Normally ended callsRif Fail ccB13 Radio if failureRif Msg ccB1B Radio if msg failureOutC Fail ccA07 Call failure from outgoing circuitRmt Eqp ccB16 Remote equipment failureNet Fail cc811 Network failureHO Fail ccB14 HO failureNoRe HLR cc81B No response from HLRNoRe VLR cc81C No response from VLRBSS Map ccB1A BSS MAP protocol errorNo Res cc719 No resource for call

The percentage share of some congestion related clear codes is calculatedfor each MSC over the given time interval.

Rif Cong cc205 Radio if congestionCrct Cong cc80F Circuit congestionOutC Cong cc804 Outgoing circuit congestionOvld Cong cc60B Overload congestionCM Cong cc718 CM analysis congestionMAP Cong cc040 MAP congestion


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

MSC call clear codes per MSC from 19980901 to 19981108

Nrm Rif Rif OutC Rmt Net HO NoRe NoRe BSS No End Fail Msg Fail Eqp Fail Fail HLR VLR Map Res 000 B13 B1B A07 B16 811 B14 81B 81C B1A 719MSC Name (%) (%) (%) (%) (%) (%) (%) (%) (%) (%) (%)--------------- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----


MSC reports

MSC1 38.9 1.9 0.1 0.0 0.4 0.1 0.1 0.0 0.0 0.2 0.1

MSC congestion related call clear codes per MSC from 19980901 to 19981108

Rif Crct OutC Ovld CM MAP Cong Cong Cong Cong Cong Cong 205 80F 804 60B 718 040MSC Name (%) (%) (%) (%) (%) (%)--------------- ---- ---- ---- ---- ---- ----MSC1 0.1 0.1 0.0 0.0 0.0 0.0

Figure 34. Report 617: Clear code set per MSC

6.4.4 Clear codes of destinations (626)

================================================================================= CLEAR CODES OF DESTINATIONS== Network: PLMN= MSC: MSC4= Period: from 19971119 to 19971119================================================================================

Clear Code Id The clear code idenficationCalls in Sign The % of calls ending with a clear code in the signalling. phase.Calls in Ring The % of calls ending with a clear code in the ring phase.Calls in Spch The % of calls ending with a clear code in the speech phase.Calls Total The % of calls ending with a clear code.

Measurement used: p_msc_cc_dest

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

Clear Codes of Destinations for MSC4 from 19971119 to 19971119

Call Call Call Clear Clear in in in CallDest Code Code Sign Ring Spch Total CallNumber Id Name (%) (%) (%) (%) Total-------- ----- -------------------------- ----- ----- ----- ------ -----------358 0 NORMAL END OF THE CALL 0.0 0.7 73.7 26.1 161 5 B-SUBSCRIBER BUSY 12.3 0.0 0.0 5.2 32 6 B ANSWER TIME OUT 0.0 0.7 0.0 0.2 1 517 RADIO IF CONGESTION 36.8 0.0 0.0 15.6 96 520 MS RE-ESTABLISHMENT FAIL 0.0 0.0 1.4 0.5 3 778 A ONHOOK DURING SET UP 5.7 0.0 0.0 2.4 15 779 A ONHOOK DUR_WAIT ANSWER 0.0 83.3 0.0 18.7 115 792 TERMINAL SWITCH OFF 0.4 0.0 0.9 0.5 3 1539 NO RESPONSE FROM CO-PROC 0.0 0.7 0.0 0.2 1 2052 OUTGOING CIRCUIT CONGEST 7.7 0.0 0.0 3.2 20 2068 CIRCUIT GROUP CONGESTION 9.6 0.0 0.0 4.1 25 2071 N-UNALLOCATED NUMBER 0.4 0.0 0.0 0.2 1 2565 CRCT RELEASED BY CO-EXCHA 0.0 0.0 0.5 0.2 1 2567 CALL FAIL FROM OUT CRCT 14.9 7.2 0.0 8.0 49


NSS Network Doctor

2833 MODEM COMMUNICATION ERROR 0.0 0.0 20.3 7.1 44 2835 RADIO IF FAILURE 0.0 3.6 2.3 1.6 10 2836 HANDOVER FAILURE 0.0 0.7 0.9 0.5 3 2842 BSSMAP PROTOCOL ERROR 0.0 0.7 0.0 0.2 1 2843 RADIO IF MSG FAILURE 5.7 2.2 0.0 2.9 18 2844 RADIO IF FAIL REV TO OLD 5.7 0.0 0.0 2.4 15 3073 UNKNOWN DIALLING 0.8 0.0 0.0 0.3 2

Figure 35. Report 626: Clear codes of destinations

6.4.5 Signalling clear codes (625)

================================================================================= SIGNALLING CLEAR CODES== Network: PLMN= MSC: MSC1= Period: from 19971119 to 19971119================================================================================

Clear Code Id The clear code idenficationCalls in Signal The number of calls ending with a clear code in the. signalling phase.Calls in Ring The number of calls ending with a clear code in the ring. phase.Calls in Speech The number of calls ending with a clear code in the speech. phase.Calls Total The percentage of calls ending with a clear code.

Measurement used: p_msc_signal_cc

NOTE: You may retrieve similar statistics by MML (ZTUL:SER;) where the clear. code name is shown.. To see what is the actual meaning of the clear code in this report,. see the document ’Mapping of external data’, which is site-specific.

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

Signalling Clear Codes for MSC1 from 19971119 to 19971119

Calls Calls Calls Clear in in in CallSignalling Code Sign Ring Spch TotalProtocol Id Calls (%) (%) (%) (%)---------- ----- ---------- ----- ----- ----- ------ITUP 003H 2358 0.4 0.0 0.0 0.2 005H 39 0.0 0.0 0.0 0.0 006H 42 0.0 0.0 0.0 0.0 008H 19 0.0 0.0 0.0 0.0 015H 169 0.0 0.0 0.0 0.0 020H 2 0.0 0.0 0.0 0.0 021H 77719 9.2 18.0 0.0 7.1 022H 6 0.0 0.0 0.0 0.0 023H 85319 14.3 1.6 0.0 7.8 025H 88315 15.2 0.0 0.0 8.1 026H 271353 29.7 74.0 0.0 24.7 027H 388987 0.0 6.2 99.8 35.5


MSC reports

051H 6799 1.2 0.0 0.0 0.6 055H 1 0.0 0.0 0.0 0.0 057H 5069 0.9 0.0 0.0 0.5 062H 6 0.0 0.0 0.0 0.0 063H 1 0.0 0.0 0.0 0.0 069H 841 0.0 0.1 0.2 0.1 075H 3021 0.5 0.0 0.0 0.3 077H 103485 17.8 0.0 0.0 9.4 083H 236 0.0 0.0 0.0 0.0 084H 4 0.0 0.0 0.0 0.0 085H 44444 7.6 0.0 0.0 4.1 087H 18752 3.2 0.0 0.0 1.7

MS CC 000H 6 0.0 0.0 0.0 0.0 016H 847346 98.6 94.2 99.9 99.0 017H 5755 0.0 4.6 0.0 0.7 018H 20 0.0 0.0 0.0 0.0 021H 1089 0.0 0.9 0.0 0.1 024H 1 0.0 0.0 0.0 0.0 041H 1 0.0 0.0 0.0 0.0 081H 614 0.1 0.2 0.0 0.1 100H 245 0.3 0.0 0.0 0.0 101H 423 0.0 0.2 0.0 0.0 102H 572 0.9 0.0 0.0 0.1

R2 007H 14 17.3 0.0 0.0 0.5 030H 2835 0.0 0.0 99.5 94.7 033H 67 82.7 0.0 0.0 2.2 034H 64 0.0 100.0 0.0 2.1 035H 15 0.0 0.0 0.5 0.5

Figure 36. Report 625: Signalling clear codes

6.4.6 Trafficability statistics (622)

================================================================================= TRAFFICABILITY STATISTICS== Network: PLMN= Period: from 19981120 to 19990629= Time aggregation: hour================================================================================

This report counts for all MSCs:

Calls Number of call attemptsCalls CCGR Number of calls counted from clear code groupsAnsw Ratio of answered calls to all callsNot a Ratio of unanswered calls to all calls. A subscriber cleared call in ring phase or waiting. time expired.CCCR1..8 Ratio of calls in a clear code group to all calls.

Measurement used: p_msc_trafficability

Instructions:

This report can give useful information if the clear code groups are definedin a practical way (command ZTUM:RGC:RGC1= ,...,RGC8= ;)

Groups could be set e.g. in the following manner:


NSS Network Doctor

RGC1.. normal end (clear code 0)RGC2.. BSS related problemsRGC3.. NSS related problemsRGC4.. Miscellaneous problemsRGC5.. PNET related problemsRGC6.. MS related problemsRGC7.. Radio interface related problemsRGC8.. normal behaviour (clear codes 1..1FF, C00..FFF)

The measurement is started by command: ZTUS:SER,DAY

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

Trafficability Statistics for MSC11 from 19981120 to 19990629

Answ Calls Not a CCGR1 CCGR2 CCGR3 CCGR4 CCGR5 CCGR6 CCGR7 CCGR8YYYYMMDD HH:MI Calls CCGR (%) (%) (%) (%) (%) (%) (%) (%) (%)-------- ----- ---------- ----- ----- ----- ----- ----- ----- ----- ----- -----19981120 00:00 1081476 58.6 92.8 0.0 5.2 2.2 0.0 0.0 0.0 0.0 1083127 12.6

19981121 00:00 1005834 59.0 92.9 0.0 4.9 2.2 0.0 0.0 0.0 0.0 1007012 12.6

19981122 00:00 929500 58.0 92.7 0.0 5.2 2.2 0.0 0.0 0.0 0.0 930526 12.6

19981123 00:00 1049906 58.7 92.6 0.0 5.4 2.2 0.0 0.0 0.0 0.0 1051252 12.3

Figure 37. Report 622: Trafficability statistics

6.4.7 GSM observations analysis (218)

================================================================================= GSM OBSERVATIONS ANALYSIS== Network: PLMN= Period: from 19970101 to 19980331= Clear code selection: =’205’= Grouping by: A subsc inc PCM/TSL================================================================================

This report counts statistics on the GSM observations received from MSC.The user can select different grouping and clear code.

Note: Some of the most common clear codes are converted to textual form in thereport. Those that are not decoded are shown both in Hex and Dec values.Yoy can check their meaning, for example, from MSC (MML command ZTUT:CLR;)where the number is hexadecimal.

Measurement used: p_msc_gsm_obs2

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


MSC reports

Dx CC CCA subsc inc PCM/TSL (Hex) Dx CC Description count-------------------- ----- ------------------------------ -------1--1 205 Radio if congestion 70

Figure 38. Report 218: GSM observations analysis

6.5 Data Calls

6.5.1 MSC call clear codes of data calls (527)

The report shows all occurrences of the internal data call clear codes used. Clearcode distribution is presented according to the call phase. The report includes thenumber and plain text name of individual clear codes. The clear codes are updatedon the basis of the clear code number. This measurement is similar to the clearcode measurement.

It is included in Total trafficability performance of exchange reporting Controlledby MML command in the command group of TU (Field Reporting).

================================================================================= MSC CLEAR CODES OF DATA CALLS== Network: PLMN= Period: from 20010213 to 20010213= Sorted by: by clear code share================================================================================

This report shows MSC data call clear code statistics for each MSC,and for all MSCs if there are more than one MSC in the network.


CC Id Clear code identification numberCC Name Clear code nameSignal Share (%) of particular CC occurred in the signalling phase.Ring Share (%) of particular CC occurred in the ringing phase.Speech Share (%) of particular CC occurred in the speech phase.Share of all CC Share (%) of all calculated clear codes

Measurement used: p_msc_data_cc


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

MSC Clear Code of Data Calls between 20010213 and 20010213 MSC1

CC ShareId Signal Ring Speech of all CC(H) CC Name Occurences (%) (%) (%) (%)---- ------------------------------ ---------- ------ ------ ------ ---------0 NORMAL END OF THE CALL 234 0.0 0.0 100.0 63.4


NSS Network Doctor

B17 ADDRESS INCOMPLETE 61 100.0 0.0 0.0 16.5B13 RADIO IF FAILURE 24 0.0 0.0 100.0 6.5A04 TRUNK CRCT PROTOCOL ERROR 10 100.0 0.0 0.0 2.7300 OUTGOING CALLS BARRED 6 100.0 0.0 0.0 1.6206 CALL REJECTED 5 100.0 0.0 0.0 1.470B MODEM ERROR 5 0.0 0.0 100.0 1.430A A ONHOOK DURING SET UP 4 100.0 0.0 0.0 1.130B A ONHOOK DUR_WAIT ANSWER 3 0.0 100.0 0.0 0.815 NORMAL UNSPECIFIED 2 0.0 0.0 100.0 0.5D03 SERV OR FUNC NOT IMPLEM 2 100.0 0.0 0.0 0.5B16 REMOTE EQUIPMENT FAILURE 2 50.0 0.0 50.0 0.5B12 RPL OR MS FRAME SYN ERROR 2 0.0 0.0 100.0 0.522 B BUSY CCBS NOT POSSIBLE 2 100.0 0.0 0.0 0.5311 BEARER SERV NOT PROV 2 100.0 0.0 0.0 0.512 NO PAGING RESPONSE 1 100.0 0.0 0.0 0.3814 CIRCUIT GROUP CONGESTION 1 100.0 0.0 0.0 0.3318 TERMINAL SWITCH OFF 1 0.0 100.0 0.0 0.3C09 SERV/FACIL ACTIVA RESTR 1 100.0 0.0 0.0 0.3102 CALL RECORD REL DURING CA 1 0.0 100.0 0.0 0.3

Clear Codes of Data Calls, all MSCs between 20010213 and 20010213

CC ShareId Signal Ring Speech of all CC(H) CC Name Occurences (%) (%) (%) (%)---- ------------------------------ ---------- ------ ------ ------ ---------0 NORMAL END OF THE CALL 234 0.0 0.0 100.0 63.4B17 ADDRESS INCOMPLETE 61 100.0 0.0 0.0 16.5B13 RADIO IF FAILURE 24 0.0 0.0 100.0 6.5A04 TRUNK CRCT PROTOCOL ERROR 10 100.0 0.0 0.0 2.7300 OUTGOING CALLS BARRED 6 100.0 0.0 0.0 1.6206 CALL REJECTED 5 100.0 0.0 0.0 1.470B MODEM ERROR 5 0.0 0.0 100.0 1.430A A ONHOOK DURING SET UP 4 100.0 0.0 0.0 1.130B A ONHOOK DUR_WAIT ANSWER 3 0.0 100.0 0.0 0.815 NORMAL UNSPECIFIED 2 0.0 0.0 100.0 0.5D03 SERV OR FUNC NOT IMPLEM 2 100.0 0.0 0.0 0.5B16 REMOTE EQUIPMENT FAILURE 2 50.0 0.0 50.0 0.5B12 RPL OR MS FRAME SYN ERROR 2 0.0 0.0 100.0 0.522 B BUSY CCBS NOT POSSIBLE 2 100.0 0.0 0.0 0.5311 BEARER SERV NOT PROV 2 100.0 0.0 0.0 0.512 NO PAGING RESPONSE 1 100.0 0.0 0.0 0.3814 CIRCUIT GROUP CONGESTION 1 100.0 0.0 0.0 0.3318 TERMINAL SWITCH OFF 1 0.0 100.0 0.0 0.3C09 SERV/FACIL ACTIVA RESTR 1 100.0 0.0 0.0 0.3102 CALL RECORD REL DURING CA 1 0.0 100.0 0.0 0.3

Figure 39. Report 527: Data call clear codes

6.5.2 Data call clear code groups by number destination (528)

The report shows how the data call clear codes of a given number destination aredivided into clear code groups. If a number matches more than one numberdestination, it is updated in each of the matching number destinations. The clearcodes are divided into eight clear code groups. Each clear code belongs to oneclear code group only.


MSC reports

This measurement is similar to the clear code by number destinationmeasurement. It is included in Total trafficability performance of exchangereporting Controlled by MML command in the command group of TU (FieldReporting). Destinations are defined by MML TD command group (DestinationObject Lists).

================================================================================= DATA CALL CLEAR CODE GROUPS BY NUMBER DESTINATION== Network: PLMN= MSC: All MSCs= Period: from 20010212 to 20010221================================================================================

Destination MSISDN number of called destinationCC grpN Clear code group. Defined by MML what clear codes belong to. each group

Measurement used: p_msc_data_cc_dest

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

Data call clear code groups by number destination for MSC1 from 20010212 to 20010221

CC CC CC CC CC CC CC CCDestination grp1 grp2 grp3 grp4 grp5 grp6 grp7 grp8----------------- ------ ------ ------ ------ ------ ------ ------ ------101 0 0 0 0 0 0 0 0209 0 0 0 0 0 0 0 0358 0 0 0 0 0 0 0 0454 0 0 0 0 0 0 0 0968 0 0 0 0 0 0 0 0

Figure 40. Report 528: Data call clear codes by destination

6.5.3 Data service unit statistics (529)

This report relates to the Data service unit measurement.

================================================================================= DATA SERVICE UNIT STATISTICS== Network: PLMN= MSC: All MSCs= Time criteria: Whole period= Period: from 20010216 to 20010220================================================================================

This report shows for all MSCs or a selected single MSC the statistics perdata call type either as averaged or for the busy hour.

Call type Type of the data callCalls Number of calls, number of answered calls and


NSS Network Doctor

. calls that have met online stateCalls% Number of calls, number of answered calls and. calls that have met online state as a percentageSuccess Number of accepted, number of SFAILs, number of IFAILs. and number of EFAILs of the callsSuccess% Number of accepted, number of SFAILs, number of IFAILs. and number of EFAILs of the calls as a percentageTraf Average traffic in erlang (from circuit reservation torelease)

Measurement used: p_msc_data_service

=============================================================================== Data service unit usage in MSC1 from 20010216 to 20010220

Success Success% Calls Calls% ******* ******* ******* ******* Accep Accep Number Number Sfail Sfail Answ Answ Ifail Ifail TrafCall type On-line On-line Efail Efail (Erl)-------------------- -------- -------- -------- -------- ---------3.1 KHZ, 1 TCH CDSU 66 100.0 55 83.3 0.3 52 78.8 0 0.0 49 74.2 1 1.5 10 15.2

3.1 KHZ, 2 TCH CDSU 33 100.0 30 90.9 0.4 30 90.9 0 0.0 28 84.8 0 0.0 3 9.1

3.1 KHZ, 3 TCH CDSU 16 100.0 14 87.5 0.2 14 87.5 0 0.0 13 81.3 0 0.0 2 12.5

3.1 KHZ, NO GBS CDSU 145 100.0 131 90.3 0.7 140 96.6 2 1.4 117 80.7 2 1.4 10 6.9

FAX CDSU 7 100.0 7 100.0 0.0 7 100.0 0 0.0 7 100.0 0 0.0 0 0.0

GBS UDI, 1 TCH CDSU 63 100.0 38 60.3 0.3 55 87.3 1 1.6 55 87.3 0 0.0 17 27.0

GBS UDI, 2 TCH CDSU 16 100.0 9 56.3 0.3 11 68.8 2 12.5 11 68.8 0 0.0 5 31.3

GBS UDI, 3 TCH CDSU 50 100.0 32 64.0 0.7 46 92.0 0 0.0 46 92.0 0 0.0 12 24.0

UDI CDSU 69 100.0 60 87.0 0.3 63 91.3 0 0.0


MSC reports

63 91.3 0 0.0 9 13.0

Figure 41. Report 529: Data service unit statistics

6.5.4 GBS data service statistics (530)

This report relates to the GBS data service measurement.

================================================================================= GBS DATA SERVICE STATISTICS== Network: PLMN= MSC: All MSCs= Period: from 20010219 to 20010220================================================================================

Part 1: Attempts and usage of Fixed Network User Rate in Transparent connectionsFNUR kbit/s Fixed Network User RateSETUP Setup attempts for 9.6, 14.4 and EDGE channel codingsUSAGE Successful setup attempts of 9.6, 14.4 and EDGE channel codingsHO USE Result of channel configuration changes in handovers

Part 2: Maximum number of requested traffic channels (from MS to network)FNUR Fixed Network User RateTCH1...TCH8 Number of traffic channels from 1 to 8

Part 3: Attempts and usage of Air Interface User Rate in Non-TransparentconnectionsAIUR kbit/s Air Interface User RateSETUP Setup attempts for 9.6, 14.4 and EDGE channel codingsUSAGE REQ Successful setup attempts with requested channel coding. of 9.6, 14.4 and EDGEUSAGE DOWNG Setup attempts with requested channel configuration notenabled,. leading to downgraded channel coding of 9.6, 14.4 and EDGEMODIFY Number of user initiated level-up and downgrade attemptsHO USE REQ Result of channel configuration changes in handovers in which. requested channel configuration is enabledHO USE DOWNG Result of channel configuration changes in handovers in which. requested channel configuration is downgraded

Part 4: Maximum number of requested traffic channels (from MS to network)AIUR Air Interface User RateTCH1...TCH8 Number of traffic channels from 1 to 8

Measurement used: p_msc_gbs_data_aiur and p_msc_gbs_data_fnur

Note: Running this report takes time. Patience please.

=============================================================================== Part 1: FNUR attempts and usage in MSC1 from 20010219 to 20010220

SETUP USAGE HO USE ------ ------ ------ 9.6CH 9.6CH 9.6CH 14.4CH 14.4CH 14.4CHFNUR kbit/s EDGE EDGE EDGE------------ ------ ------ ------ 9.6 8 8 0


NSS Network Doctor

0 0 0 0 0 0

14.4 0 0 0 3 3 1 0 0 0

19.2 0 0 0 0 0 0 0 0 0

28.8 0 0 0 11 11 3 0 0 0

38.4 0 0 0 3 3 0 0 0 0

48.0 0 0 0 0 0 0 0 0 0

56.0 0 0 0 0 0 0 0 0 0

64.0 0 0 0 0 0 0 0 0 0

------------------------------------------------------------------------------ Part 2: Maximum number of channels requested in MSC1 from 20010219 to 20010220

FNUR kbit/s TCH1 TCH2 TCH3 TCH4 TCH5 TCH6 TCH7 TCH8------------ ------ ------ ------ ------ ------ ------ ------ ------ 9.6 8 0 0 0 0 0 0 0 14.4 3 0 0 0 0 0 0 0 19.2 0 0 0 0 0 0 0 0 28.8 0 8 3 0 0 0 0 0 38.4 3 0 0 0 0 0 0 0 48.0 0 0 0 0 0 0 0 0 56.0 0 0 0 0 0 0 0 0 64.0 0 0 0 0 0 0 0 0------------------------------------------------------------------------------ Part 3: AIUR attempts and usage in MSC1 from 20010219 to 20010220

USAGE USAGE HO USE HO USE SETUP REQ DOWNG MODIFY REQ DOWNG ------ ------ ------ ------ ------ ------ 9.6CH 9.6CH 9.6CH 9.6CH 9.6CH 9.6CH 14.4CH 14.4CH 14.4CH 14.4CH 14.4CH 14.4CHAIUR kbit/s EDGE EDGE EDGE EDGE EDGE EDGE------------ ------ ------ ------ ------ ------ ------ 9.6 0 16 1 0 0 0 16 0 0 0 0 0 0 0 0 0 0 0

14.4 0 0 0 0 0 0 51 51 0 21 0 0 0 0 0 0 0 0

19.2 21 20 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0


MSC reports

28.8 5 5 0 0 0 0 21 21 1 15 0 0 0 0 0 0 0 0

38.4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

43.2 0 0 0 0 0 0 45 44 0 44 0 0 0 0 0 0 0 0

57.6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

------------------------------------------------------------------------------ Part 4: Maximum number of channels requested in MSC1 from 20010219 to 20010220

AIUR kbit/s TCH1 TCH2 TCH3 TCH4 TCH5 TCH6 TCH7 TCH8------------ ------ ------ ------ ------ ------ ------ ------ ------ 9.6 16 0 0 0 0 0 0 0 14.4 51 0 0 0 0 0 0 0 19.2 0 21 0 0 0 0 0 0 28.8 0 20 6 0 0 0 0 0 38.4 0 0 0 0 0 0 0 0 43.2 0 0 45 0 0 0 0 0 57.6 0 0 0 0 0 0 0 0

Figure 42. Report 530: GBS data service statistics

6.6 Handovers

6.6.1 Handover failure ratio (633)

================================================================================= HANDOVER FAILURE RATIO== Network: PLMN= MSC: all MSCs= Period: from 20001029 to 20001107================================================================================

Measurement used: p_msc_ho

=============================================================================== HO failure ratio for MSC1 from 20001029 to 20001107

Inc Out Intra Intra Intra Inter Inter Re-est. CELL BSC HO MSC HO MSC HO MSC HO HO******** ******** ******** ******** ******** ******** att att att att att att fail % fail % fail % fail %-------- -------- -------- -------- -------- --------


NSS Network Doctor

102760 4578 20200 545 1003 398 2.3 5.1 3.5 8.7

Figure 43. Report 633: Handover Failure Ratio

6.6.2 Handover failure ratio for adjacencies (636)

================================================================================= HANDOVER FAILURE RATIO FOR ADJACENCIES== Network: PLMN= MSC: MSC1= Period: from 19980120 to 19980120= Threshold: HO failure ratio (to or from) > 10 %= Threshold: HO attempts (to or from) > 20 attempts================================================================================

This report gives a list of adjacencies where the HO failure ratio and thenumber of HO attempts exceeds the given threshold.The list is sorted out by the HO failure ratio - the worst first.The ratio is counted over the selected period of days.

The target cell is defined as LAC and CI as seen and reported by a MSC.The names for BTS, BCF, BSC and MSC are joined from the NMS/2000 database.

For each adjacency:HO => fail % HO failure ratio to adj. cell.HO => Att Number of HO attempts to adj. cell.HO <= fail % HO failure ratio from adj. cell.HO <= Att Number of HO attempts from adj. cell.

Note: If there are any discrepancies between the NMS/2000 database and the. MSC, the cell with the LAC and CI cannot be found in the NMS/2000.Note: This measurement counts all types of HOs.

Measurement used: p_msc_ho_nc

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

HO failure ratio for adjacencies from 19980120 to 19980120

Source Target****** HO=> <=HO Target ******BTS NAME **** HO=> **** <=HO ****** BTS NAMEBCF NAME Fail **** Fail **** LAC BCF NAMEBSC NAME (BTS) % Att % Att CI BSC NAME (BTS)------------------ ---- ------- ---- ------- ------ ------------------Sector1 100 86 0 0 4220 Sector2Site aa 1112 Site aaBSC4 (127) BSC4 (127)MSC1 MSC1

Sector2 100 306 0 0 4220 Sector3Site bb 2505 Site bbBSC6 (25) BSC6 (25)MSC1 MSC1

Figure 44. Report 636: Handover failure ratio for adjacencies


MSC reports

Note

6.6.3 Handover observation statistics (619)

If you have not run this measurement earlier, there is no data on this in the NMSdatabase, and running this report would cause an error. You must first run themeasurement by some other means.

================================================================================= HANDOVER OBSERVATION STATISTICS== Network: PLMN= BSC Name: BSC1= BCF Name: KILO008= BTS Name: KKALLIO14= LAC: 1= CI: 10014================================================================================

This report counts the occurrences of HO reasons and HO results from the HOObservation table (p_msc_ho_obs).

Note: The observation is activated via MML command ZTPO:STA:LAC=xxx,CI=yyy

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

TargetBSC nameBTS name Handover Handover Handover(CI,LAC) Type Reason Result------------- ---------- -------------------------- -----------------------------BSC1 intra-BSC Uplink quality : Rif Msg failure :KKALLIO16 Uplink strength : Rif failure :KILO009 Downlink quality : Call control :(1,10016) Downlink strength : Rif fail ret to old : Distance : Handover successful : 3 OM intervention : Equipment failure : Response to MSC : No radio resource : Call control : Terr resource notavail : Better cell : 3 CCCH overload : Directed retry : Processor overload : Switch circuit pool: BSS not equip : MS not equip : Tsc adaption notavail : Ciphering not supported: Terr crct allocated : Invalid msg content : Info or field missing : Incorrect Value : Unknown msg type : Unknown info element : Protocol error BSC-MSC :

Figure 45. Report 619: Handover observation statistics


NSS Network Doctor

6.7 Visitor location register

6.7.1 VLR failure profiles (632)

================================================================================= VLR FAILURE PROFILES== Network: PLMN= MSC: all MSCs= Period: from 20001107 to 20001107================================================================================

This report gives an overview of VLR failures:

Home Intra LU Fail % Intra VLR, home subscriber location update failure percentageHome Inter LU Fail % Inter VLR, home subscriber location update failure percentageRoam Intra LU Fail % Intra VLR, roaming subscriber location update failurepercentageRoam Inter LU Fail % Inter VLR, roaming subscriber location update failurepercentagePer. LU Fail % Periodic location update failure percentageArr. Fail % Arriving visitors location update failure percentageDep. Fail % Departing visitors location update failure percentageVLRU Answ Rate % Rate of answered VLRU’s in measurement data inquiry operation

TMSI Fail % TMSI failure percentageIMSI Att. Fail % IMSI attach failure percentageA-if Page Fail % Failure percentage for pagings via A-interfaceSGSN Page Fail % Failure percentage for pagings via SGSNMS Search Fail % MS Search failure percentage

Measurement used: p_msc_vlr

=============================================================================== VLR failure profiles of LUs for MSC1 from 20001107 to 20001107

Home Home Roam Roam Intra Inter Intra Inter Per. Arr. Dep. VLRU LU LU LU LU LU LU LU AnswDay Hour Fail Fail Fail Fail Fail Fail Fail Rateyyyy-mm-dd hh:mm % % % % % % % %---------- ----- ----- ----- ----- ----- ----- ----- ----- -----2000-11-07 00:00 0.0 0.0 0.0 0.0 0.0 100.0 0.0 100.0 01:00 0.0 0.0 0.0 0.0 0.0 100.0 0.0 100.0 02:00 0.0 0.0 0.0 0.0 0.0 100.0 0.0 100.0 03:00 0.0 0.0 0.0 0.0 0.0 100.0 0.0 100.0 05:00 0.0 0.0 0.0 0.0 0.0 100.0 0.0 100.0 06:00 0.0 0.0 0.0 0.0 0.0 100.0 0.0 100.0 07:00 0.0 50.0 0.0 0.0 0.0 99.6 0.0 100.0 08:00 0.0 30.0 0.0 0.0 0.0 98.5 0.0 100.0

Figure 46. Report 632: VLR failure profiles

6.7.2 VLR subscriber profiles per LA (635)

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


MSC reports

= VLR SUBSCRIBER PROFILES PER LA== Network: PLMN= MSC: all MSCs= Period: from 20001107 to 20001107================================================================================

The number of subscribers in LA is a critical factor for the networkperformance. Too many subcribers can cause severe paging problems.As a rule of thumb, there should not be more than 40000 subscribers in a LA.

LALocation AreaDay yyyy-mm-ddMeasurement period dayHour hh:mmMeasurement period timeSubscribers (avg)Average amount of subscribers in LAAvg counting statusStatus for collecting subscriber data from VLRU’s

Measurement used: p_msc_vlr_la

=============================================================================== LA subscribers for MSC1 from 20001107 to 20001107

Day Hour Subscribers LA yyyy-mm-dd hh:mm (avg) Avg counting status------ ---------- ----- ----------- ---------------------------- 1 2000-11-07 00:00 21 OK 01:00 21 OK 02:00 21 OK 03:00 21 OK 05:00 21 OK 06:00 21 OK 07:00 22 OK 08:00 25 OK 2 2000-11-07 00:00 213 OK 01:00 213 OK 02:00 213 OK 03:00 213 OK 05:00 214 OK 06:00 214 OK 07:00 214 OK 08:00 213 OK

Figure 47. Report 635: VLR subscriber profiles per LA

6.7.3 VLR authentication profile (646)

================================================================================= VLR AUTHENTICATION PROFILE== Network: PLMN= MSC: All MSCs= Period: from 20010213 to 20010213================================================================================

Authentic succ Successful authentications.Authentic fail Failed authentications.Triplets req Authentication triplet requests.Triplets reused Reused triplets.Triplets trans Transferred authentication triplets.


NSS Network Doctor

Answers succ Successful answers received in response to the VLR.Answers unansw Unanswered authentication triplet requests with an. unknown subscriber in the VLR.Unknown subs Subscribers whose data cannot be found in the AUC of the HLR.VLRUs nbr Number of VLRUs in the MSC.VLRUs sent Number of VLRUs in the MSC that have sent data.Data missing Data missing in triplet transfer counters.

Measurement used: p_msc_ac_vlr

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

Authentication Profile for MSC1

Triplets Authentic ******** Answers VLRUs ********* req ******** *****Day Hour succ reused succ Unknown nbr Datayyyy-mm-dd hh:mm fail trans unansw subs sent missing---------- ----- --------- --------- --------- ------- ----- --------2001-02-13 00:00 0 0 0 0 1 NO 0 0 0 1 0

01:00 0 0 0 0 1 NO 0 0 0 1 0

02:00 0 0 0 0 1 NO 0 0 0 1 0

03:00 0 0 0 0 1 NO 0 0 0 1 0

04:00 0 0 0 0 1 NO 0 0 0 1 0

05:00 0 0 0 0 1 NO 0 0 0 1

0

Figure 48. Report 646: VLR authentication profile

6.7.4 VLR authentication statistics (650)

This report shows from the selected BSCs the number of:

• authentication triplet requests

• subscribers whose data cannot be found in AUC

• successful answers on triplet requests

• transferred authentication triplets

Authentication statistics MSC1


MSC reports

Unknown SuccHLR address SPC address Requests subscr answ Triplets------------------ ----------- -------- ------- ------- --------358454400020 0 145 0 145 580

Figure 49. Report 650: VLR authentication statistics

6.8 Announcement

6.8.1 Announcement channel statistics (621)

================================================================================= ANNOUNCEMENT CHANNEL STATISTICS== Network: PLMN= MSC: MSC1= Period: from 19971119 to 19971119================================================================================

Ann Channel PCM-TSL PCM circuit of the announcement channelNumber of Calls /M074 The number of announcement attemptsLost Calls /M075 Lost calls ratioTotal Listen Time /M076 Total listening time in secondsAverage Listen Time /M076/M074 Average listening time in seconds

Measurement used: p_msc_ann

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

MSC Announcement Channel Statistics for MSC1 from 19971119 to 19971119

Ann Number Lost Total AverageChannel of Calls listen listenPCM-TSL Calls (%) Time(s) Time(s)------- ---------- ------- ---------- ---------- 87-01 68609 0.0 480337 7 87-02 136641 0.0 688430 5 87-03 1284 0.0 9481 7 87-04 91 0.0 781 9 87-05 0 0.0 0 0 87-06 2869 0.0 18456 6 87-07 3299 0.2 32258 10 87-08 8536 0.0 64032 8 87-09 46 0.0 2715 59 87-10 4995 0.0 50797 10 87-11 31 0.0 172 6 87-12 397 0.0 7109 18

Figure 50. Report 621: Announcement channel statistics


NSS Network Doctor

6.8.2 Integrated announcement device statistics (628)

================================================================================= INTEGRATED ANNOUNCEMENT DEVICE STATISTICS== Network: PLMN= MSC: all MSCs= Period: from 19971119 to 19971119================================================================================

Number of Calls The number of call attemptsNumber of Lost Calls The number of lost callsTotal Listen Time The total listening timeAvg Listen Time The average listening time per call

Measurement used: p_msc_int_ann

Note : The device having zero number of calls is not shown in the report.

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

Integrated Announcement Device Statistisc for MSC3 from 19971119 to 19971119

Number Number of Total Avg Device of Lost Listen Listen Index Calls Calls Time(s) Time(s)------- --------- --------- --------- --------- 200 69597 0 458903 6.6 201 142826 0 682174 4.8 202 4718 0 36232 7.7 207 7804 0 63644 8.2 208 112 0 6710 59.9 209 12028 0 130302 10.8 211 737 0 6295 8.5 212 592 0 10386 17.5 400 417 0 4073 9.8 404 36 0 315 8.8

Figure 51. Report 628: Integrated announcement device statistics

6.9 Traffic and success

6.9.1 Traffic category statistics (620)

================================================================================= TRAFFIC CATEGORY STATISTICS== Network: PLMN= MSC: All MSCs= Period: from 20010213 to 20010213================================================================================


MSC reports

Calls Call and HO attemptsAnwsd Answered callCC grp n Clear code group. Defined by MML what clear codes belong to. each groupAve Erl Average traffic in Erlang

Categories:intern Internaltrans TransitorigO Originating outgoingtermI Terminating incomingorig Originatingincom Incomingterm Terminatingoutgo OutgoingpbxO PBX originatingpbxT PBX terminatingvmsO VMS originatingvmsT VMS terminatingiMSChI Inter MSC handovers, incomingiMSChO Inter MSC handovers, outgoingscpO SCP originatingdevO Device originatingdata Data calls<number> Spare for future usage

Measurement used: p_msc_tc

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

Traffic Category Statistics for MSC1 from 20010213 to 20010213

CC CC CC CC CC CC CC CC grp grp grp grp grp grp grp grp Answd 1 2 3 4 5 6 7 8 AveCatego Calls (%) (%) (%) (%) (%) (%) (%) (%) (%) Erl------ -------- ----- ----- ----- ----- ----- ----- ----- ----- ----- --------intern 187 79.1 69.0 0.0 0.0 0.0 0.0 19.3 0.0 11.8 0.39trans 7 28.6 28.6 0.0 0.0 0.0 0.0 57.1 0.0 14.3 0.00origO 517 74.7 69.8 0.0 0.0 0.0 0.0 26.5 0.0 3.7 1.19termI 195 66.7 63.1 0.0 0.0 0.0 0.0 24.1 0.0 12.8 0.08orig 1129 47.5 74.0 0.0 0.0 0.0 0.0 23.6 0.0 2.5 2.00incom 294 44.9 45.2 0.0 0.0 0.0 0.0 19.7 0.0 35.0 0.21term 382 72.8 62.3 0.0 0.0 0.0 0.0 25.7 0.0 12.0 0.47outgo 524 74.0 69.3 0.0 0.0 0.0 0.0 26.9 0.0 3.8 1.19pbxO 3 100.0 100.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.00pbxT 31 90.3 90.3 0.0 0.0 0.0 0.0 9.7 0.0 0.0 0.14vmsO 0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.00vmsT 0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.00iMSChI 0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.00iMSChO 0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.00scpO 0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.00devO 0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.00data 327 81.0 69.1 0.0 0.0 0.0 0.0 28.4 0.0 2.4 0.9918 0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0019 0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0020 0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0021 0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0022 0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.00

Figure 52. Report 620: Traffic category statistics


NSS Network Doctor

6.9.2 Cell measurement statistics (627)

================================================================================= CELL MEASUREMENT STATISTICS== Network: PLMN= Period: from 19981019 to 19981019================================================================================

Bids*********All The total number of call bids.MOC The total number of mobile originating call bids.MTC The total number of mobile terminating call bids.

Succ Ratio*********All The ratio of radio channel has been successfully reserved.MOC Ratio for mobile originating calls.MTC Ratio for mobile terminating calls.

Answ Ratio*********All The ratio of the answered calls to total bids.MOC Ratio for mobile originating calls.MTC Ratio for mobile terminating calls.

Note: More detailed information per cell can be obtained from Nokia BSS.. It is a good idea to keep on the object list of this measurement. in MSC in order to get the generic part of the measurement (average. paging time,call conversation times)

Measurement used: p_msc_cell_cell

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

Cell Measurement Statistics for MSC1KUTOJA from 19981019 to 19981019

Succ Answ Ratio Ratio Bids (%) (%) ***** ***** *****Cell name All All AllLAC MOC MOC MOCCI MTC MTC MTC----------- -------- ------ ------HER3CG3007 8 100.0 62.53 8 100.0 62.530007 0 ---.- ---.-

Figure 53. Report 627: Cell measurement statistics

6.9.3 Control unit statistics (616)

================================================================================= CONTROL UNIT STATISTICS


MSC reports

== Network: PLMN= MSC: MSC1KUTOJA= Time criteria: Busy Period= Period: from 19981012 to 19981014================================================================================

This report shows for all MSCs or a selected single MSC the statistics percontrol unit either averaged or for busy hour.

Calls Number of CallsSucc Call success ratioAnsw (%) Ratio of answered call attempts to all callsSub Error (%) Calls ended due to subscriber errorsInt Error (%) Calls ended due to an internal error conditionExt Error (%) Calls ended due to an external error conditionTraf Average traffic in erlang

Measurement used: p_msc_ce

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

Control Unit Call Success % for MSC1KUTOJA from 19981012 to 19981014

Sub Int ExtBusy Period Object Answ Succ Error Error Error Trafyyyy-mm-dd hh:mm name Calls (%) (%) (%) (%) (%) (Erl)---------------- ------- -------- ------ ------ ------ ------ ------ ---------1998-10-14 12:45 BSU-1 45 53.3 64.4 0.0 22.2 13.3 0.51998-10-14 16:45 BSU-2 34 58.8 94.1 8.8 0.0 5.9 2.71998-10-14 12:45 CCSU-2 28 67.9 92.9 0.0 10.7 0.0 0.31998-10-14 16:45 IWCU-0 9 66.7 100.0 0.0 0.0 0.0 0.41998-10-14 16:45 PAU-0 9 100.0 100.0 0.0 0.0 0.0 0.7

Figure 54. Report 616: Control unit statistics

6.10 Destinations

These reports are under the MSC Statistics... → Traffic andSuccess... menu.

6.10.1 Destinations having high failure ratio (609)

================================================================================= DESTINATIONS HAVING HIGH FAILURE RATIO== Network: PLMN= Period: from 19981008 to 19981008= MSC: MSC XXXX= Thresholds= internal errors: 0 %= external errors: 0 %= subscriber errors: 0 %= success: 100 %=


NSS Network Doctor

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

The first part:of the report gives the destinations matching or exceeding one or thethresholds for internal, external or subscriber errors.

Destination MSISDN/ISDN destinationType sub=subscriber, nat=national, int=internationalDir out=outgoing, in=incomingCalls Nbr of call attemptsAnsw (%) Ratio of answered call attempts to all callsAccep (%) Ratio of succ. call attempts(CC 0...3FF) to all calls. (=100-Sfail-Ifail-Efail)Sfail (%) Ratio of subscriber errors to all callsIfail (%) Ratio of internal errors to all callsEfail (%) Ratio of external errors to all callsTraffic (Erl) Traffic. Measuring started at a succ. call attempt when. destination data received.Output is sorted by Accep (%).

The second part:of the report gives the profiles for destinations having calls andequal or worse success ratio than the given threshold.

Note: Handovers are included if the call is started in another exchange.. Intra-MSC handovers are not shown.Instructions: Use Field Reporting / Trafficability to see the clear codes. of the destination to be investigated.. (MML cmd to set the destination under measurement: ZTUM:DES:DET=xxx;)

Measurement used: p_msc_nd

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

Destinations having high failure ratio from 19981008 to 19981008

Answ Accep Sfail Ifail Efail TrafDestination Type Dir Calls (%) (%) (%) (%) (%) (Erl)----------------- ---- --- -------- ------ ------ ------ ------ ------ --------358 int out 0 0.0 0.0 0.0 0.0 0.0 0.04544 nat in 0 0.0 0.0 0.0 0.0 0.0 0.098 nat out 0 0.0 0.0 0.0 0.0 0.0 0.096 nat out 0 0.0 0.0 0.0 0.0 0.0 0.093 nat out 0 0.0 0.0 0.0 0.0 0.0 0.094 nat out 0 0.0 0.0 0.0 0.0 0.0 0.095 nat in 3 66.7 100.0 0.0 0.0 0.0 0.0

Profiles of destinations 95

Answ Accep Sfail Ifail Efail Trafdd hh Calls (%) (%) (%) (%) (%) (Erl)-- -- -------- ------ ------ ------ ------ ------ --------08 00 0 0.0 0.0 0.0 0.0 0.0 0.008 01 0 0.0 0.0 0.0 0.0 0.0 0.008 02 0 0.0 0.0 0.0 0.0 0.0 0.008 03 0 0.0 0.0 0.0 0.0 0.0 0.008 04 0 0.0 0.0 0.0 0.0 0.0 0.008 05 0 0.0 0.0 0.0 0.0 0.0 0.008 06 0 0.0 0.0 0.0 0.0 0.0 0.008 07 0 0.0 0.0 0.0 0.0 0.0 0.008 08 0 0.0 0.0 0.0 0.0 0.0 0.008 09 0 0.0 0.0 0.0 0.0 0.0 0.008 10 0 0.0 0.0 0.0 0.0 0.0 0.008 11 0 0.0 0.0 0.0 0.0 0.0 0.008 12 2 50.0 100.0 0.0 0.0 0.0 0.0


MSC reports

08 13 0 0.0 0.0 0.0 0.0 0.0 0.008 14 0 0.0 0.0 0.0 0.0 0.0 0.008 15 1 100.0 100.0 0.0 0.0 0.0 0.008 16 0 0.0 0.0 0.0 0.0 0.0 0.008 17 0 0.0 0.0 0.0 0.0 0.0 0.008 18 0 0.0 0.0 0.0 0.0 0.0 0.008 19 0 0.0 0.0 0.0 0.0 0.0 0.008 20 0 0.0 0.0 0.0 0.0 0.0 0.008 21 0 0.0 0.0 0.0 0.0 0.0 0.008 22 0 0.0 0.0 0.0 0.0 0.0 0.008 23 0 0.0 0.0 0.0 0.0 0.0 0.0

Figure 55. Report 609: Destinations having high failure ratio

6.10.2 Destination to destination success (613)

================================================================================== DESTINATION TO DESTINATION SUCCESS= Network: PLMN= MSC: MSC1= Period: from 19981019 to 19981019= Threshold: success ratio <= 70 %==============================================================================

The first part of the report gives the success % and traffic for alldestination to destination pairs.

Destination MSISDN/ISDN destinationType nat=national, int=international, sub=subscriber,. nus=not usedCalls Number of call attemptsTraffic (Erl) Traffic. Measuring started at a succ. call attempt when. destination data has been received.Answ (%) Ratio of answered calls to all call attemptsSucc (%) Ratio of Succ. call attempts (CC 0...3FF) to all calls. (=100-Sfail-Ifail-Efail)Sfail (%) Ratio of subscriber errors to all callsIfail (%) Ratio of internal errors to all callsEfail (%) Ratio of external errors to all calls

The second part of the report gives the profiles for those destinationpairs that have equal or worse success ratio than the given threshold.

Output is sorted by Succ (%).

Measurement used: p_msc_dtd

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

Destination to destination success for MSC1KUTOJA from 19981019 to 19981019

Fails (%) ***** SfailDestination in Traf Answ Succ IfailDestination out Type Calls (Erl) (%) (%) Efail---------------- ----- -------- -------- ------ ------ ------39347 sub 120 0.2 100.0 80.0 20.0


NSS Network Doctor

1090 sub 0.0 0.0

1 row selected.

Profiles of MSC/inc/out destinations having success ratio <= 70 % MSC1KUTOJA/39347/1090

Traf Answ Succ Sfail Ifail Efaildd hh Calls (Erl) (%) (%) (%) (%) (%)-- -- -------- -------- ------ ------ ------ ------ ------19 00 0 0.0 0.0 0.0 0.0 0.0 0.019 01 0 0.0 0.0 0.0 0.0 0.0 0.019 02 0 0.0 0.0 0.0 0.0 0.0 0.019 03 0 0.0 0.0 0.0 0.0 0.0 0.019 04 0 0.0 0.0 0.0 0.0 0.0 0.019 05 0 0.0 0.0 0.0 0.0 0.0 0.019 06 0 0.0 0.0 0.0 0.0 0.0 0.019 07 0 0.0 0.0 0.0 0.0 0.0 0.019 08 0 0.0 0.0 0.0 0.0 0.0 0.019 09 120 0.2 100.0 80.0 20.0 0.0 0.019 10 0 0.0 0.0 0.0 0.0 0.0 0.019 11 0 0.0 0.0 0.0 0.0 0.0 0.0

Figure 56. Report 613: Destination to destination success

6.10.3 Busy hour traffic of destinations (618)

================================================================================= BUSY HOUR TRAFFIC OF DESTINATIONS== Network: PLMN= MSC: all MSC= Period: 7 days ending on 19980514================================================================================

Columns:Dir Destination directionT Destination type (n=national, i=international, s=subscriber)Dest Number Destination numberBH Busy hour or busy periodTraf Traffic in Erlang on busy hour/period

Measurement used: p_msc_nd

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

T fri sat sun mon tue wed thu y Dest 08-May 09-May 10-May 11-May 12-May 13-May 14-MayDir p Number BH Traf BH Traf BH Traf BH Traf BH Traf BH Traf BH Traf--- - --------- -------- -------- -------- -------- -------- -------- --------inc n 4544 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 95 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 14 0.0

out i 358 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 990 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0


MSC reports

n 90 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 91 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 92 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 93 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 94 11 0.1 0 0.0 0 0.0 0 0.0 0 0.0 21 0.1 0 0.0 96 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 97 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 98 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0

Figure 57. Report 618: Busy hour traffic of destinations

6.11 Circuit groups

These reports are under the MSC Statistics... → Traffic andSuccess... menu.

6.11.1 Circuit group statistics (602)

================================================================================= CIRCUIT GROUP STATISTICS== Network: PLMN= MSC: All MSCs= Period: from 20010122 to 20010126================================================================================

Columns:Cgr name Circuit group nameCgr (nbr) dir Circuit group identification number and dircetionCgts (avg) Average number of circuits in the circuit groupCgts (max) Maximum number of circuits in the circuit groupCgts (avl) Average number of outgoing circuits in WO-EX stateCgts (min) Minimum number of free circuitsAvg traf (erl) out/in Average outgoing/incoming traffic in ErlangMax traf (erl) out/in Maximum outgoing/incoming traffic in ErlangAvg block (%) out M097a Average outgoing call congestion (blocking)Max block (%) out M097a Maximum outgoing call congestion (blocking)Subs err (%) Ratio of subscriber errors to all calls.Ext err (%) Ratio of external errors to all calls.Int err (%) Ratio of internal errors to all calls.Answd call lngt out/in Average length of answered call in seconds. M006 outgoing circuits. M008 incoming circuits

Measurement used: p_msc_cg

Instructions:- Circuit group states can be checked with command ZCEL:<Cgr nbr>- After M7A 4.25-5 blocking is counted from any circuit seizure attempt.. This means that if alternative circuit groups are defined the blocking %. of the first ones is just raw blocking and only the last group blocking. matters. Use MML command ZRI to learn what are the alternatives.- Errors: To investigate eg. Voice mail circuit groups for clear codes you may. put the destination to Field Reporting/destination supervision.

Note: Running this report is heavy and takes time. Patience please.


NSS Network Doctor

=============================================================================== Circuit Group Statistics for MSC1 Answd Avg Max Avg Max Answ Subs Ext Int call traf traf block block calls err err err lngth Cgr Cgts Cgts (erl) (erl) (%) (%) (%) (%) (%) (%) (sec)------ ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- -----name avg avl out out out out out out out out out(nbr) dir max min in in in in in in in------------ ---- ---- ------ ------ ----- ----- ----- ----- ----- ----- -----BDREFR02 87 87 0 0 0.0 0.0 .0 0.0 0.0 0.0 0(321) bi 87 86 0 0 50.0 0.0 0.0 0.0 72

BDREFR03 30 30 0 0 0.0 0.0 100.0 0.0 0.0 0.0 54(331) bi 30 29 0 0 100.0 0.0 0.0 0.0 36

BSC02144 28 28 0 0 0.0 0.0 .0 0.0 0.0 0.0 0(323) bi 28 28 0 0 .0 0.0 0.0 0.0 0

BSC03 27 27 0 0 0.0 0.0 33.3 0.0 0.0 0.0 0(330) bi 27 26 0 0 25.0 0.0 0.0 0.0 36

BSC03144 28 28 0 0 0.0 0.0 .0 0.0 0.0 0.0 0(332) bi 28 20 0 0 80.0 0.0 55.6 0.0 103

BSC04144 28 28 0 1 0.0 0.0 100.0 0.0 0.0 0.0 324(342) bi 28 26 0 0 50.0 0.0 50.0 0.0 792

Figure 58. Report 602: Circuit group statistics

6.11.2 Circuit group profile (649)

================================================================================= CIRCUIT GROUP PROFILE== Network: PLMN= MSC: All MSCs= Cgr number: 341= Cgr name: BSC04EFR= Cgr direction: bi= Period: from 20010122 to 20010126================================================================================

Columns:Hour hh:mm Start time of the measurement period.Cgts Average number of circuits in the circuit groupCgts avail Average number of outgoing circuits in WO-EX stateCgts min free Minimum number of free circuitsTraf (erl) out/in Average outgoing/incoming traffic in ErlangBlock (%) out M097a Average outgoing call congestion (blocking)Subs err (%) out/in Ratio of subscriber errors to all calls.Ext err (%) out/in Ratio of external errors to all calls.Int err (%) out/in Ratio of internal errors to all calls.

Measurement used: p_msc_cg

Instructions:- Circuit group states can be checked with command ZCEL:<Cgr nbr>- After M7A 4.25-5 blocking is counted from any circuit seizure attempt.. This means that if alternative circuit groups are defined the blocking %


MSC reports

. are just raw blocking.- Errors: To investigate eg. Voice mail circuit groups for clear codes you may. put the destination to Field Reporting/destination supervision.

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

Circuit Group Profile for circuit group: BSC04EFR of All MSCs

Subs Ext Int Traf Block err err err (erl) (%) (%) (%) (%) Cgts ---- ---- ---- ---- ----Day Hour Cgts min out out out out outyyyy-mm-dd hh:mi Cgts avail free in in in in---------- ----- ------ ------ ------ ------- ------ ------ ------ ------2001-01-26 08:15 91 91 85 0.4 0.0 0.0 1.0 0.0 1.1 0.0 4.0 2.0

2001-01-26 09:15 91 91 84 0.3 0.0 0.0 2.7 0.0 1.5 0.0 5.3 1.5

2001-01-26 06:15 91 91 91 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

2001-01-26 07:15 91 91 89 0.1 0.0 0.0 0.0 0.0 0.1 0.0 0.0 0.0

2001-01-25 18:15 91 91 88 0.3 0.0 0.0 5.3 0.0 0.1 0.0 33.3 11.1

2001-01-26 05:15 91 91 91 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

2001-01-25 16:15 91 91 83 0.4 0.0 0.0 14.5 0.0 2.7 0.0 16.1 4.8

2001-01-25 17:15 91 91 87 0.1 0.0 0.0 0.0 0.0 0.3 0.0 42.3 0.0

2001-01-25 15:15 91 91 83 0.3 0.0 0.0 1.2 0.0 1.5 0.0 7.3 1.8

Figure 59. Report 649: Circuit group profile

6.11.3 Circuit group to destination (645)

================================================================================= CIRCUIT GROUP TO DESTINATION== Network: PLMN= MSC: all MSC= Period: from 19981019 to 19981019================================================================================

Cgr name Circuit group nameCgr nbr Circuit group numberDestination MSISDN/ISDN number destinationDest type destination type. int=international, nat= national, sub= subscriberCalls Nbr of call attemptsTraf Average traffic (Erl).


NSS Network Doctor

Answ (%) Ratio of answered calls to all call attemptsSucc (%) Ratio of succ. calls(CC 0...3FF) to all attempts. (=100-Sfail-Ifail-Efail)Fails (%)*****Sfail Ratio of subscriber errors to all callsIfail Ratio of internal errors to all callsEfail Ratio of external errors to all calls

Measurement used: p_msc_ctd

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

Circuit Group Statistics for MSC1

Fails (%) ***** SfailCgr Cgr Dest Calls Answ Succ Ifailname nbr Destination type Traf (%) (%) Efail----------------- ---- ------------ ---- -------- ------ ------ ------DDA01 186 03 nat 0 0.0 0.0 0.0 0.0 0.0 0.0

DDA01 186 09 nat 0 0.0 0.0 0.0 0.0 0.0 0.0

Figure 60. Report 645: Circuit group to destination

6.12 Subscriber facility usage

6.12.1 Subscriber facility usage (603)

================================================================================= SUBSCRIBER FACILITY USAGE== Network: PLMN= MSC: MSC11 (12345)= Period: from 19981125 to 19981125================================================================================

Columns:

Subs Facility Name Subscriber facility nameActiv Nbr of activations of the facilityPassiv Nbr of passivations of the facilityInquir Nbr of inquiries of the facilityUsage count Total amount of usage of the facility by MS userRatio to calls (%) Subscriber facility use count ratio to nbr of all calls..Measurement used: p_msc_subs_fac


MSC reports

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

-

Subscriber Facility statistics MSC11

Subs Ratio Fac Usage to callCode Subs Facility Name Activ Passiv Inquir count (%)---- ------------------------------ ------- ------- ------- ------- ------- 5 BARRING OF ALL OUTGOING CALLS 0 0 0 10 0.00 7 BARRING OF ALL INCOMING CALLS 0 0 0 90 0.01 8 CALL FORWARDING UNCONDITIONAL 0 0 0 3866 0.38 10 CALL FORWARDING ON BUSY 0 0 0 661 0.06 15 CALL FORWARDING ON NO REPLY 0 0 0 1732 0.17 22 CALL WAITING 0 0 0 10625 1.03 32 CALL HOLD 0 0 0 6212 0.61 48 CALLING NBR ID PRESENTATION 0 0 0 269294 26.23 49 CALLING NBR ID RESTRICTION 0 0 0 1838 0.18 50 PER CALL BASIS CLIR 0 0 0 14 0.00 55 UNSTRUCTURED SS DATA 0 0 0 1253 0.12 82 CALL FORWARDING NOT REACHABLE 0 0 0 20471 1.99 87 BARRING OF INTERNATIONAL MOC 0 0 0 587 0.06 90 CALL RETRIEVAL 0 0 0 1546 0.15 99 OPERATOR DET. BARRING OF MOC 0 0 0 41 0.00 134 EMERGENCY CALLS 0 0 0 3716 0.36 149 SHORT MESSAGE MT/PP 0 0 0 13179 1.28 150 SHORT MESSAGE MO/PP 0 0 0 67262 6.55 214 AUTOMATIC FACSIMILE GROUP3 0 0 0 14 0.00 325 DUAL NUMBERING 0 0 0 544 0.05 490 NONTR DATA C.D.A 9600 B/S 0 0 0 45 0.00

Figure 61. Report 603: Subscriber facility usage

6.13 MSC benchmark

The MSC network benchmark (600) report collects some of the mostinteresting indicators into one and the same report.

6.13.1 MSC network benchmark (600)

For the weekly performance follow-up you need multiple indicators. The NMSnetwork benchmark report offers a compact way to get an overview of the MSCor all MSCs.

================================================================================= MSC NETWORK BENCHMARK== Network: PLMN= MSC: All MSCs= Period: from 20010217 to 20010221================================================================================

This report counts various Performance Indicators from the selected MSCor all MSCs.


NSS Network Doctor

Measurements used: p_msc_cg, p_msc_vlr, p_msc_tc, p_msc_cc_calls, p_msc_ho,p_msc_ce and p_msc_cell


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

SUBSCRIBERS

Number of subscribers in all HLRs. in beginning of period (2001-02-17 00:00)..../M023 -1. in end of period ......(2001-02-21 15:00)..../M023 -1

Number of subscribers in VLR of the selected MSC(s). in beginning of period (2001-02-17 00:00)..../M019 na. in end of period ......(2001-02-21 15:00)..../M019 -1

CALLS AND HANDOVERS BY TRAFFIC CATEGORIES. Attempts Answ RatioInternal .............................../M027 (M027a) 343 ( 78.4 %)Transit ................................/M029 (M029a) 1 ( 0.0 %)Originated outgoing ..................../M031 (M031a) 1916 ( 80.9 %)Terminated incoming ..................../M033 (M033a) 647 ( 56.7 %)Originated ............................./M035 (M035a) 2485 ( 73.4 %)Incoming ............................../M037 (M037a) 956 ( 38.4 %)Terminating ............................/M039 (M039a) 990 ( 64.2 %)Outgoing .............................../M041 (M041a) 1917 ( 80.9 %)PBX originating ......................../M110 (M110a) 25 ( 68.0 %)PBX terminating ......................../M112 (M112a) 162 ( 97.5 %)VMS originating ......................../M114 (M114a) na ( na %)VMS terminating ......................../M116 (M116a) na ( na %)SCP originating ......................../M122 (M122a) na ( na %)Device originating ...................../M124 (M124a) na ( na %)Inter MSC handovers, incoming ........../M118 (M118a) na ( na %)Inter MSC handovers, outgoing ........../M120 (M120a) na ( na %)

For more details run report 620.

AVERAGE CALL LENGTH

From cell measurement (speech) Time. Internal calls ............................../M069 88 sec. Originating outgoing calls ................../M021 208 sec. Terminating incoming calls ................../M022 90 sec

From traffic category measurement Time. Originating calls, circuit seized .........../M077 155 sec. Terminating incoming calls, circuit seized ../M077 62 sec. Originating calls, answered ................./M078 212 sec. Terminating incoming calls, answered ......../M078 110 sec

CALLS BY CLEAR CODES

Note that CC measurement runs with min. 24h period.This is why the results show yesterday’s situationif this report is run for today.. Calls ShareCall attempts (+ inter MSC HOs in B-MSC) ......./M043 2732. Normally ended calls ......................./cc000 1597 ( 58.5 %). Radio if congestion ......................../cc205 1 ( 0.0 %). Circuit congestion ........................./cc80F 2 ( 0.1 %). Outgoing circuit congestion ................/cc804 0 ( 0.0 %). CM analysis congestion ...................../cc718 0 ( 0.0 %). Overload congestion ......................../cc60B 0 ( 0.0 %)


MSC reports

. No resources for call ....................../cc719 0 ( 0.0 %)

. Call failure from outg.circuit ............./ccA07 0 ( 0.0 %)

. Network failure............................./cc811 3 ( 0.1 %)

. HO failure ................................./ccB14 0 ( 0.0 %)

. No response from HLR ......................./cc81B 0 ( 0.0 %)

. No response from VLR ......................./cc81C 2 ( 0.1 %)

. BSS MAP protocol error....................../ccB1A 0 ( 0.0 %)

. MAP congestion ............................./cc040 0 ( 0.0 %)

. Dropped calls .............................../M092 166 ( 6.1 %)

. Subs. out of coverage, re-est. failed ...../cc208 0 ( 0.0 %)

. Call cleared by MML ......................./cc609 0 ( 0.0 %)

. Unit restarted ............................/cc60E 0 ( 0.0 %)

. Echo canceller failure ..................../cc610 0 ( 0.0 %)

. Forced clear of a call ..................../cc70A 0 ( 0.0 %)

. Radio interface failure .................../ccB13 108 ( 4.0 %)

. Handover failure ........................../ccB14 0 ( 0.0 %)

. Remote equipment failure ................../ccB16 20 ( 0.7 %)

. Radio interface message failure .........../ccB1B 6 ( 0.2 %)

. Radio interface, reversion to old channel ./ccB1C 8 ( 0.3 %)

. Subs. signalling message content error ..../ccD00 1 ( 0.0 %)

. Subs. signalling message format error ...../ccD01 0 ( 0.0 %)

. Service or function not implemented ......./ccD03 0 ( 0.0 %)

. Subs. signalling protocold error ........./ccD04 0 ( 0.0 %)

. AOCC charging error ......................./ccD06 16 ( 0.6 %)

. No resp. to call est. alerting or connect ./ccD07 0 ( 0.0 %)

. GSM ERH 4.8 protocol timer expired ......../ccD08 7 ( 0.3 %)

Hints:For MSC comparison run report 617.For full clear code profile run report 014 or 015.For drop call clear code profiles run report 015.

HANDOVERS. Attempts SuccessIntra-MSC HO (excluding intra BSC) ............/M003A 12 ( 83.3 %)Inter-MSC HO ................................../M007A 0 ( na %)

CIRCUIT GROUPS.Average Availability .........................../M009 ( 78.0 %)Average usage ................................../M010 ( 0.9 %)

A-interface circuit group blocking. average ..................................../M097a ( -2.8 %). during peak traf period (2001-02-19 11:15) /M097a ( 0.0 %)(Note: based on assumption that circuit group has. string ’BSC’ in name)

Hints:For circuit group statistics run report 602 or 649.

VLR. Attempts FailIntra-VLR LU (incl. periodic LU) .............../M013A 0 ( na %)Inter-VLR LU .................................../M014A 0 ( na %)Arriving visitors ............................../M017A 0 ( na %)IMSI attach ..................................../M018A 0 ( na %)IMSI detach ...................................../M002 0

Average number of LU attempts per subsc. ......./M019A 0


NSS Network Doctor

Total DB operations ............................/M020A 0 ( na %)Extra load due to periodic LU .................../M016 ( 0.0 %)

ALL DATA CALLS. Bids Answer rateData calls ...................................../M130A 1355 ( 85.3 %)

Data call traffic (average)...................../M132 2 erl

LOCATION UPDATES. Attempts Success. Periodic ..................................../M062 0 ( 0.0 %). Home inter VLR ............................../M063 0 ( 0.0 %). Home intra ................................../M064 0 ( 0.0 %). Roam inter VLR ............................../M065 0 ( 0.0 %). Roam intra ................................../M066 0 ( 0.0 %)

Hints:For LU failure profiles run report 632.

LOCATION UPDATES IN BUSY PERIOD(period when sum of LUs highest). start time of period ...........(2001-02-21 15:00). end time of period .............(2001-02-21 16:00). Attempts Success. Periodic ..................................../M062 0 ( 0.0 %). Home inter VLR ............................../M063 0 ( 0.0 %). Home intra ................................../M064 0 ( 0.0 %). Roam inter VLR ............................../M065 0 ( 0.0 %). Roam intra ................................../M066 0 ( 0.0 %)

CALL STATISTICS. Attempts ShareCall attemps (A seized) ......................../M050 3441Switched calls (B seized) ....................../M048 2907 ( 84.5 %)Technically successful calls (ACCEP,SFAIL)....../M046 282 ( 8.2 %)Answered switched calls ......................../M070 1502 ( 43.7 %)Normally ended calls .........................../M047 0 ( 0.0 %)

Note: CC groups 5 and 8 need predefined setting.Note: M048 can be higher than M050 e.g. due to CFB or CFNA (one A side callcan cause multiple B side calls).

PAGING

Average paging time ............................/M073 1.4 secPaging success ................................./M056 ( 0.0 %)

Hints:For paging failure profile run report 632.

ANNOUNCEMENT

Nbr of calls .................................../M098 236. Lost calls ................................../M099 0 ( 0.0 %)Total listen time ............................../M100 2057 sec


MSC reports

BUSY PERIOD===========for orig., incoming terminating and transit call attempts (from p_msc_tc)start time of period ..............(2001-02-20 13:46)end time of period ................(2001-02-20 14:46). Originating calls ............................/M035 159. Incoming terminating calls .................../M033 45. Transit calls ................................/M029 0

. Originating traffic ........................../M071 5 erl

. Incoming terminating traffic ................./M072 1 erl

. Transit traffic ............................../M088 0 erl

corresponding period from p_msc_vlrstart time of period ..............()end time of period ................(). IMSI attach attempts / MS ..................../M080 na. IMSI detach / MS ............................./M081 na. Intra VLR LU / MS ............................/M082 na. Inter VLR LU / MS ............................/M083 na. Periodic LU / MS ............................./M087 naNote: counted only if all MSCs selected

corresponding period from p_msc_hostart time of period ..............()end time of period ................(). Intra BSC HOs / call (MTC,MOC) .............../M084 na. Inter BSC HOs / call (MTC,MOC) .............../M089 na. Inter MSC HOs / call (MTC,MOC) .............../M085 na

Figure 62. Report 600: MSC network benchmark

6.14 Security

6.14.1 MSC security counters (634)

================================================================================= MSC SECURITY COUNTERS== Network: PLMN= MSC: all MSCs= Period: from 19980120 to 19980120================================================================================

ST = Service TerminalNW = Network AccessMML = MML sessionSUB = subscriber security

Measurement used: p_msc_secur_counter

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

Security counters for MSC1 from 19980120 to 19980120


NSS Network Doctor

Sum overCounter period-------------------------------- ---------- NW: successful attempts 7128 NW: unauthorised command 0 NW: unauthorised user 0 ST: sessions 14 ST: unauthorised user 0MML: command check error 0MML: log writing failed 0MML: new users 0MML: sessions 652MML: unauthorised command 33MML: unauthorised user 11SUB: authentication failure 623SUB: imei on black list 0SUB: unknown imei 0SUB: unknown imsi 9698

Figure 63. Report 634: MSC security counters

6.15 Echo cancellation units

6.15.1 ECU routine test statistics (647)

This report gives statistics on timeslots in echo cancellation units.

================================================================================= ECU ROUTINE TEST STATISTICS== Network: PLMN= MSC: all MSCs= Period: from 19980324 to 19980326================================================================================

ECU routine test is activated e.g. for time 24:00->6:00 for one dayZUEM:EXEC=ON:STIME=24-0,FTIME=6-0,DUR=1,PARAL=5,REP=4

Test results per timeslot:. = OKU = untested because of lack of times = timeslot used for signalling linkR = not tested because seized- = not tested because barredE = error in testing systemF = faulty

Measurement used: p_msc_routine_test, p_msc_routine_unit

Note: This measurement is applicable only for EC08 (not for the newer EC1P).

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

Faulty Untested Untested Total Faulty timeslots timeslots timeslots


MSC reports

timeslots timeslots (%) nbr (%)--------- --------- --------- --------- --------- 5072 0 0 5072 100.0

ECU routine test results: MSC1 1998-03-26

********* Test results ********* Unit 00000000001111111112222222222333index PCM 12345678901234567890123456789012----- ----- -------------------------------- 88 88 sUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU 89 89 ssUUUUUUUUUUUUUUUUUUUUUUUUUUUUU 90 90 sUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU 91 91 UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU 92 92 UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU 93 93 -------------------------------

Figure 64. Report 647: ECU routine test statistics

6.16 Circuit supervision

6.16.1 Circuit supervision (648)

This report shows for each MSC per day whether the PCM timeslot has beenconstantly seized or constantly free.

================================================================================= CIRCUIT SUPERVISION== Network: PLMN= MSC: all MSC= Period: from 19981028 to 19981028================================================================================

This report shows for each MSC per day if the PCM timeslot has been constantlyseized or constantly free.

The measurement is activated by MML command (e.g. PCM 65, reporting daily):TES:PCM=65:1The measurement can be focused also on PCM timeslots or Circuit Groups.

Columns:PCM 2M trunkTSL time slot of 2M trunk

Measurement used: p_msc_cir_sup

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

Circuit seizure supervision for MSC1KUTOJA

Period Use Stop Stop length of PCM TSL day hr:mi (days) tsl---- ---- -------- ----- ------ ---------- 20 7 19981028 14:49 1 not seized


NSS Network Doctor

8 19981028 14:49 1 not seized 9 19981028 14:49 1 not seized 10 19981028 14:49 1 not seized 12 19981028 14:49 1 not seized 13 19981028 14:49 1 not seized 14 19981028 14:49 1 not seized 26 0 19981028 14:49 1 not seized 8 19981028 14:49 1 not seized 16 19981028 14:49 1 not seized 24 19981028 14:49 1 not seized

Figure 65. Report 648: Circuit supervision

6.17 IN services

6.17.1 Gapped IN services (652)

This report shows data from the following gapped IN services:

• call address or service key

• restriction type

• restricted calls in SPC overload and those due to limitations made by theoperator

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

Gapped IN services for MSC01

Day Hour Call Recd SPC Operatoryyyy-mm-dd hh:mi addr type overl limit---------- ----- ---------------- ----- ----- --------1999-04-20 00:00 0 0 0

Figure 66. Report 652, Gapped IN services


HLR reports

7 HLR reportsThis chapter describes the NSS Network Doctor reports derived from HLRmeasurements. The reports are presented roughly in the order they appear in theNSS Network Doctor user interface.

7.1 Administration of HLR measurements

NSS Network Doctor provides a variety of reports for investigating the activemeasurements in a HLR.

7.1.1 How to see which measurements send data to the database

To check which measurements are active in HLRs and send data you have toanalyse the PM tables. To do this, use the report Last HLR measurementrecord times (623).

================================================================================= LAST HLR MEASUREMENT RECORD TIMES== Network: PLMN= HLR: all HLR================================================================================

The date and time of last measurements available in the NMS databaseare reported for each measurement type.

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

GSM (ZTP). HLR measurement .......................p_hlr_rep 1998-06-25 10:00. Basic Services ......................p_hlr_basic 1998-06-25 10:00. Supplementary Services ...............p_hlr_supp 1998-06-25 10:00. Subscribers in the VLR ...........p_hlr_subs_vlr 1998-06-25 10:00. EIR ...................................p_hlr_eir 1998-06-25 08:00. EIR, Detailed Request .............p_hlr_eir_req no records. AC .................................p_hlr_ac_hlr 1998-06-25 08:00. AC, Detailed VLR part ............p_hlr_ac_count 1998-06-25 08:00

LOAD OBSERVATION (ZTL). Load .................................p_hlr_load 1998-06-25 10:32


NSS Network Doctor

OSI (ZOO). OSI level 1 ..........................p_hlr_osi1 no records. OSI level 2 ..........................p_hlr_osi2 no records. OSI level 3 ..........................p_hlr_osi3 no records. OSI level 4 ..........................p_hlr_osi4 no records

SECURITY (ZIR). Security Counter ................p_hlr_secur_rep 1998-06-25 12:00. Security Counters ...........p_hlr_secur_counter 1998-06-25 12:00

FIELD REPORTING (ZTU). Availability ........................p_hlr_avail 1998-06-25 00:00

Figure 67. Report 623: Last HLR measurement record times

7.1.2 How to see what network elements send data to the database

To check which HLRs send data to the database, use the report First andlast NSS measurement record times for each HLR (610). In this reportyou have to select the measurement type.

================================================================================= FIRST AND LAST NSS MEASUREMENT RECORD TIMES FOR EACH HLR== Network: PLMN= Table: p_hlr_load================================================================================

The date and time of first and last measurements available in the NMS databaseare reported for the selected measurement type by HLRs.

First meas.pd. (stop time) Stop time of the first measurement period.Last meas.pd. (stop time) Stop time of the last measurement period.Period duration max. Maximum duration of period.Period duration min. Minimum duration of period.

Note: If the size of selected table is large, the run time of this report can. be very long.

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

Records in Load (p_hlr_load)

Period Period First meas.pd. Last meas.pd. duration durationHLR name (stop time) (stop time) max. min.-------------------- ----------------- ----------------- -------- --------HLR1KUTOJA 1998-05-26 00:16 1998-06-24 15:32 60 60

Figure 68. Report 610: First and last NSS measurement record times foreach HLR


HLR reports

7.1.3 Measurement flow

To check that the measurement flow is functioning, use the Records for aHLR measurement (611) report. The number of records, minimum reportingperiod and maximum reporting period are reported for every hour havingmeasurement results for the selected measurement type.

================================================================================= RECORDS FOR A HLR MEASUREMENT== Network: PLMN= BSC: all HLRs= Measurement table: p_hlr_basic================================================================================

The number of records, minimum reporting period and maximum reportingperiod are reported for every hour having measurement results for theselected measurement type.

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

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

Min Max prd prdDay Hour (min) (min) RECORDS-------- ---- ----- ----- ----------19970118 0015 15 15 2 0030 15 15 2 0045 15 15 2 0100 15 15 2

Figure 69. Report 611: Records for a HLR measurement

7.2 Load and availability

7.2.1 HLR CPU and MB load (606)

To check that the load of CPUs does not exceed the recommended thresholds inthe HLR, run the report HLR CPU and MB load (606).

================================================================================= HLR CPU AND MB LOAD== Network: PLMN= Period: from 19970228 to 19970509================================================================================


NSS Network Doctor

As a basic rule the following applies:If the average load is over 70 % (or 50 % for Message Bus),there can be lost traffic.

Measurement used: p_msc_load

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

CPU and MB load % for HLR from 19970228 to 19970509

Min Max Peak Load Avg Load Peak Load Peak Load hourHLR Obj.name rate % rate % rate % yyyymmddhh------------- -------- -------- --------- --------- ---------------HLR1 ACU-1 1.0 9.0 28.0 1997030816 BDCU-1 1.0 9.0 12.0 1997031420 CCSU-3 1.1 6.0 13.0 1997030619 CM-1 1.2 6.0 100.0 1997032518 HLRU-1 2.8 11.0 50.0 1997032200 M-1 1.0 10.0 13.0 1997030701 OMU-1 6.0 9.0 93.0 1997031523 STU-1 1.0 8.0 15.0 1997031413

Figure 70. Report 606: HLR CPU and MB load

For MSC, a corresponding report MSC CPU and MB load (605) is provided.

7.2.2 HLR CPU and MB load profiles (615)

To check that the load of CPUs is not even approaching the recommendedthresholds, run the report HLR CPU and MB load profiles (615).

================================================================================= HLR CPU AND MB LOAD PROFILES== Network: PLMN= Period: from 19980223 to 19980223= Threshold: Avg load >= 2 %================================================================================

As a basic rule the following applies:If the average load is over 70 % (or 50 % for Message Bus),there can be lost traffic.These hours are highlighted with "!!!" .

Note: For MB there is no peak load available, and the peak load time of MBshown is based on the start time of the measurement.

Measurement used: p_hlr_load

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

CPU and MB load profile for HLR from 19980223 to 19980223

Peak Load Peak Load day time Peak Load Avg Load


HLR reports

HLR Obj.name yyyy-mm-dd hh:mm rate % rate % Obs------------- -------- ------------ --------- --------- -------- ---HLR1 OMU-0 1998-02-23 01:47 17.0 2.0 02:17 19.0 2.0 03:08 17.0 2.0 03:59 18.0 2.0

Figure 71. Report 615: HLR CPU and MB load profiles

For MSC, a corresponding report MSC CPU and MB load profiles (614) isprovided.

7.2.3 HLR availability profiles (641)

================================================================================= HLR AVAILABILITY PROFILES== Network: PLMN= HLR: all HLRs= Period: from 19971219 to 19980120================================================================================

Discon time Time when the unit was not in woex or spex state.Discon time duplex Time when none of the duplicated units were in woex. or spex.Unit restrt Unit restarts.Adm restrt Administrative restarts.Pros restrt Processor restarts.Prepros restrt Restarts of subordinate preprocessors.Duplex restrt Simultaneous restarts of duplicated units.

Measurement used: p_hlr_availNOTE: Only units having restarts or disconnection time are reported.

=============================================================================== Availability profiles for HLR1 from 19971219 to 19980120

Discon Discon Day Hour Unit time time Admin Pros Prepros DuplexUnit yyyy-mm-dd hh:mm restrt (sec) duplex restrt restrt restrt restrt---------- ---------- ----- ------ ------ ------- ------ ------ ------- -------ACU-0-0 1998-01-04 00:00 2 -1 0 2 0 0 0 1998-01-05 00:00 2 -1 0 2 0 0 0CCSU-5 1998-01-04 00:00 4 -1 -1 2 0 0 -1 1998-01-05 00:00 4 -1 -1 2 0 0 -1 1998-01-08 00:00 5 -1 -1 0 0 0 -1 1998-01-09 00:00 6 -1 -1 0 0 0 -1 1998-01-11 00:00 8 -1 -1 0 0 0 -1 1998-01-12 00:00 1 -1 -1 0 0 0 -1

Figure 72. Report 641: HLR availability profiles

For MSC, a corresponding report MSC availability (638) is provided.


NSS Network Doctor

7.3 Authentication centre

7.3.1 AUC triplet transfer profiles (643)

This report gives the statistics over authentication centre triplet transfer. The firstsection gives a general profile, whereas the second section gives a detailed profileper VLR address and signalling point code.

================================================================================= AUC TRIPLET TRANSFER PROFILES== Network: PLMN= MSC: all HLRs= Period: from 19980326 to 19980326================================================================================

This report gives the statistics over authentication centre triplet transfer.

The first report gives a general profile:Avg ACU in use (%) Space in AC database given as average usage of ACU.Triplet requests Nbr of VLR triplet requestsTriplet answers Nbr of VLR triplet answersTriplets total Total nbr of triplet transfers

The second report gives a detailed profile per VLR address and SignallingPoint Code:Triplet requests Nbr of VLR triplet requestsTriplet answers Nbr of VLR triplet answers

Measurement used: p_hlr_ac_hlr, p_hlr_ac_count

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

AC triplet transfer profile for HLR1 from 19980326 to 19980326

Avg ACUDay Hour in use Triplet Triplet Tripletsyyyy-mm-dd hh:mm (%) requests answers total---------- ----- ---------- ---------- ---------- ----------1998-03-26 00:00 83 8 8 32 01:00 83 3 3 12 02:00 83 1 1 4 03:00 83 1 1 4 04:00 83 0 0 0 05:00 83 2 2 8 06:00 83 8 8 32 07:00 83 34 34 136 08:00 83 49 49 196 09:00 83 65 65 260 10:00 83 69 69 276 11:00 83 66 66 264 12:00 83 83 83 332 13:00 83 65 65 260

14 rows selected.

-

HLR detailed AC profiles for HLR1


HLR reports

from 19980326 to 19980326

VLR SPC Day Hour Triplet Tripletaddress address yyyy-mm-dd hh:mm requests answers------------------ ---------- ---------- ----- ---------- ---------- 9289 1998-03-26 00:00 8 8 01:00 3 3 02:00 1 1 03:00 1 1 05:00 2 2 06:00 8 8 07:00 34 34

Figure 73. Report 643: AUC triplet transfer profiles

7.4 HLR service

These reports are under the HLR Statistics → Other HLR reports...menu.

7.4.1 HLR basic service statistics (630)

================================================================================= HLR BASIC SERVICE STATISTICS== Network: PLMN= Period: from 20001107 to 20001107================================================================================

Nbr Serv Act The number of activated basic services.Route Serv The routings of the basic services in incoming calls.

Measurement used: p_hlr_basic

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

HLR Basic Service Statistics for HLR1 from 20001107 to 20001107

Basic Nbr Serv Routeservice Serv Act Route Servname Act (%) Serv (%)------------------------- ---------- ------ ---------- ------Data c.d.a 300b/s 702 0.5 0 0.0Data c.d.a 1200b/s 702 0.5 0 0.0Data c.d.a 1200-75b/s 702 0.5 0 0.0Data c.d.a 2400b/s 738 0.5 0 0.0Data c.d.a 4800b/s 738 0.5 0 0.0Data c.d.a 9600b/s 828 0.6 0 0.0General bearer service 16425 11.2 31 43.1Data c.d.s 1200b/s 702 0.5 0 0.0Data c.d.s 2400b/s 702 0.5 0 0.0Data c.d.s 4800b/s 702 0.5 0 0.0Data c.d.s 9600b/s 702 0.5 0 0.0


NSS Network Doctor

Data c.d.s general 15750 10.7 0 0.0Telephony 19539 13.3 13 18.1Short message MT/PP 19404 13.2 28 38.9Short message MO/PP 19404 13.2 0 0.0Fax gr3 and altern.speech 16470 11.2 0 0.0Autom. faxmile gr3 16767 11.4 0 0.0Alternate Line Service 16218 11.0 0 0.0

Figure 74. Report 630: HLR basic service statistics

7.4.2 HLR supplementary service statistics (631)

================================================================================= HLR SUPPLEMENTARY SERVICE STATISTICS== Network: PLMN= Period: from 20001107 to 20001107================================================================================

Ave of Provis Average nbr of service provisionsMML Activ Sum of service activations by MMLMML Deact Sum of service deactivations by MMLUser Activ Sum of service activations by the userUser Deact Sum of service deactivations by the userUser Inquire Sum of services inquired by the user

Measurement used: p_hlr_supp

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

HLR Supplementary Service Statistics for HLR1 from 20001107 to 20001107

Suppserv Ave of MML MML User User Usercode Provis Activ Deact Activ Deact Inquire---- ---------- ---------- ---------- ---------- ---------- ----------CLIP 2626 0 0 0 0 0CLIR 2592 0 0 0 0 0CFU 2626 0 0 185 46 88CFB 2625 0 0 254 12 41CFNA 2625 0 0 22 3 0CFNR 2625 0 0 8 0 0CT 2627 0 0 0 0 0CW 2627 12 0 105 48 0HOLD 2628 0 0 0 0 0MPS 2625 0 0 0 0 0CUG 8 0 0 0 0 0AOCI 712 0 0 0 0 0AOCC 6 0 0 0 0 0BAOC 2624 0 0 44 0 26BOIC 2624 0 0 5 0 0BOIH 2623 0 0 0 0 0BORO 2624 0 0 0 0 14BAIC 1512 0 0 0 0 22BIRO 2624 0 0 0 0 38ODB 3216 0 0 0 0 0================================================================================ CCBS SERVICES


HLR reports

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

Ave of Provis Average nbr of OCCBS/TCCBS service provisionsSyst Activ Sum of service activations by systemSyst Deact Sum of service deactivations by systemMML Deact Sum of service deactivations by MMLUser Activ Sum of service activations by the userUser Deact Sum of service deactivations by the userRecall Deact Sum of service deactivations by recallUser Inquire Sum of services inquired by the user

Measurement used: p_hlr_rep

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

HLR CCBS Service Statistics for HLR1 from 20001107 to 20001107

OCCBS TCCBS-------------------------- ----------Ave of Provis : 2 2Syst Activ : - 0Syst Deact : 0 0MML Deact : 0 0User Activ : 0 -User Deact : 0 -Recall Deact : 0 0User Inquiry : 0 -

Figure 75. Report 631: HLR supplementary service statistics

7.5 VLR subscribers

This report is under the HLR Statistics → Other HLR reports... menu.

7.5.1 Subscriber profiles in VLRs (640)

================================================================================= SUBSCRIBER PROFILES IN VLRs== Network: PLMN= HLR: HLR51= Period: from 19981125 to 19981125= Time aggregation: whole period================================================================================

VLR ISDN address ISDN address of VLR

Measurement used: p_hlr_subs_vlr

=============================================================================== Subscribers in VLRs - profiles for HLAA1 from 19981125 to 19981125

AverageVLR ISDN address Subscribers------------------ -----------


NSS Network Doctor

2475527831000010 1316530300000 1316540915000 1393358908000 1393358950000 0393358953000 1

Figure 76. Report 640: Subscriber profiles in VLRs

7.6 HLR security counters

This report is under the HLR Statistics → Other HLR reports... menu.

7.6.1 HLR security counters (651)

This report shows the data from the following counters:

• service terminal

• network access

• MML session

• subscriber security

Security counters for HLR1 from 19981020 to 19981022

Sum overCounter period-------------------------------- ---------- ST: sessions 0

Figure 77. Report 651: HLR security counters

7.7 HLR usage

These reports are under the HLR Statistics → Other HLR reports...menu.

7.7.1 HLR usage statistics (629)

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


HLR reports

= HLR USAGE STATISTICS== Network: PLMN= Period: from 20010213 to 20010217================================================================================

DB opr Number of database operations for call handling and. mobility management.DB opr call (%) % of database operations for call handling.DB opr mblty (%) % of database operations for mobility management.Home LU Number of updates of home subscriber location.Succ home LU % of successful home subscriber location updates.Fail home LU % of failed home subsccriber location updates.Ave GPRS subs Average number of GPRS subscribers in HLR.Ave used space Average used space in HLR database in %.Ave subs Average number of subscribers in all VLRs.HLRU max Max. amount of HLRU units in HLR during reporting periodHLRU min Min. amount of HLRU units in HLR during reporting periodHLRU data min Min. amount of HLRU units sent measurement data


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

HLR Usage Statistics for HLR1 from 20010213 to 20010217

Succ Fail Ave DB opr DB opr home home Ave Used call mblty Home LU LU GPRS Space DB opr (%) (%) LU (%) (%) subs (%)--------- ------ ------ --------- ------ ------ -------- ------ 2202 77.4 22.6 498 100.0 0.0 2278 40.0

HLR Usage Statistics for HLR1 from 20010213 to 20010217

HLRU Ave HLRU HLRU data subs max min min-------- ------ ------ ------ 3376 1 1 1

Figure 78. Report 629: HLR usage statistics

7.7.2 HLR profiles (639)

================================================================================= HLR PROFILES== Network: PLMN= HLR: all HLRs= Period: from 19970828 to 19970828================================================================================

Home visit att Number of home subscriber visit attempts to other PLMNs.Home visit fail % Failure % of home subscriber visit attempts to other PLMNs.Home ret att Number of home subscriber returns from other PLMNs.


NSS Network Doctor

Home ret fail % Failure % of home subscriber returns from other PLMNs.Home LU att Number of home subscriber location updates.Home LU fail % Failure % of home subscriber location updates.DB oper call Database operations for call handling.DB oper mobili Database operations for mobility management.DB use % Used space in HLR database.Subsc in VLR Average nbr of subscribers in all VLRs during a period.HLRU sent Nbr of HLRU units that have sent data.HLRU in HLR Nbr of HLRU units in HLR.


=============================================================================== HLR profile for HLR1 1997-08-28

Home Home Home visit ret LU DB opr **** **** **** ***** DBHour att att att call (%) Subsc use HLRU HLRUhh:mm fail % fail % fail % DB opr mblty (%) in VLR % sent in HLR----- ------- ------- ------- --------- --------- ------- ------ ---- ------00:00 29 48 533 10998 95.1 103433 45.0 na 0 0.0 0.0 4.9 4.9

01:00 20 30 453 5952 92.4 103529 45.0 na 0 0.0 0.0 4.6 7.6

02:00 6 18 246 4333 94.3 103756 45.0 na 0 0.0 0.0 2.8 5.7

03:00 7 11 197 3756 94.8 103945 45.0 na 0 0.0 0.0 3.6 5.2

04:00 6 15 146 2019 92.8 104330 46.0 na 0 0.0 0.0 1.4 7.2

05:00 8 6 126 1322 90.5 104331 46.0 na 0 0.0 0.0 12.7 9.5

06:00 17 27 245 2145 88.6 104334 46.0 na 0 0.0 0.0 4.1 11.4

Figure 79. Report 639: HLR profiles

7.8 Equipment identity register

The following reports are under the HLR Statistics → Other HLRReports... menu.

7.8.1 EIR profile (644)

This report provides information on the mobile equipment that are authorised touse the network, showing the number of equipment and IMEI requests for eachcategory, that is equipment on the white, grey or black list.

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


HLR reports

= EIR PROFILE== Network: PLMN= MSC: all MSCs= Period: from 19980223 to 19980223================================================================================

Used space black % of space used on black list (reserved records/all).Used space grey % of space used on grey list.Used space white % of space used on white list.Black reqs Nbr of IMEI requests received for devices on black list.Black entries Nbr of devices and series on black list.Grey reqs Nbr of IMEI requests received for devices on grey list.Grey entries Nbr of devices and series on grey list.White entries Nbr of devices and series on white list.White reqs Nbr of IMEI requests received for devices on white list.

Measurement used: p_hlr_eir

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

HLR EIR Profile for HLR1 from 19980223 to 19980223

Used Used Used space space spaceDay Hour black grey white Black Black Grey Grey White Whiteyyyy-mm-dd hh:mm (%) (%) (%) entries reqs entries reqs entries reqs---------- ----- ----- ----- ----- ------- ----- ------- ----- ------- -----1998-02-23 00:00 0 0 0 0 -1 0 -1 2 0 01:00 0 0 0 0 -1 0 -1 2 0 02:00 0 0 0 0 -1 0 -1 3 0 03:00 0 0 0 0 -1 0 -1 2 0

Figure 80. Report 644: EIR profile

7.8.2 EIR requests by IMEI (654)

This report shows EIR requests by IMEI from all HLRs in a mobile network,sorted out by the list type of the equipment.

================================================================================= EIR REQUESTS BY IMEI== Network: PLMN= MSC: all HLR= Period: from 19990418 to 19990420================================================================================

Measurement used: p_hlr_eir_req

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

EIR REQ profile for HLR01 from 19990418 to 19990420


NSS Network Doctor

Day Hour List IMEIIMEI yyyy-mm-dd hh:mi type req AUTHOR REASON---------------- ---------- ----- ----- ----- ------ -------------33200111180126 1999-04-18 12:00 black 1 local 99 1999-04-20 14:00 black 1 local 99493002999263670 999-04-19 15:00 black 1 local 9949309990710285 1999-04-18 16:00 grey 1 local 99 18:00 grey 1 local 99 19:00 grey 1 local 99 1999-04-19 14:00 grey 1 local 99 15:00 grey 2 local 99 22:00 grey 1 local 99 1999-04-20 07:00 grey 1 local 99 22:00 grey 1 local 99

Figure 81. Report 654: EIR requests by IMEI


IndexNumerics

60-minute reporting interval 37

A

abbreviations 16actions to take before using 37active measurements

HLR 119MSC 38, 41

administrationHLR measurements 35, 119MSC measurements 32, 41

announcement 33, 99authentication centre 35, 124

C

checkingactive measurements in HLRs 119active measurements in MSCs 41CPU load in HLR 121CPU load in MSC 44HLR measurement flow 121HLRs sending data to the database 120MSC measurement flow 43MSCs sending data to the database 43SS7 link load 49

circuit groups 107clear codes 80command line conventions 15

D

data calls 35database administration 31destinations 103dtpad 13, 27

E

echo cancellation units 116equipment identity register 130

F

formulas 17further information 14

H

handovers 33, 93HLR

load and availability 35security counters 128service 125usage 128

I

IN services 118

L

load and availabilityHLR 121MSC 44

M

measurement flowHLR 121MSC 43

model reports 27, 32monitoring

quality of a cellular network 20user log data 30

MSCbenchmark 111clear codes 33load and availability 33

N

NMS database counters 24NMS/2000

load on 37NMS/2000 database 21, 39Nokia NMS release T12 13NSS Network Doctor

menus 32user interface 27using 23

P

PCM timeslot 117performance indicator 21prerequisites

for effective analysis of the network 19


NSS Network Doctor

R

reportingintervals 17, 37procedures 20

reportsautomatic running of 19focusing your selection 29front page description 19identification numbers 27layout 29menus 32models 27output of 29shortcuts for running 27

S

security 115selecting

measurement scope 29period of time 29

settinghistory windows 39

signalling 34, 49storing periods 39subscriber facility usage 110

T

terms and concepts 16text styles 14timeslots 116Top-level User Interface 20traffic and success 34, 100typographic conventions 14

U

user log 30, 36

V

VLR 33, 96VLR subscribers 127

W

what you need to know first 13where to find more 14


NSS NetDoc

Documents

Transcript of NSS NetDoc