Cigale GSM User Manual

Cigale GSM v6.
USER MANUAL
April 2013
Any full or partial representation or reproduction of this document, without the prior consent of Astellia is unauthorised.
CIGALE GSM V6.6 USER MANUAL
WARNING
The information contained in this manual is subject to change without prior notice and in no case
constitutes a contractual undertaking on the part of ASTELLIA.
ASTELLIA cannot be held responsible for slight variations between the manual and the product described
therein, nor for any accidental damages following use of said manual and product.
Every possible effort has been made to guarantee that this manual and the information contained therein
are as accurate as possible. However, in the case of the subsistence of any error(s), please do not hesitate
to contact us. We also invite you to get in touch with us to make any comments you may have as to
possible improvements.
For any maintenance operation, please contact:
ASTELLIA
: +33 (0)2 99 04 80 66
Fax: +33 (0)2 99 04 80 61
E-mail: support@astellia.com
Registered trademarks: The products and marks mentioned have been registered by their
respective owners.
Copyright ASTELLIA, April 2013

Under license from ASTELLIA
ALL RIGHTS RESERVED
Astellia Confidential
2 / 87
CONTENT
1.
2.
3.
4.
5.
6.
GENERAL INTRODUCTION ................................................................................................... 5

1.1. OVERVIEW OF CIGALE GSM........................................................................................ 5
PRODUCT COMPONENTS ..................................................................................................... 8
HARDWARE AND SOFTWARE CONFIGURATION ............................................................... 9
3.1. GENERIC HARDWARE AND SOFTWARE CONFIGURATION ...................................... 9
QUICK START ...................................................................................................................... 10
4.1. STARTUP ..................................................................................................................... 10
4.2. SOFTWARE PROTECTION ......................................................................................... 10
4.2.1. PRESENTATION ................................................................................................... 10
4.2.2. LICENSE INFORMATION ........................................................................................ 11
INTERFACE .......................................................................................................................... 12
5.1. ASTELLIA SYSTEM MANAGEMENT ........................................................................... 12
5.2. CONFIGURATION FILE DESCRIPTION ...................................................................... 13
5.2.1. PRESENTATION ................................................................................................... 13
5.2.2. ASTELLIA PARAMETERS EDITOR ............................................................................ 13
5.2.3. CIGALE GSM CONFIGURATION FILE ...................................................................... 14
5.2.4. OUTPUT_XL3.INI FILE .......................................................................................... 24
5.2.5. TOPOLOGY.......................................................................................................... 24
5.2.6. STATE-MACHINE CONFIGURATION FILE ................................................................. 27
5.2.7. NETWORK FILE .................................................................................................... 30
5.2.8. THE CALLED NUMBERS (PHONES.ADT) .................................................................. 30
5.2.9. TAC.TXT FILE ....................................................................................................... 32
5.2.10. FAC_EC.TXT FILE ............................................................................................... 32
5.2.11. FRAME EXTRACTOR ............................................................................................. 33
5.2.12. SDR_CLIENT .................................................................................................... 33
5.2.13. MEGACO : MGW MAPPING FILE ............................................................................ 33
5.3. POST QUERIES (POSTQUERIES.BAT) ...................................................................... 34
5.4. CONFIGURATION OF CUSTOM INDEXES IN ASM .................................................... 35
DATA DESCRIPTION ............................................................................................................ 36
6.1. PRESENTATION .......................................................................................................... 36
6.2. RESULTS OVERVIEW ................................................................................................. 37
6.2.1. LOG FILE ............................................................................................................ 38
6.2.2. LHO : LINKS BSIC AND BCCH DURING HANDOVERS ................................................ 38
6.2.3. XL3 : COMPLETE INFORMATION OF EACH CONNECTION .......................................... 39
6.2.4. PERIODIC XL3 : COMPLETE INFORMATION OF EACH CONNECTION FOR A PERIOD ..... 44
6.2.5. XL2 : STATISTICS ON THE NUMBER OF A INTERFACE MESSAGES ............................. 44
6.2.6. XLH : FLOW OF OUTGOING HANDOVERS TYPES FOR EACH CELL ............................. 44
6.2.7. XLF : FLOW OF INCOMING AND OUTGOING HANDOVERS FOR EACH CELL.................. 52
6.2.8. XLU : LOCATION UPDATE FLOWS ......................................................................... 56
6.2.9. XLV : SCCP, TRAFFIC AND CIC STATISTICS ......................................................... 57
6.2.10. XLT STATISTICS .................................................................................................. 62
6.2.11. SS : SUPPLEMENTARY SERVICES ......................................................................... 64
6.2.12. SMS : SHORT MESSAGES .................................................................................... 65
3 / 87
7.
8.
6.2.13. TIM : VALUES OF THE TIMERS .............................................................................. 67

6.2.14. EFF : EFFICACE COUNTERS STATISTICS................................................................ 67
6.2.15. XSC : SMS-CENTER STATISTICS ......................................................................... 68
6.2.16. XLE : 3G HANDOVERS ........................................................................................ 68
APPENDIX A: GLOSSARY ................................................................................................... 71
APPENDIX B: LOG ERROR MESSAGES............................................................................. 76
Revision
A
Date
12/03/13
Writer
MCE
Revisions
Object
Creation
Reference documents
- Installation manual
4 / 87
1.
GENERAL INTRODUCTION
1.1. OVERVIEW OF CIGALE GSM

CIGALE has been implemented with a view to allowing upgradeability 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.
Optimisation
Network resources Traffic
load
QoS & Benchmarking

Marketing
Operation & Maintenance

Clients Complaints
Better know users and

services
Trending &
Aggregation
Early failure detection

based on KPI VIEW
Network
Elements
Troubleshoot AA
Business
Customers
SLM
Roamers
VIP
All Mobiles
Services
Radio
Capture on A
interface
GSM Solution (figure 1)

CIGALE takes into account new requirements in terms of:
- standardized installation and uninstallation procedures ;
- direct access to time ranges in the record files ;
- time resynchronization of the record files' frames ;
- automatic detection of the A interfaces associated with the frames (the analyzer
connections do not have to be configured) ;
- processing robustness in the case of incomplete signalling links on the A interface;
- connection or disconnection of the analyzer's ports for processing ;
- management of several types of analyzer by means of external DLL files ;
- display of the activity of the analyzer's ports during processing of a record file ;
- grouping together of the unknown cells in the A interfaces used ;
5 / 87
parameterization of the transitions state-machine and of the associated statistics through

the use of external files ;
integration of timers (defined in an external file) on the basis of delimiters integrated in the
state-machine ;
external declaration of the GSM networks and statistical breakdown relative to the location
updates (XLU) according to those networks ;
management of messages without connections such as complete reset messages (RESET) or
a MIC (RESET_CIRCUIT) ;
generation of statistics associated with the supplementary services ;
generation of statistics associated with the short messages ;
generation of statistics associated with SCCP, CIC and TCH resources ;
filtering of called numbers and generation of associated statistics ;
display of the content of the CRC frames (and of the invalid frames) ;
generation of a file specific to the handover links which it has not been possible to
establish ;
generation of ping pong handover statistics with detection time parameters
generation of (*_R02.txt.) files for the Cigale View application
launch of the application in batch mode
automatic certification of the Home Mobile Country Code
Output for Cigale View: changed txt files format
Outpout for Activity Analysis: changed database server from ACCESS to MySql
Automatic detection of capture redundancy on A interfaces;
DTMF sequences in XL3 output
Possibility to disable SMS User Data for text and database outputs
AMR speech codec information
CDR frames decoders through Activity Analysis
MAP and Paging CDR in Activity Analysis
On-line processing mode and save restore contexts between two consecutive captures
3G/2G statistics
Compatibility for multi-interface 3G/2 databases (Iu/a)
ANSI CIC representation for View and Activity Analysis
[optional] Compatibility with Acterna 8630 analyser
[optional] automatic indexation of Activity database
Generation of 2G/UMA and UMA/2G handover statistics
MEGACO CDR in Activity Analysis (these CDR may be linked with A CDR with a configuration
file)
Multi Interface flow chart between A/MAP and A/ISUP in Activity Analysis
Statistics on Timer (defined in the file Times.adt) in Activity Analysis
ASM compatibility
Periodic statistics for T&A generation
Extended MTP compatibility
SDR generation for TT
SDR Generation for VIP Care
Enrichment of CDR with the AIU Enrichment module
Classmark type 2 and classmark type 3 decoding for statistics on mobiles
6 / 87
Statistics with MSCs in Pool

Multi-threaded analyzers
Nodes filtering (Processing filter by Point Code MTP)
Gs lite decoding
Motorola Iden support
Detailed decoding of all A interface messages
Full IP BSC support
7 / 87
2.
PRODUCT COMPONENTS
Cigale GSM decodes record files in order to extract the various messages and associated data (called
elements). These messages are decoded per protocol layer (MTP 2 and 3 levels, SCCP, BSSAP, Layer3, RP,
TP, SMS, and SS levels).
The various messages and associated elements make it possible to extract information such as:
- the SCCP connections ;
- the cells, the location areas detected ;
- the types of the current connections (terminating calls, originating calls, handovers,
location updates, short messages, etc.).
View
KPI
AA
Browsing
Troubleshooting
Viewers
CDR
KPI
Call Trace
Cigale Engine
Capture File
Ocean Probe
Network Interfaces
Cigale Layer Model (Figure 2)
8 / 87
3.
3.1.
HARDWARE AND SOFTWARE CONFIGURATION
GENERIC HARDWARE AND SOFTWARE CONFIGURATION
For an optimal use and comfort, the following configuration is recommended:

Characteristic Recommended configuration
CPU
Intel Xeon quad core or higher
Memory
8 GB.
Disk
500 GB.
Operating System Windows 2003 R2 SP2, Windows 2008 R2.
Astellia large site architecture:
Server
Unit
- Troubleshooting Database
- KPI results
- Cigale Engine
- EDX Storage
Processing
(Optional)
Ocean
- Capture
probe(s)
Multiple simultaneous accesses to dB

Secured remote access to raw files
Unit(s)
Fast results availability

Handle high traffic volumes
Capture multiple sources simultaneously

Maintained without impacting end-users
Added Value:
o Isolate functions: Capture, Processing, Database Server
o Improve performances, allow capturing and processing in parallel
o Service is not interrupted during maintenance
Typical Server/Processing Unit: Xeon bi-pro 3GHz
Server and processing can be split in 2 different Units (server and Process) for up to
20GB/day
9 / 87
4.
4.1.
QUICK START
STARTUP
You can run Cigale GSM by clicking on the associated icon in the program group created at installation or
indeed through the link created on your desktop:
Cigale GSM
The Cigale GSM application can be started by clicking on the START/PROGRAMS/Astellia/Cigale GSM menu
or by using ASM.
4.2.
SOFTWARE PROTECTION
4.2.1. PRESENTATION
When you have installed Cigale GSM 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.
This window displays a Site Code which is specific to the computer used. You will have to contact your
administrator and give him this Site Code so that he can give you a key authorizing execution and
instructions on how to install it.
10 / 87
4.2.2. LICENSE INFORMATION

Click on Help/About/Licence Information button on Cigale GSM Menu to display your license
information.
Licence box (Figure 3)

You access the Software key input screen and the possibility to Kill your current licence
(contact support before using this option).
11 / 87
5.
5.1.
INTERFACE
ASTELLIA SYSTEM MANAGEMENT
Astellia System Management features are:

- Ensure the reliability of Astellia monitoring system
- Centralized system administration of Astellia solution
- Centralized monitoring system process flow definition and synchronization
- Automated alerting system for a better fault management
This product is including several tools to ensure the right behavior of an Astellia solution set up to monitor
and optimize the QoS of your mobile network:
- Astellia System Controller: service on each workstation who control the distributed Astellia
solution;
- Astellia System Process Flow: set of component for System Controller which allows the
Astellia solution synchronization;
- Astellia System Management: to configure the Astellia solution;
- Astellia System Administration: to supervise the Astellia solution providing alerts when
needed
Sample of process flow architecture:
Process Unit
OCEAN
Server Unit
DB View
EDX (temp)
BCK, TEXT, XL3 (temp)
SDR DB
VIP Care DB
ASM
ASM
System
Controller
+
System
Process Flow
System
Controller
+
System
Process Flow
EDX
DB Activity Analysis
Trace Files
Roaming Files
SLM Files
EDX (backup)
ASM - System Controller

+ System Process Flow
EDX Server
ASM System Management

+ System Administration
12 / 87
OCEAN: Probe dedicated for capture and EDX file storage. The high captured data rate needs an exclusive
use of the CPU. On-disk data storage constraints need also that no other process disturbs disk access.
Process Unit (PU): Dedicated machine for Cigales processing. Processing time is more and more critical and
need the whole CPU resource.
Server Unit (SU): Dedicated machine for results storage. A MySQL server is running. Many other results
(such as reassembly EDX, stats view ) are also stored.
For some light configurations, PU and SU can be a single machine.
5.2.
CONFIGURATION FILE DESCRIPTION

5.2.1. PRESENTATION
State machine description

AUTOMAT, EVENTS,CAUSES
CIGALE.CONF
Output_xl3.ini
NETWORKS, TIMES, PHONES
Record files :
REC (K1103), RF5 (K1205),
EDX (OCEAN),PCAP,
Cells description
Topology.txt
CIGALE
Engine
Cigale GSM Configuration File (Figure 4)
5.2.2. ASTELLIA PARAMETERS EDITOR

The configuration files (*.conf) must be edited with Astellia Editor. Just double-click on the file cigale.conf
from an explorer will launch Astellia Editor.
Warning : This configuration file is not used when launching Cigale GSM by ASM, use ASM to update the
process flow configuration.
13 / 87
ToolBar :
Open / Save / Close
Parameters of the
selected section are
displayed 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.
5.2.3. CIGALE GSM CONFIGURATION FILE

The parameters are divided in 7 top sections.
- Component: Information about the Cigale version.
- Network: Settings about the network.
- Processing: Settings for the processing.
- Advanced settings: Advanced settings for the processing.
- Inputs: Options for OnLine mode and Real Time mode.
- Outputs: Defines which outputs Cigale must produce (AA, View, TA, text, UPCS).
- Debug options: Options used for debugging purpose.
For each parameter you have a tooltip. Just put the mouse over the parameters and a help text will be
displayed.
14 / 87
5.2.3.1.
Group
Component/
Component/
Component parameters
Name
Component name
Component version
5.2.3.2.
Network parameters
Group
Network/
Network/ Topology/
Name
Topology
Topology directory
Network/ Topology/
Networks File Path
Network/ Topology/
Network/ Topology/
MSS Pools used

Processing nodes
(Point Code)
Operator
Network/
Description
Description
Topology settings
This field indicates the location of the file containing
topology informations
This field indicates the location of the file containing
networks informations (networks.txt)
Enable or disable the use of MSS Pools.
List of processing nodes (defined by Point Code)
Operator
15 / 87
Network/ Operator/
Country code
(MCC)
Network/
Network/ Paging/
Paging
Paging Nb Repeat
CS
Paging Repeat
Time CS
Hand-Over
Limited duration for
ping pong handover
(s)
Network/ Paging/
Network/
Network/ Hand-Over/
Network/
Network/ TAC-IMEI/
TAC-IMEI
TAC-IMEI file
5.2.3.3.
Group
Processing/
Processing/
Decoding/
Processing/
Decoding/
Processing/
Decoding/
Processing/
Processing/
Megaco/
Processing/
Megaco/
Processing/
Megaco/
Processing/
Megaco/
Processing/
Megaco/
Processing/
Megaco/
Processing/
Megaco/
Purge MEGACO/
Determines the country code [MCC] of mobile networks for

which the users should not be considered as roamers. The
users of a network with a different country code than that
indicated will, thus, be considered as roamers. By default,
this field is empty, which renders it inactive (no roamer
identification). For example, indicator 208 signifies that all
the users of the network which is not French shall be
considered as roamers. This code should be between 0
and 999
MSC maximum number of PAGING repetitions for a paging
procedure.
MSC PAGING repetition period.
Hand Over settings
Specifies the number of seconds, under which an incoming
communication can leave the cell per handover, as being
abnormally short, and thus, may correspond to a ping pong
handover. This field has a value of 10 seconds, by default.
The number of seconds must be between 0 (no results)
and 50.
TAC / handset type mapping
File for TAC / handset type mapping. Default value is
ASTELLIA Shared directory
Processing settings
Name
Decoding
Standard
Description
Decoding
ETSI , ANSI are availables. Default value is ETSI.
MTP2 extended
MTP2 extended can be used in HSL processing. Default

value is false.
Apply a full IP configuration to all captured BSCs. Traffic
stats per CIC will be counted on PCM 0 TS 0
Enable or disable the Megaco processing.
Generation of independent Megaco CDR.
Full IP BSC
Megaco
Megaco CDR
generation
Megaco CDR
Integration
Megaco Statistics
MGW mapping file
Megaco threshold
statistics time
Purge MEGACO
Purge time out
MEGACO
(Seconds)
Integration of MEGACO Information to CDR.

Generation of Megaco Statistics in AA.
This field indicates the location of the file containing MGW
mapping file
Megaco treshold statistics time for failed call in seconds
(default value is 10s)
Purge MEGACO transaction
Purge time out of containers in second for MEGACO
transaction purge. By default this field equals 600 (10 min)
16 / 87
Processing/
Megaco/
Purge MEGACO/
Processing/
Processing/
Iden Decoding/
Processing/
Processing/
GS Decoding/
Processing/
GS Decoding/
Purge number of
set MEGACO
Number of containers for MEGACO transaction purge. By

default this field equals to 6
Iden Decoding
FAC-EC-IMEI file
Enable or disable the Iden processing.

File for FAC-EC / handset type mapping for Iden. Default
value is ASTELLIA Shared directory
Enable or disable the GS processing.
MSC maximum number of PAGING repetitions for a paging
procedure.
MSC PAGING repetition period.
GS Decoding
Paging Nb
Repeat GS
Paging Repeat
Time GS
5.2.3.4.
Advanced settings
Group
Advanced settings/
Name
Treshold trace multi
capture
Advanced settings/
Detailled display of
handovers
Advanced settings/
Detail SMS User

Data
Purge
Timer purge
connexion SCCP
Long duration call
timer (s)
Advanced settings/
Advanced
settings/Purge
Advanced
settings/Purge
Advanced
settings/Purge
Advanced
settings/Purge
Group
Inputs/
Inputs/
Settings/
Inputs/Settings/
Inputs/Settings/
Inputs/Settings/
Process max
memory threshold
(MB)
Process Minimum
Free memory after
purge (MB)
Description
Detection of capture redundancy by A interface based on the
openening of connexions by probe analyzer ports. Default
value is 80. Value in [0; 100] to enable the process.
Redondancy is traced if the threshold of failed connections is
higher or equal to defined value. Value -1 to disable the
process
If this field equals true, the statistics relative to the handovers
(XLH and XLF) are generated in detail (including, in
particular, the breakdown of intra-cell handovers according to
the causes, and the taking into account of the Directed Retry
cause for all types of handover). By default this field equals
false
detail or not User Data filed in sms output file and database
Purge settings
[Timer value for SCCP connection purge] : By default this
field equals 2500 ms
Limit duration of a connection if a purge is started. All
connections which are opened since more than this timer are
purged. By default this field equals 7200 s.
If this memory treshold is reached, purge is started. By
default this field equals 1500 MB.
Minimun free memory to get during purge. If this value is not
reached, engine is stopped. By default this field equals 100
MB.
5.2.3.5.
Inputs settings
Name
Settings
Input
Description
Input setting
Capture
Comment
Analyzer
Start time
Comment
Analyzer to use for treat
Start of the time range
17 / 87
Inputs/Settings/
Inputs/Settings/
Inputs/
Inputs/
Process Mode/
Inputs/
Process Mode/
Online mode/
Inputs/
Process Mode/
Online mode/
Inputs/
Process Mode/
Online mode/
Inputs/
Process Mode/
Online mode/
Inputs/
Process Mode/
Online mode/
Inputs/
Process Mode/
Online mode/
End time
Real time
streaming
Process Mode
Online mode
End of the time range

