dn99576987x4x0xen

Traffica Reference Guide for FixedCircuit Switched CoreDN99576987 Nokia Corporation 1 (34)Issue 4-0 en Nokia Proprietary and Confidential

Traffica Reference Guide for Fixed Circuit Switched Core

The information in this documentation is subject to change without notice and describes onlythe product defined in the introduction of this documentation. This documentation is intended

for the use of Nokia's customers only for the purposes of the agreement under which thedocumentation is submitted, and no part of it may be reproduced or transmitted in any form ormeans without the prior written permission of Nokia. The documentation has been prepared tobe used by professional and properly trained personnel, and the customer assumes fullresponsibility when using it. Nokia welcomes customer comments as part of the process ofcontinuous 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 cannot be considered bindingbut shall be defined in the agreement made between Nokia and the customer. However, Nokiahas made all reasonable efforts to ensure that the instructions contained in the documentationare adequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the documentation.Nokia's liability for any errors in the documentation is limited to the documentary correction oferrors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL(INCLUDING MONETARY LOSSES), that might arise from the use of this documentation orthe information in it.This documentation and the product it describes are considered protected by copyrightaccording to the applicable laws.NOKIA logo is a registered trademark of Nokia Corporation.Other product names mentioned in this documentation may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright Nokia Corporation 2005. All rights reserved.2 (34) Nokia Corporation DN99576987Nokia Proprietary and Confidential Issue 4-0en

ContentsContents 3

List of tables 4

1 About this document 51.1 Where to find more information 51.2 Terms 61.3 Abbreviations 8

2 Change information 9

3 Real-time monitoring 113.1 Clear Code Matrix 113.2 Real-time graphs 193.2.1 Graph Categories 193.2.2 Graph Sets 20

4 Internal Data Structure 23DN99576987 Nokia Corporation 3 (34)Issue 4-0 en Nokia Proprietary and Confidential


List of tablesTable 1. Traffica terms 6Table 2. Abbreviations 8Table 3. The predefined CCMA structure: the Call Answered node. 12Table 4. Columns in Traffic News, fields in Traffica and corresponding fields in

CDR 234 (34) Nokia Corporation DN99576987Nokia Proprietary and Confidential Issue 4-0en

About this document1 About this documentTraffica Reference Guide for Fixed Circuit Switched Core offers referencematerial related to the real-time monitoring of traffic data. It is a convenientreference for the Traffica system administrator as well as the Traffica user.

The Traffica Reference Guide covers the default Traffica workspace for fixednetworks and certain aspects of Traffic News, and the Internal Data Structure(IDS).

This document relates to Traffica release Z3.1, and Fixed Network releases,starting from G2.0.

1.1 Where to find more information

If you are unfamiliar with any of the terms used in this manual, refer to Glossary.

For further information on Traffica, refer to:

Nokia NetAct Traffica Z4 Functionality Description Traffica Principles Administering TrafficaFor information on other Nokia network monitoring tools than Traffica, refer tothe following manuals:

Reporter Principles, DN9784605

Monitor Principles, DN98614174

A significant part of Traffica functionality is based on clear codes. For detailedclear code descriptions, refer to:

DX200 Clear Code List

For detailed descriptions of the data in the CDR, refer to:

Data Formats of Charging; CDR, CAG 27322DN99576987 Nokia Corporation 5 (34)Issue 4-0 en Nokia Proprietary and Confidential


1.2 TermsThe following table presents the most important Traffica terms.

Table 1. Traffica terms

Concept Description

CCMA (Clear Code Matrix) A tree structure which consists of nodes and counters, andfunctions as a data storage for the counter values post-processed from RTTs.When an RTT arrives in Traffica, the CCMA is scannedthrough and the counters are updated.For information on the CCMA, refer to Traffica Principles. Fordetailed information on the predefined Nokia CCMA, seechapter 3.1Clear Code Matrix.

Clear code Code that identifies the reason why a call ended.Clear codes are divided into four categories: 0 - 3FF, Normal release 400 - 7FF, Internal error 800 - BFF, External error C00 - FFF, Subscriber errorFor detailed clear code descriptions, refer to DX200 ClearCode List.

Database A data storage for all RTTs in the TNES. The database isautomatically cleaned up and oldest data is deleted.Database capacity depends on the size of the hard disk andthe volume of network traffic.To access the database, use Traffic News.For more information, see Administering Traffica.

Internal Data Structure (IDS) Traffica forwards an RTT report as such into Trafficas IDS.Once the RTT report data is in the IDS, the fields in the reportare mapped with corresponding IDS fields. Traffica uses thedata in the RTT reports, which are in the IDS, for updating theCCMA. Traffica stores the reports from the IDS into thedatabase. For more information, see chapter 4Internal DataStructure.

IDS field An IDS field is mapped with a corresponding field in an RTTreport. Consequently, the contents of an IDS field areidentical with the contents of an RTT report field.

Network Element (NE) General term, used for all NEs that Traffica can be connectedto, for example, Mobile Switching Centre (MSC), FixedSwitching Centre (FSC) or SGSN.6 (34) Nokia Corporation DN99576987Nokia Proprietary and Confidential Issue 4-0en

