Reliance Communications
INTEGRATED SERVICES PDSN Engineering DocumentDocument No:
C1-NW6-100-041
2007 Reliance Communications
CDMA Packet Data Network PDSN
1
Table of Contents1.
INTRODUCTION...........................................................................41.1
Purpose
...................................................................................4
1.3 Change
History...........................................................................4
2.
PACKET DATA NETWORK OVERVIEW
..........................................................5
2.1 Mobile Node /
Station..................................................................5
2.2 Radio Access
Network..................................................................6
2.3
PDSN.......................................................................................7
3. PDSN
OVERVIEW....................................................................7
4. LOCATION
DETAILS......................................................................124.1
Port & IP
Details:......................................................................12
4.2 Network
Diagram:.....................................................................13
5. CONFIGURATION DETAILS
................................................................145.1
Setting System
Information..........................................................14
5.2 Adding IP Network to a
Interface....................................................14 5.3
Setting RP
Interface...................................................................15
5.4 Setting IP Application Source
Address..............................................15 5.5 Adding
PCF in
PDSN....................................................................15
5.6 Setting AAA
Servers....................................................................16
5.7 Adding IP User
Pools...................................................................17
5.7 Adding IP
Routes.......................................................................17
6. WIRELESS 3G DATA SYSTEM
COMPONENTS.................................................176.1
Total Control 1000
Chassis...........................................................17
7. SPECIFICATIONS
OF
TC
1K..............................................................21
8.
APPENDIX..............................................................................238.1
FACN.....................................................................................23
8.2 Connectivity & Sample configuration of PDSN with
PCF.........................25 8.3 PDSN Interface IP
Details.............................................................30
8.4 PDSN User Pool
Details................................................................33
Mumbai:......................................................................................33
8.5 Mobile
IP................................................................................38
2007 Reliance Communications Ltd. CDMA Packet Data Network PDSN
2
8.6 Connectivity to Private
Network....................................................40 8.7
Important Service Orders for Future
Reference..................................41
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
3
1. INTRODUCTION
1.1 PurposeThe purpose of the document is to provide details of
architecture & configuration of PDSN installed at IDC-Hub
(Mumbai) & IDC-1 (Bangalore).
1.3 Change HistoryVersion Number 1.0 2.0 Date Released
Comments
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
4
2. PACKET DATA NETWORK OVERVIEWCDMA is one of the standards for
mobile station communication. A typical CDMA 2000 network includes
mobile station/ mobile node, Base transceiver station (BTS), Base
station controllers (BSC/PCF), PDSNs & other CDMA network &
data Network entities. The PDSN is the interface between a BSC/PCF
& a network router. Once the traffic channel is allocated to
mobile station, PCF will setup an A10-A11 (R-P) connection with
PDSN. After successful R-P tunnel setup, PPP session will be
established between PDSN and mobile station. During PPP
establishment phase, PDSN communicates with RADIUS server for
authentication using RADIUS protocol. The P-I interface of PDSN
acts as a Gateway to the public network. The below figure shows
CDMA 2000 packet data network architecture:
HLR A1
SS7 Network MSCHome Access Provider network
Visited Access Provider network (serving)
RADIUSRADIUS R-P interfacer A10/A11IP network
IP Networkpi
Home IP network
Source RN
Serving PDSNP-P interface
RADIUS
Desktop
R-P interface A10/ A11IP Network
pi
Broker IP
Laptop computer
Target RN Visited Access provider Network (target)
Target PDSN
Cell phone
2.1 Mobile Node / StationIn a cdma2000 1X network, the mobile
stationthe subscribers handsetfunctions as a mobile client. The
mobile station interacts with the Access Network to obtain
appropriate radio resources for the exchange of packets. Upon
power-up, the mobile station automatically registers with the Home
Location Register (HLR) in order to: 1. Authenticate the mobile for
the environment of the accessed network 2. Provide the HLR with the
mobiles current location 2007 Reliance Communications Ltd. CDMA
Packet Data Network PDSN 5
3. Provide the Serving Mobile Switching Center (MSC-S) with the
mobiles permitted feature set. After successfully registering with
the HLR, the mobile is ready to place voice and data calls. These
may take either of two forms, circuit-switched data (CSD) or
packet-switched data (PSD), depending on the mobiles own compliance
(or lack thereof) with the IS-2000 standard. Mobile Stations must
comply with IS-2000 standards to initiate a packet data session
using the1xRTT 1 network. Mobile stations having only IS-95
capabilities are limited to CSD, while IS-2000terminals can select
either the PSD or CSD.
2.2 Radio Access NetworkThe Radio Access Network is the mobile
subscribers entry point for communicating either data or voice
content. It consists of: The air link The cell site tower/antenna
and the cable connection to the Base Station Transceiver Subsystem
(Um) The Base Station Transceiver Subsystem (BTS) The
communications path from the Base Station Transceiver Subsystem to
the base station controller (Abis) The Base Station Controller
(BSC) The Packet Control Function (PCF)
The RAN has a number of responsibilities that impact the
networks delivery of packet services in particular. The RAN must
map the mobile client identifier reference to a unique link layer
identifier used to communicate with the PDSN, validate the mobile
station for access service, and maintain the established
transmission links. The Base Station Transceiver Subsystem (BTS)
controls the activities of the air link and acts as the interface
between the network and the mobile. RF resources such as frequency
assignments, sector separation and transmit power control are
managed at the BTS. In addition, the BTS manages the back-haul from
the cell site to the Base Station Controller (BSC) to minimize any
delays between these two elements. Normally a BTS connects to the
BSC through un-channelized E1 facilities or direct cables in
co-located equipment. The protocols used within this facility are
proprietary and are based on High-level Data Link Control (HDLC).
The Base Station Controller (BSC) routes voice- and
circuit-switched data messages between the cell sites and the MSC.
It also bears responsibility for mobility management: it controls
and directs handoffs from one cell site to another as needed. It
connects to each MTX using channelized E1 lines for voice and
circuit switched data; and to un-channelized T1 lines for signaling
and control messages to the PDSN using the 10BaseT Ethernet
protocol. The Packet Control Function (PCF) routes IP packet data
between the mobile station within the cell sites and the Packet
Data Serving Node (PDSN). During packet data sessions, it will
assign available supplemental channels as needed to comply with the
services requested by the mobile and paid for by the subscribers.
The PCF maintains a reachable state for between the RN and the
mobile station, ensuring a consistent link for packets; 2007
Reliance Communications Ltd. CDMA Packet Data Network PDSN 6
buffers packets arriving from the PDSN when radio resources are
not in place or insufficient to support the flow from the PDSN; and
relays packets between the MS and the PDSN.
2.3 PDSNThe PDSN is the gateway from the RAN into the public
and/or private packet networks. In a simple IP network, the PDSN
acts as a standalone Network Access Server (NAS), while in a mobile
IP network it can be configured as a Home Agent (HA) or a Foreign
Agent (FA). The PDSN does the following activities: 1. Manage the
radio-packet interface between the BSS (Base Station Subsystem =
BTS +BSC) and the IP network by establishing Maintaining and
terminating link layer to the mobile client 2. Terminate the PPP
session initiated by the subscriber 3. Authenticate users locally,
or forward authentication requests to the AAA server 4. Provide an
IP address for the subscriber (either from an internal pool or
through a DHCP server or through an AAA server 5. Perform packet
routing to external packet data networks 6. Collect and forward
packet billing data.
3. PDSN OVERVIEWWhen a mobile station makes a data call, it
establishes a PPP link with the PDSN which authenticates the mobile
station by communicating with AAA server. The AAA server verifies
that the user is a valid subscriber, determines available services
and tracks usage for billing. The method used to assign an IP
address and the nature of the connection depends on service type
and network configuration. Simple IP operation and Mobile IP
operation are referred to as service types. The service type
available to a user is determined by the mobile station, and by the
type of service that the service provider offers. In the context of
PDSN, a mobile station is the end user in both Simple IP and Mobile
IP operation. Once the mobile station is authenticated, it requests
an IP address. Simple IP stations communicate the request using the
Internet Protocol Control Protocol (IPCP). Mobile IP stations
communicate the request using Mobile IP registrations.
3.1 Simple IP Services:With Simple IP, a service providers PDSN
assigns a dynamic or static IP address to the mobile station during
the PPP link setup. The mobile station retains this IP address as
long as it is served by a radio network that has connectivity to
the address-assigning PDSN. Therefore, as long as the mobile
station remains within an area of RANs that is served by the same
PDSN, the MS can move or roam inside the coverage area and maintain
the same PPP links. If the mobile station moves outside the
coverage area of the given PDSN, the mobile station is assigned a
new IP address, and any application-level connections are
terminated. Figure below shows the PDSN Simple IP Scenario. 2007
Reliance Communications Ltd. CDMA Packet Data Network PDSN 7
AAA - Authentication, Authorization, and Accounting PCF - Packet
Control Function PDSN - Packet Data Service Node
VLR
HLR
Home Access Provider Network
Visited AAA
Home AAA
Home Access Provider IP Private NetworkPal To be or m not to be.
That is the Question.
Open R-P InterfacePCF
Home Network
RAN
PDSN
InternetVisited Access Provider NetworkSimple IP Mobility: per
PDSN
A connection is established in following order: 1. A PPP peer
(mobile station) connects with the local NAS (the PDSN). 2. The NAS
begins authentication when the client dials in. The NAS determines
that the PPP link should be forwarded to a tunnel server for the
client. The location of the tunnel server is provided as part of
the authentication by the Remote Authentication Dial-in User
Service (RADIUS) server. 3. The tunnel server performs its own
authentication of the user and starts the PPP negotiation. It
performs authentication for both the tunnel setup and the client.
4. The PPP client is forwarded through a Layer 2 Tunneling Protocol
(L2TP) tunnel over User Datagram Protocol (UDP). 5. The PPP setup
is completed and all frames exchanged between the client and tunnel
server are sent through the NAS. The protocols running within PPP
are transparent to the NAS. Simple IP supports the following AAA
services: PAP and CHAP authentication IP address allocation for the
mobile station Service provisioning based on authorization
information Retrieve realm for MSID based access Accounting session
information
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
8
Call Flow for Simple IP Service:Visited AAA End host
MS1-3TCH setup
PCF
PDSN
4
A10 setup
LCP Configure request 5 LCP Configure-Ack CHAP challenge
7
8 6 CHAP response 9Access request Authenticate Access accept
Framed-IP = a.b.c.d CHAP accept IPCP Configure request 12 IP =
0.0.0.0 IPCP Config-NAK (proposing address) IP = a.b.c.d
10
11
13
14
PPP link open
15
Data flows
3.2 RADIUS:RADIUS stands for Remote Authentication Dial in User
service. It is a standard for performing AAA i.e. Authorization,
Authentication and Accounting services. It provides the following
features: A single database to manage users needing dial-in
connections A client/server platform Network security through
authentication Flexible authentication support
PDSN uses the RADIUS protocol to communicate with the AAA server
to perform Authorization, Authentication and accounting
function.
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
9
Accounting Call Flow:MS1-3TCH setup
PCF
PDSN
Visited AAA
End host
4
A10 setup
LCP Configure request 5 LCP Configure-Ack CHAP challenge
7
8 6 CHAP response 9Access request Authenticate Access accept
Framed-IP = a.b.c.d CHAP accept IPCP Configure request 12 IP =
0.0.0.0 IPCP Config-NAK (proposing address) IP = a.b.c.d
10
11
13
14
PPP link open
15
Data flows
3.2 PDSN Architecture in Reliance Data Network:A Packet Data
Serving Node in CDMA 1XRTT network enables the users to access
Public and Private IP networks using CDMA RAN access. The user can
establish a PPP session from his/her user terminal (Mobile Handset)
to the Packet core network element (PDSN). The mobile handset is
used as a Modem to setup the connectivity. Radius AAA server is
used for user authentication, authorization and session accounting.
The connectivity between the PDSN and AAA is using 100 Base T FE.
Oracle Database Server is used to store and extract customers
database information (e.g. username, password) and accounting logs.
Common Element Manager (CEM) gathers SNMP traffic delivers
management information. The connectivity between the CEM and other
elements is 100 Base T FE.
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
10
Management Switch: We are using 3com 4005 layer three management
Switch for connecting all management port of network element and
the uplink is connected to the DCN network. Nortel Passport is used
separately for R-P interface traffic and Pi interface traffic,
which is the connection, point for the interfaces. The connectivity
between the PDSN on the R-P side with the RAN would be a Gigabit
Ethernet connection. A Gigabit module is placed in the L3 Switch to
connect with the MPLS Backbone Core Edge router. The R-P signaling
and User Data will traverse over the Reliance Fiber Network. The
connectivity between the PDSN on the P-I side with the Public
Internet and Reliance Application Platform (RAP) is based on
Gigabit Ethernet. A Gigabit Ethernet module is placed in the L3
Switch to connect to the edge router on the MPLS WAN. All data
traffic originating from the RAN to the PDSN network via Reliance
MPLS WAN and terminating to/from Public/Private IP Network or
Reliance Application Platform (RAP) is secured by a Firewall. In
Reliance Network, we are using Total Control-1000 (TC-1K) PDSN with
Release 5.4.103.
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
11
4. LOCATION DETAILS 4.1 Port & IP Details:Sr. No. Port IP
Address (Subnet) configured
Device
Connected to
1
Mumbai RP Chassis 1 PI Mumbai RP Chassis 2 PI
97.232.1.0/25 220.224.134.0/27 97.233.1.0/27
220.224.134.32/27
Gateway/VLAN (97.232.1.1/10) connected to RP-1 switch
Gateway/VLAN (220.224.134.1/30) connected to PI-1 switch
Gateway/VLAN (97.233.1.1/20) connected to RP-1 switch Gateway/VLAN
(220.224.134.33/40) connected to PI-1 switch Gateway/VLAN
(97.234.1.1/30) connected to RP-2 switch Gateway/VLAN
(220.224.134.65/50) connected to PI-2 switch Gateway/VLAN
(97.235.1.1/40) connected to RP-2 switch Gateway/VLAN
(220.224.134.97/60) connected to PI-2 switch Gateway/VLAN
(97.236.1.1/10) connected to RP-1 switch Gateway/VLAN
(220.224.135.0/30) connected to PI-1 switch Gateway/VLAN
(97.237.1.1/20) connected to RP-1 switch Gateway/VLAN
(220.224.135.33/40) connected to PI-1 switch Gateway/VLAN
(97.238.1.1/30) connected to RP-2 switch Gateway/VLAN
(220.224.135.65/50) connected to PI-2 switch Gateway/VLAN
(97.239.1.1/40) connected to RP-2 switch
2
Mumbai RP Chassis 3 PI Mumbai RP Chassis 4 PI
97.234.1.0/27 220.224.134.64/27 97.235.1.0/27
220.224.134.96/27
RP Bangalore PI Chassis 1 3 RP Bangalore PI Chassis 2
97.236.1.0/27 220.224.135.0/27 97.237.1.0/27
220.224.135.32/27
4
RP Bangalore PI Chassis 3 Bangalore RP Chassis 4
97.238.1.0/27 220.224.135.64/27 97.239.1.0/27
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
12
PI
220.224.135.96/27
Gateway/VLAN (220.224.135.97/60) connected to PI-2 switch
4.2 Network Diagram:Mumbai: Sr. No. 1. 2. 3. 4. 5. 6. 7. 8 9 10
Device AAA Server 1 AAA Server 2 PDSN CH-1 PDSN CH-2 PDSN CH-3 PDSN
CH-4 PI-1 PI-2 ORACLE PDSN Mgmt. Switch Serial No. 238V0133
0345AM020F 64ML25MB00KB / 15CJG1AD0F25 64MLUAFCA9GL / 15CJGAFC0B3K
64ML25MB00K0 / 15CJ1AD0F2R 64MLUAFCA9GN / 15CJGAC0B3I SSNM001575
SSNM001571 236V035D Rack Status
Rack 53R06 Installed at IDC-Hub Mumbai Rack 53R06 Installed at
IDC-Hub Mumbai Rack 53R01 Installed at IDC-Hub Mumbai Rack 53R03
Installed at IDC-Hub Mumbai Rack 53R07 Installed at IDC-Hub Mumbai
Rack 53R04 Installed at IDC-Hub Mumbai Rack 53R01 Installed Rack
53R07 Installed Rack 53R06 Installed Rack 53R02 Installed at at at
at IDC-Hub IDC-Hub IDC-Hub IDC-Hub Mumbai Mumbai Mumbai Mumbai
Bangalore: Sr. No. 1. 2. 3. 4. 5. 6. 7. 8 9 10 Device AAA Server
1 AAA Server 2 PDSN CH-1 PDSN CH-2 PDSN CH-3 PDSN CH-4 PI-1 PI-2
Serial No. 325V04CB 325V04CB 64ML25MBQ0K6 / 15CJG1AD0F2T
64MLUAFCA9GM / 15CJGAFC0B3L 64ML25MBQ0KG / 15CJG1AD072U
64MLUAFCA9GK / 15CJGAFC0B3J SSNM001576 SSNM001581 Rack Status
Row16Rack7 Installed at IDC-1 Bangalore Row16Rack6 Installed at
IDC-1 Bangalore Row11Rack1 Installed at IDC-1 Bangalore 2
Row16Rack6 Installed at IDC-1 Bangalore Row11Rack1 Installed at
IDC-1 Bangalore 1 Row16Rack7 Installed at IDC-1 Bangalore
Row11Rack12 Installed Row11Rack1 Installed 1 Row16Rack9 Installed
Row16Rack5 Installed at IDC-1 Bangalore at IDC-1 Bangalore at IDC-1
Bangalore at IDC-1 Bangalore13
ORACLE 236V0303 PDSN Mgmt. Switch
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
5. CONFIGURATION DETAILS 5.1 Setting System InformationFor
setting system parameter following is the command syntax: Set
system Contact < name system admin> Location Name
Transmit_authentication_name Here, Contact The Name of the system
administrator Location Location of the System Name Name of the
System Transmit_authentication_name This is the Host Name that will
be used by the PDSN authenticate L2TP/PPTP tunnels to
5.2 Adding IP Network to a Interfaceadd ip network address
enabled {yes| no} This command adds an IP network to the list of IP
networks available over the specified interface. Here, name -
Unique name for this IP network. White space must be surrounded by
double quotes address- IP address of the network, with or without a
mask specifier. The Mask Specifier can be A, B, C or H, or a
numeric value from 8 to 30 (32 for host) that describes the number
of one bits in the mask. You can also specify the netmask in the
xxx.xxx.xxx.xxx format. If you do not specify a mask, the system
will generate it for you from the Enable - Optional parameter
indicates whether network is enabled (YES) or disabled (NO).
Default is Yes Example: add ip network MUMP01C06-rp interFACE eth:1
address 97.232.1.7/25 enabled yes
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
14
5.3 Setting RP Interfaceset rp_interface This command specifies
which ethernet port is connected to the R-P network. This feature
allows the PDSN to filter packets received through a particular
interface (ethernet port). Once an ethernet port is designated as
the R-P network interface, the other ethernet port automatically
assumes the PI network interface. In a packet filter, 0 always
indicates the port attached to the R-P network, and 1 always
indicates the port attached to the PI network. Before entering this
command, the PDSN must first have an IP network configured to
connect to the R-P network.
5.4 Setting IP Application Source Addressset ip
application_source_address {fa | igmp | l2tp_lac | ping | radius |
snmp | syslog | traceroute} pptp_pac |
This command specifies the source IP address (where packets
exit) for various applications of the PDSN. This is necessary when
both ethernet interfaces are used for IP routing or when multi-home
logical networks are configured which need to communicate that
source address. Example: set ip application_source_address fa
220.224.134.7 set ip application_source_address radius
220.224.134.7 set ip application_source_address l2tp_lac
220.224.134.7 set ip application_source_address vha 97.232.1.7
5.5 Adding PCF in PDSNadd vha sa rn_address This command adds a
security association to allow the PDSN to establish RP tunnels with
a Radio Network Node. Use the set vha sa command to configure the
security associations. Here, Sa- Identifies which security
association is being added. Up to 100 security associations can be
added rn_address- The IP address/network of the PCF(s) in IP
address/netmask format. If netmask is omitted the PDSN would
default the netmask to 255.255.255.255
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
15
set vha sa spi shared_secret time_drift type { rp pp} This
command modifies an RP security association between the PDSN and an
RNN/PCF sa- Unique number address of the security association spi-
Security parameter (shared secret number) shared_secret- Shared
secret key for this security association time_drift- Maximum
discrepancy, in seconds, between the timestamps of the Packet Data
Serving Node and the Radio Network Node type-Specifies whether this
security association is for a Radio Node to PDSN interface (rn), or
for a PDSN to PDSN interface (pp). PDSN to PDSN interfaces are used
for fast hand-offs between PDSNs. Example: set vha sa 1 spi 256
shared_secret vhasecret time_drift 255
5.6 Setting AAA Serversset aaa_server [aaa_type {auth | acco}]
[address ] [enabled {yes | no}] [port ] [preference ] [secret ]
[timeout ] The proxy RADIUS Authentication, Authorization, and
Accounting servers, that confirm the proxy Mobile IP users, are
assigned to a domain and are programmed with a preference order for
efficient load balancing and Redundancy. aaa_type: address:
enabled: port: preference: secret: Designates the server as an
accounting (acco) or authentication (auth). IP address of the
server Defines if the server is enabled Port number this server
uses to communicate. Marks the rank of the server within the domain
Shared secret between this server and the Packet Data Serving
Node
Example: set aaa_server default aaa_type auth address
220.224.134.162 preFERENCE 101 secret pasecret set aaa_server
default aaa_type acco address 220.224.134.162 preFERENCE 104 secret
pasecret
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
16
5.7 Adding IP User PoolsThis command allows adding user IP Pool
in PDSN card. add ip pool initial_pool_address size state
Example:
add ip pool RAP initial_pool_address 97.233.64.1/20 size 4090
state public
5.7 Adding IP RoutesIP routing required for the traffic from
Internet to PCF as default gateway is PI VLAN. Routes need to be
added for PCF IP Pool in each PDSN card where gateway will be RP
VLAN. Example: add ip route 97.236.40.0/24 gateway 97.233.1.1
metRIC 1
6. WIRELESS 3G DATA SYSTEM COMPONENTS 6.1 Total Control 1000
ChassisThe Total Control 1000 chassis is the main building block of
the Wireless 3G Data system Total Control 1000 Packet Data Serving
Node (PDSN) and the Total Control1000 Home Agent (HA) card sets.
The chassis is a rack-mountable enclosure with a high-speed,
multi-layer midplane that supports up to 17 front-loaded Network
Application cards (NACs) and rearloaded Network Interface Cards
(NICs). These NACs and NICs interface with the midplane via
180-pin, high-density connectors as shown below. The chassis has an
integrated fan tray that provides cooling for the installed cards.
Two front-loaded power supply units (PSUs) and their corresponding
rear-loaded power supply interfaces (PSIs) supply power through the
midplane to the cards in the chassis. Two power supplies provide
full redundancy and load sharing. Component of TC 1K:
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
17
Power Supply Units and Interfaces The chassis receives power
from two front-loaded PSUs and their corresponding rear-loaded
PSIs. The PSU/PSI sets are rated at 130A. Each PSU/PSI set requires
either 120 AC/48VDC depending on the type of power supply that is
supplied with the chassis. With the two PSU/PSI sets installed,
automatic redundant switch over and automatic shut-off in
overvoltage and short-circuit conditions are supported. All power
connections are made at the rear of the chassis at the PSI. Each
PSI has its own cabling interface as well as its own power switch.
At the front of the chassis, the PSU has LEDs that indicate power
status for the PSU and PSI. Fan Tray At the bottom of the chassis
is an integrated fan tray containing 15 fans which provide cooling
and ventilation for the cards in the chassis. The fan tray receives
power internally from the chassis PSUs so there is no additional
external cabling associated with it. The Total Control 1000 Network
Management Card (NMC) monitors the operation of the fan tray. You
can configure the system to set alarms should any fan on the tray
fail, helping protect against the possibility of a system shutdown
due to overheating. NMC The NMC is installed in the Total Control
1000 chassis to provide a single point of management for performing
configuration, doing status queries, issuing commands, performing
tests, and downloading software to the cards within the chassis.
One NMC can manage multiple cards within the same chassis. The NMC
manages all of the devices in the chassis under the direction of a
workstation running console software such as CommWorks 5315 Common
Element Manager (CEM) for Wireless software or a standard MIB
browser. This workstation is referred to as the Management Station
(MS) and connects to the NMCs NIC locally via a LAN connection.
Management of the chassis is performed via Simple Network
Management Protocol (SNMP). The NMC Receives requests from the MS
which are communicated by the Management information Bases (MIBs)
defined for each device and then executes the request. For the
management function, the NMC uses the NAC management bus to
communicate with the other NACs in the chassis. The NAC management
buses are in the chassis 2007 Reliance Communications Ltd. CDMA
Packet Data Network PDSN 18
midplane. The capability of the NMC to forward SNMP messages to
the other cards over these buses allows you to separate the
management network from the operational network which serves the
rest of the cards in the chassis. The NMC contains a mobile Pentium
III processor running at 333 MHz. The processor module incorporates
a Dynamic Random Access Memory (DRAM) socket to allow easy upgrade
of the cards memory when necessary. The NMC processor module
contains an Intel 440BX system controller, clock generator, and
voltage generator for both the Pentium III processor and the DRAM
socket. The NMC supports interfacing to an Ethernet network via the
CommWorks 10/100 Ethernet AUX I/O NIC. PDSN Card The Total Control
1000 Packet Data Serving Node (PDSN) connects a radio network to an
IP network via a serving router. Primarily, the PDSN establishes,
maintains, and terminates link layer sessions to a mobile client.
Incremental functions include, but are not limited to, IP address
assignments for Simple IP service and performing Foreign Agent
functionality for a visiting mobile node for Mobile IP service.
Simple IP-based service mainly supports mobile node initiated
dial-in. The PDSN is the 3G System interface between an access
network and a data network. It terminates the data link layer from
the mobile and routes upper layer protocols into a data network
directly. For Mobile IP-based service, the PDSN supports the
standard Mobile IP Foreign Agent functionality with extensions to
support: Reverse tunneling Foreign agent challenge/response
authentication Network Access Identifier (NAI)-based registration
Dynamic home agent and home address assignment The PDSN card is a
single NAC that can be housed in a single Total Control 1000
chassis. A chassis can house up to 16 PDSN cards. Each PDSN card
Operates independently of the others in the chassis. For each NAC,
there is a dual 10/100 Mbps Ethernet NIC with a single RS-232
serial port. One of the Ethernet interfaces connects to the RNN/PCF
for R-P connection setup/teardown. The other Ethernet interface may
connect to a gateway and hence to appropriate networks, so the PDSN
can forward packets from Simple IP calls to appropriate network
destinations and forward packets from Mobile IP calls to
appropriate HAs. Each PDSN also has a single RS-232 interface for
local configuration and call management. A PDSN card also has the
following major components: Virtual Home Agent (VHA) (RP interface)
Remote Authentication Dial-In User Service (RADIUS) client
Point-to-Point Protocol (PPP) module Foreign Agent (FA) The chassis
supports up to 16 PDSN cards, but this number can include a mix of
PDSN cards, HA cards, and HACN cards.
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
19
FACN The CommWorks 4302 Foreign Agent Control Node (FACN)
software is an optional UNIXbased application that provides call
management for multiple PDSNs in a wireless network. It enhances
the functionality of the PDSN, providing fault tolerance,
redundancy across PDSNs and PDSN groups, PDSN load balancing and
the ability to minimize handoff conditions. HA Card The Total
Control 1000 Home Agent (HA) is responsible for accepting Mobile IP
registration requests from Mobile IP capable mobiles and the PDSN.
After successfully checking the integrity of the Mobile IP request,
the HA creates a Mobility Binding Record (MBR) and IP tunnel to
terminate tunneled IP traffic from the mobile that is forwarded by
a PDSN. The HA decapsulates and routes traffic in the reverse
direction to Internet Service Providers (ISP). It also receives IP
traffic from the ISPs, encapsulates, and tunnels it in the forward
direction to the mobile and through the appropriate PDSN. Similar
to a PDSN card, the HA card is a single Network Application Card
(NAC) installed in a single chassis. A chassis can house up to 16
HA cards. Each HA card operates independently of the others in the
chassis. For each NAC, there is a dual 10/100 Mbps Ethernet NIC
with a single RS-232 serial port. One of the Ethernet interfaces
connects to a FA for Mobile IP registration. The other Ethernet
interface provides direct connectivity to an IP network via
standard routing. Each HA card also has a single RS-232 serial
interface for local configuration and call management. AAA Server
The PDSN and HA components interoperate with several popular
authentication, authorization, and accounting (AAA) servers,
including Funk Softwares Steel-Belted Radius server. AAA (also
known as RADIUS) servers reside in a home or foreign network. The
PDSN interacts with a Foreign AAA server (FAAA) during Foreign
Agent Challenge for Mobile IP registrations. The FAAA then relays
requests to the appropriate Home AAA server. In this instance, the
FAAA serves as a Proxy AAA server. In summary, the AAA server
provides these main features: Access authentication and
authorization in a foreign network Mobile IP authentication in HA
Roaming support for mobile nodes Accounting for packet data
services CEM The CEM for Wireless software package offers service
providers with flexible and intuitive management solutions,
comprehensive and integrated management abilities, and advanced
value added features that provide industry leading element
management capabilities. CEM communicates with the Total Control
chassis via the NMC. The NMC hosts the systems SNMP agent and
provides a single point of management to the Total Control chassis,
retrieving data from and giving instructions to the other cards in
the chassis. 2007 Reliance Communications Ltd. CDMA Packet Data
Network PDSN 20
CEM includes the following features: Client / server
architecture Java-based platform independent architecture Open
solutions environment Hierarchical organization, explorer-like
logical views Management of 2G equipment from the same interface
Built-in MIB browser Supports non-CommWorks MIB-II compliant
devices SNMPv3 MIB compliant HP Open View integration (HP Open View
6.1 is supported) Logging capability Operator-restricted views Web
browser access to device inventory and status Customizable
scripting interfaces Trap interpretation Status at a glance To
complement the Command Line Interface (CLI), the graphical user
interface (GUI) of CEM also provides access for performing these
functions on cards installed in the chassis: Configuration of
network parameters Performance monitoring Viewing statistics
Performing software upgrades Bulk configuration and bulk download
Enabling/disabling added-cost features
7. SPECIFICATIONS OF TC 1KA total control 1000 PDSN chassis of
3com is used for packet data network. Software version used is PDSN
Ver3.0. Each PDSN Chassis has 16 PDSN cards and 1 NMC card. In
present scenario, Software Version used is ver 5.4.103. Each PDSN
chassis has 14 cards & 1 NMC card. Each PDSN Card consists of:
Two 100 Mbps ports, one for R-P and other for PI. The effective
throughput of the PDSN Card is 50 Mbps on the P-I interface. One
console port The NMC card is used to communicate with external Mgmt
Server for Alarm, Faults and Configuration. According to 3Com (i.e.
as per the Product Specification): The PDSN card can support 4000
PPP sessions (either active or dormant) The PDSN card can support
1300 PPP sessions @ 38.4 Kbps (all active Each PDSN card can
support 7 call events per second = 4.38 Sessions PDSN Chassis
population 2007 Reliance Communications Ltd. CDMA Packet Data
Network PDSN 21
In Reliance, we have total 112 PDSN cards i.e. total 8 chassis.
Out of which four chassis are connected in Mumbai & four in
Bangalore. A fully populated PDSN Chassis has 14 PDSN Cards and 1
NMC card. The 10/100 Ethernet ports on the PDSN Card, which
terminates to one each at R-P and P-I Interfaces. The NMC card is
connected to the Management Server (CEM). The architecture frozen
for implementing packet network is based on the following
Engineering Methodology: Reliance has two PDSN locations as Mumbai
& Bangalore. The architecture of Commworks PDSN is such that a
single chassis contains various PDSN modules & each of them is
independent PDSN network element. From the PDSN perspective Mumbai
will serve all the North & western region packet data users
whereas the Bangalore PDSN will cater to South & eastern region
subscribers. A total of 112 PDSNs spread over eight chassis are
required to support the Reliance data traffic model. A total of
four chassis at each Mumbai & Bangalore IDC location is
installed. Each PDSN Chassis will consist of 14 PDSN Cards. Each
PDSN can support a total of 1300 sessions @ 38.4 Kbps. AAA servers
and corresponding Oracle Database Server are placed at each Mumbai
& Bangalore IDC location. The Mumbai one of the AAA Server is
the Primary Server, serving Radius Authentication and Accounting.
And the other AAA will be act as secondary / load balancing and
redundant Server. Similarly in Bangalore one AAA will act as
Primary & the other Secondary. If both the Mumbai AAA is down
then authentication will be done on Bangalore AAA & vice versa.
A complete replication of both subscriber and authorization
database are implemented. The replication is configured to be
automatic over the Reliance WAN. A 100% redundancy will be
available at the Aggregation L3 Switches, both on the R-P and P-I
interface. L3 switch redundancy is achieved by installing 2
switches each at the R-P and the Pi interfaces. Physical
connectivity between the PDSN Cards and the L3 Switches is done
such a way that, the switches are not a single point of failure in
the network. Any failure on one of the switches cannot bring down
the connectivity to all the PDSN Cards. The physical connectivity
between the 56 PDSN Cards and L3 switch are split between the two
R-P and PI switches such that in the event of one of the switches
failing 50% of PDSNs are still active at that site. For more
details of RP & PI switches refer RP-PI Engineering document
The Mgmt related information from all the network elements (SNMP
traffic) is sent to both the CEMs in the network. Thus, any
unavailability of a single CEM Server will have no impact on the
Management Capability of the packet network. CEM server is the
Common Element Server, which is a SUN server.
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
22
8. APPENDIX 8.1 FACNFACN Server (Foreign agent control Node):
FACN is a Unix- based application that provides an elegant control
mechanism for managing multiple Packet Data serving Nodes. It acts
as an intermediate device between the PHE2 and the PDSN thus
controlling the PDSN loads. FACN is also doing the load balancing
for PDSN. In Reliance Network we have total two FACN. One is in
Mumbai & the other is in Bangalore. Incase of one FACN fails
all the data calls will be diverted to the other location FACN.
Incase both the FACN fails, data calls will land directly on
respective PDSN location that is from North & West location
Data call will land on Mumbai PDSN & South & East calls
will land on Bangalore PDSN. Hardware & Software details of
FACN: FACN Hardware Details SUN Fire CPU HD RAM FACN Software
details Release Version 4.0.101. FACN SUN server Other Details User
IP Address Management IP Address Port Address on PI switch
480 R 2* 900 MHz 2*72GB 4 GB
97.232.2.152 97.253.5.9 Connected on RP1 Port 1 / 46
Note: Mumbai & Bangalore Hardware & Software details are
same.
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
23
FACN Connectivity with PDSN.MUMBAI REGION PDSN1_card 1 to card
14 PDSN2_card 1 to card 14North and West PHE2s FACN_1
97.232.1.2 to 97.232.1.15 97.233.1.2 to 97.233.1.15
97.232.1.152
PDSN3_card 97.234.1.2 to 1 to card 14 97.234.1.15 PDSN4_card 1
to card 14 97.235.1.2 to 97.235.1.15
PDSN1_card 5 to card 15 PDSN2_card 1 to card 15 PDSN3_card 1 to
card 15 PDSN4_card 1 to card 15
97.236.1.6 to 97.236.1.16 97.237.1.2 to 97.237.1.16 97.238.1.2
to 97.238.1.16 97.239.1.2 to 97.239.1.16
South and East PHE2s
97.236.1.152PRIMARY SELECTION SECONDARY SELECTION TERTIARY
SELECTION
FACN_2
BANGALORE REGION
Configuration at FACN To add a group use command ag group no.
groupname. To add a PDSN in group use agp groupno. PDSN IP. To
create a backup group use agb groupno.1 groupno.2. groupno.2 is
backup for groupno.1. To add a PCF, ar PCFIP groupno. PCFIP will be
associated with groupno. Run command vsp on FACN to display the
system parameters Use command msp to modify a particular parameter
if needed Modify heartbeat = 120 Sec. by running vsp command
Configuration at PDSN To configure FACN interface in PDSN, use
add FACn_interface sa sa no. Facn_address FACNIP. To set security
parameters like (Shared Secret, SPI, Time Drift), use set
Facn_interface sa sa no. Shared_secret shared secret spi spi
time_drift time drift
Configuration at all PDSNs add facn_interface sa 1 facn_address
97.232.1.152 add facn_interface sa 2 facn_address
97.236.1.15224
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
Set facn_interface sa 1 spi 257 shared secret SECRET time_drift
255 Set facn_interface sa 2 spi 257 shared secret SECRET time_drift
255
8.2 Connectivity & Sample configuration of PDSN with PCFThe
current IP addressing schema is as per the Homing Plan of
distributing traffic to respective Mumbai & Bangalore PDSN's
FOR 3COM PDSN The PDSN call diverting is done on basis of zones
mentioned below Any Data Calls (Internet, RAP) in the WEST &
NORTH Regions will primarily land on the Mumbai FACN. & FACN
will divert these calls to PDSN based on PDSN availability .In case
of Failure of Mumbai FACN all traffic will be diverted to Bangalore
FACN Network Any Data Calls (Internet, RAP) in the EAST & SOUTH
Regions will primarily land on the BANGALORE FACNs; In case of
Failure of BANGALORE FACN all traffic will be diverted to MUMBAI
FACN Network. If Both Mumbai & Bangalore FACN fails then, North
& west Data traffic will diverted to Mumbai PDSNs & South
& East Data traffic will diverted to Bangalore PDSNs.
Region PDSN Location Circles covered West Mumbai Mumbai, MH-Goa,
Gujarat, UP (East) North Mumbai Delhi, Punjab, Rajasthan, Haryana,
Himachal Pradesh, South Bangalore Andra Pradesh, TamilNadu,
Karnataka, Kerala East Bangalore West Bengal, MP, Orissa, Bihar, UP
(West) FOR LUCENT Since the FACN is implemented in the Reliance
data Network, Both Mumbai & Bangalore FACN IP Addresses will be
configured in all PHE2 cards PCFs lying in the WEST & NORTH
zones will be configuring Primarily Mumbai FACN IP address
Secondarily Bangalore FACN IP address PARAMETERS TO CONFIGURE IN
PHE2 CARD FOR PDSN CONNECTIVITY SPI Secret Key UDP Port 100 SECRET
699
All the PCF / PHE2 cards of respective MSC locations will be
terminated on the DATA CORE NETWORK [JUNIPER]. 2007 Reliance
Communications Ltd. CDMA Packet Data Network PDSN 25
An Ethernet cable [CAT - 5 / CAT - 6] will have to be connected
to the Data router from the PHE2 card till the CORE router port.
Sample Configuration at PCF/PHE2 for South & East Region
Addition of Bangalore FACN, Mumbai FACN and All PDSN (of Mumbai
region & Bangalore) to all South & East PHE2 card 2: 1)
Repeat part 10.1 with (SM=5). 2) Selection Group naming convention
for SM4 SM5 MUMFACN4 MUMFACN5 BANFACN 4 BANFACN5 BANPDSN4 BANPDSN5
Addition of Bangalore FACN, Mumbai FACN and All PDSN (of Mumbai
region & Bangalore) to all South & East PHE2 card 1: 1.
Verify or update, 91.1 PCFOF for which type of selection Algorithm
to be used: 24. PDSN SELECT ALG CUSTOM0 PDSN SELECT ALG - The PDSN
SELECT ALG field will allow the customer to define the order that
the PDSNs will be placed in the PDSN list used by call processing.
CUSTOM0 For selection on IP list in ascending order.
1.
Insert in form 91.3. (Definition of Bangalore FACN in PHE2) Make
the following entries and insert the form.
SYS EMER CRITICAL MAJOR MINOR BLDG/PWR BLDG INH CKT LIM SYS NORM
OVERLOAD SYS INH AM AM PERPH OS LINKS SM CM MISC BANGLORE1 SCREEN 1
OF 1 RECENT CHANGE 91.3 PDCNF PDSN CONFIGURATION *1. IP ADDRESS 097
236 001 152 6. SHARED SECRET A SECRET #9. MOB HOME AUTH EXT Y #10.
REG UPD AUTH EXT Y #11. SPI AUTHENT PROTECT Y #12. SPI 100 #13.
VEND ORG SPEC EXT N #14. ESN ACCT ENABLE Y #15. IS 835 VERSION 0 N
#16. GRE CHKSUM ENABLE N 17. ORDER NUMBER 0
2007 Reliance Communications Ltd. CDMA Packet Data Network
PDSN
26
Enter Review, Change-insert, Validate, or Print:1. 2.
Repeat step 2 to define Mumbai FACN in PHE2 with Mumbai FACN IP.
Define Mumbai PDSN Group in 91.3 Make the following entries and
insert the form.
SYS EMER CRITICAL MAJOR MINOR BLDG/PWR BLDG INH CKT LIM SYS NORM
OVERLOAD SYS INH AM AM PERPH OS LINKS SM CM MISC BANGLORE1 SCREEN 1
OF 1 RECENT CHANGE 91.3 PDCNF PDSN CONFIGURATION *1. IP ADDRESS ___
___ __ __ 6. SHARED SECRET A SECRET #9. MOB HOME AUTH EXT Y #10.
REG UPD AUTH EXT Y #11. SPI AUTHENT PROTECT Y #12. SPI 100 #13.
VEND ORG SPEC EXT N #14. ESN ACCT ENABLE Y #15. IS 835 VERSION 0 N
#16. GRE CHKSUM ENABLE N 17. ORDER NUMBER 0