Cigale Iu User Manual

Cigale user manual
CIGALE IU V6.0
User Manual
Cigale Iu v6.0
page 1
Astellia
Cigale user manual
Table of contents
Cigale Iu v6.0
page 2
Astellia
Cigale Iu user manual
PRESENTATION ...............................................................5
INTRODUCTION .....................................................................................6
OVERVIEW OF CIGALE IU....................................................................7
USER INTERFACE ....................................................................................................7
PROCESSING BLOCK DIAGRAM .................................................................................9
SOFTWARE COMPONENTS ...................................................................11
HARDWARE AND SOFTWARE CONFIGURATION .......................................12
INSTALLATION AND STARTUP.....................................13

INSTALLATION PROCEDURE .................................................................14
SOFTWARE INSTALLATION .....................................................................................14
STARTUP ...........................................................................................15
SOFTWARE PROTECTION .....................................................................16
PRESENTATION.....................................................................................................16
PROCEDURE .........................................................................................................16
USER INTERFACE..........................................................18
USER INTERFACE................................................................................19
THE MENUS ..........................................................................................................20
THE TOOLBAR .......................................................................................................20
THE INFORMATION BAR .........................................................................................21
THE PROCESSING INFORMATION BAR .....................................................................21
THE USER MESSAGE ZONE ....................................................................................22
SETTING THE APPLICATION PARAMETERS...............23

CIGALE.CONF FILE .........................................................................24
DESCRIPTION .......................................................................................................24
PROCEDURE .........................................................................................................27
SET PARAMETERS WINDOW .................................................................30
DESCRIPTION .......................................................................................................30
WINDOW ASSOCIATED WITH THE STATISTICS FILES ................................34
MAIN W INDOW DESCRIPTION ................................................................................34
PACKET SERVICES MONITORING DESCRIPTION ......................................................35
CS USER PLAN EXTRACTION DESCRIPTION ...........................................................35
PROCEDURE .........................................................................................................37
OTHERS OUTPUTS PARAMETERS ...........................................................................37
FILTERS DIALOG BOX ..........................................................................39
DESCRIPTION .......................................................................................................39
OTHERS SETTING FILES .......................................................................40
TAC FILE ..............................................................................................................40
TOPOLOGY FILE ...................................................................................................40
TIMERS ................................................................................................................40
POST PROCESS QUERY .........................................................................................42
STATE-MACHINE CONFIGURATION FILES..................43

INTRODUCTION ...................................................................................44
DESCRIPTION .....................................................................................45
EVENTS DECLARATION FILE .................................................................46
CAUSES DECLARATION FILE.................................................................47
STATE-MACHINE DECLARATION FILE .....................................................48
Cigale UMTS v6.0
page 3
Astellia
Presentation
IMMEDIATE PROCESSING OF RECORD FILES...........49

PRESENTATION ..................................................................................50
PROCESSING A FILE IN ITS ENTIRETY ....................................................51
PROCESSING ON A TIME RANGE ...........................................................53
PROCESSING IN REAL TIME MODE .........................................................54
PROCESSING A LIST OF FILE ................................................................55
PROCESSING A LIST OF FILE WITH POLLING ...........................................55
COMMAND LINE PROCESSING ..............................................................56
RESULT FILES ...............................................................59

PRESENTATION ..................................................................................60
LOG FILE ..........................................................................................62
XL3 ACTIVITY REPORTS ......................................................................63
PRESENTATION.....................................................................................................63
DESCRIPTION OF XL3 ACTIVITY REPORTS ..............................................................63
XL2 STATISTICS .................................................................................66
PRESENTATION.....................................................................................................66
DESCRIPTION OF XL2 STATISTICS .........................................................................66
EFF FILE ...........................................................................................67
PRESENTATION.....................................................................................................67
DESCRIPTION OF EFF STATISTICS .........................................................................67
ANNEXES........................................................................68
ANNEX A : CIGALE.CONF ................................................................69
Cigale UMTS v6.0
page 4
Astellia
CHAPTER 1
Presentation
This chapter presents CIGALE.
Cigale UMTS v6.0
page 5
Astellia
Presentation
INTRODUCTION
Efficient and rational operation of a UMTS radio network requires a certain
number of monitoring and diagnosis tools. These tools make it possible to
identify rapidly problems that could affect the overall quality of the network so
that a solution can be found.
The operating and maintenance tools supplied as standard with the
equipment that meet the requirements of the UMTS standard have been
found to be insufficient in certain cases where analysis must be performed
with a fine degree of detail.
CIGALE Iu has been developed by ASTELLIA with a view to complete and
improves the investigation capabilities on UMTS networks.
The CIGALE Iu tool can be described as a "spy" placed in the network at the
level of the Iu interface, between the RNC (Radio Network Controller) and the
CN (Core Network), which analyzes in store-and-forward mode the protocol
frames stored by a recorder placed on the signaling channels. The capture
platform can either be the ASTELLIA Ocean3G, TEKTRONIX K12,
NETHAWK or AGILENT Network analyzer.
Cigale UMTS v6.0
page 6
Astellia
Presentation
OVERVIEW OF CIGALE IU
CIGALE IU has been implemented to ease upgrades of the various
components processed by CIGALE: analyzers, protocols, messages, etc.,
and parameterization of the statistical results using external files describing
the events, causes and the state-machine.
CIGALE takes into account requirements in terms of:
functions :
Standardized installation and uninstallation procedures ;
Direct access to time ranges in the record files ;
Parameterization of the transitions state-machine and of the

associated statistics through the use of external files ;
Generation of statistics (XL2, EFF, XL1, Activity Analysis database

and View database) and troubleshooting information (XL3, Activity
Analysis database and protocol analyzer);
Extraction of User Plan CS and replay of voice communications
ergonomics :
Graphical user interface ;
Display of messages intended for the user during processing ;
Possibility of interrupting the processing in progress (CIGALE then

proposes to generate the statistics) ;
Possibility of performing various consecutive processing operations.
Furthermore, CIGALE IU manages counters intended for the EFFICACE

post-processing software.
USER INTERFACE
The CIGALE IU graphic interface includes a toolbar providing access to the
various processing functions without having to use the menus.
There is also an information bar which indicates the function of each button
or menu.
Lastly, in addition to the information on the Iu interfaces and associated
connections, there is now a user message display zone.
Cigale UMTS v6.0
page 7
Astellia
Presentation
Example of a CIGALE screen
Cigale UMTS v6.0
page 8
Astellia
Presentation
PROCESSING BLOCK DIAGRAM

The CIGALE environment takes the following form:
Parameter
establishment file
CIGALE.CONF
DLL Analyser
(OCEAN)
Automat configuration
(*.ADT, *.BDT)
Saved file
(*.EDX) or stream
CIGALE
Statistical files for Cigale

View and Trending &
Aggregation (_6*.txt)
Log files
Key file for Iub deciphering

BCK
MySql database for Activity

Analysis
Binary file of frames

for detailed decoding (*.edx)
Oracle database for

Trouble Ticketing
Voice and video

communications (.amr
and .324)
CIGALE IU environment
Processing organization:
CIGALE IU decodes record files (e.g. .EDX for ASTELLIA Ocean3G
Analyzer, .RF5 files for TEKTRONIX K12 analyzer,.GRC files for NetHawk
Analyzer and .DAT files for AGILENT Advisor Analyzer) in order to extract
the various messages and associated data (called information elements).
These messages are decoded per protocol layer (SCCOP MTP3, SCCP,
RANAP, Layer3 and applicative).
Messages of other ATM Adaptation layers than AAL5 will be filtered.
The various messages and associated elements make it possible to extract
information such as:
the SCCP connections ;

the SAIs, the location areas detected ;
the types of the current connections (terminating calls, originating calls,
location updates, etc.).
CIGALE IU uses the decoded information to recreate the various connection
contexts and updates the internal counters used for the statistics.
Furthermore, in order to trace the connection changes, each message is sent
to a state-machine described in three external files (EVENTS.BDT,
CAUSES.BDT, and AUTOMAT.BDT). So, each message behaves like an
event that triggers a transition between the current state of the connection
associated with the message and a destination state defined for that
transition in the state-machine's configuration files.
Cigale UMTS v6.0
page 9
Astellia
Presentation
During processing of a record file, it is possible to generate the following files:
XL3: information on each connection and on their history at each

connection closure.
At the end of processing, the following statistics can be generated :
XL2: statistics on the state transitions ;

EFF: counters of transitions.
Lastly, the various error or warning messages generated during processing
can be transferred to a log file (CIGALEIU.LOG).
Cigale UMTS v6.0
page 10
Astellia
Presentation
SOFTWARE COMPONENTS
CIGALE consists of:
the application (CIGALE.EXE) ;

