5 CigaleCorePS Basics V52 ATS RA Student

Cigale Core PS
OSTILL - Fotolia
1 - Basics
Objectives
At the end of the lesson the student will be able to:
Describe the Core PS architecture Describe the different Core PS Interface protocol Understand tunnel principle Understand the different message types and give some examples Understand the main basic procedures and the different types of network configurations Understand differences between DNS Network and DNS User Understand Direct Tunnel procedure
Astellia confidential
Astellia Core PS Solution Architecture

Data acquisition
24h/24 raw data capture Gn, Gp, DNS, RADIUS, Gi Gx/Gy/Gz
Data processing
On-line CDR generation Periodic KPI generation
Results consolidation Operators Information system

Network-wide information KPI trending Export of statistics, reports, alarms
Data viewing and reporting

Site 1 Central database Probes Engines Site 2 Databases
Reporting and alarming on Web browser for all teams Dedicated investigation tools for experts
System management
Process flow automation System administration System supervision
QoS management Performance analysis Network optimization Troubleshooting SLA management
Core PS architecture
GGSN
PCRF DNS Server Foreign PLMN Gx Gy
Charging online Charging offline
Abis
PCU
DNS interface Gb
Gp Inbound SGSN Gn
Gz
DIAMETER
GGSN Gi
BTS
Internet
Iub
RNC
Iu-PS Gr
HLR
Gp Outbound Gn
SGSN
NodeB
RADIUS interface
Foreign PLMN
RADIUS Server
4
Protocol Stack
Application UDP/ TCP IP Relay SNDCP SNDCP LLC Relay RLC RLC MAC GSM RF MAC BSSGP Network service BSSGP Network service L1bis LLC GTP UDP/ TCP IP L2 L1 UDP/ TCP IP L2 L1 L1 L1 GTP Application UDP/ TCP IP
L2
L2
GSM RF L1bis
MS
Um
BSS
Gb
SGSN
Gn/Gp
GGSN
Gi
Server / Gateway
5
PDP Context
PDP: Packet Data Protocol
Information stored in MS, SGSN, GGSN to allow data exchanged with PDP network
Subscriber's IP address (IPv4, IPv6 ou IPv4v6) IP address of current SGSN Access Point Name (APN) : logical name of a PDP network (ex : mywap) Subscriber's IMSI Tunnel Endpoint ID (TEID) CP/UP at the GGSN Tunnel Endpoint ID (TEID) CP/UP at the SGSN Quality of service parameters
There are two kinds of PDP contexts.

Primary PDP Context: Has a unique IP address associated with it Secondary PDP Context: Shares an IP address with another PDP context. Is created based on an existing PDP context (to share the IP address). Secondary PDP contexts may have different Quality Of Service settings.
A total of 11 PDP contexts (with any combination of Primary and Secondary) can co-exist.
PDP Context
Quality of Service (QoS) parameters:

Reliability : defines 5 levels of data protection and acknowledgment . Precedence (3 classes) : defines priorities between sessions (low, normal & high). In case of overload, service commitments of sessions with high priority shall be maintained ahead of other ones. Delay class (4 classes): indicates the transmission duration of one packet through the network. Best effort is often used. Peak Throughput: max expected throughput. Mean Throughput: average expected throughput. Traffic Class: conversational, streaming, interactive, background Transfer delay: maximum delay for 95th percentile of the delays for all SDU. Priority handling (1, 2, 3): relative importance for handling of all SDU (Service Data Unit) belonging to the bearer service compared to the SDU of other bearers. Guaranteed bit rate for UL/DL: bearer service attributes (delay and reliability) are guaranteed for the traffic up to this value.
Tunnel principle
Core PS part
Tunnel CP UL
SGSN
Tunnel CP DL
GGSN
GTP Tunnel
Tunnel Data DL Tunnel Data UL
Internet
(Core Network)
TEID
TEID: Tunnel endpoint Identifier
Gn/Gp protocol
Used Protocol: GTP (GPRS Tunneling Protocol) - 2 differents entities: GTP-C (Control plane): Gn interface GTP-U (User plane): Gn and Iu-PS interfaces 2 different protocol versions are available: GTP V0 and GTP V1 - Release 98: GTP V0 (3GPP TS 09.60 Version 7.10.0) - Release 5: GTP V1 (3GPP TS 29.060 Version 5.9.0) GSNs implementing GTP V1 should be able to fallback to V0
Gn/Gp Protocol Stack

MMS WAP DNS SMTP POP3 HTTP FTP RTSP
Applicative layers
UDP TCP IP UDP is the mandatory protocol GTP V0: UDP ports 3386 (Control Plane and User Plane) GTP V1: UDP ports 2123 (Control Plane) and 2152 (User Plane) GTP V1: IPV4 or IPV6 GTP V0: IPV4 UDP IP L1
10
GTP
Gn/Gp Messages (1/5)

[1] Path management messages
[2] Tunnel management messages
[3] Mobility management messages
GSN
Location management messages (optional)
GSN
Gn/Gp interfaces [4] T-PDU
GTP-C GTP-U
11

[PATH MANAGEMENT]
- Messages sent between any type of GSN pair to manage logical paths. - Active Path = at least one PDP context uses the path - To find out if the peer GSN (SGSN,GGSN or RNC) is alive Keep alive (ECHO Request, ECHO Response) - To notify parameters issue Reporting (Version Not Supported, Supported Extension Headers Notification)
12

