5 CigaleCorePS Basics V52 ATS RA Student (2)

© O

STI

LL-F

otol

iaCustomer Logo:

Title:Font size: 40 ptsFont color: Grey51, 51)Font: VerdanaPosition: Left

Font size: 24 ptsFont color: Orange (RVB: 255, 102, 0)Font: VerdanaPosition: Left

Cigale Core PS1 - Basics

Title:

Font size: 36 ptsFont color: WhiteFont: VerdanaPosition: Centered

Content:

1st Level font size: 20 pts2nd Level font size: 18 pts3rd –

Font color: Grey51)Font: VerdanaPosition: Left

Word highlight: Orange255, 102, 0) + Bold

Bullet color: Orange102, 0)

Astellia confidential2

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 networkconfigurations

- Understand differences between DNS Network and DNS User

- Understand Direct Tunnel procedure

Title:


Content:






Astellia Core PS SolutionArchitecture

Data viewing and reportingReporting and alarming on Webbrowser for all teamsDedicated investigation tools forexperts

QoS managementPerformance analysisNetwork optimizationTroubleshooting

SLA management

Operator’s Information systemExport of statistics, reports, alarms

Data acquisition24h/24 raw data captureGn, Gp, DNS, RADIUS, GiGx/Gy/Gz

Data processingOn-line CDR generationPeriodic KPI generation

Results consolidationNetwork-wide informationKPI trending

System managementProcess flow automationSystem administrationSystem supervision

Engines Databases

Centraldatabase

Site 1

Probes

Site 2

Title:


Content:





Astellia confidential

Core PS architecture

4

GGSN

Internet

Gb

Gr

Gn Gi

HLR

PCU

SGSN

Gn

Abis

BTS

Iu-PSRNCIub

NodeB

GpInbound

GpOutbound

Foreign PLMNForeign PLMN

GGSN

Foreign PLMNForeign PLMN

SGSN

DNSServer

RADIUSServer

PCRFCharging

online

Chargingoffline

Gx GyGz

DIAMETERDNS

interface

RADIUSinterface

Title:


Content:






Protocol Stack

Server /GatewayGi

GSM RF

RLC

MAC

LLC

SNDCP

IP

MS SGSN GGSNBSS

GSM RF L1bis

RLC

MACNetworkservice

BSSGP

Relay

Um Gb Gn/Gp

L1bis L1

Networkservice

BSSGP

LLC

SNDCP

L2

IP

UDP/TCP

GTP

Relay

L1

L2

IP

UDP/TCP

Application

L1

L2

IP

UDP/TCP

GTP

L1

L2

UDP/TCP

Application

Title:


Content:






PDP Context

PDP: Packet Data Protocol

• Information stored in MS, SGSN, GGSN to allow data exchanged with PDPnetwork

- 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 contextsmay have different Quality Of Service settings.

• A total of 11 PDP contexts (with any combination of Primary andSecondary) can co-exist.

Title:


Content:






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 priorityshall be maintained ahead of other ones.

- Delay class (4 classes): indicates the transmission duration of one packetthrough 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.

Title:


Content:






TEID

Tunnel principle

(Core Network)

GGSN

Core PS part

SGSN

TEID: Tunnel endpoint Identifier

Internet

Tunnel CP UL

Tunnel CP DL

Tunnel Data UL

Tunnel Data DL

GTP Tunnel

Title:


Content:






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

Title:


Content:






GTP V1: IPV4 or IPV6

GTP V0: IPV4

SMTPPOP3

MMS HTTPWAP FTPDNS RTSP

… …

IP

UDP TCP

GTP

L1

IP

UDP

UDP is the mandatory protocol

• GTP V0: UDP ports 3386 (ControlPlane and User Plane)

• GTP V1: UDP ports 2123 (ControlPlane) and 2152 (User Plane)

Gn/Gp Protocol Stack

Applicative layers

Title:


Content:






[1] Path management messages

[2] Tunnel management messages

[3] Mobility management messages

[4] T-PDU

Gn/Gp interfaces

