IDEN System Overview and Functional Description

8/16/2019 IDEN System Overview and Functional Description

1/338

Technical Manual

iDEN

System Overview and

Functional Description

6871000P02-B

05-Sept-08

SR 17.0

SYSTEM LEVEL INFORMATION


2/338

Notice to Users

No part of this publication, or any software included with it, may be reproduced, stored in a retrieval system, or transmitted in any

form or by any means, including but not limited to, photocopying, electronic, mechanical, recording or otherwise, without the

express prior written permission of the copyright holder. Motorola, Inc. provides this document “AS IS” without warranty of any kind,

either expressed or implied, including but not limited to, the implied warranties of merchantability and fitness for a particular

purpose. Motorola reserves the rights to make changes or improvements in the equipment, software, or specifications described

in this document at any time without notice. These changes will be incorporated in new releases of this document.

Computer Software Copyrights

The Motorola and 3rd Party supplied Software (“SW”) products described in this instruction manual may include copyrighted

Motorola and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the United

States and other countries preserve for Motorola and other 3 rd Party supplied SW certain exclusive rights for copyrighted computerprograms, including the exclusive right to copy or reproduce in any form of the copyrighted computer program. Accordingly, any

copyrighted Motorola or other 3rd Party supplied SW computer programs contained in the Motorola products described in this

instruction manual may not be copied, reverse engineered, or reproduced in any manner without the express prior written

permission of Motorola or the 3rd Party SW supplier. Furthermore, the purchase of Motorola products shall not be deemed to grant,

either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Motorola

or other 3rd Party supplied SW, except for the normal non-exclusive, royalty free license to use that arises by operation of law in

the sale of a product.

Use and Disclosure Restrictions

The software described in this document is the property of Motorola, Inc. It is furnished under a duly executed license agreement

and may be used and/or disclosed only in accordance with the terms of the said agreement.

The software and documentation contained in this publication are copyrighted materials. Making unauthorized copies is prohibited

by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or

translated into any language or computer language, in any form or by any means, without the express prior written permission ofMotorola, Inc.

Trademarks

MOTOROLA, the Stylized M Logo, iDEN, and Message Mail are trademarks or registered trademarks of Motorola, Inc. in the United

States and other countries.

All other product or services mentioned in this document are identified by the trademarks or service marks of their respective

companies or organizations, and Motorola, Inc. disclaims any responsibility for specifying their ownership. Any such marks are

used in an editorial manner, to the benefit of the owner, with no intention of infringement.

© 2008 - Motorola, Inc. All Rights Reserved REV 12/15/06

Contact Information

Motorola, Inc.

Networks business

1501 Shure Dr.

Arlington Heights, IL 60004

U.S.A

SPECIFICATIONS ARE SUBJECT TO CHANGE WITHOUT NOTICE.

While reasonable efforts have been made to assure the accuracy of this document, this document may contain technical or

typographical errors or omissions. Motorola, Inc. and its subsidiaries and affiliates disclaim responsibility for any labor,

materials, or costs incurred by any person or party as a result of using this document. Motorola, Inc., any of its subsidiaries or

affiliates shall not be liable for any damages (including, but not limited to, consequential, indirect, incidental, or special damages

or loss of profits or data) even if they were foreseeable and Motorola has been informed of their potential occurrence, arisingout of or in connection with this document or its use. Motorola, Inc. reserves the right to make changes without notice to any

products or services described herein and reserves the right to make changes from time to time in content of this document

and substitute the new document therefor, with no obligation to notify any person or party of such changes or substitutions.


3/338


4/338

Table of Contents

Functional Description SR 17.0

iv 6871000P02-B 05-Sept-08

Urbans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Service Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Location Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Chapter 3iDEN Subsystem Overview

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Radio Access Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Key Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Links and Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Call Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Interconnect Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Interconnect Architecture . . . . . . . . . . . . . . . . . . . . . . . . 3-6


Links and Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Call Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Dispatch Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

Links and Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

Call Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

Packet Data Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20

Packet Data Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . 3-20

Key Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21


Call Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

Network Management Subsystem . . . . . . . . . . . . . . . . . . . . 3-26

Network Management Architecture. . . . . . . . . . . . . . . . 3-26

Key Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27

Databases and Applications . . . . . . . . . . . . . . . . . . . . . 3-28


Network Management Flows . . . . . . . . . . . . . . . . . . . . . 3-29

Other Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32

iDEN Gateway (iGW). . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32

http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


5/338

Table of Contents

SR 17.0 Functional Description

05-Sept-08 6871000P02-B v

Chapter 4

New Melody Core Solution in SR17.0

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

The Melody-based iDEN System . . . . . . . . . . . . . . . . . . . . . . 4-3

The Melody Controller Shelf (MCS) . . . . . . . . . . . . . . . . . . . . 4-5Shelf Switch Controller (SSC). . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Interconnect Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

iDEN Base Site Controller (iBSC). . . . . . . . . . . . . . . . . . . . . 4-11

iDEN Call Processor (iCP). . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

iDEN Call Processor Input/Output (iCP I/O) Shelf . . . . 4-14

iDEN Voice Processing Unit

Dispatch / Interconnect (iVPUdi) . . . . . . . . . . . . . . . . . . . . . 4-15

Nortel ATCA R4 Interconnect Switch. . . . . . . . . . . . . . . . . . 4-17

Dispatch Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Highly Available iDEN Home Location Register (iHLR) . . . 4-22

iDEN Surveillance Gateway (iSG). . . . . . . . . . . . . . . . . . . . . 4-24

Enhanced Global Title Translation Tool (EGT4) . . . . . . . . . 4-26

Network Management - The OMC. . . . . . . . . . . . . . . . . . . . . 4-27

Packet Data Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29

Chapter 5

iDEN System Functional Description

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Network Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Green Field Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Legacy iDEN System Architecture . . . . . . . . . . . . . . . . . 5-3

Network Links and Protocols . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

iDEN Network Protocols. . . . . . . . . . . . . . . . . . . . . . . . . 5-10

iDEN Protocol Documents . . . . . . . . . . . . . . . . . . . . . . . 5-16

Network Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

Interface Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

End-to-End Call Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

Radio Access Call Flow . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

Interconnect Call Flow . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22

Dispatch Call Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24

Packet Data Call Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25

http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


6/338

Table of Contents


vi 6871000P02-B 05-Sept-08

Chapter 6

Radio Access Network Details

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Radio Access Network Subsystem Description . . . . . . . . . . 6-2

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Radio Access Network Overview . . . . . . . . . . . . . . . . . . 6-2


Enhanced Base Transceiver System . . . . . . . . . . . . . . . . . . . 6-8

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

EBTS Hardware Description . . . . . . . . . . . . . . . . . . . . . . 6-8

EBTS Software Description . . . . . . . . . . . . . . . . . . . . . . 6-16

EBTS Network Management . . . . . . . . . . . . . . . . . . . . . 6-16

Chapter 7

Interconnect Subsystem Details

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Interconnect Subsystem Description . . . . . . . . . . . . . . . . . . 7-2

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Interconnect Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

iBSC Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

iBSC Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

iBSC Hardware Description. . . . . . . . . . . . . . . . . . . . . . . 7-9

iBSC Software Description . . . . . . . . . . . . . . . . . . . . . . 7-19iBSC Network Management . . . . . . . . . . . . . . . . . . . . . . 7-20