[TUNNEL MANAGEMENT]
- Messages sent between any type of GSN pair to manage tunnels - Tunnel Creation/Deletion (PDP) Create PDP Context Request / Create PDP Context Response Delete PDP Context Request / Delete PDP Context Response - RAU, PDP update, context redistribution (load sharing) or intersystem mobility Update PDP Context Request / Update PDP Context Response - If the GGSN receives a PDU for a not connected PDP, it will try to create it (Network-requested PDP Context Activation procedure) in order to deliver its PDU PDU Notification Request/Response/Reject Request/Reject Response
13

[MOBILITY MANAGEMENT] Mobility Management messages are control plane messages sent between SGSNs during:
- IMSI request for GPRS Attach procedure (SGSN-SGSN) Identification Request, Identification Response - Inter-SGSN Routing Area update procedure SGSN Context Request, SGSN Context Response, SGSN Context ACK - Inter RNC relocation/3G-2G handover with Core Network switch Forward Relocation Request, Forward Relocation Response, Forward Relocation Complete, Forward Relocation Complete ACK, Forward SRNS Context, Forward SRNS Context ACK, Relocation Cancel Request, Relocation Cancel Response
14

[USER PLANE] Send and Receive PDU
Only one message for Uplink and Downlink T-PDU
15
Main procedures (1/5)

PDP Context Activation Procedure
SGSN GGSN
Activate PDP context request Create PDP context request Security functions Create PDP context response Activate PDP context accept
16

PDP Context Deactivation Procedure
SGSN GGSN
Deactivate PDP context request Delete PDP context request
Delete PDP context response Deactivate PDP context response
17

Inter-SGSN Routing Area update with PDP active
New SGSN Old SGSN GGSN
RA Update request SGSN context request SGSN context response SGSN context acknowledge
Update PDP context request Update PDP context response RA Update response
18

PDP Context Update Procedure:
QoS change: at least one QoS parameter changes. 2G to 3G mobility: Rat type changes from GERAN to UTRAN. 3G to 2G mobility: Rat type changes from UTRAN to GERAN. Direct Tunnel activated: Direct Tunnel Flag. Direct Tunnel deactivated: Direct Tunnel Flag is absent and the previous Update PDP Context Request contained Direct Tunnel Flag. Inter SGSN mobility: New SGSN IP address.

Sending and receiving PDUs
SGSN GGSN
SNDCP-PDU {TLLI, NSAPI, PDP-PDU}
GTP-PDU {TID, PDP-PDU} PDP-PDU
SNDCP
GTP
GTP-PDU {TID, PDP-PDU}
IP
PDP-PDU {PDP address}
External IP network
SNDCP-PDU {TLLI, NSAPI, PDP-PDU}
20
Network Configuration (1/5)

What does the norm say:
(extract from 3GPP 29.060)
- Request messages:
The UDP Destination Port number for GTP-C request messages is 2123. It is the registered port number for GTP-C. The UDP Destination Port number for GTP-U request messages is 2152. It is the registered port number for GTP-U. The UDP Source Port is a locally allocated port number at the sending GSN/RNC.
- Response messages:
The UDP Destination Port value shall be the value of the UDP Source Port of the corresponding request message. The UDP Source Port shall be the value from the UDP Destination Port of the corresponding request message.
21

Different ways to implement the network
- Main case:
SGSN GGSN
Create PDP context request Create PDP context response IP 1 port 2123 Delete PDP context request Delete PDP context response IP 2 port 2123
22

- Random SGSN port number
SGSN
GGSN
Create PDP context request Create PDP context response IP 1 random port Delete PDP context request Delete PDP context response IP 2 port 2123
23

- IP per type of procedure
SGSN
GGSN
Create PDP context request IP 1 2123 or random port Create PDP context response Delete PDP context request Delete PDP context response IP 3 port 2123 IP 2 port 2123
24

- IP per type of message (Request vs. Response)
SGSN
GGSN
Create PDP context request IP 1 2123/random port Create PDP context response Delete PDP context request Delete PDP context response
IP 2 port 2123 IP 3 port 2123 IP 2 port 2123 IP 3 port 2123
25
3GPP Release 7
New features
Direct Tunnel New IEs in PDP Context Request messages:
IMEI RAT type (GERAN UTRAN WLAN) User location (cell type, LAC-RAC, cellid or SAC)
26
Direct Tunnel (1/4)

Flat architecture : ready for LTE networks. Reduce cost for operators. User data traffic routed directly from the radio access network to the core networks Internet gateway node. Bypass the control node (the Serving GPRS Service Node, the SGSN) through which data traffic is routed in existing networks. UMTS feature only.
27
Direct Tunnel (2/4)

Without Direct Tunnel
RNC Radio part
(RANAP)
SGSN
(GTP-C)
GGSN IP Network
(GTP-U)
(GTP-U)
Iu-PS
Gn
SGSN
Control Plan User Plan
With Direct Tunnel
(RANAP)
(GTP-C)
Radio part
GTP-U Direct Tunnel

RNC GGSN
IP Network
28
Direct Tunnel (3/4)

Direct Tunnel used in only some RNCs
RNC 1 Radio part
Control Plan User Plan
GGSN
(GTP-U) (RANAP)
(GTP-U) (GTP-C)
SGSN
IP Network
Radio part
GTP-U Direct Tunnel

RNC 2
29
Direct Tunnel (4/4)

Direct Tunnel Establishment
RNC SGSN GGSN
Activate PDP Context Request Create PDP Context Request Create PDP Context Response RAB Assignment Request
(GGSN TEID, GGSN User Traffic Address)
RAB Assignment Response Update PDP Context Request

