Escolar Documentos
Profissional Documentos
Cultura Documentos
Table of Contents
1. INTRODUCTION...........................................................................4
1.1 Purpose ...................................................................................4 1.3 Change History...........................................................................4
2.
..........................................................5
2.1 Mobile Node / Station..................................................................5 2.2 Radio Access Network..................................................................6 2.3 PDSN.......................................................................................7
7. SPECIFICATIONS
OF
TC 1K..............................................................21
8. APPENDIX..............................................................................23
8.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
1. INTRODUCTION
1.1 Purpose
The purpose of the document is to provide details of architecture & configuration of PDSN installed at IDC-Hub (Mumbai) & IDC-1 (Bangalore).
HLR A1
RADIUS
RADIUS R-P interfacer A10/A11
IP network
IP Network
pi
Home IP network
Source RN
Serving PDSN
P-P interface
RADIUS
Desktop
pi
Broker IP
Laptop computer
Target PDSN
Cell phone
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.
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 PDSN
The 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 OVERVIEW
When 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.
AAA - Authentication, Authorization, and Accounting PCF - Packet Control Function PDSN - Packet Data Service Node
VLR
HLR
Visited AAA
Home AAA
Home Network
RAN
PDSN
Internet
Visited Access Provider Network
Simple 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
MS
1-3
TCH setup
PCF
PDSN
A10 setup
8 6 CHAP response 9
Access 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
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.
PCF
PDSN
Visited AAA
End host
A10 setup
8 6 CHAP response 9
Access 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
15
Data flows
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.
11
Device
Connected to
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
12
PI
220.224.135.96/27
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 Bangalore
13
14
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
15
set vha sa <1 to 512> spi <0 to 4294967295> shared_secret <up to 16 ASCII characters> time_drift <0 to 255> 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
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
16
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.
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 1K
A 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.
22
Note: Mumbai & Bangalore Hardware & Software details are same.
23
97.232.1.152
97.236.1.152
PRIMARY 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.152
24
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
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
26
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 <-PDSN IPs of Mumbai Region
Enter Review, Change-insert, Validate, or Print: 1. Insert in form 91.2. Make following entries and insert the form (For Bangalore FACN). 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.2 PCFPD PCF PDSN IP ASSIGNMENT *1. SM 004 *2. PSU 0 *3. SHELF 1 *4. CHANNEL GROUP 15 *5. IP ADDRESS 097 236 001 152 10. SELECTION GROUP BANFACN4
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.2 PCFPD PCF PDSN IP ASSIGNMENT *1. SM 004 *2. PSU 0 *3. SHELF 1 *4. CHANNEL GROUP 15 *5. IP ADDRESS 097 232 001 152 10. SELECTION GROUP MUMFACN4
Make following entries and insert the form for 4 PDSN (which were deleted in Phase 1) 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.2 PCFPD PCF PDSN IP ASSIGNMENT *1. SM 004 *2. PSU 0 *3. SHELF 1 *4. CHANNEL GROUP 15 *5. IP ADDRESS <- PDSN IP address of 4 PDSN which were deleted in Phase I 10. SELECTION GROUP BANPDSN4
1. Update form 91.2. Make following entries and update the form for Bangalore PDSN Group (except 4 PDSN inserted in previous step) by making selection group as BANPDSN4 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.2 PCFPD PCF PDSN IP ASSIGNMENT *1. SM 004 *2. PSU 0 *3. SHELF 1 *4. CHANNEL GROUP 15 *5. IP ADDRESS ___ ___ ___ ___ <- PDSN IP of Bangalore PDSN 10. SELECTION GROUP BANPDSN4
28
1. Update RCV 91.4 PCFSG, to associate selection group defined in RCV91.2 to Order number. SCREEN 1 OF 1 RECENT CHANGE 91.4 PCFSG PCF SELECTION GROUP PRIORITY ASSIGNMENT
15
5. SELECTION GROUP LIST SELECTION GROUP ORDER NUM SELECTION GROUP ORDER NUM 1) MUMFACN4 2 6) ________ __ 2) BANFACN4 1 7) ________ __ 3) BANPDSN4 3 8) ________ __ 4) ________ __ 9) ________ __ 5) ________ __ 10) ________ __ Enter Review, Validate, or Print:
1.
Check 90.6 IPRTE form for routing from PHE2 to FACN. Gateway for both Mumbai & Bangalore, FACN & PDSN IPs should be there.
SCREEN 1 OF 1
RECENT CHANGE 90.6 IPRTE IP ROUTING TO INTERFACE *1. DEST IP ADDR ___ ___ ___ ___ *6. INTERFACE NAME ___________________ 7. NET OR HOST ____ 8. IP SUBNET MASK ___ ___ ___ ___ #13. GATEWAY IP ADDR ___ ___ ___ ___ 18. ROUTE METRIC ___
29
Mumbai Chassis 1
Chassis 2 PDSN ch2 card1 PDSN ch2 card2 PDSN ch2 card3 PDSN ch2 card4 PDSN ch2 card5 PDSN ch2 card6 PDSN ch2 card7 PDSN ch2 card8 PDSN ch2 card9 PDSN ch2 card10 PDSN ch2 card11 PDSN ch2 card12 PDSN ch2 card13 PDSN ch2 card14
RP side IP 97.233.1.2/27 97.233.1.3/27 97.233.1.4/27 97.233.1.5/27 97.233.1.6/27 97.233.1.7/27 97.233.1.8/27 97.233.1.9/27 97.233.1.10/2 7 97.233.1.11/2 7 97.233.1.12/2 7 97.233.1.13/2 7 97.233.1.14/2 7 97.233.1.15/2 7
PI Side IP 220.224.134.34/27 220.224.134.35/27 220.224.134.36/27 220.224.134.37/27 220.224.134.38/27 220.224.134.39/27 220.224.134.40/27 220.224.134.41/27 220.224.134.42/27 220.224.134.43/27 220.224.134.44/27 220.224.134.45/27 220.224.134.46/27 220.224.134.47/27
Mumbai Chassis 2
Chassis 3 PDSN ch3 card1 PDSN ch3 card2 PDSN ch3 card3
30
PDSN ch3 card4 PDSN ch3 card5 PDSN ch3 card6 PDSN ch3 card7 PDSN ch3 card8 PDSN ch3 card9 PDSN ch3 card10 PDSN ch3 card11 PDSN ch3 card12 PDSN ch3 card13 PDSN ch3 card14 Chassis 4 PDSN ch4 card1 PDSN ch4 card2 PDSN ch4 card3 PDSN ch4 card4 PDSN ch4 card5 PDSN ch4 card6 PDSN ch4 card7 PDSN ch4 card8 PDSN ch4 card9 PDSN ch4 card10 PDSN ch4 card11 PDSN ch4 card12 PDSN ch4 card13 PDSN ch4 card14
97.234.1.5/27 97.234.1.6/27 97.234.1.7/27 97.234.1.8/27 97.234.1.9/27 97.234.1.10/2 7 97.234.1.11/2 7 97.234.1.12/2 7 97.234.1.13/2 7 97.234.1.14/2 7 97.234.1.15/2 7 RP side IP 97.235.1.2/27 97.235.1.3/27 97.235.1.4/27 97.235.1.5/27 97.235.1.6/27 97.235.1.7/27 97.235.1.8/27 97.235.1.9/27 97.235.1.10/2 7 97.235.1.11/2 7 97.235.1.12/2 7 97.235.1.13/2 7 97.235.1.14/2 7 97.235.1.15/2 7
220.224.134.69/27 220.224.134.70/27 220.224.134.71/27 220.224.134.72/27 220.224.134.73/27 220.224.134.74/27 220.224.134.75/27 220.224.134.76/27 220.224.134.77/27 220.224.134.78/27 220.224.134.79/27 PI Side IP 220.224.134.98/27 220.224.134.99/27 220.224.134.100/27 220.224.134.101/27 220.224.134.102/27 220.224.134.103/27 220.224.134.104/27 220.224.134.105/27 220.224.134.106/27 220.224.134.107/27 220.224.134.108/27 220.224.134.109/27 220.224.134.110/27 220.224.134.111/27
Mumbai Chassis 4
Mumbai Chassis 3
Chassis 1 PDSN ch1 card1 PDSN ch1 card2 PDSN ch1 card3 PDSN ch1 card4 PDSN ch1 card5 PDSN ch1 card6 PDSN ch1 card7 PDSN ch1 card8 PDSN ch1 card9 PDSN ch1 card10 PDSN ch1 card11 PDSN ch1 card12 PDSN ch1 card13 PDSN ch1 card14 PDSN ch1 card15
RP Side 97.236.1.2/27 97.236.1.3/27 97.236.1.4/27 97.236.1.5/27 97.236.1.6/27 97.236.1.7/27 97.236.1.8/27 97.236.1.9/27 97.236.1.10/27 97.236.1.11/27 97.236.1.12/27 97.236.1.13/27 97.236.1.14/27 97.236.1.15/27 97.236.1.16/27
PI Side 220.224.135.2/27 220.224.135.3/27 220.224.135.4/27 220.224.135.5/27 220.224.135.6/27 220.224.135.7/27 220.224.135.8/27 220.224.135.9/27 220.224.135.10/27 220.224.135.11/27 220.224.135.12/27 220.224.135.13/27 220.224.135.14/27 220.224.135.15/27 220.224.135.16/27 31
Bangalore Chassis 1
Chassis 2 PDSN ch2 card1 PDSN ch2 card2 PDSN ch2 card3 PDSN ch2 card4 PDSN ch2 card5 PDSN ch2 card6 PDSN ch2 card7 PDSN ch2 card8 PDSN ch2 card9 PDSN ch2 card10 PDSN ch2 card11 PDSN ch2 card12 PDSN ch2 card13 PDSN ch2 card14 PDSN ch2 card15 Chassis 3 PDSN ch3 card1 PDSN ch3 card2 PDSN ch3 card3 PDSN ch3 card4 PDSN ch3 card5 PDSN ch3 card6 PDSN ch3 card7 PDSN ch3 card8 PDSN ch3 card9 PDSN ch3 card10 PDSN ch3 card11 PDSN ch3 card12 PDSN ch3 card13 PDSN ch3 card14 PDSN ch3 card15 Chassis 4 PDSN ch4 card1 PDSN ch4 card2 PDSN ch4 card3 PDSN ch4 card4 PDSN ch4 card5 PDSN ch4 card6 PDSN ch4 card7 PDSN ch4 card8 PDSN ch4 card9 PDSN ch4 card10 PDSN ch4 card11 PDSN ch4 card12 PDSN ch4 card13 PDSN ch4 card14 PDSN ch4 card15
RP side IP 97.237.1.2/27 97.237.1.3/27 97.237.1.4/27 97.237.1.5/27 97.237.1.6/27 97.237.1.7/27 97.237.1.8/27 97.237.1.9/27 97.237.1.10/27 97.237.1.11/27 97.237.1.12/27 97.237.1.13/27 97.237.1.14/27 97.237.1.15/27 97.237.1.16/27 RP side IP 97.238.1.2/27 97.238.1.3/27 97.238.1.4/27 97.238.1.5/27 97.238.1.6/27 97.238.1.7/27 97.238.1.8/27 97.238.1.9/27 97.238.1.10/27 97.238.1.11/27 97.238.1.12/27 97.238.1.13/27 97.238.1.14/27 97.238.1.15/27 97.238.1.16/27 RP side IP 97.239.1.2 97.239.1.3/27 97.239.1.4/27 97.239.1.5/27 97.239.1.6/27 97.239.1.7/27 97.239.1.8/27 97.239.1.9/27 97.239.1.10/27 97.239.1.11/27 97.239.1.12/27 97.239.1.13/27 97.239.1.14/27 97.239.1.15/27 97.239.1.16/27
PI Side IP 220.224.135.34/27 220.224.135.35/27 220.224.135.36/27 220.224.135.37/27 220.224.135.38/27 220.224.135.39/27 220.224.135.40/27 220.224.135.41/27 220.224.135.42/27 220.224.135.43/27 220.224.135.44/27 220.224.135.45/27 220.224.135.46/27 220.224.135.47/27 220.224.135.48/27 PI Side IP 220.224.135.66/27 220.224.135.67/27 220.224.135.68/27 220.224.135.69/27 220.224.135.70/27 220.224.135.71/27 220.224.135.72/27 220.224.135.73/27 220.224.135.74/27 220.224.135.75/27 220.224.135.76/27 220.224.135.77/27 220.224.135.78/27 220.224.135.79/27 220.224.135.80/27 PI Side IP 220.224.135.98/27 220.224.135.99/27 220.224.135.100/27 220.224.135.101/27 220.224.135.102/27 220.224.135.103/27 220.224.135.104/27 220.224.135.105/27 220.224.135.106/27 220.224.135.107/27 220.224.135.108/27 220.224.135.109/27 220.224.135.110/27 220.224.135.111/27 220.224.135.112/27
Bangalore Chassis 4
Bangalore Chassis 3
Bangalore Chassis 2
32
PDSN ch2 card14 Chassis 3 PDSN ch3 card1 PDSN ch3 card2 PDSN ch3 card3 PDSN ch3 card4 Mumbai Chassis 3 PDSN ch3 card5 PDSN ch3 card6 PDSN ch3 card7 PDSN ch3 card8 PDSN ch3 card9 PDSN ch3 card10 PDSN ch3 card11 PDSN ch3 card12 PDSN ch3 card13 PDSN ch3 card14 Chassis 4 PDSN ch4 card1 PDSN ch4 card2 PDSN ch4 card3 PDSN ch4 card4 Mumbai Chassis 4 PDSN ch4 card5 PDSN ch4 card6 PDSN ch4 card7 PDSN ch4 card8 PDSN ch4 card9 PDSN ch4 card10 PDSN ch4 card11 PDSN ch4 card12 PDSN ch4 card13 PDSN ch4 card14
97.233.224.0/20 RAP Pool 97.234.16.0/20 97.234.32.0/20 97.234.48.0/20 97.234.64.0/20 97.234.80.0/20 97.234.96.0/20 97.234.112.0/20 97.234.128.0/20 97.234.144.0/20 97.234.160.0/20 97.234.176.0/20 97.234.192.0/20 97.234.208.0/20 97.234.224.0/20 RAP Pool 97.235.16.0/20 97.235.32.0/20 97.235.48.0/20 97.235.64.0/20 97.235.80.0/20 97.235.96.0/20 97.235.112.0/20 97.235.128.0/20 97.235.144.0/20 97.235.160.0/20 97.235.176.0/20 97.235.192.0/20 97.235.208.0/20 97.235.224.0/20
192.168.157.0/24 SDLA Pool 192.168.160.0/24 192.168.161.0/24 192.168.162.0/24 192.168.163.0/24 192.168.164.0/24 192.168.165.0/24 192.168.166.0/24 192.168.167.0/24 192.168.168.0/24 192.168.169.0/24 192.168.170.0/24 192.168.171.0/24 192.168.172.0/24 192.168.173.0/24 SDLA Pool 192.168.176.0/24 192.168.177.0/24 192.168.178.0/24 192.168.179.0/24 192.168.180.0/24 192.168.181.0/24 192.168.182.0/24 192.168.183.0/24 192.168.184.0/24 192.168.185.0/24 192.168.186.0/24 192.168.187.0/24 192.168.188.0/24 192.168.189.0/24
10.102.116.0/22 Bberry Pool 10.102.128.0/22 10.102.132.0/22 10.102.136.0/22 10.102.140.0/22 10.102.144.0/22 10.102.148.0/22 10.102.152.0/22 10.102.156.0/22 10.102.160.0/22 10.102.164.0/22 10.102.168.0/22 10.102.172.0/22 10.102.176.0/22 10.102.180.0/22 Bberry Pool 10.102.192.0/22 10.102.196.0/22 10.102.200.0/22 10.102.204.0/22 10.102.208.0/22 10.102.212.0/22 10.102.216.0/22 10.102.220.0/22 10.102.224.0/22 10.102.228.0/22 10.102.232.0/22 10.102.236.0/22 10.102.240.0/22 10.102.244.0/22
220.224.109.128 Rconnect Pool1 220.224.112.0 220.224.112.128 220.224.113.0 220.224.113.128 220.224.114.0 220.224.114.128 220.224.115.0 220.224.115.128 220.224.116.0 220.224.116.128 220.224.117.0 220.224.117.128 220.224.118.0 220.224.118.128 Rconnect Pool1 220.224.119.0 220.224.119.128 220.224.120.0 220.224.120.128 220.224.121.0 220.224.121.128 220.224.122.0 220.224.122.128 220.224.123.0 220.224.123.128 220.224.124.0 220.224.124.128 220.224.125.0 220.224.125.128
220.224.27.0/24 Rconnect Pool3 220.224.28.0/24 220.224.29.0/24 220.224.30.0/24 220.224.31.0/24 220.224.32.0/24 220.224.33.0/24 220.224.34.0/24 220.224.35.0/24 220.224.36.0/24 220.224.37.0/24 220.224.38.0/24 220.224.39.0/24 220.224.40.0/24 220.224.41.0/24 Rconnect Pool3 220.224.42.0/24 220.224.43.0/24 220.224.44.0/24 220.224.45.0/24 220.224.46.0/24 220.224.47.0/24 220.224.48.0/24 220.224.49.0/24 220.224.50.0/24 220.224.51.0/24 220.224.52.0/24 220.224.53.0/24 220.224.54.0/24 220.224.55.0/24
220.224.77.128/25 Rconnect Pool2 220.224.78.0/25 220.224.78.128/25 220.224.79.0/25 220.224.79.128/25 220.224.80.0/25 220.224.80.128/25 220.224.81.0/25 220.224.81.128/25 220.224.82.0/25 220.224.82.128/25 220.224.83.0/25 220.224.83.128/25 220.224.84.0/25 220.224.84.128/25 Rconnect Pool2 220.224.85.0/25 220.224.85.128/25 220.224.86.0/25 220.224.86.128/25 220.224.87.0/25 220.224.87.128/25 220.224.88.0/25 220.224.88.128/25 220.224.89.0/25 220.224.89.128/25 220.224.90.0/25 220.224.90.128/25 220.224.91.0/25 220.224.91.128/25
220.224.63.108/30 R-Performance IP 220.224.63.112/30 220.224.63.116/30 220.224.63.120/30 220.224.63.124/30 220.224.63.128/30 220.224.63.132/30 220.224.63.136/30 220.224.63.140/30 220.224.63.144/30 220.224.63.148/30 220.224.63.152/30 220.224.63.156/30 220.224.63.160/30 220.224.63.164/30 R-Performance IP 220.224.63.168/30 220.224.63.172/30 220.224.63.176/30 220.224.63.180/30 220.224.63.184/30 220.224.63.188/30 220.224.63.192/30 220.224.63.196/30 220.224.63.200/30 220.224.63.204/30 220.224.63.208/30 220.224.63.212/30 220.224.63.216/30 220.224.63.220/30
34
Bangalore:
Chassis 1 PDSN ch1 card1 PDSN ch1 card2 PDSN ch1 card3 PDSN ch1 card4 PDSN ch1 card5 PDSN ch1 card6 PDSN ch1 card7 PDSN ch1 card8 PDSN ch1 card9 PDSN ch1 card10 PDSN ch1 card11 PDSN ch1 card12 PDSN ch1 card13 PDSN ch1 card14 PDSN ch1 card15 Chassis 2 PDSN ch2 card1 PDSN ch2 card2 PDSN ch2 card3 PDSN ch2 card4 PDSN ch2 card5 PDSN ch2 card6 PDSN ch2 card7 PDSN ch2 card8 PDSN ch2 card9 PDSN ch2 card10 PDSN ch2 card11 PDSN ch2 card12 PDSN ch2 card13 PDSN ch2 card14 PDSN ch2 card15 RAP Pool 97.236.16.0/20 97.236.32.0/20 97.236.48.0/20 97.236.64.0/20 97.236.80.0/20 97.236.96.0/20 97.236.112.0/20 97.236.128.0/20 97.236.144.0/20 97.236.160.0/20 97.236.176.0/20 97.236.192.0/20 97.236.208.0/20 97.236.224.0/20 97.236.240.0/20 RAP Pool 97.237.16.0/20 97.237.32.0/20 97.237.48.0/20 97.237.64.0/20 97.237.80.0/20 97.237.96.0/20 97.237.112.0/20 97.237.128.0/20 97.237.144.0/20 97.237.160.0/20 97.237.176.0/20 97.237.192.0/20 97.237.208.0/20 97.237.224.0/20 97.237.240.0/20 Bberry Pool 10.103.0.0/22 10.103.4.0/22 10.103.8.0/22 10.103.12.0/22 10.103.16.0/22 10.103.20.0/22 10.103.24.0/22 10.103.28.0/22 10.103.32.0/22 10.103.36.0/22 10.103.40.0/22 10.103.44.0/22 10.103.48.0/22 10.103.52.0/22 10.103.56.0/22 Bberry Pool 10.103.64.0/22 10.103.68.0/22 10.103.72.0/22 10.103.76.0/22 10.103.80.0/22 10.103.84.0/22 10.103.88.0/22 10.103.92.0/22 10.103.96.0/22 10.103.100.0/22 10.103.104.0/22 10.103.108.0/22 10.103.112.0/22 10.103.116.0/22 10.103.120.0/22 Rconnect Pool1 220.226.0.0/24 220.226.1.0/24 220.226.2.0/24 220.226.3.0 / 24 220.226.4.0/24 220.226.5.0/24 220.226.6.0/24 220.226.7.0/24 220.228.0.0/24 220.226.9.0/24 220.226.10.0/24 220.226.11.0/24 220.226.12.0/24 220.226.13.0/24 220.226.56.0/24 Rconnect Pool1 220.226.14.0/24 220.226.15.0/24 220.226.16.0/24 220.226.17.0/24 220.226.18.0/24 220.226.19.0/24 220.226.20.0/24 220.226.21.0/24 220.226.22.0/24 220.226.23.0/24 220.226.24.0/24 220.226.25.0/24 220.226.26.0/24 220.226.27.0/24 220.226.57.0/24 Rconnect Pool2 R-Performance IP 220.226.63.0/30 220.226.63.4/30 220.226.63.8/30 220.226.63.12/30 220.226.63.16/30 220.226.63.20/30 220.226.63.24/30 220.226.63.28/30 220.226.63.32/30 220.226.63.36/30 220.226.63.40/30 220.226.63.44/30 220.226.63.48/30 220.226.63.52/30 220.226.63.224/30 R-Performance IP 220.226.63.56/30 220.226.63.60/30 220.226.63.64/30 220.226.63.68/30 220.226.63.72/30 220.226.63.76/30 220.226.63.80/30 220.226.63.84/30 220.226.63.88/30 220.226.63.92/30 220.226.63.96/30 220.226.63.100/30 220.226.63.104/30 220.226.63.108/30 220.226.63.228/30
Bangalore Chassis 1
220.226.66.0/25 220.226.66.128/25 220.226.67.0/25 220.226.67.128/25 220.226.68.0/25 220.226.68.128/25 220.226.69.0/25 220.226.69.128/25 220.226.70.0/25 220.226.70.128/25 220.226.64.0/25 Rconnect Pool2 220.226.71.0/25 220.226.71.128/25 220.226.72.0/25 220.226.72.128/25 220.226.73.0/25 220.226.73.128/25 220.226.74.0/25 220.226.74.128/25 220.226.75.0/25 220.226.75.128/25 220.226.76.0/25 220.226.76.128/25 220.226.77.0/25 220.226.77.128/25 220.226.64.128/25
Bangalore Chassis 2
35
Chassis 3 PDSN ch3 card1 PDSN ch3 card2 PDSN ch3 card3 PDSN ch3 card4 PDSN ch3 card5 PDSN ch3 card6 PDSN ch3 card7 PDSN ch3 card8 PDSN ch3 card9 PDSN ch3 card10 PDSN ch3 card11 PDSN ch3 card12 PDSN ch3 card13 PDSN ch3 card14 PDSN ch3 card15 Chassis 4 PDSN ch4 card1 PDSN ch4 card2 PDSN ch4 card3 PDSN ch4 card4 PDSN ch4 card5 PDSN ch4 card6 PDSN ch4 card7 PDSN ch4 card8 PDSN ch4 card9 PDSN ch4 card10 PDSN ch4 card11 PDSN ch4 card12 PDSN ch4 card13 PDSN ch4 card14 PDSN ch4 card15
RAP Pool 97.238.16.0/20 97.238.32.0/20 97.238.48.0/20 97.238.64.0/20 97.238.80.0/20 97.238.96.0/20 97.238.112.0/20 97.238.128.0/20 97.238.144.0/20 97.238.160.0/20 97.238.176.0/20 97.238.192.0/20 97.238.208.0/20 97.238.224.0/20 97.238.240.0/20 RAP Pool 97.239.16.0/20 97.239.32.0/20 97.239.48.0/20 97.239.64.0/20 97.239.80.0/20 97.239.96.0/20 97.239.112.0/20 97.239.128.0/20 97.239.144.0/20 97.239.160.0/20 97.239.176.0/20 97.239.192.0/20 97.239.208.0/20 97.239.224.0/20 97.239.240.0/20
Bberry Pool 10.103.128.0/22 10.103.132.0/22 10.103.136.0/22 10.103.140.0/22 10.103.144.0/22 10.103.148.0/22 10.103.152.0/22 10.103.156.0/22 10.103.160.0/22 10.103.164.0/22 10.103.168.0/22 10.103.172.0/22 10.103.176.0/22 10.103.180.0/22 10.103.184.0/22 Bberry Pool 10.103.192.0/22 10.103.196.0/22 10.103.200.0/22 10.103.204.0/22 10.103.208.0/22 10.103.212.0/22 10.103.216.0/22 10.103.220.0/22 10.103.224.0/22 10.103.228.0/22 10.103.232.0/22 10.103.236.0/22 10.103.240.0/22 10.103.244.0/22 10.103.248.0/22
Rconnect Pool1 220.226.28.0/24 220.226.29.0/24 220.226.30.0/24 220.226.31.0/24 220.226.32.0/24 220.226.33.0/24 220.226.34.0/24 220.226.35.0/24 220.226.36.0/24 220.226.37.0/24 220.226.38.0/24 220.226.39.0/24 220.226.40.0/24 220.226.41.0/24 220.226.58.0/24 Rconnect Pool1 220.226.42.0/24 220.226.43.0/24 220.226.44.0/24 220.226.45.0/24 220.226.46.0/24 220.226.47.0/24 220.226.48.0/24 220.226.49.0/24 220.226.50.0/24 220.226.51.0/24 220.226.52.0/24 220.226.53.0/24 220.226.54.0/24 220.226.55.0/24 220.226.59.0/24
Rconnect Pool2 220.226.78.0/25 220.226.78.128/25 220.226.79.0/25 220.226.79.128/25 220.226.80.0/25 220.226.80.128/25 220.226.81.0/25 220.226.81.128/25 220.226.82.0/25 220.226.82.128/25 220.226.83.0/25 220.226.83.128/25 220.226.84.0/25 220.226.84.128/25 220.226.65.0/25 Rconnect Pool2 220.226.85.0/25 220.226.85.128/25 220.226.86.0/25 220.226.86.128/25 220.226.87.0/25 220.226.87.128/25 220.226.88.0/25 220.226.88.128/25 220.226.89.0/25 220.226.89.128/25 220.226.90.0/25 220.226.90.128/25 220.226.91.0/25 220.226.91.128/25 220.226.65.128/25
R-Performance IP 220.226.63.112/30 220.226.63.116/30 220.226.63.120/30 220.226.63.124/30 220.226.63.128/30 220.226.63.132/30 220.226.63.136/30 220.226.63.140/30 220.226.63.144/30 220.226.63.148/30 220.226.63.152/30 220.226.63.156/30 220.226.63.160/30 220.226.63.164/30 220.226.63.232/30 R-Performance IP 220.226.63.168/30 220.226.63.172/30 220.226.63.176/30 220.226.63.180/30 220.226.63.184/30 220.226.63.188/30 220.226.63.192/30 220.226.63.196/30 220.226.63.200/30 220.226.63.204/30 220.226.63.208/30 220.226.63.212/30 220.226.63.216/30 220.226.63.220/30 220.226.63.236/30
Bangalore Chassis 4
Bangalore Chassis 3
36
37
8.5 Mobile IP
With Mobile IP, the mobile station can roam beyond the coverage area of a given PDSN and still maintain the same IP address and application-level connections.
AAA - Authentication, Authorization, and Accounting PCF - Packet Control Function PDSN - Packet Data Service Node HA Home Agent
VLR HLR
Visited AAA
Home AAA
Home IP Network
Internet
Tunnel PDSN
Foreign Agent Home Agent
Mobile Client
Server Server
Visited Network
Home Network
The communication process occurs in the following order: The mobile station registers with its Home Agent (HA) through an FA. The HA accepts the registration, assigns an IP address to the mobile station, and creates a tunnel to the FA. This results in a PPP link between the mobile station and the FA (or PDSN), and an IP-in-IP or Generic Routing Encapsulation (GRE) tunnel between the FA and the HA. As part of the registration process, the HA creates a binding table entry to associate the mobile stations home address with its Care-of address. Note: While away from home, the mobile station is associated with a care-of address. This address identifies the mobile stations current, topological point of attachment to the Internet, and is used to route packets to the mobile station. In IS-835-B networks, the foreign agents address is always used as the Care-of address. The HA advertises that the network is reachable to the mobile station, and tunnels datagram to the mobile station at its current location. The mobile station sends packets with its home address as the source IP address. Packets destined for the mobile station go through the HA; the HA tunnels them the PDSN to the mobile station using the care-of address. When the PPP link is handed off to a new PDSN, the link is re-negotiated and the registration is renewed. The HA updates its binding table with the new care-of address.
2007 Reliance Communications CDMA Packet Data Network PDSN 38
through Mobile IP
Mobile IP supports the following AAA services: Skipping authentication during PPP upon receiving NACK from the MS Acting as a foreign agent and supporting FA-HA and FA-MN authentications Verifying the FA challenge response in a Mobile IP registration The Home Agent supports the following AAA services: Completing the Mobile IP registration using authentication and authorization Assigns a dynamic IP address to the MS, from one of these places: o Its own Local pool AAA server or DHCP server on the home network Protocol Stack for Data Transfer in a Mobile IP Packet Data Session
39
Home Agent (HA): Authenticate Mobile IP registrations from the mobile client Redirect packets to the Foreign Agent, and optionally receive and route reverse tunneled packets from the Foreign Agent Optionally, establish, maintain, and terminate secure communications to the PDSN (as Mobile IP Foreign Agent) using IKE procedures or the Mobile IP HA-FA authentication extension. These security associations may be configured statically. The HA may also optionally establish secure communications dynamically using certificates, or via the HA- FA authentication key or pre-shared IKE key information provided by the Home AAA via the Foreign AAA. Receive provisioning information from the AAA Function for users Optionally assigns dynamic IP address for Mobiles HA maintains A mobility binding table for all registered mobiles with registration lifetime Pointer to current serving FA
AAA
In rn t te e
L3 Sw itches
L3 Sw itches
PD s SN LNS N i M m a ID av u b i C
Priv te a N tw rk e o
Rad Ba io se Statio n
Re n s lia ce D ta a N tw e ork
AAA
Ban alore ID g C (for sim licity n t a elem ts as p , o ll en inM m ai aresh nin Blr) u b ow
Inern t t e
PD s SN
Firew ll a
Priv e 40 at N tw rk e o
CD FW / MA T Handset
Re n s lia ce CD A N tw M e ork
GRE tunnel for each PPP session transports custom traffic over ers Reliances Private Secure Netw to W ork ireless Access Gatew ay.
LNS further authenticates user, term inates PPP session, assigns IP addresses and perform stateful firew s alling and rate lim iting.
Custom traffic is ers transported securely over the Reliances netw upto LNS ork
PDSN processes the custom requests, er authenticates subscriber, does protocol conversions betw CDMA and terrestrial een netw andencapsulates PPP session ork into L2TP tunnel for further transport
Firew protects LNS and all W ireless Access gatew ays fromun desirable users / traffic fromother custom ers.
Custom trusted netw ers ork link. Leased Line to extend to custom prem er ises, or direct linkage in Host Com puters in Reliances Data Center
Whenever the customer accesses the Host Computer from a Remote Terminal connected to the CDMA Handset, a request from the CDMA Handset is sent through the RAN comprising the BTS, MSC- PHE2 card to the PDSN via the GRE tunnel for each PPP session. The PDSN on receiving the request sends it to AAA server for authorization. The AAA server on finding that the request is for a Private Network, instructs the PDSN to set up a L2TP tunnel (that encapsulates the PPP tunnel) to the LNS through a firewall as shown in the diagram. The LNS decapsulates the PPP tunnel from the L2TP Tunnel and assigns IP address for the corresponding session. It then terminates the PPP session with the Private Network after the transaction is complete. For more information on LNS refer LNS Engineering document.
SO_26th_April_2007_PDSN_FA_Card_Configuration_for_Verizon_HA.doc
HA card addition in PDSN cards. Required for Mobile IP & International Data Roaming User
41
pool
addition in PDSN cards SO_14th_April_2007_PDSN_Setting_Change_AAA2_Bangalore.doc AAA setting change in PDSN cards FA configuration in PDSN cards
SO_16th_June_2007_PDSN_FA_Card_Configuration_for_Verizon_HA_Part -2.doc
42