a file (CIGALE.CONF) in which the various application parameters or
options are stored ;
a file (Topology.txt) in which the network components as SAIs or RNCs
can be named for an easier consultation of the results
a file Network.txt in which you can find all network description all over the
world.
dynamic library files (DLL) corresponding to software components (upcs,
packer services monitoring )
dynamic library files (DLL) associated with the analyzers (e.g.
AnOcean3G.DLL for the Ocean3G (Astellia), Ank1205_32GB.DLL for the
K12 (Tektronix), AnNetHawk.dll for NetHawk, AnRadcom.dll for Radcom
and AnAgilentNA.DLL for the Agilent Advisor.
various dynamic library files (DLL) and executable files necessary for the
protection of CIGALE
other DLLs used by Cigale for Ocean3G and K12 frames reading and
MySQL database access.
for the processing functions, you will need event, cause, state-machine
parameterization files.
These files, which must be in the execution directory, are respectively
called EVENTS.BDT, CAUSES.BDT, AUTOMAT.BDT and TIMES.BDT.
Note : the components of the BDT extension (in binary format) can, in
certain cases, be installed with the ADT extension (ascii or text format)
configuration files for the User plan CS extracting (mapping ALCAP, IMSI
list)
Cigale UMTS v6.0
page 11
Astellia
Presentation
HARDWARE AND SOFTWARE CONFIGURATION

CIGALE runs on PC workstations operating with Windows 2000, Windows
XP and Server 2003. The minimum workstation configuration is as follows:
Characteristic
Minimum configuration
CPU
Dual Core CPU
RAM
2 Gb.
Hard drive
40 Gb.
Furthermore, it is recommended that you should have office automation

tools.
Cigale UMTS v6.0
page 12
Astellia
CHAPTER 2
Installation and startup
This chapter describes the various CIGALE IU installation steps, and

the special features of the software protection system.
Cigale UMTS v6.0
page 13
Astellia
INSTALLATION PROCEDURE
SOFTWARE INSTALLATION
See the installation manual: Cigale Iu Installation Manual
Cigale UMTS v6.0
page 14
Astellia
STARTUP
You can run CIGALE IU by clicking on the associated icon in the program
group created at installation or indeed through the link created on your
desktop:
CIGALE Iu
The CIGALE application can be started by

START: PROGRAMMES: Astellia : CIGALE Iu menu.
Cigale UMTS v6.0
page 15
clicking
on
the
Astellia
SOFTWARE PROTECTION
PRESENTATION
When you have installed CIGALE IU with the help of the CD ROM, you will
have to fill in an execution authorization code specific to the destination
computer.
This means that it will not be possible to install the application on different
workstations without the associated codes. However, the same installation
CD ROM may be used on different workstations. You will then simply have to
ask for the codes relative to each workstation.
Software key input screen
PROCEDURE
This window displays a Site Code which is specific to the computer used.
You will have to contact your administrator and give him this code so he can
give you a key authorizing execution.
Limitation of maximum number of RNC processed will be set at this moment
according to your license agreement.
You can then enter the key on this screen or when you start CIGALE later on
(in which case, you can quit CIGALE IU by clicking on the [Quit] button).
You can interrupt CIGALE startup by clicking on [Quit].
If you click the [Validate] button, CIGALE will check the key. There are then
two possibilities:
The key you have entered does not correspond to a valid key : a message
informs you of this error and the software key input screen remains
displayed ;
The key is correct: CIGALE IU application is displayed when you click on
the [Quit] button.
Cigale UMTS v6.0
page 16
Astellia
License Information
Click on ?->License CIGALE IU Menu to display your license

information.
Licence box
You access to the Software key input screen and the possibility to
Kill or Modify your current licence (contact support before using
those options).
Cigale UMTS v6.0
page 17
Astellia
CHAPTER 3
User interface
This chapter describes CIGALE IU user interface.
Cigale UMTS v6.0
page 18
Astellia
User interface
USER INTERFACE
When you start up the application, the CIGALE IU window is divided into
various parts:
The menus: allowing you to run the various processing functions

proposed by the graphic interface. Certain menus can also be accessed
from the keyboard ;
The toolbar: corresponding to direct access to the main functions on the
menus ;
The information bar: indicating the role of the various menus and
buttons ;
The processing information zone: providing information on the progress
status for the processing of a record file, on the A interfaces and the
connections in that file ;
The user message zone : displaying various messages relative to the
processing of a record file in real time.
Menus
Toolbar
Information bar
Processing information zone
User message zone
The various zones on the CIGALE IU window
Cigale UMTS v6.0
page 19
Astellia
User interface
THE MENUS
The following menus are available:
Session
Quit Alt+F4: closes CIGALE IU. This menu is only active when
there is no processing in progress. You can also access this menu
by simultaneously pressing the Alt and F4 keys on the keyboard or
by using the system menus.
Processing :
All F9: performs processing of a record file in its entirety. You can
also access this menu by pressing the F9 key on the keyboard ;
Time range F10: performs processing of a record file (only

available for Tektronix K12 files) on a time range. You can also
access this menu by pressing the F10 key on the keyboard ;
Interrupt ESC: interrupts processing. You can also access this

menu by pressing the ESC key on the keyboard.
Options :
SAI Database : used to modify the origin of the SAI Database which
defines the names of RNCs and SAIs.
Set Parameters : used to modify various CIGALE operating

parameters ;
Statistics: used to select or deselect the statistics files to be used.
Filters: used to select the channels to be processed
About...: displays a window which indicates CIGALE version

number.
?:
Click on the Astellias support e-mail if you need to contact us.
About Box
THE TOOLBAR
The following buttons are available:
: corresponds to the Processing: All menu;

: corresponds to the Processing: Time range menu;
: corresponds to the Processing: Real Time menu;
: corresponds to the Processing: Interrupt menu;
Cigale UMTS v6.0
page 20
Astellia
User interface
: corresponds to the Options: SAI database menu;

: corresponds to the Options: Set parameters menu;
: corresponds to the Options: Statistics menu;
: corresponds to the Options: Filter menu.
The toolbar also displays the type of analyzer used for reading the record
files:
Type of analyzer used by CIGALE
Depending on which processing operation is being performed, these buttons

may or may not be accessible. They are dimmed when inhibited.
THE INFORMATION BAR

This bar displays the description of each menu when you select it with the
mouse or the description of a button when you position the mouse on a
button.
Information bar
THE PROCESSING INFORMATION BAR

This bar provides various items of information relative to record file
processing.
This information concerns:
The name of the record file being processed ;

The list of Iu interfaces resulting from the record file, along with the
number of current connections per Iu interface ;
The number of records (articles) read and the total number of records to
be read ;
A processing progress percentage indicator.
When editing statistics, this indicator shows the statistics editing progress
percentage. So as not to confuse this indicator with the processing progress
indicator, it is displayed in a lighter color. Furthermore, the processing
information zone indicates which file is being edited.
Processing information zone

Cigale UMTS v6.0
page 21
Astellia
User interface
THE USER MESSAGE ZONE

Messages are displayed in real time in this zone during various processing
operations performed in CIGALE IU. This zone includes a vertical scroll bar
allowing you to display earlier messages than those displayed.
Furthermore, you can modify the maximum number of messages that can be
displayed simultaneously (see p.23 Setting the application parameters).
All the messages linked to a record file processing operation can be written
into a dedicated file with the LOG extension (see p.62). To do this you must
turn on the Error file (LOG) option in the choice of statistics files window (see
p.34 Window associated with the statistics files ) or insert the line EDIT_LOG=1 in
the CIGALE.CONF file before starting up CIGALE.
User message zone
When a user message appears in this zone during processing of a record

file, the frame number concerned by the message is displayed at the end of
the message.
User message during the record file processing phase.
Cigale UMTS v6.0
page 22
Astellia
CHAPTER 4
4
Setting the application parameters
This chapter describes the various parameter setting modes for

CIGALE IU.
Cigale UMTS v6.0
page 23
Astellia
CIGALE.CONF FILE
Remark:
It is recommended that you should not modify these various

parameters in the CIGALE.CONF file. You can modify these
parameters in the CIGALE parameter setting window (see p.30 Set
parameters window) or in the window associated with the statistics
file (see p.34 Window associated with the statistics files ) or with Astellia
Editor.
DESCRIPTION
CIGALE.CONF fields are listed in Annex A.
The CIGALE.CONF file is loaded when you start up CIGALE and saved
when the application is closed. Consequently, you should edit this file only
when Cigale application does not run.
This file is read if it is present in the CIGALE execution directory. If this file is
absent, CIGALE try to load CIGALE.INI (old configuration format) and
convert it in CIGALE.CONF, else if no configuration file was found the
parameters will be initialized to their default values. If you start Cigale 4.2
with a cigale.conf of Cigale 4.1, the configuration file will be converted. The
psms configuration file (psm.ini) will be deleted and its parameters will be
integrated in cigale.conf.
The configuration (cigale.conf) must be edited with Astellia Editor. Just
double-click on the file cigale.conf from an explorer will launch Astellia
Editor.
ToolBar :
Parameters of the
Open / Save / Close
selected section
are display here
The differents
sections are displayed
here. You must select
section for which you
want to change the
parameters. For some
section you must
activate the section
with checkbox to
setup it.
Cigale UMTS v6.0
page 24
Astellia
For each parameter you have a tooltip. Just put the mouse over the
parameters and a help text will be displayed.
The parameters are divided in 5 top sections.
Component: Information about the Cigale version.
Network: Settings about the network.
Processing: Settings for the processing.
Inputs: Option for OnLine mode and Real Time mode.
Outputs: Defines which outputs Cigale must produce (AA, View, TA,
text, UPCS).
The advanced settings are displayed in blue. Be careful before modify

these parameters. Only experimented users must modify these
parameters.
Cigale UMTS v6.0
page 25
Astellia
To setup the default analyzer for a command line processing. You must go in
the section Processing/Analyzer and put in Analyzer1 the default analyzer.
Cigale UMTS v6.0
page 26
Astellia
PROCEDURE
We have seen that the CIGALE.CONF file is loaded when you start up the
application. There are then several possibilities:
The CIGALE.CONF and CIGLAE.INI file is missing : a message dialog

box is displayed to inform you, and :
If you place a CIGALE.CONF file in the execution directory and click

the [Yes] button in the dialog box : the file you have inserted is taken
into account ;
If you click the [No] button in the dialog box : the application is
terminated
Message indicating that the CIGALE.CONF and CIGALE.INI file is missing
If there are a CIGALE.INI and no CIGALE.CONF, cigale will convert the INI
into CONF.
Cigale say that the Xml configuration file does not exist. After
CIGALE.CONF is generated, CIGALE will always use the CIGALE.CONF
and not the CIGALE.INI
When cigale try to convert CIGALE.INI into CIGALE.CONF, if the file is

incorrect (the [Cigale IU] line is missing) : a message is displayed to
inform you and the application is initialized with the default values ;
Cigale UMTS v6.0
page 27
Astellia

Message indicating the CIGALE.INI file is incorrect
If the CIGALE.CONF file is invalid you get this message ;
The file is correct but the value in a field is incorrect (e.g.

NB_WARNING_MESSAGES=200): a message is displayed to inform you
and the line concerned is ignored. The parameter is then initialized with its
default value ;
Message indicating that the value in a field is incorrect
The file is correct but an analyzer DLL description is incorrect :
the specified DLL file does not exist :
Analyzer DLL missing
The analyzer has already been declared in the CIGALE.CONF file

(the DLL is declared twice or another DLL including an analyzer with
the same name (K1205 by Tektronix) has already been read) :
Redundant analyzer DLL

Cigale UMTS v6.0
page 28
Astellia
The version of the analyzer DLL is obsolete :
Incorrect version
The declared DLL is not an analyzer DLL :
Incorrect DLL
The declared DLL is not a DLL :
Incorrect file
The line containing the incorrect DLL is then ignored.
The file is correct but no analyzer DLL has been declared or those
that have been declared are incorrect: a message is displayed and
CIGALE IU shuts down since it will not be possible to perform any
processing.
Execution impossible if there is no analyzer DLL
Cigale UMTS v6.0
page 29
Astellia
SET PARAMETERS WINDOW

DESCRIPTION
This window is accessed via the Options: Set parameters menu or the
button. It looks like this:
CIGALE parameter setting window
The following CIGALE.CONF file fields correspond to those of the parameter

setting window.
Processing options:
BUFFER: Resynchronization buffer Size.

If you want to set the Resynchronization buffer Size, just fill the new value
there. If you enter an out of range value, a message box will inform you
COUNTRY CODE (MCC): country code of the observed network for

roaming statistics. Field coded on 3 digits.
NETWORK CODE (MNC): network code of the observed network for
roaming statistics. Field coded on 2 or 3 digits and the size is the same for
all MNC of a given MCC.
Cigale UMTS v6.0
page 30
Astellia
Example :
NAME
MCC
MNC
GROUP
PREFIX
COUNTRY
CAN 302-001, Microcell
302
001
CA
Canada
CAN 302-360, Telus Mobility
302
360
CA
Canada
CAN 302-370, MicroCell
302
370
CA
Canada
CAN 302-651, Bell Mobility
302
651
CA
Canada
CAN 302-700, Tel Mobility
302
700
CA
Canada
CAN 302-710, Globalstar CAN
302
710
CA
Canada
CAN 302-720, Rogers Wireless
302
720
CA
Canada
MEGACO DECODING: Enable or disable the Megaco processing.

There is an optional configuration file for Megaco Decoding.
ast_megaco.conf . This file contains the mapping of the MGW IP
address, RNC id and PCM.
There is an example in the Cigale directory.
ast_megaco.conf.sample:
[MGW01]
IpAddress=10.150.136.1
RNCid=14
RNCid=15
Mapping=BSSAP
1100
400
Mapping=BSSAP
1100
400
Mapping=ISUP
1430
10200 8
[MGW02]
RNCid=16
RNCid=17
Mapping=BSSAP
1200
401
Mapping=BSSAP
1200
401
Mapping=ISUP
1430
10300 9
Database parameters:
Cigale UMTS v6.0
page 31
Astellia
DATABASE_PARAM:PUBLIC_NAME: Public MySQL server name. This

parameter is optional. It is used if the server name is a private address or
a local link. This parameter allows to transmit a public name to viewers
which offer a navigation to Activity Analysis (Cigale View, Trouble
Ticketing, etc )
DATABASE_PARAM:HOST: MySQL server name
DATABASE_PARAM:LOGIN: MySQL Login / user
DATABASE_PARAM:PASSWORD: MySQL Password
Those parameters define the database place where results will be written.
If you want to write the results on the local PC database, just fill server
name to localhost, which is the default value after Cigale setup.
If you want to write results on a distant PC database, you will have to fill the
server name, the login and password (if defined) of this PC.
Before running Cigale, you should try the validity of this database distant
connection. Just Click on test connection button and see the result. If its
different from Connection OK, the database connection is not valid (see the
reason in the error message provided).
In all cases, closing the parameters window will launch a connection test and
a warning will inform you if a connection problem arises.
Statistics editing directory:

INI file: definition of the parameters file
STATS_DIRECTORY: Statistics editing directory.
You can either directly type in a directory name (directory will be created if
it does not already exist) or browse existing directory by clicking the
button.
Selection of statistics edition directory
Cigale UMTS v6.0
page 32
Astellia
Deciphering parameters:
This box determines the generation of the file of keys for Iub deciphering.
Generate deciphering data (.bck) per Rnc: If

checked then one bck file will be genrated per RNC.
Bck pridiocity (min): If 0 then bck file are

generated at the end of processing, if different of 0
bck are generated every minute set in this
parameters. Default value is 15 minutes.
The [OK] button of the parameter window allows the confirmation of the
modifications made to the window field, then, if the values are correct,
close the window.
The [Cancel] button restores the values present when opening the
window, and then closes the window.
Cigale UMTS v6.0
page 33
Astellia
WINDOW ASSOCIATED WITH THE STATISTICS FILES

MAIN WINDOW DESCRIPTION
This window is accessed via the Options: Statistics menu or the
It looks like this:
button.
Window associated with the statistics files
The following CIGALE.CONF file fields correspond to those of the window

associated with the statistics files:
EDIT_XL3: Connections (XL3) ;

EDIT_XL2: State-machine transitions (XL2) ;
EDIT_TIM: Timers;
EDIT_XLV: Miscellaneous statistics;
EDIT_LOG: Error file (LOG) ;
EDIT_EFF: EFFICACE input file (EFF) ;
EDIT_TOP: Topology observed and non observed (DAT);
Cigale UMTS v6.0
page 34
Astellia
EDIT_BD: database for Cigale View

EDIT_ANALYSIS: database for UMTS activity analysis.
EDIT_ANALYSIS_TRA: generate or not the detailed activity table.
EDIT_NC_MESSAGES: Filter of the not connected messages in the
Analysis database
EDIT_CDR_FRAMES_SIG: Generate the signalization frames list in order
to reach the detailed decoding (protocol analyzer) from the activity report
table of Activity Analysis
EDIT_CDR_FRAMES_USER_PS: Generate the PS data frames list in
order to reach the detailed decoding (protocol analyzer) from the activity
report table of Activity Analysis
EDIT_ANALYSIS_KPI: launches SQL queries at the end of the
processing
Clicking the [OK] button confirms the selections and deselections, and then
closes the window.
Clicking the [Cancel] button restores the values that were present when you
opened the window and then closes it.
PACKET SERVICES MONITORING DESCRIPTION

The complete description of this module is in the Packet Services Monitoring
user manual.
The
Packet
Services
Monitoring
option
SERVICES_ANALYSIS in the configuration file.
corresponds
to
Checking the Packet Services Monitoring option without making any

selection in the advanced configuration box just configures CIGALE to
characterize the services (http, wap ) in the CDRs without generating any
statistics or other data for Activity Analysis.
CS USER PLAN EXTRACTION DESCRIPTION

Clicking on service analysis which corresponds to UPCS_EXTRACTION in
the configuration file, opens the following window:
Cigale UMTS v6.0
page 35
Astellia
Cigale UMTS v6.0
The generation period allows extracting voice and video files every n
seconds. If n=0, an only extraction is performed at the end of the
processing.
The aim of the option IMSI Profiling is to obtain a new list of IMSI to
be extracted. The list of IMSI is given according to a SQL queries list
stored in a file which is chosen by the user.
The extraction may be performed either on an EDX file or a list of

EDX files. The user must complete the corresponding field, (file or
directory) according to the EDX source containing the CS User plan.
The ALCAP PathId File is optional. Its aim is to define the mapping
between the quintuplet (card/ port/ VPI/ pathId/ Cid ) and the
quadruplet (card, port, VPI, VCI) of the CS user plan. In case of
absence, Cigale assumes that PathId=VCI. Its format is the following:
page 36
Astellia
[ALCAP-ATM] Card=1 Port=9 VPI=20 PathID=38
-> Card=2 Port=3 VCI=35
[ALCAP-ATM] PathID=39 -> VCI=40
The Imsi list define the list of IMSI to be extracted. Its format is the
following:
123451056512333
123451055703036
123451056275540
123454143889651
123451056437667
123451058492889
123451054266385
123451056716012
The output directories define the location where the voice and video
files must be generated.
The aim of the option Call Profiling is to obtain a list of

communications according to a SQL queries list stored in a file. Its
format to respect is the following:
SELECT
xl3_autonum,HEX(xl3_imsi) as xl3_imsi,UNIX_TIMESTAMP(xl3_start_ti)
as start,xl3_start_msec_ti,
UNIX_TIMESTAMP(xl3_end_ti) as end,xl3_end_msec_ti,xl3_path_Id,
xl3_card,xl3_port,xl3_vp, xl3_CID , elt_name, xl3_comm_duration,
xl3_cnx
FROM
JOIN
ON
WHERE
AND
xl3
oth_elts
xl3.xl3_service_type=oth_elts.idelement
oth_elts.elt_name= ''
(xl3_comm_duration is not null OR xl3_ring_duration is not null)
PROCEDURE
When you have opened the window associated with the statistics files, you
can click the check boxes to reverse their value. When a check box is
selected the associated statistics file will be generated.
OTHERS OUTPUTS PARAMETERS

Some parameters could only be accessed through Cigale.conf
Cigale UMTS v6.0
page 37
Astellia
In View section, user can specify the directory in which View text files will be
generated, and can specify which statistics he wants for View: Counters
Views means efficiency counters (Attach drop rate, number of PDP
activation procedure), Traffic Views means volume/Throughput per APN
for instance.
In T&A section, user can specify the output directory in which periodic text
files (similar to View text files) or customized statistics files will be generated.
Default T&A periodicity is 1h (60 minutes).
Dynamic statistics for T&A enables to launch post process SQL query in
order to generate specific text file that could be integrated into T&A Iu (from
release 4.0) and mapped into T&A family Customized statistics per RNC.
This SQL query has a predefined output format and should be modified
carefully. It is based on CDR table only (Activity Report) and aggregation
level is RNC.
Note: The name of this query could be modified but it should end with xxx_RNC.sql
Cigale UMTS v6.0
page 38
Astellia
FILTERS DIALOG BOX

Activate filtering
Load filters
Save filters
on disk
DESCRIPTION
This dialog box can be used to define ATM filters. Several filters can be
defined using ATM attributes: Card number, Port number, Virtual Path ID,
Virtual Circuit ID and Channel ID. Wildcards (*) can be used for any of these
fields.
During the process, all the ATM frames that do not match with at least one of
the specified filters are ignored by the Cigale engine.
When Cigale is launched, filtering is not active. Thus, the filters list is empty,
the radio button labelled Process all channels is selected and all other fields
are disabled.
Click on Process only following channels radio button to activate filtering.
Filters may be loaded from a file or directly entered using the edit boxes: type
a value for each of the 5 ATM fields. The * character can be used for any of
these fields, meaning that all values should be taken into account for the
corresponding field. Once all parameters are filled in, press the Add button.
An empty field is considered as a * character. A new filter is then added in
the Active Filters list. This list can be saved into a text file by pressing the
disk icon.
To remove a filter, select the appropriate line in the Active Filters list and click
Remove. Or click Remove All to delete all filters.
Cigale UMTS v6.0
page 39
Astellia
OTHERS SETTING FILES

TAC FILE
This file contains the names of Manufacturer and Type of mobile. The first
column is the TAC (Type Approval Code) which can be 6 or 8 digits length,
the second is the manufacturer. And the third is the type of mobile. The fields
are separated by tabulations.
The default file is TAC.txt and is located in C:\ASTELLAI\SHARED
TOPOLOGY FILE
The fields are separated by tabulations.
The default file is generated by formers lac_2g.dat and sai_names.dat in a
topology.txt located in the install directory.
cell_name
cell_type
lac
Bsc_rnc_name
rnc_id
sac
SAI_GARE
3G
23
RNC_RENNES
12
SAI_MAIRIE
3G
23
RNC_RENNES
13
SAI_MUSEE
3G
24
RNC_RENNES
14
SAI_HOPITAL
3G
99
RNC_VITRE
15
SAI_GARE
3G
99
RNC_VITRE
16
SAI_FEMTO
3G Femto
104
RNC_FEMTO
17
2G
124
2G
654
2G
123
2G
999
TIMERS
They are defined in Times.bdt
IU CS TIMERS
Timer
Description
start event
stop event
CS_Authentication_Duration
Duration of
authentication
procedure
AUTRQ
AUTRP
CS_SecurityMode_Duration
Duration of
security mode
SECMODCMD (CS)
SECMODCMP (CS)
Cigale UMTS v6.0
page 40
Astellia
procedure
CS_RAB_Assignment_Duration
Duration of Radio
Access bearer
assignment
procedure
RABAREQ_SoM
(CS)
RABARESP_SoMd
(CS)
CS_OC_Setup_Duration
Duration of
originated call
setup
CMSRQ
ALERT, PROG,
CON
CS_TC_Setup_Duration
Duration of
terminating call
setup
PAGRP
ALERT, PROG,
CON
CS_Setup_Duration
Duration of call
setup (both
originated and
terminated
PAGRP or CMSRQ
ALERT, PROG,
CON
CS_NormallyReleasedCall_Duratio Duration of
n
normally released
calls
PAGRP or CMSRQ
DISC or REL or
RELCMP
CS_Call_Duration
Communication
duration for calls
CONACK
DISC, REL ,
RELCMP ,
IuRELREQ ,
IuRELCMD or SCCP
RLSD
CS_Voice_Call_Duration
Communication
duration for voice
calls
CONACK (voice)
DISC, REL ,
RELCMP ,
IuRELREQ ,
IuRELCMD or SCCP
RLSD
CS_Video_Call_Duration
Communication
duration for video
calls
CONACK (video)
DISC, REL ,
RELCMP ,
IuRELREQ ,
IuRELCMD or SCCP
RLSD
CS_Service_Access_Delay
CMSRQ
CMSA or
SECMODCMP
CS_Transaction_Setup
SETUP
ALERT, PROG,
CON
LUREQ
LUACC
CS_Loc_Update_duration
Cigale UMTS v6.0
Duration of
location update
procedure
page 41
Astellia
3G-2G HO TIMERS
Timer
Description
start event
Reloc_preparation_2G_duration
Duration
relocation RLOCREQD
preparation 2G procedure
RLOCCMD
Reloc_completion_2G_duration
Duration
completion
IuRELCMD
relocation RLOCCMD
stop event
2G procedure
Reloc_2G_duration
Duration relocation
procedure
2G RLOCREQD
IuRELCMD
IU PS TIMERS
Timer
Description start event
stop event
PS_RA_update_duration
GMM_RA_UPD_REQ
GMM_RA_UPD_ACC
PS_RAB_duration
RABARESP
RABARESP(_RLSD),
IuRELCMD,
IuRELCMP
POST PROCESS QUERY

The file postProcess.dat contains a query that is executed if the box execute
queries in Activity Analysis configuration is checked or if the Boolean SQL
post processing file in Outputs/ Activity analysis/ is set to true. This query
generates a dynamic table of statistics in Activity Analysis and is defined as
follow:
Cell Reselection
KPI
Comments
Aggregation levels
SAI
SAI name
Aggregation point
RNC
RNC name
Per SAI
LAC
Location Area Code
Per SAI
RAC
Routing Area Code
Per SAI
Nb RAU 2G
Number of RAU coming from 2G cell
Per SAI
Nb RAU 3G
Number of RAU coming from 3G cell
Per SAI
Nb ATTACH 2G
Number of ATTACH coming from 2G

cell
Per SAI
Nb ATTACH 3G
Number of ATTACH coming from 3G

cell
Per SAI
Cigale UMTS v6.0
page 42
Astellia
CHAPTER 5
State-machine configuration files
In CIGALE IU an externally defined state-machine is used to format

the statistics.
This chapter presents the files allowing you to configure this statemachine.
Cigale UMTS v6.0
page 43
Astellia
INTRODUCTION
The state-machine is configured by means of three external files (BDT). They
must be contained in the CIGALE execution directory when you start up the
application.
These files should not be modified. They are supplied with the CIGALE
application and your administrator is responsible for their maintenance.
Cigale UMTS v6.0
page 44
Astellia
DESCRIPTION
The statistics obtained when processing a record file serve two main
purposes:
To count the various data items or situations detected during that

processing ;
To trace the changes in the various connection contexts.
The state-machine is designed to trace these changes by distinguishing
between the different types of connections (originating calls, terminating
calls, location updates, handovers, etc.).
To achieve this, the notions of states and of transitions between states have
been defined. A transition is characterized by two states (origin and
destination), a message (also called event) and a cause. These states and
transitions are contained in the AUTOMAT.BDT external file.
The events and causes are identified by names in the AUTOMAT.BDT file.
The EVENTS.BDT and CAUSES.BDT files are then used to establish the
correspondence between those names and the coded events and causes. In
fact, an event is characterized by a membership protocol and a code, and a
cause is identified by its code.
These three files are supplied with CIGALE IU and should not be modified.
They must be in the CIGALE IU execution directory in order to be taken into
account by the application. They are loaded when you start up CIGALE.
However, the CAUSES.BDT and EVENTS.BDT files are not mandatory for
processing unlike the AUTOMAT.BDT state-machine description file. If they
are missing, only the state-machine's generic transitions will be triggered and
the statistics will include the cause codes (e.g. 0x02), and for the events,
their protocol name followed by their code (e.g. SCCP :0x10).
Cigale UMTS v6.0
page 45
Astellia
EVENTS DECLARATION FILE

The EVENTS.BDT file describes the names of the events used by the statemachine. It must be in the CIGALE execution directory in order to be loaded
when you start up CIGALE.
If the format of this file is found to be incorrect (does not correspond to an
event description file), a message will be displayed and the file will be
considered to be absent.
Incorrect file format
If the EVENTS.BDT file is missing, a message will be displayed and the

events will appear in their coded form in the statistics (e.g.
RANAP:0x10) : <Protocol name>:<Event code>.
File missing
If this file is correct, CIGALE user message window will indicate that it is
being read.
Cigale UMTS v6.0
page 46
Astellia
CAUSES DECLARATION FILE

The CAUSES.BDT file describes the names of the causes used by the statemachine. It must be present in the CIGALE IU execution directory so that it
can be loaded when you start up CIGALE.
Processing of the CAUSES.BDT file is identical to that of the EVENTS.BDT
file:
If the format of this file is found to be incorrect (does not correspond to a

cause description file), a message will be displayed and the file will be
considered to be absent ;
If this file's format is found to be correct, but the file version is not
compatible with the version of CIGALE you are using, a message will be
displayed and the file will be considered to be absent ;
if this file is missing, a message will be displayed and the cause codes will
appear in the statistics (e.g. 0x02) ;
If this file is correct, CIGALE user message window will indicate that it is
being read.
Cigale UMTS v6.0
page 47
Astellia
STATE-MACHINE DECLARATION FILE

The AUTOMAT.BDT file describes the state-machine used to generate the
XL2 statistics file in particular. It must be contained in the CIGALE IU
execution directory. The state-machine is loaded when you start up CIGALE
or, if loading was interrupted (using the Processing: Interrupt menu), when
a record file is next processed.
It will not be possible to perform any processing if the AUTOMAT.BDT file is
missing.
The state-machine breaks down into a succession of transitions from one
state to another. These transitions are defined by an event (or message) and
possibly a cause. These events can also be broken down using extensions.
There are two types of extension:
Indication of certain messages' transit direction ;

The specialization of certain messages.
It should be noted that certain events can use both these types of extension
simultaneously.
This file is also used to mark certain transitions with a view to including in the
XL2 statistics file (see p.63 XL3 statistics) only the connections for which a
marked transition has been detected. This makes it possible to distinguish
between certain types of connection with a view to obtaining a finer analysis
of those connections in the XL3 file.
Counters can also be associated with the transitions. These counters then
count the number of occurrences of the associated transition(s) detected
during processing of a record file.
Furthermore, this file usually contains an internal reference name which will
be mentioned in all the statistics files. It will then be possible to study those
statistics files without any ambiguity since they are generally dependent on
the state-machine.
If the format of the AUTOMAT.BDT file is found to be incorrect (does not
correspond to a state-machine description file), a message will be displayed
and the file will be considered to be absent.
If the format of the file is found to be correct, but the file's version is not
compatible with the version of CIGALE IU you are using, a message will be
displayed and the file will be considered to be absent.
If this file is missing, a message will be displayed and it will not be possible to
perform any processing of a record file.
If this file is correct, the user message zone in the CIGALE window will
indicate that it is being read. During this loading operation, the current
loading status is indicated, along with any state-machine configuration errors.
If errors are displayed, you will have to inform your administrator since you
will not be able to perform any processing.
Cigale UMTS v6.0
page 48
Astellia
CHAPTER 6
Immediate processing of record files
This chapter presents the immediate processing modes for record

files.
Cigale UMTS v6.0
page 49
Astellia
PRESENTATION
This chapter only concerns immediate, single-step processing operations on
record files. There are three immediate processing modes for record files:
overall processing ;
processing restricted to a time range ;
command line processing
Reminder:
The parameter setting options (see p.23 Setting the application

parameters) are mainly used when processing record files.
Choose the directory in which the statistics are to be edited.
The options in the window associated with the statistics files (see
) allow you to choose
between generation of the various statistics files or no
generation.
p.34 Window associated with the statistics files
Cigale UMTS v6.0
page 50
Astellia
PROCESSING A FILE IN ITS ENTIRETY

If you want complete processing of a record file, you must use the
Processing: All menu, the

the file in the selection box:
button, or the F9 key. You can then choose
Record file selection box.
The state-machine is then read if it has not already been loaded. If this file is
incorrect, it will not be possible to continue processing.
Information will be displayed in real time during processing in the graphic
interface zone associated with the processing operation (see p.21 The processing
information bar) and in the user message zone (see p.22 The user message zone).
Cigale UMTS v6.0
page 51
Astellia
Example of a CIGALE screen during processing of a record file
The CIGALE title bar displays the processing progress percentage. This
allows you to see the degree of progress made even if you have minimized
the application.
You can interrupt processing by clicking the

button. A message is
displayed allowing you to confirm, or not, before the interruption becomes
effective:
Stopping processing
Furthermore, a check box allows to choose whether to generate the statistics

or not if you wish to interrupt processing. By default, the statistics are
generated.
Cigale UMTS v6.0
page 52
Astellia
PROCESSING ON A TIME RANGE

If you want to process a record file on a time range, you must select the file
using the Processing: Time range menu, the
button, or the F10 key.
The procedure is the same as for overall processing except that, once you
have selected the file you want to process, you will be asked to choose a
time range.
Time range selection window
The time range selection window is initialized with the beginning and end
dates of the file to be processed.
Remarks:
The dates in CIGALE IU correspond to the extreme processing

dates. So, if you enter the start time: 9h56mn40s160ms,
processing will be performed from the first frame that comes
after that date. Likewise, if you enter the end
time: 11h52mn48s500ms, processing will end on the last frame
preceding that date.
When the start date and time, or the end date and time, or both
have not been modified CIGALE considers that the processing
operations are to be performed from the beginning, or until the
end, of the file.
CIGALE IU presents the limit dates and times of the data frames
in the record file (if the extreme frames are not frames of
information to be processed, they will be excluded from the time
range presented).
Cigale UMTS v6.0
page 53
Astellia
PROCESSING IN REAL TIME MODE

If you want to process an ocean real time output, you must setup the
connection using the processing menu, real time (F11).
Processing is only available for Ocean Analyzer.
Real Time
Server Address: Hostname or Ip address of the analyzer.

Server Port: TCP/Ip port of the analyzer
Capture Duration (min): This is maximum length of the capture to process.
When capture duration is reached the process stop.
Outputs Name: This field indicate the name of the statistics outputs (AA,
View, TA, etc ).
Cigale UMTS v6.0
page 54
Astellia
PROCESSING A LIST OF FILE

If you want to process a list of files, you must launch Cigale in command line (cf: Command line
processing) with the character * in the file name option (-i) to specify a directory where the files will be
processed.
PROCESSING A LIST OF FILE WITH POLLING

If you want to process a list of files with, you must launch Cigale in command line (cf: Command line
processing) with the character * in the file name option (-i) to specify a directory where the files will be
processed, a time range and the option -p.
The beginning and the end of the specified time range must be in the same day.
Cigale will wait for a flag during the time specified in the p option. The flag is a file with an flg
extension. When the flag appears, Cigale looks for the same file with an edx extension (in case of
OCEAN capture) and process it. If such a file does not exist in the specified directory, the processing is
stopped.
The processing is stopped if a frame is later than the end (-ce) of the specified time range.
If an edx file ends just before the end of the specified time range (less than the value defined in the INI
file) then CIGALE considers than the processing is finished. Hence, Cigale supports a light
desynchronization between the end of the capture and the end of the time range and does not wait for
the timeout to achieve the processing.
Stop causes:
end of time range
no edx file corresponding to the received flag
time range specified on several days
one option (-i, *, -p, -cs or ce) missing
invalid input directory
timeout expired
user stop
Cigale UMTS v6.0
page 55
Astellia
COMMAND LINE PROCESSING

CIGALE processing can be launched via a DOS command line with the
following syntax:
cigale.exe [options]
-i file_name:
Path and file name of the trace to be processed.

In order to process a list of files, you can replace the file name by
an asterisk. Then all the files of the folder will be processed in
alphabetic order. If the f option is not used, the name for the
statistics files will be the name of the directory (cf. example).
In ordrer to process a stream, the file name has to be replaced by
the folowing syntaxte :
\\10.1.0.3\Astellia\Ocean\Streams;data;@10.1.0.3:4000
Where :
- \\10.1.0.3\Astellia\Ocean\Streams is the top directory
(containing the StreamDataFiles and StreamDescFiles directory)
where the stream is generated
- data is the name of the stream (the name of the .xde file)
- ;@10.1.0.3:4000 is the IP adress and port of the stream
(optionnal parametes)
-d directory name: Path of Cigale.exe directory

-f file_name:
Name used for the output (databases and statistics files)
-cs dd/mm/yyyy hh:mm:ss.: Start of the time range (must be used with ce).
-ce dd/mm/yyyy hh:mm:ss.: End of the time range (must be used with cs).
-cp ini_file:
Path and file name of the Cigale.conf file. This option allows use of
a specific Cigale.conf file, for instance to generate more statistics
and to specify a different configuration folder. Then, using this
option to specify a new Cigale.conf file in a different directory
implies to copy all the configuration files (*.adt or *.bdt) in this
directory.
-cf filter_name: Path and file of the channel filter to use.

-ck key_directory: Directory to be used for key files generation.
-p timer:
specifies a polling processing. This option must be used with the

options cs, -ce and -i with the character * to specify a list of to be
processed. The process is stopped if no new file arrives before
timer seconds.
-iupcs file_name: Path and file name of the trace containing CS User plan for
Voice and video files extraction.
In order to process a list of file, you can replace the file name by an
asterisk. If this parameter is missing, the extraction will be
performed on the initial source file (parameter i). To extract
UPCS files, the option UPCS_EXTRACTION must be activated
in cigale.conf
-ccon connexion_number: Number of the connection to processing in the case of on
demand process. In this cas only one connexion will be processed
-cue identity: Identity of the connexion, use in the case of processing on demand
process for one connexion. Usualy Identity of the connexion is
SCCP. In the on demand process for one connexion you must
use the field cs and ce to setup the time range of the
annalyse. cs MUST BE the start time of the connexion you
want to analyse.
Cigale UMTS v6.0
page 56
Astellia
-ccons cnx1-cnx2: This option permit to do processing on demand process for

many connexion. You just need to fill the connexion number after
the option. Separate the connexion number with a -.
-db host:port/database: This option is used in processing on demand mode,
host and port must be filled but are not used. Database must
contain the name of the reference database. The new database is
created on the host set in the configuration file.
this option forces Cigale to process on demand on time range
instead of with frames lists. This option is used in case of
incomplete or null frames lists.
-complete
-tr host:port: This option is used for Real Time process. Host and port must be
filled with ip address (or hostname) and port of the analyzer.
Example:
Normal processing:
Cigale.exe -i "c:\temp\Astellia.edx" -d "C:\Program
Files\Astellia\Cigale UMTS Iu"
Processing a list of files:

Cigale.exe -i "c:\temp\*" f stats_of_the_list -d "C:\Program
Files\Astellia\Cigale UMTS Iu"
Processing a list of files with polling:

Cigale.exe -i "c:\temp\*" f stats_of_the_list -d "C:\Program
Files\Astellia\Cigale UMTS Iu" -cs "07/02/2003 12:31:18.542" -ce
"07/02/2003 15:39:59.879" p 120
Time range processing with specific Cigale.conf file to be used:

Cigale.exe -i "c:\temp\Astellia.edx" -d "C:\Program
Files\Astellia\Cigale UMTS Iu" -cs "07/02/2003 12:31:18.542" -ce
"07/02/2003 15:39:59.879" cp
"C:\MyPC\Me\MyCigaleFolder\myCigale.conf"
On demand process for one connexion:

cigale -i "p:\astellia_test__sig_upps20060426140000.edx" -d
"E:\Dev\CIGALE_UMTS\Debug" -cp
"E:\Dev\CIGALE_UMTS\Debug\cigale.conf" -db
"127.0.0.1:3306/astellia_test__sig_upps20060426140000" -ccon
18685 -cue 129323 -f test1 -cs "26/04/2006 14:14:59" -ce
"26/04/2006 14:20:00"
On demand process for many connexions:

cigale -i "p:\astellia_test__sig_upps20060426140000.e
dx" -d "E:\Dev\CIGALE_UMTS\Debug" -cp
"E:\Dev\CIGALE_UMTS\Debug\cigale.conf" -db
"127.0.0.1:3306/astellia_test__sig_upps20060426140000" -ccons
"4-13937-18685"
-f test1
Cigale UMTS v6.0
page 57
Astellia
Real Time Processing:

Cigale tr "192.168.1.212:20000" f "realtimeprocessing"
Streaming Processing:
Cigale.exe -i "c:\trace\streaming;data;@10.1.0.3:4000"
Cigale UMTS v6.0
page 58
Astellia
Result files
CHAPTER 7
7
Result files
This chapter details the various files generated when a record file is
processed.
Cigale UMTS v6.0
page 59
Astellia
Result files
PRESENTATION
Various files are generated during and at the end of processing so that the
content of the record file can be examined. These files may be log files
(LOG) or statistics files. They are edited in a dedicated directory. This
directory corresponds by default to the directory containing the record file. It
is possible to choose another directory by filling in the STATS_DIRECTORY
field in the CIGALE.CONF file (before starting up CIGALE IU) or in the
parameter setting window (see p.23 Setting the application parameters).
Since the statistics files are generally linked to the external state-machine,
the reference name relative to the state-machine used is integrated in each
statistics file.
All the files have a similar header which contains:
The CIGALE version number (e.g. CIGALE V1.3 (01.01.01.000)

COPYRIGHT Astellia 2003) ;
The name of the statistics file (e.g. QOSIU2MO070202.XL2) ;
The record file processing start date and time (e.g. Date Start
07/02/2002 09 :56 :40 :170) ;
The record file processing end date and time (e.g. Date End
07/02/2002 11 :52 :48 :431) ;
The state-machine's reference (e.g. State-machine
(v1.0.0); Astellia [full]).
19/04/2002
Example of an XL3 file header
Remarks:
When processing has been interrupted by the user, the end of

processing date and time corresponds to the date and time of
the last frame processed for the result files generated at the end
of processing. This concerns the XL2, and EFF files. The other
result files keep the processed file's end date since they were
generated during the processing operation.
During statistics editing at the end of processing, the graphic interface

displays the name of the file being written and the gauge displays the
statistics progress percentage. The gauge is displayed in a lighter color to
avoid any confusion with the processing progress percentage for a record
file.
Cigale UMTS v6.0
page 60
Astellia
Result files
Example of the CIGALE screen during statistics editing
It is not possible to interrupt statistics generation.

Do not forget that only the statistics selected in the window associated with
the statistics files will be generated (see p.34 Window associated with the statistics
files ).
CAUTION: When generating statistics files, the existing files are replaced.
Cigale UMTS v6.0
page 61
Astellia
Result files
LOG FILE
Two Log files are generated.
The first, named CigaleIu00.log in install_directory\log\, collects some
information (options, name of the base ) and the major or critical errors
happened during the last processings. This file is limited in size. The digits at
the end of the file name correspond to the number of instances of engines
running (i.e. the second instance of Cigale will have a log file named
CigaleIu01.log).
The second LOG file will only be generated if you have chosen the error file
generation option. You can choose this option in the CIGALE.CONF file or in
the window associated with the statistics files (see p.34 Window associated with the
statistics files ).
The user messages (see p.22 The user message zone) are written in this file during
the record file processing phase.
The data processing time as well as the time it takes CIGALE to calculate
statistics that are connected to this data, are displayed at the end of this file.
Likewise, Cigale indicates at the end of a LOG file if the program was
interrupted by the user.
Cigale UMTS v6.0
page 62
Astellia
Result files
XL3 ACTIVITY REPORTS

PRESENTATION
XL3 information are used to trace the complete sequence for a given
connection by analyzing, either manually or by post-processing, the various
parts (on different SAIs) that that connection is made up of. It also indicates
the duration of each connection and the ringing duration if ringing took place.
The XL3 statistics are edited at closure of each connection or part of
connection.
As a general rule, for regular observations or for statistical processing
operations that do not concern a problem on a precise type of connection,
there is not much point in generating this file, which is very cumbersome to
exploit.
XL3 statistics are edited during processing (generally at closure of each

connection) ;
In order to generate XL3 statistics, you will have to insert the line
EDIT_XL3=1 in the CIGALE.CONF file before you start up CIGALE IU or
turn on the Connections (XL3) check box in the window associated with the
statistics files (see p.34 Window associated with the statistics files ).
DESCRIPTION OF XL3 ACTIVITY REPORTS

This file contains two kinds of information:
Connection/Transaction activity reports
After the header, the file starts directly with the text data array.
Each line in this file corresponds to one connection and if present, one
transaction. For each line, the following columns are provided:
Con. Nb: Cigale internal connection number

Start Time: start
hh:mm:ss:msmsms
time
of
the
connection,
format:
dd/mm/yyyy
End Time: end

hh:mm:ss:msmsms
time
of
the
connection,
format:
dd/mm/yyyy
First Event: first event associated with the connection.

Con. Duration: connection duration in ms.
IMSI: IMSI number according to the format of 3GPP specifications
MCC: Subscriber Mobile Country Code
MNC: Subscriber Mobile Network Code
Subscriber country
Subscriber operator
Subscriber group: group of the subscriber operator
Initial (P)TMSI: TMSI number according to the format of 3GPP specifications.
(P)TMSI: TMSI number after possible reallocation, according to the format of
3GPP specifications.
Cigale UMTS v6.0
page 63
Astellia
Result files
IMEI: IMEI number according to the format of 3GPP specifications.

SV: Software version
MS Codec List: Mobile supported codec list
PAGRP - 1st PAGING : time between first paging and paging response.
# PAGING: number or paging repetition.
Old LAC: first Location Area code according to the format of 3GPP
specifications
LAC: Location Area code according to the format of 3GPP specifications
Old RAC: first Routing Area code according to the format of 3GPP
specifications
RAC: Routing Area code according to the format of 3GPP specifications
Start SAC: first Service Area Code according to the format of 3GPP
specifications
SAC: Service Area Code according to the format of 3GPP specifications
RNC: the Controlling RNC Name, with the following format RNC =
RNC_N<number> where the number is the semaphore point code of the RNC
SRNC: The serving RNC name
CN: Core Network Id (MSC, SGSN)
Old MCC: Old mobile country code
Old MNC: Old mobile network code
Last Event : If there is a transaction: last event associated with the
transaction. If there is no transaction: last event associated with the connection
Cause : If there is a transaction: cause associated with the transaction
If there is no transaction: cause associated with the connection
Final state : If there is a transaction: last state associated with the transaction
If there is no transaction: last state associated with the connection
3G CId (2G HO): 3G Target Cell Id for 2G to 3G HO

3G Cell type: 3G Cell type (Macro, Femto ...)
Target RNC: RNC target of the last SRNC relocation procedure
Target 2G Cell: 2G cell target of the last SRNC relocation procedure
Old system: Indicates whether UE was previously localised in 2G or 3G
Nb of relocation attempts: number of SRNC relocation procedures
TI : transaction identifier, according to the format of 3GPP specifications
NSAPI: NSAPI
CN TEID: Terminal equipment identifier of core network
RNC TEID: Terminal equipment identifier of RNC
Start Time TI: start
hh:mm:ss:msmsms
End Time TI: end
hh:mm:ss:msmsms
time
time
of
the
transaction,
format:
dd/mm/yyyy
of
the
transaction,
format:
dd/mm/yyyy
Service Type: Voice, Video, SMS, WAP, MMS, HTTP

First Event TI: first event associated with the transaction.
Ringing Duration: If present, ringing time of the call in ms.
Comm. Duration: If present, communication duration in ms.
Bearer Cap: Information taken out of the Bearer Capability information
element with the format: itc, Mt, FnUr.
Phone Number: Called or Calling party phone number.
Cigale UMTS v6.0
page 64
Astellia
Result files
PDPaddress: Pdp addresses contained in message pdp address accept.

Req class of service: requested class of service
Acc class of service: accepted class of service
TC RAB: Traffic class allocated in the RAB assignment request
ARP: Allocation Or Retention Priority Level in the RAB assignment request
THP: Traffic Handling Priority in the RAB assignment request
UL RAB MBR: Max Bit Rate request by the CN to the RNC in the RAB for UL
DL RAB MBR: Max Bit Rate request by the CN to the RNC in the RAB for DL
UL RAB GBR: Uplink RAB guaranteed bit rate
DL RAB GBR: Download RAB guaranteed bit rate
AccessPointName: access point name
Path Id: ALCAP connection element identifier path id
Channel Id : ALCAP connection element identifier CID
Max forward CPS-SDU bit rate: Bit Rate reserved in DL on the AAL2 link
Vol. UL (KBytes): Data volume sent by the mobile station during this session
Vol. DL (KBytes): Data volume received by the mobile during this session
max TP UL (kbit/s): max throughput uplink
avg TP UL (kbit/s): average throughput uplink
Th. Rel. UL (%): reliability of UL throughput evaluation
max TP DL (kbit/s): max throughput downlink
avg TP DL (kbit/s): average throughput downlink
Th. Rel. DL (%):reliability of DL throughput evaluation
Type: type defined in the autmat.adt file of the last transition of the CDR
ALCAP ATM IDs card-port-vp-vc
list of ALCAP ATM Ids
RANAP ATM IDs card-port-vp-vc
list of ALCAP RANAP Ids
UL SCCP Reference
DL SCCP Reference
card
ATM values for establish request message
port
vp
vc
2G reloc fail
relocation failure from 2G
3G relocfail
relocation failure from 3G
estab. duration (ms) establishment duration

data: MEGACO Information
TLA: Transport Layer Address
Binding Id
Note: The TMSI, IMSI, IMEI and called numbers are systematically preceded
by the " " character.
Do not forget that international called or calling numbers are also
preceded by the + "character.
Cigale UMTS v6.0
page 65
Astellia
Result files
XL2 STATISTICS
PRESENTATION
The XL2 statistics file will only be generated if you choose the option for
generating statistics on the state-machine transitions. This option can be
chosen in the CIGALE.CONF file or in the window associated with the
statistics files (see p.34 Window associated with the statistics files .).
DESCRIPTION OF XL2 STATISTICS

Data is provided on a RNC basis. There is one block of information for each
RNC. The blocks are separated by a carriage return character. Each block
has the following format:
Cigale UMTS v6.0
One line indicating the RNC Name, with the following format RNC =
RNC_N<number> where the number is the semaphore point code of the
RNC
One line with the word SAI in the sixth column
One line with the title of the data columns. Starting from the sixth column
we have the SAI number, indicating which SAI this columns refers to.
One carriage return character (empty line)
Data columns providing statistics about the transitions triggered in the
state machine.
page 66
Astellia
Result files
EFF FILE
PRESENTATION
This file groups together a set of counters which are used by the EFFICACE
post-processing software.
DESCRIPTION OF EFF STATISTICS

The first 7 lines are header information. The following two lines provide the
EXCEL macro EFFICACE version that has to be used to calculate indicators
based on the EFF counters. The data are then provided on a RNC basis:
there is one block of information for each RNC. The blocks are separated by
a carriage return character. Each block has the following format:
One line indicating the RNC Name, with the following format RNC =
RNC_N<number> where the number is the semaphore point code of the
RNC
One carriage return character (empty line)
One line with the title of the data columns. The first column corresponding
to the counters names defined in the state machine has the title NAME.
Starting from the second column we have the SAI number, indicating
which SAI this columns refers to and the last column corresponds to the
whole RNC.
Data columns providing the name and values of the counters defined in
the state machine, for each SAI and for the RNC. There are as many lines
as different counters.
Cigale UMTS v6.0
page 67
Astellia
Annexes
CHAPTER 8
Annexes
Cigale UMTS v6.0
page 68
Astellia
Annexes
ANNEX A : CIGALE.CONF
Group
Component/
Component/
Network/
Network/
Topology/
Name
Component
Component name
Component version
Network
Topology
Description
Component
Component name
Component version
Network settings
Topology settings
Type
Group
Comment
Comment
Group
Group
Networks File Path
Networks description file

This field indicates the location of
the file containing topology
informations
Determining the mobile country
code of the network currently in
study.
Determining the mobile network
code of the network currently in
study.
String
Network/
Topology/
Topology File Path
Network/
Topology/
HPLMN MCC
Network/
Topology/
Network/
HPLMN MNC
Paging
Network/
Paging/
Network/
Paging/
Network/
Paging/
Network/
Paging/
Network/
Network/ TACIMEI/
MSC maximum number of

PAGING repetitions for a paging
procedure.
Paging Nb Repeat CS
Paging Repeat Time CS
Paging Nb Repeat PS
Paging Repeat Time PS
TAC-IMEI
TAC-IMEI file
Processing
Input filtering
Processing/
Processing/
Input filtering/
Processing/
Processing/
Decoding/
Standard
Processing/
Decoding/
Processing/
Frame redundancy management

Deciphering
Processing/
Deciphering/
Processing/
Deciphering/
Processing/
Deciphering/
ATM filter file

Decoding
Deciphering data path

Deciphering file type
Generate one Bck per Rnc
Processing/
Deciphering/
Generate Bck Periodicity
Processing/
Throughtputs
Processing/
Throughtputs GTP
Cigale UMTS v6.0
String
String
String
Group
Integer
MSC PAGING repetition period.

SGSN maximum number of
PAGING repetitions for a paging
procedure.
Integer
SGSN PAGING repetition period.

TAC / handset type mapping
File for TAC / handset type
mapping.
Processing settings
Input filtering
Integer
Group
Select ATM filter file.

Decoding
ETSI or ANSI are availables.
Default value is ETSI.
If checked, Cigale will try to
eliminate the double frames due to
redundancy in the capture (eg
mirror port).
Deciphering
Determining the generation and in
which directory the file of Keys for
Iub deciphering.
CSPS, CS or PS
If true then one bck file will be
genrated per RNC
If 0 then bck file are generated at
the end of treatment, if different of
0 bck are generated every minute
set in this parameters. Default
value is 15 minutes.
Throughputs settings
Integer
File
Group
Group
File
Group
Enum
Boolean
Group
Path
Enum
Boolean
Integer
Group
Group
page 69
Astellia
Annexes
/
Processing/
Throughtputs/
GTP/
Processing/
Throughtputs/
GTP/
Processing/
Throughtputs/
GTP/
Processing/
Processing/
Megaco/
Processing/
Megaco/
Processing/
Megaco/
Processing/
Megaco/
Processing/
Megaco/
Processing/
Processing/
Packet Service
Monitoring/
Processing/
Packet Service
Monitoring/
Processing/
Packet Service
Monitoring/
Processing/
Packet Service
Monitoring/
Processing/
Packet Service
Monitoring/
Processing/
Packet Service
Monitoring/
Processing/
Packet Service
Monitoring/
Processing/
Packet Service
Monitoring/
Processing/
Packet Service
Monitoring/
Min number of frames
Minimum number of frames in a

sample for throughput evaluation.
Integer
Duration
Minimum duration of a sample for

throughput evaluation (in ms).
Integer
PSDR in Activity Analysis
Maximum duration of a sample for

throughput evaluation (in ms).
Enable or disable the Megaco
processing.
Generation of independant Megaco
CDR.
Integration of MEGACO
Information to CDR.
Generation of Megaco Statistics in
AA.
Megaco treshold statistics time for
failed calls in seconds (default
value is 10s)
the file containing MGW mapping
Packet Service Monitoring
If checked, the output text files for
Cigale View database will be
generated.
If checked, the Services Activity
table for Activity Analysis will be
generated.
IPDR in Activity Analysis
If checked, the IP Activity table for

Activity Analysis will be generated.
Boolean
IP in Activity Analysis
If checked, the IP table for Activity

Analysis will be generated.
Boolean
Extended duration
Megaco
Megaco CDR generation
Megaco CDR Integration
Megaco Statistics
Megaco treshold statistics time
MGW mapping file
Packet Service Monitoring
PSM Database for VIEW
If checked then generate IPDR of

unidentified services.
For other PS statistics in View
whose size is greater than this
threshold (in Kbytes) would be
Threshold Other PS
used to generate View statistics.
Specifies the maximum number of
Do not generate more than n IPDR lines in the IP Activity table for a
during a PDP Ctxt
given PDP Context.
Enables statistics generation for
large content download in Cigale
Generate statistics on large content View (PSQ 1.2:: HTTP Large
downloads
Content Download Throughput)
Only HTTP files whose size is
greater than this threshold (in
Kbytes) would be used to generate
Large DL threshold
View statistics.
Maximum memory that could be
handled by Packet Services
Monitoring module. If reached,
current IPDR/PSDR will be closed
and reopen as soon as a new
traffic frame is seen. This
Maximum PDP Ctxt memory
parameter SHOULD NOT be
threshold (Mo)
modified
IPDR Other PS in Analysis
Processing/
Packet Service
Monitoring/
Processing/
Packet Service
Monitoring/
Minimum inactivity timeout
Cigale UMTS v6.0
Current PSDR and IPDR would be

closed after this timer expiry
page 70
Integer
Group
Boolean
Boolean
Boolean
UInt
File
Group
Boolean
Boolean
Boolean
Integer
Integer
Boolean
Integer
Integer
Integer
Astellia
Annexes
Processing/
Packet Service
Monitoring/
List max size
Dynamic stats for TA
Maximum number of portal page or

server to process
Portal pages taken into account for
statistics generation in Cigale View
on HTTP or WAP portal page
access delays (View PSQ1.1 and
PSQ2.1).
Name of the servers taken into
account for statistics per HOST in
Cigale View. It could be a
Hostname (www.astellia.com) or
server IP address (1.2.3.4)
Intervals definition for VIEW
distribution statistics. If field equals
to 100;500;1000;10000, there will
be 5 Intervals : - Interval 1 : file size
< 100 kbytes - Interval 2 : 100
kbytes < file size < 500 kbytes Interval 3 : 500 kbytes < file size
< 1000 kbytes- Interval 4 : 1000
kbytes < file size < 10000
kbytes - Interval 5 : file size >
10000 kbytes.
If checked then generate PSDR in
text file, This field indicates the
directory in which the PSDR file
must be generated.
If checked, the dynamic output text
files for TA will be generated from
the IP activity and Service Activity
tables.
Input Folder for Dynamic SQL

Requests
This Folder contains all .sql files for

dynamic requests
Path
Output Folder for Dynamic SQL

Requests
This Folder contains all .txt files

generated by dynamic requests
Path
RTCP Loss Threshold
RTCP Loss threshold.
Integer
RTCP Loss Interval
RTCP Loss Interval in milliseconds. Integer
Processing/
Packet Service
Monitoring/
Portal(s) name
Processing/
Packet Service
Monitoring/
Server(s) name
Processing/
Packet Service
Monitoring/
Size intervals
Processing/
Packet Service
Monitoring/
IPDR PSDR text
Processing/
Packet Service
Monitoring/
Processing/
Packet Service
Monitoring/
Processing/
Packet Service
Monitoring/
Processing/
Packet Service
Monitoring/
Processing/
Packet Service
Monitoring/
Processing/
Packet
Service
Monitoring/
Processing/
Packet Service
Monitoring/
Filtering/
Processing/
Packet Service
Monitoring/
Filtering/
Processing/
Packet Service
Monitoring/
Filtering/
Processing/
Packet
Service
Monitoring/
Cigale UMTS v6.0
Filtering
Integer
List
List
String
Path
Boolean
Group
Start of PSM analysis
Start of PSM analysis

(HH:MM:SS.MI) Second and
milliseond are optional
Time
End of PSM analysis
End of PSM analysis

(HH:MM:SS.MI) Second and
milliseond are optional
Time
File of IMSI to be analyzed by PSM
File of IMSI to be analyzed by PSM File
Targeting
If checked, only the specified

hosts and DNS servers are
included in PSM processing.
page 71
Group
Astellia
Annexes
Processing/
Packet Service
Monitoring/
Targeting/
Host(s) to include in processing.
Processing/
Packet Service
Monitoring/
DNS server address(es) to include
Targeting/
in processing.
Processing/
Processing/
VIPs/
Processing/
VIPs/
VIPs
Information LTTR4VIP
VIP IMSI file
Processing/
VIPs/
Processing/
VIP SQL Query file

Advanced settings
Processing/
Advanced
settings/
Resynchronization buffer size
Processing/
Advanced
settings/
Nb warning messages
Processing/
Advanced
settings/
Inputs/
Inputs/
Settings/
Inputs/
Settings/
Inputs/
Settings/
Inputs/
Settings/
Inputs/
Settings/
Inputs/
Inputs/
Process
Mode/
Mobile reachable timer

Inputs
Settings
Input
Comment
Information LTTR4VIP
This field indicates which file
contains the list of VIP IMSI.
This field indicates which file
contains the list of SQL queries to
execute to find which connections
should be processed.
Advanced settings
Determining the size of the
resynchronization buffer. By default
this field equals 100. The buffer
size must be comprised between 1
(no buffer) and 9999. For OCEAN,
as the frames are already
synchronized, the buffer is set to 1
and this parameter is not taken into
account.
Determining the maximum number
of user messages to be displayed
simultaneously on the screen. By
default this field equals 100. The
number of messages must be
comprised between 0 (no
messages) and 100.
After this timer (in minutes) the
inactive transactions are purged.
This timer simulates the procedure
of implicit detach.
Inputs settings
Input settings
File or directory to process. (With
online mode, this path must be a
directory).
Comment
File
File
Group
Integer
Integer
Integer
Group
Group
String
Analyzer
Comment
Select analyzer corresponding to
capture format
Enum
Start time
Start of time range for process.
SPFDateTime
End time
Process Mode
End of time range for process.

Process mode options
SPFDateTime
Group
Online mode
Enable Online mode

Group
Specifies a 'polling' treatment. This
option must be used with the
options -cs, -ce and -i with the
character '*' to specify a list of to be
treated. The Treatment is stopped
if no new file arrives before 'timer'
seconds.
Integer
Inputs/
Process Mode/
Online mode/
Polling timeout(s)
Cigale UMTS v6.0
Host(s) to include in processing,

when targeting is allowed.
Hostnames (www.astellia.com) and
IP addresses (1.2.3.4) are allowed. List
DNS server address(es) to include
in processing, when targeting is
allowed. Only IP addresses
(1.2.3.4) are allowed.
List
Long Term Troubleshooting for
VIPs
Group
page 72
Comment
Astellia
Annexes
During a processing in polling

mode, the CIGALE engine will not
Inputs/
wait for a new capture if the
Process Mode/
remaining time to process is
Online mode/
MIN_REMAINING_TIME_POLLING smaller than this value.
In polling mode, Cigale waits for a
Inputs/
'flag' file in capture directory.The
Process Mode/
'flag' file base name defines the
Online mode/
Remove File Once Processed
available capture files.
Inputs/
Process
Mode/
Multi probes mode
Enable Multi probes mode
- Additional File or directory to
Inputs/
process. (With online mode, those
Process Mode/
pathes must be directories).
Multi probes
Aditional Inputs and Frame
- Alias associated with the path in
mode
Server Alias
frame extractor's configuration
Inputs/
Defines the waiting timeout for
Process Mode/
unready probes when using multi
Multi probes
Multi probes synchronisation
probes input. The minimum value
mode
timeout (sec)
is 10 seconds
Inputs/
Process
Mode/
Real Time Processing
Inputs/
Process Mode/
Real Time
Processing/
Real time enabled
Real time enabled
Inputs/
Process Mode/
Real Time server where the data
Real Time
will be read. It can be a DNS name
Processing/
Real Time Server
or an IP address and a port
Inputs/
Process Mode/
Real Time
Processing/
Protocol
Define protocol
Inputs/
Process Mode/
Real Time
Processing/
Hostname
Define hostname
Inputs/
Process Mode/
Real Time
Processing/
Port
Define port
Inputs/
Process Mode/
Real Time
Maximum Processing Duration
Maximum Processing Duration in
Processing/
(min)
minutes
Inputs/
Process Mode/
Real Time
Processing/
Connection Time Out (ms)
Connection Time Out in milisecond
Inputs/
Process Mode/
Real Time
Disconnection Time Out in
Processing/
Disconnection Time Out (ms)
milisecond
Inputs/
Process Mode/
Real Time
Processing/
Read Time Out (ms)
Read Time Out in milisecond
Inputs/
Process Mode/
Real Time
Processing/
Read Buffer Size (bytes)
Read Buffer Size in bytes
Cigale UMTS v6.0
page 73
Integer
Enum
Group
ListGroup
UShort
Group
Boolean
ServerConnection
String
String
UShort
Integer
UInt
UInt
UInt
UInt
Astellia
Annexes
Outputs/
Outputs/
Settings/
Outputs/
Settings/
Outputs/
Outputs/
Activity
analysis/
Outputs/
Activity
analysis/
Outputs/
Activity
analysis/
Outputs/
Activity
analysis/
Outputs/
Activity
analysis/
Outputs/
Activity
analysis/
Outputs/
Activity
analysis/
Outputs/
Activity
analysis/
Outputs/
Activity
analysis/
Cigale UMTS v6.0
Outputs
Settings
Output mode
Activity analysis
Outputs settings
Output
Used name for the output
(databases and statistics files)
Used mode for the output
(databases and statistics files)
'Input file': outputs will be named
with the (first) source name (EDX
file) 'OutputRadical': outputs will be
named with the output radical
defined above
'date_OutputRadical': outputs will
be named with the current date and
the output radical defined above,
format is 'YYYY_MM_DD_{radical}'
'date_hour_OutputRadical': outputs
will be named with the current date,
the current time and the output
radical defined above, format is
'YYYY_MM_DD_HH_MM_{radical}'
'T&A naming': outputs will be
named with the current date and
time (small length) and the output
radical defined above, format is
'YYMMDD_HHMM_{radical}'
Activity Analysis Settings
MySQL parameters
MySQL server name, port, login

and password. You can test the
connection with the test button.
MySQL
Hostname
Define hostname
String
Port
Define port
UShort
Login
Define login
String
Password
Define password
Password
Level of detail
Trace detailed activity
Choose the correct Level of detail

Enum
Defines the public MySQL server
name. This parameter is optional. It
is used if the server name is a
private address or a local link. This
parameter allows providing a public
name to viewers which offer
navigation to Activity Analysis. If
empty, this parameter take the
SERVER NAME parameter value. String
If checked, the 'detailed activity'
table of Activity Analysis will be
generated.
Boolean
SQL post processing file
If checked, the PostProcess.dat

SQL file will be launched after
Cigale processing. This file
contains MySQL queries to be
executed at the end of the
processing. These queries must be
valid MySQL queries and the
character ();) or (--) at the
Boolean
Output radical
Server name used by viewers
page 74
Group
Group
String
Enum
Group
Astellia
Annexes
beginning of a line indicates a