(DTI flag, RNC TEID, RNC User Traffic Address)
Update PDP Context Response Activate PDP context accept
GTP-U
30
DNS Network
DNS: Domain Name System
The APN Resolution process allows to a SGSN to obtain the IP address of the GGSN which should serve an APName (Access Point Name). IP address can be an IPv4 or IPv6 address.
SGSN DNS Network GGSN_x
SGSN sends a DNS Request with an APName
DNS Query
APName
DNS Response
IP GGSN_x
DNS server answers back with GGSN IP address associated to APName.
Create PDP context request

31
DNS Network vs. DNS User

www.google.com
SGSN
DNS Network
GGSN_x
DNS User
Service request
APN: internet
DNS Query
internet
DNS Response
IP GGSN_x
Create PDP context request Create PDP context response PDP Act. Complete PDU
www.google.com
PDU DNS Query

www.google.com
PDU PDU
IP Google
DNS Response
IP Google
32
RADIUS Protocol (1/3)

RADIUS (Remote Authentication Dial In User Service) is a protocol used for Authentication, Authorization and Accounting - Authentication: user identity is checked (username/password) - Authorization: service access rights for a user are checked
RADIUS_ACCESS_REQUEST RADIUS_ACCESS_ACCEPT RADIUS_ACCESS_REJECT
Accounting: RADIUS provides information for billing (service access duration between RADIUS_ACCOUNTING_START and RADIUS_ACCOUNTING_STOP)
RADIUS headers format (request and response are associated through @IP src/dest, UDP port number and Packet identifier)
Bit
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Code Identifier Length Authenticator Attributes
33

RADIUS architecture
GGSN
Access Server RADIUS server or proxy RADIUS server 1 RADIUS server 2
Database
RADIUS server N
Optional (depends on operator configuration)

1 request could be forwarded to several servers but only the first response would be taken
34

SGSN GGSN_x RADIUS Server
Create PDP context request RADIUS Access-Request

APName
RADIUS Access-Accept
Mobile IP address
RADIUS Accounting-Request (Start) Create PDP context response RADIUS Accounting-Response (Start)
Delete PDP context request RADIUS Accounting-Request (Stop) Delete PDP context response RADIUS Accounting-Response (Stop)
35
DIAMETER Protocol (1/3)

DIAMETER is a protocol used for Authentication, Authorization and Accounting. It is an alternative to RADIUS. A DIAMETER frame consists of a Diameter header and a variable number of AttributeValue Pairs (AVP) for encapsulating information relevant to the Diameter message.
36

DIAMETER Overview
Application Function
(AF)
Rx
Subscription Profile Repository
Sp
Policy and Charging Rules Function
(SPR)
(PCRF)
Gxx Online Charging System
Gx Gy
(OCS)
Bearer Binding and Event Reporting Function Policy and Charging Enforcement Function Service Data Flow Based Credit Control
(BBERF)
(PCEF)
AN-Gateway
PDN-Gateway
Gz
Offline Charging System
(OFCS)
The Gx reference point enables a PCRF to have dynamic control over the PCC behavior at a PCEF. The Gy reference point allows online credit control for service data flow based charging. The Gz reference point enables transport of service data flow based offline charging information.
37

SGSN GGSN_x DIAMETER Server
Create PDP context request
DIAMETER Credit-Control-Request Initial Request DIAMETER Credit-Control-Answer Initial Request
Create PDP context response Update PDP context request DIAMETER Credit-Control-Request Update Request DIAMETER Credit-Control-Answer Update Request Update PDP context response Delete PDP context request DIAMETER Credit-Control-Request Termination Request DIAMETER Credit-Control-Answer Termination Request Delete PDP context response
38
Gi Protocols
Applications
MMS
WSP
RTCP
RTP
WTP
DNS
HTTP
RTSP
FTP
SMTP
POP3
UDP
TCP
ICMP Application IP UDP/TCP IP L2 L1 L2 L1
TCP/IP Model
39
Cigale Core PS
OSTILL - Fotolia
2 - Engine
Objectives
At the end of the lesson the student will be able to: - Describe Cigale Gn Engine (input/output files) - Understand the different part of user interface and main parameters of Cigale configuration - Understand Cigale Gn state machine
41
Overview (1/4)
Probe Capture on Gn, Gp, Gi, Gx, Gy or Gz (Ocean, Neptune, K12, Nethawk, Libcap)
Cigale Gn engine
Activity Analysis High detail level investigation and analysis (Troubleshooting)

42
Overview (2/4)
Cigale Gn can be described as a "spy" located at level of the Gn/Gp/Gi/Gx/Gy/Gz interfaces, between GSNs (SGSNs and GGSNs) and toward IP Network With Packet Services Monitoring (PSM) option, user can follow a session at the applicative layer (HTTP/FTP/POP3) Cigale Gn provides different kinds of results:
-
Activity Analysis database (for troubleshooting and optimization) Results files (for SI export )
Cigale Gn can work in multi engines configuration

-
Enrichment from signalling engines to data engines.
43
Overview CorePS 5.2 Neptune (3/4)

Usage Analytics Tuples (periodic IP links + APN statistics)
Stat Factory .NPS files
Fault Manager
TCPDR (TCP/UDP session summaries)
Stream (CP only)
Cigale Engine
Stat Factory Stream .CPS files
T&A Core PS (sig hourly +PSM hourly)
XCAP
AA (CDR) + VIA
NEPTUNE Probe PSM Engine