Mobile Switching Center Functional Description . . . . . . . . 7-23

MSC Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23

MSC Hardware Description . . . . . . . . . . . . . . . . . . . . . . 7-25

MSC Software Description. . . . . . . . . . . . . . . . . . . . . . . 7-27

MSC Network Management . . . . . . . . . . . . . . . . . . . . . . 7-27

Mobile Location Center Functional Description . . . . . . . . . 7-28

MLC Hardware Description . . . . . . . . . . . . . . . . . . . . . . 7-28

MLC Software Description. . . . . . . . . . . . . . . . . . . . . . . 7-28MLC Network Management . . . . . . . . . . . . . . . . . . . . . . 7-29

Interworking Function (IWF) . . . . . . . . . . . . . . . . . . . . . . . . . 7-30

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30

IWF Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30

IWF Hardware Description. . . . . . . . . . . . . . . . . . . . . . . 7-31

IWF Software Description . . . . . . . . . . . . . . . . . . . . . . . 7-33



7/338

Table of Contents


05-Sept-08 6871000P02-B vii

IWF Network Management . . . . . . . . . . . . . . . . . . . . . . . 7-33

SuperNode Data Manager/Fault Tolerant (SDM/FT) . . . . . . 7-34

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34

SDM/FT Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34

SDM/FT Hardware Description . . . . . . . . . . . . . . . . . . . 7-35

SDM/FT Software Description . . . . . . . . . . . . . . . . . . . . 7-36

SDM/FT Network Management . . . . . . . . . . . . . . . . . . . 7-36

Chapter 8

Dispatch Subsystem Details

Next Generation for Dispatch . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Final NGD Implementation. . . . . . . . . . . . . . . . . . . . . . . . 8-3

DAP Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Dispatch Subscriber Parameters . . . . . . . . . . . . . . . . . . 8-6

DAP Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

DAP Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

Core Architectural Models . . . . . . . . . . . . . . . . . . . . . . . 8-13

HA-DAP Functional Description. . . . . . . . . . . . . . . . . . . . . . 8-17

HA-DAP Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21

HA-DAP NGD Enhancements . . . . . . . . . . . . . . . . . . . . 8-23

Database Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26

HA Services Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27

iVPU Functional Description. . . . . . . . . . . . . . . . . . . . . . . . . 8-29

Software Description 34

iVPU Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34

iVPU Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34

Rolling Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . 8-37

HA-iHLR Functional Description . . . . . . . . . . . . . . . . . . . . . 8-39

HA-iHLR Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-43

HA-iHLR NGD Enhancements . . . . . . . . . . . . . . . . . . . . 8-44

HA-iHLR Database ASCII Dump . . . . . . . . . . . . . . . . . . 8-45

iDAC Functional Description . . . . . . . . . . . . . . . . . . . . . . . . 8-48

APD Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . 8-53

iSG Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . 8-57

MPS Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . 8-63



8/338

Table of Contents


viii 6871000P02-B 05-Sept-08

Chapter 9

Packet Data Subsystem Details

Packet Data Subsystem Description . . . . . . . . . . . . . . . . . . . 9-2

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Packet Data Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Mobile Data Gateway 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4

MDG2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4

MDG2 Hardware Description . . . . . . . . . . . . . . . . . . . . . . 9-5

MDG2 Software Description. . . . . . . . . . . . . . . . . . . . . . . 9-9

MDG2 Network Management . . . . . . . . . . . . . . . . . . . . . . 9-9

Mobile Data Gateway 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12

MDG4 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12

MDG4 Hardware Description . . . . . . . . . . . . . . . . . . . . . 9-14

MDG4 Software Description. . . . . . . . . . . . . . . . . . . . . . 9-17MDG4 Network Management . . . . . . . . . . . . . . . . . . . . . 9-18

Billing Accumulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22

BA Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22

BA Hardware Description. . . . . . . . . . . . . . . . . . . . . . . . 9-23

BA Software Description . . . . . . . . . . . . . . . . . . . . . . . . 9-26

BA Network Management. . . . . . . . . . . . . . . . . . . . . . . . 9-27

Chapter 10

Network Management Subsystem DetailsOMC-R Functional Description. . . . . . . . . . . . . . . . . . . . . . . 10-2

NGO Functional Description. . . . . . . . . . . . . . . . . . . . . . . . 10-11

EGT4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . 10-18

Cisco WAN Manager Functional Description . . . . . . . . . . 10-21

Chapter 11

Other Network Elements

iGW Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

NDM Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . 11-8

DM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12

ASP EM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14

NDM PWI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14

NDM BU Admin Web Interface. . . . . . . . . . . . . . . . . . . 11-14



9/338


05-Sept-08 6871000P02-B ix

List of Figures 0

Figure 1-1 Simplified SR16.0 Components Diagram.......................................................... 1-6

Figure 2-1 Initial SU System Contact.................................................................................. 2-2

Figure 2-2 iDEN Network Hierarchical Structure ................................................................ 2-7

Figure 3-1 Radio Access Network Architecture .................................................................. 3-2

Figure 3-2 Call Flow with Radio Access Network............................................................... 3-4

Figure 3-3 SR16.0 Interconnect Architecture ..................................................................... 3-6

Figure 3-4 Interconnect Resource Request Process View (Steps 1-8) ............................ 3-11

Figure 3-5 Interconnect Call Setup Process View (Steps 9-15) ....................................... 3-11

Figure 3-6 Interconnect Connecting Voice Process View (Steps 16-19).......................... 3-12

Figure 3-7 Dispatch Group Call Resource Request (Steps 1-4)....................................... 3-16

Figure 3-8 Dispatch Group Call Paging (Steps 5-9) ......................................................... 3-17

Figure 3-9 Dispatch Group Call Set up (Step 10)............................................................. 3-17

Figure 3-10 Dispatch Group Call Connect Voice (Steps 11-13) ......................................... 3-17

Figure 3-11 SR16.0 Packet Data Architecture.................................................................... 3-20

Figure 3-12 Packet Data Call Flow Registration (Steps 1-8) .............................................. 3-24

Figure 3-13 Network Management (NGO) Architecture ..................................................... 3-26

Figure 3-14 iCP Status Information Flow (Collection)......................................................... 3-30

Figure 3-15 iCP Status Information Flow (Report).............................................................. 3-31

Figure 3-16 iGW Network Flow........................................................................................... 3-33

Figure 3-17 SIP to S2D Call Flow (Steps 1-8).................................................................... 3-36

Figure 4-1 “Legacy” iDEN System...................................................................................... 4-2

Figure 4-2 Melody-based iDEN System ............................................................................. 4-4

Figure 4-3 Melody Controller Shelf (MCS) Front View ...................................................... 4-6

Figure 4-4 Melody Controller Shelf (MCS) Rear View ....................................................... 4-6

Figure 4-5 Shelf Switch Controller (SSC) Blades .............................................................. 4-7

Figure 4-6 SSC Redundancy.............................................................................................. 4-9

Figure 4-7 Interconnect Subsystem ................................................................................. 4-10

Figure 4-8 iDEN Base Site Controller (iBSC) .................................................................. 4-11

Figure 4-9 iDEN Call Processor (iCP) ............................................................................. 4-12