GTP-C

GTP-U

Gn/Gp Messages (1/5)

GSN GSNLocation management messages (optional)

Title:


Content:






• [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)


Title:


Content:






• [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 inter-system mobility

• Update PDP Context Request / Update PDP Context Response

- If the GGSN receives a PDU for a not connected PDP, it will try tocreate it (Network-requested PDP Context Activation procedure) inorder to deliver its PDU

• PDU Notification Request/Response/Reject Request/RejectResponse


Title:


Content:






• [MOBILITY MANAGEMENT]

Mobility Management messages are control plane messages sentbetween 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 CompleteACK, Forward SRNS Context, Forward SRNS Context ACK,Relocation Cancel Request, Relocation Cancel Response


Title:


Content:






• [USER PLANE]

Send and Receive PDU

- Only one message for Uplink and Downlink

- T-PDU


Title:


Content:






• PDP Context Activation Procedure

Activate PDP context request

Security functions

Create PDP context request

Create PDP context response

Activate PDP context accept

Main procedures (1/5)

SGSN GGSN

Title:


Content:






• PDP Context Deactivation Procedure


SGSN GGSN

Deactivate PDP context request

Delete PDP context request

Delete PDP context response

Deactivate PDP context response

Title:


Content:






• Inter-SGSN Routing Area update with PDP active

RA Update requestSGSN context request

RA Update response

SGSN context response

Update PDP context request

Update PDP context response

SGSN context acknowledge


NewSGSN GGSN

OldSGSN

Title:


Content:






• 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 previousUpdate PDP Context Request contained Direct Tunnel Flag.

- Inter SGSN mobility: New SGSN IP address.


Title:


Content:






• Sending and receiving PDUs

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

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

SNDCP GTP

GTP-PDU{TID, PDP-PDU}

GTP-PDU{TID, PDP-PDU}

PDP-PDU{PDP address}

IP

PDP-PDU


ExternalIP network

SGSN GGSN

Title:


Content:






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.

Title:


Content:







• Different ways to implement the network- Main case:



SGSN GGSN



IP 1 – port 2123 IP 2 – port 2123

Title:


Content:







- Random SGSN port number



SGSN GGSN



IP 1 – random port IP 2 – port 2123

Title:


Content:







- IP per type of procedure



SGSN GGSN



IP 1

2123 or random port

IP 2 – port 2123

IP 3 – port 2123

Title:


Content:







- IP per type of message (Request vs. Response)



SGSN GGSN



IP 1

2123/random port

IP 2 – port 2123

IP 3 – port 2123

IP 3 – port 2123

IP 2 – port 2123

Title:


Content:






• 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)

3GPP Release 7

Title:


Content:






• « Flat architecture »: ready for LTE networks.

• Reduce cost for operators.

• User data traffic routed directly from the radio accessnetwork to the core network’s Internet gateway node.

• Bypass the control node (the Serving GPRS ServiceNode, the SGSN) through which data traffic is routed inexisting networks.

• UMTS feature only.

Direct Tunnel (1/4)

Title:


Content:






GTP-U Direct Tunnel

Direct Tunnel (2/4)

Radio part

(GTP-U)

SGSNRNC GGSN

IPNetwork

IPNetwork

Control Plan

User Plan

(GTP-U)

(RANAP) (GTP-C)

• Without DirectTunnel

Radio part

SGSN

RNC GGSN

IPNetwork

IPNetwork

• With DirectTunnel (RANAP) (GTP-C)

Iu-PS Gn

Title:


Content:






GTP-U Direct Tunnel

Direct Tunnel (3/4)

Radio part

(GTP-U)

RNC 1Control Plan

User Plan

(GTP-U)

(GTP-C)

• Direct Tunnel used in only some RNCs

Radio part

SGSN

RNC 2

GGSN

IPNetwork

IPNetwork

(RANAP)

Title:


Content:






Direct Tunnel (4/4)

• Direct Tunnel EstablishmentSGSN

Activate PDP Context RequestCreate PDP Context Request

Create PDP Context Response