NB: PSM Engine = Cigale Gn + PSM option AA (IPDR, PSDR) + VIA
Text files Stream
VIP Care
.XLP file
HPG
.HPG file
T&A HPG 44
Overview CorePS 5.2 Ocean (4/4)

NB: PSM Engine = Cigale Gn + PSM option Fault Manager
Capture files (CP only)

EDX
Cigale Engine
Stat Factory Stream .CPS files
Ocean Probe
Enrichment files (BIN/BCK)
T&A Core PS (sig hourly +PSM hourly)
AA (CDR) + VIA
Text files
EDX
Stream
VIP Care
Capture files (UP only) NB: PSM Engine = Cigale Gn + PSM option
PSM Engine
AA (IPDR, PSDR) + VIA
.XLP file
HPG
.HPG file
T&A HPG 45
Input files
Description of the State Machine
AUTOMAT, EVENTS,CAUSES,STATES Description of the network topology GSN, DNS, RADIUS, DIAMETER topology.txt,
2G 3G topology
Configuration file
Cigale Gn
IP2country.txt, TAC.txt, networks.txt
Other files :
Capture file :
EDX (OCEAN) XCAP (NEPTUNE) PCAP (TCPDUMP, ETHEREAL)

46
Topology file (1/2)

Overview - This file is used when processing record files to name the detected GSNs, DNS, RADIUS and DIAMETER systems - The extension of the core network data base files is Txt. - Path to the topology file has to be set into the Cigale Gn configuration.
47
Topology file (2/2)

IP@ range for SGSN, GGSN, DNS, RADIUS and DIAMETER This file provides the possibility to assign explicit names to GSNs as well as for DNS/RADIUS/DIAMETER servers
If DNS/RADIUS/DIAMETER servers are not filled, no CDR would be generated
Because there is no possibility at all to discover automatically the network topology
48
IP2country
IP2country.txt
The file IP2country.txt provides a description of IP addresses allocated per country
Useful to automatically assign names to GSNs when no description is provided (no GSN description file available or incomplete description)
49
ASM Integration (1/3)

ASM : Astellia System Management
- Process flow programming:
Cigale Gn configuration Tasks configurations: copy (.edx files, results of the engines), clean,
- Process flow synchronization:

launching/stop/sequencing of the tasks
- Process flow supervision:

monitoring of the treatments, automated alarm system
- Process flow reliability:

system of relaunching of the treatments in case of error
50

Network tree structure Tasks Access to tasks configuration
Window containing : Events: displays events on local running actions Local Internal Processes: displays information on internal ASM processes Alarms: displays alarms
51

Actions menu
Engine configuration access
52
Manual Processing
Possibility to execute Cigale engine without ASM
- Execute Astellia.Tools.Engine.exe in Bin folder of the engine installation path.
Start processing
Local conf file
Engine progression and events

53
Cigale Gn Configuration (1/14)

4 different groups: Network Processing Inputs Outputs
Possibility to import/export .conf file

54
Network
- Topology:
Network prefix (usually OBS), check topology file - MANDATORY Topology file path - MANDATORY 2G/3G topology file path (for Cells/SAIs and RNCs/PCUs) - Optional Networks File Path MANDATORY
- Operator:
HPLM MCC (Only one MCC can be configured) HPLM MNC (Only one MNC can be configured) Home operator file: Possibility to configure several MCC or MNC
55
- TAC IMEI:
TAC IMEI file path: allow to translate TAC into Mobile Manufacturer and Mobile Type
56

Processing
- PSM module: Activate or deactivate - Enrichment: Activate or deactivate
Enrichment configuration for NEPTUNE
Cigale Gn and PSM Engine generate several BCK during the day. At the end of the day, a BIN file is generate with all PDP context still active. The day after, when the engine restart, this BIN files is loaded and all PDP active the day before are still present.
Cigale Gn Engine Enrichment contexts writing
BIN/ BCK
Admin only
CP Stream
PU1
Enrichment contexts reading Enrichment contexts writing

BIN/ BCK
Same configuration
PSM Engine
UP Stream
PU2
Enrichment contexts reading
- Backup file directory: destination directory of generated backup files - Period: Period of BCK generation
57

CP files (5min)
EDX
Enrichment configuration for OCEAN

Cigale Gn Engine
BIN/ BCK
Enrichment contexts writing
PU1 UP files (5min)

EDX
Enrichment contexts reading PU2
BCK periodicity should be lower or equal than EDX periodicity
PSM Engine
Cigale Gn Engine generate BCK files for enrichment.

Backup file directory: destination directory of generated backup files Period: Period of BCK generation Backup file directory: source directory for backup files. Period: must be none . Filtering equipment: allows one to retrieve only the backup file for a specific list of equipment. Equipment names must be the same as used in topology file ( node_name ).
PSM Engine load the BCK files generated by Cigale Gn Engine

-
58

RADIUS analysis
- RADIUS port list: Port used to analyze RADIUS protocol.
DIAMETER analysis
- DIAMETER port list: Port used to analyze DIAMETER protocol.

RADIUS and DIAMETER can be both activated
59

Processing
- Advanced Settings:
Settings to configure purges timeout of different procedures.
Please ask Astellia support before modifying these parameters.
- Partial Timers:
If Partial Timers is not selected, partial CDR will not be generated

60

Inputs
- Settings
Input: path to the capture files directory or capture file directly Input Server: IP address, port, login and password of Neptune Probe Analyser: .edx (Ocean), PCAP, .xcap (Neptune) Start/End Time: allow to process only a time range. Processing Timeout: used to limit the duration of processing
61

