sjzl20086265-zxpdss p200 (v3 08 11) product description

ZXPDSS P200cdma2000 Packet Data Serving Node

Product Description

Version 3.08.11

ZTE CORPORATIONZTE Plaza, Keji Road South,Hi-Tech Industrial Park,Nanshan District, Shenzhen,P. R. China518057Tel: (86) 755 26771900Fax: (86) 755 26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATION

Copyright © 2006 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution ofthis document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATIONor of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are dis-claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on theinformation contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subjectmatter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,the user of this document shall not acquire any license to the subject matter herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 12/10/2008 First Edition

Serial Number: sjzl20086265

Contents

Preface............................................................... i

Introduction to ZXPDSS ....................................1ZXPDSS System Architecture ........................................... 1

Location of ZXPDSS in CDMA Network ............................... 3

Usual Networking Modes.................................................. 5

Typical Networking Modes............................................ 5

Networking Mode Compliant with HRPD Specifica-

tions ................................................................. 6

Networking Mode Compliant with CAVE-Based Bimodal

Authentication Specifications................................ 8

Networking Scheme for Packet Prepaid Service............... 9

Performance Indexes of PDSN .........................................10

Hardware Description......................................13Hardware Configuration of ZXPDSS..................................13

Hardware Configuration of PDSN .....................................14

Hardware Configuration of OMC.......................................18

Hardware Configuration of LIS.........................................19

Hardware Configuration of Alarm Box ...............................20

Hardware Configuration of Other Devices..........................21

Software Description.......................................23ZXPDSS Software ..........................................................23

PDSN Software..............................................................24

OMC Software ...............................................................26

Interface Description ......................................27Interface Introduction ....................................................27

Interior Interfaces of ZXPDSS .........................................29

Interface between ZXPDSS and DBIO...............................30

Interface between ZXPDSS and Billing Center....................31

Interface between ZXPDSS and OMC................................32

Function Description .......................................33Supported PDSS Functions..............................................33

Simple IP Function.....................................................33

Mobile IP Function .....................................................33

Mobility Management Function ....................................34

1X/EV-DO User Access Function ..................................34

Multi-ISP Access Function ...........................................35

IP Class-Based User Classification Function ...................35

IP Address Binding Function........................................36

Always Online Function...............................................36

WAP User Access Function ..........................................36

Domain User Access Function......................................37

Local CDR Cache Function...........................................37

Local Authentication Function ......................................38

Operation and Maintenance Function ............................38

Multi-service Connection Function ................................39

Enhanced Multi-stream Function ..................................39

Bandwidth Limitation Function.....................................39

Access Control Function..............................................39

IP Address Allocation Function.....................................40

Lawful Interception Function .......................................41

QoS Guarantee Function.............................................41

Supported PDSS Services ...............................................42

Packet Prepayment Service .........................................42

L2TP-based VPN Service .............................................43

Multi-VRF VPN Service................................................43

Data Service Billing....................................................44

System Features..............................................45Processing Capability of System ......................................45

General Features ...........................................................46

Networking Feature ...................................................46

Interconnection Feature .............................................47

Convenience in Operation ...........................................47

Modulization .............................................................48

Reliability .................................................................49

Security Authentication Products Match ............................51

Mechanical Features........................................55Mechanical Features of PDSN Cabinet ...............................55

Mechanical Features of Server Cabinet .............................58

Mechanical Features of Alarm Box....................................59

Electrical Features...........................................61Electrical Features of PDSN Cabinet..................................61

Electrical Features of Server Cabinet ................................61

Electrical Features of Alarm Box ......................................62

Environment Requirements .............................63Requirements for Ground................................................63

Requirements for Temperature and Humidity.....................64

Requirements for Anti-Interference from Electromagnetic

Radiation..............................................................65

Requirements for Ventilation ...........................................66

Requirements for Fire-Fighting ........................................67

Requirements for Lighting...............................................67

Requirements for Anti-Electrostatic ..................................68

Requirements for Anti-lightning .......................................70

Requirements for Neatness .............................................72

Requirements for Earthquake Resistance Capability............74

Figures ............................................................75

Tables .............................................................77

List of Glossary................................................79

Preface

Purpose This manual introduces ZXPDSS P200 cdma2000 system features,services and functions, networking mode, and system configura-tion briefly.

IntendedAudience

This manual is intended for engineers and technicians who performoperation activities on the ZXPDSS P200 cdma2000 Packet DataServing Node.

Prerequisite Skilland Knowledge

To use this manual effectively, users should have a general under-standing of wireless telecommunications technology. Familiaritywith the following is helpful:

� ZXPDSS system and its various components

� Functions and services ZXPDSS can provide

� Local operating procedures

What Is in ThisManual

This manual contains the following chapters:

Chapter Summary

Chapter 1, Introduction toZXPDSS Introduces ZXPDSS in general.

Chapter 2, Hardware Description Introduces hardware configurationfor ZXPDSS.

Chapter 3, Software Description Introduces software configurationof ZXPDSS.

Chapter 4, Interface Description Introduces interfaces of ZXPDSS.

Chapter 5, Function Description Introduces functions of ZXPDSS.

Chapter 6, System Features Describes features of ZXPDSS.

Chapter 7, Mechanical Features Introduces mechanical features ofZXPDSS.

Chapter 8, Electrical Features Introduces electrical features ofZXPDSS.

Chapter 9, EnvironmentRequirement

Introduces environmentrequirements of ZXPDSS.

Confidential and Proprietary Information of ZTE CORPORATION i

ZXPDSS P200 Product Description

This page is intentionally blank.

ii Confidential and Proprietary Information of ZTE CORPORATION

C h a p t e r 1

Introduction to ZXPDSS

Table of ContentsZXPDSS System Architecture ............................................... 1Location of ZXPDSS in CDMA Network ................................... 3Usual Networking Modes...................................................... 5Performance Indexes of PDSN .............................................10

ZXPDSS SystemArchitecture

Overview In order to meet the requirements for packet data serviceand transmission, ZXPDSS is added into the core networkcdma2000-1X/HRPD. ZXPDSS includes two elementary entities,PDSN and AAA. In addition, ZXPDSS includes three optionalfunction entities, AN-AAA (supports EV-DO user access), LIS, andHA. With ZXPDSS, CDMA network can provide functions such ashigh-speed Internet access, video telephony, and digital business.

Architecture ZXPDSS system architecture is as shown in Figure 1.

FIGURE 1 ZXPDSS SYSTEM ARCHITECTURE

Functions The modules included in ZXPDSS implement the functions as de-scribed below:

Confidential and Proprietary Information of ZTE CORPORATION 1


� PDSN(Packet Data Serving Node)

PDSN is the gateway to access radio network and packet datanetwork. It provides Simple IP and Mobile IP access modes,which enables cdma2000 Mobile Station (MS) with packet dataservice to access Internet or Intranet.

� HA (Home Agent)

Home Agent (HA) is a router over the home network of MS. Itmanages information about current location of MS and estab-lishes correspondence between IP address of MS and IP ad-dress of MS a call is forwarded to. MS registers at HA beforemoving outside the registered network. HA delivers the pack-ets sent to MS to the forwarding address of MS through thetunnel between HA and FA. The packets are decapsulated andthen sent to MS. Thus mobile IP function is implemented.

Note: When ZXPDSS provides simple IP service, HA is unnec-essary. It is required only when mobile IP service is provided.

� LIS (Lawful Interception Server)

LIS implements information interaction between PDSN andlawful interception center.

� AAA (Authentication/Authorization/Accounting)

Authentication, Authorization, and Accounting (AAA) server isimplemented as a RADIUS server. AAA performs authentica-tion for users’ script files and authorization and accounting forthe data service. AAA also establishes new accounts of thedata service and performs management function.

� AN-AAA (Access Network-Authentication, Authorization, andAccounting)

AN-AAA server is implemented as a RADIUS server. It per-forms authentication for the access class of EV-DO network andverification for EV-DO client validity of EV-DO client, which isthe AN-Level verification. AN-AAA initiates and manages theEV-DO subscribers’ accounts.

In cdma2000 EV-DO network, there is no Circuit Switch (CS),which is included in original cdma2000 1X network. Therefore,when EV-DO subscriber access cdma2000 EV-DO network, theidentity verification is performed by AN-AAA instead of HLR,which is used normally in cdma2000 1X network for identityverification.

In ZXPDSS system, AN-AAA can be configured independentlyor in combination with AAA.

� OMC System

OMC system comprises of two parts:

OMC server

OMC client

OMC system implements the maintenance and managementfunctions for whole Packet Data Switching System.

� DBIO Server

DBIO module is the interface for the agent/billing interface toaccess the database. It implements various access operationsof the user database.

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Introduction to ZXPDSS

� Agent

Agent provides users with service acceptance function.

Location of ZXPDSS inCDMA Network

Description ZXPDSS is one of the important parts of cdma2000-1X/HRPD corenetwork. It provides Internet or Intranet service for cdma2000mobile station.

Location ofZXPDSS

ZXPDSS can be a network element for CDMA mobile networkssuch as cdma2000-1X network, cdma2000-HRPD network, andcdma2000-1X/HRPD network with BCMCS function.

In cdma2000-1X network, packet data service is implemented byMS, BTS, PCF, PDSN, AAA, and ZXPDSS location in cdma2000-1X(Phase1) network is shown in Figure 2.

FIGURE 2 ZXPDSS LOCATION IN CDMA2000-1X NETWORK

Similar to cdma2000-1X network, the packet data service incdma2000-HRPD network is jointly implemented by AT, AN, PCF,PDSN, AAA, HA (optional), and AN-AAA. ZXPDSSlocation in CDMA2000-HRPD network is shown in Figure 3.



FIGURE 3 LOCATION OF ZXPDSS IN CDMA2000-HRPD NETWORK

Other Entities The functions of other entities as shown in Figure 2 and Figure 3are described as follows:

� Mobile Terminal

Mobile Terminal (MT) includes Mobile Station (MS) and Ac-cess Terminal (AT). Cluster subscribers directly operate it. Forcdma2000 packet data service, MT refers to hand-held MobileStation, vehicle-mounted station, fixed station, notebook com-puter and PC.

� Base Station Subsystem

Base Station Subsystem comprises of Base Station Transceiver(BTS) and Base Station Controller (BSC). BSS provides accessto ordinary telephone service, data service, and other services.In addition, BSS includes the packet data control entity (PCF)to support data services.

� BTS is responsible for modulating and demodulating base-band signals, receiving and transmitting RF signals.

� BSC is responsible for the allocation of radio resources, callprocessing, power control, and supports various types ofhandovers of the terminals.

� PCF participates in the whole process of multiple types ofpacket data call control, including the setup of the commu-nication link in the originating process and the release ofthe communication link in the release process and in thepacket data hard handoff process.

� Mobile Switching System

Mobile Switching Subsystem (MSS) comprises entities suchas Mobile Switching Center (MSC), Home Location Register(HLR), Visitor Location Register (VLR), and AuthenticationCenter (AUC).

� MSC is a functional entity that controls and switches thevoice service of the terminal in the local service area anda connection device for the interworking and interconnec-



tion between the trunking service network and other publicnetworks over ordinary voice service.

� HLR provides the function of storing and managing relevantservice functions and user profiles. It also assists in com-pleting user calls and service operations.

� VLR is responsible for storing and updating the user dataof the MS which roams to this VLR service area. VLR storesthe information required for call establishment into thedatabase for the MSC to search.

� AUC is a function entity for the management of authen-tication information related to the mobile station. It au-thenticates the mobile users, stores the authentication pa-rameters of the mobile users, and is able to generate andtransport relevant authentication parameters according tothe MSC/VLR request.

� L2TP Network Server

L2TP Network Server (LNS) is the home network that L2TPtunnel accesses. It connects MS to VPN via L2TP tunnel.

� Prepayment Service/Service Control Point

When ZXPDSS provides packet prepayment service, it isnecessary to access ZXPDSS to PPS server or SCP. ExtendedRRADIUS protocol defined by 3GPP2 specifications is utilizedbetween AAA and PPS/SCP to transmit prepayment informa-tion of users.

Usual Networking ModesTypical Networking Modes

Networking Mode Typical networking mode of ZXPDSS system is shown in Figure 4.

FIGURE 4 TYPICAL NETWORKING MODE



NetworkingIntroduction

Integrated networking mode for ZXPDSS system is introduced be-low:

� ZXPDSS devices contain PDSN, AAA, HA, DBIO server andOMC. All are placed in identical LAN and directly connectedthrough switch.

� Firewall depends on the actual networking.

� PDSN can be connected with PCF through LAN, if PDSN andPCF are near in distance.

� PDSN can be connected with PCF in dedicated line mode orother IP connection modes, which can ensure stable transmis-sion bandwidth, if PDSN and PCF are far away from each other.

NetworkingFeatures

ZXPDSS networking features are as follows:

� ZXPDSS devices are deployed in integrated way, facilitating themanagement.

� PDSN-PCF transmission bearing modes are diversified:

When PDSN and PCF are close to each other, PCF can accessto PDSN directly through LAN.

In case that PDSN and PCF are far away from each other, PCFaccesses to PDSN in dedicated line mode or other IP connectionmodes which ensure stable transmission bandwidth.

Networking Mode Compliant withHRPD Specifications

Description In order to support access of 1x EV-DO users, AN-AAA is addedwhile perform networking.

Networking Mode The networking mode compliant with HRPD specifications is asshown in Figure 5.



FIGURE 5 NETWORKING MODE SUPPORTING EV-DO USERS

Note:

In Figure 5, HA is optional entity.


Networking mode supporting access of EV-DO users is describedas follows:

� Based on the 1X networking scheme, AN-AAA equipment isadded.

� AN-AAA supports multiple configuration modes.

� AN-AAA can be integrated with AAA.

