Vous êtes sur la page 1sur 53

Serving GPRS Support Node (SGSN)

For internal use


1 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Agenda

 GPRS Introduction – Duration 1 hour


 GSM Network architecture
 Circuit core vs Packet core
 GPRS network elements
 Overview of GPRS network architecture
 Brief functionality of all nodes

 GPRS Traffic Management – Duration 2 hours


 Mobility Management in SGSN
 LAC/ RAC overview
 Mobility management states
 GPRS location update call flows
 Session Management in SGSN
 PDP Context activation
 PDP Context deactivation
 PDP Context modification
 Charging
 Online Charging in SGSN
 Offline Charging in SGSN
 Lawful Interception

For internal use


2 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Agenda

 NSN SGSN Introduction – Duration 2 hours


 SGSN Network Interfaces
 SGSN Hardware Architecture
 Hardware modules overview
 Detailed functionality of each module
 Redundancy in various hardware modules
 SGSN Logical Architecture
 Mapping of hardware modules with external interfaces
 Brief on interworking of various hardware modules
 SGSN O&M
 Logging in SGSN
 Understanding SGSN CLI
 Most used commands
 Sample Configurations
 Examples of troubleshooting

 Hands On Session – Duration 1 hours

For internal use


3 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
GPRS Introduction - GSM Network architecture

The main elements of Network Switching


Subsystem are:

 Mobile Services Switching Centre (MSC)


 Visitor Location Register (VLR)
 Home Location Register (HLR)

The Base Station Subsystem consists of the


following elements:
 Base Station Controller (BSC)
 Base Transceiver Station (BTS)
 Transcoder (TC)

For internal use


4 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
GPRS Introduction - Circuit core vs Packet core

SGSN
GSM/GPRS GGSN
Packet switched vs circuit switched BSS
GS GPRS
M B Backbo
mobile
S
 Circuit-switched connections are routed via C
ne Interne
t
GSM (TCP/I
MSC BTS P)
3G
Packet-switched connections are routed via B
SGSN

SGSN GSM /
GSM S
C
Network
Subsystem SR
BTS
 RAN part is shared between CS and PS UMTS
mobile R

traffic UMTS RAN


UMTS
BS MSS HL
R
UMT RN
S C
mobile MG
W
UMTS
BS
RN Landline NW
C PSTN/ISDN

IN
SCP

For internal use


5 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Main SGSN functions

• mobility management
• session management
• charging (post-paid, prepaid)
• statistics
• 2G compression
• authentication
• 2G ciphering
• SMS handling

For internal use


6 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
GPRS Network

BTS
BSC
MSC/ VLR
RNC
PSTN
Network
NODE
B

HLR/AuC
EIR

SS7
Network
Service Control Point (SCP)

DNS SGSN
Domain Billing System
name
server
Charging
GPRS Gateway (CG)
backbone
network
(IP based) Data
SGSN network
(Internet)

Gateway GPRS
Support Node
(GGSN) Data
network
Inter- Lawful Interception (Internet)
PLMN BB Gateway (LIG)
Border
Gateway (BG)

For internal use


7 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
GPRS Traffic Management - Mobility Management

LAC/ RAC overview

The relationship between Cell, RA,


LA, and SGSN coverage area :

Cell ⊂ Routing area ⊂ Location area ⊂


MSC coverage area

Cell ⊂ Routing area ⊂ SGSN coverage area

RAI = MCC + MNC + LAC + RAC

 Where RAC is Routing Area Code


 The RAI is LAI + RAC. The RAI is
of fixed length - 15 digits.

For internal use


8 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
GPRS Traffic Management - Mobility Management
Mobility management states:

 Idle State
 Ready State
 Standby State

Ready State

Idle State
Standby State

For internal use


9 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
GPRS Traffic Management - Mobility Management

IDLE
Implicit detach or
cancel location GPRS Detach
OR
GPRS Attach Cancel Location

READY

READY timer expiry


OR PDU reception
Force to standby
OR
Abnormal RLC
condition

STANDBY
For internal use
10 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
GPRS Traffic Management - Mobility Management
The procedures of Mobility Management are:
 GPRS Attach/ GPRS Detach
 Purge
 Security
 Authentication
 subscriber identity confidentiality
 Ciphering (2G only)
 Identity check.
 Location management
 PS Paging
 Normal/periodic routing area update.
 Subscriber Management
 Interaction with MSC/VLR
 IMSI attach/detach, combined IMSI/GPRS attach/detach
 Combined routing area and location area update
 CS paging
 Non-GPRS alert