Inputs
- 2 Process Mode: Possibility to activate the feature
Online mode:
When activated, CIGALE Gn is waiting for EDX files on the directory specified in Settings/Input .
Expert only
Online timeout: Maximum time in seconds waiting EDX file before stopping Cigale Gn process Minimum remaining time polling: Minimum difference in seconds between the date of the last frame of the file processed by CIGALE Gn and the end time. Online flags: Extension of the flag files (example: flg for files.flg).
62

Inputs
Stream mode: Mode used with Neptune probes
63

Output
- Settings: name of the output database - Activity Analysis: activate the database generation
MySQL parameters Index generation
Features activation (Gi, incomplete PDP,)
Traces activation (detailed activity, fragmented IP messages,) Post process SQL queries configuration
64

Post process Queries
- If checked, post process queries are stored in the destination folder path.
Indexes T&A Statistics for AA
- What for?:
SQL Queries can be executed separtly from engine process - Need another ASM task: Post-process MySQL queries In case of abnormal end of processing. Queries can be executed even on a partial database.
65

Output
- Detailed Decoding: Activity Analysis can use Frame Extractor to visualize frames decoding. - Frame Archiving: The frame read can be archived into a directory (XCAP files) - View: Statistics for AA activation
- Stats Factory: Output data activation for stat factory
66