comment. Each query must be on
a new line and finished by the
character ();)
Outputs/
Activity
analysis/
Trace not connected message
Outputs/
Activity
analysis/
Insert sig frames into CDR
Outputs/
Activity
analysis/
Outputs/
Activity
analysis/
Outputs/
Activity
analysis/
Outputs/
Activity
analysis/
Outputs/
Activity
analysis/
Outputs/
Activity
analysis/
Outputs/
Activity
analysis/
Outputs/
Activity
analysis/
Insert PS user frames into CDR
Boolean
Boolean
Boolean
Central database parameters
Limits the number of frames per

CDRs
Derterminate the sample size of
frames list (an insertion is
performed for each sample)
Central Database server name,
port, login and password. You can
test the connection with the test
button.
Hostname
Define hostname
String
Port
Define port
UShort
Login
Define login
String
Password
Define password
Allows or not access to the
Database while being generated. If
activated, the processing will be
slightly slowed down.
Add database index on IMSI field
to improve troubleshooting
performance with this field. If
Add database index on IMEI field
Add database index on SAC field
Password
CDR Frames list max size

CDR Frames sample size
Outputs/
Activity
analysis/
Real time database access
Outputs/
Activity
analysis/
Imsi troubleshooting
Outputs/
Activity
analysis/
Imei troubleshooting
Outputs/
Activity
analysis/
SAC troubleshooting
Cigale UMTS v6.0
If checked, the not connected