For internal use


11 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
GPRS Traffic Management - Mobility Management

GPRS Attach Procedure (MS Initiated)


For internal use
12 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
GPRS Traffic Management - Mobility Management

GPRS Detach Procedure


(MS Initiated)

GPRS Detach Procedure


(HLR Initiated)

For internal use


13 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
GPRS Traffic Management - Mobility Management

The MS is detached from GPRS either explicitly or implicitly:


• Explicit detach: The network or the MS explicitly requests
detach specifying the cause for it
• Implicit detach: The network detaches the MS after the mobile
reachable timer expired or after an irrecoverable radio error
causes disconnection of the logical link
After a successful detach:
– MM context and PDP context in PAPU are removed;
– P-TMSI - IMSI association is not removed from PAPU;
– The Visiting GPRS subscriber data may be deleted from SMMU;
– otherwise the data from SMMU is removed when "Detached
subscriber storage time" timer expires. Also the IMSI-P-TMSI
association from PAPU is removed and a "Purge" message is sent to
HLR.
For internal use
14 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
GPRS Traffic Management - Session Management

INACTIVE

PDP context PDP context


activation deactivation
(the last)
GPRS detach

ACTIVE

PDP context activation


PDP context modification
PDP context deactivation
Timer expiry
Resource reallocation
PDU

For internal use


15 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
GPRS Traffic Management - Session Management

PDP Context Activation

PDP Context Modification

PDP Context Deactivation

For internal use


16 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Access Point Name
An Access Point Name is composed of two parts as follows:
The APN Network Identifier
The APN Operator Identifier
The APN Network Identifier is mandatory and is a label (for example
"corporation") or a set of labels separated by dots which is a domain name
according to the DNS naming conventions
The APN Operator Identifier is optional. It is a domain name according to
the DNS naming conventions, and consists of three labels. The APN
Operator Identifier shall end with ".gprs".

APN Network Id APN Operator Id


APN= my.isp.com. mncxxx.mccyyy.gprs

NOTE: The APN stored in the HLR does not contain the APN Operator
Identifier. Also a wild card may be stored in the HLR instead of the APN.

For internal use


17 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
APN Selection

The SGSN selects the Access Point Name (APN) to be used for a
PDP context based on the MS-requested parameters and the
subscribed PDP contexts of the user

The MS can request one of the combinations of the PDP type, PDP
address, and APN parameters, which influence the APN selection:
– PDP type, PDP address, APN
– PDP type, PDP address
– PDP type, APN
– PDP type
– None of these parameters

For internal use


18 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
GPRS Traffic Management - Charging

Offline Charging:
 S-CDRs
 M-CDRs
 SMS-CDRs

Online Charging:
 CAP3

For internal use


19 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Triggering for CDRs Generation

Action Call Data Collection New CDR Subrecord CDR Ready for Transfer
(subscriber/netw ork-generated) Start Stop S-CDR M-CDR S-CDR M-CDR
Attach M
Detach M X
Start of PDP Context S
End of PDP Context S X
Inter SGSN RA Update (old SGSN) M&S X X
Inter SGSN RA Update (new SGSN) M&S
Intra SGSN RA Update (Inter PAPU) S S X X
Cell update (Intra PAPU) X (*
O&M Request M&S X X
Time Tariff Category Sw itch X
Threshold Volume X
Threshold Time X X
QoS Change X
PAPU restart M&S X X

• Inter PAPU RA Updates are handled like Inter SGSN RA updates in S-


CDR point of view
• CDR data volume and CDR time limit are configurable parameters

*) If ‘Cell ID in S-CDR’ feature is used


For internal use
20 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
GPRS Traffic Management – Lawful Interception

For internal use


21 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – SGSN Interfaces

For internal use


22 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – Hardware Architecture
BASIC CABINET EXTENSION CABINET

SGSN Hardware Units: SGAC SGBC


 Packet Processing Unit (PAPU) PDFU-B PDFU-B PDFU-B PDFU-B
 process user data and protocol conversion 0
PDFU 0 PDFU 1
0
PDFU 0 PDFU 1

 GPRS mobility management (GMM) CPBP 0

 session management (SM) SW10C-A


SW10C-A
SW10C-A

 ciphering and compression between the MS and GSW2KBGSW2KB CPEA 1


0 1
SGSN
1
 Up to 16 + 1 PAPUs 1 0 3 6 8 10 CPRS-A 2 0 2 8 10

 Signalling and Mobility Management Unit CC4C-ACC4C-ACC4C CC4C-A CC4C-ACC4C-ACC4C-ACC4C-A