Figure 4-10 iCP Redundancy ............................................................................................ 4-13

Figure 4-11 iDEN Call Processor Input/Output (iCP I/O) Shelf .......................................... 4-14

Figure 4-12 iDEN Voice Processing Unit Dispatch / Interconnect (iVPUdi) in System ...... 4-15

Figure 4-13 iDEN Voice Processing Unit Dispatch / Interconnect (iVPUdi) Cage view...... 4-16

Figure 4-14 Nortel ATCA R4 Interconnect Switch ............................................................. 4-17

Figure 4-15 Home Location Register (HLR), Call Server (CS), Media Gateway (MGW) ... 4-18

Figure 4-16 Dispatch Subsystem ....................................................................................... 4-19



10/338

List of Figures


x 6871000P02-B 05-Sept-08

Figure 4-17 Highly Available iDEN Home Location Register (iHLR) .................................. 4-22

Figure 4-18 iSG Network .................................................................................................... 4-24

Figure 4-19 Enhanced Global Title Translation Tool (EGT4) ............................................. 4-26

Figure 4-20 Network Management - The OMC ................................................................. 4-27

Figure 4-21 OMC Network ................................................................................................. 4-28

Figure 4-22 Packet Data subsystem .................................................................................. 4-30Figure 5-1 iDEN System Architecture................................................................................. 5-2

Figure 5-2 Legacy iDEN System Architecture .................................................................... 5-3

Figure 5-3 Network Protocol and Links Diagram.............................................................. 5-10

Figure 5-4 Legacy Network Protocol and Links Diagram ................................................. 5-13

Figure 5-5 Radio Access Call Flow................................................................................... 5-21

Figure 5-6 Mobile Originated Interconnect Call Setup Step Diagram............................... 5-23

Figure 5-7 Typical Dispatch Call Summary ...................................................................... 5-25

Figure 5-8 Packet Data Call Flow ..................................................................................... 5-27

Figure 6-1 Radio Access Network Architecture................................................................. 6-3

Figure 6-2 NGD Configuration ........................................................................................... 6-4Figure 6-3 NGD Mixed Mode Configuration ....................................................................... 6-5

Figure 6-4 EBTS Cabinets.................................................................................................. 6-9

Figure 6-5 Radio Frequency Cabinet................................................................................ 6-10

Figure 6-6 iSC3 Front Panel ............................................................................................. 6-11

Figure 6-7 iSC2 - Front and Rear Views........................................................................... 6-13

Figure 6-8 Duplex RFDS .................................................................................................. 6-15

Figure 7-1 NGD System ..................................................................................................... 7-3

Figure 7-2 Mixed Mode Configuration ................................................................................ 7-4

Figure 7-3 Split Mode Configuration................................................................................... 7-5

Figure 7-4 iBSC in the iDEN Network................................................................................. 7-7

Figure 7-5 iBSC Architecture .............................................................................................. 7-8

Figure 7-6 iBSC Coverage.................................................................................................. 7-8

Figure 7-7 iBSC Hardware................................................................................................ 7-10

Figure 7-8 iCP Frame Layout ........................................................................................... 7-11

Figure 7-9 iCP I/O Shelf.................................................................................................... 7-12

Figure 7-10 RSL Configurations ......................................................................................... 7-14

Figure 7-11 iVPU Components........................................................................................... 7-15

Figure 7-12 iVPU Front Cage............................................................................................. 7-16

Figure 7-13 iVPU Rear Cage.............................................................................................. 7-17

Figure 7-14 iBSC Links and Interfaces ............................................................................... 7-19

Figure 7-15 MSC in the Interconnect Subsystem............................................................... 7-24

Figure 7-16 MSC Components........................................................................................... 7-25

Figure 7-17 Interworking Function Services ....................................................................... 7-31

Figure 7-18 IWF Front View................................................................................................ 7-32

Figure 7-19 IWF Back View ................................................................................................ 7-32

Figure 8-1 Mixed Mode Stage One..................................................................................... 8-2

Figure 8-2 Mixed Mode Stage Two..................................................................................... 8-3



11/338

List of Figures


05-Sept-08 6871000P02-B xi

Figure 8-3 Next Generation Dispatch Network................................................................... 8-3

Figure 8-4 R10K DAP Cabinet............................................................................................ 8-9

Figure 8-5 R12K DAP Cabinet.......................................................................................... 8-10

Figure 8-6 HA-DAP Cabinet- Front and Rear View .......................................................... 8-19

Figure 8-7 RX7620 Server-Front Panel............................................................................ 8-20

Figure 8-8 RX7620 Server-Back Panel ............................................................................ 8-21Figure 8-9 iVPU Front and Rear Cabinet.......................................................................... 8-32

Figure 8-10 HA-iHLR Front and Rear Cabinet.................................................................... 8-42

Figure 8-11 iDEN Dispatch Access Controller - Front View ............................................... 8-50

Figure 8-12 iDEN Dispatch Access Controller - Rear View ................................................ 8-51

Figure 8-13 Advanced Packet Duplicator - Front View....................................................... 8-55

Figure 8-14 iSG 1 and iSG 2 Cabinet ................................................................................. 8-60

Figure 8-15 MPS Cabinet Lineup ....................................................................................... 8-66

Figure 9-1 NGD System ..................................................................................................... 9-3

Figure 9-2 MDG2 - Front View............................................................................................ 9-6

Figure 9-3 Actual MDG2- Front View.................................................................................. 9-8Figure 9-4 MDG4 in the iDEN Network............................................................................. 9-13

Figure 9-5 MDG4 Board Layout........................................................................................ 9-16

Figure 9-6 MDG4 - Actual Front View............................................................................... 9-17

Figure 9-7 MGD4 User Interface Menu ............................................................................ 9-19

Figure 9-8 Billing Accumulator Mirror Function................................................................. 9-23

Figure 9-9 Billing Accumulator - Front View ..................................................................... 9-24

Figure 9-10 Back Panel of the Billing Accumulator............................................................. 9-25

Figure 10-1 Sun Fire 4800- Front View .............................................................................. 10-4

Figure 10-2 Sun Fire 4800- Rear View ............................................................................... 10-5

Figure 10-3 Enterprise 3500- Front View............................................................................ 10-6

Figure 10-4 Enterprise 3500- Review View ........................................................................ 10-7

Figure 10-5 Netra 440- Front View ................................................................................... 10-13

Figure 10-6 Netra 440-Rear View..................................................................................... 10-13

Figure 11-1 iGW in the iDEN Network ................................................................................ 11-3

Figure 11-2 iGW Cabinet Configuration.............................................................................. 11-5

Figure 11-3 NDM Connectivity in the iDEN Network .......................................................... 11-9

Figure 11-4 NDM Cabinet - Front and Rear ..................................................................... 11-11



12/338

List of Figures


xii 6871000P02-B 05-Sept-08

N O T E S . . .



13/338


05-Sept-08 6871000P02-B xiii

List of Tables 0

Table 1 Reader’s Objectives .......................................................................................... xvii

Table 2 Related Manuals ................................................................................................ xix

Table 3 Recommended iDEN Training........................................................................... xxii

Table 4 Disclosure Table.............................................................................................. xxvii

Table 5 Revision History .............................................................................................. xxviii

