G 452

Information
SURPASS hiS 700

Traffic Data Management - Counter
Description
A30828-X1176-G452-2-7618
Traffic Data Management - Counter Description
Information
SURPASS hiS 700
Important Notice on Product Safety

Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the
parts may also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.
Therefore, only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply
with the applicable safety standards.
The same text in German:

Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Spannung. Einige Teile
knnen auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverletzungen und
Sachschden fhren.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und
wartet.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Gerte
mssen die zutreffenden Sicherheitsbestimmungen erfllen.
Trademarks:
All designations used in this document can be trademarks, the use of which by third parties for their
own purposes could violate the rights of their owners.
Copyright (C) Siemens AG 2003-2004.

Issued by the Information and Communication Networks Group
Hofmannstrae 51
D-81359 Mnchen
Technical modifications possible.
Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
Reason for Update

Summary:
Adaptation for hiS 700 m
Details for first issue:

Chapter/Section
Short Description
5.2
New IP counters for signaling network element

measurement
5.5
signaling linkset IP measurement
5.8
SCCP association measurement
5.13.1
New SCCP screening counter
Issue History
Issue
Number
Date of issue
Reason for Update
01
11/2003
First issue
02
02/2004
Adaptation for hiS 700 m
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
This document consists of a total of 55 pages. All pages are issue 2.
Contents
1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Overview of traffic data management jobs . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Counters for traffic data recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4
4.1
4.1.1
4.1.2
Main processor load measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Measured values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Measured values per VCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Measured values per message handler . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
13
13
14
5
5.1
SS7 traffic measurements and monitoring . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of the SS7 traffic measurements and
SS7 monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sequence of SS7 traffic measurements . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sequence of first and interval measurement (SS7 monitoring) . . . . . . . . .
Signaling network element measurement. . . . . . . . . . . . . . . . . . . . . . . . . .
Measured values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signaling point measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signaling point utilization measurement . . . . . . . . . . . . . . . . . . . . . . . . . . .
Measured values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Obligatory signaling point utilization measurement. . . . . . . . . . . . . . . . . . .
Measured value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network MSU measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Measured values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signaling point measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Measured value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signaling link set measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Link set duration measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Measured values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Link set utilization measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Measured values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signaling Linkset IP Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Measured values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signaling destination point measurement . . . . . . . . . . . . . . . . . . . . . . . . . .
Measured values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signaling link measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Obligate link utilization measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Measured values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Link utilization measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Measured values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Obligate signaling link duration measurement . . . . . . . . . . . . . . . . . . . . . .
Measured values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Link duration measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Measured values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Link congestion measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
5.1.1
5.1.2
5.2
5.2.1
5.3
5.3.1
5.3.1.1
5.3.2
5.3.2.1
5.3.3
5.3.3.1
5.3.4
5.3.4.1
5.4
5.4.1
5.4.1.1
5.4.2
5.4.2.1
5.5
5.5.1
5.6
5.6.1
5.7
5.7.1
5.7.1.1
5.7.2
5.7.2.1
5.7.3
5.7.3.1
5.7.4
5.7.4.1
5.7.5
A30828-X1176-G452-2-7618
16
18
20
20
21
22
22
22
23
23
23
23
23
23
23
24
24
24
24
26
26
26
26
27
27
27
28
28
29
29
29
30
30
5.7.5.1
5.7.6
5.7.6.1
5.7.7
5.7.7.1
5.8
5.8.1
5.8.1.1
5.8.2
5.8.2.1
5.8.3
5.8.3.1
5.9
5.9.1
5.9.1.1
5.9.1.2
5.10
Information
SURPASS hiS 700
5.10.1
5.10.1.1
5.10.2
5.10.2.1
5.10.3
5.10.3.1
5.11
5.11.1
5.12
5.12.1
5.13
5.13.1
5.13.1.1
5.13.2
5.13.2.1
5.14
5.14.1
5.15
5.16
5.16.1
Measured values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
HSLink utilization measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Measured values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Obligate HSLink utilization measurement . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Measured values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
SCTP association measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Obligatory SCTP association utilization measurement . . . . . . . . . . . . . . . . 32
Measured values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Association utilization measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Measured values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Association duration measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Measured Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
MTP first and interval measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Monitored events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Link congestion measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Signaling point measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
SCCP measurement network-independent,
network-dependent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
SCCP error performance measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Measured values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
SCCP quality of service measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Measured values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
SCCP utilization measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Measured values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
SCCP measurement per SSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Measured values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
SCCP first and interval measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Enhanced SCCP screening measurement . . . . . . . . . . . . . . . . . . . . . . . . . 44
SCCP screening failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Measured values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
SCCP screening traffic measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Measured Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Enhanced SCCP screening first and interval measurement . . . . . . . . . . . . 47
SCCP measurement all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
ATM cell measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Measured values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6
6.1
Number portability ticket measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Output data (NPTM data record) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
7
7.1
7.2
SS7 traffic structure measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Sequence of SS7 traffic structure measurement . . . . . . . . . . . . . . . . . . . . . 53
Output data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
1 Introduction
This document describes the content and operation of traffic data management for the
SURPASS hiS 700. Traffic data management for SURPASS hiS 700 includes traffic
measurement, SS7 traffic monitoring (first and interval measurement) and SS7 traffic
structure measurement.
Traffic data management
Traffic measurement
MP load measurement
MTP measurement
SCCP measurement
ATM cell measurement
NP ticket measurement
SS7 traffic monitoring
MTP monitoring
SCCP monitoring
SS7 traffic structure measurement
Aims of traffic data recording

Analysis of the traffic measurement data plays an important part in ensuring effective
operation of the network node, in the planning and expansion of networks and in network traffic management.
Network planning and traffic forecasts
Analysis of traffic measurement data is the basis for planning new networks and expanding the existing network to meet future demands. Long-term traffic measurements (e.g. for some month) help to identify trends in traffic and to make traffic
forecasts. The measurement data also reveals extreme load situations and unused
resources, and this information can be taken into consideration when new network
components are being planned. In this way it is possible to achieve an optimum ratio
of investment to yield.
Network traffic management
The traffic data provides an accurate overview of the traffic situation in the network
and detects overload situations, unused network resources or faults in the network.
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
The network operator can respond with appropriate network management measures and make full use of the network resources. In this way the operator achieves
optimum customer satisfaction and charge losses due to rejected connections can
be kept low.
Administration of traffic data management
All features of traffic data management are controlled via tasks from the NetManager/Switch Commander.
The SS7 traffic measurement and monitoring data and the MP load data are written in
log files to the hard disk of the main processor (MP). The data are transferred from the
MP disk to the disk of the NetManager/Switch Commander with the Performance Data
Collector application. "Performance Data Collector" application serves as a central platform for performance data and offers it in ASCII formatted transmission files (post-processing files) to post-processing tools.
Traffic structure measurement and number portability ticket measurement write data in
special files on MP disk. Both files can be transferred to any postprocessing computer
with file transfer protocol over transmission control protocol/Internet protocol (FTP over
TCP/IP).
The administration of traffic data management is described in detail in the manual
OMN:EXCH - TR .
The User Manual Performance Data Collector gives an overview of the operation of the
Performance Data Collector application.
Postprocessing of traffic measurement data
Measurement data can be evaluated computer-aided with postprocessing programs.
Siemens offers the performance management tool SPOTS for postprocessing traffic data. SPOTS provides a series of reports which make provision for effective possibilities
for operation and planning. SPOTS can be installed on an optional NetManager/Switch
Commander Server and can use the full NetManager/Switch Commander basic structure. This provides a convenient and particularly effective variant for postprocessing
measurement and monitoring data.
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
2 Overview of traffic data management jobs

Components of traffic data management for SURPASS hiS 700:
Traffic measurements
Main Processor (MP) load measurement
SS7 traffic measurements
SS7 measurements are implemented for MTP and SCCP events, for SCCP
screening and for the load of HSL (ATM cell measurement)
Number portability (NP) ticket measurement
Traffic monitoring
SS7 traffic monitoring (first and interval measurements)
The first and interval measurements are part of the SS7 traffic measurements.
They represent a traffic monitoring component. The first and interval measurements monitor SCCP, MTP and SCCP screening events.
Tab. 2.1 shows the tasks for creating the measurements and the names of the measurements.
Task
Name of measured object
MP load traffic measurement

CR MPLDME
Main processor (MP) load measurement
SS7 traffic measurements and monitoring

CR SIGNEME
Signaling network element measurement
CR SIGPTME
Signaling point measurement
CR SIGLSME
Signaling link set measurement
CR SIGLSETIPME
Signaling linkset IP measurement
CR SIGDPME
Signaling destination point measurement
CR SIGLME
Signaling link measurement
CR SCTPASSOCME
SCTP association measurement
CR SIGFAIME
MTP first and interval measurement
CR SPME
SCCP measurement, network-independent
CR SPMEN
SCCP measurement, network-dependent
CR SPMESSN
SCCP measurement per SSN
CR SPMEALL
SCCP measurement, all
CR SPMEFAI
SCCP first and interval measurement, network-independent
CR SPMENFAI
SCCP first and interval measurement, network-dependent
CR SPSME
Enhanced SCCP screening measurement
CR SPSMEFAI
Enhanced SCCP screening measurement, first and interval
CR VCHANME
ATM cell measurement for virtual channels
Tab. 2.1
A30828-X1176-G452-2-7618
Overview of traffic data management tasks (create tasks)
Information
SURPASS hiS 700
Task
Name of measured object
NP ticket measurement
CR NPTME
Number portability ticket measurement

CR SIGTSMT
SS7 traffic structure measurement (with start and stop time)
CR SIGTSMD
SS7 traffic structure measurement (with start and stop time

and daily intervals)
CR SIGTSMW
SS7 traffic structure measurement (with start and stop time

and periodic weekly measurement intervals)
Tab. 2.1
10
Overview of traffic data management tasks (create tasks)
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
3 Counters for traffic data recording

Three types of counters are available for traffic measurement:
traffic volume counters
Time counters
Event counters
Traffic volume counters
The traffic volume counters (also load duration counters) indicate a holding time or a
load. The traffic volume counters are output as
Traffic volume, TV in Erls
TV indicates all the holding times within an integration period.
Traffic value or traffic carried, TC in mErl or dErl.
TC is the quotient of the observed traffic volume in the integration period and the integration period.
The following applies for an integration period of 15 minutes:
TV (Erls)
TC (Erl) =
900s
Time counters
Unlike the above-mentioned traffic volume counters, time counters measure the duration in which all the resources of the observed objects are used or blocked (Volume
counters measure the duration of a specified condition of a single system component).
Event counters
Event counters (also known as peg counters) measure how often signaling events
(pegs) occur. They are incremented each time the event occurs for which they are defined.
A30828-X1176-G452-2-7618
11
Information
SURPASS hiS 700
4 Main processor load measurement

