Master your Network Performance in 40 Characters

Master your Network Performance
1
Week 38 : CIGALE GSM
- Cigale GSM
- Cigale GSM Engine
- Cigale view
- Activity analysis
- Cigale Trace
Week 39 : CIGALE ROAMING, CIGALE ISUP and value added services

- Cigale Roaming
- Roaming view
- Abis surfer
- Cigale ISUP
- SLM
- Trending and Aggregation
Week 40 : MANTA, OCEAN

- Manta
2 - Ocean
- Processing tools
- AstAdmin
Monday, September 26th : Astellia presentation, schedule of the week, Cigale Roaming
9h30 Astellia presentation : Christian Queffelec & Frdric Vergine
10h00 Schedule of the week : David Gallas
10h30 Cigale Roaming : Emmanuel Ricci
Tuesday, September 27th : Roaming View

9h-17h Roaming View : Emmanuel Ricci
Wednesday, September 28th: Study of a capture file from Orange Cameroun network
9h-12h capture file study : Emmanuel Ricci
14h-17h Abis surfer : Jean-Marc Boisumeau
Thursday, September 29th : Cigale Isup

9h-17h Cigale Isup : David Gallas
Friday, September 30th : SLM, Trending & Aggregation and debriefing

9h SLM : David Gallas
14h Trending & Agregation : Xavier Roux
3 16h Debriefing : Emmanuel Ricci & David Gallas
Headquartered in Rennes - France
Offices in Paris, New York and Singapore
A worldwide Partner & Representative Network
A 20-year experience in the Telecom industry
75 highly qualified people
7.5 M Turnover in Y2004 (6 M in Y2003)

4
More than 100 mobile network operators & vendors worldwide
already entrusted us
Hardware & Software solutions
for
QoS Analysis
Network Optimization
Troubleshooting
Value Added Services
A clear view on Infrastructures,

Customers & Services for
Technical departments
Marketing department
General management
5
Expert in solutions dedicated to Network Operators & Vendors

HLR
PSTN ISUP
MSC
GGSN Gi
Gr
C/D
BSC A SGSN
PCU
Abis Gb
BTS Gn
Other
PLMN
Gp
Abis IuCs
BTS
IuPs
RNC
NODE Iub
B Iur
RNC
NODE Iub
B
6
ite3 e
S p tur
Ca sing
ite2 es
S ro c g Ex
t-p r tin po
ite1 s epo rt
S Po R
Engine i ng&
ro ws
B Operators
Database
Database
Engine GIS
Web
SLM Reports
me Roaming
t i
a l- sing
Re ces KPIs Browsing Operators
pro Troubleshooting customization
IMSI Tracking
Fault Management
7
Astellias solution
Your needs
Supervision Systems
Supervision
QoS
Performance Astellias Solution
VAS
Troubleshooting Protocol Analyzers
8
Products Massive Mobile
Features Call Trace Statistics
capture Expertise
!
Advanced KPIs
Correlation between service access and
radio network behaviour
Detailed information available per
network area (cell, ) or network
equipment (BSC, MSC, SGSN, RNC )
A complete and open solution

Automated process
Statistics browser
Customisable reports
KPIs export to your information system
9
"
Top-down troubleshooting tools

Detailed statistics on
communication progress
Call Data records
Detailed communication
analysis
Dedicated to mobile operators

Based on whole network traffic
Search by cell, mobile identity,
communication event,
Investigation after customer
complaint, OMC alarm,
10
# $ % &' ( )
Radio Optimisation
Radio planning validation
Validation and tuning of power
control algorithms
Handover optimisation
Interference detection
System Optimisation
Equipment failure detection
11 Congestion detection
*
+, ' -
With Astellia ROAMING solution,

get an easy answer to these questions:
Where are the main roaming capture zones?
How efficient is the capture of roamers?
How efficient are the improvement actions?
What profiles do roamers have?
How much traffic do roamers generate?
Where are roamers lost?
and increase your roaming revenue
12
*
+, ' - .
Attract and retain Major Business
Customers with enhanced SLA (Service
Level Agreement)
Establish a common understanding of SLA
Monitor up to 1000 accounts
Gain a visual evaluation of SLA
Improve provided QoS
Increase traffic and revenue
Strengthen your image
13
'' # /
14
'' # 0
15
&
Alcatel Ikatel
Aria Jersey Telecom Orange Reunion
Base Loteny Telecom Orange Romania
Belgacom Mobile Maxis Orange Thailand
Bouygues Telecom Mobilecom Orascom Telecom Algeria
Cell Plus Mobinil Orascom Telecom Tunisia
Cellis Mobistar P&T Luxembourg
China Telecom Motorola Pannon
China Unicom MSI / C eltel SFR Cegetel Reunion
Cingular Wireless MTN SFR France
Cosmote Net One Siemens
CSIT Nokia Sonatel
Digitel O2 STA
DTAC Optimus Syryatel
Dutchtone Orange Cameroon TA Orange
Fastlink Orange Caribbean TDC Denmark
France Telecom Orange CH Telefonica
Gibtel Orange Ivory Coast Vodacom
Go Mobile Orange Denmark Vodafone Malta
16 H3G Austria Orange Dominicana Vodafone Spain
3 UK Orange France Voxtel
Huawei Orange Madagascar Western Wireless Int.
/
www.astellia.com
Cigale Roaming, Cigale ISUP

17
and Value added services



Roaming Module
Applications
Software organization
Roamers detection
Nature of results
Data available
Administration
Cigale batch
Cigale GSM
Cigale roaming
19
Roaming View
Data representation
Location updates
Traffic
User configuration
User defined area
Database handling
Cells description file
20
Roaming Analysis
Principles
Identities level
Detailed level
Case Study
From roaming view to roaming analysis
21
Loss of roamers
Overview
Loss & recovery detection
Main indicators
Examples
Appendix
Location Update flow
Location Update reject causes explanation
Identities and detailed levels columns description
22
Cigale ISUP
Overview
ISUP messages
ISUP automat
Benefits
Process and viewer
Engine description
ISUP configuration
23
ISUP Analysis
Overview
Database
Interface description
Transitions
Setup efficiency
Traffic Report
Resources
CDR
Case study
24
SLM
Description and architecture
Probe level
Key concepts
SLA Management
SLM Activity Analysis
25
Trending & Aggregation for roaming
Operator requirements
Product presentation
Trending & Aggregation Roadmap
Conclusion
Q&A
Abis surfer
Introduction
Abis Surfer principles
26 Standard reports:
Case studies



28
Application Data available
Software organization Administration
Cigale batch
Roamers detection
Cigale GSM
Nature of results Cigale Roaming
Roaming Module
Applications
Software organization
Roamers detection
Nature of results
Data available
Administration
Cigale batch
Cigale GSM
Cigale roaming
29
Application (1/5) Data available
Cigale batch
Roamers detection
Cigale GSM
Detection of cells welcoming the highest number of

roamers (location updates) and where roamers generate
the most important traffic :
Technical aspect :
Improve the catch rate
Increase traffic
Coverage, radio parameters
Regular follow-up of catch rate and traffic.
Marketing aspect, specific advertisement :

From a geographical point of view
30
From a cultural point of view (country of origin)
Cigale batch
Roamers detection
Cigale GSM
Analysis of roamers traffic per network of origin
Detect specific behaviours and consumption modes in relation

with the country of origin :
short numbers,
SMS,
data calls, etc
SS (Supplementary Services: call forwarding, call waiting )
31
Cigale batch
Roamers detection
Cigale GSM
Coverage compared to competitors
competitors coverage holes : points where their subscribers try to

locate on your network
for your own subscribers : comeback points and previous

network where a location update was performed
for your own subscribers : points where they come back with a non
valid Old LAC value.
with LOR option : points where roamers leave your network or loose
32
your network
Cigale batch
Roamers detection
Cigale GSM
Be sure that the roamers can localise in your network

(analysis of reject causes)
Radio problems
Roaming specific problems (international gateways)
No inter operator agreement (generalised PLMN Not Allowed)

marketing
Subscriber without roaming option (partial PLMN Not Allowed,

Roaming Not Allowed in this Area)
33
Services not supported or restricted
Cigale batch
Roamers detection
Cigale GSM
Reach and maintain a higher QoS on cells where roamers

traffic is high.
Location updates (capture and transit)
Call setup inefficiency (avoid congestion)
Call drops (could be confirmed with Cigale View)
34
Cigale batch
Roamers detection
Cigale GSM
"
# $$$
"
% &
35
!
Cigale batch
Roamers detection (1/6)
Cigale GSM
A roamer can be detected by Cigale roaming engine thanks

to its IMSI
3 digits 2-3 digits 9-10 digits
MCC MNC MSIN
IMSI
15 digits
MCC : Mobile Country Code

MNC : Mobile Network Code
MSIN : Mobile Subscriber Identification Number
36
Cigale batch
Cigale GSM
IMSI is transmitted on A interface:
when a user performs a location updating request and there is no

user information in VLR, because :
The user is coming from another network or another VLR
The user was detached after a determined period
The user transmits its IMSI to the network
In case of Mobile terminating procedure: MT Call or MT-SMS
Paging message of A interface includes IMSI

37
Cigale batch
Cigale GSM
Location Update flow

Establishment of the RR connection, service indication and authentication
MS BSS MSC/VLR HLR

RR CHANNEL REQUEST
RR IMMEDIATE ASSIGNMENT
MM LOCATION UPDATING REQUEST

SCCP CONNECTION REQUEST
Info:
[BSSMAP COMPLETE L3 INFO
LU type:
- normal
[LOCATION UPDATING REQUEST]]
- periodic MAP_SEND_AUTHENTICATION_INFO
- IMSI Attach
MS identity: SCCP CONNECTION CONFIRM
- TMSI or IMSI MAP_SEND_AUTHENTICATION_INFO ACK
LAI
MM AUTHENTICATION REQUEST
38
MM AUTHENTICATION RESPONSE
Cigale batch
Cigale GSM
Ciphering mode
MS BSS MSC/VLR HLR
MAP_UPDATE_LOCATION
MAP_INSERT_SUBSCRIBER_DATA
MAP_INSERT_SUBSCRIBER_DATA ACK
BSSMAP CIPHER MODE MAP_UPDATE_LOCATION ACK

RR CIPHERING MODE COMMAND
COMMAND
RR CIPHERING MODE
COMPLETE
BSSMAP CIPHER MODE
39 COMPLETE
Cigale batch
Cigale GSM
Allocation of temporary identity and release of the radio channel
MS BSS MSC/VLR
Info:
MM TMSI-REALLOCATION COMMAND New TMSI
MM TMSI-REALLOCATION COMPLETE
MM LOCATION UPDATING ACCEPT
BSSMAP CLEAR COMMAND

RF CHANNEL RELEASE
BSSMAP CLEAR COMPLETE
40 SCCP_RELEASED
SCCP_RELEASE COMPLETE
Cigale batch
Cigale GSM
Once IMSI is detected, Cigale Roaming is able to follow up

the complete activity of a roamer during the capture period
by:
Using IMEI
Following TMSI reallocations
Limitations :
For short time captures
Inter - record area incoming handovers (except if IMSI is included
within HOREQ message)
41
Cigale batch
Roamers detection
Cigale GSM
Nature of results (1/2) Cigale Roaming
Statistics based on Roamers