Real time streaming
Online timeout (s)
Processing is stopped if no new file arrives before timeout

seconds. Default value is 3600 seconds (1 hour)
Minimum remaining
time polling
(seconds)
Online flag
While processing in polling mode, the Cigale engine will not

wait for a new capture if the remaining time to process is
smaller than this value.
Flag File
Max duration for

connection
attempts (min)
Number of
connection
attempts by minute
Number of attempts
to read a frame
Max duration for connection attempt (in minutes)
5.2.3.6.
Group
Outputs/
Outputs/ Settings/
Outputs/ Settings/
Name
Settings
Output radical
Output mode
Outputs/
Outputs/
Activity Analysis/
Outputs/ Activity
Analysis/
Activity Analysis
MySQL
parameters
MySQL
parameters/
Hostname
MySQL
parameters/
Outputs/
Activity Analysis/
Process mode options

Enable Online mode
Number of connection attempts by minute
Number of attempts to read a frame
Outputs settings
Description
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 server name, port, login and password. You can test the
connection with the test button.
Define hostname
Define port
18 / 87
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/
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/
Outputs/
Activity Analysis/
Outputs/
Activity Analysis/
Outputs/
Port
MySQL
parameters/
Login
MySQL
parameters/
Password
Central database
parameters
Central database
parameters/
Hostname
Central database
parameters/
Port
Central database
parameters/
Login
Central database
parameters/
Password
Server name
used by viewers
Activity Report CDRs

Bulk insert size
Level of detail
Define login
Define password
Central Database server name, port, login and password. You

can test the connection with the test button.
Define hostname
Define port
Define login
Define password
Define 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.
Activity Report - CDRs
Number of CDRs inserted at a time. A value too low will have a
negative effect on performance. Default: 512
Level of detail
Trace detailed
activity
All paging
procedures
MAP Cancel
Location (LOR)
SMS
Choose the correct Level of detail
SQL post
processing?
Timers
If checked, queries will be sent to Activity Analysis after the

processing
Generates time counters.
Location Update
on success
Real time
database access
Imsi index
Processing Location Update on success
Imei index
All paging procedures

MAP Cancel Location (LOR)
SMS
Allows or not access to the Database while being generated. If

activated, the processing will be slightly slowed down.
Used to accelerate times of requests in Activity Analysis
Databases.
19 / 87
Activity Analysis/
Outputs/
Activity Analysis/
Outputs/
Activity Analysis/
Outputs/
Activity Analysis/
Outputs/
Outputs/
Detailed decoding/
Outputs/
Detailed decoding/
Outputs/
Detailed decoding/
Outputs/
Outputs/
Frames Archiving /
Outputs/
Outputs/
Statistics files/
Detailed decoding
Hostname
Databases.
Databases.
Databases.
Databases.
Detailed decoding
Define hostname
Port
Define port
Frame server
alias
Frames Archiving
Archive Path
Define frame server alias
Statistics files
CDR (XL3)?
Statistics files
If checked, the XL3 statistics file will be generated when a record
file is processed. It should be noted that generating an XL3 file is
quite time consuming.
This field indicates the directory in which the CDR statistics files
must be generated.
If this field equals true, the mAP messages Cancel Location is
decoded and displayed in the XL3 file. This option is software
proteceted. Notice that you may tick XL3 option to use Loss of
roamer option
Value in minutes of generation of the periodical XL3 files
Cell index
LAC index
Start Event index
Outputs/
Statistics files/
Outputs/
Statistics files/
CDR Statistics
Output directory
MAP Connections
(Cancel Location)
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Periodical CDR
Periodical CDR
Output directory
Flag Extension
List
Output directory
Frames Archiving
The directory where the archive files will be created
This field indicates the directory in which the CDR statistics files
must be generated.
Flag files to create
Resources (XLT)
This field indicates the directory in which the statistics files must
be generated.
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, the traffic statistics will be generated.
Efficace (EFF)
If checked, the EFFICACE counters will be generated.
Handovers (XLH,
XLF)
Handovers links
(LHO)
Inter System
Statistics (XLE)
Location updates
If checked,statistics on the flow of Cell-Update will be generated.
State-machine
transitions (XL2)
Timers (TIM)
If checked, the Handovers links will be generated.

If checked, the Inter System Statistics will be generated.
If checked, the statistics on the Routing Area Updates will be
20 / 87
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Statistics files/
Outputs/
Outputs/ View/
Outputs/ View/
Outputs/
Outputs/ TA/
Outputs/ TA/
Outputs/ TA/
Outputs/ TA/
Outputs/
Outputs/ TT/
Outputs/ TT/
Outputs/ TT/
Outputs/ TT/
Outputs/ TT/
Outputs/ TT/
Outputs/ TT/
Outputs/ TT/
Outputs/ TT/
Outputs/ TT/ Type
Filter/
(XLU)
Short messages
(SMS)
SMS Center
efficiency (XSC)
Supplementary
services (SS)
Miscellaneous
statistics (XLV)
SDRs
View and
Statistics in AA
Output directory
Automatic daily
subdirectory
TA
TA Periodicity
Output directory
Automatic daily
subdirectory
TA periodical zip
files destination
path
TT
TT server
Protocol
Hostname
Port
Login
Password
TT V3
TT SDRs record
path
Type Filter
TT SDR Type
filter file
Outputs/ TT/
TT Disallow
Duplicates
Outputs/ TT/
TT Message Time
Out
TT Message
Retry
TT Session Test
Time Out
Outputs/ TT/
Outputs/ TT/
generated.
If checked, the Short messages will be generated.
If checked, the SMS Center efficiency will be generated.
If checked, the Supplementary services will be generated.
If checked, some ATM statistics are produced in a XLV file.
If checked, some SDRs are produced in a txt file. SDR Sender
output will be desactivated.
View and Statistics in AA
This field indicates the directory in which the Cigale View files
must be generated.
Use daily statistics subdirectory.
Trending And Aggregation
Value in minutes of generation of the TA files.
This field indicates the directory in which the TA files must be
generated.
Use daily statistics subdirectory.
If checked, 'Output directory' is used to generate temporary files.
Only for files with View format (.txt).
Trouble Ticketing SDRs
Trouble Ticketing SDRs
Define protocol
Define hostname
Define port
Define login
Define password
Defined if the type of server TT to communicate with is a TT v3
server.
This field indicates the location of the path containing the SDRs
which couldn't have been send to 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.
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 time-based 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.
Life time, in milliseconds, of a session test message that is sent
to the TT server. This number must lower or equal to 4 294 967
21 / 87
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
TT SDR Send
Packet Time Out
Period of sdr file
creation
Number of
attempts to
connect
Delay between
two connection
attempts
TT SDR Max
buffer size
VIP Care
VIP Care server
Protocol
Hostname
Port
Login
Password
VIP Care Off Line
VIP Care SDRs
record path
Outputs/ TT/
Outputs/ TT/
Outputs/ TT/
Outputs/ TT/
Outputs/ TT/
Outputs/
Outputs/ VIP Care/
Outputs/ VIP Care/
Outputs/ VIP Care/
Outputs/ VIP Care/
Outputs/ VIP Care/
Outputs/ VIP Care/
Outputs/ VIP Care/
Outputs/ VIP Care/
Outputs/ VIP Care/
Ftp hostname for

sdr file
Outputs/ VIP Care/
Ftp folder path
Outputs/ VIP Care/
VIP Care Disallow

Duplicates
Outputs/ VIP Care/
VIP Care
Message Time
Out
VIP Care
Message Retry
VIP Care Session
Test Time Out
Outputs/ VIP Care/

Outputs/ VIP Care/
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.
Time, in milliseconds, between the 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.
Time, in milliseconds, between the first session close request
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
Delay between two connection attempts to the TT server
Maximum size of the buffer when TT server is offline

VIP Care SDRs
VIP Care server parameters (IP address, login, password, port)
Define protocol
Define hostname
Define port
Define login
Define password
No connection to VIP Care server. SDRs are sent in a file.
This field indicates the location of the path containing the SDRs
in offline mode or the SDRs 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
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 time-based duplicates are allowed; 1, otherwise.
Life time, in milliseconds, of a 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.
Life time, in milliseconds, of a session test message that is sent
to the VIP Care server. This number must lower or equal to 4 294
22 / 87
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
VIP Care SDR
Send Packet
Time Out
Period of sdr file
creation (min)
Outputs/ VIP Care/
Outputs/ VIP Care/
Outputs/ VIP Care/
Outputs/ VIP Care/
Outputs/ VIP Care/

Outputs/ VIP Care/
Outputs/ VIP Care/
Outputs/ VIP Care/
IMSI Filtering
Activation/
Outputs/ VIP Care/
IMSI Filtering
Activation/
Outputs/ VIP Care/
IMSI Filtering
Activation/
Outputs/ VIP Care/
IMSI Filtering
Activation/
Outputs/ VIP Care/
Number of
attempts to
connect
Delay between
two connections
attempts
SLM SDR Max
buffer size
VIP Care options
IMSI Filtering
Activation
VIP Care Upload
Path
967 295.
Time, in milliseconds, between the first session open request
Time, in milliseconds, between the 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.
Time, in milliseconds, between the first session close request
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)
Period covered by each SDR file in minutes. SDR files are
generated in offline mode or when the connection to VIP Care
Server is bad or lost.
Number of attempts to connect to VIP Care server
Delay between two connections attempts to the VIP Care server
Maximum size of the buffer when VIP Care server is offline

General options for VIP Care
If check, Vip Care SDR are filtered by IMSI
This field indicates the location of the uploaded file containing the
IMSI followed by VIP Care
VIP Care IMSI

filter file
This field indicates the name of the file containing the IMSI
followed by VIP Care
ByPass
If check, SDR of types defined in the ByPass file are send even if
their IMSI are not followed by VIP Care
VIP Care SDR

Type filter file
This field indicates the name of the file containing the type of
SDR which are ByPass by VIP Care. This file is located in Cigale
directory.
The Reprocessing mode is used to reprocess specified data that
should have been processed from another engine (called here
original engine). This mode can be used with an online or an
offline connexion
Must indicate the installation path of the original engine of
reprocessed data. For example, C:\ASTELLIA\Cigale UMTS
Iu_1\
Advanced settings
Reprocessing
Outputs/ VIP Care/

Reprocessing/
Original engine
path
Outputs/
Advanced
settings
23 / 87
Outputs/ Advanced
settings/
Performance
indicators
periodicity (min)
5.2.3.7.
Default value is 15 minute, Periodicity of perfomances messages

send to ASM
Debug options
Options under this node are used for debugging purpose only and should be left untouched.
5.2.4. OUTPUT_XL3.INI FILE
This file configures the CDRs output file. Its composed by two sections:
- [General]
Prefix output filename: defines a prefix for the output file name;
FILEHEADER:
LINEHEADER:
SEPARATOR: specifies the separator between the columns, the possibilities are ; or TAB
- [KPIs]
KEY = value: defines the columns, KEY must be unchanged; value is the column name and if value is null
the column is not generated in the file
output_XL3.ini file example :

[General]
Prefix output filename=
FILEHEADER=1
LINEHEADER=1
SEPARATOR=;
[KPIs]
END_DATE_TIME=End of\ttransaction
START_DATE_TIME=Start of\ttransaction
DURATION=Duration
NAME1=Name 1
NAME2=Name 2
TYPE1=
TYPE2=
PC1=PC 1
PC2=PC 2
5.2.5. TOPOLOGY
This file is used when processing record files to name the detected 2G cells (GSM), designate their BSC and
MSC Number and LAC and fill in their BSIC and BCCH. These files contain also names of the detected 3G
cells (UMTS) and UMA cells.
24 / 87
5.2.5.1.
Topology file (Topology.txt)
To select a cell Topology file (also known as cell data base), use the Options: Cell data base menu or the
button. A selection box allows you to choose the file:
Topology file selection window (Figure 5)

The topology file is a text file identified by one of its title lines:
bsc_rnc_namecell_name
cell_id lac
bsic
bcch cell_type
annexe_1
bsc_pc
rnc_id annexe_2
annexe_3
azimuth
beamwidth
cluster_name_1
cluster_name_2
cluster_name_3
constructor
dl_arfcn
dl_scrambling_code
eirp
height lac_label
latitude_or_x longitude_or_y max_power mcc
micro_macro mnc msc_name
network_name on_off papu_name pcu_name
rac
rac_label
sac
sgsn_name
tilt
urban_rural
Column name
bsc_rnc_name
cell_name
cell_id
lac
bsic
bcch
cell_type
bsc_pc
Type
Mandatory
Mandatory
Mandatory
Mandatory
Mandatory 2G/UMA
Mandatory 2G/UMA
Optional 2G
Mandatory 3G/UMA
Mandatory 2G/UMA
Description
name of the BSC that the 2G cell is attached to
2G cell's name (limited to 255 caracters)
identification number (CI ; 0 - 65535)
location area code (0 65535)
cell's BSIC (0 63) ; 0 means unknown
cell's BCCH (0 1023) ; 0 means unknown
type of cell (empty (2G) / UMA / 3G)
Example
MyBSC
MyCell
28461
12654
15
36
UMA
BSC point code (0 65535)
3957
25 / 87
rnc_id
Mandatory 3G
code of the RNC that the 3G cell is attached to
The CI,, LAC, BSIC, BCCH and RNC Id values are indicated as decimals.
Example of cell data base file (contains 2G and 3G cell description):
bsc_rnc_name bsc_pc rnc_id cell_name
cell_id
BSC 1
125
MyCell1
3512
BSC 2
126
MyCell2
45818
BSC 2
126
MyCell3
45818
BSC_UMA 2
165
MyCellUMA1
7580
BSC_UMA 2
165
MyCellUMA2
7580
BSC_UMA 2
165
MyCellUMA3
7580
BSC 2
126
MyCell4
40336
BSC 2
126
MyCell5
40336
BSC 1
125
MyCell6
3512
BSC_UMA 1
164
MyCellUMA4
3577
BSC_UMA 1
164
MyCellUMA5
3577
BSC 1
125
MyCell7
23577
BSC 1
125
MyCell8
23577
BSC_UMA 1
164
MyCellUMA6
5658
RNC_TEST1
568
SAI_TEST1
15652
RNC_TEST1
568
SAI_ TEST2
15652
5.2.5.2.
lac
3967
3958
3958
3958
3958
3958
3958
3958
3967
3967
3967
3967
3967
3971
4545
4545
bsic
0
0
0
0
0
0
0
0
0
0
0
0
0
0
bcch
0
0
0
0
0
0
0
0
0
0
0
0
0
0
568
cell_type
UMA
UMA
UMA
UMA
UMA
UMA
3G
3G
Additional parameters
CigaleGSM can also group cells into clusters via the annexe labels. Up to 3 different groups can be
configured, and these groups will appear in CigaleView and Statistics in AA.
Example of cell data base file:
bsc_rnc_na
me
bsc_pc
BSC 1
BSC 2
rnc_id
cell_name cell_id
lac
bsic
bcch
cell_type
125
MyCell1
3512
3967
urban
900
126
MyCell2
45818
3958
rural
900
BSC 2
126
MyCell3
45818
3958
urban
900
BSC 2
126
MyCell4
40336
3958
Airport
urban
1800
BSC 2
126
MyCell5
40336
3958
Airport
rural
1800
BSC 1
125
MyCell6
3512
3967
rural
1800
BSC 1
125
MyCell7
23577
3967
rural
1800
BSC 1
125
MyCell8
23577
3967
urban
1800
Airport
RNC_TEST1
568
SAI_TEST1 15652
4545
3G
RNC_TEST1
568
SAI_
TEST2
4545
3G
15652
Annexe_1 Annexe_2 Annexe_3
Basically 3 groups were defined:

- the first group (annexe_1) differentiates the cells covering the airport area with the string
airport
- the second group (annexe_2) differentiates urban and rural cells
- the third group (annexe_3) specifies if the cells are 900 or 1800
26 / 87
Note that Annexe_1 and Annexe_2 contain a string of characters whereas Annexe_3 can only contain a
numeric value.
5.2.5.3.
Enhancing the cell data base during processing
During processing, the cell data base may be completed or modified. You will then be informed by
messages in the technical log.
It should be noted that these updates will only be effective for the current processing operation.
When a cell is detected that has not been filled in (identified by its Cell Identity code), this cell will be added
to the data base and named by concatenating the character string "Cell_" with the corresponding CI
number :
Message informing you that there is a new cell
If this cell is assigned to a connection, the BSC with which the connection is associated is assigned to the
cell :
Message informing you that a BSC has been assigned to a cell
Likewise, if this cell was already linked to a BSC, it is transferred to the new BSC.
Cell transfer
When a handover link is established, if the cell concerned was the only candidate cell, it is validated (cell
certification). Furthermore, its BSIC-BCCH pair is checked against the pair resulting from the Layer 3
protocol Handover Command message. If these pairs are different, the new BSIC-BCCH pair is assigned to
the cell :
Message informing that the BSIC-BCCH pair has been modified
Likewise, when several cells were candidates, but only the cell concerned by the handover is not certified, it
is certified and, if necessary, its BSIC-BCCH pair is modified.
The names of the cells that have been certified are then preceded by the "*" character in the statistics files.
Cell certifications and BSIC-BCCH pair modifications may optionally be reported in the LHO file.
5.2.6. STATE-MACHINE CONFIGURATION FILE
5.2.6.1.
Presentation
The statistics obtained from 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.
Besides the SCCP level messages relative to connections, the changes to the connection contexts concern
the higher level messages such as BSSAP, Layer 3, RP or TP.
27 / 87
(1)
(2)
(3)
(7)
(4)
(5)
(6)
(7)
BEGIN
BEGIN
BEGIN
CMSRQ _NC
CMSRQ _EC
PAGRP
OC_CMS_REQ AUTRQ
OC_CMS_REQ CMCMD
OC_CMS_REQ CMSA
OC_CMS_REQ
*
OC_CMS_REQ 1 NbOc NbOCnc