Activate PDP context accept

RNC GGSN

RAB Assignment Request(GGSN TEID, GGSN User Traffic Address)

Update PDP Context Request(DTI flag, RNC TEID, RNC User Traffic Address)

Update PDP Context Response

RAB Assignment Response

GTP-U

Title:


Content:






• 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 (AccessPoint Name).

- IP address can be an IPv4 or IPv6 address.

DNS Network

DNSNetwork

DNS Query

DNS Response

SGSN GGSN_x


APName

IP GGSN_x

SGSN sends aDNS Request with

an APName

DNS server answersback with GGSN IP

address associated toAPName.

Title:


Content:






DNS Network vs. DNS UserDNS

Network DNS User

www.google.com

DNS Query

DNS Response

SGSN GGSN_x

APN: internet


Service request

Create PDP context responsePDP Act. Complete

PDU PDU

internet

IP GGSN_x

DNS Querywww.google.com

DNS ResponsePDU

PDU IP Google

IP Google

www.google.com

Title:


Content:






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 durationbetween RADIUS_ACCOUNTING_START and RADIUS_ACCOUNTING_STOP)

• RADIUS headers format (request and response are associated through @IP src/dest, UDPport number and Packet identifier)

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

---

Attributes

Code Identifier LengthAuthenticator

Bit

Title:


Content:






RADIUS Protocol (2/3)

• RADIUS architecture

Database

- 1 request could be forwarded to several servers but only the first responsewould be taken

RADIUSserver 1

RADIUS serveror proxy

RADIUSserver N

RADIUSserver 2

Optional (depends onoperator configuration)

GGSN AccessServer

Title:


Content:






RADIUS Protocol (3/3)RADIUSServerSGSN GGSN_x



RADIUS Access-RequestAPName

RADIUS Access-AcceptMobile IP address

RADIUS Accounting-Request (Start)

RADIUS Accounting-Response (Start)



RADIUS Accounting-Request (Stop)

RADIUS Accounting-Response (Stop)

Title:


Content:






DIAMETER Protocol (1/3)

• DIAMETER is a protocol used for Authentication, Authorization and Accounting. It is analternative to RADIUS.

• A DIAMETER frame consists of a Diameter header and a variable number of Attribute-Value Pairs (AVP) for encapsulating information relevant to the Diameter message.

Title:


Content:







• DIAMETER Overview

Gy

SubscriptionProfile

Repository

(SPR)

Rx

ApplicationFunction

(AF)

Sp

Gx

Policy andCharging

EnforcementFunction

(PCEF)

Policy andCharging Rules

Function

(PCRF)

Online ChargingSystem

(OCS)

Service Data FlowBased Credit

Control

Gxx

Bearer Bindingand EventReportingFunction

(BBERF)

PDN-GatewayAN-Gateway

Gz

OfflineChargingSystem

(OFCS)

• The Gx reference point enables a PCRF to have dynamic control over the PCC behaviorat 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.

Title:


Content:







DIAMETERServerSGSN GGSN_x



DIAMETER Credit-Control-RequestInitial Request

DIAMETER Credit-Control-AnswerInitial Request

Update PDP context request

Update PDP context response

DIAMETER Credit-Control-RequestUpdate Request

DIAMETER Credit-Control-AnswerUpdate Request



DIAMETER Credit-Control-RequestTermination Request

DIAMETER Credit-Control-AnswerTermination Request

Title:


Content:






Gi Protocols

MMS

DNSWTP

WSP

RTPRTCP

UDP TCP

FTP SMTP POP3HTTP RTSP

L1L2

IP

ICMP

L1L2

UDP/TCP

Application

IP

TCP/IP Model

• Applications

© O

STI

LL-F

otol

iaCustomer Logo:



Cigale Core PS2 - Engine

Title:


Content:







- Describe Cigale Gn Engine (input/output files)

- Understand the different part of user interface and mainparameters of Cigale configuration

- Understand Cigale Gn state machine

Objectives

Title:


Content:






Probe Capture on Gn, Gp, Gi, Gx, Gy or Gz(Ocean, Neptune, K12, Nethawk, Libcap…)

Cigale Gn engine

Activity Analysis

High detail levelinvestigation and analysis

(Troubleshooting)

Overview (1/4)

Title:


Content:






• Cigale Gn can be described as a "spy" located at level of theGn/Gp/Gi/Gx/Gy/Gz interfaces, between GSNs (SGSNs andGGSNs) and toward IP Network

• With Packet Services Monitoring (PSM) option, user can follow asession 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.

Overview (2/4)

Title:


Content:






Overview CorePS 5.2Neptune (3/4)

44

NB: PSM Engine =Cigale Gn + PSM option

NEPTUNEProbe

T&A Core PS(sig hourly

+PSMhourly)

XCAP

FaultManager

VIP Care

T&A HPG

UsageAnalytics

HPG

StatFactory

StatFactory

PSMEngine

CigaleEngineStream (CP

only)

Tuples (periodic IP links+ APN statistics)

TCPD

R (

TCP/

UD

Pse

ssio

n su

mm

arie

s)

AA (IPDR,PSDR) + VIA

AA (CDR)+ VIA

Stream

.XLP file

Textfiles

Stream

.HPG file

.CPS files

.NPS files

Title:


Content:






Overview CorePS 5.2Ocean (4/4)

45

NB: PSM Engine =Cigale Gn + PSM option

NB: PSM Engine = Cigale Gn + PSM option

T&A Core PS(sig hourly

+PSMhourly)

OceanProbe

Enrich

men

t fil

es(B

IN/B

CK)

FaultManager

VIP Care

T&A HPGHPG

StatFactory

PSMEngine

CigaleEngine

AA (IPDR,PSDR) + VIA

AA (CDR)+ VIA

Stream

.XLP file

Textfiles

Stream

.HPG file

.CPS files

EDX

EDX

Capture files(CP only)

Capture files(UP only)

Title:


Content:






Cigale GnConfiguration file

Other files :IP2country.txt, TAC.txt,

networks.txtCapture file :EDX (OCEAN)XCAP (NEPTUNE)PCAP (TCPDUMP, ETHEREAL)

Input files

Description of the network topologyGSN, DNS, RADIUS, DIAMETER topology.txt,

2G – 3G topologyDescription of the State MachineAUTOMAT, EVENTS,CAUSES,STATES

Title:


Content:






• Overview

- This file is used when processing record files to name thedetected 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 Gnconfiguration.

Topology file (1/2)

Title:


Content:






• IP@ range for SGSN, GGSN, DNS, RADIUS and DIAMETERThis file provides the possibility to assign explicit names to GSNs

as well as for DNS/RADIUS/DIAMETER servers …

Topology file (2/2)

If DNS/RADIUS/DIAMETERservers are not filled, noCDR would be generated

… Because there is no possibility at all to discoverautomatically the network topology

Title:


Content:






• IP2country.txt

• The file IP2country.txtprovides a description of IPaddresses allocated percountry

Useful to automatically assign names to GSNs when no description isprovided (no GSN description file available or incomplete description)

IP2country

Title:


Content:






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

Title:


Content:






ASM Integration (2/3)Network treestructure

Window containing :• Events: displays events

on local running actions• Local Internal

Processes: displaysinformation on internalASM processes

• Alarms: displays alarms

TasksAccess to tasksconfiguration

Title:


Content:






ASM Integration (3/3)

« Actions » menu

Engineconfigurationaccess

Title:


Content:






Manual Processing

• Possibility to execute Cigale engine without ASM

- Execute Astellia.Tools.Engine.exe in Bin folder of the engineinstallation path.

Start processing

Local conf file

Engine progressionand events

Title:


Content:






Cigale Gn Configuration (1/14)

4 differentgroups:

• Network

• Processing

• Inputs

• Outputs

Possibility to import/export .conf file

Title:


Content:







• 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

Title:


Content:







- TAC – IMEI:

• TAC – IMEI file path: allow to translate TAC into Mobile Manufacturerand Mobile Type