The signaling traffic is controlled via central signaling channels by the signaling system
network control (SSNC). The main processor (MP) is the platform for implementing the
SSNC functions and the main components of the SSNC. This is a multiprocessor system which can contain up to 50 MPs when the SSNC is expanded to the maximum.
The CPU of an MP is divided into various virtual CPUs (VCPU). A VCPU is a unit to
which a specific CPU time budget is assigned. The most different software processes,
e.g. call processing, protocol handling, OA&M functions or traffic measurement run on
an MP. A VCPU is allocated to each process. Various software processes are combined
in a VCPU which have a common CPU time budget. Each MP has its own load model
with a fixed set of VCPUs with a budget >=0.
With MP load measurement, the operator receives an overview of the load situation of
selected MPs during the measurement period. The measurement registers the maximum load and the average load for the individual VCPUs and message handlers.
Sequence of MP load measurement
MP load measurement needs three tasks for recording traffic measured values:
Task to generate measurement reports for the desired measurement
The reports are created for the desired measurement type and the measurement
period (corresponds to the term integration time for the general traffic measurements). Possible measurement period values are 5 and 15 minutes.
Task to create traffic measurement for the desired MP
Task to create the log file to which the measurement report is written.
Only when these three tasks have been completed successfully can the measurement
reports be written to the disk of the MP in log files and the operator can access them.
There is no sequence for the input of the three tasks.
MP load measurement has no timing. The measurement is activated with the three Q3
tasks and runs until the operator deactivates it.
Output of the measured values
The log files for the measured values of the MP load measurement are created on the
MP disk.
The NetManager and also the Switch Commander are provided with the application
Performance Data Collector specially for the traffic measurement files. The Performance data collector transfers the measured values from the log files (hard disk of the
MP) into the common file store of the NetManager/Switch Commander. The measurement data is read from the log file of the MP, converted into ASCII format and stored in
the transmission files in the common file store of the NetManager/Switch Commander.
When the transmission of data was concluded successfully, the application Performance Data Collector deletes the data in the MP log files.
These ASCII files can be output and processed on the NetManager/Switch Commander,
e.g. the measured values can be read in Excel files. The file can also be transferred for
postprocessing. For information about the operation of the Performance Data Collector
application, see the User Manual for Performance Data Collector.
Number of measurements which can be started at the same time
The measurement can be started no more than twice per MP, i.e. one measurement for
the VCPU load and one measurement for the message handler load. A message han-
12
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
dler measurement can be created for the MP:SLT, MP:PD. and for the mixed load types
that include any of these load types. This means that, for example, in a maximum configuration of 50 MPs in the network, in which half are MP:SLTs, a maximum of 75 measurement objects can be measured simultaneously.
4.1
Measured values
The measured values are recorded for a measurement period of either 15 minutes or 5
minutes. The first measurement reports are always output at the earliest possible multiple of 5 minutes (5 minute measurement) or 15 minutes (15 minute measurement) independent of the start time of the measurement. This means that the measured values of
the first measurement report may be recorded for a measurement period of less than 5
or 15 minutes. These incomplete measurement reports are marked with an appropriate
flag (suspect flag in the output data record).
Example: Start time 12.32
Output of the first report for a 5 minute measurement: 12.35
Output of the first report for a 15 minute measurement: 12:45
The counters record the maximum load (max) and the average load (avg) per VCPU or
per message handler. During a measurement period, the measurement procedure
records the current load value for the relevant measurement object every 4 seconds.
The maximum load counters include the highest load value which occurred during a 4second interval within the measurement period. For the average load counters, the average is formed from the load values of the 4-second intervals for each measurement
period.
4.1.1
Measured values per VCPU

Object class: vcpuCurrentdata
The VCPU counters have generic names, because each MP has its own load model with
a fixed set of VCPUs with a budget >=0. To map the generic VCPU names to the real
names of the VCPUs of the MP for which the load measurements are performed, the
operator uses the task DISP OSLMRES, Parameter Virtual CPU utilization=Yes.
The output of this task contains the valid VCPUs per MP/load model, in the same order
as they are defined in the MP load measurement output. Only the IDLE VCPU is ignored
respectively skipped. The value IDLE VCPU can be calculated:
IDLE VCPU [mErl] = 1000 [mErl] - VCPU counter [mErl]
The measured VCPU load values are output in mErl.
Counter names
vcpuValid1Avg
vcpuValid1Max
.
.
.
vcpuValid13Avg
vcpuValid13Max
A30828-X1176-G452-2-7618
13
Information
SURPASS hiS 700
Example
Fig. 4.1
Output of Task DISP OSLMRES (VCPU for a selected MP)
For the selected MP shown in Fig. 4.1 for example the first four counters are mapped
like follows:
vcpuValid1Avg: System integrity average load
vcpuValid1Max: System integrity maximal load
vcpuValid2Avg: protocol handler average load
vcpuValid2Max: protocol handler maximal load
4.1.2
Measured values per message handler

Object class: mhCurrentdata
All the measured values are output in mErl.
ccs7MgrAverageLoad
Average load of the protocol handler for the SS7 network node interface
ccs7MgrMaximumLoad
Maximum load of the protocol handler for the SS7 network node interface
mhSpare04AverageLoad
This counter is not supplied with input
mhSpare04MaximumLoad
14
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
This counter is not supplied with input (reserve counter)
prhMgrBaseLoadAverageLoad
Average load of the protocol handler manager
prhMgrBaseLoadMaximumLoad
Maximum load of the protocol handler manager
sgtrMgrAverageLoad
Average load of the protocol handler for global title translation and SCCP global title
routing
sgtrMgrMaximumLoad
Maximum load of the protocol handler for global title translation and SCCP global title
routing
uniMgrAverageLoad
uniMgrMaximumLoad
A30828-X1176-G452-2-7618
15
Information
SURPASS hiS 700
5 SS7 traffic measurements and monitoring

The SS7 measurements register data for the Message Transfer Part (MTP) and data for
the Signaling Connection Control Part (SCCP). In addition the screening data is recorded.
The MTP and SCCP measurements are implemented in accordance with ITU-T Rec.
Q752 and ANSI (American National Standards Institute). The SCCP screening measurements are based on Bellcore Standard GR-82-CORE. As well as these standard
measurements, additional measurements are also performed.
The ITU-T measurements consist of a basic set of so-called obligatory measurements.
These obligatory measurements are required by the ITU-T for international networks.
Moreover, the more extensive measurements used in national networks are also available.
In addition to the measurements fulfilling ITU and ANSI requirements, measurements
according IP domain are implemented. The measurements of IP traffic uses the current
implementation of MTP measurements. So the user gets a consistent view of the traffic
in all parts of the SS7 network.
5.1
Overview of the SS7 traffic measurements and

SS7 monitoring
MTP measurements and monitoring

MTP-MSU measurements per network (signaling network element measurement,
CR SIGNEME)
Signaling point measurement, CR SIGPTME
Signaling link set measurement, CR SIGLSME
Signaling linkset IP measurement, CR SIGLSETIPME
Signaling destination point measurement, CR SIGDPME
Signaling link measurement, CR SIGLME
SCTP association measurement, CR SCTPASSOCME
MTP monitoring (MTP first and interval measurement, CR SIGFAIME)
SCCP measurements and monitoring
SCCP measurement network-independent, CR SPME
SCCP measurement network-dependent, CR SPMEN
SCCP measurement per SSN, CR SPMESSN
SCCP measurement all, CR SPMEALL
SCCP monitoring, network-independent (SCCP first and interval measurement
network-independent, CR SPMEFAI)
SCCP monitoring, network-dependent (SCCP first and interval measurement network-dependent, CR SPMENFAI)
Enhanced SCCP screening measurement and monitoring
SCCP screening measurement, CR SPSME
First and Interval measurement for screening failures
(SCCP screening monitoring) CR SPSMEFAI
ATM cell measurement for virtual channels CR VCHANME
The first and interval measurements represent a traffic monitoring component. Because
this traffic monitoring is closely connected with traffic measurement regarding administration and contents, it is explained in Sections 5.9 and 5.12.
16
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
Tab. 5.1 gives an overview about the SS7 measurements. The column measurement
time period shows the available values for the integration period of the measured values.
Task for creating
measurement/
monitoring
Measurement types
Measurement
time period
Section
CR SIGNEME
Net element measurement
5 min. /15 min.
5.2
CR SIGPTME
Signaling point utilization measurement
5 min. /15 min.
5.3.1
Obligatory signaling point utilization measurement
5 min /15 min
5.3.2
Network MSU measurement
5 min /15 min
5.3.3
5 min /15 min
5.3.4
Link set duration measurement
5 min /15 min
5.4.1
Link set utilization measurement
5 min /15 min
5.4.2
CR SIGLSETIPME
Linkset IP measurement
5 min. /15 min.
5.5
CR SIGDPME
Destination point measurement
5 min /15 min
5.6
CR SIGLME
Obligatory HSLink utilization

measurement
5 min. /15 min.
5.7.1
HSLink utilization measurement
5 min. /15 min.
5.7.2
Link congestion measurement
5 min. /15 min.
5.7.3
Link utilization measurement
5 min. / 15 min.
5.7.4
Obligatory link utilization measurement
5 min. /15 min.
5.7.5
Link duration measurement
5 min. /15 min.
5.7.4
Obligatory link duration measure- 5 min. /15 min.

ment
5.7.7
CR SIGLSME
CR SCTPASSOCME Obligatory association utilization

measurement
5 min. /15 min.
5.8.1
Association utilization measurement
5 min. /15 min.
5.8.2
Association duration measurement
5 min. /15 min.
5.8.3
Signaling link
5 min.
5.9
Signaling point
5 min.
5.9
CR SIGFAIME
* 5 min. for first and interval measurements, 15 min. for SCCP measurements and 30
min. for the SCCP screening measurements
Tab. 5.1
A30828-X1176-G452-2-7618
SS7 measurements
17
Task for creating

measurement/
monitoring
CR SPME/CR SPMEN
Information
SURPASS hiS 700
Measurement types
Measurement
time period
Section
SCCP error performance
15 min.
5.10.1
SCCP quality of service
15 min.
5.10.2
SCCP utilization
15 min.
5.10.3
CR SPMESSN
SCCP utilization per SSN
15 min.
5.11
CR SPMEFAI/CR
SPMENFAI
5 min.
5.12
CR SPSME
SCCP Screening failures
30 min.
5.13.1
SCCP Screening traffic measure- 30 min.

ment
5.13.2
CR SPSMEFAI
SCCP Screening failures
5 min.
5.14
CR SPMEALL
SCCP measurement types all
5 min./15 min./
30 min.*
5.15
CR VCHANME
ATM cell measurement for virtual

channels
15 min.
5.16
* 5 min. for first and interval measurements, 15 min. for SCCP measurements and 30
min. for the SCCP screening measurements
Tab. 5.1
5.1.1
SS7 measurements (Cont.)
Sequence of SS7 traffic measurements