OC_CMS_REQ 1 NbOc NbOCec
TC_PAGRP
1 NbTc
OC_AUT_REQ1
OC_CIM_CMD
OC_CIM_CMP
OC_CMS_REQ
(1), (2)
BEGIN
OC_CMS_REQ
(4)
OC_AUT_REQ1
(3)
TC_PAGRP
(6)
(5)
OC_CIM_CMP
OC_CIM_CMD
Automat process (Figure 6)
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.
5.2.6.2.
Automat files
The state machine is configured by three external binary files (AUTOMAT.BDT, CAUSES.BDT, EVENTS.BDT).
They must be contained in the CIGALE execution directory when you start up the application.
The 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.
The AUTOMAT.BDT file also contains the declaration of the timers intended for the EFFICACE file. When it
has read the state-machine, CIGALE reads the TIMES.ADT file. This file is used to delimit state-machine
transitions in order to generate statistics on the durations between the marked transitions.
Remark: These files must not, in any event, be modified. They are supplied with the CIGALE application and
your administrator is responsible for their maintenance.
5.2.6.3.
Timer file (times.adt)
In CIGALE, an external file called TIMES.ADT allows you to declare timers between state-machine states for
which you want to generate specific statistics in the XLV file and in the TIM file and in AA database and in
Cigale View and T&A Files.
A timer is defined by a start state and an end state. Each time CigaleGSM goes through the pre-defined
start-state for a given connection, the start timestamp for the relevant timer is stored. When CigaleGSM
28 / 87
goes through the pre-defined end-state for that same connection, the stored timestamp is deducted from
the current timestamp, and the connection is then associated with the timer value.
At the end of the processing campaign, CigaleGSM generates 4 statistics for all timers
- Number of associated connections
- Average duration
- Maximum duration
- Minimum duration
Furthermore, a distinction is made between timers relative to the BSCs and to the cells. The timers will then
be aggregated per BSC or per cell.
Below you will find a list of timers declared in the TIMES.ADT file.
The first columns in the file identify the transitions:
- initial state ;
- the message ;
- the message extension, if applicable ;
- the cause associated with the message, if applicable.
You will then find:
- the timers network aggregation : BSC or Cell ;
its identification :
for start timers, a start identifier must be specified ;
for end timers, you must declare the timer's name (to be displayed in the statistics) and
the associated start identifier. The types of the start and end timers must of course be
the same.
CAUTION :
This list is not exhaustive and cannot serve as absolute reference due to the parameterable
nature of timers.
Example:
STATE
MESSAGE
EXTENSION
CAUSE
TYPE
TIMER
ASCMP_1
ASCMP
Cell
ASCMP
Cell
ASCMP_2
ASCMP
Cell
ASCMP_3
HOCMP
Cell
HOCMP
HOPER
Cell
HOPER_IN
CLCMD
HoS
Cell
Oc_InterCel(ASCMP_1)
CLCMD
HoS
Cell
HoInterCel_InterCel(HOCMP)
CLCMD
HoS
Cell
HoIntraCel_InterCel(HOPER_IN)
CLCMD
Cell
Oc_Clr(ASCMP_2)
CLCMD
Cell
HoInterCel_Clr(HOCMP)
CLCMD
Cell
HoIntraCel_Clr(HOPER_IN)
HOPER
_OUT
Cell
Oc_IntraCel(ASCMP_3)
HOPER
_OUT
Cell
HoInterCel_IntraCel(HOCMP)
HOPER
_OUT
Cell
HoIntraCel_IntraCel(HOPER_IN)
_IN
29 / 87
In the above example the timer called Oc_InterCel starts upon reception of an ASCMP (Assignment
Complete) message in any state, and stops when a CLCMD (Clear Command) with cause HoS (handover
successful) is seen in the same connection. This timer is calculated at the Cell level.
Note that several timers start upon reception of an Assignment Complete message, it is better in this case
to duplicate the ASCMP lines to start several timers (in the above example: ASCMP_2, ASCMP_3).
The generic character * allows you to declare any initial state. It can also (but not simultaneously) be used
to declare the messages. Note that the wildcard * cannot be used in the Extension or in the Cause column.
5.2.7. NETWORK FILE
In CIGALE, an external file called NETWORKS.TXT allows you to define the GSM networks using their MNC
code (Mobile Network Code) and MCC code (Mobile Country Code).
Now, the MNC and MCC codes are also extracted during decoding, and they are associated with the value
of the LAC. The XLU statistics are then broken down according to the MNC and MCC pairs in addition to the
value of the LAC.
The definition of the GSM networks (and therefore of the corresponding MNC and MCC pair) makes it
possible to display in plain language the names of the networks to which the LACs are attached in the XLU
file.
Furthermore, this information is also used to display in plain language the subscribers' origin network.
The NETWORKS.TXT file must be contained in the CIGALE config directory so that it can be loaded when you
start up CIGALE.
Below you will find a list of the GSM networks declared in the NETWORKS.TXT file along with the following
for each one:
- its name which will be used in AA, T&A and Cigale View ;
- its MCC (Mobile Country Code) ;
- its MNC (Mobile Network Code).
GSM network
MCC
MNC
A, max.mobil.
232
03
A, A1 (PTV)
232
01
AL, AMC mobil
276
01
AND, Mobiland
213
03
5.2.8. THE CALLED NUMBERS (PHONES.ADT)

The called numbers that you want to have counted in Cigale View (Phones view) are declared in the
PHONES.ADT file.
The numbers written in this file are not necessarily complete numbers (e.g. 0142010101). Certain
numbers can include generic characters which are used to replace any character or group of characters.
The following four generic characters can be used:
- ! : to replace a character. For example, the number 123 will be equated to the number
1!3 declared in the PHONES.ADT file for the statistics ;
30 / 87
$ : to replace a group of characters at the end of the number. For example, the number
012345 will be equated to the number 012$ declared in the PHONES.ADT file for the
statistics.
? : to replace a character. For example, if the number 1?3 is declared in the PHONES.ADT
and if numbers 123, 143 and 163 are dialled, these numbers will all appear in the XLV result
file.
@ : same thing as for ? but replaces several characters. Declaration of 012@ will cause to
list every number beginning by 012.
Numbers including the generic characters ! or $ will be displayed in the statistics by accumulating the
occurrences of the numbers that have been equated to them whereas every number corresponding to a
number including the generic characters ? or @ will be displayed in the statistics.
These generic characters can be used simultaneously for the same number.
However, the fact of using generic characters means that there are no priority rules in the event that a
number detected during processing can be equated to several numbers declared in the PHONES.ADT file
(e.g. the number 012345 is detected, and at least two of the numbers 01$, 012!45 and 012345 have
been declared in PHONES.ADT).
Furthermore, the international numbers (TONE = international) are preceded by the "+" character.
It should be noted that in the statistics files the called numbers are preceded by the "" character.
Below you will find an example of a list of called numbers:
NUMBER
COMMENT
NAME
777
voicemail
Voicemail
0492$
Test_team
Test_team
014!25$
Range_014
Range_014
0836680724
John_Smith
John_Smith
04!1583030
Just_a_test
Just_a_test
Here are a few examples of what numbers match the configured ranges above:
Destination
number
Match?
explanation
777
Matches voicemail
778
Doesnt
anything
0492123
Matches test_team
Starts with 0492, and is followed by any number of digits
0492123456789
Matches test_team
Starts with 0492, and is followed by any number of digits
01482545678
Matche Range_014
Starts with 014, followed by exactly one digit and then 25 and then any number
match
of digits
014002545678
Doesnt
match
014 is followed by 2 digits, thus the range_014 cannot apply
anything
31 / 87
5.2.9. TAC.TXT FILE

This file contains the names of Manufacturer and Type of mobile. The first column is the manufacturer, the
second is the type of mobile. And the third is the TAC (Type Approval Code). The TAC can be 6 or 8 digits
length. (By default the file is present in C:\Program Files\Astellia\Shared\TAC.txt)
The
TAC
mapping
file
is
a
text
file
"TAC\tManufacturer\tType\tTechno\tUA\tComments" :
TAC
00103400
00256841
00350016
00350019
00350029
Manufacturer
Palm
Sony Ericsson
Siemens
Siemens
Motorola
Type
Treo 600
K608
SL42_45
A36
T260
identified
Techno
UA
by
this
header
line:
Comments
--------------------------
5.2.10. FAC_EC.TXT FILE

This file is an extension of the TAC file and has the exact same role (associates an identifier with a mobile
phone manufacturer and type), but is specific to iDEN Networks.
iDEN-specific handsets have a different encoding for their IMEI, and the equivalent of the TAC information
is stored in the Factory Code (FAC) and Equipment Class (EC):
When configured for iDEN networks, CigaleGSM can point to 2 mapping files : the regular TAC.txt file and
the FAC_EC.txt file. In case no match is found in the TAC file, the FAC_EC file is used to find the handset
manufacturer and type.
The content of this file is the following :
32 / 87
The
FAC_EC
mapping
file
is
a
text
file
"FAC_EC\tManufacturer\tType\tTechno\tUA\tComments" :
TAC
Manufacturer
000117
Motorola
000118
Motorola
000119
Motorola
000112
Motorola
000122
Motorola
Type
i85s
i80s
i50sx
i55sr
i50sx
Techno
iDEN
iDEN
iDEN
iDEN
iDEN
UA
identified
by
this
header
line:
Comments
5.2.11. FRAME EXTRACTOR

Frame Extractor Agent is a client-server based architecture. Its goal is to abstract Activity Analysis of the
way of retrieving binary frames and also to restore context after restarting Cigale GSM. Thus, Client part
module is directly included into Activity Analysis and Cigale GSM, while Server part is running on data
server (server dedicated to files storage).
Using SFTP mode, the SFTPMountEntry value is mandatory. It both sets the entry point the client uses for
SFTP transfer and "Frame Extractor Agent destination directory into which temporary EDX files are written.
[General]
CommandBufferSize=100000
CommandTimeOut=600000
SocketLoopTimeOut=500
[SFTP]
Login=astframeextract
Passwd=astframeextract
Port=22
5.2.12. SDR_CLIENT
The parameters allow to configure both servers are described in Cigale.conf file.
Please refer to section 5.2.3 Cigale GSM Configuration file for more information.
5.2.13. MEGACO : MGW MAPPING FILE
There is an optional configuration file for Megaco Decoding specified in the configuration Processing /
Megaco / MGW mapping file. This file contains the mapping of the MGW IP address, RNC id and PCM.
Without this mapping file, it is impossible to associate a PCM number on the MGW with a PCM number on
the AN/CN termination side. This mapping file also contains information for IuCS terminations.
The file is a text file, tab-separated and contains several sections:
- A media gateway section identifying the MGW with its IP addresses or Point Codes
- A RNC part that is listing the RNCs linked to this MGW with their RNC id
- The BSC mapping section giving a complete PCM mapping
Heres an illustration of what this mapping file does:
33 / 87
Heres an example of such a file with 2 media gateways:

[MGW_6011]
PointCode=6011
Mapping=BSSAP
Mapping=BSSAP
Mapping=BSSAP
Mapping=BSSAP
Mapping=BSSAP
Mapping=BSSAP
4419606
4419607
4419608
4419609
4419610
4419611
2192
2192
2195
2195
2191
2191
22
23
26
27
27
24
[MGW_6012]
PointCode=6012
Mapping=BSSAP
Mapping=BSSAP
Mapping=BSSAP
Mapping=BSSAP
4419608
4419609
4419610
4419611
4146
4146
4146
4140
15
7
11
5
5.3.
POST QUERIES (POSTQUERIES.BAT)
Cigale GSM allows launching a script in post queries. This script is present in Cigale GSM installation
directory PostQueries.bat.
This batch is launched by CigaleGSM at the end of the processing with one argument: the name of the AA
database.
The script could start for instance automatic SQL queries launched at the end of post-process in order to
provide additional information retrieved from Activity Report database (CDRs).
Heres an example of a PostQueries.bat file that queries the AA database in order to dump all distinct IMSIs
found in the CDRs into a text file:
34 / 87
C:\Program Files\Astellia\CigaleGSM\mysql.exe hlocalhost P3306 ucigale pastellia D%1 e select distinct

hex(xl3_imsi) from XL3 where xl3_imsi is not null; > Distinct_IMSIlist_%1.txt
5.4.
CONFIGURATION OF CUSTOM INDEXES IN ASM
There is an action QuerySQL in ASM witch can create custom indexes in MySQL database. The launch of
this task is independent of the engine processing and can operate in parallel of processing or at the end.
QuerySQL action in ASM (Figure 7)

Here are some recommandations to facilitate the configuration of this task:
- Use an environment variable to manage the address of the SU
- Use an environment variable to manage the login AA
- The password can not be managed in an environment variable and must necessarily be
filled by hand
- The name of the database is already managed by an environment variable.
Also, according to the index to create, performance on the MySql server can be degraded and Cigale
processing may be blocked.
35 / 87
6.
6.1.
DATA DESCRIPTION
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, LHO) or statistics files. They are edited in a dedicated directory.
This directory corresponds by default to the directory containing the record file.
CIGALE
Engine
LOG, ERR
XL3, TIM, SS, SMS, LHO

XL2, XLH, XLF, XLU, XLT
XLV, XSC, EFF
.txt data
Cigale
View
Activity
Analysis
qvm
base
Cigale GSM result files (Figure 8)

It is possible to choose another directory by filling in the STATS_DIRECTORY field in the CIGALE.INI file
(before starting up CIGALE) or in the parameter setting window.
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.
Cigale release
Start and end of the capture
File name
CIGALE V5.4 (05.04.01.007) COPYRIGHT Astellia

2000-2006
File
2006_06_15_CR.LOG
Start
Date
15/06/2006
00:00:01:175
End
Date
15/06/2006
23:59:30:228
State-machine
"03/04/2006 (v5.4.11); Astellia"
Release of the State machine
Header result files (Figure 9)
36 / 87
6.2.
RESULTS OVERVIEW
Cigale GSM uses the decoded information to recreate the various connection contexts and updates the
internal counters used for the statistics :
XL3
information on each connection and on their history at each

connection closure
SS
information on each message relative to the supplementary

services
SMS
information on each short message
TIM
information on the timers associated with the cells or with

the BSCs
LHO
information on the handover links that it has not been

possible to establish
XL2
statistics on the state transitions
XLH and
XLF
statistics on the flow of handovers
XLU
statistics on the location updates
XLT
statistics on the SCCP, CIC and TCH resources
XLV
miscellaneous statistics
EFF
EFFICACE counters
XLE
Inter System Statistics
Call Trace
CDRs
KPIs
Lastly, the various error or warning messages generated during processing can be transferred to a log
file (LOG).
Capture file
Source of Cigale GSM
Generated
during
process
Log file
Used by Ast Admin
Result file
Generated
after
process
Source of Roaming,
Trace,
SLM
Text files
Source of Cigale
View
Generated
after
process
Result files(Figure 10)
37 / 87
6.2.1. LOG FILE

The LOG file will only be generated if you have chosen the error file generation option.
The user messages are written in this file during the record file processing phase. It should be noted that
the messages relative to the handover links will only be included if you have not selected the LHO file
generation option.
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.
6.2.2. LHO : LINKS BSIC AND BCCH DURING HANDOVERS
The LHO file will only be generated if you have chosen the option for generating the file relative to
handover links. You can choose this option in the CIGALE.INI file or in the window associated with the
statistics files.
It contains the information associated with the handover links between the connections managed in the
Handover Command message of the Layer 3 protocol. Do not forget that the links between the connections
are based, in particular, on the cells' BSIC-BCCH pairs.
When it has not been possible to establish the handover link, because there is no correspondence between
the cell concerned (identified by its BSIC-BCCH pair) and the list of cells proposed when the handover
request was made (Handover Required message in the BSSMAP protocol), the BSIC-BCCH pair concerned
and the list of candidate cells are written in the LHO file. For example, there will be :
14460 HOCMD_RR : No cell corresponds to bsic 18 and bcch 7.
Cell
CI
BSIC
BCCH
MALESHERBE
43936
MALESHERBEBIENFAISA
37280
26
On the contrary, if there was only one candidate cell, the handover link is established despite the fact there
is no correspondence between the BSIC-BCCH pairs. In this case, this is notified to the user and in the LHO
and then the cell's BSIC-BCCH pair is updated for the rest of processing. For example :
77836 HOCMD_RR : Unique cell 42652 assigned although not identified by the proposed bsic 13 and
bcch 56.
In this case, the cell is said to be certified. The certified cells will be identified in the statistics files by the
" * " character before their name :
135204 HOCMD_RR : No cell corresponds to bsic 0 and bcch 14.
Cell
CI
BSIC
BCCH
AvenueRapp1
7581
38
TREMOILLEBOCCADOR
42908
38 / 87
*MAROTMARBOEUF
42652
13
56
It will then be possible to establish the handover links when there is no candidate cell corresponding to the
desired BSIC-BCCH pair, but only one candidate cell is not certified. In which case that cell will be managed
in the same way as for the case of a unique candidate cell.
6.2.3. XL3 : COMPLETE INFORMATION OF EACH CONNECTION
6.2.3.1.
Presentation
XL3 statistics are used to trace the complete sequence for a given connection by analyzing, either manually
or by post-processing, the various parts (on different cells) 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.
However, CIGALE allows you to mark state-machine transitions in the AUTOMAT.BDT file so that only
certain connections will be included in the XL3 file. So, a connection will only be written in this file if it has
caused a marked transition. In which case, provided the transition is not an initial transition (starting in the
BEGIN state), the transition concerned is indicated.
XL3 statistics have two special features:
- they are edited during processing (generally at closure of each connection) ;
- they can be generated in text format
- In order to generate XL3 statistics, you will have to insert the line EDIT_XL3=1 in the
CIGALE.INI file before you start up CIGALE or turn on the Connections (XL3) check box in
the window associated with the statistics files
Special case of intra-BSC handovers
In the case of intra-BSC handovers, lines are added to the XL3 file that trace the transfers between parts of
a connection when a HOPER message is detected.
The origin connection then ends in the XL3 file with an event called HOPER_OUT at the end instant t1.
The destination connection starts with a HOPER_IN event at instant t1.
It is therefore possible to find the link between several parts of connections.
In the case of an intra-cell handover, two lines appear in the XL3 file: one ending with a HOPER_IN_CEL
event, and the other starting with the same event.
When there is a change of cell during the channel assignment phase (BSC internal Directed Retry function),
two lines appear in the XL3: one ending with an ASCMP_xx_OUT event (for the cell being exited), and the
other starting with an ASCMP_xx_IN event (for the new cell).
6.2.3.2.
Description of XL3 file
The XL3 file includes by default (configurable via the output_xl3.ini file) the following fields presented in
columns for each connection :
the date of the last update (end date and time of the connection or of the part of the connection) ;
the opening date (start date and time of the connection or of the part of the connection) ;
39 / 87
the time elapsed (connection duration) between the opening date and the last update ; the duration of
time between the opening date and the most recent update: this duration is directly expressed in
milliseconds, and no longer in the format HH:MM:SS:mmm
the duration of the ringing phase (ringing duration) if there was one (between the ALERTING and
CONNECT messages or cut-off) ; this duration is directly expressed in milliseconds, and no longer in the
format HH:MM:SS:mmm
the LAC (Location Area Code) ; of the serving cell on the opening
the name of the serving cell at opening and its CI (Cell Identity) ;
the opening event (start event);
the last message (end event) received : either for a handover (with a cell change for the connection), or
for the termination of the connection ;
the state (previous state) preceding reception of the last message (the one indicated in the previous
column);
the cause (cause/rejcause) or reject cause associated with the last message received if it exists ;
the CIC that may have been used by the connection ;
the first TMSI (initial TMSI) and the new reallocated one if any (TMSI);
the current IMSI and IMEI ;
called or calling number (Number) associated with the connection, supplementary service operations
and strings, Destination or Originating addresses of RP and TP protocols .
Examples of supplementary service operations are : NotifySS, ActivateSS, EraseSS,
InterrogateSS, pud (process unstructured data), pur (process unstructured request),
Examples of supplementary services are : cfu (call forwardinfg unconditional), cfb (call
forwarding on busy), cfnrc (call forwarding on not reachable), allCondForwardingSS,
For Destination or Originating addresses of RP and TP protocols, numbers are prefixed xith
rpoa_ or rpda_ or tpoa_ or tpda.
The called or calling number (number)
A connection number (Ncnx), defined internally by CIGALE, which allows to easily find all the transfers
between parts of connection (intra-BSC or inter-BSC handovers if the 2 BSC concerned belong to the
same file processed by CIGALE)
The code of the old LAC with the corresponding (MCC-MNC) network for location updates;
the CI of the previous cell (PrevCI), in the case of a part of a connection by incoming handovers ;
the CI of the following cell (NextCI), in the case of a successful outgoing handover ;
the cause of an incoming handover (CauseHoIn), in the case of part of a connection arriving by
handover ;
the cause of an outgoing handover (CauseHoOut), in the case of a successful outgoing handover ;
information on the mobile equipment used for the connection (InfoMS): revision level (Ph1: phase 1,
Ph2 : phase 2, Phx : other phases), multiband capability (Bi), EFR support (EFR), Dual rate Full and Halfsupported (DRa), CLIR Calling Line Identification Restriction - service (CLIRi : invocation, CLIRs :
suppression) when requested in the setup message;
40 / 87
the number of the first frame (Nframe) in the saved file of the connection on every A interface. This
number corresponds to the frame containing the CR message (Connection Request) of the opening of a
SCCP connection on every A interface ; this CR message includes either a CL3I message (Complete Layer
3 Info) or a HOREQ (HandOver REQuest) ;
indication of data resource allocation for a given call (D);
the numbering of the serving BSC (NBSC) for the connection part ;
the total number of handovers (HoNb) at the end of the connection. This number is provided within the
last part of the connection (the one of the termination); otherwise, this column includes a > symbol for
the first handover, and . symbols for the other handovers.
Some elements taken out of the Bearer Capability Information Element (BearerCap) in the CALL
CONFIRMED, CALL PROCEDING or SETUP message. The aim is to provide details about data connections
in the following order : information transfert element (s : speech, UDI : unrestricted digital information,
31A : 3.1 Khz audio ex PLMN, FG3 : facsimile group 3, othITC : other ITC), User Rate (ur0.3 : 0.3 kbit/s
Rec X.1 and V.110, ur1.2 : 1.2kbit/s Rec X.1 and V.110, ur2.4 : 2.4 kbit/s Rec X.1 and V.110, ur4.8 :
4.8kbit/s Rec X.1 and V.110, ur9.6 : 9.6 kbits/s Rec X.1 and V.110, ur12trans : 12.0 kbit/s transparent (no
compliance with X.1 and V.110)), modem type (NoMod : no modem, V21, V.22, V22b : V22 bis, V26 ter,
V32, ModUnInt : modem for undefined interface, autobaudT1 : autobauding type 1) and Fixed Network
User Rate (FNur9.6 : 9.6 kbit/s Rec X.1 and V.110, FNur14.4 : 14.4 kbit/s Rec X.1 and V.110, FNur19.2 :
19.2 kbit/s Rec X.1 and V.110, FNur28.8 : 28.8 kbit/s Rec X.1 and V.110, FNur38.4 : 38.4 kbit/s Rec X.1
and V.110, FNur48 : 48 kbit/s Rec X.1 and V.110 (synch), FNur56tr : 56 kbit/s Rec X.1 and V.110 (synch)
/bit transparent, FNur64tr : 64 kbit/s bit transparent, FNur33.6tr : 33.6 kbit/s bit transparent,
FNur32I460 : 32.0 kbit/s Rec I.460)
The duration of the call (Call duration), from the CONNECT message to the last message of the
connection, in milliseconds
the paging response time (PAGRP time) in milliseconds; it is measured between the first A interface
PAGING message and the corresponding Paging Response message. If there is no answer to the paging,
this time corresponds to the time between the 2 A interface paging messages.
the number of A interface Paging messages (PAG Nb) for the paging procedure.
Incoming inter-BSC Handover Information (HoIn(HoRef/Bsic/Bcch/chaT-TN))