messages will be inserted in the
'detailed activity' table of Activity
Analysis.
If checked, the detailed decoding
(protocol analyzer) of the
signalization frames will be
reachable from the 'activity report'
table of Activity Analysis.
If checked, the detailed decoding
(protocol analyzer) of the PS data
frames will be reachable from the
'activity report' table of Activity
Analysis.
page 75
Integer
Integer
MySQL
Boolean
Enum
Enum
Enum
Astellia
Annexes
Outputs/
Activity
analysis/
Outputs/
Activity
analysis/
Outputs/
Outputs/
Detailed
decoding/
Outputs/
Detailed
decoding/
Outputs/
Detailed
decoding/
Outputs/
Detailed
decoding/
Outputs/
Detailed
decoding/
Outputs/
Detailed
decoding/
Outputs/
Detailed
decoding/
Outputs/
Outputs/ On
demand
processing/
Outputs/ On
demand
processing/
Outputs/ On
demand
processing/
Outputs/ On
demand
processing/
Frame Server
Add database index on Last Event

field to improve troubleshooting
Add database index on Last Cause
field to improve troubleshooting
Detailed decoding
Defines the IP address and port of
Frame Extractor. Default value is
[localhost:20100].
ServerConnection
Protocol
Define protocol
String
Hostname
Define hostname
String
Port
Define port
UShort
Frame Server Alias
Alias of the source directory
String
Last Event troubleshooting
Last Cause troubleshooting

