NSS NetDoc

NSS Network Doctor
DN98614198
Issue 1-1 en
Nokia Networks Oy
Nokia Proprietary and Confidential
1 (134)
NSS Network Doctor
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This document is intended for the
use of Nokia Networks' customers only for the purposes of the agreement under which the
document is submitted, and no part of it may be reproduced or transmitted in any form or
means without the prior written permission of Nokia Networks. The document has been
prepared to be used by professional and properly trained personnel, and the customer
assumes full responsibility when using it. Nokia Networks welcomes customer comments as
part of the process of continuous development and improvement of the documentation.
The information or statements given in this document concerning the suitability, capacity, or
performance of the mentioned hardware or software products cannot be considered binding
but 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 instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Networks 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 correction
of errors. Nokia Networks WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN
THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL
(INCLUDING MONETARY LOSSES), that might arise from the use of this document or the
information in it.
This document and the product it describes are considered protected by copyright according to
the applicable laws.
NOKIA logo is a registered trademark of Nokia Corporation.
Other product names mentioned in this document may be trademarks of their respective
companies, and they are mentioned for identification purposes only.
Copyright Nokia Networks Oy 2001. All rights reserved.
2 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
Contents
Contents 3
List of tables 7
List of figures 8
1
1.1
1.2
1.3
1.3.1
1.3.2
1.4
1.4.1
1.4.2
About this manual 13

What you need to know first 13
Where to find more 14
Typographic conventions 14
Text styles 14
Command line conventions 15
Terms and concepts 16
Abbreviations 16
Terms 16
2
2.1
2.2
2.3
2.4
Introduction to NSS Network Doctor 19

Prerequisites for the effective analysis of the network 19
Monitoring the quality of a cellular network 20
Reporting procedures 20
Performance indicator 21
3
3.1
Using NSS Network Doctor 23

Navigating with reports, measurement tables, formulas and counters 24
4
4.1
4.2
4.3
4.4
4.5
4.5.1
4.5.1.1
4.5.1.2
4.5.1.3
4.5.1.4
4.5.1.5
4.5.1.6
4.5.1.7
4.5.1.8
4.5.1.9
4.5.1.10
4.5.2
4.5.2.1
4.5.2.2
4.5.2.3
4.5.2.4
4.5.3
User interface 27
Report layout 29
Focusing your report selection 29
User log 30
NMS database administration 31
Report menus 32
MSC Statistics 32
Administration of MSC Measurements 32
Load and Availability 33
MSC Clear Codes 33
Handover 33
VLR 33
Announcement 33
Traffic and Success 34
Signalling 34
Data Calls 35
Other MSC Reports 35
HLR Statistics 35
Administration of HLR measurements 35
Load and Availability 35
Authentication Centre 35
Other HLR Reports 36
NMS Database Administration 36
DN98614198
Issue 1-1 en
Nokia Networks Oy
3 (134)
NSS Network Doctor
4 (134)
4.5.4
User Log 36
5
5.1
5.2
5.3
Actions to take before using the reports 37

Load on the NMS/2000 37
MSC & HLR measurements check-up 38
Setting the history windows 39
6
6.1
6.1.1
6.1.2
6.1.3
6.2
6.2.1
6.2.2
6.2.3
6.2.4
6.3
6.3.1
6.3.2
6.3.3
6.3.4
6.3.5
6.3.6
6.3.7
6.3.8
6.3.9
6.3.10
6.3.11
6.3.12
6.3.13
6.3.14
6.3.15
6.3.16
6.3.17
6.3.18
6.3.19
6.4
6.4.1
6.4.2
6.4.3
6.4.4
6.4.5
6.4.6
6.4.7
6.5
6.5.1
6.5.2
6.5.3
6.5.4
6.6
MSC reports 41
Administration of MSC measurements 41
How to see which MSC measurements send data to the database 41
How to see what network elements send data to the database 43
Measurement flow 43
Load and availability 44
MSC CPU and MB load (605) 44
MSC CPU and MB load profiles (614) 46
MSC availability (638) 47
MSC profiles for rejected calls (637) 48
Signalling 49
SS7 link load (511) 49
X25 load profile (624) 50
MAP statistics (514) 51
MTP signalling link availability (655) 51
MTP signalling link utilisation (656) 53
MTP signalling link performance (657) 55
MTP signalling point status (659) 56
MTP signalling link set and route set availability (660) 57
MTP user parts signalling traffic (662) 59
SCCP signalling point performance (664) 60
SCCP subsystem performance (665) 63
SCCP single meters (666) 65
SCCP local subsystem availability (667) 67
TCAP performance (658) 67
TCAP transactions (672) 70
PCM statistics (668) 70
LAPD error counters (669) 77
LAPD utilisation (670) 78
LAPD traffic (671) 79
Clear codes 80
MSC call clear codes (014) 80
MSC call clear codes, shares and change (015) 81
Clear code set per MSC (617) 82
Clear codes of destinations (626) 83
Signalling clear codes (625) 84
Trafficability statistics (622) 85
GSM observations analysis (218) 86
Data Calls 87
MSC call clear codes of data calls (527) 87
Data call clear code groups by number destination (528) 88
Data service unit statistics (529) 89
GBS data service statistics (530) 91
Handovers 93
Nokia Networks Oy
DN98614198
Issue 1-1 en
6.6.1
6.6.2
6.6.3
6.7
6.7.1
6.7.2
6.7.3
6.7.4
6.8
6.8.1
6.8.2
6.9
6.9.1
6.9.2
6.9.3
6.10
6.10.1
6.10.2
6.10.3
6.11
6.11.1
6.11.2
6.11.3
6.12
6.12.1
6.13
6.13.1
6.14
6.14.1
6.15
6.15.1
6.16
6.16.1
6.17
6.17.1
Handover failure ratio (633) 93

Handover failure ratio for adjacencies (636) 94
Handover observation statistics (619) 95
Visitor location register 96
VLR failure profiles (632) 96
VLR subscriber profiles per LA (635) 96
VLR authentication profile (646) 97
VLR authentication statistics (650) 98
Announcement 99
Announcement channel statistics (621) 99
Integrated announcement device statistics (628) 100
Traffic and success 100
Traffic category statistics (620) 100
Cell measurement statistics (627) 102
Control unit statistics (616) 102
Destinations 103
Destinations having high failure ratio (609) 103
Destination to destination success (613) 105
Busy hour traffic of destinations (618) 106
Circuit groups 107
Circuit group statistics (602) 107
Circuit group profile (649) 108
Circuit group to destination (645) 109
Subscriber facility usage 110
Subscriber facility usage (603) 110
MSC benchmark 111
MSC network benchmark (600) 111
Security 115
MSC security counters (634) 115
Echo cancellation units 116
ECU routine test statistics (647) 116
Circuit supervision 117
Circuit supervision (648) 117
IN services 118
Gapped IN services (652) 118
7
7.1
7.1.1
7.1.2
7.1.3
7.2
7.2.1
7.2.2
7.2.3
7.3
7.3.1
7.4
7.4.1
7.4.2
7.5
HLR reports 119

Administration of HLR measurements 119
How to see which measurements send data to the database 119
How to see what network elements send data to the database 120
Measurement flow 121
Load and availability 121
HLR CPU and MB load (606) 121
HLR CPU and MB load profiles (615) 122
HLR availability profiles (641) 123
Authentication centre 124
AUC triplet transfer profiles (643) 124
HLR service 125
HLR basic service statistics (630) 125
HLR supplementary service statistics (631) 126
VLR subscribers 127
DN98614198
Issue 1-1 en
Nokia Networks Oy
5 (134)
NSS Network Doctor
7.5.1
7.6
7.6.1
7.7
7.7.1
7.7.2
7.8
7.8.1
7.8.2
Subscriber profiles in VLRs (640) 127

HLR security counters 128
HLR security counters (651) 128
HLR usage 128
HLR usage statistics (629) 128
HLR profiles (639) 129
Equipment identity register 130
EIR profile (644) 130
EIR requests by IMEI (654) 131
Index 133
6 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
List of tables
Table 1.
Text styles in this document
15
Table 2.
Command line conventions
15
Table 3.
Abbreviations
Table 4.
Terms used in this document
Table 5.
Example of history windows in the NMS/2000 database
DN98614198
Issue 1-1 en
16
Nokia Networks Oy
17
39
7 (134)
NSS Network Doctor
List of figures
Figure 1.
General work process 24
Figure 2.
Interrelationship between reports, measurement tables, formulas and

counters 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 each
MSC 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
8 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
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
DN98614198
Issue 1-1 en
Nokia Networks Oy
9 (134)
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 each
HLR 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
10 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
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 versions
12.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 now
taken from the traffic category measurement. New formulas have been
created.
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 been
made 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.
DN98614198
Issue 1-1 en
Nokia Networks Oy
11 (134)
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 versions
11.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 and
the formulas that NSS Network Doctor is using.
This version of NSS Network Doctor makes full use of the new M8 functions.
12 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
About this manual
About this manual

This document explains the functional usage of the NSS Network Doctor
software, the emphasis being on the practical tasks. This document introduces all
reports available in NSS Network Doctor by showing extracts of model reports.
The information contained in this document relates to Nokia NMS release T12
and to release M10 of the Nokia MSC software. This document should not be
used 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:
1.1
What you need to know first
Where to find more
Typographic conventions
Terms and concepts
What you need to know first

This document assumes that you are familiar with the following areas:
DN98614198
Issue 1-1 en
The concepts of the Nokia NMS/2000 and GSM networks in general
The usage of the UNIX operating system and file system navigation
The system administration tasks of the UNIX operating system. An

overview of the responsibilities of the system administrator can be found
in the HP-UX System Administration Concepts.
A text processing utility, such as vi or dtpad. These text processors are

used for editing certain configuration files.
Nokia Networks Oy
13 (134)
NSS Network Doctor
1.2
Where to find more

When you perform the users tasks described in this document, you may need to
refer to other documentation for further information. Below is a list of manuals
that you will find useful, as well as a brief description of the manuals contents.
NSS Network Doctor documentation
NSS Network Doctor, Feature Overview, DN00308755, for a brief

overview on the application
NSS Network Doctor, System Administrators Guide, DN98619372, for

administrators tasks related to running NSS Network Doctor
NSS Network Doctor Formulas, Reference Guide, DN98619509, for

counter formulas.
Changes in NSS Network Doctor, DN0128043, for detailed information on

the changes in MSC releases and on how that is reflected in the NMS/2000
database and NSS Network Doctor.
Other Nokia documents
1.3
Performance Management Basic Operating Principles and Procedures,

DN9784605, for a description of the formulas used in the Measurement
Data Post-processing in PC application.
Database Description for MSC/HLR Measurements, DN98619478, for

information on NMS database counters.
Traffic Measurement Report Formats, DN9817208.
Clear Code List, DN987436.
Typographic conventions
The following tables present the typographic conventions which have been used
in this manual to describe different actions and restrictions.
1.3.1
Text styles
The following table presents the typefaces and fonts and their indications.
14 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
About this manual
Table 1.
Text styles in this document
Style
Explanation
Initial Upper-case
Lettering
Application names
Italiced text
Emphasis
State, status or mode
File and directory names
Courier
Names of database tables

Parameters
User names
System output
User input
1.3.2
UPPER-CASE
LETTERING
Keys on the keyboard (ALT, TAB, CTRL etc.)
Bold text
User interface components
Initial Upper-case
Lettering in Italics
Referenced documents
<bracketed text>
Variable user input
Referenced sections and chapters within a document

The following UNIX command line prompts are used to indicate which user
should enter the command(s). Note that you should not include the prompt in the
command.
Table 2.
Prompt
As which user
As the root user
omc>%
As the omc user
&
As any user
DN98614198
Issue 1-1 en
Nokia Networks Oy
15 (134)
NSS Network Doctor
1.4
Terms and concepts

The lists below presents the terms and abbreviations used in this document.
1.4.1
Abbreviations
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
1.4.2
Terms
The lists below presents the abbreviations and terms used in this document.
16 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
About this manual
Table 4.
Terms used in this document
Term
Explanation
Cell Identity (CI)
A number which identifies a cell to the

networks within a location area (LA).
Clear code
Code that describes why the call set-up or the

call itself has been disconnected.
Day
The counting of data per day is based on the

period_start_time field in the
measurement tables. This field always tells the
starting hour of the measurement period.
Under one day there are hours from 00 to 23.
Key Performance Indicator
The performance of the network is calculated

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

belongs to one and only one Maintenance
Region (MR).
Measurement data
Data that includes both measurements and

observations. Synonym for performance data.
Measurement report
A report of a specified measurement type that

is generated after every output period.
NMS/2000
A product of Nokia Networks for the operation

and maintenance of cellular networks.
Performance data
See measurement data.
Reporting interval
The result output period of measurements

which the user can set. The period is set as
one of the measurement parameters using
MML.
SQL*Plus
An interactive program for accessing the

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

NMS/2000 Workstation based on windowing.
DN98614198
Issue 1-1 en
Nokia Networks Oy
17 (134)
NSS Network Doctor
For other terms, refer to Glossary, DN9763965.
18 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
Introduction to NSS Network Doctor

NSS Network Doctor is a reporting package which provides effective easy-to-use
tools to cover the NSS Performance Management (PM) functions of the NMS/
2000.
Self-documented reports with front page description and column headers
guarantee that the basic information is always where it is needed.
To install NSS Network Doctor, follow the instructions given in the NSS Network
Doctor, System Administrators Guide.
NSS Network Doctor offers a menu-based user interface where the user can move
up and down the menu hierarchy. See chapter 4 (User Interface) for a list of all
available reports.
If you need certain reports regularly, schedule the reports and execute them
automatically. For instructions on automatic running, refer to NSS Network
Doctor, System Administrators Guide.
2.1
Prerequisites for the effective analysis of the

network
To analyse your network as efficiently as possible, ensure that:
The measurements are available
The NMS/2000 is correctly configured to collect the alarm and

measurement data (this is normally done during commissioning)
The correct measurements are activated in the network elements
The transfer of measurement result files from the NSS to the NMS/2000
succeeds.
When the NMS/2000 and the network elements are correctly configured, the
NMS/2000 can provide very valuable, continuous, network-wide information
about the status of the network.
DN98614198
Issue 1-1 en
Nokia Networks Oy
19 (134)
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 you
may have is that the resources to fix the network problems are missing, not well
defined, or that no training has been given. To find solutions for this, Nokia
provides 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 the
technical quality of a network subsystem. Models for MSC reports and HLR
reports 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 or
processing application - the load on the system resources. To reduce excessive
unplanned interactive use of NSS Network Doctor, ensure that the most
frequently needed reports are available to all people who need the information.
The reports can be stored in a commonly known directory accessible to all
necessary people, or distributed via mail or the Intranet.
Well-planned and controlled reporting reduces the load on the NMS/2000 by
letting users get necessary data quickly without accessing the Top-level User
Interface. The reports also allow for the study of the data off-line in a file or
printout.
20 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
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 that
is composed of several counters. The MSC network benchmark (600) report,
for example, collects some of the most interesting indicators into one and the
same report.
The NMS/2000 database contains a very large number of counters which all are
elementary performance indicators. For practical purposes, however, they can be
hard to interpret. NSS Network Doctor offers reporting facilities for the most
important performance indicators that often are referred to as Key Performance
Indicators.
DN98614198
Issue 1-1 en
Nokia Networks Oy
21 (134)
NSS Network Doctor
22 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
Using NSS Network Doctor

Before you use NSS Network Doctor, ensure that the measurement flow from the
network elements in the investigated area is functioning.
When enough consistent statistical data is available, you may run the reports and
analyse the results, and then take any necessary actions based on the results. After
this, you should verify the impact of actions by a new run of reports and a new
analysis. This cycle of running reports, analysing them and modifying the
network on the basis of the analysis, continues through the whole lifespan of the
network. Only the pace and scope of the key performance indicators may change
from time to time.
DN98614198
Issue 1-1 en
Nokia Networks Oy
23 (134)
NSS Network Doctor
Figure 1.
General work process
Top-level reports are a good place to start the analysis. They display the basic
quality indicators for a MSC over a period of time. Save the reports and use them
as 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 composed
of a number of counters as well as directly from the NMS database counters
which you can find in the performance measurement tables. In some reports you
can find IDs of the pattern "Mxxx" (x = digit) referring to the used formulas. In
the headers of each report the used measurement table is referred to.
24 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
Figure 2.
Interrelationship between reports, measurement tables,

formulas and counters
To see the actual formulas, refer to NSS Network Doctor Formulas Users Guide,
and if interested in the counters, see Database Description for MSC/HLR
Measurements.
DN98614198
Issue 1-1 en
Nokia Networks Oy
25 (134)
NSS Network Doctor
26 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
User interface
User interface
This chapter describes the NSS Network Doctor user interface and lists the
reports in the order they appear on the submenus.
NSS Network Doctor offers a menu-based user interface where the user can move
up and down the menu hierarchy.
All reports are listed in the submenus. You can also run the reports directly from
the main menu option Run a report by identification number.
The reports produce an output file which opens in the editor window ( dtpad in
T12). 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 the
main menu.
As a model report does not cause any load on the database server, it is a good idea
to learn about the NSS Network Doctor reports by viewing model reports first.
Note
As each submenu contains a shortcut for running any of the NSS Network Doctor
reports, you can flexibly have access to any of them regardless of which menu you
are viewing. Enter the report ID after:
DN98614198
Issue 1-1 en
m) for viewing a model report
r) for generating an actual report from the database
Nokia Networks Oy
27 (134)
NSS Network Doctor
28 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
User interface
Figure 3.
4.1
NSS Network Doctor user interface
Report layout
NSS Network Doctor reports are self-explanatory standard-size (56 lines per page
and 80 characters per line) textual reports presented usually in a table format.
Each report starts with a front page containing a description which helps you
understand what the report is used for.
Note
In some reports, instead of numerical data, a counter value may occasionally be
shown as string "#####". This means that the number of digits coming from the
database to this counter field is too large to fit in. However, in all those cases the
figure 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 ASCII
file in a readable and printable format and can thus be easily transferred and
handled. For example, to be able to view the ASCII text file in MS Word, open
the file in Word and change the font to Courier New, 8 pt.
4.2
Focusing your report selection