location updates
LOR option (correlation with
MAP-I)
Statistics based on roamers
traffic (voice and data calls,
SMS, SS)
QoS KPIs on Roamers activity
Detailed Roamers activity

42
Cigale batch
Roamers detection
Cigale GSM
Nature of results (2/2) Cigale Roaming
One part of results is computed by Cigale

Roaming (most of it)
Other computed by RoamingView

(agregation, User(cells), User(networks))
See Roaming User Manual
43
Cigale batch
Roamers detection
Cigale GSM
Level of Analysis Information Granularity
Traffic
Location Network down to cell
Statistics LOR
update
Total - per IMSI SMS - calls
QoS KPIs on Roamers Activity IMSI

QoS
Report
Details on Roamers IMSI

Detailed activity
44
Cigale batch (1/5)
Roamers detection
Cigale GSM
Cigale batch has been implemented in order to manage

easily the different Cigale components including the
roaming process.
Cigale batch takes into account the following functions

Record file storage management
Rename options
Disk cleaner options
Record file processing to extract messages and associated data on
A interface (Cigale GSM)
Database import for Cigale View
45 Roaming activity processing (Cigale Roaming)
Identities activity processing (Cigale Trace)
Cigale batch (2/5)
Roamers detection
Cigale GSM
Configuration
of global
parameters
A
B
C
D
Configuration
of process E
applications
F
46
H G
Cigale batch (3/5)
Roamers detection
Cigale GSM
Configuration of global parameters
No rename: the capture file wont be renamed
Quantum: add a number to the input file name
Year-month-day: add the date to the input file name
Use file date: if checked, the reference date is the date of capture file, if not
the reference date is the current date.
Delta: Number of day you want to add or withdraw to the previous day
47
Prefix or suffix: position for the number or date that will be added
Cigale batch (4/5)
Roamers detection
Cigale GSM
Disk cleaner: if checked, disk cleaner is enabled
Minimum disk space: free disk space to keep on the hard disk
Folder to clean: the software will delete the oldest files from this directory
Clean subfolders: if checked, cigale batch will include the subfolders of the
Folder to clean for the deletion of oldest files
Delete special files: if checked, cigale batch will also delete files with the
extension exe, com, bat, ini & cmd
Keep capture file: minimum duration (in days)
Capture file extension

48
Set a priority on deleting capture files: if checked it will try to delete first
capture files as they are often quite big files
Cigale batch (5/5)
Roamers detection
Cigale GSM
Configuration of process applications

A: Select a record file
B: Select the complete path and name of the Cigale application
C: Launch Cigale application (to configure cigale parameters)
D: Cigale roaming parameters (as output directory, Myarea name..)
E: Select the complete path and name of the Cigale Roaming application
F: Launch Cigale Roaming application (to configure cigale roaming

parameters)
49 G: To start the process
H: To save CigaleBatch parameters

Cigale batch
Roamers detection
Cigale GSM (1/7)
Cigale GSM can be described as a "spy" placed in the network at

the level of the A interface,between the BSC (Base Station
Controller) and the MSC (Mobile Switching Center), which
analyzes in store-and-forward mode the protocol frames stored
by a recorder placed on the signaling channels.
Cigale GSM provides, with one of these platforms, statistical files

which are processed with the help of the graphical operational
module Cigale View
50
Cigale batch
Roamers detection
Cigale GSM (2/7)
User interface
51
Cigale batch
Roamers detection
Cigale GSM (3/7)
Cells database file
These files are used when processing record files to name the
detected cells, designate their BSC, LAC and fill in their BSIC and
BCCH.
The extension of the cell data base files is DAT.
You can select a cell database file using the Options / Cell database
menu or click on button
52
Cigale batch
Roamers detection
Cigale GSM (4/7)
It consists of at least 6 columns:
BSC: corresponds to the name of the BSC that the cell is attached to ;
BTS: corresponds to the cell' s name ;
CI: corresponds to its identification number.
LAC: corresponds to its location area code. This value must be
comprised between 0 and 65535 ;
BSIC: corresponds to the cell' s BSIC. This value must be comprised
between 0 and 63
BCCH: corresponds to the cell' s BCCH. This value must be comprised
between 0 and 1023.
53
Cigale batch
Roamers detection
Cigale GSM (5/7)
Example:
BSC BTS CI LAC BSIC BCCH
BSC1 Cell 1 60019 18 0 2

BSC1 Cell 2 60020 18 9 15
BSC1 Cell 3 60021 18 9 21
BSC1 Cell 4 51346 18 13 3
BSC1 Cell 5 21157 18 3 6
BSC1 Cell 6 21158 18 13 23
BSC1 Cell 7 21159 18 2 25
BSC2 Cell 8 51071 18 2 21

BSC2 Cell 9 51072 18 12 17
BSC2 Cell 10 51073 18 12 29
BSC2 Cell 11 51021 18 1 10
BSC2 Cell 12 51022 18 4 8
BSC2 Cell 13 51023 18 3 18
BSC2 Cell 14 51040 18 0 1
54 BSC2 Cell 15 51051 18 1 7
Cigale batch
Roamers detection
Cigale GSM (6/7)
Set parameters
Open Options / Set parameters menu
A configuration window appears:
MCC information
HO Ping Pong duration limit
Statistics editing directory
55
Cigale batch
Roamers detection
Cigale GSM (7/7)
Set parameters
Open Statistics menu
A configuration window appears:
Connexions (XL3)
Loss of roamers
Two Mandatory options for

roaming module (if you have
56 in the same capture file A&MAP
frames).
Cigale batch
Roamers detection
Cigale GSM
Nature of results Cigale Roaming (1/8)
Cigale Roaming module is a complementary Astellia software to Cigale

GSM.
The Roaming module is dedicated to the analysis of roaming activity

from A (and MAP) interface signalling
It provides accurate and important information on roamers capture,

traffic, loss and recovery.
57
Cigale batch
Roamers detection
Cigale GSM
Cigale Roaming configuration
58
Cigale batch
Roamers detection
Cigale GSM
A: The file to process is automatically selected by GSM Roaming

when using cigale Batch software
B: Select a directory for the result files, by default, its the same
directory as XL3 input file
C: The HPLMN is set automatically to your MCC-MNC network code

if Automatic is checked
D: Select a name for the area (AREA) and choose an unique area
identifier (ID) between 1 and 255 (to differentiate the probes during
59 QRM agregation).
Cigale batch
Roamers detection
Cigale GSM
E: Options
1) Trace with IMEI : When selected, Cigale Roaming will try to associate the
procedures carrying an IMEI with the activities of the IMSI and TMSI
2) To generate .ROM and .RLS files
3) to generate .OFO, XLI and .XRC result text files
4) to generate .TRF file
5) to generate .QRM result database file. This is the input to Roaming View
module.
6) Loss of roamers: generate Loss of roamers indicators and .RCL file

60
F: It can be used to configure MySQL database output
Cigale batch
Roamers detection
Cigale GSM
Text files explanation:
RLS : statistics about roamers (with IMSI).
ROM : detailed information (time, cells, BSC, states, causes, IMSI, TMSI, IMEI
) of all the transition due to roamers.
OFO, XLI : roamers location update by network and/or by ci.
TRF : roamers traffic (VOC, VTC, SMS, IMSI attach&detach) by network and/or
by ci.
XRC : roamers categories (new, back, retrieved, collected & transit) by network
and/or by ci.
61
RCL: roamers loss and recovery informations by network and/or by ci.
Cigale batch
Roamers detection
Cigale GSM
MySQL Database test
ok Nok
62
Cigale batch
Roamers detection
Cigale GSM
Processing in command line
Input / Output
- i : "Full XL3 FileName To process"
- o : "Complete Folder for Statistics Output" (XL3 input file, if not
specified)
- d : "Program directory
Parameters
-h : "MCCMNC"
-a : "NameofMyArea" (Replace NameofMyArea by the name you want.
Default is "MyArea")
63 -g : "n" for area differentiation. (0<n<256)
Cigale batch
Roamers detection
Cigale GSM
This command line can be included into a batch file that allows
automatic processing
Example:
"C:\Program Files\Astellia\CigaleRoaming\CigaleRoaming.exe" -i
"C:\traces\Orange.xl3" -a "MSC1" -h "62402" -o "C:\traces\resultats_Orange\" -d
"C:\Program Files\Astellia\CigaleRoaming\"
C:\traces\Orange.xl3 is the input file

MSC1 is the name of the monitored area
624 and 02 are respectively the MCC and MNC of the Home PLMN
C:\traces\resultats_Orange\ is the output folder
C:\Program Files\Astellia\CigaleRoaming\ is the software directory
64
* $
65
Data representation User defined area
* $ Location updates Database handling
traffic Cells description file
User configuration
Open qrm database
66
Data representation (1/4) User defined area
User configuration
Data representation
67
User configuration
Graphs
Ex: Cells top 20 Location Update Requests (by imsi)
68
User configuration
Reports
69
User configuration
Roaming View provides two different levels.

Top level and detailed level are linked according to the following table.
70
* $ Location updates (1/21) Database handling
User configuration
At each location update, the user transmits the old location area
identification stored in its SIM card
MCC MNC LAC
Location Area Identification ( LAI )
MS BSS MSC/VLR