Administration
For the SS7 measurement, three tasks are needed to record traffic measurements:
Task for creating a scheduler for the desired measurement
This task defines the following for a measurement
The measurement time period (corresponds to the term integration time for the
general traffic measurements), possible values are 5, 15 and 30 minutes, see
Tab. 5.1.
The time sequence of the measurement (start and stop time and measurement
intervals)
Task for creating the desired traffic measurement
This task defines the following for a measurement
The measurement type
The measurement time period, possible values are 5, 15 and 30 minutes
Task for creating the log file on the disks of the MP to which the measured values
are written (File name: PM_SCANREP).
Only when these three tasks have been completed can the measured values be written
to the disk of the MP in log file and the operator can access them.
18
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
Output of the measured values

The log file for the measured values of SS7 measurements is created on the hard disk
of the MP. Therefore, it cannot be processed with the commands of CP file management
in the same way as the measurement files of the general traffic measurements.
The NetManager and also the Switch Commander are provided with the application
Performance Data Collector (PDC) specially for the traffic measurement files. The Performance Data Collector transfers the measured values from the hard disk of the MP to
the disks of the NetManager/Switch Commander. The measurement data is read from
the log file of the MP, converted into ASCII format and stored in the transmission files in
the common file store of the NetManager/Switch Commander. When the transmission
of data was concluded successfully, the application Performance Data Collector deletes the data in the MP log file.
These ASCII files can be output and processed on the NetManager/Switch Commander,
e.g. the measured values can be read in Excel files. The file can also be transferred for
postprocessing. For information about the operation of the Performance Data Collector
application, see the User Manual for Performance Data Collector.
Number of measurements that can be started simultaneously
SCCP, MTP, SCCP screening, ATM cell measurement and MP load measurement:
The following guideline applies for the sum of SCCP and MTP measurements and
monitoring, MP load and ATM cell measurement: Per network element, up to 2500
measurement objects can be measured simultaneously on the SSNC as a 15minute measurement, or 2500 measurement objects as a 5-minute measurement.
The restrictions are based on the capacity of the Application Server (PDC server) of
the NetManager/Switch Commander.
MTP measurement
As opposed to the general traffic measurements, the number of measurements
which run in parallel is not restricted. Also the number of objects which can be measured at the same time is not restricted. All the resources in the system can be measured in parallel. However, these options should not be exploited to the full because
problems in the file transfer function to the NetManager/Switch Commander may occur as a result (see above).
Obligatory measurement and normal measurement cannot be executed for a measurement object at the same time. For example: For a particular signaling point either "Signaling Point Utilization Measurement" or "Obligatory Signaling Point
Utilization Measurement" can be set up.
SCCP screening measurement
You can start two SCCP screening measurements ( for screening failures and for
screening traffic measurement) for each screening domain.
Time control
The measured values are either recorded for a measurement time period (corresponds
to the term integration time for the general traffic measurement) of 15 minutes or 5 minutes.
Any time can be entered as the start time.
The first measured values are output
for a 5 minute measurement at the next possible multiple of 5 minutes.
for a 15 minute measurement at the next possible multiple of 15 minutes.
A30828-X1176-G452-2-7618
19
Information
SURPASS hiS 700
Therefore, the first measurement may be incomplete, which is marked in the output data
record with the Suspect flag.
The last measurement report is always complete because the end of the measurement
is rounded off upward, so that a complete measurement report is output.
Example:
Start time: 12.32
Stop time: 13.47
Output of the last report for a 5 minute measurement:13.50
Output of the last report for a 15 minute measurement: 14.00
5.1.2
Sequence of first and interval measurement (SS7 monitoring)

Administration
Two tasks (for a measurement log file and for monitoring) need to be created for the first
and interval measurements because these measurements do not require a scheduler.
Task for creating the measurement log file for QoS alarms (file name: PM_QOS)
Task for creating the first and interval measurement
This task defines the measurement type
You can also start the first and interval measurement for signaling links by creating the
signaling link. Logging is only possible in this case if log files exist for storing the alarms
and interval scanning reports.
Output of alarms and measured values
For the QoS alarms and the interval reports the remarks in Section Output of the measured values are applicable.
The "alarm handler" function of the Performance Data Collector is an additional option
that enables real-time processing of QoS alarms. The alarm handler forwards the QoS
alarms in real time to a data post-processing system (DPSS), e.g. the Performance
Management Tool SPOTS.
You will find notes on the operation of the Performance Data Collector application in
the User Manual Performance Data Collector.
QoS alarms of MTP first and interval measurement are additionally displayed on the
NetManager in the alarm surveillance application or respectively on the Switch Commander in the alarm and message display.
5.2
Signaling network element measurement

Object class: switchingElementMeasurement
(MTP/MSU measurement per network)
With this measurement the incoming, outgoing, discarded and transit MSUs are recorded at the network node level.
20
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
5.2.1
Measured values
numInMSU
Number of incoming MSUs per network node
numLostMSURoutErr (ITU-T Q752/5.5)
Number of discarded MSUs because of routing errors per network node
Discarded MSUs can refer to major routing errors in the SS7 network and require an
MTP route verification test.
Discarded MSUs occur because of the following reasons:
The network indicator (NI) in the incoming MSU is compared with the NI of the incoming link. In case of inconsistency, the relevant MSU is discarded. (The error is
only detected if NI screening is active.)
Circular routing: The OPC of the incoming MSU is identical to its own special signaling point code.
The incoming MSU contains an unknown user in the service indicator (SIO). The
cause for this can be an incorrect encoding in the SIO field of the MSU.
The incoming MSUs contain an unknown message type
The incoming MSUs contain an unknown CIC (Circuit Identification Code)
The incoming MSUs have an invalid DPC. A DPC is invalid if it is unknown in its own
database of the network node.
The incoming MSUs may not be rerouted into the network if OPC/DPC screening
has been administered. (This error is only detected if OPC/DPC screening is active.)
Ping-pong effect: The incoming and the outgoing link set are the same for MSU.
The incoming MSUs have an invalid OPC. An OPC is invalid if it is unknown in the
database of the network node.
The incoming MSU contains an invalid point code. For example, a 14-bit point code
is invalid in a network which supports 24-bit point codes.
The outgoing MSU is routed to a link which does not exist in the corresponding database. This error is also taken into account for the first and interval measurement.
The MSU arriving from the network contains an invalid SCP. This case occurs if an
adjacent STP sends the following message: TFP (transfer prohibited), TFA (transfer
allowed) or RST (route set test).
The incoming MSU contains an invalid SLC (signaling link code).
The incoming MSU was received from a nonadjacent DPC.
numOutMSU
Number of outgoing MSUs per network
numTransitMSU
Number of transit MSUs per network
mSUsThroughSwitchedOctets
This measurement represents the sum of all through switched octets counted on a link
basis over a complete switch. The number of octets is output in Kilo octets.
mSUsOriginatedOctets
This measurement represents the sum of all originated octets counted on a link basis
over a complete switch. The number of octets is output in Kilo octets.
mSUsTerminatedOctets
This measurement represents the sum of all terminated octets counted on a link basis
over a complete switch. The number of octets is output in Kilo octets.
A30828-X1176-G452-2-7618
21
Information
SURPASS hiS 700
nodeIsolationForAnyReason
For the network node-based measurements nodeIsolationForAnyReason the counters
of all DPCs in the network node for routeSetUnavailable (number of failures of a Routeset per destination, Q.752/4.9) are summed.
nodeIsolationDuration
For the network node-based measurements nodeIsolationDuration the counters of all
DPCs in the network node for routeSetUnavailableDuration (duration of non-availability
of a Routeset, Q.752/4.10) are summed.
numAssocUnavailable
The number of unavailable associations of the network element is measured.
numIpLsetUnavailable
The number of unavailable IP-linksets of the network element is measured.
5.3

The signaling point measurement can be created for the following measurement objects:
5.3.1

Object class: allSignallingPointUtilizationData
This measurement is implemented as a network-based measurement. The non-availability data for all DPCs of the network (adjacent DPCs) is determined.
5.3.1.1
Measured values
adjacentInaccessibleDuration ITU-T Q752/5.2
The counter records the duration during which the adjacent DPC is not accessible. The
failure durations per destination are summed for the entire network. The measurement
is based on the measurement for the object routeSetUnavailableDuration (duration of
the non-availability of a Routeset, Q.752/4.10, reasons for non-accessibility, see Chap.
5.6.1, routeSetUnavailable).
adjacentInaccessibleEvents ITU-T Q752/5.1
The counter records the number of cases in which the adjacent DPC is not accessible.
The counter sums the failures per destination for the entire network. The measurement
is based on the measurement for the object routeSetUnavailable (number of failures of
a Routeset per destination, Q.752/4.9, reasons for non-accessibility, see Chap. 5.6.1,
routeSetUnavailable).
22
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
5.3.2

Object class: oblSignallingPointUtilizationData
This measurement is implemented as a network-based measurement. The obligatory
non-availability data for all DPCs of the network (adjacent DPCs) are determined.
5.3.2.1
Measured value
adjacentInaccessibleDuration ITU-T Q752/5.2
The counter records the duration during which the adjacent DPC is not accessible. The
failure durations per destination are summed for the entire network. The measurement
is based on the measurement for the object routeSetUnavailableDuration (duration of
the non-availability of a Routeset, Q.752/4.10, reasons for non-accessibility, see Chap.
5.6.1, routeSetUnavailable).
5.3.3

Object class: perNetCounterMSU
For this measurement object, the incoming, outgoing and transit MSUs per network are
measured.
5.3.3.1
Measured values
numInMSUperNet
Number of incoming MSUs per network.
numOutMSUperNet
Number of outgoing MSUs per network.
numTransitMSUperNet
Number of transit MSUs per network.
5.3.4

Object class: signallingPointData
For this measurement object, the number of discarded MSUs are recorded.
5.3.4.1
Measured value
discardedMSUs (ITU-T Q.752/5.5)
Number of discarded MSUs per link because of routing errors, see description of
counter NumLostMSURoutErr.
5.4
Signaling link set measurement

Signaling link set measurement can be set up for the following measurement objects:
A30828-X1176-G452-2-7618
23
5.4.1
Information
SURPASS hiS 700

Object class: signallingLinkSetDurationData
The measurement records the number of unavailable cases per link set and the unavailability duration per link set.
5.4.1.1
Measured values
numLinkSetNotAvail
Number of times a link set is unavailable during a measurement time period.
slsUnavailable (ITU-T Q.752/4.2)
Unavailability duration of the link set in seconds
The counter is started if the last link of this link set assumes the inactive mode. Reasons for this are: local blocking, foreign blocking, local and foreign blocking or failure of
the remote processor. The counter is stopped if the link set is active again. The counter
is reincremented for each measurement time period.
5.4.2

