Reliance 2G-3G PS Core HLD Ver 2.0 PDF

!
Cisco 2G/3G Mobile Packet Core Solution

Document
Reliance Communications Limited
Jan 2014

Revision History

Version
1.0
1.1
1.2
Date
Aug 18, 2010
Aug 18, 2010
Aug 19, 2010
1.3
Sept 07, 2010
1.4
1.5
Sept 22, 2010

Dec 15, 2010
2.0
Jan 13, 2014
Change Summary
First Version
Minor updates based on comments from RCOM
Minor updates. Updated with current BoM
Corrected the 2G Homing, RTL MMS APN Name; Added
soft-launch BoM etc
Added Charging scenarios & related Gy info
Updated Section-12 with 2G mapping
Added Section-11 for Expansion-1. Changed the
document template to Cisco (from Starent).
2G/3G Mobile Packet Core Solution Document
Page 2 of 36
Table of Contents

1
2
3
4
4.1
4.2
5
6
7
7.1
7.2
7.3
7.4
7.5
7.6
7.7
8
8.1
8.1.1
8.1.2
8.2
8.2.1
8.2.2
8.2.3
8.2.4
8.2.5
8.2.6
8.3
8.4
8.5
9
9.1
9.2
9.3
9.4
9.5
9.6
10
11
11.1
11.2
11.3
Introduction ....................................................................................................................... 4
ASR5000 Overview .......................................................................................................... 4
Hardware Configuration and Redundancy ........................................................................ 7
inPilot Platform .................................................................................................................. 8
Inline Services Reporting Solution (inPilot) ....................................................................... 9
inPilot Reports .................................................................................................................. 9
Network Overview ........................................................................................................... 10
Interface Support ............................................................................................................ 14
Current 2G Network ........................................................................................................ 18
SGSN (Serving GPRS Support Node) ............................................................................ 18
GGSN (Gateway GPRS Support Node) ......................................................................... 19
Charging Gateway .......................................................................................................... 20
Lawful Interception .......................................................................................................... 20
HLR ................................................................................................................................. 21
Intelligent Network .......................................................................................................... 21
NMS (Network Monitoring System) ................................................................................ 21
ASR5000 CGSN Deployment and 2G APN Migration (Soft-Launch) ............................. 22
Charging ......................................................................................................................... 23
Post-paid Charging ......................................................................................................... 23
Pre-paid Charging ........................................................................................................... 24
Services .......................................................................................................................... 26
Internet ............................................................................................................................ 26
WAP ................................................................................................................................ 26
MMS ............................................................................................................................... 26
Blackberry ....................................................................................................................... 26
WDVPN .......................................................................................................................... 27
Roaming ......................................................................................................................... 27
Deep Packet Inspection (DPI) ........................................................................................ 27
PCRF .............................................................................................................................. 27
Mediation Interface for CDR Handling ............................................................................ 28
WAP/MIG Integration ...................................................................................................... 29
Challenge ........................................................................................................................ 29
Physical Connectivity ...................................................................................................... 29
Logical Link and Routing Protocol .................................................................................. 29
Solution and Role of Cisco ............................................................................................. 29
Charging ......................................................................................................................... 30
Scope Classification for MIG / Dependencies ................................................................ 30
GERAN Migration from Huawei SGSN to ASR5000 CGSN (Phase-2) .......................... 31
CGSN Expansion 1 (Jan2014) .................................................................................... 32
Hardware & Software Augmentation .............................................................................. 32
Capacity Details .............................................................................................................. 33
Features and Functionality ............................................................................................. 35
Page 3 of 36
1 Introduction
Cisco is providing the packet core for Reliance 3G network. As part of this deployment,
3G packet data subscribers will be served by Cisco SGSN/GGSN. At the same time,
existing packet core serving 2G traffic will also be migrated over time to Cisco supplied
packet core.
This document provides the technical description and high level design of the Cisco
Systems ASR5000 SGSN+GGSN combo service architecture including dimensioning,
interface descriptions, and service connectivity to other Reliance network elements.

2 ASR5000 Overview
As part of this project Cisco will deliver combo SGSN+GGSN (CGSN Combo GSN) based
on ASR5000 hardware platform in the Reliance packet core network.
Cisco s ASR5000 is unique in the industry because it is the only platform that is capable
of running multiple network functions using the same hardware.
The hardware architecture is a non-bladed architecture - meaning there is no
dedicated processing card that runs a particular network function. All network
functions are distributed across all the available processing cards and these network
functions can all run at the same time.

Figure 1 Front View of Cisco ASR5000 System

In short, the ASR5000 is the only platform that is designed exclusively for the wireless
industry. It provides an ultra-high density solution for deployment in mobile telecoms
operator environments. The system is a high-performance, carrier-grade platform that
offers industry-leading wireless data capacity while enabling numerous integrated
applications for additional revenue generation. The ASR5000 has been designed to
address both todays needs, and to provide a scalable platform to meet the needs of
future fourth generation (4G) networks.
Page 4 of 36

The ASR5000 chassis features a 48-slot design with 16 front-loading slots for
application processing cards and 32 rear-loading slots (16 upper and 16 lower) for line
cards.

Figure 2 Front(left) and Rear(right) Views of ASR5000

The following application and line cards are required to support GPRS / UMTS wireless
data services on the system:
1. System Management Cards (SMCs): Provides full system control and
management of all cards within the ASR5000 platform. Up to two SMC can be
installed; one active, one redundant.
2. Packet Services Cards (PSCs): Within the ASR5000 platform, PSCs provide high-
speed, multi-threaded PDP context processing capabilities. Up to 14 PSCs can be
installed, allowing for multiple active and/or redundant cards. There are 2 variants
of PSC cards PSC2 and PSC3. As the function of the PSC2 and PSC3 are identical
Page 5 of 36

(apart from capacity), well refer to the PSC2/3 as PSC for the remainder of this
document.
3. Switch Processor Input/Outputs (SPIOs): Installed in the upper-rear chassis
slots directly behind the SMCs, SPIOs provide connectivity for local and remote
management, central office (CO) alarms as well as BITS for frequency
synchronization. Up to two SPIOs can be installed; one active, one redundant.
4. Line Cards: Installed directly behind PSCs, these cards provide the physical
interfaces to elements in the GPRS/UMTS data network. Up to 26 line cards can be
installed for a fully loaded system with 13 active PSCs, 13 in the upper-rear slots
(slots 17 to 32) and 13 in the lower-rear slots for redundancy/standby (slots 33 to
48). Redundant PSCs do not require line cards. ASR5000 can have the following
line cards
4 Ports Gigabit Ethernet Line Card (QGLC) for IP/Ethernet connectivity to
other network elements. Ethernet line cards support a maximum of 2048 bytes
IP MTU size.
1 port 10Gigabit Ethernet Line Card (XGLC) for IP/Ethernet connectivity to
other network elements. XGLC is full height card and requires 2 slots in the rear
of the chassis.
4 Ports Channelized STM-1 (CLC2) for providing frame relay connection over
SDH.
5. Redundancy Crossbar Cards (RCCs): Installed in the lower-rear chassis slots
directly below the SPIOs, RCCs utilize 5 Gbps serial links to ensure connectivity
between line cards and every PSCs in the system for redundancy. Two RCCs can be
installed to provide redundancy for all line cards and PCSs.
Ethernet line cards support 802.1 VLAN tagging and DSCP marking for traffic separation
and prioritisation.