Infos: [BSSMAP COMPLETE L3 INFO
LU type: Infos:
- Normal - Cell Id
- Periodic
- IMSI Attach
MS identity: SCCP CONNECTION CONFIRM
71 - IMSI ou TMSI
LAI
User configuration
This allows to obtain the following about each roamer :

Home subscriber network
Success or failure of the location update with the associated cause
Cell/BSC/LAC/Area/UserArea where the location update is performed
Previously visited country
Previously visited network
Old LAC; in case of failure during the previous LU, MS provides a non valid
72 value (0, 65534, 65535)
User configuration
Different categories of roamers
Retrieved roamers : [ HPLMN(IMSI user) observed HPLMN ] And

[ MCC(observed HPLMN) = MCC(Old LAC Lureq) ] And [ MNC(observed
HPLMN) MNC(Old LAC) ]
Every roamer whose previous location update was performed in a competitive

network
Collected roamers : [ HPLMN(IMSI user) observed

HPLMN ] And [ MCC(observed HPLMN) MCC(Old LAC Lureq) ]
Every roamer whose previous location update was performed abroad
73
User configuration
Cells welcoming the highest number of Location Update requests of

roamers coming from abroad (Collected)
74
User configuration
Same information available in a table
75
User configuration
Cells welcoming the highest number of Location Update requests of

roamers coming from competitive network (Retrieved)
76
User configuration
New Roamers : New Roamers = union of Collected roamers and

Retrieved roamers
Every roamer whose previous location update was performed abroad or in a

competitive network
Roamers in Transit : [ HPLMN(IMSI user) observed HPLMN ] And

[ MCC(observed HPLMN) = MCC(Old LAC Lureq) ] And [ MNC(observed
HPLMN) = MNC(Old LAC Lureq) ]
Every roamer whose previous location update was performed in the monitored
network
77
User configuration
Transit cells representation (where the previous roamers Location

Update was performed in other LAC)
78
User configuration

6
2
Monitored Network
Foreign Network
3
5 1
1 Foreign subscriber
2 Arrival on Observed network
4 3 Collected (New)
4 Loss of Radio Link
79
Competitors Network 5 Retrieved (New)
6 Transit
User configuration
Back subscribers : [ HPLMM(IMSI user) = observed HPLMN ]

Subscribers from the monitored network
Two ways of use:
Back : observed HPLMN PLMN(Old LAC Lureq).

Used to identify from which other network (abroad or a competitive
network) and on which cells these subscribers come back to their HPLMN
Back(iol) : observed HPLMN = PLMN(Old LAC Lureq) and Old LAC is

invalid.
Used to identify cells around which there is loss of coverage.
80
User configuration
Monitored Network Back(iol)
1 Home Subscriber
2
4 2 Loss of Radio Link
3 Failed LU Old LAC = iol
4 Back(iol)
81
User configuration
From which network subscribers come back to their HPLMN
82
User configuration
NEW
COLLECTED RETRIEVED
ALL
TRANSIT
83 Results BACK
IOL
per IMSI
User configuration
In the results, for each roamers category, a difference is made between:
IMSI : the number of roamers (number of different IMSI)

E.g: Imsi Coll(Req) : number of different Collected roamers having
performed (at least) a LU.
Total : the total number of location updating request performed by these

roamers
E.g: Tot Coll(Req) : number of LU performed by Collected roamers
A roamer performing 100 location updates on the same geographical area

will be counted :
- 1 time for IMSI results
84
- 100 times for Total results
User configuration
Networks top 20 Location Update Requests (by imsi)
85
User configuration
Networks top 20 Location Update Requests (Total)
86
User configuration
Same result available in tables
87
User configuration
Consequences for counting by identity
A single roamer can belong to several categories.

New <= Collected + Retrieved
All <= New + Transit
Geographical and temporal agregation (sum of IMSI values)
Causes distribution by location update reject causes
88
User configuration
For each roamers category (All, New, Collected, Retrieved, Transit, Back),
the following information is provided :
First, in terms of number of roamers (different IMSI)
Number of different roamers (different IMSI) belonging to this category
Number of different roamers (different IMSI) belonging to this category and

whose location updating request contained a non valid Old LAC value
Number of different roamers (different IMSI) belonging to this category and

whose location updating request was accepted
Percentage of success during the location update procedure of these roamers
Percentage of failures due to PLMN Not Allowed reject cause
89 Percentage of failures due to other reject causes or radio failures

User configuration
Then, in terms of number of location updates
Number of location updating requests of roamers belonging to this category
Number of location updating requests of roamers belonging to this category,

which contained a non valid Old LAC value
Number of location updating accept of roamers belonging to this category
Percentage of success of the location update procedures
Percentage of failures due to PLMN Not Allowed reject cause
90 Percentage of failures due to other reject causes or radio failures

User configuration
For New, Collected, Retrieved and Transit categories, the following

information is provided (by IMSI and Total) :
Number of Requests and Accepts
Distribution of the Rejects according to the reject causes *:
NF : Network Failure,
PLMNNA : PLMN not allowed,
LANA : Location Area not Allowed
IUH : IMSI unknown in HLR,
IUV : IMSI unknown in VLR,
IMI : Invalid Mandatory Information,
IMEINA : IMEI not Accepted,
RNAILA : Roaming not Allowed in this Location Area,
PEU : Protocol Error unspecified
XX : Other causes (not listed above)
Other failure causes :
ClRq_RImF : radio problems,
91
Pb_xx : all other failure causes
* Detailed explanation is available for each cause in Appendix

User configuration
Top 20 networks reject causes (by imsi)
92
User configuration
Same information available in a table
93
Traffic (1/14) Cells description file
User configuration
Roaming traffic is observed through the following procedures :
Normal Calls (voice and data, originating and terminating)

VOC, DOC, VTC, DTC
Emergency calls
E
SMS (Mobile originating and mobile terminating)
SMS O, SMS T
Supplementary services
SS O
IMSI attach
Periodic location updates
94 IMSI detach
User configuration
Information for calls (All Calls, VOC, VTC, E, DOC, DTC) :
Number of different IMSI with activity (Imsi nb)
Number of calls initiated in the selected area (Call Init)
Number of connected calls in transit in the selected area, (Call transit)
Number of connected calls ended in the selected area (Call End)
Traffic (in hours) of calls initiated in the selected area (Call Traff(init) )
Traffic (in hours) of calls in transit in the selected area (Call Traff(tran) )
Traffic (in hours) of all calls in transit in the selected area (EffCall)
95 Percentage of roaming traffic for the selected area (Call%Roam)

User configuration
The 20 networks generating most of the traffic in hours
96
User configuration
The same result is availble on a table
97
User configuration
Difference between Call Traff(init) and Call Traff(tran)
Cell n1 Cell n2
0 2 mn 6 mn
t
Call initiated HO from cell1 End of call
on cell1 to cell 2 on cell 2
Call Traff(init) Call Traff(tran)
Cell 1 6 mn 2 mn
98 Cell 2 0 4 mn
User configuration
Information for calls (all calls, VOC, VTC, E, DOC, DTC) :
Number of calls initiated in the selected area having reached the ringing phase
(Call Ring)
Percentage of calls initiated in the selected area having reached the ringing phase
(Call %Ring)
Number of calls initiated in the selected area having reached the communication
phase (Call Com)
Percentage of calls initiated in the selected area having reached the communication
phase (Call %Com)
99
User configuration
Information for calls (all calls, VOC, VTC, E, DOC, DTC) :
Number of call drops for calls initiated in the selected area (Call Drop Init)
Percentage of call drops for calls initiated in the selected area (Call %Drop Init)
Number of call drops for calls ended in the selected area (Call Drop End)
Percentage of call drops for calls ended in the selected area (Call %Drop End)
Average communication time of calls initiated in the selected area (Call Avg Com)
100
User configuration
These indicators are presented on the following table:
101
User configuration
Information for SMS (Originating and Terminating) :
Number of mobile originating and terminating SMS respectively sent and received in
the selected area (SMS O or SMS T)
Total connection time used for sending and receiving short messages in the selected
area (SMS O Time and SMS T Time)
Number of mobile originating and terminating SMS respectively sent and received
successfully in the selected area (SMS O Eff and SMS T Eff )
Percentage of short messages sent and received successfully in the selected area
(SMS O %Eff and SMS T %Eff)
102
User configuration
Information for SS :
Number of initiated SS (SS)
Number of SS sent successfully (SS Eff)
Percentage of SS sent successfully (SS %Eff)
103
User configuration
104
User configuration
Information for IMSI Attach :
Number of initiated IMSI Attach procedure (IMSI Att)
Number of successful IMSI Attach procedure (IMSI Att Eff)
Percentage of successful IMSI Attach procedure (IMSI Att %Eff)
105
User configuration
Information for periodic location update :
Number of initiated periodic location update procedure (LUpu)
Number of successful periodic location update procedure (LUpu Eff)
Percentage of successful periodic location update procedure (LUpu %Eff)
Information for IMSI detach :
Number of IMSI detach (IMSI Det)

106
User configuration
107
Traffic Cells description file
User configuration (1/3)
Roaming View gives the possibility to save and load user parameters in
order to configure the data view.
Parameters defined in a .cfg are:

List and order of displayed columns for first and detail level.
Sorting criteria
108
Example: here is a view without any .cfg file loaded
109
We have the same view with BackIol.cfg file loaded
110
Data representation User defined area (1/2)
User configuration
Two User levels are available:

User(cells) : used to create groups of cells:
e.g.: airport, boundaries
User(networks): used to create groups of networks:
e.g.: partners, networks of a same group
111
Data representation User defined area (2/2)
User configuration
User(cells) and User(networks) are saved in text files whose content

can be easily modified
e.g: User (cells)
' ( ) **+
' ( ,-./-
112
+-- +00
* $ Location updates Database handling (1/4)
User configuration
This window allows the selection of Roaming View

Database :
to open a database for the analysis
to close a database and remove it for the analysis

to agregate qrm databases
113
User configuration
Database agregation
Roaming databases can be merged in one database in order to
merge data from different geographical area and/or several time
periods.
This can be done manually or with :
Roaming aggregator
Roaming aggregator is installed in Roaming view installation
folder
It works in command line
114
User configuration
Input / Output:
-A : Complete path and name of MS ACCESS 2000 application
-R : Complete path and name of roaming view application
-D : Complete path of Roaming View Database (*.qrm files)
-F : Complete path and name of output database
115
User configuration
Example:
C:\Program Files\Astellia\Roaming
View\AGGREGATOR\ROAMING_AGGREGATOR.exe -A
C:\Program Files\Microsoft Office\Office\MSACCESS.EXE -R
C:\Program Files\Astellia\Roaming View\RoamingView.mde -
DC:\database_in -F C:\database_out\week_cameroon.qrm
Notes:
To work properly, Roaming Aggregator needs, in the output directory, a
free space between a half and a third part of the sum of the roaming
database size to aggregate.
116
Traffic Cells description file (1/2)
User configuration
A cell database file can be used (same file than Cigale GSM). This file
can be loaded by three ways:
Manually
Automatically: file called celcig.dat and located in the Roaming View
directory
In command line or Roaming View shortcut
It consists of at least 6 columns:

BSC: corresponds to the name of the BSC that the cell is attached to ;
BTS: corresponds to the cell' s name ;
CI: corresponds to its identification number.
LAC: corresponds to its location area code. This value must be comprised
between 0 and 65535 ;
BSIC: corresponds to the cell' s BSIC. This value must be comprised between 0
and 63
BCCH: corresponds to the cell' s BCCH. This value must be comprised between
117 0 and 1023.
Traffic Cells description file (2/2)
User configuration
Example:
BSC BTS CI LAC BSIC BCCH
BSC1 Cell 1 60019 18 0 2

BSC1 Cell 2 60020 18 9 15
BSC1 Cell 3 60021 18 9 21
BSC1 Cell 4 51346 18 13 3
BSC1 Cell 5 21157 18 3 6
BSC1 Cell 6 21158 18 13 23
BSC1 Cell 7 21159 18 2 25
BSC2 Cell 8 51071 18 2 21

BSC2 Cell 9 51072 18 12 17
BSC2 Cell 10 51073 18 12 29
BSC2 Cell 11 51021 18 1 10
BSC2 Cell 12 51022 18 4 8
BSC2 Cell 13 51023 18 3 18
BSC2 Cell 14 51040 18 0 1
118 BSC2 Cell 15 51051 18 1 7
119
Overview (1/2) Identities level
Database Detailed level
Interface Case study
120
Overview (2/2) Identities level
Used for troubleshooting
Activity Analysis allows the user to investigate more deeply a failure by

navigating in the statistics and the detailed activity trace.
Two levels of results are available:

Identities: summary of the activity of each roamer
Detailed activity: each activity of each roamer
The link between these two levels is automatic

Its possible to get all the detailed activity for one identity from the "Identities
" window
121
Overview Identities level
Database (1/4) Detailed level
Database
Connection to mysql server
122
Description
Hostname is the name of the database server. Localhost means that

the database server is running on the local hard drive.
Port is the database server port number. Default port is 3306.
Login indicates a database user name to use for connecting (default

login/password: cigale/astellia) .
123
Click on Database menu to open a database
124
These databases are generated by several Cigale engines:
GSM (A Interface)
ISUP (ISUP Interface)
Roaming (A and Map Interfaces)
Trace (A Interface)
125
Interface (1/7) Case study
Windows options
Go to roamers activity
Go to roamers identity
Quit
Connect/Disconnect to the server
Open/Close a database
126
Close the active window
Navigation window
Roamers identities
Roamers activity
127
Preset window
Store a defined context (database type, current view, active filters,

columns and their respective size)
Load it on the current database
The tool bar allows to add a group or a subgroup, delete a

preset or group, reload a preset, import or export a preset.
Identities Preset
128 Activity Preset

Preset creation
Create a group ; right click on the window and select save as

preset
129
Filtering and sorting tools
Close the current window
Go to the top / bottom of the view
Zoom In / Out
Increasing order / decreasing order / No order
Apply a filter equal, different, lower than the active cell
Display the number of different elements in the active column
130 Cancel the filter of the active column / all filters / the last filter
Export to Excel
Filters Display the filter palette
Advanced filter (you can use

generic character as *)
Filter with several value button
Find first
Go to roamers activity
131
Popup menus
A popup menu is displayed by right clicking on the table
Identity Activity
132
Overview Identities level (1/2)
Identities level
It corresponds to RLS Cigale roaming output
It provides, for each detected roamer, a summary

of activity through a list of KPIs
133
Overview Identities level (2/2)
134
Database Detailed level (1/2)
Detailed level
Detailed activity of each roamer:
Each line corresponds to a SCCP connection in one cell
For each activity, the available information are:

start and end time
start and end events *
end cause *
previous state *
durations (connection, ringing, call)
identities (TMSI, IMSI, IMEI)
destination numbers
135
* an example of MOC procedure is available in appendix

Database Detailed level (2/2)
136
Case study
From Roaming View to Roaming Analysis
137
Interface Case study (1/10)
Location Update rejected Cause investigation
IMSI from two networks (Orange

Carabes and Vodafone Panafon) are
totally rejected with cause NF (Network
Failure)
138
Location Update rejected Detail information for NF cause

Filter on the rejected cause (NF)
Most of the time this cause is related to accessing problem between the VLR and the
roamers HLR: wrong declaration in the VLR or lack of configuration for HLR in your
139 VLR or problem to establish a signalling link toward the HLR.
Location Update rejected Cause investigation
Some IMSI from TIMEcel network are

rejected with cause IUH (IMSI Unknown
in HLR)
140
Location Update rejected Detail information for IUH cause

generally this cause was sent due to a bad routing from the VLR toward a roamerss
HLR (well see in the table below which IMSI are involved):
In this example, we take one IMSI: 502176900166545. If we split IMSI according to

141 the standardization: 502 MCC, 17 MNC, 69(0) HLR address and
(0)0166545 MSIN
The zero in bracket can be used in the HLR address or in the MSIN
Location Update rejected Detail information for IUH cause
We see in the table below that subscribers belonging to the same HLR (69)
were accepted on the monitored network.
It can result from new TIMEcel subscribers not yet declared in the
considered HLR.
142
Traffic issue low ringing and low connection rate
Mobilink network (PAK 410-01) has low

143
ringing (62%) and also a low connection
rate (36%)
Traffic issue low ringing and low connection rate
UN (Unassigned Number) means that the MSC reject the call. Normally, with UN rejected cause,
there is a voice message which inform the subscriber he has dialled a wrong number. If no explicit
message inform the subscriber it can be interesting in changing the UN cause by INF (Invalid
Number Format) cause. INF avoids another attempt by informing the roamer the wrong number
he has entered.
144
NUR (No User Responding) means that the MSC release the call due to a timer expiry (14s in this
case). This timer can be if necessary increased.
Traffic Supplementary Services
To have detailed information for a Roamer

from TIMEcel having such Supplementary
Service:
145
Traffic Supplementary Services
Roamer is using a Supplementary Service to know his credit with the service code
146 (122). He doesnt use traffic channel but only SDCCH resources for the request and
the response.
Traffic Other Supplementary Services

Directly detected with roaming analysis:
Roamer is using a USSD call-back mechanism. He dials first a USSD string which
contains the call back service code (*100*), received a message request is being
processed and then he received an incoming call (handover during the call).
This USSD call back service is provided by the Home network of these roamers; it
allows them to reduce the cost of their calls when roaming, by transforming an
147
outgoing call into an incoming call, which is cheaper when roaming.
. &
148
Overview (1/2)
. Loss & recovery detection
Main indicators
Examples
Overview
When a roamer has lost the radio coverage, the mobile station will
initiate a location update procedure to a competitive network.
As soon as a location update request is sent from the new VLR to

the roamers HLR, a MAP_CANCEL_LOCATION message from the
roamers HLR will be sent in order to delete the subscriber record
from the old VLR.
149
Overview (2/2)
Main indicators
Examples
A Interface MAP Interface

Old Network
BSC
VLR 4 MA
P_C
an cel_L
ocat
ion
n ROAMER
t i catio
n
A u the HLR
P _ ca tion
A o
2M a te_L
BSC _ U pd
AP
VLR 3M
1 Location Updating Rq
New Network
150
Overview
. Loss & recovery detection (1/3)
Main indicators
Examples
Loss detection
When a Cancel Location message is identified, the software tries to link it to a
previously monitored activity on the A interface.
If successful, the Cancel Location is considered as a loss. A time value is then

associated to this loss ( TL), which is the elapsed time between the last monitored
activity on the A interface and the capture of the Cancel Location message.
Max ETL (300s by default) is a threshold which allows us to be more sure of the
loss area.
Using MaxETL threshold to classify the loss, TL is compared to MaxETL. If TL

< MaxETL, the software is able to locate more precisely the loss area.
A roamer had many activities on cell1 then moved after 15 minutes on cell2 and on
cell3 after 30 minutes (same VLR area). If a Cancel Location message is received,
the loss will be linked to cell1 but the subscriber has maybe lost the radio coverage
on cell2 or cell3.
151
Overview
Main indicators
Examples
Recovery detection
When a Cancel Location message is identified, the software tries to link it to

the following monitored activity on the A interface.
If successful, this new activity is considered as a recovery. A time value is

then associated to this recovery ( TR), which is the elapsed time between
the capture of the Cancel Location message and the first following
monitored activity on the A interface.
Max ETR (300s by default) is a threshold which allows us to qualify the best
recovery cells. TR is compared to MaxETR.
If TR < MaxETR, the areas, where the first following monitored activity on
the A interface happened, will be considered as the best recovery areas.
152
Overview
Main indicators
Examples
Activity
LOSS
MSC
L
MAP_Cancel_Location ROAMER
HLR
R
Activity
RECOVERY
153 Time
Overview
Main indicators
Examples
Main indicators
Tot Loss woLUn: Number of losses without a location updating

request as last message
Imsi LossETL woLUn: Number of different IMSIs that have been lost
without LU as last message and with elapsed time MaxETL
Tot Rec: Total Number of recoveries
Imsi RecETR: Number of different IMSI concerned by the recoveries

with ETR < MaxETR (Relevance of Tot RecETR)
154
Overview
Main indicators
Examples (1/5)
Top 20 Cells having the higher loss of roamers
155
Overview
Main indicators
Examples (2/5)
Same results in a table
156
Overview
Main indicators
Examples (3/5)
Top 20 Cells having the higher loss of roamers ETL
157
Overview
Main indicators
Examples (4/5)
Top 20 Cells having the higher loss of roamers ETL without Location
Update as last activity
158
Overview
Main indicators
Examples (5/5)
Top 20 cells recovering the more of roamers (graph and table)
159
Location update (1/3)
LUrej causes
'' , Outgoing calls
Identities level
Detailed level
MS BSS MSC/VLR HLR

RR CHANNEL REQUEST
RR IMMEDIATE ASSIGNMENT

[BSSMAP COMPLETE L3 INFO
T(conn est) start
MAP_SEND_AUTHENTICATION_INFO
SCCP CONNECTION CONFIRM

T(conn est) stop
MAP_SEND_AUTHENTICATION_INFO ACK
MM AUTHENTICATION REQUEST
T3260 Start
MM AUTHENTICATION RESPONSE
T3260 Stop
160
LUrej causes
'' , Outgoing calls
Identities level
Detailed level
MS BSS MSC/VLR HLR
MAP_UPDATE_LOCATION
MAP_INSERT_SUBSCRIBER_DATA
MAP_INSERT_SUBSCRIBER_DATA ACK
BSSMAP CIPHER MODE MAP_UPDATE_LOCATION ACK

RR CIPHERING MODE COMMAND
COMMAND
RR CIPHERING MODE
COMPLETE
BSSMAP CIPHER MODE
COMPLETE
161
LUrej causes
'' , Outgoing calls
Identities level
Detailed level
MS BSS MSC/VLR
MM TMSI-REALLOCATION COMMAND
T3250 Start
MM TMSI-REALLOCATION COMPLETE
T3250 Stop
MM LOCATION UPDATING ACCEPT
BSSMAP CLEAR COMMAND

RF CHANNEL RELEASE
BSSMAP CLEAR COMPLETE
SCCP_RELEASED
T(rel) start
SCCP_RELEASE COMPLETE
T(rel) stop
162
Location update
LUrej causes (1/2)
'' , Outgoing calls
Identities level
Detailed level
Lurj_NF : Location Updating Reject message with cause Network Failure

This cause is sent to the mobile station if the MSC cannot service the generated request
because of PLMN failures, e.g. problems in MAP.
Lurj_PLMNNA : Location Updating Reject message with cause PLMN Not Allowed
This cause is sent to the mobile station if it requests location updating in a PLMN where the
user, by subscription or due to operator determined barring is not allowed to operate.
Lurj_LANA : Location Updating Reject message with cause Location Area Not Allowed
This cause is sent to the mobile station if it requests location updating in a location area where
the mobile, by subscription, is not allowed to operate.
Lurj_IUH : Location Updating Reject message with cause IMSI Unknown in HLR
This cause is sent to the mobile station if the mobile station is not known (registered) in the
HLR.
Lurj_IUV : Location Updating Reject message with cause IMSI Unknown in VLR
This cause is sent to the mobile station when the given IMSI is not known at the VLR.
Lurj_IMI : Location Updating Reject message with cause Invalid Mandatory Information
This cause indicates that the equipment sending this cause has received a message with a
163 non-semantical mandatory information element error
Location update
LUrej causes (2/2)
'' , Outgoing calls
Identities level
Detailed level
Lurj_IMEINA : Location Updating Reject message with cause IMEI Not Accepted
This cause is sent to the mobile station because the network does not accept location update
procedure establishment using an IMEI.
Lurj_RNAILA : Location Updating Reject message, cause Roaming Not Allowed In this Location Area
This cause is sent to a mobile station which requests location updating in a location area of a
PLMN which do not offer roaming to that user in that location area, by subscription.
Lurj_PEU : Location Updating Reject message with cause Protocol Error Unspecified
This cause is used to report a protocol error event only when no other cause in the protocol
error class applies.
Lurj_xx : Location Updating Reject message with causes other than the previous ones
It can include (but not limited to) causes such as Congestion, or causes related to invalid
message or content.
ClRq_RImF : Clear Request message with cause Radio Interface Failure and Radio Interface
Message Failure
It covers all radio failures detected by the BSS during the location update procedure.
Pb_xx : covers all other failure (problem) message and cause than the previous ones
164 this can include (but not limited to) Clear Command, SCCP Connection Refused, direct SCCP
Released messages.
Location update
LUrej causes
'' , Outgoing calls (1/4)
Identities level
Detailed level
Event State
Protocol Message
BSS MSC
CMSRQ
OC_CMS_REQ
Connection Request [ Complete Layer 3 Information [ CM Service Request ] ]
CC
Connection Confirm
AUTRQ
OC_AUT_REQ_1
Data Form 1 [ Authentication Request ]
AUTRP
OC_AUT_REP
Data Form 1 [ Authentication Response ]
CICMD
OC_CIM_CMD
Data Form 1 [ Cipher Mode Command ]
165
CICMP OC_CIM_CMP
Data Form 1 [ Cipher Mode Complete ]
Location update
LUrej causes
Identities level
Detailed level
Event State
Protocol Message
BSS MSC
SETUP
OC_SETUP
Data Form 1 [Setup]
CPROC
OC_PROC
Data Form 1 [ Call Proceeding ]
ASREQ
Data Form 1 [ Assignment Request ] OC_ASS_REQ_1
ASCMP
OC_ASS_CMP
Data Form 1 [ Assignment Complete ]
PROG
OC_SONN
Data Form 1 [ Progress ]
166
ALERT
OC_SONN
Data Form 1 [ Alerting ]
Location update
LUrej causes
Identities level
Detailed level
Event State
Protocol Message
BSS
MSC
CON
OC_CON
Data Form 1 [ Connect ]
CONACK
OC_COMM
Data Form 1 [ Connect Acknowledge ]
Conversation phase
DISC
OC_FIN
Data Form 1 [ Disconnect ]
167
Location update
LUrej causes
Identities level
Detailed level
Event State
Protocol Message
BSS
MSC
REL
OC_FIN
Data Form 1 [ Release ]
RELCMP
Data Form 1 [ Release Complete ]
CLCMD
Data Form 1 [ Clear Command ]
CLCMP
Data Form 1 [ Clear Complete ]
RLSD
Released
RLC
168 OC_FIN
Release Complete
Location update
LUrej causes
'' , Outgoing calls
Identities level (1/3)
Detailed level
!
% ( !
$ ( )
"$
"# '
!"# $ % &
!
!
169
Location update
LUrej causes
'' , Outgoing calls
Detailed level
"$& ,
"! + * *
&! * *
"! * * * *
"! * *
"! * * &
)! # ' ( * * * ! !" %
&! # ' ( * * * * !" %
" *
& *
" * * *
" *
" * &
) ' ( * !" %
& ' ( * * * !" %
$" $ + * *
$" $ + * *
$" $ + * *
170 $" $ *
$" $ *
$" $ *
Location update
LUrej causes
'' , Outgoing calls
Detailed level
$$ + * * !
$$ + * * !
$$ + * * !
+ * * !
* "$ !
* "# ' !
* !
!
# *
!
# *
171
Location update
LUrej causes
'' , Outgoing calls
Identities level
Detailed level (1/3)
!
" %
$
$
# '
#
&
0 * * &
+ ' * * 0
-$ * *6 " %
* *
$
# 0 & 0
&
, 4 * 5 - * .&/0 0 1
222
222221 *
+ * * " %
! ! - * .&/0 0 1
222222221 *
172 &3 !
! ! - * .&/0 0 1
222222221 *
&3 !
Location update
LUrej causes
'' , Outgoing calls
Identities level
"$ !" %
"$
"# '
" * * % * !" * % &
! ! 8 '0 !
" 26 26 /6 * ! 8 '%
! " !
! " )
!
+ ! *
0 * * *
! * * !
! * * * *
/ "$ <
. ! &
* * " < % * ! -
* $ * " ! $ % 3+ '= "3 + '= %
&
" %- 0 9:; ! 0 9&;
!
173
& *
- ) 6 ! ' + 7 ',0
+ ', 8 ' *&
Location update
LUrej causes
'' , Outgoing calls
Identities level
+ * * - 8 8 *
* * * *& * *0
/ * * *
+ * * * * *
26 3 * * >
"3 ?
6 ?
6 3? %
! 26 3 5 * * >
"3 ?
6 ?
6 3? %
# ' * ! *
# ' * * !
174
''
Tel: +33 (0) 2 99 04 80 66
Email: support@astellia.com
175