Object class: signallingLinkSetUtilizationData
This measurement records data for the utilization of link sets.
Separate counters for ITU-T networks and for ANSI networks are implemented for the
measurement. For each network type only the appropriate counter data are recorded in
each case.
5.4.2.1
Measured values
ITU-T networks
receivedMSUs
Number of received MSUs.
This measurement corresponds to measurement ITU-T Q.752/3.5.
transmittedMSUs
Number of transmitted MSUs.
receivedOctets
Number of received MTP Level 3 Service Data Units.
transmittedOctets
Number of transmitted octets.
The measurement corresponds to measurement ITU-T Q.752/3.1
retransmittedOctets
Number of retransmitted octets
24
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
lostMSUsBufferOverflow
This measurement represents the sum of the distributed per link measurements concerning local buffer overflow counted by MTP L2 MH. In networks with 3 congestion levels the counter is always '0'.
The measurement corresponds to measurement ITU-T Q.752/3.10.
ANSI networks
receivedMSUs
Number of received MSUs.
transmittedMSUs
Number of transmitted MSUs.
receivedOctets
Number of received MTP Level 3 Service Data Units.
transmittedOctets
Number of transmitted octets.
The measurement corresponds to measurement Q.752/3.1
retransmittedOctets
Number of retransmitted octets
lostMSUsBufferOverflow
This measurement represents the sum of the distributed per link measurements concerning local buffer overflow counted by MTP L2 MH. In networks with 3 congestion levels the counter is always '0'.
lostMSUsCongestionEventThreshold-1
Number of MSUs rejected per link set because the L1 congestion threshold value has
been exceeded. The measurement is only relevant for networks with three congestion
levels. For networks with one congestion level this measurement is 0.
A30828-X1176-G452-2-7618
25
5.5
Information
SURPASS hiS 700
Signaling Linkset IP Measurement

Object class: ipLinkSetInformationData
This measurement records IP link set information data. The counters register the number of unavailable cases per IP link set and the unavailable duration per IP link set.
5.5.1
Measured values
numIpLinkSetUnavailable
The counter records in M3UA (MTP3 user adaption layer) Management the cases, when
the IP linkset is not available during a measurement time period.
ipLinkSetUnavailableDuration
This counter records the total time in seconds for an IP link set unavailable within a measurement time period. The counter is started when M3UA Management announces an
IP linkset is unavailable. The counter is stopped when M3UA Management announces
IP link set is available. The counter is reincremented for each measurement time period.
5.6
Signaling destination point measurement

Object class: routeSetInformationData
With this measurement the route set failures and their duration per signaling destination
point are recorded.
5.6.1
Measured values
dpcIsAdjacent
Marks the DPC of the route set as adjacent or nonadjacent
routeSetUnavailable (ITU-T Rec.Q 752/4.9)
Number of route set failures per destination
Reasons for route set failure:
The last link of a link set fails and there is no alternative route in the relevant set.
When the last link in a linkset is failed and no alternative route to the concerned route
set is available
The TFP (transfer prohibited) message is received and there is no alternative route
in the relevant set.
routeSetUnavailableDuration (ITU-T Q.752/4.10.)
Unavailability duration of a route set. The counter is output in seconds/destination.
The counter is started if L3 network management (layer 3 network control) reports an
unavailable route set. The counter is stopped if L3 network management (layer 3 network control) reports the route set to be available again.
The counter is reincremented for each measurement time period.
26
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
5.7
Signaling link measurement

This measurement records the data for signaling links. The following measurement
types are available for the measurement:
Obligatory link utilization measurement
Obligatory link duration measurement
Obligatory HSLink utilization measurement
5.7.1
Obligate link utilization measurement

Object class: oblSignallingLinkUtilizationData
This measurement records the obligatory signaling link utilization data according to
ITU-T. In addition to these standard measurements additional measurements are also
executed. The measurement is for narrowband networks only.
5.7.1.1
Measured values
receivedOctetsSIFSIO
Number of received SIF and SIO octets per link. The measurement corresponds to the
ITU-T Q.752/3.4 measurement.
signUnitsReceived
Number of incoming faulty MSUs per link.
Reasons for errors:
Checksum error
SIF and SIO exceed 272 bytes
This measurement corresponds to the ITU-T Q.752/1.8 measurement.
transmittedOctetsSIFSIO
Number of transmitted SIF and SIO octets per link. The measurement corresponds to
the ITU-T Q.752/3.1 measurement.
discardedMSUs ITU-T Q.752/3.10.
Number of discarded MSUs because of overload.
Layer 2 (message transfer) monitors an administrative signaling link overload threshold
value. If the threshold value is reached, layer 2 (message transfer) discards the MSU
and the counter is incremented.
slLocalInhibited
Sum of all events which lead to link status local inhibited. The events are counted for
each link. A link can be administratively put into the status local inhibited. The remote
link concerned in the adjacent network node then goes into the status remote inhibited.
The two links are no longer available for normal signaling traffic but test MSUs can still
be sent over them.
slRemoteInhibited
Sum of all events which lead to the status remote inhibited for an adjacent link. The
events are counted for each link.
A30828-X1176-G452-2-7618
27
Information
SURPASS hiS 700
A link can be administratively put into the status local inhibited The remote link concerned in the adjacent network node then goes into the status remote inhibited. The
two links are no longer available for normal signaling traffic but test MSUs can still be
sent over them.
slLocalBlocked
This counter is not supported for this version.
Sum of all events which lead to link status local blocked. The events are counted for
each link.
slRemoteBlocked
Sum of all events which lead to link status remote blocked. The events are counted for
each link.
5.7.2

Object class: allSignallingLinkUtilizationData
This measurement records signaling link utilization data (for narrowband only).
5.7.2.1
Measured values
receivedMSUs
Number of received MSUs. The measurement corresponds to the ITU-T Q.752/3.5 measurement.
receivedOctetsSIFSIO
Number of received SIFs and SIO octets. The measurement corresponds to the ITU-T
Q.752/3.4 measurement.
retransmittedOctets
Number of retransmitted octets per link. The measurement corresponds to the ITU-T
signUnitsReceived
Number of received faulty signaling units. The measurement corresponds to the ITU-T
transmittedMSUs
Number of transmitted MSUs. The measurement corresponds to the ITU-T Q.752/3.3
measurement.
transmittedOctetsSIFSIO
Number of transmitted SIFs and SIO octets. For this value the repeated octets (ITU-T
Q.752/3.1) are not counted. The measurement corresponds to the ITU-T Q.752/3.2
measurement.
discardedMSUs ITU-T Q.752/3.10.
Number of discarded MSUs.
Layer 2 (message transfer) monitors the administrative signaling link overload threshold
value. If the threshold value is reached, layer 2 discards the MSU and the counter is incremented.
28
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
slLocalInhibited
Sum of all events which lead to link status local inhibited. The events are counted for
each link.
sent over them.
slRemoteInhibited
Sum of all events which lead to the status remote inhibited for an adjacent link. The
events are counted for each link
sent over them.
slLocalBlocked
These counters are not supported for this version.
Sum of all events which lead to link status local blocked. The events are counted for
each link
slRemoteBlocked
Sum of all events which lead to link status remote blocked. The events are counted for
each link
5.7.3
Obligate signaling link duration measurement

Object class: oblSignallingLinkDurationData
This measurement records the available obligatory signaling link data and additional data. The measurement is for narrowband only.
5.7.3.1
Measured values
slInServiceDuration Q.752/1.1
Availability duration (in seconds) of the link. The counter is started if the link is in the active mode (the link is active and the link test ran successfully).
slUnavailabilityDuration ITU-T Q.752/2.1
Unavailability duration (in s) of a link (any reason) because of local blocking, foreign
blocking, local and foreign blocking or failure of the remote processor. The counter is
started if the link assumes the inactive mode. The counter is stopped if the link is active
again. The counter is reincremented for each measurement time period.
inhLinkDurUnavail
Duration (in seconds) of the unavailability of a link due to the inhibit state.
5.7.4

Object class: all30MinSignallingLinkDurationData
With this measurement, the unavailability duration and the availability duration of the
signaling link are recorded.
A30828-X1176-G452-2-7618
29
5.7.4.1
Information
SURPASS hiS 700
Measured values
slFailed (ITU-T Q.752/2.7)
Duration (in s) for as long as a link stays in the "faulty" mode during a measurement time
period. The link is in the unavailable mode, i.e. no MSUs can be sent via the link. The
counter is started if the link assumes the faulty mode. The counter is stopped if the link
is active again. The counter is reincremented for each measurement time period.
Reasons for the link error are related to MTP level 2 or the SAAL layer is unavailable or
there is a hardware fault (SLT).
sIInServiceDuration (ITU-T Q.752/1.1)
Availability duration of the link. The counter is started if the link is in the active mode
(the link is active and the link test ran successfully).
slRemoteProcOutage (ITU-T Q.752/2.9 and also 3.2.6/Q.704)
Unavailability duration (in seconds) of the signaling link because the remote processor
failed. The link is active in this mode, but not tested and MSUs cannot be sent via the
link. The counter is started if the link changes to the "unavailable" mode because the
remote processor failed. The counter is stopped if the link changes to another mode
than the one described above. The counter is reincremented for each measurement
time period.
sIUnavailabilityDuration (ITU-T Q.752/2.1)
Unavailability duration of a link (any reason) because of local blocking, foreign blocking,
local and foreign blocking or failure of the remote processor. The counter is started if the
link assumes the inactive mode. The counter is stopped if the link is active again. The
counter is reincremented for each measurement time period.
inhLinkDurUnavail
Duration (in seconds) of the unavailability of a link due to the inhibit state.
5.7.5

Object class: signallingLinkCongestionData
This measurement records the overload data of the signaling links.
Separate counters for ITU-T networks and for ANSI networks are implemented for the
measurement. For each network type only the appropriate counter data are recorded in
each case. For combined networks both counter groups are output.
5.7.5.1
Measured values
ITU-T Networks
slCongestedDuration (ITU-T Q.752/3.7)
Overload duration (in s) of a signaling link. The individual blocking durations are added
within a measurement time period. The counter is reincremented for each measurement
time period.
slCongestedStarts (ITU-T Q.752/3.6 and also 3.8/Q.704)
Number of times a link is unavailable during a measurement time period. In case of narrowband links, the measured values are determined by layer 2 message management
and in case of high-speed links (SAAL) by layer 3 network management.
30
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
ANSI Networks
slCongestionindication-1
Sum of all events which lead to link status congestion level1, i.e. the threshold Onset
level 1 is crossed during the measurement interval.
Sum of all events which lead to link status congestion level 2, i.e. the threshold Onset
The counter of this measurement is the sum of all begin events of signaling link in congestion level 3, i.e. when threshold Onset level 3 is crossed, during the measurement
interval.
5.7.6

