Traffica Direct Interface

Serve atOnce TrafficaZ5.4 SP2 Traffica Reference Guide for SGSN Direct Interface DN05148836 Issue 2-2 Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Siemens Networks for any additional information. Traffica Reference Guide for SGSN Direct Interface 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 DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, 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 2012/9/26. All rights reserved f Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set. The same text in German: f Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen. Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheitsanforderungen erfolgen. Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentationssatzes. 2 Id:0900d80580944034 DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Table of Contents This document has 550 pages. DN05148836 Issue 2-2 1 1.1 1.2 1.3 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to find more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Change information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 3 Required licenses for the SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 4 4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.1.6 4.1.7 4.1.8 4.1.9 4.1.10 4.1.11 4.1.12 4.1.13 4.1.14 4.1.15 4.1.16 4.1.17 4.1.18 4.1.19 4.1.20 4.2 4.3 Principles of RTT report processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RTT reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GTP_STAT reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDR_STAT reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LOA_STAT reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NSVC_STAT reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSGP_PAPU_STAT reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSGP_CELL_STAT reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PAGING_STAT reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN_PDP_THR_STAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN_RA_PAGING_STAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN_SMS_RTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN_PAPU_USER_STAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN_CS_CDR_STAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN_OPEN_CDR_STAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN_IU_RA_PAGING_STAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN_PAGING_STAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN_IU_PAGING_STAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN_GTP_C_STAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN_IPPU_GTP_STAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN_IPPU_PDP_THR_STAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Traffica report subscription and blocking . . . . . . . . . . . . . . . . . . . . . . . . Overload control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5.1 5.1.1 5.2 5.2.1 5.2.2 5.2.3 Real-time monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Clear code matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Real-time graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Graph categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Graph sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Graph descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 6 6.1 6.2 6.3 6.4 RTT report descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RTT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GTP_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDR_STAT fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Id:0900d80580944034 24 24 24 26 30 30 30 31 32 32 32 32 33 33 33 33 33 33 33 33 34 34 34 34 34 34 34 36 203 203 203 332 347 3 Traffica Reference Guide for SGSN Direct Interface 4 6.5 6.6 6.7 6.8 6.9 6.10 6.11 6.12 6.13 6.14 6.15 6.16 6.17 6.18 6.19 LOA_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 NSVC_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 BSSGP_CELL_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 BSSGP_PAPU_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 SMS_RTT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 PDP_THR_STAT fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 PAPU_USER_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424 CS_CDR_STAT fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431 OPEN_CDR_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 IU_RA_PAGING_STAT fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 PAGING_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 IU_PAGING_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 GTP_C_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463 IPPU_GTP_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469 IPPU_PDP_THR_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482 7 Traffic News logical fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495 A Appendix Internal cause to interface cause mapping from MM & SM processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502 B Appendix SGSN_Qos_Requested/Negotiated_Octet. . . . . . . . . . . . . . 527 C Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530 Id:0900d80580944034 DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface List of Tables Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 Table 23 Table 24 Table 25 Table 26 Table 27 Table 28 Table 29 Table 30 Table 31 Table 32 Table 33 Table 34 Table 35 Table 36 Table 37 Table 38 Table 39 Table 40 Table 41 Table 42 Table 43 Table 44 Table 45 DN05148836 Issue 2-2 Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Counters of CCMA time classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 SGSN SG6 combined ccma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 SG6 3G CCMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Footnotes used in table Counters of CCMA time classes . . . . . . . . . . 107 Graph Sets and explanations for 2G . . . . . . . . . . . . . . . . . . . . . . . . . 109 Graph Sets and explanations for 3G . . . . . . . . . . . . . . . . . . . . . . . . . 118 Graph Sets and explanations for I-HSPA . . . . . . . . . . . . . . . . . . . . . . 124 Graph Sets and explanations for combined graphs (2G/3G/I-HSPA) . 130 Graph descriptions for 2G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Graph descriptions for SG combined graphs . . . . . . . . . . . . . . . . . . . 158 Graph descriptions for 3G SG6 graphs . . . . . . . . . . . . . . . . . . . . . . . . 167 Graph descriptions for I-HSPA SG7 graphs . . . . . . . . . . . . . . . . . . . . 185 SGSN_Rtt fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Sgsn_Rtt_Apn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Sgsn_Rtt_Apn_crc32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Sgsn_Rtt_Apn_Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Sgsn_Rtt_Bss_Pfc_Info_Pfi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Sgsn_Rtt_Bss_Pfc_Info_Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Sgsn_Rtt_Cause_Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Sgsn_Rtt_Cause_Ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Sgsn_Rtt_Cause_Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Sgsn_Rtt_Cause_Int_Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Sgsn_Rtt_Cause_Proc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Sgsn_Rtt_Cgi_Ci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Sgsn_Rtt_Cgi_Lac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Sgsn_Rtt_Cgi_Mcc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Sgsn_Rtt_Cgi_Mnc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Sgsn_Rtt_Cgi_Rac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Sgsn_Rtt_Charging_Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Sgsn_Rtt_Charging_Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Sgsn_Rtt_Cs_External_Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Sgsn_Rtt_Data_Amount_Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Sgsn_Rtt_Data_Amount_Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Sgsn_Rtt_Ext_Data_Amount_Down . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Sgsn_Rtt_Data_Amount_Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Sgsn_Rtt_Event_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Sgsn_Rtt_Forwarded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Sgsn_Rtt_Ggsn_Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Sgsn_Rtt_Ggsn_Address_Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Sgsn_Rtt_Ggsn_Address_Version . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Sgsn_Rtt_Imei . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Sgsn_Rtt_Imei_Final_Assembly_Code . . . . . . . . . . . . . . . . . . . . . . . 224 Sgsn_Rtt_Imei_Mobile_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Id:0900d80580944034 5 Traffica Reference Guide for SGSN Direct Interface Table 46 Table 47 Table 48 Table 49 Table 50 Table 51 Table 52 Table 53 Table 54 Table 55 Table 56 Table 57 Table 58 Table 59 Table 60 Table 61 Table 62 Table 63 Table 64 Table 65 Table 66 Table 67 Table 68 Table 69 Table 70 Table 71 Table 72 Table 73 Table 74 Table 75 Table 76 Table 77 Table 78 Table 79 Table 80 Table 81 Table 82 Table 83 Table 84 Table 85 Table 86 Table 87 Table 88 Table 89 Table 90 Table 91 Table 92 6 Sgsn_Rtt_Imei_Software_Version_Number . . . . . . . . . . . . . . . . . . . . 224 Sgsn_Rtt_Imsi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Sgsn_Rtt_Imsi_Country . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Sgsn_Rtt_Imsi_Home_Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Sgsn_Rtt_Imsi_Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Sgsn_Rtt_Ms_Pdp_Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Sgsn_Rtt_Ms_Pdp_Address_Len . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Sgsn_Rtt_Ms_Pdp_Address_Organization . . . . . . . . . . . . . . . . . . . . 226 Sgsn_Rtt_Ms_Pdp_Address_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Sgsn_Rtt_Msisdn_Address_Length . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Sgsn_Rtt_Msisdn_Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Sgsn_Rtt_Msisdn_Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Sgsn_Rtt_Neg_Qos_Alloc_Retention . . . . . . . . . . . . . . . . . . . . . . . . . 228 Sgsn_Rtt_Neg_Qos_Delay_Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Sgsn_Rtt_Neg_Qos_Delivery_Erroneous . . . . . . . . . . . . . . . . . . . . . . 228 Sgsn_Rtt_Neg_Qos_Delivery_Order . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Sgsn_Rtt_Neg_Qos_Guaran_Bit_Rate_Dl . . . . . . . . . . . . . . . . . . . . . 229 Sgsn_Rtt_Neg_Qos_Guaran_Bit_Rate_Ul . . . . . . . . . . . . . . . . . . . . . 230 Sgsn_Rtt_Neg_Qos_Max_Bit_Rate_For_Dl . . . . . . . . . . . . . . . . . . . . 231 Sgsn_Rtt_Neg_Qos_Max_Bit_Rate_For_Ul . . . . . . . . . . . . . . . . . . . . 232 Sgsn_Rtt_Neg_Qos_Max_Sdu_Size . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Sgsn_Rtt_Neg_Qos_Mean_Throughput . . . . . . . . . . . . . . . . . . . . . . . 233 Sgsn_Rtt_Neg_Qos_Ms_Cont_Prof_Flag . . . . . . . . . . . . . . . . . . . . . . 234 Sgsn_Rtt_Neg_Qos_Peak_Throughput . . . . . . . . . . . . . . . . . . . . . . . 234 Sgsn_Rtt_Neg_Qos_Precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Sgsn_Rtt_Neg_Qos_Reliability_Class . . . . . . . . . . . . . . . . . . . . . . . . . 235 Sgsn_Rtt_Neg_Qos_Residual_Ber . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Sgsn_Rtt_Neg_Qos_Sdu_Error_Ratio . . . . . . . . . . . . . . . . . . . . . . . . 236 Sgsn_Rtt_Neg_Qos_Traffic_Class . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Sgsn_Rtt_Neg_Qos_Traff_Handling_Prio . . . . . . . . . . . . . . . . . . . . . . 237 Sgsn_Rtt_Neg_Qos_Transfer_Delay . . . . . . . . . . . . . . . . . . . . . . . . . 237 Sgsn_Rtt_Non_Gprs_Cause_Cause . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Sgsn_Rtt_Papu_Capa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Sgsn_Rtt_Papu_Group_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Sgsn_Rtt_Papu_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Sgsn_Rtt_Physical_Papu_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Sgsn_Rtt_Pdp_Context_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Sgsn_Rtt_Ps_External_Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Sgsn_Rtt_Report_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Sgsn_Rtt_Report_Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Sgsn_Rtt_Report_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Sgsn_Rtt_Report_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Sgsn_Rtt_Report_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Sgsn_Rtt_Req_Qos_Ms_Cont_Prof_Flag . . . . . . . . . . . . . . . . . . . . . . 245 Sgsn_Rtt_Req_Qos_Precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Sgsn_Rtt_Req_Qos_Delay_Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Sgsn_Rtt_Req_Qos_Reliability_Class . . . . . . . . . . . . . . . . . . . . . . . . . 246 Id:0900d80580944034 DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Table 93 Table 94 Table 95 Table 96 Table 97 Table 98 Table 99 Table 100 Table 101 Table 102 Table 103 Table 104 Table 105 Table 106 Table 107 Table 108 Table 109 Table 110 Table 111 Table 112 Table 113 Table 114 Table 115 Table 116 Table 117 Table 118 Table 119 Table 120 Table 121 Table 122 Table 123 Table 124 Table 125 Table 126 Table 127 Table 128 Table 129 Table 130 Table 131 Table 132 Table 133 Table 134 Table 135 Table 136 Table 137 Table 138 Table 139 DN05148836 Issue 2-2 Sgsn_Rtt_Req_Qos_Mean_Throughput . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Peak_Throughput . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Delivery_Erroneous . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Delivery_Order . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Traffic_Class . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Max_Sdu_Size . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Max_Bit_Rate_For_Ul . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Max_Bit_Rate_For_Dl . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Sdu_Error_Ratio . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Residual_Ber . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Traff_Handling_Prio . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Transfer_Delay . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Guaran_Bit_Rate_Ul . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Guaran_Bit_Rate_Dl . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Alloc_Retention . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Roaming_Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Secf_Auth_End_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Secf_Auth_End_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Secf_Auth_Start_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Secf_Auth_Start_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Secf_Authentication_Done . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Secf_Ptmsi_Reallocated . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Secf_Ptmsi_Sign_Realloc . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Secf_Imei_Chk_End_Date . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Secf_Imei_Chk_End_Time . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Secf_Imei_Chk_Start_Date . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Secf_Imei_Chk_Start_Time . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Secf_Imei_Checked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Secf_Ciph_Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Tunnel_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Whole_Data_Amount_Down . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Whole_Data_Amount_Up . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ext_Whole_Data_Amount_Down . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ext_Whole_Data_Amount_Up . . . . . . . . . . . . . . . . . . . . . . Sgsn_Sms_Nbr_Add_Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Sms_Nbr_Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Rnc_Address_Mcc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Rnc_Address_Mnc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Rnc_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Sai_Mcc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Sai_Mnc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Sai_Lac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Sai_Sac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_0_Acc_Tec_Type . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_0_Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_1_Acc_Tec_Type . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_1_Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . Id:0900d80580944034 247 247 248 248 249 249 249 250 251 252 252 252 253 253 254 255 255 255 255 256 256 256 257 257 257 257 258 258 258 259 259 259 260 260 260 260 261 261 262 262 262 263 263 263 263 264 265 7 Traffica Reference Guide for SGSN Direct Interface Table 140 Table 141 Table 142 Table 143 Table 144 Table 145 Table 146 Table 147 Table 148 Table 149 Table 150 Table 151 Table 152 Table 153 Table 154 Table 155 Table 156 Table 157 Table 158 Table 159 Table 160 Table 161 Table 162 Table 163 Table 164 Table 165 Table 166 Table 167 Table 168 Table 169 Table 170 Table 171 Table 172 Table 173 Table 174 Table 175 Table 176 Table 177 Table 178 Table 179 Table 180 Table 181 Table 182 Table 183 Table 184 Table 185 Table 186 8 Sgsn_Rtt_Ra_Cap_Array_2_Acc_Tec_Type . . . . . . . . . . . . . . . . . . . 266 Sgsn_Rtt_Ra_Cap_Array_2_Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Sgsn_Rtt_Ra_Cap_Array_3_Acc_Tec_Type . . . . . . . . . . . . . . . . . . . 268 Sgsn_Rtt_Ra_Cap_Array_3_Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Sgsn_Rtt_Ra_Cap_Array_4_Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Sgsn_Rtt_Ra_Cap_Array_5_Acc_Tec_Type . . . . . . . . . . . . . . . . . . . 271 Sgsn_Rtt_Ra_Cap_Array_5_Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Sgsn_Rtt_Old_Sai_Mcc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Sgsn_Rtt_Old_Sai_Mnc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Sgsn_Rtt_Old_Sai_Lac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Sgsn_Rtt_Old_Sai_Sac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Sgsn_Rtt_Old_Cgi_Mcc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Sgsn_Rtt_Old_Cgi_Mnc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Sgsn_Rtt_Old_Cgi_Lac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Sgsn_Rtt_Old_Cgi_Rac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Sgsn_Rtt_Old_Cgi_Ci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Sgsn_Rtt_Event_Start_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Sgsn_Rtt_Event_Start_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Sgsn_Rtt_Event_Stop_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Sgsn_Rtt_Event_Stop_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Sgsn_Rtt_Old_Rnc_Address_Mcc . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Sgsn_Rtt_Old_Rnc_Address_Mnc . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Sgsn_Rtt_Old_Rnc_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 Sgsn_Rtt_Event_Complete_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 Sgsn_Rtt_Event_Complete_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 Sgsn_Rtt_Xid_Reset_Start_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 Sgsn_Rtt_Xid_Reset_Start_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Sgsn_Rtt_Xid_Reset_End_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Sgsn_Rtt_Xid_Reset_End_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Sgsn_Rtt_Ra_Access_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Sgsn_Rtt_Ra_Cap_Array_0_Info_2 . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Sgsn_Rtt_Ra_Cap_Array_0_Info_5 . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Sgsn_Rtt_Ra_Cap_Array_0_Info_6 . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Sgsn_Rtt_Ra_Cap_Array_0_Info_7 . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Sgsn_Rtt_Ra_Cap_Array_0_Info_8 . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Sgsn_Rtt_Ra_Cap_Array_1_Info_1 . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Sgsn_Rtt_Ra_Cap_Array_1_Info_2 . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Sgsn_Rtt_Ra_Cap_Array_1_Info_3 . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Sgsn_Rtt_Ra_Cap_Array_1_Info_4 . . . . . . . . . . . . . . . . . . . . . . . . . . 288 Sgsn_Rtt_Ra_Cap_Array_1_Info_5 . . . . . . . . . . . . . . . . . . . . . . . . . . 289 Sgsn_Rtt_Ra_Cap_Array_1_Info_6 . . . . . . . . . . . . . . . . . . . . . . . . . . 290 Sgsn_Rtt_Ra_Cap_Array_1_Info_7 . . . . . . . . . . . . . . . . . . . . . . . . . . 291 Sgsn_Rtt_Ra_Cap_Array_1_Info_8 . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Sgsn_Rtt_Ra_Cap_Array_2_Info_1 . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Sgsn_Rtt_Ra_Cap_Array_2_Info_2 . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Sgsn_Rtt_Ra_Cap_Array_3_Info_3 . . . . . . . . . . . . . . . . . . . . . . . . . . 295 Sgsn_Rtt_Ra_Cap_Array_3_Info_4 . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Id:0900d80580944034 DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Table 187 Table 188 Table 189 Table 190 Table 191 Table 192 Table 193 Table 194 Table 195 Table 196 Table 197 Table 198 Table 199 Table 200 Table 201 Table 202 Table 203 Table 204 Table 205 Table 206 Table 207 Table 208 Table 209 Table 210 Table 211 Table 212 Table 213 Table 214 Table 215 Table 216 Table 217 Table 218 Table 219 Table 220 Table 221 Table 222 Table 223 Table 224 Table 225 Table 226 Table 227 Table 228 Table 229 Table 230 Table 231 Table 232 Table 233 DN05148836 Issue 2-2 Sgsn_Rtt_Ra_Cap_Array_3_Info_5 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_3_Info_6 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_3_Info_7 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_3_Info_8 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_4_Acc_Tec_Type . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_4_Info_1 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_4_Info_2 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_4_Info_3 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_4_Info_4 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_4_Info_5 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_4_Info_6 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_4_Info_7 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_4_Info_8 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_5_Info_1 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_5_Info_2 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_5_Info_3 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_5_Info_4 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_5_Info_5 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_5_Info_6 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_5_Info_7 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Ra_Cap_Array_5_Info_8 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_rtt_tunnel_info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Tlli_Ptmsi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Ext_Max_Br_Ul . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Ext_Guar_Br_Ul . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Neg_Qos_Ext_Max_Br_Ul . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Neg_Qos_Ext_Guar_Br_Ul . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_E_Alloc_Retention . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_E_Alloc_Retention_Pvi . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_E_Alloc_Retention_Pci . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Neg_Qos_E_Alloc_Retention . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Neg_Qos_E_Alloc_Retention_Pvi . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Neg_Qos_E_Alloc_Retention_Pci . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Neg_Qos_Source_Stat_Desc . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Source_Stat_Desc . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Sign_Indication . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Neg_Qos_Sign_Indication . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Ext_Max_Br_Dl . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Neg_Qos_Ext_Max_Br_Dl . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Req_Qos_Ext_Guar_Br_Dl . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Neg_Qos_Ext_Guar_Br_Dl . . . . . . . . . . . . . . . . . . . . . . . . SGSN_GTP_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Gtp_Stat_Ave_Buf_Fill_Ratio_Nominator . . . . . . . . . . . . . . . . Sgsn_Gtp_Stat_Ave_Buf_Fill_Ratio_Numerator . . . . . . . . . . . . . . . . Sgsn_Gtp_Stat_Buffer_Fill_Ratio_Peak . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Gtp_Stat_DL_Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Rtt_Inact_Reatt_Allw_On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Id:0900d80580944034 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 319 320 321 322 323 325 325 325 327 327 327 328 328 328 329 330 330 331 332 332 333 333 333 334 9 Traffica Reference Guide for SGSN Direct Interface Table 234 Table 235 Table 236 Table 237 Table 238 Table 239 Table 240 Table 241 Table 242 Table 243 Table 244 Table 245 Table 246 Table 247 Table 248 Table 249 Table 250 Table 251 Table 252 Table 253 Table 254 Table 255 Table 256 Table 257 Table 258 Table 259 Table 260 Table 261 Table 262 Table 263 Table 264 Table 265 Table 266 Table 267 Table 268 Table 269 Table 270 Table 271 Table 272 Table 273 Table 274 Table 275 Table 276 Table 277 Table 278 Table 279 Table 280 10 Sgsn_Gtp_Stat_DL_Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Sgsn_Gtp_Stat_Discarded_Packets . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Sgsn_Gtp_Stat_Event_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Sgsn_Gtp_Stat_Papu_Capa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Sgsn_Gtp_Stat_Papu_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Sgsn_Gtp_Stat_Physical_Papu_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Sgsn_Gtp_Stat_Report_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Sgsn_Gtp_Stat_Report_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Sgsn_Gtp_Stat_Report_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Sgsn_Gtp_Stat_Report_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Sgsn_Gtp_Stat_UL_Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Sgsn_Gtp_Stat_UL_Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 Sgsn_Gtp_Stat_Wynona_Overl_Data . . . . . . . . . . . . . . . . . . . . . . . . . 337 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_1 . . . . . . . . . . . . . . . . . . . . . . 337 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_1 . . . . . . . . . . . . . . . . . . . . 337 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_1 . . . . . . . . . . . . . . . . . . . . . . 338 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_1 . . . . . . . . . . . . . . . . . . . . 338 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_1 . . . . . . . . . . . . . . . . . . 338 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_1 . . . . . . . . . . . . . . . . . . . . 338 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_2 . . . . . . . . . . . . . . . . . . . . . . 339 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_2 . . . . . . . . . . . . . . . . . . . . 339 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_2 . . . . . . . . . . . . . . . . . . . . . . 339 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_2 . . . . . . . . . . . . . . . . . . . . 339 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_2 . . . . . . . . . . . . . . . . . . 340 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_2 . . . . . . . . . . . . . . . . . . . . 340 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_3 . . . . . . . . . . . . . . . . . . . . . . 340 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_3 . . . . . . . . . . . . . . . . . . . . 340 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_3 . . . . . . . . . . . . . . . . . . . . . . 340 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_3 . . . . . . . . . . . . . . . . . . . . 341 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_3 . . . . . . . . . . . . . . . . . . 341 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_3 . . . . . . . . . . . . . . . . . . . . 341 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_4 . . . . . . . . . . . . . . . . . . . . . . 341 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_4 . . . . . . . . . . . . . . . . . . . . 342 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_4 . . . . . . . . . . . . . . . . . . . . . . 342 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_4 . . . . . . . . . . . . . . . . . . . . 342 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_4 . . . . . . . . . . . . . . . . . . 342 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_4 . . . . . . . . . . . . . . . . . . . . 343 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_Str . . . . . . . . . . . . . . . . . . . . . 343 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_Str . . . . . . . . . . . . . . . . . . . . 343 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_Str . . . . . . . . . . . . . . . . . . . . . 343 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_Str . . . . . . . . . . . . . . . . . . . 343 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_Str . . . . . . . . . . . . . . . . . 344 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_Str . . . . . . . . . . . . . . . . . . . 344 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_Con . . . . . . . . . . . . . . . . . . . . 344 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_Con . . . . . . . . . . . . . . . . . . 344 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_Con . . . . . . . . . . . . . . . . . . . . 345 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_Con . . . . . . . . . . . . . . . . . . 345 Id:0900d80580944034 DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Table 281 Table 282 Table 283 Table 284 Table 285 Table 286 Table 287 Table 288 Table 289 Table 290 Table 291 Table 292 Table 293 Table 294 Table 295 Table 296 Table 297 Table 298 Table 299 Table 300 Table 301 Table 302 Table 303 Table 304 Table 305 Table 306 Table 307 Table 308 Table 309 Table 310 Table 311 Table 312 Table 313 Table 314 Table 315 Table 316 Table 317 Table 318 Table 319 Table 320 Table 321 Table 322 Table 323 Table 324 Table 325 Table 326 Table 327 DN05148836 Issue 2-2 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_Con . . . . . . . . . . . . . . . . Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_Con . . . . . . . . . . . . . . . . . Sgsn_Gtp_Stat_Dropped_Dl_Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Gtp_Stat_Physical_Papu_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Gtp_Stat_Papu_Capa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Gtp_Stat_Papu_Group_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDR_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Discarded_Due_Other . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Discarded_Due_Overflow . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Event_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Received_Cdrs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Received_Pp_Cdrs . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Report_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Report_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Report_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Report_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Resendings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Discarded_Gb_S_Cdrs . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Discarded_Gb_M_Cdrs . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Discarded_Gb_Smo_Cdrs . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Discarded_Gb_Smt_Cdrs . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Discarded_Iu_S_Cdrs . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Discarded_Iu_M_Cdrs . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Discarded_Iu_Smo_Cdrs . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_Discarded_Iu_Smt_Cdrs . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_M_Cdr_Duration_Sum . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_M_Cdr_Duration_Den . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_S_Cdr_Non_Rt_Duration_Sum . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_S_Cdr_Non_Rt_Duration_Den . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_S_Cdr_Rt_Duration_Den . . . . . . . . . . . . . . . . . . . . . Sgsn_Cdr_Stat_S_Cdr_Rt_Duration_Sum . . . . . . . . . . . . . . . . . . . . . SGSN_LOA_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Loa_Stat_Ave_Load_Rate_Sum . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Loa_Stat_Ave_Load_Rate_Den . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Loa_Stat_Objectname1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Loa_Stat_Objectname2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Loa_Stat_Peak_Load_Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Loa_Stat_Peak_Time_Hours . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Loa_Stat_Peak_Time_Days . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Loa_Stat_Report_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Loa_Stat_Report_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Loa_Stat_Report_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Loa_Stat_Report_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Loa_Stat_Succ_Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Loa_Stat_Unit_Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Loa_Stat_Unit_State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Id:0900d80580944034 345 345 346 346 346 346 347 347 347 348 348 348 348 349 349 349 349 350 350 350 350 351 351 351 351 352 352 352 352 353 353 353 354 354 354 354 355 355 355 356 356 356 356 357 357 357 357 11 . .Traffica Reference Guide for SGSN Direct Interface Table 328 Table 329 Table 330 Table 331 Table 332 Table 333 Table 334 Table 335 Table 336 Table 337 Table 338 Table 339 Table 340 Table 341 Table 342 Table 343 Table 344 Table 345 Table 346 Table 347 Table 348 Table 349 Table 350 Table 351 Table 352 Table 353 Table 354 Table 355 Table 356 Table 357 Table 358 Table 359 Table 360 Table 361 Table 362 Table 363 Table 364 Table 365 Table 366 Table 367 Table 368 Table 369 Table 370 Table 371 Table 372 Table 373 Table 374 12 SGSN_NSVC_STAT fields . . . . . . . 366 Sgsn_Nsvc_Stat_Disc_Data_In_Bytes_Pr3 . . . . . . . . . . . . 364 Sgsn_Nsvc_Stat_Pas_Data_In_Pack_Pr1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 Sgsn_Nsvc_Stat_Papu_Capa . . . . . . . 363 Sgsn_Nsvc_Stat_Upload_Data_In_Pack . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Pr2 . 359 Sgsn_Nsvc_Stat_Papu_Id . 361 Sgsn_Nsvc_Stat_Nsei . 367 Sgsn_Nsvc_Stat_Pas_Data_In_Pack_Str . . . . . . . . . . . . . . . 360 Sgsn_Nsvc_Stat_Papu_Group_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Sgsn_Nsvc_Stat_Ip_Passed_Data_In_Bytes . . . . . . . . . . . 361 Sgsn_Nsvc_Stat_Disc_Due_Cir_Overflow . . . . 368 Sgsn_Nsvc_Stat_Disc_Data_In_Pack_Str . . . . . . . 369 Id:0900d80580944034 DN05148836 Issue 2-2 . . . . . . . . . . . . 362 Sgsn_Nsvc_Stat_Og_Fr_Shared_Data_In_Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 SGSN_BSSGP_CELL_STAT fields . . . . . . . . . . 363 Sgsn_Last_message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Sgsn_Nsvc_Stat_Report_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 Sgsn_Nsvc_Stat_Disc_Data_In_Bytes_Pr4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Sgsn_Nsvc_Stat_Disc_Data_In_Bytes_Pr2 . . . . . . . . . . . . . . . 367 Sgsn_Nsvc_Stat_Disc_Data_In_Pack_Pr4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 Sgsn_Bssgp_Cell_Stat_Report_Count . . . . . . . 359 Sgsn_Nsvc_Stat_Physical_Papu_Id . . . . . . . . 366 Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Pr4 . . . . . . . . . . . . . . . . . . . . . . . 361 Sgsn_Nsvc_Stat_Ns_Vci . 359 Sgsn_Nsvc_Stat_Report_Time . . 361 Sgsn_Nsvc_Stat_Fr_Passed_Data_In_Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 Sgsn_Nsvc_Stat_Disc_Data_In_Bytes_Str . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 Sgsn_Nsvc_Stat_Nse_Count . . . . . . . . . . . . . . . . . . . . . 362 Sgsn_Nsvc_Stat_Ig_Fr_Shared_Data_In_Bytes . . 366 Sgsn_Nsvc_Stat_Pas_Data_In_Pack_Pr4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Str . . . . . . . . . . 369 Sgsn_Bssgp_Cell_Stat_Report_Length . . 364 Sgsn_Nsvc_Stat_Pas_Data_In_Pack_Pr2 . . . . . . 366 Sgsn_Nsvc_Stat_Disc_Data_In_Pack_Pr3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Sgsn_Nsvc_Stat_Disc_Data_In_Pack_Pr2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Sgsn_Sequence_Nr . . . . . . . . . . . . . . . 365 Sgsn_Nsvc_Stat_Pas_Data_In_Pack_Pr3 . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 Sgsn_Nsvc_Stat_Report_Length . . . . . . . . . . . 365 Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Pr3 . . . . . . . . . . . . . . . . 368 Sgsn_Bssgp_Cell_Stat_Report_Id . . . . . . . . . . . 358 Sgsn_Nsvc_Stat_Report_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Pr1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Sgsn_Nsvc_Stat_Disc_Data_In_Bytes_Pr1 . . . . . 358 Sgsn_Nsvc_Stat_Report_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 Sgsn_Nsvc_Stat_Nsvc_Count . . . . . . . . . . . . . 363 Sgsn_Nsvc_Stat_Upload_Data_In_Bytes . 364 Sgsn_Nsvc_Stat_Disc_Data_In_Pack_Pr1 . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_BSSGP_Lost_Data_Pr2 . . . . . . . . Sgsn_Bssgp_Cell_Stat_Report_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Bssgp_Cell_Stat_Llc_Fram_Bssgp_Den . . . . . . . . . Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr3 . . . . . . . . . . . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_Physical_Papu_Id . . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_Peak_Buf_Util_Pr1 . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Bssgp_Cell_Stat_Discarded_Packets . . . Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Den_Pr3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN_BSSGP_PAPU_STAT fields . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_Report_Date . . . . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_Peak_Buf_Util_Pr2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Id:0900d80580944034 369 370 370 370 370 371 371 371 372 372 372 372 372 373 373 373 373 374 374 374 375 375 375 375 376 376 376 376 377 377 377 377 378 378 378 378 379 379 379 380 380 380 380 381 381 381 381 13 . . . . . . . . . . . Sgsn_Bssgp_Cell_Stat_Llc_Fram_Bssgp_Peak . . . Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Pr1 . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Bssgp_Cell_Stat_Physical_Papu_Id . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_BSSGP_Lost_Data_Pr1 . Sgsn_Bssgp_Cell_Stat_Sequence_Nr . . . . . . . . . . . . . . . Sgsn_Bssgp_Cell_Stat_Last_Message . . . . . . . . . . Sgsn_Bssgp_Cell_Stat_Cgi_Lac . . . . . . . . . . . . . . . Sgsn_Bssgp_Cell_Stat_Papu_Id . . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr1 . . . . . Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Den_Pr4 . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_Report_Time . . Sgsn_Bssgp_Cell_Stat_Papu_Group_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Pr1 . . . . . . . Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr4 . Sgsn_Bssgp_Papu_Stat_Peak_Buf_Util_Pr3 . . . . . Sgsn_Bssgp_Cell_Stat_Cgi_Mnc . . . . . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Bssgp_Cell_Stat_Cell_Element_Count . . . . . . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Pr3 . . . . . Sgsn_Bssgp_Cell_Stat_Cgi_Mcc . . . . . . . . . . . . . . . Sgsn_Bssgp_Cell_Stat_Cgi_Rac . . . . . . . .Traffica Reference Guide for SGSN Direct Interface Table 375 Table 376 Table 377 Table 378 Table 379 Table 380 Table 381 Table 382 Table 383 Table 384 Table 385 Table 386 Table 387 Table 388 Table 389 Table 390 Table 391 Table 392 Table 393 Table 394 Table 395 Table 396 Table 397 Table 398 Table 399 Table 400 Table 401 Table 402 Table 403 Table 404 Table 405 Table 406 Table 407 Table 408 Table 409 Table 410 Table 411 Table 412 Table 413 Table 414 Table 415 Table 416 Table 417 Table 418 Table 419 Table 420 Table 421 DN05148836 Issue 2-2 Sgsn_Bssgp_Cell_Stat_Report_Time . . . . . . . . . Sgsn_Bssgp_Cell_Stat_Cgi_Ci . . . . . . . . . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Pr2 . Sgsn_Bssgp_Papu_Stat_Papu_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Bssgp_Cell_Stat_Passed_Data_In_Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Den_Pr2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_Peak_Buf_Util_Pr4 . . . . . Sgsn_Bssgp_Cell_Stat_Llc_Fram_Bssgp_Sum . . . . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Den_Pr1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_BSSGP_Lost_Data_Pr3 . . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr2 . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr3 . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Bssgp_Papu_Cell_Papu_Capa . . . . . . . . Sgsn_Bssgp_Papu_Stat_Report_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Bssgp_Papu_Stat_Report_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 Sgsn_Sms_Rtt_SF_Authentication_Done . . . . . . . . . . . . . . . . . . . . 396 Sgsn_Sms_Rtt_Cgi_Mcc . . . . . . . . 384 Sgsn_Sms_Rtt_Report_Id . 393 Sgsn_Sms_Rtt_Ra_Cap_Array_4_Acc_Tec_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393 Sgsn_Sms_Rtt_Ra_Cap_Array_3_Acc_Tec_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392 Sgsn_Sms_Rtt_Ra_Cap_Array_1_Acc_Tec_Type . . . . . . . . . . . . . . . . . . . . . . . . . . 386 Sgsn_Sms_Rtt_SF_Ptmsi_Sign_Realloc . . . 382 Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Den_Str . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_4 . . . . . . . . . . . 394 Sgsn_Sms_Rtt_Nw_Cap_Content . . . 393 Sgsn_Sms_Rtt_Ra_Cap_Array_5_Acc_Tec_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Sgsn_Sms_Rtt_Report_Count . . . . . . . . . . . . . . . . 388 Sgsn_Sms_Rtt_Msisdn_Address_length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 Sgsn_Sms_Rtt_Report_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 Sgsn_Sms_Rtt_Imei . . . . . . . . . . . . . . . . . . . . . . . . .Traffica Reference Guide for SGSN Direct Interface Table 422 Table 423 Table 424 Table 425 Table 426 Table 427 Table 428 Table 429 Table 430 Table 431 Table 432 Table 433 Table 434 Table 435 Table 436 Table 437 Table 438 Table 439 Table 440 Table 441 Table 442 Table 443 Table 444 Table 445 Table 446 Table 447 Table 448 Table 449 Table 450 Table 451 Table 452 Table 453 Table 454 Table 455 Table 456 Table 457 Table 458 Table 459 Table 460 Table 461 Table 462 Table 463 Table 464 Table 465 Table 466 Table 467 Table 468 14 Sgsn_Bssgp_Papu_Stat_BSSGP_Lost_Data_Pr4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 Sgsn_Sms_Rtt_Service_Center_Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 SGSN_SMS_RTT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_5 . . . . . . . . . . . . . . . . . 396 Sgsn_Sms_Rtt_Service_Center_Numbers . 390 Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Sgsn_Bssgp_Papu_Stat_Papu_Group_Id . . . . . . . . . . . . . . . . . . . . 394 Sgsn_Sms_Rtt_Nw_Cap_Length . . . . . . . . . . . 383 Sgsn_Bssgp_Papu_Stat_BSSGP_Lost_Data_Str . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392 Sgsn_Sms_Rtt_Ra_Cap_Array_2_Acc_Tec_Type . . . . . 383 Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Str . . . . . . . . . . . . . . . . . . . 392 Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_7 . . . . . . . . . . . . . . . . . . 386 Sgsn_Sms_Rtt_Imsi . . . . . . . . . . . . 388 Sgsn_Sms_Rtt_Msisdn_Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 Sgsn_Sms_Rtt_Report_Time . . . . . . . . . . . . . . . . . . . . . 386 Sgsn_Sms_Rtt_Imsi_Length . . . . . . . . . 385 Sgsn_Sms_Rtt_Event_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Pr4 . . . . 388 Sgsn_Sms_Rtt_Msisdn_Numbers . . 382 Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Str . 387 Sgsn_Sms_Rtt_SF_Ptmsi_Reallocated . . . . . . . . . . . 382 Sgsn_Bssgp_Papu_Stat_Peak_Buf_Util_Str . 389 Sgsn_Sms_Rtt_Ra_Cap_Array_0-5_Acc_Tec_Type . . . . . . . . . . . . . . 395 Sgsn_Sms_Rtt_Nw_Cap_Spare1 . . . . . . . 397 Id:0900d80580944034 DN05148836 Issue 2-2 . . . . . . . . 387 Sgsn_Sms_Rtt_SF_Ciph_Algorithm . . . . . . . 387 Sgsn_Sms_Rtt_SF_Imei_Checked . . . 395 Sgsn_Sms_Rtt_Service_Center_Address_length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 Sgsn_Sms_Rtt_Cgi_Lac . . . 383 Sgsn_Bssgp_Papu_Stat_Papu_Capa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_2 . . . . . . . . . . . . . . . . . . . . Sgsn_Sms_Rtt_SMS_Nbr_Indicators . . . . . . . . . . . . . . . . . . . Sgsn_Sms_Rtt_Cause_Ini . . . . . . . Sgsn_Sms_Rtt_Rnc_Address_Mnc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Sms_Rtt_Sai_Lac . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Charging_Index . . . . . . . Sgsn_Sms_Rtt_Roaming_Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Report_Count . . . . . . . . . . Sgsn_Sms_Rtt_Event_Start_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Sms_Rtt_Cause_Family . . . . . . . . . . Sgsn_Sms_Rtt_Ra_Access_Type . . . . . Sgsn_Pdp_Thr_Stat_Qos_Negotiated_Ms_Cont_Prof_Flag . . . . . . Sgsn_Sms_Rtt_Charging_Info . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Report_Date . . . . . . . Sgsn_Sms_Rtt_Sai_Mcc . . . . . . Sgsn_Sms_Rtt_Cause_Int_Cause . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Papu_Capa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Sms_Rtt_Sms_Length . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Sms_Rtt_Cgi_Ci . .Traffica Reference Guide for SGSN Direct Interface Table 469 Table 470 Table 471 Table 472 Table 473 Table 474 Table 475 Table 476 Table 477 Table 478 Table 479 Table 480 Table 481 Table 482 Table 483 Table 484 Table 485 Table 486 Table 487 Table 488 Table 489 Table 490 Table 491 Table 492 Table 493 Table 494 Table 495 Table 496 Table 497 Table 498 Table 499 Table 500 Table 501 Table 502 Table 503 Table 504 Table 505 Table 506 Table 507 Table 508 Table 509 Table 510 Table 511 Table 512 Table 513 Table 514 Table 515 DN05148836 Issue 2-2 Sgsn_Sms_Rtt_Cgi_Rac . . . . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Ts_Time . . . . Sgsn_Sms_Rtt_Cause_Proc . . . . . . . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Logical_Papu_Id . . . SGSN_PDP_THR_STAT fields . . . . . . . . . . . . . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Physical_Papu_Id . . . . . . . . . . . . . . . . . Sgsn_Sms_Rtt_Rnc_Address_Mcc . . . . . . . . . . . . . . . . . . . Sgsn_Sms_Rtt_Sai_Mnc . . . . . . . . . . Sgsn_Sms_Rtt_Sai_Sac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Sms_Rtt_Cause_Cause . . . Sgsn_Sms_Rtt_Rnc_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Report_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Sms_Rtt_Event_Stop_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Pdp_Cxt_Element_Count . . . . . . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Report_Length . . . . . . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Delivery_Order . . . . . . . . . . . . . . . . . Sgsn_Sms_Rtt_SMS_Nbr_Add_length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Qos_Negotiated_2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Alloc_Retention . . . . . . . . . Id:0900d80580944034 397 397 397 398 402 404 405 405 406 406 406 407 407 407 408 408 409 409 409 409 410 410 410 410 411 411 411 412 412 412 412 413 413 413 413 414 414 414 414 414 415 415 415 415 416 416 416 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Sms_Rtt_Event_Start_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Qos_Negotiated_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Report_Time . Sgsn_Pdp_Thr_Stat_Last_2bytes_Ggsn_Address . . . . . . . . . . . . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Papu_Group_Id . . . . . . . . . . . . . Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Deliv_Of_Erroneous . . . . . . . . . . . . . . . . . . . Sgsn_Sms_Rtt_Event_Stop_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_SMS_Nbr_Numbers . . . . . . . . . . . . . . . . . . . . . . Sgsn_Sms_Rtt_Physical_Smmu_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 Sgsn_Pdp_Thr_Stat_Uplink_Data . . 419 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Max_Sdu_Size . . . . . . . 417 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_8 . . . . . . . . . . . . . . . . . . . . 424 Sgsn_Bssgp_Papu_Stat_Report_Length . . . . . . . . . . . . . . . . . . . . . . . . . 420 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Traffic_Handling_Prio . . . . . . . . . . . . . . . 418 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_13 . . . . . . . . . . . . . . . . . . . 417 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425 Sgsn_Papu_User_Stat_Report_Date . . . . . . . . . . . 426 Sgsn_Papu_User_Stat_Papu_Group_Id . . . . . . . . . 418 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_11 . . . . . . . . . . . 420 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Residual_Ber . 425 Sgsn_Papu_User_Stat_Report_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 Sgsn_Pdp_Thr_Stat_Ra_Access_Type . . . . . . . . . . . . . . . . . . . . . . . 417 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_9 . 426 Sgsn_Papu_User_Stat_Attached_Iu_Users . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 Sgsn_Papu_User_Stat_Attached_Gb_Users . . 427 Sgsn_Papu_User_Stat_Open_Priority_Class_2_Pdp_Con . 427 Sgsn_Papu_User_Stat_Open_Priority_Class_3_Pdp_Con . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_6 . . . . . . . . . . . . . . . . . 426 Sgsn_Papu_User_Stat_Papu_Capa . . . . . . . . . . . . . . . . . . . . . . . . 421 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Guaran_Bit_Rate_Ul . . . . . 423 Sgsn_Pdp_Thr_Stat_Imsi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 Sgsn_Papu_User_Stat_Open_Priority_Class_1_Pdp_Con . . . . . . . . . . . . . . . . . . . . . . . . 420 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Sdu_Error_Ratio . . . . . . 422 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Source_Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . 416 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_4 . . . . . 426 Sgsn_Papu_User_Stat_Physical_Papu_Id . . . . . . . . . . 421 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Signalling_Indication . 420 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Max_Bitrate_Dl . . . . . . . . . . . . . . . . . . 423 Sgsn_Pdp_Thr_Stat_Downlink_Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Traffica Reference Guide for SGSN Direct Interface Table 516 Table 517 Table 518 Table 519 Table 520 Table 521 Table 522 Table 523 Table 524 Table 525 Table 526 Table 527 Table 528 Table 529 Table 530 Table 531 Table 532 Table 533 Table 534 Table 535 Table 536 Table 537 Table 538 Table 539 Table 540 Table 541 Table 542 Table 543 Table 544 Table 545 Table 546 Table 547 Table 548 Table 549 Table 550 Table 551 Table 552 Table 553 Table 554 Table 555 Table 556 Table 557 Table 558 Table 559 Table 560 Table 561 Table 562 16 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Guaran_Bit_Rate_Dl . . . . . . . . . 419 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Traffic_Class . . . . . . . . . . . . . . . . . . . 419 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_14 . 425 Sgsn_Papu_User_Stat_Papu_Id . . 418 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_12 . . . . . . . . . . . . 425 Sgsn_Papu_User_Stat_Report_Count . . . . . . . . . 420 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Transfer_Delay . . . . . . . . . . . . . . . . . . . . . 417 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 PAPU_USER_STAT fields . . 418 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_10 . 428 Id:0900d80580944034 DN05148836 Issue 2-2 . . . . . . . . . . . 421 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Spare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424 Sgsn_Papu_User_Stat_Report_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Ext_Guaran_Bit_Rate_Dl . . . . . . . . . . . . . . . . . . . . . . 419 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Max_Bitrate_Ul . . . . . . . . . 422 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Ext_Max_Bit_Rate_Dl . . . . . . . . . . . . . . . . . . . . . 422 Sgsn_Pdp_Thr_Stat_Imsi_Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Traffica Reference Guide for SGSN Direct Interface Table 563 Table 564 Table 565 Table 566 Table 567 Table 568 Table 569 Table 570 Table 571 Table 572 Table 573 Table 574 Table 575 Table 576 Table 577 Table 578 Table 579 Table 580 Table 581 Table 582 Table 583 Table 584 Table 585 Table 586 Table 587 Table 588 Table 589 Table 590 Table 591 Table 592 Table 593 Table 594 Table 595 Table 596 Table 597 Table 598 Table 599 Table 600 Table 601 Table 602 Table 603 Table 604 Table 605 Table 606 Table 607 DN05148836 Issue 2-2 Sgsn_Papu_User_Stat_Open_Priority_Class_4_Pdp_Con . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 Sgsn_Papu_User_Stat_Open_Gb_Pdp_Con . . . . 433 Sgsn_Cs_Cdr_Stat_Disc_Gb_S_Cdrs_Due_Other . . . . . . . . . . . . . . . . 430 Sgsn_Papu_User_Stat_Bandwidth_Limit_For_Rt_Pdp_Ctxs . . . . . . . . . 434 Sgsn_Cs_Cdr_Stat_Disc_Gb_M_Cdrs_Due_Overflow . . . . . . . . . . . . . 431 Sgsn_Cs_Cdr_Stat_Report_Length . . . 428 Sgsn_Papu_User_Stat_Open_Gb_Pdp_Con . . . . . . . . . . . . . . . . . . . . 437 Sgsn_Cs_Cdr_Stat_Disc_Gb_Smt_Cdrs_Due_Other . . 432 Sgsn_Cs_Cdr_Stat_Generated_pp_Gb_S_Cdrs . . . . . . . . . . . . . . . . . . . . . 439 Sgsn_Cs_Cdr_Stat_Disc_Iu_M_Cdrs_Due_Overflow . . . 436 Sgsn_Cs_Cdr_Stat_Generated_Gb_Smt_Cdrs . . . . . . . . . . . . . . . . . . . . . . . . . . 435 Sgsn_Cs_Cdr_Stat_Generated_Gb_Smo_Cdrs . 430 SGSN_CS_CDR_STAT fields . . . . . 435 Sgsn_Cs_Cdr_Stat_Disc_Gb_Smo_Cdrs_Due_Overflow . . . . . . . . . . . 433 Sgsn_Cs_Cdr_Stat_Generated_Gb_M_Cdrs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 Sgsn_Cs_Cdr_Stat_Report_Date . . . . . . . . . . . . . . . . . . . . . . . . 439 Id:0900d80580944034 17 . . . 438 Sgsn_Cs_Cdr_Stat_Disc_Iu_S_Cdrs_Due_Resent . . . . . . 438 Sgsn_Cs_Cdr_Stat_Disc_Iu_S_Cdrs_Due_Other . . . . . 439 Sgsn_Cs_Cdr_Stat_Generated_Pp_Iu_M_Cdrs . . . . . 436 Sgsn_Cs_Cdr_Stat_Disc_Gb_Smo_Cdrs_Due_Resent . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 Sgsn_Papu_User_Stat_Average_Bandwidth_Used_By_Rt_Pdp_Con . . . . . . . . . . . . . . . . 433 Sgsn_Cs_Cdr_Stat_Disc_Gb_S_Cdrs_Due_Overflow . . . . . 437 Sgsn_Cs_Cdr_Stat_Generated_Pp_Iu_S_Cdrs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 Sgsn_Cs_Cdr_Stat_Disc_Gb_S_Cdrs_Due_Resent . . . . . . . . . . . . . . . . . . . . . . 435 Sgsn_Cs_Cdr_Stat_Generated_Gb_Pp_Smo_Cdrs . . . . . . . . . 438 Sgsn_Cs_Cdr_Stat_Disc_Iu_S_Cdrs_Due_Overflow . . . . . . . 430 Sgsn_Papu_User_Stat_Rt_Pdp_Ctx_Capacity . . . . . . . . . . . . . . . . . . . . . 437 Sgsn_Cs_Cdr_Stat_Disc_Gb_Smt_Cdrs_Due_Resent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 Sgsn_Cs_Cdr_Stat_Generated_Gb_Pp_Smt_Cdrs . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 Sgsn_Cs_Cdr_Stat_Generated_pp_Gb_M_Cdrs . . . . . . . . . . . . . . . . . . . . . . . . . 435 Sgsn_Cs_Cdr_Stat_Disc_Gb_Smo_Cdrs_Due_Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 Sgsn_Cs_Cdr_Stat_Disc_Gb_M_Cdrs_Due_Other . . . . . . . 434 Sgsn_Cs_Cdr_Stat_Disc_Gb_M_Cdrs_Due_Resent . . . . . . . . . . 438 Sgsn_Cs_Cdr_Stat_Generated_Iu_M_Cdrs . . . 437 Sgsn_Cs_Cdr_Stat_Generated_Iu_S_Cdrs . . . . . 429 Sgsn_Papu_User_Stat_Bandwidth_Allocated_By_Rt_Pdp_Con . . . . . . . . . . 432 Sgsn_Cs_Cdr_Stat_Generated_Gb_S_Cdrs . . . . . . . . . . . 431 Sgsn_Cs_Cdr_Stat_Report_Id . . . . . . . . . . . . . . . . . . . . . . 432 Sgsn_Cs_Cdr_Stat_Report_Time . . . . . . . . . . 429 Sgsn_Papu_User_Stat_Active_Users . 431 Sgsn_Cs_Cdr_Stat_Report_Count . . . . 436 Sgsn_Cs_Cdr_Stat_Disc_Gb_Smt_Cdrs_Due_Overflow . . . . . . . . . . . . . . . . . . . . . . . . . 428 Sgsn_Papu_User_Stat_Open_Priority_Class_Streaming_Pdp_Con 428 Sgsn_Papu_User_Stat_Open_Priority_Class_Conv_Pdp_Con . . . . . . . . . . 430 Sgsn_Papu_User_Stat_Average_Bandwidth_Limit_For_Rt_Pdp_Ctxs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 Sgsn_Iu_Ra_Paging_Stat_Report_Date . . . . . . . . . . . . . 440 Sgsn_Cs_Cdr_Stat_Generated_Iu_Pp_Smo_Cdrs . . . . . . . . 444 Sgsn_Open_Cdr_Stat_Report_Count . . . . . 440 Sgsn_Cs_Cdr_Stat_Generated_Iu_Smo_Cdrs . . . . . . . . 448 Sgsn_Open_Cdr_Stat_Roaming_Iu_M_Cdrs . . . . . . . . . . . . . . . . . . . 447 Sgsn_Open_Cdr_Stat_Iu_S_Cdrs . . . . . . . . 440 Sgsn_Cs_Cdr_Stat_Disc_Iu_Smo_Cdrs_Due_Overflow . . . . . . . . . . . . . . . . . . . . . . . . 439 Sgsn_Cs_Cdr_Stat_Disc_Iu_M_Cdrs_Due_Resent . . . . . . . . . . . 447 Sgsn_Open_Cdr_Stat_Iu_M_Cdrs . . . . . . . . . . . . . . . . . . . . . . . . . . 441 Sgsn_Cs_Cdr_Stat_Disc_Iu_Smo_Cdrs_Due_Resent . . . . . . . . . . . . . . . . . . . . . . . . . . 444 Sgsn_Open_Cdr_Stat_Report_Length . . . 443 SGSN_OPEN_CDR_STAT fields . . . . 442 Sgsn_Cs_Cdr_Stat_Disc_Iu_Smt_Cdrs_Due_Resent . . . . . . . . . . . . . . . . . . . . . . . . . . 446 Sgsn_Open_Cdr_Stat_Prepaid_S_Cdrs . . . . . . . . . 448 Sgsn_Iu_Ra_Paging_Stat_Report_Id . . . . . . . 450 Sgsn_Iu_Ra_Paging_Stat_Physical_Papu_Id . . . . . . . . 447 Sgsn_Open_Cdr_Stat_Roaming_Gb_S_Cdrs . . . . . . . . . . 444 Sgsn_Open_Cdr_Stat_Report_Time . . . . . . . . . . . . . . . 450 Sgsn_Iu_Ra_Paging_Stat_Papu_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 Sgsn_Cs_Cdr_Stat_Disc_Iu_Smo_Cdrs_Due_Other . . . . . . . . . . . 445 Sgsn_Open_Cdr_Stat_Ipv6_S_Cdrs . . . . . . . . . . . . . . . . 447 Sgsn_Open_Cdr_Stat_Roaming_Gb_M_Cdrs . . . . . . . . . . . . . . . . . . . . . . . 446 Sgsn_Open_Cdr_Stat_Prepaid_M_Cdrs . . . . . . . 445 Sgsn_Open_Cdr_Stat_Gb_M_Cdrs . . . . . . . . . . . 451 Sgsn_Iu_Ra_Paging_Stat_RA_Elements_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 Sgsn_Open_Cdr_Stat_Secondary_S_Cdrs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 Id:0900d80580944034 DN05148836 Issue 2-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Sgsn_Cs_Cdr_Stat_Peak_Master_Queue_Length . . . 449 Sgsn_Iu_Ra_Paging_Stat_Report_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 Sgsn_Open_Cdr_Stat_Camel_S_Cdrs . . . . . . . . . . . . . . . 448 SGSN_IU_RA_PAGING_STAT fields . . . . 442 Sgsn_Cs_Cdr_Stat_Ave_Master_Queue_Length_Sum . . . . . . . . . 445 Sgsn_Open_Cdr_Stat_Gb_S_Cdrs . . . . . . . . . . . . 448 Sgsn_Open_Cdr_Stat_Roaming_Iu_S_Cdrs . . . . . . . . . . . . 450 Sgsn_Iu_Ra_Paging_Stat_Papu_Group_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Traffica Reference Guide for SGSN Direct Interface Table 608 Table 609 Table 610 Table 611 Table 612 Table 613 Table 614 Table 615 Table 616 Table 617 Table 618 Table 619 Table 620 Table 621 Table 622 Table 623 Table 624 Table 625 Table 626 Table 627 Table 628 Table 629 Table 630 Table 631 Table 632 Table 633 Table 634 Table 635 Table 636 Table 637 Table 638 Table 639 Table 640 Table 641 Table 642 Table 643 Table 644 Table 645 Table 646 Table 647 Table 648 Table 649 Table 650 Table 651 Table 652 Table 653 Table 654 18 Sgsn_Cs_Cdr_Stat_Disc_Iu_M_Cdrs_Due_Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 Sgsn_Iu_Ra_Paging_Stat_Papu_Capa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 Sgsn_Cs_Cdr_Stat_Disc_Iu_Smt_Cdrs_Due_Other . . . . . . . . . . 449 Sgsn_Iu_Ra_Paging_Stat_Report_Time . . . . . . . . . . . . . 446 Sgsn_Open_Cdr_Stat_Camel_M_Cdrs . . . . . . . . . . . . . . . 442 Sgsn_Cs_Cdr_Stat_Ave_Master_Queue_Length_Den . . . . . . . . . . 449 Sgsn_Iu_Ra_Paging_Stat_Report_Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Sgsn_Open_Cdr_Stat_Report_Id . . . . . . . . 445 Sgsn_Open_Cdr_Stat_Ipv4_S_Cdrs . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 Sgsn_Cs_Cdr_Stat_Generated_Iu_Smt_Cdrs . . . . . . . . . 441 Sgsn_Cs_Cdr_Stat_Generated_Iu_Pp_Smt_Cdrs . . . . . . . . . . . . . 444 Sgsn_Open_Cdr_Stat_Report_Date . . . . . . . . . . 441 Sgsn_Cs_Cdr_Stat_Disc_Iu_Smt_Cdrs_Due_Overflow . . . . . . . . . . . . . .Traffica Reference Guide for SGSN Direct Interface Table 655 Table 656 Table 657 Table 658 Table 659 Table 660 Table 661 Table 662 Table 663 Table 664 Table 665 Table 666 Table 667 Table 668 Table 669 Table 670 Table 671 Table 672 Table 673 Table 674 Table 675 Table 676 Table 677 Table 678 Table 679 Table 680 Table 681 Table 682 Table 683 Table 684 Table 685 Table 686 Table 687 Table 688 Table 689 Table 690 Table 691 Table 692 Table 693 Table 694 Table 695 Table 696 Table 697 Table 698 Table 699 Table 700 Table 701 DN05148836 Issue 2-2 Sgsn_Iu_Ra_Paging_Stat_Cgi_Mcc . . . Id:0900d80580944034 452 452 452 452 453 453 453 454 454 454 454 455 455 455 455 456 456 456 456 457 457 457 457 458 458 458 458 459 459 459 459 460 460 460 461 461 461 461 462 462 462 463 463 463 464 464 464 19 . . . . . . . . Sgsn_Paging_Stat_Report_Length . . . . . . . . . . . . . . . . . . . . . SGSN_GTP_C_STAT fields . . . . . . . . Sgsn_Paging_Stat_Pagings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Gtp_C_Stat_Report_Count . . . . . . . . . . . . . . . . Sgsn_Paging_Stat_Cgi_Lac . . . . . . . . . . . . . . . . . . . Sgsn_Iu_Paging_Stat_Papu_Capa . . . Sgsn_Paging_Stat_Papu_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Gtp_C_Stat_Report_Id . . . . . . . . Sgsn_Paging_Stat_Cgi_Rac . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Iu_Paging_Stat_Physical_Papu_Id . . . . . . . . . . . . Sgsn_Iu_Paging_Stat_Papu_Group_Id . . . . . . . . . Sgsn_Paging_Stat_Pagings . . . . . . . . . . . . . . . . . . . . Sgsn_Paging_Stat_Report_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Iu_Paging_Stat_Report_Length . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Paging_Stat_Last_Message . . . . . . . . Sgsn_Iu_Paging_Stat_Papu_Id . . . . . Sgsn_Iu_Paging_Stat_Report_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Paging_Stat_Sequence_Nr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN_PAGING_STAT fields . Sgsn_Paging_Stat_Report_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Iu_Ra_Paging_Stat_Cgi_Rac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Paging_Stat_Papu_Capa . . Sgsn_Iu_Paging_Stat_Report_Time . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Iu_Ra_Paging_Stat_Cgi_Lac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Paging_Stat_RA_Elements_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Paging_Stat_Cgi_Mnc . Sgsn_Paging_Stat_RA_Elements_Count . . . SGSN_IU_PAGING_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Paging_Stat_Cgi_Rac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Paging_Stat_Report_Count . Sgsn_Paging_Stat_Report_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Iu_Ra_Paging_Stat_Pagings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Gtp_C_Stat_Report_Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Iu_Paging_Stat_Paging_Attempts . . . . . . . . . . . . Sgsn_Paging_Stat_Cgi_Ci . . . Sgsn_Paging_Stat_Cgi_Lac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Paging_Stat_Cgi_Mcc . . . . . Sgsn_Iu_Paging_Stat_Unsuccessful_Pagings . . . . . . . . . . Sgsn_Iu_Paging_Stat_Report_Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Paging_Stat_Cgi_Mnc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Paging_Stat_Cgi_Mcc . . . . . Sgsn_Iu_Paging_Stat_Sgsn_Level_Pagings . . . . . . . . Sgsn_Paging_Stat_Papu_Group_Id . . . . . . . . . . . Sgsn_Paging_Stat_Physical_Papu_Id . . . Sgsn_Iu_Paging_Stat_Report_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Iu_Ra_Paging_Stat_Cgi_Mnc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474 Sgsn_Ul_Iu_Gtp_Packets_Pc_1 . . . . . . . . . . . . 474 Sgsn_Drop_Iu_Gtp_Packets_Pc_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 Sgsn_Gtp_Stat_ wynona_overl_data . . . . . . . . . . . . . 472 Sgsn_Ippu_Gtp_Stat_Ave_Buf_Fill_Ratio_Nominator . . . . . . . . . . . . 472 Sgsn_Ippu_Gtp_Stat_Discarded_Packets . . . . . . . . . . . . . . . . . . 467 Sgsn_Gtp_C_Stat_Bytes_In_Received_Gtpv1_Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466 Sgsn_Gtp_C_Stat_Sent_Gtpv0_Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 Sgsn_Gtp_C_Stat_Bytes_In_Received_Erroneous_GTPv0_Signaling . . . . . . . . . . . . . . . . . . 465 Sgsn_Gtp_C_Stat_Papu_Id . . . . . . . . . . . . 465 Sgsn_Gtp_C_Stat_Papu_Group_Id . . . . . . . . . . 467 Sgsn_Gtp_C_Stat_Received_Gtpv1_Signaling . . . . . . . . . . . . . . . . . . 473 Sgsn_Dl_Iu_Gtp_Bytes_Pc_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 Id:0900d80580944034 DN05148836 Issue 2-2 . . . . . . . . . . . . . . . . . . . . . 475 Sgsn_Drop_Iu_Gtp_Bytes_Pc_2 . . . . . . . . . . . . . . . . 472 Sgsn_Ippu_Gtp_Stat_Buffer_Fill_Ratio_Peak . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468 Sgsn_Gtp_C_Stat_Bytes_In_Received_Erroneous_Gtpv1_Signaling 468 SGSN_IPPU_GTP_STAT fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 Sgsn_Gtp_C_Stat_Received_Erroneous_Gtpv0_Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468 Sgsn_Gtp_C_Stat_Bytes_In_Sent_Gtpv1_Signaling . . . . . . . . . . . . 469 Sgsn_Ippu_Gtp_Stat_Report_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 Sgsn_Ippu_Gtp_Stat_Dl_Packets . . . . . . . . . . . . . . . . . . . . . . . . . 471 Sgsn_Ippu_Gtp_Stat_Dl_Bytes . . . . . . . 472 Sgsn_Ippu_Gtp_Stat_Ave_Buf_Fill_Ratio_Numerator . . . . . . . 468 Sgsn_Gtp_C_Stat_Sent_Gtpv1_Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470 Sgsn_Ippu_Gtp_Stat_Report_Time . . . . 475 Sgsn_Dl_Iu_Gtp_Packets_Pc_2 . . . . . . . . . . . . . 466 Sgsn_Gtp_C_Stat_Sent_Gtpv0_Signaling . . . . . . 468 Sgsn_Gtp_C_Stat_Received_Erroneous_Gtpv1_Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 Sgsn_Ippu_Gtp_Stat_Ul_Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . 469 Sgsn_Ippu_Gtp_Stat_Report_Length . . . . . . . . . . . . . . . . . . . . . . . . . . 471 Sgsn_Ippu_Gtp_Stat_Ul_Packets . . . . . . . . . . . 475 Sgsn_Ul_Iu_Gtp_Bytes_Pc_2 . . . . . . . . . . . . . . . . . . . . . . 469 Sgsn_Ippu_Gtp_Stat_Report_Id . . . . . . . . . . . . . . . . . . . . . . . .Traffica Reference Guide for SGSN Direct Interface Table 702 Table 703 Table 704 Table 705 Table 706 Table 707 Table 708 Table 709 Table 710 Table 711 Table 712 Table 713 Table 714 Table 715 Table 716 Table 717 Table 718 Table 719 Table 720 Table 721 Table 722 Table 723 Table 724 Table 725 Table 726 Table 727 Table 728 Table 729 Table 730 Table 731 Table 732 Table 733 Table 734 Table 735 Table 736 Table 737 Table 738 Table 739 Table 740 Table 741 Table 742 Table 743 Table 744 Table 745 Table 746 Table 747 20 Sgsn_Gtp_C_Stat_Report_Time . . 473 Sgsn_Ul_Iu_Gtp_Bytes_Pc_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470 Sgsn_Ippu_Gtp_Stat_Event_Count . . 474 Sgsn_Drop_Iu_Gtp_Bytes_Pc_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 Sgsn_Dl_Iu_Gtp_Packets_Pc_1 . . . . 470 Sgsn_Ippu_Gtp_Stat_Report_Date . . . . . . . . . . . . . . . 465 Sgsn_Gtp_C_Stat_Papu_Capa . . . . . . . . . . 465 Sgsn_Gtp_C_Stat_Physical_Papu_Id . . . . . . . 475 Sgsn_Ul_Iu_Gtp_Packets_Pc_2 . . . 466 Sgsn_Gtp_C_Stat_Bytes_In_Sent_Gtpv0_Signaling . . . . . . . . . . . . . 464 Sgsn_Gtp_C_Stat_Report_Date . . . . . . . 474 Sgsn_Dl_Iu_Gtp_Bytes_Pc_2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466 Sgsn_Gtp_C_Stat_Bytes_In_Received_Gtpv0_Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470 Sgsn_Ippu_Gtp_Stat_Physical_Ippu_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Ul_Iu_Gtp_Packets_Pc_4 . . . . . . . . . . . . . . Sgsn_Drop_Iu_Gtp_Bytes_Pc_3 . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Ul_Iu_Gtp_Bytes_Pc_4 . . . . . . Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_2 . . . . Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Alloc_Retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Ippu_Pdp_Thr_Stat_Report_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Ippu_Pdp_Thr_Stat_Ts_Time . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Dl_Iu_Gtp_Packets_ Pc_Str . . . . . . . . . . . . . Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Deliv_Of_Erroneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Drop_Iu_Gtp_Bytes_Pc_4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Ippu_Pdp_Thr_Stat_Report_Date . . . . . . . . . . Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_3 . . . . . . . . . Sgsn_Ul_Iu_Gtp_Packets_ Pc_Str . . . . . . . . . Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_5 . . . . . . Sgsn_Ul_Iu_Gtp_Bytes_ Pc_Con . . . . . Sgsn_Ippu_Pdp_Thr_Stat_Physical_Ippu_Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_1 . . . Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_4 . . . . . . . . . . . . . . . . . . Sgsn_Ippu_Pdp_Thr_Stat_Report_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Dl_Iu_Gtp_Packets_Pc_4 . . . . . . . . . . . . . . . . . . . Sgsn_Ul_Iu_Gtp_Bytes_Pc_3 . . . . . . . . . Sgsn_Drop_Iu_Gtp_Bytes_ Pc_Con . . . . Sgsn_Drop_Iu_Gtp_Packets_ Pc_Str . . . . . . . . . . . . . Id:0900d80580944034 476 476 476 477 477 477 477 478 478 478 478 479 479 479 479 480 480 480 480 481 481 481 481 482 482 482 483 483 483 483 484 484 484 484 485 485 485 485 486 486 486 486 487 487 487 487 488 21 . . Sgsn_Dl_Iu_Gtp_Bytes_Pc_3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Drop_Iu_Gtp_Packets Pc_Con . . . . . . . . . . . . . . . . . . . . . Sgsn_Ul_Iu_Gtp_Packets_ Pc_Con . . . . . . Sgsn_Ippu_Pdp_Thr_Stat_Last_2bytes_Ggsn_Address . . . . . . . . . . Sgsn_Drop_Iu_Gtp_Packets_Pc_3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Dl_Iu_Gtp_Bytes_ Pc_Str . . . . . Sgsn_Dl_Iu_Gtp_Packets_Pc_3 . . . . . . . . . . . . . . Sgsn_Ul_Iu_Gtp_Bytes_ Pc_Str . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Traffica Reference Guide for SGSN Direct Interface Table 748 Table 749 Table 750 Table 751 Table 752 Table 753 Table 754 Table 755 Table 756 Table 757 Table 758 Table 759 Table 760 Table 761 Table 762 Table 763 Table 764 Table 765 Table 766 Table 767 Table 768 Table 769 Table 770 Table 771 Table 772 Table 773 Table 774 Table 775 Table 776 Table 777 Table 778 Table 779 Table 780 Table 781 Table 782 Table 783 Table 784 Table 785 Table 786 Table 787 Table 788 Table 789 Table 790 Table 791 Table 792 Table 793 Table 794 DN05148836 Issue 2-2 Sgsn_Drop_Iu_Gtp_Packets_Pc_2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Dl_Iu_Gtp_Packets_ Pc_Con . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Ippu_Pdp_Thr_Stat_Report_Count . . . . . . . Sgsn_Dl_Iu_Gtp_Bytes_ Pc_Con . . Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Delivery_Order . . . . . Sgsn_Ippu_Pdp_Thr_Stat_Report_Length . . . . . Sgsn_Drop_Iu_Gtp_Packets_Pc_4 . . . . . . . . . . . . . Sgsn_Ippu_Gtp_Stat_Dropped_Dl_Bytes . . . . . . . . . . . . . . . . . . . SGSN_IPPU_PDP_THR_STAT fields . . . . . . . . . . . . . . . . Sgsn_Ippu_Pdp_Thr_Stat_Duration . . . . . . . . . . . . Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_Ms_Cont_Prof_Flag . . . . . . . . . Sgsn_Ippu_Pdp_Thr_Stat_Charging_Index . . . . . . . . . . . . . . . . . . . . . . Sgsn_Dl_Iu_Gtp_Bytes_Pc_4 . . Sgsn_Ippu_Pdp_Thr_Stat_Pdp_Cxt_Element_Count . . . . . . . . . . . . . . . . . . . . Sgsn_Drop_Iu_Gtp_Bytes_ Pc_Str . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sgsn_Ul_Iu_Gtp_Packets_Pc_3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_9 . . . . . . . . . . . . . . . . 492 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Spare . . . . . . . . . . 490 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Max_Bitrate_Ul . . . . . . . 491 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Guaran_Bit_Rate_Ul . . . . . . 497 Logical field:Extended Negotiated Qos Max Bitrate Ul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_13 . . . 492 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Source_Statistics . . . . . . . . . . . 492 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Guaran_Bit_Rate_Dl . . . . . . . . . . . . . . . . . . . . . . 491 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Transfer_Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 Logical field: Extended Negotiated Qos Deliv Of Errorneous . . . . . . . . . . . . . . . . . . . . . 494 Sgsn_Ippu_Pdp_Thr_Stat_Uplink_Data . . . . . . . . . . . . . 494 Logical field: Operator . . . . . . . . . . . . . . . . . . . . 488 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_8 . . . . . . . . . . . . 491 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Traffic_Handling_Prio . . . . . . . . . . . . 493 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Ext_Guaran_Bit_Rate_Dl . . . . . . . . . . . 490 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Max_Bitrate_Dl . . . . . . . . . 490 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Max_Sdu_Size . . . . . . . . . . . . . . . 497 Logical field: Extended Negotiated Qos Max Sdu Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495 Logical field: Neg_Qos_Ext_Guar_Br_Ul . . . . 497 Logical field: Extended Negotiated Qos Max Bitrate Dl . . 495 Logical field: Mobile station . . . . . . . . . . . . . . . . . . . 497 Logical field: Extended Negotiated Qos Traffic Class . . . . . . . . . . . . . . . . . . . 489 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_12 . . . . . . . . . . . . . . . . . . . . . . . . . . 490 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Traffic_Class . . . . . . . . . . 489 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_11 . . . 493 Sgsn_Ippu_Pdp_Thr_Stat_Imsi . . . . . . . . . . . 494 Sgsn_Ippu_Pdp_Thr_Stat_Downlink_Data . . . . . . . 493 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Ext_Max_Bit_Rate_Dl . . . . . . . . . . . . . . . . . . . . . . . . 489 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_14 . . . . . . . . . . . . . . . . . . . . . 496 Logical field: Extended Negotiated Qos Alloc Retention . . 495 Logical field: Neg_Qos_Ext_Max_Br_Ul . . . . 491 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Sdu_Error_Ratio . . . . . . . . . . . . . . . . . . 492 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Signalling_Indication . . . . . . . . . . . . . . . . . . . . . . . . . . 496 Logical field: Qos Negotiated 14 . . . . . . . . . . . . . . . . . . 493 Sgsn_Ippu_Pdp_Thr_Stat_Imsi_Length . 498 Id:0900d80580944034 DN05148836 Issue 2-2 . . . . 496 Logical field: Qos Negotiated 13 . . . . . . .Traffica Reference Guide for SGSN Direct Interface Table 795 Table 796 Table 797 Table 798 Table 799 Table 800 Table 801 Table 802 Table 803 Table 804 Table 805 Table 806 Table 807 Table 808 Table 809 Table 810 Table 811 Table 812 Table 813 Table 814 Table 815 Table 816 Table 817 Table 818 Table 819 Table 820 Table 821 Table 822 Table 823 Table 824 Table 825 Table 826 Table 827 Table 828 Table 829 Table 830 Table 831 Table 832 Table 833 Table 834 Table 835 Table 836 Table 837 Table 838 Table 839 Table 840 22 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_6 . . . . . . . . . 497 Logical field: Extended Negotiated Qos Delivery Order . . . . . . . . . 488 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_10 . . . . . . . . . . . 491 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Residual_Ber . . 495 Logical field: Req_Qos_Ext_Max_Br_Ul . . . . . . . . . . . . . . . . 488 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_7 . . . . . . . . . . . . . . . . . . . . 494 Sgsn_Ippu_Pdp_Thr_Stat_Ra_Access_Type . . . . . . . . . . . 498 Logical field: Extended Negotiated Qos Sdu Error Ratio . . . . . . . . . . . . . . . . . . . . 495 Logical field: Req_Qos_Ext_Guar_Br_Ul . . . 498 Logical field:Extended Negotiated Qos Residual Ber . . . . . . . . . . . . . . . . . . . . . 518 MS initiated service request rejected by the network . . . . . . .Location update procedure *SM cause(External cause to MS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Create PDP context response . . . . . . . . . . . . . . . 527 Release 97/98 fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500 Logical field: Extended Negotiated Qos Ext Guaran Bit Rate Ul . . 498 Logical field: Extended Negotiated Qos Transfer Delay . . . . . . 516 Network requested PDP context deactivation . . . . 521 Cause mapping between Gr interface(MAP protocol/HLR/AuC --> SGSN -> MS) . 528 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause . . . . . . . . . . . . . . . . . . . . . . . . 507 MS initiated combined RAU accepted for GPRS services only (CS-side fails). . . . . . . . . . . . . . 512 MS initiated PDP context activation rejected by network . . . . . . . . . . . . . . . . . . 519 NW initiated detach request . . . . . . . . 500 Logical field: Extended Negotiated Qos Ext Max Bit Rate Dl . . . . . . . 499 Logical field: Extended Negotiated Qos Guaran Bit Rate Ul . . . . . 526 QoS_Reguested/Negotiated_Octet fields . . . . . 527 Release 99 fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501 MS initiated attach (GPRS or combined) rejected by network . . . . . . . . . . . . . . 500 Logical field: Extended Negotiated Qos Ext Guaran Bit Rate Dl . . . . . . . . . . . . . . . . 499 Logical field: Extended Negotiated Qos Source Statistics . . 525 Cause mapping between GGSN --> SGSN --> MS . . . . . . . . . . . . . . . . 500 Logical field: Extended Negotiated Qos Ext Max Bit Rate Ul . . . . . 502 MS initiated combined attach accepted GPRS services only (CS-side fails) 505 MS initiated Routing area update rejected by network . 499 Logical field: Extended Negotiated Qos Signalling Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499 Logical field: Extended Negotiated Qos Guaran Bit Rate Dl .Update PDP context response . . 499 Logical field: Extended Negotiated Qos Spare . . . . . . . . 524 Cause mapping between GGSN --> SGSN --> MS . . . . . . . . 513 MS initiated PDP context modification rejected by network . . . . . .Traffica Reference Guide for SGSN Direct Interface Table 841 Table 842 Table 843 Table 844 Table 845 Table 846 Table 847 Table 848 Table 849 Table 850 Table 851 Table 852 Table 853 Table 854 Table 855 Table 856 Table 857 Table 858 Table 859 Table 860 Table 861 Table 862 Table 863 Table 864 Table 865 Table 866 Table 867 DN05148836 Issue 2-2 Logical field: Extended Negotiated Qos Traffic Handling Prio . . . . . . . 530 Id:0900d80580944034 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 1 24 Terms Id:0900d805809551ce DN05148836 Issue 2-2 . SG8 (ATCA). Consequently. For more information. see Administering Traffica.4 SP2 and SGSN releases SG7 CD3. refer to Glossary. SG7 CD6. When an RTT arrives in Traffica.4 SP2 Terms The following table lists the most important terms used in this document. Database capacity depends on the size of the hard disk and the volume of network traffic. and functions as a data storage for the counter values post-processed from RTTs.1 Where to find more information If you are unfamiliar with any of the terms used in this manual. It is a convenient reference for the Traffica system administrator as well as the Traffica user. see RTT report descriptions. Once the RTT report data is in the IDS. For detailed information on the predefined CCMA. SG7 CD4. For information on the CCMA. use Traffic News. the contents of an IDS field are identical with the contents of an RTT report field. IDS field An IDS field is mapped with a corresponding field in an RTT report. refer to: • • • 1. Concept Description CCMA (Clear Code Matrix) A tree structure which consists of nodes and counters. For more information. see section Clear Code Matrix Database A data storage for all RTTs in the TNES. which are in the IDS. the CCMA is scanned through and the counters are updated. Traffica uses the data in the RTT reports. Traffica stores the reports from the IDS into the database. For further information on Traffica. SG7 CD5.1. This document relates to Traffica Z5. the fields in the report are mapped with corresponding IDS fields. The database is automatically cleaned up and oldest data is deleted. 1. SG8 CD2(ATCA). and SG8 CD3(DX200). To access the database. refer to Traffica Principles.2 Traffica Principles Administering Traffica Installation Guide for Traffica release Z5. SG8 CD2(Dx200).About this document Traffica Reference Guide for SGSN Direct Interface 1 About this document Traffica Reference Guide for SGSN Direct Interface offers reference material related to both real-time monitoring and analysis of traffic data. for updating the CCMA. Internal Data Structure (IDS) Traffica forwards an RTT report as such into Traffica’s IDS. ) Id:0900d805809551ce 25 . for example. for example. for example. The term also includes redirected RTT reports that are transferred from a TNES to a TS. RTT (Real-time Traffic) report “RTT reports” is a general term used for the real-time traffic reports that are generated by NEs and issued to the connected TNES. one second. the counters in the current time slice are updated in real-time. minute. Time resolutions are user-definable. This technology employs 3GPP based WCDMA standards that propose the use of direct tunneling between RNC and GGSN for user plane data while the control plane packets continues to go through SGSN. The duration of the time slice defines how long the data accumulates. Time resolution is a range of time slices. Table 1 DN05148836 Issue 2-2 TNESs collect the RTT reports and these reports are stored into the Traffica database. and for the user it is typically visualised as a range of bars in a graph. the time slice is either stored as historical data or deleted. and a new time slice is started. When the defined time for one time slice is over. Traffica Network Element Server (TNES) A TNES is the Traffica that is connected to an NE. A time resolution defines how long a time the counters in that particular tree branch are accumulated before the counters are reset and how many time slices are stored in the memory as history data. During the time defined in the time resolution. is a NSN proprietary concept used for increasing the throughput of SGSN by eliminating the need to route user plane packets between RNC to GGSN via SGSN. Mobile Switching Centre (MSC). 1*1 day or 30*1 minute. Fixed Switching Centre (FSC) or SGSN. MO-SMS Mobile originated Short Message Service MT-SMS Mobile Terminated short Message Service Network Element (NE) General term.Traffica Reference Guide for SGSN Direct Interface About this document Concept Description I-HSPA I-HSPA an acronym for Internet HSPA. Terms (Cont. Time resolution A time resolution gives meaning to a Time Class. or hour. used for all NEs that Traffica can be connected to. The duration of one time slice can be. Traffic News Client A tool that can be used for database queries and can be installed into an office PC. Time Class A root item in the CCMA tree structure which acts as a container of the time resolution(s) and CCMA members. When you define a time resolution you define two things: the duration of one time slice and the number of these time slices. 3 Terms (Cont.About this document Traffica Reference Guide for SGSN Direct Interface Concept Description UMA Unlicensed Mobile Access (UMA) technology provides access to GSM and GPRS mobile services over unlicensed spectrum technologies.11. including Bluetooth and 802. subscribers receive a consistent user experience for their mobile voice and data services as they transition between networks.High speed Packet Access PS Packet Switched RCH Remote Communications function REDI Real-time Graphs function RTT (report) Real-time Traffic (report) SGIPRB SGSN IN Control Application Program Block Table 2 26 Abbreviations Id:0900d805809551ce DN05148836 Issue 2-2 . Abbreviation Explanation AH Alarms function CCMA Clear Code Matrix CCMAH Clear Code Matrix function DBBH Database Backup function DBH Database function DME Data Mediation Engine DRH Data Redirector function FTH File Transfer function GCSPRB GPRS Charging and Statistics Combiner Program Block GGBPRB GPRS Gb interface Protocol Stack Program Block GGSN Gateway GPRS Support Node GIPPRB GPRS Air Interface Transport Protocols Program Block GMGPRB Mobility and Session Manager Program Block GRNPRB Subscriber Registration Services Program Block GSPPRB Mobility and Session Management Protocol Program Block GS1PRB GPRS Short Message Delivery Service Program Block GTPPRB Backbone Tunneling Program Block IDS Internal Data Structure I-HSPA Internet. service providers can enable subscribers to roam and handover between cellular networks and public and private unlicensed wireless networks using dual-mode mobile handsets. With UMA. Table 1 1.) Abbreviations The following table lists the abbreviations used in this manual. By deploying UMA technology. Traffica Reference Guide for SGSN Direct Interface Abbreviation Explanation TNES Traffica Network Element Server UMA Universal Mobile Access Table 2 DN05148836 Issue 2-2 About this document Abbreviations (Cont.) Id:0900d805809551ce 27 . Changes in Z5.4 No changes.1 which includes support for IHSPA (internet HSPA) traffic.3 Traffica supports SGSN interface version SG8. see Network element compatibility and support in Functionality Changes in Traffica.Change information Traffica Reference Guide for SGSN Direct Interface 2 Change information This chapter lists changes between releases in this document. graph sets. For detailed information about supported network element versions. Changes in Z5. graph categories and time classes have been replaced with TRAF. with information on licenses that are required by the SGSN in order for the Traffica interface to work. The description of field Sgsn_rtt_tunnel_info has been updated with more specific information about the possible values. see Network element compatibility and support in Functionality Changes in Traffica. Changes in Z5. 28 Id:0900d805809551ce DN05148836 Issue 2-2 . which includes support for SGSN on the ATCA platform. Changes in Z5. Appendix Internal cause to interface cause mapping from MM & SM processes has been updated to SG70 level.2 Traffica supports SGSN interface version SG7 PCD3. For detailed information about supported network element versions. For detailed information about supported network element versions. Chapter Required licenses for the SGSN has been added. Changes in Z5 All references to NOKIA in predefined graphs. see Network element compatibility and support in Functionality Changes in Traffica. The descriptions of RTT fields Sgsn_Rtt_Data_Amount_Down and Sgsn_Rtt_Data_Amount_Up have been updated.4 SP1 No changes. Feature Code 541. but the Traffica RTT Monitoring Report Sending license is always needed in order to be able to operate both the Traffica Non RTT Monitoring Report Sending and the Traffica Report Sharing and Redundancy licenses. Traffica Non Real-time Traffic (Non RTT) Monitoring Report Sending.Traffica Reference Guide for SGSN Direct Interface Required licenses for the SGSN 3 Required licenses for the SGSN There are 3 licenses related to this feature: • • • Traffica Real-time Traffic (RTT) Monitoring Report Sending. The licenses can be purchased separately. Feature Code 540. Traffica Report Sharing and Redundancy. DN05148836 Issue 2-2 Id:0900d805809551ce 29 . Feature Code 539. PAGING_STAT. every other second. PDP context deactivation (successful/unsuccessful) • Mobile requested PDP context deactivation • GMC requested PDP context deactivation • PDP context deactivation due to network status • Network requested PDP context deactivation 3. The following are real-time reports: SGSN_RTT. 4. IU_PAGING_STAT. OPEN_CDR_STAT. PDP_THR_STAT. unspecified • Power off detach • MS originated GPRS detach • MS originated GPRS/IMSI detach • MS originated IMSI detach • Network requested GPRS detach 30 Id:0900d805809551ce DN05148836 Issue 2-2 . These reports are sent to Traffica. SGSN_SMS_RTT The rest are timed reports: CDR_STAT. CS_CDR_STAT. PDP context modifications (successful/unsuccessful) • Mobile or Network originated PDP context modification • Context activation to another PAPU or SGSN • HLR initiated PDP context modification 4. GTP_C_STAT.1. for example. PDP context activation (successful/unsuccessful) • Mobile requested PDP context activation • Network requested PDP context activation 2. GTP_STAT. unspecified • GPRS attach • Combined GPRS/IMSI attach • IMSI attach • Outgoing inter-SGSN attach (in new SGSN) • Outgoing inter-PAPU attach (in new PAPU) 5. IU_RA_PAGING_STAT. SGSN also receives data from GPRS mobiles and sends data to the mobiles. LOA_STAT. IPPU_GTP_STAT and IPPU_PDP_THR_STAT.1 RTT reports RTT reports are generated in following situations in SGSN: 1. BSSGP_PAPU_STAT.1 SGSN adaptation SGSN (Serving GPRS support node) in GPRS has a similar function as MSC in GSM. SGSN_BSSGP_CELL_STAT and PAGING_STAT. Detaches (successful/unsuccessful) • Detach.Principles of RTT report processing Traffica Reference Guide for SGSN Direct Interface 4 Principles of RTT report processing 4. Attaches (successful/unsuccessful) • Attach. It takes care of identifying GPRS mobiles. SGSN_PDP_RTT. PAPU_USER_STAT. registering to GPRS network and mobility management. NSVC_STAT. SGSN sends data to Traffica in 20 report types. I-HSPA RA updates 7. Subscriber location (LAC.Traffica Reference Guide for SGSN Direct Interface Principles of RTT report processing • Network requested GPRS/IMSI detach • Network requested IMSI detach • Implicit GPRS detach • Implicit GPRS/IMSI detach 6.2 Access Point Name (APN) GGSN IP address QoS data. and SAC) An Error Cause Code in case of an unsuccessful event PAPU details Roaming status and charging information The following additional information is shown in PDP context activations. and deactivations: • • • 4. IMEI. Cell ID. MSISDN and P-TMSI. Routing area updates • RA update. Data volumes GTP_STAT reports These events are reported every minute per PAPU.1. SMS deliveries (successful/unsuccessful) • MO-SMS • MT-SMS Information contained in RTT reports The following information is present in RTT reports: • • • • • Subscriber IMSI. These reports contain the following information about the past minute: • • • • • DN05148836 Issue 2-2 amount of GTP data packets sent in uplink direction amount of GTP data packets sent in downlink direction amount of GTP data in bytes sent in uplink direction amount of GTP data in bytes sent in downlink direction average GTP buffer filling ratio Id:0900d805809551ce 31 . type unspecified • Intra PAPU RA update • Inter PAPU RA update • Inter SGSN RA update • Inter SGSN RA update with IMSI attach • Intra PAPU RA update with IMSI attach • Inter PAPU RA update with IMSI attach • Intra PAPU combined RA/LA update • Inter PAPU combined RA/A update • Inter SGSN combined RA/LA update • Periodic combined RA/LA update • Periodic combined RA update • Outgoing inter PAPU RA update (in old PAPU) • Outgoing inter SGSN RA update (in old SGSN) • 2G. 3G. modifications. RAC. These events are reported every 15 minutes per SGSN.5 Average processor load Peak processor load Number of successful samples NSVC_STAT reports These events are reported every 15 minutes per PAPU unit.Principles of RTT report processing • • 4.1.3 Traffica Reference Guide for SGSN Direct Interface value of peak buffer filling ratio amount of discarded GTP packets CDR_STAT reports Charging record generator report (S4SPRB). These reports contain the following information about the past one minute period: • • • 4.1.1.6 Frame relay passed data Discarded packets due CIR overflow IP passed data FR borrowed data in bytes FR loaned data in bytes BSSGP_PAPU_STAT reports These events are reported every 15 minutes per PAPU unit. The CDR types are: • • • • S-CDR (SGSN CDR) M-CDR (Mobility Management CDR) S-SMO-CDR (SGSN MO-SMS CDR) S-SMT-CDR (SGSN MT-SMS CDR) In total there are four CDR_STAT reports every 15 minutes. There is one report for each CDR type. Each report contains the following information about the past 15 minute period: • • • • 32 BSSGP buffer utilization average per priority BSSGP buffer utilization peak values per priority BSSGP lost downlink data in bytes per priority BSSGP dropped packets due redundancy elimination Id:0900d805809551ce DN05148836 Issue 2-2 .4 average CDR recovery buffer utilization peak value CDR recovery buffer utilization number of CDRs generated number of discarded CDRs because of buffer overflow number of discarded CDRs because of some other reason total number of CDRs resent to CG LOA_STAT reports These events are reported every minute from all active SGSN units. Each report contains the following information for the past 15 minute period: • • • • • • 4. Each report contains the following information about the past 15 minute period: • • • • • 4.1. 1. The values are on cell level. Downlink data.1.9 RA level pagings SGSN_PDP_THR_STAT It is highly recommended that this report is sent to its own TNES. and QOS negotiated. • 4. and Discarded Gb and Iu CDRs SGSN_OPEN_CDR_STAT Charging record generator report (GCHPRB). • 4.1.1. These events are reported every minute per SGSN • 4.1.1. a maximum of 3 times per PAPU.12 MO-SMS and MT-SMS deliveries and delivery errors SGSN_PAPU_USER_STAT These events are reported every minute per PAPU.13 For example Attached Gb and Iu users.11 For example RA level pagings SGSN_SMS_RTT These events are reported immediately when they appear.1. and Open PDP Gb and Iu PDP contexts SGSN_CS_CDR_STAT Charging sender (GIGPRB) report. a maximum of 10 times per PAPU. Each report contains the following information about the past 15 minute period: • • 4. SGSN_RA_PAGING_STAT These events are reported every 15 minutes per PAPU.Traffica Reference Guide for SGSN Direct Interface 4.7 Principles of RTT report processing BSSGP_CELL_STAT reports These events are reported every 15 minutes.14 For example Generated Gb and Iu CDRs.1. These events are reported every second. This report is sent to Traffica a maximum of 96 times every second • 4. DN05148836 Issue 2-2 Id:0900d805809551ce 33 .10 For example Uplink data.8 Amount of data discarded by BSSGP MS-BVC flow control Amount of BSSGP MS-BVC flow control-passed data PAGING_STAT reports These events are reported every 15 minutes per SGSN. The report contains the following information about the past 15 minute period: • 4. • 4.These events are reported every minute per SGSN. So this report is sent to Traffica maximum of 96 times every second.20 For example Downlink Data. Because of this.15 Traffica Reference Guide for SGSN Direct Interface For example Open Gb and Iu CDRs SGSN_IU_RA_PAGING_STAT These events are reported every 15 minutes per SGSN.2 For example Uplink data. Uplink Data and discarded packets.1.17 For example SGSN level Gb pagings SGSN_IU_PAGING_STAT These events are reported every 15 minutes per SGSN. and QOS negotiated. • 4. Downlink data. other report types are not so relevant in respect of the capacity to send data. In addition to real-time reports several reports of type SGSN_PDP_THR_STAT are sent every second to Traffica. • 4.1.20.1. which are listed here: 1 = Report type 1 (SGSN_RTT) 2 = Report type 2 (SGSN_PDP_RTT) 34 Id:0900d805809551ce DN05148836 Issue 2-2 .1.19 For example amount of GTP v0 and GTP v1 received signalling and amount of GTP v0 and GTP v1 sent signalling SGSN_IPPU_GTP_STAT These events are reported every minute per IPPU.16 For example Iu RA level pagings SGSN_PAGING_STAT These events are reported every 15 minutes per SGSN. • 4. • 4.18 For example SGSN level Iu pagings SGSN_GTP_C_STAT These events are reported every minute per PAPU. because SGSN only sends subscribed reports to Traffica. From SG6 onwards. All report types have their own numerical value 1 .1.Principles of RTT report processing • 4. • 4. About 99 per cent of data sent to Traffica consists of reports of this type. These events are reported every second maximum of 3 times per IPPU. • 4. Traffica report subscription and blocking SGSN sends data to Traffica in 20 types of reports. Reports are subscribed or blocked in the following way. Traffica reports cannot be blocked using UTPFIL patches. SGSN_IPPU_PDP_THR_STAT It is highly recommended that this report is sent to its own TNES.1. Traffica Reference Guide for SGSN Direct Interface Principles of RTT report processing 3 = Report type 3 (SGSN_GTP_STAT) 4 = Report type 4 (SGSN_CDR_STAT) 5 = Report type 5 (SGSN_LOA_STAT) 6 = Report type 6 (SGSN_NSVC_STAT) 7 = Report type 7 (SGSN_PDP_THR_STAT) 8 = Report type 8 (SGSN_BSSGP_PAPU_STAT) 9 = Report type 9 (SGSN_BSSGP_CELL_STAT) 10 = Report type 10 (SGSN_RA_PAGING_STAT) 11 = Report type 11 (SGSN_SMS_RTT) 12 = Report type 12 (SGSN_PAPU_USER_STAT) 13 = Report type 13 (SGSN_CS_CDR_STAT) 14 = Report type 14 (SGSN_OPEN_CDR_STAT) 15 = Report type 15 (SGSN_IU_RA_PAGING_STAT) 16 = Report type 16 (SGSN_PAGING_STAT) 17 = Report type 17 (SGSN_IU_PAGING_STAT) 18 = Report type 18 (SGSN_GTP_C_STAT) 19 = Report type 19 (SGSN_IPPU_GTP_STAT) 20 = Report type 20 (SGSN_IPPU_PDP_THR_STAT) DN05148836 Issue 2-2 Id:0900d805809551ce 35 . separated with a space. all reports except PDP_THR report (number 7).3 Overload control There is an overload control mechanism implemented to statistical program block (GSTPRB).3 or 1. GSTPRB measures once per second the MCHU processor load and unhandled messages queue.Principles of RTT report processing Traffica Reference Guide for SGSN Direct Interface In the screenshot of RTT Server dialog box is shown how to subscribe reports. In the Initialisation string field write the port and the ip address of the MCHU of the SGSN. When GSTPRB notices that MCHU is in overload state following actions take place: Phase 1. you can subscribe reports 1 .2. For example. A) 36 Id:0900d805809551ce DN05148836 Issue 2-2 .3 or as in the figure. Overload state in GST means that the average percentage of MCHU’s processor load during last four seconds is over 80% (default) or that the queue of unhandled messages is over 500 (default) messages long. In Connect String field write the number of the subscribed reports. 4. traf PDP_THR and NON RTTs stop Phase 2. B) Heartbeat report identifier is changed from 0x321 to 0x320. If MCHU's overload state continues over 7 seconds after phase 1. Traffica connection is started again. Heartbeat identifier is also changed back to 0x0321. Following error logs are written to MCHU: GSTHA3: GSTHA3: GSTHA3: GSTHA3: MCHU OVERLOAD unhandled msgs of MCHU. (variable value) MCHU OL. (variable value) processor load of MCHU.Traffica Reference Guide for SGSN Direct Interface Principles of RTT report processing Sending of reports: SGSN_GTP_STAT SGSN_CDR_STAT SGSN_NSVC_STAT SGSN_PDP_THR_STAT SGSN_BSSGP_PAPU_STAT SGSN_BSSGP_CELL_STAT SGSN_RA_PAGING_STAT SGSN_PAPU_USER_STAT SGSN_CS_CDR_STAT SGSN_OPEN_CDR_STAT SGSN_IU_RA_PAGING_STAT SGSN_PAGING_STAT SGSN_IU_PAGING_STAT SGSN_GTP_C_STAT SGSN_IPPU_GTP_STAT SGSN_IPPU_PDP_THR_STAT is stopped. NOTE: SGSN_LOA_STAT report is always sent to Traffica .despite the overload status of MCHU. DN05148836 Issue 2-2 Id:0900d805809551ce 37 . sending of reports: SGSN_RTT SGSN_PDP_RTT SGSN_SMS_RTT is stopped. This helps the operator to figure out if some problems are linked to overload of units.traf RTT reports stop After the overload situation is cleared: MCHU processor load average is under 60% (default) and the number of unhandled messages is under 50 (default). The following error log is written to MCHU: GSTHA1: MCHU OL continues. See section Traffica report subscription and blocking.traf reports allowed The default limits for triggering overload situation can be modified by patching GSTPRB's parameters 3-6 of UTPFIL. SGSN can be configured to block (‘to not send’) certain Traffica reports to Traffica in order to reduce the MCHU load. 38 Id:0900d805809551ce DN05148836 Issue 2-2 .Principles of RTT report processing Traffica Reference Guide for SGSN Direct Interface The following error log is written to MCHU: GSTHA3: MCHU load normal. >=SG3 1Day/24h/30 min SGSN Report\Attaches\ Unsuccessful\LAC Vector\ Counter Counts all unsuccessful attaches for each LAC. >=SG3 1Day/24h/30 min SGSN Report\Attaches\ Unsuccessful\LAC Vector\ Error Cause Vector\ Counter Counts all unsuccessful attaches for each LAC for each Error cause code. The time class 24 Hours collects data hourly for the last 24 hours.1 5. Counters are reset and initialized every minute. There are three time classes in the CCMA: 1 Day. there will be minutely counters available until 11:30 historically. Counters are reset and initialized at the beginning of each hour. >=SG3 1Day/24h/30 min SGSN Report\Attaches\Error Cause Vector\Counter Counts all successful/unsuccessful attaches for each Error cause code. >=SG3 1Day/24h/30 min SGSN Report\Attaches\LAC Vector\ Counter Counts all successful/unsuccessful attaches for each LAC. There are separate counters for each minute for the last 30 minute period. >=SG3 1Day/24h/30 min SGSN Report\ Attaches\Counter Counts all successful/unsuccess. the Clear code matrix (CCMA). The following tables explain the counters of CCMA time classes: CCMA counter Explanation SGSN Version SGSN Report\Counter Counts all RTT reports. For example at 12:00. >=SG3 1Day/24h/30 min Table 3 TimeClass Counters of CCMA time classes DN05148836 Issue 2-2 Id:0900d805809551ce 39 . 13:00. >=SG3 1Day/24h/30 min SGSN Report\Attaches\Mobile Type Vector\Counter Counts all successful/unsuccessful attaches for each Mobile phone type. >=SG3 1Day/24h/30 min SGSN Report\ Attaches\LAC Vector\ Error Cause Vector\Counter Counts all successful/unsuccessful attaches for each LAC for each Error Cause code. 12:01. for example 12:00. 24 Hours and 30 Minutes. The time class 1 Day collects data cumulatively for one day.1. 14:00 and so on.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring 5 Real-time monitoring 5. The time class 30 Minutes collects data minutely for the last 30 minutes. 1Day/24h/30 min SGSN Report\Attaches\ Unsuccessful\Counter Counts all unsuccessful attaches. The time class is reset every midnight 00:00 and counters are initialized.>=SG3 ful attaches. The counters then update cumulatively during the current day.1 Clear code matrix Counters Traffica contains a predefined counter tree. There are separate counters for each hour for the last 24 hour period. for example at 12:00. 12:02 and so on. >=SG4 1Day/24h/30 min Counts the number of successful SGSN Report\Attaches\ Successful\ Network Operators Successful Vector\ attaches for each operator. 1Day/24h/30 min SGSN Report\Attaches\Network Operators Attempted Vector\ Counter Counts the number of attach attempts for each operator. >=SG3 1Day/24h/30 min SGSN Report\Attaches\Roaming Status\Successful\Network Operators Successful Vector\counter Counts the number of successful >=SG3 attaches attempts for each operator.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version CCMA counter Explanation SGSN Report\Attaches\Mobile Type Vector\Error Cause Vector\Counter Counts all successful/unsuccess. >=SG4 1Day/24h/30 min SGSN Report\Attaches\Roaming Status\Unsuccessful\LAC Vector\ Counter Counts all unsuccessful roaming attaches for each LAC. >=SG3 1Day/24h/30 min SGSN Report\Attaches\ Roaming Status\Counter Counts all roaming attaches. 1Day/24h/30 min Counts how many times a certain SGSN Report\Attaches\ Roaming internal situation has occurred in Status\Error Cause Vector\Program Block Vector\Internal Situation Vector\ a certain program block.) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG4 1Day/24h/30 min SGSN Report\Attaches\Roaming Status\Error Cause Vector\Program Block Vector\ Counter Counts how many times a certain program block has set a certain error cause. >=SG4 1Day/24h/30 min SGSN Report\Attaches\ Roaming Status\LAC Vector\ RAC Vector\Error Cause Vector\ Counter Counts all roaming attaches for each RAC of a specific LAC for each Error Cause.>=SG3 ful attaches for each operator. 1Day/24h/30 min SGSN Report\Attaches\ Unsuccessful\Network Operators Unsuccessful Vector\Error Cause Vector\ Counter Counts the number of error causes of the unsuccessful attaches for each operator.>=SG3 ful attaches for each Mobile phone type for each Error Cause code. >=SG4 1Day/24h/30 min SGSN Report\Attaches\ Roaming Status\Error Cause Vector\Counter Counts all successful/unsuccessful roaming attaches for each Error cause code. Counter Table 3 40 TimeClass Counters of CCMA time classes (Cont. >=SG4 1Day/24h/30 min SGSN Report\Attaches\ Roaming Status\LAC Vector\ Counter Counts all roaming attaches for each LAC. Counter >=SG4 1Day/24h/30 min SGSN Report\Attaches\Roaming Status\Unsuccessful\Counter Counts all unsuccessful roaming attaches. >=SG3 1Day/24h/30 min >=SG3 1Day/24h/30 min SGSN Report\Attaches\ Unsuccessful\Network Operators Unsuccessful Vector\Counter Counts the number of unsuccess. >=SG4 1Day/24h/30 min SGSN Report\Attaches\ Roaming Status\LAC Vector\ RAC Vector\ Counter Counts all roaming attaches for each RAC under a specific LAC. >=SG4 1Day/24h/30 min SGSN Report\Attaches\Roaming Status\Network Operators Attempted Vector\counter Counts the number of attaches attempts for each operator. 1Day/24h/30 min Table 3 TimeClass Counters of CCMA time classes (Cont.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version CCMA counter Explanation SGSN Report\Attaches\Roaming Status\Unsuccessful\LAC Vector\RAC Vector\Counter Counts all unsuccessful roaming attaches for each RAC under a specific LAC.>=SG3 ful detaches. >=SG3 1Day/24h/30 min SGSN Report\Detaches\LAC Vector\ Error Cause Vector\Counter Counts all successful/unsuccessful detaches for each LAC and for each Error Cause code. >=SG3 1Day/24h/30 min SGSN Report\RA Updates\Error Cause Vector\Counter Counts all successful/unsuccessful RA updates for each Error Cause code. >=SG3 1Day/24h/30 min SGSN Report\Detaches\Error Cause Vector\Counter Counts all successful/unsuccessful detaches for each Error Cause code. >=SG3 1Day/24h/30 min SGSN Report\RA Updates\Counter Counts all successful/unsuccessful RA updates.>=SG3 ful RA updates for each RAC. 1Day/24h/30 min SGSN Report\Detaches\Unsuccessful\ Counter Counts all unsuccessful detaches. >=SG3 1Day/24h/30 min SGSN Report\Detaches\LAC Vector\ Counter Counts all successful/unsuccessful detaches for each LAC.>=SG3 ful attaches attempts for each operator. 1Day/24h/30 min SGSN Report\Attaches\Roaming Status\Unsuccessful\LAC Vector\RAC Vector\Error Cause Vector\Counter Counts all unsuccessful roaming attaches for each RAC of a specific LAC for each Error Cause. >=SG4 1Day/24h/30 min SGSN Report\Attaches\Roaming Status\Unsuccessful\Network Operators Unsuccessful Vector\counter Counts the number of unsuccess. >=SG3 1Day/24h/30 min SGSN Report\RA Updates\RAC Vector\Counter Counts all successful/unsuccess. 1Day/24h/30 min SGSN Report\RA Updates\RAC Vector\Error Cause Vector\Counter Counts all successful/unsuccess. >=SG4 1Day/24h/30 min SGSN Report\Detaches\ Counter Counts all successful/unsuccess. >=SG3 1Day/24h/30 min SGSN Report\RA Updates\Unsuccessful\RAC Vector\Error Cause Vector\Counter Counts all unsuccessful RA updates for each RAC for each Error Cause code.>=SG3 ful RA updates for each RAC and for each Error Cause code. >=SG3 1Day/24h/30 min SGSN Report\Detaches\Unsuccessful\ LAC Vector\Error Cause Vector\ Counter Counts all unsuccessful detaches for each LAC for each Error Cause.) DN05148836 Issue 2-2 Id:0900d805809551ce 41 . >=SG3 1Day/24h/30 min SGSN Report\RA Updates\Unsuccessful\Counter Counts all unsuccessful RA updates. >=SG3 1Day/24h/30 min SGSN Report\Detaches\Unsuccessful\LAC Vector\Counter Counts all unsuccessful detaches for each LAC. >=SG3 1Day/24h/30 min SGSN Report\RA Updates\Unsuccessful\RAC Vector\Counter Counts all unsuccessful RA updates for each RAC. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Unsuccessful\Mobile Type Vector\Error Cause Vector\Vector Counts all unsuccessful PDP Context Activations for each Mobile phone type for each Error Cause code. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Unsuccessful\Mobile Type Vector\Counter Counts all unsuccessful PDP Context Activations for each Mobile phone type. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Unsuccessful\Cell Vector\Error Cause Vector\Counter Counts all unsuccessful PDP Context Activations for each Cell for each Error Cause code. >=SG3 1Day/24h/30 min Table 3 42 TimeClass Counters of CCMA time classes (Cont. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Unsuccessful\Counter Counts all unsuccessful PDP Context Activations. >=SG3 1Day/24h/30 min SGSN Report\RA Updates\Unsuccessful\Error Cause Vector\Set Prb Vector\Internal Sit Vector\Counter Counts how many times a certain internal situation has occurred in a certain program block. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Cell Vector\Error Cause Vector\ Counter Counts all successful/unsuccessful PDP Context Activations for each Cell for each Error Cause code. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Counter Counts all successful/unsuccessful PDP Context Activations. >=SG3 1Day/24h/30 min SGSN Report\RA Updates\Unsuccessful\RA Updates Vector\Error Cause Vector\Set Prb Vector\Internal Sit Vector\Counter Counts how many times a certain internal situation has occurred in a certain program block. >=SG3 1Day/24h/30 min SGSN Report\RA Updates\Unsuccessful\RA Updates Vector\Error Cause Vector\Counter Counts all unsuccessful RA Update for each RA Update type cumulatively for each error code.) Id:0900d805809551ce DN05148836 Issue 2-2 .Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version CCMA counter Explanation SGSN Report\RA Updates\Unsuccessful\Error Cause Vector\Counter Counts all unsuccessful RA Update. >=SG3 1Day/24h/30 min SGSN Report\RA Updates\Unsuccessful\RA Updates Vector\Counter Counts all unsuccessful RA Update for each RA Update type. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Error Cause Vector\Counter Counts all successful/unsuccessful PDP Context Activations for each Error Cause code. >=SG3 1Day/24h/30 min Counts how many times a certain SGSN Report\RA Updates\Unsucprogram block has set a certain cessful\RA Updates Vector\Error Cause Vector\Set Prb Vector\Counter error cause. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Unsuccessful\Cell Vector\ Counter Counts all unsuccessful PDP Context Activations for each Cell. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Cell Vector\Counter Counts all successful/unsuccessful PDP Context Activations for each Cell. >=SG3 1Day/24h/30 min SGSN Report\RA Updates\Unsuccessful\Error Cause Vector\Set Prb Vector\Counter Counts how many times a certain program block has set a certain error cause. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Successful\Counter Counts all successful PDP context activations >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Successful\Network Operators Successful Vector\Counter Counts the number of successful PDP Context Activations for each operator. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\Network Operators Attempted Vector\Mobile Phone Existence\ Mobile Phone Vector\Counter Counts the number of mobile types for each operator.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version CCMA counter Explanation SGSN Report\PDP Context Activations\Mobile Type Vector\Counter Counts all successful/unsuccess. >=SG3 1Day/24h/30 min Table 3 TimeClass Counters of CCMA time classes (Cont.>=SG3 ful PDP Context Activations for each Mobile phone type for each Error Cause code. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Unsuccessful\Network Operators Unsuccessful Vector\Counter Counts the number of unsuccess. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\Unsuccessful\Physical PAPU Vector\Counter Counts all unsuccessful PDP Context Activations for each physical PAPU. 1Day/24h/30 min SGSN Report\PDP Context Activations\Network Operators Attempted Vector\Counter Counts the number of attaches attempts for each operator.>=SG3 ful PDP Context Activations for each Mobile phone type. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Unsuccessful\Error Cause Vector\Counter Counts the error causes for all unsuccessful PDP Context Activations cumulatively. 1Day/24h/30 min SGSN Report\PDP Context Activations\Mobile Type Vector\Error Cause Vector\Counter Counts all successful/unsuccess. 1Day/24h/30 min SGSN Report\PDP Context Activations\Unsuccessful\Network Operators Unsuccessful Vector\Error Cause Vector\Counter Counts the number of error causes of the unsuccessful attaches for each operator. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Network Operators Attempted Vector\Mobile Phone Existence\ Mobile Phone Vector\Error Cause Vector\Counter Counts the number of error causes of the mobile types for a certain operator. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Network Operators Attempted Vector\Mobile Phone Existence\ Counter Mobile Phones Counts the number of all mobile types for each operator >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Unsuccessful\Logical PAPU Vector\Counter Counts all unsuccessful PDP Context Activations for each logical PAPU. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Unsuccessful\Error Cause Vector\Set Prb Vector\Counter Counts how many times a certain program block has set a certain error cause.>=SG3 ful PDP Context Activations for each operator.) DN05148836 Issue 2-2 Id:0900d805809551ce 43 . >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\APN address filled\APN Vector\ Cell Vector\Error Cause Vector\ Counter Counts all PDP context activations error causes for each APN for each cell >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\Logical PAPU Vector\Error Cause Vector\Counter Counts the number of error causes for each Logical PAPU. >=SG3 1Day/24h/30 min Counts how many times a certain SGSN Report\PDP Context Activations\Unsuccessful\PDP Context Acti.) Id:0900d805809551ce DN05148836 Issue 2-2 .Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version CCMA counter Explanation SGSN Report\PDP Context Activations\Unsuccessful\Error Cause Vector\Set Prb Vector\Internal Sit Vector\Counter Counts how many times a certain internal situation has occurred in a certain program block. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Unsuccessful\PDP Context Activation Vector\Error Cause Vector\ Counter Counts all unsuccessful PDP Context Activations for each PDP Context Activation type cumulatively for each error code.internal situation has occurred in vation Vector\Error Cause Vector\Set a certain program block. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\Logical PAPU Vector\Counter Counts all PDP Context Activations cumulatively for each Logical PAPU. Prb Vector\Internal Sit Vector\Counter >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Physical PAPU Vector\Counter Counts all PDP Context Activations cumulatively for each Physical PAPU. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\APN address filled\APN Vector\ Cell Vector\Counter Counts all PDP context activations for each APN for each cell. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Physical PAPU Vector\Error Cause Vector\Counter Counts the number of error causes for each Physical PAPU. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\Physical PAPU Vector\Unsuccessful\Counter Unsuccessful Counts all unsuccessful PDP Context Activations for physical PAPU. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Unsuccessful\PDP Context Activation Vector\Error Cause Vector\Set Prb Vector\Counter Counts how many times a certain program block has set a certain error cause. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Unsuccessful\PDP Context Activations Vector\Counter Counts all unsuccessful PDP Context Activations for each PDP Context Activation type. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Physical PAPU Vector\PAPU Capacity Vector\Counter Counts the subscriber capacity for each physical PAPU. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Logical PAPU Vector\PAPU Capacity Vector\Counter Counts the subscriber capacity for each physical PAPU. >=SG4 1Day/24h/30 min Table 3 44 TimeClass Counters of CCMA time classes (Cont. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\PAPU Group Vector\Counter Counts all PDP Context Activations cumulatively for each PAPU group. >=SG4 1Day/24h/30 min Counts how many times a certain SGSN Report\PDP Context Activaprogram block has set a certain tions\Roaming Status\Error Cause Vector\Program Block Vector\Counter error cause. >=SG4 1Day/24h/30 min Counts all successful/unsuccessSGSN Report\PDP Context Activations\APN address filled \APN Vector\ ful PDP Context Activations for each APN for each Mobile phone Mobile Type Vector\Counter type. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\APN address filled\APN Vector\ Charging Info Vector\Counter Counts the PDP Context Activations for each APN for a each charging class. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\APN address filled\Counter SGSN Report\PDP Context Activations\APN address filled\ Counter >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\APN address filled\APN Vector\ Counter Counts all PDP Context Activations cumulatively for each APN. >=SG4 1Day/24h/30 min >=SG3 Counts the number of PDP SGSN Report\PDP Context Activations\Roaming Status\Network Opera. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\APN address filled\APN Vector\ Error Cause Vector\Counter Counts the number of error causes for each APN. tors Attempted Vector\counter 1Day/24h/30 min SGSN Report\PDP Context Activations\Roaming Status\Error Cause Vector\Program Block Vector\Internal Situation Vector\Counter Table 3 TimeClass Counters of CCMA time classes (Cont. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\PAPU Group Vector\PAPU Capacity Vector\Counter Counts the subscriber capacity for each PAPU groups.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version CCMA counter Explanation SGSN Report\PDP Context Activations\Logical PAPU Vector\Unsuccessful\Counter Unsuccessful Counts all unsuccessful PDP Context Activations for logical PAPU. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\Roaming Status\Counter Counts all roaming PDP Context Activations. >=SG4 1Day/24h/30 min Counts how many times a certain internal situation has occurred in a certain program block. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\PAPU Group Vector\Error Cause Vector\Counter Counts the number of error causes for each PAPU group. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\Roaming Status\Error Cause Vector\Counter Counts all successful/unsuccessful roaming PDP Context Activations for each Error cause code.) DN05148836 Issue 2-2 Id:0900d805809551ce 45 .Context Activations for each operator. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 1\Cell Vector\Counter Counts all PDP context activations for each cell for the specific TREC >=SG4 1Day/24h/30 min Counts the number of mobile SGSN Report\PDP Context Activations\Roaming Status\Network Opera. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 0\Cell Vector\Counter Counts the number of PDP Context activations for each Cell for the specific TREC. >=SG3 1Day/24h/30 min Counts the number of successful SGSN Report\PDP Context ActivaPDP Context Activations for each tions\Roaming Status\Successful\ Network Operators Successful Vector\ operator. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\Roaming Status\Unsuccessful\ Error Cause Vector\Counter Counts all unsuccessful roaming PDP Context Activations for each Error cause code. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\Roaming Status\Unsuccessful\ Network Operators Unsuccessful Vector\counter Counts the number of unsuccess.types for each operator for roamers. counter >=SG3 1Day/24h/30 min SGSN Report\PDP Context Activations\Roaming Status\Unsuccessful\ Counter Counts all unsuccessful roaming PDP Context Activations.) Id:0900d805809551ce DN05148836 Issue 2-2 . 1Day/24h/30 min SGSN Report\PDP Context Activations\Charging Info Vector\Counter Counts the PDP Context Activations for a each charging class.Real-time monitoring CCMA counter Traffica Reference Guide for SGSN Direct Interface Explanation SGSN Version TimeClass >=SG3 1Day/24h/30 min Counts the number of error causes of unsuccessful PDP Context Activations for each mobile type for a given operator.>=SG3 ful PDP Context Activations for each operator. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\Roaming Status\Unsuccessful\ Error Cause Vector\Mobile Type Vector\Counter Counts how many times a certain program block has set a certain error cause. 1Day/24h/30 min SGSN Report\PDP Context Activations\Roaming Status\Unsuccessful\ Network Operators Unsuccessful Vector\Error Cause Vector\counter >=SG3 Counts the number of error causes of the unsuccessful PDP Context Activations for each operator. tors Attempted Vector\Mobile Phone Existence\Mobile Phone Vector\ counter SGSN Report\PDP Context Activations\Roaming Status\Network Operators Attempted Vector\Mobile Phone Existence\Mobile Phone Vector\Error Cause Vector\counter Table 3 46 Counters of CCMA time classes (Cont. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\Charging Info Vector\APN Name Vector\Counter Counts the PDP Context Activations for a each charging class for each APN. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 0\Cell Vector\Error Cause Vector\Counter Counts specific TRECattaches for each Cell for each Error cause code. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 2\Cell Vector\Counter Counts the number of PDP Context activations for each Cell for the specific TREC. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 2\Cell Vector\Error Cause Vector\Counter Counts the number of PDP Context activations for each Cell for the specific TREC. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 7\Cell Vector\Counter Counts the number of PDP Context activations for each Cell for the specific TREC. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 6\Cell Vector\Counte Counts the number of PDP Context activations for each Cell for the specific TREC. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 5\Cell Vector\Error Cause Vector\Counter Counts specific TREC attaches for each Cell for each Error cause code.) DN05148836 Issue 2-2 Id:0900d805809551ce 47 . >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 6\Cell Vector\Error Cause Vector\Counter Counts specific TREC attaches for each Cell for each Error cause code. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 5\Cell Vector\Counter Counts the number of PDP Context activations for each Cell for the specific TREC. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 7\Cell Vector\Error Cause Vector\Counter Counts specific TREC attaches for each Cell for each Error cause code.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version CCMA counter Explanation SGSN Report\PDP Context Activations\TREC 1\Cell Vector\Error Cause Vector\Counter Counts specific TREC attaches for each Cell for each Error cause code. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 8\Cell Vector\Error Cause Vector\Counter Counts specific TREC attaches for each Cell for each Error cause code. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 8\Cell Vector\Counter Counts the number of PDP Context activations for each Cell for the specific TREC. >=SG4 1Day/24h/30 min Table 3 TimeClass Counters of CCMA time classes (Cont. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 4\Cell Vector\Error Cause Vector\Counter Counts specific TREC attaches for each Cell for each Error cause code. >=SG4 1Day/24h/30 min >=SG4 SGSN Report\PDP Context Activations\TREC 3\Cell Vector\Counter Counts all PDP context activations for each cell for the specific TREC 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 3\Cell Vector\Error Cause Vector\Counter Counts specific TREC attaches for each Cell for each Error cause code. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 4\Cell Vector\Counter Counts the number of PDP Context activations for each Cell for the specific TREC. >=SG3 ful PDP Context Modifications for each Error Cause code. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Modifications\Unsuccessful\PDP Context Modification Vector\Error Cause Vector\Set Prb Vector\Counter Counts how many times a certain program block has set a certain error cause. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Modifications\Unsuccessful\Cell Vector\ Counter Counts all unsuccessful PDP Context Modifications for each Cell.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version CCMA counter Explanation SGSN Report\PDP Context Activations\TREC 9\Cell Vector\Counter Counts the number of PDP Context activations for each Cell for the specific TREC. 1Day/24h/30 min SGSN Report\PDP Context Modifications\Cell Vector\Error Cause Vector\ Counter Counts all successful/unsuccessful PDP Context Modifications for each Cell for each Error Cause code. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Modifications\Unsuccessful\Counter Counts all unsuccessful PDP Context Modifications. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Modifications\Unsuccessful\PDP Context Modification Vector\Counter Counts all unsuccessful PDP Context Modifications for each PDP Context Modification type. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Modifications\Unsuccessful\Error Cause Vector\Counter Counts all unsuccessful PDP Context Modifications cumulatively for each error code. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Modifications\Counter Counts all successful/unsuccessful PDP Context Modifications. 1Day/24h/30 min SGSN Report\PDP Context Modifications\Cell Vector\Counter Counts all PDP Context Modifica.) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG3 1Day/24h/30 min SGSN Report\PDP Context Modifications\Unsuccessful\Cell Vector\Error Cause Vector\Counter Counts all unsuccessful PDP Context Modifications for each Cell for each Error Cause code. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Modifications\Unsuccessful\PDP Context Modification Vector\Error Cause Vector\Counter Counts all unsuccessful PDP Context Modifications for each PDP Context Modification type cumulatively for each error code.>=SG3 tions for each Cell. >=SG3 1Day/24h/30 min Table 3 48 TimeClass Counters of CCMA time classes (Cont. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Modifications\Unsuccessful\Error Cause Vector\Set Prb Vector\Internal Sit Vector\Counter Counts how many times a certain internal situation has occurred in a certain program block. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Modifications\Error Cause Vector\Counter Counts all successful/unsuccess. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Activations\TREC 9\Cell Vector\Error Cause Vector\Counter Counts specific TREC attaches for each Cell for each Error cause code. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Modifications\Unsuccessful\Error Cause Vector\Set Prb Vector\Counter Counts how many times a certain program block has set a certain error cause. >=SG3 tions\Error Cause Vector\Counter ful PDP Context Deactivations for each Error Cause code. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Modifications\Roaming Status\Error Cause Vector \Program Block Vector\Internal Situation Vector\Counter Counts how many times a certain internal situation has occurred in a certain program block. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Deactiva.) DN05148836 Issue 2-2 Id:0900d805809551ce 49 .Counts the data volume downlinks for each charging class. 1Day/24h/30 min SGSN Report\PDP Context Deactiva.Counts all successful/unsuccesstions\Counter ful PDP Context Deactivations.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version CCMA counter Explanation TimeClass SGSN Report\PDP Context Modifications\Unsuccessful\PDP Context Modification Vector\Error Cause Vector\Set Prb Vector\nternal Sit Vector\Counter Counts how many times a certain internal situation has occurred in a certain program block.Counts all unsuccessful PDP tions\Unsuccessful\Counter Context Deactivations.Counts all unsuccessful PDP Context Deactivations for each tions\Unsuccessful\Cell Vector\ Cell. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Deactiva. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Deactiva.Counts all successful/unsuccesstions\Cell Vector\Counter ful PDP Context Deactivations for each Cell. tions\Charging Info Vector\Data Volume Uplink\sum >=SG4 1Day/24h/30 min SGSN Report\PDP Context Deactiva.Counts all unsuccessful PDP Context Deactivations for each tions\Unsuccessful\Cell Vector\Error Cell for each Error Cause code. 1Day/24h/30 min SGSN Report\PDP Context Deactiva. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Deactiva. >=SG3 1Day/24h/30 min SGSN Report\PDP Context Modifications\Roaming Status\Counter Counts all roaming PDP Context Modifications. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Modifica. Counter >=SG3 1Day/24h/30 min SGSN Report\PDP Context Deactiva. tions\Charging Info Vector\Data Volume Downlink\Sum >=SG4 1Day/24h/30 min Table 3 Counters of CCMA time classes (Cont.Counts the data volume uplinks for each charging class. Cause Vector\Counter >=SG3 1Day/24h/30 min SGSN Report\PDP Context Deactiva.Counts all successful/unsuccess. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Modifications\Roaming Status\Error Cause Vector\Counter Counts all successful/unsuccessful roaming PDP Context Modifications for each Error cause code.Counts how many times a certain program block has set a certain tions\Roaming Status\Error Cause Vector\Program Block Vector\Counter error cause. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Modifications\Roaming Status\Unsuccessful\ Counter Counts all unsuccessful roaming >=SG4 PDP Context Modifications cumulatively for the time period.Counts all successful/unsuccesstions\Cell Vector\Error Cause Vector\ ful PDP Context Deactivations for each Cell for each Error Cause Counter code. >=SG3 1Day/24h/30 min SGSN Report\SMS Deliveries Vector\ Unsuccessful\SMS Delivery Vector\ Error Cause Vector\Counter Counts all unsuccessful SMS Deliveries for each SMS Deliveries MO/MT type cumulatively for each error code. >=SG3 1Day/24h/30 min SGSN Report\SMS Deliveries Vector\ Unsuccessful\SMS Delivery Vector\ Counter Counts all unsuccessful SMS Deliveries for each SMS Deliveries MO/MT type. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Deactivations\APN Vector\Mobile Types\Data Volume Downlink\Sum Counts the data volume downlinks for each mobile type for each APN. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Deactivations\APN Vector\Charging Info\Data Volume Uplink\sum Counts the data volume uplinks for each charging class for each APN. >=SG3 1Day/24h/30 min SGSN Report\SMS Deliveries Vector\ Unsuccessful\SMS Delivery Vector\ Error Cause Vector\Set Prb Vector\ Counter Counts how many times a certain program block has set a certain error cause. >=SG3 1Day/24h/30 min Table 3 50 TimeClass Counters of CCMA time classes (Cont. >=SG3 1Day/24h/30 min SGSN Report\SMS Deliveries\Unsuccessful\Error Cause Vector\Counter Counts all unsuccessful SMS Deliveries cumulatively for each error code. >=SG3 1Day/24h/30 min SGSN Report\SMS Deliveries\Unsuccessful\Error Cause Vector\Set Prb Vector\Internal Sit Vector\Counter Counts how many times a certain internal situation has occurred in a certain program block. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Deactivations\APN Vector \Charging Info\Data Volume Downlink\Sum Counts the data volume downlinks for each charging class for each APN. >=SG4 1Day/24h/30 min SGSN Report\MO SMS Deliveries\ Charging Info Vector\Counter Counts the MO SMS Deliveries for each charging class. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Deactivations\APN Vector\Mobile Types\Data Volume Uplink\sum Counts the data volume uplinks for each mobile types for each APN. >=SG4 1Day/24h/30 min SGSN Report\SMS Deliveries\ Counter Counts all successful/unsuccessful SMS deliveries >=SG3 1Day/24h/30 min SGSN Report\SMS Deliveries\Unsuccessful\Counter Counts all unsuccessful SMS.) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG3 1Day/24h/30 min SGSN Report\SMS Deliveries\Unsuccessful\Error Cause Vector\Set Prb Vector\Counter Counts how many times a certain program block has set a certain error cause. >=SG4 1Day/24h/30 min SGSN Report\PDP Context Deactivations\APN Vector \Data Volume Downlink\Sum Counts the data volume downlinks for each APN.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version CCMA counter Explanation SGSN Report\PDP Context Deactivations\APN Vector\Data Volume Uplink\sum Counts the data volume uplinks for each APN. >=SG3 1Day/24h/30 min SGSN Report\MT SMS Deliveries\ Counter Counts all successful/unsuccessful MT-SMS deliveries. 1Day/24h/30 min SGSN Report\MO SMS Deliveries\ Unsuccessful\Counter Counts all unsuccessful MO-SMS deliveries.) DN05148836 Issue 2-2 Id:0900d805809551ce 51 . >=SG3 1Day/24h/30 min SGSN Report\MO SMS Deliveries\ Cell Vector\Error Cause Vector\ Counter Counts all successful/unsuccessful MO-SMS deliveries for each Cell for each Error Cause code.>=SG3 ful MO-SMS deliveries cumulatively for the time period. >=SG3 1Day/24h/30 min SGSN Report\MT SMS Deliveries\Cell Vector\Counter Counts all successful/unsuccessful MT-SMS deliveries for each Cell. >=SG3 1Day/24h/30 min SGSN Report\MT SMS Deliveries\ Unsuccessful\Cell Vector\Error Cause Vector\Counter Counts all unsuccessful MT-SMS deliveries for each Cell for each Error Cause code. Error Cause Vector\Set Prb Vector\ Internal Sit Vector\Counter Counts all data sent uplink for SGSN Report\Uplink Data Volume Available\APN Presence\APN Vector\ each APN. >=SG3 1Day/24h/30 min SGSN Report\MT SMS Deliveries\ Unsuccessful\Counter Counts all unsuccessful MT-SMS deliveries. >=SG3 1Day/24h/30 min SGSN Report\MO SMS Deliveries\ Unsuccessful\Cell Vector\Counter Counts all unsuccessful MOSMS deliveries for each Cell. >=SG3 1Day/24h/30 min SGSN Report\+MO SMS Deliveries\ Unsuccessful\Cell Vector\Error Cause Vector\Counter Counts all unsuccessful MOSMS deliveries for each Cell for each Error Cause code.Traffica Reference Guide for SGSN Direct Interface CCMA counter Real-time monitoring SGSN Version Explanation TimeClass >=SG3 1Day/24h/30 min SGSN Report\MO SMS Deliveries\ Counter Counts all successful/unsuccess. >=SG3 1Day/24h/30 min >=SG4 1Day/24h/30 min SGSN Report\SMS Deliveries Vector\ Counts how many times a certain internal situation has occurred in Unsuccessful\SMS Delivery Vector\ a certain program block. >=SG3 1Day/24h/30 min SGSN Report\MT SMS Deliveries\Cell Vector\Error Cause Vector\Counter Counts all successful/unsuccessful MT-SMS deliveries for each Cell for each Error Cause code cumulatively for the time period. >=SG3 1Day/24h/30 min SGSN Report\MT SMS Deliveries\ Error Cause Vector\Counter Counts all successful/unsuccessful MT-SMS deliveries for each Error Cause code. >=SG3 1Day/24h/30 min SGSN Report\MO SMS Deliveries\ Error Cause Vector\Counter Counts all successful/unsuccessful MO-SMS deliveries for each Error Cause code. Uplink Data Volume Addition\Sum Table 3 Counters of CCMA time classes (Cont. >=SG3 1Day/24h/30 min SGSN Report\MO SMS Deliveries\ Cell Vector\Counter Counts all successful/unsuccessful MO-SMS deliveries for each Cell. >=SG3 1Day/24h/30 min SGSN Report\MT SMS Deliveries\ Unsuccessful\Cell Vector\Counter Counts all unsuccessful MT-SMS deliveries for each Cell. >=SG4 1Day/24h/30 min SGSN Report\Data Volume Available\ Counts all data sent cumulatively Counter for the time period >=SG4 1Day/24h/30 min SGSN Report\Data Volume Available\ Counts the data volume uplink for LAC Vector\Uplink Data Volume\Sum each LAC. LAC Vector\ RAC Vector\Downlink Data Volume\Sum RAC Downlink >=SG4 1Day/24h/30 min SGSN Report\Data Volume Available\ Counts the data volume uplink for each cell. LAC Vector\RAC Vector\Cell Vector\ Downlink Data Volume\Sum Cell Downlink >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release 9798\Delay Class Presence\Counter Counts the number of negotiated updates for all delay classes >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release 9798\Requested Delay Class Presence\Counter Counts the number of negotiated updates for a specific requested delay class >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release 9798\Delay Class Presence\Delay Class 1\Counter Counts the number of negotiated updates for a specific delay class >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release9798\Delay Class Presence\Delay Class 1\Delay Class Successful Request\Counter Counts the number of successful requests for a specific delay class. Downlink Data Volume Addition\Sum >=SG4 1Day/24h/30 min Counts all data sent downlink for each charging class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release 9798\Delay Class Presence\Delay Class 2\Counter Counts the number of negotiated updates for a specific delay class >=SG4 1Day/24h/30 min SGSN Report\Downlink Data Volume Available\Charging Info Vector\ Downlink Data Volume\Sum Table 3 52 Counters of CCMA time classes (Cont. SGSN Version TimeClass >=SG4 1Day/24h/30 min SGSN Report\Downlink Data Volume Counts all data sent downlink for Available\APN Presence\APN Vector\ each APN.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface CCMA counter Explanation SGSN Report\Uplink Data Volume Available\Charging Info Vector\Uplink Data Volume\Sum Counts all data sent uplink for each charging class. LAC Vector\RAC Vector\Uplink Data Volume\Sum RAC Uplink >=SG4 1Day/24h/30 min SGSN Report\Data Volume Available\ Counts the data volume downlink for each RAC. LAC Uplink >=SG4 1Day/24h/30 min SGSN Report\Data Volume Available\ Counts the data volume downlink for each LAC.) Id:0900d805809551ce DN05148836 Issue 2-2 . LAC Vector\RAC Vector\Cell Vector\ Uplink Data Volume\Sum Cell Uplink >=SG4 1Day/24h/30 min SGSN Report\Data Volume Available\ Counts the data volume downlink for each cell. LAC Vector\Downlink Data Volume\ Sum LAC Downlink >=SG4 1Day/24h/30 min SGSN Report\Data Volume Available\ Counts the data volume uplink for each RAC. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release9798\Negotiated Delay Class Presence\Negotiated Delay Class 1\Counter Counts the number of negotiations for a specific delay class. >=SG4 1Day/24h/30 min Table 3 TimeClass Counters of CCMA time classes (Cont. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release 9798\Delay Class Presence\Delay Class 4\Counter Counts the number of negotiated updates for a specific delay class >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release9798\Delay Class Presence\Delay Class 4\Delay Class Successful Request\Counter Counts the number of successful requests for a specific delay class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release9798\Requested Delay Class Presence\Requested Delay Class 4\Counter Counts the number of requests for a specific delay class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release 9798\Negotiated Delay Class Presence\Counter Counts the number of negotiated updates for a specific negotiated delay class >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release9798\Requested Delay Class Presence\Requested Delay Class 1\Counter Counts the number of requests for a specific delay class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release 9798\Delay Class Presence\Delay Class 3\Counter Counts the number of negotiated updates for a specific delay class >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release9798\Delay Class Presence\Delay Class 3\Delay Class Successful Request\Counter Counts the number of successful requests for a specific delay class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release9798\Requested Delay Class Presence\Requested Delay Class 3\Counter Counts the number of requests for a specific delay class.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version CCMA counter Explanation SGSN Report\QoS Negotiated Update\Release9798\Delay Class Presence\Delay Class 2\Delay Class Successful Request\Counter Counts the number of successful requests for a specific delay class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release9798\Negotiated Delay Class Presence\Negotiated Delay Class 1\Data Volume Addition\ Sum Counts the data volume sent uplink and downlink for a specific delay class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release9798\Requested Delay Class Presence\Requested Delay Class 2\Counter Counts the number of requests for a specific delay class.) DN05148836 Issue 2-2 Id:0900d805809551ce 53 . >=SG4 1Day/24h/30 min Table 3 54 TimeClass Counters of CCMA time classes (Cont. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release9798\Negotiated Delay Class Presence\Negotiated Delay Class 4\Counter Counts the number of negotiations for a specific delay class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release99\Traffic Class Presence\Traffic Class 1\Traffic Class Successful Request\Counter Counts the number of successful requests for a specific traffic class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release9798\Negotiated Delay Class Presence\Negotiated Delay Class 4\Data Volume Addition\ Sum Counts the data volume sent uplink and downlink for a specific delay class.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version CCMA counter Explanation SGSN Report\QoS Negotiated Update\Release9798\Negotiated Delay Class Presence\Negotiated Delay Class 2\Counter Counts the number of negotiations for a specific delay class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release9798\Negotiated Delay Class Presence\Negotiated Delay Class 3\Counter Counts the number of negotiations for a specific delay class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release 99\Traffic Class Presence\Counter Counts the number of negotiated updates for all traffic classes >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release 99\Traffic Class Presence\Traffic Class 1\Counter Counts the number of negotiated updates for a specific traffic class >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release 99\Traffic Class Presence\Traffic Class 2\Counter Counts the number of negotiated updates for a specific traffic class >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release 99\Traffic Class Presence\Traffic Class 3\Counter Counts the number of negotiated updates for a specific traffic class >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release 99\Traffic Class Presence\Traffic Class 4\Counter Counts the number of negotiated updates for a specific traffic class >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release9798\Negotiated Delay Class Presence\Negotiated Delay Class 3\Data Volume Addition\ Sum Counts the data volume sent uplink and downlink for a specific delay class.) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release9798\Negotiated Delay Class Presence\Negotiated Delay Class 2\Data Volume Addition\ Sum Counts the data volume sent uplink and downlink for a specific delay class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release 99\Requested Traffic Class Presence\Counter Counts the number of negotiated updates for a specific requested traffic class >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release99\Requested Traffic Class Presence\Requested Traffic Class 1\Counter Counts the number of requests for a specific traffic class.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version CCMA counter Explanation SGSN Report\QoS Negotiated Update\Release99\Traffic Class Presence\Traffic Class 2\Traffic Class Successful Request\Counter Counts the number of successful requests for a specific traffic class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release99\Requested Traffic Class Presence\Requested Traffic Class 3\Counter Counts the number of requests for a specific traffic class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release99\Negotiated Traffic Class Presence\Negotiated Traffic Class 1\Data Volume Addition\Sum Counts the data volume sent uplink and downlink for a specific delay class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release99\Traffic Class Presence\Traffic Class 3\Traffic Class Successful Request\Counter Counts the number of successful requests for a specific traffic class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release99\Requested Traffic Class Presence\Requested Traffic Class 4\Counter Counts the number of requests for a specific traffic class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release99\Negotiated Traffic Class Presence\Negotiated Traffic Class 2\Counter Counts the number of negotiations for a specific traffic class.) DN05148836 Issue 2-2 Id:0900d805809551ce 55 . >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release 99\Negotiated Traffic Class Presence\Counter Counts the number of negotiated updates for all negotiated traffic class >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release99\Negotiated Traffic Class Presence\Negotiated Traffic Class 1\Counter Counts the number of negotiations for a specific traffic class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release99\Traffic Class Presence\Traffic Class 4\Traffic Class Successful Request\Counter Counts the number of successful requests for a specific traffic class. >=SG4 1Day/24h/30 min Table 3 TimeClass Counters of CCMA time classes (Cont. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release99\Requested Traffic Class Presence\Requested Traffic Class 2\Counter Counts the number of requests for a specific traffic class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release99\Negotiated Traffic Class Presence\Negotiated Traffic Class 3\Counter Counts the number of negotiations for a specific traffic class. >=SG4 1Day/24h/30 min SGSN Report\PS External Cause Vector\LAC Vector\Counter Counts all PS external causes for each LAC cumulatively for the time period. >=SG4 1Day/24h/30 min SGSN Report\S External Cause Vector\Cause Proc Vector\Error Cause Vector\Program Block Vector\ Counter Counts how many times a certain program block has set a certain error cause. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release99\Negotiated Traffic Class Presence\Negotiated Traffic Class 4\Counter Counts the number of negotiations for a specific traffic class.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version CCMA counter Explanation SGSN Report\QoS Negotiated Update\Release99\Negotiated Traffic Class Presence \Negotiated Traffic Class 2\Data Volume Addition\Sum Counts the data volume sent uplink and downlink for a specific delay class. >=SG4 1Day/24h/30 min SGSN Report\PS External Cause Vector\LAC Vector \RAC Vector\Error Cause Vector\Counter Counts all PS external causes for each RAC of a specific LAC for each Error Cause cumulatively for the time period. >=SG4 1Day/24h/30 min SGSN Report\PS External Cause Vector\Cause Proc Vector\Counter Counts all PS external causes for each cause proc >=SG4 1Day/24h/30 min SGSN Report\PS External Cause Vector\Cause Proc Vector\Error Cause Vector\Counter Counts how many times each error cause code has occurred in a each service request.) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG4 1Day/24h/30 min SGSN Report\PS External Cause Vector\Logical PAPU Vector\Counter Counts all PS external causes for each logical PAPU >=SG4 1Day/24h/30 min Table 3 56 TimeClass Counters of CCMA time classes (Cont. >=SG4 1Day/24h/30 min SGSN Report\PS External Cause Vector\LAC Vector\RAC Vector\ Counter Counts all PS external causes for each RAC under a specific LAC cumulatively for the time period. >=SG4 1Day/24h/30 min SGSN Report\PS External Cause Vector\Counter Counts PS External Causes cumulatively for the time period. >=SG4 1Day/24h/30 min SGSN Report\PS External Cause Vector\Cause Proc Vector\Error Cause Vector\Program Block Vector\ Internal Situation Vector\Counter Counts how many times a certain internal situation has occurred in a certain program block. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release99\Negotiated Traffic Class Presence\Negotiated Traffic Class 4\Data Volume Addition\Sum Counts the data volume sent uplink and downlink for a specific delay class. >=SG4 1Day/24h/30 min SGSN Report\QoS Negotiated Update\Release99\Negotiated Traffic Class Presence\Negotiated Traffic Class 3\Data Volume Addition\Sum Counts the data volume sent uplink and downlink for a specific delay class. Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version CCMA counter Explanation SGSN Report\PS External Cause Vector\Logical PAPU Vector\Error Cause Vector\Counter Counts all PS external causes for each logical PAPU for each error cause >=SG4 1Day/24h/30 min SGSN Report\PS External Cause Counts all PS external causes for Vector\Physical PAPU Vector\Counter each physical PAPU >=SG4 1Day/24h/30 min SGSN Report\PS External Cause Vector\Physical PAPU Vector\Error Cause Vector\Counter Counts all PS external causes for each physical PAPU for each error cause >=SG4 1Day/24h/30 min SGSN Report\CS External Cause Vector\Cause Proc Vector\Counter Counts all CS external causes for each cause proc >=SG4 1Day/24h/30 min SGSN Report\CS External Cause Vector\Cause Proc Vector\Error Cause Vector\Counter Counts how many times each error cause code has occurred in a each service request >=SG4 1Day/24h/30 min SGSN Report\CS External Cause Vector\Cause Proc Vector\Error Cause Vector\Program Block Vector\ Counter Counts how many times a certain program block has set a certain error cause >=SG4 1Day/24h/30 min SGSN Report\CS External Cause Vector\Cause Proc Vector\Error Cause Vector\Program Block Vector\ Internal Situation Vector\Counter Counts how many times a certain internal situation has occurred in a certain program block >=SG4 1Day/24h/30 min SGSN Report\CS External Cause Vector\LAC Vector\Counter Counts all CS external causes for each LAC >=SG4 1Day/24h/30 min SGSN Report\CS External Cause Vector\LAC Vector\RAC Vector\Error Cause Vector\Counter Counts all CS external causes for each RAC under specific LAC >=SG4 1Day/24h/30 min SGSN Report\CS External Cause Vector\LAC Vector\RAC Vector\ Counter Counts all CS external causes for each RAC of a specific LAC for each error cause >=SG4 1Day/24h/30 min SGSN Report\CS External Cause Vector\Logical PAPU Vector\Counter Counts all CS external causes for each logical PAPU cumulatively for the time period.) DN05148836 Issue 2-2 Id:0900d805809551ce 57 . >=SG4 1Day/24h/30 min SGSN Report\CS External Cause Vector\Logical PAPU Vector\Error Cause Vector\Counter Counts all CS external causes for each logical PAPU for each error cause >=SG4 1Day/24h/30 min SGSN Report\CS External Cause Counts all CS external causes for Vector\Physical PAPU Vector\Counter each physical PAPU cumulatively for the time period. >=SG4 1Day/24h/30 min SGSN Report\CS External Cause Vector\Physical PAPU Vector\Error Cause Vector\Counter Counts all CS external causes for each physical PAPU for each error cause >=SG4 1Day/24h/30 min SGSN Report\CS External Cause Vector\Counter Counts all CS external causes >=SG4 1Day/24h/30 min SGSN Report\TREC 0\Counter Counts all specific TREC attaches cumulatively for the time period. >=SG4 1Day/24h/30 min Table 3 TimeClass Counters of CCMA time classes (Cont. >=SG4 1Day/24h/30 min SGSN Report\TREC 1\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG4 1Day/24h/30 min Table 3 58 TimeClass Counters of CCMA time classes (Cont. >=SG4 1Day/24h/30 min SGSN Report\TREC 1\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 0\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 0\Error Cause Vector\Counter Counts all specific TREC attaches for each Error cause code. >=SG4 1Day/24h/30 min SGSN Report\TREC 1\Counter Counts all specific TREC attaches cumulatively for the time period. >=SG4 1Day/24h/30 min SGSN Report\TREC 1\Error Cause Vector\Counter Counts all specific TREC attaches for each Error cause code. >=SG4 1Day/24h/30 min SGSN Report\TREC 0\PDP Context Activation\APN Vector\Counter Counts all PDP Context Activations cumulatively for each APN.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version CCMA counter Explanation SGSN Report\TREC 0\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 2\PDP Context Activation\APN Vector\Counter Counts all PDP Context Activations cumulatively for each APN. >=SG4 1Day/24h/30 min SGSN Report\TREC 2\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 3\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC.) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG4 1Day/24h/30 min SGSN Report\TREC 3\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 3\Counter Counts all specific TREC attaches cumulatively for the time period. >=SG4 1Day/24h/30 min SGSN Report\TREC 2\Error Cause Vector\Counter Counts all specific TREC attaches for each Error cause code cumulatively for the time period. >=SG4 1Day/24h/30 min SGSN Report / TREC 0 / PDP Context Activation / Counter Counts all PDP Context Activations for specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 2\Counter Counts all specific TREC attaches. >=SG4 1Day/24h/30 min SGSN Report\REC 1\PDP Context Activation\APN Vector\Counter Counts all PDP Context Activations cumulatively for each APN. >=SG4 1Day/24h/30 min SGSN Report\TREC 3\Error Cause Vector\Counter Counts all specific TREC attaches for each Error cause code cumulatively for the time period. >=SG4 1Day/24h/30 min SGSN Report\TREC 2\PDP Context Activation\Counter Counts all PDP Context Activations for specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 2\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 1\PDP Context Activation\Counter Counts all PDP Context Activations for specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 4\PDP Context Activation\Counter Counts all PDP Context Activations for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 5\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 6\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC.) DN05148836 Issue 2-2 Id:0900d805809551ce 59 . >=SG4 1Day/24h/30 min SGSN Report\TREC 4\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 4\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 5\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 6\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 4\Counter Counts all specific TREC attaches cumulatively for the time period. >=SG4 1Day/24h/30 min SGSN Report\TREC 5\ Error Cause Vector\Counter Counts all specific TREC attaches for each Error cause code cumulatively for the time period. >=SG4 1Day/24h/30 min SGSN Report\TREC 5\Counter Counts all specific TREC attaches. >=SG4 1Day/24h/30 min SGSN Report\TREC 6\PDP Context Activation\APN Vector\Counter Counts all PDP Context Activations cumulatively for each APN. >=SG4 1Day/24h/30 min SGSN Report\TREC 5\PDP Context Activation\APN Vector\Counter Counts all PDP Context Activations cumulatively for each APN. >=SG4 1Day/24h/30 min SGSN Report\TREC 7\Counter Counts all specific TREC attaches cumulatively for the time period >=SG4 1Day/24h/30 min Table 3 TimeClass Counters of CCMA time classes (Cont. >=SG4 1Day/24h/30 min SGSN Report\TREC 4\Error Cause Vector\Counter Counts all specific TREC attaches for each Error cause code. >=SG4 1Day/24h/30 min SGSN Report\TREC 4\PDP Context Activation\APN Vector\Counter Counts all PDP Context Activations cumulatively for each APN. >=SG4 1Day/24h/30 min SGSN Report\TREC 6\PDP Context Activation\Counter Counts all PDP Context Activations for a specific TREC.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version CCMA counter Explanation SGSN Report\TREC 3\PDP Context Activation\Counter Counts all PDP Context Activations for specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 5\PDP Context Activation\Counter Counts all PDP Context Activations for specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 3\PDP Context Activation\APN Vector\Counter Counts all PDP Context Activations cumulatively for each APN. >=SG4 1Day/24h/30 min SGSN Report\TREC 6\Counter Counts all specific TREC attaches. >=SG4 1Day/24h/30 min SGSN Report\TREC 6\Error Cause Vector\Counter Counts all specific TREC attaches for each Error cause code. >=SG4 1Day/24h/30 min SGSN Report\TREC 7\PDP Context Activation\Counter Counts all PDP Context Activations for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 9\Error Cause Vector\Counter Counts all specific TREC attaches for each Error cause code. >=SG4 1Day/24h/30 min SGSN Report\TREC 9\Counter Counts all specific TREC attaches. >=SG4 1Day/24h/30 min SGSN Report\TREC 7\Error Cause Vector\Counter Counts all specific TREC attaches for each Error cause code cumulatively for the time period. >=SG4 1Day/24h/30 min SGSN Report\TREC 8\Counter Counts all specific TREC attaches cumulatively for the time period. >=SG4 1Day/24h/30 min Bssgp Cell Report\Counter Counts the number of Bssgp Cell reports >=SG4 1 Day Bssgp Cell Report\Bssgp Cell Available\LAC/RAC/Cell Presence\LAC Vector\Passed Data\Sum Passed Counts the passed data amount for each LAC >=SG4 1 Day Table 3 60 TimeClass Counters of CCMA time classes (Cont. >=SG4 1Day/24h/30 min SGSN Report\TREC 7\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 8\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 8\Error Cause Vector\Counter Counts all specific TREC attaches for each Error cause code cumulatively for the time period. >=SG4 1Day/24h/30 min SGSN Report\TREC 8\PDP Context Activation\APN Vector\Counter Counts all PDP Context Activations cumulatively for each APN. >=SG4 1Day/24h/30 min SGSN Report\TREC 8\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 8\ PDP Context Activation\Counter Counts all PDP Context Activations for specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 7\PDP Context Activation\APN Vector\Counter Counts all PDP Context Activations cumulatively for each APN. >=SG4 1Day/24h/30 min SGSN Report / TREC 9\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version CCMA counter Explanation SGSN Report\TREC 7\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 9\PDP Context Activation\APN Vector\Counter Counts all PDP Context Activations cumulatively for each APN. >=SG4 1Day/24h/30 min SGSN Report\TREC 9 / Data Volume Up / Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG4 1Day/24h/30 min SGSN Report\TREC 9\PDP Context Activation\Counter Counts all PDP Context Activations for a specific TREC.) Id:0900d805809551ce DN05148836 Issue 2-2 . Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version TimeClass >=SG4 1 Day Bssgp Cell Report\Bssgp Cell Available\LAC/RAC/Cell Presence\LAC Vector\RAC Vector\Passed Data\Sum Passed Counts the passed data amount >=SG6 for each RAC under a certain LAC 1 Day Bssgp Cell Report\Bssgp Cell Available\LAC/RAC/Cell Presence\LAC Vector\RAC Vector\Discarded Packets\Sum Discarded Counts the number of discarded packets for each RAC under a certain LAC >=SG6 1 Day Bssgp Cell Report\Bssgp Cell Available\LAC/RAC/Cell Presence\LAC Vector\RAC Vector\Cell Vector\ Passed Data\Sum Passed Counts the passed data amount for each cell for each RAC under certain LAC >=SG4 1 Day Bssgp Cell Report\Bssgp Cell Available\LAC/RAC/Cell Presence\LAC Vector\RAC Vector\Cell Vector\Discarded Packets\Sum Discarded Counts the number of discarded packets for each cell for each RAC under certain LAC >=SG4 1 Day Bssgp Cell Report\Bssgp Cell Available\Physical PAPU Vector\Passed Data\Sum Passed Counts the passed data amount for each physical PAPU >=SG4 1 Day Bssgp Cell Report\Bssgp Cell Available\Physical PAPU Vector\Discarded Packets\Sum Discarded Counts the number of discarded packets for each physical PAPU >=SG4 1 Day Bssgp Cell Report\Bssgp Cell Available\LAC/RAC/Cell Presence\LAC Vector\RAC Vector\Cell Id\Cell Id Vector\Counter Counts the data amount for each physical PAPU >=SG4 1Day/24h/30 min Bssgp Cell Report\Bssgp Cell Available\LAC/RAC/Cell Presence\LAC Vector\RAC Vector\Cell Id\Cell Id Vector\Passed Data\Sum Passed Counts the passed data amount for each cell for each RAC under a certain LAC >=SG4 1Day/24h/30 min Bssgp Cell Report\Bssgp Cell Available\LAC/RAC/Cell Presence\LAC Vector\RAC Vector\Cell Id\Cell Id Vector\Discarded Packets\Sum Discarded Counts the number of discarded packets for each cell for each RAC under a certain LAC >=SG4 1Day/24h/30 min BSSGP PAPU Report\Counter Counts the number of Bssgp PAPU reports >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Counter Counts the number of Bssgp PAPU events for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Average Sum Pr1 Counts the numerator of average BSSGP buffer utilisation in specific priority for each PAPU >=SG4 1 Day CCMA counter Explanation Bssgp Cell Report\Bssgp Cell Available\LAC/RAC/Cell Presence\LAC Vector\Discarded Packets\Sum Discarded Counts the number of discarded packets for each LAC Table 3 *) *) *).) DN05148836 Issue 2-2 Id:0900d805809551ce 61 . Counters of CCMA time classes (Cont. Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version TimeClass Counts the numerator of average BSSGP buffer utilisation in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Average Sum Pr3 Counts the numerator of average BSSGP buffer utilisation in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Average Sum Pr4 Counts the numerator of average BSSGP buffer utilisation in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Average Sum Pr5 Counts the numerator of average BSSGP buffer utilisation in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Average Den Pr1 Counts the denominator of average BSSGP buffer utilisation in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Average Den Pr2 Counts the denominator of average BSSGP buffer utilisation in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Average Den Pr3 Counts the denominator of average BSSGP buffer utilisation in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Average Den Pr4 Counts the denominator of average BSSGP buffer utilisation in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Average Den Pr5 Counts the denominator of average BSSGP buffer utilisation in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Counts the peak load in specific Available\Papu Vector\Peak Load Pr1 priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Counts the peak load in specific Available\Papu Vector\Peak Load Pr2 priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Counts the peak load in specific Available\Papu Vector\Peak Load Pr3 priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Counts the peak load in specific Available\Papu Vector\Peak Load Pr4 priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Counts the peak load in specific Available\Papu Vector\Peak Load Pr5 priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Lost Data Pr1 Counts the lost data amount in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Lost Data Pr2 Counts the lost data amount in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Lost Data Pr3 Counts the lost data amount in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Lost Data Pr4 Counts the lost data amount in specific priority for each PAPU >=SG4 1 Day CCMA counter Explanation BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Average Sum Pr2 Table 3 62 Counters of CCMA time classes (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG4 1Day/24h/30 min Pagings Report\Pagings Available\ LAC Vector\RAC Vector\Pagings / Sum Counts all pagings for each RAC under a specific LAC. >=SG4 1Day/24h/30 min CCMA counter Explanation BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Lost Data Pr5 NSVC Report\NSVC Available\NSEI Vector\NSVCI Vector\Cir Overflow\ Sum Table 3 Counters of CCMA time classes (Cont.) DN05148836 Issue 2-2 Id:0900d805809551ce 63 .Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version TimeClass Counts the lost data amount in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Dropped Packets Pr1 Counts the number of dropped packets in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Dropped Packets Pr2 Counts the number of dropped packets in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Dropped Packets Pr3 Counts the number of dropped packets in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Dropped Packets Pr4 Counts the number of dropped packets in specific priority for each PAPU >=SG4 1 Day BSSGP PAPU Report\Bssgp Papu Available\Papu Vector\Dropped Packets Pr5 Counts the number of dropped packets in specific priority for each PAPU >=SG4 1 Day NSVC Report\Counter Counts the number of NSVC reports >=SG4 1 Day NSVC Report\NSVC Available\NSEI Vector\Counter Counts the number of NSVC for each NSEI >=SG4 1 Day NSVC Report\NSVC Available\NSEI Vector\NSVCI Vector\Counter Counts the number of NSVC for each NSVCI for each NSEI >=SG4 1 Day Counts theCir Overflow for each NSVC Report\NSVC Available\NSEI Vector\NSVCI Vector\Fr Passed Data\ NSVCI for each NSEI Sum >=SG4 1 Day Counts the passed Fr data amount for each NSVCI for each NSEI >=SG4 1 Day Counts the passed IP data NSVC Report\NSVC Available\NSEI Vector\NSVCI Vector\IP Passed Data\ amount for each NSVCI for each NSEI Sum >=SG4 1 Day Counts the passed IG shared NSVC Report\NSVC Available\NSEI Vector\NSVCI Vector\IG Shared Data\ data amount for each NSVCI for each NSEI Sum >=SG4 1 Day NSVC Report\NSVC Available\NSEI Vector\NSVCI Vector\OG Shared Data\Sum Counts the passed OG shared data amount for each NSVCI for each NSEI >=SG4 1 Day Pagings Report\Counter Counts all pagings cumulatively for the time period >=SG4 1 Day Pagings Report\Pagings Available\ LAC Vector\Pagings\Sum Counts all pagings for each LAC. >=SG4 30min Table 3 64 TimeClass Counters of CCMA time classes (Cont. >=SG4 1Day/24h/30 min SGSN GTP Report\Logical PAPU Vector\Whole Data Amount\Sum Counts data amount transferred through each logical PAPU >=SG4 1Day/24h SGSN GTP Report\Logical PAPU Vector\Uplink Data Volume\Sum UL Counts data amount transferred >=SG4 uplink through each logical PAPU 1Day/24h SGSN GTP Report\Logical PAPU Vector\Downlink Data Volume\Sum DL Counts data amount transferred downlink through each logical PAPU >=SG4 1Day/24h SGSN GTP Report\Logical PAPU Vector\Discarded Packets\Sum Discarded Packets Counts amount of discarded data packets for each logical PAPU >=SG4 1Day/24h SGSN GTP Report\Logical PAPU Vector\Whole Packet Amount\Sum Packets Counts amount of data packets transferred through each logical PAPU >=SG4 1Day/24h SGSN GTP Report\Physical PAPU Vector\Whole Data Amount\Sum Counts data amount transferred through each physical PAPU >=SG4 1Day/24h SGSN GTP Report\Physical PAPU Vector\DataAmount Uplink\Sum UL Counts data amount transferred uplink through each physical PAPU >=SG4 1Day/24h SGSN GTP Report\Physical PAPU Vector\Data Amount Downlink\Sum DL Counts data amount transferred downlink through each physical PAPU >=SG4 1Day/24h SGSN GTP Report\Physical PAPU Vector\Discarded Packets\Sum Discarded Packets Counts amount of discarded data packets for each physical PAPU >=SG4 1Day/24h SGSN GTP Report\Physical PAPU Vector\Whole Packet Amount\Sum Packets Counts data amount transferred through each physical PAPU >=SG4 1Day/24h SGSN GTP Report\Physical Papu Vector\Counter Counts the number of GTPs for each physical PAPU >=SG4 1Day/24h LOA Stat Report\Counter Counts the number of LOA stat reports >=SG4 30min LOA Stat Report\WO-EX\Objectname\Unit Index\Load Rate Sum Counts the numerator of average load of certain WO-EX (working executing state) object unit processors.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version CCMA counter Explanation Pagings Report\Pagings Available\ PAPU Vector\Pagings\Sum Counts all pagings for each PAPU. >=SG4 1Day/24h/30 min Pagings Report\Pagings Available\ PAPU Vector\RAC Vector\Pagings\ Sum Counts all pagings for each RAC under a specific PAPU. >=SG4 30min LOA Stat Report\WO-EX\Objectname\Unit Index\Load Rate Den Counts the denominator of average load of certain WO-EX (working executing state) object unit processors.) Id:0900d805809551ce DN05148836 Issue 2-2 . For example. >=SG6 1Day/24h/ 30min SGSN Report\2G\Attaches\Error Cause Vector\Counter Counts all successful/unsuccessful 2G attaches for each error cause code >=SG6 1Day/24h/ 30min Table 4 Class SGSN SG6 combined ccma DN05148836 Issue 2-2 Id:0900d805809551ce 65 . if LAC is 003h and Cell is 001h. >=SG4 30min LOA Stat Report\SP-EX\Objectname\ Unit Index\Peak Load Rate Counts the peak load of certain SP-EX (spare executing state) object unit processors. >=SG6 1Day/24h/ 30min SGSN Report\2G\Attaches\Counter Counts all successful/unsuccessful 3G attaches. >=SG4 30min LOA Stat Report\SP-EX\Objectname\ Load Present\Load Rate Sum Counts the numerator of average load of each SP-EX (spare executing state) object unit processor group.) *) Cell ID is a unique number. >=SG4 30min LOA Stat Report\WO-EX\Objectname\Load Present\Load Rate Sum Counts the numerator of average load of each WO-EX (working executing state) object unit processor group. >=SG4 30min LOA Stat Report\SP-EX\Objectname\ Unit Index\Load Rate Sum Counts the numerator of average >=SG4 load of certain SP-EX (spare executing state) object unit processors. 30min LOA Stat Report\SP-EX\Objectname\ Unit Index\Load Rate Den Counts the denominator of average load of certain SP-EX (spare executing state) object unit processors. in which LAC and Cell are combined. >=SG4 30min LOA Stat Report\WO-EX\Objectname\Load Present\Load Rate Den Counts the denominator of average load of each WO-EX (working executing state) object unit processor group. >=SG4 30min LOA Stat Report\SP-EX\Objectname\ Load Present\Load Rate Den Counts the denominator of average load of each SP-EX (spare executing state) object unit processor group.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version TimeClass Counts the peak load of certain WO-EX (working executing state) object unit processors. >=SG4 30min CCMA counter Explanation LOA Stat Report\WO-EX\Objectname\Unit Index\Peak Load Rate Table 3 Counters of CCMA time classes (Cont. >=SG6 1Day/24h/ 30min SGSN Report\2G\Attaches\Unsuccessful\Counter Counts all unsuccessful 2G attaches. Cell ID is 0x30001h. The following counters belong to SGSN SG6 combined clear code matrix: Explanation SGSN version Time CCMA counter SGSN Report\Counter Counts all RTT reports. Counts all successful/unsuccessful 2G PDP tions\Error Cause Vector\Counter Context Modifications for each Error Cause code >=SG6 1Day/24h/ 30min SGSN Report\2G\PDP Context Deactivations\Counter Counts all successful/unsuccessful 2G PDP Context Deactivations >=SG6 1Day/24h/ 30min SGSN Report\2G\PDP Context Deactivations\Unsuccessful\Counter SGSN Report\2G\PDP Context Deactivations\Unsuccessful\Counter >=SG6 1Day/24h/ 30min SGSN Report\2G\PDP Context Deactivations\Unsuccessful\Cell Vector\ Counter Counts all unsuccessful 2G PDP Context Deactivations for each Cell.Counts all unsuccessful 2G PDP Context Modifications for each Cell for each Error tions\Unsuccessful\Cell Vector\Error Cause code Cause Vector\Counter >=SG6 1Day/24h/ 30min SGSN Report\2G\PDP Context Modifica. >=SG6 1Day/24h/ 30min SGSN Report\2G\PDP Context Deactivations\Unsuccessful\Cell Vector\Error Cause Vector\Counter Counts all unsuccessful 2G PDP Context Deactivations for each Cell for each Error Cause code >=SG6 1Day/24h/ 30min SGSN Report\2G\PDP Context Deactivations\Error Cause Vector\Counter Counts all successful/unsuccessful 2G PDP Context Deactivations for each Error Cause code >=SG6 1Day/24h/ 30min SGSN Report\2G\RA Updates\Counter Counts all successful/unsuccessful 2G RA updates >=SG6 1Day/24h/ 30min SGSN Report\2G\RA Updates\Unsuccessful\Counter Counts all unsuccessful 2G RA updates >=SG6 1Day/24h/ 30min SGSN Report\2G\RA Updates\Error Cause Vector\Counter Counts all successful/unsuccessful 2G RA updates for each Error Cause code. >=SG6 1Day/24h/ 30min Table 4 66 SGSN SG6 combined ccma (Cont.Counts all unsuccessful 2G PDP Context tions\Unsuccessful\Counter Modifications >=SG6 1Day/24h/ 30min SGSN Report\2G\PDP Context Modifica. >=SG6 1Day/24h/ 30min SGSN Report\2G\PDP Context Activations\Unsuccessful\Cell Vector\Error Cause Vector\Counter Counts all unsuccessful 2G PDP Context Activations for each Cell for each Error Cause code >=SG6 1Day/24h/ 30min SGSN Report\2G\PDP Context Activations\Error Cause Vector\Counter Counts all successful/unsuccessful 2G PDP Context Activations for each Error Cause code >=SG6 1Day/24h/ 30min SGSN Report\2G\PDP Context Modifica.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time Class CCMA counter Explanation SGSN Report\2G\PDP Context Activations\Counter Counts all successful/unsuccessful 2G PDP Context Activations >=SG6 1Day/24h/ 30min SGSN Report\2G\PDP Context Activations\Unsuccessful\Counter Counts all unsuccessful 2G PDP Context Activations >=SG6 1Day/24h/ 30min SGSN Report\2G\PDP Context Activations\Unsuccessful\Cell Vector\Counter Counts all unsuccessful 2G PDP Context Activations for each Cell.) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG6 1Day/24h/ 30min SGSN Report\2G\PDP Context Modifica.Counts all unsuccessful 2G PDP Context tions\Unsuccessful\Cell Vector\Counter Modifications for each Cell.Counts all successful/unsuccessful 2G PDP tions\Counter Context Modifications >=SG6 1Day/24h/ 30min SGSN Report\2G\PDP Context Modifica. >=SG6 1Day/24h/ 30min SGSN Report\3G\Attaches\Counter Counts all successful/unsuccessful 3G attaches. Counts all unsuccessful 3G PDP Context tions\Unsuccessful\Counter Modifications >=SG6 1Day/24h/ 30min SGSN Report\3G\PDP Context Modifica.Counts all unsuccessful 3G PDP Context tions\Unsuccessful\Sac Vector\Counter Modifications for each Sac. >=SG6 1Day/24h/ 30min SGSN Report\3G\PDP Context Deactivations\Error Cause Vector\Counter Counts all successful/unsuccessful 3G PDP Context Deactivations for each Error Cause code >=SG6 1Day/24h/ 30min SGSN Report\3G\RA Updates\Counter Counts all successful/unsuccessful 3G RA updates >=SG6 1Day/24h/ 30min SGSN Report\3G\RA Updates\Unsuccessful\Counter Counts all unsuccessful 3G RA updates >=SG6 1Day/24h/ 30min SGSN Report\3G\RA Updates\Error Cause Vector\Counter Counts all successful/unsuccessful 3G RA updates for each Error Cause code. >=SG7 1Day/24h/ 30min Table 4 Class SGSN SG6 combined ccma (Cont.Counts all successful/unsuccessful 3G PDP tions\Counter Context Modifications >=SG6 1Day/24h/ 30min SGSN Report\3G\PDP Context Modifica. >=SG6 1Day/24h/ 30min SGSN Report\RA Updates\Counter Counts all successful/unsuccessful RA updates >=SG6 1Day/24h/ 30min SGSN Report\RA Updates\RA Updates Vector\Counter Counts all successful/unsuccessful RA update attempts for each RA update types >=SG6 1Day/24h/ 30min SGSN Report\I-HSPA\Counter Counts the number of I-HSPA Reports.Counts all successful/unsuccessful 3G PDP tions\Error Cause Vector\Counter Context Modifications for each Error Cause code >=SG6 1Day/24h/ 30min SGSN Report\3G\PDP Context Deactivations\Counter Counts all successful/unsuccessful 3G PDP Context Deactivations >=SG6 1Day/24h/ 30min SGSN Report\3G\PDP Context Deactivations\Unsuccessful\Counter Counts all unsuccessful 3G PDP Context Deactivations >=SG6 1Day/24h/ 30min SGSN Report\3G\PDP Context Deactivations\Unsuccessful\Sac Vector\ Counter Counts all unsuccessful 3G PDP Context Deactivations for each Sac. >=SG6 1Day/24h/ 30min SGSN Report\3G\PDP Context Activations\Error Cause Vector\Counter Counts all successful/unsuccessful 3G PDP Context Activations for each Error Cause code >=SG6 1Day/24h/ 30min SGSN Report\3G\PDP Context Modifica.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Time CCMA counter Explanation SGSN version SGSN Report\3G\Attaches\Unsuccessful\Counter Counts all unsuccessful 3G attaches >=SG6 1Day/24h/ 30min SGSN Report\3G\Attaches\Error Cause Vector\Counter Counts all successful/unsuccessful 3G attaches for each error cause code >=SG6 1Day/24h/ 30min SGSN Report\3G\PDP Context Activations\Counter Counts all successful/unsuccessful 3G PDP Context Activations >=SG6 1Day/24h/ 30min SGSN Report\3G\PDP Context Activations\Unsuccessful\Counter Counts all unsuccessful 3G PDP Context Activations >=SG6 1Day/24h/ 30min SGSN Report\3G\PDP Context Activations\Unsuccessful\Sac Vector\Counter Counts all unsuccessful 3G PDP Context Activations for each Sac. >=SG6 1Day/24h/ 30min SGSN Report\3G\PDP Context Modifica.) DN05148836 Issue 2-2 Id:0900d805809551ce 67 . >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\Network Operators Attempted Vector\Counter Counts the number of successful/unsuccessful attaches for each operator. Counts the number of successful and unsuccessful attaches. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\ Roaming Status\Unsuccessful\Counter Counts all unsuccessful roaming attaches. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\Unsuccessful\Mobile Type Vector\Counter Counts all unsuccessful attaches for each mobile phone type. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\Successful\Network Operators Successful Vector\Counter Counts the number of successful attaches for each operator. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\Error Cause Vector\Counter Counts all successful/unsuccessful attaches for each Error cause code. >=SG7 1Day/24h/ 30min CCMA counter Table 4 68 Explanation Class SGSN SG6 combined ccma (Cont. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\Unsuccessful\Network Operators Unsuccessful Vector\Counter Counts the number of unsuccessful attach attempts for each operator.) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\Mobile Type Vector\Counter Counts all successful/unsuccessful attaches for each mobile phone type. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\Successful\Counter Counts the number of successful attaches. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\Unsuccessful\LAC Vector\Counter Counts all unsuccessful attaches for each LAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\LAC Vector\Counter Counts all successful/unsuccessful attaches for each LAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\Unsuccessful\Counter Counts the number of unsuccessful attaches. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\ Roaming Status\Counter Counts all successful/unsuccessful roaming attaches. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\Unsuccessful\Mobile Type Vector\Error Cause Vector\Counter Counts all unsuccessful attaches for each Error cause code for certain mobile phone type. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\Unsuccessful\LAC Vector\Error Cause Vector\ Counter Counts all unsuccessful attaches for each LAC for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\Mobile Counts all successful/unsuccessful Type Vector\Error Cause Vector\Counter attaches for each Error cause code for certain mobile phone type.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time SGSN Report\I-HSPA\Attaches\Counter. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\Unsuccessful\Network Operators Unsuccessful Vector\Error Cause Vector\Counter Counts the number of error causes of the unsuccessful attaches for each operator. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\LAC Vector\Error Cause Vector\Counter Counts all successful/unsuccessful attaches for each LAC for each Error cause code. Unsuccessful Vector\Counter 1Day/24h/ 30min >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\ Roaming Status\LAC Vector\RAC Vector\Error Cause Vector\Counter Counts all successful/unsuccessful roaming attaches for each RAC of a specific LAC for each Error cause.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time Class CCMA counter Explanation SGSN Report\I-HSPA\Attaches\ Roaming Status\Unsuccessful\LAC Vector\Counter Counts all unsuccessful roaming attaches for each LAC.Counts all unsuccessful PDP Context Activations for each SAC for each Error cause vations\Unsuccessful\SAC Vector\Error code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\ Roaming Status\LAC Vector\RAC Vector\Counter Counts all successful/unsuccessful roaming attaches for each RAC under a specific LAC.Counts all unsuccessful PDP Context Activations for each SAC. vations\Unsuccessful\SAC Vector\ Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.) DN05148836 Issue 2-2 Id:0900d805809551ce 69 .Counts the number of error causes of the vations\Unsuccessful\Network Operators unsuccessful PDP Context Activations for Unsuccessful Vector\Error Cause Vector\ each operator.Counts all unsuccessful PDP Context Activations for each mobile phone type. Vector\Error Cause Vector\Counter >=SG7 1Day/24h/ 30min >=SG7 SGSN Report\I-HSPA\PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. Counter Table 4 SGSN SG6 combined ccma (Cont.Counts the number of successful and vations\Counter unsuccessful PDP Context Activations. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\ Roaming Status\Unsuccessful\LAC Vector\RAC Vector\Error Cause Vector\ Counter Counts all unsuccessful roaming attaches for each RAC of a specific LAC for each Error cause.Counts the number of unsuccessful PDP vations\Unsuccessful\Counter Context Activations. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\ Roaming Status\Error Cause Vector\ Counter Counts all successful/unsuccessful roaming attaches for each Error cause code. Cause Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all unsuccessful PDP Context Activations for each Error cause code for certain vations\Unsuccessful\Mobile Type mobile phone type. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\ Roaming Status\LAC Vector\Counter Counts all successful/unsuccessful roaming attaches for each LAC.Counts the number of unsuccessful PDP vations\Unsuccessful\Network Operators Context Activation attempts for each operator. vations\Unsuccessful\Mobile Type Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\ Roaming Status\Unsuccessful\LAC Vector\RAC Vector\Counter Counts all unsuccessful roaming attaches for each RAC under a specific LAC. vations\Unsuccessful\Sac Id\Sac Id Vector\Error Cause Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.. vations\Unsuccessful\Sac Id\Sac Id Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations for each Error cause code for each vations\TREC 1\Sac Id\Sac Id Vector\ SAC.Counts all specific TREC PDP Context Acti.) Id:0900d805809551ce DN05148836 Issue 2-2 .Counts the number of unsuccessful PDP Context Activations for each APN.>=SG7 vations for each Error cause code for each vations\TREC 3\Sac Id\Sac Id Vector\ SAC.>=SG7 vations for each SAC.Counts all specific TREC PDP Context Acti. Vector\Error Cause Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all unsuccessful 3G PDP Context Activations for each SAC.Counts all specific TREC PDP Context Acti.Counts all specific TREC PDP Context Acti.Counts all successful/unsuccessful PDP Context Activations for each SAC for certain vations\APN Vector\Sac Id\Sac Id APN. Error Cause Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all unsuccessful 3G PDP Context Activations for each Error Cause code.Counts all specific TREC PDP Context Acti.Counts all specific TREC PDP Context Acti. Error Cause Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. vations\TREC 4\Sac Id\Sac Id Vector\ Counter 1Day/24h/ 30min CCMA counter Table 4 70 Explanation Class SGSN SG6 combined ccma (Cont. Error Cause Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations for each Error cause code for each vations\TREC 2\Sac Id\Sac Id Vector\ SAC.Counts all specific TREC PDP Context Acti. Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations for each SAC. Error Cause Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all successful/unsuccessful PDP Context Activations error causes for each vations\APN Vector\Sac Id\Sac Id SAC for each APN.>=SG7 vations for each SAC.>=SG7 vations for each SAC.>=SG7 vations for each Error cause code for each vations\TREC 0\Sac Id\Sac Id Vector\ SAC. vations\TREC 3\Sac Id\Sac Id Vector\ Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. vations\TREC 0\Sac Id\Sac Id Vector\ Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all specific TREC PDP Context Acti.Counts all specific TREC PDP Context Acti. vations\TREC 2\Sac Id\Sac Id Vector\ Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. vations\TREC 1\Sac Id\Sac Id Vector\ Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations for each SAC.Counts all specific TREC PDP Context Acti. vations\TREC 0\Sac Id\Sac Id Vector\ Error Cause Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. vations\Unsuccessful\APN Vector\ Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations for each SAC.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time SGSN Report\I-HSPA\PDP Context Acti. >=SG7 vations for each SAC.>=SG7 vations for each SAC.Counts all specific TREC PDP Context Acti.>=SG7 vations for each SAC.>=SG7 vations for each SAC.Counts all specific TREC PDP Context Acti.Counts all successful/unsuccessful 3G PDP vations\Sac Id\Sac Id Vector\Error Cause Context Activations for each Error Cause code.>=SG7 vations for each Error cause code for each vations\TREC 6\Sac Id\Sac Id Vector\ SAC.Counts all specific TREC PDP Context Acti.Counts all specific TREC PDP Context Acti. vations\TREC 7\Sac Id\Sac Id Vector\ Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Traffica Reference Guide for SGSN Direct Interface CCMA counter Explanation Real-time monitoring SGSN version Time Class SGSN Report\I-HSPA\PDP Context Acti.Counts all specific TREC PDP Context Acti.Counts all specific TREC PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. vations\TREC 6\Sac Id\Sac Id Vector\ Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations for each Error cause code for each vations\TREC 4\Sac Id\Sac Id Vector\ SAC.Counts all specific TREC PDP Context Acti. Error Cause Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. Error Cause Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. Error Cause Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all successful/unsuccessful 3G PDP vations\Sac Id\Sac Id Vector\Counter Context Activations for each SAC.Counts all specific TREC PDP Context Acti.>=SG7 vations for each SAC.>=SG7 vations for each Error cause code for each vations\TREC 7\Sac Id\Sac Id Vector\ SAC. vations\TREC 5\Sac Id\Sac Id Vector\ Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations for each Error cause code for each vations\TREC 9\Sac Id\Sac Id Vector\ SAC. vations\TREC 8\Sac Id\Sac Id Vector\ Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations for each Error cause code for each vations\TREC 8\Sac Id\Sac Id Vector\ SAC.Counts all specific TREC PDP Context Acti. Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\Unsuccessful\Sac Id\Sac Id Vector\Counter Counts all unsuccessful 3G PDP Context Deactivations for each SAC.) DN05148836 Issue 2-2 Id:0900d805809551ce 71 . Error Cause Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations for each Error cause code for each vations\TREC 5\Sac Id\Sac Id Vector\ SAC. Error Cause Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all specific TREC PDP Context Acti. >=SG7 1Day/24h/ 30min Table 4 SGSN SG6 combined ccma (Cont. Error Cause Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all specific TREC PDP Context Acti. vations\TREC 9\Sac Id\Sac Id Vector\ Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\Unsuccessful\Sac Id\Sac Id Vector\Error Cause Vector\Counter Counts all unsuccessful 3G PDP Context Deactivations for each Error Cause code. Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time Class CCMA counter Explanation SGSN Report\I-HSPA\PDP Context Deactivations\Sac Id\Sac Id Vector\ Counter Counts all successful/unsuccessful 3G PDP Context deactivations for each SAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. vations\Successful\Network Operators Successful Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.) Id:0900d805809551ce DN05148836 Issue 2-2 .Counts all successful/unsuccessful vations\Mobile Type Vector\Error Cause attaches for each Error cause code for certain mobile phone type.Counts all successful/unsuccessful PDP vations\SAC Vector\Error Cause Vector\ Context Activations for each SAC for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all successful/unsuccessful PDP vations\Error Cause Vector\Counter Context Activations for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Modifications\Unsuccessful\Sac Id\Sac Id Vector\Counter Counts all unsuccessful 3G PDP Context Modifications for each Sac >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Modifications\Unsuccessful\Sac Id\Sac Id Vector\Error Cause Vector\Counter Counts all unsuccessful 3G PDP Context Modifications for each Error Cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. Vector\Counter 1Day/24h/ 30min >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all successful/unsuccessful PDP vations\SAC Vector\Counter Context Activations for each SAC.Counts all successful/unsuccessful PDP vations\Mobile Type Vector\Counter Context Activations for each mobile phone type. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Modifications\Sac Id\Sac Id Vector\Error Cause Vector\Counter Counts all successful/unsuccessful 3G PDP Context Modifications for each Error Cause code.Counts the number of successful/unsuccessful PDP Context activations of the all vations\Network Operators Attempted Vector\Mobile Phone Existence\Counter mobile phones for a certain operator.>=SG7 cessful PDP Context Activations for each vations\Network Operators Attempted operator.Counts the number of the successful/unsuc.Counts the number of successful PDP vations\Successful\Counter Context Activations >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Modifications\Sac Id\Sac Id Vector\ Counter Counts all successful/unsuccessful 3G PDP Context Modifications for each SAC. Mobile Phones Table 4 72 SGSN SG6 combined ccma (Cont.Counts the number of the successful PDP Context Activations for each operator. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\Sac Id\Sac Id Vector\Error Cause Vector\Counter Counts all successful/unsuccessful 3G PDP Context Deactivations for each Error Cause code. Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. 1Day/24h/ 30min CCMA counter Table 4 Explanation Class SGSN SG6 combined ccma (Cont.) DN05148836 Issue 2-2 Id:0900d805809551ce 73 .Counts all successful/unsuccessful roaming attaches for each Error cause code.>=SG7 vations\TREC 0\APN Vector\Counter vations for each APN.Counts the number of successful/unsuccessful PDP Context activations of the vations\Network Operators Attempted mobile types for a certain operator. Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time SGSN Report\I-HSPA\PDP Context Acti.Counts all successful/unsuccessful PDP vations\APN Vector\SAC Vector\Counter Context Activations for each SAC for a certain APN. Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all successful/unsuccessful PDP Context Activations error causes for each vations\APN Vector\SAC Vector\Error SAC for each APN.Counts all specific TREC PDP Context Acti. Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. Cause Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all unsuccessful roaming attaches.Counts all PDP Context Activations for vations\TREC 0\Counter specific TREC. Vector\Mobile Phone Existence\Mobile Phone Vector\Error Cause Vector\ Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. vations\Roaming Status\Unsuccessful\ Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all successful/unsuccessful PDP vations\APN Vector\Mobile Type Vector\ Context Activations for each APN for each Mobile phone type.Counts all unsuccessful roaming attaches for each Error cause code.Counts all successful/unsuccessful PDP vations\APN Vector\Error Cause Vector\ Context Activations error causes for for each APN.Counts the number of successful/unsuccessful PDP Context activations of the vations\Network Operators Attempted mobile phone types for a certain operator. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all specific TREC PDP Context Acti.Counts the number of successful/unsucvations\APN Vector\Counter cessful PDP Context Activations for each APN. vations\Roaming Status\Unsuccessful\ Error Cause Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. vations\Roaming Status\Error Cause Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all successful/unsuccessful roaming vations\Roaming Status\Counter attaches >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all unsuccessful roaming attaches for each Error cause code for each Mobile vations\Roaming Status\Unsuccessful\ Error Cause Vector\Mobile Type Vector\ phone types.>=SG7 vations\TREC 0\SAC Vector\Counter vations for each SAC. Vector\Mobile Phone Existence\Mobile Phone Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations\TREC 2\APN Vector\Counter vations for each APN. 1Day/24h/ 30min Table 4 74 SGSN SG6 combined ccma (Cont.>=SG7 vations\TREC 0\SAC Vector\Error Cause vations for each Error cause code for each SAC.Counts all specific TREC PDP Context Acti.Counts all PDP Context Activations for vations\TREC 1\Counter specific TREC. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all specific TREC PDP Context Acti.Counts all PDP Context Activations for vations\TREC 3\Counter specific TREC. Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations\TREC 1\APN Vector\Counter vations for each APN.Counts all PDP Context Activations for vations\TREC 5\Counter specific TREC. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all specific TREC PDP Context Acti.Counts all specific TREC PDP Context Acti.>=SG7 vations\TREC 4\APN Vector\Counter vations for each APN. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Real-time monitoring CCMA counter Traffica Reference Guide for SGSN Direct Interface Explanation SGSN version Time Class SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations\TREC 3\SAC Vector\Counter vations for each SAC. Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.) Id:0900d805809551ce DN05148836 Issue 2-2 .>=SG7 vations\TREC 2\SAC Vector\Counter vations for each SAC.Counts all specific TREC PDP Context Acti. Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations\TREC 3\APN Vector\Counter vations for each APN.Counts all specific TREC PDP Context Acti.>=SG7 vations\TREC 5\APN Vector\Counter vations for each APN.Counts all specific TREC PDP Context Acti.Counts all PDP Context Activations for vations\TREC 4\Counter specific TREC.Counts all specific TREC PDP Context Acti.Counts all specific TREC PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations\TREC 1\SAC Vector\Counter vations for each SAC.Counts all specific TREC PDP Context Acti.Counts all specific TREC PDP Context Acti.>=SG7 vations\TREC 3\SAC Vector\Error Cause vations for each Error cause code for each SAC.>=SG7 vations\TREC 2\SAC Vector\Error Cause vations for each Error cause code for each SAC.>=SG7 vations\TREC 1\SAC Vector\Error Cause vations for each Error cause code for each SAC.Counts all specific TREC PDP Context Acti.>=SG7 vations\TREC 4\SAC Vector\Error Cause vations for each Error cause code for each SAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all specific TREC PDP Context Acti. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations\TREC 4\SAC Vector\Counter vations for each SAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all PDP Context Activations for vations\TREC 2\Counter specific TREC. Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all specific TREC PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. >=SG7 vations\TREC 7\SAC Vector\Counter vations for each SAC.>=SG7 vations\TREC 5\SAC Vector\Error Cause vations for each Error cause code for each SAC.Counts all specific TREC PDP Context Acti. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all specific TREC PDP Context Acti.Counts all specific TREC PDP Context Acti.>=SG7 vations\TREC 8\APN Vector\Counter vations for each APN. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations\TREC 7\SAC Vector\Error Cause vations for each Error cause code for each SAC. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all PDP Context Activations for vations\TREC 7\Counter specific TREC. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.) DN05148836 Issue 2-2 Id:0900d805809551ce 75 .>=SG7 vations\TREC 9\APN Vector\Counter vations for each APN.Counts all specific TREC PDP Context Acti.>=SG7 vations\TREC 5\SAC Vector\Counter vations for each SAC.Counts all specific TREC PDP Context Acti. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations\TREC 8\SAC Vector\Counter vations for each SAC.Counts all specific TREC PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations\TREC 6\APN Vector\Counter vations for each APN. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all PDP Context Activations for vations\TREC 8\Counter specific TREC.Counts all specific TREC PDP Context Acti. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all specific TREC PDP Context Acti.Traffica Reference Guide for SGSN Direct Interface CCMA counter Explanation Real-time monitoring SGSN version Time Class SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations\TREC 8\SAC Vector\Error Cause vations for each Error cause code for each SAC.Counts all specific TREC PDP Context Acti.Counts all specific TREC PDP Context Acti. Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations\TREC 7\APN Vector\Counter vations for each APN.Counts all specific TREC PDP Context Acti.>=SG7 vations\TREC 6\SAC Vector\Counter vations for each SAC. Vector\Counter 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\Counter 1Day/24h/ 30min Table 4 Counts the number of successful and unsuccessful PDP Context Deactivations >=SG7 SGSN SG6 combined ccma (Cont.>=SG7 vations\TREC 6\SAC Vector\Error Cause vations for each Error cause code for each SAC. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Counts all specific TREC PDP Context Acti.Counts all specific TREC PDP Context Acti.Counts all specific TREC PDP Context Acti.>=SG7 vations\TREC 9\SAC Vector\Counter vations for each SAC. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.>=SG7 vations\TREC 9\SAC Vector\Error Cause vations for each Error cause code for each SAC.Counts all PDP Context Activations for vations\TREC 9\Counter specific TREC.Counts all PDP Context Activations for vations\TREC 6\Counter specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\APN Vector\Data Volume Uplink\Sum Uplink Counts the data volume sent uplink for a specific APN. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\SAC Vector\Error Cause Vector\Counter Counts all successful/unsuccessful PDP Context Deactivations for each SAC for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\Successful\Counter Counts the number of successful PDP Context Deactivations.>=SG7 cessful PDP Context Deactivations for each operator.) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\Network Operators Attempted Vector\Counter Counts the number of the successful/unsuc.>=SG7 SGSN Report\I-HSPA\PDP Context Deactivations\Unsuccessful\SAC Vector\ tivations for each SAC. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\APN Vector\Counter Counts the number of successful/unsuccessful PDP Context Deactivations for each APN.>=SG7 SGSN Report\I-HSPA\PDP Context Deactivations\Unsuccessful\SAC Vector\ tivations for each SAC for each Error cause code. Error Cause Vector\Counter 1Day/24h/ 30min CCMA counter Explanation SGSN Report\I-HSPA\PDP Context Deactivations\Unsuccessful\Counter Counts the number of unsuccessful PDP Context Deactivations Class SGSN Report\I-HSPA\PDP Context Deactivations\Unsuccessful\Network Operators Unsuccessful Vector\Counter Counts the number of unsuccessful PDP Context Deactivations attempts for each operator >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\Unsuccessful\Network Operators Unsuccessful Vector\Error Cause Vector\Counter Counts the number of error causes of the unsuccessful PDP Context Deactivations for each operator. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\APN Vector\Data Volume Downlink\Sum Downlink Counts the data volume sent downlink for a specific APN. Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Counts the data volume sent uplink for a Deactivations\APN Vector\Mobile Types\ specific APN for each Mobile phone types. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\Error Cause Vector\ Counter Counts all successful/unsuccessful PDP Context Deactivations for each Error cause code.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time >=SG7 1Day/24h/ 30min Counts all unsuccessful PDP Context Deac. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\Successful\Network Operators Successful Vector\Counter Counts the number of the successful PDP Context Deactivations for each operator. Counter 1Day/24h/ 30min Counts all unsuccessful PDP Context Deac. >=SG7 1Day/24h/ 30min Counts all successful/unsuccessful PDP SGSN Report\I-HSPA\PDP Context Deactivations\APN Vector\Mobile Types\ Context Deactivations for each APN for each Mobile phone types. Data Volume Uplink\Sum Uplink >=SG7 1Day/24h/ 30min Table 4 76 SGSN SG6 combined ccma (Cont. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\SAC Vector\Counter Counts all successful/unsuccessful PDP Context Deactivations for each SAC. 1Day/24h/ 30min SGSN Report\I-HSPA\RA Updates\ Unsuccessful\RA Update Type Vector\ Error Cause Vector\Counter Counts the number of error causes of the RA Updates for each RA Update Types. Data Volume Downlink\Sum Downlink >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Modifications\Counter Counts the number of successful and unsuccessful PDP Context Modifications.>=SG7 fications for each SAC. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Modifications\Error Cause Vector\ Counter Counts all successful/unsuccessful PDP Context Modifications for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Modifications\SAC Vector\Counter Counts all successful/unsuccessful PDP Context Modifications for each SAC. 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Modifications\Unsuccessful\SAC Vector\ Error Cause Vector\Counter Counts all unsuccessful PDP Context Modi.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time Counts the data volume sent downlink for a SGSN Report\I-HSPA\PDP Context Deactivations\APN Vector\Mobile Types\ specific APN for each Mobile phone types. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\RA Updates\ Unsuccessful\RAC Vector\Error Cause Vector\Counter Counts all unsuccessful RA Updates for each RAC for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\RA Updates\ Unsuccessful\Counter Counts the number of unsuccessful RA Updates. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Modifications\Unsuccessful\SAC Vector\ Counter Counts all unsuccessful PDP Context Modi. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Modifications\Roaming Status\Unsuccessful\Counter Counts all unsuccessful roaming attaches.>=SG7 fications for each SAC for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Modifications\Roaming Status\Counter Counts all successful/unsuccessful roaming attaches. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Modifications\SAC Vector\Error Cause Vector\Counter Counts all successful/unsuccessful PDP Context Modifications for each SAC for each Error cause code.) DN05148836 Issue 2-2 Id:0900d805809551ce 77 . >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Modifications\Roaming Status\Error Cause Vector\Counter Counts all unsuccessful roaming attaches for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\RA Updates\ Unsuccessful\RA Update Type Vector\ Counter Counts all successful/unsuccessful RA >=SG7 Update attempts for each RA Update Types. 1Day/24h/ 30min CCMA counter Table 4 Explanation >=SG7 Class SGSN SG6 combined ccma (Cont. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\RA Updates\ Counter Counts the number of successful and unsuccessful RA Updates. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\RA Updates\ Unsuccessful\RAC Vector\Counter Counts all unsuccessful RA Updates for each RAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Modifications\Unsuccessful\Counter Counts the number of unsuccessful PDP Context Modifications. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Detaches\Unsuccessful\LAC Vector\Counter Counts all unsuccessful detaches for each LAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ Counter Counts the number of successful and unsuccessful SMS deliveries. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\RA Updates\RAC vector\Counter Counts all successful/unsuccessful RA Updates for each RAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Detaches\Successful\Counter Counts the number of successful detaches. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Detaches\Unsuccessful\Network Operators Unsuccessful Vector\Counter Counts the number of unsuccessful detach attempts for each operator. >=SG7 1Day/24h/ 30min Table 4 78 SGSN SG6 combined ccma (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG7 1Day/24h/ 30min >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Detaches\Counter Counts the number of successful and unsuccessful attaches. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Detaches\Unsuccessful\LAC Vector\Error Cause Vector\ Counter Counts all unsuccessful detaches for each LAC for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Detaches\Successful\Network Operators Successful Vector\Counter Counts the number of successful detaches for each operator. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ MT SMS Deliveries\Counter Counts the number of successful and unsuccessful MT SMS deliveries. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Detaches\Error Cause Vector\Counter Counts all successful/unsuccessful detaches for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Detaches\ Network Operators Attempted Vector\ Counter Counts the number of successful/unsuccessful detaches for each operator. SGSN Report\I-HSPA\Detaches\Unsuccessful\Counter Counts the number of unsuccessful detaches. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ MT SMS Deliveries\Unsuccessful\ Counter Counts the number of unsuccessful MT SMS deliveries. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Detaches\Unsuccessful\Network Operators Unsuccessful Vector\Error Cause Vector\Counter Counts the number of error causes of the unsuccessful detaches for each operator. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Detaches\LAC Vector\Error Cause Vector\Counter Counts all successful/unsuccessful detaches for each LAC for each Error cause code.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time Class CCMA counter Explanation SGSN Report\I-HSPA\RA Updates\ Unsuccessful\Error Cause Vector\ Counter Counts all successful/unsuccessful RA Updates for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Detaches\LAC Vector\Counter Counts all successful/unsuccessful detaches for each LAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\RA Updates\RAC vector\Error Cause Vector\Counter Counts all successful/unsuccessful RA Updates for each RAC for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ MO SMS Deliveries\Unsuccessful\SAC Vector\Counter Counts all unsuccessful MO-SMS deliveries for each SAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ MT SMS Deliveries\Unsuccessful\SAC Vector\Error Cause Vector\Counter Counts all unsuccessful MT-SMS deliveries for each SAC for each Error Cause code. Error Cause Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ MO SMS Deliveries\Counter Counts the number of successful and unsuccessful MO SMS deliveries. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ MO SMS Deliveries\Error Cause Vector\ Counter Counts all unsuccessful MO-SMS deliveries for each Error Cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ MT SMS Deliveries\Error Cause Vector\ Counter Counts all unsuccessful MT-SMS deliveries for each Error Cause code.) DN05148836 Issue 2-2 Id:0900d805809551ce 79 . >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ MO SMS Deliveries\Unsuccessful\SAC Vector\Error Cause Vector\Counter Counts all unsuccessful MO-SMS deliveries for each SAC for each Error Cause code. Counter >=SG7 1Day/24h/ 30min Counts all successful/unsuccessful MTSGSN Report\I-HSPA\SMS Deliveries\ MT SMS Deliveries\Sac Id\Sac Id Vector\ SMS deliveries for each SAC for each Error Cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ MO SMS Deliveries\Unsuccessful\ Counter Counts the number of unsuccessful MO SMS deliveries. Sac Id Vector\Error Cause Vector\ Counter >=SG7 1Day/24h/ 30min Counts all successful/unsuccessful MTSGSN Report\I-HSPA\SMS Deliveries\ MT SMS Deliveries\Sac Id\Sac Id Vector\ SMS deliveries for each SAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ MT SMS Deliveries\SAC Vector\Error Cause Vector\Counter Counts all successful/unsuccessful MTSMS deliveries for each Error Cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ MT SMS Deliveries\SAC Vector\Counter Counts all successful/unsuccessful MTSMS deliveries for each SAC for each Error Cause code. >=SG7 1Day/24h/ 30min Counts all unsuccessful MT-SMS deliveries SGSN Report\I-HSPA\SMS Deliveries\ MT SMS Deliveries\Unsuccessful\Sac Id\ for each SAC. >=SG7 1Day/24h/ 30min >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ Counts all successful/unsuccessful MOMO SMS Deliveries\SAC Vector\Counter SMS deliveries for each SAC.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time Class CCMA counter Explanation SGSN Report\I-HSPA\SMS Deliveries\ MT SMS Deliveries\Unsuccessful\SAC Vector\Counter Counts all unsuccessful MT-SMS deliveries for each SAC. Table 4 SGSN SG6 combined ccma (Cont. Sac Id Vector\Counter >=SG7 1Day/24h/ 30min Counts all unsuccessful MT-SMS deliveries SGSN Report\I-HSPA\SMS Deliveries\ MT SMS Deliveries\Unsuccessful\Sac Id\ for each SAC for each Error Cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ MO SMS Deliveries\Unsuccessful\Sac Id\Sac Id Vector\Counter Counts all unsuccessful MO-SMS deliveries for each SAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Negotiated Traffic Class Presence\Negotiated Traffic Class 1\ Counter Counts the number of negotiations for a specific traffic class. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ MO SMS Deliveries\Sac Id\Sac Id Vector\Error Cause Vector\Counter Counts all successful/unsuccessful MOSMS deliveries for each SAC for each Error Cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Traffic Class 3\Traffic Class Successful Request\Counter Counts the number of successful requests for a specific traffic class. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ MO SMS Deliveries\Unsuccessful\Sac Id\Sac Id Vector\Error Cause Vector\ Counter Counts all unsuccessful MO-SMS deliveries for each SAC for each Error Cause code.) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Traffic Class 1\Traffic Class Successful Request\Counter Counts the number of successful requests for a specific traffic class.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time Class CCMA counter Explanation SGSN Report\I-HSPA\SMS Deliveries\ MO SMS Deliveries\SAC Vector\Error Cause Vector\Counter Counts all successful/unsuccessful MOSMS deliveries for each SAC for each Error Cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\SMS Deliveries\ MO SMS Deliveries\Sac Id\Sac Id Vector\Counter Counts all successful/unsuccessful MOSMS deliveries for each SAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Negotiated Traffic Class Presence\Counter Counts the number of negotiations for all traffic classes. >=SG7 1Day/24h/ 30min Table 4 80 SGSN SG6 combined ccma (Cont. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Traffic Class 4\Traffic Class Successful Request\Counter Counts the number of successful requests for a specific traffic class. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Traffic Class 3\Counter Counts the number of events for a specific traffic class. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Traffic Class 2\Traffic Class Successful Request\Counter Counts the number of successful requests for a specific traffic class. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Traffic Class 1\Counter Counts the number of events for a specific traffic class. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Traffic Class 2\Counter Counts the number of events for a specific traffic class. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Counter Counts the number of events for all traffic classes. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Negotiated Traffic Class Presence\Negotiated Traffic Class 4\ Counter Counts the number of negotiations for a specific traffic class. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Negotiated Traffic Class Presence\Negotiated Traffic Class 3\ Data Volume Addition\Sum Counts the data volume sent uplink and downlink for a specific delay class. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Requested Traffic Class Presence\Requested Traffic Class 2\ Counter Counts the number of requests for a specific traffic class. >=SG7 1Day/24h/ 30min Table 4 SGSN SG6 combined ccma (Cont. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Requested Traffic Class Presence\Requested Traffic Class 4\ Counter Counts the number of requests for a specific traffic class. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Negotiated Traffic Class Presence\Negotiated Traffic Class 2\ Counter Counts the number of negotiations for a specific traffic class.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time Class CCMA counter Explanation SGSN Report\I-HSPA\Traffic Class Presence\Negotiated Traffic Class Presence\Negotiated Traffic Class 1\ Data Volume Addition\Sum Counts the data volume sent uplink and downlink for a specific delay class.) DN05148836 Issue 2-2 Id:0900d805809551ce 81 . >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Requested Traffic Class Presence\Counter Counts the number of requests for all traffic classes. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Requested Traffic Class Presence\Requested Traffic Class 3\ Counter Counts the number of requests for a specific traffic class. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Negotiated Traffic Class Presence\Negotiated Traffic Class 4\ Data Volume Addition\Sum Counts the data volume sent uplink and downlink for a specific delay class. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Negotiated Traffic Class Presence\Negotiated Traffic Class 3\ Counter Counts the number of negotiations for a specific traffic class. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Negotiated Traffic Class Presence\Negotiated Traffic Class 2\ Data Volume Addition\Sum Counts the data volume sent uplink and downlink for a specific delay class. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Traffic Class Presence\Requested Traffic Class Presence\Requested Traffic Class 1\ Counter Counts the number of requests for a specific traffic class. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Data Volume Available\APN Vector\Uplink Data Uplink\Sum Uplink Counts the data volume uplink for each APN. >=SG7 1Day/24h/ 30min Table 4 82 SGSN SG6 combined ccma (Cont. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Data Volume Available\APN Vector\Uplink Data Downlink\Sum Downlink Counts the data volume downlink for each APN. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 0\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC.. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 1\Counter Counts all events for specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 0\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 0\Error Cause Vector\Counter Counts all specific TREC events for each Error cause code.) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Data Volume Available\LAC Vector\RAC Vector\Sac Id\Sac Id Vector\Uplink Data Volume\ Sum Uplink Counts the data volume uplink for each SAC for each RAC under a certain LAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Data Volume Available\LAC Vector\RAC Vector\SAC Vector\Downlink Data Volume\Sum Downlink Counts the data volume downlink for each SAC for each RAC under the certain LAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 0\Counter Counts all events for specific TREC.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time Class CCMA counter Explanation SGSN Report\I-HSPA\Data Volume Available\LAC Vector\RAC Vector\SAC Vector\Uplink Data Volume\Sum Uplink Counts the data volume uplink for each SAC for each RAC under the certain LAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Data Volume Available\LAC Vector\Uplink Data Volume\Sum Uplink Counts the data volume uplink for each LAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Data Volume Available\LAC Vector\RAC Vector\Sac Id\Sac Id Vector\Counter Counts the data volume uplink/downlink for each SAC for each RAC under a certain LAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Data Volume Available\LAC Vector\RAC Vector\Sac Id\Sac Id Vector\Downlink Data Volume\ Sum Downlink Counts the data volume downlink for each SAC for each RAC under a certain LAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Data Volume Available\LAC Vector\Downlink Data Volume\Sum Downlink Counts the data volume downlink for each LAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Data Volume Available\LAC Vector\RAC Vector\ Downlink Data Volume\Sum Downlink Counts the data volume downlink for each RAC under the certain LAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Data Volume Available\LAC Vector\RAC Vector\Uplink Data Volume\Sum Uplink Counts the data volume uplink for each RAC under the certain LAC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 2\Error Cause Vector\Counter Counts all specific TREC events for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 4\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC.) DN05148836 Issue 2-2 Id:0900d805809551ce 83 . >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 5\Counter Counts all events for specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 1\Error Cause Vector\Counter Counts all specific TREC events for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 6\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 2\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 2\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 3\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 3\Error Cause Vector\Counter Counts all specific TREC events for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 3\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 5\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 5\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG7 1Day/24h/ 30min Table 4 SGSN SG6 combined ccma (Cont. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 4\Error Cause Vector\Counter Counts all specific TREC events for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 6\Counter Counts all events for specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 4\Counter Counts all events for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 5\Error Cause Vector\Counter Counts all specific TREC events for each Error cause code.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time Class CCMA counter Explanation SGSN Report\I-HSPA\TREC 1\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 2\Counter Counts all events for specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 3\Counter Counts all events for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 1\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 4\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 9\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\ Roaming Status\Successful\Network Operators Successful Vector\Counter Counts successful roaming attaches for each operator.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time Class CCMA counter Explanation SGSN Report\I-HSPA\TREC 6\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\ Roaming Status\Unsuccessful\Network Operators Unsuccessful Vector\Counter Counts unsuccessful roaming attaches for each operator. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 8\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Detaches\ Roaming Status\Network Operators Attempted Vector\Counter Counts unsuccessful/successful roaming detaches for each operator. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 6\Error Cause Vector\Counter Counts all specific TREC events for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 9\Error Cause Vector\Counter Counts all specific TREC events for each Error cause code. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 7\Error Cause Vector\Counter Counts all specific TREC events for each Error cause code.) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\ Roaming Status\Unsuccessful\Network Operators Unsuccessful Vector\Error Cause Vector\Counter Counts error causes for unsuccessful roaming attaches for each operator. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 9\Counter Counts all events for specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 7\Counter Counts all events for specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 8\Counter Counts all events for a specific TREC. >=SG7 1Day/24h/ 30min Table 4 84 SGSN SG6 combined ccma (Cont. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 7\Data Volume Up\Sum Uplink Counts the data volume sent uplink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Attaches\ Roaming Status\Network Operators Attempted Vector\Counter Counts unsuccessful/successful roaming attaches for each operator. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 9\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 8\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 7\Data Volume Down\Sum Downlink Counts the data volume sent downlink for a specific TREC. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\TREC 8\Error Cause Vector\Counter Counts all specific TREC events for each Error cause code. >=SG7 1Day/24h/ 30min Table 4 SGSN SG6 combined ccma (Cont. tors Attempted Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. vations\Roaming Status\Successful\ Network Operators Successful Vector\ Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.) DN05148836 Issue 2-2 Id:0900d805809551ce 85 .Counts error causes for unsuccessful roaming PDP context activations. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Detaches\ Roaming Status\Unsuccessful\Network Operators Vector\Error Cause Vector\ Counter Counts error causes for unsuccessful roaming detaches for each operator.Counts error causes for roaming PDP vations\Roaming Status\Network Opera.Counts unsuccessful roaming PDP context activations for each operator.Counts successful roaming PDP context activations. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time Class CCMA counter Explanation SGSN Report\I-HSPA\Detaches\ Roaming Status\Successful\Network Operators Vector\Counter Counts successful roaming detaches for each operator.context activations for each operator. tors Attempted Vector\Mobile Type Existence\Mobile Phone Vector\Error Cause Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\Detaches\ Roaming Status\Unsuccessful\Network Operators Vector\Counter Counts unsuccessful roaming detaches for each operator.Counts successful roaming PDP context activations for each operator. tors Attempted Vector\Mobile Type Existence\Mobile Phone Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. vations\Roaming Status\Unsuccessful\ Unsuccessful Network Operators Vector\ Error Cause Vector\Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti.context activations for each operator for certain mobile type.Counts mobile types for roaming PDP vations\Roaming Status\Network Opera.PDP context activations for each operator. tors Attempted Vector\Mobile Type Existence\Mobile Type Existence Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. vations\Roaming Status\Successful\ Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\Roaming Status\Counter Counts unsuccessful/successful roaming PDP context deactivations.Counts mobile phone types for roaming vations\Roaming Status\Network Opera.Counts unsuccessful/successful roaming vations\Roaming Status\Network Opera. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\Roaming Status\Network Attempted Vector\Counter Counts unsuccessful/successful roaming PDP context deactivations for each operator.PDP context activations for each operator. vations\Roaming Status\Unsuccessful\ Unsuccessful Network Operators Vector\ Counter >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Acti. >=SG8 1Day/24h Table 4 SGSN SG6 combined ccma (Cont. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Counter Counts the number of Mobility Management Reports. For example. >=SG8 1Day/24h SGSN IPPU GTP Report\Physical Ippu Vector\Data Amount Uplink\Sum UL Counts data amount transferred uplink through each physical IPPU. >=SG8 1Day/24h \SGSN IPPU GTP Report\Physical Ippu Vector\Discarded Packets\Sum Discarded Packets Counts amount of discarded data packets for each physical IPPU. in which LAC and Cell are combined. >=SG8 1Day/24h \SGSN IPPU GTP Report\Physical Ippu Vector\Whole Packet Amount\Sum Packets Counts amount of data packets transferred through each physical IPPU. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\Roaming Status\Unsuccessful\Unsuccessful Network Operator Vector\Counter Counts unsuccessful roaming PDP context deactivations for each operator. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\Roaming Status\Unsuccessful\Unsuccessful Network Operator Vector\Error Cause Vector\Counter Counts error causes for unsuccessful roaming PDP context deactivations for each operator. The following counters belong to SG6 3G clear code matrix Explanation SGSN version Time CCMA counter SGSN 3G Report\Counter Counts the number of Reports.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time Class CCMA counter Explanation SGSN Report\I-HSPA\PDP Context Deactivations\Roaming Status\Unsuccessful\Counter Counts unsuccessful roaming PDP context deactivations. >=SG8 1Day/24h \SGSN IPPU GTP Report\Physical Ippu Vector\Counter Counts the number of GTPs for each physical IPPU. if LAC is 003h and Cell is 001h. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\Roaming Status\Successful\Successful Network Operator Vector\ Counter Counts successful roaming PDP context deactivations for each operator. Cell ID is 0x30001h. >=SG6 1Day/24h/3 0min Table 5 86 Class SG6 3G CCMA Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG7 1Day/24h/ 30min SGSN IPPU GTP Report\Physical Ippu Vector\Whole Data Amount\Sum Counts total data amount transferred through each Physical IPPU. >=SG7 1Day/24h/ 30min SGSN Report\I-HSPA\PDP Context Deactivations\Roaming Status\Successful\Counter Counts successful roaming PDP context deactivations. >=SG8 1Day/24h SGSN IPPU GTP Report\Physical Ippu Vector\Data Amount Downlink\Sum DL Counts data amount transferred downlink through each physical IPPU.) *) Cell ID is a unique number. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Unsuccessful\Network Operators Unsuccessful Vector\Error Cause Vector\Counter Counts the number of error causes of the unsuccessful attaches for each operator. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\LAC Vector\Counter Counts all successful/unsuccessful attaches for each LAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Unsuccessful\LAC Vector\Counter Counts all unsuccessful attaches for each LAC.) DN05148836 Issue 2-2 Id:0900d805809551ce 87 . >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Unsuccessful\Network Operators Unsuccessful Vector\Counter Counts the number of unsuccessful attach attempts for each operator. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Successful\Network Operators Successful Vector\Counter Counts the number of successful attaches for each operator. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Successful\Counter Counts the number of successful attaches. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\LAC Vector\Error Cause Vector\Counter Counts all successful/unsuccessful attaches for each LAC for each Error cause code. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Unsuccessful\Mobile Type Vector\Error Cause Vector\Counter Counts all unsuccessful attaches for each Error cause code for certain mobile phone type. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Mobile Type Vector\ Counter Counts all successful/unsuccessful >=SG6 attaches for each mobile phone type.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time Class CCMA counter Explanation SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Counter. >=SG6 1Day/24h/3 0min Table 5 SG6 3G CCMA (Cont. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Error Cause Vector\ Counter Counts all successful/unsuccessful attaches for each Error cause code. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Network Operators Attempted Vector\Counter Counts the number of successful/unsuccessful attaches for each operator. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Unsuccessful\LAC Vector\Error Cause Vector\Counter Counts all unsuccessful attaches for >=SG6 each LAC for each Error cause code. 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Mobile Type Vector\ Error Cause Vector\Counter Counts all successful/unsuccessful attaches for each Error cause code for certain mobile phone type. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Unsuccessful\Counter Counts the number of unsuccessful attaches. 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Unsuccessful\Mobile Type Vector\Counter Counts all unsuccessful attaches for each mobile phone type. Counts the number of successful and unsuccessful attaches. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Detaches\Counter Counts the number of successful and unsuccessful attaches. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Roaming Status\ Unsuccessful\LAC Vector\RAC Vector\Error Cause Vector\Counter Counts all unsuccessful roaming attaches for each RAC of a specific LAC for each Error cause. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Roaming Status\LAC Vector\RAC Vector\Counter Counts all successful/unsuccessful roaming attaches for each RAC under a specific LAC.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time Class CCMA counter Explanation SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Roaming Status\ Counter Counts all successful/unsuccessful roaming attaches. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Roaming Status\ Unsuccessful\LAC Vector\RAC Vector\ Counter Counts all unsuccessful roaming attaches for each RAC under a specific LAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Roaming Status\ Unsuccessful\LAC Vector\Counter Counts all unsuccessful roaming attaches for each LAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Manage. 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Detaches\Unsuccessful\ Network Operators Unsuccessful Vector\ Counter Counts the number of unsuccessful detach attempts for each operator. 1Day/24h/3 0min Table 5 88 >=SG6 SG6 3G CCMA (Cont. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Roaming Status\LAC Vector\RAC Vector\Error Cause Vector\ Counter Counts all successful/unsuccessful roaming attaches for each RAC of a specific LAC for each Error cause. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Roaming Status\LAC Vector\Counter Counts all successful/unsuccessful roaming attaches for each LAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Roaming Status\ Unsuccessful\Counter Counts all unsuccessful roaming attaches. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Attaches\Roaming Status\Error Cause Vector\Counter Counts all successful/unsuccessful roaming attaches for each Error cause code. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Detaches\Unsuccessful\LAC Vector\Counter Counts all unsuccessful detaches for each LAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Detaches\Unsuccessful\LAC Vector\Error Cause Vector\Counter Counts all unsuccessful detaches for >=SG6 each LAC for each Error cause code.Counts the number of unsuccessful ment Reports\Detaches\Unsuccessful\Counter detaches.) Id:0900d805809551ce DN05148836 Issue 2-2 . 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Detaches\LAC Vector\Counter Counts all successful/unsuccessful detaches for each LAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\RA Updates\Unsuccessful\RAC Vector\Error Cause Vector\Counter Counts all unsuccessful RA Updates for each RAC for each error cause code. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\RA Updates\Unsuccessful\Error Cause Vector\Counter Counts all unsuccessful RA Updates for each error cause code. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Detaches\Error Cause Vector\ Counter Counts all successful/unsuccessful >=SG6 detaches for each Error cause code. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Detaches\Successful\Counter Counts the number of successful detaches. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\RA Updates\Unsuccessful\RA Update Type Vector\Counter Counts all unsuccessful RA update attempts for each RA update type. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\RA Updates\Unsuccessful\RAC Vector\Counter Counts all unsuccessful RA Updates for each RAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\RA Updates\Unsuccessful\RA Update Type Vector\Error Cause Vector\ Counter Counts the number of error causes of the RA updates for each RA update type. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Detaches\LAC Vector\Error Cause Vector\Counter Counts all successful/unsuccessful detaches for each LAC for each Error cause code.) DN05148836 Issue 2-2 Id:0900d805809551ce 89 . >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Detaches\Network Operators Attempted Vector\Counter Counts the number of successful/unsuccessful detaches for each operator. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\RA Updates\Unsuccessful\ Counter Counts the number of unsuccessful RA Updates.Counts all successful and unsucment Reports\RA Updates\Error Cause Vector\ cessful RA Updates for each Error cause code.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time Class CCMA counter Explanation SGSN 3G Report\SGSN 3G Mobility Management Reports\Detaches\Unsuccessful\ Network Operators Unsuccessful Vector\Error Cause Vector\Counter Counts the number of error causes of the unsuccessful detaches for each operator. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\RA Updates\Counter Counts the number of successful and unsuccessful RA Updates. Counter Table 5 SG6 3G CCMA (Cont. >=SG6 1Day/24h/3 0min >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Manage. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\Detaches\Successful\Network Operators Successful Vector\Counter Counts the number of successful detaches for each operator. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\RA Updates\RA Update Type Vector\Counter Counts all successful/unsuccessful RA Update attempts for each RA Update Types.Context Activations for each SAC for each Error cause code.Context Activations for each SAC.Context Activations for each mobile phone type.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time Class CCMA counter Explanation SGSN 3G Report\SGSN 3G Mobility Management Reports\RA Updates\RAC vector\ Counter Counts all successful/unsuccessful RA Updates for each RAC. cessful\SAC Vector\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.PDP Context Activation attempts for each operator. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\RA Updates\RAC vector\Error Cause Vector\Counter Counts all successful/unsuccessful RA Updates for each RAC for each Error cause code. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.PDP Context Activations for each APN.PDP Context Activations.Counts the number of error causes ment Reports\PDP Context Activations\Unsuc.) Id:0900d805809551ce DN05148836 Issue 2-2 . cessful\Network Operators Unsuccessful Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. cessful\APN Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. cessful\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all unsuccessful PDP ment Reports\PDP Context Activations\Unsuc.Counts the number of unsuccessful ment Reports\PDP Context Activations\Unsuc.Counts the number of successful and unsuccessful PDP Context Actiment Reports\PDP Context Activations\ vations. SGSN 3G Report\SGSN 3G Session Management Reports\PDP Context Activations\Unsuccessful\Mobile Type Vector\Error Cause Vector\Counter Table 5 90 SG6 3G CCMA (Cont.Counts all unsuccessful PDP ment Reports\PDP Context Activations\Unsuc.of the unsuccessful PDP Context Activations for each operator.Counts the number of unsuccessful ment Reports\PDP Context Activations\Unsuc.Counts all unsuccessful PDP ment Reports\PDP Context Activations\Unsuc. Counter 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. cessful\SAC Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts the number of unsuccessful ment Reports\PDP Context Activations\Unsuc.Counts the number of Session Manment Reports\Counter agement Reports. cessful\Mobile Type Vector\Counter >=SG6 1Day/24h/3 0min Counts all unsuccessful PDP Context Activations for each Error cause code for certain mobile phone type. cessful\Network Operators Unsuccessful Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. >=SG6 1Day/24h/3 0min >=SG6 1Day/24h/3 0min >=SG6 SGSN 3G Report\SGSN 3G Session Manage. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Mobility Management Reports\RA Updates\RA Update Type Vector\Error Cause Vector\Counter Counts the number of error causes of the RA Updates for each RA Update Types. Counts all successful/unsuccessful PDP Context Activations for each ment Reports\PDP Context Activations\SAC SAC for each Error cause code.Counts all successful/unsuccessful PDP Context Activations for each ment Reports\PDP Context Activations\Error Error cause code.Counts all successful/unsuccessful ment Reports\PDP Context Activations\Mobile PDP Context Activations for each mobile phone type. Type Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time SGSN 3G Report\SGSN 3G Session Manage.Counts all successful/unsuccessful PDP Context Activations for each ment Reports\PDP Context Activations\SAC SAC.Counts the number of the successful PDP Context Activations for each ment Reports\PDP Context Activations\Successful\Network Operators Successful Vector\ operator. Type Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all successful/unsuccessful ment Reports\PDP Context Activations\Mobile attaches for each Error cause code for certain mobile phone type.Counts the number of successful/unsuccessful PDP Context Actiment Reports\PDP Context Activations\APN vations for each APN. Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts the number of the successful/unsuccessful PDP Context Actiment Reports\PDP Context Activations\ Network Operators Attempted Vector\Counter vations for each operator. Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min Table 5 SG6 3G CCMA (Cont. Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Management Reports\PDP Context Activations\ Network Operators Attempted Vector\Mobile Phone Existence\Mobile Phone Vector\ Counter Counts the number of successful/unsuccessful PDP Context activations of the mobile phone types for a certain operator. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts the number of successful PDP Context Activations ment Reports\PDP Context Activations\Successful\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all successful/unsuccessful PDP Context Activations error ment Reports\PDP Context Activations\APN causes for for each APN. >=SG6 1Day/24h/3 0min CCMA counter Explanation Class SGSN 3G Report\SGSN 3G Session Management Reports\PDP Context Activations\ Network Operators Attempted Vector\Mobile Phone Existence\Counter Mobile Phones Counts the number of successful/unsuccessful PDP Context activations of the all mobile phones for a certain operator. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Management Reports\PDP Context Activations\ Network Operators Attempted Vector\Mobile Phone Existence\Mobile Phone Vector\Error Cause Vector\Counter Counts the number of successful/unsuccessful PDP Context activations of the mobile types for a certain operator.) DN05148836 Issue 2-2 Id:0900d805809551ce 91 . Counts all unsuccessful roaming attaches. 0\SAC Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all successful/unsuccessful PDP Context Activations for each ment Reports\PDP Context Activations\APN SAC for a certain APN.Counts all unsuccessful roaming attaches for each Error cause code. Vector\SAC Vector\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 1\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC.Counts all successful/unsuccessful roaming attaches for each Error ment Reports\PDP Context Activations\ cause code.Counts all successful/unsuccessful roaming attaches ment Reports\PDP Context Activations\ Roaming Status\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. Vector\Mobile Type Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all PDP Context Activations ment Reports\PDP Context Activations\TREC for specific TREC. Roaming Status\Unsuccessful\Error Cause Vector\Mobile Type Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all unsuccessful roaming attaches for each Error cause code ment Reports\PDP Context Activations\ for each Mobile phone types. 1\APN Vector\Counter >=SG6 1Day/24h/3 0min CCMA counter Table 5 92 Explanation Class SG6 3G CCMA (Cont.Counts all PDP Context Activations ment Reports\PDP Context Activations\TREC for specific TREC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each APN. Vector\SAC Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time SGSN 3G Report\SGSN 3G Session Manage. 0\SAC Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all successful/unsuccessful PDP Context Activations for each ment Reports\PDP Context Activations\APN APN for each Mobile phone type.Counts all successful/unsuccessful PDP Context Activations error ment Reports\PDP Context Activations\APN causes for each SAC for each APN. Roaming Status\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\PDP Context Activations\ Roaming Status\Unsuccessful\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\PDP Context Activations\ Roaming Status\Unsuccessful\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each APN. 0\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC.) Id:0900d805809551ce DN05148836 Issue 2-2 . 0\APN Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each APN. 2\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all PDP Context Activations ment Reports\PDP Context Activations\TREC for specific TREC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC.Counts all PDP Context Activations ment Reports\PDP Context Activations\TREC for specific TREC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC. 1\SAC Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 3\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 4\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time SGSN 3G Report\SGSN 3G Session Manage. 1\SAC Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 4\SAC Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 3\SAC Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each APN.Counts all PDP Context Activations ment Reports\PDP Context Activations\TREC for specific TREC. 3\SAC Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each APN. 2\APN Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC. 3\APN Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 5\Counter >=SG6 1Day/24h/3 0min CCMA counter Table 5 Explanation Class SG6 3G CCMA (Cont.Counts all PDP Context Activations ment Reports\PDP Context Activations\TREC for specific TREC. 2\SAC Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC. 4\SAC Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 4\APN Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC.) DN05148836 Issue 2-2 Id:0900d805809551ce 93 . 2\SAC Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC. Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC.) Id:0900d805809551ce DN05148836 Issue 2-2 . 5\SAC Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 8\APN Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 8\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 7\APN Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC. 5\APN Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 7\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 7\SAC Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC. 6\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 6\SAC Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 7\SAC Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each APN.Counts all PDP Context Activations ment Reports\PDP Context Activations\TREC for specific TREC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each APN.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC.Counts all PDP Context Activations ment Reports\PDP Context Activations\TREC for specific TREC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC.Counts all PDP Context Activations ment Reports\PDP Context Activations\TREC for specific TREC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each APN.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time SGSN 3G Report\SGSN 3G Session Manage. 5\SAC Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 8\SAC Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 8\SAC Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min CCMA counter Table 5 94 Explanation Class SG6 3G CCMA (Cont. 6\SAC Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC. 6\APN Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each APN. Counts the number of error causes of the unsuccessful PDP Context ment Reports\PDP Context Deactivations\ Unsuccessful\Network Operators Unsuccess.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC.Counts all successful/unsuccessful ment Reports\PDP Context Deactivations\SAC PDP Context Deactivations for each SAC.Counts the number of successful ment Reports\PDP Context Deactivations\Suc.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each APN.Counts the number of unsuccessful PDP Context Deactivations attempts ment Reports\PDP Context Deactivations\ Unsuccessful\Network Operators Unsuccess.Counts all PDP Context Activations ment Reports\PDP Context Activations\TREC for specific TREC. 9\SAC Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all unsuccessful PDP Context Deactivations for each SAC.for each operator ful Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 9\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 9\SAC Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all successful/unsuccessful PDP Context Deactivations for each ment Reports\PDP Context Deactivations\ Error cause code. Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 9\APN Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ful Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all successful/unsuccessful ment Reports\PDP Context Deactivations\SAC PDP Context Deactivations for each SAC for each Error cause code.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time SGSN 3G Report\SGSN 3G Session Manage. cessful\Counter >=SG6 1Day/24h/3 0min CCMA counter Table 5 Explanation Class SG6 3G CCMA (Cont.Counts the number of unsuccessful PDP Context Deactivations ment Reports\PDP Context Deactivations\ Unsuccessful\Counter >=SG6 1Day/24h/3 0min >=SG6 SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC.Counts the number of successful and unsuccessful PDP Context ment Reports\PDP Context Deactivations\ Deactivations Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\PDP Context Deactivations\ Unsuccessful\SAC Vector\Counter 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Deactivations for each operator. Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.) DN05148836 Issue 2-2 Id:0900d805809551ce 95 .Counts all unsuccessful PDP Context Deactivations for each SAC ment Reports\PDP Context Deactivations\ Unsuccessful\SAC Vector\Error Cause Vector\ for each Error cause code.PDP Context Deactivations. Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\PDP Context Modifications\ Unsuccessful\Counter >=SG6 1Day/24h/3 0min >=SG6 SGSN 3G Report\SGSN 3G Session Manage. Counter Table 5 96 Class SG6 3G CCMA (Cont. Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 1Day/24h/3 0min >=SG6 SGSN 3G Report\SGSN 3G Session Manage.Counts all unsuccessful PDP Context Modifications for each SAC ment Reports\PDP Context Modifications\ Unsuccessful\SAC Vector\Error Cause Vector\ for each Error cause code.Counts the number of the successful ment Reports\PDP Context Deactivations\Suc. Vector\Counter >=SG6 1Day/24h/3 0min CCMA counter Explanation SGSN 3G Report\SGSN 3G Session Manage.Counts the number of successful and unsuccessful PDP Context Modment Reports\PDP Context Modifications\ ifications.Counts the data volume sent ment Reports\PDP Context Deactivations\APN downlink for a specific APN.Counts all successful/unsuccessful ment Reports\PDP Context Modifications\Error PDP Context Modifications for each Error cause code.Counts all unsuccessful PDP Context Modifications for each SAC. Vector\Mobile Types\Data Volume Downlink\ Sum Downlink >=SG6 1Day/24h/3 0min >=SG6 SGSN 3G Report\SGSN 3G Session Manage. Counter 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. Vector\Counter 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts the number of the successful/unsuccessful PDP Context Deacment Reports\PDP Context Deactivations\ Network Operators Attempted Vector\Counter tivations for each operator. Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all successful/unsuccessful ment Reports\PDP Context Deactivations\APN PDP Context Deactivations for each APN for each Mobile phone types.Counts all successful/unsuccessful ment Reports\PDP Context Modifications\SAC PDP Context Modifications for each SAC.PDP Context Deactivations for each cessful\Network Operators Successful Vector\ operator.Counts the number of unsuccessful PDP Context Modifications. Vector\Data Volume Downlink\Sum Downlink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. Vector\Data Volume Uplink\Sum Uplink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts the data volume sent uplink ment Reports\PDP Context Deactivations\APN for a specific APN for each Mobile Vector\Mobile Types\Data Volume Uplink\Sum phone types.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time >=SG6 1Day/24h/3 0min >=SG6 SGSN 3G Report\SGSN 3G Session Manage. Vector\Mobile Types\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. Uplink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.) Id:0900d805809551ce DN05148836 Issue 2-2 .Counts the data volume sent ment Reports\PDP Context Deactivations\APN downlink for a specific APN for each Mobile phone types.Counts the number of successment Reports\PDP Context Deactivations\APN ful/unsuccessful PDP Context Deactivations for each APN. ment Reports\PDP Context Modifications\ Unsuccessful\SAC Vector\Counter 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts the data volume sent uplink ment Reports\PDP Context Deactivations\APN for a specific APN. Counts all specific TREC events for each Error cause code. ment Reports\TREC 1\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\PDP Context Modifications\ Roaming Status\Unsuccessful\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all events for specific TREC.Counts all successful/unsuccessful ment Reports\PDP Context Modifications\SAC PDP Context Modifications for each SAC for each Error cause code. ment Reports\PDP Context Modifications\ Roaming Status\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all successful/unsuccessful roaming attaches. ment Reports\TREC 2\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts the data volume sent downlink for a specific TREC.Counts the data volume sent uplink for a specific TREC. Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts the data volume sent downlink for a specific TREC.Counts the data volume sent uplink for a specific TREC. ment Reports\TREC 2\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min CCMA counter Table 5 Explanation Class SG6 3G CCMA (Cont. ment Reports\TREC 0\Data Volume Down\ Sum Downlink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all unsuccessful roaming attaches for each Error cause code.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time SGSN 3G Report\SGSN 3G Session Manage.Counts all events for specific TREC. ment Reports\TREC 0\Data Volume Up\Sum Uplink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\TREC 2\Data Volume Down\ Sum Downlink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all unsuccessful roaming attaches. ment Reports\TREC 1\Data Volume Down\ Sum Downlink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\TREC 0\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.) DN05148836 Issue 2-2 Id:0900d805809551ce 97 .Counts the data volume sent downlink for a specific TREC.Counts all specific TREC events for each Error cause code.Counts the data volume sent uplink for a specific TREC. ment Reports\PDP Context Modifications\ Roaming Status\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\TREC 1\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC events for each Error cause code.Counts all events for specific TREC. ment Reports\TREC 1\Data Volume Up\Sum Uplink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\TREC 0\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\TREC 2\Data Volume Up\Sum Uplink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\TREC 7\Counter >=SG6 1Day/24h/3 0min CCMA counter Table 5 98 Explanation Class SG6 3G CCMA (Cont. ment Reports\TREC 5\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts the data volume sent downlink for a specific TREC.Counts the data volume sent downlink for a specific TREC. ment Reports\TREC 5\Data Volume Up\Sum Uplink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC events for each Error cause code.Counts all events for a specific ment Reports\TREC 4\Counter TREC. ment Reports\TREC 6\Data Volume Up\Sum Uplink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC events for each Error cause code. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts the data volume sent uplink for a specific TREC. ment Reports\TREC 5\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\TREC 6\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all events for specific TREC. ment Reports\TREC 5\Data Volume Down\ Sum Downlink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts the data volume sent uplink for a specific TREC.Counts all specific TREC events for each Error cause code. ment Reports\TREC 4\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\TREC 4\Data Volume Up\Sum Uplink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all events for specific TREC.Counts all events for specific TREC.Counts the data volume sent downlink for a specific TREC. ment Reports\TREC 6\Data Volume Down\ Sum Downlink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\TREC 3\Data Volume Down\ Sum Downlink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all events for a specific ment Reports\TREC 3\Counter TREC.Counts the data volume sent uplink for a specific TREC. ment Reports\TREC 3\Data Volume Up\Sum Uplink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.) Id:0900d805809551ce DN05148836 Issue 2-2 . ment Reports\TREC 6\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts the data volume sent uplink for a specific TREC.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time SGSN 3G Report\SGSN 3G Session Manage. ment Reports\TREC 4\Data Volume Down\ Sum Downlink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\TREC 3\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts the data volume sent downlink for a specific TREC.Counts all specific TREC events for each Error cause code. Counts all specific TREC events for each Error cause code.Counts all events for specific TREC. ment Reports\TREC 7\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts the data volume sent downlink for a specific TREC. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MT SMS Deliveries\Error Cause Vector\Counter Counts all unsuccessful MT-SMS deliveries for each Error Cause code. ment Reports\TREC 8\Data Volume Up\Sum Uplink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\TREC 9\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\Counter Counts the number of successful and unsuccessful SMS deliveries. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MT SMS Deliveries\Unsuccessful\SAC Vector\Counter Counts all unsuccessful MT-SMS deliveries for each SAC. ment Reports\TREC 7\Data Volume Up\Sum Uplink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\TREC 9\Data Volume Up\Sum Uplink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts the data volume sent uplink for a specific TREC. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time SGSN 3G Report\SGSN 3G Session Manage. ment Reports\TREC 8\Data Volume Down\ Sum Downlink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. ment Reports\TREC 7\Data Volume Down\ Sum Downlink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MT SMS Deliveries\Unsuccessful\SAC Vector\Error Cause Vector\Counter Counts all unsuccessful MT-SMS deliveries for each SAC for each Error Cause code. >=SG6 1Day/24h/3 0min CCMA counter Table 5 Explanation Class SG6 3G CCMA (Cont. ment Reports\TREC 9\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC events for each Error cause code.Counts the data volume sent downlink for a specific TREC.) DN05148836 Issue 2-2 Id:0900d805809551ce 99 .Counts the data volume sent uplink for a specific TREC. ment Reports\TREC 9\Data Volume Down\ Sum Downlink >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MT SMS Deliveries\Counter Counts the number of successful and unsuccessful MT SMS deliveries. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MT SMS Deliveries\Unsuccessful\Counter Counts the number of unsuccessful MT SMS deliveries.Counts the data volume sent uplink for a specific TREC.Counts all events for a specific ment Reports\TREC 8\Counter TREC. ment Reports\TREC 8\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts the data volume sent downlink for a specific TREC.Counts all specific TREC events for each Error cause code. ) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MO SMS Deliveries\Counter Counts the number of successful and unsuccessful MO SMS deliveries. >=SG6 1Day/24h/3 0min Table 5 100 SG6 3G CCMA (Cont. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Traffic Class 4\Traffic Class Successful Request\Counter Counts the number of successful requests for a specific traffic class. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MO SMS Deliveries\Unsuccessful\SAC Vector\Error Cause Vector\Counter Counts all unsuccessful MO-SMS deliveries for each SAC for each Error Cause code. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MO SMS Deliveries\SAC Vector\Counter Counts all successful/unsuccessful MO-SMS deliveries for each SAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MO SMS Deliveries\Error Cause Vector\Counter Counts all unsuccessful MO-SMS deliveries for each Error Cause code. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MT SMS Deliveries\SAC Vector\Error Cause Vector\ Counter Counts all successful/unsuccessful MT-SMS deliveries for each Error Cause code. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Counter Counts the number of events for all traffic classes. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MO SMS Deliveries\Unsuccessful\Counter Counts the number of unsuccessful MO SMS deliveries.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time Class CCMA counter Explanation SGSN 3G Report\SMS Deliveries\MT SMS Deliveries\SAC Vector\Counter Counts all successful/unsuccessful MT-SMS deliveries for each SAC for each Error Cause code. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MO SMS Deliveries\Unsuccessful\SAC Vector\Counter Counts all unsuccessful MO-SMS deliveries for each SAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Traffic Class 1\Counter Counts the number of events for a specific traffic class. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Traffic Class 3\Counter Counts the number of events for a specific traffic class. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MO SMS Deliveries\SAC Vector\Error Cause Vector\ Counter Counts all successful/unsuccessful MO-SMS deliveries for each SAC for each Error Cause code. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Traffic Class 2\Counter Counts the number of events for a specific traffic class. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Traffic Class 1\Traffic Class Successful Request\Counter Counts the number of successful requests for a specific traffic class. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Traffic Class 2\Traffic Class Successful Request\Counter Counts the number of successful requests for a specific traffic class. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Traffic Class 3\Traffic Class Successful Request\Counter Counts the number of successful requests for a specific traffic class. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Negotiated Traffic Class Presence\Negotiated Traffic Class 2\Data Volume Addition\Sum Counts the data volume sent uplink and downlink for a specific delay class. >=SG6 1Day/24h/3 0min SGSN 3G Report\Data Volume Available\LAC Vector\RAC Vector\SAC Vector\Uplink Data Volume\Sum Uplink Counts the data volume uplink for each SAC for each RAC under the certain LAC.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time Class CCMA counter Explanation SGSN 3G Report\Traffic Class Presence\ Negotiated Traffic Class Presence\Counter Counts the number of negotiations for all traffic classes. >=SG6 1Day/24h/3 0min Table 5 SG6 3G CCMA (Cont. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Requested Traffic Class Presence\Requested Traffic Class 2\Counter Counts the number of requests for a specific traffic class. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Negotiated Traffic Class Presence\Negotiated Traffic Class 2\Counter Counts the number of negotiations for a specific traffic class. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Negotiated Traffic Class Presence\Negotiated Traffic Class 1\Data Volume Addition\Sum Counts the data volume sent uplink and downlink for a specific delay class. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Requested Traffic Class Presence\Requested Traffic Class 3\Counter Counts the number of requests for a specific traffic class. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Negotiated Traffic Class Presence\Negotiated Traffic Class 4\Data Volume Addition\Sum Counts the data volume sent uplink and downlink for a specific delay class. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Negotiated Traffic Class Presence\Negotiated Traffic Class 3\Counter Counts the number of negotiations for a specific traffic class. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Negotiated Traffic Class Presence\Negotiated Traffic Class 4\Counter Counts the number of negotiations for a specific traffic class. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Negotiated Traffic Class Presence\Negotiated Traffic Class 1\Counter Counts the number of negotiations for a specific traffic class. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Requested Traffic Class Presence\Requested Traffic Class 1\Counter Counts the number of requests for a specific traffic class. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Negotiated Traffic Class Presence\Negotiated Traffic Class 3\Data Volume Addition\Sum Counts the data volume sent uplink and downlink for a specific delay class. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Requested Traffic Class Presence\Counter Counts the number of requests for all traffic classes. >=SG6 1Day/24h/3 0min SGSN 3G Report\Traffic Class Presence\ Requested Traffic Class Presence\Requested Traffic Class 4\Counter Counts the number of requests for a specific traffic class.) DN05148836 Issue 2-2 Id:0900d805809551ce 101 . >=SG6 1Day/24h/3 0min SGSN 3G Report\Data Volume Available\LAC Vector\RAC Vector\SAC Vector\Downlink Data Volume\Sum Downlink Counts the data volume downlink for each SAC for each RAC under the certain LAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\Data Volume Available\LAC Vector\RAC Vector\Downlink Data Volume\ Sum Downlink Counts the data volume downlink for each RAC under the certain LAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\Data Volume Available\LAC Vector\Downlink Data Volume\Sum Downlink Counts the data volume downlink for each LAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\Data Volume Available\APN Vector\Uplink Data Downlink\Sum Downlink Counts the data volume downlink for each APN. 0\Sac Id\Sac Id Vector\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all successful/unsuccessful PDP Context Activations error ment Reports\PDP Context Activations\APN causes for each SAC for each APN..Counts all successful/unsuccessful PDP Context Activations for each ment Reports\PDP Context Activations\APN SAC for certain APN. Vector\Sac Id\Sac Id Vector\Counter >=SG6 1Day/24h/3 0min >=SG6 SGSN 3G Report\SGSN 3G Session Manage..Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC.) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG6 1Day/24h/3 0min SGSN 3G Report\Data Volume Available\LAC Vector\Uplink Data Volume\Sum Uplink Counts the data volume uplink for each LAC.Counts all unsuccessful 3G PDP ment Reports\PDP Context Activations\Unsuc. 1\Sac Id\Sac Id Vector\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min Table 5 102 SG6 3G CCMA (Cont.Context Activations for each SAC. 1\Sac Id\Sac Id Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 0\Sac Id\Sac Id Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. Vector\Sac Id\Sac Id Vector\Error Cause Vector\Counter 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC. cessful\Sac Id\Sac Id Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 0\Sac Id\Sac Id Vector\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time Class CCMA counter Explanation SGSN 3G Report\Data Volume Available\LAC Vector\RAC Vector\Uplink Data Volume\Sum Uplink Counts the data volume uplink for each RAC under the certain LAC.Counts all unsuccessful 3G PDP ment Reports\PDP Context Activations\Unsuc.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC. cessful\Sac Id\Sac Id Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Context Activations for each Error Cause code. >=SG6 1Day/24h/3 0min SGSN 3G Report\Data Volume Available\APN Vector\Uplink Data Uplink\Sum Uplink Counts the data volume uplink for each APN.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 4\Sac Id\Sac Id Vector\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC. 5\Sac Id\Sac Id Vector\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time SGSN 3G Report\SGSN 3G Session Manage. 6\Sac Id\Sac Id Vector\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC. 2\Sac Id\Sac Id Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 3\Sac Id\Sac Id Vector\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.) DN05148836 Issue 2-2 Id:0900d805809551ce 103 .Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC. 2\Sac Id\Sac Id Vector\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 5\Sac Id\Sac Id Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 3\Sac Id\Sac Id Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 7\Sac Id\Sac Id Vector\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. 8\Sac Id\Sac Id Vector\Counter >=SG6 1Day/24h/3 0min CCMA counter Table 5 Explanation Class SG6 3G CCMA (Cont. 6\Sac Id\Sac Id Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC. 7\Sac Id\Sac Id Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC. 4\Sac Id\Sac Id Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC. Counts all unsuccessful 3G PDP Context Modifications for each Error ment Reports\PDP Context Modifications\ Cause code.Counts all successful/unsuccessful ment Reports\PDP Context Modifications\Sac 3G PDP Context Modifications for each Error Cause code.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each SAC. Sac Id Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all successful/unsuccessful ment Reports\PDP Context Activations\Sac Id\ 3G PDP Context Activations for each Error Cause code. ment Reports\PDP Context Deactivations\ Unsuccessful\Sac Id\Sac Id Vector\Counter 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. Id\Sac Id Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. Id\Sac Id Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min >=SG6 1Day/24h/3 0min CCMA counter Explanation SGSN 3G Report\SMS Deliveries\MT SMS Deliveries\Unsuccessful\Sac Id\Sac Id Vector\ Counter Table 5 104 Counts all unsuccessful MT-SMS deliveries for each SAC.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC. 9\Sac Id\Sac Id Vector\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all unsuccessful 3G PDP Context Deactivations for each SAC. Class SG6 3G CCMA (Cont. Id\Sac Id Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all specific TREC PDP ment Reports\PDP Context Activations\TREC Context Activations for each Error cause code for each SAC. Unsuccessful\Sac Id\Sac Id Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. Sac Id Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min >=SG6 SGSN 3G Report\SGSN 3G Session Manage.Counts all unsuccessful 3G PDP Context Modifications for each Sac ment Reports\PDP Context Modifications\ Unsuccessful\Sac Id\Sac Id Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage. Id\Sac Id Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all successful/unsuccessful ment Reports\PDP Context Modifications\Sac 3G PDP Context Modifications for each SAC.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time SGSN 3G Report\SGSN 3G Session Manage.Counts all successful/unsuccessful ment Reports\PDP Context Deactivations\Sac 3G PDP Context deactivations for each SAC. Unsuccessful\Sac Id\Sac Id Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all unsuccessful 3G PDP Context Deactivations for each Error ment Reports\PDP Context Deactivations\ Cause code. 9\Sac Id\Sac Id Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.) Id:0900d805809551ce DN05148836 Issue 2-2 . 8\Sac Id\Sac Id Vector\Error Cause Vector\ Counter >=SG6 1Day/24h/3 0min SGSN 3G Report\SGSN 3G Session Manage.Counts all successful/unsuccessful ment Reports\PDP Context Deactivations\Sac 3G PDP Context Deactivations for each Error Cause code.Counts all successful/unsuccessful ment Reports\PDP Context Activations\Sac Id\ 3G PDP Context Activations for each SAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MT SMS Deliveries\Sac Id\Sac Id Vector\Error Cause Vector\Counter Counts all successful/unsuccessful MT-SMS deliveries for each SAC for each Error Cause code. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MT SMS Deliveries\Sac Id\Sac Id Vector\Counter Counts all successful/unsuccessful MT-SMS deliveries for each SAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MO SMS Deliveries\Unsuccessful\Sac Id\Sac Id Vector\ Counter Counts all unsuccessful MO-SMS deliveries for each SAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MO SMS Deliveries\Sac Id\Sac Id Vector\Error Cause Vector\Counter Counts all successful/unsuccessful MO-SMS deliveries for each SAC for each Error Cause code. >=SG6 1Day/24h/3 0min SGSN 3G Report\Data Volume Available\LAC Vector\RAC Vector\Sac Id\Sac Id Vector\ Uplink Data Volume\Sum Uplink Counts the data volume uplink for each SAC for each RAC under a certain LAC.) DN05148836 Issue 2-2 Id:0900d805809551ce 105 . 1Day/24h/3 0min SGSN 3G Mobility Management Reports\ Attaches\Roaming Status\Successful\Network Operators Successful Vector\Counter Counts successful roaming attaches for each operator. >=SG6 1Day/24h/3 0min Table 5 SG6 3G CCMA (Cont. >=SG6 1Day/24h/3 0min SGSN 3G Report\Data Volume Available\LAC Vector\RAC Vector\Sac Id\Sac Id Vector\ Counter Counts the data volume uplink/downlink for each SAC for each RAC under a certain LAC. >=SG6 1Day/24h/3 0min SGSN 3G Mobility Management Reports\ Attaches\Roaming Status\Unsuccessful\ Network Operators Unsuccessful Vector\Error Cause Vector\Counter Counts error causes for unsuccess. >=SG6 1Day/24h/3 0min SGSN 3G Report\Data Volume Available\LAC Vector\RAC Vector\Sac Id\Sac Id Vector\ Downlink Data Volume\Sum Downlink Counts the data volume downlink for each SAC for each RAC under a certain LAC. >=SG6 1Day/24h/3 0min SGSN 3G Mobility Management Reports\ Detaches\Roaming Status\Network Operators Attempted Vector\Counter Counts roaming detaches for each operator. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MO SMS Deliveries\Sac Id\Sac Id Vector\Counter Counts all successful/unsuccessful MO-SMS deliveries for each SAC. >=SG6 1Day/24h/3 0min SGSN 3G Report\SMS Deliveries\MO SMS Deliveries\Unsuccessful\Sac Id\Sac Id Vector\ Error Cause Vector\Counter Counts all unsuccessful MO-SMS deliveries for each SAC for each Error Cause code. >=SG6 1Day/24h/3 0min SGSN 3G Mobility Management Reports\ Attaches\Roaming Status\Network Operators Attempted Vector\Counter Counts unsuccessful/successful roaming attaches for each operator.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time Class CCMA counter Explanation SGSN 3G Report\SMS Deliveries\MT SMS Deliveries\Unsuccessful\Sac Id\Sac Id Vector\ Error Cause Vector\Counter Counts all unsuccessful MT-SMS deliveries for each SAC for each Error Cause code.>=SG6 ful roaming attaches for each operator. >=SG6 1Day/24h/3 0min SGSN 3G Mobility Management Reports\ Attaches\Roaming Status\Unsuccessful\ Network Operators Unsuccessful Vector\ Counter Counts unsuccessful roaming attaches for each operator. 1Day/24h/3 0min SGSN 3G Session Management Reports\PDP Context Activations\Roaming Status\Network Operators Attempted Vector\Counter Counts unsuccessful/successful roaming PDP context activations for each operator.>=SG6 SGSN 3G Mobility Management Reports\ ful roaming detaches for each operaDetaches\Roaming Status\Unsuccessful\ Network Operators Vector\Error Cause Vector\ tor.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN version Time Class CCMA counter Explanation SGSN 3G Mobility Management Reports\ Detaches\Roaming Status\Successful\ Network Operators Vector\Counter Counts successful roaming detaches for each operator. 1Day/24h/3 0min SGSN 3G Session Management Reports\PDP Context Activations\Roaming Status\Successful\Counter Counts successful roaming PDP context activations.operator. >=SG6 1Day/24h/3 0min SGSN 3G Session Management Reports\PDP Counts mobile phone types for roaming PDP context activations for Context Activations\Roaming Status\Network Operators Attempted Vector\Mobile Type Exis.operator for certain mobile type. 1Day/24h/3 0min SGSN 3G Session Management Reports\PDP Context Activations\Roaming Status\Unsuccessful\Unsuccessful Network Operators Vector\Error Cause Vector\Counter Counts error causes for unsuccess. >=SG6 1Day/24h/3 0min SGSN 3G Session Management Reports\PDP Context Deactivations\Roaming Status\ Network Attempted Vector\Counter Counts unsuccessful/successful roaming PDP context deactivations for each operator. >=SG6 1Day/24h/3 0min SGSN 3G Session Management Reports\PDP Context Deactivations\Roaming Status\ Counter Counts unsuccessful/successful roaming PDP context deactivations. tence\Mobile Phone Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Session Management Reports\PDP Counts error causes for roaming PDP context activations for each Context Activations\Roaming Status\Network Operators Attempted Vector\Mobile Type Exis.each operator.) Id:0900d805809551ce DN05148836 Issue 2-2 . tence\Mobile Type Existence Counter >=SG6 1Day/24h/3 0min SGSN 3G Session Management Reports\PDP Counts mobile types for roaming PDP context activations for each Context Activations\Roaming Status\Network Operators Attempted Vector\Mobile Type Exis. Counter 1Day/24h/3 0min SGSN 3G Session Management Reports\PDP Context Activations\Roaming Status\Unsuccessful\Unsuccessful Network Operators Vector\Counter Counts unsuccessful roaming PDP >=SG6 context activations for each operator. tence\Mobile Phone Vector\Error Cause Vector\Counter >=SG6 1Day/24h/3 0min SGSN 3G Session Management Reports\PDP Context Activations\Roaming Status\Successful\Network Operators Successful Vector\ Counter Counts successful roaming PDP >=SG6 context activations for each operator.>=SG6 ful roaming PDP context activations. >=SG6 1Day/24h/3 0min SGSN 3G Mobility Management Reports\ Detaches\Roaming Status\Unsuccessful\ Network Operators Vector\Counter Counts unsuccessful roaming detaches for each operator. >=SG6 1Day/24h/3 0min Counts error causes for unsuccess. >=SG6 1Day/24h/3 0min Table 5 106 SG6 3G CCMA (Cont. MS originated IMSI detach. IMSI attach. MS originated GPRS/IMSI detach. see Sgsn_Rtt_Cause_Error_Cause. outgoing interSGSN attach. For detailed list of possible values. cessful\Unsuccessful Network Operator Vector\Counter 1Day/24h/3 0min >=SG6 1Day/24h/3 0min CCMA counter Explanation SGSN 3G Session Management Reports\PDP Counts unsuccessful roaming PDP Context Deactivations\Roaming Status\Unsuc. 1Day/24h/3 0min Table 5 SG6 3G CCMA (Cont.context deactivations.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN version Time >=SG6 1Day/24h/3 0min >=SG6 SGSN 3G Session Management Reports\PDP Counts unsuccessful roaming PDP Context Deactivations\Roaming Status\Unsuc. 0xFFFFFF00. MS originated GPRS detach. other possible values indicate a failure in the event. unspecified attach 2) Power-off detach. network requested GPRS detach. >=SG6 1Day/24h/3 0min SGSN 3G Session Management Reports\PDP Context Deactivations\Roaming Status\Successful\Successful Network Operator Vector\ Counter >=SG6 Counts successful roaming PDP context deactivations for each operator. 4) Mobile phone type is the mobile equipment (ME) model as Type Approval Code (TAC) extracted from subscriber's IMEI. unspecified detach 3) Error cause code is a numeric value which tells if the event was successful or not. There is one value for successful event. implicit GPRS detach. network requested GPRS/IMSI detach. cessful\Unsuccessful Network Operator Vector\Error Cause Vector\Counter Class SGSN 3G Session Management Reports\PDP Context Deactivations\Roaming Status\Successful\Counter Counts successful roaming PDP context deactivations.ful roaming PDP context deactivations for each operator.) Number Explanation 1) GPRS attach. TAC is the 6 first digits of IMEI Table 6 DN05148836 Issue 2-2 Footnotes used in table Counters of CCMA time classes Id:0900d805809551ce 107 . network requested IMSI detach. implicit GPRS/IMSI detach. combined GPRS/IMSI attach. cessful\Counter SGSN 3G Session Management Reports\PDP Counts error causes for unsuccessContext Deactivations\Roaming Status\Unsuc. outgoing inter-PAPU attach.context deactivations for each operator. ARP = 1 TREC 5 Guaranteed Bit Rate. ARP = 2 TREC 7 Guaranteed Bit Rate. Network requested PDP context activation 7) Context activation to another PAPU/SGSN. place the cursor on the graph title. Priority 4. type unspecified 6) Mobile requested PDP context activation. ARP = 2 TREC 4 Guaranteed Bit Rate. 108 Id:0900d805809551ce DN05148836 Issue 2-2 .Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Number Explanation 5) Routing area updates: • • • • • • • • • • • • • • Intra PAPU RA update Inter PAPU RA update Inter SGSN RA update Inter SGSN RA update with IMSI attach Intra PAPU RA update with IMSI attach Inter PAPU RA update with IMSI attach Intra PAPU combined RA/LA update Inter PAPU combined RA/A update Inter SGSN combined RA/LA update Periodic combined RA/LA update Periodic combined RA update Outgoing inter PAPU RA update (in old PAPU) Outgoing inter SGSN RA update (in old SGSN RA update. TC = Interactive. Network requested PDP context deactivation. A ToolTip appears with information about the graph contents. ARP = 2 TREC 1 Non-Guaranteed Bit Rate. The division of graphs into Categories and Sets facilitates fast access to the data. Priority 5. Priority 1. The contents of the predefined Graph Categories and some of the Graph Sets are given below. Priority 3. ARP = 3 Table 6 5. ARP (Alloc Retention Priority) = 1 TREC 8 Guaranteed Bit Rate. Priority 2. ARP = 3 TREC 3 Non-Guaranteed Bit Rate. TC = Interactive. TC = Streaming. HLR initiated PDP context modification 8) Mobile requested PDP context deactivation. ARP = 1 TREC 2 Non-Guaranteed Bit Rate. Each predefined Graph Set consists of a number of graphs. Priority 2. TC = Conversational. PDP context deactivation due to network status 9) TRECs are: TREC 9 Guaranteed Bit Rate. To access the contents information. ARP = 3 TREC 0 Non-Guaranteed Bit Rate. TC (Traffic Class) = Conversational. TC = Background. TC = Streaming.2 Footnotes used in table Counters of CCMA time classes (Cont. ARP = 3 TREC 6 Guaranteed Bit Rate. TC = Conversational.) Real-time graphs Nokia Siemens Networks supplies predefined Graph Categories and Sets with Traffica. TC = Interactive. Priority 6. TC = Streaming. The actual contents of the graphs are given in the Traffica user interface. Priority 1. Priority 4. GMC requested PDP context deactivation. Priority 3. 2. TRAF/Preconfigured Set Repository includes all predefined Graph sets. so you can access all graphs in all categories. When you select TRAF/Preconfigured Set Repository all predefined Graph sets are listed in the Graph sets list box. The events are: • • • • Attaches Detaches PDP Context Activations/Modifications/Deactivations MO/MT-SMS Deliveries TRAF SGSN SG Failure Per.1 Graph categories All Graph Categories consist of a number of Graph sets. The events are: • • • • TRAF SGSN SG Failures (1Day / 24h / 30 min) Attaches Detaches PDP Context Activations/Modifications/Deactivations MO/MT-SMS Deliveries These graphs show the number of unsuccessful events cumula. 5.These graphs show the percentage of unsuccessful events .>=SG3 tively for the time period. Both successful and unsuccessful events are counted.2. click with the right mouse button on the graph to open a popup menu and select Properties. 5. User Set Repository is reserved for users' own Graph Sets. For a description of all CCMA counters and classes see chapter Clear Code Matrix.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring To find out which part of the CCMA provides the data for the graph. which include a number of graphs.2 Graph sets The following tables outline each Graph Set and provides an explanation for each set: • • • • Graph Sets Graph Sets Graph Sets Graph Sets and explanations for 2G and explanations for 3G and explanations for I-HSPA and explanations for combined graphs (2G/3G/I-HSPA) Graph set Explanation SGSN Version TRAF SGSN SG Events (1Day / 24h / 30 min) These graphs show the number of different events cumulatively for the time period. The name of the Graph Set indicates to which Graph Category it belongs in predefined Graph Sets. The centages (1Day / 24h / 30 min) events are: • • • • Table 7 >=SG3 >=SG3 Attaches Detaches PDP Context Activations/Modifications/Deactivations MO/MT-SMS Deliveries Graph Sets and explanations for 2G DN05148836 Issue 2-2 Id:0900d805809551ce 109 . ) Id:0900d805809551ce DN05148836 Issue 2-2 .Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph set Explanation TRAF SGSN SG PDP Context Activations (1Day / 24h / 30 min) These graphs show the following statistics cumulatively for the time period: TRAF SGSN SG PDP Context Modifications (1Day / 24h / 30 min) These graphs show the following statistics cumulatively for the time period: TRAF SGSN SG PDP Context Deactivations (1Day / 24h / 30 min) These graphs show the following statistics cumulatively for the time period: TRAF SGSN SG MO SMS Deliveries (1Day / 24h / 30 min) These graphs show the following statistics cumulatively for the time period: TRAF SGSN SG MT SMS Deliveries (1 Day) These graphs show the following statistics cumulatively for the time period: • • • • • • • • • • • • • • • • • • • • • • • • • Table 7 110 SGSN Version >=SG3 Number of PDP Context Activations Error Cause codes of failed PDP Context Activations PDP Context Activations for each Cell Unsuccessful PDP Context Activations for each Cell PDP Context Activations Error Cause code distribution for each cell >=SG3 Number of PDP Context Modifications Error Cause codes of failed PDP Context Modifications PDP Context Modifications for each Cell Unsuccessful PDP Context Modifications for each Cell PDP Context Modifications Error Cause code distribution for each cell >=SG3 Number of PDP Context Deactivations Error Cause codes of failed PDP Context Deactivations PDP Context Deactivations for each Cell Unsuccessful PDP Context Deactivations for each Cell PDP Context Deactivations Error Cause code distribution for each cell >=SG3 Number of MO SMS Deliveries Error Cause codes of failed MO SMS Deliveries MO SMS Deliveries for each Cell Unsuccessful MO SMS Deliveries for each Cell MO SMS Deliveries Error Cause code distribution for each cell >=SG3 Number of MT SMS Deliveries Error Cause codes of failed MT SMS Deliveries MT SMS Deliveries for each Cell Unsuccessful MT SMS Deliveries for each Cell MT SMS Deliveries Error Cause code distribution for each cell Graph Sets and explanations for 2G (Cont. and separate for each PDP Context Activations types.) DN05148836 Issue 2-2 Id:0900d805809551ce 111 . while the analysis of the Program block and the Internal situation will get more detailed explanation for the fault.Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph set Explanation TRAF SGSN SG Attaches (1Day / 24h / 30 min) These graphs show the following statistics cumulatively for the time period: • • • • • TRAF SGSN SG Detaches (1Day / 24h / 30 min) TRAF SGSN SG RA Updates (1Day / 24h / 30 min) • TRAF SGSN SG Mobile Types (1Day / 24h / 30 min) • • • TRAF SGSN SG PDP Context Activations Troubleshooting (1 Day / 24h / 30 min) >=SG3 Number of RA Updates Error Cause codes of failed RA updates RA updates (incoming and outgoing) for each RAC Unsuccessful RA updates (incoming and outgoing) for each RAC RA updates Error Cause distribution for each RAC These graphs show the following statistics cumulatively for the time period: • • >=SG3 Number of Detaches Error Cause codes of failed Detaches Detaches for each LAC Unsuccessful Detaches for each LAC Detaches Error Cause code distribution for each LAC These graphs show the following statistics cumulatively for the time period: • • • • >=SG3 Number of Attaches Error Cause codes of failed Attaches Attaches for each LAC Unsuccessful Attaches for each LAC Attaches Error Cause code distribution for each LAC These graphs show the following statistics cumulatively for the time period: • • • • • Real-time monitoring >=SG3 Attaches for each Mobile phone type Attaches' Error Cause code distribution for each mobile phone type PDP Context Activations for each Mobile phone type PDP Context Activations Error Cause code distribution for each Mobile phone type Unsuccessful PDP Context Activations for each Mobile phone type >=SG3 This graph set shows the total number of unsuccessful PDP Context Activations and the percentages of PDP Context Activations types for the unsuccessful activation. Table 7 Graph Sets and explanations for 2G (Cont. The These graphs show the program blocks that have set the error cause and the internal situation for each case. This graph set is assigned to troubleshooting. The graph set shows the error causes for PDP Context Activations. The error cause will provide a general information. >=SG3 This graph set is assigned to monitoring the load on physical PAPU and troubleshooting. NOTE: The capacity window is available only for solutions since SG4. the load for each APN. The graph set shows the error causes PDP Context Modification.) Id:0900d805809551ce DN05148836 Issue 2-2 . The graph set shows the error causes for SMS sending. TRAF SGSN SG PDP Context Activations Load in APNs (1 Day / 24h / 30 min) This graph set shows the number of PDP Context Activations. TRAF SGSN SG PDP Context Activations Load in Logical Papus (1 Day / 24h / 30 min) This graph set shows the number of PDP Context Activations.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph set Explanation TRAF SGSN SG PDP Context Modification Troubleshooting (1 Day / 24h / 30 min) This graph set shows the number of unsuccessful PDP Context Modifications and the percentages of unsuccessful PDP Context Modification types. The These graphs show the program blocks that have set the error cause and the internal situation for each case. >=SG3 This graph set is assigned to monitoring the load on APN and troubleshooting. NOTE: The capacity window is available only for solutions since SG4. The These graphs show the program blocks that have set the error cause and the internal situation for each case. while the analysis of the Program block and the Internal situation will get more detailed explanation for the fault. Also. The These graphs show the program blocks that have set the error cause and the internal situation for each case. The graph set shows the error causes for RA Updates. SGSN Version >=SG3 This graph set is assigned to troubleshooting. Table 7 112 Graph Sets and explanations for 2G (Cont. the load for each logical PAPU. the load for each physical PAPU. the graph set shows the error causes for each physical PAPU and the capacity of the physical PAPUs. TRAF SGSN SG RA Updates Troubleshooting (1 Day / 24h / 30 min) This graph set shows the number of unsuccessful RA Updates and the percentages of unsuccessful RA Update types. TRAF SGSN SG SMS Deliveries Troubleshooting (1 Day / 24h / 30 min) This graph set shows the number of unsuccessful SMSS sent and the percentages of the SMS sending types. The error cause will provide a general information. and separate for each SMS sending types. Also. >=SG3 This graph set is assigned to troubleshooting. while the analysis of the Program block and the Internal situation will get more detailed explanation for the fault. The error cause will provide a general information. while the analysis of the Program block and the Internal situation will get more detailed explanation for the fault. the graph set shows the error causes for each logical PAPU and the capacity of the logical PAPUs. Also. >=SG3 This graph set is assigned to troubleshooting. The error cause will provide a general information. >=SG3 TRAF SGSN SG PDP Context Activations Load in Physical Papus (1 Day / 24h / 30 min) This graph set shows the number of PDP Context Activations. the graph set shows the error causes for each APN. ) DN05148836 Issue 2-2 Id:0900d805809551ce 113 . >=SG3 This graph set is assigned to monitoring the way the subscribers are behaving and troubleshooting the problems due to attaches for roaming subscribers. the graph set contains the percentages of error causes for each mobile phone type. the load for each PAPU Group. >=SG4 TRAF SGSN SG PDP Context Activations Load in PAPU Groups(1 Day / 24h / 30 min) This graph set shows the number of PDP Context Activations.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph set Explanation TRAF SGSN SG Roaming Attaches Overview (1 Day) This graph set shows the number of attach attempts for each network operator. Also. TRAF SGSN SG PDP Context Activation Load in APNs in TRECs (1 Day / 24h / 30 min) This graph set shows the amount of PDP context activations for each APN for each TREC. TRAF SGSN SG Roaming PDP Context Activation -> Mobile Type Troubleshooting (1 Day) This graph set shows the number of PDP Context Activation attempts for each network operator. >=SG4 TRAF SGSN SG PDP Context Activation Load in TRECs (1 Day / 24h / 30 min) This graph set shows the percentages distribution of PDP Context Activations load for each TREC. The graph set contains the percentages of unsuccessful PDP Context Activation for each operator and the error causes for each network operator. the graph set shows the error causes for each PAPU Group and the capacity of the PAPU Groups. the graph set contains the percentages of unsuccessful attachments for each operator and the error causes for each network operator. The graph set contains the percentages of successful attaches for each operator. Also. Also. This graph set is assigned to monitoring the way the subscribers are behaving and troubleshooting the problems due to PDP Context Activation for roaming subscribers. The graph set contains the percentages of successful PDP Context Activation for each operator. All roaming sessions The percentages of abnormally terminated roaming sessions Error causes for terminated roaming sessions Error causes for terminated roaming sessions for each mobile phones type Table 7 Graph Sets and explanations for 2G (Cont. The graph set contains the percentages of mobile phone types usage for a certain operator. >=SG3 This graph set is assigned to monitoring the way the subscribers are behaving and troubleshooting the problems due to mobile phone type for roaming subscribers. TRAF SGSN SG Roaming PDP Context Activation Overview (1 Day) >=SG3 This graph set shows the number of PDP Context Activation attempts for each network operator. >=SG4 TRAF SGSN SG Roaming Subscriber Troubleshooting (1 Day / 24h / 30 min) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours or minutely for the last 30 minutes: >=SG4 Also. This graph set is assigned to monitoring the load on PAPU Groups and to troubleshooting. Shows the procedure codes for SGSN cause. >=SG4 TRAF SGSN SG Data Traffic / QoS (1 Day / 24h) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours: data volume sent uplink and downlink for each traffic class. Table 7 114 Graph Sets and explanations for 2G (Cont. Shows the procedure codes for SGSN cause. The distribution of MO-SMS for each charging class. >=SG4 TRAF SGSN SG APNs and Data Volumes (1 Day / 24h) This graph set shows following statistics cumulatively for the time period / hourly for the last 24 hours: >=SG4 Percentages of PDP Context Activations distribution for each APN.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph set Explanation TRAF SGSN SG PS External Causes in Procedures (1 Day / 24h / 30 min) This graph set shows the following statistics cumulatively for the time period / hourly for the last 24 hours or minutely for the last 30 minutes: SGSN Version >=SG4 The external PS (Packet Service) cause values sent to MS. Data volume sent downlink for each APN. Percentages of PDP Context Activations distribution for each APN for each charging class. >=SG4 TRAF SGSN SG Charging Info (1 Day / 24h) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours: >=SG4 The distribution of PDP Context Activations for each charging class. The error cause value for each service request and the program blocks that have set the error cause and the internal situation for each case. TRAF SGSN SG CS External Causes in Procedures (1 Day / 24h / 30 min) This graph set shows the following statistics cumulatively for the time period / hourly for the last 24 hours or minutely for the last 30 minutes: >=SG4 The external CS (circuit switched) cause values sent to MS. >=SG4 TRAF SGSN SG Data Volumes in TRECs (1 Day / 24h) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours: data volume sent uplink and downlink for each TREC. TRAF SGSN SG Error Causes in TRECs (1 Day / 24h / 30 min) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours / minutely for the last 30 minutes: The distribution percentages of error causes for each TREC. TRAF SGSN SG Charging Info and Data Volumes (1 Day / 24h) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours: data volumes sent uplink and downlink for each charging class.) Id:0900d805809551ce DN05148836 Issue 2-2 . Data volume sent uplink for each APN. The error cause value for each service request and the program blocks that have set the error cause and the internal situation for each case. ) DN05148836 Issue 2-2 Id:0900d805809551ce 115 . The logical and physical PAPUs for each PS External Causes. The successful and unsuccessful roaming attaches for each RAC under a certain LAC. Shows the percentages of error causes for a RAC for successful and unsuccessful roaming attaches. TRAF SGSN SG APN Data Volume Uplink and Downlink (1 Day) This graph set shows the following statistics cumulatively for the current day: >=SG4 Data volume being sent uplink and downlink for each APN. TRAF SGSN SG CS External Causes in LACs (1 Day) This graph set shows the following statistics cumulatively for the current day: >=SG4 The external CS (circuit switched) cause values sent to MS The CS External Causes for a certain LAC. The logical and physical PAPUs for each PS External Causes. The CS External Causes for the RACs under a certain LAC. TRAF SGSN SG CS External Causes in PAPUs (1 Day) This graph set shows the following statistics cumulatively for the current day: >=SG4 The external CS (circuit switched) cause values sent to MS. TRAF SGSN SG PS External Causes in PAPUs (1 Day) This graph set shows the following statistics cumulatively for the current day: >=SG4 The external PS (Packet Service) cause values sent to MS. Data volume being sent uplink and downlink for each RAC under certain LAC. The distribution of uplink and downlink data volumes for each charging class and mobile types for certain APNs. Table 7 Graph Sets and explanations for 2G (Cont. The error cause code for certain logical and physical PAPU for certain PS External Causes. The error cause code for certain logical and physical PAPU for certain PS External Causes.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph set Explanation TRAF SGSN SG Data Traffic Uplink and Downlink in LAC/RAC/Cell (1 Day) This graph set shows the following statistics cumulatively for the current day: >=SG4 Data volume being sent uplink and downlink for each LAC. TRAF SGSN SG Roaming Subscriber Attaches in LAC / RAC(1 Day) This graph set shows the following statistics cumulatively for the current day: >=SG4 The successful and unsuccessful roaming attaches for each LAC. Data volume being sent uplink and downlink for each Cell under certain RAC. The percentages of error causes for the RAC for CS External Causes. ) Id:0900d805809551ce DN05148836 Issue 2-2 . The PS External Causes for a certain LAC. Percentages of requested classes. TRAF SGSN SG Pagings (1 Day) This graph set shows the following statistics cumulatively for the current day: >=SG4 The number of pagings for LAC and amount of pagings for the RACs under a certain LAC. TRAF SGSN SG APN Usage(1 Day) This graph set shows the following statistics cumulatively for the current day: >=SG4 The PDP Context Activations for each APN. The PS External Causes for the RACs under a certain LAC. Percentages of negotiated classes. TRAF SGSN SG WO-EX This graph set shows the following statistics minutely for the last Computer Unit Loads (30 min) 30 minutes: >=SG4 The average load of each WO-EX (working executing state) object unit processor groups. The number of pagings for PAPU and amount of pagings for the RACs under a certain PAPU. The distribution of mobile types for certain APN. The percentages distribution of unsuccessful PDP context activations error cause code for roamings. TRAF SGSN SG QoS Version 9798 Status(1 Day) This graph set shows the following statistics cumulatively for the current day: >=SG4 Successful rate of delivering the right delay class. The percentages of error causes for a RAC for PS External Causes. Context Activations. The peak load of each WO-EX (working executing state) object unit processor. TRAF SGSN SG Roaming Status (1 Day) This graph set shows the following statistics cumulatively for the current day: >=SG4 The number of roamings and the percentage of roamings that were abnormally terminated. The average load of each WO-EX (spare executing state) object unit processor.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph set Explanation TRAF SGSN SG PS External Causes in LACs (1 Day) This graph set shows the following statistics cumulatively for the current day: SGSN Version >=SG4 The external PS (Packet Service) cause values sent to MS. The percentages distribution of error causes for each mobile types for unsuccessful roamings. The distribution of charging classes for certain APN. >=SG4 Percentages of requested classes. TRAF SGSN SG QoS Version 99 Status(1 Day) This graph set shows the following statistics cumulatively for the current day: successful rate of delivering the right traffic class. Table 7 116 Graph Sets and explanations for 2G (Cont. Percentages of negotiated classes. TRAF SGSN SG PDP Context Activation Load And Errors in Cell in TREC 5-9 (1 Day) This graph set shows the number of PDP Context activations for each Cell names for each TREC 5-9.) DN05148836 Issue 2-2 Id:0900d805809551ce 117 . TRAF SGSN SG BSSGP Peak Load / Physical PAPU (1 Day) This graph set shows the physical index for each physical PAPU. Also. >=SG5 TRAF SGSN SG Passed and Discarded Packets in LAC / RAC / CELL (1 Day) This graph set shows the following statistics cumulatively for the current day: >=SG5 >=SG5 Passed data and discarded packets for each LAC. The average load of each SP-EX (spare executing state) object unit processor.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph set Explanation TRAF SGSN SG SP-EX Computer Unit Loads (30min) This graph set shows the following statistics minutely for the last 30 minutes: >=SG4 The average load of each SP-EX (working executing state) object unit processor groups. Also. >=SG4 TRAF SGSN SG Physical PAPU GTP Packet Throughputs (24 h) This graph set shows the following statistics cumulatively for the >=SG4 current day / hourly for the last 24 hours: Shows amount of transferred and discarded data packets uplink and downlink through each physical PAPU and the percentages of abnormally terminated data transfer for each physical PAPUs. TRAF SGSN SG Logical PAPU GTP Data Throughputs (1 Day / 24 Hours) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours: Shows data amount transferred uplink and downlink in kilobytes through each logical PAPU and the percentages of abnormally terminated data transfer for each logical PAPUs. Also. This graph set is assigned to monitoring the load on TREC and troubleshooting. the graph set shows the error causes for each APN. the graph set shows the error causes for each TREC. the graph set shows the peak load of BSSGP buffer utilisation of selected PAPU in each priority class. Passed data and discarded packets for each Cell under certain RAC. TRAF SGSN SG PDP Context Activation Load And Errors in Cell in TREC 0-4 (1 Day) This graph set shows the number of PDP Context activations for >=SG5 each Cell names for TREC 0-4. the graph set shows the error causes for each TREC. TRAF SGSN SG BSSGP Average Load / Physical PAPU (1 Day) This graph set shows the physical index for each physical PAPU. This graph set is assigned to monitoring the load on APN and troubleshooting. >=SG4 TRAF SGSN SG Physical PAPU GTP Data Throughputs (1 Day / 24 Hours) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours: Shows data amount transferred uplink and downlink in kilobytes through each physical PAPU and the percentages of abnormally terminated data transfer for each physical PAPUs. This graph set is assigned to monitoring the load on TREC and troubleshooting. the load for each APN. TRAF SGSN SG PDP Context Activation Load in APNs (1 Day) This graph set shows the number of PDP Context Activations. >=SG5 Also. The peak load of certain SP-EX (working executing state) object unit processor. >=SG5 Also. the graph set shows the average load of BSSGP buffer utilisation of selected PAPU in each priority class. Passed data and discarded packets for each RAC under certain LAC. Table 7 Graph Sets and explanations for 2G (Cont. TRAF SGSN SG Data Packet Transfer / Physical IPPU (1 Day / 24 Hours) This graph set shows the following statistics cumulatively for the >=SG8 current day / hourly for the last 24 hours: Shows amount of transferred and discarded data packets uplink and downlink through each physical IPPU.) The following table lists the 3G graph sets Graph set Explanation TRAF SGSN SG 3G Events (1 Day. the graph set shows the amount in bytes of how much data has been dropped of BSSGP of selected PAPU in each priority class. Data / Physical PAPU (1 Day) Also. borrowed to another fr NS-VC control. Both successful and unsuccessful events are counted. Also. >=SG5 TRAF SGSN SG NSVC Data Statistics (1 Day) This graph set shows the Network Service Entity Identifiers (NSEI) and Network Service Virtual Connection Identifier (NSVCI) under certain NSEI. passed IP NS-VC control. borrowed from another fr NS-VC control. >=SG8 TRAF SGSN SG Data Transfer / Physical IPPU (1 Day / 24 Hours) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours: Shows data amount transferred uplink and downlink in kilobytes through each physical IPPU. Table 7 Graph Sets and explanations for 2G (Cont. 30 min)/ These graphs show the number of different events cumulatively for the time period.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph set Explanation SGSN Version TRAF SGSN SG BSSGP Lost This graph set shows the physical index for each physical PAPU. 30min) 118 >=SG6 Attaches Detaches PDP Context Activations/Modifications/Deactivations MO/MT-SMS Deliveries These graphs show the number of unsuccessful events cumula. >=SG5 TRAF SGSN SG BSSGP Dropped Packets / Physical PAPU (1 Day) This graph set shows the physical index for each physical PAPU. and also discarded packets due CIR overflow. the graph set shows the data in kilobytes which has passed frame relay NS-VC control. The events are: • • • • TRAF SGSN SG 3G Failures (1 Day. 24 h.>=SG6 tively for the time period. >=SG5 Also. 24 h. the graph set shows the discarded downlink bytes in BSSGP of selected PAPU in each priority class. The events are: • • • • Table 8 SGSN Version Attaches Detaches PDP Context Activations/Modifications/Deactivations MO/MT-SMS Deliveries Graph Sets and explanations for 3G Id:0900d805809551ce DN05148836 Issue 2-2 . 24 h. 30 min) These graphs show the following statistics cumulatively for the time period: Table 8 • • • • • • • • • • • • • • • • • • • • • • • • Real-time monitoring >=SG6 Attaches Detaches PDP Context Activations/Modifications/Deactivations MO/MT-SMS Deliveries >=SG6 Number of PDP Context Activations Error Cause codes of failed PDP Context Activations PDP Context Activations for each Cell Unsuccessful PDP Context Activations for each Cell PDP Context Activations Error Cause code distribution for each cell >=SG6 Number of PDP Context Modifications Error Cause codes of failed PDP Context Modifications PDP Context Modifications for each Cell Unsuccessful PDP Context Modifications for each Cell PDP Context Modifications Error Cause code distribution for each cell >=SG6 Number of PDP Context Deactivations Error Cause codes of failed PDP Context Deactivations PDP Context Deactivations for each Cell Unsuccessful PDP Context Deactivations for each Cell PDP Context Deactivations Error Cause code distribution for each cell >=SG6 Number of MO SMS Deliveries Error Cause codes of failed MO SMS Deliveries MO SMS Deliveries for each Cell Unsuccessful MO SMS Deliveries for each Cell MO SMS Deliveries Error Cause code distribution for each cell Graph Sets and explanations for 3G (Cont. 24 h.Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph set Explanation TRAF SGSN SG 3G Failure Percentages (1 Day.) DN05148836 Issue 2-2 Id:0900d805809551ce 119 . 24 h. 30 min) These graphs show the following statistics cumulatively for the time period: TRAF SGSN SG 3G PDP Context Deactivations (1 Day. 30 min) These graphs show the following statistics cumulatively for the time period: TRAF SGSN SG 3G MO SMS Deliveries (1 Day. 24 h. 30 min) These graphs show the following statistics cumulatively for the time period: TRAF SGSN SG 3G PDP Context Modifications (1 Day. The events are: TRAF SGSN SG 3G PDP Context Activations (1 Day. 24 h. 30 min) These graphs show the percentage of unsuccessful events cumulatively for the time period. 30 min) These graphs show the following statistics cumulatively for the time period: TRAF SGSN SG 3G Attaches (1 Day.) Id:0900d805809551ce DN05148836 Issue 2-2 . 30 min) These graphs show the following statistics cumulatively for the time period: • • • • • • • • • • TRAF SGSN SG 3G Detaches (1 Day. 24 h. 30 min) time period: • • • • >=SG6 Number of MT SMS Deliveries Error Cause codes of failed MT SMS Deliveries MT SMS Deliveries for each Cell Unsuccessful MT SMS Deliveries for each Cell MT SMS Deliveries Error Cause code distribution for each cell These graphs show the following statistics cumulatively for the time period: • • • • • SGSN Version >=SG6 Attaches for each Mobile phone type Attaches' Error Cause code distribution for each mobile phone type PDP Context Activations for each Mobile phone type PDP Context Activations Error Cause code distribution for each Mobile phone type Unsuccessful PDP Context Activations for each Mobile phone type Graph Sets and explanations for 3G (Cont. 24 h. 30 min) • TRAF SGSN SG 3G Mobile Types (1 Day.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph set Explanation TRAF SGSN SG 3G MT SMS Deliveries (1 Day. 24 h. 30 min) • • • Table 8 120 >=SG6 Number of Detaches Error Cause codes of failed Detaches Detaches for each LAC Unsuccessful Detaches for each LAC Detaches Error Cause code distribution for each LAC >=SG6 Number of RA Updates Error Cause codes of failed RA updates RA updates (incoming and outgoing) for each RAC Unsuccessful RA updates (incoming and outgoing) for each RAC RA updates Error Cause distribution for each RAC These graphs show the following statistics cumulatively for the time period: • • >=SG6 Number of Attaches Error Cause codes of failed Attaches Attaches for each LAC Unsuccessful Attaches for each LAC Attaches Error Cause code distribution for each LAC TRAF SGSN SG 3G RA These graphs show the following statistics cumulatively for the Updates (1 Day. 24 h. 24 h. 24 h. 30 min) This graph set shows the number of unsuccessful RA Updates and the percentages of error causes for all unsuccessful RA Updates. TRAF SGSN SG 3G Unsuccessful RA Update Details (1 Day. 30 min) This graph set shows the number of PDP Context Activation attempts for each network operator. This graph set is assigned to monitor the way the subscribers behave and to troubleshoot the problems due to detaches for roaming subscribers. the graph set contains the percentages of unsuccessful PDP Context Deactivation for each operator and the error causes for each network operator. The graph set contains the percentages of mobile phone types usage for a certain operator. 30 min) >=SG6 This graph set shows the number of PDP Context Activation attempts for each network operator. The graph set contains the percentages of successful PDP Context Deactivation for each operator. 24 h. Table 8 Graph Sets and explanations for 3G (Cont. This graph set is assigned to monitoring the way the subscribers are behaving and troubleshooting the problems due to PDP Context Activation for roaming subscribers. TRAF SGSN SG 3G Roaming PDP Context Activations Overview (1 Day. the graph set contains the percentages of error causes for each mobile phone type. The graph set contains the percentages of unsuccessful PDP Context Activation for each operator and the error causes for each network operator. 30 min) This graph set shows the number of detach attempts for each network operator. 24 h. 30 min) This graph set shows the number of PDP Context Deactivation >=SG6 attempts for each network operator. Also. TRAF SGSN SG 3G Roaming PDP Context Activation -> Mobile Type Troubleshooting (1 Day. the graph set contains the percentages of unsuccessful attachments for each operator and the error causes for each network operator. 24 h. >=SG3 This graph set is assigned to monitoring the way the subscribers are behaving and troubleshooting the problems due to mobile phone type for roaming subscribers. 24 h. The graph set also shows the percentages of unsuccessful RA Update types and the percentages of error causes for an unsuccessful specific RA Update type. the graph set contains the percentages of unsuccessful detachments for each operator and the error causes for each network operator. >=SG6 TRAF SGSN SG 3G Roaming Detaches Overview (1 Day. Also. The graph set contains the percentages of successful PDP Context Activation for each operator. Also. Also. Also. 30 min) This graph set shows the number of attach attempts for each network operator. The graph set contains the percentages of successful detaches for each operator.) DN05148836 Issue 2-2 Id:0900d805809551ce 121 . This graph set is assigned to monitor the way the subscribers behave and to troubleshoot the problems due to PDP Context Deactivation for roaming subscribers. 24 h. TRAF SGSN SG 3G Roaming PDP Context Deactivations Overview (1 Day.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph set Explanation TRAF SGSN SG 3G Roaming Attaches Overview (1 Day. >=SG6 This graph set is assigned to monitoring the way the subscribers are behaving and troubleshooting the problems due to attaches for roaming subscribers. The graph set contains the percentages of successful attaches for each operator. 30 min) This graph set shows the distribution percentages of PDP Context Activations load for each TREC. 30 min) This graph set shows the amount of PDP Context Activations for each APN for each TREC.) Id:0900d805809551ce DN05148836 Issue 2-2 . 24 h. 30 min) This graph set shows the following statistics cumulatively for the current day: >=SG6 The number of roamings and the percentage of roamings that were abnormally terminated. 30 min) This graph set shows the number of PDP Context Activations. 30 min) This graph set shows the number of PDP Context Activations. 24 h. the load for each APN. the load for each APN. 24 h. The percentages distribution of error causes for each mobile types for unsuccessful roamings. >=SG6 TRAF SGSN SG 3G PDP Context Activations Load in TRECs 5-9 (1 Day. Also. TRAF SGSN SG 3G Roaming Subscriber Troubleshooting (1 Day. Shows the percentages of error causes for a RAC for successful and unsuccessful roaming attaches. 24 h. 30 min) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours or minutely for the last 30 minutes: >=SG4 All roaming sessions The percentages of abnormally terminated roaming sessions Error causes for terminated roaming sessions Error causes for terminated roaming sessions for each mobile phones type TRAF SGSN SG 3G Roaming Subscriber Attaches in LAC / RAC (1 Day. >=SG6 Table 8 122 Graph Sets and explanations for 3G (Cont. 30 min) This graph set shows the following statistics cumulatively for the current day: >=SG4 The successful and unsuccessful roaming attaches for each LAC. The percentages distribution of unsuccessful PDP context activations error cause code for roamings. The successful and unsuccessful roaming attaches for each RAC under a certain LAC. TRAF SGSN SG 3G PDP Context Activations Load in TRECs 0-4 (1 Day. TRAF SGSN SG 3G PDP Context Activations Load in APNs and SACs (1 Day. the graph set shows the error causes for each APN and the error causes for each SACs APN. This graph set is assigned to monitor the load on APN and to troubleshoot the problems.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph set Explanation TRAF SGSN SG 3G PDP Context Activations Load in APNs (1 Day. 24 h. >=SG6 TRAF SGSN SG 3G PDP Context Activations Load in APNs in TRECs 0-4 (1 Day. the graph set shows the error causes for each APN. 24 h. 24 h. >=SG6 TRAF SGSN SG 3G Roaming Status (1 Day. Also. SGSN Version >=SG6 This graph set is assigned to monitoring the load on APN and troubleshooting. 30 min) This graph set shows the distribution percentages of PDP Context Activations load for each TREC. 24 h. >=SG6 TRAF SGSN SG 3G QoS Class 1 & 2 Status (1 Day. >=SG6 TRAF SGSN SG 3G APN Data Volume Uplink and Downlink (1 Day. 24 h. >=SG4 TRAF SGSN SG 3G Error Causes in TRECs 5-9 (1 Day. and percentages of negotiated classes. 30 min) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours / minutely for the last 30 minutes: data volume sent uplink and downlink for each TREC. 24 h. 30 min) This graph set shows the following statistics cumulatively for the current day: >=SG6 Data volume being sent uplink and downlink for each APN.) DN05148836 Issue 2-2 Id:0900d805809551ce 123 . >=SG4 TRAF SGSN SG 3G Error Causes in TRECs 0-4 (1 Day. 24 h. 30 min) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours / minutely for the last 30 minutes: data volume sent uplink and downlink for each TREC. 30 min) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours / minutely for the last 30 minutes: The distribution percentages of error causes for each TREC. 24 h. >=SG6 TRAF SGSN SG 3G QoS Class 3 & 4 Status (1 Day. >=SG6 TRAF SGSN SG 3G PDP Context Activations Load and Errors in SAC in TREC 7-9 (1 Day. 30 min) This graph set shows the following statistics: data volume sent uplink and downlink for each traffic class. Percentages of negotiated classes. 30 min) This graph set shows the number of PDP Context Activations and the distribution percentages of error causes for each TREC for the each SAC. 30 min) This graph set shows the following statistics: successful rate of delivering the right traffic class. >=SG6 TRAF SGSN SG 3G Data Traffic / QoS(1 Day. Percentages of requested classes. 24 h. 30 min) This graph set shows the number of PDP Context Activations and the distribution percentages of error causes for each TREC for the each SAC. 30 min) This graph set shows the amount of PDP Context Activations for each APN for each TREC.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph set Explanation TRAF SGSN SG 3G PDP Context Activations Load in APNs in TRECs 5-9 (1 Day. >=SG6 TRAF SGSN SG 3G Data Volumes in TRECs 0-4 (1 Day. >=SG4 TRAF SGSN SG 3G Data Volumes in TRECs 5-9 (1 Day. 24 h. >=SG6 TRAF SGSN SG 3G PDP Context Activations Load and Errors in SAC in TREC 4-6 (1 Day. 24 h. The distribution of uplink and downlink data volumes for each charging class and mobile types for certain APNs. >=SG6 TRAF SGSN SG 3G PDP Context Activations Load and Errors in SAC in TREC 0-3 (1 Day. Table 8 Graph Sets and explanations for 3G (Cont. 30 min) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours / minutely for the last 30 minutes: The distribution percentages of error causes for each TREC. 24 h. 24 h. percentages of requested classes. 30 min) This graph set shows the following statistics: successful rate of delivering the right traffic class. 24 h. 24 h. 24 h. 30 min) This graph set shows the number of PDP Context Activations and the distribution percentages of error causes for each TREC for the each SAC. The distribution of charging classes for certain APN. data volume sent uplink for each APN.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph set Explanation TRAF SGSN SG 3G APN Data Traffic Uplink and Downlink in LAC/RAC/SAC (1 day. The events are: • • • • Table 9 SGSN Version • • • • • • • • • >=SG7 Attaches Detaches PDP Context Activations/Modifications/Deactivations MO/MT-SMS Deliveries >=SG7 Number of PDP Context Activations Error Cause codes of failed PDP Context Activations PDP Context Activations for each Cell Unsuccessful PDP Context Activations for each Cell PDP Context Activations Error Cause code distribution for each cell Graph Sets and explanations for I-HSPA Id:0900d805809551ce DN05148836 Issue 2-2 . The events are: TRAF SGSN SG I-HSPA PDP Context Activations (1 Day. 30 min) This graph set shows the following statistics: Percentages of PDP Context Activation distribution for each APN. 30 min) These graphs show the following statistics cumulatively for the time period: 124 >=SG7 These graphs show the number of unsuccessful events cumula. and data volume being sent uplink and downlink for each SAC under certain RAC. Both successful and unsuccessful events are counted. >=SG6 TRAF SGSN SG 3G APN Usage (1 Day. 24 h. 24 h. The distribution of mobile types for certain APN. >=SG6 Table 8 Graph Sets and explanations for 3G (Cont. >=SG6 TRAF SGSN SG 3G APNs and Data Volumes (1 Day. 30min) Attaches Detaches PDP Context Activations/Modifications/Deactivations MO/MT-SMS Deliveries Attaches Detaches PDP Context Activations/Modifications/Deactivations MO/MT-SMS Deliveries TRAF SGSN SG I-HSPA Failure Percentages (1 Day.) The following table lists the I-HSPA graph sets Graph set Explanation TRAF SGSN SG I-HSPA Events (1 Day. 24 h. 24 h. 30 min)/ These graphs show the number of different events cumulatively for the time period. 30 min) These graphs show the percentage of unsuccessful events cumulatively for the time period. The events are: • • • • TRAF SGSN SG I-HSPA Failures (1 Day. 24 h. 24 h. 30 min) This graph set shows the following statistics: Data volume being sent uplink and downlink for each LAC. 30 min) This graph set shows the following: The PDP Context Activations for each APN. data volume being sent uplink and downlink for each RAC under certain LAC. Data volume sent downlink for each APN.>=SG7 tively for the time period. 24 h. 24 h. 30 min) These graphs show the following statistics cumulatively for the time period: • • • • • • • • • • • • • • • • • • • • • • • • • Table 9 Real-time monitoring >=SG7 Number of PDP Context Modifications Error Cause codes of failed PDP Context Modifications PDP Context Modifications for each Cell Unsuccessful PDP Context Modifications for each Cell PDP Context Modifications Error Cause code distribution for each cell >=SG7 Number of PDP Context Deactivations Error Cause codes of failed PDP Context Deactivations PDP Context Deactivations for each Cell Unsuccessful PDP Context Deactivations for each Cell PDP Context Deactivations Error Cause code distribution for each cell >=SG7 Number of MO SMS Deliveries Error Cause codes of failed MO SMS Deliveries MO SMS Deliveries for each Cell Unsuccessful MO SMS Deliveries for each Cell MO SMS Deliveries Error Cause code distribution for each cell >=SG7 Number of MT SMS Deliveries Error Cause codes of failed MT SMS Deliveries MT SMS Deliveries for each Cell Unsuccessful MT SMS Deliveries for each Cell MT SMS Deliveries Error Cause code distribution for each cell >=SG7 Number of Attaches Error Cause codes of failed Attaches Attaches for each LAC Unsuccessful Attaches for each LAC Attaches Error Cause code distribution for each LAC Graph Sets and explanations for I-HSPA (Cont. 24 h.Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph set Explanation TRAF SGSN SG I-HSPA PDP Context Modifications (1 Day.) DN05148836 Issue 2-2 Id:0900d805809551ce 125 . 30 min) These graphs show the following statistics cumulatively for the time period: TRAF SGSN SG I-HSPA MO SMS Deliveries (1 Day. 30 min) These graphs show the following statistics cumulatively for the time period: TRAF SGSN SG I-HSPA PDP Context Deactivations (1 Day. 30 min) These graphs show the following statistics cumulatively for the time period: TRAF SGSN SG I-HSPA MT SMS Deliveries (1 Day. 24 h. 30 min) These graphs show the following statistics cumulatively for the time period: TRAF SGSN SG I-HSPA Attaches (1 Day. 24 h. 24 h. >=SG7 This graph set is assigned to monitoring the way the subscribers are behaving and troubleshooting the problems due to attaches for roaming subscribers. Also. 24 h. 24 h. 24 h.) Id:0900d805809551ce DN05148836 Issue 2-2 . 30 min) time period: • • • • SGSN Version >=SG7 Attaches for each Mobile phone type Attaches' Error Cause code distribution for each mobile phone type PDP Context Activations for each Mobile phone type PDP Context Activations Error Cause code distribution for each Mobile phone type Unsuccessful PDP Context Activations for each Mobile phone type This graph set shows the number of attach attempts for each network operator. 24 h. This graph set is assigned to monitor the way the subscribers behave and to troubleshoot the problems due to detaches for roaming subscribers. Also. 30 min) Table 9 126 This graph set shows the number of detach attempts for each network operator. 30 min) • • • TRAF SGSN SG I-HSPA Roaming Attaches Overview (1 Day. TRAF SGSN SG I-HSPA Roaming Detaches Overview (1 Day. >=SG7 Graph Sets and explanations for I-HSPA (Cont.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph set Explanation TRAF SGSN SG I-HSPA Detaches (1 Day. 30 min) These graphs show the following statistics cumulatively for the time period: • • • • • • TRAF SGSN SG I-HSPA Mobile Types (1 Day. The graph set contains the percentages of successful attaches for each operator. 30 min) >=SG7 Number of RA Updates Error Cause codes of failed RA updates RA updates (incoming and outgoing) for each RAC Unsuccessful RA updates (incoming and outgoing) for each RAC RA updates Error Cause distribution for each RAC These graphs show the following statistics cumulatively for the time period: • • >=SG7 Number of Detaches Error Cause codes of failed Detaches Detaches for each LAC Unsuccessful Detaches for each LAC Detaches Error Cause code distribution for each LAC TRAF SGSN SG I-HSPA RA These graphs show the following statistics cumulatively for the Updates (1 Day. 24 h. The graph set contains the percentages of successful detaches for each operator. the graph set contains the percentages of unsuccessful detachments for each operator and the error causes for each network operator. the graph set contains the percentages of unsuccessful attachments for each operator and the error causes for each network operator. Also. This graph set is assigned to monitoring the way the subscribers are behaving and troubleshooting the problems due to PDP Context Activation for roaming subscribers. The percentages distribution of unsuccessful PDP context activations error cause code for roamings. Also. 24 h. Also. 30 min) This graph set shows the following statistics cumulatively for the current day: >=SG7 The number of roamings and the percentage of roamings that were abnormally terminated. >=SG7 This graph set is assigned to monitoring the way the subscribers are behaving and troubleshooting the problems due to mobile phone type for roaming subscribers. the graph set contains the percentages of unsuccessful PDP Context Deactivation for each operator and the error causes for each network operator. the load for each APN. The graph set also shows the percentages of unsuccessful RA Update types and the percentages of error causes for an unsuccessful specific RA Update type.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph set Explanation TRAF SGSN SG I-HSPA Roaming PDP Context Activations Overview (1 Day. This graph set is assigned to monitor the load on APN and to troubleshoot the problems. 30 min) This graph set shows the number of PDP Context Activations. The graph set contains the percentages of mobile phone types usage for a certain operator. Table 9 Graph Sets and explanations for I-HSPA (Cont. TRAF SGSN SG I-HSPA PDP Context Activations Load in APNs and SACs (1 Day. 24 h. 24 h. TRAF SGSN SG I-HSPA Roaming PDP Context Deactivations Overview (1 Day. 30 min) This graph set shows the number of unsuccessful RA Updates and the percentages of error causes for all unsuccessful RA Updates. 24 h. The graph set contains the percentages of successful PDP Context Activation for each operator. TRAF SGSN SG I-HSPA Unsuccessful RA Update Details (1 Day.) DN05148836 Issue 2-2 Id:0900d805809551ce 127 . the graph set contains the percentages of error causes for each mobile phone type. This graph set is assigned to monitor the way the subscribers behave and to troubleshoot the problems due to PDP Context Deactivation for roaming subscribers. >=SG7 This graph set is assigned to monitoring the load on APN and troubleshooting. 30 min) This graph set shows the number of PDP Context Activation attempts for each network operator. The percentages distribution of error causes for each mobile types for unsuccessful roamings. The graph set contains the percentages of unsuccessful PDP Context Activation for each operator and the error causes for each network operator. >=SG7 TRAF SGSN SG I-HSPA Roaming PDP Context Activation -> Mobile Type Troubleshooting (1 Day. 24 h. 30 min) This graph set shows the number of PDP Context Activations. >=SG7 TRAF SGSN SG I-HSPA Roaming Status (1 Day. 24 h. 24 h. The graph set contains the percentages of successful PDP Context Deactivation for each operator. Also. the graph set shows the error causes for each APN. 30 min) This graph set shows the number of PDP Context Deactivation >=SG7 attempts for each network operator. 30 min) >=SG7 This graph set shows the number of PDP Context Activation attempts for each network operator. the load for each APN. the graph set shows the error causes for each APN and the error causes for each SACs APN. TRAF SGSN SG I-HSPA PDP Context Activations Load in APNs (1 Day. Also. 24 h. >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations Load in APNs in TRECs 5-9 (1 Day. 24 h. 30 min) This graph set shows the amount of PDP Context Activations for each APN for each TREC. 30 min) This graph set shows the amount of PDP Context Activations for each APN for each TREC. 24 h. 30 min) This graph set shows the number of PDP Context Activations and the distribution percentages of error causes for each TREC for the each SAC. 30 min) This graph set shows the distribution percentages of PDP Context Activations load for each TREC. >=SG7 TRAF SGSN SG I-HSPA Data Volumes in TRECs 0-4 (1 Day. 30 min) This graph set shows the following statistics cumulatively for the current day: >=SG7 The successful and unsuccessful roaming attaches for each LAC. 24 h. TRAF SGSN SG I-HSPA PDP Context Activations Load in TRECs 0-4 (1 Day.Real-time monitoring Graph set Traffica Reference Guide for SGSN Direct Interface Explanation This graph set shows the following statistics cumulatively for the TRAF SGSN SG I-HSPA Roaming Subscriber Trouble. >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations Load and Errors in SAC in TREC 4-6 (1 Day. 30 min) This graph set shows the number of PDP Context Activations and the distribution percentages of error causes for each TREC for the each SAC. 24 h. 24 h. 24 h. >=SG7 Table 9 128 Graph Sets and explanations for I-HSPA (Cont. 24 h.current day / hourly for the last 24 hours or minutely for the last shooting (1 Day. 30 min) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours / minutely for the last 30 minutes: data volume sent uplink and downlink for each TREC. 30 min) This graph set shows the distribution percentages of PDP Context Activations load for each TREC. >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations Load in APNs in TRECs 0-4 (1 Day. 30 min) This graph set shows the number of PDP Context Activations and the distribution percentages of error causes for each TREC for the each SAC. 30 min) 30 minutes: SGSN Version >=SG7 All roaming sessions The percentages of abnormally terminated roaming sessions Error causes for terminated roaming sessions Error causes for terminated roaming sessions for each mobile phones type TRAF SGSN SG I-HSPA Roaming Subscriber Attaches in LAC / RAC (1 Day. >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations Load in TRECs 5-9 (1 Day. The successful and unsuccessful roaming attaches for each RAC under a certain LAC. 24 h. 24 h. >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations Load and Errors in SAC in TREC 7-9 (1 Day. Shows the percentages of error causes for a RAC for successful and unsuccessful roaming attaches. >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations Load and Errors in SAC in TREC 0-3 (1 Day.) Id:0900d805809551ce DN05148836 Issue 2-2 . The distribution of uplink and downlink data volumes for each charging class and mobile types for certain APNs. data volume being sent uplink and downlink for each RAC under certain LAC. 24 h. >=SG7 TRAF SGSN SG I-HSPA QoS Class 3 & 4 Status (1 Day. 30 min) This graph set shows the following statistics: successful rate of delivering the right traffic class. 30 min) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours / minutely for the last 30 minutes: The distribution percentages of error causes for each TREC. >=SG7 TRAF SGSN SG I-HSPA APN Usage (1 Day. and percentages of negotiated classes. 30 min) This graph set shows the following statistics: Percentages of PDP Context Activation distribution for each APN. 24 h. The distribution of charging classes for certain APN. 30 min) This graph set shows the following statistics: successful rate of delivering the right traffic class. 30 min) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours / minutely for the last 30 minutes: data volume sent uplink and downlink for each TREC. 24 h. >=SG7 TRAF SGSN SG I-HSPA APN Data Volume Uplink and Downlink (1 Day. Percentages of negotiated classes. Percentages of requested classes. >=SG7 TRAF SGSN SG I-HSPA Data Traffic / QoS(1 Day. 24 h. and data volume being sent uplink and downlink for each SAC under certain RAC. >=SG7 TRAF SGSN SG I-HSPA APNs and Data Volumes (1 Day. 30 min) This graph set shows the following statistics: Data volume being sent uplink and downlink for each LAC. TRAF SGSN SG I-HSPA APN Data Traffic Uplink and Downlink in LAC/RAC/SAC (1 day. percentages of requested classes. 24 h. 24 h. Data volume sent downlink for each APN. 24 h. The distribution of mobile types for certain APN.) The following table lists the 2G/3G/I-HSPA combined graph sets DN05148836 Issue 2-2 Id:0900d805809551ce 129 . data volume sent uplink for each APN. 30 min) This graph set shows the following statistics cumulatively for the current day: >=SG7 Data volume being sent uplink and downlink for each APN. 30 min) This graph set shows the following statistics cumulatively for the current day / hourly for the last 24 hours / minutely for the last 30 minutes: The distribution percentages of error causes for each TREC. 24 h. 24 h. >=SG7 TRAF SGSN SG I-HSPA Error Causes in TRECs 5-9 (1 Day. 30 min) This graph set shows the following statistics: data volume sent uplink and downlink for each traffic class.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph set Explanation TRAF SGSN SG I-HSPA Data Volumes in TRECs 5-9 (1 Day. 30 min) This graph set shows the following: The PDP Context Activations for each APN. 24 h. >=SG7 Table 9 Graph Sets and explanations for I-HSPA (Cont. >=SG7 TRAF SGSN SG I-HSPA Error Causes in TRECs 0-4 (1 Day. >=SG7 TRAF SGSN SG I-HSPA QoS Class 1 & 2 Status (1 Day. 30 min) These graphs show the percentage of unsuccessful events cumulatively for the time period. 30min) These graphs show the number of unsuccessful events cumula. 24 h. 24 h. 24 h. 30 min) These graphs show the number of different events cumulatively for the time period. 30 min) These graphs show the following statistics cumulatively for the time period: • • • • • • • • • • • • • • • • • • Attaches Detaches PDP Context Activations/Modifications/Deactivations MO/MT-SMS Deliveries Attaches Detaches PDP Context Activations/Modifications/Deactivations MO/MT-SMS Deliveries 130 >=SG7 Number of PDP Context Activations Error Cause codes of failed PDP Context Activations PDP Context Activations for each Cell Unsuccessful PDP Context Activations for each Cell PDP Context Activations Error Cause code distribution for each cell >=SG7 Number of PDP Context Modifications Error Cause codes of failed PDP Context Modifications PDP Context Modifications for each Cell Unsuccessful PDP Context Modifications for each Cell PDP Context Modifications Error Cause code distribution for each cell These graphs show the following statistics cumulatively for the TRAF SGSN SG 2G/3G/IHSPA PDP Context Deactiva.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph set Explanation TRAF SGSN SG 2G/3G/IHSPA Events (1 day.time period: tions (1 day. Both successful and unsuccessful events are counted. 30 min) • Number of PDP Context Deactivations • Error Cause codes of failed PDP Context Deactivations • PDP Context Deactivations for each Cell • Unsuccessful PDP Context Deactivations for each Cell • PDP Context Deactivations Error Cause code distribution for each cell Table 10 >=SG7 >=SG7 Graph Sets and explanations for combined graphs (2G/3G/I-HSPA) Id:0900d805809551ce DN05148836 Issue 2-2 . The events are: TRAF SGSN SG 2G/3G/IHSPA PDP Context Activations (1 day.>=SG7 tively for the time period. The events are: • • • • SGSN Version >=SG7 Attaches Detaches PDP Context Activations/Modifications/Deactivations MO/MT-SMS Deliveries TRAF SGSN SG 2G/3G/IHSPA Failures (1 day. 24 h. 24 h. 30 min) These graphs show the following statistics cumulatively for the time period: TRAF SGSN SG 2G/3G/IHSPA PDP Context Modifications (1 day. The events are: TRAF SGSN SG 2G/3G/IHSPA Failure Percentages (1 day. 24 h. ) 5. Graph Description Time Class SGSN version TRAF SGSN SG3 Attaches_ This graph shows the number of successful and unsuccessful Attaches 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Detaches_ This graph shows the number of successful and unsuccessful Detaches 1 day / 24 h / 30 min >=SG3 Table 11 Graph descriptions for 2G DN05148836 Issue 2-2 Id:0900d805809551ce 131 . 24 h. 30 min) These graphs show the following statistics cumulatively for the time period: • • • • • • • • • • Table 10 Number of Attaches Error Cause codes of failed Attaches Attaches for each LAC Unsuccessful Attaches for each LAC Attaches Error Cause code distribution for each LAC • • • • • >=SG7 Number of RA Updates Error Cause codes of failed RA updates RA updates (incoming and outgoing) for each RAC Unsuccessful RA updates (incoming and outgoing) for each RAC RA updates Error Cause distribution for each RAC These graphs show the following statistics cumulatively for the time period: TRAF SGSN SG 2G/3G/IHSPA All Reported Events (1Day / 24h / 30 min) >=SG7 >=SG7 Total Reported Events Reported Events percentage per Radio Access Type Percentage of Reported Events Error Cause percentage per reported event Radio Access Type percentage per reported event per error cause Graph Sets and explanations for combined graphs (2G/3G/I-HSPA) (Cont.3 Graph descriptions The following table shows individual graphs. 24 h.2. g Graph descriptions for 2G Graph descriptions for SG combined graphs Graph descriptions for 3G SG6 graphs Graph descriptions for I-HSPA SG7 graphs Explanations for the hexadecimal values can be found in the possible values fields from chapter RTT report descriptions in this document. 4. 30 min) These graphs show the following statistics cumulatively for the time period: TRAF SGSN SG 2G/3G/IHSPA RA Updates (1 day. and since which SGSN version they exist. time classes. 1. 2. 3.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph set Explanation TRAF SGSN SG 2G/3G/IHSPA Attaches (1 day. their descriptions. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Detaches Unsuccessful This graph shows the number of unsuccessful Detaches. 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Activations Unsuccessful This graph shows the number of unsuccessful PDP Context Activations. Here several error causes that do not need special attention from the operator have also been filtered out. 1 day / 24 h / 30 min >=SG3 Table 11 132 Graph descriptions for 2G (Cont. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 MO SMS Deliveries Unsuccessful This graph shows the number of unsuccessful MO-SMS deliveries. >=SG3 For example. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Deactivations Unsuccessful 1 day / 24 h / 30 min This graph shows the number of unsuccessful PDP Context Deactivations that may need operator’s attention for a potential problem in the network. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Modifications Unsuccessful This graph shows the number of unsuccessful PDP Context Modifications. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 MT SMS Deliveries Unsuccessful This graph shows the number of unsuccessful MT-SMS deliveries. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 RA Updates_ This graph shows the number of successful and unsuccessful RA (Routing Area) updates. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Detaches This graph shows the number of successful and unsuccessful Detaches.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph Description Time Class SGSN version TRAF SGSN SG3 MO SMS Deliveries_ This graph shows the number of successful and unsuccessful MO SMS Deliveries 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 MT SMS Deliveries_ This graph shows the number of successful and unsuccessful MT SMS Deliveries 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Activations_ This graph shows the number of successful 1 day / 24 h / 30 min and unsuccessful PDP Context Activations. TRAF SGSN SG3 RA Updates Unsuccessful This graph shows the number of unsuccessful RA (Routing Area) updates. >=SG3 TRAF SGSN SG3 PDP Context Deactivations_ This graph shows the number of successful and unsuccessful PDP Context Activations 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Modifications_ This graph shows the number of successful and unsuccessful PDP Context Modifications. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Attaches Unsuccessful This graph shows the number of unsuccessful Attaches.) Id:0900d805809551ce DN05148836 Issue 2-2 . 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause. For example. if there has been 1 unsuccessful Modification and 99 successful Modifications. the graph will show 1% value. For example. >=SG3 TRAF SGSN SG3 Detaches Unsuccessful % The graph shows the percentage of unsuc. the graph will show 1% value. if here has been 1 unsuccessful Attach and 99 successful Attaches. For example. For example. Also.1 day / 24 h / 30 min cessful PDP Context Activations. the graph will show 1% value.1 day / 24 h / 30 min cessful PDP Context Deactivations that may need operator’s attention for a potential problem in the network. the graph will show 1% value.1 day / 24 h / 30 min cessful MT-SMS deliveries. >=SG3 TRAF SGSN SG3 PDP Context Deactivations Unsuccessful % The graph shows the percentage of unsuc. For example.1 day / 24 h / 30 min cessful Detaches.) DN05148836 Issue 2-2 Id:0900d805809551ce 133 .1 day / 24 h / 30 min cessful Attaches. For example.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Time Class SGSN version Graph Description TRAF SGSN SG3 PDP Context Activations Unsuccessful % The graph shows the percentage of unsuc. Here several error causes that do not need special attention from the operator have also been filtered out. if there has been 1 unsuccessful Activation and 99 successful Activations. the graph will show 1% value. >=SG3 TRAF SGSN SG3 Attaches Unsuccessful % The graph shows the percentage of unsuc. if there has been 1 unsuccessful RA update and 99 successful RA updates. >=SG3 Table 11 Graph descriptions for 2G (Cont. if there has been 1 unsuccessful RA update and 99 successful RA updates. if there has been 1 unsuccessful Detach and 99 successful Detaches. For example.1 day / 24 h / 30 min cessful PDP Context Modifications. TRAF SGSN SG3 RA Updates Unsuccessful % The graph shows the percentage of unsuc. >=SG3 TRAF SGSN SG3 MT SMS Deliveries Unsuccessful % The graph shows the percentage of unsuc.1 day / 24 h / 30 min cessful RA (Routing Area) updates.1 day / 24 h / 30 min cessful RA (Routing Area) updates. if there has been 1 unsuccessful MT-SMS delivery and 99 successful MT-SMS deliveries. the graph will show 1% value. >=SG3 TRAF SGSN SG3 MO SMS Deliveries Unsuccessful % The graph shows the percentage of unsuc. >=SG3 TRAF SGSN SG3 PDP Context Modifications Unsuccessful % The graph shows the percentage of unsuc. the graph will show 1% value. the graph will show 1% value. >=SG3 For example. if there has been one unsuccessful Deactivation and 99 successful Deactivations. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. > Error Cause 1 day / 24 h / 30 min >=SG3 Shows the percentages of load for the Cells TRAF SGSN SG3 PDP Context Activations 4 -> APN . The Cell with most unsuccessful PDP Context Activations is the first in the graph. The Cells are listed in order so that the Cell where there has been the most PDP Context Activations is the first in the graph.) Id:0900d805809551ce DN05148836 Issue 2-2 . >=SG3 TRAF SGSN SG3 PDP Context Activations / Error Cause This graph shows the Error Cause codes for PDP Context Activations. 1 day / 24 h / 30 min >=SG3 Shows the percentages of error causes for TRAF SGSN SG3 PDP Context Activations 4 -> APN . > Cell 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Activations / Cell This graph shows the Cells for PDP Context Activations. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Activations Unsuccessful / Cell This graph shows the number of unsuccessful PDP Context Activations for Cells. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Activations / Cell / Error Cause This graph shows PDP Context Activations' Error Cause codes for the Cell that is selected in the left hand side graph \'PDP Context Activations / Cell\' Using this graph you can track Error Cause distribution for different Cells. >=SG3 TRAF SGSN SG3 PDP Context Activations 4 -> APN Shows the percentages of load for the APNs. other values indicate a failure in PDP Context Activation.1 day / 24 h / 30 min vations attempts. Using this graph you can track the most used Cells for PDP Context Activation. 1 day / 24 h / 30 min >=SG3 Table 11 134 Time Class SGSN version Graph Graph descriptions for 2G (Cont. Using this graph you can track Cells with most failures in PDP Context Activations.under the certain APN. Using this graph you can track most common Error Cause codes for different Cells for PDP Context Activations.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Description TRAF SGSN SG3 PDP Context Activations This graph shows the number of successful 1 day / 24 h / 30 min and unsuccessful PDP Context Activations. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Activations 4 Shows the number of all PDP Context Acti. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Activations Unsuccessful / Cell / Error Cause 1 day / 24 h / 30 min This graph shows unsuccessful PDP Context Activations' Error Cause codes for the Cell that is selected in the left hand side graph \'Unsuccessful PDP Context Activations / Cell\'. Successful PDP Context Activations has always Error Cause code 0xFFFFFF00.a specific Cell under certain APN. >=SG3 TRAF SGSN SG3 PDP Context Modifications This graph shows the number of successful and unsuccessful PDP Context Modifications. Using this graph you can track the most used Cells for PDP Context Modifications. The Cell with most unsuccessful PDP Context Modifications is the first in the graph. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Modifications Unsuccessful / Cell 1 day / 24 h / 30 min This graph shows the number of unsuccessful PDP Context Modifications for Cells. Successful PDP Context Deactivations has always Error Cause code 0xFFFFFF00. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Modifications / Cell This graph shows the Cells for PDP Context Modifications. Using this graph you can track Cells with most failures in PDP Context Modifications. 1 day / 24 h / 30 min >=SG3 Table 11 Graph descriptions for 2G (Cont. other values indicate a failure in PDP Context Deactivation. >=SG3 TRAF SGSN SG3 PDP Context Modifications Unsuccessful / Cell / Error Cause This graph shows unsuccessful PDP Context Modifications' Error Cause codes for the Cell that is selected in the left hand side graph \'Unsuccessful PDP Context Modifications / Cell\'. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. Successful PDP Context Modifications has always Error Cause code 0xFFFFFF00.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Graph Description Time Class SGSN version TRAF SGSN SG3 PDP Context Modifications / Error Cause This graph shows the Error Cause codes for PDP Context Modifications. Using this graph you can track most common Error Cause codes for different Cells for PDP Context Modifications.) DN05148836 Issue 2-2 Id:0900d805809551ce 135 . 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Deactivations This graph shows the number of successful and unsuccessful PDP Context Deactivations. other values indicate a failure in PDP Context Modification. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Modifications / Cell / Error Cause This graph shows PDP Context Modifications' Error Cause codes for the Cell that is selected in the left hand side graph \'PDP Context Modifications / Cell\' Using this graph you can track Error Cause distribution for different Cells. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. The Cells are listed in order so that the Cell where there has been the most PDP Context Modifications is the first in the graph. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Deactivations / Error Cause This graph shows the Error Cause codes for PDP Context Deactivations. Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph Description Time Class SGSN version TRAF SGSN SG3 PDP Context Deactivations / Cell This graph shows the Cells for PDP Context Deactivations. The Cells are listed in order so that the Cell where there has been the most PDP Context Deactivations is the first in the graph. Using this graph you can track the most used Cells for PDP Context Deactivations. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Deactivations / Cell / Error Cause This graph shows PDP Context Deactivations' Error Cause codes for the Cell that is selected in the left hand side graph \'PDP Context Deactivations / Cell\' Using this graph you can track Error Cause distribution for different Cells. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Deactivations Unsuccessful / Cell This graph shows the number of unsuccessful PDP Context Deactivations for Cells that may need operator’s attention for a potential problem in the network. 1 day / 24 h / 30 min >=SG3 1 day / 24 h / 30 min >=SG3 1 day / 24 h / 30 min >=SG3 The Cell with most unsuccessful PDP Context Deactivations is the first in the graph. Using this graph you can track Cells with most failures in PDP Context Deactivations. Here several error causes that do not need special attention from the operator have also been filtered out. For example, 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause. TRAF SGSN SG3 PDP Context Deactivations Unsuccessful / Cell / Error Cause This graph shows unsuccessful PDP Context Deactivations' Error Cause codes for the Cell that is selected in the left hand side graph \'Unsuccessful PDP Context Deactivations / Cell\'. Using this graph you can track most common Error Cause codes for different Cells for PDP Context Deactivations. Here several error causes that do not need special attention from the operator have also been filtered out. For example, 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause. TRAF SGSN SG3 MT SMS Deliveries Table 11 136 This graph shows the number of successful and unsuccessful MT-SMS deliveries. Graph descriptions for 2G (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Graph Description Time Class SGSN version TRAF SGSN SG3 MT SMS Deliveries / Error Cause This graph shows the Error Cause codes for MT-SMS deliveries. Place the mouse cursor on top of Error Cause value on xaxis to show the description of the Error Cause code. Successful MT-SMS deliveries has always Error Cause code 0xFFFFFF00, other values indicate a failure in MT-SMS delivery. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 MT SMS Deliveries / Cell This graph shows the Cells for MT-SMS deliveries. The Cells are listed in order so that the Cell where there has been the most MT-SMS deliveries is the first in the graph. Using this graph you can track the most used Cells for MT-SMS deliveries. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 MT SMS Deliveries / Cell / Error Cause This graph shows MT-SMS deliveries' Error Cause codes for the Cell that is selected in the left hand side graph \'MT SMS Deliveries / Cell\' Using this graph you can track Error Cause distribution for different Cells. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 MT SMS Deliveries Unsuccessful / Cell 1 day / 24 h / 30 min This graph shows the number of unsuccessful MT-SMS deliveries for Cells. The Cell with most unsuccessful MT-SMS deliveries is the first in the graph. Using this graph you can track Cells with most failures in MT-SMS deliveries. >=SG3 TRAF SGSN SG3 MT SMS Deliveries Unsuccessful / Cell / Error Cause 1 day / 24 h / 30 min This graph shows unsuccessful MT-SMS deliveries' Error Cause codes for the Cell that is selected in the left hand side graph \ 'Unsuccessful MT SMS Deliveries / Cell\'. Using this graph you can track most common Error Cause codes for different Cells for MT-SMS deliveries. >=SG3 TRAF SGSN SG3 MO SMS Deliveries This graph shows the number of successful and unsuccessful MO-SMS deliveries. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 MO SMS Deliveries / Error Cause This graph shows the Error Cause codes for MO-SMS deliveries. Place the mouse cursor on top of Error Cause value on xaxis to show the description of the Error Cause code. Successful MO-SMS deliveries has always Error Cause code 0xFFFFFF00, other values indicate a failure in MO-SMS delivery. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 MO SMS Deliveries / Cell This graph shows the Cells for MO-SMS deliveries. The Cells are listed in order so that the Cell where there has been the most MO-SMS deliveries is the first in the graph. Using this graph you can track the most used Cells for MO-SMS deliveries. 1 day / 24 h / 30 min >=SG3 Table 11 Graph descriptions for 2G (Cont.) DN05148836 Issue 2-2 Id:0900d805809551ce 137 Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Description TRAF SGSN SG3 MO SMS Deliveries / Cell / Error Cause 1 day / 24 h / 30 min This graph shows MO-SMS deliveries' Error Cause codes for the Cell that is selected in the left hand side graph \'MO SMS Deliveries / Cell\' Using this graph you can track Error Cause distribution for different Cells. >=SG3 TRAF SGSN SG3 MO SMS Deliveries Unsuccessful / Cell This graph shows the number of unsuccessful MO-SMS deliveries for Cells. The Cell with most unsuccessful MO-SMS deliveries is the first in the graph. Using this graph you can track Cells with most failures in MO-SMS deliveries. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 MO SMS Deliveries Unsuccessful / Cell / Error Cause 1 day / 24 h / 30 min This graph shows unsuccessful MO-SMS deliveries' Error Cause codes for the Cell that is selected in the left hand side graph \ 'Unsuccessful MO SMS Deliveries / Cell\'. Using this graph you can track most common Error Cause codes for different Cells for MO-SMS deliveries. >=SG3 TRAF SGSN SG3 Attaches / Error Cause This graph shows the Error Cause codes for Attaches. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. Successful Attaches has always Error Cause code 0xFFFFFF00, other values indicate a failure in Attach. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Attaches / LAC This graph shows the LACs for Attaches. The LACs are listed in order so that the LAC where there has been the most Attaches is the first in the graph. Using this graph you can track the most used LACs for Attaches. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Attaches / LAC / Error Cause 1 day / 24 h / 30 min This graph shows Attaches' Error Cause codes for the LAC that is selected in the left hand side graph \'Attaches / LAC\' Using this graph you can track Error Cause distribution for different LACs. >=SG3 TRAF SGSN SG3 Attaches Unsuccessful / LAC This graph shows the number of unsuccessful Attaches for LACs. The LAC with most unsuccessful Attaches is the first in the graph. Using this graph you can track LACs with most failures in Attaches. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Attaches Unsuccessful / LAC / Error Cause 1 day / 24 h / 30 min This graph shows unsuccessful Attaches' Error Cause codes for the LAC that is selected in the left hand side graph \'Unsuccessful Attaches / LAC\'. Using this graph you can track most common Error Cause codes for different LACs for Attaches. >=SG3 TRAF SGSN SG3 Detaches This graph shows the number of successful and unsuccessful Detaches. >=SG3 Table 11 138 Time Class SGSN version Graph 1 day / 24 h / 30 min Graph descriptions for 2G (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Graph Description Time Class SGSN version TRAF SGSN SG3 Detaches / Error Cause This graph shows the Error Cause codes for Detaches. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. Successful Detaches has always Error Cause code 0xFFFFFF00, other values indicate a failure in Detach. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Detaches / LAC This graph shows the LACs for Detaches. The LACs are listed in order so that the LAC where there has been the most Detaches is the first in the graph. Using this graph you can track the most used LACs for Detaches. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Detaches / LAC / Error Cause 1 day / 24 h / 30 min This graph shows Detaches' Error Cause codes for the LAC that is selected in the left hand side graph \'Detaches / LAC\' Using this graph you can track Error Cause distribution for different LACs. >=SG3 TRAF SGSN SG3 Detaches Unsuccessful / LAC This graph shows the number of unsuccessful Detaches for LACs. The LAC with most unsuccessful Detaches is the first in the graph. Using this graph you can track LACs with most failures in Detaches. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Detaches Unsuccessful / LAC / Error Cause This graph shows unsuccessful Detaches' Error Cause codes for the LAC that is selected in the left-hand side graph \ 'Unsuccessful Detaches / LAC\'. Using this graph you can track most common Error Cause codes for different LACs for Detaches. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 RA Updates This graph shows the number of successful and unsuccessful RA (Routing Area) updates. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 RA Updates / Error Cause This graph shows the Error Cause codes for RA (Routing Area) updates. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. Successful RA (Routing area) updates has always Error Cause code 0xFFFFFF00, other values indicate a failure in RA update. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 RA Updates / RAC This graph shows the RACs for RA updates. The RACs are listed in order so that the RAC where there has been the most RA updates is the first in the graph. Using this graph you can track the most used RACs for RA updates. 1 day / 24 h / 30 min >=SG3 Table 11 Graph descriptions for 2G (Cont.) DN05148836 Issue 2-2 Id:0900d805809551ce 139 Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph Description Time Class SGSN version TRAF SGSN SG3 RA Updates / RAC / Error Cause This graph shows RA updates' Error Cause codes for the RAC that is selected in the left hand side graph \'RA Updates / RAC\' Using this graph you can track Error Cause distribution for different RACs. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 RA Updates Unsuccessful / RAC This graph shows the number of unsuccessful RA updates for RACs. The RAC with most unsuccessful RA updates is the first in the graph. Using this graph you can track RACs with most failures in RA updates. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 RA Updates Unsuccessful / RAC / Error Cause 1 day / 24 h / 30 min This graph shows unsuccessful RA updates' Error Cause codes for the RAC that is selected in the left hand side graph \ 'Unsuccessful RA Updates / RAC\'. Using this graph you can track most common Error Cause codes for different RACs for RA updates. >=SG3 TRAF SGSN SG3 Attaches / Mobile Type This graph shows Mobile phone types that are used for Attaches. Mobile phone types are shown in order so that the most used phone type is the first in the graph. This graph can be used to track most used mobile phone types for Attaches. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Attaches / Mobile Type / Error Cause This graph shows Attaches' Error Cause code distribution for the mobile phone type that is currently selected in graph \'Attaches / Mobile Type\'. This graph can be used to track failures in different mobile phone types for Attaches. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Activations / Mobile Type This graph shows Mobile phone types that are used for PDP Context Activations. Mobile phone types are shown in order so that the most used phone type is the first in the graph. This graph can be used to track most used mobile phone types for PDP Context Activations. 1 day / 24 h / 30 min >=SG3 TRAF SGSN PDP Context Activations / Mobile Type / Error Cause This graph shows PDP Context Activations' Error Cause code distribution for the mobile phone type that is currently selected in graph \'PDP Context Activations / Mobile Type\'. This graph can be used to track failures in different mobile phone types for PDP Context Activations. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Activations Unsuccessful / Mobile Type This graph shows Mobile phone types that are used for unsuccessful PDP Context Activations. Mobile phone types are shown in order so that the most used phone type is the first in the graph. This graph can be used to track most used mobile phone types for failed PDP Context Activations. 1 day / 24 h / 30 min >=SG3 Table 11 140 Graph descriptions for 2G (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Graph Description Time Class SGSN version TRAF SGSN SG3 PDP Context Activations Unsuccessful / Mobile Type / Error Cause This graph shows PDP Context Activations' Error Cause code distribution for the mobile phone type that is currently selected in graph \'Unsuccessful PDP Context Activations / Mobile Type\'. This graph can be used to track failures in different mobile phone types for PDP Context Activations. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccessful PDP Context Activations Shows the number of unsuccessful PDP Context Activations cumulatively for the time period. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccessful PDP Context Activations -> Error Cause Shows the percentages of error causes for all unsuccessful PDP Context Activations. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccessful PDP Context Activations -> Error Cause -> SetPrb Shows the percentages of program blocks used for a specific error cause. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccess- Shows the percentages of internal situation ful PDP Context Activations -> for a specific program block. Error Cause -> SetPrb -> IntSit 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccessful PDP Context Activations 2 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccess- Shows the percentages of error causes for 1 day / 24 h / 30 min ful PDP Context Activations 2 - an unsuccessful specific PDP Context Activation type. > Error Cause >=SG3 TRAF SGSN SG3 Unsuccess- Shows the percentages of program blocks ful PDP Context Activations 2 - used for a specific error cause and a specific PDP Context Activation type. > Error Cause -> SetPrb 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccess- Shows the percentages of internal situation ful PDP Context Activations 2 - for a specific program block. > Error Cause -> SetPrb -> IntSit 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccessful PDP Context Modifications Shows the number of unsuccessful PDP Context Modifications cumulatively for the time period. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccess- Shows the percentages of error causes for ful PDP Context Modifications - all unsuccessful PDP Context Modifications. > Error Cause 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccess- Shows the percentages of program blocks ful PDP Context Modifications - used for a specific error cause. > Error Cause ->Set Prb 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccess- Shows the percentages of internal situation ful PDP Context Modifications - for a specific program block. > Error Cause ->Set Prb -> IntSit 1 day / 24 h / 30 min >=SG3 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccessful PDP Context Modifications 2 Table 11 Shows the percentages of unsuccessful PDP Context Activation types cumulatively for the time period. Shows the percentages of unsuccessful PDP Context Modification types cumulatively for the time period. Graph descriptions for 2G (Cont.) DN05148836 Issue 2-2 Id:0900d805809551ce 141 Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph Description Time Class SGSN version TRAF SGSN SG3 Unsuccessful PDP Context Modifications 2 -> Error Cause Shows the percentages of error causes for an unsuccessful specific PDP Context Modification type. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccessful PDP Context Modifications 2 -> Error Cause ->Set Prb Shows the percentages of program blocks used for a specific error cause and a specific PDP Context Modification type. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccessful PDP Context Modifications 2 -> Error Cause ->Set Prb -> IntSit Shows the percentages of internal situation for a specific program block. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 SG3 Unsuc- Shows the number of unsuccessful SMS cessful SMS Deliveries deliveries cumulatively for the time period. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 SG3 Unsuc- Shows the percentages of error causes for all unsuccessful SMS deliveries cessful SMS Deliveries -> Error Cause 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 SG3 Unsuc- Shows the percentages of program blocks used for a specific error cause. cessful SMS Deliveries -> Error Cause -> SetPrb 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 SG3 Unsuc- Shows the percentages of internal situation for a specific program block. cessful SMS Deliveries -> Error Cause -> SetPrb -> IntSit 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 SG3 Unsuc- Shows the percentages of unsuccessful cessful SMS Deliveries 2 SMS delivery types cumulatively for the time period. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 SG3 Unsuc- Shows the percentages of error causes for an unsuccessful specific SMS delivery cessful SMS Deliveries 2 -> type. Error Cause 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 SG3 Unsuc- Shows the percentages of program blocks used for a specific error cause and a cessful SMS Deliveries 2 -> specific SMS delivery type. Error Cause -> SetPrb 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 SG3 Unsuc- Shows the percentages of internal situation for a specific program block. cessful SMS Deliveries 2 -> Error Cause -> SetPrb -> IntSit 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccessful RA Update Shows the number of unsuccessful RA Updates cumulatively for the time period. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccessful RA Update -> Error Cause Shows the percentages of error causes for all unsuccessful RA Updates. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccess- Shows the percentages of program blocks ful RA Update -> Error Cause - used for a specific error cause. > SetPrb 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccess- Shows the percentages of internal situation ful RA Update -> Error Cause - for a specific program block. > SetPrb -> IntSit 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccessful RA Update 2 1 day / 24 h / 30 min >=SG3 Table 11 142 Shows the percentages of unsuccessful RA Update types cumulatively for the time period. Graph descriptions for 2G (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Time Class SGSN version TRAF SGSN SG3 Unsuccess- Shows the percentages of error causes for ful RA Update 2 -> Error Cause an unsuccessful specific RA Update type. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccessful RA Update 2 -> Error Cause -> SetPrb Shows the percentages of program blocks used for a specific error cause and a specific RA Update type. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Unsuccessful RA Update 2 -> Error Cause -> SetPrb -> IntSit Shows the percentages of internal situation for a specific program block. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Activations 0 Shows the number of all PDP Context Acti- 1 day / 24 h / 30 min vations attempts. >=SG3 TRAF SGSN SG3 PDP Context Activations -> Logical PAPU Shows the percentages of load for the logical PAPUs. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Activations -> Logical PAPU -> Error Cause Shows percentages of error causes for a specific logical PAPU. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG4 PDP Context Activations -> Logical PAPUs Shows the percentages of load for the logical PAPUs. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Activations 2 Shows the number of all PDP Context Acti- 1 day / 24 h / 30 min vations attempts. >=SG3 TRAF SGSN SG3 PDP Context Activations 2 -> Physical PAPU Shows the percentages of load for the physical PAPUs. 1 day / 24 h / 30 min >=SG3 1 day / 24 h / 30 min >=SG3 Graph Description Shows percentages of error causes for a TRAF SGSN SG3 PDP specific physical PAPU. Context Activations 2 -> Physical PAPU -> Error Cause TRAF SGSN SG4 PDP Context Activations -> Physical PAPU Shows the percentages of load for the physical PAPUs. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 PDP Context Activations 3 Shows the number of all PDP Context Acti- 1 day / 24 h / 30 min vations attempts. >=SG3 TRAF SGSN SG3 PDP Context Activations 3 -> APN Shows the percentages of load for the APNs. 1 day / 24 h / 30 min >=SG3 Shows the percentages of error causes for TRAF SGSN SG3 PDP Context Activations 3 -> APN - a specific APN. > Error Cause 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG3 Roaming Attaches Attempts Shows the number of attaches attempts for each network operator. 1 day >=SG3 TRAF SGSN SG3 Roaming Successful Attaches Shows the percentages of successful attaches for each operator. 1 day >=SG3 TRAF SGSN SG3 Roaming Unsuccessful Attaches Shows the percentages of unsuccessful attaches for each operator. 1 day >=SG3 Table 11 Graph descriptions for 2G (Cont.) DN05148836 Issue 2-2 Id:0900d805809551ce 143 Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph Description Time Class SGSN version TRAF SGSN SG3 Roaming Unsuccessful Attaches -> Error Cause Shows the percentages of error causes for unsuccessful attaches and a specific operator. 1 day >=SG3 TRAF SGSN SG3 Roaming PDP Context Activations Attempts Shows the number of PDP Context Activation attempts for each network operator. 1 day >=SG3 TRAF SGSN SG3 Roaming Successful PDP Context Activations Shows the percentages of successful PDP Context Activations for each operator. 1 day >=SG3 TRAF SGSN SG3 Roaming Unsuccessful PDP Context Activations Shows the percentages of unsuccessful 1 day PDP Context Activations for each operator. >=SG3 TRAF SGSN SG3 Roaming Unsuccessful PDP Context Activations -> Error Cause Shows the percentages of error causes for unsuccessful PDP Context Activation for a specific operator. 1 day >=SG3 TRAF SGSN Roaming PDP Shows the number of PDP Context ActivaContext Activations Attempts 2 tion attempts for each network operator. 1 day >=SG3 TRAF SGSN Roaming PDP Context Activations Attempts 2 -> Mobile Type Shows the percentages of mobile types for PDP Context Activation attempts for a specific operator. 1 day >=SG3 TRAF SGSN Roaming PDP Context Activations Attempts 2 -> Mobile Type -> Error Cause Shows the percentages of error causes for PDP Context Activation attempts for a specific mobile type. 1 day >=SG3 TRAF SGSN Roaming PDP Context Activations Attempts > Mobile Type Shows the percentage of mobile types for each operator. 1 day >=SG3 TRAF SGSN Roaming PDP Context Activations Attempts > Mobile Type -> Error Cause Shows the percentage of error causes of a specific mobile type for PDP Context Activation for each operator. 1 day >=SG3 TRAF SGSN SG4 Delay Class 1 QoS Successful Request Shows the percentage of requests for a specific delay class. 1 day >=SG4 TRAF SGSN SG4 Delay Class 2 QoS Successful Request Shows the percentage of answered requests for a specific delay class. 1 day >=SG4 TRAF SGSN SG4 Delay Class 3 QoS Successful Request Shows the percentage of answered requests for a specific delay class. 1 day >=SG4 TRAF SGSN SG4 Delay Class 4 QoS Successful Request Shows the percentage of answered requests for a specific delay class. 1 day >=SG4 TRAF SGSN SG4 Delay Class 1 QoS Requested Shows the percentage of answered requests for a specific delay class. 1 day >=SG4 TRAF SGSN SG4 Delay Class 2 QoS Requested Shows the percentage of requests for a specific delay class. 1 day >=SG4 TRAF SGSN SG4 Delay Class 3 QoS Requested Shows the percentage of requests for a specific delay class. 1 day >=SG4 TRAF SGSN SG4 Delay Class 4 QoS Requested Shows the percentage of requests for a specific delay class. 1 day >=SG4 Table 11 144 Graph descriptions for 2G (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Graph Description Time Class SGSN version TRAF SGSN SG4 Delay Class 1 QoS Negotiated Shows the percentage of negotiations for a specific delay class. 1 day >=SG4 TRAF SGSN SG4 Delay Class 2 QoS Negotiated Shows the percentage of negotiations for a specific delay class. 1 day >=SG4 TRAF SGSN SG4 Delay Class 3 QoS Negotiated Shows the percentage of negotiations for a specific delay class. 1 day >=SG4 TRAF SGSN SG4 Delay Class 4 QoS Negotiated Shows the percentage of negotiations for a specific delay class. 1 day >=SG4 TRAF SGSN SG4 Traffic Class 1 QoS Successful Request Shows the percentage of answered requests for a specific traffic class. 1 day >=SG4 TRAF SGSN SG4 Traffic Class 2 QoS Successful Request Shows the percentage of answered requests for a specific traffic class. 1 day >=SG4 TRAF SGSN SG4 Traffic Class 3 QoS Successful Request Shows the percentage of fulfilled requests for a specific traffic class. 1 day >=SG4 TRAF SGSN SG4 Traffic Class 4 QoS Successful Request Shows the percentage of fulfilled requests for a specific traffic class. 1 day >=SG4 TRAF SGSN SG4 Traffic Class 1 QoS Negotiated Shows the percentage of negotiations for a specific traffic class. 1 day >=SG4 TRAF SGSN SG4 Traffic Class 2 QoS Negotiated Shows the percentage of negotiations for a specific traffic class. 1 day >=SG4 TRAF SGSN SG4 Traffic Class 3 QoS Negotiated Shows the percentage of negotiations for a specific traffic class. 1 day >=SG4 TRAF SGSN SG4 Traffic Class 4 QoS Negotiated Shows the percentage of negotiations for a specific traffic class. 1 day >=SG4 TRAF SGSN SG4 Traffic Class 1 QoS Requested Shows the percentage of requests for a specific traffic class. 1 day >=SG4 TRAF SGSN SG4 Traffic Class 2 QoS Requested Shows the percentage of requests for a specific traffic class. 1 day >=SG4 TRAF SGSN SG4 Traffic Class 3 QoS Requested Shows the percentage of requests for a specific traffic class. 1 day >=SG4 TRAF SGSN SG4 Traffic Class 4 QoS Requested Shows the percentage of requests for a specific traffic class. 1 day >=SG4 TRAF SGSN SG4 Data Volume / Delay Class 1 Shows the data volume uplink and downlink for each Delay class. 1 day / 24 h >=SG4 TRAF SGSN SG4 Data Volume / Delay Class 2 Shows the data volume uplink and downlink for each Delay class. 1 day / 24 h >=SG4 TRAF SGSN SG4 Data Volume / Delay Class 3 Shows the data volume uplink and downlink for each Delay class. 1 day / 24 h >=SG4 TRAF SGSN SG4 Data Volume / Delay Class 4 Shows the data volume uplink and downlink for each Delay class. 1 day / 24 h >=SG4 TRAF SGSN SG4 Data Volume / Traffic Class 1 Shows the data volume uplink and downlink for the Conversational class. 1 day / 24 h >=SG4 Table 11 Graph descriptions for 2G (Cont.) DN05148836 Issue 2-2 Id:0900d805809551ce 145 Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph Description Time Class SGSN version TRAF SGSN SG4 Data Volume / Traffic Class 2 Shows the data volume uplink and downlink for the Streaming class. 1 day / 24 h >=SG4 TRAF SGSN SG4 Data Volume / Traffic Class 3 Shows the data volume uplink and downlink for the Interactive class. 1 day / 24 h >=SG4 TRAF SGSN SG4 Data Volume / Traffic Class 4 Shows the data volume uplink and downlink for the Background class. 1 day / 24 h >=SG4 TRAF SGSN SG4 PS External Causes Shows the external PS cause value of attach accept and routing area update accept messages sent to MS. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 PS External Causes / Cause Proc Shows the procedure codes for SGSN PS External Causes. Mobility Management fills this value according to the service that it is asked to offer. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 PS External Causes / Cause Proc / Error Cause Shows the distribution of error cause codes for all procedure causes. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 PS External Causes / Cause Proc / Error Cause / Program Block Shows the distribution of program blocks used for a specific error cause. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 PS External Causes / Cause Proc / Error Cause / Program Block / Internal Situation Shows the distribution of internal situation for a specific program block. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 CS External Causes Shows the external CS (circuit switched) cause value of attach accept and routing area update accept messages sent to MS. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 CS External Causes / Cause Proc Shows the procedure codes for SGSN CS External Causes. Mobility Management fills this value according to the service that it is asked to offer. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 CS External Causes / Cause Proc / Error Cause Shows the distribution of error cause codes for all procedure causes. Place the mouse cursor on top of Error Cause value on the x-axis to show the description of the Error Cause code. Successful fulfilled service request s have always the Error Cause code 0xFFFFFFFF, other values indicate a failure in service negotiation. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 CS External Causes / Cause Proc / Error Cause / Program Block Shows the distribution of program blocks used for a specific error cause. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 CS External Causes / Cause Proc / Error Cause / Program Block / Internal Situation Shows the distribution of internal situation for a specific program block. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 PS External Causes 1 Shows the external PS cause value of attach accept and routing area update accept messages sent to MS. 1 day >=SG4 Table 11 146 Graph descriptions for 2G (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 1 day >=SG4 TRAF SGSN SG4 PS External Causes 1 / LAC / RAC Shows the distribution of PS External Cause for the RACs under a certain LAC. 1 day / 24 h / 30 min >=SG4 Table 11 Graph descriptions for 2G (Cont.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Graph Description Time Class SGSN version TRAF SGSN SG4 PS External Causes 1 / LAC This graph shows the LACs for certain PS External Cause.) DN05148836 Issue 2-2 Id:0900d805809551ce 147 . 1 day >=SG4 TRAF SGSN SG4 PS External Causes 2 Shows the external PS cause value of attach accept and routing area update accept messages sent to MS. 1 day >=SG3 TRAF SGSN SG4 PS External Causes 2 / Logical PAPU Shows the distribution of logical PAPUs for certain PS External Causes 1 day >=SG3 TRAF SGSN SG4 PS External Causes 2 / Physical PAPU Shows the distribution of physical PAPUs for certain PS External Causes 1 day >=SG3 TRAF SGSN SG4 PS External Causes 2 / Logical PAPU / Error Causes Shows the error causes for certain logical PAPU for certain PS External Cause 1 day >=SG3 TRAF SGSN SG4 PS External Causes 2 / Physical PAPU / Error Causes Shows the error causes for certain physical PAPU for certain PS External Cause 1 day >=SG3 TRAF SGSN SG4 CS External Causes 2 Shows the external CS cause value of attach accept and routing area update accept messages sent to MS >=SG3 Daily 1 day >=SG3 TRAF SGSN SG4 CS External Causes 2 / Logical PAPU Shows the distribution of logical PAPUs for certain CS External Causes 1 day >=SG3 TRAF SGSN SG4 CS External Causes 2 / Physical PAPU Shows the distribution of physical PAPUs for certain CS External Causes 1 day >=SG3 TRAF SGSN SG4 CS External Causes 2 / Logical PAPU / Error Causes Shows the error causes for certain logical PAPU for certain CS External Cause 1 day >=SG3 TRAF SGSN SG4 CS External Causes 2 / Physical PAPU / Error Causes Shows the error causes for certain physical PAPU for certain CS External Causes 1 day >=SG3 TRAF SGSN SG4 CS External Causes 1 Shows the external CS (circuit switched) cause value of attach accept and routing area update accept messages sent to MS. Using this graph you can track the most used LACs for PS External Causes. Using this graph you can track the most used RACs for PS External Causes 1 day >=SG4 TRAF SGSN SG4 PS External Causes 1 / LAC / RAC / Error Causes Shows the distribution of error causes for a RAC for PS External Causes. The LACs are listed so that the LAC where there has been the most PS External Causes is first in the graph. 1 day >=SG4 TRAF SGSN SG4 APN Data Volume Uplink and Downlink / Charging Info Shows the distribution of uplink and downlink data volumes in kilobytes for each charging class for certain APNs. 1 day / 24 h >=SG4 TRAF SGSN SG4 Charging Info / MO SMS Shows the number of mobile originated SMS being sent for each charging class. 1 day / 24 h >=SG4 TRAF SGSN SG4 Charging Info / PDP Context Shows the number of PDP Contexts being transferred for each charging class. 1 day >=SG4 TRAF SGSN SG4 Subscriber APN Usage Shows the percentage of PDP context acti.1 day / 24 h vations for certain APNs. The LACs are listed so that the LAC where there has been the most CS External Causes is the first in the graph. 1 day >=SG4 TRAF SGSN SG4 PDP Context Activations / Charging Info Shows the number of PDP Contexts being transferred for each charging class. 1 day >=SG4 TRAF SGSN SG4 APN Data Volume Uplink and Downlink Shows the amount of data sent uplink and downlink in kilobytes for each APN. Table 11 148 >=SG4 Graph descriptions for 2G (Cont.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph Description Time Class SGSN version TRAF SGSN SG4 CS External Causes 1 / LAC This graph shows the LACs for a certain CS External Cause. 1 day >=SG4 TRAF SGSN SG4 APN Usage / Charging Info Shows the distribution of charging classes for certain APNs. Using this graph you can track the most used RACs for CS External Causes. 1 day >=SG4 TRAF SGSN SG4 APN Data Volume Uplink and Downlink / Mobile Types Shows the distribution of uplink and downlink data volumes in kilobytes for each mobile types for certain APNs. 1 day >=SG4 TRAF SGSN SG4 APN Usage / Mobile Types This graph shows mobile phone types that are used for a certain APN.) Id:0900d805809551ce DN05148836 Issue 2-2 . 1 day / 24 h >=SG3 TRAF SGSN SG4 APN Usage Shows the distribution of APNs for the PDP Context Activations that occurred. Using this graph you can track the most used LACs for PS External Causes. Mobile phone types are shown so that the most used phone type is first in the graph. 1 day >=SG4 TRAF SGSN SG4 CS External Causes 1 / LAC / RAC / Error Causes Shows the distribution of error causes for a RAC for CS External Causes. Charging classes are shown so that the most common charging class is first in the graph. 1 day >=SG4 TRAF SGSN SG4 CS External Causes 1 / LAC / RAC Shows the distribution of CS External Cause for the RACs under a certain LAC. 1 day / 24 h >=SG4 TRAF SGSN SG4 Charging Info / APN Shows the percentage of APNs where PDP Contexts are being transferred for each charging class. Charging classes are shown so that the most common charging class is first in the graph. 1 day >=SG4 TRAF SGSN SG4 Unsuccessful Roaming Sessions Shows the percentage of abnormally termi. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Roaming PDP Context Activations Shows the number of roaming PDP Context Activations 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Roaming PDP Context Modifications Shows the number of roaming PDP Context Modifications 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Roaming Attaches / Error Cause Shows the distribution of error causes for roaming attaches. Other values indicate a failure in roaming attach Modification. 1 day >=SG4 TRAF SGSN SG4 Uplink Data Volume / Charging Info Shows the distribution of uplink data 1 day / 24 h volume in kilobytes for each charging class. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Roaming PDP Context Activations / Error Cause Shows the distribution of error causes for roaming PDP Context Activations.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Graph Description Time Class SGSN version TRAF SGSN SG4 Subscriber Data Uplink / APN Shows the amount of data sent uplink for a specific APN. 1 day / 24 h / 30 min >=SG4 Table 11 Graph descriptions for 2G (Cont. 1 day >=SG4 TRAF SGSN SG4 Unsuccessful Roaming Sessions / Error Cause / Mobile Types Shows the distribution percentage of mobile phones type for Error Causes for abnormally terminated roaming sessions. 1 day / 24 h >=SG4 TRAF SGSN SG4 Uplink and Downlink Data Volume / LAC Shows the data volume uplink and downlink for each LAC. 1 day >=SG4 TRAF SGSN SG4 Roaming Attaches Shows the number of roaming attaches. >=SG4 TRAF SGSN SG4 Roaming Sessions Shows the number of roaming sessions. >=SG4 TRAF SGSN SG4 Unsuccessful Roaming Sessions / Error Cause Shows the distribution percentage of error causes for abnormally terminated roaming sessions. 1 day >=SG4 TRAF SGSN SG4 Uplink and Downlink Data Volume / LAC / RAC Shows the data volume uplink and downlink for each RAC in a certain LAC. Successful roaming PDP Context Activations have always the Error Cause code 0h.1 day nated roaming sessions. Other values indicate a failure in roaming PDP Context Activations. 1 day >=SG4 TRAF SGSN SG4 Uplink and Downlink Data Volume / LAC / RAC /Cell Shows the data volume uplink and downlink for each cell in a certain RAC.) DN05148836 Issue 2-2 Id:0900d805809551ce 149 . Successful roaming attach has always the Error Cause code 0h. 1 day / 24 h >=SG4 TRAF SGSN SG4 Subscriber Data Downlink / APN Shows the amount of data sent downlink for a specific APN. >=SG4 TRAF SGSN SG4 Downlink Data Volume / Charging Info Shows the distribution of downlink data 1 day / 24 h volume in kilobytes for each charging class. nated roaming PDP Context Activations vations >=SG4 TRAF SGSN SG4 Unsuccessful Roaming PDP Context Modifications Shows the percentage of abnormally termi. >=SG4 TRAF SGSN SG4 Roaming Attaches / LAC / RAC / Error Cause Shows the percentage of error causes for a RAC under a certain LAC.) Id:0900d805809551ce DN05148836 Issue 2-2 . Successful roaming has always the Error Cause code 0h. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Roaming PDP Context Activations / Error Cause / Program Block Shows the distribution of program blocks used for a specific error cause. 1 day / 24 h / 30 min >=SG4 Shows the distribution of internal situation TRAF SGSN SG4 Roaming for a specific program block.1 day / 24 h / 30 min ful Roaming PDP Context Acti. Other values indicate a failure in roaming attach. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Unsuccessful Roaming Attaches Shows the percentage of abnormally termi. Successful roaming PDP Context Modifications have always the Error Cause code 0h. 1 day >=SG4 Table 11 150 Graph descriptions for 2G (Cont.1 day / 24 h / 30 min nated roaming attaches >=SG4 TRAF SGSN SG4 Unsuccess. Other values indicate a failure in roaming PDP Context Modification.1 day / 24 h / 30 min nated roaming PDP Context Modifications.Shows the percentage of abnormally termi.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph Description Time Class SGSN version TRAF SGSN SG4 Roaming PDP Context Modifications / Error Cause Shows the distribution of error causes for roaming PDP Context Activations. 1 day >=SG4 TRAF SGSN SG4 Roaming Attaches / LAC / RAC Shows the distribution of Roaming 1 day Attaches for the RACs under a certain LAC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Roaming Attaches / Error Cause / Program Block Shows the distribution of program blocks used for a specific error cause. Attaches / Error Cause / Program Block / Internal Situation 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Roaming PDP Context Activations / Error Cause / Program Block / Internal Situation Shows the distribution of internal situation for a specific program block. >=SG4 TRAF SGSN SG4 Roaming Attaches / LAC Shows the distribution of Roaming Attaches in each LAC. 1 day >=SG4 TRAF SGSN SG4 Unsuccessful Roaming Attaches / LAC Shows the distribution of Roaming Attaches that were abnormally terminated for each LAC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Roaming PDP Context Modifications / Error Cause / Program Block Shows the distribution of program blocks used for a specific error cause. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Roaming PDP Context Modifications / Error Cause / Program Block / Internal Situation Shows the distribution of internal situation for a specific program block. >=SG4 TRAF SGSN SG4 PDP Context Activation Load in TREC 3 Shows the percentage of PDP context acti.1 day / 24 h / 30 min vation load for a specific TREC >=SG4 TRAF SGSN SG4 PDP Context Activation Load in TREC 4 Shows the percentage of PDP context acti. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG4 PDP Context Activations -> PAPU Groups -> Error Cause Shows percentages of error causes for a specific PAPU Group. >=SG4 TRAF SGSN SG4 PDP Context Activation Load in TREC 2 Shows the percentage of PDP context acti.1 day / 24 h / 30 min vation load for a specific TREC.1 day / 24 h / 30 min vation load for a specific TREC.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Graph Description Time Class SGSN version TRAF SGSN SG4 Unsuccessful Roaming Attaches / LAC / RAC Shows the distribution of Roaming Attaches that were abnormally terminated for the RACs under a certain LAC. >=SG4 Table 11 Graph descriptions for 2G (Cont. >=SG4 TRAF SGSN SG4 PDP Context Activation Load in TREC 1 Shows the percentage of PDP context acti.1 day / 24 h / 30 min vation load for a specific TREC.1 day / 24 h / 30 min vation load for a specific TREC. 1 day >=SG4 TRAF SGSN SG4 PDP Context Activations Shows the number of all PDP Context Acti. >=SG4 TRAF SGSN SG4 PDP Context Activation Load in TREC 6 Shows the percentage of PDP context acti. 1 day / 24 h / 30 min >=SG3 TRAF SGSN SG4 PDP Context Activations / PAPU Groups Shows the capacity of a certain PAPU group. >=SG4 TRAF SGSN SG4 PDP Context Activations -> PAPU Groups Shows the capacity of a certain PAPU group. >=SG4 TRAF SGSN SG4 PDP Context Activation Load in TREC 7 Shows the percentage of PDP context acti. 1 day >=SG4 TRAF SGSN SG4 Unsuccessful Roaming Attaches / LAC / RAC / Error Cause Shows the percentage of error causes for Roaming Attaches that were abnormally terminated per RAC under a specific LAC. >=SG4 TRAF SGSN SG4 PDP Context Activation Load in TREC 8 Shows the percentage of PDP context acti.1 day / 24 h / 30 min vations attempts.1 day / 24 h / 30 min vation load for a specific TREC. >=SG4 TRAF SGSN SG4 PDP Context Activation Load in TREC 5 Shows the percentage of PDP context acti.1 day / 24 h / 30 min vation load for a specific TREC. >=SG4 TRAF SGSN SG4 PDP Context Activation Load in TREC 9 Shows the percentage of PDP context acti.) DN05148836 Issue 2-2 Id:0900d805809551ce 151 .1 day / 24 h / 30 min vation load for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 PDP Context Activation Load in TREC 0 Shows the percentage of PDP context acti.1 day / 24 h / 30 min vation load for a specific TREC.1 day / 24 h / 30 min vation load for a specific TREC. 1 day >=SG4 TRAF SGSN SG4 Data Volumes in TREC 6 Shows the data volume uplink and downlink for a specific TREC. 24 h >=SG4 TRAF SGSN SG4 Data Volume in TREC 6 Shows the data volume uplink and downlink for a specific TREC. 1 day >=SG4 TRAF SGSN SG4 Data Volumes in TREC 1 Shows the data volume uplink and downlink for a specific TREC. 1 day >=SG4 TRAF SGSN SG4 Data Volumes in TREC 3 Shows the data volume uplink and downlink for a specific TREC. 24 h >=SG4 TRAF SGSN SG4 Data Volume in TREC 1 Shows the data volume uplink and downlink for a specific TREC. 24 h >=SG4 TRAF SGSN SG4 Error Causes in TREC 0 Shows the error cause distribution for a specific TREC. 1 day >=SG4 TRAF SGSN SG4 Data Volume in TREC 0 Shows the data volume uplink and downlink for a specific TREC. 1 day >=SG4 TRAF SGSN SG4 Data Volumes in TREC 2 Shows the data volume uplink and downlink for a specific TREC. 24 h >=SG4 TRAF SGSN SG4 Data Volume in TREC 2 Shows the data volume uplink and downlink for a specific TREC. 1 day >=SG4 TRAF SGSN SG4 Data Volumes in TREC 7 Shows the data volume uplink and downlink for a specific TREC. 1 day >=SG4 TRAF SGSN SG4 Data Volumes in TREC 4 Shows the data volume uplink and downlink for a specific TREC.) Id:0900d805809551ce DN05148836 Issue 2-2 . 24 h >=SG4 TRAF SGSN SG4 Data Volume in TREC 7 Shows the data volume uplink and downlink for a specific TREC. 24 h >=SG4 TRAF SGSN SG4 Data Volume in TREC 5 Shows the data volume uplink and downlink for a specific TREC. 24 h >=SG4 TRAF SGSN SG4 Data Volume in TREC 4 Shows the data volume uplink and downlink for a specific TREC. 1 day >=SG4 TRAF SGSN SG4 Data Volumes in TREC 5 Shows the data volume uplink and downlink for a specific TREC. 24 h >=SG4 TRAF SGSN SG4 Data Volume in TREC 8 Shows the data volume uplink and downlink for a specific TREC.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph Description Time Class SGSN version TRAF SGSN SG4 Data Volumes in TREC 0 Shows the data volume uplink and downlink for a specific TREC. 1 day >=SG4 TRAF SGSN SG4 Data Volumes in TREC 8 Shows the data volume uplink and downlink for a specific TREC. 24 h >=SG4 TRAF SGSN SG4 Data Volume in TREC 3 Shows the data volume uplink and downlink for a specific TREC. 1 day >=SG4 TRAF SGSN SG4 Data Volumes in TREC 9 Shows the data volume uplink and downlink for a specific TREC. 1 day / 24 h / 30 min >=SG4 Table 11 152 Graph descriptions for 2G (Cont. 24 h >=SG4 TRAF SGSN SG4 Data Volume in TREC 9 Shows the data volume uplink and downlink for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Error Causes in TREC 6 Shows the error cause distribution for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Error Causes in TREC 5 Shows the error cause distribution for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 PDP Context Activation in APNs in TREC 8 Shows the number of PDP Context activations for each APN name for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 PDP Context Activation in APNs in TREC 2 Shows the number of PDP Context activations for each APN name for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 PDP Context Activation in APNs in TREC 4 Shows the number of PDP Context activations for each APN name for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 PDP Context Activation in APNs in TREC 7 Shows the number of PDP Context activations for each APN names for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Error Causes in TREC 3 Shows the error cause distribution for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Error Causes in TREC 4 Shows the error cause distribution for a specific TREC. 1 day / 24 h / 30 min >=SG4 Table 11 Graph descriptions for 2G (Cont. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 PDP Context Activation in APNs in TREC 3 Shows the number of PDP Context activations for each APN name for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Error Causes in TREC 9 Shows the error cause distribution for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 PDP Context Activation in APNs in TREC 5 Shows the number of PDP Context activations for each APN name for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 PDP Context Activation in APNs in TREC 6 Shows the number of PDP Context activations for each APN name for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Error Causes in TREC 2 Shows the error cause distribution for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 PDP Context Activation in APNs in TREC 0 Shows the number of PDP Context activations for each APN name for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Error Causes in TREC 7 Shows the error cause distribution for a specific TREC.) DN05148836 Issue 2-2 Id:0900d805809551ce 153 .Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Graph Description Time Class SGSN version TRAF SGSN SG4 Error Causes in TREC 1 Shows the error cause distribution for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 PDP Context Activation in APNs in TREC 1 Shows the number of PDP Context activations for each APN name for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Error Causes in TREC 8 Shows the error cause distribution for a specific TREC. 1 day >=SG4 TRAF SGSN SG4 Average Load / WO-EX Computer Unit Shows the average load of each WO-EX (working executing state) object unit processor group. 1 day >=SG4 TRAF SGSN SG4 Pagings / PAPU / RAC Shows the distribution of pagings for the RACs under a certain PAPU. 30 min >=SG4 TRAF SGSN SG4 Data Transfer / Logical PAPU Shows data amount transferred uplink and downlink in kilobytes through each logical PAPU. Table 11 154 Graph descriptions for 2G (Cont. 1 day >=SG4 TRAF SGSN SG4 Pagings / PAPU Shows the number of pagings for each PAPU. 1 day >=SG4 TRAF SGSN SG4 Pagings / LAC / RAC Shows the distribution of pagings for the RACs under a certain LAC. 1 day / 24 h >=SG4 TRAF SGSN SG4 Uplink Data Transfer / Logical PAPU Shows data amount transferred uplink in kilobytes through each logical PAPU. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Data Transfer / Physical PAPU Shows data amount transferred uplink and downlink in kilobytes through each logical PAPU. 30 min >=SG4 TRAF SGSN SG4 Average Load / SP-EX Computer Unit Shows the average load of certain SP-EX (spare executing state) object unit processors. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Downlink Data Transfer / Logical PAPU Shows data amount transferred downlink in kilobytes through each logical PAPU. 30 min >=SG4 TRAF SGSN SG4 Peak Load / SP-EX Computer Unit Name Shows the peak load of certain SP-EX (spare executing state) object unit processors. 30 min >=SG4 TRAF SGSN SG4 Average Load / WO-EX Computer Unit Name Shows the average load of each WO-EX (working executing state) object unit processor. 1 day / 24 h / 30 min >=SG4 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Downlink Shows data amount transferred downlink in Data Transfer / Physical PAPU kilobytes through each physical PAPU. 30 min >=SG4 TRAF SGSN SG4 Average Load / SP-EX Computer Unit Name Shows the average load of each SP-EX (spare executing state) object unit processor group.) Id:0900d805809551ce DN05148836 Issue 2-2 . 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Uplink Data Transfer / Physical PAPU Shows data amount transferred uplink in kilobytes through each physical PAPU. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Pagings / LAC Shows the number of pagings for each LAC. 30 min >=SG4 TRAF SGSN SG4 Peak Load / WO-EX Computer Unit Name Shows the peak load of each WO-EX (working executing state) object unit processor.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph Description Time Class SGSN version TRAF SGSN SG4 PDP Context Activation in APNs in TREC 9 Shows the number of PDP Context activations for each APN name for a specific TREC. 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 Discarded Packets / Physical PAPU Shows amount of discarded data packets uplink and downlink through each physical PAPU.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Graph Description Time Class SGSN version TRAF SGSN SG4 Data Packet Transfer / Physical PAPU Shows amount of transferred data packets uplink and downlink through each physical PAPU.) DN05148836 Issue 2-2 Id:0900d805809551ce 155 . 1 day / 24 h / 30 min >=SG4 TRAF SGSN SG4 TREC 0 Usage Per Cells Shows the number of PDP Context activations for each Cell names for the TREC 0 1 day >=SG5 TRAF SGSN SG4 TREC 1 Usage Per Cells Shows the number of PDP Context activations for each Cell names for the TREC 1 1 day >=SG5 TRAF SGSN SG4 TREC 2 Usage Per Cells Shows the number of PDP Context activations for each Cell names for the TREC 2 1 day >=SG5 TRAF SGSN SG4 TREC 3 Usage Per Cells Shows the number of PDP Context activations for each Cell names for the TREC 3 1 day >=SG5 TRAF SGSN SG4 TREC 4 Usage Per Cells Shows the number of PDP Context activations for each Cell names for the TREC 4 1 day >=SG5 TRAF SGSN SG4 TREC 5 Usage Per Cells Shows the number of PDP Context activations for each Cell names for the TREC 5 1 day >=SG5 TRAF SGSN SG4 TREC 6 Usage Per Cells Shows the number of PDP Context activations for each Cell names for the TREC 6 1 day >=SG5 TRAF SGSN SG4 TREC 7 Usage Per Cells Shows the number of PDP Context activations for each Cell names for the TREC 7 1 day >=SG5 TRAF SGSN SG4 TREC 8 Usage Per Cells Shows the number of PDP Context activations for each Cell names for the TREC 8 1 day >=SG5 TRAF SGSN SG4 TREC 9 Usage Per Cells Shows the number of PDP Context activations for each Cell names for the TREC 9 1 day >=SG5 TRAF SGSN SG4 TREC 0 Errors Per Cells Shows the percentages distribution of error causes for a certain Cell for TREC 0 1 day >=SG5 TRAF SGSN SG4 TREC 1 Errors Per Cells Shows the percentages distribution of error causes for a certain Cell for TREC 1 1 day >=SG5 TRAF SGSN SG4 TREC 2 Errors Per Cells Shows the percentages distribution of error causes for a certain Cell for TREC 2 1 day >=SG5 TRAF SGSN SG4 TREC 3 Errors Per Cells Shows the percentages distribution of error causes for a certain Cell for TREC 3 1 day >=SG5 TRAF SGSN SG4 TREC 4 Errors Per Cells Shows the percentages distribution of error causes for a certain Cell for TREC 4 1 day >=SG5 TRAF SGSN SG4 TREC 5 Errors Per Cells Shows the percentages distribution of error causes for a certain Cell for TREC 5 1 day >=SG5 TRAF SGSN SG4 TREC 6 Errors Per Cells Shows the percentages distribution of error causes for a certain Cell for TREC 6 1 day >=SG5 TRAF SGSN SG4 TREC 7 Errors Per Cells Shows the percentages distribution of error causes for a certain Cell for TREC 7 1 day >=SG5 TRAF SGSN SG4 TREC 8 Errors Per Cells Shows the percentages distribution of error causes for a certain Cell for TREC 8 1 day >=SG5 Table 11 Graph descriptions for 2G (Cont. 1 day >=SG5 TRAF SGSN SG4 Pr5 Average Load / PAPU Shows the average load of BSSGP buffer utilisation of selected PAPU in priority 5.1 day isation. which has passed MS and BVC flow control for each Cell in a certain RAC. which has passed MS and BVC flow control for each LAC 1 day >=SG5 TRAF SGSN SG4 Passed Data in RAC Shows data in kilobytes. which has passed MS and BVC flow control and discarded packets due MS-BVC flow control for each RAC in a certain LAC.1 day isation.1 day isation. Current value and previous peak value are compared every 30 seconds in priority 3 >=SG5 TRAF SGSN SG4 Pr4 Peak Load / PAPU Shows the peak value of BSSGP buffer util. 1 day >=SG5 TRAF SGSN SG4 Pr1 Average Load / PAPU Shows the average load of BSSGP buffer utilisation of selected PAPU in priority 1. 1 day >=SG5 TRAF SGSN SG4 Discarded Packets in LAC Shows the discarded packets due MS-BVC flow control for each LAC 1 day >=SG5 TRAF SGSN SG4 Discarded Packets in RAC Shows the discarded packets due MS-BVC 1 day flow control for each RAC in a certain LAC. 1 day >=SG5 TRAF SGSN SG4 BSSGP Physical PAPUs This field shows the physical index of papu. 1 day >=SG5 TRAF SGSN SG4 Passed Data in Cell Shows data in kilobytes. >=SG5 TRAF SGSN SG4 Discarded Packets in Cell Shows the discarded packets due MS-BVC flow control for each Cell in a certain RAC.) Id:0900d805809551ce DN05148836 Issue 2-2 . 1 day >=SG5 TRAF SGSN SG4 Pr2 Average Load / PAPU Shows the average load of BSSGP buffer utilisation of selected PAPU in priority 2. 1 day >=SG5 TRAF SGSN SG4 Pr1 Peak Load / PAPU Shows the peak value of BSSGP buffer util. 1 day >=SG5 TRAF SGSN SG4 Pr3 Average Load / PAPU Shows the average load of BSSGP buffer utilisation of selected PAPU in priority 3. Current value and previous peak value are compared every 30 seconds in priority 1 >=SG5 TRAF SGSN SG4 Pr2 Peak Load / PAPU Shows the peak value of BSSGP buffer util.1 day isation.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph Description Time Class SGSN version TRAF SGSN SG4 TREC 9 Errors Per Cells Shows the percentages distribution of error causes for a certain Cell for TREC 9 1 day >=SG5 TRAF SGSN SG4 Passed Data in LAC Shows data in kilobytes. Current value and previous peak value are compared every 30 seconds in priority 4 >=SG5 Table 11 156 Graph descriptions for 2G (Cont. Current value and previous peak value are compared every 30 seconds in priority 2 >=SG5 TRAF SGSN SG4 Pr3 Peak Load / PAPU Shows the peak value of BSSGP buffer util. 1 day >=SG5 TRAF SGSN SG4 Pr4 Average Load / PAPU Shows the average load of BSSGP buffer utilisation of selected PAPU in priority 4. 1 day fier (NS-VCI) under certain NSEI.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Description TRAF SGSN SG4 Pr5 Peak Load / PAPU Shows the peak value of BSSGP buffer util. 1 day >=SG5 TRAF SGSN SG4 Pr3 Lost Data / PAPU Shows discarded downlink bytes in BSSGP due to buffer overflow or RED in priority 3. 1 day >=SG5 TRAF SGSN SG4 Pr3 Dropped Packets / PAPU Shows the amount in bytes of how much data has been dropped due to redundancy elimination in priority 3. 1 day >=SG5 TRAF SGSN SG4 Pr2 Lost Data / PAPU Shows discarded downlink bytes in BSSGP due to buffer overflow or RED in priority 2. 1 day >=SG5 TRAF SGSN SG4 Pr2 Dropped Packets / PAPU Shows the amount in bytes of how much data has been dropped due to redundancy elimination in priority 2.) DN05148836 Issue 2-2 Id:0900d805809551ce 157 .1 day isation. Current value and previous peak value are compared every 30 seconds in priority 5 >=SG5 TRAF SGSN SG4 Pr1 Lost Data / PAPU Shows discarded downlink bytes in BSSGP due to buffer overflow or RED in priority 1. 1 day >=SG5 TRAF SGSN SG4 IP Passed Data Data in kilobytes which has passed IP NSVC control 1 day >=SG5 Table 11 Time Class SGSN version Graph Graph descriptions for 2G (Cont. 1 day >=SG5 TRAF SGSN SG4 Pr5 Lost Data / PAPU Shows discarded downlink bytes in BSSGP due to buffer overflow or RED in priority 5. 1 day >=SG5 TRAF SGSN SG4 CIR Overflow Discarded packets due CIR overflow. 1 day >=SG5 TRAF SGSN SG4 Pr4 Lost Data / PAPU Shows discarded downlink bytes in BSSGP due to buffer overflow or RED in priority 4. 1 day >=SG5 TRAF SGSN SG4 Pr5 Dropped Packets / PAPU Shows the amount in bytes of how much data has been dropped due to redundancy elimination in priority 5. Identifier of a network service virtual connection (NSVC) within the serving GPRS support node (SGSN) having end-to-end significance across the Gb interface >=SG5 TRAF SGSN SG4 Fr Passed Data Data in kilobytes which has passed frame relay NS-VC control. 1 day >=SG5 TRAF SGSN SG4 NSEI Network Service Entity Identifier (NSEI) Identifier of a network service entity having end-to-end significance across the Gb interface 1 day >=SG5 TRAF SGSN SG4 NSVCI Network Service Virtual Connection Identi. 1 day >=SG5 TRAF SGSN SG4 Pr4 Dropped Packets / PAPU Shows the amount in bytes of how much data has been dropped due to redundancy elimination in priority 4. 1 day >=SG5 TRAF SGSN SG4 Pr1 Dropped Packets / PAPU Shows the amount in bytes of how much data has been dropped due to redundancy elimination in priority 1. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 Attaches 2G This graph shows the number of successful and unsuccessful 2G Attaches.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Graph Description Time Class SGSN version TRAF SGSN SG4 IG Shared Data Data in kilobytes borrowed from another fr NS-VC control 1 day >=SG5 TRAF SGSN SG4 OG Shared Data Data in kilobytes borrowed to another fr NS. For example. 30 min >=SG6 TRAF SGSN SG6 PDP Context Modifications 2G This graph shows the number of successful and unsuccessful 2G PDP Context Modifications. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 2G PDP Context Deactivations Unsuccessful This graph shows the number of unsuccessful 1 day / 24 h / 2G PDP Context Deactivations that may need 30 min operator’s attention for a potential problem in the network. 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause >=SG6 TRAF SGSN SG6 2G RA Updates Unsuccessful This graph shows the number of unsuccessful 2G RA (Routing Area) updates. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 2G PDP Context Activations Unsuccessful This graph shows the number of unsuccessful 2G PDP Context Activations 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 2G PDP Context Modifications Unsuccessful This graph shows the number of unsuccessful 2G PDP Context Modifications.1 day bytes for each PAPU. 1 day >=SG5 Table 11 Graph descriptions for 2G (Cont. 1 day >=SG5 TRAF SGSN SG4 GTP Passed Data at GTP / PAPU This graph shows GTP passed data in kilo.) The following table lists the SG combined graphs Graph Description Time Class SGSN Version TRAF SGSN SG6 PDP Context Acti. Here several error causes that do not need special attention from the operator have also been filtered out.This graph shows the number of successful 1 day / 24 h / vations 2G and unsuccessful 2G PDP Context Activations. >=SG6 Table 12 158 1 day / 24 h / 30 min Graph descriptions for SG combined graphs Id:0900d805809551ce DN05148836 Issue 2-2 . 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 PDP Context Deactivations 2G This graph shows the number of successful and unsuccessful 2G PDP Context Deactivations. >=SG5 TRAF SGSN SG4 Discarded Packets Between RAN and SGSN / PAPU This graph shows discarded packets between RAN and SGSN (Gb interface) for each PAPU. 1 day >=SG5 TRAF SGSN SG4 Discarded Packets at GTP / PAPU This graph shows GTP discarded packets for each PAPU.1 day VC control >=SG5 TRAF SGSN SG4 Passed Data Between RAN and SGSN / PAPU This graph shows passed data in kilobytes between RAN and SGSN (Gb interface) for each PAPU. For example. if there has been one unsuccessful modification and 99 successful modifications. the graph will show 1% value. the graph will show 1% value. For example. For example. For example. 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause TRAF SGSN SG6 2G PDP Context Activations Unsuccessful % This graph shows the percentage of unsuccessful 2G PDP Context Activations cumulatively for the time period. 1 day / 24 h / 30 min >=SG6 Here several error causes that do not need special attention from the operator have also been filtered out. 1 day / 24 h / 30 min >=SG6 For example. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 2G RA Updates Unsuccessful % 1 day / 24 h / This graph shows the percentage of unsuccessful 2G RA (Routing Area) updates cumula. the graph will show 1% value >=SG6 TRAF SGSN SG6 2G PDP Context Deactivations Unsuccessful % This graph shows the percentage of unsuccessful 2G PDP Context Deactivations that may need operator’s attention for a potential problem in the network.) DN05148836 Issue 2-2 Id:0900d805809551ce 159 . 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 2G PDP Context Modifications Unsuccessful % 1 day / 24 h / This graph shows the percentage of unsuccessful 2G PDP Context Modifications cumula. if there has been one unsuccessful Deactivation and 99 successful Deactivations.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG6 2G Attaches Unsuccessful This graph shows the number of unsuccessful 2G attaches that may need operator’s attention for a potential problem in the network. the graph will show 1% value. For example. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 2G PDP Context Modifications This graph shows the number of successful and unsuccessful 2G PDP Context Modifications. the graph will show 1% value.30 min tively for the time period. Also. >=SG6 TRAF SGSN SG6 2G Attaches Unsuccessful % This graph shows the percentage of unsuccessful 2G Attaches cumulatively for the time period.30 min tively for the time period. if there has been one unsuccessful activation and 99 successful activations. if there has been one unsuccessful RA update and 99 successful RA updates. if there has been one unsuccessful Attach and 99 successful Attaches. Here several error causes that do not need special attention from the operator have also been filtered out. Table 12 Graph descriptions for SG combined graphs (Cont. other values indicate a failure in RA update 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 PDP Context Acti. 30 min >=SG6 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 PDP Context Modifications 3G Table 12 160 This graph shows the number of successful and unsuccessful 3G PDP Context Modifications. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 2G Attaches / Error Cause This graph shows the Error Cause codes for 2G Attaches. Successful RA (Routing area) updates have always Error Cause code 0xFFFFFF00. other values indicate a failure in PDP Context Modification.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG6 2G PDP Context Modifications / Error Cause This graph shows the Error Cause codes for 2G PDP Context Modifications. other values indicate a failure in PDP Context Deactivation. Place the cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. Place the cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. Successful PDP Context Deactivations have always Error Cause code 0xFFFFFF00. Place the cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. Successful PDP Context Modifications have always Error Cause code 0xFFFFFF00. other values indicate a failure in Attach 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 2G RA Updates This graph shows the number of successful and unsuccessful 2G RA (Routing Area) updates. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 2G PDP Context Deactivations This graph shows the number of successful and unsuccessful 2G PDP Context Deactivations. Place the cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. >=SG6 TRAF SGSN SG6 2G Attaches This graph shows the number of successful and unsuccessful 2G Attaches. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 2G PDP Context Deactivations / Error Cause 1 day / 24 h / This graph shows the Error Cause codes for 30 min 2G PDP Context Deactivations. Successful attaches have always Error Cause code 0xFFFFFF00.This graph shows the number of successful 1 day / 24 h / vations 3G and unsuccessful 3G PDP Context Activations.) Id:0900d805809551ce DN05148836 Issue 2-2 . Graph descriptions for SG combined graphs (Cont. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 2G RA Updates / Error Cause This graph shows the Error Cause codes for 2G RA (Routing Area) updates. 1 day / 24 h / 30 min >=SG6 Here several error causes that do not need special attention from the operator have also been filtered out. >=SG6 Table 12 Graph descriptions for SG combined graphs (Cont. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 3G PDP Context Deactivations Unsuccessful This graph shows the number of unsuccessful 1 day / 24 h / 3G PDP Context Deactivations that may need 30 min operator’s attention for a potential problem in the network. For example. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 3G PDP Context Activations Unsuccessful % This graph shows the percentage of unsuccessful 3G PDP Context Activations cumulatively for the time period. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 3G PDP Context Activations Unsuccessful This graph shows the number of unsuccessful 3G PDP Context Activations. the graph will show 1% value. the graph will show 1% value.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG6 PDP Context Deactivations 3G This graph shows the number of successful and unsuccessful 3G PDP Context Deactivations that may need operator’s attention for a potential problem in the network. if there has been one unsuccessful Modification and 99 successful Modifications. 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause TRAF SGSN SG6 Attaches 3G This graph shows the number of successful and unsuccessful 3G Attaches. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 3G Attaches Unsuccessful This graph shows the number of unsuccessful 3G attaches. Here several error causes that do not need special attention from the operator have also been filtered out.) DN05148836 Issue 2-2 Id:0900d805809551ce 161 . For example. 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause >=SG6 TRAF SGSN SG6 3G RA Updates Unsuccessful This graph shows the number of unsuccessful 3G RA (Routing Area) updates. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 3G PDP Context Modifications Unsuccessful % 1 day / 24 h / This graph shows the percentage of unsuccessful 3G PDP Context Modifications cumula.30 min tively for the time period. if there has been one unsuccessful activation and 99 successful activations. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 3G PDP Context Modifications Unsuccessful This graph shows the number of unsuccessful 3G PDP Context Modifications. For example. For example. Successful PDP Context Deactivations have always Error Cause code 0xFFFFFF00. Here several error causes that do not need special attention from the operator have also been filtered out 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 3G RA Updates Unsuccessful % 1 day / 24 h / This graph shows the percentage of unsuccessful 3G RA (Routing Area) updates cumula. >=SG6 For example. if there has been one unsuccessful Deactivation and 99 successful Deactivations. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 3G PDP Context Deactivations / Error Cause 1 day / 24 h / This graph shows the Error Cause codes for 30 min 3G PDP Context Deactivations.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG6 3G PDP Context Deactivations Unsuccessful % This graph shows the percentage of unsuccessful 3G PDP Context Deactivations that may need operator’s attention for a potential problem in the network. other values indicate a failure in PDP Context Deactivation. other values indicate a failure in PDP Context Modification. Place the cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. For example. if there has been one unsuccessful attach and 99 successful attaches. >=SG6 TRAF SGSN SG6 3G Attaches This graph shows the number of successful and unsuccessful 3G Attaches. 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause. the graph will show 1% value.30 min tively for the current day. if there has been one unsuccessful RA update and 99 successful RA updates. Also. the graph will show 1% value. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 3G PDP Context Modifications This graph shows the number of successful and unsuccessful 3G PDP Context Modifications. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 3G PDP Context Modifications / Error Cause This graph shows the Error Cause codes for 3G PDP Context Modifications. Successful PDP Context Modifications have always Error Cause code 0xFFFFFF00. Table 12 162 1 day / 24 h / 30 min Graph descriptions for SG combined graphs (Cont. >=SG6 TRAF SGSN SG6 3G Attaches Unsuccessful % This graph shows the percentage of unsuccessful 3G Attaches cumulatively for the current day. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 3G PDP Context Deactivations This graph shows the number of successful and unsuccessful 3G PDP Context Deactivations. Place the cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. the graph will show 1% value.) Id:0900d805809551ce DN05148836 Issue 2-2 . For example. ) DN05148836 Issue 2-2 Id:0900d805809551ce 163 .3G. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 RA Updates 2G This graph shows the number of successful and unsuccessful 2G RA (Routing Area) updates. 30 min >=SG6 TRAF SGSN SG6 2G PDP Context Activations / Error Cause 1 day / 24 h / This graph shows the Error Cause codes for 2G PDP Context Activations. Successful PDP Context Activations have always Error Cause code 0xFFFFFF00. >=SG6 TRAF SGSN SG6 3G PDP Context Activations This graph shows the number of successful 1 day / 24 h / and unsuccessful 3G PDP Context Activations. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 RA Update Types This graph shows the RA update types. I-HSPA RA (Routing Area) updates. 30 min >=SG6 TRAF SGSN SG6 3G PDP Context Activations / Error Cause This graph shows the Error Cause codes for 3G PDP Context Activations. Place the cursor 30 min on top of Error Cause value on x-axis to show the description of the Error Cause code. Successful Attaches has always Error Cause code 0xFFFFFF00. >=SG7 Table 12 Graph descriptions for SG combined graphs (Cont. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 3G RA Updates / Error Cause This graph shows the Error Cause codes for 3G RA (Routing Area) updates. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 2G PDP Context Activations This graph shows the number of successful 1 day / 24 h / and unsuccessful 2G PDP Context Activations.30 min tions. 1 day / 24 h / 30 min >=SG6 1 day / 24 h / TRAF SGSN SG7 PDP Context Acti. Successful RA (Routing area) updates have always Error Cause code 0xFFFFFF00.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG6 3G Attaches / Error Cause This graph shows the Error Cause codes for 3G Attaches. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 3G RA Updates This graph shows the number of successful and unsuccessful 3G RA (Routing Area) updates. Place the cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. Place the cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. other values indicate a failure in RA update. Successful PDP Context Activations have always Error Cause code 0xFFFFFF00. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 RA Updates 3G This graph shows the number of successful and unsuccessful 3G RA (Routing Area) updates. other values indicate a failure in PDP Context Deactivation. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG6 2G/3G/I-HSPA RA Updates This graph shows the number of successful and unsuccessful 2G. other values indicate a failure in Attach.This graph shows the number of successful vations I-HSPA and unsuccessful I-HSPA PDP Context Activa. other values indicate a failure in PDP Context Modification. Place the cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. 1 day / 24 h / 30 min HSPA PDP context deactivations. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 I-HSPA PDP Context Deactivations Unsuccessful This graph shows the number of unsuccessful I-HSPA PDP Context Deactivations that may need operator’s attention for a potential problem in the network. Successful PDP context deactivations always have an error cause code equal to 0xFFFFFF00. For example. TRAF SGSN SG7 I-HSPA RA Updates Unsuccessful This graph shows the number of unsuccessful I-HSPA RA (Routing Area) updates. >=SG7 TRAF SGSN SG7 PDP Context Deactivations I-HSPA This graph shows the number of successful and unsuccessful I-HSPA PDP Context Deactivations. 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause.) Id:0900d805809551ce DN05148836 Issue 2-2 . 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 RA Updates IHSPA This graph shows the number of successful and unsuccessful I-HSPA RA (Routing Area) updates. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 Attaches I-HSPA This graph shows the number of successful and unsuccessful I-HSPA Attaches. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 RA Updates IHSPA This graph shows the number of successful and unsuccessful I-HSPA RA (Routing Area) updates.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Time Class SGSN Version Graph Description TRAF SGSN SG7 PDP Context Modifications I-HSPA 1 day / 24 h / This graph shows the number of successful and unsuccessful I-HSPA PDP Context Modifi. Other values indicate a failure in PDP context deactivation.30 min cations. 1 day / 24 h / 30 min >=SG7 Here several error causes that do not need special attention from the operator have also been filtered out. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 I-HSPA Attaches Unsuccessful This graph shows the number of unsuccessful I-HSPA attaches. 1 day / 24 h / 30 min >=SG7 Table 12 164 Graph descriptions for SG combined graphs (Cont.Place the cursor on top of the error cause value on the xaxis to view the description of the error cause code. >=SG7 TRAF SGSN SG7 I-HSPA PDP Context Modifications Shows the number of successful and unsuccessful\nI-HSPA PDP Context Modifications 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 I-HSPA PDP Context Modifications Unsuccessful This graph shows the number of unsuccessful I-HSPA PDP Context Modifications. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 I-HSPA PDP Context Deactivations This graph shows the number of successful and unsuccessful\nI-HSPA PDP Context Deactivations" 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 I-HSPA PDP Context Deactivations/ Error Cause This graph shows the error cause codes for I. if there has been one unsuccessful activation and 99 successful activations. if there has been one unsuccessful modification and 99 successful modifications. the graph will show 1% value. For example. Place the cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 I-HSPA PDP Context Activations 1 day / 24 h / This graph shows the number of successful and unsuccessful I-HSPA PDP Context Activa. the graph will show 1% value. For example. >=SG7 For example. >=SG7 TRAF SGSN SG7 I-HSPA PDP Context Activations / Error Cause This graph shows the Error Cause codes for I. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 I-HSPA Attaches Unsuccessful % This graph shows the percentage of unsuccessful I-HSPA Attaches cumulatively for the time period.1 day / 24 h / 30 min HSPA PDP Context Activations. 1 day / 24 h / 30 min >=SG7 Table 12 Graph descriptions for SG combined graphs (Cont. For example. Here several error causes that do not need special attention from the operator have also been filtered out. if there has been one unsuccessful RA update and 99 successful RA updates. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 I-HSPA PDP Context Modifications Unsuccessful % This graph shows the percentage of unsuccessful I-HSPA PDP Context Modifications cumulatively for the time period.30 min tions. For example.) DN05148836 Issue 2-2 Id:0900d805809551ce 165 . 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause. Also. if there has been one unsuccessful Attach and 99 successful Attaches. the graph will show 1% value. if there has been one unsuccessful Deactivation and 99 successful Deactivations.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG7 I-HSPA PDP Context Activations Unsuccessful % This graph shows the percentage of unsuccessful I-HSPA PDP Context Activations cumulatively for the time period. the graph will show 1% value 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 I-HSPA PDP Context Deactivations Unsuccessful % 1 day / 24 h / This graph shows the percentage of unsuc30 min cessful I-HSPA PDP Context Deactivations that may need operator’s attention for a potential problem in the network. other values indicate a failure in PDP Context Deactivation. the graph will show 1% value. >=SG7 TRAF SGSN SG7 I-HSPA RA Updates This graph shows the number of successful and unsuccessful I-HSPA RA (Routing Area) updates. TRAF SGSN SG7 I-HSPA RA Updates Unsuccessful % This graph shows the percentage of unsuccessful I-HSPA RA (Routing Area) updates cumulatively for the time period. Successful PDP Context Activations have always Error Cause code 0xFFFFFF00. other values indicate a failure in Attach 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 2G/3G/I-HSPA Total Reported Events This graph shows the total of all the reported events. this graph will show this distribution across different radio access types.) Id:0900d805809551ce DN05148836 Issue 2-2 . 1 day / 24 h >=SG8 TRAF SGSN SG Data Packet Transfer / Physical IPPU This graph shows the amount of data packets transferred uplink and downlink through each physical IPPU.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG7 I-HSPA RA Updates / Error Cause This graph shows the Error Cause codes for IHSPA RA (Routing Area) updates. Place the cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. Successful attaches have always Error Cause code 0xFFFFFF00. Eg: If there are 100 Attaches Event happening and if all 100 have successful error cause. 1 day / 24 h >=SG8 TRAF SGSN SG Uplink Data Transfer / Physical IPPU This graph shows the amount of data transferred uplink in kilobytes through each physical IPPU. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 2G/3G/I-HSPA All Reported Events Percentage This graph shows the percentage of each reported event. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 2G/3G/I-HSPA Radio Access Type % Per Event Per Error Cause 1 day / 24 h / This graph shows the percentage of Radio 30 min Access types for a reported event's error cause. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 2G/3G/I-HSPA Reported Events % Per Ra Access Type This graph shows shows the percentage of reported events per radio access type. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 I-HSPA Attaches / Error Cause This graph shows the Error Cause codes for IHSPA Attaches. 1 day / 24 h >=SG8 Table 12 166 Graph descriptions for SG combined graphs (Cont. 1 day / 24 h >=SG8 TRAF SGSN SG Discarded Packets / Physical IPPU This graph shows the amount of discarded data packets uplink and downlink through each physical IPPU. Successful RA (Routing area) updates have always Error Cause code 0xFFFFFF00. other values indicate a failure in RA update 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 I-HSPA Attaches This graph shows the number of successful and unsuccessful I-HSPA Attaches. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG7 2G/3G/I-HSPA Error Cause Percentage Per Reported Event This graph shows the percentage of error causes for a reported event. 1 day / 24 h >=SG8 TRAF SGSN SG Downlink Data Transfer / Physical IPPU This graph shows the amount of data transferred downlink in kilobytes through each physical IPPU. >=SG7 TRAF SGSN SG Data Transfer / Physical IPPU This graph shows the amount of data transferred uplink in kilobytes through each physical IPPU. Place the cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. This graph shows the number of unsuccessful cessful RA (Routing Area) updates 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G MO SMS Deliveries Unsuccessful This graph shows the number of unsuccessful MO-SMS deliveries 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G MT SMS Deliveries Unsuccessful This graph shows the number of unsuccessful MT-SMS deliveries 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Attaches Unsuccessful This graph shows the number of unsuccessful Attaches 1 day / 24 h / 30 min >=SG6 Table 13 Graph descriptions for 3G SG6 graphs DN05148836 Issue 2-2 Id:0900d805809551ce 167 .Traffica Reference Guide for SGSN Direct Interface Real-time monitoring The following table lists the SG6 3G graphs SGSN Version Graph Description Time Class TRAF SGSN SG 3G PDP Context Activations_ This graph shows the number of successful and unsuccessful\nPDP Context Activations 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Modifications_ This graph shows the number of successful and unsuccessful PDP Context Modifications 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Deactivations_ This graph shows the number of successful and unsuccessful PDP Context Deactivations 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G RA Updates_ This graph shows the number of successful and unsuccessful RA (Routing Area) updates 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G MO SMS Deliveries_ This graph shows the number of successful and unsuccessful MO-SMS deliveries 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G MT SMS Deliveries_ This graph shows the number of successful and unsuccessful MT-SMS deliveries 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Attaches_ This graph shows the number of successful and unsuccessful Attaches 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Detaches_ This graph shows the number of successful and unsuccessful Detaches 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activations Unsuccessful This graph shows the number of unsuccessful PDP Context Activations 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Modifications Unsuccessful This graph shows the number of unsuccessful PDP Context Modifications 1 day / 24 h / 30 min >=SG6 1 day / 24 h / TRAF SGSN SG 3G PDP Context Deac. For example. >=SG6 Here several error causes that do not need special attention from the operator have also been filtered out.This graph shows the number of unsuc30 min tivations Unsuccessful cessful PDP Context Deactivations that may need operator’s attention for a potential problem in the network. 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause TRAF SGSN SG 3G RA Updates Unsuc. if there has been one unsuccessful Deactivation and 99 successful Deactivations. the graph will show 1% value >=SG6 TRAF SGSN SG 3G Attaches Unsuccessful % This graph shows the percentage of unsuccessful Attaches. Table 13 168 Graph descriptions for 3G SG6 graphs (Cont. 30 min For example. Also. For example. 30 min For example.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG 3G Detaches Unsuccessful This graph shows the number of unsuccessful Detaches 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activations Unsuccessful % 1 day / 24 h / This graph shows the percentage of 30 min unsuccessful PDP Context Activations. if there has been one unsuccessful MT-SMS delivery and 99 successful MT-SMS deliveries. if there has been one unsuccessful RA update and 99 successful RA updates. the graph will show 1% value 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Deac. For example. For example. the graph will show 1% value >=SG6 TRAF SGSN SG 3G MO SMS Deliveries Unsuccessful % 1 day / 24 h / This graph shows the percentage of 30 min unsuccessful MO-SMS deliveries. the graph will show 1% value >=SG6 1 day / 24 h / 30 min >=SG6 1 day / 24 h / TRAF SGSN SG 3G RA Updates Unsuc. if there has been one unsuccessful Attach and 99 successful Attaches. if there has been one unsuccessful Activation and 99 successful Activations. the graph will show 1% value >=SG6 TRAF SGSN SG 3G PDP Context Modifications Unsuccessful % 1 day / 24 h / This graph shows the percentage of unsuccessful PDP Context Modifications.) Id:0900d805809551ce DN05148836 Issue 2-2 . if there has been one unsuccessful Modification and 99 successful Modifications.This graph shows the percentage of cessful % unsuccessful RA (Routing Area) updates. the graph will show 1% value. the graph will show 1% value >=SG6 TRAF SGSN SG 3G MT SMS Deliveries Unsuccessful % 1 day / 24 h / This graph shows the percentage of 30 min unsuccessful MT-SMS deliveries. 0xC6 indicatesa regular deactivation procedure from the mobile and is not an unsuccessful PDP context deactivation cause. For example. if there has been one unsuccessful MO-SMS delivery and 99 successful MO-SMS deliveries. For example.This graph shows the percentage of tivations Unsuccessful % unsuccessful PDP Context Deactivations that may need the operator’s attention for a potential problem in the network. Here several error causes that do not need special attention from the operator have also been filtered out. Using this graph you can track the most used SACs for PDP Context Activation. the graph will show 1% value 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activations This graph shows the number of successful and unsuccessful PDP Context Activations cumulatively for the time period 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activations / Error Cause This graph shows the Error Cause codes for PDP Context Activations. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Modifications Unsuccessful / SAC This graph shows the number of unsuccessful PDP Context Modifications for SACs (SAC IDs). Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. For example.) DN05148836 Issue 2-2 Id:0900d805809551ce 169 . if there has been one unsuccessful Detach and 99 successful Detaches.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG 3G Detaches Unsuccessful % This graph shows the percentage of unsuccessful Detaches. Successful PDP Context Activations has error cause code 0x0. Successful PDP Context Modifications has error cause code 0x0. Using this graph you can track the most used SACs for PDP Context Modifications. The SAC with most unsuccessful PDP Context Modifications is the first in the graph. The SACs are listed in order so that the SAC where there has been the most PDP Context Modifications is the first in the graph. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. other values indicate a failure in PDP Context Activation 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activations / SAC This graph shows the SAC (SAC IDs) for PDP Context Activations cumulatively for the time period. Using this graph you can track SACs with most failures in PDP Context Modifications 1 day / 24 h / 30 min >=SG6 Table 13 Graph descriptions for 3G SG6 graphs (Cont. other values indicate a failure in PDP Context Modification 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Modifications / SAC This graph shows the SACs (SAC IDs) for PDP Context Modifications cumulatively for the time period. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Modifications This graph shows the number of successful and unsuccessful PDP Context Modifications cumulatively for the time period 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Modifications / Error Cause This graph shows the Error Cause codes for PDP Context Modifications. The SACs are listed in order so that the SAC where there has been the most PDP Context Activations is the first in the graph. This graph shows the SACs (SAC IDs) for tivations / SAC PDP Context Deactivations cumulatively for the time period.) Id:0900d805809551ce DN05148836 Issue 2-2 . 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause Table 13 170 Graph descriptions for 3G SG6 graphs (Cont. Using this graph you can track SACs with most failures in PDP Context Deactivations. 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause TRAF SGSN SG 3G PDP Context Deac. Here several error causes that do not need special attention from the operator have also been filtered out.This graph shows the number of successtivations ful and unsuccessful PDP Context Deactivations cumulatively for the time period 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Deac. The SAC with most unsuccessful PDP Context Deactivations is the first in the graph. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. Using this graph you can track the most used SACs for PDP Context Deactivations. Regular PDP context deactivation has error cause code 0x24. For example.Real-time monitoring Graph Traffica Reference Guide for SGSN Direct Interface Description Time Class SGSN Version TRAF SGSN SG 3G PDP Context Deac. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Deac.This graph shows unsuccessful PDP Context Deactivations' Error Cause codes tivations Unsuccessful / SAC / Error for the SAC that is selected in the left-hand Cause side graph \'Unsuccessful PDP Context Deactivations / SAC\'. For example.This graph shows the number of unsuctivations Unsuccessful / SAC cessful PDP Context Deactivations for SACs (SAC IDs).This graph shows the Error Cause codes tivations / Error Cause for PDP Context Deactivations. The SACs are listed in order so that the SAC where there has been the most PDP Context Deactivations is the first in the graph. other values indicate a failure in PDP Context Deactivation 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Deac. 1 day / 24 h / 30 min >=SG6 1 day / 24 h / 30 min >=SG6 Here several error causes that do not need special attention from the operator have also been filtered out. Successful PDP Context Deactivations has error cause code 0x0. Using this graph you can track most common Error Cause codes for different SACs for PDP Context Deactivations. The SAC with most unsuccessful MO-SMS deliveries is the first in the graph. Using this graph you can track SACs with most failures in MT-SMS deliveries >=SG6 TRAF SGSN SG 3G MT SMS Deliveries Unsuccessful / SAC / Error Cause This graph shows unsuccessful MT-SMS deliveries' Error Cause codes for the SAC that is selected in the left-hand side graph \'Unsuccessful MT SMS Deliveries / SAC\'. Using this graph you can track the most used SACs for MO-SMS deliveries 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G MO SMS Deliveries Unsuccessful / SAC This graph shows the number of unsuccessful MO-SMS deliveries for SACs (SAC IDs). The SACs are listed in order so that the SAC where there has been the most MT-SMS deliveries is the first in the graph. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G MT SMS Deliveries / SAC This graph shows the SACs (SAC IDs) for MT-SMS deliveries cumulatively for the time period. Using this graph you can track most common Error Cause codes for different SACs for MT-SMS deliveries. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G MO SMS Deliveries This graph shows the number of successful and unsuccessful MO-SMS deliveries cumulatively for the time period 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G MO SMS Deliveries / Error Cause This graph shows the Error Cause codes for MO-SMS deliveries. Place the mouse cursor on top of Error Cause value on xaxis to show the description of the Error Cause code. The SAC with most unsuccessful MTSMS deliveries is the first in the graph. The SACs are listed in order so that the SAC where there has been the most MO-SMS deliveries is the first in the graph. Using this graph you can track SACs with most failures in MO-SMS deliveries 1 day / 24 h / 30 min >=SG6 Table 13 Graph descriptions for 3G SG6 graphs (Cont. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G MO SMS Deliveries / SAC This graph shows the SACs (SAC IDs) for MO-SMS deliveries cumulatively for the time period.) DN05148836 Issue 2-2 Id:0900d805809551ce 171 . Using this graph you can track the most used SACs for MT-SMS deliveries 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G MT SMS Deliveries Unsuccessful / SAC 1 day / 24 h / This graph shows the number of unsuccessful MT-SMS deliveries for SACs (SAC 30 min IDs). Place the mouse cursor on top of Error Cause value on xaxis to show the description of the Error Cause code.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG 3G MT SMS Deliveries This graph shows the number of successful and unsuccessful MT-SMS deliveries cumulatively for the time period 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G MT SMS Deliveries / Error Cause This graph shows the Error Cause codes for MT-SMS deliveries. Real-time monitoring Traffica Reference Guide for SGSN Direct Interface Description TRAF SGSN SG 3G MO SMS Deliveries Unsuccessful / SAC / Error Cause This graph shows unsuccessful MO-SMS 1 day / 24 h / deliveries' Error Cause codes for the SAC 30 min that is selected in the left-hand side graph \'Unsuccessful MO SMS Deliveries / SAC\ '. The LACs are listed in order so that the LAC where there has been the most Detaches is the first in the graph. The LAC with most unsuccessful Attaches is the first in the graph. Using this graph you can track most common Error Cause codes for different LACs for Attaches 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Detaches This graph shows the number of successful and unsuccessful Detaches cumulatively for the time period 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Detaches / Error Cause This graph shows the Error Cause codes for detaches. Using this graph you can track most common Error Cause codes for different SACs for MO-SMS deliveries. Time Class >=SG6 TRAF SGSN SG 3G Detaches / LAC This graph shows the LACs for Detaches cumulatively for the time period. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. Using this graph you can track LACs with most failures in Detaches 1 day / 24 h / 30 min >=SG6 Table 13 172 Time Class SGSN Version Graph Graph descriptions for 3G SG6 graphs (Cont. The LAC with most unsuccessful Detaches is the first in the graph. The LACs are listed in order so that the LAC where there has been the most Attaches is the first in the graph. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code.) Id:0900d805809551ce DN05148836 Issue 2-2 . Using this graph you can track LACs with most failures in Attaches 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Attaches Unsuccessful / LAC / Error Cause This graph shows unsuccessful Attaches' Error Cause codes for the LAC that is selected in the left-hand side graph \ 'Unsuccessful Attaches / LAC\'. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Attaches / LAC This graph shows the LACs for Attaches cumulatively for the time period. >=SG6 TRAF SGSN SG 3G Attaches This graph shows the number of successful and unsuccessful Attaches cumulatively for the time period 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Attaches / Error Cause This graph shows the Error Cause codes for attaches. Using this graph you can track the most used LACs for Attaches 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Attaches Unsuccessful / LAC This graph shows the number of unsuccessful Attaches for LACs. Using this graph you can track the most used LACs for Detaches 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Detaches Unsuccessful / LAC This graph shows the number of unsuccessful Detaches for LACs. The RAC with most unsuccessful RA updates is the first in the graph.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG 3G Detaches Unsuccessful / LAC / Error Cause This graph shows unsuccessful Detaches' Error Cause codes for the LAC that is selected in the left-hand side graph \ 'Unsuccessful Detaches / LAC\'. 1 day / 24 h / 30 min >=SG6 Table 13 Graph descriptions for 3G SG6 graphs (Cont. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G RA Updates / RAC This graph shows the RACs for RA updates cumulatively for the time period. Using this graph you can track the most used RACs for RA updates 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G RA Updates Unsuc. Using this graph you can track most common Error Cause codes for different RACs for RA updates 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Attaches / Mobile Type This graph shows Mobile phone types that are used for Attaches. Mobile phone types are shown in order so that the most used phone type is the first in the graph. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G RA Updates This graph shows the number of successful and unsuccessful RA (Routing Area) updates cumulatively for the time period 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G RA Updates / Error Cause This graph shows the Error Cause codes for RA (Routing Area) updates. The RACs are listed in order so that the RAC where there has been the most RA updates is the first in the graph. This graph can be used to track most used mobile phone types for Attaches 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Attaches / Mobile Type / Error Cause This graph shows Attaches' Error Cause code distribution for the mobile phone type that is currently selected in graph \ 'Attaches / Mobile Type\'.This graph shows the number of unsuccessful / RAC cessful RA updates for RACs. Using this graph you can track most common Error Cause codes for different LACs for Detaches. This graph can be used to track failures in different mobile phone types for Attaches.This graph shows unsuccessful RA cessful / RAC / Error Cause updates' Error Cause codes for the RAC that is selected in the left-hand side graph \'Unsuccessful RA Updates / RAC\'. Using this graph you can track RACs with most failures in RA updates 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G RA Updates Unsuc.) DN05148836 Issue 2-2 Id:0900d805809551ce 173 . 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activations 3 -> APN This graph shows the percentages of load for the APNs. Mobile phone types are shown in order so that the most used phone type is the first in the graph. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activations Unsuccessful / Mobile Type / Error Cause This graph shows PDP Context Activations' Error Cause code distribution for the mobile phone type that is currently selected in graph \'Unsuccessful PDP Context Activations / Mobile Type\'. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming Unsuccessful Attaches This graph shows the percentages of unsuccessful attaches for each operator. Mobile phone types are shown in order so that the most used phone type is the first in the graph. This graph can be used to track most used mobile phone types for failed PDP Context Activations.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG 3G PDP Context Activations / Mobile Type This graph shows Mobile phone types that are used for PDP Context Activations. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful RA Update This graph shows the percentages of unsuccessful RA Updates cumulatively for the time period. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful SMS Deliveries This graph shows the percentages of unsuccessful SMS deliveries cumulatively for the time period. This graph can be used to track most used mobile phone types for PDP Context Activations. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activations 3 This graph shows the number of all PDP Context Activations attempts. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activations 3 -> APN -> Error Cause This graph shows the percentages of error causes for a specific APN.) Id:0900d805809551ce DN05148836 Issue 2-2 . 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful PDP Context Activations This graph shows the percentage of unsuccessful PDP Context Activations cumulatively for the time period. This graph can be used to track failures in different mobile phone types for PDP Context Activations. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activations Unsuccessful / Mobile Type This graph shows Mobile phone types that are used for unsuccessful PDP Context Activations. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful PDP Context Modifications This graph shows the percentages of unsuccessful PDP Context Modifications cumulatively for the time period. 1 day / 24 h / 30 min >=SG6 Table 13 174 Graph descriptions for 3G SG6 graphs (Cont. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming Attaches Attempts This graph shows the number of attaches attempts for each network operator. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming Successful Attaches This graph shows the percentages of successful attaches for each operator. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming Unsuccessful PDP Context Activations This graph shows the percentages of unsuccessful PDP Context Activations for each operator. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming Successful PDP Context Activations This graph shows the percentages of successful PDP Context Activations for each operator.30 min vation for a specific operator. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming PDP Context Activations Attempts 2 -> Mobile Type This graph shows the percentages of mobile types for PDP Context Activation attempts for a specific operator. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Traffic Class 3 QoS Successful Request This graph shows the percentages of fulfilled Requests for a specific traffic class. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Subscriber Data Uplink / APN This graph shows the amount of data sent uplink in kbytes for a specific APN.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG 3G Roaming Unsuccessful Attaches -> Error Cause This graph shows the percentages of error causes for unsuccessful attaches and a specific operator. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming PDP Context Activations Attempts 2 -> Mobile Type -> Error Cause This graph shows the percentages of error causes for PDP Context Activation attempts for a specific mobile type. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Traffic Class 2 QoS Successful Request This graph shows the percentages of fulfilled requests for a specific traffic class. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming Unsuccessful PDP Context Activations -> Error Cause This graph shows the percentages of error 1 day / 24 h / causes for unsuccessful PDP Context Acti. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming PDP Context Activations Attempts This graph shows the number of PDP Context Activation attempts for each network operator. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Subscriber APN Usage This graph shows the distribution of APNs for the PDP Context Activations that occurred. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Uplink and Downlink Data Volume / LAC / RAC This graph shows the data volume uplink and downlink in kbytes for each RAC in a certain LAC. 1 day / 24 h / 30 min >=SG6 Table 13 Graph descriptions for 3G SG6 graphs (Cont. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Uplink and Downlink Data Volume / LAC / RAC / SAC This graph shows the data volume uplink and downlink in kbytes for each SAC in a certain RAC.) DN05148836 Issue 2-2 Id:0900d805809551ce 175 . >=SG6 TRAF SGSN SG 3G Roaming PDP Context Activations Attempts 2 This graph shows the number of PDP Context Activation attempts for each network operator. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Subscriber Data Downlink / APN This graph shows the amount of data sent downlink in kbytes for a specific APN. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Uplink and Downlink Data Volume / LAC This graph shows the data volume uplink and downlink in kbytes for each LAC. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Traffic Class 1 QoS Successful Request This graph shows the percentages of fulfilled Requests for a specific traffic class. ) Id:0900d805809551ce DN05148836 Issue 2-2 . 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Data Volume / Traffic Class 2 This graph shows the data volume uplink and downlink in kbytes for Streaming class. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Data Volume / Traffic Class 1 This graph shows the data volume uplink and downlink in kbytes for Conversational class. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Traffic Class 1 QoS Negotiated This graph shows the percentages of negotiations for a specific traffic class. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Data Volume / Traffic Class 3 This graph shows the data volume uplink 1 day / 24 h / and downlink in kbytes for Interactive class 30 min >=SG6 TRAF SGSN SG 3G Data Volume / Traffic Class 4 This graph shows the data volume uplink and downlink in kbytes for Background class. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Traffic Class 4 QoS Negotiated This graph shows the percentages of negotiations for a specific traffic class. Time Class >=SG6 TRAF SGSN SG 3G Roaming Sessions This graph shows the number of all roaming sessions. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Traffic Class 1 QoS Requested This graph shows the percentages of Requests for a specific traffic class. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Traffic Class 3 QoS Negotiated This graph shows the percentages of negotiations for a specific traffic class. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Traffic Class 4 QoS Requested This graph shows the percentages of Requests for a specific traffic class. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful Roaming Session / Error Cause / Mobile Types This graph shows the percentages distribution of mobile phones type for error causes for abnormally terminated roaming sessions. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Traffic Class 3 QoS Requested This graph shows the percentages of Requests for a specific traffic class. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Traffic Class 2 QoS Negotiated This graph shows the percentages of negotiations for a specific traffic class. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming Attaches / LAC / RAC This graph shows the distribution of Roaming Attaches for the RACs under a certain LAC.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG 3G Traffic Class 4 QoS Successful Request This graph shows the percentages of fulfilled Requests for a specific traffic class. 1 day / 24 h / 30 min >=SG6 Table 13 176 Graph descriptions for 3G SG6 graphs (Cont. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming Attaches / LAC This graph shows the distribution of Roaming Attaches in a each LAC. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Traffic Class 2 QoS Requested This graph shows the percentages of Requests for a specific traffic class. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful Roaming Sessions / Error Cause This graph shows the percentages distribution of error causes for abnormally terminated roaming sessions. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful Roaming Sessions This graph shows the percentages of abnormally terminated roaming sessions. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming PDP Context Activations This graph shows the number of roaming PDP Context Activations 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming PDP Context Modifications This graph shows the number of roaming PDP Context Modifications 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming Attaches / Error Cause This graph shows the distribution of error 1 day / 24 h / 30 min causes for roaming attaches. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful Roaming Attaches / LAC / RAC / Error Cause This graph shows the percentages of error causes for Roaming Attaches that were abnormally terminated per RAC under a specific LAC. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful Roaming Attaches / LAC / RAC This graph shows the distribution of Roaming Attaches that were abnormally terminated for the RACs under a certain LAC. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming Attaches This graph shows the number of roaming attaches. Values usually indicate a failure in roaming PDP Context Activations 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming PDP Context Modifications / Error Cause This graph shows the distribution of error 1 day / 24 h / causes for roaming PDP Context Modifica.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG 3G Unsuccessful Roaming Attaches / LAC This graph shows the distribution of Roaming Attaches that were abnormally terminated for a each LAC. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G APN Data Volume Uplink and Downlink / Mobile Types This graph shows the distribution of uplink and downlink data volumes in kbytes for each mobile types for certain APNs. Values usually indicate a failure in roaming attach >=SG6 TRAF SGSN SG 3G Roaming PDP Context Activations / Error Cause This graph shows the distribution of error causes for roaming PDP Context Activations. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Data Volumes in TREC 0 This graph shows the data volume uplink and downlink in kbytes for a TREC 0 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Data Volumes in TREC 1 This graph shows the data volume uplink and downlink in kbytes for a TREC 1 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Data Volumes in TREC 2 This graph shows the data volume uplink and downlink in kbytes for a TREC 2 1 day / 24 h / 30 min >=SG6 Table 13 Graph descriptions for 3G SG6 graphs (Cont.) DN05148836 Issue 2-2 Id:0900d805809551ce 177 .30 min tions. 30 min >=SG6 TRAF SGSN SG 3G APN Data Volume Uplink and Downlink This graph shows the amount of data sent uplink and downlink in kbytes for each APN. >=SG6 TRAF SGSN SG 3G APN Usage This graph shows the distribution of APNs for the PDP Context Activations that occurred. Values usually indicate a failure in roaming PDP Context Modifications. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G APN Usage / Mobile Types This graph shows the distribution of mobile 1 day / 24 h / phone types that are used for certain APN. Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG 3G Data Volumes in TREC 3 This graph shows the data volume uplink and downlink in kbytes for a TREC 3 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Data Volumes in TREC 4 This graph shows the data volume uplink and downlink in kbytes for a TREC 4 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Data Volumes in TREC 5 This graph shows the data volume uplink and downlink in kbytes for a TREC 5 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Data Volumes in TREC 6 This graph shows the data volume uplink and downlink in kbytes for a TREC 6 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Data Volumes in TREC 7 This graph shows the data volume uplink and downlink in kbytes for a TREC 7 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Data Volumes in TREC 8 This graph shows the data volume uplink and downlink in kbytes for a TREC 8 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Data Volumes in TREC 9 This graph shows the data volume uplink and downlink in kbytes for a TREC 9 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Error Causes in TREC 0 This graph shows the percentages distribution of error causes for the TREC 0 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Error Causes in TREC 1 This graph shows the percentages distribution of error causes for the TREC 1 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Error Causes in TREC 2 This graph shows the percentages distribution of error causes for the TREC 2 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Error Causes in TREC 3 This graph shows the percentages distribution of error causes for the TREC 3 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Error Causes in TREC 4 This graph shows the percentages distribution of error causes for the TREC 4 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Error Causes in TREC 5 This graph shows the percentages distribution of error causes for the TREC 5 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Error Causes in TREC 6 This graph shows the percentages distribution of error causes for the TREC 6 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Error Causes in TREC 7 This graph shows the percentages distribution of error causes for the TREC 7 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Error Causes in TREC 8 This graph shows the percentages distribution of error causes for the TREC 8 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Error Causes in TREC 9 This graph shows the percentages distribution of error causes for the TREC 9 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation Load in TREC 0 This graph shows the percentages of PDP context activation load for the TREC 0 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation Load in TREC 1 This graph shows the percentages of PDP context activation load for theTREC 1 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation Load in TREC 2 This graph shows the percentages of PDP context activation load for the TREC 2 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation Load in TREC 3 This graph shows the percentages of PDP context activation load for the TREC 3 1 day / 24 h / 30 min >=SG6 Table 13 178 Graph descriptions for 3G SG6 graphs (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 . Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG 3G PDP Context Activation Load in TREC 4 This graph shows the percentages of PDP context activation load for the TREC 4 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation Load in TREC 5 This graph shows the percentages of PDP context activation load for the TREC 5 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation Load in TREC 6 This graph shows the percentages of PDP context activation load for the TREC 6 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation Load in TREC 7 This graph shows the percentages of PDP context activation load for the TREC 7 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation Load in TREC 8 This graph shows the percentages of PDP context activation load for the TREC 8 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation Load in TREC 9 This graph shows the percentages of PDP context activation load for the TREC 9 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation in APNs in TREC 0 This graph shows the number of PDP context activations for each APN names for the TREC 0 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation in APNs in TREC 1 This graph shows the number of PDP context activations for each APN names for the TREC 1 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation in APNs in TREC 2 This graph shows the number of PDP context activations for each APN names for the TREC 2 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation in APNs in TREC 3 This graph shows the number of PDP context activations for each APN names for the TREC 3 Time Class >=SG6 TRAF SGSN SG 3G PDP Context Activation in APNs in TREC 4 This graph shows the number of PDP context activations for each APN names for the TREC 4 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation in APNs in TREC 5 This graph shows the number of PDP context activations for each APN names for the TREC 5 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation in APNs in TREC 6 This graph shows the number of PDP context activations for each APN names for the TREC 6 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation in APNs in TREC 7 This graph shows the number of PDP context activations for each APN names for the TREC 7 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation in APNs in TREC 8 This graph shows the number of PDP context activations for each APN names for the TREC 8 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activation in APNs in TREC 9 This graph shows the number of PDP context activations for each APN names for the TREC 9 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful Roaming Attaches This graph shows the percentages of abnormally terminated roaming attaches 1 day / 24 h / 30 min >=SG6 Table 13 Graph descriptions for 3G SG6 graphs (Cont.) DN05148836 Issue 2-2 Id:0900d805809551ce 179 . Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG 3G Unsuccessful Roaming PDP Context Activations This graph shows the percentages of abnormally terminated PDP context activation sessions. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful Roaming PDP Context Modifications This graph shows the percentages of abnormally terminated PDP context modification sessions.) Id:0900d805809551ce DN05148836 Issue 2-2 . 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 0 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 0 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 1 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 1 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 2 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 2 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 3 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 3 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 4 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 4 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 5 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 5 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 6 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 6 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 7 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 7 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 8 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 8 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 9 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 9 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 0 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 0 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 1 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 1 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 2 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 2 1 day / 24 h / 30 min >=SG6 Table 13 180 Graph descriptions for 3G SG6 graphs (Cont. Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG 3G TREC 3 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 3 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 4 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 4 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 5 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 6 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 6 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 6 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 7 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 7 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 8 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 8 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G TREC 9 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 9 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activations 4 This graph shows the number of all PDP Context Activations attempts. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful MT SMS Deliveries This graph shows the percentages of unsuccessful MT SMS deliveries cumulatively for the time period. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming Unsuccessful Detaches This graph shows the percentages of unsuccessful detaches for each operator. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activations 4 -> APN -> SAC This graph shows the percentages of load for the SACs under the certain APN. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming Detaches Attempts This graph shows the number of Detaches attempts for each network operator. 1 day / 24 h / 30 min >=SG6 Table 13 Graph descriptions for 3G SG6 graphs (Cont. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming Successful Detaches This graph shows the percentages of successful detaches for each operator. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming Unsuccessful Detaches -> Error Cause This graph shows the percentages of error causes for unsuccessful detaches and a specific operator. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful MO SMS Deliveries This graph shows the percentages of unsuccessful MO SMS deliveries cumulatively for the time period. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activations 4 -> APN -> Error Cause This graph shows the percentages of error causes for a specific SAC under the certain APN.) DN05148836 Issue 2-2 Id:0900d805809551ce 181 . 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activations 4 -> APN This graph shows the percentages of load for the APNs. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming Unsuccessful PDP Context Deactivations 1 day / 24 h / This graph shows the percentage of 30 min unsuccessful 3G PDP Context Deactivations for each network operator. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful MO Deliveries This graph shows the number of unsuccessful MO-SMS deliveries cumulatively for the time period 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful MT Deliveries This graph shows the number of unsuccessful MT-SMS deliveries cumulatively for the time period 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful Attach This graph shows the number of unsuccessful Attaches cumulatively for the time period 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful Detach This graph shows the number of unsuccessful Detaches cumulatively for the time period 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful RA Updates This graph shows the number of unsuccessful RA (Routing Area) updates cumulatively for the time period 1 day / 24 h / 30 min >=SG6 Table 13 182 Graph descriptions for 3G SG6 graphs (Cont. >=SG6 TRAF SGSN SG 3G Unsuccessful PDP Context Deactivations This graph shows the percentages of unsuccessful PDP Context Deactivations cumulatively for the time period. Obvious deactivation causes such as mobile requested deactivation and similar ones are not shown here >=SG6 TRAF SGSN SG 3G Roaming Unsuccessful PDP Context Deactivations -> Error Cause This graph shows the percentages of error causes for unsuccessful PDP Context Deactivations for a specific operator. Obvious deactivation causes such as mobile requested deactivation and similar ones will not be shown here. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Roaming Successful PDP Context Deactivations This graph shows the percentages of successful PDP Context Deactivations for each operator.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG 3G Roaming PDP Context Deactivations Attempts This graph shows the number of PDP Context Deactivations attempts for each network operator.) Id:0900d805809551ce DN05148836 Issue 2-2 . that may need operator’s attention for a potential problem in the network. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful PDP Activations This graph shows the number of unsuccessful PDP Context Activations cumulatively for the time period 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful PDP Modifications This graph shows the number of unsuccessful PDP Context Modifications cumulatively for the time period 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful PDP Deactivations 1 day / 24 h / This graph shows the number of unsuccessful 3G PDP Context Deactivations that 30 min may need operator’s attention for a potential problem in the network. The SAC with most unsuccessful PDP Context Activations is the first in the graph. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful RA Updates 3 This graph shows the number of unsuccessful RA Updates cumulatively for the time period. Using this graph you can track SACs with most failures in PDP Context Activations >=SG6 TRAF SGSN SG 3G Unsuccessful PDP Context Activations / SAC / Error Cause This graph shows unsuccessful PDP Context Activations' Error Cause codes for the SAC that is selected in the left-hand side graph \'Unsuccessful PDP Context Activations / SAC\'. >=SG6 Table 13 Graph descriptions for 3G SG6 graphs (Cont. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful RA Updates 2 This graph shows the percentages of unsuccessful RA Update types cumulatively for the time period. >=SG6 TRAF SGSN SG 3G Unsuccessful PDP Context Activations / SAC 1 day / 24 h / This graph shows the number of unsuccessful PDP Context Activations for SACs 30 min (SAC IDs).Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Graph Description Time Class SGSN Version TRAF SGSN SG 3G Unsuccessful Attaches This graph shows the percentages of unsuccessful Attaches cumulatively for the time period. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful RA Updates 2 -> Error Causes This graph shows the percentages of error causes for an unsuccessful specific RA Update type. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Unsuccessful RA Updates -> Error Causes This graph shows the percentages of error causes for all unsuccessful RA Updates. Using this graph you can track most common Error Cause codes for different SACs for PDP Context Activations 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Modifications / SAC / Error Cause This graph shows PDP Context Modifica. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activations / SAC / Error Cause 1 day / 24 h / This graph shows PDP Context Activations' Error Cause codes for the SAC that 30 min is selected in the left-hand side graph \ 'PDP Context Activations / SAC\' Using this graph you can track Error Cause distribution for different SACs.1 day / 24 h / tions' Error Cause codes for the SAC that 30 min is selected in the left-hand side graph \ 'PDP Context Modifications / SAC\' Using this graph you can track Error Cause distribution for different SACs. Time Class >=SG6 TRAF SGSN SG 3G Unsuccessful Detaches This graph shows the percentages of unsuccessful Detaches cumulatively for the time period.) DN05148836 Issue 2-2 Id:0900d805809551ce 183 . >=SG6 TRAF SGSN SG 3G MO SMS Deliveries / SAC / Error Cause This graph shows MO-SMS deliveries' Error Cause codes for the SAC that is selected in the left-hand side graph \'MO SMS Deliveries / SAC\' Using this graph you can track Error Cause distribution for different SACs.1 day / 24 h / tivations / SAC / Error Cause tions' Error Cause codes for the SAC that 30 min is selected in the left-hand side graph \ 'PDP Context Deactivations / SAC\' Using this graph you can track Error Cause distribution for different SACs. Using this graph you can track most common Error Cause codes for different SACs for PDP Context Modifications 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Deac. This graph can be used to track failures in different mobile phone types for PDP Context Activations. 1 day / 24 h / 30 min >=SG6 Table 13 184 Graph descriptions for 3G SG6 graphs (Cont. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G MT SMS Deliveries / SAC / Error Cause This graph shows the SACs (SAC IDs) for MT-SMS deliveries cumulatively for the time period.) Id:0900d805809551ce DN05148836 Issue 2-2 .This graph shows PDP Context Deactiva. The SACs are listed in order so that the SAC where there has been the most MT-SMS deliveries is the first in the graph.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG 3G PDP Context Modifications Unsuccessful / SAC / Error Cause This graph shows unsuccessful PDP Context Modifications' Error Cause codes for the SAC that is selected in the left-hand side graph \'Unsuccessful PDP Context Modifications / SAC\'. Using this graph you can track the most used SACs for MT-SMS deliveries 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Attaches / LAC / Error Cause This graph shows Attaches' Error Cause codes for the LAC that is selected in the left-hand side graph \'Attaches / LAC\' Using this graph you can track Error Cause distribution for different LACs. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G Detaches / LAC / Error Cause This graph shows Detaches' Error Cause codes for the LAC that is selected in the left-hand side graph \'Detaches / LAC\' Using this graph you can track Error Cause distribution for different LACs. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G PDP Context Activations / Mobile Type / Error Cause This graph shows PDP Context Activations' Error Cause code distribution for the mobile phone type that is currently selected in graph 'PDP Context Activations / Mobile Type'. 1 day / 24 h / 30 min >=SG6 TRAF SGSN SG 3G RA Updates / RAC / Error Cause This graph shows RA updates' Error Cause codes for the RAC that is selected in the left-hand side graph \'RA Updates / RAC\' Using this graph you can track Error Cause distribution for different RACs. Successful roaming has always Error Cause code 0h. Table 14 Graph descriptions for I-HSPA SG7 graphs DN05148836 Issue 2-2 Id:0900d805809551ce 185 . SGSN Version Graph Description Time Class TRAF SGSN SG I-HSPA PDP Context Activations_ This graph shows the number of successful and unsuccessful\nPDP Context Activations 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Modifications_ This graph shows the number of successful and unsuccessful PDP Context Modifications 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Deactivations_ This graph shows the number of successful and unsuccessful PDP Context Deactivations 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA RA Updates_ This graph shows the number of successful and unsuccessful RA (Routing Area) updates 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA MO SMS Deliveries_ This graph shows the number of successful and unsuccessful MO-SMS deliveries 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA MT SMS Deliveries_ This graph shows the number of successful and unsuccessful MT-SMS deliveries 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Attaches_ This graph shows the number of successful and unsuccessful Attaches 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Detaches_ This graph shows the number of successful and unsuccessful Detaches 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations Unsuccessful This graph shows the number of unsuccessful PDP Context Activations 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Modifications Unsuccessful This graph shows the number of unsuccessful PDP Context Modifications 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Deactivations Unsuccessful 1 day / 24 h / This graph shows the number of unsuc30 min cessful PDP Context Deactivations that may need operator’s attention for a potential problem in the network. 1 day / 24 h / 30 min Table 13 SGSN Version >=SG6 Graph descriptions for 3G SG6 graphs (Cont. other values indicate a failure in roaming attach.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Graph Description Time Class TRAF SGSN SG 3G Roaming Attaches / LAC / RAC / Error Cause This graph shows the percentages of error causes for a RAC under a certain LAC. >=SG7 For example. Here several error causes that do not need special attention from the operator have also been filtered out. 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause.) The following table lists the I-HSPA SG7 graphs. Here several error causes that do not need special attention from the operator have also been filtered out.) Id:0900d805809551ce DN05148836 Issue 2-2 . Also.This graph shows the percentage of 30 min eries Unsuccessful % unsuccessful MO-SMS deliveries. if there has been one unsuccessful Deactivation and 99 successful Deactivations. if there has been one unsuccessful Modification and 99 successful Modifications. 30 min For example. the graph will show 1% value. 1 day / 24 h / 30 min >=SG7 1 day / 24 h / This graph shows the percentage of unsuccessful RA (Routing Area) updates.This graph shows the number of unsuceries Unsuccessful cessful MT-SMS deliveries 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Attaches Unsuccessful This graph shows the number of unsuccessful Attaches 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Detaches Unsuccessful This graph shows the number of unsuccessful Detaches 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations Unsuccessful % 1 day / 24 h / This graph shows the percentage of 30 min unsuccessful PDP Context Activations. if there has been one unsuccessful RA update and 99 successful RA updates. if there has been one unsuccessful Activation and 99 successful Activations. the graph will show 1% value >=SG7 For example. the graph will show 1% value >=SG7 TRAF SGSN SG I-HSPA PDP Context Modifications Unsuccessful % 1 day / 24 h / This graph shows the percentage of unsuccessful PDP Context Modifications. the graph will show 1% value >=SG7 1 day / 24 h / TRAF SGSN SG I-HSPA MO SMS Deliv.This graph shows the number of unsuceries Unsuccessful cessful MO-SMS deliveries 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA MT SMS Deliv.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG I-HSPA RA Updates Unsuccessful This graph shows the number of unsuccessful RA (Routing Area) updates 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA MO SMS Deliv. if there has been one unsuccessful MO-SMS delivery and 99 successful MO-SMS deliveries. the graph will show 1% value >=SG7 TRAF SGSN SG I-HSPA PDP Context Deactivations Unsuccessful % This graph shows the percentage of unsuccessful PDP Context Deactivations that may need operator’s attention for a potential problem in the network. 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause. For example. TRAF SGSN SG I-HSPA RA Updates Unsuccessful % Table 14 186 Graph descriptions for I-HSPA SG7 graphs (Cont. For example. 30 min For example. Successful PDP Context Activations has error cause code 0x0. Successful PDP Context Modifications has error cause code 0x0. if there has been one unsuccessful Detach and 99 successful Detaches. the graph will show 1% value >=SG7 TRAF SGSN SG I-HSPA Attaches Unsuccessful % This graph shows the percentage of unsuccessful Attaches.This graph shows the percentage of 30 min eries Unsuccessful % unsuccessful MT-SMS deliveries. the graph will show 1% value 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations This graph shows the number of successful and unsuccessful PDP Context Activations cumulatively for the time period 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations / Error Cause This graph shows the Error Cause codes for PDP Context Activations. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code.) DN05148836 Issue 2-2 Id:0900d805809551ce 187 . Using this graph you can track the most used SACs for PDP Context Activation. other values indicate a failure in PDP Context Modification 1 day / 24 h / 30 min >=SG7 Table 14 Graph descriptions for I-HSPA SG7 graphs (Cont. The SACs are listed in order so that the SAC where there has been the most PDP Context Activations is the first in the graph. For example. For example. For example. the graph will show 1% value 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Detaches Unsuccessful % This graph shows the percentage of unsuccessful Detaches. other values indicate a failure in PDP Context Activation 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations / SAC This graph shows the SAC (SAC IDs) for PDP Context Activations cumulatively for the time period. if there has been one unsuccessful MT-SMS delivery and 99 successful MT-SMS deliveries.Traffica Reference Guide for SGSN Direct Interface Graph Description Real-time monitoring Time Class SGSN Version 1 day / 24 h / TRAF SGSN SG I-HSPA MT SMS Deliv. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Modifications This graph shows the number of successful and unsuccessful PDP Context Modifications cumulatively for the time period 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Modifications / Error Cause This graph shows the Error Cause codes for PDP Context Modifications. if there has been one unsuccessful Attach and 99 successful Attaches. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. Using this graph you can track the most used SACs for PDP Context Deactivations. For example. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Deactivations Unsuccessful / SAC This graph shows the number of unsuccessful PDP Context Deactivations for SACs (SAC IDs). Successful PDP Context Deactivations has error cause code 0x0. The SACs are listed in order so that the SAC where there has been the most PDP Context Modifications is the first in the graph. Table 14 188 Graph descriptions for I-HSPA SG7 graphs (Cont. Using this graph you can track the most used SACs for PDP Context Modifications. Regular PDP context deactivation has error cause code 0x24.) Id:0900d805809551ce DN05148836 Issue 2-2 . 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause. The SAC with most unsuccessful PDP Context Deactivations is the first in the graph.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG I-HSPA PDP Context Modifications / SAC This graph shows the SACs (SAC IDs) for PDP Context Modifications cumulatively for the time period. Using this graph you can track SACs with most failures in PDP Context Deactivations. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Modifications Unsuccessful / SAC This graph shows the number of unsuccessful PDP Context Modifications for SACs (SAC IDs). 1 day / 24 h / 30 min >=SG7 Here several error causes that do not need special attention from the operator have also been filtered out. Using this graph you can track SACs with most failures in PDP Context Modifications 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Deactivations This graph shows the number of successful and unsuccessful PDP Context Deactivations cumulatively for the time period 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Deactivations / Error Cause This graph shows the Error Cause codes for PDP Context Deactivations. The SACs are listed in order so that the SAC where there has been the most PDP Context Deactivations is the first in the graph. The SAC with most unsuccessful PDP Context Modifications is the first in the graph. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. other values indicate a failure in PDP Context Deactivation 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Deactivations / SAC This graph shows the SACs (SAC IDs) for PDP Context Deactivations cumulatively for the time period. This graph shows the number of successeries ful and unsuccessful MT-SMS deliveries cumulatively for the time period 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA MT SMS Deliv.This graph shows the SACs (SAC IDs) for eries / SAC MT-SMS deliveries cumulatively for the time period.This graph shows the Error Cause codes eries / Error Cause for MO-SMS deliveries. Place the mouse cursor on top of Error Cause value on xaxis to show the description of the Error Cause code. Using this graph you can track the most used SACs for MT-SMS deliveries 1 day / 24 h / 30 min >=SG7 1 day / 24 h / TRAF SGSN SG I-HSPA MT SMS Deliv. 1 day / 24 h / 30 min >=SG7 Here several error causes that do not need special attention from the operator have also been filtered out. Using this graph you can track most common Error Cause codes for different SACs for PDP Context Deactivations. 0xC6 indicates a regular deactivation procedure from the mobile and cannot be treated as an unsuccessful PDP context deactivation cause Table 14 Graph descriptions for I-HSPA SG7 graphs (Cont. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA MO SMS Deliv.) DN05148836 Issue 2-2 Id:0900d805809551ce 189 . The SAC with most unsuccessful MTSMS deliveries is the first in the graph.This graph shows the number of unsuceries Unsuccessful / SAC cessful MT-SMS deliveries for SACs (SAC 30 min IDs).This graph shows the Error Cause codes eries / Error Cause for MT-SMS deliveries. Place the mouse cursor on top of Error Cause value on xaxis to show the description of the Error Cause code. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA MT SMS Deliv.This graph shows the number of successeries ful and unsuccessful MO-SMS deliveries cumulatively for the time period 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA MO SMS Deliv. Using this graph you can track most common Error Cause codes for different SACs for MT-SMS deliveries. For example.This graph shows unsuccessful MT-SMS eries Unsuccessful / SAC / Error Cause deliveries' Error Cause codes for the SAC that is selected in the left-hand side graph \'Unsuccessful MT SMS Deliveries / SAC\'. Using this graph you can track SACs with most failures in MT-SMS deliveries >=SG7 TRAF SGSN SG I-HSPA MT SMS Deliv.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG I-HSPA PDP Context Deactivations Unsuccessful / SAC / Error Cause This graph shows unsuccessful PDP Context Deactivations' Error Cause codes for the SAC that is selected in the left-hand side graph \'Unsuccessful PDP Context Deactivations / SAC\'. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA MT SMS Deliv. The SACs are listed in order so that the SAC where there has been the most MT-SMS deliveries is the first in the graph. The LAC with most unsuccessful Attaches is the first in the graph. The SACs are listed in order so that the SAC where there has been the most MO-SMS deliveries is the first in the graph. Using this graph you can track SACs with most failures in MO-SMS deliveries 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA MO SMS Deliv. >=SG7 TRAF SGSN SG I-HSPA Attaches This graph shows the number of successful and unsuccessful Attaches cumulatively for the time period 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Attaches / Error Cause This graph shows the Error Cause codes for attaches. Using this graph you can track the most used LACs for Attaches 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Attaches Unsuccessful / LAC This graph shows the number of unsuccessful Attaches for LACs.) Id:0900d805809551ce DN05148836 Issue 2-2 . Using this graph you can track LACs with most failures in Attaches 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Attaches Unsuccessful / LAC / Error Cause This graph shows unsuccessful Attaches' Error Cause codes for the LAC that is selected in the left-hand side graph \ 'Unsuccessful Attaches / LAC\'. Using this graph you can track most common Error Cause codes for different LACs for Attaches 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Detaches This graph shows the number of successful and unsuccessful Detaches cumulatively for the time period 1 day / 24 h / 30 min >=SG7 Table 14 190 Graph descriptions for I-HSPA SG7 graphs (Cont. The SAC with most unsuccessful MO-SMS deliveries is the first in the graph. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code.Real-time monitoring Graph Traffica Reference Guide for SGSN Direct Interface Description Time Class SGSN Version TRAF SGSN SG I-HSPA MO SMS Deliv. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Attaches / LAC This graph shows the LACs for Attaches cumulatively for the time period. Using this graph you can track the most used SACs for MO-SMS deliveries 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA MO SMS Deliv.This graph shows unsuccessful MO-SMS 1 day / 24 h / eries Unsuccessful / SAC / Error Cause deliveries' Error Cause codes for the SAC 30 min that is selected in the left-hand side graph \'Unsuccessful MO SMS Deliveries / SAC\ '.This graph shows the SACs (SAC IDs) for eries / SAC MO-SMS deliveries cumulatively for the time period. The LACs are listed in order so that the LAC where there has been the most Attaches is the first in the graph. Using this graph you can track most common Error Cause codes for different SACs for MO-SMS deliveries.This graph shows the number of unsuceries Unsuccessful / SAC cessful MO-SMS deliveries for SACs (SAC IDs). Using this graph you can track RACs with most failures in RA updates 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA RA Updates Unsuccessful / RAC / Error Cause This graph shows unsuccessful RA updates' Error Cause codes for the RAC that is selected in the left-hand side graph \'Unsuccessful RA Updates / RAC\'.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring Graph Description Time Class SGSN Version TRAF SGSN SG I-HSPA Detaches / Error Cause This graph shows the Error Cause codes for detaches. Using this graph you can track most common Error Cause codes for different LACs for Detaches. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA RA Updates / RAC This graph shows the RACs for RA updates cumulatively for the time period. Using this graph you can track the most used LACs for Detaches 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Detaches Unsuccessful / LAC This graph shows the number of unsuccessful Detaches for LACs. Using this graph you can track LACs with most failures in Detaches 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Detaches Unsuccessful / LAC / Error Cause This graph shows unsuccessful Detaches' Error Cause codes for the LAC that is selected in the left-hand side graph \ 'Unsuccessful Detaches / LAC\'. The LACs are listed in order so that the LAC where there has been the most Detaches is the first in the graph. Time Class >=SG7 TRAF SGSN SG I-HSPA Detaches / LAC This graph shows the LACs for Detaches cumulatively for the time period. Using this graph you can track the most used RACs for RA updates 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA RA Updates Unsuccessful / RAC This graph shows the number of unsuccessful RA updates for RACs. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. The RACs are listed in order so that the RAC where there has been the most RA updates is the first in the graph. Using this graph you can track most common Error Cause codes for different RACs for RA updates 1 day / 24 h / 30 min >=SG7 Table 14 Graph descriptions for I-HSPA SG7 graphs (Cont. The LAC with most unsuccessful Detaches is the first in the graph. Place the mouse cursor on top of Error Cause value on x-axis to show the description of the Error Cause code. The RAC with most unsuccessful RA updates is the first in the graph. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA RA Updates This graph shows the number of successful and unsuccessful RA (Routing Area) updates cumulatively for the time period 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA RA Updates / Error Cause This graph shows the Error Cause codes for RA (Routing Area) updates.) DN05148836 Issue 2-2 Id:0900d805809551ce 191 . Mobile phone types are shown in order so that the most used phone type is the first in the graph.) Id:0900d805809551ce DN05148836 Issue 2-2 . 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations Unsuccessful / Mobile Type / Error Cause This graph shows PDP Context Activations' Error Cause code distribution for the mobile phone type that is currently selected in graph \'Unsuccessful PDP Context Activations / Mobile Type\'. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations 3 -> APN -> Error Cause This graph shows the percentages of error causes for a specific APN. Mobile phone types are shown in order so that the most used phone type is the first in the graph. This graph can be used to track most used mobile phone types for PDP Context Activations. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful PDP Context Activations This graph shows the percentage of unsuccessful PDP Context Activations cumulatively for the time period. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming Attaches Attempts This graph shows the number of attaches attempts for each network operator. This graph can be used to track failures in different mobile phone types for PDP Context Activations. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations 3 -> APN This graph shows the percentages of load for the APNs. This graph can be used to track failures in different mobile phone types for Attaches. This graph can be used to track most used mobile phone types for Attaches 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Attaches / Mobile Type / Error Cause This graph shows Attaches' Error Cause code distribution for the mobile phone type that is currently selected in graph \ 'Attaches / Mobile Type\'. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful PDP Context Modifications This graph shows the percentages of unsuccessful PDP Context Modifications cumulatively for the time period. This graph can be used to track most used mobile phone types for failed PDP Context Activations. 1 day / 24 h / 30 min >=SG7 Table 14 192 Graph descriptions for I-HSPA SG7 graphs (Cont.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG I-HSPA Attaches / Mobile Type This graph shows Mobile phone types that are used for Attaches. Mobile phone types are shown in order so that the most used phone type is the first in the graph. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations 3 This graph shows the number of all PDP Context Activations attempts. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations / Mobile Type This graph shows Mobile phone types that are used for PDP Context Activations. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations Unsuccessful / Mobile Type This graph shows Mobile phone types that are used for unsuccessful PDP Context Activations. 1 day / 24 h / 30 min >=SG7 Table 14 Graph descriptions for I-HSPA SG7 graphs (Cont. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming Unsuccessful PDP Context Activations This graph shows the percentages of unsuccessful PDP Context Activations for each operator. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Subscriber Data Uplink / APN This graph shows the amount of data sent uplink in kbytes for a specific APN. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming PDP Context Activations Attempts This graph shows the number of PDP Context Activation attempts for each network operator. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming PDP Context Activations Attempts 2 -> Mobile Type -> Error Cause This graph shows the percentages of error causes for PDP Context Activation attempts for a specific mobile type. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Uplink and Downlink Data Volume / LAC / RAC / SAC This graph shows the data volume uplink and downlink in kbytes for each SAC in a certain RAC. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Subscriber Data Downlink / APN This graph shows the amount of data sent downlink in kbytes for a specific APN. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Uplink and Downlink Data Volume / LAC / RAC This graph shows the data volume uplink and downlink in kbytes for each RAC in a certain LAC. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming Unsuccessful PDP Context Activations > Error Cause This graph shows the percentages of error 1 day / 24 h / causes for unsuccessful PDP Context Acti. 1 day >=SG7 TRAF SGSN SG I-HSPA Traffic Class 1 QoS Successful Request This graph shows the percentages of fulfilled Requests for a specific traffic class. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Uplink and Downlink Data Volume / LAC This graph shows the data volume uplink and downlink in kbytes for each LAC. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming Unsuccessful Attaches -> Error Cause This graph shows the percentages of error causes for unsuccessful attaches and a specific operator.) DN05148836 Issue 2-2 Id:0900d805809551ce 193 .30 min vation for a specific operator. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming Unsuccessful Attaches This graph shows the percentages of unsuccessful attaches for each operator. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Subscriber APN Usage This graph shows the distribution of APNs for the PDP Context Activations that occurred. >=SG7 TRAF SGSN SG I-HSPA Roaming PDP Context Activations Attempts 2 This graph shows the number of PDP Context Activation attempts for each network operator.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG I-HSPA Roaming Successful Attaches This graph shows the percentages of successful attaches for each operator. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming Successful PDP Context Activations This graph shows the percentages of successful PDP Context Activations for each operator. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming PDP Context Activations Attempts 2 -> Mobile Type This graph shows the percentages of mobile types for PDP Context Activation attempts for a specific operator. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Traffic Class 1 QoS Negotiated This graph shows the percentages of negotiations for a specific traffic class. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Traffic Class 2 QoS Negotiated This graph shows the percentages of negotiations for a specific traffic class.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG I-HSPA Traffic Class 2 QoS Successful Request This graph shows the percentages of fulfilled requests for a specific traffic class.) Id:0900d805809551ce DN05148836 Issue 2-2 . 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful Roaming Session / Error Cause / Mobile Types This graph shows the percentages distribution of mobile phones type for error causes for abnormally terminated roaming sessions. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Traffic Class 3 QoS Requested This graph shows the percentages of Requests for a specific traffic class. Time Class >=SG7 TRAF SGSN SG I-HSPA Roaming Sessions This graph shows the number of all roaming sessions. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful Roaming Sessions This graph shows the percentages of abnormally terminated roaming sessions. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Traffic Class 2 QoS Requested This graph shows the percentages of Requests for a specific traffic class. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Traffic Class 3 QoS Successful Request This graph shows the percentages of fulfilled Requests for a specific traffic class. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful Roaming Sessions / Error Cause This graph shows the percentages distribution of error causes for abnormally terminated roaming sessions. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Traffic Class 1 QoS Requested This graph shows the percentages of Requests for a specific traffic class. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Traffic Class 4 QoS Successful Request This graph shows the percentages of fulfilled Requests for a specific traffic class. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Data Volume / Traffic Class 2 This graph shows the data volume uplink and downlink in kbytes for Streaming class. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Traffic Class 3 QoS Negotiated This graph shows the percentages of negotiations for a specific traffic class. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Data Volume / Traffic Class 1 This graph shows the data volume uplink and downlink in kbytes for Conversational class. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Traffic Class 4 QoS Requested This graph shows the percentages of Requests for a specific traffic class. 1 day / 24 h / 30 min >=SG7 Table 14 194 Graph descriptions for I-HSPA SG7 graphs (Cont. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Data Volume / Traffic Class 3 This graph shows the data volume uplink 1 day / 24 h / and downlink in kbytes for Interactive class 30 min >=SG7 TRAF SGSN SG I-HSPA Data Volume / Traffic Class 4 This graph shows the data volume uplink and downlink in kbytes for Background class. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Traffic Class 4 QoS Negotiated This graph shows the percentages of negotiations for a specific traffic class. Values usually indicate a failure in roaming attach >=SG7 TRAF SGSN SG I-HSPA Roaming PDP Context Activations / Error Cause This graph shows the distribution of error causes for roaming PDP Context Activations.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG I-HSPA Roaming Attaches / LAC This graph shows the distribution of Roaming Attaches in a each LAC. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming Attaches This graph shows the number of roaming attaches. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful Roaming Attaches / LAC This graph shows the distribution of Roaming Attaches that were abnormally terminated for a each LAC. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful Roaming Attaches / LAC / RAC / Error Cause This graph shows the percentages of error causes for Roaming Attaches that were abnormally terminated per RAC under a specific LAC.) DN05148836 Issue 2-2 Id:0900d805809551ce 195 . Values usually indicate a failure in roaming PDP Context Activations 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming PDP Context Modifications / Error Cause This graph shows the distribution of error 1 day / 24 h / causes for roaming PDP Context Modifica. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming Attaches / LAC / RAC This graph shows the distribution of Roaming Attaches for the RACs under a certain LAC. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA APN Data Volume Uplink and Downlink / Mobile Types This graph shows the distribution of uplink and downlink data volumes in kbytes for each mobile types for certain APNs. 30 min >=SG7 TRAF SGSN SG I-HSPA APN Data Volume Uplink and Downlink This graph shows the amount of data sent uplink and downlink in kbytes for each APN. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA APN Usage / Mobile Types This graph shows the distribution of mobile 1 day / 24 h / phone types that are used for certain APN. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful Roaming Attaches / LAC / RAC This graph shows the distribution of Roaming Attaches that were abnormally terminated for the RACs under a certain LAC. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Data Volumes in TREC 0 This graph shows the data volume uplink and downlink in kbytes for a TREC 0 1 day / 24 h / 30 min >=SG7 Table 14 Graph descriptions for I-HSPA SG7 graphs (Cont. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming PDP Context Activations This graph shows the number of roaming PDP Context Activations 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming PDP Context Modifications This graph shows the number of roaming PDP Context Modifications 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming Attaches / Error Cause This graph shows the distribution of error 1 day / 24 h / 30 min causes for roaming attaches. Values usually indicate a failure in roaming PDP Context Modifications. >=SG7 TRAF SGSN SG I-HSPA APN Usage This graph shows the distribution of APNs for the PDP Context Activations that occurred.30 min tions. Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG I-HSPA Data Volumes in TREC 1 This graph shows the data volume uplink and downlink in kbytes for a TREC 1 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Data Volumes in TREC 2 This graph shows the data volume uplink and downlink in kbytes for a TREC 2 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Data Volumes in TREC 3 This graph shows the data volume uplink and downlink in kbytes for a TREC 3 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Data Volumes in TREC 4 This graph shows the data volume uplink and downlink in kbytes for a TREC 4 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Data Volumes in TREC 5 This graph shows the data volume uplink and downlink in kbytes for a TREC 5 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Data Volumes in TREC 6 This graph shows the data volume uplink and downlink in kbytes for a TREC 6 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Data Volumes in TREC 7 This graph shows the data volume uplink and downlink in kbytes for a TREC 7 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Data Volumes in TREC 8 This graph shows the data volume uplink and downlink in kbytes for a TREC 8 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Data Volumes in TREC 9 This graph shows the data volume uplink and downlink in kbytes for a TREC 9 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Error Causes in TREC 0 This graph shows the percentages distribution of error causes for the TREC 0 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Error Causes in TREC 1 This graph shows the percentages distribution of error causes for the TREC 1 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Error Causes in TREC 2 This graph shows the percentages distribution of error causes for the TREC 2 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Error Causes in TREC 3 This graph shows the percentages distribution of error causes for the TREC 3 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Error Causes in TREC 4 This graph shows the percentages distribution of error causes for the TREC 4 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Error Causes in TREC 5 This graph shows the percentages distribution of error causes for the TREC 5 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Error Causes in TREC 6 This graph shows the percentages distribution of error causes for the TREC 6 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Error Causes in TREC 7 This graph shows the percentages distribution of error causes for the TREC 7 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Error Causes in TREC 8 This graph shows the percentages distribution of error causes for the TREC 8 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Error Causes in TREC 9 This graph shows the percentages distribution of error causes for the TREC 9 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation Load in TREC 0 This graph shows the percentages of PDP context activation load for the TREC 0 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation Load in TREC 1 This graph shows the percentages of PDP context activation load for theTREC 1 1 day / 24 h / 30 min >=SG7 Table 14 196 Graph descriptions for I-HSPA SG7 graphs (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 . Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG I-HSPA PDP Context Activation Load in TREC 2 This graph shows the percentages of PDP context activation load for the TREC 2 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation Load in TREC 3 This graph shows the percentages of PDP context activation load for the TREC 3 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation Load in TREC 4 This graph shows the percentages of PDP context activation load for the TREC 4 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation Load in TREC 5 This graph shows the percentages of PDP context activation load for the TREC 5 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation Load in TREC 6 This graph shows the percentages of PDP context activation load for the TREC 6 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation Load in TREC 7 This graph shows the percentages of PDP context activation load for the TREC 7 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation Load in TREC 8 This graph shows the percentages of PDP context activation load for the TREC 8 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation Load in TREC 9 This graph shows the percentages of PDP context activation load for the TREC 9 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation in APNs in TREC 0 This graph shows the number of PDP context activations for each APN names for the TREC 0 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation in APNs in TREC 1 This graph shows the number of PDP context activations for each APN names for the TREC 1 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation in APNs in TREC 2 This graph shows the number of PDP context activations for each APN names for the TREC 2 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation in APNs in TREC 3 This graph shows the number of PDP context activations for each APN names for the TREC 3 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation in APNs in TREC 4 This graph shows the number of PDP context activations for each APN names for the TREC 4 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation in APNs in TREC 5 This graph shows the number of PDP context activations for each APN names for the TREC 5 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation in APNs in TREC 6 This graph shows the number of PDP context activations for each APN names for the TREC 6 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation in APNs in TREC 7 This graph shows the number of PDP context activations for each APN names for the TREC 7 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activation in APNs in TREC 8 This graph shows the number of PDP context activations for each APN names for the TREC 8 1 day / 24 h / 30 min >=SG7 Table 14 Graph descriptions for I-HSPA SG7 graphs (Cont.) DN05148836 Issue 2-2 Id:0900d805809551ce 197 . 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful Roaming PDP Context Modifications This graph shows the percentages of abnormally terminated PDP context modification sessions.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG I-HSPA PDP Context Activation in APNs in TREC 9 This graph shows the number of PDP context activations for each APN names for the TREC 9 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful Roaming Attaches This graph shows the percentages of abnormally terminated roaming attaches 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful Roaming PDP Context Activations This graph shows the percentages of abnormally terminated PDP context activation sessions. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 0 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 0 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 1 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 1 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 2 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 2 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 3 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 3 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 4 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 4 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 5 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 5 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 6 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 6 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 7 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 7 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 8 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 8 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 9 Usage Per SACs This graph shows the number of PDP context activations for each SAC names for the TREC 9 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 0 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 0 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 1 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 1 1 day / 24 h / 30 min >=SG7 Table 14 198 Graph descriptions for I-HSPA SG7 graphs (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 . 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming Unsuccessful Detaches -> Error Cause This graph shows the percentages of error causes for unsuccessful detaches and a specific operator. 1 day / 24 h / 30 min >=SG7 Table 14 Graph descriptions for I-HSPA SG7 graphs (Cont.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG I-HSPA TREC 2 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 2 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 3 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 3 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 4 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 4 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 5 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 6 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 6 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 6 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 7 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 7 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 8 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 8 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA TREC 9 Errors Per SACs This graph shows the percentages distribution of error causes for the certain SAC for TREC 9 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations 4 This graph shows the number of all PDP Context Activations attempts. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming Detaches Attempts This graph shows the number of Detaches attempts for each network operator. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming PDP Context Deactivations Attempts This graph shows the number of PDP Context Deactivations attempts for each network operator.) DN05148836 Issue 2-2 Id:0900d805809551ce 199 . 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations 4 -> APN -> Error Cause This graph shows the percentages of error causes for a specific SAC under the certain APN. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming Unsuccessful Detaches This graph shows the percentages of unsuccessful detaches for each operator. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations 4 -> APN -> SAC This graph shows the percentages of load for the SACs under the certain APN. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations 4 -> APN This graph shows the percentages of load for the APNs. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming Successful Detaches This graph shows the percentages of successful detaches for each operator. 1 day / 24 h / 30 min >=SG7 Table 14 200 Graph descriptions for I-HSPA SG7 graphs (Cont. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming Unsuccessful PDP Context Deactivations -> Error Cause This graph shows the percentages of error causes for unsuccessful PDP Context Deactivations for a specific operator. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful MO Deliveries This graph shows the number of unsuccessful MO-SMS deliveries cumulatively for the time period 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful MT Deliveries This graph shows the number of unsuccessful MT-SMS deliveries cumulatively for the time period 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful Attaches This graph shows the number of unsuccessful Attaches cumulatively for the time period 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful Detaches This graph shows the number of unsuccessful Detaches cumulatively for the time period 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful RA Updates This graph shows the number of unsuccessful RA (Routing Area) updates cumulatively for the time period 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful Attaches This graph shows the percentages of unsuccessful Attaches cumulatively for the time period. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful RA Updates -> Error Causes This graph shows the percentages of error causes for all unsuccessful RA Updates.) Id:0900d805809551ce DN05148836 Issue 2-2 . 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful RA Updates 3 This graph shows the number of unsuccessful RA Updates cumulatively for the time period. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful PDP Context Activations This graph shows the number of unsuccessful PDP Context Activations cumulatively for the time period 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful PDP Context Modifications This graph shows the number of unsuccessful PDP Context Modifications cumulatively for the time period 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful PDP Context Deactivations This graph shows the percentages of unsuccessful PDP Context Deactivations cumulatively for the time period.Real-time monitoring Traffica Reference Guide for SGSN Direct Interface SGSN Version Graph Description Time Class TRAF SGSN SG I-HSPA Roaming Successful PDP Context Deactivations This graph shows the percentages of successful PDP Context Deactivations for each operator. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming Unsuccessful PDP Context Deactivations This graph shows the percentages of unsuccessful PDP Context Deactivations for each operator. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful RA Updates 2 This graph shows the percentages of unsuccessful RA Update types cumulatively for the time period. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Unsuccessful Detaches This graph shows the percentages of unsuccessful Detaches cumulatively for the time period. ) DN05148836 Issue 2-2 Id:0900d805809551ce 201 . Table 14 Graph descriptions for I-HSPA SG7 graphs (Cont.1 day / 24 h / tions' Error Cause codes for the SAC that 30 min is selected in the left-hand side graph \ 'PDP Context Deactivations / SAC\' Using this graph you can track Error Cause distribution for different SACs. Using this graph you can track SACs with most failures in PDP Context Activations >=SG7 TRAF SGSN SG I-HSPA Unsuccessful PDP Context Activations / SAC / Error Cause This graph shows unsuccessful PDP Context Activations' Error Cause codes for the SAC that is selected in the left-hand side graph \'Unsuccessful PDP Context Activations / SAC\'. >=SG7 TRAF SGSN SG I-HSPA PDP Context Modifications Unsuccessful / SAC / Error Cause This graph shows unsuccessful PDP Context Modifications' Error Cause codes for the SAC that is selected in the left-hand side graph \'Unsuccessful PDP Context Modifications / SAC\'. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations / SAC / Error Cause 1 day / 24 h / This graph shows PDP Context Activations' Error Cause codes for the SAC that 30 min is selected in the left-hand side graph \ 'PDP Context Activations / SAC\' Using this graph you can track Error Cause distribution for different SACs. The SAC with most unsuccessful PDP Context Activations is the first in the graph.1 day / 24 h / tions' Error Cause codes for the SAC that 30 min is selected in the left-hand side graph \ 'PDP Context Modifications / SAC\' Using this graph you can track Error Cause distribution for different SACs. >=SG7 TRAF SGSN SG I-HSPA Unsuccessful PDP Context Activations / SAC 1 day / 24 h / This graph shows the number of unsuccessful PDP Context Activations for SACs 30 min (SAC IDs). >=SG7 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA MO SMS Deliv.Traffica Reference Guide for SGSN Direct Interface Real-time monitoring SGSN Version Graph Description Time Class TRAF SGSN SG I-HSPA Unsuccessful RA Updates 2 -> Error Causes This graph shows the percentages of error causes for an unsuccessful specific RA Update type.This graph shows MO-SMS deliveries' eries / SAC / Error Cause Error Cause codes for the SAC that is selected in the left-hand side graph \'MO SMS Deliveries / SAC\' Using this graph you can track Error Cause distribution for different SACs. Using this graph you can track most common Error Cause codes for different SACs for PDP Context Activations 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Modifications / SAC / Error Cause This graph shows PDP Context Modifica. Using this graph you can track most common Error Cause codes for different SACs for PDP Context Modifications 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Deactivations / SAC / Error Cause This graph shows PDP Context Deactiva. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Roaming Attaches / LAC / RAC / Error Cause This graph shows the percentages of error causes for a RAC under a certain LAC. Using this graph you can track the most used SACs for MT-SMS deliveries 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Attaches / LAC / Error Cause This graph shows Attaches' Error Cause codes for the LAC that is selected in the left-hand side graph \'Attaches / LAC\' Using this graph you can track Error Cause distribution for different LACs. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA RA Updates / RAC / Error Cause This graph shows RA updates' Error Cause codes for the RAC that is selected in the left-hand side graph \'RA Updates / RAC\' Using this graph you can track Error Cause distribution for different RACs.Real-time monitoring Graph Traffica Reference Guide for SGSN Direct Interface Description Time Class SGSN Version TRAF SGSN SG I-HSPA MT SMS Deliv. Successful roaming has always Error Cause code 0h. 1 day / 24 h / 30 min >=SG7 Table 14 202 Graph descriptions for I-HSPA SG7 graphs (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 . This graph can be used to track failures in different mobile phone types for PDP Context Activations. other values indicate a failure in roaming attach.This graph shows the SACs (SAC IDs) for eries / SAC / Error Cause MT-SMS deliveries cumulatively for the time period. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA PDP Context Activations / Mobile Type / Error Cause This graph shows PDP Context Activations' Error Cause code distribution for the mobile phone type that is currently selected in graph 'PDP Context Activations / Mobile Type'. The SACs are listed in order so that the SAC where there has been the most MT-SMS deliveries is the first in the graph. 1 day / 24 h / 30 min >=SG7 TRAF SGSN SG I-HSPA Detaches / LAC / Error Cause This graph shows Detaches' Error Cause codes for the LAC that is selected in the left-hand side graph \'Detaches / LAC\' Using this graph you can track Error Cause distribution for different LACs. it is denoted in a separate “Empty value” section in the field descriptions below. Field exists in the database row indicates whether the IDS field in question exists in the database or not. Datatype in IDS row shows the data type. The database column SQL data types can be found in the workspace configuration file dbd_sgsn_rtt. DN05148836 Issue 2-2 Id:0900d805809551ce 203 . a field with data type UINT8 has the empty value 0xFF in hexadecimal.1 SGSN adaptation The following tables present the IDS. empty values are identical to those in the IDS. Empty time stamps are 1970-01-02 00:00:00 in the Traffica database. which means that the field does not contain any data. the Sgsn_Rtt_Report_Count IDS field is the Report_Count column in database table <SGSN_Release_Id>_RTT. and whether the field is indexed by default. The SQL data type appears after the column name and “=” symbol. 3. whereas they are stored as -1 in the database. In the Traffica database. Each IDS field has a so called empty value. Information about every IDS field is presented in a form of a table. The default empty value for each IDS field is a value that has all bits set to value 1. UINT8 type value 0xF8 in the IDS appears as -8 in the Traffica database. 2. 6. in which the rows give the following information: 1.conf.2 RTT fields The following table shows the RTT fields: Traffic News event type SGSN_RTT_EVENT Database table <SGSN_Release_Id>_RTT Table 15 SGSN_Rtt fields The database column names are the same as the IDS field names without the Sgsn_Rtt prefix. The Traffic News field names are the same as the database column names but use spaces instead of underscores between words.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions 6 RTT report descriptions 6. Under the <SGSN_Release_Id>_RTT section. SGSN version row indicates from which SGSN version onwards the field is available. For example. the Sgsn_Rtt_Report_Count IDS field is Report Count field in Traffic News SGSN_RTT_EVENT. Also normal values. For example. Possible values row lists the possible values that the IDS field can have. If a field has some other empty value. Explanation row explains the contents of the IDS field. fields with empty values are left blank. such as. there is a single-row entry for each table column. all fields are signed whereas in Traffica all fields are unsigned. However. For example. This means that the UINT8 empty value 0xFF appears as -1 in the database. In Traffic News Clients. 4. 5. in the database. and a field with the data type UINT16 has the empty value 0xFFFF in hexadecimal. This causes the difference that in PDP Context activation. Possible values APN Field exists in the database Apn Table 16 Sgsn_Rtt_Apn Field name Sgsn_Rtt_Apn_crc32 Datatype in IDS STRINGICRC32 SGSN version >=SG3 Explanation This field is used in defining the CCMA. value in APN Length field = real APN Length + 1 (ending zero). This field is used only in the case of a PDP context activation event. In PDP Context Activation.conf Sgsn_Rtt_Apn_crc32 Field name Sgsn_Rtt_Apn_Length Datatype in IDS UINT8 SGSN version >=SG3 Explanation Contains the length of Access Point Name of PDP activation.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Rtt_Apn Datatype in IDS DOTTEDSTRING(101) SGSN version >=SG3 Explanation Contains the Access Point Name of PDP activation. there is no ending zero added.008). there is an ending zero added to the APN name and in PDP Context Deactivation. instead of Sgsn_Rtt_Apn Possible values Field exists in the database Table 17 ccd_sgsn. Possible values 0x0-0xFF Field exists in the database Apn_Length Table 18 Sgsn_Rtt_Apn_Length Field name Sgsn_Rtt_Bss_Pfc_Info_Pfi Datatype in IDS UINT8 SGSN version SG6 Explanation The Packet Flow Identifier info element indicates Packet Flow Identifier for a Packet Flow Context (see 3G TS 24. Table 19 204 Sgsn_Rtt_Bss_Pfc_Info_Pfi Id:0900d805809551ce DN05148836 Issue 2-2 . Sgsn_Rtt_Cause_Cause contains SGSN internal cause codes which are easier subject to change than Sgsn_Rtt_Ps_External_Cause field which follows the ETSI 3GPP standard. Field exists in the database Cause_Cause Table 21 Sgsn_Rtt_Cause_Cause DN05148836 Issue 2-2 Id:0900d805809551ce 205 . modify_ok_c = 0x5. modify_fail_c = 0x6. create_fail_c = 0x2. delete_fail_c = 0x4. Possible values For possible values see Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause. NOTE: You should primarily use the Sgsn_Rtt_Ps_External_Cause field. Field exists in the database Table 19 Bss_Pfc_Info_Pfi Sgsn_Rtt_Bss_Pfc_Info_Pfi (Cont. But it is updated here in future Traffica releases. not_used_c = 0xff. signaling_c = 1. Field exists in the database Table 20 Bss_Pfc_Info_Status Sgsn_Rtt_Bss_Pfc_Info_Status Field name Sgsn_Rtt_Cause_Cause Datatype in IDS UINT32 SGSN version >=SG3 Explanation This field contains error cause of SGSN. Traffica documentation will update changes to this field only occasionally and thus a change in this field's possible values is not necessarily immediately reflected in Traffica documentation. sms_c = 2. delete_ok_c = 0x3. For mapping between external (GSM standard) and internal error causes see appendix SG3/SG4 INTERNAL CAUSE TO INTERFACE CAUSE MAPPING FROM MM & SM PROCESSES. not_used_c = 0xff.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions best_eff_c = 0. Possible values create_ok_c = 0x1.) Field name Sgsn_Rtt_Bss_Pfc_Info_Status Datatype in IDS UINT8 SGSN version SG6 Explanation Packet Flow Context information of PDP context Status. RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Rtt_Cause_Ini Datatype in IDS UINT8 SGSN version >=SG3 Explanation Contains the initiation causes for the SGSN cause. Table 22 206 Sgsn_Rtt_Cause_Ini Id:0900d805809551ce DN05148836 Issue 2-2 . ) DN05148836 Issue 2-2 Id:0900d805809551ce 207 . while MS was already attached.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions 0x0 – 0xFF undefined_c 0xFF = Initialisation value. undefined ms_initiated_c 0x0 = MS-initiated nw_initiated_c 0x1 = Network-initiated rej_ra_upd_c 0x2 = Rejected inter PAPU/SGSN routing area update rej_attach_c 0x3 = Rejected GPRS attach rej_auth_c 0x4 = Failed authentication ra_upd_c 0x5 = For security procedures attach_c 0x6 = Reattach from MS Reattach from MS. the SM deactivates context no_sgsn_resources_c 0x23 = SGSN has no resources to finish the requested operation remote_release_c 0x24 = Data link has been released by the MS detach_c 0x25 = GPRS detach mnr_c 0x26 = The MS is unreachable inter_sgsn_rau_c 0x27 = Inter SGSN routing area update inter_papu_rau_c 0x28 = Inter PAPU routing area update og_inter_sgsn_rau_c 0x29 = Inter SGSN routing area update to new SGSN og_inter_papu_rau_c 0x2A = Inter PAPU routing area update to new PAPU failed_imei_chk_c 0x2B = IMEI check failed ll_fail_c 0x2C = Lower layer failure cs_call_c 0x2D = Circuit switched call no_resources_c 0x2E = The MS requests context deactivation due to the lack of resources unsupp_llc_sapi_c 0x2F = The MS does not accept SAPI in MO PDP context activation u_context_in_ggsn_c 0x30 = GGSN has no context to send the MS's data packet llc_fail_c 0x31 = GIPPRB out of order gsp_exp_c 0x32 = GSPPRB's timer expiry Table 22 Sgsn_Rtt_Cause_Ini (Cont. implicit detach for old mm-context will be initiated before new attach can be processed sm_proc_c 0x7 = For security procedures gsms_proc_c 0x8 = For security procedures mmi_c 0x9 = For security procedures reatt_req_c 0xC = The MS is requested to perform a GPRS detach and a new attach scp_initiated_c 0xD = SCP-initiated procedure hlr_initiated_c 0x20 = HLR-initiated procedure qos_not_accepted_c 0x21 = The MS starts deactivation during MO activation ggsn_recovery_c 0x22 = GGSN has been reset. ) Id:0900d805809551ce DN05148836 Issue 2-2 . continued Traffica Reference Guide for SGSN Direct Interface ms_reachab_exp_c 0x33 = MS reachable timer expiry gip_mas_ann_c 0x34 = GIPPRB's master detected that GIPPRB's slave is out of order og_attach_c 0x35 = Outgoing attach (attach in new SGSN) smmu_reset_c 0x36 = Leads to detach and activation rejection time_quota_c 0x37 = Frozen hand process leads to release llc_sndcp_error_c 0x38 = Error occurred in SNDCP/LLC layer ggsn_initiated_c 0x39 = Indicates that a GGSN-initiated PDP Context Modification is started ptmsi_realloc_c 0x50 = PTMSI reallocation procedure identity_enq_c 0x51 = Identity enquiry procedure auth_c 0x52 = Authentication procedure int_sgsn_rau_det_c 0x60 = Inter PAPU and inter SGSN situations: PDPdetach request is received in RAU intra_p_rau_det_c 0x61 = Intra PAPU situation: pdp-detach request is received in RAU int_sgsn_uns_det_c 0x62 = Used in inter SGSN RAU situations when both CRs are full pwr_off_detach_c 0x63 = The MS has made a power off detach mo_activation_c 0x64 = The MS has tried to activate the same context twice og_inter_papu_att_c 0x65 = Inter PAPU attach og_inter_sgsn_att_c 0x66 = Inter SGSN attach intra_papu_rau_c 0x67 = Intra PAPU routing area update g_att_clo_exp_c 0x68 = Inter SGSN attach. the cancel location timer has expired e_est_c 0x6A = Ack context re-establishment o_pdp_in_gtp_c 0x6B = Unknown PDP context in GTP o_pdp_in_ggsn_c 0x6C = Unknown PDP context in GGSN lr_detach_c 0x6D = HLR initiated detach. necessary for PDP context bss_initiated_c 0x70 = BSS PFC download/modify procedures og_inter_sys_rau_c 0x71 = Outgoing inter system RA update cell_change_c 0x72 = PDP context modification initiated by cell change Table 22 208 Sgsn_Rtt_Cause_Ini (Cont. the cancel location timer has expired g_rau_clo_exp_c 0x69 = Inter SGSN RAU.RTT report descriptions Possible values. continued RTT report descriptions og_inter_p_3t2_sho_c 0x80 = Outgoing inter system inter PAPU RAU from 3G system to 2G og_inter_p_2t3_sho_c 0x81 = Outgoing inter system inter PAPU RAU from 2G system to 3G og_inter_s_3t2_sho_c 0x82 = Outgoing inter system inter SGSN RAU from 3G system to 2G og_inter_s_2t3_sho_c 0x83 = Outgoing inter system inter SGSN RAU from 2G system to 3G intra_p_3t2_sho_c 0x84 = Intra PAPU inter system RAU from 3G system to 2G intra_p_2t3_sho_c 0x85 = Intra PAPU inter system RAU from 2G system to 3G inter_p_3t2_sho_c 0x86 = Inter PAPU inter system RAU from 3G system to 2G inter_p_2t3_sho_c 0x87 = Inter PAPU inter system RAU from 2G system to 3G inter_s_3t2_sho_c 0x88 = Inter SGSN inter system RAU from 3G system to 2G inter_s_2t3_sho_c 0x89 = Inter SGSN inter system RAU from 2G system to 3G rnc_initiated_c 0x90 = RNC initiated procedure rab_release_c 0x91 = RAB release initiated context modify procedure paging_c 0x92 = SGSN initiated paging procedure rab_setup_c 0x93 = RAB setup in RAU procedure service_request_c 0x94 = Service request initiated procedure gtp_initiated_c 0x95 = GTP initiated RAB release intra_papu_rel_c 0xA0 = Intra PAPU relocation inter_papu_rel_c 0xA1 = Inter PAPU relocation inter_sgsn_rel_c 0xA2 = Inter SGSN relocation og_inter_papu_rel_c 0xA3 = Outgoing inter PAPU relocation og_inter_sgsn_rel_c 0xA4 = Outgoing inter SGSN relocation no_rau_after_rel_c 0xA5 = No RAU after relocation clo_after_rel_c 0xA6 = Cancel location after relocation. RAU to different unit atm_ip_change_c 0xA7= "IP address changed because of ATM connection" mas_rel_for_rab_c 0xA8= "Mass release for RABs from GTP" ot_to_2t_lic_c 0xB0= "One tunnel changed to two tunnel because of LIC" ot_to_2t_camel_c 0xB1= "One tunnel changed to two tunnel because of CAMEL" papu_bl_mass_det_c 0xB2= "Mass detach due to PAPU blocking" multi_off_mass_det_c 0xB3= "Mass detach due to Multipoint Offload" gmlc_initiated_c 0xB6= "GMLC-initiated location request" gbu_reset_c 0xB7= ”2G mass detach due to GBU reset” Field exists in the database Table 22 Cause_Ini Sgsn_Rtt_Cause_Ini (Cont.Traffica Reference Guide for SGSN Direct Interface Possible values.) DN05148836 Issue 2-2 Id:0900d805809551ce 209 . Purpose is to help coder to identify the place where the "something" has happened or to clarify the cause. Mobility Management fills this field according to the service that it is asked to offer. GPRS Mobility and Session Manager 0x440 = gs1prb. Sgsn in control application 0x403 = ggbprb. Possible values In case of Sgsn_Cause_Cause is not success_c. For example. Using family and int_cause fields we can find the exact code line where the cause was set. If Mobility Management gets an attach request. GPRS subscriber registration services 0x582 = sgiprb. GPRS Mobility and Session Management Protocol 0x404 = grnprb. Sgsn_Cause_Proc is set to value 0x0. GPRS Air Interface Transport Protocols Field exists in the database Table 23 Cause_Family Sgsn_Rtt_Cause_Family Field name Sgsn_Rtt_Cause_Int_Cause Datatype in IDS UINT16 SGSN version >=SG3 Explanation Internal cause is meant only for the use of program block that has set it and it is not customer documented. Table 25 210 Sgsn_Rtt_Cause_Proc Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Rtt_Cause_Family Datatype in IDS UINT16:46 SGSN version >=SG3 Explanation This field contains the family identifier of a process which set the cause code. Possible values Field exists in the database Table 24 Cause_Int_Cause Sgsn_Rtt_Cause_Int_Cause Field name Sgsn_Rtt_Cause_Proc Datatype in IDS UINT8 SGSN version >=SG3 Explanation This field contains procedure codes for SGSN cause. GPRS short message delivery service 0x409 = gspprb. GPRS GB Interface protocol stack 0x3FF = gipprb. GPRS IP Backbone Tunneling Protocol 0x632 = gcsprb. possible Sgsn_Cause_Family values are: 0x408 = gtpprb. GPRS Charging and Statistics Combiner Program Block 0x40A = gmgprb. Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions undefined_c. detach_c 0x20 = Detach. type unspecified pwr_off_detach_c 0x21 = Power off detach mo_gprs_detach_c 0x22 = MS-originated GPRS detach mo_comb_detach_c 0x23 = MS-originated GPRS/IMSI detach mo_imsi_detach_c 0x24 = MS-originated IMSI detach nwr_gprs_detach_c 0x25 = Network-requested GPRS detach nwr_comb_detach_c 0x26 = Network-requested GPRS/IMSI detach nwr_imsi_detach_c 0x27 = Network-requested IMSI detach impl_gprs_detach_c 0x28 = Implicit GPRS detach impl_comb_detach_c 0x29 = Implicit GPRS/IMSI detach purge_c 0x2A = Purge authentication_c 0x30 = Authentication ptmsi_realloc_c 0x31 = PTMSI reallocation imei_chk_c 0x32 = IMEI check identity_enq_c 0x33 = MS information enquiry DN05148836 Issue 2-2 Id:0900d805809551ce 211 . 0xFF = Initialisation value attach_c 0x0 Attach = unspecified gprs_attach_c 0x1 = GPRS attach comb_attach_c 0x2 = Combined GPRS/IMSI attach imsi_attach_c 0x3 = IMSI attach og_inter_sgsn_att_c 0x5 = Outgoing inter SGSN attach og_inter_papu_att_c 0x6 = Outgoing inter PAPU attach ra_update_c 0x10 RA update = type unspecified intra_papu_ra_upd_c 0x11 = Intra PAPU RA update inter_papu_ra_upd_c 0x12 = Inter PAPU RA update inter_sgsn_ra_upd_c 0x13 = Inter SGSN RA update inter_sg_ra_w_imsi_c 0x14 = Inter SGSN RA update with IMSI attach intra_papu_ra_imsi_c 0x15 = Intra PAPU RA update with IMSI attach inter_papu_ra_imsi_c 0x16 = Inter PAPU RA update with IMSI attach intra_papu_comb_upd_c 0x17 = Intra PAPU combined RA/LA update inter_papu_comb_upd_c 0x18 = Inter PAPU combined RA/A update inter_sgsn_comb_upd_c 0x19 = Inter SGSN combined RA/LA update periodic_comb_upd_c 0x1A = Periodic combined RA/LA update periodic_ra_upd_c 0x1B = Periodic RA update og_inter_papu_rau_c 0x1C = Outgoing inter PAPU RA update og_inter_sgsn_rau_c 0x1D = Outgoing inter SGSN RA update og_inter_sys_rau_c 0x1E = Outgoing inter SGSN RA update from 2G system to 3G. RTT report descriptions Pssible values continued Traffica Reference Guide for SGSN Direct Interface cs_call_c 0x34 = CS call gmm_rel_c 0x35 = GMM connection release detach_by_timer_c 0x36 = Detach timer expired lic_activation_c 0x37 = Lawful interception resume_c 0x38 = Resume og_cs_call_c 0x39 = CS call indication to old location og_inter_s_rau_relo_c 0xD7 = Outgoing inter SGSN RAU after relocation og_inter_p_rau_relo_c 0xD8 = Outgoing inter PAPU RAU after relocation inter_p_i_ra_up_rel_c 0x3A = Inter PAPU RAU after relocation with IMSI inter_s_i_ra_up_rel_c 0x3B = Inter SGSN RAU after relocation with IMSI inter_p_c_ra_up_rel_c 0x3C = Inter PAPU combined RAU after relocation inter_s_c_ra_up_rel_c 0x3D = Inter SGSN combined RAU after relocation mo_activation_c 0x60 = MS-requested PDP context activation nwr_activation_c 0x61 = Network-requested PDP context activation mo_deactivation_c 0x62 = MS-requested PDP context deactivation nwr_deactivation_c 0x63 = Network-requested PDP context deactivation modify_service_c 0x64 = Mobile.or network-originated PDP context modification Context activation to another PAPU/SGSN param_chg_service_c 0x65 = HLR-initiated PDP context modification deact_service_c 0x66 = GMC-requested PDP context deactivation implicit_deact_c 0x67 = PDP context deactivation due to network status mo_sms_c 0xA0 = Mobile-originated SMS procedure mt_sms_c 0xA1 = Mobile-terminated SMS procedure pfc_download_c 0xB1 = BSS-initiated PFC download procedure pdp_context_inact_c 0xB2 = PDP context moves to inactive state pdp_context_active_c 0xB3 = PDP context moves to active state Table 25 212 Sgsn_Rtt_Cause_Proc (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 . ) DN05148836 Issue 2-2 Id:0900d805809551ce 213 .Traffica Reference Guide for SGSN Direct Interface Possible values continued RTT report descriptions lic_deactivation_c 0xC0 = Lawful interception deactivation lic_request_c 0xC1 = Lawful interception request ssf_activity_test_c 0xC2 = The SCP sends ‘alive’ query to the SGSN ssf_continue_c 0xC3 = The SCP instructs the SGSN to continue processing bss_trace_act_c 0xC4 = Activation of BSS TRACE bss_trace_deact_c 0xC5 = Deactivation of BSS TRACE alert_req_c 0xC6 = Alert procedure og_inter_pa_3t2_sho_c 0xC7 = Outgoing inter PAPU RA update from 3G system to 2G og_inter_pa_2t3_sho_c 0xC8 = Outgoing inter PAPU RA update from 2G system to 3G intra_papu_relo_c 0xD0 = Intra PAPU relocation inter_papu_relo_c 0xD1 = Inter PAPU relocation inter_sgsn_relo_c 0xD2 = Inter SGSN relocation og_inter_papu_relo_c 0xD3 = Outgoing inter PAPU relocation og_inter_sgsn_relo_c 0xD4 = Outgoing inter SGSN relocation inter_p_ra_upd_relo_c 0xD5 = Inter PAPU RAU after relocation inter_s_ra_upd_relo_c 0xD6 = Inter SGSN RAU after relocation intra_p_rau_relo_c 0xD9 = Intra PAPU RAU after relocation service_request_c 0xE0 = Service request iu_reset_c 0xE1 = Releasing one or more Iu connection. for example in RNC reset iu_release_c 0xE2 = Releasing one Iu connection iu_sign_conn_rel_c 0xE3 = Releasing one Iu connection intra_papu_2t3_sho_c 0xE4 Intra PAPU inter system RAU from 2G system to 3G intra_p_2t3_imsi_c 0xE5 = Intra PAPU inter system RAU from 2G system to 3G with IMSI attach intra_p_2t3_comb_c 0xE6 = Combined intra PAPU inter system RAU from 2G system to 3G intra_papu_3t2_sho_c 0xE7 = Intra PAPU inter system RAU from 3G system to 2G intra_p_3t2_imsi_c 0xE8 = Intra PAPU inter system RAU from 3G system to 2G with IMSI attach intra_p_3t2_comb_c 0xE9 = Combined intra PAPU inter system RAU from 3G system to 2G inter_papu_2t3_sho_c 0xEA Inter PAPU inter system RAU from 2G system to 3G inter_p_2t3_imsi_c 0xEB Inter PAPU inter system RAU from 2G system to 3G with IMSI attach inter_p_2t3_comb_c 0xEC = Combined inter PAPU inter system RAU from 2G system to 3G inter_papu_3t2_sho_c 0xED = Inter PAPU inter system RAU from 3G system to 2G inter_p_3t2_imsi_c 0xEE = Inter PAPU inter system RAU from 3G system to 2G with IMSI attach Table 25 Sgsn_Rtt_Cause_Proc (Cont. ) Field name Sgsn_Rtt_Cgi_Ci Datatype in IDS UINT16 SGSN version >=SG3 Explanation Contains the cell identity Possible values Cell identity (CI) Field exists in the database Cgi_Ci Table 26 Sgsn_Rtt_Cgi_Ci Field name Sgsn_Rtt_Cgi_Lac Datatype in IDS UINT16 SGSN version >=SG3 Explanation Location area code for the most recent cell Possible values Location are code (LAC) Field exists in the database Cgi_Lac Table 27 Sgsn_Rtt_Cgi_Lac Field name Sgsn_Rtt_Cgi_Mcc Datatype in IDS BCD8(2) SGSN version >=SG3 Explanation Contains the country code Possible values Mobile country code (MCC) Field exists in the database Cgi_Mcc Table 28 Sgsn_Rtt_Cgi_Mcc Field name Sgsn_Rtt_Cgi_Mnc Datatype in IDS BCD8(2) SGSN version >=SG3 Explanation Mobile network code for most recent cell Table 29 214 Sgsn_Rtt_Cgi_Mnc Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Possible values continued Traffica Reference Guide for SGSN Direct Interface inter_p_3t2_comb_c 0xEF = Combined intra PAPU inter system RAU from 3G system to 2G rab_create_c 0xF0 = RAB create gmm_info_c 0xF1 = GMM information Field exists in the database Table 25 Cause_Proc Sgsn_Rtt_Cause_Proc (Cont. Traffica Reference Guide for SGSN Direct Interface Possible values Mobile network code (MNC) Field exists in the database Cgi_Mnc Table 29 Sgsn_Rtt_Cgi_Mnc (Cont. and it is valid during the whole PDP context (even if SGSN changes). Information is used for charging record correlation in Billing System. Charging index is included in SGSN_PDP_RTT report. Table 32 Sgsn_Rtt_Charging_Info DN05148836 Issue 2-2 Id:0900d805809551ce 215 .) Field name Sgsn_Rtt_Cgi_Rac Datatype in IDS UINT8 SGSN version >=SG3 Explanation Routing area code for the most recent cell Possible values Routing area code (RAC) Field exists in the database Cgi_Rac Table 30 RTT report descriptions Sgsn_Rtt_Cgi_Rac Field name Sgsn_Rtt_Charging_Index Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the charging index which identifies the PDP context. Possible values 0x00 . Value is received from GGSN in PDP context creation.0xFFFF FFFF Field exists in the database Charging_Index Table 31 Sgsn_Rtt_Charging_Index Field name Sgsn_Rtt_Charging_Info Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains charging characteristics of the user. They are always added to charging type values if they are used. Field exists in the database Table 32 Charging_Info Sgsn_Rtt_Charging_Info (Cont.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface Possible values for charging type are: normal_c = 8 prepaid_c = 4 flat_rate_c = 2 hot_billing_c = 1 no_def_c = 0 Possible additional values are: in_prepaid_c = 32 cell_update_c = 16 Note that In_prepaid_c or cell_update_c cannot alone be the charging info value. Examples: Normal + in prepaid = 8 + 32 = 40 Prepaid + cell update = 4 + 16 = 20 Depending on the character. for example. There is also a parameter for the flat rate CDR generation. The IN prepaid CDRs are created according to the normal CDR triggers. the charging load becomes too high.) Field name Sgsn_Rtt_Cs_External_Cause Datatype in IDS UINT8 SGSN version >=SG4 Table 33 216 Sgsn_Rtt_Cs_External_Cause Id:0900d805809551ce DN05148836 Issue 2-2 . different CDR creation triggers are used: for GPRS server based prepaid users. the prepaid triggers are used and for other users. the normal triggers are used. The flat rate CDR generation can be turned off if. The separate prepaid triggers enable charging to be closer to real-time for the prepaid subscribers than for the other subscribers. Rtt_Sgsn_Cause_Proc and Rtt_Sgsn_Cause_Cause combination is one of the following: MESSAGE TOWARDS MS: attach accept routing area update accept SGSN_CAUSE_PROC: COMB_ATTACH_C INTER_SG_RA_W_IMSI_C/ INTRA_PAPU_RA_IMSI_C/ INTER_PAPU_RA_IMSI_C/ INTRA_PAPU_COMB_UPD_C/ INTER_PAPU_COMB_UPD_C/ INTER_SGSN_COMB_UPD_C/ PERIODIC_COMB_UPD_C SUCCESS_C SGSN_CAUSE_CAUSE: SUCCESS_C If SGSN_CAUSE_CAUSE is not SUCCESS_C and procedure is combined attach or combined RAU Sgsn_CS_External_Cause is set to value 0xFF because SGSN does not try procedure to CS side at all if PS side fails. External CS cause values towards MS (reject cause of attach accept and routing area update accept) are described in 3GPP TS 24. Table 33 Sgsn_Rtt_Cs_External_Cause (Cont. See internal error cause in field Sgsn_Rtt_Non_Gprs_Cause_Cause. For mapping between external (GSM standard) and internal error causes see appendix SG3/SG4 INTERNAL CAUSE TO INTERFACE CAUSE MAPPING FROM MM & SM PROCESSES.008) in case of combined attach or combined RAU.) DN05148836 Issue 2-2 Id:0900d805809551ce 217 .008. This field has other values than 0xFF if message that is sent to MS.Traffica Reference Guide for SGSN Direct Interface Explanation RTT report descriptions This field refers to optional field called ‘reject cause’ of attach accept and routing area update accept messages sent to MS (see 3GPP TS 24. 0x0F= No suitable cells in LA 0x10= MSC not reachable This cause is sent to the MS if it requests a combined GPRS attach or routing are updating in a PLMN where the MSC is temporarily not reachable via the GPRS part of the GSM network. 0x07= GPRS service not allowed This cause is sent to the MS if it requests a combined IMSI attach for GPRS and non-GPRS services. 0x09= MS identity unknown This cause is sent to the MS either if the network has implicitly detached the MS. 0x05= IMEI not accepted This cause is sent to the MS if the network does not accept emergency call establishment using an IMEI.) Id:0900d805809551ce DN05148836 Issue 2-2 . 0x0A= Implicitly detached 0x0B= PLMN not allowed This cause is sent to the MS if it requests location updating in a PLMN where the MS. 0x0E= GPRS serv not allwd in PLMN This cause is sent to the MS which requests GPRS service in a PLMN which does not offer roaming for GPRS services to that MS. 0x06= Illegal ME This cause is sent to the MS if the ME used is not acceptable to the network. blacklisted. by subscription. 0x03= Illegal MS This cause is sent to the MS when the network refuses service to the MS either because an identity of the MS is not acceptable to the network or because the MS does not pass the authentication check. 0x0D= LA roaming error This cause is sent to an MS which requests location updating in a location area of a PLMN which offers roaming to that MS in that Location Area. for example. 0x04= IMSI unknown in VLR This cause is sent to the MS when the given IMSI is not known at the VLR. by subscription.e. is not allowed to operate. if it is. by subscription or due to operator determined barring is not allowed to operate. but is not allowed to operate either of them. although it may be used by a GMM procedure.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface 0x00= Success 0xFF= Undefined 0x02= IMSI unknown in HLR This cause is sent to the MS if the MS is not known (registered) in the HLR. for example some time after the Mobile reachable timer has expired. 0x0C= LA not allowed This cause is sent to the MS if it requests location updating in a location area where the MS. or if the GMM context data related to the subscription does not exist in the SGSN. This cause code does not affect the operation of the GPRS service. 0x08= GPRS/non-GPRS serv not allowed / oper deter barring This cause is sent to the MS when the network cannot derive the MS's identity from the P-TMSI in case of inter-SGSN routing area update. Table 33 218 Sgsn_Rtt_Cs_External_Cause (Cont. the SRES received from the MS is different from that generated by the network. for example because of a SGSN restart. i. facility busy/congested etc. 0x21= Requested service option not subscribed This cause is sent when the MS requests a service option for which it has no subscription. if the SM receives a SNSM-STATUS. Table 33 Sgsn_Rtt_Cs_External_Cause (Cont. 0x23= NSAPI already used This cause code may be used by a network to indicate that the NSAPI requested by the MS in the PDP context activation request is already used by another active PDP context of this MS. 0x14= MAC failure 0x15= Synch failure 0x16= Congestion This cause is sent if the service request cannot be sent because of congestion (for example.65 [78]) 0x1A= Insufficient resources This cause code is used by the MS or by the network to indicate that a PDP context activation request. 0x1D= User auth failed This cause code is used by the network to indicate that the requested service was rejected by the external packet data network due to a failed user authentication. or if the access point name could not be resolved. see GSM 04. 0x22= Service option temporarily out of order This cause is sent when the MSC cannot service the request because of temporary outage of one or more functions required for supporting the service. no channel. secondary PDP context activation request or PDP context modification request cannot be accepted due to insufficient resources.) DN05148836 Issue 2-2 Id:0900d805809551ce 219 . 0x1E= Activation rejected by GGSN This cause code is used by the network to indicate that the requested service was rejected by the GGSN. although required.) 0x28= No PDP context activated 0x19= LLC or SNDCP failure. 0x20= Service option not supported This cause code is used by the network when the MS requests a service which is not supported by the PLMN. This cause code is used by the MS to indicate that a PDP context is deactivated because of a LLC or SNDCP failure (for example.request message with cause DM received or invalid XID response.Traffica Reference Guide for SGSN Direct Interface Possible values (continued) RTT report descriptions 0x11= Network failure This cause is sent to the MS if the MSC cannot service an MS generated request because of PLMN failures. 0x1F= Activation rejected. 0x1C= Unknown PDP address or type This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because the PDP address or type could not be recognised. for example problems in MAP. unspecified This cause code is used by the network to indicate that the requested service was rejected due to unspecified reasons. 0x1B= Missing or unknown APN This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because the access point name was not included. Table 33 220 Sgsn_Rtt_Cs_External_Cause (Cont. 0x51= Invalid transaction identifier value 0x5F= Semantically incorrect message This cause is used to report receipt of a message with semantically incorrect contents. that were indicated by the network in the PDP Context Modification procedure. 0x26= Network failure This cause code is used by the network to indicate that the PDP context deactivation is caused by an error situation in the network. cannot be accepted. 0x25= QoS not accepted This cause code is used by the MS if the new QoS. 0x2E= PDP context without TFT already activated This cause code is used by the network to indicate that the network has already activated a PDP context without TFT. 0x2C= Semantic errors in packet filter(s) This cause code is used by the network to indicate that there is one or more semantic errors in the packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification. 0x29= Semantic error in TFT operation This cause code is used by the network to indicate that the there is a semantic error in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification. 0x28= Feature not supported This cause code is used by the MS to indicate that the PDP context activation initiated by the network is not supported by the MS. 0x60= Invalid mandatory information This cause indicates that the equipment sending this cause has received a message with a non-semantical mandatory IE error. 0x61= Message type non-existent or not implemented 0x62= Message not compatible with protocol state This cause indicates that the equipment sending this cause has received a message not compatible with the protocol state. 0x2A= Syntactical error in TFT operation This cause code is used by the network to indicate that there is a syntactical error in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification. 0x27= Reactivation requested This cause code is used by the network to request a PDP context reactivation after a GGSN restart.RTT report descriptions Possible values (continued) Traffica Reference Guide for SGSN Direct Interface 0x24= Regular PDP context deactivation This cause code is used to indicate a regular MS or network initiated PDP context deactivation. 0x2D= Syntactical error in packet filter(s) This cause code is used by the network to indicate that there is one or more syntactical errors in the packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification.) Id:0900d805809551ce DN05148836 Issue 2-2 . 0x2B= unknown PDP context This cause code is used by the network to indicate that the PDP context identified by the Linked TI IE the secondary PDP context activation request is not active. This field contains user downlink data between the last SGSN_PDP_THR_STAT and this SGSN_PDP_RTT. Possible values 0x00 . Possible values 0x00 . Field exists in the database Table 33 Cs_External_Cause Sgsn_Rtt_Cs_External_Cause (Cont. In other events this field is set to zero value. 0x6F= Protocol error. 0x64= Conditional IE error This cause indicates that the equipment sending this cause has received a message with conditional IE errors. However.Traffica Reference Guide for SGSN Direct Interface Possible values (continued) RTT report descriptions 0x63= Information element non-existent or not implemented This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause. This field contains user uplink data between the last SGSN_PDP_THR_STAT and this SGSN_PDP_RTT. This field is used only in pdp context deactivation. unspecified This cause is used for reporting a protocol error event only when no other cause in the protocol error class applies. This field is used only in pdp context deactivation.) Field name Sgsn_Rtt_Data_Amount_Down Datatype in IDS UINT32 SGSN version >=SG4 Explanation Data amount in bytes. the information element is not required to be presented in the message in order for the equipment sending the cause to process the message. 0x65= Message not compatible with protocol state This cause indicates that a message has been received which is incompatible with the protocol state or that a STATUS message has been received indicating an incompatible call state.0xFFFF FFFF Field exists in the database Data_Amount_Down Table 34 Sgsn_Rtt_Data_Amount_Down Field name Sgsn_Rtt_Data_Amount_Up Datatype in IDS UINT32 SGSN version >=SG4 Explanation Data amount in bytes. In other events this field is set to zero value.0xFFFF FFFF Field exists in the database Data_Amount_Up Table 35 Sgsn_Rtt_Data_Amount_Up Field name Table 36 Sgsn_Rtt_Ext_Data_Amount_Down Sgsn_Rtt_Ext_Data_Amount_Down DN05148836 Issue 2-2 Id:0900d805809551ce 221 . Possible values 0x00 .0xFFFF FFFF FFFF FFFF Field exists in the database Ext_Data_Amount_Up Table 37 Sgsn_Rtt_Data_Amount_Up Field name Sgsn_Rtt_Event_Count Datatype in IDS UINT32 SGSN version >=SG3 Explanation Contains information on how many events of the type have been detected and whether they are reported to Traffica. This field is not used for detach procedure. Large RA Support is not activated. Table 39 222 Sgsn_Rtt_Forwarded Id:0900d805809551ce DN05148836 Issue 2-2 . If procedure is detach.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Datatype in IDS UINT64 SGSN version >=SG7 Explanation Data amount in bytes. This field contains user uplink data between the last SGSN_PDP_THR_STAT and this SGSN_PDP_RTT. This field is used only in pdp context deactivation.0xFFFF FFFF FFFF FFFF Field exists in the database Ext_Data_Amount_Down Table 36 Sgsn_Rtt_Ext_Data_Amount_Down (Cont. Possible values 0x00 .) Field name Sgsn_Rtt_Ext_Data_Amount_Up Datatype in IDS UINT64 SGSN version >=SG7 Explanation Data amount in bytes. Possible values 0x0-0xFFFFFFFF The value of the counter is reset everyday at 00:00 a. This field is used only in pdp context deactivation. This field contains user downlink data between the last SGSN_PDP_THR_STAT and this SGSN_PDP_RTT. This field is always 0 if feature. this field is set to value 0x0.m. In other events this field is set to zero value. In other events this field is set to zero value. Field exists in the database Table 38 Event_Count Sgsn_Rtt_Event_Count Field name Sgsn_Rtt_Forwarded Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains information if the message was forwarded from other unit. 125. instead of Sgsn_Rtt_Ggsn_Address Possible values Field exists in the database Table 41 No Sgsn_Rtt_Ggsn_Address_Value Field name Sgsn_Rtt_Ggsn_Address_Version Datatype in IDS UINT8 SGSN version >=SG3 Explanation Contains the version of the IP address of the GGSN Possible values 0x0=IPv4. 0x1=IPv6 Field exists in the database Ggsn_Address_Version Table 42 Sgsn_Rtt_Ggsn_Address_Version Field name Sgsn_Rtt_Imei Datatype in IDS BCD8(8) SGSN version >=SG3 Explanation Contains the IMEI-number that caused the report to be sent Table 43 Sgsn_Rtt_Imei DN05148836 Issue 2-2 Id:0900d805809551ce 223 .124.) Field name Sgsn_Rtt_Ggsn_Address Datatype in IDS IPADDR(16) SGSN version >=SG3 Explanation Contains the IP address of the GGSN. Possible values IDS: First four bytes contains IPv4 GGSN address. for example 128. Database: IPv4 address in dotted format.11 Field exists in the database Ggsn_Address Table 40 Sgsn_Rtt_Ggsn_Address Field name Sgsn_Rtt_Ggsn_Address_Value Datatype in IDS STRINGICRC32 SGSN version >=SG6 Explanation This field is used in defining the CCMA.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions 0x0 = Normal message 0x1 = Forwarded message Field exists in the database Table 39 Forwarded Sgsn_Rtt_Forwarded (Cont. This field is used only in the case of a PDP context activation event. NOTE: This field value is valid only when the IMEI is IMEISV (16 digits).) Field name Sgsn_Rtt_Imei_Final_Assembly_Code Datatype in IDS BCD32 SGSN version >=SG3 Explanation The 7th and 8th digit of IMEI. in which case this field does not contain a valid value. Identifies the mobile station software version.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Possible values IMEI Field exists in the database Imei Table 43 Sgsn_Rtt_Imei (Cont. Possible values Field exists in the database Table 46 No Sgsn_Rtt_Imei_Software_Version_Number Field name Sgsn_Rtt_Imsi Datatype in IDS BCD8(8) Table 47 224 Sgsn_Rtt_Imsi Id:0900d805809551ce DN05148836 Issue 2-2 . The length of an IMEI can also be only 15 digits. Identifies the final assembly code of the mobile model. Possible values Field exists in the database Table 44 No Sgsn_Rtt_Imei_Final_Assembly_Code Field name Sgsn_Rtt_Imei_Mobile_Type Datatype in IDS BCD32 SGSN version >=SG3 Explanation Shows the mobile model of the IMEI number that caused the report to be sent Possible values Field exists in the database Table 45 No Sgsn_Rtt_Imei_Mobile_Type Field name Sgsn_Rtt_Imei_Software_Version_Number Datatype in IDS BCD32 SGSN version >=SG3 Explanation The 16th and 17th digit of the IMEI. Table 51 Sgsn_Rtt_Ms_Pdp_Address DN05148836 Issue 2-2 Id:0900d805809551ce 225 .) Field name Sgsn_Rtt_Imsi_Country Datatype in IDS BCD32 SGSN version >=SG3 Explanation Shows the country code of the IMSI number that caused the report to be sent Possible values Field exists in the database Table 48 No Sgsn_Rtt_Imsi_Country Field name Sgsn_Rtt_Imsi_Home_Network Datatype in IDS BCD32 SGSN version >=SG3 Explanation MCC+MNC from IMSI Possible values Field exists in the database Table 49 No Sgsn_Rtt_Imsi_Home_Network Field name Sgsn_Rtt_Imsi_Length Datatype in IDS UINT8 SGSN version >=SG3 Explanation Contains the length of the IMSI-number that caused the report to be sent Possible values 0x0-0xFF Field exists in the database Imsi_Length Table 50 Sgsn_Rtt_Imsi_Length Field name Sgsn_Rtt_Ms_Pdp_Address Datatype in IDS IPADDR SGSN version SG6 Explanation PDP address.Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG3 Explanation Contains the IMSI-number that caused the report to be sent Possible values IMSI Field exists in the database Imsi Table 47 RTT report descriptions Sgsn_Rtt_Imsi (Cont. x25_min_len_c = 1 x25_max_len_c = 7 etsi_c = 0 ietf_c =1 0xFFFFFFFF Field exists in the database Table 52 Ms_Pdp_Address_Len Sgsn_Rtt_Ms_Pdp_Address_Len Field name Sgsn_Rtt_Ms_Pdp_Address_Organization Datatype in IDS UINT8 SGSN version SG6 Explanation PDP organization. Field exists in the database Ms_Pdp_Address Table 51 Sgsn_Rtt_Ms_Pdp_Address (Cont. Table 54 226 Sgsn_Rtt_Ms_Pdp_Address_Type Id:0900d805809551ce DN05148836 Issue 2-2 . which is used to bind a mobile station (MS) to various PDP addresses and to unbind the MS from these addresses after use. Network level information. ipv6_len_c = 16. Possible values 0xFF Field exists in the database Ms_Pdp_Address_Organization Table 53 Sgsn_Rtt_Ms_Pdp_Address_Organization Field name Sgsn_Rtt_Ms_Pdp_Address_Type Datatype in IDS UINT8 SGSN version SG6 Explanation PDP type. Length of the PDP address Possible values empty_c = 0 (contains no valid value) ipv4_len_c = 4.) Field name Sgsn_Rtt_Ms_Pdp_Address_Len Datatype in IDS UINT32 SGSN version SG6 Explanation Packet Data Protocol type and MS address.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Possible values undefined_c = 0xFF. 214 9 = PNP Bits 5-7: Nature of address 0 = unknown 1 = int 2 = nat 3 = nets 4 = subs Bit 8: Extension 1 = no_ext 0 = ext Field exists in the database Table 56 No Sgsn_Rtt_Msisdn_Indicators DN05148836 Issue 2-2 Id:0900d805809551ce 227 . ipv6_c = 0x57.212 7 = E.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions undefined_c = 0xFF ipv4_c = 0x21. x25_c = 0x0 Field exists in the database Table 54 Ms_Pdp_Address_Type Sgsn_Rtt_Ms_Pdp_Address_Type (Cont.164 6 = E.) Field name Sgsn_Rtt_Msisdn_Address_Length Datatype in IDS UINT8 SGSN version >=SG3 Explanation Length of the Msisdn number Possible values Field exists in the database Table 55 No Sgsn_Rtt_Msisdn_Address_Length Field name Sgsn_Rtt_Msisdn_Indicators Datatype in IDS UINT8 SGSN version >=SG3 Explanation MSISDN number indicators Possible values Bits 1-4: Numbering plan 0 = Unknown 1 = E. Possible values 0x0 = subscribed delay class requested 0x1 = delay class 1 0x2 = delay class 2 0x3 = delay class 3 0x4 = delay class 4 (best effort). DEFAULT Field exists in the database Table 59 Neg_Qos_Delay_Class Sgsn_Rtt_Neg_Qos_Delay_Class Field name Sgsn_Rtt_Neg_Qos_Delivery_Erroneous Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Rtt_Msisdn_Numbers Datatype in IDS BCD8(9) SGSN version >=SG3 Explanation MSISDN number of the subscriber Possible values MSISDN number Field exists in the database Yes Table 57 Sgsn_Rtt_Msisdn_Numbers Field name Sgsn_Rtt_Neg_Qos_Alloc_Retention Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Field exists in the database Table 58 Neg_Qos_Alloc_Retention Sgsn_Rtt_Neg_Qos_Alloc_Retention Field name Sgsn_Rtt_Neg_Qos_Delay_Class Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Table 60 228 Sgsn_Rtt_Neg_Qos_Delivery_Erroneous Id:0900d805809551ce DN05148836 Issue 2-2 . Do not pay attention to this field's value if release 97/98 is in use. Possible values 0x0 .0xFF NOTE: This field is in use only with QoS Release 99. ) Field name Sgsn_Rtt_Neg_Qos_Delivery_Order Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. DEFAULT 0x2 = Without delivery order (“no”) NOTE: This field is in use only with QoS Release 99. Do not pay attention to this field's value if release 97/98 is in use. Table 62 Sgsn_Rtt_Neg_Qos_Guaran_Bit_Rate_Dl DN05148836 Issue 2-2 Id:0900d805809551ce 229 . Possible values 0x0 = Subscribed delivery order requested 0x1 = With delivery order (“yes”). Do not pay attention to this field's value if release 97/98 is in use. DEFAULT NOTE: This field is in use only with QoS Release 99.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions 0x0 = Subscribed delivery of erroneous SDUs requested 0x1 = no detect (“-”)' 0x2 = Erroneous SDUs are delivered (“yes”) 0x3 = Erroneous SDUs are not delivered (“no”). Field exists in the database Table 61 Neg_Qos_Delivery_Order Sgsn_Rtt_Neg_Qos_Delivery_Order Field name Sgsn_Rtt_Neg_Qos_Guaran_Bit_Rate_Dl Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Field exists in the database Table 60 Neg_Qos_Delivery_Erroneous Sgsn_Rtt_Neg_Qos_Delivery_Erroneous (Cont. NOTE: This field is in use only with QoS Release 99 or newer. Bit rate value calculations should be started from extended fields. Do not pay attention to this field's value if release 97/98 is in use. ‘11111111’: 0kbps If Maximum bit rate is higher than 8640 kbps. In MS to network direction and in network to MS direction: ‘00000001’-‘00111111’: The maximum bit rate is binary coded in 8 bits.) Field name Sgsn_Rtt_Neg_Qos_Guaran_Bit_Rate_Ul Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface Values are specified in 3GPP 24. If the extended fields have a '0'.008 in chapter 10. In MS to network direction: ‘00000000’: MS request subscribed maximum bit rate.5. ‘10000000’-‘11111110’: The maximum bit rate is 576 kbps + ((the binary coded value in 8 bits –10000000) * 64 kbps) giving a range of values from 576 kbps to 8640 kbps in 64 kbps increments.5. value is set as ‘11111110’.e. using a granularity of 1 kbps giving a range of values from 1 kbps to 63 kbps in 1 kbps increments. Field exists in the database Table 62 Neg_Qos_Guaran_Bit_Rate_Dl Sgsn_Rtt_Neg_Qos_Guaran_Bit_Rate_Dl (Cont. 8640 kbps and shall encode the value to Sgsn_Rtt_Neg_Qos_Ext_Guar_Br_Dl. i. Table 63 230 Sgsn_Rtt_Neg_Qos_Guaran_Bit_Rate_Ul Id:0900d805809551ce DN05148836 Issue 2-2 .6. ‘01000000’-‘01111111’: The maximum bit rate is 64 kbps + ((the binary coded value in 8 bits –01000000) * 8 kbps) giving a range of values from 64 kbps to 568 kbps in 8 kbps increments. ignore the value and use values from the nonextended fields. using a granularity of 1 kbps giving a range of values from 1 kbps to 63 kbps in 1 kbps increments.5. If the extended fields have a '0'. Table 64 Sgsn_Rtt_Neg_Qos_Max_Bit_Rate_For_Dl DN05148836 Issue 2-2 Id:0900d805809551ce 231 . 8640 kbps and shall encode the value to Sgsn_Rtt_Neg_Qos_Ext_Guar_Br_Ul.5. Do not pay attention to this field's value if release 97/98 is in use.e. Bit rate value calculations should be started from extended fields.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions Values are specified in 3GPP 24. ‘10000000’-‘11111110’: The maximum bit rate is 576 kbps + ((the binary coded value in 8 bits –10000000) * 64 kbps) giving a range of values from 576 kbps to 8640 kbps in 64 kbps increments. In MS to network direction and in network to MS direction: ‘00000001’-‘00111111’: The maximum bit rate is binary coded in 8 bits. NOTE: This field is in use only with QoS Release 99 or newer. Field exists in the database Table 63 Neg_Qos_Guaran_Bit_Rate_Ul Sgsn_Rtt_Neg_Qos_Guaran_Bit_Rate_Ul (Cont.008 in chapter 10. value is set as ‘11111110’. ‘11111111’: 0kbps If Maximum bit rate is higher than 8640 kbps. i. In MS to network direction: ‘00000000’: MS request subscribed maximum bit rate. ‘01000000’-‘01111111’: The maximum bit rate is 64 kbps + ((the binary coded value in 8 bits –01000000) * 8 kbps) giving a range of values from 64 kbps to 568 kbps in 8 kbps increments. ignore the value and use values from the nonextended fields.6.) Field name Sgsn_Rtt_Neg_Qos_Max_Bit_Rate_For_Dl Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Do not pay attention to this field's value if release 97/98 is in use.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface Values are specified in 3GPP 24. Bit rate value calculations should be started from extended fields. i.) Field name Sgsn_Rtt_Neg_Qos_Max_Bit_Rate_For_Ul Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. using a granularity of 1 kbps giving a range of values from 1 kbps to 63 kbps in 1 kbps increments. Table 65 232 Sgsn_Rtt_Neg_Qos_Max_Bit_Rate_For_Ul Id:0900d805809551ce DN05148836 Issue 2-2 . If the extended fields have a '0'. In MS to network direction: ‘00000000’: MS request subscribed maximum bit rate.e.6.008 in chapter 10. 8640 kbps and shall encode the value to Sgsn_Rtt_Neg_Qos_Ext_Max_Br_Dl. ‘10000000’-‘11111110’: The maximum bit rate is 576 kbps + ((the binary coded value in 8 bits –10000000) * 64 kbps) giving a range of values from 576 kbps to 8640 kbps in 64 kbps increments.5. NOTE: This field is in use only with QoS Release 99 or newer. value is set as ‘11111110’. ignore the value and use values from the nonextended fields. Field exists in the database Table 64 Neg_Qos_Max_Bit_Rate_For_Dl Sgsn_Rtt_Neg_Qos_Max_Bit_Rate_For_Dl (Cont.5. ‘11111111’: 0kbps If Maximum bit rate is higher than 8640 kbps. ‘01000000’-‘01111111’: The maximum bit rate is 64 kbps + ((the binary coded value in 8 bits –01000000) * 8 kbps) giving a range of values from 64 kbps to 568 kbps in 8 kbps increments. In MS to network direction and in network to MS direction: ‘00000001’-‘00111111’: The maximum bit rate is binary coded in 8 bits. Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions Values are specified in 3GPP 24.008 in chapter 10.5.6.5. In MS to network direction: ‘00000000’: MS request subscribed maximum bit rate. In MS to network direction and in network to MS direction: ‘00000001’-‘00111111’: The maximum bit rate is binary coded in 8 bits, using a granularity of 1 kbps giving a range of values from 1 kbps to 63 kbps in 1 kbps increments. ‘01000000’-‘01111111’: The maximum bit rate is 64 kbps + ((the binary coded value in 8 bits –01000000) * 8 kbps) giving a range of values from 64 kbps to 568 kbps in 8 kbps increments. ‘10000000’-‘11111110’: The maximum bit rate is 576 kbps + ((the binary coded value in 8 bits –10000000) * 64 kbps) giving a range of values from 576 kbps to 8640 kbps in 64 kbps increments. ‘11111111’: 0kbps If Maximum bit rate is higher than 8640 kbps, value is set as ‘11111110’, i.e. 8640 kbps and shall encode the value to Sgsn_Rtt_Neg_Qos_Ext_Max_Br_Ul. Bit rate value calculations should be started from extended fields. If the extended fields have a '0', ignore the value and use values from the nonextended fields. NOTE: This field is in use only with QoS Release 99 or newer. Do not pay attention to this field's value if release 97/98 is in use. Field exists in the database Table 65 Neg_Qos_Max_Bit_Rate_For_Ul Sgsn_Rtt_Neg_Qos_Max_Bit_Rate_For_Ul (Cont.) Field name Sgsn_Rtt_Neg_Qos_Max_Sdu_Size Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x0 = Subscribed maximum SDU size requested 0x96 = Upper limit of max SDU size (1500 octets), DEFAULT NOTE: This field is in use only with QoS Release 99. Do not pay attention to this field's value if release 97/98 is in use. Field exists in the database Table 66 Neg_Qos_Max_Sdu_Size Sgsn_Rtt_Neg_Qos_Max_Sdu_Size Field name Sgsn_Rtt_Neg_Qos_Mean_Throughput Datatype in IDS UINT8 Table 67 Sgsn_Rtt_Neg_Qos_Mean_Throughput DN05148836 Issue 2-2 Id:0900d805809551ce 233 RTT report descriptions Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x0 = subscribed mean throughput requested 0x1F = best effort 0x1 = up to 100 octet/h (~0.22 bit/s), DEFAULT 0x2 = 100 to 200 octet/h (~0.44 bit/s) 0x3 = 200 to 500 octet/h (~1.11 bit/s) 0x4 = 500 to 1000 octet/h (~2.2 bit/s) 0x5 = 1000 to 2000 octet/h (~4.4 bit/s) 0x6 = 2000 to 5000 octet/h (~11.1 bit/s) 0x7 = 5000 to 10000 octet/h (~22 bit/s) 0x8 = 10000 to 20000 octet/h (~44 bit/s) 0x9 = 20000 to 50000 octet/h (~111 bit/s) 0xA = 50000 to 100000 octet/h (~0.22 kbit/s) 0xB = 100000 to 200000 octet/h (~0.44 kbit/s) 0xC = 200000 to 500000 octet/h (~1.11 kbit/s) 0xD = 500000 to 1000000 octet/h (~2.2 kbit/s) 0xE = 1000000 to 2000000 octet/h (~4.4 kbit/s) 0xF = 2000000 to 5000000 octet/h (~11.1 kbit/s) 0x10 = 5000000 to 10000000 octet/h (~22 kbit/s) 0x11 = 10000000 to 20000000 octet/h (~44 kbit/s) 0x12 = 20000000 to 50000000 octet/h (~111 kbit/s) Field exists in the database Table 67 Neg_Qos_Mean_Throughput Sgsn_Rtt_Neg_Qos_Mean_Throughput (Cont.) Field name Sgsn_Rtt_Neg_Qos_Ms_Cont_Prof_Flag Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x0 = Release 97/98 0x1 = Release 99 Field exists in the database Table 68 Neg_Qos_Ms_Cont_Prof_Flag Sgsn_Rtt_Neg_Qos_Ms_Cont_Prof_Flag Field name Sgsn_Rtt_Neg_Qos_Peak_Throughput Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Table 69 234 Sgsn_Rtt_Neg_Qos_Peak_Throughput Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions 0x0 = subscribed peak throughput requested 0x1 = up to 1000 octet/s 0x2 = 1000 to 2000 octet/s 0x3 = 2000 to 4000 octet/s 0x4 = 4000 to 8000 octet/s 0x5 = 8000 to 16000 octet/s 0x6 = 16000 to 32000 octet/s 0x7 = 32000 to 64000 octet/s 0x8 = 64000 to 128000 octet/s 0x9 = 128000 to 256000 octet/s, DEFAULT Field exists in the database Table 69 Neg_Qos_Peak_Throughput Sgsn_Rtt_Neg_Qos_Peak_Throughput (Cont.) Field name Sgsn_Rtt_Neg_Qos_Precedence Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x0 = subscribed precedence class requested 0x1 = high priority 0x2 = normal priority, DEFAULT 0x3 = low priority Field exists in the database Table 70 Neg_Qos_Precedence Sgsn_Rtt_Neg_Qos_Precedence Field name Sgsn_Rtt_Neg_Qos_Reliability_Class Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x0 = subscribed reliability class requested 0x1 = acknowledged GTP, LLC and RLC; Protected 0x2 = unacknowledged GTP, acknowledged LLC and RLC; Protected, DEFAULT 0x3 = unacknowledged GTP, LLC, acknowledged RLC; Protected 0x4 = unacknowledged GTP, LLC and RLC; Protected 0x5 = unacknowledged GTP, LLC and RLC; Unprotected Field exists in the database Table 71 Neg_Qos_Reliability_Class Sgsn_Rtt_Neg_Qos_Reliability_Class DN05148836 Issue 2-2 Id:0900d805809551ce 235 RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Rtt_Neg_Qos_Residual_Ber Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x0 = Subscribed residual BER requested 0x1 = Residual BER, value 5*10^-2 0x2 = Residual BER, value 1*10^-2 0x3 = Residual BER, value 5*10^-3 0x4 = Residual BER, value 4*10^-3 0x5 = Residual BER, value 1*10^-3 0x6 = Residual BER, value 1*10^-4 0x7 = Residual BER, value 1*10^-5, DEFAULT 0x8 = Residual BER, value 1*10^-6 0x9 = Residual BER, value 1*10^-8 NOTE: This field is in use only with QoS Release 99. Do not pay attention to this field's value if release 97/98 is in use. Field exists in the database Table 72 Neg_Qos_Residual_Ber Sgsn_Rtt_Neg_Qos_Residual_Ber Field name Sgsn_Rtt_Neg_Qos_Sdu_Error_Ratio Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x0 = Subscribed SDU error ratio requested 0x1 = SDU error ratio, value 1*10^-2 0x2 = SDU error ratio, value 7*10^-3 0x3 = SDU error ratio, value 1*10^-3 0x4 = SDU error ratio, value 1*10^-4 0x5 = SDU error_ratio, value 1*10^-5 0x6 = SDU error ratio, value 1*10^-6, DEFAULT 0x7 = SDU error ratio, value 1*10^-1 NOTE: This field is in use only with QoS Release 99. Do not pay attention to this field's value if release 97/98 is in use. Field exists in the database Table 73 Neg_Qos_Sdu_Error_Ratio Sgsn_Rtt_Neg_Qos_Sdu_Error_Ratio Field name Sgsn_Rtt_Neg_Qos_Traffic_Class Datatype in IDS UINT8 Table 74 236 Sgsn_Rtt_Neg_Qos_Traffic_Class Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface RTT report descriptions SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x0 = Subscribed traffic class requested 0x1 = Conversational class 0x2 = Streaming class 0x3 = Interactive class, DEFAULT 0x4 = Background class NOTE: This field is in use only with QoS Release 99. Do not pay attention to this field's value if release 97/98 is in use. Field exists in the database Table 74 Neg_Qos_Traffic_Class Sgsn_Rtt_Neg_Qos_Traffic_Class (Cont.) Field name Sgsn_Rtt_Neg_Qos_Traff_Handling_Prio Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x0 = Subscribed traffic handling priority requested 0x1 = Traffic handling priority, level 1, DEFAULT 0x2 = Traffic handling priority, level 2 0x3 = Traffic handling priority, level 3 NOTE: This field is in use only with QoS Release 99. Do not pay attention to this field's value if release 97/98 is in use. Field exists in the database Table 75 Neg_Qos_Traff_Handling_Prio Sgsn_Rtt_Neg_Qos_Traff_Handling_Prio Field name Sgsn_Rtt_Neg_Qos_Transfer_Delay Datatype in IDS UINT8 SGSN version >=SG4 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x0 - 0xFF Field exists in the database Neg_Qos_Transfer_Delay Table 76 Sgsn_Rtt_Neg_Qos_Transfer_Delay Field name Sgsn_Rtt_Non_Gprs_Cause_Cause Datatype in IDS UINT32 SGSN version >=SG4 Table 77 Sgsn_Rtt_Non_Gprs_Cause_Cause DN05148836 Issue 2-2 Id:0900d805809551ce 237 RTT report descriptions Explanation Traffica Reference Guide for SGSN Direct Interface This field contains internal error cause code of SGSN which is set when MS tries combined procedure which means that SGSN_CAUSE_PROC has one of the following values: COMB_ATTACH_C, INTER_SG_RA_W_IMSI_C, INTRA_PAPU_RA_IMSI_C, INTER_PAPU_RA_IMSI_C, INTRA_PAPU_COMB_UPD_C, INTER_PAPU_COMB_UPD_C, INTER_SGSN_COMB_UPD_C, PERIODIC_COMB_UPD_C If SGSN_CAUSE_PROC is not one of the above this field value must be ignored. Possible values See Sgsn_Rtt_Cause_Cause Field exists in the database Non_Gprs_Cause_Cause Table 77 Sgsn_Rtt_Non_Gprs_Cause_Cause (Cont.) Field name Sgsn_Rtt_Papu_Capa Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the subscriber capacity of particular PAPU in SGSN. Possible values 0x41 = maximum of 65 000 attached subscribers 0x64 = maximum of 100 000 attached subscribers 0xFA = maximum of 250 000 attached subscribers 0xFD = maximum of 500 000 attached subscribers Field exists in the database Table 78 Papu_Capa Sgsn_Rtt_Papu_Capa Field name Sgsn_Rtt_Papu_Group_Id Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains PAPU group id. Possible values 0-255 This field is always 0 if feature, Large RA Support is not activated. Value 0 means that PAPU does not belong to any group. Field exists in the database Table 79 238 Papu_Group_Id Sgsn_Rtt_Papu_Group_Id Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Rtt_Papu_Id Datatype in IDS UINT8 SGSN version >=SG3 Explanation Logical PAPU id. The logical PAPU id follows working PAPU in switchover. This means that the same logical PAPU id always refers to the same geographical area. Possible values 0x0-0xFF The value 0x23 is used for SMSS (SMSS do not go through PAPU). The value 0x28 is used if the physical PAPU id cannot be solved due to some internal error. Field exists in the database Table 80 Papu_Id Sgsn_Rtt_Papu_Id Field name Sgsn_Rtt_Physical_Papu_Id Datatype in IDS UINT8 SGSN version >=SG3 Explanation This field contains the physical index of PAPU. Possible values 0x0-0xFF The value 0x23 is used for SMSS (SMSS do not go through PAPU). The value 0x28 is used if the physical PAPU id cannot be solved due to some internal error. Field exists in the database Table 81 Physical_Papu_Id Sgsn_Rtt_Physical_Papu_Id Field name Sgsn_Rtt_Pdp_Context_Type Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the pdp context type. Possible values Field exists in the database Table 82 Pdp_Context_Type Sgsn_Rtt_Pdp_Context_Type Field name Sgsn_Rtt_Ps_External_Cause Datatype in IDS UINT8 SGSN version >=SG4 Table 83 Sgsn_Rtt_Ps_External_Cause DN05148836 Issue 2-2 Id:0900d805809551ce 239 RTT report descriptions Explanation Traffica Reference Guide for SGSN Direct Interface This field contains external PS (Packet Service) cause value sent to MS if the message that is sent to MS and Sgsn_Rtt_Cause_Proc combination is one of the following: MESSAGE TOWARDS MS: attach accept/reject detach req routing area update accept/reject activate PDP context accept/reject deactivate PDP context req modify PDP context accept/reject SGSN_CAUSE_PROC: GPRS_ATTACH_C/ COMB_ATTACH_C NWR_GPRS_DETACH_C/ NWR_COMB_DETACH_C/ NWR_IMSI_DETACH_C/ INTRA_PAPU_RA_UPD_C/ INTER_PAPU_RA_UPD_C/ INTER_SGSN_RA_UPD_C/ PERIODIC_RA_UPD_C/ INTER_SG_RA_W_IMSI_C/ INTRA_PAPU_RA_IMSI_C/ INTER_PAPU_RA_IMSI_C/ INTRA_PAPU_COMB_UPD_C/ INTER_PAPU_COMB_UPD_C/ INTER_SGSN_COMB_UPD_C/PERIODIC_COMB_UPD_C MO_ACTIVATION_C NWR_DEACTIVATION_C SG_PROC_T_MODIFY_SERVICE_C If Sgsn_Cause_Proc is not any of the values in table above Sgsn_PS_External_Cause is set to value 0xFF. External PS cause towards MS is mapped from SGSN’s internal cause code Sgsn_Rtt_Cause_Cause. External PS cause values towards MS are described in 3GPP TS 24.008. For mapping between external (GSM standard) and internal error causes see appendix SG3/SG4 INTERNAL CAUSE TO INTERFACE CAUSE MAPPING FROM MM & SM PROCESSES. Table 83 240 Sgsn_Rtt_Ps_External_Cause (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions 0x00= Success 0xFF= Undefined 0x02= IMSI unknown in HLR This cause is sent to the MS if the MS is not known (registered) in the HLR. This cause code does not affect the operation of the GPRS service, although it may be used by a GMM procedure. 0x03= Illegal MS This cause is sent to the MS when the network refuses service to the MS either because an identity of the MS is not acceptable to the network or because the MS does not pass the authentication check, this means that the SRES received from the MS is different from that generated by the network. 0x04= IMSI unknown in VLR This cause is sent to the MS when the given IMSI is not known at the VLR. 0x05= IMEI not accepted This cause is sent to the MS if the network does not accept emergency call establishment using an IMEI. 0x06= Illegal ME This cause is sent to the MS if the ME used is not acceptable to the network, if it is, for example, blacklisted. 0x07= GPRS service not allowed This cause is sent to the MS if it requests a combined IMSI attach for GPRS and non-GPRS services, but is not allowed to operate either of them. 0x08= GPRS/non-GPRS serv not allowed / oper deter barring This cause is sent to the MS when the network cannot derive the MS's identity from the P-TMSI in case of inter-SGSN routing area update. 0x09= MS identity unknown This cause is sent to the MS either if the network has implicitly detached the MS, for example some time after the Mobile reachable timer has expired, or if the GMM context data related to the subscription does not exist in the SGSN, for example because of an SGSN restart. 0x0A= Implicitly detached 0x0B= PLMN not allowed This cause is sent to the MS if it requests location updating in a PLMN where the MS, by subscription or due to operator determined barring is not allowed to operate. 0x0C= LA not allowed This cause is sent to the MS if it requests location updating in a location area where the MS, by subscription, is not allowed to operate. 0x0D= LA roaming error This cause is sent to an MS which requests location updating in a location area of a PLMN which offers roaming to that MS in that Location Area, by subscription. 0x0E= GPRS serv not allwd in PLMN This cause is sent to the MS which requests GPRS service in a PLMN which does not offer roaming for GPRS services to that MS. 0x0F= No suitable cells in LA 0x10= MSC not reachable DN05148836 Issue 2-2 Id:0900d805809551ce 241 RTT report descriptions Possible values (continued) Traffica Reference Guide for SGSN Direct Interface This cause is sent to the MS if it requests a combined GPRS attach or routing are updating in a PLMN where the MSC is temporarily not reachable via the GPRS part of the GSM network. 0x11= Network failure This cause is sent to the MS if the MSC cannot service an MS generated request because of PLMN failures, for example problems in MAP. 0x14= MAC failure 0x15= Synch failure 0x16= Congestion This cause is sent if the service request cannot be sent because of congestion (for example, no channel, facility busy/congested etc.) 0x28= No PDP context activated 0x19= LLC or SNDCP failure This cause code is used by the MS to indicate that a PDP context is deactivated because of a LLC or SNDCP failure (for example, if the SM receives a SNSM-STATUS.request message with cause DM received or invalid XID response, see GSM 04.65 [78]) 0x1A= Insufficient resources This cause code is used by the MS or by the network to indicate that a PDP context activation request, secondary PDP context activation request or PDP context modification request cannot be accepted due to insufficient resources. 0x1B= Missing or unknown APN This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because the access point name was not included, although required, or if the access point name could not be resolved. 0x1C= Unknown PDP address or type This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because the PDP address or type could not be recognised. 0x1D= User auth failed This cause code is used by the network to indicate that the requested service was rejected by the external packet data network due to a failed user authentication. 0x1E= Activation rejected by GGSN This cause code is used by the network to indicate that the requested service was rejected by the GGSN. 0x1F= Activation rejected, unspecified This cause code is used by the network to indicate that the requested service was rejected due to unspecified reasons. 0x20= Service option not supported This cause code is used by the network when the MS requests a service which is not supported by the PLMN. 0x21= Requested service option not subscribed This cause is sent when the MS requests a service option for which it has no subscription. 0x22= Service option temporarily out of order Table 83 242 Sgsn_Rtt_Ps_External_Cause (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Possible values (continued) RTT report descriptions This cause is sent when the MSC cannot service the request because of temporary outage of one or more functions required for supporting the service. 0x23= NSAPI already used This cause code may be used by a network to indicate that the NSAPI requested by the MS in the PDP context activation request is already used by another active PDP context of this MS. 0x24= Regular PDP context deactivation This cause code is used to indicate a regular MS or network initiated PDP context deactivation. 0x25= QoS not accepted This cause code is used by the MS if the new QoS, that were indicated by the network in the PDP Context Modification procedure, cannot be accepted. 0x26= Network failure This cause code is used by the network to indicate that the PDP context deactivation is caused by an error situation in the network. 0x27= Reactivation requested This cause code is used by the network to request a PDP context reactivation after a GGSN restart. 0x28= Feature not supported This cause code is used by the MS to indicate that the PDP context activation initiated by the network is not supported by the MS. 0x29= Semantic error in TFT operation This cause code is used by the network to indicate that the there is a semantic error in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification. 0x2A= Syntactical error in TFT operation This cause code is used by the network to indicate that there is a syntactical error in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification. 0x2B= unknown PDP context This cause code is used by the network to indicate that the PDP context identified by the Linked TI IE the secondary PDP context activation request is not active. 0x2C= Semantic errors in packet filter(s) This cause code is used by the network to indicate that there is one or more semantic errors in the packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification. 0x2D= Syntactical error in packet filter(s) This cause code is used by the network to indicate that there is one or more syntactical errors in the packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification. 0x2E= PDP context without TFT already activated This cause code is used by the network to indicate that the network has already activated a PDP context without TFT. 0x51= Invalid transaction identifier value 0x5F= Semantically incorrect message DN05148836 Issue 2-2 Id:0900d805809551ce 243 ) Field name Sgsn_Rtt_Report_Id Datatype in IDS UINT16 SGSN version >=SG3 Explanation Contains information on the report type. 0x63= Information element non-existent or not implemented This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause. 0x6F= Protocol error. the information element is not required to be presented in the message in order for the equipment sending the cause to process the message. Possible values 0x201-0x202 Field exists in the database Report_Id Table 84 Sgsn_Rtt_Report_Id Field name Sgsn_Rtt_Report_Length Datatype in IDS UINT16 Table 85 244 Sgsn_Rtt_Report_Length Id:0900d805809551ce DN05148836 Issue 2-2 . NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field. 0x64= Conditional IE error This cause indicates that the equipment sending this cause has received a message with conditional IE errors. 0x65= Message not compatible with protocol state This cause indicates that a message has been received which is incompatible with the protocol state or that a STATUS message has been received indicating an incompatible call state. However. Field exists in the database Table 83 Ps_External_Cause Sgsn_Rtt_Ps_External_Cause (Cont.RTT report descriptions Possible values (continued) Traffica Reference Guide for SGSN Direct Interface This cause is used to report receipt of a message with semantically incorrect contents. 0x61= Message type non-existent or not implemented 0x62= Message not compatible with protocol state This cause indicates that the equipment sending this cause has received a message not compatible with the protocol state. 0x60= Invalid mandatory information This cause indicates that the equipment sending this cause has received a message with a non-semantic mandatory IE error. unspecified This cause is used for reporting a protocol error event only when no other cause in the protocol error class applies. because the possible values can and will change in the future. This field is needed because empty cells are dropped from rtt_table. Sgsn_Rtt_Report_Time and Sgsn_Rtt_Report_Date are in column Report_Time as SQL TIMESTAMP format Table 88 Sgsn_Rtt_Report_Date Field name Table 89 Sgsn_Rtt_Req_Qos_Ms_Cont_Prof_Flag Sgsn_Rtt_Req_Qos_Ms_Cont_Prof_Flag DN05148836 Issue 2-2 Id:0900d805809551ce 245 . Possible values 0x0-0xFFFFFFFF Field exists in the database Report_Count Table 86 Sgsn_Rtt_Report_Count Field name Sgsn_Rtt_Report_Time Datatype in IDS BCDTIME SGSN version >=SG3 Explanation The time when the report was sent to Traffica Possible values 0x0-0xFFFFFFFF Field exists in the database Yes.m. Possible values 0x0 . Possible values 0x0-0xFFFFFFFF Field exists in the database Yes.) Field name Sgsn_Rtt_Report_Count Datatype in IDS UINT32 SGSN version >=SG3 Explanation Contains information on how many reports of this type have been send to Traffica The value of the counter is reset every day at 00:00 a. Sgsn_Rtt_Report_Time and Sgsn_Rtt_Report_Date are in column Report_Time as SQL TIMESTAMP format Table 87 Sgsn_Rtt_Report_Time Field name Sgsn_Rtt_Report_Date Datatype in IDS BCDDATE SGSN version >=SG3 Explanation The date when the report was sent to Traffica.0xFFFF Field exists in the database Report_Length Table 85 Sgsn_Rtt_Report_Length (Cont.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions SGSN version >=SG3 Explanation This field contains the length of report in bytes. DEFAULT Field exists in the database Table 91 Req_Qos_Precedence Sgsn_Rtt_Req_Qos_Delay_Class Field name Sgsn_Rtt_Req_Qos_Reliability_Class Datatype in IDS UINT8 SGSN version >=SG4 Table 92 246 Sgsn_Rtt_Req_Qos_Reliability_Class Id:0900d805809551ce DN05148836 Issue 2-2 .) Field name Sgsn_Rtt_Req_Qos_Precedence Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests. Possible values 0x0 = Release 97/98 0x1 = Release 99 0x2 = Release 5 0x4 = Release 7 Field exists in the database Table 89 Req_Qos_Ms_Cont_Prof_Flag Sgsn_Rtt_Req_Qos_Ms_Cont_Prof_Flag (Cont.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests. DEFAULT 0x3 = low priority Field exists in the database Table 90 Req_Qos_Precedence Sgsn_Rtt_Req_Qos_Precedence Field name Sgsn_Rtt_Req_Qos_Delay_Class Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests. Possible values 0x0 = subscribed delay class requested 0x1 = delay class 1 0x2 = delay class 2 0x3 = delay class 3 0x4 = delay class 4 (best effort). Possible values 0x0 = subscribed precedence class requested 0x1 = high priority 0x2 = normal priority. Unprotected Field exists in the database Table 92 Req_Qos_Reliability_Class Sgsn_Rtt_Req_Qos_Reliability_Class (Cont.11 kbit/s) 0xD = 500000 to 1000000 octet/h (~2.4 kbit/s) 0xF = 2000000 to 5000000 octet/h (~11.Traffica Reference Guide for SGSN Direct Interface Explanation Field of Quality of Service that the user requests. Protected.) Field name Sgsn_Rtt_Req_Qos_Mean_Throughput Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests. acknowledged LLC and RLC. acknowledged RLC.44 kbit/s) 0xC = 200000 to 500000 octet/h (~1.2 kbit/s) 0xE = 1000000 to 2000000 octet/h (~4.44 bit/s) 0x3 = 200 to 500 octet/h (~1. Possible values 0x0 = subscribed mean throughput requested 0x1F = best effort 0x1 = up to 100 octet/h (~0. Possible values 0x0 = subscribed reliability class requested RTT report descriptions 0x1 = acknowledged GTP. Protected 0x4 = unacknowledged GTP.22 kbit/s) 0xB = 100000 to 200000 octet/h (~0. DEFAULT 0x3 = unacknowledged GTP. LLC and RLC.11 bit/s) 0x4 = 500 to 1000 octet/h (~2. Protected 0x5 = unacknowledged GTP. LLC. Protected 0x2 = unacknowledged GTP. LLC and RLC. LLC and RLC.1 bit/s) 0x7 = 5000 to 10000 octet/h (~22 bit/s) 0x8 = 10000 to 20000 octet/h (~44 bit/s) 0x9 = 20000 to 50000 octet/h (~111 bit/s) 0xA = 50000 to 100000 octet/h (~0.2 bit/s) 0x5 = 1000 to 2000 octet/h (~4.4 bit/s) 0x6 = 2000 to 5000 octet/h (~11.1 kbit/s) 0x10 = 5000000 to 10000000 octet/h (~22 kbit/s) 0x11 = 10000000 to 20000000 octet/h (~44 kbit/s) 0x12 = 20000000 to 50000000 octet/h (~111 kbit/s) Field exists in the database Table 93 Sgsn_Rtt_Req_Qos_Mean_Throughput Field name Table 94 Req_Qos_Mean_Throughput Sgsn_Rtt_Req_Qos_Peak_Throughput Sgsn_Rtt_Req_Qos_Peak_Throughput DN05148836 Issue 2-2 Id:0900d805809551ce 247 . DEFAULT 0x2 = 100 to 200 octet/h (~0.22 bit/s). Do not pay attention to this field's value if release 97/98 is in use. Table 96 248 Sgsn_Rtt_Req_Qos_Delivery_Order Id:0900d805809551ce DN05148836 Issue 2-2 .) Field name Sgsn_Rtt_Req_Qos_Delivery_Erroneous Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests. Field exists in the database Table 95 Delivery_Erroneous Sgsn_Rtt_Req_Qos_Delivery_Erroneous Field name Sgsn_Rtt_Req_Qos_Delivery_Order Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests. Possible values 0x0 = subscribed peak throughput requested 0x1 = up to 1000 octet/s 0x2 = 1000 to 2000 octet/s 0x3 = 2000 to 4000 octet/s 0x4 = 4000 to 8000 octet/s 0x5 = 8000 to 16000 octet/s 0x6 = 16000 to 32000 octet/s 0x7 = 32000 to 64000 octet/s 0x8 = 64000 to 128000 octet/s 0x9 = 128000 to 256000 octet/s. DEFAULT 0x2 = Without delivery order (“no”) NOTE: This field is in use only with QoS Release 99.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests. DEFAULT Field exists in the database Table 94 Req_Qos_Peak_Throughput Sgsn_Rtt_Req_Qos_Peak_Throughput (Cont. Do not pay attention to this field's value if release 97/98 is in use. Possible values 0x0 = Subscribed delivery of erroneous SDUs requested 0x1 = no detect (“-”)' 0x2 = Erroneous SDUs are delivered (“yes”) 0x3 = Erroneous SDUs are not delivered (“no”). DEFAULT NOTE: This field is in use only with QoS Release 99. Possible values 0x0 = Subscribed delivery order requested 0x1 = With delivery order (“yes”). Possible values 0x0 = Subscribed maximum SDU size requested 0x96 = Upper limit of max SDU size (1500 octets).Traffica Reference Guide for SGSN Direct Interface Field exists in the database Table 96 RTT report descriptions Delivery_Order Sgsn_Rtt_Req_Qos_Delivery_Order (Cont.) Field name Sgsn_Rtt_Req_Qos_Traffic_Class Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests. DEFAULT NOTE: This field is in use only with QoS Release 99. Field exists in the database Table 98 Req_Qos_Max_Sdu_Size Sgsn_Rtt_Req_Qos_Max_Sdu_Size Field name Sgsn_Rtt_Req_Qos_Max_Bit_Rate_For_Ul Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests. Do not pay attention to this field's value if release 97/98 is in use. Field exists in the database Table 97 Req_Qos_Traffic_Class Sgsn_Rtt_Req_Qos_Traffic_Class Field name Sgsn_Rtt_Req_Qos_Max_Sdu_Size Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests. Possible values 0x0 = Subscribed traffic class requested 0x1 = Conversational class 0x2 = Streaming class 0x3 = Interactive class. DEFAULT 0x4 = Background class NOTE: This field is in use only with QoS Release 99. Table 99 Sgsn_Rtt_Req_Qos_Max_Bit_Rate_For_Ul DN05148836 Issue 2-2 Id:0900d805809551ce 249 . Do not pay attention to this field's value if release 97/98 is in use. Bit rate value calculations should be started from extended fields. value is set as ‘11111110’. using a granularity of 1 kbps giving a range of values from 1 kbps to 63 kbps in 1 kbps increments. ‘11111111’: 0kbps If Maximum bit rate is higher than 8640 kbps. NOTE: This field is in use only with QoS Release 99 or newer. In MS to network direction: ‘00000000’: MS request subscribed maximum bit rate. 8640 kbps and shall encode the value to Sgsn_Rtt_Req_Qos_Ext_Max_Br_Ul.e.5. If the extended fields have a '0'. ‘01000000’-‘01111111’: The maximum bit rate is 64 kbps + ((the binary coded value in 8 bits –01000000) * 8 kbps) giving a range of values from 64 kbps to 568 kbps in 8 kbps increments. Table 100 250 Sgsn_Rtt_Req_Qos_Max_Bit_Rate_For_Dl Id:0900d805809551ce DN05148836 Issue 2-2 . ignore the value and use values from the nonextended fields. In MS to network direction and in network to MS direction: ‘00000001’-‘00111111’: The maximum bit rate is binary coded in 8 bits. Do not pay attention to this field's value if release 97/98 is in use. ‘10000000’-‘11111110’: The maximum bit rate is 576 kbps + ((the binary coded value in 8 bits –10000000) * 64 kbps) giving a range of values from 576 kbps to 8640 kbps in 64 kbps increments. i.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface Values are specified in 3GPP 24.008 in chapter 10. Field exists in the database Table 99 Req_Qos_Max_Bit_Rate_For_Ul Sgsn_Rtt_Req_Qos_Max_Bit_Rate_For_Ul (Cont.) Field name Sgsn_Rtt_Req_Qos_Max_Bit_Rate_For_Dl Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests.5.6. value 1*10^-5 0x6 = SDU error ratio. value 1*10^-4 0x5 = SDU error_ratio. value 1*10^-6. If the extended fields have a '0'. ‘01000000’-‘01111111’: The maximum bit rate is 64 kbps + ((the binary coded value in 8 bits –01000000) * 8 kbps) giving a range of values from 64 kbps to 568 kbps in 8 kbps increments.6. value 1*10^-2 0x2 = SDU error ratio.5. Field exists in the database Table 100 Req_Qos_Max_Bit_Rate_For_Dl Sgsn_Rtt_Req_Qos_Max_Bit_Rate_For_Dl (Cont. i. using a granularity of 1 kbps giving a range of values from 1 kbps to 63 kbps in 1 kbps increments. Do not pay attention to this field's value if release 97/98 is in use. Possible values 0x0 = Subscribed SDU error ratio requested 0x1 = SDU error ratio.e. Table 101 Sgsn_Rtt_Req_Qos_Sdu_Error_Ratio DN05148836 Issue 2-2 Id:0900d805809551ce 251 . ignore the value and use values from the nonextended fields. DEFAULT 0x7 = SDU error ratio. value is set as ‘11111110’. 8640 kbps and shall encode the value to Sgsn_Rtt_Req_Qos_Ext_Max_Br_Dl.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions Values are specified in 3GPP 24. In MS to network direction and in network to MS direction: ‘00000001’-‘00111111’: The maximum bit rate is binary coded in 8 bits. value 1*10^-3 0x4 = SDU error ratio. ‘11111111’: 0kbps If Maximum bit rate is higher than 8640 kbps. Bit rate value calculations should be started from extended fields. NOTE: This field is in use only with QoS Release 99 or newer.5.008 in chapter 10. value 1*10^-1 NOTE: This field is in use only with QoS Release 99. ‘10000000’-‘11111110’: The maximum bit rate is 576 kbps + ((the binary coded value in 8 bits –10000000) * 64 kbps) giving a range of values from 576 kbps to 8640 kbps in 64 kbps increments. Do not pay attention to this field's value if release 97/98 is in use. In MS to network direction: ‘00000000’: MS request subscribed maximum bit rate. value 7*10^-3 0x3 = SDU error ratio.) Field name Sgsn_Rtt_Req_Qos_Sdu_Error_Ratio Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests. DEFAULT 0x8 = Residual BER. DEFAULT 0x2 = Traffic handling priority. level 1. value 1*10^-3 0x6 = Residual BER. value 4*10^-3 0x5 = Residual BER. Possible values 0x0 = Subscribed traffic handling priority requested 0x1 = Traffic handling priority. value 1*10^-2 0x3 = Residual BER. level 3 NOTE: This field is in use only with QoS Release 99. value 1*10^-8 NOTE: This field is in use only with QoS Release 99. Do not pay attention to this field's value if release 97/98 is in use. value 1*10^-4 0x7 = Residual BER. Field exists in the database Table 103 Req_Qos_Traff_Handling_Prio Sgsn_Rtt_Req_Qos_Traff_Handling_Prio Field name Sgsn_Rtt_Req_Qos_Transfer_Delay Datatype in IDS UINT8 Table 104 252 Sgsn_Rtt_Req_Qos_Transfer_Delay Id:0900d805809551ce DN05148836 Issue 2-2 . value 1*10^-5. Do not pay attention to this field's value if release 97/98 is in use. Field exists in the database Table 102 Req_Qos_Residual_Ber Sgsn_Rtt_Req_Qos_Residual_Ber Field name Sgsn_Rtt_Req_Qos_Traff_Handling_Prio Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests. value 1*10^-6 0x9 = Residual BER. level 2 0x3 = Traffic handling priority. value 5*10^-3 0x4 = Residual BER.RTT report descriptions Field exists in the database Table 101 Traffica Reference Guide for SGSN Direct Interface Req_Qos_Sdu_Error_Ratio Sgsn_Rtt_Req_Qos_Sdu_Error_Ratio (Cont. value 5*10^-2 0x2 = Residual BER. Possible values 0x0 = Subscribed residual BER requested 0x1 = Residual BER.) Field name Sgsn_Rtt_Req_Qos_Residual_Ber Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests. 5. Possible values 0x0 . Possible values Values are specified in 3GPP 24. value is set as ‘11111110’. Do not pay attention to this field's value if release 97/98 is in use. In MS to network direction: ‘00000000’: MS request subscribed maximum bit rate.e. ‘10000000’-‘11111110’: The maximum bit rate is 576 kbps + ((the binary coded value in 8 bits –10000000) * 64 kbps) giving a range of values from 576 kbps to 8640 kbps in 64 kbps increments.008 in chapter 10. using a granularity of 1 kbps giving a range of values from 1 kbps to 63 kbps in 1 kbps increments.Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG4 Explanation Field of Quality of Service that the user requests.5. In MS to network direction and in network to MS direction: ‘00000001’-‘00111111’: The maximum bit rate is binary coded in 8 bits. ‘01000000’-‘01111111’: The maximum bit rate is 64 kbps + ((the binary coded value in 8 bits –01000000) * 8 kbps) giving a range of values from 64 kbps to 568 kbps in 8 kbps increments. Field exists in the database Table 104 Req_Qos_Transfer_Delay Sgsn_Rtt_Req_Qos_Transfer_Delay (Cont. NOTE: This field is in use only with QoS Release 99 or newer.6. 8640 kbps and shall encode the value to Sgsn_Rtt_Req_Qos_Ext_Guar_Br_Ul. Bit rate value calculations should be started from extended fields. Do not pay attention to this field's value if release 97/98 is in use. ‘11111111’: 0kbps If Maximum bit rate is higher than 8640 kbps. ignore the value and use values from the nonextended fields.) Field name Sgsn_Rtt_Req_Qos_Guaran_Bit_Rate_Ul Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests. If the extended fields have a '0'. i.0xFF RTT report descriptions NOTE: This field is in use only with QoS Release 99. Field exists in the database Table 105 Sgsn_Rtt_Req_Qos_Guaran_Bit_Rate_Ul Field name Table 106 Req_Qos_Guaran_Bit_Rate_Ul Sgsn_Rtt_Req_Qos_Guaran_Bit_Rate_Dl Sgsn_Rtt_Req_Qos_Guaran_Bit_Rate_Dl DN05148836 Issue 2-2 Id:0900d805809551ce 253 . Allocation/retention priority Possible values 0x0 . using a granularity of 1 kbps giving a range of values from 1 kbps to 63 kbps in 1 kbps increments.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests.5. Bit rate value calculations should be started from extended fields. ‘11111111’: 0kbps If Maximum bit rate is higher than 8640 kbps. Field exists in the database Table 106 Req_Qos_Guaran_Bit_Rate_Dl Sgsn_Rtt_Req_Qos_Guaran_Bit_Rate_Dl (Cont. Field exists in the database Table 107 254 Req_Qos_Alloc_Retention Sgsn_Rtt_Req_Qos_Alloc_Retention Id:0900d805809551ce DN05148836 Issue 2-2 .5. Do not pay attention to this field's value if release 97/98 is in use.6. value is set as ‘11111110’. In MS to network direction: ‘00000000’: MS request subscribed maximum bit rate.e.) Field name Sgsn_Rtt_Req_Qos_Alloc_Retention Datatype in IDS UINT8 SGSN version >=SG4 Explanation Field of Quality of Service that the user requests. Possible values Values are specified in 3GPP 24.008 in chapter 10. In MS to network direction and in network to MS direction: ‘00000001’-‘00111111’: The maximum bit rate is binary coded in 8 bits. ignore the value and use values from the nonextended fields. ‘01000000’-‘01111111’: The maximum bit rate is 64 kbps + ((the binary coded value in 8 bits –01000000) * 8 kbps) giving a range of values from 64 kbps to 568 kbps in 8 kbps increments. 8640 kbps and shall encode the value to Sgsn_Rtt_Req_Qos_Ext_Guar_Br_Dl.0xFF NOTE: This field is in use only with QoS Release 99. If the extended fields have a '0'. i. Do not pay attention to this field's value if release 97/98 is in use. ‘10000000’-‘11111110’: The maximum bit rate is 576 kbps + ((the binary coded value in 8 bits –10000000) * 64 kbps) giving a range of values from 576 kbps to 8640 kbps in 64 kbps increments. NOTE: his field is in use only with QoS Release 99 or newer. Possible values Field exists in the database Table 109 Secf_Auth_End_Date Sgsn_Rtt_Secf_Auth_End_Date Field name Sgsn_Rtt_Secf_Auth_End_Time Datatype in IDS BCDTIME SGSN version >=SG6 Explanation The time when authentication was completed. Sgsn Secf_auth_end_time field does not contain valid information either. Time is in format hundredsofseconds:seconds:minutes:hours. 0x00000000 = authentication has no end date.0x1 Field exists in the database Roaming_Status Table 108 Sgsn_Rtt_Roaming_Status Field name Sgsn_Rtt_Secf_Auth_End_Date Datatype in IDS BCDDATE SGSN version >=SG6 Explanation The date when authentication was completed. Possible values Field exists in the database Table 110 Secf_Auth_End_Time Sgsn_Rtt_Secf_Auth_End_Time Field name Sgsn_Rtt_Secf_Auth_Start_Date Datatype in IDS BCDDATE SGSN version >=SG6 Table 111 Sgsn_Rtt_Secf_Auth_Start_Date DN05148836 Issue 2-2 Id:0900d805809551ce 255 . This field does not contain valid information if Sgsn_Secf_auth_end_date is 0. Possible values 0x0 .Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Rtt_Roaming_Status Datatype in IDS UINT8 SGSN version >=SG4 Explanation If this field value is something other than zero. attached subscriber is roaming from VPLMN. Date is in format day:month:year. Possible values Field exists in the database Table 111 Secf_Auth_Start_Date Sgsn_Rtt_Secf_Auth_Start_Date (Cont.RTT report descriptions Explanation Traffica Reference Guide for SGSN Direct Interface The date when authentication was started.0x1 Field exists in the database Secf_Authentication_Done Table 113 Sgsn_Rtt_Secf_Authentication_Done Field name Sgsn_Rtt_Secf_Ptmsi_Reallocated Datatype in IDS UINT8 SGSN version >=SG4 Explanation If this field value is non-zero.0x1 Field exists in the database Secf_Ptmsi_Reallocated Table 114 256 Sgsn_Rtt_Secf_Ptmsi_Reallocated Id:0900d805809551ce DN05148836 Issue 2-2 . Sgsn Secf_auth_start_time field does not contain valid information either. Date is in format day:month:year. Possible values Field exists in the database Table 112 Secf_Auth_Start_Time Sgsn_Rtt_Secf_Auth_Start_Time Field name Sgsn_Rtt_Secf_Authentication_Done Datatype in IDS UINT8 SGSN version >=SG4 Explanation If this field’s value is something other than zero. 0x00000000 = authentication has no start date. This field does not contain valid information if Sgsn_Secf_auth_start_date is 0. Possible values 0x0 .) Field name Sgsn_Rtt_Secf_Auth_Start_Time Datatype in IDS BCDTIME SGSN version >=SG6 Explanation The time when authentication was started. Time is in format hundredsofseconds:seconds:minutes:hours. the authentication security function has been performed before the main GMM/SM procedure. ptmsi_reallocated function has been performed in the main GMM/SM procedure. Possible values 0x0 . Time is in format hundredsofseconds:seconds:minutes:hours. Date is in format day:month:year. This field does not contain valid information if Sgsn_Secf_imei_chk_end_date is 0. 0x00000000 = identity check has no end date.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Rtt_Secf_Ptmsi_Sign_Realloc Datatype in IDS UINT8 SGSN version >=SG4 Explanation If this field value is non-zero. Possible values Field exists in the database Table 117 Secf_Imei_Chk_End_Time Sgsn_Rtt_Secf_Imei_Chk_End_Time Field name Sgsn_Rtt_Secf_Imei_Chk_Start_Date Datatype in IDS BCDDATE SGSN version >=SG6 Table 118 Sgsn_Rtt_Secf_Imei_Chk_Start_Date DN05148836 Issue 2-2 Id:0900d805809551ce 257 . Sgsn Secf_imei_chk_end_time field does not contain valid information either. Possible values Field exists in the database Table 116 Secf_Imei_Chk_End_Date Sgsn_Rtt_Secf_Imei_Chk_End_Date Field name Sgsn_Rtt_Secf_Imei_Chk_End_Time Datatype in IDS BCDTIME SGSN version >=SG6 Explanation The time when identity check was completed.0x1 Field exists in the database Secf_Ptmsi_Sign_Realloc Table 115 Sgsn_Rtt_Secf_Ptmsi_Sign_Realloc Field name Sgsn_Rtt_Secf_Imei_Chk_End_Date Datatype in IDS BCDDATE SGSN version >=SG6 Explanation The date when identity check was completed. ptmsi_sign_realloc function has been performed in the main GMM/SM procedure Possible values 0x0 . Date is in format day:month:year. Sgsn imei_chk_start_time field does not contain valid information either. This field does not contain valid information if Sgsn_imei_chk_start_date is 0. Possible values Field exists in the database Table 119 Secf_Imei_Chk_Start_Time Sgsn_Rtt_Secf_Imei_Chk_Start_Time Field name Sgsn_Rtt_Secf_Imei_Checked Datatype in IDS UINT8 SGSN version >=SG4 Explanation If this field’s value is something other than zero. 0x00000000 = identity check has no start date. Time is in format hundredsofseconds:seconds:minutes:hours. Possible values Field exists in the database Table 118 Secf_Imei_Chk_Start_Date Sgsn_Rtt_Secf_Imei_Chk_Start_Date (Cont.) Field name Sgsn_Rtt_Secf_Imei_Chk_Start_Time Datatype in IDS BCDTIME SGSN version >=SG6 Explanation The time when identity check was started. Table 121 258 Sgsn_Rtt_Secf_Ciph_Algorithm Id:0900d805809551ce DN05148836 Issue 2-2 . the ciph_algorithm function has been performed before the main GMM/SM procedure.RTT report descriptions Explanation Traffica Reference Guide for SGSN Direct Interface The date when identity check was started.0x1 Field exists in the database Secf_Imei_Checked Table 120 Sgsn_Rtt_Secf_Imei_Checked Field name Sgsn_Rtt_Secf_Ciph_Algorithm Datatype in IDS UINT8 SGSN version >=SG4 Explanation If this field value is something other than zero. Possible values 0x0 . the imei_checked function has been performed in the main GMM/SM procedure. Possible values Field exists in the database Table 122 Tunnel_Id Sgsn_Rtt_Tunnel_Id Field name Sgsn_Rtt_Whole_Data_Amount_Down Datatype in IDS UINT32 SGSN version >=SG4 Explanation Data amount in bytes. This field contains user uplink data during whole pdp context lifetime.0xFFFFFFFF Field exists in the database Whole_Data_Amount_Up Table 124 Sgsn_Rtt_Whole_Data_Amount_Up DN05148836 Issue 2-2 Id:0900d805809551ce 259 . Possible values 0x00 . Possible values 0x00 .0xFFFFFFFF Field exists in the database Whole_Data_Amount_Down Table 123 Sgsn_Rtt_Whole_Data_Amount_Down Field name Sgsn_Rtt_Whole_Data_Amount_Up Datatype in IDS UINT32 SGSN version >=SG4 Explanation Data amount in bytes.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions 0x0 = no_ciph 0x1 = gea_1 0x2 = gea_2 0x3 = gea_3 0x4 = gea_4 0x5 = gea_5 0x6 = gea_6 0x7 = gea_7 Field exists in the database Table 121 Secf_Ciph_Algorithm Sgsn_Rtt_Secf_Ciph_Algorithm (Cont. This field contains user downlink data during whole pdp context lifetime. This field is filled only in pdp context deactivation. In other events this field is set to value zero. In other events this field is set to value zero.) Field name Sgsn_Rtt_Tunnel_Id Datatype in IDS BCD8(8) SGSN version >=SG4 Explanation This field contains GSN end point id for tunnelling. This field is filled only in pdp context deactivation. Possible values 0x0 . This field is filled only in pdp context deactivation. This field contains user uplink data during whole pdp context lifetime.0xFF Field exists in the database Nbr_Add_Length Table 127 Sgsn_Sms_Nbr_Add_Length Field name Sgsn_Sms_Nbr_Indicators Datatype in IDS UINT8:68 SGSN version >=SG3 Table 128 260 Sgsn_Sms_Nbr_Indicators Id:0900d805809551ce DN05148836 Issue 2-2 .0xFFFF FFFF FFFF FFFF Field exists in the database Ext_Whole_Data_Amount_Down Table 125 Sgsn_Rtt_Ext_Whole_Data_Amount_Down Field name Sgsn_Rtt_Ext_Whole_Data_Amount_Up Datatype in IDS UINT64 SGSN version >=SG7 Explanation Data amount in bytes. In other events this field is set to value zero. This field contains user downlink data during whole pdp context lifetime.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Rtt_Ext_Whole_Data_Amount_Down Datatype in IDS UINT64 SGSN version >=SG7 Explanation Data amount in bytes.0xFFFF FFFF FFFF FFFF Field exists in the database Ext_Whole_Data_Amount_Up Table 126 Sgsn_Rtt_Ext_Whole_Data_Amount_Up Field name Sgsn_Sms_Nbr_Add_Length Datatype in IDS UINT8:67 SGSN version >=SG3 Explanation This field contains the length of an address. If RTT is not sent to Traffica because of mobile originated SMS the value is set to 0x0. Possible values 0x00 . Possible values 0x00 . In other events this field is set to value zero. This field is filled only in pdp context deactivation. ) Field name Sgsn_Rtt_Rnc_Address_Mcc Datatype in IDS UINT16 SGSN version >=SG6 Explanation RNC’s country code.164 6 = E. Double_digit has two parts. Possible values This field contains country code. if Mcc is 358 the Sgsn_Cgi_Mcc field is:53 F8 Field exists in the database Rnc_Address_Mcc Table 129 Sgsn_Rtt_Rnc_Address_Mcc Field name Sgsn_Rtt_Rnc_Address_Mnc Datatype in IDS UINT16 SGSN version >=SG6 Table 130 Sgsn_Rtt_Rnc_Address_Mnc DN05148836 Issue 2-2 Id:0900d805809551ce 261 .214 9 = PNP Bits 5-7: Nature of address 0 = unknown 1 = int 2 = nat 3 = nets 4 = subs Bit 8: Extension 1 = no_ext 0 = ext Field exists in the database Table 128 Nbr_Indicators Sgsn_Sms_Nbr_Indicators (Cont.212 7 = E. Possible values Bits 1-4: Numbering plan 0 = Unknown 1 = E. Field contents are:array(2) OF double_digit. For example.Traffica Reference Guide for SGSN Direct Interface Explanation RTT report descriptions This field contains address indicators of addresses used in MAPSgsn_ SMS_Dest_Nbr_Indicators is a packed struct including three parts: • • • nbr_plan na_of_ad ext (0:15) Numbering Plan indicator (0:7) Nature of address indicator (0:1) Extension indicator If RTT is not sent to Traffica because of mobile originated SMS the value is set to 0x0. one double_digit field is of size byte. lower_digit (4bits) and upper_digit (4bits). Mcc is stored in decimal format and the endmark is 0xF. Possible values RNC’s identifier Field exists in the database Rnc_Id Table 131 Sgsn_Rtt_Rnc_Id Field name Sgsn_Rtt_Sai_Mcc Datatype in IDS BCDREV8(2) SGSN version >=SG6 Explanation The country code of the service area Possible values This field contains country code. Field contents are: array(2) OF double_digit. For example.413).RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Explanation This field contains mobile network code Possible values Field contents are:array(2) OF double_digit.For example. one double_digit field is of size byte. lower_digit (4bits) and upper_digit (4bits). Mnc is stored in decimal format and the endmark is 0xF. lower_digit (4bits) and upper_digit (4bits).) Field name Sgsn_Rtt_Rnc_Id Datatype in IDS UINT16 SGSN version >=SG6 Explanation RNC’s identifier. Field exists in the database Sai_Mnc Table 133 262 Sgsn_Rtt_Sai_Mnc Id:0900d805809551ce DN05148836 Issue 2-2 . Mnc is stored in decimal format and the endmark is 0xF. Field exists in the database Rnc_Address_Mnc Table 130 Sgsn_Rtt_Rnc_Address_Mnc (Cont. Double_digit has two parts. Double_digit has two parts. Mcc is stored in decimal format and the endmark is 0xF. For example. Double_digit has two parts. if Mcc is 358 the Sgsn_Cgi_Mcc field is: 53 F8 Field exists in the database Table 132 Sai_Mcc Sgsn_Rtt_Sai_Mcc Field name Sgsn_Rtt_Sai_Mnc Datatype in IDS BCDREV8(2) SGSN version >=SG6 Explanation The mobile network code of the service area Possible values Field contents are:array(2) OF double_digit. one double_digit field is of size byte. one double_digit field is of size byte. (UMTS 25. if Mnc is 400 the Sgsn_Cgi_Mnc field is:04 F0. lower_digit (4bits) and upper_digit (4bits). if Mnc is 400 the Sgsn_Cgi_Mnc field is: 04 F0. UMTS 25. Possible values 0x1 – 0xFFFF Field exists in the database Sai_Lac Table 134 Sgsn_Rtt_Sai_Lac Field name Sgsn_Rtt_Sai_Sac Datatype in IDS UINT16 SGSN version >=SG6 Explanation Service area identity (SAC.401). Possible values 0x0 = GSM 900-P Access Technology Type 0x1 = GSM 900-E Access Technology Type 0x2 = GSM 900-R Access Technology Type 0x3 = GSM 1800 Access Technology Type 0x4 = GSM 1900 Access Technology Type 0x5 = GSM 450 Access Technology Type 0x6 = GSM 480 Access Technology Type 0x7 = GSM 850 Access Technology Type 0xFF = Not used Field exists in the database Table 136 Ra_Cap_Array_0_Acc_Tec_Type Sgsn_Rtt_Ra_Cap_Array_0_Acc_Tec_Type Field name Sgsn_Rtt_Ra_Cap_Array_0_Info Datatype in IDS BCDREV8(8) SGSN version >=SG6 Table 137 Sgsn_Rtt_Ra_Cap_Array_0_Info DN05148836 Issue 2-2 Id:0900d805809551ce 263 . Possible values 0x0 – 0xFFFF Field exists in the database Sai_Sac Table 135 RTT report descriptions Sgsn_Rtt_Sai_Sac Field name Sgsn_Rtt_Ra_Cap_Array_0_Acc_Tec_Type Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains MS Radio access capability arrays technology type.Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Rtt_Sai_Lac Datatype in IDS UINT16 SGSN version >=SG6 Explanation The location area code of the service area. 008 v.1).) Field name Sgsn_Rtt_Ra_Cap_Array_1_Acc_Tec_Type Datatype in IDS UINT8 SGSN version >=SG6 Table 138 264 Sgsn_Rtt_Ra_Cap_Array_1_Acc_Tec_Type Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Explanation This field contains radio access capability information (24.3.4. Possible values This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 137 Ra_Cap_Array_0_Info Sgsn_Rtt_Ra_Cap_Array_0_Info (Cont. Possible values 0x0 = GSM 900-P Access Technology Type 0x1 = GSM 900-E Access Technology Type 0x2 = GSM 900-R Access Technology Type 0x3 = GSM 1800 Access Technology Type 0x4 = GSM 1900 Access Technology Type 0x5 = GSM 450 Access Technology Type 0x6 = GSM 480 Access Technology Type 0x7 = GSM 850 Access Technology Type 0xFF = Not used Field exists in the database Table 138 Ra_Cap_Array_1_Acc_Tec_Type Sgsn_Rtt_Ra_Cap_Array_1_Acc_Tec_Type (Cont.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Explanation This field contains MS Radio access capability arrays technology type.1). Table 139 Sgsn_Rtt_Ra_Cap_Array_1_Info DN05148836 Issue 2-2 Id:0900d805809551ce 265 .008 v.3.4.) Field name Sgsn_Rtt_Ra_Cap_Array_1_Info Datatype in IDS BCDREV8(8) SGSN version >=SG6 Explanation This field contains radio access capability information (24. Table 140 266 Sgsn_Rtt_Ra_Cap_Array_2_Acc_Tec_Type Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 139 Ra_Cap_Array_1_Info Sgsn_Rtt_Ra_Cap_Array_1_Info (Cont.) Field name Sgsn_Rtt_Ra_Cap_Array_2_Acc_Tec_Type Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains MS Radio access capability arrays technology type. 008 v.4.) Field name Sgsn_Rtt_Ra_Cap_Array_2_Info Datatype in IDS BCDREV8(8) SGSN version >=SG6 Explanation This field contains radio access capability information (24. Table 141 Sgsn_Rtt_Ra_Cap_Array_2_Info DN05148836 Issue 2-2 Id:0900d805809551ce 267 .1).3.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions 0x0 = GSM 900-P Access Technology Type 0x1 = GSM 900-E Access Technology Type 0x2 = GSM 900-R Access Technology Type 0x3 = GSM 1800 Access Technology Type 0x4 = GSM 1900 Access Technology Type 0x5 = GSM 450 Access Technology Type 0x6 = GSM 480 Access Technology Type 0x7 = GSM 850 Access Technology Type 0xFF = Not used Field exists in the database Table 140 Ra_Cap_Array_2_Acc_Tec_Type Sgsn_Rtt_Ra_Cap_Array_2_Acc_Tec_Type (Cont. ) Field name Sgsn_Rtt_Ra_Cap_Array_3_Acc_Tec_Type Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains MS Radio access capability arrays technology type.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6 Field exists in the database Table 141 Ra_Cap_Array_2_Info Sgsn_Rtt_Ra_Cap_Array_2_Info (Cont. Table 142 268 Sgsn_Rtt_Ra_Cap_Array_3_Acc_Tec_Type Id:0900d805809551ce DN05148836 Issue 2-2 . 4. Table 143 Sgsn_Rtt_Ra_Cap_Array_3_Info DN05148836 Issue 2-2 Id:0900d805809551ce 269 .1).008 v.3.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions 0x0 = GSM 900-P Access Technology Type 0x1 = GSM 900-E Access Technology Type 0x2 = GSM 900-R Access Technology Type 0x3 = GSM 1800 Access Technology Type 0x4 = GSM 1900 Access Technology Type 0x5 = GSM 450 Access Technology Type 0x6 = GSM 480 Access Technology Type 0x7 = GSM 850 Access Technology Type 0xFF = Not used Field exists in the database Table 142 Ra_Cap_Array_3_Acc_Tec_Type Sgsn_Rtt_Ra_Cap_Array_3_Acc_Tec_Type (Cont.) Field name Sgsn_Rtt_Ra_Cap_Array_3_Info Datatype in IDS BCDREV8(8) SGSN version >=SG6 Explanation This field contains radio access capability information (24. ) Field name Sgsn_Rtt_Ra_Cap_Array_4_Info Datatype in IDS BCDREV8(8) SGSN version >=SG6 Explanation This field contains radio access capability information (24.1).RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 143 Ra_Cap_Array_3_Info Sgsn_Rtt_Ra_Cap_Array_3_Info (Cont. Table 144 270 Sgsn_Rtt_Ra_Cap_Array_4_Info Id:0900d805809551ce DN05148836 Issue 2-2 .008 v.4.3. Table 145 Sgsn_Rtt_Ra_Cap_Array_5_Acc_Tec_Type DN05148836 Issue 2-2 Id:0900d805809551ce 271 .) Field name Sgsn_Rtt_Ra_Cap_Array_5_Acc_Tec_Type Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains MS Radio access capability arrays technology type.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 144 Ra_Cap_Array_4_Info Sgsn_Rtt_Ra_Cap_Array_4_Info (Cont. 1).RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface 0x0 = GSM 900-P Access Technology Type 0x1 = GSM 900-E Access Technology Type 0x2 = GSM 900-R Access Technology Type 0x3 = GSM 1800 Access Technology Type 0x4 = GSM 1900 Access Technology Type 0x5 = GSM 450 Access Technology Type 0x6 = GSM 480 Access Technology Type 0x7 = GSM 850 Access Technology Type 0xFF = Not used Field exists in the database Table 145 Ra_Cap_Array_5_Acc_Tec_Type Sgsn_Rtt_Ra_Cap_Array_5_Acc_Tec_Type (Cont. Table 146 272 Sgsn_Rtt_Ra_Cap_Array_5_Info Id:0900d805809551ce DN05148836 Issue 2-2 .) Field name Sgsn_Rtt_Ra_Cap_Array_5_Info Datatype in IDS BCDREV8(8) SGSN version >=SG6 Explanation This field contains radio access capability information (24.4.008 v.3. Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 146 Ra_Cap_Array_5_Info Sgsn_Rtt_Ra_Cap_Array_5_Info (Cont.) Field name Sgsn_Rtt_Old_Sai_Mcc Datatype in IDS BCDREV8(2) SGSN version >=SG6 Explanation The country code of the old service area in case of RAU Table 147 Sgsn_Rtt_Old_Sai_Mcc DN05148836 Issue 2-2 Id:0900d805809551ce 273 . Mnc is stored in decimal format and the endmark is 0xF. lower_digit (4bits) and upper_digit (4bits). if Mcc is 358 the Sgsn_Cgi_Mcc field is:53 F8 Field exists in the database Table 147 Old_Sai_Mcc Sgsn_Rtt_Old_Sai_Mcc (Cont. one double_digit field is of size byte. For example. lower_digit (4bits) and upper_digit (4bits). Possible values Field contents are: array(2) OF double_digit. Field exists in the database Table 148 Old_Sai_Mnc Sgsn_Rtt_Old_Sai_Mnc Field name Sgsn_Rtt_Old_Sai_Lac Datatype in IDS UINT16 SGSN version >=SG6 Explanation The location area code of the old service area in case of RAU. one double_digit field is of size byte. Field contents are:array(2) OF double_digit. if Mnc is 400 the Sgsn_Cgi_Mnc field is:04 F0. For example.) Field name Sgsn_Rtt_Old_Sai_Mnc Datatype in IDS BCDREV8(2) SGSN version >=SG6 Explanation The mobile network code of the old service area in case of RAU. Double_digit has two parts. Possible values 0x0 – 0xFFFF Field exists in the database Old_Sai_Sac Table 150 274 Sgsn_Rtt_Old_Sai_Sac Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values 0x1 – 0xFFFF Field exists in the database Old_Sai_Lac Table 149 Sgsn_Rtt_Old_Sai_Lac Field name Sgsn_Rtt_Old_Sai_Sac Datatype in IDS UINT16 SGSN version >=SG6 Explanation Service area identity of the old service area in case of RAU. Mcc is stored in decimal format and the endmark is 0xF. Double_digit has two parts.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field contains country code. For example. Possible values Field contents are: array(2) OF double_digit. lower_digit (4bits) and upper_digit (4bits). RTT report descriptions Field contents are: array(2) OF double_digit. Mnc is stored in decimal format and the endmark is 0xF. if Mcc is 358 the Sgsn_Cgi_Mcc field is: 53 F8 Field exists in the database Table 151 Old_Cgi_Mcc Sgsn_Rtt_Old_Cgi_Mcc Field name Sgsn_Rtt_Old_Cgi_Mnc Datatype in IDS BCDREV8(2) SGSN version >=SG6 Explanation The mobile network code of the cell in the case of RAU.Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Rtt_Old_Cgi_Mcc Datatype in IDS BCDREV8(2) SGSN version >=SG6 Explanation The country code of the old cell in the case of RAU. if Mnc is 400 the Sgsn_Cgi_Mnc field is: 04 F0. Mcc is stored in decimal format and the endmark is 0xF. Double_digit has two parts. Double_digit has two parts. lower_digit (4bits) and upper_digit (4bits). Possible values This field contains the country code. For example. one double_digit field is of size byte. one double_digit field is of size byte. Field exists in the database Table 152 Old_Cgi_Mnc Sgsn_Rtt_Old_Cgi_Mnc Field name Sgsn_Rtt_Old_Cgi_Lac Datatype in IDS UINT16 SGSN version >=SG6 Explanation The location area code of the old cell in the case of RAU Possible values 0x1 – 0xFFFF Field exists in the database Old_Cgi_Lac Table 153 Sgsn_Rtt_Old_Cgi_Lac Field name Sgsn_Rtt_Old_Cgi_Rac Datatype in IDS UINT8 SGSN version >=SG6 Table 154 Sgsn_Rtt_Old_Cgi_Rac DN05148836 Issue 2-2 Id:0900d805809551ce 275 . RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Explanation The old routing area code of the cell in the case of RAU Possible values 0x1 – 0xFF Field exists in the database Old_Cgi_Rac Table 154 Sgsn_Rtt_Old_Cgi_Rac (Cont. Field exists in the database Event_Start_Time Table 156 Sgsn_Rtt_Event_Start_Time Field name Sgsn_Rtt_Event_Start_Date Datatype in IDS BCDDATE SGSN version >=SG6 Explanation The date when the event was started Possible values Date is in format day:month:year. Table 158 276 Sgsn_Rtt_Event_Stop_Time Id:0900d805809551ce DN05148836 Issue 2-2 . Field exists in the database Event_Start_Date Table 157 Sgsn_Rtt_Event_Start_Date Field name Sgsn_Rtt_Event_Stop_Time Datatype in IDS BCDTIME SGSN version >=SG6 Explanation The time when the event was stopped Possible values Time is in format hundredsofseconds:seconds:minutes:hours.) Field name Sgsn_Rtt_Old_Cgi_Ci Datatype in IDS UINT16 SGSN version >=SG6 Explanation The old cell identity of the cell in the case of RAU Possible values 0x1 – 0xFFFF Field exists in the database Old_Cgi_Ci Table 155 Sgsn_Rtt_Old_Cgi_Ci Field name Sgsn_Rtt_Event_Start_Time Datatype in IDS BCDTIME SGSN version >=SG6 Explanation The time when the event was started Possible values Time is in format hundredsofseconds:seconds:minutes:hours. one double_digit field is of size byte. For example. lower_digit (4bits) and upper_digit (4bits). lower_digit (4bits) and upper_digit (4bits). Field contents are: array(2) OF double_digit. Field exists in the database Event_Stop_Date Table 159 RTT report descriptions Sgsn_Rtt_Event_Stop_Date Field name Sgsn_Rtt_Old_Rnc_Address_Mcc Datatype in IDS UINT16 SGSN version >=SG6 Explanation The old RNC’s mobile country code in the case of RAU.) Field name Sgsn_Rtt_Event_Stop_Date Datatype in IDS BCDDATE SGSN version >=SG6 Explanation The date when the event was stopped. is Mnc is 400 the Sgsn_Cgi_Mnc field is: 04 F0. if Mcc is 358 the Sgsn_Cgi_Mcc field is: 53 F8 Field exists in the database Table 160 Old_Rnc_Address_Mcc Sgsn_Rtt_Old_Rnc_Address_Mcc Field name Sgsn_Rtt_Old_Rnc_Address_Mnc Datatype in IDS UINT16 SGSN version >=SG6 Explanation The old RNC’s mobile network code in the case of RAU. Possible values Field contents are: array(2) OF double_digit. Mnc is stored in decimal format and the endmark is 0xF. Mcc is stored in decimal format and the end mark is 0xF. For example. Possible values This field contains country code.Traffica Reference Guide for SGSN Direct Interface Field exists in the database Table 158 Event_Stop_Time Sgsn_Rtt_Event_Stop_Time (Cont. one double_digit field is of size byte. Field exists in the database Table 161 Old_Rnc_Address_Mnc Sgsn_Rtt_Old_Rnc_Address_Mnc DN05148836 Issue 2-2 Id:0900d805809551ce 277 . Possible values Date is in format day:month:year. Double_digit has two parts. Double_digit has two parts. Sgsn_Event Complete_Time field does not contain valid information either Field exists in the database Table 164 Event_Complete_Date Sgsn_Rtt_Event_Complete_Date Field name Sgsn_Rtt_Xid_Reset_Start_Time Datatype in IDS The time when XID Reset was started. This field does not contain valid information if Sgsn_Event_Complete_Date is 0. Field exists in the database Table 163 Event_Complete_Time Sgsn_Rtt_Event_Complete_Time Field name Sgsn_Rtt_Event_Complete_Date Datatype in IDS BCDDATE SGSN version >=SG6 Explanation The date when the event was stopped. This field does not contain valid information if Sgsn_Xid_Reset_Start_Date is 0 Table 165 278 Sgsn_Rtt_Xid_Reset_Start_Time Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values Time is in format hundredsofseconds:seconds:minutes:hours. Possible values Time is in format hundredsofseconds:seconds:minutes:hours.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Rtt_Old_Rnc_Id Datatype in IDS UINT16 SGSN version >=SG6 Explanation The old RNC’s identifier in the case of RAU. 0x00000000 = Event has no complete date. Possible values Date is in format day:month:year. Possible values RNC’s identifier Field exists in the database Old_Rnc_Id Table 162 Sgsn_Rtt_Old_Rnc_Id Field name Sgsn_Rtt_Event_Complete_Time Datatype in IDS BCDTIME SGSN version >=SG6 Explanation The time when the event was completed. SGSN version >=SG6 Explanation The time when XID Reset was started. 0x00000000 = XID reset has no end date.Traffica Reference Guide for SGSN Direct Interface Field exists in the database Table 165 RTT report descriptions Xid_Reset_Start_Time Sgsn_Rtt_Xid_Reset_Start_Time (Cont. Possible values Date is in format day:month:year. Possible values Time is in format hundredsofseconds:seconds:minutes:hours. Sgsn Xid_Reset_Start_Time field does not contain valid information either Field exists in the database Table 166 Xid_Reset_Start_Date Sgsn_Rtt_Xid_Reset_Start_Date Field name Sgsn_Rtt_Xid_Reset_End_Time Datatype in IDS BCDTIME SGSN version >=SG6 Explanation The time when XID Reset was completed. Possible values Date is in format day:month:year.) Field name Sgsn_Rtt_Xid_Reset_Start_Date Datatype in IDS BCDDATE SGSN version >=SG6 Explanation The date when XID Reset was started. Field exists in the database Table 167 Xid_Reset_End_Time Sgsn_Rtt_Xid_Reset_End_Time Field name Sgsn_Rtt_Xid_Reset_End_Date Datatype in IDS BCDDATE SGSN version >=SG6 Explanation The date when XID Reset was completed. 0x00000000 = identity check has no end date. This field does not contain valid information if Sgsn_Xid_Reset_End_Date is 0. Sgsn Xid_Reset_End_Time field does not contain valid information either Field exists in the database Table 168 Xid_Reset_End_Date Sgsn_Rtt_Xid_Reset_End_Date Field name Sgsn_Rtt_Ra_Access_Type Datatype in IDS UINT8 Table 169 Sgsn_Rtt_Ra_Access_Type DN05148836 Issue 2-2 Id:0900d805809551ce 279 . ) Field name Sgsn_Rtt_Ra_Cap_Array_0_Info_2 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24. Table 170 280 Sgsn_Rtt_Ra_Cap_Array_0_Info_2 Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG6 Explanation The type of the radio access network.1).3.4. Possible values utran = 0x01 geran = 0x02 distr_uma_c = 0xD0 ihspa_c = 0xD2 not_def = 0xFF Field exists in the database Table 169 Ra_Access_Type Sgsn_Rtt_Ra_Access_Type (Cont.008 v. Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1)a5_6 BITS(1)a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 170 Ra_Cap_Array_0_Info_2 Sgsn_Rtt_Ra_Cap_Array_0_Info_2 (Cont.3. Table 171 Sgsn_Rtt_Ra_Cap_Array_0_Info_5 DN05148836 Issue 2-2 Id:0900d805809551ce 281 .008 v.) Field name Sgsn_Rtt_Ra_Cap_Array_0_Info_5 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.4.1). Table 172 282 Sgsn_Rtt_Ra_Cap_Array_0_Info_6 Id:0900d805809551ce DN05148836 Issue 2-2 .1).RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 171 Ra_Cap_Array_0_Info_5 Sgsn_Rtt_Ra_Cap_Array_0_Info_5 (Cont.3.) Field name Sgsn_Rtt_Ra_Cap_Array_0_Info_6 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.4.008 v. ) Field name Sgsn_Rtt_Ra_Cap_Array_0_Info_7 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.1). Table 173 Sgsn_Rtt_Ra_Cap_Array_0_Info_7 DN05148836 Issue 2-2 Id:0900d805809551ce 283 .Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1)sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 172 Ra_Cap_Array_0_Info_6 Sgsn_Rtt_Ra_Cap_Array_0_Info_6 (Cont.4.3.008 v. Table 174 284 Sgsn_Rtt_Ra_Cap_Array_0_Info_8 Id:0900d805809551ce DN05148836 Issue 2-2 .3.008 v.4.) Field name Sgsn_Rtt_Ra_Cap_Array_0_Info_8 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind hscsd BITS(2) BITS(5) gprs_multi_sl_cl gedac BITS(5) BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp egprs_supp BITS(1) BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 spare Field exists in the database Table 173 BITS(1) BITS(6) Ra_Cap_Array_0_Info_7 Sgsn_Rtt_Ra_Cap_Array_0_Info_7 (Cont.1). Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 174 Ra_Cap_Array_0_Info_8 Sgsn_Rtt_Ra_Cap_Array_0_Info_8 (Cont.4.3.) Field name Sgsn_Rtt_Ra_Cap_Array_1_Info_1 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.008 v.1). Table 175 Sgsn_Rtt_Ra_Cap_Array_1_Info_1 DN05148836 Issue 2-2 Id:0900d805809551ce 285 . Table 176 286 Sgsn_Rtt_Ra_Cap_Array_1_Info_2 Id:0900d805809551ce DN05148836 Issue 2-2 .) Field name Sgsn_Rtt_Ra_Cap_Array_1_Info_2 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.4.1).008 v.3.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 175 Ra_Cap_Array_1_Info_1 Sgsn_Rtt_Ra_Cap_Array_1_Info_1 (Cont. Table 177 Sgsn_Rtt_Ra_Cap_Array_1_Info_3 DN05148836 Issue 2-2 Id:0900d805809551ce 287 .4.008 v.3.) Field name Sgsn_Rtt_Ra_Cap_Array_1_Info_3 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.1).Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 176 Ra_Cap_Array_1_Info_2 Sgsn_Rtt_Ra_Cap_Array_1_Info_2 (Cont. 1). Table 178 288 Sgsn_Rtt_Ra_Cap_Array_1_Info_4 Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 177 Ra_Cap_Array_1_Info_3 Sgsn_Rtt_Ra_Cap_Array_1_Info_3 (Cont.008 v.3.) Field name Sgsn_Rtt_Ra_Cap_Array_1_Info_4 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.4. Table 179 Sgsn_Rtt_Ra_Cap_Array_1_Info_5 DN05148836 Issue 2-2 Id:0900d805809551ce 289 .4.008 v.) Field name Sgsn_Rtt_Ra_Cap_Array_1_Info_5 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.1).Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 178 Ra_Cap_Array_1_Info_4 Sgsn_Rtt_Ra_Cap_Array_1_Info_4 (Cont.3. 3. Table 180 290 Sgsn_Rtt_Ra_Cap_Array_1_Info_6 Id:0900d805809551ce DN05148836 Issue 2-2 .) Field name Sgsn_Rtt_Ra_Cap_Array_1_Info_6 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.008 v.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 179 Ra_Cap_Array_1_Info_5 Sgsn_Rtt_Ra_Cap_Array_1_Info_5 (Cont.4.1). Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 180 Ra_Cap_Array_1_Info_6 Sgsn_Rtt_Ra_Cap_Array_1_Info_6 (Cont.) Field name Sgsn_Rtt_Ra_Cap_Array_1_Info_7 Datatype in IDS UINT8 SGSN version >=SG6 Explanation UINT8 Table 181 Sgsn_Rtt_Ra_Cap_Array_1_Info_7 DN05148836 Issue 2-2 Id:0900d805809551ce 291 . ) Field name Sgsn_Rtt_Ra_Cap_Array_1_Info_8 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.4.3. Table 182 292 Sgsn_Rtt_Ra_Cap_Array_1_Info_8 Id:0900d805809551ce DN05148836 Issue 2-2 .1).008 v.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 181 Ra_Cap_Array_1_Info_7 Sgsn_Rtt_Ra_Cap_Array_1_Info_7 (Cont. Table 183 Sgsn_Rtt_Ra_Cap_Array_2_Info_1 DN05148836 Issue 2-2 Id:0900d805809551ce 293 .) Field name Sgsn_Rtt_Ra_Cap_Array_2_Info_1 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 182 Ra_Cap_Array_1_Info_8 Sgsn_Rtt_Ra_Cap_Array_1_Info_8 (Cont.1).008 v.3.4. RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 183 Ra_Cap_Array_2_Info_1 Sgsn_Rtt_Ra_Cap_Array_2_Info_1 (Cont.4. Table 184 294 Sgsn_Rtt_Ra_Cap_Array_2_Info_2 Id:0900d805809551ce DN05148836 Issue 2-2 .008 v.3.1).) Field name Sgsn_Rtt_Ra_Cap_Array_2_Info_2 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24. Table 185 Sgsn_Rtt_Ra_Cap_Array_3_Info_3 DN05148836 Issue 2-2 Id:0900d805809551ce 295 .1).) Field name Sgsn_Rtt_Ra_Cap_Array_3_Info_3 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 184 Ra_Cap_Array_2_Info_2 Sgsn_Rtt_Ra_Cap_Array_2_Info_2 (Cont.008 v.4.3. ) Field name Sgsn_Rtt_Ra_Cap_Array_3_Info_4 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 185 Ra_Cap_Array_2_Info_3 Sgsn_Rtt_Ra_Cap_Array_3_Info_3 (Cont.4.1).008 v.3. Table 186 296 Sgsn_Rtt_Ra_Cap_Array_3_Info_4 Id:0900d805809551ce DN05148836 Issue 2-2 . 1).) Field name Sgsn_Rtt_Ra_Cap_Array_3_Info_5 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.3.4. Table 187 Sgsn_Rtt_Ra_Cap_Array_3_Info_5 DN05148836 Issue 2-2 Id:0900d805809551ce 297 .Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 186 Ra_Cap_Array_2_Info_4 Sgsn_Rtt_Ra_Cap_Array_3_Info_4 (Cont.008 v. RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 187 Ra_Cap_Array_2_Info_5 Sgsn_Rtt_Ra_Cap_Array_3_Info_5 (Cont.4. Table 188 298 Sgsn_Rtt_Ra_Cap_Array_3_Info_6 Id:0900d805809551ce DN05148836 Issue 2-2 .008 v.) Field name Sgsn_Rtt_Ra_Cap_Array_3_Info_6 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.3.1). 1).4.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 188 Ra_Cap_Array_2_Info_6 Sgsn_Rtt_Ra_Cap_Array_3_Info_6 (Cont.008 v.) Field name Sgsn_Rtt_Ra_Cap_Array_3_Info_7 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.3. Table 189 Sgsn_Rtt_Ra_Cap_Array_3_Info_7 DN05148836 Issue 2-2 Id:0900d805809551ce 299 . RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 189 Ra_Cap_Array_2_Info_7 Sgsn_Rtt_Ra_Cap_Array_3_Info_7 (Cont.) Field name Sgsn_Rtt_Ra_Cap_Array_3_Info_8 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.4. Table 190 300 Sgsn_Rtt_Ra_Cap_Array_3_Info_8 Id:0900d805809551ce DN05148836 Issue 2-2 .008 v.3.1). Table 191 Sgsn_Rtt_Ra_Cap_Array_4_Acc_Tec_Type DN05148836 Issue 2-2 Id:0900d805809551ce 301 .Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 190 Ra_Cap_Array_2_Info_8 Sgsn_Rtt_Ra_Cap_Array_3_Info_8 (Cont.) Field name Sgsn_Rtt_Ra_Cap_Array_4_Acc_Tec_Type Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains MS Radio access capability arrays technology type. RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface 0x0 = GSM 900-P Access Technology Type 0x1 = GSM 900-E Access Technology Type 0x2 = GSM 900-R Access Technology Type 0x3 = GSM 1800 Access Technology Type 0x4 = GSM 1900 Access Technology Type 0x5 = GSM 450 Access Technology Type 0x6 = GSM 480 Access Technology Type 0x7 = GSM 850 Access Technology Type 0xFF = Not used Field exists in the database Table 191 Ra_Cap_Array_4_Acc_Tec_Type Sgsn_Rtt_Ra_Cap_Array_4_Acc_Tec_Type (Cont.008 v.) Field name Sgsn_Rtt_Ra_Cap_Array_4_Info_1 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.4.3.1). Table 192 302 Sgsn_Rtt_Ra_Cap_Array_4_Info_1 Id:0900d805809551ce DN05148836 Issue 2-2 . 4.) Field name Sgsn_Rtt_Ra_Cap_Array_4_Info_2 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 192 Ra_Cap_Array_4_Info_1 Sgsn_Rtt_Ra_Cap_Array_4_Info_1 (Cont.1). Table 193 Sgsn_Rtt_Ra_Cap_Array_4_Info_2 DN05148836 Issue 2-2 Id:0900d805809551ce 303 .3.008 v. 4.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) mts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 193 Ra_Cap_Array_4_Info_2 Sgsn_Rtt_Ra_Cap_Array_4_Info_2 (Cont.008 v.1). Table 194 304 Sgsn_Rtt_Ra_Cap_Array_4_Info_3 Id:0900d805809551ce DN05148836 Issue 2-2 .) Field name Sgsn_Rtt_Ra_Cap_Array_4_Info_3 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.3. 1).4.) Field name Sgsn_Rtt_Ra_Cap_Array_4_Info_4 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.008 v. Table 195 Sgsn_Rtt_Ra_Cap_Array_4_Info_4 DN05148836 Issue 2-2 Id:0900d805809551ce 305 .Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1 a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 194 Ra_Cap_Array_4_Info_3 Sgsn_Rtt_Ra_Cap_Array_4_Info_3 (Cont.3. Table 196 306 Sgsn_Rtt_Ra_Cap_Array_4_Info_5 Id:0900d805809551ce DN05148836 Issue 2-2 .3.1).RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 195 Ra_Cap_Array_4_Info_4 Sgsn_Rtt_Ra_Cap_Array_4_Info_4 (Cont.008 v.) Field name Sgsn_Rtt_Ra_Cap_Array_4_Info_5 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.4. 1).Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 196 Ra_Cap_Array_4_Info_5 Sgsn_Rtt_Ra_Cap_Array_4_Info_5 (Cont. Table 197 Sgsn_Rtt_Ra_Cap_Array_4_Info_6 DN05148836 Issue 2-2 Id:0900d805809551ce 307 .3.4.008 v.) Field name Sgsn_Rtt_Ra_Cap_Array_4_Info_6 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24. 1).3.4. Table 198 308 Sgsn_Rtt_Ra_Cap_Array_4_Info_7 Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 197 Ra_Cap_Array_4_Info_6 Sgsn_Rtt_Ra_Cap_Array_4_Info_6 (Cont.008 v.) Field name Sgsn_Rtt_Ra_Cap_Array_4_Info_7 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24. 008 v. Table 199 Sgsn_Rtt_Ra_Cap_Array_4_Info_8 DN05148836 Issue 2-2 Id:0900d805809551ce 309 .4.3.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 198 Ra_Cap_Array_4_Info_7 Sgsn_Rtt_Ra_Cap_Array_4_Info_7 (Cont.) Field name Sgsn_Rtt_Ra_Cap_Array_4_Info_8 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.1). Table 200 310 Sgsn_Rtt_Ra_Cap_Array_5_Info_1 Id:0900d805809551ce DN05148836 Issue 2-2 .008 v.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 199 Ra_Cap_Array_4_Info_8 Sgsn_Rtt_Ra_Cap_Array_4_Info_8 (Cont.3.4.1).) Field name Sgsn_Rtt_Ra_Cap_Array_5_Info_1 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24. ) Field name Sgsn_Rtt_Ra_Cap_Array_5_Info_2 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.1).3. Table 201 Sgsn_Rtt_Ra_Cap_Array_5_Info_2 DN05148836 Issue 2-2 Id:0900d805809551ce 311 .008 v.4.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) mts_tdd BITS(1) dma_2000 BITS(1) spare BITS(6) Field exists in the database Table 200 Ra_Cap_Array_5_Info_1 Sgsn_Rtt_Ra_Cap_Array_5_Info_1 (Cont. 1).) Field name Sgsn_Rtt_Ra_Cap_Array_5_Info_3 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.008 v.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 201 Ra_Cap_Array_5_Info_2 Sgsn_Rtt_Ra_Cap_Array_5_Info_2 (Cont. Table 202 312 Sgsn_Rtt_Ra_Cap_Array_5_Info_3 Id:0900d805809551ce DN05148836 Issue 2-2 .4.3. Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) dma_2000 BITS(1) spare BITS(6) Field exists in the database Table 202 Ra_Cap_Array_5_Info_3 Sgsn_Rtt_Ra_Cap_Array_5_Info_3 (Cont.4. Table 203 Sgsn_Rtt_Ra_Cap_Array_5_Info_4 DN05148836 Issue 2-2 Id:0900d805809551ce 313 .1).008 v.) Field name Sgsn_Rtt_Ra_Cap_Array_5_Info_4 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.3. 4. Table 204 314 Sgsn_Rtt_Ra_Cap_Array_5_Info_5 Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) mts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 203 Ra_Cap_Array_5_Info_4 Sgsn_Rtt_Ra_Cap_Array_5_Info_4 (Cont.008 v.) Field name Sgsn_Rtt_Ra_Cap_Array_5_Info_5 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.1).3. 1).Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 204 Ra_Cap_Array_5_Info_5 Sgsn_Rtt_Ra_Cap_Array_5_Info_5 (Cont.4.3. Table 205 Sgsn_Rtt_Ra_Cap_Array_5_Info_6 DN05148836 Issue 2-2 Id:0900d805809551ce 315 .) Field name Sgsn_Rtt_Ra_Cap_Array_5_Info_6 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.008 v. 008 v.) Field name Sgsn_Rtt_Ra_Cap_Array_5_Info_7 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.3.4. Table 206 316 Sgsn_Rtt_Ra_Cap_Array_5_Info_7 Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 205 Ra_Cap_Array_5_Info_6 Sgsn_Rtt_Ra_Cap_Array_5_Info_6 (Cont.1). 4.008 v. Table 207 Sgsn_Rtt_Ra_Cap_Array_5_Info_8 DN05148836 Issue 2-2 Id:0900d805809551ce 317 .) Field name Sgsn_Rtt_Ra_Cap_Array_5_Info_8 Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains radio access capability information (24.3.1).Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_c BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 206 Ra_Cap_Array_5_Info_7 Sgsn_Rtt_Ra_Cap_Array_5_Info_7 (Cont. ) Field name Sgsn_rtt_tunnel_info Datatype in IDS UINT8 SGSN version >=SG6 CD4 Table 208 318 Sgsn_rtt_tunnel_info Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) hscsd BITS(5) gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) sms_value BITS(4) sm_value BITS(4) ecsd_multi_sl_cl BITS(5) egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) mac_mode_supp BITS(1) egprs_supp BITS(1) _8psk_pw_cap BITS(2) compact_imc BITS(1) revision_level BITS(1) umts_fdd BITS(1) umts_tdd BITS(1) cdma_2000 BITS(1) spare BITS(6) Field exists in the database Table 207 Ra_Cap_Array_5_Info_8 Sgsn_Rtt_Ra_Cap_Array_5_Info_8 (Cont. Possible value 0x0 means that Direct Tunneling is not used but user plane traffic goes via SGSN." Possible Values Field exists in database Table 209 Tlli_Ptmsi Sgsn_Tlli_Ptmsi Field name Sgsn_Rtt_Req_Qos_Ext_Max_Br_Ul Datatype in IDS UINT8 SGSN Version >=SG7 Explanation Field of Quality of Service that the user requests. Possible values 0x0 = two tunnel 0x1 = one tunnel 0x2 = two tunnel to one tunnel 0x3 = one tunnel to two tunnel 0xFF = not used Field exists in the database Table 208 Sgsn_rtt_tunnel_info (Cont.Traffica Reference Guide for SGSN Direct Interface Explanation RTT report descriptions One GTP tunnel PDP context information. Temporary identifier which unambiguously identifies the logical link between GPRS mobile station and serving GPRS support node (SGSN) within one routing area in the logical link control (LLC) level. Possible value 0x1 means that Direct Tunneling is used. Random number allocated by the serving GPRS support node (SGSN) that offers extra security when identifying the subscriber .) Field name Sgsn_Tlli_Ptmsi Datatype in IDS UINT32 SGSN Version >=SG7 Explanation "TLLI Temporary logical link identity. Table 210 Sgsn_Rtt_Req_Qos_Ext_Max_Br_Ul DN05148836 Issue 2-2 Id:0900d805809551ce 319 . Possible values 0x2 and 0x3 are related to PDP Context modification cases where DT (Direct Tunneling) is taken away or into use.P-TMSI Packet temporary mobile subscriber identity. Table 211 320 Sgsn_Rtt_Req_Qos_Ext_Guar_Br_Ul Id:0900d805809551ce DN05148836 Issue 2-2 . giving a range of values from 17 Mbps to 128 Mbps in 1 Mbps increments.74] ‘00000001’ – ‘01001010’: 8600 kbps + (the binary coded value in 8 bits * 100 kbps).186] ‘01001011’ – ‘10111010’: 16 Mbps + (the binary coded value in 8 bits * 1 Mbps). [187 . [75 . For all other values: Ignore the value indicated by the Maximum bit rate for uplink (Sgsn_Rtt_Req_Qos_Max_Bit_Rate_For_Ul) and use the following value: [1 . Field exists in database Table 210 Req_Qos_Ext_Max_Br_Ul Sgsn_Rtt_Req_Qos_Ext_Max_Br_Ul (Cont. use the value indicated by the Maximum bit rate for uplink in field Sgsn_Rtt_Req_Qos_Max_Bit_Rate_For_Ul. giving a range of values from 130 Mbps to 256 Mbps in 2 Mbps increments.RTT report descriptions Possible Values Traffica Reference Guide for SGSN Direct Interface With value ‘00000000’.250] ‘10111011’ – ‘11111010’: 128 Mbps + (the binary coded value in 8 bits * 2 Mbps). giving a range of values from 8700 to 16000 kbps in 100 kbps increments.) Field name Sgsn_Rtt_Req_Qos_Ext_Guar_Br_Ul Datatype in IDS UINT8 SGSN Version >=SG7 Explanation Field of Quality of Service that the user requests. For all other values: Ignore the value indicated by the Guaranteed bit rate for uplink (Sgsn_Rtt_Req_Qos_Guaran_Bit_Rate_Ul) and use the following value: [1 .74] ‘00000001’ – ‘01001010’: 8600 kbps + (the binary coded value in 8 bits * 100 kbps). [75 . use the value indicated by the Guaranteed bit rate for uplink in field Sgsn_Rtt_Req_Qos_Guaran_Bit_Rate_Ul.Traffica Reference Guide for SGSN Direct Interface Possible Values RTT report descriptions With value ‘00000000’.250] ‘10111011’ – ‘11111010’: 128 Mbps + (the binary coded value in 8 bits * 2 Mbps). giving a range of values from 130 Mbps to 256 Mbps in 2 Mbps increments. giving a range of values from 8700 to 16000 kbps in 100 kbps increments.186] ‘01001011’ – ‘10111010’: 16 Mbps + (the binary coded value in 8 bits * 1 Mbps). Field exists in database Table 211 Req_Qos_Ext_Guar_Br_Ul Sgsn_Rtt_Req_Qos_Ext_Guar_Br_Ul (Cont. [187 . giving a range of values from 17 Mbps to 128 Mbps in 1 Mbps increments.) Field name Sgsn_Rtt_Neg_Qos_Ext_Max_Br_Ul Datatype in IDS UINT8 SGSN Version >=SG7 Explanation Field of Quality of Service that user gets after SGSN and GGSN negotiation. Table 212 Sgsn_Rtt_Neg_Qos_Ext_Max_Br_Ul DN05148836 Issue 2-2 Id:0900d805809551ce 321 . giving a range of values from 8700 to 16000 kbps in 100 kbps increments.74] ‘00000001’ – ‘01001010’: 8600 kbps + (the binary coded value in 8 bits * 100 kbps).250] ‘10111011’ – ‘11111010’: 128 Mbps + (the binary coded value in 8 bits * 2 Mbps). use the value indicated by the Maximum bit rate for uplink in field Sgsn_Rtt_Neg_Qos_Max_Bit_Rate_For_Ul.186] ‘01001011’ – ‘10111010’: 16 Mbps + (the binary coded value in 8 bits * 1 Mbps).RTT report descriptions Possible Values Traffica Reference Guide for SGSN Direct Interface With value ‘00000000’. Field exists in database Table 212 Neg_Qos_Ext_Max_Br_Ul Sgsn_Rtt_Neg_Qos_Ext_Max_Br_Ul (Cont. [75 . [187 . giving a range of values from 17 Mbps to 128 Mbps in 1 Mbps increments. giving a range of values from 130 Mbps to 256 Mbps in 2 Mbps increments.) Field name Sgsn_Rtt_Neg_Qos_Ext_Guar_Br_Ul Datatype in IDS UINT8 SGSN Version >=SG7 Explanation Field of Quality of Service that user gets after SGSN and GGSN negotiation. Table 213 322 Sgsn_Rtt_Neg_Qos_Ext_Guar_Br_Ul Id:0900d805809551ce DN05148836 Issue 2-2 . For all other values: Ignore the value indicated by the Maximum bit rate for uplink (Sgsn_Rtt_Neg_Qos_Max_Bit_Rate_For_Ul) and use the following value: [1 . use the value indicated by the Guaranteed bit rate for downlink in field Sgsn_Rtt_Neg_Qos_Guaran_Bit_Rate_Ul. giving a range of values from 8700 to 16000 kbps in 100 kbps increments. Field exists in database Table 213 Neg_Qos_Ext_Guar_Br_UI Sgsn_Rtt_Neg_Qos_Ext_Guar_Br_Ul (Cont. Table 214 Sgsn_Rtt_Req_Qos_E_Alloc_Retention DN05148836 Issue 2-2 Id:0900d805809551ce 323 .) Field name Sgsn_Rtt_Req_Qos_E_Alloc_Retention Datatype in IDS UINT8 SGSN Version >=SG8 Explanation This field has the details about the Quality of Service that the user requests.74] ‘00000001’ – ‘01001010’: 8600 kbps + (the binary coded value in 8 bits * 100 kbps). giving a range of values from 17 Mbps to 128 Mbps in 1 Mbps increments. Evolved Allocation/retention priority. giving a range of values from 130 Mbps to 256 Mbps in 2 Mbps increments. [75 .186] ‘01001011’ – ‘10111010’: 16 Mbps + (the binary coded value in 8 bits * 1 Mbps).Traffica Reference Guide for SGSN Direct Interface Possible Values RTT report descriptions With value ‘00000000’.250] ‘10111011’ – ‘11111010’: 128 Mbps + (the binary coded value in 8 bits * 2 Mbps). For all other values: Ignore the value indicated by the Guaranteed bit rate for uplink (Sgsn_Rtt_Neg_Qos_Guaran_Bit_Rate_Ul) and use the following value: [1 . [187 . e_arp_8_c = 0x8 Evolved allocation/retention priority value 8'. e_arp_12_c = 0xC Evolved allocation/retention priority value 12'. Field exists in database Table 214 324 Req_Qos_E_Alloc_Retention Sgsn_Rtt_Req_Qos_E_Alloc_Retention (Cont. e_arp_no_prior_c = 0xF Evolved allocation/retention no priority'. e_arp_1_c = 0x1 Evolved allocation/retention priority value 1'. e_arp_5_c = 0x5 Evolved allocation/retention priority value 5'.) Id:0900d805809551ce DN05148836 Issue 2-2 . e_arp_2_c = 0x2 Evolved allocation/retention priority value 2'. e_arp_14_c = 0xE Evolved allocation/retention priority value 14'. e_arp_high_c = 0x1 Evolved allocation/retention highest priority value'. e_arp_13_c = 0xD Evolved allocation/retention priority value 13'. e_arp_9_c = 0x9 Evolved allocation/retention priority value 9'. e_arp_3_c = 0x3 Evolved allocation/retention priority value 3'. e_arp_low_c = 0xE Evolved allocation/retention lowest priority value'. e_arp_11_c = 0xB Evolved allocation/retention priority value 11'. e_arp_6_c = 0x6 Evolved allocation/retention priority value 6'. e_arp_4_c = 0x4 Evolved allocation/retention priority value 4'. e_arp_15_c = 0xF Evolved allocation/retention priority value 15'.RTT report descriptions Possible Values Traffica Reference Guide for SGSN Direct Interface e_arp_not_in_use_c = 0xFF Evolved allocation/retention priority not in use'. e_arp_7_c = 0x7 Evolved allocation/retention priority value 7'. e_arp_10_c = 0xA Evolved allocation/retention priority value 10'. Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Rtt_Req_Qos_E_Alloc_Retention_Pvi Datatype in IDS UINT8 SGSN Version >=SG8 Explanation This field has the details about the Quality of Service that the user requests. Field exists in database Table 216 Req_Qos_E_Alloc_Retention Sgsn_Rtt_Req_Qos_E_Alloc_Retention_Pci Field name Sgsn_Rtt_Neg_Qos_E_Alloc_Retention Datatype in IDS UINT8 SGSN Version >=SG8 Explanation This field has the details about the Quality of Service that the user gets after SGSN and GGSN negotiation. Field exists in database Table 215 Req_Qos_E_Alloc_Retention_Pvi Sgsn_Rtt_Req_Qos_E_Alloc_Retention_Pvi Field name Sgsn_Rtt_Req_Qos_E_Alloc_Retention_Pci Datatype in IDS UINT8 SGSN Version >=SG8 Explanation This field has the details about the Quality of Service that the user requests. shall not trigger pre-emption. Not used = 0xFF Field is not used. pre-emptable. Possible Values pvi_enabled_c = 0x0 Pre-emption Vulnerability. Possible Values pci_enabled_c = 0x0 Pre-emption Capability. not pre-emptable. Evolved Allocation/retention priority. Evolved allocation/retention priority: Pre-emption Capability. Evolved allocation/retention priority: Pre-emption Vulnerability. Table 217 Sgsn_Rtt_Neg_Qos_E_Alloc_Retention DN05148836 Issue 2-2 Id:0900d805809551ce 325 . pvi_disabled_c = 0x1 Pre-emption Vulnerability. pci_disabled_c = 0x1 Pre-emption Capability. Not used = 0xFF Field is not used. may trigger pre-emption. e_arp_4_c = 0x4 Evolved allocation/retention priority value 4'. e_arp_8_c = 0x8 Evolved allocation/retention priority value 8'. e_arp_10_c = 0xA Evolved allocation/retention priority value 10'. e_arp_low_c = 0xE Evolved allocation/retention lowest priority value'. e_arp_15_c = 0xF Evolved allocation/retention priority value 15'. e_arp_high_c = 0x1 Evolved allocation/retention highest priority value'. e_arp_12_c = 0xC Evolved allocation/retention priority value 12'. Field exists in database Table 217 326 Neg_Qos_E_Alloc_Retention Sgsn_Rtt_Neg_Qos_E_Alloc_Retention (Cont. e_arp_1_c = 0x1 Evolved allocation/retention priority value 1'. e_arp_3_c = 0x3 Evolved allocation/retention priority value 3'. e_arp_7_c = 0x7 Evolved allocation/retention priority value 7'. e_arp_11_c = 0xB Evolved allocation/retention priority value 11'. e_arp_2_c = 0x2 Evolved allocation/retention priority value 2'. e_arp_no_prior_c = 0xF Evolved allocation/retention no priority'. e_arp_14_c = 0xE Evolved allocation/retention priority value 14'. e_arp_9_c = 0x9 Evolved allocation/retention priority value 9'. e_arp_13_c = 0xD Evolved allocation/retention priority value 13'.) Id:0900d805809551ce DN05148836 Issue 2-2 . e_arp_5_c = 0x5 Evolved allocation/retention priority value 5'.RTT report descriptions Possible Values Traffica Reference Guide for SGSN Direct Interface e_arp_not_in_use_c = 0xFF Evolved allocation/retention priority not in use'. e_arp_6_c = 0x6 Evolved allocation/retention priority value 6'. Possible Values pci_enabled_c = 0x0 Pre-emption Capability. Not used = 0xFF Field is not used. Evolved allocation/retention priority: Pre-emption Capability. Possible Values pvi_enabled_c = 0x0 Pre-emption Vulnerability. Table 220 Sgsn_Rtt_Neg_Qos_Source_Stat_Desc DN05148836 Issue 2-2 Id:0900d805809551ce 327 . may trigger pre-emption. Field exists in database Table 219 Neg_Qos_E_Alloc_Retention Sgsn_Rtt_Neg_Qos_E_Alloc_Retention_Pci Field name Sgsn_Rtt_Neg_Qos_Source_Stat_Desc Datatype in IDS UINT8 SGSN Version >=SG6 Explanation Field of Quality of Service that the user gets after SGSN and GGSN negotiation. Field exists in database Table 218 Neg_Qos_E_Alloc_Retention_Pvi Sgsn_Rtt_Neg_Qos_E_Alloc_Retention_Pvi Field name Sgsn_Rtt_Neg_Qos_E_Alloc_Retention_Pci Datatype in IDS UINT8 SGSN Version >=SG8 Explanation This field has the details about the Quality of Service that the user gets after SGSN and GGSN negotiation.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Rtt_Neg_Qos_E_Alloc_Retention_Pvi Datatype in IDS UINT8 SGSN Version >=SG8 Explanation This field has the details about the Quality of Service that the user gets after SGSN and GGSN negotiation. pre-emptable. Not used = 0xFF Field is not used. shall not trigger pre-emption. Source Statistics Descriptor. pvi_disabled_c = 0x1 Pre-emption Vulnerability. not pre-emptable. pci_disabled_c = 0x1 Pre-emption Capability. Evolved allocation/retention priority: Pre-emption Vulnerability. ) Field name Sgsn_Rtt_Req_Qos_Source_Stat_Desc Datatype in IDS UINT8 SGSN Version >=SG6 Explanation Field of Quality of Service that the user requests. Field exists in database Table 220 Neg_Qos_Source_Stat_Desc Sgsn_Rtt_Neg_Qos_Source_Stat_Desc (Cont. The Signalling Indication value is ignored if the Traffic Class is Conversational class. Field exists in database Table 221 Req_Qos_Source_Stat_Desc Sgsn_Rtt_Req_Qos_Source_Stat_Desc Field name Sgsn_Rtt_Req_Qos_Sign_Indication Datatype in IDS UINT8 SGSN Version >=SG6 Explanation Field of Quality of Service that user requests. NOTE: This field is in use only with QoS Release 5 or newer. 0x0 = Unknown 0x1 = Speech The Source Statistics Descriptor value is ignored if the Traffic Class is Interactive class or a Background class. Field exists in database Table 222 Field name Table 223 328 Req_Qos_Sign_Indication Sgsn_Rtt_Req_Qos_Sign_Indication Sgsn_Rtt_Neg_Qos_Sign_Indication Sgsn_Rtt_Neg_Qos_Sign_Indication Id:0900d805809551ce DN05148836 Issue 2-2 . NOTE: This field is in use only with QoS Release 5 or newer. Possible Values Possible values are enumerated. Source Statistics Descriptor.RTT report descriptions Possible Values Traffica Reference Guide for SGSN Direct Interface Possible values are enumerated. 0x0 =Not optimized for signaling traffic 0x1 =Optimized for signaling traffic If set to '1' the QoS of the PDP context is optimised for signalling. Signalling Indication. Possible Values Possible values are enumerated. NOTE: This field is in use only with QoS Release 5 or newer. 0x0 = Unknown 0x1 = Speech The Source Statistics Descriptor value is ignored if the Traffic Class is Interactive class or a Background class. Streaming class or Background class. use the value indicated by the Maximum bit rate for downlink in field Sgsn_Rtt_Req_Qos_Max_Bit_Rate_For_Dl. giving a range of values from 17 Mbps to 128 Mbps in 1 Mbps increments. For all other values: Ignore the value indicated by the Maximum bit rate for downlink (Sgsn_Rtt_Req_Qos_Max_Bit_Rate_For_Dl) and use the following value: [1 . The Signalling Indication value is ignored if the Traffic Class is Conversational class. 0x0 =Not optimized for signaling traffic 0x1 =Optimized for signaling traffic If set to '1' the QoS of the PDP context is optimised for signalling. giving a range of values from 8700 to 16000 kbps in 100 kbps increments. Signalling Indication.74] ‘00000001’ – ‘01001010’: 8600 kbps + (the binary coded value in 8 bits * 100 kbps). Possible Values Possible values are enumerated. Field exists in database Table 224 Req_Qos_Ext_Max_Br_Dl Sgsn_Rtt_Req_Qos_Ext_Max_Br_Dl DN05148836 Issue 2-2 Id:0900d805809551ce 329 . Streaming class or Background class.250] ‘10111011’ – ‘11111010’: 128 Mbps + (the binary coded value in 8 bits * 2 Mbps).186] ‘01001011’ – ‘10111010’: 16 Mbps + (the binary coded value in 8 bits * 1 Mbps).Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Datatype in IDS UINT8 SGSN Version >=SG6 Explanation Field of Quality of Service that user gets after SGSN and GGSN negotiation.) Field name Sgsn_Rtt_Req_Qos_Ext_Max_Br_Dl Datatype in IDS UINT8 SGSN Version >=SG6 Explanation Field of Quality of Service that the user requests. giving a range of values from 130 Mbps to 256 Mbps in 2 Mbps increments. [187 . [75 . NOTE: This field is in use only with QoS Release 5 or newer. Possible Values With value ‘00000000’. Field exists in database Table 223 Neg_Qos_Sign_Indication Sgsn_Rtt_Neg_Qos_Sign_Indication (Cont. Table 226 330 Sgsn_Rtt_Req_Qos_Ext_Guar_Br_Dl Id:0900d805809551ce DN05148836 Issue 2-2 . giving a range of values from 130 Mbps to 256 Mbps in 2 Mbps increments. [75 .186] ‘01001011’ – ‘10111010’: 16 Mbps + (the binary coded value in 8 bits * 1 Mbps).250] ‘10111011’ – ‘11111010’: 128 Mbps + (the binary coded value in 8 bits * 2 Mbps). Field exists in database Table 225 Neg_Qos_Ext_Max_Br_Dl Sgsn_Rtt_Neg_Qos_Ext_Max_Br_Dl Field name Sgsn_Rtt_Req_Qos_Ext_Guar_Br_Dl Datatype in IDS UINT8 SGSN Version >=SG6 Explanation Field of Quality of Service that the user requests. use the value indicated by the Maximum bit rate for downlink in field Sgsn_Rtt_Neg_Qos_Max_Bit_Rate_For_Dl. Possible Values With value ‘00000000’.74] ‘00000001’ – ‘01001010’: 8600 kbps + (the binary coded value in 8 bits * 100 kbps). giving a range of values from 8700 to 16000 kbps in 100 kbps increments. giving a range of values from 17 Mbps to 128 Mbps in 1 Mbps increments.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Rtt_Neg_Qos_Ext_Max_Br_Dl Datatype in IDS UINT8 SGSN Version >=SG6 Explanation Field of Quality of Service that user gets after SGSN and GGSN negotiation. [187 . For all other values: Ignore the value indicated by the Maximum bit rate for downlink (Sgsn_Rtt_Neg_Qos_Max_Bit_Rate_For_Dl) and use the following value: [1 . Traffica Reference Guide for SGSN Direct Interface Possible Values RTT report descriptions With value ‘00000000’. giving a range of values from 130 Mbps to 256 Mbps in 2 Mbps increments.186] ‘01001011’ – ‘10111010’: 16 Mbps + (the binary coded value in 8 bits * 1 Mbps). use the value indicated by the Guaranteed bit rate for downlink in field Sgsn_Rtt_Neg_Qos_Guaran_Bit_Rate_Dl. giving a range of values from 8700 to 16000 kbps in 100 kbps increments.250] ‘10111011’ – ‘11111010’: 128 Mbps + (the binary coded value in 8 bits * 2 Mbps).74] ‘00000001’ – ‘01001010’: 8600 kbps + (the binary coded value in 8 bits * 100 kbps). [187 . giving a range of values from 17 Mbps to 128 Mbps in 1 Mbps increments. [75 .) Field name Sgsn_Rtt_Neg_Qos_Ext_Guar_Br_Dl Datatype in IDS UINT8 SGSN Version >=SG6 Explanation Field of Quality of Service that user gets after SGSN and GGSN negotiation. Field exists in database Table 226 Req_Qos_Ext_Guar_Br_Dl Sgsn_Rtt_Req_Qos_Ext_Guar_Br_Dl (Cont. Table 227 Sgsn_Rtt_Neg_Qos_Ext_Guar_Br_Dl DN05148836 Issue 2-2 Id:0900d805809551ce 331 . For all other values: Ignore the value indicated by the Guaranteed bit rate for downlink (Sgsn_Rtt_Neg_Qos_Guaran_Bit_Rate_Dl) and use the following value: [1 . The SQL datatype appears after the column name and '=' sign. giving a range of values from 130 Mbps to 256 Mbps in 2 Mbps increments. Under the [<SGSN_Release_Id>_GTP_STAT] section. Field exists in database Table 227 Neg_Qos_Ext_Guar_Br_Dl Sgsn_Rtt_Neg_Qos_Ext_Guar_Br_Dl (Cont. For all other values: Ignore the value indicated by the Guaranteed bit rate for downlink (Sgsn_Rtt_Neg_Qos_Guaran_Bit_Rate_Dl) and use the following value: [1 . Sgsn_Gtp_Stat_Report_Count IDS field is Report Count field in Traffic News' SGSN_GTP_STAT_EVENT.) 6.3 GTP_STAT fields The following table shows the GTP_STAT fields: Traffic News event type SGSN_GTP_STAT_EVENT Database table <SGSN_Release_Id>_GTP_STAT Table 228 SGSN_GTP_STAT fields Database column names are the same as IDS fields names without the “Sgsn_Gtp_Stat” prefix.RTT report descriptions Possible Values Traffica Reference Guide for SGSN Direct Interface With value ‘00000000’. Traffic News field names are the same as database column names with spaces used instead of underscores between words. there is a single-row entry for each table column. giving a range of values from 17 Mbps to 128 Mbps in 1 Mbps increments. Sgsn_Gtp_Stat_Report_Count IDS field is Report_Count column in database table <SGSN_Release_Id>_GTP_STAT.250] ‘10111011’ – ‘11111010’: 128 Mbps + (the binary coded value in 8 bits * 2 Mbps). use the value indicated by the Guaranteed bit rate for downlink in field Sgsn_Rtt_Neg_Qos_Guaran_Bit_Rate_Dl.186] ‘01001011’ – ‘10111010’: 16 Mbps + (the binary coded value in 8 bits * 1 Mbps). For example. For example.conf. [75 . [187 . Database column SQL datatypes can be found in the workspace configuration file dbd_sgsn_gtp_stat. Field name Sgsn_Gtp_Stat_Ave_Buf_Fill_Ratio_Nominator Datatype in IDS UINT32 Table 229 332 Sgsn_Gtp_Stat_Ave_Buf_Fill_Ratio_Nominator Id:0900d805809551ce DN05148836 Issue 2-2 . giving a range of values from 8700 to 16000 kbps in 100 kbps increments.74] ‘00000001’ – ‘01001010’: 8600 kbps + (the binary coded value in 8 bits * 100 kbps). ) Field name Sgsn_Gtp_Stat_Ave_Buf_Fill_Ratio_Numerator Datatype in IDS UINT32 SGSN version >=SG3 Explanation Nominator of average GTP buffer utilisation. Sum of GTP buffer samples (0% . You can calculate the average GTP buffer fill ratio by dividing Sgsn_Gtp_Stat_Ave_Buf_Fill_Ratio_Numerator with this field value. Only downlink data with acknowledged LLC mode is stored in the buffer.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions SGSN version >=SG3 Explanation Contains a nominator to calculate average GTP buffer filling ratio. Possible values 0x0-0xFFFFFFFF Field exists in the database Ave_Buf_Fill_Ratio_Numerator Table 230 Sgsn_Gtp_Stat_Ave_Buf_Fill_Ratio_Numerator Field name Sgsn_Gtp_Stat_Buffer_Fill_Ratio_Peak Datatype in IDS UINT32 SGSN version >=SG3 Explanation Contains the value of peak GTP buffer filling ratio as a percentage Possible values 0%-100% Field exists in the database Buffer_Fill_Ratio_Peak Table 231 Sgsn_Gtp_Stat_Buffer_Fill_Ratio_Peak Field name Sgsn_Gtp_Stat_DL_Bytes Datatype in IDS UINT32 SGSN version >=SG3 Explanation Contains the amount of DownLink user data in bytes Possible values Field exists in the database Table 232 DL_Bytes Sgsn_Gtp_Stat_DL_Bytes DN05148836 Issue 2-2 Id:0900d805809551ce 333 .100%) taken. A count of the samples is taken. Possible values 0x0-0xFFFFFFFF Field exists in the database Ave_Buf_Fill_Ratio_Nominator Table 229 Sgsn_Gtp_Stat_Ave_Buf_Fill_Ratio_Nominator (Cont. The average GTP buffer fill ratio can be calculated by dividing this field value with field Sgsn_Gtp_Stat_Ave_Buf_Fill_Ratio_Nominator. RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Rtt_Inact_Reatt_Allw_On Datatype in IDS UINT8 SGSN version SG5 Explanation This field contains information if mobility management noticed first time that subscriber is inactive re-attached always-online type. This counter resets at 00:00 a. Possible values 0x0 = FALSE 0x1 = TRUE (mobility management has noticed first time that subscriber is inactive re-attached always-online type) 0xFF = This fields value must be ignored because the procedure isn’t attach.m. whether reported to Traffica. This field can have values 0x0 or 0x1 only when subscriber makes an attach. Field exists in the database Table 233 Inact_Reatt_Allw_On Sgsn_Rtt_Inact_Reatt_Allw_On Field name Sgsn_Gtp_Stat_DL_Packets Datatype in IDS UINT32 SGSN version >=SG3 Explanation Contains the amount of DownLink GTP packages Possible values Field exists in the database Table 234 DL_Packets Sgsn_Gtp_Stat_DL_Packets Field name Sgsn_Gtp_Stat_Discarded_Packets Datatype in IDS UINT32 SGSN version >=SG3 Explanation Contains the amount of discarded GTP packets Possible values 0x0-0xFFFFFFFF Field exists in the database Discarded_Packages Table 235 Sgsn_Gtp_Stat_Discarded_Packets Field name Sgsn_Gtp_Stat_Event_Count Datatype in IDS UINT32 SGSN version >=SG3 Explanation Contains information about how many reports of this type have been detected. When this field has value 0x1 counter 001186 is updated. Table 236 334 Sgsn_Gtp_Stat_Event_Count Id:0900d805809551ce DN05148836 Issue 2-2 . This means that the same logical PAPU id always refers to the same geographical area.Traffica Reference Guide for SGSN Direct Interface Possible values 0x0-0xFFFFFFFF Field exists in the database Event_Count Table 236 RTT report descriptions Sgsn_Gtp_Stat_Event_Count (Cont. Possible values 0x0-0xFF Field exists in the database Papu_Id Table 238 Sgsn_Gtp_Stat_Papu_Id Field name Sgsn_Gtp_Stat_Physical_Papu_Id Datatype in IDS UINT8 SGSN version SG4 Explanation This field contains the physical index of papu. Possible values 0x41 = maximum of 65 000 attached subscribers 0x64 = maximum of 100 000 attached subscribers 0xFA = maximum of 250 000 attached subscribers Field exists in the database Table 237 Papu_Capa Sgsn_Gtp_Stat_Papu_Capa Field name Sgsn_Gtp_Stat_Papu_Id Datatype in IDS UINT32 SGSN version >=SG3 Explanation Logical PAPU id.0xFF Value 0x28 is used if physical papu id cannot be solved due some internal error Field exists in the database Physical_Papu_Id Table 239 Sgsn_Gtp_Stat_Physical_Papu_Id Field name Sgsn_Gtp_Stat_Report_Count Datatype in IDS UINT32 SGSN version >=SG3 Table 240 Sgsn_Gtp_Stat_Report_Count DN05148836 Issue 2-2 Id:0900d805809551ce 335 .) Field name Sgsn_Gtp_Stat_Papu_Capa Datatype in IDS UINT8 SGSN version SG4 Explanation This field contains the subscriber capacity of particular PAPU in SGSN. Possible values 0x0 . The logical PAPU id follows working PAPU in switchover. Sgsn_Gtp_Stat_Report_Time and Sgsn_Gtp_Stat_Report_Date are stored as SQL TIMESTAMP datatype in column Report_Time. because the possible values can and will change in the future.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Explanation Contains information about how many reports of this type have been sent to Traffica. NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field.m.) Field name Sgsn_Gtp_Stat_Report_Date Datatype in IDS BCDDATE SGSN version >=SG3 Explanation Contains the date when the report was sent to Traffica. Possible values 0x0-0xFFFFFFFF Field exists in the database Report_Count Table 240 Sgsn_Gtp_Stat_Report_Count (Cont. The value of this counter is reset every day at 00:00 a. Possible values 0x0-0xFFFFFFFF Field exists in the database Yes. Possible values 0x0203 (You should avoid using this field in CCMA.) Field exists in the database Report_Id Table 242 Sgsn_Gtp_Stat_Report_Id Field name Sgsn_Gtp_Stat_Report_Time Datatype in IDS BCDTIME SGSN version >=SG3 Explanation Contains the time when the report was sent to Traffica Possible values 0x0-0xFFFFFFFF Field exists in the database Yes. Sgsn_Gtp_Stat_Report_Time and Sgsn_Gtp_Stat_Report_Date are stored as SQL TIMESTAMP datatype in column Report_Time Table 241 Sgsn_Gtp_Stat_Report_Date Field name Sgsn_Gtp_Stat_Report_Id Datatype in IDS UINT16 SGSN version >=SG3 Explanation Contains information of the report type. Table 243 Field name Table 244 336 Sgsn_Gtp_Stat_Report_Time Sgsn_Gtp_Stat_UL_Bytes Sgsn_Gtp_Stat_UL_Bytes Id:0900d805809551ce DN05148836 Issue 2-2 . the value may change in next SGSN releases. Priority Class 1 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Dl_Iu_Gtp_Bytes_Pc_1 Table 247 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_1 Field name Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_1 Datatype in IDS UINT32 Table 248 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_1 DN05148836 Issue 2-2 Id:0900d805809551ce 337 . the ethernet driver might discard incoming packets. This field also shows the total amount of discarded ethernet packets.Traffica Reference Guide for SGSN Direct Interface Datatype in IDS UINT32 SGSN version >=SG3 Explanation Contains the amount of UpLink user data in bytes RTT report descriptions Possible values Field exists in the database Table 244 UL_Bytes Sgsn_Gtp_Stat_UL_Bytes (Cont.) Field name Sgsn_Gtp_Stat_UL_Packets Datatype in IDS UINT32 SGSN version >=SG3 Explanation Contains the amount of UpLink GTP packages Possible values Field exists in the database Table 245 UL_Packets Sgsn_Gtp_Stat_UL_Packets Field name Sgsn_Gtp_Stat_Wynona_Overl_Data Datatype in IDS UINT32 SGSN version >=SG3 Explanation This field contains value of overload data from wynona. In case of a unit overload. Possible values 0x0-0xFFFFFFFF Field exists in the database UL_Packets Table 246 Sgsn_Gtp_Stat_Wynona_Overl_Data Field name Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_1 Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in bytes in DL on Iu-Interface. Priority Class 1 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Ul_Iu_Gtp_Bytes_Pc_1 Table 249 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_1 Field name Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_1 Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in packets in UL on Iu-Interface. Priority Class 1 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Drop_Iu_Gtp_Packets_Pc_1 Table 251 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_1 Field name Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_1 Datatype in IDS UINT32 SGSN version >=SG6 Explanation Dropped GTP Data bytes on Iu-Interface. Priority Class 1 Table 252 338 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_1 Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG6 Explanation GTP Data in packets in DL on Iu-Interface. Priority Class 1 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Dl_Iu_Gtp_Packets_Pc_1 Table 248 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_1 (Cont. Priority Class 1 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Ul_Iu_Gtp_Packets_Pc_1 Table 250 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_1 Field name Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_1 Datatype in IDS UINT32 SGSN version >=SG6 Explanation Dropped GTP Data packets on Iu-Interface.) Field name Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_1 Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in bytes in UL on Iu-Interface. Priority Class 2 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Ul_Iu_Gtp_Bytes_Pc_2 Table 255 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_2 Field name Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_2 Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in packets in UL on Iu-Interface.) Field name Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_2 Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in bytes in DL on Iu-Interface. Priority Class 2 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Dl_Iu_Gtp_Bytes_Pc_2 Table 253 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_2 Field name Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_2 Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in packets in DL on Iu-Interface. Priority Class 2 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Ul_Iu_Gtp_Packets_Pc_2 Table 256 RTT report descriptions Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_2 DN05148836 Issue 2-2 Id:0900d805809551ce 339 . Priority Class 2 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Dl_Iu_Gtp_Packets_Pc_2 Table 254 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_2 Field name Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_2 Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in bytes in UL on Iu-Interface.Traffica Reference Guide for SGSN Direct Interface Possible values 0x1 – 0xFFFFFFFF Field exists in the database Drop_Iu_Gtp_Bytes_Pc_1 Table 252 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_1 (Cont. Priority Class 2 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Drop_Iu_Gtp_Bytes_Pc_2 Table 258 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_2 Field name Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_3 Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in bytes in DL on Iu-Interface.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_2 Datatype in IDS UINT32 SGSN version >=SG6 Explanation Dropped GTP Data packets on Iu-Interface. Priority Class 2 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Drop_Iu_Gtp_Packets_Pc_2 Table 257 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_2 Field name Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_2 Datatype in IDS UINT32 SGSN version >=SG6 Explanation Dropped GTP Data bytes on Iu-Interface. Priority Class 3 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Dl_Iu_Gtp_Packets_Pc_3 Table 260 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_3 Field name Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_3 Datatype in IDS UINT32 Table 261 340 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_3 Id:0900d805809551ce DN05148836 Issue 2-2 . Priority Class 3 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Dl_Iu_Gtp_Bytes_Pc_3 Table 259 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_3 Field name Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_3 Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in packets in DL on Iu-Interface. Priority Class 3 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Drop_Iu_Gtp_Packets_Pc_3 Table 263 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_3 Field name Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_3 Datatype in IDS UINT32 SGSN version >=SG6 Explanation Dropped GTP Data bytes on Iu-Interface. Priority Class 3 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Ul_Iu_Gtp_Bytes_Pc_3 Table 261 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_3 (Cont.Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG6 Explanation GTP Data in bytes in UL on Iu-Interface. Priority Class 3 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Drop_Iu_Gtp_Bytes_Pc_3 Table 264 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_3 Field name Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_4 Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in bytes in DL on Iu-Interface.) Field name Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_3 Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in packets in UL on Iu-Interface. Priority Class 3 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Ul_Iu_Gtp_Packets_Pc_3 Table 262 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_3 Field name Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_3 Datatype in IDS UINT32 SGSN version >=SG6 Explanation Dropped GTP Data packets on Iu-Interface. Priority Class 4 Table 265 RTT report descriptions Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_4 DN05148836 Issue 2-2 Id:0900d805809551ce 341 . Priority Class 4 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Ul_Iu_Gtp_Bytes_Pc_4 Table 267 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_4 Field name Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_4 Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in packets in UL on Iu-Interface. Priority Class 4 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Drop_Iu_Gtp_Packets_Pc_4 Table 269 342 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_4 Id:0900d805809551ce DN05148836 Issue 2-2 .) Field name Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_4 Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in packets in DL on Iu-Interface.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Possible values 0x1 – 0xFFFFFFFF Field exists in the database Dl_Iu_Gtp_Bytes_Pc_4 Table 265 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_4 (Cont. Priority Class 4 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Dl_Iu_Gtp_Packets_Pc_4 Table 266 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_4 Field name Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_4 Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in bytes in UL on Iu-Interface. Priority Class 4 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Ul_Iu_Gtp_Packets_Pc_4 Table 268 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_4 Field name Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_4 Datatype in IDS UINT32 SGSN version >=SG6 Explanation Dropped GTP Data packets on Iu-Interface. Priority Class Streaming Possible values 0x1 – 0xFFFFFFFF Field exists in the database Dl_Iu_Gtp_Bytes_Pc_Str Table 271 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_Str Field name Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_Str Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in packets in DL on Iu-Interface. Priority Class 4 Possible values 0x1 – 0xFFFFFFFF Field exists in the database Drop_Iu_Gtp_Bytes_Pc_4 Table 270 RTT report descriptions Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_4 Field name Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_Str Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in bytes in DL on Iu-Interface. Priority Class Streaming Possible values 0x1 – 0xFFFFFFFF Field exists in the database Dl_Iu_Gtp_Packets_Pc_Str Table 272 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_Str Field name Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_Str Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in bytes in UL on Iu-Interface.Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_4 Datatype in IDS UINT32 SGSN version >=SG6 Explanation Dropped GTP Data bytes on Iu-Interface. Priority Class Streaming Possible values 0x1 – 0xFFFFFFFF Field exists in the database Ul_Iu_Gtp_Bytes_Pc_Str Table 273 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_Str Field name Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_Str Datatype in IDS UINT32 Table 274 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_Str DN05148836 Issue 2-2 Id:0900d805809551ce 343 . Priority Class Streaming Possible values 0x1 – 0xFFFFFFFF Field exists in the database Drop_Iu_Gtp_Packets_Pc_Str Table 275 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_Str Field name Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_Str Datatype in IDS UINT32 SGSN version >=SG6 Explanation Dropped GTP Data bytes on Iu-Interface. Priority Class Conversational Table 278 344 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_Con Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG6 Explanation GTP Data in packets in UL on Iu-Interface.) Field name Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_Str Datatype in IDS UINT32 SGSN version >=SG6 Explanation Dropped GTP Data packets on Iu-Interface. Priority Class Streaming Possible values 0x1 – 0xFFFFFFFF Field exists in the database Drop_Iu_Gtp_Bytes_Pc_Str Table 276 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_Str Field name Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_Con Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in bytes in DL on Iu-Interface. Priority Class Conversational Possible values 0x1 – 0xFFFFFFFF Field exists in the database Dl_Iu_Gtp_Bytes_Pc_Con Table 277 Sgsn_Gtp_Stat_Dl_Iu_Gtp_Bytes_Pc_Con Field name Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_Con Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in packets in DL on Iu-Interface. Priority Class Streaming Possible values 0x1 – 0xFFFFFFFF Field exists in the database Ul_Iu_Gtp_Packets_Pc_Str Table 274 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_Str (Cont. Priority Class Conversational Possible values 0x1 – 0xFFFFFFFF Field exists in the database Drop_Iu_Gtp_Bytes_Pc_Con Table 282 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_Con DN05148836 Issue 2-2 Id:0900d805809551ce 345 . Priority Class Conversational Possible values 0x1 – 0xFFFFFFFF Field exists in the database Ul_Iu_Gtp_Bytes_Pc_Con Table 279 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_Con Field name Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_Con Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in packets in UL on Iu-Interface.Traffica Reference Guide for SGSN Direct Interface Possible values 0x1 – 0xFFFFFFFF Field exists in the database Dl_Iu_Gtp_Bytes_Pc_Con Table 278 RTT report descriptions Sgsn_Gtp_Stat_Dl_Iu_Gtp_Packets_Pc_Con (Cont. Priority Class Conversational Possible values 0x1 – 0xFFFFFFFF Field exists in the database Drop_Iu_Gtp_Packets_Pc_Con Table 281 Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_Con Field name Sgsn_Gtp_Stat_Drop_Iu_Gtp_Bytes_Pc_Con Datatype in IDS UINT32 SGSN version >=SG6 Explanation Dropped GTP Data bytes on Iu-Interface.) Field name Sgsn_Gtp_Stat_Ul_Iu_Gtp_Bytes_Pc_Con Datatype in IDS UINT32 SGSN version >=SG6 Explanation GTP Data in bytes in UL on Iu-Interface. Priority Class Conversational Possible values 0x1 – 0xFFFFFFFF Field exists in the database Ul_Iu_Gtp_Packets_Pc_Con Table 280 Sgsn_Gtp_Stat_Ul_Iu_Gtp_Packets_Pc_Con Field name Sgsn_Gtp_Stat_Drop_Iu_Gtp_Packets_Pc_Con Datatype in IDS UINT32 SGSN version >=SG6 Explanation Dropped GTP Data packets on Iu-Interface. Possible values 0x1 – 0xFF Field exists in the database Physical_Papu_Id Table 284 Sgsn_Gtp_Stat_Physical_Papu_Id Field name Sgsn_Gtp_Stat_Papu_Capa Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains the subscriber capacity of particular PAPU in SGSN. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Dropped_Dl_Bytes Table 283 Sgsn_Gtp_Stat_Dropped_Dl_Bytes Field name Sgsn_Gtp_Stat_Physical_Papu_Id Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains the physical index of PAPU. Possible values 0x41 = maximum of 65 000 attached subscribers 0x64 = maximum of 100 000 attached subscribers 0xFA = maximum of 250 000 attached subscribers Field exists in the database Table 285 Papu_Capa Sgsn_Gtp_Stat_Papu_Capa Field name Sgsn_Gtp_Stat_Papu_Group_Id Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains PAPU group id Possible values 0-255. Large RA Support isn’t activated.Value 0 means that PAPU doesn’t belong to any group Field exists in the database Papu_Group_Id Table 286 346 Sgsn_Gtp_Stat_Papu_Group_Id Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Gtp_Stat_Dropped_Dl_Bytes Datatype in IDS UINT32 SGSN version >=SG6 Explanation Dropped dl bytes due to data throughput limiter per papu. FNSG01060. This field is always 0 if feature. Sgsn_Cdr_Stat_Report_Count IDS field is Report_Count column in database table <SGSN_Release_Id>_CDR_STAT. Under [<SGSN_Release_Id>_CDR_STAT] section. For example.4 RTT report descriptions CDR_STAT fields The following table shows the CDR_STAT fields: Traffic News event type SGSN_CDR_STAT_EVENT Database table <SGSN_Release_Id>_CDR_STAT Table 287 CDR_STAT fields Database column names are the same as IDS fields names without the “Sgsn_Cdr_Stat” prefix. Removed • • • Sgsn_Cdr_Stat_Ave_Rec_Buf_Util_Ratio_Numerator Sgsn_Cdr_Stat_Ave_Rec_Buf_Util_Ratio_Nominator Sgsn_Cdr_Stat_Queue_Len_Peak Field name Sgsn_Cdr_Stat_Discarded_Due_Other Datatype in IDS UINT32 SGSN version >=SG3 Explanation Amount of discarded CDRs because of some other reason Possible values 0x0-0xFFFFFFFF Field exists in the database Yes Table 288 Sgsn_Cdr_Stat_Discarded_Due_Other Field name Sgsn_Cdr_Stat_Discarded_Due_Overflow Datatype in IDS UINT32 SGSN version >=SG3 Explanation Contains the amount of discarded CDRs due to buffer overflow Possible values 0x0-0xFFFFFFFF Field exists in the database Discarded_Due_Overflow Table 289 Sgsn_Cdr_Stat_Discarded_Due_Overflow DN05148836 Issue 2-2 Id:0900d805809551ce 347 .Traffica Reference Guide for SGSN Direct Interface 6. Sgsn_Cdr_Stat_Report_Count IDS field is Report Count field in Traffic News' SGSN_CDR_STAT_EVENT. For example. there is a single-row entry for each table column. Changes in SG3 The following list shows what has been removed from CDR_STAT fields. Database column SQL datatypes can be found in the workspace configuration file dbd_sgsn_cdr_stat. The SQL datatype appears after the column name and '=' sign. Traffic News field names are the same as database column names with spaces used instead of underscores between words.conf. i. 3=MT-SMS-CDR Field exists in the database Id Table 291 Sgsn_Cdr_Stat_Id Field name Sgsn_Cdr_Stat_Received_Cdrs Datatype in IDS UINT32 SGSN version >=SG3 Explanation Number of CDRs generated.e. 1=M-CDR. 2=MO-SMS-CDR. received from charging collection entity Possible values 0x0-0xFFFFFFFF Field exists in the database Yes Table 293 348 Sgsn_Cdr_Stat_Received_Pp_Cdrs Id:0900d805809551ce DN05148836 Issue 2-2 .m. Possible values 0x0-0xFFFFFFFF Field exists in the database Event_Count Table 290 Sgsn_Cdr_Stat_Event_Count Field name Sgsn_Cdr_Stat_Id Datatype in IDS UINT8 SGSN version >=SG3 Explanation This field contains identity of CDR-type Possible values 0=S-CDR. i. The counter is reset at 00:00 a.e.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Cdr_Stat_Event_Count Datatype in IDS UINT32 SGSN version >=SG3 Explanation Contains information on how many events of this type have been detected whether they have been sent to Traffica or not. received from charging collection entity Possible values 0x0-0xFFFFFFFF Field exists in the database Received_Cdrs Table 292 Sgsn_Cdr_Stat_Received_Cdrs Field name Sgsn_Cdr_Stat_Received_Pp_Cdrs Datatype in IDS UINT32 SGSN version >=SG3 Explanation Number of prepaid CDRs generated. m. The value of this counter resets daily at 00:00 a. Sgsn_Cdr_Stat_Report_Time and Sgsn_Cdr_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time. Possible values 0x0-0xFFFFFFFF Field exists in the database Yes. Possible values 0x0204 (You should avoid using this field in CCMA. Table 295 Sgsn_Cdr_Stat_Report_Date Field name Sgsn_Cdr_Stat_Report_Id Datatype in IDS UINT16 SGSN version >=SG3 Explanation Contains information on the report type. Possible values 0x0-0xFFFFFFFF Field exists in the database Yes. NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field. Possible values 0x0-0xFFFFFFFF Field exists in the database Report_Count Table 294 Sgsn_Cdr_Stat_Report_Count Field name Sgsn_Cdr_Stat_Report_Date Datatype in IDS BCDDATE SGSN version >=SG3 Explanation Contains the date when the report was sent to Traffica. Field exists in the database Report_Id Table 296 Sgsn_Cdr_Stat_Report_Id Field name Sgsn_Cdr_Stat_Report_Time Datatype in IDS BCDTIME SGSN version >=SG3 Explanation Contains the time when the report was sent to Traffica. because the possible values can and will change in the future. because the value might change in future SGSN releases).Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Cdr_Stat_Report_Count Datatype in IDS UINT32 SGSN version >=SG3 Explanation Contains information on how many reports of this type have been sent to Traffica. Sgsn_Cdr_Stat_Report_Time and Sgsn_Cdr_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Table 297 Sgsn_Cdr_Stat_Report_Time DN05148836 Issue 2-2 Id:0900d805809551ce 349 . GIGPRBs send buffer is full and GIGPRB is not able to receive new CDRs from GCHPRB Possible values 0x1 – 0xFFFFFFFF Field exists in the database Discarded_Gb_M_Cdrs Table 300 Sgsn_Cdr_Stat_Discarded_Gb_M_Cdrs Field name Sgsn_Cdr_Stat_Discarded_Gb_Smo_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation GCHPRB's CDR statistics counter: number of discarded SMO-CDRs for Gb -interface because of active overload control in CDR sending. GIGPRBs send buffer is full and GIGPRB is not able to receive new CDRs from GCHPRB Possible values 0x1 – 0xFFFFFFFF Table 301 350 Sgsn_Cdr_Stat_Discarded_Gb_Smo_Cdrs Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Cdr_Stat_Resendings Datatype in IDS UINT32 SGSN version >=SG3 Explanation Number of CDRs resent to the charging gateway. Possible values 0x0-0xFFFFFFFF Field exists in the database Resendings Table 298 Sgsn_Cdr_Stat_Resendings Field name Sgsn_Cdr_Stat_Discarded_Gb_S_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation GCHPRB's CDR statistics counter: number of discarded S-CDRs for Gb -interface because of active overload control in CDR sending. GIGPRBs send buffer is full and GIGPRB is not able to receive new CDRs from GCHPRB Possible values 0x1 – 0xFFFFFFFF Field exists in the database Discarded_Gb_S_Cdrs Table 299 Sgsn_Cdr_Stat_Discarded_Gb_S_Cdrs Field name Sgsn_Cdr_Stat_Discarded_Gb_M_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation GCHPRB's CDR statistics counter: number of discarded M-CDRs for Gb -interface because of active overload control in CDR sending. GIGPRBs send buffer is full and GIGPRB is not able to receive new CDRs from GCHPRB Possible values 0x1 – 0xFFFFFFFF Field exists in the database Discarded_Iu_S_Cdrs Table 303 Sgsn_Cdr_Stat_Discarded_Iu_S_Cdrs Field name Sgsn_Cdr_Stat_Discarded_Iu_M_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation GCHPRB's CDR statistics counter: number of discarded M-CDRs for Iu interface because of active overload control in CDR sending.Traffica Reference Guide for SGSN Direct Interface Field exists in the database Table 301 RTT report descriptions Discarded_Gb_Smo_Cdrs Sgsn_Cdr_Stat_Discarded_Gb_Smo_Cdrs (Cont.) Field name Sgsn_Cdr_Stat_Discarded_Gb_Smt_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation GCHPRB's CDR statistics counter: number of discarded SMT-CDRs for Gb -interface because of active overload control in CDR sending. GIGPRBs send buffer is full and GIGPRB is not able to receive new CDRs from GCHPRB Possible values 0x1 – 0xFFFFFFFF Field exists in the database Discarded_Gb_Smt_Cdrs Table 302 Sgsn_Cdr_Stat_Discarded_Gb_Smt_Cdrs Field name Sgsn_Cdr_Stat_Discarded_Iu_S_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation GCHPRB's CDR statistics counter: number of discarded S-CDRs for Iu interface because of active overload control in CDR sending. GIGPRBs send buffer is full and GIGPRB is not able to receive new CDRs from GCHPRB Possible values 0x1 – 0xFFFFFFFF Field exists in the database Discarded_Iu_M_Cdrs Table 304 Sgsn_Cdr_Stat_Discarded_Iu_M_Cdrs Field name Sgsn_Cdr_Stat_Discarded_Iu_Smo_Cdrs Datatype in IDS UINT32 Table 305 Sgsn_Cdr_Stat_Discarded_Iu_Smo_Cdrs DN05148836 Issue 2-2 Id:0900d805809551ce 351 . ) Field name Sgsn_Cdr_Stat_Discarded_Iu_Smt_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation GCHPRB's CDR statistics counter: number of discarded SMT-CDRs for Iu -interface because of active overload control in CDR sending. GIGPRBs send buffer is full and GIGPRB is not able to receive new CDRs from GCHPRB Possible values 0x1 – 0xFFFFFFFF Field exists in the database Discarded_Iu_Smo_Cdrs Table 305 Sgsn_Cdr_Stat_Discarded_Iu_Smo_Cdrs (Cont. GIGPRBs send buffer is full and GIGPRB is not able to receive new CDRs from GCHPRB Possible values 0x1 – 0xFFFFFFFF Field exists in the database Discarded_Iu_Smt_Cdrs Table 306 Sgsn_Cdr_Stat_Discarded_Iu_Smt_Cdrs Field name Sgsn_Cdr_Stat_M_Cdr_Duration_Sum Datatype in IDS UINT32 SGSN version >=SG6 Explanation Total duration of all M-CDRs closed during the measurement period Possible values 0x1 – 0xFFFFFFFF Field exists in the database M_Cdr_Duration_Sum Table 307 Sgsn_Cdr_Stat_M_Cdr_Duration_Sum Field name Sgsn_Cdr_Stat_M_Cdr_Duration_Den Datatype in IDS UINT32 SGSN version >=SG6 Explanation Total amount of all M-CDRs closed during the measurement period Possible values 0x1 – 0xFFFFFFFF Field exists in the database M_Cdr_Duration_Den Table 308 Field name Table 309 352 Sgsn_Cdr_Stat_M_Cdr_Duration_Den Sgsn_Cdr_Stat_S_Cdr_Non_Rt_Duration_Sum Sgsn_Cdr_Stat_S_Cdr_Non_Rt_Duration_Sum Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG6 Explanation GCHPRB's CDR statistics counter: number of discarded SMO-CDRs for Iu -interface because of active overload control in CDR sending. Possible values Field exists in the database Table 312 S_Cdr_Rt_Duration_Sum Sgsn_Cdr_Stat_S_Cdr_Rt_Duration_Sum 6.) Field name Sgsn_Cdr_Stat_S_Cdr_Non_Rt_Duration_Den Datatype in IDS UINT32 SGSN version >=SG6 Explanation Total amount of all non real-time S-CDRs closed during the measurement period Possible values 0x1 – 0xFFFFFFFF Field exists in the database S_Cdr_Non_Rt_Duration_Den Table 310 Sgsn_Cdr_Stat_S_Cdr_Non_Rt_Duration_Den Field name Sgsn_Cdr_Stat_S_Cdr_Rt_Duration_Den Datatype in IDS UINT32 SGSN version >=SG6 Explanation Total duration of all real-time S-CDRs closed during the measurement period Possible values 0x1 – 0xFFFFFFFF Field exists in the database S_Cdr_Rt_Duration_Den Table 311 Sgsn_Cdr_Stat_S_Cdr_Rt_Duration_Den Field name Sgsn_Cdr_Stat_S_Cdr_Rt_Duration_Sum Datatype in IDS UINT32 SGSN version >=SG6 Explanation Total amount of all real-time S-CDRs closed during the measurement period.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Datatype in IDS UINT32 SGSN version >=SG6 Explanation Total duration of all non real-time S-CDRs closed during the measurement period Possible values 0x1 – 0xFFFFFFFF Field exists in the database S_Cdr_Non_Rt_Duration_Sum Table 309 Sgsn_Cdr_Stat_S_Cdr_Non_Rt_Duration_Sum (Cont.5 LOA_STAT fields The following table shows the LOA_STAT fields: DN05148836 Issue 2-2 Id:0900d805809551ce 353 . conf. the Sgsn_LOA_STAT_Report_Count IDS field is Report Count field in Traffic News SGSN_LOA_STAT_EVENT. first 4 characters. The database column SQL datatypes can be found in the workspace configuration file dbd_sgsn_loa_stat. For example. Field name Sgsn_Loa_Stat_Ave_Load_Rate_Sum Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the average load rate percentage of the object unit processor. Possible values Always 1 (as this is the value sent by the SGSN element to Traffica) Field exists in the database Ave_Load_Rate_Den Table 315 Sgsn_Loa_Stat_Ave_Load_Rate_Den Field name Sgsn_Loa_Stat_Objectname1 Datatype in IDS CHAR(4) SGSN version >=SG4 Explanation This field contains the name of the measured object unit. Possible values 0-100 Field exists in the database Ave_Load_Rate_Sum Table 314 Sgsn_Loa_Stat_Ave_Load_Rate_Sum Field name Sgsn_Loa_Stat_Ave_Load_Rate_Den Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the average object unit processor load rate.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Traffic News event type SGSN_LOA_STAT_EVENT Database table <SGSN_Release_Id>_LOA_STAT Table 313 SGSN_LOA_STAT fields The database column names are the same as the IDS field names without the Sgsn_LOA_STAT prefix. Table 316 354 Sgsn_Loa_Stat_Objectname1 Id:0900d805809551ce DN05148836 Issue 2-2 . For example. The SQL datatype appears after the column name and “=” symbol. the Sgsn_LOA_STAT_Report_Count IDS field is the Report_Count column in database table <SGSN_Release_Id>_LOA_STAT. there is a single-row entry for each table column. The Traffic News field names are the same as the database column names but use spaces instead of underscores between words. Under the <SGSN_Release_Id>_LOA_STAT section. ) Field name Sgsn_Loa_Stat_Objectname2 Datatype in IDS CHAR(4) SGSN version >=SG4 Explanation This field contains the name of the measured object unit. Possible values Coded in Binary Coded Decimal (BCD): Day: byte Month: byte Year: word Hundredths of seconds: byte Seconds: byte Minutes: byte Hours: byte Field exists in the database Table 319 Peak_Time Sgsn_Loa_Stat_Peak_Time_Hours DN05148836 Issue 2-2 Id:0900d805809551ce 355 . last 4 characters. Field exists in the database Objectname2 Table 317 Sgsn_Loa_Stat_Objectname2 Field name Sgsn_Loa_Stat_Peak_Load_Rate Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the peak load rate percentage of the object unit processor. Possible values 0-100 Field exists in the database Peak_Load_Rate Table 318 Sgsn_Loa_Stat_Peak_Load_Rate Field name Sgsn_Loa_Stat_Peak_Time_Hours Datatype in IDS BCDTIME SGSN version >=SG4 Explanation This field contains the peak load time of the processor within a measurement period.Traffica Reference Guide for SGSN Direct Interface Possible values Empty fields are filled with 0x20 (=end of the string). Possible values Empty fields are filled with 0x20 (=end of the string). Field exists in the database Objectname1 Table 316 RTT report descriptions Sgsn_Loa_Stat_Objectname1 (Cont. Possible values 0x0-0xFFFFFFFF Field exists in the database Report_Count Table 321 Sgsn_Loa_Stat_Report_Count Field name Sgsn_Loa_Stat_Report_Date Datatype in IDS BCDDATE SGSN version >=SG4 Explanation The date when the report was sent to Traffica.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Loa_Stat_Peak_Time_Days Datatype in IDS BCDDATE SGSN version >=SG4 Explanation This field contains the peak load time of the processor within a measurement period. Possible values Field exists in the database Table 322 Sgsn_Loa_Stat_Report_Time and Sgsn_Loa_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Sgsn_Loa_Stat_Report_Date Field name Sgsn_Loa_Stat_Report_Id Datatype in IDS UINT16 Table 323 356 Sgsn_Loa_Stat_Report_Id Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values Coded in Binary Coded Decimal (BCD): Day: byte Month: byte Year: word Hundredths of seconds: byte Seconds: byte Minutes: byte Hours: byte Field exists in the database Table 320 Peak_Time Sgsn_Loa_Stat_Peak_Time_Days Field name Sgsn_Loa_Stat_Report_Count Datatype in IDS UINT32 SGSN version >=SG4 Explanation Contains information on how many reports of this type have been sent to Traffica. integer value. Possible values 0x00 . because the possible values can and will change in the future.) Field name Sgsn_Loa_Stat_Report_Time Datatype in IDS BCDTIME SGSN version >=SG4 Explanation The time when the report was sent to Traffica.Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG4 Explanation Contains information on the report type.0xFFFF FFFF Field exists in the database Unit_Index Table 326 Sgsn_Loa_Stat_Unit_Index Field name Sgsn_Loa_Stat_Unit_State Datatype in IDS UINT32 Table 327 Sgsn_Loa_Stat_Unit_State DN05148836 Issue 2-2 Id:0900d805809551ce 357 . RTT report descriptions NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field. Possible values 0x0 .0x FFFF FFFF Field exists in the database Succ_Samples Table 325 Sgsn_Loa_Stat_Succ_Samples Field name Sgsn_Loa_Stat_Unit_Index Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the index of the object unit. Possible values 0x020F Field exists in the database Report_Id Table 323 Sgsn_Loa_Stat_Report_Id (Cont. Possible values 0x0-0xFFFFFFFF Field exists in the database Sgsn_Loa_Stat_Report_Time and Sgsn_Loa_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Table 324 Sgsn_Loa_Stat_Report_Time Field name Sgsn_Loa_Stat_Succ_Samples Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the number of successful samples of the load rate. the Sgsn_NSVC_STAT_Report_Count IDS field is the Report_Count column in database table <SGSN_Release_Id>_NSVC_STAT. For example. the Sgsn_NSVC_STAT_Report_Count IDS field is Report Count field in Traffic News SGSN_NSVC_STAT_EVENT. there is a single-row entry for each table column. Possible values 0x0210 Field exists in the database Report_Id Table 329 Sgsn_Nsvc_Stat_Report_Id Field name Sgsn_Nsvc_Stat_Report_Count Datatype in IDS UINT32 Table 330 358 Sgsn_Nsvc_Stat_Report_Count Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG4 Explanation This field contains state of the object unit.) 6.conf. For example. NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field. Under the <SGSN_Release_Id>_NSVC_STAT section.6 NSVC_STAT fields The following table shows the NSVC_STAT fields: Traffic News event type SGSN_NSVC_STAT_EVENT Database table <SGSN_Release_Id>_NSVC_STAT Table 328 SGSN_NSVC_STAT fields The database column names are the same as the IDS field names without the Sgsn_NSVC_STAT prefix. The Traffic News field names are the same as the database column names but use spaces instead of underscores between words. because the possible values can and will change in the future. Possible values 00 = WO-EX (working executing state) 37 = SP-EX (spare executing state) Field exists in the database Table 327 Unit_State Sgsn_Loa_Stat_Unit_State (Cont. The SQL datatype appears after the column name and “=” symbol. Field name Sgsn_Nsvc_Stat_Report_Id Datatype in IDS UINT16 SGSN version >=SG4 Explanation Contains information on the report type. The database column SQL datatypes can be found in the workspace configuration file dbd_sgsn_nsvc_stat. Possible values 0 . Possible values 0x0 . Possible values 0x0-0xFFFFFFFF Field exists in the database Sgsn_Nsvc_Stat_Report_Time and Sgsn_Nsvc_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Table 331 Sgsn_Nsvc_Stat_Report_Date Field name Sgsn_Nsvc_Stat_Report_Time Datatype in IDS BCDTIME SGSN version >=SG4 Explanation The time when the report was sent to Traffica. The value of the counter is reset every day at 00:00 a.0xFFFFFFFF) Field exists in the database Report_Count Table 330 Sgsn_Nsvc_Stat_Report_Count (Cont.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions SGSN version >=SG4 Explanation Contains information on how many reports of this type have been sent to Traffica.0xFFFF Field exists in the database Report_Length Table 333 Sgsn_Nsvc_Stat_Report_Length Field name Table 334 Sgsn_Nsvc_Stat_Papu_Id Sgsn_Nsvc_Stat_Papu_Id DN05148836 Issue 2-2 Id:0900d805809551ce 359 . Possible values 0x0-0xFFFFFFFF Field exists in the database Sgsn_Nsvc_Stat_Report_Time and Sgsn_Nsvc_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Table 332 Sgsn_Nsvc_Stat_Report_Time Field name Sgsn_Nsvc_Stat_Report_Length Datatype in IDS UINT16 SGSN version >=SG4 Explanation This field contains the length of report in bytes.) Field name Sgsn_Nsvc_Stat_Report_Date Datatype in IDS BCDDATE SGSN version >=SG4 Explanation The date when the report was sent to Traffica. This field is needed because empty cells are dropped from nsvc_table.4 294 967 296 (0x0 .m. ) Field name Sgsn_Nsvc_Stat_Physical_Papu_Id Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the physical index of papu. Field exists in the database Table 335 Physical_Papu_Id Sgsn_Nsvc_Stat_Physical_Papu_Id Field name Sgsn_Nsvc_Stat_Papu_Capa Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the subscriber capacity of a particular PAPU in SGSN. Possible values 0x0 . Possible values 0x41 = maximum of 65 000 attached subscribers 0x64 = maximum of 100 000 attached subscribers 0xFA = maximum of 250 000 attached subscribers Field exists in the database Table 336 Papu_Capa Sgsn_Nsvc_Stat_Papu_Capa Field name Sgsn_Nsvc_Stat_Papu_Group_Id Datatype in IDS BCDTIME SGSN version >=SG4 Explanation This field contains PAPU group id. Value 0 means that PAPU does not belong to any group Field exists in the database Table 337 360 Papu_Group_Id Sgsn_Nsvc_Stat_Papu_Group_Id Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains identity of papu.0xFF Field exists in the database Papu_Id Table 334 Sgsn_Nsvc_Stat_Papu_Id (Cont. Possible values 0-255 This field is always 0 if feature. Possible values 0x0 .0xFF Value 0x28 is used if physical papu id cannot be solved due some internal error. Large RA Support is not activated. 0xFFFF Field exists in the database Nsei Table 340 Sgsn_Nsvc_Stat_Nsei Field name Sgsn_Nsvc_Stat_Ns_Vci Datatype in IDS UINT16 SGSN version >=SG4 Explanation NSVC indentifier Possible values 0x0 . Possible values 0x0 .0xFFFF Field exists in the database Nse_Count Table 338 Sgsn_Nsvc_Stat_Nse_Count Field name Sgsn_Nsvc_Stat_Nsvc_Count Datatype in IDS UINT16 SGSN version >=SG4 Explanation The number of NSVC elements in actual use.0xFFFF Field exists in the database Ns_Vci Table 341 Sgsn_Nsvc_Stat_Ns_Vci Field name Sgsn_Nsvc_Stat_Fr_Passed_Data_In_Bytes Datatype in IDS UINT32 Table 342 RTT report descriptions Sgsn_Nsvc_Stat_Fr_Passed_Data_In_Bytes DN05148836 Issue 2-2 Id:0900d805809551ce 361 .Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Nsvc_Stat_Nse_Count Datatype in IDS UINT16 SGSN version >=SG4 Explanation Count of NSE elements in actual use. Possible values 0x0 .0xFFFF Field exists in the database Nsvc_Count Table 339 Sgsn_Nsvc_Stat_Nsvc_Count Field name Sgsn_Nsvc_Stat_Nsei Datatype in IDS UINT16 SGSN version >=SG4 Explanation NSE indentifier Possible values 0x0 . Possible values 0x0 .0xFFFF FFFF Field exists in the database Fr_Passed_Data_In_Bytes Table 342 Sgsn_Nsvc_Stat_Fr_Passed_Data_In_Bytes (Cont.0xFFFF FFFF Field exists in the database Disc_Due_Cir_Overflow Table 343 Sgsn_Nsvc_Stat_Disc_Due_Cir_Overflow Field name Sgsn_Nsvc_Stat_Ip_Passed_Data_In_Bytes Datatype in IDS UINT32 SGSN version >=SG4 Explanation Data in bytes which has passed IP NSVC control Possible values 0x0 . Possible values 0x0 .) Field name Sgsn_Nsvc_Stat_Disc_Due_Cir_Overflow Datatype in IDS UINT32 SGSN version >=SG4 Explanation Discarded packets due CIR overflow Possible values 0x0 .RTT report descriptions Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG4 Explanation Data in bytes which has passed frame relay NSVC control.0xFFFF FFFF Field exists in the database Ip_Passed_Data_In_Bytes Table 344 Sgsn_Nsvc_Stat_Ip_Passed_Data_In_Bytes Field name Sgsn_Nsvc_Stat_Ig_Fr_Shared_Data_In_Bytes Datatype in IDS UINT32 SGSN version >=SG4 Explanation Data in bytes borrowed from another fr NSVC control. Table 346 362 Sgsn_Nsvc_Stat_Og_Fr_Shared_Data_In_Bytes Id:0900d805809551ce DN05148836 Issue 2-2 .0xFFFF FFFF Field exists in the database Ig_Fr_Shared_Data_In_Bytes Table 345 Sgsn_Nsvc_Stat_Ig_Fr_Shared_Data_In_Bytes Field name Sgsn_Nsvc_Stat_Og_Fr_Shared_Data_In_Bytes Datatype in IDS UINT32 SGSN version >=SG4 Explanation Data in bytes borrowed to another fr NSVC control. Value T in this field indicates that it is the last report.) Field name Sgsn_Sequence_Nr Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the sequence number of response message.0xFFFF FFFF Field exists in the database Og_Fr_Shared_Data_In_Bytes Table 346 RTT report descriptions Sgsn_Nsvc_Stat_Og_Fr_Shared_Data_In_Bytes (Cont. Possible values 1 -10 Table 347 Sgsn_Sequence_Nr Field name Sgsn_Last_message Datatype in IDS UINT8 SGSN version >=SG4 Explanation Because the maximum number of cells per PAPU is 3000. numbering starts from 1. counters of all cells don't necessarily fit to one report. Possible values 0-1 Table 348 Sgsn_Last_message Field name Sgsn_Nsvc_Stat_Upload_Data_In_Bytes Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC upload data in bytes Possible values 0x1 – 0xFFFF Field exists in the database Upload_Data_In_Bytes Table 349 Sgsn_Nsvc_Stat_Upload_Data_In_Bytes Field name Sgsn_Nsvc_Stat_Upload_Data_In_Pack Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC download data in bytes Possible values 0x1 – 0xFFFF Field exists in the database Upload_Data_In_Pack Table 350 Sgsn_Nsvc_Stat_Upload_Data_In_Pack DN05148836 Issue 2-2 Id:0900d805809551ce 363 .Traffica Reference Guide for SGSN Direct Interface Possible values 0x0 . Maximum number of needed SGSN_BSSGP_CELL_STAT reports per papu is 10. RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Pr1 Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC passed data in bytes in priority class 1 Possible values 0x1 – 0xFFFF Field exists in the database Pas_Data_In_Bytes_Pr1 Table 351 Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Pr1 Field name Sgsn_Nsvc_Stat_Pas_Data_In_Pack_Pr1 Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC passed data in packets in priority class 1 Possible values 0x1 – 0xFFFF Field exists in the database Pas_Data_In_Pack_Pr1 Table 352 Sgsn_Nsvc_Stat_Pas_Data_In_Pack_Pr1 Field name Sgsn_Nsvc_Stat_Disc_Data_In_Bytes_Pr1 Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC discarded data in bytes in priority class 1 Possible values 0x1 – 0xFFFF Field exists in the database Disc_Data_In_Bytes_Pr1 Table 353 Sgsn_Nsvc_Stat_Disc_Data_In_Bytes_Pr1 Field name Sgsn_Nsvc_Stat_Disc_Data_In_Pack_Pr1 Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC discarded data in packets in priority class 1 Possible values 0x1 – 0xFFFF Field exists in the database Disc_Data_In_Pack_Pr1 Table 354 Sgsn_Nsvc_Stat_Disc_Data_In_Pack_Pr1 Field name Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Pr2 Datatype in IDS UINT32 Table 355 364 Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Pr2 Id:0900d805809551ce DN05148836 Issue 2-2 . ) Field name Sgsn_Nsvc_Stat_Pas_Data_In_Pack_Pr2 Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC passed data in packets in priority class 2' Possible values 0x1 – 0xFFFF Field exists in the database Pas_Data_In_Pack_Pr2 Table 356 Sgsn_Nsvc_Stat_Pas_Data_In_Pack_Pr2 Field name Sgsn_Nsvc_Stat_Disc_Data_In_Bytes_Pr2 Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC discarded data in bytes in priority class 2 Possible values 0x1 – 0xFFFF Field exists in the database Disc_Data_In_Bytes_Pr2 Table 357 Sgsn_Nsvc_Stat_Disc_Data_In_Bytes_Pr2 Field name Sgsn_Nsvc_Stat_Disc_Data_In_Pack_Pr2 Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC discarded data in packets in priority class 2 Possible values 0x1 – 0xFFFF Field exists in the database Disc_Data_In_Pack_Pr2 Table 358 Sgsn_Nsvc_Stat_Disc_Data_In_Pack_Pr2 Field name Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Pr3 Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC passed data in bytes in priority class 3 Table 359 RTT report descriptions Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Pr3 DN05148836 Issue 2-2 Id:0900d805809551ce 365 .Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG6 Explanation NS-VC passed data in bytes in priority class 2 Possible values 0x1 – 0xFFFF Field exists in the database Pas_Data_In_Bytes_Pr2 Table 355 Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Pr2 (Cont. ) Field name Sgsn_Nsvc_Stat_Pas_Data_In_Pack_Pr3 Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC passed data in packets in priority class 3' Possible values 0x1 – 0xFFFF Field exists in the database Pas_Data_In_Pack_Pr3 Table 360 Sgsn_Nsvc_Stat_Pas_Data_In_Pack_Pr3 Field name Sgsn_Nsvc_Stat_Disc_Data_In_Bytes_Pr3 Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC discarded data in bytes in priority class 3 Possible values 0x1 – 0xFFFF Field exists in the database Disc_Data_In_Bytes_Pr3 Table 361 Sgsn_Nsvc_Stat_Disc_Data_In_Bytes_Pr3 Field name Sgsn_Nsvc_Stat_Disc_Data_In_Pack_Pr3 Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC discarded data in packets in priority class 3 Possible values 0x1 – 0xFFFF Field exists in the database Disc_Data_In_Pack_Pr3 Table 362 Sgsn_Nsvc_Stat_Disc_Data_In_Pack_Pr3 Field name Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Pr4 Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC passed data in bytes in priority class 4 Possible values 0x1 – 0xFFFF Field exists in the database Pas_Data_In_Bytes_Pr4 Table 363 366 Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Pr4 Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Possible values 0x1 – 0xFFFF Field exists in the database Pas_Data_In_Bytes_Pr3 Table 359 Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Pr3 (Cont. Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Nsvc_Stat_Pas_Data_In_Pack_Pr4 Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC passed data in packets in priority class 4 Possible values 0x1 – 0xFFFF Field exists in the database Pas_Data_In_Pack_Pr4 Table 364 Sgsn_Nsvc_Stat_Pas_Data_In_Pack_Pr4 Field name Sgsn_Nsvc_Stat_Disc_Data_In_Bytes_Pr4 Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC discarded data in bytes in priority class 4 Possible values 0x1 – 0xFFFF Field exists in the database Disc_Data_In_Bytes_Pr Table 365 Sgsn_Nsvc_Stat_Disc_Data_In_Bytes_Pr4 Field name Sgsn_Nsvc_Stat_Disc_Data_In_Pack_Pr4 Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC discarded data in packets in priority class 4 Possible values 0x1 – 0xFFFF Field exists in the database Disc_Data_In_Pack_Pr4 Table 366 Sgsn_Nsvc_Stat_Disc_Data_In_Pack_Pr4 Field name Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Str Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC passed data in bytes in streaming class Possible values 0x1 – 0xFFFF Field exists in the database Pas_Data_In_Bytes_Str Table 367 Sgsn_Nsvc_Stat_Pas_Data_In_Bytes_Str Field name Sgsn_Nsvc_Stat_Pas_Data_In_Pack_Str Datatype in IDS UINT32 Table 368 RTT report descriptions Sgsn_Nsvc_Stat_Pas_Data_In_Pack_Str DN05148836 Issue 2-2 Id:0900d805809551ce 367 . RTT report descriptions Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG6 Explanation NS-VC passed data in packets in streaming class Possible values 0x1 – 0xFFFF Field exists in the database Pas_Data_In_Pack_Str Table 368 Sgsn_Nsvc_Stat_Pas_Data_In_Pack_Str (Cont. The Traffic News field names are the same as the database column names but use spaces instead of underscores between words. For example.) Field name Sgsn_Nsvc_Stat_Disc_Data_In_Bytes_Str Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC discarded data in bytes in streaming class Possible values 0x1 – 0xFFFF Field exists in the database Disc_Data_In_Bytes_Str Table 369 Sgsn_Nsvc_Stat_Disc_Data_In_Bytes_Str Field name Sgsn_Nsvc_Stat_Disc_Data_In_Pack_Str Datatype in IDS UINT32 SGSN version >=SG6 Explanation NS-VC discarded data in packets in streaming class Possible values 0x1 – 0xFFFF Field exists in the database Disc_Data_In_Pack_Str Table 370 Sgsn_Nsvc_Stat_Disc_Data_In_Pack_Str 6.7 BSSGP_CELL_STAT fields The following table shows the BSSGP_CELL_STAT fields: Traffic News event type SGSN_BSSGP_CELL_STAT_EVENT Database table <SGSN_Release_Id>_BSSGP_CELL_S TAT Table 371 SGSN_BSSGP_CELL_STAT fields The database column names are the same as the IDS field names without the Sgsn_NSVC_STAT prefix. the Sgsn_BSSGP_CELL_STAT_Report_Count IDS field is Report Count field in Traffic News SGSN_BSSGP_CELL_STAT_EVENT. For example. the Sgsn_BSSGP_CELL_STAT_Report_Count IDS field is the Report_Count column in database table <SGSN_Release_Id>_BSSGP_CELL_STAT. 368 Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values 0 . Field name Sgsn_Bssgp_Cell_Stat_Report_Id Datatype in IDS UINT16 SGSN version >=SG4 Explanation Contains information on the report type. This field is needed because empty cells are dropped from cell_stat_table. there is a single-row entry for each table column. Under the <SGSN_Release_Id>_BSSGP_CELL_STAT section. because the possible values can and will change in the future. NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field. Possible values 0x0 .m. Possible values 0x0213 Field exists in the database Report_Id Table 372 Sgsn_Bssgp_Cell_Stat_Report_Id Field name Sgsn_Bssgp_Cell_Stat_Report_Count Datatype in IDS UINT32 SGSN version >=SG4 Explanation Contains information on how many reports of this type have been sent to Traffica.4 294 967 296 (0x0 . The SQL datatype appears after the column name and “=” symbol. The value of the counter is reset everyday at 00:00 a.0xFFFF Field exists in the database Report_Length Table 374 Sgsn_Bssgp_Cell_Stat_Report_Length Field name Sgsn_Bssgp_Cell_Stat_Report_Time Datatype in IDS BCDTIME SGSN version >=SG4 Table 375 Sgsn_Bssgp_Cell_Stat_Report_Time DN05148836 Issue 2-2 Id:0900d805809551ce 369 .Traffica Reference Guide for SGSN Direct Interface RTT report descriptions The database column SQL datatypes can be found in the workspace configuration file dbd_sgsn_bssgp_cell_stat.conf.0xFFFFFFFF) Field exists in the database Report_Count Table 373 Sgsn_Bssgp_Cell_Stat_Report_Count Field name Sgsn_Bssgp_Cell_Stat_Report_Length Datatype in IDS BCDDATE SGSN version >=SG4 Explanation This field contains the length of report in bytes. 0xFF Value 0x28 is used if physical papu id cannot be solved due some internal error Field exists in the database Table 378 Physical_Papu_Id Sgsn_Bssgp_Cell_Stat_Physical_Papu_Id Field name Sgsn_Bssgp_Cell_Stat_Last_Message Datatype in IDS UINT8 SGSN version >=SG4 Table 379 370 Sgsn_Bssgp_Cell_Stat_Last_Message Id:0900d805809551ce DN05148836 Issue 2-2 .) Field name Sgsn_Bssgp_Cell_Stat_Report_Date Datatype in IDS BCDDATE SGSN version >=SG4 Explanation The date when the report was sent to Traffica. Possible values 0x0 . Possible values 0x0 .0xFF Field exists in the database Papu_Id Table 377 Sgsn_Bssgp_Cell_Stat_Papu_Id Field name Sgsn_Bssgp_Cell_Stat_Physical_Papu_Id Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the physical index of papu.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Explanation The time when the report was sent to Traffica. Possible values 0x0-0xFFFFFFFF Field exists in the database Sgsn_Nsvc_Stat_Report_Time and Sgsn_Nsvc_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Table 375 Sgsn_Bssgp_Cell_Stat_Report_Time (Cont. Possible values 0x0-0xFFFFFFFF Field exists in the database Sgsn_Nsvc_Stat_Report_Time and Sgsn_Nsvc_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Table 376 Sgsn_Bssgp_Cell_Stat_Report_Date Field name Sgsn_Bssgp_Cell_Stat_Papu_Id Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains identity of papu. Possible values 0-255 This field is always 0 if feature. Possible values 0-1 Field exists in the database Last_Message Table 379 Sgsn_Bssgp_Cell_Stat_Last_Message (Cont.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Explanation Because the maximum number of cells per PAPU is 3000. Possible values 0x41 = maximum of 65 000 attached subscribers 0x64 = maximum of 100 000 attached subscribers 0xFA = maximum of 250 000 attached subscribers Field exists in the database Table 381 Papu_Capa Sgsn_Bssgp_Papu_Cell_Papu_Capa Field name Sgsn_Bssgp_Cell_Stat_Papu_Group_Id Datatype in IDS UINT8 SGSN version SG4 Explanation This field contains the PAPU group id. Large RA Support is not activated. Value T in this field indicates that it is the last report.10 Field exists in the database Sequence_Nr Table 380 Sgsn_Bssgp_Cell_Stat_Sequence_Nr Field name Sgsn_Bssgp_Papu_Cell_Papu_Capa Datatype in IDS UINT16 SGSN version >=SG4 Explanation This field contains the subscriber capacity of particular PAPU in SGSN. numbers starts from 1. Value 0 means that PAPU does not belong to any group Field exists in the database Table 382 Papu_Group_Id Sgsn_Bssgp_Cell_Stat_Papu_Group_Id DN05148836 Issue 2-2 Id:0900d805809551ce 371 .) Field name Sgsn_Bssgp_Cell_Stat_Sequence_Nr Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the sequence number of a response message. Maximum number of needed SGSN_BSSGP_CELL_STAT reports per papu is 10. Possible values 1 . counters of all cells do not necessarily fit a single report. RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Bssgp_Cell_Stat_Cell_Element_Count Datatype in IDS UINT16 SGSN version >=SG4 Explanation Number of cell elements in actual use. Possible values 0x0 . Possible values Mobile network code (MNC) Field exists in the database Cgi_Mnc Table 385 Sgsn_Bssgp_Cell_Stat_Cgi_Mnc Field name Sgsn_Bssgp_Cell_Stat_Cgi_Lac Datatype in IDS UINT16 SGSN version >=SG4 Explanation Location area code for the most recent cell.0xFFFF Field exists in the database Cell_Element_Count Table 383 Sgsn_Bssgp_Cell_Stat_Cell_Element_Count Field name Sgsn_Bssgp_Cell_Stat_Cgi_Mcc Datatype in IDS UINT16 SGSN version >=SG4 Explanation Contains the country code Possible values Mobile country code (MCC) Field exists in the database Cgi_Mcc Table 384 Sgsn_Bssgp_Cell_Stat_Cgi_Mcc Field name Sgsn_Bssgp_Cell_Stat_Cgi_Mnc Datatype in IDS UINT16 SGSN version >=SG4 Explanation Mobile network code for the most recent cell. Possible values Location are code (LAC) Field exists in the database Cgi_Lac Table 386 Sgsn_Bssgp_Cell_Stat_Cgi_Lac Field name Sgsn_Bssgp_Cell_Stat_Cgi_Rac Datatype in IDS UINT16 Table 387 372 Sgsn_Bssgp_Cell_Stat_Cgi_Rac Id:0900d805809551ce DN05148836 Issue 2-2 . ) Field name Sgsn_Bssgp_Cell_Stat_Cgi_Ci Datatype in IDS UINT16 SGSN version >=SG4 Explanation Contains the cell identity. which has passed MS and BVC flow control. Possible values 0x0-0xFFFFFFFF Field exists in the database Og_Fr_Shared_Data_In_Bytes Table 389 Sgsn_Bssgp_Cell_Stat_Discarded_Packets Field name Sgsn_Bssgp_Cell_Stat_Passed_Data_In_Bytes Datatype in IDS UINT32 SGSN version >=SG4 Explanation Data. Possible values 0x0-0xFFFFFFFF Field exists in the database Og_Fr_Shared_Data_In_Bytes Table 390 Sgsn_Bssgp_Cell_Stat_Passed_Data_In_Bytes Field name Sgsn_Bssgp_Cell_Stat_Llc_Fram_Bssgp_Sum Datatype in IDS UINT32 SGSN version >=SG6 Explanation Sum of numbers of LLC Frames Waiting In The BSSGP Table 391 RTT report descriptions Sgsn_Bssgp_Cell_Stat_Llc_Fram_Bssgp_Sum DN05148836 Issue 2-2 Id:0900d805809551ce 373 . Possible values Cell identity (CI) Field exists in the database Ig_Fr_Shared_Data_In_Bytes Table 388 Sgsn_Bssgp_Cell_Stat_Cgi_Ci Field name Sgsn_Bssgp_Cell_Stat_Discarded_Packets Datatype in IDS UINT32 SGSN version >=SG4 Explanation Discarded packets due to MS-BVC flow control. in bytes. Possible values Routing area code (RAC) Field exists in the database Cgi_Rac Table 387 Sgsn_Bssgp_Cell_Stat_Cgi_Rac (Cont.Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG4 Explanation Routing area code for the most recent cell. Under the <SGSN_Release_Id>_BSSGP_PAPU_STAT section.conf. The SQL datatype appears after the column name and “=” symbol.8 BSSGP_PAPU_STAT fields The following table shows the BSSGP_PAPU_STAT fields: Traffic News event type SGSN_BSSGP_PAPU_STAT_EVENT Database table <SGSN_Release_Id>_BSSGP_PAPU_ STAT Table 394 SGSN_BSSGP_PAPU_STAT fields The database column names are the same as the IDS field names without the Sgsn_BSSGP_PAPU_STAT prefix.) Field name Sgsn_Bssgp_Cell_Stat_Llc_Fram_Bssgp_Den Datatype in IDS UINT32 SGSN version >=SG6 Explanation Denominator of samples of LLC Frames Waiting In The BSSGP Queue Possible values 0x1 – 0xFFFF Field exists in the database Llc_Fram_Bssgp_Den Table 392 Sgsn_Bssgp_Cell_Stat_Llc_Fram_Bssgp_Den Field name Sgsn_Bssgp_Cell_Stat_Llc_Fram_Bssgp_Peak Datatype in IDS UINT32 SGSN version >=SG6 Explanation Peak value of numbers of LLC Frames Waiting In The BSSGP Queue Possible values 0x1 – 0xFFFF Field exists in the database Llc_Fram_Bssgp_Peak Table 393 Sgsn_Bssgp_Cell_Stat_Llc_Fram_Bssgp_Peak 6. For example. the Sgsn_BSSGP_PAPU_STAT_Report_Count IDS field is Report Count field in Traffic News SGSN_BSSGP_PAPU_STAT_EVENT. The Traffic News field names are the same as the database column names but use spaces instead of underscores between words. the Sgsn_BSSGP_PAPU_STAT_Report_Count IDS field is the Report_Count column in database table <SGSN_Release_Id>_BSSGP_PAPU_STAT. For example. 374 Id:0900d805809551ce DN05148836 Issue 2-2 . The database column SQL datatypes can be found in the workspace configuration file dbd_sgsn_bssgp_papu_stat. there is a single-row entry for each table column.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Possible values 0x1 – 0xFFFF Field exists in the database Llc_Fram_Bssgp_Sum Table 391 Sgsn_Bssgp_Cell_Stat_Llc_Fram_Bssgp_Sum (Cont. 0xFFFFFFFF) Field exists in the database Report_Count Table 396 Sgsn_Bssgp_Papu_Stat_Report_Count Field name Sgsn_Bssgp_Papu_Stat_Report_Date Datatype in IDS BCDDATE SGSN version >=SG4 Explanation The date when the report was sent to Traffica.Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Bssgp_Papu_Stat_Report_Id Datatype in IDS UINT16 SGSN version >=SG4 Explanation RTT report descriptions Contains information on the report type.m. Possible values 0x0-0xFFFFFFFF Field exists in the database Sgsn_Bssgp_Papu_Stat_Report_Time and Sgsn_Bssgp_Papu_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Table 397 Sgsn_Bssgp_Papu_Stat_Report_Date Field name Sgsn_Bssgp_Papu_Stat_Report_Time Datatype in IDS BCDTIME SGSN version >=SG4 Explanation The time when the report was sent to Traffica. Possible values 0x0212 Field exists in the database Report_Id Table 395 Sgsn_Bssgp_Papu_Stat_Report_Id Field name Sgsn_Bssgp_Papu_Stat_Report_Count Datatype in IDS UINT32 SGSN version >=SG4 Explanation Contains information on how many reports of this type have been sent to Traffica. Possible values 0x0-0xFFFFFFFF Table 398 Sgsn_Bssgp_Papu_Stat_Report_Time DN05148836 Issue 2-2 Id:0900d805809551ce 375 . NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field. Possible values 0 .4 294 967 296 (0x0 . because the possible values can and will change in the future. The value of the counter is reset everyday at 00:00 a. Sampling interval is 30 seconds.0xFF Field exists in the database Papu_Id Table 399 Sgsn_Bssgp_Papu_Stat_Papu_Id Field name Sgsn_Bssgp_Papu_Stat_Physical_Papu_Id Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the physical index of papu. Only downlink data is stored to buffer. Possible values 0x0 .0xFF Value 0x28 is used if physical papu id cannot be solved due some internal error Field exists in the database Table 400 Physical_Papu_Id Sgsn_Bssgp_Papu_Stat_Physical_Papu_Id Field name Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr1 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the average of BSSGP buffer utilisation.) Field name Sgsn_Bssgp_Papu_Stat_Papu_Id Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the identity of papu. Priority 1.RTT report descriptions Field exists in the database Table 398 Traffica Reference Guide for SGSN Direct Interface Sgsn_Nsvc_Stat_Report_Time and Sgsn_Nsvc_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Sgsn_Bssgp_Papu_Stat_Report_Time (Cont. Possible values 0x0 . Possible values 0x0 . Sum of samples (0-100%) taken.0xFFFF FFFF Field exists in the database Ave_Buf_Util_Sum_Pr1 Table 401 Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr1 Field name Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Den_Pr1 Datatype in IDS UINT32 SGSN version >=SG4 Table 402 376 Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Den_Pr1 Id:0900d805809551ce DN05148836 Issue 2-2 . Priority 1.0xFFFF FFFF Field exists in the database Ave_Buf_Util_Den_Pr1 Table 402 Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Den_Pr1 (Cont. Count of samples taken.100 Field exists in the database Peak_Buf_Util_Pr1 Table 403 Sgsn_Bssgp_Papu_Stat_Peak_Buf_Util_Pr1 Field name Sgsn_Bssgp_Papu_Stat_BSSGP_Lost_Data_Pr1 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains discarded downlink bytes in BSSGP due to buffer overflow or RED. Possible values 0x0 . Priority 1. Possible values 0 . Priority 1.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Explanation This field contains the average BSSGP buffer utilisation. Current value and previous peak value are compared every 30 seconds. Possible values 0x0 .0xFFFF FFFF Field exists in the database Lost_Data_Pr1 Table 404 Sgsn_Bssgp_Papu_Stat_BSSGP_Lost_Data_Pr1 Field name Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Pr1 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the amount in bytes of how much data has been dropped due to redundancy elimination. Possible values 0x0 . Priority 1.) Field name Sgsn_Bssgp_Papu_Stat_Peak_Buf_Util_Pr1 Datatype in IDS UINT16 SGSN version >=SG4 Explanation This field contains the peak value of BSSGP buffer utilisation.0xFFFF FFFF Field exists in the database BSSGP_Dropped_Packets_Pr1 Table 405 Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Pr1 Field name Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Pr1 Datatype in IDS UINT32 Table 406 Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Pr1 DN05148836 Issue 2-2 Id:0900d805809551ce 377 . Priority 2. Priority 1.0xFFFF FFFF Field exists in the database Cgi_Lac Table 408 Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Den_Pr2 Field name Sgsn_Bssgp_Papu_Stat_Peak_Buf_Util_Pr2 Datatype in IDS UINT16 SGSN version >=SG4 Explanation This field contains the peak value of BSSGP buffer utilisation. Possible values 0.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG4 Explanation This field contains the amount in bytes of how much data has been dropped due to redundancy elimination.0xFFFF FFFF Field exists in the database Ave_Buf_Util_Sum_Pr2 Table 407 Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr2 Field name Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Den_Pr2 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the average of BSSGP buffer utilisation. Priority 2. Count of samples taken. Possible values 0x0 . Possible values 0x0 . Only downlink data is stored to buffer. Current value and previous peak value are compared every 30 seconds.) Field name Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr2 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the average of BSSGP buffer utilisation. Sampling interval is 30 seconds.0xFFFF FFFF Field exists in the database BSSGP_Dropped_Packets_Pr1 Table 406 Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Pr1 (Cont. Sum of samples (0-100%) taken.100 Field exists in the database Peak_Buf_Util_Pr2 Table 409 Field name Table 410 378 Sgsn_Bssgp_Papu_Stat_Peak_Buf_Util_Pr2 Sgsn_Bssgp_Papu_Stat_BSSGP_Lost_Data_Pr2 Sgsn_Bssgp_Papu_Stat_BSSGP_Lost_Data_Pr2 Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values 0x0 . Priority 2. Sampling interval is 30 seconds.0xFFFF FFFF Field exists in the database BSSGP_Lost_Data_Pr2 Table 410 Sgsn_Bssgp_Papu_Stat_BSSGP_Lost_Data_Pr2 (Cont. Priority 2. Count of samples taken. Possible values 0x0-0xFFFFFFFF Field exists in the database BSSGP_Dropped_Packets_Pr2 Table 411 Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Pr2 Field name Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr3 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the average of BSSGP buffer utilisation. Only downlink data is stored to buffer. Priority 2. Possible values 0x0-0xFFFFFFFF Field exists in the database Ave_Buf_Util_Den_Pr3 Table 413 Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Den_Pr3 DN05148836 Issue 2-2 Id:0900d805809551ce 379 . Possible values 0x0-0xFFFFFFFF Field exists in the database Og_Fr_Shared_Data_In_Bytes Table 412 Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr3 Field name Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Den_Pr3 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the average of BSSGP buffer utilisation. Priority 3. Priority 3. Sum of samples (0-100%) taken. Possible values 0x0 .) Field name Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Pr2 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the amount in bytes of how much data has been dropped due to redundancy elimination.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains discarded downlink bytes in BSSGP due to buffer overflow or RED. Priority 3. in bytes. Priority 3. Possible values 0x0-0xFFFFFFFF Field exists in the database BSSGP_Dropped_Packets_Pr3 Table 417 380 Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Pr3 Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Bssgp_Papu_Stat_Peak_Buf_Util_Pr3 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the peak value of BSSGP buffer utilisation. Current value and previous peak value are compared every 30 seconds. that has been dropped due to redundancy elimination. Possible values 0x0-0xFFFFFFFF Field exists in the database BSSGP_Lost_Data_Pr3 Table 416 Sgsn_Bssgp_Papu_Stat_BSSGP_Lost_Data_Pr3 Field name Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Pr3 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the amount of data. Priority 3. Sampling interval is 30 seconds. Only downlink data is stored to buffer.100 Field exists in the database Peak_Buf_Util_Pr3 Table 414 Sgsn_Bssgp_Papu_Stat_Peak_Buf_Util_Pr3 Field name Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr3 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the average of BSSGP buffer utilisation. Possible values 0. Sum of samples (0-100%) taken. Priority 3. Possible values 0x0-0xFFFFFFFF Field exists in the database Og_Fr_Shared_Data_In_Bytes Table 415 Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr3 Field name Sgsn_Bssgp_Papu_Stat_BSSGP_Lost_Data_Pr3 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains discarded downlink bytes in BSSGP due to buffer overflow or RED. Sum of samples (0-100%) taken. Current value and previous peak value are compared every 30 seconds. Sum of samples (0-100%) taken. Priority 4. Possible values 0x0-0xFFFFFFFF Field exists in the database Og_Fr_Shared_Data_In_Bytes Table 419 Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr3 Field name Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Den_Pr4 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the average of BSSGP buffer utilisation. Only downlink data is stored to buffer. Only downlink data is stored to buffer. Number of samples taken. Priority 3. Sampling interval is 30 seconds. Possible values 0-100 Field exists in the database Peak_Buf_Util_Pr4 Table 421 Sgsn_Bssgp_Papu_Stat_Peak_Buf_Util_Pr4 DN05148836 Issue 2-2 Id:0900d805809551ce 381 . Priority 4.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr4 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the average of BSSGP buffer utilisation. Possible values 0x0-0xFFFFFFFF Field exists in the database Ave_Buf_Util_Den_Pr4 Table 420 Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Den_Pr4 Field name Sgsn_Bssgp_Papu_Stat_Peak_Buf_Util_Pr4 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the peak value of BSSGP buffer utilisation. Priority 3. Sampling interval is 30 seconds. Possible values 0x0-0xFFFFFFFF Field exists in the database Ave_Buf_Util_Sum_Pr4 Table 418 Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr4 Field name Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Pr3 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the average of BSSGP buffer utilisation. that has been dropped due to redundancy elimination. in bytes. Priority 5.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Bssgp_Papu_Stat_BSSGP_Lost_Data_Pr4 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains discarded downlink bytes in BSSGP due to buffer overflow or REDPriority 4. Number of samples taken. Possible values 0x0-0xFFFFFFFF Field exists in the database Ave_Buf_Util_Sum_Str Table 424 Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Str Field name Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Den_Str Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the average of BSSGP buffer utilisation. Priority streaming Possible values 0x0-0xFFFFFFFF Field exists in the database Ave_Buf_Util_Den_Str Table 425 382 Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Den_Str Id:0900d805809551ce DN05148836 Issue 2-2 . Sum of samples (0-100%) taken. Only downlink data is stored to buffer. Possible values 0x0-0xFFFFFFFF Field exists in the database BSSGP_Lost_Data_Pr4 Table 422 Sgsn_Bssgp_Papu_Stat_BSSGP_Lost_Data_Pr4 Field name Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Pr4 Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the amount data. Sampling interval is 30 seconds. Possible values 0x0-0xFFFFFFFF Field exists in the database BSSGP_Dropped_Packets_Pr4 Table 423 Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Pr4 Field name Sgsn_Bssgp_Papu_Stat_Ave_Buf_Util_Sum_Str Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the average of BSSGP buffer utilisation. Priority 4. Possible values 0x0 . is not activated.100 Field exists in the database Peak_Buf_Util_Str Table 426 Sgsn_Bssgp_Papu_Stat_Peak_Buf_Util_Str Field name Sgsn_Bssgp_Papu_Stat_BSSGP_Lost_Data_Str Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains discarded downlink bytes in BSSGP due to buffer overflow or RED.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Bssgp_Papu_Stat_Peak_Buf_Util_Str Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the peak value of BSSGP buffer utilisation. Field exists in the database Og_Fr_Shared_Data_In_Bytes Table 428 Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Str Field name Sgsn_Bssgp_Papu_Stat_Papu_Capa Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the subscriber capacity of particular PAPU in SGSN. Possible values 0 . because redundancy elimination is not made for priority streaming. Table 429 Sgsn_Bssgp_Papu_Stat_Papu_Capa DN05148836 Issue 2-2 Id:0900d805809551ce 383 . Field exists in the database Table 427 BSSGP_Lost_Data_Str Sgsn_Bssgp_Papu_Stat_BSSGP_Lost_Data_Str Field name Sgsn_Bssgp_Papu_Stat_BSSGP_Dropped_Packets_Str Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains the amount in bytes of how much data has been dropped due to redundancy elimination. Priority streaming. Priority streaming. Push to talk over Cellular (PoC) in 2GSGSN (Streaming QoS). This field is always 0 if feature.0xFFFF FFFF. Current value and previous peak value are compared every 30 seconds. Possible values This field is always 0. Large RA Support is not activated. there is a single-row entry for each table column. The SQL datatype appears after the column name and “=” symbol. the Sgsn_SMS_RTT_Report_Count IDS field is the Report_Count column in database table <SGSN_Release_Id>_SMS_RTT. The database column SQL datatypes can be found in the workspace configuration file dbd_sgsn_sms_rtt.conf.) Field name Sgsn_Bssgp_Papu_Stat_Papu_Group_Id Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains PAPU group id. For example. For example.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface 0x41 = maximum of 65 000 attached subscribers 0x64 = maximum of 100 000 attached subscribers 0xFA = maximum of 250 000 attached subscribers Field exists in the database Table 429 Papu_Capa Sgsn_Bssgp_Papu_Stat_Papu_Capa (Cont. Field name Sgsn_Sms_Rtt_Report_Id Datatype in IDS UINT16 SGSN version >=SG4 Table 432 384 Sgsn_Sms_Rtt_Report_Id Id:0900d805809551ce DN05148836 Issue 2-2 . the Sgsn_SMS_RTT_Report_Count IDS field is Report Count field in Traffic News SGSN_SMS_RTT_EVENT. Possible values 0-255 This field is always 0 if feature. Under the <SGSN_Release_Id>_BSSGP_CELL_STAT section.9 SMS_RTT fields The following table shows the SMS_RTT fields: Traffic News event type SGSN_SMS_RTT_EVENT Database table <SGSN_Release_Id>_SMS_RTT Table 431 SGSN_SMS_RTT fields The database column names are the same as the IDS field names without the Sgsn_SMS_RTT prefix. Value 0 means that PAPU does not belong to any group Field exists in the database Table 430 Papu_Group_Id Sgsn_Bssgp_Papu_Stat_Papu_Group_Id 6. The Traffic News field names are the same as the database column names but use spaces instead of underscores between words. Possible values 0x0-0xFFFFFFFF Field exists in the database Sgsn_Sms_Rtt_Report_Time and Sgsn_Sms_Rtt_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Table 435 Sgsn_Sms_Rtt_Report_Date DN05148836 Issue 2-2 Id:0900d805809551ce 385 . Possible values 0x0215 Field exists in the database Report_Id Table 432 Sgsn_Sms_Rtt_Report_Id (Cont. and whether they are reported to Traffica. NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field. Field exists in the database Table 434 Event_Count Sgsn_Sms_Rtt_Event_Count Field name Sgsn_Sms_Rtt_Report_Date Datatype in IDS BCDTIME SGSN version >=SG4 Explanation The date when the report was sent to Traffica.) Field name Sgsn_Sms_Rtt_Report_Count Datatype in IDS UINT32 SGSN version >=SG4 Explanation Contains information on how many reports of this type have been sent to Traffica.0xFFFFFFFF) Field exists in the database Report_Count Table 433 Sgsn_Sms_Rtt_Report_Count Field name Sgsn_Sms_Rtt_Event_Count Datatype in IDS BCDDATE SGSN version >=SG4 Explanation This field contains information about how many events of this type have been detected.m. Possible values 0 . because the possible values can and will change in the future. The value of the counter is reset every day at 00:00 a. Possible values 0x0-0xFFFFFFFF The value of the counter is reset everyday at 00:00 a.m.4 294 967 296 (0x0 .Traffica Reference Guide for SGSN Direct Interface Explanation RTT report descriptions Contains information on the report type. if imsi is 420018000100001 the Sgsn_Imsi field is: 24 00 81 00 10 00 00 FI. Double_digit has two parts. Field contents are: array(8) OF double_digit. For example.0x1 Field exists in the database SF_Authentication_Done Table 439 386 Sgsn_Sms_Rtt_SF_Authentication_Done Id:0900d805809551ce DN05148836 Issue 2-2 . lower_digit (4bits) and upper_digit (4bits). Possible values 0x0 . Possible values IMSI numbers Field exists in the database Imsi Table 438 Sgsn_Sms_Rtt_Imsi Field name Sgsn_Sms_Rtt_SF_Authentication_Done Datatype in IDS UINT8 SGSN version >=SG4 Explanation If this field value is something other than zero.0xFF Field exists in the database Imsi_Length Table 437 Sgsn_Sms_Rtt_Imsi_Length Field name Sgsn_Sms_Rtt_Imsi Datatype in IDS BCDREV8(8) SGSN version >=SG4 Explanation This field contains the IMSI number which caused report sending. Imsi is stored in decimal format and the endmark is 0xF. one double_digit field is of size byte. Possible values 0x0 . Possible values 0x0-0xFFFFFFFF Field exists in the database Sgsn_Paging_Stat_Report_Time and Sgsn_Paging_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Table 436 Sgsn_Sms_Rtt_Report_Time Field name Sgsn_Sms_Rtt_Imsi_Length Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains length of IMSI-number.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Sms_Rtt_Report_Time Datatype in IDS BCDTIME SGSN version >=SG4 Explanation The time when the report was sent to Traffica. authentication security function has been performed before the main GMM/SM procedure. 0x1 Field exists in the database SF_Imei_Checked Table 442 Sgsn_Sms_Rtt_SF_Imei_Checked Field name Sgsn_Sms_Rtt_SF_Ciph_Algorithm Datatype in IDS UINT32 SGSN version >=SG4 Explanation If this field value is non-zero.0x1 Field exists in the database SF_Ptmsi_Reallocated Table 441 Sgsn_Sms_Rtt_SF_Ptmsi_Reallocated Field name Sgsn_Sms_Rtt_SF_Imei_Checked Datatype in IDS UINT8 SGSN version >=SG4 Explanation If this field value is something other than zero. ptmsi_sign_realloc function has been performed before the main GMM/SM procedure. Possible values 0x0 .Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Sms_Rtt_SF_Ptmsi_Sign_Realloc Datatype in IDS UINT8 SGSN version >=SG4 Explanation If this field value is something other than zero. Possible values 0x0 .0x1 Field exists in the database SF_Ptmsi_Sign_Realloc Table 440 Sgsn_Sms_Rtt_SF_Ptmsi_Sign_Realloc Field name Sgsn_Sms_Rtt_SF_Ptmsi_Reallocated Datatype in IDS UINT8 SGSN version >=SG4 Explanation If this field value is something other than zero. Table 443 Sgsn_Sms_Rtt_SF_Ciph_Algorithm DN05148836 Issue 2-2 Id:0900d805809551ce 387 . ciph_algorithm function has been performed before the main GMM/SM procedure. imei_checked function has been performed before the main GMM/SM procedure. Possible values 0x0 . ptmsi_reallocated function has been performed before the main GMM/SM procedure. Possible values Imei Field exists in the database Imei Table 444 Sgsn_Sms_Rtt_Imei Field name Sgsn_Sms_Rtt_Msisdn_Address_length Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the length of an address. The term ‘served’ equipment is used to describe the ME involved in the transaction recorded. for example. Possible values 0x0 . Double_digit has two parts.) Field name Sgsn_Sms_Rtt_Imei Datatype in IDS BCDREV8(8) SGSN version >=SG4 Explanation The international mobile equipment identity (IMEI) of the equipment served. Field contents are: array(8) OF double_digit. the called ME in the case of a network initiated PDP context. For example. one double_digit field is of size byte.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface no_ciph_c = 0 gea_1_c = 1 gea_2_c = 2 gea_3_c = 3 gea_4_c = 4 gea_5_c = 5 gea_6_c = 6 gea_7_c = 7 Field exists in the database Table 443 SF_Ciph_Algorithm Sgsn_Sms_Rtt_SF_Ciph_Algorithm (Cont. lower_digit (4bits) and upper_digit (4bits). if imei is 420018000100001 the Sgsn_Imei field is: 24 00 81 00 10 00 00 F1. Imei is stored in decimal format and the endmark is 0xF.0xFF Field exists in the database Msisdn_Address_length Table 445 Sgsn_Sms_Rtt_Msisdn_Address_length Field name Sgsn_Sms_Rtt_Msisdn_Indicators Datatype in IDS UINT8 SGSN version >=SG4 Table 446 388 Sgsn_Sms_Rtt_Msisdn_Indicators Id:0900d805809551ce DN05148836 Issue 2-2 . ) Field name Sgsn_Sms_Rtt_Msisdn_Numbers Datatype in IDS BCDREV8(9) SGSN version >=SG4 Explanation MSISDN number of the subscriber. Table 448 Sgsn_Sms_Rtt_Ra_Cap_Array_0-5_Acc_Tec_Type DN05148836 Issue 2-2 Id:0900d805809551ce 389 . Possible values MSISDN number Field exists in the database Msisdn_Numbers Table 447 Sgsn_Sms_Rtt_Msisdn_Numbers Field name Sgsn_Sms_Rtt_Ra_Cap_Array_0-5_Acc_Tec_Type Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains MS Radio access capability arrays slot 0 technology type.Traffica Reference Guide for SGSN Direct Interface Explanation RTT report descriptions This field contains address indicators of addresses used in MAP. Sgsn_Msisdn_Indicators is a packed struct including three parts: nbr_plan (0:15) Numbering Plan indicator na_of_ad (0:7) Nature of address indicator ext (0:1) Extension indicator Possible values Bits 1-4: Numbering plan 0 = Unknown 1 = E.212 7 = E.214 9 = PNP Bits 5-7: Nature of address 0 = unknown 1 = int 2 = nat 3 = nets 4 = subs Bit 8: Extension 1 = no_ext 0 = ext Field exists in the database Table 446 Msisdn_Indicators Sgsn_Sms_Rtt_Msisdn_Indicators (Cont.164 6 = E. 1).) Field name Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_1 Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains radio access capability information (24.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface 0x0 = GSM 900-P Access Technology Type 0x1 = GSM 900-E Access Technology Type 0x2 = GSM 900-R Access Technology Type 0x3 = GSM 1800 Access Technology Type 0x4 = GSM 1900 Access Technology Type 0x5 = GSM 450 Access Technology Type 0x6 = GSM 480 Access Technology Type 0x7 = GSM 850 Access Technology Type 0xFF = Not used Field exists in the database Table 448 Ra_Cap_Array_0-5_Acc_Tec_Type Sgsn_Sms_Rtt_Ra_Cap_Array_0-5_Acc_Tec_Type (Cont. This field is a packed struct: rf_power_cap BITS(3) a5_7 BITS(1) a5_6 BITS(1) a5_5 BITS(1) a5_4 BITS(1) a5_3 BITS(1) Possible values Field exists in the database Table 449 Ra_Cap_Array_1-5_Info_1 Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_1 Field name Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_2 Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains radio access capability information (24.4.1).008 v.3.008 v.4. This field is a packed struct: a5_2 BITS(1) a5_1 BITS(1) es_ind BITS(1) ps_cap BITS(1) vgcs BITS(1) vbs BITS(1) multi_sl_ca_ind BITS(2) Table 450 390 Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_2 Id:0900d805809551ce DN05148836 Issue 2-2 .3. 4. This field is a packed struct: hscsd BITS(5) Possible values Field exists in the database Table 451 Ra_Cap_Array_1-5_Info_3 Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_3 Field name Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_4 Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains radio access capability information (24.008 v. This field is a packed struct: sms_value BITS(4) Possible values Field exists in the database Table 453 Ra_Cap_Array_1-5_Info_5 Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_5 DN05148836 Issue 2-2 Id:0900d805809551ce 391 .) Field name Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_3 Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains radio access capability information (24.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Possible values Field exists in the database Table 450 Ra_Cap_Array_1-5_Info_2 Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_2 (Cont.3.1).1).1).3.008 v.008 v.4.4.3. This field is a packed struct: gprs_multi_sl_cl BITS(5) gedac BITS(1) sms_ind BITS(1) Possible values Field exists in the database Table 452 Ra_Cap_Array_1-5_Info_4 Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_4 Field name Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_5 Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains radio access capability information (24. 4.1).008 v.4. This field is a packed struct: ecsd_multi_sl_cl BITS(5) Possible values Field exists in the database Table 454 Ra_Cap_Array_1-5_Info_6 Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_6 Field name Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_7 Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains radio access capability information (24.008 v.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_6 Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains radio access capability information (24.3. This field is a packed struct: egprs_multi_sl_cl BITS(5) eedac BITS(1) dtm_multi_sub_cl BITS(2) Possible values Field exists in the database Table 455 Ra_Cap_Array_1-5_Info_7 Sgsn_Sms_Rtt_Ra_Cap_Array_1-5_Info_7 Field name Sgsn_Sms_Rtt_Ra_Cap_Array_1_Acc_Tec_Type Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains MS Radio access capability arrays slot 1 technology type.3. Possible values 0x0 = GSM 900-P Access Technology Type 0x1 = GSM 900-E Access Technology Type 0x2 = GSM 900-R Access Technology Type 0x3 = GSM 1800 Access Technology Type 0x4 = GSM 1900 Access Technology Type 0x5 = GSM 450 Access Technology Type 0x6 = GSM 480 Access Technology Type 0x7 = GSM 850 Access Technology Type 0xFF = Not used Field exists in the database Table 456 392 Ra_Cap_Array_1_Acc_Tec_Type Sgsn_Sms_Rtt_Ra_Cap_Array_1_Acc_Tec_Type Id:0900d805809551ce DN05148836 Issue 2-2 .1). Possible values 0x0 = GSM 900-P Access Technology Type 0x1 = GSM 900-E Access Technology Type 0x2 = GSM 900-R Access Technology Type 0x3 = GSM 1800 Access Technology Type 0x4 = GSM 1900 Access Technology Type 0x5 = GSM 450 Access Technology Type 0x6 = GSM 480 Access Technology Type 0x7 = GSM 850 Access Technology Type 0xFF = Not used Field exists in the database Table 457 Ra_Cap_Array_2_Acc_Tec_Type Sgsn_Sms_Rtt_Ra_Cap_Array_2_Acc_Tec_Type Field name Sgsn_Sms_Rtt_Ra_Cap_Array_3_Acc_Tec_Type Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains MS Radio access capability arrays slot 3 technology type Possible values 0x0 = GSM 900-P Access Technology Type 0x1 = GSM 900-E Access Technology Type 0x2 = GSM 900-R Access Technology Type 0x3 = GSM 1800 Access Technology Type 0x4 = GSM 1900 Access Technology Type 0x5 = GSM 450 Access Technology Type 0x6 = GSM 480 Access Technology Type 0x7 = GSM 850 Access Technology Type 0xFF = Not used Field exists in the database Table 458 Ra_Cap_Array_3_Acc_Tec_Type Sgsn_Sms_Rtt_Ra_Cap_Array_3_Acc_Tec_Type Field name Sgsn_Sms_Rtt_Ra_Cap_Array_4_Acc_Tec_Type Datatype in IDS UINT8 SGSN version >=SG4 Table 459 Sgsn_Sms_Rtt_Ra_Cap_Array_4_Acc_Tec_Type DN05148836 Issue 2-2 Id:0900d805809551ce 393 .Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Sms_Rtt_Ra_Cap_Array_2_Acc_Tec_Type Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains MS Radio access capability arrays slot 2 technology type. Possible values Field exists in the database Table 461 394 Nw_Cap_Length Sgsn_Sms_Rtt_Nw_Cap_Length Id:0900d805809551ce DN05148836 Issue 2-2 .) Field name Sgsn_Sms_Rtt_Ra_Cap_Array_5_Acc_Tec_Type Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains MS Radio access capability arrays slot 5 technology type Possible values 0x0 = GSM 900-P Access Technology Type 0x1 = GSM 900-E Access Technology Type 0x2 = GSM 900-R Access Technology Type 0x3 = GSM 1800 Access Technology Type 0x4 = GSM 1900 Access Technology Type 0x5 = GSM 450 Access Technology Type 0x6 = GSM 480 Access Technology Type 0x7 = GSM 850 Access Technology Type 0xFF = Not used Field exists in the database Table 460 Ra_Cap_Array_5_Acc_Tec_Type Sgsn_Sms_Rtt_Ra_Cap_Array_5_Acc_Tec_Type Field name Sgsn_Sms_Rtt_Nw_Cap_Length Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the length of network capability context.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Explanation This field contains MS Radio access capability arrays slot 4 technology type Possible values 0x0 = GSM 900-P Access Technology Type 0x1 = GSM 900-E Access Technology Type 0x2 = GSM 900-R Access Technology Type 0x3 = GSM 1800 Access Technology Type 0x4 = GSM 1900 Access Technology Type 0x5 = GSM 450 Access Technology Type 0x6 = GSM 480 Access Technology Type 0x7 = GSM 850 Access Technology Type 0xFF = Not used Field exists in the database Table 459 Ra_Cap_Array_4_Acc_Tec_Type Sgsn_Sms_Rtt_Ra_Cap_Array_4_Acc_Tec_Type (Cont. 0 = SS screening indicator default value for phase 1 1 = SS screening indicator value for phase 2 0 = The ME has a preference for the default alphabet over UCS2 1 = The ME has no preference between the use of the default alphabet and the use of UCS2 0 = MS does not support MT point to point SMS via dedicated signalling channels/ via GPRS packet data channels 1 = MS supports MT point to point SMS via dedicated signalling channels/ via GPRS packet data channels 0 = Encryption algorithm GEA/1 not available 1 = Encryption algorith GEA/1 available Field exists in the database Table 462 Nw_Cap_Content Sgsn_Sms_Rtt_Nw_Cap_Content Field name Sgsn_Sms_Rtt_Nw_Cap_Spare1 Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the spare byte of network capability context.Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Sms_Rtt_Nw_Cap_Content Datatype in IDS UINT16 SGSN version >=SG4 Explanation RTT report descriptions This field contains MS network capability union. Possible values Field exists in the database Table 463 Nw_Cap_Spare1 Sgsn_Sms_Rtt_Nw_Cap_Spare1 DN05148836 Issue 2-2 Id:0900d805809551ce 395 . Nw_cap_info_t is packed struct: spare BITS(1) gea7 BITS(1) gea6 BITS(1) gea5 BITS(1) gea4 BITS(1) gea3 BITS(1) gea2 BITS(1) pfc_feature rev_level solsa_cap ss_scr_i ucs2 BITS(1) BITS(1) BITS(1) BITS(2) BITS(1) sms_cap_gprs BITS(1) sms_cap_ded BITS(1) gea1 Possible values BITS(1). Number is stored in decimal format and the endmark is 0xF. lower_digit(4bits) and upper_digit(4bits). Possible values Service center number Field exists in the database Service_Center_Numbers Table 466 Sgsn_Sms_Rtt_Service_Center_Numbers Field name Sgsn_Sms_Rtt_Cgi_Mcc Datatype in IDS UINT16 SGSN version >=SG4 Explanation Contains the country code. Field contents are: array(9) OF double_digit. one double_digit field is of size byte. Possible values Field exists in the database Table 465 Service_Center_Indicators Sgsn_Sms_Rtt_Service_Center_Indicators Field name Sgsn_Sms_Rtt_Service_Center_Numbers Datatype in IDS BCDREV8(9) SGSN version >=SG4 Explanation This field contains the service center number. Double_digit has two parts. Possible values 0x0 .0xFF Field exists in the database Service_Center_Address_length Table 464 Sgsn_Sms_Rtt_Service_Center_Address_length Field name Sgsn_Sms_Rtt_Service_Center_Indicators Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains address indicators of addresses used in MAP Indicators is a packed struct including three parts: nbr_plan (0:15) Numbering Plan indicator na_of_ad (0:7) Nature of address indicator ext (0:1) Extension indicator.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Sms_Rtt_Service_Center_Address_length Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the length of an address. Possible values Mobile country code (MCC) Table 467 396 Sgsn_Sms_Rtt_Cgi_Mcc Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values Location are code (LAC) Field exists in the database Cgi_Lac Table 468 Sgsn_Sms_Rtt_Cgi_Lac Field name Sgsn_Sms_Rtt_Cgi_Rac Datatype in IDS UINT16 SGSN version >=SG4 Explanation Routing area code for the most recent cell.Traffica Reference Guide for SGSN Direct Interface Field exists in the database Table 467 Cgi_Mcc Sgsn_Sms_Rtt_Cgi_Mcc (Cont.0x1 Field exists in the database Roaming_Status Table 471 Sgsn_Sms_Rtt_Roaming_Status DN05148836 Issue 2-2 Id:0900d805809551ce 397 .) Field name Sgsn_Sms_Rtt_Cgi_Lac Datatype in IDS UINT16 SGSN version >=SG4 Explanation Location area code for the most recent cell. Possible values Cell identity (CI) Field exists in the database Cgi_Ci Table 470 RTT report descriptions Sgsn_Sms_Rtt_Cgi_Ci Field name Sgsn_Sms_Rtt_Roaming_Status Datatype in IDS UINT8 SGSN version >=SG4 Explanation If this field value is something other than zero. Possible values 0x0 . attached subscriber is roaming from VPLMN. Possible values Routing area code (RAC) Field exists in the database Cgi_Rac Table 469 Sgsn_Sms_Rtt_Cgi_Rac Field name Sgsn_Sms_Rtt_Cgi_Ci Datatype in IDS UINT16 SGSN version >=SG4 Explanation Contains the cell identity. RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Sms_Rtt_Cause_Proc Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains procedure codes for SGSN cause. Mobility Management fills this field according to the service that it is asked to offer. For example. Table 472 398 Sgsn_Sms_Rtt_Cause_Proc Id:0900d805809551ce DN05148836 Issue 2-2 . if Mobility Management gets an attach request. Sgsn_Cause_Proc is set to value 0x0. 0xFF = Initialisation value attach_c 0x0 Attach = unspecified gprs_attach_c 0x1 = GPRS attach comb_attach_c 0x2 = Combined GPRS/IMSI attach imsi_attach_c 0x3 = IMSI attach og_inter_sgsn_att_c 0x5 = Outgoing inter SGSN attach og_inter_papu_att_c 0x6 = Outgoing inter PAPU attach ra_update_c 0x10 RA update = type unspecified intra_papu_ra_upd_c 0x11 = Intra PAPU RA update inter_papu_ra_upd_c 0x12 = Inter PAPU RA update inter_sgsn_ra_upd_c 0x13 = Inter SGSN RA update inter_sg_ra_w_imsi_c 0x14 = Inter SGSN RA update with IMSI attach intra_papu_ra_imsi_c 0x15 = Intra PAPU RA update with IMSI attach inter_papu_ra_imsi_c 0x16 = Inter PAPU RA update with IMSI attach intra_papu_comb_upd_c 0x17 = Intra PAPU combined RA/LA update inter_papu_comb_upd_c 0x18 = Inter PAPU combined RA/A update inter_sgsn_comb_upd_c 0x19 = Inter SGSN combined RA/LA update periodic_comb_upd_c 0x1A = Periodic combined RA/LA update periodic_ra_upd_c 0x1B = Periodic RA update og_inter_papu_rau_c 0x1C = Outgoing inter PAPU RA update og_inter_sgsn_rau_c 0x1D = Outgoing inter SGSN RA update og_inter_sys_rau_c 0x1E = Outgoing inter SGSN RA update from 2G system to 3G. detach_c 0x20 = Detach. type unspecified pwr_off_detach_c 0x21 = Power off detach mo_gprs_detach_c 0x22 = MS-originated GPRS detach mo_comb_detach_c 0x23 = MS-originated GPRS/IMSI detach mo_imsi_detach_c 0x24 = MS-originated IMSI detach nwr_gprs_detach_c 0x25 = Network-requested GPRS detach nwr_comb_detach_c 0x26 = Network-requested GPRS/IMSI detach nwr_imsi_detach_c 0x27 = Network-requested IMSI detach impl_gprs_detach_c 0x28 = Implicit GPRS detach impl_comb_detach_c 0x29 = Implicit GPRS/IMSI detach purge_c 0x2A = Purge authentication_c 0x30 = Authentication ptmsi_realloc_c 0x31 = PTMSI reallocation imei_chk_c 0x32 = IMEI check identity_enq_c 0x33 = MS information enquiry DN05148836 Issue 2-2 Id:0900d805809551ce 399 .Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions undefined_c. ) Id:0900d805809551ce DN05148836 Issue 2-2 .or network-originated PDP context modification Context activation to another PAPU/SGSN param_chg_service_c 0x65 = HLR-initiated PDP context modification deact_service_c 0x66 = GMC-requested PDP context deactivation implicit_deact_c 0x67 = PDP context deactivation due to network status mo_sms_c 0xA0 = Mobile-originated SMS procedure mt_sms_c 0xA1 = Mobile-terminated SMS procedure pfc_download_c 0xB1 = BSS-initiated PFC download procedure pdp_context_inact_c 0xB2 = PDP context moves to inactive state pdp_context_active_c 0xB3 = PDP context moves to active state lic_deactivation_c 0xC0 = Lawful interception deactivation lic_request_c 0xC1 = Lawful interception request ssf_activity_test_c 0xC2 = The SCP sends ‘alive’ query to the SGSN ssf_continue_c 0xC3 = The SCP instructs the SGSN to continue processing bss_trace_act_c 0xC4 = Activation of BSS TRACE bss_trace_deact_c 0xC5 = Deactivation of BSS TRACE alert_req_c 0xC6 = Alert procedure og_inter_pa_3t2_sho_c 0xC7 = Outgoing inter PAPU RA update from 3G system to 2G og_inter_pa_2t3_sho_c 0xC8 = Outgoing inter PAPU RA update from 2G system to 3G intra_papu_relo_c 0xD0 = Intra PAPU relocation inter_papu_relo_c 0xD1 = Inter PAPU relocation inter_sgsn_relo_c 0xD2 = Inter SGSN relocation Table 472 400 Sgsn_Sms_Rtt_Cause_Proc (Cont.RTT report descriptions Possible values continued Traffica Reference Guide for SGSN Direct Interface cs_call_c 0x34 = CS call gmm_rel_c 0x35 = GMM connection release detach_by_timer_c 0x36 = Detach timer expired lic_activation_c 0x37 = Lawful interception resume_c 0x38 = Resume og_cs_call_c 0x39 = CS call indication to old location og_inter_s_rau_relo_c 0xD7 = Outgoing inter SGSN RAU after relocation og_inter_p_rau_relo_c 0xD8 = Outgoing inter PAPU RAU after relocation inter_p_i_ra_up_rel_c 0x3A = Inter PAPU RAU after relocation with IMSI inter_s_i_ra_up_rel_c 0x3B = Inter SGSN RAU after relocation with IMSI inter_p_c_ra_up_rel_c 0x3C = Inter PAPU combined RAU after relocation inter_s_c_ra_up_rel_c 0x3D = Inter SGSN combined RAU after relocation mo_activation_c 0x60 = MS-requested PDP context activation nwr_activation_c 0x61 = Network-requested PDP context activation mo_deactivation_c 0x62 = MS-requested PDP context deactivation nwr_deactivation_c 0x63 = Network-requested PDP context deactivation modify_service_c 0x64 = Mobile. for example in RNC reset iu_release_c 0xE2 = Releasing one Iu connection iu_sign_conn_rel_c 0xE3 = Releasing one Iu connection intra_papu_2t3_sho_c 0xE4 Intra PAPU inter system RAU from 2G system to 3G intra_p_2t3_imsi_c 0xE5 = Intra PAPU inter system RAU from 2G system to 3G with IMSI attach intra_p_2t3_comb_c 0xE6 = Combined intra PAPU inter system RAU from 2G system to 3G intra_papu_3t2_sho_c 0xE7 = Intra PAPU inter system RAU from 3G system to 2G intra_p_3t2_imsi_c 0xE8 = Intra PAPU inter system RAU from 3G system to 2G with IMSI attach intra_p_3t2_comb_c 0xE9 = Combined intra PAPU inter system RAU from 3G system to 2G inter_papu_2t3_sho_c 0xEA Inter PAPU inter system RAU from 2G system to 3G inter_p_2t3_imsi_c 0xEB Inter PAPU inter system RAU from 2G system to 3G with IMSI attach inter_p_2t3_comb_c 0xEC = Combined inter PAPU inter system RAU from 2G system to 3G inter_papu_3t2_sho_c 0xED = Inter PAPU inter system RAU from 3G system to 2G inter_p_3t2_imsi_c 0xEE = Inter PAPU inter system RAU from 3G system to 2G with IMSI attach inter_p_3t2_comb_c 0xEF = Combined intra PAPU inter system RAU from 3G system to 2G rab_create_c 0xF0 = RAB create gmm_info_c 0xF1 = GMM information 0x22 mo_gprs_detach_c MS originated GPRS detach 0x23 mo_comb_detach_c MS originated GPRS/IMSI detach 0x24 mo_imsi_detach_c MS originated IMSI detach 0x25 nwr_gprs_detach_c Network requested GPRS detach 0x26 nwr_comb_detach_c Network requested GPRS/IMSI detach 0x27 nwr_imsi_detach_c Network requested IMSI detach 0x28 impl_gprs_detach_c Implicit GPRS detach 0x29 impl_comb_detach_c Implicit GPRS/IMSI detach Table 472 Sgsn_Sms_Rtt_Cause_Proc (Cont.) DN05148836 Issue 2-2 Id:0900d805809551ce 401 .Traffica Reference Guide for SGSN Direct Interface Possible values continued RTT report descriptions og_inter_papu_relo_c 0xD3 = Outgoing inter PAPU relocation og_inter_sgsn_relo_c 0xD4 = Outgoing inter SGSN relocation inter_p_ra_upd_relo_c 0xD5 = Inter PAPU RAU after relocation inter_s_ra_upd_relo_c 0xD6 = Inter SGSN RAU after relocation intra_p_rau_relo_c 0xD9 = Intra PAPU RAU after relocation service_request_c 0xE0 = Service request iu_reset_c 0xE1 = Releasing one or more Iu connection. PDP context is active and this event activates it in the new unit. Used when subscriber is attached and has an active pdp-context.When Inter-PAPU RAU with PDP context is made. Sgsn_Cause_ini informs why the procedure told in Sgsn_Cause_proc started in the first place.RTT report descriptions Possible values (continued) Traffica Reference Guide for SGSN Direct Interface 0x30 Authentication_c Authentication 0x31 ptmsi_realloc_c PTMSI reallocation 0x32 imei_chk_c IMEI check 0x33 identity_enq_c MS information enquiry 0x34 cs_call_c CS call 0x35 gmm_rel_c GMM connection release 0x36 Subscriber is detached because of detach timer 0x37 Subscriber is set to interception 0x38 GIPPRB indicates GMGPRB about ending of CS call 0x60 mo_activation_c Mobile requested PDP context activation 0x61 nwr_activation_c Network requested PDP context activation 0x62 mo_deactivation_c Mobile requested PDP context deactivation 0x63 nwr_deactivation_c Network requested PDP context deactivation 0x64 modify_service_c Context activation to another PAPU/SGSN. It is quite normal during inter-unit raus. 0x67 implicit_deact_c PDP context deactivation due to network status 0xA0 mo_sms_c Mobile originated SMS delivery 0xA1 mt_sms_c Mobile terminated SMS delivery 0x2A Detached user is removed from SGSN. In the old unit the PDP context is deactivated with event 0x66 GMC requested PDP context activation. 0x65 param_chg_service_c HLR initiated PDP context modification 0x66 deact_service_c GMC requested PDP context deactivation. and subscriber performs inter-papu or inter-sgsn rau. Field exists in the database Table 472 Downlink_Data Sgsn_Sms_Rtt_Cause_Proc (Cont.) Field name Sgsn_Sms_Rtt_Cause_Ini Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains initiation causes for SGSN cause. It is used to remove the PDP-context from the old unit when the pdp-context has moved successfully to new unit/sgsn. Table 473 402 Sgsn_Sms_Rtt_Cause_Ini Id:0900d805809551ce DN05148836 Issue 2-2 . Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions 0x0 – 0xFF undefined_c 0xFF = Initialisation value. while MS was already attached. undefined ms_initiated_c 0x0 = MS-initiated nw_initiated_c 0x1 = Network-initiated rej_ra_upd_c 0x2 = Rejected inter PAPU/SGSN routing area update rej_attach_c 0x3 = Rejected GPRS attach rej_auth_c 0x4 = Failed authentication ra_upd_c 0x5 = For security procedures attach_c 0x6 = Reattach from MS Reattach from MS. the SM deactivates context no_sgsn_resources_c 0x23 = SGSN has no resources to finish the requested operation remote_release_c 0x24 = Data link has been released by the MS detach_c 0x25 = GPRS detach mnr_c 0x26 = The MS is unreachable inter_sgsn_rau_c 0x27 = Inter SGSN routing area update inter_papu_rau_c 0x28 = Inter PAPU routing area update og_inter_sgsn_rau_c 0x29 = Inter SGSN routing area update to new SGSN og_inter_papu_rau_c 0x2A = Inter PAPU routing area update to new PAPU failed_imei_chk_c 0x2B = IMEI check failed ll_fail_c 0x2C = Lower layer failure cs_call_c 0x2D = Circuit switched call no_resources_c 0x2E = The MS requests context deactivation due to the lack of resources unsupp_llc_sapi_c 0x2F = The MS does not accept SAPI in MO PDP context activation u_context_in_ggsn_c 0x30 = GGSN has no context to send the MS's data packet llc_fail_c 0x31 = GIPPRB out of order gsp_exp_c 0x32 = GSPPRB's timer expiry Table 473 Sgsn_Sms_Rtt_Cause_Ini (Cont.) DN05148836 Issue 2-2 Id:0900d805809551ce 403 . implicit detach for old mm-context will be initiated before new attach can be processed sm_proc_c 0x7 = For security procedures gsms_proc_c 0x8 = For security procedures mmi_c 0x9 = For security procedures reatt_req_c 0xC = The MS is requested to perform a GPRS detach and a new attach scp_initiated_c 0xD = SCP-initiated procedure hlr_initiated_c 0x20 = HLR-initiated procedure qos_not_accepted_c 0x21 = The MS starts deactivation during MO activation ggsn_recovery_c 0x22 = GGSN has been reset. RTT report descriptions Possible values. the cancel location timer has expired e_est_c 0x6A = Ack context re-establishment o_pdp_in_gtp_c 0x6B = Unknown PDP context in GTP o_pdp_in_ggsn_c 0x6C = Unknown PDP context in GGSN lr_detach_c 0x6D = HLR initiated detach.) Field name Sgsn_Sms_Rtt_Cause_Family Datatype in IDS UINT16 SGSN version >=SG4 Table 474 404 Sgsn_Sms_Rtt_Cause_Family Id:0900d805809551ce DN05148836 Issue 2-2 . continued Traffica Reference Guide for SGSN Direct Interface ms_reachab_exp_c 0x33 = MS reachable timer expiry gip_mas_ann_c 0x34 = GIPPRB's master detected that GIPPRB's slave is out of order og_attach_c 0x35 = Outgoing attach (attach in new SGSN) smmu_reset_c 0x36 = Leads to detach and activation rejection time_quota_c 0x37 = Frozen hand process leads to release llc_sndcp_error_c 0x38 = Error occurred in SNDCP/LLC layer ggsn_initiated_c 0x39 = Indicates that a GGSN-initiated PDP Context Modification is started ptmsi_realloc_c 0x50 = PTMSI reallocation procedure identity_enq_c 0x51 = Identity enquiry procedure auth_c 0x52 = Authentication procedure int_sgsn_rau_det_c 0x60 = Inter PAPU and inter SGSN situations: PDPdetach request is received in RAU intra_p_rau_det_c 0x61 = Intra PAPU situation: pdp-detach request is received in RAU int_sgsn_uns_det_c 0x62 = Used in inter SGSN RAU situations when both CRs are full pwr_off_detach_c 0x63 = The MS has made a power off detach mo_activation_c 0x64 = The MS has tried to activate the same context twice og_inter_papu_att_c 0x65 = Inter PAPU attach og_inter_sgsn_att_c 0x66 = Inter SGSN attach intra_papu_rau_c 0x67 = Intra PAPU routing area update g_att_clo_exp_c 0x68 = Inter SGSN attach. the cancel location timer has expired g_rau_clo_exp_c 0x69 = Inter SGSN RAU. necessary for PDP context bss_initiated_c 0x70 = BSS PFC download/modify procedures og_inter_sys_rau_c 0x71 = Outgoing inter system RA update cell_change_c 0x72 = PDP context modification initiated by cell change Field exists in the database Table 473 Cause_Ini Sgsn_Sms_Rtt_Cause_Ini (Cont. Possible values In case of Sgsn_Cause_Cause is not success_c. possible Sgsn_Cause_Family values are: 0x408 = gtpprb. GPRS Mobility and Session Manager 0x440 = gs1prb.) Field name Sgsn_Sms_Rtt_Cause_Cause Datatype in IDS UINT32 SGSN version >=SG4 Explanation This field contains error cause of SGSN. Sgsn in control application 0x403 = ggbprb. GPRS IP Backbone Tunneling Protocol 0x632 = gcsprb. Possible values Field exists in the database Table 476 Cause_Int_Cause Sgsn_Sms_Rtt_Cause_Int_Cause DN05148836 Issue 2-2 Id:0900d805809551ce 405 . GPRS GB Interface protocol stack 0x3FF = gipprb. GPRS short message delivery service 0x409 = gspprb. GPRS Charging and Statistics Combiner Program Block 0x40A = gmgprb. GPRS Mobility and Session Management Protocol 0x404 = grnprb. This field value is useful in program block designing when tracing faults. NOTE: STATISTICAL MEASUREMENTS SHOULD BE DONE ACCORDING TO EXTERNAL CAUSE CODE FIELDS Sgsn_PS_External_Cause AND Sgsn_CS_External_Cause.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Explanation This field contains the family identifier of a process who set the cause code. SGSN PM COUNTERS ARE UPDATED ACCORDING TO EXTERNAL CAUSE CODE VALUES. Using family and int_cause fields you can find the exact code line where the cause was set. GPRS Air Interface Transport Protocols Field exists in the database Table 474 Cause_Family Sgsn_Sms_Rtt_Cause_Family (Cont. Possible values See Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause Field exists in the database Cause_Cause Table 475 Sgsn_Sms_Rtt_Cause_Cause Field name Sgsn_Sms_Rtt_Cause_Int_Cause Datatype in IDS UINT16 SGSN version >=SG4 Explanation Internal cause is meant only for the use of program block that has set it and it's not customer documented. GPRS subscriber registration services 0x582 = sgiprb. RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Sms_Rtt_Sms_Length Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the length of SMS user data including addresses, types and SMS text. Possible values Field exists in the database Table 477 Sms_Length Sgsn_Sms_Rtt_Sms_Length Field name Sgsn_Sms_Rtt_Charging_Info Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains charging characteristics of the user. Possible values Possible values for charging type are: 0 = no_def 1 = hot_billing 2 = flat_rate 4 = prepaid 8 = normal Possible additional values are: 16 = cell_update 32 = in_prepaid in_prepaid or cell_update cannot alone be the charging info value. They are always added to charging type values if they are used. Examples: Normal + in prepaid = 8 + 32 = 40 Prepaid + cell update = 4 + 16 = 20 Depending on the character, different CDR creation triggers are used: for GPRS server based prepaid users, the prepaid triggers are used and for other users, the normal triggers are used. The separate prepaid triggers enable charging to be more real time for the prepaid subscribers than for the other subscribers. There is also a parameter for the flat rate CDR generation. The flat rate CDR generation can be turned off if, for example, the charging load becomes too high. The IN prepaid CDRs are created according to the normal CDR triggers Field exists in the database Table 478 Charging_Info Sgsn_Sms_Rtt_Charging_Info Field name Sgsn_Sms_Rtt_SMS_Nbr_Add_length Datatype in IDS UINT8 Table 479 406 Sgsn_Sms_Rtt_SMS_Nbr_Add_length Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface RTT report descriptions SGSN version >=SG4 Explanation This field contains the length of an address. If RTT is not sent to Traffica because of mobile originated SMS, the value is set to 0x0. Possible values 0x0 - 0xFF Field exists in the database SMS_Nbr_Add_length Table 479 Sgsn_Sms_Rtt_SMS_Nbr_Add_length (Cont.) Field name Sgsn_Sms_Rtt_SMS_Nbr_Indicators Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains address indicators of addresses used in MAPSgsn_SMS_Dest_Nbr_Indicators is a packed struct including three parts: * nbr_plan (0:15) Numbering Plan indicator * na_of_ad (0:7) Nature of address indicator * ext (0:1) Extension indicator If RTT is not sent to traffica because of mobile originated SMS the value is set to 0x0. Possible values Field exists in the database Table 480 SMS_Nbr_Indicators Sgsn_Sms_Rtt_SMS_Nbr_Indicators Field name Sgsn_SMS_Nbr_Numbers Datatype in IDS UINT8 SGSN version >=SG4 Explanation If this field value is something other than zero, attached subscriber is roaming from VPLMN. Possible values This field contains SMS destination number in case of MO SMS or calling party number in case of MT SMS. Field contents are: array(9) OF double_digit; one double_digit field is of size byte. Msisdn is stored in decimal format and the endmark is 0xF. Double_digit has two parts, lower_digit(4bits) and upper_digit(4bits). For example, if the destination number is 420018000100001 the Sgsn_SMS_Nbr_Numbers field is: 24 00 81 00 10 00 00 F1 FF. If RTT is not sent to Traffica because of mobile originated SMS ormobile terminated SMS, the value is set to 0x0. The number is in the international E.164 format. Field exists in the database Table 481 Sgsn_SMS_Nbr_Numbers Field name Table 482 SMS_Nbr_Numbers Sgsn_Sms_Rtt_Ra_Access_Type Sgsn_Sms_Rtt_Ra_Access_Type DN05148836 Issue 2-2 Id:0900d805809551ce 407 RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Datatype in IDS UINT8 SGSN version >=SG6 Explanation The type of the radio access network. Possible values utran_c = 0x01 geran_c = 0x02 distr_uma_c = 0xD0 ihspa_c = 0xD2 not_def_c = 0xFF Field exists in the database Table 482 Ra_Access_Type Sgsn_Sms_Rtt_Ra_Access_Type (Cont.) Field name Sgsn_Sms_Rtt_Rnc_Address_Mcc Datatype in IDS UINT16 SGSN version >=SG6 Explanation RNC’s country code. Possible values This field contains the country code. Field contents are: array(2) OF double_digit one double_digit field is of size byte. Mcc is stored in decimal format and the endmark is 0xF. Double_digit has two parts, lower_digit (4bits) and upper_digit (4bits). For example, if Mcc is 358 the Sgsn_Cgi_Mcc field is:53 F8 Field exists in the database Table 483 Rnc_Address_Mcc Sgsn_Sms_Rtt_Rnc_Address_Mcc Field name Sgsn_Sms_Rtt_Rnc_Address_Mnc Datatype in IDS UINT16 SGSN version >=SG6 Explanation This field contains mobile network code Possible values Field contents are: array(2) OF double_digit one double_digit field is of size byte Mnc is stored in decimal format and the endmark is 0xF Double_digit has two parts, lower_digit(4bits) and upper_digit(4bits). For example, if Mnc is 400 the Sgsn_Cgi_Mcc field is:04 F0. Field exists in the database Table 484 408 Rnc_Address_Mnc Sgsn_Sms_Rtt_Rnc_Address_Mnc Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Sms_Rtt_Rnc_Id Datatype in IDS UINT16 SGSN version >=SG6 Explanation RNC’s identifier. (UMTS 25.413). Possible values RNC’s identifier Field exists in the database Rnc_Id Table 485 RTT report descriptions Sgsn_Sms_Rtt_Rnc_Id Field name Sgsn_Sms_Rtt_Sai_Mcc Datatype in IDS BCDREV8(2) SGSN version >=SG6 Explanation The country code of the service area Possible values This field contains country code. Field contents are: array(2) OF double_digit; one double_digit field is of size byte. Mcc is stored in decimal format and the end mark is 0xF. Double_digit has two parts, lower_digit(4bits) and upper_digit(4bits). for example, if Mcc is 358 the Sgsn_Cgi_Mcc field is:53 F8 Field exists in the database Table 486 Sai_Mcc Sgsn_Sms_Rtt_Sai_Mcc Field name Sgsn_Sms_Rtt_Sai_Mnc Datatype in IDS BCDREV8(2) SGSN version >=SG6 Explanation The mobile network code of the service area Possible values Field contents are: array(2) OF double_digit; one double_digit field is of size byte. Mnc is stored in decimal format and the end mark is 0xF. Double_digit has two parts, lower_digit (4bits) and upper_digit (4bits). For example, if Mnc is 400 the Sgsn_Cgi_Mnc field is: 04 F0. Field exists in the database Table 487 Sai_Mnc Sgsn_Sms_Rtt_Sai_Mnc Field name Sgsn_Sms_Rtt_Sai_Lac Datatype in IDS UINT16 SGSN version >=SG6 Table 488 Sgsn_Sms_Rtt_Sai_Lac DN05148836 Issue 2-2 Id:0900d805809551ce 409 RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Explanation The location area code of the service area. Possible values 0x1 – 0xFFFF Field exists in the database Sai_Lac Table 488 Sgsn_Sms_Rtt_Sai_Lac (Cont.) Field name Sgsn_Sms_Rtt_Sai_Sac Datatype in IDS UINT16 SGSN version >=SG6 Explanation Service area identity (SAC, UMTS 25.401). Possible values 0x1 – 0xFFFF Field exists in the database Sai_Sac Table 489 Sgsn_Sms_Rtt_Sai_Sac Field name Sgsn_Sms_Rtt_Physical_Smmu_Id Datatype in IDS UINT8 SGSN version >=SG6 Explanation Physical Smmu Id Number Possible values 0x1 – 0xFF Field exists in the database Physical_Smmu_Id Table 490 Sgsn_Sms_Rtt_Physical_Smmu_Id Field name Sgsn_Sms_Rtt_Event_Start_Time Datatype in IDS BCDTIME SGSN version >=SG6 Explanation The time when the event was started Possible values Time is in format hundredsofseconds:seconds:minutes:hours. Field exists in the database Event_Start_Time Table 491 Sgsn_Sms_Rtt_Event_Start_Time Field name Sgsn_Sms_Rtt_Event_Start_Date Datatype in IDS BCDDATE SGSN version >=SG6 Explanation The date when the event was started Possible values Date is in format day:month:year. Table 492 410 Sgsn_Sms_Rtt_Event_Start_Date Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Field exists in the database Table 492 RTT report descriptions Event_Start_Date Sgsn_Sms_Rtt_Event_Start_Date (Cont.) Field name Sgsn_Sms_Rtt_Event_Stop_Time Datatype in IDS BCDTIME SGSN version >=SG6 Explanation The time when the event was stopped Possible values Time is in format hundredsofseconds:seconds:minutes:hours. Field exists in the database Event_Stop_Time Table 493 Sgsn_Sms_Rtt_Event_Stop_Time Field name Sgsn_Sms_Rtt_Event_Stop_Date Datatype in IDS BCDDATE SGSN version >=SG6 Explanation The date when the event was stopped. Possible values Date is in format day:month:year. Field exists in the database Event_Stop_Date Table 494 Sgsn_Sms_Rtt_Event_Stop_Date 6.10 PDP_THR_STAT fields The following table shows the PDP_THR_STAT fields: Traffic News event type SGSN_PDP_THR_STAT_EVENT Database table <SGSN_Release_Id>_PDP_THR_STAT Table 495 SGSN_PDP_THR_STAT fields The database column names are the same as the IDS field names without the Sgsn_PDP_THR_STAT prefix. For example, the Sgsn_PDP_THR_STAT_Report_Count IDS field is the Report_Count column in database table <SGSN_Release_Id>_PDP_THR_STAT. The Traffic News field names are the same as the database column names but use spaces instead of underscores between words. For example, the Sgsn_PDP_THR_STAT_Report_Count IDS field is Report Count field in Traffic News SGSN_PDP_THR_STAT_EVENT. The database column SQL data types can be found in the workspace configuration file dbd_sgsn_pdp_thr_stat.conf. Under the <SGSN_Release_Id>_PDP_THR_STAT section, there is a single-row entry for each table column. The SQL datatype appears after the column name and “=” symbol. DN05148836 Issue 2-2 Id:0900d805809551ce 411 RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Pdp_Thr_Stat_Report_Id Data type in the IDS UINT16 SGSN version >=SG6 Explanation Contains information on the report type. NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field, because the possible values can and will change in the future. Possible values Field exists in the database Table 496 Sgsn_Pdp_Thr_Stat_Report_Id Field name Sgsn_Pdp_Thr_Stat_Report_Length Data type in the IDS UINT16 SGSN version >=SG6 Explanation This field contains the length of report in bytes. This field is needed because empty cells are dropped from pdp_thr_stat_table. Possible values 0x0 - 0xFFFF Field exists in the database Report_Length Table 497 Sgsn_Pdp_Thr_Stat_Report_Length Field name Sgsn_Pdp_Thr_Stat_Report_Count Data type in the IDS UINT32 SGSN version >=SG6 Explanation Contains information on how many reports of this type have been sent to Traffica. Possible values Field exists in the database Table 498 Report_Count Sgsn_Pdp_Thr_Stat_Report_Count Field name Sgsn_Pdp_Thr_Stat_Report_Time Data type in the IDS UINT32 SGSN version BDCTIME Explanation The time when the report was sent to Traffica. Possible values Field exists in the database Table 499 412 Sgsn_Pdp_Thr_Stat_Report_Time and Sgsn_Pdp_Thr_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Sgsn_Pdp_Thr_Stat_Report_Time Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Pdp_Thr_Stat_Report_Date Data type in the IDS BDCDATE SGSN version >=SG6 Explanation The date when the report was sent to Traffica. RTT report descriptions Possible values Field exists in the database Table 500 Sgsn_Pdp_Thr_Stat_Report_Time and Sgsn_Pdp_Thr_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Sgsn_Pdp_Thr_Stat_Report_Date Field name Sgsn_Pdp_Thr_Stat_Papu_Capa Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains the subscriber capacity of particular PAPU in SGSN. Possible values 0x41 = maximum of 65 000 attached subscribers 0x64 = maximum of 100 000 attached subscribers 0xFA = maximum of 250 000 attached subscribers Field exists in the database Table 501 Papu_Capa Sgsn_Pdp_Thr_Stat_Papu_Capa Field name Sgsn_Pdp_Thr_Stat_Papu_Group_Id Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains PAPU group id. Possible values 0-255. This field is always 0 if feature, FNSG01060, Large RA Support isn’t activated.Value 0 means that PAPU doesn’t belong to any group. Field exists in the database Papu_Group_Id Table 502 Sgsn_Pdp_Thr_Stat_Papu_Group_Id Field name Sgsn_Pdp_Thr_Stat_Pdp_Cxt_Element_Count Datatype in IDS UINT16 SGSN version >=SG6 Explanation Number of PDP Context element Possible values 0x1 – 0xFFFF Field exists in the database Pdp_Cxt_Element_Count Table 503 Sgsn_Pdp_Thr_Stat_Pdp_Cxt_Element_Count DN05148836 Issue 2-2 Id:0900d805809551ce 413 RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Pdp_Thr_Stat_Logical_Papu_Id Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains the logical index of PAPU. Possible values 0x1 – 0xFF Field exists in the database Logical_Papu_Id Table 504 Sgsn_Pdp_Thr_Stat_Logical_Papu_Id Field name Sgsn_Pdp_Thr_Stat_Physical_Papu_Id Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains the physical index of PAPU. Possible values 0x1 – 0xFF Field exists in the database Physical_Papu_Id Table 505 Sgsn_Pdp_Thr_Stat_Physical_Papu_Id Field name Sgsn_Pdp_Thr_Stat_Last_2bytes_Ggsn_Address Datatype in IDS UINT16 SGSN version >=SG6 Explanation Last two bytes from Ggsn Ip-Address Possible values 0x1 – 0xFFFF Field exists in the database Last_2bytes_Ggsn_Address Table 506 Sgsn_Pdp_Thr_Stat_Last_2bytes_Ggsn_Address Field name Sgsn_Pdp_Thr_Stat_Charging_Index Datatype in IDS UINT32 SGSN version >=SG6 Explanation This field contains the index of charging Possible values 0x1 – 0xFFFFFFFF Field exists in the database Charging_Index Table 507 Sgsn_Pdp_Thr_Stat_Charging_Index Field name Sgsn_Pdp_Thr_Stat_Duration Datatype in IDS UINT8 Table 508 414 Sgsn_Pdp_Thr_Stat_Duration Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG6 Explanation This field contains the duration Possible values 0x1 – 0xFF Field exists in the database Duration Table 508 Sgsn_Pdp_Thr_Stat_Duration (Cont.) Field name Sgsn_Pdp_Thr_Stat_Ts_Time Datatype in IDS BCDTIME SGSN version >=SG6 Explanation The time when the TS was started Possible values Time is in format hundredsofseconds:seconds:minutes:hours. Field exists in the database Ts_Time Table 509 Sgsn_Pdp_Thr_Stat_Ts_Time Field name Sgsn_Pdp_Thr_Stat_Qos_Negotiated_Ms_Cont_Prof_Flag Datatype in IDS UINT8 SGSN version >=SG6 Explanation Field of Quality of Service that user requests Possible values 0x0 = Release 97/980x1 = Release 99 Field exists in the database Qos_Negotiated_Ms_Cont_Prof_Flag Table 510 RTT report descriptions Sgsn_Pdp_Thr_Stat_Qos_Negotiated_Ms_Cont_Prof_Flag Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Alloc_Retention Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x0 - 0xFF Field exists in the database Negotiated_QoS_Alloc_Retention Table 511 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Alloc_Retention Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Deliv_Of_Erroneous Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Table 512 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Deliv_Of_Erroneous DN05148836 Issue 2-2 Id:0900d805809551ce 415 RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Possible values Field exists in the database Table 512 Negotiated_QoS_Deliv_Of_Erroneous Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Deliv_Of_Erroneous (Cont.) Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Delivery_Order Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values Field exists in the database Table 513 Negotiated_QoS_Delivery_Order Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Delivery_Order Field name Sgsn_Pdp_Thr_Stat_Qos_Negotiated_1 Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x00-0xFF Field exists in the database Qos_Negotiated_1 Table 514 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_1 Field name Sgsn_Pdp_Thr_Stat_Qos_Negotiated_2 Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x00-0xFF Field exists in the database Qos_Negotiated_2 Table 515 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_2 Field name Sgsn_Pdp_Thr_Stat_Qos_Negotiated_3 Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x00-0xFF Field exists in the database Qos_Negotiated_3 Table 516 416 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_3 Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Pdp_Thr_Stat_Qos_Negotiated_4 Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x00-0xFF Field exists in the database Qos_Negotiated_5 Table 518 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_5 Field name Sgsn_Pdp_Thr_Stat_Qos_Negotiated_6 Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x00-0xFF Field exists in the database Qos_Negotiated_6 Table 519 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_6 Field name Sgsn_Pdp_Thr_Stat_Qos_Negotiated_7 Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x00-0xFF Field exists in the database Qos_Negotiated_7 Table 520 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_7 Field name Sgsn_Pdp_Thr_Stat_Qos_Negotiated_8 Datatype in IDS UINT8 Table 521 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_8 DN05148836 Issue 2-2 Id:0900d805809551ce 417 . Possible values 0x00-0xFF Field exists in the database Qos_Negotiated_4 Table 517 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_4 Field name Sgsn_Pdp_Thr_Stat_Qos_Negotiated_5 Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x00-0xFF Field exists in the database Qos_Negotiated_8 Table 521 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_8 (Cont.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x00-0xFF Field exists in the database Qos_Negotiated_9 Table 522 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_9 Field name Sgsn_Pdp_Thr_Stat_Qos_Negotiated_10 Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Table 525 418 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_12 Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values 0x00-0xFF Field exists in the database Qos_Negotiated_10 Table 523 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_10 Field name Sgsn_Pdp_Thr_Stat_Qos_Negotiated_11 Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x00-0xFF Field exists in the database Qos_Negotiated_11 Table 524 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_11 Field name Sgsn_Pdp_Thr_Stat_Qos_Negotiated_12 Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.) Field name Sgsn_Pdp_Thr_Stat_Qos_Negotiated_9 Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values Field exists in the database Table 529 Negotiated_QoS_Max_Sdu_Size Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Max_Sdu_Size DN05148836 Issue 2-2 Id:0900d805809551ce 419 . Field exists in the database Negotiated_QoS_Traffic_Class Table 528 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Traffic_Class Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Max_Sdu_Size Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.) Field name Sgsn_Pdp_Thr_Stat_Qos_Negotiated_13 Datatype in IDS UINT8 SGSN version >=SG7 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x00-0xFF Field exists in the database Qos_Negotiated_13 Table 526 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_13 Field name Sgsn_Pdp_Thr_Stat_Qos_Negotiated_14 Datatype in IDS UINT8 SGSN version >=SG7 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.Traffica Reference Guide for SGSN Direct Interface Possible values 0x00-0xFF Field exists in the database Qos_Negotiated_12 Table 525 RTT report descriptions Sgsn_Pdp_Thr_Stat_Qos_Negotiated_12 (Cont. Possible values 0x00-0xFF Field exists in the database Qos_Negotiated_14 Table 527 Sgsn_Pdp_Thr_Stat_Qos_Negotiated_14 Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Traffic_Class Datatype in IDS UINT8 SGSN version >=SG6 Explanation Possible values Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values Field exists in the database Table 530 Negotiated_QoS_Max_Bitrate_Ul Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Max_Bitrate_Ul Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Max_Bitrate_Dl Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values Field exists in the database Table 531 Negotiated_QoS_Max_Bitrate_Dl Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Max_Bitrate_Dl Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Sdu_Error_Ratio Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values Field exists in the database Table 532 Negotiated_QoS_Sdu_Error_Ratio Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Sdu_Error_Ratio Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Residual_Ber Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Max_Bitrate_Ul Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values Field exists in the database Table 533 Negotiated_QoS_Residual_Ber Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Residual_Ber Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Traffic_Handling_Prio Datatype in IDS UINT8 Table 534 420 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Traffic_Handling_Prio Id:0900d805809551ce DN05148836 Issue 2-2 . Traffica Reference Guide for SGSN Direct Interface RTT report descriptions SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.) Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Transfer_Delay Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values Field exists in the database Table 534 Negotiated_QoS_Traffic_Handling_Prio Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Traffic_Handling_Prio (Cont. Possible values Field exists in the database Table 537 Negotiated_QoS_Guaran_Bit_Rate_Dl Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Guaran_Bit_Rate_Dl Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Spare Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values Field exists in the database Table 535 Negotiated_QoS_Transfer_Delay Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Transfer_Delay Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Guaran_Bit_Rate_Ul Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values Field exists in the database Table 536 Negotiated_QoS_Guaran_Bit_Rate_Ul Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Guaran_Bit_Rate_Ul Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Guaran_Bit_Rate_Dl Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Table 538 Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Spare DN05148836 Issue 2-2 Id:0900d805809551ce 421 . Possible values Field exists in the database Table 539 Negotiated_QoS_Signalling_Indication Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Signalling_Indication Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Source_Statistics Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values Field exists in the database Table 540 Negotiated_QoS_Source_Statistics Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Source_Statistics Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Ext_Max_Bit_Rate_Dl Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Possible values Field exists in the database Table 538 Negotiated_QoS_Spare Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Spare (Cont. Possible values Field exists in the database Table 542 422 Negotiated_QoS_Ext_Guaran_Bit_Rate_Dl Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Ext_Guaran_Bit_Rate_Dl Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values Field exists in the database Table 541 Negotiated_QoS_Ext_Max_Bit_Rate_Dl Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Ext_Max_Bit_Rate_Dl Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Ext_Guaran_Bit_Rate_Dl Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.) Field name Sgsn_Pdp_Thr_Stat_Negotiated_QoS_Signalling_Indication Datatype in IDS UINT8 SGSN version >=SG6 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Uplink_Data Table 545 Sgsn_Pdp_Thr_Stat_Uplink_Data Field name Sgsn_Pdp_Thr_Stat_Downlink_Data Datatype in IDS UINT32 SGSN version >=SG6 Explanation Downlink data amount in bytes.Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Pdp_Thr_Stat_Imsi_Length Datatype in IDS UINT8 SGSN version >=SG6 Explanation The leght of IMSI Possible values 15-16 Field exists in the database Imsi_Length Table 543 Sgsn_Pdp_Thr_Stat_Imsi_Length Field name Sgsn_Pdp_Thr_Stat_Imsi Datatype in IDS BDCREV8(8) SGSN version >=SG6 Explanation Contains the IMSI-number that caused the report to be sent Possible values IMSI Field exists in the database Imsi Table 544 Sgsn_Pdp_Thr_Stat_Imsi Field name Sgsn_Pdp_Thr_Stat_Uplink_Data Datatype in IDS UINT32 SGSN version >=SG6 Explanation Uplink data amount in bytes. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Downlink_Data Table 546 Sgsn_Pdp_Thr_Stat_Downlink_Data Field name Sgsn_Pdp_Thr_Stat_Ra_Access_Type Datatype in IDS UINT8 Table 547 RTT report descriptions Sgsn_Pdp_Thr_Stat_Ra_Access_Type DN05148836 Issue 2-2 Id:0900d805809551ce 423 . For example. Sgsn_Cdr_Stat_Report_Count IDS field is Report Count field in Traffic News' SGSN_PAPU_USER_STAT_EVENT.) 6. Sgsn_PAPU_USER_STAT_Report_Count IDS field is Report_Count column in database table <SGSN_Release_Id>_PAPU_USER_STAT. Possible values Field exists in the database Table 549 424 Report_Id Sgsn_Papu_User_Stat_Report_Id Id:0900d805809551ce DN05148836 Issue 2-2 .conf. Traffic News field names are the same as database column names with spaces used instead of underscores between words. there is a single-row entry for each table column. Under [<SGSN_Release_Id>_PAPU_USER_STAT] section. For example.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG6 Explanation The type of the radio access network. because the possible values can and will change in the future. Database column SQL datatypes can be found in the workspace configuration file dbd_sgsn_cdr_stat. Possible values utran_c = 0x01 geran_c = 0x02 distr_uma_c = 0xD0 ihspa_c = 0xD2 not_def_c = 0xFF Field exists in the database Table 547 Ra_Access_Type Sgsn_Pdp_Thr_Stat_Ra_Access_Type (Cont. Field name Sgsn_Papu_User_Stat_Report_Id Datatype in IDS UINT16 SGSN version >=SG6 Explanation Contains information on the report type. NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field.11 PAPU_USER_STAT fields The following table shows the PAPU_USER_STAT fields: Traffic News event type SGSN_PAPU_USER_STAT_EVENT Database table <SGSN_Release_Id>_PAPU_USER_STAT Table 548 PAPU_USER_STAT fields Database column names are the same as IDS fields names without the Sgsn_PAPU_USER_STAT prefix. The SQL datatype appears after the column name and '=' sign. Sgsn_Papu_User_Stat_Report_Time and Sgsn_Papu_User_Stat_Report_Date are in column Report_Time as SQL TIMESTAMP format Table 552 Sgsn_Papu_User_Stat_Report_Time Field name Sgsn_Papu_User_Stat_Report_Date Datatype in IDS BCDDATE SGSN version >=SG6 Explanation The date when the report was sent to Traffica. This field is needed because empty cells are dropped from papu_user_stat_table. Possible values Field exists in the database Table 550 Report_Length Sgsn_Bssgp_Papu_Stat_Report_Length Field name Sgsn_Papu_User_Stat_Count Datatype in IDS UINT32 SGSN version >=SG6 Explanation Contains information on how many reports of this type have been send to Traffica The value of the counter is reset every day at 00:00 a.m.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Papu_User_Stat_Report_Length Datatype in IDS UINT16 SGSN version >=SG6 Explanation This field contains the length of report in bytes. Sgsn_Papu_User_Stat_Report_Time and Sgsn_Papu_User_Stat_Report_Date are in column Report_Time as SQL TIMESTAMP format Table 553 Sgsn_Papu_User_Stat_Report_Date DN05148836 Issue 2-2 Id:0900d805809551ce 425 . Possible values 0x0-0xFFFFFFFF Field exists in the database Yes. Possible values 0x0-0xFFFFFFFF Field exists in the database Report_Count Table 551 Sgsn_Papu_User_Stat_Report_Count Field name Sgsn_Papu_User_Stat_Report_Time Datatype in IDS BCDTIME SGSN version >=SG6 Explanation The time when the report was sent to Traffica Possible values 0x0-0xFFFFFFFF Field exists in the database Yes. Possible values 0x0-0xFF The value 0x23 is used for SMSS (SMSS do not go through PAPU). Field exists in the database Table 554 Papu_Id Sgsn_Papu_User_Stat_Papu_Id Field name Sgsn_Papu_User_Stat_Physical_Papu_Id Datatype in IDS UINT8 SGSN version >=SG3 Explanation This field contains the physical index of PAPU. Possible values 0x41 = maximum of 65 000 attached subscribers 0x64 = maximum of 100 000 attached subscribers 0xFA = maximum of 250 000 attached subscribers Field exists in the database Table 556 Papu_Capa Sgsn_Papu_User_Stat_Papu_Capa Field name Sgsn_Papu_User_Stat_Papu_Group_Id Datatype in IDS UINT8 SGSN version >=SG6 Table 557 426 Sgsn_Papu_User_Stat_Papu_Group_Id Id:0900d805809551ce DN05148836 Issue 2-2 . The logical PAPU id follows working PAPU in switchover. The value 0x28 is used if the physical PAPU id cannot be solved due to some internal error. The value 0x28 is used if the physical PAPU id cannot be solved due to some internal error. Field exists in the database Table 555 Physical_Papu_Id Sgsn_Papu_User_Stat_Physical_Papu_Id Field name Sgsn_Papu_User_Stat_Papu_Capa Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains the subscriber capacity of particular PAPU in SGSN.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Papu_User_Stat_Papu_Id Datatype in IDS UINT8 SGSN version >=SG3 Explanation Logical PAPU id. This means that the same logical PAPU id always refers to the same geographical area. Possible values 0x0-0xFF The value 0x23 is used for SMSS (SMSS do not go through PAPU). Possible values 0x1 – 0xFFFFFFFF Field exists in the database Attached_Gb_Users Table 559 Sgsn_Papu_User_Stat_Attached_Gb_Users Field name Sgsn_Papu_User_Stat_Open_Priority_Class_1_Pdp_Con Datatype in IDS UINT32 SGSN version >=SG6 Explanation Open priority class 1 PDP contexts (IU+GB). Possible values 0x1 – 0xFFFFFFFF Field exists in the database Attached_Iu_Users Table 558 Sgsn_Papu_User_Stat_Attached_Iu_Users Field name Sgsn_Papu_User_Stat_Attached_Gb_Users Datatype in IDS UINT32 SGSN version >=SG6 Explanation Amount of attached Gb-interface subscribers.Traffica Reference Guide for SGSN Direct Interface Explanation This field contains PAPU group id Possible values 0-255 RTT report descriptions This field is always 0 if feature. Value 0 means that PAPU does not belong to any group.) Field name Sgsn_Papu_User_Stat_Attached_Iu_Users Datatype in IDS UINT32 SGSN version >=SG6 Explanation Amount of attached Iu-interface subscribers. FNSG01060. Field exists in the database Table 557 Papu_Group_Id Sgsn_Papu_User_Stat_Papu_Group_Id (Cont. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Open_Priority_Class_1_Pdp_Con Table 560 Sgsn_Papu_User_Stat_Open_Priority_Class_1_Pdp_Con Field name Sgsn_Papu_User_Stat_Open_Priority_Class_2_Pdp_Con Datatype in IDS UINT32 SGSN version >=SG6 Table 561 Sgsn_Papu_User_Stat_Open_Priority_Class_2_Pdp_Con DN05148836 Issue 2-2 Id:0900d805809551ce 427 . Large RA Support is not activated. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Open_Priority_Class_3_Pdp_Con Table 562 Sgsn_Papu_User_Stat_Open_Priority_Class_3_Pdp_Con Field name Sgsn_Papu_User_Stat_Open_Priority_Class_4_Pdp_Con Datatype in IDS UINT32 SGSN version >=SG6 Explanation Open priority class 4 PDP contexts (IU+GB). Possible values 0x1 – 0xFFFFFFFF Field exists in the database Open_Priority_Class_4_Pdp_Con Table 563 Sgsn_Papu_User_Stat_Open_Priority_Class_4_Pdp_Con Field name Sgsn_Papu_User_Stat_Open_Priority_Class_Streaming_Pdp_Con Datatype in IDS UINT32 SGSN version >=SG6 Explanation Open priority streaming PDP contexts (IU+GB).) Field name Sgsn_Papu_User_Stat_Open_Priority_Class_3_Pdp_Con Datatype in IDS UINT32 SGSN version >=SG6 Explanation Open priority class 3 PDP contexts (IU+GB).RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Explanation Open priority class 2 PDP contexts (IU+GB). Possible values 0x1 – 0xFFFFFFFF Field exists in the database Open_Priority_Class_2_Pdp_Con Table 561 Sgsn_Papu_User_Stat_Open_Priority_Class_2_Pdp_Con (Cont. Possible values 0x1 – 0xFFFFFFFF Table 565 428 Sgsn_Papu_User_Stat_Open_Priority_Class_Conv_Pdp_Con Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values 0x1 – 0xFFFFFFFF Field exists in the database Open_Priority_Class_Streaming_Pdp_Con Table 564 Sgsn_Papu_User_Stat_Open_Priority_Class_Streaming_Pdp_Con Field name Sgsn_Papu_User_Stat_Open_Priority_Class_Conv_Pdp_Con Datatype in IDS UINT32 SGSN version >=SG6 Explanation Open priority conversational PDP contexts (IU+GB). Possible values 0x1 – 0xFFFFFFFF Field exists in the database Open_Iu_Pdp_Con Table 567 RTT report descriptions Sgsn_Papu_User_Stat_Open_Gb_Pdp_Con Field name Sgsn_Papu_User_Stat_Active_Users Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of active subscribers (having one or more active PDP contexts) Possible values 0x1 – 0xFFFFFFFF Field exists in the database Active_Users Table 568 Sgsn_Papu_User_Stat_Active_Users Field name Sgsn_Papu_User_Stat_Bandwidth_Allocated_By_Rt_Pdp_Con Datatype in IDS UINT32 SGSN version >=SG6 Explanation Real bandwidth used by priority class streaming and conversational pdp contexts.Traffica Reference Guide for SGSN Direct Interface Field exists in the database Table 565 Open_Priority_Class_Conv_Pdp_Con Sgsn_Papu_User_Stat_Open_Priority_Class_Conv_Pdp_Con (Cont. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Bandwidth_Allocated_By_Rt_Pdp_Con Table 569 Sgsn_Papu_User_Stat_Bandwidth_Allocated_By_Rt_Pdp_Con DN05148836 Issue 2-2 Id:0900d805809551ce 429 .) Field name Sgsn_Papu_User_Stat_Open_Gb_Pdp_Con Datatype in IDS UINT32 SGSN version >=SG6 Explanation Open Gb-interface PDP contexts. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Open_Gb_Pdp_Con Table 566 Sgsn_Papu_User_Stat_Open_Gb_Pdp_Con Field name Sgsn_Papu_User_Stat_Open_Iu_Pdp_Con Datatype in IDS UINT32 SGSN version >=SG6 Explanation Iu-interface PDP contexts. Possible values 0 – 64000 0xFFFF = Feature SG01007 not in use Table 573 430 Sgsn_Papu_User_Stat_Bandwidth_Limit_For_Rt_Pdp_Ctxs Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values 0x1 – 0xFFFFFFFF Field exists in the database Average_Bandwidth_Used_By_Rt_Pdp_Con Table 570 Sgsn_Papu_User_Stat_Average_Bandwidth_Used_By_Rt_Pdp_Con Field name Sgsn_Papu_User_Stat_Rt_Pdp_Ctx_Capacity Datatype in IDS UINT16 SGSN version >=SG6 Explanation Tells how many per cent of PAPU capacity is allowed for RT PDP contexts. Possible values 0 – 100 0xFFFF = Feature SG01007 not in use Field exists in the database Table 571 Rt_Pdp_Ctx_Capacity Sgsn_Papu_User_Stat_Rt_Pdp_Ctx_Capacity Field name Sgsn_Papu_User_Stat_Average_Bandwidth_Limit_For_Rt_Pdp_Ctxs Datatype in IDS UINT16 SGSN version >=SG6 Explanation Tells how much (real) average bandwidth (Kbit/s) the active RT PDP contexts are allowed to use per PAPU.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Papu_User_Stat_Average_Bandwidth_Used_By_Rt_Pdp_Con Datatype in IDS UINT32 SGSN version >=SG6 Explanation Bandwidth used by priority class streaming and conversational pdp contexts. Possible values 0 – 64000 0xFFFF = Feature SG01007 not in use Field exists in the database Table 572 Average_Bandwidth_Limit_For_Rt_Pdp_Ctxs Sgsn_Papu_User_Stat_Average_Bandwidth_Limit_For_Rt_Pdp_Ctxs Field name Sgsn_Papu_User_Stat_Bandwidth_Limit_For_Rt_Pdp_Ctxs Datatype in IDS UINT16 SGSN version >=SG6 Explanation Tells how much bandwidth (Kbit/s) the active RT PDP contexts are allowed to use per PAPU. there is a single-row entry for each table column. Database column SQL data types can be found in the workspace configuration file dbd_sgsn_cs_cdr.Traffica Reference Guide for SGSN Direct Interface Field exists in the database Table 573 RTT report descriptions Bandwidth_Limit_For_Rt_Pdp_Ctxs Sgsn_Papu_User_Stat_Bandwidth_Limit_For_Rt_Pdp_Ctxs (Cont. Possible values Field exists in the database Table 575 Report_Id Sgsn_Cs_Cdr_Stat_Report_Id Field name Sgsn_Cs_Cdr_Stat_Report_Length Data type in the IDS UINT16 SGSN version >=SG6 Explanation This field contains the length of report in bytes. The SQL datatype appears after the column name and '=' sign. Sgsn_Gtp_Stat_Report_Count IDS field is Report Count field in Traffic News' SGSN_CS_CDR_STAT_EVENT. Sgsn_Cs_Cdr_Stat_Report_Count IDS field is Report_Count column in database table <SGSN_Release_Id>_CS_CDR_STAT. Traffic News field names are the same as database column names with spaces used instead of underscores between words. For example. Field name Sgsn_Cs_Cdr_Stat_Report_Id Data type in the IDS UINT16 SGSN version >=SG6 Explanation Contains information on the report type. Possible values 0x0 .conf. NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field.12 CS_CDR_STAT fields The following table shows the CS_CDR_STAT fields: Traffic News event type SGSN_CS_CDR_STAT_EVENT Database table <SGSN_Release_Id>_CS_CDR_STAT Table 574 SGSN_CS_CDR_STAT fields Database column names are the same as IDS fields names without the ‘Sgsn_Cs_Cdr_Stat’ prefix.) 6. Under the [<SGSN_Release_Id>_CS_CDR_STAT] section. This field is needed because empty cells are dropped from cdr_stat_table.0xFFFF Field exists in the database Report_Length Table 576 Sgsn_Cs_Cdr_Stat_Report_Length DN05148836 Issue 2-2 Id:0900d805809551ce 431 . For example. because the possible values can and will change in the future. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Generated_Gb_S_Cdrs Table 580 432 Sgsn_Cs_Cdr_Stat_Generated_Gb_S_Cdrs Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values Field exists in the database Table 578 Sgsn_Cs_Cdr_Stat_Report_Time and Sgsn_Cs_Cdr_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Sgsn_Cs_Cdr_Stat_Report_Time Field name Sgsn_Cs_Cdr_Stat_Report_Date Data type in the IDS BDCDATE SGSN version >=SG6 Explanation The date when the report was sent to Traffica. Possible values Field exists in the database Table 579 Sgsn_Cs_Cdr_Stat_Report_Time and Sgsn_Cs_Cdr_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Sgsn_Cs_Cdr_Stat_Report_Date Field name Sgsn_Cs_Cdr_Stat_Generated_Gb_S_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Gb S-CDRs generated.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Cs_Cdr_Stat_Report_Count Data type in the IDS UINT32 SGSN version >=SG6 Explanation Contains information on how many reports of this type have been sent to Traffica. that is. received from a charging collection entity. Possible values 0x0-0xFFFFFFFF Field exists in the database Report_Count Table 577 Sgsn_Cs_Cdr_Stat_Report_Count Field name Sgsn_Cs_Cdr_Stat_Report_Time Data type in the IDS UINT32 SGSN version BDCTIME Explanation The time when the report was sent to Traffica. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Gb_S_Cdrs_Due_Other Table 583 Sgsn_Cs_Cdr_Stat_Disc_Gb_S_Cdrs_Due_Other Field name Sgsn_Cs_Cdr_Stat_Disc_Gb_S_Cdrs_Due_Resent Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded GTP' packets for Gb S-CDRs due to a reason that too many resends has been done Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Gb_S_Cdrs_Due_Resent Table 584 Sgsn_Cs_Cdr_Stat_Disc_Gb_S_Cdrs_Due_Resent DN05148836 Issue 2-2 Id:0900d805809551ce 433 .Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Cs_Cdr_Stat_Generated_pp_Gb_S_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Gb prepaid S-CDRs generated. received from a charging collection entity. that is. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Generated_pp_Gb_S_Cdrs Table 581 Sgsn_Cs_Cdr_Stat_Generated_pp_Gb_S_Cdrs Field name Sgsn_Cs_Cdr_Stat_Disc_Gb_S_Cdrs_Due_Overflow Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded Gb S-CDRs due to resend buffer overflow Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Gb_S_Cdrs_Due_Overflow Table 582 Sgsn_Cs_Cdr_Stat_Disc_Gb_S_Cdrs_Due_Overflow Field name Sgsn_Cs_Cdr_Stat_Disc_Gb_S_Cdrs_Due_Other Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded GTP' packets for Gb S-CDRs due to a reason other than resend buffer overflow. that is. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Generated_pp_Gb_M_Cdrs Table 586 Sgsn_Cs_Cdr_Stat_Generated_pp_Gb_M_Cdrs Field name Sgsn_Cs_Cdr_Stat_Disc_Gb_M_Cdrs_Due_Overflow Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded Gb M-CDRs due to resend buffer overflow Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Gb_M_Cdrs_Due_Overflow Table 587 Sgsn_Cs_Cdr_Stat_Disc_Gb_M_Cdrs_Due_Overflow Field name Sgsn_Cs_Cdr_Stat_Disc_Gb_M_Cdrs_Due_Other Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded GTP packets for Gb M-CDRs due to a reason other than resend buffer overflow. received from a charging collection entity. received from a charging collection entity. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Generated_Gb_M_Cdrs Table 585 Sgsn_Cs_Cdr_Stat_Generated_Gb_M_Cdrs Field name Sgsn_Cs_Cdr_Stat_Generated_pp_Gb_M_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Gb prepaid M-CDRs generated.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Cs_Cdr_Stat_Generated_Gb_M_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Gb M-CDRs generated. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Gb_M_Cdrs_Due_Other Table 588 434 Sgsn_Cs_Cdr_Stat_Disc_Gb_M_Cdrs_Due_Other Id:0900d805809551ce DN05148836 Issue 2-2 . that is. Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Cs_Cdr_Stat_Disc_Gb_M_Cdrs_Due_Resent Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded GTP packets for Gb M-CDRs due to a reason that too many resends have been done Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Gb_M_Cdrs_Due_Resent Table 589 Sgsn_Cs_Cdr_Stat_Disc_Gb_M_Cdrs_Due_Resent Field name Sgsn_Cs_Cdr_Stat_Generated_Gb_Smo_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Gb SMO-CDRs generated. that is. received from a charging collection entity Possible values 0x1 . Possible values 0x1 .0xFFFFFFFF Field exists in the database Generated_Gb_Pp_Smo_Cdrs Table 591 Sgsn_Cs_Cdr_Stat_Generated_Gb_Pp_Smo_Cdrs Field name Sgsn_Cs_Cdr_Stat_Disc_Gb_Smo_Cdrs_Due_Overflow Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded Gb SMO-CDRs due to resend buffer overflow. received from a charging collection entity.0xFFFFFFFF Field exists in the database Generated_Gb_Smo_Cdrs Table 590 Sgsn_Cs_Cdr_Stat_Generated_Gb_Smo_Cdrs Field name Sgsn_Cs_Cdr_Stat_Generated_Gb_Pp_Smo_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Gb S-SMO-CDRs generated. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Gb_Smo_Cdrs_Due_Overflow Table 592 Sgsn_Cs_Cdr_Stat_Disc_Gb_Smo_Cdrs_Due_Overflow DN05148836 Issue 2-2 Id:0900d805809551ce 435 . that is. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Generated_Gb_Smt_Cdrs Table 595 Sgsn_Cs_Cdr_Stat_Generated_Gb_Smt_Cdrs Field name Sgsn_Cs_Cdr_Stat_Generated_Gb_Pp_Smt_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Gb prepaid S-SMT-CDRs generated. that is. that is. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Generated_Gb_Pp_Smt_Cdrs Table 596 436 Sgsn_Cs_Cdr_Stat_Generated_Gb_Pp_Smt_Cdrs Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Gb_Smo_Cdrs_Due_Other Table 593 Sgsn_Cs_Cdr_Stat_Disc_Gb_Smo_Cdrs_Due_Other Field name Sgsn_Cs_Cdr_Stat_Disc_Gb_Smo_Cdrs_Due_Resent Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded GTP packets for Gb S-SMO-CDRs due to the reason that too many resends have been done. received from a charging collection entity.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Cs_Cdr_Stat_Disc_Gb_Smo_Cdrs_Due_Other Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded GTP packets for Gb SMO-CDRs due to a reason other than resend buffer overflow. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Gb_Smo_Cdrs_Due_Resent Table 594 Sgsn_Cs_Cdr_Stat_Disc_Gb_Smo_Cdrs_Due_Resent Field name Sgsn_Cs_Cdr_Stat_Generated_Gb_Smt_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Gb S-SMT-CDRs generated. received from a charging collection entity. that is.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Cs_Cdr_Stat_Disc_Gb_Smt_Cdrs_Due_Overflow Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded Gb S-SMT-CDRs due to resend buffer overflow. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Generated_Iu_S_Cdrs Table 600 Sgsn_Cs_Cdr_Stat_Generated_Iu_S_Cdrs DN05148836 Issue 2-2 Id:0900d805809551ce 437 . Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Gb_Smt_Cdrs_Due_Other Table 598 Sgsn_Cs_Cdr_Stat_Disc_Gb_Smt_Cdrs_Due_Other Field name Sgsn_Cs_Cdr_Stat_Disc_Gb_Smt_Cdrs_Due_Resent Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded GTP packets for Gb S-SMT-CDRs due to a reason that too many resends have been done. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Gb_Smt_Cdrs_Due_Overflow Table 597 Sgsn_Cs_Cdr_Stat_Disc_Gb_Smt_Cdrs_Due_Overflow Field name Sgsn_Cs_Cdr_Stat_Disc_Gb_Smt_Cdrs_Due_Other Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded GTP packets for Gb S-SMT-CDRs due to a reason other than resend buffer overflow. received from a charging collection entity. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Gb_Smt_Cdrs_Due_Resent Table 599 Sgsn_Cs_Cdr_Stat_Disc_Gb_Smt_Cdrs_Due_Resent Field name Sgsn_Cs_Cdr_Stat_Generated_Iu_S_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Gb Iu-S-CDRs generated. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Generated_Pp_Iu_S_Cdrs Table 601 Sgsn_Cs_Cdr_Stat_Generated_Pp_Iu_S_Cdrs Field name Sgsn_Cs_Cdr_Stat_Disc_Iu_S_Cdrs_Due_Overflow Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded Iu-S-CDRs due to resend buffer overflow. received from a charging collection entity. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Iu_S_Cdrs_Due_Other Table 603 Sgsn_Cs_Cdr_Stat_Disc_Iu_S_Cdrs_Due_Other Field name Sgsn_Cs_Cdr_Stat_Disc_Iu_S_Cdrs_Due_Resent Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded GTP' packets for Iu-S-CDRs due to a reason that too many resends has been done Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Iu_S_Cdrs_Due_Resent Table 604 438 Sgsn_Cs_Cdr_Stat_Disc_Iu_S_Cdrs_Due_Resent Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Iu_S_Cdrs_Due_Overflow Table 602 Sgsn_Cs_Cdr_Stat_Disc_Iu_S_Cdrs_Due_Overflow Field name Sgsn_Cs_Cdr_Stat_Disc_Iu_S_Cdrs_Due_Other Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded GTP' packets for Iu-S-CDRs due to a reason other than resend buffer overflow.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Cs_Cdr_Stat_Generated_Pp_Iu_S_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Gb prepaid Iu-S-CDRs generated. that is. received from a charging collection entity. that is. received from a charging collection entity. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Generated_Iu_M_Cdrs Table 605 Sgsn_Cs_Cdr_Stat_Generated_Iu_M_Cdrs Field name Sgsn_Cs_Cdr_Stat_Generated_Pp_Iu_M_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Gb prepaid Iu-M-CDRs generated. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Generated_Pp_Iu_M_Cdrs Table 606 Sgsn_Cs_Cdr_Stat_Generated_Pp_Iu_M_Cdrs Field name Sgsn_Cs_Cdr_Stat_Disc_Iu_M_Cdrs_Due_Overflow Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded Gb Iu-M-CDRs due to resend buffer overflow Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Iu_M_Cdrs_Due_Overflow Table 607 Sgsn_Cs_Cdr_Stat_Disc_Iu_M_Cdrs_Due_Overflow Field name Sgsn_Cs_Cdr_Stat_Disc_Iu_M_Cdrs_Due_Other Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded GTP packets for Gb Iu-M-CDRs due to a reason other than resend buffer overflow. that is.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Cs_Cdr_Stat_Generated_Iu_M_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Gb Iu-M-CDRs generated. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Iu_M_Cdrs_Due_Other Table 608 Sgsn_Cs_Cdr_Stat_Disc_Iu_M_Cdrs_Due_Other DN05148836 Issue 2-2 Id:0900d805809551ce 439 . received from a charging collection entity.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Cs_Cdr_Stat_Disc_Iu_M_Cdrs_Due_Resent Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded GTP packets for Gb Iu-M-CDRs due to the reason that too many resends has been done Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Iu_M_Cdrs_Due_Resent Table 609 Sgsn_Cs_Cdr_Stat_Disc_Iu_M_Cdrs_Due_Resent Field name Sgsn_Cs_Cdr_Stat_Generated_Iu_Smo_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Gb Iu-Smo-CDRs generated. that is. that is. received from a charging collection entity. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Generated_Iu_Smo_Cdrs Table 610 Sgsn_Cs_Cdr_Stat_Generated_Iu_Smo_Cdrs Field name Sgsn_Cs_Cdr_Stat_Generated_Iu_Pp_Smo_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Gb prepaid Iu-Smo-CDRs generated. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Generated_Iu_Pp_Smo_Cdrs Table 611 Sgsn_Cs_Cdr_Stat_Generated_Iu_Pp_Smo_Cdrs Field name Sgsn_Cs_Cdr_Stat_Disc_Iu_Smo_Cdrs_Due_Overflow Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded Gb Iu-Smo-CDRs due to resend buffer overflow Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Iu_Smo_Cdrs_Due_Overflow Table 612 440 Sgsn_Cs_Cdr_Stat_Disc_Iu_Smo_Cdrs_Due_Overflow Id:0900d805809551ce DN05148836 Issue 2-2 . Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Cs_Cdr_Stat_Disc_Iu_Smo_Cdrs_Due_Other Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded GTP packets for Gb Iu-Smo-CDRs due to a reason other than resend buffer overflow. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Iu_Smo_Cdrs_Due_Other Table 613 Sgsn_Cs_Cdr_Stat_Disc_Iu_Smo_Cdrs_Due_Other Field name Sgsn_Cs_Cdr_Stat_Disc_Iu_Smo_Cdrs_Due_Resent Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded GTP packets for Gb Iu-Smo-CDRs due to a reason that too many resends has been done Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Iu_Smo_Cdrs_Due_Resent Table 614 Sgsn_Cs_Cdr_Stat_Disc_Iu_Smo_Cdrs_Due_Resent Field name Sgsn_Cs_Cdr_Stat_Generated_Iu_Smt_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Iu S-SMT-CDRs generated. received from a charging collection entity. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Generated_Iu_Pp_Smt_Cdrs Table 616 Sgsn_Cs_Cdr_Stat_Generated_Iu_Pp_Smt_Cdrs DN05148836 Issue 2-2 Id:0900d805809551ce 441 . that is. received from a charging collection entity. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Generated_Iu_Smt_Cdrs Table 615 Sgsn_Cs_Cdr_Stat_Generated_Iu_Smt_Cdrs Field name Sgsn_Cs_Cdr_Stat_Generated_Iu_Pp_Smt_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Gb prepaid Iu-Smt-CDRs generated. that is. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Iu_Smt_Cdrs_Due_Other Table 618 Sgsn_Cs_Cdr_Stat_Disc_Iu_Smt_Cdrs_Due_Other Field name Sgsn_Cs_Cdr_Stat_Disc_Iu_Smt_Cdrs_Due_Resent Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded GTP packets for Gb Iu-Smt-CDRs due to a reason that too many resends has been done Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Iu_Smt_Cdrs_Due_Resent Table 619 Sgsn_Cs_Cdr_Stat_Disc_Iu_Smt_Cdrs_Due_Resent Field name Sgsn_Cs_Cdr_Stat_Ave_Master_Queue_Length_Sum Datatype in IDS UINT32 SGSN version >=SG6 Explanation Numerator of the average resend buffer utilisation.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Cs_Cdr_Stat_Disc_Iu_Smt_Cdrs_Due_Overflow Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded Gb Iu-Smt-CDRs due to resend buffer overflow Possible values 0x1 – 0xFFFFFFFF Field exists in the database Disc_Iu_Smt_Cdrs_Due_Overflow Table 617 Sgsn_Cs_Cdr_Stat_Disc_Iu_Smt_Cdrs_Due_Overflow Field name Sgsn_Cs_Cdr_Stat_Disc_Iu_Smt_Cdrs_Due_Other Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of discarded GTP packets for Gb Iu-Smt-CDRs due to a reason other than resend buffer overflow. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Ave_Master_Queue_Length_Sum Table 620 442 Sgsn_Cs_Cdr_Stat_Ave_Master_Queue_Length_Sum Id:0900d805809551ce DN05148836 Issue 2-2 . A sample is taken every 10 seconds. The buffer is common to all CDR types and includes GTP packets under duplicate CDR prevention handling. DN05148836 Issue 2-2 Id:0900d805809551ce 443 . Sgsn_Gtp_Stat_Report_Count IDS field is Report Count field in Traffic News' SGSN_OPEN_CDR_STAT_EVENT. The buffer is common to all CDR types and includes GTP packets under duplicate CDR prevention handling. A sample is taken every 10 seconds. there is a single-row entry for each table column. The buffer is common to all CDR types and includes GTP packets under duplicate CDR prevention handling. A sample is taken every 10 seconds. For example. Traffic News field names are the same as database column names with spaces used instead of underscores between words. Sgsn_Open_Cdr_Stat_Report_Count IDS field is Report_Count column in database table <SGSN_Release_Id>_OPEN_CDR_STAT. The SQL datatype appears after the column name and '=' sign. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Ave_Master_Queue_Length_Den Table 621 Sgsn_Cs_Cdr_Stat_Ave_Master_Queue_Length_Den Field name Sgsn_Cs_Cdr_Stat_Peak_Master_Queue_Length Datatype in IDS UINT32 SGSN version >=SG6 Explanation Peak resend buffer utilisation. Database column SQL datatypes can be found in the workspace configuration file dbd_sgsn_open_cdr.13 OPEN_CDR_STAT fields The following table shows the OPEN_CDR_STAT fields: Traffic News event type SGSN_OPEN_CDR_STAT_EVENT Database table <SGSN_Release_Id>_OPEN_CDR_ST AT Table 623 SGSN_OPEN_CDR_STAT fields Database column names are the same as IDS fields names without the ‘Sgsn_Open_Cdr_Stat’ prefix.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Cs_Cdr_Stat_Ave_Master_Queue_Length_Den Datatype in IDS UINT32 SGSN version >=SG6 Explanation Denominator of the average resend buffer utilisation.conf. For example. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Peak_Master_Queue_Length Table 622 Sgsn_Cs_Cdr_Stat_Peak_Master_Queue_Length 6. Under the [<SGSN_Release_Id>_OPEN_CDR_STAT] section. RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Open_Cdr_Stat_Report_Id Data type in the IDS UINT16 SGSN version >=SG6 Explanation Contains information on the report type. because the possible values can and will change in the future. NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field. Possible values 0x0 . Possible values Field exists in the database Table 627 444 Sgsn_Open_Cdr_Stat_Report_Time and Sgsn_Open_Cdr_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Sgsn_Open_Cdr_Stat_Report_Time Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values 0x0-0xFFFFFFFF Field exists in the database Report_Count Table 626 Sgsn_Open_Cdr_Stat_Report_Count Field name Sgsn_Open_Cdr_Stat_Report_Time Data type in the IDS BCDTIME SGSN version >=SG6 Explanation The time when the report was sent to Traffica.0xFFFF Field exists in the database Report_Length Table 625 Sgsn_Open_Cdr_Stat_Report_Length Field name Sgsn_Open_Cdr_Stat_Report_Count Data type in the IDS UINT32 SGSN version >=SG6 Explanation Contains information on how many reports of this type have been sent to Traffica. Possible values Field exists in the database Table 624 Report_Id Sgsn_Open_Cdr_Stat_Report_Id Field name Sgsn_Open_Cdr_Stat_Report_Length Data type in the IDS UINT16 SGSN version >=SG6 Explanation This field contains the length of report in bytes. This field is needed because empty cells are dropped from cdr_stat_table. Possible values 0x1 – 0xFFFFFFFF Table 631 Sgsn_Open_Cdr_Stat_Ipv4_S_Cdrs DN05148836 Issue 2-2 Id:0900d805809551ce 445 .Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Open_Cdr_Stat_Report_Date Data type in the IDS BCDDATE SGSN version >=SG6 Explanation The date when the report was sent to Traffica. GIGPRBs send buffer is full and GIGPRB is not able to receive new CDRs from GCHPRB Possible values 0x1 – 0xFFFFFFFF Field exists in the database Gb_S_Cdrs Table 629 Sgsn_Open_Cdr_Stat_Gb_S_Cdrs Field name Sgsn_Open_Cdr_Stat_Gb_M_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation GCHPRB's CDR statistics counter: number of discarded M-CDRs for Gb -interface because of active overload control in CDR sending. GIGPRBs send buffer is full and GIGPRB is not able to receive new CDRs from GCHPRB Possible values 0x1 – 0xFFFFFFFF Field exists in the database Gb_M_Cdrs Table 630 Sgsn_Open_Cdr_Stat_Gb_M_Cdrs Field name Sgsn_Open_Cdr_Stat_Ipv4_S_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Amount of open Ipv4 S-CDRs. RTT report descriptions Possible values Field exists in the database Table 628 Sgsn_Open_Cdr_Stat_Report_Time and Sgsn_Open_Cdr_Stat_Report_Date are as SQL TIMESTAMP data type in column Report_Time Sgsn_Open_Cdr_Stat_Report_Date Field name Sgsn_Open_Cdr_Stat_Gb_S_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation GCHPRB's CDR statistics counter: number of discarded S-CDRs for Gb -interface because of active overload control in CDR sending. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Camel_S_Cdrs Table 634 Sgsn_Open_Cdr_Stat_Camel_S_Cdrs Field name Sgsn_Open_Cdr_Stat_Prepaid_M_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Amount of open prepaid M-CDRs. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Ipv6_S_Cdrs Table 632 Sgsn_Open_Cdr_Stat_Ipv6_S_Cdrs Field name Sgsn_Open_Cdr_Stat_Camel_M_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Amount of open M-CDRs with CAMEL relation. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Camel_M_Cdrs Table 633 Sgsn_Open_Cdr_Stat_Camel_M_Cdrs Field name Sgsn_Open_Cdr_Stat_Camel_S_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Amount of open S-CDRs with CAMEL relation. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Prepaid_M_Cdrs Table 635 446 Sgsn_Open_Cdr_Stat_Prepaid_M_Cdrs Id:0900d805809551ce DN05148836 Issue 2-2 .) Field name Sgsn_Open_Cdr_Stat_Ipv6_S_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Amount of open Ipv6 S-CDRs.RTT report descriptions Field exists in the database Table 631 Traffica Reference Guide for SGSN Direct Interface Ipv4_S_Cdrs Sgsn_Open_Cdr_Stat_Ipv4_S_Cdrs (Cont. Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Open_Cdr_Stat_Prepaid_S_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Amount of open prepaid S-CDRs Possible values 0x1 – 0xFFFFFFFF Field exists in the database Prepaid_S_Cdrs Table 636 RTT report descriptions Sgsn_Open_Cdr_Stat_Prepaid_S_Cdrs Field name Sgsn_Open_Cdr_Stat_Secondary_S_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Amount of open S-CDRs that are related to secondary PDP contexts. received from a charging collection entity. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Iu_M_Cdrs Table 639 Sgsn_Open_Cdr_Stat_Iu_M_Cdrs Field name Table 640 Sgsn_Open_Cdr_Stat_Roaming_Gb_M_Cdrs Sgsn_Open_Cdr_Stat_Roaming_Gb_M_Cdrs DN05148836 Issue 2-2 Id:0900d805809551ce 447 . Possible values 0x1 – 0xFFFFFFFF Field exists in the database Secondary_S_Cdrs Table 637 Sgsn_Open_Cdr_Stat_Secondary_S_Cdrs Field name Sgsn_Open_Cdr_Stat_Iu_S_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Amount of open Iu S-CDRs. that is. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Iu_S_Cdrs Table 638 Sgsn_Open_Cdr_Stat_Iu_S_Cdrs Field name Sgsn_Open_Cdr_Stat_Iu_M_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of Iu M-CDRs generated. ) Field name Sgsn_Open_Cdr_Stat_Roaming_Gb_S_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Amount of Gb S-CDRs that are related to roaming subscriber. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Roaming_Gb_S_Cdrs Table 641 Sgsn_Open_Cdr_Stat_Roaming_Gb_S_Cdrs Field name Sgsn_Open_Cdr_Stat_Roaming_Iu_M_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Amount of Iu M-CDRs that are related to roaming subscriber Possible values 0x1 – 0xFFFFFFFF Field exists in the database Roaming_Iu_M_Cdrs Table 642 Sgsn_Open_Cdr_Stat_Roaming_Iu_M_Cdrs Field name Sgsn_Open_Cdr_Stat_Roaming_Iu_S_Cdrs Datatype in IDS UINT32 SGSN version >=SG6 Explanation Amount of Iu S-CDRs that are related to roaming subscriber. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Roaming_Iu_S_Cdrs Table 643 Sgsn_Open_Cdr_Stat_Roaming_Iu_S_Cdrs 6.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Datatype in IDS UINT32 SGSN version >=SG6 Explanation Amount of Gb M-CDRs that are related to roaming subscriber.14 IU_RA_PAGING_STAT fields The following table shows the IU_RA_PAGING_STAT fields: Traffic News event type Table 644 448 SGSN_IU_RA_PAGING_STAT_EVENT SGSN_IU_RA_PAGING_STAT fields Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values 0x1 – 0xFFFFFFFF Field exists in the database Roaming_Gb_M_Cdrs Table 640 Sgsn_Open_Cdr_Stat_Roaming_Gb_M_Cdrs (Cont. The value of the counter is reset every day at 00:00 a. NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field. For example.conf.0xFFFFFFFF) Field exists in the database Report_Count Table 646 Sgsn_Iu_Ra_Paging_Stat_Report_Count Field name Sgsn_Iu_Ra_Paging_Stat_Report_Length Datatype in IDS BCDDATE Table 647 Sgsn_Iu_Ra_Paging_Stat_Report_Length DN05148836 Issue 2-2 Id:0900d805809551ce 449 . The SQL datatype appears after the column name and “=” symbol. the Sgsn_BSSGP_CELL_STAT_Report_Count IDS field is Report Count field in Traffic News SGSN_IU_RA_PAGING_STAT_EVENT. The database column SQL datatypes can be found in the workspace configuration file dbd_sgsn_iu_ra_paging_stat. Possible values 0 .) The database column names are the same as the IDS field names without the Sgsn_IU_RA_PAGING_STAT prefix. there is a single-row entry for each table column. The Traffic News field names are the same as the database column names but use spaces instead of underscores between words.Traffica Reference Guide for SGSN Direct Interface Database table Table 644 RTT report descriptions <SGSN_Release_Id>_IU_RA_PAGING _STAT SGSN_IU_RA_PAGING_STAT fields (Cont. the Sgsn_IU_RA_PAGING_STAT_Report_Count IDS field is the Report_Count column in database table <SGSN_Release_Id>_IU_RA_PAGING_STAT.m. because the possible values can and will change in the future. Field name Sgsn_Iu_Ra_Paging_Stat_Report_Id Datatype in IDS UINT16 SGSN version >=SG6 Explanation Contains information on the report type. For example.4 294 967 296 (0x0 . Possible values 0x0214 Field exists in the database Report_Id Table 645 Sgsn_Iu_Ra_Paging_Stat_Report_Id Field name Sgsn_Iu_Ra_Paging_Stat_Report_Count Datatype in IDS UINT32 SGSN version >=SG6 Explanation Contains information on how many reports of this type have been sent to Traffica. Under the <SGSN_Release_Id>_IU_RA_PAGING_STAT section. Possible values 0x0-0xFFFFFFFF Field exists in the database Sgsn_Iu_Ra_Paging_Stat_Report_Time and Sgsn_Iu_Ra_Paging_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Table 648 Sgsn_Iu_Ra_Paging_Stat_Report_Time Field name Sgsn_Iu_Ra_Paging_Stat_Report_Date Datatype in IDS BCDDATE SGSN version >=SG6 Explanation The date when the report was sent to Traffica.) Field name Sgsn_Iu_Ra_Paging_Stat_Report_Time Datatype in IDS BCDTIME SGSN version >=SG6 Explanation The time when the report was sent to Traffica.0xFFFF Field exists in the database Report_Length Table 647 Sgsn_Iu_Ra_Paging_Stat_Report_Length (Cont. This field is needed because empty cells are dropped from paging_table. Possible values 0x1 – 0xFF Field exists in the database Papu_Id Table 650 Field name Table 651 450 Sgsn_Iu_Ra_Paging_Stat_Papu_Id Sgsn_Iu_Ra_Paging_Stat_Physical_Papu_Id Sgsn_Iu_Ra_Paging_Stat_Physical_Papu_Id Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values 0x0 . Possible values 0x0-0xFFFFFFFF Field exists in the database Sgsn_Iu_Ra_Paging_Stat_Report_Time and Sgsn_Iu_Ra_Paging_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Table 649 Sgsn_Iu_Ra_Paging_Stat_Report_Date Field name Sgsn_Iu_Ra_Paging_Stat_Papu_Id Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains the index of PAPU.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface SGSN version >=SG6 Explanation This field contains the length of report in bytes. FNSG01060. Value 0 means that PAPU doesn’t belong to any group Field exists in the database Table 652 Papu_Group_Id Sgsn_Iu_Ra_Paging_Stat_Papu_Group_Id Field name Sgsn_Iu_Ra_Paging_Stat_Papu_Capa Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains the subscriber capacity of particular PAPU in SGSN. FNSG01060.Traffica Reference Guide for SGSN Direct Interface Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains the physical index of PAPU. Large RA Support isn’t activated. Value 0 means that PAPU doesn’t belong to any group Field exists in the database Table 651 Physical_Papu_Id Sgsn_Iu_Ra_Paging_Stat_Physical_Papu_Id (Cont. Possible values 0-255 This field is always 0 if feature. Possible values 0x41 = maximum of 65 000 attached subscribers 0x64 = maximum of 100 000 attached subscribers 0xFA = maximum of 250 000 attached subscribers Field exists in the database Table 653 Papu_Capa Sgsn_Iu_Ra_Paging_Stat_Papu_Capa Field name Sgsn_Iu_Ra_Paging_Stat_RA_Elements_Count Datatype in IDS UINT16 SGSN version >=SG6 Explanation Number of RA elements. Possible values 0-255 RTT report descriptions This field is always 0 if feature. Large RA Support isn’t activated. Possible values Field exists in the database Table 654 RA_Elements_Count Sgsn_Iu_Ra_Paging_Stat_RA_Elements_Count DN05148836 Issue 2-2 Id:0900d805809551ce 451 .) Field name Sgsn_Iu_Ra_Paging_Stat_Papu_Group_Id Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains PAPU group id. Field contents are:array(2) OF double_digit. if Mnc is 400 the Sgsn_Cgi_Mnc field is: 04 F0.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Iu_Ra_Paging_Stat_Cgi_Mcc Datatype in IDS BDCREV8(2) SGSN version >=SG6 Explanation This field contains the country code. lower_digit (4bits) and upper_digit (4bits). if Mcc is 358 the Sgsn_Cgi_Mcc field is: 53 F8 Field exists in the database Cgi_Mcc Table 655 Sgsn_Iu_Ra_Paging_Stat_Cgi_Mcc Field name Sgsn_Iu_Ra_Paging_Stat_Cgi_Mnc Datatype in IDS BDCREV8(2) SGSN version >=SG6 Explanation This field contains the mobile network code. For example. Mcc is stored in decimal format and the end mark is 0xF. Field exists in the database Table 656 Cgi_Mnc Sgsn_Iu_Ra_Paging_Stat_Cgi_Mnc Field name Sgsn_Iu_Ra_Paging_Stat_Cgi_Lac Datatype in IDS UINT16 SGSN version >=SG6 Explanation This field contains location area code Possible values 0x1 – 0xFFFF Field exists in the database Cgi_Lac Table 657 Sgsn_Iu_Ra_Paging_Stat_Cgi_Lac Field name Sgsn_Iu_Ra_Paging_Stat_Cgi_Rac Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains routing area code. lower_digit (4bits) and upper_digit (4bits). one double_digit field is of size byte. Possible values Field contents are: array(2) OF double_digit. Possible values This field contains country code. Double_digit has two parts. one double_digit field is of size byte. Mnc is stored in decimal format and the end mark is 0xF. For example. Possible values 0x1 – 0xFF Table 658 452 Sgsn_Iu_Ra_Paging_Stat_Cgi_Rac Id:0900d805809551ce DN05148836 Issue 2-2 . Double_digit has two parts. Possible values 0x0214 Field exists in the database Report_Id Table 661 Sgsn_Paging_Stat_Report_Id DN05148836 Issue 2-2 Id:0900d805809551ce 453 . The Traffic News field names are the same as the database column names but use spaces instead of underscores between words. For example. because the possible values can and will change in the future.Traffica Reference Guide for SGSN Direct Interface Field exists in the database Table 658 RTT report descriptions Cgi_Rac Sgsn_Iu_Ra_Paging_Stat_Cgi_Rac (Cont. The database column SQL datatypes can be found in the workspace configuration file dbd_sgsn_paging_stat. Field name Sgsn_Paging_Stat_Report_Id Datatype in IDS UINT16 SGSN version >=SG4 Explanation Contains information on the report type. the Sgsn_PAGING_STAT_Report_Count IDS field is the Report_Count column in database table <SGSN_Release_Id>_PAGING_STAT. the Sgsn_BSSGP_CELL_STAT_Report_Count IDS field is Report Count field in Traffic News SGSN_PAGING_STAT_EVENT. NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field.15 PAGING_STAT fields The following table shows the PAGING_STAT fields: Traffic News event type SGSN_PAGING_STAT_EVENT Database table <SGSN_Release_Id>_PAGING_STAT Table 660 SGSN_PAGING_STAT fields The database column names are the same as the IDS field names without the Sgsn_PAGING_STAT prefix. Under the <SGSN_Release_Id>_PAGING_STAT section. The SQL datatype appears after the column name and “=” symbol. there is a single-row entry for each table column.conf.) Field name Sgsn_Iu_Ra_Paging_Stat_Pagings Datatype in IDS UINT32 SGSN version >=SG6 Explanation This field contains the number of pagings Possible values 0x1 – 0xFFFFFFFF Field exists in the database Stat_Pagings Table 659 Sgsn_Iu_Ra_Paging_Stat_Pagings 6. For example. 0xFFFFFFFF) Field exists in the database Report_Count Table 662 Sgsn_Paging_Stat_Report_Count Field name Sgsn_Paging_Stat_Report_Length Datatype in IDS BCDDATE SGSN version >=SG4 Explanation This field contains the length of report in bytes. Possible values 0 .0xFFFF Field exists in the database Report_Length Table 663 Sgsn_Paging_Stat_Report_Length Field name Sgsn_Paging_Stat_Report_Time Datatype in IDS BCDTIME SGSN version >=SG4 Explanation The time when the report was sent to Traffica. The value of the counter is reset every day at 00:00 a. Possible values 0x0-0xFFFFFFFF Field exists in the database Sgsn_Paging_Stat_Report_Time and Sgsn_Paging_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Table 664 Sgsn_Paging_Stat_Report_Time Field name Sgsn_Paging_Stat_Report_Date Datatype in IDS BCDDATE SGSN version >=SG4 Explanation The date when the report was sent to Traffica. Possible values 0x0 . This field is needed because empty cells are dropped from paging_table. Possible values 0x0-0xFFFFFFFF Field exists in the database Sgsn_Paging_Stat_Report_Time and Sgsn_Paging_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Table 665 454 Sgsn_Paging_Stat_Report_Date Id:0900d805809551ce DN05148836 Issue 2-2 .m.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Paging_Stat_Report_Count Datatype in IDS UINT32 SGSN version >=SG4 Explanation Contains information on how many reports of this type have been sent to Traffica.4 294 967 296 (0x0 . 0xFF = Unused PAPU:spare or separated Field exists in the database Table 668 Papu_Capa Sgsn_Paging_Stat_Papu_Capa Field name Sgsn_Paging_Stat_Papu_Group_Id Datatype in IDS UINT8 SGSN version >=SG4 Table 669 Sgsn_Paging_Stat_Papu_Group_Id DN05148836 Issue 2-2 Id:0900d805809551ce 455 . Possible values 0x14 = 20000 subscribers 0x19 = 25000 subscribers 0x1B = 26667 subscribers 0x1E = 30000 subscribers 0x22 = 33334 subscribers 0x23 = 35000 subscribers 0x28 = 40000 subsribers (640k subscriber capacity.0xFF Field exists in the database Papu_Id Table 666 Sgsn_Paging_Stat_Papu_Id Field name Sgsn_Paging_Stat_Physical_Papu_Id Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the physical index of PAPU.Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Paging_Stat_Papu_Id Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains identity of papu. Possible values 0x0 . activated) 0x3C = 60000 subscribers. FNSG01065. High capacity PAPU. Possible values 0x1 – 0xFF Field exists in the database Physical_Papu_Id Table 667 RTT report descriptions Sgsn_Paging_Stat_Physical_Papu_Id Field name Sgsn_Paging_Stat_Papu_Capa Datatype in IDS UINT8 SGSN version >=SG4 Explanation This field contains the subscriber capacity of a particular PAPU in SGSN. 0xFFFF Field exists in the database RA_Elements_Count Table 670 Sgsn_Paging_Stat_RA_Elements_Count Field name Sgsn_Paging_Stat_Cgi_Mcc Datatype in IDS UINT16 SGSN version >=SG4 Explanation Contains the country code Possible values Mobile country code (MCC) Field exists in the database Cgi_Mcc Table 671 Sgsn_Paging_Stat_Cgi_Mcc Field name Sgsn_Paging_Stat_Cgi_Mnc Datatype in IDS UINT16 SGSN version >=SG4 Explanation Mobile network code for the most recent cell. Table 673 456 Sgsn_Paging_Stat_Cgi_Lac Id:0900d805809551ce DN05148836 Issue 2-2 . Value 0 means that PAPU does not belong to any group Field exists in the database Table 669 Papu_Group_Id Sgsn_Paging_Stat_Papu_Group_Id (Cont. Possible values Mobile network code (MNC) Field exists in the database Cgi_Mnc Table 672 Sgsn_Paging_Stat_Cgi_Mnc Field name Sgsn_Paging_Stat_Cgi_Lac Datatype in IDS UINT16 SGSN version >=SG4 Explanation Location area code for the most recent cell.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Explanation This field contains PAPU group id.) Field name Sgsn_Paging_Stat_RA_Elements_Count Datatype in IDS UINT16 SGSN version >=SG4 Explanation Number of RA elements in actual use Possible values 0x0 . Possible values 0-255 This field is always 0 if feature Large RA Support is not activated. 0xFFFFFFFF Field exists in the database Pagings Table 676 RTT report descriptions Sgsn_Paging_Stat_Pagings Field name Sgsn_Paging_Stat_Last_Message Datatype in IDS UINT8 SGSN version >=SG6 Explanation Because the maximum number of cells per PAPU is 3000.Traffica Reference Guide for SGSN Direct Interface Possible values Location are code (LAC) Field exists in the database Cgi_Lac Table 673 Sgsn_Paging_Stat_Cgi_Lac (Cont. counters of all cells don't necessarily fit to one report. Possible values 0x0 .) Field name Sgsn_Paging_Stat_Cgi_Rac Datatype in IDS UINT16 SGSN version >=SG4 Explanation Routing area code for the most recent cell.Value T in this field indicates it is the last report Table 677 Sgsn_Paging_Stat_Last_Message DN05148836 Issue 2-2 Id:0900d805809551ce 457 . Possible values Routing area code (RAC) Field exists in the database Cgi_Rac Table 674 Sgsn_Paging_Stat_Cgi_Rac Field name Sgsn_Paging_Stat_Cgi_Ci Datatype in IDS UINT16 SGSN version >=SG4 Explanation Contains the cell identity Possible values Cell identity (CI) Field exists in the database Cgi_Ci Table 675 Sgsn_Paging_Stat_Cgi_Ci Field name Sgsn_Paging_Stat_Pagings Datatype in IDS UINT32 SGSN version >=SG4 Explanation RA level pagings. Maximum number of needed SGSN_BSSGP_CELL_STAT reports per papu is 10. ) Field name Sgsn_Paging_Stat_Sequence_Nr Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains the sequence number of response message. Mcc is stored in decimal format and the end mark is 0xF.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Possible values 1-0 Field exists in the database Last_Message Table 677 Sgsn_Paging_Stat_Last_Message (Cont. if Mcc is 358 the Sgsn_Cgi_Mcc field is: 53 F8 Field exists in the database Table 680 Cgi_Mcc Sgsn_Paging_Stat_Cgi_Mcc Field name Sgsn_Paging_Stat_Cgi_Mnc Datatype in IDS BCDREV8(2) SGSN version >=SG6 Explanation This field contains mobile network code Table 681 458 Sgsn_Paging_Stat_Cgi_Mnc Id:0900d805809551ce DN05148836 Issue 2-2 . numbering starts from 1. For example. Possible values 1-10 Field exists in the database Sequence_Nr Table 678 Sgsn_Paging_Stat_Sequence_Nr Field name Sgsn_Paging_Stat_RA_Elements_Count Datatype in IDS UINT16 SGSN version >=SG6 Explanation Number of RA Elements Possible values 0x1-0xFFFF Field exists in the database RA_Elements_Count Table 679 Sgsn_Paging_Stat_RA_Elements_Count Field name Sgsn_Paging_Stat_Cgi_Mcc Datatype in IDS BCDREV8(2) SGSN version >=SG6 Explanation This field contains the country code. Possible values 0x0 – 0XFFFF. lower_digit (4bits) and upper_digit (4bits). Double_digit has two parts. Possible values 0x1 – 0xFF Field exists in the database Cgi_Rac Table 683 Sgsn_Paging_Stat_Cgi_Rac Field name Sgsn_Paging_Stat_Pagings Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of pagings Possible values 0x1 – 0xFFFFFFFF Field exists in the database Stat_Pagings Table 684 Sgsn_Paging_Stat_Pagings 6.) Field name Sgsn_Paging_Stat_Cgi_Lac Datatype in IDS UINT16 SGSN version >=SG6 Explanation This field contains location area code Possible values 0x1 – 0xFFFF Field exists in the database Cgi_Lac Table 682 Sgsn_Paging_Stat_Cgi_Lac Field name Sgsn_Paging_Stat_Cgi_Rac Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains routing area code. Field exists in the database Table 681 Cgi_Mnc Sgsn_Paging_Stat_Cgi_Mnc (Cont. lower_digit (4bits) and upper_digit (4bits). if Mnc is 400 the Sgsn_Cgi_Mnc field is: 04 F0.16 IU_PAGING_STAT fields The following table shows the IU_PAGING_STAT fields: Traffic News event type Table 685 DN05148836 Issue 2-2 SGSN_IU_PAGING_STAT_EVENT SGSN_IU_PAGING_STAT fields Id:0900d805809551ce 459 . For example.Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions 0x1 – 0xFFFF Mnc is stored in decimal format and the end mark is 0xF. Double_digit has two parts. the Sgsn_BSSGP_CELL_STAT_Report_Count IDS field is Report Count field in Traffic News SGSN_IU_PAGING_STAT_EVENT. Under the <SGSN_Release_Id>_IU_PAGING_STAT section. For example. there is a single-row entry for each table column. Field name Sgsn_Iu_Paging_Stat_Report_Id Datatype in IDS UINT16 SGSN version >=SG6 Explanation Contains information on the report type. NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field.) The database column names are the same as the IDS field names without the Sgsn_IU_PAGING_STAT prefix. For example. The SQL datatype appears after the column name and “=” symbol. The database column SQL datatypes can be found in the workspace configuration file dbd_sgsn_iu_paging_stat. The Traffic News field names are the same as the database column names but use spaces instead of underscores between words. Possible values 0 .4 294 967 296 (0x0 .RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Database table Table 685 <SGSN_Release_Id>_ IU_PAGING_STAT SGSN_IU_PAGING_STAT fields (Cont. because the possible values can and will change in the future. The value of the counter is reset every day at 00:00 a. Possible values 0x0214 Field exists in the database Report_Id Table 686 Sgsn_Iu_Paging_Stat_Report_Id Field name Sgsn_Iu_Paging_Stat_Report_Count Datatype in IDS UINT32 SGSN version >=SG6 Explanation Contains information on how many reports of this type have been sent to Traffica.conf.0xFFFFFFFF) Field exists in the database Report_Count Table 687 Sgsn_Iu_Paging_Stat_Report_Count Field name Sgsn_Iu_Paging_Stat_Report_Length Datatype in IDS BCDDATE Table 688 460 Sgsn_Iu_Paging_Stat_Report_Length Id:0900d805809551ce DN05148836 Issue 2-2 .m. the Sgsn_IU_PAGING_STAT_Report_Count IDS field is the Report_Count column in database table <SGSN_Release_Id>_IU_PAGING_STAT. Possible values 0x0-0xFFFFFFFF Field exists in the database Sgsn_Iu_Paging_Stat_Report_Time and Sgsn_Iu_Paging_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Table 689 Sgsn_Iu_Paging_Stat_Report_Time Field name Sgsn_Iu_Paging_Stat_Report_Date Datatype in IDS BCDDATE SGSN version >=SG6 Explanation The date when the report was sent to Traffica.) Field name Sgsn_Iu_Paging_Stat_Report_Time Datatype in IDS BCDTIME SGSN version >=SG6 Explanation The time when the report was sent to Traffica.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions SGSN version >=SG6 Explanation This field contains the length of report in bytes. Possible values 0x0-0xFFFFFFFF Field exists in the database Sgsn_Iu_Paging_Stat_Report_Time and Sgsn_Iu_Paging_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Table 690 Sgsn_Iu_Paging_Stat_Report_Date Field name Sgsn_Iu_Paging_Stat_Papu_Id Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains the index of PAPU.0xFFFF Field exists in the database Report_Length Table 688 Sgsn_Iu_Paging_Stat_Report_Length (Cont. Possible values 0x0 . This field is needed because empty cells are dropped from paging_table. Possible values 0x1 – 0xFF Field exists in the database Papu_Id Table 691 Sgsn_Iu_Paging_Stat_Papu_Id Field name Table 692 Sgsn_Iu_Paging_Stat_Physical_Papu_Id Sgsn_Iu_Paging_Stat_Physical_Papu_Id DN05148836 Issue 2-2 Id:0900d805809551ce 461 . Value 0 means that PAPU does not belong to any group Field exists in the database Table 694 Papu_Group_Id Sgsn_Iu_Paging_Stat_Papu_Group_Id Field name Sgsn_Iu_Paging_Stat_Sgsn_Level_Pagings Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of started Gb PS pagings procedures. FNSG01060. Possible values 0x41 = maximum of 65 000 attached subscribers 0x64 = maximum of 100 000 attached subscribers 0xFA = maximum of 250 000 attached subscribers Field exists in the database Table 693 Papu_Capa Sgsn_Iu_Paging_Stat_Papu_Capa Field name Sgsn_Iu_Paging_Stat_Papu_Group_Id Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains PAPU group id Possible values 0-255 This field is always 0 if feature.) Field name Sgsn_Iu_Paging_Stat_Papu_Capa Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains the subscriber capacity of particular PAPU in SGSN. Updated: When the first paging message is sent to the MS during the paging procedure Possible values 0x1 – 0xFFFFFFFF Field exists in the database Sgsn_Level_Pagings Table 695 462 Sgsn_Iu_Paging_Stat_Sgsn_Level_Pagings Id:0900d805809551ce DN05148836 Issue 2-2 . Large RA Support is not activated.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains the index of PAPU. Possible values 0x1 – 0xFF Field exists in the database Physical_Papu_Id Table 692 Sgsn_Iu_Paging_Stat_Physical_Papu_Id (Cont. and 2G SGSN-level paging attempts have been made and no answer has been received.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Iu_Paging_Stat_Unsuccessful_Pagings Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of failed Gb PS pagings procedures. For example. The Traffic News field names are the same as the database column names but use spaces instead of underscores between words. the Sgsn_BSSGP_CELL_STAT_Report_Count IDS field is Report Count field in Traffic News SGSN_GTP_C_STAT_EVENT. For example.17 GTP_C_STAT fields The following table shows the GTP_C_STAT fields: Traffic News event type SGSN_ GTP_C_STAT_EVENT Database table <SGSN_Release_Id>_ GTP_C_STAT Table 698 SGSN_GTP_C_STAT fields The database column names are the same as the IDS field names without the Sgsn_GTP_C_STAT prefix. Updated: Every time a SGSN level paging request is sent. Updated: When the maximum number of RA. or when a single RA-level paging attempt has been made after an unsuccessful paging procedure and no answer has been received Possible values 0x1 – 0xFFFFFFFF Field exists in the database Unsuccessful_Pagings Table 696 Sgsn_Iu_Paging_Stat_Unsuccessful_Pagings Field name Sgsn_Iu_Paging_Stat_Paging_Attempts Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of SGSN level Gb pagings. command group EJ. The database column SQL datatypes can be found in the workspace configuration file dbd_sgsn_gtp_c_stat. Under the <SGSN_Release_Id>_GTP_C_STAT DN05148836 Issue 2-2 Id:0900d805809551ce 463 .conf. the Sgsn_GTP_C_STAT_Report_Count IDS field is the Report_Count column in database table <SGSN_Release_Id>_GTP_C_STAT. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Paging_Attempts Table 697 Sgsn_Iu_Paging_Stat_Paging_Attempts 6. The maximum number of SGSN-level paging attempts in one paging procedure is defined with the GPRS Network Handling MML. Possible values Field exists in the database Table 699 Sgsn_Gtp_C_Stat_Report_Id Field name Sgsn_Gtp_C_Stat_Report_Length Data type in the IDS UINT16 SGSN version >=SG6 Explanation This field contains the length of report in bytes. The SQL datatype appears after the column name and “=” symbol. Field name Sgsn_Gtp_C_Stat_Report_Id Data type in the IDS UINT16 SGSN version >=SG6 Explanation Contains information on the report type. This field is needed because empty cells are dropped from C_stat_table. Possible values 0x0-0xFFFFFFFF Field exists in the database Report_Count Table 701 Sgsn_Gtp_C_Stat_Report_Count Field name Sgsn_Gtp_C_Stat_Report_Time Data type in the IDS BDCTIME SGSN version >=SG6 Explanation The time when the report was sent to Traffica. because the possible values can and will change in the future.0xFFFF Field exists in the database Report_Length Table 700 Sgsn_Gtp_C_Stat_Report_Length Field name Sgsn_Gtp_C_Stat_Report_Count Data type in the IDS UINT32 SGSN version >=SG6 Explanation Contains information on how many reports of this type have been sent to Traffica.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface section. Possible values Table 702 464 Sgsn_Gtp_C_Stat_Report_Time Id:0900d805809551ce DN05148836 Issue 2-2 . there is a single-row entry for each table column. NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field. Possible values 0x0 . Traffica Reference Guide for SGSN Direct Interface Field exists in the database Table 702 RTT report descriptions Sgsn_Gtp_C_Stat_Report_Time and Sgsn_Gtp_C_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Sgsn_Gtp_C_Stat_Report_Time (Cont.) Field name Sgsn_Gtp_C_Stat_Report_Date Data type in the IDS BDCDATE SGSN version >=SG6 Explanation The date when the report was sent to Traffica. Table 706 Sgsn_Gtp_C_Stat_Papu_Capa DN05148836 Issue 2-2 Id:0900d805809551ce 465 . Possible values 0x1 – 0xFF Field exists in the database Table 704 Sgsn_Gtp_C_Stat_Papu_Id Field name Sgsn_Gtp_C_Stat_Physical_Papu_Id Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains the physical index of PAPU. Possible values Field exists in the database Table 703 Sgsn_Gtp_C_Stat_Report_Time and Sgsn_Gtp_C_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Sgsn_Gtp_C_Stat_Report_Date Field name Sgsn_Gtp_C_Stat_Papu_Id Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains the index of PAPU. Possible values 0x1 – 0xFF Field exists in the database Table 705 Sgsn_Gtp_C_Stat_Physical_Papu_Id Field name Sgsn_Gtp_C_Stat_Papu_Capa Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains the subscriber capacity of particular PAPU in SGSN. Large RA Support isn’t activated. FNSG01060.Value 0 means that PAPU doesn’t belong to any group.RTT report descriptions Possible values Traffica Reference Guide for SGSN Direct Interface 0x41 = maximum of 65 000 attached subscribers 0x64 = maximum of 100 000 attached subscribers 0xFA = maximum of 250 000 attached subscribers Field exists in the database Table 706 Sgsn_Gtp_C_Stat_Papu_Capa (Cont.) Field name Sgsn_Gtp_C_Stat_Papu_Group_Id Datatype in IDS UINT8 SGSN version >=SG6 Explanation This field contains PAPU group id Possible values 0-255. Field exists in the database Table 707 Sgsn_Gtp_C_Stat_Papu_Group_Id Field name Sgsn_Gtp_C_Stat_Sent_Gtpv0_Signaling Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of successfully received GTPv0 signaling packets. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Table 708 Sgsn_Gtp_C_Stat_Sent_Gtpv0_Signaling Field name Sgsn_Gtp_C_Stat_Bytes_In_Received_Gtpv0_Signaling Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number bytes in successfully received GTPv0 signaling packets Possible values 0x1 – 0xFFFFFFFF Field exists in the database Table 709 Sgsn_Gtp_C_Stat_Bytes_In_Received_Gtpv0_Signaling Field name Sgsn_Gtp_C_Stat_Sent_Gtpv0_Signaling Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of sent GTPv0 signaling packets. Table 710 466 Sgsn_Gtp_C_Stat_Sent_Gtpv0_Signaling Id:0900d805809551ce DN05148836 Issue 2-2 . This field is always 0 if feature. Traffica Reference Guide for SGSN Direct Interface Possible values RTT report descriptions 0x1 – 0xFFFFFFFF Field exists in the database Table 710 Sgsn_Gtp_C_Stat_Sent_Gtpv0_Signaling (Cont.) Field name Sgsn_Gtp_C_Stat_Bytes_In_Sent_Gtpv0_Signaling Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number bytes in sent GTPv0 signaling packets Possible values 0x1 – 0xFFFFFFFF Field exists in the database Table 711 Sgsn_Gtp_C_Stat_Bytes_In_Sent_Gtpv0_Signaling Field name Sgsn_Gtp_C_Stat_Received_Erroneous_Gtpv0_Signaling Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of received erroneous GTPv0 signaling packets. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Table 712 Sgsn_Gtp_C_Stat_Received_Erroneous_Gtpv0_Signaling Field name Sgsn_Gtp_C_Stat_Bytes_In_Received_Erroneous_GTPv0_Signaling Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of bytes in received erroneous GTPv0 signaling packets Possible values 0x1 – 0xFFFFFFFF Field exists in the database Table 713 Sgsn_Gtp_C_Stat_Bytes_In_Received_Erroneous_GTPv0_Signaling Field name Sgsn_Gtp_C_Stat_Received_Gtpv1_Signaling Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of successfully received GTPv1 signaling packets. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Table 714 Sgsn_Gtp_C_Stat_Received_Gtpv1_Signaling DN05148836 Issue 2-2 Id:0900d805809551ce 467 . RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Gtp_C_Stat_Bytes_In_Received_Gtpv1_Signaling Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number bytes in successfully received GTPv1 signaling packets. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Table 717 Sgsn_Gtp_C_Stat_Bytes_In_Sent_Gtpv1_Signaling Field name Sgsn_Gtp_C_Stat_Received_Erroneous_Gtpv1_Signaling Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of received erroneous GTPv1 signaling packets Possible values 0x1 – 0xFFFFFFFF Field exists in the database Table 718 Sgsn_Gtp_C_Stat_Received_Erroneous_Gtpv1_Signaling Field name Sgsn_Gtp_C_Stat_Bytes_In_Received_Erroneous_Gtpv1_Signaling Datatype in IDS UINT32 Table 719 468 Sgsn_Gtp_C_Stat_Bytes_In_Received_Erroneous_Gtpv1_Signaling Id:0900d805809551ce DN05148836 Issue 2-2 . Possible values 0x1 – 0xFFFFFFFF Field exists in the database Table 715 Sgsn_Gtp_C_Stat_Bytes_In_Received_Gtpv1_Signaling Field name Sgsn_Gtp_C_Stat_Sent_Gtpv1_Signaling Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number of sent GTPv1 signaling packets Possible values 0x1 – 0xFFFFFFFF Field exists in the database Table 716 Sgsn_Gtp_C_Stat_Sent_Gtpv1_Signaling Field name Sgsn_Gtp_C_Stat_Bytes_In_Sent_Gtpv1_Signaling Datatype in IDS UINT32 SGSN version >=SG6 Explanation Number bytes in sent GTPv1 signaling packets. For example.) 6. Possible values 0x1 – 0xFFFFFFFF Field exists in the database Table 719 Sgsn_Gtp_C_Stat_Bytes_In_Received_Erroneous_Gtpv1_Signaling (Cont. Field name Sgsn_Ippu_Gtp_Stat_Report_Id Data type in IDS UINT16 SGSN Version >=SG8 Explanation Contains information on the report type. NOTE: It is recommended that you do not create any of your own counters in CCMA or database queries based on this field. because the possible values can and will change in the future. there is a single-row entry for each table column. Possible Values Field exists in database Table 721 Report_Id Sgsn_Ippu_Gtp_Stat_Report_Id Field name Sgsn_Ippu_Gtp_Stat_Report_Length Data type in IDS UINT16 SGSN Version >=SG8 Table 722 Sgsn_Ippu_Gtp_Stat_Report_Length DN05148836 Issue 2-2 Id:0900d805809551ce 469 . The SQL data type appears after the column name and “=” symbol. the Sgsn_IPPU_GTP_STAT _Report_Count IDS field is Report Count Field in Traffic News SGSN_IPPU_GTP_STAT EVENT. Under the <SGSN_Release_Id>_ IPPU_GTP_STAT section. The Traffic News field names are the same as the database column names but use spaces instead of underscores between words. For example. the SGSN_IPPU_GTP_STAT_Report_Count IDS field is the Report_Count column in database table <SGSN_Release_Id>_IPPU_GTP_STAT.conf. The database column SQL data types can be found in the workspace configuration file dbd_sgsn_ippu_gtp_stat.18 IPPU_GTP_STAT fields The following table shows the IPPU_GTP_STAT fields: Traffic News event type SGSN_IPPU_GTP_STAT_EVENT Database table <SGSN_Release_Id>_IPPU_GTP_STAT Table 720 SGSN_IPPU_GTP_STAT fields The database column names are the same as the IDS field names without the SGSN_IPPU_GTP_STAT prefix.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions SGSN version >=SG6 Explanation Number of bytes in received erroneous GTPv1 signaling packets. Possible Values Field exists in database Table 725 Sgsn_Ippu_Gtp_Stat_Report_Time and Sgsn_Ippu_Gtp_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Sgsn_Ippu_Gtp_Stat_Report_Date Field name Sgsn_Ippu_Gtp_Stat_Event_Count Data type in IDS UINT32 Table 726 470 Sgsn_Ippu_Gtp_Stat_Event_Count Id:0900d805809551ce DN05148836 Issue 2-2 . Possible Values 0x0 – 0xFFFF Field exists in database Report_Length Table 722 Sgsn_Ippu_Gtp_Stat_Report_Length (Cont.) Field name Sgsn_Ippu_Gtp_Stat_Report_Count Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains information on how many reports of this type have been sent to Traffica. Possible Values 0x0 – 0xFFFFFFFF Field exists in database Report_Count Table 723 Sgsn_Ippu_Gtp_Stat_Report_Count Field name Sgsn_Ippu_Gtp_Stat_Report_Time Data type in IDS BCDTIME SGSN Version >=SG8 Explanation The time when the report was sent to Traffica.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Explanation This field contains the length of report in bytes. Possible Values Field exists in database Table 724 Sgsn_Ippu_Gtp_Stat_Report_Time and Sgsn_Ippu_Gtp_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Sgsn_Ippu_Gtp_Stat_Report_Time Field name Sgsn_Ippu_Gtp_Stat_Report_Date Data type in IDS BCD SGSN Version >=SG8 Explanation The date when the report was sent to Traffica. Value 0x28 is used if physical ippu id can't be solved due some internal error.) Field name Sgsn_Ippu_Gtp_Stat_Physical_Ippu_Id Data type in IDS UINT8 SGSN Version >=SG8 Explanation This field contains the physical index of ippu. Possible Values 0x0 – 0xFFFFFFFF Field exists in database Dl_Packets Table 729 Sgsn_Ippu_Gtp_Stat_Dl_Packets Field name Sgsn_Ippu_Gtp_Stat_Ul_Bytes Data type in IDS UINT32 SGSN Version >=SG8 Table 730 Sgsn_Ippu_Gtp_Stat_Ul_Bytes DN05148836 Issue 2-2 Id:0900d805809551ce 471 . Possible Values 0x0 – 0xFFFFFFFF Field exists in database Ul_Packets Table 728 Sgsn_Ippu_Gtp_Stat_Ul_Packets Field name Sgsn_Ippu_Gtp_Stat_Dl_Packets Data type in IDS UINT32 SGSN Version >=SG8 Explanation Number of GTP packets sent in downlink direction. Possible Values 0x1 – 0xFFFFFFFF Field exists in database Event_Count Table 726 Sgsn_Ippu_Gtp_Stat_Event_Count (Cont.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions SGSN Version >=SG8 Explanation This field contains information about how many events of this type have been detected and whether they are reported to Traffica or not. Possible Values 0x0 – 0xFF Field exists in database Physical_Ippu_Id Table 727 Sgsn_Ippu_Gtp_Stat_Physical_Ippu_Id Field name Sgsn_Ippu_Gtp_Stat_Ul_Packets Data type in IDS UINT32 SGSN Version >=SG8 Explanation Number of GTP packets sent in uplink direction. 100%) taken. Possible Values 0x0 – 0xFFFFFFFF Field exists in database Dl_Bytes Table 731 Sgsn_Ippu_Gtp_Stat_Dl_Bytes Field name Sgsn_Ippu_Gtp_Stat_Ave_Buf_Fill_Ratio_Numerator Data type in IDS UINT32 SGSN Version >=SG8 Explanation Nominator of average GTP buffer utilization. Number of samples taken. Only downlink data with acknowledged LLC mode is stored in the buffer. Possible Values 0x0 – 0xFFFFFFFF Field exists in database Ul_Bytes Table 730 Sgsn_Ippu_Gtp_Stat_Ul_Bytes (Cont.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Explanation Amount of GTP data in bytes sent in uplink direction. Sum of GTP buffer samples (0% .) Field name Sgsn_Ippu_Gtp_Stat_Dl_Bytes Data type in IDS UINT32 SGSN Version >=SG8 Explanation Amount of GTP data in bytes sent in downlink direction. Possible Values 0x0 – 0xFFFFFFFF Field exists in database Ave_Buf_Fill_Ratio_Nominator Table 733 Sgsn_Ippu_Gtp_Stat_Ave_Buf_Fill_Ratio_Nominator Field name Sgsn_Ippu_Gtp_Stat_Buffer_Fill_Ratio_Peak Data type in IDS UINT32 SGSN Version >=SG8 Table 734 472 Sgsn_Ippu_Gtp_Stat_Buffer_Fill_Ratio_Peak Id:0900d805809551ce DN05148836 Issue 2-2 . Possible Values 0x0 – 0xFFFFFFFF Field exists in database Ave_Buf_Fill_Ratio_Numerator Table 732 Sgsn_Ippu_Gtp_Stat_Ave_Buf_Fill_Ratio_Numerator Field name Sgsn_Ippu_Gtp_Stat_Ave_Buf_Fill_Ratio_Nominator Data type in IDS UINT32 SGSN Version >=SG8 Explanation Denominator to calculate average GTP buffer filling ratio. Possible Values 0% – 100% Field exists in database Buffer_Fill_Ratio_Peak Table 734 Sgsn_Ippu_Gtp_Stat_Buffer_Fill_Ratio_Peak (Cont. Possible Values Field exists in database Table 737 Dl_Iu_Gtp_Bytes_Pc_1 Sgsn_Dl_Iu_Gtp_Bytes_Pc_1 Field name Sgsn_Dl_Iu_Gtp_Packets_Pc_1 Data type in IDS UINT32 SGSN Version >=SG8 Table 738 Sgsn_Dl_Iu_Gtp_Packets_Pc_1 DN05148836 Issue 2-2 Id:0900d805809551ce 473 . the ethernet driver might discard incoming packets. This field shows the total amount of discarded ethernet packets. Possible Values 0x0 – 0xFFFFFFFF Field exists in database Discarded_Packets Table 735 Sgsn_Ippu_Gtp_Stat_Discarded_Packets Field name Sgsn_Gtp_Stat_ wynona_overl_data Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains value of overload data from wynona. Priority Class 1.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Explanation This field contains the value of peak GTP buffer filling ratio as a percentage.) Field name Sgsn_Ippu_Gtp_Stat_Discarded_Packets Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains the values for the amount of discarded GTP packets. Possible Values 0x0 – 0xFFFFFFFF Field exists in database Wynona_Overl_Datas Table 736 Sgsn_Gtp_Stat_ wynona_overl_data Field name Sgsn_Dl_Iu_Gtp_Bytes_Pc_1 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains GTP Data in bytes in DL on Iu-Interface. In case of a unit overload. Possible Values Field exists in database Table 741 Ul_Iu_Gtp_Bytes_Pc_1 Sgsn_Drop_Iu_Gtp_Bytes_Pc_1 Field name Sgsn_Drop_Iu_Gtp_Packets_Pc_1 Data type in IDS UINT32 SGSN Version >=SG8 Table 742 474 Sgsn_Drop_Iu_Gtp_Packets_Pc_1 Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Explanation Traffica Reference Guide for SGSN Direct Interface This field contains GTP Packets in bytes in DL on Iu-Interface. Possible Values Field exists in database Table 738 Dl_Iu_Gtp_Packets_Pc_1 Sgsn_Dl_Iu_Gtp_Packets_Pc_1 (Cont. Possible Values Field exists in database Table 739 Ul_Iu_Gtp_Bytes_Pc_1 Sgsn_Ul_Iu_Gtp_Bytes_Pc_1 Field name Sgsn_Ul_Iu_Gtp_Packets_Pc_1 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains GTP Data in packets in UL on Iu-Interface. Priority Class 1. Possible Values Field exists in database Table 740 Ul_Iu_Gtp_Packets_Pc_1 Sgsn_Ul_Iu_Gtp_Packets_Pc_1 Field name Sgsn_Drop_Iu_Gtp_Bytes_Pc_1 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains Dropped GTP Data Bytes on Iu-Interface. Priority Class 1. Priority Class 1.) Field name Sgsn_Ul_Iu_Gtp_Bytes_Pc_1 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains GTP Data in bytes in UL on Iu-Interface. Priority Class 1. ) Field name Sgsn_Dl_Iu_Gtp_Bytes_Pc_2 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains GTP Data in bytes in DL on Iu-Interface. Priority Class 1. Priority Class 2.Traffica Reference Guide for SGSN Direct Interface Explanation RTT report descriptions This field contains Dropped GTP Data Packets on Iu-Interface. Priority Class 2. Possible Values Field exists in database Table 743 Dl_Iu_Gtp_Bytes_Pc_2 Sgsn_Dl_Iu_Gtp_Bytes_Pc_2 Field name Sgsn_Dl_Iu_Gtp_Packets_Pc_2 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains GTP Packets in bytes in DL on Iu-Interface. Possible Values Field exists in database Table 742 Drop_Iu_Gtp_Packets_Pc_1 Sgsn_Drop_Iu_Gtp_Packets_Pc_1 (Cont. Priority Class 2. Possible Values Field exists in database Table 745 Ul_Iu_Gtp_Bytes_Pc_2 Sgsn_Ul_Iu_Gtp_Bytes_Pc_2 Field name Sgsn_Ul_Iu_Gtp_Packets_Pc_2 Data type in IDS UINT32 SGSN Version >=SG8 Table 746 Sgsn_Ul_Iu_Gtp_Packets_Pc_2 DN05148836 Issue 2-2 Id:0900d805809551ce 475 . Possible Values Field exists in database Table 744 Dl_Iu_Gtp_Packets_Pc_2 Sgsn_Dl_Iu_Gtp_Packets_Pc_2 Field name Sgsn_Ul_Iu_Gtp_Bytes_Pc_2 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains GTP Data in bytes in UL on Iu-Interface. Possible Values Field exists in database Table 748 Drop_Iu_Gtp_Packets_Pc_2 Sgsn_Drop_Iu_Gtp_Packets_Pc_2 Field name Sgsn_Dl_Iu_Gtp_Bytes_Pc_3 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains GTP Data in bytes in DL on Iu-Interface. Possible Values Field exists in database Table 749 Dl_Iu_Gtp_Bytes_Pc_3 Sgsn_Dl_Iu_Gtp_Bytes_Pc_3 Field name Sgsn_Dl_Iu_Gtp_Packets_Pc_3 Data type in IDS UINT32 SGSN Version >=SG8 Table 750 476 Sgsn_Dl_Iu_Gtp_Packets_Pc_3 Id:0900d805809551ce DN05148836 Issue 2-2 . Priority Class 2. Possible Values Field exists in database Table 747 Ul_Iu_Gtp_Bytes_Pc_2 Sgsn_Drop_Iu_Gtp_Bytes_Pc_2 Field name Sgsn_Drop_Iu_Gtp_Packets_Pc_2 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains Dropped GTP Data Packets on Iu-Interface.RTT report descriptions Explanation Traffica Reference Guide for SGSN Direct Interface This field contains GTP Data in packets in UL on Iu-Interface.) Field name Sgsn_Drop_Iu_Gtp_Bytes_Pc_2 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains Dropped GTP Data Bytes on Iu-Interface. Priority Class 3. Possible Values Field exists in database Table 746 Ul_Iu_Gtp_Packets_Pc_2 Sgsn_Ul_Iu_Gtp_Packets_Pc_2 (Cont. Priority Class 2. Priority Class 2. Priority Class 3. Possible Values Field exists in database Table 750 Dl_Iu_Gtp_Packets_Pc_3 Sgsn_Dl_Iu_Gtp_Packets_Pc_3 (Cont.) Field name Sgsn_Ul_Iu_Gtp_Bytes_Pc_3 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains GTP Data in bytes in UL on Iu-Interface.Traffica Reference Guide for SGSN Direct Interface Explanation RTT report descriptions This field contains GTP Packets in bytes in DL on Iu-Interface. Priority Class 3. Possible Values Field exists in database Table 751 Ul_Iu_Gtp_Bytes_Pc_3 Sgsn_Ul_Iu_Gtp_Bytes_Pc_3 Field name Sgsn_Ul_Iu_Gtp_Packets_Pc_3 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains GTP Data in packets in UL on Iu-Interface. Priority Class 3. Possible Values Field exists in database Table 752 Ul_Iu_Gtp_Packets_Pc_3 Sgsn_Ul_Iu_Gtp_Packets_Pc_3 Field name Sgsn_Drop_Iu_Gtp_Bytes_Pc_3 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains Dropped GTP Data Bytes on Iu-Interface. Priority Class 3. Possible Values Field exists in database Table 753 Ul_Iu_Gtp_Bytes_Pc_3 Sgsn_Drop_Iu_Gtp_Bytes_Pc_3 Field name Sgsn_Drop_Iu_Gtp_Packets_Pc_3 Data type in IDS UINT32 SGSN Version >=SG8 Table 754 Sgsn_Drop_Iu_Gtp_Packets_Pc_3 DN05148836 Issue 2-2 Id:0900d805809551ce 477 . RTT report descriptions Explanation Traffica Reference Guide for SGSN Direct Interface This field contains Dropped GTP Data Packets on Iu-Interface. Priority Class 4. Priority Class 4.) Field name Sgsn_Dl_Iu_Gtp_Bytes_Pc_4 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains GTP Data in bytes in DL on Iu-Interface. Priority Class 3. Possible Values Field exists in database Table 757 Ul_Iu_Gtp_Bytes_Pc_1 Sgsn_Ul_Iu_Gtp_Bytes_Pc_4 Field name Sgsn_Ul_Iu_Gtp_Packets_Pc_4 Data type in IDS UINT32 SGSN Version >=SG8 Table 758 478 Sgsn_Ul_Iu_Gtp_Packets_Pc_4 Id:0900d805809551ce DN05148836 Issue 2-2 . Possible Values Field exists in database Table 755 Dl_Iu_Gtp_Bytes_Pc_4 Sgsn_Dl_Iu_Gtp_Bytes_Pc_4 Field name Sgsn_Dl_Iu_Gtp_Packets_Pc_4 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains GTP Packets in bytes in DL on Iu-Interface. Possible Values Field exists in database Table 754 Drop_Iu_Gtp_Packets_Pc_3 Sgsn_Drop_Iu_Gtp_Packets_Pc_3 (Cont. Possible Values Field exists in database Table 756 Dl_Iu_Gtp_Packets_Pc_4 Sgsn_Dl_Iu_Gtp_Packets_Pc_4 Field name Sgsn_Ul_Iu_Gtp_Bytes_Pc_4 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains GTP Data in bytes in UL on Iu-Interface. Priority Class 4. Priority Class Streaming. Possible Values Field exists in database Table 759 Drop_Iu_Gtp_Bytes_Pc_4 Sgsn_Drop_Iu_Gtp_Bytes_Pc_4 Field name Sgsn_Drop_Iu_Gtp_Packets_Pc_4 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains Dropped GTP Data Packets on Iu-Interface. Possible Values Field exists in database Table 760 Drop_Iu_Gtp_Packets_Pc_4 Sgsn_Drop_Iu_Gtp_Packets_Pc_4 Field name Sgsn_Dl_Iu_Gtp_Bytes_ Pc_Str Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field GTP Data in bytes in DL on Iu-Interface. Possible Values Field exists in database Table 761 Dl_Iu_Gtp_Bytes_ Pc_Str Sgsn_Dl_Iu_Gtp_Bytes_ Pc_Str Field name Sgsn_Dl_Iu_Gtp_Packets_ Pc_Str Data type in IDS UINT32 SGSN Version >=SG8 Table 762 Sgsn_Dl_Iu_Gtp_Packets_ Pc_Str DN05148836 Issue 2-2 Id:0900d805809551ce 479 . Priority Class 4.) Field name Sgsn_Drop_Iu_Gtp_Bytes_Pc_4 Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains Dropped GTP Data Bytes on Iu-Interface. Possible Values Field exists in database Table 758 Ul_Iu_Gtp_Packets_Pc_4 Sgsn_Ul_Iu_Gtp_Packets_Pc_4 (Cont. Priority Class 4.Traffica Reference Guide for SGSN Direct Interface Explanation RTT report descriptions This field contains GTP Data in packets in UL on Iu-Interface. Priority Class 4. Priority Class Streaming. Possible Values Field exists in database Table 765 Drop_Iu_Gtp_Bytes_ Pc_Str Sgsn_Drop_Iu_Gtp_Bytes_ Pc_Str Field name Sgsn_Drop_Iu_Gtp_Packets_ Pc_Str Data type in IDS UINT32 SGSN Version >=SG8 Table 766 480 Sgsn_Drop_Iu_Gtp_Packets_ Pc_Str Id:0900d805809551ce DN05148836 Issue 2-2 . Possible Values Field exists in database Table 764 Ul_Iu_Gtp_Packets_ Pc_Str Sgsn_Ul_Iu_Gtp_Packets_ Pc_Str Field name Sgsn_Drop_Iu_Gtp_Bytes_ Pc_Str Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains Dropped GTP Data Bytes on Iu-Interface. Priority Class Streaming.RTT report descriptions Explanation Traffica Reference Guide for SGSN Direct Interface This field GTP Data in Packets in DL on Iu-Interface. Priority Class Streaming. Possible Values Field exists in database Table 763 Ul_Iu_Gtp_Bytes_ Pc_Str Sgsn_Ul_Iu_Gtp_Bytes_ Pc_Str Field name Sgsn_Ul_Iu_Gtp_Packets_ Pc_Str Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field GTP Data in Packets in UL on Iu-Interface.) Field name Sgsn_Ul_Iu_Gtp_Bytes_ Pc_Str Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field GTP Data in bytes in UL on Iu-Interface. Possible Values Field exists in database Table 762 Dl_Iu_Gtp_Packets_ Pc_Str Sgsn_Dl_Iu_Gtp_Packets_ Pc_Str (Cont. Priority Class Streaming. Priority Class Conversational. Priority Class Conversational. Possible Values Field exists in database Table 766 Drop_Iu_Gtp_Packets_ Pc_Str Sgsn_Drop_Iu_Gtp_Packets_ Pc_Str (Cont.) Field name Sgsn_Dl_Iu_Gtp_Bytes_ Pc_Con Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains GTP Data in bytes in DL on Iu-Interface. Possible Values Field exists in database Table 768 Dl_Iu_Gtp_Packets_ Pc_Con Sgsn_Dl_Iu_Gtp_Packets_ Pc_Con Field name Sgsn_Ul_Iu_Gtp_Bytes_ Pc_Con Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains GTP Data in bytes in UL on Iu-Interface. Possible Values Field exists in database Table 767 Dl_Iu_Gtp_Bytes_ Pc_Con Sgsn_Dl_Iu_Gtp_Bytes_ Pc_Con Field name Sgsn_Dl_Iu_Gtp_Packets_ Pc_Con Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains GTP Data in Packets in DL on Iu-Interface. Priority Class Conversational. Possible Values Field exists in database Table 769 Ul_Iu_Gtp_Bytes_ Pc_Con Sgsn_Ul_Iu_Gtp_Bytes_ Pc_Con Field name Sgsn_Ul_Iu_Gtp_Packets_ Pc_Con Data type in IDS UINT32 SGSN Version >=SG8 Table 770 Sgsn_Ul_Iu_Gtp_Packets_ Pc_Con DN05148836 Issue 2-2 Id:0900d805809551ce 481 . Priority Class Streaming.Traffica Reference Guide for SGSN Direct Interface Explanation RTT report descriptions This field contains Dropped GTP Data packets on Iu-Interface. Possible Values Field exists in database Table 772 Drop_Iu_Gtp_Packets_ Pc_Con Sgsn_Drop_Iu_Gtp_Packets Pc_Con Field name Sgsn_Ippu_Gtp_Stat_Dropped_Dl_Bytes Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains Dropped DL bytes due to data throughput limiter per IPPU. Possible Values Field exists in database Table 771 Drop_Iu_Gtp_Bytes_ Pc_Con Sgsn_Drop_Iu_Gtp_Bytes_ Pc_Con Field name Sgsn_Drop_Iu_Gtp_Packets Pc_Con Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains Dropped GTP Data packets on Iu-Interface. Possible Values Field exists in database Table 773 Dropped_Dl_Bytes Sgsn_Ippu_Gtp_Stat_Dropped_Dl_Bytes 6. Priority Class Conversational.RTT report descriptions Explanation Traffica Reference Guide for SGSN Direct Interface This field contains GTP Data in Packets in UL on Iu-Interface.19 IPPU_PDP_THR_STAT fields The following table shows the IPPU_PDP_THR_STAT fields: 482 Id:0900d805809551ce DN05148836 Issue 2-2 .) Field name Sgsn_Drop_Iu_Gtp_Bytes_ Pc_Con Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains Dropped GTP Data Bytes on Iu-Interface. Priority Class Conversational. Priority Class Conversational. Possible Values Field exists in database Table 770 Ul_Iu_Gtp_Packets_ Pc_Con Sgsn_Ul_Iu_Gtp_Packets_ Pc_Con (Cont. there is a single-row entry for each table column. because the possible values can and will change in the future.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Traffic News event type SGSN_IPPU_PDP_THR_STAT_EVENT Database table <SGSN_Release_Id>_IPPU_PDP_THR_STAT Table 774 SGSN_IPPU_PDP_THR_STAT fields The database column names are the same as the IDS field names without the SGSN_IPPU_PDP_THR_STAT prefix. The database column SQL data types can be found in the workspace configuration file dbd_sgsn_ippu_pdp_thr_stat.0xFFFF Field exists in database Report_Length Table 776 Sgsn_Ippu_Pdp_Thr_Stat_Report_Length Field name Sgsn_Ippu_Pdp_Thr_Stat_Report_Count Data type in IDS UINT32 Table 777 Sgsn_Ippu_Pdp_Thr_Stat_Report_Count DN05148836 Issue 2-2 Id:0900d805809551ce 483 . Possible Values 0x0 . NOTE: It is recommended that you do not create any of your own counters in CCMA or databases queries based on this field.Under the <SGSN_Release_Id>_IPPU_PDP_THR_STAT section. the Sgsn_IPPU_PDP_THR_STAT_Report_Count IDS field is Report Count field in Traffic News SGSN_IPPU_PDP_THR_STAT EVENT. For example. The SQL datatype appears after the column name and “=” symbol. For example. Possible Values Field exists in database Table 775 Sgsn_Ippu_Pdp_Thr_Stat_Report_Id Field name Sgsn_Ippu_Pdp_Thr_Stat_Report_Length Data type in IDS UINT16 SGSN Version >=SG8 Explanation This field contains the length of report in bytes.conf. Field name Sgsn_Ippu_Pdp_Thr_Stat_Report_Id Data type in IDS UINT16 SGSN Version >=SG8 Explanation Contains information on the report type. the SGSN_IPPU_PDP_THR_STAT_Report_Count IDS field is the Report_Count column in database table <SGSN_Release_Id>_IPPU_PDP_THR_STAT. This field is needed because empty cells are dropped from ippu_pdp_thr_stat table. The Traffic News field names are the same as the database column names but use spaces instead of underscores between words. Possible Values Field exists in database Table 777 Report_Count Sgsn_Ippu_Pdp_Thr_Stat_Report_Count (Cont.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface SGSN Version >=SG8 Explanation Contains information on how many reports of this type have been sent to Traffica.) Field name Sgsn_Ippu_Pdp_Thr_Stat_Report_Time Data type in IDS BCDTIME SGSN Version >=SG8 Explanation The time when the report was sent to Traffica. Possible Values Field exists in database Table 779 Sgsn_Ippu_Pdp_Thr_Stat_Report_Time and Sgsn_Ippu_Pdp_Thr_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Sgsn_Ippu_Pdp_Thr_Stat_Report_Date Field name Sgsn_Ippu_Pdp_Thr_Stat_Pdp_Cxt_Element_Count Data type in IDS UINT16 SGSN Version >=SG8 Explanation Number of PDP Context elements. Possible Values 0x1 – 0xFFFF Field exists in database Pdp_Cxt_Element_Count Table 780 Field name Table 781 484 Sgsn_Ippu_Pdp_Thr_Stat_Pdp_Cxt_Element_Count Sgsn_Ippu_Pdp_Thr_Stat_Physical_Ippu_Id Sgsn_Ippu_Pdp_Thr_Stat_Physical_Ippu_Id Id:0900d805809551ce DN05148836 Issue 2-2 . Possible Values Field exists in database Table 778 Sgsn_Ippu_Pdp_Thr_Stat_Report_Time and Sgsn_Ippu_Pdp_Thr_Stat_Report_Date are as SQL TIMESTAMP datatype in column Report_Time Sgsn_Ippu_Pdp_Thr_Stat_Report_Time Field name Sgsn_Ippu_Pdp_Thr_Stat_Report_Date Data type in IDS BCD SGSN Version >=SG8 Explanation The date when the report was sent to Traffica. Possible Values 0x1 – 0xFFFF Field exists in database Last_2bytes_Ggsn_Address Table 782 Sgsn_Ippu_Pdp_Thr_Stat_Last_2bytes_Ggsn_Address Field name Sgsn_Ippu_Pdp_Thr_Stat_Charging_Index Data type in IDS UINT32 SGSN Version >=SG8 Explanation This field contains the index of charging.Traffica Reference Guide for SGSN Direct Interface Data type in IDS UINT8 SGSN Version >=SG8 Explanation This field contains the physical index of IPPU. Possible Values 0x1 – 0xFFFFFFFF Field exists in database Charging_Index Table 783 Sgsn_Ippu_Pdp_Thr_Stat_Charging_Index Field name Sgsn_Ippu_Pdp_Thr_Stat_Duration Data type in IDS UINT8 SGSN Version >=SG8 Explanation This field contains the duration of PDP context session. Possible Values 0x1 – 0xFF Field exists in database Duration Table 784 Sgsn_Ippu_Pdp_Thr_Stat_Duration Field name Sgsn_Ippu_Pdp_Thr_Stat_Ts_Time Data type in IDS BCDTIME SGSN Version >=SG8 Table 785 RTT report descriptions Sgsn_Ippu_Pdp_Thr_Stat_Ts_Time DN05148836 Issue 2-2 Id:0900d805809551ce 485 . Possible Values 0x1 – 0xFF Field exists in database Physical_Ippu_Id Table 781 Sgsn_Ippu_Pdp_Thr_Stat_Physical_Ippu_Id (Cont.) Field name Sgsn_Ippu_Pdp_Thr_Stat_Last_2bytes_Ggsn_Address Data type in IDS UINT16 SGSN Version >=SG8 Explanation Last two bytes from Ggsn Ip-Address. Possible Values 0x0 .0xFF Field exists in database No Table 787 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Alloc_Retention Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Deliv_Of_Erroneous Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Explanation The time when the TS was started. Possible Values Table 789 486 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Delivery_Order Id:0900d805809551ce DN05148836 Issue 2-2 . Possible Values Field exists in database Table 788 No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Deliv_Of_Erroneous Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Delivery_Order Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible Values 0x0 = Release 97/98 0x1 = Release 99 Field exists in database Table 786 Qos_Negotiated_Ms_Cont_Prof_Flag Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_Ms_Cont_Prof_Flag Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Alloc_Retention Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.) Field name Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_Ms_Cont_Prof_Flag Data type in IDS UINT8 SGSN Version >=SG8 Explanation Field of Quality of Service that the user requests. Field exists in database Ts_Time Table 785 Sgsn_Ippu_Pdp_Thr_Stat_Ts_Time (Cont. Possible Values Time is in format hundredsofseconds:seconds:minutes:hours. Possible Values 0x00 .0xFF Field exists in database Qos_Negotiated_4 Table 793 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_4 DN05148836 Issue 2-2 Id:0900d805809551ce 487 .Traffica Reference Guide for SGSN Direct Interface Field exists in database Table 789 RTT report descriptions No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Delivery_Order (Cont. Possible Values 0x00 . Possible Values 0x00 .) Field name Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_1 Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.0xFF Field exists in database Qos_Negotiated_2 Table 791 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_2 Field name Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_3 Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.0xFF Field exists in database Qos_Negotiated_1 Table 790 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_1 Field name Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_2 Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.0xFF Field exists in database Qos_Negotiated_3 Table 792 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_3 Field name Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_4 Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible Values 0x00 . 0xFF Field exists in database Qos_Negotiated_6 Table 795 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_6 Field name Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_7 Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.0xFF Field exists in database Qos_Negotiated_8 Table 797 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_8 Field name Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_9 Data type in IDS UINT8 Table 798 488 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_9 Id:0900d805809551ce DN05148836 Issue 2-2 .RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_5 Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.0xFF Field exists in database Qos_Negotiated_5 Table 794 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_5 Field name Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_6 Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible Values 0x00 .0xFF Field exists in database Qos_Negotiated_7 Table 796 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_7 Field name Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_8 Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible Values 0x00 . Possible Values 0x00 . Possible Values 0x00 . Possible Values 0x00 .0xFF Field exists in database Qos_Negotiated_9 Table 798 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_9 (Cont.0xFF Field exists in database Qos_Negotiated_11 Table 800 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_11 Field name Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_12 Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible Values 0x00 . Table 802 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_13 DN05148836 Issue 2-2 Id:0900d805809551ce 489 . Possible Values 0x00 . Possible Values 0x00 .0xFF Field exists in database Qos_Negotiated_12 Table 801 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_12 Field name Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_13 Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.) Field name Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_10 Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.0xFF Field exists in database Qos_Negotiated_10 Table 799 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_10 Field name Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_11 Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. 0xFF Field exists in database Qos_Negotiated_14 Table 803 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_14 Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Traffic_Class Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible Values Field exists in database Table 804 No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Traffic_Class Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Max_Sdu_Size Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible Values Field exists in database Table 805 No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Max_Sdu_Size Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Max_Bitrate_Ul Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.) Field name Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_14 Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible Values 0x00 .RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Possible Values 0x00 .0xFF Field exists in database Qos_Negotiated_13 Table 802 Sgsn_Ippu_Pdp_Thr_Stat_Qos_Negotiated_13 (Cont. Possible Values Field exists in database Table 806 490 No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Max_Bitrate_Ul Id:0900d805809551ce DN05148836 Issue 2-2 . Possible Values Field exists in database Table 808 No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Sdu_Error_Ratio Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Residual_Ber Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible Values Field exists in database Table 807 No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Max_Bitrate_Dl Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Sdu_Error_Ratio Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible Values Field exists in database Table 810 No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Traffic_Handling_Prio Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Transfer_Delay Data type in IDS UINT8 Table 811 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Transfer_Delay DN05148836 Issue 2-2 Id:0900d805809551ce 491 . Possible Values Field exists in database Table 809 No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Residual_Ber Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Traffic_Handling_Prio Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Max_Bitrate_Dl Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible Values Field exists in database Table 811 No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Transfer_Delay (Cont. Possible Values Field exists in database Table 813 No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Guaran_Bit_Rate_Dl Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Spare Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible Values Field exists in database Table 814 No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Spare Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Signalling_Indication Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible Values Field exists in database Table 812 No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Guaran_Bit_Rate_Ul Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Guaran_Bit_Rate_Dl Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.) Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Guaran_Bit_Rate_Ul Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Table 815 492 Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Signalling_Indication Id:0900d805809551ce DN05148836 Issue 2-2 . Possible Values Field exists in database Table 818 No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Ext_Guaran_Bit_Rate_Dl Field name Sgsn_Ippu_Pdp_Thr_Stat_Imsi_Length Data type in IDS UINT8 SGSN Version >=SG8 Explanation The length of IMSI. Possible Values Field exists in database Table 816 No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Source_Statistics Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Ext_Max_Bit_Rate_Dl Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible Values Field exists in database Table 817 No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Ext_Max_Bit_Rate_Dl Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Ext_Guaran_Bit_Rate_Dl Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Possible Values 15-16 Field exists in database Imsi_Length Table 819 Sgsn_Ippu_Pdp_Thr_Stat_Imsi_Length DN05148836 Issue 2-2 Id:0900d805809551ce 493 .) Field name Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Source_Statistics Data type in IDS UINT8 SGSN Version >=SG8 Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.Traffica Reference Guide for SGSN Direct Interface RTT report descriptions Possible Values Field exists in database Table 815 No Sgsn_Ippu_Pdp_Thr_Stat_Negotiated_QoS_Signalling_Indication (Cont. Possible Values 0x1 – 0xFFFFFFFF Field exists in database Downlink_Data Table 822 Sgsn_Ippu_Pdp_Thr_Stat_Downlink_Data Field name Sgsn_Ippu_Pdp_Thr_Stat_Ra_Access_Type Data type in IDS UINT8 SGSN Version >=SG8 Explanation The type of the radio access network.RTT report descriptions Traffica Reference Guide for SGSN Direct Interface Field name Sgsn_Ippu_Pdp_Thr_Stat_Imsi Data type in IDS BDCREV8(8) SGSN Version >=SG8 Explanation Contains the IMSI-number that caused the report to be sent. Possible Values utran_c = 0x01 geran_c = 0x02 distr_uma_c = 0xD0 ihspa_c = 0xD2 not_def_c = 0xFF Field exists in database Table 823 494 Ra_Access_Type Sgsn_Ippu_Pdp_Thr_Stat_Ra_Access_Type Id:0900d805809551ce DN05148836 Issue 2-2 . Possible Values 0x1 – 0xFFFFFFFF Field exists in database Uplink_Data Table 821 Sgsn_Ippu_Pdp_Thr_Stat_Uplink_Data Field name Sgsn_Ippu_Pdp_Thr_Stat_Downlink_Data Data type in IDS UINT32 SGSN Version >=SG8 Explanation Downlink data amount in bytes. Possible Values IMSI Field exists in database Imsi Table 820 Sgsn_Ippu_Pdp_Thr_Stat_Imsi Field name Sgsn_Ippu_Pdp_Thr_Stat_Uplink_Data Data type in IDS UINT32 SGSN Version >=SG8 Explanation Uplink data amount in bytes. but their values are extracted from the database fields.1 Table 826 Logical field: Req_Qos_Ext_Max_Br_Ul Traffic News event type SGSN_RTT Traffic News field index 2805 Traffic News field name Req Qos Ext Guar Br Ul Explanation Field of Quality of Service that the user requests. blocks of bits. Logical fields can represent a single bit. a fixed length part of a varchar field. Version >SG7 PCD3. a variable length part of a varchar field (for example country code) or a combination of the following database fields: Traffic News event type SGSN_RTT_EVENT Traffic News field index 10500 Traffic News field name Operator Explanation First 5 characters extracted from IMSI field Table 824 Traffic News event type SGSN_RTT_EVENT Traffic News field index 10501 Traffic News field name Mobile station Explanation First 6characters extracted from IMEI field Table 825 Logical field: Mobile station Traffic News event type SGSN_RTT Traffic News field index 2806 Traffic News field name Req Qos Ext Max Br Ul Explanation Field of Quality of Service that the user requests.Traffica Reference Guide for SGSN Direct Interface Traffic News logical fields 7 Traffic News logical fields Traffic News logical fields are fields that do not have one to one correspondence with the actual fields in the database.1 Table 827 Logical field: Req_Qos_Ext_Guar_Br_Ul Traffic News event type SGSN_RTT Traffic News field index 2804 Table 828 DN05148836 Issue 2-2 Logical field: Operator Logical field: Neg_Qos_Ext_Max_Br_Ul Id:0900d805809551ce 495 . Version >SG7 PCD3. 1 Table 829 Logical field: Neg_Qos_Ext_Guar_Br_Ul Traffic News event type SGSN_PDP_THR Traffic News field index 2807 Traffic News field name Qos Negotiated 13 Explanation Version Table 830 >SG7 PCD3.Traffic News logical fields Traffica Reference Guide for SGSN Direct Interface Traffic News field name Neg Qos Ext Max Br Ul Explanation Quality of Service that the user gets after SGSN and GGSN negotiation Version >SG7 PCD3.) Traffic News event type SGSN_RTT Traffic News field index 2803 Traffic News field name Neg Qos Ext Guar Br Ul Explanation Quality of Service that the user gets after SGSN and GGSN negotiation Version >SG7 PCD3. Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.1 Logical field: Extended Negotiated Qos Alloc Retention Id:0900d805809551ce DN05148836 Issue 2-2 . Version >=SG8 Table 832 496 >SG7 PCD3.1 Logical field: Qos Negotiated 13 Traffic News event type SGSN_PDP_THR Traffic News field index 2808 Traffic News field name Qos Negotiated 14 Explanation Version Table 831 Logical field: Qos Negotiated 14 Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50345 Traffic News field name Extended Negotiated Qos Alloc Retention.1 Table 828 Logical field: Neg_Qos_Ext_Max_Br_Ul (Cont. Version >=SG8 Table 835 Logical field: Extended Negotiated Qos Traffic Class Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50349 Traffic News field name Extended Negotiated Qos Max Sdu Size Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Version >=SG8 Table 836 Logical field: Extended Negotiated Qos Max Sdu Size Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50350 Traffic News field name Extended Negotiated Qos Max Bitrate Ul Table 837 DN05148836 Issue 2-2 Traffic News logical fields Logical field:Extended Negotiated Qos Max Bitrate Ul Id:0900d805809551ce 497 . Version >=SG8 Table 834 Logical field: Extended Negotiated Qos Delivery Order Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50348 Traffic News field name Extended Negotiated Qos Traffic Class Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Version >=SG8 Table 833 Logical field: Extended Negotiated Qos Deliv Of Errorneous Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50347 Traffic News field name Extended Negotiated Qos Delivery Order Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.Traffica Reference Guide for SGSN Direct Interface Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50346 Traffic News field name Extended Negotiated Qos Deliv Of Errorneous Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. ) Logical field: Extended Negotiated Qos Traffic Handling Prio Id:0900d805809551ce DN05148836 Issue 2-2 .Traffic News logical fields Traffica Reference Guide for SGSN Direct Interface Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Version >=SG8 Table 838 Logical field: Extended Negotiated Qos Max Bitrate Dl Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50352 Traffic News field name Extended Negotiated Qos Sdu Error Ratio Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Version >=SG8 Table 837 Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50351 Traffic News field name Extended Negotiated Qos Max Bitrate Dl Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Version >=SG8 Table 841 498 Logical field:Extended Negotiated Qos Max Bitrate Ul (Cont. Version >=SG8 Table 840 Logical field:Extended Negotiated Qos Residual Ber Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50354 Traffic News field name Extended Negotiated Qos Traffic Handling Prio Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Version >=SG8 Table 839 Logical field: Extended Negotiated Qos Sdu Error Ratio Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50353 Traffic News field name Extended Negotiated Qos Residual Ber Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Traffica Reference Guide for SGSN Direct Interface Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50355 Traffic News field name Extended Negotiated Qos Transfer Delay Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Version >=SG8 Table 845 Logical field: Extended Negotiated Qos Spare Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50359 Traffic News field name Extended Negotiated Qos Signalling Indication Table 846 DN05148836 Issue 2-2 Traffic News logical fields Logical field: Extended Negotiated Qos Signalling Indication Id:0900d805809551ce 499 . Version >=SG8 Table 844 Logical field: Extended Negotiated Qos Guaran Bit Rate Dl Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50358 Traffic News field name Extended Negotiated Qos Spare Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Version >=SG8 Table 842 Logical field: Extended Negotiated Qos Transfer Delay Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50356 Traffic News field name Extended Negotiated Qos Guaran Bit Rate Ul Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Version >=SG8 Table 843 Logical field: Extended Negotiated Qos Guaran Bit Rate Ul Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50357 Traffic News field name Extended Negotiated Qos Guaran Bit Rate Dl Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Version >=SG8 Table 846 Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50360 Traffic News field name Extended Negotiated Qos Source Statistics Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Version >=SG8 Table 849 Logical field: Extended Negotiated Qos Ext Guaran Bit Rate Dl Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50381 Traffic News field name Extended Negotiated Qos Ext Max Bit Rate Ul Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Version >=SG8 Table 847 Logical field: Extended Negotiated Qos Source Statistics Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50361 Traffic News field name Extended Negotiated Qos Ext Max Bit Rate Dl Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.Traffic News logical fields Traffica Reference Guide for SGSN Direct Interface Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Version >=SG8 Table 850 500 Logical field: Extended Negotiated Qos Signalling Indication (Cont. Version >=SG8 Table 848 Logical field: Extended Negotiated Qos Ext Max Bit Rate Dl Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50362 Traffic News field name Extended Negotiated Qos Ext Guaran Bit Rate Dl Explanation Quality of Service that the user gets after SGSN and GGSN negotiation.) Logical field: Extended Negotiated Qos Ext Max Bit Rate Ul Id:0900d805809551ce DN05148836 Issue 2-2 . Traffica Reference Guide for SGSN Direct Interface Traffic News event type SGSN_IPPU_PDP_THR_STAT Traffic News field index 50382 Traffic News field name Extended Negotiated Qos Ext Guaran Bit Rate Ul Explanation Quality of Service that the user gets after SGSN and GGSN negotiation. Version >=SG8 Table 851 DN05148836 Issue 2-2 Traffic News logical fields Logical field: Extended Negotiated Qos Ext Guaran Bit Rate Ul Id:0900d805809551ce 501 . Note that the External cause value can be found in the field Sgsn_Rtt_Ps_External_Cause in PS (packet switched) cases. Internal Error cause Internal cause value GMM cause (External cause to MS) External Cause Value AUTH_FAILURE_C 0x14 Illegal MS #3 UNKNOWN_EQUIP_C 0x2E Illegal ME #6 IMEI_CHK_FAILED_C 0x51 Illegal ME #6 NO_GPRS_SUBSCR_C 0x30 GPRS services not allowed #7 IMSI_U_IN_AUC_C 0x2A GPRS services not allowed #7 IMEI_FAIL_CS_ALLOW_C 0xDB GPRS services not allowed #7 IMSI_U_IN_HLR_C GPRS services and non-GPRS services not allowed #8 HLR_ACC_REST_2G_11_ 0x135 C PLMN not allowed #11 HLR_ACC_REST_3G_11_ 0x13A C PLMN not allowed #11 PLMN_REST_2GTO2G_1 1_C 0x13F PLMN not allowed #11 PLMN_REST_2GTO3G_1 1_C 0x144 PLMN not allowed #11 PLMN_REST_3GTO2G_1 1_C 0x149 PLMN not allowed #11 PLMN_REST_3GTO3G_1 1_C 0x14E PLMN not allowed #11 SUBS_CNT_REST_2G_1 1_C 0x153 PLMN not allowed #11 SUBS_CNT_REST_3G_1 1_C 0x158 PLMN not allowed #11 SUBS_CNT_REST_CAM_ 11_C 0x178 PLMN not allowed #11 Table 852 502 0x29 MS initiated attach (GPRS or combined) rejected by network Id:0900d805809551ce DN05148836 Issue 2-2 . and in the field Sgsn_Rtt_Cs_External_Cause in CS (circuit switched) cases. Explanations for the values can be found in the possible values for the aforementioned fields in this document. Explanations for the values can be found in the possible values for the aforementioned fields in this document.Appendix Internal cause to interface cause mapping from MM & SM processes Traffica Reference Guide for SGSN Direct Interface A Appendix Internal cause to interface cause mapping from MM & SM processes Note that the Internal cause value can be found in the field Sgsn_Rtt_Cause_Cause in PS (packet switched) cases. and in the field Sgsn_Rtt_Non_Gprs_Cause_Cause in CS (circuit switched) cases. ) Id:0900d805809551ce 503 .Traffica Reference Guide for SGSN Direct Interface Internal cause value GMM cause (External cause to MS) External Cause Value 0x17D PLMN not allowed #11 CONTR_ROAM_RL97_RE 0x0B7 J_C Location Area not allowed #12 HLR_ACC_REST_2G_12_ 0x136 C Location Area not allowed #12 HLR_ACC_REST_3G_12_ 0x13B C Location Area not allowed #12 PLMN_REST_2GTO2G_1 2_C 0x140 Location Area not allowed #12 PLMN_REST_2GTO3G_1 2_C 0x145 Location Area not allowed #12 PLMN_REST_3GTO2G_1 2_C 0x14A Location Area not allowed #12 PLMN_REST_3GTO3G_1 2_C 0x14F Location Area not allowed #12 SUBS_CNT_REST_2G_1 2_C 0x154 Location Area not allowed #12 SUBS_CNT_REST_3G_1 2_C 0x159 Location Area not allowed #12 SUBS_CNT_REST_CAM_ 12_C 0x179 Location Area not allowed #12 ROAM_NT_ALLOW_IN_L A_C 0x0A4 Roaming not allowed in this location area #13 HLR_ACC_REST_2G_13_ 0x137 C Roaming not allowed in this location area #13 HLR_ACC_REST_3G_13_ 0x13C C Roaming not allowed in this location area #13 PLMN_REST_2GTO2G_1 3_C 0x141 Roaming not allowed in this location area #13 PLMN_REST_2GTO3G_1 3_C 0x146 Roaming not allowed in this location area #13 PLMN_REST_3GTO2G_1 3_C 0x14B Roaming not allowed in this location area #13 PLMN_REST_3GTO3G_1 3_C 0x150 Roaming not allowed in this location area #13 SUBS_CNT_REST_2G_1 3_C 0x155 Roaming not allowed in this location area #13 SUBS_CNT_REST_3G_1 3_C 0x15A Roaming not allowed in this location area #13 SUBS_CNT_REST_CAM_ 13_C 0x17A Roaming not allowed in this location area #13 Internal Error cause CS_PS_COORDINATION _C Table 852 DN05148836 Issue 2-2 Appendix Internal cause to interface cause mapping from MM & SM processes MS initiated attach (GPRS or combined) rejected by network (Cont. ) Id:0900d805809551ce DN05148836 Issue 2-2 .Appendix Internal cause to interface cause mapping from MM & SM processes Internal cause value GMM cause (External cause to MS) External Cause Value GPRS services not allowed in this PLMN #14 HLR_ACC_REST_2G_14_ 0x138 C GPRS services not allowed in this PLMN #14 HLR_ACC_REST_3G_14_ 0x13D C GPRS services not allowed in this PLMN #14 PLMN_REST_2GTO2G_1 4_C 0x142 GPRS services not allowed in this PLMN #14 PLMN_REST_2GTO3G_1 4_C 0x147 GPRS services not allowed in this PLMN #14 PLMN_REST_3GTO2G_1 4_C 0x14C GPRS services not allowed in this PLMN #14 PLMN_REST_3GTO3G_1 4_C 0x151 GPRS services not allowed in this PLMN #14 SUBS_CNT_REST_2G_1 4_C 0x156 GPRS services not allowed in this PLMN #14 SUBS_CNT_REST_3G_1 4_C 0x15B GPRS services not allowed in this PLMN #14 SUBS_CNT_REST_CAM_ 14_C 0x17B GPRS services not allowed in this PLMN #14 CONTR_ROAMING_REJ_ C 0x5A No suitable cells in location area #15 HLR_ACC_REST_2G_15_ 0x139 C No suitable cells in location area #15 HLR_ACC_REST_3G_15_ 0x13E C No suitable cells in location area #15 PLMN_REST_2GTO2G_1 5_C 0x143 No suitable cells in location area #15 PLMN_REST_2GTO3G_1 5_C 0x148 No suitable cells in location area #15 PLMN_REST_3GTO2G_1 5_C 0x14D No suitable cells in location area #15 PLMN_REST_3GTO3G_1 5_C 0x152 No suitable cells in location area #15 SUBS_CNT_REST_2G_1 5_C 0x157 No suitable cells in location area #15 SUBS_CNT_REST_3G_1 5_C 0x15C No suitable cells in location area #15 SUBS_CNT_REST_CAM_ 15_C 0x17C No suitable cells in location area #15 NO_RES_AVAILABLE_C 0x0C Congestion #22 OVERLOAD_C 0x59 Congestion #22 Internal Error cause ROAMING_NOT_ALLOW ED_C Table 852 504 Traffica Reference Guide for SGSN Direct Interface 0x7E MS initiated attach (GPRS or combined) rejected by network (Cont. Traffica Reference Guide for SGSN Direct Interface Appendix Internal cause to interface cause mapping from MM & SM processes Internal Error cause Internal cause value GMM cause (External cause to MS) External Cause Value CONGESTION_C 0x3D Congestion #22 MAX_SGSN_2G_SUBS_R 0xD9 E_C Congestion #22 MAX_SGSN_3G_SUBS_R 0x12C E_C Congestion #22 MAX_SGSN_UMA_SUB_ RE_C 0x12D Congestion #22 MAX_SGSN_SUBS_RE_ C 0x12E Congestion #22 MAND_IE_INC_C 0x0E Invalid mandatory infor- #96 mation INV_MAND_INF_C 0x23 Invalid mandatory infor- #96 mation MAND_IE_MISSING_C 0x0F Invalid mandatory infor- #96 mation IE_NOT_EX_OR_IMP_C 0x46 Information element non-existent or not implemented #99 COND_IE_ERR_C 0x26 Conditional IE error #100 All other causes Table 852 MS initiated attach (GPRS or combined) rejected by network (Cont.) Internal Error cause Internal cause value IMSI_U_IN_H LR_C 0x29 GMM cause(External cause to MS) External Cause Value IMSI unknown in HLR #2 ILLEGAL_MS_ 0x93 C Illegal MS #3 IMSI_UNKNW N_IN_VLR_C IMSI unknown in VLR #4 ILLEGAL_ME_ 0x0A1 C Illegal ME #6 PLMN_NOT_A 0x0A2 LLOW_C PLMN not allowed #11 LOC_AREA_N 0x0A3 OT_ALLOW_ C Location Area not allowed #12 Table 853 DN05148836 Issue 2-2 Protocol error, unspeci- #111 fied 0x0A7 MS initiated combined attach accepted GPRS services only (CS-side fails) Id:0900d805809551ce 505 Appendix Internal cause to interface cause mapping from MM & SM processes Internal Error cause GMM cause(External cause to MS) External Cause Value ROAM_NT_AL 0x0A4 LOW_IN_LA_ C Roaming not allowed in this location area #13 NO_SUIT_CE LL_IN_LA_C 0x0B1 No suitable cells in location area #15 VLR_UNREA CHABLE_C 0x81 MSC temporarily not reachable #16 NO_RSP_FR OM_VLR_C 0x7A MSC temporarily not reachable #16 NETWORK_F AILURE_C 0x0A8 Network failure #17 UNDEFINED_ C 0xFFFFFFFF Network failure #17 VLR_CONGE STION_C 0x0AB Congestion #22 SEMANTIC_I NC_MSG_C 0x0A9 Semantically incorrect message #95 MANDAT_INF O_EL_ERR_C 0x0A5 Invalid mandatory information #96 MSG_NOT_E X_OR_IMPL_ C 0x0AA Message type non-existent or not implemented #97 INFO_EL_NO _EX_OR_I_C 0x0A6 Information element nonexistent or not implemented #99 COND_IE_ER R_C 0x26 Conditional IE error #100 Protocol error, unspecified #111 All other causes Table 853 506 Internal cause value Traffica Reference Guide for SGSN Direct Interface MS initiated combined attach accepted GPRS services only (CS-side fails) Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Internal Error cause Internal cause value GMM cause(External cause to MS) AUTH_FAILU RE_C 0x14 Illegal MS #3 UNKNOWN_E QUIP_C 0x2E Illegal ME #6 IMEI_CHK_FA ILED_C 0x51 Illegal ME #6 IMEI_FAIL_CS 0xDB _ALLOW_C GPRS services not allowed #7 NO_GPRS_S UBSCR_C 0x30 GPRS services not allowed #7 IMSI_U_IN_H LR_C 0x29 GPRS services and non-GPRS services not allowed #8 IMSI_NOT_KN 0x08 OWN_C MS identity cannot be derived by the network #9 INV_RAI_INF O_C 0x28 MS identity cannot be derived by the network #9 IMSI_U_IN_A UC_C 0x2A MS identity cannot be derived by the network #9 MS_GPRS_D ETACHED_C 0x09 Implicitly detached #10 UNKNOWN_M 0x3A S_C Implicitly detached #10 DNS_FAILUR E_C Implicitly detached #10 HLR_ACC_RE 0x135 ST_2G_11_C PLMN not allowed #11 HLR_ACC_RE 0x13A ST_3G_11_C PLMN not allowed #11 0x13F PLMN not allowed #11 PLMN_REST_ 2GTO2G_11_ C Table 854 DN05148836 Issue 2-2 Appendix Internal cause to interface cause mapping from MM & SM processes 0x170 External Cause Value MS initiated Routing area update rejected by network Id:0900d805809551ce 507 Appendix Internal cause to interface cause mapping from MM & SM processes GMM cause(External cause to MS) Internal Error cause Internal cause value PLMN_REST_ 2GTO3G_11_ C 0x144 PLMN not allowed #11 PLMN_REST_ 3GTO2G_11_ C 0x149 PLMN not allowed #11 PLMN_REST_ 3GTO3G_11_ C 0x14E PLMN not allowed #11 SUBS_CNT_R 0x153 EST_2G_11_ C PLMN not allowed #11 SUBS_CNT_R 0x158 EST_3G_11_ C PLMN not allowed #11 0x0B7 Location Area not allowed #12 HLR_ACC_RE 0x136 ST_2G_12_C Location Area not allowed #12 HLR_ACC_RE 0x13B ST_3G_12_C Location Area not allowed #12 PLMN_REST_ 2GTO2G_12_ C 0x140 Location Area not allowed #12 PLMN_REST_ 2GTO3G_12_ C 0x145 Location Area not allowed #12 PLMN_REST_ 3GTO2G_12_ C 0x14A Location Area not allowed #12 PLMN_REST_ 3GTO3G_12_ C 0x14F Location Area not allowed #12 SUBS_CNT_R 0x154 EST_2G_12_ C Location Area not allowed #12 SUBS_CNT_R 0x159 EST_3G_12_ C Location Area not allowed #12 ROAM_NT_AL 0x0A4 LOW_IN_LA_ C Roaming not allowed in this location area #13 CONTR_ROA M_RL97_REJ _C Table 854 508 Traffica Reference Guide for SGSN Direct Interface External Cause Value MS initiated Routing area update rejected by network (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface Internal Error cause GMM cause(External cause to MS) External Cause Value HLR_ACC_RE 0x137 ST_2G_13_C Roaming not allowed in this location area #13 HLR_ACC_RE 0x13C ST_3G_13_C Roaming not allowed in this location area #13 PLMN_REST_ 2GTO2G_13_ C 0x141 Roaming not allowed in this location area #13 PLMN_REST_ 2GTO3G_13_ C 0x146 Roaming not allowed in this location area #13 PLMN_REST_ 3GTO2G_13_ C 0x14B Roaming not allowed in this location area #13 PLMN_REST_ 3GTO3G_13_ C 0x150 Roaming not allowed in this location area #13 SUBS_CNT_R 0x155 EST_2G_13_ C Roaming not allowed in this location area #13 SUBS_CNT_R 0x15A EST_3G_13_ C Roaming not allowed in this location area #13 GPRS services not allowed in this PLMN #14 HLR_ACC_RE 0x138 ST_2G_14_C GPRS services not allowed in this PLMN #14 HLR_ACC_RE 0x13D ST_3G_14_C GPRS services not allowed in this PLMN #14 PLMN_REST_ 2GTO2G_14_ C 0x142 GPRS services not allowed in this PLMN #14 PLMN_REST_ 2GTO3G_14_ C 0x147 GPRS services not allowed in this PLMN #14 ROAMING_N OT_ALLOWE D_C Table 854 DN05148836 Issue 2-2 Internal cause value Appendix Internal cause to interface cause mapping from MM & SM processes 0x7E MS initiated Routing area update rejected by network (Cont.) Id:0900d805809551ce 509 Appendix Internal cause to interface cause mapping from MM & SM processes GMM cause(External cause to MS) Internal Error cause Internal cause value PLMN_REST_ 3GTO2G_14_ C 0x14C GPRS services not allowed in this PLMN #14 PLMN_REST_ 3GTO3G_14_ C 0x151 GPRS services not allowed in this PLMN #14 SUBS_CNT_R 0x156 EST_2G_14_ C GPRS services not allowed in this PLMN #14 SUBS_CNT_R 0x15B EST_3G_14_ C GPRS services not allowed in this PLMN #14 CONTR_ROA MING_REJ_C No suitable cells in location area #15 HLR_ACC_RE 0x139 ST_2G_15_C No suitable cells in location area #15 HLR_ACC_RE 0x13E ST_3G_15_C No suitable cells in location area #15 PLMN_REST_ 2GTO2G_15_ C 0x143 No suitable cells in location area #15 PLMN_REST_ 2GTO3G_15_ C 0x148 No suitable cells in location area #15 PLMN_REST_ 3GTO2G_15_ C 0x14D No suitable cells in location area #15 PLMN_REST_ 3GTO3G_15_ C 0x152 No suitable cells in location area #15 SUBS_CNT_R 0x157 EST_2G_15_ C No suitable cells in location area #15 SUBS_CNT_R 0x15C EST_3G_15_ C No suitable cells in location area #15 VLR_UNREA CHABLE_C MSC temporarily not reachable #16 Table 854 510 Traffica Reference Guide for SGSN Direct Interface 0x5A 0x81 External Cause Value MS initiated Routing area update rejected by network (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface GMM cause(External cause to MS) Internal Error cause Internal cause value NO_RSP_FR OM_VLR_C 0x7A MSC temporarily not reachable #16 OVERLOAD_ C 0x59 Congestion #22 CONGESTIO N_C 0x3D Congestion #22 NO_RES_AVA 0x0C ILABLE_C Congestion #22 MAX_SGSN_2 0xD9 G_SUBS_RE_ C Congestion #22 MAX_SGSN_3 0x12C G_SUBS_RE_ C Congestion #22 MAX_SGSN_ UMA_SUB_R E_C 0x12D Congestion #22 MAX_SGSN_ SUBS_RE_C 0x12E Congestion #22 INCORRECT_ MSG_C 0x22 Semantically incorrect message #95 INV_MAND_I NF_C 0x23 Invalid mandatory information #96 MAND_IE_IN C_C 0x0E Invalid mandatory information #96 MAND_IE_MI SSING_C 0x0F Invalid mandatory information #96 IE_NOT_EX_ OR_IMP_C 0x46 Information element nonexistent or not implemented #99 COND_IE_ER R_C 0x26 Conditional IE error #100 Protocol error, unspecified #111 All other causes Table 854 DN05148836 Issue 2-2 Appendix Internal cause to interface cause mapping from MM & SM processes External Cause Value MS initiated Routing area update rejected by network (Cont.) Id:0900d805809551ce 511 Appendix Internal cause to interface cause mapping from MM & SM processes Internal Error cause Internal cause value IMSI_U_IN_H LR_C 0x29 GMM cause(External cause to MS) External Cause Value IMSI unknown in HLR #2 ILLEGAL_MS_ 0x93 C Illegal MS #3 IMSI_UNKNW N_IN_VLR_C IMSI unknown in VLR #4 ILLEGAL_ME_ 0x0A1 C Illegal ME #6 PLMN_NOT_A 0x0A2 LLOW_C PLMN not allowed #11 LOC_AREA_N 0x0A3 OT_ALLOW_ C Location Area not allowed #12 ROAM_NT_AL 0x0A4 LOW_IN_LA_ C Roaming not allowed in this location area #13 NO_SUIT_CE LL_IN_LA_C 0x0B1 No suitable cells in location area #15 VLR_UNREA CHABLE_C 0x81 MSC temporarily not reachable #16 NO_RSP_FR OM_VLR_C 0x7A MSC temporarily not reachable #16 NETWORK_F AILURE_C 0x0A8 Network failure #17 UNDEFINED_ C 0xFFFFFFFF Network failure #17 VLR_CONGE STION_C 0x0AB Congestion #22 SEMANTIC_I NC_MSG_C 0x0A9 Semantically incorrect message #95 MANDAT_INF O_EL_ERR_C 0x0A5 Invalid mandatory information #96 MSG_NOT_E X_OR_IMPL_ C 0x0AA Message type non-existent or not implemented #97 Table 855 512 Traffica Reference Guide for SGSN Direct Interface 0x0A7 MS initiated combined RAU accepted for GPRS services only (CS-side fails). Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface GMM cause(External cause to MS) Internal Error cause Internal cause value INFO_EL_NO _EX_OR_I_C 0x0A6 Information element nonexistent or not implemented #99 COND_IE_ER R_C 0x26 Conditional IE error #100 Protocol error, unspecified #111 All other causes Table 855 External Cause Value MS initiated combined RAU accepted for GPRS services only (CS-side fails). (Cont.) GMM cause(External cause to MS) Internal Error cause Internal cause value NO_SGSN_R ESOURCES_ C 0x6B Insufficient resources #26 OVERLOAD_ C 0x59 Insufficient resources #26 NO_RES_AVA 0x0C ILABLE_C Insufficient resources #26 DYN_IPS_OC CUPIED_C 0x17 Insufficient resources #26 NO_MEM_AV AILABLE_C 0x18 Insufficient resources #26 MAX_SGSN_2 0x12F G_PDP_RE_C Insufficient resources #26 MAX_SGSN_3 0x130 G_PDP_RE_C Insufficient resources #26 MAX_SGSN_ UMA_PDP_R E_C 0x131 Insufficient resources #26 MAX_SGSN_ PDP_RE_C 0x132 Insufficient resources #26 UNKNOWN_D NS_C 0x5C Unknown or missing access point name #27 Unknown PDP address or PDP type #28 UNK_PDP_AD 0x0B6 D_OR_TYPE_ C Table 856 DN05148836 Issue 2-2 Appendix Internal cause to interface cause mapping from MM & SM processes External Cause Value MS initiated PDP context activation rejected by network Id:0900d805809551ce 513 Appendix Internal cause to interface cause mapping from MM & SM processes GMM cause(External cause to MS) Internal Error cause Internal cause value UNKNOWN_P DP_CTXT_C 0x5B Unknown PDP address or PDP type #28 NONEXISTEN T_C 0x06 Unknown PDP address or PDP type #28 USR_AUTH_F AIL_C 0x15 User authentication failed #29 AUTH_FAILU RE_C 0x14 User authentication failed #29 IMEI_CHK_FA ILED_C 0x51 User authentication failed #29 APN_ACCES S_DENIED_C 0x173 User authentication failed #29 SERV_NOT_S 0x0D UPP_C Service option not supported #32 NO_PDP_CO NTEXT_C 0x68 Requested service option not subscribed #33 UNKNOWN_A PN_C 0x1E Requested service option not subscribed #33 NO_SUBSCRI PTION_C 0x67 Requested service option not subscribed #33 NSAPI_IN_US E_C 0x66 NSAPI already used #35 OP_NOT_ALL OWED_C 0x61 NSAPI already used #35 SEM_ERR_IN _TFT_C 0x1A Semantic error in TFT operation #41 SYN_ERR_IN _TFT_C 0x1B Syntactical error in TFT operation #42 NO_LINKED_ TI_C 0x70 Unknown PDP context #43 CTXT_NOT_F OUND_C 0x16 Unknown PDP context #43 SEM_ERR_IN _PFI_C 0x1C Semantic errors in packet filters #44 Table 856 514 Traffica Reference Guide for SGSN Direct Interface External Cause Value MS initiated PDP context activation rejected by network (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 Traffica Reference Guide for SGSN Direct Interface GMM cause(External cause to MS) Internal Error cause Internal cause value SYN_ERR_IN _PFI_C 0x1D Syntactical errors in packet filters #45 PDP_WITHOU 0x74 T_TFT_C PDP context without TFT already activated #46 INCORRECT_ MSG_C 0x22 Semantically incorrect message #95 INV_MAND_I NF_C 0x23 Invalid mandatory information #96 INV_MSG_FR M_C 0x07 Invalid mandatory information #96 MAND_IE_IN C_C 0x0E Invalid mandatory information #96 MAND_IE_MI SSING_C 0x0F Invalid mandatory information #96 NONEX_MSG _TYPE_C 0x24 Message type non-existent or not implemented #97 MSG_INC_W_ 0x27 PROT_ST_C Message not compatible with protocol state #98 MSG_T_INC_ 0x25 W_PROT_ST_ C Message not compatible with protocol state #98 IE_NOT_EX_ OR_IMP_C 0x46 Information element nonexistent or not implemented #99 COND_IE_ER R_C 0x26 Conditional IE error #100 OPT_IE_INC_ C 0x10 Protocol error, unspecified #111 PROT_ERRO R_UNSPEC_ C 0x49 Protocol error, unspecified #111 Table 856 DN05148836 Issue 2-2 Appendix Internal cause to interface cause mapping from MM & SM processes External Cause Value MS initiated PDP context activation rejected by network (Cont.) Id:0900d805809551ce 515 unspecified #31 MS initiated PDP context activation rejected by network (Cont.Appendix Internal cause to interface cause mapping from MM & SM processes Internal Error cause Internal cause value PROTOCOL_ C 0x54 All other causes Table 856 GMM cause(External cause to MS) External Cause Value Protocol error. unspecified #111 Activation rejected.) GMM cause(External cause to MS) Internal Error cause Internal cause value NO_SGSN_R ESOURCES_ C 0x6B Insufficient resources #26 OVERLOAD_ C 0x59 Insufficient resources #26 NO_RES_AVA 0x0C ILABLE_C Insufficient resources #26 DYN_IPS_OC CUPIED_C 0x17 Insufficient resources #26 NO_MEM_AV AILABLE_C 0x18 Insufficient resources #26 UNKNOWN_A PN_C 0x1E Unknown or missing access point name #27 UNKNOWN_P DP_CTXT_C 0x5B Unknown PDP address or PDP type #28 NONEXISTEN T_C 0x06 Unknown PDP address or PDP type #28 USR_AUTH_F AIL_C 0x15 User authentication failed #29 AUTH_FAILU RE_C 0x14 User authentication failed #29 IMEI_CHK_FA ILED_C 0x51 User authentication failed #29 SERV_NOT_S 0x0D UPP_C Service option not supported #32 Table 857 516 Traffica Reference Guide for SGSN Direct Interface External Cause Value MS initiated PDP context modification rejected by network Id:0900d805809551ce DN05148836 Issue 2-2 . ) Id:0900d805809551ce 517 .Traffica Reference Guide for SGSN Direct Interface GMM cause(External cause to MS) Internal Error cause Internal cause value NO_PDP_CO NTEXT_C 0x68 Requested service option not subscribed #33 NO_SUBSCRI PTION_C 0x67 Requested service option not subscribed #33 NSAPI_IN_US E_C 0x66 NSAPI already used #35 SEM_ERR_IN _TFT_C 0x1A Semantic error in TFT operation #41 SYN_ERR_IN _TFT_C 0x1B Syntactical error in TFT operation #42 NO_LINKED_ TI_C 0x70 Unknown PDP context #43 CTXT_NOT_F OUND_C 0x16 Unknown PDP context #43 SEM_ERR_IN _PFI_C 0x1C Semantic errors in packet filters #44 SYN_ERR_IN _PFI_C 0x1D Syntactical errors in packet filters #45 PDP_WITHOU 0x74 T_TFT_C PDP context without TFT already activated #46 INCORRECT_ MSG_C 0x22 Semantically incorrect message #95 INV_MAND_I NF_C 0x23 Invalid mandatory information #96 INV_MSG_FR M_C 0x07 Invalid mandatory information #96 MAND_IE_IN C_C 0x0E Invalid mandatory information #96 MAND_IE_MI SSING_C 0x0F Invalid mandatory information #96 Table 857 DN05148836 Issue 2-2 Appendix Internal cause to interface cause mapping from MM & SM processes External Cause Value MS initiated PDP context modification rejected by network (Cont. unspecified #111 All other causes Table 857 MS initiated PDP context modification rejected by network (Cont.) GMM cause(External cause to MS) Internal Error cause Internal cause value NO_SGSN_R ESOURCES_ C 0x6B Insufficient resources #26 OVERLOAD_ C 0x59 Insufficient resources #26 NO_RES_AVA 0x0C ILABLE_C Insufficient resources #26 DYN_IPS_OC CUPIED_C 0x17 Insufficient resources #26 NO_MEM_AV AILABLE_C 0x18 Insufficient resources #26 USR_AUTH_F AIL_C 0x15 User authentication failed #29 AUTH_FAILU RE_C 0x14 User authentication failed #29 NO_RSP_FR OM_SCP_C 0x58 SM network failure #38 Table 858 518 Traffica Reference Guide for SGSN Direct Interface External Cause Value Network requested PDP context deactivation Id:0900d805809551ce DN05148836 Issue 2-2 .Appendix Internal cause to interface cause mapping from MM & SM processes Internal Error cause Internal cause value NONEX_MSG _TYPE_C 0x24 GMM cause(External cause to MS) External Cause Value Message type non-existent or not implemented #97 MSG_T_INC_ 0x25 W_PROT_ST_ C Message not compatible with protocol state #98 MSG_INC_W_ 0x27 PROT_ST_C Message not compatible with protocol state #98 IE_NOT_EX_ OR_IMP_C 0x46 Information element nonexistent or not implemented #99 COND_IE_ER R_C 0x26 Conditional IE error #100 Protocol error. unspecified #111 Regular PDP context deactivation #36 All other causes Table 858 External Cause Value Network requested PDP context deactivation (Cont.) Internal Error cause Internal cause value GMM cause(External cause to MS) AUTH_FAILU RE_C 0x14 Illegal MS #3 UNKNOWN_E QUIP_C 0x2E Illegal ME #6 IMEI_CHK_FA ILED_C 0x51 Illegal ME #6 NO_GPRS_S UBSCR_C 0x30 GPRS services not allowed #7 IMSI_U_IN_H LR_C 0x29 GPRS services and non-GPRS services not allowed #8 Table 859 DN05148836 Issue 2-2 Appendix Internal cause to interface cause mapping from MM & SM processes External Cause Value MS initiated service request rejected by the network Id:0900d805809551ce 519 .Traffica Reference Guide for SGSN Direct Interface GMM cause(External cause to MS) Internal Error cause Internal cause value SYSTEM_FAI LURE_C 0x11 SM network failure #38 NO_RSP_FR OM_GSN_C 0x4F SM network failure #38 UNSUCC_OP _C 0x60 SM network failure #38 OP_NOT_ALL OWED_C 0x61 SM network failure #38 CTXT_NOT_F OUND_C 0x16 Reactivation requested #39 NO_RSP_FR OM_GGSN_C 0x5F Reactivation requested #39 GGSN_REST ARTED_C 0xD8 Reactivation requested #39 PROTOCOL_ C 0x54 Protocol error. Appendix Internal cause to interface cause mapping from MM & SM processes Internal Error cause GMM cause(External cause to MS) External Cause Value IMSI_NOT_KN 0x08 OWN_C MS identity cannot be derived by the network #9 IMSI_U_IN_A UC_C 0x2A MS identity cannot be derived by the network #9 MS_GPRS_D ETACHED_C 0x09 Implicitly detached #10 UNKNOWN_M 0x3A S_C Implicitly detached #10 CONTR_ROA M_RL97_REJ _C 0x0B7 Location Area not allowed #12 ROAMING_N OT_ALLOWE D_C 0x7E GPRS services not allowed in this PLMN #14 CONTR_ROA MING_REJ_C 0x5A No suitable cells in location area #15 OVERLOAD_ C 0x59 Congestion #22 CONGESTIO N_C 0x3D Congestion #22 NO_RES_AVA 0x0C ILABLE_C Congestion #22 NO_PDP_CO NTEXT_C 0x68 No PDP context activated #40 INV_MAND_I NF_C 0x23 Invalid mandatory information #96 MAND_IE_IN C_C 0x0E Invalid mandatory information #96 MAND_IE_MI SSING_C 0x0F Invalid mandatory information #96 IE_NOT_EX_ OR_IMP_C 0x46 Information element is non-existent or not implemented #99 Table 859 520 Internal cause value Traffica Reference Guide for SGSN Direct Interface MS initiated service request rejected by the network (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 . ) Internal cause value FAILED_IMEI_ 0x2B CHK_C GMM cause(External cause to MS) External Cause Value Illegal ME #6 IMSI unknown in HLR #2 GPRS services not allowed #7 Cause will not be sent to MS -- Cause will not be sent to MS -- Cause will not be sent to MS -- Cause will not be sent to MS -- Cause will not be sent to MS -- ----- Cause value has no meaning HLR_INITIATE 0x20 D_C IMSI_U_IN_H LR_C 0x29 HLR_INITIATE 0x20 D_C NO_GPRS_S UBSCR_C 0x30 HLR_INITIATE 0x20 D_C DN05148836 Issue 2-2 GMM cause(External cause to MS) Protocol error.Traffica Reference Guide for SGSN Direct Interface Internal Error cause Internal cause value All other causes Table 859 External Cause Value #111 MS initiated service request rejected by the network (Cont. unspecified Internal Error cause SUCCESS_C 0x00 NW_INITIATE D_C 0x01 SUCCESS_C 0x00 NW_INITIATE D_C 0x01 UNDEFINED_ C 0xFFFFFFFF UNDEFINED_ C 0xFF SUCCESS_C 0x00 UNDEFINED_ C 0xFF UNDEFINED_ C 0xFFFFFFFF Table 860 Appendix Internal cause to interface cause mapping from MM & SM processes NW initiated detach request Id:0900d805809551ce 521 . Appendix Internal cause to interface cause mapping from MM & SM processes Internal Error cause Internal cause value Init cause value has no meaning ---- MS_GPRS_D ETACHED_C 0x09 Init cause value has no meaning ---- Traffica Reference Guide for SGSN Direct Interface GMM cause(External cause to MS) External Cause Value Implicitly detached #10 Implicitly detached #10 MS identity cannot be derived by the network #9 MS identity cannot be derived by the network #9 MS identity cannot be derived by the network #9 GPRS services not allowed #7 GPRS services not allowed #7 GPRS services and non-GPRS services not allowed #8 UNKNOWN_M 0x3A S_C ---- Init cause value has no meaning IMSI_NOT_KN 0x08 OWN_C Init cause value has no meaning ---- IMSI_U_IN_A UC_C 0x2A Init cause value has no meaning ---- INV_RAI_INF O_C 0x28 Init cause value has no meaning ---- IMEI_FAIL_CS 0xDB _ALLOW_C Init cause value has no meaning ---- NO_GPRS_S UBSCR_C 0x30 Init cause value has no meaning ---- IMSI_U_IN_H LR_C 0x29 Table 860 522 NW initiated detach request (Cont.) Id:0900d805809551ce DN05148836 Issue 2-2 . ) Id:0900d805809551ce 523 .Traffica Reference Guide for SGSN Direct Interface Internal Error cause Internal cause value GMM cause(External cause to MS) Init cause value has no meaning ---- Illegal ME #6 UNKNOWN_E QUIP_C 0x2E Init cause value has no meaning ---- Illegal ME #6 IMEI_CHK_FA ILED_C 0x51 Init cause value has no meaning ---- #14 ROAMING_N OT_ALLOWE D_C 0x7E GPRS services not allowed in this PLMN Init cause value has no meaning ---- Illegal MS #3 AUTH_FAILU RE_C 0x14 Init cause value has no meaning ---- MSC temporarily not reachable #16 VLR_UNREA CHABLE_C 0x81 Init cause value has no meaning ---- MSC temporarily not reachable #16 NO_RSP_FR OM_VLR_C 0x7A Congestion #22 Congestion #22 Init cause value has no meaning OVERLOAD_ C CONGESTIO N_C Table 860 External Cause Value 0x59 Init cause value has no meaning DN05148836 Issue 2-2 Appendix Internal cause to interface cause mapping from MM & SM processes 0x3D NW initiated detach request (Cont. Appendix Internal cause to interface cause mapping from MM & SM processes Internal Error cause Internal cause value CONTR_ROA MING_REJ_C External Cause Value #15 0x5A Network failure #17 All other causes regardless of init cause or error cause value NW initiated detach request (Cont. unspecified Protocol error.) Location update fail reason Internal Error cause Internal cause value Unknown subscriber (IMSI unknown) IMSI_U_IN_HLR_C Roaming not allowed ROAMING_NOT_A LLOWED_C System failure Attach reject* RAU reject* 0x29 GPRS services and nonGPRS services not allowed 0x7E ATT# RAU# GPRS services and nonGPRS services not allowed #8 #8 GPRS services not allowed in this PLMN GPRS services not allowed in this PLMN #14 #14 MAP_SYSTEM_FAI 0x2B L_C Protocol error. unspecified #111 #111 Unknown equipment UNKNOWN_EQUIP 0x2E _C Illegal ME Illegal ME #6 #6 GPRS subscription unknown NO_GPRS_SUBSC 0x30 R_C GPRS services not allowed GPRS services not allowed #7 #7 Table 861 524 GMM cause(External cause to MS) No suitable cells in location area Init cause value has no meaning Table 860 Traffica Reference Guide for SGSN Direct Interface 0x2D Cause mapping between Gr interface(MAP protocol/HLR/AuC --> SGSN -> MS) . unspecified Protocol error.Location update procedure *SM cause(External cause to MS) Id:0900d805809551ce DN05148836 Issue 2-2 . unspecified #111 #111 Unexpected data value UNEXP_DATA_VA L_C Protocol error. unspecified Protocol error. unspecified #31 Semantic error in the TFT operation 215 SEM_ERR_IN_TFT _C 0x1A Semantic error in TFT operation #41 Syntactic error in the TFT operation 216 SYN_ERR_IN_TFT _C 0x1B Syntactical error in TFT operation #42 Semantic errors in packet filter(s) 217 SEM_ERR_IN_PFI _C 0x1C Semantic errors in packet filters #44 Table 862 Internal Error cause Cause mapping between GGSN --> SGSN --> MS . unspecified Protocol error.Location update procedure *SM cause(External cause to MS) Internal cause value SM cause(External cause to MS) External Cause Value NO_RES_AVAILAB LE_C 0x0C Insufficient recources #26 211 DYN_IPS_OCCUPI ED_C 0x17 Insufficient recources #26 No memory is available 212 NO_MEM_AVAILA BLE_C 0x18 Insufficient recources #26 Missing or unknown APN 219 UNKNOWN_DNS_ C 0x5C Unknown or missing access point name #27 Unknown PDP address or PDP type 220 UNK_PDP_ADD_O R_TYPE_C 0x0B6 Unknown PDP address or PDP type #28 APN access denied 222 APN_ACCESS_DE NIED_C 0x173 User authentication failed #29 User authentication failed 209 USR_AUTH_FAIL_ C 0x15 User authentication failed #29 System failure 204 SYSTEM_FAILURE 0x11 _C Activation rejected. unspecified #111 #111 Table 861 Create PDP context response cause Appendix Internal cause to interface cause mapping from MM & SM processes Cause mapping between Gr interface(MAP protocol/HLR/AuC --> SGSN -> MS) .Create PDP context response DN05148836 Issue 2-2 Id:0900d805809551ce 525 .Traffica Reference Guide for SGSN Direct Interface Location update fail reason Respon se cause value No resources available 199 All dynamic PDP addresses are occupied Internal cause value Internal Error cause Attach reject* RAU reject* ATT# RAU# Unexpected MAP error value UNEXP_CAUSE_V AL_C 0x2F Protocol error. unspecified #111 #111 Abort received from MAP protocol ABORT_FROM_M AP_C 0x79 Protocol error. unspecified #111 215 SEM_ERR_IN_TFT _C 0x1A Semantic error in TFT operation #41 Syntactic error in the TFT operation 216 SYN_ERR_IN_TFT _C 0x1B Syntactical error in TFT operation #42 Semantic errors in packet filter(s) 217 SEM_ERR_IN_PFI _C 0x1C Semantic errors in packet filters #44 Syntactic errors in packet filters(s) 218 SYN_ERR_IN_PFI_ 0x1D C Syntactical errors in packet filters #45 Mandatory IE incorrect 201 MAND_IE_INC_C 0x0E Invalid mandatory informa. unspecified Invalid message format 193 INV_MSG_FRM_C 0x07 Invalid mandatory informa.Create PDP context response (Cont.Appendix Internal cause to interface cause mapping from MM & SM processes Create PDP context response cause Respon se cause value Syntactic errors in packet filters(s) 218 Table 862 Internal cause value Internal Error cause SYN_ERR_IN_PFI_ 0x1D C Traffica Reference Guide for SGSN Direct Interface SM cause(External cause to MS) External Cause Value Syntactical errors in packet filters #45 Cause mapping between GGSN --> SGSN --> MS .#96 tion All other causes Table 863 526 Protocol error.Update PDP context response Id:0900d805809551ce DN05148836 Issue 2-2 .#96 tion Optional IE incorrect 203 OPT_IE_INC_C 0x10 Protocol error. unspecified #111 #111 Cause mapping between GGSN --> SGSN --> MS .) Update PDP context response cause Respon se cause value Internal Error cause Internal cause value Non-existent 192 NONEXISTENT_C Service not supported 200 SERV_NOT_SUPP _C System failure 204 Semantic error in the TFT operation SM cause(External cause to MS) External Cause Value 0x06 Unknown PDP address or PDP type #28 0x0D Service option not supported #32 SYSTEM_FAILURE 0x11 _C Protocol error.#96 tion Mandatory IE missing 202 MAND_IE_MISSIN G_C 0x0F Invalid mandatory informa. The length of the QoS IE in the CDRs is 9 octets (according to 3GPP TS 24.008 QoS IE definition the length should be 13 octets). Note that in S31 there are 10 octets to present R99 QoS parameters. missequencing of or corruption of SDUs. In the following containers QoS Negotiated is present only if the previous change condition was the QoS change. The encoding of the QoS profile is defined in 3GPP TS 24. Rules for determining R99 attributes from R97/98 attributes are defined in 3GPP TS 23. 10 Relevant only if the QoS is R99. QoS Service Negotiated indicates the applied QoS accepted by the network. the following fields are: Field name Field length Description octet Reliability class 3 bits 2 The reliability parameter indicates the transmission characteristics that are required by an application. The QoS IE is defined to allow backward compatibility to earlier version of Session Management Protocol.008 and 23. 9 octets is enough to present either R97/98 QoS or R99 QoS parameters by using union representation. QoS Service Requested IE contains the QoS wanted by MS at PDP context activation. there is a name that describes the logical field. 1.6. They are named otherwise the same but instead of octet number in the end of the field name. The reliability class defines the probability of loss of. see 3GPP TS 24. 2 and 3. duplication of. Table 864 QoS_Reguested/Negotiated_Octet fields If the QoS profile flag value is 0x0 (Release 97/98).008 (Chapter 10.5. In CCMA Vector nodes and Traffic News you can use logical fields derived from these octets.107 Table 865 Release 97/98 fields DN05148836 Issue 2-2 Id:0900d805809551ce 527 . Possible values: 0 (Not in use). Quality of Service). but they are not necessarily present in every container of the S-CDR.Traffica Reference Guide for SGSN Direct Interface Appendix SGSN_Qos_Requested/Negotiated_Octet B Appendix SGSN_Qos_Requested/Negotiated_Octet The purpose of Quality of service information elements is to specify the QoS parameters for a PDP context. Field name Field length Description octet QoS profile flag byte 0x0 = Release 97/98 1 0x1 = Release 99 Allocation/Retention Priority byte Specifies the relative importance compared to other UMTS bearers for allocation and retention of the UMTS bearer. Both of the QoS IEs have the same data format. First container includes the following optional fields: QoS (Quality of Service) Requested and QoS Negotiated.5.107. The delay parameter defines the end-to-end transfer delay incurred in the transmission of SDUs through the GPRS network(s). 4 see 3GPP TS 24.Appendix SGSN_Qos_Requested/Negotiated_Octet Traffica Reference Guide for SGSN Direct Interface Field name Field length Description octet Delay class 3 bits 2 The delay parameter thus defines the maximum values for the mean delay and 95-percentile delay to be incurred by the transfer of data through the GPRS network(s).) If the QoS profile flag value is 0x1 (Release 99). 2 see 3GPP TS 24.008 and 23.008 and 23. 3 see 3GPP TS 24.107 Delivery order 2 bits Indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not.107 3 Peak throughput 4 bits The throughput parameter indicates the user data throughput requested by the user.008 and 23. see 3GPP TS 24. see 3GPP TS 24.107 3 Spare bit 1 byte see 3GPP TS 24.008 and 23.008 and 23.107 4 Release 97/98 fields (Cont.107 Spare bits Table 865 3 bits see 3GPP TS 24.008 and 23.008 and 23. 3 see 3GPP TS 24. divided by the duration of the period.107 Mean throughput 5 bits The throughput parameter indicates the user data throughput requested by the user.107 Maximum SDU size 8 bits The maximum SDU size allowed.008 and 23.107 Spare bits 2 bits see 3GPP TS 24.008 and 23. 4 see 3GPP TS 24.008 and 23. the following fields are: Field name Field length Description octet Delivery of erroneous SDU 3 bits 2 Indicates whether SDUs detected as erroneous shall be delivered or discarded.107 Traffic class 3 bits Type of application for which the UMTS bearer service is optimised 2 see 3GPP TS 24.107 Table 866 528 Release 99 fields Id:0900d805809551ce DN05148836 Issue 2-2 .008 and 23.107 2 Precedence class 3 bits see 3GPP TS 24.107 Maximum bit rate for UL 8 bits Maximum number of bits delivered by UMTS and to UMTS at a SAP within a period of time.008 and 23. divided by the duration of the period.107 Guaranteed bit rate for DL 8 bits Guaranteed number of bits delivered by UMTS at a SAP within a period of time.107 Residual BER 4 bits 6 Indicates the undetected bit error ratio in the delivered SDUs. divided by the duration of the period.107 Traffic Handling priority 2 bits Specifies the relative importance for handling of all SDUs belonging to the UMTS bearer compared to the SDUs of other bearers.107 Transfer delay 6 bits Indicates maximum delay for 95th percentile of the distribution of delay for all delivered SDUs during the lifetime of a bearer service. If no error detection is requested.107 SDU error ratio 4 bits Indicates the fraction of SDUs lost or detected as erroneous.) Id:0900d805809551ce 529 . 8 see 3GPP TS 24.008 and 23. see 3GPP TS 24.Traffica Reference Guide for SGSN Direct Interface Appendix SGSN_Qos_Requested/Negotiated_Octet Field name Field length Description octet Maximum bit rate for DL 8 bits 5 Maximum number of bits delivered by UMTS and to UMTS at a SAP within a period of time. divided by the duration of the period.008 and 23. Residual bit error ratio indicates the bit error ratio in the delivered SDUs. 7 see 3GPP TS 24.107 Guaranteed bit rate for UL 8 bits Guaranteed number of bits delivered by UMTS at a SAP within a period of time. 7 see 3GPP TS 24. see 3GPP TS 24.008 and 23. SDU error ratio is defined only for conforming traffic.008 and 23.107 Table 866 DN05148836 Issue 2-2 Release 99 fields (Cont.008 and 23. 6 see 3GPP TS 24. 9 see 3GPP TS 24. where delay for an SDU is defined as the time from a request to transfer an SDU at one SAP to its delivery at the other SAP.008 and 23.008 and 23. 15). 0x09 ms_gprs_detached GTPPRB: GTPPRB informs old SGSN about collide of attach or detach. 0x0C no_res_available GTPPRB: GTPPRBs TID table or sequence number table (for RAUs) has run out of room.15).15).15). GS1PRB: Service not supported by the mobile station. 0x10 opt_ie_inc GTPPRB: GTPPRB tells that GGSN could not decode optional IE. 0x03 another_down GTPPRB: Cause code returned by Charging Gateway (see ETSI TS 12. GS1PRB: Mobile station has done gprs detach. 0x02 receive_full GTPPRB: Cause code returned by Charging Gateway (see ETSI TS 12. 0x0B version_not_supp GTPPRB: Cause code returned by Charging Gateway (see ETSI TS 12. 0x12 roam_restr GTPPRB: GTPPRB informs old SGSN that MS is not allowed to roam. 0x0A ms_not_gprs_rsp GTPPRB: GTPPRB informs old SGSN about MS lost or is not GPRS quality. 0x08 imsi_not_known GTPPRB tells old SGSN IMSI cannot be found. After that there are resources for 5000 simultaneous inter-unit RAU's.Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Traffica Reference Guide for SGSN Direct Interface C Appendix Possible values Sgsn_Sms_Rtt_Cause_Cause Sgsn_Rtt_Cause_Cause for and Value Error code Explanation 0xFFFFF FFF Undefined Undefined 0x00 Success Success 0x01 send_full GTPPRB: Cause code returned by Charging Gateway (see ETSI TS 12. 0x11 system_failure GTPPRB: GTPPRB sets this when there is no appropriate error cause. Table 867 530 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause Id:0900d805809551ce DN05148836 Issue 2-2 . 0x04 this_down GTPPRB: Cause code returned by Charging Gateway (see ETSI TS 12.060).This cause can also come directly from GGSN (see 3GPP TS 29.15). GCSPRB has noted that IMSI is changed during MM/SM procedure. 0x05 req_acc GTPPRB: GTPPRB notifies GGSN about successful operation. 0x07 inv_msg_frm GTPPRB: GTPPRB received message with invalid format. GTP had resources for 500 simultaneous inter-unit rau's before Change Notes SG3_0152 and SG31_0199. 0x0F mand_ie_missing GTPPRB: GTPPRB tells that GGSN could not find mandatory IE. 0x0E mand_ie_inc GTPPRB: GTPPRB tells that GGSN could not decode mandatory IE. 0x06 Nonexistent GTPPRB: GTPPRB tells GGSN delete operation failed due to nonexistent context. Ongoing procedure is rejected. 0x0D serv_not_supp GTPPRB: MS97/98 is trying to create secondary context. 060). 0x14 auth_failure GTPPRB: Cause code returned by GGSN (see 3GPP TS 29. Ongoing procedure is interrupted. Table 867 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. 0x1F req_rel_poss_dupl GTPPRB: Cause code returned by Charging Gateway (see ETSI TS 12.Traffica Reference Guide for SGSN Direct Interface Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Value Error code Explanation 0x13 ptmsi_sign_mism GTPPRB: GTPPRB informs old SGSN about PTMSI signature mismatch.060). GGSN does not have enough memory to perform the tasks SGSN (or actually MS) has requested it to perform.060).15).060).060). 0x25 msg_t_inc_w_prot_st GSPPRB (MS initiated): Network may set this cause indicate that it has received a message incompatible with the protocol state (see 3GPP TS 24.GGSN does not have any more room for dynamic PDP addresses. 0x17 dyn_ips_occupied GTPPRB: Cause code returned by GGSN (see 3GPP TS 29. when SGSN (or actually MS) has requested for dynamic PDP address. 0x15 usr_auth_fail Subscriber authentication fails. 0x1B syn_err_in_tft GTPPRB: Cause code returned by GGSN (see 3GPP TS 29.060). 0x24 nonex_msg_type GSPPRB (MS initiated): Network may set this cause to indicate that it has received a message of a type it does not recognize either because this is a message not defined. 24. PDP context activation is rejected.008).060). 24. 0x20 synch_failure GSPPRB (MS initiated): This cause is sent to the network by ME if the SIM detects that the SQN(sequence number) in the authentication request message is out of range (see 3GPP TS 33.060). Authentication shall be considered as failed and GSPPRB's GMM/SM hand uses this internal cause to inform GSPPRB's GSMS hand to abort SMS procedure. GMGPRB: Ptmsi_signature received from previous PAPU/SGSN does not match to current one.) DN05148836 Issue 2-2 Id:0900d805809551ce 531 . 0x1C sem_err_in_pfi GTPPRB: Cause code returned by GGSN (see 3GPP TS 29. or defined but not implemented by the equipment sending this cause (see 3GPP TS 24. 0x1D syn_err_in_pfi GTPPRB: Cause code returned by GGSN (see 3GPP TS 29. 0x1E unknown_apn GMGPRB: Failed to select APN for PDP context during PDP context activation. 0x19 unkn_mand_ext_hd GTPPRB: Cause code returned by GGSN (see 3GPP TS 29. 0x21 mac_failure This cause is sent to the network by ME if the SIM detects that the MAC (message authentication code) in the authentication request message is not fresh (see 3GPP TS 33. 0x1A sem_err_in_tft GTPPRB: Cause code returned by GGSN (see 3GPP TS 29. Routing area update or attach is rejected to new PAPU/SGSN. 0x23 inv_mand_inf GSPPRB (MS initiated): Network may set this cause to indicate that it has received a message with a non-semantical mandatory IE error (see 3GPP TS 24. Ongoing procedure is interrupted.060). 0x22 incorrect_msg GCSPRB: GCSPRB has received message from wrong GMGPRB hand.102. GMGPRB sets this error cause 0x16 ctxt_not_found GTPPRB: Cause code returned by GGSN (see 3GPP TS 29.008).102.008).008).008). 0x18 no_mem_available GTPPRB: Cause code returned by GGSN (see 3GPP TS 29. 0x2E unknown_equip GRNPRB: MAP protocol returned MAP error Unknown equipment. Specified in [SSP . SCP orders SGSN to release MO-SMS Sending. 0x34 cug_reject SGIPRB: Cause code returned by SCP.SCP interface]. 0x33 call_barred SGIPRB: Cause code returned by SCP. GRNPRB: VLR returned Location Update Reject with unexpected Reject Cause. E. GS1PRB sets this error cause in various situations where SM transfer is interrupted (for example when SMS sending is rejected from mobile station direction or when type of subsriber number is invalid or when SMS authentication and/or IMEI check fails or when MAP interface returns negative acknowledgement). 0x28 inv_rai_info GMGPRB: Abnormal RAI values. Specified in [SSP . 0x37 dest_out of_serv Not in use at the moment. GRNPRB: Unexpected data received in MAP message. GRNPRB: VLR returned Location Update Reject with Reject Cause #2. 0x27 msg_inc_w_prot_st GSPPRB (MS initiated): Network may set this cause to indicate that a message it has been received is incompatible with the protocol state (see.008). GRNPRB: Some mandatory data missing from received MAP message.g there is no IMSI in received message from GMGPRB. 0x31 Unassigned_number SGIPRB: Cause code returned by SCP. 3GPP TS 24. Routing area update is rejected to new PAPU/SGSN. 0x30 no_gprs_subscr GRNPRB: MAP protocol returned MAP error Not GPRS subscriber. 0x36 mem_cap_exceeded Not in use at the moment. MS sends incorrect RAI information in routing area update request message to SGSN or GMGPRB receives incorrect RAI information during CS-call.SCP interface]. 0x35 sm_trans_reject SGIPRB: SGIPRB can receive this cause code in ReleaseSMS operation. GCSPRB: Data is missing in received message from GMGPRB. 0x32 oper_det_barring SGIPRB: Cause code returned by SCP. Table 867 532 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont.Ongoing process is rejected. GS1PRB: Short message transfer rejected. 0x2D unexp_data_val GRNPRB: MAP protocol returned MAP error Unexpected data value. GRNPRB: HLR returned unexpected value in MAP message.SCP interface].Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Traffica Reference Guide for SGSN Direct Interface Value Error code Explanation 0x26 cond_ie_err GRNPRB: VLR returned Location Update Reject with Reject Cause #100. GS1PRB sets this error cause when reading of MO or MT SMS subscriber information from database failed. 0x2A imsi_u_in_auc GRNPRB: MAP protocol returned MAP error IMSI unknown in AuC. 0x38 unident_ms GS1PRB: Unidentified mobile station. 0x2B map_system_fail GRNPRB: MAP protocol returned MAP error System failure. Specified in [SSP . 0x2F unexp_cause_val GRNPRB: MAP protocol returned unexpected MAP error value. 0x2C data_missing GRNPRB: MAP protocol returned MAP error Data missing.) Id:0900d805809551ce DN05148836 Issue 2-2 . 0x29 imsi_u_in_hlr GRNPRB: MAP protocol returned MAP error IMSI unknown in HLR. SGIPRB can send this in EventReportSMS operation. SGIPRB can send this in EventReportSMS operation. GS1PRB: Temporary failure. Specified in [SSP . Specified in [SSP . GMGPRB: MS or network has requested action to unknown subscriber.SCP interface].SCP interface]. GS1PRB sets this error cause when subscriber number is not within limits or when MS has done gprs detach or when reading MO SMS subscriber information from database failed.SCP interface].SCP interface].GS1PRB sets this error cause when MO or MT hand creation failed. GS1PRB: Network out of order. SGIPRB can send this in EventReportSMS operation. 0x42 invalid_message SGIPRB: SGIPRB can receive this cause code in ReleaseSMS operation. Specified in [SSP . GS1PRB sets this error cause when MO or MT SMS teleservice code is not provisioned. SGIPRB can send this in EventReportSMS operation. 0x3C temp_failure SGIPRB: Error in SMS handling. SGIPRB: SGIPRB can receive this cause code in ReleaseSMS operation. Specified in [SSP .SCP interface]. SGIPRB can send this in EventReportSMS operation. SGIPRB can send this in EventReportSMS operation. SGIPRB: SGIPRB can receive this cause code in ReleaseSMS operation. 0x44 msg_not_ex_or_imp SGIPRB: SGIPRB can receive this cause code in ReleaseSMS operation.SCP interface]. Specified in [SSP . SGIPRB can send this in EventReportSMS operation. SGIPRB: SGIPRB can receive this cause code in ReleaseSMS operation. SGIPRB can send this in EventReportSMS operation. 0x3B net_outof_order SGIPRB: SGIPRB can receive this cause code in ReleaseSMS operation. 0x3D Congestion SGIPRB: SGIPRB can receive this cause code in ReleaseSMS operation. 0x3E res_navail_unspec Hand creation failed. SGIPRB can send this in EventReportSMS operation. Specified in [SSP .SCP interface]. 0x40 req_fac_nimp SGIPRB: SGIPRB can receive this cause code in ReleaseSMS operation. 0x45 msg_type_not_comp SGIPRB: SGIPRB can receive this cause code in ReleaseSMS operation.SCP interface]. 0x43 info_elem_missing SGIPRB: SGIPRB can receive this cause code in ReleaseSMS operation.) DN05148836 Issue 2-2 Id:0900d805809551ce 533 . SGIPRB can send this in EventReportSMS operation. 0x3F req_fac_not_subsc GS1PRB: Requested facility not subscribed. 0x41 inv_sm_trans_ref SGIPRB: SGIPRB can receive this cause code in ReleaseSMS operation.SCP interface].SCP interface]. Cause code is sent to GMGPRB in message ssf_release_context_ind_s and ssf_release_gprs_ind_s. 0x3A unknown_ms GS1PRB: Unknown mobile station. SGIPRB sets this error cause when Default Call handling is used.Traffica Reference Guide for SGSN Direct Interface Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Value Error code Explanation 0x39 facility_reject GS1PRB: Facility rejected. Specified in [SSP .SCP interface]. Specified in [SSP . Specified in [SSP . Table 867 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. Specified in [SSP . Cause code is sent to GMGPRB in message ssf_release_context_ind_s and ssf_release_gprs_ind_s. Specified in [SSP . detach or RAU update type is unknown. GRNPRB: VLR returned Location Update Reject with Reject Cause #111.SCP interface]. 0x52 param_err GMGPRB: In attach. 0x4A interwork_unspec SGIPRB: SGIPRB can receive this cause code in ReleaseSMS operation.) Id:0900d805809551ce DN05148836 Issue 2-2 . 0x4D cell_reselection GGBPRB: BSS has ordered the MS to perform a cell reselection. GMGPRB: Unknown procedure. GMGPRB: Illegal proc value in gmg internal check. GCSPRB: GCSPRB does not get message from GMGPRB.SCP interface]. SGIPRB can send this in EventReportSMS operation. Specified in [ SSP . Attach or RAU is rejected. 0x4F no_rsp_from_gsn GMGPRB: GTPPRB informs GMGPRB.SCP interface]. GIPPRB: PDP context is released when PS paging fails when QoS traffic class attribute is streaming. The cause code is set after N200 counter is exceeded. Specified in [ SSP . Specified in [ SSP . GTPPRB: GTPPRB informs GMG. 0x4C bad_quality GGBPRB: Radio link quality insufficient to continue communication.Detach is performed. SGIPRB can send this in EventReportSMS operation. Specified in [SSP . that there were no response to SGSN Context Request /Identification Request.SCP interface]. 0x47 invalid_ie_cont Not in use at the moment. 0x4B ms_lost GGBPRB: Radio contact lost with the MS. 0x50 0x51 MS unknown in old PAPU imei_chk_failed GRNPRB: IMEI check of subscriber failed due to no EIR address. 0x48 ncompat_sm_trans Not in use at the moment. GMGPRB: Timer has been expired when co-process did not answer our MM or SM query. Ongoing process is interrupted.Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Traffica Reference Guide for SGSN Direct Interface Value Error code Explanation 0x46 ie_not_ex_or_imp Not in use at the moment. that there were no response to SGSN Context Request/Identification Request. Specified in [SSP . Table 867 534 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. 0x49 prot_error_unspec SGIPRB: SGIPRB can receive this cause code in ReleaseSMS operation. GMGPRB: Mobile is black listed and imei check fails. Ongoing process is interrupted except detach or PDP context deactivation.SCP interface]. 0x4E no_rsp GIPPRB: Mobile was unable to respond to SGSN initiated XID reset. GMGPRB: Unpacking the input message fails. 0x5D hand_ini_failed GCSPRB: Hand process could not be created. 0x55 ptmsi_alloc_fail GMGPRB: PTMSI allocation fails and we cannot use old PTMSI. 0x5B unknown_pdp_ctxt GTPPRB: Requested PDP context was not found. 0x60 unsucc_op GTPPRB: GTPPRB master has removed hand process forcefully. GMGPRB: Search for subscriber from GISFIL/GPIFIL fails. File might be corrupted or search of subscriber from GISFIL/GPIFIL fails. Ongoing process is interrupted. 0x54 protocol GTPPRB: A protocol error occurred between SGSN and GGSN. 0x5A contr_roaming_rej GMGPRB: Routing area update is rejected by feature controlled roaming.GTPPRB sets this error cause. 0x5E no_gg_res_av 0x5F no_rsp_from_ggsn GTPPRB: GGSN did not answer to n3 amount of requests. TC_Guard).) DN05148836 Issue 2-2 Id:0900d805809551ce 535 . 0x5C unknown_dns GTPPRB: Requested APN did not yield any IP addresses or DNS does not answer. Ongoing process is interrupted.Traffica Reference Guide for SGSN Direct Interface Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Value Error code Explanation 0x53 table_err GIPPRB: Attach or inter PAPU RAU rejected during lower layer GPRS mobility management procedures because there is room for new subscriber in TLLI table. GSPPRB sets this error cause when MS has sent message which contains protocol error. Hand creation failed. 0x58 No_rsp_from_scp GMGPRB: Timer has been expired when SCP does not answer to CAMEL operation. GCSPRB: Handling (reading or writing) of GCSPRB file fails. Ongoing process is interrupted. This is internal error in SGSN that prevented one Attach or inter PAPU RAU. GRNPRB: The procedure is discarded because of overload. Subscriber is not allowed to roam. 0x56 unspecified 0x57 opt_not_supp GMGPRB: Authentication. Some parameters in the message were unappropriate. 0x61 op_not_allowed GTPPRB: The same NSAPI already has a tunnel operation ongoing. 0x59 overload GMGPRB: The procedure is discarded because of overload. Cause code is sent to GMGPRB in message ssf_release_context_ind_s and ssf_release_gprs_ind_s. Table 867 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. GSPPRB sets this error cause when MS has sent SMS and MS is not allowed to do any more procedures. GMG does not get ticket from tisero. File might be corrupted or search of subscriber from GCBFIL fails. GSPPRB: General code for different protocol errors. ptmsi reallocation or ptmsi signature reallocation is requested from GMGPRB but service is not activated in SGSN. SGIPRB: No response from SCP. Ongoing procedure is rejected. SCP did not answer during supervision timer (Tssf. GMGPRB: Hand creation fails. imei check. GMGPRB: Handling (reading or writing) of GMGPRB files fails. GSPPRB: Network error. 0x68 no_pdp_context GMGPRB: Modification or deactivation to PDP context that does not exist.Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Traffica Reference Guide for SGSN Direct Interface Value Error code Explanation 0x62 error Switchover takes place. Message gtp_datavolume_res_s is a response to message gtp_datavolume_req_s sent by SGIPRB. 0x6F GTPPRB: Invalid packet received and discarded. 0x63 GGSN unreachable 0x64 discard 0x65 not_defined 0x66 nsapi_in_use GMGPRB: Subscriber tries to activate a PDP context that is already activated. 0x77 master_write_fail 0x78 no_rsp_from_map GRNPRB: MAP protocol did not responded before response timer expired. GMGPRB sets this error cause. SGIPRB master has received message prepare_for_switchover_s. you can purchase more capacity. If not. PDP context modification or deactivation is rejected. 0x69 Error No Access Point Name 0x6A invalid_ti GSPPRB (MS initiated): Network has received SM-message with invalid transaction identifier. PDP context activation is rejected. This is the case when there is no PDP context with these IMSI and NSAPI. 0x6E apn_changed GMGPRB: PDP context APN is changed in HLR. 0x67 no_subscription GMGPRB: No subscriptions for subscriber in GSBASE.) Id:0900d805809551ce DN05148836 Issue 2-2 . SGIPRB forwards this cause code to GMGPRB in message ssf_release_context_ind_s when cause code is received from GTPRPB in message gtp_datavolume_res_s. Table is full or max amount of same kind of contexts is exceeded. PDP context activation procedure is rejected. An active PDP context is deactivated. Switchover is indicated to hand process with this cause code. PDP context activation is rejected. 0x7A no_rsp_from_vlr GRNPRB: VLR did not respond before response timer expired. 0x71 og_inter_sys_rau_c Outgoing inter system RA update 0x75 max_pdp_exceeded GMGPRB: User has more PDP contexts than supported amount of contexts in inter SGSN RAU (RAU from other vendors SGSN to Nokia Siemens Network SGSN).008) 0x6B no_sgsn_resources Adding PDP context to GCNFIL fails. Unsupported PDP context are deactivated. Table 867 536 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. This cause code is used only internally by SGIPRB between SGIPRB master and SGIPRB hand process. If there is enough capacity. you should distribute the BSCs more evenly for each PAPU/SGSN. (See specification 3GPP TS 24. An active PDP context is deactivated. 0x79 abort_from_map GRNPRB: Abort received from MAP protocol. Check that you have enough PDP context capacity in your SGSNs. SAPI changed 0x70 no_linked_ti GMGPRB: MS tries to activate secondary PDP context without linked Transaction Identity. PDP context activation is rejected. 0x6C vaa_not_allowed 0x6D pdp_type_changed GMGPRB: PDP context type is changed in HLR. 0x7D 0x7E No triplet available roaming_not_allowed GRNPRB: MAP protocol returned MAP error Roaming not allowed. 0x89 Table 867 ciph_hw_malfunct GIPPRB: Malfunction of Cipher HW. 0x84 in_roaming_rejected 0x85 no_peer_response 0x86 0x87 GIPPRB: PDP context was released when retransmission counter N200 was exceeded for acknowledged LLC data transfer. 0x80 hand_creation_fail GRNPRB: Creation of hand process failed. In this case mobile just rejected the PDP context modification or establishment to acknowledged LLC data transfer mode. Radio link failed inv_xid_response GIPPRB: PDP context was released because mobile sent XID in RAU procedure that was not encoded according to 3GPP TS 44. Attach/RAU is rejected. This is PDP context modification collision case between SGSN and mobile.064 and 3GPP TS 44. 0x83 db_no_hlr GRNPRB: HLR of subscriber does not exist in GSBASE. 0x81 vlr_unreachable GRNPRB: VLR of subscriber is unreachable or VLR association does not exist. HLR returns this cause when services supported by subscriber's home PLMN are not supported in this PLMN. Attach/RAU is rejected.065 specifications. Attach/RAU is rejected. GIPPRB: PDP context establishment or modification rejected because mobile sent disconnect mode response (DM) when acknowledged LLC data transfer mode was being established by SGSN.Traffica Reference Guide for SGSN Direct Interface Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Value Error code Explanation 0x7B db_error GRNPRB: Database error in GSBASE. GMGPRB: MAP protocol returned MAP error Roaming not allowed. GRNPRB: Roaming is not allowed for subscriber. 0x88 dm_received GIPPRB: PDP context establishment or modification rejected because mobile send disconnect command (DISC) or when acknowledged LLC data transfer mode was being established by SGSN. GIPPRB: PDP context was released because there was no free memory left when a mobile tried to negotiate data or header compression. For example. GMGPRB: Roaming is not allowed for subscriber (no roaming agreement with subscriber's PLMN).) DN05148836 Issue 2-2 Id:0900d805809551ce 537 . Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. 0x82 db_no_subs GRNPRB: Subscriber not found from GSBASE. GMGPRB: MS does not support ciphering. 0x7C subscr_chk_fail GRNPRB: Subscription check indicated that access to network is not allowed. 0x8F Table 867 538 coll_ra_upd Colliding routing area update request from MS. This is an internal error in SGSN that caused the release of modified PDP context or prevented establishment of one PDP context. (Case 7): GIPPRB: PDP context establishment or modification rejected by SNDCP layer because GPRS mobility management requested acknowledged LLC transfer mode in High Capacity PAPU.) Id:0900d805809551ce DN05148836 Issue 2-2 . (Case 4): PDP context establishment or modification rejected because the maximum amount of supported PDP contexts were already established. Scenarios: Collision of 2 RAU from same MS1) 2 incoming RAU (first one is killed with cause 0x8F) 2) 2 outgoing RAUs (first one is killed with cause 0x8F) 3) 1 incoming and 1 outgoing RAU 4) 1 outgoing and 1 incoming RAU. 0x8B qos_mismatch GIPPRB: PDP context establishment or modification rejected because GPRS mobility management sent unsupported value in QoS reliability class attribute. (Case 6): PDP context establishment rejected because SNDCP protocol layer internal variable was corrupted in RAU procedure. Ongoing procedure is interrupted/rejected and attach procedure is started. GIPPRB: PDP context establishment or modification rejected because there was an internal error in SNDCP layer during PDP context establishment. This is internal error in SGSN that caused the release of modified PDP context or prevented establishment of one PDP context. 0x8E coll_attach GSPPRB: GSPPRB's GMM/SM hand uses this internal cause to inform GSPPRB's GSMS hand to abort SMS procedure. 0x8C sys_mem_exceeded GIPPRB: PDP context was released because there were not enough memory for acknowledged LLC data transfer. (Case 2): GPRS mobility management requested SNDCP layer to release or modify PDP context with NSAPI that cannot be found. (Case 3): PDP context establishment or modification rejected because GPRS mobility management sent a NSAPI value that was already used by another PDP context. 0x8D gb_unavailable GGBPRB: Internal error in Gb interface. Network has a task ongoing and attach request arrives from MS. This is an internal error in SGSN that prevented the establishment of one PDP context.Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Value Error code 0x8A Traffica Reference Guide for SGSN Direct Interface Explanation (Case 1): PDP context establishment or modification failed because there was no free memory left for PDP context reassembly buffer. This is an internal error in SGSN that caused the release of modified PDP context or prevented establishment of one PDP context. (Case 5): PDP context establishment or modification rejected because mapping of NSAPI value sent to SAPI failed in SNDCP protocol layer. Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. This is an internal error in SGSN that prevented establishment of a PDP context. GMGPRB: Colliding attach request from MS. SMS procedure collides with an attach procedure. This is an internal error in SGSN that prevented establishment of a PDP context. Network has a task ongoing and routing area update request arrives from MS. Ongoing procedure is interrupted/rejected and routing area update procedure is started. This is an internal error in SGSN that caused the release of modified PDP context or prevented establishment of one PDP context. GSPPRB's GMM/SM hand uses this internal cause to inform GSPPRB's GSMS hand to abort SMS procedure. Cause code is sent to GMGPRB in message ssf_release_context_ind_s and ssf_release_gprs_ind_s. 0x99 coll_identity_enq GSPPRB: When MS has a task ongoing and identity enquiry procedure is started from network. GMGPRB sets this error cause. 0x9D cap_unspecified Unspecified error situations in SGIPRB. ActivityTest operation failed. GMGPRB: Network has a MM or SM process ongoing and detach request is arrived from MS or the network. This is a SGSN fault. 0x9E cap_no_credit Table 867 GSPPRB: When MO. create CAP failed. create session failed. 0x97 gip_err GMGPRB: GIPPRB does not answer to radio param update or assign Kc. 0x9C nw_err GSPPRB: When MS is not allowed to start anymore procedures. This cause does not cause any failure and GSPPRB uses it to suspend SMS procedure until authentication procedure is handled. Resends of different messages have been defined in specs (see. For example. This cause does not cause any failure and GSPPRB uses it to suspend SMS procedure until PTMSI reallocation procedure is handled. 0x9A coll_auth When MS has a task ongoing and authentication procedure is started from network. Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. Maximum amount of resends have been sent to MS and MS does not respond. Ongoing process is interrupted. 0x94 mnr GSPPRB: MS is unreachable. Ongoing procedure is interrupted.or MT SMS is received and there is already a GMM procedure ongoing. SMS procedure collides with a detach procedure. GSPPRB sets this error cause. 0x95 cs_call GS1PRB: Network has a MM or SM process ongoing and CS call indication is received from MS or the network. unknown operation from SCP. SMS procedure collides with an attach or a detach procedure. create context failed.Traffica Reference Guide for SGSN Direct Interface Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Value Error code Explanation 0x90 coll_detach GSPPRB: GSPPRB's GMM/SM hand uses this internal cause to inform GSPPRB's GSMS hand to abort SMS procedure. 0x91 coll_gmm_proc 0x92 ll_fail 0x93 illegal_ms GRNPRB: VLR returned Location Update Reject with Reject Cause #3. GSPPRB's GMM/SM hand uses this internal cause to inform GSPPRB's GSMS hand to abort SMS procedure. 0x9B coll_ptmsi_realloc GSPPRB: When MS has a task ongoing and PTMSI reallocation procedure is started from network.) DN05148836 Issue 2-2 Id:0900d805809551ce 539 . Timer has expired when GSPPRB or MS does not answer to authentication and ciphering request during MM or SM process. 3GPP TS 24. 0x96 gsp_exp GMGPRB: Timer has been expired when GSPPRB or MS do not answer authentication and ciphering requests during MM or SM process.008). This cause does not cause any failure and GSPPRB uses it to suspend SMS procedure until the identity procedure is handled. operation response is not acknowledged. 0x98 gsp_err GSPPRB: GMM/SM hand uses this internal cause to inform GSPPRB's GSMS hand to abort SMS procedure when GSPPRB's procedure timer has been expired. Ongoing process is interrupted and a CS call is activated. 0xA2 plmn_not_allow GRNPRB: VLR returned Location Update Reject with Reject Cause #11. This cause is used when MS is older than 3GPP Release 99. 0xB4 coll_mod Network has a PDP modification ongoing and a new PDP modification request has arrived from MS. 0xAC sabm_disc_collision GIPPRB: SABM-DISC collision . 0xA5 mandat_info_el_err GRNPRB: VLR returned Location Update Reject with Reject Cause #96. 0xB3 coll_act GMGPRB: Network has a PDP activation ongoing and new PDP activation request has arrived from MS. Table 867 540 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. unk_pdp_add_or_type 0xB7 contr_roam_rl97_rej Roaming is restricted by a controlled roaming feature. 0xA1 illegal_me GRNPRB: VLR returned Location Update Reject with Reject Cause #6. 0xA6 info_el_no_ex_or_i GRNPRB: VLR returned Location Update Reject with Reject Cause #99. 0xB9 ac_max_user_fail GMGPRB: Admission control: allowed RT PDP context user limit exceeded. 0xAB vlr_congestion GRNPRB: VLR returned Location Update Reject with Reject Cause #22. 0xB0 cdr_decoding_error GTPPRB: CG could not decode CDR. Colliding deactivation interrupts ongoing process and PDP deactivation is performed.) Id:0900d805809551ce DN05148836 Issue 2-2 .DM response sent. 0xAF req_not_fulfilled GTPPRB: CG did not fulfil the requested operation. 0xB5 info_to_gs1 GIPPRB informs GS1PRB about MS activity as requested by GRNPRB. 0xAA msg_not_ex_or_impl GRNPRB: VLR returned Location Update Reject with Reject Cause #97. 0xB8 ac_max_bw_fail GMGPRB: Admission control: allowed RT PDP context bandwidth limit exceeded. 0xA9 semantic_inc_msg GRNPRB: VLR returned Location Update Reject with Reject Cause #95. Ongoing process is interrupted and a new activation is performed. 0xAD req_allr_fulfilled GTPPRB: CG has already fulfilled the request.Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Traffica Reference Guide for SGSN Direct Interface Value Error code Explanation 0x9F forced_deact GCSPRB: GCSPRB asks GCHPRB to close all this IMSIs S-CDR. 0xA3 loc_area_not_allow GRNPRB: VLR returned Location Update Reject with Reject Cause #12. 0xA7 imsi_unknwn_in_vlr VLR returned Location Update Reject with Reject Cause #4 0xA8 network_failure GRNPRB: VLR returned Location Update Reject with Reject Cause #17. 0xAE incorrect_seqnums GTPPRB: CG thinks Sequence Number of Released/Cancelled Packets IE is incorrect. Routing area update or attach is rejected. 0xA4 roam_nt_allow_in_la GRNPRB: VLR returned Location Update Reject with Reject Cause #13. Ongoing process is interrupted and new modification is performed. 0xB1 no_suit_cell_in_la GRNPRB: VLR returned Location Update Reject with Reject Cause #15. 0xBA ac_max_act_user_fail GMGPRB: Admission control: allowed active RT PDP context user limit exceeded. IMSI's all S-CDRs are closed. 0xB6 unk_pdp_add_or_type GGSN does not support PDP address or PDP type requested by SGSN. When GCSPRB is not received S-CDR related information from GMGPRB during PDP context deactivation or detach. 0xB2 coll_deact GMGPRB: Network has a SM process ongoing and PDP deactivation request has arrived from MS or network. 0xC6 regular_deact GSPPRB: MS sends PDP context deactivation message with cause #36. 0xC7 qos_not_accepted GSPPRB: MS sends PDP context deactivation with cause #37. 0xCB not_prepaid_user GTPPRB: Modification or deactivation to pdp context that is not for prepaid/CAMEL subscriber. 0xC4 llc_or_sndcp_fail GSPPRB: MS sends PDP context deactivation message with cause #25. Table 867 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. Cause code is sent to GMGPRB in message ssf_release_context_ind_s and ssf_release_gprs_ind_s. 0xCD abort_from_cap SGIPRB: TC_Abort received from SCP. 0xC2 mo_sms_smsc_barr GS1PRB: MO-SMS denied based on SMSC. Message gtp_datavolume_res_s is response to message gtp_datavolume_req_s sent by SGIPRB.Traffica Reference Guide for SGSN Direct Interface Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Value Error code Explanation 0xBB ac_max_bw_fail_2 GMGPRB: Secondary admission control: allowed RT PDP context bandwidth limit exceeded. Cause code is sent to GMGPRB in message ssf_release_context_ind_s and ssf_release_gprs_ind_s. 0xC3 mt_sms_smsc_barr GS1PRB: MT-SMS denied based on SMSC. 0xC7 qos_not_accepted GSPPRB: MS sends PDP context deactivation with cause #37. 0xC1 mo_sms_a_num_barr GS1PRB: MO-SMS denied based on A-number. 0xBF no_rsp_from_bss GMGPRB: No response from BSS. This is the case when GTP recognizes that this is not prepaid subscriber. In this case the setup of streaming class PDP context was delayed too much. 0xBD ac_modify_fail GMGPRB: Admission control: allowed RT PDP context bandwidth limit exceeded in PDP context modify procedure. 0xC0 rt_setup_timeout GIPPRB: Streaming class PDP context was released when the context admission control timer expired. SGIPRB: SGIPRB forwards this cause code to GMGPRB in message ssf_release_context_ind_s when cause code is received from GTPRPB in message. gtp_datavolume_res_s. 0xCA inv_own_ip_address GTPPRB: GTP tells GMG that own PAPU IP address is invalid. SCP orders SGSN to release GPRS session and/or PDP contexts.) DN05148836 Issue 2-2 Id:0900d805809551ce 541 . Attach and RAU are rejected. 0xC9 alert_req_grn_case GIPPRB: GIPPRB informs GRNPRB about MS activity as requested by GRNPRB. 0xCE SG4:ptmsi_imsi_mismatch _c There are two subscribers with the same P-TMSI but with a different IMSI. 0xBC ac_max_act_user_f_2 GMGPRB: Secondary admission control: allowed active RT PDP context user limit exceeded. 0xBE pfc_create_fail BSS rejects PFC creation procedure. 0xC5 insuf_recources GSPPRB: MS sends PDP context deactivation message with cause #26. 0xC8 no_pfc_support GGBPRB: BSS does not support PFC procedures. 0xCC release_from_scp SGIPRB: ReleaseGPRS operation from SCP received. ) Id:0900d805809551ce DN05148836 Issue 2-2 . This is an internal error in the 2G SGSN that prevented the establishment of a PDP context. 0xD2 nsapi_error_c Case 1 GIPPRB: PDP context establishment or modification rejected. GIPPRB (Case 2): The Iu-initiated PS Paging could not be performed in the Gb-interface because there were no GIPPRB hand processes left. 0xD0 inv_xid_command_c A PDP context was released because the MS sent a XID command that was not encoded according to specifications 3GPP TS 44.065. no free records 0xD8 ggsn_restarted_c GTPPRB sets this error cause.Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Traffica Reference Guide for SGSN Direct Interface Value Error code Explanation 0xCE SG5:disc_received_c GIPPRB (Case 1): PDP context establishment or modification was rejected because the MS sent a disconnect command (DISC) when the acknowledged LLC data transfer mode was being established by the SGSN. GIPPRB (Case 2): PDP context was released because there was not enough memory for acknowledged LLC data transfer. 0xD4 sndcp_out_of_sync_c PDP context released because SNDCP protocol entities in 2G SGSN and mobile were out of synchrony. This is a PDP context modification collision case between the SGSN and the MS. 0xD7 max_subs_exceeded_c Subscriber table in GMGPRB is full. 0xD6 ptmsi_imsi_mismatch_c There are two subscribers who have different IMSIs but have the same PTMSI. GIPPRB: An Iu-initiated PS Paging was unsuccessful because neither IMSI nor P-TMSI matched with the one already known in the GIPPRB hand process. because GPRS mobility management sent NSAPI value was already used by another PDP context. This is an internal error in the SGSN that prevents the establishment of a PDP context. This is internal error in 2G SGSN that caused release of modified PDP context or prevented establishment of one PDP context. GIPPRB (Case 3): The Iu-initiated PS Paging could not be performed in the Gb-interface because the GIPPRB hand creation failed. 0xD1 no_resources_c GIPPRB (Case 1): The PDP context establishment was rejected because the maximum amount of supported PDP contexts had already been established. Case 2 GIPPRB: PDP context establishment or modification rejected because mapping of NSAPI value sent to SAPI failed in SNDCP protocol layer. when GGSN has restarted. GIPPRB (Case 2): a PDP context was released because the MS sent a disconnect command (DISC) in the acknowledged LLC data transfer mode.064 and 3GPP TS 44. Table 867 542 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. 0xCF out_of_memory_c GIPPRB (Case 1): PDP context establishment or modification failed because there was no free memory left for the PDP context buffering mechanism. 0xD3 serv_rej_in_hc_mode PDP context establishment or modification rejected by SNDCP layer because GPRS mobility management requested acknowledged LLC transfer mode in High Capacity PAPU. 0xD5 variable_corrupted_c The mapping of an SNDCP protocol layer internal parameter failed when a PDP context was being established. 0xE4 req_gbr_dl_not_avail_c GMGPRB internal cause code GSPPRB: The RNC sends for example a RAB assignment response with RANAP cause 35 (see 3GPP TS 25. 0xEA r_conn_lost_ue_c GMGPRB internal cause code GSPPRB: The RNC sends for example a RAB assignment response with RANAP cause 46 (see 3GPP TS 25.413).413).413). emergency calls are possible for MEs with a blacklisted IMEI. 0xDF req_trf_c_not_avl_c GMGPRB: This cause comes from the RNC (see 3GPP TS 25.413).413). 0xEB Rls_due_ue_sig_c GMGPRB internal cause code 0xEC Rls_due_utran_r_c GMGPRB: internal cause code Table 867 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont.413).413).413).) DN05148836 Issue 2-2 Id:0900d805809551ce 543 .413). GSPPRB: The RNC sends for example a RAB assignment response with RANAP cause 18 (see 3GPP TS 25.413). 0xE3 req_gbr_not_avail_c GMGPRB internal cause code GSPPRB: The RNC sends for example a RAB assignment response with RANAP cause 21 (see 3GPP TS 25. 0xDE ac_max_ave_bw_limit_c Admission control: the RT PDP contexts exceeded the average bandwidth limit.413). 0xE0 req_mbr_not_avail_c GMGPRB internal cause code GSPPRB: The RNC sends for example a RAB assignment response with RANAP cause 20 (see 3GPP TS 25. 0xE8 inv_rab_param_c_c GMGPRB internal cause code GSPPRB: The RNC sends for example a RAB assignment response with RANAP cause 23 (see 3GPP TS 25. 0xE5 req_gbr_ul_not_avail_c GMGPRB internal cause code GSPPRB: The RNC sends for example a RAB assignment response with RANAP cause 36 (see 3GPP TS 25.413). 0xE2 req_mbr_ul_not_avail_c GMGPRB internal cause code GSPPRB: The RNC sends for example a RAB assignment response with RANAP cause 34 (see 3GPP TS 25. 0xE1 req_mbr_dl_not_avail_c GMGPRB internal cause code GSPPRB: The RNC sends for example a RAB assignment response with RANAP cause 33 (see 3GPP TS 25. 0xE6 req_tr_delay_not_a_c GMGPRB internal cause code GSPPRB: The RNC sends for example a RAB assignment response with RANAP cause 22 (see 3GPP TS 25.413). 0xE9 inv_rab_param_v_c GMGPRB internal cause code GSPPRB: The RNC sends for example a RAB assignment response with RANAP cause 19 (see 3GPP TS 25.Traffica Reference Guide for SGSN Direct Interface Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Value Error code Explanation 0xDB sg_err_t_imei_fail_cs _allow_c When the feature enabling blacklisted MEs to have CS service (Feature SG02156) is active. 0xE7 invalid_rab_id_c GMGPRB internal cause code GSPPRB: The RNC sends for example a RAB assignment response with RANAP cause 30 (see 3GPP TS 25. while waiting for a response to Relocation Request. 0xF7 treloccompl_exp_c In relocation. 0xFC unkn_target_rnc_c The CN rejects relocation with RANAP cause 9 (see 3GPP TS 25. Relocation is interrupted. Table 867 544 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. 0xF2 coll_og_cs_call_c An outgoing CS call indication collided in the previous location (in case of an SGSN Context Request where the extension header includes a Suspend Request). 0xF4 rab_pre_empted_c The RNC sends for example RAB assignment response with RANAP cause 53 (see 3GPP TS 25. The ongoing process is interrupted and the outgoing attach is performed.413) because the target RNC is not known to the CN. timer has been expired. timer has been expired. The ongoing process is interrupted and the purge is performed. 0xF5 trelocovera_exp_c The SRNC sends for example Relocation cancel with RANAP cause 2 (see 3GPP TS 25. The ongoing process is interrupted and the outgoing CS call is performed.413). or SRSN context request. 0xF0 coll_og_rau_c An outgoing RA update request collided with an ongoing procedure. while waiting for Relocation Complete.413). The ongoing process is interrupted and the outgoing RA update is performed.413).413). 0xFF req_cip_a_n_sup_c The RNC rejects security mode procedure with RANAP cause 12 (see 3GPP TS 25. 0xFB unabl_estab_d_r_c The RNC sends for example a RAB assignment response with RANAP cause 8 (see 3GPP TS 25. 0xFE successfu_reloc_c The RNC sends for example an Iu release request with RANAP cause 11 (see 3GPP TS 25. 0xEF coll_og_attach_c An outgoing attach request collided with an ongoing procedure.Note:Queuing is not supported in the SGSN 0xF9 reloc_triggered_c The RNC indicates failed operation because of relocation by sending RANAP cause 6 (see 3GPP TS 25. 0xFD reloc_cancelled_c Relocation cancel has been received. Relocation is interrupted. 0xEE no_res_tar_cell_c GMGPRB: internal cause code GSPPRB: The RNC sends for example a RAB assignment response with RANAP cause 53 (see 3GPP TS 25.413).413) because of the requested ciphering parameters.413). 0xF6 trelocprep_exp_c The SRNC sends for example Relocation cancel with RANAP cause 3 (see 3GPP TS 25. 0xFA trelocalloc_exp_c In relocation. 0xF8 tqueing_expiry_c The RNC sends for example a RAB assignment response with RANAP cause 5 (see 3GPP TS 25.413).) Id:0900d805809551ce DN05148836 Issue 2-2 .413).413). RAB assignment. CN indicates a failed Relocation resource allocation procedure due to the expiry of the timer TRELOCalloc. 0xF3 No_rsp_from_rnc_c There is no response from the RNC to security mode-. 0xF1 coll_purge_c A purge request collided with an ongoing procedure.Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Traffica Reference Guide for SGSN Direct Interface Value Error code Explanation 0xED user_inactivity_c GMGPRB: internal cause codeGSPPRB: The RNC sends for example an Iu release request with RANAP cause 16 (see 3GPP TS 25. 413).413). 0x106 cond_viol_t_h_p_c The RNC sends for example a RAB assignment response with RANAP cause 25 (see 3GPP TS 25.413). 0x110 res_opt_reloc_c SRNC requests Relocation for resource optimization with RANAP cause 41 (see 3GPP TS 25. 0x103 time_criti_relo_c SRNC requests Relocation for time critical reason with RANAP cause 17 (see 3GPP TS 25.413) 0x10D rep_integ_chk_f_c The RNC rejects security mode procedure with RANAP cause 37 (see 3GPP TS 25. Table 867 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont.413).Case 2: LAI has not been configured to target RNC.413) because there is a conflict with the existing security parameters.413).Traffica Reference Guide for SGSN Direct Interface Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Value Error code Explanation 0x101 Ch_ci_pro_n_sup_c The RNC rejects security mode procedure with RANAP cause 13 (see 3GPP TS 25. 0x10A Rel_fail_targ_c The TRNC indicates a failed Relocation resource allocation with RANAP cause 29 (see 3GPP TS 25.413). 0x102 fail_r_if_proce_c The RNC sends for example an Iu release request with RANAP cause 14 (see 3GPP TS 25. 0x108 Up_versio_n_sup_c The RNC sends for example a RAB assignment response with RANAP cause 27 (see 3GPP TS 25.413).413). 0x117 ded_ass_dat_n_a_c GSPPRB: The RNC indicates failed procedure with RANAP cause 49 (see 3GPP TS 25. 0x104 req_tr_dela_n_a_c The RNC sends for example a RAB assignment response with RANAP cause 22 (see 3GPP TS 25. 0x107 cond_viol_gbr_c The RNC sends for example a RAB assignment response with RANAP cause 26 (see 3GPP TS 25. 0x116 dec_keys_n_avl_c The RNC rejects security mode procedure with RANAP cause 48 (see 3GPP TS 25. 0x10B no_remain_rab_c GSPPRB: The RNC sends for example an Iu release request with RANAP cause 31 (see 3GPP TS 25.413) 0x109 iu_up_failure_c The RNC sends for example an Iu release request with RANAP cause 28 (see 3GPP TS 25.) DN05148836 Issue 2-2 Id:0900d805809551ce 545 . 0x112 reloc_dsrbl_r_r_c SRNC requests Relocation for radio interface reasons with RANAP cause 43 (see 3GPP TS 25.413). 0x115 rnc_un_est_rfcs_c The RNC sends for example a RAB assignment response with RANAP cause 47 (see 3GPP TS 25.413).413) 0x118 reloc_targ_n_al_c Case 1: The RNC state is not ‘available’.413).413). 0x10F req_superseded_c The RNC sends for example a RAB assignment response with RANAP cause 39 (see 3GPP TS 25.Case 3: The allocation of connection ID failed.413).413). 0x113 reloc_n_su_targ_c GMGPRB: Relocation Required message is not received with target RNC information.GSPPRB: TRNC indicates failed Relocation resource allocation with RANAP cause 44 (see 3GPP TS 25. 0x105 cond_viol_sdu_p_c The RNC sends for example a RAB assignment response with RANAP cause 24 (see 3GPP TS 25. 0x111 req_info_na_c The RNC rejects request with RANAP cause 42 (see 3GPP TS 25.413). 0x114 directed_retry_c RANAP cause 45 (see 3GPP TS 25.413).413). 413). 0x120 usr_restr_s_ind_c The RNC indicates location reporting procedure with RANAP cause 81 (see 3GPP TS 25. external cause #12 is sent to the MS. 0x11E loa_hig_in_tar_c The RNC indicates failed procedure with RANAP cause 57 (see 3GPP TS 25. 0x11B geran_iu_fail_c The RNC sends for example a RAB assignment response with RANAP cause 54 (see 3GPP TS 25.GSPPRB: The RNC indicates failed procedure with RANAP cause 115 (see 3GPP TS 25. 0x12A network_optimis_c The RNC indicates failed procedure with RANAP cause 116 (see 3GPP TS 25. 0x134 iu_conn_fail_es_c The RNC or CN indicates the failed procedure with RANAP cause 66 (see 3GPP TS 25. 0x126 absrt_stx_e_f_c_c The RNC or CN indicates protocol error with RANAP cause 102 (see 3GPP TS 25. 0x11F unkn_iu_trns_as_c The RNC indicates failed procedure with RANAP cause 65 (see 3GPP TS 25.Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Traffica Reference Guide for SGSN Direct Interface Value Error code Explanation 0x119 loc_report_cong_c The RNC indicates the failed location reporting procedure with RANAP cause 51 (see 3GPP TS 25. 0x132 max_sgsn_pdp_re_c The GCSPRB rejects request to activate a PDP context due to the lack of SGSN level capacity. 0x125 abstr_stx_e_i_c The RNC or CN indicates protocol error with RANAP cause 101 (see 3GPP TS 25. 0x135 hlr_acc_rest_2g_11_c Subscriber access to GERAN is rejected due to HLR access restriction. 0x121 usr_restr_e_ind_c The RNC indicates location reporting procedure with RANAP cause 82 (see 3GPP TS 25.413).413). 0x11A r_loa_serv_cell_c RNC overload indication with RANAP cause 52 (see 3GPP TS 25.413).413).413).413). Table 867 546 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. 0x127 om_intervention_c The RNC indicates failed procedure with RANAP cause 113 (see 3GPP TS 25. 0x11C a_r_due_sh_net_c The RNC indicates failed procedure with RANAP cause 55 (see 3GPP TS 25.) Id:0900d805809551ce DN05148836 Issue 2-2 .413).413).413).413). 0x122 normal_release_c GSPPRB: The RNC or CN indicates Iu release with RANAP 0x123 trnsfr_syntax_e_c The RNC or CN indicates protocol error with RANAP cause 97 (see 3GPP TS 25.413). 0x128 no_resource_avl_c The RNC indicates failed procedure with RANAP cause 114 (see 3GPP TS 25.413).413).413).413). 0x124 abstr_stx_e_r_c The RNC or CN indicates protocol error with RANAP cause 100 (see 3GPP TS 25.413). 0x129 unspecific_fail_c GMGPRB: A RAB Assignment Response is received with an unknown context identifier. 0x136 hlr_acc_rest_2g_12_c Subscriber access to GERAN is rejected due to HLR access restriction. external cause #11 is sent to the MS.413). 0x11D rl_n_s_due_pue_c The TRNC indicates failed Relocation resource allocation with RANAP cause 56 (see 3GPP TS 25. external cause #14 is sent to the MS. external cause #11 is sent to the MS. 0x14C plmn_rest_3gto2g_14_c UMTS subscriber access to GERAN is rejected due to the local access restriction. 0x149 plmn_rest_3gto2g_11_c UMTS subscriber access to GERAN is rejected due to the local access restriction. 0x13B hlr_acc_rest_3g_12_c Subscriber access to UTRAN is rejected due to HLR access restriction. 0x14A plmn_rest_3gto2g_12_c UMTS subscriber access to GERAN is rejected due to the local access restriction. 0x148 plmn_rest_2gto3g_15_c GSM subscriber access to UTRAN is rejected due to the local access restriction. external cause #12 is sent to the MS. 0x13D hlr_acc_rest_3g_14_c Subscriber access to UTRAN is rejected due to HLR access restriction. external cause #12 is sent to the MS. external cause #15 is sent to the MS. 0x142 plmn_rest_2gto2g_14_c GSM subscriber access to GERAN is rejected due to the local access restriction. external cause #13 is sent to the MS. external cause #15 is sent to the MS. 0x13F plmn_rest_2gto2g_11_c GSM subscriber access to GERAN is rejected due to the local access restriction. 0x138 hlr_acc_rest_2g_14_c Subscriber access to GERAN is rejected due to HLR access restriction. external cause #14 is sent to the MS. external cause #14 is sent to the MS. 0x140 plmn_rest_2gto2g_12_c GSM subscriber access to GERAN is rejected due to the local access restriction. 0x14B plmn_rest_3gto2g_13_c UMTS subscriber access to GERAN is rejected due to local access restriction. 0x139 hlr_acc_rest_2g_15_c Subscriber access to GERAN is rejected due to HLR access restriction. 0x141 plmn_rest_2gto2g_13_c GSM subscriber access to GERAN is rejected due to the local access restriction. 0x13C hlr_acc_rest_3g_13_c Subscriber access to UTRAN is rejected due to HLR access restriction. external cause #11 is sent to the MS. external cause #14 is sent to the MS. Table 867 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. external cause #13 is sent to the MS.Traffica Reference Guide for SGSN Direct Interface Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Value Error code Explanation 0x137 hlr_acc_rest_2g_13_c Subscriber access to GERAN is rejected due to HLR access restriction.) DN05148836 Issue 2-2 Id:0900d805809551ce 547 . external cause #11 is sent to the MS. 0x147 plmn_rest_2gto3g_14_c GSM subscriber access to UTRAN is rejected due to the local access restriction. external cause #13 is sent to the MS. external cause #13 is sent to the MS. external cause #12 is sent to the MS. 0x13A hlr_acc_rest_3g_11_c Subscriber access to UTRAN is rejected due to HLR access restriction. external cause #12 is sent to the MS. external cause #13 is sent to the MS. 0x145 plmn_rest_2gto3g_12_c GSM subscriber access to UTRAN is rejected due to the local access restriction. external cause #15 is sent to the MS. external cause #14 is sent to the MS. external cause #11 is sent to the MS. 0x13E hlr_acc_rest_3g_15_c Subscriber access to UTRAN is rejected due to HLR access restriction. 0x143 plmn_rest_2gto2g_15_c GSM subscriber access to GERAN is rejected due to the local access restriction. 0x144 plmn_rest_2gto3g_11_c GSM subscriber access to UTRAN is rejected due to the local access restriction. 0x146 plmn_rest_2gto3g_13_c GSM subscriber access to UTRAN is rejected due to the local access restriction. external cause #15 is sent to the MS. external cause #12 is sent to the MS. external cause #11 is sent to the MS. external cause #13 is sent to the MS. 0x158 subs_cnt_rest_3g_11_c The subscriber access to UTRAN is rejected due to subscriber count access restriction. 0x14E plmn_rest_3gto3g_11_c UMTS subscriber access to UTRAN is rejected due to the local access restriction. 0x15F coll_serv_request_c A Service request collided with an ongoing procedure. 0x162 identity_no_resp_c Indication of the failed procedure. external cause #15 is sent to the MS. external cause #15 is sent to the MS. 0x156 subs_cnt_rest_2g_14_c The subscriber access to GERAN is rejected due to subscriber count access restriction. 0x151 plmn_rest_3gto3g_14_c UMTS subscriber access to UTRAN is rejected due to the local access restriction. external cause #11 is sent to the MS. 0x161 auth_no_resp_c Indication of the failed procedure. 0x15B subs_cnt_rest_3g_14_c The subscriber access to UTRAN is rejected due to subscriber count access restriction. 0x155 subs_cnt_rest_2g_13_c The subscriber access to GERAN is rejected due to subscriber count access restriction. external cause #15 is sent to the MS. 0x154 subs_cnt_rest_2g_12_c The subscriber access to GERAN is rejected due to subscriber count access restriction. 0x15A subs_cnt_rest_3g_13_c The subscriber access to UTRAN is rejected due to subscriber count access restriction. external cause #14 is sent to the MS. because there is no response to the identity request. external cause #12 is sent to the MS. external cause #14 is sent to the MS. external cause #13 is sent to the MS. 0x150 plmn_rest_3gto3g_13_c UMTS subscriber access to UTRAN is rejected due to the local access restriction. 0x152 plmn_rest_3gto3g_15_c UMTS subscriber access to UTRAN is rejected due to the local access restriction. external cause #15 is sent to the MS. 0x15C subs_cnt_rest_3g_15_c The subscriber access to UTRAN is rejected due to subscriber count access restriction. 0x160 coll_isho_c A new procedure from a different system collided with an ongoing procedure. external cause #14 is sent to the MS.) Id:0900d805809551ce DN05148836 Issue 2-2 . The ongoing process is interrupted and the relocation is performed. The ongoing process is interrupted and the new is performed. Table 867 548 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. external cause #13 is sent to the MS. The ongoing process is interrupted and the service request is performed. 0x157 subs_cnt_rest_2g_15_c The subscriber access to GERAN is rejected due to subscriber count access restriction. 0x15D coll_relocation_c A Relocation collided with an ongoing procedure. 0x14F plmn_rest_3gto3g_12_c UMTS subscriber access to UTRAN is rejected due to the local access restriction. 0x15E coll_og_relocation_c An outgoing Relocation collided with an ongoing procedure. external cause #12 is sent to the MS. because there is no response to the authentication and ciphering request. 0x159 subs_cnt_rest_3g_12_c The subscriber access to UTRAN is rejected due to subscriber count access restriction. 0x153 subs_cnt_rest_2g_11_c The subscriber access to GERAN is rejected due to subscriber count access restriction. The ongoing process is interrupted and the outgoing relocation is performed. external cause #11 is sent to the MS.Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Traffica Reference Guide for SGSN Direct Interface Value Error code Explanation 0x14D plmn_rest_3gto2g_15_c UMTS subscriber access to GERAN is rejected due to the local access restriction. external cause #11 is sent to the MS. 0x168 coll_iu_reset_c An Iu-reset request collided with an ongoing procedure. external cause #12 is sent to the MS.Traffica Reference Guide for SGSN Direct Interface Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Value Error code Explanation 0x165 rel_due_sgsn_c Case 1: In Relocation Required message the received target RNC identifies the confusing PAPU identifier (possible configuration error). the ongoing procedure is interrupted 0x178 subs_cnt_rest_cam_11_c The subscriber access is rejected due to camel subscriber count access restriction. external cause #13 is sent to the MS. 0x167 no_rsp_co_process_c The timer has expired while waiting for answer from the co-process.060). 0x179 subs_cnt_rest_cam_12_c The subscriber access is rejected due to camel subscriber count access restriction. The ongoing process is interrupted. GMGPRB changes this cause code to dns_failure_c.Case 2: Internal error in GMGPRB.no subscription. The ongoing process is interrupted and the Iu reset is performed. Optional feature 0x172 Gtp_res_unavail RAB release procedure initiated by RNC when it has received GTP-Error indication 0x177 pos_method_failure Positioning failed or timer for location request expired 0x17F coll_attach_dif_p_c Attach and another task from different PAPU collided with each other 0x180 coll_detach_dif_p_c Detach and another task from different PAPU collided with each other 0x181 coll_ra_upd_dif_p_c Routing area update and another task from different PAPU collided with each other 0x182 coll_og_rau_dif_p_c Outgoing RA update and another task from different PAPU collided with each other 0x183 coll_serv_req_dif_p_c Service request and another task from different PAPU collided with each other 0x184 coll_mo_act_dif_p_c MO activation and another task from different PAPU collided with each other 0x185 coll_deact_dif_p_c Deactivation and another task from different PAPU collided with each other 0x186 coll_mod_dif_p_c Modification and another task from different PAPU collided with each other 0x187 coll_reloc_dif_p_c Relocation and another task from different PAPU collided with each other 0x188 coll_og_reloc_dif_p_c Outgoing relocation and another task from different PAPU collided with each other 0x173 apn_access_denied_c Cause code (222) returned by the GGSN (see 3GPP TS 29. 0x16D coll_iu_release_c An Iu-release procedure collided with an ongoing procedure The ongoing process is interrupted and the Iu release is performed 0x16E rnc_unsup_rab_mod RNC initiated RAB modification although RNC doesn't support RAB modification 0x170 dns_failure Inter SGSN RAU is received with cause code unknown_dns_c. "subs_cnt_rest_cam_13_c" Table 867 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. APN authentication fails .. 0x17A subs_cnt_rest_cam_13_c The subscriber access is rejected due to camel subscriber count access restriction. except if it is a detach or a PDP context deactivation.) DN05148836 Issue 2-2 Id:0900d805809551ce 549 . Ongoing procedure information is missed. Table 867 550 Possible values for Sgsn_Sms_Rtt_Cause_Cause and Sgsn_Rtt_Cause_Cause (Cont. external cause #14 is sent to the MS. 0x17E cap_unknown_apn_c Release GPRS operation is received from the SCP. The SCP orders the SGSN to release the GPRS session and/or the PDP contexts. 0x17C subs_cnt_rest_cam_15_c The subscriber access is rejected due to camel subscriber count access restriction.Appendix Possible values for Sgsn_Sms_Rtt_Cause_Cause and Traffica Reference Guide for SGSN Direct Interface Value Error code Explanation 0x17B subs_cnt_rest_cam_14_c The subscriber access is rejected due to camel subscriber count access restriction.) Id:0900d805809551ce DN05148836 Issue 2-2 . The cause code is sent to GMGPRB in the ssf_release_context_ind_s and ssf_release_gprs_ind_s messages. 0x17D cs_ps_coordination_c SGSN may not able to provide service to the UE due MOCN feature SG01179. Wrong APN settings in mobile. external cause #15 is sent to the MS.