Table 6 Acknowledgements .......................................................................................... xxix

Table 5-1 Key to iDEN System Components Diagrams.................................................... 5-3

Table 5-2 Key to Network Protocols and Links Diagram ................................................. 5-11

Table 5-3 Key to Legacy Network Protocols and Links Diagram .................................... 5-14

Table 5-4 iDEN Protocol Documentation......................................................................... 5-16Table 7-1 iCP Board Functions ....................................................................................... 7-13

Table 7-2 Split Mode RSL Card Configuration ................................................................ 7-14

Table 7-3 iVPU Board Functions..................................................................................... 7-17

Table 8-1 Mixed Mode and Final NGD Architecture NEs.................................................. 8-4

Table 8-2 Statistics Changes for BCCB 862 ................................................................... 8-12

Table 8-3 Parameters Added for BCCB 1020 ................................................................. 8-25

Table 8-4 Statistics Added for BCCB 1020 ..................................................................... 8-25

Table 8-5 iVPU User Account Commands ...................................................................... 8-37



14/338

List of Tables


xiv 6871000P02-B 05-Sept-08

N O T E S . . .



15/338

About this manual...


05-Sept-08 6871000P02-B xv


This chapter of the manual describes the manual in general terms. The major

topics of the chapter include: The intended content of the manual

How the manual is to be used

Other reference material that supports information in this manual

Elements in the appearance of the manual and their meaning

General safety guidelines

The changes to the manual over time

Who helped produce and validate information in the manual



16/338


Purpose


xvi 6871000P02-B 05-Sept-08

Purpose 0

The primary purpose of the iDEN System Overview and Functional

Description is to provide general technical background about the iDEN

system, key subsystems, and network elements. The information in the iDEN

System Overview and Functional Description will expose users to the purposeand parts of the iDEN system and prepare them to locate and use additional

technical information.



17/338


How to Use this Manual


05-Sept-08 6871000P02-B xvii

How to Use this Manual 0

This manual is designed to supports reader goals for various kinds of infor-

mation. (see Audience Profile).

Chapters 1 through 4 are designed to give the reader a simple overview of theiDEN system. The remaining chapters go into more details and specifics

about the iDEN functions and components.

Audience Profile 1

The iDEN System Overview and Functional Description is intended for iDEN

service providers and iDEN network operators, two key roles associated with

an iDEN system.

Service Providers are those interested in the iDEN system from a business

perspective. This audience is responsible for seeing that the system

generates revenue and meets regulations and service level agreements by

delivering calling services to subscribers and users. Network Operators are those involved in the front-line of an iDEN system,

e.g., implementation or support. This audience is the technical entity

responsible for installing and operating the network infrastructure and links

by which the services are provided to subscribers and users.

Table 1 Reader’s Objectives

Chapter Reader’s Goals

Chapter 1 iDEN Technology Foundation Basic Knowledge

Chapter 2 iDEN System Overview Basic Knowledge

Chapter 3 iDEN Subsystem Overview Basic Knowledge

Chapter 4 New Melody Core Solution for SR17.0 Basic Knowledge

Chapter 5 iDEN System Functional Description Advanced Knowledge

Chapter 6 Radio Access Network Details Advanced Knowledge

Chapter 7 Interconnect Subsystem Details Advanced Knowledge

Chapter 8 Dispatch Subsystem Details Advanced Knowledge

Chapter 9 Packet Data Subsystem Details Advanced Knowledge

Chapter 10 Network Management Subsystem Details Advanced Knowledge

Chapter 11 Other Network Elements Advanced Knowledge



18/338


Customer Network Resolution Center


xviii 6871000P02-B 05-Sept-08

Customer Network Resolution Center 1

The Customer Network Resolution Center (CNRC) is a integral part of the

network support process.

Before performing any major changes or optimization on the system, pleasecontact the CNRC. Notify the CNRC with the nature of the change and the

schedule for the change. This will allow CNRC to have the correct technical

support engineers on call in case they are needed.

Please refer to the Customer Guide to iDEN Customer Network Resolution

Center (CNRC) (WP2000-003) for more information regarding:

Procedures for calling CNRC

Classification of trouble tickets

The escalation processes

This document is located on the iDEN extranet website at the URL:

http://mynetworksupport.motorola.com

The CNRC can be contacted at the following telephone numbers:

United States and Canada

1-800- 499-6477

International

1+847-704-9800

Note Toll-free international access codes are available for many locations.Please refer to Appendix E of the Customer Guide to iDEN Customer

Network Resolution Center (WP2000-003) for a list of these access

codes and dialing instructions.



19/338


Related Manuals


05-Sept-08 6871000P02-B xix

Related Manuals 1

The following publications may be required to supplement the information

contained in this manual.

These references are available on the Motorola Extranet web site at http://mynetworksupport.motorola.com.

Table 2 Related Manuals

Part Number Document Name

68P81001Y90 OMC-R System Overview

68P81001Y91 OMC-R Configuration Management User’s Guide

68P81001Y93 OMC-R System Administrator Guide

68P81001Y95 OMC-R Performance Management

68P81001Y97 OMC-R Online Change Configuration User’s Guide

68P81001Y92 OMC-R Configuration Management Parameters

68P81001Y94 OMC-R Event/Alarm Management

68P80801A10 MSC Planning and Expansion Guide

68P80801C90 iDEN Packet Data Service Registration And Call

Processes

68P81001Y54 EGT4 Alarm Documentation

68P81001Y53 EGT4 Users Manual

68P81095E55 iDEN System Technical Overview

68P81131E90 Guide to Motorola Acronyms and Terms

68P80801E35 EBTS Volume 1 System Installation and Testing

68P80801E35 EBTS Volume 2 Base Radios

68P80801E35 EBTS Volume 3 RF Distribution Systems

68P81098E05 iDEN Integrated Site Controller System Manual

68P80801E30 iDEN Gen 3 Site Controller System Manual

68P81001Y55 Ethernet Analyzer Detective Software User's Manual

6881012Y80 Interconnect Troubleshooting Guide

68P81001Y77 iBSC Hardware Manual

68P80800H75 BSC Troubleshooting Guide

6880802F80 BSSC3 Hardware Change Manual



20/338


Related Manuals


xx 6871000P02-B 05-Sept-08

6880802F05 BSC MMI Commands

68P81006Y39 Interconnect Troubleshooting Tools - Tools from the

MSC, BSC & SMS

68P80801A10 MSC Planning and Expansion Guide

68P80801A20 MSC Optimization

68P80800E10 IWF Installation Manual

68P80802B05 IWF System Release Implementation Manual

68P80800B95 MDG System Manual SR12.0

68P80801C90 iDEN Packet Data Service –Registration and Call

Processes

68P80802D30 MDG Command Reference

6881012Y82 Packet Data Subsystem Troubleshooting Guide

68P81001Y76 MDG4 Hardware Installation Manual

6881001Y49 DAP User Guide

6881001Y50 DAP Hardware Installation Manual

68P81001Y83 HA Dispatch Application Processor (HA-DAP) User

Manual

68P81001Y84HA-DAP Hardware Installation Manual

68P81001Y52 iHLR User Manual

6881001Y51 iHLR Hardware Installation Manual

68P80801H50 iDEN CPX1205 Common Platform Hardware Refer-