Title:


Content:






• Processing- PSM module: Activate or deactivate- Enrichment: Activate or deactivate

• Enrichment configuration for NEPTUNECigale Gn and PSM Engine generate several BCK during the day. At the end of theday, a BIN file is generate with all PDP context still active. The day after, whenthe engine restart, this BIN files is loaded and all PDP active the day before arestill present.

- Backup file directory: destination directory of generated backup files- Period: Period of BCK generation

57


Adminonly

Sameconfiguration

CP Stream

UP Stream

Cigale GnEngine

BIN/BCK

Enrichmentcontexts writing

PU1Enrichmentcontexts reading

PSM Engine

BIN/BCK


PU2Enrichmentcontexts reading

Title:


Content:






• Enrichment configuration for OCEAN

• Cigale Gn Engine generate BCK files for enrichment.- Backup file directory: destination directory of generated backup files- Period: Period of BCK generation

• PSM Engine load the BCK files generated by Cigale Gn Engine- 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 »).


BCK periodicity shouldbe lower or equal thanEDX periodicity

EDX

EDX

CP files(5min)

UP files(5min)

PSM Engine

PU2

Cigale GnEngine

BIN/BCK


PU1Enrichmentcontextsreading

58

Title:


Content:






• 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

Title:


Content:






• Processing- Advanced Settings:

- Partial Timers:


Settings to configure purges timeout ofdifferent procedures.

Please ask Astellia support beforemodifying these parameters.

If Partial Timers is not selected, partial CDR will not be generated

Title:


Content:






• 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


Title:


Content:






• Inputs- 2 Process Mode: Possibility to activate the feature

• Online mode:

When activated, CIGALE Gn is waiting for EDX files on thedirectory specified in « Settings/Input ».

• Online timeout: Maximum time in seconds waiting EDX file beforestopping Cigale Gn process

• Minimum remaining time polling: Minimum difference in secondsbetween the date of the last frame of the file processed by CIGALEGn and the end time.

• Online flags: Extension of the flag files (example: “flg” for“files.flg”).


Expertonly

Title:


Content:






• Inputs• Stream mode: Mode used with Neptune probes


Title:


Content:






• 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 queriesconfiguration

Title:


Content:






• Post process Queries

- If checked, post process queries are stored in the destinationfolder 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.


Title:


Content:






• Output- Detailed Decoding: Activity Analysis can use

Frame Extractor to visualize frames decoding.

- Frame Archiving: The frame read can be archived into adirectory (XCAP files)

- View: Statistics for AA activation

- Stats Factory: Output data activation for stat factory


Title:


Content:






• 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 VIPCare Server.

• 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


Only with PSM Engine

Title:


Content:






• 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 directorywhen you start up the application.

- These files must not be modified without authorization.

Gn State Machine (1/15)

Title:


Content:






• Automat.adt

- The state machine is able to distinguish the different types ofprocedure (Tunnel management, Mobility) in order to tracemobile activity.

- These states and transitions are contained in theAUTOMAT.ADT external file.

- The events and causes are identified by names in theAUTOMAT.ADT file.


Title:


Content:






• 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


Title:


Content:







BEGINCR_PDP_

CTX_PENDING

CR_PDP_CTXT_REQ

DEL_PDP_CTX_PENDING

CR_PDP_CTXT_RES

T_PDU

DEL_PDP_CTXT_REQ

DEL_PDP_CTXT_RSP

BEGINTUNNEL MANAGEMENT

MOBILITY MANAGEMENT

PDP ACTIV

SGSN_CTXT_REQ

END

SGSN_CTXT_REQ

MS leaves the SGSN

T-PDU_UL

Title:


Content:







BEGINWAIT_SGSN_

CTX_RESWAIT_SGSN_CTXT

_ACK

SGSN_CTXT_REQ SGSN_CTXT_RES

WAIT_INTER_SGSN_TRX

END

TIMER

MOBILITY MANAGEMENT

END

SGSN_CTXT_ACK

SGSN_CTXT_RES_PDP_ACTIVE