Detailed decoding
Enum
Group
File generation periodicity (min)

On demand processing
A partial EDX will be generated in

this directory
Defines the detailed decoding file
generation periodicity in seconds.
Default value is 15 minutes if Real
Time Database Access is on, 24
hours if Real Time Database
Access is off
On Demand Processing
Integer
Group
On Demand Server
Defines the IP address and port of

On Demand Process Server.
Default value is [localhost:20200].
ServerConnection
Protocol
Define protocol
String
Hostname
Define hostname
String
Port
Define port
Root path to the capture file
storage space. In the Astellia
System process flow, after the
automatic Cigale process, the
capture files can be moved from
their original directory to a storage
space (keeping the last directory
name unchanged). When using on
demand processing, the above
option indicates to Cigale where
the captures file has been moved
(The last directory must be
removed).
Statistics files
This field indicates the directory in
which the statistics files must be
generated.
UShort
Detailed decoding directory
Outputs/ On
demand
processing/
Outputs/
Captures file storage directory

Statistics files
Outputs/
Statistics files/
Output directory
Cigale UMTS v6.0
Enum
page 76
Path
Path
Group
Path
Astellia
Annexes
Outputs/
Statistics files/
CDR (XL3) periodicity (s)
Outputs/
Statistics files/
CDR Output directory
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Periodicity for XL3 files generation