Page 6 of 36
3 Hardware Configuration and Redundancy

The hardware configurations of the CGSN for Reliance has been designed with
redundancy as explained below.

The CGSN is configured with no single point of failure in a standalone chassis. The
different levels of redundancy for the different cards are summarized below:
1. 1:1 Switch Processor Card (SMC) redundancy
2. N:1 Packet Services Card (PSC) redundancy
3. 1:1 Switch Processor I/O (SPIO) card redundancy
4. 1:1 4 Ports GE Line Card (QGLC) redundancy
5. 1:1 (active/active) Channelized Line Card (CLC2) configuration. Note that although
active and standby CLC2 are provided, active/standby configuration will not be
supported till R11.0 of the SGSN (Dec2010).
6. Configurable line card port redundancy on Ethernet Cards
7. Redundancy Crossbar Card (RCC) for PSC-to-line card failover using the 280 Gbps
Redundancy Bus
8. Self-healing redundant 320 Gbps switching fabric
9. Multiple fans in two fan trays.
10. Redundant Power Filter Units (PFUs)
11. Hot-swappable cards, allowing dynamic replacement while the system is
operational

This will ensure that 100% capacity will be provided on each system in case of internal
module or interface cards failure.

Page 7 of 36
4 inPilot Platform

After introducing 3G with attractive data tariffs for mobile data usage the mobile
network operators are today facing two challenges:
a potentially small number of subscribers is using the network resources in such an

extensive way that network capacity has to be permanently increased to avoid
having a negative impact on all subscribers
instant messaging or VoIP applications can reduce the revenue generated by the
traditional operator services for SMS and circuit voice

One of the countermeasures against heavy data usage, which are now being introduced
by operators, is bandwidth management to throttle all traffic of a subscriber after
exceeding a fair usage limit defined by the contract. Simply policing or shaping a
subscribers data traffic to a maximum allowed bandwidth does not take into
consideration though that only the busy hour is really the driving factor for the
operator to increase capacity. If a heavy user is transferring his data e.g. during the
night where usually a lot of capacity is available, a throttling may not be necessary.
Instead of policing all traffic, the operator may still want to allow the subscriber to
access his billing data and to upgrade the tariff at full speed.
On the other hand, the operator may wish to control the impact of heavy users even
before reaching the fair usage limit. P2P applications are often creating many flows
which require resources in the network elements such as the GGSN, and are known to
be very data intensive when used for file sharing. And while controlling VoIP traffic
using SIP based on UDP port 5060 can easily be achieved by blocking or rate-limiting
traffic on this port, P2P applications such as Skype make it harder to implement such
countermeasures.
To decide how to address these challenges mentioned above, it is therefore essential in
a first step to understand what the subscribers are doing:
how much network capacity is used by only the top N subscribers, i.e. is there a need
to introduce better subscriber specific bandwidth management controls?
what applications are being used by the top subscribers or by all subscribers? Are
capacity savings possible by limiting the usage of specific data intensive applications
what content is being transferred? Is this optimizable by TCP optimization or media
adaptation and caching proxies, and how big is the benefit?
how many minutes are already being used by VoIP applications and protocols? Is
there a significant revenue loss which should perhaps be addressed by offering a
VoIP client with special tariffs by the operator itself (and blocking other VoIP
usage)?
Page 8 of 36
4.1 Inline Services Reporting Solution (inPilot)
InPilot is a unified reporting solution which is meant to integrate all data feeds from
Starent platforms. Once DPI is enabled on ASR5000 chassis, it can generate the EDRs,
which is processed by inPilot servers and inPilot reports are generated. The information
will be presented via an easy-to-use web based GUI.

4.2 inPilot Reports

The inPilot application supports generation of canned statistical reports that can be
used to analyze network performance, and decide the policies for users, and identify the
customer trends, network usage patterns, network categorization, etc. The reports can
be per gateway, or multiple gateways, or for the overall network. The reports can be
generated for the usage of different entities such as gateway, RG type, etc on an hourly,
daily, weekly, or monthly basis.
The typical canned reports that are supported for the inPilot application include:
Historical summary reports (Daily/Weekly/Monthly)
Average Reports
Top N Reports
Statistical and analytical reports

Page 9 of 36
5 Network Overview

There are four packet core locations, Mumbai, Delhi, Kolkata and Bhopal with following
capacity requirements. 100% session redundancy has been planned for 3G, while there
is no DR planned for throughput. 80% of 3G traffic has been considered using Direct
Tunnel.

3G Capacity Requirements:
3G
Mumbai Delhi
Kolkata Bhopal Total
SAU (K)
857.62 673.01 562.88 204.49 2297.99
PDP (K)
334.47 262.47 219.52
79.75 896.22
Throughput (Gbps)
5.00
4.15
3.51
1.23
13.89

3G Traffic Requirements with 100% Session DR, 0% Throughput DR, 80% Direct
Tunnel [Mumbai & Delhi in one pool, Kolkata & Bhopal in one pool for session
DR]:

3G SGSN Requirements:
3G SGSN
Mumbai Delhi
SAU (K)
1530.62 1530.62 767.37 767.37 4595.99
PDP (K)
596.94 596.94 299.27 299.27 1792.44
Throughput (Gbps)
[20% non-DT]
1.00
0.83
0.70
0.25
2.78

3G GGSN Requirements:
3G GGSN
Mumbai Delhi
PDP (K)
596.94 596.94 299.27 299.27 1792.44
Throughput (Gbps)
5.00
4.15
3.51
1.23
13.89

One SGSN+GGSN combo (CGSN Combo GSN) has been proposed in each of the 4 packet
core locations to take care of 3G traffic requirements.

In addition to above 3G traffic, current deployed 2G capacity (on Huawei SGSN/GGSN
for RCOM and RTL) will be migrated to Cisco ASR5000 CGSN. Following are the capacity
requirements for 2G traffic:

2G Traffic Requirements (Current Deployed 2G Capacity)
2G
Mumbai Delhi Kolkata Bhopal Total
SAU (K)
2000
2000
960
620 5580.00
PDP (K)
200
200
101
90 591.00
Throughput (Gbps)
0.250 0.250
0.100
0.100
0.700
Cell Capacity Reqmt
(K)
60
80
60
50
250
Page 10 of 36

3G+2G Traffic Requirements (3G traffic with 100% Session DR, 0% Throughput
DR, 80% Direct Tunnel):

3G+2G SGSN Requirement:
3G+2G SGSN
Mumbai Delhi
SAU (K)
3530.62 3530.62 1727.37 1387.37 10175.99
PDP (K)
796.94 796.94 400.27 389.27 2383.44
Throughput
(Gbps) [20% non-
DT for 3G]
1.25
1.08
0.80
0.35
3.48