WAIT_SGSN_CTXT_ACK_PDP-ACTIVE

SGSN_CTXT_ACK

END

UPDT_PDP_CTXT_REQ

WAIT_GGSN_

UPDATE

TUNNEL MANAGEMENT

MOBILITY MANAGEMENT

At least oneactive

Title:


Content:







WAIT_GGSN_

UPDATEUPDT_PDP_

CTX_PENDING

TUNNEL MANAGEMENT(GGSN UPDATE)

UPDT_PDP_CTXT_REQ UPDT_PDP_CTXT_RESP

UPDT_DEL_PDP_CTX_PENDING

T_PDU

DEL_PDP_CTXT_REQ

BEGIN

UPDT_PDP ACTIV

SGSN_CTXT_REQ

END

SGSN_CTXT_REQ

MS leaves the SGSN

TUNNEL MANAGEMENT

MOBILITY MANAGEMENT

DEL_PDP_CTXT_RSP

Title:


Content:







BEGINWAIT_ID

_RES END

IDENTIFICATION MANAGEMENT

ID_REQ ID_RES

Title:


Content:







BEGIN_DNS WAIT_DNS_RESP

END_DNS

DNS MANAGEMENT

DNS_REQUEST DNS_RESPONSE

Title:


Content:







RADIUS MANAGEMENT AUTHENTICATION ACCOUNTING

RADIUS_ACCOUNTING_REQUEST_STOPRADIUS_ACCOUNTING_RESPONSE

BEGIN_RADIUSWAIT_RADIUS_ACCESS_ACCRADIUS_ACCESS_REQUEST

RADIUS_ACCESS_ACCEPT

WAIT_RADIUS_

ACCOUNT_

RES_START

RADIUS_ACCOUNT_ACTIVE

END_RADIUS

WAIT_RADIUS_

ACCOUNT_

RES_STOP

RADIUS_ACCOUNTING_REQUEST_START

RADIUS_ACCESS_REJECT

RADIUS_ACCOUNTING_RESPONSE

Title:


Content:






DIAMETER_CCR_Upd


77

DIAMETER_CCR_Upd

DIAMETER_CCR_Stop

DIAMETER_CCR_Start

BEGIN_DIAM

WAIT_DIAM_CC_

RES_START

WAIT_DIAM_CC_

RES_UPD

DIAMETER_CCA_Start

DIAMETER_CCA_UpdDIAM_CC_ACTIVE

WAIT_DIAM_CC_

RES_STOP

DIAMETER_CCA_Stop

DIAM_CC_END

DIAMETER_CCR_Stop

DIAMETER MANAGEMENTCREDIT CONTROL COMMAND (Gx/Gy)

Title:


Content:






DIAMETER_ACR_Upd


78

DIAMETER_ACR_Upd

DIAMETER_ACR_Stop

DIAMETER_ACR_Start

BEGIN_DIAM

WAIT_DIAM_ACCT_

RES_START

WAIT_DIAM_ACCT_

RES_UPD

DIAMETER_ACA_Start

DIAMETER_ACA_UpdDIAM_ACCT_ACTIVE

WAIT_DIAM_ACCT_

RES_STOP

DIAMETER_ACA_Stop

DIAM_ACCT_END

DIAMETER_ACR_Stop

DIAMETER MANAGEMENTACCOUNTING COMMAND (Gz)

Title:


Content:






• Events.adt, Causes.adt and States.adt

- These files are then used to establish the correspondencebetween those names and the coded events and causes.

- CAUSES.ADT file describes the names of the causes used bythe state-machine.

- EVENTS.ADT file describes the names of the events used by thestate-machine.

- STATES.ADT file describes the names of the state used by thestate-machine


Title:


Content:






• Events.adt


Title:


Content:






• Causes.adt


Title:


Content:






• States.adt


Title:


Content:






CDR Purges (1/4)

• Purge End!

• Purge Inactivity!- Triggered on Gn, Gp and Gi interfaces

Title:


Content:






CDR Purges (2/4)