About this document

Table 1. Traffica terms (Continued)RTT (Real-time Traffic)report

RTT reports is a general term used for the real-time trafficreports that are generated by NEs and issued to theconnected TNES. The term also includes redirected RTTreports that are transferred from a TNES to a TS.An RTT report can contain, for example, the followinginformation: Call start and end time Cause why the call ended Clear code A and B subscribers identities Incoming and outgoing CGR, PCM and TSL In the GSM networks, the RTT report contains also the

mobile identities (IMEI), the dialled digits, incoming andoutgoing BSC, LAC and the cell

Time Class A root item in the CCMA tree structure which acts as acontainer of the time resolution(s) and CCMA members.

Time resolution A time resolution gives meaning to a Time Class. A timeresolution defines how long a time the counters in thatparticular tree branch are accumulated before the countersare reset and how many time slices are stored in the memoryas history data.When you define a time resolution you define two things: theduration of one time slice and the number of these timeslices. The duration of one time slice can be, for example,one second, minute, or hour. The duration of the time slicedefines how long the data accumulates.Time resolutions are user-definable, for example, 1*1 day or30*1 minute.Time resolution is a range of time slices, and for the user it istypically visualised as a range of bars in a graph.During the time defined in the time resolution, the counters inthe current time slice are updated in real-time. When thedefined time for one time slice is over, the time slice is eitherstored as historical data or deleted, and a new time slice isstarted.

Traffica Network ElementServer (TNES)

A TNES is the Traffica that is connected to an NE.TNESs collect the RTT reports and these reports are storedinto the Traffica database.

Traffica Server (TS) A central point in the Traffica system, and is connected to allTNESs. Acts as a server for Traffica clients.

Concept DescriptionDN99576987 Nokia Corporation 7 (34)Issue 4-0 en Nokia Proprietary and Confidential


1.3 AbbreviationsThe following table lists the Traffica-specific abbreviations used in this manual.

Table 2. Abbreviations

Abbreviation Explanation

CDR Charging Record (Call Detail Record)CCMA Clear Code Matrix

IDS Internal Data Structure

RTT (report) Real-time Traffic (report)8 (34) Nokia Corporation DN99576987Nokia Proprietary and Confidential Issue 4-0en

Change information2 Change informationThis chapter lists changes between releases in this document.

In the previous release (Z3.1) The chapter Internal alarms was removed from this document. The

available internal alarms and their configuration in Traffica are describedin chapter Internal alarms in Administering Traffica.

The chapter Query conditions in Traffic News was removed since theTraffic News user interface and the Help provide enough information formaking queries.DN99576987 Nokia Corporation 9 (34)Issue 4-0 en Nokia Proprietary and Confidential

Traffica Reference Guide for Fixed Circuit Switched Core10 (34) Nokia Corporation DN99576987Nokia Proprietary and Confidential Issue 4-0en

Real-time monitoring3 Real-time monitoring3.1 Clear Code Matrix

Traffica contains a Nokia predefined counter tree, the Clear Code Matrix(CCMA). There are three Time Classes in the CCMA: NOKIA_FSC_Daily,NOKIA_FSC_24h, and NOKIA_FSC_30min. They all have a similar structure.

The Time Class NOKIA_FSC_Daily consists of one time resolution, NOKIADaily, and the data is collected during the current day, starting from midnightwhen the counters are initialised, up to the present moment.

The Time Class NOKIA_FSC_24h collects data for the 24 hours preceding thelatest 30 minutes, in one-hour slices and stores the data in the memory.

NOKIA_FSC_30min collects data for the latest 30 minutes in one-minute slicesand stores the data in the memory.

The following table explains, node by node, the contents of the Time ClassNOKIA_FSC_Daily in the predefined Nokia CCMA. The other two TimeClasses, NOKIA_FSC_24h and NOKIA_FSC_30min, are smaller versions of theDaily Time Class, which means that you can find the explanations for the CCMAmembers in the 24-hour and 30-minute Time Classes in the explanations givenfor the Time Class NOKIA_FSC_Daily.

Notice that if intermediate charging is in use in the switch, Traffica can receivemore than one RTT report from one call. However, only the last RTT report, thatis the RTT report that is generated at the end of the call, affects the default NokiaCCMA. This is defined in the CCMA so that in the Expression properties for RTTReport the clear code 0xF is excluded. If you want the same function in your ownTime Classes, you should create the same kind of Expression into the root of yourown Time Classes.

The first items in the path are always the Time Class NOKIA_FSC_Daily andRTT Report.DN99576987 Nokia Corporation 11 (34)Issue 4-0 en Nokia Proprietary and Confidential

Traffica Reference Guide for Fixed Circuit Switched CoreTable 3. The predefined CCMA structure: the Call Answered node.

Path for the CCMA member Explanation

/ All Reports Counter Counts the number of all calls and call attempts.

/ Call Duration An Expression node which calculates a call duration in seconds.

/ Call Duration / Sum

Sums the duration of all calls which were answered and ended.

/ Clear Code Counts the number of calls and call attempts which have ended in anyclear code.