3G+2G GGSN Requirement:
3G+2G GGSN
Mumbai Delhi
PDP (K)
796.94 796.94 400.27 389.27 2383.44
Throughput
(Gbps)
5.25
4.40
3.61
1.33
14.59

One additional ASR5000 has been proposed in Delhi location to take care of the 80K
cells requirements in Delhi SGSN.

Along with ASR5000 SGSN/GGSN following elements have been proposed for packet
core based on Reliances requirements. Cisco is supplying SGSN and GGSN nodes
(HW+SW for ASR5000), and Cisco EMS/InPilot software. Other elements shown in
below table are being directly procured by Reliance through their existing contracts
with respective vendors:

Node
Hardware
SGSN+GGSN Combo
EMS
inPilot Server
inPilot Aggregator Server
Cisco 7609
Cisco Firewall
Cisco Border Gateway
DNS (for APN Resolution)
Cisco ASR5000
Sun Server T5220
Sun Netra 4450
Sun Netra 4450
Cisco 7609
Cisco ASA 5580-40
Cisco BG 7201
Sun Server X4140
Quantity
Mumbai Delhi Kolkata Bhopal
1

1
1
2
2
2
2
2

1

2
2
2
2
1
1
1

2
2
2
2
1

1

2
2
2
2

Attached sheet captures the BoM agreed based on above requirements for 3G and 2G
traffic. The sheet also captures the necessary assumptions taken while deriving the
BoM, inline with discussion with Reliance.

Reliance 3G BoM.xls
Page 11 of 36

Diagram below shows the high level implementation of the Cisco CGSNs within the Reliance
network.

Traffic Path from RNC to ASR5000:

Page 12 of 36

Traffic Path from ASR5000 to RNC:

The following table shows hardware/software releases for the surrounding nodes:

Node Type
Vendor
2G SGSN
Huawei (Reliance to provide HW & SW Release Details)
RNC
ZTE & Huawei (Reliance to provide HW & SW Release Details)
BSC
ZTE & Huawei (Reliance to provide HW & SW Release Details)
HLR
HP (Reliance to provide HW & SW Release Details)
LI
Verint (Reliance to provide HW & SW Release Details)
CGF
Cisco ASR5000 HDD
IN
Comverse (Reliance to provide HW & SW Release Details)
PCRF
TBD
AAA
Not Planned
LNS
Cisco

Table 1 Connecting Nodes Version Information
Page 13 of 36
6 Interface Support

The CGSN needs to support the following interfaces into Reliance network.

IuPS-Control (IuPS-C) Interface

Interface between the RNC and the ASR5000 for signaling. Iu-PS control interface is
separated from the Iu-PS user plane, and provides the SS7 SIGTRAN connectivity to
RNC.

IuPS User (IuPS-U) interface

Interface between the RNC and the ASR5000 for user traffic. The link is planned for
Point to Point connectivity. Iu-flex is considered with Mumbai and Delhi in one pool, and
Kolkata and Bhopal in one pool. RNC should be configured with primary-secondary
algorithm for SGSN selection. For example, if the Mumbai CGSN fails, then that RNC
should send the call to Delhi CGSN.
The physical interface considered is via XGLC line card in all locations apart from
Bhopal where QGLC line card has been considered based on throughput requirements.
Gb Interface
Interface between the 2G BSCs and the Cisco ASR5000 for Gb Link. Gb-flex is not
planned for deployment.
Gb over IP is considered and the physical interface is via QGLC line card. In order to
support few RTL BSCs which require TDM connectivity, STM-1 line card has been
considered in Kolkata and Bhopal CGSN for providing Gb over FR connectivity. Reliance
will multiplex the E1s from these BSCs and provide STM-1 interface connectivity to ASR
5000.

Active
Card
Active
Card
pp
er
EA
Layer-2/3 LAN
Switch
tiv
Ac
ctiv
-1
M
ST
Gig
a
e
SDH MUX
db
Ac
St
an
aE
op
pe
ST
M
-1
rG
ig
Standby
Card
tiv
Co

Figure 3: Quad GigE Card Connectivity
Standby
Card

Figure 4: STM-1 Connectivity
Page 14 of 36

Gn interface
Interface between SGSN and GGSN, and to other SGSN/GGSN in the home PLMN. The
physical interface considered is via XGLC line card in all locations apart from Bhopal
where QGLC line card has been considered based on throughput requirements.

Gr Interface
The Interface to Home and Roaming HLRs are via Reliance signalling gateway.
The Gr interface from ASR5000 CGSN is provided over SIGTRAN.

The physical interface will be Copper GE for Gr. One pairs of active and standby GE port,
total of 2 GE ports will be use for connectivity.

Ge interface
The interface to IN for online charging using CAP3 protocol. This interface is being used
in current 2G deployment for prepaid online charging for RCOMNET APN. However, this
interface will not be used in ASR5000 CGSN, as online charging will be done using 3GPP
DIAMETER Gy interface for both 2G and 3G subscribers.

Gy interface
The interface to OCS for online charging using 3GPP TS 32.299 compliant DIAMETER Gy
protocol.

The physical interface will be Copper GE for Gr. One pairs of active and standby GE port,
total of 2 GE ports will be use for connectivity.
Gp interface
The Gp Interface shares the same protocol stack as the Gn Interface, but traffic using this
interface is destined to SGSN/GGSNs outside of the Reliance network. Traffic is routed
from the Reliance Gn/Gp network out through the GTP firewall to GRX network. Cisco
ASA 5580 firewall has been proposed as part of the solution.
Ga Interface
The Ga interface is the billing interface and in this implementation is a store and collect
system using SFTP.

The CGSN will write files containing S-CDRs & e/G-CDRs onto a HDD located on the SMC
card. The Reliance Mediation system will connect to the CGSN over SFTP at regular
intervals, identify the new files, retrieve them, and mark those files as processed by
renaming those files with .p extension.
Page 15 of 36

At regular intervals, a cleanup utility will run that purges the uploaded files after a
configurable period of time.

The physical interface will be Copper GE, operating in active/standby mode using static
routes to interface to the Reliance transport network.

Gi Interface
Provides consumer connection to the Reliance Packet Data Network.
The physical interface considered is via XGLC line card in all locations apart from
Bhopal where QGLC line card has been considered based on throughput requirements.

Gd Interface
This interface is for SGSN to SMSC connectivity for enabling SMS over GPRS. This
interface is not planned in Reliance network.
Gs Interface
This interface is for GGSN to MSC connectivity for enabling NRPCA. This interface is not
planned in Reliance network.
Gf Interface
This interface is for SGSN to EIR connectivity. This interface is not planned in Reliance
network.
AAA interface
Radius interface to AAA for authentication of a subset of customers. No AAA is
envisaged in phase-1 for soft launch.
CGSN will generate the RADIUS accounting messages and will directly send it to the
WAP/MIG gateway.
DNS Interface
SGSN will communicate with the DNS at context activation to determine the list of
GGSNs that can support the requested APN for the new context. This list is cached for
that APN to minimise the impact on the DNS. The GGSN IP address will be provided that
informs the SGSN where to send the context create request to this may be to home
GGSNs or foreign network GGSNs.