Object class: saalAllSignallingLinkUtilizationData
This measurement records the utilization data for high-speed links. This measurement
can only be taken on high-speed links.
5.7.6.1
Measured values
discardedSD-PDUs
Number of discarded sequenced data protocol data units because of overload. The
measurement corresponds to the 163 TR 84/2.2.10 measurement.
The SAAL (signaling ATM adaption layer) monitors the administrative signaling link
overload threshold value. Should the threshold value be reached, the SAAL discards the
PDU and the counter is incremented per link. This measurement is only required for the
international method.
receivedSD-PDUs
Number of received SSCOP (Service Specific Connection Oriented Protocol) sequenced data protocol data units. The measurement corresponds to the 163 TR
84/2.2.5 measurement.
sduReceivedOctets
Number of received MTP layer 3 service data unit octets. The measurement corresponds to the 163 TR 84/2.2.4 measurement.
sduRetransmittedOctets
Number of retransmitted SSCOP sequenced data protocol data units. The measurement corresponds to the 163 TR 84/2.2.2 measurement.
sduTransmittedOctets
Number of transmitted MTP layer 3 service data unit octets. The measurement corresponds to the 163 TR 84/2.2.1 measurement.
transmittedSD-PDUs
Number of transmitted SSCOP sequenced data protocol data units. The measurement
corresponds to the 163 TR 84/2.2.3 measurement.
A30828-X1176-G452-2-7618
31
5.7.7
Information
SURPASS hiS 700
Obligate HSLink utilization measurement

Object class: saalOblSignallingLinkUtilizationData
This measurement records the obligatory utilization data for high-speed links (SAAL).
This measurement can only be created for high-speed links.
5.7.7.1
Measured values
discardedSD-PDUs
Number of sequenced data protocol data units discarded because of overload. The
measurement corresponds to the 163 TR 84/2.2.10 measurement.
The SAAL (signaling ATM adaption layer) monitors the administrative signaling link
overload threshold value. Should the threshold value be reached, the SAAL discards the
PDU and the counter is incremented per link.
sduReceivedOctets
Number of received MTP layer 3 service data unit octets. The measurement corresponds to the 163 TR 84/2.2.4 measurement.
sduTransmittedOctets
Number of transmitted MTP layer 3 service data unit octets. The measurement corresponds to the 163 TR 84/2.2.1 measurement.
5.8
SCTP association measurement

The SCTP (Stream Control Transmission Protocol) association measurement records
utilization data of SCTP associations and data concerning availability and unavailability
of the associations.
5.8.1
Obligatory SCTP association utilization measurement

Object class: oblAssociationUtilizationData
This measurement records the obligatory SCTP association utilization data.
5.8.1.1
Measured values
numM3UA-MsgSent
This counter records the number of M3UA (MTP3 user adaption layer) messages sent
to the peers per association.
numM3UA-MsgReceived
This counter records the number of M3UA messages per association received from the
peers.
numSCTP-PacketsSent
This counter records the number of SCTP (Stream Control Transmission Protocol)
packets per association sent to the peers.
numSCTP-PacketsReceived
This counter records the number of SCTP packets per association received from the
peers.
32
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
numOctetsSentPerAssoc
This counter records the number of transmitted octets per association (inclusive SCTP
control chunks and SACK chunks).
numOctetsReceivedPerAssoc
This counter records the number of received octets per association (inclusive SCTP
control chunks and SACK chunks).
numM3UA-MsgDiscarded
This counter records the number of discarded M3UA messages per association due to
congestion.
5.8.2
Association utilization measurement

Object class: allAssociationUtilizationData
This measurement records all SCTP association utilization data.
5.8.2.1
Measured values
numM3UA-MsgSent
This counter records the number of M3UA messages sent to the peers per association.
numM3UA-MsgReceived
This counter records the number of M3UA messages per association received from the
peers.
numSCTP-PacketsSent
This counter records the number of SCTP packets per association sent to the peers.
numSCTP-PacketsReceived
This counter records the number of SCTP packets per association received from the
peers.
numOctetsSentPerAssoc
This counter records the number of transmitted octets per association inclusive SCTP
control chunks and SACK chunks.
numOctetsReceivedPerAssoc
This counter records the number of received octets per association inclusive SCTP control chunks and SACK chunks.
numM3UA-MsgDiscarded
This counter records the number of discarded M3UA messages per association due to
congestion.
numOctetsSentPerAssocNoCtrl
This counter records the number of transmitted octets per association without SCTP
control chunks.
numOctetsReceivedPerAssocNoCtrl
This counter records the number of received octets per association without SCTP control chunks.
A30828-X1176-G452-2-7618
33
Information
SURPASS hiS 700
numOctetsRetransPerAssocNoCtrl
This counter records the number of retransmitted octets per association without SCTP
control chunks.
5.8.3
Association duration measurement

Object class: allAssociationDurationData
This measurement records all SCTP association duration data.
5.8.3.1
Measured Values
assocUnavailable
The counter records the duration of unavailability for an required association. The duration counter is restarted for each measurement time period.
assocAvailable
The counter records the duration of availability for an required association. The duration
counter is restarted for each measurement time period.
sctpPathUnavailable
The counter records the duration of SCTP path unavailability within an association. The
duration counter is restarted for each measurement time period.
sctpAssocCongestion
The counter records the cumulative duration of congestion per association. The duration
counter is restarted for each measurement time period.
numCongestionLevel1
Number of the congestions events of an association, i.e. the counter is implemented
when the threshold level 1 is crossed.
numCongestionLevel2
numCongestionLevel3
numPerAssocUnavailable
The number of unavailability events of an association.
5.9
MTP first and interval measurement

The MTP first and interval measurement is a traffic monitoring which monitors the overload of signaling links and discarded MSUs per network because of link blocking and
routing errors. A QoS alarm report is generated by traffic monitoring whenever the value
of one of the monitored parameters in a network element reaches the predefined threshold.
MTP monitoring is started with the task for the first and interval measurement. However,
MTP monitoring can also be started immediately on creating the signaling link. A requirement is that there must also be a log file which records the measurement data.
34
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
MTP first and interval measurement can be started for the following measurement types:
The measurement time period is 5 minutes for the first and interval measurement.
Two reports are generated for each of the two measurement types:
Alarm report for the first occurrence of an event (quality of service alarms)
Interval report
Alarm report
A quality of service (QoS) alarm report is generated if one of monitored events reaches
the 1 threshold value. That is, an alarm report is generated if the monitored event occurs for the first time in the measurement time period.
The alarm report contains both the event and further information, e.g. information about
the priority of the alarm. The alarm report for monitoring the signaling point data, contains, inter alia, both the monitored event and the reasons for the occurrence of discarded MSUs and information about DPC, OPC, SIO and CIC.
Interval report
The measurement procedure generates both an alarm report for the first occurrence of
the event and an interval report which contains all the events which occurred during the
measurement time period. The interval report is output only if an alarm report was generated in the measurement time period. This report also contains both the measured values and additional information.
Alarm output at alarm panel
The QoS alarms for link congestion and for routing data error, produced by the first and
interval measurement CR SIGFAIME, are additionally written in the alarm panel of the
alarm surveillance.
5.9.1
Monitored events
The same counters as for signaling link measurement and signaling point measurement
are used here.
5.9.1.1

Object class: signallingLinkCongestionData (QualityOfServiceAlarm)
Separate counters for ITU-T networks and for ANSI networks are implemented for first
and interval measurement. For each network type only the appropriate counter data are
monitored in each case.
ITU networks
slCongestedDuration (ITU-T Q.752/3.7)
The counter records the overload duration (in seconds) of a signaling link. The individual
blocking durations are added within the measurement time period. The counter is reincremented for each measurement time period.
slCongestedStarts (ITU-T Q.752/3.6 and also 3.8/Q.704)
A30828-X1176-G452-2-7618
35
Information
SURPASS hiS 700
Number of times a link is unavailable during a measurement time period. In case of narrowband links, the measured values are determined by layer 2 message management
and in case of high-speed links (SAAL) by layer 3 network management.
ANSI networks
slCongestionIndication-1
Sum of all events which lead to link status congestion level1, i.e. the threshold Onset
5.9.1.2

Object class: signallingPointData (QualityOfServiceAlarm)
discardedMSUs (ITU-T Q.752/5.5)
Number of discarded MSUs per link because of routing errors.
5.10
SCCP measurement network-independent,

network-dependent
These measurements register SCCP events which are exchanged during normal system operation. These are signaling messages or information between digital network
nodes, mobile network nodes or service control points of the intelligent network on the
basis of SS7. The data provides information about the sequence, the occurrence of errors and the performance of the SCCP. The data is also used for dimensioning purposes.
The network-independent and network-dependent SCCP measurement can be created
for the following measurement types:
This measurement records errors in the signaling traffic such as routing errors,
blocking or errors because of the unavailability of certain components.
SCCP quality of service
The SCCP quality of service measurement gives information about the quality of
service of the SS7 traffic on SCCP basis.
SCCP utilization
This measurement records the general SCCP traffic data
The measurement time period is 15 minutes for all the measurement types.
The SCCP measured values, can be summarized both per SS7 network and networkindependent for all the SS7 networks. Two Q3 tasks sets are provided for these two
measurement types.
36
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
Basic principles for SCCP measurements and monitoring

The SCCP (signaling connection control part) is a user part of signaling system No.7
(SS7). It is used for extending the MTP function and sending signaling information without using speech channels. The routing label only consists of OPC, DPC and SLS; there
is no CIC. A logical (virtual) signaling connection (= transaction) between two network
nodes is always packet-switched. Although the speech channels are not busy, the connecting partners occupy both physical and logical resources.
The SCCP offers different transaction control possibilities. If the SCCP controls the
transactions, this is called connection-oriented services. If the SCCP only has a carrier
function and the transactions are controlled by the TCAP (transaction capabilities application part), this is called connection less services.
Connection-oriented means that first of all a virtual signaling connection is created between the services (users) involved. It corresponds to an END-to-END connection. The
users determine the setup and release of the connection. The messages contain a connection reference parameter by means of which they can be allocated to a specific virtual connection.
Connectionless means that users in various network nodes can exchange data with one
another without having to create a connection reference beforehand. The messages do
not have a connection reference parameter.
A more detailed subdivision of the applications or the functional scope is achieved by
introducing protocol classes. ITU-T defines four protocol classes (0,...,3).
Protocol classes 0 and 1 comprise the connection less services and protocol classes 2
and 3 the connection-oriented services.
The connection less services of protocol classes 0 and 1 use five SCCP messages:
Unitdata (UDT), Long Unitdata (LUDT)
Message UDT is used for the connection less sending of an entire message
Extended Unitdata" (XUDT)
Unitdata Service (UDTS)
Extended Unitdata Service (XUDTS)
The unitdata service messages (UDTS and XUDTS) are used to return a message
to the sender which could not be delivered to the receiver. They, inter alia, also contain the reason for rejection
An UDT is rerouted with UDTS, an XUDT with XUDTS and an LUDT with LUDTS.
The following messages exist for the connection-oriented services of protocol class 2
Connect Request (CR)
Connect Confirm (CC)
Connect Refused (CREF),
Data Form 1 (DT1)
Released (RLSD)
Release Complete (RLC)
Data Form 2 (DT2)
Data Acknowledgement (AK)
Reset Request (RSR)
Reset Confirm (RSC)
The SCCP transaction is set up when the initiating side sends the Connect Request
(CR) message to the opposite side. If the signaling connection cannot be set up for
some or other reason, the Connect Refused (CREF) message will be returned. If the
opposite side receives the CR, the Connect Confirm (CC) message will be returned.
A30828-X1176-G452-2-7618
37
Information
SURPASS hiS 700
In this way the two sides are informed and the SCCP transaction is set up. Both sides
can exchange user messages as long as the SCCP transaction exists. This takes place
with the SCCP message Data Form 1.
If one of the two partners wishes to release the SCCP transaction, the Released
(RLSD) message must be sent to the opposite side. The opposite side then answers
with Released Complete (RLC).
User messages can also already be transmitted while the transaction is being set up (in
CR and/or CC) and still while it is being released (in RLSD).
5.10.1
SCCP error performance measurement