Output
- VIP Care:
VIP Care Server: IP address, port, login and password of VIP Care Server VIP Care Off Line: If no selected, the connection with VIP Care server can be attempt. VIP Care SDRs record path: When VIP Care Off Line is checked, this path is the location of the directory containing the SDRs. Ftp hostname for sdr file: FTP hostname used by VIP Care to retrieve SDR. Ftp folder path: Path of ftp server where the sdr files are stored.
- IMSI Filtering Activation: SDRs are selected before being sent to VIP Care Server.
Only with PSM Engine VIP Care Upload Path: Path containing the list of IMSI. ByPass: If selected SDRs defined in typebypass.txt are sent (event if IMSI is not tracked by VIP Care VIP Care SDR Type Bypass file: Type of SDR which are ByPassed by VIPCare
67
Gn State Machine (1/15)
Presentation - The state machine is configured by 4 external files (AUTOMAT.ADT, CAUSES.ADT, EVENTS.ADT, STATES.ADT) - They must be contained in the CIGALE execution directory when you start up the application. - These files must not be modified without authorization.
68

Automat.adt - The state machine is able to distinguish the different types of procedure (Tunnel management, Mobility) in order to trace mobile activity. - These states and transitions are contained in the AUTOMAT.ADT external file. - The events and causes are identified by names in the AUTOMAT.ADT file.
69
One transition is defined by: - An origin state - A final state - A message (event) with sometimes an associated cause Events are sometimes linked with an extension : - To indicate the sense of the message - To add a supplementary information
70

T-PDU_UL
CR_PDP_CTXT_REQ
CR_PDP_CTXT_RES
BEGIN
CR_PDP_ CTX_PENDING
PDP ACTIV
T_PDU
DEL_PDP_CTXT_REQ
MS leaves the SGSN DEL_PDP_ CTX_PENDING

SGSN_CTXT_REQ
DEL_PDP_CTXT_RSP
SGSN_CTXT_REQ
TUNNEL MANAGEMENT
BEGIN
MOBILITY MANAGEMENT
END
71

MOBILITY MANAGEMENT
SGSN_CTXT_REQ SGSN_CTXT_RES SGSN_CTXT_ACK
BEGIN
WAIT_SGSN_ CTX_RES
WAIT_SGSN_CTXT _ACK
END
At least one active

SGSN_CTXT_RES_PDP_ACTIVE
SGSN_CTXT_ACK
UPDT_PDP_CTXT_REQ
WAIT_SGSN_CTXT _ACK_PDP-ACTIVE
WAIT_INTER_ SGSN_TRX
END
TUNNEL MANAGEMENT
TIMER
WAIT_GGSN_ MOBILITY MANAGEMENT END UPDATE
72

TUNNEL MANAGEMENT (GGSN UPDATE)
UPDT_PDP_CTXT_REQ UPDT_PDP_CTXT_RESP
WAIT_GGSN_ UPDATE
UPDT_PDP_ CTX_PENDING
UPDT_PDP ACTIV
T_PDU
DEL_PDP_CTXT_REQ
MS leaves the SGSN UPDT_DEL_PDP_ CTX_PENDING

SGSN_CTXT_REQ
TUNNEL MANAGEMENT
SGSN_CTXT_REQ DEL_PDP_CTXT_RSP
BEGIN MOBILITY MANAGEMENT END
73

IDENTIFICATION MANAGEMENT
ID_REQ
ID_RES
BEGIN
WAIT_ID _RES
END
74

DNS MANAGEMENT
DNS_REQUEST
DNS_RESPONSE
BEGIN_DNS
WAIT_DNS _RESP
END_DNS
75

RADIUS MANAGEMENT
AUTHENTICATION ACCOUNTING
BEGIN_RADIUS
RADIUS_ACCESS_REQUEST
WAIT_RADIUS_ ACCESS_ACC
RADIUS_ACCESS_REJECT
RADIUS_ACCESS_ACCEPT
END_RADIUS
RADIUS_ACCOUNTING_REQUEST_START
RADIUS_ACCOUNTING_RESPONSE
RADIUS_ACCOUNTING_RESPONSE
RADIUS_ACCOUNTING_REQUEST_STOP
WAIT_RADIUS_ ACCOUNT_ RES_START RADIUS_ACCOUNT_A CTIVE
WAIT_RADIUS_ ACCOUNT_ RES_STOP 76

DIAMETER MANAGEMENT
WAIT_DIAM_CC_ RES_START
DIAMETER_CCA_Start
CREDIT CONTROL COMMAND (Gx/Gy)
DIAMETER_CCR_Start
DIAMETER_CCR_Upd
DIAMETER_CCA_Upd
BEGIN_DIAM
WAIT_DIAM_CC_ RES_UPD
DIAMETER_CCR_Upd
DIAM_CC_ACTIVE
DIAMETER_CCR_Stop DIAMETER_CCR_Stop
DIAMETER_CCA_Stop
WAIT_DIAM_CC_ RES_STOP
DIAM_CC_END
77

DIAMETER MANAGEMENT
WAIT_DIAM_ACCT_ RES_START
DIAMETER_ACA_Start
ACCOUNTING COMMAND (Gz)
DIAMETER_ACR_Start
DIAMETER_ACR_Upd
DIAMETER_ACA_Upd
BEGIN_DIAM
WAIT_DIAM_ACCT_ RES_UPD
DIAMETER_ACR_Upd
DIAM_ACCT_ACTIVE
DIAMETER_ACR_Stop DIAMETER_ACR_Stop
DIAMETER_ACA_Stop
WAIT_DIAM_ACCT_ RES_STOP
DIAM_ACCT_END
78

Events.adt, Causes.adt and States.adt - These files are then used to establish the correspondence between those names and the coded events and causes. - CAUSES.ADT file describes the names of the causes used by the state-machine. - EVENTS.ADT file describes the names of the events used by the state-machine. - STATES.ADT file describes the names of the state used by the state-machine
79

Events.adt
80

Causes.adt
81

States.adt
82
CDR Purges (1/4)
Purge End!
Purge Inactivity!
- Triggered on Gn, Gp and Gi interfaces
83
CDR Purges (2/4)

Purge Timeout!
No response from GGSN
Inter-SGSN Mobility
84
CDR Purges (3/4)
Purge NewTrans!
- Same TEID but another MS
Purge SGSNOut!
- PDP mobility
85
CDR Purges (4/4)

Purge NewRequest!
86
Partial CDRs (1/3)

Partial CDR on inactivity:
Only applied on CREATE procedure . By default, timeout partial CDR is 30 seconds. If 30 seconds after a CREATE Procedure, no message was exchanged, a Partial CDR on Inactivity is generated. If a new request (UPDATE/DELETE) is received before timer expiry, the partial CDR is generated
Partial CDR on activity:

Applied on UPDATE procedure. UPDATE Procedures are factorized and an activity partial CDR is periodically generated on timer expiry. By default, timeout activity partial CDR is 5 minutes. If a DELETE request is received, the partial CDR is generated without waiting timer expiry
87
Partial CDRs (2/3)

One example:
4 CDR generated: 1 CDR partial on inactivity : 30 seconds after the CREATE procedure. 2 CDR partial on activity : sum up of UPDATE procedures exchanged during 5 minutes. 1 CDR non partial : all procedure of PDP.
Partial 1 1 1 0 Start 05/01/2012 00:09:38 05/01/2012 00:21:58 05/01/2012 00:27:05 05/01/2012 00:09:38 End 05/01/2012 00:09:38 05/01/2012 00:26:06 05/01/2012 00:29:48 05/01/2012 00:34:57 1st Event CR_PDP_CTXT_REQ_V1 UPDT_PDP_CTXT_REQ_V1 UPDT_PDP_CTXT_REQ_V1 CR_PDP_CTXT_REQ_V1 Event CR_PDP_CTXT_RES_V1 UPDT_PDP_CTXT_RES_V1 UPDT_PDP_CTXT_RES_V1 DEL_PDP_CTXT_RES_V1 Cause V1_ReqAccept V1_ReqAccept V1_ReqAccept V1_ReqAccept 88
Partial CDRs (3/3)

Number UDPATE procedure are listed by CDR in Activity Analysis: Number Number Number Number Number Number UPDATE of UPDATE 2G to 3G mobility of UPDATE 3G to 2G mobility of UPDATE with SGSN changes of UPDATE with Direct Tunnel Flag of UPDATE with QoS changes. of UPDATE with no Direct Tunnel Flag (previous contained the DIRECT Tunnel Flag)
89
T&A Core PS (1/2)

Trending & Aggregation provides the following services:
Trending of the network performance over the time, Aggregation from a cell view to a consolidated view (per network element, region or network) Centralization and long term storage of information, Alarm generation, Reporting.
A Gb IuCs IuPs Iub
T&A server
Administration KPIs Browsing

90
T&A Core PS (2/2)

CIGALE Engine
.CPS files
Stat Factory
T&A Core PS
10 families of dashboards
PDP APN Mobility Roaming Roamout DNS RADIUS PDP Activation per NE Session Management per NE PDP Activation per APName Session Management per APName Inter SGSN Mobility Inbound Roamers Outbound Roamers DNS Performances RADIUS Performances Gi Session Management
91
PSM Overview (1/2)
PSM is a module for Cigale UMTS Iu (from release Iu3.2), Gn (from release Gn3.0) and Cigale GPRS Gb (from release Gb4.0) tools It offers the following features:
Decode and analyze protocols encapsulated in IP frame Provide through a state engine, statistics of normal/abnormal events that occurred to mobiles Provide metrics on traffic and transmission delays
PSM uses a specific automat for services in addition to Cigale engine automat It provides deep analysis for following services: HTTP, WAP, Email (POP3, SMTP), Streaming (RTSP, RTP/RTCP), MMS, DNS
92
PSM Overview (2/2)

New KPIs to monitor QoS and QoE of subscribers
Time to Connect Data access time Session Setup Time Volumes and throughputs for each subscriber activities TCP retransmission volume Statistics for AA based on PSM KPIs
- And much more !!!

93
Cigale Core PS
OSTILL - Fotolia
3 - Viewers
Objectives
At the end of the lesson the student will be able to:

- Describe Activity Analysis tables - Understand Gn KPIs - Understand AA main functionalities and how to use them efficiently
95
Overview
AA is a MySQL database viewer
- Where : On each probe and user PC - When : After Cigale Gn process - can be used also next to other Cigale engine (GSM, UMTS, Core CS...) - Why : To create a database and visualise results thanks to a graphical user interface that helps investigation - How : created during the Cigale Gn engine process
Activity Analysis Cigale engine Significant statistics High detail level investigation and analysis
96
Overview
AA connection 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)
97
Overview
Gn database could be composed of 5 different tables depending on processing configuration: Cigale Gn PSM
Activity Report: provides summary of a procedure (PDP Context creation...) through a Call Data Record (CDR) XL3 table Detailed Activity: gives information on all subscribers activity during the capture period Services Activity: provides summary of a service session between one client and one server through Packet Services Data Record (PSDR) IP Activity: gives information on every client/server transaction (1 request and 1 response) through Internet Protocol Data Record (IPDR) Internet protocol: gives information on all captured IP data frames
98
Activity Analysis tables (1/3)