ence Manual

68P80801H55 iDEN Dispatch Access Controller Application Manual

68P80800C45 iDEN Advanced Packet Duplicator Installation

Manual

68P81131E11 CPX Common Platform Hardware Reference Manual

6881012Y17 iDEN Surveillance Gateway (iSG) Application

Manual

68P80802A85 GR Implementation Manual System Release MPS5.1

6871000P31 iDEN Switch Shelf Controller User Manual

Table 2 Related Manuals (continued)




21/338


Related Manuals


05-Sept-08 6871000P02-B xxi

6871000P36 iDEN Melody Core Solution Hardware Reference

Manual

WP04003o MSO Timing System

WP2002-025 EBTS Backhaul: Frame Relay DSO Requirements

WP2003-009 Initial RF Design Guidelines - RF Planning

WP05008B 900 Quad EBTS Multi-Sector Rack Configuration

WP2003-014 iDEN EBTS Fan Maintenance Plan

WP2001-010 iDEN EBTS Total Site Maintenance

WP2002-026 Inbound Handover Threshold Optimization

WP04008 Legacy BSC to iBSC Reference Guide

WP2002-021 Understanding iDEN System Fault Tolerance -

Interconnect Subsystem

WP2000-002 Overview of iDEN Packet Data RF Operation and

Performance

WP2002-023 Understanding iDEN System Fault Tolerance –

Packet Data Subsystem

WP2003-019 Packet Data Troubleshooting Equipment List for 64K

MDG

WP2003-020 Remote Access to 64K MDG MMI

WP2002-022 Understanding iDEN System Fault Tolerance -

Dispatch Subsystem

WP06003 iVPUd Management of BPP2 Resources

WP06006 SR14.0 IVPUdi BPP2 Resource Management

HC05002 MPS and CWM Health Checks

HC06006 SR14.0 Packet Data Health Check

HC06003 iBSC Health Check

ASCE16 SR16.0 iDEN Alarm and State Change EventReference Manual

Table 2 Related Manuals (continued)




22/338


Recommended Training


xxii 6871000P02-B 05-Sept-08

Recommended Training 2

To further enhance your understanding of the iDEN system, it is recom-

mended that you complete the following Motorola-offered training courses.

Contact your local training coordinator for course enrollment information.

Training Access 3

To access the iDEN Technical Training Course Catalog on MyNetwork-

Support, follow the steps below.

Table 3 Recommended iDEN Training

Course Number Description

GEN101 iDEN Overview

GEN102 iDEN System School

GEN103 iDEN System Overview

FND106 OMC Fundamentals Course

SRL316 An Introduction to System Release 16.0

OPM202 OMC System Administration Course

ADV401 iDEN System Recovery Topics Course

OPM214 iBSC Operations & Maintenance

TO Access the iDEN Technical Training Course Catalog

Step Action

1 Login to MyNetworkSupport at:https://mynetworksupport.motorola.com/

The MyQuickLinks screen appears.

2 Scroll down to the section for iDEN technology.

3 On the right side of the page, click on iDEN Training Catalog.



23/338


Manuals On-line


05-Sept-08 6871000P02-B xxiii

Manuals On-line 3

This manual is available on the World Wide Web at mynetworksupport , the

iDEN customer site. This site was created to provide secure access to critical

iDEN Infrastructure information. This web site features a library of iDEN

Infrastructure technical documentation such as bulletins, system releasedocuments and product manuals.

The documents are located on the secured extranet website at the URL:

https://mynetworksupport.motorola.com

For information on obtaining an account on this site, go to:

https://membership.motorola.com/motorola

Reporting Manual Errors 3

If you locate an error or identify a deficiency in this manual, please take the

time to contact us at the following email address:

[email protected]

Be sure to include your name, fax or phone number, the complete manual title

and part number, the page number where the error is located, and any

comments you may have regarding what you have found.

Thank you for your time. We appreciate any comments from the users of our

manuals.



24/338


Conventions


xxiv 6871000P02-B 05-Sept-08

Conventions 3

Software submenu commands— Table > Table Designer

new terms— mobile station

keystrokes— Ctrl+Alt+Delete, Return

mouse clicks—click, double-click

user input—Type delete

screen output— DAP is starting....

Hardware CD-ROM

Safety This manual may contain safety notices (alerts). Alerts are based on thestandards that apply to graphics on Motorola equipment. Specific procedural

notices are stated in the procedures as required and have specific visual repre-

sentations. The representations are:

! DANGER

INDICATES AN IMMINENTLY HAZARDOUS SITUATION

WHICH, IF NOT AVOIDED, WILL RESULT IN DEATH OR

SERIOUS INJURY.

! WARNING

Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.

! CAUTION

Indicates a potentially hazardous situation which, if not

avoided, could result in minor or moderate injury.

CAUTIONWithout the alert symbol indicates a potentially hazardous

situation which, if not avoided, may result in property damage.



25/338


Conventions


05-Sept-08 6871000P02-B xxv

Important Indicates an item of the essence of a topic that is indispensable.

Note Indicates something of notable worth or consequence.

General Safety 3

Important Remember Safety depends on you!!

General safety precautions must be observed during all phases ofoperation, service, and repair of the equipment described in thismanual. 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.

You must heed the safety precautions and warnings listed in the product

manuals for your equipment. Any individual using or maintaining the

product(s), should follow these warnings and all other safety precautions

necessary for the safe operation of the equipment in your operating

environment. Motorola, Inc. assumes no liability for failure to comply with

these requirements.



26/338


CMM Labeling and Disclosure Table


xxvi 6871000P02-B 05-Sept-08

CMM Labeling and Disclosure Table 3

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 areused 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.

The Environmental Friendly Use Period (EFUP) is the period (in years)

during which the Toxic and Hazardous Substances (T&HS) contained in theElectronic Information Product (EIP) will not leak or mutate causing environ-

mental 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 (shown on the following page) is intended only to

communicate compliance with China requirements; it is not intended to

communicate compliance with EU RoHS or any other environmental require-

ments.



27/338


CMM Labeling and Disclosure Table


05-Sept-08 6871000P02-B xxvii

Table 4 Disclosure Table



28/338


Revision History


xxviii 6871000P02-B 05-Sept-08

Revision History 4

The following table contains a list of the revisions made to this guide.

Table 5 Revision History

Date Issue Description of Changes

02/26/06 O Original Publication for SR15.0

10/04/07 A Updated for SR16.0

05/09/08 B Updated for SR17.0



29/338


Acknowledgements


05-Sept-08 6871000P02-B xxix

Acknowledgements 5

We recognize and thank the following contributors.

Table 6 Acknowledgements

Name Name

Ann Kohut John Mabbott

Mark Interrante Patti Rausch

Elayne Tillman Steve Hart

Todd Mueller Gil Scovill

Carlos Carrillo Thomas Logsdon

Sheila Raines Bryan Blanco

Gabriel Bovino



30/338


List of Changed Pages


xxx 6871000P02-B 05-Sept-08

List of Changed Pages 6

The table below lists new or changed information, of a technical nature, that

has been added or changed since the previous release of this document.

Chapter Page(s) Type of Change

Chapter 4- New Melody Core Solution

for SR17.0

All Chapter 4

pages

Replaced the SR16.0 new features