• Purge Timeout!

Inter-SGSNMobility

No response from GGSN

Title:


Content:






CDR Purges (3/4)

• Purge NewTrans!- Same TEID but another MS

• Purge SGSNOut!- PDP mobility

Title:


Content:






CDR Purges (4/4)

• Purge NewRequest!

Title:


Content:






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

Title:


Content:






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 Start End 1st Event Event Cause

1 05/01/2012 00:09:38 05/01/2012 00:09:38 CR_PDP_CTXT_REQ_V1 CR_PDP_CTXT_RES_V1 V1_ReqAccept

1 05/01/2012 00:21:58 05/01/2012 00:26:06 UPDT_PDP_CTXT_REQ_V1 UPDT_PDP_CTXT_RES_V1 V1_ReqAccept

1 05/01/2012 00:27:05 05/01/2012 00:29:48 UPDT_PDP_CTXT_REQ_V1 UPDT_PDP_CTXT_RES_V1 V1_ReqAccept

0 05/01/2012 00:09:38 05/01/2012 00:34:57 CR_PDP_CTXT_REQ_V1 DEL_PDP_CTXT_RES_V1 V1_ReqAccept

Title:


Content:






Partial CDRs (3/3)

• Number UDPATE procedure are listed by CDR in Activity Analysis:

• Number of UPDATE 2G to 3G mobility• Number of UPDATE 3G to 2G mobility• Number of UPDATE with SGSN changes• Number of UPDATE with Direct Tunnel Flag• Number of UPDATE with QoS changes.• Number of UPDATE with no Direct Tunnel Flag (previous

UPDATE contained the DIRECT Tunnel Flag)

Title:


Content:






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.

IuPsIuCsGbA Iub

T&A server

KPIs Browsing

Administration

Title:


Content:






T&A Core PS (2/2)

• 10 families of dashboards

CIGALEEngine Stat Factory T&A Core PS

- 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

.CPS files

Title:


Content:






PSM – Overview (1/2)