After you have started to run a report, NSS Network Doctor will in most cases
prompt you for some of the following options before the actual report is
generated:
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 (to
make the report shorter) or define the sorting. A reference to the measurement
table used by the report appears on the description part of the report.
DN98614198
Issue 1-1 en
Nokia Networks Oy
29 (134)
NSS Network Doctor
4.3
User log
NSS Network Doctor provides you with reports for monitoring the user log data
from the use of this application. These reports are common to both BSS and NSS
Network Doctor.
The Log statistics (512) report gives basic information about the NSS
Network Doctor log file.
OS User
Name
---------neva
Host
Name
---------nea
teh
nea
Package
Version
---------v.1.18.41
Report
No
---------120
603
998
v.1.18.41B 120
120
014
020
021
021
022
023
024
25
Figure 4.
Start Time
Exec Time
yyyy-mm-dd hh:mm
(s)
------------------ --------1997-12-22 15:53
3
1997-12-22 15:56
2
1997-12-22 15:56
2
1997-12-18 15:09
1
1997-12-18 15:09
0
1997-12-18 16:00
5
1997-12-18 16:02
76
1997-12-18 16:03
17
1997-12-18 16:12
16
1997-12-18 16:16
10
1997-12-18 16:18
148
1997-12-18 16:20
147
1997-12-18 16:23
2
Report 512: Log statistics
The Network Doctor use statistics (513) report shows how many times
a report has been used and its average execution time.
How many times a report has been used and its average execution time
Report Times
Number
Used
------ -----120
1
122
4
127
1
163
2
196
1
200
2
204
17
207
1
212
5
213
3
218
6
252
10
512
1
515
8
516
5
517
25
519
11
Average
Execution
Time
(sec)
--------17
4
59
11
27
84
48
58
22
16
3
3
6
3
9
12
55
How many times a user has run a report

Report
30 (134)
Nokia Networks Oy
Times
DN98614198
Issue 1-1 en
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.
4.4
Report 513: Network Doctor use statistics
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 running
NSS Network Doctor. As a database user you will have adequate but not
extensive 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 Doctor
System Administrators Guide, DN98619372.
DN98614198
Issue 1-1 en
Nokia Networks Oy
31 (134)
NSS Network Doctor
4.5
Report menus
The list below highlights the types of reports that NSS Network Doctor provides
for the collection of performance data from the telecommunications network.
Note
If you are just learning the contents of the reports, you may run a model report
first by its ID to get an example of the type of report produced by NSS Network
Doctor. This reduces the load on the system.
MSC Statistics
-
HLR Statistics
-
4.5.1
Administration of MSC Measurements

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

Other HLR Reports
User Log
MSC Statistics
This menu contains reports derived from MSC measurements.
4.5.1.1
32 (134)
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)
Nokia Networks Oy
DN98614198
Issue 1-1 en
User interface
4.5.1.2
4.5.1.3
4.5.1.4
4.5.1.5
4.5.1.6
DN98614198
Issue 1-1 en
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)
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)
Handover
1.
Handover failure ratio (633)
2.
Handover failure ratio for adjacencies (636)
3.
Handover observation statistics (619)
1.
VLR failure profiles (632)
2.
VLR subscriber profiles per LA (635)
3.
4.
VLR authentication statistics (650)
VLR
Announcement
1.
Announcement channel statistics (621)
2.
Integrated announcement device statistics (628)
Nokia Networks Oy
33 (134)
NSS Network Doctor
4.5.1.7
4.5.1.8
34 (134)
Traffic and Success
1.
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.
8.
9.
Circuit group to destination (645)
10.
Subscriber facility usage (603)
11.
MAP statistics (514)
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)
Nokia Networks Oy
DN98614198
Issue 1-1 en
User interface
4.5.1.9
4.5.1.10
4.5.2
16.
LAPD error counters (669)
17.
LAPD utilisation (670)
18.
LAPD traffic (671)
Data Calls
1.
2.
3.
4.
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)
HLR Statistics
This menu contains reports derived from HLR measurements.
4.5.2.1
4.5.2.2
4.5.2.3
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)
1.
HLR CPU and MB load (606)
2.
HLR CPU and MB load profiles (615)
3.
HLR availability profiles (641)
1.
DN98614198
Issue 1-1 en
AUC triplet transfer profiles (643)
Nokia Networks Oy
35 (134)
NSS Network Doctor
4.5.2.4
4.5.3
4.5.4
36 (134)
Other HLR Reports
1.
HLR supplementary service statistics (631)
2.
Subscriber profiles in VLRs (640)
3.
HLR security counters (651)
4.
5.
HLR profiles (639)
6.
HLR basic service statistics (630)
7.
EIR profile (644)
8.
EIR requests by IMEI (654)
NMS Database Administration

1.
Show tables and views created by Network Doctor
2.
Database user creation (520)
User Log
1.
Log statistics (512)
2.
Network Doctor use statistics (513)
Nokia Networks Oy
DN98614198
Issue 1-1 en
Actions to take before using the reports

Before the reports can give reliable and comparable results, you have to check the
NMS/2000 for the following basic issues:
5.1
load on the NMS/2000
MSC & HLR measurements check-up
setting the History Windows
Load on the NMS/2000

This section gives you some basic information on how you should use the
measurements to fully benefit from the data the reports provide.
Note
The load caused by receiving measurements and by inserting them in the database
can be considerable, and can affect the proper functioning of the NMS/2000.
Many of the NSS measurements allow you to use very short measurement
periods, for example, 5 minutes. The 60 min interval in the network analysis is
often sufficient for practical needs. Experience from the field has shown that there
is no forcing need to constantly use shorter reporting intervals.
Whenever possible, it is a good idea to start new measurements at full hours. By
doing so it is easier to compare the counters in different measurements.
DN98614198
Issue 1-1 en
Nokia Networks Oy
37 (134)
NSS Network Doctor
If you choose to use a short period, you must bear in mind that this solution
requires more capacity and therefore there should always be a very good reason
behind the decision to go for short periods. If you want to change the
measurement period, you must stop the measurement, and you will lose the data
from the current period.
Note
A precise way to calculate how much data a measurement set will produce is to
use the Nokia NMS Excel spreadsheet that is available on request from Nokia
Customer Services. The spreadsheet gives the amount of data but not the load on
the NMS/2000. This is why the tool is applicable if the measurement set is going
to be changed and you want to see what is the net impact on the overall data
volume.
5.2
MSC & HLR measurements check-up

NSS Network Doctor provides a variety of reports for investigating the active
measurements 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), see
Section 6.1.2
For HLRs, run the report:

First and last NSS measurement record times for each HLR (610), see
Section 7.1.2
38 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
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 disk
space, and you must compromise when deciding which information is worth
storing the longest.
The following table gives you an idea about storing lengths which have proven
practical.
Table 5.
Type of data
Measurements
Example of history windows in the NMS/2000 database

Storing period
10 days
In some reports it is necessary to see more
than one weeks data in order to find out the
repetition patterns.
Observations
3 days
The observations are typically used for
troubleshooting and do not need a long history.
For long-term storage, Nokia provides the Network Data Warehouse product.
DN98614198
Issue 1-1 en
Nokia Networks Oy
39 (134)
NSS Network Doctor
40 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
MSC reports
This chapter describes the NSS Network Doctor reports derived from MSC
measurements. The reports are presented roughly in the order they appear on the
menu of the NSS Network Doctor user interface.
6.1
Administration of MSC measurements

measurements 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 to
analyse the PM tables. To do this use the report Last MSC measurement
record times (607).
===============================================================================
=
=
LAST MSC MEASUREMENT RECORD TIMES
=
=
Network:
PLMN
=
MSC:
All MSCs
=
===============================================================================
The date and time of last measurements available in the NMS database
are reported for each measurement type.
The measurement groups and their MML command classes (Zxx) are shown.
===============================================================================
TRAFFIC (ZTM, ZT2)
.
Circuit Group...........................p_msc_cg
.
Destination ............................p_msc_nd
.
Control Unit ...........................p_msc_ce
.
Cell (global) ........................p_msc_cell
.
Cell (cell specific) ............p_msc_cell_cell
.
Traffic Category .......................p_msc_tc
.
Announcement Channel ..................p_msc_ann
.
Integrated Announcement Device ....p_msc_int_ann
.
Circuit Group to Destination ..........p_msc_ctd
.
Destination to Destination ............p_msc_dtd
DN98614198
Issue 1-1 en
Nokia Networks Oy
2001-02-16
2001-02-16
2001-02-16
2001-02-16
2001-02-16
2001-02-16
2001-02-16
2001-02-16
no records
no records
07:15
10:00
10:00
10:00
10:00
09:46
09:50
09:49
41 (134)
NSS Network Doctor
.
.
Data service unit.............p_msc_data_service

GBS Data service.............p_msc_gbs_data_aiur
no records
no records
GSM (ZTP)
.
Handover (global) ......................p_msc_ho
.
Handover (cell) ...................p_msc_ho_cell
.
Handover (adj. cell) ................p_msc_ho_nc
.
VLR ...................................p_msc_vlr
.
VLR, Location Area .................p_msc_vlr_la
.
AC in the VLR ......................p_msc_ac_vlr
.
AC in the VLR, Detailed HLR part .p_msc_ac_count
2001-02-16
2001-02-16
2001-02-16
2001-02-16
no records
2001-02-16
no records
LOAD OBSERVATION (ZTL)

.
Load .................................p_msc_load
.
Rejected Calls ........................p_msc_rej
2001-02-16 10:14
2001-02-16 10:12
OSI (ZOO)
.
OSI, Level 1 .........................p_msc_osi1
.
.
.
no
no
no
no
SIGNALLING (ZOS)
.
MTP link availability ......p_msc_mtp_link_avail
.
MTP link performance..p_msc_mtp_link_performance
.
MTP link utilisation ........p_msc_mtp_link_util
.
MTP SP status ...............p_msc_mtp_sp_status
.
MTP link/route ....p_msc_mtp_sp_link_route_avail
.
MTP SP traffic .............p_msc_mtp_sp_traffic
.
MTP usr traffic ...p_msc_mtp_signal_traffic_user
.
MTP matrix traffic..p_msc_mtp_signal_traffic_mtx
.
SCCP SP ...........................p_msc_sccp_sp
.
SCCP subsystem ...................p_msc_sccp_sub
.
SCCP subsystem avail..p_msc_sccp_sub_local_avail
.
SCCP single meters ......p_msc_sccp_single_meter
.
TCAP performance .........p_msc_tcap_performance
.
TCAP transactions ........p_msc_tcap_transaction
.
LAPD traffic .................p_msc_lapd_traffic
.
LAPD utilisation ................p_msc_lapd_util
.
LAPD error counter .............p_msc_lapd_error
2001-02-16
2001-02-16
2001-02-16
2001-02-16
2001-02-16
2001-02-16
2001-02-16
2001-02-16
2001-02-16
2001-02-16
2001-02-16
2001-02-16
2001-02-16
2001-02-16
2001-02-15
2001-02-15
2001-02-15
CIRCUIT SUPERVISION (ZTE)

.
Circuit Seizure Supervision .......p_msc_cir_sup
.
PCM Statistics ...................p_msc_pcm_stat
2001-02-13 15:49
no records
SECURITY (ZIR)
.
Security ........................p_msc_secur_rep
.
Security Counters ...........p_msc_secur_counter
2001-02-16 12:00
2001-02-16 12:00
ECU (ZUE)
.
ECU routine Testing .........p_msc_routine_test
.
ECU routine Testing Detailed .p_msc_routine_unit
2001-02-15 13:00
2001-02-15 13:00
FIELD REPORTING (ZTU)

.
Availability ........................p_msc_avail
.
Trafficability .............p_msc_trafficability
.
Clear Codes of Calls .............p_msc_cc_calls
.
Clear Codes of Data Calls..........p_msc_data_cc
.
Clear Codes of Destinations .......p_msc_cc_dest
.
Clear Code Groups of Destin.....p_msc_ccgrp_dest
.
CC Grp of Dest. in Data Calls.p_msc_data_cc_dest
.
Subscriber Facilities ............p_msc_subs_fac
.
IN-service Gapping .................p_msc_in_gap
2001-02-16
no records
2001-02-16
2001-02-16
2001-02-13
no records
2001-02-16
2001-02-16
2001-02-16
42 (134)
Nokia Networks Oy
10:00
10:00
10:00
10:00
10:00
records
records
records
records
10:00
10:00
10:00
10:00
10:00
10:00
10:00
10:00
10:00
10:00
10:00
10:00
10:00
10:00
11:30
11:30
11:30
00:00
00:00
10:05
16:43
10:03
00:10
07:15
DN98614198
Issue 1-1 en
MSC reports
.
.
Signalling Specific CC ..........p_msc_signal_cc

Circ.Gr.Sign. Specific CC ....p_msc_signal_ccgrp
Figure 6.
6.1.2
2001-02-16 10:07
2001-02-16 10:07
Report 607: Last MSC measurement record times
How to see what network elements send data to the database

To check which MSCs send data to the database, use the report First and
last NSS measurement record times for each MSC (601). In this report
you 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 database
are 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)
First meas.pd.
MSC name
(stop time)
-------------------- ----------------MSC1KUTOJA
1998-05-26 00:22
Figure 7.
6.1.3
Period
Period
Last meas.pd.
duration duration
(stop time)
max.
min.
----------------- -------- -------1998-06-24 15:45
60
60
Report 601: First and last NSS measurement record times for
each MSC
Measurement flow
To check that the measurement flow from the MSC is functioning, use the report
Records for a MSC measurement (608).
===============================================================================
=
=
RECORDS FOR A MSC MEASUREMENT
=
=
Network:
PLMN
=
BSC:
all MSCs
DN98614198
Issue 1-1 en
Nokia Networks Oy
43 (134)
NSS Network Doctor
=
Measurement table: p_msc_cg
=
===============================================================================
The number of records, minimum reporting period and maximum reporting
period are reported for every hour having measurement results for the
selected measurement type.
Note: Running this report takes a while. Patience please.
===============================================================================
Day
Hour
-------- ---19970113 0103
0203
0303
Min
Max
prd
prd
(min) (min)
RECORDS
----- ----- ---------60
60
21
60
60
21
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 in
MSC, 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 lost
traffic. These hours are highlighted with "!!!" in the Obs column.
For hunting the heavy load hours choose the Time aggregation hourly and
Threshold 50 %.
For generic report choose the Time aggregation average and
Threshold 0 %.
Note: For MB there is no peak load available.
Measurement used: p_msc_load, 60min measurement period recommended
===============================================================================
44 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
CPU and MB load % MSC1

from 19981122 to 19981124
Avg Load Peak Load
Obj.name
rate %
rate % Obs
------------ -------- --------- --BDCU-0
1.0
12.0
BDCU-1
1.0
12.0
BSU-0
11.4
33.0
BSU-1
11.9
36.0
BSU-2
9.8
30.0
BSU-3
15.4
44.0
BSU-4
6.7
23.0
CCM-0
8.9
53.0
CCM-1
1.0
15.0
CCSU-0
8.0
28.0
CCSU-1
6.0
22.0
CCSU-2
7.8
28.0
CCSU-3
7.1
24.0
CCSU-4
9.1
28.0
CCSU-5
2.8
15.0
CCSU-6
10.1
30.0
CHU-0
3.8
18.0
CHU-1
6.0
42.0
CM-0
4.8
28.0
CM-1
4.1
18.0
M-0
2.6
14.0
M-1
2.0
13.0
MB
10.6
0.0
OMU-0
7.3
81.0
OMU-1
2.0
15.0
STU-0
4.9
21.0
STU-1
5.0
21.0
VLRU-0-0
11.6
37.0
VLRU-0-1
10.2
32.0
VLRU-1-0
11.1
45.0
VLRU-1-1
10.6
44.0
VLRU-2-0
11.6
37.0
VLRU-2-1
10.2
31.0
VLRU-3-0
11.3
36.0
VLRU-3-1
9.9
32.0
CPU and MB load % MSC2
from 19981122 to 19981124
Avg Load Peak Load
Obj.name
rate %
rate % Obs
------------ -------- --------- --BDCU-0
1.0
13.0
BDCU-1
1.2
15.0
BSU-0
6.8
23.0
BSU-1
1.0
12.0
BSU-2
6.8
25.0
BSU-3
12.7
35.0
BSU-4
13.6
39.0
BSU-5
12.8
34.0
CASU-0
2.0
15.0
CASU-1
2.6
16.0
CCM-0
1.0
14.0
CCM-1
1.0
13.0
CCSU-0
10.1
32.0
CCSU-1
8.9
27.0
CCSU-2
4.6
20.0
CCSU-3
8.1
27.0
CCSU-4
8.9
28.0
CCSU-5
1.0
12.0
CCSU-6
9.4
28.0
DN98614198
Issue 1-1 en
Nokia Networks Oy
45 (134)
NSS Network Doctor
CCSU-7
CCSU-8
CHU-0
CHU-1
CM-0
CM-1
CMU-0
CMU-1
IWCU-0
IWCU-1
M-0
M-1
MB
OMU-0
OMU-1
STU-0
STU-1
VLRU-0-0
VLRU-0-1
VLRU-1-0
VLRU-1-1
VLRU-2-0
VLRU-2-1
VLRU-3-0
VLRU-3-1
10.9
8.2
2.7
4.0
3.6
4.1
2.5
1.5
1.0
1.6
1.5
2.0
9.7
9.3
2.0
3.7
3.4
11.3
12.7
11.3
12.5
11.3
12.7
11.2
12.6
32.0
25.0
15.0
37.0
16.0
19.0
15.0
12.0
11.0
13.0
12.0
13.0
0.0
64.0
15.0
19.0
17.0
40.0
43.0
39.0
42.0
35.0
41.0
41.0
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 recommended
thresholds, 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 %
=
===============================================================================
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 MB
shown is based on the start time of the measurement.
Measurement used: p_msc_load
===============================================================================
CPU and MB load %
46 (134)
for MSC from 19971118 to 19971119
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
Peak Load
day
MSC
Obj.name yyyy-mm-dd
------------- -------- -----------MSC1
MB
1997-11-18
1997-11-19
Peak Load
time
Peak Load Avg Load
hh:mm
rate %
rate % Obs
--------- --------- -------- --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
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) is
provided.
6.2.3
MSC availability (638)
===============================================================================
=
=
MSC AVAILABILITY
=
=
Network:
PLMN
=
MSC:
MSC1
=
Period:
from 19980119 to 19980119
=
===============================================================================
Discon time
Discon time duplex
.
Unit restrt
Adm restrt
Pros restrt
Prepros restrt
Duplex restrt
Time when the unit was not in woex or spex state.

Time when none of the duplicated units were in woex
or spex.
Unit restarts.
Administrative restarts.
Processor restarts.
Restarts of subordinate preprocessors.
Simultaneous restarts of duplicated units.
Measurement used: p_msc_avail

NOTE: Only units having restarts or disconnection time are reported.
NOTE: -1 values mean that the value is not calculated by MSC.
===============================================================================
DN98614198
Issue 1-1 en
Nokia Networks Oy
47 (134)
NSS Network Doctor
Availability for MSC1