/ Clear Code / Counter

Counts the number of all occurred clear codes.

/ Clear Code / Clear Codes 1-3FF

A Group node which evaluates as true a call or a call attempt which ends with a clear code within the range 1-3FF in hex

/ Clear Code / Clear Codes 1-3FF / Counter

Counts the number of calls and call attempts which have ended with aclear code between 1-3FF in hex.

/ Clear Code / Clear Codes 400-FFF

A Group node which evaluates as true a call or call attempt which ends with a clear code within the range 400-FFF in hex

/ Clear Code / Clear Codes 400-FFF / Counter

Counts the number of calls or call attempts which ended with a clearcode between 400-FFF in hex.

/ Clear Code / Clear Codes 400-7FF

A Group node which evaluates as true a call or a call attempt which ends with a clear code within the range 400-7FF in hex.

/ Clear Code / Clear Codes 400-7FF / Counter

Counts the number of calls and call attempts that ended in a clear codewithin the range 400-7FF.

/ Clear Code / Clear Codes 800-BFF

A Group node which evaluates as true a call or a call attempt which ends with a clear code within the range 800-BFF in hex

/ Clear Code / Clear Codes 800-BFF / Counter

Counts the number of calls and call attempts that ended in a clear codewithin the range 800-BFF.

/ Clear Code / Clear Codes C00-FFF

A Group node which evaluates as true a call or a call attempt which ends with a clear code within the range C00-FFF in hex

/ Clear Code / Clear Codes C00-FFF / Counter

Counts the number of calls and call attempts that ended in a clear codewithin the range C00-FFF.12 (34) Nokia Corporation DN99576987Nokia Proprietary and Confidential Issue 4-0en

Real-time monitoring

Table 3. The predefined CCMA structure: the Call Answered node./ Clear Code / Clear Code Vector

A Vector node for each clear code.

/ Clear Code / Clear Code Vector / Counter

Counts the number of calls and call attempts for each clear code.

/ Clear Code / Clear Code Vector / Circuit Group Vector

A circuit group vector node for each clear code.

/ Clear Code / Clear Code Vector / Circuit Group Vector / Counter (A Side)

Counts the number of calls and call attempts that have ended in a certainclear code in a certain circuit group (A subscriber).

/ Clear Code / Clear Code Vector / Circuit Group Vector / Counter (B Side)

Counts the number of calls and call attempts that have ended in a certainclear code in a certain circuit group (B subscriber).

/ Clear Code / Clear Code Vector / Circuit Group Vector / PCM Vector

A Vector node for each PCM under each circuit group.

/ Clear Code / Clear Code Vector / Circuit Group Vector / PCM Vector / Counter (A Side)

Counts the number of calls and call attempts that have ended in a certainclear code in a certain PCM under a certain circuit group (A subscriber).

/ Clear Code / Clear Code Vector / Circuit Group Vector / PCM Vector / Counter (B Side)

Counts the number of calls and call attempts that have ended in a certainclear code in a certain PCM under a certain circuit group (B subscriber).

/ Clear Code / Clear Code Vector / Circuit Group Vector / PCM Vector / TSL Vector

A Vector node for each time slot under each PCM under each CGR.

Path for the CCMA member ExplanationDN99576987 Nokia Corporation 13 (34)Issue 4-0 en Nokia Proprietary and Confidential


Table 3. The predefined CCMA structure: the Call Answered node./ Clear Code / Clear Code Vector / Circuit Group Vector / PCM Vector / TSL Vector / Counter (A Side)

Counts the number of calls and call attempts that have ended in a certainclear code in a certain time slot in a certain PCM under a certain circuitgroup (A subscriber).

/ Clear Code / Clear Code Vector / Circuit Group Vector / PCM Vector / TSL Vector / Counter (B Side)

Counts the number of calls and call attempts that have ended in a certainclear code in a certain time slot in a certain PCM under a certain circuitgroup (B subscriber).

/ Circuit Group Vector A Vector node for each circuit group.

/ Circuit Group Vector / Counter (A Side)

Counts the number of calls or call attempts for A subscriber circuitgroups.

/ Circuit Group Vector / Counter (B Side)

Counts the number of calls or call attempts for B subscriber circuitgroups.

/ Circuit Group Vector / Clear Code Vector

A clear code vector node for each circuit group.

/ Circuit Group Vector / Clear Code Vector / Counter (A Side)

Counts the number of calls and call attempts that have ended in a certainclear code in certain circuit group (A subscriber).

/ Circuit Group Vector / Clear Code Vector / Counter (B Side)

Counts the number of calls and call attempts that have ended in a certainclear code in certain circuit group (B subscriber).

/ Teleservice Vector A Vector node for each teleservice.

/ Teleservice Vector / Counter

Counts the number of calls where a teleservice has been used.

/ Teleservice Vector / Clear Code Vector

A clear code vector node for each teleservice.

/ Teleservice Vector / Clear Code Vector / Counter

Counts the number of clear codes for each teleservice.

/ Bearer Service Vector A Vector node for each bearer service.

Path for the CCMA member Explanation14 (34) Nokia Corporation DN99576987Nokia Proprietary and Confidential Issue 4-0en


