NN20000-131 06 02

Nortel CDMA2000 1X
Planning and Engineering

Release: NBSS 15.0
Document Revision: 06.02
www.nortel.com
NN20000-131
.
Nortel CDMA2000 1X
Release: NBSS 15.0
Publication: NN20000-131
Document status: Standard
Document release date: 17 September 2007
Copyright 2003, 2007 Nortel Networks
All Rights Reserved.
Sourced in Canada and the United States of America
This document is protected by copyright laws and international treaties. All information, copyrights and any other
intellectual property rights contained in this document are the property of Nortel Networks. Except as expressly
authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein and
this document shall not be published, copied, produced or reproduced, modified, translated, compiled, distributed,
displayed or transmitted, in whole or part, in any form or media.
Information is subject to change without notice. Nortel reserves the right to make changes in design or components
as progress in engineering and manufacturing warrants.
* Nortel, the Nortel logo, the Globemark, Unified Networks, HLR, Metro Cell, and MSC are trademarks of Nortel.
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
Contents
New in this release
Features 7
EVRC-B Vocoder 7
Other changes 8
Document revision history 8
Document revision 06.02 8
General deployment strategy
Step 1: Business strategy 9

Step 2: Overall network distribution 11
Step 3: Comprehensive network plan 11
Network planning considerations 11
Step 4: System hardware and software status 12
Step 5: Data network strategy 13
Step 6: Customer care and billing 14
Initial state of your network

DMS-MTX and HLR 17
Preparation work 18
NBSS-BSM EBSC or BSC BTS 19
PDSN and RADIUS 19
CFDS and SOC 19
Signal quality handoff triggers 21
KRS_DSFP_CAPACITY_ENABLER 22
DSFPV capacity enabler 23
CSVS MEC enabler 25
CSVS 128ECAN enabler 26
SBS CNFP EVRC voice channel - preliminary
KRS sector power pooling 27
Transcoder free operation 28
1XRTT Rel A basic access mode 28
AABS additional sector 29
17
26
Comparing the IS-95 network to the CDMA2000 1X network

CDMA2000 1X network nodes and hardware 31
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
31
4
User terminal equipment 32
Cell site hardware 32
Hardware for the Base Station Controller or Enhanced Base Station
Controller 33
Hardware for the mobile switching center 33
Network node: Packet Data Service Node 33
Network node: Mobile IP Home Agent 34
OAM platform: Web Element Management Server 34
Hardware for the packet data network 34
Network node: external OAM gateway 35
Network management hardware 35
NBSS software upgrade from an IS95 to CDMA2000 1X network 35
NBSS BTS XCEM activation 36
NBSS-EBSC 36
MTX CDMA2000 1X voice activation 37
BTS and BSC database configuration for data 38
IP addressing strategy 39
Network access models and IP address management 39
Minimum IP address requirements 41
Private addressing 44
Public addressing 46
CDMA2000 1X network configuration
47
Network topology framework 47

Network categories 48
Local CDMA2000 1X service provider 49
Regional CDMA2000 1X service provider 50
Central CDMA2000 1X service provider 51
Logical areas 54
Generic physical connectivity 55
CDMA2000 1X network connections 59
Nortel Multiservice Switch 8100 Edge switch 60
Data network cabling 61
CDMA2000 1X routing engines 66
CDMA2000 1X server architectures 66
RADIUS servers 67
Closed R-P interface fault detection 68
Open R-P interface fault detection 69
CDMA2000 1X hardware and nodes

The CDMA2000 1X channel element module 73
Channel element 73
Capacity 73
IS-95 compatibility 74
XCEM software 74
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
73
5
Automatic detection of card type 74
The selector common interface-supreme card
Compatibility issues 75
SCI-S support for 3G data 75
SCI and 3G voice-only networks 75
Enhanced selector card 76
Selector upgrades 76
Mobile switching center 76
Upgrade to FLIS 76
Upgrade to XA-Core 77
Packet data serving node 77
Standard 78
Components 78
Physical connectivity 78
Client-server connectivity 78
R-P interface support 79
IP services 79
Home Agent 79
Hardware platform 79
Software load 80
OAM platform 80
Home Agent IP services 80
PDSN and Home Agent cards 80
Packet Accelerator card 80
Switch Processor card 81
Redundancy Crossbar card 81
Line cards 81
Element Management System (EMS) 81
EMS users 81
EMS architecture 81
EMS client 82
Server platform 82
Serving areas and regions 82
RADIUS server 82
Exception 82
Platform 83
Redundancy 83
RADIUS database 83
External OAM gateway 83
Purpose 83
The Contivity 83
Optional high-capacity solution 84
Security 84
Supporting devices 84
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
74
6
Location 85
Connectivity diagram
85
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
New in this release

The following sections detail whats new in Nortel CDMA2000 1X Planning
and Engineering, (NN20000-131) for NBSS 15.0:
Features (page 7)
Other changes (page 8)
Features
See the following sections for information about feature changes:
EVRC-B Vocoder (page 7)
EVRC-B Vocoder
This feature allows service providers the ability to trade off RF capacity
(users/sector) for voice quality and the reverse. This is achieved by
introducing an effective EVRC-B mode management scheme.
This feature also adds the Automatic Gain Control (AGC) function which
impacts the voice quality functionality for all calls on the 2pVS. This
function stabilizes the varying amplitude of speech around a comfortable
listening level, and operates in ingress, egress and both (ingress and
egress) directions.
The sections are affected by the introduction of this feature:
CFDS and SOC (page 19)

CSVS EVRC voice channel (page 23)
Selector upgrades (page 76)
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
8 New in this release
Other changes
The following global changes appear in this NTP:
Updated references to information regarding Shasta PDSN and SCS

server
Added PDSN 1600 information

NTP titles updated as required
Document revision history

Document revision 06.02
Reason for change:
Standard version of technical document for Channel Ready (ChR)

milestone.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
General deployment strategy

This chapter outlines details of the general deployment strategy and
highlights planning categories. The deployment strategy for each network
entity must be considered in great detail for successful implementations.
This chapter lists a simplistic view of the areas to be covered. Contact
data network engineers or system designers for detailed information. The
six steps outlined here give insight into areas of interest in the CDMA2000
1X network.
The steps are as follows:
1. business strategy
2. overall network distribution
3. comprehensive network plan
4. system hardware and software status
5. data network strategy
6. customer care and billing
Given the complexity of futuristic networks, use a systematic strategy when
gathering information or enforcing requirements. The general deployment
strategy is a gauge with which to measure what needs to be done to
implement the new technology. Each of the steps is explained further in
the following sections.
Step 1: Business strategy

A clear understanding of the needs and uses of the CDMA2000 1X
network drives particular solutions. Gathering as much information as
possible from the marketplace, as well as from the customer base, creates
an opportunity for focused network development.
Figure 1 "Business strategy" (page 10) provides a simple representation
of the business strategy process.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
10 General deployment strategy

Figure 1
Business strategy
While planning your CDMA2000 1X business strategy, there are a number

of issues that you need to consider. The following list provides some of
these issues.
1. Pre-paid customer and CDMA2000 1X data customer profiles must be

exclusive.
2. Currently, each subscriber must be datafilled in several places: Home

Location Register (HLR); and Authentication, Authorization, and
Accounting (AAA). Refer to CDMA PDSN 16000 System Administration
and Configuration Guide, (NN20000-197) .
3. Moving a circuit-switched data subscriber to packet data services has

both advantages and disadvantages. Using Radio Frequency (RF) is
the main advantage, because the traffic channels are only allocated
when necessary. However, packet data requires new terminals,
and the HLR datafill for circuit-switched data is different than for
packet data. Additional datafill is required on the PDSN 1600; EMS
(optionally); and the Authorization, Authentication, and Accounting
(AAA) server.
4. The requirements for updating a subscriber from IS-95 to CDMA2000

1X without data must be defined. This requires a terminal charge, but
the advantage is reduced customer cost of ownership due to increased
capacity with Code Division Multiple Access (CDMA) 3G mobiles. In
addition, there are no HLR datafill differences, so only activating the
phone is required.
5. The requirements for adding data to CDMA2000 1X must be defined.

This affects the datafill for the HLR, PDSN 1600, EMS (optionally), and
AAA.
6. Offering circuit-switched data to a CDMA 3G mobile owner increases

the cost of ownership and is counter to deploying CDMA2000 1X.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Step 3: Comprehensive network plan
11
Step 2: Overall network distribution

Provisioning the appropriate capacity for the various components in the
CDMA2000 1X network requires inputs such as subscriber distribution,
grade of service, call hold times, subscriber erlangs, data application call
model, and data-rate distribution. All of these characteristics are combined
to determine the overall network distribution for the number of 1x Channel
Element Modules (XCEM), Selector Common Interface Supreme (SCI-S)
cards, or Enhanced Selector (ESEL) cards. Figure 2 "Overall network
distribution" (page 11) represents the overall network distribution.
Figure 2
Overall network distribution
Step 3: Comprehensive network plan

Though it is extremely important to develop and capture the nodal
requirements for a CDMA2000 1X data network, those components are
combined to produce a comprehensive network. Implementation of an
effective network from IS-95 to CDMA2000 1X requires detailed planning.
Prior to the installation and commissioning of the data network
components, a clear network plan must be in place. Detailed plans can
be obtained by the appropriate Nortel Data Network Engineering groups.
Acquire the information and digest it thoroughly before attempting to
construct a CDMA2000 1X network. Consideration of the hardware entities
and their locations in the network can be measured against the Network
planning considerations (page 11) list.
Network planning considerations

Network planning considerations are as follows:
Number of co-located SCI-S cards

Number of sites with SCI-S cards
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Number of sites (local, regional, central)
Redundant hardware
Number of PDSNs
Location of PDSNs
PDSN connectivity (FELC, GELC, or both)
Existing network infrastructure
Simple IP
Mobile IP
Network management strategy
Remote operations, administration, and maintenance (OAM) access to
data network components
Figure 3 "Comprehensive network plan" (page 12) represents the major

network blocks with network security as the critical junction.
Figure 3
Comprehensive network plan
Step 4: System hardware and software status

Prior to finalizing new requirements for the comprehensive network,
the existing network must be examined. The current number of Metro
Cells*, Base Station Controllers (BSC) and configurations, Mobile
Telephone Exchanges (MTX) and peripherals, software loads, mobiles,
and applications need to be determined so that the deltas between the
existing networks and the new requirements can be resolved. Figure 4
"System hardware and software status" (page 13) shows the CDMA2000
1X network variables that need to be explored.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Step 5: Data network strategy

Figure 4
System hardware and software status
Step 5: Data network strategy

The CDMA2000 1X end-to-end network includes a supporting data
infrastructure. This infrastructure supports the basic communications
between the network elements, as well as sustains subscriber traffic.
The ultimate solution can contain multi-vendor equipment or a solution.
Figure 5 "Data network strategy" (page 14) shows required data network
elements.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
13

Figure 5
Data network strategy
Step 6: Customer care and billing

The reason for building CDMA2000 1X networks is the revenue generated
by subscribers who wish to use the services. Traditional Call Detail
Records (CDR) are used on the MTX side and either User Data Records
(UDR) or Event Detail Records (EDR) are used to keep track of and
charge customers for network use. Figure 6 "Customer care and billing"
(page 15) represents a simplistic view of the billing system.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Step 6: Customer care and billing
15
Figure 6
Customer care and billing
Upgrades to your system to establish a CDMA2000 1X network include

the following features:
Enhanced Selector Card (ESEL) deployment
ATTENTION
ESEL or CSVS cards are a requirement for CDMA2000 1X features.
XCEM or CSVS passive and active deployment

SCI-S deployment
ATTENTION
The SCI-S card is a requirement for CDMA2000 1X data capabilities (Ethernet connectivity to the
PDSN). The correct vintage of SCI-S card is required to be compatible for a given network.
CDMA2000 1X voice and data activation

Base Station Transceiver Subsystem (BTS) and BSC database
configuration for data
ATTENTION
The Metro Cell family of base stations are the only BTSs that support CDMA2000 1X features.
In addition to the components listed above, the final network configuration

contains data network elements such as aggregation nodes for the SCI-S
10BaseT links, core routers or routing switches, network management
entities (Element Manager Server [EMS] and RADIUS), Packet Data
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Switched Network-Foreign Agents (PDSN-FA) and Home Agents, network

security, and remote support structure. CALEA (Legal Intercept) solutions
are applied separately.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
17
Initial state of your network

The initial state of the customers network must consist of the following
minimum levels of hardware and software.
DMS-MTX and HLR