This will be shared with the Gn interface.

LI Interface
The LI interface will connect to the existing Verint LIM Server. The physical interface
will be Copper GE, operating in active/standby mode using static routing to the routers.
Page 16 of 36

O&M
The O&M interface is used for administrative access to the ASR5000 node (both by CLI
and GUI), performance counter offload to the WEM, NTP updates, and alarm reporting.
The alarms generated by CGSN will be collected and displayed on the TTI server as well
as Ciscos WEM. Alarms will be communicated via SNMP.

The physical interface will be Copper GE, operating in active/standby mode using Static
Routing to interface to the O&M routers.

Performance Statistics
CGSN performance statistics (bulkstats) are sent to the TTI server via Ciscos WEM. The
data is CSV formatted. Sampling and transfer intervals are configurable. Bulkstats files
are delivered by each ASR5000 CGSN into a dedicated directory of WEM. TTI will pull
the bulkstats data from WEM and generate the necessary performance reports.

Page 17 of 36
7 Current 2G Network
Reliance has 4 packet core locations currently for GERAN network. RCOM (Reliance
Communications) has 2 packet core locations, Mumbai and Bangalore. Mumbai has one
SGSN and one GGSN while Bangalore has two SGSNs and one GGSN. RTL (Reliance
Telecom Ltd) has 2 packet core locations, Kolkata and Indore. Each location has one
SGSN and one GGSN.

7.1 SGSN (Serving GPRS Support Node)

For RCOM, SGSN to circle mapping is as following:
Mumbai SGSN
o
o
o
o
o
o
o
Delhi
Haryana
J&K
Maharashtra
Mumbai
Punjab
Rajasthan

Bangalore SGSN
o
o
o
o
o
o
o
o
Andhra Pradesh
Chennai
Karnataka
Kerala
Tamilnadu
Gujarat
Uttar Pradesh(E)
Uttar Pradesh(W)

For RTL, SGSN to circle mapping is as following:

Kolkata SGSN
o Bihar
o Jharkhand
o Assam
o North East
o North Bengal
o South Bengal
Page 18 of 36

o Kolkata

Indore SGSN
o
o
o
o
Madhya Pradesh
Chattishgarh
Orrisa
Himachal Pradesh

SGSN connects to HLR and IN (Intelligent Network) over IP interface via STP. SGSN
connects to multiple STPs in different geographical locations to provide redundancy.
Below diagram captures current HLR and IN connectivity for RCOM:

Figure: RCOM existing HLR & IN connectivity

7.2 GGSN (Gateway GPRS Support Node)

Reliance 2G network has 4 GGSNs (2 RCOM + 2 RTL), located at Mumbai, Bangalore,
Kolkata and Indore. GGSN connects to RDN (Reliance Data Network IP/MPLS core) for
WAP, MMS, Blackberry and Internet services.

WAP, MMS and Blackberry services are centralized in Mumbai, so traffic for these
services is aggregated at Mumbai location. Separate instance of WAP GW are used for
Page 19 of 36

RCOM and RTL traffic. RCOM GGSN connects to the RCOM WAP GW at Mumbai via RDN.
RTL GGSN connects to the RTL WAP GW at Mumbai via RDN.

For Internet connectivity, links are decentralized at GGSN locations. Traffic meant for
Internet is routed to IAG (Internet Aggregation Gateway) and from there to public
Internet.

GGSNs are configured in pool to provide redundancy. SGSN can route the traffic to
secondary GGSN in case of primary GGSN fails.

Following table illustrates the APN being used in current RCOM and RTL networks.
Same APN is used for postpaid and prepaid subscribers. Same APNs are envisaged to be
used in 3G networks as well.

Service
Internet
WAP
MMS
Blackberry
WDVPN
RCOM
RCOMNET
RCOMWAP
RCOMMMS
blackberry.net
RCOMVPN
APN
RTL
SMARTNET
SMARTWAP
MMS
blackberry.net

7.3 Charging Gateway

In existing network 3 CGs (2 RCOM and 1 RTL) are deployed to cater 4 PS core locations.
CGs are located at Mumbai, Bangalore and Kolkata, with following mapping:
Mumbai CG serves Mumbai SGSN/GGSN

Bangalore CG serves Bangalore SGSN/GGSN
Kolkata CG serves Kolkata and Indore SGSN/GGSN

All CGs connect to central mediation server in Mumbai and provide the CDR in 3GPP R4
format. S-CDRs are used for subscriber billing for offline charging.

7.4 Lawful Interception

All SGSN and GGSN are integrated with LI system provided by Verint. Active mode of
interception is being used. Necessary licenses have been provisioned on the ASR5000
SGSN/GGSN for active LI. Reliance needs to ensure necessary SW/HW from Verint for
this integration, as Verint would require a mediation specific to ASR5000.

Connectivity between the SGSN/GGSN and Verint mediation is provided via DCN
(Reliance Management Network) network.

Page 20 of 36
7.5 HLR
In existing network HLR is provided by HP and Huawei in Mumbai, Faridabad, Kolkata

and Hyderabad, while STP is provided by Tekelec. All SGSNs connect to STP for HLR
connectivity over SIGTRAN. All signaling traffic to HLR is routed via STP.

STPs are located at Mumbai, Faridabad, Kolkata and Hyderabad.

Mumbai SGSN is connected to Mumbai & Faridabad HLR via Mumbai STP & Faridabad
STP respectively.

Bangalore SGSN is connected to Kolkata & Hyderabad HLR via Kolkata & Hyderabad STP
respectively.

HLR & STP of Mumbai & Faridabad work in a mated pair. Similarly, HLR & STP of
Kolkata & Hyderabad work in a mated pair.

7.6 Intelligent Network

In existing network IN is provided by Comverse in Mumbai, Faridabad, Kolkata &
Chennai locations. All SGSN connect to respective IN systems through STP.

CAP-3 protocol is being used for online charging of RCOMNET APN (for internet
service), providing real time charging based on time and volume.

7.7 NMS (Network Monitoring System)

SGSN and GGSNs are connected to central NMS (TTI) for real time system monitoring
and reporting for fault, diagnostics, administration and performance reporting.

Page 21 of 36
8 ASR5000 CGSN Deployment and 2G APN Migration (Soft-

Launch)

In this phase, following is planned:
Deploy CGSN and integrate all planned interface in the network

Connect RNCs to CGSN using IuPS interface
Enable all existing 2G APNs and services
Enable DIAMETER Gy charging for 2G/3G prepaid subscribers.
Enable eGCDR based charging for postpaid subscribers
ASR5000 will serve softlaunch traffic as mentioned in subsequent paragraph below.

It is assumed that Radio coverage would be limited to few Node-Bs which will be homed
to 3G RNC to ASR5000 CGSN. The 2G subscribers having 3G enabled device can latch to
3G RAN. Reliance will have to ensure that service/billing for such subscribers are
handled properly.

Direct Tunnel will be used for home network, for which 80% of the traffic has been
considered. 20% of the traffic has been considered for roamers for which traditional
two-tunnel architecture would apply.