Table 3. The predefined CCMA structure: the Call Answered node./ Bearer Service Vector / Counter

Counts the number of calls where a bearer service has been used.

/ Bearer Service Vector / Clear Code Vector

A clear code vector node for each bearer service.

/ Bearer Service Vector / Clear Code Vector / Counter

Counts the number of clear codes for each bearer service.

/ Service Vector A Vector node for each service.

/ Service Vector / Counter

Counts the number of calls where a service has been used.

/ Service Vector / Clear Code Vector

A clear code vector node for each service.

/ Service Vector / Clear Code Vector / Counter

Counts the number of clear codes for each service.

/ Subscriber Category Exists An Expression node which evaluates as true a call or a call attemptwhere a subscriber category exists.

/ Subscriber Category Exists / Subscriber Category Vector

A Vector node that collects all calls and call attempts of the subscribersthat exist in different subscriber categories.

/ Subscriber Category Exists / Subscriber Category Vector / Counter

Counts the number of calls for each subscriber category.

/ Subscriber Category Exists / Subscriber Category Vector / Clear Code Vector

A clear code vector node for each subscriber category.

/ Subscriber Category Exists / Subscriber Category Vector / Clear Code Vector / Counter

Counts the number of clear codes for each subscriber category.

/ Subscriber Type Vector A Vector node for each subscriber type.

/ Subscriber Type Vector / Counter

Counts the number of calls where a subscriber type has been used.

/ Subscriber Type Vector / Clear Code Vector

A clear code vector node for each subscriber type.



Table 3. The predefined CCMA structure: the Call Answered node./ Subscriber Type Vector / Clear Code Vector / Counter

Counts the number of clear codes for each subscriber type.

/ Facility Code Vector A Vector node for each facility.

/ Facility Code Vector / Counter (A Side)

Counts the number of calls or call attempts for each facility (Asubscriber).

/ Facility Code Vector / Counter (B Side)

Counts the number of calls or call attempts for each facility (Asubscriber).

/ Facility Code Vector / Clear Code Vector

A clear code vector node for each facility.

/ Facility Code Vector / Clear Code Vector / Counter (A Side)

For each facility, counts the number of calls and call attempts that haveended in a certain clear code (A subscriber).

/ Facility Code Vector / Clear Code Vector / Counter (B Side)

For each facility, counts the number of calls and call attempts that haveended in a certain clear code (B subscriber).

/ Facility Type Vector A Vector node for each facility type.

/ Facility Type Vector / Counter

Counts the number of calls or call attempts for each facility type.

/ Facility Type Vector / Clear Code Vector

A clear code vector node for each facility type.

/ Facility Type Vector / Clear Code Vector / Counter

For each facility type, counts the number of calls and call attempts thathave ended in a certain clear code.

/ Additional Data Vector A Vector node for each additional data.

/ Additional Data Vector / Counter

Counts the number of calls where the additional data field has beenused.

/ Additional Data Vector / Clear Code Vector

A clear code vector node for each additional data field.

/ Additional Data Vector / Clear Code Vector / Counter

Counts the number of clear codes for each additional data field.

/ PBX Head_8 Vector A Vector node for the first eight digits of the PBX identifier (PBX header).



Table 3. The predefined CCMA structure: the Call Answered node./ PBX Head_8 Vector / Counter

Counts the number of calls where the PBX header has been used.

/ PBX Head_8 Vector / Clear Code Vector

A clear code vector node for each PBX header.

/ PBX Head_8 Vector / Clear Code Vector / Counter

Counts the number of clear codes for each PBX header.

/ Centrex Internal Call An expression node which evaluates as true a call or a call attempt whichis a Centrex Internal Call (value 00002000H in the additional data field)

/ Centrex Internal Call / PBX Head_8 Vector

A Vector node for the PBX header (first eight digits of the PBX identifier)of a Centrex internal call.

/ Centrex Internal Call / PBX Head_8 Vector / Counter

Counts the number of clear codes for each PBX header in Centrexinternal calls.

/ Centrex Internal Call / PBX Head_8 Vector / Clear Code Vector

A clear code vector node for each PBX header in Centrex internal calls.

/ Centrex Internal Call / PBX Head_8 Vector / Clear Code Vector / Counter

Counts the number of clear codes for each PBX header in Centrexinternal calls.

/ Carrier Access Code A Presence node for all calls and call attempts where a carrier accesscode was used.

/ Carrier Access Code / Carrier Access Code Vector

A Vector node for each carrier access code.

/ Carrier Access Code / Carrier Access Code Vector / Counter

Counts the number of calls or call attempts for each carrier access code.

/ Carrier Access Code / Carrier Access Code Vector / Call Duration

An Expression node which calculates a call duration in seconds for eachcarrier access code.



Table 3. The predefined CCMA structure: the Call Answered node./ Carrier Access Code / Carrier Access Code Vector / Call Duration / Sum

Sums the duration of calls for each carrier access code.

/ Carrier Access Code / Carrier Access Code Vector / Clear Code Vector

A clear code vector node for each carrier access code.