chapter with this new chapter to

introduce the SR17.0 Melody Core

solution.



31/338


05-Sept-08 6871000P02-B 1-1

Chapter 1

iDEN Technology Foundation

Introduction 1

The outgrowth of the wireless communications market has produced vast

opportunities to enhance and improve the communications between

individuals. Because of this growth, the need to optimize Radio Frequency

(RF) spectral resources and provide ever-increasing services is essential.

To support the increase in wireless services while making best use of available

resources, the iDEN system capitalizes on the fact that communications can

be:

Half-duplex—where one user is transmitting (talking) and other users are

receiving (listening)

Full-duplex—where there is an open bi-directional link that allows full two-way communication

Many times communication does not require a full-duplex link. Messaging,

paging, some forms of data communication, and structured voice communi-

cation are, or can effectively operate in, half-duplex mode.

Traditional telephone conversations and more intensive data links require the

ability to interrupt; that requires full-duplex operation.

By utilizing both full and half-duplex operations, iDEN allows much of the

voice traffic to be run in half-duplex mode, while providing full-duplex

functionality when required.

As part of the ongoing effort to support the outgrowth in wireless communi-

cation, the iDEN system is an integration of traditional Push-To-Talk (PTT),

half-duplex, analog radio technology, and feature-rich, full-duplex digital

cellular communications. This integration of mobile communication technol-

ogies provides state-of-the-art functions and benefits to mobile users while

optimizing the available infrastructure resources.



32/338



1-2 6871000P02-B 05-Sept-08

iDEN System Introduction 1

At the highest-level, the iDEN system is the infrastructure that is used to

deliver services to mobile subscribers (MS) using a single subscriber unit

(SU). This subsection briefly describes the subscriber/user services available

from the iDEN system and the network infrastructure that delivers these

services.

Note SU is also referred to sometimes as Mobile Station. For clarity purposes, in this manual the term SU is used, not Mobile Station (MS).

Subscriber Services 1

The iDEN system provides services that include: two-way radio communi-

cation, cellular/wireless telephone communication, and wireless data services.

The iDEN network provides the customer with a complete solution to all of

their wireless needs, using a single SU.

The iDEN network converts analog voice to digital code for transmissionover the air.

iDEN uses TDMA technology which separates RF channels into time slots,

allowing multiple users to share each RF channel by transmitting at

different times.

The iDEN SU continually measures signal quality to maintain strong signal

reception.



33/338


iDEN System Technologies


05-Sept-08 6871000P02-B 1-3

iDEN System Technologies 1

The iDEN system is a digital wireless system that uniquely combines digital

mobile telephone and data technologies. Through all of these features and

services, the iDEN system provides subscribers with the latest integrated

wireless communications solutions.

Wireless Telephony 1

To convert an analog voice signal to a digital signal, the wave pattern is

sampled at different points and a digital representation of 1s and 0s is given to

the sample at each point. This digital representation can be stored, replicated,

or transmitted without further degradation.

The SU performs the conversion of analog voice into digital code using two

voice encoding, or vocoding, techniques called VSELP and AMBE++. These

techniques also compress large segments of voice into smaller segments formore efficient transmission of the voice data.

The iDEN system uses Time Division Multiple Access (TDMA). TDMA

divides each 25 kilohertz radio frequency, or RF channel into 6 time slots,

allowing 6 communication paths on a single RF channel. Multiple users are

assigned the same channel frequency and share the RF channel by trans-

mitting at different times. The sharing of RF channels enables TDMA

technology to be more efficient in its utilization of resources.

iDEN maintains strong signal reception by continually measuring the signal

quality of the serving cell and all of the surrounding neighbor cells. If the

signal quality drops below an acceptable level, the SU moves to a site thatoffers a better signal, and thus be assigned a new RF channel and time slot for

transmission.

Two-way Dispatch Radio 1

Dispatch offers two-way radio communication between subscribers.

The Dispatch features of the iDEN network are based on two-way trunking,

which allows individual subscribers, or groups of subscribers, to commu-

nicate quickly and easily with each other.

Dispatch operates in a half-duplex mode, which means that a subscriber can

either talk or listen to another subscriber using the push-to-talk button, but can

not do both at the same time.



34/338


iDEN System Technologies


1-4 6871000P02-B 05-Sept-08

Data 1

There are three categories of data services supported by the iDEN network.

They are as follows:

Short Message Service (SMS)—This service is commonly referred to as

text messaging. Circuit Data—Circuit data enables the subscriber to send and receive faxes

and email, connect to online services such as a web service provider, and to

access databases.

Packet Data—Packet Data provides the subscriber access to Intranet and

Internet applications using standard Internet Protocols.



35/338


Network Infrastructure


05-Sept-08 6871000P02-B 1-5

Network Infrastructure 1

The network infrastructure of the iDEN system offers a variety of services and

features that provide subscribers with the latest integrated wireless communi-

cations solutions. These services and features are divided into three

categories:

Interconnect—The Interconnect subsystem allows a SU to travel freely

throughout an iDEN system and communicate with other subscribers and

land line systems. Within this extended network, a user can originate or

receive Interconnect calls, and if so provisioned, access data and voice mail

services.

Dispatch—Dispatch calls are voice communications that use the half-

duplex Push-To-Talk (PTT) form of communication. This type of call does

not use other provider networks except as transport facilities.

Packet Data—Packet Data in iDEN, is a non-voice communication

interface that connects the SU directly with the Intranet, Internet, Virtual

Private Network (VPN), and the Extranet. Packet Data networking allows

the service provider to become a point-of-presence for mobile users on the

Internet.



36/338




1-6 6871000P02-B 05-Sept-08

iDEN Infrastructure for the MSO 1

There are four subsystems in the infrastructure of the Mobile Switching

Office (MSO) for the iDEN system: Interconnect, Dispatch, Packet Data

(PD), and Network Management - Operations and Maintenance Center

(OMC). These subsystem support the services and features for the iDEN

system.

Figure 1-1 displays the basic infrastructure of the iDEN system at its basic

level.

Figure 1-1 Simplified SR16.0 Components Diagram

Note The EBTS is not part of the MSO. See iDEN Subsystem Overview on page 3-1 for more information for all iDEN subsystems.

OMC



37/338




05-Sept-08 6871000P02-B 1-7

Interconnect The Interconnect subsystem allows a SU to travel freely throughout an iDEN

system and communicate with other subscribers and land line systems. Within

this extended network, a user can originate or receive Interconnect calls, and

if so provisioned, access data and voice mail services.

The major components of the Interconnect subsystem are as follows:

iDEN Base Site Controller (iBSC)—routes Interconnect packets between

the EBTS and the MSC.

Mobile Switching Center (MSC)—determines Interconnect services

(iHLR) and SU location information (VLR) and also controls/routes

Interconnect calls within the network and to other service providers.

Short Message Service (SMS)—provides text message services.

Voice Mail Server (VMS)—serves as an answering machine and stores

messages for the SU. VMS also indicates when voice mail is present.

Supernode Data Manager-Fault Tolerant (SDM/FT)—allows law

enforcement agencies to obtain call data records as well as intercept audioin an Interconnect phone call for court authorized monitoring. This is part

of the Call Intercept System (CIS).