www.astellia.com
Cigale ISUP
177
Cigale ISUP
Overview
ISUP messages
ISUP automat
Benefits
Process and viewer
Engine description
ISUP configuration
178
ISUP Analysis
Overview
Database
Transitions
Setup efficiency
Traffic Report
Resources
CDR
179 Case study

Overview (1/2) Process and viewer
ISUP messages Engine description
ISUP automat ISUP configuration
Benefits
Overview
180
Overview (2/2) Process and viewer
Benefits
ISUP Interface available in all networks
Between MSC and PSTN ( public network in the country)

Inter MSC (within the GSM network)
Between MSC and GW MSC ( international Gateway)
Used to find/solve interconnection issues
181
Overview Process and viewer
ISUP messages (1/3) Engine description
Benefits
ISUP messages (with an example)

Communication establishment Communication release
MSC PSTN MSC PSTN
IAM
REL
ringing ACM Called

party
Alerted
RLC
ANM
182 Conversation phase

Benefits
Acronym Signification
IAM Initial Address Message (contain called
number, identity of the calling line, ) :
reservation of a CIC (Circuit Identity Code)
ACM Address Complete Message : called party
alerted
ANM ANswer Message : called party hang up
CON CONnect : direct connection towards vocal
service
REL RELease : connection release
183
RLC ReLease Complete : acknowledgment of the
release
Benefits
Call flow example