from 19980119 to 19980119
Day
Unit
yyyy-mm-dd
---------- ---------VLRU-1-0
1998-01-19
VLRU-1-1
1998-01-19
Discon Discon
Hour
Unit
time
time Admin
Pros Prepros Duplex
hh:mm restrt (sec) duplex restrt restrt restrt restrt
----- ------ ------ ------- ------ ------ ------- ------00:00
5
6
0
0
0
0
0
00:00
2
8
0
0
0
0
0
Figure 11. Report 638: MSC availability

For HLR, a corresponding report HLR availability profiles (641) is
provided.
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
Rej calls
Rej calls %
Queue max lgth
Cust wait trh
Rej. inc low
Rej. inc up
Rej. out up
Process family name

Rejected calls of window access control
Ratio of rejected calls (%)
Maximum length of queue
Nbr of customers whose waiting time is greater than threshold.
Incoming calls rejected due to lower limit in message buffer.
Incoming calls rejected due to upper limit in message buffer.
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_rej
Measurement start: ZTLS:R; (with load observation ZTLS:B;)
===============================================================================
Rejected calls for MSC1
from 19971101 to 19971119
Day
Object
Fmly yyyy-mm-dd
---------- ---- ---------BSU-3
1997-11-19
BSU-5
BSU-6
EXCHG.
48 (134)
Rej. Queue
Hour
Rej. calls max
hh:mm calls
% lgth
----- ------ ------ ----16:26
24
0.0 na
14:26
32
0.0 na
15:26
30
0.0 na
14:26
32
0.0 na
Nokia Networks Oy
Cust
wait
trh
----na
na
na
na
Rej.
inc
low
----na
na
na
na
Rej.
inc
up
----na
na
na
na
Rej.
out
up
----na
na
na
0
DN98614198
Issue 1-1 en
MSC reports
EXCHG.
EXCHG.
15:26
16:26
30
24
0.0 na
0.0 na
na
na
na
na
na
na
0
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 and
Availability... 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).
Note
This report is run through MML based on ZOLU command output
postprocessing, and therefore cannot be run by its ID number or by auto script
generation.
The load is usually checked on the Busy Hour. To find out about earlier Busy
Hour, run the MSC network benchmark (600) report.
DX 200
MSC2
1998-01-19
16:32:34
SIGNALLING LINK UTILIZATION

ACTIVE UNIT
METERS 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.
===============================================================================
LINK
Nbr
====
1
2
3
4
5
6
7
10
11
Traf
RX
(Erl)
====
0.09
0.09
0.09
0.09
0.09
0.09
0.09
0.08
0.08
Traf
TX
(Erl)
====
0.05
0.05
0.05
0.05
0.05
0.05
0.05
0.05
0.05
Figure 13. Report 511: SS7 link load
DN98614198
Issue 1-1 en
Nokia Networks Oy
49 (134)
NSS Network Doctor
6.3.2
X25 load profile (624)

The X25 link load is calculated from OSI4 measurement using the X25 load
profile (624) report.
Note
This report is valid only for X25 channels, but all channels that are defined in the
measurement are shown. The report assumes that the measurement period is 60
minutes.
===============================================================================
=
=
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,60
2) 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
50 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
6.3.3
MAP statistics (514)

This report is MML based, and therefore cannot be run by its ID number or by
auto 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
START TIME
LAST SAMPLE TIME
SOURCE: MSC
1998-01-22 00:00:00
1998-01-22 15:00:00
DESTINATION: HLR
NETWORK ISDN NUMBER

NETWORK IMSI NUMBER
END TIME
9999-12-31 24:00:00
: 86 49
: -
MAP STATISTIC GENERAL DATA

OUTGOING
INCOMING
-------------------------------------------------------------------MISSING DATA
:
0.0 %
0.0 %
SUM OF STARTED OPERATIONS :
519053
1302
SUM OF SUCCEEDED OPERATION :
381294
1302
SUM OF FAILED OPERATIONS
:
137759
0
Figure 15. Report 514: MAP statistics, MML-based
6.3.4
MTP signalling link availability (655)
===============================================================================
=
DN98614198
Issue 1-1 en
Nokia Networks Oy
51 (134)
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
all
link
block
cpu
.
local mng
.
remote mng
.
Signalling link
Duration of signalling
outage
actions
actions
link
link
link
link
unavail.
unavail.
unavail.
unavail.
for
due
due
due
any reason
to link failure
to local blocking
to remote processor
link unavail. due to local management

link unavail. due to remote management
Part 2:
Sign link
local busy
local co
.
remote co
start remote cpu
stop remote cpu
local mng inhib
local mng unhib
Signalling link
Duration of local busy (number of SIBs)
Local manual changeovers and changeovers due to system
recovery actions
Remote initiative changeovers
Start of remote processor outage
Stop of remote processor outage
Local management inhibit
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
52 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
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 1
cong2
level 2
cong3
level 3
Duration
MSU disc
.
MSU loss
30m peak (Erl)
.
5m peak (Erl)
.
Duration of congestion
The number of message signal units (MSU) discarded due to
signalling link congestion
The number of congestion events resulting in loss of MSUs
Peak load in Erlangs measured in 30 min periods during
the reporting period
Peak load in Erlangs measured in 5 min periods during
the reporting period
Part 2:
SIF SIO trans
DN98614198
Issue 1-1 en
The number of SIF and SIO octets transmitted
Nokia Networks Oy
53 (134)
NSS Network Doctor
SIF SIO recv

msg trans
msg recv
retr
bit rate kbit/s
The
The
The
The
The
number of SIF and SIO octets received

number of message signal units transmitted
number of message signal units received
number of octets retransmitted
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
sign
link
----0
Level
******
cong1
cong2
duration
cong3
(hh:mi:ss) MSU disc MSU loss
------ ------------ --------- -------0
0:00:00
0
0
0
0:00:00
0
0
0
0:00:00
0
0
30m peak
(Erl)
********
IN
OUT
-------0.000
0.000
5m peak
(Erl)
********
IN
OUT
-------0.001
0.001
0
0
0
0:00:00
0:00:00
0:00:00
0
0
0
0
0
0
0.000
0.000
0.001
0.001
0
0
0
0:00:00
0:00:00
0:00:00
0
0
0
0
0
0
0.000
0.000
0.001
0.001
0
0
0
0
0.000
0.000
0.001
0.001
3
0
0
0:00:00
0
0:00:00
0:00:00
0
0
31
0
0
0
0:00:00
0:00:00
0:00:00
0
0
0
0
0
0
0.000
0.000
0.000
0.000
40
0
0
0
0:00:00
0:00:00
0:00:00
0
0
0
0
0
0
0.001
0.001
0.002
0.001
109
0
0
0
0:00:00
0:00:00
0:00:00
0
0
0
0
0
0
0.001
0.001
0.002
0.003
110
0
0
0
0:00:00
0:00:00
0:00:00
0
0
0
0
0
0
0.001
0.001
0.002
0.003
144
0
0
0
0:00:00
0:00:00
0:00:00
0
0
0
0
0.001
0.001
0.003
0.002
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
54 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
109
110
144
643458
652451
604431
621217
612054
604001
30045
29989
30234
30212
29806
30005
0
0
0
64
64
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 reasons
abn
abnormal FIBR/BSNR
ack
excessive delay
error rate
excessive error rate
cong
excessive duration
align
Signalling alignment or proving failure
Part 2:
service duration
sign unit
neg ack
auto co
auto cb
link rest
Duration of signaling link in the in-service

The number of signal units received in error
The number of negative acknowledgements received
Automatic changeover
Automatic changeback
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
DN98614198
Issue 1-1 en
Nokia Networks Oy
55 (134)
NSS Network Doctor
144
145
146
158
159
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
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
sign point
duration adjacent
adj inacc
msg
MSU DISC ROUT Tran
.
Rec
MSU STP spc opc stp
UPU MSG Tra Rec
Network
Signalling point
Duration of inaccessibility of adjacent signalling point
Adjacent signalling point inaccessible
The number of transfer controlled messages received
The number of message signal units discarded due to
routing data error (transmitted/received)
Unauthorised STP MSU count for inhibited SPC/OPC/STP
Transmitted/Received UPU (User Part Unavailable) messages
Measurement used: p_msc_mtp_sp_status
56 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
===============================================================================
MTP signalling point status for MSC1
from 20001104 to 20001108
sign
net
point
----- ------NA0
90
MSU
DISC
ROUT
duration adj
Tran
adjacent inac msg
Rec
------------ ---- ---- ---61:30:00
0
0
0
0
MSU
STP
spc
opc
stp
---0
0
0
UPU
MSG
Tra
Rec
---0
0
1024
0:00:00
0
0
0
0
0
0
0
2040
0:00:00
0
0
0
0
0
0
0
16256
0:00:00
0
0
0
0
0
0
0
16257
0:00:00
0
0
0
0
0
0
0
16260
61:30:00
0
0
0
0
0
0
0
16261
0:00:00
0
0
0
0
0
0
0
16262
0:00:00
0
0
0
0
0
0
0
16263
0:00:00
0
0
0
0
0
0
0
16264
0:00:00
0
0
0
0
0
0
0
16266
61:30:00
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
DN98614198
Issue 1-1 en
Nokia Networks Oy
57 (134)
NSS Network Doctor
=
MSC:
all MSCs
=
Period:
from 19990923 to 19990923
=
Time aggregation:
whole period
=
===============================================================================
Report description:
net
sign point
link set unavail duration
link set fail start
link set fail stop
trans block
.
trans allow
.
unavail route
.
unavail set
unavail duration route
.
unavail|duration route set
Network
Signalling point
Duration of unavailability of signalling link set
Start of signalling link set failure
Stop of signalling link set failure
Transmission of transfer prohibited message started
due to signalling link failure
Transmission of transfer allowed message started
due to signalling link failure
Unavailability of signalling route due to transfer
prohibited message received
Unavailability of signalling route set
Duration of the unavailability of signalling route
transfer prohibited message received
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
sign
unavail
net
point
duration
----- ------- -----------NA0
90
24:00:00
58 (134)
link set
unavail
fail trans unavail
duration
******** ***** *******
********
start block
route
route
stop allow
set
route set
-------- ------ ------- -----------0
0
0
0:00:00
0
0
0
24:00:00
1024
0:00:00
0
0
0
0
0
0
0:00:00
0:00:00
16256
0:00:00
0
0
0
0
0
0
0:00:00
0:00:00
16257
0:00:00
0
0
0
0
0
0
0:00:00
0:00:00
16261
0:00:00
0
0
0
0
0
0
0:00:00
0:00:00
16262
0:00:00
0
0
0
0
0
0
0:00:00
0:00:00
16263
0:00:00
0
0
0
0
0
0
0:00:00
0:00:00
16264
0:00:00
0
0
0
0
0
0
0:00:00
0:00:00
16265
0:00:00
0
0
0
0
0
0
0:00:00
0:00:00
16266
24:00:00
0
0
0
0
0
0
0:00:00
24:00:00
16273
0:00:08
5
5
5
5
0
5
0:00:00
0:00:08
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
NA1
16274
0:00:00
0
0
0
0
0
0
0:00:00
0:00:00
16275
0:00:00
0
0
0
0
0
0
0:00:00
0:00:00
16298
24:00:00
0
0
0
0
0
0
0:00:00
24:00:00
1280
0:00:00
0
0
0
0
0
0
0:00:00
0:00:00
Signalling link set and route set availability for MSC1KUTOJA

from 19990923 to 19990923
link set
sign
unavail
net
point
duration
----- ------- -----------NA1
12160
0:00:00
link set
unavail
fail trans unavail
duration
******** ***** *******
********
start block
route
route
stop allow
set
route set
-------- ------ ------- -----------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
SIO
user part
SIF SIO recv
SIF SIO trans
Network
Service information octet
User part
The number of received SIF and SIO octets with a given SIO
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
net
SIO
----- --------NA0
128
129
130
131
133
DN98614198
Issue 1-1 en
SIF
SIF
user
SIO
SIO
part
recv
trans
----- ---------- ---------SNM
112
108
SNT
574320
574320
SNTA
0
0
SCCP
45805659
45353706
ISUP
41078
32471
Nokia Networks Oy
59 (134)
NSS Network Doctor
NA1
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
SNM
SNT
SNTA
SCCP
TUP
ISUP
DUP0
DUP1
IND8
IND9
INDA
INDB
INDC
INDD
INDE
INDF
0
36705
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
36705
0
0
0
0
0
0
0
0
0
0
0
0
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
GT1 fail
GT2 fail
GT3 fail
GT4 fail
GT unkno
GT trans
Network
Routing
Routing
Routing
Routing
Routing
Routing
error
error
error
error
error
error
no
no
no
no
no
no
translation
translation
translation
translation
translation
translation
of
of
of
of
of
of
GT type 1.
GT type 2.
GT type 3.
GT type 4.
unknown GT type.
spesific GT.
Part 2: SCCP signalling point performance. Failures per reason

Net fail
Net overl
Sub overl
Sub Fail
Uneq user
Unkn reas
Syn err
Routing error Routing error Routing error Routing error Routing error Routing error Observed syntax
due to a failure in the network.

due to the network overload.
due to the subsystem overload.
due to a failure in the subsystem.
unequipped user.
unknown reason.
errors.
Part 3: SCCP signalling point performance. Messages

UDT trans
UDT rec
UDTS trans
60 (134)
UDT messages sent.

UDT messages received.
UDTS messages sent.
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
UDTS rec
XUDT trans
XUDT rec
XUDTS trans
XUDTS rec
UDTS messages received.

XUDT messages sent.
XUDT messages received.
XUDTS messages sent.
XUDTS messages received.
Part 4: SCCP signalling point performance. Messages

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

CR messages received fron MTP plus ISDN-UP embedded CRs.
CREF messages sent to MTP.
CREF messages received fron MTP.
RSR messages sent to MTP.
RSR messages received fron MTP.
ERR messages sent to MTP.
ESR messages received fron MTP.
Part 5: SCCP signalling point performance. Failures, timers, resets and releases
Fail Rel Comp cl
Fail Rel Comp cl
Timer (iar) Expi
Timer (iar) Expi
Prov Ini Reset
Prov Ini Rel
2
Failure of release complete supervision for DPC (class 2)
3
Failure of release complete supervision for DPC (class 3)
cl 2 Timer T(iar) expiry for DPC (class 2)
cl 3 Timer T(iar) expiry for DPC (class 3)
Provider initiated reset of a connection to DPC
Provider initiated release of a connection to DPC
Part 6: SCCP signalling point performance. Subsystem messages

SCCP SubSys Cong Received SCCP/Subsystem congested messages
SubSys Prohi Received Subsystem prohibited messages
SubSys 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
DN98614198
Issue 1-1 en
Nokia Networks Oy
61 (134)
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
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
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
from 20001021 to 20001109
Sign
point
-----0
1024
1280
16256
16260
16262
16264
16267
16274
16315
62 (134)
Fail
Fail Timer Timer
Rel
Rel (iar) (iar)
Prov
Prov
Comp
Comp
Expi
Expi
Ini
Ini
cl 2
cl 3
cl 2
cl 3 Reset
Rel
------ ------ ------ ------ ------ -----0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports

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
Sub name
NW
Subsystem
Subsystem name.
Network
To local
To redun
Too large msg
Trans class0/class1
Rec class0/class1
All
All
Too
All
All
messages related to a local subsystem.

messages transmitted to the redundant subsystem.
large messages for segmentation.
transmitted messages in protocols class 0 / class 1.
received messages in protocols class 0 / class 1.

CSM acc loc
.
CSM acc rem
CSM rej loc
CSM rej rem
To local wiout GT
From local wiout GT
To local with GT
From local with GT
Acceptance of a coordinated state modification (CSM)

request by a local subsystem
Acceptance of a CSM request by a remote subsys.
Rejection of a CSM request by a local subsys.
Rejection of a CSM request by a remote subsys.
Msg. to a local subsys. that dont require GT translation.
Msg. from a local subsys. that doesnt require GT transl.
Msg. addressed to a local subsys. that requires GT transl.
Msg. from a local subsys. that requires GT transl.

DT1 rec
DN98614198
Issue 1-1 en
DT1 messages received from MTP per sink SSN.
Nokia Networks Oy
63 (134)
NSS Network Doctor
DT1 trans
DT2 recs
DT2 trans
ED rec
ED trans
DT1
DT2
DT2
ED
ED
messages
messages
messages
messages
messages
sent to MTP per source SSN.

received from MTP per sink SSN.
received from MTP per sink SSN.

Last Prohi Start
Last Prohi Stop
Last start time when of local subsystem becomes prohibited

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
Sub
sys
-----1
Too
Sub
To
To
large
name NW
local
redun
msg
----- ---- ------- ------- ------SCMG NA0
15
0
0
Trans
class0
class1
------148
0
Rec
class0
class1
------15
0
NA1
0
0
0
0
NA0
17105
16930
0
17105
0
NA1
0
0
0
0
NA0
10514
9527
0
7333
3115
NA1
0
0
0
0
12 INAP
NA0
24
0
27
0
24
149 MAPS
NA0
0
0
0
0
192 BSSAS NA0
401
295
0
401
0
254 BSSAP NA0
361158
8097
0
213
0
7 MAPV
8 MAPM
Part 2:SCCP subsystem performance for MSC1

from 20001022 to 20001110
CSM
Sub Sub
acc
sys name NW
loc
------ ----- ---- --1 SCMG NA0
0
NA1
0
7 MAPV NA0
0
64 (134)
CSM
acc
rem
--0
0
0
CSM
rej
loc
--0
0
0
To
From
To
From
CSM
local
local local local
rej
wout
wout
with
with
rem
GT
GT
GT
GT
--- ------- ------- ------ -----0
15
183
0
0
0
0
0
0
0
0
0
0 17105 16930
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
NA1
NA0
NA1
12 INAP NA0
149 MAPS NA0
192 BSSAS NA0
254 BSSAP NA0
0
0
0
0
0
0
0
8 MAPM
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
361158
0
0
0
0
0
291
439185
0
10514
0
24
0
401
0
0
9527
0
27
0
4
0

from 20001022 to 20001110
Sub
sys
-----1
7
8
12
149
192
254
Sub
DT1
DT1
DT2
DT2
ED
ED
name NW
rec
trans
rec
trans
rec
trans
----- ---- ------- ------- ------- ------- ------- ------SCMG NA0
0
0
0
0
0
0
NA1
0
0
0
0
0
0
MAPV NA0
0
0
0
0
0
0
NA1
0
0
0
0
0
0
MAPM NA0
0
0
0
0
0
0
NA1
0
0
0
0
0
0
INAP NA0
0
0
0
0
0
0
MAPS NA0
0
0
0
0
0
0
BSSAS NA0
0
0
0
0
0
0
BSSAP NA0
283976 278907
0
0
0
0
from 20001022 to 20001110
Sub
sys
-----1
7
8
12
149
192
254
Sub
name NW
----- ---SCMG NA0
NA1
MAPV NA0
NA1
MAPM NA0
NA1
INAP NA0
MAPS NA0
BSSAS NA0
BSSAP NA0
Last
Prohi
Start
-----00:00
00:00
00:00
00:00
00:00
00:00
00:00
00:00
00:00
00:00
Last
Prohi
Stop
-----00:00
00:00
00:00
00:00
00:00
00:00
00:00
00:00
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
DN98614198
Issue 1-1 en
To a local subsystem.
Nokia Networks Oy
65 (134)
NSS Network Doctor
From local
STP
SCCP user
SCCP total
From a local subsystem.

