pdn 98904742
Post on 03-Jun-2018
231 Views
Preview:
TRANSCRIPT
-
8/12/2019 Pdn 98904742
1/47
Serve atOnce Traffica Traffica
Z5.2
Traffica Principles
DN98904742
Issue 6-0
-
8/12/2019 Pdn 98904742
2/47
2 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805806352e0
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-
TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-
RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED
TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY
OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION
IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2010/9/9. All rights reserved
f Important Notice on Product SafetyElevated 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 Span-
nung. Einige Teile knnen auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverlet-
zungen 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.
-
8/12/2019 Pdn 98904742
3/47
DN98904742
Issue 6-0
3
Traffica Principles
Id:0900d805806352e0
Table of ContentsThis document has 47 pages.
1 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Where to find more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3 Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2 Change information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3 Introduction to Traffica. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1 Traffica applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2 Benefits for user groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4 Traffica architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.1 Traffica components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164.1.1 Traffica Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.1.2 Traffica CCMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.1.3 RTT Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.1.4 NtAlfo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.1.5 Traffic News Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.1.6 Traffic Views Server (optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.1.7 Traffica Database Export Server (optional) . . . . . . . . . . . . . . . . . . . . . . 18
4.1.8 Traffica Configuration and User Server . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.1.9 Traffica Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.1.10 Measurement Server (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.1.11 Traffica File Transfer Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.2 Traffica applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.2.1 Traffic News Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.2.2 Traffic Views Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.2.3 Database Export Admin Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.2.4 Traffic Simulator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.2.5 Summary Report Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.2.6 RTT Server GUI functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.2.7 Traffica Admin Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.2.8 KPI Export Config Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.3 Connections between Traffica components and applications . . . . . . . . 21
4.4 Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.4.1 KPI Export interface to Service Quality Manager. . . . . . . . . . . . . . . . . . 23
4.4.2 Interface to NetAct Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.4.3 Interface to SNMP Managers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.4.4 Interface to NTMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5 Traffica functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1 Traffica basic functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1.1 Data collecting and storing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1.2 Clear Code Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.1.3 Real-time graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.1.4 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
-
8/12/2019 Pdn 98904742
4/47
4 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805806352e0
5.2 Traffic News . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.3 Traffic Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.4 Summary Report Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.5 Traffica Database Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365.6 Traffic Simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.7 Traffica at Customer Care. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6 Using TNESs remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.1 Receiving data from TNESs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.1.1 Remote graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.1.2 Redirecting RTT reports to the TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.2 Forwarding alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.3 Managing TNESs remotely. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
7 Using Traffica for real-time monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . 41
7.1 Customising real-time monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427.1.1 Defining new counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
7.1.2 Defining new graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
7.1.3 Creating a new graph based on a predefined graph. . . . . . . . . . . . . . . . 44
7.1.4 Defining new alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
8 Using Traffica for data analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
-
8/12/2019 Pdn 98904742
5/47
DN98904742
Issue 6-0
5
Traffica Principles
Id:0900d805806352e0
List of FiguresFigure 1 Traffica architecture, basic solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 2 Traffica architecture, dual level solution. . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 3 Traffica components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 4 Interfaces from Traffica . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 5 Data flow in Traffica . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 6 Different CCMA members and their icons . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 7 An example of the Clear Code Matrix. . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 8 An example of linked graphs. A cell is selected in the upper graph and the
clear codes of the cell are displayed in the lower graph. . . . . . . . . . . . . 31
Figure 9 Limit alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 10 Delta threshold alarm (the threshold is positive in this example). . . . . . 32
Figure 11 Burst alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 12 Traffic Simulator architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Figure 13 Graph definitions hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
-
8/12/2019 Pdn 98904742
6/47
6 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805806352e0
List of TablesTable 1 Traffica terms and concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Table 2 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 3 Traffica components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Table 4 Traffica applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Table 5 Differences between the Traffic News java client and the Traffic News web
client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
-
8/12/2019 Pdn 98904742
7/47
DN98904742
Issue 6-0
7
Traffica Principles About this document
Id:0900d805807719ba
1 About this documentTraffica Principles is a document for the operating personnel using Traffica. It includes
information about the Traffica architecture, features related to Traffica, and the operat-
ing principles of Traffica. It also describes how Traffica can be used for the real-time
monitoring and analysis of traffic data.
All information in this document relates to Traffica release Z5.2
1.1 Where to find more information
For instructions on how to use Traffica, Summary Report Tool, Traffic News, Traffic
Views, Traffica Admin Tool, and Traffic Simulator, see the online help of the application
in question.
If you are unfamiliar with any of the terms used in this document, refer to Glossary.
Traffica general information
For further information on Traffica, refer to:
Administering Traffica
For more information on the Traffica alarm interface, refer to:
Multivendor FM Integration Principles(in NetAct documentation)
Traffica for GPRS Networks
For further information on Traffica, refer to:
Traffica Reference Guide for 2G SGSN Direct Interface
Traffica Reference Guide for 3G SGSN Direct Interface Traffica Reference Guide for 2G/3G Packet Core Probes
Traffica for 2G/3G Circuit Switched Networks
For further information on Traffica, refer to:
Traffica Reference Guide for 2G/3G Mobile Circuit Switched Core
Traffica Reference Guide for 2G Circuit Switched Probes
A significant part of Traffica functionality is based on clear codes. For detailed clear code
descriptions, refer to:
M14 Clear Code List
Interpreting MSC Clear Codes
For more information on the RPC interface, refer to:
Multivendor FM Integration Principles, (in NetAct documentation)
Traffica for Fixed Networks
For further information on Traffica, refer to:
Traffica Reference Guide for Fixed Circuit Switched Core
A significant part of Traffica functionality is based on clear codes. For detailed clear code
descriptions, refer to:
DX200 Clear Code List
For detailed descriptions of the data in the CDR, refer to:
http://general_glossary.pdf/http://pdn98904754.pdf/http://pdn05148836.pdf/http://pdn05148875.pdf/http://pdn0687206.pdf/http://pdn98904766.pdf/http://pdn0660224.pdf/http://pdn70447835.pdf/http://pdn99576987.pdf/http://pdn078927.pdf/http://pdn078927.pdf/http://pdn99576987.pdf/http://pdn70447835.pdf/http://pdn0660224.pdf/http://pdn98904766.pdf/http://pdn0687206.pdf/http://pdn05148875.pdf/http://pdn05148836.pdf/http://pdn98904754.pdf/http://general_glossary.pdf/ -
8/12/2019 Pdn 98904742
8/47
8 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805807719ba
About this document
Data Formats of Charging; CDR
Traffica for PaCo and GPRS
For further information, refer to:
Traffica Reference Guide for 2G/3G Packet Core via Charging Gateway
Traffica for MSS, SIP, UMA
For further information, refer to:
Traffica Reference Guide for 2G/3G Mobile Circuit Switched Core
Traffica for RNC
For further information, refer to:
Traffica Reference Guide for RNC Direct Interface
1.2 Terms
The following table presents the most important Traffica terms and concepts. If a term
or a word does not appear in this section, see Glossary.
Concept Description
Basic solut ion In the Traffica basic solution, TS components run in the same TS but it is possible that TS com-
ponents are divided into several TSs in a certain site.
CCMA (Clear Code Matrix) A tree structure which consists of nodes and counters, and functions as a data storage for the
counter values post-processed from RTTs.
When an RTT arrives in Traffica, the CCMA is scanned through and the counters are updated.
For information on the CCMA, see chapter Clear Code Matrixand RTT Server Help.
For detailed information on the Predefined CCMA, refer to the relevant Traffica Reference
Guide.
CDR Call Detailed Record. Billing information.
CG Charging Gateway
Clear code Code that identifies the reason why a call ended.
Clear codes are divided into four categories:
0 - 3FF, Normal release
400 - 7FF, Internal error
800 - BFF, External error
C00 - FFF, Subscriber error
For detailed clear code descriptions, refer to Traffica Clear Code Helpand M14 Clear Code List.
CUL (Computer Unit Load)
report
Contains the processor loads of each computer unit in an MSC. A CUL report is sent to Traffica
once a minute.
CUS Traffica Configuration and User Server. TS SW component which is used to store Traffica's
configuration information.
Table 1 Traffica terms and concepts
http://pdn05148899.pdf/http://pdn98904766.pdf/http://pdn70395427.pdf/http://general_glossary.pdf/http://pdn70447835.pdf/http://pdn70447835.pdf/http://general_glossary.pdf/http://pdn70395427.pdf/http://pdn98904766.pdf/http://pdn05148899.pdf/ -
8/12/2019 Pdn 98904742
9/47
DN98904742
Issue 6-0
9
Traffica Principles About this document
Id:0900d805807719ba
Database A data storage for all RTTs in the TNES. The database is automatically cleaned up and oldest
data is deleted. Database capacity depends on the size of the hard disk and the volume of
network traffic.To access the database, use Traffic News.
For more information, see Managing databasesinAdministering Traffica.
Data source The origin of the information that Traffica receives. A data source is typically a network element.
When RTTs are redirected from a TNES to a TS, the TNES is a data source for the TS.
DBM Traffica Database Manager (DBM) takes care of Traffica databases. DBM is a service that runs
on TS and TNES.
Dual level solution In Traffica dual level solution, Traffica Tier 2 is divided into several physical sites and several
TSs.
DX cause The same as clear code.
Event Event that triggers off the sending of an RTT report to Traffica. An event can be a GSM call,SMS, GPRS attach, or GPRS PDP context activation, for example.
Field A field in RTT report, in IDS, or in database column in Traffica database.
Field set A Traffic News client term: a collection of fields which is shown to you at the same time in a
defined order.
FTS Traffica File Transfer Service. TNES SW component that provides automatic transferring of
files to a remote server.
IDS, Internal Data Structure Traffica forwards an RTT report as such into Trafficas IDS. Once the RTT report data is in the
IDS, the fields in the report are mapped with the corresponding IDS fields. Traffica uses the data
in the RTT reports, which are in the IDS, for updating the CCMA. Traffica stores the reports from
the IDS into the database. For more information on the IDS, refer to the relevant Traffica Ref-erence Guide.
IDS field An IDS field is mapped with a corresponding field in an RTT report. Consequently, the contents
of an IDS field are identical with the contents of an RTT report field.
Lower Traffica A Traffica that is lower in the hierarchy. A TNES is a lower Traffica for a TS.
Network Element (NE) A general term, used for all NEs that Traffica can be connected to, for example, Mobile Switch-
ing Centre (MSC), Fixed Switching Centre (FSC) or Serving GPRS Support Node (SGSN).
RTT (Real-time Traffic) report RTT reports is a general term used for the real-time traffic reports that are generated by NEs
and issued to the connected TNES. The term also includes redirected RTT reports that are
transferred from a TNES to a TS.An RTT report can contain, for example, the following information:
Call start and end time
Cause why the call ended
Clear code
A and B subscribers identities
Incoming and outgoing CGR, PCM and TSL
In the GSM networks, the RTT report contains also the mobile identities (IMEI), the dialled
digits, incoming and outgoing BSC, LAC, and the cell
RTT Server Software component which runs in every TNES and possibly in TS. Consists of Traffica.exe and
Solid database. Responsible for collecting, storing and analysing RTT reports.
Concept Description
Table 1 Traffica terms and concepts (Cont.)
http://pdn98904754.pdf/http://pdn98904754.pdf/ -
8/12/2019 Pdn 98904742
10/47
10 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805807719ba
About this document
SNMP Simple Network Management Protocol
Summary report Summary report is an extensive report that contains a vast number of analysed sections and
the data for the report is provided by RTT reports. For more information on the contents of asummary report, see Traffica Reference Guide for 2G/3G Mobile Circuit Switched Core.
Traffica for probes (TFP) Traffica for probes solution is based on the probe system, which captures signalling events in
real-time from different interfaces in 2G, GPRS, and 3G networks. Probes may also correlate
the data before it is passed to Traffica and shared among a variety of end users.
TCC Traffica at Customer Care
Time Class A root item in the CCMA tree structure that acts as a container of the time resolution(s) and
CCMA members.
Time resolution A time resolution gives meaning to a Time Class. A time resolution defines how long a time the
counters in that particular tree branch are accumulated before the counters are reset and how
many time slices are stored in the memory as history data.
When you define a time resolution you define two things: the duration of one time slice and the
number of these time slices. The duration of one time slice defines how long the data accumu-
lates and it can be, for example, one second, minute, or hour.
Time resolutions are user-definable, for example, 1*1 day or 30*1 minute.
A time resolution is a range of time slices, and for the user it is typically visualised as a range
of bars in a graph.
During the time defined in the t ime resolution, the counters in the current time slice are updated
in real-time. When the defined time for one time slice is over, the time slice is either stored as
historical data or deleted, and a new time slice is started.
Traffic News client A tool that can be used for database queries and can be installed into an office PC.
When the term Traffic News client is used, it refers to both the java and the web client. If there
are differences, it is mentioned separately.
Traffica Network Element
Server (TNES)
A TNES is the Traffica that is connected to an NE.
TNESs receive the RTT reports and these reports are stored into the Traffica database.
Traffica Server (TS) TS is a central point in the Traffica system, and is connected to all TNESs. It acts as a server
for Traffica clients.
Upper Traffica A Traff ica that is higher in the hierarchy. For example, a TS is an upper Traff ica for a TNES.
Workspace A workspace is a set of configuration files which define how the TNES/TS works. The configu-
ration files are read when Traffica is started (in other words, the workspace is opened). They
can be divided into*.conf
files, which are predefined by Nokia Siemens Networks and*.ini
files, which contain user specific information.
A workspace contains, for example, definitions for
predefined CCMA and graphs
user defined CCMA, graphs and alarms
RTT report structures and identification rules
database tables and indexes
Concept Description
Table 1 Traffica terms and concepts (Cont.)
http://pdn98904766.pdf/http://pdn98904766.pdf/ -
8/12/2019 Pdn 98904742
11/47
DN98904742
Issue 6-0
11
Traffica Principles About this document
Id:0900d805807719ba
1.3 Abbreviations
This section provides a brief list of Traffica specific abbreviations. If an abbreviation does
not appear in this section, see Glossary.
Abbreviation Explanation
AH Alarms function
CCMA Clear Code Matrix
CCMAH Clear Code Matrix function
CGR Circuit Group
CUL (report) Computer Unit Load (report)
CUS Configuration and User Server
DBBH Database Backup function
DBM Traffica Database Manager
DBH Database function
DME Data Mediation Engine
DRH Data Redirector function
FTH File Transfer function
FTS File Transfer Service
IDS Internal Data Structure
KPI Key Performance Indicator
MS Measurement Server
NTMS Nokia Siemens Networks Terminal Manage-
ment Server
PI Performance Indicator
RCH Remote Communications function
REDI Real-time Graphs function
RTT (report) Real-time Traffic (report)
TCC Traffica at Customer Care
TFP Traffica for probes
TNES Traffica Network Element Server
TS Traffica Server
Table 2 Abbreviations
http://general_glossary.pdf/http://general_glossary.pdf/ -
8/12/2019 Pdn 98904742
12/47
12 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805807719ba
Change information
2 Change informationThis chapter lists changes between releases in this document.
In Z5.2
You can now forward internal and threshold alarms using SNMP protocol. Alarms
can be forwarded to NetAct Monitor and SNMP Manager. For more information, see
section Interface to SNMP Managers. For configuration instructions, see Installation
Guide for Traffica release Z5.2.
You can now create Workflows in Traffic News Client. For more information, see
section Traffic News in this document and section Workflows in Traffic News Help.
In Z5
Traffica databases are now handled by Traffica Database Manager. For more infor-
mation, see Traffica database.
User management is now handled centrally. Traffica User Manager has been
removed, and the user management tasks that were previously handled with
Traffica User Manager are now done with Traffica Admin Tool. Traffica Admin Tool
also manages Traffic News user rights and configuration as well as RTT Server
application user rights. The information in this document regarding the administra-
tion of Traffic News has been updated accordingly. For more information, see
Managing Traffic NewsinAdministering Trafficaand Creating users and user
groupsin Traffica Admin Tool Help. For more information on RTT Server user man-
agement, see RTT Server Help.
Traffica Configuration and User Server (CUS) now handles all Traffica licensing
apart from RTT Server licenses. For more information, see chapter Traffica Config-
uration and User Server. Summary Report Tool is now part of the Traffica Client installation. For more infor-
mation, see Summary Report Tooland Installation Guide for Traffica release Z5.2
It is now possible to launch external applications from Traffic News Client. For more
information, see chapter Traffic Newsin this document and chapter Launching an
external toolin Traffic News Help.
Traffic News Java Client can now be launched with Java Web Start from Traffica
web pages. Section Traffic News Clienthas been updated accordingly.
http://pdn0171584.pdf/http://pdn98904754.pdf/http://pdn0432433.pdf/http://pdn0432433.pdf/http://pdn0171584.pdf/http://pdn0171584.pdf/http://pdn0171584.pdf/http://pdn0171584.pdf/http://pdn0432433.pdf/http://pdn0432433.pdf/http://pdn98904754.pdf/http://pdn0171584.pdf/ -
8/12/2019 Pdn 98904742
13/47
DN98904742
Issue 6-0
13
Traffica Principles Introduction to Traffica
Id:0900d805807719ba
3 Introduction to TrafficaTraffica is a real-time traffic monitoring tool, which is designed to facilitate the monitoring
and analysis of network traffic. Traffica allows you to see how the network functions from
the Network Element (NE) level down to individual subscriber information.
Traffica receives information from NEs and visualises it in real-time graphs. For visual-
ising the network traffic, Nokia Siemens Networks provides an extensive selection of
predefined real-time graphs. These graphs cover various situations in the network and
you can immediately see if there is congestion or other problems in the network. Real-
time graphs can also be tailored to meet the exact needs at the operators site. For more
information, see chapter Real-time graphs.
Traffica makes it possible for you to define your own alarms. Alarms can be forwarded
to NetAct Monitor where action can be taken. For more information on alarms, see
chapter Alarms.
3.1 Traffica applications
The following features are included in Traffica release Z5.
Real-time Traffic Server (RTT Server)
End users can use RTT Server for viewing real-time graphs and alarms. In addition, it
can be used for administering the Traffica system. RTT Server also implements server
functionalities. For more information, see chapter RTT Server.
Traffic News
Traffic News is designed for the offline analysis of traffic data.
Traffic News allows you to make queries in the database and define conditions for your
search. There are two features of Traffic News available: the standard Traffic News that
is available with Traffica, and the Traffic News client solution which is an optional
feature. For more information, see chapter Traffic News.
Traffic Views (optional)
Traffic Views is a client solution for viewing Traffica real-time graphs. It is an optional
feature. For more information, see chapter Traffic Views.
Summary Report Tool (optional, only for GSM adaptation)
Summary Report Tool is an optional client application for traffic data analysis. It allows
you to generate a comprehensive summary report of call and SMS traffic data. For moreinformation, see chapter Summary Report Tool.
Database Export (optional)
Database Export is a tool for exporting data from Traffica Database to external systems.
It is an optional feature. For more information, see chapter Traffica Database Export.
Traffic Simulator
Traffic Simulator is a tool for simulating network traffic with Traffica. For more informa-
tion, see chapter Traffic Simulator.
-
8/12/2019 Pdn 98904742
14/47
14 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805807719ba
Introduction to Traffica
Traffica at Customer Care (optional)
Traffica at Customer Care is a solution for operators' customer care personnel. For more
information, see Traffica at Customer Care.
Administration tools
The tools which are used for administering Traffica system are RTT Server, Traffica
Admin Tool, and KPI Export Config Tool. For more information, see the respective online
helps; RTT Server Helpand Traffica Admin Tool Help. For KPI Export Config Tool, see
chapterAdministering KPI ExportinAdministering Traffica.
3.2 Benefits for user groups
The technical personnel at the operators site can use Traffica for the following
tasks:
To observe the network behaviour using freely user-definable time resolutions. To observe the effects of the software change notes or parameter changes in real
time.
To verify that recently installed elements deliver traffic as expected.
To create alarms to indicate problems in traffic. For instructions, refer to RTT Server
Help.
Customer Care and Service and Business Management can use the data collected
by Traffica to analyse the following:
Subscriber behaviour. The average call duration, the destination of calls.
Competitors. The number and duration of the calls going to the competitors network
through your switches. Subscriber-specific information.
Roaming. The operators whose roamers are making calls in your network. The
success rate and duration of the calls.
Manufacturers. The mobile equipment used in the network. The performance of the
various manufacturers BSSs.
http://pdn98904754.pdf/http://pdn98904754.pdf/ -
8/12/2019 Pdn 98904742
15/47
DN98904742
Issue 6-0
15
Traffica Principles Traffica architecture
Id:0900d805807719ba
4 Traffica architectureThis chapter describes Traffica system architecture. The Traffica system consists of
three tiers. Every tier consists of a certain type of physical machines. Corresponding
tiers and physical machines are listed here:
Traffica Tier 1: Traffica Client
Traffica Tier 2: Traffica Server (TS)
Traffica Tier 3: Traffica Network Element Server (TNES)
Figure 1 Traffica architecture, basic solution
Traffica Tier 3 consists of TNESs which are connected to Network Elements (NE) or
probes. After a certain event has occurred in an NE, the NE or probes send Real-Time
Traffic Reports (RTT) to TNES. TNES stores and processes incoming RTTs in real time.
TNESs communicate with the TS.
TNESs can be unmanned and they can be remotely managed from the TS. Because of
high bandwidth and security requirements, TNESs are physically located near the NE
and they communicate in a dedicated LAN.
Traffica Tier 2 consists of a TS or TSs connected to TNESs. It acts as a mediation
between Tier 3 and Tier 1, and as a server for Traffica Clients. TS is also used partly inadministering the system.
In the basic solution, TSs are only on one level. However, it is possible that TS compo-
nents are divided into several TSs. In larger networks, TSs can be divided into two levels
when, at the same time, TNESs are divided into regions (see the figure below). In the
dual level solution, Traffica Tier 2 is divided into several physical sites and several TSs.
TS configurations are described in detail in Installation Guide for Traffica release Z5.2.
Traffica Tier 1
Traffica Tier 2
Traffica Tier 3
TrafficaClient
TS
TNES
NENE Probes
TrafficaClient
TrafficaClient
TNESTNES
-
8/12/2019 Pdn 98904742
16/47
16 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805807719ba
Traffica architecture
Figure 2 Traffica architecture, dual level solution
The simplest and most typical case is that all TS components run in the same TS. It is
possible that TS components are divided into several TSs in a certain site.
Traffica supports multi-technology environments. One TS can be connected to TNESswhich are connected to different NEs, for example 2G MSC and 2G SGSN.
Traffica Tier 2 and 3 have dedicated Traffica HW and they use Windows operating
system.
Traffica Clients are existing PCs in the operator's network. The end-users can use
Traffic News Client and Traffic Views Client from them. They are described in chapters
Traffic News Clientand Traffic Views Client.
4.1 Traffica components
This chapter lists the Traffica server-side components, which are running in TNES or TS.
TrafficaTier 1
TrafficaTier 2
TrafficaTier 3
TrafficaClient
TrafficaClient
TrafficaClient
TrafficaClient
NE Probes
TNESTNES TNES
NENE NE
TNESTNES TNES
NE
TS
TSTS
Traffica component
Location
Traffica Tier 3
Location
Traffica Tier 2
Traffica Database x (x)
Traffica CCMA x (x)
RTT Server x x
NtAlfo x x
Traffic News Server x
Traffic Views Server x
Table 3 Traffica components
-
8/12/2019 Pdn 98904742
17/47
DN98904742
Issue 6-0
17
Traffica Principles Traffica architecture
Id:0900d805807719ba
4.1.1 Traffica Database
Traffica Database Manager (DBM) takes care of Traffica databases. DBM is a service
that runs on TS and TNES. DBM database configuration is modified with registry param-eters and Traffica Admin Tool. RTT Server, Traffic News, Traffica Database Export and
Traffica Configuration and User Server (CUS) interact with DBM in order to access data-
bases. For more information, see Managing Traffica databasesinAdministering Traf-
fica.
4.1.2 Traffica CCMA
TNESs have an online data storage for post-processed counter data. It is called Traffica
Clear Code Matrix (CCMA).
Counter data in CCMA is used locally for updating real-time graphs and generating
alarms. Traffic Views gets its data remotely from TNES CCMA.CCMA contains a predefined part delivered by Nokia Siemens Networks and a user-
defined part that operators can define themselves.
If RTT redirecting from TNES to TS is used, Traffica CCMA can exist in TS also. For
more information about CCMA, see chapter Clear Code Matrix.
4.1.3 RTT Server
The core of TNES functionality is Traffica Real-time Traffic Server (RTT Server). It
receives the RTTs from an NE or probes, stores the RTTs in Traffica Database, and
updates CCMA counters based on the content of the RTTs.
RTT Server carries out the following functions:
Collects RTT reports from an NE
Stores RTT reports into the database
Updates the CCMA counters based on the information in the RTT reports
Updates local graphs based on the local CCMA counters
Generates alarms based on the user definitions and local CCMA counters
Communicates with RTT Server in the TS
RTT Server component also runs in TS. When running in TS, RTT Server is configured
differently and used for administration and for viewing TNES real-time graphs remotely.
Traffica Database Export Server x
Traffica Configuration and User Server x
Traffica Web Server x
Measurement Server x
Traffica File Transfer Service x x
Traffica component
Location
Traffica Tier 3
Location
Traffica Tier 2
Table 3 Traffica components (Cont.)
http://pdn98904754.pdf/http://pdn98904754.pdf/ -
8/12/2019 Pdn 98904742
18/47
18 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805807719ba
Traffica architecture
4.1.4 NtAlfo
NtAlfo is used for forwarding and uploading alarms from Traffica to NetAct Monitor and
SNMP Managers. It can be used for user-defined threshold alarms based on CCMA
counters and for Traffica system internal alarms.
NtAlfo exists in both TNES and TS.
4.1.5 Traffic News Server
Traffic News Server runs in TS and acts as a server for Traffic News Clients. There is
only one of them in the system.
The Traffic News Server sends the query from the client to the selected TNESs where
the query is executed in the Traffica Database. The Traffic News Server sends the query
results back to the client.
Traffic News is administered with Traffica Admin Tool. For more information, see
chapter Traffica Admin Tool.
4.1.6 Traffic Views Server (optional)
Traffic Views Server runs in TS and acts as a server for Traffic Views Clients. It sub-
scribes required counters from Traffica CCMA in TNES for graphs which Views Clients
have activated.
The Traffic Views Server reads all configuration data from CUS. User specific settings
are also stored in CUS when the user logs out from the client.
Traffica Admin Tool is used for administering the Traffic Views system.
In a small network and for a small number of client users, there is only one Traffic ViewsServer. In larger networks and/or with larger amount of users, it can be scaled. For more
information on Traffic Views configuration alternatives, see chapter Traffic Views Server
ConfigurationsinAdministering Traffica.
4.1.7 Traffica Database Export Server (optional)
Traffica Database Export Server runs in TS. It is configured with Database Export Admin
Client and it exports defined data from Traffica Database from TNES. There is only one
of them in the system.
4.1.8 Traffica Configuration and User ServerTraffica Configuration and User Server (CUS) is a centralized storage for Traffica
system configuration, user, and user group definitions. It also provides license informa-
tion for all Traffica applications apart from RTT Server. CUS runs in TS as a Windows
service. The configuration can be viewed and modified with Traffica Admin Tool. For
more information, see chapter Traffica Admin Tool.
Traffic Views, Traffic News, Traffic Simulator, Database Export, KPIE, SRT and RTT
Server authenticate users from CUS. In addition, Traffic Views and Traffic News read
Traffica system configuration and user/user group specific configuration data from CUS.
http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/ -
8/12/2019 Pdn 98904742
19/47
DN98904742
Issue 6-0
19
Traffica Principles Traffica architecture
Id:0900d805807719ba
4.1.9 Traffica Web Server
Traffica Web Server runs Traffic News Web Client and contains Traffica Customer Doc-
umentation in NED format and provides instructions to launch Traffic News Java Client
and Traffic Views Client. Traffic News, Traffic Views, and Traffica Admin Tool provideaccess to online helps from Traffica Web Server.
4.1.10 Measurement Server (optional)
Measurement Server (MS) runs in TS if KPI Export is in use. It reads measurement con-
figuration from CUS and subscribes required CCMA counters from TNESs. TNES sends
CCMA counter values at time class reset to MS, and MS creates output files and sends
them to NetAct.
In larger networks, there needs to be multiple MSs so that each of them handles only
part of the TNESs.
4.1.11 Traffica File Transfer Service
Traffica File Transfer Service is a service for automated transferring of any Traffica files
to a remote server. This service is used for example when transferring RTT Export files
from TNESs to an external FTP server. File transfer configurations are made with
Traffica Admin Tool. For more information, see chapter Traffica Admin Toolin this
document and Creating and modifying file transfer configurationsin Traffica Admin Tool
Help.
4.2 Traffica applications
This chapter lists the Traffica applications that have a graphical user interface.
Traffica applications can be running either in Traffica Client or TNES/TS. They can be
divided into applications which are used by end users or administrators. See the table
below:
4.2.1 Traffic News Client
There are two versions of Traffic News Client:
Traffica Application End user Admin
Traffica
Tier 3
Traffica Tier
2
Traffica
Tier 1
Traffic News Client x x
Traffic Views Client x x
Database Export Admin Client x x x
Traffic Simulator x x
Summary Report Tool x x x x
RTT Server x x x x
Traffica Admin Tool x x x
KPI Export Config Tool x x x
Table 4 Traffica applications
http://pdn0432433.pdf/http://pdn0432433.pdf/ -
8/12/2019 Pdn 98904742
20/47
20 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805807719ba
Traffica architecture
Traffic News Java Client
Traffic News Java Client is a Java application that can be either installed as a local
standalone Java application to the Traffica Client machine or started directly from a URL
in the Traffica Web Server as a Java Web Start application. The standalone version canbe installed from the Traffica Web Server or with Traffica Setup. The Java Web Start
version is recommended because it requires only a JRE installation on the Traffica
Client machine and the latest version of the software is always used automatically.
Traffic News Web Client
Traffic News Web Client runs in the Traffica Web Server and can be launched from a
web browser in the Traffica Client. The Traffic News Java Client connects to Traffica
Web Server which connects to Traffic News Server.
4.2.2 Traffic Views Client
Traffic Views Client is a Java Web Start application. This means that it can be launchedin Traffica Client directly from the URL which is provided in Traffica Web Server. A pre-
condition is that Java Runtime Environment is installed.
4.2.3 Database Export Admin Client
Database Export Admin Client is a remote GUI for configuring the Database Export
Server.
4.2.4 Traffic Simulator
Traffic Simulator is a stand-alone application. For using Traffic Simulator, connection toTraffica Database in TNES is needed. Normally, Traffica Database is copied to a PC
where Traffic Simulator is running. Also, connection to CUS is needed to authenticate
the user.
4.2.5 Summary Report Tool
Summary Report Tool is available for MSC Adaptation only. It can be installed to any
TNES or TS. Summary Report Tool is included in the Traffica Client installation. It
connects directly to the Traffica Database in TNES. For more information on configuring
Summary Report Tool, see Summary Report Tool Help.
4.2.6 RTT Server GUI functions
RTT Server runs in TNES and TS. In addition to its server role, RTT Server has also a
GUI.
In TNES, RTT Server can be used for viewing real-time graphs and alarms. Administra-
tor can use it for defining CCMA, graph and alarm definitions locally.
From TS, RTT Server can be used for viewing remote graphs and for configuring TNESs
remotely. For more information about using TNESs remotely, see chapter Using TNESs
Remotely.
-
8/12/2019 Pdn 98904742
21/47
DN98904742
Issue 6-0
21
Traffica Principles Traffica architecture
Id:0900d805807719ba
4.2.7 Traffica Admin Tool
Traffica Admin Tool is a tool for administrators. It is used for viewing and modifying con-
figuration and user data in CUS.
With Traffica Admin Tool you can give user rights for all applications.
Traffica Admin Tool is used for managing Traffic News users and user rights. The user
group specific rights define which fields and TNESs the users in that user group can use
when making the queries, and which fields can be used when browsing the results.
Traffica Admin Tool is also used for configuring password settings, file transfer settings,
e-mail settings, reason codes for queries and workflows, time and date settings and RTT
server database settings.
If the optional feature Traffic Views exists, Traffica Admin Tool is used for defining TNES
hierarchy, Traffic Views topology, users and user group for Traffic Views. For more infor-
mation, see Traffica Admin Tool Help.
4.2.8 KPI Export Config Tool
KPI Export Config Tool is used for downloading, validating and uploading KPI Export
configuration files. Configuration files are stored in CUS and modified with a text editor.
For more information about KPI Export Config Tool, see chapterAdministering KPI
ExportinAdministering Traffica.
4.3 Connections between Traffica components and applica-
tions
The figure below presents all Traffica components and their connections.
http://pdn0432433.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn0432433.pdf/ -
8/12/2019 Pdn 98904742
22/47
22 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805807719ba
Traffica architecture
Figure 3 Traffica components
4.4 Interfaces
Traffica can be connected to Nokia Siemens Networks components according to the fol-
lowing figure.
NtAlfo
Traffica Tier 1
TrafficaTier 2
Traffica Tier 3
TrafficaCCMA
writealarm orinternalalarm
Traffic ViewsServer
writealarm orinternalalarm
updatecounters
write RTTs
write CRC32-to-string mappings
subscribercounters
readRTTs
query RTTs
export RTTs
Traffic NewsJava Client
Traffic NewsWeb Client
DBE AdminClient
Traffic ViewsClient
connect
connect
administer
get online help
connect andget online help
get online help
get online help
read and writeconfiguration
Traffic NewsServer
DBEServer
connect web client
check license
authenticate, checklicense, read andwrite configuration
TrafficaDatabase
TrafficSimulator
read RTTs
NtAlfo
Trafficaapplications
Trafficaserver-sidecomponents
downloadand uploadconfiguration
subscriber
counters
readconfiguration
KPI ExportConfig Tool
DatabaseManager
SummaryReport Tool
CUS
DatabaseManager
RTTServer
MeasurementServer
write internalalarm
check license
authenticate
authenticate
authenticate
RTTServer
Traffica WebServer
TrafficaAdmin Tool
authenticate
-
8/12/2019 Pdn 98904742
23/47
DN98904742
Issue 6-0
23
Traffica Principles Traffica architecture
Id:0900d805807719ba
Figure 4 Interfaces from Traffica
4.4.1 KPI Export interface to Service Quality Manager
KPI Export is Trafficas PM data interface towards Service Quality Manager (SQM). KPI
Export processes Key Performance Indicators (KPIs) based on RTT Reports, forms
measurements consisting of these KPIs and sends them to the NetAct PM Pipe. The
processing rules of KPIs and measurement structures are predefined. They can be cus-tomised within certain limits. In NetAct, KPI Export measurement data can be utilised in
SQM.
For more information on the KPI Export interface, seeAdministering KPI Exportin
Administering Traffica.
4.4.2 Interface to NetAct Monitor
Traffica user-defined alarms and internal alarms can be forwarded to NetAct Monitor.
NtAlfo needs to be installed on the server from where alarms are forwarded.
SNMP and RPC protocols are used to forward these alarms to NetAct Monitor.
RTT Server user-defined and internal alarms are sent from TNES. Also internal alarms
from Traffic Views, Traffic News, Database Manager, Database Export and File Transfer
Service can be sent to NetAct Monitor. For more information, see chapter Internal
AlarmsinAdministering Traffica.
For information on how to configure alarm forwarding to these NetAct Monitor, refer to
the Installation Guide for Traffica release Z5.2.
4.4.3 Interface to SNMP Managers
Traffica user-defined alarms and internal alarms can be forwarded to NetAct Monitor.
NtAlfo needs to be installed on the server from where alarms are forwarded.
SNMP protocol is used.to forward alarms to SNMP Manager.
http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/ -
8/12/2019 Pdn 98904742
24/47
24 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805807719ba
Traffica architecture
RTT Server user-defined and internal alarms are sent from TNES. Also internal alarms
from Traffic Views, Traffic News, Database Manager, Database Export and File Transfer
Service can be sent to NetAct Monitor. For more information, see chapter Internal
AlarmsinAdministering Traffica.
For information on how to configure alarm forwarding to these SNMP Managers, refer
to the Installation Guide for Traffica release Z5.2
4.4.4 Interface to NTMS
Traffica sends IMSI, IMEI, and MSISDN triplets to NTMS (Nokia Siemens Networks
Terminal Management Server). Traffica writes this data in ASCII files that are trans-
ferred periodically to NTMS using FTP.
NTMS uses the data, for example, for identifying new devices used in the network, and
also devices that have faulty settings.
The NTMS interface is optional.
http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/ -
8/12/2019 Pdn 98904742
25/47
DN98904742
Issue 6-0
25
Traffica Principles Traffica functions
Id:0900d805807719ba
5 Traffica functions
5.1 Traffica basic functions
5.1.1 Data collecting and storing
The following figure illustrates the data flow in Traffica.
Figure 5 Data flow in Traffica
1. Network elements generate statistical data, which is a basis for both the RTT reports
and Charging Records (CDR). Most of the data in RTT and CDR are the same but
data that is not relevant for traffic monitoring is not included in the RTT.
RTT report is a general term used for the real-time traffic reports that are generated
by NEs, and issued to the connected TNESs. Typical RTT reports are voice call
RTTs, SMS RTTs, data call RTTs, and GPRS event RTTs. A voice call RTT is gen-
erated after each call has ended. MSCs generate two kinds of SMS RTTs: one is for
mobile originated short messages, and the other for mobile terminated short mes-
sages.Traffica for probes solution collects its data from the signalling interfaces by Traffica
Certified third party probing solutions. The probes monitor signalling events and
send the collected information to Traffica Network Element Server (TNES).
2. Traffica receives RTT reports from the NEs and identifies them.
3. The CCMA and the database are updated.
4. The real-time graphs and the alarms are updated according to the CCMA.
5. Charging Gateway: CDRs from different network elements.
An essential part of the internal data handling in Traffica is the Internal Data Structure
(IDS). It is an intermediate storage for the incoming binary data. In practice, the IDS
consists of fields, called IDS fields, and all incoming data is copied temporarily into the
IDS fields. Traffica reads RTTs from the IDS one by one, and updates the CCMA anddatabase.
1
CDR
RTT report
Graphs
Alarms
DatabaseData handling
in Traffica
1
2
3
3
4
4CCMA
NE/Probes
5
CG
5
-
8/12/2019 Pdn 98904742
26/47
26 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805807719ba
Traffica functions
Traffica is intended for monitoring the network performance during short time periods,
from a one-second time slice up to 24-hour time slices. However, there are no restric-
tions on the length of the monitored time periods. Still, if you want to collect data, for
example, during one week, the memory capacity sets limits for the accuracy of the data.
In other words, it is not possible to collect data with one-second accuracy for one week.
gIf the Traffica NE connection is down, all the traffic data that the NE generatesduring the time the connection is down, is lost.
The basic idea of Traffica is to collect and store Real-time Traffic (RTT) reports received
directly from Nokia Siemens Networks network elements or probes, or CDRs that are
received from network elements via the Nokia Siemens Networks Charging Gateway
(NCG).
CDRs are generated in the network elements for traffic events according to given rules.
CDRs are normally triggered only for events that are charged. In Nokia Siemens
Networks network elements, it is possible to trigger and send the CDRs in real time, but
it may also be defined by the operator that the CDRs are only sent to NCG at set inter-vals. Traffica receives the CDR data according to these operator specific definitions.
One event generates several CDRs, which are collected and combined in charging and
billing. The Nokia Siemens Networks Charging Gateway generates a copy of each CDR
received and sends the copy to Traffica.
5.1.2 Clear Code Matrix
The CCMA (Clear Code Matrix) is a counter tree. It functions as the real-time data
storage, and as a basis for creating real-time graphs and alarms. In addition to using
predefined CCMA, you can create your own CCMA. For more information, see the
relevant Reference Guide.
You can control the data collected to the CCMA with user-defined formulas and you can
define freely the time resolutions over the data. As an example, the time resolutions can
be one second, one minute, or one day. Certain data can be presented with one-minute
bars or the data can be collected from the beginning of the day and at the end of the day
you can observe, for example, how many calls there were in a certain NE during that
day. After defining the time resolutions you can select the data to be collected under
each time resolution.
There are three member types in the CCMA tree view. The hierarchy is as follows:
Time Class is the root item in the CCMA tree. Time Class icons are displayed in
yellow.
There are five node member types: Expression, Group, Presence, Vector, and Open
node. The node member icons are displayed in blue.
There are three leaf member types: Addition, Counter, and Move. The leaf members
are the actual data storage in the CCMA and their icons are displayed in red.
-
8/12/2019 Pdn 98904742
27/47
DN98904742
Issue 6-0
27
Traffica Principles Traffica functions
Id:0900d805807719ba
Figure 6 Different CCMA members and their icons
Figure 7 An example of the Clear Code Matrix
-
8/12/2019 Pdn 98904742
28/47
28 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805807719ba
Traffica functions
Every time a new RTT report arrives the CCMA is updated. The Time Classes and the
nodes and leaves under them are updated one by one. Each node member contains a
reference to one or several IDS fields which are mapped with the corresponding fields
in an RTT report. Each node member, except for a Vector, also includes a condition
which can be evaluated true or false. If the node condition is evaluated true, the updating
of the subtree under the node is continued. However, if the condition is evaluated false,
the updating of the node is discarded and the following node which has not yet been
updated is inspected to find out whether the condition for that node is evaluated true or
false. As an example, in Figure An example of the Clear Code Matrix, a node of
Presence type with the name Call Answered has a reference to the IDS field
B_Answered_Time and the corresponding field in the RTT report. If the incoming RTT
report contains a value in the B_Answered_Timefield, the condition of the Call
Answered node is evaluated true.
Time Class
When you create a new tree view in the CCMA, Time Class is the root item in the treeview. The Time Class defines how long a time period you want to monitor before the
counters are reset. The CCMA consists of either one or several Time Classes and a
Time Class consists of one or several time resolutions. For the Time Class you define
the time resolution by giving the duration of one time slice interval. You also define the
number of time slices which are stored in the memory as historical data.
For more details on the operating principles of a Time Class, see RTT Server Help.
Expression
Expression is a node member in the CCMA tree view. The Expression type of a node is
intended for general use. The Group and Presence types are special cases of the
Expression type. For Expressions you can use C programming language style expres-sions. In the Expression, you can use IDS field names, operators, and digits. For more
information on the operators, refer to the Expression Properties dialog in the RTT Server
Help. The result of Expression can be saved into CCMA Vector. For more information,
refer to the Vector Properties dialog in the RTT Server Help. The condition for Expres-
sion is evaluated true if the value for Expression equals to or is bigger than (=>) 1, and
the condition is evaluated false if the value equals to (==) 0. You can also use an Expres-
sion node with the IDS fields of array or BCD type, for example, A_Imei.
gNegative expression values are not supported.
Group
Group is a node member in the CCMA tree view. The Group member is useful when youwant to monitor, for example, one or several subscribers, mobile equipment types,
roaming subscribers, cells, or BSCs. Monitoring calls to a certain area code or country
code are also possible.
Group is associated with only one IDS field. The condition for Group consists of a list of
single values, a list of value ranges, or of a list which is a combination of both of these.
The condition is evaluated true if the field in the RTT report, to which Group refers to,
contains the value listed in the Group member. The condition is evaluated false if the
field does not contain a listed value.
The following is an example of an array type of an IDS field. The IDS field is A_Imsi
and the type is BCD8 [8], which is an array of type BCD8 and it consists of eight ele-
ments. The BCD8 type consists of two decimal digits and, consequently, A_Imsiconsists of 16 decimal digits. If you want to create a Group for A_Imsiswhich begins
-
8/12/2019 Pdn 98904742
29/47
DN98904742
Issue 6-0
29
Traffica Principles Traffica functions
Id:0900d805807719ba
with digits 23, you can enter 23 as the value range. Traffica automatically expands this
to 2300000000000000 - 23FFFFFFFFFFFFFF.
Presence
Presence is a node member in the CCMA tree view. Use the Presence type when you
want to see whether a specified field has a value in the RTT report or whether the value
is an empty value. Usually, Presence is associated with one IDS field but it can also be
associated with several IDS fields. If Presence is associated with one IDS field, the
Presence condition is evaluated true when the value for that IDS field exists in the RTT
report. If Presence is associated with several IDS fields, the Presence condition is eval-
uated true when there are values in the RTT report for all the IDS fields defined in Pres-
ence. If this is not the case, the condition is evaluated false.
Vector
Vector is a node member in the CCMA tree view. Usually, a Vector is associated with
one IDS field but it can also be associated with several IDS fields. For example, to definea Vector for both the A and B subscriber cell, the Vector contains two IDS fields, A_Cell
and B_Cell. An array type of IDS field cannot be used in connection with the Vector
member. However, you can use a part of an array field, for example, the first six digits
of A_Imeior B_Imeito create a Vector node.
Vector is a versatile node type. Use Vector when you want to see in one graph all the
values of a certain field in an RTT report. Use Vector also when you want to create one
alarm which applies to all, for example, NEs, clear codes, or cells, and you want to see,
in the Alarms window, the item which triggered the alarm. Also, when you want to create
links between graphs, use a Vector that has another Vector under it in the subtree struc-
ture.
The graphical user interface shows the Vector node and one subtree under it even if aVector creates a subtree for each element in the Vector. These subtrees are physically
in the memory. Structurally these subtrees are alike but the leaf members contain differ-
ent values. For example, in the CCMA you can see a Clear Code Vector and one
counter under it, but physically there is a subtree for each clear code in the memory and
the subtree contains a counter.
Open node
Open node is a node member. Its content can be defined in the
open_node_ccma*.ini files. This enables the updating of a members condition
without using the RTT Server GUI even if a members condition often changes. For more
information, see chapter Managing open nodesinAdministering Traffica.
Addition
Addition is a leaf member in the CCMA tree view. Addition can be placed only under an
Expression node.
The starting value in Addition is 0. When a new RTT report comes, a value is calculated
for the Expression, and this value is added to the value in Addition.
You can use Addition, for example, when you want to know the average call duration.
You have a Counter which shows the number of all calls and, on the same level in the
CCMA, an Expression which calculates the call durations as seconds. The Addition leaf
under Expression cumulates the call durations as seconds. When you create a relative
graph or an alarm, for the Data you insert the Addition and for the Relative Data you
http://pdn98904754.pdf/http://pdn98904754.pdf/ -
8/12/2019 Pdn 98904742
30/47
30 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805807719ba
Traffica functions
insert the Counter, which means that the duration of all calls is divided by the number of
all calls.
Counter
Counter is a leaf member in the CCMA tree view. A Counter can be added anywhere
under a Time Class in the CCMA. When a new RTT report comes and the CCMA is
updated, the value in a Counter is increased by one. The nodes control which Counter
values are increased. When Traffica is started or the CCMA is reset, the Counters are
initialised.
You can place a Counter, for example, directly under a Time Class and name it All
Reports Counter (see Figure An example of the Clear Code Matrix), and the Counter
shows the number of all reports which have come to Traffica. Another example, you can
place a Counter under a node with the name Call Answered and name it Call Answered
Counter, and there the Counter shows the number of answered calls.
MoveMove is a leaf member in the CCMA tree view. A Move member can be added anywhere
under a Time Class in the CCMA. You define an IDS field for the Move. An array type
of an IDS field cannot be used.
The IDS field which is defined in the Move is searched from an RTT report and moved
as such to be the value of the Move member. As an example, the IDS field defined in
the Move is Call_Amount, which in itself is a precalculated counter (by the switch).
When an RTT report arrives, Traffica searches for the Call_Amountfield in the RTT
report and moves the value of the field to be the value of the Move member.
5.1.3 Real-time graphsReal-time graphs visualise the data collected in the CCMA.
Nokia Siemens Networks provides an extensive selection of predefined real-time
graphs. You can easily see the contents of the predefined real-time graphs: place the
cursor on the graph title and a ToolTip appears showing information about the graph
contents. These predefined graphs cannot be changed, but you can use them as a basis
of your own graphs. You can also define entirely new graphs of your own. By using a
predefined graph as a basis or by creating entirely new graphs you can tailor the Traffica
real-time monitoring to meet the needs of your business.
Links between real-time graphs
You can set links between the real-time graphs presenting the measurement data. Forexample, one graph can show the number of calls in each cell. When you click a bar that
presents a cell, the linked graph shows in the form of clear codes how the traffic is suc-
ceeding or failing. When you select another cell, the linked graph is updated and shows
the clear codes for the selected cell.
-
8/12/2019 Pdn 98904742
31/47
DN98904742
Issue 6-0
31
Traffica Principles Traffica functions
Id:0900d805807719ba
Figure 8 An example of linked graphs. A cell is selected in the upper graph and the
clear codes of the cell are displayed in the lower graph.
It is possible that one graph is, at the same time, a target and the starting point of a link,
and that one graph is linked to more than one graph. In this way, a number of graphs
can be linked together, and as a result, versatile information can be derived by linking
the graphs in various ways.
5.1.4 Alarms
You can define your own alarms in Traffica. There are three different types of alarms
available: Limit alarms, Delta threshold alarms, and Burst alarms. In addition to these
user-definable alarms, there are also Traffica internal alarms.
Alarms can be forwarded from TNESs to the TS, and also to NetAct Monitor. Alarms are
also written in the werlogTrafficaAlarm.log file.
When you want to forward an alarm to NetAct Monitor, the alarm number must be within
the ranges 34000 - 34499, 19000-19099, 21500-23799. Make sure that you use differ-
ent alarm numbers for different alarms. Notice however, that if the severity level is Info,the alarm is not forwarded to NetAct Monitor.
Limit alarms
An alarm is triggered when a predefined Limit threshold has been reached.
Figure 9 Limit alarm
Delta threshold alarms
The counter values between two successive time slices are compared, and when the
difference reaches the Delta threshold value the alarm is triggered. The Delta threshold
is specified as a value and direction. The direction can be POSITIVE, NEGATIVE or
Alarm
Thresholdvalue
-
8/12/2019 Pdn 98904742
32/47
32 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805807719ba
Traffica functions
EITHER. This allows the alarm to be triggered if the value of consecutive counters
increases, decreases or changes in either direction.
Figure 10 Delta threshold alarm (the threshold is POSITIVE in this example)
Burst alarms
Short bursts in counter changes between successive time slices are observed, and an
alarm is triggered when the Burst threshold has been reached.
Figure 11 Burst alarm
In addition to the triggering and cancellation details, for each of these alarms you candefine whether the alarm is forwarded to a TS or NetAct Monitor, or both. The interface
timeslice
timeslice
timeslice
timeslice
timeslice
timeslice
Counter values
Differencesbetween
counter values Deltathresholdvalue
Alarm
Burstthreshold
Burstthreshold
No alarm generated:
Alarm generated:
-
8/12/2019 Pdn 98904742
33/47
DN98904742
Issue 6-0
33
Traffica Principles Traffica functions
Id:0900d805807719ba
for the alarms at the NetAct Monitor end is the SNMP interface. Also, for the alarm for-
warding to work, the feature NMS1128 - Alarm collection from Traffica should be acti-
vated. The connection between Traffica and NetAct Monitor is configured by Nokia
Siemens Networks. For more information on the SNMP interface, see Installation Guide
for Traffica release Z5.2.
Traffica internal alarms
In addition to the user-definable alarms, there are a number of Traffica internal alarms.
The number range 19800-19899 is reserved for internal alarms. For details on internal
alarms, see chapter Internal alarmsinAdministering Traffica.
Traffica internal alarms can be automatically forwarded to NetAct Monitor if the following
conditions are met:
In NetAct Monitor Alarm collection from Traffica is activated.
The Alarm severity is other than Info.
The Alarm is enabled.For instructions on how to enable and disable internal alarms, see Configuring internal
alarmsinAdministering Traffica. Alarms are also written in the
werlogTrafficaAlarm.log file.
5.2 Traffic News
Traffic News allows you to make queries in the database and define conditions for your
search.
It is also possible to launch an external tool from Traffic News. This feature is only avail-
able in the Traffic News Java Client. For more information, see Launching an external
toolin Traffic News Helpand Configuring the launch of external applications from TrafficNews ClientinAdministering Traffica.
There are two features of Traffic News available: the standard Traffic News that is avail-
able with Traffica, and the Traffic News client solution which is an optional feature. The
basic functions that allow you to make queries and browse the query results are
common for both of these features.
There are also two different types of Traffic News clients to serve different types of
users. The following table lists the main differences between the clients:
Traffic News, java client Traffic News, web client
You can run user defined queries. You can run user defined queries made in java client
You can create user or user group specific query tem-
plates.
You cannot create queries.
You can define field sets. Field sets are predefined.
You can choose the field sets when browsing the results
after the query.
You have to choose the field sets before the query, it
cannot be changed afterwards.
You can choose events freely. Events are defined in the template, you cannot change
the settings.
Meant for Traffica administrators and other advanced
users.
Meant for users with restricted rights, such as
customer care personnel.
Table 5 Differences between the Traffic News java client and the Traffic News web client
http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn0171584.pdf/http://pdn0171584.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn0171584.pdf/http://pdn0171584.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/ -
8/12/2019 Pdn 98904742
34/47
34 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805807719ba
Traffica functions
With Traffic News you can make a query, for example, if you want to search the calls
made by a certain subscriber.
Making a query and browsing the results with the Java client:
Select a query or start a new query.
Select the databases (TNESs) you want to query. All the databases, custom selec-
tion, TNES group and single TNES selections are available. Select the time span.
Select the event types.
Define the query conditions.
Run the query.
When browsing the results, you can switch between field sets to get different views
on the results.
You can get more specific information about a particular result record by launching
a third party probe vendors application from Traffic News. For more information, see
Launching an external toolin Traffic News Help.
You can also save the results to a file.
Making a query and browsing the results with web client:
Select a query.
Select the databases (TNESs) you want to query. Customised database selection is
not available in the web client, otherwise the database selection is similar to the Java
client.
Select the time span.
Define the query conditions. You can edit/add conditions for fields that are included
in the query. Adding new fields to the query is not possible.
Select field set to be used for viewing the results.
Run the query.
Browse the results. Note: changing field sets is not possible after the query is run.
For instructions on how to make a query, refer to Traffic News Help.
In Traffic News the queries are made in selected TNESs. There are separate queues for
indexed queries and non-indexed queries in the TNESs. An indexed query means a
query where a condition is entered for one or more of the indexed fields in the database.
The queries are executed in the order of arrival in such a fashion that queries from both
queues can run at the same time. This prevents the slower non-indexed queries from
blocking the faster indexed queries.The results are sent back to the clients immediately
after the query is completed. In a situation where several databases are queried simul-
taneously the results will arrive in the client at different times. You are also allowed to
cancel a query.
You can write the query results in a file. You cannot write the query results in a file.
Launch of external applications is available. Launch of external applications is not available.
You can run predefined workflows. There are no predefined workflows.
You can create and run user defined workflows. You cannot create workflows.
Traffic News, java client Traffic News, web client
Table 5 Differences between the Traffic News java client and the Traffic News web client (Cont.)
http://pdn0171584.pdf/http://pdn0171584.pdf/http://pdn0171584.pdf/http://pdn0171584.pdf/http://pdn0171584.pdf/http://pdn0171584.pdf/ -
8/12/2019 Pdn 98904742
35/47
DN98904742
Issue 6-0
35
Traffica Principles Traffica functions
Id:0900d805807719ba
To make queries faster, you can use Traffic News post indexing. For more information
on post indexing, see chapter Configuration filesinAdministering Traffica.
You can perform queries in Traffic News according to a particular workflow, for example,
a series of linked queries where certain query results are used as parameters for thenext query in the series. In addition to the pre-defined workflows, you can also create
new workflows using Traffic News client.
Workflows can be used to troubleshoot problems related to packet switched and circuit
switched data across different elements of a network. For more information, see section
Workflows in Traffic News Help.
Use Traffica Admin Tool for administrating the Traffic News users, user groups and
fields available for the groups. For more information, see chapter Traffica Admin Tool.
The load caused for the Traffica database by the queries is controlled and therefore the
queries do not disturb the basic Traffica functionality. If a TNES is too loaded, the
queries are buffered and executed after the load drops. The number of licences limits
the number of users. However, the more queries there are the slower you receive
results.
There is an automatic log-off feature: if the user has not made any operations for a
certain time, the user is automatically logged off from the server. The time period is
defined in Traffica Admin Tool.
5.3 Traffic Views
In standard Traffica, real-time graphs can be accessed with RTT Server only from TNES
or TS. The optional Traffic Views feature allows the user to access from any client PC a
real-time overview of the network and service status, making the graphs simultaneously
available for any operator task areas. Traffic Views clients can be installed to a normal
office PC in the same LAN as the TNESs and TSs.
Traffic Views is a tool for searching, viewing, and analysing Traffica real-time graphs that
provide visibility to the entire Traffica network and the traffic from the end user point of
view.
Traffic Views provides the user improved functionality to perform tasks related to daily
monitoring, network and traffic benchmarking, and troubleshooting.
Traffic Views client solution includes the following functionality:
Real-time graphs can be viewed from end users PCs, in addition to Traffica Network
Element Servers (TNES) and Traffica Servers (TS).
Reliable security properties: User authentication and encrypted communication.
Flexibility for different user groups: Different user groups can have different graphs
visible by default.
Organising and customising graphs and graph sets according to end-user prefer-
ence.
Basic and linked graphs, graphs based on CCMA counters on TNES.
Possibility to view traffic data in different time dimensions, visualising traffic of one
TNES, a group of TNESs, or the entire Traffica network in graphs. Traffic data can
be viewed combined or separated from a TNES group. Predefined graphs for each
Traffica adaptation.
Selectable time class and data source for a graph. When a graph is defined to
support multiple time classes, you can easily change the time dimension, for
http://pdn98904754.pdf/http://pdn0171584.pdf/http://pdn0171584.pdf/http://pdn98904754.pdf/ -
8/12/2019 Pdn 98904742
36/47
36 DN98904742
Issue 6-0
Traffica Principles
Id:0900d805807719ba
Traffica functions
example, from current day cumulative situation to 30 last minutes values minute by
minute. When a graph is defined to support multiple data sources, you can easily
change from which TNES the data is shown.
Parametrised graphs enable the user to sort the graph by selecting the cell group or
Service Area, for example, that the graph will visualise. Vector parameters can be
predefined or definable run-time by the end user. They can be used to filter or group
CCMA vector items.
Startup parameters for launching the client so that certain graphs and graph sets are
open. It is also possible give filter and grouping parameters for parametrised graphs.
Possibility to see if counter values for a certain graph has not been updated all the
time as they are supposed. The end user can easily detect the reliability of the data.
For more information, see chapter Administering Traffic ViewsinAdministering Traffica.
5.4 Summary Report Tool
Summary Report Tool allows you to generate comprehensive summary reports of both
the call and SMS traffic data in GSM networks.
Nokia Siemens Networks provides a predefined summary report template for generating
the report. The predefined summary report includes fixed sections but you can exclude
certain sections, such as, Paging analysis and Call analysis by PCM line. It can be
useful to create a summary report, for example, once a month, and compare the results
to see the trends.
For the contents of the predefined summary report, see Traffica Reference Guide for
2G/3G Mobile Circuit Switched Core.
For instructions on how to make a report, refer to Summary Report Tool Help.
5.5 Traffica Database Export
Traffica Database Export is a tool for exporting raw data from TNES databases to
external systems where the data can be post-processed and analysed further. Data
Export provides an open interface to TNES database, and thus makes it possible to inte-
grate Traffica with various customer systems, for example:
Customer behaviour analysis system
Profiling system
Fraud detection system
Long-term database for Traffica data
PM tools
Traffica Database Export is adaptation independent. Data transport causes only
minimum load to the network, thus ensuring the basic system performance at all times.
Traffica Database Export reads the selected data in the Traffica database, saves the
data to ASCII type export files, and provides the data to the end user or the system. All
data is encrypted and compressed.
For instructions on how to manage Database Export, see chapter Managing Database
ExportinAdministering Traffica.
http://pdn98904754.pdf/http://pdn98904766.pdf/http://pdn98904766.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904754.pdf/http://pdn98904766.pdf/http://pdn98904766.pdf/http://pdn98904754.pdf/ -
8/12/2019 Pdn 98904742
37/47
DN98904742
Issue 6-0
37
Traffica Principles Traffica functions
Id:0900d805807719ba
5.6 Traffic Simulator
Traffic Simulator is an application that is designed for rerunning the collected network
traffic data with a separate version of Traffica, which is designed especially for display-
ing the simulator data, called Traffica Traffic Simulator Edition. Traffic Simulator is usedin a separate PC than TNES or TS.
Traffic Simulator can be used for the following purposes:
Network planners can access data from a real network, and they can visualise it with
Traffica.
Repeating failure situations in the network and visualising them. This helps to create
alarms with correct thresholds so that the failure would be noticed before it takes
place again.
Demonstrations and training, when a real NE connection is not possible.
In the Traffic Simulator, RTT senders play an important role. An RTT sender reads data
from the database and sends it to Traffica. You can configure several RTT senders intothe Traffic Simulator. The figure below illustrates the architecture.
Figure 12 Traffic Simulator architecture
You can configure remote and local database connections. In this context the term local
is used when the database is physically located on the same machine as the Traffic Sim-
ulator. In a remote configuration the database is physic
top related