� AN-AAA can be separated from AAA. In this case, AN-AAAcan be placed in either ZXPDSS network or BSS network(In Figure 5, AN-AAA is separated from AAA and positionedin ZXPDSS network).

� The above diagram shows the separated AAA and AN-AAA(in ZXPDSS network).

� The mode connecting AN-AAA and AN (BSC) is similar to thatfor PDSN-PCF connection.

NetworkingFeatures

This scheme has the following features:


� AN-AAA can be flexibly set.



Networking Mode Compliant withCAVE-Based Bimodal AuthenticationSpecifications

Description With networking compliant with CAVE-based bimodal authentica-tion specifications, inter-HLR circuit domain authentication mes-sage interface is introduced into AN-AAA.

Networking Mode The networking mode compliant with CAVE-based bimodal authen-tication specifications is as shown in Figure 6.

FIGURE 6 NETWORKING MODE COMPLIANT WITH CAVE-BASED BIMODAL AUTHENTICATIONSPECIFICATIONS


Networking mode compliant with CAVE-based bimodal authentica-tion specifications is described as follows:

� Based on 1X networking scheme, AN-AAA equipment is added.

� AN-AAA supports multiple configuration modes:

� AN-AAA can be integrated with AAA.

� AN-AAA can be separated from AAA. In this case, AN-AAAcan be placed in either ZXPDSS network or BSS network(In Figure 6, AN-AAA and AAA are separated).

� The above diagram shows the separated AN-AAA (in ZX-PDSS network) and AAA.

� The connection between AN-AAA and AN (BSC) is similar withthat between PDSN-PCF, which has diverse connection modes.



� The signaling front-end processor is directly connected withHLR through E1 line.

NetworkingFeatures

This scheme has the following features:


� AN-AAA can be flexibly set.

Networking Scheme for PacketPrepaid Service

Description ZXPDSS cdma2000 Packet Data Switching System supports twopacket prepayment networking modes, which are as follows:

� Enhanced 3GPP2 packet prepayment mode

� Fixed network mode

Both modes require integrated setting of SCP and PPS.

Enhanced3GPP2 Packet

Prepayment Mode

Enhanced 3GPP2 packet prepayment mode is shown in Figure 7.

FIGURE 7 PACKET PREPAID SERVICE NETWORKING SCHEME



Note:

Based on 1X networking mode, in enhanced 3GPP2 packet prepay-ment networking mode, PPS and SCP are added.

Fixed networkmode

The diagram for fixed network mode is the same as shown in Figure7.

Note:

For details about packet prepayment service, refer to ZXPDSSP200 cdma2000 Packet Data Serving Node Feature Description.

Performance Indexes ofPDSN

Description Performance indexes reflect whether the normal indexes PDSNsupports are higher or lower with certain configuration.

PerformanceIndexes

When PDSN has typical configuration, that is, PDSN has only onepair of interface boards, one pair of media boards, one pair ofSMPs and one pair of OMPs, the performance indexes of PDSN areas described in Table 1.

TABLE 1 PERFORMANCE INDEXES OF PDSN WITH TYPICAL CONFIGURATION

Capacity Index Value Remark

Number of activated (online)PPP connections 5000 Typical

Configuration

Number of A10 supported 5000*7 Active/standbyinterfaces

Maximum data throughput(1500 bytes) 1.6 Gbps Active/standby

interfaces

Maximum data throughput(IMIX model) 1.6 Gbps -

Packet forwarding ability (64bytes) 900Kpps -

Concurrent access ability 300/second -

Maximum number ofconnectable PCFs 512 -

Availability ≥99.999% -




Mean Time Between Failures(MTBF) ≥100,000 hours -

System Restoration Time ≤30 mins -

Note:

The performance indexes provided above are based on typical con-figuration of PDSN, which are only for reference. With differentconfigurations, the performance indexes of each function entityare vary greatly.


C h a p t e r 2

Hardware Description

Table of ContentsHardware Configuration of ZXPDSS......................................13Hardware Configuration of PDSN .........................................14Hardware Configuration of OMC...........................................18Hardware Configuration of LIS.............................................19Hardware Configuration of Alarm Box ...................................20Hardware Configuration of Other Devices..............................21

Hardware Configuration ofZXPDSS

Components ZXPDSS includes the following components in hardware:

� PDSN

� HA (optional)

� LIS

� AAA sever

� AN-AAA server

� OMC server

� OMC client

� DBIO server

� Firewall (optional)

� Alarm box

� Materials of matching devices

Classifications ZXPDSS devices are divided into two types, which are as follows:

� Foreground Devices

Foreground devices refer to PDSN and HA, including PDSN cab-inet, HA cabinet, shelves in cabinets, and all boards insertedin shelves.

� Background Devices

All other devices in ZXPDSS except PDSN and HA are called asbackground devices. These devices include servers, networkdevices, various clients, and alarm boxes.



Hardware Configuration ofPDSN

Description PDSN hardware platform consists of shelves (including level-1switching subrack, resources subrack, and control subrack) andvarious circuit boards.

Boards in PDSN system include:

� Interface unit (GLIQV, FLIQV)

� Network processing unit (URPM)

� Control plane processing unit (MP)

� Switching unit (PSN, UIM)

Boards which can be plugged in subracks are shown in Table 2 andTable 3.

TABLE 2 FRONT BOARDS

Functional Unit Physical Board Remark Redundancy Mode

GLIQV

This board ispositioned in level-1switching subrack,providing two Ginterfaces

1 (ActiveBoard)+1(StandbyBoard)

FLIQV

is positioned in level-1switching subrack,providing six 100 Mports outward.


Interface Unit

URPMPDSN RP/PI mediaservice processingboard

1 (ActiveBoard)+1(StandbyBoard) plus loadsharing mode

OMP/RPUserviceprocessing board

OMP provides OMCinterface outward;RPU implementsmaintenance of routinginformation on thenetwork processingunit


Control PlaneProcessing Unit

PDSN SignalingService ProcessingBoard (SMP)

Implementingprotocols and signalingprocessing of PDSN


Packets SwitchingBoard PSN

Implementing IPswitching at mediaplane

1 (ActiveBoard)+1(StandbyBoard) plus loadsharing mode

Switching Unit

UIM Board

ImplementingEthernet switching atcontrol plane, mediaplane, and level-1circuit switching



Chapter 2 Hardware Description

TABLE 3 REAR BOARDS

Logic IDon Boards Board Name

PrintedName Remark

RMPB Rear board of OMP RMPB- -

RUIM2 Rear board of UIM(Type 2) RUIM2 -

RUIM3 Rear board of UIM(Type 3) RUIM3 -

RPSN Rear board of PSN RPSN

Configuredfor systemmaintenance,providingoutward Ethernetinterface andserial portof PPSN fordebugging.

RGIM1

Rear boardfor debuggingGLIQV,URPM (Type1)

RGIM1

Configuredfor systemmaintenance,providingoutward Ethernetinterface ofGLIQV and URPMfor debugging;must be replacedby empty panelafter debugging.

Note:

Logic IDs of boards are different from the names printed on boardsand the board names seen from rearward.

PDSN HardwareSystem

Block diagram representing PDSN hardware system is shown inFigure 8.



FIGURE 8 BLOCK DIAGRAM REPRESENTING PDSN HARDWARE SYSTEM

PDSN HardwareStructure

Block diagram representing PDSN hardware structure is shown inFigure 9.



FIGURE 9 BLOCK DIAGRAM REPRESENTING PDSN HARDWARE STRUCTURE

Functional BlockDiagram of PDSN

Functional block diagram of PDSN is shown in Figure 10.



FIGURE 10 FUNCTIONAL BLOCK DIAGRAM

Hardware Configuration ofOMC

Description OMC facilitates operation and maintenance of the system by pro-viding graphic interfaces for maintenance personnel.

In ZXPDSS, operation and maintenance systems in PDSN, HA, andAAA all include operation and maintenance server and operationand maintenance client. Universal PC servers are used as OMCservers and universal PCs as OMC clients.

Basic Configura-tion

Basic hardware configuration for OMC is shown in Table 4.

TABLE 4 BASIC HARDWARE CONFIGURATION FOR OMC

ModelOperation &Maintenance

ServerOperation &

Maintenance Client

CPU Both CPU (≥2.8 GHz) Single CPU (≥1.8 GHz)

Memory ≥2 G ≥1 G

Hardware 2×36 GB (10 Krpm) 40 GB

Network Card Two NICs; One 100Madapter Two NICs

ConfigurationList per server



ModelOperation &Maintenance

ServerOperation &

Maintenance Client

SpecialConfiguration

One RAID card integratedwith main board, used toconfigure the two local harddisks as RAID1

-

Other Configura-tion

Integrated display adapter,software drive, compactdisk, dual power supplies

Display adapter/17”color display/ compactdisk/Standard OS/keyboard /mouse /HP LJ5000LE or similarprinter

Rack fixture set Yes None

Amount One set for PDSN and onefor AAA Multiple

DELL2850;Recommended Model

HP DL380 G4PC

Note:

The actual amount of the operation and maintenance client is con-figured based on the actual condition of each system. However,both PDSN and AAA should be configured with at least one set ofoperation and maintenance client.

If mobile IP service is available, at least one set of operation andmaintenance server and client for HA.

Hardware Configuration ofLIS

Description Lawful interception server uses general computers as its hardwareplatform. Basic requirements for the computers are as shown inTable 5.

TABLE 5 HARDWARE PLATFORM OF LIS

Function Node Lawful Interception Server

Computer Type One universal PC server

Hard Disk Capacity Capacity≥20G



Function Node Lawful Interception Server

Network Adapter At least 2 network adapters withidentical model

Others Integrated display adapter/floppydrive/CD-ROM/dual power supplies

Hardware Configuration ofAlarm Box

Description ZXPDSS has relatively perfect alarm system. It includes PDSNalarm system, AAA server alarm system, HA alarm system (onlywhen the system has HA function), and correspondent alarmboxes.

Alarm SystemComponents

Schematic diagram of alarm system is as shown in Figure 11.

FIGURE 11 SCHEMATIC DIAGRAM OF ALARM SYSTEM

For the functions of the parts shown in Figure 11, refer to Table 6.

TABLE 6 PARTS AND FUNCTIONS

Alarm System Function Description

Foreground alarmsystems

Collect and process foreground alarms,implement background man-machinecommands, and returns results.

Server-end alarmsystem

Processes, saves and forwards information,and controls alarm boxes.



Alarm System Function Description

Client-end alarm systemDisplays, queries, prints alarms, displaysrack diagram, and executes man-machinecommands.

Alarm BoxA device with indicator lights and louderspeaker to indicate operation status of aswitch.

Configuration ZXPDSS alarm system is composed of the following:

� Alarm box

CPU is the most important part of alarm box. CPU receives thealarm information, which is sent from the background throughEthernet interface. During running state of the system, alarmbox prompts the current failures in the form of sound, light,liquid crystal display, short messages, and transmitted files.

Besides the sound, light and liquid crystal output, the alarmbox has mobile phone module and Modem module to sendalarm messages in the form of short message. If there is largeamount of information to be sent to the control center, it canbe implemented through Modem dial-up. The mobile phonemodule is normally put inside the alarm box and an externalmobile phone can also be connected through RS232/RS485 in-terface to perform the same function.

� OMC system

OMC system has two entities as follows:

� OMC server

OMC server is connected with the alarm box. It sends thealarm messages through TCP/IP protocol to the alarm boxand sends the alarm short massage to the specified num-ber through the mobile phone module on the alarm box.Alarm box displays the alarm message on the liquid crystaldisplay, and provides prompts with the alarm indicator lightand alarm tone. OMC server determines whether to trans-mit the error log files utilizing the mobile phone module.

� OMC Client

Through OMC client, user can set the alarm level requiredat which alarm box sends alarm short messages, and themobile phone number to which the short message is sent,and the number of the short message center, and the num-ber dialed to transmit files.

Hardware Configuration ofOther Devices

Description ZXPDSS system also needs to configure routers, firewalls, bridgesand other facilities, for the realization of the system’s equipmentand between the system and external network connectivity.



Basic Configura-tions

Basic configurations for other devices are shown in Table 7:

TABLE 7 HARDWARE CONFIGURATION OF OTHER DEVICES

Device Configuration List AmountRecommended

Model

FirewallAppendixes with 168bitencrypted license |CISCOPIX-VPN-3DES

2 Suites PIX-515E-R-BUN

L2 Switch24 FE Network Ports,two 1000 M optical fiberinterfaces

2 Suites

Allied AT-8724xl (oneswitch is equipped withone optical moduleAT-A35SX/SC), CiscoWS-C2950SX-24

Network Bridge Four-way switching from E1to 10/100 M Ethernet Optional

Converters CTCETU-04, JS-044E1/10BASE-T

L3 Switch24 FE Network Ports,two 1000 M optical fiberinterfaces

1 Suite Allied AT-8724xl

Optical connector(multi-modefiber)

Actual length is determinedbased on project survey 1 Suite -

Note:

Configuration and model in the table above are only recomendedconfiguration, and can be adjusted according to the different re-quirements of the system.


C h a p t e r 3

Software Description

Table of ContentsZXPDSS Software ..............................................................23PDSN Software..................................................................24OMC Software...................................................................26

ZXPDSS SoftwareSoftware

CompositionZXPDSS software is correspondent with ZXPDSS hardware. PDSN,AAA and HA have correspondent software.

PDSN software is composed of PDSN version software and OMCsoftware.

SoftwareClassification

In order to distinguish software in ZXPDSS, ZXPDSS software isdivided as follows:

� Foreground software

� Foreground software generally refers to version softwareloaded in PDSN and HA, including version software and con-figuration information of all boards on PDSN and HA.

� Background software

� Other software except the version software loaded in PDSN isgenerally called background software, including software usedin AAA server, AN-AAA server, OMC, network devices, termi-nals, and alarm boxes.

Relation BetweenSoftware and