HoRef
Reference number associated to the HandOver

Value range is [000; 255]
Bsic
Base Station Identity Code

BCCH
Broadcast Control channel

ChaT-TN
Channel Type Timeslot Number.

Value range is [0; 31] for Channel Type and [0;7] for Timeslot Number
Outgoing inter-BSC Handover Information (HoOut(HoRef/Bsic/Bcch/chaT-TN))

HoRef
Reference number associated to the HandOver

41 / 87
Bsic
Base Station Identity Code

BCCH
Broadcast Control Channel

ChaT-TN
Channel Type Timeslot Number.

Value range is [0; 31] for Channel Type and [0;7] for Timeslot Number
Transition tag (TypeTrans) : indicates the CDR type based on the following table:
Byte 2
4
3
Not used
PROCEDURE_TYPE
Byte 1
4
3
CONNEXION_PHASE
SYSTEM
where:
Procedure Type:
Hexadecimal value
Name
explanation
0x00
OC
Outgoing Call
0x01
TC
Incoming Call
0x02
SMS_MO
Outgoing SMS
0x03
SMS_MT
Incoming SMS
0x04
SS_MO
Outgoing Supplementary Service
0x05
SS_MT
Incoming Supplementary Service
0x06
LU_NU
Normal Location Update
0x07
LU_PU
Periodic Location Update
0x08
LU_IA
Location Update for IMSI attach
0x09
HO_IN
Incoming inter-BSC Handover
0x0A
IMSID
IMSI Detach
Connexion Phase
Hexadecimal value
Name
explanation
0x00
Setup
From the start of connection to the Alerting phase
0x01
Alerting
From the Alerting phase to the Communication phase
0x02
Communication
From the Communication phase to the End of connection
System
Hexadecimal value
Name
0x00
User
0x01
BSS
0x02
NSS
42 / 87
0x03
Normal
For example the type 702 represents :
Procedure: 0x7, that is LU_PU_
Connexion: 0x0, that is Setup
System: 0x02, that is NSS
The digit sequence of DTMF (DTMF).
Codec type (Codec Type)
The mobile manufacturer (Mobile Manufacturer)
The mobile type (Mobile Type)
The Software Version (SV)
The MSC (MSC)
The LAC of the previous serving cell (Previous LAC)
The type of the serving cell (Current type cell): can be 2G, UMA or 3G
The type of the previous serving cell (Previous type cell): can be 2G, UMA or 3G
The type of the next serving cell (Next type cell) : can be 2G, UMA or 3G
TAC: first 6 or 8 digits of the IMEI, between square brackets, for example [35905102]
The duration of the setup phase in milliseconds (Setup duration)
The number of failed 3G HO (Nb 3G HO Failed)
The number of failed 2G HO (Nb 2G HO Failed)
The type of old LAC (Type Old LAC) : can be 2G, 3G or Invalid
Classmark type 2: hexadecimal value of the Classmark Type 2
Classmark type 3 : hexadecimal value of the Classmark Type 3
HPG type: based on Classmark Type 2 and Classmark Type 3, uses the following bit mask:
UMTS
GPS
13107
2
6553
6
HFR
AMR
WB
32768
OFR AMR
WB
HR AMR
WB
FR AMR
WB
HRAM
R
16384
8192
4096
2048
The LAC of the next serving cell (Next LAC)
The MNC of the current cell (MNC of current cell)
The MCC of the current cell (MCC of current cell)
The Cell Identifier of the current cell
FR
AMR
1024
EFR FR
512
25
6
A5/ A5/ GSMHR 3

2
E
85
0
190
0
180
0
90
0
12
8
64
32
16
If the connection has detected a non-initial transition that is marked in the state-machine's description file,
the following three columns will be included :
43 / 87
the initial state ;

the event (message and extension) ;
the cause of the transition.
Note :
The TMSI, IMSI, IMEI and called numbers are systematically preceded by the " " character
(obtained via ALT+0183)
Do not forget that international called or calling numbers are also preceded by the " + "
character.
6.2.4. PERIODIC XL3 : COMPLETE INFORMATION OF EACH CONNECTION FOR A PERIOD
The Periodic XL3 files are generated periodically every 1,2,5,10,15,20,60 mn (configurable in Cigale GSM
configuration). They are used by ROAMING RAN and contains exactly the same information of the XL3 file.
6.2.5. XL2 : STATISTICS ON THE NUMBER OF A INTERFACE MESSAGES
The XL2 statistics file will only be generated if you choose the option for generating statistics on the statemachine transitions. This option can be chosen or in the window associated with the statistics files.
This file gives detailed statistics on the number of messages observed on each A interface according to the
connection step and the cell on which the transition is made.
Each connection evolves according to a state-machine's states. Each connection begins in the
BEGIN state and follows a specific transition depending on the service requested (e.g. originating
call, terminating call, location update, handover managed by the MSC, supplementary service,
outgoing short message, etc.).
Connection evolution is therefore followed by means of the states of the state-machine. It is also followed
from cell to cell and the messages received are counted according to their arrival in such and such a cell.
This results in the message occurrence statistics being presented by states and by cells.
In-depth knowledge of the protocols used on the A interface is required to analyze this file.
The XL2 file is classified by BSC. For each BSC, the lists of cells without any observed traffic and of those
with observed traffic are given.
The content, column by column, of the XL2 files is described below:
- the state of the connection at the moment the event was received ;
- the event (including the extension if applicable) ;
- the cause, if applicable, associated with the event ;
- the state of the connection after reception of the event ;
- the total number of occurrences of that event in the current state (all cells considered) ;
- the following columns give the breakdown of those event occurrences per cell for the BSC
being monitored.
This file therefore traces the evolution of the connections in great detail for each cell in statistical form.
6.2.6. XLH : FLOW OF OUTGOING HANDOVERS TYPES FOR EACH CELL
The XLH statistics file will only be generated if you have chosen the option for generating statistics on
handovers. You can choose this option in the window associated with the statistics files.
44 / 87
This file gives a table of flows of handover types. It takes the form of a series of tables separated by two
blank lines.
This file contains all the intra-cell, intra-BSC and inter-BSC handovers
causes for all origin cells.
BSC
Studied cell
(Source cell)
Ho information
Cells names and CI involved in