Object class: sccpErrorPerformance
This measurement records errors in the signaling traffic such as routing errors, overload
situations or errors because of the unavailability of certain components.
5.10.1.1
Measured values
segmentationFailed
Segmentation error - Segmentation failed, event 7.20, Tab 7/ITU-T Rec. Q752
segmentationNotSupported
Segmentation error - Segmentation not supported, event 7.19, Tab 7/ITU-T Rec. Q752
providerInitiatedRelease
Provider-initiated release of the connection.
The connection is released because
an inactivity timer cannot be set
internal resources are unavailable
there is an audit error
there is a backup error
for an external connection, event 7.18, Tab. 7/ITU-T Rec. Q752
tiarExpiry
Error during inactivity check because
the inactivity receive timer expires
the data in the received inactivity timer (IT) message does not correspond to the locally stored data;
for external messages, event 7.16, Tab. 7/ITU-T Rec. Q752
noReassemblyResources
Reassembly error - No resources for reassembly, event 7.12, Tab 7/ITU-T Rec. Q752
reassemblyTimerExpired
Timer for segmentation feedback expired (for external XUDT and DT1 messages),
event 7.10, Tab. 7/ITU-T Rec. Q752
reassemblyFailed
Reassembly error - Reassembly failed, event 7.21, Tab 7/ITU-T Rec. Q752
unknownDestinationAddress
Unknown destination address ITU-T Rec. Q714/3.2
38
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
providerInitiatedReset
A connection is reset by the provider, event 7.17, Tab 7/ITU-T Rec. Q752
violationOfHopCounter
Hop counter violation, event 7.13 Tab. 7/ITU-T Rec. Q.752
messageTooLarge
Message too large for segmentation, event 7.14, Tab 7/ITU-T Rec. Q752
subsystemCongestion
Routing error - SCCP subsystem blocking, event 7.6, Tab7/ITU-T Rec. Q752
failReleaseComplete
Failure of RELEASE COMPLETE monitoring; the interval timer expires, i.e. no RELEASE COMPLETE message is received;
for external messages, event 7.15, Tab. 7/ITU-T Rec. Q752
noPointCodeAvailable
SPC unavailable (identified by the SPC status check); event 7.3; Tab. 7/ITU-T Rec.
Q752
noTranslForSpecificAddress
Routing error; no translation for this specific address; event 7.2, Tab. 7/ITU-T Rec. Q752
Global title translation fails because there is no translation for the specified global title
digits
networkCongestion
SPC overloaded (identified by the SPC status check); event 7.4, Tab. 7/ITU-T Rec.
Q752
subsystemFailure
Routing error; subsystem unavailable; event 7.5, Tab. 7/ITU-T Rec. Q752, external
messages (CR, UDT, XUDT, UDTS or XUDTS) cannot be sent because the subsystem
is unavailable;
userUnequipped
Routing error; subsystem not provided in advance; event 7.7, Tab. 7/ITU-T Rec. Q752,
external messages (CR, UDT, XUDT, UDTS or XUDTS) cannot be sent because the
subsystem has not been created;
sccpSyntaxErrorList
Syntax error in incoming external messages identified; event 7.8, Tab. 7/ITU-T Rec.
Q752
unknownOrUnqualifiedRoutingFailure
Unknown routing error, ITU-T Rec. event 7.9, Tab. 7/ITU-T Rec. Q752.
segmentReceivedOutOfSequence
Reassembly error - received segment not in sequence
(including duplicates, receipt of other than first segment for which no reassembly process is available)
Event 7.11, Tab 7/ITU-T Rec. Q752
noTranslForNatureAddress
A30828-X1176-G452-2-7618
39
Information
SURPASS hiS 700
Routing error; no translation for this address because of unknown address type, event
7.1, Tab. 7/ITU-T Rec. Q752
5.10.2
SCCP quality of service measurement

Object class: sccpQualityOfService
This measurement comprises the counters on the network layer according to Tab. 9
ITU-T Rec. Q752. These counters are at the same time also used for traffic monitoring
(first and interval measurement). The measurement is a quality of service measurement.
5.10.2.1
Measured values
ludtsMessagesReceived
Long UNITDATA SERVICE message received, event 9 to 20, Tab 9 to/ITU-T Rec. Q752
errMessagesReceived
PROTOCOL-DATA-UNIT-ERROR messages received from the MTP; event 9 to 12,
Tab. 9 to/table 9 ITU-T Rec. Q752
xudtsMessagesSent
All outgoing externally sent EXTENDED UNITDATA SERVICE (XUDTS) messages,
event 9 to 14, Tab. 9 to/ITU-T Rec. Q752
ludtsMessagesSent
Long UNITDATA SERVICE message sent
Event 9 to 18, Tab 9 to/ITU-T Rec. Q752
rsrMessagesSent
All the sent reset request messages
Event 9 to 9, Tab. 9 to/ITU-T Rec. Q752
ludtMessagesSent
Long UNITDATA message sent event 9 to 17, Tab 9 to/ITU-T Rec. Q752
udtsMessagesReceived
Received UNITDATA SERVICE messages; event 9 to 4, Tab 9 to/ITU-T Rec. Q752
udtMessagesReceived
Received UNITDATA messages; event 9 to 1, Tab. 9 to/ITU-T Rec. Q752
crMessagesReceived
Connection request (CR) messages received from MTP plus ISDN-UP embedded CR
messages; event 9 to 7, Tab. 9 to/ITU-T Rec. Q752
crMessagesSent
Connection request message sent to the MTP (message transfer part) plus ISDN-UP
embedded CR messages; event 9 to 5, Tab. 9 to/ITU-T Rec. Q752, all outgoing external
CR messages
xudtMessagesReceived
All the received EXTENDED UNIT-DATA (XUDT) messages including the messages
with syntax/protocol and addressing errors; event 9 to 15, Tab. 9 to/ITU-T Rec. Q752
crefMessagesReceived
40
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
All the connection refused (CREF) messages received from the MTP; event 9 to 8, Tab.
9 to/ITU-T Rec. Q752
udtMessagesSent
Sent UNITDATA messages; event 9 to 1, Tab. 9 to/ITU-T Rec. Q752,
xudtsMessagesReceived
All the received EXTENDED UNIT-DATA-SERVICE (XUDTS) messages including the
messages with syntax/protocol and addressing errors; event 9 to 16, Tab. 9 to/ITU-T
Rec. Q752
errMessagesSent
All outgoing externally sent PROTOCOL-DATA-UNIT-ERROR messages; event 9 to
11, Tab. 9 to/ITU-T Rec. Q752
rsrMessagesReceived
All the reset request (RSR) messages received from the MTP; event 9 to 10, Tab. 9/ITUT Rec. Q752
ludtMessagesReceived
Long UNITDATA message received
Event 9 to 19, Tab 9 to/ITU-T Rec. Q752
crefMessagesSent
Sent connection refused messages
Event 9 to 6, Tab. 9 to/ITU-T Rec. Q752
xudtMessagesSent
All outgoing externally sent EXTENDED UNITDATA (XUDT) messages, event 9 to 13,
Tab. 9 to/ITU-T Rec. Q752
udtsMessagesSent
Sent UNITDATA SERVICE MESSAGES event 9 to 2, Tab. 9 to/ITU-T Rec. Q752
5.10.3
SCCP utilization measurement

Object class: sccpUtilization
This measurement records SCCP utilization data according to table 9 (9.3 to 9.5) ITU-T
Req. Q752.
5.10.3.1
Measured values
messagesHandled
Totality of the externally processed messages (from local or remote systems); event 9.3,
Tab. 9/ITU-T Rec. Q752, all incoming and outgoing external SCCP messages
messagesRequiringGTTranslation
All the messages requiring global title translations; event 9.5, Tab. 9/ITU-T Rec. Q752
The number of messages depends on whether or not the global title could be translated.
This counter is only required for SCCP network nodes with global title translation.
messagesForLocalSubsystems
Totality of the messages intended for local subsystems; event 9.4, Tab. 9/ITU-T Rec.
Q752
A30828-X1176-G452-2-7618
41
Information
SURPASS hiS 700
numberOfTransitMessagesProcessed
Number of processed transit messages (see draft recommendations for ETSI OMAP
Q752/9: agreed at 10/1997).
5.11
SCCP measurement per SSN

Object class: sccpUtilizationPerSsn
The SCCP measurement per SSN comprises the counters per subsystem according to
Tab. 9 ITU-T Rec. Q752.
5.11.1
Measured values
dt2MessagesToSinkSSN
All incoming externally received DATA2 (DT2) messages from the MTP to the subsystem; event 9.11, Tab. 9/ITU-T Rec. Q752
messagesOriginatedPerSsnSpcCl0
All externally sent UDT/XUDT messages (for connection less only (without virtual signaling connection)) of class 0 from the subsystem to an MTP service access point; event
9.6, Tab. 9/ITU-T Rec. Q752
dt1MessagesToSinkSSN
All incoming externally received DATA1 (DT1) messages from the MTP to the subsystem; event 9.9, Tab. 9/ITU-T Rec. Q752
messagesToBackupSsn
Number of messages which were sent to a backup subsystem, event 9.8, Tab 9/ITU-T
Rec. Q752
messagesReceivedOrTerminatedPerSsnSpcCl1
Totality of the externally received UDT/XUDT messages (for connection less (without
virtual signaling connection)) of class 1 to the subsystem; event 9.7, Tab. 9/ITU-T Rec.
Q752, not for transfer messages
messagesReceivedOrTerminatedPerSsnSpcCl0
Totality of the externally sent UDT/XUDT messages (for connection less only (without
virtual signaling connection)) of class 0 from the subsystem; event 9.6, Tab. 9/ITU-T
Rec. Q752, not for transfer messages
messagesOriginatedPerSsnSpcCl1
Totality of the externally sent UDT/XUDT messages (for connection less only (without
virtual signaling connection)) of class 1 from the subsystem; event 9.6, Tab. 9/ITU-T
Rec. Q752, not for transfer messages
dt1MessagesFromSourceSSN
All outgoing externally sent DATA1 (DT1) messages to the MTP from the subsystem;
edMessagesToSinkSSN
Quick data messages received from the MTP per sink SSN
event 9.14, Tab 9/ITU-T Rec. Q752
edMessagesFromSourceSSN
42
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
Quick data messages sent from the MTP per source SSN
event 9.13, Tab 9/ITU-T Rec. Q752
dt2MessagesFromSourceSSN
All outgoing externally sent DATA2 (DT2) messages from the MTP per source SSN;
5.12
SCCP first and interval measurement