STP messages.
User independent.
Total.
Part 2: Messages requiring GT translation

GT
GT
GT
GT
to local
fr local
STP
tot al
To a local subsystem.
From a local subsystem.
STP messages.
Total.
Part 3: Reassembly errors

Timer T(reass) expires
Segment out of sequence
No ReAss space
ReAss failed
Timer T(reass) expires for segmented message

Received XUDT segment out of sequence
Reassembly failures due lack of reassembly resources
Failed reassemblies of segmented messages
Part 4: Segmentation errors and hop counter violations

Segment not supported
Segment failed
Hop counter violation
.
Attempts to send XUDT to denied destination

Amount of failed message segmentations
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
from 20001025 to 20001113
Messages requiring GT translation
GT to
GT fr
GT
GT
local
local
STP
total
--------- --------- --------- --------22432
21158
736
44326
from 20001025 to 20001113
Reassembly errors
Timer
Segment
No
T(reass)
out of
ReAss
ReAss
expires sequence
space
failed
--------- --------- --------- --------0
0
0
0
from 20001025 to 20001113
66 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
Segmentation errors and hop counter violations

Segment
Hop
not
Segment
counter
supported
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
SCCP
SCCP
SCCP
SCCP
SCCP
fail
busy
cong
stop
unava
Network
Start of unavailability of a local SCCP due to failure.
Start of unavail. of a local SCCP due to maintenance busy.
Start of unavailability of a local SCCP due to congestion.
Stop of unavailability of a local SCCP
Duration of the unavailability of a local SCCP.
Measurement used: p_msc_sccp_sub_local_avail

===============================================================================
SCCP local subsystem availability for MSC_1
from 19990930 to 19990930
SCCP
SCCP
SCCP
SCCP
SCCP unava
NW
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
DN98614198
Issue 1-1 en
Nokia Networks Oy
67 (134)
NSS Network Doctor
=
===============================================================================
Part 1 : Protocol errors in transaction portion, abort sent/received
Msg type
Ta incor
Bad frmt
Id unrgn
Resource limit
Unregocnised message type

Incorrect transaction portion
Badly formated transaction portion
Unidentified transaction identifier
Resource limitation
Part 2 : Protocol errors in comp. portion, reject sent/received

Unrgn
Mistypd
Bad strctd
Unrecog
Unrecog lnk id
Unrecog invoke id
Return rsl expctd
Unrecog invk id
Ret err expctd
Unrecognized component
Mistyped component
Badly structured component
Unidentified component
Unidentified linked id
Unidentified invoke id
Return result expected
Unidentified invoke id
Return error expected
Part 3 : TC user generated problems, reject sent/received

Duplic invk id
Unknown opertn
Mistypd param
Resourc limit
Initng release
Linked resp unexpd
Linked oper unexpd
Duplicate invoke id
Unknown operation
Mistyped parameter
Resource limit
Initiating release
Linked response unexpected
Linked operation unexpected
Part 4 : TC user generated problems (continues)

Unrecog error
Unexpd error
Mistpd prmRR
Mistpd prmRE
Unrecognized error
Unexpected error
Mistyped parameter RR
Mistyped parameter RE
Part 5 : Utilization meters, messages sent/received

UNIDIRE
BEGIN
CONTINU
END
ABORT
TC msg
TC tot
UNIDIRECTIONAL messages
BEGIN messages
CONTINU messages
END messages
ABORT messages
Total number of TC messages
Total number of TC components
Part 6 : Miscellaneous cancellations, rejects, aborts, errors

User cancel class1
Msg disc
Prov abort rece
Rece rejec oper
TraAct port err
User cancellations of class 1 operations

Messages discarded by the TC (incorrect/unexpected)
Received TC-P-ABORT -messages
Received operation rejects
Errors detected in transaction portion of the TC
Measurement used: p_msc_tcap_performance

===============================================================================
Part 1: TCAP performance for MSC1
from 20001106 to 20001115
Protocol errors, abort sent/received
Resource
Msg type Ta incor Bad frmt Id unrgn limit
68 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
****
rcvd
trans
-------0
0
****
rcvd
trans
-------0
0
****
rcvd
trans
-------0
0
****
rcvd
trans
-------0
0
****
rcvd
trans
-------0
0
Part 2: TCAP report for MSC1

from 20001106 to 20001115
Protocol errors in comp.portion, reject sent/received
Unrgn
****
rcvd
trans
------0
0
Bad
strctd
****
rcvd
trans
------0
0
Mistypd
****
rcvd
trans
------0
0
Unrecog
lnk id
****
rcvd
trans
------0
0
Unrecog
invk id
****
rcvd
trans
------0
0
Ret rsl
expctd
****
rcvd
trans
------0
0
Unrecog
invk id
****
rcvd
trans
------0
0
Ret err
expctd
****
rcvd
trans
------0
0

from 20001106 to 20001115
TC user generated problem, reject sent/received
Duplic
invk id
****
rcvd
trans
------0
0
Unknown
opertn
****
rcvd
trans
------0
0
Mistypd
param
****
rcvd
trans
------0
0
Resourc
limit
****
rcvd
trans
------0
0
Initng
release
****
rcvd
trans
------0
0
Linked
resp
unexpd
****
rcvd
trans
------0
0
Linked
oper
unexpd
****
rcvd
trans
------0
0

from 20001106 to 20001115
TC user generated problem (continues)
Unrecog
error
****
rcvd
trans
------0
0
Unexp
error
****
rcvd
trans
----0
0
Misty
prmRR
****
rcvd
trans
----0
0
Misty
prmRE
****
rcvd
trans
----0
0
from 20001106 to 20001115
Utilization meters, messages sent/received
UNIDIR
******
rcvd
trans
-----0
0
BEGIN
******
rcvd
trans
------126
242
CONTINU
******
rcvd
trans
------52
55
END
******
rcvd
trans
------226
74
ABORT
*****
rcvd
trans
----1
7
TC msg
******
rcvd
trans
------405
378
TC tot
******
rcvd
trans
------328
366

from 20001106 to 20001115
Miscellaneous cancellations, rejects, aborts, errors
User
cancel
Msg
class1 discard
DN98614198
Issue 1-1 en
Prov
abort
rece
Rece TraAct
rejec portion
oper
err
Nokia Networks Oy
69 (134)
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
Open TraAct
Mean durat
Max open
Number of new transactions

Average number of open transaction IDs
Mean duration of transactions
Average number of maximum open transaction IDs
Measurement used: p_msc_tcap_transaction

===============================================================================
TCAP transactions for MSC1
from 20001111 to 20001120
Sub Sub
New
Open
Mean
Max
NW
sys name
TraAct TraAct
durat
open
---- ------ ----- ------- ------- ------- ------NA0
7 MAPV
0
0
0
0
NA0
8 MAPM
1
1
48
1
NA0
12 INAP
0
0
0
0
NA1
7 MAPV
0
0
0
0
NA1
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
70 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
Type
Ind
limit1 upper/lower
limit2 upper/lower
limit3 upper/lower
limit4 lower
SIG error
Frame align lost
AIS recv
Remote alarm
ET type
ET index
Disturbance counter 1 limit upper/lower
Disturbance counter 4 limit lower
Signal missing counter 1, 2, 3, and 4
Frame alignment lost counter 1, 2, 3, and 4
AIS received counter 1, 2, 3, and 4
Remote end alarm counter 1, 2, 3, and 4
Part 2: frame alignment signal errors

limit1 upper/lower
limit2 upper/lower
limit3 upper/lower
limit4 lower
Frame align lost
Frame
Frame
Frame
Frame
Frame
alignment
alignment
alignment
alignment
alignment
lost
lost
lost
lost
lost
limits:
limits:
limits:
limits:
counter
stat limit 1
stat limit 2
stat limit 3
stat limit 4
1, 2, 3, and
upper/lower
upper/lower
upper/lower
lower
4
Part 3: slips
Negative
Positive
Counter value for negative slips

Counter value for positive slips
Part 4: CRC
local
remote
.
Total time that the CRC statistics has been on

Total time that the CRC statistics has been on at the
remote end
Part 5: Others
deg
err
err
ser
min
sec
free
err
Degraded minutes
Errored seconds
Error free seconds
Seriously errored seconds
Measurement used: p_msc_pcm_stat

===============================================================================
PCM statistics for MSC1KUTOJA
from 19990922 to 19990922
limit1 limit2 limit3 limit4
****** ****** ****** ******
Frame
upper upper upper
SIG align
AIS Remote
Type 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
66
67
DN98614198
Issue 1-1 en
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Nokia Networks Oy
71 (134)
NSS Network Doctor
68
69
70
71
72
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985

from 19990922 to 19990922
****** ****** ****** ******
Frame
upper upper upper
SIG align
AIS Remote
err lost recv
alarm
---- ---- ------ ------ ------ ------ ----- ----- ----- ------20
73
50
1000
0
0
0
0
0
10
200
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
74
75
76
77
78
79
72 (134)
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
80
81
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985

from 19990922 to 19990922
****** ****** ****** ******
Frame
upper upper upper
SIG align
AIS Remote
err lost recv
alarm
---- ---- ------ ------ ------ ------ ----- ----- ----- ------20
82
50
1000
0
0
0
0
0
10
200
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
85
86
88
90
104
105
107
108
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
PCM statistics for
DN98614198
Issue 1-1 en
Nokia Networks Oy
MSC1KUTOJA
73 (134)
NSS Network Doctor
from 19990922 to 19990922

****** ****** ****** ******
Frame
upper upper upper
SIG align
AIS Remote
err lost recv
alarm
---- ---- ------ ------ ------ ------ ----- ----- ----- ------20 109
50
1000
0
0
0
0
0
10
200
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
110
136
137
138
139
142
143
144
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
2
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985

from 19990922 to 19990922
****** ****** ****** ******
Frame
upper upper upper
SIG align
AIS Remote
err lost recv
alarm
---- ---- ------ ------ ------ ------ ----- ----- ----- ------20 145
50
1000
0
0
0
0
0
10
200
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
146
74 (134)
50
1000
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
158
159
10
200
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
9985
50
10
1000
200
0
0
0
2
0
0
2
0
0
2
0
0
0
0
0
0
0
9985

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
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
DN98614198
Issue 1-1 en
Nokia Networks Oy
75 (134)
NSS Network Doctor
88
90
105
107
108
109
110
145
158
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
from 19990922 to 19990922
Part 5: others
avail time
unavail time
**********
************
local
local
Type Ind
remote
remote
---- ---- --------------- --------------20
85
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
local
remote
*****
******
deg min deg min
err sec err sec
err free err free
ser err ser err
-------- -------0
0
0
0
0
0
0
0
86
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0
0
0
0
0
0
0
0
88
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0
0
0
0
0
0
0
0
90
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0
0
0
0
0
0
0
0
105
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0
0
0
0
0
0
0
0
107
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0
0
0
0
0
0
0
0
108
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0
0
0
0
0
0
0
0
109
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0
0
0
0
0
0
0
0
110
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0
0
0
0
0
0
from 19990922 to 19990922
Part 5: others
local
76 (134)
Nokia Networks Oy
remote
DN98614198
Issue 1-1 en
MSC reports
*****
******
avail time
unavail time deg min deg min
**********
************ err sec err sec
local
local err free err free
Type Ind
remote
remote ser err ser err
---- ---- --------------- --------------- -------- -------0
0
20
145
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0
0
0
0
0
0
0
0
158
0:00:00:00
0:00:00:00
0:00:00:00
0:00:00:00
0
0
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
Type
RR F1
DM F1
UA F1
UA F0
DM F0
peer re-est
SABME
DISC
STAT
NR fail
FRMR
Frame
I field
Size
N201 error
D channel
Channel type (pri or sec)
Receipt of unsolicited RR/RNR/REJ, F=1 (cntr A)
Receipt of unsolicited DM, F=1 (cntr B)
Receipt of unsolicited UA, F=1 (cntr C)
Receipt of unsolicited UA, F=0 (cntr D)
Receipt of unsolicited DM, F=0 (cntr E)
Peer initiated re-establishment (cntr F)
Unsuccessful retransmission of SABME (cntr G)
Unsuccessful retransmission of DISC (cntr H)
Unsuccessful retransmission of status inquiry (cntr I)
NR error (cntr J)
Receipt of FRMR response (cntr K)
Receipt of non_implemented frame (cntr L)
Receipt of I field not permitted (cntr M)
Receipt of frame with wrong size (cntr N)
N201 error (cntr O)
Measurement used: p_msc_lapd_error

===============================================================================
LAPD error counters for MSC_1
from 19990929 to 19990929
RR
DM
UA
UA
DN98614198
Issue 1-1 en
F1
F1
F1
F0
SABME
DISC
peer STAT
FRMR
Frame
NR I field
Nokia Networks Oy
N201
77 (134)
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
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
Type
DL DATA Req
DL DATA Ind
DL DATA UNIT Req
DL DATA UNIT Ind
Errors CRC
Errors frame
Deleted DL DATA REQ
Deleted I frames
T200 exp
DMC ovflw
Clck mis
D channel
The number of DL-DATA-REQUESTS
The number of DL-DATA-INDICATIONS
The number of DL-DATA-UNIT-REQUESTS
The number of DL-DATA-UNIT-INDICATIONS
CRC errors
Frame errors
Deleted DL-DATA-REQUESTS
Deleted I frames in the window
T200 expiries
DMC message buffer overflows
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
******* ******* ******
*******
Req
Req
CRC DL DATA REQ
Chn Type
Ind
Ind
frame
I frames
---- ---- ------- ------- ------- ----------80 PRI
89
0
0
0
89
0
0
0
81 PRI
78 (134)
199
Nokia Networks Oy
T200 exp
DNC oflw
Clck mis
-------0
0
0
0
DN98614198
Issue 1-1 en
MSC reports
178
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
Type
I frames trans
I frames received
UI frames trans
UI frames received
I octets trans
I octets received
UI octets trans
UI octets received
Total octets trans
Total octets received
D channel
Transmitted I frames
Received I frames
Transmitted UI frames
Received UI frames
Transmitted I frame octets
Received I frame octets
Transmitted UI frame octets
Received UI frame octets
Transmitted total octet count
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
178
0
0
3544
2842
0
0
38612
37994
Figure 31. Report 671: LAPD traffic
DN98614198
Issue 1-1 en
Nokia Networks Oy
79 (134)
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 MSCs
if there are more than one MSC in the network.
For Clear Code descriptions, see Clear Code List CAG27903, Operating Manual
CC Id
CC Name
Signal
Ring
Speech
Share of all CC
Clear
Clear
Share
Share
Share
Share
code identification number

code name
(%) of particular CC occurred in the signalling phase.
(%) of particular CC occurred in the ringing phase.
(%) of particular CC occurred in the speech phase.
(%) 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
Id
(H)
---0
10
102
12
15
202
203
205
206
208
300
301
304
306
307
30A
30B
30C
312
314
318
405
407
5
6
CC Name
Occurences
------------------------------ ---------NORMAL END OF THE CALL
630399
ABSENT SUBSCRIBER
67817
CALL RECORD REL DURING CA
229
NO PAGING RESPONSE
27831
NORMAL UNSPECIFIED
23
CLEAR REQUEST RECEIVED
3
B CHANNEL UNACCEPTABLE
1
RADIO IF CONGESTION
21447
CALL REJECTED
1715
MS RE-ESTABLISHMENT FAIL
1466
OUTGOING CALLS BARRED
98
OPER RESTR IN OUT DIRECT
36
B-LINE OUT OF SERVICE
5261
B-CALLS RESTRICTED
78
B-NUMBER UNUSED
2829
A ONHOOK DURING SET UP
63725
A ONHOOK DUR_WAIT ANSWER
126215
B ONHOOK TIME OUT
445
TELE SERV NOT PROV
471
UNIDENTIFIED SUBSCRIBER
33
TERMINAL SWITCH OFF
6187
ERR REQUE FROM COPROCESS
41
ERR ANSWER FROM CO-PROC
112
B-SUBSCRIBER BUSY
34682
B ANSWER TIME OUT
10885
80 (134)
Nokia Networks Oy
Share
Signal
Ring Speech of all CC
(%)
(%)
(%)
(%)
------ ------ ------ --------0.0
0.7
99.3
58.2
100.0
0.0
0.0
6.3
0.9
55.0
44.1
0.0
100.0
0.0
0.0
2.6
17.4
78.3
4.3
0.0
0.0
33.3
66.7
0.0
100.0
0.0
0.0
0.0
100.0
0.0
0.0
2.0
7.4
91.8
0.8
0.2
0.7
90.0
9.3
0.1
100.0
0.0
0.0
0.0
100.0
0.0
0.0
0.0
100.0
0.0
0.0
0.5
100.0
0.0
0.0
0.0
100.0
0.0
0.0
0.3
100.0
0.0
0.0
5.9
0.0
99.9
0.0
11.7
0.0
0.2
99.8
0.0
100.0
0.0
0.0
0.0
100.0
0.0
0.0
0.0
9.6
37.2
53.3
0.6
97.6
0.0
2.4
0.0
100.0
0.0
0.0
0.0
73.1
26.9
0.0
3.2
0.0 100.0
0.0
1.0
DN98614198
Issue 1-1 en
MSC reports
603
7
70A
70E
80D
80E
80F
811
812
813
814
815
816
817
NO RESPONSE FROM CO-PROC

CALL WAITING TIME OUT
FORCED CLEAR OF A CALL
CONFIGURATION ERROR
OUT CIRCUIT OUT OF ORDER
IN CIRCUIT OUT OF ORDER
CIRCUIT CONGESTION
NETWORK FAILURE
MAP FAILURE
SWITCHING EQUI CONGESTION
CIRCUIT GROUP CONGESTION
B ACCESS BARRED
CALL UNSUC SEND INFO TONE
N-UNALLOCATED NUMBER
57
1358
20
62
242
532
108
770
571
492
2081
47
115
2545
0.0
0.0
65.0
100.0
100.0
100.0
100.0
100.0
100.0
100.0
94.3
100.0
100.0
100.0
96.5
100.0
5.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
5.7
0.0
0.0
0.0
3.5
0.0
30.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.1
0.0
0.0
0.0
0.0
0.0
0.1
0.1
0.0
0.2
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)
Note
If you have not run this measurement earlier, there is no data on this in the NMS
database, and running this report would cause an error. You must first run the
measurement 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 or
per MSC). The report is arranged by the Avg Share out of all CC.
CC Id
CC Name
Sign
Ring
Spch
Delta
Clear code identification number