ho with the studied cell
Each table represents the counts of handover types made by mobiles from a given source cell to one of its
neighboring cells (the mobile's destination cell).
The source cell (the mobile's origin cell before the handover) is indicated on the first line of the table (name
of its attachment BSC, name of the cell and CI). The rest of the line contains the titles of the table's columns
(see below for the description of each column).
Each of the following lines in the table concerns a target cell identified by the name of its attachment BSC,
its own name and its CI. The following columns correspond to the breakdown of handover types for the
source cell in the first line to the target cell.
The content of this file depends on whether you have chosen the Detailed display of the handovers option
or not.
This table's columns can be broken down into four parts :
6.2.6.1.
Description of the cell
The first part concerns the first three columns: it includes the implemented cells with, in order: the name of
the attachment BSC, the cell's name and its CI.
6.2.6.2.
Handover messages relative to the source cell
This part is filled in when the source cell belongs to a BSC whose A interface has been observed.
This part consists of the following columns:
intra-BSC, intra-cell handovers :
the CEL column : characterizes the changes of channel within a given cell (all causes considered).
This column will only be displayed if the Detailed display of handovers option is not selected ;
the CEL_ULQ column (cause : Uplink Quality) : channel changes inside a given cell due to poor
quality in the uplink direction. This column will only be displayed if the Detailed display of
handovers option is selected ;
the CEL_ULS column (cause : Uplink Strength) : channel changes within a given cell due to field
weakness in the uplink direction. This column will only be displayed if the Detailed display of
45 / 87
the CEL_DLQ column (cause : Downlink Quality) : channel changes inside a given cell due to poor
quality in the downlink direction. This column will only be displayed if the Detailed display of
the CEL_DLS column (cause : Downlink Strength) : channel changes within a given cell due to field
weakness in the downlink direction. This column will only be displayed if the Detailed display of
the CEL_D column (cause : Distance) : channel changes within a given cell due to distance. This
column will only be displayed if the Detailed display of handovers option is selected ;
the CEL_BC column (cause : Better Cell) : channel changes within a given cell due to the existence
of a better field. This column will only be displayed if the Detailed display of handovers option is
selected ;
the CEL_DR column (cause : Directed Retry) : channel changes within a given cell due to Directed
Retry. This column will only be displayed if the Detailed display of handovers option is selected ;
the CEL_XX column (other causes) : characterizes the channel changes within a given cell for a
cause other than those listed above. This column will only be displayed if the Detailed display of
intra-BSC handovers with change of cell :
the OUT_ULQ column (cause : Uplink Quality) : handovers triggered due to poor quality in the
uplink direction ;
the OUT_ULS column (cause : Uplink Strength) : handovers triggered due to field weakness in the
uplink direction ;
the OUT_DLQ column (cause : Downlink Quality) : handovers triggered due to poor quality in the
downlink direction ;
the OUT_DLS column (cause : Downlink Strength) : handovers triggered due to field weakness in
the downlink direction ;
the OUT_D column (cause : Distance) : handovers triggered due to distance ;
the OUT_BC column (cause : Better Cell) : handovers triggered due to the existence of a better
field ;
the OUT_DR column (cause : Directed Retry) : handovers triggered due to Directed Retry. This
column will only be displayed if the Detailed display of handovers option is selected ;
the OUT_XX column (other causes) : handovers triggered for a cause other than those listed
above. This column will only be displayed if the Detailed display of handovers option is selected ;
the ASS column (ASSIGNMENT COMPLETE message : change of cell during channel assignment
(BSS internal Directed Retry function) ;
inter-BSC handovers(checked by the MSC) :

The inter-BSC handover procedure consists of a dialogue between the origin BSC and the MSC and the
destination BSC and the MSC. The way of evaluating the efficiency of an inter-BSC handover is explained in
the graphic below : two different rates are built based on the messages exchange in the procedure, the
response rate and the failure rates (or success rate).
46 / 87
Outgoing handovers
% Response = Nb HO Command/Nb Ho Required
% Failure = Nb HO Clear Command/Nb HO Command
Incoming handovers
% Response = Nb HO Request Ack/Nb Ho Request
% Failure = Nb HO Complete/Nb HO Request Ack
the RQD1_ULQ column (cause : Uplink Quality) : handovers due to degraded quality in the uplink
direction for which the target cell (indicated at the beginning of the corresponding line) is
classified in the first position (hence the 1) in the list of eligible cells transmitted in the Handover
Required message ;
the RQD1_ULS column (cause : Uplink Strength) : handovers due to a field that is too weak in the
uplink direction for which the target cell (indicated at the beginning of the corresponding line) is
classified in the first position (hence the 1) in the list of eligible cells transmitted in the Handover
Required message ;
the RQD1_DLQ column (cause : Downlink Quality) : handovers due to degraded quality in the
downlink direction for which the target cell (indicated at the beginning of the corresponding line)
is classified in the first position (hence the 1) in the list of eligible cells transmitted in the
Handover Required message ;
the RQD1_DLS column (cause : Downlink Strength) : handovers due to a field that is too weak in
the downlink direction for which the target cell (indicated at the beginning of the corresponding
line) is classified in the first position (hence the 1) in the list of eligible cells transmitted in the
Handover Required message ;
the RQD1_D column (cause : Distance) : handovers due to an excessive distance with respect to
the source cell whose target cell (indicated at the beginning of the corresponding line) is classified
in the first position (hence the 1) in the list of eligible cells transmitted in the Handover
Required message ;
the RQD1_BC column (cause : Better Cell) : handovers due to a better cell with respect to the
source cell whose target cell (indicated at the beginning of the corresponding line) is classified in
the first position (hence the 1) in the list of eligible cells transmitted in the Handover
Required message ;
the RQD1_DR column (cause : Directed Retry) : handovers due to lack of TCH resources on the
originating cell whose target cell (indicated at the beginning of the corresponding line) is classified
in the first position (hence the 1) in the list of eligible cells transmitted in the Handover
Required message. This column will only be displayed if the Detailed display of handovers option
is selected ;
the RQD1_XX column (other causes) : handovers for a cause other than those described above for
which the target cell (indicated at the beginning of the corresponding line) is classified in the first
position (hence the 1) in the list of eligible cells transmitted in the Handover Required message.
This column will only be displayed if the Detailed display of handovers option is selected ;
The meaning of the RQD2_ULQ, RQD2_ULS, RQD2_DLQ, RQD2_DLS, RQD2_D, RQD2_BC,

RQD2_DR and RQD2_XX columns is similar to their RQD1 counterparts except that the target cell
is in the second position (hence the 2) in the list of eligible cells called up by the Handover
47 / 87
Required message. The RQD2_DR and RQD2_XX columns will only be displayed if the Detailed
display of handovers option is selected ;
The meaning of the RQD3_ULQ, RQD3_ULS, RQD3_DLQ, RQD3_DLS, RQD3_D, RQD3_BC,

RQD3_DR and RQD3_XX columns is similar to their RQD1 counterparts except that the target cell
is in the third position (hence the 3) in the list of eligible cells called up by the Handover Required
message. The RQD3_DR and RQD3_XX columns will only be displayed if the Detailed display of
the CMDx column : execution of handovers (Handover Command message) to a cell which it has
not been possible to connect with the cells contained in the previous Handover
Required message's list (hence the designation "cell x") ;
the CMD1 column : execution of handovers (Handover Command message) to the first cell in the
list of eligible cells called up earlier by the Handover Required message (hence the 1) ;
the meaning of the CMD2 and CMD3 columns is similar to that of the CMD1 column for the cell
placed in the second and third positions respectively of the list called up by the Handover
Required message ;
Remark :
When the list of eligible cells called up by the Handover Required message contains more than
three cells, the information concerning the cells after the fourth position does not appear in
the table.
the HOsu column (Clear Command message, cause : Handover successful) : indicates the number of
successful inter-BSC handovers ;
the RRJ column (Handover Required Reject message) : indicates the number of inter-BSC handovers that
have failed due to the absence of cells able to support the mobile ;
The FAIr column (Handover Failure message, cause : Reversion to old channel) : indicates the number of
handovers that have failed due to reversion to the old channel (failed connection to the target cell).
6.2.6.3.
Handover messages relative to the target cell
This part is filled in when the target cell belongs to a BSC whose A interface has been observed.
This part consists of the following columns :
the REQ column (Handover request message) : indicates the number of inter-BSC handover requests.
This column will only be displayed if the Detailed display of handovers option is not selected ;
the REQ_None column (no cause) : indicates the number of requested inter-BSC handovers for which no
cause is specified. This column will only be displayed if the Detailed display of handovers option is
selected ;
the REQ_ULQ column (cause Uplink Quality) : indicates the number of inter-BSC handover requests due
to poor quality in the uplink direction. This column will only be displayed if the Detailed display of
the REQ_ULS column (cause Uplink Strength) : indicates the number of inter-BSC handover requests due
to field weakness in the uplink direction. This column will only be displayed if the Detailed display of
the REQ_DLQ column (cause Downlink Quality) : indicates the number of inter-BSC handover requests
due to poor quality in the downlink direction. This column will only be displayed if the Detailed display
of handovers option is selected ;
48 / 87
the REQ_DLS column (cause Downlink Strength) : indicates the number of inter-BSC handover requests
due to field weakness in the downlink direction. This column will only be displayed if the Detailed
display of handovers option is selected ;
the REQ_D column (cause Distance) : indicates the number of inter-BSC handover requests due to
distance. This column will only be displayed if the Detailed display of handovers option is selected ;
the REQ_BC column (cause Better Cell) : indicates the number of inter-BSC handover requests due to
the existence of a better field. This column will only be displayed if the Detailed display of handovers
option is selected ;
the REQ_DR column (cause Directed Retry) : indicates the number of inter-BSC handover requests due
to Directed Retry. This column will only be displayed if the Detailed display of handovers option is
selected ;
the REQ_XX column (autres causes) : indicates the number of inter-BSC handover requests for a cause
other than those listed above. This column will only be displayed if the Detailed display of handovers
option is selected ;
the RAC column (Handover Request Acknowledge message) : indicates the number of inter-BSC
handover request acknowledgments ;
the FAI column (Handover Failure) : indicates the number of handovers that have failed after attempted
connection to the target cell ;
the DET column (Handover Detect message) : indicates the number of attempted accesses by handover.
Certain manufacturers have not introduced this message, it is therefore possible that this column will
not be filled in (see the restrictions made by the manufacturers) ;
the CMP column (Handover Complete message) : indicates the number of successful inter-BSC
handovers ;
the CLR column (Clear Command message) : indicates the number of failed handovers after successful
access to the target cell (for example failure at level 2).
6.2.6.4.
Ping pong handovers relative to source cells
This part is given when a source cell belongs to a BSC for which its A interface was observed. It is only
displayed if the option Detailled handover display is selected. The delay for a handover to be considered a
ping pong handover is configurable.
49 / 87
HoOut : outgoing handover

Ho-Ho : Crossing Handover from cell B
CELL A
CELL B
CELL C
Ho-Ho < xx s : Crossing Handover from cell B

CELL A
CELL B
CELL C
Call stays less

than xx seconds
HoPPG: Ping
Pong
CELL
A handovers from cell B CELL B
Call stays less
than xx seconds
Ping-Pong view indices (Figure 11)

The following columns make up this part :
the HoHoOut column : indicates the number of successful outgoing handovers (towards the target cell)
for calls that arrived by handover (from any cell) on the source cell ;
the HoHo(<NNs)column : indicates the number of successful outgoing handovers for calls that arrived
by handover (from any cell), and which remained on the source cell for less than NN seconds.
Remember that the NN value is defined by the Limited duration for ping pong handover execution
parameter (see. Application parameter) ;
the HoPPG_ULQ column (cause Uplink Quality) indicates the number of successful outgoing ping-pong
handovers with bad quality causes in the uplink direction, for calls that arrived by handover (from the
cell to which they return) and which remained on the source cell less than NN seconds [value defined by
the Limited duration for ping pong handover execution parameter];
the HoPPG_ULS column (cause Uplink Strength) : indicates the number of successful outgoing ping-pong
handovers due to radio level weakness causes in the uplink direction, for calls that arrived by handover
(from the cell to which they return) and which remained on the source cell less than NN seconds [value
defined by the Limited duration for ping pong handover execution parameter];
the HoPPG_DLQ column (cause Downlink Quality) : indicates the number of successful outgoing pingpong handovers with bad quality causes in the downlink direction, for calls that arrived by handover
the HoPPG_DLS column (cause Downlink Strength) : indicates the number of successful outgoing
handovers due to field weakness causes in the downlink direction, for calls that arrived by handover
50 / 87
the HoPPG_D column (cause Distance) ; indicates the number of successful outgoing handovers with
distance causes, for calls that arrived by handover (from the cell to which they return) and which
remained on the source cell less than NN seconds [value defined by the Limited duration for ping pong
handover execution parameter];
the HoPPG_BC column (cause Better Cell); indicates the number of successful outgoing handovers with
better cell causes, for calls that arrived by handover (from the cell to which they return) and which
remained on the source cell less than NN seconds [value defined by the Limited duration for ping pong
handover execution parameter];
the HoPPG_DR column (cause Directed Retry) : indicates the number of successful outgoing handovers
with directed retry causes, for calls that arrived by handover (from the cell to which they return) and
which remained on the source cell less than NN seconds [value defined by the Limited duration for ping
pong handover execution parameter];
the HoPPG_XX column (other causes) : indicates the number of successful outgoing handovers with
causes other than the previous ones, for calls that arrived by handover (from the cell to which they
return) and which remained on the source cell less than NN seconds [value defined by the Limited
duration for ping pong handover execution parameter];
the HOPPG column: indicates the number of ping-pong handovers, those successful outgoing handovers
for calls that return to their previous cell after they arrived by handover from that cell and remained on
the source cell less than NN seconds [value defined by the Limited duration for ping pong handover in
seconds execution parameter];
These columns will only be displayed if the Detailed display of handovers option is selected.
intra-BSC, intra-cell handovers :
CEL_TRA column (cause : Traffic) : channel changes within a given cell due to Traffic.
CEL_OM column (cause Operation & Maintenance) : channel changes within a given cell due
to Operation & Maintenance.
intra-BSC handovers with change of cell :
OUT_TRA column (cause : Traffic) : handovers triggered due to Traffic.
OUT_OM column (cause Operation & Maintenance) : handovers triggered due to Operation
& Maintenance.
inter-BSC handovers(checked by the MSC) :
RQD1_TRA column (cause : Traffic) : handovers triggered due to Traffic.
RQD1_OM column (cause : Operation & Maintenance) ; handovers triggered due to

Operation & Maintenance.
RQD2_OM column (cause Operation & Maintenance) : handovers triggered due to Operation
& Maintenance.
RQD3_OM column (cause Operation & Maintenance) : handovers triggered due to Operation
& Maintenance.
51 / 87
the handover messages relative to the target cell
REQ_TRA column (cause : Traffic) : indicates the number of inter-BSC handover requests due
to Traffic.
REQ_OM column (cause Operation & Maintenance) : indicates the number of inter-BSC
handover requests due to Operation & Maintenance.
ping pong handovers relative to source cells
HoPPG_TRA column (cause : Traffic) : indicates the number of successful outgoing handovers
with directed Traffic causes, for calls that arrived by handover (from the cell to which they
return) and which remained on the source cell less than NN seconds [value defined by the
Limited duration for ping pong handover execution parameter];
HoPPG_OM column (cause Operation & Maintenance) : indicates the number of successful
outgoing handovers with directed Operation & Maintenance causes, for calls that arrived by
handover (from the cell to which they return) and which remained on the source cell less
than NN seconds [value defined by the Limited duration for ping pong handover execution
parameter];
It should be noted that it is assumed here that all the handovers checked by the MSC are inter-BSC
handovers. It is possible, however, in certain special cases that the check of the intra-BSC handovers may
be returned to the MSC. The first columns of the table (CEL and OUT_xx) will then not be meaningful and
the other columns will give overall statistics on the successes and failures of all the handovers (intra and
inter-BSC).
The tables, each of which is relative to a source cell, are classified in increasing order of source cell CIs. The
target cells (lines) in each table are also classified in increasing order of their CI (all BSCs considered).
6.2.7. XLF : FLOW OF INCOMING AND OUTGOING HANDOVERS FOR EACH CELL
The XLF statistics file will only be generated if you have chosen the option for generating handover
statistics. You can choose this option in the window associated with the statistics files.
This file also concerns the handover flows, but gives a different view to that obtained in the XLH file. It also
consists of a series of tables relative to each cell. The purpose of each table is to indicate the handover
incoming and outgoing flows for the cell designated on the first line.
The tables are delimited by the terms START_XLF and END_XLF.
The first line of a table indicates the cell relative to the table. This first column identifies this line
(START_XLF term). The next three columns give the name of the cell's attachment BSC, the cell's name and
its CI. The rest of the line delimits the columns of the table associated with the incoming and outgoing
flows.
The second line contains the titles of the table's columns.
The next lines give the list of cells neighboring the cell being examined and on which at least one handover
has been observed. Each cell is filled in on three columns respectively indicating the name of its attachment
BSC, the cell's name and its CI. They are classified in increasing CI order.
Each table then has three parts, one concerning the handover flow leaving the cell concerned (whose name
is given on the first line), the second one the handover flow entering into that cell, and the last concerns
the flow of ping pong handovers.
52 / 87
This file's content depends on whether you have chosen the Detailed display of handovers and written XLF
results reduction option or not.
6.2.7.1.
Outgoing flows
the ULQ column (Handover Performed and Handover Request messages, cause : Uplink
Quality) : handovers triggered due to poor quality in the uplink direction (intra-BSC handovers that have
succeeded and inter-BSC handovers). The number indicates the percentage of handovers generated by
this cause with respect to the total number of handovers observed from the source cell (indicated on
the first line of the table) to the target cell (indicated at the beginning of the line) ;
the ULS column (Handover Performed and Handover Request messages, cause : Uplink
Strength) : handovers triggered due to a field that is too weak in the uplink direction (intra-BSC
handovers that have succeeded and inter-BSC handovers). The number indicates the percentage of
handovers generated by this cause with respect to the total number of handovers observed from the
source cell (indicated on the first line of the table) to the target cell (indicated at the beginning of the
line) ;
the DLQ column (Handover Performed and Handover Request messages, cause : Downlink
Quality) : handovers triggered due to poor quality in the downlink direction (intra-BSC handovers that
have succeeded and inter-BSC handovers). The number indicates the percentage of handovers
generated by this cause with respect to the total number of handovers observed from the source cell
(indicated on the first line of the table) to the target cell (indicated at the beginning of the line) ;
the DLS column (Handover Performed and Handover Request messages, cause : Downlink
Strength) : handovers triggered due to a field that is too weak in the uplink direction (intra-BSC
handovers that have succeeded and inter-BSC handovers). The number indicates the percentage of
handovers generated by this cause with respect to the total number of handovers observed from the
source cell (indicated on the first line of the table) to the target cell (indicated at the beginning of the
line) ;
the D column (Handover Performed and Handover Request messages, cause : Distance) : handovers
triggered because the distance between the mobile and the source cell is too great (intra-BSC handovers
that have succeeded and inter-BSC handovers). The number indicates the percentage of handovers
generated by this cause with respect to the total number of handovers observed from the source cell
(indicated on the first line of the table) to the target cell (indicated at the beginning of the line) ;
the BC column (Handover Performed and Handover Request messages, cause : Better Cell) : handovers
(intra-BSC handovers that have succeeded and inter-BSC handovers) triggered because there is a better
cell (from the radio viewpoint). The number indicates the percentage of handovers generated by this
cause with respect to the total number of handovers observed from the source cell (indicated on the
first line of the table) to the target cell (indicated at the beginning of the line) ;
the DR column (Handover Performed and Handover Request messages, cause : Directed
retry) : handovers (intra-BSC handovers that have succeeded and inter-BSC handovers) triggered due to
a lack of TCH resources on the origin cell. The number indicates the percentage of handovers generated
by this cause with respect to the total number of handovers observed from the source cell (indicated on
the first line of the table) to the target cell (indicated at the beginning of the line). This column will only
be displayed if the Detailed display of handovers option is selected ;
53 / 87
the XX column (Handover Performed and Handover Request messages, other causes) : handovers (intraBSC handovers that have succeeded, channel assignment handovers and inter-BSC handovers) triggered
for reasons other than those listed above. The number indicates the percentage of handovers generated
by this cause with respect to the total number of handovers observed from the source cell (indicated on
the first line of the table) to the target cell (indicated at the beginning of the line). This column will only
be displayed if the Detailed display of handovers option is selected ;
the Total column : this column indicates the total number of handovers leaving the cell indicated on the
first line of the table and going to the cell indicated at the beginning of the corresponding line (the
handover's destination cell). These are absolute values and not percentages ;
the %total column : this column indicates the proportion of each cell pair (source cell on the first line of
the table, and the target cell at the beginning of the line) with respect to the total number of handovers
leaving the cell indicated on the first line ;
the Tx rep column : this column indicates the percentage of the number of handovers performed
(Handover Command message relative to the first cell in the list called up by the previous Handover
Required message, CMD1 column in XLH) with respect to the number of handover requests (Handover
Required message with the cell indicated at the beginning of the line classified in the first position of the
list of eligible cells that has been called up, RQD1 column of XLH) ;
the Tx failed column : this column indicates the complement to 100% of the percentage of successful
handovers (Clear Command message with the cause Handover successful) with respect to the number of
handovers performed (Handover Command message).
The following columns deal with inter-BSC handovers times. The measured times are between the MSC
BSC Handover command and the MSC BSC Clear Command cause Handover successful. It corresponds to
the time the mobile station needs to access its newly allocated traffic channel.
the Avg duration column : average duration of the handovers from the cell indicated on the first line of
the table to the cell indicated at the beginning of the corresponding line ;
the Max duration column : maximum duration of the handovers from the cell indicated on the first line
of the table to the cell indicated at the beginning of the corresponding line ;
the Min duration column : minimum duration of the handovers from the cell indicated on the first line
of the table to the cell indicated at the beginning of the corresponding line ;
The Num HO column : represents the absolute number of handovers for which it was possible to
measure the execution time.
6.2.7.2.
Incoming flows
The second part, relative to the handover incoming flows to the cell being examined, consists of columns
similar to those in the first part. The only difference being that the handover direction is reversed. The
source cell is the one indicated at the beginning of the line and the target cell is the one indicated on the
first line of the table (incoming handovers to the cell being examined, that is to say the one indicated on
the first line of the table).
The only difference lies in the measured inter-BSC handover times. For the incoming handovers, the time is
measured between the BSC MSC Handover request acknoledge and BSC MSC the Handover
complete. It corresponds to the time the mobile station needs to access its newly allocated traffic channel.
54 / 87
Third part : ping pong handover flows

the HO-HO Out, Total column : the HO-HO Out represents the number of outgoing handovers from the
cell indicated on the first line of the table towards the cell indicated at the beginning of the line, for
connections that have already had an handover (regardless of what the old cell is). This represents the
number of times the connections were transisting (arriving and leaving by handover) on the cell
indicated at the first line of the table.
the HO-HO (< NN s), % HO-HO < column : The HO-HO (< NN s) are HO-HO Out that stayed less than NN
seconds [value defined by the Limited Ping Pong handover time execution parameter] on the source
cell (or in this case the Transit cell) indicated on the first line of the table. The column gives the HO-HO
percentage (< NN s) in relation to Ho-Ho Out ;
the HOPPG columns : The HOPPG [or HOPPEGcel (< NN s)] are the HO-HO (< NN s) for which the
handover target cell, the one indicated at the beginning of the line, is identical to the cell of origin of the
previous handover. They are considered as being "ping-pong" handovers:
the ULQ, ULS, DLQ, DLS, D, BC, DR and XX columns: indicates the pourcentage of every ping pong
handover cause, in relation to the total number of ping pong handovers for the cell couple
concerned ;
the HoHo <, Total column : gives the total number of HO-HO (< NN s) from the cell indicated in the first
line of the table towards the cell indicated at the beginning of the line ;
the HOPPGcel (< NN s) columns:
the %total column: informs for the weigth of every cell couple (source cell in the first line of the
table, target cell at the beginning of the line) in relation to the total number of HOPPG leaving the
cell indicated by the first line
the Total column: gives the total number of HOPPG, over quick handovers ("ping-pong") between
the cell indicated on the first line of the table towards the cell indicated at the beginning of the line,
previously exited cell ;
the %PPGcel column: gives the HOPPG percentage in relation to the Ho-Ho Out ;
The last line of each table, called Total, gives : for the first part the total number of outgoing handovers and
their breakdown according to the causes when they are filled in ; and for the second part, the total number
of incoming handovers and a similar breakdown.
After the second part, the HO In/Out column indicates the ratio between the number of incoming
handovers and the number of outgoing handovers. So, if this number is 1, the flow is balanced ; if this
number is lower than 1, there are more outgoing handovers than incoming handovers ; if this number is
greater than 1, the incoming handover flow is greater than the outgoing handover flow.
For the third part, the total number of HO-HO Out, HO-HO (< NN s), and HOPPGcel (< NN s) are given, with
an indication of HO-HO (< NN s) causes.
Last column contains Bsic and BCCH information for cells for which either this information was provided
within the cell description file, or was decoded from signaling messages during handover procedures driven
by the MSC. In the latter, a * symbol is added to indicate that these Bsic and Bcch values have been
obtained using the signaling information.
55 / 87
Outgoing flows
the HoOut_TRA column: (Handover Performed and Handover Request messages, cause :
Traffic) : handovers (intra-BSC handovers that have succeeded and inter-BSC handovers)
triggered due to
. The number indicates the percentage of
handovers generated by this cause with respect to the total number of handovers
observed from the source cell (indicated on the first line of the table) to the target
cell (indicated at the beginning of the line). This column will only be displayed if the
Detailed display of handovers option is selected ;
the HoOut_OM column: (Handover Performed and Handover Request messages, cause :
Operation&Maintenance) : handovers (intra-BSC handovers that have succeeded and
inter-BSC handovers) triggered due to
. The number indicates the
percentage of handovers generated by this cause with respect to the total number of
handovers observed from the source cell (indicated on the first line of the table) to the
target cell (indicated at the beginning of the line). This column will only be displayed if the
Detailed display of handovers option is selected ;
Incoming flows
the HoIn_TRA column: indicates the pourcentage of incoming handover with cause Traffic.
This column will only be displayed if the Detailed display of handovers option is selected ;
the HoIn_OM column: indicates the pourcentage of incoming handover with cause
Operation&Maintenance. This column will only be displayed if the Detailed display of
ping pong handover flows
the HoPPG_TRA column: indicates the pourcentage of ping pong handover with cause
Traffic, in relation to the total number of ping pong handovers for the cell couple
concerned ; This column will only be displayed if the Detailed display of handovers option
is selected ;
the HoPPG_OM column: indicates the pourcentage of ping pong handover with cause
Operation & Maintenance, in relation to the total number of ping pong handovers for the
cell couple concerned ; This column will only be displayed if the Detailed display of
6.2.8. XLU : LOCATION UPDATE FLOWS
The location update procedure allows a mobile device to inform the cellular network, whenever it moves
from one location area to the next. Mobiles are responsible for detecting location area codes. When a
mobile finds that the location area code is different from its last update, it performs another update by
sending to the network, a location update request, together with its previous location, and its Temporary
Mobile Subscriber Identity (TMSI).
The XLU statistics file will only be generated if you have chosen the option for generating the statistics on
the location updates. You can choose this option in the window associated with the statistics files.
This file contains a series of tables indicating the location update flows. Each table is separated by two
blank lines from the next table.
56 / 87
CIGALE creates LAC flow tables per destination Furthermore, the XLU statistics are broken down per MNC
and associated MCC pairs and per the subscribers' origin GSM networks.
The first line of a table indicates the LAC (Location Area Code) of the destination location area followed by
the titles relative to each column
The XLU statistics are ventilated in relation to the MCC and MNC couples associated with the LAC and in
relation to the Home GSM network of the subscribers. They also contain the details of particular reject
causes of location updates.
The XLU statistics contain two types of tables :
a local table for subscribers networks :here the statistics are grouped by subscribers network,
independent of the original LAC and destination
The first line of the table indicates the titles for each column
The following lines are relative to the network subscribers.
Tables per destination LAC : the statistics here are detailled by LAC of origin and by mobile network.
The first line of a table indicates the LAC of the destination location zone followed by the title relative to
every column. The following lines are relative to original location zones.
The following lines concern the origin location areas. For each line, you will see the following columns :
the LAC of the former location area (only for the type of table indicating per destination LAC);
the subscribers' origin GSM network (when the IMSI has been requested during the location update). If
not you will find a ? symbol ;
the number of normal location update requests ;
the number of successful normal location update requests ;
the number of rejected normal location update requests ;
the number of normal location updates interrupted by radio cuts ;
the number of rejected normal location updates with a PLMN Not Allowed cause ;
the number of rejected normal location updates with an IMSI Unknown in HLR cause ;
the number of rejected normal location updates with a Location Area Not Allowed cause ;
the number of rejected normal location updates with a Network Failure cause ;
the number of normal location updates rejected with a Invalid Mandatory Information cause ;
the number of normal location updates rejected with a cause other than the previous ones ;
the number of periodic location update requests ;
the number of successful periodic location update requests ;
the number of rejected periodic location update requests.
6.2.9. XLV : SCCP, TRAFFIC AND CIC STATISTICS
The XLV statistics file will only be generated if you have chosen the option for generating the miscellaneous
statistics. You can choose this option in the window associated with the statistics files
57 / 87
This file contains miscellaneous items of information that do not necessarily have any link with each other.
The first series of information items concerns the processing time and the initial (at the beginning of
processing) and minimum remaining memories.
Processing time
Frames
The second series of information items concerns the processed file : count of records read, origins of the
captured frames broken down according to the analyzer's logic ports and the file's exploitation ratios
according to the protocols (processed frames rate, error frames rate).
Connections purged (still open at the end of the capture) for each interface
Number of CI and Time Slots for each BSC
58 / 87
Remark :
If the analyzer manages several ports, the informations on the logic ports indicate the
direction (RX or TX) followed by the board's number in parentheses and then the IT number.
For example, you will have RX(1)14 for the 14th port in reception mode on the 1st board.
The third series of information items concerns the list of connections that are open at the end of processing
of the record file. These connections are broken down per observed A interface.
Number of SCCP messages
SCCP breakdown and messages repartition
Messages repartition on all

interfaces
Then come the statistics on the observed BSCs :

firstly, the number of CIs seen on each observed BSC ;
then, classified per BSC, the following information :
Establishing, Setup, Ringing and Communication duration for OC and TC for each BSC
Establishing: between the Initial and the

setup messages
Setup: between the Setup and Alerting or
Progress messages
Ringing: between the Alerting or Progress
and the Connect messages
communication: between the Connect and
the 1st release messages
Initial
Setup
Establishing
message
Setup
Alerting,
Progress Ringing
Connect
Communication
1st release
message
Establishing durations (broken down per originating and terminating calls with the distinction
being made between successful and failed calls and an indication of the handover rate)
Setup durations (same breakdown),
59 / 87
ringing durations (same breakdown),
connection duration (same breakdown),
list of observed cells,

List of observed cells in the BSC
Mobile statistics per cell
Mobile Class
and Revision level
percentage of attempted connections broken down per cell and per class and mobile revision
levels.
The next part gives an overall accumulation of the called numbers broken down per type of called number.
These counts are also performed for the numbers declared in the PHONES.ADT file
These counts are detailed by two other statistics:
- column Setup/Alerting : setup durations
- column Alerting/Connect:ringing duration
Phones information
The phone numbers are defined in the file PHONES.ADT

The information are the following:
Total called number
Minimum values
Number of unknown dialed number
Number of international calls
Number of PROGRESS messages
Number of ALERTING messages
Number of CONNECT messages
Number of user DISCONNECT messages with cause NC
Number of Fixed network DISCONNECT messages with causes NCCA (No Circuit Channel Available, TF
or SEC (Switching Equipment Congestion)
Then, we found accumulated statistics of timers.
60 / 87
Timers values per BSC and cells

Average value
Minimum values
Maximum values
All the timers are defined in the file

TIMES.ADT
The following statistics concern the number of SCCP messages seen when processing the record file.
The overall count of messages (SCCP, BSSAP, Layer3, RP, TP, SS and SMS) is then given with a breakdown
per observed A interface.
Lastly, the number of eligible cells contained in the lists called up in the HORQD messages, all A interfaces
considered.
6.2.9.1.
Timer table
The statistics are generated per BSC and per Cells

Timers values per BSC and cells (different representation)
The KPI are :

-
Name : BSC or Cell Name

MSC
BSC
LAC : filled if cells statistics
CI : filled if cells statistics
Timer Name and Number
Avg time for this timer
Min time for this timer
Max time for this timer
61 / 87
6.2.9.2.
USSD statistics
The statistics are generated per BSC and per Cells

The USSD KPI are :
- Avg time session (TOTAL) : average duration between CMSRQ_SS, and RELCMP_SS or
CLREQ, for all the USSD procedures
- Avg time session (SUCCESS) : average duration between CMSRQ_SS and RELCMP_SS for
successful USSD procedures.
- Nb USSD Start : REGISTER_SS number
- Nb USSD success : number of RELCMP_SS with no error causes
- Nb USSD failed
- Error numbers detailled by causes
USSD information per BSC and Cell
6.2.10. XLT STATISTICS

The XLT statistics file will only be generated if you have chosen the option for generating the statistics on
the resources. You can choose this option in the window associated with the statistics files.
This file groups together the statistics relative to the SCCP, TCH and CIC resources.
A first series of information presents a summary of the traffic data per BSC observed during the CIGALE
processing.
Here we find, for the BSC and all cells (linked to it) with observed traffic, the number of Erlangs (average
number of occupied ressources) during the observed period as well as the maximum number of resources
simultaneously occupied (as seen during the processing). These resources are either CICs (A interface ) for
the BSC, or TCHs for the cells.
62 / 87
MS
BSS
MM AUTHENTICATION REQUEST
MSC
/VLR
LOSS OF THE RADIO LINK

BSSMAP CLEAR REQUEST (RIF)
BSSMAP CLEAR COMMAND (RIF)
BSSMAP CLEAR COMPLETE
SCCP_RELEASED
SCCP_RELEASE COMPLETE
Failure cases during authentication (Figure 12)

The second series of information contains detailled statistics for each BSC.
These statistics are broken down per BSC.
The observed cells are listed for each BSC.
Then, a table lists the various CICs used. For each CIC, the minimum, maximum and average durations are
indicated, along with the number of allocations.
Then, a table lists the various MICs used. For each MIC, the minimum, maximum and average durations are
indicated, along with the number of allocations
MS
MSC
/VLR
BSS
BSSMAP ASSIGNMENT REQUEST
congestion
BSSMAP ASSIGNMENT FAILURE
(NRRA)
CC DISC
SCCP_RELEASED
SCCP_RELEASE COMPLETE
Failure cases during TCH allocation (Figure 13)
63 / 87
The next table is global to all the CICs used by the current BSC. It lists the accumulated durations per
number of simultaneous allocations, and the durations during which there were that number of
simultaneous allocations at the most (this corresponds to the duration sum of the numbers of allocations
lower than or equal to the current number of allocations). The table ends with the resource's average
number of allocations. The resource's number of allocations is also indicated at the beginning and end of
the file.
Then there is a table similar to the previous one relative to the SCCP resources of the current BSC.
Resource Nb
3
0 resource : D1 + D3
1 resource : D2 + D4 + D6
2 resources : D5 + D7 + D9
2
1
0
Time
D1
D2
D3
D4
D5
D6
D7
D8
D9
TCH cumulated information per cell (Figure 14)

Lastly for each observed cell, a similar table relative to the TCH resources is displayed.
The resource allocations and releases are performed on the following messages:
Resources
Allocations
Releases
SCCP
Connection request (SCCP)
Connection refused (SCCP)

Released (SCCP)
Released complete (SCCP)
Reset (SCCP)
CIC
Assignment request (BSSMAP)
Clear command (BSSMAP)
Handover request (BSSMAP)
Handover failure (BSSMAP)

Connection refused (SCCP)
Released (SCCP)
Reset (SCCP)
TCH
Handover request acknowledge (BSSMAP) (if the CIC Handover performed (BSSMAP) (release of the
is already assigned)
resource on the origin cell)
Clear command (BSSMAP)
Assignment complete (BSSMAP) (if the CIC is already Connection refused (SCCP)
assigned)
Released (SCCP)

Handover performed (BSSMAP) (resource allocation Reset (SCCP)
on destination cell)
6.2.11. SS : SUPPLEMENTARY SERVICES

The SS statistics file will only be generated if you have chosen the option for generating the statistics on the
supplementary services. You can choose this option in the window associated with the statistics files.
64 / 87
This file groups together all the information on each message relative to the supplementary services
detected during processing of a record file.
It is comprised of the following columns :
- Date : message reception date ;
- Time : reception time ;
- Message : message from the Layer 3 protocol concerned (with its extension if applicable) ;
- State : state of the state-machine at the time of the message reception transaction ;
- Cell : cell concerned ;
- Operation : name of the supplementary services' operation concerned ;
- Service : name of the supplementary service.
6.2.12. SMS : SHORT MESSAGES
The SMS statistics file will only be generated if you have chosen the option for generating the statistics on
the short messages. You can choose this option in the window associated with the statistics files.
MS
BSS
MSC
/VLR
Access and channel assignment

Authentication and ciphering
SMS CP-DATA [RPDATA]
SMS CP-ACK
SMS CP-DATA [RPACK]

SMS CP-ACK
HLR
SMS-IWMSC
SC
Nb SMS MO
Zone SMS OC failures
MAP_FORWARD_SHORT_MESSAGE
Message
Message and
transfer
adress
acknowledgment storage
ack
Nb SMS MO success
release
SMS Mobile Originating (Figure 15)

This file groups together information on short messages that are detected when processing a result file.
It is comprised of the following columns:
Date : message reception date ;
Time : reception time ;
Message : message from the TP protocol concerned (with its extension if applicable) ;
65 / 87
State : state of the state-machine at the time of the message reception transaction ;
Cell : cell concerned ;
RP MR : value of the Message Reference field delivered by the RP protocol ;
RP OA : value of the Originating Address field delivered by the RP protocol ;
RP DA : value of the Destination Address field delivered by the RP protocol ;
TP MR : value of the Message Reference field delivered by the TP protocol ;
TP OA : value of the Originating Address field delivered by the TP protocol ;
TP DA : value of the Destination Address field delivered by the TP protocol ;
PID : value of the Protocol IDentifier field delivered by the TP protocol ;
DCS : value of the Data Coding Scheme field delivered by the TP protocol ;
SCTS : value of the Service Centre Time Stamp field delivered by the TP protocol ;
CT : value of the Command Type field delivered by the TP protocol ;
MN : value of the Message number field delivered by the TP protocol ;
VP : value of the Validity Period field delivered by the TP protocol ;
Num char. : number of characters contained in the short message ;
UD : short message displayed depending to the character set ;
For 7 bit character set, short message is displayed in plain language
For 8 bit and UCS2 messages, shoert message is displayed in hexadecimal format
CD : command displayed in hexadecimal.
HLR
MS
MSC
/VLR
BSS
SMSIWMSC
SC
Message
transfer
MAP_SEND_ROUTING_INFO_FOR_SM
MAP_SEND_ROUTING_INFO_FOR_SM ack
Access and channel

assignment
Authentication
and ciphering
Nb SMS MT
SMS CP-DATA [RP-DATA]
SMS CP-ACK
Zone SMS TC failures
SMS CP-DATA [RP-ACK]

SMS CP-ACK
Nb SMS MT success
ack
release
SMS Mobile Terminating (Figure 16)
66 / 87
6.2.13. TIM : VALUES OF THE TIMERS

The TIM statistics file will only be generated if you have chosen the option for generating the statistics on
the timers.
You can choose this option in the window associated with the statistics.
This file groups together the successive unit values of the timers. It is comprised of the following columns :
- Type : timer associated with the cells or with the BSCs ;
- Name : number between parentheses and name of the cell or of the BSC ;
- Timer : timer name ;
- Start event : message at the beginning of the connection ;
- Duration (ms) : corresponding duration in milliseconds.
- Connection number : this number corresponds to the internal connection numbering of
CIGALE ; it is the same numbering than the one used for XL3 statistics.
6.2.14. EFF : EFFICACE COUNTERS STATISTICS
This file groups together a set of counters. The Efficace counters are defined in the successive columns of
each associated transition in the state-machine description file (AUTOMAT.BDT).
Each counter can be associated with one or several transitions.
The AUTOMAT.BDT file also declares the version of EFFICACE that is compatible with those counters. This
version number will be written in the EFF file when the statistics are generated.
The table below presents examples of counters associated with the state-machine transitions.
Present
Cause
Next state
in
XL3
(by default = 0)
OC_CMS_REQ
NbOC
OC_CMS_REQ
NbOC
SSUP
NbOCss
SMS
NbOCsms
REEST
TC_PAG_RP
NbTC
HO_TCH_REQ
NbHORQ_HO
PrcHOREQ_INOUT
PqsHOREQ
HO_TCH_REQ
NbHORQ_HO
PrcHOREQ_INOUT
PqsHOREQ
HO_TCH_REQ
NbHORQ_HO
PrcHOREQ_INOUT
PqsHOREQ
HO_SD_REQ
HO_SD_REQ
HO_SD_REQ
LU_N
NbLUREQ_NU
LU_P
NbLUREQ_PU
67 / 87
LU_IA
NbLUREQ_IA
END
NbIMSID
BEGIN
BEGIN
BEGIN
BEGIN
END
OC_AUT_REQ_1
OC_CIM_CMD
6.2.15. XSC : SMS-CENTER STATISTICS

The XSC statistics file will only be generated if you have chosen the option for generating the statistics on
the SMS-C efficiency. You can choose this option in the window associated with the statistics files.
It is comprised of the following columns :
- SMS-C Nb :SMS-C number
- Message type : procedure type (SMS MO SUBMIT, SMS MO COMMAND, SMS MT DELIVER,
SMS STATUS REPORT)
- Procedure Number : number of efficiency procedures
- Efficiency rate
- Event-Cause : numbers of inefficiency procedures listed by event cause
Remark: All the inefficiency causes are not listed below.
6.2.16. XLE : 3G HANDOVERS
6.2.16.1.
3G handovers
Two sorts of Handover are considerered: the outgoing Ho to 3G and the Incoming Ho from 3G.
The Incoming Ho from 3G per cell KPI are listed by (RNC, Cell) or (SAI, Cell):
RNC
LAC from 3G
SAC
LAC
CELL
Incoming Ho from 3G Req
Incoming Ho from 3G Cmd
Incoming Ho from 3G Succ
Incoming Ho from 3G Rate
Resp
Incoming Ho from 3G Rate Det
Incoming Ho from 3G Rate
Number of Handover Request (HOREQ) messages received by the target BSS for handovers
from 3G.
Number of Handover Request Acknowledge (HORAC) messages sent by the target BSS for
handovers from 3G.
Number of Handover Complete (HOCMP) messages sent by the target BSS for handovers
from 3G.
Incoming Inter-Ho Cmd / Incoming Inter-Ho Req.
number of Handover Detect (HODET) messages divided by Incoming Ho from 3G Cmd.
Incoming Ho from 3G Succ / Incoming Ho from 3G Cmd.
68 / 87
Succ
Incoming Ho from 3G Average
duration (ms)
Incoming Ho from 3G Min
duration (ms)
Incoming Ho from 3G Max
duration (ms)
average duration between Ho Request Ack and Ho Complete

min duration between Ho Request Ack and Ho Complete
Nb of HO 2G->2G
max duration between Ho Request Ack and Ho Complete

Number of call Release after 3G/2G HO and before
DELAY_END_COMM_MAX_AFTER_HO3G2G seconds
Number of 2G/2G HO after 3G/2G HO and before DELAY_HO2G2G_MAX_AFTER_HO3G2G
seconds
Nb of drop in 2G cell
Number of drop after 3G/2G HO and before DELAY_DROP_MAX_AFTER_HO3G2G seconds
Nb of Call Release
The Outgoing Ho to 3G per cell KPI are listed by (Cell, RNC):

LAC
CELL
RNC
Outgoing
Ho to 3G
Req
Outgoing
Ho to 3G
Cmd
Outgoing
Ho to 3G
Succ
Outgoing
Ho to 3G
Rate Resp
Outgoing
Ho to 3G
Rate Succ
Outgoing
Ho to 3G
Rate Cut
Outgoing
Ho to 3G
Rate Ret
Number of Handover Required (HORQD) messages sent by the handover's originating

BSS for handovers to 3G.
Number of Handover Command (HOCMD) messages received by the handover's
originating BSS for handovers to 3G.
Number of Clear Command (CLCMD) messages with cause Handover Successful (HoS)
received by the handover's originating BSS for handovers to 3G.
Outgoing 3G-Ho Cmd / Outgoing 3G-Ho Req
Outgoing 3G-Ho Succ / Outgoing 3G-Ho Cmd

Number of abnormal call drop during an outgoing handover to 3G (after Handover
Command HOCMD- message) divided by Outgoing Ho to 3G Cmd
Number of outgoing handover to 3G failures with return to the old channel (Handover
Failure HOFAI- cause Radio Interface Failure reversion to old channel RIFroc-) divided
by Outgoing Ho to 3G Cmd
6.2.16.2.
UMA handovers
Two sorts of Handover are considerered: the outgoing Ho to UMA and the Incoming Ho from UMA.
The Incoming Ho from UMA per cell KPI are listed by (UMA cell, Cell).
The Outgoing Ho to UMA per cell KPI are listed by (Cell, UMA Cell).
Incoming Ho from UMA
Req
Number of Handover Request (HOREQ) messages received by the target BSS for handovers from UMA.

Cmd
Number of Handover Request Acknowledge (HORAC) messages sent by the target BSS for handovers from UMA.
Number of Handover Complete (HOCMP) messages sent by the target BSS for handovers from UMA.
69 / 87
Succ
Rate Resp

Rate Det
number of Handover Detect (HODET) messages divided by Incoming Ho from UMA Cmd.

Rate Succ
Incoming Ho from UMA Succ / Incoming Ho from UMA Cmd.

Average duration (ms)
Average duration between Ho Request Ack and Ho Complete

Min duration (ms)
Min duration between Ho Request Ack and Ho Complete

Max duration (ms)
Max duration between Ho Request Ack and Ho Complete
Nb of Call Release
Number of call Release after 3G/2G HO and before DELAY_END_COMM_MAX_AFTER_HOUMA2G seconds
Nb of HO 2G->2G
Number of 2G/2G HO after 3G/2G HO and before DELAY_HO2G2G_MAX_AFTER_HOUMA2G seconds
Nb of drop in 2G cell
Number of drop after 3G/2G HO and before DELAY_DROP_MAX_AFTER_HOUMA2G seconds
Incoming Ho from 2G
Req
Number of Handover Request (HOREQ) messages received by the target BSS for handovers from 2G.
Incoming Ho from 2G
Cmd
Number of Handover Request Acknowledge (HORAC) messages sent by the target BSS for handovers from 2G.
Incoming Ho from 2G
Succ
Number of Handover Complete (HOCMP) messages sent by the target BSS for handovers from 2G.
Incoming Ho from 2G
Rate Resp
Incoming Ho from 2G
Rate Det
number of Handover Detect (HODET) messages divided by Incoming Ho from 2G Cmd.
Incoming Ho from 2G
Rate Succ
Incoming Ho from UMA Succ / Incoming Ho from UMA Cmd.
Incoming Ho from 2G
Average duration (ms)
Average duration between Ho Request Ack and Ho Complete
Incoming Ho from 2G
Min duration (ms)
Min duration between Ho Request Ack and Ho Complete
Incoming Ho from 2G
Max duration (ms)
Max duration between Ho Request Ack and Ho Complete
Nb of Call Release
Number of call Release after 2G/UMA HO and before DELAY_END_COMM_MAX_AFTER_HOUMA2G seconds
Nb of HO UMA->UMA
Number of UMA/UMA HO after 2G/UMA HO and before DELAY_HO2G2G_MAX_AFTER_HO2GUMA seconds
Nb of drop in UMA cell
Number of drop after UMA/2G HO and before DELAY_DROP_MAX_AFTER_HO2GUMA seconds
Note : UMA cells must be tagged as UMA in topology.txt file.
70 / 87
7.
APPENDIX A: GLOSSARY
2G
3G
3GPP
2nd Generation
3rd Generation
Third Generation Partnership Project
A
AAL
AAL2
AAL5
APN
ASN.1
ATM
AuC
ATM Adaptation Layer

ATM Adaptation Layer type 2
ATM Adaptation Layer type 5
Access Point Name
Abstract Syntax Notation One
Asynchronous Transfer Mode
Authentication Centre
B
BER
BSS
BTS
Basic Encoding Rules (of ASN.1)

Base Station Subsystem
Base Transceiver Station
C
CAMEL Customised Application for Mobile network Enhanced Logic
CAP
CAMEL Application Part
CCI
Capability / Configuration Identifier
CCITT Comit Consultatif International Tlgraphique et Tlphonique (The International Telegraph and
Telephone Consultative Committee)
CEIR Central Equipment Identity Register
CN
Core Network
CRC
Cyclic Redundancy Check
CRNC Controlling Radio Network Controller
CS-GW Circuit Switched Gateway
CS
Circuit Switched
D
DCS
Data Coding Scheme
E
E-GGSN Enhanced GGSN
E-HLR Enhanced HLR
EGPRS Enhanced GPRS
EHPLMN
Equivalent Home PLMN
EIR
Equipment Identity Centre
Equipment Identity Register
ETSI
European Telecommunications Standards Institute
71 / 87
F
FTN
forwarded-to number
G
GERAN
GGSN
GMSC
GPRS
GSM
GTP
GTP-U
GSM EDGE Radio Access Network

Gateway GPRS Support Node
Gateway MSC
General Packet Radio Service
Global System for Mobile communications
GPRS Tunneling Protocol
GPRS Tunnelling Protocol for User Plane
H
H-CSCF Home CSCF
HLR
Home Location Register
HPLMN Home Public Land Mobile Network
I
IETF
IMEI
IMSI
IN
INAP
IP
IPv4
IPv6
ISDN
ISUP
ITU
Internet Engineering Task Force

International Mobile Equipment Identity
International Mobile Subscriber Identity
Intelligent Network
Intelligent Network Application Part
Internet Protocol
Internet Protocol Version 4
Internet Protocol Version 6
Integrated Services Digital Network
ISDN User Part
International Telecommunication Union
K
Kc
Ki
Ciphering key
Individual subscriber authentication key
L
L1
Layer 1 (physical layer)
L2
Layer 2 (data link layer)
L2ML Layer 2 Management Link
L2R
Layer 2 Relay
L2R BOP
L2R Bit Orientated Protocol
L2R COP
L2R Character Orientated Protocol
L3
Layer 3 (network layer)
LAC
Location Area Code
72 / 87
LAI
LMSI
LPLMN
LU
Location Area Identity

Local Mobile Station Identity
Local PLMN
Location Update
M
M
Mandatory
MAP Mobile Application Part
MCC Mobile Country Code
MO-SMS
Mobile Originated Short Message Service
MSC Mobile Switching Centre
MSID Mobile Station Identifier
MSIN Mobile Station Identification Number
MSISDN
Mobile Subscriber ISDN Number
MSRN Mobile Station Roaming Number
MT-SMS
Mobile Terminated Short Message Service
MTP Message Transfer Part
MTP3-BMessage Transfer Part level 3
N
NMSI
NNI
NO
NPA
NPI
NSS
National Mobile Station Identifier

Network-Node Interface
Network Operator
Numbering Plan Area
Numbering Plan Identifier
Network Sub System
O
O
Optional
O&M Operations & Maintenance
OID
Object Identifier
OPLMN Operator Controlled PLMN (Selector List)
P
P-TMSI
PCU
PDP
PDU
PID
PIN
PKCS
PLMN
PS
PSTN
Packet TMSI
Packet Control Unit
Packet Data Protocol
Protocol Data Unit
Packet Identification
Personal Identification Number
Public-Key Cryptography Standards
Public Land Mobile Network
Packet Switched
Location Probability
Public Switched Telephone Network
73 / 87
Q
QoS
Quality of Service
R
Rel-4 Release 4
Rel-5 Release 5
RPLMN Registered Public Land Mobile Network
RT
Real Time
S
S-CSCF Serving CSCF
SAPI Service Access Point Identifier
SCCP Signalling Connection Control Part
SCP
Service Control Point
SGSN Serving GPRS Support Node
SIM
GSM Subscriber Identity Module
SIP
Session Initiated Protocol
SM
Short Message
SMS Short Message Service
SMS-SC Short Message Service - Service Centre
SS
Supplementary Service
SS7
Signalling System No. 7
SSF
Service Switching Function
SSN
Sub-System Number
STP
Signalling Transfer Point
T
TAC
TC
TLV
TMSI
TPDU
TS
Type Approval Code

Transaction Capabilities
Tag Length Value
Temporary Mobile Subscriber Identity
Transfer Protocol Data Unit
Time Slot
U
UE
UI
UL
UMTS
UP
URAN
USIM
USSD
UTRAN
User Equipment
User Interface
Uplink (Reverse Link)
Universal Mobile Telecommunications System
User Plane
UMTS Radio Access Network
Universal Subscriber Identity Module
Unstructured Supplementary Service Data
Universal Terrestrial Radio Access Network
74 / 87
V
VLR
Visitor Location Register
VMSC Visited MSC
VPLMN Visited Public Land Mobile Network
W
WAP
WIN
Wireless Application Protocol

Wireless Intelligent Network
75 / 87
8.
APPENDIX B: LOG ERROR MESSAGES
There are two possible types of error:

- blocking errors : it is impossible to continue the current processing operation. In this case, a
window informs you of the error that has been detected :
- Warnings: processing can continue, and warnings are displayed in the log file.
Severity
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Label
Missing or bad parameter for Polling
You have not declared an analyzer DLL
in the INI file.\nThe application operation
is therefore interrupted.
Error(s) found : %s
Nb failed (HORAC-HOCMP) (%lu) >
Nb REQ (%lu) => Nb failed=Nb REQ
Error in a database insert operation : %s
Error in %s
file list mode / On-line processing mode:
invalid command line (missing -f option)
Error in index addition into XL3 : %s
Error in update of source table : %s
Error while initializing extract server:
%s:%s
BSC name restoration: changing %s by

%s
Error in database creation : %s
Error in index addition into TRA : %s
Free memory during threshold purge is
not enough (%s Mo). The engine will
stop.
Description
Missing parameter for Polling
You must declare at least one analyzer DLL to run
CIGALE (otherwise it will not be possible to perform
any record file processing).
Error found in command line.
Number of failed HO.
Error while inserting in database.
An error as occured.
Missing parameter in command line. No ouptut
name define.
Error while indexing database.
The source database update has failed.
Error while initializing extract server. See Frame
Extractor configuration.
In the case of a BTS migration, the data process
detects an incorrect BSC name in the cell
description file: the process can not any more affect
the BSC name from description file. The BSC is also
considered as Unknown.
Error while writing in MySQL Database
Error while indexing database.
The memory used by the process is too high. To

prevent a crash, Cigale GSM is stopped.
Your licence Key is not valid. Please contact Astellia
Bad Licence Key !
support.
The FAC-EC-IMEI file declared in Cigale
FAC_EC_IMEI.txt filename does not exist configuration file is not present.
%s
Error.
The input file is not filled properly or we don't have
Incorrect Input File
R/W right on the path.
Analyser threw exception!!
Error occured in Analyzer (SDK error)
Analyser thread bailed out.. and user
code recvs AnalyserException!!
Error in Analyzer
Analyser : %s
Analyzer Info
Processing has been interrupted: Critical
error
Critical error with ocean 2G analyzer.
%s
Error in Protection process.
76 / 87
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
------------------------------------------------------------------------------------------------=> Loading the configuration file %s.

The %s configuration file is being loaded
=> Loading the %s declaration file %s. The %s declaration file is being loaded
=> Loading the state-machine %s ...
The state-machine is being loaded.
The state-machine has been correctly loaded. The
=> State-machine (ref. %s) loading
value given after corresponds to the state-machine's
completed.
internal reference."
=> States (ref. %s) loading completed. The states has been correctly loaded.
**************************************************************************
=====================
*** Start %s ***
Start of the process.
Cmd parameters: %s
Parameters of the application.
The application has been launched with
The application has been launched with no
no parameters.
parameters.
[Config] %s
Configuration.
2G cell description find in topology file
2G cell (GSM) description find in cell data base file
3G cell description find in topology file
3G cell (UMTS) description find in cell data base file
3G cells (UMTS), 2G cells (GSM), UMA cells
Mixed cell description find in topology file description may be find in cell data base file
The application has ended successfully.
The application has ended successfully.
Opening of the cell description file
completed.
Opening of the cell description file completed.
X Frames have been successfully purged in the
%d frames purged : OK
purge file with frame extractor.
EDX purge file copy OK : %s
Copy of the purge file is OK
EDX purge file copy failed : %s
Copy of the purge file failed
%s%s%s%s%s
Generic Message.
SCCP RESET message present.
A SCCP Reset message is present.
The cell described in the cell description file isn't
Cell %s transferred to BSC : %s.
really connected to the BSC declared.
Cell: %s
Problem with the cell.
GSM networks %s and %s have the
Two GSM networks have been declared with the
same code.
same code.
It is not possible to allocate an IMEI to the
IMEI already filled in.
transaction because it already has one.
Called number %s has already been
Several occurrences of the number have been
declared.
detected.
Requested AA bases : %s
AA Bases which will be generated by the engine.
Processing file %s, from %s to %s, with
All the files beetween the defined range will be
analyzer %s.
process.
Opening of the cell description file : %s.
Opening of the cell description file
Time slots : %d min.
Periodic Statistics creation timeslot.
Add File <%s> (ID=%i) successful
Creation of the purge file with frame extractor OK.
Problem with creation of the purge file with frame
Add File <%s> (ID=%i) failed
extractor
Cigale process certifies that the current MCC value
is correct (value specified by the user in Set
Application parameters : MCC certified to Parameter window OR value detected previoulsly
the value (%d)
by the process
Application parameters : changing MCC
value from (%d) to (%d)
The MCC is set to a new value.
Application parameters : MNC value
Cigale process certifies the MNC value associated
77 / 87
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
associated to MCC is (%s)

No error found on command line.
Command Line Analysis
CPU: %.2f %%, Memory: %.0f KB, Peak
Memory: %.0f KB, FreeDisk Space: %2.f
MB, FreeDisk Space for CDR Statistics:
%2.f MB, FreeDisk Space for View and
TA Statistics: %2.f MB, Number of IA:
%d, Number of connections: %d.
Total Memory: %d KB, Available
Memory: %d KB, Total Swap: %d KB,
Available Swap: %d KB, FreeDisk Space:
%2.f MB, FreeDisk Space for CDR
Statistics: %2.f MB
Error in EVE initialisation :%s
Error in EVE end session :%s
Megaco Error : %s
=> Session completed. %s
file %s is loaded
Analyzer frame error : %s
Frame redundant number :%s
Error while inserting SMS in the database
: %s
Error loading configuration : %s
Capture information versus Cell
description file information
BSC_name %s, %s cells of description
file are declared on BSC %s
Error in creating DB table : %s
CDR Output Statistics Directory is not
filled, the files will be generated in
Statistics default directory
Log Mode : %s
with the current MCC

Command line is correct.
Analysis of the command line.
System properties
System properties
Error while initializing EVE.
Error occured while terminating EVE.
An error occured on MEGACO frame.
Indicated the data and statistics process are over
The file is loaded by the engine.
A frame in the capture file is not correct. This frame
will be ignored.
The frame has already been seen. It will be ignored.
Error while inserting SMS in the database.
The configuration file hasn't been load properly.
Compare cell Info between cellcig.dat and capture
process
The BSC declared for the cell in cell description file
is incorrect.
Error creating Database.
CDR Output Statistics Directory is not filled, the files

will be generated in Statistics default directory
Describe the log mode (SHORT or VERBOSE)
EVE sent a callback indicating an error to the
Eve callback, Reactivity error : %s
engine.
Number of CDR sent at the end of the session with
endSession, CDR Sent = %d
EVE.
Number of CDR received at the end of the session
endSession, CDR Received = %d
with EVE.
endSession, Waiting time = %s (ms)
Waiting time at the end of the session with EVE.
Error in insertion in XL3 table : %s
Error in insertion into DB : %s
%s
Error.
=> Processing in progress...
A record file is being processed.
%s %s
Error.
%s - [%d%%]
Error.
=> Database ...
Writing in MySQL database
Second occurrence of a GSM network for A new GSM network for subscriber has been
subscriber : %s
detected for a transaction which already has one.
Error in TAC file line %d
A line of the TAC file is incorrect
Iden decoding is activated
Iden decoding is activated
78 / 87
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
CDR Builder licence is activated. All

outputs except periodic XL3 and daily
CDR Builder licence is activated. All outputs except
XL3 will be desactivated.
periodic XL3 and daily XL3 will be desactivated.
[Thread ID : %d] : %s
Thread ID
Number of Purge during overall process:
Part! %d, Cnx! %d, Timeout! %d,
Abnormal! %d, End! %d.
Number of purge during overall process
Number of Purge during last period: Part!
%d, Cnx! %d, Timeout! %d, Abnormal!
%d.
Number of Purge during last period
BSC equipment [GT-%I64x/PC-%d] has
been detected
BSC equipment has been detected
Requested Files : %s
Files which will be generated by the engine.
Requested Other Outputs : %s
Other outputs which will be generated by the engine.
flag file not found
Analyser thread stopped
The analyzer is stopped.
Analyser %s has stopped the current file process
Analyser : %s
Analyzer error
Analyser : %s
Analyzer Info
[%s] %s: %s %s
[Key] PerfName: PerfValue PerfUnit
[%s][%s] %s: %s %s
[Key1][Key2] PerfName: PerfValue PerfUnit
[%s][%s][%s] %s: %s %s
[Key1][Key2][Key3] PerfName: PerfValue PerfUnit
[%s,%s][%s] processed time range
TracePerf : %s,%s,%s,%s,%s
TracePerf
Volontary interrupted processing by the
user
User stop the process.
Processing has been interrupted: End of Problem with Ocean 2G analyzer. End of time band
time band
reached in capture file
Processing has been interrupted: End of
file
Problem with ocean 2G analyzer. End of file reached
Processing has been interrupted: No
more capture and near of end of time
Problem with Ocean 2G analyzer. End of time band
band
reached in capture file
Processing has been interrupted by real
time server
Real time server stop the process
Processing of a record file has been completed
Processing completed, %s
(duration).
Statistics...
The statistics are being generated.
Statistics completed, %s
The statistics have been generated (duration).
End of file processing
End of file processing
STOP
Stop of process
Running post process...
Post process start
Post process completed.
Post process completed.
It is not possible to allocate an IMSI to the
IMSI already filled in.
transaction because it already has one.
=> Writing of %s ...
Writing of BDT files
=> Writing of %s completed.
Writing of BDT files complete
=> Conversion of .ADT files
completed.
ADT File conversion completed.
Frame N%s desynchronized with respect to the last frame processed (N%s) by %s
milliseconds.
Executing scheduled action %s at (%s)
79 / 87
Info
Info
Info
Info
Major
Major
Major
Major
Delete file %s
Probe number : %d detected on : %s
=> Loading the event declaration file
%s.
Event n %d : %s" was called %d times"
[Internal] GetProcAddress failed
[Internal] LoadLibrary failed
State-machine description file missing.
%s file missing
Major
State %s without transition.
Major
State %s without generic transition.
Major
Major
File %s incorrect
File %s incorrect: %s
Line %s in file %s is incorrect.It will
therefore be ignored.
Incorrect %s description file version
number.
The version number of DLL %s\n
declared in the CIGALE.Conf file is
incorrect.
DLL %s declared in the configuration file
does not exist.
DLL %s declared in the configuration file
is not an analyzer DLL.
DLL % declared in the CIGALE.CONF file
is incorrect\n(it does not enable an
analyzer to be created).
DLL %s declared in the CIGALE.CONF
file is an incorrect file.
Analyzer %s\nis declared several times in
the CIGALE.CONF file
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
The event declaration file is being loaded.

Problem occurs while loading a DLL.
Problem occurs while loading a DLL.
The state-machine description file is missing
A file is missing.
The state does not have any transition. It therefore
corresponds to a final state, which is incorrect.
The state does not have any generic transition. It
can therefore correspond to a final state for certain
events, which is incorrect.
The file does not correspond to the expected type of
file.
The file is incorrect.
A line in the file is incorrect. This line will be ignored.
The file have a wrong version number.
The DLL is not compatible with CIGALE.

A DLL declare in the Cigale configuration file is not
present in the DLL repertory.
A DLL declare in the Cigale configuration file is not a
valid DLL.
The DLL is not compatible with CIGALE.
Analyzer DLL is invalid

The same analyzer DLL has been declared several
times.
The line specifying the compatible version of
The EFFICACE version declaration line is EFFICACE is incorrect in the state-machine
incorrect (%s).
declaration file.
Line ignored: %s.
A line of a file has been ignored.
Line incorrect: %s
The line is incomplete.
The TIMES.BDT file is not compatible
with the state-machine description
The TIMES.BDT file is not compatible with the statefile.\nReading of this file is interrupted.
machine description file
Impossible to create a transition: it must
include 2 states and an event.
Incorrect transition
Transition request error : it must include a
state and an event.
Incorrect transition.
Invalid Cause Type: %s
An invalid cause has been defined in the cause file.
Cause duplicated (line %s).
A cause has been defined twice in the cause file.
Cause invalid (line %s).
An incorrect Cause value has been detected.
The name of the protocol associated with the event
Event %s: Incorrect protocol name.
is incorrect.
80 / 87
The name of the protocol associated with the event

is incorrect.
The event's extension is incorrect.
Incorrect event.
An event code is invalid.
The input directory of edx files is missing in polling
mode.
Polling not supported by analyzer
The current analyzer DLL is not compatible with the
record file. Cigale is therefore using a compatible
DLL for processing.
All the ports of analyzer are connected for this
processing operation.
A error occured while initializing frame extractor
client.
Problem with creation of the purge file
Problem with creation of the purge file
Indicated that states configuration file is missing
Major
Major
Major
Major
Event %s: Incorrect protocol.

Event %s: Incorrect extension.
Event %s : Incorrect code.
Invalid event code (line %s).
Major
Major
Input directory missing for Polling

Polling not supported by analyzer %s
Analyzer %s replaces analyzer %s (due
to incompatibility) for this processing
operation.
All the ports of analyzer %s are
connected for this processing operation.
Error while initializing extract server:
%s:%d
%d frames not purged : failed!
Error while building EDX purge File!
State description file missing
Impossible to create a handover link (%s)
(already exists).
Impossible to create a handover link.
The links between handovers have been found by
HOCMD_RR : Conflict between certified means of the cell numbers (CI) but the BSIC and
cell %s (HOCMD) and the proposed
BCCH are different whereas the cell is declared to
BSIC %s and BCCH %s.
be certified.
An unknown mobile revision level has been
Incorrect Classmark Revision Level.
detected.
Incorrect state-machine version number. The version of the AUTOMAT.BDT file is not valid.
The number of ports per board (%s)
defined in the analyzer DLL %s\n must
The number of ports per board defined in an
be an even number (RX and TX ports).
analyzer DLL must be an even number. The DLL will
The DLL is therefore ignored.
be ignored.
The resynchronization buffer must be
An invalid value has been entered for the
comprised between %s and %s.
resynchronization buffer size.
The number of user messages must be
An invalid value has been entered for the number of
comprised between %s and %s.
user messages.
Threshold for detection of ping-pong
handover must be comprised between
Threshold for detection of ping-pong handover isn't
%s et %s seconds.
correct.
Unknown handover type.
The handover type does not exist.
CIGALE is trying to link various connections when
performing handovers using the reference of the
handover and BSIC, BCCH and Channel description
elements. When this link was created, CIGALE
established the link between the two connections
Impossible to assign an origin to the
concerned. This error occurs when you try to link a
handover link (%s) (one already exists).
third connection.
You must define at least a state or an
The line in the timer declaration file is incorrect
event (line : %s).
because it must contain at least one state or event.
Event missing (line : %s).
Event missing.
Incorrect state (line : %s).
Incorrect state.
Incorrect timer description file version
number.
Invalid version of the TIMES.ADT file.
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
81 / 87
Major
Timer type incorrect (ligne : %s).
Major
Timer missing (line : %s).
Major
Undefined timer (line : %s).

Processing data aborted: error detected
in file %s
Error on a transaction's duration.
Error on a transaction's communication
duration.
Error on a transaction's ringing duration.
SCCP protocol : frame of length [%s]
ignored.
Major
Major
Major
Major
Major
Major
Major
Major
TP protocol delimitation error.

Incorrect %s message code: %s.
Incorrect called number description file
version number
Process goes on without information
loaded from cell data base file
Major
Read error on Cell identifier list.
Major
Error while loading extract DLL: %s
Major
Error while initializing extract DLL : %s
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Application licence limited to %d MSC.

(%d MSC detected)
The GSM network's %s code is invalid
(line %s).
Frame of length [%s] ignored.
Timer description file missing.

because the timer type is incorrect.
because it does not include an associated timer.
because it must contain at least one state or event.
A problem occured while reading trace file with the
analyzer.
Transaction duration is incorrect.
Transaction communication duration is incorrect.
Transaction ringing duration is incorrect.
The SCCP frame length is incorrect. The frame will
be ignored.
The length read in the frame for the TP protocol is
incorrect (frame too long).
The message code found in the frame doesn't exist.
Invalid version of the PHONES.ADT file.
The cell declaration file hasn't been found. Cell will
be named by their point code.
The Cell Identifier List element read in the frame is
incorrect.
Error while loading extract DLL. See Frame
Error while initializing extract DLL. See Frame
Crypkey licence is limited to x MSC. (x MSC are
detected). Check your links or contact Astellia to
have an other licence
Network code is invalid.
Frame length too short. This frame will be ignored.
The timer description file is missing.
The TAC file declared in Cigale configuration file is
not present.
TAC.txt filename does not exist

EDX purge File build OK : <%s> (%i
Frames purged)
Creation of the purge file with frame extractor OK.
Error in EVE starting session : %s
An error occured while lunching EVE client.
File XLF_XLH - correction on HO In
HO statistics number incorrect. Value will be
statistics : origin %s destination %s
corrected.
%s. Activity Analysis output is
desactivated
Test on validity of MySQL output
The TA output directory is empty. Ouptuts files will be place in Cigale default ouptut directory.
Error in insertion of XL3 frame : %s
Analyzer %s : %s
Error in Analyzer.
Error while building EDX purge File! See Frame
Error while building EDX purge File : %s Extractor configuration.
Can't create Central Database. Error : %s The central database can't be create.
Wrong Header in TAC files
the header of the TAC file is insorrect
Capture redundancy : %d frames
Capture redundancy
Error opening SSN.conf file : %s
Error occured while opening SSN.conf file
82 / 87
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Major
Periodic XL3 Path is not filled. Periodic XL3 output will be desactivated.
End of threshold memory purge (Number
of purge Part!: %d, Number of purge
Timeout!: %d, Free memory: %s).
End of threshold Purge.
Process memory is too high (%s Mo),
Process memory is too high, threshold purge
threshold purge starting.
starting.
Undefined GlobalTitle [%I64x]: PointCode Undefined GlobalTitle : a PointCode will be affected
[%d] will be affected to this GlobalTitle
to this GlobalTitle
Immediate Stop asked by ASM, data
Immediate Stop asked by ASM, data might have
might have been lost while stopping.
been lost while stopping.
Analyser : %s
Analyzer Info
Unknow Exception
Unknow Exception
CAUTION: Processing interruption because there is less than %s Kb memory left.
Processing has been interrupted because Processing of a record file has been interrupted
an error has been detected.
because an error has been detected.
Processing has been interrupted: Time
out
Problem with ocean 2G analyzer.
Processing has been interrupted: Bad
Problem with Ocean 2G analyzer. The flag is
flag
created but EDX file does not existed.
Processing has been interrupted:
Problem with ocean 2G analyzer. Capture files are
desynchronized files
in the disorder
On demand process error: no connection
found.
On demand process error: no connection found.
Exception while trying to connect to
database
Exception while trying to connect to database
PSM Error: %s
SDR Sender Client Error: %s
A problem occured in SDR client (TT or SLM)
UPCS Error: %s
File %s skipped --> File time earlier than current time
Unable to open %s
Probe : %d is timed out
Maximum probe number reached : %d
[Probe : %d] Unknown Exception while %s
[Probe : %d] Exception while %s : %s
File %s is invalid.
File %s incorrect. Its identification line
The file does not correspond to the type of file
'%s' is missing.
expected because line ... is missing.
Unknown cause (line : %s).
An unknown Cause value has been detected.
The event description file is not present in the
Event description file missing.
CIGALE conf directory.
Incorrect event description file version
number.
Invalid version of the EVENTS.BDT file.
Line incorrect (Extension, cause and
destination state missing) : %s.
The line is incomplete.
Cause description file missing.
The cause declaration file is missing.
Invalid cause type (line %s).
The cause is incorrectly defined.
Two occurrences of the same cause have been
Cause duplicated (line %s).
detected.
Incorrect cause description file version
number.
Invalid version of the CAUSES.BDT file.
Line ignored (unknown Cause) : %s.
The cause is incorrect.
Line ignored (unknown extension) : %s.
83 / 87
Major
Major
Major
Major
Major
Major
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Line ignored (unknown Event) : %s.

The event is incorrect.
Line ignored : %s (A generic transition
A generic transition (any event) must not be broken
cannot have a cause).
down according to causes.
Line ignored : %s (A generic transition
A generic transition (any event) must not be broken
cannot have an extension).
down according to causes.
Line incorrect (Destination state missing) : %s.
Line incorrect (Cause and destination state missing) : %s.
Line incorrect (Event, extension, cause and destination state missing) : %s.
Serious errors have been detected while loading the
state-machine. The state-machine is therefore
invalid. You will have to ask your administrator for a
new state-machine and inform him of the errors
displayed in the user message zone. The value
=> State-machine (ref. %s) loading
given after %s corresponds to the state-machine's
interrupted.
internal reference."
The %s --- %s -- %s ---> %s
Two occurrences of the same transaction have been
transition already exists.
detected.
The state does not have any transition. It can
State without transition. Unknown
therefore correspond to a final state for certain
transition (and therfore ignored).
events, which is incorrect.
Transition %s %s %s unknown (and
therefore ignored).
The transition does not exist.
Unknown extension : %s.
The extension does not exist.
The event does not correspond to any declared
Unknown event : %s.
event.
Trying to add transition that is already
A transition has been defined twice in the automat
referenced in transition list
file.
Trying to add cause that is already
referenced in cause list
A cause has been defined twice in the cause file.
Trying to add event that is already
referenced in event list
An event has been defined twice in the event file.
A cell that is not filled in in the cell data base file has
Unknown cell : %s.
been detected lac is also mentionned
%s invalid on line: %s
Invalid line.
Duplicate cells have been detected
Several definitions of cells with the same CI have
(Cell_%s).
been detected.
Duplicate SAI have been detected
Duplicate SAI have been detected in cell data base
(SAI_%s_%s).
file
Code error : %s (%s expected) in [%s]
An incorrect code element has been detected during
field.
decoding.
A cell data base file is required in order to carry out
processing. You must therefore declare one before
A cell data base file must be specified.
carrying out this processing operation.
File error : Problem of capture. Check
links!
There is a problem in capture file. Check links!
HOREQ message : The connection
Connection identifier already in used for another
already has a handover.
connection.
Crypkey licence is limited to x MSC. (More MSC are
Software licence limited to %d MSC
detected). Check your links or contact Astellia to
(more MSC detected)
have an other licence
Ciphering Key Sequence Number | CM
Service Type : Unknown service type
CM Service Type is Unknown in CMSRQ message.
84 / 87
(CMSRQ).
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
LUACC : Allocation of different GSM

networks.
HOCMD_RR : Unique cell %s allocated

although not identified by the proposed
BSIC %s and BCCH %s.
Incorrect number of %s resources.
Negative duration of %s resource
allocation.
Extraction of state : %s.
Incorrect Classmark.
A location update acceptance has been detected

with a GSM network value different to that in the
location update request.
When performing a handover for which only one cell
has been proposed, if that cell has a BSIC and a
BCCH different to those defined in the cell data base
file, the cell is selected and its BSIC and BCCH are
updated.
The number of resources isn't correct.
Duration of resource alloction inferior to 0.

The state-machine's state .. is currently being read.
An unknown Classmark value has been detected.
A cell that is not filled in in the cell data base file has
Unknown cell: %s allocated to BSC : %s. been attached to a BSC.
A BSC has been identified during processing that
corresponds to the A interface. The A interface is
The BSC %s is now incorrect and IA
therefore attached to that BSC and its BSC's Info
Number %s is attached to the new BSC
(resources, cells, etc.) is transferred to the new
(%s).
BSC.
A connection closing has been requested but the
transit direction of the frame between the BSC and
Non-oriented connection %s.
the MSC is still unknown.
The GSM network description file is not present in
GSM network description file missing.
the CIGALE execution directory.
Incorrect GSM Network description file
Incorrect GSM network description file version
version number.
number.
The number of ports (%s) defined in the
The number of ports per board defined in an
analyzer DLL %s\n can't be upper than
analyzer DLL can't be upper than 1000. The DLL will
1000. The DLL is therefore ignored.
be ignored.
Allocation of a CIC has been requested for a
Allocation of a CIC to connection that
connection but that connection has already reserved
already has one.
a CIC.
A TCH allocation has been requested for a
TCH allocation to connection impossible connection, but that connection has already
(already allocated).
reserved a TCH.
The end timer in the timer declaration file is not of
The end counter is not of the same type
the same type (BSC or Cellule) as the start timer it is
as the start counter (line : %s).
associated with.
Events %s and %s have the same code. Two events have been declared with the same code.
An end timer has been declared with the same
The end counter has already been
name in the TIMES file but with a different type of
declared with another type (line : %s).
counter (BSC or Cell).
The theoretical length of a frame has been
Frame length exceeded for message %s. exceeded when decoding that record frame.
Called number description file missing.
The called number declaration file is missing.
%s MAP messages detected but
At he end of session Info about untreated MAP
untreated
messages
A 1/2 byte element is expected instead of
%s [%s].
Element size isn't correct.
Duplicate RNC have been detected
Duplicate RNC have been detected in cell
85 / 87
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
(RNC_%s).
Duplicate BSC groups have been
detected : %s.
HOREQ message without a %s.
description file.
Distinct BSC groups have been detected.

A message is missing in sequence of message.
The A interface number # has x opened connections
and Cigale has purged them In most of the cases
the reason is that the messages for opening
connexions has been captured but not the following
Problem with partly opened connections : ones (It shall be checked if the capture file is based
%s connections purged.
on all necessary signalling links).
Impossible to create an IA [%s] (max
Max number of IA is reached. No statistics will be
number = %s reached).
created on new IA which may be seen.
It has not been possible to associate a
start counter with an end counter (line
%s).
Line of the Times declaration fileis incorrect.
Nb HOcmd (%lu) < Nb HOsu (%lu)
=> failed=0
Number of HO message.
Nb CMP (%lu) > NbRAC (%lu) =>
failed=0
Number of correct HO.
Nb responses (%lu)> Nb REQ (%lu)
=> Nb responses = Nb REQ
Number of HO Request.
Error in the database update : %s
Error while updating database.
Update BSC name (old=%s new=%s
The BSC name was incorrect.
replace id (old=%s new=%s
Database id is incorrect.
Exception line : %s
Exception occured.
Error in sending CDRs to EVE : %s
Error while sending a CDR to EVE occured.
Error when get CDRs from EVE : %s
Error while reading a CDR received from EVE.
Frame Error : %s
The frame is incorrect. It will be ignored.
Files processed : %d
Number of processed files
Total processed file size : %.2f Go
Total size of processed files.
Total process duration : %s
Total process duration
Total connections : %d
Total number of connections
...
None of the cells in the list of proposed cells
HOCMD_RR : No cell corresponds to
(HORQD) corresponds to the proposed BSIC and
BSIC %d and BCCH %d.
BCCH (HOCMDRR).
PC of BSC %s isn't filled line %s in file
%s
The central database can't be create.
Error in FAC-EC-IMEI file line %d
A line of the FAC-EC-IMEI file is incorrect
Wrong Header in FAC-EC-IMEI files
the header of the FAC-EC-IMEI file is insorrect
Gs decoding is activated
Gs decoding is activated
Global Title %I64x is defined several
times in globaltitle_pointcode.txt file. Only A Global Title is defined several times in
the first occurence of this Global Title will globaltitle_pointcode.txt file. Only the first occurence
be used.
of this Global Title will be used.
No more file to proceed
File is not opened
Not GSM compliant file
Out of band origin
Error in SDK GetProcessLastFrame
Error in SDK DecodeType
Error ibn SDK GetProcessFirstFrame
86 / 87
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Warning
Error in SDK StartCaptureStreamExtr

End frame of file not found
Start frame of file not found
SetDecipherParam called in
MTProxyAnalyzer when not in INIT state
SetInterfaceFilter called in
MTProxyAnalyzer when not in INIT state
MTProxyAnalyzer::update(info) BUT NO
CgFrameBuffer to apply it to!!

Error in Analyzer
Error in Analyzer
Error in Analyzer
Stop of the process (the end time band defined by
Time out reached in polling mode
the user is reached)
View - correction on HO In statistics : origin %s destination %s
A location update acceptance has been detected
LUACC : Allocation of different LACs :
with a GSM network value different to that in the
%s - %s.
location update request.
Analyser : %s
Analyzer Info
The current connection is closed and then opened
Connection closure on double
again subsequent to a new opening request for the
connection.
same connection.
=> Conversion of .ADT files
interrupted.
ADT File conversion is interrupted.
Action: %s is reported 24h later
Scheduled operation change asked at %s is out of file start time %s
Debug Message : %s
Mode Debug : %s
87 / 87

Cigale GSM User Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cigale GSM User Manual

Uploaded by

Copyright:

Available Formats

Cigale GSM v6.

CIGALE GSM V6.6 USER MANUAL

Copyright ASTELLIA, April 2013

ALL RIGHTS RESERVED

CIGALE GSM V6.6 USER MANUAL

GENERAL INTRODUCTION ................................................................................................... 5

CIGALE GSM V6.6 USER MANUAL

6.2.13. TIM : VALUES OF THE TIMERS .............................................................................. 67

CIGALE GSM V6.6 USER MANUAL

1.1. OVERVIEW OF CIGALE GSM

QoS & Benchmarking

Operation & Maintenance

Better know users and

Early failure detection

GSM Solution (figure 1)

CIGALE GSM V6.6 USER MANUAL

parameterization of the transitions state-machine and of the associated statistics through

CIGALE GSM V6.6 USER MANUAL

Statistics with MSCs in Pool

CIGALE GSM V6.6 USER MANUAL

CIGALE GSM V6.6 USER MANUAL

HARDWARE AND SOFTWARE CONFIGURATION

GENERIC HARDWARE AND SOFTWARE CONFIGURATION

For an optimal use and comfort, the following configuration is recommended:

Multiple simultaneous accesses to dB

Fast results availability

Capture multiple sources simultaneously

CIGALE GSM V6.6 USER MANUAL

CIGALE GSM V6.6 USER MANUAL

4.2.2. LICENSE INFORMATION

Licence box (Figure 3)

CIGALE GSM V6.6 USER MANUAL

ASTELLIA SYSTEM MANAGEMENT

Astellia System Management features are:

BCK, TEXT, XL3 (temp)

ASM - System Controller

ASM System Management

CIGALE GSM V6.6 USER MANUAL

CONFIGURATION FILE DESCRIPTION

State machine description

NETWORKS, TIMES, PHONES

5.2.2. ASTELLIA PARAMETERS EDITOR

CIGALE GSM V6.6 USER MANUAL

The differents sections

5.2.3. CIGALE GSM CONFIGURATION FILE

CIGALE GSM V6.6 USER MANUAL

Networks File Path

MSS Pools used

CIGALE GSM V6.6 USER MANUAL

Determines the country code [MCC] of mobile networks for

MTP2 extended can be used in HSL processing. Default

Integration of MEGACO Information to CDR.

CIGALE GSM V6.6 USER MANUAL

Number of containers for MEGACO transaction purge. By

Enable or disable the Iden processing.

Detail SMS User

CIGALE GSM V6.6 USER MANUAL

End of the time range

Online timeout (s)

Processing is stopped if no new file arrives before timeout

While processing in polling mode, the Cigale engine will not

Max duration for

Max duration for connection attempt (in minutes)

Process mode options