Object class: sccpErrorPerformance (QualityOfServiceAlarm)
The SCCP first and interval measurement is a traffic monitoring which monitors routing
errors, blocking or errors because of the unavailability of certain components.
The SCCP first and interval measurement can be started network-independent and network-dependent for the measurement type error performance measurement.
The measurement time period is 5 minutes.
The network-dependent and network-independent measurements generate two reports
each:
Alarm report for the first occurrence of an event
Interval report
Alarm report
A quality of service (QoS) alarm report is generated if one of these events reaches the
1 threshold value. That is, an alarm report is generated if the monitored event occurs
for the first time in the measurement time period.
The alarm report contains both the event and further information, e.g. information about
the priority of the alarm and the SCCP address of the calling and the called side.
A complete listing of the output data you can find in the document PDC 2.2/2.3 Description of Postprocessing Format for SSNC Files. The output field USER CODE is only
provided for Siemens internal use. The user code represents an internal error code
which can be used by development to identify the error uniquely.
Interval report
5.12.1
Monitored events
The event counters specified below are available for SCCP monitoring. They are the
same counters as for the SCCP error performance measurement type in SCCP measurement. All the events recorded with these counters can be monitored.
The counters are described in detail in Section 5.10.1.
segmentationFailed
segmentationNotSupported
providerInitiatedRelease
tiarExpiry
A30828-X1176-G452-2-7618
43
Information
SURPASS hiS 700
noReassemblyResources
reassemblyTimerExpired
reassemblyFailed
unknownDestinationAddress
providerInitiatedReset
violationOfHopCounter
messageTooLarge
sccpCongestion
failReleaseComplete
noPointCodeAvailable
noTranslForSpecificAddress
networkCongestion
subsystemFailure
userUnequipped
sccpSyntaxErrorList
unknownOrUnqualifiedRoutingFailure
segmentReceivedOutOfSequence
noTranslForNatureAddress
5.13
Enhanced SCCP screening measurement

The SS7 Screening feature ensures that only authorized signaling traffic is forwarded.
Unauthorized traffic is rejected and can be registered.
Enhanced SCCP screening is based on Bellcore GR-82-Core Generic Requirements.
Enhanced SCCP screening can be applied for each global title translation (GTT), which
is executed for a message received from an adjacent operator, i.e. enhanced SCCP
screening function screens the SCCP traffic, requiring global title translations (GTT), received from one originating point code (OPC) or group of OPCs. The SCCP screening
function screens also the traffic allocated directly to an SCCP user. Additionally, SCCP
management user data screening is implemented.
The screening measurement can be created for the following measurement objects:
SCCP screening failures
SCCP screening traffic measurement
5.13.1
SCCP screening failures

Object class: sccpScreeningFailures
5.13.1.1
Measured values
failedGtTransNoRuleForSpecAddress
This counter records the number of global title translations that cannot be performed on
messages received from the interconnecting operator because no rule can be selected
matching the global digits. This counter is the representative of the GR-82-CORE
C.6.1.C measurement.
44
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
disallowedCdpaAfterTranslation
The called party address resulting from global title translation is screened for a valid
routing indicator/signaling point/subsystem number combination. If the routing indicator
and/or SPC and/or SSN of the called party address after global title translation is not allowed for messages received from the interconnecting operator, the counter is incremented. This counter is the representative of the GR-82-CORE C.6.3.13.
disallowedSSTMessages
For SCCP management data screening, incoming SCCP management messages (subsystem status allowed (SSA)/subsystem status prohibited (SSP)/subsystem status test
(SST)/SCCP/subsystem congested (SSC)) can be screened for a valid format identifier/signaling point/subsystem number combination. The counter records invalid affected
point code and/or affected subsystem number in subsystem-status-test messages (SCCP management messages) received from the interconnecting operator.
This counter is the representative of the GR-82-CORE C.6.3.11 measurement.
disallowedSSCMessage
point code and/or affected subsystem number in subsystem-status-congestion messages (SCCP management messages) received from the interconnecting operator.
failedGtTransNoAddressOfSuchNature
Number of global title translations that cannot be performed on messages received from
the interconnecting operator because there is no translation table for this translator. This
counter is the representative of the GR-82-CORE C.6.1.B measurement.
disallowedCdpaDig
The called party address of the incoming message is screened for a valid digit combination. If the global title digits of the called party address are not allowed for messages
received from the interconnecting operator, the counter is incremented.
disallowedCdpaTranslator
The called party address of the incoming message is screened for a valid translator selector, i.e.translation type (TT), numbering plan (NP) and nature of address indicator
(NAI). If the translator information (TTN/NP/NA) of the called party address is not allowed for messages received from the interconnecting operator, the counter is incremented. This counter is the representative of the GR-82-CORE C.6.3.14 measurement.
disallowedCdpa
The called party address of the incoming message is screened for a valid routing indicator/signaling point/subsystem number combination. If the routing indicator and/or
SPC and/or the subsystem of the called party address is not allowed for messages received from the interconnecting operator, the counter is incremented. This counter is the
representative of the GR-82-CORE C.6.3.12 measurement.
disallowedCgpaTranslator
The calling party address of the incoming message is screened for a valid translator selector, i.e. translation type (TT), numbering plan (NP) and nature of address indicator
(NAI). If the translator information (TTN/NP/NA) of the calling party address is not al-
A30828-X1176-G452-2-7618
45
Information
SURPASS hiS 700
lowed for messages received from the interconnecting operator, the counter is incremented.
disallowedCgpa
The calling party address of the incoming message is screened for a valid routing indicator/signaling point/subsystem number combination. The counter records the number
of messages rejected because the routing indicator and/or signaling point and/or subsystem number of the calling party is not allowed. This counter is the representative of
the GR-82-CORE C.6.3.9 measurement.
disallowedSSAMessages
point code and/or affected subsystem number in subsystem-allowed messages (SCCP
management messages) received from the interconnecting operator. This counter is the
representative of the GR-82-CORE C.6.3.10 (b) measurement.
disallowedScreeningDomain
This counter records the number of Level 3 MTP sap addresses which are not allowed
for messages received from the interconnecting operator.
disallowedSSPMessages
point code and/or affected subsystem number in subsystem-prohibited messages (SCMG messages) received from the interconnecting operator. This counter is the representative of the GR-82-CORE C.6.3.10 (a) measurement.
disallowedMsgType
This counter records the number of messages whose message type is not allowed for
messages received from the interconnecting operator.
disallowedCgpaDig
The calling party address of the incoming message is screened for a valid digit combination. If the global title digits of the calling party address are not allowed for messages
received from the interconnecting operator, the counter is incremented
disallowedOperationContext
The application information of the user data is not allowed for messages received from
the interconnecting operator.
5.13.2
SCCP screening traffic measurement

Object class: sccpScreeningTrafficMeas
5.13.2.1
Measured Values
nrOfGtTranslationsToOrigDomain
46
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
This counter records the number of global title translations performed that result in a
DPC belonging to the original operator. The counter is the representative of the GR-82CORE C.6.1.D measurement.
nrOfGtTranslations
This counter records the number of global translation performed messages received
from the interconnecting operator. The counter is the representative of the GR-82CORE C.6.1.A measurement.
nrOfSSAMessagesReceived
This counter records the number of subsystem-allowed messages (SCMG messages)
received from the interconnecting operator.
The counter is the representative of the GR-82-CORE C.6.2.O (a) measurement.
nrOfSSCMessagesReceived
This counter records the number of subsystem-status-congestion messages (SCMG
messages) received from the interconnecting operator.
nrOfSSPMessagesReceived
This counter records the number of subsystem-prohibited messages (SCMG messages) received from the interconnecting operator.
The counter is the representative of the GR-82-CORE C.6.2.N (a) measurement.
nrOfSSTMessagesReceived
This counter records the number of subsystem-status-test messages (SCMG messages) received from the interconnecting operator.
The counter is the representative of the GR-82-CORE C.6.2.P (a) measurement.
5.14
Enhanced SCCP screening first and interval measurement

Object class: sccpScreeningFailures
The enhanced Screening first and interval measurement is a traffic monitoring which
monitors the SCCP screening failures. A QoS alarm report is generated by traffic monitoring whenever the value of one of the monitored parameters in a network element
reaches the predefined threshold.
Screening first and interval measurement can be started for the measurement object
SCCP screening failure.
Two reports are generated for first and interval measurement:
Alarm report
Interval report
The measurement time period is 5 minutes for the first and interval measurement.
Alarm report
A quality of service (QoS) alarm report is generated if one of these events reaches the
1 threshold value. That is, an alarm report is generated if the monitored event occurs
for the first time in the measurement time period.
The alarm report contains both the event and further information. A complete listing of
the output data you can find in the document PDC 2.2/2.3 Description of Postprocessing Format for SSNC Files. The output field USER CODE is only provided for Siemens
A30828-X1176-G452-2-7618
47
Information
SURPASS hiS 700
internal use. The user code represents an internal error code which can be used by development to identify the error uniquely.
Interval report
5.14.1
Monitored events
The event counters specified below are available for SCCP screening monitoring. They
are the same counters as for the SCCP screening failures measurement in SCCP
screening measurement. All the events recorded with these counters can be monitored.
The counters are described in detail in Section 5.13.1.
FailedGtTransNoAddressOfSuchNature
disallowedCdpaAfterTranslation
disallowedSSTmessages
disallowedSSCmessages
failedGtTransNoAddressOfSuchNature
disallowedCdpaDig
disallowedCdpaTranslator
disallowedCdpa
disallowedCgpaTranslator
disallowedCgpa
disallowedSSAMessages
disallowedScreeningDomain
disallowedSSPMessages
disallowedMsgType
disallowedCgpaDig
disallowedOperationContext
5.15
SCCP measurement all

With this task, all the SCCP and SCCP screening measurements and first and interval
measurements explained above can be set up.
5.16