Hardware

In ZXPDSS, the corresponding relation between software andhardware is shown in Table 8 and Table 9.

TABLE 8 RELATION BETWEEN SOFTWARE AND HARDWARE (PDSN)

Hardware Correspondent Software

PDSN foreground PDSN version software

OMC server OMC server software

OMC client OMC client software



TABLE 9 RELATION BETWEEN SOFTWARE AND HARDWARE (AAA)

Hardware Correspondent Software

AAA server AAA software

OMC server OMC server software

OMC client OMC client software

Note:

For software configuration in HA, refer to the delivery attacheddocument of HA device.

Installation Mode After completing the hardware installation, install all software inZXPDSS according to the description in software installation man-ual.

PDSN SoftwareDescription PDSN software is composed of PDSN version software and OMC

Unified Network Management Platform corresponding to PDSN.

Required software in OMC server includes operating system Win-dows 2000 or 2003, database software SQL, and OMC server soft-ware. Required software in OMC client includes operating systemWindows 2000 or 2003 and OMC client software.

PDSN VersionSoftware

PDSN version software corresponds to various boards on PDSNforeground. Generally, the software includes 31 independent files.Table 10 shows the list of version files.

TABLE 10 FILES INCLUDED IN PDSN VERSION SOFTWARE

Version File NameCorrespondent

ModuleFunc-tion

AHDLC_00_050300_FPGA_105._V3.08.11.B5.BIN FPGA of URPM

GLIQV_01_040202_FPGA_104._V3.08.11.B5.BIN

GLIQV2_03_060201_FPGA_105._V3.08.11.B5.BIN

GLIQV2_04_060203_FPGA_107._V3.08.11.B5.BIN

FPGA software ofGLIQV

MPX86_05_040202_FPGA_105._V3.08.11.B5.RBF

MPX862_04_040704_FPGA_107._V3.08.11.B5.RBFFPGA of MP

FPGApro-cessesHDLC


Chapter 3 Software Description

Version File NameCorrespondent

ModuleFunc-tion

UIM2_02_040204_FPGA_16KNET_102._V3.08.11.B5.BIN

UIM2_02_040205_FPGA_16knet_102._V3.08.11.B5.BIN

UIM2_03_060201_FPGA_UIMU_100._V3.08.11.B5.BIN

FPGA of UIM

UPB_00_050301_FPGA_101._V3.08.11.B5.BIN

UPB_01_060201_FPGA_103._V3.08.11.B5.BINFPGA of UPB

PDSS_GLIQV_IGPS_EGRESS_V3.08.11.B5.UOF Egress module of IGPS

PDSS_GLIQV_GCONT_EGRESS_V3.08.11.B5.UOF Egress module ofGCONT

PDSS_UPB_URPM_EGRESS_V3.08.11.B5.UOF Egress Microcode Soft-ware for URPM

Egressdistrib-utesserv-ice dataand mes-sages

PDSS_GLIQV_IGPS_INGRESS_V3.08.11.B5.UOF Ingress module of IGPS

PDSS_GLIQV_GCONT_INGRESS_V3.08.11.B5.UOF Ingress module ofGCONT

PDSS_UPB_URPM_INGRESS_V3.08.11.B5.UOF Ingress module ofURPM

Ingressreceivesserv-ice dataand mes-sages

PDSS_MPX86_2_MP_P4_V3.08.11.B5_Z.BIN

PDSS_MPX86_MP_X86_V3.08.11.B5_Z.BINMP module

LoadingMP mod-ule

PDSS_MPX86_2_RPU_P4_V3.08.11.B5_Z.bin

PDSS_MPX86_RPU_X86_V3.08.11.B5_Z.binRPU module

Load-ing RPUmodule

PDSS_PSN_PSN_852_V3.08.11.B5_Z.bin

PDSS_PSN_PSN_860_V3.08.11.B5_Z.binPSN module

Load-ing PSNboard

PDSS_UIM_2_UIM_755_V3.08.11.B5_Z.bin

PDSS_UIM_2_UIM_8260_V3.08.11.B5_Z.binUIM module

Load-ing UIMboard

PDSS_GLIQV_GCONT_CPU0_XSCALE_V3.08.11.B5_Z.BIN

PDSS_GLIQV_GCONT_CPU1_XSCALE_V3.08.11.B5_Z.BINGCONT module

LoadingGCONTboard

PDSS_UPB_URPM_CPU0_XSCALE_V3.08.11.B5_Z.bin

PDSS_UPB_URPM_CPU1_XSCALE_V3.08.11.B5_Z.binURPM module

LoadingURPMboard

PDSS_GLIQV_IGPS_CPU0_XSCALE_V3.08.11.B5_Z.bin

PDSS_GLIQV_IGPS_CPU1_XSCALE_V3.08.11.B5_Z.binIGPS module

Load-ing IGPSboard



Note:

Version files listed in Table 10 are only for reference. The namesof foreground version files vary with version numbers.

OMC SoftwareDescription Generally, OMC server software corresponding to PDSN is installed

in general PC servers and OMC client software is installed in gen-eral PCs. The software details are shown in Table 11.

TABLE 11 OMC SOFTWARE FOR PDSN

Correspond-ent Server

OperatingSystem Database

ApplicationName Function

OMC ServerWindows 2000AS or WINDOWS2003 AS

SQL Server 2000or SQL Server2005

OMC UnifiedNetworkManagementplatform(includingsoftware forserver and client)

OMC is usedto configureZXPDSS. Itcooperates withforegrounddevices tomanage theboards andmodules inZXPDSS.

OMC ClientWindows 2000AS or WINDOWS2003 AS

None

Software forclient in OMCUnified NetworkManagementplatform

PerformsconnectingOMCserver, providingconfigurationand maintenanceinterface.

Note:

For software configuration of HA OMC, refer to the delivery at-tached document of HA devices.


C h a p t e r 4

Interface Description

Table of ContentsInterface Introduction ........................................................27Interior Interfaces of ZXPDSS .............................................29Interface between ZXPDSS and DBIO...................................30Interface between ZXPDSS and Billing Center........................31Interface between ZXPDSS and OMC....................................32

Interface IntroductionDescription Interfaces include the devices interior to the system, and those for

interior and the exterior devices.

When interfaces are mentioned, two aspects are always included,one is the hardware connection mode utilized for interfaces, andthe other is the types of protocols used for interfaces. Hence,interfaces are closely related with communication protocols.

ZXPDSSInterfaces incdma2000-1X

Network

ZXPDSS interfaces based on cdma2000-1X network are as in Fig-ure 12.



FIGURE 12 ZXPDSS INTERFACES (BASED ON CDMA2000-1X)

ZXPDSSInterfaces

Based on HRPDSpecifications

ZXPDSS interfaces based on HRPD specifications are as shown inFigure 13.

FIGURE 13 ZXPDSS INTERFACES (BASED ON HRPD SPECIFICATIONS)

In Figure 12 and Figure 13, each functional module is connectedvia Ethernet. And the other functional modules except lawful inter-ception module use TCP/IP protocol to carry interface information.


Chapter 4 Interface Description

Interior Interfaces ofZXPDSS

Description The interior interfaces of ZXPDSS include interfaces among PDSN,LIS, AAA, AN-AAA and corresponding OMC.

Interface BetweenPCF and PDSN

The interface between wireless network RN (that is BSC/PCF) andPDSN is R-P interface, which is an A10 or A11 interface as stipu-lated in the 3GPP2 specifications. Here, A10 interface is the serviceinterface between PCF and PDSN, and A11 interface is the singlinginterface between PCF and PDSN.

InterfacesBetween PDSN

and AAA

RADIUS protocol is adopted between PDSN and local AAA server totransmit authorization, authentication and accounting information.AAA server is used as the server end of RADIUS protocol, andPDSN serves as the client of RADIUS protocol.

InterfacesBetween PDSN

and HA

When PDSN provides mobile IP service, it acts as FA. IP protocol isused between PDSN/FA and HA to transmit mobile IP registrationinformation of subscribers, thus establishes data tunnel for sub-scribers and transmit packet data for subscribers.

InterfacesBetween HA and

AAA

RADIUS protocol is used between HA and home AAA server totransmit authentication and authorization information of mobile IPsubscribers. AAA server acts as the server of RADIUS protocol.And HA acts as the client of RADIUS protocol.

Interface betweenPDSN and LNS

When ZXPDSS provides data VPN service, PDSN acts as LAC (L2TPAccess Concentrator). In this case, L2TP protocol is used betweenit and LNS, providing packet transmission and carrier for users whoremotely access to enterprise LNS.

InterfacesBetween AAA and

PPS

To support the packet prepayment solution with AAA separatedfrom PPS, the extended RADIUS protocol defined by the 3GPP2specifications is used between AAA and PPS to transmit sub-scribers’ prepayment information.

Interface BetweenAAA/PPS and SCP

To support combination of AAA and PPS, SCP manages packet pre-payment solution of subscriber accounts, and the extended RA-DIUS protocol is used between AAA/PPS and SCP to transmit sub-scribers’ prepayment information.

InterfacesBetween AN and

AN-AAA

When ZXPDSS provides access function for EV-DO subscribers,A12 interface defined by 3GPP2 specifications is used betweenAN-AAA and AN to implement AN-Level authentication function.

Interface BetweenAN-AAA and

HLR/AUC

The interface between AN-AAA and HLR/AUC is the authenticationinterface defined by ANSI-41-D specifications. It performs authen-tication and SSD sharing based on CAVE algorithm.

Interface BetweenPDSN and OMC

OMC is connected with PDSN through SNMP interface to enablethe operation and maintenance on PDSN, including configuring thedaily operation data of PDSN, performance management, alarmmanagement, and signaling tracing.

Interface BetweenAAA And OMC

OMC is connected with AAA through SNMP interface to enable theoperation and maintenance on AAA, including AAA performancemanagement and alarm management.

Interface betweenLIS and LIC

LIC is connected with LIS through lawful interception interfaces,which can be logically divided into 3 interfaces, No.1 interface, No.2 interface, and No. 3 interface.



For details about lawful interception interfaces, refer to ZXPDSSP200 cdma2000 Packet Serving Node LIS Manual.

Interface between ZXPDSSand DBIO

Description Interface between ZXPDSS and accounting system of carriers iscalled accounting interface (or DBIO interface). Accounting in-terface is the open interface provided by AAA for the accountingsystem of carriers and to meet the requirements of the accountingsystem of carriers to access AAA service database.

Accounting system of the carriers logs into the accounting interfacethrough exterior gateway TCPOUT (the login name and passwordare both admin), and then sends request through the accountinginterface to access the AAA database, and process the subscribersinformation in the database.

Location ofAccountingInterface

The accounting interface exists between ZXPDSS and accountingsystem of the carriers, the specific position is shown in Figure 14.

FIGURE 14 LOCATION OF ACCOUNTING INTERFACE

Basic Functions Through accounting interface, ZXPDSS provides message inter-face for accounting system of carriers, transmits the online ac-counting commands (including service acceptance, account open-ing, account writing off, subscribers’ information querying) sent bythe accounting system of carriers, performs relevant operations onAAA service database, and returns the results to accounting sys-tem.

CommunicationMode

Accounting interface of ZXPDSS is based on TCP/IP protocol andtransmits standard IP packet.

Requirements In order to ensure normal operation of the accounting interface, itis necessary to guarantee normal communication of the IP link be-tween accounting system of carriers and DBIO server of ZXPDSS.


Chapter 4 Interface Description

Interface between ZXPDSSand Billing Center

Description The interface between ZXPDSS and billing center of carriers iscalled as billing interface. Billing interface is an open interfaceprovided by AAA server for the billing center of carriers and tomeet the requirement of the billing center to access AAA serverand extract CDR files.

Billing interface provided by ZXPDSS is standard FTP interface.

Location of BillingInterface

Billing interface is located between ZXPDSS and billing center ofcarriers, as shown in Figure 15.

FIGURE 15 POSITION OF BILLING INTERFACE

Basic Functions AAA server uses FTP service process of the system and providesFTP service. It allows the billing center to log into AAA serverthrough FTP interface as FTP user (generally, ftpget) every fixedperiod, to extract CDR files from FTP directory and performs pricingprocess. Generally, the billing center deletes the extracted CDRfiles.

CommunicationMode

Billing interface of ZXPDSS is based on FTP protocol. Collectors ofAAA server and the billing center are connected through networkcable. It transmits standard IP packet.

Requirement To ensure the normal operation of the billing interface, it is neces-sary to guarantee that the IP link between AAA server of ZXPDSSand the billing center of carriers is normal.



Interface between ZXPDSSand OMC

Description OMC is used to implement operation and maintenance on eachfunctional module in PDSN.

OMC generally has server/client structure. The server is the corepart of the entire OMC, having powerful processing ability. It cansave a big amount of data with short response time and is stableand reliable enough. Subscribers may conduct various manage-ments on MSS system through the man-machine interface andprograms run in the client which is usually a PC based on Windowssystem. Large relation-type database (for example: SQL Server)is used to provide such services as data saving and data querying.

InterfaceClassification

Interfaces between ZXPDSS and OMC include three types, inter-faces with network elements, interfaces with the upper level net-work manager, and interfaces with subscribers, as shown in Figure16.

FIGURE 16 INTERFACES BETWEEN ZXPDSS AND OMC

Basic Function Network element interface is private interface. It provides accessability for network elements of ZXPDSS. The data about proper-ties of network elements and alarms is uploaded to OMC throughthe network element interface. The management commands ofsubscribers are sent to network elements through the network el-ement interface and performed. OMC system provides networkelement interface through the Element Mediation Function (EMF)module.

CommunicationMode

The interface between OMC and the upper level network manageris CORBA interface, thus OMC is able to access to integrated net-work management system.

The interface for subscribers is G interface, provided by WSF sub-system, and used for OMC to interact with subscribers.