Dispatch Dispatch calls are voice communications that use the half-duplex Push-To-

Talk (PTT) form of communication. This type of call does not use other

provider networks except as transport facilities.

The major components of the Dispatch subsystem are as follows:

High Availability Dispatch Application Processor (HA-DAP)—The HA-

DAP is responsible for the overall control and coordination of Dispatch andPacket Data services.

iDEN Home Location Register (HA-iHLR)—The HA-iHLR database for

Dispatch and Packet Data services.

Network Dispatch Messenger (NDM)—The NDM allows a direct

connection between your PC and the iDEN phone. (optional)

Enhanced Global Title Translation Table Tool (EGT4)—The EGT4 is a

centrally located workstation. It provides the following information to all

HA-DAPs and HA-iHLRs in the network:

International Mobile Station Identifier (IMSI) ranges associated with a

particular HA-iHLR

IP addresses of all HA-iHLRs and D-VLRs

iDEN Surveillance Gateway (iSG)—The iSG provides law enforcement

surveillance capability for the iDEN Dispatch and Packet Data subsystems.



38/338




1-8 6871000P02-B 05-Sept-08

Packet Data Packet Data (PD) in iDEN is a non-voice communication interface that

connects the SU directly with the Intranet, Internet, Virtual Private Network

(VPN), and the Extranet. Packet Data networking allows the service provider

to become a point-of-presence for mobile users on the Internet.

The major components of the Packet Data subsystem are as follows:

Mobile Data Gateway (MDG)—The MDG interface to the Internet. It also

converts the iDEN protocol to the Internet Protocol and vice versa. The

MDG also functions as the Foreign Agent (FA).

Home Agent (HA)—The HA routes packets from the Internet to the correct

MDG for delivery to the SU.

Billing Accumulator (BA)—The main functions of the BA are as follows:

Collect and store billing records that are produced by the MDG.

Provide an avenue for the stored billing records to be transferred to an

outside billing center There are two BAs in the Packet Data system. One

is the primary and one is the secondary. Authentication, Authorization, and Accounting (AAA) Server—The AAA

Server is a carrier provided network element that is used for Packet Data

Mobile IP authentication. The job of the AAA Server is to provide the

following:

Subscriber authentication—Verifies and identifies the SU.

Subscriber authorization—SU level of service (what it can and cannot

do).

Subscriber accounting—Tracks services, session times, etc.

NetworkManagement

The Next Generation OMC-R (NGO) is the network management subsystem

that establishes, maintains, collects information about the network, and

presents it to the system operator. This data is used primarily to support the

daily operation of the network radio system elements and to provide the

system operator with valid information for future planning decisions.

The major components of the NGO subsystem are as follows:

OMC-R—establishes, maintains, collects information about the network,

and presents it to the system operator.

Backup Server —provides automated tape backups for the urban. Only one

backup server is supported per urban.

E0 LAN—supports tape backup activities.



39/338


40/338

iDEN System Overview


2-2 6871000P02-B 05-Sept-08

Call and Data Services for Subscribers and Users 2

The iDEN system provides many services for its subscribers and users. It

provides these services through three main services: Interconnect, Dispatch,

and Packet Data.

Interconnect provides basic mobile-mobile, land-mobile, mobile-land, aswell as supplementary and adjunct services, such as call forwarding, call

waiting, voice mail, and caller ID.

Dispatch provides private call, talk group call, horizontal networking, and

data services, such as SMS, and dial-up laptop.

Packet Data (including WiDEN) provides mobile IP services such as

Internet enabled phones.

Delivery Features for Service Providers 2

Over-the-Air-Programming

The information needed to define an SUs operating parameters is sent to the

SU by the system using the over-the-air, Radio Link Protocol (RLP).

Other optional data (user convenience options) must be programmed by the

user or service technician with the SU keypad or with a Radio Service

Software (RSS) programmer. The method of programming depends on the

model of the SU. The RSS programmer can also be used to upgrade the SU

operating software version or to modify the Control Channel Band Map.

Initial Registration Before an SU can obtain service, it must be activated and registered in the

system. Service activation requires that International Mobile EquipmentIdentifier (SIM ID), basic device parameters, and the services definition be

entered in the Home Location Register (HLR) on the home Mobile Switching

Center (MSC), and a home DAP. The data entry requirements are shown in

Figure 2-1 below.

Figure 2-1 Initial SU System Contact

i



41/338



05-Sept-08 6871000P02-B 2-3

Call Monitoring/Surveillance

The iDEN system is in compliance with the Communications Assistance for

Law Enforcement Act (CALEA). Through Interconnect and Dispatch calls,

law enforcement agencies can monitor the communications of a selectedSU(s).

Note Before a carrier can begin call surveillance, a warrant must be presented. The warrant authorizes a Law Enforcement Agency (LEA)

to conduct wiretap surveillance on a particular individual or group of

individuals.

Billing The Billing and Administration equipment is supplied by the customer.

Business operations are solely the responsibility of the service provider. The

iDEN system supplies usage and performance data for business operations

and decision support.Note The policies, procedures, and mechanisms for the exchange of data,

administrative, and operational control of the billing information is

the responsibility of the service provider.

HorizontalNetworking

Horizontal Networking (HN) in Dispatch, provides the capability for

individual Dispatch services between DAPs in a home urban area or any

urban area, and receives Private Call (PC), Call Alert (CA), and SU status.

SubscriberDatabases

The High Availability iDEN Home Location Register (HA-iHLR) provides a permanent database of all subscribers registered in the system. The subscriber

profile includes: the types of Dispatch calls individual subscribers are allowed

to make, the fleet assignments, talkgroup, and individual subscriber identifi-

cation numbers. The HA-iHLR also stores the subscriber databases for

wireless data services.

Interfaces forCustomer-providedAdministrative DataPlatforms

iDEN supports interfaces to a customer supplied Administrative Data Center

(ADC). The ADC is the service provider’s administrative and business

control equipment. The ADC may be used to enter/provision user information

and accepts system metrics and call records.

Encryption Supportfor Dispatch

This feature allows the Encryption of a Private Call (EPC) without a key

exchange with the system infrastructure. The Dispatch encryption feature has

various market applications; however, primary use focuses on the ability to

make a Dispatch call to another capable subscriber using a sophisticated layer

of eavesdropping protection.



42/338



2-4 6871000P02-B 05-Sept-08

Network Management Features for Network Operators 2

The iDEN system provides many features for managing the network for the

network operators. The main features are discussed here.

PerformanceManagement

The performance management function controls the collection and presen-

tation of metrics to the system operator.

On-LineConfigurationChange

The On-Line Configuration Change (OLCC) feature improves operability and

availability by significantly reducing system down time.

The OLCC feature accomplishes this by the following:

Allowing network operators to change the iDEN system configuration

while the system continues to process calls.

Providing the capability to change the iDEN radio system configurationwhile network elements are online processing calls, thereby reducing the

overall scheduled configuration change outage time for the iDEN radio

network.

Providing the mechanism to change the allocated system parameters

without re-initializing the network element off-line.

ConfigurationManagement

The iDEN configuration management monitors and controls the system and

subsystem components for state, software release, and components.

iDEN configuration management relates to the following areas: Software Load Management

Database Management

State Management

