Cdma2000 1x Ran

68P09266A13–AAPR 2005ENGLISH

SOFTWARE RELEASE 2.17.0.X

TechnicalInformation

CDMA2000 1X RAN FUNCTIONALDESCRIPTION

SPECIFICATIONS SUBJECT TO CHANGE WITHOUT NOTICE

NoticeWhile reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no liability resulting from anyinaccuracies or omissions in this document, or from use of the information obtained herein. The information in this document has beencarefully checked and is believed to be entirely reliable. However, no responsibility is assumed for inaccuracies or omissions. Motorola,Inc. reserves the right to make changes to any products described herein and reserves the right to revise this document and to makechanges from time to time in content hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does notassume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it conveylicense under its patent rights or the rights of others.It is possible that this publication may contain references to, or information about Motorola products (machines and programs),programming, or services that are not announced in your country. Such references or information must not be construed to meanthat Motorola intends to announce such Motorola products, programming, or services in your country.

Copyrights

This instruction manual, and the Motorola products described in this instruction manual may be, include or describe copyrightedMotorola material, such as computer programs stored in semiconductor memories or other media. Laws in the United States andother countries preserve for Motorola and its licensors certain exclusive rights for copyrighted material, including the exclusiveright to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, anycopyrighted material of Motorola and its licensors contained herein or in the Motorola products described in this instruction manualmay not be copied, reproduced, distributed, merged or modified in any manner without the express written permission of Motorola.Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel, orotherwise, any license under the copyrights, patents or patent applications of Motorola, as arises by operation of law in the sale of aproduct.

Computer Software Copyrights

The Motorola and 3rd Party supplied Software (SW) products described in this instruction manual may include copyrighted Motorolaand other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the United States and othercountries preserve for Motorola and other 3rd Party supplied SW certain exclusive rights for copyrighted computer programs, includingthe exclusive right to copy or reproduce in any form the copyrighted computer program. Accordingly, any copyrighted Motorola orother 3rd Party supplied SW computer programs contained in the Motorola products described in this instruction manual may not becopied (reverse engineered) or reproduced in any manner without the express written permission of Motorola or the 3rd Party SWsupplier. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel, orotherwise, any license under the copyrights, patents or patent applications of Motorola or other 3rd Party supplied SW, except for thenormal non–exclusive, royalty free license to use that arises by operation of law in the sale of a product.

VENDOR COPYRIGHTApache Software Foundation Copyright 2002–2003 All Rights ReservedArtesyn Copyright 2002–2003 All Rights ReservedCMU * Copyright 2002–2003 All Rights ReservedFreeware Tools / Utilities * Copyright 2002–2003 All Rights ReservedPerformance Technologies Copyright 2002–2003 All Rights ReservedTelelogic Copyright 2002–2003 All Rights ReservedQNX * Copyright 2002–2003 All Rights Reserved* Freeware

Usage and Disclosure Restrictions

License AgreementThe software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express licenseagreement only and may be used only in accordance with the terms of such an agreement.

Copyrighted MaterialsSoftware and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part of the software ordocumentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language orcomputer language, in any form or by any means, without prior written permission of Motorola, Inc.

High Risk ActivitiesComponents, units, or third–party products used in the product described herein are NOT fault–tolerant and are NOT designed,manufactured, or intended for use as on–line control equipment in the following hazardous environments requiring fail–safecontrols: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication Systems, Air Traffic Control, LifeSupport, or Weapons Systems (“High Risk Activities”). Motorola and its supplier(s) specifically disclaim any expressed or impliedwarranty of fitness for such High Risk Activities.

Trademarks

MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names arethe property of their respective owners.

© Copyright 2003, 2004, 2005 Motorola, Inc.

Javat Technology and/or J2MEt: Java and all other Java–based marks are trademarks or registered trademarks of SunMicrosystems, Inc. in the U.S. and other countries.UNIXR: UNIX is a registered trademark of The Open Group in the United States and other countries.

REV052604

APR 2005 CDMA2000 1X RAN Functional Description i

Table of Contents

CDMA2000 1X RAN Functional Description

Software Release 2.17.0.x

List of Figures iii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of Tables iv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Foreword v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

General Safety vii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Revision History ix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1: Introduction

Overview 1-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2: System Architecture

System Architecture 2-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3: BTS / BTS RTR

Overview 3-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BTS Functional Description 3-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GLI3 Functional Description 3-25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BTS Router Functional Description 3-27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 4: Digital Access and Cross–Connect System (DACs)Digital Access and Cross–Connect System (DACs) 4-1 . . . . . . . . . . . . . . . . . . . . .

Chapter 5: CBSC

CBSC 5-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MM II 5-13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 6: Access Node (AN)Access Node (AN) 6-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 7: SDU (Selection Distribution Unit)

SDU (Selection Distribution Unit) 7-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDF Functional Description 7-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCF Functional Description 7-41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RA (Resource Allocation) Functional Description 7-47 . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents – continued

ii CDMA2000 1X RAN Functional Description APR 2005

Chapter 8: Packet Data Network (PDN)

Introduction 8-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packet Data Serving Node (PDSN) 8-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Home Agent (HA) 8-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

AAA Server 8-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 9: Operations and Maintenance (O&M)

Operations and Maintenance (O&M) 9-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 10: Vocoding Processing Unit (VPU)

Vocoding Processing Unit (VPU) 10-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 11: WAN/LAN Router

WAN Router 11-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APR 2005 CDMA2000 1X RAN Functional Description iii

List of Figures



Figure 1-1: Configurations Available with the CDMA2000 Standard 1-2 . . . . . . . .

Figure 1-2: MTSO Definition 1-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 1-3: RANMD Definition 1-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 1-4: RAN Federation Definition 1-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 1-5: Logical Diagram of a 1X RTT Design 1-8 . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-1: 17.0 Motorola Radio–Packet Access Network Architecture with MM (DNP) 2-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-2: 17.0 Motorola Radio–Packet Access Network Architecture with MM II 2-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-3: 17.0 Motorola Radio–Packet Access Network Architecture with MM II and DNP in Mixed System 2-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-4: CDMA2000 1X Reference Architecture 2-4 . . . . . . . . . . . . . . . . . . . . .

Figure 2-5: Network Configuration for IS 95 A/B Voice/Data and IS–2000 IX Voice/Data 2-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-6: Network Configuration for 1X with Voice Only (No Data) 2-9 . . . . . .

Figure 2-7: 1X with Data (IS95 A/B & 1X) Only (No Voice) 2-11 . . . . . . . . . . . . . .

Figure 3-1: SCt 4812T Frame without doors 3-10 . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-2: SCt 4812T Signal Flow 3-13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-3: SCt480 Chassis Layout 3-19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-4: SCt480 Signal Flow 3-20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-5: SCt 4812T–MC (+27v Left) (–48v Right) Frame (shown without doors) 3-23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-6: Typical BTS Router Configuration 3-28 . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-1: DACs Illustration 4-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5-1: PSI Card Signal Flow 5-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5-2: PBIB–ES Physical Layout 5-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5-3: PBIB–E Physical Layout 5-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5-4: IP–BSC 5-15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5-5: MM II Network I/O Interfaces 5-19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5-6: MM II Network I/O Interfaces 5-19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6-1: Access Node (AN) 6-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of Figures – continued

iv CDMA2000 1X RAN Functional Description APR 2005

Figure 6-2: IP Packets 6-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6-3: TCP Segments 6-19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6-4: UDP 6-21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6-5: SCTP Datagrams 6-25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-1: IP–BSC 7-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-2: CDMA Handoff Functional Diagram, SDU architecture 7-11 . . . . . . . .

Figure 7-3 Signalling paths – Intra–CBSC Handoff Scenarios 7-22 . . . . . . . . . . . . .

Figure 7-4: Signalling paths – Inter CBSC scenarios with ICSRCHAN 7-23 . . . . . .

Figure 7-5: Signalling paths – Inter–CBSC scenarios with AN 7-24 . . . . . . . . . . . . .

Figure 7-6: Bearer connectivity for Intra–CBSC scenarios (SRCHAN and AN) 7-25

Figure 7-7: Bearer connectivity for Inter–CBSC scenarios with ICSRCHAN 7-26 .

Figure 7-8: Bearer connectivity for Inter–CBSC scenarios with AN 7-27 . . . . . . . . .

Figure 7-9: Forward Power Control 7-37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-10: PCF Architecture 7-42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 9-1: OAMP Connections/Relationships 2.17.0.x. 9-2 . . . . . . . . . . . . . . . . . .

Figure 9-2: Netra Cabinet – OMC Cabinet Layout 9-8 . . . . . . . . . . . . . . . . . . . . . .

Figure 9-3: Operations and Maintenance Hierarchy 9-15 . . . . . . . . . . . . . . . . . . . . . .

Figure 10-1: VPU Implementation (Circuit) 10-2 . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 10-2: VPU Implementation (IP–BSC) 10-3 . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 10-3: VPU External Interfaces 10-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 10-4: VPU External Timing Sources 10-17 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 11-1: WAN/LAN Router Implementation 11-1 . . . . . . . . . . . . . . . . . . . . . . . .

APR 2005 CDMA2000 1X RAN Functional Description v

List of Tables



Table 1-1: Acronyms and Terms 1-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-1: Legacy Overlay Options 3-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-1: MM Signalling Interfaces 5-21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 6-1: Catalyst 6509 redundancy 6-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 6-2: MuxPPP in RAN 6-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 6-3: MLPPP 6-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 6-4: cUDP 6-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 6-5: MGX Redundancy 6-14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 6-6: IP Applications 6-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 6-7: Network Elements implementing TCP 6-20 . . . . . . . . . . . . . . . . . . . . . . .

Table 6-8: UDP Implementation 6-21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 6-9: Network elements implementing SCTP 6-25 . . . . . . . . . . . . . . . . . . . . . .

Table 11-1: WAN Router Inputs and Outputs 11-3 . . . . . . . . . . . . . . . . . . . . . . . . . .

Foreword

vi CDMA2000 1X RAN Functional Description APR 2005

Scope of manual

This manual is intended for use by cellular telephone systemcraftspersons in the day-to-day operation of Motorola cellular systemequipment and ancillary devices.

This manual is not intended to replace the system and equipmenttraining offered by Motorola, although it can be used to supplement orenhance the knowledge gained through such training.

Obtaining manuals

To view, download, or order manuals (original or revised), visit theMotorola Lifecycles Customer web page athttps://mynetworksupport.motorola.com/, or contact your Motorolaaccount representative.

If Motorola changes the content of a manual after the original printingdate, Motorola publishes a new version with the same part number but adifferent revision character.

Text conventions

The following special paragraphs are used in this manual to point outinformation that must be read. This information may be set-off from thesurrounding text, but is always preceded by a bold title in capital letters.The four categories of these special paragraphs are:

Presents additional, helpful, non-critical information thatyou can use.

NOTE

Presents information to help you avoid an undesirablesituation or provides additional information to help youunderstand a topic or concept.

IMPORTANT

*

Presents information to identify a situation in whichdamage to software, stored data, or equipment could occur,thus avoiding the damage.

CAUTION

Presents information to warn you of a potentiallyhazardous situation in which there is a possibility ofpersonal injury.

WARNING

Foreword – continued

APR 2005 CDMA2000 1X RAN Functional Description vii

The following typographical conventions are used for the presentation ofsoftware information:

S In text, sans serif BOLDFACE CAPITAL characters (a type stylewithout angular strokes: for example, SERIF versus SANS SERIF)are used to name a command.

S In text, typewriter style characters represent prompts and thesystem output as displayed on an operator terminal or printer.

S In command definitions, sans serif boldface characters representthose parts of the command string that must be entered exactly asshown and typewriter style characters represent command outputresponses as displayed on an operator terminal or printer.

S In the command format of the command definition, typewriterstyle characters represent the command parameters.

Reporting manual errors

To report a documentation error, call the CNRC (Customer NetworkResolution Center) and provide the following information to enableCNRC to open an SR (Service Request):– the document type – the manual title, part number, and revision character– the page number(s) with the error– a detailed description of the error and if possible the proposed solutionMotorola appreciates feedback from the users of our manuals.

Contact us

Send questions and comments regarding user documentation to the emailaddress below:[email protected]

Motorola appreciates feedback from the users of our information.

Manual banner definitions

A banner (oversized text on the bottom of the page, for example,PRELIMINARY) indicates that some information contained in themanual is not yet approved for general customer use.

24-hour support service

If you have problems regarding the operation of your equipment, pleasecontact the Customer Network Resolution Center (CNRC) for immediateassistance. The 24 hour telephone numbers are:

North America +1–800–433–5202Europe, Middle East, Africa +44– (0) 1793–565444Asia Pacific +86–10–88417733Japan & Korea +81–3–5463–3550. . . . . . . . . . .

For further CNRC contact information, contact your Motorola accountrepresentative.

General Safety

viii CDMA2000 1X RAN Functional Description APR 2005

Remember! . . . Safetydepends on you!!

The following general safety precautions must be observed during allphases of operation, service, and repair of the equipment described inthis manual. Failure to comply with these precautions or with specificwarnings elsewhere in this manual violates safety standards of design,manufacture, and intended use of the equipment. Motorola, Inc. assumesno liability for the customer’s failure to comply with these requirements.The safety precautions listed below represent warnings of certain dangersof which we are aware. You, as the user of this product, should followthese warnings and all other safety precautions necessary for the safeoperation of the equipment in your operating environment.

Ground the instrument

To minimize shock hazard, the equipment chassis and enclosure must beconnected to an electrical ground. If the equipment is supplied with athree-conductor ac power cable, the power cable must be either pluggedinto an approved three-contact electrical outlet or used with athree-contact to two-contact adapter. The three-contact to two-contactadapter must have the grounding wire (green) firmly connected to anelectrical ground (safety ground) at the power outlet. The power jack andmating plug of the power cable must meet International ElectrotechnicalCommission (IEC) safety standards.

Refer to Grounding Guideline for Cellular RadioInstallations – 68P81150E62.

NOTE

Do not operate in an explosiveatmosphere

Do not operate the equipment in the presence of flammable gases orfumes. Operation of any electrical equipment in such an environmentconstitutes a definite safety hazard.

Keep away from live circuits

Operating personnel must:

S not remove equipment covers. Only Factory Authorized ServicePersonnel or other qualified maintenance personnel may removeequipment covers for internal subassembly, or componentreplacement, or any internal adjustment.

S not replace components with power cable connected. Under certainconditions, dangerous voltages may exist even with the power cableremoved.

S always disconnect power and discharge circuits before touching them.

General Safety – continued

APR 2005 CDMA2000 1X RAN Functional Description ix

Do not service or adjust alone

Do not attempt internal service or adjustment, unless another person,capable of rendering first aid and resuscitation, is present.

Use caution when exposing orhandling the CRT

Breakage of the Cathode–Ray Tube (CRT) causes a high-velocityscattering of glass fragments (implosion). To prevent CRT implosion,avoid rough handling or jarring of the equipment. The CRT should behandled only by qualified maintenance personnel, using approved safetymask and gloves.

Do not substitute parts ormodify equipment

Because of the danger of introducing additional hazards, do not installsubstitute parts or perform any unauthorized modification of equipment.Contact Motorola Warranty and Repair for service and repair to ensurethat safety features are maintained.

Dangerous procedurewarnings

Warnings, such as the example below, precede potentially dangerousprocedures throughout this manual. Instructions contained in thewarnings must be followed. You should also employ all other safetyprecautions that you deem necessary for the operation of the equipmentin your operating environment.

Dangerous voltages, capable of causing death, are present in thisequipment. Use extreme caution when handling, testing, andadjusting.

WARNING

Revision History

x CDMA2000 1X RAN Functional Description APR 2005

Manual Number

68P09266A13–A

Manual Title

CDMA2000 1X RAN Functional Description Software Release 2.17.0.x

Version Information

The following table lists the manual version, date of version, andremarks on the version.

VersionLevel

Date of Issue Remarks

A APR 2005 Updated for release 2.17.0.x.x

APR 2005 CDMA2000 1X RAN Functional Description

Chapter 1: Introduction

Table of Contents

Overview 1-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 1-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The CDMA 1X Standard 1-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Boundaries 1-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of CDMA 1X IP Solution 1-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . Acronyms 1-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1


CDMA2000 1X RAN Functional Description APR 2005

Notes

1

Overview

APR 2005 1-1CDMA2000 1X RAN Functional Description

Introduction

This chapter covers the following information:

S overview of release(s) 2.17.0.x.

S overview of the CDMA 1X standard.

S system boundaries and how the various topologies can be realized andwhere external network services might be required.

Release 2.17.0.x

Release 2.17.0.x will add the MM II which replaces the DNP. Theconcept of IP–BSC is introduced in this release. This is really anevolutionary change as parts of the concept have been added in previousreleases but the addition of MM II brings to concept to fruition. NewBTS models will be added in some markets. 1xEV–DO capabilities willbe added to additional BTSs. A new optional feature called REACH willbe added, while not introducing new equipment will effect how MCC1Xresources are allocated.

The CDMA 1X Standard

CDMA2000 1X is the first step into third–generation (3G) networks foran IS–95–based network. CDMA2000 1X is a standard that defines theair interface and portions of the core network for delivering 3G services.These standards enable 3G networks to deliver new services for endusers and new revenue streams for operators.

The CDMA2000 1X standard delivers higher data rates and improvedvoice capacity than the existing 2G and 2.5G CDMA technologies. TheMotorola implementation of the standard can support data rates up to144 kpbs and a voice capacity improvement of up to 1.7 times overIS–95A/B. Since CDMA2000 1X is completely backwards compatiblewith IS–95A/B, it allows a cost– effective migration from IS–95A/B to1X. Therefore, an operator can upgrade to 1X while maintaining theircurrent infrastructure and handset investments.

The CDMA2000 standard provides a choice of overlay or non–overlayconfigurations, allowing operators to implement the 1X technology ineither their existing spectrum or in a new 3G spectrum. (See Figure 1-1.)

1

Overview – continued

CDMA2000 1X RAN Functional Description APR 20051-2

f 1 f 2 f 3 f 4 f 5

A/B A/B A/B

1X 1X

f 1 f 2 f 3

A/B

1X

1X Non–Overlay1X Non–Overlay 1X Overlay1X Overlay

Figure 1-1: Configurations Available with theCDMA2000 Standard

By using the overlay configuration, operators without the new 3Gspectrum can use their existing spectrum to implement 1X. The benefitof such a configuration is limited as there are conflicts with the existingIS–95A/B RF links in the spectrum.

On the flip side, operators who buy the new 3G spectrum can assigndedicated 1X carriers to high data rate traffic and can use other IS–95Aand IS–95B carriers for the low speed data and voice. Such aconfiguration is known as the non–overlay configuration. This scheme isparticularly suitable for markets where high–speed data traffic is high.By directing all the low speed data and voice traffic to IS–95A andIS–95B carriers, the enhanced 1X air interface can take the full carriercapacity and provide peak data rate radio frequency (RF) links on the 1Xcarriers under suitable conditions.

1



System Boundaries

Introduction

This section describes high–level system views, network components,and boundaries.

Defining Network components

This section describes the network from the smallest functional block tothe largest to enable the view of the possible variations in the topology.

BSS

The BSS (Base Station Subsystem) consists of the BSS end nodes andthe Transport Network devices that connect all those network elements.

The BSS end nodes consist of:

S The BTS, located remotely at the cell–site;

S XC, located at the MTSO;

S SDU, located at the MTSO;

S VPU, located at the MTSO;

S MM, located at the MTSO.

S IP–BSC, located at the MTSO.

The AN IP Switch and Aggregation Point frames contain the routing andswitching equipment used to interconnect all the BSS end nodes,forming the Transport Network.

The scope of a BSS is determined by the end nodes (XCs, BTSs, SDU,etc) that have their call processing controlled by the MM.

Each physical SDU is shared between many BSSs.

NOTE

BSSAN

The BSSAN consists of a set of multiple BSSs that communicate via aco–located portion of the AN Transport Network (connected via LAN).

The Transport Network that supports a BSSAN can consist of multiplepairs of MLSs (contained in the AN IP Switch frames). A BSSAN canalso consist of a pair of MLSs supporting multiple BSSs. A BSSAN isalso an Autonomous System (AS) running a specific routing protocol(i.e. OSPF). The size of a BSSAN and hence the number of BSSs thatcan be supported is limited by the size of an Autonomous System (AS),which in turn is limited by routing protocol convergence times andphysical interface capacity.

1



Mobile Telephone Switching Office (MTSO)

A single MTSO (e.g. an office tower) contains multiple BSSANs (hencemultiple ASs) which are themselves inter–connected with LANconnections.

The MTSOs are inter–connected with WAN connections (via the use of aWAN gateway).

To support packet data services from the CDMA IP RAN, an MTSOmay contain one or more PDSNs which are connected via LAN to aBSSAN. The traffic from the radio side of the PDSN (R–P) may becontained within the MTSO or may traverse the inter–MTSO WANlinks. The traffic from the packet data network (PDN) side of the PDSN(P–I) is not shown here as this is considered to be a separate IP network(i.e. not part of the RAN).

WAN gateways are used to route traffic between MTSOs across WANlinks and are themselves unique ASs. In some cases, the WAN GW isalso used to route traffic between BSSANs.

Figure 1-2: MTSO Definition

RAN Management Domain (RANMD)

The RAN connects the subscriber devices with the core, providing voiceand data services to individual wireless subscriber devices.

For the purposes of management, the RAN is broken down into multiplemanagement domains, each comprised of the components of one or moreMTSOs: the O&M controller devices such as the OMCR and CEM, thegateway devices used for communication with other operators networksor vendors equipment, and the Transport Network devices that connectall of these end nodes.

Assuming the CEM has the same or larger scope, the size of theRANMD is defined by the number of end–nodes that can be managed bya single OMCR.

1



Figure 1-3 shows a RANMD that consists of two MTSOs. The MTSOsare connected together in the Transport Network via a set of WANinterfaces. The OMCR and CEMs manage all the elements that make upthe BSSs and Transport Network. The RANMD is connected via theTransport Network to the Core, which provides PDSN and Pushservices. The Motorola/Cisco RAN is also connected to another vendor’sor operators RAN via a Gateway device.

Figure 1-3: RANMD Definition

RAN Federation

The RAN Federation is the area within which traffic can be routedwithout having to travel through a Gateway device. From the TransportNetwork perspective, inside a RAN Federation, a single IP address spaceis utilized, allow for all devices to communicate without requiring anaddress space conversion (e.g. NAT), security or inter–workingfunctions. In addition to the IP address space scope, the RANFederation’s size may be limited by QoS and delay considerations (e.g.,# of inter–MTSO links traversed).

The RAN Federation MAY also contain another level of O&Mhierarchy, used for Network Management of the entire RAN Federation.As mentioned earlier, the Transport Network that makes up the RANFederation might be comprised of devices other than BSSAN IPswitches, BTS routers and Aggregation Points. Also, for purposes ofdelay budgets, it is quite possible that the complete Transport Networkwould not comprise a mesh but would instead be a hierarchical design,using a WAN router for fast routing between the various MTSOs.

1



Figure 1-4: RAN Federation Definition

Boundaries

There are essentially two areas of consideration in determining aboundary for the system: Distance and Functionality.

Distance

Any time a network exceeds the transmission distance limits of thedefined interfaces on the Motorola AN (Cat 5e data (10/100/1000BaseT)and T1/E1) or when the RAN boundaries are crossed, work withMotorola System Engineering to determine what services might berequired to make your network operate.

Function

The BSSAN is essentially the borderline for function. Anything leavingthe Catalyst t or SDU is viewed as “the outside”. These “borders” caninclude but are not limited to:

S PDN

S Internet, Intranet, extranet

S WAN to another RAN or MTSO (transport)

The PDN consists of the PDSN, AAA, and optionally the HA. The RANPacket Control Function (PCF), residing in the XC (16.0) or SDU(16.1), interfaces to the PDN through the PDSN. The AAA may alsoneed a Mediation Device to interface the data billing with a legacy voicebilling systems.

1



Interface to the Internet or other network will work if you do not violatethe laws of TCP/IP. Most of the concerns here are those of applicationcompatibility. Some operators may prefer to build a private network formobile applications that they sponsor and leave any Internet applicationsto whatever level of operation is available, as the actual performance isbeyond their control. Other customers with different business mixesmay choose to hang their application on the Internet.

For the interface to the WAN for the RAN or the MTSO, the WAN canbe operator owned or a leased service. The same engineeringconsiderations apply (see the “Distance” topic) and the testing should bethat which is required by the transported protocol and any transmissionquality tests required.

1



Overview of CDMA 1X IPSolution

3G 1XRTT Design

The high–level logical diagram below illustrates the Access Node (AN),a Packet Data Serving Node (PDSN), IP Core ATM Transit, and a AAAarchitecture and interfaces with Motorola’s 16.0 1st generation CDMA1X RAN. This end–to–end Packet Data Network (PDN) solutionenables 3G 1XRTT high–speed packet data for both 800MHz and1.9GHz scenarios.

Figure 1-5: Logical Diagram of a 1X RTT Design

1



IP Core – The IP Core consists of:

S Packet Data Serving Node (PDSN)

S Access Node (AN)

S Other switches and routers

S F/W

S Internet

The AN/PDSN connects the Motorola CDMA 2000 1X Networkelements (the RAN) into the IP Core network.

The AN provides IP network connectivity, and the PDSN providesSimple IP, Mobile IP, and Proxy Mobile IP services.

Transit IP Core – The Transit IP Core consists of the AggregationPoint ( MGX t) portion of the AN, providing interfaces for the BTSs.

1



Acronyms

Table 1-1 lists the acronyms used in this manual.

Table 1-1: Acronyms and Terms

Acronym/Term Description

AAA AAA (Authentication, Authorization, andAccounting) Server

ACL Access Control List

Aggregation Point Refer to the “AN” item.

AMR Alarm Monitoring and Reporting

AN Access Node (AN). The AN consists of:

S IP Switch frame containing the CatalystMulti–layer switches (MLSs)

S Aggregation Point frame containing the MGXwith the Edge Routing function

The AN forms the Transport Network.

ARP Address Resolution Protocol

AS OSPF protocol Autonomous System

BBX Broadband Transceiver

BGP Border Gateway Protocol

BHCA Busy Hour Call Attempts

BHSA Busy Hour Session Attempts

BMD Billing Mediation Device

BPP, BPPR1 Bearer Payload Processor card

BSS Base Station Subsystem

BSSAN Base Station Subsystem Access Node

BTS Base Transceiver Station

Catalyst Refer to the “AN” item.

CBSC Centralized Base Station Controller

CCD CDMA Clock Distribution

CDB Central Database

CDL Call Detail Log

CDP CDMA Data Process

CDR Call Detail Record

. . . continued on next page

1





CE Channel Element

CEM Cisco Element Manager

CFC Call Final Class

CHAN Channel

CHAP Challenge Handshake Authentication Protocol

CIO Combiner Input/Output

CLI Command Line Interface

CMIP Common Management Information Protocol

DACS Digital Access and Cross Connect

DAHO Data Assisted Handoff

DMK Device Manager Kit

DXCDR Data XCDR

Edge Router Refer to the “AN” item.

EM Element Manager

EMS Element Manager System

EPG Equipment Planning Guide

FA Foreign Agent

FCAPS Network Management protocol

FER Frame Error Rate

FRU Field Replacement Unit

FTP File Transfer Protocol

GoS Grade of Service

GRE Generic Resource Encapsulation Protocol

GPS Global Positioning System

HA Home Agent

HARP High Availability RADIUS Proxy

HLR Home Location Register

HSD High Speed Data

HSO High Stability Oscillator


1





HSPD IS–95B High Speed Packet Data

HSRP Hot Standby Routing Protocol

ICBS Inter–CBSC

ICLINK Internet Control Links

ICMP Internet Control Message Protocol

IC SPAN Inter–CBSC Span

ICSR Inter–CBSC Soft–handoff Reserve

ICTRKGRP Inter–CBSC Soft Handoff Trunk Group

IGMP Interior Gateway Protocol

IOS Interoperability Standard

IP Internet Protocol

IPM Inter–network Performance Management

IP Switch Refer to the “AN” item.

ITU International Telecommunications Union

IWU Inter–working Unit

LAN Local Area Network

LAPD Link Access Protocol

LWRTR LAN–WAN Router

MAC Media Access Control

MAHO Mobile Assisted Hand Off

MCAP Motorola Cellular Advance Processor Bus

MGX Refer to the “AN” item.

MIB Management Information Base

MLS Refer to the “AN” item.

An MLS can be local or remote.

MM Mobility Manager

MS Mobile Station

MSC Mobile Switching Center

MSID Mobile Station Identifier


1





MTSO Mobile Telephone Switching Office

NAI Network Address Identifier

NIB Network Interface Box

O&M Operations and Maintenance

OHCG Overhead Channel Group

OMC Operations Maintenance Center

OMC–CLI Operations Maintenance Center Command LineInterface

OMC–IP Operations Maintenance Center Internet Protocol

OMC–R Operations Maintenance Center – Radio

OMP Operations and Maintenance Processor

OSPF Open Shortest Path First protocol

OSS Operations Support Systems

PAP Password Authentication Protocol

PCF Packet Control Function. PCF resides on eitherXC PSI cards or the SDU.

PCM Pulse Code Modulation

PDN Packet Data Network (PDSN, HA, AAA)

PDSN Packet Data Serving Node

PIM Protocol Independent Multicast routing protocol

PM Performance Management

PPP Point–to–Point Protocol

PSI Packet Sub–rate Interface

PSI–CE XC PSI card performing the circuit–to–packetconversion function.

PSI–PCF XC PSI card performing the packet controlfunction.

PSI–SEL XC PSI card performing the selection anddistribution function.

PZID Packet Zone ID

QoS Quality of Service


1





RADIUS Remote Authentication User Dial–In Service

RAN Radio Access Network

RAS Reduced Active Set

RC Radio Configuration

RDBMS Relational Database Management Systems

RF Radio Frequency

RLP Radio Link Protocol

RMON Remote Monitoring

RNOC Remote Network Operations Center

RPM MGX Route Processor Modules which performthe edge routing function. Refer to the “AN”item.

SDF Selector / Distributor function

The SDF resides in the SDU on the BPP card andreplaces the 16.0 PSI–SEL function.

SDU Selector Distribution Unit

SHO Soft Hand Off

SMNE Self Managed Network Elements

SNMP Simple Network Management Protocol

TCH Traffic Channels

TDM Time Division Multiplexing

TN Transport Network. Refer to “AN”.

TSM BTS Time Slice Manager

UDP User Datagram Protocol

UIS User Interface Server

UNIR Unified Network Information Record

UNO Universal Network Operations

USART Universal Synchronous / AsynchronousReceiver–Transmitter

VLAN Virtual Local Area Network

VLR Visitor Location Register


1





VPDN Virtual Private Dial Network

VPU Vocoding Processing Unit

WAN Wide Area Network

WAP Wireless Access Protocol

XC Transcoder

XCDR Transcoder Card

XDR XACCT Detail Record

XIS Xacct Interface Server

1



Notes

1


Chapter 2: System Architecture

Table of Contents

System Architecture 2-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Architecture 17.0 2-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Configuration Variations 2-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2



Notes

2

System Architecture


System Architecture 17.0

Figure 2-1 illustrates the major elements of the 17.0system architecture.

Figure 2-1: 17.0 Motorola Radio–Packet Access Network Architecture with MM (DNP)

2

System Architecture – continued


Figure 2-2: 17.0 Motorola Radio–Packet Access Network Architecture with MM II

You will note that the MM II supports only packet based systemelements. This new architecture is intended for Greenfield installationsand operators who have implemented packet architecture and wish totake first advantage of the emerging technology with increasedefficiencies, performance capabilities and reduced space requirements.

2



Figure 2-3 shows a mixed system with both DNP and MM II Mobilitymanagers.

Figure 2-3: 17.0 Motorola Radio–Packet Access Network Architecture with MM II and DNP in Mixed System 2



System ConfigurationVariations

2.17.0.x will allow a number of system configurations to meet variousoperator requirements. The following, DNP based, configurations areillustrated and briefly described in this section:

S The reference or base architecture

S Interfaces

S IS 95 A/B voice/data and IX voice/data (Packet backhaul)

S IX with voice only (no data)

S 1X data only

1xEV–DO is also supported in this release but this iscovered in a separate document.

NOTE

Reference Architecture

Figure 2-4 illustrates the CDMA2000 1X Reference architecture.

Figure 2-4: CDMA2000 1X Reference Architecture

2



Radio Access Network (RAN)

The Radio Access Network (RAN) provides the basic transmission, localcontrol, and management functions associated with processingSubscriber Device services. This involves the management and controlof establishing the Subscriber on the Radio Channel, as well asestablishing procedures with the Core and Packet Data Network fornetwork level processing (e.g., Call Delivery). The RAN also includesthe OMC–R.

Core Network (Core NW)

The Core Network element provides the functional responsibility forestablishing connections into the PSTN for Circuit Oriented Services.The Core NW, more specifically the MSC, manages Subscriberinformation (Static and Dynamic). The Core NW is also responsible forthe generation of billing records. The Core NW provides authenticationand MS location services via interactions with HLR and VLR corecomponents.

Packet Network (Packet Data Network)

The Packet Network element provides the functional responsibility forestablishing sessions into the PSTN (e.g., VOIP) or IP Networks forPacket Data Oriented Services. The Packet Data Network provides basicnon–real time data services with the proposed evolution to real–timebased applications, such as VOIP. The Packet Data Network currentlyrelies on the Core NW for subscriber authentication and location.Authentication of packet data sessions is performed by the Packet DataNetwork (AAA server). From a RAN perspective, the Packet NW isviewed as either Packet IWU based or PDSN based.

Mobile Subscriber (MS)

The Mobile Subscriber (MS) element defines the end point for services.The MS is responsible for the initiation services. It also processesservice requests from the network to establish services initiated by otherend devices. The MS operates a set of procedures to enable themanagement and control of services with the system, such asRegistration.

Circuit Based RANs

The Circuit Based RAN refers to a remote Motorola Circuit Based RadioAccess Network which supports connections to the RAN for soft handoffsupport. This Circuit Based RAN refers to the selected interconnect usedbetween the two CBSCs for Soft Handoff support. For the RemoteCBSC to be a Packet CBSC, the operator must choose a Circuit BasedInterconnect for soft handoff.

Packet Backhaul Based RANs

The Packet Based RAN refers to a remote Motorola Packet Based RadioAccess Network, which supports connects to the RAN for soft handoffsupport.

2



Inter–Vendor RANs

The Inter–Vendor RAN refers to a remote non–Motorola Radio AccessNetwork which supports connects to the RAN for soft handoff support.

Interfaces

The following provides an overview of the interfaces to the MotorolaRAN.

RAN to Core/MSC:

–A1

–A2

–A5

–A1 over TCP/IP

RAN to PDN:

–L–interface to Packet IWU (viewed only for systemconfigurations containing installed Packet IWUs)

–L–Interface to Circuit IWU

–A10, A11 (R–P) to PDSN

RAN to Mobile Station (MS):

–IS–95 A/B (including HSPD)

–IS–2000

RAN to “circuit based” RAN:

–Anchor PCF support via the Transport Network (ANs)

–Inter–CBSC SHO support via the Transport Network (ANs)

2



IS–95 A/B Voice/Data, 1X Voice/Data

The configuration illustrated below is anticipated to be the primary onefor systems that may still contain circuit elements and retain DNP basedMM. The configurations that follow this one (i.e., the remainder of thischapter) allow operators to meet specific system requirements.

Figure 2-5: Network Configuration for IS 95A/B Voice/Data and IS–2000 IX Voice/Data

Packet BTS Packet BTS

MGX 8800 MGX 8800

AN

C6500C650010/100 Ethernet

Virtual LAN

XC

MM

OMCRTo MSC/PSTN

Token Ring

CBSC

Circuit BTS

Circuit BTS

Circuit BTS

PDSN

AAA

HA

SpanGrooming

SDU

OMC–IP

Circuit IWU Packet IWU

Compressionadapter andGLI3

Non

Packetpipe/mixedbackhaul

WANrouter toother

networks Other Internal

IP Networks

PTSNExternal IPNetwork(Internet)

data

VPU

To MSC/PSTN

The BTS Router may be present between the Packet BTSand AN.

NOTE

2



1X with Voice Only (No Data)

This configuration is for operators who have either:

S Minimal data plans that can be met via circuit–based data, or

S An alternate delivery system for data services but want the benefits of1X voice capacity.

S This service could also be realized with the MM II with the PDNnetwork eliminated. The circuit IWU would have to connect at theMSC, for this release. Obviously, the requirements of the MM IInetwork would also apply.

This system could have packet or circuit backhaul. Packetbackhaul provides maximum efficiency and capacity butrequires the AN, OMC–IP, and SDU. Circuit backhaulrequires no AN, OMC–IP, or SDU but provides muchsmaller capacity. Addition of VPU requires AN, SDU,OMC–IP, and mesh elimination.

NOTE

2



Figure 2-6: Network Configuration for 1X withVoice Only (No Data)


MGX 8800 MGX 8800

AN


Virtual LAN

XC

MM

OMCRTo MSC/PSTN

Token Ring

CBSC

Circuit BTS

Circuit BTS

Circuit BTS

VPU

OMC–IP

Circuit IWU

Other InternalIP Networks

PTSN

SDU

To MSC/PSTN

2



1X With Data Only (No Voice)

This configuration is for operators who have:

S Existing voice capacity and available spectrum for data

S An alternate delivery system for Data services but wants the voicecapacity of CDMA 1X.

S This configuration could also be realized with the MM II via theelimination of all the circuit based aspects

This configuration is still supported, but 1xEV–DO is therecommended solution.

NOTE

2



Figure 2-7: 1X with Data (IS95 A/B & 1X)Only (No Voice)


MGX 8800 MGX 8800

AN


Virtual LAN

XC

MM

OMCRTo MSC/PSTN

Token Ring

CBSC

Circuit BTS

Circuit BTS

Circuit BTS

PDSN

SDU

OMC–IP

Circuit IWU Packet IWU

SpanGrooming

External IPNetwork(Internet)


PTSN

AAA

HA

2



Notes

2


Chapter 3: BTS / BTS RTR

Table of Contents

Overview 3-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 3-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BTS Functional Description 3-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCt 4812T Starter BTS 3-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCt 4812T 1X and Packet Backhaul Upgrade BTS 3-15 . . . . . . . . . . . . . . Expansion SCt4812T 3-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCt48x 3-17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrated BTS Router 3-21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCt4812T–MC CDMA BTS 2.1 GHz 3-21 . . . . . . . . . . . . . . . . . . . . . . . . SCt4812T–MC Dynamic PA Functionality 3-24 . . . . . . . . . . . . . . . . . . . . Rural Cell Enabler 3-24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GLI3 Functional Description 3-25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Function 3-25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inputs and Outputs 3-25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Card Description 3-25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signal Flow 3-25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redundancy 3-25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O & M 3-26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BTS Router Functional Description 3-27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Router 3-27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrated BTS Router 3-30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3



Notes

3

Overview


Overview

Introduction

This chapter provides an overview of the Motorola CDMAMacroCell and MicroCell Base Transceiver Station (BTS)products delivering CDMA2000 1X capability in system release2.17.0.x. The BTS is part of the Motorola SCt architecture, andprovides the necessary equipment to implement the CDMA airinterface.

This chapter will focus on providing basic information on theSC 4812Tt and SC480 for new and 1X upgrade equipment.Legacy MacroCell BTSs are addressed by adding one of thevariations of SC 4812 to implement the 1X and retaining IS–95A&B on the legacy BTS.

3

BTS Functional Description


SCt 4812T Starter BTS

Description

The SCt 4812T is the primary MacroCell within the 4812 platform.Listed below are the additional variations.

Function

The SCt 4812 BTS portfolio contains the following options:

S SCt 4812MF (Modem Frame) – The SCt 4812MF, an indoor unitoperating at 800 MHz, is generally intended to act as anexpansion frame to support the expansion of existing SCt 9600 andHDII 20–channel medium to high–density cell sites, withshared TX functionality. The Modem Frame will rely onexternal power amplification for the TX path. Accordingly, theSCt 4812MF is based on the SCt 4812T Expansion Frame,with major changes to the TX path.

S SCt 4812T – The SCt 4812T, an indoor unit operating at 800,1700 & 1900 MHz, has one major difference from itspredecessor, the SCt 4812 (non–trunked). The difference is theuse of a new RF trunking technique that reduces the number ofLPAs required and provides increased power capability.

The SCt 4812 product uses 2 single tone LPA modules percarrier–sector to provide 20 watts post duplex per carrier–sector.The SCt4812T uses a set of 4 higher power LPA modules per 3sectors of one carrier to provide 20 watts simultaneously (60watts total) per carrier–sector post duplex. The 60W trunked TXpower offered by the SCt 4812T is intended to providesufficient power to balance the link with the receive sensitivityimprovements of the EMAXX chipset.

The SCt 4812T replaced the non–trunked version of SCt 4812.The trunked LPA cage & trunking module and trunked LPA setsare not available to retrofit in the SCt 4812 product that wasoriginally shipped with the conventional LPA scheme. The newLPAs can be used in the non–trunked version of SCt 4812.

S SCt 4812T –48v – The SCt 4812T (–48v), an indoor unitoperating at 800 MHz, is functionally the same design as theexisting SCt 4812T, with one major difference being the use of newinternal power conversion hardware which utilizes a supplyvoltage of –48V rather than the existing +27V nominal.

3

BTS Functional Description – continued


S SCt 4812ET – The SCt 4812ET, an outdoor unit operating at800 & 1900 MHz, is functionally the same design as theSCt 4812T, with specifications for outdoor applications. TheSCt4812ET is a self–contained, weatherized version of theSCt 4812T. The RF portion of the BTS has been separatedfrom the Power Supply portion, each one having its own cabinet.

The 800 MHz SCt 4812ET was Motorola’s first manufacturersupplied 800 MHz CDMA outdoor base station. Previously,customers have in some instances taken a Legacy base station(for example: SCt2400, SCt2450, or SCt 9600) andcontracted a third–party cabinet supplier to retrofit for outdoorenvironments. By splitting the RF and Power Supplycomponents into two cabinets, each cabinet will fit into a typicalfreight elevator.

S SCt 4812ET Lite – The SCt 4812ET Lite, an outdoor unitoperating at 800 & 1900 MHz, is Motorola’s latest CDMA basestation product optimal for medium capacity sites and ubiquitoussystem coverage applications. It requires lower initial capitalinvestment than the larger macro–BTS products, yet is easilyexpandable for future growth.

The SCt 4812ET Lite packs an indoor/outdoor two–carrierCDMA communications base station in a small, single framepackage. The single–frame configuration integrates the RadioFrequency (RF), power rectification and battery backup forcost–effective installation and maintenance.

The SCt4812ET Lite is expandable to four carriers by addingone expansion frame. It requires only two antennas per sectorfor any carrier configuration, from one carrier up to four carriers.The single frame design reduces the overall footprint, yieldingreduced deployment costs and increased ease of installation.Common spares or Field Replaceable Units (FRUs) shared withthe SCt 4812ET make equipment management more efficient.

As we migrate to 3G–1X and beyond, the SCt 4812ET Lite willshare a common software and hardware migration path with theSCt 4812 series of BTS, making upgrades more efficient.

3



S SCt 4812 T Lite – (–48, 27,AC)The SCt 4812T Lite single frame CDMA BTS is Motorola’s800 MHz Low Tier CDMA base station product and is designedto support medium to high–density cell sites. The SCt 4812TLite base station is for indoor application and can support up totwo CDMA carriers per frame in a 3–sector (or omni) configuration.

SCt 4812T Lite can expand to a maximum of two frames for a totalof four CDMA carriers per 3–Sector site. Channel Elements are sharedacross carriers and sectors within a frame with up to 192 physicalchannels per frame using MCC1X–48 cards in circuit backhaul modeor 256 physical channels per frame using MCC1X–64 cards in packetmode.

The BTS<–>CBSC interfaces provide control and trafficcommunication paths necessary for operation of the SCt4812TLite base station. The physical interface for all of the framenetwork and communications is located on the top of the frame.

The SCt4812T Lite is supported on R16.1.1 with the MCC1X cardand does not support non–1X BBX cards or non–1X MCCcards. Full use of channel elements for the MCC1X–64 cardrequires packet backhaul.

For Release 17, Motorola is introducing the 1900 MHz SCt4812TLite BTS to compliment the 800 MHz version BTS that wasintroduced in R16.1.1.

S SCt – 4812T–MC Functional Overview – The SCt4812T–MCsingle frame CDMA BTS is Motorola’s 800 MHz High CapacityCDMA Multicarrier base station product and is designed to supportmedium to high density cell sites. The SCt4812T–MC base station isfor indoor applications. It can support up to four (Only three carriersper frame on converted SCt4812T BTSs) CDMA carriers perframe in a 3–Sector, 2–Sector, or OMNI configuration and up totwo CDMA carriers per frame in a 6–Sector configuration. TheSCt 4812T–MC sites can expand to a maximum of two framesfor a total of eight (Only three carriers per frame on convertedSCt4812T BTSs) CDMA carriers per 3–Sector site or up tofour CDMA carriers per 6–Sector site. The SCt4812T–MCarchitecture enables flexible CDMA carrier frequency assignment andrequires only one TX antenna per sector, including the adjacent carrierconfiguration. Channel Elements are shared across carriers and sectorswithin a frame with up to 576 physical channels per frame usingMCC1X–48 cards in circuit backhaul mode or 768 physical channelsper frame using MCC1X–64 cards in packet mode. There are twoinput sources that the SCt4812T–MC can support: 27V and –48Vnominal.

The BTS<–>CBSC interfaces provide control and trafficcommunication paths necessary for operation of the SCt4812T–MC

3



CDMA base stations. The physical interface for all of theframe network and communications is located on the top of theframe for the SCt 4812T–MC.

The SCt4812T–MC frame consists of the following items:redundant power supplies, fan and cooling equipment for theentire frame, doors, two Alarm Monitoring and Reporting(AMR) Boards, two Span I/O Boards, the Site I/O Board, twoClock Synchronization Modules (CSM), two Multi–CouplerPreselector Cards (MPC), two CDMA Clock Distribution (CCD)Modules, two Group Line Interface (GLI2 or GLI3) Cards,MCC1X or MCC24 or MCC8E Cards, BBX1X (LA, or laterversion) cards for both primary and a redundant module (note:BBX2 and BBX1X should not be used due to their drive levellimitation), multi–carrier LPA, PA backplane Combiner/Splitter,Multi–Carrier Trunking Module and TX Filters, HP BBX SwitchCard (C, or later version), HSO, MCIO, and all required frameinstallation hardware. The –48v frame also includes necessarypower conversion equipment.

The SCt4812T–MC is designed for use with internal Multi–ToneCLPAs. The basic Trunking technique utilized in the SCt4812T isenhanced to provide forward power sharing capability across sectorsand carriers. The SCt4812T–MC will provide 81 Watts per carrier (3sectors) when equipped with the 3x3 Enhanced Trunking Module, or108 Watts with the 4x4 ETM. The instantaneous TX power per sectoris limit to the lower of 60 Watts. The SCt4812T–MC is also capableofdelivering 81 Watts per carrier (with a 3x3 ETM) in the Omniconfiguration, but limits to two carriers per antenna and 4 carriers perframe.

The SCt 4812T–MC backplane supports the new MCC1X cardas well as Motorola’s EMAXX Chipset, via the MCC8E andMCC24. For Release 16.0, the MCC1X is available as either aMCC1X–16 (16 channels) or MCC1X–48 (48 channels). Forrelease 16.1, the MCC1X card is available as; MCC1X–16,MCC1X–32, MCC1X–48, and MCC1X–64. The MCC1X–64card requires packet backhaul. All MCC Channel Cards,(MCC1X or MCC8E or MCC24), can be intermixed within asingle CCCP shelf.

3



S SCt4812T–MC 2.1, 1.9 GHz and 800 MHz

The SCt4812T–MC single frame CDMA BTS is Motorola’s HighCapacity CDMA Multicarrier base station product and is designed tosupport medium to high–density cell sites. The SCt4812T–MC basestation is for indoor applications. In a 3–Sector, 2–Sector, or OMNIconfiguration, the SCt4812T–MC can support up to (per frame):

Four 1X CDMA carriersThree DO carriers with MCC–DO redundancyFour carriers in a combination of 1X and DO

Although the SCt4812T–MC can expand to a maximum of threeframes for a total of twelve CDMA carriers, this document describeshardware supported by the Starter frame only. The SCt4812T–MCarchitecture enables flexible CDMA carrier frequency assignment andrequires only one TX antenna per sector, per frame, including theadjacent carrier configuration. Channel Elements are shared acrosscarriers and sectors within a frame with up to 576 physical channelsper frame using MCC1X–48 cards in circuit backhaul mode or 768physical channels per frame using MCC1X–64 cards in packet mode.MCC–DO supports 531 traffic channels per frame. There are twoinput voltage sources that the SCt4812T–MC can support: 27Vand –48V DC nominal.

The BTS<–>CBSC interfaces provide control and trafficcommunication paths necessary for operation of the SCt4812T–MCCDMA base stations. The physical interface for all of the framenetwork and communications is located on top of the SCt4812TMCframe.

The SCt4812T–MC frame accommodates the following items:redundant input DC feeds, redundant power supplies, fan and coolingequipment for the entire frame, doors, two Alarm Monitoring andReporting (AMR) cards, two Span I/O Boards, the Site I/O Board, twoClock Synchronization Modules (CSM), two Multi–CouplerPreselector Cards (MPC), two CDMA Clock Distribution (CCD)Modules, two Group Line Interface (GLI3) Cards, MCC1X Cards,MCC–DO Cards, BBX1X cards for both primary and a redundantmodule multi–tone CLPA, PA backplane Combiner/Splitter, Multi–Carrier Trunking Module and TX Filters, BBX Switch Card, HSO,MCIO, and all required frame installation hardware. The MCC1X cardis available as; MCC1X–16, MCC1X–32, MCC1X–48, andMCC1X–64. The MCC1X–64 card requires packet backhaul toachieve full card capacity. The –48v frame also includes necessarypower conversion equipment.

The SCt4812T–MC is designed for use with internal Multi–ToneCLPAs. The SCt4812T–MC will support standard and high powerconfigurations.

3



Optional Items: Duplexer directional couplers, BTS Router, CSU,EV–DO Kit and CRMS are offered as optional equipment external tothe SCt4812T–MC. (Note: the BTS Router is required for packetmode, optional for circuit mode).

Inputs and Outputs

The BTS and CBSC interfaces provide control and trafficcommunication paths necessary for operation of the SCt 4812CDMA base station. The span line transports both control andtraffic data between the SCt4812 CDMA BTS and the CBSC.The control channel on the span carries the necessary controlinformation to operate the BTS. Traffic data is transported viathe span interface to the appropriate channel–processing elementfor eventual broadcast over the air interface.

For backhaul of 1X high–speed data channels, a number of DS0son a span are reserved just for high–speed data backhaul (Circuitbackhaul). For packet backhaul the high speed data is packetized withthe voice for increased backhaul efficiency.

Span connection to the SCt 4812 CDMA BTS is located at thetop of the SCt 4812 Frame through the Site I/O and Span I/Opanel.

The term BBX will be used when the information isapplicable to both BBX2 and BBX1X. Information specificto one BBX or the other will refer to them by name(BBX2or BBX1X).

NOTE

3



Transmit Path – The SCt 4812T can accommodate up to fourseparate carriers in a three–sector configuration or up to twocarriers in a six–sector configuration in a single frame/cabinet.The TX baseband path begins at the MCC card. Traffic channelinformation is generated by the MCC card, and data is routed tothe BBX module for combining and filtering of transmitteddigital I and Q signals. Each MCC has a direct connection toeach BBX.

The TX RF path begins at the output of the BBX modules. TheBBX generates the CDMA RF signal, which will be amplifiedby the LPAs. A redundant BBX is combined with all sectors andis automatically switched into service in the event of a primaryBBX failure. The BBXs output is routed through the CIO cardin the C–CCP cage to the LPA trunking backplane of each carriervia a cabled connection. The Trunked LPA Sets amplify themodulated transceiver transmit signal. The LPA output connectsto the TX bandpass filter, or cavity combiner modules and isrouted to the TX antenna ports (N type connectors) on the I/OPanel at the top of the BTS. Up to four sector–carrier outputs canbe combined together via cavity combiner(s) to minimize thenumber of TX antennas (see Combiner/Filter section) perframe..

3



Receive Path – For the SCt 4812T, the RX signal path in thestarter frame begins at the N–type RX antenna inputs located onthe I/O Panel at the top of the frame. The signals are routedthrough the RX Tri–filters, located on the I/O Plate, to the MPCmodule on the C–CCP Shelf via coax. A frame is equipped withtwo MPCs, one supporting the main signals and the othersupporting the diversity signals. An MPC module provides lownoise amplification for the incoming RX signals. The MPC outputs arerouted to the Combiner Input/Output (CIO) card via the C–CCPbackplane.

The CIO routes the RF receive signals to the respective BBXcards or BBX Switch cards, and provides the expansion output.A primary BBX card is designated to one and only one sector,which is determined by its slot address (physical address). Theredundant BBX–13 (i.e., The redundant BBX is number 13) canbe connected to any sector via the Switchcard. This configuration allowsthe redundant BBX–13 card to replace any defective primary BBX. AllRX redundant paths are routed from the CIO card to the BBX Switchcard. If a BBX fails, the redundant BBX–13 will detect the fault and willdirect the Switch Card to switch the RF path to the redundant BBX–13,therefore replacing the defective primary BBX. The BBX demodulatesthe RF signals to baseband digital I and Q data. The baseband I and Q isthen routed to the MCC cards for de–spreading.

A BTS can support up to two SCt4812T expansion frames.The first frame in a three–frame configuration is called thestarter; the second and third are referred to as the expansionframes. The first expansion frame receives RX signals from theCIO card in the Starter Frame (after MPC gain). The secondexpansion frame receives RX signals from the CIO card in thefirst expansion frame. The EMPC module in each expansionframe provides lower gain amplification for the incoming RXsignals. The EMPC outputs are routed the same way as thestarter frame..

Intra–frame communications – The LAN facilitates intra–framecommunications in a single–frame cell site and also inter–framecommunications in a multiple–frame cell site. In addition,the LAN also provides the connections for the LocalMaintenance Facility (LMF)..

Inter–cell communications – The Inter–cell Link in theSCt4812T is the Span Line Interface (T1/E1). The Inter–cellLink comprises all digital communication links from the cell siteto the EMX/CBSC or from the cell site to other cell sites. Theselinks include call traffic as well as control information. AChannel Service Unit (CSU) is required for the inter–cellcommunications. The CSU is a customer provided option for theSCt 4812T..

3



Frame Description

The following figure shows a SCt 4812T Frame without doors.

Figure 3-1: SCt 4812T Frame without doors

The frame level components consist of the following items:

S Redundant power supplies, fan and cooling equipment for theentire frame

S (1) C–CCP cage

S (2) Alarm Monitoring and Reporting (AMR) Boards

S (1) Span I/O Board

S (1) Cell Site I/O Board

3



S (2) Clock Synchronization Modules (CSM), one with GPS andone without GPS

S (2) Multi–Coupler Pre–selector Cards (MPC)

S (1) CDMA Clock Distribution (CCD) Module

S (2) Group Line Interface (GLI–2) Cards

S (1) Switch Card

S (1) CIO backplane card (3–S or 6–S)

S All required frame installation hardware

S Doors

The SCt4812T CDMA BTS supports the air interface in any of theseconfigurations:

S Omni–transmit / omni–receive

S 3–sector transmit / 3–sector receive

S 6–sector transmit / 6–sector receive

Module/Card Descriptions

The SCt4812T CDMA frame contains all of the CDMA functions in:

S The Combined CDMA Channel Processor (C–CCP) Cage, and

S The CDMA Trunked Linear Power Amplifier (T–LPA) Shelf

The CCP Cage includes the following items:

S MCC–8, MCC–24 and/or MCC1X (16, 32,48 or 64)

S BBX2 and/or BBX1X

S CIO

S CSM

S AMR

S CCD

S HSO/LFR

S MPC

S Power Supply Converter Card

S Switch Card

C–CCP Cage – The single SCt4812T C–CCP shelf provides the spanline interfaces, channel processing, shelf control, and CDMAtransceivers. The SCt4812T C–CCP cage supports up to a total of 12sector–carriers (e.g., 3–sector, 4–carrier or 6–sector, 2–carrier) and up to768 physical channels (using MCC1X 64 cards).

A fully loaded 1X C–CCP shelf houses the following:

S (13) Broad Band Transceiver boards (BBX–1X s), one per sectorper carrier with one redundant

S (12) Multi–Channel CDMA cards (MCC1X)

S (1) Switch card

3



S (1) Combiner Input/Output (CIO) board

S (2) Multi–Coupler Pre–selectors cards (MPCs)

S (2) Alarm Module Reporting (AMR) boards

S (2) Clock Synchronization Manager

S (1) Rubidium High Stability Oscillator (HSO)

S (2) Clock Distribution Modules (CCD)

S (2 or 3) power supply boards

The CDMA T–LPA Shelf includes the following items:

S CDMA T–LPAs

S Trunking Module(s)

S Combiners/Filters

Signal Flow

The following figure illustrates the signal flow in the SCt 4812T.

3



Figure 3-2: SCt 4812T Signal Flow

3



Redundancy

The SCt4812T has components that are redundant by one of threemethods: N+1, 2N, or soft–fail. N+1: MCC, BBX, P/S. 2N: GLI,CSM/CCD, AMR. Soft–Fail: LPA, MPC.

MCC – Overhead channel redundancy is presently supported byequipping N+1 MCCs, where N is equal to the number of MCCcards required to support traffic and overhead channels (withoutredundancy). For overhead channel redundancy, a three–sectoror Omni configuration requires a minimum of two MCCs, and asix–sector configuration requires a minimum of three MCCcards.

P/S – To maintain Power Supply redundancy, a minimum of twosupplies are required for a 1 or 2 carrier, 3–sector C–CCP andSCCP shelf. When carrier 3 through 4 are added to a 3–sector C–CCPcage, a third power supply must be added. A minimum oftwo supplies are required for a 1 carrier, 6–sector C–CCP shelf.A minimum of 3 power supplies must be used when a secondcarrier is added to a 6–sector frame. In other words: Two cardswill support operation of up to 6 sector carriers. Three cards willalways be required when seven or more sector carriers are in use.

T–LPA – The four linear power amplifiers (LPAs) per threesectors of one carrier are combined in soft–fail redundancy. Insoft–fail redundancy, none of the sectors go out of service if anLPA module fails. In the event of an ST–LPA failure, the LPAmodule takes itself out of service, sends an alarm to the GLI2,and directs the three sectors supported by that LPA module tooperate at 2.5 dB reduced power. Each trunked LPA Setoperates independently and is monitored separately. Monitoringand control of the LPAs is via the RS485 bus to the GLI2. TheGroup Line Interface (GLI2) queries the LPAs for: alarm status,parameters involving Intermodulation Distortion (IM)suppression, electronic ID, and the general state of the device.

For 800 Mhz BTS, the T–LPA is being replaced by the C–LPA.Trunked Power is defined as serving multiple sectors with a bankof shared CLPAs. In this shared (or trunked) arrangement, power isdynamically allocated to each sector as required and thus provides highereffective power with fewer CLPA modules.

Space for up to two Trunked CLPA Sets may be equipped ineach SCt 4812 XX CDMA frame. in the 4812T/T Lite. EachTrunked CLPA Set consists of three (CLPA) modules, two fanmodules, and a trunking backplane.

3



The linear power amplifiers (CLPAs) per three sectors of onecarrier are combined in soft–fail redundancy. In soft–failredundancy, none of the sectors go out of service if a CLPAmodule fails. In the event of an CLPA failure, the CLPA moduletakes itself out of service, sends an alarm to the GLI, and thethree sectors supported by that CLPA module operate atapproximately 3.5 dB reduced power. Each Trunked CLPA Setoperates independently and is monitored separately. Monitoringand control of the CLPAs is via the RS485 bus to the GLI. TheGroup Line Interface (GLI) queries the CLPAs for: Alarm status,Parameters involving Intermodulation Distortion (IM)suppression, Electronic ID, and the General state of device.

Operations and Maintenance

The Operations and Maintenance Center for the radio (OMC–R)operates as the user interface for the SCt 4812 system andsupports daily management of the cellular network. The OMC–R,located at the CBSC, manages subsystem events and alarms,performance, configuration, and security.

SCt 4812T 1X and PacketBackhaul Upgrade BTS

Function

System release 16.0 introduces cdma2000 1X functionality intoIS–95A/B systems. SCt4812 platform frames deployed in thefield can be upgraded to support cdma2000 1X along with IS–95A/B. System release 16.1 introduces full packet backhaul.

The upgraded BTS provides the signal processing functionsnecessary to implement the various IS–95A/B CDMA channelfunctions including the pilot channel, sync channel, pagingchannel, access channel, and fundamental channels. In addition,sites that have installed the cdma2000 1X capabilities cansupport supplemental channels.

Card Descriptions

There are two types of cards required to upgrade the SCt 4812BTS to support cdma2000 1X in release 16.0.

S MCC–1X

S BBX–1X

There are two additional pieces of equipment required toupgrade the SCt 4812 BTS to support cdma2000 1X data packetbackhaul in release 16.1.

S GLI3

S BTS Router

Starting with release 16.4.1, the system release software will allow theGLI3 card to support cdma2000 1X data packet backhaul. This optionrequires no new BTS hardware other than the GLI3 card.

3



Signal Flow

See the signal flow section for the SCt 4812.

Redundancy

The basic redundancy requirements for the MCC–1X and BBX–1Xcards are listed below.

S MCC–1X: N+1 redundancy

S BBX–1X: N+1 redundancy

The basic redundancy requirements for the packet backhaul upgradeelements are listed below.

S GLI3: 2N redundancy

S BTS Router: 2N redundancy

Expansion SCt 4812T

Description

With an Option B overlay, an SCt 4812T expansion frame withthe current equipment needs to be added if present frames arefully utilized. With these deployments, the legacy equipmentwill continue to support IS–95A/B traffic, while the SCt 4812Twill support cdma2000 1X traffic. The table below outlineswhich types of SCt4812T frames are compatible with thelegacy equipment.

Table 3-1: Legacy Overlay Options

Legacy Product Overlay Options

HDII SCt 4812T Modem Frame 1

SCt 9600/9650 SCt 4812T Modem Frame 1

SCt 2400 SCt 4812T Expansion Frame 1

SCt 2450 SCt 4812T Expansion Frame 1

SCt 4850/2 SCt 4812T Expansion Frame 1

NOTE1. Only option available.

3



SCt480

Description

The SCt480 is the new primary MicroCell in the SCt BTS portfolio.

Function

The SCt480 is available as an indoor and outdoor (with additionalequipment) unit operating at 800 MHz or 1.9 GHz. It is available at–48V for China A Band and at +27V both A and B band. This is amedium to low density site.

The SCt480 is an Omni, two carrier site which supports IS95, 1X and1xEV–DO. Expansion BTS configurations are also supported so that upto 3 units can be added to the base unit to support up to 8 carriers.

The outdoor configuration only supports 2 expansion frames for up to 6carriers. The 800 MHz SCt480 is capable of either circuit or packet(with Integrated BTS Router) backhaul, whereas the 1.9 GHz onlysupports packet backhaul. A mixture of backhauls is not supported.

The SCt480 utilizes several cards from the macro BTS product lines toreduce the number of configuration options for Motorola BTS’ andenable re–use of cards between the micro and macro BTS frames.

Inputs and Outputs

The BTS and CBSC interfaces provide control and trafficcommunication paths necessary for operation of the SCt480 CDMAbase station. The span line transports both control and traffic databetween the SCt480 CDMA BTS and the CBSC. The control channelon the span carries the necessary control information to operate the BTS.Traffic data is transported via the span interface to the appropriatechannel–processing element for eventual broadcast over the air interface.

For backhaul of 1X high–speed data channels, a number of DS0s on aspan are reserved just for high–speed data backhaul (Circuit backhaul).For packet backhaul the high speed data is packetized with the voice forincreased backhaul efficiency.

Span connection to the SCt480 CDMA BTS is located at the top of theSCt480 Frame through the Site I/O and Span I/O panel.

Application Considerations

This section provides information on the basic operation of the SCt480by discussing the following topics:

S Transmit path

S Receive path

S Intra–frame communications

S Inter–cell communications

3



The term BBX will be used when the information isapplicable BBX1X only.

NOTE

Transmit Path

The SCt480 can accommodate up to two separate carriers in a omniconfiguration in a single frame. The TX baseband path begins at theMCC card. Traffic channel information is generated by the MCC card,and data is routed to the BBX module for combining and filtering oftransmitted digital I and Q signals. Each MCC has a direct connection toeach BBX.

The TX RF path begins at the output of the BBX modules. The BBXgenerates the CDMA RF signal, which will be amplified by the cCLPAs.The BBXs output is routed through the CIO card in the CCP2 cage tothe cCLPA via a cabled connection.

Receive Path

For the SCt480, the RX signal path in the starter frame begins at theRX antenna input located on the I/O Panel. The signals are routedthrough to the cMPC module on the CCP2 Cage. A frame is equippedwith one cMPC supporting both the main and diversity signals. A cMPCmodule provides low noise amplification for the incoming RX signals.The cMPC outputs are routed to the BIO card via the CCP2 backplane.

The BIO routes the RF receive signals to the respective BBX cards andprovides the expansion output. The BBX demodulates the RF signals tobaseband digital I and Q data. The baseband I and Q is then routed to theMCC cards for de–spreading.

An SCt480 BTS can support up to three SCt480 expansion frames.The first frame in a four–frame configuration is called the starter; thesecond, third and fourth are referred to as the expansion frames.

Intra–frame Communications

The LAN facilitates intra–frame communications in a single–frame cellsite and also inter–frame communications in a multiple–frame cell site.In addition, the LAN also provides the connections for the LocalMaintenance Facility (LMF).

Inter–frame Communications

The Inter–cell Link in the SCt480 is the Span Line Interface (T1/E1).The Inter–cell Link comprises all digital communication links from thecell site to the CBSC or from the cell site to other cell sites. These linksinclude call traffic as well as control information. A Channel ServiceUnit (CSU) is required for the inter–cell communications. The CSU is acustomer provided option for the SCt480.

Frame Description

A fully loaded CCP2 cage houses the following:

3



S (2) Broad Band Transceiver boards (BBX–1Xs), one per carrier

S (3) Multi–Channel CDMA cards (MCC1X) or (2) MCC–DO +MCC1X

S (1) Group Line Interface (GLI3)

S (1) Clock Synchronization and Alarms Card (CSA)

S (1) compact Multi–Coupler Pre–selector card (cMPC)

S (1) High Stability Oscillator (HSO) or (1) Medium Stability Oscillator(MSO)

S (1) CCP2 Cage Power Supply Card

Figure 3-3: SCt480 Chassis Layout

3



Signal Flow

The following figure illustrates the signal flow of the SCt480.

Figure 3-4: SCt480 Signal Flow

Redundancy

MCC – Overhead channel redundancy is presently supported byequipping N+1 MCCs, where N is equal to the number of MCC cardsrequired to support traffic and overhead channels (without redundancy).For overhead channel redundancy, an Omni configuration requires aminimum of two MCCs.

O&M

The Operations and Maintenance Center for the radio (OMC–R) operatesas the user interface for the SCt480 system and supports dailymanagement of the cellular network. The OMC–R, located at the CBSC,manages subsystem events and alarms, performance, configuration, andsecurity.

3



Integrated BTS Router

Starting with system release G16.4.1, the GLI3 will be capable ofproviding low capacity, two–span, integrated packet routingfunctionality capable of supporting up to 120 simultaneous calls(assuming 8k EVRC.)

This is implemented through software upgrade at the BTS. ExistingGLI3 hardware installed in the field can be upgraded with software tosupport integrated BTS router (IBR) functionality.

When the GLI3 is upgraded to IBR, the external BTS router is notnecessary to support the first packet span. When additional packetcapacity is required, an external BTS router group (redundant ornon–redundant) can be added to support up to four physical T1 or E1packet spans per C–CAP shelf.

Logical BTS configurations and fractional spans are not currentlysupporting IBR.

The IBR is also compatible with the SCt4812 BTS family and theSCt480 BTS. Configuring the GLI3 as an IBR will limit support of upto eight MAC modules in the SCt4812, SCt4812T, SCt4812T–MC,and SCt4812ET C–CCP shelf; and, IBR will limit support of up tothree MCC1X modules in the SCt4812T–Lite and SCt4812ET–LiteC–CCP shelf.

SCt4812T–MC CDMA BTS 2.1GHz

Description

The SCt4812T–MC single frame CDMA BTS is Motorola’s 2.1 GHzHigh Capacity CDMA Multicarrier base station product and is designedto support medium to high–density cell sites. The SCt4812T–MC basestation is for indoor applications. In a 3–Sector, 2–Sector, or OMNIconfiguration, the SCt4812T–MC can support up to (per frame):

S Four 1X CDMA carriers

S Three DO carriers with MCC–DO redundancy

S Four carriers in a combination of 1X and DO

Function

Although the SCt4812T–MC can expand to a maximum of threeframes for a total of twelve CDMA carriers, this document describeshardware supported by the Starter frame only.

The SCt4812T–MC architecture enables flexible CDMA carrierfrequency assignment and requires only one TX antenna per sector, perframe, including the adjacent carrier configuration.

Channel Elements are shared across carriers and sectors within a framewith up to 576 physical channels per frame using MCC1X–48 cards incircuit backhaul mode or 768 physical channels per frame usingMCC1X–64 cards in packet mode. MCC–DO supports 531 trafficchannels per frame.

3



There are two input voltage sources that the SCt4812T–MC cansupport: 27V and –48V DC nominal.

Inputs and Outputs

The BTS<–>CBSC interfaces provide control and traffic communicationpaths necessary for operation of the SCt4812T–MC CDMA basestations. The physical interface for all of the frame network andcommunications is located on top of the SCt4812T–MC frame.

Frame Description

The SCt4812T–MC frame accommodates the following items:

S Redundant input DC feeds

S Redundant power supplies

S Fan and cooling equipment for the entire frame

S Doors

S (2) Alarm Monitoring and Reporting (AMR) cards

S (2) Span I/O Boards

S (1) Site I/O Board

S (1) Clock Synchronization Modules (CSM)

S (1) Multi–Coupler Preselector Cards (MPC)

S (2) CDMA Clock Distribution (CCD) Modules

S (2) Group Line Interface (GLI3) Cards

S MCC1X Cards

S MCC–DO Cards

S BBX1X cards for both primary and a redundant module multi–toneCLPA

S PA backplane Combiner/Splitter

S Multi–Carrier Trunking Module and TX Filters

S BBX Switch Card

S HSO

S MCIO

S All required frame installation hardware

The –48v frame also includes necessary power conversion equipment.

The MCC1X card is available as; MCC1X–16, MCC1X–32,MCC1X–48, and MCC1X–64. The MCC1X–64 card requires packetbackhaul to achieve full card capacity.

The SCt4812T–MC is designed for use with internal Multi–ToneCLPAs. The SCt4812T–MC will support standard and high powerconfigurations.

Optional Items: Duplexer directional couplers, BTS Router, CSU,EV–DO Kit, and CRMS are offered as optional equipment external tothe SCt4812T–MC. (Note: the BTS Router is required for packetmode, optional for circuit mode).

3



Figure 3-5: SCt 4812T–MC (+27v Left) (–48vRight) Frame (shown without doors)

3



SC4812T–MC Dynamic PAFunctionality

In addition to the efficient use of RF power, the SCt4812T–MCintroduces the ability for operators to add carriers to the BTS withouthaving to add LPAs. This enables operators to size their power to fit therequirements of each site. This enhancement significantly reduces costs,operating expenses, and increases flexibility. Operators now have thechoice to add CLPA Sets or not as carriers are added based on each sitesrequirements.

Rural Cell Enabler

Sometimes called “MOTOBOOMER”, the rural cell enabler is asoftware modification offering greatly extended range for Motorola BTS.The feature can support a cell radius of 180 km. vs. the 56 previouslysupported. The applications are typically Marine/coastal and lowcapacity rural environments. The feature is supported only on theMCC1X card and is available on SCt 4812, SCt480 BTS usingBBX1X and either GLI2 or GLI3. Because of propagation time at theextended distances, there are PN offset considerations. Consultdocumentation for details.

3

GLI3 Functional Description


Function

The GLI3 can only be deployed starting with System Release 16.1, andis not operable on prior releases. The GLI3 card is added to the BTS inplace of the GLI card to enable the packet data backhaul feature. TheGLI3 is equipped to support packet operation and also supportsoperation in 1X circuit and circuit mode.

Inputs and Outputs

While all the inputs and outputs are bidirectional, the inputs from theBTS are from the MCC24/8E (IS95A/B) and MCC1X cards. The inputsfrom the CBSC side are packet streams, which are combined by the BTSrouter to form a single stream or a split span (circuit backhaul) transportdepending upon the backhaul type.

Card Description

The GLI3 will meet the following circuit functions:

S Packet Functionality Overlays Circuit

S All existing circuit functions on GLI2 supported

S New Functions for Packet Operation

S Ethernet Switch (Four 100BASE–T ports on front panel)

S GLI3 interconnect (one 100BASE–T)

S Packet router interconnect (two 100BASE–T RJ–45s)

S Auxiliary/Monitor Port (100BASE–T RJ–45)

S CHI Block for packet protocol translation

S Translates between IP and efficient CHI format

S Provides IP termination for MCCs

Signal Flow

See the “Inputs and Outputs” section for the BTS router.

Redundancy

Redundancy for the GLI3 is 2N with a spare GLI3 per cage.

3

GLI 3 Functional Description – continued


O & M

Two new O&M concepts require some additional explanation for 16.1:

16.1 will introduce a new maintenance paradigm called SMNE (SelfManaged Network Elements). Under the old paradigm, elements wouldreport a fault to a central location and the location would then tell thereporting unit what to do or direct the information to maintenance foraction. Under the new paradigm, the management is de–centralized andthe elements will usually take care of any required action and then reportthe action and result only for record keeping. Much of the SMNE piecefor the BTS will be resident on the GLI3 card. SMNE operation willonly begin to function when the BTS is in the Packet mode.

The second concept for O&M new in 16.1 is that of the “O&M straw”for the BTS Router while the BTS is in the circuit mode. The BTSRouter is essentially a Network Element and would normally get itsO&M information via a packet based backhaul. When the BTS is still inthe circuit mode (before cutover to the packet mode) the BTS Routermust get its O&M information via a dedicated DS0 that is routedthrough the GLI3 as part of the cutover preparation and this DS0 isprovisioned and sent to the BTS router so it can perform the O&M whilestill in the circuit mode.

3

BTS Router Functional Description


BTS Router

Function

The BTS Router (MWR1941) is required to implement packet backhaulat all MacroCell BTS sites that can be upgraded to support 1X (SCt4812 platform). The BTS Router essentially interfaces the packet datastream generated by the GLI3 card to the Span based backhaul to theMGX. It is used to provide bandwidth efficient IP transport of voice anddata bearer traffic, as well as maintenance, control and signaling trafficfor backhaul to the AN in the RAN. The BTS Router is a multi functiondevice with the following basic capabilities.

S High–Performance PPPmux/cUDP Implementation

S Compatible with the Severe Environmental Conditions at a BTS

S Full Remote Management Support via OMCR/CMP Application

Three implementations of the BTS router are available in the 2.17.0.xproduct:

S Redundant BTS Router offers redundant protection ofpacket–backhaul span interface

S Non–redundant BTS Router offers packet backhaul without redundantprotection.

S Integrated BTS router offers low capacity routing using resources onthe GLI card. This reduces available use of MCC slots in the C–CCPcage by 1 chi bus.

Inputs and Outputs

The inputs and outputs are bi–directional. When viewing the BTSRouter from the MGX or DACs, the inputs are T1 or E1. Coming from aDACs or MGX, and the outputs are 100Base T Ethernet going to theGLI3 cards.

3

BTS Router Functional Description – continued



There are numerous configurations for the BTS router. Some sites mayrequire multiple routers per site depending on span count. The BTSrouter can terminate up to four physical T1 or E1 span lines. However, aBTS Router equipped with E1 WICs will support the capacity of up tothree full E1 spans. This does not preclude the physical termination ofup to four E1 span lines since lines will be balanced. The BTS router canbe deployed in fully redundant configuration, which requires two routersor a non–redundant configuration, which require only one router. Onlyone BTS Router/pair is supported per modem frame.

The figure below illustrates the typical configuration.

Figure 3-6: Typical BTS Router Configuration

Card Description

Each BTS router comes with one WIC (WAN Interface Card), which isthe interface for the two span lines. An additional WIC can be added toprovide two more span lines. The BTS Router is intended to be installedin redundant pairs and can be expanded with additional pairs of routers.

Signal Flow

See “Inputs and Outputs”.

3



Redundancy

The BTS Router can be deployed in redundant pairs and will supportredundancy via Hot–Standby Router Protocol ensuring that only a singlerouter is actively controlling the span interfaces. A relay switch isintegral to the WIC and will allow the spans to be Y–cabled to bothrouters.

Once an active BTS Router has been elected, that router attempts toactivate one (or more) PPP links on the span interfaces. The definition ofthese initial PPP links (span and timeslots) is stored in non–volatilememory on both the routers. This memory may be updated either locallyvia a terminal or remotely via the OMCR/CMP support application.

After an initial PPP link has been established over the span lines, DHCPand TFTP are used to locate and transfer any additional configurationinformation. SNMP and Telnet are used for general access and control.

If a router is unable to establish a PPP link within a reasonabletimeframe, it will relinquish control of the span interface and allow theredundant router to attempt establishment of the PPP link. Thisfunctionality will allow the system to recover from failure in the spaninterface electronics of a router.

OSPF routing control is used to detect and recover from any failures inthe WAN or LAN interconnects.

BTS Router redundancy is capable of operating in both packet andcircuit mode.

O & M

The Mobile Wireless Center (MWC) is an application that willimplement the workflow steps necessary to configure the BTS Router,the MGX, and the MGX RPM card. Considered a piece of the overallworkflow, MWC will provide a template based configuration generationand deployment function. The MWC, through an API interface, willpopulate configurations and on a transactional basis assure thedeployment of the configuration. If the configuration action fails, thedevice can be rolled back to its previous version, thereby assuringconsistency and accuracy within the network. The naming convention ofthe devices will be mapped and persisted for use by components of theOMC–IP. The APIs for the MWC will be abstract to provide the mostflexibility and deployment and isolate the configuration specifics fromthe higher–level applications such as the OMC–R and other managementsystems.

The OMC–IP will be the collector of all alarm and event informationrequired for the BTS routers via MWFM. CW4MW will forward thealarms from the BTS routers directly to UNO via SNMP.

3



Integrated BTS Router

Starting with system release 2.16.4.1.x, the GLI3 will be capable ofproviding low capacity, two–span, integrated packet routingfunctionality capable of supporting up to 120 simultaneous calls per span(assuming 1x EVRC).

This is implemented through software upgrade at the BTS. ExistingGLI3 hardware installed in the field can be upgraded with software tosupport Integrated BTS Router (IBR) functionality.

When the GLI3 is upgraded to IBR, the external BTS router is notnecessary to support the first packet span(s). When additional packetcapacity is required, an external BTS router group (redundant ornon–redundant) can be added to support up to four physical T1 or E1packet spans per CCP shelf.

Logical BTS configurations and fractional spans are not currentlysupported with IBR.

The IBR is compatible with the SC4812 BTS family and the SC480BTS. Configuring the GLI3 as an IBR will limit support of up to eightMCC modules in the SC4812, SC4812T, SC4812T–MC, and SC4812ETC–CCP shelf; and, IBR will limit support of up to three MCC modulesin the SC4812T–Lite and SC4812ET–Lite C–CCP shelf.

3


Chapter 4: Digital Access and Cross–Connect System (DACs)

Table of Contents

Digital Access and Cross–Connect System (DACs) 4-1. . . . . . . . . . . . . . . . . . . . . Overview 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DACs Description 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4



Notes

4

Digital Access and Cross–Connect System (DACs)


Chapter Overview/Function

For 17.0 the DACs is not required in packet backhaul. The DACs canstill be used to do span grooming that may be required in certainnetwork topologies. The split backhaul is still allowed as a supportedconfiguration for circuit backhaul for 1X Data. For the SC3XX series ofBTS the DACSs is still needed. The information in this chapter isretained for those who wish to use a split backhaul.

Some customers have chosen to use the DACs to concentrate lines fromT1 to T3 and they may choose to retain the DACs for flexibility innetwork configuration.

A new Digital Cross–connect can be required with the VPU and thisdocument will use the acronym DCS to distinguish it from the DACs.

DACs Description

Network operators must supply their own DACs, selecting the unit thatbest meets the needs of their specific network.

Function

To function properly, for this application, the DACS selected shouldmeet the following requirements:

S Able to cross connect at a 64k bit DS0 signal level in the format of theoperator’s spans. If this condition is not meant, the operator mustensure that all system elements are compatible with the appliedscheme and any required system settings are planned for

S Able to handle E1, T1, J1 inputs as required by the customer

S Compatible with network management supplied by the customer

S Utilize redundant configuration (optional)

S Able to handle backhaul specified in the backhaul plan for the system

Inputs/Outputs

Input for the DACs is a mixture of unsorted voice, circuit–based data,and packet–based data.

Output consists of the following traffic streams:

S Voice and base channel 1X Data: Traveling to the transcoder (XC),located on the Central Base Station Controller (CBSC) if splitbackhaul is retained. SCH data traveling to the AN.

S Packet–based data: and voice traveling to the MGX if Packet backhaulis implemented

4

Digital Access and Cross–Connect System (DACs) – continued


For the split backhaul application where Fundamental datachannels are backhauled to the XC MSI, the Fundamentaldata channels are routed to the XC PSI–CE for circuit topacket conversion and eventual combination with thesupplemental channels.With packet backhaul, the FCH and SCH is sent to the AN(MGX).

NOTE

To accommodate the necessary sorting, the DS0s used for 1X data willbe grouped contiguously in the bearer medium. That grouping is referredto as a “packet pipe.”

For information about the restrictions placed on packet pipes, refer toFigure 4-1.

Figure 4-1: DACs Illustration

The remaining DS0s in a span are assigned to voice (1X or IS 95 A/B)or circuit–based data (IS95A). Combining packet pipe and voice on thesame circuit–based transport is sometimes referred to as “mixedbackhaul” or “packet pipe backhaul”.

4



The total backhaul will include all the IS 95 A/B voice anddata that existing systems may have had in place, as well asthe 1X data and voice.

IMPORTANT

*


Refer to the documentation provided with your specific DACs.

Card Descriptions

For information about the cards in your DACs, refer to thedocumentation that came with the unit(s).

Signal Flow

In release 16.0 and succeeding releases, if circuit backhaul is retained,voice and data are backhauled from the various Base TransceiverStations (BTSs) through a circuit–based network to the CBSC. There,the DACs separates voice from data activity, routing voice and data callFCHs to the transcoder (XC) and data call SCHs to the AN.

In Release 16.1, 16.3, 16.5, and 17.0, the backhaul can be converted topacket. With the packet backhaul conversion, both voice and data areco–mingled on the same backhaul with the separation being made viainformation contained in the packet. All Packetized information flowsthrough the MGX (this requires a significant increase in capacity of theMGX).

Redundancy

Unless a redundant backhaul is used, the DACs will remain a singlepoint of failure. To limit any possible downtime in a failure, it isadvisable to have a documented contingency plan for either getting to analternate configuration or replacing a DACs.

Operation and Maintenance

For more specific information about the operation and maintenance ofyour DACs, refer to the documentation that came with the DACs. Themanagement of DACs is not included in Motorola provided O&M.

4



Notes

4


Chapter 5: CBSC

Table of Contents

CBSC 5-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PSI Cards 5-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIB Cards 5-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MMll 5-13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobility Manager II 5-13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5



Notes

5

CBSC


Introduction

Release 17.0 continues the evolution of the Motorola CDMA producttowards an all IP based RAN. Please refer to the MM II section to betterunderstand the convergence of the IP transport and RAN network.

The introduction of the VPU introduces the need for a newPSI resource type called the PSI–Ter if the cIWU isattached at the XC. The VPU requires an SDU so mostcustomers will probably have PSI cards but additionalPBIB–ESs may be required.

NOTE

There is a change in terminology in this version vs.previous versions. The previously referred to PSI (ce) isnow called PSI (pktif) to align with the O&Midentification of the element.

NOTE

This chapter covers those CBSC items added in 16.0 and reviews howthey are affected in 16.3.

S Packet Subrate Interface (PSI) cards: This card has multiplefunctions in 16.3.

S Packet BIB cards: The PBIB–ES and the PBIB–E cards are requiredto interface between PSI cards and the data network.

Overview

The CBSC contains the XC and the MM. This chapter will focus onchanges to the XC.

MM Overview

The MM is the main focal point for call processing in the CBSC/SDU. Itdirects the sequence of a call in the CBSC/SDU by maintaining stateinformation for the call and responding to message input from the othersubsystems. When messages are received from other subsystems, theMM decides what action, if any, should be taken next and invokes thataction by sending a message(s) to other subsystem(s).

During the course of a call setup, exceptions may occur which mandatethat the call be released. Examples of these exceptions include subscribervalidation failure in the MSC, no resources available, and failure of themobile to acquire an assigned TCH. The MM has the responsibility ofdetecting call setup exceptions, either via message receipt from the othersubsystems or internally, and subsequently taking the appropriate action.

In the 16.0 release, the MM communicates with devices through theTransport Network (TN).

5

CBSC – continued


The MM provides the following radio resource management functions:

S Functional Element Coordinator

S Handoff Management

S Global RF Resource Management

S Collection of Statistics

Functional Element Coordinator – the MM serves as the coordinatorbetween the various BSS functional elements for the establishment ofcalls within the BSS. Essentially, for a given call, the serving MM is thecentral point of control for that call. This centralization shields otherBSS elements from architectural changes.

Handoff Management – the MM handles management of handoffprocessing within the RAN and coordination of other access networkelements to orchestrate handoffs. The control point for handoffs is theRadio Network Control Server (RNCS). The RNCS is a control functionthat provides interworking between the BTS and the core voice and dataservice. The RNCS establishes radio access call legs and provides radioresource management call control. The handoff control that the RNCShas includes the inter–BTS, intra–BTS, inter–RNCS, intra–RNCS andsoft handoffs. In most cases, these handoffs are negotiated amongRNCS(s) of the involved RAN(s) without involvement from the corenetwork.

Global RF Resource Management – The MM provides global RFresource management and admission control of connections andconnection attributes (e.g., data service bandwidth) based upon RFresource conditions.

Collection of Statistics – The MM is responsible for collecting statisticsused for RF resource utilization (analogous to current performancemanagement statistics). The MM is also responsible for the collection ofper–call information and generation of post call records (such as a CallDetail Log) or in real–time via trace facilities.

MSC Interface

As indicated, a major functionality of the MM is the interface to theMSC. The MSC is responsible for receiving the Subscribed Rateparameter provisioned in the subscriber record in the HLR and thenpassing it onto the RAN. The Subscribed Rate parameter is themaximum allowable data rate that a subscriber can be assigned forIS–2000 1X packet data services. It defines restrictions on the level ofpacket data service that is to be provided to a subscriber on both theforward and reverse channels. The following Subscribed Rate forwardand reverse channel data rates are applicable to IS–2000 1X:

S 9.6 Kbps

S 14.4 Kbps

S 19.2 Kbps

S 28.8 Kbps

S 38.4 Kbps

5

CBSC – continued


S 57.6 Kbps

S 76.8 Kbps

S 115.2 Kbps

S 144 Kbps

S 153.6 Kbps

When the operator defines a default/override Subscribed Rate parametervalue for roamers, this will be used by the MSC to validate servicerequests. The MSC will meet the general requirement to allow fordefault/override capability through the Roamer Profile Override feature.The Roamer Profile Override enables operators to override certainfeatures and functions of a visiting subscriber otherwise specified bytheir home system. The default/override capability provides defaultCDMA Service Option List and Subscribed Rate values for a servingnetwork. It supports the new IS–2000 1X service option, 33. Also, theMSC will maintain usage statistics for the CDMA Service OptionList and Subscribed Rate override capabilities.

The MSC also queries the VLR for the IS–2000 Mobile Capabilitiesinformation when it initiates some paging operation to the mobile (suchas voice call or SMS).

Starting in release 16.5, the MM – MSC interface supports:

S Service Option 35 and 36, for both mobile origination andtermination, enabling idle mobile Location Based services. The basicCBSC (MM/XC), SDU, and SDU/VPU systems support thisfunctionality. Position Location Data is transported over the IS–2000Interface via the Data Burst message and over the A1 interface via theADDS Deliver message. The exchange is transported as signalingtraffic. No bearer traffic will be supported with these service options.

S Smart paging for Short Message Service (SMS) Page messages. SmartPaging allows paging of a limited area, rather than a large generalpaging area. Smart SMS Paging provides an enhancement to thesystem’s delivery of messages to a CDMA mobile station. Thisenhancement includes the capability to page a mobile (via the CAI:General Page message) to determine its availability and cell locationbefore delivering the SMS payload to the mobile (via the CAI: DataBurst Message). The selection of the cells/sectors that will transmitthe CAI: Data Burst Message will be based on the mobile and basestation capabilities. Following transmission of the CAI: Data Burstmessage, the RAN will release the mobile.

5

CBSC – continued


S ESN Verification for Smart SMS: With this feature, the SMS messageis delivered over the sector paging channel only after receipt of a pageresponse message from a mobile with a valid ESN. Because themobile is paged first in the Smart SMS algorithm, the mobileresponds with a CAI: Page Response Message (PRM) which containsthe mobile ESN. This feature provides the MSC with the functionalityto include the ESN in the A1: ADDS Page message and the RAN withthe functionality to receive the ESN and store it for later verification.Thus, when the mobile responds with its ESN in the CAI: PRMmessage, the RAN can compare it to the one saved from the MSC. Ifthe ESNs are the same, the RAN continues with Smart SMSfunctionality by sending out the CAI: Data Burst Message (DBM). Ifthe ESNs do not match, the RAN will ignore the received CAI: PRMand continue to wait until the T42m expires, processing any additionalCAI: PRM received during that time. Delivery of the ESN from theMSC will also need to be supported for intersystem (ANSI–41 andDMX) scenarios as well. If the RAN does not receive an ESN in theA1: ADDS Page, Smart SMS will continue but no ESN verificationwill be provided.

SDU functions

Beginning in the 16.1 release, the MM/RNCS will manage devicescalled the Selector Distribution Units (SDU) as a pool of servers. Amethod will be implemented to “flag” the presence of the SDU andensure proper load balance across the SDUs. The MM will interact withthe SDU for SDU element allocation/assignment andde–allocation/disconnect, and as well for handoff process sequencing andresource/bandwidth negotiation. Some of the data now gathered in theMM to build the CDL will be migrated to the SDU in release 16.1.

XC Overview

The XC (transcoder) along with the MM combine to make the CBSC.The transcoding function is required in a CDMA system to convert56Kbps/64Kbps PCM signals into 8Kbps (optional 13Kbps) encodedsignals and vice versa. The switching capability within the XC is used toconcentrate lightly loaded T1/E1 coming from the base stations into afewer number of fully loaded T1/E1 going to the MSC. This alsoprovides a common point of interface for many BTSs. The switchingfunction additionally separates control and TCHs coming from the BTS.Traffic channels are sent via the XCDR cards to the MSC, and thecontrol channels are routed to the MM. Lastly, while the CBSC selectsthe radio channel, the land–side circuits are selected in an A+ (IS–634)interface compliant manner. The switching matrix is used to connect thetwo together. The switching matrix also allows Intra–BTS andInter–BTS handoffs to be performed with a minimal involvement of theMSC when radio channel paths involved in the handoff are connected tothe same CBSC.

5

CBSC – continued


Each XC cage contains two sizes of cards and boards. The larger card isreferred to as a full–size card. These include GPROC (or EGP),KSW/DSW, GCLK, XCDR, MSI, and BUS Terminator cards. Thesmaller cards in the same cage are referred to as the half size cards.These include the KSWX/DSWX, CLKX, and LANX. Allshelf–to–shelf interconnections on the transcoder frame are obtained byinterconnecting via fiber optic cable using only the half size cards. Newto 16.0 is the Packet Subrate Interface (PSI) card that enables newnetwork elements using IP–based communication to work with legacynetwork elements. The PSI has both circuit and packet configurationswithin one unit. It supports circuit voice/data and packet data for the 1Xsystem. The data from the RAN is converted from ethernet on thepacket side to internal protocols of the XC on the circuit side.Essentially, the PSI is a bridge and a router between the circuit networkof the XC and the packet network of the RAN for bearer (STRAU <–>IS–634 conversion) and call control traffic.

PSI Cards

Description

The PSI card can best be described as a highly programmable I/Oprocessor. It is essentially a packet capable version of the MultipleSpan–line Interface (MSI) card.

Function

Overview

Depending on which software is loaded on it, the same physical PSI cardcan handle any one of the following three different functions:

S Packet Interface Function: PSI (pktif)

S Selector Function: PSI (pktsel)

S Packet Control Function: PSI (pktpcf)

PSI (pktif)

The PSI (pktif) acts as both bridge and router for voice, data, and callcontrol traffic traveling between the circuit network of the Transcoder(XC) and the packet network of the SDU/Radio Access Network (RAN).

The bridge functionality converts data from gigabit Ethernet on thepacket side to internal XC protocols on the circuit side.

The PSI (pktif) has three logical subfunctions:

S PSI–ce: conversion between 16Kbps circuit IOS and packet IOSframes

S PSI–ter: conversion between 64Kbps circuit PCM and packet PCM

S PSI–sig: conversion of SCAP signalling from LAPD to IP

5

CBSC – continued


On the circuit side, the PSI router works with and routes to and from thefollowing devices:

S MSI card

S Transcoder card (XCDR)

S Front End Processor (FEP)

On the packet side, the PSI routes messages via IPv4.

PSI (pktsel)

Dedicated to the Selector Function, PSI (pktsel) cards are used forhigh–speed packet data (IS–95B and IS–2000).

Operationally, when packet data signals come from multiple BTSs, thePSI (pktsel) makes its selection based on the basis of load and signalquality. In this way, it acts similarly to the current XCDRs, terminatingthe Radio Link Protocol (RLP).

These cards are deployed as PSI (pktif) or PSI (ter) cards if the freestanding SDU is used.

PSI (pktpcf)

Dedicated to the Packet Control Function (PCF), the PSI (pktpcf) workswith the Packet Data Service Node (PDSN) to manage a complete datasession. Operationally, the PCF terminates the layer 4 protocol stackfrom the mobile and the PDSN. The PCF should be viewed as facingand controlling the BSS resources while the PDSN controls the activitytoward the IP network.

Together the PCF and PDSN manage all 1X data sessions.

These cards are redeployed as PSI (pktif) or PSI (ter) cards if thefree–standing SDU is used.

Inputs and Outputs

Each PSI function has a different set of inputs and outputs. The inputsand outputs are really bidirectional so the designation of input andoutput is somewhat arbitrary.

PSI (pktif) Cards – PSI (pktif) cards have their input bridged throughthe MSI card(s) in the XC, to the PSI (pktif) card. The output is coupledthrough the XC bus to the PBIB–ES card via ribbon cable and then tothe AN IP Switch (Catalyst) via 1000 BaseT rated Ethernet cable.

PSI (pktsel) Cards – the input for PSI (pktsel) cards is from the AN IPSwitch (Catalyst). The output comes from the XC bus to the PBIB–Evia ribbon cable and to both AN IP Switches (Catalysts) via 100 BaseTEthernet.

PSI (pktpcf) Cards – These cards get their input from several CBSCfunctions and send their output to the PDSN via the AN IP Switch(Catalyst).

5

CBSC – continued


Signal Flow

PSI (pktif) Cards – The PSI (pktif) card provides packet to circuitinterworking which allows communication between the circuit domainof the XCDR and circuit backhauled BTSs and the packet domain of thePacket Data Network and the standalone SDU. In 16.0, the interworkingapplies to 1X data (FCH only) and ICSHO Mesh Elimination voicetraffic. In 16.1, the interworking applies to 1X data (FCH only) andvoice traffic on circuit backhauled BTSs to the SDU (External) and allvoice traffic from the SDU (packet domain) to the XC. Data traffic frompacket backhauled BTSs travels directly through the SDU to the PDNand does not impact the XC. For cIWU call setup with VPU, signalingmessages are also exchanged with VPU through this card.

PSI (pktsel) cards – The PSI (pktsel) card takes inputs from the variousBTSs receiving the same signal and selects the one for use in the systembased on signal and traffic criteria. This data selection process is similarto the voice selection that was performed by the XCDR. Thisfunction can move to the stand–alone SDU for 16.1 or remain on theCBSC.

PSI (pktpcf) card – The PSI (pktpcf) works with the PDSN to controlthe data secession with subscriber units. The PSI (pktpcf) can be viewedas the subscriber/RF–facing element of data secession control. The PSI(pktpcf) manages the RF capacity, data buffering, and other issues facingthe RF environment while interfacing with the PDSN controlling thenetwork facing management. The inputs (really bi–directional) to the PSI(pktpcf) come from the PSI (pktsel) card and the Catalyst and go to thePDSN through the Catalyst.

5

CBSC – continued


Figure 5-1: PSI Card Signal Flow

cBTS pBTS

MSC

SDF–EPSI–CE

VPF–E(cktiw)

MSI

B3

B1

XC

SDU

B1

Ckt–IOS

A2

CAI over TCHCAI over TCH

Provides Circuit/Packetconversion of modemtones to/from MSC.

PSI–TER

PSI–CEB2

MSI

MSI

DXCDR

CktIWU

PSI–TER provides Circuit/Packetconversion of modem tonesto/from Circuit IWU.

MS Data Path

PSTN Path (modem tones)

DXCDR terminatesRLP1 connection andprovides UI framingfor MS Data Path

XC required to provide Linterface to the Circuit IWU.

VPUDOC3

Redundancy

The PSI card is used in two redundancy modes:

S PSI (pktif) is used in the 2N redundancy mode and a separate PSI(pktif) card is used for each side of the AN IP Switch.

S PSI (pktsel) and PSI (pktpcf) use a high availability mode and thesame card feeds both AN IP Switches (Catalysts). Inputs to the cardsare controlled via poling or pulse checking, ensuring thatnon–responsive cards are not included in the pool of available cards.

O&M

Like other cards in the XC, provisioning for the PSI (pktsel) and PSI(pktif) cards is handled through OMC–R. Alarms too are handled as withother cards.

The PSI (pktpcf) is provisioned in the same manner as the PSI (pktif)and the PSI (pktsel). In addition however, the PSI (pktpcf) gets a pool ofIP addresses from the OMC–R. The addresses are assigned inconjunction with the PDSN and part of the IP management.

5

CBSC – continued


BIB Cards

Description

Recall that a Balanced Interconnection Board (BIB) card of any flavorprovides connectivity to three card slots.

In 16.0, the current BIB kit continued to be supported and two new typesof BIB cards will be introduced, bringing the total number of uniqueBIB kits to three. All three support Ethernet connectivity between thePSI and AN IP Switch (Catalyst). The original MSI BIB (commonlyand currently called “BIB”) will remain unchanged. Like the “BIB,” thepBIB supports three card slots. Each kit type provides a different type ofinterface provided for each of the three slots served by a single BIB asfollows:

S BIB: (For T1/T1/T1.) This configuration represents the existing BIBkit. The BIB will continue to:

– Support slots requiring T1/E1 connectivity

– Provide connectivity to three MSI card slots of T1s or E1s

With the BIB kit, MSI boards can be installed in any of the threeslots served by the BIB. Each MSI card provides 2 T1 or E1interfaces; therefore, this BIB configuration provides a total 2 * 3slots = 6 T1 or E1 interfaces.

S PBIB–ES: (For 1G/T1/T1.) The PBIB–ES kit supports a PSI (pktif) in the first of three slots served by the PBIB–ES, and 2 MSIs in the other two slots. This PBIB–ES card therefore will have1 RJ–45 connector with the 1G Ethernet interface and 4 T1/E1interfaces corresponding to the 2 MSI cards in the other two slots.

S PBIB–E: (For 100M/100M/100M.) The PBIB–E kit supports PSI(pktsel) or PSI (pktpcf) devices in any of the three slots served by thePBIB–E. This PBIB–E card therefore will have 6 RJ–45 connectorscorresponding to the 6 100M Ethernet interfaces corresponding to the3 PSI (pktsel) or PSI (pktpcf) cards that are in the three card slotsserved by this PBIB–E.

For 16.1/16.3, if the stand–alone SDU is selected, the PBIB–E will beeliminated as the function of those cards will be moved to the SDU, andadditional PBIB–ESs will be required to handle the additional trafficassociated with having both voice and data packetized. The PSI (ter) willalso use the PBIB–ESs so additional quantities may be required.

In the configurations listed above, the formats listed are described morespecifically as follows:

S BIB: T1 dual–channelized serial links in T1 or E1 frame format, assupported today by the existing BIB.

S PBIB–E: 100M / dual 100 megabit Ethernet links. This PBIB–E cardwill have 3 pairs of RJ–45 interfaces corresponding to the 3 card slotsthat it serves.

S PBIB–ES: 1G / single 1 Gigabit Ethernet link plus 2 T1s.

5

CBSC – continued


Function

Both of the pBIBs are essentially output panels that allow a signal takenof an internal bus to be routed to an external device.

Inputs and Outputs

As with most devices, the signals dealt with are bidirectional so thedesignation of an input is somewhat arbitrary. For the purpose ofseparating the two, consider the ribbon cable from the CBSC bus theinput and the RJ–45 output to the AN IP Switch (Catalyst) the output.

Card Description

The following illustrations show the physical layout of the PBIB–ES andPBIB–E cards.

Figure 5-2: PBIB–ES Physical Layout

Figure 5-3: PBIB–E Physical Layout

Signal Flow

The card serves only as a tie point for the signal.

5

CBSC – continued


Redundancy

The PBIB–ES is deployed in a 2N redundancy and each pBIB cardoutput would go to the different AN IP Switches (Catalysts) in pairs.

The PBIB–E is part of a high availability redundancy and each card hastwo outputs, PSI (pktsel) or PSI (pktpcf), which go to different AN IPSwitches (Catalysts) in a pair.

O&M

No O&M function associated with this card.

5

CBSC – continued


Notes

5

MM II


Mobility Manager II

Overview

The Mobility Manager II or MM II is the next generation mobilitymanager platform and performs the call processing functionality in theIP–BSC. The MM II provides new functionality over the PUMA MMincluding:

S Reduced size, weight, and power

S Increased performance up to 232 KBHCA

S Consistent operational philosophy with packet BTS, VPU and SDU

S Co–location with either SDU or VPU platform (i.e. in same IP–BSCframe)

S Hardware version information for each MM II node available fromOMC

The MM II uses commodity carrier–grade server hardware with an openoperating system to provide several benefits to both Motorola andCustomers. First, the new architecture provides the ability to ride thetechnology curve (i.e. Moore’s Law) to achieve higher performance andincreased capacity at lower cost. Second, open operating systemleverages the strength of open source improvements via the contributionsof a global consortium. Lastly, the MM II has enabled Motorola tominimize software development effort and time by leveraging openinterfaces and standards.

5

MMII – continued


Frame Description – IP–BSC

R17 introduces the next step in Motorola’s all IP–BSC, which replacesthe previous product known as the CBSC. The IP–BSC is a highcapacity and scalable product offering that leverages shared or pooledcomponents in an architecture that allows each service to be scaledindependently so resources are not wasted (i.e. Only deploy as manyvocoders as necessary for voice requirements). The functions performedby the IP–BSC include:

S Selection

S Vocoding

S Mobility Management

S PCF

Each function is performed by a particular unit within the IP–BSC. TheSDU performs Selection and PCF, the Mobility Manager II (MM II)performs Mobility Management and the VPU performs the Vocoding.

The IP–BSC also introduces a Common Frame. This common frame willhouse up to two SDU or VPU or MM II units or a mixture of two of thethree units. Each unit will be completely independent of the other. Also,each will have its own Power Supply Module (PSM) and PowerDistribution Unit (PDU) (except the MM II which has power distributionwithin the Field Replaceable Unit (FRU), separate thermal management,and separate redundant physical connections to the Access Node. Theframe provides a controlled environment for the IP–BSC units andcontrols emissions to and from the cabinet.

Frame Overview

The IP–BSC is a common frame that can hold up to two units of eitherthe MM II, SDU, or VPU. The IP–BSC frame has three high levelmodels.

S MM II, SDU or VPU

S MM II, MM II

S Any combination of SDU or VPU in either position.

5

MMll – continued


Figure 5-4: IP–BSC

5

MMII – continued


Within each model, “T–options” exist that further refine an operator’sdeployment requirements. For example each MM II can be ordered in aV.35 or a T1/E1 configuration. Also, the models generically include thebackplane and common hardware for the SDU or VPU (except Option2). There are “T–options” that must be specified at the time of orderingthat will determine whether a VPU or SDU is deployed in that particularframe.

Function

Platform Differences

Functionally, the MM II is identical to the legacy MM for callprocessing, CDL creation and statistics with the exception of the supportfor the following functions:

S The MM II will NOT support a Transcoder (XC), Token Ring LANs,or FEPs (i.e. purely packet MM)

S The MM II will NOT support a Packet–IWU (MM II will onlysupport the PDSN)

S The MM II will NOT support a Circuit BTS, and therefore the MMII will NOT support fallback from a Packet BTS to a Circuit BTS

S The MM II will NOT operate with a Helix OMCR

S The MM II will NOT support circuit based ICLINK communicationsbetween CBSCs.

MM II Call Control Functions

The Mobility Manager II performs call control within the CDMA RAN,which includes the following high–level call processing functions:

S Registration – Power up, power down, timer based and parameterchange registrations

S Paging – Process by which the location of a mobile is determined

S Call Setup – Allocation and coordination of RAN radio resources formobile originated calls and mobile terminated calls

S Hard Handoff – Movement of call control to an external CDMA oranalog system (hard hand out) as well as receipt of call controlfrom an external system (hard hand in)

S Soft Handoff – Addition and removal of legs to/from a call tomaintain the strongest available set of sector connections

S Softer Handoff – Addition and removal of legs to/from a call within asingle BTS

S Inter–CBSC Soft Handoff – Addition and removal of legs to/from acall under a remote MM II

S Call Tear Down – De–allocation and coordination of RAN radioresources

S Power Control – Dynamic adjustment and stabilization of the mobile’sforward and reverse link

5

MMll – continued


S ADDS, SMS – Exchange of short application specific data messagesto and from the mobile

S SSD – Authentication of a mobile requesting services from thenetwork

S Unique Challenge – Verification of SSD updates as well as mobileauthentication independent of a mobile requesting services fromthe network

S Data – Circuit Data, Low Speed Packet Data (LSPD), HighSpeed Packet Data (HSPD) and 1X packet data

S Overload and Congestion Control – Shedding of excessive load topreserve call capacity and Licensing Capacity control at either 1,000,3,000, or 5,000 Erlangs.

S Admission Control – Provision of a given level of performance thatthe user requires for the duration of the call

S PM Statistics – Aggregate measurements of system operation.

S CDL – Detailed information on call setup, tear down, and handoff on a per call basis. The MM II only supports variablelength CDLs (vCDL).

MM II Management Functions

The MM II also includes additional functionality related to managementof the MM II from the OMC including convergence on a common O&Minterface to improve overall system operability. The functionalityassociated with this improvement includes:

S The MM II operator interface changes to become consistent with theSDU, VPU, and pBTS.

S Task–based (work flow) Operational Procedures that align with SDU,VPU, and pBTS.

S Eliminates platform CLI interface.

S ISO X.73x alarm and ISO state management

S Improved performance/response for some operator tasks

S Automatic synchronization of configuration data, alarms, and statsbetween OMC and MM

S Link (OMC/MM) sanity audit

S Network based software install/upgrade with minimized operatorintervention

5

MMII – continued


MM_NODEs Description

The MM_NODE is the operating platform for the MM II. Under eachMM II, there are two MM_NODE servers operating in an active/standbymode. The backup MM_NODE server can take over for the primaryMM_NODE server.

MM II Network Interfaces

The MLS_MM_LINK (LAN Circuit) device connects the MM II and theAN. The LAN terminates on the LanPort on the MM_NODE. There aretwo MLS_MM_LINKs per MM_NODE, for a total of four in the MM II.Each MM_NODE is a parent device to a set of two MLS_MM_LINKs.A state transition of a single MM_NODE affects only the associated setof MLS_MM_LINKs.

The C7LINK is a communication link between the CBSC and the MSCwhich carries O&M and Call Processing traffic. The C7 links that tie theMM II to the MSC use the SS7 protocol. C7LINKs are dependent on theassociated MM_NODE. The physical MSC (Mobile Switching Center)manages the terrestrial circuits that carry traffic between the BSC andMSC.

The ICLINK is a logical connection between two packet CBSCs. Thelogical ICLINK is a Stream Control Transfer Protocol (SCTP)connection between CBSCs through the Access Network (AN). Allcommunication span lines between the packet CBSCs can be used forInter–CBSC Soft Handoffs (ICSHOs).

5

MMll – continued


Inputs/Outputs

The interfaces to the MM II are logically grouped into 3 categories:Span I/O, Network I/O, and Power. This grouping does not indicate aphysical grouping on the unit but is provided to logically group theinterfaces.

The Network I/O interface for each node is shown below and consists ofthe following:

S Primary 100 Base–TX Ethernet interface connected to AN

S Redundant 100 Base–TX Ethernet interface connected to AN

S Redundant Primary Internodal 100 Base–TX Ethernet interfaceconnected between MM II nodes with a crossover cable

S Redundant Secondary Internodal 100 Base–TX Ethernet interfaceconnected between MM II nodes with a crossover cable

Figure 5-5: MM II Network I/O Interfaces

Figure 5-6: MM II Network I/O Interfaces 5

MMII – continued


The Span I/O interface for each node is available with either aconfiguration supporting either T1, E1, or JT1 or in configurationsupporting up to eight V.35 DS0 interfaces. The interfaces for each nodeon an MM II must be configured with the same Span I/O interface andupgrade of the Span I/O interface requires replacement of the each node.

The T1/E1/JT1 interface consists of the following:

S Span A

The V.35 interface consists of the following:

S V.35 Span A

S V.35 Span B

S V.35 Span C

S V.35 Span D

S V.35 Span E

S V.35 Span F

S V.35 Span G

S V.35 Span H

The power interface per node consists of the following:

S –48 VDC A

S –48 VDC B

Card/Chassis Descriptions

The MM II provides an improvement in call processing capacity in an8U form factor with corresponding decrease in power consumption andmass reduction. The MM II will utilize commercial off–the–shelf serverproduct and commercial off–the–shelf carrier grade operating system.

The MM II will be deployed in an IP–BSC frame with an SDU, VPU oranother MM II. The MM II cannot be installed into an existing SDU orVPU frame. As stated in the earlier section, the IP–BSC frame is sold inpredetermined configurations.

For the MM II, the server is the Field Replaceable Unit (FRU). In nocase will the server be opened for service by the customer. All internalfailures, including the failure of PCI cards, memory modules, andprocessors will warrant repair of the unit by the vendor or replacement ofthe server. In addition, all configurable hardware options requirereplacement of the FRU. This includes changes to the SS7 interfacefrom V.35 to T1/E1 since this requires replacement of the SS7 I/O cardinternal to the MM II.

Signal Flow

The MM II interface definitions generally follow the philosophy of theDNP MM. There are however some changes to the MM II functionalityfrom the DNP MM. The MM II does NOT support circuit basedfunctionality directly.

5

MMll – continued


The MM II complies with 3GPP2 IOS specification of the A1 interfacein the same manner as the DNP MM. (In addition, the MM II can exhibitdifferent message sequencing during A1 Global Reset depending on thetype of switch connected to the MM II).

There are no other impacts to external interfaces, including the ANSI–41interface and the Cellular Air Interface.

The MM II supports all of the packet architecture call processing linksthat the DNP MM supports. Furthermore the MM II surveils the samelinks that the DNP MM surveilled. Just as with the CP interfaces, theMM II supports all of the packet oriented O&M interfaces thatthe DNP MM supports.

Table 5-1 is provided for reference and defines the interfaces between theMM II and the RANs other Network Elements as well as the MSC.

Table 5-1: MM Signalling Interfaces

Name Description

IOS–A1 Interface (A1) – Signaling to the MSC for callcontrol and TERCKTmanagement

BTS Call ProcessingControl

– Forwarding of accessmessaging (originations, pageterminations)– Initiating call set–up/callrelease signaling– Paging, registration– NE integrity/surveillance

Selector ResourceAllocation Controland Integrity

– Allocating/de–allocating SDUresources– NE integrity/surveillance

Packet ControlFunction (PCF) ResourceAllocationControl and Integrity

Allocating/de–allocating PCFresources– Configuring PCF resources– NE integrity/surveillance

Inter–CBSC SoftHandoff (ICSHO)Control and Integrity

– Initiating/releasing ofInter–CBSC connections– NE integrity/surveillance

Vocoder Allocationand Set–up Control

– Establishing and maintainingvocoding– Allocating vocoder resources– MSC connection requests

Selector Call ProcessingControl

– Mobility management (handoffdetection, execution)– Call set–up– Call tear–down

table continued on next page

5

MMII – continued


Table 5-1: MM Signalling Interfaces

Name Description

BTS Resource AllocationControl andIntegrity

– Allocating / de–allocating BTSresources

Broadcast Paging Broadcast paging.

Packet ControlFunction (PCF) CallCall Control

– Initiating the re–establishmentof a dormant IS–2000 data call– Short data delivery

SMAP Signaling – Sending call trace responsedata to SMAP

MM–MS Inter–Working – Inter–working SCAP messagesand their CAI Layer 3counterpartswhich are delivered to/receivedfrom the MS

Vocoder Modificationand ResourceDe–Allocation Control

– Modifying vocoding mode andservice type– De–allocating vocoderresources

Terrestrial CircuitManagement

– Blocking/Un–Blocking ofTerrestrial Circuits

MM–BTS ResourceManagement Control

– Discovering the BTS– Registering the BTS– Establishing the C1 interface

MM–SDU ResourceManagement Control

– Discovering the SDU– Registering the SDU– Establishing the C3 interface

MM–PCF ResourceManagement Control

– Discovering the PCF– Registering the PCF– Establishing the C4 interface

MM–VPU ResourceManagement Control

– Discovering the VPU– Registering the VPU– Establishing the C8 interface

CNEOMI OAMPControl

– Initiating O&M activitiesbetween the OMC–R and theMM

5

MMll – continued


The MM II supports the following protocols:

S IP

S DHCP

S OSPF

S SCTP

S UDP

S Multicast

S NTP

S SS7

For an overview of the functioning of IP routing protocols in the IPRAN, refer to Chapter 6.

Redundancy

The MM II will be configured as a pair of servers in an Active / Standbyconfiguration. The mated–pair configuration of the servers provides fullhardware redundancy. Each MM II node in the pair is a fully containedhardware fault zone. Internodal connectivity is restricted to redundantcrossover Ethernet cables.

Single node failure results in the failover to the redundant node. EachMM II node supports up to 8 DS0 connections to the MSC. Theseconnections operate in load sharing mode so that there are a total of 16DS0s to the MSC. The capacity planning for the MM II loads eachnode’s SS7 links at 40% so that in the case of a failure of a node theremaining node will have the capacity to take over the load from thefailed node.

Operation and Maintenance (O&M)

The MM II will use the SMNE maintenance paradigm, similar to thaton the SDU. This allows for consistent monitoring between the SDU,VPU, and MM II network elements from the OMC.

5

MMII – continued


Notes

5


Chapter 6: Access Node (AN)

Table of Contents

Access Node (AN) 6-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 6-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP Switch Frame (Catalyst) 6-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aggregation Point Frame (MGX) 6-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of IP RAN Protocols 6-15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of AN Routing 6-26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . QoS (Quality of Service) 6-35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP Addressing 6-36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6



Notes

6

Access Node (AN)


Introduction

AN Overview

The Access Node (AN), a set of IP switches and routers, interconnectsall of the cellular infrastructure devices and transports IP–based traffic toand from the CDMA 2000 (1X) cellular network.

The AN hardware architecture consists of two custom frames, theAggregation Point frame and the IP Switch frame. The AggregationPoint frame houses one or two Aggregation Points (MGX 8850 WANswitches). The IP Switch frame houses two IP Switches (Catalyst 6509Multilayer switches).

The Aggregation Point provides WAN connections to the BTSs andsupports JT1, T1, E1 and T3. The IP Switch interconnects the othercellular infrastructure devices and supports various types of EthernetLAN interfaces.

The Aggregation Point and IP Switch frames, in addition to housing theCisco equipment, provide power distribution functions.

Release 17 does not involve any new functionality orhardware updates for the AN. Maintenance releasesoftware upgrades may be required.

NOTE

Release 16.0

Release 16.0 utilizes the AN and packet backhaul for data calls andICSHO. Release 16.0 splits the existing circuit backhaul to providepacket pipes for 1X data. The voice path uses the existing circuitbackhaul. Release 16.1 will utilize the AN for packet backhaul of bothdata and voice traffic.

Release 16.0 uses the span grooming element (DACs) to groom thecircuit traffic and packet data pipe onto the BTS link (from the BTS tothe span grooming element). The span element also grooms the packetdata traffic off the BTS link and forwards it to the AN.

Release 16.1 and 16.3

Beginning in 16.1, the AN and packet backhaul work together to handledata calls, voice calls, and Inter–CBSC Soft Handoff (ICSHO).

The circuit backhaul is still supported in 16.1.

In 16.1 the AN will handle the packet backhaul for both data and voicetraffic.

A DACs may be used in 16.1 for some customerconfigurations.

NOTE

6

Access Node (AN) – continued


In release 16.3 the VPU becomes another element switched by the ANIP Switch.

Figure 6-1: Access Node (AN)

MGX 8800 MGX 8800

SDU, VPU

MM

OMCR

AN

To MSC/PSTN

Packet BTS Packet BTSCircuit BTS

Token Ring


Virtual LAN

PDSN


External IPNetwork

(Internet)

XC

The following figure illustrates the release 17.0 ANarchitecture and connectivity. See Chapter 2 for alternatearchitectures including MM II.

NOTE

6



Overview of AN Functions

This section describes the functions of the Access Node in an overview.

Provide the Transport Network for the CDMA2000 1X system

The main function of the AN is to provide the Transport Network for theCDMA2000 1X system.

The Access Node, which consists of a set of Layer 2 switches and Layer3 routers, performs the following Transport Network functionality:

S Interconnection all of the CDMA2000 1X system devices into ahub–like formation, using span line and Ethernet interfaces.

S Implement BTS backhaul functions by aggregating span links to/fromthe BTSs.– For 16.0, only the CDMA2000 1X Supplemental traffic channel is

backhauled from the BTS (through a DACs) to the AN AggregationPoint frame.

– For 16.1, both the CDMA2000 1X Supplemental channel andFundamental channel is backhauled from the BTS Router (no DACsused) to the AN Aggregation Point frame.

For 16.0 the scenario is called “split backhaul” since theFundamental channel traffic still follows the old circuitpath to/from the BTSs, but the Supplemental channelinterfaces directly to the AN. For 16.1 the scenario iscalled “full packet backhaul” since both traffic channeltypes interface directly to the AN to/from the BTSs(actually, the BTS Routers).

NOTE

S The IP Switch performs the Layer 2 switching and Layer 3 routing ofall IS–95/IS–2000 call traffic (voice, circuit, and packet data calls),control signalling, and O&M needed to support call processing in theCDMA2000 1X system.

S The AN functions as a pass–through network that interfaces thecellular network to IP data networks to transport packet data calltraffic. The IP data network elements that must interface to the cellularnetwork are the PDSN, AAA and optionally the HA. The AN canconnect to other networks using LAN and WAN interfaces with Layer3 routing functions.

Integrate separate ANs to increase the borders of the CDMA2000 1Xsystem

To integrate separate ANs (local and/or remote), it is necessary to useLAN–WAN routers. The AN uses the protocols necessary to establishinter–AN communication.

A main purpose of integrating multiple ANs, and therefore multipleBSSANs, under one OMC–R is to extend the O&M, PCF (packetcontrol function, data sent to PDSN), and soft handoff boundaries furtheracross multiple AN areas.

6



Mesh Elimination Feature

The AN enables the Mesh Elimination feature.

Implement the Following Switching and Routing Protocols

OSPF (Open Shortest Path First) is the AN’s primary routing protocol. Ituses OSPF version 2. The router, when receiving data to send to adestination, determines the best/most efficient path to the networkdestination based on routing tables that it continually updates with thestatus of links between network routers (OSPF requires routers in thenetwork to send messages indicating current status of links). Routersusing OSPF determine the best path to the network destination based onthe metric of bandwidth (other protocols use other metrics, such as hopcount for example, which is distance–based). The OSPF protocolsupports authentication.

The AN uses other common protocols such as:

S SNMP (Simple Network Management Protocol) which is enabled onthe system to manage AN performance and troubleshoot networkproblems

S PPP (Point–to–Point): PPP is a protocol for transporting data acrossPoint–to–Point links through a WAN to remote networks.

S TCP, UDP, IGMP, PIM, SCTP, BGP, PPP, HSRP, VTP.

S BGP (Border Gateway Protocol) is used for WAN routing whenLAN–WAN routers are installed between ANs.

6



IP Switch Frame (Catalyst)

Overview

The AN IP Switch (Catalyst 6509) is the central IP Switch of the IPRAN Architecture. All Ethernet connections are connected to theCatalyst 6509. The Catalyst 6509s are deployed in a redundant pairconfiguration so each device in the network has a redundant Ethernetlink to ensure a robust network.

An IP Switch consists of a Catalyst 6509 chassis, with redundant powersupplies and nine available slots. The backplane capacity is scalable to256 gigabits. Supervisor cards occupy two of the slots. The remainingseven slots hold a combination of 48 port 10/100 MB Ethernet switchingmodules and 16 port 1GB Ethernet switching modules. The operator canconfigure or add additional Ethernet switching modules as required, toaccommodate additional connections to the network.

Release 2.16.5.x

Release 2.16.5.x introduces a new IP–Switch Catalyst chassis and cards.These new hardware components support the evolution of the Catalyst6509 platform. The new components introduced are:

S Catalyst 6509 NEB A Chassis (replaces the Catalyst 6509–NEBSchassis)

S Supervisor 2 Engine with MSFC2 (replaces the Supervisor Engine Iwith MSFC2)

S 6148 10/100 Mbps Ethernet module (replaces the 6348 10/100MbpsEthernet module)

S 6516 Gigabit Ethernet module (replaces the 6316 Gigabit Ethernetmodule).

The primary benefit of this feature is the support of the Catalyst 6509platform evolution with backwards compatibility. This feature has nofunctional or performance impacts to the network.

Inputs and Outputs

The Catalyst Inputs and outputs (bidirectional) are from almost everycard and device in the data portion of the system. The Catalyst functionis that of a switch so any element that requires switching and that isvirtually all Data elements will go through the Catalyst.


The Catalyst 6509 must be located with its associated CBSCs andMGXs. If transmission lengths exceed 100 meters, special physicalmedia considerations need to be implemented. It will support remoteconnections to other Access Nodes and an OMC–R through a WANconnection.

6



Functions

The IP Switch performs the following functions.

Layer 2 (Data–link Layer) Switching

The IP Switch performs Layer 2 switching of bearer and control traffic toand from the IP RAN devices.

Layer 2 switching is a data link layer function that connects the LANlinks and forwards data based on physical addresses received from theupper layer (Layer 3, the network routing layer). Layer 2 switching alsoinvolves notifying upper–layer protocols of frame errors, and sequencingout–of–order frames.

Layer 3 (Network Layer) Routing

The IP Switch performs Layer 3 routing of traffic to and from:

S Devices directly connected to that particular Access Node.

S Devices connected to other ANs.

It is possible to co–locate ANs.

NOTE

Layer 3 routing has two major functions: path determination andforwarding (transporting incoming packets arriving at one interface portto one or more output ports).

The AN uses the OSPF protocol for the primary routing function.

The BGP protocol is used for inter–AN connections.

The Supervisor card with MSFC (Multilayer Switch Feature card)performs the initial Layer 3 routing decisions using the MLS(Multi–Layer Switching) protocol, which routes the first packet, andthen switches the subsequent packets to save router processing.

VLAN (Virtual Local Area Network)

The IP Switch uses the Layer 2 VLAN protocol between the Catalystand the Transcoder PSI cards (all packet PSI interfaces are in oneVLAN, and all circuit PSI interfaces are in another VLAN). A VLAN isa logical subnet or a broadcast domain. The VLAN is similar to thesubnet at Layer 3.

Load Sharing and Redundancy

A variable number of Gigabit Ethernet links connect two Catalystswitches together within the IP Switch frame, using fiber or EthernetCategory 5 cross–over cables. This provides both load sharing andredundancy. This trunk uses ISL, a Cisco protocol, for the connection.

6



Hot Standby Routing Protocol (HSRP)

HSRP was created to provide a mechanism for routing around routerfaults without requiring every host to run the routing protocol. Thisprotocol will be used in the CDMA RAN to provide fault tolerance forthe XC PSI card and other devices that do not run OSPF (such as the3com PDSN).

Card Descriptions

Gigabit Ethernet Modules – The 16–port Gigabit Ethernet modulessupport the physical interface for gigabit connectivity. The Supervisorcard uses a Gigabit Interface Converter (GBIC) which works inconjunction with the Gigabit Ethernet Module.

10/100BaseT Ethernet Modules – The 48–port 10/100BaseT EthernetModules provide the 10/100BaseT physical interface for Fast Ethernetconnectivity.

Supervisor card – The Supervisor card contains the Layer 2 and Layer 3forwarding engines, with 2 GBIC interfaces. The Supervisor card alsocontains the MSFC Multilayer Switch Feature, which makes the initialLayer 3 forwarding decisions.

AN links should be planned and installed in a fan outconfiguration, to avoid concentration on DSPs. Refer to theappropriate site planning and installation documentationfor information on planning and installing AN links.

IMPORTANT

*

Signal Flow

The signal flow for the Catalyst 6509 is typical for an Ethernet switch.Signals are terminated on line cards and switch through Supervisorengines.

10/100BaseT Ethernet Cards – provide Fast Ethernet switching of call,control, and O&M traffic between the Catalyst and:

S PDSN

S MM

S MM II

S WAN Router (when applicable)

S EV–DO (stand alone, when applicable)

S OMC–R

S OMC–IP

S MGX RPM card (Aggregation Point)

S In 16.0 and 16.1 without SDU: XC PSI–PCF and XC PSI–SEL.

Gigabit Ethernet Modules – provides Gigabit Ethernet switching of call,control, and O&M traffic between the Catalyst and:

6



S WAN Router (when applicable)

S EV–DO (stand alone, when applicable)

S SDU

S VPU

S XC PSI (Circuit–to–Packet Interworking function)

S Catalyst in the same IP Switch frame

Redundancy

The IP Switch frame contains two Catalyst 6509 chassis for purposes ofredundancy. A variable number of Gigabit Ethernet links (CatalystGigabit Ethernet modules) connect the two Catalyst switches.

For each redundant type of device, the system automatically updates astandby unit to take the place of a primary unit if and when any of thefollowing circumstances occur:

S The system detects the critical failure of a primary unit.

S A primary unit is taken out of service by operator command.

S A primary unit is physically removed from the frame.

Table 6-1: Catalyst 6509 redundancy

Component HardwareRedundancy

Type

Comments

Catalyst Sup Eng/MSFC 2N Routing protocol.HSRP for XC endnodes.

Catalyst GB or FEEthernet cards

6509 pair (Notredundant inchassis)

Provides Ethernetconnectivity.Ethernet pathredundancy.

IP Switch Power Supply 2N Redundant powersupply and fanstake over incase of failure.


The operator uses the OMC–R to generate the configuration files for theIP Switch, in terms of adding links to the network, and other functions.

An Operations and Maintenance Center – IP (OMC–IP) will handleoperations and maintenance control for the Access Node componentsand interface with the existing network management architecture, i.e. theOMC–R and UNO platforms. Cisco software products are planned to runon a Sun hardware platform with a Solaris operating system. Other BSCelements, such as the SDU, MM, XC, and BTS are supported andmanaged by the OMC–R.

6



Aggregation Point Frame(MGX)

Overview

The Aggregation Point frame (MGX) implements BTS backhaulfunctions by aggregating span links to/from the BTSs.

The Aggregation Point frame contains an MGX 8850 chassis, withredundant power supplies and 32 single height (16 double/full height)function module slots.

The standard configuration reserves two full slots for the redundantPXM1 processing engine, and two half slots for the Service RedundancyModules (SRM) per shelf. This leaves 12 usable full height slots that cancontain T1 cards, T3 cards, etc. or Route Processor Module (RPM)cards. The span termination Frame Relay Service Modules (FRSM) arein the front of the chassis, with span termination cards in back. An eightport T1 card takes a single slot. The RPM card is a double–slot frontcard with two single slot Fast Ethernet back cards.

16.1 Changes

16.0 introduced 1X voice and data into the system.

For the 16.0 release, the following traffic types were backhauled with thecurrent circuit backhaul functionality.

S voice

S circuit data

S 1X fundamental channel

S IS95B data

1X supplemental channels were backhauled over dedicated DS0s on thesame span as the voice circuits and were split out by a DACS or otherspan–grooming device at the CBSC location and sent to the ANAggregation Point (Cisco MGX8850). Optionally, at large sites where aseparate span is needed to handle all the data DS0s, the data DS0 spancan be backhauled directly to the MGX.

For 16.1, the packet backhaul will bring greatly increase backhaulefficiency and reduced costs. The impact on the AN is the addition ofone new card (Compression Adapter) and some additional cards requiredto handle the increased packet traffic brought on with the inclusion ofpacketized voice along with the data in 16.0.

6



Functions

The AN Aggregation Point performs the following functions:

S It aggregates BTS spans containing the voice and data traffic

S The Aggregation Point connects with the IP Switches in order totransport data to and from BTSs to the network. It sends data to andfrom the AN IP Switch (Catalyst 6509 IP Switch).

The spans terminate on a T1, E1, or T3 port card. The processing forspan termination occurs on Frame Relay Service Modules (FRSMs).Data is routed on the backplane and switched through the ProcessorSwitch Modules (PXMs) to the Route Processor Modules (RPMs.)Traffic is sent to and from the RPMs via 100Mbit Ethernet to theCatalyst 6509.

Point to Point Protocol with Multiplexing – PPPMux is a newprotocol that increases the utilization of slow serial links for real–timeapplications that generate a large number of small packets. Theimprovement is provided by multiplexing multiple application levelpackets in a single PPP frame thereby reducing the PPP header overheadper packet.

MuxPPP is used to encapsulate IP packets transported between the BTSRouter and the RPM over the WAN interface.

The Compression Adapter card is added to the MGX to perform the PPPMux/de–mux functions.

Table 6-2: MuxPPP in RAN

Network element Purpose Communicateswith

MGX RPM card (EdgeRouter)

Transport IPdatagrams over itsWAN Interface tothe BTS Router

BTS Router

BTS Router Transport IPdatagrams over itsWAN Interface tothe Edge Router(RPM card)

MGX RPM card(Edge Router)

6



Multi link Point to Point protocol – MLPPP is a protocol that providesthe capability to coordinate multiple independent links between fixedpair of systems, providing a virtual link with bandwidth equal to sum ofthe bandwidths for individual links. The aggregated link is called abundle.

MLPPP will be used to transport HDLC frames over multiple linksbetween the BTS Router and the MGX RPM card (Edge Router).

Table 6-3: MLPPP



Transport HDLCframes overmultiple links tothe BTS Router

BTS Router

BTS Router Transport HDLCframes overmultiple links tothe MGX RPMcard (EdgeRouter)

MGX RPM card(Edge Router)

The WAN routers may also use MLPPP.

NOTE

cUDP – Compressed User Datagram Protocol (cUDP) is a method forcompressing the headers of IP/UDP datagrams to reduce overhead onlow–speed serial links. In many cases, the two headers can becompressed to 2–4 bytes.

The BTS router uses cUDP for sending UDP data, coming from thePacket BTS, over the packet back haul to the Edge Router (the MGXRPM card) where the Compression Adapter converts cUDP to UDPbefore forwarding it on to the rest of the AN. On the forward link EdgeRouter uses cUDP to transmit UDP data to the BTS Router over thepacket back haul. BTS Router then converts the data back to UDP beforeforwarding it to the Packet BTS.

The Compression Adapter card implements this feature.

Table 6-4: cUDP


BTS Router forwarding UDPdata

RPM (EdgeRouter)

RPM (Edge router) forwarding UDPdata

BTS Router

6



Inputs and Outputs

For Circuit backhaul, the inputs (bidirectional) come from the DACS viaT1 or T3 and are the aggregated packet pipes from the various BTSs.The outputs go to the RPM card via the MGX bus; they are thepacketized version of the backhaul sent to the Catalyst for routing to thevarious modules.

For packet backhaul, the inputs come from the DACs via T3 or from theBTS/BTS RTR via packet backhaul.

Card Descriptions

S PXM1 card – Processor Switch Module. The PXM is the brains of theMGX and has a 1.2 Gbps switching capability. The PXM cardprovides the internal ATM switching fabric for the MGX. The PXMalso handles RPM redundancy. In the event of an RPM card failure,the PXM signals the redundant RPM to load the configuration of thefailed RPM, and re–maps through the mid–plane the appropriate dataconnections to the newly active RPM. The PXM also has 1:1 hotstandby redundancy.

S UI card – Provides connectivity to the user interface.

S FRSM card – Frame Service Module, which provides transport to theRPMs within the MGX chassis. The FRSM back cards providephysical termination of the T1/JT1/E1 and T3 links.

S FRSM Redundant back cards – The FRSM redundant back cardsprovide loopback capability for the redundant FRSM cards so that thecorresponding FRSM front cards are recognized as redundant.

S SRM cards – Service Resource Module, provides redundancy controlfor the FRSM cards.

S RPM cards – RPM cards are the Edge Routers for the system. RPMdetermines the path to route traffic to the next network element. Themain RPM function is to route traffic to and from the BTS. RPMs arerequired for Layer 3 services such as routing, load balancing and loadsharing. The front RPM is the route processor engine.

An individual RPM card feeds two Ethernet back cards. The twoEthernet cards operate in load balancing/sharing fashion. The options,per RPM, include:

– Two RJ–45 FEs – used for circuit backhaul

– One 1FE–CP and one RJ–45 FE – used for packet backhaul

– Two 1FE–CPs, one with the CP function disabled and only actingas an FE interface – used to increase capacity a for packet backhaulsystem. Release 16.4.1 introduces this capability.

6



S 1FE–CP card – The Compression Adapter / Fast Ethernet backcardprovides a Compression Adapter function in addition to Fast Ethernetconnectivity.

– MuxPPP

– MLPPP

– cUDP

Signal Flow

For 16.0, signals flow through the MGX as follows: from the BTS to thespan backcard, to the FRSM, to the PXM1 to the RPM to the Ethernetbackcard to the Catalyst 6509 IP Switch. The signals to the BTS followa reverse path.

For 16.1 with the pBTS feature:

S Traffic to/from the BTS Router (HDLC) terminates at the MGX FRSMspan line card (T1, E1, etc).

S The PXM card switches traffic between the FRSM and RPM using anATM cell bus.

S The RPM makes the Layer 3 routing decision, and also works with theCompression Adapter function on its corresponding CompressionAdapter/Fast Ethernet backcard to process the packets forinput/output:

– MuxPPP processing

– MLPPP processing

– cUDP processing

S The RPM card sends/receives UDP traffic through the two FastEthernet backcards. Since the RPM card uses the two Fast Ethernetback cards for load sharing purposes, the back card used to output thetraffic will depend on current bandwith usage.

The following traffic types flow through the MGX:

S For 16.0, only the CDMA2000 1X Supplemental traffic channel isbackhauled from the BTS (through a DACs) to the AN AggregationPoint frame.

S For 16.1 with the pBTS feature, both the CDMA2000 1XSupplemental channel and Fundamental channel is backhauled fromthe BTS Router (no DACs used) to the AN Aggregation Point frame.

6



Redundancy

There are redundant connections from each RPM card to each Catalyst(100BaseT Fast Ethernet card).

Table 6-5: MGX Redundancy

Component Hardware RedundancyType

Impact on MGX Services When Failed Unit Recov-ered

MGX PXM1 2N Hot standby PXM switches over on detection of fail-ure.

MGX RPM N+1 Redundant RPM switches over on detection of fail-ure. Upon initiation from PXM1, configuration ofthe primary card is copied to a standby card after itbecomes active.

MGX FRSM T1/JT1/E1 N+1 per shelf FRSM in each shelf switches over under SRM con-trol.

MGX T1/E1/J1 BackCard

Not Redundant Provides span connectivity.

MGX FRSM T3/J3 2N Hot standby FRSM switches over on detection offailure.

MGX T3/J3 Back Card 2N Provides span connectivity.

MGX SRM 2N Redundant SRM for each active SRM per FRSMshelf. Note that the SRMs on the top/bottom shelfprovide redundancy for the FRSMs on the top/bottomshelf.

MGX Power Supply 2N Redundant unit takes over in case of failure.


An Operations and Maintenance Center – Internet Protocol (OMC–IP)will handle operations and maintenance control for AN components andinterface with the existing network management architecture; i.e., theOMC–R and UNO platforms. Cisco software products will run on a Sunhardware platform with a Solaris operating system.

OMC–R will continue to support other CBSC elements, such as theMobility Manager (MM), Transcoder (XC), and BTS.

6



Overview of IP RAN Protocols

The following pages cover the basic protocols implemented in the IPRAN.

IP

Internet Protocol (IP) is the basic network layer service implemented inthe Radio Access Network (RAN), and it forms the foundation for thenetwork’s higher–level protocols.

Properties of IP:

S Connectionless (datagram–oriented) –– packets are delivered with”best effort” service

The RAN/BSSAN implements QoS functions to improveservice. For more information, refer to the “QoS” section.

NOTE

S Unreliable Transmission –– lost packets are not retransmitted (noacknowledgement)

S Segmentation –– if necessary, the sending host and/or intermediaterouters will segment messages into more than one IP packet

S Reassembly –– segmented messages are reassembled by IP at thereceiving host

IP packets are made up of two parts: header and payload. The IP packetheader is used to address the message so that it can be delivered to itsdestination. The header also contains other information such asprecedence and error detection data. The payload portion of the packetcontains the data that is being transported.

6



Figure 6-2: IP Packets

IP Datagram Format

32 bits

Total Length

Options (0 or more 32–bit words)

Data

20 bytes

Vers HDR Length TOS

ID Number Flags Fragment Offset

Time T o Live Protocol Checksum

Source IP Address

Destination IP Address

IP is the network layer mechanism for all applications in the network.Thus, O&M, Call Processing and Bearer Traffic applications all use IP.Similarly, any network element which must communicate with any othernetwork element must implement IP.

The following table lists the network elements that implement IP.

Table 6-6: IP Applications

Network Element Communicates with

OMCR Customer Workstations, UNO,MM, MM II, XC(OMP), pBTS,SMAP, FEP, Terminal Server,OMCIP, SDU/VPU SPROC

UNO OMCR, Customer workstation,TCM, PDSN

MM OMCR, XC (OMP), XC (FEP),XC (PSI–PCF), pBTS, MM(remote), MM (DNPnode–to–node), MMII, SDU,VPU

MM II OMCR, SDU, VPU, pBTS

XC (OMP) OMCR

XC (FEP) MM, OMCR

XC (PSI–SIG) XC (remote PSI–SIG), pBTS,SDU (SDF), VPU–vpf (cktiw)

XC (PSI–CE) Remote XC (PSI–CE), XC(PSI–SEL), pBTS, SDU (SDF)


6





XC (PSI–PCF) XC (PSI–SEL, local and remote),PDSN, MM

XC (PSI–SEL) XC (PSI–PCF, local and remote,PSI–CE), MAWI–1X orMCC–1X (via packet pipe),pBTS

XC (PSI–TER) VPU–vpf (cktiw)

SDU (SDF) MM, MM II, SDU (PCF, localand remote), XC (PSI–CE), XC(PSI–SIG), pBTS, VPU vpf(a5iw)

SDU (PCF) PDSN, SDU (SDF local orremote), MM, MM II

VPUvpf(voc) MM, MM II, SDU (SDF)

VPUvpf(cktiw) MM, XC (PSI–SIG)

VPUvpf(a5iw) SDU (SDF)

VPUvpf–ra MM, MM II

SMAP XC (FEP), Customerworkstation, pBTS, SDU (SDF)

MCC–1X, MAWI–1X MM, MM II, OMCR, XC(PSI–SIG, local and remote),XC(PSI–CE, local and remote),XC (PSI–SEL, local and remote)

OMCIP OMCR, TN, RPM, Catalyst,MGX, Cisco PDSN

Customer Workstation UNO, SMAP

AAA PDSN

3COM PDSN XC (PSI–PCF), SDU (PCF),UNO, TCM, AAA

Cisco PDSN XC (PSI–PCF), SDU (PCF),UNO, OMCIP, AAA

TCM UNO, IWU, 3COM PDSN

Terminal Server OMCR

pBTS SPROC MM, MM II, SDU, XC andOMCR

pBTS Payload Function MM, MM II, VPU and SDU


6





MOSCAD RTU MOSCAD GW

MOSCAD GW MOSCAD RTU, UNO

TCP

Transmission Control Protocol (TCP) delivers messages betweennetwork elements using the underlying IP implementation of the networklayer. TCP builds upon IP and provides additional features andcapabilities that IP does not provide. The properties of TCP include:

S Connection–Oriented –– network elements must establish aconnection before they can communicate

S Reliable –– lost (unacknowledged) messages are retransmitted

S Flow Control –– data rates are adjusted in real time

S Ordered Delivery –– messages are delivered in the order intended bythe sender

Before data can be exchanged between a client and a server, apoint–to–point TCP connection must be established. This isaccomplished using a connection establishment protocol performedcooperatively between the two communicating systems. Similarly,connections no longer needed can be cooperatively terminated.

TCP breaks long messages into segments. Each TCP segment isencapsulated in an IP packet (each IP packet contains a single TCPsegment).

6



Figure 6-3: TCP Segments

IP Encapsulation of TCP Segments

TCP Segment Format

IP Packet

TCP Segment

IP Header TCP Header(20 bytes)(20 bytes)

TCP Payload

IP Payload

Options (0 or more 32–bit words)

Data

20 bytes

32 Bits

16 bit source port number 16 bit destination port number

32 bit sequence number

32 bit acknowledgment number

4 bit Header Leng. 6 bits reserved 6 fag bits 16 bit window size

16 bit TCP checksum 16 bit urgent pointer

TCP is used for O&M applications between the MM and the OMCR.TCP is also used for most communication between the MM and XCdevices (for both O&M and for Call Processing). Among otherfunctions, O&M includes data uploads/downloads between the MM anddownstream devices (e.g., GLI, MAWI). These functions are performedusing the Volume Data Transfer (VDT) application protocol overTCP/IP.

6



Table 6-7: Network Elements implementing TCP

Network Element Purpose – Communicates with

OMCR O&M – MM, UNO, SMAP

MM O&M – OMCR, XC(FEP), UNO

CP – XC–FEP

MM II O&M – OMCR

XC (FEP) O&M – OMCR, MM, UNO

CP – MM

SMAP PM – OMCR

SDU and VPU O&M – OMCR

pBTS–SPROC O&M – OMCR

MOSCAD RTU O&M – MOSCAD GW

MOSCAD GW O&M – MOSCAD RTU, UNO

UDP

User Datagram Protocol (UDP) delivers messages between networkelements using the underlying IP network layer (similar to TCP).However, UDP is much simpler and provides a much more limited set ofcapabilities compared to TCP. UDP is primarily used with applicationswhere the additional overhead of TCP is not desired, and reliabledelivery at the transport layer is not required. The properties of UDP are:

S Connectionless –– no virtual connection is established between senderand receiver

S Unreliable –– no provision is made for detecting or retransmitting lostmessages

S No Segmentation or Reassembly –– no provision is made to segmentor reassemble long messages (each UDP message results in a single IPdatagram)

S Unordered Delivery –– messages are not guaranteed to be delivered inthe order they were sent

Each UDP datagram is encapsulated into a single IP datagram.

6



Figure 6-4: UDP

IP Encapsulation of UDP Datagrams

UDP Datagram Format

IP Packet

UDP Datagram

IP Header UDP Header(8 bytes)(20 bytes)

UDP Payload

IP Payload

32 bits

Destination Port (16 bits)Source Port Number (16 bits)

Data (if any)

UDP Length (16 bits) UDP Checksum (16 bits)

The MM uses UDP for sending Paging request messages to the XC.UDP is also used in some O&M operations (i.e., bulk datadownloads/uploads between the MM and OMCR using Trivial FileTransfer Protocol, TFTP, which is built on top of UDP, bearer traffic).

In 16.1, the Helix MM uses UDP for communication with the SDU(SDF).

Table 6-8: UDP Implementation

Network Element Purpose Communicateswith

OMCR O&M OMP, XC (FEP),pBTS–SPROC &SDU

MM Paging XC(FEP),pBTS–SPROC,pBTS–PAYLOADFunction

MM II Paging pBTS–SPROC,pBTS–PAYLOADFunction

6




Network Element Communicateswith

Purpose

XC (PSI–SEL) Supplementalchannelmanagement

MCC–1X,MAWI–1X,pBTS–SPROC

Control XC(PSI–CE)

O&M OMCR

Bearer MCC–1X,MAWI–1X,RemoteXC(PSI–CE),pBTS–PAYLOADFunction

XC (PSI–PCF) Control PDSN,XC(PSI–SEL)

O&M OMC–R

XC (PSI–CE) Bearer RemoteXC(PSI–CE),XC(PSI–SEL),pBTS–PAYLOADFunction

XC (PSI–TER) Bearer VPUvpf(cktiw)

MCC–1X, MAWI–1X Supplementalchannelmanagement

XC(PSI–SEL)

Bearer XC(PSI–SEL)

Catalyst Routing protocols Catalyst, MGXRPM card (EdgeRouter)


Routing protocols Catalyst, MGXRPM card (EdgeRouter)

PDSN Bearer External networks

SDU (core) Control MM (SDU–RA)

SDU (core) O&M OMCR

SDU (SDF) Bearer Traffic XC (PSI–CE),pBTS, SDU(PCF),VPUvpf(voc),VPUvpf(a5iw)

Call Control MM (Helix)

6





Purpose

SDU (PCF) Bearer Traffic PDSN, SDU(SDF)

VPU (SPROC) Control MM

O&M OMCR

VPUvpf(voc) Bearer Traffic SDU (SDF)

VPUvpf(a5iw) Bearer Traffic SDU (SDF)

VPUvpf(cktiw) Bearer Traffic XC (PSI–TER)

pBTS–SPROC O&M OMCR

pBTS–SPROC Control MM, MM II, SDU

Routing BTS Router

pBTS Payload function Control MM, MM II, SDU

Bearer SDU

BTS router Routing protocols RPM, Packet BTS

SCTP

SCTP (Stream Control Transmission Protocol) is similar to TCP in thatit provides for the reliable transport of data via virtual connections.However, the architecture of these connections and the way in whichthey are managed is very different from TCP. The basic characteristics ofSCTP are:

S Connection–Oriented –– virtual circuits called associations areestablished between hosts

S Reliable –– the protocol detects and retransmits lost(unacknowledged) messages

S Segmentation –– messages are segmented to conform to thediscovered path MTU

S Flow Control –– data rates are adjusted in real time

S Path Redundancy –– multiple destination IP addresses per associationprovide path redundancy

S Heartbeats –– the built–in heartbeat mechanism facilitates link faultmanagement

6



As mentioned previously, SCTP is connection–oriented (like TCP),however, the connections (called ”associations”) are more sophisticated.When an association is created between two endpoints, each endpointcan provide a list of destination transport addresses (i.e., multiple IPaddresses sharing a single SCTP port number) that the endpoint will useto receive messages. Therefore, an association between two endpointsincludes all of the possible source/destination IP address combinations,which provides path redundancy.

Functionally, SCTP provides a number of sub–functions. For detailsrefer to the SCTP standards document identified below. To summarize,these functions are:

S Association Startup and Takedown –– Associations are initiated onrequest by an SCTP User. Associations can be terminated gracefullyusing the TERMINATE primitive or they can be terminatedungracefully using the ABORT primitive.

S Sequenced Delivery within Streams –– SCTP Streams are a method ofmultiplexing several data streams (i.e., sequences of user messages)within an association. This optional function uses a streamidentification number to isolate streams of messages from one anotherwithin the association. There are no plans to use this functionality in16.0.

S User Data Segmentation –– SCTP will segment user data as requiredto conform to the re–quirements of lower level protocols such as IP(i.e., the Maximum Transmission Unit).

S Acknowledgment and Congestion Avoidance –– SCTP uses SelectiveAcknowledgement (SACK) to acknowledge specific data chunkswithin an SCTP datagram. Congestion Avoidance and CongestionControl mechanisms are very similar to those implemented in TCP.

S Chunk Multiplex –– SCTP allows the bundling of several usermessages (”chunks”) into a single SCTP datagram sharing a commonSCTP header. SCTP assembles these multiplexed messages at thesending endpoint and disassembles them at the receiving end–point.

S Message Validation –– SCTP uses both a Verification Tag and aChecksum for message validation. A Verification Tag is selected byeach of the endpoints during association initialization,and subsequent messages must contain the correct Verification Tag tobe accepted. The Adler–32 Checksum validates the accuracy of thedata transmitted.

S Path Management –– SCTP injects heartbeat messages (in the absenceof regular traffic) to constantly monitor the reachability andperformance of each destination address in an association. SCTP willdirect traffic to the path most likely to provide the best performanceat any given time.

6



Figure 6-5: SCTP Datagrams

32 bits

Common Header

Chunk #1

Chunk #2

...

Chunk #n

SCTP ”chunks” contain either control information or user data. Anynumber of chunks can be multiplexed up to the MTU (maximumtransmission unit) supported by the underlying network layer. Note:there are some restrictions on the types of chunks that can bemultiplexed. Refer to the standards document for details.

If a user message does not fit within a single datagram, SCTP willsegment it into multiple SCTP datagrams.

Since chunks can be multiplexed into a datagram, each chunk must haveits own identification field so that it can be de–multiplexed at thereceiver.

Table 6-9: Network elements implementing SCTP

Network Element Purpose Communicateswith

MM Call control XC(PSI–PCF),MM–CP(ICBSC), pBTS,SDU (PCF), SDU(SDF), VPUvpfra

Resourcemanagement

pBTS–SPROC,SDU (SDU–RA)

MM II Call control MM–CP(ICBSC), pBTS,SDU (PCF), SDU(SDF), VPUvpfra

Resourcemanagement

pBTS–SPROC,SDU (SDU–RA)

XC (PSI–PCF) Call control MM–CP

XC (PSI–SIG) Call control XC(PSI–SIG),pBTS–SPROC,SDU (SDF),VPUvpf(cktiw)

SDU (SDU–RA) O&M MM, MM II

table continued next page

6



Table 6-9: Network elements implementing SCTP


Purpose

SDU (PCF) Call control MM, MM II, SDU(SDF)

SDU (SDF) Call control MM (Puma), MMII, pBTS, SDU(PCF), XC(PSI–SIG),VPUvpf(voc),VPUvpf(a5iw)

VPUvpf–ra O&M MM, MM II

VPUvpf(voc) Call Control SDU (SDF)

VPUvpf(a5iw) Call Control SDU (SDF)

VPUvpf(cktiw) Call Control XC (PSI–SIG)

pBTS–SPROC Resourcemanagement

MM, SDU

Call control SDU (SDF)

Overview of AN Routing

Routing overview

Routing is the network function used to get a message sent by one hostto the correct destination host. Routing in IP networks is done at layer 3(the Network Layer) using the address that appears in the header of everyIP message. Each router in the network is responsible for maintaining arouting table that allows it to forward any incoming message on to thecorrect host (or the next router in the path).

This table must be updated frequently because routes may fail or hostsmay enter or leave the network. Routers become aware of such changesand update their tables. They also share information with other routers inthe network so that all other router tables get updated with any newinformation.

Routing protocols are used to standardize the router–to–routercommunications and other aspects of the routing function.

Autonomous System Overview

The concept of an Autonomous System (AS) is used to establish routingmanagement domains in large networks. The AS represents a singlerouting domain managed as a single unit. Routers within an AS workcooperatively to develop the required routing tables for the AS. Routingadvertisements for the AS remain within the AS.

6



Routing outside of the AS is controlled only by routers designated to beAS border routers (ASBR in OSPF routing protocol). Border routersmay run different protocols and may be managed differently from otherrouters within an AS.

Routing within the AS can be further subdivided into areas with ahierarchical relationship. Area hierarchies are used to limit how widelyrouting information is shared. Typically, routers within an area share acomplete routing database. However, routers that share data betweenareas (known as Area Border Routers or ABRs in the OSPF routingprotocol) limit the routing information they share.

The Layered Network Model

A layered model is often used to design large networks. The layeredmodel is useful when discussing routing within a network since it helpsdetermine which functions each component in the network will perform.

It is important to remember that these layers are not necessarily highlydistinct. A given layer may be spread across a number of networkelements. Conversely, a given network element may play a role inseveral layers simultaneously.

The Core layer provides the backbone functionality. It provideshigh–speed switching between routing sub–domains and requires a highdegree of route summarization. In the BSSAN AS, this function isprovided in the aggregate by the IP Switch MLSs and the AggregationPoint Edge Routing functions. Additional routers may be implementedin the BSSAN to provide WAN connectivity to other BSSANs orconnectivity to customer LANs. These routers, if they are present, arealso part of the core layer.

The Distribution layer provides functions that require the manipulationof IP packets or the building of routes within non–backbone areas of thenetwork. In the BSSAN AS these services are also provided by the IPSwitch MLSs and Aggregation Point Edge Routing functions in the AN.This is possible because these routers lie on the boundary between theCore and Distribution areas. These routers serve both layerssimultaneously.

In simplest terms, the Access layer provides an interface to servicesrequired by users of the network. In the BSSAN AS, this function isprovided by the BSS.

OSPF

The Open Shortest Path First (OSPF) routing protocol is a link stateprotocol (rather than a distance vector protocol like RIP). This meansthat each router does not exchange distances with its neighbors. Instead,each router actively tests the status of its link to each of its neighbors.The results of these tests is forwarded on to other neighbors whichpropagate it on to their neighbors and so on. OSPF embodies a numberof concepts that affect the way that the network is configured.

6



An OSPF router detects neighboring routers by sending a “hello”message to a multicast address reserved for that purpose. When a routerdetects a neighbor (by receiving a response to its hello message) itattempts to form an adjacency with that neighbor.

Adjacency is a relationship formed between neighboring routers for thepurpose of exchanging routing information (not every pair ofneighboring routers become adjacent in a typical network but in theCDMA RAN it is likely that all routers will form adjacencies with alltheir neighbors since they are all on area borders as will be describedlater). Adjacencies are established during network initialization in pairs,between two neighbors. As the adjacency is established the neighborsexchange information and build a consistent synchronized databasebetween them.

For example, an MM is connected to a Catalyst. The MM and Catalystdiscover each other because they multicast out hello packets on theirinterfaces. The MM and the Catalyst cooperatively create an adjacencybecause they are neighbors.

OSPF routers will send hello packets to all their neighbors periodically.Any changes in the network’s topology (from added, removed or failedrouters) will be detected when the hello packets are sent. When a changeis detected by an adjacent router using the hello protocol, Link StateAdvertisements (LSAs) are sent to all other routers in the area. LSAscontain (among other things) the names of all the links that the router isaware of and the cost of these links. LSAs make it possible for all therouter databases to be updated. The point at which all the routers haveupdated databases that are in agreement is called “convergence”.

OSPF Hierarchies

OSPF uses a hierarchical routing concept to allow large scale networktopologies. Without this hierarchical design, increasing the scale of thenetwork would increases the size of routing tables maintained by eachrouter and the number of inter–router messages needed to update thetables limiting the practical size of the network that can be implemented.

OSPF solves this problem by designating OSPF areas. Routinginformation for an OSPF area is exchanged between routers within thearea. However, routing advertisements external to the OSPF area arerestricted to (typically) a single summarized route that encompasses theentire OSPF area.

Several OSPF areas can be connected together by a backbone area(always indicated as OSPF Area 0). The backbone can be a high–speedswitching network because it only needs to route to a small number ofmostly stable routes.

6



Within these areas in multiaccess networks (networks supporting morethan two routers), the hello protocol elects a designated router (DR) anda backup designated router (BDR). Among other things, the designatedrouter is responsible for generating LSAs for the entire multiaccessnetwork. Designated routers allow a reduction in network traffic and inthe size of the topological database. Hello packets are exchanged via IPmulticast on each segment. The router with the highest OSPF priority ona segment will become the DR for that segment. The same process isrepeated for the BDR. In the case of a tie, the router with the highestRID will win. Both OSPF priority and RID are configurable items.Routers set to OSPF priority 0 (on a given port) will not be selected asthe designated router.

OSPF areas have the following characteristics:

S All routers within the area have the same OSPF area ID

S Both internal routes and external routes are summarized whereverpossible

In an OSPF routed network, different routers play different roles. Thereare 4 router roles:

S Internal Router (IR): All networks and hosts directly connected to anIR belong to the same OSPF area. IRs all have the same link statedatabase because they all belong to the same area.

S Area Border Router (ABR): ABRs are located on the border of one ormore OSPF areas. ABRs connect their OSPF area to the backbonearea. ABRs distribute only summarized routes to the backbone. ABRshave multiple instances of the link–state database, one for each area towhich it attaches.

S Backbone Router (BR): BRs typically have an interface to thebackbone area (area 0) and several other OSPF areas. BRs do not haveto be ABRs.

S Autonomous System Border Router (ASBR): ASBRs are connected tomore than one AS and exchange routing information with routers inanother AS. Normally, ASBR runs both OSPF and a boarder routingprotocol like BGP.

Stubby areas – To reduce the cost of routing, OSPF supports stub areas.A stub area is a LAN connected to an OSPF back–bone in which adefault route summarizes all external routes. Typically stubby areas haveonly a single exit point and are connected to the backbone by a singleABR.

For such areas there is no need to maintain information about externalroutes. Stub areas do not receive LSAs for external routes. Thereforestub areas differ from regular OSPF areas in that the stub area routersmaintain routing information only for intra–area routes and the defaultroute (to the single area exit point).

6



In addition “totally” stubby areas are supported in OSPF (but only onCisco routers). As in stubby areas, external routes are not advertised tothe totally stubby area. However, in totally stubby areas, routes internalto the OSPF area containing the totally stubby area are also notadvertised to other totally stubby areas. This means that intra–area routesare not known to the totally stubby area routers. In summary, this meansthat no LSA are sent to a totally stubby area and no LSAs are sent outfrom the totally stubby area except for the default route.

Routers within the stubby area only have entries for the default path totheir closest ABR gateway. This path is used for any traffic flowing intoor out of the totally stubby area.

OSPF on Cisco routers also supports areas called Not so Stubby Area(NSSA). These areas are similar to a stub area except it has thecapability to import AS external routes in a limited capacity within theNSSA area.

BSSAN Implementation

Overview

In R16.0 the BSSAN is equivalent to the Autonomous System (AS) forrouting purposes. The BSSAN AS contains the Area 0 (backbone), Area1 and Area 2.

In 16.1, a single BSSAN contains a Core AS plus one AS for eachexternal network (pBTS and SDU) allocated from the private set of ASnumbers. The core AS number is equivalent to the R16.0 BSSAN ASnumber. The Core AS contains Area 0, Area 1, Area 2 and Area 3. Itcontains the CBSC devices and the BTS routers (only the links to theCatalyst).

1X Circuit BTSs will be connected to the CBSC through span groomingfunctions on separate T1 (or other) communication spans that terminateon an Aggregation Point using packet pipes. This function remainsunchanged in the R16.1 network design.

Area 0

The backbone (Area 0) of the BSAAN AS in R16.0 or BSSAN Core ASin 16.1 is defined to include all AN IP Switches (Catalysts) ,Aggregation Points (e.g. MGX8850 w/RPM)) and all the interfacesbetween them. Since all these routers are also on the boundary of Area 0each router is both a Backbone Router (BR) and an Area Boarder Router(ABR). These routers also provide interfaces external to the AS throughWAN connections or gateway routers. If these extra–AS connections aredirectly connected to the Catalysts, then each Catalyst runs BGP on theinterfaces and serve as an Autonomous System Boundary Router(ASBR). If the extra–AS connections are provided by adding anadditional router (or routers) to serve as the ASBR then links betweenthese routers and the Catalysts are OSPF and links from the ASBR tooutside of the AS are BGP.

6



Catalysts will form adjacencies with all the MGX RPM Edge Routersthey are connected to and with each other. In addition, they will formadjacencies with other platforms directly connected to them (becausethey are ABRs). The speed of convergence of OSPF is affected by thenumber of adjacencies and the number of route entries.

Area 1

The second area is Area 1. Area 1 contains the OMCR, the OMCIP, theCisco PDSN cluster, the MMs, the AAA, the Terminal Server (TS) andany gateway routers connected to customer LANs.

The area also includes the Catalysts which serve as ABRs for betweenthis area and the backbone (Area 0). Area 1 contains no ASBR routers. Itwill operate using the default route and will be configured as a totallystubby area. If a device in Area 1 requires more than the default route (ifattached to several networks (e.g. O&M LAN and the BSSAN network)then that NE will be configured with the static route(s) summarizing theaccess to that network (e.g. RAN network could be summarized to10.x.x.x). Those static routes will alleviate the process of re–distributingin Area 1 external routing information (Type–5 LSA).

Area 2

The third OSPF area is Area 2. This area contains an RPM within anMGX, the pBTS router and the connections between them. The RPMcard Edge Routers are ABRs for between Area 2 and the backbone (Area0). This area is actually a series of areas, each one associated with anRPM card Edge Router but having the same area number. Thiseliminates the need for Edge Routers on each Aggregation Point fromhaving to exchange routing information.

The BTS routers act as ASBR between this area and the pBTS AS. SinceArea 2 contains an ASBR, it must be configured as a a “not so stubbyarea” (NSSA) which limits the flow of LSAs and routes needed todetermine the routing functions. However, this allows for external routesfrom the pBTS to be summarized (as possible) and advertised to area 0.All packets coming from a pBTS can only flow out through the EdgeRouter and on to the Catalyst. The packets flowing into a BTS cannotexit that routing area (stub) and are only terminated there. This purposeof enabling OSPF in this area is to allow the connection to a BTS to bere–parented to another RPM card Edge Router on the same or a differentAggregation Point without changing the configuration files for thepBTS. The Aggregation Point connections may need to be re–configuredto match the span provisioning to the pBTS.

6



Each connection between an RPM card Edge Router and a pBTS routeris configured as a totally stubby area. This eliminates the need for routeadvertisements into or out of these areas (except for the default route)and reduces the routing table on the RPMs /Edge Routers. It alsoeliminates the need for the RPMs /Edge Routers to exchange routinginformation about their stubs (because they are totally stubby). Packetpipe connections can also be configured as NSSA so that the same RPM/Edge Router can be used for both packet pipe connections and pBTSrouter connections in R16.1 and on. Since these areas are totally stubbyand Area 2 is not continuous across all RPMs/Edge Routers, a pBTSrouter cannot be connected across RPM/EdgeRouter boundaries.

Hence, area 2 is configure as an NSSA total stub.

IP addressing at each Aggregation Point does not need to be contiguoussince there is no summarization at the Aggregation Point level. Theaddresses for each pBTS are selected from a subnet and can besummarized. All of the spans for a particular pBTS router will generallyshare a single MLPPP session and must connect to one Edge Router(e.g. one RPM card). However, the spans from a pBTS router may besplit into more than one MLPPP group during re–parenting or otheroperations. Each RPM/Edge Router will connect to two or three pBTSsand can connect to a maximum of 8 BTSs.

SDU/VPU Area

The SDU and VPU have their own OSPF Area. The SDU area containsthe SDU and the Catalysts which serve as ABRs between this area andthe Core AS back–bone.

For redundancy, each Catalyst will have a pair of links per SDU, onelink per ISB. Each link is a Gbps Ethernet. The ISBs in the SDU will beconfigured as ASBRs and therefor this area needs to be configure asNSSA which will allow external–AS LSAs of the SDU to reach theBSSAN. A default route must be provided by the Catalysts to the SDUsto route external addresses.

The only element reachable by SDUs are the Catalysts ABR therefore itis not necessary to advertise inter–area summary LSAs (type–3 andtype–4) which will reduce the size of the routing tables of the NEs.

SDU Area will be configure as a totally stubby NSSA.

The VPU routers (ASBRs) connecting the VPU AS to the BSSAN CoreAS will be part of this Area. The VPU has one link per ISB to each CoreRouter. The Core Router ABR is the only element directly connected tothe VPU. Since this area is configured as an NSSA, the external–ASLSAa from the VPU will re–distributed in the BSSAN Core AS. Sincethis area is totally stubby, the inter–area summary LSAs from outsidethis Area will not be advertised into this area.

MM II Area

Area 3 and Area 4 contain the MMII. They are NSSAs. The Core routerwill act as the ABR between the Area 0 and Area 3 and Area 0 and Area4.

6



BTS AS

(New to 16.1) Another OSPF area is the packet BTS Area 51 (which isnot part of the BSSAN Core AS). Each BTS will,in effect, form its ownAS. This area is managed and used internal to the BTS. The pBTS routerserves as an ASBR for this area/system and isolates the private addressesused within each BTS from other BTSs and the rest of the network. AllpBTSs use the same AS number. The pBTS router does not use BGP tocommunicate internal addresses so the AS number is not advertisedoutside of the BTS.

SDU AS

Each SDU forms an AS by itself and is required for the followingreasons:

S The SDU uses an internal subnet referred to as the Internal SDUsubnet. This subnet is part of the common platform and allows theSDU to use internal IP addresses for communication. All SDUs willre–use the same set of IP addresses for internal communication. Thisimplies that this subnet is not to be advertised by the routing protocol.

S The SDU needs to advertise end points (e.g. BPP subnets, SPROC,etc.) to the BSSAN Core AS and will be summarized via externalType–7 LSAs.

The SDU AS is formed by configuring the ISB routers as ASBR and oneor more OSPF areas including the ISBs by them self and other SDUcomponents (e.g. SPROC cards, BPP cards, etc.).

The default route from the BSSAN Core AS needs to be distributed intothe SDU AS. The ISBs needs to be configured to perform route filteringso that the private SDU addresses (from the Internal SDU network) arenot advertised to the SDU Area NSSA.

VPU AS

The VPU re–uses the same platform as the SDU and the AS descriptionfor the SDU also applies for the VPU.

BGP

As described previously, OSPF provides routing within the BSSANwhich is equivalent to saying that OSPF provides routing functionalitywithin the Autonomous System. However, a routing function is alsorequired for communication between Autonomous Systems.

The protocol used for this routing is the Border Gateway Protocol(BGP). The main function of a BGP system is to exchange networkreachability information with other BGP systems. This includesinformation on the full path of Autonomous Systems that traffic musttransit in order to reach the target network. BGP works on the“hop–by–hop” basis since a given AS only reports those routes it uses toits neighboring ASs.

6



As stated previously, the BSSAN communicates externally over BGPlinks. In general the Catalysts within a BSSAN will be used to providethe EBGP links. These links will attach directly to other BSSANs withinthe same Mobile Telephone Switch Office (MTSO) or to WAN routersthat are part of a BGP backbone. The BGP backbone forms a separateAS. The architecture includes designs and rules for an MTSO with avariety of sizes.

BGP uses a reliable transport protocol (i.e., TCP) to exchange routinginformation. This eliminates the need to perform messagesegmentation/recovery within the BGP protocol. BGP requirements inthis document assume TCP/IP as the underlying transport protocol.

If a particular AS has more than one BGP speaker, care must be taken sothat each BGP speaker has a consistent view of routing within the AS.This will ensure that all BGP speakers on the border of the AS arereporting a consistent routing picture to external networks. In the CDMARAN this is accomplished by requiring that all BGP routers serving asgateways externally to the BSSAN also serve as OSPF routers internallyto the BSSAN. The routing updates preformed by OSPF will ensure thateach BGP speaking router has a consistent routing picture.

It is also important that all BGP speakers in an AS present a consistentpicture of external routes when advertising routing information into theAS. In the BSSAN this is accomplished by requiring that all BGProuters in the BSSAN be inter–connected. Routers that have BGPconnections to other routers that are within the same AS are said to berunning “Internal” BGP (IBGP).

Routers that are running BGP on interfaces that are external to the ASare said to be running “External” BGP (EBGP). Any two routers thathave established a connection (i.e., a TCP virtual circuit) for thepurposes of exchanging BGP information are said to be “neighbors” or“peers”.

To configure a BGP link to another router three things are required.First, the router must be configured as a BGP router and given the AS IDfor the Autonomous System it is part of. Second, the interface IP addressof each BGP neighbor must be specified. Finally, the AS ID of eachneighbor must be specified.

Specifying the IP address of the BGP neighbor interface has onedrawback. Should that interface fail, the route will become unavailable.One way around this is to define the interface IP address to be aloopback interface configured on the neighbor router. This way theneighbor router will always be reachable even if one interface fails(assuming a second route is configured in the network). This capabilityis selectively implemented.

6



If EBGP routers are connected and the remote interfaces are loopbackinterfaces, these interfaces must be defined as “BGP Multihop”connections. This indicates to the router that it is not directly connectedto the interface that terminates the BGP connection. More than one hopwill be required to reach the loopback connection (i.e., one hop to thedirect connect interface then another hop from there to the loopbackinterface).

In the R16.1 network many BGP routers will be directly connected andto prevent single interface failures from causing an outage, each interfacebetween two ASs will have two physical links. Since the failure of anygiven interface cannot cause an outage we will not need to configureloopback interfaces and make use of BGP multihop in these cases 16.0.

In some situations, it may not be desirable to use BGP for interfacesbetween ASs. Instead, static routes could be configured between the ASsand default gateways configured. In this case, BGP requirements do notapply.

QoS (Quality of Service)

The 16.1 CDMA RAN QoS functions for IP datagrams include thefollowing:

S Traffic marking

S Classification and scheduling

The marking function exists at the edge of the devices of the CDMARAN for ingress traffic. Marking also occurs at the end nodes fororiginating traffic, e.g. signalling and O&M. The purpose is to ensureconsistent marking of all traffic in the Transport Network. In thebackhaul interface between the Packet BTS and the Aggregation Point,the Packet BTS will mark the generated traffic.

The system marks the packets in 4 classes. Each class has a differentpriority level.

S Voice Bearer

S Packet Data Bearer

S Supplemental Data Bearer

S Low Latency Signalling (call processing signalling that requires lowtransfer delay)

Routing devices, such as the BTS Router and the Aggregation PointRPM card for example, perform the queuing function. During thequeuing process, the router gives higher precedence to packets markedwith a high priority than packets marked with a lower priority.

6



In a release 16.4.1 system with the RPM Capacity increasefeature, the QoS feature is removed from the processing ofpackets in the forward direction on the RPM. The removalof QoS means that there is no longer priority given to voicepackets over the other traffic classes. All packets areprocessed in the order that they arrive.

NOTE

IP Addressing

The following information is subject to change; pleaserefer to IP Planning documentation for the most currentinformation.

NOTE

The IP address allocation process at the system level shall follow theguidelines/requirements in the System Address Allocation Strategy, theRAN Network Topology and the RAN IP Routing Architecture andRequirements to determine how many IP addresses each BSSAN needsand how to divide the available IP addresses into different contiguousaddress pools to satisfy the OSPF routing area requirements. The systemlevel IP addressing allocation process shall produce a detailed plan of IPaddress allocation at the BSSAN level based on the physicalconnections.

CDMA RAN (System) Level IP Address Allocation:

A block of IP addresses from 10.a1.b1.c1 to 10.x1.y1.z1 is allocated forBSSAN#1



Blocks of IP addresses are reserved for the existing circuit system (2GSystem).

Blocks of IP addresses are reserved for certain O&M systems that areoutside the system level IP management domain.

System Level IP Address Allocation:

The IP addresses of the NEs in a BSSAN will be extracted from severalpools. The IP addresses in each pool need to be contiguous. There are 4different pool types per BSSAN: CBSC, AN, BTS and the PCF.

The PCF pool is optional and is used to assigned IP addresses to thePSI–PCF cards. The three other pool are mandatory. The IP addresses ofthe PCFs could be from the CBSC or the PCF pool but the IP addressesof all PCFs in a CBSC will be allocated from the same pool.

6



The four other pools are mandatory. Each BSSAN will have its ownCBSC, BTS and AN pool of IP addresses while the same range of IPaddresses defines the Common pool and is reused in each BSSAN.

Each BSSAN pool contains following pools:

1) IP addresses for CBSC NEs (MM, XC (pPSI (PKTPCF and PKTSEL)and cPSI ), SDU and other NEs (OMCR, OMCIP, Cisco PDSN, AAA,terminal server) that are connected with a particular AN. IP addresses forthe interfaces between the NEs and the AN.

2) IP addresses for BTSs in a particular AN and IP addresses forthe interfaces between the BTSs, BTS routers and RPM.

3) IP addresses for NEs that are inside a particular AN and the interfaceIP addresses between these NEs.

4) The IP addresses that could be reused in each BSSAN (Common ineach BSSAN).

5) IP addresses for the PCFs inside a BSSAN. This pool is optional.

DHCP Client on SDU and VPU

In release 2.16.4.1, the SDU and VPU upgrade adds a DHCP clientwhich supports automatic provisioning of IP addresses by the DHCPserver on the Core router (Catalyst). The SDU and VPU will discover IPaddressing and OSPF parameters using DHCP rather than throughmanual commissioning (no commissioning device needed). The OMC–Rgenerates the DHCP configuration for the Catalysts.

DNS

In release 2.16.4.1, the RAN capabilities for DNS expand to include:

S Linked name space across MTSOs. Operators can navigate to otherdevices in other MTSOs using DNS names.

S MM and OMC–R upgrade to each include DNS clients. An operatoron an MM will be able to navigate from these devices to other devicesin the RAN using DNS names.

S Allows creation of DNS name for every device in the RAN. TheOMC–R no longer manages operator defined names for devices.

S Automatic updates of the DNS root server by the subordinate DNSservers.

6



Notes

6


Chapter 7: SDU (Selection Distribution Unit)

Table of Contents

SDU (Selection Distribution Unit) 7-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selection Distribution Unit 7-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDF Functional Description 7-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 7-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selection and Distribution 7-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handoff Detection and Execution 7-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Layer 3 Call Control (L3 CC) 7-28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Implement IS–95/IS–2000 Call Control Signalling Messages 7-28 . . . . . . . Vocoder connection 7-28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocate BTS Resources during Handoff/Call Setup 7-28 . . . . . . . . . . . . . . A8 / A9 Packet Data Call Functions 7-29 . . . . . . . . . . . . . . . . . . . . . . . . . . . Supports Supplementary Services 7-30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supports Call Trace 7-30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDL Support 7-30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface to Resource Management/Allocation Function 7-31 . . . . . . . . . . . ICSHO for 16.0 CBSCs 7-31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supplemental Channel Management 7-31 . . . . . . . . . . . . . . . . . . . . . . . . . . . RAS Determination 7-32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L2 MS 7-33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UDP Termination 7-33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UDP–ER Termination 7-33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCTP Termination 7-33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SMAP UDP 7-33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BCP/CPE UDP 7-33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Control 7-34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Segmentation and Reassembly (SAR) 7-38 . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Link Protocol (RLP) 7-39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiplexing function 7-40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Termination 7-40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XC Termination 7-40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VPU Termination 7-40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCF Functional Description 7-41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Control Function 7-41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCF Architecture 7-41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCF Management 7-44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A9 Link Management 7-44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A11 Link Management 7-44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7



SCTP Termination 7-45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A9 UDP 7-45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A11 UDP 7-45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downlink Bearer Manager 7-45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uplink Bearer Manager 7-46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A8 GRE 7-46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A10 Termination 7-46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Address Translation Function 7-46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RA (Resource Allocation) Functional Description 7-47 . . . . . . . . . . . . . . . . . . . . . . . SPROC Card – Resource Allocation, Management Function 7-47 . . . . . . . .

7

SDU (Selection Distribution Unit)


Selection Distribution Unit

Overview

The Selection Distribution Unit or SDU is the element within theIP–BSC that performs the Selection and Distribution as well as thePacket Control functions. The SDU has many advantages:

S Move from an embedded functionality to a “Client Server” model

S Network level redundancy

S Decouple capacity planning

S Increased network design flexibility

S Simplified Configuration data management

The SDU uses a tier 1 platform with significant architectural advantagesthat adds additional value in the continuing product evolution.

BPP/BPPR1

In release 2.17.0.x, BPPR1 replaces the BPP. BPPR1 is a hardwarerevision due to parts obsolescence. BPPR1 functionality is the same asBPP. Note that the terms BPP and BPPR1 may be used interchangeablyin this document. Whenever the document refers to ”BPP,” it impliesboth BPP/BPPR1 HW types.

7

SDU (Selection Distribution Unit) – continued


Figure 7-1: IP–BSC

7



The term SDU will be used to denote the external SDUfunction. The use of PSI cards to do the SDU function willbe specifically referred to as “Internal SDU”.

NOTE

Description

The name Selection Distribution Unit identifies two of the three keyfunctions of the SDU: selection and distribution (SDF) and PacketControl Function (PCF).

Function

Selection (SDF)

In a IP–BSC the signal from the handset may be received by multipleBTSs. These signals are sent to the SDU for selection and the SDUpicks the signal that is most usable using a complex algorithm thatconsiders multiple factors including signal strength, error rate, and otherfactors. The “Selected” signal is then used in the remainder of thesystem. This selection process is done every 20 milliseconds to ensurecontinued signal quality. The information used for selection is also usedfor soft handoff (SHO). The functionality is listed below:

S Terminates upstream packets from multiple BTSs involved in a callor data session.

S Relays payload data from selected packets to Vocoder or DataGateway Unit.

S For each air frame, selects the one upstream packet containing thefewest bit–errors. (Frame Selection)

S Extracts and terminates BTS control messages embedded in packets.(In–Band Control including Power Control/PATE)

S Extracts and terminates Mobile Station control messages embeddedin packets. (RF–L2)

S Extracts and relays Mobile Station data burst messages embedded inpackets. Forwards these messages to data gateway unit. (RLP)

See the SDF Functional Description, PCF Functional Description, andRA Functional Description section(s) of this chapter for additionaldetails on BPP functionality.

7



Distribution (SDF)

Distribution is the forward path selection from BTS to the handset.Multiple BTSs can service a handset. The “Distribution” algorithm usespower control information, signal to noise, traffic, and other factors tochoose the BTSs that service the handset. The functionality is listedbelow:

S Sources downstream packets to multiple BTSs involved in a call ordata session.

S Relays payload data from Vocoder or Data Gateway Unit to packets.

S Duplicates downstream packets for transmission to each BTS.(Frame Duplication)

S Sources and embeds BTS control messages into packets. (In–BandControl)

S Sources and embeds Mobile Station control messages into packets.Implements reliable transmission over the air. (RF–L2)

S Embeds Data Gateway Unit data burst messages into packets.Implements reliable transmission of these messages over the air.(RLP)


Packet Control Function (PCF)

The Packet control function is the radio side of the data call connectionfrom an IP network. The PDSN terminates the PPP session and workswith the PCF to control the radio side of the data call. The PCF performsthe following functions:

S Terminates A10/A11 IOS standard interfaces.

S Terminates A8/A9–like Motorola proprietary interface.

S Maintains the dormant session when the MS is not on an RF channelbut still connected to a PPP session with PDSN.


Inputs and Outputs

The best description of inputs would be voice signals from various BTSsas received from handsets, and additional parameters about systemoperation. Outputs are processed or selected signals headed either for theBTS or into the voice part of the system.

For the PCF, the signals are bi–directional. The standard model wouldprobably view the Internet via the PDSN as the input and the RAN tohandset as the output.

7



Card Description

With the introduction of R17, the backplane of the SDUand VPU is now common. The difference between theSDU and VPU is that the SDU will still use BPP cards anda different ISB/SPROC. The VPU is then made up of apopulation of BPP2 and DOC–3 cards as well as differentISB/SPROCS. All other hardware is completely commonbetween the SDU and VPU.

NOTE

A new BPP card, BPPR1, will be introduced in R17.Redesign of the previous BPP was required due to partsobsolescence. The new card will offer the samefunctionality as the older version of BPP board, howeverR17 software will be required to utilize the new BPP card.New and previous version of boards can be mixed in thesame SDU shelf provided that the shelf is upgraded to R17software.

NOTE

Chassis Description

The SDU will be housed within the IP–BSC frame with the followingphysical features:

S The IP–BSC frame can house up to 2 SDU Shelves. The shelves in aframe are totally separate units and have no connectivity betweenthem.

Each shelf can accommodate

S Fifteen (15) BPP or BPPR1 cards

S Two (2) CCA cards

S Two (2) ISB/SPROC cards

S Two (2) DGBE cards

S One (1) AIO card

S Two (2) Power Supply Modules

S Three (3) Fan Modules

Each shelf has nineteen slots in the front and and eleven in the rear of theshelf. Four of the front slots are occupied with 2 ISB/SPROCS and2 CCAs leaving 15 payload slots. All cards are Hot Swappable. Thecards described here include CCA, SPROC, BPP/BPPR1, PSM, ISB,DGBE, and AIO.

The payload card, called the Bearer Payload Processor (BPP/BPPR1),performs all the functions above with different software loads. Thequantity of these cards is the primary sizing/scaling factor of system.

7



CCA

The Cabinet and Customer and Alarm (CCA) card provides a 2Nredundant collection point for the presence of ”detect” signals from eachcard, and for terminating the Electronic Identification Device (EID) oneach card. The CCA also provides inputs for shelf level alarms andcontrol over shelf level LEDs. In addition, the CCA providestermination of any Motorola– or Customer–defined alarms that might beterminated at the SDU shelf. Optional relay contacts that could be usedto control the customer’s site equipment are provided by the CCA. Fordebugging purposes, each CCA provides an RS–232 port with accessthrough the AIO boards. The CCA communicates to both ISBsthrough a standard CP2 interface. Finally, the CCA provides acommunication point through its processor to any USB device thatmight be required by a customer (again via the AIO board).

SPROC

The SPROC is a 6U cPCI form factor processor board designed for Tier–1 applications. This board houses a Power PC750 processor, networkinterfaces, MMI ports, and local memory. The 6U SPROC will require aSpryex 4 port 10/100 E–Net NIC PMC module to provide the CP8 linksrequired by the Common Platform architecture. Controlsoftware for the SDU shelf will reside on this card along with some callprocessing and resource management functionality.

BPP/BPPR1

The Bearer Payload Processor (BPP/BPPR1) card is a general purposepayload card capable of providing the Selection, Distribution, and PacketControl Functions of the SDU application.

PSM

The Power Supply Module provides cage level input power conversionfor distribution throughout a given SDU cage.

ISB

The Interface Switch Board implements the Hub connecting the SPROC,network interface, and all payload cards.

Ethernet runs should not exceed 80 meters from the frametop with this card.

NOTE

Cross coupled redundancy is not supported. The Ethernetrequirement will be 1 per ISB>>>2 per shelf and 4 perframe.

NOTE

7



AIO

The AIO slot resides in the rear portion of the SDU shelf assembly andaccommodates one AIO board. The AIO board is the interface for thealarm I/O. The board interfaces with the CCAs through the backplane.An individual AIO board is capable of accepting 16 Customer alarminputs, and providing 8 Customer alarm outputs. Each CCA relays thealarms to the Platform Management O&M function which notifies theOMCR of the alarm condition. The AIO card will also be the input ifBITS (Building Integrated Timing Source) is used.

DGBE

The DGBE resides in the rear portion of the SDU shelf assembly. Theshelf accommodates two DGBE boards. Each DGBE board interfaces toa Gigabit Ethernet signal. The 1000BaseT Ethernet connectionsprovided by the DGBE board are used to interface from the SDU to theAccess Node (AN). Gigabit interfaces are cabled to the top of the frame.

Signal Flow

See Inputs and Outputs.

Redundancy

Multiple redundancy schemes are used in the SDU to meet variousfunctional requirements.

S CCA and SPROC use a 2N redundancy

S Both SDF and PCF BPP cards use load sharing redundancy.

Operation and Maintenance (O&M)

The SDU uses the SMNE maintenance paradigm. Under the oldparadigm, elements would report a fault to a central location and thelocation would then tell the reporting unit what to do or direct theinformation to maintenance for action. Under the new paradigm, themanagement is de–centralized and the elements will usually take care ofany required action and then report the action and result only for recordkeeping.

7

SDF Functional Description


Overview

BPP Configuration

The operator configures a BPP card to perform the SDF set of functionsor the PCF set of functions.

The SDF in the SDU replaces the 16.0 PSI–SEL function.

NOTE

Selector Distributor Function (SDF) Overview

A BPP card with SDF software performs the following main functions:

S Selection and Distribution

S Handoff detection and execution

S Layer 3 Call Control

S Implement IS–95/IS–2000 Control Signalling Messages

S Vocoder connection

S Allocate BTS resources during handoff

S A8 / A9 Packet data call functions

S Support for Supplementary services

S Support for Call Detail Logging and Call Trace

S Interface to Resource Allocation/Management function

S Supports IP–ICSHO with 16.0 CBSCs

S Supplemental channel management

S Reduced Active Set (RAS) determination

S L2 interface to Mobile Station

S UDP Termination

S UDP–ER Termination

S SCTP Termination

S SMAP UDP

S Performs Power control functions

S Performs Segmentation and Reassembly

S Radio Link Protocol

S Multiplexing functions

S cBTS and pBTS termination

S XC Termination

7

SDF Functional Description – continued


Selection and Distribution

The SDF’s main function is Selection and Distribution. After Selectionof traffic received from BTSs, the SDU transfers voice traffic to theVocoder for processing. After receiving voice traffic from the Vocoder,the SDU Distributes the voice traffic to all sectors in the mobile’s activeset. This is done for circuit and packet BTSs.

As a product of frequent soft handoffs in the CDMA system, the mobilestation may have multiple Sectors in its “Active set”, meaning themobile is communicating with multiple Sectors at once during the call.In this case, there is a need for the SDU to pick the best signal from thevarious “copies” of the signal received from different sectors (intra andinter BTS). Likewise, it must distribute copies of the downlink signal toall sectors in the active set of the mobile.

The selection and distribution capability of each CPE provides thefollowing functionality:

S Receives IOS v4.1 formatted bearer frames; these frames contain themessage type and CRC.

S Indicates state changes to Layer 3 Call Control confirming BTS linkestablishment, mobile station acquisition, etc.

S Verifies the reception of packets and aligns the packets based on theFrame Sequence Number from all appropriate BTSs involved in thesoft handoff. This includes declaring time outs and initiating theselection of the best received packet, when necessary.

S From the uplink packets received from each Sector in the mobile’sactive set, the SDU selects the best packet based on the receivedFrame Quality Indicator field.

S Extracts Packet Arrival Timing Error (PATE) information, smoothsdata and generates Time/Frame Alignment requests to the Vocoderwhen necessary.

S Performs Time and Frame Alignment, on a link–by–link basis, in theforward direction.

S Performs (SIR+RSSI) filtering for SCH management to determine thereduced active set.

S Distributes downlink frames to all BTSs involved in the soft handoff.

7



Handoff Detection andExecution

Overview

SDF supports handoff procedures including intra–CBSC soft handoff,inter–CBSC soft handoff as well as hard handoff.

Handoff Overview

For CDMA systems, handoff detection processing will take place in theXC (16.0)/SDU (16.1) and in the MM. The XC/SDU will detect the needto handoff, perform handoff pre–processing and identify events. TheMM will determine the handoff type, perform target selection andperform channel allocation. Both the MM and the SDU request PacketBTSs to allocate traffic channel resources. For Circuit BTSs, the MMwill still perform the traffic channel resource allocation.

Throughout this section, a function performed by“XC/SDU” means that in a 16.0 system the XC performsthe function and in a 16.1 system the SDU performs thefunction if equipped.

NOTE

7



Figure 7-2: CDMA Handoff Functional Diagram, SDU architecture

Handover

Execution

SDUControl

SDU

Selector

CentralizedPower CTL

BFIGeneration

Spreading/Despreading

Modulation/Demodulation

Packet MCC

GLIpBTS

PDSNInternet traffic

A10/A11

EstimationResourceAllocation

MM Hardware Platform & Phys Interface

Application Interface

Mobility Manager

System DatabaseHandover Detection

CallProcessing Handover Execution

ResourceAllocation

RLP(variable rate frame generation)

Control Interface

XCTranscoding

(variable rate frame generation)

CentralizedPower CTL

BFIGeneration

Spreading/Despreading

Modulation/Demodulation

Circuit MCC

GLIcBTS

Eb/Io and Eb/NoEstimation

MSCForVoice

User Traffic

Interface

XC Control

CentralizedPwr Ctrl

Eb/Io and Eb/No

Packetframeformat

PSI–CE PSI– SIG

Traffic

Control

If equipped, the VPU can replace the XC cabinet for theVocoding function.

NOTE

7



CDMA Handoff Types

CDMA allows for several types of handoff to take place. The followinglist elaborates and summarizes each possible type of supported handoff.Note that there are always two types of soft and softer handoff. One typecalled an “add” is used to instruct the mobile to include new pilots in itsactive set. The other type called a “drop” is used to instruct the mobile toexclude old pilots from its active set.

Handoffs may be triggered by either Mobile Assisted Handoff (MAHO)or Database Assisted Handoff (DAHO) techniques. MAHO techniquesdepend on measurements made by the mobile and returned to the BTS.DAHO techniques depend on information on cell configuration stored inthe CBSC/BTS along with the system’s knowledge of whichcells/sectors control a particular call.

MAHO techniques may be used to trigger soft, softer and hard handoffs.DAHO techniques may be used to trigger hard handoffs.

S Inter BTS, intra XC/SDU Soft Handoff: This handoff type is expectedto be the highest percentage of handoffs in CDMA systems as thistype contributes to the greatest amount of reverse channel interferencereduction and capacity increase. A mobile station has simultaneousconnections to two or more cells and receives power control orders(for reverse link closed loop power control) from each cell in the softhandoff.

S Inter BTS, Inter–CBSC Soft Handoff: This handoff type denotes astate where a mobile station maintains connections to multiple sectorslocated under control of different CBSCs. In this case, the CBSCscontrolling the BTSs are linked by either special sub–rate trunk circuitconnection or by packet network connection.

S Intra BTS, Inter Sector, Intra XC/SDU Softer Handoff: This handofftype denotes a state where a mobile station maintains connections tomultiple sectors all based at the same cellsite location.

S Inter or Intra BTS Hard Handoff: This handoff type denotes either achange in operating frequency, a change in 1.25ms frame offset, achange from an IS–2000 radio configuration 1 to another, or a handoffin which the intersection of old active set pilots with new active setpilots is the null set.

S Hard Handoff to Analog: This handoff type is used to transition amulti–mode mobile station from CDMA operation to operation on ananalog system.

7



Additional Handoff Functionality – The following describe subtypesof handoff.

S CASHO: In release 16.3, the system supports the CASHO featurewhere the system can, during call setup, assign the mobile into softhandoff, using the Extended Channel Assignment message.

S CDMA Inter–band Handoff: This handoff type enables CDMAnetworks to perform inter–band hard handoffs for voice calls in adual–band CDMA system, for mobiles capable of the two bandsinvolved. This handoff type supports handoffs within a dual–bandCBSC, inter–CBSC handoffs, and inter–MSC IS–41 handoffs. As ofrelease 2.16.4.x.x, DAHO and pilot beacon methods can trigger thishandoff type. The supported bands are 800 MHz and 1900 MHzbands. Handoffs in both directions are supported. This handoff typesupports IS–95A, 1X, and 1xEV–DV (when available). There is onekind of IBHO that will not be supported: when the mobile is movingfrom a single–band area to a dual–band area; the mobile will stay onits current band (soft handoff).

S 1X Hard Handdown: This handoff type enables the CDMA system totrigger hand downs to IS–95A for 1X voice calls in situations where1X resources (1X channel elements) are provisioned but are busy orotherwise unavailable for assignment into Soft Handoffs. The MMwill not process a hand down request if resource allocation fails forconditions such as RF load, walsh code availability, backhaul capacity,etc. In addition, the MM will proceed with the HHO if the candidatepilot strength is 0.5 * Tcomp stronger than all the active pilots. Bothcircuit BTS and packet BTS support 1X Hard Handdown.

S Band Overflow for Dual–Band CDMA Systems: This handoff typeenables operators with dual–band systems to overflow calls betweenbands during blocking scenarios. When mobiles access a particularband where the capacity threshold has been reached, the systemoverflows mobiles to the other band for system access. Overflow onlyoccurs when the capacity threshold is reached. (Mobiles must be dualband capable). The Band Overflow functionality depends upon theLeast–Loaded Carrier feature, which enables monitoring of the Ec/Ior(remaining capacity) and unused or available throughput on eachcarrier to determine the least loaded carrier for calls.

S Software Based Idle Mobile Hard Handoff Support (Packet Backhaulonly): This handoff type provides support for hard handoffs acrosscarriers and CBSCs (intra– or inter–band) in the situation where amobile is idle and there is no hardware pilot beacon to redirect themobile. The Extended Neighbor List message (Band class 1, 3, 4) orGeneral Neighbor List message (all Band classes) on the Pagingchannel tells the mobile to scan PNs on alternate carriers (within thesame band or in the different band). The MS algorithm determines thedecision to retune to a new carrier.

7



Complex Handoffs

A complex handoff in a CDMA system is defined as a handoffinstruction to the mobile station which makes more than one change tothe mobile’s active set. For example, MAHO measurements from themobile station may indicate that it is desirable to enter into a state wherenew connections are supported from both the current cellsite location(softer handoff) and from another cellsite location (soft handoff).

The current system supports multiple add operations and multiple dropoperations for inter–CBSC soft/softer and intra–CBSC soft/softerhandoffs. A maximum active set size of 6 pilots is supported. Multipleadd and multiple drop operations are limited to a single channel elementeach for each handoff detection event.

Pilot shuffling with multiple add–drops, triggered from a single handoffdetection event, is also supported to maintain an optimal active set whenthe number of soft/ softer legs is at the maximum. The system currentlysupport pilot shuffle involving channel elements in up to two BTSs in asingle handoff direction message to the mobile station.

Database Assisted Handoff

This handoff detection algorithm is used to determine when to transitiona mobile station to another frequency band and/or air interface other thanCDMA. Since normal CDMA Mobile Assisted Handoff (MAHO)handoff detection methods cannot be used to determine a suitable target,database–stored information concerning partially or fully overlappinghandoff targets must be used to carry out the handoff process.

Inter–CBSC Soft Handoff

Soft and softer handoffs can be performed with a cell under anotherCBSC by using inter–CBSC soft and softer handoff procedures toconnect the target CBSC channel element to the source CBSC via aninter–CBSC subrate channel or an inter–CBSC packet network.

The method of performing inter–CBSC soft/softer handoffs via subratechannels and Motorola proprietary control links between CBSCs isreferred to as the trunking method, to distinguish it from the A1 method,using standardized IS–634 procedures, which may be implemented in thefuture, or from the method where bearer connection between CBSCs canbe established through the common AN.

A call can be in inter–CBSC soft/softer handoff with multiple targetCBSCs at the same time. A call enters into inter–CBSC soft handoffwhen the mobile reports a viable candidate pilot that points to anXCSECT (external sector data base), and this XCSECT has inter–CBSCsoft handoffs enabled. Note that the XCSECT can be residing in thesource CBSC or can be backhauled from target CBSC as part of aprevious inter–cbsc handoff procedure. Subsequent inter–CBSC soft andsofter handoff operations may occur with pilots that are in the neighborlist of a target CBSC cell. Target CBSC neighbor lists are sent back tothe source as part of the inter–CBSC soft/softer procedure. In these“remote neighbor lists”, the source checks for matches with candidatesreported by the MS.

7



The source CBSC remains in control of the call until no source handofflegs remain. At this point the source determines if it should transfercontrol to a target CBSC via a hard handoff. Such a hard handoff isnamed “Anchor Handoff”.

Handoff Modes

The system is required to support various “handoff modes”. The handoffmode defines how the handoff detection algorithm and executionprocedures operate. The mode defines what triggers the system to add apilot to the mobile station’s active set. Two modes are defined – “TAdd”and “TComp”. When operating in the TAdd mode, any time a pilot risesabove the TAdd or the TComp threshold, the system will attempt to addthat pilot to the mobile station’s active set via a soft or softer handoff.When operating in the TComp mode, a pilot must rise above the TCompthreshold before the system attempts to add it to the mobile stationactive set.

For further description of the air interface (RF:) messagesdiscussed throughout this chapter, refer to the SMAPOperator’s Guide. SMAP is the tool which collects anddecodes the air interfaces messages from the XC/SDU.

NOTE

Mobile Station Operation

The mobile station assists the handoff process by transmitting PilotStrength Measurement Messages or Extended Pilot StrengthMeasurement Messages. The mobile measures the strength of theForward Pilot channels and includes the measured pilot strength in thePSMM or EPSMM along with the PN Offset Index/PN Offsetidentifying the measured pilots.

7



Database Parameters

The following are the database parameters which apply to handoffdetection.

Some parameters are specific to SDU, some are not. Thissection does not discuss the Complex soft handoffparameters in the MM database. Refer to the CellularSystem Administration Guide for further information anddefault values.

NOTE

S TAdd – Pilot Detection Threshold – The threshold above which a pilotmust rise in order for the MS to transmit a pilot strength measurementmessage. The system sends this parameter to the mobile station in theRF: Extended System Parameters Message, RF: Extended HandoffDirection Message, RF: General Handoff Direction Message, RF:Universal Handoff Direction message and the RF: In Traffic SystemParameters Message.

S TComp – Active Versus Candidate Set Comparison Threshold – Thethreshold which a candidate set pilot strength must rise above anactive set pilot to cause the MS to transmit a pilot strengthmeasurement message. The system sends this parameter to the mobilestation in the RF: Extended System Parameters Message, RF:Extended Handoff Direction Message, RF: General Handoff DirectionMessage, RF: Universal Handoff Direction message and the RF: InTraffic System Parameters Message. This parameter is also used forhandover detection event discrimination in the XC/SDU subsystem.

S TDrop – Pilot Drop Threshold – The threshold below which a pilotstrength must drop in order for the MS to transmit a pilot strengthmeasurement message. The system sends this parameter to the mobilestation in the RF: Extended System Parameters Message, RF:Extended Handoff Direction Message, RF: General Handoff DirectionMessage, RF: Universal Handoff Direction message and the RF: InTraffic System Parameters Message.

S TTDrop – Active or Candidate Set Drop Timer – The amount of timein seconds the MS will allow an active or candidate set pilot strengthto remain below the drop threshold before action is taken to removethe pilot from the active or candidate set. The system sends thisparameter to the mobile station in the RF: Extended SystemParameters Message, RF: Extended Handoff Direction Message, RF:General Handoff Direction Message, RF: Universal Handoff Directionmessage and the RF: In Traffic System Parameters Message.

S Soft_Slope – the slope used by the mobile station to calculate the Addand Drop thresholds for adding a pilot to the active set, or dropping apilot from the active set. The system sends this parameter to themobile station in the RF: Extended System Parameters Message, theRF: In Traffic System Parameters Message,, RF: Universal HandoffDirection message, and the RF: General Handoff Direction Message.

7



S Add_Intercept – the intercept used by the mobile station to calculatethe Add threshold for adding a pilot to the active set. The systemsends this parameter to the mobile station in the RF: Extended SystemParameters Message, the RF: In Traffic System Parameters Message,RF: Universal Handoff Direction message, and the RF: GeneralHandoff Direction Message.

S Drop_Intercept – the intercept used by the mobile station to calculatethe Drop threshold for dropping a pilot from the active set. The systemsends this parameter to the mobile station in the RF: Extended SystemParameters Message, the RF: In Traffic System Parameters Message,RF: Universal Handoff Direction message, and the RF: GeneralHandoff Direction Message.

S HandOffMode – Specifies to the XC/SDU which handoff mode to use.Currently two modes are defined. TAdd mode and TComp mode.TAdd mode tells the system to add a pilot to a call as soon as itcrosses the TAdd threshold. TComp mode tells the system to wait fora pilot to rise above the TComp threshold before it is added to a call.This data exists in the XC/SDU database, not in the MIB.

S PilotInc – Pilot PN Sequence Offset Index Increment – The mobilestation uses this field to determine how remaining set pilots should besearched. It is set to the largest increment such that the pilots of theneighboring sectors are integer multiples of the increment. This data issent to the mobile station in the RF: Neighbor List Message and theRF: Neighbor List Update Message. The XC/SDU must use the samevalue as is contained in the MIB.

S NeighborList – Neighbor List – This list contains all of the neighborsector PN offsets for the current call. This parameter is passed to theXC/SDU during a CDMA parameters update.

S DAHO – DAHO Indicator – This parameter indicates whether asector–carrier is near a border and contains neighboring or overlappingsectors operating on another frequency and/or non–CDMA signallingscheme.

S DAHOHysTimer – DAHO Hysteresis Timer – This parameter is usedto prevent “ping–pong” handoffs between two sectors which havebeen marked with the DAHO flag. After a hard hand–in, origination,or termination in a border sector, majority border checks will bedisabled for a period of time in seconds equal to the value of thisparameter.

S HandoffMethod – Handoff Method – This parameter specifies themethod (none, hard, soft trunking, soft aplus) to be used to hand thecall off to a sector external to the CBSC. The scope of this parameteris per external CDMA sector.

S Inter–CBSC Soft Handoff Override – This parameter is used to“turn–off” Inter–CBSC soft handoffs between two MMs. It is checkedby both source (in handoff detection) and target procedures. Whenoverride is allowed, the alternative action of either no handoffs or hardhandoffs is indicated (no handoffs, hard, no override). The scope ofthis parameter is per inter–CBSC trunk group.

7



S AnchorHoMeth – Anchor Handoff Method – This per CBSCparameter indicates the condition upon which triggers the source MMto move a mobile in Inter–CBSC soft handoff from a source (or“anchor”) MM to a target MM once all the source legs have beendropped.

S Num_Cand – Number Candidates – The maximum number ofcandidate pilots reported by the mobile station that will be considered,in strength order, for handoff.

S ICTRKGRP:: ConnToggle: indicates whether an ICSRCHAN basedor IP based inter–CBSC handoff connection type shall be used toconduct the soft handoff.

S CBSC:: N–Way Hard Hand Out flag – This flag indicates whetherN–way Hard Hand Out is turned on, turn on for hand down only, orturned off.

S Sector/Carrier::Radio Configuration Class Capability: This parameterindicates whether the BTS is capable of supporting 2G voice andpacket data calls only, or 2G voice and packet data calls and also 3Gvoice calls, or 2G voice and pacekt data calls and 3G voice and packetdata calls, or 3G packet data calls only. The scope of this parameter isper carrier/sector.

S CBSC::MSCIntVer: Indicates the IOS compliance of the MSC. Thisparameter can be set to Pre–3G or IOS_4_1

RF Measurements Used in CDMA Handoff and Power ControlDetection

For handoffs, the main piece of data to contend with is the contents ofthe pilot strength measurement message. The RF: Pilot StrengthMeasurement Message or RF: Extended Pilot Strength MeasurementMessage is sent autonomously by the mobile station in response to aparticular pilot crossing the T_ADD, T_COMP, or T_DROP thresholds.The message contains PN phase measurements and strengths of thepilots that the mobile station is monitoring.

XC/SDU Handoff Detection

Upon reception of the Pilot Strength Measurement message by theXC/SDU, this L3 message is routed to the handoff detection process.Note that the handoff detection process shall store the contents of the last16 RF: Pilot Strength Measurement Messages or RF: Extended PilotStrength Measurement Messages. This information can then (if desired)be retrieved by MMI or used in additional handoff detection processing.

The XC/SDU will identify the base stations used in the PSMMs, andidentify to the MM whether the pilots in these base stations are currentlyactive pilots or candidate pilots.

7



The XC/SDU will determine which events caused the mobile station tosend a PSMM to the base station. In the current system, the only validevents are: TAdd threshold crossed, TComp threshold crossed, andTDrop threshold crossed. Note also that multiple events may be possiblewithin each message (a complex handoff). In the current system, only asingle event will be reported. The precedence will be TComp, TAdd, andTDrop. Pilots not in the active set are scanned to see if their associatedstrengths have crested over the TAdd threshold, or if their strengths haveexceeded the TComp of one of these pilots. The XC/SDU will determineif the events triggering the PSMMs are valid given the mobile’s activeset state (i.e. the number of pilots in the mobile’s active set).

When a PSMM containing valid events is received by the XC/SDU, theXC/SDU will determine whether to signal to the MM that a handoff isnecessary.

The MM determines the type of handoff to be performed – either soft orsofter and add or drop (or multiple adds/drops) or shuffle.

Handoff Execution

CDMA standards introduces the concept of soft handoff. In this system,a soft handoff is defined as a state where a mobile station iscommunicating with two or more cell sites simultaneously.

During soft handoff, the mobile station will perform maximal ratiodiversity combining on the downlink signals received from each cell site.Each cell site which receives the mobile station’s uplink transmissionwill forward it to the XC/SDU. The XC/SDU then selects the frame tobe decoded.

There is a special case of soft handoff called softer handoff. Softerhandoff is similar to soft handoff except that two of the cell sitesinvolved are sectors of the same cell. Softer handoff provides equipmentsavings for the following reason. The mobile station will frequently be insofter handoff, and the CDMA cell site receiver (the MCC,Multi–Channel CDMA card) is designed in such a way that a singlechannel element can support multiple sides of the softer handoff. Asingle CDMA channel resource that generates multiple Walsh channelsis used in this case.

The MCC uses a RAKE mechanism with multiple taps which can beallocated to any of the sectors within a cellsite location. In softerhandoff, maximal ratio combining is performed between two sectorantennas to yield one uplink stream to the XC/SDU. This is differentthan soft handoff which is actually selection diversity on the uplinkbetween multiple cellsite receivers at the XC/SDU.

Handoff execution is the act of bringing together many different piecesof hardware and the associated software, plus the mobile station, into asynchronized procedure to transfer the infrastructure connections andmobile station code programming.

7



In the simplest case, the following are two of the more importantoperations that must occur in order to facilitate a handoff.

S The target cell transceiver must be notified of the impending incominghandoff. Information communicated to the target cell may be the typeof call, type of mobile and the mobile identity, encryption informationfor the mobile, and possibly priority of the call that the subscriber iscurrently engaged in.

S The XC/SDU must be notified of the change in connection from onecell to another. The notion of soft handoff requires a device to selectthe best traffic channel frame with the lowest error rate from among 2or 3 possible inputs. In addition, the XC/SDU handles the variablerate data feature of respective CDMA Air interface standards thatmobile complies to.

SDU Handoff Execution

This section describes the procedures required for an inter/intra cell,inter/intra–CBSC generic handoff. This section describes the proceduresfor:

S soft add

S soft drop

S softer add

S softer drop

S (complex handoff) combination of all of the above

Currently, this procedure handles fundamental traffic channel adds, ifany, on a BTS, fundamental traffic channel drops, if any, on a BTSwhich can be the same as the BTS targeted for fundamental trafficchannel adds, and supplemental traffic channel adds or drops across allBTSs involved in the hand–off.

In high speed packet data calls, supplemental trafficchannels are used in combination with the fundamentaltraffic channel when greater throughput is required.

NOTE

This procedure handles the connectivity for both intra–CBSC andinter–CBSC (source side) soft/softer handoff operations. This procedureis applicable to (IS95B FCH/SCCH channels and IS–2000 1X FCHsonly) high speed packet data calls, low speed packet data calls, circuitdata calls, fax calls, or voice calls.

Upon detection of a soft/softer handoff add and/or drop event, the XC orSDU–SDF signals the MM with the information the MM needs todetermine the necessary handoff type. It is possible that the MM willmake an alternate decision based upon other information, as in the caseof hard handoff.

For example, in the case of a handoff add, the MM notes that a hand–offadd has been requested based on information received from theXC/SDU, and begins the call processing procedures to select targetcellsites for the handoff operation.

7



Upon the MM’s selection of appropriate target cellsites and, for circuitBTSs, the MM’s allocation of appropriate radio channel resources tosupport the handoff, the MM will send the request for handoff and waitfor completion. The Handoff Direction message is “filtered” downthrough the system with each responsible device (e.g. BTS, SDU) takingthe information it needs to execute the handoff, and then an IS–95 orIS–2000 Handoff Direction message is sent to the mobile over the airinterface. The final version sent to the mobile includes the informationthe mobile needs to change to the new active set, such as the list ofSectors, the walsh codes to use for fundamental and/or supplementaltraffic channels, and so on.

A couple differences to this scenario are as follows:

S When the handoff target list contains a packet BTS, the MM willnotify the SDU–SDF of the BTS resource allocator location. TheSDU–SDF is responsible for requesting resources from any PacketBTSs. For packet BTSs, the packet BTS rather than MM will allocateappropriate radio channel resources to support the handoff.

S When a handoff target is a local circuit BTS or remote circuit BTSover ICSRCHAN, the MM will also allocate a CPP and a PSI–SIGand notify the SDU–SDF of their location. This allows the SDU–SDFto communicate with the XC (CPP) to setup connectivity to thesecircuit BTSs via PSI–CEs.

7



Intra–CBSC Handoff Scenarios

If equipped, the VPU can replace the XC cabinet for theVocoding function. Refer to the VPU chapter for details onVPU protocols.

NOTE

Figure 7-3 depicts signalling paths for Intra–CBSC handoff scenarios.

SDU

CPP

MSI

cBTS

XCDR

PSI–SIG

XC

MSC

MSI

(cTCH)

KSW

SCTP/IP SRCHAN

A1

PDSN SDFPCFpBTS

(pTCH)SCTP/IP

IPSCAP

IPSCAPR–P

A1 1

A9

SCAP/LAPD

MM

FEPSCAP/TR

IPSCAP

SCTP/IP

MCAP

MCAPMCAP

MCAP

SCAP

SCAP

PSI–CE

MCAP

T1/E1

SCAP

A1

Figure 7-3 Signalling paths – Intra–CBSCHandoff Scenarios

7



Inter–CBSC Handoff Scenarios with ICSRCHAN

Figure 7-4 depicts signalling paths – Inter CBSC scenarios withICSRCHAN.

SDU

SDFPCF

cBTS

MSC

(cTCH)

CPP

MSI

XC

KSW

TargetCBSCSourceCBSC

SRCHAN

ICSRCHAN

SCTP/IP

(A1)T1/E1

MSI

PDSN

IPSCAP

R–P

A11

SCAP/LAPD

A9

CPP

MSI

XCDR

PSI–SIG

XC

MSIKSW

FEP MCAP

MCAPMCAP

MCAP

SCAP

SCAP

PSI–CE

MCAPMM

SCAP/TR

IPSCAP

SCTP/IP

FEP MM

SCAP/LAPD

SCAP/TR

SCAP

A1

Figure 7-4: Signalling paths – Inter CBSCscenarios with ICSRCHAN

7



Inter–CBSC Handoff Scenarios with AN

Figure 7-5 depicts signalling paths for inter–CBSC handoff scenarioswith the AN.

Figure 7-5: Signalling paths – Inter–CBSCscenarios with AN

SDU

SDFPCF

cBTS

MSC

(cTCH)

CPP

MSI

XC

KSW

Target CBSCSource CBSC

SRCHAN

SCTP/IP

(A1)T1/E1

pBTS

(pTCH)

PSI–SIG

PDSN

IPSCAP

R–P

A11SCTP/IP

IPSCAP

SCAP/LAPD

A9

CPPXCDR

PSI–SIG

XC

MSIKSW

FEP

MCAPMCAP

MCAP

SCAP

SCAP

PSI–CE

MCAP

MM

SCAP/TR

IPSCAP

SCTP/IP

FEP MM

SCAP/TR

MCAP

IPSCAP

SCTP/IP

A1

7



Bearer Connectivity for Intra–CBSC Scenarios (SRCHAN andAN)

Figure 7-6 depicts bearer connectivity for Intra–CBSC scenarios(SRCHAN and AN).

SDU

PSI–CE

CPP

MSI

cBTS

XCDR

PSI–CE(cBTS)(SDU)

XC

MSC

MSI

(cTCH)

KSW

UDP/IPUDP/IPSRCHAN

T1/E1

TDM

PDSN SDFPCFpBTS

(pTCH)

UDP/IP

A3/DPPF

A3/DPPFR–P

A10

A8

DS0:CPCF/Strau

A3/DPPF

Figure 7-6: Bearer connectivity for Intra–CBSC scenarios (SRCHAN and AN)

7



Bearer Connectivity for Inter–CBSC Scenarios – ICSRCHAN

Figure 7-7 depicts bearer connectivity for Inter–CBSC scenarios withICSRCHAN.

SDU

SDFPCF

PSI–CE

CPP

cBTS

XCDR

PSI–CE(cBTS)(SDU)

XC

MSC

MSI

(cTCH)

KSW CPP

MSI

XC

KSW

TargetCBSCSource CBSC

SRCHAN

ICSRCHAN

UDP/IP

T1/E1

TDMTDM

MSIMSIMSI MSI

PSI–CE

(pBTS)

PDSN

A3/DPPF

R–P

A10

DS0:CPCF/Stra

A8

Figure 7-7: Bearer connectivity for Inter–CBSC scenarios with ICSRCHAN

7



Bearer Connectivity for Inter–CBSC Scenarios – AN

Figure 7-8 depicts bearer connectivity for Inter–CBSC scenarios with theAN architecture.

CPP

cBTS

XCDR

PSI–CE

(SDU)

XC

MSC

MSI

(cTCH)

KSW CPP

MSI

XC

PSI–CE

KSW

TargetCBSCSource CBSC

SRCHAN

T1/E1

TDMTDM

pBTS

(pTCH)

(cBTS)

SDU

SDFPCFPDSN

UDP/IP

A3/DPPF

UDP/IP

A3/DPPF

UDP/IP

A3/DPPF

R–P

A10

A8

Figure 7-8: Bearer connectivity for Inter–CBSC scenarios with AN

7



Layer 3 Call Control (L3 CC)

The BCP element on a BPP card performs Layer 3 Call Control (L3CC). The BCP L3 CC, in conjunction with the MM and the MSC,controls call setup with service negotiation, call release, handoff, andsupplementary services for the mobile station. L3 CC interfaces withexternal network elements including the MM, BTS, and vocoder tomanage call resources.

Implement IS–95/IS–2000 CallControl Signalling Messages

The SDF L3 CC supports IS–95 A/B and IS–2000 RF upper layercontrol messages over the traffic channel.

Vocoder connection

During call setup, the SDF L3 CC establishes a connection to thevocoder gateway (in the VPU frame or the XC frame) to providevocoding services for voice calls.

Allocate BTS Resources duringHandoff/Call Setup

The SDF L3 CC interfaces with BTSs to establish connections during ahandoff:

S If the target cell is a packet BTS, the SDF L3 CC requests the packetBTS to allocate channel elements. In the case of a handoff where atarget cell is a circuit BTS, the MM requests that circuit BTS toallocate channel elements.

S If the target cell is a circuit BTS, the SDF L3 CC requests the XCs toprovide circuit interworking functionality for the call. This means thatthe circuit BTS and SDU will process the call through the assignedXC PSI–CE circuit–to–packet interworking card.

The SDF L3 CC performs the same process during call setup.

7



A8 / A9 Packet Data CallFunctions

Overview

For the system to successfully set up a packet data call, the end resultmust be that the mobile station can establish a PPP (Point to Pointprotocol) software connection with the PDSN. The mobile station andPDSN use PPP to configure an “OSI model” datalink–layer andnetwork–layer connection, including IP address assignment. Once thePPP session is established, the MS can access the IP network (ISP,Intranet, etc) through its connection to the PDSN.

The following RAN logical, upper–layer connections provide thesupport for the MS – PDSN interface:

S A10/A11 – a bearer and control interface between the PCF and thePDSN, where the bearer path is established for a particular MS

S A8/A9 – a bearer and control interface between the SDF and the PCF,where the bearer path is established for a particular MS

Once the system establishes the A8/A9 connections and the A10/A11connections, the communication path exists for the MS – PDSN PPPsession setup. In effect, the mobile station and PDSN communicationsession (control, bearer) runs “over” the A10/A11 and A8/A9 logicalconnections. The A10/A11 connection acts as a “bridge” between thePDSN and SDU and the A8/A9 connection acts as a “bridge” betweenthe SDU and the BTS to the MS.

L3 CC Role

The SDF L3 CC requests the “A9 manager” to establish A8 connectionswith the PCF to provide data service for the requested packet datasession.

A9 Link Management

A9 Link Management is performed by the BPP card’s BCP and providesthe IOS V4.1 A9 control functions to and from PCFs. The A9management functionality includes the following:

S Supports A8/A9 interface setup procedures: including MS initiatedcall set up events and re–activations from the dormant state, andNetwork initiated re–activations from the dormant state.

S Supports A8/A9 interface call clearing procedures for both MS andnetwork initiated call releases to the dormant state.

S MS power downs.

S PDSN initiated call releases.

7



A8 GRE

PCF termination is performed by each BPP card Channel ProcessingElement (CPE), terminating bearer Generic RoutingEncapsulation(GRE) frames to/from the PCF. A8 is Motorola’sproprietary version of the A8 IOS interface, modified to account forMotorola specific congestion management and keep alive procedures onthe A8 bearer path.

All call traffic exchanged between the PDSN and the SDUis wrapped in GRE headers.

NOTE

A9 UDP

UDP is used for A9 signaling transport to communicate with the PCFcontrol function. A9 is Motorola’s proprietary version of the A9 IOSinterface, modified to account for Motorola specific SCTP messagesbetween the MM and the PCF, while all the other A9 signaling messageswill be carried over UDP between SDF and PCF.

Supports SupplementaryServices

The SDF L3 CC supports IS–95 or IS–2000 signalling to the MS neededto support supplementary services, including Flash with information,Feature Notification, DTMF and Short Message Service.

Supports Call Trace

The SDF L3 CC provides call trace support to SMAP, supportingreal–time call activity events, layer 2 events and real–time statisticgathering.

CDL Support

The SDF L3 CC provides call detail logging on a per call basis. L3/L2events and power control related statistics will be gathered by L3 CCand reported to the MM’s CDL facility as part of call release procedures.

Supplemental channel statistics appear in CDLs for 1X data calls.

7



Interface to ResourceManagement/AllocationFunction

During initialization, the SDF L3 CC provides resource capacityinformation to the SDU Resource Management/Allocation function. Thisfunction resides on the SDU’s SPROC card.

When the MM receives an Origination or Page Response message fromthe mobile station triggering setup of a call, the MM communicates withthe SDU Resource Management/Allocation function to request SDUresources for the call. It will request a channel processing element(CPE) on the BPP’s Board Control Processor (BCP) and that channelelement will run SDF or PCF depending upon its configuration. Forpacket data calls, the MM asks the Resource Management/Allocationfunction to assign a channel element from an SDF card and a channelelement from a PCF card.

The SDF L3 CC also supports resource audits in conjunction with theResource Allocation application in order to synchronize resource usage.

ICSHO for 16.0 CBSCs

The SDU supports IP–ICSHO with 16.0 CBSCs.

Supplemental ChannelManagement

The BCP performs supplemental channel scheduling, supportingon–demand time slices for packet data users. The BCP supportson–demand supplemental channel allocations for the 1X forward andreverse channel, including the following functionality:

S Determines the Forward Supplemental Channel data rate required forthe mobile based on the buffer information provided by the RLP layer.When the amount of downlink packet data buffered is above a certainthreshold, the BCP determines the F–SCH rate to request from theBTS for transmission of the data to the MS.

S Determines the reverse supplemental data rate required upon receipt ofIS–2000 Supplemental Channel Request Messages (SCRM) from themobile. During an established packet data session, the mobile stationtransmits SCRMs when it has to transmit more data than can besupported by the base Fundamental traffic channel assigned to the call.

S Determines the forward/reverse Reduced Active Set (RAS), selectinga subset of active pilots to provide supplemental service to mobiles inorder to increase the efficiency of the radio channel. The forward linkRAS is determined by the filtered Ec/Io of each sector and theRSSI+SIR provided by the BTS. The reverse link RAS is determinedby filtered RSSI+SIR provided by the BTS.

S Requests supplemental channel resources from the BTSs (selectedafter RAS determination). The BCP coordinates among multiple BTSsto obtain a common supplemental channel timeslice to provide highspeed data service to the mobile.

7



S Originates IS–2000 Extended Supplemental Channel AssignmentMessages to mobiles via BTS radio interface, to assign Forward orReverse supplemental traffic channels for certain time slices. TheSDU sends an ESCAM based on MS request for higher data rate(SCRM) or after the SDU determines that the forward link data rateneeds to be increased based on RLP buffer information. Assignmentof a supplemental traffic channel in combination with an existing basetraffic channel (either Fundamental or Dedicated Control) enableshigher transmitting/receiving throughput.

RAS Determination

Periodic PMRM Reporting

For packet data calls operating in on–demand supplemental assignmentmode and with Reduced Active Set (RAS) mode enabled throughdatabase configuration, periodic Power Measurement Report Messagereporting will be turned on. The periodic reports are used by the SDU(or, in 16.0, the XC PSI–Selector function) to determine the reducedactive set for assigning supplementals. The mobile station transmitsPMRMs to report forward link frame errors and signal strength.

Resource Request Processing

This is the processing that occurs for each databurst. In this phase, theSDU determines that there is a need to request supplemental resources,and determines the active set into which the supplementals should beassigned. For forward supplementals, the decision to requestsupplementals and the requested rate are driven by the amount of databuffered for the call at the SDU and PCF. For reverse supplementals, thisdecision is driven by the request from the mobile.

After the decision is made to request supplementals, SDU determines theactive set for supplementals. For forward supplemental channel requests,if the database parameter FwdRAS1x is ENABLED, the SDUdetermines the supplemental active set as a subset of the base channel(fundamental traffic channel or dedicated control traffic channel) activeset. For reverse supplemental channel requests, if the database parameterRevRAS1x is ENABLED, SDU determines the supplemental active setas a subset of the base channel (fundamental traffic channel or dedicatedcontrol traffic channel) active set. Once the SDU has determined theneed for a supplemental and the desired rate, the SDU and the BTSinteract to setup the assignment, after which SDU communicates theassignment, if any, to the mobile.

The SDU uses two main sources for determining the RAS:

S The mobile station’s measurement of the Ec/Io of each Forward Pilotchannel – this is sent to the SDU in the PMRM (as well as PSMM)

S The reverse signal estimate, from the BTS (an estimated RSSI)

7



L2 MS

The L2 MS function provides assured and unassured delivery service toLayer 3 messages. This implements the ARQ sublayer functionality asspecified in the cdma2000 standard.

The functionality includes the following:

S Terminates L2 mobile signaling and forwards it to the upper layerapplication.

S Inserts message sequence numbers and ack sequence numbers fordownlink MS messages.

S Handles L2 retransmissions to provide a reliable transport for layer 3messages.

S Ensures reliable transmission via per message setting of ack requiredand/or fast repeat fields.

S Identifies and discards duplicate messages.

UDP Termination

Supplementary channel control messages between the SDU SDF BoardControl Processor (BCP) and the BTSs will use UDP.

UDP–ER Termination

Call control application messages between the SDU SDF Board ControlProcessor (BCP) and the control portion of the BTS will use UDP–ER.UDP–ER is a proprietary enhancement implemented on top of UDP toprovide an acknowledge based retransmission mechanism that istransparent to the application.

SCTP Termination

Call control application messages between the BCP and each MM andthe control portion of the XC will use SCTP.

SMAP UDP

Call activity, layer 2 logging and statistics gathering will be providedand reported to SMAP using UDP.

BCP/CPE UDP

UDP communication is used between the BCP controller and each CPEfor call processing control messages.

7



Power Control

Power Control Overview

In 16.1, the system will only support Centralized PowerControl.

NOTE

The 16.0 release supports distributed and centralized power control. Asin IS–95, distributed power control uses Open Loop Power Control,Outer Loop Power Control, and Closed Loop Power control schemes.

Currently in IS–95, power control is done via distributed power control.This means that the power control mechanism is distributed betweendifferent functional entities including the channel element. This methodwill still be supported for 2G calls.

The 16.0 release introduced centralized power control functionality. In16.0, this functionality is in the XC PSI card, and in 16.1 thisfunctionality is in the SDU if equipped. When a call needs to be setup orhanded to a different system, the MM will decide what power controlscheme to use, centralized or distributed, based on the mobile’scapabilities.

Power Control is performed by each SDU SDF Channel ProcessingElement, consisting of the following 2G and 3G centralized powercontrol functions:

S Calculates forward link gain ratio and communicates it to theselection/distribution function.

S Calculates reverse link outer loop thresholds and communicates it tothe selection/distribution function.

Overview of Open and Closed Loop Power Control

Reverse power control consists of open and closed loop components.

Open loop power control, which is performed at the MS accounts forcommon or symmetrical losses on the reverse and forward links due topath loss and shadowing. It is relatively slow (with respect to the closedloop) generating new updates roughly every 20 ms. The amount ofmobile transmit power necessary to establish the reverse link isestimated by subtracting total noise plus interference measured at themobile antenna from a factor. The open loop mobile transmit powerestimate will be refined by reverse closed loop power control.

7



The closed power control loop consists of an inner and outer loop. Theouter loop is maintained at the base station and involves feedback basedon frame erasures to determine an Eb/No set point in order to maintain aconstant FER. The inner loop is distributed between the mobile and thebase station where the feedback mechanism is based on the powercontrol bit. The closed loop accounts for non–symmetrical (uncorrelated)losses between the reverse and forward links due to Raleigh/Rician (fast)fading, interference level variations (e.g. voice activity or loading),differences in an antenna’s transmit and receive gain, and otherassociated losses (combiners, connectors, duplexers, etc.). It is the fastpower control loop being updated at an 800 Hz rate for fundamentalchannels and at 400Hz for supplemental channels that effectivelymitigates small to medium power variations due to fast fading. Fastpower control is most effective at slow speeds whereas interleaving isnot. (Note: the smaller the power swings or variations measured at theserving base station for each mobile the smaller can be the transmittedmobile power necessary to achieve a 1% FER. This lower requiredpower level results in less interference and hence allows more channelsto be supported.)

Overview of Forward Power Control

The purpose of forward channel power control is to minimize theamount of power transmitted to a particular mobile station on theforward link. Minimizing power in a CDMA system reduces interferenceand thus increases forward channel capacity. However, there is atrade–off between the amount of forward link power dedicated to amobile station and the forward link voice quality that mobile station willexperience. The power control algorithm must balance power againstacceptable voice quality.

Forward power control is based on monitoring RF: Power MeasurementReport Messages from the mobile station. This message reports themobile station’s count of detected forward link frame errors in additionto the mobile station’s measurement of the signal strength of the Forwardpilot(s).

Also, J–STD–008 and some IS–95 standards support Erasure IndicatorBit (EIB) for Rate Set 2 calls. The EIB indicates whether a forwardframe was an erasure frame or not. This is a good indication of whetherthe forward power gain should be adjusted or not.

7



Centralized Reverse Power Control

The XC/SDU guides reverse power control for the IS–2000 call.

S The XC/SDU designates an MCC–1X channel element to performreverse power control with the mobile. The MCCces perform reversepower control under the guidance of the XC/SDU.

S The XC/SDU calculates the outer loop threshold and provides thethreshold to the MCC–1X channel element which is performingreverse power control for the mobile. The power control outer loopoperation uses the post–Selection Frame Quality Indicator (FQI) asinput to determine the outer loop threshold. FQI is sent by a BTSinvolved in a call to the SDU every frame period using an IOS 3Greverse FCH/DCCH packet frame. For a voice call, FQIs of the FCHframes are used; for a data call, the FQIs of the DCCH frames areused.

S The XC/SDU calculates the reverse link set point and propagates theset point to all channel elements supporting the Fundamental/DCCHchannel of the call through forward link Fundamental/DCCH frames.The set point is really the reverse pilot set point.

S If the MCC1Xce gets the set point, the MCCce uses certain pieces ofinformation to “translate” the outer loop threshold into reverse pilotEc/Nt and compares that with the chip energy of each power controlgroup received on the Reverse Pilot Channel. The MCC1Xce sets thepower control bit based on that comparison. The mobile uses thatpower control bit to adjust transmit power. However, before the firstforward frame arrives, the channel element sets the outer loopthreshold to nominal threshold.

Centralized Forward Power Control

The XC/SDU calculates the Forward traffic channel gain for FCH,DCCH, and SCH and provides the information to the MCC–1X channelelements. The CBSC supports separate forward power controlsubchannels on the reverse pilot channel for controlling the forwardFCH, DCCH and SCH, if required for the call.

Each MCC–1X channel element supporting the call follows the forwardpower control guidance provided by the centralized call control and thepower control indications in the reverse power control to adjust theForward traffic channel power when transmitting on the forward link tothe mobile. However, the effective power is within the maximum andminimum gain of the current hand–off state.

7



Forward Gain Setting

Time (frames)

MCC periodically stepsdown forward gain setting

Mobile station measuresexcessive frame errors, sendsPMRM for Rate Set 1 and 2 calls.

For RS1 and RS2 calls, CPP receives PMRMrequests gain increase from XCDR , MCCincreases gain setting.

The mobile use EIB to indicateforward frame erasure for RateSet 2 calls.

For RS2 calls, XCDR increase gain settingwhen an erasure EIB is received.

Figure 7-9: Forward Power Control

7



Segmentation and Reassembly(SAR)

SAR is performed by each Channel Processing Element and provides thefollowing functionality:

S Buffers fragmented uplink LAC PDU frames and reassembles theLAC frame.

S Verifies CRCs and discards frames if a match is not made.

S Appends the CRC on the LAC frame received from Layer 2.

S Segments LAC PDUs received from Layer 2 into a maximumavailable size to fit in the downlink frame.

S Sends layer 2 confirm messages after transmission of each final frameof air interface signaling messages.

7



Radio Link Protocol (RLP)

Overview of RLP

The RLP layer is responsible for managing transfer of user data framesin IS–95 and IS–2000 low speed and high speed data calls. The RLPlayer resides in the SDF and the mobile station (they are RLP “peerlayers”).

S maintains and checks the sequencing of the received user data framesto determine if there are any skips in sequencing and therefore anymissing/unreceived frames.

S sends NACK control frames to the peer RLP layer to requestretransmission of the missing frames.

S resequences the frames (since some are received out–of–order) in itsbuffer and sends them to the upper layer.

S maintains a NACK list and if it does not get a response in a certainnumber of rounds of NAK frame transmission, it aborts the frame.

S RLP can also segment frames if necessary

There are three versions of the Radio Link Protocol:

S IS–2000 1X HSPD – RLP 3

S IS–95B HSPD – RLP 2

S IS–95A LSPD – RLP 1

RLP frames consist of three basic types: a frame that contains user data,Idle frames (to maintain the link), or RLP control frames.

For more information on Radio Link Protocol in relation to CDMA dataservice option calls, refer to the document TIA/EIA/IS–707–A DataService Options for Spread Spectrum Systems.

Overview of SDU Support for RLP

The following functionality is supported on each SDF ChannelProcessing Element:

S RLP 1, 2, and 3 protocols.

S Receives forward–link bearer data and buffer–level information fromPCFs

S Receives frame–by–frame transmission indications, includingbandwidth allocations after multiplexing.

S Transmits the RLP bearer channel for multiplexing and IOSencapsulation.

S Provides aggregate buffer level information from the RLP and thePCF to the Supplemental Channel manager for supplemental channelscheduling purposes.

S Provides flow control signaling to the PCF based on configurable highand low buffer watermarks.

S Receives reverse–link RLP data after multiplexing.

7



S Routes re–sequenced GRE encapsulated data to the PCF.

S Notifies L2 MS when data inactivity timer has expired.

Multiplexing function

The Mux capability of each SDF Channel Processing Element providesthe following functionality:

S Indicates erasures to the vocoder in case of bad packets, late packets orlost packets.

S Extracts frame quality information and EIB (for IS–95 A/B 13K only)and routes this information for use by power control.

S Extracts any L2 information and passes the L2 frame for SAR.

S Extracts traffic data and passes it to the vocoder for voice calls orcircuit data calls.

S Extracts traffic data and passes it to RLP for packet data calls.

S Receives L2 messages and determines the transmission schedule basedon voice activity, fast repeat requests, etc.

S Generates dim&burst requests as appropriate.

S Receives transmission F–SCH/R–SCH timeslice information via SCHmanagement to control 1X supplemental channel transmission.

S Performs forward multiplexing to combine layer 2 signalinginformation and packet payload data.

BTS Termination

BTS termination is performed by each SDF Channel ProcessingElement, terminating bearer (call traffic) UDP/IP packets to/from

S circuit BTSs, via the PSI–CE cards in the XC which provide thecircuit–to–packet interworking function, and

S packet BTSs.

XC Termination

XC termination is performed by each SDF Channel Processing Element,terminating bearer (call traffic) IOS frames to/from the XC subsystem.

VPU Termination

VPU termination is performed by each SDF Channel ProcessingElement, terminating bearer (call traffic) frames to/from the VPUsubsystem.

7

PCF Functional Description


Packet Control Function

This section provides a description of the SDU Packet Control Function.The SDU performs Packet Control functions for CDMA2000 1X packetdata calls.

PCF Architecture

Overview

For the system to successfully set up a packet data call, the end resultmust be that the mobile station can establish a PPP (Point to Pointprotocol) software connection with the PDSN. The mobile station andPDSN use PPP to configure an “OSI model” datalink–layer andnetwork–layer connection, including IP address assignment. Once thePPP session is established, the MS can access the IP network (ISP,Intranet, etc) through its connection to the PDSN.

S Simple IP – The PDSN provides the MS with a temporary IP addressto use, which the PDSN or associated AAA selects from the IPaddress pool; or

S Mobile IP – The PDSN allows the MS to use its home network IPaddress, and sets up a tunnel to the HA in the MS user’s home IPnetwork.

The following RAN logical, upper–layer connections provide thesupport for the MS – PDSN interface:

S A10/A11 – a bearer and control interface between the PCF and thePDSN, where the bearer path is established for a particular MS

S A8/A9 – a bearer and control interface between the SDF and the PCF,where the bearer path is established for a particular MS

Once the system establishes the A8/A9 connections and the A10/A11connections, the communication path exists for the MS – PDSN PPPsession setup. In effect, the mobile station and PDSN communicationsession (control, bearer) runs “over” the A10/A11 and A8/A9 logicalconnections. The A10/A11 connection acts as a “bridge” between thePDSN and SDU and the A8/A9 connection acts as a “bridge” betweenthe SDU and the BTS to the MS.

7

PCF Functional Description – continued


A9

IP–SCAP

PPP

IS–2000PPP

RAN

(Radio Access Network) MM

PCF

ISP

(IP Network)

PDSN

AAA HA

Packet Access Network

SDF (SEL)

BTS

MS

A9

A8

A11

A10 (GRE)A8

PCF

PSI PlatformServices

RA

(GRE)

API

Figure 7-10: PCF Architecture

7



MS Functions

The MS (mobile station) is the user of the packet data service. The MSaccesses the IP network (ISP, Intranet, etc) through its PPP connection tothe PDSN. The RAN provides the support connection for the MS –PDSN interface.

SDF (SEL) Functions

SDF is the Selector / Distributor function as described in the “SDFFunctional Description” portion of this chapter. SDF manages the A8/A9link to the PCF supporting packet data calls.

PCF Functions

The PCF manages the A10/A11 interface to the PDSN for each packetdata session. The PCF interfaces to the SDF (the SEL) to complete the“bridge” between the PDSN and the RAN.

PDSN Functions

The PDSN acts as the gateway between the landline IP Packet DataNetworks and the cellular system. That is, the PDSN transfers packetdata traffic between the cellular system and the landline PDN. ThePDSN accomplishes this through the interface to the PCF function.

The PDSN, in combination with HA and AAA devices, provides thefollowing types of Internet/Intranet access services to users accessing thesystem:

S Mobile IP

S Simple IP

S Proxy Mobile IP

HA Functions

An HA performs the following major functions:

S Interface to the PDSN for Mobile IP registration actions and per–calltunnel creation

S Forwarding of Mobile IP call packets from the home network to thePDSN

S Forwarding of Mobile IP call packets from the PDSN to the homenetwork (reverse tunneling)

AAA

The role played by an AAA Server in a data network is to authenticate,authorize, and perform accounting for an incoming client that wants touse network resources for data activities.

The AAA server is a complete implementation of the widely–used IETFstandards–track RADIUS (Remote Authentication Dial–In User Service)protocols, and is a full–function AAA (authentication, authorization,accounting) server.

7



The main functionality provided by the AAA Server is the Visited AAAfunctionality. It can also offer Home AAA services to mobiles whosehome IP network is the same as the home access provider network. (I.E.,The home access service provider is also an Internet service provider.)Optionally, the AAA Server may provide Broker AAA functionality toother domains.

PCF Management

PCF Management is performed by the Board Control Processor andprovides the following functionality.

S Coordinates with A9 and A11 management to provide tunnelingbetween the PDSN and the SDU.

S Maintains mobile sessions, both active and dormant.

S Allocates the A8 uplink and A10 downlink key field and sets uprouting tables in the bearer manager.

S Updates the Resource Management/Allocation function of the mobilesession status to keep the Resource Management function (on theSDU SPROC card) in sync with the PCF load.

S For new mobile sessions, the PCF manager provides PDSN selection.

S Provides fault management upon a PDSN failure: for active calls, PCFreselects the PDSN and establishes a A10 connection; for dormantcalls, PCF pages the mobile to re–establish a connection with anotherPDSN.

S Releases A8 connections when an A8 link failure is reported bydownlink bearer management.

S Interfaces with the MM to page mobiles when downlink bearermanagement receives data for a dormant mobile.

S Supports the status audit procedures with ResourceManagement/Allocation function to ensure resource usage is in sync.

S Provides resource capacity information to the ResourceManagement/Allocation function during initialization.

S Performs resource allocation between Channel Processing Elements(CPEs) and assigns calls to specific CPEs.

A9 Link Management

A9 Link Management is performed by the BCP and supports:

S A9/A8 setup procedures

S A9/A8 clearing procedures

A11 Link Management

A11 Link Management is performed by the BCP and supports:

S A10 connection setup procedures

S A10 connection registration procedures

S A10 connection release procedures

7



S A10 connection accounting procedures

SCTP Termination

Call control application messages between the BCP and the MM will useSCTP.

A9 UDP

UDP is used for A9 signaling to communicate with the SDF controlfunction. A9 is Motorola’s proprietary version of the A9 IOS interface,modified to account for Motorola specific SCTP messages between theMM and the PCF, while all the other A9 signaling messages will becarried over UDP between SDF and PCF.

A11 UDP

UDP is used for A11 signaling transport to communicate with thePDSN.

Downlink Bearer Manager

Downlink Bearer Management is performed by each CPE via modifiedA8 and A10 interfaces for bearer traffic from the PDSN to the SDF.

Bearer Management consists of the following for the downlink:

S Extracts key fields in PDSN GRE packets and looks up the A8 SDFdestination, including the IP address and key field.

S Provides buffer storage for downlink packets towards the SDF whendownlink traffic is congested or the mobile is in a dormant state.

S Provides the remaining downlink buffer information in the proprietaryA8 interface.

S Informs the PCF Management when data is received for a dormantmobile.

S Supports downlink flow control when the congestion bit is set in anuplink packet received from an SDF; it will stop sending A8 outboundbearer packets and start buffering the A10 incoming packets receivedfrom the PDSN.

S Sends keep alive control packets every so often to ensure linkintegrity.

7



Uplink Bearer Manager

Uplink Bearer Management is performed by each CPE via modified A8and A10 interfaces for bearer traffic from the SDF to the PDSN.

Bearer Management consists of the following for the uplink:

S Extracts key fields in SDF GRE packets and looks up thecorresponding A10 PDSN destination, including the IP address andkey field.

S Informs the Downlink Bearer Management of congestion controlinformation.

S Monitors A8 connections and reports link loss when packets are notreceived for a certain duration.

A8 GRE

GRE from the SDF is terminated at the CPE. A8 is Motorola’sproprietary version of the A8 IOS interface, modified to account forMotorola specific congestion management and keep alive procedures onthe A8 bearer path. Uplink packets are received from the SDF and routedfor uplink bearer management. In the downlink, packets are receivedafter downlink bearer management and forwarded to the SDF over theGRE tunnel.

A10 Termination

GRE from the PDSN is terminated at the CPE. Uplink packets arereceived from the PDSN and routed for downlink bearer management. Inthe uplink direction, packets are received after downlink bearermanagement and forwarded to the PDSN.

Address Translation Function

ATF (Address Translation Function) is a feature which is available toadvertise a single PCF IP address to the PDSN. The first DSP will beused for (Address Translation Functionality).

7

RA (Resource Allocation) Functional Description


SPROC Card – ResourceAllocation, ManagementFunction

Logical Functions

At a high level, the Resource Management application provides thefollowing common functionality on behalf of both SDFs and PCFs:

S Provides SDU resource availability updates to the resource clients(MMs).

S Allocates SDF/PCF resources upon receipt of allocate resource requestfrom the resource clients (MMs).

S Keeps track of resource status via the O&M interface

S Performs resource clean up upon resource failure.

S Places resources back into the resource pool upon resource recovery.

S Performs load balancing by distributing allocations between thepayload cards to ensure resources are not overloaded.

S Performs resource audits of payload cards.

S Supports test commands to allow specific resources to be used for testcalls only

S Applicable to both SDF and PCFs

S A SDF or PCF resource is provisioned as either Test or Commercial,on a BPP level.

S Collects PM statistics.

S For PCF resources, the Resource Allocator provides the followingadditional functionality: Maintains mobile session state (idle, active,dormant); stores service configuration information for dormantmobiles; supports an anchor PCF by querying for mobile sessionsamong external PCF RAs.

Auto Discovery Management

Auto–discovery multicast and registration procedures are used to supportmultiple MMs.

During initialization, RM obtains the allocatable resources from allpayload cards, specifically SDF and PCF payloads. Once RM gatherscapacity information from all payload cards, RM informs the MMs ofthe resource availability.

Under normal operating conditions, resource availability information isupdated periodically. However, if a certain resource type (SDF or PCF)becomes unavailable or a new resource becomes available, RM updatesresource clients of the change in resource availability.

7

RA (Resource Allocation) Functional Description – continued


Client Registration and Link Management

The Client Registration and Link Management functionality provides theresource client registration function in support of registration withmultiple MMs as well as the link management function for RM links tothese MMs.

SDF Resource Allocation

Upon receipt of an SDF resource request from an MM, RM allocates therequested resource from its available SDF resource pool. RM performsload balancing to distribute the load between the SDF payload cards.Because the data transmission requirements of a call cannot be knownahead of time, a unit called a Band Width Unit (BWU) is used toestimate load on a SDF. A voice or low speed data call is permanentlyset at 100 BWU while the default setting for high speed data calls will be200 BWU. The setting for high speed data calls will also be configurableat the OMC–R. When a call is released, the SDF notifies RM of themobile state. RM then moves the resource back to the available resourcepool and updates the capacity status.

PCF Resource Allocation

RM manages mobile dormancy as well as resource allocation. Resourceallocation procedures for PCF calls rely on the same calculations forcapacity to balance the load as SDF calls. All calls, irrespective of theservice option, are assigned the same bandwidth usage. In order tomanage mobile dormancy, however, RM checks if it has a dormantsession for a mobile upon receipt of a PCF resource request from a MM.If there is no local dormant session, RM queries other remote RAs ofany existing dormant session by sending a multicast query messagewithin the PCF zone. If any remote RM has the existing dormant sessionfor the mobile, the remote RM forwards the remote PCF address alongwith service configuration information, if stored, to the local RM. Thelocal RM then forwards the details of the remote PCF resource to theMM. In the case when the dormant call is not located, either locally orby another RA, a new call be allocated.

For dormant mobiles, PCF resources are reserved. A high water mark isdefined such that resource requests will only be honored for dormantmobiles being reactivated. However, if the bandwidth required for thecall is not available, the RM will report this back to the MM which willsubsequently select a different PCF–RA for the call. RM is alsoresponsible for keeping the service configuration for 1X packet data callsin order to reduce the call set up time by skipping service negotiation.Upon receipt of a service configuration update from an MM for adormant mobile, RM stores the service configuration locally and informsthe MM if the mobile comes back from dormancy at a later point.

7



Resource Type Specific (SDF/PCF) Event Dispatcher

The Resource Type Specific Event Dispatcher provides functionalityrequired to handle messages for the application specific resources. Anyapplication specific messaging between the SPROC RM application andthe BPP SDF or PCF application will be over the proxy interface anddispatched through the Resource Type Specific Event Dispatcher.

SCTP Termination

Resource Allocation messages between the SPROC and the MM will useSCTP as transport to support specific resource allocations andde–allocations as well as client registrations.

UDP Termination

Auto–discovery multi–cast messages between the SPROC and the MMand multi–cast messages to other PCFs will use UDP as transport.

Redundancy Support

2N redundancy is supported for the SPROC, subsequently ResourceManagement resides on both the active and the standby SPROC. RM onthe active SPROC will use HAP platform services and APIs to checkpoint the necessary state information to the standby SPROC RM. Whena failure is detected by the HAP platform, fail over is performed and thestandby RM takes over the active role and continues to provide resourcemanagement service. This fail over of SPROCs maintains stable calls.Externally, a client registration procedure will once again be executed byrestarting Auto–Discovery process. Calls will be preserved, therefore,re–registration will not cause any call clean–up activity at the MM.

7



Notes

7


Chapter 8: Packet Data Network (PDN)

Table of Contents

Introduction 8-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 8-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of PDN 8-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packet Data Serving Node (PDSN) 8-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 8-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functions 8-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Home Agent (HA) 8-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 8-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functions 8-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

AAA Server 8-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 8-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functions 8-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inputs and Outputs 8-12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signal Flow 8-12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8



Notes

8

Introduction


Introduction

Introduced in 16.0, the Packet Data Network (PDN) implementsIS–2000 Packet Data, enabling flexible intra/Internet network access formobiles placing or receiving packet data calls. To accomplish thatobjective, the PDN includes special software and some dedicatedhardware to interface the cellular system to the Internet and intranets.

Release 2.17.0.x does not introduce any new functionality in the PDNfrom that provided on 2.16.5.x.

This chapter includes the following:

S An overview of the PDN, and the data equipment needed for a PDN.

S Describes the Packet Data Service Node (PDSN) equipment, whichacts as the gateway between the landline IP PDN and the cellularsystem.

S Describes the Home Agent (HA), which is responsible for managingthe mobility of mobile devices when they leave their home networks.

S Describes the Authentication, Authorization, and Accounting (AAA)Server.

8

Introduction – continued


Overview of PDN

PDSN description

The PDN provides the following:

S Connectivity for CDMA2000 1X packet data

S Support for IS–95B packet data calls

Although the circuit–based Inter–working Unit (IWU), connected to theXC, will continue to support circuit–based Quick Net Connect (QNC)calls, the IWU can share a common services network for transparency ofbasic data services such as text–based Wireless Access Protocol (WAP).

The IS–2000 packet data feature provides subscribers with the ability towirelessly access the Internet, a carrier–supplied intranet, and/or externalcorporate intranets. An IS–2000 packet data–capable subscriber device isassigned an Internet Protocol (IP) address and utilizes the CDMA AirInterface to transfer user data between the subscriber device and theland–based packet data networks. The network implements specialfunctions that allow communication with the wireless subscriber device.

Packet data states

Once registered and assigned a PPP session with the CDMA PDN, aCDMA subscriber device can be in either:

S An active state

S A dormant state.

When in an active state, the subscriber device is assigned to one or moreRF traffic channels and is capable of transferring data. A single CDMAFundamental Channel (FCH) or Dedicated Control Channel (DCCH) isassigned to an active subscriber in both the forward (RAN to MS) andreverse (MS to RAN) directions (one for forward and one for reverse). Ifthe subscriber device supports DCCH, then DCCH will always beassigned. If the subscriber device does not support DCCH, then FCHwill always be assigned. In cases where additional throughput isrequired, a Supplemental Channel (SCH) can be assigned to both theforward and reverse links. The decisions to assign a SCH to the forwardor reverse link are made independently.

When in a dormant state, the subscriber device is registered with thenetwork (has a PPP context with PDSN), but is no longer assigned to anRF traffic channel and is not capable of transferring data.

8

Introduction – continued


Packet data zones

A packet zone is the coverage area managed by a grouping of PacketControl Functions. The PCF grouping is a pooled resource acrossmultiple XCs/SDUs, subtended by a single Mobile Switching Center(MSC).

Limiting a packet zone to a single MSC reduces the complexitiesassociated with setting up calls across MSC boundaries, making it thepreferred system design. While it’s possible to have multiple packetzones within an MSC boundary, we recommend that a packet zone bekept as large as possible, thereby reducing the number of PCF handoffsand eliminating the must do inter–PCF handoff, which requires themobile to temporarily move to dormant.

Maintaining large packet zones reduces the number of PCF handoffsbecause, within a packet zone, the anchored PCF function ensures thatthe user remains on the same PCF.

Each PCF can connect with up to 16 different PDSNs.

Packet Control Function (PCF)

The XC PSI–PCF or SDU BPP–PCF provides the functional interface tothe PDSN portion of the PDN, and is necessary for packet datafunctionality.

8

Packet Data Serving Node (PDSN)


Overview

Introduction

This section describes the PDSN portion of the PDN.

Overview of PDSN

The PDSN acts as the gateway between the landline IP PDN and thecellular system. That is, the PDSN transfers packet data traffic betweenthe cellular system and the landline PDN. The PDSN accomplishes thisthrough the interface to the PCF (XC PSI–PCF or SDU BPP–PCF).

PDSN Clusters

Operators can choose to group from 2 to 12 PDSNs on the samesub–network, forming a PDSN cluster. Each PDSN in a PDSN clusterperiodically broadcasts information about its status and load to all theother PDSNs in the cluster. These broadcasts enable the cluster–basedPDSNs to:

S Minimize the number of handoffs between PDSNs in the cluster

S Balance subscriber call load across the PDSNs in the cluster

S Dynamically add and remove PDSNs from the cluster to provide forredundancy and increased service availability

8

Packet Data Serving Node (PDSN) – continued


Functions

Internet/Intranet Access Services

The PDSN, in combination with HA and AAA devices, provides thefollowing types of Internet/Intranet access services to users accessing thesystem:

S Mobile IP

– An access method allowing a Mobile IP mobile subscriber to accessthe Internet or an Intranet through its connection to the PDSN.

– Mobile IP is an access method allowing a mobile to have a static ordynamic IP address belonging to its home network where it canaccess the Internet/Intranet and receive data, and also roam toforeign networks where it can have data packets forwarded from thehome address to the current address. The PDSN registers the mobilewith its HA in order to notify the HA of the mobile’s currentcare–of–address so that the HA can redirect the packets to thecurrent location (the PDSN IP address).

S Simple IP

– An access method allowing a Simple IP mobile subscriber to accessthe Internet or an Intranet through its connection to the PDSN.

– The PDSN (or AAA) assigns a temporary IP address to the mobile.

– When the call is finished the PDSN releases the IP address. If themobile moves out of the PDSN serving area, the IP address isreleased and the mobile can no longer receive packets sent to thataddress. The mobile must set up a session with the new PDSN.

– The user profile provided by the AAA can contain information forthe PDSN to either grant access to the IP network or set up a tunnelto an ISP or a Private network. L2TP access to the intranet issupported.

S Proxy Mobile IP

– An access method allowing a Simple IP mobile subscriber to accessthe Internet or an Intranet through its connection to the PDSN, butthe PDSN also registers the mobile with the local HA in order toprovide Mobile IP type services.

8

Home Agent (HA)


Overview

Introduction

This section describes the HA portion of the PDN.

Overview of HA

An HA (Home Agent) provides Mobile IP Internet/Intranet accessservices for users belonging to the network. An HA can be located indifferent types of networks: home ISP networks, private networks,CDMA2000 1X packet data networks (which are visited or homenetworks depending upon the point of view of the mobile accessing thesystem). When a mobile is roaming and accesses a CDMA2000 packetdata network, the PDSN/FA (Foreign Agent) contacts the mobile’s HAwhich may be located in any of these different types of networks.

Functions

Overview

An HA performs the following major functions:

S Interface to the PDSN for Mobile IP registration actions and per–calltunnel creation

S Forwarding of Mobile IP call packets from the home network to thePDSN

S Forwarding of Mobile IP call packets from the PDSN to the homenetwork (reverse tunneling)

Registration

Mobiles on foreign networks or a new PDSN need to register with theirHA to convey their location. This location is called a ”care–of address”.The HA creates a mobility binding table that tracks the association of ahome address with the current care–of address of the mobile.

Registration is the task of the mobile IP client/user located in the mobilefor Mobile IP. The mobile IP client/user notifies the HA of the Mobile’slocation by performing packet registrations. The mobile IP client/user isrequired by the IS–707A standard to perform a packet registration whenit detects a new SID/NID broadcast by the serving system. The mobileIP client/user is also required to perform a packet registration if thePacket Zone ID broadcast by the serving system is non zero and isdifferent than any packet zone id that is on the subscriber device’s list ofvisited packet zones. The IS–707A standard allows for the mobile tohave an internal packet zone list with multiple entries. For thisimplementation of the Packet Data feature, the mobile restricts itsinternal packet zone list to be of length equal to 1. This will effectivelyforce the mobile to register anytime it moves from one Packet Zone toanother.

8

Home Agent (HA) – continued


Care–of–Addresses

While away from home, the mobile will be associated with a care–ofaddress. This address will identify the mobile’s current, topological pointof attachment to the Internet and will be used to route packets to themobile while the user visits other locations. Either a PDSN/foreignagent’s address or an address obtained by the mobile for use while it ispresent on a particular network will be used as the care–of address. Theformer is called a foreign agent care–of address and the later aco–located care–of address.

After the mobile decides on its care–of option, it sends a registrationrequest to it’s HA. In this request it lists the options it would like for itsregistration. Tunneling to mobiles can be done via IP in IPencapsulation (RFC 2003) or generic route encapsulation, GRE (RFC1701). Cisco IOS has also implement tunnel ”soft state” as described inRFC 2003 to aid in path maximum transmittable unit (pMTU) discovery.Tunnel soft state allows the tunnel head to keep track of the tunnel pathMTU and return this value to senders of larger packets via internetcontrol message protocol (ICMP) type 4 responses. The registrationrequests and replies are required to have an authentication extension thatincludes a keyed MD5 hash of the registration packet as well as atimestamp to ensure the origination of the request and the time it wassent, to prevent replay attacks.

When the home agent receives a registration request, it determines,whether the authentication hash is valid, if the timestamp is within anacceptable range, and if it can honor the request in terms of resources aswell as options. It then sends a reply to the mobile. When the mobileand the HA agree upon a set of service options then a mobility binding isput into the HA’s binding table and used to associate the mobile’s homeaddress with the care–of address. This binding will allow the mobile toreceive tunneled datagrams destined for its home address when it is notphysically connected to that network. Since the HA is attached to thehome LAN of the mobile it will merely accept and forward trafficdestined for the registered mobile.

When this binding is first added to the table, the HA sends a gratuitousARP (Address Resolution Protocol) on the mobile’s home LAN so thatall directly connected devices can continue to communicate with themobile through the HA. While the mobile is registered with the homeagent, the home agent will proxy ARP for the home address of themobile and tunnel packets to it using the care of address in its mobilitybinding. When the mobile moves its point of attachment to the Internet,it will notify the home agent and indicate its new care–of IP address.This change in location is only known to the HA and all other devicescan continue to communicate with the mobile transparently. When amobile returns to its home network it will send a gratuitous ARPresponses in order to indicate its return and allow devices to send packetsdirectly to the mobile on its home subnet.

8



Packet Zone Overview and Relationship with HA

The Packet Control Function (PCF) is responsible for storing anddelivering packets to mobiles. PCF is the entity where the MAC state ofthe mobile is maintained. Anchored PCF is a feature that allows a PCFto be assigned and used over multiple BSS coverage area. An R–Pinterface (a.k.a., A10/A11 interface) tunnel exists for every active anddormant mobile between a PCF and a PDSN. If the mobile leaves a PCFserving area this tunnel must be moved. Otherwise, the PDSN will senddata to the wrong PCF. This could result in data loss.

The coverage area of the PCF determines a Packet Zone. A Packet Zonecan be defined as the area in which the system is able to reconnect adormant mobile to the same PCF that it was using before it wentdormant. When a PCF can be reached across multiple CBSC coverageareas, it becomes possible to extend the Packet Zone to include morethan one CBSC coverage area.

In packet data service, dormant mobiles are expected to register whenthey notice a change in the Packet Zone ID, which is broadcast fromeach sector. This procedure is necessary to update any IP tunnels withinthe network so that data destined to a dormant mobile can be delivered tothe current serving system. The Larger the Packet Zone areas, lessfrequent are the registrations and data loss.

When a PCF can be reached across multiple CBSC coverage area, itbecomes possible to extend the Paging Zone to include more than oneCBSC coverage area. The PCF first assigned to a mobile is anchored forthe session and the mobile can be served by the same PCF as long itremains within the same Packet Zone. In the Motorola CDMAarchitecture for release 16, a group of CBSCs communicate with eachother and when a dormant mobile becomes active a query is madeamong the CBSCs to figure out if a PCF is already established to servethis mobile. Each time a dormant mobile originates a call, the CBSCreceiving the call will first check its database to see if an anchor PCFexists for the mobile within in its own pool of PCFs. If not, it will querythe other CBSCs within the Packet Zone to see if an anchor PCF existsfor that mobile. If so, a connection from the serving SDU SEL to theanchor PCF will be established. Include 6–8 CBSCs in a Packet Zone tostrike a balance between Packet Zone size and the cost of multicastqueries to multiple CBSCs.

Reverse tunneling

The HA also accepts data from the PDSN for routing to the homenetwork (reverse tunneling support).

8



Inter–PDSN mobility

The HA supports inter–PDSN mobility. Inter–PDSN mobility isimportant because it allows the user application to not be affected byroaming to a new PDSN. If the mobile session hands off to a new PDSN(the PPP session between the mobile and PDSN is re–negotiated), andthe mobile has Mobile IP service, the HA maintains the mobile station’sIP address and its communication with any Internet/Intranetcorrespondent nodes. If the mobile only has Simple IP services, thePDSN may assign it a new IP address and may break any applicationlevel connections.

8

AAA Server


Introduction

Overview of AAA Concepts

The role played by an AAA Server in a data network is to authenticate,authorize, and perform accounting for an incoming client that wants touse network resources for data activities. A short definition of each ofthe three terms is provided below:

S Authentication – The act of proving a claimed identity through theverification of some pre–determined credentials.

S Authorization – The act of determining whether access to certainnetwork resources can be granted to a mobile client.

S Accounting – The act of collecting information on resource usage forthe purpose of billing, auditing, cost allocation or trend analysis.

Overview of AAA Functionality

The AAA server is a complete implementation of the widely–used IETFstandards–track RADIUS (Remote Authentication Dial–In User Service)protocols, and is a full–function AAA (authentication, authorization,accounting) server.

Mobile clients obtain data services by negotiating a point of attachmentto a ”home domain.” Mobile clients can migrate from their home domainto foreign domains, and still gain access to resources needed for dataactivities. The typical scenario is described in the following steps:

S Mobile client attempts to gain access to network resources providedby the local domain.

S The PDSN, acting as the Network Access Server (NAS) in thedomain, initiates the authorization process to determine whetheraccess can be granted to the mobile client.

S The mobile client is asked to provide credentials for authentication bythe home domain.

S The home domain grants access to the mobile client, specifying thetype of services to which the user is entitled.

S The NAS generates accounting information on resource usage forbilling purposes.

8

AAA Server – continued


CDMA2000 1X AAA Implementation

A mobile client’s ability to gain services from the home domain, as wellas while moving between domains, requires that the system supportAAA services.

The AAA Server provides these capabilities in the MotorolaCDMA2000 1X CDMA Packet Data Network.

The AAA Server is an enhanced version of the RADIUS Server forremote network access control. The AAA Server is able to supportroaming for mobiles served by other AAAs and to collect additionalbilling data and statistics.

The CDMA2000 1X AAA Server will not play a role in providingmobility to the end user as in IS–95B systems. The only mobility agentsin CDMA2000 1X systems are the PDSN and the HA.

Functions

The AAA Server provides Authentication, Authorization andAccounting services specified for CDMA2000 1X networks. The AAAServer incorporates the necessary functionality needed to interact withPacket Data Network elements and with AAA Servers from othernetworks. It can also specify the quality of service the mobile is entitledto in an effort to provide transparency across multiple wireless networks.

The AAA Server is part of the access service provider network.

The main functionality provided by the AAA Server is the Visited AAAfunctionality.

It can also offer Home AAA services to mobiles whose home IP networkis the same as the home access provider network. (I.E., The home accessservice provider is also an Internet service provider.)

Optionally, the AAA Server may provide Broker AAA functionality toother domains.

For billing purposes, the AAA Server delivers accounting data to theoperator’s Billing Mediation Device.

8

AAA Server – continued


Inputs and Outputs

The AAA server supports RADIUS attribute formats as defined in RFC2138 and RFC 2139. Parameters transmitted across the R–P interfacefollow the RADIUS format.

Attributes of type ”26” defined in RFC 2138 and RFC 2139 are vendorspecific, and are used to transport CDMA radio specific parameters:

S Airlink Record Identifier (26/xf0)

S Release Indicator (26/xf1)

S Mobile Originate/Mobile Terminated Indicator (26/xf2)

The PDSN sends RADIUS UDR data to the AAA Server.

All of the RADIUS accounting attributes that the AAA server receivesfrom the PDSN, are reformatted and logged to a comma–delimited file.A file of this format is easily imported into spreadsheets and databaseprograms for report generation and billing.

Signal Flow

If the mobile station uses CHAP/PAP, the AAA server will receive aRADIUS Access Request from the PDSN with CHAP/PAPauthentication information, and shall forward the RADIUS AccessRequest to the home network if it does not have the authority toaccept/deny the request.

The AAA server will later receive a RADIUS Access Accept messagefrom home network. The AAA server shall then send the RADIUSAccess Accept to the PDSN.

Later on, the RADIUS server will receive a RADIUS AccountingStart/Stop from the RAN via the PDSN. If the AAA server is in theserving network, the Foreign AAA server shall forward the RADIUSaccounting messages to the Home AAA server.

8


Chapter 9: Operations and Maintenance (O&M)

Table of Contents

Operations and Maintenance (O&M) 9-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 9-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC–R Overview 9-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UNO Overview 9-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC–IP Overview 9-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Platform for all O&M Products – Sun Netra 440 9-7 . . . . . . . . . OMC–R 9-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UNO 9-12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC–IP 9-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9



Notes

9

Operations and Maintenance (O&M)


Overview

This chapter provides the following:

S An overview of Operations and Maintenance (O&M) functionality

S An overview of the Universal Network Operations (UNO), Operationsand Maintenance Center – Radio (OMC–R), and Operations andMaintenance Center – Internet Protocol (OMC–IP) managementplatforms

S Introduction to SMAP

S Introduction to the SMNE concept

Description

The OMC solution for the CDMA2000 1X network is an integration ofthese OMC building blocks, each of which was designed and developedto serve the specific needs of the elements of its domain.

S OMC–R

S UNO

S OMC–IP

S SMAP

S SMNE (Introduced in G16.1)

S Hardware Platform for all O&M Products

9

Operations and Maintenance (O&M) – continued


Figure 9-1: OAMP Connections/Relationships 2.17.0.x.

9



OMC–R Overview

Overview

Like UNO, OMC–R plays a number of key roles in the CDMA 1Xarchitecture. The following are the new roles assigned to the OMC–R inthe 1X architecture:

S Coordinate configuration of the radio/IP network intersection

S Collect alarm and event information by connecting to the CiscoWanManager applications and the Cisco elements

Some may view these OMC–R activities as an elevation to a partialnetwork management role. But seen within the context of the AN’s roleas an extended element of the Radio Access Network (RAN), the newfunctionality is consistent with OMC–R’s charter as an ElementManagement System (EMS).

OMC–R Coordination Role

The OMC–R was selected for the coordination role based on itsproximity to the elements supported, its ownership of the data modelthat defines the RAN network, and the capabilities the platform alreadypossessed from its support of 2G networks.

The OMC–R coordination function is critical because each newIP–based RAN deployment or re–deployment involves configuration onboth the Motorola radio side and on the Cisco IP side. The OMC–R’sspecially designed management tools greatly simplify these deploymentactivities, insulating the operators as much as possible from the specificsof the configuration needed to make the IP RAN elements communicateand operate together.

OMC–R Connection and Collection Role

OMC–R ability to connect to the Cisco WanManager applications andCisco elements to collect alarm and event information is a secondary butno less important role. By having this information flow throughOMC–R for eventual display on the UNO or other network managementsolutions, OMC–R is able to apply the contextual knowledge it hasabout the AN devices to the messages sent to the higher level managers.Consequently, the total management solution can both tell operatorswhich AN routers or switches have failed and identify what the impactwill be on the radio components of the solution.

9



UNO Overview

Description

UNO provides integrated and consolidated monitoring of 1X IP–RAN,2G RAN, and other network elements.

For the CDMA 1X solution, the UNO product satisfies two key roleswithin the element and network management space. First and foremost,by providing alarm, state, and performance functionality that is anextension of the capabilities of OMC–R, UNO continues to complete theelement management picture for the CDMA RAN. Secondly, byproviding some integrated support for equipment introduced withCDMA 1X, UNO allows Motorola to offer better end–to–endmanagement of the IP–based CDMA solution.

For the components of the AN, UNO provides the operator with aworkable solution for consolidated fault management of these newdevices as well as for the circuit–based architecture devices traditionallyassociated with the Motorola CDMA RAN solution. The UNO solutionincludes the capability to sort, filter, store, analyze, track, notify–on, etc.alarms generated by the AN in the same format and to the same capacityas alarms generated by the other elements of the RAN.

The northbound interface from UNO’s alarm manager provides a singleconnection point for other third–party network management systems(NMS), and this data stream can be configured to take advantage ofUNO’s value–add alarm functionality, which includes user–definedalarms and performance thresholding.

Logical and physical representation of the AN devices in the UNOCommand Center also provides the operator with a visual reference forthe relationship between the devices of the IP–RAN and the AN. Withthese displays and the context provided via communication withOMC–R, operators are able to “see” the impact that any failure of an ANdevice will have on the IP–RAN devices it supports. Without thiscontext, an individual router or IP switch just becomes one of many,with a less obvious scope of impact.

The UNO solution also gives the operator the ability to access theindividual element management systems and applications (provided byCisco) from a single operator station and keyboard or to split the FaultManagement and Performance Management function onto individualstations supporting task based operations.

OMC–IP is only integrated at the operator terminal level;there is no integration of applications or operations data ofOMC–IP.

NOTE

9



OMC–IP Overview

Overview

OMC–IP provides element management capabilities for the Ciscocomponents of the RAN, playing an important enabling role in the datacomponent of the 1X solution. Device Manager Kit (DMK), CiscoWanManager (CWM) and Mobile Wireless Center (MWC) are the maincomponents of OMC–IP. These products provide device–level supportand the fundamentals for domain–level management of the IP aspect ofthe network.

Device Manager Kit (DMK)

Device Manager Kit is the major element management component of thearchitecture. It provides element management functionality for suchIOS–based devices as the Catalyst switches, and the route processormodules (RPM). This suite of applications will provide the following:

S A chassis view of the equipment

S Image and configuration management

S Numerous tools and aids for the operator managing the IP domain ofthe RAN

Cisco WanManager (CWM)

Cisco Wan Manager (CWM), as part of release 2.17.0.x, introduces anew GUI user interface and new software applications.

The Cisco WAN Manager manages the Layer 2 switch infrastructure ofthe MGX 8850, a component of the AN. CWM is a series of applicationsthat provide comprehensive configuration, connection, fault,performance, and security management through GUIs and flow–throughinterfaces that deal with the specifics of the MGX.

By presenting the operator with a standardized interface to OMC–R andby mediating between the MGX device and OMC–R, CWM is also partof the integrated fault management solution in the CDMA 1X network.

Operators can access the CWM applications either through a connectionfrom an UNO management platform or, more directly, through a terminalconnected to the CWM supporting Sun Microsystems server.

Mobile Wireless Center (MWC)

The Mobile Wireless Center (MWC) provides a single point–of–entry tomanage all the mobile wireless functionality. MWC providesconfiguration management for the BTS Routers, RPM and MGX in awireless provider network. The MWC alleviates the need for the provideror a system integrator to create specific interfaces and functions formanaging multiple Cisco EMSs that configure and monitor numerouspieces of Cisco devices. It provides an abstraction layer on top of theCisco EMSs from configuration management aspects. It also allowsrapid development of OSS for managing the complete wireless networkby providing the flow through management capabilities (publishedAPIs).

9



The MWC–FM, now part of MWC (used to be part of CW4MW), is avalue added feature for the CDMA environment. The MWC–FMcorrelates, filters, and determines root cause in relation to the Layer 3Transport portion of the IP RAN equipment through the BTS Routers.Its feature sets have been specialized to support the IP enabled CDMAenvironment and assists in the integration and persistence of events withrespect to OMC and UNO management environment.

SMNE (Self–Managed Network Elements)

SMNE is a new O&M maintenance paradigm for Motorola GTSSinfrastructure. SMNE will change the O&M from a central/ hierarchicalto a distributed model. In the past most actions were controlled from acentral location. An event was reported up to a controller, which decidedwhat action to take and sent the information back to the element foraction.

In the distributed model, each element has enough knowledge to take itsown action and the event and results are reported up for record keepingand not of analysis and action. The distributed model will place theresponsibility for managing an element as part or the development of theelement and not as a separate and dependant activity. Allcommunication between an element and its manager is in the form of adefined file structure with the common types being:

S Network Element Configuration File Overview

S Bulk Configuration Change Request File

S Auto–provisioning File

S Key Statistical Interval File

S Alarm Summary File

S Object Status Summary File

S Global Event Log File

S Diagnostics Results File

S Calibration Data File

S Software Load Information File

S Entity Type Definition File

S Available Key Statistics List File

S Streaming Data Format

By using this standard method of element to manager communications,development of O&M becomes much less tied to development ofelements. Currently (release 2.17.0.x) the SDU, VPU, MM ll and theGLI3 cards have the SMNE feature. This will be extended to otherelements in future releases. SMNE is a software and design architecturethat is designed to be platform independent and no new hardware isinvolved in the SMNE implementation.

9



SMAP

SMAP is a workstation based interactive program, designed to gatherand process radio frequency (RF) data from different components of theCDMA system through its connection to the Operations & MaintenanceCenter–Radio (OMC–R) subsystem. SMAP users include fieldengineers responsible for pre–commercial CDMA system optimization,and cellular engineers responsible for commercial CDMA systemoptimization. SMAP is a key element of Motorola’s SystemOptimization solution. The Optimization solution is part of Motorola’stotal O&M offering. Customers use our Network Operations, Planningand Optimization Products, such as SMAP, UNO, OMC–R, OMC–IPand NetPlanE

Hardware Platform for all O&MProducts – Sun Netra 440

The Sun Netra 440 platform will be provided for new O&Mdeployments in release 2.17.0.x. (Older hardware platforms will continueto be supported, per the configuration/ordering guides). The commonNetra 440 platform allows for easy re–use among the O&M platforms asoperators will be able to easily re–deploy Netra 440 hardware as requiredin their markets.

The Netra 440 platform is Sun’s latest telco platform and provides thesame benefits as the Netra 20 along with the added capability ofredundant power supplies and the ability to use up to 4 CPUs :

S Overall O&M product cost reduction over current offering forcomplete O&M solution (OMC–R, UNO, OMC–IP, SMAP).

S Reduces overall solution footprint through racking in a single OMCcabinet.

S Enables common installation deployment tasks.

S Lowers cost of ownership through common spare parts.

S Provides consistent environmental and power specifications.

OMC Hardware Cabinet

The OMC cabinet will be capable of mounting up to (6) Netra 440servers and (2) Sun 3310 Disk Arrays. The cabinet includes all internalcabling, master power breaker panel (MBP), and front/rear doors. Theoperator may choose to mount the Netra 440s and Disk Arrays in othercabinets or even on desktops, but the optional OMC cabinet provides asimple, efficient method of mounting all O&M equipment in a singlerack. The single rack reduces floor space while providing consistentenvironmental and power specifications for all the O&M platforms.

9



Figure 9-2: Netra Cabinet – OMC Cabinet Layout

9



OMC–R

Description

The OMC–R is a highly available, UNIX–based O&M platform thatsupports the core components of the CDMA RAN, including the CentralBase Site Controller (CBSC), the Base Transceiver Stations (BTS), andIP components for circuit and packet networks. This Element Manager(EM) platform interfaces directly to the elements via Ethernet and actsprimarily as a data collection and mediation device for alarms, events,statistics, and configuration.

The OMC–R consists of either a Sun Microsystems E4500 Enterpriseserver, D1000 Disk Array, and other third party equipment integratedinto a NEBS Level 3 seismic–compliant cabinet, a Sun Netra 20 serverand 3310 Disk Array, or a Sun Netra 440 and 3310 Disk Array. Anoptional OMC cabinet is also available that is capable of mounting (6)Netra 440 servers and (2) Disk Arrays. The Netra 440 and Disk Arraycan be mounted in other racks if desired, offering the operator maximumflexibility in configuring the O&M products. The OMC–R providesO&M functions for both IS95A/B and CDMA2000 1X networktopologies. Together OMC–R, OMC–IP, UNO, and SMAP platformsprovide total O&M functions for both the traditional radio network andthe new IP network.

A substantial quantity of enhanced PM data pegs will be available inrelease 2.17.0.x which will be derived from CDL data. CDLs will nowbe reported in a variable length format, providing for increasedprocessing efficiency as well as additional call data including all handoffinformation. (Fixed length CDLs will continue to be reported by theMM and circuit data elements. Refer to the 2.17.0.x releasedocumentation for more information on the enhanced PM pegs and thevariable length CDL format.) There are no hardware impacts to theOMC–R due to the new PM data pegs. The new PM Server will be usedto perform post–processing of the CDL records to derive the PM pegs.

Function

The OMC–R provides the following primary functions:

S Event/Alarm Management – OMC–R collects and logs alarm andevent information from the RAN and AN devices, making thisinformation available through ASCII and Common ManagementInformation Protocol (CMIP) interfaces. The data can be viewed usingtabular or graphical reports on OMC–R and/or UNO.

S Performance Management – OMC–R provides a temporary store ofperformance management (PM) and Call Detail Log (CDL) data thatcan be uploaded to external platforms, such as Motorola’s UNO, forlonger–term storage and analysis. The OMC–R can gather otherCBSC performance–related information such as CPU utilization, diskusage, and processor status, creating another avenue for systemanalysis. This data can also be viewed using tabular or graphicalreports on OMC–R and/or UNO.

9



S Security Management – By allowing each operator to be assigned auser ID and password, OMC–R helps control access to the operationsand maintenance functions. OMC–R’s security management alsoprovides special features for the management of dial–up lines, and forthe management of terminals connected to OMC–R using onlyon–premises cabling. All CLI commands are validated and executedconcurrently for different users. The security settings can be changedinstantaneously and the mechanism is scalable to achieve any level ofgranularity (i.e., on a per–user, per–group, or per–command basis, asneeded).

S Configuration Management – In the 1X network, OMC–R has acritical new function: to coordinate configuration management of theRadio/IP network intersection. That is because each new IP–basedRAN deployment or re–deployment involves configuration on boththe Motorola radio side and on the Cisco IP side. The OMC–R’sspecially designed management tools greatly simplify thesedeployment activities, insulating the operators as much as possiblefrom the specifics of the configuration needed to make the IP RANelements communicate and operate together.

S Fault Management – This function provides the capability to queryand change device states of elements under OMC–R’s control. Itcontrols RF diagnostics by enabling the execution of loopback andforward/reverse power tests, allowing operators to selectively test thecall–processing capability of the RAN. Because the fault managementfunction is integrated with UNO’s scheduling capabilities, operatorscan create automated verification of network operation.

Inputs and Outputs

Standard Ethernet connections are provided for LAN access to OMC–R.Each Mobility Manager (MM) connection is provided on separate,isolated primary and redundant Ethernet LANs.

A separate LAN is provided for the UNO connection, and a fourth LANis provided for a customer–specific LAN. Communication withOMC–R is provided via CMIP and ASCII output streams. The OMC–Ralso supports Motorola’s Super Cell Application Protocol (SCAP) andSNMP messaging protocols.

Refer to the RAN Hardware Installation manual for details on physicalinterfaces for the different types of hardware used for the OMC–R.

Signal Flow

See Inputs and Outputs.

9



Redundancy

OMC–R availability does not affect call–processing capability. Howeverthe redundancy described in this section is built into the system tomaximize OMC–R availability and data integrity and thus preserve thecritical data collected by OMC–R.

The OMC–R architecture uses the following:

S Two (2) CPU modules, each with its own cache memory

S Two (2) memory modules

S Mirrored disks

S Dual paths for I/O

S Dual power paths

S Redundant DC power supplies (E4500 and Netra 440)

In addition, the operating system supports mirrored disks that writeidentical information to two disk drives simultaneously. Mirroringpreserves data integrity and provides continuous data access despite thefailure of an I/O path, a disk, or a disk controller.

O&M

While OMC–R provides O&M functions for the elements under itscontrol, it uses the Sun Validation Test Suite (VTS) software to performdiagnostics on any subsystem within either the E4500 or Netraplatforms.

9



UNO

Description

UNO is designed to provide the centralized point from which operatorshave access to the data and interfaces needed for network administration. UNO’s user interfaces are standards–based Graphical User Interfaces(GUIs) built upon the latest technologies, including web–supporting Javaapplications. For the specialized interfaces of the Element ManagementSystems (EMS) needed for the different components of the mobilenetwork, UNO executes its “Don’t Get Up” philosophy by providingintegrated access to these interfaces.

UNO currently provides integrated support for CDMA OMC–R,OMC–IP, CBSC, and BTS for:

S cdmaOne, IS2000 1X, and CDMA2000 1X Radio Access Networks

S Access Node(AN)

S Motorola’s EMX 2500 and 5000 Mobile Switching Stations (MSC)

S Circuit and packet Inter–Working Units (IWUs)

S Motorola’s MOSCAD environmental monitoring system

S Radio Frequency Diagnostics Subsystem (RFDS)

S Packet Data Service Node (PDSN)

The roadmap for the UNO platform/software has several key goals:

S Integrated management of diverse network elements utilizing standardinterfaces such as CMIP and SNMP

S Consolidation of operations to a single operator’s station

S Support for the “Don’t get up” philosophy of operator stationintegration

S Provider of open access to network wide configuration, performance,alarm, event, and call data with integrity and in a timely manner

S Support of end–to–end Network Operations, Planning, andOptimization activities through integration with external analysisapplications such as Motorola’s NetPlan and SMAP

S Provider of advanced analysis applications that simplify operationaltasks and automatically identify and remedy network problems beforethey impact system availability and performance

9



What New in Release 2.17.0.x?

This section provides an overview of changes that were introducedduring the UNO 2.17.0.x release. Please refer to UNO productdocumentation for further details.

General ChangesS Support was added for the optional Variable Length CDL (vCDL)

feature.

S Support was added for the optional Performance ManagementExpansion via CDL Data feature.

S Support was added for the optional Performance ManagementExpansion – CDL Post Processing feature.

Functionality

System Engineering Performance Management UtilitiesEnhancements include:

S AN Dashboard Enhancements including integration of thesemeasurements into PM on UNO.

S Enhanced downtime reporting

S Functional robustness reporting parity with GSM and iDEN.

S Capacity charts

S Integration of Key Capacity Indicator (KCI) reports

S Added reports for the new R–EACH air interface signaling channels

Function

UNO focuses on these management areas: device status, alarm andperformance management. The UNO Alarm Manager presents theoperator with a customizable interface that displays alarm and eventinformation from all supported elements in a consistent and highlyreadable format. From this interface, operators can sort, filter, define,search, acknowledge, and clear the alarms received. With integration totrouble ticketing and automated user notification systems, operators canleave the constant monitoring of the system to UNO, only payingattention to events defined by the operator to be critical to operations.

For state and status management, UNO offers Command Center, ageographical, logical, and hierarchical display that provides the operatorwith a clear view of current device status within the network. Throughapplication integration, the operator can also quickly gather performanceand alarm information on the devices displayed in the Command Center,allowing him or her to quickly assess and address network problems.

In the performance management functional area, UNO providesshort–term and long–term storage of performance and CDL data.Operators are able to access this relational database stored informationeither through UNO’s own report generation tools or via an interface forprocessing in off–line analysis systems. UNO’s User DefinedMeasurements suite of applications allows operators to define their owncounters and to establish thresholds that automatically alert their staffwhen the system is operating outside of expected parameters.

9



Additional UNO applications support operators in tasks as diverse asaccess to on–line system documentation, loop–back test scheduling andanalysis, element software distribution, Call Final Class (CFC) analysis,load analysis for element processors.

Inputs and Outputs

The Motorola Universal Network Operations (UNO) system is an opennetwork management system whose framework is based on theTelecommunications Management Network (TMN) series ofinternational standards (ITU Recommendation M.3100).Communication to the network’s element managers (EMs) and elementsis accomplished through agent software utilizing CMIP (CommonManagement Interface Protocol, ITU X.711), SNMP (Simple NetworkManagement Protocol) and/or other standard methods ofcommunication; e.g., FTP (file transfer protocol) for bulk–data transfers.Applications implement the functionality specified by the systemmanagement areas defined by the ITU in the X.730/740 series ofstandards for configuration management, fault management, securitymanagement, and performance management.

Card Description

UNO is built upon industry–standard hardware available from SunMicrosystems and various third–party software solutions.

Signal Flow

(Not applicable)

Redundancy

UNO does not have redundancy requirements. However, you do havethe option of inserting a local element management layer at the OMC–Rin addition to the UNO Market Manager. This can be done with a MM atthe highest level working with either another MM or an EM at the locallevel.

O&M

In the area of O&M, UNO is at the top of the flow chart. All O&M ofthe elements within the RAN, start with UNO. Therefore, UNO doesnot have O&M requirements.

9



Figure 9-3: Operations and Maintenance Hierarchy

BTSRouters

BTSRouters

BTSRouters

BTSRouters

BTSRouters

BTSRouters

ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ

ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ

RPM1RPM ..

ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ

CAT 1CAT ..

CAT 24

MGX 1MGX ..

MGX 24

LAN/WAN 1

LAN/WAN ..

LAN/WAN12(3662)

PBTS 1

PBTS ..

pBTS 575

OMCR 1OMCR ..

OMCR 12

CWM 1CWM 2

CW4MW 1

CW4MW 2

UNO(Distributed Alarm Manager)

UNO 1UNO 2

UNO 3

pCBSC 1pCBSC ..

pCBSC 52

OMC–IP

RPM 148

OMC–R

UNO

PDSNMWC

AAA

9



OMC–IP

Description

The Operations and Maintenance Center – IP or OMC – IP, is a vitalcomponent to the CDMA Network Operations, Planning, andOptimization solution for the CDMA IS2000–1X deployment. In thisdeployment, the OMC–IP is a logical suite of functionality that consistsof an integrated solution of Sun Microsystems server platforms, Ciscoelement managers, Motorola software and other third party applications.The primary function of this OMC–IP is to provide ElementManagement capabilities for the Cisco technology domains, includingLayer 2 switching and Layer 3 Internet Protocol (IP) enablingcomponents of the IS2000 1X IP RAN.

The Cisco element management systems are mature commercialproducts with added mobile wireless features. The primary componentsof the solution are Cisco System’s Cisco WanManager (CWM), DeviceManager Kit (DMK) and Mobile Wireless Center (MWC). These piecesof software provide the customer with the element management controlneeded to configure, manage and troubleshoot the Cisco networkelements that make management simple and mobile IP a possibility.These software components also provide integration with Motorola’sRadio Access Network (RAN) management solutions (OMC–R andUNO), needed to make the management of this new architecture aneasier task for the cellular operator.

Function

Cisco Wan Manager (CWM), as part of release 2.17.0.x, introduces anew GUI user interface and new software applications.

The Cisco WanManager manages the Layer 2 switch infrastructure of theMGX 8850. The Cisco WanManager (CWM) is an element managementsystem with WAN network visibility that enables operations,maintenance, and management of multi–service WAN networks. CWMprovides comprehensive configuration, connection, fault, performance,and security management through GUIs and flow–through interfaces.

Cisco WanManager is an SNMP–based, multi–protocol managementsoftware package designed specifically for wide–area multi–servicenetworks. It provides integrated service management and processautomation to simplify the management of even the most complexnetworks. The Cisco WanManager allows you to easily monitor usage,provision connections, detect faults, configure devices, and tracknetwork statistics.

Based on a robust, scalable architecture, Cisco WanManager not onlymeets today’s business requirements for control and operation, but alsointegrates with other Cisco network management products to provideend–to–end service management of wide–area multi–service networks.

9



The Device Manager Kit is a commercial product with applications thatprovide FCAPS. The element management application bundle has beendeveloped to support each IP enabled Cisco elements. This product suitehas been enhanced for the CDMA functionality.

The Device Manager Kit features a set of Web–based management toolsfor configuring, administering, monitoring, and troubleshooting theIPbased wireless network. The Device Manager Kit providesmanagement for the Catalyst Router, the RPM and the BTS Routers.

The Device Manager Kit solution consists of operationally focused toolsuseful in managing the day–to–day operations of critical services andlinks found in an enterprise campus network. These tools includescalable topology views, sophisticated configuration, Layer 2 / Layer 3path analysis, traffic monitoring, end–station tracking, and devicetroubleshooting.

The Mobile Wireless Center (MWC) provides a single point–of–entry tomanage all the mobile wireless functionality. MWC–CM providesconfiguration management for the BTS Routers, RPM and MGX in awireless provider network. The MWC–CM alleviates the need for theprovider or a system integrator to create specific interfaces and functionsfor managing multiple Cisco EMSs that configure and monitornumerous pieces of Cisco devices. It provides an abstraction layer on topof the Cisco EMSs from configuration management aspects. It alsoallows rapid development of OSS for managing the complete wirelessnetwork by providing the flow through management capabilities(published APIs).

The MWC–FM, now part of MWC (used to be part of CW4MW), is avalue added feature for the CDMA environment. The MWC–FMcorrelates, filters, and determines root cause in relation to the Layer 3Transport portion of the IP RAN equipment through the BTS Routers.Its feature sets has been specialized to support the IP enabled CDMAenvironment and assists in the integration and persistence of events withrespect to OMC and UNO management environment.

9



Inputs and Outputs

The OMC–IP, and the software that executes on these servers, primarilyact as interfaces for the human operator to the network elements theysupport. The I/O on one side (that facing the operator) is a collection ofgraphical/text interfaces, and standard open interfaces to other managers.The I/O on the other side (facing the supported elements) is a set ofinterfaces, both standardized and proprietary.

Card (Platform) Description

The platform for each application of the OMC–IP is a Sun MicrosystemsUNIX server. Platform requirements vary based on usage and type(s) ofOMC–IP applications installed.

Signal Flow

The integrated O&M architecture of the 1X network involvescommunication between Cisco element managers running on theOMC–IP and the UNO and OMC–R management platforms of the radiocomponents. Through these connections it is possible to integrate all ofthe alarms collected by these platforms.

Redundancy

All versions of the OMC–IP platform are deployed with mirrored diskstorage to provide integrity for all data deposited and collected on thesystems.

Since loss of a Cisco WanManager (CWM), Device Manager Kit (DMK)and Mobile Wireless Center (MWC) platforms will in no way impact theoperations of the AN elements it supports, complete redundancy is notrequired.

O&M

By utilizing the Sun Management Center, the customers will be able tomonitor the OMC–IP platform.

9


Chapter 10: Vocoding Processing Unit (VPU)

Table of Contents

Vocoding Processing Unit (VPU) 10-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 10-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Function 10-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inputs and Outputs 10-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Card Description 10-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signal Flow 10-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redundancy 10-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O&M 10-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VPU DCS Description 10-12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of VPU Timing Options 10-14 . . . . . . . . . . . . . . . . . . . . . . . . . . .

10



Notes

10

Vocoding Processing Unit (VPU)


Overview

The Vocoder Processing Unit (VPU) is the portion of the IP–BSCproduct offering that performs Transcoding functions. The VPU hasmany advantages:

S High Capacity (2500 Erlangs per VPU shelf)

S Client Server model

S High speed Optical interface to MSC

S Network level redundancy

S Greatly reduced foot print for functionality

S Increased network design flexibility

S Shares some common hardware with SDU to reduce spares expense

S The VPU uses a common platform with significant architecturaladvantages that adds additional value in the continuing productevolution. Figure 10-1 shows the VPU implementation in release 16.5.Figure 10-2 shows the IP–BSC implementation in an all IP network.

10

Vocoding Processing Unit (VPU) – continued


Figure 10-1: VPU Implementation (Circuit)

10



Figure 10-2: VPU Implementation (IP–BSC)

10



Function

Functions

The VPU has multiple functions but its name gives its most importantfunction of vocoder processing. PCM to any selected CDMA vocoding(8K EVRC, 8K CELP, 13K QCELP) format can be accomplished. TheVPU has full functional transparency to the existing Transcoder,including echo cancellation, but it uses a packet interface for compressedmobile traffic rather than circuit. A list of VPU functions is given below:

1. The conversion of vocoded frames to PCM for uplink frames (whichentails speech decoding).

2. The conversion of PCM to downlink vocoded frames prior todistribution by the SDU (which entails speech compression) inaddition to echo cancellation from the network side.

3. The support for CDMA 13 Kbps Qualcomm Code Excited LinearPredictive (QCELP) vocoder, the 8 Kbps Enhanced Variable RateCoder (EVRC) and the 8 Kbps Basic Variable Rate vocoder.

4. TTY/TDD encoding (forward link) and decoding (reverse link).

5. The termination of SONET/SDH OC–3 circuit PCM interfaces fromthe MSC/DCS.

6. The termination of IP over Gigabit Ethernet connection from theAccess Node (AN).

7. The support of DTMF tone generation in PCM format.

8. The support of circuit data calls when the circuit IWU is located atthe XC (packet to circuit interworking only, with no transcoding).

9. The support of circuit data calls when the circuit IWU is located atthe MSC.

Other Functional Details

There are numerous application considerations for the VPU:

S The VPU will only handle packet based traffic (BTS using packetbackhaul) if XCs are eliminated.

S An SDU must be implemented in a network employing a VPU.

S Networks using a VPU must be converted to IP based SHO i.e. meshelimination must have been implemented if XCs are eliminated.

S If a PUMA is being used as the MM, an XC is still required with theVPU to boot up the MM (and also to support IWU (CBSC based)and any circuit based BTS (SC3XX or others)).

S VPUs can be shared across IP–BSCs and MSCs for increasedavailability and resource utilization.

10



Inputs and Outputs

The physical I/O of the VPU is Ethernet (1000 Base T) towards the BSSand SONET or SDH towards the MSC. For MSCs that do not supportthe SONET/STM–1 interface, a DCS will be required to adapt physicalinterfaces and line rates.

Card Description

Chassis/Cards Overview

Refer to the MMII section for a description of the IP–BSCframe.

NOTE

The VPU frame will have the following features:

S House up to 2 Shelves(Note the shelves in a frame are totally separate units and have noconnectivity between them).

S 4 Power Supply Modules (PSMs) and Power Distribution Unit(PDU) at Top of Frame.

S Front–to–Back Air Cooling

S Front/Rear Access for Maintenance

Each shelf has 19 front slots and eleven in the rear of the shelf. Four ofthe front slots are occupied with 2 ISB/SPROCS and 2 CCAs leaving 15payload slots. All cards are Hot Swappable. The cards described hereinclude AIO, CCA, SPROC, BPP2, PSM, ISB, DGBEs, and DOC3s.

10



CCA

The CCA provides card presence detection as well as module EIDretrieval for the AIO and DGBE cards. Additionally, it provides inputsfor shelf level alarms (such as the fans and the PSMs) and control overshelf level LEDs. The CCA also provides termination of customerdefined alarms that can be terminated at the VPU shelf. Customerdefined alarms are made available to the OMC–R by the O&M functionsof the VPU. Alarm outputs can be defined for interface to site alarmscollection facilities through relay contacts provided on the AIO.Alternately, these relays may be used to control other site equipment.

SPROC

The SPROC coordinates all shelf O&M. It houses a Power PC750processor, network interfaces, MMI ports and local memory. Theprimary functions of this card are:

S Download, stores code and configuration data for entire VPU fromOMCR.

S Acts as download server for ISB, BPP2, and CCA, and DOC3.

S Fault Management (Fault monitoring and recovery, Alarm reporting toOMCR, and Redundancy State Management).

S PM Data collection and forwarding to OMCR.

The SPROC performs central call processing resource management andis implemented in a 2N Redundant configuration. The SPROC iscoupled with the ISB as a single Field Replaceable Unit.

ISB

The ISB (Interface Switch Board) is the master time based reference forthe VPU. It provides Layer 3 routing to the AN and provides the packetswitching function for the VPU. The Board Control Processor (BCP)supports local O&M operations including bootstrap, code and data load,alarm/event reporting, etc. The ISB is a common FRU also used in theCBTS Platform and SDU equipment, and carries the SPROC (literally).The ISB interfaces to the RAN, specifically to the AN, via GigabitEthernet links. It is implemented as 2N Redundant allowing for routefailover to be accomplished via OSPF routing protocols on the AN, ISB,and BPP2. Additionally, the SPROC is physically part of the same FRUas the ISB.

There are different software loads from the SDU and VPUand therefore the ISB is not a common spare.

NOTE

BPP 2

The BPP2 board is the general payload board of the VPU. The BoardControl Processor (BCP) on the BPP2 supports local O&M operationsincluding bootstrap, code and data load, alarm/event reporting, etc.

10



The BPP2 will provide the following:

S Vocoding, i.e, transcoding between PCM and CDMA encoded voice.

S Interworking of vocoded payload to UDP/IP/MAC.

S Bypass (for circuit data calls) of transcoding.

S A5 Interface function (for circuit data calls using a IWU at MSC) i.e.,ISLP framing.

S Interworking of circuit data payload to UDP/IP/MAC.

S Termination of circuit TDM interface from the DOC3.

Most of the BPP2 functionality is provided by the Vocoding ChannelProcessing elements, which are supported by the Board ControlProcessor (BCP) and an Ethernet switch. The BPP2 performs eitherVocoder Processing Functions (VPF) or vocoder bypass. The phrase“vocoder bypass” here simply means the bearer data stream traverses theBPP2 without being transcoded back to PCM format. The BPP2s allowfor implementing of a load sharing configuration for vocoding bydistributing calls among all the VPF BPP2 cards in the shelf.

PSM

The Power Supply Module provides cage level input power conversionfor distribution throughout a given VPU cage.

AIO

The AIO slot resides in the rear portion of the VPU shelf assembly andaccommodates one AIO board. The AIO board is the interface for thealarm I/O. The board interfaces with the CCAs through the backplane.An individual AIO board is capable of accepting 16 Customer alarminputs, and providing 8 Customer alarm outputs. Each CCA relays thealarms to the Platform Management O&M function which notifies theOMCR of the alarm condition. The AIO card will also be the input ifBITS (Building Integrated Timing Source) is used.

DGBE

The DGBE resides in the rear portion of the VPU shelf assembly. Theshelf accommodates two DGBE boards. Each DGBE board interfaces toa Gigabit Ethernet signal. The 1000BaseT Ethernet connections providedby the DGBE board are used to interface from the VPU to the AccessNode (AN). Gigabit interfaces are cabled to the top of the frame.

DOC3

The Dual Optical Carrier 3 Interface card (DOC–3) resides in the rearportion of the VPU shelf assembly and accommodates two DOC–3boards. The DOC3 converts (multiplexes/demultiplexes) betweenSONET Optical Channel 3 (*The corresponding (ITU–T) SDH versionof OC–3, i.e., STM–1, is also supported) signals at a rate of 155.520Mbps and DS0–level signals at a rate of 64 Kbps. In other words, itterminates channelized OC–3 from the DCS or MSC, and distributes(via fan–out) the PCM octets to designated BPP2 cards (forward link).The DOC–3 multiplexes reverse link octet streams from BPP2 cards intocommon OC–3/STM–1 streams back to the DCS or MSC.

10



Two DOC3 cards interface to the ISB, and are managed by the SPROC.The DOC3 provides the following functionality:

S Termination of two OC–3 SONET/ STM–1 SDH optical interfaces,each having an active and a standby optical fiber interface. EachOC–3/ STM–1 active interface supports 2016 channels of 64KbpsPCM (DS0).

S Supports OC–3/STS–1 pointer processing and STM–1/AU–4 pointerprocessing.

S Distribution of PCM stream via high speed circuit connection fabric toeach BPP2 (forward direction).

S Multiplexing of N payload slot PCM streams to a given OC–3SONET/ STM–1 SDH stream (reverse direction).

S Automatic Protection Switching (APS).

S O&M interface to SPROC via PMI for SONET/SDH APS alarm andfailure alarm indications, host processor code management, FaultManagement rules, and responses.

There will be one, plus one redundant DOC3 cards per VPU shelf, for atotal of 2. The DOC3 supports Dual OC3 SONET/ STM–1 SDHinterfaces to either a DCS or MSC and interconnects with all 15 BPP2sthrough the High Speed Circuit Interconnect Interface.

Signal Flow

Overview

This section describes the logical Control, Bearer, and O&M interfacessupported by the VPU.

10



Figure 10-3: VPU External Interfaces

MM SDU

VPU

SPROC BPP2

VPF

Vocoder

C8 C9RM8 B2

DOC3

SPF

ISB

L3 Routing

MSC/DCS

A2/A5

HCI

XC

B3

OMCR

O3

CP

Routing

CP2

RoutingO&MP

O&MRM/RA

Mux/

Dist

AN

CP9CP8CP7

B4C24 C23FM1

10



Call Processing Control Paths

Control interfaces are terminated at the following points in the CDMAVPU architecture:1. Vocoder Call Control (C8) – This is a signalling and control

interface between the MM call processing and the RM/RA (ResourceManagement/Resource Allocation) function of the VPU. It isproprietary and used to establish and maintain services such as voicevocoding and circuit data through requests for vocoder re–sourcesand MSC connection requests.

2. VPU–SEL Control (C9) – This is a signalling and control interfacebetween the SDU–SDF and the CP function of the VPU. It isproprietary and used to carry vocoder signalling and controlinformation for voice calls and circuit data calls when the IWU islocated at the MSC.

3. VPU–XC (C23) – This is a signalling and control interface betweenthe XC and the CP function of the VPU. It is proprietary and used tocarry vocoder signalling and control information for circuit data callswhen the IWU is located at the RAN.

4. VPU–MM (C24) – This is a signalling and control interface betweenthe MM call processing and the CP function of the VPU. It isproprietary and used to carry vocoder bypass and release messages.After a call has been established using C8 messaging, all subsequentsignalling messages are sent via the C24 interface.

Traffic Paths

The CDMA VPU supports the following Bearer interfaces andtermination points:1. IOS–A2 Interface (A2) – This is a bearer traffic interface used to

carry 64 kbit/sec PCM information. The A2 interface is defined byIOS and connects the VPU and the MSC. The A2 interface carries aduplex stream of user traffic.

2. IOS–A5 Interface (A5) – This is a bearer traffic interface used tocarry circuit data IWU interface between the VPU and the MSC. It isused when the IWU is located at the MSC. The A5 protocol is ISLPover the DS0 PCM bearer.

3. VPF–Traffic (B2) – This is a bearer traffic interface that is internal tothe CBSC and is used to carry duplex traffic for voice calls betweenthe VPU and the SDU–SDF. This interface is primarily for thetransfer of compressed speech information between the selectiondistribution function on the SDU–SDF and the vocoding functionVPF card within the VPU.

4. PTCIF/PSI–TER–Traffic (B3) – This is a bearer traffic interface thatis internal to the CBSC and is used to carry duplex traffic for circuitdata calls where the IWU is located at the RAN. The interface isbetween the XC and the CKTIW function on the VPF of the VPU.

5. A5IF–Traffic (B4) – This is a bearer traffic interface that is internalto the CBSC and is used to carry duplex traffic for circuit data callswhere the IWU is located at the MSC. The interface is between theSDU–SDF and the A5IW function on the VPF of the VPU.

10



O&M Paths

The CDMA VPU O&M interface paths are:

1. VPU/MM–RM (RM8) – This is a resource management signallinginterface between the MM and the RM/RA function of the VPU.This interface is used to discover, register, and request re–sourcesfrom the VPU. SCTP is used as the transport mechanism.

2. VPU/MM–FM (FM1) – This is a signalling interface between MMfault management and the RM/RA function of the VPU. Thisinterface is used to report terrestrial circuit block and unblockmessages.

3. CNEOMI O&M–Control (O3) – This is an O&M signallinginterface between the OMC–R and the O&M function of the VPU.This interface is used to initiate O&M related activities. Themanagement protocol between the OMC–R and the VPU isSNMPv2 over UDP in order to support the required CNEOMIinterface.

Redundancy

Multiple redundancy schemes are used in the VPU to meet variousfunctional requirements.

S CCA, ISB, DGBE, PSM, DOC3 and SPROC use 2N redundancy

S The BPP2 uses load sharing/over provisioning redundancy

S The pool of VPU shelves uses load sharing redundancy with an MMload manager handling distribution of the VPU load.

All MMs connected to a VPU must be under the sameOMC–R. A VPU cannot be managed by more than oneOMC–R.

NOTE

O&M

The VPU will use the SMNE (Self–Managed Network Elements)paradigm started in release 16.1 with the SDU and BTS (packet) andnow expanded to the VPU for release 16.3. Primary O&M interface willbe provided by the OMC–R.

10



VPU DCS Description

Description

With the introduction of the VPU, the RAN is OC–3/STM–1 capable atthe A2/A5 interface. The DCS is a new optional network elementstarting in release 16.3. If an MSC’s interface with the RAN is notOC–3/STM–1 capable, a point–to–point DCS configuration is needed toprovide multiplexing/demultiplexing between T1/E1 interfaces and aOC–3/STM–1 interface.

The DCS is not provided as part of the Motorola RAN solution. If theNetwork Operator’s MSC can not be equipped with an OC3/STM–1interface, then the operator must supply their own DCS.

Function

The DCS (de)multiplexes between T1/E1 and OC–3/STM–1 at aDS1/E1 and VT1.5/VT2 level. The DCS selected should meet thefollowing minimum requirements:

S Support E1 or T1 inputs as appropriate for the customer site.

S Support OC–3 or STM–1 as appropriate for the customer site.

S Cross–connect at a DS1/E1 to VT1.5/VT2 level.

S Support DS1/E1 capacity as appropriate for the customer site.

S Support 1+1 linear APS.

S Support dual BITS input or other suitable network timing interface.

Inputs and Outputs

The DCS will typically support the following inputs and outputs:

S T1/E1

S OC–3/STS–1 and/or STM–1/AU–4

S BITS

S Communication ports (O&M)

Card Description

The DCS may be new equipment supplied by the customer chosen thirdparty vendor. For specific information on the cards in the DCS, consultthe DCS product documentation. A typical DCS will consist of a NEBScompliant frame with 1 or more racks mounted within. The DCS willtypically contain the following primary board types or functions:

S T1, T3, or E1 terminates links from the MSC.

S OC–3 or STM–1 terminates OC–3/STM–1 links from the VPU.Supports linear 1+1 APS.

S Support for OC–3/STS–1 and/or STM–1/AU–4 pointer processing

S Clock card(s) – General equipment clocking and also supplies backupsynchronization timing when the timing source (e.g. BITS) fails.

10



S Processor card(s) – Providing O&M and FM functionality.

S Switch subsystem– supports DS1/E1 level cross–connect betweenT1/E1 and VT1.5/ VT2 on a OC–3/STM–1.

Signal Flow

Prior to 16.3, all circuit and voice data between the MSC and RAN wascarried over T1/E1 spans. With the introduction of the VPU in 16.3,voice and circuit data is carried over an optic fiber, OC–3/STM–1. If anMSC attached to the VPU does not support OC–3/STM–1 links, then aDCS is required to multiplex/demultiplex T1/E1 signals to an OC–3/STM–1 between the MSC and the VPU. With linear 1+1 APS, eachOC–3/STM–1 span has a working/protection relationship with anotherOC–3/STM–1 span. For outbound data, the working/protection pairsends the exact same data on both pairs. For inbound data, the DCSchooses to extract data from either the working or protectionOC–3/STM–1 span based on its APS configuration and the condition onthe OC–3/STM–1 spans.

Restrictions:

S The VPU only allows Working/Protection to be designated at a DOC3card level (as opposed to at a OCPORT level).

S The VPU does not allow both DOC3s to have “Working” OC–3 spansat the same time.

S The DCS must also allow Working/Protection to be designated at aOC–3 card level for the previous configuration to be feasible.

S The following configuration would be required if the DCS only allowsWorking/Protection to be designated at an OC–3 port level (asopposed to on an OC–3 card level). Cross Connecting theOC–3/DOC3 cards as shown would result in the loss of one of theOC–3 span pairs if the DCS OC–3 card fails.

Redundancy

See the DCS manufacturer information for specific redundancyinformation. The DCS’s OC–3/ STM–1 spans are provided in workingand protection pairs in order to deploy Automatic Protection Switching(APS).

O&M

All O&M is supported through the DCS’s O&M application.Provisioning of the DCS must be consistent with the provisioning of theVPU at the OMCR for the following:

S T1/E1 to VT1.5/VT2 mapping on the OC–3/STM–1.

S SDH Frame Type selection corresponds to VPU STM–1/AU–4 pointerprocessing and SONET Frame Type selection corresponds to VPUOC–3/STS–1 pointer processing.

S Working and protection OC–3/STM–1 ports and fibers.

S Linear 1+1 APS unidirectional/bidirectional andrevertive/non–revertive provisioning.

10



Also clock references source types, such as BITS, must be provisionedon the DCS in accordance with the DCS vendor recommendations.

Description of VPU TimingOptions

Overview

The VPU has three timing options. There are two external timingoptions, BITS and MSCVPUSPAN. There is one internal timing option,free–run mode. It is recommended that the BITS external timing optionbe used as the first choice as this will provide the most accurate VPUtiming configuration. The MSCVPUSPAN timing option isrecommended as the second choice and if neither external timing optionis available, the VPU can operate on its internal clock in the free–runmode and meet the OC3 SONET operating requirements.

Function

The VPU internal clock, one per ISB, is used to establish an internaltiming reference for all of the VPU Payload boards. The ISBs keep theirinternal clocks locked together so that if the master ISB clock shouldfail, the other ISB clock can immediately take over as the VPU timingsource. The VPU internal clock can be disciplined by the use of theexternal timing options, BITS and MSCVPUSPAN. The VPU internalclock will automatically use the following order of precedence fordisciplining the internal clock: 1st–BITS, 2nd–MSCVPUSPAN, and3rd– Free–Run mode. The VPU can be configured to use BITS,MSCVPUSPAN, or both as external timing sources, with the VPUautomatically enforcing the timing reference source order of precedence.

The VPU internal clock is also used as the OC3 transmit timing source.The OC3 S–byte, which is one of the bytes in the SONET overheadfield, is always set by the VPU to Do Not Use (DUS) for timing. TheVPU is considered the end of a timing chain and in order to ensure that atiming loop is not possible, the VPU S–Byte is permanently set to theDUS state so that the Network Entity (NE) on the other end of the OC3link will not attempt to recover timing from the VPU.

Inputs and Outputs

The VPU has two BITS connector inputs at the top of the frame. TheBITS connector is a DB–9 with a wire–wrap mating connector that isprovided standard with each frame. If wire–wrap is not the preferredinterconnect method, then the wire–wrap mating connector can beremoved and the VPU frame female DB–9 connector can be used.

10



The AIO board connector should be removed any timewiring changes are made to the BITS–1 or BITS–2wire–wrap connectors on a live system. The VPU willremain in–service if the AIO cable is unplugged and willautomatically begin using the BITS inputs again when theAIO board connector is plugged back into the rear AIOboard.

NOTE

BITS External Timing Source Input

The VPU will accept a 2.048 MHz square wave as a BITS timingreference source in accordance with ITU–T Table11/G.703(ver. 11/2001)& Figure 20/G.703(ver. 11/2001). The BITS connector is located at thetop of the VPU Frame. This clock source type is available from BITSequipment suppliers as a timing module that plugs into a BITSequipment shelf, typically with up to 10 clock ports per card. Forreference purposes, a Larus BITS configuration is provided in the BITSTiming Source section.

MSCVPUSPAN External Timing Source Input

Once the MSCVPUSPAN has been equipped via the VPUMSCVPUSPAN OMC–R CLI command, the VPU CLOCKSOURCEOMC–R CLI command is used to designate the MSCVPUSPAN as theclock source.

The VPU can terminate terrestrial circuits from more thanone MSC. The external MSCVPUSPAN external timingoption should be used only when there is one MSC beingserved by the VPU or when all MSCs use the same timingsource.

NOTE

BITS External Timing Source Description

A Building Integrated Timing Source (BITS) can be rack mounted andmanaged with its own management system. The BITS equipmenttypically requires an accurate timing source as its timing reference, atiming source such as GPS. The BITS equipment can be used as themaster timing source for an entire MTSO. The BITS shelf willaccommodate different clock modules in order to provide compatibletiming signals to the different Network Elements within an MTSO. Forinstance, the MSC and DCS may require a 1.544 MHz external timingreference from the BITS while the VPU will use a 2.048 MHz squarewave reference.

10



An example of a compatible BITS Source for use with the VPU is aLarus 5400 Series BITS system with a 5409–3 Clock module or a Larus54500 Series BITS system with a 54574 Clock module. The 5409–3module generates up to 10 clock outputs per clock module. The VPUwill accept a 2.048 MHz square wave as a BITS timing reference sourcein accordance with ITU–T Table11/G.703(ver. 11/2001)& Figure20/G.703(ver. 11/2001).

The VPU BITS inputs are transformer–isolated inputs with inputimpedances of 120 ohms. A BITS clock source that is rated to drive a120 ohm input should not require the use of an impedance matchingBalun.

MSCVPUSPAN External Timing Source Description

The OMC–R will only allow the VPU to be configured to use one of theWorking MSCVPUSPAN as it external timing reference. The OMC–Rautomatically maps the MSCVPUSPAN device ID to a DOC3 OC3 portand VT number on the Working/Protection DOC3 pair. There is only oneWorking/Protection DOC3 pair as a standard configuration in VPUrelease R16.3. The VPU will automatically choose the same OC3 portand VT number on the Protection OC3 should an automatic protectionswitch over to the Protection DOC3 occur.

10



VPU External Timing Signal Flow

The signal flow for the VPU external timing sources are as shown in thefollowing figure.

Figure 10-4: VPU External Timing Sources

Redundancy

The VPU internal clock source is located on each of the two ISBs.However only the active ISB provides the VPU timing. Upon ISBfailover to the warm–standby ISB, the VPU timing source moves to thewarm–standby that is turned into the active ISB. A VPU clock sourcechange from one ISB to the other is accomplished without being serviceaffecting.

10



Each ISB will accept external timing from the VPU BITS and from theMSCVPUSPAN inputs when the VPU is configured for the externaltiming reference inputs. Both BITS inputs are at the highest precedencelevel so if one input should fail, the VPU will automatically choose thesecond BITS input. Should both BITS inputs not be available or fail, theVPU will automatically choose the next highest precedence externaltiming source, the MSCVPUSPAN if provisioned. Else, the VPU willenter free–run mode and operate using the ISB internal clock and stillmeet the OC3 SONET operating requirements.

O&M

The VPU timing is provisioned from the O&M interface using thecommand line interface (CLI) command EDIT VPU CLOCKSOURCE.

The OMC–R CLI interface will prompt the user to specify at least oneexternal timing reference, either MSCVPUSPAN or BITS. If theMSCVPUSPAN timing source is used, the user will need to specify atthe OMC–R CLI which Span device ID number to use. The OMC–Rwill automatically map the SPAN device ID to an OC3 port andOC3–VT number to a Working/Protection DOC3 pair.

The VPU will automatically use the Working DOC3 board OC3interfaces if external timing is provisioned for a MSCVPUSPAN. Ifprotection switching from the Working DOC3 to the Protection DOC3should occur, then the Protection DOC3 OC3–VT will automaticallybecome the external clock source.

Once the VPU is put into service, should the VPU enter the free–runmode of operation an “all external references out–of–lock” alarm isissued. If no external timing sources are available by choice, then thisalarm should be ignored. The alarm is automatically cleared upon thereturn of either the MSCVPUSPAN or the BITS external timing sources.

10


Chapter 11: WAN/LAN Router

Table of Contents

WAN Router 11-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WAN/LAN Router Overview 11-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WAN/LAN Router Description 11-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11



Notes

11

WAN Router

APR 2005 CDMA2000 1X RAN Functional Description 11-1

WAN/LAN Router Overview

The WAN Router provides remote connectivity between Access Nodes,allowing for a seamless connection within the CDMA1X IPRAN.

The WAN router platform is the Cisco 7206VXR. Multiple WANRouters can be connected together for added system capacity and higheravailability.

Figure 11-1 depicts the basic architecture and connectivity diagram.

Figure 11-1: WAN/LAN Router Implementation

WAN Router – continued

11-2 CDMA2000 1X RAN Functional Description APR 2005

WAN/LAN Router Description

Function

Some customers have a Motorola CDMA RAN system configured withLAN WAN routers (LWRTRs) to provide WAN transport forinter–MTSO connectivity. This inter–MTSO WAN connection transportsSHO (Soft Handoff) bearer traffic, post–selected PCF (Packet ControlFunction) to PDSN (Packet Data Serving Node) traffic, managementtraffic for remote O&M, and signaling traffic between the MTSOs.

Each interconnected MTSO is configured with either dual–redundantactive–active LWRTRs or non–redundant single LWRTR.

Each MTSO being interconnected is equipped with LWRTRs thatconnect via Fast Ethernet/Gigabit Ethernet LAN interface to the Catalystswitches (CATs) in the AN IP Switch frame. The LWRTRs of eachMTSO are interconnected via T1, T3 or E1 type WAN interfaces.The LWRTR may be connected to more than one pair of CATs in anMTSO, depending on number of BSSANs.

LWRTRs are rack mounted and co–located with MTSO AN IP Switchframe(s).

Queuing functionality is available on the Cisco 7206VXR.

Chassis Description

The Motorola approved LWRTR is the Cisco 7206VXR/NPE Router.This router package includes:

S 6–slot chassis with mid–plane, fan tray with three cooling fans, andone 24V to 60V DC power supply

S Network Processing Engine (NPE) card with integrated I/O controllerand 3 Gigabit Ethernet ports

S Required software/firmware and RAM memory modules

S Required Compact Flash Memory card used in NPE card

S Optional redundant 24V to 60V DC power supply

S Optional Motorola approved LAN/WAN interface port adapter cards– LAN interface port adapter card; Cisco PA–2FE–TX– WAN interface port adapter cards; Cisco PA–2T3+, PA–MC–2T3+,PA–MC–8TE1+, and PA–A6–T3

All five port adapter cards can be installed in any available port adapterslot 1 through 6. The exact quantity and type of port adapters used isdependent on amount of traffic to be transported, traffic throughputrequirements, available LAN interfaces on CATs, available WAN spanlines, etc. These parameters may vary for each CDMA RAN system.


APR 2005 CDMA2000 1X RAN Functional Description 11-3

Card Description

Network Processing Engine (NPE): Maintains and executes the systemmanagement functions.

NPE

The following port adapters are supported with the NPE:

S PA–2FE–TX: 2 port Fast Ethernet Network Module (TX only).

S PA–MC–8TE1+: 8 port multichannel T1/E1 module with integratedCSU/DSU providing connectivity for up to 8 T1s.

S PA–T3+: 2 Port T3 Serial Port Adapter Enhanced with integratedCSU/DSU

S PA–MC–2T3+: 2 port multichannel (channelized) T3 port adapter

S PA–A6–T3: 1Port Enhanced ATM DS3 Port Adapter(8kVCs)

Inputs and Outputs

The 7206VXR WAN router can interface to the LAN with redundant100/1000 MB Ethernet interfaces. The function of the Inter–WAN routeris to transport traffic across MTSOs via the WAN interface.

Table 11-1: WAN Router Inputs and Outputs

Device ConnectionType

Quantity Specification

Comments

Catalyst to7206VXR orCatalyst to Tier2Switch to 7206VXR

100/1000 2 IEEE802.3ab100 m

System DesignDependent

7206VXR toTermination Equipment

T1,E1,T3,ATM

Up to 8 T1s perslot;total of 48 per7206VXRplatformUp to 2 T3 perslot;total of 12 per7206VXRplatform.T3 ATM is up tooneT3 per slot; totalof 6per 7206VXRplatform.

G.703133 ft

System DesignDependent


11-4 CDMA2000 1X RAN Functional Description APR 2005

Signal Flow

Internal in the 7206VXR a sample traffic flow would be:

S Ingress at the 100/1000 MB Ethernet port, across the back plane to theNPE routing engine.

S The routing engine makes the routing decision and forwards the trafficacross the back plane to the WAN Interface.

S The traffic is then encapsulated in the appropriate link technology andthen flows across the WAN link to the adjacent MTSO.

S This pattern is repeated in reverse on the adjacent WAN router.

Redundancy

The WAN/LAN Router can be deployed in either non–redundant orredundant configurations. An optional second WAN router can be addedfor 2N redundancy.

*68P09266A13−A*

68P09266A13–A

68P09266A13–AAPR 2005ENGLISH

SOFTWARE RELEASE 2.17.0.X

TechnicalInformation

CDMA2000 1X RAN FUNCTIONALDESCRIPTION

SO

FT

WA

RE

RE

LE

AS

E 2.17.0.X

CD

MA

2000 1X R

AN

FU

NC

TIO

NA

L DE

SC

RIP

TIO

N

ENGLISH

APR 2005

68P09266A13–A

Technical Information Products and Services

1 1

ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ

STANDARD MANUAL PRINTING INSTRUCTIONS

STANDARD SPECIFICATIONS – FOR REFERENCE–DO NOT MODIFY

Part Number: 68P09266A13–A APC:

Title: CDMA2000 1X RAN Functional Description

PAPER:

Body: 70 lb.

Inside Cover: 65 lb. Cougar

Tabs: 110 lb. Index

Binder Cover: Standard TEDcover – 10 pt. Carolina

1st. LEVEL TABS:

Single Sided

5 Cuts

Clear Mylar

Pantone 2706–C

Black Ink

2nd. LEVEL TABS: FINISHING:

3–Ring BinderSlant–D

3–Hole Punched(5/16–in. dia.)

Shrink Wrap Body

Black ink for body, inside cover, and binder cover.

SPECIAL INSTRUCTIONS

TAB and SHEET SIZE/QUANTITY

7X9 8.5x11 11x17

NON–STANDARD SPECIFICATIONS

Tape Bound Corner Stitch

Other: Meet with manager to determine the deliverable.

Sheets = (Total Pages) / 2

Single Sided

7 Cuts

Clear Mylar

White

Black Ink

Filename:

1st Level Tabs 2nd Level Tabs

Volume APR 2005of DatePrint Vendor: eDOC

Caring for the environment

Caring for the environment■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The following information is provided to enable regulatory compliance with the European Union (EU)Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE) when using Motorola Networksequipment in EU countries.

Disposal of Motorola Networks equipment in EU countries

Please do not dispose of Motorola Networks equipment in landfill sites.

In the EU, Motorola Networks in conjunction with a recycling partner will ensure that equipment is collectedand recycled according to the requirements of EU environmental law.

Please contact the Customer Network Resolution Center (CNRC) for assistance. The 24 hour telephonenumbers are listed at https://mynetworksupport.motorola.com/. Select Customer Network ResolutionCenter contact information, from the menu located to the left of the Login box. Alternatively if you do not have access to CNRC or the internet, contact the local Motorola office.

Disposal of Motorola Networks equipment in non-EU countries

In non-EU countries, dispose of Motorola Networks equipment in accordance with national and regionalregulations.

12JUL 2005

MPREJS1

Rectangle

CMM labeling and disclosure table

The People’s Republic of China requires that Motorola’s products comply with China Management Methods (CMM) environmental regulations. (China Management Methods refers to the regulation Management Methods for Controlling Pollution by Electronic Information Products.) Two items are used to demonstrate compliance; the label and the disclosure table.

The label is placed in a customer visible position on the product.

• Logo 1 means that the product contains no substances in excess of the maximum concentration value for materials identified in the China Management Methods regulation.

• Logo 2 means that the product may contain substances in excess of the maximum concentration value for materials identified in the China Management Methods regulation, and has an Environmental Friendly Use Period (EFUP) in years, fifty years in the example shown.

Logo 1 Logo 2

The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic and Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP) will not leak or mutate causing environmental pollution or bodily injury from the use of the EIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain field-replaceable parts, such as battery modules, can have a different EFUP and are marked separately.

The Disclosure Table is intended only to communicate compliance with China requirements; it is not intended to communicate compliance with EU RoHS or any other environmental requirements.

© 2007 Motorola, Inc. 68P02901W00-E

Cdma2000 1x Ran

Documents

Transcript of Cdma2000 1x Ran