C h a p t e r 5

Function Description

Table of ContentsSupported PDSS Functions..................................................33Supported PDSS Services ...................................................42

Supported PDSS FunctionsSimple IP Function

Description Simple IP is an access mode in which CDMA packet data networkprovides mobile users with data service. Users acquire dynamicand variable IP addresses while implementing data communicationin this access mode.

Details That users access to packet data network using mobile station insimple IP mode is similar to that users access to Internet usingfixed telephone through dialing on Modem.

While accessing to packet data network using simple IP function,a user acquires an IP address from the service access provider.This IP address is dynamic and variable. The user keeps the allo-cated IP address within the network covering a certain geographicscope. But if the user moves outside the geographic scope (cross-ing PDSNs), the system terminates the ongoing data communica-tion. The user must reinitiate the data communication.

Simple IP function only implements the data communication withMSs as callers. With simple IP mode, addresses are only allocatedwhile users accessing, so the IP address resources occupied in thismode is comparatively less.

While users accessing in simple IP mode, the serving PDSN or theserving AAA allocates dynamic IP addresses for mobile stationsand provides IP route service. PPP protocol is utilized betweenmobile stations and PDSN as the data link protocol.

Mobile IP Function

Description Mobile IP function is another access mode in which CDMA packetdata network provides mobile users with data service. Users ac-



quire permanent and IP addresses constant while implementingdata communication in this access mode.

Details Mobile IP function is a solution of providing mobile data commu-nication function over global Internet. When users access in mo-bile IP mode, they can move to anywhere within CDMA networkscope or other network scope and keep identical IP address. Thatmeans MS keeps the ongoing data communication even if it crossesPDSNs.

Mobile IP function implements data communication when MS is thecalled party.

Mobility Management Function

Description The mobility management of the system enables MS to keep theoriginal PPP session with PDSN while handing over within PCF,crossing PCFs within PDSN, or crossing PDSNs.

Handover withinPCF

The system enables MS to hand over within one PCF.

While handing over within PCF, the R-P session between PCF andPDSN still goes on, because PDSN does nothing in controlling thiskind of handover.

HandoverCrossing PCFswithin PDSN

The system enables MS to hand over crossing PCFs within onePDSN. PDSN supports unique R-P session between each MS andPCF. PDSN interacts with the two PCFs before and after handoverof MS through A11 interface, releases the R-P session with the for-mer PCF, and creates the R-P session with the latter PCF. Thus thehandover between PCFs is done without terminating the originalPPP session.

HandoverCrossing PDSNs

The system enables MS to hand over crossing PDSNs in mobile IPmode.

When a MS with mobile IP service hands over crossing PDSNs, thePPP session between the MS and the target PDSN is created, andthe MS reinitiates mobile IP registration, informing HA to updatethe forwarding address, in order to keep the mobile IP session. Theresource PDSN initiates release of the original R-P session and PPPsession after the mobile IP registration timer times out.

1X/EV-DO User Access Function

Description When ZXPDSS provides AN-AAA, and supports EV-DO user accessauthentication complying with the definition for A12 interface, itsupports both 1X and EV-DO users to access.

Details 1X users still access to IP network through BSC/PCF and PDSN.AAA performs user authentication. ZXPDSS provides 1X users withwireless data service capacity of 153.5kbps.

EV-DO users access to network through EV-DO AN, EV-DO PCFand PDSN. AN-AAA performs AN-Level authentication on users.ZXPDSS provides EV-DO Rev 0 users with wireless data servicecapacity up to 2 Mbps. And ZXPDSS provides EV-DO Rev A userswith wireless data service capacity up to 3.1Mbps.


Chapter 5 Function Description

Multi-ISP Access Function

Description When carriers implement packet data service, they can alterna-tively introduce multiple ISPs for cooperation besides providingpublic IP network resource for users. Different users access to dif-ferent ISPs. Thus enrich the ISP services provided for users andprolong the product chain of carriers.

Details ZXPDSS supports multiple ISPs to access, and provides three ISPselection schemes.

� Selecting ISP based on the ISP address information in sign-upinformation of users.

� Users’ sign-up information is included in users’ sign-up in-formation of home AAA, in which authentication informa-tion related with ISP, such as ISP Server (LNS) address, isincluded.

� When users access, the home AAA determines that theuser’s sign-up information includes ISP information, thenit returns the ISP information to PDSN in the message Ac-cess Accept.

� Selecting ISP based on the Domain information of the sign-upattributes of users.

The users’ sign-up information saved in the home AAA com-prises information about users’ domain.

� In the home AAA, the correspondence between users’ do-main and ISP is configured.

� When users access, the home AAA matches the domaininformation in users’ sign-up information with the ISP in-formation configured in AAA system, determines which ISPa user belongs to, and returns the ISP information to PDSNin the message Access Accept.

� Select ISP based on the realm information in users’ NAI.

� In the Home AAA, the correspondence between the realmof user NAI (with a format of UserName@Realm) and ISPis configured.

� When users access, the Home AAA matches the realm in-formation comprised in user NAI with the ISP informationconfigured in AAA, determines which ISP a user belongsto, and returns the ISP information to PDSN in the mes-sage Access Accept.

IP Class-Based User ClassificationFunction

Description ZXPDSS supports user classification based on IP class. Differentaccess policies are configured for each IP section through routesand firewalls of the system.



Details In ZXPDSS, different access policies can be configured for eachIP section through routes and firewalls of the system. And usersof different classes can be allocated with addresses of different IPsections (including public network and private network addresses)from different IP address pools. Thus different users accessing topacket access system have different access resources and author-ities.

IP Address Binding Function

Description ZXPDSS supports binding of users and IP addresses in simple IPservice mode.

Details For standard simple IP service, when users log in, ZXPDSS dynam-ically allocates IP addresses for terminals and the addresses dy-namically changes. User can only make a call but can not be called.In other words, the other hosts over the network cannot activelyaccess to this mobile terminal. As a result, such characteristic ser-vices as point-to-point communication, dynamic video monitoringand video conference are unavailable. In addition, when simple IPaccess users initiate inter-PDSN handoff, service termination usu-ally occurs due to dynamic IP address assignment.

IP address binding technology implements sustained service uponinter-PDSN handoff occurs in simple IP access mode. Meanwhile,ZXPDSS supports point-to-point communication, dynamic videomonitoring and other functions which are only supported by mo-bile IP communication.

Always Online Function

Description ZXPDSS supports always online function for users and detects thestates of terminals periodically. If it finds a terminal in standbymode, it actively activates the user.

Details ZXPDSS supports always online users, and holds specific serviceterminals, such as bank service terminal and video monitoring ter-minal, always activated. In always online mode, the system main-tains the service connection and makes it free from release due totimeout, regularly detects the activity states of the terminals, andautomatically activates terminals in standby mode.

WAP User Access Function

Description To enable WAP users to log into the WAP gateway through ZXPDSS,AAA supports transmission of user’s UDR information to the WAPgateway.

Details When a WAP user logs in PDSN to get online:

1. PDSN sends the Accounting Start message to AAA.

AAA determines this user as WAP user.



2. AAA forwards the Accounting Start message to the WAP gate-way.

WAP determines that the user is online based on this message,and then records the correspondence between the user’s IPaddress and IMSI.

3. After this, PDSN sends the IP data message of the WAP userto the WAP gateway. Thus comprehensive WAP service is im-plemented.

When the WAP user gets offline, PDSN sends the AccountingStop message to AAA. AAA determines this user as WAP user,and then forwards the Accounting Stop message to the WAPgateway, which determines the user as offline based on thismessage.

Domain User Access Function

Description ZXPDSS supports users accessing with different domain postfixes(for example. user@realm). PDSN accesses to different AAAs(Visit AAA or Home AAA) according to the domain postfixes toperform authentication and accounting.

Details When Home AAA of a domain subscriber and Home AAA of othernon-domain subscribers are not in the same network, the accessmode mentioned above can be considered. Different from the VPNaccess modes (such as L2TP), in this mode, the subscriber onlyneeds to open an account in AAA of VPN network. When the sub-scriber accesses to PDSN, PDSN is directly connected to that AAAfor authentication and accounting. Besides, it is unnecessary toaccess through a tunnel when accessing to the VPN network of adomain subscriber.

Besides authentication at different AAAs, PDSN may also distributeIP address specified by PDSN (or AAA) for domain subscribers, todistinguish them from common non-domain subscribers. Differentdomain users accept authentication and accounting at differentAAAs.

Local CDR Cache Function

Description PDSN of ZXPDSS has CDR cache function and stores the account-ing information of users in local disk.

Details The CDR cache function of PDSN is represented in two aspects:

� While the accounting server (that is AAA server) is down, PDSNstores the Accounting Start and Accounting Stop messages tobe sent in local directory.

� When the accounting server restores, PDSN sends the account-ing record stored in local disk to the server.



Local Authentication Function

Description When the communication between PDSN and AAA is interrupted,user authentication can be performed at PDSN to guarantee thesuccess of users in accessing.

Details In some cases, users may fail in accessing due to intermediatetransmission network faults or AAA server abnormalities. In orderto guarantee the success of users in accessing and improve theexperience of users, PDSN automatically activates local authenti-cation mechanism after it detects that the remote AAA does notrespond to successive access requests. Meanwhile, PDSN regu-larly detects the status of AAA server. When AAA server restores,the subsequent access requests of users are authenticated at AAAserver.

Operation and Maintenance Function

Description The operation and maintenance system OMC of ZXPDSS performsfunctions such as system management, fault management, per-formance management, configuration management, and systemtool.

Details The functions of the subsystems of OMC are described as follows:

� System management subsystem

This subsystem includes five modules, topology management,policy management, system management, log management,and security management.

� Fault management subsystem

This subsystem includes two modules, alarm management andalarm box management.

� Performance management subsystem

This module supports users to collect various performance in-dexes through creating measurement tasks (including serviceamount, resources used, and service quality), and further an-alyze the working status of the network . Thus provide basisand verification method for optimizing network.

� Configuration management subsystem

This subsystem controls the configuration of NE devices ona whole, including identifying NEs, collecting data associatedwith NE configuration from NEs, designing the capacity of el-ementary network devices based on the services specified innetwork plan and traffic load and requirement prediction, andconfiguring various resources (such as physical devices anddata parameters)

� System tool subsystem

This subsystem provides functions such as signal tracing, fail-ure observation, service observation, version management,probe management, and clock management.



Multi-service Connection Function

Description Users can map different services to different A10 links throughcreating auxiliary connections besides main connection.

Details Besides web exploring, FTP downloading, in packet data service,a subscriber may request such QoS guaranteed advanced servicessuch as VoIP and online video. For the purpose of carrying outservices that require high-degree QoS guarantee, auxiliary con-nections may be created for users besides the main connection.

Here, main service connection is created when packet data ser-vice is initially created, providing QoS guarantee of Best-effort bydefault.

Auxiliary service connections are normally used to carry out ser-vices requiring special QoS guarantee such as VoIP. PDSN mapsservices of different QoS guarantees to different A10 links accord-ing to TFT template negotiated with AT terminal and authorized byservices.

Enhanced Multi-stream Function

Description PDSN provides enhanced multi-steam function to optimize datatransmission channel and reduce message transmission latency.With this function, real-time services such as VoIP, video tele-phone, and video on demand are better implemented.

Details In order to better support latency-sensitive real-time services suchas VoIP, video telephone, and video on demand services, to opti-mize the data transmission channel for the type of services andreduce transmission latency, PDSN supports segment-based frag-ment.

Bandwidth Limitation Function

Description To protect investment of carriers better and provide users with di-versified service qualities, ZXPDSS supports user bandwidth limi-tation function, to control the largest available bandwidth for users’uplink and downlink media stream.

Details PDSN detects, monitors, and measures the transmission rate ofusers’ media stream in real time according to the limited band-width authorized by AAA. When the rate exceeds the thresholdvalue, traffic shaping is performed to stabilize the message trans-mission rate and protect the investment of carriers.

Access Control Function

Description ZXPDSS implements access control function based on differentusers.



Details ZXPDSS supports PAP/CHAP based service authentication to verifywhether users are valid or not. Additionally, the system supports1x/DO access control. PDSN can set whether 1x users or DO usersare allowable to access special services. Thus refined service con-trol is implemented.

IP Address Allocation Function

Description ZXPDSS supports diversified IP address allocation policies to meetdifferent requirements.

IP Address Pool PDSN allocates different IP address pools and IP addresses for dif-ferent users.

� Different IP address pools are allocated to distinguish usernames and domain names.

PDSN allocates IP address pools independent from each otherfor different users. With this IP address allocation policy, pub-lic network and office network users and value-added serviceusers use independent IP address pool. The IP addresses ofdifferent users are separated from one another, and policiescan be set to prohibit accessing between different users.

� Different IP addresses are allocated to distinguish public net-work and private network.

PDSN allocates IP addresses of different types for differentusers. With this mode, different IP addresses are allocated todistinguish public network and value-added service network.Users of different networks use respective routes. And policiescan be set to prohibit users of different networks from data in-teracting.

IP AddressAllocation Mode

PDSN supports the following IP address allocation modes:

� Supporting dynamic and static IP address allocation

PDSN supports MS to allocate IP address dynamically. Everytime users call, PDSN dynamically allocates a free IP addressfor the MS. This allocation mode is applicable for the conditionthat the number of current users is much larger than that ofIP addresses because only online users are allocated with IPaddresses.

In addition, PDSN supports allocating fixed IP addresses forMSs. In this case, PDSN supports AAA to specify an IP addressfor a MS in authorization attributes. If PDSN checks and de-termines that the IP address is valid, it allocates the addressto a user.

� Supporting AAA to specify IP address

PDSN supports allocating special IP addresses for usersthrough AAA authorizing special IP addresses from IP addresspool. And it can be set that users having no authority can notuse the IP address pool.