SS7 SS7
Network network
A B C
MS IAM
IAM
MS
ACM Ringing
ACM
ANM
Connect
Ringing ANM
Conversation phase
184
ISUP automat (1/2) ISUP configuration
Benefits
ISUP Automat description (part 1)
185
ISUP automat (2/2) ISUP configuration
Benefits
ISUP Automat description (part 2)
186
Benefits (1/2)
Benefits :
interconnection troubleshooting
Congestion detection
Network or service access failure detection
White communications (looped PCM, CIC problems)
Customer complaints
187
Detailed CIC ISUP Analysis
Benefits (2/2)
Analysis of problems detected on other interfaces (e.g. on GSM A)
Research on calling/called numbers
Procedure timing analysis
Detection of releases caused by timing problems

188
Overview Process and viewer (1/3)
Benefits
Process and viewer

From ISUP links to troubleshooters :
Protocol Analyser for sporadic use OCEAN probe for frequent use:
Up to 20 PCM (620TS)
Continuous file capture
Automatic file processing
(can be used with MANTA
for signalling grooming)
Captured files:
binary frames
Processing Engine
results data base Results ISUP Analysis
generation from a Data
189 Base
complete file or a
period in a file
Benefits
A top-down troubleshooting tool
Statistics :
Traffic Setup efficiency CIC activity Releases
Sorting,
filtering,
searching, Activity report :

CDRs
190
Benefits
Results display
Access to other
Powerful results
searching,
filtering
and sorting
Result display
(Current window = CDRs)
191
ISUP messages Engine description (1/3)
Benefits
Engine description
User interface: File to process
Analysers Configuration
available menu (next pages)
Licence and
version information
Open/reset
ISUP Log
192
Benefits
configuration menu:
Output mysql database Processing time range
creation options (by default possibility
everything is selected)
193
Benefits
configuration menu:
Mysql
server
test
Country information
If selected, text files generated (same

information than Mysql database)
194 European or American standard

ISUP automat ISUP configuration (1/1)
Benefits
ISUP configuration
PhoneNumbers.txt file makes the correlation between numbers
(originating and destination) and countries name.
Extract of the configuration file:
[Service (FULL_NUM)]
Service 221=221
Service 224=224
Service 577=577
[Emergency (FULL_NUM)]
Pompier = 18
Police = 17
Urgence 112 = 112
[Operator (PREFIX_NUM)]
SFR = +33(0)603??????
SFR = +33(0)609??????
Orange = +33(0)607??????
195 Orange = +33(0)608??????
Bouygues Telecom = +33(0)698??????

Bouygues Telecom = +33(0)699??????
196
Overview Setup efficiency
Database Traffic Report
Interface description Resources
Transitions CDR
ISUP Analysis
Overview
Database
Transitions
Setup efficiency
Traffic Report
Resources
CDR
197
Overview (1/2) Setup efficiency
Transitions CDR
Overview
ISUP Analysis allows the user to investigate a failure by navigating from the transitions
198 view until the Activity report view.
Overview (2/2) Setup efficiency
Transitions CDR
Where : On each ocean probe and user PC

When : After Cigale ISUP process - can be used also next to
Cigale Gb and Gn (GPRS), Cigale Iu and Iub (UMTS), Cigale
GSM, Cigale Roaming and Cigale Trace
Why : To create a database and visualise results thank to a
graphical user interface that helps investigation
How : created during the Cigale ISUP engine process
Cigale ISUP ISUP Analysis
199
Database (1/2) Traffic Report
Transitions CDR
Database
Connection to MySQL server
The server can be the local

machine (Localhost) or a distant
connected server.
Default port is 3306
Two logins :
Cigale : all rights (pwd : astellia)
Analysis : read only (no pwd)
200
Database (2/2) Traffic Report
Transitions CDR
MySQL database
MySQL database are

generated by the Cigale
engines.
- GSM (A interface)
- Trace (A interface)
- ISUP (ISUP interface)
- Roaming (A and MAP interfaces)
- GPRS (Gb or Gn interfaces)
- UMTS (Iu or Iub interfaces)
201
Interface description (1/8) Resources
Transitions CDR
Configuration menus
Windows options
Table selection
Quit View selection

Connect/Disconnect to the server
Open/Close a database
Close the active window
202
Transitions CDR
Navigation windows
Counter viewer
Call Data Record
List of causes Viewer
List of events Traffic Viewer
Setup efficiency
List of States Viewer
Resources Viewer
203
Transitions table Activity report tables

Transitions CDR
Preset window
Store a defined context (database type, current view, active filters, columns and their
respective size)
Load it on the current database
The tool bar allows to add a group or a subgroup,

delete a preset or group, reload a preset, import or
export a preset.
Preset icons represent the type of view.
204
Transitions CDR
Preset creation
Create a group ; right click in the preset window
Preset Added
3 Filter selection
2
Add group
205
1
Group added
Transitions CDR
Filtering and sorting tools

The tool bar contents vary depending on the selected view.
Close the current window
Go to the top / bottom of the view
Zoom In / Out
Increasing order / decreasing order / No order
Apply a filter equal, different, lower than the active cell
Display the number of different elements in the active column
206 Cancel the filter of the active column / all filters / the last filter
Transitions CDR
Export to Excel
Go to Call Data Record viewer

Go to Traffic viewer
Go to Setup efficiency viewer
Go to Resources viewer
Advanced filter (you can

use generic character as *)
Filter with several value button

(only for CDR and Setup efficiency views)
207 Find first

Transitions CDR
Filters Display the filter palette
Filter palette Detail of the active filters in

the current view
(only for CDR and Setup efficiency views)
The filter can be saved and loaded.
208
Transitions CDR
Popup menus
A popup menu is displayed by right clicking on the table
Counters, Traffic
Report and Resources
views
CDR and Setup
209 efficiency views
Transitions (1/4) CDR
Transitions
For each OPC/DPC link
Distribution (counters and percentage) of the different release

cases:
Communication state before the release occurs
ISUP message causing the release
Release message cause
Release originating point (OPC /DPC)
210 => Troubleshooting of abnormal releases

Transitions Release statistics view
Current use of the transition view:

Interconnection issue with a equipment/country/network:
211
by filtering on release cause and going to the CDR viewer in order to check the
duration, destination number
Go to Activity Report
This option enables to display all the CDR corresponding to the release
cause for this OPC-DPC direction.
Counters
Activity Report ( CDR viewer)
212
Go to Traffic Report, to Setup Efficiency, and to Resources

These 3 options enable to display the corresponding view for the OPC-DPC
direction where youve the release cause.
Counters
Example for Resources
213
Overview Setup efficiency (1/2)
Transitions CDR
Setup Efficiency
For each OPC/DPC link
Analysis of the setup progress for each communication :

Connection start (IAM)
Next connection steps (CON, ACM, ANM)
Connection end (REL)
For each step (either successful or not) :

Event counters
Percentage (event counter / IAM counter)
214
=> Troubleshooting of call setup inefficiency
Overview Setup efficiency (2/2)
Transitions CDR
Setup Efficiency view
Current use of the Setup efficiency view:

Calls inefficiency quick detection for one link
215 As Transitions view, you can

go to all other tables (for the
OPC-DPC direction selected)
Database Traffic Report (1/2)
Transitions CDR
Traffic Report
General traffic view for each OPC/DPC link
CIC use statistics for the monitored period :

At the beginning of the period
At the end of the period
Average number of used CIC
Maximum number of used CIC
=> functions to detect congestion, abnormal traffic distribution,

216
Database Traffic Report (2/2)
Transitions CDR
Traffic Report view
As Transitions view, you can

go to all other tables (for the
OPC-DPC direction selected)
217
Interface description Resources (1/2)
Transitions CDR
Resources
Detailed activity for each CIC
CIC reset counters :

During a connection
Out of connection
Statistics :
For Connections (CIC reservation for a call attempt either successful or not)
For Communications (successful call attempts)
Counters
Durations (average, maximum, minimum)
218 => Searching, sorting and filtering functions to detect white

communications, abnormal circuit use,
Interface description Resources (2/2)
Transitions CDR
Resources view
Current use of the Resources view:

Abnormal CIC repartition for one link,
219 Detection of white communication (or cabling issue) by a low average time
communication.
Transitions CDR (1/4)
Call Data Record
CDRs providing a detailed description for each communication progress :