/ Carrier Access Code / Carrier Access Code Vector / Clear Code Vector / Counter

For each carrier access code, counts the number of calls and callattempts that have ended in a certain clear code.

/ Carrier Access Code / CAC in Dialling

An Expression node which evaluates as true a call or a call attemptwhere the CAC can be obtained from the subscriber dialling (value

00000080H in the additional data field)./ Carrier Access Code / CAC in Dialling / Carrier Access Code Vector

A Vector node for each carrier access code that was obtained from thesubscriber dialling.

/ Carrier Access Code / CAC in Dialling / Carrier Access Code Vector / Counter

For each CAC, counts the number of call attempts where the CAC wasobtained from subscriber dialling.

/ Carrier Access Code / CAC Preselected

An Expression node which evaluates as true a call or a call attemptwhere the CAC was preselected (value 00000100H in the additional data

field)./ Carrier Access Code / CAC Preselected / Carrier Access Code Vector

A Vector node for each carrier access code that was preselected.

/ Carrier Access Code / CAC Preselected / Carrier Access Code Vector / Counter

For each carrier access code, counts the number of call attempts whereCAC was preselected.



3.2 Real-time graphsNokia supplies predefined Graph Categories and Sets for fixed networks. Thedivision of graphs into Categories and Sets facilitates fast access to the data.

Each predefined Nokia Graph Set consists of a number of graphs. The actualcontents of the graphs are given in the Traffica user interface. To access thecontents information, place the cursor on the graph title. A ToolTip appears withinformation about the graph contents.

To find out which part of the CCMA provides the data for the graph, click withthe right mouse button on the graph to open a popup menu and select Properties.

3.2.1 Graph Categories

All Graph Categories consist of a number of Graph Sets, which, in turn, includea number of graphs.

Traffica release Z3F contains the following Graph Categories:

User Set Repository

NOKIA FSC Daily

NOKIA FSC 24 h

NOKIA FSC 30 min

User Set Repository includes all Nokia predefined Graph Sets. When you selectSet Repository, all Graph Sets are listed in the options menu and, thus, you canaccess all graphs in all Categories. The fact that a Graph Set belongs to the GraphCategory NOKIA FSC 24 h is indicated by the character h in brackets, (h).Similarly, when a Graph Set belongs to the Graph Category NOKIA FSC 30 min,it is indicated by the character m in brackets, (m).

The graphs in the Sets of the Graph Category NOKIA FSC Daily are based on theCCMA Time Class NOKIA FSC Daily. The Time Class NOKIA FSC Dailyaccumulates the data starting from midnight when the counters are initialised. Inthe CCMA, NOKIA FSC Daily is defined as follows: count = 1, interval = 86400seconds, which equals to 24 hours. In other words, there is one counter for 24hours.

The graphs in the Sets of the Graph Category NOKIA FSC 30 min are based onthe first time resolution of the CCMA Time Class NOKIA_FSC_30min+24h.This time resolution is defined as follows: count = 30, interval = 60, that is, 30times one minute. The data in the graphs is presented in one-minute slices.DN99576987 Nokia Corporation 19 (34)Issue 4-0 en Nokia Proprietary and Confidential


The graphs in the Sets of the Category NOKIA FSC 24h are based on the secondtime resolution of the CCMA Time Class NOKIA_FSC_30min+24h. This time

resolution is defined as follows: count = 24, interval = 3600, that is, 24 times one-hour counters. The data in the graphs is presented in one-hour slices.

User Set Repository is reserved for users own Graph Sets.

3.2.2 Graph Sets

The following sections give hints about the usage of some of the Graph Sets.

NOKIA General

Graphs in this Graph Set can be used for the following purposes:

Technical Management: to study, for example, the amount of traffic, andthe number of successful and failed calls.

Dimensioning and Planning: to study the amount of traffic.

Fault Analysis: to study the problems in the normal traffic flow.

Top Management: use this information combined with Network DataWarehouse and long term data.

NOKIA Clear Codes

Graphs in this Graph Set show the number and percentage of certain clear coderanges. Fault Analysis can use these graphs to track certain faults or to monitortheir frequency.

NOKIA Services

Graphs in this Graph Set show the number calls and call attempts that have had acertain service in use, and the clear codes for those calls. These graphs can beused, for example, to see the number of the services used and to check how wella certain service succeeds.

NOKIA Circuit Groups

Graphs in this Graph Set show the number calls and call attempts that haveoccurred in the incoming and outgoing circuit groups, and the clear codes forthose calls. These graphs can be used, for example, to check how well a certaincircuit group functions. If there are problems in a certain circuit group, you cansee the clear codes it generates.20 (34) Nokia Corporation DN99576987Nokia Proprietary and Confidential Issue 4-0en


NOKIA Clear Code CGR PCM TSLGraphs in this Graph Set are intended for fault finding. The graph Number ofClear Code X / CGR Y / PCM Z / TSL is available only in the Graph CategoryNOKIA Daily. Other Categories have a similar graph, except for that TSL is notincluded. The linked graphs show how a selected clear code occurs in the CGRs,PCMs and TSLs.

NOKIA Facility Codes and Types