� Supporting IP address allocation based on privileges

In PDSN, users can be allocated with IP addresses of high-privilege IP address pool through configuring IP address poolprivileges.



Lawful Interception Function

Description Lawful interception function refers to real-time tracing and inter-ception performed on all calls and non-call activities of monitoredobjects, without influencing telecom-network equipment securityand services.

Interfaces Used The interfaces used between three interception standards Verint,CALEA, ETSI and the lawful interception center include:

� According to Verint standard, TCP mode communication is uti-lized for interfaces 1, 2, and 3 between the lawful interceptionserver and the lawful interception center.

� According to CALEA standard, TELNET mode communication isutilized for interface 1, and TCP communication mode is utilizedfor interfaces 2 and 3 between the lawful interception serverand the lawful interception center.

� According to ETSI standard, TELNET mode communication isutilized for interface 1, and FTP communication mode is utilizedfor interfaces 2 and 3 between the lawful interception serverand the lawful interception center.

Details The lawful interception interfaces between PDSN/AAA and LIC(Lawful Interception Center) comply with X1, X2, and X3 interfacespecifications. With these interfaces, monitoring and controllingset directed to monitored users is done. Besides, activity eventsof monitored users are reported and media stream the usersaccessed are copied and distributed.

� X1 interface is used to set monitored users and maintain X2and X3 interfaces. In addition, this interface receives com-mands from LIC or local to monitor and control users.

� X2 interface is used for LISto report activity events of users toLIC.

� X3 interface is used for LIS to report the copies of the packetsthe monitored users accessed to LIC, which in turn resolvesthe services the monitored users accessed and monitors theactivities of users.

QoS Guarantee Function

Description QoS (Quality of Service) is used to control the quality of transmis-sion.

PDSN adopts Diffserv QoS guarantee mode, which is used to con-trol the user IP message stream from PI interface and IP mes-sage stream of A10 carrier from RP interface. PDSN performsDSCP (Differentiated Services Code Point) of IP message steamand queuing and scheduling of messages based on DSCP value.

DiffServ is a multi-service model and meets different QoS require-ments. Different from IntServ, DiffServ does not need RSVP. Thatis to say, before application sending out messages, there is no needto inform routers to reserve resources. For DiffServ service mode,the network does not need to maintain the status of each stream.



It provides specified services according to QoS specified in eachmessage. Message QoS can be specified by IP precedence, sourceaddress, and destination address of messages. With this infor-mation, operations such as message classification, traffic shaping,traffic supervision, and queuing and scheduling are done.

Details The basic functions of QoS include:

� Data traffic QoS of network

� Handling network congestion, taking measures to processtraffic of congested network.

� Avoiding network congestion.

� Monitoring and shaping network traffic.

� End-to-End QoS of CDMA 2000 Wireless IP network

� Creating various data application services for users, andguaranteeing users to experience differentiated servicequalities of data service in wireless mobile environment.

� Providing service expanding ability with differentiated ser-vice qualities for wireless network carriers.

Supported PDSS ServicesPacket Prepayment Service

Description Packet prepayment refers to a packet data service with prepay-ment before consumption. It allows users to pre-purchase service(duration or traffic) of a certain sum of money.

Packet prepayment function performs real-time charge settlementfor mobile users’ packet data service. And it controls users’ dataservice based on users’ actual account amount, thus protectingcarriers’ profit.

Prepayment client requests available quote from prepaymentserver, and monitors the usage status of user quote to controlservices in real time. Prepayment server collects charge in realtime according to service usage.

Details ZXPDSS provides the following packet prepayment functions:

� Prepayment based on duration.

� Prepayment based on traffic.

� Rate changing based on duration or traffic.

� Supporting online quote update and quote authorization bysegment, precisely controlling user charge and providing uni-fied account.

� Supporting Disconnect dynamic authorization, connection canbe released actively at network side to call back the quote.



L2TP-based VPN Service

Description Data VPN service means providing packet data users with ability ofaccessing remote servers internal enterprises or fleets. The usedtechnologies include the access ability of the system, carrier abilityof packet network, IP tunnel technique, and IP security technique.Users access to these remote servers just like accessing to theservers of their own enterprises and fleets. They can use variousdata services provided by the remote servers, forming a data vir-tual special network of their enterprises and fleets. All data virtualnetworks share the network resources but are independent of eachother while working.

Details L2TP-based VPN access scheme is introduced as below:

� L2TP tunnel is a kind of two-level tunnel technique, utilizing IPnetwork to create L2TP tunnel. Data is encapsulated into PPPand transmitted through L2TP tunnel.

� PDSN performs LAC (L2TP Access Concentrator) function, cre-ating and maintaining L2TP session with LNS (L2TP NetworkServer) of enterprise networks, and forwarding PPP negotia-tion. LNS is the access server positioned internal enterprises.

� The ending points of PPP session are MS and LNS. PPP mes-sages are sent from MS to LAC, which sends the messages toLNS through L2TP tunnel.

Multi-VRF VPN Service

Description Through VRF (Virtual Routing Forwarding) mode, PDSN can con-nect with VPN network through directly utilizing route instead oftunnel encapsulating. In this case, PDSN searches and processesdata messages of various VPN users through combining specialVPN route forwarding table and 802.1Q VLAN protocol.

Details PDSN creates individual VPN route forwarding table for every kindof VPN users. Different kinds of users use their own route forward-ing tables. Thus PDSN is directly connected with VPN network andforwards data information between users’ terminals and VPN net-work.

After users accessing to PDSN, PDSN searches route for user datafrom the route forwarding table specified by VPN, and forwardsuser data through the specified sub-interface. The messageheader is marked with VLAN ID of the user data. After PDSNreceiving the user data messages with specified VLAN ID, itdetermines the VPN attributes of users according to VLAN ID, andthen forwards the messages to users.



Data Service Billing

Description Billing information parameters of packet data service can be di-vided into wireless parameters (collected by PCF) and IP networkparameters (collected by PDSN).

Billing Procedure PCF sends wireless parameters to PDSN through RP interface.PDSN collects parameters of users and forms the data into UDR(Usage Data Record), which is sent to AAA server through RADIUSmessages. PDSN generates one UDR for each IP address of eachMS.

AAA saves original UDR information in local disk according to RA-DIUS billing messages from PDSN. AAA provides FTP interface forbilling center, which in turn collects original UDR information fromAAA through FTP interface and forms final UDR.


C h a p t e r 6

System Features

Table of ContentsProcessing Capability of System ..........................................45General Features ...............................................................46Security Authentication Products Match ................................51

Processing Capability ofSystem

Definition Processing capability of ZXPDSS depends on the configuration ofPDSN and AAA.

The number of SMPs in PDSN and the performance of AAA serverjointly contribute to processing capability of ZXPDSS(including thetotal number of system subscriber and data traffic).

PerformanceIndex

When PDSN individually forms a switch and has typical configura-tion, the performance indexes are as shown in Table 12.

TABLE 12 PERFORMANCE INDEXES OF PDSN WITH TYPICAL CONFIGURATION


Number of activated (online) PPPconnections 5000 Typical

Configuration

Number of A10 supported 5000*7Ac-tive/standbyinterfaces

Maximum data throughput (1500bytes) 1.6 Gbps

Ac-tive/standbyinterfaces

Maximum data throughput (IMIXmodel) 1.6 Gbps -

Packet forwarding ability (64 bytes) 900Kpps -

Concurrent access ability 300/second -

Maximum number of connectablePCFs 512 -




Availability ≥99.999% -

Mean Time Between Failures (MTBF) ≥100,000hours

-

System Restoration Time ≤30 mins -

ImplementingMeasures

Each board of PDSN uses high performance network processor toenable wire speed data distributing (dedicated data forwarding en-gine), the data cache is up to 2G. Dedicated high-performancecommunication RISC processor is used. The hardware supports tosearch and forward data in high speed.

General FeaturesNetworking Feature

Definition Networking feature of the system describes whether the network-ing structure adopted in the system fulfills the requirements fornetwork security and stability.

ZXPDSS system has dual networks and dual planes to ensure thesystem security and reliability.


ZXPDSS system has dual networks and dual planes, includingPDSN, HA (optional), AAA, OMC. LIS, All of these are put in thesame local area network, and connected through two Ethernetswitches (one is active and the other is standby). In principle,two firewalls should be configured, one is active and the otheris standby, which is implemented by HA. Use routers instead iffirewalls are unavailable. Routers are located in the positionswhere the firewalls should have been. HSRP is used betweentwo routers to make one active and the other standby. Firewallsor routers should be configured to have at least 3 ports, one ofwhich is used for accounting system.

ComparativeAdvantages

Comparative advantages of the networking features are listed inTable 13.

TABLE 13 COMPARATIVE ADVANTAGES

Measures Advantage if adopted Risks if notadopted

Two switchesare used toform the localarea network

Two switches backup mutually toavoid absolute failure of whole LANdue to failure of one switch.

Switch failurecausesabsolutefailure of wholeLAN.


Chapter 6 System Features

Measures Advantage if adopted Risks if notadopted

PDSN/AAA/OMCare intercon-nected withtwo switches

To avoid service interruption due tonetwork cable failure.

Easy to causesingle-pointfailure.

Two firewallsare used

Two firewalls backup mutually toavoid interruption of communicationwith DBIO and billing center due tofailure of one firewall.

Easy to causesingle-pointfailure.

Interconnection Feature

Definition Interconnection feature of the system refers to whether the sys-tem utilizes standard protocol interfaces, and whether the systemhas desired interconnection ability to be interconnected with othermanufacturers’ devices.

ZXPDSS provides open interface which is based on3GPP2.P.S001-A and RFC. It follows the CDMA technical specifi-cations and relevant standards issued by Ministry of InformationIndustry, and can be interconnected with the products that meetthe standard.


Interfaces between PDSN and PCF comply with the standard RP in-terface specifications, that is, A10/A11 specified by A.S0001 Spec-ifications.

Interfaces between ZXPDSS and accounting system of carriers arebased on the standard TCP/IP protocol, easy to be interconnectedwith the accounting system.

Interfaces between ZXPDSS and billing system of carriers arebased on the standard FTP protocol. UDR can be directly sent tothe billing center.

Convenience in Operation

Definition For convenience in daily maintenance of subscribers, the systemshould have friendly man-machine interfaces for convenient oper-ation and management.

OMCs of PDSN and AAA are based on the unified network manage-ment platform, and utilize the operating system Windows 2000 orWindows 2003 and database SQL Server 2000 or SQL Server 2005.These operating systems and database systems are universal andcommonly used, so it is convenient for subscribers to operate.

OMC has graphic management interfaces to manage the networkelements inside the system more intuitively.


OMC performs operation and maintenance functions for the sys-tem and unified management for the network. Through the in-terfaces and platform provided by OMC subsystem, the operationand maintenance personnel can perform configuring, analyzing,



accounting, diagnostic testing for the devices present in the net-work, and acquire such data as the alarm and statistic informationof the devices.

Operation and maintenance system includes foreground and back-ground. Communication between these two parts is implementedthrough TCP (UDP)/IP/Ethernet carrier; Ethernet port is located onOMP and other MPs.

The operation and maintenance subsystem includes the followingfunctional modules:

� Alarm management module

Alarm management module is used to receive the detailedalarm information sent by each network element in the form offailure report. Alarm management also monitors the networkstatus to find the abnormal network state, and convert the in-formation into the forms of sound, light, and screen display todraw attention of operators.

� Configuration management module

Configuration management module manages all configurationdata of current system.

� Performance management module

Performance management module enables the performancemeasurement function of the system, collects and processesmeasurement data, and takes effective measures to guaran-tee the high performance of the system.

� Security management module

Security management module is used to avoid important databeing modified or damaged consciously or unconsciously bythe unauthorized personnel through background. It limits theoperation authorities of the operation personnel of differentlevels. Based on this, it is integrated with the system operatingauthority management to construct the security policy for thewhole operation and maintenance system.

� Diagnostic test module

Diagnostic test module is used when there are alarms or thesystem performance is degraded. The operation personnelstart the relevant testing programs to diagnose and find thefailure, in order to do maintenance operation and minimize theimpact of failures on the network.

� System tool module

System tool module supports and completes the system man-agement, including tools such as service observation, signalingtracing, version management, files management, timer andprinting management.

Modulization

Definition For the purpose of easy capacity expansion and daily maintenance,it is generally desired that the system may be divided into a num-



ber of functional modules, each module independent from eachother.

Description ZXPDSS is composed of PDSN, HA, LIS, AAA, and AN-AAA, andrelevant alarm box. It has flexible construction and is easy to beextended and upgraded, in other words, it has desirable compli-ance and expansibility.

� PDSN

Hardware system of PDSN is based on hardware system of ZTEV3 platform, with the software and hardware being modulatedfor easiness in expansion.

� HA

HA hardware is based on ZTE V3 platform hardware system,implementing mobile IP function.

� AAA

Hardware system of AAA is a host system with two universalservers plus disk array, with flexibility in expansion and ap-plication. Subscribers may conduct configuration flexibly andexpansion smoothly according to the actual applications. Thusprovide the resolution with highest performance-price ratio.

� LIS

Lawful interception server is used to interact with lawful inter-ception center, implementing adaption of various lawful inter-ception standards, encapsulating these standards into internalinterfaces and customized interfaces for foreground intercep-tion devices, and cooperating to implement lawful interceptionfunction. LIS flexibly supports various lawful interception stan-dards.

� AN-AAA

AN-AAA may utilize the devices similar to those in AAA system,and it can be integrated with AAA.

� Alarm Box

Alarm box utilizes alarm box module generally used in ZTE,and multiple alarm boxes can be added to the system.

Reliability

Description Reliability of the system refers to the availability of the system.It is related with the Mean Time Between Failures (MTBF) and theMean Time To Repair (MTTR) of the system. The index correspond-ing to reliability is defined as a percentage.