Object class: atmTrafficLoadCurrentDataExt
The ATM (asynchronous transfer mode) cell measurement CR VCHANME (virtual channel measurement) records the load on high speed signaling links (HSLs). It records the
number of transmitted cells on HSL Links on a virtual channel connection-related basis.
48
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
The measurement is implemented for the line interface cards (LIC) of the SSNC.
5.16.1
Measured values
pcr
This counter (peak cell rate) is only provided for AAL 2 links. It records the maximum
possible number of cells, which can be transmitted per virtual channel.
incoming cells
The counter records the total number of incoming cells with a valid header per virtual
channel.
outgoing cells
The counter records the total number of outgoing cells with a valid header per virtual
channel.
A30828-X1176-G452-2-7618
49
Information
SURPASS hiS 700
6 Number portability ticket measurement

The feature Number Portability (NP) allows subscribers to keep their directory number
when they change to another network carrier or when they move within the same local
area. The routing and signaling informations for ported numbers are stored at NP server
on MP:NP (main processor: number portability) and MP:SLT (main processor: signaling
link termination).
The NP ticket measurement supplies statistical data about the usage of the NP server.
The measurement records server accesses for bearer related applications (BRA), e.g.
for INAP, MAP, CAP and/or for SCCP applications, in data records on the MP hard disk.
Unlike traffic measurement, which produces traffic data per counter, NP ticket measurement uses data records. The data is recorded for individual accesses to the NP server
and collected per access in a data record. The data records are also called tickets. The
measurement uses a random sample method whereby a data record is only registered
for every n-th (n - trace factor) time the NP server is accessed. The value of the trace
factor (Target trace factor) can be between 0 and 65535. The recommended value is
5000.
The tickets are registered on the MP hard disk in SAM (sequential access method) file
arrays.
Administration
You create the NP ticket measurement with the task CR NPTME. Before starting the NP
ticket measurement, use the task CR SAMAR to create the SAM (sequential access
method) file array (file prefix NP) on the MP system disk. You can also start the NP ticket
measurement by the help of the NetManager application Number Portability.
Output of the NP tickets
The measured values are stored in binary format in the SAM file array (prefix NP) on
the MP hard disk. The SAM file array can be transferred directly with FTP via TCP/IP to
a post-processing computer. The transferred files are in binary format.
6.1
Output data (NPTM data record)

The NPTM (number portability ticket measurement) data record contains the data packages:
Data/time
Error code
New destination
Calling party number
Called party number
Trace factor
Number portability
Originating SPC (signaling point code)
Date/time
The data package contains the time and date of the NP query result.
Error code
In the sub package query result the following data are stored:
50
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
NP entry found
NP no entry found
NP collect more digits
NP no translator
NP inactive
NP success
NP internal error
NP external error
New destination
The packet contains the ported number, i.e the called party number after NP translation.
Informations about the ported number are recorded in the fields:
NADI (nature of address indicator)
NPI (numbering plan indicator)
This data package is only present, if NP translation was executed.
Calling party number
The package is only present in the data record, if the application SCCP or BRA makes
it available (only for special features like call completion on busy subscriber or for the
service ISDN).
This package contains the calling party number. Informations about the calling party
number are recorded in the fields:
Presentation indicator
This field is only present, if it is supplied by the application BRA.
Screening indicator
This field is only present, if it is supplied by the application BRA.
Called party number
The package contains the supposed ported number, i.e. the dialed destination party
number. Informations about the ported number are recorded in the fields:
Trace factor
The package contains the trace factor, which was specified by the operator in the measurement task.
Number portability
The package contains the specific application values for the correct interpretation of the
whole ticket. Only sub package Application type is always present.
The package number portability contains the sub packages
Translation type ID for calling party
Translation number for the calling party
Translation type ID for the called party
Translation type number for the called party
Subsystem number for the calling party address
Subsystem ID for calling party address
A30828-X1176-G452-2-7618
51
Information
SURPASS hiS 700
Subsystem number for called party address

Subsystem ID for called party address
Application type
Application context
Subsystem number for called party address
Subsystem ID for called party address
Originating SPC (signaling point code)

The package is only present in the data record, if the application SCCP or BRA makes
it available (only for special features like call completion on busy subscriber or for the
service ISDN).
The package contains the originating signaling point code.
52
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
7 SS7 traffic structure measurement

SS7 traffic structure measurement records the message signal units (MSU). This involves a random sampling measurement where every nth MSU (n = trace factor) is recorded in a data record. This statistically determined data can be post processed
accordingly. The operator thus receives information about the traffic flow in SS7 networks and can draw conclusions as to the quality and performance of the signaling traffic. The data also forms the basis for planning and dimensioning SS7 networks.
7.1
Sequence of SS7 traffic structure measurement

Traffic structure measurement records incoming, outgoing and transit message signal
units (MSU).
Administration
For the SS7 traffic structure measurement, two Q3 tasks are needed to record traffic data:
Task to create a file to which the measured values are to be written
The task creates 7 daily files on the hard disks of MP:SM. A separate file is allocated
to each day of the week.
Task to create traffic structure measurement
Up to 32 SS7 networks can be measured with a traffic structure measurement job.
Only one traffic structure measurement job can ever be active in the system. It follows that the same trace factor is used for all networks which are included in a measurement job.
Trace rate
So as to restrict the load on the system, data are only recorded for every n-th MSU in
the relevant signaling network.
The parameter has a value in the range n = 50...1 000000. The default value is
n = 100 000.
If the trace factor specified is too small, not all MSUs may be recorded. The number of
discarded MSUs per measurement period (15 minutes) is stored in the date/time modification data record (only for the octet9 data record format).
If more than 100,000 MSUs are not recorded in a 15-minute period for a platform, an
internal process ends the measurement so as to prevent additional barriers to the performance of the level 3 message handling function.
Output of measurement data in daily files
SS7 traffic structure data is recorded in daily files until the measurement is activated.
After seven days, the oldest of the seven daily files is overwritten without prior warning.
Should there already be a daily file when a measurement is activated for the corresponding day, a new file will not be created but the existing daily file will be used to record the
data and the existing data overwritten.
Transfer of traffic measurement files (daily files) to post processing computers
The daily files can be transferred to any postprocessing computer with FTP over
TCP/IP. By using FTP the TSM (traffic structure measurement) File Converter reads the
A30828-X1176-G452-2-7618
53
Information
SURPASS hiS 700
daily files and converts the binary format of the daily files to the ISO 7 Bit format (post
processing format).
Note: The transfer of the daily files is only possible if file names aren't changed. For files
at MP you have to add one \ (backslash) at the begin of the file name. If you work with
a UNIX system add two \\ (backslashes) at the begin of the file name.
7.2
Output data
Traffic structure data records and administration data records are output for SS7 traffic
structure measurement.
The following data record types are available:
SS7 traffic structure data record
Two formats can be selected:
octet6
This format corresponds to the known file format of SS7 traffic structure measurement for CCNC. The first 6 octets are recorded per MSU.
octet9
For this format, the first 9 octets are recorded per MSU.
Time modification data record
This data record contains, inter alia, the number of rejected MSUs per measurement
interval (only for data record format octet9)
Activation and deactivation data record
Recovery data record
Should there be a recovery, this event will be recorded in a recovery data record.
Output of the measured values for the octet6 format
Tab. 7.1 shows the data which is recorded for the octet6 output format per MSU.
Output
data
Designation
Explanation
LI
Length indicator
Actual number of
signaling information (SIF)
and
service information (SIO)
octets of MSU
SSF
Subservice field
SI
Service indicator *
Service information octet

(SIO)
DPC
Destination point code
OPC
Originating point code
SLS
Signaling link selection
H1
Message code for network management
Routing label
Heading code
H0
Tab. 7.1
SS7 traffic structure measurement data
* Explanation about the service indicator (SI)

0
54
Signaling network management message (SNM)
A30828-X1176-G452-2-7618
Information
SURPASS hiS 700
Signaling network testing and maintenance message (SNT& M)
Operation, maintenances and administration part (OMAP)
Signaling connection control part (SCCP)
Telephone user part (TUP)
ISDN user part (ISUP)
Data user part 1 (call and circuit related messages)
Data user part 2 (facility registration and cancellation messages)
8-12 Free
13
FuN C (in closed network)
14
Telephone user part (TUP) (modified TUP for INAT0)
Output of the measured values for the octet 9 format

For this format, the first 9 octets of each MSU are recorded.
For broadband MSUs, the measured values also contain the message type code
(1 byte) and the length of the MSU (2 bytes).
For narrow band MSUs, the message type code (1 byte) and two bytes of the parameter
field are also recorded.
Data evaluation
The following information can be derived from the measured data:
The message flow of transit traffic (STP), incoming and local originating traffic per
originating/destination pair
The average number of SIF and SIO octets
The number or percentage of MSU types sent in the message traffic
Statistical values for billing purposes
A30828-X1176-G452-2-7618
55

G 452

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

G 452

Hochgeladen von

Copyright:

Verfügbare Formate

Information

SURPASS hiS 700

Traffic Data Management - Counter Description

Important Notice on Product Safety

The same text in German:

Copyright (C) Siemens AG 2003-2004.

Traffic Data Management - Counter Description

Reason for Update

Details for first issue:

New IP counters for signaling network element

signaling linkset IP measurement

SCCP association measurement

New SCCP screening counter

Reason for Update

Adaptation for hiS 700 m

Traffic Data Management - Counter Description

Traffic Data Management - Counter Description

This document consists of a total of 55 pages. All pages are issue 2.

Overview of traffic data management jobs . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Counters for traffic data recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Main processor load measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SS7 traffic measurements and monitoring . . . . . . . . . . . . . . . . . . . . . . . . .

Traffic Data Management - Counter Description

Number portability ticket measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

SS7 traffic structure measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Traffic Data Management - Counter Description

Traffic data management

Aims of traffic data recording

Traffic Data Management - Counter Description

Traffic Data Management - Counter Description

2 Overview of traffic data management jobs

Name of measured object

MP load traffic measurement

Main processor (MP) load measurement

SS7 traffic measurements and monitoring

Signaling network element measurement

Signaling point measurement

Signaling link set measurement

Signaling linkset IP measurement

Signaling destination point measurement

Signaling link measurement

SCTP association measurement

MTP first and interval measurement

SCCP measurement, network-independent

SCCP measurement, network-dependent

SCCP measurement per SSN

SCCP measurement, all

SCCP first and interval measurement, network-independent

SCCP first and interval measurement, network-dependent

Enhanced SCCP screening measurement

Enhanced SCCP screening measurement, first and interval

ATM cell measurement for virtual channels

Overview of traffic data management tasks (create tasks)

Traffic Data Management - Counter Description

Name of measured object

Number portability ticket measurement

SS7 traffic structure measurement

SS7 traffic structure measurement (with start and stop time)

SS7 traffic structure measurement (with start and stop time

SS7 traffic structure measurement (with start and stop time

Overview of traffic data management tasks (create tasks)

Traffic Data Management - Counter Description