Graphs in this Graph Set show the facility codes and facility types that have beenused by the calling subscribers, the number of these calls, and the clear codes forthose calls.

NOKIA Subscriber Categories and Types

Graphs in this Graph Set show the number of calls and call attempts made by thecalling subscribers in the given subscriber categories, or of the given subscribertype, and the clear codes for those calls.

NOKIA Carrier Access Codes

Graphs in this Graph Set show the number of calls and call attempts that havebeen made by using the listed carrier access codes, the clear codes for those calls,and their average duration.

These graphs can be used to study how much a certain CAC is used, how callsusing a certain CAC succeed, and the average duration of calls using a certainCAC.

NOKIA Carrier Access Code Selection

Graphs in this Graph Set show the Carrier Access Codes dialled by thesubscribers, and their numbers.

This information is valuable for marketing personnel.

NOKIA PBX Calls

Graphs in this Graph Set show the number of PBX and Centrex Internal calls, andhow these calls are succeeding.DN99576987 Nokia Corporation 21 (34)Issue 4-0 en Nokia Proprietary and Confidential

Internal Data Structure4 Internal Data StructureThe following table lists the fields in Traffica and their correspondences to thefields in CDR. To find the explanations for Traffica fields, search for thecorresponding field in the Data Formats of Charging; CDR document.

Table 4. Columns in Traffic News, fields in Traffica and corresponding fieldsin CDR

Columns in TrafficNews Fields in Traffica

Explanation /Corresponding fields inCDR document

Fnw_Dr_Id Trafficas internalinformation

Sub ID Fnw_Sub_Id Trafficas internalinformation: identifier of thereport

Establishment Code ofRecord Ext Bits 0-1

Fnw_Establishment_Code_Of_Record_Ext CDR field: Establishmentcode of record

Establishment Code ofRecord Bits 0-31

Fnw_Establishment_Code_Of_Record CDR field: Establishmentcode of record

Call ID Fnw_Call_Id CDR field: Call identifier

Report Count Fnw_Report_Count Shows the ordinal numberof the call. If an RTT reportis not generated of a call,then the counter values arenot consecutive in Traffica.CDR field: Order number ofgenerated call detailedrecord

Record Index of OneConnection

Fnw_Record_Index_Of_One_Connection CDR field: Record index ofone connection

Service Event Identifier Fnw_Service_Event_Identifier CDR field: Service eventidentifierDN99576987 Nokia Corporation 23 (34)Issue 4-0 en Nokia Proprietary and Confidential


Table 4. Columns in Traffic News, fields in Traffica and corresponding fieldsin CDR (Continued)A Direction Number Fnw_A_Direction_Number A subscribers numberCDR field: Callingsubscriber

Fnw_A_Direction_Number_Head_1 The first digit in the Asubscribers number

Fnw_A_Direction_Number_Head_2 The first two digits in the Asubscribers number

Fnw_A_Direction_Number_Head_3 The first three digits in the Asubscribers number

Fnw_A_Direction_Number_Head_4 The first four digits in the Asubscribers number

Fnw_A_Direction_Number_Head_5 The first five digits in the Asubscribers number

Fnw_A_Direction_Number_Head_8 The first eight digits in the Asubscribers number

A Type Fnw_A_Type CDR field: Type of callingsubscriber

A Category Fnw_A_Category CDR field: Category ofcalling subscriber

A Facility Code Fnw_A_Facility_Code CDR field: Facility codeused by calling subscriber

A Used Facility Type Fnw_A_Used_Facility_Type CDR field: Facility type usedby calling subscriber

A Facility Code 1 Fnw_A_Facility_Code_1 CDR field: Facility codesused by calling subscriber(4 preceding)





Explanation /Corresponding fields inCDR document24 (34) Nokia Corporation DN99576987Nokia Proprietary and Confidential Issue 4-0en

Internal Data Structure

Table 4. Columns in Traffic News, fields in Traffica and corresponding fieldsin CDR (Continued)Used Services Fnw_Used_Services CDR field: Service used

Authorization Code Fnw_Authorization_Code CDR field: Authorizationcode

Identification Number Fnw_Identification_Number CDR field: Identificationnumber

Carrier Access Code Fnw_Carrier_Access_Code Carrier access code for thenetwork operator usedCDR field: Carrier accesscode

Fnw_Carrier_Access_Code_Head The first six digits in thecarrier access code

B Direction Number Fnw_B_Direction_Number B subscribers numberCDR field: Called subscriber

Fnw_B_Direction_Number_Head_1 The first digit in the Bsubscribers number

Fnw_B_Direction_Number_Head_2 The first two digits in the Bsubscribers number

Fnw_B_Direction_Number_Head_3 The first three digits in the Bsubscribers number

Fnw_B_Direction_Number_Head_4 The first four digits in the Bsubscribers number

Fnw_B_Direction_Number_Head_5 The first five digits in the Bsubscribers number

Fnw_B_Direction_Number_Head_8 The first eight digits in the Bsubscribers number

Translated Number Fnw_Translated_Number CDR field: Translatednumber

B Facility Code Fnw_B_Facility_Code CDR field: Facility codeused by called subscriber