Clear code name
Share (%) of CC occurred in the signalling phase. Whole period.
Share (%) of CC occurred in the ringing phase. Whole period.
Share (%) of CC occurred in the speech phase. Whole period.
The difference between first and last day %.

===============================================================================
MSC Clear Code of Calls
between 19981120 and 19981125
all MSCs, all clear codes
DN98614198
Issue 1-1 en
Nokia Networks Oy
81 (134)
NSS Network Doctor
CC
Id
(H)
---0
30B
30A
10
5
Sign Ring Spch

CC Name
(%) (%) (%)
------------------------------ ---- ---- ---NORMAL END OF THE CALL
0
1
99
0 100
0
100
0
0
ABSENT SUBSCRIBER
100
0
0
B-SUBSCRIBER BUSY
70
30
0
First
Last
Avg
day
day
Share Share Share
out of out of out of
all CC all CC all CC Delta
(%)
(%)
(%)
(%)
------ ------ ------ ----58.0
57.9
58.3
0.3
11.8
11.8
11.8
0.0
6.4
6.5
6.4 -0.1
5.3
5.1
4.9 -0.2
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 calculated
for each MSC over the given time interval.
Nrm End
Rif Fail
Rif Msg
OutC Fail
Rmt Eqp
Net Fail
HO Fail
NoRe HLR
NoRe VLR
BSS Map
No Res
cc000
ccB13
ccB1B
ccA07
ccB16
cc811
ccB14
cc81B
cc81C
ccB1A
cc719
Normally ended calls

Radio if failure
Radio if msg failure
Call failure from outgoing circuit
Remote equipment failure
Network failure
HO failure
No response from HLR
No response from VLR
BSS MAP protocol error
No resource for call
The percentage share of some congestion related clear codes is calculated

for each MSC over the given time interval.
Rif Cong
Crct Cong
OutC Cong
Ovld Cong
CM Cong
MAP Cong
cc205
cc80F
cc804
cc60B
cc718
cc040
Radio if congestion
Circuit congestion
Outgoing circuit congestion
Overload congestion
CM analysis congestion
MAP congestion

===============================================================================
MSC call clear codes per MSC
from 19980901 to 19981108
Nrm
End
000
MSC Name
(%)
--------------- ----
82 (134)
Rif
Fail
B13
(%)
----
Rif
Msg
B1B
(%)
----
OutC
Fail
A07
(%)
----
Rmt
Eqp
B16
(%)
----
Net
Fail
811
(%)
----
Nokia Networks Oy
HO
Fail
B14
(%)
----
NoRe
HLR
81B
(%)
----
NoRe
VLR
81C
(%)
----
BSS
Map
B1A
(%)
----
No
Res
719
(%)
----
DN98614198
Issue 1-1 en
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 040
MSC 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
Calls
.
Calls
Calls
Calls
Code Id
in Sign
in Ring
in Spch
Total
The clear code

The % of calls
phase.
The % of calls
The % of calls
The % of calls
idenfication
ending with a clear code in the signalling
ending with a clear code in the ring phase.
ending with a clear code in the speech phase.
ending with a clear code.
Measurement used: p_msc_cc_dest

===============================================================================
Clear Codes of Destinations for MSC4

from 19971119 to 19971119
Clear
Dest
Code
Number
Id
-------- ----358
0
5
6
517
520
778
779
792
1539
2052
2068
2071
2565
2567
DN98614198
Issue 1-1 en
Call Call Call

Clear
in
in
in
Call
Code
Sign Ring Spch Total
Call
Name
(%)
(%)
(%)
(%)
Total
-------------------------- ----- ----- ----- ------ ----------NORMAL END OF THE CALL
0.0
0.7 73.7
26.1
161
B-SUBSCRIBER BUSY
12.3
0.0
0.0
5.2
32
B ANSWER TIME OUT
0.0
0.7
0.0
0.2
1
RADIO IF CONGESTION
36.8
0.0
0.0
15.6
96
MS RE-ESTABLISHMENT FAIL
0.0
0.0
1.4
0.5
3
5.7
0.0
0.0
2.4
15
0.0 83.3
0.0
18.7
115
TERMINAL SWITCH OFF
0.4
0.0
0.9
0.5
3
NO RESPONSE FROM CO-PROC
0.0
0.7
0.0
0.2
1
OUTGOING CIRCUIT CONGEST
7.7
0.0
0.0
3.2
20
9.6
0.0
0.0
4.1
25
N-UNALLOCATED NUMBER
0.4
0.0
0.0
0.2
1
CRCT RELEASED BY CO-EXCHA
0.0
0.0
0.5
0.2
1
CALL FAIL FROM OUT CRCT
14.9
7.2
0.0
8.0
49
Nokia Networks Oy
83 (134)
NSS Network Doctor
2833
2835
2836
2842
2843
2844
3073
MODEM COMMUNICATION ERROR

RADIO IF FAILURE
HANDOVER FAILURE
BSSMAP PROTOCOL ERROR
RADIO IF MSG FAILURE
RADIO IF FAIL REV TO OLD
UNKNOWN DIALLING
0.0
0.0
0.0
0.0
5.7
5.7
0.8
0.0
3.6
0.7
0.7
2.2
0.0
0.0
20.3
2.3
0.9
0.0
0.0
0.0
0.0
7.1
1.6
0.5
0.2
2.9
2.4
0.3
44
10
3
1
18
15
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
Calls
.
Calls
.
Calls
.
Calls
Code Id
in Signal
in Ring
in Speech
Total
The clear code idenfication

The number of calls ending with a clear code in the
signalling phase.
The number of calls ending with a clear code in the ring
phase.
The number of calls ending with a clear code in the speech
phase.
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
Call
Signalling Code
Sign Ring Spch Total
Protocol
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
84 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
051H
055H
057H
062H
063H
069H
075H
077H
083H
084H
085H
087H
6799
1
5069
6
1
841
3021
103485
236
4
44444
18752
1.2
0.0
0.9
0.0
0.0
0.0
0.5
17.8
0.0
0.0
7.6
3.2
0.0
0.0
0.0
0.0
0.0
0.1
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.2
0.0
0.0
0.0
0.0
0.0
0.0
0.6
0.0
0.5
0.0
0.0
0.1
0.3
9.4
0.0
0.0
4.1
1.7
MS CC
000H
016H
017H
018H
021H
024H
041H
081H
100H
101H
102H
6
847346
5755
20
1089
1
1
614
245
423
572
0.0
98.6
0.0
0.0
0.0
0.0
0.0
0.1
0.3
0.0
0.9
0.0
94.2
4.6
0.0
0.9
0.0
0.0
0.2
0.0
0.2
0.0
0.0
99.9
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
99.0
0.7
0.0
0.1
0.0
0.0
0.1
0.0
0.0
0.1
R2
007H
030H
033H
034H
035H
14
2835
67
64
15
17.3
0.0
0.0
0.0
82.7
0.0
0.0 100.0
0.0
0.0
0.0
99.5
0.0
0.0
0.5
0.5
94.7
2.2
2.1
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
Calls CCGR
Answ
Not a
.
.
CCCR1..8
Number of call attempts

Number of calls counted from clear code groups
Ratio of answered calls to all calls
Ratio of unanswered calls to all calls
A subscriber cleared call in ring phase or waiting
time expired.
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 defined
in a practical way (command ZTUM:RGC:RGC1= ,...,RGC8= ;)
Groups could be set e.g. in the following manner:
DN98614198
Issue 1-1 en
Nokia Networks Oy
85 (134)
NSS Network Doctor
RGC1..
RGC2..
RGC3..
RGC4..
RGC5..
RGC6..
RGC7..
RGC8..
normal end (clear code 0)

BSS related problems
NSS related problems
Miscellaneous problems
PNET related problems
MS related problems
Radio interface related problems
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 CCGR8
YYYYMMDD 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
1007012
59.0
12.6
92.9
0.0
4.9
2.2
0.0
0.0
0.0
0.0
19981122 00:00
929500
930526
58.0
12.6
92.7
0.0
5.2
2.2
0.0
0.0
0.0
0.0
19981123 00:00
1049906
1051252
58.7
12.3
92.6
0.0
5.4
2.2
0.0
0.0
0.0
0.0
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 the
report. 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
===============================================================================
86 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
Dx CC
CC
A 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

The report shows all occurrences of the internal data call clear codes used. Clear
code distribution is presented according to the call phase. The report includes the
number and plain text name of individual clear codes. The clear codes are updated
on the basis of the clear code number. This measurement is similar to the clear
code measurement.
It is included in Total trafficability performance of exchange reporting Controlled
by 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
CC Name
Signal
Ring
Speech
Share of all CC
Clear
Clear
Share
Share
Share
Share
code identification number

code name
(%) of particular CC occurred in the signalling phase.
(%) of particular CC occurred in the ringing phase.
(%) of particular CC occurred in the speech phase.
(%) of all calculated clear codes
Measurement used: p_msc_data_cc

===============================================================================
MSC Clear Code of Data Calls
between 20010213 and 20010213
MSC1
CC
Share
Id
Signal
(H) CC Name
Occurences
(%)
(%)
(%)
(%)
---- ------------------------------ ---------- ------ ------ ------ --------0
NORMAL END OF THE CALL
234
0.0
0.0 100.0
63.4
DN98614198
Issue 1-1 en
Nokia Networks Oy
87 (134)
NSS Network Doctor
B17
B13
A04
300
206
70B
30A
30B
15
D03
B16
B12
22
311
12
814
318
C09
102
ADDRESS INCOMPLETE
RADIO IF FAILURE
TRUNK CRCT PROTOCOL ERROR
CALL REJECTED
MODEM ERROR
NORMAL UNSPECIFIED
SERV OR FUNC NOT IMPLEM
REMOTE EQUIPMENT FAILURE
RPL OR MS FRAME SYN ERROR
B BUSY CCBS NOT POSSIBLE
BEARER SERV NOT PROV
NO PAGING RESPONSE
TERMINAL SWITCH OFF
SERV/FACIL ACTIVA RESTR
61
24
10
6
5
5
4
3
2
2
2
2
2
2
1
1
1
1
1
100.0
0.0
100.0
100.0
100.0
0.0
100.0
0.0
0.0
100.0
50.0
0.0
100.0
100.0
100.0
100.0
0.0
100.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
100.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
100.0
0.0
100.0
0.0
100.0
0.0
0.0
0.0
100.0
0.0
0.0
100.0
0.0
50.0
100.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
16.5
6.5
2.7
1.6
1.4
1.4
1.1
0.8
0.5
0.5
0.5
0.5
0.5
0.5
0.3
0.3
0.3
0.3
0.3
Clear Codes of Data Calls, all MSCs

between 20010213 and 20010213
CC
Id
(H)
---0
B17
B13
A04
300
206
70B
30A
30B
15
D03
B16
B12
22
311
12
814
318
C09
102
CC Name
Occurences
------------------------------ ---------NORMAL END OF THE CALL
234
ADDRESS INCOMPLETE
61
RADIO IF FAILURE
24
TRUNK CRCT PROTOCOL ERROR
10
6
CALL REJECTED
5
MODEM ERROR
5
4
3
NORMAL UNSPECIFIED
2
SERV OR FUNC NOT IMPLEM
2
REMOTE EQUIPMENT FAILURE
2
RPL OR MS FRAME SYN ERROR
2
B BUSY CCBS NOT POSSIBLE
2
BEARER SERV NOT PROV
2
NO PAGING RESPONSE
1
1
TERMINAL SWITCH OFF
1
SERV/FACIL ACTIVA RESTR
1
1
Share
Signal
(%)
(%)
(%)
(%)
------ ------ ------ --------0.0
0.0 100.0
63.4
100.0
0.0
0.0
16.5
0.0
0.0 100.0
6.5
100.0
0.0
0.0
2.7
100.0
0.0
0.0
1.6
100.0
0.0
0.0
1.4
0.0
0.0 100.0
1.4
100.0
0.0
0.0
1.1
0.0 100.0
0.0
0.8
0.0
0.0 100.0
0.5
100.0
0.0
0.0
0.5
50.0
0.0
50.0
0.5
0.0
0.0 100.0
0.5
100.0
0.0
0.0
0.5
100.0
0.0
0.0
0.5
100.0
0.0
0.0
0.3
100.0
0.0
0.0
0.3
0.0 100.0
0.0
0.3
100.0
0.0
0.0
0.3
0.0 100.0
0.0
0.3
Figure 39. Report 527: Data call clear codes
6.5.2

The report shows how the data call clear codes of a given number destination are
divided into clear code groups. If a number matches more than one number
destination, it is updated in each of the matching number destinations. The clear
codes are divided into eight clear code groups. Each clear code belongs to one
clear code group only.
88 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
This measurement is similar to the clear code by number destination

measurement. It is included in Total trafficability performance of exchange
reporting Controlled by MML command in the command group of TU (Field
Reporting). Destinations are defined by MML TD command group (Destination
Object Lists).
===============================================================================
=
=
DATA CALL CLEAR CODE GROUPS BY NUMBER DESTINATION
=
=
Network:
PLMN
=
MSC:
All MSCs
=
Period:
from 20010212 to 20010221
=
===============================================================================
Destination
CC grpN
.
MSISDN number of called destination

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
from 20010212 to 20010221
MSC1
CC
CC
CC
CC
CC
CC
CC
CC
Destination
grp1
grp2
grp3
grp4
grp5
grp6
grp7
grp8
----------------- ------ ------ ------ ------ ------ ------ ------ -----101
0
0
0
0
0
0
0
0
209
0
0
0
0
0
0
0
0
358
0
0
0
0
0
0
0
0
454
0
0
0
0
0
0
0
0
968
0
0
0
0
0
0
0
0
Figure 40. Report 528: Data call clear codes by destination
6.5.3

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 per
data call type either as averaged or for the busy hour.
Call type
Calls
DN98614198
Issue 1-1 en
Type of the data call

Number of calls, number of answered calls and
Nokia Networks Oy
89 (134)
NSS Network Doctor
.
Calls%
.
Success
.
Success%
.
Traf
release)
calls that have met online state