Reliability=MTBF / (MTBF+MTTR)*100%

If MTBF of ZXPDSS is above 100,000 hours, and MTTR is less than30 seconds, the reliability exceeds 99.999%.

Measure In ZXPDSS, reliability of the system is increased through utilizingthe following techniques.

� Key parts work in active/standby hot backup mode or loadsharing mode



� Key parts such as main processor and the switch plane workin active/standby hot backup mode. Handover automati-cally takes place when failures occur to guarantee uninter-rupted operation of the system.

� Database is structured to have cluster dual computers andhas magnetic disk array.

� Dual computers and dual buses are used for controlling.Network is structured in dual networks mode to improvesystem reliability.

� Security measures are taken to limit the control in differentlevels.

� Two AAA servers are used, with one is activated and theother standby.

� Communication link is structured to have dual networks toguarantee unblocked network.

� Highly reliable database with high performance

� AAA database utilizes advanced cluster technology and diskarray technology. It supports high-speed accessing to thedatabase with large capacity.

� The software platform of OMC server uses Windows oper-ating system. Combining with the management functionof commercial database SQL Server, it can guarantee thesecurity and reliability in real-time data accessing.

� Powerful failure positioning ability

The system provides another powerful failure positioning andsignaling tracing system to locate failures of boards and evensome slots.

ComparativeAdvantages

Comparative advantages of the system in reliability are listed inTable 14.

TABLE 14 COMPARATIVE ADVANTAGES IN RELIABILITY

Measure Advantages If Adopted Risk If NotAdopted

Double (Acti-vated/Standby)Servers andWarm Backup

Automatically hand over whenfailure occurs, the system operationis uninterrupted.

Morefrequentsingle-pointFailure.

Dual clustercomputers/ diskarray

Data is less lost, and moreconvenient to expand the capability.

Failureof singlemachineleads to theinterruptionof allservices.

HierarchicalControl inAuthorities

Security guaranteeing systemwithout being invaded by others.

Poor Securityof Network.



Measure Advantages If Adopted Risk If NotAdopted

Dual Com-puters/Buses/net-works

Reliability of the system is improved.

Morefrequentsingle-pointFailure.

Sharing LoadAutomatically hand over whenfailures occur, the system operationis uninterrupted.

Serviceis morefrequentlyinterrupted.

Dual computersand dual planes Unblocked Communication. Poor Stability

of Network.

Security AuthenticationProducts Match

StandardsSupported

ZXPDSS provides open interfaces based on 3GPP2.P.S001-A andRFC. The protocols and standards supported include:

� 3GPP2 A.S0001-A 3GPP2 Access Network Interfaces Interop-erability Specification, November 2000

� 3GPP2 P.R0001 Version 1.0.0 Wireless IP Architecture Basedon IETF Protocols, July 2000

� 3GPP2 P.S0001-A Version 3.0 Wireless IP Network Standard,July 2001

� 3GPP2 P.S0001-B Version 2.0 Wireless IP Network Standard,September 2004

� 3GPP2 X.S0011-002-C Version: 1.0.0,CDMA2000 Wireless IPNetwork Standard: Simple IP and Mobile IP Access Services,August 2003

� 3GPP2 X.S0011-003-C Version: 1.0.0, cdma2000 Wireless IPNetwork Standard: Packet Data Mobility and Resource Man-agement, August 2003

� 3GPP2 X.S0011-004-C Version: 1.0.0,cdma2000 Wireless IPNetwork Standard: Quality of Service and Header Reduction,August 200

� 3GPP2 X.S0011-005-C Version: 1.0.0,cdma2000 Wireless IPNetwork Standard: Accounting Services and 3GPP2 RADIUSVSAs, August 2003

� 3GPP2 X.S0011-006-C Version: 1.0.0,cdma2000 Wireless IPNetwork Standard: Pre-Paid Packet Data Service, August 2003

� 3GPP2 X.S0011-001-D Version: 1.0.0, CDMA2000 Wireless IPNetwork Standard: Introduction, February 2006

� 3GPP2 X.S0011-002-D Version: 1.0.0,CDMA2000 Wireless IPNetwork Standard: Simple IP and Mobile IP Access Services,February 2006



� 3GPP2 X.S0011-003-D Version: 1.0.0,CDMA2000 Wireless IPNetwork Standard: Packet Data Mobility and Resource Man-agement, February 2006

� 3GPP2 X.S0011-004-D Version: 1.0.0,CDMA2000 Wireless IPNetwork Standard: Quality of Service and Header Reduction,February 2006

� 3GPP2 X.S0011-005-D Version: 1.0.0,CDMA2000 Wireless IPNetwork Standard: Accounting Services and 3GPP2 RADIUSVSAs, February 2006

� 3GPP2 X.S0011-006-D Version: 1.0.0,CDMA2000 WirelessIP Network Standard: PrePaid Packet Data Service, February2006

� 3GPP2 A.S0008-0 v3.0, Interoperation Specification (IOS) forHigh Rate Packet Data 74(HRPD) Access Network Interfaces,May 2003

� 3GPP2 A.S0008-A V1.0 Interoperability Specification (IOS) forHigh Rate Packet Data (HRPD) Radio Access Network Interfaceswith Session Control in the Access Network, March 2006

� 3GPP2 A.S0008-B V1.0 Interoperability Specification (IOS) forHigh Rate Packet Data (HRPD) Radio Access Network Interfaceswith Session Control in the Access Network, October 2006

� 3GPP2 A.S0011-17-C v1.0, Interoperability Specification (IOS)for cdma2000 Access Network Interfaces, March 2005

� 3GPP2 S.R0104-0 Version 1.0,HRPD Network Access Authenti-cation for a Hybrid Access Terminal (HAT) with an R-UIM Usedto Access Spread Spectrum Systems--System Requirements,October 2004

� 3GPP2: X.S0022-0 ver. 1.0, Broadcast and Multicast Servicein cdma2000 wireless IP network, Revision A, February 2004

� 3GPP2: A.S0019-0, Interoperability Specification (IOS) forBroadcast Multicast Services (BCMCS), November 2004

� RFC 768 User Datagram Protocol, August 1980

� RFC 791 Internet Protocol, September 1981

� RFC 792 Internet Control Message Protocol, September 1981

� RFC 793 Transmission Control Protocol, September 1981

� RFC 826 An Ethernet Address Resolution Protocol, November1982

� RFC 854 Telnet Protocol Specification, May 1983

� RFC 1122 Requirements for Internet Hosts -CommunicationLayers, October 1989

� RFC 1144 Compressing TCP/IP Headers for Low Speed SerialLinks, February 1990

� RFC 1321 The MD5 Message-Digest Algorithm, April 1992

� RFC 1332 The PPP Internet Protocol Control Protocol(IPCP),May 1992

� RFC 1334 PAP Authentication Protocols

� RFC 1661 The Point-to-Point Protocol (PPP),July 1994



� RFC 1662 PPP in HDLC-like Framing, July 1994

� RFC 1701 Generic Routing Encapsulation (GRE),October 1994

� RFC 1702 Generic Routing Encapsulation over Ipv4 networks,October 1994

� RFC 1918 Address Allocation for Private Internets, February1996

� RFC 1962 The PPP Compression Control Protocol (CCP),June1996

� RFC 1974 PPP Stac LZS Compression Protocol, August 1996

� RFC 1979 PPP Deflate Protocol, August 1996

� RFC 1994 PPP Challenge Handshake Authentication Protocol(CHAP),August 1996

� RFC 2002 IP Mobility Support, October 1996

� RFC 2003 IP Encapsulation within IP, October 1996

� RFC 2004 Minimal Encapsulation within IP, October 1996

� RFC 2005 Applicability Statement for IP Mobility support, Oc-tober 1996

� RFC 2006 The Definitions of Managed Objects for IP MobilitySupport Using SMIv2,October 1996

� RFC 2118 Microsoft Point-To-Point Compression (MPPC) Proto-col, March 1997

� RFC 2136 Dynamic Updates in the Domain Name System (DNSUPDATE), April 1997

� RFC 2474 Definition of the Differentiated Services Field (DSField) in the IPv4 and IPv6 Headers, December 1998

� RFC 2284 PPP Extensible Authentication Protocols(EAP),March1998

� RFC 2475 An Architecture for Differentiated Services, Decem-ber 1998

� RFC 2486 The Network Access Identifier, January 1999

� RFC 2597 Assured Forwarding PHB Group, June 1999

� RFC 2598 An Expedited Forwarding PHB, June 1999

� RFC 2661 Layer Two Tunneling Protocol "L2TP",August 1999

� RFC 2784 Generic Routing Encapsulation (GRE), March 2000

� RFC 2794 Mobile NAI Extension, March 2000

� RFC 2865 Remote Authentication Dial In User Service (RA-DIUS),June 2000

� RFC 2866 RADIUS Accounting, June 2000

� RFC 2868 RADIUS Attributes for Tunnel Support, June 2000

� RFC 2869 RADIUS Extensions, June 2000

� RFC 3012 Mobile IPv4 Challenge/Response Extensions,November 2000

� RFC 3024 Reverse Tunneling for Mobile IP, January 2001

� RFC 3543 Registration Revocation in Mobile IPv4, July 2003



� RFC 3576, Dynamic Authorization Extensions to Remote Au-thentication Dial In User Service (RADIUS),July 2003

� ITU-T Recommendation E.212 The International IdentificationPlan for Mobile Terminals and Mobile Users

� IEEE Std 802.11 Wireless LAN Medium Access Con-trol(MAC)and Physical Layer (PHY) Specifications

� IEEE Std 802.1x-2001 IEEE Standard for Local and Metropoli-tan Area Networks-Port-Based Network Access Control

� IEEE Std 802.11b Higher Speed Physical Layer Extension in the2.4GHz Band

� ANSI-41-D, Cellular Radio Telecommunications IntersystemOperations, Dec 1999

� ZXPDSS acquires the following certificates:

� ZXPDSS P200 IC (ICES-003 CONFORMANCE VERIFICATION)

� ZXPDSS P200 FCC (VERIFICATION OF CONFORMITY)


C h a p t e r 7

Mechanical Features

Table of ContentsMechanical Features of PDSN Cabinet...................................55Mechanical Features of Server Cabinet .................................58Mechanical Features of Alarm Box........................................59

Mechanical Features ofPDSN Cabinet

Description PDSN cabinet is standard 19"cabinet. Number of plug-in shelvescan be installed within the cabinet as listed below:

� Service shelf

Service shelf is installed with boards, and it performs functionsof PDSN.

� Fan shelf

Fan shelf is installed with fan modules to provide the functionof cooling the entire cabinet.

� Power shelf

Power shelf is used to install the power board to provide stablepower supply for other shelves.

� Cable shelf

Cable shelf provides cable trough.



Appearance ofCabinet

PDSN cabinet appearance is as shown in Figure 17.

FIGURE 17 APPEARANCE OF PDSN CABINET

Cabinet Structure The structure of PDSN cabinet is as shown in Figure 18.


Chapter 7 Mechanical Features

FIGURE 18 PDSN CABINET STRUCTURE

1. Blank Panel (1U)2. Power shelf (2U)3. Fan shelf (1U)4. Service shelf (8U)5. Cable shelf (1U)6. Service shelf (8U)7. Cable shelf (1U)

8. Fan shelf (1U)9. Service shelf (8U)10. Cable shelf (1U)11. Service shelf (8U)12. Cable shelf (1U)13. Fan shelf (1U)14. Dust screen

Size Overall size of PDSN cabinet is 2000mm×600mm×800mm(Height*Width*Depth).



Weight Maximum weight of PDSN cabinet is about 350 kg.

Mechanical Features ofServer Cabinet

Description General PC server (suitable to be installed on cabinets), magneticdisk array, HUB and routers are installed within server cabinets.

Appearance View The structure of a server cabinet is as shown in Figure 19, the leftside is the front view, and the right side is the side view.

FIGURE 19 STRUCTURE OF SERVER CABINET


Chapter 7 Mechanical Features

Size The server cabinet is standard 19" rack. Net height inside is 42U(1U=44.45 mm) and overall size is 2000 mm×600 mm×1000 mm(cover should be added when cabling on top).

Weight With all boards for ZXPDSS inserted, the maximum weight of aserver cabinet is 350 kg.

Note:

AAA server uses the servers manufactured by the third-party man-ufacturer. The server cabinets manufactured by the third-partymanufacturer are also used on site. For specific mechanical fea-tures, refer to the document of the third-party manufacturer.

Mechanical Features ofAlarm Box

Description Alarm box is generally installed on the walls of maintenance ormonitoring room for the on-duty staff to view and operate. It isconnected with the background operation and maintenance sys-tem through Ethernet.

Appearance View Alarm box appearance is shown in Figure 20.

FIGURE 20 APPEARANCE VIEW OF ALARM BOX

Size The overall size of the alarm box is 210 mm×30 mm×52 mm(Height*Width*Depth).

Weight The alarm box has a weight of 2 kg.


C h a p t e r 8

Electrical Features

Table of ContentsElectrical Features of PDSN Cabinet......................................61Electrical Features of Server Cabinet ....................................61Electrical Features of Alarm Box ..........................................62

Electrical Features of PDSNCabinet

Overview In order to guarantee the security and stability of PDSN cabinet,DC power is supplied for each PDSN cabinet in two circuits respec-tively from different DC power distributing cabinets.

Power SupplyTypes

PDSN cabinet uses -48 V DC power supply.

Input Voltage The rated voltage of the DC power used in PDSN cabinet is -48 V.

The input voltage of the DC power is within -57 V~ -40 V.

Power of PDSNCabinet

With typical configuration, the power of PDSN is:

� 1250 W with single shelf forming a switch

� 1950 W with dual shelves forming a switch

Electrical Features of ServerCabinet