It is assumed that following will be provided by Reliance for soft launch:
L2/L3 Switch
Existing DNS would be used for APN Resolution
No GRX planned in Soft launch. Existing connecitivity towards GRX may be used
Firewall in not planned for soft launch

inPilot is not required for soft-launch, and existing EMS at Mumbai (for PDSN) will be used for
3G as well.

For soft-launch, following capacities are considered, based on inputs from Reliance:
Mumbai and Kolkata combined throughput (for 2G) = 150Mbps
Mumbai and Kolkata combined PDPs (for 2G )= 100K
No 2G SGSN. 2G RAN will continue to be homed to existing Huawei SGSNs
3G traffic for 20K subscribers. i.e.:
o 3G SAU = 20K x 70% = 14K SAUs
o 3G PDP = 14K x 30%*1.3 = 5.5K PDPs
o 3G Throughput = 5.5K x 30kbps x 50% = 83 Mbps

In order to cater to above capacity for soft-launch, only 2 PSC1 active cards will suffice.
However, keeping various connectivity requirements into consideration, 4 active PSC1 cards
Page 22 of 36

(total 6: 4+1+1; 4 Active, 1 Standby and 1 Session Recovery), 1 active QGLC (total 2: 1 Active,
1 Standby), 1 active GELC (total 2: 1 Active, 1 Standby) and 2 active FELC (total 4: 2 Active, 2
Standby). Detailed BoM for ASR5000 considering soft-launch requirement is as attached.

Reliance 3G-2G BoM
for Soft-launch.xls
8.1 Charging
8.1.1 Post-paid Charging
For home subscribers, GGSN eG-CDRs shall be used for offline charging.

Charging Characteristics field (CC=08) in the CDR would indicate whether the
subscriber is prepaid or postpaid and apply further treatment accordingly. Custom6
dictionary will be used for S/e/G-CDRs. File format for the CDR should be Custom3.

CDR storage will be done on the SMC HDD. ASR5000 SMC provides 100GB of storage
capacity. Reliance mediation would be required to FTP the CDR files from SMC HDD, and
rename the .u files to .p after successful transfer to Mediation. ASR5000 will purge the
processed files with .p extension after a pre-configurable period of time. Separate
directory for S-CDR and e/G-CDR would be created.

Mumbai CGSN is planned to be carrying maximum traffic, where the requirement is to
serve 335K 3G PDPs and 200K 2G PDPs, i.e. total 535K PDPs. With session DR for 3G,
PDP capacity for Mumbai CGSN goes to 797K PDPs.

Assuming 1.6M sessions during busy hour and 2 CDR per session, the system would
generate 3.2M CDRs during the busy hour. Assuming a 24 hours day to be equivalent to
18 busy hours, total of 57.6M CDRs would be generated per day. Based on further
assumption of average 350 byte CDR size, the total storage requirement for a day works
out to 20 GB. Based on these calculations, on board HDD can support up to 5 days of
CDR storage (290M CDRs).

In current 2G network, post-paid charging is done via SGSN S-CDRs. S-CDRs will
continue to be used for subscribers accessing GERAN via Huawei SGSNs, and GGSN
CDRs generated by ASR5000 would be ignored for such PDPs. If the subscriber is served
by ASR5000 SGSN, then GGSN CDRs will be processed and S-CDR from ASR5000 will be
filtered out for home subscribers. Sample CDRs are attached for reference.

Text Format:
Page 23 of 36
GCDR/eGCDR:

SCDR:
SCDR:
ASN.1 Format:
GCDR/eGCDR:

8.1.2 Pre-paid Charging
DIAMETER based Gy interface will be used for online charging for 2G and 3G
subscribers on ASR5000 GGSN.

Charging Characteristics with value 04 would indicate subscriber type as prepaid.
Based on CC, the GGSN would derive the subscriber as prepaid and initiate the DCCA.

IN selection for the subscriber will be done statically at the GGSN using MCC/MNC
portion of the IMSI. GGSN has the option to configure the DCCA peers statically and the
selection can be based on IMSI prefix/suffix (MCC/MNC).
It is not possible to select different set of OCS servers for online charging of postpaid
subscribers without AAA/PCRF integration, where AAA/PCRF could return the OCS IP
address per subscriber.

In current 2G network, prepaid charging is done over CAMEL for Internet services.
However, prepaid charging is planned over DIAMETER Gy for all prepaid subscribers in
Cisco ASR5000 CGSN, as it enables flexible charging. With the introduction of Cisco
ASR5000 CGSN in the network, CAMEL based prepaid charging will be migrated to
DIAMETER based Gy charging:
Remove GPRS-CSI (GPRS CAMEL Subscription Information) from HLR profile for
prepaid subscriber, so that CAMEL charging from Huawei SGSN is discontinued
o Above may not be required if CAMEL service is not configured in the SGSN,
the SGSN will not send the CAMEL capability in the Update GPRS Location
Message to the HLR. So, HLR should not send the GPRS-CSI to SGSN. Even if
GPRS-CSI is received from HLR, SGSN will ignore it if CAMEL service is not
configured on the SGSN.
Ensure that CC (Charging Characteristics) for prepaid subscribers is configured as
04 in HLR, so that GGSN recognizes the subscriber as prepaid and initiates DCCA
charging
Page 24 of 36

Based on the CC profile, the GGSN would invoke the rulebase with DCCA charging as
discribed above.
Reliance to align the CAMEL migration to DIAMETER Gy accordingly for 2G
subscribers

Following table illustrates the charging scenarios for various subscriber types:

Subscriber
Type
Charging
Characte-
ristics
CAMEL
CSI
Cisco SGSN
Cisco GGSN
2G Prepaid
ON
NA
2G Postpaid
OFF
NA
CAP3 not invoked.

Gy based on CC=4
S-CDR
3G Prepaid
ON
CAP3 not invoked.

Gy based on CC=4
CAP3 not invoked. Gy

based on CC=4
3G Postpaid
OFF
GGSN CDR
Softlaunch Cisco
CGSN. SGSN serves
only 3G RNCs. GGSN
serves 3G traffic and
2G traffic from
Mumbai & Kolkata
SGSNs
S-CDR
Huawei SGSNs of
Mumbai, Kolkata
They will resolve to
Cisco GGSN. CAMEL
config will be disabled
on these SGSNs, and
will not invoke CAMEL
charging
Remarks
Huawei SGSN
Cisco GGSN
Huawei SGSN
Huawei GGSN
CAMEL
S-CDR
CAMEL
S-CDR
Huawei SGSNs of
Bangalore &
Indore - they will
continue to
resolve to Huawei
GGSN and use
CAMEL charging

For prepaid Gy integration with Comverse IN, following two gaps have been identified during
lab testing:
1) Comverse OCS does not send AVP supported-vendor-id=10415 (indicating 3GPP
compliant) in Capability Exchange Answer (CEA) message; because of which Cisco
GGSN does not send the PS-Info AVP in the CCR message
2) Comverse OCS expects only Granted Service Units to be reported back in CCR
messages from Cisco GGSN.
Cisco will be providing the fix for above two issues.