Number of calls, number of answered calls and
calls that have met online state as a percentage
Number of accepted, number of SFAILs, number of IFAILs
and number of EFAILs of the calls
Number of accepted, number of SFAILs, number of IFAILs
and number of EFAILs of the calls as a percentage
Average traffic in erlang (from circuit reservation to
Measurement used: p_msc_data_service

===============================================================================
Data service unit usage in MSC1
from 20010216 to 20010220
Calls
*******
Number
Answ
Call type
On-line
-------------------- -------3.1 KHZ, 1 TCH CDSU
66
52
49
Calls%
*******
Number
Answ
On-line
-------100.0
78.8
74.2
Success
*******
Accep
Sfail
Ifail
Efail
-------55
0
1
10
Success%
*******
Accep
Sfail
Ifail
Traf
Efail
(Erl)
-------- --------83.3
0.3
0.0
1.5
15.2
3.1 KHZ, 2 TCH CDSU
33
30
28
100.0
90.9
84.8
30
0
0
3
90.9
0.0
0.0
9.1
0.4
3.1 KHZ, 3 TCH CDSU
16
14
13
100.0
87.5
81.3
14
0
0
2
87.5
0.0
0.0
12.5
0.2
145
140
117
100.0
96.6
80.7
131
2
2
10
90.3
1.4
1.4
6.9
0.7
7
7
7
100.0
100.0
100.0
7
0
0
0
100.0
0.0
0.0
0.0
0.0
GBS UDI, 1 TCH CDSU
63
55
55
100.0
87.3
87.3
38
1
0
17
60.3
1.6
0.0
27.0
0.3
GBS UDI, 2 TCH CDSU
16
11
11
100.0
68.8
68.8
9
2
0
5
56.3
12.5
0.0
31.3
0.3
GBS UDI, 3 TCH CDSU
50
46
46
100.0
92.0
92.0
32
0
0
12
64.0
0.0
0.0
24.0
0.7
UDI CDSU
69
63
100.0
91.3
60
0
87.0
0.0
0.3
3.1 KHZ, NO GBS CDSU
FAX CDSU
90 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
63
91.3
0
9
0.0
13.0
Figure 41. Report 529: Data service unit statistics
6.5.4

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 connections
FNUR kbit/s
Fixed Network User Rate
SETUP
Setup attempts for 9.6, 14.4 and EDGE channel codings
USAGE
Successful setup attempts of 9.6, 14.4 and EDGE channel codings
HO USE
Result of channel configuration changes in handovers
Part 2: Maximum number of requested traffic channels (from MS to network)
FNUR
Fixed Network User Rate
TCH1...TCH8
Number of traffic channels from 1 to 8
Part 3: Attempts and usage of Air Interface User Rate in Non-Transparent
connections
AIUR kbit/s
Air Interface User Rate
SETUP
Setup attempts for 9.6, 14.4 and EDGE channel codings
USAGE REQ
Successful setup attempts with requested channel coding
.
of 9.6, 14.4 and EDGE
USAGE DOWNG
Setup attempts with requested channel configuration not
enabled,
.
leading to downgraded channel coding of 9.6, 14.4 and EDGE
MODIFY
Number of user initiated level-up and downgrade attempts
HO USE REQ
Result of channel configuration changes in handovers in which
.
requested channel configuration is enabled
HO 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 Rate
TCH1...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
-----9.6CH
14.4CH
FNUR kbit/s EDGE
------------ -----9.6
8
DN98614198
Issue 1-1 en
USAGE
-----9.6CH
14.4CH
EDGE
-----8
HO USE
-----9.6CH
14.4CH
EDGE
-----0
Nokia Networks Oy
91 (134)
NSS Network Doctor
0
0
0
0
0
0
14.4
0
3
0
0
3
0
0
1
0
19.2
0
0
0
0
0
0
0
0
0
28.8
0
11
0
0
11
0
0
3
0
38.4
0
3
0
0
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
SETUP
-----9.6CH
14.4CH
AIUR kbit/s EDGE
------------ -----9.6
0
16
0
USAGE
REQ
-----9.6CH
14.4CH
EDGE
-----16
0
0
USAGE
DOWNG
-----9.6CH
14.4CH
EDGE
-----1
0
0
MODIFY
-----9.6CH
14.4CH
EDGE
-----0
0
0
HO USE
REQ
-----9.6CH
14.4CH
EDGE
-----0
0
0
HO USE
DOWNG
-----9.6CH
14.4CH
EDGE
-----0
0
0
14.4
0
51
0
0
51
0
0
0
0
0
21
0
0
0
0
0
0
0
19.2
21
0
0
20
0
0
0
0
0
0
0
0
0
0
0
0
0
0
92 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
28.8
5
21
0
5
21
0
0
1
0
0
15
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
45
0
0
44
0
0
0
0
0
44
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 %
-------- -------- -------- -------- -------- --------
DN98614198
Issue 1-1 en
Nokia Networks Oy
93 (134)
NSS Network Doctor
102760
4578
20200
2.3
545
5.1
1003
3.5
398
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 the
number 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
******
BTS NAME
BCF NAME
BSC NAME (BTS)
-----------------Sector1
Site aa
BSC4 (127)
MSC1
Sector2
Site bb
BSC6 (25)
MSC1
HO=>
****
HO=>
Fail
****
%
Att
---- ------100
86
100
306
<=HO
Target
****
<=HO ******
Fail
**** LAC
%
Att CI
---- ------- -----0
0 4220
1112
0 4220
2505
Target
******
BTS NAME
BCF NAME
BSC NAME (BTS)
-----------------Sector2
Site aa
BSC4 (127)
MSC1
Sector3
Site bb
BSC6 (25)
MSC1
Figure 44. Report 636: Handover failure ratio for adjacencies
94 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
6.6.3
Handover observation statistics (619)
Note
If you have not run this measurement earlier, there is no data on this in the NMS
database, and running this report would cause an error. You must first run the
measurement 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 HO
Observation table (p_msc_ho_obs).
Note: The observation is activated via MML command ZTPO:STA:LAC=xxx,CI=yyy
===============================================================================
Target
BSC name
BTS name
(CI,LAC)
------------BSC1
KKALLIO16
KILO009
(1,10016)
Handover
Type
---------intra-BSC
Handover
Reason
-------------------------Uplink quality
:
Uplink strength
:
Downlink quality
:
Downlink strength :
Distance
:
OM intervention
:
Response to MSC
:
Call control
:
Better cell
: 3
Directed retry
:
Switch circuit pool:
Handover
Result
----------------------------Rif Msg failure
:
Rif failure
:
Call control
:
Rif fail ret to old
:
Handover successful
: 3
Equipment failure
:
No radio resource
:
Terr resource notavail :
CCCH overload
:
Processor overload
:
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
DN98614198
Issue 1-1 en
Nokia Networks Oy
95 (134)
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
Home Inter LU Fail
Roam Intra LU Fail
percentage
Roam Inter LU Fail
percentage
Per. LU Fail %
Arr. Fail %
Dep. Fail %
VLRU Answ Rate %
TMSI Fail
IMSI Att.
A-if Page
SGSN Page
MS Search
%
Fail
Fail
Fail
Fail
%
%
%
%
% Intra VLR, home subscriber location update failure percentage

% Inter VLR, home subscriber location update failure percentage
% Intra VLR, roaming subscriber location update failure
% Inter VLR, roaming subscriber location update failure
Periodic location update failure percentage
Arriving visitors location update failure percentage
Departing visitors location update failure percentage
Rate of answered VLRUs in measurement data inquiry operation
TMSI failure percentage
IMSI attach failure percentage
Failure percentage for pagings via A-interface
Failure percentage for pagings via SGSN
MS Search failure percentage
Measurement used: p_msc_vlr

===============================================================================
VLR failure profiles of LUs for MSC1
from 20001107 to 20001107
Day
yyyy-mm-dd
---------2000-11-07
Hour
hh:mm
----00:00
01:00
02:00
03:00
05:00
06:00
07:00
08:00
Home
Intra
LU
Fail
%
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
Home
Inter
LU
Fail
%
----0.0
0.0
0.0
0.0
0.0
0.0
50.0
30.0
Roam
Intra
LU
Fail
%
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
Roam
Inter
LU
Fail
%
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
Per.
LU
Fail
%
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
Arr.
LU
Fail
%
----100.0
100.0
100.0
100.0
100.0
100.0
99.6
98.5
Dep.
LU
Fail
%
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
VLRU
Answ
Rate
%
----100.0
100.0
100.0
100.0
100.0
100.0
100.0
100.0
Figure 46. Report 632: VLR failure profiles
6.7.2
VLR subscriber profiles per LA (635)
===============================================================================
=
96 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
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 network
performance. 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 Area
Day yyyy-mm-ddMeasurement period day
Hour hh:mmMeasurement period time
Subscribers (avg)Average amount of subscribers in LA
Avg counting statusStatus for collecting subscriber data from VLRUs
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
=
=
Network:
PLMN
=
MSC:
All MSCs
=
Period:
from 20010213 to 20010213
=
===============================================================================
Authentic succ
Authentic fail
Triplets req
Triplets reused
Triplets trans
Successful authentications.
Failed authentications.
Authentication triplet requests.
Reused triplets.
Transferred authentication triplets.
DN98614198
Issue 1-1 en
Nokia Networks Oy
97 (134)
NSS Network Doctor
Answers succ
Answers unansw
.
Unknown subs
VLRUs nbr
VLRUs sent
Data missing
Successful answers received in response to the VLR.

Unanswered authentication triplet requests with an
unknown subscriber in the VLR.
Subscribers whose data cannot be found in the AUC of the HLR.
Number of VLRUs in the MSC.
Number of VLRUs in the MSC that have sent data.
Data missing in triplet transfer counters.
Measurement used: p_msc_ac_vlr

===============================================================================
Authentication Profile for MSC1
Authentic
*********
Day
Hour succ
yyyy-mm-dd hh:mm fail
---------- ----- --------2001-02-13 00:00
0
0
Triplets
********
req
reused
trans
--------0
0
0
Answers
VLRUs
********
*****
succ
Unknown nbr
unansw
subs sent
--------- ------- ----0
0
1
0
1
Data
missing
-------NO
01:00
0
0
0
0
0
0
0
1 NO
1
02:00
0
0
0
0
0
0
0
1 NO
1
03:00
0
0
0
0
0
0
0
1 NO
1
04:00
0
0
0
0
0
0
0
1 NO
1
05:00
0
0
0
0
0
0
1 NO
1
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
98 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
Unknown
Succ
HLR 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
Number of Calls
/M074
Lost Calls
/M075
Total Listen Time
/M076
Average Listen Time /M076/M074
PCM circuit of the announcement channel

The number of announcement attempts
Lost calls ratio
Total listening time in seconds
Average listening time in seconds
Measurement used: p_msc_ann

===============================================================================
MSC Announcement Channel Statistics for MSC1
from 19971119 to 19971119
Ann
Channel
PCM-TSL
------87-01
87-02
87-03
87-04
87-05
87-06
87-07
87-08
87-09
87-10
87-11
87-12
Number
of
Calls
---------68609
136641
1284
91
0
2869
3299
8536
46
4995
31
397
Lost
Calls
(%)
------0.0
0.0
0.0
0.0
0.0
0.0
0.2
0.0
0.0
0.0
0.0
0.0
Total
listen
Time(s)
---------480337
688430
9481
781
0
18456
32258
64032
2715
50797
172
7109
Average
listen
Time(s)
---------7
5
7
9
0
6
10
8
59
10
6
18
Figure 50. Report 621: Announcement channel statistics
DN98614198
Issue 1-1 en
Nokia Networks Oy
99 (134)
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
Number of Lost Calls
Total Listen Time
Avg Listen Time
The
The
The
The
number of call attempts

number of lost calls
total listening time
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
Device
Index
------200
201
202
207
208
209
211
212
400
404
Number
Number
of
Total
Avg
of
Lost
Listen
Listen
Calls
Calls
Time(s)
Time(s)
--------- --------- --------- --------69597
0
458903
6.6
142826
0
682174
4.8
4718
0
36232
7.7
7804
0
63644
8.2
112
0
6710
59.9
12028
0
130302
10.8
737
0
6295
8.5
592
0
10386
17.5
417
0
4073
9.8
36
0
315
8.8
Figure 51. Report 628: Integrated announcement device statistics
6.9
Traffic and success
6.9.1
===============================================================================
=
=
TRAFFIC CATEGORY STATISTICS
=
=
Network:
PLMN
=
MSC:
All MSCs
=
Period:
from 20010213 to 20010213
=
===============================================================================
100 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
Calls
Anwsd
CC grp n
.
Ave Erl
Call and HO attempts

Answered call
Clear code group. Defined by MML what clear codes belong to
each group
Average traffic in Erlang
Categories:
intern
trans
origO
termI
orig
incom
term
outgo
pbxO
pbxT
vmsO
vmsT
iMSChI
iMSChO
scpO
devO
data
<number>
Internal
Transit
Originating outgoing
Terminating incoming
Originating
Incoming
Terminating
Outgoing
PBX originating
PBX terminating
VMS originating
VMS terminating
Inter MSC handovers, incoming
Inter MSC handovers, outgoing
SCP originating
Device originating
Data calls
Spare for future usage
Measurement used:
p_msc_tc
===============================================================================
Traffic Category Statistics for MSC1
from 20010213 to 20010213
Answd
Catego
Calls (%)
------ -------- ----intern
187 79.1
trans
7 28.6
origO
517 74.7
termI
195 66.7
orig
1129 47.5
incom
294 44.9
term
382 72.8
outgo
524 74.0
pbxO
3 100.0
pbxT
31 90.3
vmsO
0
0.0
vmsT
0
0.0
iMSChI
0
0.0
iMSChO
0
0.0
scpO
0
0.0
devO
0
0.0
data
327 81.0
18
0
0.0
19
0
0.0
20
0
0.0
21
0
0.0
22
0
0.0
CC
grp
1
(%)
----69.0
28.6
69.8
63.1
74.0
45.2
62.3
69.3
100.0
90.3
0.0
0.0
0.0
0.0
0.0
0.0
69.1
0.0
0.0
0.0
0.0
0.0
CC
grp
2
(%)
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
CC
grp
3
(%)
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
CC
grp
4
(%)
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
CC
grp
5
(%)
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
CC
grp
6
(%)
----19.3
57.1
26.5
24.1
23.6
19.7
25.7
26.9
0.0
9.7
0.0
0.0
0.0
0.0
0.0
0.0
28.4
0.0
0.0
0.0
0.0
0.0
CC
grp
7
(%)
----0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
CC
grp
8
Ave
(%)
Erl
----- -------11.8
0.39
14.3
0.00
3.7
1.19
12.8
0.08
2.5
2.00
35.0
0.21
12.0
0.47
3.8
1.19
0.0
0.00
0.0
0.14
0.0
0.00
0.0
0.00
0.0
0.00
0.0
0.00
0.0
0.00
0.0
0.00
2.4
0.99
0.0
0.00
0.0
0.00
0.0
0.00
0.0
0.00
0.0
0.00
Figure 52. Report 620: Traffic category statistics
DN98614198
Issue 1-1 en
Nokia Networks Oy
101 (134)
NSS Network Doctor
6.9.2
Cell measurement statistics (627)
===============================================================================
=
=
CELL MEASUREMENT STATISTICS
=
=
Network:
PLMN
=
Period:
from 19981019 to 19981019
=
===============================================================================
Bids
*********
All
MOC
MTC
The total number of call bids.

The total number of mobile originating call bids.
The total number of mobile terminating call bids.
Succ Ratio
*********
All
MOC
MTC
The ratio of radio channel has been successfully reserved.

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

Ratio for mobile originating calls.
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
Bids
*****
Cell name
All
LAC
MOC
CI
MTC
----------- -------HER3CG3007
8
3
8
30007
0
Succ
Ratio
(%)
*****
All
MOC
MTC
-----100.0
100.0
---.-
Answ
Ratio
(%)
*****
All
MOC
MTC
-----62.5
62.5
---.-
Figure 53. Report 627: Cell measurement statistics
6.9.3
Control unit statistics (616)
===============================================================================
=
=
CONTROL UNIT STATISTICS
102 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
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 per
control unit either averaged or for busy hour.
Calls
Succ
Answ (%)
Sub Error (%)
Int Error (%)
Ext Error (%)
Traf
Number of Calls
Call success ratio
Ratio of answered call attempts to all calls
Calls ended due to subscriber errors
Calls ended due to an internal error condition
Calls ended due to an external error condition
Average traffic in erlang
Measurement used: p_msc_ce

===============================================================================
Control Unit Call Success % for MSC1KUTOJA
from 19981012 to 19981014
Busy Period
yyyy-mm-dd hh:mm
---------------1998-10-14 12:45
1998-10-14 16:45
1998-10-14 12:45
1998-10-14 16:45
1998-10-14 16:45
Sub
Object
Answ
Succ Error
name
Calls
(%)
(%) (%)
------- -------- ------ ------ -----BSU-1
45
53.3
64.4
0.0
BSU-2
34
58.8
94.1
8.8
CCSU-2
28
67.9
92.9
0.0
IWCU-0
9
66.7 100.0
0.0
PAU-0
9 100.0 100.0
0.0
Int
Error
(%)
-----22.2
0.0
10.7
0.0
0.0
Ext
Error
Traf
(%)
(Erl)
------ --------13.3
0.5
5.9
2.7
0.0
0.3
0.0
0.4
0.0
0.7
Figure 54. Report 616: Control unit statistics
6.10
Destinations
These reports are under the MSC Statistics... Traffic and
Success... 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 %
=
DN98614198
Issue 1-1 en
Nokia Networks Oy
103 (134)
NSS Network Doctor
===============================================================================
The first part:
of the report gives the destinations matching or exceeding one or the
thresholds for internal, external or subscriber errors.
Destination
MSISDN/ISDN destination
Type
sub=subscriber, nat=national, int=international
Dir
out=outgoing, in=incoming
Calls
Nbr of call attempts
Answ (%)
Ratio of answered call attempts to all calls
Accep (%)
Ratio of succ. call attempts(CC 0...3FF) to all calls
.
(=100-Sfail-Ifail-Efail)
Sfail (%)
Ratio of subscriber errors to all calls
Ifail (%)
Ratio of internal errors to all calls
Efail (%)
Ratio of external errors to all calls
Traffic (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 and
equal 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
Destination
----------------358
4544
98
96
93
94
95
Type
---int
nat
nat
nat
nat
nat
nat
Answ Accep Sfail Ifail Efail

Traf
Dir
Calls
(%)
(%)
(%)
(%)
(%)
(Erl)
--- -------- ------ ------ ------ ------ ------ -------out
0
0.0
0.0
0.0
0.0
0.0
0.0
in
0
0.0
0.0
0.0
0.0
0.0
0.0
out
0
0.0
0.0
0.0
0.0
0.0
0.0
out
0
0.0
0.0
0.0
0.0
0.0
0.0
out
0
0.0
0.0
0.0
0.0
0.0
0.0
out
0
0.0
0.0
0.0
0.0
0.0
0.0
in
3
66.7 100.0
0.0
0.0
0.0
0.0
Profiles of destinations
95
dd
-08
08
08
08
08
08
08
08
08
08
08
08
08
Answ Accep Sfail Ifail Efail

Traf
hh
Calls
(%)
(%)
(%)
(%)
(%)
(Erl)
-- -------- ------ ------ ------ ------ ------ -------00
0
0.0
0.0
0.0
0.0
0.0
0.0
01
0
0.0
0.0
0.0
0.0
0.0
0.0
02
0
0.0
0.0
0.0
0.0
0.0
0.0
03
0
0.0
0.0
0.0
0.0
0.0
0.0
04
0
0.0
0.0
0.0
0.0
0.0
0.0
05
0
0.0
0.0
0.0
0.0
0.0
0.0
06
0
0.0
0.0
0.0
0.0
0.0
0.0
07
0
0.0
0.0
0.0
0.0
0.0
0.0
08
0
0.0
0.0
0.0
0.0
0.0
0.0
09
0
0.0
0.0
0.0
0.0
0.0
0.0
10
0
0.0
0.0
0.0
0.0
0.0
0.0
11
0
0.0
0.0
0.0
0.0
0.0
0.0
12
2
50.0 100.0
0.0
0.0
0.0
0.0
104 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
08
08
08
08
08
08
08
08
08
08
08
13
14
15
16
17
18
19
20
21
22
23
0
0
1
0
0
0
0
0
0
0
0
0.0
0.0
100.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
100.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.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 all
destination to destination pairs.
Destination
Type
.
Calls
Traffic (Erl)
.
Answ (%)
Succ (%)
.
Sfail (%)
Ifail (%)
Efail (%)
MSISDN/ISDN destination
nat=national, int=international, sub=subscriber,
nus=not used
Number of call attempts
Traffic. Measuring started at a succ. call attempt when
destination data has been received.
Ratio of answered calls to all call attempts
Ratio of Succ. call attempts (CC 0...3FF) to all calls
The second part of the report gives the profiles for those destination
pairs 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
Destination in
Traf
Answ
Destination out Type
Calls
(Erl)
(%)
---------------- ----- -------- -------- -----39347
sub
120
0.2 100.0
DN98614198
Issue 1-1 en
Nokia Networks Oy
Fails
(%)
*****
Sfail
Succ Ifail
(%) Efail
------ -----80.0 20.0
105 (134)
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
dd
-19
19
19
19
19
19
19
19
19
19
19
19
Traf
Answ
Succ Sfail Ifail Efail
hh
Calls
(Erl)
(%)
(%)
(%)
(%)
(%)
-- -------- -------- ------ ------ ------ ------ -----00
0
0.0
0.0
0.0
0.0
0.0
0.0
01
0
0.0
0.0
0.0
0.0
0.0
0.0
02
0
0.0
0.0
0.0
0.0
0.0
0.0
03
0
0.0
0.0
0.0
0.0
0.0
0.0
04
0
0.0
0.0
0.0
0.0
0.0
0.0
05
0
0.0
0.0
0.0
0.0
0.0
0.0
06
0
0.0
0.0
0.0
0.0
0.0
0.0
07
0
0.0
0.0
0.0
0.0
0.0
0.0
08
0
0.0
0.0
0.0
0.0
0.0
0.0
09
120
0.2 100.0
80.0
20.0
0.0
0.0
10
0
0.0
0.0
0.0
0.0
0.0
0.0
11
0
0.0
0.0
0.0
0.0
0.0
0.0
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
T
Dest Number
BH
Traf
Destination direction
Destination type (n=national, i=international, s=subscriber)
Destination number
Busy hour or busy period
Traffic in Erlang on busy hour/period
Measurement used: p_msc_nd

===============================================================================
T
y
Dir p
--- inc n
fri
Dest
08-May
Number
BH Traf
--------- -------4544
0
0.0
95
0
0.0
out i 358
990
106 (134)
0
0
0.0
0.0
sat
09-May
BH Traf
-------0
0.0
0
0.0
0
0
0.0
0.0
sun
10-May
BH Traf
-------0
0.0
0
0.0
0
0
0.0
0.0
Nokia Networks Oy
mon
11-May
BH Traf
-------0
0.0
0
0.0
0
0
0.0
0.0
tue
12-May
BH Traf
-------0
0.0
0
0.0
0
0
0.0
0.0
wed
13-May
BH Traf
-------0
0.0
0
0.0
0
0
0.0
0.0
thu
14-May
BH Traf
-------0
0.0
14
0.0
0
0
0.0
0.0
DN98614198
Issue 1-1 en
MSC reports
n 90
91
92
93
94
96
97
98
0
0
0
0
11
0
0
0
0.0
0.0
0.0
0.0
0.1
0.0
0.0
0.0
0
0
0
0
0
0
0
0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0
0
0
0
0
0
0
0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0
0
0
0
0
0
0
0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0
0
0
0
0
0
0
0
0.0 0
0.0 0
0.0 0
0.0 0
0.0 21
0.0 0
0.0 0
0.0 0
0.0
0.0
0.0
0.0
0.1
0.0
0.0
0.0
0
0
0
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 and
Success... menu.
6.11.1
===============================================================================
=
=
CIRCUIT GROUP STATISTICS
=
=
Network:
PLMN
=
MSC:
All MSCs
=
Period:
from 20010122 to 20010126
=
===============================================================================
Columns:
Cgr name
Cgr (nbr) dir
Cgts (avg)
Cgts (max)
Cgts (avl)
Cgts (min)
Avg traf (erl) out/in
Max traf (erl) out/in
Avg block (%) out
Max block (%) out
Subs err (%)
Ext err (%)
Int err (%)
Answd call lngt out/in
.
.
Circuit group name

Circuit group identification number and dircetion
Average number of circuits in the circuit group
Maximum number of circuits in the circuit group
Average number of outgoing circuits in WO-EX state
Minimum number of free circuits
Average outgoing/incoming traffic in Erlang
Maximum outgoing/incoming traffic in Erlang
M097a Average outgoing call congestion (blocking)
M097a Maximum outgoing call congestion (blocking)
Ratio of subscriber errors to all calls.
Ratio of external errors to all calls.
Ratio of internal errors to all calls.
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.
DN98614198
Issue 1-1 en
Nokia Networks Oy
107 (134)
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
(331) bi
30
30
30
29
0
0
0
0
0.0
0.0 100.0
100.0
0.0
0.0
0.0
0.0
0.0
0.0
54
36
BSC02144
(323) bi
28
28
28
28
0
0
0
0
0.0
0.0
.0
.0
0.0
0.0
0.0
0.0
0.0
0.0
0
0
BSC03
(330) bi
27
27
27
26
0
0
0
0
0.0
0.0
33.3
25.0
0.0
0.0
0.0
0.0
0.0
0.0
0
36
BSC03144
(332) bi
28
28
28
20
0
0
0
0
0.0
0.0
.0
80.0
0.0
0.0
0.0
55.6
0.0
0.0
0
103
BSC04144
(342) bi
28
28
28
26
0
0
1
0
0.0
0.0 100.0
50.0
0.0
0.0
0.0
50.0
0.0
0.0
324
792
Figure 58. Report 602: Circuit group statistics
6.11.2
===============================================================================
=
=
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
Cgts
Cgts avail
Cgts min free
Traf (erl) out/in
Block (%) out
Subs err (%) out/in
Ext err (%) out/in
Int err (%) out/in
M097a
Start time of the measurement period.

Average number of circuits in the circuit group
Average number of outgoing circuits in WO-EX state
Minimum number of free circuits
Average outgoing/incoming traffic in Erlang
Average outgoing call congestion (blocking)
Ratio of subscriber errors to all calls.
Ratio of external errors to all calls.
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 %
108 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
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
Cgts
Hour
Cgts
min
hh:mi
Cgts avail
free
----- ------ ------ -----08:15
91
91
85
Day
yyyy-mm-dd
---------2001-01-26
Subs
Ext
Int
Traf Block
err
err
err
(erl)
(%)
(%)
(%)
(%)
---------------out
out
out
out
out
in
in
in
in
------- ------ ------ ------ -----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
1.5
0.0
0.0
0.0
2.7
5.3
0.0
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.1
0.0
0.0
0.0
0.0
0.0
0.0
0.0
2001-01-25 18:15
91
91
88
0.3
0.1
0.0
0.0
0.0
5.3
33.3
0.0
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
2.7
0.0
0.0
0.0
14.5
16.1
0.0
4.8
2001-01-25 17:15
91
91
87
0.1
0.3
0.0
0.0
0.0
0.0
42.3
0.0
0.0
2001-01-25 15:15
91
91
83
0.3
1.5
0.0
0.0
0.0
1.2
7.3
0.0
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
Cgr nbr
Destination
Dest type
.
Calls
Traf
DN98614198
Issue 1-1 en
Circuit group name

Circuit group number
MSISDN/ISDN number destination
destination type
int=international, nat= national, sub= subscriber
Nbr of call attempts
Average traffic (Erl).
Nokia Networks Oy
109 (134)
NSS Network Doctor
Answ (%)
Succ (%)
.
Fails (%)
*****
Sfail
Ifail
Efail
Ratio of answered calls to all call attempts

Ratio of succ. calls(CC 0...3FF) to all attempts
Measurement used: p_msc_ctd

===============================================================================
Circuit Group Statistics for MSC1
Cgr
Cgr
name
nbr Destination
----------------- ---- -----------DDA01
186 03
Dest Calls
Answ
Succ
type Traf
(%)
(%)
---- -------- ------ -----nat
0
0.0
0.0
0.0
DDA01
nat
186 09
0
0.0
0.0
Fails
(%)
*****
Sfail
Ifail
Efail
-----0.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 name
Activ
Nbr of activations of the facility
Passiv
Nbr of passivations of the facility
Inquir
Nbr of inquiries of the facility
Usage count
Total amount of usage of the facility by MS user
Ratio to calls (%)
Subscriber facility use count ratio to nbr of all calls.
.
Measurement used: p_msc_subs_fac
110 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
===============================================================================
Subscriber Facility statistics MSC11
Subs
Fac
Code
---5
7
8
10
15
22
32
48
49
50
55
82
87
90
99
134
149
150
214
325
490
Subs Facility Name

Activ Passiv Inquir
------------------------------ ------- ------- ------BARRING OF ALL OUTGOING CALLS
0
0
0
BARRING OF ALL INCOMING CALLS
0
0
0
CALL FORWARDING UNCONDITIONAL
0
0
0
CALL FORWARDING ON BUSY
0
0
0
CALL FORWARDING ON NO REPLY
0
0
0
CALL WAITING
0
0
0
CALL HOLD
0
0
0
CALLING NBR ID PRESENTATION
0
0
0
CALLING NBR ID RESTRICTION
0
0
0
PER CALL BASIS CLIR
0
0
0
UNSTRUCTURED SS DATA
0
0
0
CALL FORWARDING NOT REACHABLE
0
0
0
BARRING OF INTERNATIONAL MOC
0
0
0
CALL RETRIEVAL
0
0
0
OPERATOR DET. BARRING OF MOC
0
0
0
EMERGENCY CALLS
0
0
0
SHORT MESSAGE MT/PP
0
0
0
SHORT MESSAGE MO/PP
0
0
0
AUTOMATIC FACSIMILE GROUP3
0
0
0
DUAL NUMBERING
0
0
0
NONTR DATA C.D.A 9600 B/S
0
0
0
Ratio
Usage to call
count (%)
------- ------10
0.00
90
0.01
3866
0.38
661
0.06
1732
0.17
10625
1.03
6212
0.61
269294
26.23
1838
0.18
14
0.00
1253
0.12
20471
1.99
587
0.06
1546
0.15
41
0.00
3716
0.36
13179
1.28
67262
6.55
14
0.00
544
0.05
45
0.00
Figure 61. Report 603: Subscriber facility usage
6.13
MSC benchmark
The MSC network benchmark (600) report collects some of the most
interesting 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 NMS
network benchmark report offers a compact way to get an overview of the MSC
or all MSCs.
===============================================================================
=
=
MSC NETWORK BENCHMARK
=
=
Network:
PLMN
=
MSC:
All MSCs
=
Period:
from 20010217 to 20010221
=
===============================================================================
This report counts various Performance Indicators from the selected MSC
or all MSCs.
DN98614198
Issue 1-1 en
Nokia Networks Oy
111 (134)
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
. in end of period ......(2001-02-21 15:00)..../M023
-1
-1
Number of subscribers in VLR of the selected MSC(s)

. in beginning of period (2001-02-17 00:00)..../M019
. in end of period ......(2001-02-21 15:00)..../M019
na
-1
CALLS AND HANDOVERS BY TRAFFIC CATEGORIES

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

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

. Originating calls, circuit seized .........../M077
. Terminating incoming calls, circuit seized ../M077
. Originating calls, answered ................./M078
. Terminating incoming calls, answered ......../M078
Time
155
62
212
110
sec
sec
sec
sec
CALLS BY CLEAR CODES

Note that CC measurement runs with min. 24h period.
This is why the results show yesterdays situation
if this report is run for today.
.
Call attempts (+ inter MSC HOs in B-MSC) ......./M043
. Normally ended calls ......................./cc000
. Radio if congestion ......................../cc205
. Circuit congestion ........................./cc80F
. Outgoing circuit congestion ................/cc804
. CM analysis congestion ...................../cc718
. Overload congestion ......................../cc60B
112 (134)
Nokia Networks Oy
Calls
2732
1597
1
2
0
0
0
Share
(
(
(
(
(
(
58.5
0.0
0.1
0.0
0.0
0.0
%)
%)
%)
%)
%)
%)
DN98614198
Issue 1-1 en
MSC reports
.
.
.
.
.
.
.
.
No resources for call ....................../cc719

Call failure from outg.circuit ............./ccA07
Network failure............................./cc811
HO failure ................................./ccB14
No response from HLR ......................./cc81B
No response from VLR ......................./cc81C
BSS MAP protocol error....................../ccB1A
MAP congestion ............................./cc040
0
0
3
0
0
2
0
0
(
(
(
(
(
(
(
(
0.0
0.0
0.1
0.0
0.0
0.1
0.0
0.0
%)
%)
%)
%)
%)
%)
%)
%)
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Dropped calls .............................../M092

Subs. out of coverage, re-est. failed ...../cc208
Call cleared by MML ......................./cc609
Unit restarted ............................/cc60E
Echo canceller failure ..................../cc610
Forced clear of a call ..................../cc70A
Radio interface failure .................../ccB13
Handover failure ........................../ccB14
Remote equipment failure ................../ccB16
Radio interface message failure .........../ccB1B
Radio interface, reversion to old channel ./ccB1C
Subs. signalling message content error ..../ccD00
Subs. signalling message format error ...../ccD01
Service or function not implemented ......./ccD03
Subs. signalling protocold error ........./ccD04
AOCC charging error ......................./ccD06
No resp. to call est. alerting or connect ./ccD07
GSM ERH 4.8 protocol timer expired ......../ccD08
166
0
0
0
0
0
108
0
20
6
8
1
0
0
0
16
0
7
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
6.1
0.0
0.0
0.0
0.0
0.0
4.0
0.0
0.7
0.2
0.3
0.0
0.0
0.0
0.0
0.6
0.0
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
.
Intra-MSC HO (excluding intra BSC) ............/M003A
Inter-MSC HO ................................../M007A
Attempts
12
0
CIRCUIT GROUPS
.
Average Availability .........................../M009
Average usage ................................../M010
A-interface circuit group blocking
. average ..................................../M097a
. during peak traf period (2001-02-19 11:15) /M097a
(Note: based on assumption that circuit group has
.
string BSC in name)
Success
( 83.3 %)
(
na %)
(
(
78.0 %)
0.9 %)
(
(
-2.8 %)
0.0 %)
Hints:
For circuit group statistics run report 602 or 649.
VLR
.
Intra-VLR LU (incl. periodic LU) .............../M013A
Inter-VLR LU .................................../M014A
Arriving visitors ............................../M017A
IMSI attach ..................................../M018A
IMSI detach ...................................../M002
Attempts
0
0
0
0
0
Average number of LU attempts per subsc. ......./M019A
DN98614198
Issue 1-1 en
Nokia Networks Oy
Fail
(
(
(
(
na
na
na
na
%)
%)
%)
%)
113 (134)
NSS Network Doctor
Total DB operations ............................/M020A

Extra load due to periodic LU .................../M016
ALL DATA CALLS

.
Data calls ...................................../M130A
Bids
1355
(
(
na %)
0.0 %)
Answer rate
( 85.3 %)
Data call traffic (average)...................../M132
erl
LOCATION UPDATES
.
. Periodic ..................................../M062
. Home inter VLR ............................../M063
. Home intra ................................../M064
. Roam inter VLR ............................../M065
. Roam intra ................................../M066
Attempts
0
0
0
0
0
Success
(
0.0
(
0.0
(
0.0
(
0.0
(
0.0
%)
%)
%)
%)
%)
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)
.
. Periodic ..................................../M062
. Home inter VLR ............................../M063
. Home intra ................................../M064
. Roam inter VLR ............................../M065
. Roam intra ................................../M066
Attempts
0
0
0
0
0
Success
(
0.0
(
0.0
(
0.0
(
0.0
(
0.0
%)
%)
%)
%)
%)
CALL STATISTICS
.
Call attemps (A seized) ......................../M050
Switched calls (B seized) ....................../M048
Technically successful calls (ACCEP,SFAIL)....../M046
Answered switched calls ......................../M070
Normally ended calls .........................../M047
Attempts
3441
2907
282
1502
0
Share
Hints:
For LU failure profiles run report 632.
(
(
(
(
84.5
8.2
43.7
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 call
can cause multiple B side calls).
PAGING
Average paging time ............................/M073
Paging success ................................./M056
1.4 sec
(
0.0 %)
236
0
(
2057 sec
0.0 %)
Hints:
For paging failure profile run report 632.
ANNOUNCEMENT
Nbr of calls .................................../M098
. Lost calls ................................../M099
Total listen time ............................../M100
114 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
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
. Incoming terminating traffic ................./M072
. Transit traffic ............................../M088
corresponding period from p_msc_vlr
start time of period ..............()
end time of period ................()
. IMSI attach attempts / MS ..................../M080
. IMSI detach / MS ............................./M081
. Intra VLR LU / MS ............................/M082
. Inter VLR LU / MS ............................/M083
. Periodic LU / MS ............................./M087
Note: counted only if all MSCs selected
corresponding period from p_msc_ho
start time of period ..............()
end time of period ................()
. Intra BSC HOs / call (MTC,MOC) .............../M084
. Inter BSC HOs / call (MTC,MOC) .............../M089
. Inter MSC HOs / call (MTC,MOC) .............../M085
5
1
0
erl
erl
erl
na
na
na
na
na
na
na
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
NW
MML
SUB
=
=
=
=
Service Terminal
Network Access
MML session
subscriber security
Measurement used: p_msc_secur_counter

===============================================================================
Security counters for MSC1
from 19980120 to 19980120
DN98614198
Issue 1-1 en
Nokia Networks Oy
115 (134)
NSS Network Doctor
Sum over
Counter
period
-------------------------------- ---------NW: successful attempts
7128
NW: unauthorised command
0
NW: unauthorised user
0
ST: sessions
14
ST: unauthorised user
0
MML: command check error
0
MML: log writing failed
0
MML: new users
0
MML: sessions
652
MML: unauthorised command
33
MML: unauthorised user
11
SUB: authentication failure
623
SUB: imei on black list
0
SUB: unknown imei
0
SUB: 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 day
ZUEM:EXEC=ON:STIME=24-0,FTIME=6-0,DUR=1,PARAL=5,REP=4
Test results per timeslot:
. = OK
U = untested because of lack of time
s = timeslot used for signalling link
R = not tested because seized
- = not tested because barred
E = error in testing system
F = faulty
Measurement used: p_msc_routine_test, p_msc_routine_unit
Note: This measurement is applicable only for EC08 (not for the newer EC1P).
===============================================================================
Total
116 (134)
Faulty Untested Untested

Faulty timeslots timeslots timeslots
Nokia Networks Oy
DN98614198
Issue 1-1 en
MSC reports
timeslots timeslots
(%)
nbr
(%)
--------- --------- --------- --------- --------5072
0
0
5072
100.0
ECU routine test results: MSC1
1998-03-26
********* Test results *********

Unit
00000000001111111112222222222333
index
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 been
constantly 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 constantly
seized or constantly free.
The measurement is activated by MML command (e.g. PCM 65, reporting daily):
TES:PCM=65:1
The measurement can be focused also on PCM timeslots or Circuit Groups.
Columns:
PCM
TSL
2M trunk
time slot of 2M trunk
Measurement used: p_msc_cir_sup

===============================================================================
Circuit seizure supervision for MSC1KUTOJA
Stop
PCM TSL day
---- ---- -------20
7 19981028
DN98614198
Issue 1-1 en
Period Use
Stop length of
hr:mi (days) tsl
----- ------ ---------14:49
1 not seized
Nokia Networks Oy
117 (134)
NSS Network Doctor
26
8
9
10
12
13
14
0
8
16
24
19981028
19981028
19981028
19981028
19981028
19981028
19981028
19981028
19981028
19981028
14:49
14:49
14:49
14:49
14:49
14:49
14:49
14:49
14:49
14:49
1
1
1
1
1
1
1
1
1
1
not
not
not
not
not
not
not
not
not
not
seized
seized
seized
seized
seized
seized
seized
seized
seized
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 the
operator
===============================================================================
Gapped IN services for MSC01
Day
yyyy-mm-dd
---------1999-04-20
Hour Call
Recd
SPC Operator
hh:mi addr
type overl
limit
----- ---------------- ----- ----- -------00:00
0
0
0
Figure 66. Report 652, Gapped IN services
118 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
HLR reports
HLR reports
This chapter describes the NSS Network Doctor reports derived from HLR
measurements. The reports are presented roughly in the order they appear in the
NSS Network Doctor user interface.
7.1
Administration of HLR measurements

measurements 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 to
analyse the PM tables. To do this, use the report Last HLR measurement
record times (623).
===============================================================================
=
=
LAST HLR MEASUREMENT RECORD TIMES
=
=
Network:
PLMN
=
HLR:
all HLR
=
===============================================================================
The date and time of last measurements available in the NMS database
are reported for each measurement type.
===============================================================================
GSM (ZTP)
.
HLR measurement .......................p_hlr_rep
.
Basic Services ......................p_hlr_basic
.
Supplementary Services ...............p_hlr_supp
.
Subscribers in the VLR ...........p_hlr_subs_vlr
.
EIR ...................................p_hlr_eir
.
EIR, Detailed Request .............p_hlr_eir_req
.
AC .................................p_hlr_ac_hlr
.
AC, Detailed VLR part ............p_hlr_ac_count
1998-06-25
1998-06-25
1998-06-25
1998-06-25
1998-06-25
no records
1998-06-25
1998-06-25
LOAD OBSERVATION (ZTL)

.
Load .................................p_hlr_load
1998-06-25 10:32
DN98614198
Issue 1-1 en
Nokia Networks Oy
10:00
10:00
10:00
10:00
08:00
08:00
08:00
119 (134)
NSS Network Doctor
OSI (ZOO)
.
OSI level 1 ..........................p_hlr_osi1
.
.
.
no
no
no
no
SECURITY (ZIR)
.
Security Counter ................p_hlr_secur_rep
.
Security Counters ...........p_hlr_secur_counter
1998-06-25 12:00
1998-06-25 12:00
FIELD REPORTING (ZTU)

.
Availability ........................p_hlr_avail
1998-06-25 00:00
records
records
records
records
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 and
last NSS measurement record times for each HLR (610). In this report
you 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 database
are reported for the selected measurement type by HLRs.
First meas.pd. (stop time)
Last meas.pd. (stop time)
Period duration max.
Period duration min.
Stop time of the

Stop time of the
Maximum duration
Minimum duration
first measurement period.

last measurement period.
of period.
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)
First meas.pd.
HLR name
(stop time)
-------------------- ----------------HLR1KUTOJA
1998-05-26 00:16
Period
Period
Last meas.pd.
duration duration
(stop time)
max.
min.
----------------- -------- -------1998-06-24 15:32
60
60
Figure 68. Report 610: First and last NSS measurement record times for
each HLR
120 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
HLR reports
7.1.3
Measurement flow
To check that the measurement flow is functioning, use the Records for a
HLR measurement (611) report. The number of records, minimum reporting
period and maximum reporting period are reported for every hour having
measurement results for the selected measurement type.
===============================================================================
=
=
RECORDS FOR A HLR MEASUREMENT
=
=
Network:
PLMN
=
BSC:
all HLRs
=
Measurement table: p_hlr_basic
=
===============================================================================
The number of records, minimum reporting period and maximum reporting
period are reported for every hour having measurement results for the
selected measurement type.
Note: Running this report takes a while. Patience please.
===============================================================================
Day
Hour
-------- ---19970118 0015
0030
0045
0100
Min
Max
prd
prd
(min) (min)
RECORDS
----- ----- ---------15
15
2
15
15
2
15
15
2
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 in
the HLR, run the report HLR CPU and MB load (606).
===============================================================================
=
=
HLR CPU AND MB LOAD
=
=
Network:
PLMN
=
Period:
from 19970228 to 19970509
=
===============================================================================
DN98614198
Issue 1-1 en
Nokia Networks Oy
121 (134)
NSS Network Doctor

If the average load is over 70 % (or 50 % for Message Bus),
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 hour
HLR
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 recommended
thresholds, 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 %
=
===============================================================================
If the average load is over 70 % (or 50 % for Message Bus),
These hours are highlighted with "!!!" .
Note: For MB there is no peak load available, and the peak load time of MB
shown 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
day
122 (134)
Peak Load
time
Peak Load Avg Load
Nokia Networks Oy
DN98614198
Issue 1-1 en
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) is
provided.
7.2.3
HLR availability profiles (641)
===============================================================================
=
=
HLR AVAILABILITY PROFILES
=
=
Network:
PLMN
=
HLR:
all HLRs
=
Period:
from 19971219 to 19980120
=
===============================================================================
Discon time
Discon time duplex
.
Unit restrt
Adm restrt
Pros restrt
Prepros restrt
Duplex restrt
Time when the unit was not in woex or spex state.

Time when none of the duplicated units were in woex
or spex.
Unit restarts.
Administrative restarts.
Processor restarts.
Restarts of subordinate preprocessors.
Simultaneous restarts of duplicated units.
Measurement used: p_hlr_avail

NOTE: Only units having restarts or disconnection time are reported.
===============================================================================
Availability profiles for HLR1
from 19971219 to 19980120
Day
Unit
yyyy-mm-dd
---------- ---------ACU-0-0
1998-01-04
1998-01-05
CCSU-5
1998-01-04
1998-01-05
1998-01-08
1998-01-09
1998-01-11
1998-01-12
Discon Discon
Hour
Unit
time
time Admin
Pros Prepros Duplex
hh:mm restrt (sec) duplex restrt restrt restrt restrt
----- ------ ------ ------- ------ ------ ------- ------00:00
2
-1
0
2
0
0
0
00:00
2
-1
0
2
0
0
0
00:00
4
-1
-1
2
0
0
-1
00:00
4
-1
-1
2
0
0
-1
00:00
5
-1
-1
0
0
0
-1
00:00
6
-1
-1
0
0
0
-1
00:00
8
-1
-1
0
0
0
-1
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.
DN98614198
Issue 1-1 en
Nokia Networks Oy
123 (134)
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 first
section gives a general profile, whereas the second section gives a detailed profile
per 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 requests
Triplet answers
Nbr of VLR triplet answers
Triplets total
Total nbr of triplet transfers
The second report gives a detailed profile per VLR address and Signalling
Point Code:
Triplet requests
Nbr of VLR triplet requests
Triplet 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
Day
yyyy-mm-dd
---------1998-03-26
Avg ACU
Hour
in use
Triplet
Triplet
Triplets
hh:mm
(%)
requests
answers
total
----- ---------- ---------- ---------- ---------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
124 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
HLR reports
from 19980326 to 19980326

VLR
SPC
address
address
------------------ ---------9289
Day
yyyy-mm-dd
---------1998-03-26
Hour
Triplet
Triplet
hh:mm
requests
answers
----- ---------- ---------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
Route Serv
The number of activated basic services.

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
Route
service
Serv
Act
Route
Serv
name
Act
(%)
Serv
(%)
------------------------- ---------- ------ ---------- -----Data c.d.a 300b/s
702
0.5
0
0.0
Data c.d.a 1200b/s
702
0.5
0
0.0
Data c.d.a 1200-75b/s
702
0.5
0
0.0
Data c.d.a 2400b/s
738
0.5
0
0.0
Data c.d.a 4800b/s
738
0.5
0
0.0
Data c.d.a 9600b/s
828
0.6
0
0.0
General bearer service
16425
11.2
31
43.1
Data c.d.s 1200b/s
702
0.5
0
0.0
Data c.d.s 2400b/s
702
0.5
0
0.0
Data c.d.s 4800b/s
702
0.5
0
0.0
Data c.d.s 9600b/s
702
0.5
0
0.0
DN98614198
Issue 1-1 en
Nokia Networks Oy
125 (134)
NSS Network Doctor
Data c.d.s general

Telephony
Short message MT/PP
Short message MO/PP
Fax gr3 and altern.speech
Autom. faxmile gr3
Alternate Line Service
15750
19539
19404
19404
16470
16767
16218
10.7
13.3
13.2
13.2
11.2
11.4
11.0
0
13
28
0
0
0
0
0.0
18.1
38.9
0.0
0.0
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
MML Activ
MML Deact
User Activ
User Deact
User Inquire
Average nbr of service provisions

Sum of service activations by MML
Sum of service deactivations by MML
Sum of service activations by the user
Sum of service deactivations by the user
Sum of services inquired by the user
Measurement used: p_hlr_supp

===============================================================================
HLR Supplementary Service Statistics for
from 20001107 to 20001107
HLR1
Supp
serv
Ave of
MML
MML
User
User
User
code
Provis
Activ
Deact
Activ
Deact
Inquire
---- ---------- ---------- ---------- ---------- ---------- ---------CLIP
2626
0
0
0
0
0
CLIR
2592
0
0
0
0
0
CFU
2626
0
0
185
46
88
CFB
2625
0
0
254
12
41
CFNA
2625
0
0
22
3
0
CFNR
2625
0
0
8
0
0
CT
2627
0
0
0
0
0
CW
2627
12
0
105
48
0
HOLD
2628
0
0
0
0
0
MPS
2625
0
0
0
0
0
CUG
8
0
0
0
0
0
AOCI
712
0
0
0
0
0
AOCC
6
0
0
0
0
0
BAOC
2624
0
0
44
0
26
BOIC
2624
0
0
5
0
0
BOIH
2623
0
0
0
0
0
BORO
2624
0
0
0
0
14
BAIC
1512
0
0
0
0
22
BIRO
2624
0
0
0
0
38
ODB
3216
0
0
0
0
0
===============================================================================
=
CCBS SERVICES
126 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
HLR reports
===============================================================================
Ave of Provis
Syst Activ
Syst Deact
MML Deact
User Activ
User Deact
Recall Deact
User Inquire
Average nbr of OCCBS/TCCBS service provisions

Sum of service activations by system
Sum of service deactivations by system
Sum of service deactivations by MML
Sum of service activations by the user
Sum of service deactivations by the user
Sum of service deactivations by recall
Sum of services inquired by the user
Measurement used: p_hlr_rep

===============================================================================
HLR CCBS Service Statistics for HLR1
from 20001107 to 20001107
OCCBS
-------------------------Ave of Provis : 2
Syst Activ
: Syst Deact
: 0
MML Deact
: 0
User Activ
: 0
User Deact
: 0
Recall Deact
: 0
User Inquiry
: 0
TCCBS
---------2
0
0
0
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
Average
VLR ISDN address
Subscribers
------------------ -----------
DN98614198
Issue 1-1 en
Nokia Networks Oy
127 (134)
NSS Network Doctor
24755
1
1
1
1
0
1
27831000010
316530300000
316540915000
393358908000
393358950000
393358953000
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 over
Counter
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
===============================================================================
=
128 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
HLR reports
=
HLR USAGE STATISTICS
=
=
Network:
PLMN
=
Period:
from 20010213 to 20010217
=
===============================================================================
DB opr
.
DB opr call (%)
DB opr mblty (%)
Home LU
Succ home LU
Fail home LU
Ave GPRS subs
Ave used space
Ave subs
HLRU max
HLRU min
HLRU data min
Number of database operations for call handling and

mobility management.
% of database operations for call handling.
% of database operations for mobility management.
Number of updates of home subscriber location.
% of successful home subscriber location updates.
% of failed home subsccriber location updates.
Average number of GPRS subscribers in HLR.
Average used space in HLR database in %.
Average number of subscribers in all VLRs.
Max. amount of HLRU units in HLR during reporting period
Min. amount of HLRU units in HLR during reporting period
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
Home visit fail %
Home ret att
DN98614198
Issue 1-1 en
Number of home subscriber visit attempts to other PLMNs.

Failure % of home subscriber visit attempts to other PLMNs.
Number of home subscriber returns from other PLMNs.
Nokia Networks Oy
129 (134)
NSS Network Doctor
Home ret fail %

Home LU att
Home LU fail %
DB oper call
DB oper mobili
DB use %
Subsc in VLR
HLRU sent
HLRU in HLR
Failure % of home subscriber returns from other PLMNs.

Number of home subscriber location updates.
Failure % of home subscriber location updates.
Database operations for call handling.
Database operations for mobility management.
Used space in HLR database.
Average nbr of subscribers in all VLRs during a period.
Nbr of HLRU units that have sent data.
Nbr of HLRU units in HLR.

===============================================================================
HLR profile for HLR1 1997-08-28
Home
visit
****
Hour att
hh:mm fail %
----- ------00:00
29
0.0
Home
ret
****
att
fail %
------48
0.0
Home
LU
****
att
fail %
DB opr
------- --------533
10998
4.9
DB opr
*****
DB
call (%)
Subsc
use HLRU
HLRU
mblty (%) in VLR
% sent in HLR
--------- ------- ------ ---- -----95.1
103433
45.0 na
0
4.9
01:00
20
0.0
30
0.0
453
4.6
5952
92.4
7.6
103529
45.0 na
02:00
6
0.0
18
0.0
246
2.8
4333
94.3
5.7
103756
45.0 na
03:00
7
0.0
11
0.0
197
3.6
3756
94.8
5.2
103945
45.0 na
04:00
6
0.0
15
0.0
146
1.4
2019
92.8
7.2
104330
46.0 na
05:00
8
0.0
6
0.0
126
12.7
1322
90.5
9.5
104331
46.0 na
06:00
17
0.0
27
0.0
245
4.1
2145
88.6
11.4
104334
46.0 na
Figure 79. Report 639: HLR profiles
7.8
Equipment identity register

The following reports are under the HLR Statistics Other HLR
Reports... menu.
7.8.1
EIR profile (644)

This report provides information on the mobile equipment that are authorised to
use the network, showing the number of equipment and IMEI requests for each
category, that is equipment on the white, grey or black list.
===============================================================================
=
130 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
HLR reports
=
EIR PROFILE
=
=
Network:
PLMN
=
MSC:
all MSCs
=
Period:
from 19980223 to 19980223
=
===============================================================================
Used space black
Used space grey
Used space white
Black reqs
Black entries
Grey reqs
Grey entries
White entries
White reqs
% of space used on black list (reserved records/all).

% of space used on grey list.
% of space used on white list.
Nbr of IMEI requests received for devices on black list.
Nbr of devices and series on black list.
Nbr of IMEI requests received for devices on grey list.
Nbr of devices and series on grey list.
Nbr of devices and series on white list.
Nbr of IMEI requests received for devices on white list.
Measurement used: p_hlr_eir

===============================================================================
HLR EIR Profile for HLR1
from 19980223 to 19980223
Day
yyyy-mm-dd
---------1998-02-23
Hour
hh:mm
----00:00
01:00
02:00
03:00
Used Used Used

space space space
black grey white
Black Black
Grey Grey
White White
(%)
(%)
(%) entries reqs entries reqs entries reqs
----- ----- ----- ------- ----- ------- ----- ------- ----0
0
0
0
-1
0
-1
2
0
0
0
0
0
-1
0
-1
2
0
0
0
0
0
-1
0
-1
3
0
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
DN98614198
Issue 1-1 en
Nokia Networks Oy
131 (134)
NSS Network Doctor
Day
Hour List
IMEI
IMEI
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
99
493002999263670
999-04-19 15:00 black
1 local
99
49309990710285
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
132 (134)
Nokia Networks Oy
DN98614198
Issue 1-1 en
Index
Numerics
60-minute reporting interval
37
A
abbreviations 16
actions to take before using 37
active measurements
HLR 119
MSC 38, 41
administration
HLR measurements 35, 119
MSC measurements 32, 41
announcement 33, 99
authentication centre 35, 124
handovers 33, 93
HLR
load and availability 35
security counters 128
service 125
usage 128
I
IN services
118
L
load and availability
HLR 121
MSC 44
checking
active measurements in HLRs 119
active measurements in MSCs 41
CPU load in HLR 121
CPU load in MSC 44
HLR measurement flow 121
HLRs sending data to the database 120
MSC measurement flow 43
MSCs sending data to the database 43
SS7 link load 49
circuit groups 107
clear codes 80
command line conventions 15
data calls 35
database administration
destinations 103
dtpad 13, 27
echo cancellation units 116

equipment identity register 130
NMS database counters 24

NMS/2000
load on 37
NMS/2000 database 21, 39
Nokia NMS release T12 13
NSS Network Doctor
menus 32
user interface 27
using 23
31
formulas 17
further information
DN98614198
Issue 1-1 en
14
Nokia Networks Oy
measurement flow
HLR 121
MSC 43
model reports 27, 32
monitoring
quality of a cellular network
user log data 30
MSC
benchmark 111
clear codes 33
load and availability 33
20
PCM timeslot 117

performance indicator 21
prerequisites
for effective analysis of the network
19
133 (134)
NSS Network Doctor
R
reporting
intervals 17, 37
procedures 20
reports
automatic running of
focusing your selection
front page description
identification numbers
layout 29
menus 32
models 27
output of 29
shortcuts for running
19
29
19
27
27
S
security 115
selecting
measurement scope 29
period of time 29
setting
history windows 39
signalling 34, 49
storing periods 39
subscriber facility usage 110
T
terms and concepts 16
text styles 14
timeslots 116
Top-level User Interface
traffic and success 34,
typographic conventions
20
100
14
U
user log
30,
36
V
VLR 33, 96
VLR subscribers
127
W
what you need to know first
where to find more 14
134 (134)
13
Nokia Networks Oy
DN98614198
Issue 1-1 en

Bien plus que des documents.

NSS NetDoc

Transféré par

Informations du document

Description :

Droits d'auteur :

Formats disponibles

NSS NetDoc

Transféré par

Description :

Droits d'auteur :

Formats disponibles

Titres liés

NSS Network Doctor

NSS Network Doctor

About this manual 13

Introduction to NSS Network Doctor 19

Using NSS Network Doctor 23

NSS Network Doctor

Actions to take before using the reports 37

Handover failure ratio (633) 93

HLR reports 119

NSS Network Doctor

Subscriber profiles in VLRs (640) 127

Text styles in this document

Command line conventions

Terms used in this document

Example of history windows in the NMS/2000 database

NSS Network Doctor

General work process 24

Interrelationship between reports, measurement tables, formulas and

NSS Network Doctor user interface 29

Report 512: Log statistics 30

Report 513: Network Doctor use statistics 31

Report 607: Last MSC measurement record times 43

Report 608: Records for a MSC measurement type 44

Report 605: MSC CPU and MB load 46

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

Figure 29. Report 669: LAPD error counters 78

NSS Network Doctor

Figure 60. Report 645: Circuit group to destination 110

MSC call clear codes of data calls (527)

Data call clear code groups by number destination (528)

Data service unit statistics (529)

GBS data service statistics (530)

MSC network benchmark (600):

Circuit group statistics (602)

Last MSC measurement record times (607)

Traffic category statistics (620)

HLR usage statistics (629)

VLR authentication profile (646)

Circuit group profile (649)

NSS Network Doctor

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

About this manual

About this manual

What you need to know first

Where to find more

Terms and concepts

What you need to know first

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

The system administration tasks of the UNIX operating system. An

A text processing utility, such as vi or dtpad. These text processors are

NSS Network Doctor

Where to find more

NSS Network Doctor, Feature Overview, DN00308755, for a brief

NSS Network Doctor, System Administrators Guide, DN98619372, for

NSS Network Doctor Formulas, Reference Guide, DN98619509, for

Changes in NSS Network Doctor, DN0128043, for detailed information on

Other Nokia documents

Performance Management Basic Operating Principles and Procedures,

Database Description for MSC/HLR Measurements, DN98619478, for

Traffic Measurement Report Formats, DN9817208.

Clear Code List, DN987436.

About this manual

Text styles in this document

Names of database tables

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

User interface components

Variable user input