Activity Report
Following information are available from this table:

Subscriber identification: IMSI, MSISDN Source/Destination node (GSN/server): @IP, port number PDP information: APN, QoS parameters, PDP Id Mobility information: old LAC, old RAC, old PTMSI Traffic information: User payload (IP traffic over GTP), total Gn traffic (user plane + signalling) and IP Gi traffic
99

Detailed Activity
Following information are available:

Subscriber identification: IMSI, MSISDN Source/Destination node (GSN/server): @IP, port number Frame information: frame number, GTP sequence number, message direction, frame length
100

Services Activity IP Activity Internet Protocol PSM tables (need activation)
Following information are available: - Mobile identification: IMSI, MSISDN, MS @IP, MS port number - Source/Destination node (GSN/server): @IP, port number - Service: APN, requested URL, protocol, service - Traffic: volume, throughput, TCP/WTP retransmissions - Connection delays: Time to connect, reply peer delay, setup delay - Procedure efficiency: sent/received objects ratio, response ratio -
101
Toolbar options (1/3)

Filtering and sorting tools
The tool bar contents could vary depending on the selected view
Close the current window Go to the top / bottom of the view Zoom In / Out Export to Excel or in text file format (.txt) Go to Activity report Go to Detailed Activity Go to Services Activity Go to IP Activity
102
Flow Chart Display the number of different elements in the active column Multi interfaces Protocol decoding Export selected xDR to an EDX or XCAP file
Find Next Record/Find Previous Record
103
Increasing order / decreasing order / No order Apply a filter equal, different, lower than the active cell Cancel the filter of the active column / all filters / the last filter Advanced filter (you can use * as wildcard or NULL)
Filter with several value button Filters Display the filter palette
Filter palette Detail of the active filters in the current view The filter can be saved and loaded. It is possible to lock filter.
104
Activity Analysis
Current use of the CDR Viewer
The CDR viewer allows to filter some activities on all the columns. For instance, filter on all the PDP Context Activation Sorting by decreasing DL volume
&
105
AA Main features
Activity Analysis is a powerful investigation tool that enables a deep troubleshooting Some features get easier this troubleshooting - Navigation - CDR Type - UE Call Trace - Distribution function - Preset filters - Flow Chart - Decoding - Multi-interface - Statistics for AA - Global tracing
106
Navigation
Depending on the active table you have selected, by right clicking on a line you can navigate between the different tables to follow subscriber activity
Detailed Activity Transitions Activity Report
IP Activity
Services Activity
PSM tables
107
CDR Type
To analyze more easily subscribers activity through Activity Report, each CDR is summed up in Type column
This type indicates during which procedure it has ended and why
All transitions from activity reports are tagged with a specific color.
Green color normal end tunnel transition Blue color inter SGSN procedure Navy color normal end DNS transition Purple color normal end RADIUS/DIAMETER transition Black color transaction Purge Olive color failure no response or user inactivity Grey color ICMP v6 Red color abnormal end: reject
108
Distribution function
It enables to display the number of different elements in the active column in table or chart format Additional criteria could be added with
109
Preset filters
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.
110
Preset filters
Preset creation
Create a group select it, then right click and select save as preset
111
Flow Chart (1/2)

It enables to follow easily the activity of a subscriber (CDR) through the message exchanged on Gn interface between GSN nodes:
Flow Chart for the selected connection either on signalling frames or on all signalling and data frames. Flow Chart for the entire PDP/Call Id Flow Chart of the selected connection with same options (signalling or signalling & data).
112
Flow Chart (2/2)