Quota Holding Timer (QHT) will be disabled in the implementation to avoid issues related to
CCR/CCA-updates as observed during lab testing.

Page 25 of 36
8.2 Services
8.2.1 Internet
Current 2G APN (RCOMNET, SMARTNET) for Internet access will be used. ASR5000
CGSN will be connected to RIN (Reliance Internet Network) for providing Internet
connectivity to 3G/2G subscribers.

There will be a separate context configured on ASR5000 for Gi internet APN. eBGP
would be configured on the Gi-internet interface on CGSN and IPEs on RIN network. For
commercial launch, we would have eBGP multi-hop along with static routing to enable
BGP peering with an IP in a different network due to introduction of Firewall in
between.
8.2.2 WAP
Current 2G APN (RCOMWAP, SMARTWAP) for WAP GW will be used. ASR5000 CGSN
will be connected to RDN (Reliance Data Network) for providing WAP connectivity for
3G/2G subscribers.

Current 2G network does not use S-CDR/G-CDR for transport charging for WAP, and it is
being done by WAP GW. With ASR5000 CGSN, transport charging will be done using
GGSN CDRs for postpaid subscribers and using DIAMETER Gy for prepaid subscribers.

RADIUS dictionary used will be Starent. ASR5000 GGSN will need to send RADIUS
accounting to the WAP GW so that WAP GW could create subscriber IP address to IMSI
mapping.
A separate context will be used on the CGSN for WAP & MMS APN. Static routing would
be used for these APNs to point to the VRRP address of the PE on the appropriate VLAN.
8.2.3 MMS
Current 2G APN (RCOMMMS, MMS) for MMS service will be used. ASR5000 CGSN will be
connected to RDN (Reliance Data Network) for providing WAP/MMSC connectivity for
3G/2G subscribers.
A separate context will be used on the CGSN for WAP & MMS APN. Static routing would
be used for these APNs to point to the VRRP address of the PE on the appropriate VLAN.

8.2.4 Blackberry
Current 2G APN (blackberry.net) for WAP GW will be used. ASR5000 CGSN will be
connected to RDN (Reliance Data Network) for providing Blackberry connectivity for
3G/2G subscribers.
A separate context will be used on the CGSN for Blackberry APN. Static routing would be
used for these APNs to point to the VRRP address of the PE on the appropriate VLAN.

Page 26 of 36

8.2.5 WDVPN
Current 2G APN (RCOMNET) will be used for providing WDVPN services to customers
like banks, AMR etc. Existing LNS will be used for terminating L2TP tunnel.

8.2.6 Roaming
Gn IP addresses of SGSN/GGSN will be advertized to GRX and existing connectivity to
GRX will be used.
In-roamers accessing services via 2G RAN will be using existing Huawei SGSN and
foreign GGSN. In-roamers accessing services via 3G RAN would use ASR5000 SGSN and
foreign GGSN. In this scenario the S-CDRs from SGSN will be processed for in-roamers
billing.
Out-roamers will use ASR5000 GGSN for PDP establishment and subsequently accessing
PS services. GGSN CDRs will need to be processed for such subscribers. Based on SGSN
IP address, or User-Location-Information, foreign network could be indentified. For
prepaid subscribers, Gy charging will happen from ASR5000 GGSN.
It is assumed that ASR5000 CGSN IP addresses are already advertised to roaming
partners and connectivity through existing BG is in place.

8.3 Deep Packet Inspection (DPI)

DPI will be enabled on the ASR5000 GGSN for both prepaid/postpaid subscribers for
flow based differential charging.

Based on RAT type, session based charging can be done for 2G subscribers. For post-
paid 2G subscribers, eGCDR will be generated with single rating-group. For 3G
subscribers, flow level usage reporting would apply.

It is not possible to enable DPI selectively for 2G or 3G subscriber (for any set of
subscribers) without returning subscriber profile from external source like AAA/PCRF,
as GGSN is not aware of the subscriber type (2G or 3G). This can only be possible
(without AAA/PCRF) on GGSN if separate APN is used for 2G and 3G subscribers.

8.4 PCRF
PCRF can be invoked from ASR5000 GGSN at APN level. Since 3G and 2G subscribers
will use common APN for a particular service, policy request to PCRF would be sent for
all subscribers accessing that APN.
PCRF is not planned for soft-launch. It will be available at commercial launch.

Page 27 of 36
8.5 Mediation Interface for CDR Handling
Custom6 GTPP dictionary will be used in the ASR5000. GGSN CDRs will be used for
billing.
Mediation interface for SGSN/GGSN CDR handling has been discussed with NPE and
mediation/billing team and clarifications to all queries have been provided.

Page 28 of 36
9 WAP/MIG Integration
Reliance intends to deploy Mobile Internet Gateway as part of up-gradation of current
WAP infrastructure serving 2G and CDMA 1X/DO Service to 3G Services strategy, which
will help Reliance provide mobile internet data service for WAP Subscribers with WAP
2.0 and WAP 1.0 handhelds.
The Mobile Internet Gateway is intended to be deployed / co-located with Packet Core
location ie. Mumbai, Delhi, Kolkata & Bhopal. MIG will not be applicable at soft launch.
9.1 Challenge
1. The existing hand held devices of subscribers are configured with 10.239.221.5 IP
address which belongs to existing WAP gateway deployed in Mumbai.
2. The hand held devices of existing subscribers cannot be changed with the planned new
IP Address, this requires manual intervention of the subscriber and success rate is
expected to be very low.
3. Geographical Redundancy of the MIG platform is planned as follows and needs to be
supported:-
a. Mumbai Delhi
b. Kolkata Bhopal
9.2 Physical Connectivity

1. 2 x 1 Gigabit Ethernet Ports per Load Balancer is required per Cisco 7609 Router-cum-
switch = 2 (7609 Switch) x 2 (Load Balancer) = 4 Ports
2. Physical Connectivity would be based on Copper Interface

9.3 Logical Link and Routing Protocol

1. HSRP would be implemented at Cisco 7609 Router end being connected to Load
Balancer and VRRP would be used at Load Balancer end
2. Two different VLANs would be configured between Load Balancer and Cisco 7609
Router
9.4 Solution and Role of Cisco

1. Packet Core external Firewall proposed as part of the Packet Core solution will be used
to for Destination based NAT of the existing 10.239.221.5 IP address with the new IP
address of local MIG Load balancer Virtual IP Address and would be routed toward the
local interface
Page 29 of 36

2. Geographical redundancy of the MIG platform would be NAT with the destination IP
address and would be routed towards the Reliance Data Network (RDN) with higher
link weight
3. The Egress traffic coming from the MIG platform would be routed from MIG load
balancer to Packet Core firewall which in turn would be routed towards the Reliance
Data Network (RDN) and Reliance Internet Network (RIN) for On-Net and Off-Net
content access.
4. The Physical connectivity is explained in the Figure 5