Circuit identification (OPC, DPC, SLS, CIC)
Called / calling phone number
Communication events and related timings
=> Powerful troubleshooting tool :
Sorting and filtering (=, #, <, <=, ) on each provided info element :
OPC/DPC link
Called / calling country or phone number
Event XX number
220
XX procedure duration

Call Data Record view (1/2)
221
Call Data Record view (2/2)
222
Current use of the CDR Viewer

The CDR viewer allows to filter the connections on all the columns.
For instance, filter of all the connections with CONNECT messages and
sorting on increasing CDR duration.
Decreasing sorting
&
223
Case study
-From Setup efficiency to CDR viewer
-CIC Resources allocation
-Investigation from Tansitions to CDR Viewer
224
Case study 1 (1/4)
Case study 2
Case study 3
From Setup efficiency to CDR viewer
Explanation for the link 1 of the values found and the correlation with CDR
viewer.
For couple (10601->10712), we have 3808 IAM with only ACM message
225 following the IAM (no CONnect message).
Case study 1 (2/4)
Case study 2
Case study 3
Link with activity report:
We find 3931 IAM, but the difference

226 is due to connections without
release message (in the column End status
with F letter means end of the capture file).
Case study 1 (3/4)
Case study 2
Case study 3
For couple (10712->10601), we have 8843 IAM with ACM et CON messages.
Split of the 8843 IAM number in Activity Report view
2107 ACM
messages
5378 CON
messages
227
Case study 1 (4/4)
Case study 2
Case study 3
1274 IAM without

ACM or CON
messages
84 Reset
circuit
228
Case study 1
Case study 2 (1/3)
Case study 3
CIC Resources allocation

For OPC=501 and DPC=500 (decreasing sorting for CIC column)
For this ISUP link

only even CIC
number are
allocated
CIC numbers 2
and 4 are allocated
only once
229
Case study 1
Case study 2 (2/3)
Case study 3
For OPC=500 and DPC=501 (decreasing sorting for CIC column)
For this ISUP link

direction, odd CIC
number are allocated
and few even CIC
are allocated when
all odd CIC are used.
CIC number 1 are

allocated only once.
230
Case study 1
Case study 2 (3/3)
Case study 3
Other points
Allocation direction comparison

For OPC=500 and DPC=501, even CIC are allocated between 155
& 275 times.
For OPC=501 and DPC=500, odd CIC are allocated between 86 &
812 times.
No allocation rule for entity 501.
Allocation issue for entity 501

Even CIC between 776 and 868 are allocated 3 times maximum
Allocation issue for entity 500
Odd CIC between 777 and 867 are allocated 10 times maximum
231 PCM ou board issue for this range of CIC (776->868)

Case study 1
Case study 2
Case study 3 (1/5)
Investigation from Tansitions to CDR Viewer
Transitions View:
&
232
Case study 1
Case study 2
Case study 3 (2/5)
Mains releases cause:
releases with cause U-NC (Normal Clearing)

releases with cause LN-NRtD (location=Network serving Local user, cause=No
Route to Destination)
releases with cause RLN-UB (location=Network serving the Remote user, cause
User Busy)
releases with cause INTL-NCCA ( congestion)
releases with cause LN-Itwu (location=Network serving Local user,
cause=Interworking unspecified)
233
Case study 1
Case study 2
Case study 3 (3/5)
INTL-NCCA : location=international, cause=no circuit channel available
&
Congestion seems limited to only a few international destination countries : 218

(Libya), 964 (Iraq),
234 The available capacity of international links towards those destination countries
should be checked, and increased if possible.
Case study 1
Case study 2
Case study 3 (4/5)
LN-Itwu : location=Network serving Local user, cause=Interworking

unspecified
&
connections released by DPCs are for IAM messages in which the Calling party
235 number (ORIG P Nbr) seems not correct : when only a 0 digit, or 0000000 string
or some numbers starting with several 0 digits.
Case study 1
Case study 2
Case study 3 (5/5)
To complement this first analysis, we can select all connections where the called
party number is phone number : 77928515. We can see that :
&
When the calling number is not correct (i.e. set to 0) the connection is released with
cause LN-Itwu; when no calling number is included in the IAM message, there isnt
connection problem
For this release problem we can say that the OPC 274 should not send non correct
Calling numbers.
236



Service Level Management
238
Probe level
Key concepts
SLA Management
239
Description and architecture (1/2)
Probe level
. Key concept
SLA Management

High level description
Service Level Management (SLM) is the ideal tool to manage the

SLAs for Business Customers
Track all activities from one mobile to a fleet
Measure, evaluate and report the QoS per Business Customer
Compare QoS with thresholds to evaluate SLA fulfillment
240
Get SLA satisfaction statistics at the higher level
Description and architecture (2/2)
Probe level
. Key concept
SLA Management
SLM
SLM Analysis
SLA management SERVER QoS
Database
KPIs & CDRs

Database
Intranet
KPIs & CDRs

Database
OCEAN OCEAN
MSC
SGSN
BSC
A
Gb
BTS BTS BTS

241
.
Probe level
Key concepts
SLA Management
242
Probe level (1/2)
. Key concept
SLA Management
Probe level (synoptic)

ALREADY EXISTING NEW
Export_Identities.txt
.los
Cigale
Cigale
GSM/GPRS F
GSM/GPRS .xl3 .slm T
SLM P
Engine
SIGNALING DATA
Engine
KPIs & CDRs

Ocean Probe CigaleBatch AST_cleaner Database
243
Probe level (2/2)
. Key concept
SLA Management
SLM is based on XL3 file (summarized CDRs) processing

At each launch, SLM engine checks for a new Identity file
Search for Business Customers (IMSI in Export_Identities.txt)
Correlation TMSI/IMSI for GSM
Each found CDR is stored in KPIs&CDRs Database
KPIs calculation for Identity, sub-accounts & Accounts
Storage in KPIs&CDRs Database
Generation and copy of result file (.slm) in ftp server area
Check the los file on a regular basis
244
.
Probe level
Key concepts
SLA Management
245 SLM Activity Analysis

Probe level
. Key concept (1/6)
SLA Management
Key concepts
Process overview
Level Tasks
SLM Analysis Troubleshoot on poor delivered QoS
SLA Management Check Service Level respect
QoS Database Keep the QoS history for each identity, each sub-account and each
account (30 days, 52 weeks)
SLM Server Calculate the QoS for each identity, each sub-account and each account
SLM Server Aggregate the SLM KPIs for each identity, each sub-account and each
account for the whole monitored area (network)
KPIs & CDRs Keep the KPIs & CDRs history for each identity, KPIs history for each
Database sub-account and each account (1 Database file per day & per probe)
246 Ocean Probes Calculate the SLM KPIs for each identity within its capture area
Ocean Probes Capture the signaling for all mobiles

Probe level
. Key concept (2/6)
SLA Management
Account/ Sub Account definition
An account is the SLM implementation of a Business Customer fleet
An account can be divided within sub-accounts to reflect different

levels of contract (Sales, Management, office,)
Accounts and sub-accounts are defined by:

Optional Parameters (fully customizable)
A list of IMSI (the identities)
The list of tracked services: GSM, Mobility, Traffic, Voice, Data, SMS
The associated thresholds defining SLAs
247
Probe level
. Key concept (3/6)
SLA Management
Account/ Sub Account Parameters
Optional and customizable for each SLM site
15 fields per Account/sub Account to define for example:

SLA contract type (Premium, Gold, )
BAN: The Business Account Number to identify Business Customers
(sub BAN for sub-accounts)
PriorityClass: The class of priority to sort accounts
KAM: The identification of the Key Account Manager
SalesRepCode: The identification of the Sales Representative
...
248
Used to filter customers on satisfaction reports
Probe level
. Key concept (4/6)
SLA Management
Identities definition
Identity: The IMSI of the identity (Mandatory)

Name: The name of the identity
Account: The account the identity belongs to (Mandatory)
Sub-account: The sub-account the identity belongs to
MSISDN_V: The Voice MSISDN of the identity
MSISDN_D: The Data MSISDN of the identity
MSISDN_F: The Fax MSISDN of the identity
IMEI : The last one used by the identity (Information from capture)
Identity is the database index but other fields (MSISDN, Name, even
249
IMEI) can be used on display.
Probe level
. Key concept (5/6)
SLA Management
SLM QoS for GSM
QoS(GSM) = Weighted average of Mobility & Traffic QoS
QoS(Mobility) = Weighted average of the success rates for

Handovers and Location updating requests (Normal)
QoS(Traffic) = Weighted average voice & data calls, SMS, SS QoS
QoS(Voice calls) & QoS(Data calls) = Weighted success rates for

incoming & outgoing calls
QoS(SMS) & QoS(SS) = Weighted success rates for incoming &
outgoing SMS & SS
250
Probe level
. Key concept (6/6)
SLA Management
SLM QoS for GPRS
QoS(GPRS) = Weighted average of Mobility & Traffic QoS
QoS(Mobility) = Weighted average of the success rates for

Attachment and Routing Area Update procedures
QoS(Traffic) = Weighted average of PDP ctx and visited cells QoS
QoS(PDP ctx) = % of successful PDP ctx (excl. blocked & dropped)

QoS(visited cells) = % of visited cells without radio problems
QoS(Min MS Leak rate) = min(100%, Min Ms Leak Rate/Objective)
QoS(Avg MS Leak rate) = min(100%, Avg Ms Leak Rate/Objective)
251
.
Probe level
Key concepts
SLA Management

Probe level
. Key concept
SLA Management (1/10)
SLA Management
Access through a Web Browser
Requires once SVG Viewer (Adobe) download
Requires Login/password
A Home screen is associated to each user
3 different screens :
Service Level Check
253
Satisfaction Ratio
Satisfaction Period
Probe level
. Key concept
SLM main screen

Menu access
Full screen & export
Comment
254
Probe level
. Key concept
Account, sub-account, Identities
Service to be checked
Display period (up to a month

255 (days), up to a year (weeks))
Probe level
. Key concept
Main screen:
Allow to navigate within the
graphs (double Click
or Right Click: on next page)
256
Probe level
. Key concept
Isolate worst and best

Sub-Accounts or Identities
(one day or one week)
257
Probe level
. Key concept
Going one level down for this

Account_1 gives the QoS for
GSM, Trafic and Mobility
Help balloons (Account (Sub

Acc./Identity), QoS and service,
Probe name and date to select AA
database )
258
Probe level
. Key concept
Satisfaction Ratio Screen
259
Probe level
. Key concept
Accounts/sub-accounts or identities sorted on a QoS value
Filtering on the value of the customizable fields
Selection of a date (a day or a week) and a service
Ratio of satisfied accounts/sub-accounts/Identities
A Top value filtering to reduce the number of items
Access to the Service Level Check
260
Access to the satisfaction period screen
Probe level
. Key concept
Satisfaction Period Screen
261
Probe level
. Key concept
SLA Management (1010)
Satisfaction Period definition
Week QoS Threshold State Satisfaction Period

1 91 90 Satisfied -
2 89 90 Unsatisfied 1
3 87 90 Unsatisfied 2
4 94 90 Satisfied 1
5 90 90 Satisfied 2
6 92 90 Satisfied 3
7 89.9 90 Unsatisfied 1
262
.
Probe level
Key concepts
SLA Management

Probe level
. Key concept
SLA Management
SLM Activity Analysis (1/5)
Used when SLA for one account (or identities) are under the
threshold defined.
Access to the KPIs & CDRS database
1 database per day and per probe
Filtering features enable quick access to the relevant data
264
From Account/ Sub Account/ Identities then the CDRs
Probe level
. Key concept
SLA Management
KPIs for accounts and sub accounts

KPIs for Identities
CDRs
265
Probe level
. Key concept
SLA Management
Go to identities table for this Account
266
Probe level
. Key concept
SLA Management
Go to Activity table for one Identity
267
Probe level
. Key concept
SLA Management
Details connections for this identity
268
10h Cigale Roaming : Emmanuel Ricci

9h-17h : Emmanuel Ricci

9h-17h : David Gallas

16h Debriefing : Emmanuel Ricci & David Gallas
269
www.astellia.com
Trending & Aggregation

270
- Roaming -
Requirements Interfaces
Product Administration
1 Network User
Software Roadmap
Hardware Conclusion
Trending & Aggregation for Roaming

Conclusion
Q&A
271
Requirements (1/2) Interfaces
1 Network User
Software Roadmap
Hardware Conclusion
T&A is also available for the Iu interface (UMTS)
Interfaces
Conclusion
Q&A
272
Requirements (2/2) Interfaces
1 Network User
Software Roadmap
Hardware Conclusion
Improve the detection and resolution of problems

History of Cigale results
Means to perform KPI trending analysis
Provision of a network level view for KPIs
Alarm generation on KPI crossing threshold
Ease the access to Cigale Data

Web browser based solution
Automatic broadcasting of pdf reports
Extraction of data towards GIS or Data Mining solutions
Provision of a Business Objects universe
Ease the adaptation to specific needs & environments

User defined KPI and views
273
Configurable reports and alarms
Product (1/11) Administration
1 Network User
Software Roadmap
Hardware Conclusion
Network architecture
Software structure
Hardware needs
Interfaces
Conclusion
Q&A
274
1 Network (1/4) User
Software Roadmap
Hardware Conclusion
Network architecture
Probes & Cigale Engines
T&A Server
Administration
275
KPIs Browsing
Software Roadmap
Hardware Conclusion
Roaming files collector
T&A Server
Administration
276
KPIs Browsing
Software Roadmap
Hardware Conclusion
Global architecture
Regional/Affiliate T&A Server
National/Corporate T&A Server
Regional/Affiliate T&A Server
277 Administration
KPIs Browsing
Software Roadmap
Hardware Conclusion
Probes & Cigale Engines Madagascar

le Maurice
Cameroun
Orange Afrique
Cte dIvoire
278 Administration
KPIs Browsing
1 Network User
Software (1/5) Roadmap
Hardware Conclusion
Software structure
Administration
Cigale Engines Import Database Web Server

End users
Business Objects
Universe
T&A kernel
279
1 Network User
Hardware Conclusion
Import module
Automatic import of Cigale counters

Hourly/daily
Customizable set
Ability to compute specific KPIs
Network Aggregation :
Cell/BSC/LAC/MSC/Network + Group of cells (highways, train, airport, etc.)
280
1 Network User
Hardware Conclusion
Third axis aggregation

Home network/Country/Group for Roaming
Network level
PLMN
MSC
BSC
LAC
Cell Time
Operator X
Day1 Day2 Day3
Operator Y
Home network
281
Alarm generation (email) on threshold crossing
1 Network User
Hardware Conclusion
Database
Database language is PostgresSQL
Business Objects Universe

Planned for Ending 2005
History size for a regional/affiliate server

(taking parameters : 10,000 cells and 1000 values (counters & KPIs)
History of 1 week for hourly values
History of 6 months for daily values
History of 1 year for weekly values
History of 5 years for monthly values
282
1 Network User
Hardware Conclusion
Web server
Navigation
Graphs (Over time || Topology)
GIS (Vorono)
Report generation
Automatic export of data as Excel files
283
1 Network User
Software Roadmap
Hardware (1/1) Conclusion
Hardware requirements
Servers configuration (To be provided by the customer)

Bi-processors Server 3Ghz
8GB of RAM
Hard Disk Sizes :
2 hard Disks of 36GB/15000rpm each (Raid 1) for the Operating System
3 hard disks of 146GB/15000rpm each (Raid 5) for the data storage (or remote)
Backup on DLT/DAT Tapes or network
Redundant Power Supply
Linux
Minimal throughput requirement

2 Mb/s between regional/affiliate servers and National/Group server
284
1 Network User
Software Roadmap
Hardware Conclusion
Interfaces
Administration interface
User interface
Conclusion
Q&A
285
Product Administration (1/2)
1 Network User
Software Roadmap
Hardware Conclusion
Counter selection
286
Product Administration (2/2)
1 Network User
Software Roadmap
Hardware Conclusion
KPI builder
287
1 Network User (1/15)
Software Roadmap
Hardware Conclusion
KPI display
288
Software Roadmap
Hardware Conclusion
Dashboards
Roaming Activity Overview

Efficiency of roaming Location Updates
Efficiency of voice roaming traffic
Categories of Accepted Roamers
Main roaming networks for location updates
Main roaming networks for traffic
289
Software Roadmap
Hardware Conclusion
290
Software Roadmap
Hardware Conclusion
291
Software Roadmap
Hardware Conclusion
Roamers capture (over network elements / time)

Global efficiency of roamers LU
Efficiency of roamers LU (with a different IMSI)
Reject causes for roamers LU
Reject causes for roamers LU (with a different IMSI)
292
Software Roadmap
Hardware Conclusion
293
Software Roadmap
Hardware Conclusion
294
Software Roadmap
Hardware Conclusion
Roamers traffic (over network elements / time)

Roaming traffic
Roaming traffic repartition and efficiency
Roaming voice calls setup success rate
Roaming voice calls drop call rate
Roaming MT SMS
Roaming MO SMS
295
Software Roadmap
Hardware Conclusion
296
Software Roadmap
Hardware Conclusion
297
Software Roadmap
Hardware Conclusion
Roamers loss (over network elements / time)

Roamers Loss
Roamers Recoveries
Biol
298
Software Roadmap
Hardware Conclusion
299
Software Roadmap
Hardware Conclusion
300
Software Roadmap
Hardware Conclusion
Alarm display
301
Software Roadmap
Hardware Conclusion
Report builder
302
1 Network User
Software Roadmap (1/2)
Hardware Conclusion
Interfaces
Conclusion
Q&A
303
1 Network User
Software Roadmap (2/2)
Hardware Conclusion
2005 2006
Q1 Q2 Q3 Q4
T&A Cigale GSM T&A Gb

T&A Roaming + BO Interface T&A Iub
Trending & Beta Version + Enhancements T&A Gn
Aggregation
T&A Iu Oracle Support

T&A Roaming SNMP alarms
New features for 2006

Alarm filtering
304 Multi severity alarms
Black cells
Busy hours
1 Network User
Software Roadmap
Hardware Conclusion (1/2)
The requirements of Astellia Customers

Astellia solution
Interfaces
Conclusion
Q&A
305
1 Network User
Software Roadmap
Hardware Conclusion (2/2)
Conclusion
KPI trending & aggregation
Alarms triggering on KPI threshold crossing
Automatic pdf report
Access through a Web browser (Simple GIS)
A centralized and integrated system
High level of customization but also a turnkey solution
Huge history database (Oracle capable)
Business Objects Universe (end 2005)
306
!1
Please ask any question you might have
307
www.astellia.com
Abis surfer
308
"
Training content
Introduction :
Concept and approach
Advantages
Vendors compatibility
Abis Surfer principles
Files processing
Graphical user Interface description
Standard reports:
Interference detection & Sensitivity measurement
Spatial analysis
Link balance analysis
Path balance analysis
neighbor analysis
Automatic reporting
309 Case studies:

Case studies based on demonstration file
Analysis based on customer file.
310
' ''
Easy access to radio optimization by Abis data analysis.

Detection and identification of radio problems thanks to a statistic view at
different levels (BTS, Cell, Trx).
Based on real subscribers communications.

Statistical tool => needs massive capture tool.
Typical applications:
Sensitivities measurement
Interference Detection
Cell Size Evaluation
Link Balance
Path Balance

311
' ''
Abis Measurement Results
Um Abis
MS BTS BSC
Meas. Report Meas. Result
[DL RxLev, DL RxQual] [ Meas. Report, UL RxLev, UL RxQual, T. A.]
Abis Surfer exploits Meas. Result messages to provide statistics from

following values:
DL RxLev*, DL RxQual
UL RxLev, UL RxQual
Timing Advance.
312
* (from serving cell and the 6 strongest neighbors cells)
' ''
A relevant approach
Abis Interface MR analysis is an important tool in the radio engineers test

outfit.
In most of the cases, it can spare drive test.

Saving of time and money
Access to information on both Uplink and Downlink.
Allows to weight a problem:

Does it affect a lot of subscribers ?
Does it have a high priority level?
Resolves 80% of encountered radio problems.

313
' ''
Who are the users?
Radio engineers:
Optimization and planning
Operation & Maintenance engineers:

Troubleshooting
Detection of defective equipment (Trx, Combiner, Feeder,.).
Validation of new site commissioning.
Antenna tuning.
314
' ''
Implementation
Mobile use: AbisSurfer pack
Laptop For
RS-232 Quick on site
Abis links serial link captures
Abis Sufer
Pack
223
Ethernet
Desktop PC for remote

controlled campaigns
Deployment: Manta & Ocean
Abis links Ethernet

MANTA OCEAN
MANTA Abis Surfer

for capture files
223
MANTA processing Remote control
315 Abis Surfer Software for
MANTA analysis
' ''
Abis Surfer Pack Features
All-in-one tool
One switching module
8 E1 PCM inputs.
Auto detection of signaling TS.
One acquisition module

31 signaling TS
Supports all Abis signaling throughput.
64kbits/s
16kbits/s
statistical multiplexing on 64 kbits/s
Capture and treatment automation

316 Remote control
"
Meas. Res. Analysis Vs Drive-Test
Meas. Res. Analysis advantages:
Access to DL and UL information (only DL for Drive-tests)
Provides statistical view for complete cells (drive tests only give a
snapshot view)
Results quickly obtained.
Call non simulated : real calls.
The most pertinent optimization method for indoor coverage.
Drive-tests advantages.
Benchmarking between operators
Provides accurate localization.
BTS Setting up in a small traffic area
317
"
Meas. Res. Analysis Vs OMC
Abis Surfer advantages:
Vendors independant data.
No extra-processing load on BSC and BTS.
Doesnt require communication between different teams.
Ease of use for regional O&M teams (no need to get statistics from
OMC).
Cheap price.
318
* ' "
Full automatic compatibility

Ericsson
Nokia
Alcatel
Full compatibility : Parameters setting required before capture

Nortel : Flag activation on OMC for each monitored BTS to force
BTS to transmit MR in the standard form
Siemens : setting of two parameters on OMC for each monitored TRX
(RadioMR=true, RadioMG = 1)
Incompatibility
Motorola : Any tool using MR faces the same problem
319
For other vendors, notice that Abis Surfer is fully compatible with Abis
GSM standard phase 1, 2 and 2+.
"
'
320
" ' '
Files Processing
Automatic : each new capture file (.edx or .edb) is automatically post-

processed with Abis Surfer SW.
Thanks to a line command included in a batch file.
The corresponding batch file must be declared in Ocean.
At the end of the process, a result file (.abs) is automatically stored.
User has just to use the File|Import command to analyze this result file.
Manual : one or several files can be processed simultaneously.

User has just to use the File|Open command.
Process results can be exported in .abs file thanks to the File|Export
command.
321
" ' '
Graphical User Interface
Capture file
level
Exportable table
result
Cell level
Trx level
Chart results
Neighbor cell
selection
Results are available at all levels: Capture File, Cell, Trx.

322 The count value allows to determine the statistical validity of the results.
Any result table can be separately exported in text format (.csv) to be used in a
spreadsheet.
'
323
'
Sensitivity / Interference chart(1)
Used to detect interference and measure sensitivity.
Interference detection
RxQual Vs RxLev chart
Interference: bad quality (high RxQual) with a relatively high level.
Interference-free cell or Trx: good quality until the level becomes low.
( lower than -100 dBm).
324 Interferences.
No Interference
The number of samples shows that the
problem affects a lot of subscribers.
'
Sensitivity / Interference chart(2)
Sensitivity Measurement.
Sensitivity: lowest RxLev to guarantee a BER of 2%
(RxQual = 4).
Useful to check values given by manufacturers
(Most of the manufacturers give optimistic values).
Field reference value taken as a base calculation mark.
Measurement
conditions:
-no interference.
RxQual = 4 -a minimum of 500 to
1000 samples
325
5 @ 2A . 6
'
Spatial Analysis (1)
Based on Timing Advance value:

One TA unit represents 500m in the field.
Timing Advance Distribution:

Displays the number of MR messages per TA.
Used to estimate the traffic geographical distribution and cell size.
326
'
Level vs. Timing Advance:

Shows the average level experienced by the users as a function of the
distance to the cell antenna.
Used to coverage holes and island detection.
Quality vs. Timing Advance :

shows the average quality experienced by the users as a function of the
distance to the cell antenna.
Used to validate frequency planning
327
'
Example of cell size evaluation .

RxLev Vs Timing Advance chart
RxQual Vs Timing Advance
A well designed cell with a radius of Cell with coverage island at 14 Kms
4 Kms. from the BTS
328 The low number of samples shows that few subscribers are affected.
Such a chart can be usefull to tune antenna tilt.
'
Link Balance Analysis (1)
To balance means to insure a bi-directional communication in any point of the

cell coverage between MS and BTS.
The principle is to adjust BTS output power to the MS possibilities.
Unbalanced Link Balanced Link
329 An unbalanced link can be the cause of interferences.

'
Link Balance Analysis (2)
The link balance distribution chart is used to determine if a link is well
balanced.
This chart provides a statistical distribution of the delta between
downlink and uplink level: (RxLev DL - RxLev UL).
A link is balanced if :
Link Balance(Avg)= Sensitivity DL - Sensitivity UL
330
Sensitivities value are measured with Sensitivity/Interference chart.
'
Path Balance Analysis (1)
Path Balance represents delta between DL path loss and UL path loss.
Used to point :
damaged equipement (Trx, antenna feeder,).
differences in antenna gains.
system malfunctioning.
For these computations, following MS powers are assumed :

1W mobile for a 1800 MHz cell.
2W mobile for a 900 MHz cell.
TRX nominal power must be set to the correct value in order to have valid
results:
331 globally for a cell using Cell | Set Power Menu,
TRX by TRX using TRX | Set Power Menu.
'
Path Balance Analysis (2)
The Path balance distribution chart provides a statistical distribution of the

delta between downlink path loss and uplink path loss.
Path BalanceAvg = (Path loss DL Path loss UL) Avg
Two ways of use:

Long term: periodical check of the value to detect an equipment degradation.
Short term: comparison between the different Trx of a
332 BTS to detect a defective unit.
"
Principles
For the 6 strongest neighbors cells, the MS reports periodically to the BTS:
the Signal Strength,
the BA index (the position, starting with 0, of the BCCH carrier in the BA list), and
the BSIC.
In Abis Surfer, user provides a Network Configuration File describing the cells
and their associated neighbors with the following format:
ServingLAC;ServingCI;ServingName followed by n times
;NeighborLAC;NeighborCI;NeighborName;NeighborBCCH;NeighborBSIC
Example:
10500;35450;BAKER-STREET-G-0;10500;10120;SHADWELL-G;23;20
10500;35651;CHARING-CROSS-G-0;10500;10122;TOWER-HILL-G-0;78;22;10500;10102;EAST-INDIA-G-0;86;23
10800;38452;EUSTON-D-2
Two types of results are available:

neighbor RxLev
333 Server - neighbor Delta Level distribution.
"
neighbor RxLev (1)
This analysis is useful to validate neighbor lists and frequency plans.
Provides the average RxLev of all neighbors as well as the number of reports
including this neighbor (count).
Chart display the neighbors, sorted by order of decreasing level or count with
their BA index, BCCH and BSIC.
Cells declared by operator as neighbors must appear at the top of the list
334
"
Server - neighbor Delta Level distribution.
This analysis can assist the operator in many of its common tasks:
Handover margin tuning,
Handover threshold tuning,

Provides a statistical distribution of the delta between the serving cell RxLev
and the neighbor cell RxLev.
Serving Cell selection
Delta level distribution

335
Neighbor Cell selection
'
The automatic report allows user to partly automate Abis Trace analysis
Different domains of reporting are available:

Cells & TRX problems
TCH traffic analysis
Frequency configuration

Results are displayed in:
Expert Report tab
A text file saved on demand
336
337
Path Balance
On this site, the theoretical difference between DL and UL path are:

Combiner loss in the DL path: 5.2 dB (manufacturer value)
Diversity gain in the UL path: 3 dB (assumed)
The path balance value should be approximately
8 dB
Measurements: the distribution shows a bump

on the curve. The measured value are:
Cell: 8.6 Db
Cell average value= 8.6 dB
TRX 1 : 6.3 dB
TRX 2 : 31.8 dB
TRX 3 : 6.6 dB
Path Balance is too high for TRX2:

=> The equipment is damaged and needs
338 to be changed
TRX 2 average value= 31.8 dB

neighbor Analysis
neighbor RxLev measurement:
Two cells with BCCH 80 are measured:
BCCH 80/ BSIC 20 reported 68527 times
Not declared in the network configuration file
BCCH 80 / BSIC 21 reported 11018 times
This cell really declared in the network configuration file (name BANK-G-0)
This is an abnormal situation and the following points need to be checked:

Are BCCH frequencies properly defined ?
Do the neighbor cells list need to be modied?
Addition of BCCH 80/ BSIC 20
Deletion of BANK-G-0
339

Master your Network Performance in 40 Characters

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Master your Network Performance in 40 Characters

Încărcat de

Drepturi de autor:

Formate disponibile

Master your Network Performance

Week 39 : CIGALE ROAMING, CIGALE ISUP and value added services

Week 40 : MANTA, OCEAN

Tuesday, September 27th : Roaming View

Thursday, September 29th : Cigale Isup

Friday, September 30th : SLM, Trending & Aggregation and debriefing

Offices in Paris, New York and Singapore

A worldwide Partner & Representative Network

A 20-year experience in the Telecom industry

75 highly qualified people

7.5 M Turnover in Y2004 (6 M in Y2003)

A clear view on Infrastructures,

Expert in solutions dedicated to Network Operators & Vendors

Troubleshooting Protocol Analyzers

A complete and open solution

Top-down troubleshooting tools

Dedicated to mobile operators

With Astellia ROAMING solution,

and increase your roaming revenue

Cigale Roaming, Cigale ISUP

Tuesday, September 27th : Roaming View

Thursday, September 29th : Cigale Isup

Friday, September 30th : SLM, Trending & Aggregation and debriefing

Tuesday, September 27th : Roaming View

Thursday, September 29th : Cigale Isup

Friday, September 30th : SLM, Trending & Aggregation and debriefing

Detection of cells welcoming the highest number of

Marketing aspect, specific advertisement :

Analysis of roamers traffic per network of origin

Detect specific behaviours and consumption modes in relation

Coverage compared to competitors

competitors coverage holes : points where their subscribers try to

for your own subscribers : comeback points and previous

Be sure that the roamers can localise in your network

Roaming specific problems (international gateways)

No inter operator agreement (generalised PLMN Not Allowed)

Subscriber without roaming option (partial PLMN Not Allowed,

Reach and maintain a higher QoS on cells where roamers

Location updates (capture and transit)

Call setup inefficiency (avoid congestion)

Call drops (could be confirmed with Cigale View)

A roamer can be detected by Cigale roaming engine thanks

MCC MNC MSIN

MCC : Mobile Country Code

IMSI is transmitted on A interface:

when a user performs a location updating request and there is no

The user transmits its IMSI to the network

In case of Mobile terminating procedure: MT Call or MT-SMS

Paging message of A interface includes IMSI

Location Update flow

MS BSS MSC/VLR HLR

MM LOCATION UPDATING REQUEST

MS BSS MSC/VLR HLR

BSSMAP CIPHER MODE MAP_UPDATE_LOCATION ACK

Allocation of temporary identity and release of the radio channel

MM LOCATION UPDATING ACCEPT

BSSMAP CLEAR COMMAND

BSSMAP CLEAR COMPLETE

Once IMSI is detected, Cigale Roaming is able to follow up

Statistics based on Roamers

QoS KPIs on Roamers activity

Detailed Roamers activity

One part of results is computed by Cigale