Mobile Telephone Exchange (MTX) (often referred to as Mobile Switching
Center [MSC]) software must be at MTX11 or later for the CDMA2000 1X
network.
To install MTX11, existing and new Greenfield sites must be upgraded to
either the SR70EM or the Extended Architecture (XA) Core configuration,
depending on their processing capacity requirements. For MTX11,
new greenfield sites must be engineered with one of the available XA
processors. Inventory of the customers current load and equipment
must be taken so upgrade plans can be made (see Table 1 "Processors
supported by each MTX release" (page 17)).
Table 1
Processors supported by each MTX release
Release 12
Release 13
Release 14
Process
or
MTX12
MSC-o
nly and
MTX12
MSC/
HLR
MTX12
Stand
alone
HLR
MTX13
MSC-o
nly and
MTX13
MSC/
HLR
MTX13
Stand
alone
HLR
PMSC
13
MTX14
MSC-o
nly and
MTX14
MSC/
HLR
MTX 14
Stand
alone
HLR
PMSC14
BRISC
(SR70
EM)
Yes
Yes
Yes
Yes
No
No
No
No
Atlas
1+1 ( 2
- NTLX
02DA)
No
No
Yes
No
No
Yes
No
No
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
18 Initial state of your network
Table 1
Processors supported by each MTX release (contd.)
Release 12
Release 13
Release 14
Process
or
MTX12
MSC-o
nly and
MTX12
MSC/
HLR
MTX12
Stand
alone
HLR
MTX13
MSC-o
nly and
MTX13
MSC/
HLR
MTX13
Stand
alone
HLR
PMSC
13
MTX14
MSC-o
nly and
MTX14
MSC/
HLR
MTX 14
Stand
alone
HLR
PMSC14
Atlas
2+1 (3 NTLX
02DA)
Yes
Yes
Yes
Yes
No
Yes
Yes
No
Atlas
3+1 (4 NTLX
02DA)
Yes
No
Yes
No
Yes
Yes
No
Yes
Atlas
5+1 (6 NTLX
02DA)
No
No
Yes
No
No
Yes
No
Yes
Rhino
3+1 (4NTLX
02CA)
Yes
Yes
Yes
Yes
No
Yes
Yes
No
While enabling your Digital Multiplex System-Mobile Telephone Exchange

(DMS-MTX) platforms with the processing capacity required for future
releases, the following upgrade road map adds immediate benefits as well:
XA Cores scalable processing capacity easily accommodates network

growth.
Processor upgrades support succession evolution and 3G networks.

The road map provides a clear upgrade path for SR60 and SR70
series processors, which makes it easy to plan for higher processing
capacity needed for new releases.
Preparation work
This section contains preparation information.
Hardware preparation information is as follows:
The minimum XA-Core CPU supported by MTX11 is NTLX02CA.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
CFDS and SOC
19
ATTENTION
When planning for a CM-upgrade requirement, factor in the capacity hit on relative CPOCC. This
can reflect a need to upgrade to XA-Core sooner than planned.
Migrate existing XA-Core 1+1 to a 5+1 configuration during the MTX11

upgrade. This is part of the ONP-to-MTX12 and adds two CPU cards
to the frame.
XA-Core-equipped MTXs require an SDM for billing.
For more information about the SDM, refer to DMS-MTX SDMX

SuperNode Billing Application User Guide, (411-2131-902).
HLRs in the network must be at software baseline of MTX11.
NBSS-BSM EBSC or BSC BTS

The current Base Station Subsystem Manager (BSSM), enhanced Base
Station Controller (EBSC) or Base Station Controller (BSC), Base Station
Transceiver Subsystem (BTS) software must be at NBSS 13.0 to upgrade
to NBSS 14.0. The BTS (Metro Cell) must have XCEM circuit packs.
EBSC or BSC must have appropriate SCI-S circuit packs to allow data
calls. EBSC or BSC must have ESEL circuit packs to allow for voice or
data calls. SBS shelf must have the appropriate cable assembly to allow
10-BASE T connection from the SBS shelf to the PDSN. Finally, EBSC or
BSC hardware must be at NBSS 13.0 before upgrading to NBSS 14.0.
PDSN and RADIUS

The PDSN 1600 must have a minimum software level of PDN 4.5.
The RADIUS software must be confirmed to be compatible with the
specific data network configuration.
CFDS and SOC

The following CDMA Customer Feature Delivery System (CFDS) software
features must be reviewed to confirm sufficient licenses have been
purchased for the expected voice/data capacity.
EVRC (CPC code of A0716537/feature order code of CDMA0001)
3G Voice Enabler (CPC A0846806/Nortel PEC of NT2J11AD/KRS_

3G_Voice_Enabler)
3G Packet Data Enabler (CPC A0846812/Nortel PEC of

NT2J11AH/KRS_3G_Packet_Data_Enabler)
EVRC-B (CPC N0127991/Nortel PEC of NT2J11DF/KRS_CSVS_E

VRC-B_CAPACITY_ENABLER)
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
1XRTT Radio Resource Management (CPC A0846807/Nortel PEC of

NT2J11AE/KRS_1XRTT_RADIO_RESOURCE_MGMT)
E SBS Shelf Data Capability (CPC A0846813/Nortel PEC of

NT2J11AI/KRS_ESBSSHELF_DATA_CAPABILITY)
Quick Paging Channel Control (CPC A0846809/Nortel PEC of

NT2J11AF/KRS_QUICK_PAGING_CHANNEL_CONTROL)
Additional MFRM Carrier (CPC A0846803/Nortel PEC of NT2J11AA/

KRS_ADDITIONAL_MFRM_CARRIER)
Extended Coverage MFRM (CPC A0846804/Nortel PEC of NT2J11AB/

KRS_EXTENDED_COVERAGE_MFRM)
MFRM Extender Fiber (CPC A0846805/Nortel PEC of NT2J11AC/

KRS_EXTENDED_FIBER)
Extended Coverage XCEM (CPC A0846810/Nortel PEC of NT2J11AG/

KRS_EXTENDED_COVERAGE_XCEM)
Reverse Supplemental Channel Control (CPC A0846815/Nortel PEC of

NT2J11AJ/ KRS_REVERSE_SUPPLEMENT_CH)
11pMSW FP Provisioning (CPC A0838296/Nortel PEC of NT2J11BA/

KRS_CDMA_11PMSW_FP)
24pBCN FP Provisioning (CPC A0838384/Nortel PEC of

NT2J11BB/KRS_CDMA_24PBCNW_FP)
MCTA Phase II MMTA Enabler (CPC A0011821/Nortel PEC of

NT2J11CD/ KRS_MCTA_Phase_II-MMTA_ENABLER)
1xEV-DO Carrier Enabler (CPC A0992425/Nortel PEC of NT2J11CA/

KRS_1XEV_DO_CARRIER_ENABLER)
RC Management for Voice (CPC A0502167/Nortel PEC of NT2J11CH/

KRS_RC_Management_Enabler)
Eighth Rate Reverse FCH Gating (CPC A0502171/Nortel PEC of

NT2J11CI/ KRS_R_FCH_Gating_Enabler)
eDCG Dual_DCG (CPC A0503804/Nortel PEC of NT2J11CC/KRS_DU

AL_DCG_Enabler)
eDCG Capacity Enabler (CPC A0503803/Nortel PEC of NT2J11CB/

KRS_eDCG_Capacity_Enabler)
DSFP 100FCH Capacity Enabler (CPC A0505389/Nortel PEC of

NT2J11CE/ KRS_DSFP_100FCH_CAPACITY_ENABLER)
1xRTT Phase II (12.1) (CPC A0512059/Nortel PEC of NT2J11CJ/

KRS_CONFIGURABLE_BURST_SCHEDULER)
XCEM192-CESubpools Enabler (CPC A0518998/Nortel PEC of

NT2J11CK/ KRS_XCEM_CE_Enabler)
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Signal quality handoff triggers
21
Signal Quality Handoff Triggers (CPC A0551183/Nortel PEC of

NT2J11CT/ KRS_EC_SIGNAL_QUALIT_HO_TRIG
KRS_DSFP_CAPACITY_ENABLER (CPC A0539822/Nortel PEC of

NT2J11CL/ KRS_DSFP_CAPACITY_ENABLER)
DSFPV Capacity Enabler (CPC A0539823/Nortel PEC of NT2J11CM/

KRS_2pVS_CAPACITY_ENABLER)
CSVS EVRC Voice Channel (CPC A0539824/Nortel PEC of

NT2J11CY/KRS_CSVS_EVRC_Voice_Channel)
CSVS MEC Enabler (CPC A0539826/Nortel PEC of NT2J10CQ/

KRS_CSVS_MEC_CSVS_Enabler)
CSVS 128ECAN Enabler (CPC A0539827/Nortel PEC of NT2J10CR/

KRS_CSVS_128ECAN_CSVS_Enabler)
SBS CNFP EVRC Voice Channel - Preliminary (CPC A0546399/Nortel

PEC of NT2J11CZ/KRS_SBS_CNFP_EVRC_Voice_Channel)
KRS Sector Power Pooling (CPC N0059903/Nortel PEC of

NT2J11CU/KRS_SECTOR_POWER_POOLING)
Transcoder Free Operation (CPC N0044562/Nortel PEC of

NT2J11CV/Transcoder_Free_Operation)
1XRTT Rel A Basic Access Mode (CPC N0077008/Nortel PEC of

NT2J11CW/1XRTT_Rel_A_Basic_Access_Mode)
AABS Additional Sector (CPC N0075390/Nortel PEC of

NT2J11CX/KRS_AABS_ADDITIONAL_SECTOR)
The following Software Optionality Control (SOC) features are required

for CDMA2000 1X implementation:
MTX SOC feature TEL00009 is optionally required for 3G handoffs to

occur between Nortel MTXs.
MTX SOC feature CDMA0011 is required for the Voice Call

Preemption of an Active Data Call feature.
MTX SOC feature CDMA0009 is required to support following 3G

service

This feature introduces a new Signal Quality Handoff Trigger based on Ec
to minimize unused capacity on the overlay carrier and provide a more
reliable link quality trigger using the Ec metric.
A single RTU is purchased per BSC.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
CPC: A0551183
PEC: NT2J11CT
Name: KRS_EC_SIGNAL_QUALIT_HO_TRIG
Feature Type: State
S/W Dependencies: NBSS13.0
Licensing Requirements:
Min. load NBSS13.0

Provide one (1) license per BSC
KRS_DSFP_CAPACITY_ENABLER
This feature allows the ability to increment the capacity of a DSFP_V card
pair in increments of one Voice Channel. When the card is initially installed
252 Voice Channels are enabled in the card (by default not requiring any
CCDS license). Each CCDS license increases the card capability of one
Voice Channel.
CPC: A0539822
PEC: NT2J11CL
Name: KRS_DSFPV_CAPACITY_ENABLER
Feature Type: Pool
Min. load NBSS14.0

In order to reach the full capacity of a DSFP_V card pair, 423 Capacity
Enabler licenses (NT2J11CL) are required. Licenses are taken from,
and returned to, the CCDS Server based on the capacity being
enabled in the card.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
23
DSFPV capacity enabler

This feature allows the ability to increment the capacity of a 2pVS card pair
in increments of one Voice Channel. When the card is initially installed
252 Voice Channels are enabled in the card (by default not requiring any
CCDS license). Each CCDS license increases the card capability of one
Voice Channel.
CPC: A0539823
PEC: NT2J11CM
Name: KRS_2pVS_CAPACITY_ENABLER
Feature Type: Pool
Min. load NBSS14.0

In order to reach the full capacity of a 2pVS card pair, 1,764 Capacity
Enabler licenses (NT2J11CL) are required. Licenses are taken from,
and returned to, the CCDS Server based on the capacity being
enabled in the card.
CSVS EVRC voice channel

This option allows the increment of the maximum number of EVRC
Channels allowed in the EBSC. When the system is deployed no EVRC
support is provided. Each CFDS license increments by one the number of
EVRC channels supported in the EBSC. The EBSC capacity is configured
at the CNFP card level.
CPC: A0539824
PEC: NT2J11CY
Name: KRS_CSVS_EVRC_Voice_Channel
Feature Type: Pool
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Min. load NBSS14.0

One CSVS EVRC Voice Channel license (NT2J11CN) is required for
each EVRC Channel support at EBSC level. Licenses are taken from,
and returned to, the CFDS Server based on the capacity being enabled
in the EBSC.
CSVS EVRC-B vocoder

This option enables voice channel capacity for EVRC-B SO (on CSVS)
which is a spectral efficient next generation CDMA vocoder. EVRC-B
enables customers to tradeoff RF capacity (users/sector) for voice quality
or the reverse.
CPC: N0127991
PEC: NT2J11DF
Name: KRS_CSVS_EVRC-B_CAPACITY_ENABLER
Feature Type: Pool
S/W Dependencies: NBSS15.0 and NOIS 15.0 or later
Min. load NBSS15.0

You set the CSVS EVRC-B attribute to the total number of channels
desired, the corresponding number of CCDS licenses is requested
at CNFP card activation, or when the attribute is set after Activation.
Licenses are taken from, and returned to, the CFDS Server based on
the capacity being enabled in the EBSC.
CSVS Automatic Gain Control

Automatic Gain Control (AGC) is a voice quality enhancement feature that
maintains comfortable listening level and improves speech intelligibility.
The feature amplifies speech signal that is too low or attenuates if it is too
high. It reduces listener fatigue and facilitates longer conversation, which
translates to potential revenue increase for the operator.
CPC: N0127992
PEC: NT2J10CX
Name: KRS_CSVS_AGC_ENABLER
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
25
Feature Type: State

Min. load NBSS15.0

Enabling AGC automatically retrieves an AGC license from KRS. The
license for AGC is applied when the feature is configured on a 2pVS
card. Licenses are taken from, and returned to, the CFDS Server
based on the capacity being enabled in the EBSC.
CSVS MEC enabler

This option allows the enabling of the Mobile Echo Control feature at 2pVS
card level. When the system is deployed the Mobile Echo Control (MEC)
is disabled for all 2pVS cards. This feature can be enabled at EBSC wide
basis or at card basis depending on the voice profile defined to each card.
If you enable the MEC feature at EBSC wide level all the cards using the
EBSC voice profile has the MEC feature enabled. If the cards have its own
voice profile the enabling/disabling of the feature is done directly at the
card.
CPC: A0539826
PEC: NT2J10CQ
Name: KRS_CSVS_MEC_CSVS_Enabler
Feature Type: Pool
Min. load NBSS14.0

One CSVS MEC Enabler license (NT2J10CQ) is required to allow the
enabling of the MEC feature to all 2pVS cards in the EBSC. License is
taken from, and returned to, the CFDS Server based on the number of
2pVS cards with the MEC feature enabled. If no 2pVS card is using
MEC feature no license is required even when the MEC feature is
enabled at EBSC level.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
CSVS 128ECAN enabler

This option allows the enabling of the 128 Echo Cancellation feature at
2pVS card level. When the system is deployed the 128 Echo Cancellation
(128ECAN) is disabled for all 2pVS cards. This feature can be enabled
configuring a MgTdmProfile to use the ECAN128 and associating it with a
2pVS trunk.
CPC: A0539827
PEC: NT2J10CR
Name: KRS_CSVS_128ECAN_CSVS_Enabler
Feature Type: State
Min. load NBSS14.0

One CSVS 128ECAN Enabler license (NT2J10CR) is required to allow
the enabling of the 128ECAN feature to all 2pVS cards in the EBSC.
License is taken from, and returned to, the CFDS Server based on the
number of 2pVS cards with the 128ECAN feature enabled. If no 2pVS
card is using the 128ECAN feature no license is required even when
the 128ECAN feature is enabled at EBSC level.
SBS CNFP EVRC voice channel - preliminary

This option allows the increment of the maximum number of EVRC
Channels in the entire SBS ESEL under the control of CNFP. When the
system is deployed no EVRC support is allowed for the SBS ESEL. One
license represents the increment of one EVRC channel at the SBS ESEL
controlled by the CNFP.
CPC: A0546399
PEC: NT2J11CZ
Name: KRS_SBS_CNFP_EVRC_Voice_Channel
Feature Type: Pool
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
27
Min. load NBSS14.0

One SBS EVRC Voice Channel license (NT2J11CS) is required for
each EVRC Channel support at SBS ESEL controlled by the CNFP.
Licenses are taken from, and returned to, the CFDS Server based on
the capacity being enabled in the EBSC.
KRS sector power pooling

This option allows you to steer power from one sector to other. This allows
for flexibility in the distribution of power across sectors when configuring
the radio and allows the radio to adapt to changing conditions when the
demand for power across sectors is uneven.
Sector Power Pooling is made possible by the coherent power combining
mechanism available on the MFRM-3 and it allows PA power management
in a pool across all three sectors and dynamically distribute it into different
sectors, when enabled by the operator. The limited PA power resource no
longer belongs to a specific sector, allowing in a scenario where a sector is
experiencing heavy traffic loading and the other sectors have lighter traffic,
for the loaded sector to transmit beyond its nominal max power.
This feature can be enabled or disabled by the operator at RFM level
through the new attribute SectorPowerPoolingEnabled on the RFM MO via
attribute set command. A CCDS license is required to enable sector power
pooling.
CPC: N0059903
PEC: NT2J11CU
Name: KRS_SECTOR_POWER_POOLING
Feature Type: Pool
Min. load NBSS14.0

One Sector Power Pooling license is required for each MFRM3 which
has the SectorPowerPoolingEnabled attribute set to TRUE. Licenses
are taken from, and returned to, the CFDS Server based on the CCDS
controlled attribute SPPE (Sector Power Pooling Enabled).
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Transcoder free operation

Transcoder Free Operation (TrFO) is the ability of a wireless network
to transmit native coded voice between the source and destination.
Transcoding is performed if origination and termination codes do not match
(to some common format understood by both parties, for example, G.711).
The TrFO feature enables transport capacity improvements/savings.
TrFO is configured at a 2pVS card pair level by setting the TransportType
attribute to PacketTrFO. This setting requires one license from the CFDS
server at card activation or later. Each 2pVS card pair with PacketTrFO
requires their own license. If a license is unavailable the set request or
card activation fails.
CPC: N0044562
PEC: NT2J11CV
Name: Transcoder_Free_Operation
Feature Type: Pool
Min. load NBSS14.0

One Transcoder_Free_Operation license (NT2J11CV) is required to
allow TrFO on one 2pVS card pair.
1XRTT Rel A basic access mode

This feature provides support for the IS2000 Release-A Basic Access
Mode (BAM) functionality on a per carrier-sector basis. Basic Access
Mode requires support of Mandatory Release-A (PREV 7) functionality and
three new Release-A common channels on the BTS: Broadcast Control
Channel (F-BCCH), Forward Common Control Channel (F-CCCH), and
Enhanced Access Channel (R- EACH). This feature also provides support
for the Synch Channel Workaround solutions proposed by the CDMA
Development Group for non-compliant IS95 (PREV 5) Nokia and Motorola
mobiles.
The BAM is a CFDS controlled feature. One license is required to enable
the feature across all the network managed by one CDMA OA Server.
CPC: N0077008
PEC: NT2J11CW
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
29
Name: 1XRTT_Rel_A_Basic_Access_Mode
Feature Type: State
Min. load NBSS14.0

One 1XRTT_Rel_A_ Basic_ Access_Mode license (NT2J11CW) is
required to enable BAM feature on all BTSs managed by a single
CDMA OA Server.
AABS additional sector

The Adaptive Antenna Beam Selection (AABS) solution improves the
CDMA system capacity of the MetroCell BTS by improving the spectral
efficiency, typically by a factor of 2, in terms of Erlangs per carrier sector
(for voice calls) or subscribers/data rate per carrier sector (for packet data).
Feature provides the ability to provision carrier-sector as AABS to use
AABS capabilities.
The AABS is a CFDS controlled feature and licenses must be available
when configuring the SectorType attribute to AABS in the AdvancedSector
MO.
CPC: N0075390
PEC: NT2J11CX
Name: KRS_AABS_ADDITIONAL_SECTOR
Feature Type: Pool
Min. load NBSS14.0

One AABS license is required for each carrier-sector to be provisioned
as AABS.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
31
Comparing the IS-95 network to the

CDMA2000 1X network
CDMA2000 1X network nodes and hardware
The Nortel CDMA2000 1X product offers a network evolution path so that
carriers can reuse most of their existing IS-95 wireless networks. However,
some hardware changes and installations are required to complete the
upgrade from an IS-95 network to an CDMA2000 1X network.
Figure 7 "Network nodes and hardware upgrades in the Nortel CDMA2000
1X product" (page 32) shows the relationship between the upgraded
hardware components in a CDMA2000 1X system and their context within
the CDMA2000 1X product model.
ATTENTION
The figures reference the BSC; however, you can also have an EBSC within your CDMA2000
1X network.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
32 Comparing the IS-95 network to the CDMA2000 1X network
Figure 7
Network nodes and hardware upgrades in the Nortel CDMA2000 1X product
User terminal equipment

The mobile device can be any electronic communications equipment
that supports the IS-2000 CDMA air interface. IS-95 mobile telephones
can also make and receive calls on the CDMA2000 1X network, but they
cannot make packet data calls.
Typical user devices include cellular telephone handsets, Personal
Digital Assistants (PDA), and laptop computers equipped with IS-2000
CDMA modem cards. The choice of an access device depends on the
requirements and budget of the subscriber. The categories of devices are
not mutually exclusive. Many high-end cellular telephones also include
PDA capabilities, and many PDA devices and a radio-equipped computer
can make voice calls with the use of a special head-set.
Cell site hardware

The CDMA2000 1X product reuses the existing CDMA Metro Cell* Base
station Transceiver Subsystem (BTS). All variants of the Metro Cell BTS
(outdoor, indoor, Rural Cell, CDMA Minicell) are capable of running
CDMA2000 1X compatible software.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
CDMA2000 1X network nodes and hardware 33
The only upgrade required to Metro Cell hardware is the CDMA2000 1X

Channel Element Module (XCEM). The XCEM is an 3G-ready version of
the IS-95 channel element module (the Classic Channel Element Module,
or CCEM).
For more information about the XCEM card, see The CDMA2000 1X
channel element module (page 73).
Hardware for the Base Station Controller or Enhanced Base Station

Controller
The only subsystem in the Base Station Controller (BSC) that requires new
hardware is the Selector Bank Subsystem (SBS). The following hardware
replacements are necessary when a Nortel BSC becomes part of an
CDMA2000 1X wireless network:
The Enhanced Selector card (ESEL) replaces the selector card. See
Enhanced selector card (page 76).
The Selector Common Interface Supreme (SCI-S) card replaces

the selector common interface card. See The selector common
interface-supreme card (page 74).
Hardware for the mobile switching center

There are no mandatory hardware upgrades for the DMS-MTX* switch
or for the DMS-100W* switch when the switch becomes part of an
CDMA2000 1X network.
The network configuration and call model of the service provider
determines if the following optional upgrades are necessary:
upgrade of the Link Peripheral Processor (LPP) to Fiberized Link

Interface Shelf (FLIS) to support increased signaling traffic
upgrade to XA-Core to support capacity requirements
See Mobile switching center (page 76).
Network node: Packet Data Service Node

The Packet Data Service Node (PDSN) is a node the CDMA2000 1X
product introduces into the CDMA network. The PDSN serves as a
gateway for packet data traffic between the BSC or EBSC and a long-haul
IP transport network, such as the Internet. Using the PDSN, the carrier
can offer value-added IP services. The PDSN can also host a Mobile IP
Foreign Agent (FA) in networks that deploy mobile IP.
For a more detailed description of the PDSN, please see Packet data
serving node (page 77).
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Network node: Mobile IP Home Agent

The Mobile IP Home Agent conforms to the requirements of the IS-835
standard that apply to the Home Agent functionality within a wireless IP
network. The Home Agent tracks the location of a Mobile IP subscriber as
the mobile unit moves from one packet zone to another, and forwards IP
packets to the radio network that is the IP access to the mobile.
For more information, see Home Agent (page 79).
OAM platform: Web Element Management Server

The Element Management Server (EMS) is a graphical Operations,
Administration, and Maintenance (OAM) platform that provides for the
remote management and monitoring of the system network elements.
The software uses client server architecture to provide complete FCAPS
(Faults, Configuration, Administration, Provisioning, Security) management
operations for the PDSN and Home Agent nodes within the CDMA2000
1X network.
For more information, see CDMA PDSN 16000 System Administration and
Configuration Guide, (NN20000-197) and Nortel CDMA PDSN 16000 Web
Element Manager Guide, (NN20000-205).
Hardware for the packet data network

A carrier that deploys the CDMA2000 1X product must provide an IP
access network to connect the CDMA radio network to the ultimate
destination of the packet traffic, which in most cases is the Internet.
The packet data network must include both a transport backbone and
resources to provide IP-based services.
The number and types of network elements in the packet-switched
network depend on several factors, including the size of the network
and what existing network hardware the carrier already has. The packet
data network of the carrier typically contains some or all of the following
equipment:
Ethernet hubs
Routers
Switching routers
Asynchronous Transfer Mode (ATM) switches
For more information, please see Packet data serving node (page 77).
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
NBSS software upgrade from an IS95 to CDMA2000 1X network
35
Network node: external OAM gateway

Nortel recommends the Contivity VPN Switch for this function. The
Contivity allows secure access for up to 30 encrypted tunnels between
the carrier IP network and Nortel support facilities. These tunnels use
state-of-the-art encryption techniques to transport sensitive OAM packet
traffic across a network that is not secure, such as the Internet.
For more information, please see External OAM gateway (page 83).
Network management hardware

Even if the carrier already has a packet data network in place, adding
CDMA2000 1X packet data and supporting hardware to this network
increases the amount of resources required for network management:
configuration, surveillance, and operations.
The network management hardware typically takes the form of a server
farm, which contains at least one each of the following:
management console
application servers
directory and database servers
server managers
RADIUS servers
For more information, see RADIUS server (page 82).

The preparation work and upgrades for Nortel Base Station Subsystem
(NBSS) can vary depending on the planned deployment. The following
scenarios outline the most common characteristics required for upgrading
the network.
NBSS software upgrade from an IS95 to CDMA2000 1X network

When upgrading from one NBSS release to another, cell sites are taken
down for approximately one hour when they are upgraded, which can
impact service. Passively inserting the XCEM in the Metro Cell at this
time does not impact service. For more information about NBSS software
upgrades, refer to the following documents:
Nortel CDMA ATM BSC and EBSC Upgrades -- Software,

(NN20000-132)
Nortel CDMA BSC Upgrades -- Software, (NN20000-133)

Nortel CDMA BTS Upgrades -- Software, (NN20000-134)
Nortel CDMA CSP Upgrades -- Software, (NN20000-135)
Nortel CDMA Upgrades -- Network Prechecks, (NN20000-136)
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
NBSS BTS XCEM activation

If the XCEM 32/64 has not been passively added, it must be added now,
but with caution not to over-provision Channel Element Modules (CEM)
on the BTS. Create the XCEM MO at the BSS Manager and bring it into
service. See Figure 8 "NBSS BTS XCEM activation" (page 36).
Adding XCEMs requires BTS commissioning, which makes the site
unavailable for about two hours. No installation and commissioning (I&C)
activity is required to add a CEM. The only operation impacts are during
regression testing and benchmarking.
IS95 voice capabilities remain. Feature activation cannot take place until
the MTX12 upgrade (CDMA2000 1X voice or data). Rural cell Customer
Feature Delivery System (CFDS) can be enabled.
Figure 8
NBSS BTS XCEM activation
NBSS-EBSC
NBSS software delivers the Enhanced BSC (EBSC) functionality. It
requires a BSS Manager upgrade and a load for the Multiservice Switch
15000 that replaces the DISCO. Deployment requires I&C activities.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
MTX CDMA2000 1X voice activation
37
For more information, see Nortel CDMA EBSC Planning and Engineering,
(NN20000-139).
MTX CDMA2000 1X voice activation

To activate CDMA2000 1X voice, the CDMA2000 1X/IS-95 coexistence
must be engineered. CDMA2000 1X voice (CFDS) and traffic steering
(CFDS) must also be enabled. See Figure 9 "CDMA 3G voice activation"
(page 38).
Service is impacted when the reload of the DMS-MTX is restarted. The
operations cannot be interrupted during new feature testing. Voice
capacity and quality, as well as battery life, must also be tested, however,
parameters are entered on the fly and do not affect service.
ATTENTION
Restrictions exist on CDMA2000 1X functionality delivered on the extended cell. This is an SHO
restriction for CDMA2000 1X.
IS95 voice capabilities remain. CDMA 3G voice calls are enabled with
proper mobiles, where new XCEMs are deployed and CDMA 3G voice
enabler CFDS is activated. Quick paging CFDS and Rural cell CFDS can
be enabled. For more information about the activation of theses services,
refer to the Nortel CDMA CFDS Configuration -- Feature Activation,
(411-2133-206). Radio Resource Management (RRM) is not activated until
data functionality is achieved (that is, until the PDSN deploys).
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007

Figure 9
CDMA 3G voice activation
BTS and BSC database configuration for data

Shelves on the BSC must be configured for voice or voice and data
because data-only shelf configurations are not supported. See Figure 10
"BTS and BSC database configuration for data" (page 39).
ATTENTION
T1s from SBS to MSC are still needed, even if they are not used for data traffic.
On the BTS, the carrier must be configured for voice, voice and data, or
data only. Service is not impacted on the BTS, because all parameters
are entered on the fly.
Refer to Nortel CDMA Configuration , (411-2133-310) for more information
required to make BTS and BSC changes.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
IP addressing strategy
39
Figure 10
BTS and BSC database configuration for data
The IP address strategy for the end-to-end network solution needs to be
carefully planned. Recommendations and suggestions are listed in this
section.
Network access models and IP address management

Criteria for the IP addresses in each Network Access Model is listed below
and in Table 2 "Access Model IP address summary" (page 40).
Simple IP
The mobile terminal receives a dynamically assigned address from the
pools located on the PDSN-FA or AAA. It is recommended that the IP
addresses in the pool are unique and can be publicly routed.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Simple IP VPN
The mobile terminal receives a dynamically assigned address from private
IP space belonging to the Service Provider or the ISP. The pools are
configured on the Security Gateway or through other unspecified means.
The IP address can be private or an address that can be routed publicly.
The IP address does not have to be unique.
Mobile IP
The mobile terminal receives either a dynamically assigned or statically
pre-configured address from the Home Agent or the Home Agents AAA
server within the Service Providers IP space. The IP address must be
able to publicly route and must be unique across both the PDSN-FA and
the Home Agent.
Mobile IP VPN
server within the Service Providers IP space. The IP address can be able
to publicly or privately route and must be unique across the Home Agent.
Uniqueness is not required across the PDSN-FA.
Mobile IP reverse tunnel

server within the Service Providers IP space. The IP address can be able
to publicly or privately route and can be unique across the Home Agent.
Uniqueness is not required across the PDSN-FA.
Mobile IP Network-based VPN

The mobile terminal receives a dynamically assigned address from the
Home Agent or the Home Agents AAA server. The IP address comes
from the IP address space of the private network or from the Service
Provider space if the private network/ISP is capable of routing on the
Service Providers address space. The IP address must be unique across
the Home Agent.
Table 2
Access Model IP address summary
Network access model
IP address management
IP address
location
Simple IP
Dynamic, Public
PDSN-FA or AAA
Simple IP VPN
Dynamic, Private or Public
Security Gateway
or AAA
Mobile IP
Static or Dynamic, Public
Home Agent
(PDSN-HA) or
AAA
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
41
Table 2
Access Model IP address summary (contd.)
Network access model
IP address management
IP address
location
Mobile IP VPN
Static or Dynamic, Private or Public
Home Agent
(PDSN-HA) or
AAA
Mobile IP Reverse Tunnel
Static or Dynamic, Private or Public
Home Agent
(PDSN-HA) or
AAA
Mobile IP Network-based VPN
Dynamic
Home Agent
(PDSN-HA) or
AAA
Minimum IP address requirements

Network component separation through subnet management is one way
to keep track of areas in a network design. The suggestions presented
are guidelines for planning and are not meant to suggest a rigid structure.
Only the minimum IP address requirements are listed. As the network
needs dictate, more IP space is required. Each subnet segment is
described with its affected components. Keep in mind that there are two
ends to each connection. Therefore, each component needs to be made
aware of its counterpart through IP communication.
Subnet A: R-P interface

This subnet is dedicated to the connections between the BSC and
Aggregation Nodes such as Nortel Multiservice Switch 8100 Edge
Switches. It includes the following equipment:
SCI-S
Aggregation Node
Base Station Subsystem Manager (BSS Manager)
Reserved: 4+ (one for SCI-S, one for the Aggregation Node, one for
the BSS Manager, plus spares. The number of spares depends on the
number of SCI-S links.)
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Subnet B: Aggregation nodes to core equipment

This subnet is dedicated to the connections between the aggregation node
and core equipment routing engines. Whether a Nortel Ethernet Routing
Switch, Nortel Multiservice Switch 8000 Series Routing switch, or Alteon
Web switch is used depends on the size of the network being built. It
includes:
Aggregation nodes
Core equipment
Reserved: 3+ (one for aggregation node, one for interface on core
equipment, spares. The number of spares depends on the number of
aggregation node links.)
Subnet C: Core equipment to RADIUS

This subnet is dedicated to the connections between the core equipment
and the RADIUS segment. It is important to isolate Network Management
areas especially. These components are critical to operation and recovery.
This subnet includes the following equipment:
Core equipment
RADIUS server(s)
Reserved: 7+ (one for each RADIUS server links, spares. The number
of spares depends on the number of RADIUS server links.)
Subnet D: Core equipment to EMS

This subnet is dedicated to the connection between the core equipment
and the EMS segment. The number of EMS servers depends on the
number of PDSNs and the number of regions per PDSN. It is important to
isolate Network Management areas especially. These components are
critical to operation and recovery.
This subnet includes the following components:
Core equipment
EMS server(s)
Reserved: 4+ (one for each of the EMS server links, spares. The
number of spares depends on the number of EMS server links.)
Subnet E: Core equipment to PDSN

This subnet is dedicated to the connection between the core equipment
and the PDSN. The number of PDSNs depends on the number of
subscribers supported and the loading required per PDSN.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
43
This subnet includes the following components:
Core equipment
PDSN
Reserved: 2+ (one for each of the PDSN links, spares. The number of
spares depends on the number of PDSNs required.)
Subnet F: PDSN-to-firewall (Subnet F: Core Equipment-to-firew

all)
This subnet is dedicated to the connection between the PDSN-to-firewall
or core equipment-to-firewall. The choice depends on whether PDSN
firewall capabilities or a network edge firewall solution is used.
This subnet includes the following equipment:
PDSN
Core equipment
Firewall
Reserved: 2+ (one for each firewall link, spares. The number of spares
depends on the number of firewall access links.)
Subnet G: PDSN-FA IP address pool

This subnet is dedicated to the pool of IP addresses allocated in the
PDSN-FA or Home Agent for dynamic or static assignment to mobile
users. This number depends on the number of data subscribers. This
subnet includes:
Reserved: 10+ (This number depends on the number of data
subscribers.)
The minimum subnet requirements are listed in Table 3 "Minimum subnet
requirements" (page 44).
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007

Table 3
Minimum subnet requirements
Subnets ->
Address Type
Pr
Pr
PrPb
Pr
PrPb
Pb
Pb
Equipment IP Addresses
10
Total (Spares Included)
4+
3+
7+
4+
2+
2+
10+
Pr means that the IP addresses are private and inaccessible for the general public as in
Class A-10.x.x.x, Class B-172.16.x.x, and Class C-192.168.x.x.
PrPb means that the IP addresses are private-public on an internal corporate LAN/WAN
environment. Inaccessible from the general public. Addresses that are blocked from the
Internet by a firewall, but if unguarded by a firewall can be generally accessible from the
Internet
Pb means that the IP addresses public and are accessible to everyone as in the Internet.
Private addressing
The private IP address map presented in this section is to be used in
cases where customers have not provided their actual IP addressing
scheme to the appropriate Nortel contacts. The goal of this method
is to streamline the process of network configuration and to minimize
the amount of down time experienced while waiting for appropriate IP
addresses from the service provider. Shows the private IP address classes
and ranges.
Table 4
Private IP addresses
IP clas
s
Private IP range
Default subnet
mask
Number of
networks
Number of hosts
per network
Class A
10.0.0.0-10.255.255.255
255.0.0.0
126
16 777 214
127.0.0.0-127.255.255.255
Internal Loopback Range
Class B
172.16.0.0-172.31.255.255
255.255.0.0
16 384
65 534
Class
C
192.168.0.0-192.168.255.2
55
255.255.255.0
2 097 152
254
The IP address ranges have been engineered for maximum configuration

and network simplicity. Each network portion is assigned a unique subnet.
Multiples of each network entity are likely to appear in every network.
For example, you can have up to 112 SCI-S cards for a maximum
configuration on a 4-DISCO BSC. Up to 127 host addresses have been set
aside for SCI-S cards on each BSC. An excessive amount of BayStack
450 IP addresses have also been set aside. Since there can be up to 14
SBS frames, each with a maximum of 8 10BaseT ethernet links, there can
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
45
be up to 16 BayStack 450 24-Port switches per BSC. While it is unlikely

that the maximum number of networks is encountered, room for it exists,
just in case.
The 172.16.x.x Class B private subnet was chosen because it is
not commonly used in many networks. The preference for Network
Administrators is usually 10.x.x.x Class A or 192.168.x.x Class C. Table 5
"Private IP address map" (page 45) contains an IP address map example.
Table 5
Private IP address map
Data Network
Component
Network Ranges
Subnet Masks
# of Hosts
BSC 1: SCI-S
172.16.1.2 172.16.1.127
255.255.255.0
126
BSC 1: BS450 /
PP8100
172.16.1.128 172.16.1.254
255.255.255.0
127
BSC 2: SCI-S
172.16.2.2 172.16.2.127
255.255.255.0
126
BSC 2: BS450 /
PP8100
172.16.2.128 172.16.2.254
255.255.255.0
127
BSN Mgmt Ports
172.16.3.2 172.16.3.254
255.255.255.0
253
EMS Server
172.16.21.2 172.16.21.30
255.255.255.224
29
RADIUS Servers
172.16.22.2 172.16.22.30
255.255.255.224
29
Device Mgmt
Terminals
172.16.23.2 172.16.23.30
255.255.255.224
29
Contivity Extranet
Switches
172.16.24.2 172.16.24.30
255.255.255.224
29
Alteon Web Switches
172.16.25.2 172.16.25.30
255.255.255.224
29
BSN IP Pool
172.16.26.2 172.16.26.30
255.255.255.224
29
BSN xLC Ports
172.16.4.2 172.16.20.2
255.255.255.252
1 per Subnet
BLN-2 / PP8600
172.16.11 172.16.25.1
255.255.255.252
1 per Subnet
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Public addressing
Public IP address ranges provide the same type of communication
channels as private addresses. A major difference is that the public
IP addresses are assigned to companies and individuals based on a
regulated process through the Internet Assigned Numbers Authority
(IANA). Public address space must be regulated to prevent network
conflicts where different hosts carry the same address.
Private address space does not require external regulation and can be
applied at will. However, private IP addresses cannot be routed on the
Internet. Companies who apply private addressing schemes require a
method of address translation to gain general Internet access. Network
Address Translation (NAT) and firewall translations are two such methods.
Applying combination IP addressing schemes (private or public) to the
CDMA2000 1X network follows the basic principles of routing. Take care
to gain a thorough understanding of these principles before planning the
data network. Table 6 "IP address ranges" (page 46) lists the IP address
ranges for each IP class. Service Providers must provide the required IP
addresses.
Table 6
IP address ranges
IP class
1st octet range
Default subnet
mask
Number of
networks
Number of
hosts per
network
Class A
1.x.x.x-127.x.x.x
255.0.0.0
127
16 777 214
Class B
128.x.x.x-191.x.x.x
255.255.0.0
16 384
65 534
Class C
192.x.x.x-223.x.x.x
255.255.255.0
2 097 152
254
Class D
&E
Not for general network traffic
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
47
CDMA2000 1X network configuration

This chapter describes various ways that you can configure a CDMA2000
1X network. It is important that you have completed the CDMA2000 1X
planning and engineering stage described in this document and have
contacted your Nortel regional support engineers so that the configuration
that you have chosen meets your needs.
Network topology framework

The final configuration of the CDMA2000 1X network depends on the
type of services that your customer requires; this environment produces
a flexible nature to the CDMA2000 1X network. However, to plan and
engineer a flexible network, you must establish boundaries such that
a systematic approach to network design can be accomplished. For
CDMA2000 1X, these boundaries begin with the Network Topology
Framework (NTF) and progress through the Logical Topology. The
combination of both concepts are explained in subsequent sections. The
goal is to produce an end-to-end solution from many complex choices.
The NTF contains end-to-end clusters that capture the broadest categories
of the CDMA solution. The clusters are listed in Table 7 "Network topology
clusters" (page 47).
Table 7
Network topology clusters
Cluster
Acronym
Major components
Cell Site Cluster
CSC
Metro Cell, BTS
Metro Aggregation Network
MAN
MSC/VLR, BSC/PCF,
PDSN-FA
Internet Peering Point Network
IPPN
POP, Home Agent, Core

Routed IP Network
Network Management
Network
NMN
NOC, Master Servers
Applications and Services

Network
ASN
Applications and Services

Architecture Element
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
48 CDMA2000 1X network configuration
Table 7
Network topology clusters (contd.)
Cluster
Acronym
Major components
Internal Security Network*
ISN
Network Management Firewall
External Security Network*
ESN
Border Gateway Router,

Firewall
CALEA Network*
CALEA
Third-Party, Verint Solution
Figure 11 "Network topology framework" (page 48) shows the composite

NTF and the relationship between each cluster and the logical layers.
The layers are explained in Logical areas (page 54).
Figure 11
Network topology framework
Network categories
The size and complexity of a service providers network determines how
many subnetworks need to be considered for data network components.
All subnetworks need not be co-located and there can be overlap between
the logical layers from subnetwork to subnetwork. For example, the
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Network categories
49
Network Management Network elements can be located in distant Metro

Aggregation Network, Internet Peering Point Networks or both. Three
major network categories are: local, regional, and central.
Local CDMA2000 1X service provider

Local network topology works well for service providers deploying data
in isolated markets requiring limited coverage, local management, and a
single Internet Point of Presence (POP). Applications and services can
be out-sourced.
The network combinations shown in Figure 12 "Local network topology"
(page 50) are for illustration purposes only and can vary from provider to
provider. The network combinations are as follows:
Single Internet Peering Point Network
Single Network Management Network co-located within the Internet

Peering Point Network
Core and Transport equipment provides Internet connectivity through a

Level 3 Regional ISP
Applications and services can be outsourced
Single Metro Aggregation Network co-located within the Internet

Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007

Figure 12
Local network topology
Regional CDMA2000 1X service provider

Regional network topology works well for service providers deploying
data in multiple segmented markets where several related sites can
be physically separated but unified through a single Internet POP and
centralized management. Applications and services can be out-sourced
or hosted by the service provider.
The network combinations shown in Figure 13 "Regional network topology"
provider:
Single Internet Peering Point Network
Single Network Management Network co-located within the Internet

Multiple Metro Aggregation Networks, one of which is located within

the Internet Peering Point Network
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Network categories
51

Level 2 National ISP
Applications and services out-sourced or hosted by the service

provider
Figure 13
Regional network topology
Central CDMA2000 1X service provider

Central network topology works well for service providers deploying data
in multiple segmented markets with multiple Internet POPs and redundant
management at each POP location. Applications and services are hosted
by the service provider.
The network combinations shown in Figure 14 "Central network topology"
provider. The network combinations are as follows:
Multiple Internet Peering Point Networks

Multiple Metro Aggregation Networks, one of which is located within
the Internet Peering Point Network
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Redundant Network Management Networks co-located within the

Internet Peering Point Networks

Level 2 National ISP
Applications and Services hosted by service provider
Figure 14
Central network topology
A sample network plan is shown in Figure 15 "Sample regional network

topology plan" (page 53) and Figure 16 "Sample network management
plan" (page 53).
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Network categories
Figure 15
Sample regional network topology plan
Figure 16
Sample network management plan
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
53
Logical areas
The logical areas explain the interaction of various network components.
The areas are listed in Table 8 "Logical areas" (page 54).
Table 8
Logical areas
Logical areas
Definition
Aggregation area
Multiplexes users into a single flow of

information
Access area
Authenticates users and grants access to the

internal network
Core area
Internal high-capacity switching and

core-routing network
External area
Controls access to the outside world
Security area
Prevents access into protected areas
Apps & Svcs area
Provides the structure for application support

for end-users
Transport area
LAN and long-haul MAN/WAN connection

network
CALEA area
Communications Assistance for Law

Enforcement Assistance Act, implementation
based on J-STD-025
The advantage of using areas is the simplification of the design of large

and complex networks. By understanding the functions of each area, a
network designer can focus on the specific area to be designed rather
than focusing on the functionality of the surrounding areas. In conjunction
with the Network Topology Framework, the Logical areas produce a solid
method of approaching CDMA2000 1X network design. Figure 17 "Logical
topology diagram" (page 55) shows the logical equipment relationships.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Generic physical connectivity
55
Figure 17
Logical topology diagram

The generic physical connectivity diagrams represented in Figure 18
"Generic physical connectivity (switching and routing separated)" (page
56) and Figure 19 "Generic physical connectivity (switching and routing
co-located)" (page 57) show the data-link requirements between the
network nodes. These diagrams are not meant to imply that all of the
equipment is co-located.
Two main types of connectivity are as follows:
Option 1: Switching and Routing Separated

Option 2: Switching and Routing Co-Located
Based on the functionality of the SCI-S card support for ESEL cards,
Option 1 is the best choice.
Each SCI-S card supports up to six ESEL cards, three of which can be
data-capable. In order to eliminate a potential single point of failure, the
10BaseT links to the data network are allocated to different aggregation
nodes. Each SCI-S located in Slot 1 of the SBS shelf is terminated to
Aggregation Node 1 and each SCI-S located in Slot 2 of the SBS shelf is
terminated to Aggregation Node 2. Connectivity to the Core Layer routing
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
engines is treated in a similar manner. The uplinks from Aggregation

Nodes 1 and 2 are separately terminated to each routing engine. Since
each unit Aggregation Node has connectivity to each routing engine, in the
unlikely scenario of a routing engine failure the traffic on the Aggregation
Nodes are handled by the remaining routing engine using Virtual Router
Redundancy Protocol (VRRP).
Option 2 provides a measure of protection for SCI-S support as well.
However, using the same scenario of unlikely routing engine failure, the
SCI-S traffic from the first routing engine is not automatically handled by
the second routing engine as there are no link fan-outs as in the case of
the separate aggregation nodes. Option 2 makes it possible for service
providers to maximize the use of the routing engine port capacity while
adding risk to the SCI-S traffic handling.
Figure 20 "SCI-S aggregation strategic wiring: SBS frames and 24 port
data switches" (page 57) through Figure 23 "SCI-S aggregation strategic
wiring: SBS frames and PP8100-6 Edge switches" (page 59) are examples
of Strategic Wiring Methods for Option 1. Option 2 wiring excludes the
aggregation nodes. More information can be obtained from Data Network
Engineering Groups.
Figure 18
Generic physical connectivity (switching and routing separated)
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007

Figure 19
Generic physical connectivity (switching and routing co-located)
Figure 20
SCI-S aggregation strategic wiring: SBS frames and 24 port data switches
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
57

Figure 21
SCI-S aggregation strategic wiring: SBS frames 1,2: 24 port data switch 1,2
Figure 22
SCI-S aggregation strategic wiring: SBS frames 3, 4: 24 port data switch 1,2
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Figure 23
SCI-S aggregation strategic wiring: SBS frames and PP8100-6 Edge switches
CDMA2000 1X network connections

The link between the radio network and the data network is 10BaseT
Ethernet. This connection is located on the SCI-S card. Each SBS shelf
contains two SCI-S cards. There can be up to 12 SCI-S cards per SBS
frame. Up to 144 10BaseT connections per BSC need to be terminated to
the data network. Figure 24 "Number of SCI-S aggregation links per MSC"
(page 59) summarizes the number of SCI-S Aggregation Links per MSC.
Figure 24
Number of SCI-S aggregation links per MSC
ATTENTION
The number of supported SBS shelves increases with upgrades to MTX and NBSS software.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Since each SCI-S controls half of the SBS shelf, it is prudent to build the
aggregation infrastructure to eliminate potential full-shelf downtime. The
aggregation nodes provide relief of a potential single point of failure.
The recommendations are as follows:
Each SCI-S in slot 1 goes to aggregation node 1

Each SCI-S in slot 2 goes to aggregation node 2
The Nortel Multiservice Switch 8100 Edge switch is an excellent choice

that creates the maximum support through redundant power supplies,
stackable or modular units for expansion, and MLT uplink capabilities.
Switches are more savvy than hubs for LAN connectivity. Switches
perform network segmentation and isolation functions through the creation
of Virtual Local Area (VLAN) and broadcast domains. Latency times
associated with other network devices, such as hubs, are minimized
through the use of switches. Devices connected to switches can be on
different subnets through VLAN configurations. IP address assignments
are not required for the switch itself, but are helpful. The benefits gained
when assigning IP addresses to each switch for troubleshooting the
network outweigh the cost of a single host IP address per stack.
Nortel Multiservice Switch 8100 Edge switch

Nortel Multiservice Switch 8100 Series routing switches (Edge switches),
shown in Figure 25 "Nortel Multiservice Switch 8100 Edge switch" (page
61), are part of the Nortel next generation networking platforms. The
series comes in 6-slot and 10-slot chassis with the following interface
capabilities: 10/100/1000 Ethernet, Layer 2/3 Switching, and IP. The units
have redundant power supplies. All components are hot-swappable.
The backplane scales up to 50 Gb/s switching capacity with a Layer 2
routing throughput of 24 million packets per second and with less than 10
microseconds of latency. The chassis maximum port density is 192 for
the 6-slot unit and 384 for the 10-slot unit. Port capacity is impacted by
considerations like CALEA (Legal Intercept), Core Layer connectivity, and
spares. The 10-slot unit is shown below. This aggregation node type is
ideal for medium-to-large, compact networks.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007

Figure 25
Nortel Multiservice Switch 8100 Edge switch
Data network cabling

The glue that ties the data network together are the cables between the
network components. Two main types of cables appear in the network:
Ethernet and Fiber. For Ethernet cables, American National Standards
Institute / Electronic Industries Association (ANSI/EIA) Standard 568 is
one of several standards that specifies categories (CAT) of twisted-pair
cabling systems by the data rates that they can sustain. The specifications
describe the cable material as well as the types of connectors and junction
blocks to be used in order to conform to a category. The categories are
summarized in Table 9 "CAT summary" (page 61).
Table 9
CAT summary
Category
Maximum data rate
Usual application
CAT 1
Less than 1 Mb/s
Analog voice (POTS), ISDN
CAT 2
Up to 4 Mb/s
IBM cabling system for Token Ring
CAT 3
Up to 16 Mb/s
Voice and data on 10BaseT Ethernet
CAT 4
Up to 20 Mb/s
16 Mb/s Token Ring, low usage
CAT 5
Up to 100 Mb/s
100 Mb/s TPDDI, 155 ATM
CAT 5e
Up to 1 Gb/s
Voice and data on 1000BaseT

Ethernet
CAT 6
Up to 1 Gb/s
Voice and data on 1000BaseT

Ethernet
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
10BaseT Ethernet
10BaseT means 10 megabits per second transmission rate baseband
signaling across twisted-pair (T) wires. The cable distance is limited to 100
meters.
Additional 10Base media types are as follows:
10BASE-2-Thin wire coaxial cable with a maximum segment length of

185 meters (200 m)
10BASE-5-Thick wire coaxial cable with a maximum segment length of

500 meters
10BASE-F-Optical Fiber Cable

10BASE-36-Broadband coaxial cable carrying multiple baseband
channels for a maximum length of 3 600 meters
100BaseT Ethernet
100BaseT means 100 megabits per second transmission rate baseband
signaling across twisted-pair (T) wires. The cable distance is limited to 100
meters.
Additional 100Base media types are as follows:
100BASE-T4-Four pairs of telephone twisted pair wire

100BASE-TX-Two pairs of data grade twisted-pair wire
100BASE-FX-A two-strand optical fiber cable
Though CAT3 wiring configurations can be used for the 10BaseT SCI-S
links, for wiring consistency. Nortel recommends using CAT5 cables for
both 10BaseT and 100BaseT connections.
1000BaseT Ethernet
1000BaseT is a specification for Gigabit Ethernet over copper wire (IEEE
Std. 802.3ab). The standard defines 1 Gigabites per second data transfer
over distances of up to 100 meters using 4 pairs of CAT-5 balanced
copper cabling and a 5-level coding scheme.
Fiber optic cables

Optical fibers transmit information as light pulses along a glass or plastic
wire. These fibers carry more information than conventional copper wire
and are generally not subject to electromagnetic interference and the need
to retransmit signals.
As is the case with CAT cables, fiber optic cables are rated according to
Optical Carrier levels or OCx. The levels are summarized in Table 10
"OCx summary" (page 63).
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
OC-3 can be used to interconnect routers and IP switches in the packet

core network. Single-Mode (SM) and Multi-Mode (MM) fiber options exist
for many data networking devices. Single-Mode options are for long
distances, up to 28 km. Multi-Mode options are for short distances, up to 2
km.
Table 10
OCx summary
OC Level
Maximum Data Rate
Usual Application
OC-1
51.84 Mb/s -> 51 Mb/s
Small ISP-to-Internet infrastructure
OC-2
103.68 Mb/s -> 103 Mb/s
Large LAN, Low Usage
OC-3
155.52 Mb/s -> 155 Mb/s
Large company or Internet backbone
OC-12
622.08 Mb/s -> 622 Mb/s
Internet backbone
OC-48
2.488 Gb/s-> 2.5 Gb/s
Internet backbone
OC-192
9.953 Gb/s -> 10 Gb/s
Backbone
CAT5 straight-through cable pin-out

The connector commonly used for Ethernet LAN links is the RJ-45
(Registered Jack-45) connector. The connector is shown in Figure 26
"RJ-45 connector" (page 63).
Figure 26
RJ-45 connector
When wiring two dissimilar interfaces such as a hub and a PC,

a straight-through cable must be used. The color code for CAT5
straight-through cables depends on whether the 568A or 568B scheme
is being used. The only real difference between the two is that the
White/Orange-Orange/White and White/Green-Green/White pairs are
swapped. Figure 27 "568A and 568B color code" (page 64) shows the two
configurations.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007

Figure 27
568A and 568B color code
The easiest way to make straight-through cables is to make sure that

both ends are the same (see Figure 28 "Straight-through cable pin-out
diagrams" (page 64)). Apply the same standard, 568A or 568B, throughout
the network. Also, ensure that the RJ-45 connector is being viewed from
the same angle as the color code is being applied.
Figure 28
Straight-through cable pin-out diagrams
CAT5 cross-over cable pin-out

When wiring two similar interfaces such as PC-to-PC or router-to-router,
cross-over cables must be used. The color code for CAT5
cross-over cables depends on whether the 568A or 568B scheme
is being used. The only real difference between the two is that the
White/Orange-Orange/White and White/Green-Green/White pairs are
swapped. Figure 29 "Cross-over cable pin-out" (page 65) shows the two
configurations.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007

Figure 29
Cross-over cable pin-out
The easiest way to make cross-over cables is to make sure that both ends
are not the same. Apply the same standard, 568A or 568B, throughout the
network. Also, ensure that the RJ-45 connector is being viewed from the
same angle as the color code is being applied.
Fiber optic cable terminators

Several types of Optical Carrier (OCx) terminators are available. For the
components in these data networks, the connectors shown in Table 11
"OCx terminator connectors" (page 65) are typically used.
Table 11
OCx terminator connectors
Type
Definition
SC
Stick and Click
ST
Stick and Twist
MT-RJ
MT-Registered Jack, 50% smaller than SC connector
The Nortel Multiservice Switch 8600 Routing Switch OC-3 ports have
MT-RJ terminators. See Figure 30 "Fiber optic cable SC connector
diagram" (page 66).
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007

Figure 30
Fiber optic cable SC connector diagram
CDMA2000 1X routing engines

Routers are used to interconnect LANs, MANs, and WANs. Routers
provide traffic control and filtering functions over mesh technologies. Media
conversion between networks such as Ethernet, token ring, and Fiber
Distributed Data Interface (FDDI) are performed. Some routers provide
compression and prioritization for WAN bandwidth optimization. Each
interface on a router requires a unique subnet.
Routing switches combine the functionality of switches and routers to
include OSI Layers 2 and 3 into one network entity. IP multicast, security,
and Quality of Service (QoS) are some of the advantages of routing
switches. IP address assignments adhere to the rules that apply to both
switches and routers for respective modules on the routing switch platform.
As part of the core network build-out, the routing engines listed below
provide the best-in-class interface capabilities and performance:
Nortel Ethernet Routing Switch 8600 (Enterprise)

Nortel Multiservice Switch 8600 carrier routing switch
Alteon Web switch module
Alteon 180 and ACE Director Series Web switches
CDMA2000 1X server architectures

Without servers to provide configuration, maintenance, upgrades, and
monitoring, the data network does not function. Two types of servers are
absolutely critical to the operation of CDMA 3G: PDSN/EMS Servers and
RADIUS servers. Each of the servers are listed in this section.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
CDMA2000 1X server architectures
67
For EMS server/client information, see Nortel CDMA2000 1X

Fundamentals, (NN20000-129).
RADIUS servers
RADIUS is an industry-leading product designed to deliver authentication,
authorization, accounting, and service delivery to service providers.
RADIUS authenticates subscribers when access to services is required.
Also, Usage Accounting Data (UDR) for statistics and billing are collected
through RADIUS. Figure 31 "RADIUS server architecture" (page 68) shows
the RADIUS architecture.
Directory server
The functions of the directory server are as follows:
Sun/Netscape iPlanet
Central data store for customer organizations and RADIUS profiles
RADIUS and Management Console communicates through Light
Weight Directory Access Protocol (LDAP)
Database server
The functions of the database server are as follows:
Central Oracle database for IP addresses and Domain Name System

(DNS) information
No built-in redundancy since data is propagated and stored locally
Application/Web logic server

The functions of the application/Web logic server are as follows:
Processes user requests for display of information from repositories

Passes input information to repositories for storage
AAA server
The functions of the AAA server are as follows:
Authenticates subscribers for access to services

Authorizes subscribers for allowed service levels
Communicates with directory through LDAP
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Management console
The functions of the management console are as follows:
GUI used by administrators to view and manage IP service information

Communicates with directory through LDAP
Figure 31 "RADIUS server architecture" (page 68) illustrates the RADIUS

server architecture.
Figure 31
RADIUS server architecture
Closed R-P interface fault detection

Fault detection is required to quickly trigger fault recovery and to ensure
new call attempts are not continuously send into a black hole. The ability
of Packet Data Function (PCF) or Packet Control Unit (PCU) to effectively
deal with PDSN failure conditions is implementation specific. Therefore
fault detection can be achieved in different ways.
The SBS PCU monitors the status of the PDSNs using two complementary
methods: L2TP hellos and Internet Control Message Protocol (ICMP)
pings. After a L2TP tunnel is established, a keep-alive mechanism is
employed by the Selector Bank Subsystem (SBS) PCU to detect extended
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Open R-P interface fault detection
69
periods of inactivity across the L2TP Radio Network - PDSN (R-P)

tunnel. This is accomplished by sending L2TP Hello control messages
after a specified period of time has elapsed since the last data or control
message was received on the tunnel. Hello messages ensure that a
connectivity failure between the SBS PCU and the PDSN is detected at
both ends of the R-P tunnel. When the SBS PCU has not received any
message (data or control) from the PDSN for a period varying from 30
to 60 seconds (referred as the wake-up timer), the SBS PCU sends a
L2TP hello message across the tunnel. As with all control messages, the
PDSN returns either a ZLB ACK or an (unrelated) L2TP control message
piggybacking the necessary acknowledgement information. If the PDSN is
unreachable (no responses), the SBS PCU continues transmitting hello
messages according to the setting of the L2TP attributes under the PCU
MO. The InitialAckTimer specifies the initial number of seconds
for acknowledging a L2TP control message and can be set between 1
to 5 seconds (inclusive). It is started when the first Hello is sent, and
stopped when the acknowledgement is received. The NumberofRetrys
determines the number of hello retransmissions before cleaning up the
tunnel and can be set between 1 to 10 retries (inclusive). For a setting of
three retransmissions and one second for the initial acknowledge timer, it
takes between 38 and 68 seconds (including the wake-up timer of 30 to 60
seconds) for the SBS PCU to consider the PDSN out-of service. When
this occurs, the SBS creates a fault event report and an alarm is raised on
the BSSM (indicating which PDSN is unavailable). The PCU releases the
tunnel and initiate the teardown of dormant and active data calls across
the faulty tunnel.
If connectivity to a PDSN fails, the SBS PCU marks it as unavailable.
New R-P connections requests are directed to available PDSNs in the
PDSN IP Address Array. The unavailable PDSN is excluded from the
PDSN selection process. If the IMSH hash algorithm is configured on the
SBS PCU, the PCU selects other PDSN(s) by performing the modulo hash
function over the remaining PDSNs. After releasing all Radio Network
PDSN (R-P) resources associated with an unreachable PDSN, the SBS
PCU continuously monitor the status of the PDSN by sending ICMP echo
request (ping) messages every 30 seconds. The SBS PCU automatically
begins the re-establishment of the L2TP tunnel after the PDSN responds
with a single ICMP reply message.

Fault detection is required to quickly trigger fault recovery and to ensure
new call attempts are not continuously send into a black hole. If a R-P
connection setup fails with the selected PDSN IP address, the CPDS PCU
attempts to establish the R-P connection with the next available primary
PDSN IP address on the list. This is the normal process as described in
the standards. However, the standard selection process also implies that
a group of mobiles always attempt to connect to the same PDSN even
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
thought it is not responding. As in the case of the SBS PCU, the CDMA
Packet Data Subsystem (CPDS) PCU periodically checks the health of the
PCU-PDSN IP connectivity and blacklist unreachable PDSN(s). For the
Open R-P interface, the CPDS PCU uses ICMP for determining the status
of the IP reachability between the CPDS PCU and the PDSN. The CPDS
PCU also triggers loss of connectivity when the PDSN is not responding
to A11 registration messages.
Upon activation, each CPDS PCU verifies IP connectivity with the
non-dummy PDSN(s) by sending ICMP echo (ping) request messages.
If connectivity succeeds, the PCU marks the PDSN as available. If
connectivity to a PDSN fails, the PCU marks it as unavailable in the pool
in which it is configured. R-P connections requests are only directed to
available PDSNs in the pools. Unavailable PDSNs are excluded from
the PDSN selection process. The result of the ICMP check is stored in the
PDSN status table. The period of the health check is configurable through
an attribute listed in the Open R-P parameters. The ICMPPingDelay
attribute controls the delay between PDSN ping cycles. A PDSN ping cycle
is defined as a set of pings sent sequentially to all non-dummy PDSNs
across both pools. The default is 120 seconds with a valid range from
60 to 65, 535 seconds. Note that the CPDS PCU continuously pings all
PDSNs (available and unavailable) regardless of the A10/A11 activity.
After a PDSN failure, the CPDS PCU declares the PDSN is unavailable
after one ping cycle assuming that A11 registration messages are not send
by the PCU during this period. If an A11-registration message (new calls,
handoffs, refreshments and transfers of airlink records) is sent to a faulty
PDSN before the ping cycle has detected the failure, the PCU marks the
PDSN as unavailable and blacklist it from the selection process. This is
done after a number of A11-registration retransmissions.
ATTENTION
Nortel recommends keeping the default ping cycle of 120 seconds on the CPDS PCUs and favors
fault detection through A11 signaling. Bringing back a PDSN online does not require immediate
responses by the PCUs. However, this action eventually changes the PDSN selection process and
can result in an increased number of inter-PCU inter- PDSN handoffs.
After detecting connectivity or A11 signaling failure, the faulty PDSN is

immediately blacklisted and excluded from the IMSI hash selection. As
stated in the standards, new calls that were normally directed towards the
faulty PDSN are now send to the next available PDSN on the pool until IP
connectivity is re-established with the original PDSN. Note that this can
create uneven distribution across the remaining PDSNs especially when
the primary pools contain three or more IP addresses.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
71
Existing calls to the faulty PDSN cannot be immediately released by the

CPDS PCU. The connections are released when the PDSN does not
respond to A11 registration messages. More specifically, the connection is
released after the PDSN does not acknowledge refreshment or does not
accept the reception of an Active Start or Active Stop accounting records.
If the mobile is dormant and stays dormant during the PDSN failure, the
connection is released in less than 30 minutes (with the default A10
Connection Lifetime timer). If the mobile is active during the PDSN failure,
the connection is released when the subscriber goes dormant, that is when
the PCU is attempting to send an Active Stop airlink record to the PDSN. If
the PCU releases the call due to PDSN not responding to A11 registration
messages, the radio link resources for this call are also released.
After releasing all R-P and radio resources associated for calls associated
with the faulty PDSN, the CPDS PCU continuously monitors the status
of the available and unavailable PDSNs by sending ICMP echo request
(pings) according to the configured ping cycle. The CPDS PCU clears the
alarm and automatically changes the status to available when it receives
two successful ICMP echo reply messages (two ping cycles) from the
PDSN plus a waiting period of 10 seconds.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
73
Appendix
CDMA2000 1X hardware and nodes
The CDMA2000 1X channel element module
The CDMA2000 1X Channel Element Module (XCEM) is the CDMA2000
1X version of the Channel Element Module (CEM) of the Metro Cell BTS.
The XCEM performs IS-2000 baseband signal processing and implements
the IS-2000 channel structure.
A more powerful CEM is required in CDMA2000 1X because the IS-2000
physical layer is more complicated than its IS-95 equivalent and takes
more processing power to implement.
Channel element
The Channel Element (CE) is the unit of functionality within the XCEM.
Each voice call or leg of a voice call in soft handoff uses one channel
element. Each overhead channel also requires a separate channel
element.
In a data call, the number of required channel elements depends on the
data rate. For example, at 153.6 kb/s (16x9.6 kb/s), a data call requires
16 channel elements.
Capacity
The XCEM is available with two different channel element densities. The
available variants of the XCEM are:
an XCEM with 32 channel elements

an XCEM with 64 channel elements
The XCEM provides approximately twice as much CE capacity on the

forward link as on the reverse link. For example, a 64-CE XCEM has 64
reverse resources and approximately 128 forward resources.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
74 CDMA2000 1X hardware and nodes
IS-95 compatibility
The XCEM provides the same support for IS-95 calls as the existing
module, or Classic Channel Element Module (CCEM). As a result, there is
no need to have both CCEM and XCEM in a 3G Metro Cell.
However, if a Metro Cell carries a large amount of 2G traffic, the carrier
has the option to leave the CCEM units in place to process IS-95 calls,
and to deploy only enough XCEM units to support the CDMA2000 1X
traffic. Both the XCEM and the CCEM can co-exist in the same BTS.
The only situation when a carrier must deploy a 2G CEM card to support
IS-95 traffic is for an extended CDMA cell with a radius greater than 150
km. In this situation, the extended cell must contain both XCEM and
Extended CEM (ECEM) cards.
XCEM software
The XCEM and the CCEM run different software loads. Like the CCEM
software, the XCEM software is available for in-service download. The
Digital Control Group (DCG) managed object contains the application
ID and the loader ID of the software that is needed to run the XCEM or
CCEM.
ATTENTION
Earlier versions of the NBSS software stored the loader ID and application ID for the CEM software
in the CEM MO. In NBSS 12.1, this information is available in the DCG MO instead of the CEM
MO.
Automatic detection of card type

A CEM MO automatically detects the hardware type of the module to
which it corresponds. When the MO initializes, it checks the hardware type
and determines whether the module is a CCEM or XCEM.
This functionality simplifies the process to upgrade a CEM. After a
technician replaces and initializes a CEM, the card is ready to provide
service. No additional manual intervention is necessary.
ATTENTION
Specific NBSS and MTX software prerequisites are required to enable the operation of the XCEM
card.

The Selector Common Interface-Supreme (SCI-S) card is an improved
version of the selector common interface card. Like the original
NTGB08BA SCI card, the NTGB08FA SCI-S card terminates T1 trunks
to and from the DMS-MTX switch and distributes DS0 channels to the
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
75
Enhanced Selector (ESEL) cards. Unlike the NTGB80BA SCI card, the
SCI-S card has a 10Base-T Ethernet interface, and it supports both T1
and E1 trunking.
ATTENTION
The NTGB08FA card supports E1 and T1 trunking in software release NBSS 12.1.
The CDMA2000 1X BSC uses the Ethernet port of the SCI-S card to
connect the BSC to the carrier IP network. The SCI-S card software
implements Packet Control Unit (PCU) functionality, which controls the
flow of packets into the packet network.
Compatibility issues
Carriers that deploy fixed wireless access with a Nortel BSC (V5.2) have
NTGB08DA SCI-S cards. These cards are different from the NTGB08FA
SCI-S cards required for CDMA2000 1X. The NTGB08DA SCI-S card
supports only E1 trunks and is not compatible with the Nortel CDMA2000
1X product.
In NBSS 12.1, the CDMA2000 1X product is not available in a fixed
wireless configuration.
SCI-S support for 3G data

The CDMA2000 1X software that runs on the SCI-S card performs the
following tasks in support of packet data:
provides resource control functionality within the packet session
encapsulates Point-to-Point Protocol (PPP) frames into closed R-P

interface frames and tunnels them through to the PDSN
routes packets from the mobile to the PDSN, and from the PDSN to
the mobile
exchanges signaling with software running on the selector elements

sets up and tears down closed radio-packet (R-P) interface sessions
at the request of the ESEL card
SCI and 3G voice-only networks

If an Enhanced Selector Bank Subsystem (ESBS) shelf carries only
CDMA2000 1X voice traffic, but not packet data traffic, the ESBS shelf
can combine ESEL cards with the NTGB08BA SCI card instead of the
SCI-S. However, the preferred configuration is to use the SCI-S card, as
this provides the carrier with the capability for quick deployment of packet
data support into the BSC.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
The SCI-S card can coexist in the same shelf with ESEL cards, but not
with first generation selector cards. The SCI-S card cannot coexist with
earlier OEM SCI-S cards or with SCI cards.
Enhanced selector card

The Enhanced Selector (ESEL) card is required to deploy a CDMA2000
1X network. The complexity of the CDMA2000 1X air interface places
demands on the selector card that require the increased processing power
of the ESEL card.
In CDMA2000 1X, as in IS-95, the ESEL is responsible for the following
components:
power control
vocoding and echo cancellation
selection of the best frame for handoffs
implementation of service options
CDMA2000 1X adds two additional responsibilities for the BSC:
support of data call throughput

management of the Radio Link Protocol (RLP)
Selector upgrades
The ESEL is a requirement for the Enhanced Variable Rate Codec
(EVRC), an improved vocoding standard that allows near-wireline voice
quality on an 8-kbit/s data stream. Consequently, many carriers already
have ESEL cards installed in their base station controllers.
EVRC-B is not supported on ESEL.
Mobile switching center

In the CDMA2000 1X product, either the DMS-MTX or the DMS-100W
digital switching center serves as the CDMA2000 1X MSC. The Mobile
Switching Center (MSC) provides a point of entry into the Public Switched
Telephone Network (PSTN) for voice trunks and IS-41 connections. It also
performs billing, call routing, and diagnostic record keeping in a central
location.
Upgrade to FLIS
The increased level of signaling traffic that accompanies the
implementation of CDMA2000 1X requires that some carriers upgrade their
Link Peripheral Processors (LPP) to the Fiberized Link Interface Shelf
(FLIS). The number of cell-carriers that mark the threshold for this upgrade
requirement depends on the network configuration and the traffic model.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Packet data serving node
77
Upgrade to XA-Core
Some central offices must be upgraded from the DMS Computing Module
(CM) to XA-Core to get the maximum improvement in capacity available
with CDMA2000 1X. The network configuration and call model of a
DMS-MTX switch determines if it requires an XA-Core upgrade. The
upgrade requirement applies in particular to mobile switching centers that
are operating at or near their maximum CM capacity.
The XA-Core is a multi-processor computing platform that supplies the
functionality that the CM and System Load Module (SLM) previously
provided. XA-Core removes processing power at the MSC as a bottleneck
in system capacity because it is a scalable solution for the MSC
processing hardware.
ATTENTION
Carriers that choose to deploy an XA-Core into a DMS-MTX or DMS-100W office that runs the
MTX10 load must deploy the XA-Core 3+1 configuration (NTLX02CA).
For information about the procedures required to upgrade to the XA-Core,

refer to XA-Core Cutover Software Delivery, (297-8991-307).
Packet data serving node

The Packet Data Serving Node (PDSN) is the wireless packet data
gateway into an external packet data network.
The PDSN performs the following functions:
manages the Radio-Packet (R-P) interface that connects the BSC to

the carriers IP transport network
provides routing and packet management services
collects packet billing data
applies IP services to IP connections

implements Mobile IP as a Foreign Agent (FA)
implements Mobile IP as a Home Agent
authenticates packet connections or serves as a client to an

authentication server
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Standard
The Third Generation Partnership Project for North American CDMA
(3GPP2) defines a packet routing function to complement the CDMA2000
1X wireless standard. The PDSN in the CDMA2000 1X product
corresponds to this packet routing function. Refer to 3GPP2 TSG-P,
Wireless IP Network Standard, for more details.
Components
The Nortel CDMA PDSN-FA consists of the following components:
the Nortel PDSN 1600 hardware platform providing packet forwarding

and routing
the PDSN Operating System providing service scalability and

extensibility
the Element Management System (EMS) providing policy and

subscriber provisioning
The Nortel CDMA PDSN is an NEBS-compliant platform designed for

operation in demanding central office and Point-of-Presence (PoP)
environments. The chassis itself supports 16 vertically aligned card slots
in the front and 48 vertical slots in the rear of the chassis that contain
switching, control, service processing, and input/output modules.
The Nortel implementation of basic Mobile IP provides functionality for a
Foreign Agent (FA) integrated with the PDSN, according to the IS-835
standard, and a stand-alone Home Agent, also implemented in the PDSN.
Physical connectivity
A Line Card (LC) on the PDSN connects into the private packet network
that the carrier provisions for 3G wireless traffic. Packets travel from the
PDSN through the private packet network to the SCI-S card in the BSC.
Packets from the subscriber return from the BSC to the line card.
The PDSN can use the same line card for traffic on both the R-P interface
(to and from the BSC) and the Pi interface (to and from the Internet), but it
is generally advisable to distribute this traffic between two line cards that
provide redundancy for these traffic links.
Client-server connectivity
The PDSN uses the managed IP network to provide connectivity to the
following services:
the RADIUS AAA servers for authentication and accounting of data

sessions
the Element Management System (EMS) server

the mobile IP Home Agent
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Home Agent
79
The PDSN uses UDP or TCP running on IP to exchange packets with

the servers that host these services. Depending on the network model,
a data subscriber can have a Home Agent or a AAA server that resides
on another network. The routers in the managed IP network must have
correct routing table entries so that the PDSN can communicate with
servers on other networks, and data users can roam from one regional
network to another.
R-P interface support

The PDSN software supports two variants of the R-P interface:
the closed R-P interface is a proprietary implementation of the R-P

interface that connects the PDSN to the Nortel BSC in conformance
with the requirements of IS-835.
the open R-P interface implements the open A10/A11 interface. The
open interface allows the Nortel PDSN to connect to any Packet
Control Function (PCF) in a radio network that complies with the open
standard.
See Subnet A: R-P interface (page 41), for more information.
IP services
The PDSN can provide a rich suite of IP services to Mobile IP subscribers.
As a rule, the PDSN can apply IP services whenever it processes the
IP packets of a subscriber data session. In some network models, the
PDSN is unable to apply some IP services, or any IP services at all. For
a complete description of which IP services are available at the PDSN
in a particular network access model, see the detailed discussion in the
CDMA PDSN 16000 System Administration and Configuration Guide,
(NN20000-197).
Home Agent
The Nortel Home Agent for CDMA2000 is part of the CDMA2000 1X
solution. It exists within the CDMA2000 1X network as a stand-alone
node. The Home Agent node provides Home Agent services for mobile IP
subscribers within a CDMA2000 network and is compliant with the IS-835
standard for wireless IP networks.
The Home Agent keeps track of the location of packet data subscribers as
they move from one location to another in a CDMA2000 network.
Hardware platform
Like the PDSN, the Home Agent resides on the Nortel PDSN 1600
platform.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
The chassis and cards of the Home Agent are the same as the PDSN. For
further information on the hardware components of the Nortel PDSN 1600,
see Packet data serving node (page 77).
Software load
The Nortel Mobile IP Home Agent runs as a separate service within the
same software load as the PDSN-FA.
OAM platform
The Home Agent can use the Element Management System (EMS)
for configuration management, datafill, and event reporting. For more
information, see Element Management System (EMS) (page 81).
Home Agent IP services

Like the PDSN, the Home Agent can provide a rich suite of IP services to
Mobile IP subscribers.
As a rule, the Home Agent can apply IP services whenever it processes
the IP packets of a subscriber data session. In some network models, the
Home Agent is unable to apply some IP services, or any IP services at all.
For a complete description of which IP services are available at the Home
Agent in a particular network access model, see the detailed discussion in
the CDMA PDSN 16000 System Administration and Configuration Guide,
(NN20000-197).
PDSN and Home Agent cards

The PDSN contains four types of modules. Both the PDSN and Home
Agent contain these modules. Every module is equipped with operational
status indicators. All modules can be hot-swapped and are capable of
redundant operation.
The generic module types of the PDSN and Home Agent are as follows:
Switch Processor Card (SPC)

Packet Accelerator Card (PAC)
Line Card - Switch Processor Input/Output Card (SPIO)
Redundancy Crossbar Card (RCC)
ATTENTION
The PDSN and Home Agent in a CDMA2000 1X network support only some variants of these card
types, as indicated below.
Packet Accelerator card

The Packet Accelerator Card (PAC) provides the packet processing and
forwarding capabilities within the system.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Element Management System (EMS)
81
Switch Processor card

The Switch Processor Card (SPC) serves as the primary controller for
the system. It is responsible for initializing the entire system, loading the
softwares configuration image, monitoring chassis cards, and it provides
the highest level of redundancy hierarchy.
Redundancy Crossbar card

The Redundancy Crossbar Card (RCC) utilizes redundant 5 Gbps links
ensuring connectivity between rear-mounted Ethernet 10/100 or Ethernet
1000 line cards (LCs), and every PAC in the system.
Line cards
The Switch Processor I/O (SPIO) card provides connectivity for local and
remote management and central office (CO) alarming.
For the PDSN and Home Agent:
the supported line card is an eight-port Fast Ethernet card. The

ports of the Fast Ethernet line card operate at either 10BASE-T or
100BASE-T, and automatically detect the line rate of the network
connection
the Ethernet 1000 line card, commonly referred to as the Gigabit

Ethernet Line Card (GELC), provides for network connectivity. The
GELC has one port that can be ordered in the 1000 SX and 1000
Ethernet Copper forms.
Element Management System (EMS)

The Web Element Management Server (EMS) is a Java-based software
application for the remote management and monitoring of system
network elements. This software uses client-server architecture to provide
complete FCAPS (Faults, Configuration, Administration, Provisioning,
Security) management operations.
EMS users
The EMS can have any number of users with any combination of privileges
that are deemed necessary by the SuperUser. The SuperUser account is
the only account that pre-exists in the software. Other necessary accounts
can be created using the SuperUser account.
EMS architecture
The EMS consists of an EMS server and one or more clients. An
EMS server consists of several components within the Sun server. It
contains the EMS Application software, the Apache Web Server, and the
PostgreSQL Database Engine. These three components are used to
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
provide the EMS functionality, the web interface, and the database engine
needed to allow the EMS server to provision and monitor any number of
PDSN devices.
EMS client
The EMS client provides a user-friendly, graphical user interface into the
management server. The EMS client is available for several platforms:
Microsoft Windows Operating System, Sun, other UNIX, and Linux.
A technician can use the EMS client GUI to access the tools and services
of the EMS to manage, monitor, or provision any of the PDSN and home
agent nodes to which the EMS server connects.
Server platform
The EMS server software runs on a dedicated Sun workstation.
Serving areas and regions

One EMS server can administer multiple PDSN and home agent nodes.
A carrier can divide the PDSNs contained in the network by topology maps
on the EMS. Each map can contain several PDSN devices. The carrier
can choose to have only one map. If the limit is not exceeded, that map
can contain all the network PDSNs, FAs, and HAs, see Nortel PDSN 1600
Element Manager Guide, (NN20000-205).
RADIUS server
A CDMA2000 1X network requires an Authentication, Authorization,
and Accounting (AAA) server to approve or deny access to the packet
data network. The AAA server implements the Remote Access Dial-In
User Service (RADIUS) standards for authentication and for packet data
accounting, as described in RFC 2138 and RFC 2139.
Nortel recommends that operating companies use the Bridgewater
RADIUS server to implement the AAA functionality.
Exception
A service provider has the option to omit Password Authentication Protocol
(PAP) or Challenge Handshake Authentication Protocol (CHAP) during
PPP setup. In this case, the PDSN grants access to the packet network to
any subscriber that has a Mobile Station Identification (MSID) that matches
the range in one of the MSID templates in the SCS.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Platform
Each RADIUS server requires a dedicated Sun* workstation. The number
of RADIUS servers that a network requires depends on the desired level of
redundancy, the number of subscribers on the network, the call model, and
the number of processors in the server. It is advisable to have separate
RADIUS servers for accounting and authentication.
Redundancy
To provide redundancy for the RADIUS function, Policy Services can
provide the same subscriber information to several RADIUS servers.
RADIUS redundancy requires that the PDSN datafill contain a list of
possible RADIUS servers that the PDSN RADIUS client can use. In the
event of the failure of the preferred RADIUS server, the PDSN can send
an authentication request to the next server in the list.
RADIUS database
A RADIUS server retrieves information about subscribers from a directory.
In the CDMA2000 1X product, this is normally an LDAP database residing
on a Metasolv directory server.
External OAM gateway

The external OAM gateway allows remote access to a CDMA2000
1X network. It allows external support staff to connect to devices in a
CDMA2000 1X network by establishing secure tunnels between a remote
site and the gateway device. In essence, this creates a Virtual Private
Network (VPN) that connects the operating company to the equipment
vendor. The gateway device selectively gives IP-based applications that
runs on external computers access to the CDMA2000 1X network in order
to perform Operations, Administration, and Maintenance (OAM) functions.
Nortel requires the operating company to deploy the Contivity 600 VPN
switch as an external OAM gateway to ensure premium network and
technical support from Nortel teams, when needed.
Purpose
The additional complexity of packet data networking places means that
the requirements for external support access to a CDMA2000 1X network
are more stringent than for a second-generation CDMA network. There
are more types of nodes to support, Graphical User Interfaces (GUI) are
more common, and troubleshooting network problems often requires
simultaneous access to multiple platforms with multiple toolkits.
The Contivity
The Contivity is a secure network access device. It uses encrypted packet
tunnels to give external users secure access to a private network across
an insecure medium.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
The Contivity family of products has an external access client that runs on
generic personal computers. Using the Contivity client, an external user
can log on to the private network, establish a secure tunnel, and establish
IP-based application sessions with devices within the private network. All
communications between the client and the VPN switch are secured with
IPSec and Data Encryption Standard (DES) or triple-DES, depending on
the market where the Contivity is purchased.
Optional high-capacity solution

If the operating company expects very heavy traffic through its external
OAM gateway, it can optionally deploy the Contivity 1600 VPN switch in
place of a Contivity 1100.
This option is not necessary in most networks. The Contivity 1100
supports a maximum of 30 simultaneous VPN tunnels.
Security
The operating company has complete control over the Contivity device.
External users can only create tunnels to the Contivity device with proper
identification and with the permission of the operating company. The
operating company can physically disconnect CDMA2000 1X OAM
network from the external network at any time by disconnecting power
from the external OAM gateway.
The Contivity VPN switch has a built-in, state-aware firewall that provides
industry standard protection against unwanted traffic. The operating
company can configure this firewall to limit the types of applications
that can access their network and to restrict the devices with which
these applications can communicate. The operating company can also
differentiate between users or classes of users by the use of firewall
policies.
Supporting devices
Nortel recommends that the operating company configure a RADIUS
server within the managed IP network to authenticate external access
through the external OAM gateway. The Contivity has the capability to
authenticate users on a local LDAP directory, but the external RADIUS
device is necessary to allow the authentication of users by group identity
as well as user identity.
For increased reliability, Nortel recommends that the Contivity periodically
backs up its configuration database to a back-up server. The back-up
server can be any computer in the managed IP network capable of hosting
an FTP server.
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Location
The recommended location for the installation of the external OAM
gateway is the external security cluster, if it is physically separate from the
internet peering point cluster. Otherwise, the operating company must
deploy the external OAM gateway in the internet peering point cluster.
Connectivity diagram
Figure 32 "Contivity VPN switch in a CDMA2000 1X network" (page
85) illustrates how a Contivity VPN switch, serving as an external OAM
gateway, connects external support staff with a CDMA2000 1X network.
Figure 32
Contivity VPN switch in a CDMA2000 1X network
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Nortel CDMA2000 1X
NN20000-131 06.02 Standard
17 September 2007
Nortel CDMA2000 1X

All Rights Reserved.
Sourced in Canada and the United States of America
Release: NBSS 15.0
Publication: NN20000-131
Document status: Standard
Document revision: 06.02
Document release date: 17 September 2007
To provide feedback or to report a problem in this document, go to www.nortel.com/documentfeedback.

www.nortel.com
This document is protected by copyright laws and international treaties. All information, copyrights and any other intellectual
property rights contained in this document are the property of Nortel Networks. Except as expressly authorized in writing by Nortel
Networks, the holder is granted no rights to use the information contained herein and this document shall not be published,
copied, produced or reproduced, modified, translated, compiled, distributed, displayed or transmitted, in whole or part, in any
form or media.
Information is subject to change without notice. Nortel reserves the right to make changes in design or components as progress in
engineering and manufacturing warrants.
* Nortel, the Nortel logo, the Globemark, Unified Networks, HLR, Metro Cell, and MSC are trademarks of Nortel.
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.

NN20000-131 06 02

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

NN20000-131 06 02

Enviado por

Direitos autorais:

Formatos disponíveis

Nortel CDMA2000 1X

Planning and Engineering

General deployment strategy

Step 1: Business strategy 9

Initial state of your network

Comparing the IS-95 network to the CDMA2000 1X network

CDMA2000 1X network configuration

Network topology framework 47

CDMA2000 1X hardware and nodes

New in this release

EVRC-B Vocoder (page 7)

CFDS and SOC (page 19)

8 New in this release

Updated references to information regarding Shasta PDSN and SCS

Added PDSN 1600 information

Document revision history

Standard version of technical document for Channel Ready (ChR)

General deployment strategy

Step 1: Business strategy

10 General deployment strategy

While planning your CDMA2000 1X business strategy, there are a number

1. Pre-paid customer and CDMA2000 1X data customer profiles must be

2. Currently, each subscriber must be datafilled in several places: Home

3. Moving a circuit-switched data subscriber to packet data services has

4. The requirements for updating a subscriber from IS-95 to CDMA2000

5. The requirements for adding data to CDMA2000 1X must be defined.

6. Offering circuit-switched data to a CDMA 3G mobile owner increases

Step 3: Comprehensive network plan

Step 2: Overall network distribution

Step 3: Comprehensive network plan

Network planning considerations

Number of co-located SCI-S cards

12 General deployment strategy

Number of sites (local, regional, central)

Figure 3 "Comprehensive network plan" (page 12) represents the major

Step 4: System hardware and software status

Step 5: Data network strategy

Step 5: Data network strategy

14 General deployment strategy

Step 6: Customer care and billing

Step 6: Customer care and billing

Upgrades to your system to establish a CDMA2000 1X network include

Enhanced Selector Card (ESEL) deployment

XCEM or CSVS passive and active deployment

CDMA2000 1X voice and data activation

In addition to the components listed above, the final network configuration

16 General deployment strategy

Switched Network-Foreign Agents (PDSN-FA) and Home Agents, network

Initial state of your network

DMS-MTX and HLR

18 Initial state of your network

While enabling your Digital Multiplex System-Mobile Telephone Exchange

XA Cores scalable processing capacity easily accommodates network

Processor upgrades support succession evolution and 3G networks.

The minimum XA-Core CPU supported by MTX11 is NTLX02CA.

CFDS and SOC

Migrate existing XA-Core 1+1 to a 5+1 configuration during the MTX11

XA-Core-equipped MTXs require an SDM for billing.

For more information about the SDM, refer to DMS-MTX SDMX

NBSS-BSM EBSC or BSC BTS

PDSN and RADIUS

CFDS and SOC

EVRC (CPC code of A0716537/feature order code of CDMA0001)