-A
(SMMU) MCHU SMMU SMMU MCHU
MCHU
CPLC18 3
SMMU SMMU PAPU PAPU
 support subscriber mobility management 0
0 0 1 1 3 4 3 4

 SS7-based interfaces Gr, Gd, Gs, and Gf 2 0


10
FTRB-A FTRB-A 1 CPLAN-A4 2 FTRB-A 0 FTRB-A 1
3 6 9 0 3 6 9
 Up to 4 + 1 SMMU
 Operation and Maintenance Unit (OMU)
CC4C-ASD4C-ASD4C-ACC4C-C CPLC18 5 CC4C-ACC4C-ACC4C-ACC4C-A
SD0 SD 1
OMU OMU OMU OMU PAPU PAPU PAPU PAPU
 traffic control functions 0 MCHU MCHU 1 CPETS-E/ 5 6 7 8
 maintenance, system configuration CPETC-E6
3
3 0 3 6 9 0 3 6 9
administration, and system management CPETS-E/
7
 Marker and Charging Unit (MCHU) CC4C-ACC4C-ACC4C-ACC4C-A
CPETC-E CC4C-ACC4C-ACC4C-ACC4C-A

 collects and stores charging information SMMU PAPU PAPU PAPU CPETS-E/8 PAPU PAPU PAPU PAPU
9 10 11 12
 controls and supervises the group switch (GSW) 2 0 1 2 CPETC-E

 hunts free circuits 4 0


FTRB-A 2
6
FTRB-A 3 4
0
FTRB-A 2
3 6
FTRB-A 3
9
CPETS-E/9
 establishing and releasing connections CPETC-E
CC4C-ACC4C-ACC4C-ACC4C-A
 Group Switch (GSW) – Connect to BSS/ NSS GT4C-AGT4C-A
GTIC 0 GTIC 1 CPETS-E/
10 PAPU PAPU PAPU PAPU
 Exchange Terminal (ET) – Connect
ET16 ET16 CPETC-E
(ETS2) (ETS2) 13 14 15 16

Transmission to GSW 5 0 2 6 9 5 0 3 6 9

 Message Bus (MB) – Interconnect Cards FRONT SIDE

For internal use


23 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – Logical Architecture

The main units supporting GPRS are PAPU and SMMU.

The SMMU and PAPU have N+1 redundancy, whereas the MCHU,
OMU, MB, GSW and CLS have 2N redundancy

For internal use


24 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Signalling and Mobility Management Unit - SMMU
(1/2)
SMMU supports subscriber mobility management functionality. For
this it uses several SS7–based interfaces that connect the SGSN
to various NSS network elements
SMMU manages a visiting GPRS subscriber database (GSBASE)
One SMMU can handle 750.000 subscribers simultaneously
SGAC SGBC
PDFU 0 PDFU 1 PDFU 0 PDFU 1
0 0
0

DBG DBG
RST RST
1
PSC6-CB

PSC6-CB

J7 J7 -slot 1: PSC6-CB Power Supply 1 2


1
CPU
AS7
CPU

-slot 2: AS7C CCS7 interface unit


AS7

J6 J6 CC4C-A
MCHU MCHU 3 PAPU PAPU PAPU
MCHU 1
OP R OP R -slot 3/4: CP816-AC Central Processing Unit 0
0 7 8 9
WO WO 4 2
RUN RUN -slot 5: PSC6 Power Supply 2
FTRB-A 0 FTRB-A 1 FTRB-A 0 FTRB-A 1
LF LF
OL OL
-slot 6: AS7C CCS7 interface unit 5
TE TE
OMU PAPU PAPU OMU PAPU PAPU PAPU PAPU
AP
DRAM
AP
DRAM -slot 7: CP816-AC Central Processing Unit 0 0 1 1
6
10 11 12 13
SB SB
3
ON CPSI ON CPSI 3
SCSI SCSI
ETx0 ETx0 7
OFF OFF
ERx0 ERx0
ETx1 ETx1 PAPU PAPU PAPU PAPU PAPU PAPU PAPU
AP AP
ERx1 ERx1
2 3 4 5 8 14 15 16

FTRB-A 2 FTRB-A 3 4 FTRB-A 2 FTRB-A 3


4 9

PAPU ET16 ET16