The system configuration databases of the HA-DAP, EBTS, iBSC, iHLR, and

MDG are downloaded from the OMC-R. These databases change as the

physical configuration of the network expands to accommodate growth.

IOS Import / ExportTool for Airgen

The Intelligent Optimization system (IOS) import / export tool is designed to

help the AirGen user import carrier/frequency usage information from the

currently running workspace in AirGen.



43/338


iDEN System Organization


05-Sept-08 6871000P02-B 2-5

iDEN System Organization 2

To support the growing need for emerging telecommunications services,

iDEN systems are organized into different levels or areas. These areas are

based on geographical areas of decreasing size. The areas are divided as

follows:

Global

Region

Domain

Urbans

Service Area

Location Area

Cell

Global 2

Global refers to the worldwide, multi-provider, Public Telephone Switched

Network (PSTN). The telephone services available worldwide may be

accessed from the iDEN system using Interconnect calling. When the iDEN

system uses the PSTN (Interconnect) system, the rules and procedures of the

PSTN are used. Interconnect calling is the access to land-line systems and the

services available and emerging in the public switched environment.

Region 2

A region is a large geographic area that is usually associated with more thanone market or more than one urban area. Just as urban areas tend to be

adjacent and overlap, so do service provider coverage areas. A single service

provider supplies services by regions. A service provider may have adjacent

or overlapping markets that can be linked to provide contiguous service

across the areas. Regions are covered by Interconnect and Dispatch calling.

Domain 2

A domain is an optional logical division of a region. This is usually defined by

marketing and sales strategies as a fleet-based geographical area. The intent is

to subdivide the region into smaller areas based on expected usage patterns.

Domain 0 is a system-wide domain. The default for Domain 0 is all service

areas. There can be up to 50 domains assigned per region. Each domain may

contain up to 254 service areas and represents the area of operation for a fleet

or fleets. The domain rules are as follows:

Can not split a service area.

Can cross MSO boundaries.



44/338




2-6 6871000P02-B 05-Sept-08

Should be geographically contiguous and should not intertwine or overlap.

Should conform to obvious geographic - demographic borders.

Should have borders in areas of zero or few subscribers.

Should make use of natural obstacles that constrain subscriber movement.

To minimize movement of subscribers between domains, domain bordersshould avoid major roads, highways, and thoroughfares. Obstacles like rivers,

mountain ranges, and diverse geographic areas separated by a lack of

contiguous RF coverage are good boundaries.

Users within a domain tend to stay within its borders. A business' fleet will

normally stay within a domain throughout the course of the work day.

Urbans 2

The iDEN system is divided up into large geographical areas known as

urbans. In most cases, an urban is centered on a large city such as New York,

Los Angeles, or Chicago. An urban can also span more than one city or more

than one state. Urbans are sometimes referred to as markets. See iDEN

Network Structure on page 2-7.

Service Area 2

A service area is Dispatch-only and is defined in provisioning by the

subscriber and user databases. A service area is a group of Dispatch Location

Areas (DLA) that define a range of operation. Multiple service areas may be

defined. Service areas may overlap. Users in a service area tend to stay within

its borders.

Location Area 2

A location area is a logical geographical area that is based on the current

location of a SU. Each SU contains Location Area Identifiers (LAIs) used by

the location area to locate the SU for paging and call setup.

Note The Interconnect location areas are usually larger than Dispatchlocation areas.

A Dispatch Location Area (DLA) is a geographic area comprised of one or

more EBTS sites that manages and tracks the most recent location of a SU.

The DLA defines the area where the Dispatch SU is currently located for paging and call setup. Since Dispatch call traffic is typically heavy, a DLA

may be smaller than a Interconnect Location Area (ILA).



45/338




05-Sept-08 6871000P02-B 2-7

Cell 2

A cell is defined as a uniquely identified coverage area whose function is

influenced by the following variables:

The environment (buildings, trees, terrain)

Antenna pattern

Tower height

The transmit power of the serving EBTS

An EBTS may be configured to support one or more cells. A site with one cell

is known as an omni-directional site. A site with two or more cells is known

as a sectored site. Sectored sites typically have three cells.

While the SU is served by a single cell at any given time, it monitors the

quality of other cells to determine when a change is required. This mobility

function is discussed further in subsequent sections of this manual.

iDEN Network Structure 2

The iDEN network has the following hierarchical structure (see Figure 2-2):

Urbans—large geographical areas, often referred to as markets.

Fleets—the broad logical group of users based on a common bond.

Talkgroups—a subset of a fleet based on the inter-relationship of users in

the fleet (managers, sales, transportation, drivers, etc.).

Subscriber Units (SU)—the radio equipment a mobile subscriber uses to

access the iDEN system.

Figure 2-2 iDEN Network Hierarchical Structure



46/338




2-8 6871000P02-B 05-Sept-08

The iDEN network is divided into Urbans, and each urban is made up of

hundreds of fleets.

Each Fleet is assigned a unique fleet ID. Each individual subscriber in the

iDEN network is a member of a fleet.

Each fleet is divided into Talkgroups. Talkgroups allow groups of users tocommunicate with multiple subscribers at the same time.



47/338


05-Sept-08 6871000P02-B 3-1

Chapter 3

iDEN Subsystem Overview

Introduction 3

This chapter describes the major subsystems in the iDEN system in terms of

their key equipment, software and databases, and function in providing

system services such as calls.



48/338


Radio Access Network


3-2 6871000P02-B 05-Sept-08

Radio Access Network 3

The Radio Access Network key component is the Enhanced Base Radio

Transceiver (EBTS). EBTS is the equipment through which the radio signal

from the subscriber gains access to the system. This is also referred to as a

site or cell site.

Figure 3-1 describes the basic Radio Access Network.

Figure 3-1 Radio Access Network Architecture

Key Network Elements 3

This section provides a brief description of the key Radio Access Network

network elements.

EBTS The EBTS consists of the control cabinets that house the components.

Control Cabinet

Power Cabinet

RF Cabinet

RFDS The Radio Frequency Distribution System (RFDS) is an 800 MHz or 900

MHz system that connects the base radios to the RF antennas. The RFDS is

part of the RF Cabinet.



49/338


Radio Access Network


05-Sept-08 6871000P02-B 3-3

IMU/EAS/EAS2 Both the iMU and EAS receive alarm signals from various EBTS site

equipment. The IMU and EAS are part of the Control Cabinet.

iSC The Integrated Site Controller (iSC) performs all control and synchronizationfunctions for the EBTS. The iSC is part of the Control Cabinet. The iSC is

sometimes referred to as an Access Controller Gateway (ACG).

BR The Base Radio (BR) is responsible for control signaling and user voice/data.

The BR is the RF interface of the EBTS site and transmits and receives in

either the 800 MHz or 900 MHz iDEN frequency bands. The BR is part of the

RF Cabinet.

Power Cabinet The power cabinet typically consists of the power supply cabinet and back-up batteries and supplies negative 48 DC voltage for powering the control and

RF cabinets and for charging the batteries.

DCS The Digital Cross Connect Switch (DCS) is a standard, programmable

telephone industry device that provides a transport system within the iDEN

network. It is the central connecting point for ALL

IDEN System Overview and Functional Description

Documents

Transcript of IDEN System Overview and Functional Description