in seconds. Default value is 0 (only
1 XL3 file)
which the CDR statistics files must
be generated.
State-machine transitions (XL2)

Timers (TIM)
Miscellaneous statistics (XLV)
Efficace (EFF)
EFF type
Topology (DAT)
View
Outputs/ View/
Output directory
Outputs/ View/
Counters Views
Outputs/ View/
Outputs/
Outputs/ TA/
Outputs/ TA/
Traffic Views
TA
Warning
Information
Outputs/ TA/
Outputs/ TA/
Outputs/ TA/
Output directory
Automatic daily subdirectory
TA periodical zip files destination
path
Outputs/ TA/
TA Periodicity
Outputs/ TA/
Efficace 1/4 hour
Outputs/ TA/
Outputs/
Efficace 1/4 hour directory

TT
Outputs/ TT/
TT server
Outputs/ TT/
TT V3
Cigale UMTS v6.0
If checked, the XL2 statistics file

will be generated at the end of
processing of a record file.
If checked, the different procedure
timers defined will be generated
during process.
If checked, some ATM statistics
are produced in a XLV file.
If checked, the EFFICACE
counters will be generated.
This flag determines the orientation
of the Efficace table in the file
[file].eff. By default the flag is set to
0, then the counters are on the yaxis and the SAIs on the x-axis. If
the flag is set to 1, the axes are
swapped and the macro Efficace is
not usable (It is useful to avoid the
Excel limitation of 255 columns in
case of a big amount of SAIs).
If checked, the topology file
(name.dat) will be generated.
View
which the Cigale View files must be
generated.
If checked, all views except traffic
will be generated.
If checked, all traffic views will be
generated.
Trending and Aggregation
Warning
Information
which the TA files must be
generated.
Use daily statistics subdirectory.
If checked, 'Output directory' is
used to generate temporary files
Value in minutes of generation of
the TA files.
If this field equals to 'True', T_A
efficace counter is generated all
1/4 hours.
If this field equals to 'True', T_A
efficace counter is generated all
1/4 hours.
Trouble Ticketing SDRs
Trouble Ticketing server
parameters (IP address, login,
password, port)
Defined if the type of server TT to
communicate with is a TT v3
server.
page 77
Integer
Path
Boolean
Boolean
Boolean
Boolean
Boolean
Boolean
Group
Path
Boolean
Boolean
Group
Comment
Comment
Path
Boolean
Path
Enum
Boolean
Path
Group
ServerConnection
Boolean
Astellia
Annexes
Outputs/ TT/
TT SDRs record path
Outputs/ TT/
TT Disallow Duplicates
Outputs/ TT/
TT Message Time Out
Outputs/ TT/
TT Message Retry
Outputs/ TT/
TT Session Test Time Out
Outputs/ TT/
TT Session Start Time Out
Outputs/ TT/
TT SDR Send Time Out
Outputs/ TT/
TT Session Stop Time Out
Outputs/ TT/
TT SDR Send Packet Count
Outputs/ TT/
TT SDR Send Packet Time Out
Outputs/ TT/
Period of sdr file creation
Outputs/ TT/
Number of attempts to connect