1 2 3 4 5 6 7 6 (ETS2 (ETS2
10

5 5

For internal use


25 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Signalling and Mobility Management Unit – SMMU
(2/2)

SMMU can handle up to 64 CCS7 links


Support for SS7oIP (SIGTRAN)
DBG DBG
RST RST

N+1 Redundancy
PSC6-CB

PSC6-CB

J7 J7

Up to 6 SMMU in SGSN
CPU
AS7
CPU
AS7

J6 J6

OP R OP R

WO WO
RUN RUN
LF LF
OL OL

TE TE
AP AP
DRAM DRAM
SB SB

ON CPSI ON CPSI
SCSI SCSI
OFF ETx0 OFF ETx0
ERx0 ERx0

AP
ETx1 AP
ETx1
ERx1 ERx1

1 2 3 4 5 6 7

For internal use


26 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Packet Processing Unit - PAPU (1/4)

• The main purpose of PAPU is to process the user data to/from


the RAN and relay it from/to the GPRS backbone network.
• Also handles session and mobility management functions

SGAC SGBC

PDFU 0 PDFU 1 PDFU 0 PDFU 1


0 0
0

1
1 2

CC4C-A
MCHU MCHU 3 PAPU PAPU PAPU
MCHU
0 1 7 8 9
0
FTRB-A 0 FTRB-A 1 4 2 FTRB-A 0 FTRB-A 1
2

5
OMU PAPU PAPU OMU PAPU PAPU PAPU PAPU
10 11 12 13
0 0 1 1
6
3
3
7

PAPU PAPU PAPU PAPU PAPU PAPU


PAPU
8 14 15 16
2 3 4 5

FTRB-A 2 FTRB-A 3 4 FTRB-A 2 FTRB-A 3


4
9

PAPU ET16 ET16


10
6 (ETS2 (ETS2

5 5

For internal use


27 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Packet Processing Unit - PAPU (1/4)

DBG
RST

J7

J6

OPR OP R
WO
RUN
LF
OL

IOCP-EA
TE

PSC 6
AP

AS7

AS7

CPU
DRAM
SB

CPSI
ON ON
SCSI
ETx0
OFF OFF ERx0
AP AP ETx1
ERx1

1 2 3 4 5 6 7 1 2 3 4 5 6 7

PAPU with IOCP-E PAPU with IOCP-EA


- slot 1: PSC6 Power supply - slot 1: PSC6 Power Supply
- slot 2: AS7-C - slot 2-4: IOCP-EA Central Processing Unit
Frame Relay Unit
for I/O Interface Unit
- slot 3/4: IOCP -E Central Processing Unit
- slot 5: AS7-C Frame Relay Unit
for I/O Interface Unit
- slot 6: AS7-C Frame Relay Unit
- slot 5: AS7-C Frame Relay Unit - slot 7: CPU Central Processing Unit
- slot 6: AS7-C Frame Relay Unit
- slot 7: CP816 -A Central Processing Unit

For internal use


28 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Packet Processing Unit - PAPU (2/4)

In order to carry the user data between the RAN (Gb or Iu) and
the Backbone (Gn), PAPU needs to support a large set of
protocols:
PAPU IOCP-E or IOCP-EA
Relay Relay
SNDCP GTP GTP GTP
LLC
UDP UDP UDP
BSSGP
NS cntl IP IP IP
FR ATM Ethernet Ethernet
Ethernet
Gb/FR (BSS) E1 Gn (GGSN)
Iu user (RAN) Gn (GGSN)
2G : Gb/FR 3G: Iu User Plane

PAPU PAPU CPU


Relay RANAP
SNDCP GTP SCCP
LLC
BSSGP UDP MTP-3b M3uA
NS cntl IP SCTP
ATM relay
UDP/IP Gn (GGSN) to IOCP-EA
Ethernet IP
Gb/IP (BSS) Ethernet
Ethernet
Iu control (RAN)
2G : Gb/IP 3G: Iu Control Plane
For internal use
29 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Packet Processing Unit - PAPU (3/3)

One AS7-C can handle up to 256 tsls at 64kbit/s for frame relay
connection;

IOCP-E contains 4 Ethernet interfaces: 2 Ethernet connections for the


Gn interface and 2 Ethernet connections for the Iu interface over IP
(optional). IOCP-EA adds 4x155Mbps Fibre ATM interfaces

CPU816-A also contains 4 Ethernet interfaces: 2 Ethernet connections


for the Gb interface over IP and 2 Ethernet connections for EMB
interfaces

Can manage up to 100 000 subscribers in High Traffic mode or


250.000 subscribers in High Attach mode.

A standalone PAPU serves maximum 1000 RA

N+1 Redundancy (IOCP-E) or N+ redundancy (IOCP-EA)

Up to 17 PAPUs in SGSN
For internal use
30 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Central Processing Unit for I/O Interface –
IOCP-E/EA
IOCP-E plug-in unit performs CIPHERING and COMPRESSION
2G CIPHERING
In GPRS, both user data and signalling are ciphered all the way
between the MS and the SGSN, not between the MS and the BTS.
2G COMPRESSION
Used between SGSN and MS to minimize the usage of radio and BSS
transmission resources, and to speed up the user perceived data
throughput.
IOCP-E can perform two kinds of compression:
HEADER COMPRESSION
USER DATA COMPRESSION
EA-variant includes 4x155Mbps ATM interfaces

For internal use


31 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Interface capacity

• A maximum of 512 bearer channels per PAPU and maximum of 3072


bearer channels per SGSN towards 2G RAN(Gb).
• A maximum of 64 SS7 signalling links per SMMU and maximum of
320 SS7 signalling links (Gr, Gd, Gf and Gs) with 5 SMMU per SGSN,
HW supports that number but SW may bring restrictions.
• A maximum of 240 physical E1/T1 PCM lines (Gb and all SS7-based
interfaces).
• A maximum of 256 RACs (with or without Multipoint) per SGSN

For internal use


32 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Capacity licence management

SGSN element level subscriber, PDP context, and data throughput


capacity control are handled with licence management

A valid licence for SGSN level subscriber capacity, PDP context


capacity, and data throughput capacity is needed. The following
feature codes are in use:
– SGSN Total Attach Capacity
– SGSN Gb Attach Capacity
– SGSN Iu Attach Capacity
– SGSN PDP Context Capacity
– SGSN Data Throughput Capacity

For internal use


33 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – O & M
Logging in SGSN

For internal use


34 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – O & M
Logging in SGSN

For internal use


35 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – O & M
Logging in SGSN

For internal use


36 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – O & M
Understanding SGSN CLI

For internal use


37 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – O & M

Command Description
ZMMO Check subscriber status
Subscriber Management Commands ZMMS Check subscriber profile (subscribed APNs)
ZMMN Display Number of subscribers
ZMMD Delete subscriber from SGSN

Command Description
ZFWO Check GB link status
ZEJL Check BVCI status
ZW7I Check Licence installed (used for BVCI Count)
General Health Check and O&M Commands ZQRI Check IP configurations
ZAHO Check system alarms
ZQRX Ping/ Traceroute for any interface
ZWVI Check GT/ MNC/ MCC details for own SGSN
ZWQO Backup
ZGHI Check Charging Gateway Status

Command Description
ZOYI Check SCTP association set status
ZCFI Check IMSI to GT analysis
SS7 Signaling Management Commands ZNBI Check GT analysis
ZNAI Check GT Translation results
ZNHI Check Subsystem States

For internal use


38 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – O & M
Sample Configurations – Gb Link

For internal use


39 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – O & M
Sample Configurations – PLMN Configuration

For internal use


40 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – O & M
Sample Configurations – IMSI To GT Table

For internal use


41 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – O & M
Sample Configurations – LAC Configuration

For internal use


42 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – O & M
Sample Configurations – Signaling Link status

For internal use


43 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – O & M
Sample Configurations – Check Unit Load

For internal use


44 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – O & M
Sample Configurations – Checking System Clock

For internal use


45 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – Analysing Traces

For internal use


46 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – Analysing Traces

For internal use


47 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – Analysing Traces

For internal use


48 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – Analysing Traces

For internal use


49 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
NSN SGSN Introduction – O & M
Examples of troubleshooting
 Gb Link Trouble shooting
 Ping Remote IP
 Take traceroute
 Get configurations checked at both SGSN and BSC ends
 Check for any information in alarms
 PAPU Switchover

 GPRS not working


 Check if subscriber is attached in SGSN
 Check APNs allowed for subscriber
 Verify APN subscriber is using for Data Call
 Take trace on Gn and Gb interfaces

 Subscriber not getting attached


 Check IMSI to GT analysis
 Check GTT
 Take trace on Gb and Gr interfaces

 Ga, Gn interfaces trouble shooting


 Ping GGSN/ Charging Gateway IP
 Take traceroute
 Take trace on Gn interface

For internal use


50 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Hands On Session

For internal use


51 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Q&A

For internal use


52 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010
Thank you

For internal use


53 © Nokia Siemens Networks SGSN Training Module Vikas Malhotra -26 Mar 2010