B Used Facility Type Fnw_B_Used_Facility_Type CDR field: Facility type usedby called subscriber

B Facility Code 1 Fnw_B_Facility_Code_1 CDR field: Facility codesused by called subscriber (4preceding)


Explanation /Corresponding fields inCDR documentDN99576987 Nokia Corporation 25 (34)Issue 4-0 en Nokia Proprietary and Confidential


Table 4. Columns in Traffic News, fields in Traffica and corresponding fieldsin CDR (Continued)B Facility Code 2 Fnw_B_Facility_Code_2 CDR field: Facility codesused by called subscriber (4preceding)



Forwarding Subscriber Fnw_Forwarding_Subscriber CDR field: Forwardingsubscriber

Forwarding AdditionalNumber

Fnw_Forwarding_Additional_Number CDR field: Forwardingadditional number

Call Forwarding Counter Fnw_Call_Forwarding_Counter CDR field: Call forwardingcounter

Call Start Time Fnw_Call_Start_Time CDR field: Start time of call

Fnw_Call_Start_Date CDR field: Start time of call

Call End Time Fnw_Call_End_Time CDR field: End time of call

Fnw_Call_End_Date CDR field: End time of call

Charged Call Time Fnw_Charged_Call_Time CDR field: Charged call timein seconds

A CGR Fnw_A_Cgr CDR field: Number ofincoming circuit group

A PCM Fnw_A_Pcm CDR field: Incoming circuit

A TSL Fnw_A_Tsl CDR field: Incoming circuit

B CGR Fnw_B_Cgr CDR field: Number ofoutgoing circuit group

B PCM Fnw_B_Pcm CDR field: Outgoing circuit

B TSL Fnw_B_Tsl CDR field: Outgoing circuit

Location Information ofBase Station

Fnw_Location_Information_Of_Base_Station CDR field: Locationinformation of base station

Charging Pulse Count Fnw_Charging_Pulse_Count CDR field: Charging pulses




Table 4. Columns in Traffic News, fields in Traffica and corresponding fieldsin CDR (Continued)Generated Pulse Count Fnw_Generated_Pulse_Count CDR field: Generatedpulses

Received Pulse Count Fnw_Received_Pulse_Count CDR field: Received pulses

Received Pulses Classifby Tariff Type 1

Fnw_Received_Pulses_Classif_By_Tariff_Type_1 CDR field: Received pulsesclassified by tariff type











Received Pulses Adviceof Charge Bits 0-5

Fnw_Received_Pulses_Advice_Of_Charge CDR field: Received AOCpulses

Execution of Charging Fnw_Execution_Of_Charging CDR field: Execution ofcharging

Main Charging Zone Fnw_Main_Charging_Zone CDR field: Main chargingzone

Charged Call Time inMain Chrg Zone 1

Fnw_Charged_Call_Time_In_Main_Chrg_Zone_1 CDR field: Charged call timein main charging zone







First Additional ChargingZone

Fnw_First_Additional_Charging_Zone CDR field: 1st additionalcharging zone

Charged Call Time in 1stAdd Chrg Zone 1

Fnw_Charged_Call_Time_In_1st_Add_Chrg_Zone_1

CDR field: Charged call timein 1st additional chargingzone




Table 4. Columns in Traffic News, fields in Traffica and corresponding fieldsin CDR (Continued)Charged Call Time in 1stAdd Chrg Zone 2









Second AdditionalCharging Zone

Fnw_Second_Additional_Charging_Zone CDR field: 2nd additionalcharging zone

Charged Call Time in 2ndAdd Chrg Zone 1

Fnw_Charged_Call_Time_In_2nd_Add_Chrg_Zone_1

CDR field: Charged call timein 2nd additional chargingzone










Third Additional ChargingZone

Fnw_Third_Additional_Charging_Zone CDR field: 3rd additionalcharging zone

Charged Call Time in 3rdAdd Chrg Zone 1

Fnw_Charged_Call_Time_In_3rd_Add_Chrg_Zone_1

CDR field: Charged call timein 3rd additional chargingzone













Table 4. Columns in Traffic News, fields in Traffica and corresponding fieldsin CDR (Continued)Traffic Category Fnw_Traffic_Category CDR field: Traffic category

Clear Code Fnw_Clear_Code CDR field: Clear code of call

PBX Identifier Fnw_Pbx_Identifier CDR field: Pbx identifier

Fnw_Pbx_Identifier_Head_8 The first eight digits in thePbx IdentifierCDR field: Pbx identifier

Tariff Type of GeneratedPulses

Fnw_Tariff_Type_Of_Generated_Pulses CDR field: Tarifftype/generated pulses

Tariff Type of ReceivedPulses 1

Fnw_Tariff_Type_Of_Received_Pulses_1 CDR field: Tarifftype/received pulses











Tariff Type of Sent Pulses1

Fnw_Tariff_Type_Of_Sent_Pulses_1 CDR field: Tariff type/sentpulses











Bearer Service Fnw_Bearer_Service CDR field: Bearer service