Description In order to improve the reliability, AC power is supplied for eachserver cabinet in two circuits respectively from one phase of differ-ent three-phase powers in AC power distributing cabinets. The twoinput power supplies of one server cabinet can not be of the samephase. When a number of cabinets are connected, power supplyof each phase should be equally distributed to acquire proximatelybalanced power.

Input VoltageTypes

Server cabinet uses 220 V AC power supply

Input Voltage The input voltage used in server cabinet is 200 V240 V.



Other Require-ments

Input power of server cabinet has a frequency of 50 Hz ±5% .

Electrical Features of AlarmBox

Description Alarm box is supplied with direct current power and the power ca-ble is directly connected to the direct current distributing cabinet.

Input Power Type The alarm box uses DC power supply of -48 V.

Input Voltage The input voltage in the alarm box is in the range of -57 V~ -40 V.

Power of AlarmBox

The power of an alarm box is 20 W.


C h a p t e r 9

EnvironmentRequirements

Table of ContentsRequirements for Ground....................................................63Requirements for Temperature and Humidity.........................64Requirements for Anti-Interference from Electromagnetic Ra-diation .............................................................................65Requirements for Ventilation ...............................................66Requirements for Fire-Fighting ............................................67Requirements for Lighting...................................................67Requirements for Anti-Electrostatic ......................................68Requirements for Anti-lightning ...........................................70Requirements for Neatness .................................................72Requirements for Earthquake Resistance Capability................74

Requirements for GroundDescription To guarantee long-time security, stability and reliability of the sys-

tem, decrease the failure rate of devices caused by environmentalfactors, and prolong the lifetime of devices, the grounding condi-tion of the devices should meet correspondent requirements.

Significance Grounding plays an important role in guaranteeing a good electro-magnetic condition and anti-interference ability of the operatingenvironment of the principal and auxiliary equipment in the sys-tem, which requires high attention.

Required Index Grounding resistance must be less than 1 Ω, thus various factorsthat affect the grounding resistance shall be taken into account,such as the soil condition, resistances of grounding devices andgrounding cables.

� Soil type influences the grounding resistance. For areas withpoor soil conditions, auxiliary chemical agents (such as prope-namide) may be used around the grounding post to reduce thesoil resistance and the contact resistance between the soil andthe grounding post.

Temperature and humidity also affects the grounding resis-tance. When the temperature is lower than 0℃ or the humidityis too low, the grounding resistance varies greatly. Hence, thegrounding post may be buried deeply and the chemical auxil-iaries may be added to meet the requirements for groundingresistance.



� Connecting cables between the grounding post and the ground-ing bolt on principal equipment of the system should be madeof copper core, with a large-enough cross section area gener-ally no less than 50 mm2. These cables must be as short aspossible. The cross section area of the copper wire should befurther enlarged when the length exceeds 50 m.

Both ends of the connection wire should experience tinning orthermal tin dipping processing, and the coating, varnish, paintand oxidized layer should be removed from the fastening pointsto guarantee good contact between the two metal surfaces.

The grounding posts should be angle irons not less than 2 m inlength, and the ground grid is preferred if conditions permit.

� Before commissioning, carriers should measure the accurateground resistance and provide data for the engineers of ZTE.If the grounding resistance does not meet the requirement,no commissioning can get started until accepted by relevantdepartments of ZTE.

Requirements forTemperature and Humidity

Description To guarantee long-time security, stability and reliability of the sys-tem, decrease the failure rate of devices caused by environmentalfactor, and prolong the lifetime of devices, the temperature andhumidity should meet the requirements of ZXPDSS.

Significance If the temperature and humidity within the equipment room is toohigh or too low, the lifetime of the devices may be shortened.

Required Index In order to ensure that the environmental condition of the de-vices meets the recommended requirement, air-conditioner andventilation equipment must be installed. Generally, yearly-oper-ated air-conditioner should be arranged in main equipment room,and seasonal air-conditioner in auxiliary equipment room accord-ing to actual conditions (climate and economic conditions of thesubscribers) must be installed.

The basic requirements for air-conditioners are as followed:

� Humidity Scope: 20%~90%

� Temperature Scope: 0℃~40℃Reference The capacity of the ventilation system of the air-conditioner is de-

termined through calculating the heating quantity of the main de-vices in the system, plus the heat from the exterior heat resources(e.g. heat from the sunlight into the equipment room through win-dows and walls, heat from the maintenance personnel and the heatbrought in by the maintenance personnel from outside).

For the purpose of security and reliability in the air-conditioner andventilation system, double sets of air-conditioners are required,especially in the main equipment room. The capacity of the eachset should be at least more than half of the required total capacityfor the air-conditioner.


Chapter 9 Environment Requirements

Sealing condition of the equipment room should not be damagedwhile installing the air-conditioner. In addition, the ratio of freshair into the equipment room should be no less than 5%, to guar-antee comparatively fresh air.

Since the hot air flow is generally upward moving, cooling pro-vided for the main equipment of the system adopts the mode ofexhausting air upward. Therefore, when central air-conditioningsystem is installed, the ventilation mode may be selected to sup-ply air upward and return air downward. The air intake is arrangedunder movable floor for easy cooling of machines. Generally, airsupply pipe is not installed on the top, to ensure that no conden-sation occurs at any condition.

Typically, air-conditioners with function of regulating humidityshould be installed in large equipment room, while commoncabinet or window air conditioner will do in small equipment room.

Negative ImpactIf Requirements

Are Not Met

There would be negative impact on the system if the system re-quirements mentioned above are not met. For example, if thetemperature is 10℃ above the normal temperature, the lifetime ofthe equipment is reduced by half or so; if the temperature is toolow, the performance of the optical devices, crystals can not beguaranteed; if the relative humidity is too high for a long time, theinsulating performance of some insulating materials may degrade,and even leakage may occur, besides, various metal parts may getrusted; if the relative humidity is too low for a long time, the in-sulating gasket may shrink and cause the fastening bolts less fas-tened, and it may probably lead to strong electrostatic discharge,that may cause damage to the CMOS circuit of the equipment.

Requirements forAnti-Interference fromElectromagnetic Radiation

Description To guarantee long-time security, stability and reliability of the sys-tem, decrease the failure rate of devices caused by environmen-tal factor, and prolong the lifetime of the devices, the require-ments of ZXPDSS for anti-interference from electromagnetic radi-ation should be met.

Significance Anti-interference from electromagnetic radiation plays an impor-tant role in operation of the communication devices, and it affectsthe stability, reliability and security of the devices.

Required Index Basic requirements are as follows:

� The electric-field intensity and magnetic-field intensity in theequipment room should meet the following indices:

� Electric-field Intensity ≤ 130d B (μV/m)

� Magnetic-field intensity ≤ 800 A/m

� Proper shielding and protection measures should be taken inthe equipment room to reduce the interference of equipment



room from the outside electromagnetic environment and theinterference between the devices in the equipment room.

The equipment room should be positioned far away from radiostations, radar stations with great power and devices with highfrequency and super current. The actual radiation energy ex-perienced by the equipment room should be controlled below300 mV/m, and the magnetic-field intensity around the equip-ment room should be less than 11 Gs.


are not met

Negative impact on the system if the requirements mentionedabove are not met shows as follows:

� Electromagnetic interference occurs

The interference resources causing electromagnetic interfer-ence include corona discharge in power transmission line, elec-tromagnetic radiation in transformer, electromagnetic radiationof switch equipment, wave form distortion caused by opera-tions on huge equipment in power net, space radio frequency,magnetic field of the earth, external radiation, etc.

These interferences affect the communication devices in suchtransmitting mode as capacitance coupling, inductance cou-pling, electromagnetic wave radiation, common impedance (in-cluding grounding system) and wires (power cord, signal wireand supply wire).

� Damage of electromagnetic interference on communication de-vices

When electromagnetic interference reaches to an extent, fail-ures may frequently occur, such as communication crosstalk,block, error code, interruption, etc. That may even lead to thesoftware confusion when it is more serious, and the equipmentmay be damaged.

Requirements for VentilationDescription In order to guarantee long-time security, stability and reliability of

the system, decrease the failure rate of devices caused by envi-ronment factor, and prolong the lifetime of the devices, ventilationequipment should meet correspondent requirements of the sys-tem.

Significance Ventilation plays an important role in operation of the communi-cation devices, and it directly affects the stability, reliability andsecurity of the devices.

Required Index Basic requirements for the air-conditioning devices are as follows:

� Humidity Scope: 20%~90%

� Temperature Scope: 0℃~40℃To guarantee the security and reliability in operating the ventilationsystem in the air-conditioner, double sets of air-conditioners arerequired. The capacity of the each set should be at least morethan half of the required total capacity for the air-conditioner.

Sealing condition of the equipment room should not be damagedwhile installing the air-conditioner. In addition, the ratio of fresh



air into the equipment room should be not less than 5 % to theguarantee comparatively fresh air.


are not met

Shutting down the air-conditioner may cause sudden raise of tem-perature in equipment room, which may destroy the boards.

Requirements forFire-Fighting

Description In order to guarantee the security, stability, and reliability duringthe system runs, decrease the failure rate of equipment resultingfrom environmental factors, and prolong the lifetime of the equip-ment, fire-fighting devices should meet the requirements of thesystem.

Significance In order to guarantee the security o the equipment in equipmentroom, corresponding fire requirement must be met.

Required Index The main building in which the equipment room is located mustmeet the relevant requirement of Code for Design of Building FireProtection. There must be relevant fire protection and fire channelaccording to the local fire fighting regulations. Put the sign panelwith written words Key Unit of Fire Security in proper position.

Inflammable or explosive hazardous materials are not allowed inthe equipment rooms and No smoking sign board must be putup in obvious position. Available fire protection must be equip-ment must be placed in easily accessible positions in case of anemergency, Fire fighting water tank must be and the installed inproper positions. The quantity of stored water must be no lessthan 2 hours fire fighting time. The water supply pipe (includingdrainage pipe and rain water pipe) must not traverse the equip-ment room, and the fire hydrant should not be arranged in theequipment rooms.

Alarm devices for smoke, high temperature should be installed,and examined frequently to ensure optimum performance.


are not met

The whole equipment room may be completely damaged in caseof fire occurring. The result is unpredictable.

Requirements for LightingDescription To guarantee long-time security, stability and reliability of the sys-

tem, decrease the failure rate of devices caused by environmentalfactorso, and prolong the lifetime of the devices, lighting devicesshould meet the requirements of the system.

Significance Lighting in equipment room is very important. The maintenancepersonnel can perform operation activities using lightning in theequipment room when the sunlight is less strong or is unavailable.



Required Index It is suggested that tinted glasses and dark opaque curtain areselected. Fluorescent lamps may be utilized in the main part of theequipment room, inserted into the ceiling. The mean illuminationis 150 lx~200 lx.

Luminous light or emergency lighting should be installed in properpositions between cabinets to illuminate while installing and main-taining.


are not met

Avoid long-time illumination of light and sunlight on the equip-ment, to prevent aging and deformation of the circuit boards andelements and devices due to extremely high temperature.

Requirements forAnti-Electrostatic

Description To guarantee long-time security, stability and reliability of the sys-tem, decrease the failure rate of devices caused by environmentalfactors, and prolong the lifetime of the devices, anti-electrostaticrequirements should be met.

Significance Anti-electrostatic requirement is quite important for communica-tion devices. It directly influences the stability, reliability and se-curity of the equipment.

Required Index The following measures should be taken to prevent or reduce thestatic charge generated in the equipment room.

� Equipment should be grounded reliably (ground resistance isless than 1 ohm) to eliminate static charge in time and avoidaccumulation of static charge. Meanwhile, anti-electrostaticfloor or similarities should be arranged in the equipment roomas an auxiliary measure.

� Enhance the dust prevention measure to prevent or reduceelectrostatic absorption.

� Keep the temperature and humidity in the equipment roomaccording to the conditions described above.

� Do not use insulating floor wax on the antistatic floor.

� Clear off the insulating oil coat, resin and rubber adhered tothe anti-electrostatic table pad, floor and blanket. Use neutraldetergent or antistatic agent to clean the floor pad.

� Antistatic devices, tools and electrostatic sensitive materialsshould have obvious antistatic signs; there should be obviousgrounding sign description on the antistatic ground system.

� The maintenance personnel should comply with the relative an-tistatic regulations while operating the equipment, for exam-ple, wearing the antistatic clothes, and using antistatic com-puter cover.

� To completely control the electrostatic current from humanbody, the chair on which the operators are seated must haveantistatic property and do not use the chairs with the surfacemade of common artificial leather, and chemical fiber fabric or



plastics, and do not use wooden chairs instead of antistaticchair.


are not met

It is obvious that electrostatic discharge damages the equipment.The instantaneous value of the electrostatic voltage is usually upto thousands or ten thousands volts, and when it touches withelectron devices (e.g. large scale of integrated circuit) sensitive toelectrostatic made by CMOS process and discharges, these devicesare generally damaged irreversibly. It is dangerous to the securityof the equipment.

According to the statistics, 60% of the damaged plug-in boardswere due to electrostatic. Besides, electrostatic may cause soft-ware fault, and leads to the malfunctions of electron switches.

Reference For details of electrostatic voltage from human body, refer to Table15.

TABLE 15 ELECTROSTATIC VOLTAGE ON HUMAN BODY

Condition Generated Voltage Range (V)

People walking on insulating blanket 12000 ~ 39000

People walking on insulating Floor 4000 ~ 13000

People sitting on chairs 500 ~ 3000

Table 15 lists the rising tendencies of voltage on human body within40 sec. in three circumstances, the voltage scope beyond 12 kVis considered dangerous.

Insulating materials can accumulate static, while conducting ma-terials can not. Insulating materials include plastic floor, blanketmade of nylon and chemical fiber fabrics, leather shoes, plasticshoes, service coat made of chemical fiber fabrics and low humid-ity environment (or dry environment). While the environment withmore than 60% of humidity, floor made of semiconductor materi-als and cement floor are all desirable antistatic environments.