Delay between two connection
attempts
Type Filter
Outputs/ TT/
Outputs/ TT/
Outputs/ TT/
Type Filter
Outputs/
Outputs/VIP
Care/
Outputs/VIP
Care/
Outputs/VIP
Care/
Cigale UMTS v6.0
TT SDR Type filter file

VIP Care
VIP Care server
VIP Care Off Line
VIP Care SDRs record path

the path containing the SDRs in
offline mode or the SDRs which
couldn't have been send to TT
server
A SDR is a time based duplicate if
the xEndDate field of SDR is lower
than the xEndDate field of any SDR
that was already sent.0, if timebased duplicates are allowed; 1,
otherwise.
Life time, in milliseconds, of a
message that is sent to the TT
server. This number must be lower
or equal to 4 294 967 295.
Number of retry after what the sent
is considered as failed.
session test message that is sent
to the TT server. This number must
lower or equal to 4 294 967 295.
Time, in milliseconds, between the
first session open request
message and the moment when
the request is considered to be
failed. This number must be lower
or equal to 4 294 967 295.
first send of a SDR and the
moment when the send of the SDR
is considered to be failed. This
number must be lower or equal to 4
294 967 295.
first session close request
or equal to 4 294 967 295.
Maximum number of SDR per
packet. When reached, packet is
sent.
When this timeout (in ms) elapsed,
packet is sent (whatever the
number of SDR)
Periodicity of SDR file generation
when connection white TT Server
is lost.
Number of attempts to connect to
TT server
attempts to the TT server
If check, TT SDRs are filtered
This field indicates the name of the
file containing the type of SDR
which are filtered by Trouble
Ticketing. This file is located in
Cigale directory.
VIP Care SDRs
VIP Care server parameters (IP
address, login, password, port)
No connection to VIP Care server.
SDRs are sent in a file.
the path containing the SDRs in
page 78
Path
Boolean
Integer
Integer
Integer
Integer
Integer
Integer
Integer
Integer
Enum
Byte
UInt
Group
String
Group
ServerConnection
Boolean
Path
Astellia
Annexes
Outputs/VIP
Care/
Ftp hostname for sdr file
Outputs/VIP
Care/
Ftp folder path
Outputs/VIP
Care/
VIP Care SDR Type filter file
Outputs/VIP
Care/
VIP Care Disallow Duplicates
Outputs/VIP
Care/
Outputs/VIP
Care/
VIP Care Message Time Out

