pdn0687206 PDF

Serve atOnce Traffica
Z5.2
Traffica Reference Guide for 2G/3G

Packet Core Probes
P-DN0687206
Issue 2-2
Traffica Reference Guide for 2G/3G Packet Core
Probes
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 which
the 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 respective
owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2010/9/9. All rights reserved
f 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 zwangsläufig bestimmte Teile der Geräte unter Span-
nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-
zungen und Sachschäden führen.
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
Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.
2 Id:0900d8058063638c P-DN0687206
Issue 2-2
Probes
Table of Contents
This document has 344 pages.
1 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.1 Where to find more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2 Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3 Terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4 Datatypes and notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5 Traffica for Probes Content for PaCo TNES . . . . . . . . . . . . . . . . . . . . . 14
2 Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1 Changes in Z5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1.2 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1.2.1 General part of each application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1.2.2 Diameter Credit Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1.2.3 DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.1.2.4 HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.1.2.5 MMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.1.2.6 RTSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.1.2.7 SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.1.3 Flow report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.1.4 Gb report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.1.5 Gn report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.1.6 Iu-PS report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.2 Changes in Z5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.3 Changes in Z5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3 Principles of RTT report processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.1 Report generation rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1.1 Application report triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1.1.1 Diameter Credit Control report triggers . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1.1.2 DNS report triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.1.1.3 FTP report triggers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.1.1.4 HTTP report triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.1.1.5 IMAP report triggers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.1.1.6 MMS report triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.1.1.7 POP3 report triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.1.1.8 RADIUS Authentication report triggers . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.1.1.9 RTSP report v2.0 triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.1.1.10 RTSP Method report triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.1.1.11 RTSP QoS report triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.1.1.12 SIP Method report triggers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1.1.13 SIP QoS report triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1.1.14 SMTP report triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1.1.15 WAP report triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1.2 Flow report triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1.3 Gb report triggers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
P-DN0687206 Id:0900d8058063638c 3
Issue 2-2
Probes
3.1.4 Gn report triggers . . . . ...... ....... ...... ....... ...... . . . . . . 24

3.1.5 Gr report triggers. . . . . ...... ....... ...... ....... ...... . . . . . . 25
3.1.6 Iu-PS report triggers . . ...... ....... ...... ....... ...... . . . . . . 25
3.1.7 SMS report triggers. . . ...... ....... ...... ....... ...... . . . . . . 25
4 Real-time monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.1 Open nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.2 Clear Code Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.2.1 Application counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.2.1.1 Diameter Credit Control Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.2.1.2 DNS counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2.1.3 FTP counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.2.1.4 HTTP counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.2.1.5 IMAP counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.2.1.6 MMS counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.2.1.7 POP3 counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2.1.8 RADIUS Authentication counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.2.1.9 RTSP v2.0 counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.2.1.10 RTSP Method counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.2.1.11 RTSP QoS counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.2.1.12 SIP counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.2.1.13 SIP Method counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.2.1.14 SIP QoS counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.2.1.15 SMTP counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.2.1.16 WAP counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.2.2 Flow counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.2.3 Gb counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.2.4 Gn counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.2.5 Gr counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.2.6 Iu-PS counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.2.7 SMS counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.3 Real-time graphs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.3.1 Graph categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.3.2 Graph sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.3.2.1 TRAF TFP 2G PS Default graph sets . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.3.2.2 TRAF TFP 2G/3G PS Default graph sets . . . . . . . . . . . . . . . . . . . . . . . . 66
4.3.2.3 TRAF TFP 3G PS Default graph sets . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.3.2.4 TRAF TFP 2G PS Gb Default weekly graph sets . . . . . . . . . . . . . . . . . . 67
4.3.2.5 TRAF TFP Application Default graph sets . . . . . . . . . . . . . . . . . . . . . . . 67
4.3.2.6 TRAF TFP PS Flow Default graph sets . . . . . . . . . . . . . . . . . . . . . . . . . 70
4.3.3 Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4.3.3.1 TRAF TFP 2G PS Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4.3.3.2 TRAF TFP 2G/3G PS Default Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.3.3.3 TRAF TFP 3G Default Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.3.3.4 TRAF TFP Application Default graphs . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4.3.3.5 TRAF TFP PS Flow Default graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
5 RTT Report descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4 Id:0900d8058063638c P-DN0687206
Issue 2-2
Probes
5.1 Application report fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

5.1.1 General application report fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
5.1.2 Diameter Credit Control specific fields. . . . . . . . . . . . . . . . . . . . . . . . . 110
5.1.3 DNS specific fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.1.4 FTP specific fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.1.5 HTTP specific fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
5.1.6 IMAP specific fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
5.1.7 MMS specific fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
5.1.8 POP3 specific fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
5.1.9 RADIUS Authentication specific fields . . . . . . . . . . . . . . . . . . . . . . . . . 128
5.1.10 RTSP v2.0 specific fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
5.1.11 RTSP Method specific fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
5.1.12 RTSP QoS specific fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
5.1.13 SIP Method specific fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5.1.14 SIP QoS specific fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
5.1.15 SMTP specific fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
5.1.16 WAP specific fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
5.2 Flow report fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
5.3 Gb interface report fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
5.4 Gn interface report fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
5.5 Gr interface report fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
5.6 Iu-PS interface report fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
5.7 SMS report fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
5.8 Logical fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
5.8.1 IDS logical fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
5.8.2 Traffic News logical fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
6 Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
6.1 Appendix A: Cause codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
6.2 Appendix B: Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
6.3 Appendix C: Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
6.4 Appendix D: Mobile Country Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . 335
6.5 Appendix E: Audio and video codecs . . . . . . . . . . . . . . . . . . . . . . . . . 341
6.6 Appendix F: Content types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
P-DN0687206 Id:0900d8058063638c 5
Issue 2-2
Probes
List of Figures
Figure 1 Traffica for Probes environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6 Id:0900d8058063638c P-DN0687206
Issue 2-2
Probes
List of Tables
Table 1 Traffica terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Table 2 Terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Table 3 Datatypes and notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 4 TFP_<Application> database table naming convention . . . . . . . . . . . . 99
Table 5 TFP_GSN_PS_FLOW fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Table 6 TFP_GSN_PS_GB fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Table 7 TFP_GSN_PS_GN fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Table 8 TFP_GSN_PS_GR fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Table 9 TFP_GSN_PS_IUPS fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Table 10 TFP_GSN_PS_SMS fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Table 11 Cause codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Table 12 Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Table 13 Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Table 14 Audio and video codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Table 15 Content types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
P-DN0687206 Id:0900d8058063638c 7
Issue 2-2
About this document Traffica Reference Guide for 2G/3G Packet Core
Probes
1 About this document

Traffica Reference Guide for 2G/3G Packet Core Probes offers reference material
related to both real-time monitoring and analysis of traffic data. It covers the default
Traffica workspace and certain aspects of Traffic News. It is a convenient reference for
the Traffica system administrator as well as the Traffica user.
1.1 Where to find more information

If you are unfamiliar with any of the terms used in this manual, refer to Nokia Siemens
Networks General Glossary.
For further information, refer to:
• Traffica Principles
• Administering Traffica
• 3GPP TS 23.003 Numbering, addressing and identification
• 3GPP TS 23.060 General Packet Radio Service (GPRS); Service description; Stage
2
• 3GPP TS 24.008 Mobile radio interface Layer 3 specification; Core network proto-
cols; Stage 3
• 3GPP TS 24.011 Point-to-Point (PP) Short Message Service (SMS) support on
mobile radio interface
• 3GPP TS 25.413 UTRAN Iu interface Radio Access Network Application Part
(RANAP) signalling
• 3GPP TS 29.002 Mobile Application Part (MAP) specification
• 3GPP TS 29.060 General Packet Radio Service (GPRS); GPRS Tunnelling Protocol
(GTP) across the Gn and Gp interface
• 3GPP TS 33.102 3G security; Security architecture
• 3GPP TS 48.018 General Packet Radio Service (GPRS); Base Station System
(BSS) - Serving GPRS Support Node (SGSN); BSS GPRS protocol (BSSGP)
• IETF RFC 2865 Remote Authentication Dial In User Service (RADIUS)
• IETF RFC 959 File Transfer Protocol (FTP)
• IETF RFC 2821 Simple Mail Transfer Protocol
• IETF RFC 1939 Post Office Protocol - Version 3
• IETF RFC 3501 Internet Message Access Protocol - Version 4rev1
• IETF RFC 2326 Real Time Streaming Protocol (RTSP)
• IETF RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1
• IETF RFC 4006 Diameter Credit-Control Application
• IETF RFC 3261 SIP: Session Initiation Protocol
• IETF RFC 1889 RTP: A Transport Protocol for Real-Time Applications
• IETF RFC 2327 SDP: Session Description Protocol
• IETF RFC3555: MIME Type Registration of RTP Payload Formats
1.2 Terms
The following table presents the most important Traffica terms used in this document. If
a term does not appear in this section, see Nokia Siemens Networks General Glossary.
8 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Traffica Reference Guide for 2G/3G Packet Core About this document
Probes
Concept Description
CCMA (Clear Code Matrix) A tree structure which consists of nodes and counters, and func-
tions 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 Traffica Principles. For
detailed information on the predefined CCMA, see section
CCMA.
Cause code Code that identifies how an event or transaction has ended.
Cause codes are defined for Gb, Gi, Gn, Gr, and Iu-Ps inter-
faces. For detailed cause codes descriptions, refer to the field
description of the reports.
Database A data storage for all RTTs in the TNES. The database is auto-
matically 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 Administering 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.
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 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, see chapter RTT report descriptions.
IDS field An IDS field is mapped with a corresponding field in an RTT
report.
Lower Traffica A Traffica that is lower in the hierarchy. A TNES is a lower
Traffica for a TS.
Network Element (NE) General term, used for all NEs that Traffica can be connected to,
for example, Serving GPRS Support Node (SGSN), Gateway
GPRS Support Node (GGSN) or DX HLR (HLR).
Time Class A root item in the CCMA tree structure which acts as a container
of the time resolution(s) and CCMA members.
Table 1 Traffica terms
P-DN0687206 Id:0900d805807819d6 9
Issue 2-2
Probes
Concept Description
Time resolution A time resolution gives meaning to a Time Class. A time resolu-
tion 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 can be, for example, one second,
minute, or hour. The duration of the time slice defines how long
the data accumulates.
Time resolutions are user-definable, for example, 1*1 day or
30*1 minute.
Time resolution is a range of time slices, and for the user it is typ-
ically visualised as a range of bars in a graph.
During the time defined in the time 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.
Traffica Network Element TNESs collect the RTT reports and these reports are stored in
Server (TNES) the Traffica database.
Traffica Server (TS) A central point in the Traffica system, it is connected to all
TNESs. TS acts as a server for Traffica clients.
Upper Traffica A Traffica that is higher in the hierarchy. For example, a TS is an
upper Traffica for a TNES.
Table 1 Traffica terms (Cont.)
1.3 Terms and abbreviations

The following table lists most of the terms and abbreviations used in this document. If
an abbreviation does not appear in this section, see Nokia Siemens Networks General
Glossary.
Term Explanation
3GPP 3rd Generation Partnership Project, see www.3gpp.org
APN Access Point Name
AUTN Authentication Token
BCD Binary Coded Decimal
BCDTIMESTAMP Datatype that contains date and time
BSC Base Station Controller, Network Element in 2G
BSSGP Base Station System GPRS Protocol
CCA Credit Control Answer (in Diameter protocol)
CCR Credit Control Request (in Diameter protocol)
CGI Cell Global Identification
Table 2 Terms and abbreviations
10 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
Term Explanation
Diameter Computer networking protocol for AAA (authentication, authorization
and accounting).
Diameter Credit- A Diameter application used for credit control.
Control
DL Downlink
DNS Domain Name Server
Empty value The value that is present in the report if no value is specified for the
field.
FTP File Transfer Protocol
Gb The interface between BSC and SGSN
GGSN Gateway GPRS Support Node
Gi The interface between GGSN and the Internet
GMM GPRS Mobility Management
Gn The interface between SGSN and GGSN or between two SGSNs.
Gp Interface between the serving GPRS support nodes (SGSN) of differ-
ent operators' PLMNs.
GPRS General Packet Radio Service
Gr The interface between HLR and SGSN
GTP GPRS Tunnelling Protocol
GTP-C GPRS Tunnelling Protocol - Control plane
GTP-U GPRS Tunnelling Protocol - User plane
HLR Home Location Register
HTTP Hypertext Transfer Protocol
ID Identification
IMAP Internet Message Access Protocol
IMEI International Mobile Equipment Identity
IMSI International Mobile Subscriber Identity
IN Towards mobile, downlink
IP Internet Protocol
IPADDR Datatype that contains IPv4 or IPv6 address
IPv4 Internet Protocol version 4
IPv6 Internet Protocol version 6
Iu-PS The interface between RNC and SGSN
LA Location Area
LAC Location Area Code
LLC Low Layer Compatibility
MAP Mobile Application Part
MCC Mobile Country Code
Table 2 Terms and abbreviations (Cont.)
P-DN0687206 Id:0900d805807819d6 11
Issue 2-2
Probes
Term Explanation
MMS Multimedia Messaging Service
MNC Mobile Network Code
MO Mobile Originated
MS Mobile Station (mobile terminal)
MSIN Mobile Subscriber Identification Number
MSISDN Mobile Subscriber International ISDN number
MT Mobile Terminated
NSAPI Network Layer Service Access Point Identifier
OUT From mobile, uplink
P-TMSI Packet -TMSI
PaCo Packet Core network
PDP Packet Data Protocol
POP3 Post Office Protocol, version 3
PS Packet Switched
QoS Quality of Service
RA Routing Area
RAB Radio Access Bearer
RAC Routing Area Code
RADIUS Protocol used in IP networks, for example, for user authentication and
IP address allocation.
RANAP Radio Access Network Application Part
RAU Routing Area Update
RNC Radio Network Controller, Network Element in 3G
RTCP Real-time Control Protocol
RTP Real-time Transport Protocol
RTSP Real-time Streaming Protocol
SAC Service Area Code
SAPI Service Access Point Identifier
SCCP Signalling Connection Control Part
Service Service that is accessed in the internet; Service IP Address contains
the URL that is accessed, for example in the case of HTTP Service.
SGSN Serving GPRS Support Node
SM Session Management
SMS Short Message Service
SMTP Simple Mail Transfer Protocol
SNDCP Subnetwork Dependent Convergence Protocol
TCP Transmission Control Protocol
12 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
Term Explanation
TEID Tunnel Endpoint Identifier
TFP Traffica for Probes
TIME64 Datatype for time and date, 64-bits
TLLI Temporary Logical Link Identity
TMSI Temporary Mobile Subscriber Identity
UL Uplink
URI Uniform Resource Identifier
UTC Universal Time Co-ordinates
WAP Wireless Application Protocol
1.4 Datatypes and notations

The following datatypes and notations are used in this document:
Datatype or notation Explanation

BCD(n) Binary coded decimal.
A decimal number is coded so that each digit reserves four bits. This
means that one octet is reserved for two digits. The field is n bytes
long.
BCD8(n) Eight-bit binary coded decimal.
BCDTIMESTAMP Data type that contains date and time
Time and date in BCD format: Hour:Min:Sec:10-milliseconds Day-
Month-Year, for example 19:57:32:76 15-11-2005 (hh:mm:ss:nn DD-
MM-CCYY)
Binary(n) Pure hexdump. The length is n bytes.
CHAR(n) n 8-bit long characters
IPADDR UINT8[16]
Data type that presents IPv4 or IPv6 address.
TIME64 64-bit value representing the number of 100-nanosecond intervals
since January 1, 1601 (UTC).
UINT16 16-bit Integer
UINT8 8-bit Integer
Table 3 Datatypes and notations
P-DN0687206 Id:0900d805807819d6 13
Issue 2-2
Probes
1.5 Traffica for Probes Content for PaCo TNES

Traffica for Probes for PaCo TNES gathers data in real time from the main Packet Core
interfaces via probe system, which collects data from Gr, Gb (2G), Gn/Gp, Gi and Iu-PS
(3G) interfaces.
Traffica: Data
collection
and analysis
(TNES)
Probe system:
Signal event
collection and
correlation
Probes
HLR
Gr
Gn Gi
Gb SGSN GGSN Internet
BSC
Iu-PS
RNC
Figure 1 Traffica for Probes environment
14 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Traffica Reference Guide for 2G/3G Packet Core Summary of changes
Probes
2 Summary of changes
This chapter describes the changes in the TFP PS adaptation between releases and
how these changes are reflected in this document.
2.1 Changes in Z5.2
2.1.1 General
• TFP PS interface versions 2.x and 3.0 are supported in Z5.2. TFP PS v1.0 content
has been removed from the TFP PS adaptation. Accordingly all content related to
TFP PS v1.0 has been removed from this document.
• The Open Nodes [RTSP Service IP Address Group] and [DNS Service IP Address
Group] must be defined before the RTSP and DNS graph sets can be used effec-
tively. This is done by editing the open_node_ccma_TFP_PS_1.ini file.For instruc-
tions on how to define Open Nodes, see section Managing Open Nodes in
Administering Traffica.
• IP address -related CRC32-fields will be removed from the TFP PS adaptation in the
future, and should therefore not be used in graph definitions.
2.1.2 Applications
2.1.2.1 General part of each application

The following new fields have been added to all application reports:
• TFP_<Application>_APN
• TFP_<Application>_Direct_Tunnel
• TFP_<Application>_MCC_MNC
• TFP_<Application>_PDP_Context_Activation_Date
• TFP_<Application>_PDP_Context_Activation_Time
• TFP_<Application>_RAN
• TFP_<Application>_RAN_Address_for_User_Traffic
The datatype of the following fields has been changed from UINT32 to UINT64 and the
names of the new fields differ from the old fields as follows (the old UINT32 fields still
exist but it is recommended that their use is discontinued):
– TFP_<Application>_Bytes_IN -> TFP_<Application>_Bytes_IN_Ext
– TFP_<Application>_Bytes_OUT -> TFP_<Application>_Bytes_OUT_Ext
– TFP_<Application>_Packets_IN -> TFP_<Application>_Packets_IN_Ext
– TFP_<Application>_Packets_OUT -> TFP_<Application>_Packets_OUT_Ext
Diameter, RTSP and SIP graphs have been added to the TRAF TFP Application Default
graph sets.
2.1.2.2 Diameter Credit Control

Diameter Credit Control has been added as a new application. For more information on
triggers, counters, fields and graphs, see the following sections respectively:
• Diameter Credit Control report triggers
P-DN0687206 Id:0900d805807819d6 15
Issue 2-2
Summary of changes Traffica Reference Guide for 2G/3G Packet Core
Probes
• Diameter Credit Control counters

• Diameter Credit Control specific fields
• TRAF TFP Application Default graphs
2.1.2.3 DNS
• The following field has been added to the DNS report:
TFP_DNS_Resolved_IP_Address.
• The counter
DNS REPORT\Service IP Vector\UnSuccessful Causes Vector\Counter (Cause)
has been changed to:
DNS REPORT\DNS Service IP Address Group\Service IP Vector\Cause Code
Vector\Counter (Cause).
2.1.2.4 HTTP
• The following field has been added to the HTTP report:
TFP_HTTP_First_URL
2.1.2.5 MMS
• The following trigger has been removed:
81 = Delivery report
2.1.2.6 RTSP
• • TFP PS v2.0 RTSP content is no longer supported in TFP PS v3.0. This content
has been replaced with new RTSP Method and RTSP QoS report types.
• The graphs in graph set TRAF TFP PS Application RTSP are not filled in TFP PS
v3.0.
• The RTSP Method report has been added to application reports. For more informa-
tion, see sections:
– RTSP Method report triggers
– RTSP Method counters
– RTSP Method specific fields
– The following graph sets in section TRAF TFP Application Default graphs:
– TRAF TFP PS Application RTSP Method Monitoring
– TRAF TFP PS Application RTSP Method Service Failures
– TRAF TFP PS Application RTSP Method Statuses
• The RTSP QoS report has been added to application reports. For more information,
see sections:
– RTSP QoS report triggers
– RTSP QoS counters
– RTSP QoS specific fields
– The following graph set in section TRAF TFP Application Default graphs:
– TRAF TFP PS Application RTSP QoS
16 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
2.1.2.7 SIP
• The SIP Method report has been added to application reports. For more information,
see sections:
– SIP Method report triggers
– SIP Method counters
– SIP Method specific fields.
• The SIP QoS report has been added to application reports. For more information,
see sections:
– SIP QoS report triggers
– SIP QoS counters
– SIP QoS specific fields.
– The following graph set in section TRAF TFP Application Default graphs:
– TRAF TFP PS Application SIP QoS
2.1.3 Flow report

• The following new fields have been added to the Flow report:
– TFP_Flow_Direct_Tunnel
– TFP_Flow_RAN
– TFP_Flow_RAN_Address_for_User_Traffic
• The datatype of the following fields has been changed from UINT32 to UINT64 and
the names of the new fields differ from the old fields as follows (the old UINT32 fields
still exist but it is recommended that their use is discontinued):
– TFP_Flow_Bytes_IN -> TFP_Flow_Bytes_IN_Ext
– TFP_Flow_Bytes_OUT -> TFP_Flow_Bytes_OUT_Ext
– TFP_Flow_Packets_IN -> TFP_Flow_Packets_IN_Ext
– TFP_Flow_Packets_OUT -> TFP_Flow_Packets_OUT_Ext
2.1.4 Gb report
• The following triggers have been removed because TFP PS v1.0 is no longer sup-
ported:
– 6 = Data amount based report; active PDP Context
– 8 = Used application is changed
– 9 = Used service is changed
– 11 = Location Area Update, if PDP Context is active
– 13 = SMS sent/received
– 14 = Location Area Update, if GPRS Attached; no active PDP Context
• The following UINT32 fields have been combined into new UINT64 fields as follows:
– TFP_Gb_Total_Bytes_Downlink_High + TFP_Gb_Total_Bytes_Downlink_Low
-> TFP_Gb_Total_Bytes_Downlink
– TFP_Gb_Total_Bytes_Uplink_High + TFP_Gb_Total_Bytes_Uplink_Low ->
TFP_Gb_Total_Bytes_Uplink
– TFP_Gb_User_Data_Bytes_Downlink_High +
TFP_Gb_User_Data_Bytes_Downlink_Low ->
TFP_Gb_User_Data_Bytes_Downlink
P-DN0687206 Id:0900d805807819d6 17
Issue 2-2
Summary of changes Traffica Reference Guide for 2G/3G Packet Core
Probes
– TFP_Gb_User_Data_Bytes_Uplink_High +
TFP_Gb_User_Data_Bytes_Uplink_Low -> TFP_Gb_User_Data_Bytes_Uplink
2.1.5 Gn report
• The following new fields have been added to the Gn report:
– TFP_Gn_Cell_Identity
– TFP_Gn_Direct_Tunnel
– TFP_Gn_Geographic_Location_Type
– TFP_Gn_MCC_MNC
– TFP_Gn_Mean_Throughput_Downlink
– TFP_Gn_Mean_Throughput_Uplink
– TFP_Gn_Peak_Throughput_Downlink
– TFP_Gn_Peak_Throughput_Uplink
– TFP_Gn_RAN
– TFP_Gn_RAN_Address_For_User_Traffic
– TFP_Gn_SAC
– TFP_Gn_User_LAC
• The following graph set has been added to the Gn report:
– TRAF TFP 2G/3G PS Gn MCC-MNC
ported:
– TFP_Gn_GTP_Data_Packets_Downlink_High +
TFP_Gn_GTP_Data_Packets_Downlink_Low ->
TFP_Gn_GTP_Data_Packets_Downlink
– TFP_Gn_GTP_Data_Packets_Uplink_High +
TFP_Gn_GTP_Data_Packets_Uplink_Low ->
TFP_Gn_GTP_Data_Packets_Uplink
– TFP_Gn_GTP_User_Data_Bytes_Downlink_High +
TFP_Gn_GTP_User_Data_Bytes_Downlink_Low ->
TFP_Gn_GTP_User_Data_Bytes_Downlink
– TFP_Gn_GTP_User_Data_Bytes_Uplink_High +
TFP_Gn_GTP_User_Data_Bytes_Uplink_Low ->
TFP_Gn_GTP_User_Data_Bytes_Uplink
– TFP_Gn_Total_Bytes_Downlink_High + TFP_Gn_Total_Bytes_Downlink_Low
-> TFP_Gn_Total_Bytes_Downlink
– TFP_Gn_Total_Bytes_Uplink_High + TFP_Gn_Total_Bytes_Uplink_Low ->
TFP_Gn_Total_Bytes_Uplink
2.1.6 Iu-PS report

• The RTT field TFP_IuPs_Reserved_2 has been split into two fields,
TFP_IuPs_Reserved_22 and TFP_IuPs_GGSN.
18 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
ported:
– TFP_IuPs_Total_Bytes_Downlink_High +
TFP_IuPs_Total_Bytes_Downlink_Low -> TFP_IuPs_Total_Bytes_Downlink
– TFP_IuPs_Total_Bytes_Uplink_High + TFP_IuPs_Total_Bytes_Uplink_Low ->
TFP_IuPs_Total_Bytes_Uplink
– TFP_IuPs_User_Data_Bytes_Downlink_High +
TFP_IuPs_User_Data_Bytes_Downlink_Low ->
TFP_IuPs_User_Data_Bytes_Downlink
– TFP_IuPs_User_Data_Bytes_Uplink_High +
TFP_IuPs_User_Data_Bytes_Uplink_Low ->
TFP_IuPs_User_Data_Bytes_Uplink
2.2 Changes in Z5.1

No changes.
2.3 Changes in Z5
All references to NOKIA in predefined graphs, graph sets, graph categories and time
classes have been replaced with TRAF.
P-DN0687206 Id:0900d805807819d6 19
Issue 2-2
Principles of RTT report processing Traffica Reference Guide for 2G/3G Packet Core
Probes
3 Principles of RTT report processing

This chapter explains which RTT reports are generated for the Traffica system. Multiple
events in signalling can initiate a report to Traffica. These events are defined in section
Report generation rules.
On the other hand, one event may be visible in multiple interfaces, and hence generate
multiple reports. One example of this is PDP Context Activation which can be seen (in
2G environment) in Gb and Gn interfaces.
In case of incomplete signalling, the Signalling Ended time shows the time for the last
signal seen.
Probes can generate some data content to the reports that does not exist in the actual
signalling. An example of this kind of data is network element related data, for example
the logical fields indicating SGSN identification number.
3.1 Report generation rules

Triggering rules are adjustable, and can be turned on and off by the probe.
3.1.1 Application report triggers

Application reports can be collected from Gi, Gn, or Gp interfaces. Optionally reports can
also be collected from Gb and Iu-PS interfaces.
Each application has its own report. The general part is common to all applications. The
general part of the application report is described in section General application report
fields.
At the end of the report there is a section that includes application specific fields. Appli-
cation specific fields are described in the following sections:
• DIAMETER Credit Control specific fields
• DNS specific fields
• FTP specific fields
• HTTP specific fields
• IMAP specific fields
• MMS specific fields
• POP3 specific fields
• RADIUS Authentication specific fields
• RTSP v2.0 specific fields
• RTSP Method specific fields
• RTSP QoS specific fields
• SIP Method specific fields
• SIP QoS specific fields
• SMTP specific fields
• WAP specific fields
The events that trigger application reports are application specific.
3.1.1.1 Diameter Credit Control report triggers

The following events can initiate the Diameter Credit Control report to be sent to Traffica:
20 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Traffica Reference Guide for 2G/3G Packet Core Principles of RTT report processing
Probes
121 = Diameter Credit Control Request and Answer. This report is sent to report a CCR-
CCA pair in case of Initial, Update or Terminate.
122 = Diameter Credit Control Request + idle timeout (no CCA). This report Is sent when
the Diameter Credit Control Request (CCR) has been unreported too long, i.e. for
certain time (see Appendix C: Variables, DIAMETER_CC_timeout_trigger).
3.1.1.2 DNS report triggers

The following events can initiate the DNS report to be sent to Traffica:
73 = DNS reply. Each DNS reply initiates report.
3.1.1.3 FTP report triggers

The following events can initiate the FTP report to be sent to Traffica:
94 = Client receives 221-response from FTP server (closing connection).
95 = FTP idle timeout. There are no transactions for a certain time.
3.1.1.4 HTTP report triggers

The following events can initiate the HTTP report to be sent to Traffica:
70 = HTTP time based report This report is sent if the trigger 71 is not activated
and certain time (see Appendix C: Variables, HTTP_time_trigger) has passed since the
previous report or session start. Session will be closed (no partial reports).
71 = HTTP session idle timeout. If there is no traffic in HTTP session for a certain time
(see Appendix C: Variables, HTTP_idle_timeout) session will be closed and report will
be sent
HTTP report is based on the host field in the HTTP header. One report can include
several GET and response messages. If there are several GET messages where the
host is the same, the GET messages are summed into the same report. If the specified
time (HTTP_time_trigger in chapter variables) has elapsed since the previous
message with the same host field, a report is sent. Referer field is taken from the first
GET message of the report. If HTTP traffic includes WAP messages, then an HTTP
report is not sent. <Messaging_start_time_local> referes to the first HTTP request
message in the report.<Messaging_end_time_local> refers to the last HTTP response
from the server.
3.1.1.5 IMAP report triggers

The following events can initiate the DNS report to be sent to Traffica:
117 = IMAP Bye procedure. Client sends logout-command and receives Bye-response
from IMAP server. Session is closed.
118 = IMAP idle timeout. There are no transactions for a certain time. Session is closed.
119 = IMAP timeout. There are continuous polling/other transactions for a long period.
3.1.1.6 MMS report triggers

The following events can initiate the MMS report to be sent to Traffica:
79 = Send confirmation. MMS Proxy-Relay sends M-Send.conf PDU to mobile
P-DN0687206 Id:0900d805807819d6 21
Issue 2-2
Probes
80 = Send request timeout. M-Send.req PDU is sent from mobile, but MMS Proxy-Relay
doesnt answer (M-Send.conf PDU) in certain time (MMS_send_conf_timeout)
82 = MM notification. MMS Proxy-Relay sends M-Notify-resp-ind PDU to mobile.
83 = Retrieve. MMS Proxy-Relay sends M-Retrieve.conf PDU to mobile.
84 = Retrieve timeout. Mobile has send WSP/HTTP GET message to MMS Proxy-
Relay, but M-retrieve.conf message is not sent to mobile in certain time
(MMS_retrieve_timeout)
3.1.1.7 POP3 report triggers

The following events can initiate the POP3 report to be sent to Traffica:
113 = POP3 QUIT procedure. Client sends QUIT-command and receives OK-response
from POP3 server). Session is closed.
114 = POP3 idle timeout. There are no transactions for a certain time. Session is closed.
115 = POP3 timeout. There are continuous polling/other transactions for a long period.
3.1.1.8 RADIUS Authentication report triggers

The following events can initiate the RADIUS Authentication report to be sent to Traffica:
90 = Access-Accept response is received.
91 = Access-Reject response is received
92 = RADIUS timeout. Client sends request, but server does not respond.
3.1.1.9 RTSP report v2.0 triggers

f These RTSP report triggers are only supported in TFP PS v2.0.
The following events can initiate the RTSP report to be sent to Traffica:
86 = DESCRIBE response. RTSP server sends response to DESCRIBE request
87 = TEARDOWN response. RTSP server sends response to TEARDOWN request
88 = RTSP timeout. Client sends request, but server does not respond
3.1.1.10 RTSP Method report triggers

The following events can initiate the RTSP Method report to be sent to Traffica:
123 = Response to any RTSP method. RTSP server sends response to RTSP method
request
124 = RTSP timeout to any RTSP method. Client sent a request, but the server did not
respond (see Appendix C: Variables, RTSP_timeout_trigger).
3.1.1.11 RTSP QoS report triggers

The following events can initiate the RTSP QoS report to be sent to Traffica:
125 = TEARDOWN response with quality data. The RTSP server sends a response to
a TEARDOWN request.
126 = RTSP timeout with quality data. The connection is inactive for a specified length
of time and therefore closed by the probe (see Appendix C: Variables,
22 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
RTSP_timeout_trigger) AND the probe has started to collect a report (collection is

started from the first setup where the ssrc is defined). This trigger is also used when
TEARDOWN message is lost.
3.1.1.12 SIP Method report triggers

The following events can initiate the SIPMethod report to be sent to Traffica:
127 = Final Response to any SIP method except REGISTER.
128 = SIP timeout to any SIP method. Client sent request, but server does not respond
(see Appendix C: Variables, SIP_timeout_trigger)
129 = SIP: Unsuccessful REGISTER method
130 = SIP: Successful REGISTER method
3.1.1.13 SIP QoS report triggers

The following events can initiate the SIPQoS report to be sent to Traffica:
132 = SIP session is ended.
133 = SIP session idle timeout
3.1.1.14 SMTP report triggers

The following events can initiate the SMTP report to be sent to Traffica:
97 = SMTP close procedure. Client receives 221-response from SMTP server (closing
connection).
98 = SMTP idle timeout. There are no transactions for a certain time.
3.1.1.15 WAP report triggers

The following events can initiate the WAP report to be sent to Traffica:
74 = WSP Connect This report is send when WSP CONNECT primitive is sent and
response is received (Connection-mode WSP)
75 = WSP Disconnect This report is send when WSP connection is closed by WSP Dis-
connect primitive (Connection-mode WSP).
76 = WSP timeout This report is send when WSP connection has been active for certain
time and trigger 75 has not been activated. If WSP session still continues, rest of the
data will be ignored (Connection-mode WSP)
77 = WSP/HTTP Reply This report is triggered when WSP uses connectionless mode
or WAP2 is used. Every WSP/HTTP Reply generates new report
78 = WAP GET timeout. No answer to WSP/HTTP GET primitive. (see Appendix C:
Variables, WAP_GET_time_trigger)
3.1.2 Flow report triggers

Flow reports can be collected from Gi, Gn, or Gp interfaces. Optionally reports can also
be collected from Gb and Iu-PS interfaces. Triggering rules are adjustable; each rule can
be turned on or off by the probe. Each flow session is triggered only once (there are no
partial flow reports). In practice one long flow generates many reports.
P-DN0687206 Id:0900d805807819d6 23
Issue 2-2
Probes
The following events can initiate a flow report to Traffica:

55 = Flow time based report. This report is sent if a certain amount of time has passed
since since the start of the flow session. The session will be closed.
58 = Flow is ended. TCP FIN flag sequence. UDP flow reports cannot use trigger 58.
59 = Flow idle timeout. If there is no traffic in a flow for a certain amount of time, the flow
will be closed and a report will be sent.
3.1.3 Gb report triggers

Triggering rules are adjustable - each rule can be turned on/off by the probe. The follow-
ing events can initiate a Gb report to Traffica:
1 = GPRS Attach
2 = GPRS Detach
3 = PDP Context Activation
4 = PDP Context Modification
5 = Time based report (active PDP Context). This report is sent for active PDP context
after collecting data for xx minutes. Reports with no new/additional data are not pro-
vided. If there is nothing to report, the next checkup takes place after xx minutes again.
Here xx is configurable (see Appendix C: Variables, context_time_trigger) with default
value of 15 minutes.
7 = PDP Context Deactivation
10 = Routing Area Update, if PDP Context is Active
12 = P-TMSI Reallocation
15 = Routing Area Update, if GPRS Attached (no Active PDP Context)
20 = PDP Context closed by the probe system.
21 = Secondary PDP Context Activation
22 = Suspend a GPRS Service
23 = Resume a suspended GPRS Service
101 = Authentication
3.1.4 Gn report triggers

ing events can initiate a Gn report to Traffica:
5 = Time based report; active PDP Context
16 = SGSN Context Transfer
20 = PDP Context closed by the probe system
26 = Identification (GPRS Attach procedure)
24 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
3.1.5 Gr report triggers

ing event can initiate a Gr report to Traffica:
3.1.6 Iu-PS report triggers

Triggering rules are adjustable; each rule can be turned on or off by the probe. The fol-
lowing events can initiate an Iu-PS report to Traffica:
1 = GPRS Attach
2 = GPRS Detach
5 = time based report (active PDP Context). This report is sent for active PDP context
after collecting data for xx minutes. Reports with no new or additional data are not pro-
vided. If there is nothing to report, the next checkup occurs after xx minutes. Here xx is
configurable, with the default value of 15 minutes.
10 = Routing Area Update, if PDP Context is Active
12 = P-TMSI Reallocation
15 = Routing Area Update, if GPRS Attached (no Active PDP Context)
20 = PDP Context closed by the probe system.
21 = Secondary PDP Context Activation
3.1.7 SMS report triggers

Triggering rules are adjustable; each rule can be turned on or off by the probe. The fol-
lowing events can initiate an SMS report to Traffica:
24 = MO SMS
25 = MT SMS
P-DN0687206 Id:0900d805807819d6 25
Issue 2-2
Real-time monitoring Traffica Reference Guide for 2G/3G Packet Core
Probes
4 Real-time monitoring
4.1 Open nodes

Before taking the following open nodes into use, you must define their properties in the
open_node_ccma_TFP_PS_1.ini file:
[RTSP Service IP Address Group]
[DNS Service IP Address Group]
For instructions, see section Managing Open Nodes in Administering Traffica.
4.2 Clear Code Matrix

The counters are presented here in alphabetical order.
4.2.1 Application counters

Application Report\Application Vector\Counter
Description Counts the number of Application reports for each application.
Time class TRAF TFP PS, 1 Day, 24 Hours, 30 Minutes.
Version TFP PS v2.0, TFP PS v3.0
Application Report\Counter
Description Counts the number of Application reports.
4.2.1.1 Diameter Credit Control Counters

DIAMETER CC REPORT\Bits Total\Sum (Total)
Description Cumulative number of total bits. Divided by overall seconds in each
timeclass.
DIAMETER CC REPORT\Counter
Description Counts the number of Diameter Credit Control Reports.
Time class TRAF TFP PS APP, 1 Week; TRAF TFP PS APP, 24 Hours; TRAF TFP
PS APP, 30 Minutes
Version TFP PS v3.0
DIAMETER CC REPORT\Failures\Counter
Description Counts the number of failuring Diameter Credit Control Reports.
PS APP, 30 Minutes
Version TFP PS v3.0
26 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Traffica Reference Guide for 2G/3G Packet Core Real-time monitoring
Probes
DIAMETER CC REPORT\Failures\Failure Result Codes Vector\Counter

Description Counts the number of failuring Diameter Credit Control Reports for each
Failure Result Code.
PS APP, 30 Minutes
Version TFP PS v3.0
DIAMETER CC REPORT\Failures\Failure Result Codes Vector\Request Type

Vector\Counter
Failure Result Code and Request Type.
PS APP, 30 Minutes
Version TFP PS v3.0
DIAMETER CC REPORT\Failures\Failure Result Codes Vector\Service Identifier

Vector\Counter
Failure Result Code and Service identifier.
PS APP, 30 Minutes
Version TFP PS v3.0

Vector\GGSN User Traffic IP Vector\Counter
Failure Result Code, Service identifier and GGSN User Traffic IP.
PS APP, 30 Minutes
Version TFP PS v3.0

Vector\Service IP Vector\Counter
Failure Result Code, Service identifier and Service IP.
PS APP, 30 Minutes
Version TFP PS v3.0
DIAMETER CC REPORT\Initial Messages\Counter

Description Counts the number of Initial Messages of Diameter Credit Control
Reports.
PS APP, 30 Minutes
Version TFP PS v3.0
P-DN0687206 Id:0900d805807819d6 27
Issue 2-2
Probes
DIAMETER CC REPORT\Service Identifier existing\Service Identifier Vector\

Counter
Description Counts the number of Diameter Credit Control Reports for each existing
Service Identifier.
PS APP, 30 Minutes
Version TFP PS v3.0

Failures\Failure Counter
existing Service Identifier.
PS APP, 30 Minutes
Version TFP PS v3.0

Failures\Result Code Vector\Counter
existing Service Identifier and Result Code.
PS APP, 30 Minutes
Version TFP PS v3.0
DIAMETER CC REPORT\Terminate Messages\Counter

Description Counts the number of Terminate Messages of Diameter Credit Control
Reports.
PS APP, 30 Minutes
Version TFP PS v3.0
DIAMETER CC REPORT\Update Messages\Counter

Description Counts the number of Update Messages of Diameter Credit Control
Reports.
PS APP, 30 Minutes
Version TFP PS v3.0
4.2.1.2 DNS counters

DNS REPORT\DNS Service IP Address Group\Bits Total\Sum (Total)
timeclass.
Time class TRAF TFP PS APP, 1 Week, 24 Hours, 30 Minutes
28 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
DNS REPORT\DNS Service IP Address Group\Counter (DNS)

Description Counts number of DNS reports.
DNS REPORT\DNS Service IP Address Group\Service IP Vector\Bits IN\Sum (Bits

IN)
Description Cumulative number of bits towards mobile per DNS server IP. Divided
by overall seconds in each timeclass.
DNS REPORT\DNS Service IP Address Group\Service IP Vector\Bits OUT\Sum

(Bits OUT)
Description Cumulative number of bits from mobile per DNS server IP. Divided by
overall seconds in each timeclass.
DNS REPORT\DNS Service IP Address Group\Service IP Vector\Cause Code

Vector\Counter (Cause)
Description Cause code counter per DNS server IP
DNS REPORT\DNS Service IP Address Group\Service IP Vector\Counter

(Reports/IP)
Description Counts number of DNS reports per DNS server IP.
DNS REPORT\DNS Service IP Address Group\Service IP Vector\Packets IN\Sum

(Packets IN)
Description Cumulative number of packets towards mobile per DNS server IP.
DNS REPORT\DNS Service IP Address Group\Service IP Vector\Packets OUT\

Sum (Packets OUT)
Description Cumulative number of packets from mobile per DNS server IP.
DNS REPORT\DNS Service IP Address Group\Service IP Vector\TCP Retransmit

IN\Sum (Retransmit IN)
Description Cumulative number of TCP retransmitted packets towards mobile per
DNS server IP.
P-DN0687206 Id:0900d805807819d6 29
Issue 2-2
Probes

DNS REPORT\DNS Service IP Address Group\Service IP Vector\TCP Retransmit

OUT\Sum (Retransmit OUT)
Description Cumulative number of TCP retransmitted packets from mobile per DNS
server IP.
DNS REPORT\\DNS Service IP Address Group\Service IP Vector\Unsuccessful

Reports\Counter (Failure)
Description Counts number of errors per DNS server IP.
4.2.1.3 FTP counters

FTP REPORT\Bits Total\Sum (Total)
timeclass.
FTP REPORT\Counter (FTP)

Description Counts number of FTP reports.
FTP REPORT\Service IP Vector\Bits IN\Sum (Bits IN)

Description Cumulative number of bits towards mobile per FTP server IP. Divided
FTP REPORT\Service IP Vector\Bits OUT\Sum (Bits OUT)

Description Cumulative number of bits from mobile per FTP server IP. Divided by
FTP REPORT\Service IP Vector\Cause Codes\Counter (Cause)

Description Cause code counter per FTP server IP
30 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
FTP REPORT\Service IP Vector\Counter

Description Counts number of FTP reports per FTP server IP.
FTP REPORT\Service IP Vector\Error\Counter (Error)

Description Counts number of errors per FTP server IP.
FTP REPORT\Service IP Vector\Packets IN\Sum (Packets IN)

Description Cumulative number of packets towards mobile per FTP server IP.
FTP REPORT\Service IP Vector\Packets OUT\Sum (Packets OUT)

Description Cumulative number of packets from mobile per FTP server IP.
FTP REPORT\Service IP Vector\TCP Retransmit IN\Sum (Retransmit IN)

FTP server IP.
FTP REPORT\Service IP Vector\TCP Retransmit OUT\Sum (Retransmit OUT)

Description Cumulative number of TCP retransmitted packets from mobile per FTP
server IP.
4.2.1.4 HTTP counters

HTTP REPORT\4xx Error\4xx Error Sum\Sum (Error)
Description Counts number of total HTTP 4xx error messages
HTTP REPORT\4xx Error\4xx Error vector\Counter (Error Vector)

Description Cause code counter for HTTP GET 4xx errors
HTTP REPORT\5xx Error\5xx Error Sum\Sum (Error)

Description Counts number of total HTTP 5xx error messages
P-DN0687206 Id:0900d805807819d6 31
Issue 2-2
Probes

HTTP REPORT\5xx Error\5xx Error vector\Counter (Error Vector)

Description Cause code counter for HTTP 5xx errors
HTTP REPORT\Bits IN\Sum (Bits IN)

Description Cumulative number of bits towards mobile. Divided by overall seconds
in each timeclass.
HTTP REPORT\Bits OUT\Sum (Bits OUT)

Description Cumulative number of bits from mobile. Divided by overall seconds in
each timeclass.
HTTP REPORT\Bits Total\Sum (Bits Total)

timeclass.
HTTP REPORT\Counter (HTTP)

Description Counts number of HTTP reports.
HTTP REPORT\Failure\Sum (Failure)

Description Cumulative sum of total HTTP GET errors
HTTP REPORT\GET messages\Sum (Get Messages)

Description Cumulative sum of total HTTP GET messages
4.2.1.5 IMAP counters

IMAP REPORT\Bits Total\Sum (Total)
timeclass.
32 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes

IMAP REPORT\Counter (IMAP)

Description Counts number of IMAP reports.
IMAP REPORT\Service IP Vector\Bits IN\Sum (Bits IN)

Description Cumulative number of bits towards mobile per IMAP server IP. Divided
IMAP REPORT\Service IP Vector\Bits OUT\Sum (Bits OUT)

Description Cumulative number of bits from mobile per IMAP server IP. Divided by
IMAP REPORT\Service IP Vector\Counter

Description Counts number of IMAP reports per IMAP server IP.
IMAP REPORT\Service IP Vector\Error\Counter (Error)

Description Counts number of errors per IMAP server IP.
IMAP REPORT\Service IP Vector\Packets IN\Sum (Packets IN)

Description Cumulative number of packets towards mobile per IMAP server IP.
IMAP REPORT\Service IP Vector\Packets OUT\Sum (Packets OUT)

Description Cumulative number of packets from mobile per IMAP server IP.
IMAP REPORT\Service IP Vector\TCP retransmit IN\Sum (Retransmit IN)

IMAP server IP.
P-DN0687206 Id:0900d805807819d6 33
Issue 2-2
Probes
IMAP REPORT\Service IP Vector\TCP Retransmit OUT\Sum (Retransmit OUT)

Description Cumulative number of TCP retransmitted packets from mobile per
IMAP server IP.
4.2.1.6 MMS counters

MMS REPORT\Bits Total\Sum (Total)
timeclass.
MMS REPORT\Counter (MMS)

Description Counts number of MMS reports.
MMS REPORT\Service IP Vector\Bits IN\Sum (Bits IN)

Description Cumulative number of bits towards mobile per MMS server IP. Divided
MMS REPORT\Service IP Vector\Bits OUT\Sum (Bits OUT)

Description Cumulative number of bits from mobile per MMS server IP. Divided by
MMS REPORT\Service IP Vector\Cause Codes\Counter (Cause)

Description Cause code counter per MMS server IP
MMS REPORT\Service IP Vector\Counter (IP)

Description Counts number of MMS reports per MMS server IP.
MMS REPORT\Service IP Vector\Failure\Counter (Failure)

Description Counts number of errors per MMS server IP.
34 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
MMS REPORT\Service IP Vector\Packets IN\Sum (Packets IN)

Description Cumulative number of packets towards mobile per MMS server IP.
MMS REPORT\Service IP Vector\Packets OUT\Sum (Packets OUT)

Description Cumulative number of packets from mobile per MMS server IP.
MMS REPORT\Service IP Vector\TCP Retransmit IN\Sum (Retransmit IN)

MMS server IP.
MMS REPORT\Service IP Vector\TCP Retransmit OUT\Sum (Retransmit OUT)

Description Cumulative number of TCP retransmitted packets from mobile per MMS
server IP.
4.2.1.7 POP3 counters

POP3 REPORT\Bits Total\Sum (Total)
Description Cumulative number of toal bits. Divided by overall seconds in each time-
class.
POP3 REPORT\Counter (POP3)

Description Counts number of POP3 reports.
POP3 REPORT\Service IP Vector\Bits IN\Sum (Bits IN)

Description Cumulative number of bits towards mobile per POP3 server IP. Divided
POP3 REPORT\Service IP Vector\Bits OUT\Sum (Bits OUT)

Description Cumulative number of bits from mobile per POP3 server IP. Divided by
P-DN0687206 Id:0900d805807819d6 35
Issue 2-2
Probes
POP3 REPORT\Service IP Vector\Counter

Description Counts number of POP3 reports per POP3 server IP.
POP3 REPORT\Service IP Vector\Error\Count (Error)

Description Counts number of errors per POP3 server IP.
POP3 REPORT\Service IP Vector\Packets IN\Sum (Packets IN)

Description Cumulative number of packets towards mobile per POP3 server IP.
POP3 REPORT\Service IP Vector\Packets OUT\Sum (Packets OUT)

Description Cumulative number of packets from mobile per POP3 server IP.
POP3 REPORT\Service IP Vector\TCP Retransmit IN\Sum (Retransmit IN)

POP3 server IP.
POP3 REPORT\Service IP Vector\TCP Retransmit OUT\Sum (Retransmit OUT)

POP3 server IP.
4.2.1.8 RADIUS Authentication counters

RADIUS REPORT\Bits Total\Sum (Bits Total)
timeclass.
RADIUS REPORT\Service IP Vector\Bits IN\Sum (Bits IN)

Description Cumulative number of bits towards mobile per RADIUS server IP.
Divided by overall seconds in each timeclass.
36 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
RADIUS REPORT\Service IP Vector\Bits OUT\Sum (Bits OUT)

Description Cumulative number of bits from mobile per RADIUS server IP. Divided
RADIUS REPORT\Service IP Vector\Counter (Reports/IP)

Description Counts number of RADIUS reports per RADIUS server IP.
RADIUS REPORT\Service IP Vector\Packets IN\Sum (Packets IN)

Description Cumulative number of packets towards mobile per RADIUS server IP.
RADIUS REPORT\Service IP Vector\Packets OUT\Sum (Packets OUT)

Description Cumulative number of packets from mobile per RADIUS server IP.
RADIUS REPORT\Service IP Vector\TCP Retransmit IN\Sum (Retransmit IN)

RADIUS server IP.
RADIUS REPORT\Service IP Vector\TCP Retransmit OUT\Sum (Retransmit OUT)

RADIUS server IP.
RADIUS REPORT\Service IP Vector\Unsuccesful\Counter (Unsuccesful Reports)

Description Counts number of errors per RADIUS server IP.
4.2.1.9 RTSP v2.0 counters

RTSP REPORT\Bits Total\Sum (Bits Total)
timeclass.
P-DN0687206 Id:0900d805807819d6 37
Issue 2-2
Probes
RTSP REPORT\Bytes IN\sum

Description Cumulative number of bits towards mobile per RTSP server IP. Divided
RTSP REPORT\Bytes OUT\sum

Description Cumulative number of bits from mobile per RTSP server IP. Divided by
RTSP REPORT\Counter (RTSP)

Description Counts number of RTSP reports.
RTSP REPORT\Service IP Vector\Bits IN\Sum (Bits IN)

Description Cumulative number of bits towards mobile per RTSP server IP. Divided
RTSP REPORT\Service IP Vector\Bits OUT\Sum (Bits OUT)

Description Cumulative number of bits from mobile per RTSP server IP. Divided by
RTSP REPORT\Service IP Vector\Cause Code Vector\Counter (Cause Code)

Description Cause code counter per RTSP server IP
Version TFP PS v2.0
RTSP REPORT\Service IP Vector\Counter (Reports/IP)

Description Counts number of RTSP reports per RTSP server IP.
RTSP REPORT\Service IP Vector\Failure\Counter (Failure)

Description Counts number of errors per RTSP server IP.
Version TFP PS v2.0
38 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
RTSP REPORT\Service IP Vector\Packets IN\Sum (Packets IN)

Description Cumulative number of packets towards mobile per RTSP server IP.
RTSP REPORT\Service IP Vector\Packets OUT\Sum (Packets OUT)

Description Cumulative number of packets from mobile per RTSP server IP.
RTSP REPORT\Service IP Vector\TCP Retransmit IN\Sum (Retransmit IN)

RTSP server IP.
RTSP REPORT\Service IP Vector\TCP Retransmit OUT\Sum (Retransmit OUT)

RTSP server IP.
4.2.1.10 RTSP Method counters

RTSP REPORT\RTSP Service IP Address Group\RTSP Method\Failed\RTSP
Service IP Vector\Counter
Description Counts RTSP Method Reports with failed status for each RTSP Service
IP.RTSP Service IPs are limited with Open Node.
Version TRAF TFP PS APP, 1 Week; TRAF TFP PS APP, 24 Hours; TRAF TFP
PS APP, 30 Minutes
Version TFP PS v.3.0
RTSP REPORT\RTSP Service IP Address Group\RTSP Method\RTSP Service IP

Vector\Counter
Description Counts the RTSP Service IPs in RTSP Method Report. RTSP Service
IPs are limited with Open Node.
PS APP, 30 Minutes

Vector\Failed\Failed Counter
Description Counts the failing RTSP Service IPs in RTSP Method Report. RTSP
Service IPs are limited with Open Node.
PS APP, 30 Minutes
P-DN0687206 Id:0900d805807819d6 39
Issue 2-2
Probes

Vector\Failed\Method Vector\Counter
Description Counts the failed methods for each RTSP Service IPs in RTSP Method
Report. RTSP Service IPs are limited with Open Node.
PS APP, 30 Minutes

Vector\Failed\Method Vector\Status Vector\Counter
Description Counts statuses for each failed method for each RTSP Service IPs in
RTSP Method Report. RTSP Service IPs are limited with Open Node.
PS APP, 30 Minutes

Vector\Failed\Status Vector\Counter
Description Counts failed statuses for each RTSP Service IPs in RTSP Method
Report. RTSP Service IPs are limited with Open Node.
PS APP, 30 Minutes

Vector\Failed\Status Vector\Method Vector\Counter
Description Counts methods for each failed status for each RTSP Service IPs in
RTSP Method Report. RTSP Service IPs are limited with Open Node.
PS APP, 30 Minutes
RTSP REPORT\RTSP Service IP Address Group\RTSP Method\RTSP Session\

RTSP Service IP Vector\Counter
Description Counts RTSP Service IPs in RTSP Session in RTSP Method Reports.
RTSP Sessions are counted from RTSP Method Reports with Method
= Describe. RTSP Service IPs are limited with Open Node.
PS APP, 30 Minutes
RTSP REPORT\RTSP Service IP Address Group\RTSP Method\Status Vector\

Counter
Description Counts Statuses in RTSP Method Reports. RTSP Service IPs are
limited with Open Node.
40 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
PS APP, 30 Minutes

Method Vector\Counter
Description Counts Methods in RTSP Method Reports for each Status.RTSP
Service IPs are limited with Open Node.
PS APP, 30 Minutes

Method Vector\RTSP Service IP Vector\Counter
Description Counts RTSP Service IP Addresses for each Status and Method in
RTSP Method Reports. RTSP Service IPs are limited with Open Node.
PS APP, 30 Minutes

RTSP Service IP Vector\Counter
Description Counts RTSP Service IP Addresses for each Status in RTSP Method
Reports. RTSP Service IPs are limited with Open Node.
PS APP, 30 Minutes

RTSP Service IP Vector\Method Vector\Counter
Description Counts Methods for each Service IP Address and Status in RTSP
Method Reports. RTSP Service IPs are limited with Open Node.
PS APP, 30 Minutes
4.2.1.11 RTSP QoS counters

RTSP REPORT\RTSP Service IP Address Group\RTSP QoS Report\Audio DL MOS
Reliable\RTSP Service IP Vector\Counter
Description Counts the number of RTSP QoS reports for user defined (open node)
RTSP Service IPs where the Audio downlink MOS values are reliable.
This is done for each RTSP Service IP Address.
PS APP, 30 Minutes
Version TFP PS v3.0
P-DN0687206 Id:0900d805807819d6 41
Issue 2-2
Probes

Reliable\RTSP Service IP Vector\Min MOS Audio DL x100\Sum Min MOS Audio DL
x100
Description Sums the min audio MOS values (unit 0.01) of the downlink data from
the RTSP QoS Reports where the values are reliable for each RTSP
Service IP.
PS APP, 30 Minutes
Version TFP PS v3.0

Reliable\RTSP Service IP Vector\MOS Audio DL x100\Sum MOS Audio DL x100
Description Sums the average audio MOS values (unit 0.01) of the downlink data
from the RTSP QoS Reports where the values are reliable for each
RTSP Service IP.
PS APP, 30 Minutes
Version TFP PS v3.0
RTSP REPORT\RTSP Service IP Address Group\RTSP QoS Report\DL Volumes

exist\RTSP Service IP Vector\bytes DL\Sum Bytes DL
Description Sums the downlink bytes for each RTSP Service IP (open node limited).
This information is from RTSP QoS report.
PS APP, 30 Minutes
Version TFP PS v3.0
RTSP REPORT\RTSP Service IP Address Group\RTSP QoS Report\RTSP Service

IP Vector\Counter
Description Counts the RTSP QoS reports for each RTSP Service IP.
PS APP, 30 Minutes
Version TFP PS v3.0
RTSP REPORT\RTSP Service IP Address Group\RTSP QoS Report\Video DL MOS

Reliable\RTSP Service IP Vector\Counter
Description Counts the number of RTSP QoS reports for user defined (open node)
RTSP Service IPs where the Video downlink MOS values are reliable.
This is done for each RTSP Service IP Address.
PS APP, 30 Minutes
Version TFP PS v3.0
42 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes

Reliable\RTSP Service IP Vector\Min MOS Video DL x100\Sum Min MOS Video DL
x100
Description Sums the min video MOS values (unit 0.01) of the downlink data from
the RTSP QoS Reports where the values are reliable for each RTSP
Service IP.
PS APP, 30 Minutes
Version TFP PS v3.0

Reliable\RTSP Service IP Vector\MOS Video DL x100\Sum MOS Video DL x100
Description Sums the average video MOS values (unit 0.01) of the downlink data
from the RTSP QoS Reports where the values are reliable for each
RTSP Service IP.
PS APP, 30 Minutes
Version TFP PS v3.0
4.2.1.12 SIP counters

SIP REPORT\Counter
Description Counts the number of SIP reports.
PS APP, 30 Minutes
Version TFP PS v3.0
SIP REPORT\Bits Total\Sum (Total)

timeclass.
PS APP, 30 Minutes
Version TFP PS v3.0
4.2.1.13 SIP Method counters

SIP REPORT\SIP Method\GGSN User Traffic Vector\Counter
Description Counts the number of SIP Method reports for each GGSN.
PS APP, 30 Minutes
Version TFP PS v3.0
SIP REPORT\SIP Method\SIP Failed Method\GGSN User Traffic Vector\Counter

Description Counts the number of failing SIP Method reports for each GGSN.
PS APP, 30 Minutes
P-DN0687206 Id:0900d805807819d6 43
Issue 2-2
Probes
Version TFP PS v3.0
SIP REPORT\SIP Method\SIP Failed Method\GGSN User Traffic Vector\No Reply\

No Reply Counter
Description Counts the number of SIP Method reports which is triggered by timeout.
PS APP, 30 Minutes
Version TFP PS v3.0
SIP REPORT\SIP Method\SIP Failed Method\GGSN User Traffic Vector\Others\

Status Vector\Counter
Description Counts the number of SIP errros for each GGSN and Status. Unsuc-
cessful registrations and no replys are not counted here.
PS APP, 30 Minutes
Version TFP PS v3.0
SIP REPORT\SIP Method\SIP Failed Method\GGSN User Traffic Vector\Unsuc-

cessful Registrations\Status Vector\Counter
Description Counts the number of Unsuccessful SIP Registrations for each GGSN
and for each Status.
PS APP, 30 Minutes
Version TFP PS v3.0
SIP REPORT\SIP Method\SIP Session\GGSN User Traffic Vector\Counter

Description Counts the number of SIP Sessions for each GGSN.
PS APP, 30 Minutes
Version TFP PS v3.0
4.2.1.14 SIP QoS counters

SIP REPORT\SIP QoS\Audio MOS Reliable\GGSN User Traffic Vector\Min MOS
Audio x100\Sum Min MOS Audio x100
Description Sums the reliable minimum Audio MOS (x100) values (UL+DL) for each
GGSN.
PS APP, 30 Minutes
Version TFP PS v3.0
SIP REPORT\SIP QoS\Audio MOS Reliable\GGSN User Traffic Vector\MOS Audio

x100\Sum MOS Audio x100
Description Sums the reliable Audio MOS (x100) values (UL+DL) for each GGSN.
PS APP, 30 Minutes
Version TFP PS v3.0
44 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
SIP REPORT\SIP QoS\Audio MOS Reliable\GGSN User Traffic Vector\Reliable

Values\Sum Reliable Values
Description Sums the reliable audio UL+DL values.
PS APP, 30 Minutes
Version TFP PS v3.0
SIP REPORT\SIP QoS\GGSN User Traffic Vector\Bytes\Sum Bytes

Description Sums the bytes for each GGSN.
PS APP, 30 Minutes
Version TFP PS v3.0
SIP REPORT\SIP QoS\GGSN User Traffic Vector\Counter

Description Counts the number of SIP QoS reports for each GGSN.
PS APP, 30 Minutes
Version TFP PS v3.0
SIP REPORT\SIP QoS\Video MOS Reliable\GGSN User Traffic Vector\Min MOS

Video x100\Sum MinMOS Video x100
Description Sums the reliable minimum Videl MOS (x100) values (UL+DL) for each
GGSN.
PS APP, 30 Minutes
Version TFP PS v3.0
SIP REPORT\SIP QoS\Video MOS Reliable\GGSN User Traffic Vector\MOS Video

x100\Sum MOS Video x100
Description Sums the reliable Video MOS (x100) values (UL+DL) for each GGSN.
PS APP, 30 Minutes
Version TFP PS v3.0
SIP REPORT\SIP QoS\Video MOS Reliable\GGSN User Traffic Vector\Reliable

Values\Sum Reliable Values
Description Sums the reliable video UL+DL values.
PS APP, 30 Minutes
Version TFP PS v3.0
4.2.1.15 SMTP counters

SMTP REPORT\Bits IN\Sum (Bits IN)
Description Cumulative number of bits towards mobile per SMTP server IP. Divided
P-DN0687206 Id:0900d805807819d6 45
Issue 2-2
Probes

SMTP REPORT\Bits OUT\Sum (Bits OUT)

Description Cumulative number of bits from mobile per SMTP server IP. Divided by
SMTP REPORT\Bits Total\Sum (Bits Total)

timeclass.
SMTP REPORT\Cause Codes\Counter (Cause)

Description Cause code counter per SMTP server IP
SMTP REPORT\Counter (SMTP)

Description Counts number of SMTP reports.
SMTP REPORT\Error\Counter (Error)

Description Counts number of errors per SMTP server IP.
SMTP REPORT\Packets IN\Sum (Packets IN)

Description Cumulative number of packets towards mobile per SMTP server IP.
SMTP REPORT\Packets OUT\Sum (Packets OUT)

Description Cumulative number of packets from mobile per SMTP server IP.
SMTP REPORT\TCP Retransmit IN\Sum (Retransmit IN)

SMTP server IP.
46 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
SMTP REPORT\TCP Retransmit OUT\Sum (Retransmit OUT)

SMTP server IP.
4.2.1.16 WAP counters

WAP REPORT\Bits IN\Sum (Bits IN)
Description Cumulative number of bits towards mobile. Divided by overall seconds
in each timeclass.
WAP REPORT\Bits OUT\Sum (Bits OUT)

Description Cumulative number of bits from mobile. Divided by overall seconds in
each timeclass.
WAP REPORT\Bits Total\Sum (Bits Total)

timeclass.
WAP REPORT\Counter (WAP)

Description Counts number of WAP reports.
WAP REPORT\Delay\Sum (Delay)

Description Sum of delay in WAP GET messages
WAP REPORT\Fail Total\Sum (Fail Total)

Description Cumulative sum of total WAP errors
WAP REPORT\Get Fail Reason Vector\Counter (Get Reason)

Description Cause code counter for WAP GET messages
P-DN0687206 Id:0900d805807819d6 47
Issue 2-2
Probes
WAP REPORT\Get Fail\Sum (Fail)

Description Counts number of WAP GET errors
WAP REPORT\GET Success\Sum (Succes)

Description Counts number of succesful WAP GET messages
WAP REPORT\Post Fail Reason Vector\Counter (Post Reason)

Description Cause code counter for WAP POST messages
WAP REPORT\Total Messages\Sum (Total Messages)

Description Cumulative sum of total WAP messages
4.2.2 Flow counters

FLOW REPORT\Bits Total\Sum (Bits Total)
timeclass and multiplied by FLOW sampling rate
FLOW REPORT\Counter
Descriptions Counts the number of Flow reports.
Tme class TRAF TFP PS, 1 Day, 24 Hours, 30 Minutes.
FLOW REPORT\Counter (FLOW)

Description Counts number of FLOW reports.
FLOW REPORT\L4 port\Bandwidth\Sum (Bandwidth)

timeclass.
48 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
FLOW REPORT\L4 port\Bits IN\Sum (Bits IN)

Description Cumulative number of bits towards mobile per TCP/UDP port. Divided
FLOW REPORT\L4 port\Bits OUT\Sum (Bits OUT)

Description Cumulative number of bits from mobile per TCP/UDP port. Divided by
FLOW REPORT\L4 port\Counter (L4 Port)

Description Counts number of FLOW reports per TCP/UDP port
FLOW REPORT\L4 port\Delay\Sum (Delay)

Description Sum of delay in FLOW reports
FLOW REPORT\L4 port\Packets IN\Sum (Packets IN)

Description Cumulative number of packets towards mobile per TCP/UDP port.
FLOW REPORT\L4 port\Packets OUT\Sum (Packets OUT)

Description Cumulative number of packets from mobile per TCP/UDP port.
FLOW REPORT\L4 port\Packets Total\Sum (Packets Total)

TCP/UDP port.
FLOW REPORT\L4 port\TCP Retransmit IN\Sum (TCP Retransmit IN)

TCP/UDP port.
P-DN0687206 Id:0900d805807819d6 49
Issue 2-2
Probes
FLOW REPORT\L4 port\TCP Retransmit OUT\Sum (TCP Retransmit OUT)

TCP/UDP port.
FLOW REPORT\L4 port\TCP Retransmit Total\Sum (TCP Retransmit)

TCP/UDP port.
4.2.3 Gb counters
The following counters involve the Gb interface only.
Gb Report\APN Vector\Counter
Description Counts the number of Gb reports for each APN.
Gb Report\APN Vector\Downlink PDP Context kilobytes\Sum Downlink kilobytes

Description Counts the PDP context download in kilobytes for each APN.
Gb Report\APN Vector\SM Cause Vector\Counter

Description Counts the number of Gb reports for each APN for each SM Cause.
Gb Report\APN Vector\Uplink PDP Context kilobytes\Sum Uplink kilobytes

Description Counts the PDP context upload in kilobytes for each APN.
Gb Report\Counter
Description Counts the number of Gb Reports.
Time class TRAF TFP PS, 1 Day, 24 Hours, 30 Minutes, Week
Gb Report\GPRS Attach\Counter
Description Counts the number of GPRS Attaches.
Time class TRAF TFP PS, Week
50 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
Gb Report\GPRS Attaches\Counter
Description Counts the number of GPRS Attach attempts.
Gb Report\GPRS Attaches\Mobile Type Vector\Counter

Description Counts the number of GPRS Attach attempts for each Mobile Type.
Gb Report\GPRS Attach\Mobile Type Vector\Counter

Description Counts the number of GPRS Attaches for each Mobile Type.
Gb Report\GPRS Attach\Mobile Type Vector\GMM Cause Vector\Counter

Description Counts the number of GPRS Attaches for each Mobile Type for each
GMM Cause.
Gb Report\GPRS Attach\Mobile Type Vector\SM Cause Vector\Counter

Description Counts the number of GPRS Attaches for each Mobile Type for each
SM Cause.
Gb Report\GPRS Attaches\LAC Vector\Counter

Description Counts the number of GPRS Attach attempts for each LAC.
Gb Report\GPRS Attaches\Unsuccessful\Counter
Description Counts the number of unsuccessful GPRS Attach attempts.
Gb Report\GPRS Attaches\Unsuccessful\GMM Cause Vector\Counter

Gb Report\GPRS Attaches\Unsuccessful\GMM Cause Vector\LAC Vector\Counter

Description Counts the number of unsuccessful GPRS Attach attempts for each
GMM Cause for each LAC.
P-DN0687206 Id:0900d805807819d6 51
Issue 2-2
Probes
Gb Report\GPRS Attaches\Unsuccessful\LAC Vector\Counter

LAC.
Gb Report\GPRS Attaches\Unsuccessful\LAC Vector\GMM Cause Vector\Counter

LAC for each GMM Cause.
Gb Report\GPRS Detaches\Counter
Description Counts the number of GPRS Detach attempts.
Gb Report\GPRS Detaches\Unsuccessful\Counter
Description Counts the number of unsuccessful GPRS Detaches.
Gb Report\PDP Context Activations\Cell Vector\Counter

Description Counts the number of PDP Context Activation attempts for each Cell.
Gb Report\PDP Context Activations\Counter

Description Counts the number of PDP Context Activation attempts.
Gb Report\PDP Context Activations\LAC Vector\Cell Vector\Counter

Description Counts the number of PDP Context Activation attempts for each LAC
and for each Cell.
Gb Report\PDP Context Activations\LAC Vector\Counter

Description Counts the number of PDP Context Activation attempts for each LAC.
52 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
Gb Report\PDP Context Activations\Mobile Type Vector\Counter

Description Counts the number of PDP Context Activation attempts for each Mobile
Type.
Gb Report\PDP Context Activations\Unsuccessful\Cell Vector\Counter

Description Counts the number of unsuccessful PDP Context Activation attempts
for each Cell.
Gb Report\PDP Context Activations\Unsuccessful\Cell Vector\SM Cause Vector\

Counter
for each Cell and for each SM Cause.
Gb Report\PDP Context Activations\Unsuccessful\Counter

Description Counts the number of unsuccessful PDP Context Activation attempts.
Gb Report\PDP Context Activations\Unsuccessful\LAC Vector\Cell Vector\

Counter
for each LAC and for each Cell.
Gb Report\PDP Context Activations\Unsuccessful\LAC Vector\Cell Vector\SM

Cause Vector\Counter
for each LAC for each Cell and for each SM Cause.
Gb Report\PDP Context Activations\Unsuccessful\LAC Vector\Counter

for each LAC.
P-DN0687206 Id:0900d805807819d6 53
Issue 2-2
Probes
Gb Report\PDP Context Activations\Unsuccessful\SM Cause Vector\Cell Vector\

Counter
for each SM Cause for each Cell.
Gb Report\PDP Context Activations\Unsuccessful\SM Cause Vector\Counter

for each SM Cause.
Gb Report\PDP Context Activations\Unsuccessful\SM Cause Vector\LAC Vector\

Cell Vector\Counter
for each SM Cause for each LAC and for each Cell.
Gb Report\PDP Context Activations\Unsuccessful\SM Cause Vector\LAC Vector\

Counter
for each SM Cause for each LAC.
Gb Report\PDP Context Deactivations\Counter

Description Counts the number of PDP Context Deactivation attempts.
Gb Report\PDP Context Deactivations\Unsuccessful\Counter

Description Counts the number of unsuccessful PDP Context Deactivation
attempts.
Gb Report\PDP Context Modifications\Counter

Description Counts the number of PDP Context Modification attempts.
Gb Report\PDP Context Modifications\Unsuccesful\Counter

Description Counts the number of unsuccessful PDP Context Modification attempts.
54 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
Gb Report\RAU\Counter
Description Counts the number of RAU attempts.
Gb Report\RAU\Unsuccesful\Counter
Description Counts the number of unsuccessful RAU attempts.
Gb Report\Report Reason Vector\Counter

Description Counts the number of Gb Reports for each report trigger.
Gb Report\Report Reason Vector\Mobile Home Network Vector\Counter

Description Counts the number of Gb Reports for each report trigger for each Mobile
Home Network.
Gb Report\Report Reason Vector\Mobile Home Network Vector\Mobile Type

Vector\Counter
Home Network for each Mobile Type.

Vector\GMM Cause Vector\Counter
Description Counts the number of Gb Reports for each Mobile Home Network for
each Mobile Type for each report trigger for each GMM Cause.

Vector\SM Cause Vector\Counter
Home Network for each Mobile Type for each SM Cause.
P-DN0687206 Id:0900d805807819d6 55
Issue 2-2
Probes
Gb Report\Report Reason Vector\Mobile Home Network Vector\Successful\Suc-

cessful Counter
Description Counts the number of successful Gb Reports for each report trigger for
each Mobile Home Network.
Gb Report\Report Reason Vector\Mobile Home Network Vector\Unsuccessful\

GMM Cause Vector\Counter
Description Counts the number of unsuccessful Gb Reports for each report trigger
for each Mobile Home Network for each GMM Cause.
Gb Report\Report Reason Vector\Mobile Home Network Vector\Unsuccessful\SM

Cause Vector\Counter
for each Mobile Home Network for each SM Cause.

Unsuccessful Counter
for each Mobile Home Network.

Unsuccessful GMM\GMM Cause Vector\Counter
for each Mobile Home Network for each GMM Cause.

Unsuccessful SM\SM Cause Vector\Counter
for each Mobile Home Network for each SM Cause.
Gb Report\Report Reason Vector\Mobile Type Vector\Counter

Type.
56 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
Gb Report\Report Reason Vector\Mobile Type Vector\GMM Cause Vector\Counter

Type for each GMM Cause.
Gb Report\Report Reason Vector\Mobile Type Vector\SM Cause Vector\Counter

type for each SM Cause.
Gb Report\Unsuccessful\Mobile Type Vector\Counter

Description Counts the number of unsuccessful reports for each Mobile Type.
Gb Report\Unsuccessful\Mobile Type Vector\Report Reason Vector\Counter

Description Counts the number of unsuccessful reports for each Mobile Type for
each report trigger.
Gb Report\Unsuccessful\Mobile Type Vector\Report Reason Vector\GMM Cause

Vector\Counter
each trigger for each GMM Cause.
Gb Report\Unsuccessful\Mobile Type Vector\Report Reason Vector\SM Cause

Vector\Counter
each trigger for each SM Cause.
4.2.4 Gn counters
Gn Report\APN Vector\Counter
Description Counts the number of Gn reports for each APN.
Gn Report\APN Vector\Downlink PDP Context kilobytes\Sum Downlink kilobytes

P-DN0687206 Id:0900d805807819d6 57
Issue 2-2
Probes

Gn Report\APN Vector\GTP Cause Vector\Counter

Description Counts the number of Gn reports for each APN for each GTP Cause.
Gn Report\APN Vector\Uplink PDP Context kilobytes\Sum Uplink kilobytes

Gn Report\Counter
Description Counts the number of Gn reports.
Gn Report\Other Operators\MCC_MNC Vector\Counter

Description Counts the number of Gn reports for each MCC-MNC pair
Version TRAF TFP PS, 1 Day, 24 Hours, 30 Minutes
Version TFP PS v3.0
Gn Report\Other Operators\MCC_MNC Vector\GTP Cause Vector\Counter

Description Counts the GTP Causes for each selected MCC-MNC pair.
Version TFP PS v3.0
Gn Report\Other Operators\MCC_MNC Vector\kilobytes\Sum of kilobytes

Description Counts the data amounts monitored for each MCC-MNC pair
Version TFP PS v3.0
Gn Report\Report Reason Vector\Counter

Description Counts the number of Gn Reports for each report trigger.
Gn Report\Report Reason Vector\GTP Cause Vector\APN Vector\Counter

Description Counts the number of Gn Reports for each report trigger for each GTP
Cause for each APN.
58 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
Gn Report\Report Reason Vector\GTP Cause Vector\Counter

Description Counts the number of Gn Reports for each report trigger for each GTP
Cause.
Gn Report\Report Reason Vector\Imsi Country Network Vector\Counter

Description Counts the number of Gn Reports for each report trigger for each IMSI
Country Network.
Gn Report\Report Reason Vector\Imsi Country Network Vector\GTP Cause

Vector\Counter
Description Counts the number of Gn Reports for each report trigger for each IMSI
Country Network for each GTP Cause.
4.2.5 Gr counters
Gr Report\Counter
Description Counts the number of Gr reports.
4.2.6 Iu-PS counters

IuPS Report\APN Vector\Counter
Description Counts the number of Iu-PS reports for each APN.
IuPS Report\APN Vector\Downlink PDP Context kilobytes\Sum Downlink kilo-

bytes
IuPS Report\APN Vector\SM Cause Vector\Counter

Description Counts the number of Iu-PS reports for each APN for each SM cause.
P-DN0687206 Id:0900d805807819d6 59
Issue 2-2
Probes
IuPS Report\APN Vector\Uplink PDP Context kilobytes\Sum Uplink kilobytes

IuPS Report\Counter
Description Counts the number of Iu-PS Reports.
IuPS Report\GPRS Attaches\Counter

Description Counts the number of GPRS Attach attempts.
IuPS Report\GPRS Attaches\LAC Vector\Counter

Description Counts the number of GPRS Attach attempts for each LAC.
IuPS Report\GPRS Attaches\Mobile Type Vector\Counter

Description Counts the number of GPRS Attach attempts for each Mobile Type.
IuPS Report\GPRS Attaches\Unsuccessful\Counter

IuPS Report\GPRS Attaches\Unsuccessful\GMM Cause Vector\Counter

Description Counts the number of unsuccessful GPRS Attaches for each attempt
for each GMM Cause.
IuPS Report\GPRS Attaches\Unsuccessful\GMM Cause Vector\LAC Vector\

Counter
Description Counts the number of unsuccessful GPRS Attaches for each GMM
Cause for each LAC.
IuPS Report\GPRS Attaches\Unsuccessful\LAC Vector\Counter

Description Counts the number of unsuccessful GPRS Attaches for each LAC.
60 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
IuPS Report\GPRS Attaches\Unsuccessful\LAC Vector\GMM Cause Vector\

Counter
Description Counts the number of unsuccessful GPRS Attaches for each LAC for
each GMM Cause.
IuPS Report\GPRS Detaches\Counter

Description Counts the number of GPRS Detach attempts.
IuPS Report\GPRS Detaches\Unsuccessful\Counter

Description Counts the number of unsuccessful GPRS Detaches.
IuPS Report\PDP Context Activations\Counter

Description Counts the number of PDP Context Activation attempts.
IuPS Report\PDP Context Activations\Mobile Type Vector\Counter

Description Counts the number of PDP Context Activation attempts for each Mobile
Type.
IuPS Report\PDP Context Activations\SAC Vector\Counter

Description Counts the number of PDP Context Activation attempts for each SAC.
IuPS Report\PDP Context Activations\Unsuccessful\Counter

Description Counts the number of unsuccessful PDP Context Activations.
IuPS Report\PDP Context Activations\Unsuccessful\SAC Vector\Counter

Description Counts the number of unsuccessful PDP Context Activations for each
SAC.
P-DN0687206 Id:0900d805807819d6 61
Issue 2-2
Probes
IuPS Report\PDP Context Activations\Unsuccessful\SAC Vector\SM Cause

Vector\Counter
SAC for each SM Cause.
IuPS Report\PDP Context Activations\Unsuccessful\SM Cause Vector\Counter

SM Cause.
IuPS Report\PDP Context Activations\Unsuccessful\SM Cause Vector\SAC

Vector\Counter
SM Cause for each SAC.
IuPS Report\PDP Context Deactivations\Counter

Description Counts the number of PDP Context Deactivation attempts.
IuPS Report\PDP Context Deactivations\Unsuccessful\Counter

Description Counts the number of unsuccessful PDP Context Deactivations.
IuPS Report\PDP Context Modifications\Counter

Description Counts the number of PDP Context Modification attempts.
IuPS Report\PDP Context Modifications\Unsuccessful\Counter

Description Counts the number of unsuccessful PDP Context Modifications.
IuPS Report\RAUs\Counter
Description Counts the number of RAUs.
62 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
IuPS Report\RAUs\Unsuccessful\Counter
Description Counts the number of unsuccessful RAUs.
4.2.7 SMS counters

SMS Report\2G SMS\Counter
Description Counts the number of 2G SMSs.
SMS Report\2G SMS\Unsuccessful\Counter

Description Counts the number of unsuccessful 2G SMSs.
SMS Report\3G SMS\Counter

Description Counts the number of 3G SMSs.
SMS Report\3G SMS\Unsuccessful\Counter

Description Counts the number of unsuccessful 3G SMSs.
SMS Report\Counter
Description Counts the number of SMS reports.
4.3 Real-time graphs
4.3.1 Graph categories

All Graph Categories consist of a number of Graph Sets, which, in turn, include a
number of graphs. This Traffica release contains the following Graph Categories in
alphabetical order:
TRAF TFP 2G PS Default Graphs

Time Class: TRAF TFP PS, 1 Day, 24 Hours, 30 Minutes
Description: Contains Gb specific graph sets.
Version: TFP PS v2.0, TFP PS v3.0
P-DN0687206 Id:0900d805807819d6 63
Issue 2-2
Probes
TRAF TFP 2G/3G PS Default Graphs

Time class: TRAF TFP PS, 1 Day, 24 Hours, 30 Minutes
Description: Contains Gn specific graph sets. Additionally contains a general overview
of the PS interfaces.
TRAF TFP 3G PS Default Graphs

Time class: TRAF TFP PS, 1 Day, 24 Hours, 30 Minutes
Description: Contains Iu-PS specific graph sets.
TRAF TFP 2G PS Gb Default Graphs, Weekly

Time class: TRAF TFP PS, 1 Week
Description: Contains default weekly Gb specific graph sets.
TRAF TFP Application Default Graphs

TRAF TFP PS APP, 1 Week, 24 Hours, 30 Minutes
Description: Contains application-specific graph sets.
TRAF TFP PS Flow Default Graphs

TRAF TFP PS APP, 1 Week, 24 Hours, 30 Minutes
Description: Contains flow-specific graph sets.
4.3.2 Graph sets
4.3.2.1 TRAF TFP 2G PS Default graph sets

These graph sets belong to TRAF TFP 2G PS Default Graphs category and involve the
Gb interface.
TRAF TFP 2G PS Gb APN

Explanation Shows the APNs and the corresponding upload/download amounts and
GTP Causes.
Time Class TRAF TFP PS, 1 Day, 24 Hours, 30 Minutes
TRAF TFP 2G PS Gb Attaches

Explanation Shows the LAC distribution for GPRS Attach Attempts, used mobile
types and the corresponding LACs and GMM Causes for unsuccessful
GPRS Attaches.
64 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
TRAF TFP 2G PS Gb Events

Explanation Shows the number of different events.
TRAF TFP 2G PS Gb Failure Percentages

Explanation Shows the failure percentage for different events.
TRAF TFP 2G PS Gb PDP Context Activations

Explanation Shows the cell distribution and used mobile types for PDP Context Acti-
vation Attempts and the corresponding cells and SM Causes for unsuc-
cessful PDP Context Activations in Gb interface.
TRAF TFP 2G PS Gb Report Reasons per Mobile Type

Explanation Shows the used mobile types and the cause codes for each report
reason.
TRAF TFP 2G PS Gb Roaming Mobile Types

Explanation Shows the subscriber home networks, mobile type percentages and
cause codes for each Report Reason.
TRAF TFP 2G PS Gb Roaming Overview

Explanation Shows the subscriber home networks, subscriber home network
success ratios and the cause code percentages for each Report
Reason.
TRAF TFP 2G PS Gb SMSs

Explanation Shows the number of SMS reports in Gb interface.
TRAF TFP 2G PS Gb Unsuccessful SMSs %

Explanation Shows the percentage of unsuccessful 2G SMSs in Gb interface.
P-DN0687206 Id:0900d805807819d6 65
Issue 2-2
Probes
TRAF TFP 2G PS Gb Unsuccessful Reports per Mobile Type

Explanation Shows the mobile types for unsuccessful reports for report reasons and
cause codes.
4.3.2.2 TRAF TFP 2G/3G PS Default graph sets

These graph sets belong to TRAF TFP 2G/3G PS Default Graphs category.
TRAF TFP 2G/3G PS General Overview 2

Explanation Shows the number of events in each interface.
TRAF TFP 2G/3G PS Gn APN

GTP Causes in Gn interface.
TRAF TFP 2G/3G PS Gn GTP Causes

Explanation Shows the Report Reasons, their GTP Causes and APNs in Gn inter-
face.
TRAF TFP 2G/3G PS Gn MCC-MNC

Explanation This graph set shows the traffic for each MCC-MNC by showing the
data amounts and report amounts. Reports can be drilled down to GTP
Causes.
Version TFP PS v3.0
TRAF TFP 2G/3G PS Gn Overview

Explanation Shows the number of events in the Gn interface.
4.3.2.3 TRAF TFP 3G PS Default graph sets

These graph sets belong to TRAF TFP 3G PS Default Graphs category.
TRAF TFP 3G PS Iu-PS APN

GTP Causes.
66 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
TRAF TFP 3G PS Iu-PS Events

Explanation Shows the number of different events.
TRAF TFP 3G PS Iu-PS Failure Percentages

Explanation Shows the failure percentage for different events.
TRAF TFP 3G PS Iu-PS GPRS Attaches

Explanation Shows the number of GPRS Attaches.
TRAF TFP 3G PS Iu-PS PDP Context Activations

Explanation Shows the number of PDP Context Activaitons.
4.3.2.4 TRAF TFP 2G PS Gb Default weekly graph sets

These graph sets belong to TRAF TFP 2G PS Gb Default Graphs, Weekly category.
TRAF TFP 2G PS GPRS Attaches

Explanation In Gb interface this graph set shows in weekly timeclass the mobile
types in GPRS Attaches and the corresponding GMM and SM Cause
values.
Time Class TRAF TFP PS, Week
4.3.2.5 TRAF TFP Application Default graph sets

TRAF TFP PS Application Diameter CC Failures
Description This graph set shows the failure percent for each Service Identifier for
Diameter Credit Control Reports. It also shows the failed result codes
for the selected Service Identifier. Also the number of Diameter Credit
Control attempts are available by Service Identifiers.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application Diameter CC Overview

Description This graph set shows the different Diameter Credit Control message
types. Furthermore it shows the failure percentage. The failed result
P-DN0687206 Id:0900d805807819d6 67
Issue 2-2
Probes
codes can be drilled down to Service Identifiers (and down to GGSN IP

and Service IP) and Request Types.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application DNS

Description This graph set shows DNS information per server.
TRAF TFP PS Application FTP

Description This graph set shows FTP information per server.
TRAF TFP PS Application General

Description This graph set shows bandwidth of each application.
TRAF TFP PS Application HTTP

Description This graph set shows HTTP information.
TRAF TFP PS Application IMAP

Description This graph set shows IMAP information per server.
TRAF TFP PS Application MMS

Description This graph set shows MMS information per server.
TRAF TFP PS Application POP3

Description This graph set shows POP3 information per server.
TRAF TFP PS Application RADIUS

Description This graph set shows RADIUS information per server.
68 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
TRAF TFP PS Application RTSP

Description This graph set shows RTSP information per server.
Version TFP PS v2.0
TRAF TFP PS Application RTSP Method Monitoring

Description This graph set shows a general view to RTSP Method reports by
showing simultaneously RTSP Sessions, RTSP Method reports, RTSP
Failed Method reports and failure %s for each Service IP Address.
RTSP Service IPs are limited with Open Node.
Version TFP PS v3.0
TRAF TFP PS Application RTSP Method Service Failures

Description This graph set shows the RTSP Failures per Service IP Address.
Selecting on IP shows its failure % and Methods that was failed and
failing response statuses. Each of those can be drilled down until status
and method respectively. RTSP Service IPs are limited with Open
Node.
Version TFP PS v3.0
TRAF TFP PS Application RTSP Method Statuses

Description This graph set shows the RTSP Response statuses. Selecting one of
them drills down to methods and RTSP Service IP Addresses, which
can be drilled down to RTSP Service IP Addresses and Methods
respectively.RTSP Service IPs are limited with Open Node.
Version TFP PS v3.0
TRAF TFP PS Application RTSP QoS

Description This graph set shows the average and minimum MOS for audio and
video for user defined (open node) RTSP Service IPs. Addiotionally it
shows the data amounts and report counts.
Version TFP PS v3.0
TRAF TFP PS Application SIP Sessions

Description This graph set shows the SIP Sessions for each GGSN.
Version TFP PS v3.0
TRAF TFP PS Application SIP QoS

Description This graph set shows the average of the following measurements:
Audio average MOS, Audio min MOS, Video average MOS and Video
min MOS for each GGSN. Additionally it shows the data volumes and
report count per GGSN.
P-DN0687206 Id:0900d805807819d6 69
Issue 2-2
Probes

Version TFP PS v3.0
TRAF TFP PS Application SMTP

Description This graph set shows SMTP information per server.
TRAF TFP PS Application WAP

Description This graph set shows WAP information.
4.3.2.6 TRAF TFP PS Flow Default graph sets

TRAF TFP PS Flow General
Description This graph set shows flow statistics per TCP/UDP port. Sorted by band-
width.
TRAF TFP PS Flow TCP Retransmit

Description This graph set shows flow statistics per TCP/UDP port. Sorted by TCP
retransmit.
4.3.3 Graphs
4.3.3.1 TRAF TFP 2G PS Graphs

These graphs involve the Gb interface.
TRAF TFP 2G PS Gb APN

Description Shows the APNs in the reports.
Time class TRAF TFP PS, 1 Day, 24 Hours, 30 Minutes
TRAF TFP 2G PS Gb APN -> Downlink in Mbyte

Description Shows the PDP Context downlink traffic for each APN in Mbytes.
TRAF TFP 2G PS Gb APN -> SM Cause

Description Shows the SM Cause values for each APN.
70 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
TRAF TFP 2G PS Gb APN -> Uplink in Mbytes

Description Shows the PDP Context uplink traffic for each APN in Mbytes.
TRAF TFP 2G PS Gb Attach GMM Causes

Description Shows the GMM Causes for each Mobile Type.
Time class TRAF TFP PS, 1 week
TRAF TFP 2G PS Gb Attach Mobile Type

Description Shows the GPRS Attach attempts for each Mobile Type.
TRAF TFP 2G PS Gb Attach SM Causes

Description Shows the SM Causes for each Mobile Type.
TRAF TFP 2G PS Gb Attaches per Mobile Type

Description Shows the GPRS Attach attemps for each Mobile Type.
TRAF TFP 2G PS Gb GPRS Attach

Description Shows the number of GPRS Attach attempts.
TRAF TFP 2G PS Gb GPRS Attaches per LAC

Description Shows the number of GPRS attaches for each LAC.
TRAF TFP 2G PS Gb GPRS Detach

Description Shows the number of GPRS Detach attempts.
TRAF TFP 2G PS Gb Model -> Reason -> GMM Cause

Description Shows the GMM Causes for the unsuccessful reports for each Mobile
Type for each report reason.
P-DN0687206 Id:0900d805807819d6 71
Issue 2-2
Probes
TRAF TFP 2G PS Gb Model -> Reason -> SM Cause

Description Shows the SM Causes for the unsuccessful reports for each Mobile
Type for each report reason.
TRAF TFP 2G PS Gb Model -> Report Reason

Description Shows the Report Reasons for each Mobile Type.
TRAF TFP 2G PS Gb PDP Context Activation per Cell

Description Shows the number of PDP Context Activations, distributed according to
Cell for selected LAC. Both successful and unsuccessful Context Acti-
vations are counted.
TRAF TFP 2G PS Gb PDP Context Activation per LA

LACs. Both successful and unsuccessful Context Activations are
counted.
TRAF TFP 2G PS Gb PDP Context Activation per Mobile Type

Mobile Types. Both successful and unsuccessful Context Activations
are counted.
TRAF TFP 2G PS Gb PDP Context Activations_1

Description Shows the number of PDP Context Activation attempts.
TRAF TFP 2G PS Gb PDP Context Deactivations

Description Shows the number of PDP Context Deactivation attempts.
TRAF TFP 2G PS Gb PDP Context Modifications

Description Shows the number of PDP Context Modification attempts.
72 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
TRAF TFP 2G PS Gb RAU

Description Shows the number of reported Routing Area Update attempts.
TRAF TFP 2G PS Gb Reason -> Mobile Type

Description Shows for each Report Reason the Mobile Type distribution.
TRAF TFP 2G PS Gb Reason -> Model -> GMM Cause

Description Shows the GMM Causes for each Report Reasons for each Mobile
Types.
TRAF TFP 2G PS Gb Reason -> Model -> SM Cause

Description Shows the SM Causes for each Report Reasons for each Mobile Types.
TRAF TFP 2G PS Gb Reason -> NO

Description Shows the Attemps for selected report reason for each Subscriber
Home Network.
TRAF TFP 2G PS Gb Reason -> NO -> Mobile Type Percent

Description Shows the Mobile Types percentages for selected report reason and for
selected subscriber home network.
TRAF TFP 2G PS Gb Reason -> NO -> Model -> GMM Cause

Description Shows the GMM Causes for selected report reason, subscriber home
network and Mobile Type.
TRAF TFP 2G PS Gb Reason -> NO -> Model -> SM Cause

Description Shows the SM Causes for selected report reason, subscriber home
network and Mobile Type.
P-DN0687206 Id:0900d805807819d6 73
Issue 2-2
Probes
TRAF TFP 2G PS Gb Reason -> Successful %

Description Shows the percentage of success for the selected event.
TRAF TFP 2G PS Gb Reason -> Unsuccessful %

Description Shows the percentage of unsuccess for the selected event.
TRAF TFP 2G PS Gb Reason -> Unsuccessful -> GMM Cause %

Description Shows the percentage of the GMM Causes for the selected Subscriber
Home Network and unsuccessful Report Reason.
TRAF TFP 2G PS Gb Reason -> Unsuccessful -> SM Cause

Description Shows the precentage of the SM Causes for the selected Subscriber
Home Network and unsuccessful Report Reason.
TRAF TFP 2G PS Gb Report Reason

Description Shows how many and which reports are seen.
TRAF TFP 2G PS Gb Report Reasons

Description Shows the Report Reasons.
TRAF TFP 2G PS Gb Unsuccessful GMM Cause

Description Shows the unsuccessful GPRS Attach GMM Causes.
TRAF TFP 2G PS Gb Unsuccessful GMM Cause -> LAC

Description Shows LACs for each GMM Cause.
TRAF TFP 2G PS Gb Unsuccessful GPRS Attaches %

Description Shows the percentage of GPRS Attaches that has GPRS Mobility Man-
agement related error code (Gb interface).
74 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
TRAF TFP 2G PS Gb Unsuccessful GPRS Detaches %

Description Shows the percentage of GPRS Detaches that has GPRS Mobility Man-
agement related error code (Gb interface).
TRAF TFP 2G PS Gb Unsuccessful LAC

Description Shows LACs in unsuccessful GPRS Attaches.
TRAF TFP 2G PS Gb Unsuccessful LAC -> GMM Cause

Description Shows the GMM Causes for selected LAC.
TRAF TFP 2G PS Gb Unsuccessful PDP Context Activation Cells per SM Cause

Description Shows the Cells for each SM Cause and LAC in Unsuccessful PDP
Context Activations.
TRAF TFP 2G PS Gb Unsuccessful PDP Context Activation LACs per SM Cause

Description Shows the LACs for each SM Cause in Unsuccessful PDP Context Acti-
vations.
TRAF TFP 2G PS Gb Unsuccessful PDP Context Activation SM Causes

Description Shows the SM Causes in Unsuccessful PDP Context Activations.
TRAF TFP 2G PS Gb Unsuccessful PDP Context Activations %

Description Shows the percentage of PDP Context Activations that has Session
Management related error code (Gb interface).
TRAF TFP 2G PS Gb Unsuccessful PDP Context Activations per Cell

Description Shows the number of unsuccessful PDP Context Activations, distrib-
uted according to Cell for selected LAC.
P-DN0687206 Id:0900d805807819d6 75
Issue 2-2
Probes
TRAF TFP 2G PS Gb Unsuccessful PDP Context Activations per Cell per SM

Cause
Description Shows the number of unsuccessful PDP Context Activations for
selected LAC and Cell, distributed according to SM Cause.
TRAF TFP 2G PS Gb Unsuccessful PDP Context Activations per LAC

Description Shows the number of unsuccessful PDP Context Activations, distrib-
uted according to LAC.
TRAF TFP 2G PS Gb Unsuccessful PDP Context Deactivations %

Description Shows the percentage of PDP Context Deactivations that has Session
TRAF TFP 2G PS Gb Unsuccessful PDP Context Modification %

Description Shows the percentage of PDP Context Modifications that has Session
TRAF TFP 2G PS Gb Unsuccessful RAUs %

Description Shows the percentage of reported PDP Context Routing Area Updates
that has Session Management related error code (Gb interface).
TRAF TFP 2G PS Gb Unsuccessful Reports per Mobile Type

Description Shows the distribution of Mobile Types for unsuccessful Gb reports.
4.3.3.2 TRAF TFP 2G/3G PS Default Graphs

TRAF TFP 2G/3G PS Application Count
Description This graph shows the total number of application reports.
TRAF TFP 2G/3G PS Applications Count

Description Shows the number of different Application reports.
76 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
TRAF TFP 2G/3G PS Flow Report Count

Description This graph shows the number of Flow reports.
TRAF TFP 2G/3G PS Gb Report Count2

Description Shows the number of Gb reports.
TRAF TFP 2G/3G PS Gn APN

Description Shows the APNs in the reports in the Gn interface.
TRAF TFP 2G/3G PS Gn APN -> Downlink in Mbyte

Description Shows the PDP Context downlink traffic for each APN in Mbytes in Gn
interface.
TRAF TFP 2G/3G PS Gn APN -> GTP Cause

Description Shows the GTP Cause values for each APN in Gn interface.
TRAF TFP 2G/3G PS Gn APN -> Uplink in Mbytes

Description Shows the PDP Context uplink traffic for each APN in Mbytes in Gn
interface.
TRAF TFP 2G/3G PS Gn MCC_MNC data

Description This graph shows the data (uplink+downlink) amounts in kilobytes for
each MCC-MNC pair that is unequal to Imsi-operator.
Version TFP PS v3.0
TRAF TFP 2G/3G PS Gn MCC_MNC GTP Cause

Description This graph shows the GTP Causes for selected MCC-MNC pair that is
unequal to Imsi-operator.
Version TFP PS v3.0
P-DN0687206 Id:0900d805807819d6 77
Issue 2-2
Probes
TRAF TFP 2G/3G PS Gn MCC_MNC reports

Description This graph shows the report count for each MCC-MNC pair that is
unequal to Imsi-operator.
Version TFP PS v3.0
TRAF TFP 2G/3G PS Gn Reason -> Cause

Description Shows the GTP Causes for each Gn Report Reason.
TRAF TFP 2G/3G PS Gn Reason -> Cause -> APN

Description Shows the APNs for each GTP Cause for each Gn Report Reason.
TRAF TFP 2G/3G PS Gn Reason -> Imsi Country Network

Description Shows the Subscriber Home Networks for selected Report Reason in
Gn interface.
TRAF TFP 2G/3G PS Gn Reason -> MNC -> GTP Cause

Description Shows the GTP Causes for the selected Report Reason and Home
Network Subscriber in Gn interface.
TRAF TFP 2G/3G PS Gn Report Count2

Description Shows the number of Gn reports.
TRAF TFP 2G/3G PS Gn Report Reason

Description Shows the Report Reasons in Gn interface.
TRAF TFP 2G/3G PS Gr Report Count2

Description Shows the number of Gr reports.
TRAF TFP 2G/3G PS IuPS Report Count2

Description Shows the number of Iu-PS reports.
78 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
TRAF TFP 2G/3G PS SMS Report Count2

Description Shows the number of SMS reports.
4.3.3.3 TRAF TFP 3G Default Graphs

All graphs in this set involve the Iu-PS interface.
TRAF TFP 3G PS Iu-PS APN

Description Shows the APNs in the reports.
TRAF TFP 3G PS Iu-PS APN -> Downlink in Mbytes

Description Shows the PDP Context downlink traffic for each APN in Mbytes.
TRAF TFP 3G PS Iu-PS APN -> SM Cause

Description Shows the SM Cause values for each APN.
TRAF TFP 3G PS Iu-PS APN -> Uplink in Mbytes

Description Shows the PDP Context uplink traffic for each APN in Mbytes.
TRAF TFP 3G PS Iu-PS Attach

Description Shows the number of GPRS Attaches.
TRAF TFP 3G PS Iu-PS Detach

Description Shows the number of GPRS Detaches.
TRAF TFP 3G PS Iu-PS GMM Cause in Unsuccessful GPRS Attach

Description Shows the number of unsuccessful GPRS Attaches for each GMM
Cause.
P-DN0687206 Id:0900d805807819d6 79
Issue 2-2
Probes
TRAF TFP 3G PS Iu-PS GMM Cause -> LAC

Description Shows the number of unsuccessful GPRS Attaches for each LAC for
each GMM Cause.
TRAF TFP 3G PS Iu-PS LACs in Attach

Description Shows the number of GPRS Attach attempts for each LAC.
TRAF TFP 3G PS Iu-PS Mobile Types in Attach

Description Shows the GPRS Attach attempts for each Mobile Type.
TRAF TFP 3G PS Iu-PS Mobile Types in PDP Context Activation

Description Shows the PDP Context Activation Attemps for each Mobile Type.
TRAF TFP 3G PS Iu-PS PDP Context Activations2

Description Shows the number of PDP Context Activations.
TRAF TFP 3G PS Iu-PS PDP Context Activations per SAC

Description Shows the number of attempted PDP Context Activations for each SAC.
TRAF TFP 3G PS Iu-PS PDP Context Deactivations

Description Shows the number of PDP Context Deactivations.
TRAF TFP 3G PS Iu-PS PDP Context Modifications

Description Shows the number of PDP Context Modifications.
TRAF TFP 3G PS Iu-PS SMSs

Description Shows the number of SMSs.
80 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
TRAF TFP 3G PS Iu-PS Successful RAUs

Description Shows the number of RAUs.
TRAF TFP 3G PS Iu-PS Unsuccessful GPRS Attach

Description Shows the percentage of GPRS Attaches that has GMM error code (Iu-
PS interface).
TRAF TFP 3G PS Iu-PS Unsuccessful GPRS Attaches per LAC

Description Shows the LACs for the unsuccessful GPRS Attaches.
TRAF TFP 3G PS Iu-PS Unsuccessful GPRS Attaches per LAC per GMM Cause
Description Shows the GMM Causes for the selected LAC.
TRAF TFP 3G PS Iu-PS Unsuccessful GPRS Detach

Description Shows the percentage of GPRS Detaches that has GMM error code (Iu-
PS interface).
TRAF TFP 3G PS Iu-PS Unsuccessful PDP Context Activation

Description Shows the percentage of PDP Context Activations that has Session
Management related error code (Iu-PS interface).
TRAF TFP 3G PS Iu-PS Unsuccessful PDP Context Activations per SAC

Description Shows the number of unsuccessful PDP Context Activations for each
SAC.
TRAF TFP 3G PS Iu-PS Unsuccessful PDP Context Activations per SAC per SM
SAC and for each SM Cause.
P-DN0687206 Id:0900d805807819d6 81
Issue 2-2
Probes
TRAF TFP 3G PS Iu-PS Unsuccessful PDP Context Activations per SM

SM Cause.
TRAF TFP 3G PS Iu-PS Unsuccessful PDP Context Deactivation

Description Shows the percentage of PDP Context Deactivations that has Session
TRAF TFP 3G PS Iu-PS Unsuccessful PDP Context Modification

Description Shows the percentage of PDP Contet Modifications that has Session
TRAF TFP 3G PS Iu-PS Unsuccessful RAU when active PDP Context

Description Shows the percentage of reported RAUs that has GMM or Session
Management error code (Iu-PS interface).
TRAF TFP 3G PS Iu-PS Unsuccessful SM Cause -> SAC

Description Shows the SACs for the selected SM Cause in Unsuccessful PDP
Context Activations.
TRAF TFP 3G PS Iu-PS Unsuccessful SMSs

Description Shows the percentage of unsuccessful 3G SMSs.
4.3.3.4 TRAF TFP Application Default graphs

TRAF TFP PS Application DIAMETER CC Bits Total
Description Average bandwidth (uplink + downlink) in selected timeclass
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application DIAMETER Failed RC Request Type

Description This graph shows the Request Types for the selected Result Code.
82 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application DIAMETER Failed RC Service Identifiers

Description This graph shows the Service Identifiers for the selected failed Result
Code.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application DIAMETER Failed RC -> Service Id -> GGSN

Description This graph shows the GGSN IPs for the selected Result Code and
Service identifiers.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application DIAMETER Failed RC -> Service Id -> Service IP

Description This graph shows the Peer2 addresses for selected result codes and
service identifiers.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application DIAMETER Failed Result Codes

Description This graph shows the Result Codes that are unequal to 2001 (Diameter
Success).
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application DIAMETER Failures

Description This graph shows the failure per cents for every Service Identifier. An
attempt is unsuccessful if the Result code is not empty value and not
Diameter success (2001).
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application DIAMETER Failures -> Result Codes

Description This graph shows the Result Codes for the Diameter Credit Control
Attempts for the selected Service Identifier.
PS APP, 30 Minutes
Version TFP PS v3.0
P-DN0687206 Id:0900d805807819d6 83
Issue 2-2
Probes
TRAF TFP PS Application DIAMETER Failure percent

Description This graph shows the failure percent for the Diameter Credit Control
messages. All messages with Result Code unequal to 2001 (Diameter
Success) is interpreted as failed.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application DIAMETER Initial Messages

Description This graph shows the number of Diameter Credit Control Initial Mes-
sages.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application DIAMETER Service Identifier

Description This graph shows the Service Identifier specific Diameter Credit Control
messages.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application DIAMETER Terminate Messages

Description This graph shows the number of Diameter Credit Control Terminate
messages.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application DIAMETER Total Count

Description This graph shows the total number of Diameter Credit Control mes-
sages.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application DIAMETER Update Messages

Description This graph shows the number of Diameter Credit Control Update Mes-
sages.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application DNS Bits IN

Description Bandwidth from internet to mobile network
84 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
TRAF TFP PS Application DNS Bits OUT

Description Bandwidth from mobile network to internet
TRAF TFP PS Application DNS Bits Total

TRAF TFP PS Application DNS Cause Codes

Description Cause code
TRAF TFP PS Application DNS Failure%

Description Failure % of DNS queries
TRAF TFP PS Application DNS IP

Description Report count per DNS
TRAF TFP PS Application DNS TCP Retransmit IN

Description TCP retransmit from internet to mobile network
TRAF TFP PS Application DNS TCP Retransmit OUT

Description TCP retransmit from mobile network to internet
TRAF TFP PS Application FTP Bits IN

TRAF TFP PS Application FTP Bits OUT

P-DN0687206 Id:0900d805807819d6 85
Issue 2-2
Probes
TRAF TFP PS Application FTP Bits Total

TRAF TFP PS Application FTP Cause Codes

TRAF TFP PS Application FTP Failure%

Description Failure % of FTP transactions
TRAF TFP PS Application FTP IP

Description Report count per FTP server
TRAF TFP PS Application FTP Retransmit OUT

TRAF TFP PS Application FTP TCP Retransmit IN

TRAF TFP PS Application HTTP 4xx cause

Description Cause code. Client error
TRAF TFP PS Application HTTP 5xx Cause

Description Cause code. Server error
TRAF TFP PS Application HTTP Bits IN

86 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
TRAF TFP PS Application HTTP Bits OUT

TRAF TFP PS Application HTTP Bits Total

TRAF TFP PS Application HTTP Failure%

Description Failure % of HTTP transactions
TRAF TFP PS Application IMAP Bits IN

TRAF TFP PS Application IMAP Bits OUT

TRAF TFP PS Application IMAP Bits Total

TRAF TFP PS Application IMAP Failure%

Description Failure % of IMAP transactions
TRAF TFP PS Application IMAP IP

Description Report count per IMAP server
TRAF TFP PS Application IMAP TCP Retransmit IN

P-DN0687206 Id:0900d805807819d6 87
Issue 2-2
Probes
TRAF TFP PS Application IMAP TCP Retransmit OUT

TRAF TFP PS Application MMS Bits IN

TRAF TFP PS Application MMS Bits OUT

TRAF TFP PS Application MMS Bits Total

TRAF TFP PS Application MMS Cause Codes

TRAF TFP PS Application MMS Failure%

Description Failure % of MMS transactions
TRAF TFP PS Application MMS IP

Description Report count per MMS server
TRAF TFP PS Application MMS TCP Retransmit IN

TRAF TFP PS Application MMS TCP Retransmit OUT

88 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
TRAF TFP PS Application POP3 Bits IN

TRAF TFP PS Application POP3 Bits OUT

TRAF TFP PS Application POP3 Bits Total

TRAF TFP PS Application POP3 Failure%

Description Failure % of POP3 transactions
TRAF TFP PS Application POP3 IP

Description Report count per POP3 server
TRAF TFP PS Application POP3 TCP Retransmit IN

TRAF TFP PS Application POP3 TCP Retransmit OUT

TRAF TFP PS Application RADIUS Bits IN

TRAF TFP PS Application RADIUS Bits OUT

P-DN0687206 Id:0900d805807819d6 89
Issue 2-2
Probes
TRAF TFP PS Application RADIUS Bits Total

TRAF TFP PS Application RADIUS Failure%

Description Failure % of RADIUS transactions
TRAF TFP PS Application RADIUS IP

Description Report count per RADIUS server
TRAF TFP PS Application RADIUS TCP Retransmit IN

TRAF TFP PS Application RADIUS TCP Retransmit OUT

TRAF TFP PS Application RTSP Bits IN

TRAF TFP PS Application RTSP Bits OUT

TRAF TFP PS Application RTSP Bits Total

TRAF TFP PS Application RTSP Cause Codes

90 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
TRAF TFP PS Application RTSP Failure%

Description Failure % of RTSP transactions
TRAF TFP PS Application RTSP IP

Description Report count per RTSP server
TRAF TFP PS Application RTSP Failure percents

Description This graph shows the failure percent for each RTSP Service IP. 10
values is required before showing any values.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application RTSP Failured

Description This graph shows the number of reports with RTSP Status 4xx or 5xx.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application RTSP Method Failure percent

Description This graph shows the failure percent for the selected RTSP Service IP.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application RTSP Method Methods

Description This graph shows which methods was failed for selected RTSP Service
IP.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application RTSP Method Methods Status

Description This graph shows the Method Statuses for the failing selected Method
for the selected RTSP Service IP.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application RTSP Method Service Failures

Description This graph shows the number of reports with RTSP Status 4xx or 5xx.
P-DN0687206 Id:0900d805807819d6 91
Issue 2-2
Probes
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application RTSP Method Sessions

Description This graph shows for each RTSP Service IP the number of RTSP
Sessions by showing the number of reports with Method = 'Describe'.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application RTSP Method Statuses

Description This graph shows the failing statuses for selected RTSP Service IP.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application RTSP Method Statuses Method

Description This graph shows which methods initiated the selected errors (failing
RTSP method status) in selected RTSP Service IP.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application RTSP Methods

Description This graph shows the number of RTSP method reports for each RTSP
Service IP.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application RTSP Response Statuses

Description This graph shows all RTSP Response Statuses reported for the open
node specified RTSP Service IPs.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application RTSP Status IP

Description This graph shows the IP addresses connected to the RTSP method
reports with selected Response Status. IP addresses are Open Node
limited.
PS APP, 30 Minutes
Version TFP PS v3.0
92 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
TRAF TFP PS Application RTSP Status IP Method

Description This graph shows the Methods reported for the selected Response
Status and Service IP.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application RTSP Status Method

Description This graph shows the methods used with selected RTSP Response
Status.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application RTSP Status method IP

Description This graph shows the RTSP Service IPs for the selected RTSP Method
and RTSP Status.
PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application RTSP QoS DL Audio Average MOS

Description This graph shows the average of the average MOS values for Audio
downlink. RTSP Service IPs are Open Node limited.
Version TFP PS v3.0
TRAF TFP PS Application RTSP QoS DL Audio Min MOS

Description This graph shows the average of the minimum MOS values for Audio
Version TFP PS v3.0
TRAF TFP PS Application RTSP QoS DL Video Average MOS

Description This graph shows the average of the average MOS values for Video
Version TFP PS v3.0
TRAF TFP PS Application RTSP QoS DL Video Min MOS

Description This graph shows the average of the min MOS values for Video down-
link. RTSP Service IPs are Open Node limited.
Version TFP PS v3.0
P-DN0687206 Id:0900d805807819d6 93
Issue 2-2
Probes
TRAF TFP PS Application RTSP QoS DL Volumes

Description This graph shows the data volumes for each RTSP Service IP. RTSP
Service IPs are Open Node limited.
Version TFP PS v3.0
TRAF TFP PS Application RTSP QoS Report Count

Description This graph shows the report count for each RTSP Service IP. RTSP
Service IPs are Open Node limited.
Version TFP PS v3.0
TRAF TFP PS Application RTSP TCP Retransmit IN

TRAF TFP PS Application RTSP TCP Retransmit OUT

TRAF TFP PS Application SIP Bits Total

PS APP, 30 Minutes
Version TFP PS v3.0
TRAF TFP PS Application SIP Audio MOS

Description This graph shows the average of the average MOS values in SIP Audio
traffic for each GGSN.
Version TFP PS v3.0
TRAF TFP PS Application SIP Data Volumes

Description This graph shows the data volumes in SIP traffic for each GGSN.
Version TFP PS v3.0
TRAF TFP PS Application SIP Failures

Description This graph shows the SIP failed method reports. Failed method here is
SIP method report with error code or without a reply.
Version TFP PS v3.0
94 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
TRAF TFP PS Application SIP Method Reports

Description This graph shows the number of SIP Method Reports for each GGSN.
Version TFP PS v3.0
TRAF TFP PS Application SIP Min Audio MOS

Description This graph shows the average of the min MOS values in SIP Audio
Version TFP PS v3.0
TRAF TFP PS Application SIP Min Video MOS

Description This graph shows the average of the min MOS values in SIP Video
Version TFP PS v3.0
TRAF TFP PS Application SIP No Reply

Description This graph shows the number of SIP Method reports with no reply for
the selected GGSN.
Version TFP PS v3.0
TRAF TFP PS Application SIP Report Count

Description This graph shows the number of SIP QoS reports.
Version TFP PS v3.0
TRAF TFP PS Application SIP Sessions

Description This graph shows the SIP Sessions for each GGSN. SIP Sessions are
calculated as the number of Invite Methods with Status 200 (OK).
Version TFP PS v3.0
TRAF TFP PS Application SIP Statuses

Description This graph shows the Error status codes for the selected GGSN for all
other SIP Methods except Registrations.
Version TFP PS v3.0
TRAF TFP PS Application SIP Unsuccessful Registrations

Description This graph shows the error codes for the unsuccessful registrations for
the selected GGSN.
Version TFP PS v3.0
P-DN0687206 Id:0900d805807819d6 95
Issue 2-2
Probes
TRAF TFP PS Application SIP Video MOS

Description This graph shows the average of the average MOS values in SIP Video
Version TFP PS v3.0
TRAF TFP PS Application SMTP Bits IN

TRAF TFP PS Application SMTP Bits OUT

TRAF TFP PS Application SMTP Bits Total

TRAF TFP PS Application SMTP Cause Codes

TRAF TFP PS Application SMTP Failure%

Description Failure % of SMTP transactions
TRAF TFP PS Application SMTP TCP Retransmit IN

TRAF TFP PS Application SMTP TCP Retransmit OUT

TRAF TFP PS Application WAP Bits IN

96 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Probes
TRAF TFP PS Application WAP Bits OUT

TRAF TFP PS Application WAP Bits Total

TRAF TFP PS Application WAP Failure%

Description Failure % of WAP transactions
TRAF TFP PS Application WAP Get Reason

TRAF TFP PS Application WAP Post Reason

4.3.3.5 TRAF TFP PS Flow Default graphs

TRAF TFP PS Flow Bits IN
TRAF TFP PS Flow Bits OUT

TRAF TFP PS Flow Count

Description Number of flows
TRAF TFP PS Flow Delay

Description Average delay (TCP handshake delay)
P-DN0687206 Id:0900d805807819d6 97
Issue 2-2
Probes
TRAF TFP PS Flow Ports

Description Total bandwidth on TCP/UDP port. Including ports 0-5300 and 8080.
TRAF TFP PS Flow TCP Retransmit Average Delay

Description Average delay (TCP handshake delay)
TRAF TFP PS Flow TCP Retransmit Bits IN

TRAF TFP PS Flow TCP Retransmit Bits OUT

TRAF TFP PS Flow TCP Retransmit Count

Description Number of flows
TRAF TFP PS Flow TCP Retransmit IN

TRAF TFP PS Flow TCP Retransmit OUT

TRAF TFP PS Flow TCP Retransmit Ports

Description Total TCP retransmit per port, Including ports 0-5300 and 8080.
98 Id:0900d805807819d6 P-DN0687206
Issue 2-2
Traffica Reference Guide for 2G/3G Packet Core RTT Report descriptions
Probes
5 RTT Report descriptions
5.1 Application report fields

This chapter lists the fields in the Application report.
5.1.1 General application report fields

This chapter lists the application report fields that are common for all application report
types. For information on fields specific to each application, see the following chapters:
• Diameter Credit Control specific fields
• DNS specific fields
• FTP specific fields
• HTTP specific fields
• IMAP specific fields
• MMS specific fields
• POP3 specific fields
• RADIUS Authentication specific fields
• RTSP v2.0 specific fields
• RTSP Method specific fields
• RTSP QoS specific fields
• SIP Method specific fields
• SIP QoS specific fields
• SMTP specific fields
• WAP specific fields
The database column names are the same as the IDS field names without the
TFP_<Application>_ prefix. For example, the TFP_FTP_User_Name IDS field is the
User Name column in the database table TFP_FTP_<TFP_Release_Id>_REPORT.
The Traffic News field names are the same as the database column names but use
spaces instead of underscores between words. For example, the
TFP_FTP_User_Name IDS field is the User Name field in the Traffic News TFP PS FTP
event.
The database column SQL data types can be found in the workspace configuration file
dbd_*.conf. Under the TFP_<Application>_<TFP_Release_Id>_REPORT section,
there is a single-row entry for each table column. The SQL data type appears after the
column name and “=” symbol.
Traffic News Event type TFP PS FTP

Database table TFP_FTP_<TFP_Release_Id>_REPORT
Table 4 TFP_<Application> database table naming convention
g <Application> indicates the application-specific label. It can be DIAMETER_CC

(Diameter Credit Control), DNS, FTP, HTTP, IMAP, MMS, POP3, RADIUS (Note:
RADIUS in this context refers to RADIUS Authentication), RTSP, SIP, SMTP, or
WAP.
The general application report RTT fields are the following:
P-DN0687206 Id:0900d805807819d6 99
Issue 2-2
RTT Report descriptions Traffica Reference Guide for 2G/3G Packet Core
Probes
TFP_<Application>_APN
Field name TFP_<Application>_APN
Datatype in IDS CHAR(102)
Versions TFP PS v3.0
Explanation Access Point Name as a string.
Possible values
Exists in db Yes
CCD section
TFP_<Application>_Application_Id
Field name TFP_<Application>_Application_Id
Datatype in IDS UINT16
Versions TFP PS v2.0, TFP PS v3.0
Explanation Check the ID from the separate protocol number list in Appendix B: Pro-
tocols.
Possible values
Exists in db Yes
CCD section [Application]
TFP_<Application>_Bytes_IN
Field name TFP_<Application>_Bytes_IN
Explanation Downlink byte count related to the report. IP header is included.
g This field will be taken out of use and replaced with the field
TFP_<Application>_Bytes_IN_Ext, in order to support larger
Bytes IN values in the future. Therefore it is recommended that the
TFP_<Application>_Bytes_IN_Ext field be used instead.
Possible values
Exists in db Yes
CCD section
TFP_<Application>_Bytes_IN_Ext
Field name TFP_<Application>_Bytes_IN_Ext
Explanation Downlink byte count related to the report. IP header is included.
Possible values
Exists in db Yes
CCD section
TFP_<Application>_Bytes_OUT
Field name TFP_<Application>_Bytes_OUT
100 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Explanation Uplink byte count related to the report. IP header is included.
TFP_<Application>_Bytes_OUT_Ext, in order to support larger
Bytes OUTvalues in the future. Therefore it is recommended that
the TFP_<Application>_Bytes_OUT_Ext field be used instead.
Possible values
Exists in db Yes
CCD section
TFP_<Application>_Bytes_OUT_Ext
Field name TFP_<Application>_Bytes_OUT_Ext
Explanation Uplink byte count related to the report. IP header is included.
Possible values
Exists in db Yes
CCD section
TFP_<Application>_Delay
Field name TFP_<Application>_Delay
Explanation Delay of first TCP reply (in milliseconds)
Possible values
Exists in db Yes
CCD section
TFP_<Application>_Direct_Tunnel
Field name TFP_<Application>_Direct_Tunnel
Explanation 0 = no direct tunnel
1 = direct tunnel
Possible values 0, 1
Exists in db Yes
CCD section [Direct Tunnel indicator]
TFP_<Application>_GGSN
Field name TFP_<Application>_GGSN
P-DN0687206 Id:0900d805807819d6 101

Issue 2-2
Probes
Explanation Logical field indicating GGSN identification number. Fixed number for
each GGSN.
Possible values Predefined.
Exists in db Yes
CCD section
TFP_<Application>_GGSN_Address_For_User_Traffic
Field name TFP_<Application>_GGSN_Address_For_User_Traffic
Datatype in IDS IPADDR(16)
Explanation IP address of GGSN interface which is monitored
Possible values Correlated. IPv4 or IPv6 address.
Exists in db Yes
CCD section
TFP_<Application>_Imei
Field name TFP_<Application>_Imei
Datatype in IDS BCD8(8)
Explanation International Mobile Equipment Identity
Possible values Correlated.
Exists in db Yes
CCD section
TFP_<Application>_Imsi
Field name TFP_<Application>_Imsi
Explanation International Mobile Subscriber Identity (IMSI), BCD string content
(length in digits): MCC(3) + MNC(2-3) + MSIN. Total length is not more
than 15 digits.
Exists in db Yes
CCD section
TFP_<Application>_Interface
Field name TFP_<Application>_Interface
Explanation probe monitoring interface. 1=Gi, 2=Gn, 3=Gp, 4=Gb, 5= Iu-PS
Exists in db Yes
CCD section
102 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_<Application>_MCC_MNC
Field name TFP_<Application>_MCC_MNC
Explanation MCC and MNC in one field. 3 digits for MCC and max 3 digits for MNC.
Possible values Max 6 digits
Exists in db Yes
CCD section
TFP_<Application>_Messaging_End_Time_Local_Date
Field name TFP_<Application>_Messaging_End_Time_Local_Date
Datatype in IDS BCDDATE
Explanation Local time and date in BCDTIMESTAMP format. Last packet in connec-
tion.
Possible values Date
Exists in db Yes
CCD section
TFP_<Application>_Messaging_End_Time_Local_Time
Field name TFP_<Application>_Messaging_End_Time_Local_Time
Datatype in IDS BCDTime
Explanation Local time and date in BCDTIMESTAMP format.
Possible values Time
Exists in db Yes
CCD section
TFP_<Application>_Messaging_Start_Time_Local_Date
Field name TFP_<Application>_Messaging_Start_Time_Local_Date
Explanation Local time and date in BCDTIMESTAMP format. First packet which ini-
tiated the connection.
Exists in db Yes
CCD section
TFP_<Application>_Messaging_Start_Time_Local_Time
Field name TFP_<Application>_Messaging_Start_Time_Local_Time
P-DN0687206 Id:0900d805807819d6 103

Issue 2-2
Probes
Explanation Local time and date in BCDTIMESTAMP format.

Exists in db Yes
CCD section
TFP_<Application>_Mobile_IP_Address
Field name TFP_<Application>_Mobile_IP_Address
Explanation IP address of mobile
Possible values IPv4 or IPv6 address.
Exists in db Yes
CCD section
TFP_<Application>_MSISDN
Field name TFP_<Application>_MSISDN
Explanation MSISDN of the user.
Possible values
Exists in db Yes
CCD section
TFP_<Application>_NSAPI
Field name TFP_<Application>_NSAPI
Explanation Network layer service access point identifier.
Possible values
Exists in db Yes
CCD section
TFP_<Application>_Packets_IN
Field name TFP_<Application>_Packets_IN
Explanation Downlink IP packet count related to the report.
TFP_<Application>_Packets_IN_Ext, in order to support larger
Packets IN values in the future. Therefore it is recommended that
the TFP_<Application>_Packets_IN_Ext field be used instead.
Possible values
Exists in db Yes
104 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
CCD section
TFP_<Application>_Packets_IN_Ext
Field name TFP_<Application>_Packets_IN
Explanation Downlink IP packet count related to the report
Possible values
Exists in db Yes
CCD section
TFP_<Application>_Packets_OUT
Field name TFP_<Application>_Packets_OUT
Explanation Uplink IP packet count related to the report
TFP_<Application>_Packets_OUT_Ext, in order to support larger
Packets OUT values in the future. Therefore it is recommended that
the TFP_<Application>_Packets_OUT_Ext field be used instead.
Possible values
Exists in db Yes
CCD section
TFP_<Application>_Packets_OUT_Ext
Field name TFP_<Application>_Packets_OUT_Ext
Explanation Uplink IP packet count related to the report.
Possible values
Exists in db Yes
CCD section
TFP_<Application>_PDP_Context_Activation_Date
Field name TFP_<Application>_PDP_Context_Activation_Date
Explanation Timestamp (local time) for Activate PDP Context Accept.
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 105

Issue 2-2
Probes
TFP_<Application>_PDP_Context_Activation_Time
Field name TFP_<Application>_PDP_Context_Activation_Time
Datatype in IDS BCDTIME
Possible values
Exists in db Yes
CCD section
TFP_<Application>_RAN
Field name TFP_<Application>_RAN
Explanation Logical field indicating RAN identification number.
Possible values
Exists in db Yes
CCD section
TFP_<Application>_RAN_Address_for_User_Traffic
Field name TFP_<Application>_RAN_Address_for_User_Traffic
Explanation RAN address for user traffic in case of direct tunnel.
Possible values IPv4 or IPv6 address
Exists in db Yes
CCD section
TFP_<Application>_RAT_Type
Field name TFP_<Application>_RAT_Type
Explanation 1 = UTRAN, 2 = GERAN, 3 = WLAN. RAT value is correlated when
application session starts (New RAT during application session does
not affect this field)
Exists in db Yes
CCD section [RAT Type]
TFP_<Application>_Report_Count
Field name TFP_<Application>_Report_Count
106 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Explanation The number of application reports sent to Traffica after midnight.

Report_Count is specific to report type and Traffica connection. Reset
at midnight. Starting from one. Little-Endian byte order used.
Possible values
Exists in db Yes
CCD section
TFP_<Application>_Report_Date
Field name TFP_<Application>_Report_Date
Explanation Report sending local time and date in BCDTIMESTAMP format.
Possible values
Exists in db Yes
CCD section
TFP_<Application>_Report_Id
Field name TFP_<Application>_Report_Id
Explanation Report ID.
Exists in db Yes
CCD section [Report Id]
TFP_<Application>_Report_Reason
Field name TFP_<Application>_Report_Reason
Explanation Reason for sending report. See triggering rules in chapter Report gen-
eration rules.
Possible values
Exists in db Yes
CCD section [Report Reason]
TFP_<Application>_Report_Time
Field name TFP_<Application>_Report_Time
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 107

Issue 2-2
Probes
TFP_<Application>_Report_UTC_Date
Field name TFP_<Application>_Report_UTC_Date
Explanation Report sending UTC time and date in BCDTIMESTAMP format.
Possible values
Exists in db Yes
CCD section
TFP_<Application>_Report_UTC_Time
Field name TFP_<Application>_Report_UTC_Time
Exists in db Yes
CCD section
TFP_<Application>_Reserved_1
Field name TFP_<Application>_Reserved_1
Explanation Reserved for future use.
Possible values
Exists in db Yes
CCD section
TFP_<Application>_Reserved_2
Field name TFP_<Application>_Reserved_2
Possible values
Exists in db Yes
CCD section
TFP_<Application>_Sampling_Rate
Field name TFP_<Application>_Sampling_Rate
Explanation Application report sampling rate. Default value is 1. Each application
has own sampling rate. See Appendix C: Variables.
108 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Exists in db Yes
CCD section
TFP_<Application>_Sender_Id
Field name TFP_<Application>_Sender_Id
Explanation Sender ID number. Little-Endian byte order used.
Exists in db Yes
CCD section
TFP_<Application>_Service_IP_Address
Field name TFP_<Application>_Service_IP_Address
Explanation IP Address for the service (e.g. HTTP server IP)
Exists in db Yes
CCD section
TFP_<Application>_Service_Port
Field name TFP_<Application>_Service_Port
Explanation TCP or UDP port of the service
Possible values
Exists in db Yes
CCD section
TFP_<Application>_SGSN
Field name TFP_<Application>_SGSN
Explanation Logical field indicating SGSN identification number. Fixed number for
each SGSN.
Exists in db Yes
CCD section
TFP_<Application>_SGSN_Address_For_User_Traffic
Field name TFP_<Application>_SGSN_Address_For_User_Traffic
P-DN0687206 Id:0900d805807819d6 109

Issue 2-2
Probes

Explanation IP Address for SGSN (from GGSN point of view) used for user traffic
Possible values Correlated. IPv4 or IPv6 address.
Exists in db Yes
CCD section
TFP_<Application>_TCP_Retransmit_IN
Field name TFP_<Application>_TCP_Retransmit_IN
Explanation Retransmits in TCP downlink connections counted from TCP headers;
the number of incoming TCP packets with the same Sequence Number
field.
Possible values
Exists in db Yes
CCD section
TFP_<Application>_TCP_Retransmit_OUT
Field name TFP_<Application>_TCP_Retransmit_OUT
Explanation Retransmits in TCP uplink connections counted from TCP headers; the
number of outgoing TCP packets with the same Sequence Number
field.
Possible values
Exists in db Yes
CCD section
TFP_<Application>_Vendor_Id
Field name TFP_<Application>_Vendor_Id
Explanation Vendor ID is specified by Nokia Siemens Networks. Little-Endian byte
order used.
Exists in db Yes
CCD section [Vendor ID]
5.1.2 Diameter Credit Control specific fields

TFP_DIAMETER_Called_Station_Id
Field name TFP_DIAMETER_Called_Station_Id
110 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Explanation Contains an identifier of the access point which the user is connected
to. Can be a logical number or access point name (limited to 30 char-
acters). This AVP is defined in [RFC2865] and it is present in initial CCR
only.
Possible values
Exists in db Yes
CCD section
TFP_DIAMETER_Destination_Host
Field name TFP_DIAMETER_Destination_Host
Explanation From the Destination-Host field in a request or the Origin-Host field in
an answer.
Possible values
Exists in db Yes
CCD section
TFP_DIAMETER_Destination_Realm
Field name TFP_DIAMETER_Destination_Realm
Explanation From the Destination-Realm field in a request.
Possible values
Exists in db Yes
CCD section
TFP_DIAMETER_DIAMETER_Reserved_1
Field name TFP_DIAMETER_DIAMETER_Reserved_1
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 111

Issue 2-2
Probes
Possible values
Exists in db Yes
CCD section
Possible values
Exists in db Yes
CCD section
TFP_DIAMETER_Framed_IP_Address
Field name TFP_DIAMETER_Framed_IP_Address
Explanation Framed IP Address. Present only in initial CCR. Contains the mobile IP
address. This AVP is defined in [RFC2865] for IPv4 and [RFC3162] for
IPv6. Data type IPADDR is used in both cases.
Possible values
Exists in db Yes
CCD section
TFP_DIAMETER_Origin_Host
Field name TFP_DIAMETER_Origin_Host
Explanation From the Origin-Host field in a request.
Possible values
Exists in db Yes
CCD section
TFP_DIAMETER_Rating_Group
Field name TFP_DIAMETER_Rating_Group
Explanation The Rating Group to which a service belongs. From Multiple-Services-
Credit-Control field AVP Rating-Group.
Possible values
Exists in db Yes
CCD section
112 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_DIAMETER_Request_Type
Field name TFP_DIAMETER_Request_Type
Explanation Credit Control Request Type. From Credit Control Request. Enumer-
ated: 1=Initiate, 2=Update, 3=Terminate.
Possible values
Exists in db Yes
CCD section [Diameter Request Type]
TFP_DIAMETER_Result_Code
Field name TFP_DIAMETER_Result_Code
Explanation If the Result-Code on the command level indicates a value other than
SUCCESS, it is provided. If that is SUCCESS, the Multiple-Services-
Credit-Control AVP Result-Code is provided if available.
Possible values
Exists in db Yes
CCD section [Diameter Result Code]
TFP_DIAMETER_Service_Identifier
Field name TFP_DIAMETER_Service_Identifier
Explanation A numeric identifier for a service as determined by the user profile and
the service configuration. Identifies the service for which a quota is
being granted. From Multiple-Services-Credit-Control field AVP
Service-Identifier.
Possible values
Exists in db Yes
CCD section
TFP_DIAMETER_Session_Id
Field name TFP_DIAMETER_Session_Id
Explanation Session-id in string format, as follows: <host name>;<context creation
time>;<context teid> The field <context creation time> specifies the
point in time when the context was created in seconds from 1970. In the
signaling this is on each CCR and CCA.
Possible values
Exists in db Yes
P-DN0687206 Id:0900d805807819d6 113

Issue 2-2
Probes
CCD section
TFP_DIAMETER_Termination_Cause
Field name TFP_DIAMETER_Termination_Cause
Explanation From the final Credit Control Request (CC-Request_Type =
TERMINATION_REQUEST)
Possible values
Exists in db Yes
CCD section [Diameter Termination Cause]
TFP_DIAMETER_Username
Field name TFP_DIAMETER_Username
Explanation From the User-Name field
Possible values
Exists in db Yes
CCD section
5.1.3 DNS specific fields

TFP_DNS_Cause_Code
Field name TFP_DNS_Cause_Code
Explanation DNS Rcode.
Possible values
Exists in db Yes
CCD section [DNS Cause Code]
TFP_DNS_Question_Name
Field name TFP_DNS_Question_Name
Explanation Question name from DNS question section.
Possible values
Exists in db Yes
CCD section
TFP_DNS_Resolved_IP_Address
Field name TFP_DNS_Resolved_IP_Address
114 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Datatype in IDS IPADDR

Explanation IP Address that is resolved from the Question name.
Possible values
Exists in db Yes
CCD section
5.1.4 FTP specific fields

TFP_FTP_Error_Reason_1
Field name TFP_FTP_Error_Reason_1
Explanation Error reason for failed command (4xx-5xx)
Possible values 4xx-5xx
Exists in db Yes
CCD section [FTP Cause Code]
TFP_FTP_Error_Reason_2
Field name TFP_FTP_Error_Reason_2
Explanation Error reason for failed command
Possible values 4xx-5xx
Exists in db Yes
CCD section [FTP Cause Code]
TFP_FTP_Failed_Command_1
Field name TFP_FTP_Failed_Command_1
Explanation Name of the command which failed
Possible values
Exists in db Yes
CCD section
TFP_FTP_Failed_Command_2
Field name TFP_FTP_Failed_Command_2
Explanation Name of the command which failed.
Possible values
P-DN0687206 Id:0900d805807819d6 115

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_FTP_Files_Transferred
Field name TFP_FTP_Files_Transferred
Explanation Number of files transferred successfully
Possible values
Exists in db Yes
CCD section
TFP_FTP_FTP_Reserved_1
Field name TFP_FTP_FTP_Reserved_1
Possible values N/A
Exists in db Yes
CCD section
TFP_FTP_FTP_Reserved_2
Field name TFP_FTP_FTP_Reserved_2
Possible values N/A
Exists in db Yes
CCD section
TFP_FTP_Passive
Field name TFP_FTP_Passive
Explanation 1=passive mode used, 2= no passive mode used
Exists in db Yes
CCD section [FTP passive mode]
TFP_FTP_User_Name
Field name TFP_FTP_User_Name
116 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Explanation Argument of 'USER NAME'-command

Possible values
Exists in db Yes
CCD section
5.1.5 HTTP specific fields

TFP_HTTP_1xx_First_SC
Field name TFP_HTTP_1xx_First_SC
Explanation First 1xx status code.
Possible values
Exists in db Yes
CCD section [HTTP Cause Code]
TFP_HTTP_1xx_Responses
Field name TFP_HTTP_1xx_Responses
Explanation Number of 1xx status code responses within report.
Possible values
Exists in db Yes
CCD section
Possible values
Exists in db Yes
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 117

Issue 2-2
Probes
Possible values
Exists in db Yes
Possible values
Exists in db Yes
CCD section
Possible values
Exists in db Yes
Possible values
Exists in db Yes
CCD section
Possible values
118 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Exists in db Yes
Possible values
Exists in db Yes
CCD section
TFP_HTTP_Average_Delay
Field name TFP_HTTP_Average_Delay
Explanation Average delay in milliseconds of succesful responses to HTTP GET
messages.
Possible values
Exists in db Yes
CCD section
TFP_HTTP_Cause_Code
Field name TFP_HTTP_Cause_Code
Explanation Status code of first HTTP reply.
Possible values
Exists in db Yes
TFP_HTTP_First_URL
Field name TFP_HTTP_First_URL
Explanation First URL requested by the user.
Possible values
Exists in db Yes
CCD section
TFP_HTTP_GET_Messages
Field name TFP_HTTP_GET_Messages
P-DN0687206 Id:0900d805807819d6 119

Issue 2-2
Probes

Explanation Number of GET messages within report.
Possible values
Exists in db Yes
CCD section
TFP_HTTP_Host
Field name TFP_HTTP_Host
Explanation Name of WWW server. For example:
www.nokiasiemensnetworks.com.
Possible values
Exists in db Yes
CCD section
TFP_HTTP_HTTP_Reserved_1
Field name TFP_HTTP_HTTP_Reserved_1
Possible values
Exists in db Yes
CCD section
TFP_HTTP_Referer
Field name TFP_HTTP_Referer
Explanation From HTTP message header(not always available). Method name is
not included in the report (In this case text: "Referer:" is not included).
Referer is got from first GET message.
Possible values
Exists in db Yes
CCD section
TFP_HTTP_User_Agent
Field name TFP_HTTP_User_Agent
Explanation From HTTP message header. Method name is not included.
Possible values
120 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_HTTP_Version
Field name TFP_HTTP_Version
Explanation From HTTP GET message. 1 = 1.0, 2 = 1.1
Possible values 1 = 1.0, 2 = 1.1
Exists in db Yes
CCD section [HTTP Version]
5.1.6 IMAP specific fields

TFP_IMAP_Err_Command_1
Field name TFP_IMAP_Err_Command_1
Explanation Command which caused Bad or No response
Possible values
Exists in db Yes
CCD section
TFP_IMAP_Err_Command_2
Field name TFP_IMAP_Err_Command_2
Explanation Command which caused Bad or No response
Possible values
Exists in db Yes
CCD section
TFP_IMAP_Err_Response_1
Field name TFP_IMAP_Err_Response_1
Explanation Response text to TFP_IMAP_Err_Command_1.
Possible values
Exists in db Yes
CCD section
TFP_IMAP_Err_Response_2
Field name TFP_IMAP_Err_Response_2
P-DN0687206 Id:0900d805807819d6 121

Issue 2-2
Probes

Explanation Response text to TFP_IMAP_Err_Command_2.
Possible values
Exists in db Yes
CCD section
TFP_IMAP_IMAP_Reserved_1
Field name TFP_IMAP_IMAP_Reserved_1
Explanation Reserved for future use
Possible values
Exists in db Yes
CCD section
TFP_IMAP_Mail_Count
Field name TFP_IMAP_Mail_Count
Explanation number of mails retrieved during session
Possible values
Exists in db Yes
CCD section
TFP_IMAP_User_Name
Field name TFP_IMAP_User_Name
Explanation Login user name if available
Possible values
Exists in db Yes
CCD section
5.1.7 MMS specific fields

TFP_MMS_Content_Class
Field name TFP_MMS_Content_Class
Explanation MMS content class.
122 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Possible values 1 = text, 2 = image-basic, 3 = image-rich, 4 = video-basic, 5 = video-

rich, 6 = megapixel, 7 = content-basic, 8 = content-rich
Exists in db Yes
CCD section [MMS Content Class]
TFP_MMS_Content_Type
Field name TFP_MMS_Content_Type
Explanation Assigned number. For more information, see Appendix F: Content
types.
Possible values
Exists in db Yes
CCD section [MMS Content Type]
TFP_MMS_Content_URI
Field name TFP_MMS_Content_URI
Explanation From Content-Location header field.
Possible values
Exists in db Yes
CCD section
TFP_MMS_From
Field name TFP_MMS_From
Explanation See OMA-TS-MMS-ENC-V1_3.
Possible values
Exists in db Yes
CCD section
TFP_MMS_Message_Id
Field name TFP_MMS_Message_Id
Explanation According to RFC2822.
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 123

Issue 2-2
Probes
TFP_MMS_Message_Size
Field name TFP_MMS_Message_Size
Explanation Bytes. From MM notification header. Calculated in case of send MMS.
Possible values
Exists in db Yes
CCD section
TFP_MMS_Recipient_Count
Field name TFP_MMS_Recipient_Count
Explanation Number of recipients (To+Cc+Bcc).
Possible values
Exists in db Yes
CCD section
TFP_MMS_Response_Status
Field name TFP_MMS_Response_Status
Explanation See Appendix A: Cause codes.
Possible values
Exists in db Yes
CCD section [MMS Reponse Status]
TFP_MMS_Status
Field name TFP_MMS_Status
Explanation MMS status.
Possible values 1 = Expired, 2 = Retrieved, 3 = Rejected, 4 = Deferred, 5 = Unrecog-
nised, 6 = Indeterminate, 7 = Forwarded, 8 = Unreachable
Exists in db Yes
CCD section [MMS Status]
TFP_MMS_To_1
Field name TFP_MMS_To_1
Explanation If To-field is empty, then first Cc or Bcc value is put to this field.
124 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Possible values
Exists in db Yes
CCD section
TFP_MMS_To_2
Explanation Next address in the To-field. If the next To-field is empty, then the next
Cc or Bcc value is put in this field.
Possible values
Exists in db Yes
CCD section
TFP_MMS_To_3
Possible values
Exists in db Yes
CCD section
TFP_MMS_To_4
Possible values
Exists in db Yes
CCD section
TFP_MMS_To_5
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 125

Issue 2-2
Probes
TFP_MMS_Transaction_Id
Field name TFP_MMS_Transaction_Id
Possible values
Exists in db Yes
CCD section
TFP_MMS_User_Agent
Field name TFP_MMS_User_Agent
Explanation From WSP/HTTP message header. Method name is not included.
Possible values
Exists in db Yes
CCD section
TFP_MMS_Version
Field name TFP_MMS_Version
Possible values
Exists in db Yes
CCD section [MMS Version]
5.1.8 POP3 specific fields

TFP_POP3_Err_Command_1
Field name TFP_POP3_Err_Command_1
Explanation Command which caused -ERR reply
Possible values
Exists in db Yes
CCD section
TFP_POP3_Err_Command_2
Field name TFP_POP3_Err_Command_2
126 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Explanation Command which caused -ERR reply

Possible values
Exists in db Yes
CCD section
TFP_POP3_Err_Response_1
Field name TFP_POP3_Err_Response_1
Explanation Response text to TFP_POP3_Err_Command_1.
Possible values
Exists in db Yes
CCD section
TFP_POP3_Err_Response_2
Field name TFP_POP3_Err_Response_2
Explanation Response text to TFP_POP3_Err_Command_2.
Possible values
Exists in db Yes
CCD section
TFP_POP3_Mail_Count
Field name TFP_POP3_Mail_Count
Explanation number of mails retrieved during session
Possible values
Exists in db Yes
CCD section
TFP_POP3_POP3_Reserved_1
Field name TFP_POP3_POP3_Reserved_1
Possible values
Exists in db Yes
CCD section
TFP_POP3_User_Name
Field name TFP_POP3_User_Name
P-DN0687206 Id:0900d805807819d6 127

Issue 2-2
Probes

Explanation Login user name if available.
Possible values
Exists in db Yes
CCD section
5.1.9 RADIUS Authentication specific fields

TFP_RADIUS_3GPP-Charging-Id
Field name TFP_RADIUS_3GPP-Charging-Id
Explanation RADIUS attribute 26. Vendor code 10415(3GPP).
Possible values
Exists in db Yes
CCD section
TFP_RADIUS_3GPP-GGSN-Address
Field name TFP_RADIUS_3GPP-GGSN-Address
Possible values
Exists in db Yes
CCD section
TFP_RADIUS_3GPP-NSAPI
Field name TFP_RADIUS_3GPP-NSAPI
Possible values
Exists in db Yes
CCD section
TFP_RADIUS_3GPP-PDP_Type
Field name TFP_RADIUS_3GPP-PDP_Type
Explanation RADIUS attribute 26. Vendor code 10415(3GPP). 0=IPv4, 1=PPP,
2=IPv6
128 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Possible values
Exists in db Yes
CCD section [RADIUS PDP type]
TFP_RADIUS_3GPP-SGSN-Address
Field name TFP_RADIUS_3GPP-SGSN-Address
Possible values
Exists in db Yes
CCD section
TFP_RADIUS_Called-Station-Id
Field name TFP_RADIUS_Called-Station-Id
Explanation RADIUS attribute 30.
Possible values
Exists in db Yes
CCD section
TFP_RADIUS_Calling-Station-Id
Field name TFP_RADIUS_Calling-Station-Id
Possible values
Exists in db Yes
CCD section
TFP_RADIUS_Framed-Compression
Field name TFP_RADIUS_Framed-Compression
Explanation RADIUS attribute 13. 0=None, 1=VJ TCP/IP header compression,
2=IPX header compression, 3=Stac-LZS compression
Possible values
Exists in db Yes
CCD section [RADIUS framed compression]
TFP_RADIUS_Framed-IP-Address
Field name TFP_RADIUS_Framed-IP-Address
P-DN0687206 Id:0900d805807819d6 129

Issue 2-2
Probes

Possible values
Exists in db Yes
CCD section
TFP_RADIUS_Framed-Protocol
Field name TFP_RADIUS_Framed-Protocol
Explanation RADIUS attribute 7. 1=PPP, 2=SLIP, 3=AppleTalk Remote Access
Protocol (ARAP), 4=Gandalf proprietary SingleLink/MultiLink protocol,
5=Xylogics proprietary IPX/SLIP, 6=X.75 Synchronous
Possible values
Exists in db Yes
CCD section [RADIUS framed protocol]
TFP_RADIUS_Identifier
Field name TFP_RADIUS_Identifier
Explanation From RADIUS header.
Possible values
Exists in db Yes
CCD section
TFP_RADIUS_Idle-Timeout
Field name TFP_RADIUS_Idle-Timeout
Possible values
Exists in db Yes
CCD section
TFP_RADIUS_Login-IP-Host
Field name TFP_RADIUS_Login-IP-Host
Possible values
130 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_RADIUS_Login-Service
Field name TFP_RADIUS_Login-Service
Explanation RADIUS attribute 15. 0=Telnet, 1=Rlogin, 2=TCP Clear, 3=PortMaster
(proprietary), 4=LAT, 5=X25-PAD, 6=X25-T3POS, 8=TCP Clear Quiet
(suppresses any NAS-generated connect string)
Possible values
Exists in db Yes
CCD section [RADIUS login service]
TFP_RADIUS_Login-TCP-Port
Field name TFP_RADIUS_Login-TCP-Port
Possible values
Exists in db Yes
CCD section
TFP_RADIUS_NAS-Identifier
Field name TFP_RADIUS_NAS-Identifier
Possible values
Exists in db Yes
CCD section
TFP_RADIUS_NAS-IP-Address
Field name TFP_RADIUS_NAS-IP-Address
Possible values
Exists in db Yes
CCD section
TFP_RADIUS_NAS-Port_Type
Field name TFP_RADIUS_NAS-Port_Type
P-DN0687206 Id:0900d805807819d6 131

Issue 2-2
Probes

Explanation RADIUS attribute 61. Number of port type (RFC2865).
Possible values
Exists in db Yes
CCD section [RADIUS NAS port type]
TFP_RADIUS_Nokia-Service-Name1
Field name TFP_RADIUS_Nokia-Service-Name1
Explanation RADIUS attribute 26. Vendor code 94(Nokia). Possibly many service
names in one message
Possible values
Exists in db Yes
CCD section
Explanation RADIUS attribute 26. Vendor code 94(Nokia).
Possible values
Exists in db Yes
CCD section
Possible values
Exists in db Yes
CCD section
Possible values
Exists in db Yes
132 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
CCD section
Possible values
Exists in db Yes
CCD section
TFP_RADIUS_RADIUS_Reserved_1
Field name TFP_RADIUS_RADIUS_Reserved_1
Possible values
Exists in db Yes
CCD section
TFP_RADIUS_RADIUS_Reserved_2
Field name TFP_RADIUS_RADIUS_Reserved_2
Possible values
Exists in db Yes
CCD section
TFP_RADIUS_Reply-Message
Field name TFP_RADIUS_Reply-Message
Possible values
Exists in db Yes
CCD section
TFP_RADIUS_Service-Type
Field name TFP_RADIUS_Service-Type
P-DN0687206 Id:0900d805807819d6 133

Issue 2-2
Probes
Explanation RADIUS attribute 6. 1=Login, 2=Framed, 3=Callback Login, 4=Callback

Framed, 5=Outbound, 6=Administrative, 7=NAS Prompt, 8=Authenti-
cate Only, 9=Callback NAS Prompt, 10=Call Check, 11=Callback
Administrative
Possible values
Exists in db Yes
CCD section [RADIUS service type]
TFP_RADIUS_Session-Timeout
Field name TFP_RADIUS_Session-Timeout
Possible values
Exists in db Yes
CCD section
TFP_RADIUS_User-Name
Field name TFP_RADIUS_User-Name
Possible values
Exists in db Yes
CCD section
5.1.10 RTSP v2.0 specific fields

TFP_RTSP_Content-Length
Field name TFP_RTSP_Content-Length
Explanation From DESCRIBE response. Bytes.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Content-Type
Field name TFP_RTSP_Content-Type
Explanation From DESCRIBE response.
Possible values
134 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_RTSP_Error_Status_2
Field name TFP_RTSP_Error_Status_2
Explanation Response status from RTSP header corresponding to
TFP_RTSP_Failed_Method_2.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Failed_Method_1
Field name TFP_RTSP_Failed_Method_1
Explanation Method name which was not responded to (trigger 88). E.g. "PLAY".
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Failed_Method_2
Field name TFP_RTSP_Failed_Method_2
Explanation Method name which caused error response (400-551).
Possible values
Exists in db Yes
CCD section
TFP_RTSP_RTSP_Reserved_1
Field name TFP_RTSP_RTSP_Reserved_1
Explanation Reserved for future use
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Ssrc
Field name TFP_RTSP_Ssrc
P-DN0687206 Id:0900d805807819d6 135

Issue 2-2
Probes

Explanation From SETUP message (Transport field).
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Ssrc_High
Field name TFP_RTSP_Ssrc_High
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Status
Field name TFP_RTSP_Status
Explanation Response status from RTSP header.
Possible values
Exists in db Yes
CCD section [RTSP Response status]
TFP_RTSP_Transport_Protocol
Field name TFP_RTSP_Transport_Protocol
Possible values
Exists in db Yes
CCD section
TFP_RTSP_URL
Field name TFP_RTSP_URL
Explanation From RTSP request header.
Possible values
Exists in db Yes
CCD section
136 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_RTSP_User-Agent
Field name TFP_RTSP_User-Agent
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Version
Field name TFP_RTSP_Version
Explanation RTSP version. The major number of the version is stored in the high-
order 4 bits, and the minor number is stored in the low-order 4 bits. E.g.
1.2 = 0001 0010 = 0x12
Possible values
Exists in db Yes
CCD section [RTSP Version]
5.1.11 RTSP Method specific fields

TFP_RTSP_Method
Field name TFP_RTSP_Method
Explanation This is a logical field that shows the method that caused the report.
Possible values 1 = OPTIONS 2 = DESCRIBE 3 = ANNOUNCE 4 = SETUP 5 = PLAY
6 = PAUSE 7 = TEARDOWN 8 = GET_PARAMETER 9 =
SET_PARAMETER 10 = REDIRECT 11 = RECORD 12 = Embedded
(Interleaved) Binary Data
Exists in db Yes
CCD section [RTSP Method]
TFP_RTSP_Reserved_1
Field name TFP_RTSP_Reserved_1
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 137

Issue 2-2
Probes
TFP_RTSP_Session_Id
Field name TFP_RTSP_Session_Id
Explanation Session identifier.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Status
Field name TFP_RTSP_Status
Explanation Response status from RTSP header. With reports with trigger 124 this
field is left empty.
Possible values
Exists in db Yes
CCD section [RTSP Response status]
TFP_RTSP_Status_Description
Field name TFP_RTSP_Status_Description
Explanation The text that the server has included in the signaling just after the
status. For example, 403 Forbidden - user unknown.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_URL
Possible values
Exists in db Yes
CCD section
TFP_RTSP_User_Agent
Field name TFP_RTSP_User_Agent
138 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Possible values
Exists in db Yes
CCD section
TFP_RTSP_Version
order 4 bits, and the minor number is stored in the low-order 4 bits. For
example:
1.2 = 0001 0010 = 0x12
Possible values
Exists in db Yes
5.1.12 RTSP QoS specific fields

TFP_RTSP_Audio_DL_Average_Jitter
Field name TFP_RTSP_Audio_DL_Average_Jitter
Explanation Inter-Arrival Jitter (RTP/RTCP-jitter) is calculated according to the prin-
ciples of RFC 3550. The value of this field shows the average jitter
downlink for the audio stream in hundredths of milliseconds (1 x 10-5 s).
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_DL_Average_MOS_x100
Field name TFP_RTSP_Audio_DL_Average_MOS_x100
Explanation Mean Opinion Score (from downlink audio stream) multiplied by 100.
The value of this field is sent to Traffica as an integer, but is handled by
Traffica as a decimal fraction with the precision of two decimal places,
in order to ensure the accuracy of real-time graphs. For example, a
value which is stored as 432 in the Traffica database is shown as 4.32
in Traffic News.
Possible values 500
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 139

Issue 2-2
Probes
TFP_RTSP_Audio_DL_Bytes
Field name TFP_RTSP_Audio_DL_Bytes
Explanation Downlink byte count related to the audio stream.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_DL_Last_Used_Codec
Field name TFP_RTSP_Audio_DL_Last_Used_Codec
Explanation Shows the last used codec of the downlink audio stream. RFC 3555.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_DL_Max_Jitter
Field name TFP_RTSP_Audio_DL_Max_Jitter
Explanation Indicates the maximum Audio DL Jitter from reliable jitter values in hun-
dredths of milliseconds (1 x 10-5 s).
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_DL_Min_Jitter
Field name TFP_RTSP_Audio_DL_Min_Jitter
Explanation Calculated from RTP or from RTCP; Indicates the minimum Audio DL
Interarrival Jitter from reliable jitter values in hundredths of milliseconds
(1 x 10-5 s).
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_DL_Min_MOS_x100
Field name TFP_RTSP_Audio_DL_Min_MOS_x100
140 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Explanation Indicates the minimum MOS experienced during the downlink audio
session. The value of this field is sent to Traffica as an integer, but is
handled by Traffica as a decimal fraction with the precision of two
decimal places, in order to ensure the accuracy of real-time graphs. For
example, a value which is stored as 432 in the Traffica database is
shown as 4.32 in Traffic News.
Possible values ≤ 500
Exists in db Yes
CCD section
TFP_RTSP_Audio_DL_Number_of_RTCP_RR_Reports
Field name TFP_RTSP_Audio_DL_Number_of_RTCP_RR_Reports
Explanation Number of RTCP Receiver Reports received related to the audio
stream downlink.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_DL_Number_of_RTCP_SR_Reports
Field name TFP_RTSP_Audio_DL_Number_of_RTCP_SR_Reports
Explanation Number of RTCP Sender Reports received related to the audio stream
downlink.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_DL_Packets
Field name TFP_RTSP_Audio_DL_Packets
Explanation Downlink packet count related to the audio stream.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_DL_Packets_Lost
Field name TFP_RTSP_Audio_DL_Packets_Lost
P-DN0687206 Id:0900d805807819d6 141

Issue 2-2
Probes
Explanation Number of audio packets lost downlink. If the value is negative, it is set
to 0.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_DL_Packets_Out_of_Order
Field name TFP_RTSP_Audio_DL_Packets_Out_of_Order
Explanation Number of audio packets out of order downlink.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_DL_Payload_Type
Field name TFP_RTSP_Audio_DL_Payload_Type
Explanation Indicates the format of the payload in the downlink audio stream and
determines its interpretation by the application.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_DL_Reserved
Field name TFP_RTSP_Audio_DL_Reserved
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_DL_SSRC
Field name TFP_RTSP_Audio_DL_SSRC
Explanation Synchronization source (SSRC) for the downlink audio stream: The
source of a stream of RTP packets, identified by a 32-bit numeric SSRC
identifier carried in the RTP header so as not to be dependent upon the
network address.
Possible values
142 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_RTSP_Audio_DL_Standard_Deviation_for_MOS_x100
Field name TFP_RTSP_Audio_DL_Standard_Deviation_for_MOS_x100
Explanation Standard deviation for MOS audio downlink multiplied by 100. The
value of this field is sent to Traffica as an integer, but is handled by
in Traffic News.
Exists in db Yes
CCD section
TFP_RTSP_Audio_DL_Used_Codecs
Field name TFP_RTSP_Audio_DL_Used_Codecs
Explanation Shows the codecs used in the session (audio DL). For more information
on coding, see Appendix E: Audio and video codecs.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_Reliable_Bits
Field name TFP_RTSP_Audio_Reliable_Bits
Explanation Reliability bits for audio Jitter and MOS values. Bit 1 Audio Jitter DL;
0b0=Not reliable; 0b1=Reliable Bit 2 Audio Jitter UL; 0b0=Not reliable;
0b1=Reliable Bit 3 Audio Jitter method: 0b0 = RTCP; 0b1 = RTP Bit 4
Audio MOS DL; 0b0=Not reliable; 0b1=Reliable Bit 5 Audio MOS UL;
0b0=Not reliable; 0b1=Reliable Bit 6 = 0 Bit 7 = 0 Bit 8 = 0
Possible values
Exists in db Yes
CCD section [Audio Reliable Bits]
TFP_RTSP_Audio_UL_Average_Jitter
Field name TFP_RTSP_Audio_UL_Average_Jitter
P-DN0687206 Id:0900d805807819d6 143

Issue 2-2
Probes
Explanation Inter-Arrival Jitter (RTP/RTCP-jitter) is calculated according to princi-

ples of RFC3550. This field Indicates the average jitter uplink for the
audio stream in hundredths of milliseconds (1 x 10-5 s).
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_UL_Average_MOS_x100
Field name TFP_RTSP_Audio_UL_Average_MOS_x100
Explanation Mean Opinion Score (from uplink audio stream) multiplied by 100. The
in Traffic News.
Exists in db Yes
CCD section
TFP_RTSP_Audio_UL_Bytes
Field name TFP_RTSP_Audio_UL_Bytes
Datatype in IDS UIT64
Explanation Uplink byte count related to the audio stream.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_UL_Last_Used_Codec
Field name TFP_RTSP_Audio_UL_Last_Used_Codec
Explanation Shows the last used codec of the uplink audio stream. RFC 3555.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_UL_Max_Jitter
Field name TFP_RTSP_Audio_UL_Max_Jitter
144 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Explanation Indicates the maximum Audio UL Jitter from reliable jitter values in hun-
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_UL_Min_Jitter
Field name TFP_RTSP_Audio_UL_Min_Jitter
Explanation Calculated from RTP or from RTCP; Indicates the minimum Audio UL
(1 x 10-5 s).
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_UL_Min_MOS_x100
Field name TFP_RTSP_Audio_UL_Min_MOS_x100
Explanation Indicates the minimum MOS experienced during the uplink audio
Exists in db Yes
CCD section
TFP_RTSP_Audio_UL_Number_of_RTCP_RR_Reports
Field name TFP_RTSP_Audio_UL_Number_of_RTCP_RR_Reports
stream uplink.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_UL_Number_of_RTCP_SR_Reports
Field name TFP_RTSP_Audio_UL_Number_of_RTCP_SR_Reports
P-DN0687206 Id:0900d805807819d6 145

Issue 2-2
Probes

uplink.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_UL_Packets
Field name TFP_RTSP_Audio_UL_Packets
Explanation Uplink packet count related to the audio stream.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_UL_Packets_Lost
Field name TFP_RTSP_Audio_UL_Packets_Lost
Explanation Number of audio packets lost. From RTCP or RTP. If the value is neg-
ative, it is set to 0.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_UL_Packets_Out_of_Order
Field name TFP_RTSP_Audio_UL_Packets_Out_of_Order
Explanation Number of audio packets out of order uplink. From RTP.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_UL_Payload_Type
Field name TFP_RTSP_Audio_UL_Payload_Type
Explanation Indicates the format of the payload in the uplink audio stream and deter-
mines its interpretation by the application. Available in RTP.
Possible values
Exists in db Yes
146 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
CCD section
TFP_RTSP_Audio_UL_Reserved
Field name TFP_RTSP_Audio_UL_Reserved
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_UL_SSRC
Field name TFP_RTSP_Audio_UL_SSRC
Explanation Synchronization source (SSRC) for the uplink audio stream: The source
of a stream of RTP packets, identified by a 32-bit numeric SSRC iden-
tifier carried in the RTP header so as not to be dependent upon the
network address.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Audio_UL_Standard_Deviation_for_MOS_x100
Field name TFP_RTSP_Audio_UL_Standard_Deviation_for_MOS_x100
Explanation Standard deviation for MOS audio uplink multiplied by 100. E.g. The
in Traffic News.
Exists in db Yes
CCD section
TFP_RTSP_Audio_UL_Used_Codecs
Field name TFP_RTSP_Audio_UL_Used_Codecs
Explanation Shows the codecs used in the session (audio UL). For more information
on coding, see Audio and video codecs.
Possible values
P-DN0687206 Id:0900d805807819d6 147

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_RTSP_Session_Id
Field name TFP_RTSP_Session_Id
Explanation Session identifier.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_URL
Possible values
Exists in db Yes
CCD section
TFP_RTSP_User_Agent
Field name TFP_RTSP_User_Agent
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Version
order 4 bits, and the minor number is stored in the low-order 4 bits. E.g.
1.2 = 0001 0010 = 0x12
Possible values
Exists in db Yes
TFP_RTSP_Video_DL_Average_Jitter
Field name TFP_RTSP_Video_DL_Average_Jitter
148 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

ples of RFC3550. This field Indicates the average jitter downlink for the
video stream in hundredths of milliseconds (1 x 10-5 s).
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_DL_Average_MOS_x100
Field name TFP_RTSP_Video_DL_Average_MOS_x100
Explanation Mean Opinion Score (from downlink video stream) multiplied by 100.
in Traffic News.
Exists in db Yes
CCD section
TFP_RTSP_Video_DL_Bytes
Field name TFP_RTSP_Video_DL_Bytes
Explanation Downlink byte count related to the video stream.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_DL_Last_Used_Codec
Field name TFP_RTSP_Video_DL_Last_Used_Codec
Explanation Shows the last used codec of the downlink video stream. RFC 3555.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_DL_Max_Jitter
Field name TFP_RTSP_Video_DL_Max_Jitter
P-DN0687206 Id:0900d805807819d6 149

Issue 2-2
Probes

Explanation Indicates the maximum video DL Jitter from reliable jitter values in hun-
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_DL_Min_Jitter
Field name TFP_RTSP_Video_DL_Min_Jitter
Explanation Calculated from RTP or from RTCP; Indicates the minimum video DL
(1 x 10-5 s).
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_DL_Min_MOS_x100
Field name TFP_RTSP_Video_DL_Min_MOS_x100
Explanation Indicates the minimum MOS experienced during the downlink video
Exists in db Yes
CCD section
TFP_RTSP_Video_DL_Number_of_RTCP_RR_Reports
Field name TFP_RTSP_Video_DL_Number_of_RTCP_RR_Reports
Explanation Number of RTCP Receiver Reports received related to the video stream
downlink.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_DL_Number_of_RTCP_SR_Reports
Field name TFP_RTSP_Video_DL_Number_of_RTCP_SR_Reports
150 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Explanation Number of RTCP Sender Reports received related to the video stream
downlink.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_DL_Packets
Field name TFP_RTSP_Video_DL_Packets
Explanation Downlink packet count related to the video stream.
Possible values
Exists in db Yes
CCD section [Packet count unit]
TFP_RTSP_Video_DL_Packets_Lost
Field name TFP_RTSP_Video_DL_Packets_Lost
Explanation Number of video packets lost. From RTCP or RTP. If the value is neg-
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_DL_Packets_Out_of_Order
Field name TFP_RTSP_Video_DL_Packets_Out_of_Order
Explanation Number of video packets out of order downlink. From RTP.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_DL_Payload_Type
Field name TFP_RTSP_Video_DL_Payload_Type
Explanation Indicates the format of the payload in the downlink video stream and
determines its interpretation by the application.
Possible values
P-DN0687206 Id:0900d805807819d6 151

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_RTSP_Video_DL_Reserved
Field name TFP_RTSP_Video_DL_Reserved
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_DL_SSRC
Field name TFP_RTSP_Video_DL_SSRC
Explanation Synchronization source (SSRC) for the downlink video stream: The
source of a stream of RTP packets, identified by a 32-bit numeric SSRC
identifier carried in the RTP header so as not to be dependent upon the
network address.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_DL_Standard_Deviation_for_MOS_x100
Field name TFP_RTSP_Video_DL_Standard_Deviation_for_MOS_x100
Explanation Standard deviation for MOS video downlink multiplied by 100. The
in Traffic News.
Exists in db Yes
CCD section [Standard Deviation for MOS x100]
TFP_RTSP_Video_DL_Used_Codecs
Field name TFP_RTSP_Video_DL_Used_Codecs
Explanation Shows the codecs used in the session (video DL). For more information
152 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_Reliable_Bits
Field name TFP_RTSP_Video_Reliable_Bits
Explanation Reliability bits for video Jitter and MOS values. Bit 1 Video Jitter DL;
0b0=Not reliable; 0b1=Reliable Bit 2 Video Jitter UL; 0b0=Not reliable;
0b1=Reliable Bit 3 Video Jitter method: 0b0 = RTCP; 0b1 = RTP Bit 4
Video MOS DL; 0b0=Not reliable; 0b1=Reliable Bit 5 Video MOS UL;
Possible values
Exists in db Yes
CCD section [Video Reliable bits]
TFP_RTSP_Video_UL_Average_Jitter
Field name TFP_RTSP_Video_UL_Average_Jitter
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_UL_Average_MOS_x100
Field name TFP_RTSP_Video_UL_Average_MOS_x100
Explanation Mean Opinion Score (from uplink video stream) multiplied by 100. The
in Traffic News.
Exists in db Yes
CCD section
TFP_RTSP_Video_UL_Bytes
Field name TFP_RTSP_Video_UL_Bytes
P-DN0687206 Id:0900d805807819d6 153

Issue 2-2
Probes

Explanation Uplink byte count related to the video stream.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_UL_Last_Used_Codec
Field name TFP_RTSP_Video_UL_Last_Used_Codec
Explanation Shows the last used codec of the uplink video stream. RFC 3555.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_UL_Max_Jitter
Field name TFP_RTSP_Video_UL_Max_Jitter
Explanation Indicates the maximum video UL Jitter from reliable jitter values in hun-
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_UL_Min_Jitter
Field name TFP_RTSP_Video_UL_Min_Jitter
Explanation Calculated from RTP or from RTCP; Indicates the minimum video UL
(1 x 10-5 s).
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_UL_Min_MOS_x100
Field name TFP_RTSP_Video_UL_Min_MOS_x100
Explanation Indicates the minimum MOS experienced during the uplink video
154 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Exists in db Yes
CCD section
TFP_RTSP_Video_UL_Number_of_RTCP_RR_Reports
Field name TFP_RTSP_Video_UL_Number_of_RTCP_RR_Reports
uplink.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_UL_Number_of_RTCP_SR_Reports
Field name TFP_RTSP_Video_UL_Number_of_RTCP_SR_Reports
uplink.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_UL_Packets
Field name TFP_RTSP_Video_UL_Packets
Explanation Uplink packet count related to the video stream.
Possible values
Exists in db Yes
CCD section [Packet count unit]
TFP_RTSP_Video_UL_Packets_Lost
Field name TFP_RTSP_Video_UL_Packets_Lost
Explanation Number of video packets lost. If the value is negative, it is set to 0.
Possible values
Exists in db Yes
P-DN0687206 Id:0900d805807819d6 155

Issue 2-2
Probes
CCD section
TFP_RTSP_Video_UL_Packets_Out_of_Order
Field name TFP_RTSP_Video_UL_Packets_Out_of_Order
Explanation Number of video packets out of order uplink.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_UL_Payload_Type
Field name TFP_RTSP_Video_UL_Payload_Type
Explanation Indicates the format of the payload in the uplink video stream and deter-
mines its interpretation by the application.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_UL_Reserved
Field name TFP_RTSP_Video_UL_Reserved
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_UL_SSRC
Field name TFP_RTSP_Video_UL_SSRC
Explanation Synchronization source (SSRC) for the uplink video stream: The source
of a stream of RTP packets, identified by a 32-bit numeric SSRC iden-
tifier carried in the RTP header so as not to be dependent upon the
network address.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_UL_Standard_Deviation_for_MOS_x100
Field name TFP_RTSP_Video_UL_Standard_Deviation_for_MOS_x100
156 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Explanation Standard deviation for MOS video uplink multiplied by 100. The value of
this field is sent to Traffica as an integer, but is handled by Traffica as a
decimal fraction with the precision of two decimal places, in order to
ensure the accuracy of real-time graphs. For example, a value which is
stored as 432 in the Traffica database is shown as 4.32 in Traffic News.
Possible values
Exists in db Yes
CCD section
TFP_RTSP_Video_UL_Used_Codecs
Field name TFP_RTSP_Video_UL_Used_Codecs
Explanation Shows the codecs used in the session (video UL). For more information
Possible values
Exists in db Yes
CCD section
5.1.13 SIP Method specific fields

TFP_SIP_CSeq
Field name TFP_SIP_CSeq
Explanation From SIP message.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Direction_of_SIP_Method
Field name TFP_SIP_Direction_of_SIP_Method
Explanation 1 = from UE 2 = to UE
Possible values
Exists in db Yes
CCD section [Direction of SIP]
TFP_SIP_Expiration_Interval
Field name TFP_SIP_Expiration_Interval
P-DN0687206 Id:0900d805807819d6 157

Issue 2-2
Probes

Explanation Expiration interval from REGISTER.
Possible values
Exists in db Yes
CCD section
TFP_SIP_From_Contact_URI_Domain_Name
Field name TFP_SIP_From_Contact_URI_Domain_Name
Explanation Domain name or IP address in Contact field: username@domain. This
represents the A side. For originating site: taken from the first Invite
detected. For terminating site: taken from the last Invite detected.
Possible values
Exists in db Yes
CCD section
TFP_SIP_From_Contact_URI_IP_Port
Field name TFP_SIP_From_Contact_URI_IP_Port
Explanation Port in Contact field: username@ip-address:port. This represents the A
side. For originating site: taken from the first Invite detected. For termi-
nating site: taken from the last Invite detected.
Possible values
Exists in db Yes
CCD section
TFP_SIP_From_Contact_URI_Telephone_Subscriber
Field name TFP_SIP_From_Contact_URI_Telephone_Subscriber
Explanation Telephone subscriber in the From field. For example:
+358400001@nsn.com → 358400001. This field is populated only if a
telephone number is present. This represents the A side. For originating
site: taken from the first Invite detected. For terminating site: taken from
the last Invite detected.
Possible values
Exists in db Yes
CCD section
TFP_SIP_From_Contact_URI_Username
Field name TFP_SIP_From_Contact_URI_Username
158 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Explanation User name in Contact field. username@domain. This represents the A
side. For originating site: taken from the first Invite detected. For termi-
nating site: taken from the last Invite detected.
Possible values
Exists in db Yes
CCD section
TFP_SIP_From_URI_Domain
Field name TFP_SIP_From_URI_Domain
Explanation Domain name or IP address in From field: username@domain or user-
name@ip-address. This represents the A side. For originating site:
taken from the first Invite detected. For terminating site: taken from the
last Invite detected.
Possible values
Exists in db Yes
CCD section
TFP_SIP_From_URI_Telephone_Subscriber
Field name TFP_SIP_From_URI_Telephone_Subscriber
Possible values
Exists in db Yes
CCD section
TFP_SIP_From_URI_Username
Field name TFP_SIP_From_URI_Username
Explanation User name in the From field. For example: username@domain. This
detected. For terminating site: taken from the last Invite detected.
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 159

Issue 2-2
Probes
TFP_SIP_Method_Id
Field name TFP_SIP_Method_Id
Explanation Indicates the logical number of the method used: 0 = other, undefined 1
= INVITE 2 = OPTIONS 3 = BYE 4 = CANCEL 5 = ACK 6 = REGISTER
7 = SUBSCRIBE (RFC3265) 8 = NOTIFY (RFC3265) 9 = REFER
(RFC3515) 10 = MESSAGE (RFC3428) 11 = PRACK (RFC3262) 12 =
UPDATE (RFC3311) 13 = INFO (RFC2976) 14 = PUBLISH (RFC3903)
Possible values 0-14
Exists in db Yes
CCD section [SIP Method]
TFP_SIP_Owner_Address
Field name TFP_SIP_Owner_Address
Explanation From SDP.; the Owner Address. For originating site: from INVITE, For
terminating site: from response to INVITE (200 OK)
Possible values
Exists in db Yes
CCD section
TFP_SIP_Session_id
Field name TFP_SIP_Session_id
Explanation SIP: Call id; Identification of the SIP session. From SIP message.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Status
Field name TFP_SIP_Status
Explanation From SIP Status line. 1xx = provisional; 2xx = success; 3xx = redirect;
4xx = client error; 5xx = server error; 6 = global error Status is set empty
in case of ACK.
Possible values
Exists in db Yes
CCD section
160 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_SIP_Status_Description
Field name TFP_SIP_Status_Description
status.
Possible values
Exists in db Yes
CCD section
TFP_SIP_To_Contact_URI_Domain_Name
Field name TFP_SIP_To_Contact_URI_Domain_Name
Explanation Domain name or IP address in Contact field: username@domain or
username@ip-address.
Possible values
Exists in db Yes
CCD section
TFP_SIP_To_Contact_URI_IP_Port
Field name TFP_SIP_To_Contact_URI_IP_Port
Explanation Port in Contact field: username@ip-address:port. This represents the
B side.
Possible values
Exists in db Yes
CCD section
TFP_SIP_To_Contact_URI_Telephone_Subscriber
Field name TFP_SIP_To_Contact_URI_Telephone_Subscriber
telephone number is present. This represents the B side. For originating
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 161

Issue 2-2
Probes
TFP_SIP_To_Contact_URI_Username
Field name TFP_SIP_To_Contact_URI_Username
Explanation User name in Contact field. username@domain. This represents the B
side.
Possible values
Exists in db Yes
CCD section
TFP_SIP_To_URI_Domain
Field name TFP_SIP_To_URI_Domain
Explanation Domain name or IP address in To field: username@domain or user-
name@ip-address. This represents the B side. For originating site:
taken from the first Invite detected. For terminating site: taken from the
last Invite detected.
Possible values
Exists in db Yes
CCD section
TFP_SIP_To_URI_Telephone_Subscriber
Field name TFP_SIP_To_URI_Telephone_Subscriber
Possible values
Exists in db Yes
CCD section
TFP_SIP_To_URI_Username
Field name TFP_SIP_To_URI_Username
Explanation User name in To field. username@domain. This represents the B side.
For originating site: taken from the first Invite detected. For terminating
site: taken from the last Invite detected.
Possible values
162 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_SIP_User_Agent
Field name TFP_SIP_User_Agent
Possible values
Exists in db Yes
CCD section
TFP_SIP_Version
Field name TFP_SIP_Version
Explanation SIP version. The major number of the version is stored in the high-order
4 bits, and the minor number is stored in the low-order 4 bits. E.g. 1.2 =
0001 0010 = 0x12
Possible values
Exists in db Yes
CCD section [SIP version]
TFP_SIP1_Reserved_1
Field name TFP_SIP1_Reserved_1
Possible values
Exists in db Yes
CCD section
5.1.14 SIP QoS specific fields

TFP_SIP_Audio_DL_Average_Jitter
Field name TFP_SIP_Audio_DL_Average_Jitter
Possible values
Exists in db Yes
P-DN0687206 Id:0900d805807819d6 163

Issue 2-2
Probes
CCD section
TFP_SIP_Audio_DL_Average_MOS_x100
Field name TFP_SIP_Audio_DL_Average_MOS_x100
Explanation Mean Opinion Score (from downlink audio stream) multiplied by 100.
in Traffic News.
Exists in db Yes
CCD section
TFP_SIP_Audio_DL_Last_Used_Codec
Field name TFP_SIP_Audio_DL_Last_Used_Codec
Explanation Shows the last used codec of the downlink audio stream. RFC 3555.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Audio_DL_Max_Jitter
Field name TFP_SIP_Audio_DL_Max_Jitter
Explanation Indicates the maximum Audio DL Jitter from reliable jitter values in hun-
Possible values
Exists in db Yes
CCD section
TFP_SIP_Audio_DL_Min_Jitter
Field name TFP_SIP_Audio_DL_Min_Jitter
Explanation Calculated from RTP or from RTCP; Indicates the minimum Audio DL
(1 x 10-5 s).
Possible values
Exists in db Yes
164 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
CCD section
TFP_SIP_Audio_DL_Min_MOS_x100
Field name TFP_SIP_Audio_DL_Min_MOS_x100
Explanation Indicates the minimum MOS experienced during the downlink audio
session. Values similarly to Audio DL Average MOS x100. The value of
Exists in db Yes
CCD section
TFP_SIP_Audio_DL_Number_of_RTCP_RR_Reports
Field name TFP_SIP_Audio_DL_Number_of_RTCP_RR_Reports
stream downlink.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Audio_DL_Number_of_RTCP_SR_Reports
Field name TFP_SIP_Audio_DL_Number_of_RTCP_SR_Reports
downlink.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Audio_DL_Packets_Lost
Field name TFP_SIP_Audio_DL_Packets_Lost
Explanation Number of audio packets lost downlink. From RTCP or RTP. If the value
is negative, it is set to 0.
Possible values
Exists in db Yes
P-DN0687206 Id:0900d805807819d6 165

Issue 2-2
Probes
CCD section
TFP_SIP_Audio_DL_Packets_Out_of_Order
Field name TFP_SIP_Audio_DL_Packets_Out_of_Order
Explanation Number of audio packets out of order downlink. From RTP.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Audio_DL_Reserved
Field name TFP_SIP_Audio_DL_Reserved
Possible values
Exists in db Yes
CCD section
TFP_SIP_Audio_DL_Standard_Deviation_for_MOS_x100
Field name TFP_SIP_Audio_DL_Standard_Deviation_for_MOS_x100
Explanation Standard deviation for MOS audio downlink multiplied by 100. The
in Traffic News.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Audio_DL_Used_Codecs
Field name TFP_SIP_Audio_DL_Used_Codecs
Explanation Shows the codecs used in the session (audio DL). For more information
Possible values
Exists in db Yes
CCD section
166 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_SIP_Audio_Reliable_Bits
Field name TFP_SIP_Audio_Reliable_Bits
Explanation Reliability bits for audio Jitter and MOS values. Bit 1 Audio Jitter DL;
0b0=Not reliable; 0b1=Reliable Bit 2 Audio Jitter UL; 0b0=Not reliable;
0b1=Reliable Bit 3 Audio Jitter method: 0b0 = RTCP; 0b1 = RTP Bit 4
Audio MOS DL; 0b0=Not reliable; 0b1=Reliable Bit 5 Audio MOS UL;
Possible values
Exists in db Yes
CCD section
TFP_SIP_Audio_UL_Average_Jitter
Field name TFP_SIP_Audio_UL_Average_Jitter
Possible values
Exists in db Yes
CCD section
TFP_SIP_Audio_UL_Average_MOS_x100
Field name TFP_SIP_Audio_UL_Average_MOS_x100
Explanation Mean Opinion Score (from uplink audio stream) multiplied by 100. The
in Traffic News.
Exists in db Yes
CCD section
TFP_SIP_Audio_UL_Last_Used_Codec
Field name TFP_SIP_Audio_UL_Last_Used_Codec
Explanation Shows the last used codec of the uplink audio stream. RFC 3555.
Possible values
P-DN0687206 Id:0900d805807819d6 167

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_SIP_Audio_UL_Max_Jitter
Field name TFP_SIP_Audio_UL_Max_Jitter
Explanation Indicates the maximum Audio UL Jitter from reliable jitter values in hun-
Possible values
Exists in db Yes
CCD section
TFP_SIP_Audio_UL_Min_Jitter
Field name TFP_SIP_Audio_UL_Min_Jitter
Explanation Calculated from RTP or from RTCP; Indicates the minimum Audio UL
(1 x 10-5 s).
Possible values
Exists in db Yes
CCD section
TFP_SIP_Audio_UL_Min_MOS_x100
Field name TFP_SIP_Audio_UL_Min_MOS_x100
Explanation Indicates the minimum MOS experienced during the uplink audio
session. Values similarly to Audio UL Average MOS x100. The value of
Exists in db Yes
CCD section
TFP_SIP_Audio_UL_Number_of_RTCP_RR_Reports
Field name TFP_SIP_Audio_UL_Number_of_RTCP_RR_Reports
stream uplink.
168 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Possible values
Exists in db Yes
CCD section
TFP_SIP_Audio_UL_Number_of_RTCP_SR_Reports
Field name TFP_SIP_Audio_UL_Number_of_RTCP_SR_Reports
uplink.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Audio_UL_Packets_Lost
Field name TFP_SIP_Audio_UL_Packets_Lost
Explanation Number of audio packets lost. From RTCP or RTP. If the value is neg-
Possible values
Exists in db Yes
CCD section
TFP_SIP_Audio_UL_Packets_Out_of_Order
Field name TFP_SIP_Audio_UL_Packets_Out_of_Order
Explanation Number of audio packets out of order uplink. From RTP.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Audio_UL_Reserved
Field name TFP_SIP_Audio_UL_Reserved
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 169

Issue 2-2
Probes
TFP_SIP_Audio_UL_Standard_Deviation_for_MOS_x100
Field name TFP_SIP_Audio_UL_Standard_Deviation_for_MOS_x100
Explanation Standard deviation for MOS audio uplink multiplied by 100. The value
of this field is sent to Traffica as an integer, but is handled by Traffica as
a decimal fraction with the precision of two decimal places, in order to
Possible values
Exists in db Yes
CCD section
TFP_SIP_Audio_UL_Used_Codecs
Field name TFP_SIP_Audio_UL_Used_Codecs
Explanation Shows the codecs used in the session (audio UL). For more information
Possible values
Exists in db Yes
CCD section
TFP_SIP_Direction_of_SIP_Session
Field name TFP_SIP_Direction_of_SIP_Session
Explanation 1 = from UE 2 = to UE
Possible values
Exists in db Yes
CCD section [Direction of SIP]
TFP_SIP_From_Contact_URI_Domain_Name
Field name TFP_SIP_From_Contact_URI_Domain_Name
Explanation Domain name or IP address in Contact field: username@domain. This
detected . For terminating site: taken from the last Invite detected .
Possible values
Exists in db Yes
CCD section
170 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_SIP_From_Contact_URI_IP_Port
Field name TFP_SIP_From_Contact_URI_IP_Port
Explanation Port in Contact field: username@ip-address:port. This represents the A
side. For originating site: taken from the first Invite detected . For termi-
nating site: taken from the last Invite detected .
Possible values
Exists in db Yes
CCD section
TFP_SIP_From_Contact_URI_Telephone_Subscriber
Field name TFP_SIP_From_Contact_URI_Telephone_Subscriber
+358400001@nsn.com -> 358400001. This field is populated only if a
Possible values
Exists in db Yes
CCD section
TFP_SIP_From_Contact_URI_Username
Field name TFP_SIP_From_Contact_URI_Username
Explanation User name in Contact field. username@domain. This represents the A
Possible values
Exists in db Yes
CCD section
TFP_SIP_From_URI_Domain
Field name TFP_SIP_From_URI_Domain
Explanation Domain name or IP address in From field: username@domain or user-
name@ip-address. This represents the A side. For originating site:
taken from the first Invite detected . For terminating site: taken from the
last Invite detected .
Possible values
P-DN0687206 Id:0900d805807819d6 171

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_SIP_From_URI_Telephone_Subscriber
Field name TFP_SIP_From_URI_Telephone_Subscriber
Possible values
Exists in db Yes
CCD section
TFP_SIP_From_URI_Username
Field name TFP_SIP_From_URI_Username
Explanation User name in From field. username@domain. This represents the A
Possible values
Exists in db Yes
CCD section
TFP_SIP_Latest_Method_Used
Field name TFP_SIP_Latest_Method_Used
Explanation The latest method used. In case of trigger 132 this field is 3 (BYE). 0 =
other, undefined 1 = INVITE 2 = OPTIONS 3 = BYE 4 = CANCEL 5 =
ACK 6 = REGISTER 7 = SUBSCRIBE (RFC3265) 8 = NOTIFY
(RFC3265) 9 = REFER (RFC3515) 10 = MESSAGE (RFC3428) 11 =
PRACK (RFC3262) 12 = UPDATE (RFC3311) 13 = INFO (RFC2976)
14 = PUBLISH (RFC3903)
Possible values
Exists in db Yes
CCD section [SIP Method]
TFP_SIP_Owner_Address
Field name TFP_SIP_Owner_Address
172 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Explanation From SDP.; the Owner Address. For originating site: from INVITE, For
terminating site: from response to INVITE (200 OK)
Possible values
Exists in db Yes
CCD section
TFP_SIP_Session_Duration
Field name TFP_SIP_Session_Duration
Explanation Duration between ACK for INVITE and BYE. Unit : ms. In case of trigger
133, the time between session start and idle time start.
Possible values
Exists in db Yes
CCD section [SIP Session Duration Unit]
TFP_SIP_Session_Id
Field name TFP_SIP_Session_Id
Explanation SIP: Call id; Identification of the SIP session. From SIP message.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Session_Type
Field name TFP_SIP_Session_Type
Explanation Indicates the SIP session type: SIP call (1), SIP Message (2).
Possible values 0x1-0x2
Exists in db Yes
CCD section [SIP Session Type]
TFP_SIP_Status
Field name TFP_SIP_Status
Explanation Status of the latest method used. In case of trigger 132, from SIP BYE
response Status line. 1xx = provisional; 2xx = success; 3xx = redirect;
4xx = client error; 5xx = server error; 6 = global error
Possible values
P-DN0687206 Id:0900d805807819d6 173

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_SIP_Status_Description
Field name TFP_SIP_Status_Description
status.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Timestamp_for_ACK_Date
Field name TFP_SIP_Timestamp_for_ACK_Date
Explanation Timestamp when ACK for INVITE was in network. Local time.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Timestamp_for_ACK_Time
Field name TFP_SIP_Timestamp_for_ACK_Time
Explanation Timestamp when ACK for INVITE was in network. Local time.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Timestamp_for_INVITE_Date
Field name TFP_SIP_Timestamp_for_INVITE_Date
Explanation Timestamp when INVITE was in network. Local time.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Timestamp_for_INVITE_Time
Field name TFP_SIP_Timestamp_for_INVITE_Time
174 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Explanation Timestamp when INVITE was in network. Local time.
Possible values
Exists in db Yes
CCD section
TFP_SIP_To_Contact_URI_Domain_Name
Field name TFP_SIP_To_Contact_URI_Domain_Name
Explanation Domain name or IP address in Contact field: username@domain or
username@ip-address.
Possible values
Exists in db Yes
CCD section
TFP_SIP_To_Contact_URI_IP_Port
Field name TFP_SIP_To_Contact_URI_IP_Port
Explanation Port in Contact field: username@ip-address:port. This represents the
B side.
Possible values
Exists in db Yes
CCD section
TFP_SIP_To_Contact_URI_Telephone_Subscriber
Field name TFP_SIP_To_Contact_URI_Telephone_Subscriber
telephone number is present. This represents the Bside. For originating
Possible values
Exists in db Yes
CCD section
TFP_SIP_To_Contact_URI_Username
Field name TFP_SIP_To_Contact_URI_Username
P-DN0687206 Id:0900d805807819d6 175

Issue 2-2
Probes
Explanation User name in Contact field. username@domain. This represents the B

side.
Possible values
Exists in db Yes
CCD section
TFP_SIP_To_URI_Domain
Field name TFP_SIP_To_URI_Domain
Explanation Domain name or IP address in To field: username@domain or user-
name@ip-address. This represents the B side. For originating site:
taken from the first Invite detected . For terminating site: taken from the
last Invite detected .
Possible values
Exists in db Yes
CCD section
TFP_SIP_To_URI_Telephone_Subscriber
Field name TFP_SIP_To_URI_Telephone_Subscriber
Possible values
Exists in db Yes
CCD section
TFP_SIP_To_URI_Username
Field name TFP_SIP_To_URI_Username
Explanation User name in To field. username@domain. This represents the B side.
For originating site: taken from the first Invite detected . For terminating
site: taken from the last Invite detected .
Possible values
Exists in db Yes
CCD section
TFP_SIP_User_Agent
Field name TFP_SIP_User_Agent
176 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Possible values
Exists in db Yes
CCD section
TFP_SIP_Version
Field name TFP_SIP_Version
Explanation SIP version. The major number of the version is stored in the high-order
4 bits, and the minor number is stored in the low-order 4 bits. E.g. 1.2 =
0001 0010 = 0x12
Possible values
Exists in db Yes
CCD section [SIP version]
TFP_SIP_Video_DL_Average_Jitter
Field name TFP_SIP_Video_DL_Average_Jitter
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_DL_Average_MOS_x100
Field name TFP_SIP_Video_DL_Average_MOS_x100
Explanation Mean Opinion Score (from downlink video stream) multiplied by 100.
in Traffic News.
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 177

Issue 2-2
Probes
TFP_SIP_Video_DL_Last_Used_Codec
Field name TFP_SIP_Video_DL_Last_Used_Codec
Explanation Shows the last used codec of the downlink video stream. RFC 3555.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_DL_Max_Jitter
Field name TFP_SIP_Video_DL_Max_Jitter
Explanation Indicates the maximum video DL Jitter from reliable jitter values in hun-
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_DL_Min_Jitter
Field name TFP_SIP_Video_DL_Min_Jitter
Explanation Calculated from RTP or from RTCP; Indicates the minimum video DL
(1 x 10-5 s).
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_DL_Min_MOS_x100
Field name TFP_SIP_Video_DL_Min_MOS_x100
Explanation Indicates the minimum MOS experienced during the downlink video
session. Values similarly to Video DL Average MOS x100. The value of
Exists in db Yes
CCD section
178 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_SIP_Video_DL_Number_of_RTCP_RR_Reports
Field name TFP_SIP_Video_DL_Number_of_RTCP_RR_Reports
downlink.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_DL_Number_of_RTCP_SR_Reports
Field name TFP_SIP_Video_DL_Number_of_RTCP_SR_Reports
downlink.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_DL_Packets_Lost
Field name TFP_SIP_Video_DL_Packets_Lost
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_DL_Packets_Out_of_Order
Field name TFP_SIP_Video_DL_Packets_Out_of_Order
Explanation Number of video packets out of order downlink. From RTP.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_DL_Reserved
Field name TFP_SIP_Video_DL_Reserved
P-DN0687206 Id:0900d805807819d6 179

Issue 2-2
Probes

Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_DL_Standard_Deviation_for_MOS_x100
Field name TFP_SIP_Video_DL_Standard_Deviation_for_MOS_x100
Explanation Standard deviation for MOS video downlink multiplied by 100. The
in Traffic News.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_DL_Used_Codecs
Field name TFP_SIP_Video_DL_Used_Codecs
Explanation Shows the codecs used in the session (video DL). For more information
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_Reliable_Bits
Field name TFP_SIP_Video_Reliable_Bits
Explanation Reliability bits for video Jitter and MOS values. Bit 1 Video Jitter DL;
0b0=Not reliable; 0b1=Reliable Bit 2 Video Jitter UL; 0b0=Not reliable;
0b1=Reliable Bit 3 Video Jitter method: 0b0 = RTCP; 0b1 = RTP Bit 4
Video MOS DL; 0b0=Not reliable; 0b1=Reliable Bit 5 Video MOS UL;
Possible values
Exists in db Yes
CCD section [Video Reliable bits]
TFP_SIP_Video_UL_Average_Jitter
Field name TFP_SIP_Video_UL_Average_Jitter
180 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_UL_Average_MOS_x100
Field name TFP_SIP_Video_UL_Average_MOS_x100
Explanation Mean Opinion Score (from uplink video stream) multiplied by 100. The
in Traffic News.
Exists in db Yes
CCD section
TFP_SIP_Video_UL_Last_Used_Codec
Field name TFP_SIP_Video_UL_Last_Used_Codec
Explanation Shows the last used codec of the uplink video stream. RFC 3555.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_UL_Max_Jitter
Field name TFP_SIP_Video_UL_Max_Jitter
Explanation Indicates the maximum video UL Jitter from reliable jitter values in hun-
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_UL_Min_Jitter
Field name TFP_SIP_Video_UL_Min_Jitter
P-DN0687206 Id:0900d805807819d6 181

Issue 2-2
Probes

Explanation Calculated from RTP or from RTCP; Indicates the minimum video UL
(1 x 10-5 s).
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_UL_Min_MOS_x100
Field name TFP_SIP_Video_UL_Min_MOS_x100
Explanation Indicates the minimum MOS experienced during the uplink video
session. Values similarly to Video UL Average MOS x100. The value of
Exists in db Yes
CCD section
TFP_SIP_Video_UL_Number_of_RTCP_RR_Reports
Field name TFP_SIP_Video_UL_Number_of_RTCP_RR_Reports
uplink.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_UL_Number_of_RTCP_SR_Reports
Field name TFP_SIP_Video_UL_Number_of_RTCP_SR_Reports
uplink.
Possible values
Exists in db Yes
CCD section
182 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_SIP_Video_UL_Packets_Lost
Field name TFP_SIP_Video_UL_Packets_Lost
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_UL_Packets_Out_of_Order
Field name TFP_SIP_Video_UL_Packets_Out_of_Order
Explanation Number of video packets out of order uplink. From RTP.
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_UL_Reserved
Field name TFP_SIP_Video_UL_Reserved
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_UL_Standard_Deviation_for_MOS_x100
Field name TFP_SIP_Video_UL_Standard_Deviation_for_MOS_x100
Explanation Standard deviation for MOS video uplink multiplied by 100. The value of
Possible values
Exists in db Yes
CCD section
TFP_SIP_Video_UL_Used_Codecs
Field name TFP_SIP_Video_UL_Used_Codecs
P-DN0687206 Id:0900d805807819d6 183

Issue 2-2
Probes

Explanation Shows the codecs used in the session (video UL). For more information
Possible values
Exists in db Yes
CCD section
5.1.15 SMTP specific fields

TFP_SMTP_Err_Code_1
Field name TFP_SMTP_Err_Code_1
Explanation Error code to TFP_SMTP_Err_Command_1.
Possible values
Exists in db Yes
CCD section [SMTP Cause Code]
TFP_SMTP_Err_Code_2
Field name TFP_SMTP_Err_Code_2
Explanation Error code to TFP_SMTP_Err_Command_2.
Possible values
Exists in db Yes
CCD section [SMTP Cause Code]
TFP_SMTP_Err_Command_1
Field name TFP_SMTP_Err_Command_1
Explanation Command which caused error with response code 4xx-5xx.
Possible values
Exists in db Yes
CCD section
TFP_SMTP_Err_Command_2
Field name TFP_SMTP_Err_Command_2
Explanation Command which caused error with response code 4xx-5xx.
184 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Possible values
Exists in db Yes
CCD section
TFP_SMTP_From
Field name TFP_SMTP_From
Explanation [RFC2821] E-mail address of sender.
Possible values
Exists in db Yes
CCD section
TFP_SMTP_SMTP_Reserved_1
Field name TFP_SMTP_SMTP_Reserved_1
Possible values
Exists in db
CCD section
TFP_SMTP_To
Field name TFP_SMTP_To
Explanation [RFC2821] E-mail address of receiver (first address in To-field).
Possible values
Exists in db Yes
CCD section
TFP_SMTP_User_Name
Field name TFP_SMTP_User_Name
Explanation Login user name if available.
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 185

Issue 2-2
Probes
5.1.16 WAP specific fields

TFP_WAP_Average_Delay
Field name TFP_WAP_Average_Delay
Explanation Average delay in milliseconds of successful responses to WSP/HTTP
GET messages.
Possible values
Exists in db Yes
CCD section
TFP_WAP_GET_Error_Reason
Field name TFP_WAP_GET_Error_Reason
Explanation Reason code of first failed GET-message.
Possible values
Exists in db Yes
CCD section [WAP Cause Code]
TFP_WAP_GET_Fail
Field name TFP_WAP_GET_Fail
Explanation Number of failed GET-messages within the report.
Possible values
Exists in db Yes
CCD section
TFP_WAP_GET_Success
Field name TFP_WAP_GET_Success
Explanation Number of succesful GET-messages within the report.
Possible values
Exists in db Yes
CCD section
TFP_WAP_Host
Field name TFP_WAP_Host
186 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Explanation Name of WWW server. For example: www.nsn.com. From the first
GET-message.
Possible values
Exists in db Yes
CCD section
TFP_WAP_HTTP_Version
Field name TFP_WAP_HTTP_Version
Explanation From HTTP GET message. 1 = 1.0, 2 = 1.1
Possible values
Exists in db Yes
CCD section [HTTP version]
TFP_WAP_Post_Error_Reason
Field name TFP_WAP_Post_Error_Reason
Explanation Reason code of the first failed Post-message.
Possible values
Exists in db Yes
CCD section [WAP Cause Code]
TFP_WAP_Post_Fail
Field name TFP_WAP_Post_Fail
Explanation Number of failed Post-messages within the report.
Possible values
Exists in db Yes
CCD section
TFP_WAP_Post_Success
Field name TFP_WAP_Post_Success
Explanation Number of succesfull Post-messages within the report.
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 187

Issue 2-2
Probes
TFP_WAP_Referer
Field name TFP_WAP_Referer
Explanation From the WSP/HTTP message header (not always available). Method
name is not included in the report (in this case the text: "Referer:" is not
inluded). Referer is acquired from the first GET message.
Possible values
Exists in db Yes
CCD section
TFP_WAP_User_Agent
Field name TFP_WAP_User_Agent
Explanation From the WSP/HTTP message header. Method name is not included.
Possible values
Exists in db Yes
CCD section
TFP_WAP_WAP_Reserved_1
Field name TFP_WAP_WAP_Reserved_1
Possible values
Exists in db Yes
CCD section
TFP_WSP_Connect_Reply
Field name TFP_WSP_Connect_Reply
Explanation ConnectReply = 2, Redirect = 3, Reply (Disconnect.res) = 4, Disconnect
=5
Possible values
Exists in db Yes
CCD section [WSP Connect Reply]
TFP_WSP_Connect_Time
Field name TFP_WSP_Connect_Time
188 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Explanation WSP connection time in milliseconds (gap between WSP connect prim-
itive and response).
Exists in db Yes
CCD section
TFP_WSP_Version
Field name TFP_WSP_Version
Explanation WSP protocol version. The major number of the version is stored in the
high-order 4 bits, and the minor number is stored in the low-order 4 bits.
Possible values
Exists in db Yes
CCD section WSP Version]
5.2 Flow report fields

TFP_<Interface_tag>_ prefix. For example, the TFP_Flow_Delay IDS field is the Delay
column in database table TFP_FLOW_<TFP_Release_Id>_REPORT.
spaces instead of underscores between words. For example, the TFP_Flow_Delay IDS
field is the Delay field in the Traffic News TFP PS Flow event.
dbd_*.conf. Under the TFP_<Interface_tag>_<TFP_Release_Id>_REPORT section,
column name and = symbol.
The following shows the RTT fields:
Traffic News Event type TFP PS Flow

Database table TFP_FLOW_<TFP_Release_Id>_REPORT
Table 5 TFP_GSN_PS_FLOW fields
TFP_Flow_Bytes_IN
Field name TFP_Flow_Bytes_IN
Explanation IN byte count related to the flow. IP header is included.
TFP_Flow_Bytes_IN_Ext, in order to support larger Bytes IN
values in the future. Therefore it is recommended that the
TFP_Flow_Bytes_IN_Ext field be used instead.
P-DN0687206 Id:0900d805807819d6 189

Issue 2-2
Probes
If the value of TFP_Flow_Bytes_IN exceeds 32 bits, it will be

clipped, whereas the TFP_Flow_Bytes_IN_Ext field will contain
the entire value.
Possible values
Exists in db Yes
CCD section
TFP_Flow_Bytes_IN_Ext
Field name TFP_Flow_Bytes_IN_Ext
Explanation IN byte count related to the flow. IP header is included.
Possible values
Exists in db Yes
CCD section
TFP_Flow_Bytes_OUT
Field name TFP_Flow_Bytes_OUT
Explanation OUT byte count related to the flow. IP header is included.
TFP_Flow_Bytes_OUT_Ext, in order to support larger Bytes IN
TFP_Flow_Bytes_OUT_Ext field be used instead.
If the value of TFP_Flow_Bytes_OUT exceeds 32 bits, it will be
clipped, whereas the TFP_Flow_Bytes_OUT_Ext field will contain
the entire value.
Possible values
Exists in db Yes
CCD section
TFP_Flow_Bytes_OUT_Ext
Field name TFP_Flow_Bytes_OUT
Explanation OUT byte count related to the flow. IP header is included.
Possible values
Exists in db Yes
CCD section
TFP_Flow_Delay
Field name TFP_Flow_Delay
190 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Explanation Delay of first TCP reply (in milliseconds).
Possible values
Exists in db Yes
CCD section
TFP_Flow_Direct_Tunnel
Field name TFP_Flow_Direct_Tunnel
Explanation Direct Tunneling can be identified from PDP Context Update (IE: Direct
Tunnel Flags/DTI)
Possible values 0 = no direct tunnel 1 = direct tunnel
Exists in db Yes
CCD section [Direct Tunnel indicator]
TFP_Flow_End_Time_Local_Date
Field name TFP_Flow_End_Time_Local_Date
Explanation Local time and date in BCDTIMESTAMP format. Last packet in a flow
(e.g. TCP FIN packet).
Exists in db Yes
CCD section
TFP_Flow_End_Time_Local_Time
Field name TFP_Flow_End_Time_Local_Time
Explanation Local time and date in BCDTIMESTAMP format. Last packet in a flow
(e.g. TCP FIN packet).
Exists in db Yes
CCD section
TFP_Flow_Flow_Initiator
Field name TFP_Flow_Flow_Initiator
Possible values
Exists in db Yes
P-DN0687206 Id:0900d805807819d6 191

Issue 2-2
Probes
CCD section
TFP_Flow_Flow_Sampling_Rate
Field name TFP_Flow_Flow_Sampling_Rate
Explanation Flow sampling rate. Default value is 1.
Possible values
Exists in db Yes
CCD section
TFP_Flow_Fragmented_Status
Field name TFP_Flow_Fragmented_Status
Explanation Flow fragmented status.
Possible values 1=some flow packets are fragmented 0=no fragmented packets
Exists in db Yes
CCD section [Fragmented_status]
TFP_Flow_GGSN
Field name TFP_Flow_GGSN
each GGSN.
Possible values
Exists in db Yes
CCD section
TFP_Flow_GGSN_Address_For_User_Traffic
Field name TFP_Flow_GGSN_Address_For_User_Traffic
Explanation IP address of GGSN interface which is monitored.
Exists in db Yes
CCD section
TFP_Flow_Imei
Field name TFP_Flow_Imei
192 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Explanation International Mobile Equipment Identity.

Possible values
Exists in db Yes
CCD section
TFP_Flow_Imsi
Field name TFP_Flow_Imsi
than 15 digits.
Possible values
Exists in db Yes
CCD section
TFP_Flow_Interface
Field name TFP_Flow_Interface
Explanation probe monitoring interface. 1=Gi, 2=Gn, 3=Gb, 4= Iu-PS
Possible values
Exists in db Yes
CCD section [Interface]
TFP_Flow_IP_Precedence
Field name TFP_Flow_IP_Precedence
Explanation RFC2474 from IP header.
Possible values
Exists in db Yes
CCD section
TFP_Flow_L4_Destination_Port
Field name TFP_Flow_L4_Destination_Port
Explanation TCP/UDP destination port.
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 193

Issue 2-2
Probes
TFP_Flow_L4_Source_Port
Field name TFP_Flow_L4_Source_Port
Explanation TCP/UDP source port.
Possible values
Exists in db Yes
CCD section
TFP_Flow_Mobile_IP_Address
Field name TFP_Flow_Mobile_IP_Address
Explanation IP address of mobile.
Exists in db Yes
CCD section
TFP_Flow_MSISDN
Field name TFP_Flow_MSISDN
Explanation MSISDN.
Possible values
Exists in db Yes
CCD section
TFP_Flow_NSAPI
Field name TFP_Flow_NSAPI
Possible values
Exists in db Yes
CCD section
TFP_Flow_Packet_Sampling_Rate
Field name TFP_Flow_Packet_Sampling_Rate
Explanation Packet sampling rate. Default value is 1.
Possible values
194 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_Flow_Packets_IN
Field name TFP_Flow_Packets_IN
Explanation IN IP packet count related to the flow.
Possible values
Exists in db Yes
CCD section
TFP_Flow_Packets_IN_Ext
Field name TFP_Flow_Packets_IN_Ext
Explanation IN IP packet count related to the flow.
TFP_Flow_Packets_IN_Ext, in order to support larger Bytes IN
TFP_Flow_Packets_IN_Ext field be used instead.
Possible values
Exists in db Yes
CCD section
TFP_Flow_Packets_OUT
Field name TFP_Flow_Packets_OUT
Explanation OUT IP packet count related to the flow.
Possible values
Exists in db Yes
CCD section
TFP_Flow_Packets_OUT_Ext
Field name TFP_Flow_Packets_OUT_Ext
Explanation OUT IP packet count related to the flow.
TFP_Flow_Packets_OUT_Ext, in order to support larger Bytes IN
TFP_Flow_Packets_OUT_Ext field be used instead.
P-DN0687206 Id:0900d805807819d6 195

Issue 2-2
Probes
Possible values
Exists in db Yes
CCD section
TFP_Flow_Protocol
Field name TFP_Flow_Protocol
Explanation Protocol field from IP header.
Possible values
Exists in db Yes
CCD section
TFP_Flow_RAN
Field name TFP_Flow_RAN
Possible values
Exists in db Yes
CCD section
TFP_Flow_RAN_Address_for_User_Traffic
Field name TFP_Flow_RAN_Address_for_User_Traffic
Possible values
Exists in db Yes
CCD section
TFP_Flow_RAT_Type
Field name TFP_Flow_RAT_Type
Explanation 1 = UTRAN, 2 = GERAN, 3 = WLAN. RAT value is correlated when flow
starts (New RAT during flow does not affect this field).
Possible values
Exists in db Yes
TFP_Flow_Report_Count
Field name TFP_Flow_Report_Count
196 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Explanation The number of flow reports sent to Traffica after midnight. Count is
specific to report type and Traffica connection. Reset at midnight.
Starting from one. Little-Endian byte order used.
Possible values
Exists in db Yes
CCD section
TFP_Flow_Report_Date
Field name TFP_Flow_Report_Date
Possible values
Exists in db Yes
CCD section
TFP_Flow_Report_Id
Field name TFP_Flow_Report_Id
Possible values 285
Exists in db Yes
TFP_Flow_Report_Reason
Field name TFP_Flow_Report_Reason
Explanation Reason for sending report. See triggering rules descriptions.
Possible values
Exists in db Yes
TFP_Flow_Report_Time
Field name TFP_Flow_Report_Time
P-DN0687206 Id:0900d805807819d6 197

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_Flow_Report_UTC_Date
Field name TFP_Flow_Report_UTC_Date
Possible values
Exists in db Yes
CCD section
TFP_Flow_Report_UTC_Time
Field name TFP_Flow_Report_UTC_Time
Exists in db Yes
CCD section
TFP_Flow_Reserved_1
Field name TFP_Flow_Reserved_1
Possible values
Exists in db Yes
CCD section
TFP_Flow_Reserved_2
Field name TFP_Flow_Reserved_2
Possible values
Exists in db Yes
CCD section
TFP_Flow_Sender_Id
Field name TFP_Flow_Sender_Id
198 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Possible values
Exists in db Yes
CCD section
TFP_Flow_Service_IP_Address
Field name TFP_Flow_Service_IP_Address
Explanation IP Address for the service (e.g. HTTP server IP)
Exists in db Yes
CCD section
TFP_Flow_SGSN
Field name TFP_Flow_SGSN
each SGSN.
Possible values
Exists in db Yes
CCD section
TFP_Flow_SGSN_Address_For_User_Traffic
Field name TFP_Flow_SGSN_Address_For_User_Traffic
Explanation IP Address for SGSN (from GGSN point of view) used for user traffic.
Exists in db Yes
CCD section
TFP_Flow_Start_Time_Local_Date
Field name TFP_Flow_Start_Time_Local_Date
tiated the flow.
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 199

Issue 2-2
Probes
TFP_Flow_Start_Time_Local_Time
Field name TFP_Flow_Start_Time_Local_Time
tiated the flow.
Exists in db Yes
CCD section
TFP_Flow_TCP_Flags
Field name TFP_Flow_TCP_Flags
Explanation Cumulative OR of all packets within flow (similar to IPFIX and Cisco
NetFlow).
Possible values
Exists in db Yes
CCD section
TFP_Flow_TCP_Retransmit_IN
Field name TFP_Flow_TCP_Retransmit_IN
Explanation Retransmits in TCP connections incoming. counted from TCP headers;
field.
Possible values
Exists in db Yes
CCD section
TFP_Flow_TCP_Retransmit_OUT
Field name TFP_Flow_TCP_Retransmit_OUT
Explanation Retransmits in TCP connections outgoing. counted from TCP headers;
field.
Possible values
Exists in db Yes
CCD section
200 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_Flow_Vendor_Id
Field name TFP_Flow_Vendor_Id
order used.
Possible values 0-0xFFFFFFFF
Exists in db Yes
TFP_Flow_VLAN_Tag
Field name TFP_Flow_VLAN_Tag
Explanation 802.1q VLAN tag from ethernet framing.
Possible values
Exists in db Yes
CCD section
5.3 Gb interface report fields

The database column names are the same as the IDS field names without the TFP_Gb_
prefix. For example, the TFP_Gb_GMM_Cause IDS field is the GMM_Cause column in
database table TFP_GB_<TFP_Release_Id>_REPORT (TFP_Release_Id = 20 refers
to v2.0 and TFP_Release_Id = 30 refers to v3.0).
"TFP_Gb_GMM_Cause IDS" field is the "GMM Cause" field in Traffic News TFP PS Gb
event.
dbd_*.conf. Under the TFP_Gb_<TFP_Release_Id>_REPORT section, there is a
single-row entry for each table column. The SQL data type appears after the column
name and = symbol.
Traffic News Event type TFP PS Gb

Database table TFP_GB_<TFP_Release_Id>_REPORT
Table 6 TFP_GSN_PS_GB fields
The RTT fields in the Gb interface report are the following:
TFP_Gb_Allocated_Bandwidth
Field name TFP_Gb_Allocated_Bandwidth
P-DN0687206 Id:0900d805807819d6 201

Issue 2-2
Probes
Explanation Allocated bandwidth (in kbits/s); Connection speed that is allocated to

the user. Example: The data connection uses two 64-kbits timeslots; the
value for <Allocated bandwith> is 128. In case the allocated bandwidth
changes, the maximum value is given. Negotiated QoS Peak Through-
put can be put here, but calculation from signalling is preferred. In the
compliance document the probe vendor shall specify the method used.
Possible values Range
Exists in db Yes
CCD section
TFP_Gb_APN
Field name TFP_Gb_APN
Possible values APN
Exists in db Yes
CCD section
TFP_Gb_AttachDetach_Type
Field name TFP_Gb_AttachDetach_Type
Explanation Attach Type or respectively in a detach report Detach Type, indicates
which type of attach/detach is to be performed, see coding above.
(3GPP TS 23.060) Information in Attach Request, Detach Request
(direction: MS to Network) 1 = GPRS Attach only (Type of attach in sig-
nalling: bits 321 = 001, or others 1xx); 2 = GPRS Attach while already
IMSI Attached (similarly bits 321 = 010); 3 = combined GPRS / IMSI
Attach. (011); 11 = GPRS Detach only (001); 12 = IMSI Detach only
(010); 13 = combined GPRS and IMSI Detach (bits = 011, or others
1xx)
Possible values 1-3, 11-13
Exists in db Yes
CCD section [Attach Detach Type]
TFP_Gb_BSC
Field name TFP_Gb_BSC
Explanation Logical field indicating BSC identification number. Fixed number for
each BSC.
Possible values 0-0xFFFE
Exists in db Yes
CCD section
202 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_Gb_BSC_IP_Address
Field name TFP_Gb_BSC_IP_Address
Explanation IP (IPv4 or IPv6) Address of BSC, which address SGSN uses to send
data to BSC. Only available when Gb over IP.
Exists in db Yes
CCD section
TFP_Gb_BSSGP_Cause
Field name TFP_Gb_BSSGP_Cause
Explanation BSSGP Cause; base station system GPRS protocol; 3GPP TS 48.018.
Possible values 1-0xFE
Exists in db Yes
CCD section [BSSGP Cause]
TFP_Gb_Cell
Field name TFP_Gb_Cell
Explanation Cell identification when the signalling ended.
Exists in db Yes
CCD section
TFP_Gb_Collection_End_Date
Field name TFP_Gb_Collection_End_Date
Explanation Timestamp (local time) when the collection for this trigger has been
ended. Used with time based trigger and Context closing triggers.
Possible values
Exists in db Yes
CCD section
TFP_Gb_Collection_End_Time
Field name TFP_Gb_Collection_End_Time
P-DN0687206 Id:0900d805807819d6 203

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_Gb_Collection_Start_Date
Field name TFP_Gb_Collection_Start_Date
started. Used with time based trigger and Context closing triggers.
Possible values
Exists in db Yes
CCD section
TFP_Gb_Collection_Start_Time
Field name TFP_Gb_Collection_Start_Time
Exists in db Yes
CCD section
TFP_Gb_GMM_Cause
Field name TFP_Gb_GMM_Cause
Explanation GPRS Mobility Management Error Cause; coded in 3GPP TS 24.008.
Possible values <0x70
Exists in db Yes
CCD section [GMM Cause]
TFP_Gb_Imei
Field name TFP_Gb_Imei
Explanation International Mobile Equipment Identity (IMEI). Unused (or string end)
is marked with value 0xF. 15 digits.
Possible values 15 digits
Exists in db Yes
204 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
CCD section
TFP_Gb_Imsi
Field name TFP_Gb_Imsi
than 15 digits. The length of the MNC (two or three digits) depends on
the value of the MCC. Unused (or string end) is marked with value 0xF.
E.g. IMSI value = 103254110691735F contains the following informa-
tion:MCC = 103 MNC = 25 MSIN = 4110691735.
Possible values 15 digits maximum.
Exists in db Yes
CCD section
TFP_Gb_Initiator
Field name TFP_Gb_Initiator
Explanation Transaction initiator, indicates who initiated the action, can be either
user or network. E.g. In PDP Context deactivation 1 = User initiated; 3
= SGSN initiated. From signal direction.
Exists in db Yes
CCD section [Initiator]
TFP_Gb_LAC
Field name TFP_Gb_LAC
Explanation Location Area Code when the signalling ended.
Exists in db Yes
CCD section [LAC Names]
TFP_Gb_MCC
Field name TFP_Gb_MCC
Explanation Field contains the Mobile Country Code (MCC) of Cell Global Identifica-
tion (CGI). BCD string content (length in digits): MCC(3) + padding(1).
Unused (or string end) is marked with value 0xF.
Possible values
P-DN0687206 Id:0900d805807819d6 205

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_Gb_MNC
Field name TFP_Gb_MNC
Explanation Field contains the Mobile Network Code (MNC) of Cell Global Identifi-
cation (CGI). BCD string content (length in digits): MNC(2-3) + pad-
ding(1-2). Unused (or string end) is marked with value 0xF.
Exists in db Yes
CCD section
TFP_Gb_Mobile_IP_Address
Field name TFP_Gb_Mobile_IP_Address
Explanation Mobile IP Address using either IPv4 or IPv6.
Exists in db Yes
CCD section
TFP_Gb_Mobile_IP_Address_Originator
Field name TFP_Gb_Mobile_IP_Address_Originator
Explanation From Activate PDP Context request/Requested PDP Address; 1=static,
2=dynamic, 0xFF=empty value.
Exists in db Yes
CCD section [Mobile IP Address Originator]
TFP_Gb_MSISDN
Field name TFP_Gb_MSISDN
Explanation MSISDN, max 40 digits, E.g. MSISDN = 420018000100001F. This field
is expected to be correlated from the Gn interface.
Exists in db Yes
CCD section
206 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_Gb_Negotiated_QoS_10
Field name TFP_Gb_Negotiated_QoS_10
Explanation Quality of Service information element, octet 10. Specified in 3GPP TS
24.008.
Possible values Coded
Exists in db Yes
CCD section
24.008.
Exists in db Yes
CCD section
24.008.
Exists in db Yes
CCD section
24.008.
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 207

Issue 2-2
Probes

24.008.
Exists in db Yes
CCD section
24.008.
Exists in db Yes
CCD section
24.008.
Exists in db Yes
CCD section
24.008.
Exists in db Yes
CCD section
24.008.
208 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Exists in db Yes
CCD section
24.008.
Exists in db Yes
CCD section
24.008.
Exists in db Yes
CCD section
24.008.
Exists in db Yes
CCD section
24.008.
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 209

Issue 2-2
Probes
24.008.
Exists in db Yes
CCD section
24.008.
Exists in db Yes
CCD section
24.008.
Exists in db Yes
CCD section
TFP_Gb_P_TMSI
Field name TFP_Gb_P_TMSI
Explanation Packet TMSI.
Exists in db Yes
CCD section
TFP_Gb_PDP_Context_Activation_Date
Field name TFP_Gb_PDP_Context_Activation_Date
210 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Exists in db Yes
CCD section
TFP_Gb_PDP_Context_Activation_Time
Field name TFP_Gb_PDP_Context_Activation_Time
Exists in db Yes
CCD section
TFP_Gb_RAC
Field name TFP_Gb_RAC
Explanation Routing Area Code when the signalling ended.
Exists in db Yes
CCD section [RAC Names]
TFP_Gb_Radio_Cause
Field name TFP_Gb_Radio_Cause
Explanation Radio specific error cause.
Exists in db Yes
CCD section [Radio Cause]
TFP_Gb_Radio_Priority
Field name TFP_Gb_Radio_Priority
Explanation The radio priority specifies the priority level that the MS shall use at the
lower layers for transmission of data related to a PDP context. Allocates
3 bits: 001 = priority level 1 (highest); 100 = priority level 4 (lowest) and
so forth.
Possible values 3bits
Exists in db Yes
CCD section [Radio Priority]
P-DN0687206 Id:0900d805807819d6 211

Issue 2-2
Probes
TFP_Gb_Report_Count
Field name TFP_Gb_Report_Count
Explanation The number of Gb reports sent to Traffica after midnight. Count is
Exists in db Yes
CCD section
TFP_Gb_Report_Date
Field name TFP_Gb_Report_Date
Explanation Report sending local date.
Possible values
Exists in db Yes
CCD section
TFP_Gb_Report_Id
Field name TFP_Gb_Report_Id
Explanation Report identification
Possible values 257, 262.
Exists in db Yes
TFP_Gb_Report_Reason
Field name TFP_Gb_Report_Reason
Explanation Why the report is delivered: see Report_Id.
Possible values 1, 2, 3, 4, 5, 7, 10, 12, 15, 20, 21, 22, 23, 101.
Exists in db Yes
TFP_Gb_Report_Time
Field name TFP_Gb_Report_Time
212 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Exists in db Yes
CCD section
TFP_Gb_Report_UTC_Date
Field name TFP_Gb_Report_UTC_Date
Explanation Report sending UTC date.
Possible values
Exists in db Yes
CCD section
TFP_Gb_Report_UTC_Time
Field name TFP_Gb_Report_UTC_Time
Explanation Report sending UTC time.
Exists in db Yes
CCD section
TFP_Gb_Requested_QoS_10
Field name TFP_Gb_Requested_QoS_10
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 213

Issue 2-2
Probes
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
214 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
P-DN0687206 Id:0900d805807819d6 215

Issue 2-2
Probes
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
216 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
24.008.
Possible values
Exists in db Yes
CCD section
TFP_Gb_Reserved_1
Field name TFP_Gb_Reserved_1
Possible values
Exists in db Yes
CCD section
TFP_Gb_Reserved_2
Possible values
Exists in db Yes
CCD section
TFP_Gb_Reserved_3
Possible values
Exists in db Yes
CCD section
TFP_Gb_SAPI
Field name TFP_Gb_SAPI
P-DN0687206 Id:0900d805807819d6 217

Issue 2-2
Probes
Explanation Service Access Point Identifier: identifier of the point where the logical
link control (LLC) of the link layer provides services to higher layers.
Possible values 1 = Signalling 2 = Data 5 = Data 7 = SMS 9 = Data 11 = Data
Exists in db Yes
CCD section [SAPI]
TFP_Gb_Sender_Id
Field name TFP_Gb_Sender_Id
Possible values
Exists in db Yes
CCD section
TFP_Gb_Set_Of_Authentication_Params_Quintuplets
Field name TFP_Gb_Set_Of_Authentication_Params_Quintuplets
Possible values
Exists in db Yes
CCD section
TFP_Gb_Set_Of_Authentication_Params_Triplets
Field name TFP_Gb_Set_Of_Authentication_Params_Triplets
Possible values
Exists in db Yes
CCD section
TFP_Gb_SGSN
Field name TFP_Gb_SGSN
Explanation A logical field indicating SGSN identification number. Fixed number for
each SGSN.
Exists in db Yes
CCD section
218 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_Gb_SGSN_IP_Address
Field name TFP_Gb_SGSN_IP_Address
Explanation IP Address of SGSN, which address the BSC uses to send data to
SGSN. Only available when Gb over IP.
Exists in db Yes
CCD section
TFP_Gb_Signalling_Ended_Date
Field name TFP_Gb_Signalling_Ended_Date
Explanation A timestamp for the last message that was needed to complete the Gb
report.
Possible values
Exists in db Yes
CCD section
TFP_Gb_Signalling_Ended_Time
Field name TFP_Gb_Signalling_Ended_Time
Explanation A timestamp for the last message that was needed to complete the Gb
report.
Exists in db Yes
CCD section
TFP_Gb_Signalling_Incomplete
Field name TFP_Gb_Signalling_Incomplete
Explanation Indicates whether there are missing messages in signalling: signalling
completed (0) or signalling incomplete (1).
Exists in db Yes
CCD section [Signalling Incomplete]
TFP_Gb_Signalling_Started_Date
Field name TFP_Gb_Signalling_Started_Date
P-DN0687206 Id:0900d805807819d6 219

Issue 2-2
Probes

Explanation A timestamp for the first message that was needed to initiate a Gb
report.
Possible values
Exists in db Yes
CCD section
TFP_Gb_Signalling_Started_Time
Field name TFP_Gb_Signalling_Started_Time
Explanation A timestamp for the first message that was needed to initiate a Gb
report.
Exists in db Yes
CCD section
TFP_Gb_SM_Cause
Field name TFP_Gb_SM_Cause
Explanation Session Management Success / Error Cause
Possible values 8 = Operator Determined Barring 24 = MBMS bearer capabilities
insufficient for the service 25 = LLC or SNDCP failure (A/Gb mode only)
26 = Insufficient resources 27 = Missing or unknown APN 28 =
Unknown PDP address or PDP type 29 = User authentication fai
Exists in db Yes
CCD section [SM Cause]
TFP_Gb_SNDCP_NSAPI
Field name TFP_Gb_SNDCP_NSAPI
Explanation Sub network dependent convergence protocol, network layer service
access point identifier.
Exists in db Yes
CCD section
TFP_Gb_Suspend_Resume_Cause
Field name TFP_Gb_Suspend_Resume_Cause
220 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Explanation From Suspend-nack or Resume-nack (3GPP 48.018)

Possible values 0-0x28
Exists in db Yes
CCD section [Suspend Resume Cause]
TFP_Gb_Teardown_Ind
Field name TFP_Gb_Teardown_Ind
Explanation The tear down indicator information element may be included in the
DEACTIVATE PDP CONTEXT REQUEST message in order to indicate
whether only the PDP context associated with this specific TI or all
active PDP contexts sharing the same PDP address as the PDP context
associated with this specific TI shall be deactivated. If the tear down
indicator information element is not included in the DEACTIVATE PDP
CONTEXT REQUEST message, only the PDP context associated with
this specific TI shall be deactivated. 0 = tear down not requested, 1 =
tear down requested
Exists in db Yes
CCD section [Teardown ind]
TFP_Gb_TLLI
Field name TFP_Gb_TLLI
Explanation Foreign, Local or Random TLLI, Temporary Logical Link Identity; tem-
porary identifier, which unambiguously identifies the logical link
between GPRS mobile station and SGSN within one RA in the LLC
level. TLLI is defined in 3GPP TS 23.003.
Possible values
Exists in db Yes
CCD section
TFP_Gb_Total_Bytes_Downlink
Field name TFP_Gb_Total_Bytes_Downlink
Explanation The total amount of user data transmitted (in bytes) downlink during the
lifetime of the PDP context. (Available only in report due to PDP Context
deactivation).
g The 64-bit TFP_Gb_Total_Bytes_Downlink replaces the 32-bit
TFP_Gb_Total_Bytes_Downlink_High and
TFP_Gb_Total_Bytes_Downlink_Low fields, to improve the usabil-
ity of the field. The 64-bit TFP_Gb_Total_Bytes_Downlink field
P-DN0687206 Id:0900d805807819d6 221

Issue 2-2
Probes
should be preferred, because the 32-bit fields will be removed from

the adaptation in the future.
Possible values 0x0-0xFFFFFFFFFFFFFFFF
Exists in db Yes
CCD section
TFP_Gb_Total_Bytes_Downlink_High
Field name TFP_Gb_Total_Bytes_Downlink_High
Explanation The upper 32 bits of the value of the total amount of user data transmit-
ted (in bytes) downlink during the lifetime of the PDP context. (Available
only in report due to PDP Context deactivation).
Exists in db Yes
CCD section
TFP_Gb_Total_Bytes_Downlink_Low
Field name TFP_Gb_Total_Bytes_Downlink_Low
Explanation The lower 32 bits of the value of the total amount of user data transmit-
ted (in bytes) downlink during the lifetime of the PDP context. (Available
If the total amount of bytes is less than 0xFFFFFFFF, the value of this
field equals that of the 64-bit TFP_Gb_Total_Bytes_Downlink, and the
field TFP_Gb_Total_Bytes_Downlink_High will equal 0.
Exists in db Yes
CCD section
TFP_Gb_Total_Bytes_Uplink
Field name TFP_Gb_Total_Bytes_Uplink
222 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Explanation The total amount of user data transmitted (in bytes) uplink during the
lifetime of the PDP context. (Available only in report due to PDP Context
deactivation).
g The 64-bit TFP_Gb_Total_Bytes_Uplink replaces the 32-bit
TFP_Gb_Total_Bytes_Uplink_High and
TFP_Gb_Total_Bytes_Uplink_Low fields, to improve the usability of
the field. The 64-bit TFP_Gb_Total_Bytes_Uplink field should be
preferred, because the 32-bit fields will be removed from the adap-
tation in the future.
Exists in db Yes
CCD section
TFP_Gb_Total_Bytes_Uplink_High
Field name TFP_Gb_Total_Bytes_Uplink_High
Explanation The upper 32 bits of the value of the total amount of user data transmit-
ted (in bytes) uplink during the lifetime of the PDP context. (Available
Exists in db Yes
CCD section
TFP_Gb_Total_Bytes_Uplink_Low
Field name TFP_Gb_Total_Bytes_Uplink_Low
Explanation The lower 32 bits of the amount of user data transmitted (in bytes) uplink
during the lifetime of the PDP context. (Available only in report due to
PDP Context deactivation).
field equals that of the 64-bit TFP_Gb_Total_Bytes_Uplink, and the field
TFP_Gb_Total_Bytes_Uplink_High will equal 0.
P-DN0687206 Id:0900d805807819d6 223

Issue 2-2
Probes

Exists in db Yes
CCD section
TFP_Gb_Update_Type
Field name TFP_Gb_Update_Type
Explanation The area the updating procedure is associated with. Possible values:
0=RA updating, 1=combined RA/LA updating, 2=combined RA/LA
updating with IMSI attach, 3=periodic updating. 3GPP TS 24.008.
Possible values 0, 1, 2, 3
Exists in db Yes
CCD section [Update type]
TFP_Gb_User_Data_Bytes_Downlink
Field name TFP_Gb_User_Data_Bytes_Downlink
Explanation Data amount in bytes transferred downlink since the previous Gb report
sent to Traffica (same PDP Context) Data amount from LLC layer and
above. Data amount in bytes transferred uplink since the previous Gb
report sent to Traffica (same PDP Context).
g The 64-bit TFP_Gb_User_Data_Bytes_Downlink replaces the 32-
bit TFP_Gb_User_Data_Bytes_Downlink_High and
TFP_Gb_User_Data_Bytes_Downlink_Low fields, to improve the
usability of the field. The TFP_Gb_User_Data_Bytes_Downlink
field should be preferred, because the old fields will be removed in
the future.
Exists in db Yes
CCD section
TFP_Gb_User_Data_Bytes_Downlink_High
Field name TFP_Gb_User_Data_Bytes_Downlink_High
Explanation The upper 32 bits of the value of the data amount in bytes transferred
downlink since the previous Gb report sent to Traffica (same PDP
Context) Data amount from LLC layer and above. Data amount in bytes
transferred uplink since the previous Gb report sent to Traffica (same
PDP Context).
224 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

usability of the field. The 64-bit
TFP_Gb_User_Data_Bytes_Downlink field should be preferred,
because the 32-bit fields will be removed from the adaptation in the
future.
Exists in db Yes
CCD section
TFP_Gb_User_Data_Bytes_Downlink_Low
Field name TFP_Gb_User_Data_Bytes_Downlink_Low
Explanation The lower 32 bits of the data amount in bytes transferred downlink since
the previous Gb report sent to Traffica (same PDP Context) Data
amount from LLC layer and above. Data amount in bytes transferred
uplink since the previous Gb report sent to Traffica (same PDP Con-
text).
field equals that of the 64-bit TFP_Gb_User_Data_Bytes_Downlink,
and the field TFP_Gb_User_Data_Bytes_Downlink_High will equal 0.
TFP_Gb_User_Data_Bytes_Downlink field should be preferred,
future.
Exists in db Yes
CCD section
TFP_Gb_User_Data_Bytes_Uplink
Field name TFP_Gb_User_Data_Bytes_Uplink
Explanation Data amount in bytes transferred uplink since the previous Gb report
sent to Traffica (same PDP Context). Data amount from LLC layer and
above. Available in BSSGP UL-UNITDATA/ LLC-PDU. Data amount in
bytes transferred uplink since the previous Gb report sent to Traffica
(same PDP Context).
g The 64-bit TFP_Gb_User_Data_Bytes_Uplink replaces the 32-bit
TFP_Gb_User_Data_Bytes_Uplink_High and
TFP_Gb_User_Data_Bytes_Uplink_Low fields, to improve the
P-DN0687206 Id:0900d805807819d6 225

Issue 2-2
Probes
usability of the field. The 64-bit TFP_Gb_User_Data_Bytes_Uplink

field should be preferred, because the 32-bit fields will be removed
from the adaptation in the future.
Exists in db Yes
CCD section
TFP_Gb_User_Data_Bytes_Uplink_High
Field name TFP_Gb_User_Data_Bytes_Uplink_High
Explanation The upper 32 bits of the data amount in bytes transferred uplink since
the previous Gb report sent to Traffica (same PDP Context). Data
amount from LLC layer and above. Available in BSSGP UL-UNITDATA/
LLC-PDU. Data amount in bytes transferred uplink since the previous
Gb report sent to Traffica (same PDP Context).
Exists in db Yes
CCD section
TFP_Gb_User_Data_Bytes_Uplink_Low
Field name TFP_Gb_User_Data_Bytes_Uplink_Low
Explanation The lower 32 bits of the data amount in bytes transferred uplink since
the previous Gb report sent to Traffica (same PDP Context). Data
amount from LLC layer and above. Available in BSSGP UL-UNITDATA/
LLC-PDU. Data amount in bytes transferred uplink since the previous
Gb report sent to Traffica (same PDP Context).
field equals that of the 64-bit TFP_Gb_User_Data_Bytes_Uplink, and
the field TFP_Gb_User_Data_Bytes_Uplink_High will equal 0.
226 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_Gb_Vendor_Id
Field name TFP_Gb_Vendor_Id
order used.
Possible values Nokia Siemens Networks specified
Exists in db Yes
5.4 Gn interface report fields

The database column names are the same as the IDS field names without the TFP_Gn_
prefix. For example, the "TFP_Gn_APN IDS" field is the "APN" column in database table
"TFP_GN_<TFP_Release_Id>_REPORT" (TFP_Release_Id = 20 refers to v2.0 and
TFP_Release_Id = 30 refers to v3.0).
spaces instead of underscores between words. For example, the "TFP_Gn_APN IDS"
field is "APN" field in Traffic News TFP PS Gn event.
The following shows the RTT fields:
Traffic News Event type TFP PS Gn

Database table TFP_GN_<TFP_Release_Id>_REPORT
Table 7 TFP_GSN_PS_GN fields
TFP_Gn_APN
Field name TFP_Gn_APN
Possible values APN
Exists in db Yes
CCD section
TFP_Gn_Cell_Identity
Field name TFP_Gn_Cell_Identity
P-DN0687206 Id:0900d805807819d6 227

Issue 2-2
Probes

Explanation Cell Identity of the CGI when the PDP context is created. Available in
Rel-6.
Possible values
Exists in db Yes
CCD section
TFP_Gn_User_LAC
Field name TFP_Gn_User_LAC
Explanation LAC where the user is currently registered. From Create PDP Context
Request, IE User Location Information. Available in Rel-6.
Possible values
Exists in db Yes
CCD section
TFP_Gn_Charging_Characteristics
Field name TFP_Gn_Charging_Characteristics
Explanation Charging characteristics applied to the PDP Context (defined in 3GPP
TS 32.298).
Possible values 0x0-0xFFFF
Exists in db Yes
CCD section
TFP_Gn_Charging_Gateway_Address
Field name TFP_Gn_Charging_Gateway_Address
Explanation The Charging Gateway Address information element contains an Ipv4
or Ipv6 address of a Charging Gateway (defined in 3GPP TS 29.060).
Exists in db Yes
CCD section
TFP_Gn_Charging_Id
Field name TFP_Gn_Charging_Id
Explanation Charging Identification; This field contains the charging index which
identifies the PDP context. Value is received from GGSN in PDP
228 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
context creation, and it's valid during the whole PDP context (even if
SGSN changes). Information is used for charging record correlation in
Billing System.
Possible values 0x0-0xFFFFFFFF
Exists in db Yes
CCD section
TFP_Gn_Collection_End_Date
Field name TFP_Gn_Collection_End_Date
Exists in db Yes
CCD section
TFP_Gn_Collection_End_Time
Field name TFP_Gn_Collection_End_Time
Exists in db Yes
CCD section
TFP_Gn_Collection_Start_Date
Field name TFP_Gn_Collection_Start_Date
Exists in db Yes
CCD section
TFP_Gn_Collection_Start_Time
Field name TFP_Gn_Collection_Start_Time
P-DN0687206 Id:0900d805807819d6 229

Issue 2-2
Probes

Exists in db Yes
CCD section
TFP_Gn_Direct_Tunnel
Field name TFP_Gn_Direct_Tunnel
Explanation 0 = no direct tunne l1 = direct tunnel Direct Tunneling can be identified
from PDP Context Update (IE: Direct Tunnel Flags/DTI)
Possible values
Exists in db Yes
CCD section [Direct Tunnel Indicator]
TFP_Gn_Geographic_Location_Type
Field name TFP_Gn_Geographic_Location_Type
Explanation From Create PDP Context Request, IE User Location Information field
Geographic Location Type. Available in Rel-6. 0 = CI is available, 1 =
SAC is available.
Possible values
Exists in db Yes
CCD section [Geographic Location Type]
TFP_Gn_GGSN_Address_IP
Field name TFP_Gn_GGSN_Address_IP
Explanation GGSN Address, taken from IP layer. This is the only GGSN address in
case of failed initialization.
Exists in db Yes
CCD section
TFP_Gn_GSN
Field name TFP_Gn_GSN
Explanation Logical field indicating GSN identification number. Fixed number for
each GSN. GSN is GGSN or in case of SGSN Context Request,
another SGSN.
230 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_Gn_GSN_Address_For_Signalling
Field name TFP_Gn_GSN_Address_For_Signalling
Explanation IP Address for GGSN (from SGSN point of view) or other SGSN used
for Signalling.
Exists in db Yes
CCD section
TFP_Gn_GSN_Address_For_User_Traffic
Field name TFP_Gn_GSN_Address_For_User_Traffic
Explanation IP Address for GGSN (from SGSN point of view) or other SGSN used
for user traffic.
Exists in db Yes
CCD section
TFP_Gn_GTP_Cause
Field name TFP_Gn_GTP_Cause
Explanation GTP Cause; specified in the GTP message table, in 3GPP TS 29.060.
Exists in db Yes
CCD section [GTP Cause]
TFP_Gn_GTP_Data_Packets_Downlink
Field name TFP_Gn_GTP_Data_Packets_Downlink
Explanation Amount of GTP data packets sent in downlink direction (GTP-U mes-
sages). Replaces TFP_Gn_GTP_Data_Packets_Sent_UL_Low in TFP
PS v2.0.
g The 64-bit TFP_Gn_GTP_Data_Packets_Downlink replaces the
32-bit TFP_Gn_GTP_Data_Packets_Downlink_High and
TFP_Gn_GTP_Data_Packets_Downlink_Low fields, to improve the
TFP_Gn_GTP_Data_Packets_Downlink field should be preferred,
P-DN0687206 Id:0900d805807819d6 231

Issue 2-2
Probes
future.
Exists in db Yes
CCD section
TFP_Gn_GTP_Data_Packets_Downlink_High
Field name TFP_Gn_GTP_Data_Packets_Downlink_High
Explanation The upper 32 bits of the amount of GTP data packets sent in downlink
direction (GTP-U messages). Replaces
TFP_Gn_GTP_Data_Packets_Sent_UL_High in TFP PS v2.0.
future.
Exists in db Yes
CCD section
TFP_Gn_GTP_Data_Packets_Downlink_Low
Field name TFP_Gn_GTP_Data_Packets_Downlink_low
Explanation The lower 32 bits of the amount of GTP data packets sent in downlink
TFP_Gn_GTP_Data_Packets_Sent_UL_Low in TFP PS v2.0.
field equals that of the 64-bit TFP_Gn_GTP_Data_Packets_Downlink,
and the field TFP_Gn_GTP_Data_Packets_Downlink_High will equal
0.
future.
Exists in db Yes
CCD section
232 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_Gn_GTP_Data_Packets_Uplink
Field name TFP_Gn_GTP_Data_Packets_Uplink
Explanation Amount of GTP data packets sent in uplink direction (GTP-U mes-
sages). Replaces TFP_Gn_GTP_Data_Packets_Sent_UL_Low in TFP
PS v2.0.
g The 64-bit TFP_Gn_GTP_Data_Packets_Uplink replaces the 32-
bit TFP_Gn_GTP_Data_Packets_Uplink_High and
TFP_Gn_GTP_Data_Packets_Uplink_Low fields, to improve the
TFP_Gn_GTP_Data_Packets_Uplink field should be preferred,
future.
Exists in db Yes
CCD section
TFP_Gn_GTP_Data_Packets_Uplink_High
Field name TFP_Gn_GTP_Data_Packets_Uplink_High
Explanation The upper 32 bits of the amount of GTP data packets sent in uplink
TFP_Gn_GTP_Data_Packets_Sent_UL_High in TFP PS v2.0.
future.
Exists in db Yes
CCD section
TFP_Gn_GTP_Data_Packets_Uplink_Low
Field name TFP_Gn_GTP_Data_Packets_Uplink_low
Explanation The lower 32 bits of the amount of GTP data packets sent in uplink
TFP_Gn_GTP_Data_Packets_Sent_UL_Low in TFP PS v2.0.
P-DN0687206 Id:0900d805807819d6 233

Issue 2-2
Probes
field equals that of the 64-bit TFP_Gn_GTP_Data_Packets_Uplink, and
the field TFP_Gn_GTP_Data_Packets_Uplink_High will equal 0.
future.
Exists in db Yes
CCD section
TFP_Gn_GTP_Tunneled_Protocol
Field name TFP_Gn_GTP_Tunneled_Protocol
Possible values
Exists in db Yes
CCD section
TFP_Gn_GTP_User_Data_Bytes_Downlink
Field name TFP_Gn_GTP_User_Data_Bytes_Downlink
Explanation Amount of GTP data in bytes sent in downlink direction (GTP-U mes-
sages, counted in bytes). Available in GTP Header: length (= payload
without GTP header).
g The 64-bit TFP_Gn_GTP_User_Data_Bytes_Downlink replaces
the 32-bit TFP_Gn_GTP_User_Data_Bytes_Downlink_High and
TFP_Gn_GTP_User_Data_Bytes_Downlink_Low fields, to improve
the usability of the field. The 64-bit
TFP_Gn_GTP_User_Data_Bytes_Downlink field should be pre-
ferred, because the 32-bit fields will be removed from the adaptation
in the future.
Exists in db Yes
CCD section
TFP_Gn_GTP_User_Data_Bytes_Downlink_High
Field name TFP_Gn_GTP_User_Data_Bytes_Downlink_High
234 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Explanation The upper 32 bits of the amount of GTP data in bytes sent in downlink
direction (GTP-U messages, counted in bytes). Available in GTP
Header: length (= payload without GTP header).
in the future.
Exists in db Yes
CCD section
TFP_Gn_GTP_User_Data_Bytes_Downlink_Low
Field name TFP_Gn_GTP_User_Data_Bytes_Downlink_low
Explanation The lower 32 bits of the amount of GTP data in bytes sent in downlink
Header: length (= payload without GTP header).
field equals that of the 64-bit
TFP_Gn_GTP_User_Data_Bytes_Downlink, and the field
TFP_Gn_GTP_User_Data_Bytes_Downlink_High will equal 0.
in the future.
Exists in db Yes
CCD section
TFP_Gn_GTP_User_Data_Bytes_Uplink
Field name TFP_Gn_GTP_User_Data_Bytes_Uplink_low
Explanation Amount of GTP data in bytes sent in uplink direction (GTP-U messages,
counted in bytes). Available in GTP Header: length (= payload without
GTP header) (GTP Header is specified in 3GPP 29.060).
g The 64-bit TFP_Gn_GTP_User_Data_Bytes_Uplink replaces the
32-bit TFP_Gn_GTP_User_Data_Bytes_Uplink_High and
TFP_Gn_GTP_User_Data_Bytes_Uplink_Low fields, to improve
P-DN0687206 Id:0900d805807819d6 235

Issue 2-2
Probes

TFP_Gn_GTP_User_Data_Bytes_Uplink field should be preferred,
future.
Exists in db Yes
CCD section
TFP_Gn_GTP_User_Data_Bytes_Uplink_High
Field name TFP_Gn_GTP_User_Data_Bytes_Uplink_High
Explanation The upper 32 bits of the value of the amount of GTP data in bytes sent
in uplink direction (GTP-U messages, counted in bytes). Available in
GTP Header: length (= payload without GTP header) (GTP Header is
specified in 3GPP 29.060).
future.
Exists in db Yes
CCD section
TFP_Gn_GTP_User_Data_Bytes_Uplink_Low
Field name TFP_Gn_GTP_User_Data_Bytes_Uplink_low
Explanation The lower 32 bits of the amount of GTP data in bytes sent in uplink
Header: length (= payload without GTP header) (GTP Header is speci-
fied in 3GPP 29.060).
field equals that of the 64-bit TFP_Gn_GTP_User_Data_Bytes_Uplink,
and the field TFP_Gn_GTP_User_Data_Bytes_Uplink_High will equal
0.
future.
236 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Exists in db Yes
CCD section
TFP_Gn_Imei
Field name TFP_Gn_Imei
Explanation International Mobile Equipment Identity (IMEI).
Exists in db Yes
CCD section
TFP_Gn_Imsi
Field name TFP_Gn_Imsi
For example, IMSI value = 103254110691735F contains the following
information:MCC = 103 MNC = 25 MSIN = 4110691735.
Exists in db Yes
CCD section
TFP_Gn_Initiator
Field name TFP_Gn_Initiator
user or network. E.g. in PDP Context deletion. 3 = SGSN initiated; 4 =
GGSN initiated. From signal direction.
Possible values 3,4
Exists in db Yes
TFP_Gn_LAC
Field name TFP_Gn_LAC
Explanation LAC, Location Area Code from Routing Area Identity of the SGSN
where the MS is registered when the signalling started.
P-DN0687206 Id:0900d805807819d6 237

Issue 2-2
Probes
Possible values 0-0xFFF

Exists in db Yes
TFP_Gn_Linked_NSAPI
Field name TFP_Gn_Linked_NSAPI
Explanation Linked NSAPI; Indicates the NSAPI assigned to any one of the already
activated PDP contexts for this PDP address and APN.
Possible values 0-0xF
Exists in db Yes
CCD section
TFP_Gn_MCC
Field name TFP_Gn_MCC
Explanation MCC, Mobile Country Code from Routing Area Identity of the SGSN
where the MS is registered.
Exists in db Yes
CCD section
TFP_Gn_MCC_MNC
Field name TFP_Gn_MCC_MNC
Explanation MCC and MNC in one field. 3 digits for MCC and max 3 digits for MNC.
Availability as in TFP_Gn_MCC and TFP_Gn_MNC
Exists in db Yes
CCD section
TFP_Gn_MNC
Field name TFP_Gn_MNC
Explanation MNC, Mobile Network Code from Routing Area Identity of the SGSN
where the MS is registered.
Exists in db Yes
CCD section
238 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_Gn_Mean_Throughput_Downlink
Field name TFP_Gn_Mean_Throughput_Downlink
Explanation Mean throughput in kbit/s for downlink traffic. For trigger 7 the mean
value is calculated for the entire session, for trigger 5 the mean value is
calculated for the delta time.
Possible values
Exists in db Yes
CCD section
TFP_Gn_Mean_Throughput_Uplink
Field name TFP_Gn_Mean_Throughput_Uplink
Explanation Mean throughput in kbit/s for uplink traffic. For trigger 7 the mean value
is calculated for the entire session, for trigger 5 the mean value is cal-
culated for the delta time.
Possible values
Exists in db Yes
CCD section
TFP_Gn_Mobile_IP_Address
Field name TFP_Gn_Mobile_IP_Address
Explanation Mobile IP Address using either IPv4 or IPv6. (IPv4 or IPv6 Address in
End user address IE).
Exists in db Yes
TFP_Gn_Mobile_IP_Address_Originator
Field name TFP_Gn_Mobile_IP_Address_Originator
Explanation From Create PDP Context request; 1=static, 2=dynamic, 0xFF=empty
value: Dynamic = the end user address is not defined in the Create PDP
Context Request message (If PDP Type Organisation = ETSI and PDP
Type Number = 1, the End User Address is negotiated later as part of
the PPP protocol.)
Possible values 1,2
Exists in db Yes
P-DN0687206 Id:0900d805807819d6 239

Issue 2-2
Probes
TFP_Gn_MSISDN
Field name TFP_Gn_MSISDN
Explanation MSISDN, 40 digits maximum, for example, MSISDN =
420018000100001F.
Exists in db Yes
CCD section
TFP_Gn_Negotiated_QoS_10
Field name TFP_Gn_Negotiated_QoS_10
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
240 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 241

Issue 2-2
Probes

24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
242 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 243

Issue 2-2
Probes
TFP_Gn_NSAPI
Field name TFP_Gn_NSAPI
Possible values 0x0-0xFF
Exists in db Yes
CCD section
TFP_Gn_P_TMSI
Field name TFP_Gn_P_TMSI
Exists in db Yes
CCD section
TFP_Gn_Password
Field name TFP_Gn_Password
Explanation Password from Create PDP Context Request/ IE Protocol Configuration
Options.
Possible values Text field.
Exists in db Yes
CCD section
TFP_Gn_PDP_Address
Field name TFP_Gn_PDP_Address
Explanation PDP Address from PDP Context IE (PDP Address).
Exists in db Yes
CCD section
TFP_Gn_PDP_Context_Activation_Date
Field name TFP_Gn_PDP_Context_Activation_Date
Explanation Timestamp (local time) for Create PDP Context Response.
244 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Exists in db Yes
CCD section
TFP_Gn_PDP_Context_Activation_Time
Field name TFP_Gn_PDP_Context_Activation_Time
Explanation Timestamp (local time) for Create PDP Context Response.
Exists in db Yes
CCD section
TFP_Gn_Peak_Throughput_Downlink
Field name TFP_Gn_Peak_Throughput_Downlink
Explanation Peak throughput in kbit/s for downlink traffic. For trigger 7 the peak
value is calculated from the entire session, for trigger 5 the peak value
is calculated from the delta time. The sampling value used to determine
the peak value is provided in the vendor specific compliancy document.
Possible values
Exists in db Yes
CCD section
TFP_Gn_Peak_Throughput_Uplink
Field name TFP_Gn_Peak_Throughput_Uplink
Explanation Peak throughput in kbit/s for uplink traffic. For trigger 7 the peak value
is calculated from the entire session, for trigger 5 the peak value is cal-
culated from the delta time. The sampling value used to determine the
peak value is provided in the vendor specific compliancy document.
Possible values
Exists in db Yes
CCD section
TFP_Gn_RAC
Field name TFP_Gn_RAC
Explanation RAC, Routing Area Code from Routing Area Identity of the SGSN where
the MS is registered when the signalling started.
P-DN0687206 Id:0900d805807819d6 245

Issue 2-2
Probes
Exists in db Yes
TFP_Gn_Radio_Priority
Field name TFP_Gn_Radio_Priority
Explanation Contains the radio priority level that the MS uses when accessing the
network for the transmission of uplink user data for a PDP context as
identified by NSAPI.
Possible values 3 bits
Exists in db Yes
TFP_Gn_RAN
Field name TFP_Gn_RAN
Exists in db Yes
CCD section
TFP_Gn_RAN_Address_For_User_Traffic
Field name TFP_Gn_RAN_Address_For_User_Traffic
Exists in db Yes
CCD section
TFP_Gn_RAT_Type
Field name TFP_Gn_RAT_Type
Explanation Shows the Radio Access Technology currently serving. 1=UTRAN,
2=GERAN; possible values depend on Release version.
Possible values 1,2
Exists in db Yes
246 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_Gn_Report_Count
Field name TFP_Gn_Report_Count
Explanation The number of Gn reports sent to Traffica after midnight. Count is
Exists in db Yes
CCD section
TFP_Gn_Report_Date
Field name TFP_Gn_Report_Date
Explanation Report sending local date in BCDTIMESTAMP format.
Exists in db Yes
CCD section
TFP_Gn_Report_Id
Field name TFP_Gn_Report_Id
Possible values 260, 264, 289
Exists in db Yes
TFP_Gn_Report_Reason
Field name TFP_Gn_Report_Reason
Explanation The reason the report is delivered: see TFP_Gn_Report_Id.
Possible values 3,4,5,7,16,20,26
Exists in db Yes
TFP_Gn_Report_Time
Field name TFP_Gn_Report_Time
P-DN0687206 Id:0900d805807819d6 247

Issue 2-2
Probes
Explanation Report sending local time in BCDTIMESTAMP format.

Exists in db Yes
CCD section
TFP_Gn_Report_UTC_Date
Field name TFP_Gn_Report_UTC_Date
Explanation Report sending UTC date in BCDTIMESTAMP format.
Exists in db Yes
CCD section
TFP_Gn_Report_UTC_Time
Field name TFP_Gn_Report_UTC_Time
Explanation Report sending UTC time in BCDTIMESTAMP format.
Exists in db Yes
CCD section
TFP_Gn_Requested_QoS_10
Field name TFP_Gn_Requested_QoS_10
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
248 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 249

Issue 2-2
Probes

24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
250 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 251

Issue 2-2
Probes
24.008.
Possible values
Exists in db Yes
CCD section
TFP_Gn_Reserved_1
Field name TFP_Gn_Reserved_1
Exists in db Yes
CCD section
TFP_Gn_Reserved_2
Exists in db Yes
CCD section
TFP_Gn_Reserved_3
Exists in db Yes
CCD section
TFP_Gn_SAC
Field name TFP_Gn_SAC
252 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Explanation Service Area Code, where the user is currently registered. Available in
Rel-6.
Possible values
Exists in db Yes
CCD section
TFP_Gn_SAPI
Field name TFP_Gn_SAPI
Explanation Service Access Point Identifier: identifier of the point where the logical
link control (LLC) of the link layer provides services to higher layers.
Exists in db Yes
CCD section [SAPI]
TFP_Gn_Selection_mode
Field name TFP_Gn_Selection_mode
Explanation indicates the origin of the APN in the message. 0 = MS or network
provided APN, subscribed verified 1 = MS provided APN, subscription
not verified 2 or 3 = Network provided APN, subscription not verified.
Possible values 0,1,2,3
Exists in db Yes
CCD section [Selection Mode]
TFP_Gn_Sender_Id
Field name TFP_Gn_Sender_Id
Exists in db Yes
CCD section
TFP_Gn_SGSN
Field name TFP_Gn_SGSN
each SGSN. Can be provided only if the vendor is able to deliver con-
figured values.
P-DN0687206 Id:0900d805807819d6 253

Issue 2-2
Probes

Exists in db Yes
CCD section
TFP_Gn_SGSN_Address_For_Signalling
Field name TFP_Gn_SGSN_Address_For_Signalling
Explanation IP Address for SGSN (from GGSN point of view) used for Signalling.
Exists in db Yes
CCD section
TFP_Gn_SGSN_Address_For_User_Traffic
Field name TFP_Gn_SGSN_Address_For_User_Traffic
Explanation IP Address for SGSN (from GGSN point of view) used for user traffic.
Exists in db Yes
CCD section
TFP_Gn_Signalling_Ended_Date
Field name TFP_Gn_Signalling_Ended_Date
Explanation A timestamp for the last message that was needed to complete the Gn
report. E.g. in PDP Context activation, the timestamp for the Create
PDP Context Response. Local time is used.
Possible values
Exists in db Yes
CCD section
TFP_Gn_Signalling_Ended_Time
Field name TFP_Gn_Signalling_Ended_Time
Explanation A timestamp for the last message that was needed to complete the Gn
PDP Context Response. Local time is used.
Exists in db Yes
CCD section
254 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_Gn_Signalling_Incomplete
Field name TFP_Gn_Signalling_Incomplete
Possible values 0,1
Exists in db Yes
TFP_Gn_Signalling_Started_Date
Field name TFP_Gn_Signalling_Started_Date
Explanation A timestamp for the first message that was needed to initiate a Gn
PDP Context Request. Local time is used.
Exists in db Yes
CCD section
TFP_Gn_Signalling_Started_Time
Field name TFP_Gn_Signalling_Started_Time
Explanation A timestamp for the first message that was needed to initiate a Gn
PDP Context Request. Local time is used.
Exists in db Yes
CCD section
TFP_Gn_Teardown_ind
Field name TFP_Gn_Teardown_ind
Explanation With value '1', shows that all PDP contexts that share the same PDP
address with the PDP context identified by the NSAPI included in the
Delete PDP Context Request Message will be torn down. With value '0',
shows that only the PDP context identified by the NSAPI included in the
Delete PDP context Request will be torn down.
Possible values 0,1
Exists in db Yes
P-DN0687206 Id:0900d805807819d6 255

Issue 2-2
Probes
TFP_Gn_TEID_Data_II
Field name TFP_Gn_TEID_Data_II
Explanation Tunnel Endpoint Identifier Data II. This field contains the TEID for data
transmission between the old SGSN and the new SGSN for a particular
PDP context.
Exists in db Yes
CCD section
TFP_Gn_TEID_GGSN_Control_Plane
Field name TFP_Gn_TEID_GGSN_Control_Plane
Explanation Tunnel Endpoint Identifier GGSN Control Plane.
Exists in db Yes
CCD section
TFP_Gn_TEID_GGSN_Data
Field name TFP_Gn_TEID_GGSN_Data
Explanation Tunnel Endpoint Identifier GGSN Data.
Exists in db Yes
CCD section
TFP_Gn_TEID_SGSN_Control_Plane
Field name TFP_Gn_TEID_SGSN_Control_Plane
Explanation Tunnel Endpoint Identifier SGSN Control Plane.
Exists in db Yes
CCD section
TFP_Gn_TEID_SGSN_Data
Field name TFP_Gn_TEID_SGSN_Data
256 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Explanation Tunnel Endpoint Identifier SGSN Data.
Exists in db Yes
CCD section
TFP_Gn_TLLI
Field name TFP_Gn_TLLI
Explanation Temporary Logical Link Identity; temporary identifier which unambigu-
ously identifies the logical link between GPRS mobile station and SGSN
within one RA in the LLC level; TLLI is defined in 3GPP TS 23.003.
Exists in db Yes
CCD section
TFP_Gn_Total_Bytes_Downlink
Field name TFP_Gn_Total_Bytes_Downlink
Explanation Total amount of bytes transferred downlink during the lifetime of a PDP
context. Available only in report due to PDP Context deactivation. Avail-
able in Sum of all related GTP-U.
g The 64-bit TFP_Gn_Total_Bytes_Downlink replaces the 32-bit
TFP_Gn_Total_Bytes_Downlink_High and
TFP_Gn_Total_Bytes_Downlink_Low fields, to improve the usabil-
Exists in db Yes
CCD section
TFP_Gn_Total_Bytes_Downlink_High
Field name TFP_Gn_Total_Bytes_Downlink_High
Explanation The upper 32 bits of the total amount of bytes transferred downlink
during the lifetime of a PDP context. Available only in report due to PDP
Context deactivation. Available in Sum of all related GTP-U.
P-DN0687206 Id:0900d805807819d6 257

Issue 2-2
Probes

should be preferred, because the 32-bit fields will be removed in the
future.
Exists in db Yes
CCD section
TFP_Gn_Total_Bytes_Downlink_Low
Field name TFP_Gn_Total_Bytes_Downlink_Low
Explanation The lower 32 bits of the total amount of bytes transferred downlink
during the lifetime of a PDP context. Available only in report due to PDP
field equals that of the 64-bit TFP_Gn_Total_Bytes_Downlink, and the
field TFP_Gn_Total_Bytes_Downlink_High will equal 0.
Exists in db Yes
CCD section
TFP_Gn_Total_Bytes_Uplink
Field name TFP_Gn_Total_Bytes_Uplink
Explanation Total amount of bytes transferred uplink during the lifetime of a PDP
context. Available only in report due to PDP Context deactivation. Avail-
able in Sum of all related GTP-U.
g The 64-bit TFP_Gn_Total_Bytes_Uplink replaces the 32-bit
TFP_Gn_Total_Bytes_Uplink_High and
TFP_Gn_Total_Bytes_Uplink_Low fields, to improve the usability of
the field. The 64-bit TFP_Gn_Total_Bytes_Uplink field should be
Exists in db Yes
CCD section
258 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_Gn_Total_Bytes_Uplink_High
Field name TFP_Gn_Total_Bytes_Uplink_High
Explanation The upper 32 bits of the total amount of bytes transferred uplink during
the lifetime of a PDP context. Available only in report due to PDP
Exists in db Yes
CCD section
TFP_Gn_Total_Bytes_Uplink_Low
Field name TFP_Gn_Total_Bytes_Uplink_Low
Explanation The lower 32 bits of the total amount of bytes transferred uplink during
the lifetime of a PDP context. Available only in report due to PDP
field equals that of the 64-bit TFP_Gn_Total_Bytes_Uplink, and the field
TFP_Gn_Total_Bytes_Uplink_High will equal 0.
Exists in db Yes
CCD section
TFP_Gn_Username
Field name TFP_Gn_Username
Explanation Username from Create PDP Context Request/ IE Protocol Configura-
tion Options.
Possible values Text field.
P-DN0687206 Id:0900d805807819d6 259

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_Gn_Vendor_Id
Field name TFP_Gn_Vendor_Id
order used.
Exists in db Yes
5.5 Gr interface report fields

The database column names are the same as the IDS field names without the TFP_Gr_
prefix. For example, the "TFP_Gr_AUTN_1 IDS" field is the "AUTN 1" column in
database table TFP_GB_<TFP_Release_Id>_REPORT (TFP_Release_Id = 20 refers
to v2.0 and TFP_Release_Id = 30 refers to v3.0).
spaces instead of underscores between words. For example, the "TFP_Gr_AUTN_1
IDS" field is "AUTN 1" field in Traffic News TFP PS Gr event.
dbd_*.conf. Under the TFP_Gr_<TFP_Release_Id>_REPORT section, there is a
single-row entry for each table column. The SQL data type appears after the column
name and = symbol.
Traffic News Event type TFP PS Gr

Database table TFP_GR_<TFP_Release_Id>_REPORT
Table 8 TFP_GSN_PS_GR fields
The RTT fields in the Gr interface report are the following:
TFP_Gr_Abort_Reason
Field name TFP_Gr_Abort_Reason
Explanation Indicates the abort reason detected on TCAP.
Exists in db Yes
CCD section
TFP_Gr_Abort_Type
Field name TFP_Gr_Abort_Type
260 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Explanation Indicates the abort type detected on TCAP. The values: 0 for TCAP
Provider Abort. 1 for TCAP User ABORT: MAP-U-ABORT source dia-
nostic. 2 for TCAP User ABORT: MAP-P-ABORT source diagnostic. 3
for TCAP User ABORT: MAP-P-ABORT abort reason. 4 for TCAP User
ABORT: MAP-U-ABORT abort reason.
Exists in db Yes
CCD section
TFP_Gr_Access_Type
Field name TFP_Gr_Access_Type
Explanation It indicates whether the authentication procedure was initiated due to a
call, an emergency call, a location updating, a supplementary service
procedure, a short message transfer, a GPRS attach procedure, a
routing area updating, a service request, a MS initiated Detach in
GPRS, a PDP context activation or a PDP context deactivation proce-
dure.
Exists in db Yes
CCD section
TFP_Gr_Authentication_Failure_Cause
Field name TFP_Gr_Authentication_Failure_Cause
Explanation This parameter refers to an authentication failure which has occurred. It
may take values as follows: wrong user response; wrong network sig-
nature. (3GPP 29.002 / FailureCause)
Possible values range
Exists in db Yes
CCD section [Authentication Failure Cause]
TFP_Gr_Destination_Address_GT
Field name TFP_Gr_Destination_Address_GT
Explanation The address of the MAP request recipient.
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 261

Issue 2-2
Probes
TFP_Gr_Destination_SPC
Field name TFP_Gr_Destination_SPC
Explanation Indicates the destination signaling point code. This is based on the first
message. ITU representation. (MTP-3 ITU)
Exists in db Yes
CCD section
TFP_Gr_HLR
Field name TFP_Gr_HLR
Explanation Logical field indicating HLR identification number. Fixed number for
each HLR.
Exists in db Yes
CCD section
TFP_Gr_Imei
Field name TFP_Gr_Imei
is marked with value 0xF. 15 digits.
Exists in db Yes
CCD section
TFP_Gr_Imsi
Field name TFP_Gr_Imsi
tion:MCC = 103 MNC = 25 MSIN = 4110691735.
Possible values max 15 digits
Exists in db Yes
CCD section
262 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_Gr_MSISDN
Field name TFP_Gr_MSISDN
Explanation MSISDN, max 40 digits, E.g. MSISDN = 420018000100001F.
Exists in db Yes
CCD section
TFP_Gr_Number_of_requested_vectors
Field name TFP_Gr_Number_of_requested_vectors
Explanation A number indicating how many authentication vectors the SGSN is
prepared to receive.
Possible values 1-5
Exists in db Yes
CCD section
TFP_Gr_Originating_SPC
Field name TFP_Gr_Originating_SPC
Explanation Indicates the originating signaling point code that initiated the MAP
dialog. This is based on the first message. ITU representation. (MTP-3
ITU)
Exists in db Yes
CCD section
TFP_Gr_Originator_Address_GT
Field name TFP_Gr_Originator_Address_GT
Explanation The address of the MAP request originator.
Exists in db Yes
CCD section
TFP_Gr_Re_Attempt
Field name TFP_Gr_Re_Attempt
P-DN0687206 Id:0900d805807819d6 263

Issue 2-2
Probes
Explanation It indicates whether the failure occurred in a normal authentication

attempt or in an authentication reattempt (there was a previous unsuc-
cessful authentication).
Possible values 0,1
Exists in db Yes
CCD section
TFP_Gr_Report_Count
Field name TFP_Gr_Report_Count
Explanation The number of Gr reports sent to Traffica after midnight. Count is
Exists in db Yes
CCD section
TFP_Gr_Report_Date
Field name TFP_Gr_Report_Date
Exists in db Yes
CCD section
TFP_Gr_Report_Id
Field name TFP_Gr_Report_Id
Exists in db Yes
TFP_Gr_Report_Reason
Field name TFP_Gr_Report_Reason
Explanation Why the report is delivered: see above
Possible values 101
Exists in db Yes
264 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_Gr_Report_Time
Field name TFP_Gr_Report_Time
Exists in db Yes
CCD section
TFP_Gr_Report_UTC_Date
Field name TFP_Gr_Report_UTC_Date
Exists in db Yes
CCD section
TFP_Gr_Report_UTC_Time
Field name TFP_Gr_Report_UTC_Time
Exists in db Yes
CCD section
TFP_Gr_Reserved_1
Field name TFP_Gr_Reserved_1
Exists in db Yes
CCD section
TFP_Gr_Reserved_2
P-DN0687206 Id:0900d805807819d6 265

Issue 2-2
Probes

Exists in db Yes
CCD section
TFP_Gr_Reserved_3
Exists in db Yes
CCD section
TFP_Gr_Sender_Id
Field name TFP_Gr_Sender_Id
Exists in db Yes
CCD section
TFP_Gr_Set_of_Authentication_Params_Quintuplets
Field name TFP_Gr_Set_of_Authentication_Params_Quintuplets
Explanation Indicates the number of authentication parameters quintuplets that are
sent on the MAP interface. UMTS phone in GSM network.
Exists in db Yes
CCD section
TFP_Gr_Set_of_Authentication_Params_Triplets
Field name TFP_Gr_Set_of_Authentication_Params_Triplets
Explanation Indicates the number of authentication parameters triplets that are sent
on the MAP interface. GSM phone in GSM network.
Exists in db Yes
CCD section
266 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_Gr_SGSN
Field name TFP_Gr_SGSN
each SGSN.
Exists in db Yes
CCD section
TFP_Gr_Signalling_Ended_Date
Field name TFP_Gr_Signalling_Ended_Date
Explanation MAP Operation end time (in local time) and date in BCDTIMESTAMP
format.
Exists in db Yes
CCD section
TFP_Gr_Signalling_Ended_Time
Field name TFP_Gr_Signalling_Ended_Time
Explanation MAP Operation end time (in local time) and date in BCDTIMESTAMP
format.
Exists in db Yes
CCD section
TFP_Gr_Signalling_Incomplete
Field name TFP_Gr_Signalling_Incomplete
Explanation Indicates whether there are missing messages in signaling: signaling
completed (0) or signaling incomplete (1).
Possible values 0,1
Exists in db Yes
TFP_Gr_Signalling_Started_Date
Field name TFP_Gr_Signalling_Started_Date
P-DN0687206 Id:0900d805807819d6 267

Issue 2-2
Probes

Explanation MAP Operation start time (in local time) and date in BCDTIMESTAMP
format.
Exists in db Yes
CCD section
TFP_Gr_Signalling_Started_Time
Field name TFP_Gr_Signalling_Started_Time
Explanation MAP Operation start time (in local time) and date in BCDTIMESTAMP
format.
Exists in db Yes
CCD section
TFP_Gr_Sub_Service_Network_Indicator
Field name TFP_Gr_Sub_Service_Network_Indicator
Explanation Indicates the type of the network. (0=international, 2=national network)
Exists in db Yes
CCD section
TFP_Gr_TC_Error_Code_Parameter
Field name TFP_Gr_TC_Error_Code_Parameter
Explanation Specifies why an operation cannot be completed.
Possible values
Exists in db Yes
CCD section
TFP_Gr_Timeout_In_Mediation_Device_Date
Field name TFP_Gr_Timeout_In_Mediation_Device_Date
Possible values
Exists in db Yes
268 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
CCD section
TFP_Gr_Timeout_In_Mediation_Device_Time
Field name TFP_Gr_Timeout_in_Mediation_Device_Time
Possible values
Exists in db Yes
CCD section
TFP_Gr_Timeout_In_Signalling_Date
Field name TFP_Gr_Timeout_In_Signalling_Date
Explanation Timeout reported in signaling local time and date in BCDTIMESTAMP
format. The probes connected to the signaling links reported a timeout
during a dialogue.
Exists in db Yes
CCD section
TFP_Gr_Timeout_In_Signalling_Time
Field name TFP_Gr_Timeout_In_Signalling_Time
Explanation Timeout reported in signalling local time and date in BCDTIMESTAMP
format. The probes connected to the signaling links reported a timeout
during a dialogue.
Exists in db Yes
CCD section
TFP_Gr_Vendor_Id
Field name TFP_Gr_Vendor_Id
order used.
Exists in db Yes
P-DN0687206 Id:0900d805807819d6 269

Issue 2-2
Probes
5.6 Iu-PS interface report fields

TFP_IuPs_ prefix. For example, the "TFP_IuPs_Allocated_Bandwidth" IDS field is the
"Allocated bandwidth" column in database table
TFP_IUPS_<TFP_Release_Id>_REPORT (TFP_Release_Id = 20 refers to v2.0 and
TFP_Release_Id = 30 refers to v3.0).
"TFP_IuPs_Allocated_Bandwidth" IDS field is the "Allocated bandwidth" field in Traffic
News TFP PS IuPS event.
Traffic News Event type TFP PS IuPs

Database table TFP_IUPS_<TFP_Release_Id>_REPORT
Table 9 TFP_GSN_PS_IUPS fields
The RTT fields in the Iu-PS report are the following:
TFP_IuPs_Allocated_Bandwidth
Field name TFP_IuPs_Allocated_Bandwidth
Explanation Allocated bandwidth (in kbits/s); Connection speed that is allocated to
the user.
Exists in db Yes
CCD section
TFP_IuPs_APN
Field name TFP_IuPs_APN
Explanation Access Point Name (APN) as a string.
Possible values APN
Exists in db Yes
CCD section
TFP_IuPs_AttachDetach_Type
Field name TFP_IuPs_AttachDetach_Type
270 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Explanation Attach Type or respectively in a detach report Detach Type, indicates

which type of attach/detach is to be performed. See 3GPP TS 23.060.
Possible values 1-3, 11-13
Exists in db Yes
CCD section [Attach Detach Type]
TFP_IuPs_Collection_End_Date
Field name TFP_IuPs_Collection_End_Date
Exists in db Yes
CCD section
TFP_IuPs_Collection_End_Time
Field name TFP_IuPs_Collection_End_Time
Exists in db Yes
CCD section
TFP_IuPs_Collection_Start_Date
Field name TFP_IuPs_Collection_Start_Date
Exists in db Yes
CCD section
TFP_IuPs_Collection_Start_Time
Field name TFP_IuPs_Collection_Start_Time
P-DN0687206 Id:0900d805807819d6 271

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_IuPs_GGSN
Field name TFP_IuPs_GGSN
each GGSN. Applies only in case of Direct Tunnel.
Possible values
Exists in db Yes
CCD section
TFP_IuPs_GMM_Cause
Field name TFP_IuPs_GMM_Cause
Explanation GPRS Mobility Management Error Cause; coded in 3GPP TS 24.008.
Exists in db Yes
CCD section [GMM Cause]
TFP_IuPs_Imei
Field name TFP_IuPs_Imei
is marked with value 0xF.
Exists in db Yes
CCD section
TFP_IuPs_Imsi
Field name TFP_IuPs_Imsi
tion:MCC = 103 MNC = 25 MSIN = 4110691735.
Exists in db Yes
272 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
CCD section
TFP_IuPs_Initiator
Field name TFP_IuPs_Initiator
user or network. E.g. In PDP Context deactivation 2 = UE initiated; 3 =
SGSN initiated. From signal direction.
Possible values 2,3
Exists in db Yes
TFP_IuPs_LAC
Field name TFP_IuPs_LAC
Exists in db Yes
TFP_IuPs_MCC
Field name TFP_IuPs_MCC
Explanation Field contains the Mobile Country C ode (MCC) of Cell Global Identifi-
cation (CGI). BCD string content (length in digits): MCC(3) + pad-
ding(1). Unused (or string end) is marked with value 0xF.
Possible values 3 digits.
Exists in db Yes
CCD section
TFP_IuPs_MNC
Field name TFP_IuPs_MNC
cation (CGI). BCD string content (length in digits): MNC(2-3) + pad-
ding(1-2). Unused (or string end) is marked with value 0xF.
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 273

Issue 2-2
Probes
TFP_IuPs_Mobile_IP_Address
Field name TFP_IuPs_Mobile_IP_Address
Explanation Mobile IP Address using either IPv4 or IPv6.
Possible values IPv4 or PIv6 address.
Exists in db Yes
CCD section
TFP_IuPs_Mobile_IP_Address_Originator
Field name TFP_IuPs_Mobile_IP_Address_Originator
Explanation From RAB ASSIGNMENT REQUEST (IE: RAB Parameters). Enumer-
ated (0=conversational, 1=streaming, 2=interactive, 3=background¦)
Exists in db Yes
CCD section
TFP_IuPs_MSISDN
Field name TFP_IuPs_MSISDN
Explanation MSISDN, max 40 digits, E.g. MSISDN = 420018000100001F; This field
is expected to be correlated from the Gn interface.
Possible values 40 digits maximum
Exists in db Yes
CCD section
TFP_IuPs_Negotiated_QoS_10
Field name TFP_IuPs_Negotiated_QoS_10
24.008.
Possible values
Exists in db Yes
CCD section
274 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
P-DN0687206 Id:0900d805807819d6 275

Issue 2-2
Probes
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
276 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 277

Issue 2-2
Probes

24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
TFP_IuPs_Negotiated_QoS_Length
Field name TFP_IuPs_Negotiated_QoS_Length
Explanation Length of the Quality of Service information element.
Possible values
Exists in db Yes
CCD section
TFP_IuPs_NSAPI
Field name TFP_IuPs_NSAPI
Explanation Network layer service success point identifier.
Exists in db Yes
CCD section [SAPI]
TFP_IuPs_Number_of_RAB_Assignment_Attempts
Field name TFP_IuPs_Number_of_RAB_Assignment_Attempts
Explanation Number of RAB Assignment Attempts.
Exists in db Yes
278 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
CCD section
TFP_IuPs_P_TMSI
Field name TFP_IuPs_P_TMSI
Possible values
Exists in db Yes
CCD section
TFP_IuPs_PDP_Context_Activation_Date
Field name TFP_IuPs_PDP_Context_Activation_Date
Exists in db Yes
CCD section
TFP_IuPs_PDP_Context_Activation_Time
Field name TFP_IuPs_PDP_Context_Activation_Time
Exists in db Yes
CCD section
TFP_IuPs_RAB_Cause
Field name TFP_IuPs_RAB_Cause
Explanation RAB Cause (RAB = Radio Access Bearer).
Possible values See possible values of field TFP_IuPS_RANAP_Cause.
Exists in db Yes
CCD section [RANAP Cause]
TFP_IuPs_RAB_Signalling_Incomplete
Field name TFP_IuPs_RAB_Signalling_Incomplete
P-DN0687206 Id:0900d805807819d6 279

Issue 2-2
Probes

Possible values 0, 1.
Exists in db Yes
TFP_IuPs_RAB_Traffic_Class
Field name TFP_IuPs_RAB_Traffic_Class
Explanation From RAB ASSIGNMENT REQUEST (IE: RAB Parameters). Enumer-
ated (0=conversational, 1=streaming, 2=interactive, 3=background)
Exists in db Yes
CCD section [Traffic Class]
TFP_IuPs_RAC
Field name TFP_IuPs_RAC
Exists in db Yes
TFP_IuPs_Radio_Cause
Field name TFP_IuPs_Radio_Cause
Possible values
Exists in db Yes
CCD section
TFP_IuPs_Radio_Priority
Field name TFP_IuPs_Radio_Priority
Explanation The radio priority specifies the priority level that the MS shall use at the
lower layers for transmission of data related to a PDP context. Allocates
3 bits: 001 = priority level 1 (highest); 100 = priority level 4 (lowest) and
so forth.
Possible values 3bits
280 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Exists in db Yes
TFP_IuPs_RANAP_Cause
Field name TFP_IuPs_RANAP_Cause
Explanation RANAP Cause (RANAP = Radio Access Network Application Part),
3GPP TS 25.413.
Possible values 1 = RAB pre-empted
2 = Trelocoverall Expiry
3 = Trelocprep Expiry
4 = Treloccomplete Expiry
5 = Tqueing Expiry
6 = Relocation Triggered
8 = Unable to Establish During Relocation
9 = Unknown Target RNC
10 = Relocation Cancelled
11 = Successful Relocation
12 = Requested Ciphering and/or Integrity Protection Algorithms not
Supported
13 = Conflict with already existing Integrity protection and/or Ciphering
information
14 = Failure in the Radio Interface Procedure
15 = Release due to UTRAN Generated Reason
16 = User Inactivity
17 = Time Critical Relocation
18 = Requested Traffic Class not Available
19 = Invalid RAB Parameters Value
20 = Requested Maximum Bit Rate not Available
33 = Requested Maximum Bit Rate for DL not Available
34 = Requested Maximum Bit Rate for UL not Available
21 = Requested Guaranteed Bit Rate not Available
35 = Requested Guaranteed Bit Rate for DL not Available
36 = Requested Guaranteed Bit Rate for UL not Available
22 = Requested Transfer Delay not Achievable
23 = Invalid RAB Parameters Combination
24 = Condition Violation for SDU Parameters
25 = Condition Violation for Traffic Handling Priority
26 = Condition Violation for Guaranteed Bit Rate
P-DN0687206 Id:0900d805807819d6 281

Issue 2-2
Probes
27 = User Plane Versions not Supported

28 = Iu UP Failure
7 = TRELOCalloc Expiry
29 = Relocation Failure in Target CN/RNC or Target System
30 = Invalid RAB ID
31 = No remaining RAB
32 = Interaction with other procedure
37 = Repeated Integrity Checking Failure
38 = Requested Request Type not supported
39 = Request superseded
40 = Release due to UE generated signalling connection release
41 = Resource Optimisation Relocation
42 = Requested Information Not Available
43 = Relocation desirable for radio reasons
44 = Relocation not supported in Target RNC or Target system
45 = Directed Retry
46 = Radio Connection With UE Lost
47 = RNC unable to establish all RFCs
48 = Deciphering Keys Not Available
49 = Dedicated Assistance data Not Available
50 = Relocation Target not allowed
51 = Location Reporting Congestion
65 = Signalling Transport Resource Failure
66 = Iu Transport Connection Failed to Establish
81 = User Restriction Start Indication
82 = User Restriction End Indication
83 = Normal Release
97 = Transfer Syntax Error
98 = Semantic Error
99 = Message not compatible with receiver state
100 = Abstract Syntax Error (Reject)
101 = Abstract Syntax Error (Ignore and Notify)
102 = Abstract Syntax Error (Falsely Constructed Message
113 = O&M Intervention
114 = No Resource Available
115 = Unspecified Failure
116 = Network Optimisation
Exists in db Yes
CCD section [RANAP Cause]
282 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_IuPs_Reject_Cause
Field name TFP_IuPs_Reject_Cause
Possible values
Exists in db Yes
CCD section
TFP_IuPs_Report_Count
Field name TFP_IuPs_Report_Count
Explanation The number of Iu-PS reports sent to Traffica after midnight. Count is
Exists in db Yes
CCD section
TFP_IuPs_Report_Date
Field name TFP_IuPs_Report_Date
Explanation Report sending local date BCDTIMESTAMP format.
Exists in db Yes
CCD section
TFP_IuPs_Report_Id
Field name TFP_IuPs_Report_Id
Possible values 259, 263, 288
Exists in db Yes
TFP_IuPs_Report_Reason
Field name TFP_IuPs_Report_Reason
P-DN0687206 Id:0900d805807819d6 283

Issue 2-2
Probes
Explanation The reason the report is delivered. See section Report generating rules.
Possible values 1 = "GPRS Attach" 2 = "GPRS Detach" 3 = "PDP Context Activation"
4 = "PDP Context Modification" 5 = "time based report" 7 = "PDP
Context Deactivation" 10 = "Routing Area Update, if PDP Context is
Active" 12 = "P-TMSI Reallocation" 15 = "Routing Area Update, if GPRS
Attached (no Active PDP Context)" 20 = "PDP Context closed by the
probe system." 21 = "Secondary PDP Context Activation" 101 =
"Authentication"
Exists in db Yes
TFP_IuPs_Report_Time
Field name TFP_IuPs_Report_Time
Explanation Report sending local time in BCDTIMESTAMP format.
Exists in db Yes
CCD section
TFP_IuPs_Report_UTC_Date
Field name TFP_IuPs_Report_UTC_Date
Explanation Report sending UTC date in BCDTIMESTAMP format.
Exists in db Yes
CCD section
TFP_IuPs_Report_UTC_Time
Field name TFP_IuPs_Report_UTC_Time
Explanation Report sending UTC time in BCDTIMESTAMP format.
Exists in db Yes
CCD section
TFP_IuPs_Requested_QoS_10
Field name TFP_IuPs_Requested_QoS_10
24.008.
284 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 285

Issue 2-2
Probes
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
286 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
P-DN0687206 Id:0900d805807819d6 287

Issue 2-2
Probes
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
24.008.
Possible values
Exists in db Yes
CCD section
TFP_IuPs_Reserved_1
Field name TFP_IuPs_Reserved_1
Possible values
Exists in db Yes
CCD section
TFP_IuPs_Reserved_2
Possible values
Exists in db Yes
CCD section
288 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_IuPs_Reserved_22
Possible values
Exists in db Yes
CCD section
TFP_IuPs_Reserved_3
Possible values
Exists in db Yes
CCD section
TFP_IuPs_RNC_identification
Field name TFP_IuPs_RNC_identification
Explanation A logical field indicating the RNC identification number. There is a fixed
number for each RNC. This field replaces TFP_IuPS_RNC in TFP PS
v2.0.
Possible values
Exists in db Yes
CCD section
TFP_IuPs_RNC_IP_Address
Field name TFP_IuPs_RNC_IP_Address
Explanation RNC identification (IP Address). This address SGSN uses to send data
to RNC. This field replaces TFP_IuPS_RNC in TFP PS v2.0.
Exists in db Yes
CCD section
TFP_IuPs_SAC
Field name TFP_IuPs_SAC
P-DN0687206 Id:0900d805807819d6 289

Issue 2-2
Probes
Explanation 3G Service Area Code when the signalling ended.

Possible values
Exists in db Yes
CCD section [SAC]
TFP_IuPs_SCCP_Release_Cause
Field name TFP_IuPs_SCCP_Release_Cause
Explanation From the RLSD message (which is a message used in the SCCP con-
nection oriented service to release a signalling connection. (Q.713)
Exists in db Yes
CCD section
TFP_IuPs_Sender_Id
Field name TFP_IuPs_Sender_Id
Exists in db Yes
CCD section
TFP_IuPs_Set_of_Authentication_Params_Quintuplets
Field name TFP_IuPs_Set_of_Authentication_Params_Quintuplets
Possible values
Exists in db Yes
CCD section
TFP_IuPs_Set_of_Authentication_Params_Triplets
Field name TFP_IuPs_Set_of_Authentication_Params_Triplets
Possible values
Exists in db Yes
CCD section
290 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_IuPs_SGSN_id
Field name TFP_IuPs_SGSN_id
each SGSN.
Possible values 0-0xFFF
Exists in db Yes
CCD section
TFP_IuPs_SGSN_IP_Address
Field name TFP_IuPs_SGSN_IP_Address
Explanation IP Address of SGSN, which address the RNC uses to send data to
SGSN.
Exists in db Yes
CCD section
TFP_IuPs_Signalling_Ended_Date
Field name TFP_IuPs_Signalling_Ended_Date
Explanation A timestamp for the last message that was needed to complete an Iu-
PS report. E.g. in PDP context deactivation initiated by MS the time-
stamp for the Deactivate PDP Context Accept. Local time is used.
Exists in db Yes
CCD section
TFP_IuPs_Signalling_Ended_Time
Field name TFP_IuPs_Signalling_Ended_Time
Explanation A timestamp for the last message that was needed to complete an Iu-
PS report. E.g. in PDP context deactivation initiated by MS the time-
stamp for the Deactivate PDP Context Accept. Local time is used.
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 291

Issue 2-2
Probes
TFP_IuPs_Signalling_Incomplete
Field name TFP_IuPs_Signalling_Incomplete
Possible values 0,1
Exists in db Yes
TFP_IuPs_Signalling_Started_Date
Field name TFP_IuPs_Signalling_Started_Date
Explanation A timestamp for the first message that was needed to initiate an Iu-PS
report. E.g. in PDP context deactivation initiated by MS, the timestamp
for the Deactivate PDP Context Request. Local time is used.
Exists in db Yes
CCD section
TFP_IuPs_Signalling_Started_Time
Field name TFP_IuPs_Signalling_Started_Time
Explanation A timestamp for the first message that was needed to initiate an Iu-PS
report. E.g. in PDP context deactivation initiated by MS, the timestamp
for the Deactivate PDP Context Request. Local time is used.
Exists in db Yes
CCD section
TFP_IuPs_SM_Cause
Field name TFP_IuPs_SM_Cause
Explanation Session Management Success / Error Cause; The SM cause informa-
tion element is coded in 3GPP TS 24.008.
Exists in db Yes
CCD section
292 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
TFP_IuPs_Teardown_ind
Field name TFP_IuPs_Teardown_ind
Explanation The tear down indicator information element may be included in the
DEACTIVATE PDP CONTEXT REQUEST message in order to indicate
whether only the PDP context associated with this specific TI or all
active PDP contexts sharing the same PDP address as the PDP context
associated with this specific TI shall be deactivated. If the tear down
indicator information element is not included in the DEACTIVATE PDP
CONTEXT REQUEST message, only the PDP context associated with
this specific TI shall be deactivated.
Possible values 0 = Tear down not requested 1 = Tear down requested
Exists in db Yes
TFP_IuPs_Total_Bytes_Downlink
Field name TFP_IuPs_Total_Bytes_Downlink
Explanation Total amount of user plane bytes downlink during the lifetime of the PDP
context (Available only in report due to PDP Context deactivation).
g The 64-bit TFP_IuPS_Total_Bytes_Downlink replaces the 32-bit
TFP_IuPS_Total_Bytes_Downlink_High and
TFP_IuPS_Total_Bytes_Downlink_Low fields, to improve the
usability of the field. The 64-bit TFP_IuPS_Total_Bytes_Downlink
Exists in db Yes
CCD section
TFP_IuPs_Total_Bytes_Downlink_High
Field name TFP_IuPs_Total_Bytes_Downlink_High
Explanation The upper 32 bits of the total amount of user plane bytes downlink
during the lifetime of the PDP context (Available only in report due to
P-DN0687206 Id:0900d805807819d6 293

Issue 2-2
Probes

Exists in db Yes
CCD section
TFP_IuPs_Total_Bytes_Downlink_Low
Field name TFP_IuPs_Total_Bytes_Downlink_low
Explanation The lower 32 bits of the total amount of user plane bytes downlink
during the lifetime of the PDP context (Available only in report due to
field equals that of the 64-bit TFP_IuPS_Total_Bytes_Downlink, and
the field TFP_IuPS_Total_Bytes_Downlink_High will equal 0.
Exists in db Yes
CCD section
TFP_IuPs_Total_Bytes_Uplink
Field name TFP_IuPs_Total_Bytes_Uplink
Explanation The total amount of user plane bytes uplink during the lifetime of the
PDP context (Available only in report due to PDP Context deactivation).
g The 64-bit TFP_IuPS_Total_Bytes_Uplink replaces the 32-bit
TFP_IuPS_Total_Bytes_Uplink_High and
TFP_IuPS_Total_Bytes_Uplink_Low fields, to improve the usability
of the field. The 64-bit TFP_IuPS_Total_Bytes_Uplink field should
be preferred, because the 32-bit fields will be removed from the
adaptation in the future.
Exists in db Yes
CCD section
TFP_IuPs_Total_Bytes_Uplink_High
Field name TFP_IuPs_Total_Bytes_Uplink_High
294 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Explanation The upper 32 bits of the total amount of user plane bytes uplink during
the lifetime of the PDP context (Available only in report due to PDP
Context deactivation).
Exists in db Yes
CCD section
TFP_IuPs_Total_Bytes_Uplink_Low
Field name TFP_IuPs_Total_Bytes_Uplink_Low
Explanation The lower 32 bits of the total amount of user plane bytes uplink during
the lifetime of the PDP context (Available only in report due to PDP
Context deactivation).
field equals that of the 64-bit TFP_IuPS_Total_Bytes_Uplink, and the
field TFP_IuPS_Total_Bytes_Uplink_High will equal 0.
Exists in db Yes
CCD section
TFP_IuPs_Transport_Layer_Address
Field name TFP_IuPs_Transport_Layer_Address
Explanation an IP address to be used for the user plane transport. (3GPP 25.413)
From RAB Assignment.
Exists in db Yes
CCD section
TFP_IuPs_Update_Type
Field name TFP_IuPs_Update_Type
P-DN0687206 Id:0900d805807819d6 295

Issue 2-2
Probes

Explanation The area the updating procedure is associated with. Possible values:
0=RA updating, 1=combined RA/LA updating, 2=combined RA/LA
updating with IMSI attach, 3=periodic updating. 3GPP TS 24.008.
Possible values 0, 1, 2, 3.
Exists in db Yes
CCD section [Update Type]
TFP_IuPs_User_Data_Bytes_Downlink
Field name TFP_IuPs_User_Data_Bytes_Downlink
Explanation Amount of user plane bytes in downlink direction in the PDP context.
g The 64-bit TFP_IuPs_User_Data_Bytes_Downlink replaces the 32-
bit TFP_IuPs_User_Data_Bytes_Downlink_High and
TFP_IuPs_User_Data_Bytes_Downlink_Low fields, to improve the
TFP_IuPs_User_Data_Bytes_Downlink field should be preferred,
future.
Exists in db Yes
CCD section
TFP_IuPs_User_Data_Bytes_Downlink_High
Field name TFP_IuPs_User_Data_Bytes_Downlink_High
Explanation The upper 32 bits of the amount of user plane bytes in downlink direc-
tion in the PDP context.
future.
Exists in db Yes
CCD section
TFP_IuPs_User_Data_Bytes_Downlink_Low
Field name TFP_IuPs_User_Data_Bytes_Downlink_Low
296 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Explanation The lower 32 bits of the amount of user plane bytes in downlink direction
in the PDP context.
field equals that of the 64-bit TFP_IuPS_User_Data_Bytes_Downlink,
and the field TFP_IuPS_User_Data_Bytes_Downlink_High will equal 0.
future.
Exists in db Yes
CCD section
TFP_IuPs_User_Data_Bytes_Uplink
Field name TFP_IuPs_User_Data_Bytes_Uplink
Explanation Amount of user plane bytes in uplink direction in the PDP context.
g The 64-bit TFP_IuPs_User_Data_Bytes_Uplink replaces the 32-bit
TFP_IuPs_User_Data_Bytes_Uplink_High and
TFP_IuPs_User_Data_Bytes_Uplink_Low fields, to improve the
TFP_IuPs_User_Data_Bytes_Uplink field should be preferred,
future.
Exists in db Yes
CCD section
TFP_IuPs_User_Data_Bytes_Uplink_High
Field name TFP_IuPs_User_Data_Bytes_Uplink_High
Explanation The upper 32 bits of the amount of user plane bytes in uplink direction
in the PDP context.
P-DN0687206 Id:0900d805807819d6 297

Issue 2-2
Probes
future.
Exists in db Yes
CCD section
TFP_IuPs_User_Data_Bytes_Uplink_Low
Field name TFP_IuPs_User_Data_Bytes_Uplink_Low
Explanation The lower 32 bits of the amount of user plane bytes in uplink direction
in the PDP context.
field equals that of the 64-bit TFP_IuPS_User_Data_Bytes_Uplink, and
the field TFP_IuPS_User_Data_Bytes_Uplink_High will equal 0.
future.
Exists in db Yes
CCD section
TFP_IuPs_Vendor_Id
Field name TFP_IuPs_Vendor_Id
order used.
Possible values Nokia Siemens Networks specified.
Exists in db Yes
5.7 SMS report fields

TFP_SMS_ prefix. For example, the "TFP_SMS_Cell_Id" IDS field is the "Cell Id"
column in database table TFP_IUPS_<TFP_Release_Id>_REPORT (TFP_Release_Id
= 20 refers to v2.0 and TFP_Release_Id = 30 refers to v3.0).
spaces instead of underscores between words. For example, the "TFP_SMS_Cell_Id"
IDS field is the "Cell Id" field in Traffic News TFP PS SMS event.
298 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Traffic News Event type TFP PS SMS

Database table TFP_SMS_<TFP_Release_Id>_REPORT
Table 10 TFP_GSN_PS_SMS fields
The RTT fields in the SMS report are the following:
TFP_PS_SMS_BSC
Field name TFP_PS_SMS_BSC
Explanation Logical field indicating BSC identification number. Fixed number for
each BSC. Can be provided only if the vendor is able to deliver config-
ured values.
Exists in db Yes
CCD section
TFP_PS_SMS_Cell_Id
Field name TFP_PS_SMS_Cell_Id
Explanation Cell identification when the signalling ended.
Exists in db Yes
CCD section
TFP_PS_SMS_Classmark_2_Octet_1
Field name TFP_PS_SMS_Classmark_2_Octet_1
Explanation Contains the 5 octets of classmark 2. Specified in 24.008, classmark 2
information element.
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 299

Issue 2-2
Probes

Possible values
Exists in db Yes
CCD section
Possible values
Exists in db Yes
CCD section
Possible values
Exists in db Yes
CCD section
Possible values
Exists in db Yes
CCD section
TFP_PS_SMS_CP_Cause
Field name TFP_PS_SMS_CP_Cause
Explanation The Control Protocol cause code. Specified in 24.01, CP-cause
element, cause value octet.
300 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Exists in db Yes
CCD section [CP Cause]
TFP_PS_SMS_Destination_Address
Field name TFP_PS_SMS_Destination_Address
Explanation The destination number of the SMS.
Exists in db Yes
CCD section
TFP_PS_SMS_Destination_Address_Length
Field name TFP_PS_SMS_Destination_Address_Length
Explanation The length of the SMS destination digits.
Exists in db Yes
CCD section
TFP_PS_SMS_Destination_Address_Numbering_Plan
Field name TFP_PS_SMS_Destination_Address_Numbering_Plan
Explanation The number plan of the SMS destination number. Specified in the
23.040, Type-of-address.
Exists in db Yes
CCD section
TFP_PS_SMS_Destination_Address_Type
Field name TFP_PS_SMS_Destination_Address_Type
Explanation The address type of the SMS destination number. Specified in the
23.040, Type-of-address.
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 301

Issue 2-2
Probes
TFP_PS_SMS_Imei
Field name TFP_PS_SMS_Imei
Explanation International Mobile Equipment Identity.
Exists in db Yes
CCD section
TFP_PS_SMS_Imsi
Field name TFP_PS_SMS_Imsi
Explanation International Mobile Subscriber Identity. From Attach request.
Exists in db Yes
CCD section
TFP_PS_SMS_Interface
Field name TFP_PS_SMS_Interface
Explanation 4 = Gb, 5 = Iu-PS
Exists in db Yes
CCD section [Interface]
TFP_PS_SMS_LAC
Field name TFP_PS_SMS_LAC
Exists in db Yes
CCD section [LAC]
TFP_PS_SMS_MCC
Field name TFP_PS_SMS_MCC
Explanation This field contains the Mobile Country Code (MCC) of Cell Global Iden-
tification (CGI) when the signalling ended. BCD string content (length in
302 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
digits): MCC(3) + padding(1). Unused (or string end) is marked with

value 0xF.
Exists in db Yes
CCD section
TFP_PS_SMS_Message_Acknowledgement_Date
Field name TFP_PS_SMS_Message_Acknowledgement_Date
Explanation MO: SMS Center's RP-ACK message local timestamp. From: SMS-
SUBMIT, SMS-COMMAND or RP-SMMA. MT: MS's RP-ACK message
local timestamp. From: SMS-DELIVER or SMS-STATUS-REPORT.
Local time is used.
Exists in db Yes
CCD section
TFP_PS_SMS_Message_Acknowledgement_Time
Field name TFP_PS_SMS_Message_Acknowledgement_Time
Explanation MO: SMS Center's RP-ACK message local timestamp. From: SMS-
SUBMIT, SMS-COMMAND or RP-SMMA. MT: MS's RP-ACK message
local timestamp. From: SMS-DELIVER or SMS-STATUS-REPORT.
Local time is used.
Exists in db Yes
CCD section
TFP_PS_SMS_Message_Date
Field name TFP_PS_SMS_Message_Date
Explanation MO: MS's mobile originated message local timestamp (The message
can be: SMS-SUBMIT, SMS-COMMAND or RP-SMMA.) MT: SMS
Center's message local timestamp (The message can be: SMS-
DELIVER or SMS-STATUS-REPORT.) local time is used.
Exists in db Yes
CCD section
TFP_PS_SMS_Message_Time
Field name TFP_PS_SMS_Message_Time
P-DN0687206 Id:0900d805807819d6 303

Issue 2-2
Probes

Explanation MO: MS's mobile originated message local timestamp (The message
can be: SMS-SUBMIT, SMS-COMMAND or RP-SMMA.) MT: SMS
Center's message local timestamp (The message can be: SMS-
DELIVER or SMS-STATUS-REPORT.) local time is used.
Exists in db Yes
CCD section
TFP_PS_SMS_MNC
Field name TFP_PS_SMS_MNC
cation (CGI) when the signalling ended. BCD string content (length in
digits): MNC(2-3) + padding(1-2). Unused (or string end) is marked with
value 0xF.
Exists in db Yes
CCD section
TFP_PS_SMS_MSISDN
Field name TFP_PS_SMS_MSISDN
Explanation MSISDN.
Possible values 40 digits maximum
Exists in db Yes
CCD section
TFP_PS_SMS_Originating_Address
Field name TFP_PS_SMS_Originating_Address
Explanation The SMS sender number sent over the Gb/Iu-PS interface.
Exists in db Yes
CCD section
TFP_PS_SMS_Originating_Address_Length
Field name TFP_PS_SMS_Originating_Address_Length
304 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Explanation The length of the SMS sender number.
Exists in db Yes
CCD section
TFP_PS_SMS_Originating_Address_Numbering_Plan
Field name TFP_PS_SMS_Originating_Address_Numbering_Plan
Explanation The number plan of the SMS sender number sent over the Gb/Iu-PS
interface. Specified in the 23.040, Type-of-address.
Exists in db Yes
CCD section
TFP_PS_SMS_Originating_Address_Type
Field name TFP_PS_SMS_Originating_Address_Type
Explanation The number type of the SMS sender number sent over the Gb/Iu-PS
interface. Specified in the 23.040, Type-of-address.
Exists in db Yes
CCD section
TFP_PS_SMS_RAC
Field name TFP_PS_SMS_RAC
Exists in db Yes
CCD section [RAC]
TFP_PS_SMS_Report_Count
Field name TFP_PS_SMS_Report_Count
Explanation The number of SMS reports sent to Traffica after midnight. Count is
P-DN0687206 Id:0900d805807819d6 305

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_PS_SMS_Report_Date
Field name TFP_PS_SMS_Report_Date
Exists in db Yes
CCD section
TFP_PS_SMS_Report_Id
Field name TFP_PS_SMS_Report_Id
Possible values 287
Exists in db Yes
TFP_PS_SMS_Report_Reason
Field name TFP_PS_SMS_Report_Reason
Explanation Why the report is delivered: see above
Exists in db Yes
TFP_PS_SMS_Report_Time
Field name TFP_PS_SMS_Report_Time
Exists in db Yes
CCD section
TFP_PS_SMS_Report_UTC_Date
Field name TFP_PS_SMS_Report_UTC_Date
306 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

Exists in db Yes
CCD section
TFP_PS_SMS_Report_UTC_Time
Field name TFP_PS_SMS_Report_UTC_Time
Exists in db Yes
CCD section
TFP_PS_SMS_Reserved_1
Field name TFP_PS_SMS_Reserved_1
Exists in db Yes
CCD section
TFP_PS_SMS_Reserved_2
Field name TFP_PS_SMS_Reserved_2
Exists in db Yes
CCD section
TFP_PS_SMS_RNC
Field name TFP_PS_SMS_RNC
Explanation Logical field indicating RNC identification number. Fixed number for
each RNC.
Exists in db Yes
CCD section
P-DN0687206 Id:0900d805807819d6 307

Issue 2-2
Probes
TFP_PS_SMS_RP_Cause
Field name TFP_PS_SMS_RP_Cause
Explanation The Relay Protocol cause code. Specified in 24.01, RP-cause element,
cause value octet.
Exists in db Yes
CCD section [RP CAuse]
TFP_PS_SMS_SAC
Field name TFP_PS_SMS_SAC
Explanation 3G Service Area Code when the signalling ended.
Exists in db Yes
CCD section [SAC]
TFP_PS_SMS_Sender_Id
Field name TFP_PS_SMS_Sender_Id
Exists in db Yes
CCD section
TFP_PS_SMS_Service_Center_Number
Field name TFP_PS_SMS_Service_Center_Number
Explanation The SMSC number.
Exists in db Yes
CCD section
TFP_PS_SMS_Service_Center_Number_Plan
Field name TFP_PS_SMS_Service_Center_Number_Plan
308 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Explanation Indicates the numbering plan of the SMSC number. See 23.040, Type-
of-address.
Exists in db Yes
CCD section
TFP_PS_SMS_Service_Center_Number_Type
Field name TFP_PS_SMS_Service_Center_Number_Type
Explanation Indicates the type of number of the SMSC number. See 23.040, Type-
of-address.
Exists in db Yes
CCD section
TFP_PS_SMS_Service_Centre_Date
Field name TFP_PS_SMS_Service_Centre_Date
Explanation Message arrived at the SM TL entity of the SC local time and date in
BCDTIMESTAMP format.
Exists in db Yes
CCD section
TFP_PS_SMS_Service_Centre_Time
Field name TFP_PS_SMS_Service_Centre_Time
Explanation Message arrived at the SM TL entity of the SC local time and date in
BCDTIMESTAMP format.
Exists in db Yes
CCD section
TFP_PS_SMS_SGSN
Field name TFP_PS_SMS_SGSN
each SGSN.
P-DN0687206 Id:0900d805807819d6 309

Issue 2-2
Probes
Exists in db Yes
CCD section
TFP_PS_SMS_Signalling_Incomplete
Field name TFP_PS_SMS_Signalling_Incomplete
completed (0) or signalling incomplete (>0).
Possible values 0, 1, 2,3
Exists in db Yes
TFP_PS_SMS_SMS_Length
Field name TFP_PS_SMS_SMS_Length
Explanation Contains the length of the text message typed.
Exists in db Yes
CCD section
TFP_PS_SMS_TP_Cause
Field name TFP_PS_SMS_TP_Cause
Explanation The Transfer Protocol cause code. Specified in 23.040, TP-Failure-
cause element.
Exists in db Yes
CCD section [TP Cause]
TFP_PS_SMS_Vendor_Id
Field name TFP_PS_SMS_Vendor_Id
order used.
Exists in db Yes
310 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
5.8 Logical fields

Logical fields are fields that do not have one to one correspondence with database
fields, but their values are extracted from them.
5.8.1 IDS logical fields

IDS logical fields represent defined number of digits from the beginning of the field, or
they make the field value as such that they can be shown.
<Application>_Service_IP_Address_CRC32
Explanation This field is to provide the facilities to show the GGSN Internet IP
Address in graphs.
g As the IP address -related CRC-32 fields will become obsolete in
the future, their use is not recommended.
Event type TFP PS DIAMETER CC, TFP PS DNS, TFP PS FTP, TFP PS HTTP,
TFP PS IMAP, TFP PS MMS, TFP PS POP3, TFP PS RADIUS, TFP
PS RTSP, TFP PS SIP, TFP PS SMTP, TFP PS WAP
Field Index Not in database
APN_Crc32
Explanation This field is to provide the facilities to show the APN in graphs.
Event type TFP PS Gb, TFP PS Gn, TFP PS IuPS
BSC_IP_Address_Crc32
Explanation This field is to provide the facilities to show the BSC IP Address in
graphs.
Event type TFP PS Gb
MCC_Head_4
Explanation The field makes available the first 4 digits of the MCC. See MCC for a
description of the field.
Event type TFP PS Gb, TFP PS IuPS, TFP PS Gn, TFP PS SMS
MCC_MNC_Head
Explanation The field makes available the first digit of the MCC-MNC.
Event type TFP PS Gn
MCC_MNC_Value
Explanation MCC and MNC from the IMSI
P-DN0687206 Id:0900d805807819d6 311

Issue 2-2
Probes
Field index Not in database
MCC_MNC_Value5
Explanation MCC and MNC from the IMSI
MNC_Head_4
Explanation The field makes available the first 4 digits of the MNC. See MNC for a
description of the field.
Event type TFP PS Gb, TFP PS IuPS, TFP PS Gn, TFP PS SMS
MSISDN_Number_Head_1
Explanation The field makes available the first digit of the MSISDN Number. See
MSISDN Number for a description of the field.
Event type TFP PS Gb, TFP PS Gr, TFP PS Gn, TFP PS IuPS, TFP PS SMS, TFP
PS Flow
Explanation The field makes available the first 2 digits of the MSISDN Number. See
PS Flow
PS Flow
PS Flow
PS Flow
312 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
PS Flow
Negotiated_QoS_Delay_Class
Explanation Bits 4-6 extracted form Negotiated QoS Information Element, octet 3
Field index 51555
Negotiated_QoS_Delivery_Erroneous_SDUs
Field index 51604
Negotiated_QoS_Delivery_Order
Field index 51605
Negotiated_QoS_Guaranteed_Bitrate_DL
Explanation Negotiated QoS Information Element, octet 13
Field index 51615
Negotiated_QoS_Guaranteed_Bitrate_UL
Field index 51614
Negotiated_QoS_Maximum_Bitrate_DL
Field index 51609
Negotiated_QoS_Maximum_Bitrate_UL
Field index 51608
Negotiated_QoS_Maximum_SDU_Size
Field index 51607
P-DN0687206 Id:0900d805807819d6 313

Issue 2-2
Probes
Negotiated_QoS_Mean_Throughput
Field index 51558
Negotiated_QoS_Peak_Throughput
Field index 51557
Negotiated_QoS_Precedence_Class
Field index 51556
Negotiated_QoS_Reliability_Class
Field index 51554
Negotiated_QoS_Residual_BER
Field index 51611
Negotiated_QoS_SDU_Error_Ratio
Field index 51610
Negotiated_QoS_Traffic_Class
Field index 51606
Negotiated_QoS_Traffic_Handling_Priority
Field index 51612
Negotiated_QoS_Transfer_Delay
Field index 51613
314 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Requsted_QoS_Delay_Class
Explanation Bits 4-6 extracted form Requested QoS Information Element, octet 3
Field index 51560
Requsted_QoS_Delivery_Erroneous_SDUs
Field index 51616
Requsted_QoS_Delivery_Order
Field index 51617
Requsted_QoS_Guaranteed_Bitrate_DL
Explanation Requested QoS Information Element, octet 13
Field index 51627
Requsted_QoS_Guaranteed_Bitrate_UL
Field index 51626
Requsted_QoS_Maximum_Bitrate_DL
Field index 51621
Requsted_QoS_Maximum_Bitrate_UL
Field index 51620
Requsted_QoS_Maximum_SDU_Size
Field index 51619
Requsted_QoS_Mean_Throughput
Field index 51563
P-DN0687206 Id:0900d805807819d6 315

Issue 2-2
Probes
Requsted_QoS_Peak_Throughput
Field index 51562
Requsted_QoS_Precedence_Class
Field index 51561
Requsted_QoS_Reliability_Class
Field index 51559
Requsted_QoS_Residual_BER
Field index 51623
Requsted_QoS_SDU_Error_Ratio
Field index 51622
Requsted_QoS_Traffic_Class
Field index 51618
Requsted_QoS_Traffic_Handling_Priority
Field index 51624
Requsted_QoS_Transfer_Delay
Field index 51625
Served_Imei_Mobile_Model
Explanation Shows the mobile model of the IMEI number that caused the report to
be sent.
Event type TFP PS Gr
316 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Served_Imei_Mobile_Station
Explanation The field makes available the last 8 digits of the Served IMEI.
Event type TFP PS Gn, TFP PS IuPS, TFP PS Gr, TFP PS Gb, TFP PS SMS
Field index 10707
Served_Imei_Mobile_Type
Explanation The field makes available the first 8 digits of the Served IMEI.
Event type TFP PS Gb, TFP PS Gn, TFP PS IuPS, TFP PS SMS
Served_Imsi_Country
Explanation Shows the country code of the IMSI number that caused the report to
be sent
Event type TFP PS Gn, TFP PS IuPS, TFP PS Gr, TFP PS Gb,Flow, TFP PS SMS
Field index 10704
Served_Imsi_Country_Network
Explanation Shows the network of the IMSI number that caused the report to be sent
Event type TFP PS Gb, TFP PS Gn, TFP PS IuPS, TFP PS SMS, Flow, TFP PS Gr
Field index 10705
SGSN_IP_Address_Crc32
Explanation This field is to provide the facilities to show the SGSN IP Address in
graphs.
Event type TFP PS Gb, TFP PS IuPS
5.8.2 Traffic News logical fields

Traffic News logical fields are used to represent parts of a field, which has a special
meaning. For example in Quality of services the fields are coded to save bits.
Negotiated QoS Signalling Indication

Explanation Bit 5 extracted form Negotiated QoS Information Element, octet 14.
Field Index 51628
Negotiated QoS Source Statistics Descriptor

Explanation Bits 1-4 extracted form Negotiated QoS Information Element, octet 14.
Field Index 51629
Negotiated QoS Maximum Bit Rate For Downlink (Extended)

Explanation Negotiated QoS Information Element, octet 15.
P-DN0687206 Id:0900d805807819d6 317

Issue 2-2
Probes

Field Index 51630
Negotiated QoS Guaranteed Bit Rate For Downlink (Extended)

Field Index 51631
Negotiated QoS Maximum Bit Rate For Uplink (Extended)

Field Index 51632
Negotiated QoS Guaranteed Bit Rate For Uplink (Extended)

Field Index 51633
Requested QoS Signalling Indication

Explanation Bit 5 extracted form Requested QoS Information Element, octet 14.
Field Index 51634
Requested QoS Source Statistics Descriptor

Explanation Bits 1-4 extracted form Requested QoS Information Element, octet 14.
Field Index 51635
Requested QoS Maximum Bit Rate For Downlink (Extended)

Explanation Requested QoS Information Element, octet 15.
Field Index 51636
Requested QoS Guaranteed Bit Rate For Downlink (Extended)

Field Index 51637
Requested QoS Maximum Bit Rate For Uplink (Extended)

Field Index 51638
Requested QoS Guaranteed Bit Rate For Uplink (Extended)

318 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
Field Index 51639
PDP Context Duration

Explanation The time period from PDP context activation to Signalling Started.
Field Index 40002
P-DN0687206 Id:0900d805807819d6 319

Issue 2-2
Appendices Traffica Reference Guide for 2G/3G Packet Core
Probes
6 Appendices
6.1 Appendix A: Cause codes
Protocol Cause Description

code
Diameter 1 Diameter logout
Diameter 2 Diameter service not provided
Diameter 3 Diameter bad answer
Diameter 4 Diameter administrative
Diameter 5 Diameter link broken
Diameter 6 Diameter auth expired
Diameter 7 Diameter user moved
Diameter 8 Diameter session timeout
Diameter 1001 Diameter multi round auth
Diameter 2002 Diameter limited success
Diameter 2003 Diameter first registration
Diameter 2004 Diameter subsequent registration
Diameter 2005 Diameter unregistered service
Diameter 2006 Diameter success server name not stored
Diameter 2007 Diameter server selection
Diameter 2008 Diameter success auth sent server not stored
Diameter 3001 Diameter command unsupported
Diameter 3002 Diameter unable to deliver
Diameter 3003 Diameter realm not served
Diameter 3004 Diameter too busy
Diameter 3005 Diameter loop detected
Diameter 3006 Diameter redirect indication
Diameter 3007 Diameter application unsupported
Diameter 3008 Diameter invalid hdr bits
Diameter 3009 Diameter invalid avp bits
Diameter 3010 Diameter unknown peer
Diameter 4001 Diameter authentication rejected
Diameter 4002 Diameter out of space
Diameter 4003 Election lost
Diameter 4005 Diameter error mip reply failure
Diameter 4006 Diameter error ha not available
Table 11 Cause codes
320 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Traffica Reference Guide for 2G/3G Packet Core Appendices
Probes

code
Diameter 4007 Diameter error bad key
Diameter 4008 Diameter error mip filter not supported
Diameter 4010 Diameter end user service denied
Diameter 4011 Diameter credit control not applicable
Diameter 4012 Diameter credit limit reached
Diameter 4013 Diameter user name required
Diameter 5001 Diameter avp unsupported
Diameter 5002 Diameter unknown session id
Diameter 5003 Diameter authorization rejected
Diameter 5004 Diameter invalid avp value
Diameter 5005 Diameter missing avp
Diameter 5006 Diameter resources exceeded
Diameter 5007 Diameter contradicting avps
Diameter 5008 Diameter avp not allowed
Diameter 5009 Diameter avp occurs too many times
Diameter 5010 Diameter no common application
Diameter 5011 Diameter unsupported version
Diameter 5012 Diameter unable to comply
Diameter 5013 Diameter invalid bit in header
Diameter 5014 Diameter invalid avp length
Diameter 5015 Diameter invalid message length
Diameter 5016 Diameter invalid avp bit combo
Diameter 5017 Diameter no common security
Diameter 5018 Diameter radius avp untranslatable
Diameter 5024 Diameter error no foreign ha service
Diameter 5025 Diameter error end to end mip key encryption
Diameter 5030 Diameter user unknown
Diameter 5031 Diameter rating failed
Diameter 5032 Diameter error user unknown
Diameter 5033 Diameter error identities dont match
Diameter 5034 Diameter error identity not registered
Diameter 5035 Diameter error roaming not allowed
Diameter 5036 Diameter error identity already registered
Diameter 5037 Diameter error auth scheme not supported
[RFC4740]
Diameter 5038 Diameter error in assignment type
Table 11 Cause codes (Cont.)
P-DN0687206 Id:0900d805807819d6 321

Issue 2-2
Probes

code
Diameter 5039 Diameter error too much data
Diameter 5040 Diameter error not supported user data
DNS 0 No Error
DNS 1 FormErr Format Error
DNS 2 ServFail Server Failure
DNS 3 NXDomain Non-Existent Domain
DNS 4 NotImp Not Implemented
DNS 5 Refused Query Refused
DNS 6 YXDomain Name Exists when it should not
DNS 7 YXRRSet RR Set Exists when it should not
DNS 8 NXRRSet RR Set that should exist does not
DNS 9 NotAuth Server Not Authoritative for zone
DNS 10 NotZone Name not contained in zone
DNS 16 BADVERS Bad OPT Version
DNS 16 BADSIG TSIG Signature Failure
DNS 17 BADKEY Key not recognized
DNS 18 BADTIME Signature out of time window
DNS 19 BADMODE Bad TKEY Mode
DNS 20 BADNAME Duplicate key name
DNS 21 BADALG Algorithm not supported
DNS 22 BADTRUNC Bad Truncation
FTP 110 Restart marker reply. In this case, the text is exact
and not left to the particular implementation; it
must read: MARK yyyy = mmmm Where yyyy is
User-process data stream marker, and mmmm
servers equivalent marker (note the spaces
between markers and "=")
FTP 120 Service ready in nnn minutes.
FTP 125 Data connection already open; transfer starting.
FTP 150 File status okay; about to open data connection.
FTP 200 Command okay.
FTP 202 Command not implemented, superfluous at this
site.
FTP 211 System status, or system help reply.
FTP 212 Directory status.
FTP 213 File status.
322 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

code
FTP 214 Help message. On how to use the server or the
meaning of a particular non-standard command.
This reply is useful only to the human user.
FTP 215 NAME system type. Where NAME is an official
system name from the list in the Assigned
Numbers document.
FTP 220 Service ready for new user.
FTP 221 Service closing control connection. Logged out if
appropriate.
FTP 225 Data connection open; no transfer in progress.
FTP 226 Closing data connection. Requested file action
successful (for example, file transfer or file abort).
FTP 227 Entering Passive Mode (h1,h2,h3,h4,p1,p2).
FTP 230 User logged in, proceed.
FTP 250 Requested file action okay, completed.
FTP 257 "PATHNAME" created.
FTP 331 User name okay, need password.
FTP 332 Need account for login.
FTP 350 Requested file action pending further information.
FTP 421 Service not available, closing control connection.
This may be a reply to any command if the service
knows it must shut down.
FTP 425 Cant open data connection.
FTP 426 Connection closed; transfer aborted.
FTP 450 Requested file action not taken. File unavailable
(e.g., file busy).
FTP 451 Requested action aborted. Local error in process-
ing.
FTP 452 Requested action not taken. Insufficient storage
space in system.
FTP 500 Syntax error, command unrecognized. This may
include errors such as command line too long.
FTP 501 Syntax error in parameters or arguments.
FTP 502 Command not implemented.
FTP 503 Bad sequence of commands.
FTP 504 Command not implemented for that parameter.
FTP 530 Not logged in.
FTP 532 Need account for storing files.
FTP 550 Requested action not taken. File unavailable (e.g.,
file not found, no access).
P-DN0687206 Id:0900d805807819d6 323

Issue 2-2
Probes

code
FTP 551 Requested action aborted. Page type unknown.
FTP 552 Requested file action aborted. Exceeded storage
allocation (for current directory or dataset).
FTP 553 Requested action not taken. File name not
allowed
HTTP 100 Continue
HTTP 101 Switching Protocols
HTTP 200 OK
HTTP 201 Created
HTTP 202 Accepted
HTTP 203 Non-Authoritative Information
HTTP 204 No Content
HTTP 205 Reset Content
HTTP 206 Partial Content
HTTP 300 Multiple Choices
HTTP 301 Moved Permanently
HTTP 302 Found
HTTP 303 See Other
HTTP 304 Not Modified
HTTP 305 Use Proxy
HTTP 306 -- Unused (used in a previous version, now
reserved)
HTTP 307 Temporary Redirect
HTTP 400 Bad Request
HTTP 401 Unauthorized
HTTP 402 Payment Required
HTTP 403 Forbidden
HTTP 404 Not Found
HTTP 405 Method Not Allowed
HTTP 406 Not Acceptable
HTTP 407 Proxy Authentication Required
HTTP 408 Request Time-out
HTTP 409 Conflict
HTTP 410 Gone
HTTP 411 Length Required
HTTP 412 Precondition Failed
HTTP 413 Request Entity Too Large
324 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

code
HTTP 414 Request-URI Too Large
HTTP 415 Unsupported Media Type
HTTP 416 Requested Range not satisfiable
HTTP 417 Expectation Failed
HTTP 500 Internal Server Error
HTTP 501 Not Implemented
HTTP 502 Bad Gateway
HTTP 503 Service Unavailable
HTTP 504 Gateway Time-out
HTTP 505 HTTP Version not supported
MMS 1 Response-status-value = Ok
MMS 2 Error-unspecified
MMS 3 Error-service-denied
MMS 4 Error-message-format-corrupt
MMS 5 Error-sending-address-unresolved
MMS 6 Error-message-not-found
MMS 7 Error-network-problem
MMS 8 Error-content-not-accepted
MMS 9 Error-unsupported-message
MMS 10 Error-transient-failure
MMS 11 Error-transient-sending-address-unresolved
MMS 12 Error-transient-message-not-found
MMS 13 Error-transient-network-problem
MMS 14 Error-transient-partial-success
MMS 15 Error-permanent-failure
MMS 16 Error-permanent-service-denied
MMS 17 Error-permanent-message-format-corrupt
MMS 18 Error-permanent-sending-address-unresolved
MMS 19 Error-permanent-message-not-found
MMS 20 Error-permanent-content-not-accepted
MMS 21 Error-permanent-reply-charging-limitations-not-
met
MMS 22 Error-permanent-reply-charging-request-not-
accepted
MMS 23 Error-permanent-reply-charging-forwarding-
denied
MMS 24 Error-permanent-reply-charging-not-supported
P-DN0687206 Id:0900d805807819d6 325

Issue 2-2
Probes

code
MMS 25 Error-permanent-address-hiding-not-supported
MMS 26 Error-permanent-lack-of-prepaid
MMS 0x80 Ok
MMS 0x81 Error-unspecified
MMS 0x82 Error-service-denied
MMS 0x83 Error-message-format-corrupt
MMS 0x84 Error-sending-address-unresolved
MMS 0x85 Error-message-not-found
MMS 0x86 Error-network-problem
MMS 0x87 Error-content-not-accepted
MMS 0x88 Error-unsupported-message
MMS 0xC0 Error-transient-failure
MMS 0xC1 Error-transient-sending-address-unresolved
MMS 0xC2 Error-transient-message-not-found
MMS 0xC3 Error-transient-network-problem
MMS 0xC4 Error-transient-partial-success
MMS 0xE0 Error-permanent-failure
MMS 0xE1 Error-permanent-service-denied
MMS 0xE2 Error-permanent-message-format-corrupt
MMS 0xE3 Error-permanent-sending-address-unresolved
MMS 0xE4 Error-permanent-message-not-found
MMS 0xE5 Error-permanent-content-not-accepted
MMS 0xE6 Error-permanent-reply-charging-limitations-not-
met
MMS 0xE7 Error-permanent-reply-charging-request-not-
accepted
MMS 0xE8 Error-permanent-reply-charging-forwarding-
denied
MMS 0xE9 Error-permanent-reply-charging-not-supported
MMS 0xEA Error-permanent-address-hiding-not-supported
POP3 1 -ERR
RTSP 100 Continue
RTSP 200 OK
RTSP 201 Created
RTSP 250 Low on Storage Space
RTSP 300 Multiple Choices
RTSP 301 Moved Permanently
326 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

code
RTSP 302 Moved Temporarily
RTSP 303 See Other
RTSP 305 Use Proxy
RTSP 400 Bad Request
RTSP 401 Unauthorized
RTSP 402 Payment Required
RTSP 403 Forbidden
RTSP 404 Not Found
RTSP 405 Method Not Allowed
RTSP 406 Not Acceptable
RTSP 407 Proxy Authentication Required
RTSP 408 Request Time-out
RTSP 410 Gone
RTSP 411 Length Required
RTSP 412 Precondition Failed
RTSP 413 Request Entity Too Large
RTSP 414 Request-URI Too Long
RTSP 415 Unsupported Media Type
RTSP 451 Invalid parameter
RTSP 452 Illegal Conference Identifier
RTSP 453 Not Enough Bandwidth
RTSP 454 Session Not Found
RTSP 455 Method Not Valid In This State
RTSP 456 Header Field Not Valid
RTSP 457 Invalid Range
RTSP 458 Parameter Is Read-Only
RTSP 459 Aggregate Operation Not Allowed
RTSP 460 Only Aggregate Operation Allowed
RTSP 461 Unsupported Transport
RTSP 462 Destination Unreachable
RTSP 500 Internal Server Error
RTSP 501 Not Implemented
RTSP 502 Bad Gateway
RTSP 503 Service Unavailable
RTSP 504 Gateway Time-out
RTSP 505 RTSP Version Not Supported
P-DN0687206 Id:0900d805807819d6 327

Issue 2-2
Probes

code
RTSP 551 Option Not Supported
SMTP 211 System status, or system Help reply
SMTP 214 Help message [Information on how to use the
receiver or the meaning of a particular non-
standard command; this reply is useful only to the
human user]
SMTP 220 <domain> Service ready
SMTP 221 <domain> Service closing transmission channel
SMTP 235 Authentication Succeeded
SMTP 250 Requested MAIL action okay, completed
SMTP 251 OK, no messages waiting for node <x>.
SMTP 252 Cannot VRFY user, but will accept message and
attempt delivery
SMTP 253 OK, <n> pending messages for node <x> started
SMTP 354 Start MAIL input; end with <CRLF>.<CRLF>
SMTP 355 Octet-offset is the transaction offset
SMTP 421 <domain> Service not available, closing transmis-
sion channel [This may be a reply to any command
if the service knows it must shut down]
SMTP 432 A password transition is needed
SMTP 450 Requested MAIL action not taken: mailbox
unavailable [E.g., mailbox busy]
SMTP 451 Unable to process ATRN request now
SMTP 452 Requested action not taken: insufficient system
storage
SMTP 453 You have no mail
SMTP 454 Temporary authentication failure
SMTP 458 Unable to queue messages for node <x>
SMTP 459 Node <x> not allowed: <reason>
SMTP 500 Syntax error, command unrecognized [This may
include errors such as command line too long]
SMTP 501 Syntax error in parameters or arguments
SMTP 502 Command not implemented
SMTP 503 Bad sequence of commands
SMTP 504 Command parameter not implemented
SMTP 521 Reply Code; Host does not accept mail
SMTP 530 Authentication required
SMTP 534 Authentication mechanism is too weak
SMTP 535 Authentication credentials invalid
328 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

code
SMTP 538 Encryption required for requested authentication
mechanism
SMTP 550 Requested action not taken: mailbox unavailable
[E.g., mailbox not found, no access]
SMTP 551 User not local; please try <forward-path>
SMTP 552 Requested MAIL action aborted: exceeded
storage allocation
SMTP 553 Requested action not taken: mailbox name not
allowed [E.g., mailbox syntax incorrect]
SMTP 554 Transaction failed
WAP 0x10 Continue
WAP 0x11 Switching Protocols
WAP 0x20 OK
WAP 0x21 Created
WAP 0x22 Accepted
WAP 0x23 Non-Authoritative Information
WAP 0x24 No Content
WAP 0x25 Reset Content
WAP 0x26 Partial Content
WAP 0x30 Multiple Choices
WAP 0x31 Moved Permanently
WAP 0x32 Moved Temporarily
WAP 0x33 See Other
WAP 0x34 Not Modified
WAP 0x35 Use Proxy
WAP 0x40 Bad Request server could not understand request
WAP 0x41 Unauthorized
WAP 0x42 Payment Required
WAP 0x43 Forbidden operation is understood bit refused
WAP 0x44 Not Found
WAP 0x45 Method Not Allowed
WAP 0x46 Not Acceptable
WAP 0x47 Proxy Authentication Required
WAP 0x48 Request Timeout
WAP 0x49 Conflict
WAP 0x4B Length Required
WAP 0x4C Precondition Failed
P-DN0687206 Id:0900d805807819d6 329

Issue 2-2
Probes

code
WAP 0x4D Request Entity Too Large
WAP 0x4E Request-URI Too Large
WAP 0x4F Unsupported Media Type
WAP 0x50 Gone
WAP 0x60 Internal Server Error
WAP 0x61 Not Implemented
WAP 0x62 Bad Gateway
WAP 0x63 Service Unavailable
WAP 0x64 Gateway Time-out
WAP 0x65 HTTP Version not supported
330 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
6.2 Appendix B: Protocols

Protocol numbers and headers are used in report templates.
Protocol Number
DNS 53
FTP 21
HTTP 80
IMAP 143
MMS 4991
POP3 110
RADIUS 1812
RTSP 554
SMTP 25
WAP 225
Diameter Credit Control 3868
RTSP method 555
RTSP with RTP, RTCP 556
SIP method 5060
SIP with RTP, RTCP 5061
Table 12 Protocols
P-DN0687206 Id:0900d805807819d6 331

Issue 2-2
Probes
6.3 Appendix C: Variables
Variable name Default value Description

application_idle_timeout 60 seconds If there is no traffic in application for
certain time, application is closed and
reported. Unit is seconds.
application_time_trigger 300 seconds Time trigger in application reports.
Unit is seconds. Default value is 300
(seconds).
Context_idle_timeout 72 hours The time the probe supports a PDP
context in idle state. This variable
should be set as high as possible.
context_time_trigger 15 minutes Time interval used for time-based
reports with active PDP context (Gb,
Iu-PS and Gn interface).
DIAMETER_CC_timeout_trig 60 seconds The maximum time how long the
ger probe is waiting for CCA (Credit
Control Answer) to a CCR (Credit
Control Request) before reporting it.
DNS_sampling_rate 1 Indicates the sampling rate for DNS
reports. For example, value 10
means that only one out of 10 reports
is sent to Traffica.
flow_idle_timeout 30 seconds If there is no traffic in a flow for a
certain time, the flow is ended and
reported. Unit is seconds.
flow_sampling_rate 1 Indicates the sampling rate for flows.
For example, value 25 means that
only one out of 25 flows is reported.
flow_time_trigger 600 seconds Time trigger in flow reports. Unit is
seconds.
FTP_timeout_trigger 60 seconds There are no transactions for a
certain time.
GGSN Each GGSN id corresponds to one
IP address. If a probe is attached to
several GGSNs then it can have
several GGSN id and IP counter-
parts.
HTTP_idle_timeout 10 seconds If there are no HTTP GET messages
with same host field in 10 seconds,
the trigger is activated.
HTTP_sampling_rate 1 Indicates the sampling rate for HTTP
reports. Value 10 means that only
one out of 10 reports is sent to Traf-
fica.
HTTP_time_trigger 300 seconds If there are HTTP GET messages
with the same host field for certain
period (and HTTP_idle_timeout is not
triggered), the trigger is activated.
Table 13 Variables
332 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

IMAP_idle_timeout_trigger 600 seconds There are no transactions for a
certain time.
IMAP_timeout_trigger 900 seconds There is continuous polling/other
transactions for a long period of time.
MMS_retrieve_timeout 60 seconds Mobile has sent WSP/HTTP GET
message to MMS Proxy-Relay, but
M-retrieve.conf message is not sent
to mobile within a certain time.
MMS_send_conf_timeout 120 seconds M-Send.req PDU is sent from mobile,
but MMS Proxy-Relay does not
answer (M-Send.conf PDU) within a
certain time.
packet_sampling_rate 1 Indicates sampling rate for IP packets
in probe interface. For example value
10 means that only one of 10 packets
are captured to flow analysis.
POP3_idle_timeout_trigger 600 seconds There are no transactions for a
certain time.
POP3_timeout_trigger 900 seconds There is continuous polling/other
transactions for a long period of time.
RADIUS_timeout_trigger 60 seconds Client sends request, but server does
not respond.
RTSP_timeout_trigger 60 seconds Client sends request, but server does
not respond.
SGSN Each SGSN id corresponds to one IP
address. If a probe is attached to
several SGSNs then it can have
several SGSN id and IP counterparts.
SIP_idle_timeout 2h No SIP messages or RTP traffic in
session for specified time (2 hours as
default).
SIP_INVITE_timeout_trigger 300 seconds Client sends INVITE, no final
response in
SIP_INVITE_timeout_trigger time.
SIP_timeout_trigger 80 seconds Client sends request, but server does
not respond.
SMTP_idle_timeout_trigger 60 seconds There are no transactions for a
certain time.
WAP_GET_time_trigger 60 seconds No answer to WSP/HTTP GET primi-
tive.
WSP_time_trigger 30 minutes WSP connection has been active for
a certain time and trigger 75 has not
been activated. If WSP session still
continues, the rest of the data will be
ignored.
BSC BSC identification that is adjustable.
Table 13 Variables (Cont.)
P-DN0687206 Id:0900d805807819d6 333

Issue 2-2
Probes

HLR HLR identification that is adjustable.
RNC RNC identification that is adjustable.
Table 13 Variables (Cont.)
334 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
6.4 Appendix D: Mobile Country Codes

202= Greece
204= Netherlands
206= Belgium
208= France
212= Monaco
213= Andorra
214= Spain
216= Hungary
218= Bosnia and Herzegovina
219= Croatia
220= Yugoslavia
222= Italy
225= Vatican City State
226= Romania
228= Switzerland
230= Czech Republic
231= Slovak Republic
232= Austria
234= United Kingdom
235= United Kingdom
238= Denmark
240= Sweden
242= Norway
244= Finland
246= Lithuania
247= Latvia
248= Estonia
250= Russian Federation
255= Ukraine
257= Belarus
259= Moldova
260= Poland
262= Germany
266= Gibraltar
268= Portugal
270= Luxembourg
272= Ireland
274= Iceland
P-DN0687206 Id:0900d805807819d6 335

Issue 2-2
Probes
276= Albania
278= Malta
280= Cyprus
282= Georgia
283= Armenia
284= Bulgaria
286= Turkey
288= Faroe Islands (Denmark)
290= Greenland (Denmark)
292= San Marino
293= Slovenia
294= Macedonia
295= Liechtenstein
302= Canada
308= Saint Pierre and Miquelon
310 - 316 = United States of America
330= Puerto Rico
332= United States Virgin Islands
334= Mexico
338= Jamaica
340= Guadeloupe/Martinique
342= Barbados
344= Antigua and Barbuda
346= Cayman Islands
348= British Virgin Islands
350= Bermuda
352= Grenada
354= Montserrat
356= Saint Kitts and Nevis
358= Saint Lucia
360= Saint Vincent and the Grenadines
362= Netherlands Antilles
363= Aruba
364= Bahamas
365= Anguilla
366= Dominica
368= Cuba
370= Dominican Republic
372= Haiti
336 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
374= Trinidad and Tobago

376= Turks and Caicos Islands
400= Azerbaijani Republic
401= Kazakstan
404= India
410= Pakistan
412= Afghanistan
413= Sri Lanka
414= Myanmar
415= Lebanon
416= Jordan
417= Syrian Arab Republic
418= Iraq
419= Kuwait
420= Saudi Arabia
421= Yemen
422= Oman
424= United Arab Emirates
425= Israel
426= Bahrain
427= Qatar
428= Mongolia
429= Nepal
430= United Arab Emirates, Abu Dhabi
431= United Arab Emirates, Dubai
432= Iran
434= Uzbekistan
436= Tajikistan
437= Kyrgyz Republic
438= Turkmenistan
440= Japan
441= Japan
450= Korea
452= Vietnam
454= Hongkong
455= Macau
456= Cambodia
457= Lao People's Democratic Republic
460= China
P-DN0687206 Id:0900d805807819d6 337

Issue 2-2
Probes
461= China
466= Taiwan, China
467= Democratic People's Republic of Korea
470= Bangladesh
472= Maldives
502= Malaysia
505= Australia
510= Indonesia
515= Philippines
520= Thailand
525= Singapore
528= Brunei Darussalam
530= New Zealand
534= Northern Mariana Islands
535= Guam
536= Nauru
537= Papua New Guinea
539= Tonga
540= Solomon Islands
541= Vanuatu
542= Fiji
543= Wallis and Futuna
544= American Samoa
545= Kiribati
546= New Caledonia
547= French Polynesia
548= Cook Islands
549= Western Samoa
550= Micronesia
602= Egypt
603= Algeria
604= Morocco
605= Tunisia
606= Libya
607= Gambia
608= Senegal
609= Mauritania
610= Mali
611= Guinea
338 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
612= Cote d'Ivoire

613= Burkina Faso
614= Niger
615= Togolese Republic
616= Benin
617= Mauritius
618= Liberia
619= Sierra Leone
620= Ghana
621= Nigeria
622= Chad
623= Central African Republic
624= Cameroon
625= Cape Verde
626= Sao Tome and Principe
627= Equatorial Guinea
628= Gabonese Republic
629= Congo
630= Zaire
631= Angola
632= Guinea-Bissau
633= Seychelles
634= Sudan
635= Rwandese Republic
636= Ethiopia
637= Somali Democratic Republic
638= Djibouti
639= Kenya
640= Tanzania
641= Uganda
642= Burundi
643= Mozambique
645= Zambia
646= Madagascar
647= Reunion
648= Zimbabwe
649= Namibia
650= Malawi
651= Lesotho
P-DN0687206 Id:0900d805807819d6 339

Issue 2-2
Probes
652= Botswana
653= Swaziland
654= Comoros
655= South Africa
657= Eritrea
702= Belize
704= Guatemala
706= El Salvador
708= Honduras
710= Nicaragua
712= Costa Rica
714= Panama
716= Peru
722= Argentine Republic
724= Brazil
730= Chile
732= Colombia
734= Venezuela
736= Bolivia
738= Guyana
740= Ecuador
742= Guiana
744= Paraguay
746= Suriname
748= Uruguay
340 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes
6.5 Appendix E: Audio and video codecs

The following table lists the audio and video codecs.
Bit Codecs
0 PCMU
1 reserved
2 reserved
3 GSM
4 G723
5 DVI4
6 DVI4
7 LPC
8 PCMA
9 G722
10 L16
11 L16
12 QCELP
13 CN
14 MPA
15 G728
16 DVI4
17 DVI4
18 G729
19 reserved
20 unassigned
21 unassigned
22 unassigned
23 unassigned
dynamic others
Table 14 Audio and video codecs
6.6 Appendix F: Content types
Encoding Version Assigned Number Content Type

1.1 0x00 */*
1.1 0x01 text/*
Table 15 Content types
P-DN0687206 Id:0900d805807819d6 341

Issue 2-2
Probes

1.1 0x02 text/html
1.1 0x03 text/plain
1.1 0x04 text/x-hdml
1.1 0x05 text/x-ttml
1.1 0x06 text/x-vCalendar
1.1 0x07 text/x-vCard
1.1 0x08 text/vnd.wap.wml
1.1 0x09 text/vnd.wap.wmlscript
1.1 0x0A text/vnd.wap.wta-event
1.1 0x0B multipart/*
1.1 0x0C multipart/mixed
1.1 0x0D multipart/form-data
1.1 0x0E multipart/byterantes
1.1 0x0F multipart/alternative
1.1 0x10 application/*
1.1 0x11 application/java-vm
1.1 0x12 application/x-www-form-urlencoded
1.1 0x13 application/x-hdmlc
1.1 0x14 application/vnd.wap.wmlc
1.1 0x15 application/vnd.wap.wmlscriptc
1.1 0x16 application/vnd.wap.wta-eventc
1.1 0x17 application/vnd.wap.uaprof
1.1 0x18 application/vnd.wap.wtls-ca-certificate
1.1 0x19 application/vnd.wap.wtls-user-certificate
1.1 0x1A application/x-x509-ca-cert
1.1 0x1B application/x-x509-user-cert
1.1 0x1C image/*
1.1 0x1D image/gif
1.1 0x1E image/jpeg
1.1 0x1F image/tiff
1.1 0x20 image/png
1.1 0x21 image/vnd.wap.wbmp
1.1 0x22 application/vnd.wap.multipart.*
1.1 0x23 application/vnd.wap.multipart.mixed
Table 15 Content types (Cont.)
342 Id:0900d805807819d6 P-DN0687206

Issue 2-2
Probes

1.1 0x24 application/vnd.wap.multipart.form-data
1.1 0x25 application/vnd.wap.multipart.byteranges
1.1 0x26 application/vnd.wap.multipart.alternative
1.1 0x27 application/xml
1.1 0x28 text/xml
1.1 0x29 application/vnd.wap.wbxml
1.1 0x2A application/x-x968-cross-cert
1.1 0x2B application/x-x968-ca-cert
1.1 0x2C application/x-x968-user-cert
1.1 0x2D text/vnd.wap.si
1.2 0x2E application/vnd.wap.sic
1.2 0x2F text/vnd.wap.sl
1.2 0x30 application/vnd.wap.slc
1.2 0x31 text/vnd.wap.co
1.2 0x32 application/vnd.wap.coc
1.2 0x33 application/vnd.wap.multipart.related
1.2 0x34 application/vnd.wap.sia
1.3 0x35 text/vnd.wap.connectivity-xml
1.3 0x36 application/vnd.wap.connectivity-wbxml
1.4 0x37 application/pkcs7-mime
1.4 0x38 application/vnd.wap.hashed-certificate
1.4 0x39 application/vnd.wap.signed-certificate
1.4 0x3A application/vnd.wap.cert-response
1.4 0x3B application/xhtml+xml
1.4 0x3C application/wml+xml
1.4 0x3D text/css
1.4 0x3E application/vnd.wap.mms-message
1.4 0x3F application/vnd.wap.rollover-certificate
1.5 0x40 application/vnd.wap.locc+wbxml
1.5 0x41 application/vnd.wap.loc+xml
1.5 0x42 application/vnd.syncml.dm+wbxml
1.5 0x43 application/vnd.syncml.dm+xml
1.5 0x44 application/vnd.syncml.notification
1.5 0x45 application/vnd.wap.xhtml+xml
P-DN0687206 Id:0900d805807819d6 343

Issue 2-2
Probes

1.5 0x46 application/vnd.wv.csp.cir
1.5 0x47 application/vnd.oma.dd+xml
1.5 0x48 application/vnd.oma.drm.message
1.5 0x49 application/vnd.oma.drm.content
1.5 0x4A application/vnd.oma.drm.rights+xml
1.5 0x4B application/vnd.oma.drm.rights+wbxml
344 Id:0900d805807819d6 P-DN0687206

Issue 2-2

pdn0687206 PDF

Hochgeladen von

Dokumentinformationen

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

pdn0687206 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Serve atOnce Traffica

Traffica Reference Guide for 2G/3G

f Important Notice on Product Safety

The same text in German:

1 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3 Principles of RTT report processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.1.4 Gn report triggers . . . . ...... ....... ...... ....... ...... . . . . . . 24

5 RTT Report descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

5.1 Application report fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

1 About this document

1.1 Where to find more information

Table 1 Traffica terms

Table 1 Traffica terms (Cont.)

1.3 Terms and abbreviations

Table 2 Terms and abbreviations

Table 2 Terms and abbreviations (Cont.)

Table 2 Terms and abbreviations (Cont.)

Table 2 Terms and abbreviations (Cont.)

1.4 Datatypes and notations

Datatype or notation Explanation

Table 3 Datatypes and notations

1.5 Traffica for Probes Content for PaCo TNES

Figure 1 Traffica for Probes environment

2.1 Changes in Z5.2

2.1.2.1 General part of each application

2.1.2.2 Diameter Credit Control

• Diameter Credit Control counters

2.1.3 Flow report

2.1.6 Iu-PS report

2.2 Changes in Z5.1

3 Principles of RTT report processing

3.1 Report generation rules

3.1.1 Application report triggers

3.1.1.1 Diameter Credit Control report triggers

3.1.1.2 DNS report triggers

3.1.1.3 FTP report triggers

3.1.1.4 HTTP report triggers

3.1.1.5 IMAP report triggers

3.1.1.6 MMS report triggers

3.1.1.7 POP3 report triggers

3.1.1.8 RADIUS Authentication report triggers

3.1.1.9 RTSP report v2.0 triggers

3.1.1.10 RTSP Method report triggers

3.1.1.11 RTSP QoS report triggers

RTSP_timeout_trigger) AND the probe has started to collect a report (collection is

3.1.1.12 SIP Method report triggers

3.1.1.13 SIP QoS report triggers

3.1.1.14 SMTP report triggers

3.1.1.15 WAP report triggers

3.1.2 Flow report triggers

The following events can initiate a flow report to Traffica:

3.1.3 Gb report triggers

3.1.4 Gn report triggers

3.1.5 Gr report triggers

3.1.6 Iu-PS report triggers

3.1.7 SMS report triggers

4.1 Open nodes

4.2 Clear Code Matrix

4.2.1 Application counters

4.2.1.1 Diameter Credit Control Counters

DIAMETER CC REPORT\Failures\Failure Result Codes Vector\Counter

DIAMETER CC REPORT\Failures\Failure Result Codes Vector\Request Type

DIAMETER CC REPORT\Failures\Failure Result Codes Vector\Service Identifier