Table 4. Columns in Traffic News, fields in Traffica and corresponding fieldsin CDR (Continued)Teleservice Fnw_Teleservice CDR field: Teleservice

UUI Element Count Fnw_Uui_Element_Count CDR field: Number of UUIinformation elements

UUI Call Element Count Fnw_Uui_Call_Element_Count CDR field: Number of UUIinformation elements in callphase

Project Number Fnw_Project_Number CDR field: Project numberAdditional Data Bits 0-21 Fnw_Additional_Data CDR field: Additional data

A CGR Call Start Time Fnw_A_Cgr_Call_Start_Time CDR field: Start time of callon incoming circuit

Fnw_A_Cgr_Call_Start_Date CDR field: Start time of callon incoming circuit

A CGR Connection Time Fnw_A_Cgr_Connection_Time CDR field: Connection timeon incoming circuit

A CGR ConversationTime

Fnw_A_Cgr_Conversation_Time CDR field: Conversationtime on incoming circuit

Cumulative Pulses Sent Fnw_Cumulative_Pulses_Sent CDR field: Cumulativepulses sent

Sent Pulses Classified byTariff Type 1

Fnw_Sent_Pulses_Classified_By_Tariff_Type_1 CDR field: Sent pulsesclassified by tariff type











Sent Pulses AccountCode Billing

Fnw_Sent_Pulses_Account_Code_Billing CDR field: Sent AOC pulses

B CGR Call Start Time Fnw_B_Cgr_Call_Start_Time CDR field: Start time of callon outgoing circuit




Table 4. Columns in Traffic News, fields in Traffica and corresponding fieldsin CDR (Continued)Fnw_B_Cgr_Call_Start_Date CDR field: Start time of callon outgoing circuit

B CGR Connection Time Fnw_B_Cgr_Connection_Time CDR field: Connection timeon outgoing circuit

B CGR ConversationTime

Fnw_B_Cgr_Conversation_Time CDR field: Conversationtime on outgoing circuit

Cumulative PulsesReceived

Fnw_Cumulative_Pulses_Received CDR field: Cumulativepulses received

Outgoing Side ChargeIndicator

Fnw_Outgoing_Side_Charge_Indicator CDR field: Outgoing sidecharge indicator

A Mpty Conference CallID

Fnw_A_Mpty_Conference_Call_Id CDR field: Call identifier a ofthe Multi-Party Conferencecall

B Mpty Conference CallID

Fnw_B_Mpty_Conference_Call_Id CDR field: Call identifier b ofthe Multi-Party Conferencecall

Start Time of the UsedFacility

Fnw_Start_Time_Of_The_Used_Facility CDR field: Start time of theused facility

Fnw_Start_Date_Of_The_Used_Facility CDR field: Start time of theused facility

End Time of the UsedFacility

Fnw_End_Time_Of_The_Used_Facility CDR field: End time of theused facility

Fnw_End_Date_Of_The_Used_Facility CDR field: End time of theused facility

Payer of this Conn inMpty Conference

Fnw_Payer_Of_This_Conn_In_Mpty_Conference CDR field: Payer of thisconnection in the Multi-Party Conference

Number of Participants inConference

Fnw_Number_Of_Participants_In_Conference CDR field: Number of theparticipants in theconference

Original CallingSubscriber

Fnw_Original_Calling_Subscriber CDR field: Original callingsubscriber

Original Called Number Fnw_Original_Called_Number CDR field: Original callednumber




Table 4. Columns in Traffic News, fields in Traffica and corresponding fieldsin CDR (Continued)ConnectionConfigurationIndex of Call

Fnw_Connection_Configuration_Index_Of_Call CDR field: Connectionconfiguration index of call

Service Key Fnw_Service_Key CDR field: Service key

Incoming Side ChargeIndicator

Fnw_Incoming_Side_Charge_Indicator CDR field: Incoming sidecharge indicator

Report Time Fnw_Report_Time Indicates the time the reportwas sent. This field does notexist in the CDR.




Table 4. Columns in Traffic News, fields in Traffica and corresponding fieldsin CDR (Continued)Fnw_Report_Date Indicates the time the reportwas sent. This field does notexist in the CDR.

Souce ID Source_Id If the report is redirectedfrom lower Traffica, this fieldcontains the identifier of thesource. You can specify thesource_id in lower Trafficawhen editing dataredirection properties. Forexample, if lower Traffica isINES connected to MSC,the source_id can bespecified as C-number ofMSC and in upper Traffica(TS) you can see that theredirected report is receivedfrom that particular MSC.Tip: You can createccd.inisection for (networkelement) NE C_numbers sothat each C-number has amatching NE name asdescription.The field does not exist inthe CDR.

Db_Overload Tells if the database serveris overloaded. The possiblevalues:0 = no overload1 = high overload2 = very high load3 = critically high load




Traffica Reference Guide for Fixed Circuit Switched Core1 About this document1.1 Where to find more information1.2 Terms1.3 Abbreviations

2 Change information3 Real-time monitoring3.1 Clear Code Matrix3.2 Real-time graphs3.2.1 Graph Categories3.2.2 Graph Sets

4 Internal Data Structure

Documents

dn99576987x4x0xen