VIP Care Message Retry
Outputs/VIP
Care/
VIP Care Session Test Time Out
Outputs/VIP
Care/
VIP Care Session Start Time Out
Outputs/VIP
Care/
VIP Care SDR Send Time Out
Outputs/VIP
Care/
VIP Care Session Stop Time Out
Outputs/VIP
Care/
VIP Care SDR Send Packet Count
Outputs/VIP
Care/
VIP Care SDR Send Packet Time

Out
Outputs/VIP
Care/
Outputs/VIP
Care/
Outputs/VIP
Care/
Cigale UMTS v6.0
Period of sdr file creation

Number of attempts to connect
attempts
offline mode or the SDRs which

which couldn't have been send to
VIP Care server"
This field indicates the FTP
hostname used by the VIP Care
server to retrieved SDRs which
have been saved in file when
connection with VIP Care server is
lost.
This field indicates the path on the
FTP server where the SDR file are
stored
which are filtered by VIP Care. This
file is located in Cigale directory.
A SDR is a time based-based
duplicate if the xEndDate field of
SDR is lower than the xEndDate
field of any SDR that was already
sent.0, if time-based duplicates are
allowed; 1, otherwise.
message that is sent to the VIP
Care server. This number must be
lower or equal to 4 294 967 295.
Number of retry after what the sent
is considered as failed.
session test message that is sent
to the VIP Care server. This
number must lower or equal to 4
294 967 295.
first session open request
or equal to 4 294 967 295.
first send of a SDR and the
moment when the send of the SDR
is considered to be failed. This
number must be lower or equal to 4
294 967 295.
first session close request
or equal to 4 294 967 295.
Maximum number of SDR per
packet. When reached, packet is
sent.
When this timeout (in ms) elapsed,
packet is sent (whatever the
number of SDR)
Periodicity of SDR file generation
when connection white VIP Care
Server is lost.
Number of attempts to connect to
VIP Care server
attempts to the VIP Care server
page 79
String
String
String
Boolean
Integer
Integer
Integer
Integer
Integer
Integer
Integer
Integer
Enum
Byte
UInt
Astellia
Annexes
Outputs/VIP
Care/
Outputs/VIP
Care/ IMSI
Filtering
Activation
Outputs/VIP
Care/ IMSI
Filtering
Activation
Outputs/VIP
Care/ IMSI
Filtering
Activation
IMSI Filtering Activation
If check, Vip Care SDR are

filtered by IMSI
Group
VIP Care Upload Path

the uploaded file containing the
IMSI followed by VIP Care
Path
VIP Care IMSI filter file
ByPass
Outputs/VIP
Care/ IMSI
Filtering
Activation
Outputs/
VIP Care ByPass file

UPCS
Outputs/
UPCS/
Generation Period (minutes)
Outputs/
UPCS/
Timeout (minutes)
Outputs/
UPCS/
ALCAP PathId file
Outputs/
UPCS/
Purge EDX files
Outputs/
UPCS/
Outputs/
UPCS/
Outputs/
UPCS/
Capture
location/
Outputs/
UPCS/
Capture
location/
Outputs/
UPCS/
Capture
location/
Outputs/
UPCS/
Outputs/
UPCS/ Audio/
Outputs/
UPCS/ Audio/
Cigale UMTS v6.0
Purge Delay

file containing the IMSI followed by
VIP Care
If check, SDR of types defined in
the ByPass file are send even if
their IMSI are not followed by VIP
Care
which are ByPass by VIP Care.
This file is located in Cigale
directory.
CS user plan extraction
Value in seconds of generation of
voice and video files. If this value is
set to 0, an only extraction is
performed at the end of the
processing.
Cigale supports a
desynchronization between the end
of the capture and the end of the
UPCS treatment.
the configuration file for the
mapping pathId Cid.
This field indicates if the
suppression of files EDX treated by
UPCS is authorized.
This field indicates the purging
delay of files UPCS. It is accessible
only if treatment UPCS is done with
a list of files EDX.
Capture location
String
Boolean
String
Group
Integer
Integer
Path
Boolean
Integer
Group
Scan whole directory
This flag checked indicates if the

extraction must be performed on a
list of edx files contained in a
directory (true) or on an only edx
file (false).
File
If the extraction must be performed

on a single edx file, this field
indicates the source file.
File
Directory
If the extraction must be performed

on a whole directory, this field
indicates the source directory.
Path
Audio
All
Call profiling
Boolean
Group
This field indicates that all voice
Boolean
extraction of audio communications
according to criteria must be
performed.
Boolean
page 80
Astellia
Annexes
Outputs/
UPCS/ Audio/
Call profiling file
Outputs/
UPCS/ Audio/
IMSI list
Outputs/
UPCS/ Audio/
IMSI list file
Outputs/
UPCS/ Audio/
IMSI Profiling
Outputs/
UPCS/ Audio/
IMSI Profiling file
Outputs/
UPCS/ Audio/
Outputs/
UPCS/
Outputs/
UPCS/ Video/
Output directory
Video
Call profiling
Outputs/
UPCS/ Video/
Call profiling file
Outputs/
UPCS/ Video/
IMSI list
Outputs/
UPCS/ Video/
IMSI list file
Outputs/
UPCS/ Video/
IMSI Profiling
Outputs/
UPCS/ Video/
IMSI Profiling file
Cigale UMTS v6.0
File
Boolean
File
Boolean
File
Path
Group
This field indicates that all video

This checked indicates if the
extraction of video communications
(according to criteria) must be
performed.
the file containing the file for
extraction of video files according
to criteria.
This field indicates if the extraction
of video files according a list of
IMSI must be generated.
the file containing the IMSI list for
video files extraction.
extraction of video files
corresponding to communications
of listeners must be performed.
extraction of video files
of listeners.
which the video files must be
generated.
Advanced settings
All
Outputs/
UPCS/ Video/
Outputs/
UPCS/ Video/
Outputs/
Outputs/
Advanced
settings/
Outputs/
Advanced
settings/

extraction of audio files according
to criteria.
This field indicates if the extraction
of voice files according a list of
IMSI must be generated.
the file containing the IMSI list for
audio files extraction.
extraction of audio files
of listeners must be performed.
extraction of audio files
of listeners.
which the voice files must be
generated.
Output directory
Advanced settings
Error file (LOG)
Performance indicators periodicity
(min)
ExitCode
Database output
View output
TA output
If checked, the technical log will be

generated.
Default value is 15 minute,
Periodicity of perfomances
messages send to ASM
Exit code of the command
Database name
View output
TA output path
page 81
Boolean
Boolean
File
Boolean
File
Boolean
File
Path
Group
Boolean
Integer
Long
String
String
String
Astellia
Annexes
Text statistics output
Upcs audio output
Upcs video output
Text CDR output
Text PSDR output
Daily subdirectory
Cigale UMTS v6.0
Text statistics output path

Upcs audio output
Upcs video output
Text CDR output
Text PSDR output
Daily subdirectory generated from
the START_TIME_RANGE
parameter value if defined, else
from the today's date.
page 82
String
String
String
String
String
String
Astellia

Cigale Iu User Manual

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Cigale Iu User Manual

Hochgeladen von

Copyright:

Verfügbare Formate

Cigale user manual

Cigale user manual

Cigale Iu user manual

INSTALLATION AND STARTUP.....................................13

SETTING THE APPLICATION PARAMETERS...............23

STATE-MACHINE CONFIGURATION FILES..................43

IMMEDIATE PROCESSING OF RECORD FILES...........49

RESULT FILES ...............................................................59

Cigale UMTS v6.0

This chapter presents CIGALE.

Cigale UMTS v6.0

Cigale UMTS v6.0

Standardized installation and uninstallation procedures ;

Direct access to time ranges in the record files ;

Parameterization of the transitions state-machine and of the

Generation of statistics (XL2, EFF, XL1, Activity Analysis database

Extraction of User Plan CS and replay of voice communications

Graphical user interface ;

Display of messages intended for the user during processing ;

Possibility of interrupting the processing in progress (CIGALE then

Possibility of performing various consecutive processing operations.

Furthermore, CIGALE IU manages counters intended for the EFFICACE

Cigale UMTS v6.0

Example of a CIGALE screen

Cigale UMTS v6.0

PROCESSING BLOCK DIAGRAM

Statistical files for Cigale

Key file for Iub deciphering

MySql database for Activity

Binary file of frames

Oracle database for

Voice and video

the SCCP connections ;

Cigale UMTS v6.0

During processing of a record file, it is possible to generate the following files:

XL3: information on each connection and on their history at each

XL2: statistics on the state transitions ;

Cigale UMTS v6.0

the application (CIGALE.EXE) ;

Cigale UMTS v6.0

HARDWARE AND SOFTWARE CONFIGURATION

Dual Core CPU

Furthermore, it is recommended that you should have office automation

Cigale UMTS v6.0

Installation and startup

This chapter describes the various CIGALE IU installation steps, and

Cigale UMTS v6.0

Installation and startup

Cigale UMTS v6.0

Installation and startup

The CIGALE application can be started by

Cigale UMTS v6.0

Installation and startup

Software key input screen

Cigale UMTS v6.0

Installation and startup

Click on ?->License CIGALE IU Menu to display your license

Cigale UMTS v6.0

This chapter describes CIGALE IU user interface.

Cigale UMTS v6.0

The menus: allowing you to run the various processing functions

Processing information zone

User message zone

The various zones on the CIGALE IU window