• PSM is a module for Cigale UMTS Iu (from release Iu3.2), Gn (from releaseGn3.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 engineautomat

• It provides deep analysis for following services: HTTP, WAP, Email (POP3,SMTP), Streaming (RTSP, RTP/RTCP), MMS, DNS

Title:


Content:






• 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 !!!

PSM – Overview (2/2)

Title:


Content:







- Describe Activity Analysis tables

- Understand Gn KPIs

- Understand AA main functionalities and how to use themefficiently

Objectives

Title:


Content:






• 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

Cigale engineSignificant statistics

Activity Analysis

High detail level investigationand analysis

Overview

Title:


Content:






• AA connection

Connection to MySQL server

The server can be the localmachine (Localhost) or a distantconnected server.

Default port is 3306

Two logins :Cigale : all rights (pwd : astellia)Analysis : read only (no pwd)

Overview

Title:


Content:






• Gn database could be composed of 5 different tables depending onprocessing configuration:

- 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 captureperiod

- Services Activity: provides summary of a service session between one client andone server through Packet Services Data Record (PSDR)

- IP Activity: gives information on every client/server transaction (1 request and 1response) through Internet Protocol Data Record (IPDR)

- Internet protocol: gives information on all captured IP data frames

OverviewPS

MC

igal

e G

n

Title:


Content:






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

Title:


Content:







• 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

Title:


Content:







• Services Activity• IP Activity PSM tables (need activation)• Internet Protocol

• 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- …

Title:


Content:






• 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

Toolbar options (1/3)

Export to Excel or in text file format (.txt)

Go to Activity report

Go to Detailed Activity

Go to IP Activity

Go to Services Activity

Title:


Content:







Protocol decoding

Flow Chart

Multi interfaces

Display the number of different elements in the active column

Find Next Record/Find Previous Record

Export selected xDR to an EDX or XCAP file

Title:


Content:






Filters – Display the filter palette


Filter palette – Detail of the active filtersin the current view

The filter can be saved and loaded. It ispossible to lock filter.

Cancel the filter of the active column / all filters / the last filter

Apply a filter equal, different, lower… than the active cell

Increasing order / decreasing order / No order

Advanced filter (you can use * aswildcard or NULL)

Filter with several value – button

Title:


Content:






• 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

&

Activity Analysis

Title:


Content:






AA Main features

• Activity Analysis is a powerful investigation tool that enables adeep 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

Title:


Content:






Navigation

• Depending on the active table you have selected, by right clickingon a line you can navigate between the different tables to followsubscriber activity

Transitions

ActivityReport

DetailedActivity

IP Activity

ServicesActivity

PSM tables

Title:


Content:






• To analyze more easily subscribers activity through Activity Report, eachCDR 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

CDR Type

Title:


Content:






Distribution function

• It enables to display the number of different elements in the activecolumn in table or chart format

• Additional criteria could be added with

Title:


Content:






• Preset window

- Store a defined context (database type, current view, active filters, columns andtheir 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 orexport a preset.

Preset icons represent the type of view.

Preset filters

Title:


Content:






• Preset creation- Create a group select it, then right click and select ‘save as preset’

Preset filters

Title:


Content:






Flow Chart (1/2)

• It enables to follow easily the activity of a subscriber (CDR)through the message exchanged on Gn interface between GSNnodes:

- Flow Chart for the selected connection either on signalling frames or onall signalling and data frames.

- Flow Chart for the entire PDP/Call Id Flow Chart of the selectedconnection with same options (signalling or signalling & data).

Title:


Content:






Flow Chart (2/2)

• It can be launched from Activity Report or Detailed Activity

• The arrow indicates the event that ended the CDR (LastEvent)

Title:


Content:






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 clickingon 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)

Title:


Content:






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

Title:


Content:






Decoding (3/3)

• Decoding window example

Signalling frames

User can expandeach layer to seeprotocol decoding

User frames

Possibility to export theseframes in a pcap file

Title:


Content:






Multi-interface (1/2)

• When analyzing one issue on Gn interface you may want to go further andfollow 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...

Title:


Content:






Multi-interface (2/2)

• ...or in flow chart mode (Iu/Gn example)

Title:


Content:






Statistics for AA

• KPI statistics integrated in AA

ViewSelection

Statisticsfor AA

CriteriaSelection

Max valuesdisplayed andbitmap export

Sortingand

filtering Gridexport

GraphicalView

GridView

Title:


Content:






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

Title:


Content:






Global Tracing (2/2)

SearchedIMSI/IMEI

SelectDate/Time

range

Selecteddatabases

Selectedinterfaces

Databasesstatus

FoundCDRs

Title:


Content:






Exercises

1. Filter on PDP Context creation. Display all termination event/cause. Whichones are abnormal?

2. Filter on PDP Context creation for blackberry service. Display alltermination event/cause. What is the meaning of termination cause« Timeout! »? Why does it appear?

3. Filter on CR_PDP_CTXT_RES_V1/V1_UserAuthFail. What is the origin ofthis reject?

4. Create a preset to view only PDP context reject for cause V1_UserAuthFail

5. Select one IMSI that failed PDP Context creation with UserAuthFail. Whatis the whole activity done by this subscriber.

Title:


Content:






Exercises

6. Select one PDP session with enough DL volume traffic. Which kind oftraffic is it? WAP, HTTP...? (PSM needed)

7. What is the meaning of reject cause “V1_AllDynAddrOcc”

8. 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?

9. Find all traffic sessions with at least 300 Kbytes of UL volume. Find thosewith packets lost over Gi interface.

10. Find one successful RADIUS transaction. Which information is given byRADIUS server on RADIUS_ACCESS_ACCEPT event?

Title:

Font size: 36 pts

Font: Verdana


Thank you

Title:

Font size: 36 pts

Font: Verdana


Tel: +33 (0) 2 99 04 80 66

Email: [email protected]

Astellia Support

5 CigaleCorePS Basics V52 ATS RA Student (2)

Documents

Transcript of 5 CigaleCorePS Basics V52 ATS RA Student (2)