It can be launched from Activity Report or Detailed Activity
The arrow indicates the event that ended the CDR (Last Event)
113
Decoding (1/3)
In Activity Report, Services Activity or IP Activity, when a line is selected (CDR, PSDR or IPDR), the user can decode all associated frames by clicking on icon
3 options are proposed

Decode signalling: only signalling messages would be decoded (Create PDP Context Request...) Decode signalling & user plane: signalling messages + user plane messages on Gn interface would be decoded (HTTP request, MMS message...)
Option Insert frames into CDR must be activated (GEN_CDR_FRAMES=1 in CIGALE.INI)

114
Decoding (2/3)
User can also decode frames from flow chart by right-clicking on one arrow
Or from Detailed Activity user can decode one selected frame or all frames
115
Decoding (3/3)
Decoding window example
Possibility to export these frames in a pcap file Signalling frames
User frames
User can expand each layer to see protocol decoding
116
Multi-interface (1/2)
When analyzing one issue on Gn interface you may want to go further and follow subscriber activity on Gb or Iu interface
you need to have correlated databases
You can visualize the activity of the selected UE in table mode...
117
Multi-interface (2/2)
...or in flow chart mode (Iu/Gn example)
118
Statistics for AA
KPI statistics integrated in AA
Statistics for AA Criteria Selection
Max values displayed and bitmap export View Selection
Graphical View
Sorting and filtering
Grid export
Grid View
119
Global Tracing (1/2)

Optional module for AA
Find activities of one IMSI or IMEI over:

- Multiple sites - Multiple interfaces/technologies - For a defined date or time range
Filter, sort, distribute for further investigation

120
Global Tracing (2/2)

Databases status Searched IMSI/IMEI
Select Date/Time range
Selected databases
Selected interfaces
Found CDRs
121
Exercises
1. Filter on PDP Context creation. Display all termination event/cause. Which ones are abnormal? Filter on PDP Context creation for blackberry service. Display all termination event/cause. What is the meaning of termination cause Timeout! ? Why does it appear? Filter on CR_PDP_CTXT_RES_V1/V1_UserAuthFail. What is the origin of this reject? Create a preset to view only PDP context reject for cause V1_UserAuthFail Select one IMSI that failed PDP Context creation with UserAuthFail. What is the whole activity done by this subscriber.
2.
3.
4. 5.
122
Exercises
6. Select one PDP session with enough DL volume traffic. Which kind of traffic is it? WAP, HTTP...? (PSM needed) What is the meaning of reject cause V1_AllDynAddrOcc Filter on inter-SGSN RAU procedures with at least 1 session running. Which kind of information is transferred from old SGSN to new SGSN. How many PDP is running? How many authentication key is transferred? Find all traffic sessions with at least 300 Kbytes of UL volume. Find those with packets lost over Gi interface.
7. 8.
9.
10. Find one successful RADIUS transaction. Which information is given by RADIUS server on RADIUS_ACCESS_ACCEPT event?
123
Thank you
124
Astellia Support
Tel: Email:
+33 (0) 2 99 04 80 66 support@astellia.com

125

5 CigaleCorePS Basics V52 ATS RA Student

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

5 CigaleCorePS Basics V52 ATS RA Student

Hochgeladen von

Copyright:

Verfügbare Formate

Cigale Core PS

Astellia Core PS Solution Architecture

Results consolidation Operators Information system

Data viewing and reporting

QoS management Performance analysis Network optimization Troubleshooting SLA management

PCRF DNS Server Foreign PLMN Gx Gy

Charging online Charging offline

There are two kinds of PDP contexts.

Quality of Service (QoS) parameters:

Gn/Gp Protocol Stack

Gn/Gp Messages (1/5)

[2] Tunnel management messages

[3] Mobility management messages

Location management messages (optional)

Gn/Gp interfaces [4] T-PDU

Gn/Gp Messages (2/5)

Gn/Gp Messages (3/5)

Gn/Gp Messages (4/5)

Gn/Gp Messages (5/5)

Main procedures (1/5)

Main procedures (2/5)

Deactivate PDP context request Delete PDP context request

Delete PDP context response Deactivate PDP context response

Main procedures (3/5)

Main procedures (4/5)

Main procedures (5/5)

SNDCP-PDU {TLLI, NSAPI, PDP-PDU}

GTP-PDU {TID, PDP-PDU} PDP-PDU

SNDCP-PDU {TLLI, NSAPI, PDP-PDU}

Network Configuration (1/5)

Network Configuration (2/5)

Network Configuration (3/5)

Network Configuration (4/5)

Network Configuration (5/5)

IP 2 port 2123 IP 3 port 2123 IP 2 port 2123 IP 3 port 2123

Direct Tunnel (1/4)

Direct Tunnel (2/4)

Control Plan User Plan

With Direct Tunnel

GTP-U Direct Tunnel

Direct Tunnel (3/4)

Control Plan User Plan

GTP-U Direct Tunnel

Direct Tunnel (4/4)

RAB Assignment Response Update PDP Context Request

Update PDP Context Response Activate PDP context accept

SGSN sends a DNS Request with an APName

DNS server answers back with GGSN IP address associated to APName.

Create PDP context request

DNS Network vs. DNS User

PDU DNS Query

RADIUS Protocol (1/3)

RADIUS Protocol (2/3)

Optional (depends on operator configuration)

RADIUS Protocol (3/3)

Create PDP context request RADIUS Access-Request

DIAMETER Protocol (1/3)

DIAMETER Protocol (2/3)

Subscription Profile Repository

Policy and Charging Rules Function

Offline Charging System

DIAMETER Protocol (3/3)

Create PDP context request