Table 16 lists the sensitivities of different elements or devices toelectrostatic damage:

TABLE 16 SENSITIVITIES OF DIFFERENT ELEMENTS OR DEVICES TOELECTROSTATIC DAMAGE

Elements or Devices Destructive Voltage (V)

MOS (Integrated Circuit) 100 ~ 200

CMOS (Integrated Circuit) 250 ~ 2000

TTL Circuit 300 ~ 1500

Field Effect Transistor 380 ~ 7900

Mixed with Printed Circuit Board 500

Silicon Controlled (SCR) 680 ~ 1000



From Table 15 and Table 16, it is clear that electrostatic is fatalto the devices. If walking in a room without antistatic measure,electrostatic of 12 kV may be caused. If one touches the devicesimmediately in this case, it may be dangerous to the devices.

Requirements forAnti-lightning

Description To guarantee long-time security, stability and reliability of the sys-tem, decrease the failure rate of devices caused by environmentalfactors , and prolong the lifetime of the devices, anti-lightning re-quirements should be met.

Significance Desirable anti-lightning ground is one of key technologies to makethe communication devices stable and reliable. It plays an impor-tant role in safeguarding personal security, preventing electrostaticinterference, electromagnetic interference, lightning interference.

Required Index The requirement of ZXPDSS for the anti-lightning ground is listedin Table 17.

TABLE 17 REQUIREMENT FOR ANTI-LIGHTNING GROUND

Item Requirement Detail

Requirement forinfrastructure constructionof equipment room

Equipment room is better built in steelconcrete structure; the building shouldbe installed with lightning protectiondevices (e.g. lightning arrester); theanti-lightning ground of the buildingshould share a group of grounding bodieswith the protection ground of the room.

Special power transformer should bearranged in communication office orstation, the power cable is led intothe communication office or station byleading the cable with metal shield orinsulating shield through steel pipes,which are buried into the soil. Both endsof the metal shield of the power cableor the steel pipes should be reliablygrounded to its nearest, the length of theburied part should be at least 15 m.

AC supply system shoulduse TN-S power supplysystem

Add seamless zinc oxide lightningarrester to three phase lines on the lowvoltage end of the AC power transformerin the office or station. The shell of thetransformer, the zero line at the lowvoltage end and the metal over sheath ofthe power cable connected with the shellof the transformer should be connectedto a local earth ground.




Do not lead aerial alternating or directcurrent power cord into or out of theoffice (station).

After leading the power cable of lowvoltage into the equipment room,lightning protection unit should be addedto the power cable in the AC voltageregulator and AC power distribution unit.

In cities, it is suggested to add lightningprotect unit with at least 20 kA ofnominal discharge current. In suburbslying in middle thunderstorm region, itis suggested to add lightning protectunit with more than 60 kA of dischargecurrent capacity. In mountain areas, itis suggested to add lightning protectunit with more than 100 kA of dischargecurrent capacity to the areas withinheavy thunderstorm region and theisolated tall buildings in cities.

Add lightning arrester toincoming power cable

The grounding cable of the lightningprotect unit should have a length of lessthan 1 m.

DC working grounding (-48 V for anode,24 V for cathode with DC) in the officeor station should be connected to localground in the indoor ground bondingwire, and the grounding cable shouldmeet the largest load requirement of thedevices.Ground for DC Power

DistributionThe power supply equipment supplyingpower for communication office or stationshould have DC working grounding cableled from the grounding bonding wire (orfrom the protection grounding bar in theequipment room)to the power supply.

Protective measure should be taken tovarious communication equipment andcorollary equipment (mobile base station,racks for transmission, switching, powersupply and distributing) in the equipmentroom. The protective ground for all kindsof equipment in the office or stationshould be bonded to one groundingbar, and the protective ground of theequipment in one equipment room shouldbe bonded to the protective groundingbar of the same one equipment room.

The working grounding, protectivegrounding of the communicationequipment in equipment rooms shouldbe grounded in a combined way, that isto say, working grounding and protectivegrounding should share a group ofground net.

Equipotent Connection




Protective ground should be taken tocable rack, suspension rack, rack orchassis, metal ventilation pipes, metaldoors and windows, etc.

The common wire of AC power cordis forbidden to be connected to theprotective grounding of all kinds ofcommunication equipment.

Forbid to add fuse, switches etc. to thegrounding cable.

General Requirement forGround

All grounding cables should be asshort and straight as possible, avoidingtwisting.

Less than 1 Ohm.

The upper end of the grounding bodydeparts from the floor at least 0.7 m; Incold region, the grounding body shouldbe buried under the frozen soil layer.

Requirement for GroundingResistance

Monitor the grounding resistance at fixedinterval to ensure the ground validity.

Signal Cable WiringRequirement

Aerial should not be arranged incommunication office or station,lead signal cable into the office fromunderground.

Grounding bonding wire can be groundingbonding ring or bonding bar.

Grounding cable can not be made ofaluminum. Prevent electrolytic corrosionwhile interconnecting different metals.Requirement for Grounding

Bonding WireThe cross-sectional area of the groundingbonding wire is generally copper bar ofat least 120 mm2 or made of galvanizedsteel plate having the same resistance.The grounding bonding wire should beisolated from the steel bar of buildings.

Requirement for GroundLead-in

The length of the ground lead-in shouldbe at most 30m, and the materialsshould be galvanized steel plate with thecross-sectional area of 40 mm×4 mm or50 mm×5 mm.

Requirements for NeatnessDescription To guarantee long-time security, stability and reliability of the sys-

tem, decrease the failure rate of devices caused by environmentalfactors, and to prolong the lifetime of the devices, requirementsfor neatness should be met.



Significance Neatness requirement is quite important for the communicationequipment; it directly influences the stability and security of theequipment.

Required Indices There are two indices for air neatness, one is the concentrationof mechanical active substance, and other is the concentration ofchemical active substance. Proper measures should be taken inthe equipment room to ensure the following requirements are metwith:

� There is no explosive, conductive, magnetic conductive andcorrosive dust.

� Concentration of mechanical active-substance meets the re-quirements listed in Table 18.

TABLE 18 REQUIREMENT FOR CONCENTRATION OF MECHANICALACTIVE-SUBSTANCE

Mechanical Active-substance Content

Dust Particle ≤3×105 Particl/m3

Suspended Dust ≤0.2 mg/m3

Degradable Dust ≤1.5 mg/m2·h

Grit ≤30 mg/m3

Remark: Dust Particle:Diameter≥5μm

Suspended Dust: Diameter≤75μm

Degradable Dust: 75μm≤Diame-ter≤150μm

Grit: 150μm≤Diameter≤1000μm

� Concentration of chemical active-substance should meet thefollowing requirements as listed in Table 19.

TABLE 19 REQUIREMENT FOR CONCENTRATION OF HARMFUL GAS

Chemical Active Substance Content

Sulfur Dioxide (SO2) 0.30 ~ 1.00 mg/m³

Sulfureted Hydrogen (H2S) 0.10 ~ 0.50 mg/m³

Silicon Dioxide (NO2) 0.50 ~ 1.00 mg/m³

Ammonia (NH3) 1.00 ~ 3.00 mg/m³

Chlorine (Cl2) 0.10 ~ 0.30 mg/m³

Hydrochloric Acid (HCl) 0.10 ~ 0.50 mg/m³

hydrofluoric acid (HF) 0.01 ~ 0.03 mg/m³



Chemical Active Substance Content

Ozone (O3) 0.05 ~ 0.10 mg/m³

Carbon Monoxide (CO) ≤5.0 mg/m³


are not met

When concentration of dust particle in air is too high, large amountof dust particles are absorbed on the surface of electronic compo-nents and the integrated circuits. The cooling ability of the com-ponents and circuits degrades. If conductive dust falls into thecomponents, insulation property between components degradesand short circuit may occur.

Chemical active-substance also has significant influence on com-munication equipment, e.g. when the concentration of acid gasessuch as sulfur dioxide is too high, communication equipment mayget corrupted, and it lead to poor contact or short circuit; if theconcentration of carbon monoxide is too high, explosion may becaused.

Requirements forEarthquake ResistanceCapability

Description To guarantee long-time security, stability and reliability of the sys-tem, decrease the failure rate of devices caused by environmentalfactors, and prolong the lifetime of the devices, requirements forearthquake resistance capability should be met.

Significance Earthquake resistant requirement is quite important for the com-munication equipment; it directly influences the stability and se-curity of the equipment.

Required Indices The design for earthquake resistance capability of the telecom-munication building where the equipment room is located shouldbe one degree higher than basic intensity of the local buildings.Earthquake resistant engineering and retrofitting is required forthose equipment buildings that do not meet the earthquake resis-tance capability requirement. For specific measures, consult thearchitecture design department to make and perform retrofittingdesign. The equipment should be resistant to M7 earthquake.


Figures

Figure 1 ZXPDSS System Architecture ................................... 1

Figure 2 ZXPDSS Location in cdma2000-1X Network ............... 3

Figure 3 Location of ZXPDSS in cdma2000-HRPD Network........ 4

Figure 4 Typical Networking Mode ......................................... 5

Figure 5 Networking Mode Supporting EV-DO Users ................ 7

Figure 6 Networking Mode Compliant with Cave-Based

Bimodal Authentication Specifications.................... 8

Figure 7 Packet Prepaid Service Networking Scheme ............... 9

Figure 8 Block Diagram Representing PDSN Hardware

System ............................................................16

Figure 9 Block Diagram Representing PDSN Hardware

Structure..........................................................17

Figure 10 Functional Block Diagram .....................................18

Figure 11 Schematic Diagram of Alarm System......................20

Figure 12 ZXPDSS Interfaces (Based on cdma2000-1X) ..........28

Figure 13 ZXPDSS Interfaces (Based on Hrpd Specifications)...28

Figure 14 Location of Accounting Interface............................30

Figure 15 Position of Billing Interface ...................................31

Figure 16 Interfaces Between ZXPDSS and OMC ....................32

Figure 17 Appearance of PDSN Cabinet.................................56

Figure 18 PDSN Cabinet Structure .......................................57

Figure 19 Structure of Server Cabinet ..................................58

Figure 20 Appearance View of Alarm Box ..............................59


Tables

Table 1 Performance Indexes of PDSN with Typical

Configuration ....................................................10

Table 2 Front Boards ..........................................................14

Table 3 Rear Boards ...........................................................15

Table 4 Basic Hardware Configuration for OMC.......................18

Table 5 Hardware Platform of LIS.........................................19

Table 6 Parts and Functions.................................................20

Table 7 Hardware Configuration of Other Devices ...................22

Table 8 Relation Between Software and Hardware (PDSN) .......23

Table 9 Relation Between Software and Hardware (AAA) .........24

Table 10 Files Included in PDSN Version Software ..................24

Table 11 OMC Software for PDSN.........................................26

Table 12 Performance Indexes of PDSN with Typical

Configuration ....................................................45

Table 13 Comparative Advantages .......................................46

Table 14 Comparative Advantages in Reliability......................50

Table 15 Electrostatic Voltage on Human Body.......................69

Table 16 Sensitivities of Different Elements or Devices to

Electrostatic Damage .........................................69

Table 17 Requirement for Anti-Lightning Ground ....................70

Table 18 Requirement for Concentration of Mechanical

Active-Substance...............................................73

Table 19 Requirement for Concentration of Harmful Gas..........73


List of Glossary

1x EV-DO - 1x Evolution Data Optimized

3GPP2 - 3rd Generation Partnership Project 2

AAA - Authentication, Authorization, Accounting

AN - Access Network

AT - Access Terminal

AUC - Authentication Center

BCMCS - Broadcast and Multicast Service

BSC - Base Station Controller

BSS - Base Station Subsystem

BTS - Base Transceiver Station

CDMA - Code Division Multiple Access

cdma2000-1X - cdma2000 Phase One

CHAP - Challenge Handshake Authentication Protocol

DBIO - DataBase Input & Output

FA - Foreign Agent

FPGA - Field Programmable Gate Arrays

FTP - File Transportation Protocol

GCONT - General Count

GLIQV - Vitesse Quad GE GLI

HA - Home Agent

HLR - Home Location Register

HRPD - High Rate Packet Data

IGPS - Interface Ge of PDSS

IMSI - International Mobile Subscriber Identifier

L2TP - Layer2 Tunnel Protocol

LAC - Location Area Code

LIC - Lawful Interception Center

LIS - Lawful Interception Server

LNS - L2TP Network Server

MP - Main Processor

MS - Mobile Station

MSC - Mobile Switching Centre

OMC - Operations & Maintenance Center

OMP - Operation Main Processor

PAP - Password Authentication Protocol



PCF - Packet Control Function

PDSN - Packet Data Serving Node

PPP - Point to Point Protocol

PPS - PrePaid Server

PSN - Packet Switch Network

QoS - Quality of Service

R-P - Radio-PDSN interface

RADIUS - Remote Authentication Dial In User Service

RMPB - Rear board of Main Processor Board

RPSN - Rear Card for PSN4V

RPU - Router Pocess Unit

RUIM2 - Rear board of UIM (type2)

RUIM3 - Rear board of UIM (type3)

SCP - Service Control Point

SMP - Service Main Processor

SNMP - Simple Network Management Protocol

UDR - Usage Data Record

UIM - Universal Interface Module

UPB - User process Borad

URPM - PDSS Subscriber Data Processing Module at RP Side

VLAN - Virtual Local Area Network

VLR - Visitor Location Register

VoIP - Voice over IP

VPN - Virtual Private Network

VRF - Virtual Route Forwarding Table


sjzl20086265-zxpdss p200 (v3 08 11) product description

Documents

hardware configuration

hardware configuration

hardware configuration

zte corporationor

hardware description

zte corporationzte plaza

networking mode compliant

distribution ofthis