Reliance Data
Network (RDN)
Reliance Internet
Network (RIN)
Firewall-A
Firewall-B
10-GigE
Interface
10-GigE
Interface
10-GigE
Interface
10-GigE
Interface
Cisco
7609-A
10-GigE Interface
10-GigE Interface
NAT of 221.5 (Old WAP) IP with MIG IP at

Packet core Firewall
Primary Local NAT IP of MIG to be routed
towards Big F5
Secondary MIG DR NAT IP to be routed
towards RDN
10-GigE Interface
10-GigE Interface
VLAN-MIG-A1
Big F5-A
Ingress to MIG
VLAN-MIG-A2
Ingress and Egress will flow using the same VLAN
GGSN
Common Trunk
Cisco
7609-B
VLAN-MIG-A1
Big F5-B
VLAN-MIG-A2
Ingress and Egress will flow using the same VLAN
Figure 5: Architecture of MIG and Packet Core
egress from MIG
9.5 Charging
1. Pre-Paid subscribers are charged currently for Transport usage through Reliance in-
house charging platform called RTCI (Real Time Charging Interface) and Content is
charged through the IN Platform
2. Post-Paid subscribers are charged currently for transport usage through S-CDR and G-
CDR
9.6 Scope Classification for MIG / Dependencies

1. Starent has shared the RADIUS accounting details will all attributes present in RADIUS
accounting message from ASR5000 GGSN
Page 30 of 36

2. Public IP Address allocation for Network Element and their subsequent routing to be
provided by Reliance Comm
3. End to end Service testing / Charging testing to be organized by Reliance Comm.

10 GERAN Migration from Huawei SGSN to ASR5000 CGSN (Phase-
2)

In this phase, 2G RAN currently homed to Huawei SGSN will be migrated to ASR5000
CGSN over a period of time. As well as, traffic from Bangalore and Indore Huawei GGSN
will be migrated to ASR5000. With new Packet Core locations, following 2G homing will
apply:

SGSN
Location
Mumbai
Delhi-1
Delhi-2
Kolkata
Bhopal
Circle
GUJARAT
MAHARASHTRA + GOA
MUMBAI
RAJASTHAN
DELHI
HARYANA
JAMMU & KASHMIR
PUNJAB
UP E
UP W
ANDHRA PRADESH
CHENNAI
KARNATAKA
KERALA
TAMIL NADU
ASSAM
BIHAR + Jharkhand
KOLKATA
North-East
WEST BENGAL
HIMACHAL PRADESH
MADHYA PRADESH + CG
ORISSA
# 2G
Cells
30519
31314
36306
22956
13527
Circles highlighted in green carry 3G-traffic as well.
Page 31 of 36
11 CGSN Expansion 1 (Jan2014)

With growing traffic demand, Reliance has planned to expand the 2G/3G packet core capacity.
Cards expansion in existing chassis is planned, and no new site is planned. Delhi-1 site will be
equipped with PSC3, while other 4 CGSNs will be equipped with PSC2s.
11.1 Hardware & Software Augmentation

Following table illustrates the node wise hardware details as per original deployment in year
2010:

Part Number
Part Description
Location
Mumbai
Delhi-1
Delhi-2
Kolkata
Bhopal
Hardware
ASR5000-CHS-SYS-K9
ASR-5000 Multimedia Core Platform Complete Chassis
ASR5K-SMC-K9
System Management Card 4GB
ASR5K-SPS3-BNC-K9 Switch Processor I/O, BNC BITS with Stratum 3
ASR5K-RCC-K9
ASR5K-PSC-32G-K9 Packet Services Card (PSC2) 32GB
14
ASR5K-C4OC3-SM-K9 Channelized

4-Port STM-1/OC-3 Line Card w/SM SFP
ASR5K-041GE-T-K9 4-Port Ethernet 1000 with Copper SFP
ASR5K-0110G-MM-K9 XGLC 1-Port 10 Gigabit Ethernet Line Card w/MM SFP+

Spares
Redundancy Crossbar

Based on the network requirements, some PSC cards were re-shuffled in the field, and
following table provides the current PSC configuration as on date:

Part Number
Part Description
Mumbai
13
Delhi-1
12
Location
Delhi-2
3
Kolkata
12
Bhopal
5

Following table illustrates node wise delta hardware & software augmentation planned as per
expansion-1:

Part Number
Hardware
ASR5K-PSC-64G-K9=
ASR5K-0110G-SM-K9=
Spares
ASR5K-PSC-64G-K9=
ASR5K-PSC-32G-K9=
Software
ASR5K-00-SN01SESS
ASR5K-00-GN01SESS
ASR5K-00-CS01ECG2
Part Description
Packet Services Card (PSC3) 64GB
XGLC 1-Port 10 Gigabit Ethernet Line Card w/SM SFP+
SGSN 1K SW licenses, 1K Sessions
GGSN 1K SW licenses, 1K Sessions
Enhanced Charging Bundle 2, 1K Sessions
Mumbai
Delhi-1
Location
Delhi-2
Kolkata
Bhopal
14
2
94
94
78
75
75
111
16
16
11
10
10
95

20
20
20
Page 32 of 36

ASR5K-00-CS01PIF
LIF5K-00-SN01SESS
LIF5K-00-GN01SESS
LIF5K-00-CS01ECG2
LIF5K-00-CS01PIF
Policy Interface, 1K sessions

SGSN 1K SW licenses
GGSN 1K SW licenses
Enhanced Charging Bundle 2 per 1K License
Policy Interface, 1K sessions
20
20
20
20
20
158
94
94
78
158

154
0
0
0
0
13
16
16
11
13
143
10
10
95
143

Delhi-1 chassis is planned to have 14 PSC3 cards as per expansion-1, and the freed up PSC2s
from this chassis will be distributed to other locations. And final HW configuration will be as
per following table:

Part Number
Part Description
Hardware
ASR5000-CHS-SYS-K9
ASR-5000 Multimedia Core Platform Complete Chassis
ASR5K-SMC-K9
System Management Card 4GB
ASR5K-SPS3-BNC-K9 Switch Processor I/O, BNC BITS with Stratum 3
ASR5K-RCC-K9
Redundancy Crossbar
ASR5K-PSC-64G-K9=
ASR5K-C4OC3-SM-K9 Channelized

4-Port STM-1/OC-3 Line Card w/SM SFP
ASR5K-041GE-T-K9 4-Port Ethernet 1000 with Copper SFP
ASR5K-0110G-MM-K9 XGLC 1-Port 10 Gigabit Ethernet Line Card w/MM SFP+
ASR5K-0110G-SM-K9= XGLC 1-Port 10 Gigabit Ethernet Line Card w/SM SFP+
Mumbai
Delhi-1
1
2
2
2
13
1
2
2
2
0
14
0
4
4
2

0
6
4
2
Location
Delhi-2
Kolkata
Bhopal
1
2
2
2
7
1
2
2
2
14
1
2
2
2
13

0
6
0
4

2
6
4
2

2
8
0
4
11.2 Capacity Details

Location wise capacity details as per original deployment done in year 2010:

SGSN
Mumbai
Delhi-1
Delhi-2
Kolkata
Bhopal
Total
2000
2000
960
620
5580
1530.62
1530.62
0.00
767.37
767.37
4595.98
3530.62
1530.62
2000.00
1727.37
1387.37
10175.98
PDP 2G (K)
200
200
101
90
591.00
PDP 3G (K)
596.94
596.94
0.00
299.27
299.27
1792.42
796.94
596.94
200.00
400.27
389.27
2383.42
Throughput 2G (Gbps)
0.25
0.00
0.25
0.10
0.10
0.70
Throughput 3G (Gbps) [20% non-DT]
1.00
0.83
0.00
0.70
0.25
2.78
1.25
0.83
0.25
0.80
0.35
3.48
Mumbai
200
596.94
796.94
0.25
5.00
5.25
Delhi-1
0
596.94
596.94
0.00
4.15
4.15
Delhi-2
200
0.00
200.00
0.25
0.00
0.25
Kolkata
101
299.27
400.27
0.10
3.50
3.60
Bhopal
90
299.27
389.27
0.10
1.23
1.33
Total
591.00
1792.42
2383.42
0.70
13.88
14.58
SAU 2G (K)
SAU 3G (K)
Total SAU
Total PDP
Total Throughput

GGSN
PDP 2G (K)
PDP 3G (K)
Total PDP
Total Throughput
Page 33 of 36

Location wise delta capacity enhancements as per Expansion-1:

SGSN
SAU 2G (K)
SAU 3G (K)
Total PDP
Total Throughput
Mumbai
0
0.00
0.00
28
12
40.00
0.53
0.05
0.57
Delhi-1
0
0.00
0.00
56
132
188.00
1.10
0.51
1.61
Delhi-2
0
0.00
0.00
75
0
75.00
2.75
0.00
2.75
Kolkata
0.00
0.00
0.00
10
22
32.00
0.87
0.41
1.28
Bhopal
0.00
0.00
0.00
6
14
20.00
1.40
0.65
2.05
Total
0.00
0.00
0.00
175.00
180.00
355.00
6.64
1.62
8.26
GGSN
Mumbai
Delhi-1
Delhi-2
Kolkata
Bhopal
Total
Total SAU
PDP 2G (K)
PDP 3G (K)

PDP 2G (K)
28
56
75
10
175.00
PDP 3G (K)
12
132
22
14
180.00
40.00
188.00
75.00
32.00
20.00
355.00
0.53
1.10
2.75
0.87
1.40
6.64
0.23
2.56
0.00
2.03
3.27
8.08
0.75
3.65
2.75
2.90
4.67
14.72
Total PDP
Total Throughput

Location wise revised capacity post Expansion-1:

SGSN
SAU 2G (K)
Mumbai
2000
Delhi-1
0
Delhi-2
2000
Kolkata
960
Bhopal
620
Total
5580.00
SAU 3G (K)
PDP 2G (K)
PDP 3G (K)
1530.62
3530.62
228
609
1530.62
1530.62
56
729
0
2000.00
275
0
767.37
1727.37
111
321
767.37
1387.37
96
313
4595.98
10175.98
766.00
1972.42
Total PDP
Total Throughput
836.94
0.78
1.05
1.82
784.94
1.10
1.34
2.44
275.00
3.00
0.00
3.00
432.27
0.97
1.11
2.08
409.27
1.50
0.90
2.40
2738.42
7.34
4.40
11.74
Mumbai
Delhi-1
Delhi-2
Kolkata
Bhopal
Total
228
56
275
111
96
766.00
Total SAU

GGSN
PDP 2G (K)
PDP 3G (K)
609
729
322
313
1972.42
836.94
784.94
275.00
432.27
409.27
2738.42
0.78
1.10
3.00
0.97
1.50
7.34
5.23
6.71
0.00
5.53
4.50
21.96
6.00
7.80
3.00
6.50
6.00
29.30
Total PDP
Total Throughput
Page 34 of 36
11.3 Features and Functionality

Existing features and functionality as deployed will continue, and there is no plan to add any
new features, barring capacity augmentation for PSCs and Line Cards.

Page 35 of 36

< End of Document >
Page 36 of 36

Reliance 2G-3G PS Core HLD Ver 2.0 PDF

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

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

Reliance 2G-3G PS Core HLD Ver 2.0 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

!

Cisco 2G/3G Mobile Packet Core Solution

Sept 07, 2010

Sept 22, 2010

Jan 13, 2014

2G/3G Mobile Packet Core Solution Document

2G/3G Mobile Packet Core Solution Document

functions can all run at the same time.

Figure 1 Front View of Cisco ASR5000 System

2G/3G Mobile Packet Core Solution Document

2G/3G Mobile Packet Core Solution Document

2G/3G Mobile Packet Core Solution Document

3 Hardware Configuration and Redundancy

2G/3G Mobile Packet Core Solution Document

a potentially small number of subscribers is using the network resources in such an

2G/3G Mobile Packet Core Solution Document

4.1 Inline Services Reporting Solution (inPilot)

4.2 inPilot Reports

Historical summary reports (Daily/Weekly/Monthly)

Statistical and analytical reports

2G/3G Mobile Packet Core Solution Document

2G/3G Mobile Packet Core Solution Document

2G/3G Mobile Packet Core Solution Document

Table 1 Connecting Nodes Version Information

2G/3G Mobile Packet Core Solution Document

IuPS-Control (IuPS-C) Interface

IuPS User (IuPS-U) interface

2G/3G Mobile Packet Core Solution Document

2G/3G Mobile Packet Core Solution Document

2G/3G Mobile Packet Core Solution Document

2G/3G Mobile Packet Core Solution Document

7.1 SGSN (Serving GPRS Support Node)

2G/3G Mobile Packet Core Solution Document

7.2 GGSN (Gateway GPRS Support Node)

2G/3G Mobile Packet Core Solution Document

7.3 Charging Gateway

Mumbai CG serves Mumbai SGSN/GGSN

7.4 Lawful Interception

2G/3G Mobile Packet Core Solution Document

In existing network HLR is provided by HP and Huawei in Mumbai, Faridabad, Kolkata

7.6 Intelligent Network

7.7 NMS (Network Monitoring System)

2G/3G Mobile Packet Core Solution Document

8 ASR5000 CGSN Deployment and 2G APN Migration (Soft-

Deploy CGSN and integrate all planned interface in the network

2G/3G Mobile Packet Core Solution Document

2G/3G Mobile Packet Core Solution Document

2G/3G Mobile Packet Core Solution Document

CAP3 not invoked.

CAP3 not invoked.

CAP3 not invoked. Gy

2G/3G Mobile Packet Core Solution Document

2G/3G Mobile Packet Core Solution Document

8.3 Deep Packet Inspection (DPI)

2G/3G Mobile Packet Core Solution Document

8.5 Mediation Interface for CDR Handling

2G/3G Mobile Packet Core Solution Document

9.2 Physical Connectivity

9.3 Logical Link and Routing Protocol

9.4 Solution and Role of Cisco

2G/3G Mobile Packet Core Solution Document

NAT of 221.5 (Old WAP) IP with MIG IP at