iDEN Call Procedure

Technical Manual iDEN System Overview and Functional Description 6871000P02-A 05-Oct-07 SR 16.0 SYSTEM LEVEL INFORMATION 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 3rd Party supplied SW certain exclusive rights for copyrighted computer programs, 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 of Motorola, 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. 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, arising out 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. © 2007 - 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. Table of Contents List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -ix List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xiii List of Changed Pages - - - - - - - - - - - - - - - - - - - - - - - - - - -xv About this manual... Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xx How to Use this Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xxi Customer Network Resolution Center . . . . . . . . . . . . . . . . . -xxii Related Manuals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xxiii Recommended Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xxvi Training Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xxvi Manuals On-line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xxvii Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xxviii CMM Labeling and Disclosure Table . . . . . . . . . . . . . . . . . . -xxx Revision History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xxxii Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xxxiii Chapter 1 iDEN Technology Foundation Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 iDEN System Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Subscriber Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 iDEN System Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Wireless Telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Two-way Dispatch Radio . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Network Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 iDEN Infrastructure for the MSO . . . . . . . . . . . . . . . . . . . 1-8 Chapter 2 iDEN System Overview Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Call and Data Services for Subscribers and Users . . . . 2-3 Delivery Features for Service Providers. . . . . . . . . . . . . 2-4 Network Management Features for Network Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 iDEN System Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 Global. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 SR 16.0 05-Oct-07 6871000P02-A Functional Description iii Table of Contents Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 Urbans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Service Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Location Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Chapter 3 iDEN Subsystem Overview Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Radio Access Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Key Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Links and Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 Call Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 Interconnect Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 Interconnect Architecture . . . . . . . . . . . . . . . . . . . . . . . . 3-9 Key Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10 Links and Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11 Call Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13 Dispatch Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17 Links and Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17 Call Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19 Packet Data Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23 Packet Data Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . 3-23 Key Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24 Links and Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25 Call Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26 Network Management Subsystem . . . . . . . . . . . . . . . . . . . . 3-29 Network Management Architecture. . . . . . . . . . . . . . . . 3-29 Key Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30 Databases and Applications . . . . . . . . . . . . . . . . . . . . . 3-31 Links and Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32 Network Management Flows . . . . . . . . . . . . . . . . . . . . . 3-33 Other Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35 iDEN Gateway (iGW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35 Functional Description iv 6871000P02-A SR 16.0 05-Oct-07 Table of Contents Chapter 4 New Features in SR16.0 SR16.0 Feature Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 iDEN Gateway Dispatch Roaming Registration . . . . . . . 4-2 Private Call on 900 MHz (PC) . . . . . . . . . . . . . . . . . . . . . . 4-2 Selective Dynamic Group Call on Secondary Bands (SDGC) . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Lifetime Audit Registration Renewal Required . . . . . . . 4-3 OMC Password Policy Enhancements . . . . . . . . . . . . . . 4-3 5K Sites in an Urban in Full NGD, Legacy OMC and NGO Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 OMC Display & Process Enhancements. . . . . . . . . . . . . 4-4 RMA (Retuning Management Application) . . . . . . . . . . . 4-4 EBTS Re-rack with Dual Band RFDS . . . . . . . . . . . . . . . 4-4 Global Positioning System Denial Response . . . . . . . . 4-5 Feature Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 Chapter 5 iDEN System Functional Description Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Network Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Green Field Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Legacy iDEN System Architecture . . . . . . . . . . . . . . . . . 5-5 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 SR 16.0 05-Oct-07 6871000P02-A Functional Description v Table of Contents Chapter 6 Radio Access Network Details Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Radio Access Network Subsystem Description . . . . . . . . . . 6-4 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 Radio Access Network Overview . . . . . . . . . . . . . . . . . . 6-4 Key Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8 Enhanced Base Transceiver System . . . . . . . . . . . . . . . . . . 6-10 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10 EBTS Hardware Description . . . . . . . . . . . . . . . . . . . . . 6-10 EBTS Software Description . . . . . . . . . . . . . . . . . . . . . . 6-19 EBTS Network Management . . . . . . . . . . . . . . . . . . . . . 6-19 Chapter 7 Interconnect Subsystem Details Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4 Interconnect Subsystem Description . . . . . . . . . . . . . . . . . . 7-5 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Interconnect Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 iBSC Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . 7-9 iBSC Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9 iBSC Hardware Description . . . . . . . . . . . . . . . . . . . . . . 7-12 iBSC Software Description . . . . . . . . . . . . . . . . . . . . . . 7-22 iBSC Network Management . . . . . . . . . . . . . . . . . . . . . . 7-23 Mobile Switching Center Functional Description . . . . . . . . 7-26 MSC Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26 MSC Hardware Description . . . . . . . . . . . . . . . . . . . . . . 7-28 MSC Software Description . . . . . . . . . . . . . . . . . . . . . . . 7-30 MSC Network Management . . . . . . . . . . . . . . . . . . . . . . 7-30 Mobile Location Center Functional Description . . . . . . . . . 7-31 MLC Hardware Description . . . . . . . . . . . . . . . . . . . . . . 7-31 MLC Software Description . . . . . . . . . . . . . . . . . . . . . . . 7-31 MLC Network Management . . . . . . . . . . . . . . . . . . . . . . 7-32 Interworking Function (IWF) . . . . . . . . . . . . . . . . . . . . . . . . . 7-33 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33 IWF Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33 IWF Hardware Description . . . . . . . . . . . . . . . . . . . . . . . 7-34 IWF Software Description . . . . . . . . . . . . . . . . . . . . . . . 7-36 Functional Description vi 6871000P02-A SR 16.0 05-Oct-07 . . . . . . . 8-34 Software Description 39 iVPU Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6 Next Generation for Dispatch . . . . . . . 8-44 HA-iHLR Features . . . . . . . . . . . . . . . . .Table of Contents IWF Network Management . . . . . . . . . . . . . . . 8-7 Final NGD Implementation . . . . . . . . . . . . . . . . . . . . . 8-8 DAP Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18 HA-DAP Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22 HA-DAP Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39 Rolling Software Upgrade . . . . 8-16 DAP Enhancements . . . . 7-39 Chapter 8 Dispatch Subsystem Details Purpose. . . . . . . . . . 8-10 Dispatch Subscriber Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11 DAP Feature . 8-48 HA-iHLR NGD Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31 HA Services Layer . . . . . . . . . . . . . . 8-16 Core Architectural Models . . . . . . . . . . . . . 7-39 SDM/FT Network Management . . . . . . . 7-38 SDM/FT Software Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-53 APD Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . 8-49 HA-iHLR Database ASCII Dump . . . . . . . . . . . . . . . . 8-50 iDAC Functional Description . . .0 05-Oct-07 6871000P02-A Functional Description vii . . . 8-39 iVPU Enhancements . . . . . . . . . . . . . . . 8-68 SR 16. . . . . . . . . . . . . . . 8-26 HA-DAP NGD Enhancements . . . . . . . . . . . . . . . . 7-37 SDM/FT Hardware Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58 iSG Functional Description. 7-37 SDM/FT Overview . . . . . . 7-36 SuperNode Data Manager/Fault Tolerant (SDM/FT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32 iVPU Functional Description. . . . . . . . . . . . . 8-62 MPS Functional Description . . . . . . . . . . . . . 8-42 HA-iHLR Functional Description . 8-28 Database Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24 BA Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7 MDG2 Software Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 Packet Data Overview . 9-3 Packet Data Subsystem Description . . 9-11 Mobile Data Gateway 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19 MDG4 Network Management . . . . . . . . . . . . . . 9-14 MDG4 Overview . . . . . . . . . . . . . . . . . . . . . . . . . .0 05-Oct-07 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 Mobile Data Gateway 2 . . . . . . . . . . 10-3 OMC-R Functional Description. . 9-6 MDG2 Overview . . . . . . 9-25 BA Software Description . . . 10-20 Cisco WAN Manager Functional Description . . . . . . . 9-14 MDG4 Hardware Description . . . . . . 9-4 Introduction . . . 10-23 Functional Description viii 6871000P02-A SR 16. . . . 10-4 NGO Functional Description. . . . . . . . . . . . . . . . . 9-6 MDG2 Hardware Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13 EGT4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Table of Contents Chapter 9 Packet Data Subsystem Details Purpose. . . . . . . . 9-29 Chapter 10 Network Management Subsystem Details Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24 BA Hardware Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11 MDG2 Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16 MDG4 Software Description. . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28 BA Network Management. . . . . 9-20 Billing Accumulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-16 SR 16. . . . 11-4 NDM Functional Description. . . . . . . .0 05-Oct-07 6871000P02-A Functional Description ix . . . 11-16 NDM BU Admin Web Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10 DM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3 iGW Functional Description . . . . . . . . . . . . . . . . . . . . . 11-14 ASP EM . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Table of Contents Chapter 11 Other Network Elements Purpose. . . . . 11-16 NDM PWI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table of Contents NOTES.0 05-Oct-07 ... Functional Description x 6871000P02-A SR 16. .............. 3-33 iCP Status Information Flow (Report).............. 6-17 Cavity Combining RFDS .................................................................... 4-5 iDEN System Architecture....................0 05-Oct-07 6871000P02-A Functional Description ix .................................... 6-17 NGD System ........ 2-9 Radio Access Network Architecture ............................. 3-27 Network Management (NGO) Architecture .................................0 Interconnect Architecture .......................................................................................... 3-29 iCP Status Information Flow (Collection)........................... 3-14 Interconnect Connecting Voice Process View (Steps 16-19)................. 5-22 Mobile Originated Interconnect Call Setup Step Diagram........................................................................................................................ 6-11 Radio Frequency Cabinet....................................... 3-39 Single EBTS Rack...........................List of Figures Figure 1-1 Figure 2-1 Figure 2-2 Figure 3-1 Figure 3-2 Figure 3-3 Figure 3-4 Figure 3-5 Figure 3-6 Figure 3-7 Figure 3-8 Figure 3-9 Figure 3-10 Figure 3-11 Figure 3-12 Figure 3-13 Figure 3-14 Figure 3-15 Figure 3-16 Figure 3-17 Figure 4-1 Figure 5-1 Figure 5-2 Figure 5-3 Figure 5-4 Figure 5-5 Figure 5-6 Figure 5-7 Figure 5-8 Figure 6-1 Figure 6-2 Figure 6-3 Figure 6-4 Figure 6-5 Figure 6-6 Figure 6-7 Figure 6-8 Figure 6-9 Figure 7-1 Figure 7-2 0 Simplified SR16...................................................................................................................................................................................... 6-12 iSC3 Front Panel .................................................................................................................................................. 3-14 Interconnect Call Setup Process View (Steps 9-15) ................ 2-4 iDEN Network Hierarchical Structure ........................................................................................................................................................ 5-4 Legacy iDEN System Architecture ............................................... 7-7 SR 16................................................................................................. 3-9 Interconnect Resource Request Process View (Steps 1-8) .... 3-36 SIP to S2D Call Flow (Steps 1-8) ................. 5-11 Legacy Network Protocol and Links Diagram ...................................................................................................................... 6-5 NGD Configuration ................................ 6-7 EBTS Cabinets....... 5-26 Packet Data Call Flow .................................................................................................................................................................. 3-15 Dispatch Group Call Resource Request (Steps 1-4)..................................................................................................................................... 1-8 Initial SU System Contact..................................... 7-6 Mixed Mode Configuration ..................................................................... 3-34 iGW Network Flow. 3-7 SR16................. 6-13 iSC2 ...................................................0 Components Diagram..............................................................................................................................Front and Rear Views..................................................0 Packet Data Architecture.............................................. 5-28 Radio Access Network Architecture ............................... 3-21 SR16. 3-20 Dispatch Group Call Connect Voice (Steps 11-13) . 6-6 NGD Mixed Mode Configuration ...................................................................................................................... 3-20 Dispatch Group Call Set up (Step 10) ............................................................................................. 3-23 Packet Data Call Flow Registration (Steps 1-8) ........................................................................................................................... 3-20 Dispatch Group Call Paging (Steps 5-9) ........................... 6-15 Duplex RFDS ........................................................................................................... 5-14 Radio Access Call Flow.......................... 3-5 Call Flow with Radio Access Network .................................................... 5-24 Typical Dispatch Call Summary ............. 5-5 Network Protocol and Links Diagram ..................................................... 9-8 Actual MDG2.................................................................................................................................................... 8-7 Mixed Mode Stage Two................................. 8-55 iDEN Dispatch Access Controller .................................................................... 8-8 Next Generation Dispatch Network .................................................................................................................................................... 8-26 iVPU Front and Rear Cabinet....................................................................Front View ........... 7-34 IWF Front View.............. 8-8 R10K DAP Cabinet............................................................................................... 7-19 iVPU Rear Cage........................................................................................................................................... 7-18 iVPU Front Cage ....................... 8-37 HA-iHLR Front and Rear Cabinet............................................................................................................................................ 7-8 iBSC in the iDEN Network........................................................................................................................ 9-18 MDG4 ............................................................................... 9-15 MDG4 Board Layout................................................. 7-35 Mixed Mode Stage One........................................................ 9-5 MDG2 ............................. 7-11 iBSC Coverage...................................... 8-65 MPS Cabinet Lineup .. 7-10 iBSC Architecture ...................... 9-19 MGD4 User Interface Menu .................................................................................................................................. 7-13 iCP Frame Layout ..............................Front View........................... 7-27 MSC Components ......................... 8-24 RX7620 Server-Front Panel ............................................................................................................................. 7-22 MSC in the Interconnect Subsystem ..........................................Front View .........................Front View............................................................................ 10-6 Functional Description x 6871000P02-A SR 16....................... 8-56 Advanced Packet Duplicator ...................................................................................Front View.................................................................................................................List of Figures Figure 7-3 Figure 7-4 Figure 7-5 Figure 7-6 Figure 7-7 Figure 7-8 Figure 7-9 Figure 7-10 Figure 7-11 Figure 7-12 Figure 7-13 Figure 7-14 Figure 7-15 Figure 7-16 Figure 7-17 Figure 7-18 Figure 7-19 Figure 8-1 Figure 8-2 Figure 8-3 Figure 8-4 Figure 8-5 Figure 8-6 Figure 8-7 Figure 8-8 Figure 8-9 Figure 8-10 Figure 8-11 Figure 8-12 Figure 8-13 Figure 8-14 Figure 8-15 Figure 9-1 Figure 9-2 Figure 9-3 Figure 9-4 Figure 9-5 Figure 9-6 Figure 9-7 Figure 9-8 Figure 9-9 Figure 9-10 Figure 10-1 Split Mode Configuration ................................................................................................................ 7-15 RSL Configurations ... 9-26 Back Panel of the Billing Accumulator...... 8-14 R12K DAP Cabinet........................................... 7-14 iCP I/O Shelf................................................................................................................................................................................ 7-17 iVPU Components................................................................................................... 9-27 Sun Fire 4800................. 9-21 Billing Accumulator Mirror Function.......................................Rear View .............................Actual Front View................. 8-60 iSG 1 and iSG 2 Cabinet ................ 7-11 iBSC Hardware.................................................. 7-35 IWF Back View . 8-71 NGD System ..................................................................................................................................... 8-15 HA-DAP Cabinet...................................Front View ...................................................................0 05-Oct-07 ........................................................................... 9-10 MDG4 in the iDEN Network..................................................................................................... 7-20 iBSC Links and Interfaces .............. 9-25 Billing Accumulator ......................................Front and Rear View ........................................................ 8-47 iDEN Dispatch Access Controller ............ 8-25 RX7620 Server-Back Panel ......................................................................... 7-28 Interworking Function Services ............................................................................................................................................................................................................................................................................... ................................................................................ 11-7 NDM Connectivity in the iDEN Network ................Rear View ........................................... 11-13 SR 16................................................................................. 10-9 Netra 440.........Front View......................................................0 05-Oct-07 6871000P02-A Functional Description xi .................Review View ..................... 10-8 Enterprise 3500.......................................................................... 10-15 iGW in the iDEN Network ............. 10-15 Netra 440-Rear View..................... 11-11 NDM Cabinet .........Front and Rear ...................................................Front View ........................................................................................................................ 10-7 Enterprise 3500.........................................................................Figure 10-2 Figure 10-3 Figure 10-4 Figure 10-5 Figure 10-6 Figure 11-1 Figure 11-2 Figure 11-3 Figure 11-4 Sun Fire 4800.. 11-5 iGW Cabinet Configuration. . Functional Description xii 6871000P02-A SR 16..0 05-Oct-07 .List of Figures NOTES. ....................................... xvii Related Manuals ..............................................List of Tables Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 5-1 Table 5-2 Table 5-3 Table 5-4 Table 7-1 Table 7-2 Table 7-3 Table 8-1 Table 8-2 Table 8-3 Table 8-4 Table 8-5 0 Reader’s Objectives ........................................................................................................................................................... 5-5 Key to Network Protocols and Links Diagram ............................. 8-9 Statistics Changes for BCCB 862 ................... xxvii Revision History . 7-17 iVPU Board Functions ............................................................................................ 8-30 Statistics Added for BCCB 1020 ............................. 5-12 Key to Legacy Network Protocols and Links Diagram ..................................................................................... xxix Key to iDEN System Components Diagrams .......................................................................................... 5-17 iCP Board Functions .................................................................................................................................................. 8-30 iVPU User Account Commands ............................ 8-17 Parameters Added for BCCB 1020 ................................... 7-16 Split Mode RSL Card Configuration ........................ xxii Disclosure Table....0 05-Oct-07 6871000P02-A Functional Description xiii .............................................. 8-42 SR 16.......................................................................................................................... 5-15 iDEN Protocol Documentation................................................................................................................................................................................................... xix Recommended iDEN Training................... 7-20 Mixed Mode and Final NGD Architecture NEs ...................................... xxviii Acknowledgements .................................................................. . Functional Description xiv 6871000P02-A SR 16.List of Tables NOTES.0 05-Oct-07 .. .iDEN Technology Foundation xxv 1-8 1-9 Page(s) Type of Change Updated “Related Manuals” Section Added CMM information Updated figure Replaced: “Next Generation ” With: “High Availability ” Inserted: “Application Processer ” Replaced: “NGD” With: “HA-DAP” Chapter 2 ......” Inserted: “.List of Changed Pages The table below lists new or changed information. ” Replaced: “Internetworking Operating System ” With: “Intelligent Optimization system ” 2-8 2-9 Chapter 3 .. of a technical nature. The RFDS is part . that has been added or changed since the previous release of this document.” Updated figure Inserted: “..iDEN Subsystem Overview 3-5 Replaced: “DSA” With: “DLA” Updated figure Inserted: “Control Cabinet” Inserted: “. The IMU and EAS .” Updated figure 3-6 3-7 SR 16.” Inserted: “. Chapter xix About this manual Chapter 1 . The BR is part .iDEN System Overview 2-4 Replaced: “IMEI” With: “SIM ID” Updated figure 2-6 Inserted: “iHLR..0 05-Oct-07 6871000P02-A Functional Description xv .” Deleted: “DCS to/from the .. The iSC is part . . 6-12 6-13 6-15.Interconnect Subsystem Details 7-6 thru 7-8.0 Chapter 5 . 5-26.. 611. 5-14 5-18 Deleted:“Legacy BSC Functional Description” Updated figure Functional Description xvi 6871000P02-A SR 16. 5-24. 7-28. 7-22 7-26 7-27. 7-34.” With: “controller” Inserted: “APD contains four ” 5-22. 6-6.List of Changed Pages Chapter Page(s) Type of Change Replaced: “Green Field Systems” With: “Interconnect Architecture” Deleted: “Split and Mixed Mode Systems” Updated figure Updated figure Deleted: “Green Field Systems” Replaced: “Green Field Systems” With: “Packet Data Subsystem” Replaced: “Green Field Systems” With: “Network Management Architecture” Deleted: “Split and Mixed Mode Systems” Added new feature descriptions Updated figure Updated figure Replaced: “cell ” With: “EBTS ” Replaced: “(EBTS) distribution and . 7-10 thru 7-11.Radio Access Network Details 6-5. 6-7.New Features in SR 16.iDEN System Functional Description All 5-4. 5-28 Chapter 6 .. 7-13 thru 7-15.continued 3-17 3-23 3-29 Chapter 4 .” With: “The iSC3 supports ” Updated figure Updated figure 3-9 3-14. 3-15 Chapter 3 . 5-5 5-11. 7-35 Updated figure Updated figure Replaced: “It also provides capabilities to . 6-17 Chapter 7 .0 05-Oct-07 . 7-17 thru 7-20.. ” Replaced: “Mixed Mode configuration” Deleted: “AFR is supported in both . 9-19. split backhaul. site ” Replaced: “hub ” With: “BSC port number..0 05-Oct-07 6871000P02-A Functional Description xvii .. 9-10. 8-65. 8-55.List of Changed Pages Chapter Page(s) Type of Change Updated figure Chapter 8 .. 1111.. 9-15. 8-47. 8-56. 9-18.Other Network Elements 11-5..” Replaced: “Site ” With: “BSC ” Replaced: “The OMC-R ” With: “Displays ” Replaced: “address is removed ” With: “address. or .” Deleted: “The NGD architecture supports various .Network Management Subsystem Details 10-6 thru 10-9 10-13 10-15 10-18 Updated figure Updated figure Replaced: “two ” With: “three ” Updated figure Inserted: “Displays input fields for the ” Inserted: “shelf. 8-71 Chapter 9 . 9-21. 11-17 Updated figure SR 16.” With: “card fields” Chapter 11 ... 8-60..” Updated figure 9-8. hub ” Replaced: “all sites on a BSC . 11-7. 8-37. 9-25 thru 9-27 Chapter 10 . 8-8. 8-24 thru 8-26..Dispatch Subsystem Details 8-7. ” Replaced: “card display fields are added” With: “BSC time slot number” Deleted: “EBTS screen – The X.Packet Data Subsystem Details 9-5 Deleted: “.. .List of Changed Pages NOTES. Functional Description xviii 6871000P02-A SR 16..0 05-Oct-07 . This chapter of the manual describes the manual in general terms.... About this manual. 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 SR 16.0 05-Oct-07 6871000P02-A Functional Description xix .About this manual.. .About this manual. key subsystems. Purpose Purpose The primary purpose of the iDEN System Overview and Functional Description is to provide general technical background about the iDEN system.. 0 Functional Description xx 6871000P02-A SR 16.0 05-Oct-07 . The information in the iDEN System Overview and Functional Description will expose users to the purpose and parts of the iDEN system and prepare them to locate and use additional technical information. and network elements. two key roles associated with an iDEN system. (see Audience Profile). 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. 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.0 05-Oct-07 6871000P02-A Functional Description xxi .g. e. „ 1 Service Providers are those interested in the iDEN system from a business perspective. „ SR 16... Network Operators are those involved in the front-line of an iDEN system. How to Use this Manual How to Use this Manual This manual is designed to supports reader goals for various kinds of information..0 Chapter 5 iDEN System Functional Description Chapter 6 Radio Access Network Details Chapter 7 Interconnect Subsystem Details Chapter 8 Dispatch Subsystem Details Chapter 9 Packet Data Subsystem Details Chapter 10 Network Management Subsystem Details Chapter 11 Other Network Elements Audience Profile The iDEN System Overview and Functional Description is intended for iDEN service providers and iDEN network operators. 0 Table 1 Reader’s Objectives Chapter Reader’s Goals Basic Knowledge Basic Knowledge Basic Knowledge Basic Knowledge Advanced Knowledge Advanced Knowledge Advanced Knowledge Advanced Knowledge Advanced Knowledge Advanced Knowledge Advanced Knowledge Chapter 1 iDEN Technology Foundation Chapter 2 iDEN System Overview Chapter 3 iDEN Subsystem Overview Chapter 4 New Features in SR16. Chapters 1 through 4 are designed to give the reader a simple overview of the iDEN system. The remaining chapters go into more details and specifics about the iDEN functions and components.About this manual. implementation or support. motorola. please contact the CNRC. Before performing any major changes or optimization on the system.com The CNRC can be contacted at the following telephone numbers: United States and Canada 1-800.About this manual. Functional Description xxii 6871000P02-A SR 16. Please refer to the Customer Guide to iDEN Customer Network Resolution Center (CNRC) (WP2000-003) for more information regarding: „ „ „ 1 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. Customer Network Resolution Center Customer Network Resolution Center The Customer Network Resolution Center (CNRC) is a integral part of the network support process. 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. This will allow CNRC to have the correct technical support engineers on call in case they are needed. Notify the CNRC with the nature of the change and the schedule for the change.0 05-Oct-07 ..499-6477 International 1+847-704-9800 Note Toll-free international access codes are available for many locations.. com..motorola. Related Manuals Related Manuals The following publications may be required to supplement the information contained in this manual.About this manual.. Table 2 Related Manuals Document Name OMC-R System Overview OMC-R Configuration Management User’s Guide OMC-R System Administrator Guide OMC-R Performance Management OMC-R Online Change Configuration User’s Guide OMC-R Configuration Management Parameters OMC-R Event/Alarm Management MSC Planning and Expansion Guide iDEN Packet Data Service Registration And Call Processes EGT4 Alarm Documentation EGT4 Users Manual iDEN System Technical Overview Guide to Motorola Acronyms and Terms EBTS Volume 1 System Installation and Testing EBTS Volume 2 Base Radios EBTS Volume 3 RF Distribution Systems iDEN Integrated Site Controller System Manual iDEN Gen 3 Site Controller System Manual Ethernet Analyzer Detective Software User's Manual Interconnect Troubleshooting Guide iBSC Hardware Manual BSC Troubleshooting Guide BSSC3 Hardware Change Manual 1 Part Number 68P81001Y90 68P81001Y91 68P81001Y93 68P81001Y95 68P81001Y97 68P81001Y92 68P81001Y94 68P80801A10 68P80801C90 68P81001Y54 68P81001Y53 68P81095E55 68P81131E90 68P80801E35 68P80801E35 68P80801E35 68P81098E05 68P80801E30 68P81001Y55 6881012Y80 68P81001Y77 68P80800H75 6880802F80 SR 16.0 05-Oct-07 6871000P02-A Functional Description xxiii . These references are available on the Motorola Extranet web site at http://mynetworksupport. About this manual.Tools from the MSC. Related Manuals Table 2 Related Manuals (continued) Document Name BSC MMI Commands Interconnect Troubleshooting Tools .1 MSO Timing System Part Number 6880802F05 68P81006Y39 68P80801A10 68P80801A20 68P80800E10 68P80802B05 68P80800B95 68P80801C90 68P80802D30 6881012Y82 68P81001Y76 6881001Y49 6881001Y50 68P81001Y83 68P81001Y84 68P81001Y52 6881001Y51 68P80801H50 68P80801H55 68P80800C45 68P81131E11 6881012Y17 68P80802A85 WP04003o Functional Description xxiv 6871000P02-A SR 16. BSC & SMS MSC Planning and Expansion Guide MSC Optimization IWF Installation Manual IWF System Release Implementation Manual MDG System Manual SR12.0 iDEN Packet Data Service –Registration and Call Processes MDG Command Reference Packet Data Subsystem Troubleshooting Guide MDG4 Hardware Installation Manual DAP User Guide DAP Hardware Installation Manual HA Dispatch Application Processor (HA-DAP) User Manual HA-DAP Hardware Installation Manual iHLR User Manual iHLR Hardware Installation Manual iDEN CPX1205 Common Platform Hardware Reference Manual iDEN Dispatch Access Controller Application Manual iDEN Advanced Packet Duplicator Installation Manual CPX Common Platform Hardware Reference Manual iDEN Surveillance Gateway (iSG) Application Manual GR Implementation Manual System Release MPS5...0 05-Oct-07 . Related Manuals Table 2 Related Manuals (continued) Document Name EBTS Backhaul: Frame Relay DSO Requirements Initial RF Design Guidelines .0 IVPUdi BPP2 Resource Management MPS and CWM Health Checks SR14.0 Packet Data Health Check iBSC Health Check SR16.0 iDEN Alarm and State Change Event Reference Manual Part Number WP2002-025 WP2003-009 WP05008B WP2003-014 WP2001-010 WP2002-026 WP04008 WP2002-021 WP2000-002 WP2002-023 WP2003-019 WP2003-020 WP2002-022 WP06003 WP06006 HC05002 HC06006 HC06003 ASCE16 SR 16.RF Planning 900 Quad EBTS Multi-Sector Rack Configuration iDEN EBTS Fan Maintenance Plan iDEN EBTS Total Site Maintenance Inbound Handover Threshold Optimization Legacy BSC to iBSC Reference Guide Understanding iDEN System Fault Tolerance Interconnect Subsystem Overview of iDEN Packet Data RF Operation and Performance Understanding iDEN System Fault Tolerance – Packet Data Subsystem Packet Data Troubleshooting Equipment List for 64K MDG Remote Access to 64K MDG MMI Understanding iDEN System Fault Tolerance Dispatch Subsystem iVPUd Management of BPP2 Resources SR14.0 05-Oct-07 6871000P02-A Functional Description xxv ...About this manual. it is recommended that you complete the following Motorola-offered training courses.. click on iDEN Training Catalog. On the right side of the page. Training Access To access the iDEN Technical Training Course Catalog on MyNetworkSupport. 3 Step 1 2 3 Functional Description xxvi 6871000P02-A SR 16.0 OMC System Administration Course iDEN System Recovery Topics Course iBSC Operations & Maintenance 2 Course Number GEN101 GEN102 GEN103 FND106 SRL316 OPM202 ADV401 OPM214 Contact your local training coordinator for course enrollment information.About this manual.0 05-Oct-07 . Scroll down to the section for iDEN technology. TO Access the iDEN Technical Training Course Catalog Action Login to MyNetworkSupport at: https://mynetworksupport.com/ The MyQuickLinks screen appears. follow the steps below.. Table 3 Recommended iDEN Training Description iDEN Overview iDEN System School iDEN System Overview OMC Fundamentals Course An Introduction to System Release 16. Recommended Training Recommended Training To further enhance your understanding of the iDEN system.motorola. and any comments you may have regarding what you have found. the iDEN customer site. the complete manual title and part number.com 3 Be sure to include your name. Thank you for your time.. We appreciate any comments from the users of our manuals. system release documents and product manuals.0 05-Oct-07 6871000P02-A Functional Description xxvii . SR 16.About this manual.com 3 For information on obtaining an account on this site. please take the time to contact us at the following email address: tpid23@motorola. Manuals On-line Manuals On-line This manual is available on the World Wide Web at mynetworksupport.motorola. go to: https://membership. This web site features a library of iDEN Infrastructure technical documentation such as bulletins.com/motorola Reporting Manual Errors If you locate an error or identify a deficiency in this manual. the page number where the error is located. This site was created to provide secure access to critical iDEN Infrastructure information.motorola.. fax or phone number. The documents are located on the secured extranet website at the URL: https://mynetworksupport. CAUTION Without the alert symbol indicates a potentially hazardous situation which. Functional Description xxviii 6871000P02-A SR 16. could result in death or serious injury. The representations are: Ì ! DANGER INDICATES AN IMMINENTLY HAZARDOUS SITUATION WHICH. Hardware „ CD-ROM Safety This manual may contain safety notices (alerts). if not avoided. Specific procedural notices are stated in the procedures as required and have specific visual representations... Ì CAUTION Indicates a potentially hazardous situation which. IF NOT AVOIDED. if not avoided. may result in property damage. Ì ! ! WARNING Indicates a potentially hazardous situation which. Alerts are based on the standards that apply to graphics on Motorola equipment. if not avoided. could result in minor or moderate injury. Return mouse clicks—click... double-click user input—Type delete screen output—DAP is starting. WILL RESULT IN DEATH OR SERIOUS INJURY. Conventions Conventions Software „ „ „ „ „ „ 3 submenu commands—Table > Table Designer new terms—mobile station keystrokes—Ctrl+Alt+Delete.0 05-Oct-07 .About this manual.. About this manual... Conventions Important Indicates an item of the essence of a topic that is indispensable. Note Indicates something of notable worth or consequence. General Safety Important Remember Safety depends on you!! General safety precautions must be observed during all phases of operation, service, and repair of the equipment described in this manual. Failure to comply with these precautions or with specific warnings 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. 3 SR 16.0 05-Oct-07 6871000P02-A Functional Description xxix About this manual... CMM Labeling and Disclosure Table 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. „ 3 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 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 fieldreplaceable 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 requirements. Functional Description xxx 6871000P02-A SR 16.0 05-Oct-07 About this manual... CMM Labeling and Disclosure Table Table 4 Disclosure Table SR 16.0 05-Oct-07 6871000P02-A Functional Description xxxi About this manual... Revision History Revision History The following table contains a list of the revisions made to this guide. Table 5 Revision History 4 Date 02/26/06 10/04/07 Issue O A Description of Changes Original Publication for SR15.0 Updated for SR16.0 Functional Description xxxii 6871000P02-A SR 16.0 05-Oct-07 About this manual... Acknowledgements Acknowledgements We recognize and thank the following contributors. Table 6 Acknowledgements Name Ann Kohut Mark Interrante Elayne Tillman Todd Mueller Carlos Carrillo Sheila Raines Gabriel Bovino John Mabbott Patti Rausch Steve Hart Gil Scovill Thomas Logsdon Bryan Blanco 5 Name SR 16.0 05-Oct-07 6871000P02-A Functional Description xxxiii About this manual... Acknowledgements NOTES... Functional Description xxxiv 6871000P02-A SR 16.0 05-Oct-07 . . .. . .. . . . . .. .. . .. .. .... .. . ... ... ..... ... . . ... .. .. . .. ... . ... . ... . . .. .. . 1-8 Interconnect .. ..... . .. . .. . . . . . ... .. .. .... ... . .. . . ..... .... 1-6 Network Infrastructure .. . .. . .... .. 1-5 Two-way Dispatch Radio .... . . ... . . . . ... ... .. . . . ... ..... . . . 1-4 iDEN System Technologies ........ . ........ ... .. ... . ... . .... . . .. . ..... ..... . ... . . ........ 1-8 Dispatch . ...... . . . .. ....... .. . 1-3 Subscriber Services .... . ... .. . ... ... . . .. . . . .. . . .. . ... . . .. . . . . ... . . .. 1-9 Network Management .. . . .... . .. ...... . .. . . 1-9 Packet Data. ... ........ . .... .. .. .. .... . . ....Chapter 1 iDEN Technology Foundation In This Chapter Topic See Page Introduction .. ...... .. .. . .. .... . ... ... .. . 1-5 Data . ....... . ... . .. .. . . . . . . ... .. ... .... 1-7 iDEN Infrastructure for the MSO . . .. ... ....... . . ... .. 1-10 SR 16..... . . ..... .. . ...... .... .. . . ... . .. .. . . . ... .. . .... . .. .. . ... . . ... .. .... . .. .... . . . . .... .. .... . .... .. ... ... .. . . .. .. ..... . . ... . . . . . .... ....0 05-Oct-07 6871000P02-A Functional Description 1-1 ............ 1-2 iDEN System Introduction... .. . 1-5 Wireless Telephony . . . while providing full-duplex functionality when required. half-duplex mode. the need to optimize Radio Frequency (RF) spectral resources and provide ever-increasing services is essential.iDEN Technology Foundation Introduction Introduction The outgrowth of the wireless communications market has produced vast opportunities to enhance and improve the communications between individuals. half-duplex.0 05-Oct-07 . iDEN allows much of the voice traffic to be run in half-duplex mode. analog radio technology. Functional Description 1-2 6871000P02-A SR 16. or can effectively operate in. some forms of data communication. that requires full-duplex operation. and structured voice communication are. Because of this growth. and feature-rich. the iDEN system capitalizes on the fact that communications can be: „ 1 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 twoway communication „ Many times communication does not require a full-duplex link. To support the increase in wireless services while making best use of available resources. Traditional telephone conversations and more intensive data links require the ability to interrupt. By utilizing both full and half-duplex operations. paging. the iDEN system is an integration of traditional Push-To-Talk (PTT). full-duplex digital cellular communications. Messaging. As part of the ongoing effort to support the outgrowth in wireless communication. This integration of mobile communication technologies provides state-of-the-art functions and benefits to mobile users while optimizing the available infrastructure resources. not Mobile Station (MS). Note SU is also referred to sometimes as Mobile Station.iDEN Technology Foundation iDEN System Introduction iDEN System Introduction 1 At the highest-level. in this manual the term SU is used. This subsection briefly describes the subscriber/user services available from the iDEN system and the network infrastructure that delivers these services. SR 16. the iDEN system is the infrastructure that is used to deliver services to mobile subscribers (MS) using a single subscriber unit (SU). For clarity purposes.0 05-Oct-07 6871000P02-A Functional Description 1-3 . allowing multiple users to share each RF channel by transmitting at different times.0 05-Oct-07 . using a single SU. iDEN uses TDMA technology which separates RF channels into time slots.iDEN Technology Foundation Subscriber Services Subscriber Services The iDEN system provides services that include: two-way radio communication. The iDEN SU continually measures signal quality to maintain strong signal reception. „ 1 The iDEN network converts analog voice to digital code for transmission over the air. cellular/wireless telephone communication. The iDEN network provides the customer with a complete solution to all of their wireless needs. „ „ Functional Description 1-4 6871000P02-A SR 16. and wireless data services. Dispatch operates in a half-duplex mode. and thus be assigned a new RF channel and time slot for transmission. or vocoding. the wave pattern is sampled at different points and a digital representation of 1s and 0s is given to the sample at each point. allowing 6 communication paths on a single RF channel. If the signal quality drops below an acceptable level. or groups of subscribers. or RF channel into 6 time slots. Through all of these features and services. 1 SR 16. 1 Wireless Telephony To convert an analog voice signal to a digital signal.iDEN Technology Foundation iDEN System Technologies iDEN System Technologies The iDEN system is a digital wireless system that uniquely combines digital mobile telephone and data technologies. which means that a subscriber can either talk or listen to another subscriber using the push-to-talk button. These techniques also compress large segments of voice into smaller segments for more efficient transmission of the voice data. The sharing of RF channels enables TDMA technology to be more efficient in its utilization of resources. to communicate quickly and easily with each other. Multiple users are assigned the same channel frequency and share the RF channel by transmitting at different times. The SU performs the conversion of analog voice into digital code using two voice encoding. The Dispatch features of the iDEN network are based on two-way trunking. which allows individual subscribers. the iDEN system provides subscribers with the latest integrated wireless communications solutions. the SU moves to a site that offers a better signal.0 05-Oct-07 6871000P02-A Functional Description 1-5 . but can not do both at the same time. TDMA divides each 25 kilohertz radio frequency. This digital representation can be stored. iDEN maintains strong signal reception by continually measuring the signal quality of the serving cell and all of the surrounding neighbor cells. 1 Two-way Dispatch Radio Dispatch offers two-way radio communication between subscribers. or transmitted without further degradation. The iDEN system uses Time Division Multiple Access (TDMA). replicated. techniques called VSELP and AMBE++. Circuit Data—Circuit data enables the subscriber to send and receive faxes and email. and to access databases.0 05-Oct-07 . Packet Data—Packet Data provides the subscriber access to Intranet and Internet applications using standard Internet Protocols. „ „ Functional Description 1-6 6871000P02-A SR 16. They are as follows: „ 1 Short Message Service (SMS)—This service is commonly referred to as text messaging.iDEN Technology Foundation iDEN System Technologies Data There are three categories of data services supported by the iDEN network. connect to online services such as a web service provider. „ „ SR 16. and if so provisioned. This type of call does not use other provider networks except as transport facilities. Packet Data networking allows the service provider to become a point-of-presence for mobile users on the Internet. access data and voice mail services. Dispatch—Dispatch calls are voice communications that use the halfduplex Push-To-Talk (PTT) form of communication. Packet Data—Packet Data in iDEN. a user can originate or receive Interconnect calls. Internet. Within this extended network. Virtual Private Network (VPN). These services and features are divided into three categories: „ 1 Interconnect—The Interconnect subsystem allows a SU to travel freely throughout an iDEN system and communicate with other subscribers and land line systems.iDEN Technology Foundation Network Infrastructure Network Infrastructure The network infrastructure of the iDEN system offers a variety of services and features that provide subscribers with the latest integrated wireless communications solutions. and the Extranet. is a non-voice communication interface that connects the SU directly with the Intranet.0 05-Oct-07 6871000P02-A Functional Description 1-7 . 0 Components Diagram 1 Note The EBTS is not part of the MSO.0 05-Oct-07 . Within this extended network. and if so provisioned. Packet Data (PD). 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. See iDEN Subsystem Overview on page 3-1 for more information for all iDEN subsystems. Interconnect The Interconnect subsystem allows a SU to travel freely throughout an iDEN system and communicate with other subscribers and land line systems. access data and voice mail services. Figure 1-1 Simplified SR16.iDEN Technology Foundation Network Infrastructure iDEN Infrastructure for the MSO There are four subsystems in the infrastructure of the Mobile Switching Office (MSO) for the iDEN system: Interconnect. These subsystem support the services and features for the iDEN system. „ „ Functional Description 1-8 6871000P02-A SR 16. Figure 1-1 displays the basic infrastructure of the iDEN system at its basic level. Dispatch. a user can originate or receive Interconnect calls. Short Message Service (SMS)—provides text message services. and Network Management Operations-Radio (NGO). Supernode Data Manager-Fault Tolerant (SDM/FT)—allows law enforcement agencies to obtain call data records as well as intercept audio in an Interconnect phone call for court authorized monitoring. This is part of the Call Intercept System (CIS). and the Extranet. The major components of the Packet Data subsystem are as follows: „ Mobile Data Gateway (MDG)—The MDG interface to the Internet. The MDG also functions as the Foreign Agent (FA). Packet Data networking allows the service provider to become a point-of-presence for mobile users on the Internet. This type of call does not use other provider networks except as transport facilities. Packet Data Packet Data (PD) in iDEN is a non-voice communication interface that connects the SU directly with the Intranet.iDEN Technology Foundation Network Infrastructure „ Voice Mail Server (VMS)—serves as an answering machine and stores messages for the SU. VMS also indicates when voice mail is present. Billing Accumulator (BA)—The main functions of the BA are as follows: Œ „ „ Collect and store billing records that are produced by the MDG.0 05-Oct-07 6871000P02-A Functional Description 1-9 . Home Agent (HA)—The HA routes packets from the Internet to the correct MDG for delivery to the SU. (optional) Enhanced Global Title Translation Table Tool (EGT4)—The EGT4 is a centrally located workstation. The major components of the Dispatch subsystem are as follows: „ High Availability Dispatch Application Processor (HA-DAP)—The HADAP is responsible for the overall control and coordination of Dispatch and Packet Data services. „ Dispatch Dispatch calls are voice communications that use the half-duplex Push-ToTalk (PTT) form of communication. Network Dispatch Messenger (NDM)—The NDM allows a direct connection between your PC and the iDEN phone. iDEN Home Location Register (HA-iHLR)—The HA-iHLR database for Dispatch and Packet Data services. Internet. It also converts the iDEN protocol to the Internet Protocol and vice versa. Virtual Private Network (VPN). 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. SR 16. and presents it to the system operator. Only one backup server is supported per urban. 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. Authorization. collects information about the network. Billing Accumulator (BA)—Collects Packet Data billing information. maintains. „ „ Functional Description 1-10 6871000P02-A SR 16. The major components of the NGO subsystem are as follows: „ OMC-R—establishes. The job of the AAA Server is to provide the following: Œ Œ Œ Œ Subscriber authentication—Verifies and identifies the SU.iDEN Technology Foundation Network Infrastructure Œ 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. Subscriber accounting—Tracks services. E0 LAN—supports tape backup activities. „ Authentication. and presents it to the system operator. maintains. Network Management The Next Generation OMC-R (NGO) is the network management subsystem that establishes. and Accounting (AAA) Server—The AAA Server is a carrier provided network element that is used for Packet Data authentication. etc. collects information about the network. Backup Server —provides automated tape backups for the urban. Subscriber authorization—SU level of service (what it can and cannot do).0 05-Oct-07 . One is the primary and one is the secondary. session times. ...... . ... .......... ... . . .... . 2-6 Configuration Management ..... ...... . . 2-7 Global.. . .. . . ....... ... . ... ..... .. .. .. .. . ... ....... .. . ... .. . . ... ... ... . . 2-5 Horizontal Networking ...... . 2-7 Domain.. .... .. . ........ 2-6 iDEN System Organization . ...... ...... .... ........ ... . . .... ... .. .... . .. . .. .. .... ........ 2-8 Location Area . . ... .. .. . .......... ............ . .. .. .... ... . .. ...... . .... . ....... ...... ... .. .. 2-5 Network Management Features for Network Operators 2-6 Performance Management. ... ..... .. ..... ..... .... .. ... .... .. ....... .... . .. . .. . ... 2-6 IOS Import / Export Tool for Airgen .. . ...... ..... ..... .. . . 2-5 Subscriber Databases . ........ .. .. . ... . . ....... .. .. ........ . . . . ... . . .. . 2-9 SR 16..... . . ... .. ....0 05-Oct-07 6871000P02-A Functional Description 2-1 .. . ..... ....... .......... . . .. . ..... ... .. . ... .. . . .. . 2-7 Region ... .... .. .. .. . . ... ....... .. . .... .. . ...... ... .... ... . .. . .... ........ ..... . ......... ......... . ...... .... ..... ..... .... .. .. ..... ...... ... ..... . .... 2-6 On-Line Configuration Change .... ..... .. ... . . ..... .. 2-4 Initial Registration...... .. .... . .. .. . . ...... . ... ... . .. . .... . .. ... . .... . . . ....... .. ........ .. . .... .... 2-8 Cell ..... . . ... 2-8 Service Area ... ... .......... . . ... ... .......... ... 2-4 Call Monitoring/Surveillance... .... .. . ......... . ... .. . ... ...Chapter 2 iDEN System Overview In This Chapter Topic See Page Introduction . .. 2-3 Call and Data Services for Subscribers and Users .. . .. ........ ... .. ... .. . . . . ... .... ..... ... ... .... . . ... . .. .. .. ... .. .. .. . ... ... . ... ..... .. 2-4 Over-the-Air-Programming ...... 2-5 Encryption Support for Dispatch. ... . .. . . . . .... . . 2-7 Urbans . .. . ........ .. .. . .... ... . . .. ....... ..... .. 2-4 Billing.. .......... ... ....... ..... .... .. . ...... ..... ... .. ... 2-5 Interfaces for Customer-provided Administrative Data Platforms . . ..... .. ... ... . . .. ... .. . . .. . . .. . ... ... ..... .. . .... 2-3 Delivery Features for Service Providers. iDEN System Overview Functional Description 2-2 6871000P02-A SR 16.0 05-Oct-07 . 0 on page 4-1 for the system features in SR16. Packet Data (including WiDEN) provides mobile IP services such as Internet enabled phones.0 05-Oct-07 6871000P02-A Functional Description 2-3 . voice mail. Those roles are as follows: „ 2 Subscriber/User—The subscribers and users of the iDEN system are those who utilize the calling services. horizontal networking. It provides these services through three main services: Interconnect. Dispatch. 2 Call and Data Services for Subscribers and Users The iDEN system provides many services for its subscribers and users. „ „ SR 16. Service Provider—The service providers of the iDEN system are the business entity responsible for generating revenue and meeting regulations and service level agreements by delivering calling services to subscribers and users. Note See New Features in SR16. talk group call. „ 2 Interconnect provides basic mobile-mobile.0. land-mobile. such as call forwarding. and Packet Data. Network Operator—The network operators of the iDEN system are the technical entity responsible for installing and operating the network infrastructure and links by which the services are provided to subscribers and users. call waiting. Dispatch provides private call. as well as supplementary and adjunct services. such as SMS. „ „ iDEN System Features The numerous features of the iDEN system can be described in terms of the roles involved in the iDEN system.) This subsection briefly describes key features of the iDEN system from the viewpoint of those three roles.iDEN System Overview Introduction Introduction This chapter introduces the features and organization of the iDEN system from the viewpoints of service providers and network operators. and data services. and caller ID. and dial-up laptop. 2 Roles in the iDEN System At the highest level. mobile-land. (See Roles in the iDEN System. there are three roles involved in the iDEN system. 2 Initial Registration Before an SU can obtain service. Note Before a carrier can begin call surveillance. 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. it must be activated and registered in the system. Through Interconnect and Dispatch calls.0 05-Oct-07 . The RSS programmer can also be used to upgrade the SU operating software version or to modify the Control Channel Band Map.iDEN System Overview Introduction Delivery Features for Service Providers Over-the-AirProgramming The information needed to define an SUs operating parameters is sent to the SU by the system using the over-the-air. The method of programming depends on the model of the SU. and a home DAP. Radio Link Protocol (RLP). basic device parameters. The warrant authorizes a Law Enforcement Agency (LEA) to conduct wiretap surveillance on a particular individual or group of individuals. Service activation requires that International Mobile Equipment Identifier (SIM ID). The data entry requirements are shown in Figure 2-1 below. a warrant must be presented. law enforcement agencies can monitor the communications of a selected SU(s). and the services definition be entered in the Home Location Register (HLR) on the home Mobile Switching Center (MSC). Functional Description 2-4 6871000P02-A SR 16. Figure 2-1 Initial SU System Contact Call Monitoring/ Surveillance The iDEN system is in compliance with the Communications Assistance for Law Enforcement Act (CALEA). procedures. the fleet assignments. administrative. Interfaces for Customer-provided Administrative Data Platforms iDEN supports interfaces to a customer supplied Administrative Data Center (ADC). primary use focuses on the ability to make a Dispatch call to another capable subscriber using a sophisticated layer of eavesdropping protection. The Dispatch encryption feature has various market applications. The ADC is the service provider’s administrative and business control equipment. talkgroup. Encryption Support for Dispatch This feature allows the Encryption of a Private Call (EPC) without a key exchange with the system infrastructure. and mechanisms for the exchange of data. and individual subscriber identification numbers. The iDEN system supplies usage and performance data for business operations and decision support. The HA-iHLR also stores the subscriber databases for wireless data services. Business operations are solely the responsibility of the service provider. SR 16. Horizontal Networking Horizontal Networking (HN) in Dispatch.0 05-Oct-07 6871000P02-A Functional Description 2-5 . and SU status. provides the capability for individual Dispatch services between DAPs in a home urban area or any urban area. Call Alert (CA). Note The policies.iDEN System Overview Introduction Billing The Billing and Administration (BA) equipment is supplied by the customer. The subscriber profile includes: the types of Dispatch calls individual subscribers are allowed to make. Subscriber Databases The High Availability iDEN Home Location Register (HA-iHLR) provides a permanent database of all subscribers registered in the system. and receives Private Call (PC). and operational control of the billing information is the responsibility of the service provider. however. The ADC may be used to enter/provision user information and accepts system metrics and call records. 2 Performance Management The performance management function controls the collection and presentation of metrics to the system operator. These databases change as the physical configuration of the network expands to accommodate growth.iDEN System Overview Introduction Network Management Features for Network Operators The iDEN system provides many features for managing the network for the network operators. The main features are discussed here. iBSC. IOS Import / Export Tool 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. iHLR. On-Line Configuration Change The On-Line Configuration Change (OLCC) feature improves operability and availability by significantly reducing system down time. Providing the mechanism to change the allocated system parameters without re-initializing the network element off-line.0 05-Oct-07 . thereby reducing the overall scheduled configuration change outage time for the iDEN radio network. and MDG are downloaded from the OMC-R. and components. The OLCC feature accomplishes this by the following: „ Allowing network operators to change the iDEN system configuration while the system continues to process calls. „ „ Configuration Management The iDEN configuration management monitors and controls the system and subsystem components for state. Providing the capability to change the iDEN radio system configuration while network elements are online processing calls. EBTS. Functional Description 2-6 6871000P02-A SR 16. software release. iDEN configuration management relates to the following areas: „ „ „ Software Load Management Database Management State Management The system configuration databases of the HA-DAP. There can be up to 50 domains assigned per region. multi-provider. Just as urban areas tend to be adjacent and overlap. The intent is to subdivide the region into smaller areas based on expected usage patterns. Can cross MSO boundaries. When the iDEN system uses the PSTN (Interconnect) system. iDEN systems are organized into different levels or areas.iDEN System Overview iDEN System Organization iDEN System Organization To support the growing need for emerging telecommunications services. 2 Domain A domain is an optional logical division of a region.0 05-Oct-07 6871000P02-A Functional Description 2-7 . Public Telephone Switched Network (PSTN). The default for Domain 0 is all service areas. A service provider may have adjacent or overlapping markets that can be linked to provide contiguous service across the areas. so do service provider coverage areas. Region A region is a large geographic area that is usually associated with more than one market or more than one urban area. A single service provider supplies services by regions. The domain rules are as follows: „ „ 2 Can not split a service area. This is usually defined by marketing and sales strategies as a fleet-based geographical area. the rules and procedures of the PSTN are used. The telephone services available worldwide may be accessed from the iDEN system using Interconnect calling. Each domain may contain up to 254 service areas and represents the area of operation for a fleet or fleets. These areas are based on geographical areas of decreasing size. SR 16. Regions are covered by Interconnect and Dispatch calling. Interconnect calling is the access to land-line systems and the services available and emerging in the public switched environment. The areas are divided as follows: „ „ „ „ „ „ „ 2 Global Region Domain Urbans Service Area Location Area Cell 2 Global Global refers to the worldwide. Domain 0 is a system-wide domain. Should conform to obvious geographic . 2 Service Area A service area is Dispatch-only and is defined in provisioning by the subscriber and user databases. highways. Since Dispatch call traffic is typically heavy.0 05-Oct-07 . and thoroughfares. Multiple service areas may be defined. Should make use of natural obstacles that constrain subscriber movement. 2 Functional Description 2-8 6871000P02-A SR 16. Los Angeles. Note The Interconnect location areas are usually larger than Dispatch location areas. A service area is a group of Dispatch Location Areas (DLA) that define a range of operation. In most cases. Urbans are sometimes referred to as markets. See iDEN Network Structure on page 2-9. 2 Location Area A location area is a logical geographical area that is based on the current location of a SU. mountain ranges. Urbans The iDEN system is divided up into large geographical areas known as urbans. An urban can also span more than one city or more than one state. Obstacles like rivers. The DLA defines the area where the Dispatch SU is currently located for paging and call setup. A business' fleet will normally stay within a domain throughout the course of the work day. Users in a service area tend to stay within its borders. or Chicago. Service areas may overlap. 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. and diverse geographic areas separated by a lack of contiguous RF coverage are good boundaries. domain borders should avoid major roads. a DLA may be smaller than a Interconnect Location Area (ILA). Each SU contains Location Area Identifiers (LAIs) used by the location area to locate the SU for paging and call setup. an urban is centered on a large city such as New York.iDEN System Overview iDEN System Organization „ „ „ „ Should be geographically contiguous and should not intertwine or overlap. Should have borders in areas of zero or few subscribers. Users within a domain tend to stay within its borders.demographic borders. To minimize movement of subscribers between domains. Subscriber Units (SU)—the radio equipment a mobile subscriber uses to access the iDEN system. A site with one cell is known as an omni-directional site.iDEN System Overview iDEN System Organization Cell A cell is defined as a uniquely identified coverage area whose function is influenced by the following variables: „ „ „ „ 2 The environment (buildings. often referred to as markets. This mobility function is discussed further in subsequent sections of this manual. While the SU is served by a single cell at any given time. Talkgroups—a subset of a fleet based on the inter-relationship of users in the fleet (managers. iDEN Network Structure The iDEN network has the following hierarchical structure (see Figure 2-2): „ „ „ 2 Urbans—large geographical areas. trees. sales. iDEN Network Hierarchical Structure „ Figure 2-2 SR 16. A site with two or more cells is known as a sectored site. drivers. etc.). terrain) Antenna pattern Tower height The transmit power of the serving EBTS An EBTS may be configured to support one or more cells. Sectored sites typically have three cells. Fleets—the broad logical group of users based on a common bond. it monitors the quality of other cells to determine when a change is required. transportation.0 05-Oct-07 6871000P02-A Functional Description 2-9 . Each individual subscriber in the iDEN network is a member of a fleet. and each urban is made up of hundreds of fleets. Each fleet is divided into Talkgroups.0 05-Oct-07 .iDEN System Overview iDEN System Organization „ The iDEN network is divided into Urbans. Each Fleet is assigned a unique fleet ID. Talkgroups allow groups of users to communicate with multiple subscribers at the same time. „ „ Functional Description 2-10 6871000P02-A SR 16. .... ........ 3-6 IMU/EAS/EAS2 ...... .. . 3-7 DCS. . ....... ................ ...... . .... .. ... . . ..0 05-Oct-07 6871000P02-A Functional Description 3-1 ........ . . 3-11 IVR ...... ..... 3-11 MLC... ... .... ........... .... .. ....... ........ 3-6 EBTS ..... . ....... . ................. .... .......... ........ ........ 3-7 Power Cabinet.. .. .... .. . ...... .. ..... ................. ... . ... ... ... 3-10 Interconnect Architecture .. ...... . ............. ....................... . ......... . . ..... . ........ .... ..................... .... ... .... . ......... .................... . ....... ... .. ......... ............ ... . .......... ... .................. . . .... ...... . .......... .................... . ........ .......... . 3-11 SMS .. . ........... ................ . 3-10 Key Network Elements ...Chapter 3 iDEN Subsystem Overview In This Chapter Topic See Page Introduction ... .......... .............. ....... .... .......................... ....... .......... . ....... .. .... .. ............ ...... 3-8 Interconnect Subsystem ........ ...................... ....................... 3-7 Links and Protocols ...... ............... .. ....... . .... .... .. ................ ............... ... ........... ... ..... .... . .......... .... ...... 3-7 EBTS .. .......................... ........................ ............................ .. ..... ..... ............. ............................... ..... .......... ....... ....... 3-6 RFDS .. ............ ................ ............ . . .... .............. .. 3-11 MSC .. ... 3-11 iBSC ..... ...... ................ .... ............ ... ... .......... .......... .. 3-7 iSC (ACG) .. 3-11 SR 16........ .... ... ...... ..... ... .... .................. ........... .. ...................................... . .... ... .......... .......... 3-11 HLR . .. ........... ....... ............................. . .. . . ...... .. ......... .. . ................. ......... . . . 3-6 Key Network Elements ... ......... ....... ........... ............ 3-8 Call Flow ....... .... . .............. . .... . ..... . ...... ..... .. ............................. ........ ... ............... ....... ................. ............... . ... 3-11 VMS .. .... ....... .. ......... .. . .. ......... . ... .......... ....... ......................... ..... .... ... ........... ... .. 3-5 Radio Access Network ......... 3-7 BR ... 3-7 DCS....... ........ ....... ................ . ... ............. ........ .... ............... ....... . . . ...... ................ .. ... ..................... ....... ... ..... . ............. ............ 3-19 EGT4 . .. 3-13 Legacy BSC ..... ...... .. . ....... ................. .... ........ ......................... .... ..... .... ............ ...... .. .0 05-Oct-07 ..... .............. .................. . .......... ... ... .. ...... ................ Authorization. 3-12 iBSC ........ . .... ... ................................ ......... ................ ....................... . .. 3-11 Links and Protocols ............ ....... 3-13 SDM/FT .................................. .. .......... ........................ ... ........ ..... .......... 3-24 Key Network Elements .. 3-24 Packet Data Subsystem ........... .............. .............. 3-20 Packet Data Subsystem ...... . ... 3-27 AAA Server .. ............. ................. ... 3-27 Call Flow ....... .................... .................... ... ............ 3-20 Call Flow .......... .... ....................... .... .................... .. .. ......... . 3-30 Functional Description 3-2 6871000P02-A SR 16.................. ................ ..... .............. .......... .............. ............ ... ............. ... ... ....... ......................... ... .. .......... 3-26 Links and Protocols .............................................. 3-26 BA ..... ............. and Accounting Server . 3-14 XCDR ............ ...... ................. .. .. . .. ....... ........ .............. ... .. ................ ........ ..... 3-27 HA ... 3-14 Dispatch Subsystem ............. ..... .. .... ........... ... .............. ................. .. ..... 3-19 HA-iHLR . ........ ..... ............ . .................... ...... ....... ..... .. ..... 3-12 iCP. ................ ....... .............. ................... ......................... .......................... .. .......... ...... ........... 3-18 Links and Protocols .... ................ ............. ......... .............. ........................ ............. 3-13 IVR ........ ........... ............................... 3-25 Mobile Data Gateway ............... ..... ............. ............................. .. ... .... ... ............ . 3-12 iVPU . .. ...... ...... ......................... ..... . .............. ............. ...... . .............. ........... ...... . .. ....... .... ... .................... .............. .... 3-13 HLR ... 3-25 Billing Accumulator. ... 3-19 APD . . .... .............. ....... 3-12 MSC .. . ............. .. .... ..................... ............ .... .... ...... ........... .... .... ... ..... .............. .... .. ....................... ........ ............. .. .. . ........ . 3-11 IWF...... .... ................ ...... ....... . .... ... .... ...... ..... ...... ......... ......... . ........ ... .......... ....... ........ ............. ... . ............... ........................ ....... .......... .......... ... ......... .............. 3-19 iSG ........ 3-25 Mobile Data Gateway 4 . ............ 3-14 CP . .... 3-14 Call Flow .. .. ............. ................ 3-19 HA-DAP. . ................... ... 3-26 MDG .. .. ......... ..... .. ......... ... .......... ...................... ... .. .......... ............. 3-26 Home Agent ................. ..... ......... .... ..... ..... ....... .................. ...... ............. ... ...... ..... ...... ......... .. ........iDEN Subsystem Overview SDM/FT ....... . ........ .............................. 3-25 Authentication. ............ ........ . ...................... 3-19 iDAC .......... ............. ...... ......... ........... ......... ............................. . ........ .. ... .......... 3-13 MLC..... ...... 3-13 Legacy IWF ......... ... 3-13 VMS ....... ........... ........... .... ................................ .. ....... . 3-27 Network Management Subsystem .. .. ... ......... ... ......... ..... .... ................ .............. ............... .. 3-18 iVPUd/iVPUdi ........ ........... ................ ........................... ..................................... ............... . .... .. .. ............... .................. .................... ... 3-30 Key Network Elements . ........ ... ....................... ......... 3-34 Status Information Collection .......... ...................................... .......... LVCP .............. 3-31 Ethernet......... 3-31 Legacy PTI Hub ........ .... ............... ....... ... ... ..... ........ 3-39 SR 16.............. ................................. ........... ........ ..................... ... 3-32 Databases and Applications ................................... ....... ............. ..... ..... .................... .................. ....... .......... 3-31 OMC-R System Processor ........ ......... .. ...... ..... .......... ............ ....... ... ............ ....... .. ........ . ...... VSGW .......... ........................ ........................ 3-36 Key Network Elements .. .... ...... ..... ........ ... ........ ... ............... ............................ .... ..... ......... .................. .................. ...... ..... RTP ..... 3-31 Sun Ray Terminals..................... 3-32 Legacy Network Access Server ......... ............... .. .............................. ............................... . 3-34 Status Information Report ............ .......... ............................. . .. ..... ......... SDGC Calls .............. .... . . 3-33 Security Management ..................... ............. ............ ... 3-33 Links and Protocols ..................... .. .................. XCDR . 3-36 Links and Protocols .................................. .... .................. 3-37 3-37 3-37 3-38 3-38 3-38 3-38 3-38 3-39 3-39 Call Flow .....25 Packet Switch...................... .... 3-31 Legacy Cisco WAN Manager ..... iGW ... ........ .............. SIP........... ........ . 3-31 Network Time Server........... .................. .... .iDEN Subsystem Overview Network Management Architecture..............0 05-Oct-07 6871000P02-A Functional Description 3-3 .......................... ..... ............. .............. 3-32 Other NGO Hardware................... .............. ........................... .... .. ............... 3-31 Legacy X....................... ........................ ..... .... ....... 3-32 Event/Alarm Management. .. ................ .............. ... ................ 3-32 Performance Management......... ........ 3-33 Network Management Flows .. . ..... .. ... ................. ..... ................... 3-35 Other Network Elements .................................. ............ .. ....... FTP....... 3-32 Configuration/Load Management .. .... ....... ..... .... .... ...................... ........... ....... SDP .. 3-32 Fault Management ................ ..... ......................... .......... ................................... ...... ..... ................. 3-36 iDEN Gateway (iGW) ......... ............................. .......... ...... ................................ ..... ............... ....... ..... . ........................... ................................... .... ....... ..... ...... ........................ 3-31 Man-Machine Interface .. ........... .......... .... ...................... software and databases. and function in providing system services such as calls. 3 Functional Description 3-4 6871000P02-A SR 16.iDEN Subsystem Overview Introduction Introduction This chapter describes the major subsystems in the iDEN system in terms of their key equipment.0 05-Oct-07 . iDEN Subsystem Overview Radio Access Network Radio Access Network The Radio Access Network key component is the Enhanced Base Radio Transceiver (EBTS). SR 16.0 05-Oct-07 6871000P02-A Functional Description 3-5 . Figure 3-1 Radio Access Network Architecture 3 Key Network Elements This section provides a brief description of the key Radio Access Network network elements. This is also referred to as a site or cell site. 3 EBTS The EBTS consists of the control cabinets that house the components. The RFDS is part of the RF Cabinet. Figure 3-1 describes the basic Radio Access Network. Œ 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. EBTS is the equipment through which the radio signal from the subscriber gains access to the system. coded voice. It is the central connecting point for ALL T1 and E1 links in the iDEN network and is used to separate the information on the T1 or E1 links and route the data to the correct network element. and data traffic. The BR is part of the RF Cabinet. EBTS to/from the DCS is via T1/E1 links using a DS0. packet and circuit data traffic. the Operations and Maintenance Link (OML). 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. 3 Links and Protocols The network elements in the Radio Access Network subsystem are connected to and communicate with each other and other iDEN network elements as described below. call control. The iSC is part of the Control Cabinet. „ Functional Description 3-6 6871000P02-A SR 16. 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. and MOBIS signaling. Ethernet 10Base2 connects the BR to the integrated Site Controller (iSC) carrying VSELP/AMBE++ traffic.0 05-Oct-07 . programmable telephone industry device that provides a transport system within the iDEN network. BR The Base Radio (BR) is responsible for control signaling and user voice/data. The IMU and EAS are part of the Control Cabinet. EBTS The EBTS links and interfaces are as follows: „ „ „ EBTS to/from the SU is via RF Carrier. iSC to/from the MSC via a T1/E1 connection to transports system information. iSC (ACG) The Integrated Site Controller (iSC) performs all control and synchronization functions for the EBTS.iDEN Subsystem Overview Radio Access Network IMU/EAS/EAS2 Both the iMU and EAS receive alarm signals from various EBTS site equipment. DCS The Digital Cross Connect Switch (DCS) is a standard. Note iDEN training classes offer additional information on call flows for the Radio Access Network system. Figure 3-2 displays the processes and related call flow steps listed in the TO Setup a Call Flow with Radio Access Network on page 3-8.0 05-Oct-07 6871000P02-A Functional Description 3-7 . EIA232 provides service access as administrative links for user interface purposes. 3 Call Flow The Radio Access Network has a role in both Interconnect and Dispatch call scenarios.iDEN Subsystem Overview Radio Access Network DCS The DCS links are as follows: „ DCS to/from the BSC/iBSC Interconnect paths and control signaling are routed from the EBTS spans to the BSC/iBSC. The high-level steps for a Mobile-to-Mobile call that are impacted by the Radio Access Network components only are provided here. Figure 3-2 Call Flow with Radio Access Network SR 16. „ „ DCS to/from the EBTS is via T1/E1 links using a DS0. Œ The originating SU sends a connect acknowledge message back to the MSC. The voice connection for the originating SU goes from the originating SU to the MSC.iDEN Subsystem Overview Radio Access Network TO Setup a Call Flow with Radio Access Network Action The originating SU to the MSC setup follows the same process as the Mobile-to-Land call with the exception of not connecting to the PSTN. b) Receipt of page prompts SU to request a channel from the EBTS. Œ At this point the MSC opens the voice channel between the PSTN and the SU. The EBTS assigns a channel that will be used to complete the call setup and to carry voice traffic. a) The SU makes a call and sends a request channel message. and conversation takes place. The voice connection for the target SU goes from the MSC to the target SU. e) MSC gives channel assignment request to BSC/iBSC which gives it to the EBTS. the MSC sends instructions to the BSC/iBSC to page the target SU. Step 1 b) EBTS assigns a channel in the cell where the SU is located. a) After a land call is initiated. c) The EBTS assigns a new channel in the cell where SU is located. The BSC/iBSC then forwards the page request to all EBTSs in the location area. 3 4 Functional Description 3-8 6871000P02-A SR 16. c) The MSC signals to the BSC/IBSC which sends the EBTS a channel assignment request (DCCH).0 05-Oct-07 . d) The EBTS assigns a channel that will be used to complete call setup and to carry voice traffic. 2 The MSC to target SU setup follows the same process as the Landto-Mobile call with the exception of not connecting from the PSTN. The EBTSs send pages for all cells in the location area identified by the VLR for the SU. d) The MSC sets up the connection to the BSC/iBSC and EBTS for voice traffic. 0. 3 Interconnect Architecture This architecture represents the Interconnect system for SR16. Figure 3-3 SR16. It makes connections between the wireless subsystem and the land telephony network and routes Interconnect calls. Within this extended network. The system tracks the SUs location and services. Using networked regions. the SU can roam into those Interconnected regions originating and receiving calls as if the SU is in its home system.0 05-Oct-07 6871000P02-A Functional Description 3-9 . Interconnect calling allows a SU to travel freely throughout an iDEN system and teamed roaming partners.0 Interconnect Architecture 3 SR 16.iDEN Subsystem Overview Interconnect Subsystem Interconnect Subsystem The Interconnect subsystem tracks the Subscriber Unit’s (SU) general location area and authorizes services. It also routes the calls. a user can originate or receive Interconnect calls. IWF The Interworking Function (IWF) provides circuit switched data services to provide wireless modem and fax data capabilities. VMS The Voice Message Service (VMS) is not iDEN-specific equipment and serves as an answering machine and stores messages for the SU. Functional Description 3-10 6871000P02-A SR 16. SDM/FT The SuperNode Data Manager/Fault Tolerant (SDM/FT). IVR The Interactive Voice Response (IVR) is not iDEN-specific equipment that allow SUs to communicate directly with a computer using recorded voice prompts and text-to-speech. MLC Mobile Location Center (MLC) is a central office platform that determines the physical location of a handset (SU) in a cellular telephone network. HLR The Home Location Register (HLR) is the location (database) where the SU permanent subscriber records are stored. also known as SDM.0 05-Oct-07 . manages data formatting and provides a point of access to the switch.iDEN Subsystem Overview Interconnect Subsystem Key Network Elements The key Interconnect subsystem network elements are described here. 3 iBSC The iDEN Base Site Controller (iBSC) performs call processing. customer provisioning. allowing Interconnect surveillance. and routes Interconnect packets between the EBTS and the MSC via the iDEN Call Processor (iCP) and iDEN Vocoder (iVPU) MSC The Mobile Switching Center (MSC) is a Nortel DMS100 switch that determines Interconnect services and location information and also controls and routes the calls to other providers. operations and maintenance. SMS The Short Message Service provides text messaging services for short messages (up to 140 characters in length) to the SU. indicating when voice mail is present. including the legacy network elements. and billing. Coded voice to and from the radios and PCM to and from the switch is sent over wire from the radios and over fiber to the MSC. Links for the iBSC and Legacy BSC are essentially the same. „ SR 16. iBSC The links for the iBSC are dependent on the component. „ „ „ 3 MOBIS is used for call set-up and tear down to and from the radios. The specific links are as follows: iCP „ iCP to/from the EBTS via DCS is on T1/E1 links carrying MOBIS and SNMP channels. iCP to/from the MSC is via T1/E1 links using SS7 signaling. SS7 is used for call set-up and tear down to and from the switch and PSTN. Links between the call processors and voice processors support control and maintenance functions that are carried over wire or are delivered in packets on a LAN. „ iVPU „ „ iVPUi to/from the MSC is via OC3 using SS7. iVPUi to /from the EBTS via DCS is on OC3 links using SNMP and MOBIS channels. An Ethernet (Internet Protocol) supports control and maintenance functions that are carried over wire or delivered on a LAN. SNMP is used for operational management to and from the EBTS sites and the OMC-R.iDEN Subsystem Overview Interconnect Subsystem Links and Protocols The network elements in the Interconnect subsystem are connected to and communicate with each other and other iDEN network elements as described below. „ „ Additional interface information is provided below.0 05-Oct-07 6871000P02-A Functional Description 3-11 . An Ethernet connection supports IWF to/from the MSC.0 05-Oct-07 . SDM/FT The SDM/FT links are as follows: „ „ SDM/FT to/from the MSC is via a DS512.35 using SS7 signaling. VMS The VMS links are as follows: „ „ VMS to/from the MSC is via V. HLR The HLR is connected to the MSC via a V. billing. MSC to/from SMS and HLR is via V. EIA232 provides service access. VMS to/from the SMS is via an ethernet link using a TCP/IP SMPP connection. Functional Description 3-12 6871000P02-A SR 16. Legacy IWF The legacy IWF links are as follows: „ „ „ IWF from the MSC is via T1/E1 using serial data.35 link using SS7 signaling. EIA232 provides Service Access. Ethernet (Internet Protocol) provides input/output of customer provisioning. „ „ „ „ MLC The MLC is connected to the MSC using an SS7 connection. MSC to/from the PSTN is via T1/E1 using PCM or OC3.iDEN Subsystem Overview Interconnect Subsystem MSC The MSC links are as follows: „ MSC to/from the BSC via the DCS uses T1/E1 connected by PCM voice on wire or OC3. „ IVR The IVR is connected to the MSC via PCM voice. SDM/FT to/from the Call Intercept Provisioning Center (CIPC) and Law Enforcement Monitor (LEM) is via an ethernet link to set up the MSC for surveillance. EIA232 provides service access. surveillance and set-up of IWF for circuit data.35 using SS7 signaling. 3 Call Flow A typical Interconnect Mobile-to-Land call is comprised of three processes. They are as follows: „ „ „ Resource Request Call Setup Connecting Voice The iDEN training classes offer additional information on call flows for the Interconnect system. Note The following figures display the processes and related call flow steps listed in the TO Setup the Interconnect Call on page 3-15 table.25.iDEN Subsystem Overview Interconnect Subsystem Legacy BSC The links for the Legacy BSC are dependent on the component. „ „ XCDR „ „ BSC-XCDR to/from the MSC is via T1/E1 carrying user voice (PCM). The specific links are as follows: CP „ BSC-CP to/from the EBTS via DCS is on T1/E1 links carrying MOBIS and SNMP channels. BSC-CP to/from the OMC-R is via T1/E1 links using X.0 05-Oct-07 6871000P02-A Functional Description 3-13 . SR 16. BSC-CP to/from the MSC is via T1/E1 links using SS7 signaling. BSC-XCDR to /from EBTS via DCS is on T1/E1 links using VSELP/ AMBE+. iDEN Subsystem Overview Interconnect Subsystem Figure 3-4 Interconnect Resource Request Process View (Steps 1-8) Figure 3-5 Interconnect Call Setup Process View (Steps 9-15) Functional Description 3-14 6871000P02-A SR 16.0 05-Oct-07 . 0 05-Oct-07 6871000P02-A Functional Description 3-15 . Channel Assigned—EBTS assigns channel in cell where SU is located. 4 Set Mobile Busy—The MSC sets the SU to busy to prevent allocation of radio resources for other calls intended for this SU.iDEN Subsystem Overview Interconnect Subsystem Figure 3-6 Interconnect Connecting Voice Process View (Steps 16-19) TO Setup the Interconnect Call Step 1 2 3 Action Channel Request—The user initiates a call. Call Service Request— „ „ If a channel is not available. If the channel is successfully assigned. Service Accepted—If authentication is successful. Call Proceeding—The MSC sends a call proceeding message to the SU. Authentication Request—As an option. the service request containing the ID of the SU and type of service being requested is sent to the MSC. Setup Call Information—The SU sends the dialed digits (telephone number) of the target telephone to the MSC (DCCH). This message tells the SU that the MSC will not accept any further call setup information and that it is proceeding to set the call up with the information it has (DCCH). authentication takes place between the VLR and the SU. Authentication Response—The SU sends an Authentication response back to the VLR (DCCH). Access Request—The MSC looks up the current SU subscriber information in the VLR to make sure the SU is authorized for the type of service being requested. the service request is not sent and the SU user receives an alert to indicate all channels are busy. 5 6 7 8 9 10 SR 16. and for administration of supplementary services. the VLR sends a service accepted message to the SU (DCCH). and conversation takes place. The SU switches over to that channel (TCCH). Channel Assignment Complete—The EBTS assigns a channel that will be used to complete call setup and to carry voice traffic. Alerting—The MSC sends an alerting message as a ringing indication to the SU (ACCH) Answer Message—When the called party answers the phone. Channel Assignment Request—The MSC signals to the BSC/IBSC which sends to the EBTS a channel assignment request (DCCH). 14 15 16 17 18 19 Functional Description 3-16 6871000P02-A SR 16. The PSTN sends a termination success message to the MSC. Trunk. Connect—The MSC sends a connect message to the SU. Send Outgoing Call Information—The MSC seizes a trunk and sends the outgoing call information to the PSTN as an Initial Address Message (IAM). Connect Acknowledge—The SU sends a connect acknowledge message to the MSC (ACCH). This whole process should take place in 1 to 5 seconds (TCH). Termination Success Message—The PSTN completes the connection to the called phone and causes it to ring. the PSTN sends an answer message to the MSC. Conversation—The MSC opens the voice channel between the PSTN and the SU.0 05-Oct-07 .iDEN Subsystem Overview Interconnect Subsystem TO Setup the Interconnect Call (continued) Step 11 12 13 Action Seize. indicating the connection is complete (ACCH). The protocols and links in the Dispatch subsystem are as follows: „ 3 Hyper Text Transfer Protocol Secure (HTTPS). and User Datagram Protocol (UPD) port number. and the SDP offer. switching. The transcoders convert 3G Voice Over IP (VoIP) packets to VSELP or AMBE++. the Virtual Router Redundancy Protocol (VRRP) is required to support high availability on the iVPU. Additional interface information for the network elements is provided below. and the signaling needed for Dispatch call set up and control. SR 16. and convert Real Time Transport Protocol (RTP) to the iDEN version of RTP (iRTP). The Dispatch subsystem elements provide wireline transmission. complete with a virtual IP address and a virtual MAC address. „ Session Description Protocol (SDP) The iGW supports Selective Dynamic Group Calls (SDGC) between a 3G network and the iDEN network. 3 Links and Protocols The network elements in the Dispatch subsystem are connected to and communicate with each other and other iDEN network elements as described below. and sends a page request to the appropriate DAP when a Session Initiation Protocol (SIP) invite request is received. call processing. „ „ Hot Standby Router Protocol (HSRP) Hot Standby Routing Protocol (HSRP) offers a failover mechanism for pairs of routers within a LAN. Since static routes are utilized. The Voice Signaling Gateway (VSGW) converts 3G SIP signaling messages to iDEN proprietary signaling. The invite includes the group identifier or group list.iDEN Subsystem Overview Dispatch Subsystem Dispatch Subsystem The Dispatch subsystem is the group of network elements and links that are actively involved in providing two-way Dispatch services. HSRP introduces the idea of a virtual router.0 05-Oct-07 6871000P02-A Functional Description 3-17 . and Secure FTP Virtual Router Redundancy Protocol (VRRP) With the NGD architecture. static routes are used instead of OSPF. The SDP offer includes call details such as vocoder. Secure Shell. to reduce and simplify the configuration requirements. Described in RFC 2281. Functional Description 3-18 6871000P02-A SR 16. it has several interface types: „ Frame Relay – indirect connections. and the DAPs. An RS-232 connection is the service access point between the LMT and the iDAC. the provisioning client. „ EGT4 The EGT4 connects to the central LAN by ethernet. APD High Speed Serial Interface (HSSI) provides communication of VSELP and AMBE++ to and from the MPS. The two Ethernet links support communication from each of the nodes to the Central LAN. iDAC The HSSI link brings the coded voice from the MPS to the iDAC for interurban routing of voice. External communications are supported by two types of links: „ The EIA-232 interface is used to communicate Man-Machine Interface (MMI) commands to and from the Local Maintenance Terminal (LMT).0 05-Oct-07 . via the MPS to: Œ Œ Œ Œ EBTS sites (via the DCS using T1/E1) APDs (High Speed Serial Interface – HSSI) iDAC (High Speed Serial Interface – HSSI) MPS (V.iDEN Subsystem Overview Dispatch Subsystem iVPUd/iVPUdi The iVPUd and iVPUdi connect to the following: „ „ „ DCS by AFR and AMBE DACS by OC3 LAN by OML HA-DAP Since the DAP is the Dispatch and Packet Data call manager/router. the HA-iHLR communicates between 2 nodes across a private dedicated LAN.35) OMC-R iHLR „ Ethernet (Internet Protocol) Œ Œ HA-iHLR Internally. The iHLR communicates via the Central LAN with the OMC-R. The EIA-232 interface is used for communication iDAC to and from the LMT. The iDEN training classes offer additional information on all call flows for the Dispatch system. The iSG reports alarms. A typical Dispatch call is comprised of the following three processes: „ „ „ 3 Establish radio link Route digital voice packets Duplicate packets There are different types of Dispatch calls. the order of the call flow. The descriptions and illustrations reference the key network elements involved. The iSG uses ethernet from the SPA to set up the DAP for surveillance. APD and MPS to deliver voice over an HSSI frame relay connection to the iSG. Note The following figures display the processes and related call flow steps listed in the TO Setup a Dispatch Group Call Procedure on page 3-21 table. iSG The iSG receives its runtime software from the OMC via a 10BaseT ethernet interface. and statistics to the OMC over this interface. WAN and Remote iDACs. The ethernet LAN (100Base T) provides control to and from the DAPs and SNMP to the OMC-R. SR 16. Call Flow This subsection describes and illustrates a simplified view of the procedure for typical Dispatch calls. The group call is described below. and what and how the system communicates at each step (links and protocols). An additional 100BaseT ethernet interface provides a conduit for delivery of surveillance information to Law Enforcement. This allows a local maintenance terminal to be connected to the iSG to serve as a basic Man-Machine Interface (MMI) between field service personnel and the iSG. The iSG is equipped with an RS232 interface as a service access point.iDEN Subsystem Overview Dispatch Subsystem The ethernet WAN (100 Base T) passes the coded voice over the internet using either ATM or IP virtual circuits via the central LAN. state changes. as well as between the iSG and the SPA.0 05-Oct-07 6871000P02-A Functional Description 3-19 . A voice path is setup by the DAP. The 10BaseT ethernet interface also provides connectivity between the iSG and the DAP population. iDEN Subsystem Overview Dispatch Subsystem Figure 3-7 Dispatch Group Call Resource Request (Steps 1-4) Figure 3-8 Dispatch Group Call Paging (Steps 5-9) Figure 3-9 Dispatch Group Call Set up (Step 10) Functional Description 3-20 6871000P02-A SR 16.0 05-Oct-07 . Note that steps 5 and 6 may be reinitiated by the iSC for a short period of time. 3 Group Call Proceeding The iSC acknowledges back to the SU that the Group Call Request is being processed (PCCH). Group Call Page Request The HA-DAP sends a Group Call Page Request to each iSC in the location area registered as serving each SU.iDEN Subsystem Overview Dispatch Subsystem Figure 3-10 Dispatch Group Call Connect Voice (Steps 11-13) TO Setup a Dispatch Group Call Procedure Step 1 2 Action Subscriber initiates Call (PCCH). Group Call Page Response The SU responds with its Individual ID and Dispatch Group ID. 4 5 Group Call Request The iSC sends the Group Call Request Information to the HA-DAP. Group Call Request The SU sends a Group Call Request to the iSC containing the Individual ID. 6 7 Group Call Page Request The iSC passes on the request to the SU (PCCH). SR 16. the Dispatch Group ID and the Service Area Identification (PCCH). but not for the entire duration of the call.0 05-Oct-07 6871000P02-A Functional Description 3-21 . Thus an SU could miss a call if it is in a coverage null for an extended period of time. This message passes the Global Call ID assigned to the service request to the iSC. 12 Group Call Grant The iSC sends a Group Call Grant message to the SU.0 05-Oct-07 . This has the effect of setting the SU in a Busy condition with respect to subsequent service requests (PCCH). and the VSELP voice packet. „ Frame relay packets inbound to the MSO from the originating iSC contain the frame relay address of the packet duplicator handling the call. setting up the call on a traffic channel (PCCH). 11 Group Call Start The HA-DAP sends a Group Call Start Notification to each iSC serving the call. and the VSELP voice packet. the Global Call ID.iDEN Subsystem Overview Dispatch Subsystem TO Setup a Dispatch Group Call Procedure (continued) Step 8 Action Group Call Proceeding The iSC sends a Group Call Proceeding message to the SU. „ Functional Description 3-22 6871000P02-A SR 16. 10 Add Configuration The HA-DAP sets up the call and sends a message to the iVPU to establish the routing table for the call. the Global Call ID. indicating that the SU is present and that traffic resources are available and assigned. 9 Group Call Page Response Information The iSC forwards the Group Call Page Response Information to the HADAP. as follows (TCH). 13 Voice SU units set up in the group call are now ready to exchange digital voice information. Frame relay packets outbound to the iSCs from the iVPU contain the frame relay address of the serving iSC. The Packet Data subsystem allows a carrier to supply their subscribers Internet Protocol (IP)-based network access to either the Internet or their own networks. and shows how they interact during typical Packet Data calls. databases.0 Packet Data Architecture 3 SR 16. The iDEN Packet Data subsystem is a data-internetworking network that is integrated with the existing wireless iDEN System. They accomplish this through a microbrowser embedded in their SU. 3 Packet Data Subsystem The following diagram represents the architecture of the Packet Data subsystem. It is designed to enable computers that currently exchange data through wired networks to exchange data via the wireless Radio Frequency (RF) medium. and protocols in the Packet Data subsystem. Figure 3-11 SR16.0 05-Oct-07 6871000P02-A Functional Description 3-23 . links.iDEN Subsystem Overview Packet Data Subsystem Packet Data Subsystem This subsection introduces the key network elements. or through a standard serial port interface utilizing the dial-up networking feature and the TCP/IP protocol function found in most computer operating systems. applications. 0 05-Oct-07 . The MDG2 supports 5000 Packet Data subscribers. MDG Cluster Management is a new concept in the MDG4 architecture that replaces the AFRP in the MDG2 architecture. Functional Description 3-24 6871000P02-A SR 16. This process has been replaced in the MDG4 (see the next section below). The MDG generates billing records for provided Packet Data service and sends them to the Billing Accumulator (BA). and 600K subscribers. The MDG can be visualized as the new local address of the SU on a foreign link.0) to replace the MDG2. toward their final destination. The MDG4 supports up to 600K subscribers per MDG4 node versus 5000 in the MDG2. 384K. The iHLR is a new database specifically designed for the Packet Data subsystem. Its function is to collect Packet Data subscriber usage data for billing purposes. The MDG receives operational information (datafill and downloaded on bootup) from the OMC-R and subscriber information from the iDEN Home Location Register (iHLR) from the DAP. 3 Mobile Data Gateway The Mobile Data Gateway (MDG) is the centerpiece element of the Packet Data subsystem. Mobile Data Gateway 4 The Mobile Data Gateway 4 (MDG4) was deployed in SR13. and it provides subscriber provisioning for Packet Data and is the essential element for roaming. in conjunction with the HA router. The MDG also routes packets from the SU. The Automatic Fault Recovery Process (AFRP) is a procedure used by the OMC-R to move an active Resource Allocation Group (RAG) from a failed MDG2 to a backup MDG2 to restore Packet Data service. Its primary purpose is to execute the functions of a foreign agent as specified by the mobile IP standard. The scalability of the MDG4 node also provides the ability to address four subscriber targets: 256K. Billing Accumulator The Billing Accumulator (BA) is custom-built for inclusion in the iDEN Packet Data subsystem. It works in conjunction with the Home Agent (HA) router to receive forwarded packets from its home address and distributes these packets to the MS. 512K.4 (and did not change in SR15. MDG Cluster Management is managed by a mechanism resident to the pool of MDG4 nodes within the MDG4 cluster itself without OMC-R involvement.iDEN Subsystem Overview Packet Data Subsystem Key Network Elements The key Packet Data subsystem network elements are described below. This usage data is stored on a hard drive on the BA until compilation. The BAs control the designation of which one is the primary and which one is the secondary unit. MDG The MDG communicates using two separate subnetworks: the Packet Data subnetwork and the Dispatch subnetwork. the secondary unit continues with data collection.iDEN Subsystem Overview Packet Data Subsystem The BA receives usage detail records from the MDG nodes using Billing Message Protocol (BMP) and Billing Session Protocol (BSP). Authentication.0 05-Oct-07 6871000P02-A Functional Description 3-25 . and Accounting Server The Authentication. Both BAs receive the same billing data from all MDGs (to accomplish mirroring). They are as follows: „ „ Packet Data subnetwork: IP/Ethernet Dispatch subnetwork: V. Authorization. not at the AAA Server (see the next section). If the primary BA becomes unavailable. which are proprietary protocols on top of TCP/IP.35 FR SR 16. One BA is designated as the primary unit and the other is designated as the secondary or standby. 3 Links and Protocols The network elements in the Packet Data subsystem are connected to and communicate with each other and other iDEN network elements as described below. Note The actual authentication of an SU takes place on the HA. This is accomplished using two different methods. Home Agent The Home Agent (HA) router resides on the home network of the SU and is aware of the SU home IP address. and whether it should forward the packets to the MDG. Note The BA is also referred to as the Distributed Call Measurement System (DCMS). It is used in conjunction with the HA router for SU authentication that determines whether an SU is authorized to receive Packet Data service. In conjunction with the AAA Server. The HA provides the necessary authentication procedures as outlined in the mobile IP standard. the HA provides authentication procedures that determine whether the SU is authorized to receive Packet Data service. The HA performs Mobile IP registration by intercepting and forwarding (or tunneling) packets that are destined for the SU home link to the MDG that is currently serving the MS. Authorization. and Accounting (AAA) Server is customer-provided equipment that contains security-provisioning information for subscribers to Packet Data service. 35 FR Ethernet connection through the hubs to the interface router: Œ MDG-to-both BAs: Proprietary protocols on top of IP/ethernet Œ MDG-to-Interface Router: IP/ethernet MDG-to-OMC-R: V. activate. Specifically. Packet Data registration is discussed here. Note Figure 3-5 displays the processes and related call flow steps listed in the TO Setup a Packet Data Call Flow on page 3-27 table.0 05-Oct-07 . It uses the same protocol to connect to the AAA Server. 3 Call Flow Generally speaking. the purpose of Packet Data registration is to validate. HA The HA is connected to the Public LAN via IP/Ethernet. Packet Data has several types of call flows. The iDEN training classes offer additional information on all call flows for the Packet Data system.35 FR routed through the MPS to the OMC-R MDG-to-DAP/iHLR: V. Initializes the RF link related procedures into a known state.iDEN Subsystem Overview Packet Data Subsystem The MDG physical and virtual links are as follows: „ Physical links: Œ Œ MDG-to-MPS connection: V. Packet Data registration performs the following: „ „ „ „ Assigns the SU to a Mobile Data Gateway (MDG) node. „ AAA Server The AAA Server is connected to the Public LAN via IP/Ethernet. Creates and populates a working record in the chosen MDG node.35 FR through the MPS to the DAP MDG-to-ACG: V. It uses the same protocol to connect to the HA. Functional Description 3-26 6871000P02-A SR 16.35 FR through the MPS. and out to the Access Controller Gateway (ACG) „ Virtual links: Œ Œ Œ BA The BA is connected to the Public LAN via IP/Ethernet. Each BA is connected to the HA via IP/Ethernet. Negotiates Packet Data related parameters between the SU and the MDG. „ Both BAs are connected to the MDG using proprietary protocols on top of IP/Ethernet. FR over the T1 span through the DCS. and maintain Packet Data service. iDEN Subsystem Overview Packet Data Subsystem Figure 3-12 Packet Data Call Flow Registration (Steps 1-8) TO Setup a Packet Data Call Flow Step 1 2 3 Action Successful Dispatch Registration Packet Data Registration Request The SU makes a Packet Data Registration Request to the DAP via the iSC. The DAP sends PD information to the selected MDG node. Registration Complete The SU returns complete registration to the DAP (PCCH). Backs Up Data Sent to SU The DAP backs up information sent to the SU in the registration accept for use in MDG failure recovery. SR 16. it round-robins over the available MDGs to evenly distribute the load. When the DAP chooses an MDG for a new Packet Data registration. 4 5 6 7 Packet Data Registration Response The MDG returns successful status to DAP Packet Data Registration Response The DAP returns Packet Data registration acceptance to the SU (PCCH). Packet Data Registration Request The DAP selects an MDG to serve the SU.0 05-Oct-07 6871000P02-A Functional Description 3-27 . iDEN Subsystem Overview Packet Data Subsystem TO Setup a Packet Data Call Flow (continued) Step 8 Action MDG Determines Final Parameters The MDG determines final negotiated parameters from the proposed parameters and its own capabilities. final negotiated parameters. It then creates a new subscriber working record that includes the IMSI. etc. Functional Description 3-28 6871000P02-A SR 16. For more information on Packet Data call flows. Individual ID. see Packet Data Service Registration And Call Processes (68P80801C90).0 05-Oct-07 . the need for control and monitoring equipment also increases. and collects information about the network. Figure 3-13 Network Management (NGO) Architecture SR 16. The Backup server provides automated tape backups for the urban.0 05-Oct-07 6871000P02-A Functional Description 3-29 . maintains. This data is used primarily to support the daily operation of the network radio system elements and to provide the system engineers with valid information for future planning decisions.iDEN Subsystem Overview Network Management Subsystem Network Management Subsystem The Operations and Maintenance Center-Radio (OMC-R) is the Network Management subsystem that establishes. The Network Time Server provides time of day clocking 3 Network Management Architecture This architecture represents the Network Management (NGO) system. and presents it to the system operator. The Network Management processes are as follows: „ „ „ 3 The OMC-R system operator’s interface to the iDEN network. As the complexity and control requirements of the iDEN system and its relationship to other systems increases. The Packet switch re-transmits packets on the V. Legacy X. It provides the Time-of-Day time stamps to the OMC-R equipment via a NTS Output Card.iDEN Subsystem Overview Network Management Subsystem Key Network Elements The key Network Management subsystem network elements are described below.25 Packet Switch The legacy X. 3 OMC-R System Processor OMC-R System Processor is the communication link and resource manager within the OMC-R for the following: „ „ „ „ „ Event/Alarm Management Fault Management Performance Management Configuration/Load Management Security Management The OMC-R is either an Enterprise 3500 or Sun Fire 4800.25 Packet Switch takes packets from the OMC-R Processor V. Note Man-Machine Interface Man-Machine Interface (MMI) is a Graphical User Interface (GUI) that allows you to enter commands and review alarms within the OMC-R. Ethernet Many of the network elements connect to the OMC-R via the Central LAN. Note The MMI is either a Sun Ultra 60 or Sun Netra 20. Legacy Cisco WAN Manager The legacy Cisco WAN Manager (CWM) is a graphical user interface that allows system operators to select which tool or application to launch for Metro Packet Switch (MPS) management. Network Time Server The Network Time Server (NTS) is part of the Larus BITS equipment. The Sun Ray terminal is connected to the system processor via the LAN to run various Graphical User Interface (GUI) applications.0 05-Oct-07 .35 links. The switch reads the packets' addresses and then selects the right link for the addressed network node. Functional Description 3-30 6871000P02-A SR 16.35 link outbound for addressed network nodes. Sun Ray Terminals The Sun Ray terminals allow operators to login to the OMC-R and perform network management and system maintenance tasks. iDEN Subsystem Overview Network Management Subsystem Legacy PTI Hub The legacy Performance Technology Inc. the fault management features enables an operator to do the following: „ „ Pinpoint location of the fault by remotely running diagnostics. packet switch or channel bank. (PTI) ZT5088 X.25 hub forwards traffic between the OMC-R and legacy BSCs via an integrated Ethernet switch. Performance Management Performance Management provides system operators with information necessary for efficient network management and indications of quality of service failures.0 05-Oct-07 6871000P02-A Functional Description 3-31 . NAS grooms each V. Other NGO Hardware Other NGO hardware includes the following: „ Disk array.35 signal onto a T1 DS0. frame relay hardware.35 links. and LAN gigabit Ethernet switch Routers. Isolate the fault by changing state of a device. The X. backup server (Sun Netra 240 and C4 StorEdge tape juke box). network timing hardware 3 „ Databases and Applications The OMC-R databases and applications control and monitor the following: „ „ „ „ „ Event/Alarm Management Fault Management Performance Management Configuration/Load Management Security Management Event/Alarm Management Events/Alarms are generated at a network element and sent to the OMC-R via an X. Performance Measurements are as follows: „ Traffic– Both user and signaling traffic SR 16.25 network.25 hub is needed for legacy BSCs. network access server. The operator will be informed only of those events/alarms to which a subscription has been made. Legacy Network Access Server The legacy Network Access Server (NAS) receives packets coming from the Packet Switch on many V. Fault Management If an operator is notified of system fault by event/alarm management. Service Access Œ Functional Description 3-32 6871000P02-A SR 16. this provides the ability to fine-tune the performance of the network elements. „ Ethernet (IP) . and configuration/load files Legacy BSCs. System Processor checks validity of source address and validity of user on all incoming traffic on X. and time.25: Event and Alarm and Statistics reporting. the RF frequencies of an EBTS) that are stored in the network elements’ configuration file. Users are logged off by system after a specified interval if no activity is seen. Security Management Security Management includes Network/System Security and Data security. 3 „ „ „ „ „ Links and Protocols The network elements in the Network Management subsystem are connected to and communicate with each other and other iDEN network elements as described below.OMC-R to/from the central LAN Œ For monitored and not-monitored Network Elements in Legacy. Using event/alarm and performance management information.0 05-Oct-07 . The security feature includes the following: „ Each operator has a unique user name and associated password to gain access to the system. OMC-R to/from the MDG Frame Relay: Operations and Maintenance Links to the MDGs OMC-R to/from the OMC-R X. terminal ID. All login attempts are logged by operator ID.25 network.35 Œ Œ „ EIA232 . EBTSs A high-speed Ethernet LAN is used within the network management subsystem (E0 LAN) and is optional on the rest of the LAN (E1 LAN). System administrators can add/change/remove passwords.25 Packet Switch X. Mixed Mode.iDEN Subsystem Overview Network Management Subsystem „ „ Quality of Service– Call setup delay as an example Availability– Beginning and end times of service unavailability Configuration/Load Management Configuration and Load Management is used to change any managed network elements operating parameters (for example. and Next Generation Dispatch. Operators are assigned security classes specifying what commands operators may access and what output messages can be seen. „ V. iCP forwards these messages from the site to OMC-R (SNMP using IP). including download from OMC-R to all network elements. software version control. Note The NAS and Packet Switch are not used in this process. performance monitoring. Step 1 2 3 SR 16. The two function flows in the OMC-R are as follows: „ „ 3 Status Information Collection Status Information Report Status Information Collection The describes the collection flow of status information with the iCP.iDEN Subsystem Overview Network Management Subsystem Network Management Flows This subsection describes and illustrates the processes that the network management subsystem is responsible for.0 05-Oct-07 6871000P02-A Functional Description 3-33 . configuration management. System Processor maintains status on all Network Elements. event and alarm management. Figure 3-14 iCP Status Information Flow (Collection) TO Follow the Information of the Status Flow of the iCP Action Site and MDG send status updates to System Processor. iDEN Subsystem Overview Network Management Subsystem Status Information Report The following describes the reporting flow of status information for the iBSC. Note The NAS and Packet Switch are not used in this process. Figure 3-15 iCP Status Information Flow (Report) TO Follow the Information of the Report Flow of the iCP Action Sun Ray Terminal operator requests status of network elements (System Status Display). MMI requests status information from System Processor. System Processor provides information to MMI for display. MMI formats data for display on Sun Ray Terminal. Sun Ray Terminal displays status of equipment. Step 1 2 3 4 5 Functional Description 3-34 6871000P02-A SR 16.0 05-Oct-07 iDEN Subsystem Overview Other Network Elements Other Network Elements This subsection introduces network elements that are not part of the major subsystems. 3 iDEN Gateway (iGW) This subsection introduces the function of the iGW, including the iGW hardware, links and protocols in the iDEN system, and call and data flow. The iDEN Gateway (iGW) interworks the signaling and voice packets between a 3G network and the iDEN (2G) Dispatch network. The iGW supports private Dispatch calls (Private Call and Call Alert) and Selective Dynamic Group Calls (SDGC) between a 3G network and iDEN. When a SDGC call is in progress, the iGW also performs routing and duplication for the voice packets. The Transcoder Packet Duplication (XPD) channel element performs packet duplication for iDEN controlled SDGC calls. 3 Key Network Elements The iGW is comprised of two separate pieces of equipment: „ VSGW - Voice Signaling Gateway Œ Œ Œ Œ Converts between 3G Session Initiated Protocol (SIP) signaling messages and iDEN proprietary signaling Converts the standard RTP to the iDEN RTP (iRTP), and also checks RTP packet integrity Provides protocol interworking between proprietary iDEN system and the 3G Access Networks Provides pseudo-HLR (P-iHLR) function by providing the iDEN system with the next hop route to the 3G network Transcoders interwork 3G Voice over IP (VoIP) packets and iDEN Dispatch VoIP packets Provides voice transcoding and de-jitter between the iDEN vocoders and the 3G Access Network Transcoding between VSELP and AMBE++ (on the iDEN side) to SMV, EVRC, and G.711 on the 3G side „ XCDR - Transcoder Œ Œ Œ See Figure 3-16 for information about iGW in the iDEN network. SR 16.0 05-Oct-07 6871000P02-A Functional Description 3-35 iDEN Subsystem Overview Other Network Elements Figure 3-16 iGW Network Flow Links and Protocols The network elements in the iGW subsystem are connected to and communicate with each other and other iDEN network elements as described below. iGW The iGW is linked using ethernet. The protocol used between the OMC-R is SNMP/UDP. VSGW The VSGW is linked using ethernet. The protocol used between: „ XCDR is: Œ Œ Megaco RTP/UDP „ „ Billing is FTP 3G Network is: Œ Œ SIP/UDP SIP/TCP „ „ „ HA-DAP is MAP 2G iHLR is MAP Craft WS is Telnet Functional Description 3-36 6871000P02-A SR 16.0 05-Oct-07 iDEN Subsystem Overview Other Network Elements XCDR The XCDR is linked using ethernet. The protocol used between: „ „ 3G Network is RTP/UDP Craft WS is Telnet The iGW utilizes the following protocols in a SDGC call: „ „ „ „ „ File Transfer Protocol (FTP) Link Version Control Protocol (LVCP) Real-Time Protocol (RTP) Session Initiation Protocol (SIP) Session Description Protocol (SDP) SDGC Calls The iGW utilizes the following protocols in a SDGC call: „ „ „ „ „ File Transfer Protocol (FTP) Link Version Control Protocol (LVCP) Real-Time Protocol (RTP) Session Initiation Protocol (SIP) Session Description Protocol (SDP) FTP Call detail records are transferred by VSGW to the billing server using FTP. LVCP The LVCP provides the interface for peer DAPS to exchange Selective Dynamic Group (SDG) parameter information. If the LVCP message contains an invalid SDG parameter, then the receiving DAP sends an alarm to the OMC-R and utilizes the default configuration for the SDG call. RTP The bearer path for a private Dispatch call carries the Voice over IP (VoIP) packets between SIP and iDEN domains.The RTP header carries the payload type, sequence number, and timestamp. The payload type field distinguishes between media packets, inband (tone) signaling, fax, or noise packets. The sequence number detects missing or out of sequence packets. The timestamp is used for jitter control and silence suppression recovery. SR 16.0 05-Oct-07 6871000P02-A Functional Description 3-37 iDEN Subsystem Overview Other Network Elements SIP SDP creates the encoding type, origin and destination IP addresses, UPD port numbers session start/stop time, and other attributes. SDP parameters are carried in any SIP request or response message body. When a Session Initiation Protocol (SIP) Invite request is received, the Invite includes the group identifier or group list, and the SDP offer. The SDP offer includes call details such as vocoder, and User Datagram Protocol (UPD) port number. The transcoders use the SDP information to convert 3G Voice Over IP (VoIP) packets to VSELP or AMBE++, and convert Real Time Transport Protocol (RTP) to the iDEN version of RTP (iRTP). SDP The iDEN network interacts with various 3G and broadband next generation networks. These networks utilize high-speed access, multimedia and data services over IP, and call control signaling using the SIP and the SDP. SIP is an open standard that is used in various 3G networks, while iDEN uses proprietary Motorola signaling. The iGW translates the signaling standard between the SIP domains and the iDEN network. Call Flow The private call setup flows create a signaling path and a bearer path. During the call, the signaling path is used for talker arbitration (floor control), and call tear-down. The bearer path for a private call carries the voice over IP (VoIP) packets between the SIP and iDEN domains. Note There are different types of iGW calls. The Selective Dynamic Group Call (SDGC) Session Initiated Protocol (SIP) to iDEN (S2D) call is described below. The iDEN training classes offers additional information on all call flows for the iGW system. Figure 3-17 displays the processes and related call flow steps listed in the Follow the Call Flow for a iGW SIP to S2D table on page 3-39. Functional Description 3-38 6871000P02-A SR 16.0 05-Oct-07 iDEN Subsystem Overview Other Network Elements Figure 3-17 SIP to S2D Call Flow (Steps 1-8) TO Follow the Call Flow for a iGW SIP to S2D Step 1 Action Invitation Request The 3G network forwards a Session Initiated Protocol (SIP) Invite request from a 3G subscriber. The Invite includes the group identifier or group list and the Session Description Protocol (SDP) offer. SDP includes call details such as vocoder, UDP port number, and so on. 2 Session Progress The VSGW sends a 183 Session Progress response to the Invite, and forwards a Proxy Page Request Forward message to the HA-DAP. 3 Reserve Resource The VSGW reserves Transcoder (XCDR) resources using the Vocoder Resource Reservation Request. 4 Reserve Response The Transcoder (XCDR) allocates the resources and replies with Vocoder Resource Reservation Response. 5 Page Response Forward After an iDEN subscriber responds to the page, the HA-DAP sends an SDGC Page Response Forward message to the VSGW. SR 16.0 05-Oct-07 6871000P02-A Functional Description 3-39 iDEN Subsystem Overview Other Network Elements TO Follow the Call Flow for a iGW SIP to S2D (continued) Step 6 Action Dispatch Call Connected The VSGW sends a response ('200 OK') to the 3G endpoint signaling that the Dispatch call is connected. 7 8 Endpoint Acknowledges The 3G endpoint sends an acknowledgement message (ACK) to close the Invite process. Floor Control The VSGW interworks the floor control signaling.0 05-Oct-07 . The Selective Dynamic Group Call is set-up and active Functional Description 3-40 6871000P02-A SR 16. . . .0 Feature Descriptions . 4-3 5K Sites in an Urban in Full NGD. . . . . . . . . . 4-4 RMA (Retuning Management Application) . . . . . . . . . . . . . . . . . . . . . . . . . Legacy OMC and NGO Capacity . . . 4-3 OMC Password Policy Enhancements . . . . . . . . . 4-4 EBTS Re-rack with Dual Band RFDS . . . . . . . . . . . . . . . . . . . . . . . 4-7 SR 16. . . . . . . . . . . . . . . . . . . . . . .0 05-Oct-07 6871000P02-A Functional Description 4-1 . . 4-2 Private Call on 900 MHz (PC) . . . . . . . . . . . . . 4-2 iDEN Gateway Dispatch Roaming Registration . . . . . . . . . . . . . . . . .Chapter 4 New Features in SR16. . . . . . . . . . 4-3 OMC Display & Process Enhancements. . . . . . 4-2 Lifetime Audit Registration Renewal Required . . . . .0 In This Chapter Topic See Page SR16. . . . . . 4-2 Selective Dynamic Group Call on Secondary Bands (SDGC) . 4-4 Global Positioning System Denial Response . . . . . . . . . . . . . . 4-5 Feature Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . there may be a situation where most of the SDGC calls are assigned to the 900 band and then moved to a lower band once a new 800U only SDGC user joins the call. Note Legacy group call will not be supported for secondary band.0 are described in this chapter.0 Feature Descriptions SR16. „ „ „ If there are not enough 900 capable SDGC subscribers. 4 Selective Dynamic Group Call on Secondary Bands (SDGC) SDGC on Secondary Bands allows Selective Dynamic Group Call to use upper 800 MHz band and 900 MHz band resources. depending on the rate SDGCs are moved. 900 resources) channel resources available in the current cell.New Features in SR16. ACG is configured to use 900 band for SDGC and 900 band resources The controlling DAP supports SDGC on 900 band All participating SUs in the cell are Private Call on 900 Capable. 4 Private Call on 900 MHz (PC) Private Call on 900 MHz allows a Private Call to use 900 MHz band resources. Functional Description 4-2 6871000P02-A SR 16. The 900 band resources will be assigned for SDGC participant(s) in a particular cell only if all of the following conditions are met: „ ACG has suitable 900 band resource available: 900 I+N threshold rules will be applied for 900 band resource assignment. the operator may wish to turn off SDGC on 900 Bands until a greater penetration of 900 capable users are added. Each unit is homed in one network and will be considered roaming when operating in a different network. Available 800S 4 channel resources will be assigned only if there are no 800U (and by consequence.0 SR16.0 Feature Descriptions The new features for SR16. The feature includes new Subscriber and FNE procedures to move calls inprogress to upper bands when possible (or lower bands if necessary).0 05-Oct-07 . In this case. 4 iDEN Gateway Dispatch Roaming Registration Dispatch roaming registration is support for SUs that can operate in two networks using different technologies (iDEN & 3G). Note 3G systems will have a SIP “IRD” interface instead of an iGW. This is in addition to previous support for 900 Mhz Interconnect. no T-DAPs.New Features in SR16. 4 OMC Password Policy Enhancements 4 This feature provides better security on the NGO OMC. files. and OMC-R internal requirements such as encryption. Only one login will be needed for any OMCR in an Urban. This means that no more than 3200 sites can be placed in a PDR and therefore. Œ Site capacity per OMC beginning in SR15. Legacy OMC and NGO Capacity This feature supports 5000 sites (15000 cells) per urban and is aimed at working in Final NGD mode.0 is 2000 sites SR 16. then two or more PDRs are required if those PDRs contain MDG2s.e all HA-DAPs. Migration to Final NGD mode is required before more than 4000 sites are allowed in the system. Note Œ Final NGD is a prerequisite (i. allowing the administrative operator to control access. Passwords will be on a Urban basis. Fault Management and upload/download capacity. if an Urban area has more than 3200 sites. 4 „ „ „ „ „ „ „ 5K Sites in an Urban in Full NGD. is limited to its current 3200 site capacity. Password files must be encrypted.0 05-Oct-07 6871000P02-A Functional Description 4-3 . change. The NGO OMC-R will conform to the following policies for passwords: „ „ Password a minimum of seven (7) characters in alphanumeric format Passwords will not be stored in plain-text format in scripts. but does not require changing site capacity per OMC-R. This feature requires changing some capacity rules and number of Dispatch Location Areas in the system. It enforces requirements on password creation.0 Feature Descriptions Lifetime Audit Registration Renewal Required The purpose of the Lifetime Audit Registration Renewal Required feature is to eliminate the need for periodic registration renewals in the SU. also facing capacity constraints. PDRs with only MDG4s are under no such constraint.0 SR16. or executable programs Maintain history of previous used passwords to prevent users from reusing a password for a minimum of five (5) cycles Required to change passwords at least once every ninety (90) days User IDs disabled if inactive for 60 consecutive days User ID's at least 8 characters in alphanumeric formats Authorized user (root) will have the ability to turn on/off the password policy. no APD). Like OMC MDG2. validation. It consists of one cabinet configured to support the equivalent capabilities and capacity as a fully configured GEN4 EBTS using multiple RF cabinets. 4 EBTS Re-rack with Dual Band RFDS The Dualband Multisector (DMS) EBTS cabinet houses the 5th generation of the hybrid RFDS and a redesigned multi-channel base radio referred to as the Quad2 BR.0. The duplexers in the DMS rack support both 800 and 900 MHz frequencies. The feature assists the SU in prioritizing the measurement of neighbors.0 05-Oct-07 . The new dual band RFDS supports the following spectrum: Current Spectrum Band Type 800 Mhz 900 Mhz Re-band Spectrum Mobile TX 806-824 Mhz 896-901 Mhz Network TX 851-869 Mhz 935-940 Mhz Mobile TX 817-824 Mhz 896-901 Mhz Network TX 862-869 Mhz 935-940 Mhz Functional Description 4-4 6871000P02-A SR 16.0 SR16. housed in groups of three. The Quad2 BRs are software configurable from the OMC for 800 or 900 MHz frequencies. in a 3-sector.0 Feature Descriptions OMC Display & Process Enhancements These enhancements consist of several enhancements aimed at improving the OMC display/screens and improving internal processes for the Next Generation OMC-R platform introduced in SR15. thus eliminating the need for a duplexer. Three sets of RFDS components. The DMS rack is configured to support: „ „ „ „ 4 Two iSC3s One EAS Up to nine Quad2 BRs. Refer to the OMC System Administrators Guide for a full explanation of these enhancements 4 RMA (Retuning Management Application) This version of the RMA introduces the Neighbor Ordering feature which facilitates the reordering of neighbors in a neighbor list. 3-branch diversity configuration.New Features in SR16. rather than de-keying BRs when the normal timing quality thresholds are not met. ACG reports alarms to indicate operation outside of normal specifications. can command the ACG to attempt to continue using a degrading local time reference. 4 SR 16.0 SR16. The disruption-tolerant mode.0 05-Oct-07 6871000P02-A Functional Description 4-5 . enabled by system operators at the OMC. thus allowing call service to continue (though impaired) beyond the normal 4 hour outage limit.New Features in SR16.0 Feature Descriptions The Single Rack is shown below: Figure 4-1 Single EBTS Rack Global Positioning System Denial Response GPS Denial Response allows system operators to manually adjust GPS parameters in the iDEN system in the rare event that GPS Denial or Spoofing may occur by government action. GPS Spoofing Warning – sent when ACG detects an abnormal condition that might indicate spoofing of the GPS signal.0 05-Oct-07 . Functional Description 4-6 6871000P02-A SR 16.0 Feature Descriptions The following new ACG alarms are reported with this feature: „ GPS Key-up Override Alarm – sent when configuration parameter is enabled and the site has proceeded to key-up with its time reference out of specification.New Features in SR16.0 SR16. GPS tolerance Event – sent before a reset that is related to an operator clearing tolerance parameters. „ „ These parameters are tunable from both the Urban and the Site screens with settings from the Urban screen overriding those of the Site screen. 0 05-Oct-07 6871000P02-A Functional Description 4-7 SU IP . Process & Password GPS Denial Response Automated Neighbor list X X X X X X X X X X SR 16.0 Feature Matrix Feature Matrix The table below shows the major features of SR 16. 4 NETWORK HA DAP Feature OMC-R MDG4 EBTS iBSC DAP iGW X iGW Dispatch Roaming Registration PC on 900 MHz X X X X X X X X X X SDGC on Secondary Bands Re-rack EBTS with Dual Band RFDS X X X X X X X 5.0 and the Network Elements impacted by these features.000 Sites OMC Display.New Features in SR16. New Features in SR16. Functional Description 4-8 6871000P02-A SR 16...0 Feature Matrix NOTES.0 05-Oct-07 . . ...... .... .. 5-19 Radio Link Protocol . ......... ........ .. ..... . ..... . . .... . .... ...... . ..... ...... .......... ........ ......... ........... ..... ... ........ ... .35 . .. ... ..... .. ...... .. ........ ..... ....... .... . . .. . ..... ......... .. . ............... . ... ................... ....... .. .. ........ .. ........ ... ........... ......... ............. .. ..... .. . .. .... ....... 5-17 HSSI ... . ................................... ....... . .. .... ... ..... 5-16 Network Links . .. ... ... .. .. 5-17 V... . ................... . . ....... ...... ....... ......Chapter 5 iDEN System Functional Description In This Chapter Topic See Page Introduction . ..... .. .............. .. .. ..... ..... ...... ...... ... .............. .......... ......... . ........... . ......... ..... .... .... ...... .. ................... ........... . ...... ........ ...... ....... . .. .. . .... . ......... ......... 5-18 EIA-232 . ..... . ... ....... ...... ... . . .......... ... ......... .. ...... 5-19 SR 16..... ...... . . 5-18 Interface Protocols . . ......... ............ . .. . ... ... . .. .. .. ....... ........ ..... . .... .. . ........... . ........ .. ....... . ........ .... ...... 5-18 Twisted Pair . ..... . ... . .... .... 5-17 Coaxial ... ... ........ 5-4 Split and Mixed Mode Systems ....... ........ ...... 5-4 Green Field Systems .. . 5-9 Green Field Systems....... .................. .. 5-19 Motorola Implementation A-bis .. ........ . .. . .. ...... .... ..... ....... 5-12 iDEN Protocol Documents .... . . .. .... ... . ... ..... 5-19 Signaling System Seven ................. ..... . ..... ............... 5-9 Split and Mixed Mode Systems .. ....... ....0 05-Oct-07 6871000P02-A Functional Description 5-1 . .... . 5-9 iDEN Network Protocols. 5-3 Network Architecture... .... . ... ..... . ...... .... 5-5 Network Links and Protocols ........ 5-18 T1/E1. 5-18 AFR ... .... .... .... . .. ...... . ....... .. ........ ....... ... . .. . ...... ........ ...... ....... .... .. .. ... ........ ........ ... .. ....... . ... ..... ....... ... ... .. ..... ......... . ..... ... ... .. . . .... ....... ..... ..... . ...... ...... . .. ........ 5-20 Frame Relay....... .... 5-20 Simple Network Management Protocol . ... ........... ............ 5-20 Vector Sum Excited Linear Predicting... .. ......0 05-Oct-07 .. 5-20 Pulse Code Modulation ... . ..... ... .. . ..25 .. .. .. ...... .. ...... ........ ... ...... .. . ......... ............. . ......iDEN System Functional Description X.. . .. 5-21 Radio Access Call Flow ... . . .... . ... . . .. ... ..... ..... ..... .. . . 5-24 Packet Data Call Flow.. 5-22 Dispatch Call Flow ........ .... ..... .. .... ... ................ . .. ... ...... . .. .... . ......... . .... ...... .... .. .. 5-21 Interconnect Call Flow ... ..... ... ..... ... ......... ....... ... .. .. ..... .... .. .... . ................... ... ...... ... .. .. .... . . 5-19 Ethernet..................... 5-20 End-to-End Call Flows. .... ... ... .. .. . . ..... ... . ..... .. . .. . .... ... .. .... . ... 5-25 Functional Description 5-2 6871000P02-A SR 16.. ... ....... .. ........ It has a site configuration characterized with MOBIS.e... SR 16.e.0 05-Oct-07 6871000P02-A Functional Description 5-3 .iDEN System Functional Description Introduction Introduction This chapter discusses two versions of SR15. HA-DAPs. DAPs. SNMP. and Interconnect voice traffic being carried by circuit switch channels and Dispatch traffic being carried by a Frame Relay channel. iVPUd/di). APDs. They are as follows: „ „ 5 Green Field —A new iDEN system. iDACs) and new network elements (i.0. Mixed/Split Mode —A system configuration characterized by a mixture of Legacy network elements (i. iDEN System Functional Description Network Architecture Network Architecture This section describes the basic iDEN network using system diagrams that show the system with its subsystems and their major components.0 05-Oct-07 .0. Your system may differ. Please note the following: „ 5 See Table 5-1 Key to iDEN System Components Diagrams on page 5-5 for definitions of the components illustrated in the following diagrams. Figure 5-1 iDEN System Architecture Functional Description 5-4 6871000P02-A SR 16. The components and linkages discussed are for a basic iDEN system. 5 „ Green Field Systems This architecture represents the iDEN system for SR16. Authorization and Accounting Server—Non-Motorola Supplied . Figure 5-2 Legacy iDEN System Architecture 5 Table 5-1 Key to iDEN System Components Diagrams General Description Authentication.Used with HA for unit AAA. iDEN Components AAA ACG APD SR 16.0 05-Oct-07 6871000P02-A Functional Description 5-5 . Note This diagram does not illustrate all possible configurations. Access Controller Gateway—The ACG is the site controller and the communications gateway between an EBTS site and the System's central network. Advanced Packet Duplicator—The APD duplicates voice packets that need to be sent to multiple SUs in a group calling.iDEN System Functional Description Network Architecture Legacy iDEN System Architecture This architecture represents legacy iDEN systems. Communications Assistance for Law Enforcement Act—assist law enforcement in executing electronic surveillance pursuant to court order or other lawful authorization. Digital Service Cross Connect—patch panel that consists of hardwired connections on the front and back that allow connections to T1/E1 lines. Broadband Packet eXchange—converts frame relay traffic to ATM cells for transport through the BPX switch node. Building Integrated Timing System—assures the proper processing of voice and data across the network. Enhanced Global Title Translation Table Tool— It provides the following information to all DAPs. Base Site Controller—performs call processing. Environmental Alarm System or External Alarm System—receives alarm signals from various EBTS site equipment and sends them to the iSC for processing. Digital Trunk Controller—terminates facilities for the switch.iDEN System Functional Description Network Architecture Table 5-1 Key to iDEN System Components Diagrams (continued) General Description Billing Accumulator—gathers usage details from the MDG and stores the data for retrieval for billing purposes. sending both the control information and the compressed speech over a radio channel. Digital Cross Connect Switch—central connecting point for ALL T1 and E1 links in the network and is used to separate the information on the T1 or E1 links and route the data to the correct network element. operations and maintenance. iHLRs and iDACs in the network: „ „ iDEN Components BA BITS BPX BR BSC CALEA CWM DAP DCS DSX DTC EAS EBTS EC EGT4 International Mobile Station Identifier (IMSI) ranges associated with a particular iHLR IP addresses of all iHLRs and D-VLRs Functional Description 5-6 6871000P02-A SR 16. Data is retrieved or forwarded to the customer’s Billing Accumulator for further processing. Cisco WAN Manager—a graphical user interface that allows system operators to select which tool or application to launch for Metro Packet Switch (MPS) management. Dispatch Applications Processor—responsible for the overall control and coordination of Dispatch and Packet Data services. Echo Canceller—filters unwanted noise from the main transmitted signal.0 05-Oct-07 . Enhanced Base Transceiver System—carries the radio signal from the SU to the system. Base Radio—performs the RF communications with the SUs. and provides the interface between the XCDR system and the EBTS. maintain. Interactive Voice Response—this is not iDEN-specific equipment. Alarm and status information is reported to the OMC-R through the EAS. It also provides handover support and control in Mobility Management. The iDAC provides the routing of the voice for inter-urban Dispatch calls across different urbans. The iGW supports Selective Dynamic Group Calls (SDGC) which include iDEN and 3G subscribers. Home Agent—routes packets from the Internet to the correct MDG for delivery to the SU. and provides the interface between the iVPU system and the EBTS.0 05-Oct-07 6871000P02-A Functional Description 5-7 . iDEN Base Site Controller—performs call processing. Internet Service Provider—a vendor providing services to the Internet and the web. and tear down calls. iDEN Vocoder Processing Unit—converts the VSELP or AMBE++ voice packets used on the radio link to PCM used by local and Interconnected PSTNs. iDEN Monitor Unit—contains the Environmental Alarm System (EAS). Global Positioning System—assures that input and output data streams within the iDEN system are synchronized. iDEN Components ENET FLPP GPS HA iBSC iCP iDAC iGW iGX iMU iSG ISP iVPU iVR iWF MCTM SR 16. Meridian Cabinet Trunk Module—Cabinet that houses the DTC.iDEN System Functional Description Network Architecture Table 5-1 Key to iDEN System Components Diagrams (continued) General Description Enhanced Network (Switch Matrix)—a set of digital cross connections between input and output trunks that represent the path to be followed for a particular call setup. iDEN Surveillance Gateway—provides an access point for law enforcement agencies to monitor Dispatch calls. Inter-Working Function—performs the data-rate adaptation between the PSTN and the iDEN system. iDEN Dispatch Access Controller—provides Dispatch audio routing between horizontally networked iDEN systems. you select your own. iDEN Call Processor—controls the signaling necessary to set up. operations and maintenance. Fiber Link Peripheral Processor—cabinet that houses the Link Peripheral Processor using DS512 fiber-optic instead of DS30 copper wires. iDEN Gateway—interworks signaling and bearer paths between 3G networks and the iDEN Dispatch network. Integrated GigaBit Exchange—routes frame relay traffic from one network element to another. MPS NDM Mobile Package Switch—routes Dispatch and Packet Data packets to the proper Dispatch subsystem element. and is available to the system operator. Short Message Service—provides the functionality of receiving short text messages. maintains.Gigabyte Exchange— „ „ „ iDEN Components MDG MGX Provides connectivity and interface to the network elements.0 05-Oct-07 . Point of Demarcation—Tap point on the HSSI interface to connect the Dulch comp/analyzer to collect data on the link. RF Distribution System—connects the base radios to the RF antennas. Supernode Data Manager / Fault Tolerant—allows law enforcement agencies to obtain call data records as well as intercept audio in an Interconnect phone call for court authorized monitoring. Signaling Transfer Point—supports SS7 connectivity to network’s switches. Transfers the frame relay connections to a single ATM trunk to the BPX for switching. Packages frame relay packets on to ATM packets and routes these to the BPX for delivery to the correct network element. Packet Data—allows a carrier to supply their subscribers Internet Protocol (IP)-based network access to either the Internet or their own networks. Voice Mail—contains stored voice mail for the subscriber. Multi. Transcoder—converts between PCM from the MSC and VSELP to the EBTS. Operations and Maintenance Center-Radio—establishes. Network Dispatch Messenger—is an optional feature that provides dispatch services and messaging capabilities to end-users operating in an IP environment who want to communicate with iDEN subscriber units or other Dispatch Messenger units.iDEN System Functional Description Network Architecture Table 5-1 Key to iDEN System Components Diagrams (continued) General Description Mobile Data Gateway—manages the overall process of Mobile IP. The MDG works in conjunction with the HA router to receive forwarded packets from its “home address” and distributes these packets to an SU. OMC-R PD POD RFDS SDM/FT SMS SPME STP VM XCDR Functional Description 5-8 6871000P02-A SR 16. Spectrum Peripheral Module Enclosure—cabinet that houses the SPM. collects information about the network. links between MSO and EBTS.iDEN System Functional Description Network Links and Protocols Network Links and Protocols This section uses the OSI layer model to describe the interfaces and links in the iDEN system. Ethernet links. etc. 5 SR 16.0 05-Oct-07 6871000P02-A Functional Description 5-9 . including the RF link. 0 05-Oct-07 .iDEN System Functional Description Network Links and Protocols iDEN Network Protocols Figure 5-3 Network Protocol and Links Diagram 5 Functional Description 5-10 6871000P02-A SR 16. 0 05-Oct-07 6871000P02-A Functional Description 5-11 . IVR. EC and iVPU.iDEN System Functional Description Network Links and Protocols Table 5-2 Key to Network Protocols and Links Diagram Where used Connection to the DCS and to the iVPU Connection to the DACS and to the iVPU Connection to the EBTS and to the DACS Protocol and Links AFR AMBE E1 Connection to the MSC and to the EC Connection to the OMC-R and to theE1 Switch Connection to the NDM and to the DACS Connection to the DSX and to the DACS Connection to the EBTS and to the DSX Connection to the E0 Switch and to the Network Time Server Connection to the E0 Switch and to the E0 Router Ethernet Connection to all ISP/Internet and all LAN/WAN networks. STP. Connection to the EBTS and to the DACS Connection to the MSC and to the VM. Connection to the PSTN and to the STP STM1 Connection to the MSC and to the EC and iVPU Connection to the DACS and to the iVPU SR 16. and IVR Frame relay MOBIS Connection to the EBTS and to the DACS Connection to the DACs and to the iCP Connection to the EBTS and to the DACS MTL OC3 Connection to the DACS and to the MSC Connection to the MSC and to the EC and iVPU Connection to the DACS and to the iVPU OML Connection to the DACs and to the iCP Connection to the iBSC and to the LAN Connection to the iVPU and to the LAN PCM SNMP SS7 Connection to the MSC and to the VM. SMS. and PSTN. Connections within the Network Managements components Connections between the VM. SMS. Table 5-2 Key to Network Protocols and Links Diagram on page 5-11 explains where the protocols and links are used in a legacy SR15.iDEN System Functional Description Network Links and Protocols Table 5-2 Key to Network Protocols and Links Diagram (continued) Where used Connection to the MSC and to the EC Connection to the NDM and to the DACS Connection to the EBTS and to the DSX Connection to the DSXand to the DACS Protocol and Links T1 VSELP Connection to the DACS and to the iVPU Connection to the EBTS and to the DACS Split and Mixed Mode Systems Please note the following: „ Figure 5-4 Legacy Network Protocol and Links Diagram on page 5-13 illustrates the various protocols used throughout the basic legacy SR15.0 05-Oct-07 .0 iDEN system. „ „ Functional Description 5-12 6871000P02-A SR 16.0 iDEN network. This diagram does not illustrate all possible configurations. 0 05-Oct-07 6871000P02-A Functional Description 5-13 .iDEN System Functional Description Network Links and Protocols Figure 5-4 Legacy Network Protocol and Links Diagram SR 16. SMS. iSG Functional Description 5-14 6871000P02-A SR 16. di) Connection to the DACS and to the iVPU(i.35 Patch HSSI Connection to the MPS and to the PODs Connection to the PODs and to the APD. Hi Speed V. DSX. POD. d.35 Patch Connection to the POD and to the APD. BSC.0 05-Oct-07 .35 Patch and to the MDG2 Connection to the Hi Speed V. di) Connection to the EBTS and to the DACS Connection to the XCDR and to the DSX Connection to the DSX and to the DACS Protocol and Links AFR AMBE E1 Connection to the MSC and to the EC Connection to the DACS and to the MPS Connection to the XCDR and to the MSC Connection to the DSX and to the MSC Connection to the OMC-R and to the E1 Switch Connection to the NDM and to the DACS Connection to the E0 Switch and to the Network Time Server Connection to the E0 Switch and to the E0 Router Connection to the EBTS and to the DSX Connection to the DSX and to the DACS E3 Ethernet Connection to the DSX and to the MPS Connection to all ISP/Internet and all LAN/WAN networks.35 Patch and to the MDG4 Connection to the TDAP (R12K) and to the DSX Connection to the TDAP (R10K) and to the V. Connections within the Network Managements components Connections between the VM. iDAC.35 Patch. NDM. iSG Connection to the V. iDAC. V.iDEN System Functional Description Network Links and Protocols Table 5-3 Key to Legacy Network Protocols and Links Diagram Where Used Connection to the DCS and to the iVPU(i. and IVR Frame Relay Connection to the DSX and to the DACS Connection to the MPS and to the DACS. d. Connection to the PSTN and to the Channel Bank. d. and Channel Bank. and iVPU(i. IVR. IWF. d. di) and to the LAN Connection to the iBSC and to the LAN PCM Connection to the MSC and to the VM. Connection to the XCDR and to the MCTM cabinets SNMP Connection to the EBTS and to the DACS Connection to the CP and to the DSX Connection to the iCP and to the DSX Connection to the DSX and to the DACS Connection to the DACS and to the NDM SS7 Connection to the MSC and to the VM. STM1 Connection to the MSC and to the EC and iVPU(i. EC. di) Connection to the DACS and to the iVPU(i. di) Connection to the DACS and to the iVPU(i. STP. di) OML Connection to the DACs and to the iCP Connection to the CP and to the DSX Connection to the iCP and to the DSX Connection to the XCDR and to the DSX Connection to the iVPU(i. d. di) T1 Connection to the MSC and to the EC Connection to the DACS and to the MPS Connection to the XCDR and to the MSC Connection to the DSX and to the MSC Connection to the NDM and to the DACS Connection to the EBTS and to the DSX Connection to the DSX and to the DACS T3 Connection to the DSX and to the MPS SR 16. SMS. d. d.0 05-Oct-07 6871000P02-A Functional Description 5-15 .iDEN System Functional Description Network Links and Protocols Table 5-3 Key to Legacy Network Protocols and Links Diagram (continued) Where Used Connection to the DACs and to the iCP Connection to the DSX and to the DACS Connection to the CP and to the DSX Connection to the iCP and to the DSX Protocol and Links MOBIS OC3 Connection to the MSC and to the EC and iVPU(i. di). d. d.35 VSELP Connection to the DACS and to the iVPU(i.35 Patch Connection to the V. di) Connection to the EBTS and to the DACS Connection to the XCDR and to the DSX Connection to the DSX and to the DACS iDEN Protocol Documents See the documentation listed in Table 5-4 for additional information on protocols.35 Patch Connection to the MPS and to the V. Table 5-4 iDEN Protocol Documentation Title iDEN DPSO EBTS Layer 3: Messages and Procedures iDEN DPSO to EBTS Dispatch Interface: Layer 1 and Layer 2 iDEN DPSO to EBTS Dispatch Interface: Voice Packets iDEN MAP Interface iDEN Naming Specification iDEN RF Interface: A-Interface in iDEN System iDEN RF Interface: Alternate Line Service Specification iDEN RF Interface: General Information on Supplementary Services iDEN RF Interface: In-Band Protocol iDEN RF Interface: Layer 1 iDEN RF Interface: Layer 2 iDEN RF Interface: Layer 3 General Aspects iDEN RF Interface: Layer 3 Messages iDEN RF Interface: Layer 3 Procedures for Circuit-mode Telephone and Data Operation 5 Part Number 68P81129E05 68P81129E03 68P81129E04 68P81129E13 68P81129E11 68P81129E12 68P81129E02 68P81129E01 68P81127E99 68P81127E88 68P81127E89 68P81127E90 68P81127E96 68P81127E93 Functional Description 5-16 6871000P02-A SR 16.0 05-Oct-07 .35 Patch and to the MPS Connection to the MPS and to the OMC-R Protocol and Links V.iDEN System Functional Description Network Links and Protocols Table 5-3 Key to Legacy Network Protocols and Links Diagram (continued) Where Used Connection to the MPS and to the Hi Speed V. The iDAC has one High-Speed Serial Interface (HSSI) interface which transports the voice packets between the iDAC and the Switching Modules. When a port is opened the incoming packet is duplicated to the output ports to the EBTS sites as determined by the mobility management of the DAP.35 EIA . The iDAC uses this interface to communicate with the frame relay devices. SR 16.232 Twisted Pair T1/E1 Coaxial Within the system. coaxial cable is the physical interface between the EBTS BRs and the antenna system.0 05-Oct-07 6871000P02-A Functional Description 5-17 .iDEN System Functional Description Network Links and Protocols Table 5-4 iDEN Protocol Documentation (continued) Title iDEN RF Interface: Layer 3 Procedures for Dispatch and Packet Data Operation iDEN RF Interface: Mobile Subscriber DTE/DCE Interface for Data Services iDEN RF Interface: Radio Link Control iDEN RF Interface: Radio Link Protocol iDEN RF Interface: RF Interface Convergence Layer iDEN RF Interface: Short Message Service iDEN RF Interface: System Information Broadcast Procedure VSELP 4200 BPS Voice Coding Algorithm for iDEN Part Number 68P81127E95 68P81129E10 68P81127E91 68P81127E98 68P81129E08 68P81127E97 68P81127E92 68P81129E15 Network Links The iDEN system uses several interface types. and/or copper. Coaxial cable is also used between the BRs and the EBTS site controller. The HSSI interface can carry up to 10 Mega bits per second (Mbps) of traffic (which includes all the packets for voice and control). fiber. HSSI The APD contains four High Speed Serial Interface (HSSI) ports that are opened and closed under the control of the MTX board. The iDEN system uses the following links: „ „ „ „ „ „ 5 Coaxial HSSI V. The transport facilities between the DACS may include microwave. A minimum of Category 5 cable and connections is required. OML also uses EIA-232 cabling to the switched circuits (MSC). Interface Protocols The iDEN system supports and uses several protocols and interface standards. reconfiguring may impact the capacity of network elements. Optimization. EIA-232 The OMC-R. The exchange of information between the various pieces of equipment is over direct link or dedicated facilities using T1 (E1) industry standards. Other elements may be optionally networked by Ethernet. load balancing and capacity planning will be affected by the physical backbone used. In the MSO.25 Ethernet Simple Network Management Protocol Functional Description 5-18 6871000P02-A SR 16.35 The OMC-R Operations and Maintenance Link (OML) uses V.35 cabling between the OMC-R and the DAP. the network devices are Interconnected with T1s.0 05-Oct-07 . These include the following: „ „ „ „ „ „ „ 5 AFR Radio Link Protocol Motorola Implementation A-Bis interface Signaling System Seven X. Since an E1s have a different configuration than T1s. The connection to the BSC may also be V. OMC-Rs may be networked using an Ethernet link. The equipment may be re-configured between the span types by replacing hardware. The DAP and the iHLR communicate with each other over the twisted pair. Network and iDEN equipment is ordered with the appropriate hardware to support either E1 or T1 facility. V. T1/E1 The iDEN network has standardized on the T1 as the physical interface. DAP to DAP communication occurs over the twisted pair. Twisted Pair Thin-wire (10baseT) ethernet may be used between the OMC-R and the TDAP.iDEN System Functional Description Network Links and Protocols The Tandem DAP uses High Speed Serial Interface (HSSI) to interface to the APDs.35 cabling. „ „ „ The T-DAP and the iHLR communicate to the OMC-R with this interface. Full or fractional T1s are used. 25 functions primarily at 19. CCITT SS7 signaling is used between the MSC and the HLR and the MSC and the SMS-SC. The OMC-R uses X. Modifications adapt the A-bis standard to the RF link sideband and help to assure timing and mapping of radio link data packets. The LAP-D protocol is used in signaling as the Message Transport Protocol (MTP) between the EBTS and the BSC.25 The X. Signaling System Seven Signaling System Seven (SS7) is the routing and control interface between the other provider networks and the MSC and from the MSC to the BSC-CP. The BSC handles the translation between LAP-D and LAP-B. X.Link Access Protocol -B-Channel (LAP-B) and Link Access Protocol . These modifications include changes in message format and the inclusion of additional parameters for handover messaging.25. This SS7 is the Message Transfer Link (MTL) and is implemented in accordance with ANSI SS7-ISUP. and iVPU. Motorola Implementation A-bis Motorola’s implementation of GSM A-bis (MOBIS) is a modified version of the GSM A-bis interface.0 05-Oct-07 6871000P02-A Functional Description 5-19 . LAP-B is the protocol used between the BSC and the OMC-R.25 protocol is used primarily in the operation and maintenance functions of the network.Data (LAP-D).25 link is used by the operation and maintenance Link (OML) and its functions between network devices linked to the OMC-R.25 . SR 16. Radio Link Protocol Radio Link Protocol (RLP) is the method of transferring compressed character data between the SU and the MSC-IWF during circuit switch data networking. Interconnect calls use SS7 at the BSC. X.2Kbps on V.35 cables (including the DAP). SS7 is used by the Short Message Service and Voice Mail. The T-DAP uses an Ethernet link but maintains X. MOBIS provides increased timing and error handling capabilities to provide greater radio link reliability and improved link quality. EBTS.iDEN System Functional Description Network Links and Protocols „ „ „ VSELP Frame Relay Pulse Code Modulation AFR All Frame Relay (AFR) is used on the OMC-R. iBSC. The X. Pulse Code Modulation Pulse Code Modulation (PCM) is the telephone industry standard for the format and encoding of data packets transmitted across voice networks.iDEN System Functional Description Network Links and Protocols Ethernet The principle use of ethernet in the iDEN system is between components in the EBTS. SNMP is used within the X.LAP-D on a V. For additional information. The speed is at least 256kbps from the DAP to the MPS.25 protocol. PCM is used by iDEN for Interconnect calls to and from land networks. The EBTS uses ethernet for traffic and control by running Carrier Sense Multiple Access/Collision Detect (CSMA/CD) protocol. and is set by the MPS. The MSC and the BSC XCDR use PCM for voice and data transmission.0 05-Oct-07 . messaging. Simple Network Management Protocol Simple Network Management Protocol (SNMP) is used over the dedicated links between the EBTS and BSC.X. TCP/IP may be used to communicate with the administration and data and other service provider equipment. Depending on how the EBTS is configured for Interconnect and Dispatch.35 link. The iDEN system engineering staff provides guidelines to allow service providers to provision the T1/E1s for Interconnect and Dispatch. The XCDR converts between PCM from the MSC and VSELP to the EBTS. the number of DS0s available will vary. The BSC-XCDR converts VSELP to Pulse Code Modulation (PCM) for Interconnect calls. The Advanced Packet Duplicators (APD) and iSC are linked using Frame Relay . Functional Description 5-20 6871000P02-A SR 16. The T-DAP uses High Speed Serial Interface (HSSI) to interface to the APDs. This is an indirect link through the MPS.OMC-R interface is ethernet running X. Frame Relay The iDEN system supports frame relay protocol during Dispatch communications. see EBTS Backhaul: Frame Relay DSO Requirements (WP2002-025).25 OML to manage the alarm. control and performance data routing to the EBTS. The TDAP . Transmission Control Protocol/Internet Protocol (TCP/IP) is supported in the ethernet environment in accordance with IEEE 802. The SU compresses voice for all transmits and decompresses on voice on all receives. Vector Sum Excited Linear Predicting Vector Sum Excited Linear Predicting (VSELP) protocol is a voice compression method used in the mobile station and the XCDR. The MPS-DAP cluster controls the movement of VSELP packets between EBTSs during Dispatch calls. channel access. and data transfer steps. The iMU/EAS/EAS2 receive alarm signals from various EBTS site equipment and sends them to the iSC for processing. programmable telephone industry device that provides a transport system within the iDEN network.0 05-Oct-07 6871000P02-A Functional Description 5-21 . The iSC performs all control and synchronization functions for the EBTS.iDEN System Functional Description End-to-End Call Flows End-to-End Call Flows This subsection describes and illustrates how typical types of calls flow through the network elements in the iDEN system. 5 Radio Access Call Flow The procedure for Radio Access call flow process consists of the following registration. into the EBTS. and back out to the site antennas for transmission. The Base Radio (BR) sends and receives control information and compressed voice data. The Radio Frequency Distribution System (RFDS) routes radio frequency signals from the site receive antennas. Radio Access Call Flow „ „ „ Figure 5-5 SR 16. The Digital Cross Connect Switch (DCS) is a standard. The Radio Access Network call process is as follows: „ „ 5 The SU transmits a signal to the antennas. The MSC determines services and location information. TO Setup an Interconnect Call Action Make a Call (origination) a) Send Random Access Protocol (RAP) on PCCH Step 1 b) c) d) e) f) g) 2 Mobile gets a dedicated control channel assigned Authentication (optional) Call setup transaction Get assigned to a traffic channel Call termination request on associated control channel Channel released Get a Call (receive) a) Locate SU by last known Interconnect Location Area (ILA) b) c) d) e) f) g) h) i) Page SU on primary control channel of all sites in ILA RAP on primary control channel Get dedicated control channel assigned Authentication (optional) Call setup transaction Get assigned to a traffic channel Call termination request on associated control channel Channel released Functional Description 5-22 6871000P02-A SR 16. The iBSC-iVPU handles voice circuits subrates and PCM CICs. The MSC also controls and routes the calls to other providers. The iBSC-iCP routes control packets. and data transfer steps. „ „ „ „ The procedure for Interconnect call flow process consists of the following registration. channel access.0 05-Oct-07 . The EBTS converts the radio link to the land link and discriminates between Interconnect and Dispatch calls. The iBSC routes Interconnect packets between the EBTS and the MSC.iDEN System Functional Description End-to-End Call Flows Interconnect Call Flow The Interconnect call process is as follows: „ „ 5 The SU sends and receives voice data. SR 16.0 05-Oct-07 6871000P02-A Functional Description 5-23 .iDEN System Functional Description End-to-End Call Flows Figure 5-6 Mobile Originated Interconnect Call Setup Step Diagram Note See Interconnect Subsystem on page 3-9 for a more detailed call flow. The Dispatch Application Processor (HA-DAP) assigns signaling and routing paths for Dispatch and Packet Data calls. Step 1 2 3 4 5 6 The DAP recognizes the MSs group and finds the group members by location area (DLA). Call voice packets are sent to the PD. Enhanced Global Title Translation Table Tool (EGT4) provides International Mobile Station Identifier (IMSI) ranges associated with a particular iHLR and the IP addresses of all iHLRs and D-VLRs. The group member MSs respond with each’s current sector or cell location. The iDEN Home Location Register (HA-iHLR) authenticates the SU and registers the Dispatch and Packet Data in the iDEN system. The iDEN Surveillance Gateway (iSG) provides law enforcement surveillance capability for the iDEN Dispatch and Packet Data subsystems. Network Dispatch Messenger (NDM) allows a direct connection between your PC and the iDEN phone. Functional Description 5-24 6871000P02-A SR 16.0 05-Oct-07 . „ „ „ „ „ The simplified steps of a typical Dispatch call are: TO Setup a Dispatch Call Action A Dispatch call is requested via PTT activation. where they are replicated and distributed to the MSs sites.iDEN System Functional Description End-to-End Call Flows Dispatch Call Flow The Dispatch call process is as follows: „ „ 5 The SU sends and receives voice data. The DAP supplies each member’s routing information to the MPS and PD. The EBTS converts the radio link to the land link and discriminates between Interconnect and Dispatch calls. The call request packet is routed to the DAP. The DAP sends location requests to the member's DLA to obtain current sector or cell. The Authentication. The MDG (Mobile Data Gateway) directs connections to the Internet. Authorization. 5 Packet Data Call Flow The Packet Data call process is as follows: „ „ The SU sends and receives voice data. The Home Agent (HA) routes Packet Data information to and from the SU. „ „ „ „ SR 16.iDEN System Functional Description End-to-End Call Flows Figure 5-7 Typical Dispatch Call Summary Note See Dispatch Subsystem on page 3-17 for a more detailed call flow. The EBTS converts the radio link to the land link and discriminates between Interconnect and Dispatch calls. and Accounting (AAA) Server authenticates Packet Data. The Billing Accumulator (BA) collects and stores billing records that are produced by the MDG and provides an avenue for the stored billing records to be transferred to an outside billing center.0 05-Oct-07 6871000P02-A Functional Description 5-25 . Session reconnect/reselect during cell changes occurs. and data transfer steps. SU initiates a data transfer session to gain access to a packet channel and goes into Session Active state. TO Setup a Packet Data Call Action Registration for Dispatch service (in home or visited network) and authentication occurs. When the SU is outside its home network. registration for Dispatch service is processed differently.iDEN System Functional Description End-to-End Call Flows The procedure for Packet Data call flow process consists of the following registration.0 05-Oct-07 . MDG initiates a session for the targeted MS. channel access. Functional Description 5-26 6871000P02-A SR 16. Registration for mobile IP service and tunnel setup occurs. Step 1 2 3 4 5 6 Registration for Packet Data service occurs. Note See Packet Data Subsystem on page 3-23 for a more detailed call flow.0 05-Oct-07 6871000P02-A Functional Description 5-27 . SR 16.iDEN System Functional Description End-to-End Call Flows Figure 5-8 Packet Data Call Flow For more information see iDEN Packet Data Service Registration and Call Processes (68P80801C90). .iDEN System Functional Description End-to-End Call Flows NOTES.0 05-Oct-07 .. Functional Description 5-28 6871000P02-A SR 16. .............. . .. 6-7 General Call Functionality ... .. 6-4 Next Generation Dispatch Configurations ........................... 6-7 Radio Link Functionality ..... ........... ..................................................... ..... . ..... ....... ... ......... .. ...... ....... ........ ... ........... ....... . 6-13 iSC2 ........... . ..............0 05-Oct-07 6871000P02-A Functional Description 6-1 . ........ 6-9 Base Radio.... . ...... 6-18 SR 16........ .... .... 6-7 All Frame Relay.................. .................................. . ..... .. .... ..................... 6-6 Split Mode ........... .. .................. ............ .. 6-8 iSC . .... .. . ........... ... 6-9 RFDS ..... 6-10 EBTS Hardware Description ............. .... ..... ............... ... .. .... 6-8 Key Network Elements ........... ..... ................... .... .. ......... ... .. ............ .. .... .... ..... . ......... .... ............ ............ ..... ... .... .... 6-3 Radio Access Network Subsystem Description ........ .. ................. ....................... ............... ...... ... ... .... .. 6-10 ACG . ......... ......... 6-4 Introduction ..... ........ ..... ........... ......... ..... ......... . . ............. .. .................. 6-8 EBTS ....... .... ..... ...................................... ............ .... ... .. .... 6-14 iMU and EAS...... 6-16 RFDS . ......... . .................... ........................ ....... .......................... ... ....... ........ 6-5 Mixed Mode Configuration ....... . ................... ....... .................. ....... .......... ........ ..... ... ..... ........ ..................... ..... ................... .... . 6-4 References ................... .. ............ ... . ................. ...... ............................................ ...... ....... .. ... ...... ........ . .................... 6-4 Radio Access Network Overview ..... ............... ............. ..... .... . ............. ... ......... ............... ........ ............ . 6-8 DCS.. . .... .. . .. .... 6-10 Overview ... ..... .... . .. 6-9 Enhanced Base Transceiver System .. .......... . ......... ... . ........ .... .... ........... ............. .................... .. 6-13 iSC3 ... ........ 6-16 Base Radio. ...... ................. .... ...... ................. .....Radio Access Network Details Chapter 6 Radio Access Network Details In This Chapter Topic See Page Purpose............. ....... .. ..... . . ......... ....... .......... .. . .. . . ... .... . ... .............. .......... .. ... . ............. .... .... ... .. 6-19 OMC-R .............. ..... .... ..................... ...... ...... ......... ...................0 05-Oct-07 .......... 6-20 Load Shedding ............. ....................... .................. ....................... ............... ...... . ..... .. . .......... ..... 6-19 EBTS Network Management ........... ..... .. ..... . ............... . ..... 6-19 MMI Commands ......... ... 6-19 Status Indicators ........................ . ............................ ......... 6-19 Event Logs ..... ................... ...... .... ................ . ..... ..... ..... 6-20 Functional Description 6-2 6871000P02-A SR 16............Radio Access Network Details EBTS Software Description . ................ 6 SR 16.0 05-Oct-07 6871000P02-A Functional Description 6-3 . and the network management. hardware and software descriptions.Radio Access Network Details Purpose Purpose This chapter describes the major network elements of the Radio Access Network subsystem in terms of their key hardware components. software function. Each key component is explained. and network management facilities. including its key functions. and network management facilities.com unless otherwise stated. software function. cell sites.Radio Access Network Details Radio Access Network Subsystem Description Radio Access Network Subsystem Description Introduction 6 6 This section describes the iDEN Radio Access Network Subsystem. Figure 6-1 Radio Access Network Architecture on page 6-5 represents the architecture of the Radio Access Network. more commonly.0 05-Oct-07 . The EBTS provides the Radio Frequency link between the land network and the Subscriber Units (SUs). the base station radios and associated control equipment are contained in the Enhanced Base Transceiver System (EBTS) or. The Base Radios (BRs) perform the communications with the SUs. sending both the control information and the compressed speech over a radio channel. Radio Access Network Overview In the iDEN system.motorola. 6 Functional Description 6-4 6871000P02-A SR 16. including key hardware components. References The following is a list of technical documentation and training courses that support the EBTS: „ „ „ „ „ „ „ „ „ „ „ „ „ EBTS Fundamentals Course (FND104) EBTS Operations & Maintenance Course (OPM203) EBTS Troubleshooting Guide (6881012Y79) EBTS Volume 1 System Installation and Testing (68P80801E35) EBTS Volume 2 Base Radios (68P80801E35) EBTS Volume 3 RF Distribution Systems (68P80801E35) 900 Quad EBTS Multi-Sector Rack Configuration (WP05008B) iDEN EBTS Fan Maintenance Plan (WP2003-14) iDEN Integrated Site Controller System Manual (68P81098E05) iDEN Gen 3 Site Controller System Manual (68P80801E30) iDEN EBTS Total Site Maintenance (WP2001-010) Ethernet Analyzer Detective Software User's Manual (68P81001Y55) Inbound Handover Threshold Optimization (WP2002-026) These documents and others are available on the Motorola Extranet web site at http://mynetworksupport. It is characterized by All Frame Relay (AFR). SR 16. Supports Split Backhaul and AFR Backhaul EBTSs. Supports Split Backhaul EBTS’ only. split backhaul.0 05-Oct-07 6871000P02-A Functional Description 6-5 . iVPU Dispatch Interconnect (iVPUdi) — Software upgrade to support Dispatch and Packet Data functions in addition to Interconnect transcoding.Radio Access Network Details Radio Access Network Subsystem Description Figure 6-1 Radio Access Network Architecture Next Generation Dispatch Configurations The Next Generation Dispatch (NGD) provides higher capacity and greater system reliability in a significantly smaller footprint. (There is no Interconnect transcoding. iVPU Interconnect (iVPUi) — Interconnect transcoding. or a combination of configurations. The main changes to the iDEN network with the NGD system are: „ The iDEN Vocoder Processor Unit (iVPU) is designated with respect to its configuration: Œ Œ Œ iVPU Dispatch (iVPUd) — iVPU hardware operating with only Dispatch and Packet Data functions.) The iVPUd supports Split Mode Backhaul EBTSs only. Software upgrade of iVPUs in the field default to this mode. iDACs) and new NGD network elements (e. HA-DAPs. Functional Description 6-6 6871000P02-A SR 16.0 05-Oct-07 . These network elements can coexist with the legacy network elements. In the Mixed Mode phase of the iDEN architecture. iVPUs). the Mixed Mode network is considered a transitional phase. BSCs. The backhaul is determined through backhaul negotiation rather than configuration. See Figure 6-3 NGD Mixed Mode Configuration on page 6-7. including: Œ Mixed Mode Œ Split Mode Œ All Frame Relay Mixed Mode Configuration Between Legacy and NGD architecture.g.. (See Figure 6-2 NGD Configuration on page 6-6..) „ „ Single Software Load One Network Element from the perspective of the OMC Figure 6-2 NGD Configuration The NGD configuration allows the EBTS to automatically determine which backhaul mode (Split or AFR) to use in order to communicate with the Northbound network and to communicate with the new NGD NEs.Radio Access Network Details Radio Access Network Subsystem Description The NGD system configuration impacts the EBTS in that all EBTSs communicate via the iVPUs. DAPs. The NGD architecture supports various configurations. the network elements that are required for Next Generation Dispatch are migrated into the Legacy architecture. APDs.g. Mixed Mode is a system configuration that is characterized by a mixture of Legacy network elements (e. The HA-iHLR provides the databases where subscriber profile information is stored for Dispatch authentication. All Frame Relay All Frame Relay (AFR) is supported in both Mixed Mode and in the final NGD configurations. and interconnect voice traffic being carried by circuit switch channels and dispatch traffic being carried by a Frame Relay channel. In the AFR configuration.0 05-Oct-07 6871000P02-A Functional Description 6-7 . or iVPUdi. Mobis. Interconnect voice traffic can terminate on either a legacy Transcoder (XCDR).Radio Access Network Details Radio Access Network Subsystem Description Figure 6-3 NGD Mixed Mode Configuration Split Mode The NGD network also supports the Split Mode site configuration which is characterized with Mobis. The Mobis and SNMP channels must terminate on an iCP or legacy Base Site Controller (BSC). The voice packets are duplicated and routed to the appropriate cell sites to support the group call. The EBTS’ traditional circuit traffic (O&M. The Frame Relay traffic can terminate on a legacy Dispatch Application Processor (DAP). the EBTS converts the radio link to various land-line protocols depending on whether the call is Dispatch. Mobile Data Gateway (MDG). and interconnect bearer) must be encapsulated in frame relay packets using appropriate methods. interconnect. SR 16. iVPUd. SNMP. General Call Functionality When a call is initiated. or Packet Data. iVPUi. dispatch and packet data traffic over Frame Relay. all traffic is to be packetized. Interconnect. The DAP/HA-DAP then determines service availability and location information. or iVPUdi. AFR trunks carry signaling. programmable telephone industry device that provides a transport system within the iDEN network.0 05-Oct-07 .Radio Access Network Details Radio Access Network Subsystem Description Radio Link Functionality The EBTS establishes and maintains the radio link on the RF control channels when a call is initiated. DCS The Digital Cross Connect Switch (DCS) is a standard. If the location of the SU indicates that another EBTS has better radio link quality. It is the central connecting point for ALL T1 and E1 links in the iDEN network and is used to separate the information on the T1 or E1 links and route the data to the correct network element. The availability of the traffic channel in a specific area increases when additional BRs are added. 6 EBTS The EBTS is the equipment through which the radio signal from the subscriber gains access to the system. under the direction of the HA-DAP. the EBTS determines what protocol to use based on whether the call is Dispatch. and/or Copper Functional Description 6-8 6871000P02-A SR 16. Once the radio link is established. including the following: „ „ „ Microwave Fiber. the DCS crossconnects interconnect voice packets to the BSC/iBSC complex. or Packet Data. With an increase in BRs. The iVPU coordinates the movement of voice packets between the EBTS’ and the iVPUs. This is also referred to as a site or cell site. The iVPU. routes voice packets to another EBTS if the Subscriber Unit (SU) reconnects. the DCS connects dispatch voice packets to the iVPU. then the SU reconnects to the new EBTS without handover control overhead. more Digital Access Cross-Connect Switch (DAC) and DAP/HA-DAP resources are needed to support the increase in radio link capacity Key Network Elements This section provides a brief description of the key Radio Access Network network elements. For Interconnect calls. Interconnect. The BSC/iBSC coordinates the movement of packets between the DCS and the MSC. For Dispatch calls. EBTS also supports a power backup system. The SU reselects and connects dynamically as required. Transport facilities between the EBTS and DCS may use several interface types. and backhaul to the Mobile Switching Office (MSO). SR 16. Dispatch. BRs send both the control information and the compressed speech over a radio channel and packet data translations. RFDS The Radio Frequency Distribution System (RFDS) permits the combining of the transmit RF signal out of the BRs. It routes interconnect.0 05-Oct-07 6871000P02-A Functional Description 6-9 . It amplifies and distributes the receive signal to the BRs. while the EBTS provides the Radio Frequency (RF) link between the land network and the SU’. Base Radio The BRs perform the RF communications with the SUs. performs resource allocation.Radio Access Network Details Radio Access Network Subsystem Description iSC The iSC controls the routing of information to/from the Base Radio(s). satellite tracking. and Packet information to and from the MSO via a T1 or E1 trunk. The hardware consists of the Transmit Combiner Deck(s) and the Receive Multicoupler assemblies. interconnect. including key hardware components. and a Radio Frequency (RF) Cabinet that contains the BR which is responsible for control signaling and user voice/data.) EBTS components are rack-mounted. and packet data services.Radio Access Network Details Enhanced Base Transceiver System Enhanced Base Transceiver System This section describes the Enhanced Base Transceiver System (EBTS) of the Radio Access Network subsystem. 6 Overview The Radio Access Network includes the EBTS which provides the RF interface for the SU. 6 EBTS Hardware Description The EBTS consists of a Control Cabinet that houses the integrated Site Controller (iSC) which performs all control and synchronization functions for the EBTS. 6 Functional Description 6-10 6871000P02-A SR 16. This is also referred to as a site or cell site. A standard configuration is recommended. which provides dispatch. but an EBTS can be configured with different equipment to tailor the performance. The EBTS also supports a power backup system. The EBTS is the equipment through which the radio signal from the subscriber gains access to the system.0 05-Oct-07 . It also provides the T1 serial data interface between the iDEN Mobile Switching Office (MSO). software function. and network management facilities. (See Figure 6-4 EBTS Cabinets on page 6-11. 0 05-Oct-07 6871000P02-A Functional Description 6-11 . The circuit breakers provide an on/off control for these modules. and monitoring of the radio channels and Time Division Multiple Access (TDMA) time slots of the radios under the control cabinet’s control.provides a central location for cabinet grounding and intercabling.the central location for power distribution and overload protection of the RF Cabinet. Radio resource management is the control. which contains various equipment modules including the following (see Figure 6-5 Radio Frequency Cabinet on page 6-12): „ „ Base Radio Breaker Panel . The RF Cabinet is a self-supporting structure. In addition to radio resource management. the control cabinet also routes data and voice information to the correct network element at the MSO and provides the interface between the rest of the EBTS equipment and the MSO. Access to the Junction Panel is gained from the rear of the RF Cabinet. Junction Panel (rear of cabinet) . RF Distribution System „ „ SR 16.Radio Access Network Details Enhanced Base Transceiver System Figure 6-4 EBTS Cabinets The EBTS Control Cabinet contains the network elements that are responsible for radio resource management. They also act as automatic disconnect switches in the event of an electrical overload. assignment. Radio Access Network Details Enhanced Base Transceiver System Figure 6-5 Radio Frequency Cabinet Functional Description 6-12 6871000P02-A SR 16.0 05-Oct-07 Radio Access Network Details Enhanced Base Transceiver System The following EBTS network elements are described in more detail below: „ „ „ „ „ Access Control Gateway (ACG) iDEN Site Controller iMU/EAS RFDS BR ACG The Access Control Gateway (ACG) is the site controller and the communications gateway between an EBTS site and the MSO. The ACG manages its RF resources as well and reports performance data to the OMC which can be used for troubleshooting. Note The terms Integrated Site Controller (iSC) and Access Controller Gateway (ACG) can be used interchangeably to refer to the same component. The ACG uses either of two integrated Site Controller (iSC) platforms: „ „ iSC3 - this is the current platform iSC2 - this platform is still used in the field but is not available in new EBTS shipments The main differences between the two iSCs are the number of rack units (size/ height), processor speed and the number of T1/E1 and Ethernet ports. The ACG also allows the OMC-R operator to remotely switch over to the standby ACG. iSC3 The third generation Site Controller (iSC3) is capable of supporting the advanced iDEN features that will be developed over the next several years. The GEN III Site Controller (see Figure 6-6 below) is compatible with the current generation of EBTS equipment. The iSC3 supports more RF carriers than the iSC2. iSC3 Front Panel Figure 6-6 SR 16.0 05-Oct-07 6871000P02-A Functional Description 6-13 Radio Access Network Details Enhanced Base Transceiver System Two iSCs are recommended for redundant/standby operation. These units are software switchable (active-standby). Communication between the master (active) and standby is initiated by the active controller. This redundancy reduces maintenance and downtime. In the event of an EBTS failure, the iSC allows an OMC-R operator to perform tests to isolate faults between the EBTS and the facilities (T1/E1) and load new software. The functionality of the SRI, ELP, STP, and transient protection cards in the iSC2 is built into the motherboard of this newer version of controller. The iSC3 does not contain field replaceable units. The main differences between the two iSCs are the number of rack units (size/ height), processor speed and the number of T1/E1 and Ethernet ports. iSC2 As with the latest version of the site controller, the iSC2 performs all control and synchronization functions for the EBTS. This includes radio resource management or the control, assignment, and monitoring of the radio channels and time slots of the radios under its control. Note Beginning with SR 15.0, the iSC will periodically monitor its CPU utilization. When it goes higher than certain thresholds, the iSC2 performs a set of actions to reduce CPU utilization. When CPU utilization is lowered and it exits the threshold level, normal processing is restored. All iSC2s will be required to have their RAM upgraded to 32MB. The OMC will not download new configuration files to iSC2s with less than 32MB. The iSC is also the interface between the MSO and the BRs. The iSC communicates with the MSO via either a T1 or E1 interface, and with the BRs via an Ethernet LAN. There is usually a redundant iSC that will control the site in the event the primary iSC fails. The iSC2 consists of the following modules (see Figure 6-7 iSC2 - Front and Rear Views on page 6-15): „ Ethernet LAN PCI (ELP) - Provides IEEE 802.3 10Base2 Ethernet interface between the Controller and the BRs. Subrated T1 PCI/subrated E1 PCI card (STP/SEP) - Provides the site network interface between the Controller T1/E1 span. Integrates the Channel Service Unit (CSU) functionality used in other systems. Site Reference ISA card (SRI) – Provides EBTS with accurate frequency reference (5 MHz) and timing information (1 PPS). „ „ Functional Description 6-14 6871000P02-A SR 16.0 05-Oct-07 Radio Access Network Details Enhanced Base Transceiver System „ Serial/Parallel Transient protection card – Provide transient protection for the serial/parallel data I/O. The Serial/Parallel card is the connection point for the RS232 and IEEE 1284 parallel connection between the Controller and the iMU. T1/E1 Transient protection card – Provides physical interface to the network (MSO) and conditions the signals. The T1 is first routed through the transient protection circuitry before being processed by the STP card. The circuitry protects the STP card from surges on the T1 line. iSC2 - Front and Rear Views „ Figure 6-7 Most systems are configured with two Controllers (a main and a standby) and an iMU. SR 16.0 05-Oct-07 6871000P02-A Functional Description 6-15 Radio Access Network Details Enhanced Base Transceiver System iMU and EAS Both the iDEN Monitor Unit (iMU) and the Environmental Alarm Systems (EAS or EAS2) receive alarm signals from various EBTS site equipment and sends them to the iSC for processing. The alarm signals can come from BRs, the RFDS, circuit breaker status signals, as well as customer-defined alarms such as AC power, smoke alarms, intrusion alarms, high/low temperature alarms, and antenna tower lights. The EAS monitors EBTS site alarms and reports the alarms to both iSC3s through the parallel ports on the back labeled “Controller A” and “Controller B”. The EAS is sometimes referred to as the IMU II. The control cabinet contains either an iMU or an EAS depending on the type of iSC that is installed. „ „ iSC2 contains the iMU iSC3 contains the EAS RFDS The RFDS is the frequency combiner that allows several BRs to share a common antenna system. The EBTS can be configured with either hybrid or cavity combiners. This creates minor changes in maintenance and operation but does not affect the functionality of the radio link. The EBTS site antenna configurations will vary with each installation. Each EBTS cell requires RF antennas for TX and RX signals. Site antenna configurations include three RX antennas for each omni or sector RF coverage area. Sites may be configured with a separate TX antenna for each omni or sector RF coverage area, but typically the site antennas are configured so that the TX signals are applied to one or more of the RX antennas. Therefore a site may have either four or three antennas for each omni or sector RF coverage area. There are several different ways to configure the RFDS depending upon the number of BRs and the antenna configurations. The following are the types of RFDS used in the EBTS site: „ Duplex RFDS - is a broadband, three-antenna RF distribution system. It allows a transmit (TX) and a receive (RX) path to share a common antenna. A total of three duplexers reside within this distribution system. (See Figure 6-8 Duplex RFDS on page 6-17.) Cavity Combining RFDS - is a narrowband, three or four antenna, nonduplexed RF combining system. It consists of two or three receive antennas and a single transmit antenna. (See Figure 6-9 Cavity Combining RFDS on page 6-17.) „ Functional Description 6-16 6871000P02-A SR 16.0 05-Oct-07 Radio Access Network Details Enhanced Base Transceiver System Figure 6-8 Duplex RFDS Figure 6-9 Cavity Combining RFDS SR 16.0 05-Oct-07 6871000P02-A Functional Description 6-17 0 05-Oct-07 .) A BR can be removed from the EBTS and replaced with a new BR without taking the site off the air. The RF PA provides the final TX RF power output to the RFDS and TX antenna. Call setup. It can be software-configured from the OMC-R for from 1 to 4 carriers. The BR is mounted below the RF Distribution System in the RF Cabinet. and control will occur in the 800 MHz band. Increased channel capacity is achieved through voice compression techniques and time division multiplexing. a Quad2 BR is supported only on sites with an iSC3 or an iSC2 with a memory upgrade.Provide DC voltages for various BR modules „ „ „ „ The BR platforms that are currently supported include the following: „ „ EBRC — These can only support a single 25 KHz RF carrier.contains three receivers that provide RX antenna diversity Power Supply . The QUAD BR can be software-configured from the OMC-R for 1 to 4 carriers. Quad BR — These can support four 25 KHz RF carriers on one physical BR and utilizes the same platform as the single channel BR. To support the extra memory requirements for a Quad2 BR image.controls the BR RF transmitter (TX) and receiver (RX). Receiver . 900 MHz Quad BR— These are assigned 900 MHz frequencies whenever possible for interconnect traffic.provides low level TX RF output signal to drive the RF Power Amplifier RF Power Amplifier (PA) . Exciter . „ „ Functional Description 6-18 6871000P02-A SR 16. Each BR consists of the following components: „ Base Radio Controller (BRC) . BRs are either single-channel units that provide a single 25 KHz RF carrier in one physical unit or a QUAD Channel BR that supports up to four 25 KHz RF carriers in one physical unit. The BRC has a 10Base2 Ethernet interface for communication with the ACG/iSC. The BRs and the radio link traffic (voice and data) are controlled by the ACG/iSC over the Ethernet LAN.Radio Access Network Details Enhanced Base Transceiver System Base Radio The BR provides reliable digital capabilities via a compact softwarecontrolled design. (See Figure 6-5 Radio Frequency Cabinet on page 6-12.amplifies the low level TX RF signal from the exciter. Quad 2 BR — These provide customers with the flexibility to deploy either 800 MHz or 900 MHz frequencies with the same hardware platform and reduce the number of BR Field Replaceable Units (FRUs) to be maintained. MMI Commands As with other iDEN network elements. The OMC-R receives events and alarms to help isolate problems.Radio Access Network Details Enhanced Base Transceiver System EBTS Software Description The EBTS software and configuration data are loaded into the system via the Operation and Maintenance Center (OMC-R). access to alarm log files. and isolating faults within the iDEN network. „ SR 16.0 05-Oct-07 6871000P02-A Functional Description 6-19 .the front panel display card provides a means of monitoring operation of the Controller.the Front Panel Display Card provides a means for monitoring operation of the EBTS equipment. Alarms. and various diagnostic tests. It also provides support for performance and security management. and faults are sent as they occur. Configuration Management allows for parallel BR downloads. Status Indicators The following status indicators support the EBTS operations and maintenance functions: „ EBTS Indicators . MMI commands also provide a means to configure the control and RF cabinets for various system tests. Statistics are sent to the OMC-R every 30 minutes. the Subrated T1/E1 PCI card. the network. state events. These LEDs provide information on the status of the iSC Controller. providing the network operator a means of loading. and Site Reference ISA card. configuring. 6 EBTS Network Management The Network Management functions for the Radio Access Network are performed by the following: „ „ „ „ „ 6 OMC-R MMI Commands Status Indicators Event Logs Load shedding OMC-R As with other iDEN network elements. iSC . the OMC-R provides the capability to remotely monitor and maintain the EBTS. communication with the system is through the use of Man Machine Interface (MMI) commands and a service computer. MMI commands provide testing capabilities. This allows simultaneous software downloads to each BR in the EBTS and reduces downtime. Also. CPU usage. It is also possible to review the history of a resource or CRU using the information from system messages and hardware message logs. Load Shedding The load shedding mechanism involves memory usage. To use the system event log for diagnosing problems.0 05-Oct-07 . including: „ Maintenance messages (including messages related to the Resource Allocation Group (RAG) management and fault management) Fault management Location tracking of the Subscriber Unit (SU) „ „ Functional Description 6-20 6871000P02-A SR 16. the OS maintains a system log file of events. respectively. Status messages are reported to the OMC where they are received and stored for historical reference.the BRC monitors the functions of all the modules in the BR. Minor failures are indicated by a flashing red LED. A solid red LED indicates hard failures. iMU/EAS . are used to indicate the status of the EAS input alarms and relay outputs. such as several hours or even longer.three LEDs are provided to monitor the status of the iMU. The LEDs on the front panel indicate the status of the modules monitored by the BRC. „ Event Logs As with other iDEN Network Elements.Radio Access Network Details Enhanced Base Transceiver System „ BR . one LED is used to indicate that the iMU is powered on. including changes of state and failures of hardware Customer Replaceable Units (CRUs). Alarms will be used to indicate when the trigger points are reached. review log entries that were recorded over an interval of time. The load shedding algorithm uses three major priority categories. These status messages may be used to aid in system troubleshooting and diagnostics. and possibly queue sizes as a trigger. Input Active and Output Active. Two LEDs. .............. ...... . ... 7-16 I/O Blade Cards.... . ....... 7-6 Mixed Mode configuration ....... .. ..... ..... . .. . ........... . .... .. ..... ... . ... ..... ........................ 7-15 iCP Boards ....... .................. . .. ... .... ..... . ....... ........... .... .. .. .. ............. .... ......... ....... 7-9 iCP Function... ...... . 7-5 Interconnect Overview .......... ............. . ..... ........... .. 7-9 References ........ ... . ... ............. .... ...... ........... . 7-19 IP Footprint Reduction.............. ..... ......... 7-8 iBSC Functional Description .. ......... ........ ..... ... . . .. ... ........... . ... 7-22 iVPU Rolling Software Upgrade ............... . .... .... . 7-8 All Frame Relay... .... ............ .............. 7-9 iBSC Overview . ............... ....... ..... ......... ....... .................... . ...... .... ............................... . ..... .... .. ........ . ....... . .......... .. ... ................. ... ............ ....... . 7-5 Introduction .. . ...... ......................... ... . ....... ..... ... ... .. ... .. ............. 7-16 iVPU Components... ...... . . ........ .. ..................0 05-Oct-07 6871000P02-A Functional Description 7-1 ....... . .... .... ... 7-12 iBSC Hardware Description . .... .. ... .................. ...... ...... .... .. ... ....... .......... ................ .... ... .............. ... .. ... .. .. ....... ........ .... 7-5 NGD Features ....... . ... 7-12 iCP Components . . 7-21 iBSC Software Description .. .... .... . 7-4 Interconnect Subsystem Description ......... . .... .......... .. 7-12 iVPU Function .... ........ .... .. .... .. .... ........... .. ................. ... ................. ...... ........ .... ... . . . 7-7 Split Mode ....... .. 7-17 iVPU Front Cage Boards. .. . .. .......Chapter 7 Interconnect Subsystem Details In This Chapter Topic See Page Purpose.... ... ...... ........... ........ . 7-22 SR 16.......... ... .. ... .. ....... . .... ....... ............. .... .. ...... ....... .. ...... 7-21 iBSC Links and Interfaces ...... .............. 7-13 iCP Input/Output Shelf............. ... . . ..... 7-5 Next Generation Dispatch (NGD) Configurations. .... . ....... .... ..... ..... .... .... .... ....... . ... .......................... .... ... ... . ...... 7-24 Online Configuration Change ........ .. . . ..... ..... . .. 7-37 Monitored Events .... ......... . . .. ....... ........ ... .... Signal Interface ......... ......... ................. ... ....... .. . . . ... . .. ...... ... ....... . ... ............ 7-31 MLC Software Description ... ....... .. .. 7-23 iCP Configurations ... 7-33 Radio Protocol....... ......... ... ..... ..... ........ 7-32 Interworking Function (IWF) ...... 7-33 References ............ . .. ... . . . . .. ... .... ... ..... . . . . . .. ....... .... .... ..... . .......... ..... .. 7-31 MLC Hardware Description ...... .. . .... ........... .. ... ...... . . .. . ...... ...... .... . . .... .... .... ... .. .... .. . ........ 7-23 iCP Firmware Downloads...0 05-Oct-07 . ...... .. . ... . . ... .. ....... ... ....... .......... . . ... . .. 7-26 MSC Functionality.. .... . .. .... 7-34 IWF Software Description . ... 7-37 SDM/FT Overview ..... .............. . ... 7-34 IWF Hardware Description .. ... . . .... .. .... ...... .. .. 7-31 MLC Network Management ..... ... ... ....... .. ... . ..... .... .. ....... .... . .... .. ...... .. . .. ........ . .. . .. .. 7-33 IWF Overview . . ........ . ........... . . . .... ... . . .. ..... .... .. ...... ...... ..... ...... ..... 7-36 SuperNode Data Manager/Fault Tolerant (SDM/FT) .. ....... .... 7-38 Functional Description 7-2 6871000P02-A SR 16.. ....... ... .. ... . ..... ..... ..... .. .... .. ... ...... .. ........ ........ .. .. . 7-25 Mobile Switching Center Functional Description ........ ......... ................... . ..... 7-30 MSC Network Management . ....... . .. .. .. .... ........... . ... .............. ..... . ....... ..... ..... 7-37 Introduction .. .... ..... .. ..... 7-26 References ...... .. .Interconnect Subsystem Details iBSC Network Management .... ...... .. . ... ....... ...... .. ............ ....... ........ ....... . Home Location Register..... ... ...... ..... ...... ... ...... ..... ..... ... .... . ...... ... ... .... 7-25 OLCC Display and Logging... . . .... 7-30 Monitoring Center. .. .... ... 7-30 Mobile Location Center Functional Description ........ 7-24 OMC-R .......... .... . ..... .. . ..... ....... ... .... .. ... ..... . 7-25 PDR Warning . .. . ..... ..... ...... ..... Facilities Interface .................. . . . ... .. .. .... . ...... . .. .. . ... ...... . ... . ... 7-25 Virtual Router Redundancy Protocol .... .... ... ....... .... .. .. Core Processor ... . .... . ...... ..... ... . .... ..... ..... . 7-33 Introduction ...... ... . .... . ........ . ... .. ........... .... 7-25 iVPU LMT User Accounts... .. ... ..... . .............. . . ....... ...... .... .... . . .... . ....... ........... ......... . ........ 7-28 7-28 7-29 7-29 7-29 7-29 MSC Software Description ... ... .............. .. .... ..... ... ... . .... ......... .. . 7-26 MSC Hardware Description .. ... .... . .. ....... . . . .......... . . 7-38 SDM/FT Hardware Description ........ ....... ... . .. . .. ... ....... .. . .... . ............ 7-36 IWF Network Management . .. ...... . ........ .... .. .. .. . .... .................. . .. ...... ... . . ........ . . ... .. ... ..... ....... ... .......... .... . ...... 7-28 Switch Matrix . .. . . ... ......... ..... . Visiting Home Location Register .. ... ... .. 7-31 References .. .... . ... .. .. .... ........ ................. .. .... .. . .. .............. 7-37 References ... ... ............ ... .... . . . ... ... ......... ....... ..... . ......... ... .... 7-39 Call Intercept Provisioning Center....... . .......Interconnect Subsystem Details SDM/FT Software Description . .. 7-39 OMC-R ...................... ....... ........ ................ .... ...... 7-39 SR 16... . . ..0 05-Oct-07 6871000P02-A Functional Description 7-3 ................ 7-39 MMI Commands .... . ... ....... ........... ...... ... .. ..... ........ ...... ... .......... . . .. ........... 7-39 SDM/FT Network Management ......... ..... . . ........... Interconnect Subsystem Details Purpose Purpose This chapter describes the major network elements of the Interconnect subsystem in terms of their key hardware components. hardware and software descriptions.0 05-Oct-07 . software function. including its key functions. Each key component is explained. and network management facilities. 7 Functional Description 7-4 6871000P02-A SR 16. and the network management. similar to cellular telephone calling.determines Interconnect services and location information and also controls and routes the calls to other providers IWF (Inter-working Function) . With networked regions the SU can roam into those interconnected regions originating and receiving calls as if the SU is in its home system. and software information. 7 7 Interconnect Overview Interconnect calling.provides text message services VMS (Voice Mail Server) . allows a Subscriber Unit (SU) to travel freely throughout an iDEN system and communicate with other subscribers and landline systems. Split Backhaul.) SR 16.serves as an answering machine and stores messages for the SU. including functionality.provides circuit switched data services SMS (Short Message Service) . a user can originate or receive interconnect calls. „ „ „ „ „ „ Next Generation Dispatch (NGD) Configurations The Next Generation Dispatch provides higher capacity and greater system reliability in a significantly smaller footprint. or a combination of both configurations. (See Figure 7-1 NGD System on page 7-6. SDM/FT (SuperNode Data Manager/Fault Tolerant) . hardware.0 05-Oct-07 6871000P02-A Functional Description 7-5 . the services available to the SU.part of the Call Intercept System (CIS) that allows law enforcement agencies to obtain call data records as well as intercept audio in an Interconnect phone call for court authorized monitoring. It also indicates when voice mail is present.sends and receives voice data EBTS (Enhanced Base Transceiver System) .converts the radio link to the land link and discriminates between interconnect and dispatch calls BSC/iBSC (Base Site Controller / iDEN Base Site Controller) . It supports All Frame Relay (AFR). The system tracks the location of the SU.Interconnect Subsystem Details Interconnect Subsystem Description Interconnect Subsystem Description Introduction This section describes the iDEN Interconnect subsystem.routes interconnect packets between the EBTS and the MSC MSC (Mobile Switching Center) . and the routing of calls to/from the SU as it travels throughout the system. Within this extended network. The major Network Elements involved in an Interconnect call are: „ „ 7 SU (Subscriber Unit) . iVPU hardware operating with only Dispatch and Packet Data functions. iVPUi .Interconnect transcoding. „ Single Software Load One iVPU software load supports the following: Œ Interconnect Transcoding Œ Dispatch Intra-Urban Dispatch Audio Routing and Duplication (APD) Œ Dispatch Inter-Urban Dispatch Audio Routing and Duplication (iDAC) Œ Frame Relay and IP Inter-working „ One Network Element from the perspective of the OMC The NGD architecture supports various configurations.) The iVPUd supports Split Mode Backhaul EBTSs only. Supports Split Backhaul EBTSs only.Interconnect Subsystem Details Interconnect Subsystem Description Figure 7-1 NGD System NGD Features The main changes to the iDEN network with the NGD system are: „ The iVPU is designated with respect to its configuration: Œ Œ Œ iVPUd .Software upgrade to support Dispatch and Packet Data functions in addition to Interconnect transcoding. Supports Split Backhaul and AFR Backhaul EBTSs. iVPUdi . (There is no Interconnect transcoding.0 05-Oct-07 . including: Œ Mixed Mode Œ Split Mode Œ All Frame Relay (AFR) Functional Description 7-6 6871000P02-A SR 16. Software upgrade of iVPUs in the field default to this mode. .g. In the mixed mode phase of the iDEN architecture. DAPs. iVPUs). iDACs) and new NGD network elements (e.. Figure 7-2 Mixed Mode Configuration SR 16. BSCs.) In the NGD configuration. Mixed Mode is a system configuration that is characterized by a mixture of Legacy network elements (e. the network elements that are required for Next Generation Dispatch are migrated into the Legacy architecture. along with dispatch and packet data services.Interconnect Subsystem Details Interconnect Subsystem Description Mixed Mode configuration Between Legacy and Next Generation Dispatch architecture.0 05-Oct-07 6871000P02-A Functional Description 7-7 . HADAPs. an iVPU can be configured as: „ „ „ iVPUi (for Interconnect only) iVPUd (for Dispatch only) iVPUdi (for Interconnect or Dispatch) This depends upon the system configuration. The difference between the iVPUi and iVPUdi is that the iVPUi only supports interconnect for split backhaul sites whereas the iVPUdi supports interconnect for both split backhaul and AFR backhaul sites. the Mixed Mode network is considered a transitional phase. APDs.g. (See Figure 7-2 below. These network elements can coexist with the legacy network elements. Interconnect Voice traffic can terminate on either a legacy XCDR. (See Figure 7-1 NGD System on page 7-6.) Figure 7-3 Split Mode Configuration All Frame Relay AFR is supported in both Mixed Mode and in the final NGD configurations. MDG. and interconnect voice traffic being carried by circuit switch channels and dispatch traffic being carried by a Frame Relay channel. iVPUd. iVPUi. The Mobis and SNMP channels must terminate on an iCP or legacy BSC.Interconnect Subsystem Details Interconnect Subsystem Description Split Mode The NGD network also supports the Split Mode site configuration which is characterized with Mobis. or iVPUdi.0 05-Oct-07 . or iVPUdi. AFR trunks carry signaling.) Functional Description 7-8 6871000P02-A SR 16. (See Figure 7-3 below. interconnect. SNMP. dispatch and packet data traffic over Frame Relay. The Frame Relay traffic can terminate on a legacy DAP. Interconnect Subsystem Details iBSC Functional Description iBSC Functional Description This section describes the iDEN Base Site Controller (iBSC). 7 References The following is a list of technical documentation and training courses that support the Legacy BSC: „ „ „ „ „ „ „ „ Interconnect Fundamentals Course (FND105) Interconnect Operations & Maintenance Course (OPM207) iBSC Operations & Maintenance Course (OPM214) iDEN System Recovery Topics Course (ADV401) Interconnect Troubleshooting Guide (6881012Y80) iBSC Hardware Manual (68P1001Y77) iBSC Health Check (HC04003) Legacy BSC to iBSC Reference Guide (WP 04008) These documents are available on the Motorola Extranet web site at http://mynetworksupport.com unless otherwise stated. including hardware and software descriptions and network management information. and addresses cost concerns for maintaining legacy platforms due to end-of-life issues.0 05-Oct-07 6871000P02-A Functional Description 7-9 .motorola. increases availability. See Figure 7-4 iBSC in the iDEN Network on page 7-10. The iBSC presents technology that increases the Erlang capacity per square foot. 7 SR 16. iBSC Overview The iBSC is a network element in the Interconnect portion of the Mobile Switching Office (MSO) of the iDEN system. Interconnect Subsystem Details iBSC Functional Description Figure 7-4 iBSC in the iDEN Network The iBSC consists of an iCP (iDEN Call Processor) and two iVPUis (iDEN Voice Processing Unit(s). and tear down calls and provides handover support and control in Mobility Management. provides subrate allocation. and so on.0 and later. It is a configurable network element. (See Figure 7-5 iBSC Architecture on page 7-11. The iVPUi controls the voice traffic. maintain. Functional Description 7-10 6871000P02-A SR 16. Note that the iVPUi is the same element with the same capabilities as the legacy iVPU. It continues to support Interconnect and can now support Dispatch and Packet Data.) Only the name has been changed to identify it as an Interconnect element. the iVPU becomes more important to the overall iDEN network. This includes compressing voice traffic being sent to the mobile while decompressing voice traffic being sent from the mobile. It transcodes between VSELP/AMBE to PCM audio.0 05-Oct-07 . The iCP controls the signaling necessary to set up. With the rollout of SR14. 0 and later. up to 176 AFR sites are supported. the iBSC supports a maximum of 384 split-mode sites.) Figure 7-6 iBSC Coverage SR 16. (See Figure 7-6 below. The maximum number of All Frame Relay (AFR) sites supported has not increased.0 05-Oct-07 6871000P02-A Functional Description 7-11 . As in earlier releases.Interconnect Subsystem Details iBSC Functional Description Figure 7-5 iBSC Architecture With SR15. iBSC Hardware Description Each of the iBSC components is housed in its own cabinet/frame.Interconnect Subsystem Details iBSC Functional Description iCP Function The iCP performs the same functions as in legacy networks. Vocoder Bypass for Mobile-to-Mobile calls of the same type. See Figure 7-7 iBSC Hardware on page 7-13.0 05-Oct-07 . maintain. and Circuit Data Calls The iVPU performs transcoding between VSELP/AMBE++ to PCM audio. „ „ Functional Description 7-12 6871000P02-A SR 16. The iBSC consists of a combination of one iCP and two iVPUis. converting the VSELP or AMBE++ voice packets used on the radio link to the Pulse Code Modulation (PCM) used by local and interconnected Public Switched Telephone Networks (PSTN). and tear down interconnect calls Provides handover support and control in Mobility Management Conversion of radio link to land network format Control Transcoder audio „ „ „ iVPU Function The iVPUi also performs the same functions as in legacy networks. TTY Baudot and Circuit Data Calls. The iVPUi frame/cabinet consists of two iVPUi nodes. audio path setup. EBTS Span audits. TTY Baudot. including: „ Controls the signaling necessary to set up. The iCP frame/cabinet in a standard configuration consists of two iCP nodes and an I/O shelf. subrate allocation. The iVPU also performs: „ „ „ „ Subrate allocation EBTS span audits Audio path setup Vocoder bypass for mobile-to-mobile calls of the same type. The component specifications include the following: „ 7 iCP refers to 2 Unix Nodes and 1 I/O cage in an Active-Active (with one of the Nodes as Supervisor) Configuration iCP Node: refers to 1 of the 2 Unix Nodes which comprise the iCP iVPUi refers to a single iVPUi shelf with a maximum of 15 BPP2 cards (BPP2 refers to the transcoder card). MOBIS.Interconnect Subsystem Details iBSC Functional Description „ The iBSC may co-exist on the same MSC and OMC with legacy BSC equipment.0 05-Oct-07 6871000P02-A Functional Description 7-13 . nor can an iVPUi be paired with a legacy CP. iBSC Hardware Figure 7-7 iCP Components The iCP consists of: „ One I/O shelf provides for the termination of the T1/E1 spans carrying the SS7. however the iCP cannot be paired with a legacy EXCDR. and SNMP Two Server Nodes manage the call signaling and voice paths between the EBTS and the iVPUi or iVPUdi (load balanced) „ SR 16. Interconnect Subsystem Details iBSC Functional Description See Figure 7-8 iCP Frame Layout on page 7-14 for details. Figure 7-8 iCP Frame Layout Functional Description 7-14 6871000P02-A SR 16.0 05-Oct-07 . SS7 and LAPD Protocol Support iCP I/O Shelf „ „ „ „ „ „ „ „ Figure 7-9 SR 16.Interconnect Subsystem Details iBSC Functional Description iCP Input/Output Shelf The iCP I/O shelf (see Figure 7-9 iCP I/O Shelf on page 7-15) consists of the following: „ The iCP I/O shelf provides termination of the T1/E1 spans hosting the MTL. 2 for SS7 and 0 to 4 for site traffic (LAPD). and SNMP RSL links. Mobis RSL. T1 Termination Solution for Dual Node iCP Switch Cards . All I/O shelf cards are hot swappable. The I/O shelf supports dual -48VDC power feeds. each capable of terminating up to 8 T1 or E1 spans. Can have between 2 and 6 I/O Blades.Redundant Ethernet Connectivity (to iCP nodes) MGMT card – Intelligent Platform Management Interface (IPMI) Support T1 cards .0 05-Oct-07 6871000P02-A Functional Description 7-15 . redundant (2) switch Blades. The internally packet switched I/O shelf consists of a management Blade. as part of SR 15. IP Switch card I/O Blade card I/O Blade Cards With SR 15. Processes either LAPD (Link Access Protocol on D-Channel) or SS7 traffic which is terminated at the Rear Transition Module. Local movement of the RSL cards via the LMT is no longer supported. no RSL cards are required. and are used to gather. Note If all EBTS sites are connected through AFR trunks.0 05-Oct-07 . The number of cards or configuration of MTL2 cards has not changed. the RSL board and slot ID must be configured from the OMC. A complete 24 10/100 and 2 Gigabit Ethernet switching subsystem that performs all switching functions with a throughput of up to 6.) Also.0. and monitor systems status over the IPMI bus.0. The MTL2 cards remain installed in slots 1 and 2. the number of RSL cards may range from 0 to 4. control.6 million packets-per-second. Functional Description 7-16 6871000P02-A SR 16. (See Figure 7-10 below.Interconnect Subsystem Details iBSC Functional Description iCP Boards The iCP contains the following boards (see Table 7-1 iCP Board Functions on page 7-16): „ „ „ Alarm Management Controller (AMC) IP Switch cards IO Blade (also known as Payload cards) Table 7-1 iCP Board Functions Card Functions AMC Hot-swappable boards provide for N+1 redundancy. Each RSL card may be installed in any slot between 3 and 9. Interconnect Subsystem Details iBSC Functional Description Figure 7-10 RSL Configurations Table 7-2 indicates the number of RSL cards required to support a range of split mode sites. The iVPU frame has the following major equipment areas: „ „ „ Top of cabinet I/O panel DC power distribution iVPU cages (lower and upper) front and rear SR 16. each independent of one another. A midplane provides the communication between all modules.288 289 . Each cage is an integral product.0 05-Oct-07 6871000P02-A Functional Description 7-17 . which houses a common platform and iVPUspecific Circuit modules. Table 7-2 Split Mode RSL Card Configuration # of Split Mode # of Required RSL Cards Sites 0 (all AFR sites) 1 .192 193 .96 97 .384 0 cards 1 card 2 cards 3 cards 4 cards iVPU Components The iVPU frame houses two iVPU cages. 0 05-Oct-07 .Interconnect Subsystem Details iBSC Functional Description An iVPU frame is equipped with two iVPU cages is populated with cards depending upon the configuration (1 iCP connected to 2 iVPUs). by adding 2 iVPU cages along with the iCP. Figure 7-11 iVPU Components Functional Description 7-18 6871000P02-A SR 16. This can be done by adding more Bearer Payload Processor (BPP2) cards for more voice processor circuits. as well as at the iVPU pool level. (See Figure 7-11 iVPU Components on page 7-18.) Expanding iVPU capacity is done at the iVPU cage level. and the voice processing capacity required. Interconnect Subsystem Details iBSC Functional Description iVPU Front Cage Boards The iVPU front cage contains the following cards: „ „ „ „ „ Circuit Breaker Module (CBM) Power Supply Module (PSM) Customer and Cabinet Alarm (CCA) card Interface Switch Board/System Processor card (ISB/SPROC) Bearer Payload Processor2 (BPP2) card Fan Module Figure 7-12 provides the layout of the boards and modules in the front cage of the iVPU.0 05-Oct-07 6871000P02-A Functional Description 7-19 . Figure 7-12 iVPU Front Cage The iVPU rear cage contains the following cards: „ „ Alarm I/O (AIO) card Dual Gigabit Ethernet (DGBE) card SR 16. network interface. Figure 7-13 iVPU Rear Cage The following table (Table 7-3) provides the iVPU board descriptions: Table 7-3 iVPU Board Functions Board Name Function CBM PSM CCA Contains seven 20A Circuit Breakers that provide current overload protection. and all payload cards. Implements the Hub connecting the SPROC. A DC–DC converter Payload card that provides the alarm and status monitor and control interface between the ISB/ SPROC and other iVPU plug–in cards/modules. and supports O&M and centralized call processing activities in the iVPU cage.Interconnect Subsystem Details iBSC Functional Description „ Dual Optical Channel Layer-3 (DOC3) card The Figure 7-13 iVPU Rear Cage on page 7-20 provides the layout of the boards in the rear cage of the iVPU.0 05-Oct-07 . ISB/SPROC Functional Description 7-20 6871000P02-A SR 16. and PSTN and SNMP for operational management to and from the EBTS sites and the OMC. which synchronize clock/timing signals on iVPU cards. iVPUdi. The interfaces are used to transport control signaling between the iVPU and other subsystems through the external Ethernet switch. etc. It also provides BITS interface for external clock source inputs. Provides the external interface for customer alarm equipment input/output to/from the CCA cards located in the iVPU cage. including iVPUi. Provides Gigabit Ethernet 1000BaseT LAN interfaces between external Catalyst Ethernet switches and the Interface Switching Board (ISB) located in the iVPU cage. SS7 for call set-up and tear down to and from the switch.Interconnect Subsystem Details iBSC Functional Description Table 7-3 iVPU Board Functions (continued) Board Name Function BPP2 Payload card containing a multipurpose processor and an array of DSPs configured to support vocoder processing (speech compression.0 significantly reduces the number of IP network addresses required by the iVPU. Provides dual OC3 links between the MSC/Digital Cross-connect Switch (DCS) and the iVPU cage. SR 16. It also transfers optical data from/to the iVPU payload cards (BPP2) via 15 (fifteen) High-speed Circuit Interconnect (HCI) interfaces. It impacts all versions of the iVPU.) of the bearer channels Provides cooling airflow for the iVPU cage and its plug–in cards. The iVPUs enabled with the IPFR feature enable the use of the following IP addresses: „ „ Each ISB is assigned an external IP address The external logical SPROC is assigned an IP address A total of 5 or 8 IP addresses are consumed by the iVPUi. iBSC Links and Interfaces The links for the legacy BSC and iBSC are virtually the same. These links are Mobis for call set-up and tear down to and from the radios. See Figure 7-14 iBSC Links and Interfaces on page 7-22 for more detail. rate adaption. and iVPUd.0 05-Oct-07 6871000P02-A Functional Description 7-21 . Fan Module AIO DGBE DOC3 IP Footprint Reduction The IP Footprint Reduction (IPFR) feature in SR 15. the configuration data. Required configuration changes should be applied to both nodes at the same time. will be identical. Because each node is providing the same services. which will result in a loss of capacity. 7 iVPU Rolling Software Upgrade The iVPU Rolling Upgrade (RUP) feature enables the user to upgrade an iVPU to a new software release with zero downtime. Functional Description 7-22 6871000P02-A SR 16. However. with the exception of the nodal identifiers. coded voice to and from the radios and PCM to and from the switch will be sent over wire from the radios and over fiber to the MSC. This means that the platform will remain in service and continue to process calls.0 05-Oct-07 . Figure 7-14 iBSC Links and Interfaces iBSC Software Description Each iCP node requires its own software and configuration data. Links between the call processors and voice processors support control and maintenance functions that are carried over wire or are delivered in packets on a LAN. individual cards will be taken out of service.Interconnect Subsystem Details iBSC Functional Description In addition. Configuration changes that are not on-line changeable should be performed one node at a time to avoid an entire iCP outage. calls on the BPP2 that are upgraded would be interrupted. such as call setups and handovers. These include the following: „ „ „ ISB/SPROCs CCAs DOC3s Upon transition of the ISB/SPROC active state.Interconnect Subsystem Details iBSC Functional Description A key prerequisite to a successful rolling software upgrade is compatibility between the running software and the new software. It is recommended that upgrade is performed during the maintenance window to reduce end user interruptions. a momentary loss of IP connectivity may effect interconnect calls that are “in transition”. „ 2N redundant boards are upgraded one at a time. The OMC-R should not allow initiation of a rolling software upgrade unless the two releases are compatible. the iVPUi continues to provide interconnect service.0 05-Oct-07 6871000P02-A Functional Description 7-23 . However. iBSC Network Management The Network Management functionality on the iCP and iVPU is similar to that of the legacy BSC: „ „ „ 7 Supports iCP pair related configurations The iCP and iVPU are included in the OMC System Status Display The iCP does not take software downloads from the OMC Œ Œ Software upgrades are performed via a CD ROM drive resident on each iCP node Application level patches may be sent to the iCP via FTP iCP Configurations Network Management of the iCP platform provides the capability to: „ „ „ „ Download configuration data Store and upload statistics Perform time synchronization with the OMC-R Report alarms and state change events to the OMC-R SR 16.4 for an iVPU configuration and the same guidelines apply for the iVPUi mode: „ As FRUs are software upgraded. RUP was introduced in SR13. 0 05-Oct-07 . The io_versions command displays the shelf and card software versions and status.0. You must specify the iCP card slot or fan number. the LMT operator may upgrade the iCP firmware using two new commands: io_upgrade and io_versions.Radio (OMC-R) performs the following functions on the iBSC (and other iDEN network elements): „ „ „ „ „ Configurations Upgrades Optimizing Monitoring Reports alarms and state change events Functional Description 7-24 6871000P02-A SR 16. Each iCP Node is managed independently and includes the following support: „ „ „ „ „ „ „ Treated as a separate NE Managed by the same OMC-R Supporting all applicable configuration Fault Performance Time LMT functionality iCP Firmware Downloads Effective with SR 15.Interconnect Subsystem Details iBSC Functional Description The iCP is considered a single entity in the following areas: „ „ Configuration Fault management Required iCP configuration changes should be applied to both nodes at the same time. OMC-R The Operation and Maintenance Center . The io_upgrade command performs a firmware upgrade for a specific iCP card or fan. Configuration changes that are not on-line changeable should be performed one node at a time to avoid an entire iCP outage. iVPUs can propagate their user accounts to other iVPUs. Similar to Hot Standby Router Protocol (HSRP).0 05-Oct-07 6871000P02-A Functional Description 7-25 . the LMT account master knows the IP addresses for all iVPUs in the urban. Virtual Router Redundancy Protocol Virtual Router Redundancy Protocol (VRRP) supports high availability for IP hosts in a LAN. In addition to its user accounts file. It also provides the mechanism to change the allocated system parameters without re-initializing the network element off-line. In addition.Interconnect Subsystem Details iBSC Functional Description Online Configuration Change The Online Configuration Change (OLCC) feature allows network operators to change the iDEN system configuration while the system continues to process calls. In addition. PDR Warning The Packet Data Region (PDR) Warning is a new message that indicates a potential service problem. One iVPU is selected as the LMT user account master for the urban. The PDR warning message prevents this from occurring. VRRP creates a simple failover capability for a VRRP group. SR 16. OLCC Display and Logging The OLCC changes being applied will be displayed at the LMT when the OLCC switch occurs. The account master iVPU can “synchronize” the user account files for all iVPUs in the urban. If an operator connects a new EBTS site to an iBSC and a packet data region is controlled by different OMCs. the OLCC changes will be placed in the iVPU customer log. The OLCC provides the capability to change the iDEN system configuration while network elements are online processing calls. iVPU LMT User Accounts Admin LMT users may create and maintain user accounts on each iVPU. packet data service will not work. In the case where a new site is associated with an iBSC and DAP is mapped to different OMCs. thereby reducing the overall scheduled configuration change outage time for the iDEN network. the interconnect service is supported but packet data service is not supported. iVPUs support Open Shortest Path First (OSPF) and VRRP for high availability. Either technique may be configured in each iVPU. The message will describe the OLCC add/modify/ delete action and whether it was successful. The switch is generic in nature and is dependent upon the various software packages used to determine its function.0 05-Oct-07 .motorola. Signaling . It is often referred to as message links. including hardware and software descriptions and network management information. Message .Interconnect Subsystem Details Mobile Switching Center Functional Description Mobile Switching Center Functional Description This section describes the Mobile Switching Center (MSC). The MSC has basic functionality as well as specific functions in the iDEN system (see Figure 7-15 MSC in the Interconnect Subsystem on page 7-27).com unless otherwise stated. a gateway switch.the information sent between Central Offices and the BSC/iBSC and EBTS for digit transmission and call details for billing. The MSC is a Nortel Digital Multiplex System-100 Family product.the internal information sent by the entire DMS (Digital Multiplexing Switch) switch for call setup. MSC Functionality The MSC is a GSM-based mobile telephone switch that provides Interconnect services by serving as an interface between the mobile network and the PSTNs of other service providers. Each MSC provides service within a geographic coverage area. and a single iDEN urban may contain more than one MSC. The information is only passed through a peripheral module and the network. SS7 signaling controller. „ „ Functional Description 7-26 6871000P02-A SR 16. as well as a database controller. These include: „ 7 Speech . 7 References The following is a list of technical documentation and training courses that support the MSC: „ „ MSC Planning and Expansion Guide (68P80801A10) MSC Optimization (68P80801A20) These documents are available on the Motorola Extranet web site at http://mynetworksupport. a wireless switch.the information sent by the customer from one location to another. The MSC can function as a landline switch. 0 05-Oct-07 6871000P02-A Functional Description 7-27 .Interconnect Subsystem Details Mobile Switching Center Functional Description Figure 7-15 MSC in the Interconnect Subsystem Additional functions include: „ „ „ „ „ „ „ „ „ „ „ Control and interface to the PSTN Call processing for Interconnect calls Echo cancellation for voice calls (with associated equipment) Provisioning of subscriber supplementary services Authentication of subscriber units Intra-system roaming and/or handover between BSCs/iBSCs Inter-system roaming and/or handover between MSCs Billing record collection Interface to a customer-supplied billing system Control of IWF for data networking Interface to the Voice Mail System SR 16. Figure 7-16 MSC Components 7 Switch Matrix This is a set of digital cross connections between input and output lines that represents the path to be followed for a particular call setup.000 lines may be attached to the switch matrix. The MSC includes the components shown in Figure 7-16 below.Interconnect Subsystem Details Mobile Switching Center Functional Description MSC Hardware Description The MSC is configured several ways using a variety of add-on modules. Core Processor The Core Processor is a CPU that interprets signaling from the external PSTN and the iDEN network equipment to identify. Functional Description 7-28 6871000P02-A SR 16. service. The design of the matrix uses E1 style connections. Up to 60. Digits dialed by land users or iDEN mobile users are ultimately used by the core module to make the connection the user desired.0 05-Oct-07 . authenticate. It also communicates with other intelligent nodes in the iDEN network to coordinate the iDEN network-wide setup of communications circuit paths between mobile users and land telephone users. and route call signaling and traffic in the MSC. All interconnect signaling from the PSTN and the iDEN system passes through the LLP. The HLR performs Subscriber Access Control. Signal Interface The Link Peripheral Processor (LLP) is the signaling interface of the MSC.0 05-Oct-07 6871000P02-A Functional Description 7-29 . The HLR may be implemented as part of the MSC or as a separate computing system. The core processor reads this location register database to check SU authorization and location information it requires for call setup. It is queried each time an interconnect call is initiated or interconnect call features are requested and the VLR does not contain an entry. containing the IDs and the most recent location information on each iDEN Subscriber Unit (SU). The DTC is the interface between the external T1/E1 trunks. Specialty markets are also supported with other tailored DTC cards. Visiting Home Location Register The Visitor Location Register (VLR) is the location and activity database of the MSC. The DTC cards may be one of two types: T1 for North American markets and E1 for International markets. The Spectrum Peripheral Module (SPM) is an upgraded external interface used to interface OC-3 fiber optic trunks. and the Switch Matrix. The MSC manages access to the system by verifying requests for service against a database of subscriber privileges. The DTC is the interface between the MSC. DTCs and SPMs can co-exist.Interconnect Subsystem Details Mobile Switching Center Functional Description Facilities Interface Both iDEN system span line and the PSTN transport facilities (T1 and/or E1) are connected to the MSC through Digital Trunk Controllers (DTCs). SR 16. and the external world. The Signalling and data span lines of the T1/E1s are split off and connected to the switch matrix for telephony data and the LLP for signal processing. T1 or E1 telephony connections may be hardwired to the DTC. Home Location Register The Home Location Register (HLR) is the location where every Subscriber Unit's permanent subscriber records are stored. The HLR database also contains Mobile Station Identification data and Fixed Network Data.The exact number will depend on the market and system configuration as specified by planning and capacity. the iDEN system. All SU identities and the various supplementary services are provisioned in the HLR. the Core Processor. Each user who wants to gain access to the MSC switch has to go through a LOGIN process. 7 MSC Network Management The MSC has its own monitoring system and is not monitored through the OMC. and services. a user interface screen is displayed. Monitoring Center The Monitoring Center is the site where all call intercept data is collected. This monitoring is done with the MSC Maintenance and Administration Position (MAP) Terminal. Access is restricted to authorized users by means of user names and passwords that are recognized by the switch.Interconnect Subsystem Details Mobile Switching Center Functional Description The VLR is a fast-access database storing data about the SU units that are now or have been recently active. The command and utility interface is accessed through a login process. Motorola does not provide any of this equipment.0 05-Oct-07 . Each port into the switch is a data circuit. 7 Functional Description 7-30 6871000P02-A SR 16. The VLR speeds call setup because the entire HLR subscriber database that is located on disk is not searched. permissions. MSC Software Description The MSC Core Processor runs the Switching software for the iDEN network. All users of the switch are connected to the switch through a card and port. Once a user identity and password are successfully entered. All monitoring and recording equipment in located here. It is a fast look up for Interconnect calls. The MLC processing units are SUN Netra units. „ SR 16. The MLC uses the Nortel Networks Universal Signaling Point (USP) to communicate with the SS7 network.Input to the MLC database can use a CORBA interface that includes methods for reading and writing subscriber data. 7 MLC Hardware Description The MLC is a high-availability. The MLC: „ „ „ consists of software and/or hardware offering location service capabilities accepts requests. It is provided by a third-party vendor which supports the product. The specific MLC entities are: „ „ Gateway Mobile Location Center (GMLC) Serving Mobile Location Center (SMLC) These network elements can be deployed separately or in combination. An MLC is part of a standard cellular network as defined by GSM and 3GPP specifications.Interconnect Subsystem Details Mobile Location Center Functional Description Mobile Location Center Functional Description This section describes the Mobile Location Center (MLC).SNMP is an industrystandard interface for fault management and performance monitoring. including hardware and software descriptions and network management information. MLC Software Description The following are the Industry Standard Software supported on the MLC: „ 7 CORBA (Common Object Request Broker Architecture) . CORBA is a machine-to-machine interface with a well-defined protocol. using the Solaris operating system on a SPARC platform. and responds to the received requests consists of location service components which are distributed to one or more Public Land Mobile Networks (PLMN) and/or service providers. SNMP (Simple Network Management Protocol) .0 05-Oct-07 6871000P02-A Functional Description 7-31 . scalable central office platform for determining the physical location of a handset in a cellular telephone network. services requests. 7 References Technical documentation that supports the MLC is available from the vendor. alarms. Sun Microsystems Solaris . The purpose of the SDK is to provide developers with a tool kit.Interconnect Subsystem Details Mobile Location Center Functional Description „ XML (Extensible Markup Language) . The OAM Processing Unit collates and stores all the information needed to monitor the MLC such as Logs. and Maintenance function of the MLC resides on the SunNetra Servers. performance.XML is the universal format for structured documents and data on the internet. which allows development and testing of applications without interfacing directly with the MLC.The Solaris Operating Environment is acknowledged by the industry to be the premier UNIX environment for SPARCTM and Intel Architecture systems.The SDK provides information needed to develop location-based applications that can interface to the MLC. „ „ MLC Network Management Operation. audit. It is similar to HTML.0 05-Oct-07 . and location event records. SDK (Software Development Kit) . 7 Functional Description 7-32 6871000P02-A SR 16. Administration. It is a set of guidelines for designing text formats for producing files that are easy to generate and read. The IWF provides a modem bank that allows data transmitted from data devices on an external network to access SU and RF modems. IWF Overview The Inter-Working Function (IWF) performs the data-rate adaptation between the PSTN and the iDEN system.com unless otherwise stated.0 05-Oct-07 6871000P02-A Functional Description 7-33 . including hardware and software descriptions.Interconnect Subsystem Details Interworking Function (IWF) Interworking Function (IWF) Introduction This section describes the Interworking Function (IWF). 7 7 References The following is a list of technical documentation and training courses that support the IWF: „ „ „ „ Interconnect Fundamentals Course (FND105) Interconnect Operations & Maintenance Course (OPM207) IWF Installation Manual (68P80800E10) IWF System Release Implementation Manual (68P80802B05) These documents are available on the Motorola Extranet web site at http://mynetworksupport. Consisting of hardware and software elements. facsimile and dial-up networking.motorola. The IWF terminates the PCM digital data format such as Teletype (TTY). the IWF (Inter-working Function) platform has the following functionalities (see Figure 7-17 Interworking Function Services on page 7-34): „ „ „ 7 Provides circuit switched data services Serves as a translation and conversion point Allows an end-to-end connection between an SU and a remote device such as a dial-up modem Provides required rate adaptation between the SU and PSTN or between two SUs Œ „ This allows subscribers to connect a laptop computer or fax machine directly to an iDEN SU to provide wireless modem and fax data capabilities SR 16. and network management information. Functional Description 7-34 6871000P02-A SR 16.0 05-Oct-07 . IWF Hardware Description The IWF has either one or two nodes per chassis.Interconnect Subsystem Details Interworking Function (IWF) Figure 7-17 Interworking Function Services Radio Protocol Radio Link Protocol (RLP) is the method of transferring compressed character data between the Mobile Subscriber and the MSC-IWF during Circuit Switch data networking. depending on the number of ports in the configuration: „ „ 7 48/60 ports IWF consist of 2 nodes per chassis 24/30 ports IWF consist of 1 node per chassis See Figure 7-18 IWF Front View on page 7-35 for the front view and Figure 7-19 IWF Back View on page 7-35 for a view of the back of the IWF. Interconnect Subsystem Details Interworking Function (IWF) Figure 7-18 IWF Front View Figure 7-19 IWF Back View The signaling interface between the MSC and the Interworking Function (IWF) occurs through Ethernet Interface Units (EIU) in the Link Peripheral Processor (LPP) in the MSC.Communications from the Network to IWF Network side supports connection between a fixed modem and IWF element SR 16. The IWF functions can be divided into two elements: „ Network Inter-working Trunk (NIT) .0 05-Oct-07 6871000P02-A Functional Description 7-35 . 7 IWF Network Management The Interworking Function software is loaded from a Host computer that is capable of File Transfer Protocol (FTP) transfers. Access to the software can be from a laptop using an internet browser such as Netscape or MS Explorer. while the network side of operations is referred to as the Network-side IWF Trunk (NIT). contains all IWF Code Objects necessary to correctly upgrade/install.Communications from the SUs to the IWF Mobile side supports the iDEN protocol connection to the SU The IWF function can be split into two separate sections. the mobile side and the network side.15. and operate the iDEN IWF. currently IWF 04. initialize. IWF Software Description The Interworking Function Software Release.Interconnect Subsystem Details Interworking Function (IWF) „ Mobile Inter-working Trunk (MIT) . The mobile side is referred to as the Mobile-side IWF Trunk (MIT).05. MITs and NITs are configured to work as an element within the circuit switch function.0 05-Oct-07 . 7 Functional Description 7-36 6871000P02-A SR 16. Interconnect Subsystem Details SuperNode Data Manager/Fault Tolerant (SDM/FT) SuperNode Data Manager/Fault Tolerant (SDM/FT) Introduction This section describes the SuperNode Data Manager/Fault Tolerant (SDM/ FT). Call Intercept Provisioning Center (CIPC) . 7 7 References The following is a list of technical documentation and training courses that support the SDM/FT: „ „ „ Interconnect Fundamentals Course (FND105) Interconnect Operations & Maintenance Course (OPM207) Understanding iDEN System Fault Tolerance .motorola. and billing.0 05-Oct-07 6871000P02-A Functional Description 7-37 .provides the point of access for a law enforcement agency to log into the system and obtain interconnect voice data. „ SR 16. including hardware and software descriptions and network management information. customer provisioning.com unless otherwise stated.provides a web interface to provision surveillance information. This access allows Interconnect surveillance. the CIPC provides the surveillance ID and password for the law enforcement agency to gain access to the surveillance. the CIPC informs the SDMs of the presence of the new warrant. Also as a part of the warrant provisioning. SDM/FT Overview The SDM/FT (most commonly referred to as SDM) manages data formatting and provides a point of access to the switch. The SDM/FT provides a surveillance capability in the iDEN Interconnect subsystems. Surveillance of communications may involve delivery (to law enforcement) of a combination of: „ „ „ 7 Call identifying information Call content information (digital voice) Location information There are three primary elements used to provide this service: „ SuperNode Data Manager (SDM) . Once the information has been submitted.Interconnect subsystem (WP2002-021) These documents are available on the Motorola Extranet web site at http://mynetworksupport. Interconnect Subsystem Details SuperNode Data Manager/Fault Tolerant (SDM/FT) „ Law Enforcement Monitor (LEM) . Once those are stored. Both feeds are normally operational. If a module in one of the domains malfunctions. SDM/FT Hardware Description The SDM/FT is a dedicated multi-application Operations Administration and Maintenance processor that supports the MSC.0 05-Oct-07 . It is then sent to the Monitoring Center as Call Data Records (CDRs) over X. then collect and store the audio and data about the calls under surveillance. This ensures uninterrupted cooling during servicing of a fan tray. 7 Functional Description 7-38 6871000P02-A SR 16.provides the ability to log into the SDM/FT with a surveillance ID and password. the unaffected domain continues to provide all required services uninterrupted. SDM/FT hardware is divided into two domains that mirror each others functionality to achieve fault tolerant operation. the corresponding module in the second domain takes over the operations without service interruption. and sets up a “listen-only” bridge connection to the Monitoring Center. Power is provided by two separate battery feeds supplied from the separate breakers. The data is sent to the attached SDM. Monitored Events The call content of the intercepted call is delivered to one or more monitoring centers through PET7 (ANSI/ETSI-ISUP) trunks from the DMS-MSC. The call data of the intercepted call originates at the MSC or HLR. The MSC selects an idle trunk member from the observation group. where the data records are formatted according to the legal requirements of the market area. Each SDM/FT is connected to one MSC or HLR. The fan trays provide cooling to the cabinet and are powered by separate battery feeds. During a single feed failure.25 or Ethernet data lines. The system modules are provisioned in pairs. the LEM must be able to decode the audio and data into some format usable by the agency in court. The CIPC performs the following functions: „ „ „ Starts monitoring Stops monitoring Queries monitoring information SR 16. The functions include the following: „ Automatic configuration parameters validation to catch errors that might cause an outage The capability to perform network management functions remotely. and remote switch to a standby unit for faulty network elements Remote login to access other network element and perform diagnostics and failure recovery procedures „ „ Call Intercept Provisioning Center The Call Intercept System (CIS) management is handled by the Call Intercept Provisioning Center (CIPC). software installation and upgrades. 7 SDM/FT Network Management The SDM/FT operations and maintenance functions are provided by the following: „ „ „ 7 OMC-R MMI commands Call Intercept Provisioning Center OMC-R OMC-R is responsible for configuring and monitoring the SDM/FT using MMI commands to control the specific functions. remote statistics uploads.0 05-Oct-07 6871000P02-A Functional Description 7-39 . such as remote configuration downloads. These disk drive units are used for data storage. and recovery in the event of disruption of the SDM/FT. MMI Commands The Man-Machine Interface (MMI) provides a graphical user interface using the Airgen application software.Interconnect Subsystem Details SuperNode Data Manager/Fault Tolerant (SDM/FT) SDM/FT Software Description SDM/FT software applications are backed up via mirrored disk drive units. 0 05-Oct-07 . Functional Description 7-40 6871000P02-A SR 16..Interconnect Subsystem Details SuperNode Data Manager/Fault Tolerant (SDM/FT) NOTES.. .... ... ........ ................. ... ... 8-13 MSD ..... ........ ........ ............ ...... . .. ....... .... ..... .... 8-6 Next Generation for Dispatch .................. 8-10 References ...... . .. ......... 8-10 Introduction ............... .... ......................... ......... 8-8 DAP Functional Description ... .... ................... .. . ... .... ......... ..... .. ..... .. 8-11 Urban ID .. .. .... ........... ... ... .. ......... ........ . 8-13 ROC ...... . ......... ....... .... .. . ............ .... ........... ...... .......... ............. ... ..... .. .. ..... ..... ... .......... .... ..... .... 8-10 DAP Overview ...Chapter 8 Dispatch Subsystem Details In This Chapter Topic See Page Purpose.... . .. ........... .... ... ... ..... .... 8-7 Final NGD Implementation .............. 8-12 CPU.... ..... .. .. ..... ...... 8-11 Fleet ID....... 8-13 IOC . ... .......... .... . ......... .. ..... ..... .......... .. .. . ........ ........... ....... ................. . .. .. . ......... .. ....... 8-16 SR 16.... 8-11 Multiple Simultaneous Talk Group ID........ ... . ....... .. ... .. ................ .. ............ ...... ..... . . ............... ............ 8-7 Split Mode . .... . .... . .. .. . ... .. ......... 8-16 DAP Feature . . ..... ...... ....... .... ........ .......... ........ . . 8-11 Talk Group ID . .... ..... ............. ......... ............ .............. . . ............... .................................. .....0 05-Oct-07 6871000P02-A Functional Description 8-1 ... ..... ....... .. ......... ...... . .... 8-12 Site Specific Parameters ...... ......... . . ........... ........ .. 8-13 Software Description ..... . 8-12 Hardware Description......... ........ ...... .. 8-11 Fleet Member ID .. ....... .... .......... ............. 8-7 Mixed Mode. ... .............. ................... .. .. ........ ...... .................... .. ....... .. ....... 8-10 Dispatch Subscriber Parameters .... 8-13 SSC .... ................. ... . ............ ... . ....... . ......... ... . ..... ...... ... .. .......... .. .. ..... ........ .... ... .............. .... . .. .. . .. . . ... ............. ... ..... . . .. ............ ..... ....... . ..... . ..... . .. . .................... ............................. ... . ... ..... . ...... ......... ..... .......... .. . .... ........ .. . ..... ... ..... ... ..... ...... .... ................... 8-18 Database Management ... ... ......... .. ............ . .. . .... ...... .......... .... 8-19 SMT Menu... .... . ..... .................. ...... ... ......... ........... . .......... .. ............ .............. .... ......... .... ... ......... ....... ........ ...... ........ .......... ..................... .. ..... ......... .. . ...... ............. ................ .. ........ ............. ...................... . . ..... ...................... ....... .. ..... 8-18 System Control Management.... ..... . ............ ............... 8-22 Introduction ................ ............... ... ..... ..... ........ .... . . ....... .. .... .. .. . . .... ..... ............................... ..... ...... ...... . ...... ......... ............ ... . .. ..... ......... .. ....... . ......... ....... ........... . ........ ..... ... ........ ............................ 8-26 HA-DAP Feature ............ ..... .. ... ........ .. 8-29 Database Maintenance .. . .... 8-18 Resource Management .............. ..........0 05-Oct-07 ........ ... .............. ....... .. .... ....... .. 8-28 Alarm on LMT Login/Logout .... ...................... . ..... .. .. .......... .. .. . . ......... . .... ................ .... ................. .... ..... . .. ... . . ... .... ..... .. . ............. ............... .. 8-19 Availability Management ....... ......... . .. . ... 8-24 RX7620 Server... ......... . .......................... ........................ 8-19 Network Management...... 8-17 Core Architectural Models ... . ... ...... . . . ......... 8-32 Network Management....... . ... ........... ...... 8-17 DAP Migration for NGO.... ................................... ...... ........ .................. .. ................... .. 8-19 Call Processing Management .. 8-20 CA ... ........... . .. .. .... ... ......... ...... . ......... 8-17 BCCB 1020 ..................... 8-20 MAP ............ 8-22 HA-DAP Overview ..... 8-19 iDEN Menu .............. ..... ... ... ... .................... 8-31 Database Query .. ........ .. 8-16 DAP Enhancements ......... .. ...... .. .... ................... ..... . ........ . . ........... ............. . .. ..... ... ...... 8-20 CCP Layer........ ..................... ... 8-26 HA-DAP NGD Enhancements ..... 8-18 Account and Performance Management....... . ................... .. 8-29 BCCB 1020 .... 8-25 Software Description ..... .......... . ......... 8-28 Remote Access Security ....... .. 8-31 HA Services Layer ... 8-31 Database Replication ... ... . .. 8-28 Root Access Control .. ................. 8-16 BCCB 862 .... .......... .... .. .. ......... ................ ...... ............. ........ .. .. 8-22 References . ............... .. ... 8-32 Functional Description 8-2 6871000P02-A SR 16. .. ........................................ ....... ....... ................ .. 8-21 HA-DAP Functional Description ................. .. .......... .. ............................... 8-18 Configuration and State Management ......... .. ................ ................. ..... ...... . .. .. ........ ... .................. ............. ........ .Dispatch Subsystem Details iGW-SDGC Enhancement......... .. .... ................. 8-20 Event Logs .............. ..... ... 8-29 LMT Master iVPU ......... .......... .. .... ... . 8-23 Hardware Description..... ....... ......................... ............... ........ ... .... ... ........... ... ....................... ........ ....... .................................. ........... ........................ .. .......... .. .............. 8-16 BCCB 1008 .... 8-26 iGW-SDGC Enhancement.... ... .. ...... . ...... ........ .......... ..... ....... . ......... .......... ................ . . .................................. .. .... 8-45 Hardware Description....... .. .... .......... .......... .............. ... . ....... ...... . ..... .. ... ... .... 8-40 LMT Master iVPU ........ ..................... ............. .... ....... .......... . ..... .. .... ....... ... ... ...... ............. . .............. .. ............. . .. ...... ... .. ................ 8-42 MMI Command Interface... ... .... ........... ............ .... ........................ .... . ... . .... 8-35 Hardware Description....... 8-48 Load Shedding Status ........... . ... ...... 8-39 iVPU Footprint Reduction...... . ... ........... .. .. .......... .... .. ....... ............... .... ... .. ..Dispatch Subsystem Details LMT . .............. . ...... ........ .... . ... .0 05-Oct-07 6871000P02-A Functional Description 8-3 ......... .. ... .... ....... 8-48 SR 16..... ........ .. ......... ........... ... 8-32 ELMT. ...... .... .. . .. ......... .. . 8-40 Root Access Control ... ..... .................. .... ... ...... ............ ............. ... ............... ........ ...... 8-41 Rolling Software Upgrade .. ..... . .... ....... 8-40 Enhanced LMT Capabilities .. ....... 8-43 HSRP Protocol . .. ...... 8-48 Ethernet Physical Port Status ........... ............... . ............ .. ........... ........................... ..... . ....... ..... ..... ........ ........... ............... ............................ ....... . ... .. . ..... ... 8-44 References .............. ........ ... . .................. ................... .. .... ...... ........................ .. ... ............ .................................... . ............ 8-37 iVPU Feature ....... . .......... ................. . .. .... ................. ...... .......... ................... .. ... .... ..... ........... ........... . .. .......... .. ... ... .. . ............. ............ 8-34 iVPUdi . 8-39 iVPU Enhancements .... . ... .. .......... .... ... ............... 8-46 Disk Arrays ............ . ............... 8-40 Enhanced Frame Relay Channel Statistics... .... .. 8-42 VRRP Protocol ................... .... .................. . .................. ...... ......... . . .. ....... 8-33 Activity Log Files ... 8-34 iVPUd ... ............. .... ............... .... .............. ...................... .............. ............. ........... ................. ......... . .......... ....... ... . ........ .......... ............. 8-42 Network Management.. 8-36 iVPUd ................. .. 8-34 iVPU Overview ............ ..... ...... ...................... .... .. ........... .. ...... 8-46 Alarm Panel......... . . ........................... . ... .. .......... . . 8-44 Introduction ...... ... ... . ... ............ ....... 8-46 Software Description ..... . ................. ..... .. 8-39 Alarm on LMT Login/Logout ................. . ... ............ ..... .. ......... ................ . 8-46 TS40 AlphaServer ......... ........... 8-44 HA-iHLR Overview ......... .... ...... ............... ............ . .......... ... .......... ..... .. ... 8-39 iVPU SPROC/ISB LED Indicators ........... ... ....... 8-41 VRRP Support on iVPU ....... 8-33 iVPU Functional Description...... ........ ............. ..... .... ..... ..... .. .... .. ......... ....... 8-41 Remotely Manage iVPU .. ....... ... ... .. 8-36 iVPUdi ... .. .. ........... . .................. . ... ....... ........ .............. .......... ....... ... ..... ......... ............ ... .... ......................................... ................ ..... ................ 8-34 References ........ .......... .. .............. .......... 8-34 Introduction ....... 8-48 HA-iHLR Features ... .. ...... .................... ... . 8-35 iVPUi ...... ... .......... . 8-43 HA-iHLR Functional Description ........ ..... ....................................... .... ........ 8-50 ELMT... 8-59 HSSI I/O Boards.. ... ................ .......... ....................... .. ..... .... .. ....... .... ... 8-59 MTX Board ...... 8-50 HA-iHLR Database ASCII Dump ................. ... . ......... ......... ... ........ 8-49 Debugging Data Collection Tool. 8-50 Network Management............... ....... .. ............ .. ............. .. 8-57 GTT-IIC Data File ..... .............. .. .............. ............... .................... .................. ........... .. ......... .. 8-57 Network Management............................. .. ........ . .. ...... ........... .... ............. .... ....... .. ............ .... . ..... ..................... ........... ..... .... .... ...... .. ........... ....... . 8-49 Remote Access Security .... .................. ........ ............. .. ..... ................. ................... ... . ... ....... ............ .... .......... . ............... .... .... . ....... .......... .. ........ ...... ............... .. .............. .. ....... ............. ... .... 8-54 HSSI Interface Module ........... . ................... ..... ...... ........ 8-53 iDAC Overview ....... ........ ................. 8-57 LMT ......... ............................ 8-49 Root Access Control ........................ . ...... .......................... .................. .... ....... .... 8-49 Data Collection Time Interval .... ........................ .. . ....... ........ ..... .. .... ..... .... ... . ................................... .................. ... .......... ............... . ......... ....... .... ..... ...... ........... .......... ........................... . .. ........... 8-53 References .. ...OMC-R Software Interface ......... ...... .. 8-52 iDAC Functional Description .... ........ ...... 8-58 APD Overview ........ ........................ .. ..... . .... ............... ......... 8-51 Backup and Restore CLI .... ..Dispatch Subsystem Details Health Check. ... 8-51 SRM ... ... ..... 8-53 Introduction . . .... .......... ......... .. ............... .... .. 8-58 Hardware Description............. .............. 8-48 Restricted Access Key ........ .................0 05-Oct-07 ................... . . . 8-59 LED Board... ..... .... 8-53 Hardware Description.. ... . .... .. 8-49 Alarm on LMT Login/Logout .. ....................... . .............. .. ..................... ................ 8-49 LMT Master iVPU ........ ........................ ... 8-60 Functional Description 8-4 6871000P02-A SR 16..... ..... ......... .... .. ....... 8-48 Ping and TraceRoute . ..... .... ............ . .. ..... .. .. ............. ........ 8-51 RMC ...... ........ .... ..... .. .............. ........ ... ........... 8-54 Software Description ............. ....... 8-59 APD Power Supply. ....................... ..... ............. ................... ....................... . . ..................... . ....... .. ............. ................ ..... ..................... ........ .. ....... 8-49 HA-iHLR NGD Enhancements ... ... .... .. .. ...... .......... 8-57 iDAC ....... ........... 8-50 LMT .. 8-57 iDAC .... . ......................... . 8-58 References . .... . ............................... ................. .. ................... .... .... ... ..... ...... .................. .. .... .......................... ... 8-57 APD Functional Description ........ 8-54 Alarm Panel............ . .......... ................... ..... ................. 8-54 CPU Board ................ ......... .... .. ...... ............ ............................. ........... .. ............... . ... ...... .......... .... .... .......... 8-51 Provisioning Transaction Log File ...... ..... 8-58 Introduction .... ..... ........ .................. ......OMC-R Network Interface .. . ....... ............ .................... .. ........ .. 8-73 MPS Redundancy .... .......... .... 8-66 SPA ... . .... . ............ .... ...... ..... . ........... .. .............. ... . .. . ..... .. .......... ............... ... ........... .. 8-68 MPS Overview ......0 05-Oct-07 6871000P02-A Functional Description 8-5 ............ ........................................ ....... ...... ............... ......... ................. . ........ . . .................................. ........ ..... . ... 8-72 Network Management. .. ........... .......... .. .. ............... .................. ......... ........... ............. .. 8-62 iSG Overview. .......... ............... ..... .... .. .... .. .... ... . ........... ... ........ ........... ................ .. ............................... . . . .. 8-64 Cooling Fans .............. ....... 8-73 CLI..................... 8-73 Cisco WAN Manager...... ...... ........................... ......... ................... ... ......... ............ ....... ........ ........ 8-62 References ..... ....... 8-70 SES PNNI ....... ... .. 8-64 DC Power Distribution Panel... .... 8-61 MMI ............... 8-69 MGX 8820 .......... 8-68 References ..... .. ..... ...... ..... ... . .. .......... ...... .................... ................ ............ .. ....... . ....... ..... ... ... ..... 8-62 Hardware Description.... 8-64 Alarm Panel.... .... ........... 8-68 Hardware Description.. ... ...... ....... ............. 8-70 MGX 8850 . . ......... .................. .. .. 8-74 SR 16.... 8-61 Network Management.. ...... . ......... .... ....... ....... ........................................ ........... 8-71 SES Node Architecture .......... ..... ..................... ..... ... ........................... .. .. ............. 8-64 Software Description ............. .. .... ......... . ....... . .... ...... ... ...... .......................... ... ........... .......... .... . 8-72 MGX 8850 Architecture ....... . . .............. 8-66 iSG Software ... .. .................... ......................... .. .. ...... .. ..... ..... .... .... .... ..... . ......... ..... ... .. ............. ......... .................... ..Dispatch Subsystem Details Software Description .. ... ......... ....... .. .. . ......... 8-62 Introduction ....... .. ... ..... .... . ............... .... ...... ... .. .. ........ ........ .. ........ ........... ........... .. .... 8-66 LMT .... 8-66 Network Management............... ........ ............. ...... . ............. .. .. .... .. .............. .. ..... ........ .... ............ .. . ........ .... . ... .... .. ...... .... ............ .... .......... ... ... .... ... .... .... ........... 8-72 MGX 8820 Architecture ..... ... ............................ ... ..... ...... .................. ........... ....... ........ . 8-61 OMC-R Interface ..... ............ ...... ...... . 8-61 iSG Functional Description.... ................. .. ... ........... ......... ........ ....... .... .......... .... ............... ....... 8-67 MPS Functional Description .......... .. 8-63 HSC Board .... . ............. . 8-70 Software Description .......... ..... ....... .... ........ ..... .... ....... ...... ....................... ....... ... .... ........ ....... . ........... .. .... .......... . ................ .. ... ... .. .. . .......... ...... ...... ... 8-68 Introduction ......... ...... .... .................... .. ... .. . ............ ........ ..... .... 8-63 CPU............ 8-69 BPX ... ....... .. ........ ...... .. .... ..... .................... ........ ... 8-66 SPA ....... 8-64 HSSI Adapter Board... ..... .......... ...... 0 05-Oct-07 .Dispatch Subsystem Details Purpose Purpose This chapter describes the Network Elements (NEs) that comprise the Dispatch subsystem in the Integrated Digital Enhanced Network (iDEN) network. The following Dispatch NEs are supported in the Next Generation Dispatch (NGD) architecture: „ „ „ „ „ „ 8 High-Availability Dispatch Application Processor (HA-DAP) High-Availability iDEN Home Location Register (HA-iHLR) iDEN Surveillance Gateway (iSG) iDEN Vocoder Processing Unit (iVPU) iDEN Vocoder Processing Unit for Dispatch (iVPUd) iDEN Vocoder Processing Unit for Dispatch (iVPUdi) The following legacy Dispatch NEs are contained in this chapter for reference until the NGD architecture has been fully deployed in each service provider’s network. Each NE is documented in a functional description. „ „ „ „ Dispatch Application Processor (DAP) iDEN Dispatch Access Controller (iDAC) Advanced Packet Duplicator (APD) Metro Packet Switch (MPS) Functional Description 8-6 6871000P02-A SR 16. and network management facilities. software function. Each functional description includes information on the key hardware components. Mixed Mode Stage One. feature functionality and enhancements improved capacity. and the iDEN Vocoder Processing Unit for Interconnect (iVPUi) are now available in the NGD architecture. In NGD. In Mixed Mode Stage Two (see Figure 8-2 on page 8-8). the HA-DAP. all EBTS must be associated with an IVPUd or IVPUdi. Mixed Mode Stage One (see Figure 8-1) combines the legacy NEs with the iVPUd. Figure 8-1 Mixed Mode Stage One SR 16. Mixed Mode Mixed Mode architecture is comprised of two different stages. the iVPUd or iVPUdi is routed through the MPS. iVPUd. While Interconnect voice traffic terminates to either a legacy XCDR transcoder. and management in the iDEN network.Dispatch Subsystem Details Next Generation for Dispatch Next Generation for Dispatch The NGD architecture introduced a phased migration that included Mixed Mode and Split Mode architecture. Before the HA-DAP is integrated into the network. the iVPUdi.0 05-Oct-07 6871000P02-A Functional Description 8-7 . Mobile Data Gateway (MDG). In Split Mode. then an iVPUd is installed. Dispatch FR traffic terminates on a legacy DAP. Interconnect traffic is sent to the BSC and the Dispatch traffic passes through the iVPUd. or iVPUdi. 8 Split Mode Split Mode consists of a site configuration with Dispatch traffic carried by a Frame Relay (FR) channels. performance. Since the HA-DAP has not yet been added to the network. and Mixed Mode Stage Two. and Interconnect voice traffic carried by circuit switch channels. or iDEN Vocoder Processing Unit for Dispatch and Interconnect (iVPUdi). If the service provider configuration still includes a legacy Base Site Controller (BSC). iDEN Vocoder Processing Unit for Dispatch (iVPUd). The MPS. Figure 8-3 Next Generation Dispatch Network Functional Description 8-8 6871000P02-A SR 16.Dispatch Subsystem Details Next Generation for Dispatch Figure 8-2 Mixed Mode Stage Two Final NGD Implementation 8 In the final NGD implementation (see Figure 8-3). and all EBTSs communicate through the iVPUd or the iVPUdi. See Table 81 Mixed Mode and Final NGD Architecture NEs on page 8-9 for a comparison of what Dispatch NEs are supported in each phase of the NGD implementation. all legacy DAPs are replaced by HA-DAPs.0 05-Oct-07 . APD. and iDAC are decommissioned from the iDEN network according to the service providers deployment schedule. Table 8-1 Mixed Mode and Final NGD Architecture NEs NEs Mixed Mode Stage One Mixed Mode Stage Two MPS Legacy DAP HA-DAP APD iDAC iSG HA-iHLR iVPUd iVPUdi iVPUi Fully supported Fully supported Fully supported Fully supported Fully supported Fully supported Fully supported Fully supported Not supported Not supported Fully supported Fully supported Fully supported Fully supported Fully supported Fully supported Fully supported Fully supported Fully supported Fully supported Final NGD Not supported Not supported Fully supported Not supported Not supported Fully supported Fully supported Fully supported Fully supported Fully supported SR 16.0 05-Oct-07 6871000P02-A Functional Description 8-9 .Dispatch Subsystem Details Next Generation for Dispatch Table 8-1 shows a comparison of what Dispatch NEs are supported in each phase of the NGD implementation . The R12K 4-way DAP supports up to 330. software.Dispatch Subsystem (WP2002-022) These documents are available on the Motorola Extranet web site at http://mynetworksupport. Provides first-time registration for Dispatch and Interconnect subscribers. private calls.000 Dispatch subscribers. call alerts. The R12K 2-way DAP supports up to 2. „ „ „ „ EBTS Backhaul: Frame Relay DSO Requirements (WP2002-025) DAP User Guide (6881001Y49) SR13. The DAP provides the following capacity in the iDEN network: „ The R10K DAP supports up to a maximum of 2. and additional information for the Legacy DAP. DAP Overview The DAP coordinates and controls Dispatch and Packet Data (PD) communication services. Provides the Visitor Location Register (VLR) for subscriber information.000 Dispatch subscribers. The DAP is optimized to support rapid response time for services such as group calls.motorola. Sets up Dispatch group calls.com unless otherwise stated.4 DAP Hardware Installation Manual (68P81001Y50) Understanding iDEN System Fault Tolerance . emergency calls and Packet Data networking. 8 References The following publications may be required to supplement the information contained in this chapter.000 simultaneous Dispatch voice calls and 150. The DAP provides the following functionality in the iDEN network: „ „ „ „ „ „ „ 8 Overall coordination and control of Dispatch and Packet Data functions. network management access.000 simultaneous Dispatch voice calls and 180. Tracks Subscriber Unit (SU) deactivation.Dispatch Subsystem Details DAP Functional Description DAP Functional Description Introduction This subsection describes the hardware. Tracks and maintains Dispatch and Packet Data mobility. Collects alarms and performance statistics. „ „ Functional Description 8-10 6871000P02-A SR 16.0 05-Oct-07 .000 Dispatch subscribers. Members of the fleet are assigned to different groups based on task. and the number of groups in a fleet vary with the requirements of each fleet. and those groups are defined and managed by the HA-iHLR and D-VLR. so a fleet member identifier number can be removed from a fleet without having to renumber the fleet. function. These parameters determine mobile subscriber access and services. and permit inter-region and horizontal Dispatch (cross fleet) calling.Dispatch Subsystem Details DAP Functional Description Dispatch Subscriber Parameters The are several parameters used for Dispatch call processing. or another method. The Fleet ID parameter is the largest functional unit of a Dispatch call. The Fleet Member ID is also used to show which SU is transmitting in the PTT-ID service. There can be approximately 11 million Urban IDs in the iDEN network. or members.0 05-Oct-07 6871000P02-A Functional Description 8-11 . This parameter allows an SU to roam outside the home region and maintain a unique ID that is used to confirm service. organization. The Dispatch-Home Location Register (D-HLR) and Dispatch-Visitor Location Register (D-VLR) maintain the Urban ID information in its databases. This parameter is used to identify the originator or target SU during a Private Dispatch call. A SU may be part of more than one SR 16. Each group in a fleet has a dispatcher (user 0) that is the control point for all Dispatch communication. Fleet Member ID The Fleet Member ID parameter is a number assigned by the service provider to uniquely identify an SU as a member of a particular fleet. Fleet ID The Fleet ID parameter is an identification number assigned to major corporate or municipal subscribers by the service provider. Talk Group ID The Talk Group ID parameter is a number given by the service provider to divide fleets into groups or logical units. users. A fleet is comprised of different groups. The parameters include: „ „ „ „ „ „ 8 Urban Identifier (Urban ID) Fleet Identifier (Fleet ID) Talk Group Identifier (Talk Group ID) Multiple Simultaneous Talk Group ID (MST ID) Fleet Member Identifier (Fleet Member ID) Site specific parameters Urban ID The Urban ID parameter defines the home region for a particular SU. The type of fleet. The Fleet Member ID does not need to be contiguous. one GB RAM. This optional feature allows a user to monitor and participate with other groups. And the capability to select different associated talk-groups for all modes can be toggled on or off. as long as the change is allowed in provisioning by the service provider. Site Specific Parameters In the iDEN network. The DAP is comprised of the following components: „ „ Central Processing Units (CPUs) Input/Output Controllers (IOCs) Functional Description 8-12 6871000P02-A SR 16. two GB RAM. and the other 3 potential groups are called associated groups. The R12K 4-way DAP is housed in one cabinet that supports 32 T1 or E1 connections to the MPS (see Figure 8-5 on page 8-15). and two 4 GB hard drives. The R12K 4-way DAP uses two CPUs. and can change the default talk group. The MST feature allows a SU to belong to up to four groups in the same fleet. and two 4 GB hard drives. each EBTS has unique site specific identifiers to coordinate activities associated with the Radio Link. Multiple Simultaneous Talk Group ID The Multiple Simultaneous Talk (MST) Group ID is an optional feature associated with advanced feature software. The original group is called the selected group. There is only one selected group allowed per mode switch setting.1 Giga-Byte (GB) Random Access Memory (RAM). and two 18 GB hard drives. Hardware Description The following platforms are available in the DAP subsystem: „ „ „ 8 R10K DAP R12K 4-way DAP R12K 2-way DAP The R10K DAP is housed in two cabinets that support 24 V. An AFU SU is required to support the MST optional feature. The Dispatch service provider creates specific limitations for each member of the fleet so a user only hears the conversations and announcements related to members of that same group. The R12K 2-way DAP is housed in one cabinet that supports 32 T1 or E1 connections to the MPS.Dispatch Subsystem Details DAP Functional Description talk group.0 05-Oct-07 . The R12K 2-way DAP uses two 300 MHx CPUs. The site specific parameters are read and utilized by each SU as link control procedures are run. The R10K DAP utilizes two Central Processing Units (CPUs).35 I/O ports to the MPS (see Figure 8-4 on page 8-14). Site specific parameters are transmitted on the Broadcast Control Channel (BCCH) by each cell to the mobile subscribers on that cell. The user operates a mode switch to change to the associated group from the current selected group. and operations and maintenance communications. In most cases. All of these devices are Small Computer System Interface (SCSI). The databases contain the identification. MSD The MSD stores and maintains the operating software and databases. SSC There are two SSCs in the DAP cabinet for fault tolerant redundancy.35 may be used to handle FR communication (Dispatch call and Packet Data processing) with the MPS. The CPUs provide the logic circuits to execute Dispatch processing code and access the databases for service and location information. There are two cards for redundancy and fault tolerance. ROC The ROCs manage the routing of control signaling and operations and maintenance information between the DAP processor and the rest of the system. IOC The IOC cards provide for the connection of external equipment. Some installations may use another card to provide a single port to an ethernet LAN transceiver for operations and maintenance.Dispatch Subsystem Details DAP Functional Description „ „ „ Mass Storage Devices (MSD) Router Controller Card (ROC) Standard System Controller (SSC) CPU The two CPUs provide the processing engine and memory for the DAP. V. The SSC cards provide the ServerNet communications routing for the following: „ „ „ „ „ „ Configuration and maintenance Host Bus Adapters (HBAs) I/O controllers I/O expansion functions for the system Internal control and maintenance of the system SCSI disk drives SR 16. Tape backup and CD-ROM devices are also available. location and authentication information for Dispatch enabled mobile subscribers.0 05-Oct-07 6871000P02-A Functional Description 8-13 . 316 IOC3.314 IOC3.318 SSC3319 CPU Modules Blower Modules Power Modules Figure 8-4 I/O Modules Functional Description Dispatch Subsystem Details DAP Functional Description R10K DAP Cabinet R10K DAP Front 6871000P02-A Storage/ Expansion Module Storage/ Expansion Module R10K DAP Rear SR 16.318 IOC4.414 IOC3.316 IOC1.418 SSC4319 SSC3313 IOC1.315 IOC3.417 IOC3.0 05-Oct-07 .Storage/ Expansion Module 8-14 ROC2201 CPU2202 JUMPER JUMPER CPU2205 ROC2206 ROC2207 CPU2208 CPU2209 CPU2210 CPU2211 ROC2212 SSC4313 IOC3.317 IOC3.315 IOC4.416 IOC3.318 IOC3.317 IOC1.415 IOC3.316 IOC4.315 IOC1.314 IOC1.314 IOC4.317 IOC4. 317 IOC4.317 IOC3.315 IOC3.314 IOC3.318 SSC3319 SSC4313 IOC4.316 IOC3.318 SSC4319 I/O Modules Storage/ Expansion Module Storage/ Expansion Module ROC2206 ROC2207 CPU2202 Blank Storage/ Expansion Module SR 16.315 IOC4.314 IOC4.Dispatch Subsystem Details DAP Functional Description Figure 8-5 R12K DAP Cabinet R12K DAP Front R12K DAP Rear Power Modules Blower Modules SSC3313 IOC3.316 IOC4.0 05-Oct-07 6871000P02-A Blank Blank CPU Modules JUMPER Blank ROC2212 ROC2201 CPU2205 JUMPER Functional Description 8-15 . Functional Description 8-16 6871000P02-A SR 16. For additional information about the feature. the DAP sends an SDGC Page Response Forward message to the VSGW. they were not forwarded to the OMC-R because the statistic ACG/DLA ID 0 was considered invalid. see iGW-SDGC Enhancement on page 8-26. failed mobility attempts were tracked by the ACG/DLA ID zero (0) statistics. renewal. 8 DAP Enhancements The following performance and status enhancements were added for the DAP: „ „ „ „ Business Change Control Channel (BCCB) 862 BCCB 1008 BCCB 1020 DAP Migration for NGO BCCB 862 Previously. and deactivation events. and deactivation events. And three new statistics were added to count failed reconnect. Even when the DAP incremented these statistics. renewal.Dispatch Subsystem Details DAP Functional Description Software Description This section contains the following software related information: „ „ „ 8 DAP feature DAP enhancements Core architectural models 8 DAP Feature The iGW-SDGC Enhancement feature impacts the DAP. When the iDEN SU responds to the page. So four existing statistics were redefined to count successful reconnect. iGW-SDGC Enhancement The iGW now supports SDGC between a 3G network and the iDEN network. When an SDGC call is initiated. The VSGW sends an OK response to the 3G network endpoint signaling that the Dispatch call is connected. Failed registrations are already tracked/counted in the existing DAP_REG_REQ_IMEI_FAIL and DAP_REG_REQ_IMSI_FAIL statistics. the 3G network forwards a SIP invite request.0 05-Oct-07 . The VSGW forwards the new Proxy Page Request Forward message to the DAP and reserves transcoder resources. BCCB 1020 The BCCB 1020 enhancement addresses a PCCH spiking problem caused by a high rate of Registration Renewals (RR).0 05-Oct-07 6871000P02-A Functional Description 8-17 . or on a periodic basis once every 10 hours. To maintain DAP link state information for sites on an OMC-R basis.Dispatch Subsystem Details DAP Functional Description See Table 8-2 for information on the new and revised statistics. DAP Migration for NGO With the introduction of NGO. Urbans with up to seven OMC-Rs are upgraded into Urbans with up to two Netra 440. The HA-DAP supports 2000 sites. For more information see BCCB 1020 on page 8-29 for more information. a migration procedure is performed. Table 8-2 Statistics Changes for BCCB 862 Existing Statistic New Statistic Stat ID Level New Description TOT_RRNC_REQ TOT_RRN_REQ TOT_R_REQ TOT_DEA_REQ N/A N/A N/A TOT_SUCC_RRNC_REQ TOT_SUCC_RRN_REQ TOT_SUCC_R_REQ TOT_SUCC_DEA_REQ 1088 1089 108A 108B ACG DLA DLA DLA DLA DAP DAP Successful reconnects (registration renewals with call) Successful registration renewals with no call Successful registration renewals handled by the serving DAP Successful deactivations Failed reconnects (registration renewals with call) Failed registration renewals with no call Failed deactivations TOT_FAILED_RRNC_REQ 1ABC TOT_FAILED_RRN_REQ TOT_FAILED_DEA_REQ 1ABD 1ABE BCCB 1008 The BCCB 1008 enhancement increased the number of supported sites from 800 sites per Mobile Switching Office (MSO) to 2000. A RR is sent by the mobile to update the D-VLR when the mobile crosses a DLA boundary. SR 16. 0 05-Oct-07 . The iSG Resource Management Task (IRMT). and the Surveillance Provisioning Management Task (SPMT). and handles surveillance requests from iSGs. System Control Management The System Control Management architecture consists of three interfaces. the System Administration Management Task (SAMT). The VLRT manages the D-VLR database. Database Management The Database Management architecture consists of the Lifetime Registration Audit Task (LRAT). The MRMT manages MDG status information. the Packet Duplicator Management Task (P2MT). The IRMT manages iSG status information. And the DRMT manages the status information of other DAPs. and the DAP Resource Management Task (DRMT). The CDTT is the interface to turn on/off traces and retrieve various database tables. the Visitor Location Register Task (VLRT). or system and database maintenance. Resource Management The Resource Management architecture consists of the MDG Resource Management Task (MRMT). The SAMT is the interface to request system startup/shut down. The LRAT performs database audits. The P2MT manages APD and iDAC status information. the System Maintenance Terminal Task (SMTT). and the Control Database Trace Task (CDTT). and sends subscriber information to the MDGs. Functional Description 8-18 6871000P02-A SR 16. The SMTT is the interface to retrieve or updated system configuration and state information. the MDG Backup Download Task (MBDT). The SPMT manages subscriber surveillance information. The APMT also creates billing records and sends statistics to the Common Agent (CA). The MBDT stores and updates Mobile Data Gateway (MDG) related subscriber information.Dispatch Subsystem Details DAP Functional Description Core Architectural Models The DAP uses the following core architecture models in the iDEN network: „ „ „ „ „ „ „ 8 Account and performance management Database management System control management Resource management Configuration and state management Availability management Call processing management Account and Performance Management The Account Performance Management Task (APMT) retrieves data from shared memory and from other tasks. Network Management DAP operation and maintenance activities. and applies provisioning changes sent from the HA-iHLR. The DLMT handles link state management for the DAP.Dispatch Subsystem Details DAP Functional Description Configuration and State Management The Configuration and State Management architecture consists of four interfaces: the Configuration Management Task (CFMT). The CPMT sets up Dispatch calls. The menu interface provides the following functionality: „ „ „ „ System and configuration file maintenance Statistics and queries for D-VLR Alarm and billing file maintenance Hardware status and diagnostics SR 16. the DAP Link Management Task (DLMT). and the Node State Management Task (NSMT). node. The GDMT receives and manages the Global Title Translation (GTT) data. The RRRT sends registration renewal required messages to all or a subset of the Access Controller Gateway (ACGs). and processes Dispatch and Packet Data calls. the GTT Data Manager Task (GDMT). The NSMT handles application. Call Processing Management The Call Processing Management architecture consists of the Call Processing Management Task (CPMT). and load shedding state management for the DAP. and network interfaces are provided by the following: „ „ „ „ „ 8 iDEN and SMT Menus Event logs CA Common Controller Platform (CCP) Layer Mobile Application Part (MAP) iDEN Menu The iDEN Menu provides the interface to operate and maintain the DAP. The DURT determines the availability of the DAP and sends the availability information to the ACGs.0 05-Oct-07 6871000P02-A Functional Description 8-19 . Availability Management The Availability Management architecture consists of the DAP Utilization Resource Task (DURT). The MBMT tracks the location of the mobile subscriber. handles Dispatch and Packet Data registrations. the Mobility Management Task (MBMT). The CFMT manages the system configurations for other tasks. SU authentication. and the Registration Renewal Required Task (RRRT). and PD parameters. To use the system event log for diagnosing problems. including changes of state and failures of hardware CRUs. review log entries that were recorded over an interval of time. A single event entry in the event log can be misleading. It is also possible to review the history of a resource or CRU using the information from system messages and hardware message logs. These parameters can be configured. statistics collection Configuration management Alarm/event reporting OMC-R simulator Functional Description 8-20 6871000P02-A SR 16. „ „ „ Update billing View state management information Update MDG Packet Data information Event Logs The OS maintains a system log file of events. but the updates are only temporary until the configuration file is updated. The CA is the interface between the OMC-R and the various NEs (except for legacy BSC and EBTS). CA The CA provides a set of common network management facilities for the NEs. The CA implements the following network management facilities: „ „ „ „ „ „ Bootstrap Protocol (BOOTP) client Simple Network Time Protocol (SNTP) client File transfer protocol. the parameters default to the original values. however. and is OS independent.0 05-Oct-07 . Each NE can selectively use the CA services based on their needs. trace parameters. I/O parameters.Dispatch Subsystem Details DAP Functional Description „ „ Start and stop the DAP IP address maintenance SMT Menu The SMT Menu provides the user interface for the following functionality: „ „ View and update alarm table parameters Configure service parameters. a series of similar or related events recorded over time often identify the source of the problem. If the application is stop-started. performance parameters. such as several hours or even longer. Dispatch Subsystem Details DAP Functional Description CCP Layer The CCP Layer is the interface between the box hardware or OS. SR 16. The CCP implements a common functionality for multiple applications. MAP The MAP communicates between VLRs and HLRs. and the application.0 05-Oct-07 6871000P02-A Functional Description 8-21 . and allows the application to be platform-independent. authentication services. and provides services such as. location management. and provisioning. The MAP application is implemented in the Mobile Application Part for VLR Task (MAVT) on the DAP. Dispatch Subsystem Details HA-DAP Functional Description HA-DAP Functional Description Introduction This subsection describes the hardware, software, network management access, and additional information for the HA-DAP. 8 References The following publications may be required to supplement the information contained in this chapter. „ HA Dispatch Application Processor (HA-DAP) User Manual (68P81001Y83) HA-DAP Hardware Installation Manual (68P81001Y84) „ These documents are available on the Motorola Extranet web site at http://mynetworksupport.motorola.com unless otherwise stated. Functional Description 8-22 6871000P02-A SR 16.0 05-Oct-07 Dispatch Subsystem Details HA-DAP Functional Description HA-DAP Overview The HA-DAP is the next generation DAP for the iDEN network, and is responsible for the overall coordination and control of Dispatch and Packet Data services. The HA-DAP has two nodes that work in an active/standby configuration to provide highly available Dispatch services. With the HADAP, operation costs associated with Dispatch services are reduced, and the availability of Dispatch services has increased. The HA-DAP is optimized to support rapid response time for all Dispatch call types and Packet Data networking. The HA-DAP provides the following functionality in the iDEN network: „ „ „ 8 Assigns signaling and routing paths for Dispatch and Packet Data. Collects and maintains Alarms and performance statistics. Supports first-time registration for all Dispatch and Interconnect subscribers. Tracks Dispatch subscriber mobility through the last known Dispatch Location Area (DSA). Controls the activity of a subscriber unit (SU) through the D-VLR. Provides a LMT interface for subscriber provisioning and services. „ „ „ A single HA-DAP supports a maximum of 20,000 simultaneous Dispatch calls with up to 5,000 of those calls designated as Inter-Urban Dispatch calls. The HA-DAP supports the following Dispatch functionality: „ „ „ „ „ „ 8,000,000 Subscribers in an Urban 1,031,851 multi-service subscribers (Home and Roaming) 275,000 fleets 1,031,851 talk groups 1,031,851 modes 150,000 Selective Dynamic Group (SDG) records SR 16.0 05-Oct-07 6871000P02-A Functional Description 8-23 Dispatch Subsystem Details HA-DAP Functional Description Hardware Description The HA-DAP is comprised of the following components (see Figure 8-6): Figure 8-6 HA-DAP Cabinet- Front and Rear View 8 Circuit Breaker Panel Future Alarm Panel RX7620 Server RX7620 Server RX7620 Server RX7620 Server Front Front Rear Rear Functional Description 8-24 6871000P02-A SR 16.0 05-Oct-07 Dispatch Subsystem Details HA-DAP Functional Description RX7620 Server The RX7620 server includes up to 16 IA64 processors and a maximum of two cell boards. See Figure 8-7 and Figure 8-8 RX7620 Server-Back Panel on page 8-26 for more information. The cell board contains up to four Central Processor Units (CPUs), PCI-X Input/Output (I/O) backplane, the Cache Coherency Controller, internal disk drives, the memory controllers, and the memory Dual In-line Memory Modules (DIMMs). The PCI-X backplane is the primary I/O interface for the RX7620, is a single board that acts like two independent partitions, and provides 16 64-bit hot-plug slots. The PCI card section includes redundant Small Computer System Interface (SCSI) controller cards, and redundant dual port ethernet cards. The Platform Dependant Hardware (PDH) Riser board is a daughter card for the cell board. The PDH obtains cell board configuration information from cell board signals and from the cell's LPM. It contains the memory interface microcircuit, processor-dependent hardware, flash memory, and a manageability micro controller, called the Platform Dependant Hardware Controller (PDHC). Figure 8-7 RX7620 Server-Front Panel SCSI Disk Drives Front Panel Display DVD+RW Drive PCI Power Module Smart Fan DC Power Supply SR 16.0 05-Oct-07 6871000P02-A Functional Description 8-25 Dispatch Subsystem Details HA-DAP Functional Description Figure 8-8 RX7620 Server-Back Panel PCI Backplane Smart Fans DC Power Input Software Description This section contains the following software related information: „ „ „ „ 8 HA-DAP feature HA-DAP NGD enhancements Database maintenance HA services layer 8 HA-DAP Feature The iGW-SDGC Enhancement feature impacts the HA-DAP. iGW-SDGC Enhancement Previously, the iDEN Gateway (iGW) supported private Dispatch calls between two mobile stations. Now, the iGW supports SDGC between a 3G network and the iDEN network. When an SDGC call is initiated, the 3G network forwards a Session Internet Protocol (SIP) invite request. The Voice and Signaling Gateway (VSGW) then sends a Session Progress response to the Invite, and forwards the new Proxy Page Request Forward message to the Functional Description 8-26 6871000P02-A SR 16.0 05-Oct-07 Dispatch Subsystem Details HA-DAP Functional Description HA-DAP. Next, the VSGW reserves transcoder resources to convert 3G voice encoding to Vector Sum Excited Linear Prediction (VSELP) or Advanced Multi-Band Excitation Enhanced plus Two (AMBE++), and to convert Real Time Transport Protocol (RTP) to the iDEN version of RTP (iRTP). When the iDEN SU responds to the page, the HA-DAP sends an SDGC Page Response Forward message to the VSGW. The VSGW sends an OK response to the 3G network endpoint signaling that the Dispatch call is connected. The following new DAP statistics were added to track iGW SDGC feature functionality: „ SDGC_PMC_INIT_ORIG - Number of calls that originated initially in the SIP domain. „ SDGC_PMC_CALLBK_ORIG - Number of callback requests received by the PMC-DAP from its own Urban. SDGC_PMC_SC_CALLBK_ORIG - Number of callback requests received by the PMC-DAP from other urbans within the iDEN domain. SDGC_PMC_VSGW_CALLBK_ORIG - Number of callback requests received by the PMC-DAP that were originated by the SIP domain. SDGC_PMC_SUCC - Number of successful SDGCs that terminated due to hang „ „ „ timer expiration as measured by PMC-DAP. „ SDGC_PMC_INTRA_URBAN_SUCC - Number of successful S2D calls that contained participants from only the PMC Urban. SDGC_PMC_FAIL_F1 „ - Number of SDGCs that failed because not even a single target in the iDEN domain responded to pages. „ SDGC_PMC_FAIL_F2 - Number of SDGCs that failed for reasons not pegged by any other statistic. SDGC_PMC_FAIL_F3 „ - Number S2D SDGCs that failed because the originator opted out of the call. - Number S2D SDGCs that failed because the originator validation check failed. - Number S2D SDGCs that failed because no targets are available in the iDEN domain. CSC timeout. „ SDGC_PMC_FAIL_F4 „ SDGC_PMC_FAIL_F5 „ SDGC_PMC_FAIL_CSC - Number of SDGCs that failed because of DAP-DAP SDGC_PMC_PAR_SZ „ „ - Number of active participants per SDGC. - Number of serving DAPs per SDGC within the SDGC_PMC_SRVNG_DAP PMC-DAPs Urban. The following existing DAP statistics were changed to track iGW SDGC feature functionality: „ „ „ „ „ SDGC_NO_PEER_IVGW SDGC_HN_PAR_SZ SDGC_SC_PER_SDGC TOT_DAP_SDGC_CSC_RECV NUM_DAP_PRB_SENT SR 16.0 05-Oct-07 6871000P02-A Functional Description 8-27 HA-iHLR. date and timestamp. or iVPU. the userid. For enhancement R111. the NE sends an ActionStatus trap to the OMC-R to record in the log.Dispatch Subsystem Details HA-DAP Functional Description „ „ „ „ „ „ „ „ „ „ „ „ „ „ „ „ „ NUM_DAP_PRB_RECV TOT_SDGC_TIMEOUTS SDGC_UPDATES SDGC_UPD_REQ_FWD_SENT SDGC_UPD_REQ_FWD_RCVD SDGC_CONT_FWD_SENT SDGC_CONT_FWD_RECV SDGC_PAR_STATUS_UPD_FWD_SENT SDGC_PAR_STATUS_UPD_FWD_RECV SDGC_INDV_STATUS_INFO_FWD_SENT SDGC_INDV_STATUS_INFO_FWD_RECV SDGC_URBAN_STATUS_INFO_FWD_SENT SDGC_URBAN_STATUS_INFO_FWD_RECV SDGC_STOP_FWD_RECV SDGC_PAGE_FWD_SENT SDGC_LOAD_SHED NUM_SDGC_REC_RLS HA-DAP NGD Enhancements The following enhancements impact the HA-DAP: „ „ „ „ „ 8 Alarm on LMT Login/Logout Remote Access Security Root Access Control LMT Master iVPU BCCB 1020 Alarm on LMT Login/ Logout The Alarm on LMT Login/Logout enhancement gives the ability to track users as they access NGD NEs. When a user logs in/out of the Local Maintenance Terminal (LMT) on the HA-DAP. Remote Access Security Previously. Telnet and FTP. Functional Description 8-28 6871000P02-A SR 16. Dispatch NEs were accessed from the LMT using insecure applications such as HTTP. the following secure protocols are available for use: HTTPS. The trap includes the log in/out action.0 05-Oct-07 . Secure Shell and Secure FTP. If root access is disabled. but there is no command or GUI option to administer root access across multiple NEs. and passwords. ensure that the root access is enabled if needed. The user accounts are synchronized when the tx_us_file command transmits the user account file to a iVPU. LMT access is denied. When a iVPU is selected as the LMT master for the Urban. Administrative LMT users can create and maintain user accounts on any iVPU. Prior to maintenance activities.Dispatch Subsystem Details HA-DAP Functional Description Root Access Control The Root Access Control enhancement gives the service provider control over NE root (super user) access. if an active mobile subscriber did not cross a DLA boundary for five days. At the Root Access Management screen in the LMT. and a user logs in as super user. If the tx_us_file command is issued at the LMT master iVPU. the master iVPU maintains the user accounts file and the IP addresses for all the iVPUs in the Urban. to System Maintenance -> Performance Management: „ „ „ „ „ View D-VLR Statistics View Subscriber/Fleet Totals View System Boundary Totals View Replication Memory Usage Statistics View Replication Internal Statistics SR 16. The BCCB 1020 enhancement added a Lifetime Audit Registration Renewal Required (LA RRR) process to solve the PCCH spiking issue. the master user account file of the LMT master iVPU is transferred to every iVPU in the IP address list. LMT Master iVPU Every iVPU has a separate user account file with userids. The following menu items were added to the Performance Management Submenu: „ „ View current Lifetime Audit RRR Statistics View Previous Lifetime Audit RRR Statistics The following D-VLR statistics were moved from the Database Maintenance screen. the following three menu items were added: „ „ „ View Super User Access Control Status Enable Super User Access Disable Super User Access Any LMT user can view information on the Enable Super User Access screen. BCCB 1020 Prior to the BCCB 1020 enhancement. The LA RRR process allows the mobile to send an RR by sending it an individually addressed Registration Renewal Required (RRR) message.0 05-Oct-07 6871000P02-A Functional Description 8-29 . Note Root access is disabled by default. The administrative LMT user may enable or disable root access on a per node basis. but only Administrative users can enable or disable super user access. then the mobile subscriber entry was removed from the D-VLR. SDGC service. The following BCCB 1020 provisioning conditions apply: „ If T3206=10 and LA RRR is disabled or non-existent. Provisioning changes are also applied with a power cycle or DLA change. „ „ „ „ Functional Description 8-30 6871000P02-A SR 16. Table 8-4 Statistics Added for BCCB 1020 Statistic Name Description NUM_AUD_RRR_SENT NUM_AUD_RRR_MS Number of RRR messages sent in the last statistics reporting period as a result of the LA RRR process. LIFETIME_AUDIT_RRR_RATE_SECOND 10 1-25 LIFETIME_AUDIT_RRR_RATE_THIRD 5 1-25 LIFETIME_AUDIT_RRR_RETRY_TIMER 60 0-120 See Table 8-4 for information on the statistics added for BCCB 1020. The minimum time between retry passes for the LA RRR process. home DAP Reassignments are scheduled prior to the 1 AM daily audit. If T3206=0 and LA RRR is enabled and a provisioning change occurs right before the daily audit. then provisioning changes are applied within T3206 (10) hours. A zero value disables the LA RRR process. If T3206=10 and LA RRR is disabled or non-existent then most subscribers are moved to the new DAP within T3206 (10) hours. NUM_AUD_RRR_MS_OVERFLW Number of mobile stations discarded in the last statistics reporting period of the LA RRR process and were not sent RRR messages.Dispatch Subsystem Details HA-DAP Functional Description See Table 8-3 for a list of the parameters added for this enhancement. BCCB 1020 provisioning changes such as. If T3206=0 and LA RRR is enabled.0 05-Oct-07 . Table 8-3 Parameters Added for BCCB 1020 Parameter Name Default Range Description LIFETIME_AUDIT_RRR_RATE_FIRST 20 1-25 The number of subscriber units per second processed by the DAP during the first pass in the LA RRR process. If T3206=0 and LA RRR is enabled and a provisioning change occurs right after the daily audit. encrypted dispatch flag. Otherwise. there is an additional 24 hour delay for subscribers to be moved to the new DAP. The number of SUs per second which the DAP processes during the third pass in the LA RRR process. then the change could take up to 29 hours to be applied. individual dispatch roaming. The number of SUs per second which the DAP processes during the second pass in the LA RRR process. Number of mobile stations that were sent RRR messages in the last statistics reporting period as a result of the LA RRR process. then the change is applied within 1-6 hours. and SCCH seed allow the SU to perform dispatch registration by rejecting the next RR. If the number of conflicts for a specific region reaches the maximum threshold.Dispatch Subsystem Details HA-DAP Functional Description Database Maintenance The HA-DAP uses the following activities for database operations and maintenance: „ „ 8 Database query Database replication Database Query The LMT provides the user with an option to view D-VLR statistics. and check status of the Resource Allocation Group (RAG). Logs hold about 30 minutes of changes in normal load. Activate Replication. Database Replication The HA-DAP replicates database information between the two HA-DAP nodes using the Carrier Signaling Intranet and the Private HA Intranet. Replication events are queued and are sent periodically to the other node in bursts. the latest version of the object is maintained. and the backlog of changes are automatically synchronized when the connection is re-established. then replication performs a conflict resolution to improve the condition. Database replication is automatic and starts up as part of the HA-DAP application. then replication performs a synchronization activity for that particular region. The LMT menu item. query subscriber units stored in the D-VLR. SR 16. When there is a conflict. is used to manually start a database replication if a node has been down for an extended period of time and the database needs to be re-synchronized manually. the following databases are duplicated: „ „ „ „ „ „ D-VLR MDG RAG information Usability information GTT information LMT user information DAP user configured information The queue holds events during communication failures. If a conflict condition is detected when data replication starts on the target node.0 05-Oct-07 6871000P02-A Functional Description 8-31 . During replication. Functional Description 8-32 6871000P02-A SR 16.0 05-Oct-07 . User accounts are now managed through the LMT to support multiple DAP maintenance and provisioning users. the interface is viewed through ssh or a local console. Lynx is viewable through a web browser and utilizes a basic set of HTML elements.Dispatch Subsystem Details HA-DAP Functional Description HA Services Layer The HA Services layer provides the interface for the two HA-DAP nodes to exchange state information. The LMT replaces the previous DAP text-based interface. and the functionality from the iDEN and SMT Menus has been combined. This interface uses a Private IP address that is configured by Open Shortest Path First (OSPF) to work seamlessly with both the Carrier Signaling Intranet and the Private HA-DAP Intranet. The types of maintenance operations that are available have increased dramatically. The LMT contains the following functionality: „ „ „ „ „ „ „ „ Activity Log Management Billing Database Maintenance and Database Query Link Maintenance Load Shedding Parameter Maintenance Software Patch Maintenance System Maintenance (includes configuration file management. and IP network management) User Management „ A text-based version of the LMT is also available if needed through Lynx. and the Private HA Intranet to increase communication between the two HA-DAP nodes. And passwords are no longer needed on individual menu items. 8 Network Management The HA-DAP operation and maintenance activities are provided by the following: „ „ „ 8 LMT Emergency Local Maintenance Terminal (ELMT) Activity log files LMT The LMT is the web-based maintenance terminal interface that operates and maintains the HA-DAP. and to manage switchovers between the active and standby node. Since Lynx is HTML-based. The HA Services layer makes use of both the Carrier Signaling Intranet. The user can also view system messages through the LMT. SR 16. The ELMT has limited functionality and allows the user to start-stop the HA-DAP. and start-stop the web server.Dispatch Subsystem Details HA-DAP Functional Description ELMT The ELMT is used only when the LMT is inaccessible due to network outage or system failure. Activity Log Files The HA-DAP LMT allows the user to backup activity log files to an archive device. shut down and reboot the HA-DAP.0 05-Oct-07 6871000P02-A Functional Description 8-33 . The iVPU supports high availability with the active/standby SPROC/ISB cards.0 05-Oct-07 . „ „ iVPUd Management of BPP2 Resources (wp06003) SR14. Packet Data. The IVPUd operates in a Split Mode Backhaul configuration.com unless otherwise stated. network management access. The iVPU provides the following functionality in the iDEN network: „ „ „ Performs audio routing and duplication for the NGD. iVPU Overview 8 The iVPU supports Dispatch. and each site has an average of 17 carriers. 8 References The following publications may be required to supplement the information contained in this chapter. In the NGD architecture.0 IVPUdi BPP2 Resource Management (wp06006) These documents are available on the Motorola Extranet web site at http://mynetworksupport. static routes are used instead of OSPF to simplify the configuration requirements.EBTS. and the MPS. and internally configures resources on the BPP2 to perform the audio routing and duplication. software.Dispatch Subsystem Details iVPU Functional Description iVPU Functional Description Introduction This subsection describes the hardware. the MDG . Control messages verify the connectivity between the site and the iVPUd and are sent over the C1 link. Provides pass-through connectivity between the HA-DAP . the ISB uses the OSPF routing protocol for high availability. Functional Description 8-34 6871000P02-A SR 16.EBTS. All NGD Dispatch traffic is sent over the C1 link and terminates on the iVPUd. Interfaces with the HA-DAP and MDGs to provide Dispatch and Packet Data service. and Interconnect traffic. In the Mixed Mode architecture. „ „ iVPUd The iVPUd provides Dispatch audio routing and duplication. C1. The iVPUd also provides connectivity to the MPS network for the legacy FR network. there are 3 control links (C0. The iVPUd is configured to interface with the HA-DAP and MDGs to provide Dispatch and Packet Data control. Supports the Horizontal Function with the BPP2 card. and additional information for the iVPU. In the NGD architecture. C13a) between the ACG to the iVPU interface at the physical layer. Manages control links from the HA-DAPs and MDGs (northbound links).motorola. Interconnect vocoding. the iVPUdi supports up to a maximum of 192 sites.0 05-Oct-07 6871000P02-A Functional Description 8-35 . Interconnect Subsystem Details for more information on iVPUi. and also provides connectivity to the MPS for the legacy FR network. and Packet Data services. or 100% All Frame Relay (AFR) Backhaul configuration. the iVPUdi supports up to a maximum number of 252 sites. iVPUi The iVPUi supports Interconnect traffic only. For additional information on how iVPUdi provides vocoding for Interconnect service. Interconnect Subsystem Details. In Split Mode Backhaul. see Chapter 7. In AFR Backhaul mode. The iVPUdi operates in either a 100% Split Mode Backhaul. and 3200 sites in a single Urban Area.Dispatch Subsystem Details iVPU Functional Description iVPUdi The iVPUdi provides Dispatch audio routing and duplication. See Chapter 7. The iVPUdi interfaces with the HA-DAP and MDG. SR 16. The iVPUd configures enough DSPs to equip the FR and MPS connections configured in the database file. A subset of these 18 DSPs are assigned Frame Relay to Internet Protocol (FRIP). HN links reside on a subnet that is separate from the 16 subnets assigned to the FRIP DSPs. and the FRIP is configured for up to 52 DS0s. All FRIPs in a subnet are allocated to a single BPP2. The FRIPs that are assigned to directly handle site traffic are called EBTS Frame Relay to Internet Protocol (eFRIPs). with up to five FRIP DSPs per subnet.0 05-Oct-07 .Each FRIP is configured with up to 10 FR connections and the FR connections are not mixed with MPS connections on a single DSP. and are only configured on an as needed basis. The iVPU distributes the FRIP as well as northbound NE links. The FRIP function provides the following two capabilities: FRIP interworking function to route the various traffic types to and from the sites. FRIP Each iVPUd is configured with up to 16 groups of FRIP DSPs. Functional Description 8-36 6871000P02-A SR 16. And the iVPU ensures that a FRIP DSP is filled to capacity before a new FRIP DSP is configured. Digital Services Level 0 (DS0s) comprise the FR connections assigned to the FRIP. and audio routing and duplication function for intraUrban dispatch calls. The BPP2 BCP is composed of a host processor and 18 DSPs. or the Horizontal Function. The iVPU uses a round-robin criteria to determine which BPP2 card is allocated with the next FRIP DSP.Dispatch Subsystem Details iVPU Functional Description Hardware Description The iVPU is comprised of the following platform configurations: „ „ 8 iVPUd iVPUdi iVPUd There are two iVPUd units to a cabinet and each unit supports up to a maximum of 500 sites (see Figure 8-9 iVPU Front and Rear Cabinet on page 8-37). Horizontal Network Up to 800 Horizontal Network (HN) links are configured on a single DSP. and FRIPs that handle MPS connection traffic are called MPS Frame Relay to Internet Protocol (mFRIPs). and these links are evenly distributed across the active BPP2s in the iVPUdi. System configuration determines if the VPU cage is populated with cards. and three I/O DSPs (see Figure 8-9 iVPU Front and Rear Cabinet on page 8-37). and these links are distributed across the active BPP2 cards on the iVPUdi. A BPP2 card also hosts a maximum of 18 MDG to iVPU links. iVPUdi The iVPUdi shelf contains up to 15 BPP2 cards. with each BPP2 configured for 15 VPF DSPs. SR 16.0 05-Oct-07 6871000P02-A Functional Description 8-37 . A BPP2 card hosts a maximum of three HA-DAP to iVPU links.Dispatch Subsystem Details iVPU Functional Description Figure 8-9 iVPU Front and Rear Cabinet Front Top I/O Panel Top I/O Panel Rear Circuit Breaker Power Supply Modules Circuit Breaker Modules Main Filler Panel Breaker Panel DC Power Distribution Power Supply Shelf VPU Cage Circuit Breaker Label Upper VPU Cage Front and Rear (See Note 1) Fan Modules VPU Cage Cable Access Panel Circuit Breaker Label Lower VPU Cage Front and Rear (See Note 1) Fan Modules Notes: 1. All FRIPs in the subnet are allocated to a single BPP2. the iVPUdi maximizes the efficiency of eFRIPs and mFRIPs that are allocated on the iVPUdi shelf. Functional Description 8-38 6871000P02-A SR 16. IOPs. Each FRIP is configured with up to 10 FR connections. the board is limited to one FRIP subnet. Horizontal Network HN is available on the iVPUdi. and these connections are not mixed with other MPS connections. MPS FR channels. and a Horizontal capable iVPUdi assigns HN to one DSP on the BPP2 for Inter-Urban dispatch calls. IOP functions. A BPP2 card without the Horizontal Function provides a maximum of two FRIP subnets. A FRIP DSP must be filled to capacity before a new FRIP DSP is configured. The eFRIP are assigned to either Split Backhaul or AFR sites. and eFRIP and mFRIP resources are configured on up to 52 DS0s. the iVPUdi handles site traffic with eFRIPs. Like the iVPUd. When initialized in the iDEN network.0 05-Oct-07 . The HN resides on its own subnet. and is independent of the 15 FRIP subnets. If the BPP2 card is assigned a Horizontal Function. FRIPs or Horizontal Function. A BPP2 card is limited to either six FRIP DSPs. or Horizontal Functions. or three FRIP DSPs plus one Horizontal DSP. and are configured only as needed. The I/O DSPs are allocated for site backhaul FR channels. and up to three FRIP DSPs per subnet.Dispatch Subsystem Details iVPU Functional Description The BPP2 board is comprised of a BCP and 18 DSPs where a subset are assigned as VPFs. FRIP Each iVPUdi is configured with up to 15 subnets of FRIP DSPs. and MPS connection traffic with mFRIPs. 0 05-Oct-07 6871000P02-A Functional Description 8-39 . So with the IPFR enabled. When iVPUs have the IPFR feature activated. an external horizontal IP address is also assigned. the NE sends an ActionStatus trap to the OMC-R to record in the log. The IVPU Footprint Reduction Feature (IPFR) significantly reduces the number of IP addresses that are needed. The trap includes the log in/out action. Each iVPUd/di assigns an IP address to every DSP which consumes a large amount of IP addresses. each ISB is assigned an external IP address. SR 16.Dispatch Subsystem Details iVPU Functional Description Software Description This section contains the following software related information: „ „ „ 8 iVPU feature iVPU enhancements Rolling software upgrade 8 iVPU Feature The following feature impacts the iVPU. HA-iHLR. date and timestamp. the following enhancements are available: „ „ Each iVPUd/di shelf utilizes 22 IP addresses (without a horizontal iVPU) Each horizontal iVPUd/di utilizes 23 IP addresses 8 iVPU Enhancements The following enhancements impact the iVPU: „ „ „ „ „ „ „ „ NGDE: Alarm on LMT Login/Logout iVPU SPROC/ISB LED Indicators Root Access Control Enhanced Frame Relay Channel Statistics Enhanced LMT Capabilities LMT Master iVPU Remotely Manage iVPU VRRP Support on iVPU Alarm on LMT Login/ Logout This enhancement gives the ability to track users as they log in and log out of the LMT. or iVPU. Dispatch voice traffic is carried as VoIP. iVPU Footprint Reduction With an iVPUd/di configuration. the userid. When a user logs in/out of the LMT on the HA-DAP. and the SPROC and BPP2 are assigned an IP address. For a horizontal iVPUd/di. or queue overflow events Enhanced LMT Capabilities With this enhancement. This capability only applies to iVPUd and iVPUdi. and a user logs in as super user. This enhancement applies to iVPUd. There are three access control commands added for this enhancement: „ „ „ enable_su_access—Allows root access for the iVPU. The LMT administrator may enable or disable root access on a per node basis. Functional Description 8-40 6871000P02-A SR 16. although any user level may display root access status. Root Access Control This enhancement gives the LMT administrator control over NE root (super user) access. Root access is disabled by default. the LMT user can view frame relay channel utilization over a 30 minute statistics interval. SPROC identifier. but there is no command or GUI option to administer root access across multiple NEs. LMT access is denied. Now. Prior to maintenance activities. including receive errors. and also iVPUdi. Statistics are typically reported to the OMC-R at the end of the statistics interval. ensure that the root access is enabled if needed. disp_su_access—Displays the current root access status for the iVPU. Also the MMI prompt and iVPU log files are updated to include the iVPU identifier. channel statistics are displayed real-time at the LMT. Enhanced Frame Relay Channel Statistics This enhancement adds new FR channel statistics for the iVPU. SPROC state. Previously. userid. The SPROC and ISB were a combined FRU with one set of LEDs that only indicated ISB status.Dispatch Subsystem Details iVPU Functional Description iVPU SPROC/ISB LED Indicators The IVPU SPROC/ISB LEDs are reprogrammed to show SPROC and ISB status. disable_su_access—Disables root access for the iVPU.0 05-Oct-07 . FR channels between the iVPU and the EBTS support the following statistics: „ „ „ Maximum bytes transmitted and received per second Total bytes transmitted and received per measurement interval Maximum Forward Queue Depth per measurement interval FR channels between the iVPU and the MPS supports the following statistics: „ „ „ „ Maximum bytes transmitted and received per second Total bytes transmitted and received per measurement interval Maximum Forward Queue Depth per measurement interval Total packets lost. If root access is disabled. New LED states were added to show SPROC status in addition to ISB status. and timestamp. and associated levels. and supports high availability and failover on the iVPU. The Catalyst switches must be configured by the Hot Standby Router Protocol (HSRP) for high availability and failover. then the ISB becomes the master router for the subnet.Dispatch Subsystem Details iVPU Functional Description LMT Master iVPU Every iVPU has a separate user account file with userids. and all LAN traffic flows through that active router. passwords. The LMT administrator can create and maintain user accounts on any iVPU. technicians used telnet to perform operations and maintenance activities. The user accounts are synchronized when the tx_us_file command transmits the user account file to another iVPU. Since the ISB-2 MAC address is associated with the primary iVPU IP address. Remotely Manage iVPU When iVPU was introduced into the iDEN network. Only one router in the group is designated as the active router. only the master or active VRRP router receives traffic. The disp_element lmt_account_master command is used to determine whether or not this iVPU is the LMT account master. The VRRP router selects a master or active router for the subnet. When the SPROC/iSG Field Replaceable Units (FRUs) in slots 2 and 18 are configured for VRRP. and the IP addresses for all the iVPUs in the Urban. The iVPU ports share the same HSRP IP address. The HSRP introduces the idea of a virtual router. the router with the highest IP address is elected the active router. OMC-R users may launch a telnet session to remotely manage the operations of the iVPU. a priority value is associated with each FRU. Each ISB has a unique IP address. the master iVPU then contains the user accounts file. The iVPU is assigned a primary IP address for use as a default gateway by the bearer cards. SR 16. When a iVPU is selected as the LMT master for the Urban. VRRP Support on iVPU The Virtual Router Redundancy Protocol (VRRP) is available to support static routing instead of the OSPF. all traffic is routed to the ISB-2. and forwards traffic out of the LAN. In normal operation. which is a group of physical routers on the same LAN.0 05-Oct-07 6871000P02-A Functional Description 8-41 . If the tx_us_file command is issued at the LMT master iVPU. The VRRP router (ISB-2) then sends a Address Resolution Protocol (ARP) to the Catalyst switch to associate the Media Access Control (MAC) address with the primary iVPU address. If both the active and standby routers have the same assigned priority. the master user account file of the LMT master iVPU is transferred to every iVPU in the IP address list. If the ISB in slot 2 has a higher priority. This change reduces and simplifies configuration requirements. And all VRRP routers must reside in the same subnet. Deletes a user account. all users with a specified type. or all users. 8 Network Management The iVPUs operation and maintenance activities. and network protocols are maintained by the following: „ „ „ 8 MMI command interface VRRP protocol HSRP protocol MMI Command Interface Table 8-5 The following MMI commands create and manage user accounts on any iVPU: iVPU User Account Commands Description Creates a new user account. some sites and NB links may momentarily lose connectivity through the iVPU. a BPP2 provides connectivity to up to three HA-DAPs and 18 MDGs. All links are then reestablished starting from the time when the subnet was moved to another BPP2.Dispatch Subsystem Details iVPU Functional Description Rolling Software Upgrade The iVPU supports Rolling Software Upgrade (RUP).0 05-Oct-07 . This way the associated sites are prevented from having more than 1 subnet on a BPP2. and from having some BPP2s with no subnets. Due to this re-distribution. During RUP. ISB. reset_password <user_name> tx_ua_file [iVPU IP address] Resets the password to a default value. CCA. iVPU User Account Command Syntax add_user <user_type1> <user_name2> del_user <user_name> disp_users [user_type | user_name | all] mod_user_type <user_type> <user_name> Changes the type (level) for an existing user account. and an iVPU rolling upgrade is performed in either serial or parallel mode. Displays one user. Functional Description 8-42 6871000P02-A SR 16. the iVPU re-distributes the subnets. Transmits the user account file to the specified iVPU. During a RUP when all the boards (SPROC. DOC3. and BPP2s) are upgraded. or all iVPUs (if executed by the master iVPU). The standby router also sends and receives HSRP Hello messages. The HSRP introduces the idea of a virtual router. HSRP Protocol The HSRP provides high availability for a pair of routers in a LAN. The HSRP supports Hello. Priority—Priority configured for the VRRP master (1-255). HRSP Group Identifier—The HSRP group ID for this HSRP router pair (1255). Each VRRP advertisement packet contains the following critical fields: „ „ Virtual Router ID (VRID)—VRRP group identifier (1-255). The default value is 10 seconds. Holdover Timer—Length of time this Hello message is valid. The HSRP periodically sends Hello messages to indicate router status or values. protocol. The VRRP master router uses its physical MAC address as the message source.Dispatch Subsystem Details iVPU Functional Description VRRP Protocol The VRRP supports high availability and failover on the iVPU. The VRRP master sends a VRRP advertisement packet every second. SR 16. VRRP messages are broadcast to all other LAN stations. The active router uses the virtual MAC address for the message. „ „ „ „ The HSRP Group Identifier. The standby router uses its physical MAC address for the message. The ethernet MAC addresses vary based on the router that sends the information. „ The IP address. then the router with the highest IP address is elected the active router. The VRRP standby router does not send a VRRP advertisement. The IP addresses and TTL field in the IP header are used to forward the message to another HSRP router in the same LAN. and the VRRP stations interpret the message based on the destination IP address. Coup and Resign messages in the iDEN network. Priority—The priority configured for the sending router (1-255). which utilizes a virtual IP address and a virtual MAC address. The VRRP is used for static routing and supports high availability for IP hosts in a LAN. HSRP Virtual IP Address—Virtual IP address configured for this HSRP group. If the active and standby routers are assigned the same priority.0 05-Oct-07 6871000P02-A Functional Description 8-43 . and Time to Live (TTL) field in the IP header are used to forward the message to another VRRP router in the same LAN. Advertisement Interval—Interval between advertisement messages sent by the VRRP master: the default value is 1 second. virtual MAC address. The VRRP router selects a master or active router for the subnet. The Hello message contains the following critical fields: „ Hello Timer—Interval between Hello messages sent by this router. The default value is 3 seconds. and all LAN traffic flows through that active router. but does not forward traffic or respond to ARP message requests. and various timer values are all configured in the HSRP. priority. HSRP Virtual IP Address. indicating that the router is active. 4 iHLR Hardware Installation Manual (68P81001Y51) These documents are available on the Motorola Extranet web site at http://mynetworksupport. software. and additional information for the HA-iHLR. 8 References The following publications may be required to supplement the information contained in this chapter. Functional Description 8-44 6871000P02-A SR 16.motorola. „ „ iHLR User Manual (68P81001Y52) SR13. network management access.0 05-Oct-07 .Dispatch Subsystem Details HA-iHLR Functional Description HA-iHLR Functional Description Introduction This subsection describes the hardware.com unless otherwise stated. and provisioning operations. call processing.000 talk groups SR 16.0 05-Oct-07 6871000P02-A Functional Description 8-45 .000 fleets 1. „ „ „ „ „ The HA-iHLR currently supports the following capacity in the iDEN network: „ „ „ 1. Transfers partial databases to other HA-iHLRs when needed. The HA-iHLR is comprised of two redundant iHLR nodes that provide increased reliability and an active/standby configuration.000. while the standby node is available when needed.Dispatch Subsystem Details HA-iHLR Functional Description HA-iHLR Overview The Highly Available iDEN Home Location Register (HA-iHLR) is responsible for dispatch authentication.000. and talkgroup and individual subscriber identification numbers. fleet assignments. Offers feature licensing to view and backup feature data. The active node processes a full load of all mobility.000 subscribers 250. and dispatch and packet data registration in the iDEN network. Receives and maintains its own set of Global Title Translation (GTT) data. The active node contains a standalone database that stores subscriber information. Provides the Remote Management Console (RMC) and Service Resource Module (SRM) Command Line Interface (CLI) to monitor and control the HA-iHLR. The subscriber information includes the types of Dispatch calls subscribers are provisioned for. The HA-iHLR supports the following functionality in the iDEN network: „ 8 Provides a stand-alone database that stores and maintains subscriber information for Dispatch and Packet Data. Provides a LMT interface for subscriber provisioning and services. then the node will switchover. The AlphaServer TS40 server can support up to four CPUs. and a 16-character alphanumeric display. The reset button restarts the system and reinitializes the console firmware. When a single disk fails in either the primary or mirror disk array. this does not cause a switchover. whereas the TS20 server supports up to two CPUs. an alarm panel. a primary and mirror array for each HA-iHLR node with 8 disks each. Each CPU module has 8 MB of secondary backup cache.Dispatch Subsystem Details HA-iHLR Functional Description Hardware Description The HA-iHLR is comprised of the following main components: „ „ „ 8 TS40 AlphaServers Alarm Panel Disk Arrays TS40 AlphaServer The HA-iHLR cabinet contains two AlphaServer TS40 servers. two LEDs. a optional DAT tape. Disk Arrays There are two separate disk arrays on the AlphaServer. and disk array (see Figure 8-10 HA-iHLR Front and Rear Cabinet on page 8-47). The AlphaServer chassis houses a CD-ROM drive. The PCI backplane has two 33 MHz PCI buses that support 64-bit PCI slots. The GREEN LED lights when the power button is depressed. Functional Description 8-46 6871000P02-A SR 16. The MMBs have either 4 Dual Inline Memory Module (DIMM) slots (TS20 server). and an optional disk storage cage. Memory is installed into memory motherboards (MMB) on the system motherboard. A secondary power supply provides redundancy if the original power supply fails. The display indicates status during power up and testing. The power button turns the system AC power on and off. or 8 DIMM slots (TS40 server).0 05-Oct-07 . a floppy disk drive. Alarm Panel The alarm panel has status indicators for each active/standby node. One power supply provides enough power for most configurations. the alarm panel indicates which node needs to be checked. The power supply provides power to system components. If two disks fail. And the amber halt LED lights when the halt button is depressed. If there is an alarm condition in either node. The Operator Control Panel (OCP) is located on the front of the server and consists of three buttons. Dispatch Subsystem Details HA-iHLR Functional Description Figure 8-10 HA-iHLR Front and Rear Cabinet DC Power Distribution Unit Alarm Panel 1U Panel DC Power Connections TS40 #1 Front TS40 #1 Rear SW4310 #1 Fans SW4310 #2 TS40 #2 Front TS40 #2 Rear Front Rear SR 16.0 05-Oct-07 6871000P02-A Functional Description 8-47 . The HA-iHLR Health Check is an option is in the System Maintenance Menu. See the following list of features for the HA-iHLR: „ „ „ „ „ „ „ Load Shedding Status Ethernet Port Status Health Check Ping & Traceroute Restricted Access Key iHLR Data Collection Data Collection Timer Load Shedding Status This feature adds the Load Shedding information option to display the current CPU utilization load level. Ethernet Physical Port Status This feature utilizes the Physical Port Status Check tool to test the status of the HA-iHLRs four ethernet ports. Any user can utilize the Load Shedding information option. and can be run by any user. Ping provides a simple end-to-end IP connectivity check. the View Details button launches the Health Check Detailed Results report which includes what tests passed or failed. In addition. and TraceRoute reveals any routers in the end-to-end route.DAP link status.Dispatch Subsystem Details HA-iHLR Functional Description Software Description This section contains the following software related information: „ „ „ 8 HA-iHLR features HA-iHLR NGD enhancements HA-iHLR database ASCII dump 8 HA-iHLR Features All of the new features for the HA-iHLR impact or extend LMT access or functionality. and HA-iHLR . The summary report also provides links to detailed reports for database replication conflicts. Ping and TraceRoute This feature provides a connectivity check using the LMT. Health Check This feature creates a new summary report for the existing HA-iHLR Health Check. This option also indicates if any services are affected.0 05-Oct-07 . and any user can display the status information. Functional Description 8-48 6871000P02-A SR 16. This tool is an option in the System Maintenance Menu. The LMT administrator may enable or disable root access on a per node basis. HA-iHLR. but there is no command or GUI option to administer root access across multiple NEs. date and timestamp. Dispatch NEs were accessed from the LMT using insecure applications such as HTTP. or iVPU.Dispatch Subsystem Details HA-iHLR Functional Description Restricted Access Key This feature prevents unauthorized users from modifying the HA-iHLR configuration. the userid. When a user logs in/out of the LMT on the HA-DAP. Note Root access is disabled by default. Debugging Data Collection Tool This feature allows the LMT user to select files for data collection. Remote Access Security Previously. Now. SR 16. Telnet and FTP. If root access is disabled. The selected files are bundled for external debugging of field cases or defects. The trap includes the log in/out action. 8 HA-iHLR NGD Enhancements The following enhancements impact the HA-iHLR: „ „ „ „ NGDE: Alarm on LMT Login/Logout Remote Access Security Root Access Control LMT Master iVPU Alarm on LMT Login/ Logout This enhancement gives the LMT administrator the ability to track users as they log in and log out of the LMT. An access key is required to update feature data. The minimum time interval may range from 0 to 15 minutes.0 05-Oct-07 6871000P02-A Functional Description 8-49 . and a user logs in as super user. Secure Shell and Secure FTP. Root Access Control This enhancement gives the service provider control over NE root (super user) access. Prior to maintenance activities. ensure that the root access is enabled if needed. the following secure protocols are available for use: HTTPS. LMT access is denied. Data Collection Time Interval This feature controls the minimum time interval between consecutive HAiHLR data collection events. and this option is restricted to developer and engineer users. the NE sends an ActionStatus trap to the OMC-R to record in the log. the Provisioning Client Manager (PCM). and the program will stop if the HA-iHLR goes into loadshedding while the report is generated. The user accounts are synchronized when the tx_us_file command transmits the user account file to another iVPU. passwords. the Network Operator Technician (NOT). the master iVPU then contains the user accounts file.5 hours and increase CPU utilization. the Network Operator Administrator (NOA). The HA-iHLR only allows a single DB Object Report to be generated at a time. Running the iDBAD program could take up to 1. the Provisioning Interface Manager (PIM). and the Migration Operator Group (MOG). see the Home Location Register (iHLR) User Manual (68P81001Y52).Dispatch Subsystem Details HA-iHLR Functional Description LMT Master iVPU Every iVPU has a separate user account file with userids. If the tx_us_file command is issued at the LMT master iVPU. See the Home Location Register (iHLR) User Manual (68P81001Y52) for specific information on each interface. Network Management The HA-iHLR uses the following network management interfaces in the iDEN network: „ „ „ „ „ „ 8 LMT Emergency Local Maintenance Terminal (ELMT) RMC SRM Backup and restore Command Line Interface (CLI) Provisioning transaction log file LMT The LMT is the web-based interface that operates and maintains the HAiHLR. The LMT has several management/administrator interfaces. Functional Description 8-50 6871000P02-A SR 16. When a iVPU is selected as the LMT master for the Urban. the master user account file of the LMT master iVPU is transferred to every iVPU in the IP address list. 8 HA-iHLR Database ASCII Dump The iDEN Database ASCII Dump (iDBAD) is an automated way to retrieve HA-iHLR Provisioning DB Object Reports. and associated levels.0 05-Oct-07 . And the LMT administrator can create and maintain user accounts on any iVPU. and the IP addresses for all the iVPUs in the Urban. The LMT contains different options for each management/administrator interfaces. the Maintenance Terminal Administrator (MTA). For additional information on the iDBAD. The iDBAD program will only run if the HA-iHLR is not loadshedding. Using the LMT interface to generate DB Object reports is not allowed if the iDBAD program is running. The ELMT has limited functionality and allows the user to start-stop the HA-DAP. SRM The SRM provides a command-line interface to perform system management and maintenance tasks. see the iDEN Commonly Used Commands for Troubleshooting and Restoration (6881012Y94). The LMT web-based interface and database engine must be running in order for the Backup and Restore CLI to function properly.0 05-Oct-07 6871000P02-A Functional Description 8-51 . ELMT The ELMT is used only when the LMT is inaccessible due to network outage or system failure. For additional information on RMC commands see the iDEN Commonly Used Commands for Troubleshooting and Restoration (6881012Y94). and start-stop the web server. SR 16. A console connection is needed to access a node when it is in shut down status. shut down and reboot the HA-DAP.Dispatch Subsystem Details HA-iHLR Functional Description The MTA manages the accounts and sessions for LMT users. Backup and Restore CLI The Backup and Restore CLI allows the user to retrieve a file using FTP to perform a backup or restore. the interface is viewable through ssh or a local console. The SRM prompt (P00>>>) is available when a node is in shut down status. And the MOG performs steps in preparation for a fleet migration. For additional information on SRM commands. RMC The RMC provides a command-line interface to monitor and control the system through console access. The PCM is manages maintenance activities related to the provisioning clients. or when the node is shut down. The PIM is responsible for the maintenance activities related to the provisioning interface. Lynx is viewable through a web browser and utilizes a basic set of HTML elements. A text-based version of the LMT is available if needed through Lynx. such as viewing provisioning session information and provisioning priority management. The NOA performs the highest level of customer system maintenance and diagnostics. Since Lynx is HTML-based. The NOT provides the first level of system maintenance and diagnostics. The Backup and Restore CLI is accessed by doing an rlogin on the HA-iHLR. The provisioning client applications send provisioning transactions to the HA-iHLR to create.0 05-Oct-07 .Dispatch Subsystem Details HA-iHLR Functional Description Provisioning Transaction Log File A provisioning interface is available for the HA-iHLR based on the iDEN Provisioning Protocol (iPP). remove. Functional Description 8-52 6871000P02-A SR 16. See the Home Location Register (iHLR) User Manual (68P81001Y52) for more information. modify. Results of each provisioning transaction are provided in the Provisioning Transaction Log file if logging is enabled in the HA-iHLR LMT. or query provisioning objects in the HA-iHLR database. Transports voice packets between the iDAC and the SMs. One Urban has at least two redundant iDACs available.0 05-Oct-07 6871000P02-A Functional Description 8-53 . APDs and the OMCR in the same Urban.Dispatch Subsystem Details iDAC Functional Description iDAC Functional Description Introduction This subsection describes the hardware. When the voice reaches the remote iDAC. software. An iDEN subscriber in one Urban area can make a Dispatch call to another iDEN subscriber in another Urban. Reports alarms. iDAC Overview The iDAC provides the routing of voice for Inter-Urban Dispatch calls across different Urbans. The iDACs are deployed in the N+1 redundant configuration in each Urban. 8 References The following publications may be required to supplement the information contained in this chapter. and additional information for the iDAC. it specifies the local APD and the remote iDAC to route the voice. state changes. SR 16. and statistics to the OMC-R. One iDAC can support up to 32 APDs (one FR connection per APD). and have a high reliability PCI system that allows for the hot swap replacement of CPU and I/O boards and fans. Provides LMT interface to operate and maintain the iDAC.com unless otherwise stated. „ iDEN CPX1205 Common Platform Hardware Reference Manual (68P80801H50) iDEN Dispatch Access Controller Application Manual (68P80801H55) „ These documents are available on the Motorola Extranet web site at http://mynetworksupport. When the APD receives voice for a call. „ „ The iDAC supports the following capacity in the iDEN network: „ „ „ „ One iDAC supports 15 DAPs (TCP/IP). network management access. it routes the voice to the iDAC. Maintains performance statistics and uploads the statistics when requested by the OMC-R.motorola. The iDAC communicates with DAPs. One iDAC supports 800 remote iDAC (UDP/IP). and with remote iDACs in other Urbans. When a DAP sets up an Inter-Urban Dispatch call. the iDAC converts and sends the voice to its local APD. The iDAC provides the following functionality in the iDEN network: „ „ „ 8 Sends and receives voice and control traffic to APDs and remote iDACs. The iDAC software uses the two alarm panel LEDs on the side of the CPU card. The iDAC uses this interface to communicate with FR devices through the MPS. The iDAC uses the ethernet port marked “1” for the 100 BaseT connection to the OMC-R and DAPs. The PMC module adds four 10/100 Mbps ethernet ports at the rear of the chassis. See the iDEN Dispatch Access Gateway Application Manual (68P80801H55) for additional information. The CPU TM provides four ethernet ports and two RS-232 ports at the rear of the chassis. Each iDAC system slot has a RED LED on the front panel that indicates the status of the iDACs downloaded software. There are also LEDs to indicate power. Alarm Panel The iDAC alarm panel provides a visible indication of the condition of iDAC hardware and software. and these ports are also located at the rear of the chassis. PORT 2 is not utilized. See Figure 8-11 iDEN Dispatch Access Controller . HSSI Interface Module The HSSI interface module carries up to 10 Mbps of traffic.Dispatch Subsystem Details iDAC Functional Description „ One iDAC can handle up to 1000 simultaneous calls. Functional Description 8-54 6871000P02-A SR 16. The LEDs are marked OUT SVC and IN SVC. The HSSI port marked PORT 1 connects to the APDs. The CPU board contains 192 MB Compact Flash and 256 MB of RAM. The iDAC provides a total of two HSSI ports per subsystem. The other ports are not utilized.Front View on page 8-55 for additional information on the iDAC. The PMC module has two LEDs per port: the GREEN LED indicates port status.0 05-Oct-07 . external faults and internal faults. and the YELLOW LED indicates link activity. The iDAC has a GREEN LED on the front panel that indicates the status of the iDAC application start-up and shut down cycle. Ethernet port marked “2” is for the 100BaseT connection to the remote iDACs. The PCI Mezzanine Control (PMC) module is mounted on the CPU board. operational status. The CPU Transition Module (TM) is located in a slot at the rear of the chassis. Hardware Description The iDAC is comprised of the following main components: „ „ „ 8 CPU board HSSI interface module Alarm panel CPU Board The iDAC CPU board is equipped with one 10/100 Megabits per second (Mbps) ethernet port and one RS-232 serial port connector. or Flashing. and on-board temperature sensors.Front View MCP750 CPU Module Slot Number Front View Alarm/Exhaust Fan Module ESD Bond Point HSSI Module Power Supply/Inlet Fan Module SR 16. On the vertical alarm panel labeled UP.The software controlled LEDs adjacent to each slot are software programmed to be RED.Dispatch Subsystem Details iDAC Functional Description There are four hardware controlled LEDs that monitor the status of power supply voltages. All the lights on the first vertical panel are RED in color. Figure 8-11 iDEN Dispatch Access Controller . and indicate that a PCI card is in the slot and the driver is installed. fan speed. the LED can have a status of On or Off. On the vertical alarm panel labeled DOWN.0 05-Oct-07 6871000P02-A Functional Description 8-55 . All the lights on the second vertical panel are GREEN in color. The connection status LEDs are located in the two vertical panels of alarm LEDs on the side of the I/O cards. GREEN or YELLOW. Off. the LED can have a status of On. There should be only one LED ON or Flashing at any time for any pair of LEDs. Installed LEDs (INST) are programmed to be YELLOW. Dispatch Subsystem Details iDAC Functional Description See Figure 8-12 for additional information on the iDAC.0 05-Oct-07 . Figure 8-12 iDEN Dispatch Access Controller .Rear View Dual Earth Ground Attachment Points DC Breaker Switch Cover CPU Transition Module Exhaust Fan Module Rear View DC Input Plug ESD Bond DC Power Input Module Point Slot Number HSSI Transition Module Functional Description 8-56 6871000P02-A SR 16. container status for iDACDAP (DAP links).0 05-Oct-07 6871000P02-A Functional Description 8-57 . and statistics to the OMC-R to notify the operator when an error or warning condition is detected.OMC-R interface LMT The LMT helps to operate and maintain the iDAC system.OMC-R Software Interface The OMC-R provides the iDAC with software and configuration files.OMC-R Network Interface The iDAC reports alarms. Network Management The iDAC uses the following network management interfaces in the iDEN network: „ „ 8 LMT iDAC . SR 16. then the information is written to the file.OMC-R interface GTT-IIC Data File The GTT-IIC ASCII file contains the iDAC-iDAC configuration data. this file gets regenerated after data is successfully validated. and container status for the load. iDAC-APD (SM links) and iDAC-iDAC (WAN-links). iDAC . iDAC . logical link status for iDAC-DAP links. If the iDAC does not have a connection with the OMC-R. The OMC-R system status display console provides status on the iDAC. The iDAC downloads the configuration information from the OMC-R and validates the information. The iDAC also maintains performance statistics and uploads the statistics when requested by the OMC-R. If the remote iDAC is configured and validated.Dispatch Subsystem Details iDAC Functional Description Software Description This section contains the following software related information: „ „ 8 GTT-IIC data file iDAC . the previously downloaded executable and configuration files are utilized. If the iDAC-iDAC information is changed through On-Line Configuration Change (OLCC). state changes. This field-accessible login is available through the iDACs serial port. Provides the MMI interface to operation and maintain the APD. When a Dispatch voice packet is received. „ iDEN Advanced Packet Duplicator Installation Manual (68P080800C45) These documents are available on the Motorola Extranet web site at http://mynetworksupport. network management access.com unless otherwise stated. APD Overview The APD provides the duplication and routing of voice packets for the Legacy iDEN network. the DAP sends the APD a routing table that contains all of the targeted subscriber IDs and EBTS sites associated with each mobile subscriber. The HSSI interface carries all non-OMC-R based packets (typically voice packets). One of the HSSI interfaces is also configured through the OMC-R to carry the call control interface. The APD supports the following capacity in the iDEN network: „ „ „ 500 simultaneous calls per HSSI port A total of 2000 simultaneous calls across all four ports 3200 EBTS sites. and additional information for the Advanced Packet Duplicator (APD). software. The APD provides the following functionality in the iDEN network: „ „ „ 8 Duplicates and routes voice packets to each site on the call. Packets are transferred between the APD and packet switches through four High-Speed Serial Interface (HSSI). The APD after receiving voice packets from one site on a call. 8 References The following publications may be required to supplement the information contained in this chapter. the APD looks up the call ID in the routing table and performs the necessary duplication and routing. When a Dispatch call is initiated. Reports alarm and state information to the OMC-R. The packets are duplicated and routed to the various HSSI boards for re-transmission to the packet switches. Configuration information is sent by the OMC-R to the APD. 800 per port (EBTS and iDACs included in total 3200 device capacity) Functional Description 8-58 6871000P02-A SR 16.0 05-Oct-07 . then duplicates and routes them to the other sites on the call.Dispatch Subsystem Details APD Functional Description APD Functional Description Introduction This subsection describes hardware.motorola. and an HSSI daughter card that provides the HSSI interface. When a port is opened. a 10BaseT ethernet interface. Four PCI slots interface with the four HSSI boards used by the MTX board. SOFT STAT – Sends signals to the LED board to indicate the status of the HSSI ports. PWR STAT – Sends an OK status signal to the LED board. See Figure 8-13 Advanced Packet Duplicator . The APD power supply receives -48 Volts -direct current (Vdc) site power through a front panel power/breaker switch.Dispatch Subsystem Details APD Functional Description Hardware Description The APD is comprised of the following main components: „ „ „ „ 8 MTX board HSSI I/O boards APD power supply LED board MTX Board The MTX board provides the APD with the capability to receive and retransmit data packets through the HSSI I/O boards. The MTX board interfaces with the LED board to provide system status information over four interfaces. LAN activity. The power supply converts the -48 Vdc to regulated and filtered ±12 Vdc and +5 Vdc.0 05-Oct-07 6871000P02-A Functional Description 8-59 . SR 16. The +12 Vdc also powers two front panel fans. and PCI activity. the incoming packet is duplicated and transferred by the HSSI boards to the PCI bus and on to the MTX. DCE – The RS-232 Data Communications Equipment (DCE) port provides a service interface for the APD. and one RS-232 serial interface port. The MTX board interfaces with the HSSI I/O boards using a 32-bit PCI bus. APD Power Supply The APD power supply converts the power coming in from the site to several different voltages. and the boards transmit and receive packets. The HSSI ports are controlled by the MTX. four PCI slots.Front View on page 8-60. The MTX board contains a processor. The ±12 Vdc and +5 Vdc supply outputs apply to the MTX board. a bus system. The interface also monitors push button interrupts from the buttons located on the LED board. „ „ „ HSSI I/O Boards The APD contains four HSSI I/O boards. memory. The HSSI I/O board contains a main card that interfaces with the PCI bus. The OMC-R exchanges status and control information with the MTX through a RJ45 twisted pair connector on the board. These interfaces include the following: „ HW STAT – Sends signals to the LED board to indicate APD hardware status conditions such as processor run. Software Controlled LEDs –The software controlled LEDS include eight Installed and Active LED sets which correspond to eight MTX ports.Dispatch Subsystem Details APD Functional Description LED Board The LED board contains the APD front panel LED status indicators. Also. „ „ „ Figure 8-13 Advanced Packet Duplicator . These buttons send signals to the MTX board initiating abort or reset through the HW STAT interface. and PCI LED.Front View Power Active Installed Port Service Access Functional Description 8-60 6871000P02-A SR 16. LAN LED. the other four are reserved. and a Reset button.) The signals for these LEDs are received through the SOFT STAT interface from the MTX board. push button switches. The APD software uses four of the eight sets of port LEDs positioned on the front panel that correspond to the four APD ports. The LED board provides the following functionality: „ HW LEDs – The hardware LEDs include a RUN LED. an Alarm LED indicates if a hardware failure has occurred during hardware initialization. DCE – The DCE interface from the MTX board is directly connected to the LED board to provide front-panel access to the DCE interface. and a service access connector.0 05-Oct-07 . And the POWER LED is enabled through PWR STAT interface from the MTX board. (Only four of the eight sets are used in the APD. Front-Panel Push buttons – The front panel push buttons include a Abort button. The signals for these LEDs are received through the HW STAT interface from the MTX board. Dispatch Subsystem Details APD Functional Description Software Description This section contains the following software related information about the OMC-R interface. device names. Network Management The APD uses the Man Machine Interface (MMI) as the network management interface in the iDEN network: 8 MMI The APD is equipped with an RS-232 interface that allows a field service terminal to serve as a MMI between field service personnel and the APD.0 05-Oct-07 6871000P02-A Functional Description 8-61 . 8 OMC-R Interface The APD receives its configuration software from the OMC-R through an ethernet interface. MMI commands are used for the following system maintenance tasks: „ „ „ „ „ „ „ Commissioning management Configuration management Device management Fault management Performance management (statistics) Resource management System management The format of an MMI commands is case-sensitive. These exceptions must be entered in uppercase. The APD also reports alarm/state information to the OMCR through the same ethernet interface. SR 16. Exceptions to this requirement include function names. and statistical parameter names. „ „ CPX Common Platform Hardware Reference Manual (68P81131E11) iDEN Surveillance Gateway (iSG) Application Manual (6881012Y17) These documents are available on the Motorola Extranet web site at http://mynetworksupport. When provisioning surveillance in the iDEN network. The iSG utilizes the iDEN network to retrieve surveillance information. The iSG provides the following functionality in the iDEN network: „ „ „ 8 Provides surveillance capability for Dispatch and Packet Data subsystems. The iSG also maintains a list of which IMSI subjects are under surveillance and what type of surveillance is being conducted. Maintains an IMSI listing for surveillance activities. and routes to one or more LEMs. The LEM connects to the iSG through the TCP/IP network.Dispatch Subsystem Details iSG Functional Description iSG Functional Description Introduction This subsection describes the hardware. 8 References The following publications may be required to supplement the information contained in this chapter. iSG Overview The iSG provides law enforcement surveillance capability for the iDEN Dispatch and Packet Data subsystems.0 05-Oct-07 . Filters dispatch call data streams received from DAPs and APDs. each Urban has one or more pairs of iSG for redundancy.motorola. state changes. and additional information for the iSG. software. Reports alarms.com unless otherwise stated. and statistics to the OMC-R. duplicates as necessary. and the surveillance information is transmitted to the LEM. Retrieves surveillance information and forwards it to the LEA. „ „ Functional Description 8-62 6871000P02-A SR 16. the LEM must log into the iSG using the surveillance ID and password that was assigned by the warrant. and forwards it to the appropriate Law Enforcement Agency (LEA) where it is recorded in a Law Enforcement Monitor (LEM). Before connecting to the iSG. network management access. the call is reported to the iSG with the target as subject. 2 USB ports Compact Flash Module On-board debug monitor with self-test diagnostics and status LEDs Reset and Abort buttons Motorola PowerPC 750 processor SR 16. the call is reported to the iSG with the originator as subject and the target as associate. In the NGD architecture. The iSG converts the call information and the user voice to pass on to the LEA using VoIP. a voice path is setup by the DAP. surveillance features remain available even if an individual iSG is removed from service.0 05-Oct-07 6871000P02-A Functional Description 8-63 . CPU The CPU board is a single-slot Compact PCI board equipped with the following features: „ „ „ „ „ „ Error Correction Code (ECC) DRAM 3 Ethernet ports. When the target is under surveillance in the target’s Urban area. and the originator as associate. In the Legacy architecture. APD and MPS to deliver voice over an HSSI FR connection to the iSG.Dispatch Subsystem Details iSG Functional Description When an SU is under surveillance in their Urban area. As a result. there is nothing reported to the iSG in the target’s Urban area. Hardware Description The iSG is comprised of the following components: „ „ „ „ „ „ 8 CPU High Speed Controller (HSC) board HSSI Adapter board Alarm panel DC power distribution panel Cooling panel The iSG contains two separate subsystems in a single chassis for each Urban area. there is nothing is reported to the iSG in the originator’s Urban area. If the target is under surveillance in the originator’s Urban area. If the originator is under surveillance in the target’s Urban area. a voice patch is setup by the iVPUd to deliver voice over an IP to the iSG. Each iSG pair is in an active/active configuration and provides surveillance on the identical set of IMSI. 1 async port (COM1). and distributes the DC input power to the iSG power supplies. The three alarm panel LEDs are positioned above the CPU card on each iSG domain. HSSI Adapter Board The HSSI adapter board transfers data between a host computer and its WAN interface. The fans are mounted on the front of the fan/power supply sled. Each alarm panel has three LEDs.0 05-Oct-07 . The transition module provides two HSSI (TIA/EIA-613) interfaces to the HSSI adapter. and in case of a failure. The DC power supplies are mounted on a sled along with the cooling fans.Dispatch Subsystem Details iSG Functional Description HSC Board The HSC board connects to the CPU module through a local PCI bus. IN SERVICE. Alarm Panel The iSG alarm panel gives information about each of the boards. and contains the following components: „ „ „ „ Dual local buses CPCI Bus and Interface Controller (CPCIBIC) Hot swap CPCI accelerator High Speed Data Link Control (HDLC) The HSSI transition module is linked back to back to the HSSI adapter by a J5 connector. Note The iSG should not be shut off without properly shutting down the system software. Cooling Fans Three fans provide forced-air cooling for the iSGs power supplies. and alarms. See Figure 8-14 iSG 1 and iSG 2 Cabinet on page 8-65. The HSC boards provide a bridge between the two seven-slot Compact PCI buses so that they are managed by a single CPU module. Power to both domains is controlled by the circuit breaker on the back of the chassis. OUT OF SERVICE. and the overall system. DC Power Distribution Panel The DC power distribution panel is located at the rear of the chassis. The HSSI adapter board consists of a motherboard and a rear panel HSSI interface module. the third fan is part of the iSG system for high availability. The HSC functionality provides high availability in the iSG. Functional Description 8-64 6871000P02-A SR 16. Only two fans are needed to adequately cool the components. Use this switch only during an emergency power down situation. board and system LEDs. The HSC monitors and controls the peripherals which includes power and fan sleds. and IMPAIRED. and maintains a control status register that contains information on the status of each module. The DC power distribution panel supports redundant input power supplies to support high availability in the iSG. CPU and I/O controller card cage and transition module card cage. Dispatch Subsystem Details iSG Functional Description Figure 8-14 iSG 1 and iSG 2 Cabinet SR 16.0 05-Oct-07 6871000P02-A Functional Description 8-65 . The service provider uses the SPA to initiate surveillance on an individual or group based on information included in a warrant. consult with the SPA administrator to remove those impacted iSGs from the SPA database. The iSG software is provided by Motorola. Functional Description 8-66 6871000P02-A SR 16. Network Management The iSG uses the following network management interfaces in the iDEN network: „ „ 8 SPA LMT SPA The SPA is the web interface that manages and provisions Dispatch surveillance.Dispatch Subsystem Details iSG Functional Description Software Description This section contains the following software related information: „ „ 8 SPA iSG software SPA The SPA is configured by entering parameter values in the SPA web interface that manages and provisions Dispatch surveillance. The SPA database contains the warrant information. and is maintained in a secure location. When the iSG software is loaded on the iCCP. the Dispatch surveillance feature set is available. If an iSG is permanently removed from service.0 05-Oct-07 . The following parameters are configured through the SPA web interface: „ All Urban area networks (identified by the Urban Area Network Code (UANC) An iSG pair that is associated with each UANC The IP address that allows SPA communication with the iSG for each iSG The IP address that allows LEM communication with the iSG for each iSG „ „ „ iSG Software The iSG is comprised of the iCCP hardware. The iSG uses an ethernet from the SPA to provide surveillance to the DAP. and the iSG software. SR 16. See the iDEN Surveillance Gateway (iSG) Application Manual (68P80802D75) for additional information on the LMT and associated commands.Dispatch Subsystem Details iSG Functional Description LMT An LMT login is available through the iSG serial port by attaching a serial terminal device to the RS-232 port.0 05-Oct-07 6871000P02-A Functional Description 8-67 . If you type EXIT. The field shell is now ready to receive commands. the shell session is ended. Log in as field and the FieldMaint prompt appears. Dispatch Subsystem Details MPS Functional Description MPS Functional Description Introduction This subsection describes the hardware.1 (68P80802A85) MPS Technical Reference Guide (68P80802A95) These documents are available on the Motorola Extranet web site at http://mynetworksupport. The MPS is implemented in a tiered architecture and routes signaling and control information between the DAP. The BPX provides the following functionality in the iDEN network: „ „ Broadband connectivity between MBX nodes. MDG and the EBTS sites.com unless otherwise stated. The DAP controls the source and definitions for routing and movement of voice and data packets. the MPS is a FR digital data packet switch that provides the interface for EBTS FR connections to the DAP. APD. Functional Description 8-68 6871000P02-A SR 16. and additional information for the MPS. When the BPX is used in conjunction with the MGX. Fast switching of Asynchronous Transfer Mode (ATM) cells.motorola. and the data packet paths used during Packet Data networking. The MPS provides the following functionality in the iDEN network: „ „ 8 Provides the FR interface to the DAP. 8 References The following publications may be required to supplement the information contained in this chapter. and the Internet Gateway Exchange (IGX). together they form the MPS complex. software. „ There are two MPS platforms for the iDEN network: Broadband Packet Exchange (BPX)/Multi-Gigabit Exchange (MGX) 8850™ and 8820™.0 05-Oct-07 . „ „ GR Implementation Manual System Release MPS5. The MPS manipulates the paths used by Dispatch voice packets during a Dispatch call. MPS Overview In the Legacy network. network management access. and MDG. Routes voice and data packets for group Dispatch calls and network multicasts to and from the APDs to the correct destination. APD. and MDG. Controls the overhead and manages the flow of voice and data packets between the Dispatch NEs. The other twelve slots are general purpose slots for network interface or service interface cards. Attaches FR packets onto ATM packets. For more information. and one Alarm Status Monitor (ASM) card. The BCC is the central processor for the BPX switch. Transfers the FR connections from a single ATM trunk to the BPX for switching. network management and billing services. The BPX. Network clocking is also provided by the BCC. One of the BCCs is designated the active processor. however.000 to 32. The MGX provides the following functionality in the iDEN network: „ „ Provides connectivity and an interface to the Dispatch NEs. „ „ Hardware Description The MPS consists of the following components: „ „ „ „ 8 BPX MGX 8820 MGX 8850 Service Expansion Shelf (SES) PNNI BPX The BPX switch consists of a shelf with fifteen card slots that may be colocated with the MGX 8820. The ATM cells are then routed by the BPX to another MGX connection to be transferred back to FR packets for use by another NE. is an ATM switch.Dispatch Subsystem Details MPS Functional Description FR is used in the Legacy iDEN network for dispatch. and the MGX shelf converts FR packets to ATM cells. packet data.0 05-Oct-07 6871000P02-A Functional Description 8-69 . and routes to the BPX for delivery to the designated NE. Utilizes from 12.000 Permanent Virtual Circuits (PVCs) per the MPS complex. see Figure 8-15 MPS Cabinet Lineup on page 8-71. Three of the slots on the BPX shelf are reserved for two Broadband Controller Cards (BCCs) that run the AutoRoute or/and Private Network-Network Interface (PNNI) software. The BCC stores configuration databases and system software for the BPX. SR 16. The Broadband Switch Module (BXM) card provides the FR connection on the MGX shelf and supports lines or trunks out of the BPX switch. MGX 8850 and Service Expansion Shelf (SES) interface as needed. while the other BCC is the standby. The BCC runs system software and manages other network cards. and slots 3 and 4 are reserved for Axis Shelf Controller (ASC) cards. The PXM card module is the central processor of the MGX 8850 and is responsible for switching cells. ATM trunk interface—The PXM ATM uplink provides line drivers for the uplink interface. The slots on the top half of the card cage are reserved for T3/E3 and OC-3 cards as the higher bandwidth cell buses reside in the upper portion of the backplane.0. SMs occupy the other 10 slots and provide communication and transfer capability. and a audio and visual alarm interface port. The same is also true for slots 8. the PXM ATM interface uplink card uses a single port from the quad single-mode port back card. Slots 15 and 16 are reserved for the SRM. 16. while the other serves as the standby. 31. there is a corresponding pair of PXM back cards. and 31 (PXMs and SRMs) work together as a card set. The PXM supports two back cards: one for shelf management. and slots 15. The back row is used for line modules. The same is true for slots 2. Slots 7. 16.0. A pair of PXM back cards consists of the following: „ User interface back card—The PXM-UI along with the following: ethernet port. 15.11) is comprised of a card cage with 32 slots.A backplane runs across the card cage spanning all 16 slots which allows for a function module card to be inserted in the slot from the front. 3.Dispatch Subsystem Details MPS Functional Description MGX 8820 The MGX 8220 shelf (version 5. SES PNNI The SES PNNI Controller contains two PXMs that run the PNNI software (version 4. Slots 5 to 14 (10 slots) are available for Service Modules (SMs). One of the PXMs is the active processor. RS-232 control port. and 15 work together as an active/standby set. All PXMs must have a PXM-UI installed in the upper-bay back card slot. slots 1 and 2 are reserved for Broadband Network Module (BNM) cards.20) is comprised of a card cage with 16 slots. 32.0 05-Oct-07 . 4. and one for trunk and line interfaces. In the MGX 8220 shelf. and these cards provide the interface to the MGX 8220 shelf. The maximum number of slots designated for service modules is 24. For SES PNNI application. and storing configuration and firmware images for the other card modules in the shelf. For every installed PXM front card. and 16.15). 32 are for the SRMs. The front row is reserved for function modules as they perform complex tasks such as FR to ATM conversion. The lower-bay back card slot houses the trunk/line interface card. RS-232 maintenance port. and a smaller line module card to be inserted in the slot from the back. MGX 8850 The MGX 8850 shelf (version 1. „ Functional Description 8-70 6871000P02-A SR 16. The PNNI controller connects to the BPX switch by the ATM/OC-3 interface.3. unless double height cards are utilized. T1/E1 timing reference ports. Slots 1. Slots are 7 and 8 are reserved for the primary and redundant PXM1s. MGX COOLING UNIT MGX COOLING UNIT MGX COOLING UNIT MGX BOOSTER FAN UNIT MGX BOOSTER FAN UNIT MGX COOLING UNIT MGX COOLING UNIT Software Description This section contains the following software related information: „ „ „ 8 SES node architecture MGX 8820 architecture MGX 8850 architecture SR 16.0 05-Oct-07 6871000P02-A Functional Description 8-71 .Dispatch Subsystem Details MPS Functional Description Figure 8-15 MPS Cabinet Lineup MGX BOOSTER FAN UNIT Note: Do not stack more than 4 MGXs under one plenum. The BXMs route the ATM cells from one MGX shelf to another. the SES PNNI Controller provides the signaling and routing information to the BPX BXM uplink trunks. The PXM is the central processor for the SES PNNI Controller and provides ATM Switched Virtual Circuit (SVC) routing and signaling for WAN switching networks. SNMP implementation. A subagent also resides on the PXM to support the PNNI application. and application performance. a master agent resides on a PXM card. The interfaces available for user traffic include the following: „ „ „ „ FR to ATM network interworking and service interworking IP-based virtual private network Video Circuit emulation services for private line replacement Functional Description 8-72 6871000P02-A SR 16. The MGX 8820 platform converts incoming data to ATM cells for transport over the ATM network. MGX 8850 Architecture The MGX 8850 switch utilizes a universal edge architecture and supports a wide range of services over narrowband and mid-band user interfaces. In the SES controller. A redundant bus architecture provides high capacity.Dispatch Subsystem Details MPS Functional Description SES Node Architecture The SES node architecture consists of the BPX switch and the SES PNNI Controller. The PXM runs the system software and maintains the trunk to the BPX. The FR channels of the MGX convert FR data to ATM cells. The PNNI is a Soft Permanent Virtual Circuit (SPVC) that connects the FR channels on the MGX shelves.0 05-Oct-07 . The MGX 8850 converts all user information into ATM cells for transport over the ATM network. software-based system architecture that enables the switch to support new features through downloadable software upgrades or new hardware modules. In a iDEN network. A connection on the SES allows the two endpoints of the iDEN PVC to communicate through the ATM network. The MGX 8850 maps all traffic to and from the ATM. MGX 8820 Architecture The MGX 8820 is a modular. and fault management. There is one redundant card per MGX shelf that connects to EBTS sites. power supplies. crosspoint switch matrixes. The MGX 8820 supports one or two Power Entry Modules (PEMs) and these modules provide power supply redundancy for a fully loaded MGX 8820 shelf. and high-speed data and control lines. The CWM provides an interface to monitor and configure the BPX/MGX.50) provides the Graphical User Interface (GUI) that allows the user to select a management tool to operate and maintain the MPS. element management. This one card maintains N+1 redundancy for all the T1/E1 line cards in the shelf. and a collection generation service that allows a user to add connections to the MPS NEs. The CWM provides network management. The backplane also contains a bus for support of N+1 redundancy. the BPX switch shelf is equipped with the following redundant components: common control modules.Dispatch Subsystem Details MPS Functional Description Network Management This section contains the following: „ „ „ 8 Cisco WAN Manager (CWM) MPS redundancy CLI Cisco WAN Manager The CWM (version 15. The SRM card controls redundancy in any of the service modules.0 which is a bulk provisioning tool that sets up all parameters for the user. SR 16. The CWM also utilizes BLAST 4. high-speed network interface cards. MGX 8820 The MGX 8820 cell bus contains two pairs of uni-directional buses for redundancy.1. MPS Redundancy The following MPS components use redundancy to manage resources in the iDEN network. BPX For protection against hardware failure.0 05-Oct-07 6871000P02-A Functional Description 8-73 . The MGX 8850 supports one or two PEMs which are connected to their own independent 48V DC supply. SES The SES node architecture includes the BPX switch and the SES PNNI Controller. The MGX 8850 also has APS and SRM redundancy. The SES node architecture is completely redundant and offers a hitless active/standby switchover.Dispatch Subsystem Details MPS Functional Description MGX 8850 The MGX 8850 backplane contains a main system bus. and are capable of supplying enough power for a fully loaded MGX 8850 shelf. CLI The CLI is used for low-level configuration.0 05-Oct-07 . The cell bus contains two pairs of unidirectional buses for redundancy. The backplane also contains a bus for support of N+1 service module redundancy. and access to the BPX. MGX and SES. These modules provide redundancy. and a cell bus for communication between card slots. Functional Description 8-74 6871000P02-A SR 16. .. .. . ....... .. ...... .. .... ..... 9-9 MDGio Board.... ........... ..... . . 9-6 MDG2 Hardware Description . .... ........ .......... ..... .... . .... ...... . ......................... .......... . ...... ....... .. ... 9-8 MDGp Board .............. ..... ............ .......... ...... .. . .. .. . ...0 05-Oct-07 6871000P02-A Functional Description 9-1 .... . . .. . ..... .... .. .... ..... 9-7 MDG2 Boards ... ... . ...... .. ..... ... . . ... ..... 9-4 Next Generation Dispatch Configurations . .... .. ....... .... ..... .. 9-12 Input Power Switch... ..... 9-5 All Frame Relay (AFR) .. ....... . .......... ...... ........ . ....... . 9-6 References . .... . ... 9-4 Introduction .. ...... .... .. ....... ....... 9-9 MDG Encryption Compression Processor Boards . . . .... ..... . . ..... .. ..... .......... .......... .. .... ...... ........... . .. ... .. ... 9-12 SR 16.... .... ..... . ... .. ... .. .. ... ...... .... . ............... ....... .. ..... .. .. .... ..... . ... . ... .. . ... 9-12 Indicators and Controls . 9-10 Field Replaceable Units .. .... ............... ...... . ... . ..... ...... . .... ...... ......... .. .. ....... .... . 9-6 MDG2 Overview ............ .. 9-3 Packet Data Subsystem Description ... 9-12 Indicators..... .. ........ ... .............. . ... .. .. ........ ............... ... 9-9 Power Supply Modules.... .... . .. . ................... ... ...... . ........ . .. .. .... ..... ... ...... .. . .... ... . 9-5 Mobile Data Gateway 2 . . ..... .. ..... ..... ... .. ... ... .. ........ ... .. . ... ........ ..... . ..... ..... ..Chapter 9 Packet Data Subsystem Details In This Chapter Topic See Page Purpose.... .. ...... . .... .... ............ 9-11 MDG2 Network Management . 9-11 MDG2 Software Description...... .. ....... ...... ..... .. .. ... ... .... .... ... .... ........... .... . ... .... ........ 9-9 PCI Mezzanine Card .... ....... . ............. .... ... .... .. ............. 9-11 OMC-R .. .. ....... ..... 9-4 Packet Data Overview ...... ............. ... ........ .. .... .... .. ..... ...... ......... ....... .... ... ......... ........ ........... System Monitor Board.............. ..... . 9-29 Alarms ......... .. .. ............ ... 9-24 BA Hardware Description.... ............... ... .... 9-28 Data Files . .. ............ ................. .......... ............. ............... ........... .... ................ .... ... ............. .. ..... .... I/O Communications Transition Board ........ ..... ..... ....... . ............... .............. ......................... .. ......... 9-22 Load Shedding . ............... ........................... Main Serial Port Transition Board ..................... .... ................ ................. .... .................... ...... 9-19 MDG4 Network Management ....... .... ... IP Switch Board Cards ........ . ..... . ................. ......... ............ .... .. 9-14 MDG4 Overview ..... .. ........ .................... ........... ...... ... ... . MDGd Card . ......... ..... . .... . ..................... ... Ethernet Board . . .... 9-26 9-26 9-26 9-26 9-27 9-27 9-27 9-28 9-28 BA Software Description ........ .... ......... MDGv Card . ..................... 9-20 OMC-R ... .......... .......... ........... .......... 9-13 Mobile Data Gateway 4 .. .......... 9-14 MDG4 Hardware Description .... ....... ...... ....... .. .......... ....... .................... ............. .. ............. .. ..... .... ..... .... ............. ........ ..... ...... .............. ......... .... ............ .... ...... 9-29 OMC-R ............ .......... ............ ............................ ......... .................... . . ...... .................... .. ............. ........ .. ....................... ........... 9-21 Event Logs . ..... .............. ... 9-22 VLR Mirroring ... . .. 9-23 Billing Accumulator ...... . . . SCSI Hard Drive. .. ........... ... ...... ........ 9-16 9-16 9-17 9-17 9-17 MDG4 Software Description................ ............ . 9-25 Power Converter Module. ... Input Power Transition Board................... ..................... . ............. .... ... .. ............... .................................. ................. ... ...... ............... ......... ...... .... ..................... . ... ....................... .... ... .... 9-14 References .... .. .......... ........ ....... ............ .............. ... .. .... 9-22 RAG Downloads.. ....... ..... .. 9-13 Event Logs ... 9-21 User Interface Menu........ ... ........ ...... ........... ....... .......... ....... .................. .... . .................. CPU Board ........ .. . ................. 9-24 BA Overview ................ 9-29 Functional Description 9-2 6871000P02-A SR 16.. .................. .. .. ....... 9-19 System Management Software ........ ..... ............ ...... .. ....... MDGc Card ....... .......... ......... .. .... 9-22 MDG Cluster Management/Fault Recovery .. ...... . ........... .... 9-16 Alarm Management Controller Card........................ .... ..... ................ ........ .. ........ . . .... ...0 05-Oct-07 ..... . .......... ............ ... ..... ............ .. . . ................... 9-28 BA Network Management... ..................... .... 9-24 References ............................ .. ........ ..................... .... ............ . .............. .... 9-20 MMI Commands ...... .Packet Data Subsystem Details MMI Commands ........... .. ............ ... ............ .............. 9-13 RAG Downloads........... ............................. .......... ..... Ethernet Port Connector Board .. .... .... ...... ................... .. .. ..... ........... . .... including its key functions.Packet Data Subsystem Details Purpose Purpose This chapter describes the major network elements of the Packet Data subsystem in terms of their key hardware components.0 05-Oct-07 6871000P02-A Functional Description 9-3 . and the network management. 9 SR 16. software function. Each key component is explained. hardware and software descriptions. and network management facilities. The Packet Data subsystem consists of the following equipment: „ MDG . Packet Data provides additional data services using the Dispatch subsystem. The Packet Data subsystem is made up of the following equipment: „ „ 9 Subscriber Unit (SU) sends and receives data directly. converting.interfaces to the Internet. Packet Data Networking allows the service provider to become a point-of-presence for mobile users on the Internet. hardware.0 05-Oct-07 . Packet data provides the user access to Intranet and Internet applications using standard Internet protocols. Internet. Billing Accumulator (BA) collects time and bit-transfer information for billing as desired by the service provider. and administer the system is primarily internal to the iDEN system. and software information. Metro Packet Switch (MPS) routes data packets.Packet Data Subsystem Details Packet Data Subsystem Description Packet Data Subsystem Description Introduction This section describes the iDEN Packet Data Subsystem. Mobile Data Gateway (MDG) routes the data to and from the Internet. The MDG also functions as the Foreign Agent (FA). The exception to this procedure is the billing information collection and external routing of the MDG or any servers that may be part of the service provider hosting network. BA . and the Extranet. Virtual Private Network (VPN).collects packet data billing information. Enhanced Base Transceiver System (EBTS) determines the call as packet data and converts the radio link to data packets. iDEN protocol to the Internet Protocol and vice versa. monitor. including functionality. „ „ „ „ The equipment used to control. The packet data process follows the same procedures as dispatch call processing. 9 9 Packet Data Overview Packet Data in iDEN is a non-voice communication interface that connects the subscriber unit directly with the Intranet. The Packet Data subsystem uses the iDEN system Dispatch calling functions and infrastructure. a user can originate or receive packet data. „ Functional Description 9-4 6871000P02-A SR 16. If a Subscriber Unit (SU) is supported and provisioned. The Packet Data subsystem uses portions of the Dispatch subsystem along with its own network elements to provide packet data services. Dispatch Application Processor (DAP) determines services and location. NGD System All Frame Relay (AFR) A site configuration is characterized by all traffic being carried on a single Frame Relay channel. Central LAN . SR 16. See Figure 9-1 below.provides for the routing of private network connections within the Dispatch and Packet Data Subsystems and also utilizes public network connections to other systems and networks.0 05-Oct-07 6871000P02-A Functional Description 9-5 . It is characterized by All Frame Relay (AFR).routes packets from the Internet to the correct MDG for delivery to the subscriber unit. This channel must terminate on an iVPUdi.Packet Data Subsystem Details Packet Data Subsystem Description „ HA (Home Agent) . „ Next Generation Dispatch Configurations Figure 9-1 The Next Generation Dispatch provides higher capacity and greater system reliability in a significantly smaller footprint. software function. 9 References The following is a list of technical documentation and training courses that support the MDG2: „ „ „ „ „ Packet Data Fundamentals Course (FND107) Packet Data Operations & Maintenance Course (OPM208) iDEN System Recovery Topics Course (ADV401) MDG System Manual SR12. This device is rack mounted and has a number of ports available that vary according to the provisioning and growth planning of the individual iDEN system.Packet Data Subsystem Details Mobile Data Gateway 2 Mobile Data Gateway 2 This section describes the Mobile Data Gateway 2 (MDG2) of the Packet Data subsystem.4 (HC06005) „ „ „ „ „ „ „ These documents are available on the Motorola Extranet web site at http://mynetworksupport.0 (68P80800B95) iDEN Packet Data Service –Registration and Call Processes (68P80801C90) Overview of iDEN Packet Data RF Operation and Performance (WP2000002) Understanding iDEN System Fault Tolerance – Packet Data Subsystem (WP2002-023) MDG Command Reference (68P80802D30) Remote Access to 64K MDG MMI (WP2003-020) Packet Data Subsystem Troubleshooting Guide (6881012Y82) Packet Data Troubleshooting Equipment List for 64K MDG (WP2003-019) SR13. Key points about the MDG include that it: „ 9 Is the essence of Packet Data functionality within the iDEN system infrastructure. The MDG is an enterprise-level switching router that directs connections to the Internet. and network management facilities. „ Functional Description 9-6 6871000P02-A SR 16.motorola. MDG2 Overview The primary function of the MDG is to manage the overall process of Mobile IP. Is the interface to the Internet and the World Wide Web for the iDEN system during packet data operation.0 05-Oct-07 .com unless otherwise stated.4 Packet Data Health Check for SR 13. including key hardware components. and LEDs. indicators. and care-of-address information Acts as the Mobile IP foreign agent handling IP registration and decapsulation Responsible for performing packet data reconnect for SUs after each cell change „ Accounting . All cabling attaches to the rear of the card cage. Each has its own set of fans to supply forced-air cooling separate from the VME modules.Maintains a count on incoming/outbound datagrams and transfers this data to BA for customer billing Encryption Œ Œ „ Encrypts IP datagrams sent via the RF link Handles service conflict „ Datagram Delivery . and drives is furnished by 700W autoranging Power Supply Module. The power supply modules (one for each MDG) are installed below the VME module card cage. See Billing Accumulator on page 9-24 for more details. MDG2 Hardware Description The MDG hardware consists of five separate VME CPU cards. The functions of the MDG include the following: „ Mobility Management Œ Œ Œ Assists DAP in SU registration for packet data. As it collects billing data on the subscribers on its Resource Allocation Group (RAG). it must pass that billing data to a BA for storage and later processing.0 05-Oct-07 6871000P02-A Functional Description 9-7 . establishing parameters. working records. cooling fans. power supplies. Has all software and configurable parameters that are downloaded from the OMC (Operations & Maintenance Center).Executes session state transitions based upon: Œ Œ Œ Œ „ Response or lack of response to paging Expiration of the session timer Notification from the DAP Notifies the DAP whenever an SU session experiences a state change The MDG works as a router and a protocol converter but it has no hard drive or means of mass storage. switches.Delivers inbound datagrams after de-capsulation by the Foreign Agent function Session State Control . The MDG can be installed in any standard 19-inch or 23-inch rack. The MDG chassis is a dual plane 9-slot VME chassis manufactured by Motorola. 9 SR 16.Packet Data Subsystem Details Mobile Data Gateway 2 „ „ Is a highly reliable and fault recoverable system entity. fans. DC power for the backplane. 0 05-Oct-07 . If the key is in the RUN position when the chassis is plugged in or power is restored. „ „ MDG2 Boards There are five separate VME CPU cards within the MDG as described below. the power supply cycles on immediately. The RUN position is “on. With the key in the STANDBY position. Figure 9-2 MDG2 . Figure 9-3 Actual MDG2.” The key can be removed in either position to lock the switch in that setting.Packet Data Subsystem Details Mobile Data Gateway 2 The MDG dual 9-slot chassis is equipped with two sets of key switches and indicator lights to control power to the respective card cages.Front View Functional Description 9-8 6871000P02-A SR 16. RESET is a momentary-contact setting that is available only when the key is inserted in the switch. The RESET position supplies a reset signal to the backplane to reset the system in case of a malfunction. See Figure 9-2 for the board placement in the chassis. but the primary side of the power supply remains energized. „ A three-position key turns the power supply outputs on or off. power to the card cage is removed.Front View on page 9-10 provides an actual photograph of the MDG2 without the front cover.” the STANDBY position is “off. The key employs a “standby power” arrangement. This board provides an ethernet IEEE 802.3 (10Base T) interface which is used to connect to the iDEN IP network. MDGio Board The MDGio board provides serial connectivity to the Frame Relay network. It is powered by a single 350Mhz PowerPC 750 processor with 256MB of RAM.35/HDLC ports running the Frame Relay packet switching protocol. It supports from one to four 2MBPS V. The I/O connectivity is provided via the transition module. The MDGio processor board is a single processor CPU board with a 350 Mhz PowerPC 750 processor with 256 MB RAM that also supports a PCI Mezzanine Card (PCM) with two 68360 “QUICC” processors.3 (10BaseT) interface via the port connection panel. SR 16.Packet Data Subsystem Details Mobile Data Gateway 2 MDGp Board The MDGp board is the main processor of the MDG. The MDGio board also provides an ethernet IEEE 802. The three instances of the MDGecp boards are powered by the same hardware as the MDGp board. attaches to the baseboard. powered by two 68360 QUICC communication processors. There are three MDG ECP processor boards.0 05-Oct-07 6871000P02-A Functional Description 9-9 . additionally it is used to send subscriber accounting summaries to a billing accumulator. PCI Mezzanine Card A double-wide PCI Mezzanine Card (PMC). MDG Encryption Compression Processor Boards The MDG Encryption Compression Processor (ECP) boards provide encryption and compression functionality. This interface is used to connect the MDG to the IP network. The ECP boards on a backup MDG (N+1 MDG) are used to store mirror images of the Packet Data VLR information of all active MDG nodes within the same MDG cluster. The ECP is a single processor CPU board with a 350 MHz PowerPC 750 processor with 256 MB RAM. Front View Power Supply Modules DC power for the backplane.and 115/230Vac-compatible versions are available. and -12 Vdc to the system (with power factor correction in the AC version). each providing +5 Vdc. +12 Vdc. Both -48Vdc. and drives is furnished by a UL/CSA/ VDE-approved 700W autoranging power supply module. Each has its own set of fans to supply forced-air cooling. Functional Description 9-10 6871000P02-A SR 16. The power supply modules are not adjustable when they are installed in the system. fans.Packet Data Subsystem Details Mobile Data Gateway 2 Figure 9-3 Actual MDG2. The power supply modules are installed below the VME module card cage.0 05-Oct-07 . MDG2 Network Management The MDG2 operations and maintenance functions are performed by the following: „ „ „ „ „ „ 9 OMC-R MMI Commands Alarm Indicators and Controls RAG Downloads Event Logs Automatic Fault Recover Process SR 16.0 (68P80800B95) for details on the specific procedures and related information.0 05-Oct-07 6871000P02-A Functional Description 9-11 .35 Transition module MVME2434 750PPC-350Mhz with 256MB of memory with PCI Mezzanine Card (PMC) MVME2434 750PPC-350Mhz with 256MB of memory XR fan module 9 „ „ MDG2 Software Description All software and configurable parameters are downloaded to the MDG from the iDEN OMC-R for this fully Network Managed entity. Refer to the MDG System Manual SR12. The following MDG2 components are replaceable in the field: „ „ „ „ XR DC Power Supply XR System Air Filter SMM762 4 port V.Packet Data Subsystem Details Mobile Data Gateway 2 Field Replaceable Units Several components of the MDG2 are replaceable in the field. The top row displays red LEDs for Out of Service activity. first check the fan filter to make sure the airflow is not obstructed. the MDG executes ROM code and establishes a connection to the OMC-R. and fan. They are located on the front panel of the card cage and power supply. There are also three system alarm LEDs to indicate system status.0 05-Oct-07 . „ Functional Description 9-12 6871000P02-A SR 16. During MDG boot. The software load is downloaded to an MDG node by using the Proprietary File Transfer Protocol (PFTP) for both the MDG node bootstrap download and online download. Turning the switch On (I) supplies power to the platform’s power supplies.0 and later MDG2 is capable of communicating with OMC-R only over IP. „ The alarm display panel is located on the front of the chassis and provides LEDs and alarms for each slot of the chassis. In the event of a Fan/Filter Out of Service alarm. slot status. Each of three power/fan modules are equipped with four status LEDs on the front panel. The OMC-R serves as a file server for storing the software load required by each MDG node to function. The SR 14. Indicators Several indicators display the system status.Packet Data Subsystem Details Mobile Data Gateway 2 OMC-R The MDG receives its software download from the OMC-R. Input Power Switch A rocker switch turns the power supply outputs on or off. Turning the switch Off (O) removes input power from the platform’s power supplies. The MDG will then begin the PFTP procedures. the second row displays green LEDs for In Service. status of power supply. The MDG may download files based on several conditions: „ „ „ MDG does not have the file or contains a corrupted file MDG detects a version mismatch MDG detects the OMC-R is forcing a file download Indicators and Controls The MDG 21-slot chassis is equipped with two sets of key switches and indicator lights to control power to the respective card cages (System A and System B). These logs are updated to the SYS processor but should always be viewed from the MMI processor. but is vital to the continued service of Packet Data in a market.Packet Data Subsystem Details Mobile Data Gateway 2 MMI Commands The MDG does not require a user name and password to be entered before using the MMI.0 05-Oct-07 6871000P02-A Functional Description 9-13 . Basic commands are available on all the MMI ports. RAG Downloads A Resource Allocation Group (RAG) download is the process by which the RAG assignment must be moved from an Active MDG to a Standby MDG. There are 3 levels of commands that can be executed: „ „ „ engineering development user (usr) To access the MDG RAM software. These commands can be accessed using the “help” function for each individual board. The location of the event logs is on the MMI processor. or any of the MDGecp modules. This process if often referred to as a "RAG Swap". The process to view the OMC-R event logs from the command prompt of the OMC-R MMI box is described in the OMC-R System Administrator Manual (6881001y44). login to any of the Man Machine Interface (MMI) ports on the MDGio. however. Event Logs Through the use of the OMC-R console it is possible to navigate the event logs on the OMC-R through a GUI interface. commands specific to each module in the MDG. Without a RAG assignment. MDGp. Packet Data will not function in the iDEN system. This process happens in many different situations. There are. SR 16. Mobile-IP is a standard IP protocol which achieves mobility through the cooperation of three entities: Mobile Node (MN). The iDEN packet data architecture supports N+1 redundancy for MDG4 nodes. one at the MDG4 node level and one at the MDG4 cluster level. Home Agent (HA) and the FA. 9 Functional Description 9-14 6871000P02-A SR 16. software function. It becomes active in the event of the failure of an active MDG4 node and assumes the responsibility for the set of users previously served by the failed MDG4.motorola. 384K. 9 References The following is a list of technical documentation and training courses that support the MDG4: „ „ „ „ „ „ Packet Data Fundamentals Course (FND107) Packet Data Operations & Maintenance Course (OPM208) iDEN System Recovery Topics Course (ADV401) SR13. The MDG4 supports up to 600K subscribers per MDG4 node.0 05-Oct-07 . MDG4 Overview The MDG is a network element that provides Mobile subscribers packet data functionality within the iDEN system infrastructure. The Packet Data VLR Mirroring feature allows the backup MDG4 node to automatically reconstruct the VLR information of the mobile users at the time of recovery once the packet data VLR mirror is established. The scalability of the MDG4 node provides the ability to address four subscriber targets: 256K. An MDG4 cluster is composed of multiple (two or more) MDG4 nodes. and network management facilities. 512K. There are N+1 MDGs in an MDG4 cluster. See Figure 9-4 MDG4 in the iDEN Network on page 9-15.4 Packet Data Health Check for SR 13. Two levels of redundancy are used in MDG4 architecture.4 (HC06005) These documents are available on the Motorola Extranet web site at http://mynetworksupport.Packet Data Subsystem Details Mobile Data Gateway 4 Mobile Data Gateway 4 This section describes the Mobile Data Gateway 4 (MDG4) of the Packet Data subsystem. including key hardware components. and 600K subscribers. The MDG4 acts as Mobile-IP Foreign Agent (FA). One of the MDG4 nodes has a backup role. The actual value of N may be affected by the number of RAGs serviced by the MDG4 cluster.4 MDG4 Hardware Installation Manual (68P81001Y76) Packet Data Troubleshooting Equipment List for 64K MDG (WP2003-019) SR13.com unless otherwise stated. 0 05-Oct-07 6871000P02-A Functional Description 9-15 .Packet Data Subsystem Details Mobile Data Gateway 4 The MDG works as a router and a protocol converter but it has no hard drive or means of mass storage. it must pass that billing data to a BA for storage and later processing. Figure 9-4 MDG4 in the iDEN Network SR 16. As it collects billing data on the subscribers on its Resource Allocation Group (RAG). See Billing Accumulator on page 9-24 for more details. and provides the MDG4 node with Ethernet and IP switching. There will be four different platform configurations supported: MDG4 node supporting up to 256K users. running Active/ Standby. It is a 19-inch rack mountable card cage containing single MDG4 node. IP Switch Board Cards Two IP Switch Board (IPSB) cards operate as 2N mated pair. 512K users. (See Figure 9-5 MDG4 Board Layout on page 9-18 for the board layout and Figure 9-6 MDG4 Actual Front View on page 9-19 for an actual view of the MDG4. between the chassis and the packet data IP network.) These include the following: „ „ „ 9 Alarm Management Controller (AMC) cards IP Switch Board (IPSB) cards The three types of logical blades in the MDG4 architecture include: Œ Œ Œ VLR Manager card (MDGv) Data Processing card (MDGd) Communication card (MDGc) The remaining slots of the chassis are populated with the payload cards listed above. and 600K users. Functional Description 9-16 6871000P02-A SR 16. The system management software evaluates the status inputs and responds as appropriate. It also includes routing functionality within the chassis. There are several new cards introduced in MDG4. running Active/Standby.0 05-Oct-07 . The AMC relays system status information to system management software by way of an Ethernet link.Packet Data Subsystem Details Mobile Data Gateway 4 MDG4 Hardware Description The MDG4 chassis is a MXP3121 Multi-Service Platform 21-slot CompactPCI chassis manufactured by Motorola. Alarm Management Controller Card Two Alarm Management Controller (AMC) cards operate as 2N mated pair. and between the chassis and the iDEN IP network. The IPSB card acts as a layer 2 switch and/or layer 3 router. The AMC controls the display of the chassis LEDs and relays. 384K users. Each of the MDG cards are located in the appropriate range of chassis slots according to card type: „ „ „ Slots 1-2 for V cards Slots 3-8 for D cards Slots 9-18 for C cards SR 16. All the packet data session-related information previously managed by the failed MDGd card will be lost (all active packet data sessions will become dormant) as a result of MDGd card switchover. the MDG Cluster Management information. Other information generated by the failed card (such as statistic information and billing information) might also be lost as a result of MDGd switchover. High Speed V. and DS3 (T3) interfaces. operating in N active and 1 standby mode. Additional features of the MDGd card are as follows: „ „ „ There are N+1 MDGd cards. Each active MDGd card has an interface to the PD IP network.35. Other features of the MDGv card include: „ The MDG chassis/application manager and the Master Agent of the node also reside on the MDGv card. The packet data VLR information.Packet Data Subsystem Details Mobile Data Gateway 4 MDGv Card The MDGv card is used for storing and managing packet data VLR information.0 05-Oct-07 6871000P02-A Functional Description 9-17 . „ MDGc Card The MDGc card provides iDEN I/O connectivity with all the cell sites (up to 3200 sites) and the DAPs. A modular I/O interface (plug in module) is built into the MDG4 architecture to support: HSSI. There is no checkpointed data between these MDGd cards. running Active/Standby. and communication between the MDG node and the OMC-R. „ „ „ MDGd Card The MDGd card is used for packet data processing including packet data encryption and compression functionality. The two MDGv cards in the MDG node operate as 2N mated pair. and the chassis management configuration data are checkpointed between the two MDGv cards. communication between the MDG node and the Billing Accumulators. The active MDGv card has an interface to the iDEN IP network which is used for communication between the MDG nodes in the same packet data region. Packet Data Subsystem Details Mobile Data Gateway 4 Figure 9-5 MDG4 Board Layout Functional Description 9-18 6871000P02-A SR 16.0 05-Oct-07 . 9 System Management Software System management software receives system status information from the Alarm Management Controller (AMC) board by way of an Ethernet link.0 05-Oct-07 6871000P02-A Functional Description 9-19 .Actual Front View MDG4 Software Description All software and configurable parameters are downloaded to the MDG4 from the iDEN OMC-R for this fully Network Managed entity. The system management software has the task of making all decisions pertaining to the state of the system and transmitting them back to the AMC board as long as the AMC-CM (Configuration Management) link exists. The system management software evaluates the status inputs and responds as appropriate. SR 16.Packet Data Subsystem Details Mobile Data Gateway 4 Figure 9-6 MDG4 . 0 and later. Œ Œ Œ Elements selected for download are moved to a download queue and the download process immediately started. Network Views supports filtering icons based on element status. „ „ OMC-R will act as the TFTP server Upgraded MDGs request new IP bootstrap code and IP load from the OMC-R The latest enhancements to the OMC-R include the Network Views graphical display and the LDM Download Manager: „ Network Views .Packet Data Subsystem Details Mobile Data Gateway 4 MDG4 Network Management The MDG4 operations and maintenance functions are performed by the following: „ „ „ „ „ „ „ 9 OMC-R MMI Commands Event Logs RAG Downloads VLR Mirroring MDG Cluster Management/Fault Recovery Load Shedding OMC-R In SR 14. Œ Œ „ Colors indicate element status. LDM Download Manager . with each network element identified by type. and status. yellow for impaired status. the MDG/OMC-R communication switches from FR to Internet Protocol (IP). Functional Description 9-20 6871000P02-A SR 16. Extensive warnings alert the operator about network impacts.0 05-Oct-07 . including green for OK. name. and so on.controls download operations using a spreadsheet format. Download rules are built into the package to minimize network disruption.offers a graphical display. 0 05-Oct-07 6871000P02-A Functional Description 9-21 . Figure 9-7 MGD4 User Interface Menu SR 16. User Interface Menu These logins allow the user to easily status the MDG4 and perform specific functions via menu selection. reference should be made to the release notes for the MDG4 version being used.Packet Data Subsystem Details Mobile Data Gateway 4 MMI Commands The MDG does not require a user name and password to be entered before using the MMI. commands specific to each module in the MDG. There are however. See Figure 9-7 below for an example of MDG4 menu. These commands can be accessed using the “help” function for each individual board. There are 3 levels of commands that can be executed: „ „ „ engineering development user (usr) Basic commands are available on all the MMI ports. For the user password. The MDG4 Cluster Management consists of two procedures: Election Process (to elect an MDG node to be the Cluster Coordinator) and Resource Distribution Process (to distribute RAGs among MDG nodes in the cluster). MDG Cluster Management/Fault Recovery MDG Cluster Management is a new concept in the MDG4 architecture that replaces the Automatic Fault Recovery Process (AFRP) in the MDG2 architecture. The N+1 redundancy model within an MDG cluster is maintained to handle failures which are not recoverable within an MDG node or to handle operator initiated switchover. The following is a list of triggering events for an MDG node switchover: „ Failures which are not recoverable within an MDG node Œ Œ Œ Lost communication to PD IP network Lost communication to all DAPs connected to the MDG node Loss of more than 25% of MDGc cards functionality „ „ Graceful shutdown request from OMC-R MDG node failure Functional Description 9-22 6871000P02-A SR 16. MDG Cluster Management is managed by a mechanism resident to the pool of MDG4 nodes within the MDG4 cluster itself without OMC-R involvement. Without a RAG assignment.0 05-Oct-07 . The process to view the OMC-R event logs from the command prompt of the OMC-R MMI box is described in the OMC-R System Administrator Manual (6881001y44). VLR Mirroring The Packet Data VLR Mirroring feature allows the backup MDG4 node to automatically reconstruct the VLR information of the mobile users at the time of recovery once the packet data VLR mirror is established. This is the process in which the RAG assignment must be moved from an Active MDG to a Standby MDG. This process if often referred to as a "RAG Swap". RAG Downloads The Resource Allocation Group (RAG) download is also used by MDG4. The location of the event logs is on the MMI processor. These logs are updated to the SYS processor but should always be viewed from the MMI processor. This process happens in many different situations but is vital to the continued service of Packet Data in a market. Packet Data will not function in the iDEN system.Packet Data Subsystem Details Mobile Data Gateway 4 Event Logs Through the use of the OMC-R console it is possible to navigate the event logs on the OMC-R through a GUI interface. CPU usage.Packet Data Subsystem Details Mobile Data Gateway 4 Load Shedding The load shedding mechanism involves memory usage. SR 16. The load shedding algorithm uses three major priority categories. Alarms will be used to indicate when the trigger points are reached.0 05-Oct-07 6871000P02-A Functional Description 9-23 . including: „ Maintenance messages (including messages related to RAG management and fault management) Fault management Location tracking of Subscriber Unit (SU) „ „ Packet Data traffic is the lowest priority with SU not in session at lower priority than SU in session. and possibly queue sizes as a trigger. 0 05-Oct-07 . which mirrors the billing data to the Secondary BA If the Primary BA becomes unavailable. Provide an avenue for the stored billing records to be transferred to an outside billing center.Packet Data Subsystem Details Billing Accumulator Billing Accumulator References The following is a list of technical training courses that support the BA: „ „ 9 Packet Data Fundamentals Course (FND107) Packet Data Operations & Maintenance Course (OPM208) 9 BA Overview The main function of the BA is to: „ „ Collect and store billing records that are produced by the MDG. the Secondary BA takes over „ Functional Description 9-24 6871000P02-A SR 16. and System Monitor board One BA is the Primary and the other is Secondary Each MDG is connected to both Billing Accumulators Data is sent to the Primary BA. There are two Billing Accumulators in the Packet Data subsystem (See Figure 9-8 Billing Accumulator Mirror Function on page 9-25): „ „ „ „ Each consists of a CPU board. Similar to call data records from the MSC. this information is used by the service provider to gather usage (time and/or data transferred) and similar account information. Ethernet board. The BA consists of the following boards (as shown in Figure 9-9 Billing Accumulator .Packet Data Subsystem Details Billing Accumulator Figure 9-8 Billing Accumulator Mirror Function The BA is a Unix-based computer designed to collect billing data from the MDGs. If a TCP/IP connection is lost to an MDG it is often the BA that turns in the failure to the OMC.Front View on page 9-26): „ „ „ „ „ 9 Power Converter Module CPU Board Ethernet Board System Monitor Board SCSI Hard Drive SR 16.0 05-Oct-07 6871000P02-A Functional Description 9-25 . the BAs are connected through the Local Area Network. BA Hardware Description BAs work in pairs and burn secure connections to MDGs constantly. BAs have one Ethernet port each and can be accessed via telnet if needed. In order to allow connection to the MDGs. It also has a Small Computer Systems Interface (SCSI) bus interface. Ethernet Board The Ethernet board provides a communication path between the VME bus and the devices (IRs. voltage test points.0 05-Oct-07 . The front of the power converter contains voltage level indicators. System Monitor Board The System Monitor Board (SMB) monitors the BA for errors and issues visual and audible alarms in case of problems. and the power converter switch. CPU Board The CPU Board is the main processing board in the BA. and MDGs) on the LAN. Hubs.Packet Data Subsystem Details Billing Accumulator Figure 9-9 Billing Accumulator .Front View Power Converter Module The Power Converter is a modular unit that slides into the BA. Functional Description 9-26 6871000P02-A SR 16. 0 05-Oct-07 6871000P02-A Functional Description 9-27 . The BA back panel consists of the following boards (as shown in Figure 9-10 below): „ „ „ „ I/O Communications Transition Board Ethernet Port Connector Board Main Serial Port Transition Board Input Power Transition Board Figure 9-10 Back Panel of the Billing Accumulator I/O Communications Transition Board The I/O Communications Transition board provides an internal connection for 2 telephone lines and 5 serial communication ports. It has a removable aluminum case that houses the hard disk drive and transition board. These serial ports can be used to connect external modems or communications devices using standard DB-25 or 26 pin connectors.Packet Data Subsystem Details Billing Accumulator SCSI Hard Drive The disk is a Modular Disk Subsystem unit that is used for storing information. Ethernet Port Connector Board The Ethernet Port Connector board provides the Ethernet communication connection. SR 16. Packet Data Subsystem Details Billing Accumulator Main Serial Port Transition Board The Main Serial Port Transition Board provides an interface between the CPU and peripheral devices. 9 Functional Description 9-28 6871000P02-A SR 16. The data is stored on a hard drive until compilation. These files have a “Pr” prefix in the name. This raw data file will be exchanged with the other BA and then forms the input for the processing of data by the Processing Task (PRC). proprietary protocols on top of TCP/IP. allowing you to use the system. Input Power Transition Board The Input Power Transition board Provides an external connection from a –48 volt DC power source and also performs the following functions: „ „ „ Filters input power Provides an in-line fuse Provides an internal board connection for supplying power to a BA resident converter unit Generates airflow through the BA „ BA Software Description The BA uses the AIX UNIX operating system. Once the data files are processed. they can be polled from the server.0 05-Oct-07 . The BA receives usage detail records from the MDG nodes using Billing Message Protocol (BMP) and Billing Session Protocol (BSP). The BA application’s processes run on top of AIX. The AIX operating system and the BA application automatically boot when you power up the DCMS. This board also provides proper termination by attaching a SCSI Terminator Cap to the right of the printer connection. Data Files The BA will write data into a “raw” data file every hour. 0 05-Oct-07 6871000P02-A Functional Description 9-29 . Alarms BA errors can range in severity from minor faults to critical situations that can cause degradation and put billing information at risk.Packet Data Subsystem Details Billing Accumulator BA Network Management The BA operations and maintenance functions are performed using the following: „ „ 9 OMC-R Alarms OMC-R The MDG will generate alarms at the OMC-R when various problems are indicated on the BA. SR 16. on the individual boards. The System Monitor Board will help identify various problems by generating an alarm. such as a power interruptions or a faulty boards. Activated FAILED LEDs indicate problems. .Packet Data Subsystem Details Billing Accumulator NOTES. Functional Description 9-30 6871000P02-A SR 16..0 05-Oct-07 . . .......... .......... . ..... ... .. ........ . .............. ...... 10-4 OMC-R Overview..... ....... 10-10 MMI Processor Application.......... ... ..... . . .. .. .... .... ...... .............. ..... 10-11 Performance Management. ............... .. .... .. ............... ... 10-12 Redundancy .. ... 10-3 OMC-R Functional Description.... ........ ........ .. . .... ...... .......... ....... .......... . .. . .............. ... 10-4 Hardware Description...... 10-13 SR 16.. .... .. . .. . ... ............. 10-5 MMI Processor ............ . ..... 10-9 X-terminal Clients . ...... .. .... .... ........... .. ........ ....... ...... ..0 05-Oct-07 6871000P02-A Functional Description 10-1 ........ ...... 10-10 Network Management............. .. ........... ....... .. . .. ....... .............. .. .... .... ............................ .................. ... .. .... . .. ................ 10-10 System Processor Applications..................... ........ 10-10 NE Software Loads ............. .... .. .... ........ 10-11 Fault Management .................... .. ........... . .... ........... ..... . .. ...... 10-11 Configuration and Load Management ...... . 10-4 Introduction ...... ..... ............. . . 10-11 Event/Alarm Management........ .... ... . ....... 10-12 NGO Functional Description. .... .. 10-5 OMC-R System Processor .. ..... . .. ... .. ...... .................. .... ....... ......... ...... ............... ..... . .... ........ . ...... ............ .................. ........ . ........ .... .. .. ...... ........ .. ......... . . ....... ..... . ................ ...... ..... .. ..... .......... ...... ... ... ... .. ........... .... .... 10-4 References ................ ....... .. ..... ... ... ... . .. .......... . ........... .... .............. .... ......... .... ... . ........ ...... 10-10 Software Description ..... .. . . . 10-12 Security Management ... ....... ..... ........... ........ 10-5 OML ... .......... ... ....... . .... .......Chapter 10 Network Management Subsystem Details In This Chapter Topic See Page Purpose. ...................... ... .... 10-22 LDAP Directory Server .......... ............ ..... . .......... . ... ......... .. ......... ... .......... . .......Network Management Subsystem Details Introduction . .. ... ............... ....... .... 10-23 Hardware Description..... 10-14 Sun Netra 440 ...... ... ........... ....... ......... . . ........... .... ...... .. ..... ......... ......... .. ........... ................ ..... ..... .. .... ............ .......... . ... . 10-23 References .... 10-16 LAN Switch......... ......... 10-21 NBI Access Manager ......... ....... .. ........ ...... ............... ..... ............... ......... ................. . .... .. ......... .. 10-17 LDM Download Manager..... . 10-24 Software Description ............... ... 10-16 NTS ... . 10-16 SunRay X-terminal .... 10-23 SES PNNI Controller ........... ......... ... .......... ........................... 10-13 NGO Overview............ 10-21 NBI Notification Manager .... . .. . ......... . ....... .... .... ........ . . ............ . ... ....... ..... ............................ ...... . .. ............ ........ 10-22 Cisco WAN Manager Functional Description .......... .. . ............ ... ......... . ... ... ............... . .... .. .......... . .. 10-21 Network Management....... ... .. 10-22 Web Server .... ...... .... ... .. .............. . 10-19 Network Views ... . ...... 10-17 AirGen ....... ...... . . . ......... ...... . ... .... ................ ... ..... .......... ...... . ... ......... .... ........ ....... . ... ...... . ... . .... 10-16 Software Description .... ........ .. . ..... 10-13 References .......... .. 10-20 EGT4 Overview . ............. ............. ........... 10-17 Download Queue Manager ... ........... ... .. ....... ... ..... ..... ... .......... ........ .. . ........... ............. .............................. ... ..... ..... ......... . 10-14 Sun StorEdge 3510 Disk Array . .... . 10-16 Sun Netra 240 Backup Server . . ......... ..... .. ...... . ... ..... 10-21 Software Description ........... ..... . .. .. ....... ..... ................... ..... ... 10-24 Network Management..... .... .......... . .. . .. ...... . ......... .................... 10-24 Functional Description 10-2 6871000P02-A SR 16...... ....... ... ...... ........ ........... ................... .. 10-23 PXM .. .... ............... .. ........ 10-23 Introduction .. ............... .. ............. .. ....... ........ 10-23 Cisco WAN Manager Overview ........ .. 10-20 References ...... .................... .................... 10-13 Hardware Description.. ...... ....... . .............. ............. .. . .. ...... 10-19 EGT4 Functional Description .. ................ .... ... ..................... ................. . .... ...... .... ................... ............ . 10-20 Hardware Description.................. ... ... ............ . ... ...... .. . .... .... .......... ...... ... . . ...................25 Hub ...... ............ 10-20 Introduction ......0 05-Oct-07 .. . .. . ...... ............... .. .... ..... .. . ........ .. .... ............... .. ..... 10-22 CORBA Name Service ... 10-21 NBI Object Manager.......... ..... . ... ............. ..... 10-22 Client Web Browser.......... .......... ........ .. ... ....... .. ......... ............... ........ .......... ..... ............ ..... .. ................... .... ........... ............... .. .. ......... ......... ...... .... ............. . .. ... .... .... . ... . ...... ... ........ ....... ................... ................... ....... .............................. .... 10-18 Network Management...... ...... ........... ........ . ..... ........... ..... 10-18 Informix ......... .. . . ...... ..... .. 10-16 External X.... ..... ............. . .... Each NE contains information on the key hardware components.0 05-Oct-07 6871000P02-A Functional Description 10-3 . The following NEs are supported in the legacy Network Management subsystem: „ „ „ Legacy OMC-R Enhanced Global Title Translation Tool (EGT4) Cisco® WAN Manager The following NEs are supported in the next generation Network Management subsystem: „ „ „ Next Generation OMC-R (NGO) EGT4 Cisco WAN Manager SR 16.Network Management Subsystem Details Purpose Purpose 10 This chapter describes the Network Elements (NEs) that comprise the Network Management subsystem. software function. and network management facilities. com unless otherwise stated. and additional information for the Legacy OMC-R. For an installation with more than 500 sites.motorola. The OMC-R however. system configuration reports.0 05-Oct-07 . IOS operation. Provides event logging and display and site status display for the NEs. Administers user accounts at both the primary and secondary OMC-R. Coordinates system configuration and validation. OMC-R Overview The OMC-R is the control center that provides system configuration. the OMC-R manages up to 500 sites and is located in a Mobile Switching Office (MSO). does not provide functional operations for Dispatch. network management access. Interconnect. Functional Description 10-4 6871000P02-A SR 16. the sites must be distributed among multiple OMC-Rs to efficiently manage the traffic and network requirements. or Packet Data services. Each OMC-R provides the following functionality in the iDEN network: „ „ „ 10 Coordinates uploads/downloads to the NEs that interface with the OMC-R. „ In a typical configuration.Network Management Subsystem Details OMC-R Functional Description OMC-R Functional Description Introduction This subsection describes the hardware. software. „ „ „ „ „ „ „ OMC-R System Overview (68P81001Y90) OMC-R Configuration Management Parameters (68P81001Y92) OMC-R Configuration Management User’s Guide (68P81001Y91) OMC-R Event/Alarm Management (68P81001Y94) OMC-R Online Change Configuration User’s Guide (68P81001Y97) OMC-R Performance Management (68P81001Y95) OMC-R System Administrator Guide (68P81001Y93) These documents are available on the Motorola Extranet web site at http://mynetworksupport. and MDG fault tolerance for the entire Urban. 10 References The following publications may be required to supplement the information contained in this chapter. performance monitoring. and status monitoring for the NEs that comprise the iDEN network. a MMI processor. and other miscellaneous equipment.35 physical protocol in the OMC-R links to the T1 or E1 physical protocol used in the BSC network elements. Xterminals.Rear View on page 10-7 for additional information. Two timeslots in one of the T1 span lines is used for OMC-R network management communications. and other OMC-R data is transferred through two timeslots. or frame relay. SR 16. The Network Access Server (NAS) converts V. The OMLs are duplex connections that carry configuration information to each NE. as well as information regarding the status of that NE. The following platforms are available for the OMC-R system processor: „ Sun Fire 4800™—The Sun Fire 4800 contains two 1. and a timing server. See Figure 10-1.25. „ OMC-R System Processor The OMC-R system processor is the communication link. Ethernet maintenance links NEs report status information across the ethernet network using Internet Protocol (IP). ethernet. configuration commands. The following links are utilized with the OMC-R: „ LAN Each OMC-R consists of a system processor. These modules are linked by an ethernet LAN. „ Metro Packet Switch (MPS) links Each NE connects to the MPS using T1 or E1 facilities. 73 Gbyte mirrored hard drives.0 05-Oct-07 6871000P02-A Functional Description 10-5 .2 Gigahertz (GHz) CPUs. Requests for data. resource manager and server for the OMC-R.Network Management Subsystem Details OMC-R Functional Description Hardware Description The legacy OMC-R is comprised of the following main components: „ „ „ „ 10 Operations and Maintenance Links (OML) OMC-R system processor Man-Machine Interface (MMI) processor X-terminal clients OML Each of the NEs are connected to the OMC-R by X. „ Simple Network Management Protocol (SNMP) links Status and event reporting across the OML utilizes the SNMP. and Figure 10-2 Sun Fire 4800. These connections are called OMLs. 4 Giga-Byte (GB) Random Access Memory (RAM). Network Management Subsystem Details OMC-R Functional Description Figure 10-1 Sun Fire 4800.Front View Functional Description 10-6 6871000P02-A SR 16.0 05-Oct-07 . Network Management Subsystem Details OMC-R Functional Description Figure 10-2 Sun Fire 4800.0 05-Oct-07 6871000P02-A Functional Description 10-7 .Rear View „ Enterprise 3500™—The Enterprise 3500 contains one to three 400 Megahertz (Mhz) Central Processing Units (CPUs). and other miscellaneous equipment (see Figure 10-3 and Figure 10-4 Enterprise 3500.Review View on page 10-9. SR 16. and increased storage capacity for medium to large installations. 0 05-Oct-07 .Network Management Subsystem Details OMC-R Functional Description The Enterprise 3500 supports the following: —Up to 800 X.25 sites —6 Dispatch Application Processor (DAP) cluster —8 active Mobile Data Gateways (MDGs) and 1 standby MDG Figure 10-3 Enterprise 3500.Front View Key: HD=HARD DISK Functional Description 10-8 6871000P02-A SR 16. see the OMC-R System Administrator Guide (68P81001Y93). or as a secondary MMI processor in a larger network.Review View Key: SB=SYSTEM BOARD HME=HUNDRED MEGABIT ETHERNET MMI Processor The MMI processor provides the functionality for user management. other operations and maintenance type procedures. The MMI processor may exist as a single primary installation in a smaller Urban.0 05-Oct-07 6871000P02-A Functional Description 10-9 . security. resource allocation. The following platforms are available for the MMI processor: SR 16.Network Management Subsystem Details OMC-R Functional Description Figure 10-4 Enterprise 3500. For more information on the MMI processor. Network Management Subsystem Details OMC-R Functional Description „ Netra 20—The Netra 20 contains a 360 Mhz CPU module with a 4 Megabyte cache. The system processor interacts with NEs and processes event information and performance statistics. The system processor administers system configuration information. remote logins. modems. System Processor Applications The functionality of the system processor includes the storage and download of network status. Up to five X-terminals may be supported by an OMC-R configuration. „ X-terminal Clients The X-terminals are connected through the LAN to the system processor to run various Graphical User Interface (GUI) applications such as the MMI interface. The MMI application includes: „ Informix OnLine Dynamic Server Relational Database Management Functional Description 10-10 6871000P02-A SR 16. either two 9.0 05-Oct-07 .1 GB internal mirrored hard drives. 256 or 512 Mbtye of RAM. Ultra 60—The Ultra 60 contains a 1. Software Description This section contains information on the OMC-R software architecture. see the OMC-R System Overview (68P81001Y90). DVD and tape drives. A code set contains the basic operational and/or software process software for the NE. and other miscellaneous equipment. The X-terminals are equipped with either a 17 inch or 21 inch color display. Each new configuration file or load is made up of code sets. The X-terminals also contain 32 Mb of memory and 128 bytes of Non-Volatile Random Access Memory (NVRAM). user permissions. and other miscellaneous equipment. CD-ROM and tape drives.2 Ghz CPU module with a 4 Megabyte cache. 73 GB internal mirrored hard drives. and X-terminals.1 GB internal mirrored hard drives or two 36. and OMC-R resources such as printers. „ „ „ 10 NE software loads System processor applications MMI processor application NE Software Loads The OMC-R is the repository for the NE operating software and the software for each NE is downloaded as configuration changes or enhancements are needed. MMI Processor Application The MMI application is available on an X-terminal and is used to operate and maintain the applications and databases of the OMC-R system processor. 1 GB of RAM. For more information. and the utilization of performance and configuration information. SR 16. Performance Management The OMC-R collects performance-related data from all of the NEs that are managed by the OMC-R for network planning and optimization. Statistics are collected by each particular NE and periodically uploaded to a database on the OMC-R.Network Management Subsystem Details OMC-R Functional Description „ „ „ „ Reports and query management Event and alarm status definition and display Load and network configuration interface Spreadsheet package for the manipulation and reporting of statistics Network Management This section contains the following network management information: „ „ „ „ „ „ 10 Event/alarm management Performance management Configuration and load management Fault management Security management Redundancy Event/Alarm Management Events/alarms are generated at a specific NE and sent to the OMC-R on the X. This data provides the information needed to fine-tune the performance of the NEs in the iDEN network. In addition. or new software download. or events that require immediate attention. Each new configuration file changes and manages the NEs system software and hardware parameters.0 05-Oct-07 6871000P02-A Functional Description 10-11 . Alarm conditions are referred to as active events. but that provide information regarding the status of a particular NE. Each event sent to the OMC-R includes the alarm condition and informational status reports. The OMC-R collects and stores events and alarms from the NEs to monitor the iDEN network. Events and alarms are also monitored for the links that connect the NEs together. the technician can also reconfigure existing network elements and introduce new system features.25 network. Informational status reports are referred to as a passive events that do not need immediate attention. Configuration and Load Management The NEs application software is updated with each new configuration file. the technician can determine the location of a fault by running diagnostics.Network Management Subsystem Details OMC-R Functional Description Fault Management With the fault management function. Security Management The OMC-R functions are protected by security management. Authorized technicians are assigned security classes that specify what commands are accessed and what output messages are displayed. and changes are only performed by authorized personnel. Redundancy The following redundant module is available with the OMC-R: OMC-R system processor mirrored hard drives Functional Description 10-12 6871000P02-A SR 16. and display NE status.0 05-Oct-07 . place NEs in or out of service. Each authorized technician is given a unique user name and password to gain access to the system. network management access. The NGO merges the OMC-R system processor and the MMI processor into the same physical box on the Netra 440 platform. Coordinates system configuration and validation. IOS operation. To complete the merge. Previously. The Sun Netra 440™ was chosen for the OMC-R platform as the architecture supports up to 10. and additional information for the NGO. NGO Overview The Next Generation OMC-R (NGO) is available in the iDEN network and replaces the legacy OMC-R. the global zone for the OMC-R system processor and a local zone for the MMI processor.0 05-Oct-07 6871000P02-A Functional Description 10-13 . up to three OMC-Rs are utilized in an Urban.com unless otherwise stated.000 sites. and MDG fault tolerance for the OMC-Rs in the Urban. Logs and displays events and site status display for the NEs. one primary and up to three secondary. 10 References The following publications may be required to supplement the information contained in this chapter: „ „ „ „ „ „ „ OMC-R System Overview (68P81001Y90) OMC-R Configuration Management Parameters (68P81001Y92) OMC-R Configuration Management User’s Guide (68P81001Y91) OMC-R Event/Alarm Management (68P81001Y94) OMC-R Online Change Configuration User’s Guide (68P81001Y97) OMC-R Performance Management (68P81001Y95) OMC-R System Administrator Guide (68P81001Y93) These documents are available on the Motorola Extranet web site at http://mynetworksupport.Network Management Subsystem Details NGO Functional Description NGO Functional Description Introduction This subsection describes the hardware. the single box is divided into two Solaris zones. In the next generation architecture. There was also a sizable gain in performance over the Enterprise E3500 and the Sun Fire 4800. Administers user accounts at both the primary or secondary OMC-R. software. „ SR 16. The OMC-R provides the following functionality in the iDEN network: „ „ „ 10 Coordinates uploads/downloads to the NEs. up to seven OMC-Rs were utilized in an Urban.motorola. 25 Hub Network Time Server (NTS) Sun Netra 440 The Netra 440 platform contains the following components (See Figure 10-5 and Figure 10-6 Netra 440-Rear View on page 10-15: „ „ „ „ „ „ „ Solaris 10 Operating System (OS) Four 1.Network Management Subsystem Details NGO Functional Description The OMC-R provides the following capacity in the iDEN network: „ „ A single OMC-R supports a maximum of up to 1000 sites. and each of the two secondary OMC-Rs supports up to 2000 sites for a total of 4000 sites. and the secondary OMC-R supports up to 2000 sites. One primary OMC-R contains the MMI. „ Hardware Description The NGO consists of the following: „ „ „ „ „ „ „ 10 Sun Netra 440 Sun StorEdge 3510™ Disk Array Sun Netra 240™ backup server SunRay™ X-Terminal LAN switch External X.593 GHz processors 32 GB of RAM 4-Port Frame Relay (FR) Card – supports 4 cables Four 146 GB mirrored internal SCSI disk drives Two Fibre Channel Cards – to connect to external disk array Two 10/100/1000 Megabits per second (Mbps) Ethernet ports Functional Description 10-14 6871000P02-A SR 16. One primary OMC-R contains the MMI.0 05-Oct-07 . 35 Four DC Power Supplies Rear View DC Ground Studs SR 16.0 05-Oct-07 6871000P02-A Functional Description 10-15 .Front View On/Standby Button Rotary Switch Hard Drives System Configuration Card Reader DVD Drive Power Distribution Board Fan Trays 0-2 Figure 10-6 Netra 440-Rear View Serial and Net Management Six PCI Card Slots Serial Port (TTYB) E0 E1 Serial Port PCI single FC 2 Gb Host Bus Adapters 4 Port V.Network Management Subsystem Details NGO Functional Description Figure 10-5 Netra 440. an Explora 700™. or an NC900™. External X. Now the backup server on the Sun Netra 240 platform performs daily tape backups for the OMC-Rs in the Urban. The SunRay X-terminal contains the following: „ „ „ „ „ A 17 or 21 inch color display 32 Mb of memory Set of boot PROMS 128 bytes of NVRAM IEEE 802.Network Management Subsystem Details NGO Functional Description Sun StorEdge 3510 Disk Array The Sun StorEdge 3510 external disk array is shared by all the OMC-Rs in the Urban and holds the Informix databases and ne_data partitions. This LAN switch supports the Gigabit speed requirement for the E0 LAN.25 traffic from the legacy BSCs to the OMC-R. SunRay X-terminal The SunRay X-terminal displays the status for the MMI processor and system processor. The disk array is logically partitioned into six Logical Unit Numbers (LUNs). and each OMC-R is allocated 2 LUNs. The X-terminal is typically either a T-HMX™. The StorEdge 3510 holds up to 12 physical disk drives and utilizes RAID5 mirroring.25 switch and NAS hub. Up to five X-terminals are supported by the OMC-R. One hub supports all X. MMI processor and Informix database were completed in separate components. Each OMCR is connected to the disk array by two fibre channel connections.25 hub replaces the existing X. The Sun Netra 240 platform is connected to a tape jukebox by a SCSI interface. 5 clone tapes. backups for the OMC-R system processor. The hub forwards X. NTS The NTS has Global Positioning System (GPS) input and is used as a primary time source.25 traffic in an Urban. and a cleaning tape. A gigabit ethernet (1000 Mbps) has been added to support the tape backup activities.25 Hub The external X. The NTS server supports the Network Time Protocol (NTP) and the Simple Network Time Protocol (SNTP) protocol over IP network. Sun Netra 240 Backup Server Previously.3 Ethernet connection (co-axial or twisted pair) LAN Switch The LAN switch is a Gigabit ethernet switch with 48 ports. The Sun C4 StorEdge™ tape jukebox holds 36 HP StorageWorks Ultrium™ 2 tapes: 30 backup tapes.0 05-Oct-07 . Functional Description 10-16 6871000P02-A SR 16. If a download fails. Uses an Acknowledgement (ACK) for both foreground and background downloads. Allows the technician time to apply a set of download/switch rules to minimize the downtime of NEs. „ „ „ „ „ „ SR 16. a total of 3 retry attempts are allowed. The Download Queue Manager provides the following functionality: „ „ Assigns a download order for each NE in the queue.Network Management Subsystem Details NGO Functional Description Software Description This section contains the following software information: „ „ „ „ 10 Load Management (LDM) Download Manager Download Queue Manager AirGen Informix LDM Download Manager The LDM Download Manager controls download operations using a spreadsheet format. Extensive warnings alert the technician about network impacts. Download Queue Manager The Download Queue Manager works with the LDM Download Manager and is a process on the System Zone. Gives the option to stop a OMC-R download if there is insufficient memory on the Integrated Site Controller (ISC2). The DQM controls and maintains the download queue order of NEs that are selected by the technician for download. Introduces conditions for a successful iDEN Vocoder Processing Unit Dispatch (iVPUd) or iDEN Vocoder Processing Unit Dispatch/ Interconnect (iVPUdi) download.0 05-Oct-07 6871000P02-A Functional Description 10-17 . Download rules are built into the package to minimize network disruption. Elements selected for download are moved to a download queue and the download process immediately starts. Allows the technician to change the download order of a NE whose download has not yet started. Gives precedence to Internetworking Operating System (IOS)/Nonversioned Data (NVD) by blocking versioned downloads that have reserved download slots. At the beginning of the backup. A single backup process captures the OMC-R system processor file systems. iDEN System Objects screen – The OMC-R X25 object moved under Urban. „ „ „ „ „ Informix A shared disk array contains the Informix databases for all of the OMC-Rs in the urban. and BSC time slot number.25 shelf.25 Select screen – Displays the X. BSC screen – Displays input fields for the X.25 shelf and card number.25 shelf and card.Network Management Subsystem Details NGO Functional Description AirGen AirGen is an embedded GUI application running on the OMC-R platform that allows the technician to configure and manage the iDEN NEs. Functional Description 10-18 6871000P02-A SR 16. Airgen provides the following functionality: „ „ OMC-R DTE addresses are associated with shelf/card at the upgrade time. and the Informix database. BSC port number.25 screen – Displays input fields for the X. Urban screen – X. Move BSC screen – Displays X. hub and card fields. OMC-R X.0 05-Oct-07 .25 address. the Informix data is backed up by performing a binary dump to a file on the system processor.25 Line Type indicates the PTI hub uses either T1s or E1s. OMC-R X. The OMC-R builds a backup image that includes the Informix data and the information is sent to the backup server over the E0 LAN. the MMI processor file systems. site address. Timer Based Refresh is available.Network Management Subsystem Details NGO Functional Description Network Management This section contains information on Network Views. Objects in the left panel are ordered and named differently. Each network element is identified by type. And different colors indicate the status of each NE. Text Only View has been added. Detailed Information display changes were incorporated. 10 Network Views Network Views is a graphical display that monitors the NEs in the iDEN network. See Network Management on page 10-11 for a complete description of OMC-R related network management functions. The OMC-R has the same network management functionality as the legacy OMC-R. The Network Views application displays network element status for multiple urbans or a single OMC-R. SR 16. The Network Views application also supports filtering icons based on element status. Quick Filtered View has been added. name and status.0 05-Oct-07 6871000P02-A Functional Description 10-19 . Network Views provides the following functionality: „ „ „ „ „ „ Combined root view is the default. com unless otherwise stated. The EGT4 is configured by default to operate in a 3G mode supporting 2G and 3G Urbans. Monitors software loads between different Urbans. non-version data is ready for download to the local NEs. push the data to the EGT4. The local primary OMC-R configures the local NEs through the on-line change interface. The urban distribution manager process alerts the local OMC-R that new. The urban distribution manager then coordinates the OMC-R processes to perform impact calculations.motorola. and additional information for the EGT4. Functional Description 10-20 6871000P02-A SR 16. Then the download success or failure is reported back to the EGT4. The EGT4 provides the following functionality in the iDEN network: „ „ „ „ „ 10 Supports 2G and 3G Urbans in the same HN. replication. Distributes changed information to the Urbans in the iDEN network. The EGT4 supplies complete interUrban configuration information to the primary OMC-R in each Urban Area. and download of the information. Utilizes the NBI to add or modify HN configuration information. Manages Global 3G Universal Fleet Member ID (UFMI) ranges.0 05-Oct-07 . 10 References The following publications may be required to supplement the information contained in this chapter: „ EGT4 Users Manual (68P81001Y53) These documents are available on the Motorola Extranet web site at http://mynetworksupport. and distribute the change to the other Urbans. The EGT4 also keeps configuration data synchronized between different Urbans in the urban distribution process. network management access. A North-Bound Interface (NBI) between the OMC-R and the EGT4 allows the technician to add or modify the HN configuration information. build. EGT4 Overview Enhanced Global Title Translation Table Tool (EGT4) provides seamless support for both 2G and 3G Urban areas simultaneously in the same Horizontal Network (HN). software. The non-versioned data from EGT4 is coordinated with the local Urban OMC-R through the urban distribution manager process.Network Management Subsystem Details EGT4 Functional Description EGT4 Functional Description Introduction This subsection describes the hardware. The NBI notification manager allows clients to subscribe to certain events. allows the EGT4 to change the EGT4 account password. NBI Access Manager The NBI access manager (nbiaccessmgr) is responsible for EGT4 login/ logout information. The NBI access manager performing EGT4 client authentication (MD5 encryption). The NBI object managers retrieves GTT data from the EGT4. and NEs that may send or receive events asynchronously. SR 16. and keeps track of EGT4 client login sessions.Network Management Subsystem Details EGT4 Functional Description Hardware Description The EGT4 operates on a UNIX workstation with the following minimum requirements: „ 10 A dual 450 MHz processor UltraSPARC series computer from Sun Micro Systems 512 MB RAM 36 GB hard disk Monitor (1024x768 resolution) Ethernet controller CD-ROM drive „ „ „ „ „ Software Description The sections includes the following EGT4-related software information: „ „ „ 10 NBI object manager NBI access manager NBI notification manager NBI Object Manager The NBI object manager (nbiobjectmgr) is responsible for database-related activities and exchanges database tables with the EGT4.0 05-Oct-07 6871000P02-A Functional Description 10-21 . NBI Notification Manager The NBI notification manager (nbinotificationmgr) serves as an event channel for EGT4. and monitors EGT4 table iterators to sequentially access NE information. dispatches the subscribed events to the subscribers when needed. and provides event filtering. NBI. The web browser is installed on the client machine (if the client machine is different than the server). The LDAP server must run co-resident with the web server. LDAP Directory Server The LDAP directory server is the persistent data store utilized by EGT4 to track the current HN network configuration data. Functional Description 10-22 6871000P02-A SR 16. The client machine must have IP connectivity to the machine hosting the EGT4 application.x in a Solaris or Windows environment. The web server must run co-resident with the LDAP directory server. The web server processes requests received from one or more connected web browser clients and performs data storage and NBI operations on their behalf. the JacORB CORBA name service must run on the EGT4 server host machine. Internet Explorer is not supported.2.0 05-Oct-07 .Network Management Subsystem Details EGT4 Functional Description Network Management The EGT4 is a three-tier web application that consists of the following components: „ „ „ „ 10 Client web browser Web server Back-end Light Weight Directory Access Protocol (LDAP) data store COBRA name service Client Web Browser The client web browser serves as the EGT4 interface for managing the system data. CORBA Name Service To support NBI connectivity to one or more OMC-Rs. Web Server The web server is the main processing engine of the EGT4 application. The name server allows various OMC-Rs to register their network location so that the EGT4 may locate them for connection purposes. EGT4 currently supports Netscape v6. com unless otherwise stated. Cisco WAN Manager Overview The legacy Cisco WAN Manager (CWM) is a graphical user interface that allows the technician to select which tool or application to launch for MPS management. Collects statistics on the health of the network. 10 References The following publications may be required to supplement the information contained in this chapter.Network Management Subsystem Details Cisco WAN Manager Functional Description Cisco WAN Manager Functional Description Introduction This subsection describes the hardware. The CWM provides the following functionality in the iDEN network: „ 10 Monitors and configures the Broadband Packet Exchange (BPX)/Internet Gateway Exchange (IGX)/Multi-Gigabyte Exchange (MGX).motorola. network management access. software. and additional information for the Cisco WAN Manager.0 05-Oct-07 6871000P02-A Functional Description 10-23 . The PXM runs the system software and maintains the trunk to the BPX. „ „ Hardware Description This section contains the following CWM-related hardware information: „ „ 10 Processor Switching Module (PXM) Service Expansion Shelf (SES) Private Network-Network Interface (PNNI) controller PXM The PXM is the central processor for the SES PNNI controller and provides Asynchronous Transfer Mode (ATM) switched virtual circuits routing and signaling for Cisco WAN switching networks. „ „ MPS and CWM Health Checks (HC05002) MPS Technical Reference Guide (68P80802A95) These documents are available on the Motorola Extranet web site at http://mynetworksupport. SR 16. Provides connection generation to various MPS elements. network browser. Software Description The CWN downloads firmware to various MPS boxes. traps display.0 05-Oct-07 . image download for the AutoRoute/PNNI network. configuration/restore.Network Management Subsystem Details Cisco WAN Manager Functional Description SES PNNI Controller The SES PNNI Controller uses the combined network management system of Cisco WAN Manager to configure and monitor the SES PNNI node. 10 Functional Description 10-24 6871000P02-A SR 16. The PXM is responsible for network management and communicates with the Cisco WAN Manager station. and saves the MPS configurations. 10 Network Management CWM is used for network and connection management functions such as topology. .. ... ........ .. . .... ........ ... ... . ...... ................ .. .......... ... 11-9 3G-XCDR SAM .... .......... ........................ . .. .. ....... ...... . ... .. ... ...... ....... ... . ... . ..... ..... . 11-8 VSGW Billing. .... ... ................... ..... ............. ............. .. .... 11-6 iGTN ........ .......... .............. . ......... .......... . ........... . ................... . ..... ............. .... ....Chapter 11 Other Network Elements In This Chapter Topic See Page Purpose. ..... .. ...... . .. ....... . ..................... 11-11 ASP .... ..... ......... .. .... ...... ..... ..................... . .. . ....... ..... ...... . ............. ..... ........ . ........ ... ... 11-3 iGW Functional Description .... .... 11-10 Introduction . ... ........ .... .... ...... .............. ........ ... 11-9 NDM Functional Description..... ...... . ..... ......... . . .... ....... ... 11-9 iGTN SNMP Configuration .. .. .. . ....... 11-12 SR 16...... ......... .... ... ........... ...... . .. .... 11-11 PTx-AS ... ...... . ...... .. . ............. ........ .. 11-6 3G-XCDR ..... ... . 11-10 Hardware Description............. ........... ... .0 05-Oct-07 6871000P02-A Functional Description 11-1 ..... .... ...... .. ............... .. .... ....... ..... ........ ......... ..... . ......... ....... .... ...... ..... .. . ... ............. .............. ... 11-9 CLI. ..... ... ........... ......... ......... .... .. ..... .. .......... ..... . ............................ .... . . .... 11-6 Software Description . 11-4 iGW Overview .............. ........ . 11-8 Time Synchronization. ...... ..... ... .............................. . .. .... .. .......... ... .. ........... .......... 11-4 Introduction ........ . ......... .... . .. . ...... .... .... 11-10 NDM Overview.. ......... .... ...... ......... .... .. .. . . ...... 11-9 EGT4 ... .. .. ..... .. 11-8 Network Management.. ... .. ..... .... .... ...... . .. ... ..... .. ... .. 11-6 VSGW ..... ... ............ . ....... ..... .. .... .............. .............. .... ..... .. ... ... . . ...... ....... ......... . . .......... ........... 11-7 iGW Feature ................ . 11-9 OMC-R Network Interface ........ . ...... 11-4 Hardware Description....... ... .... ..... .. . .................. ... .. ........................ ... .... ... 11-14 Network Management.. . . . .... . .. .. .. 11-15 Presence and Availability ..... 11-14 Alarms and Events .. ... . .. ..... ........... .... ...... . . ... . .. . 11-16 Functional Description 11-2 6871000P02-A SR 16.......... . .. ..... ..... ..... .... . ... .... . .... ...... ........... ... . ...... .... . ......... .... 11-16 NDM PWI .. . ... ... .. ... ... .... .... ........ . ..0 05-Oct-07 .... ... .. ....... . . ..... . ...... . .. 11-14 Statistics ... ... .... .. ..... .. ... 11-16 NDM BU Admin Web Interface.. .. .. .. .. ... . ... .. 11-14 Instant Message Text to Speech Dispatch Voice. .... .. .. . 11-15 ASP EM ..... .. . .... . .. ...... . ..... .. . . . .. ....... ... ......... ...... .. 11-15 Dispatch Voice Notes ....... .... . .. ... . .. ..... ... .. . .....Other Network Elements Software Description . .. .......... .... 11-14 DM . . ......... .... ........ ...... ... .. ..... ..... .... ... .. ............ .. .... . ..... ............. ...... .... . . 11-15 Dispatch Voicemail.... .. ... ........ .... ..... . ... .. ... ...... ......... ... . . . ......... .. .. ... ... . .. . ... ... . .... .......... .. .. . ... .. . ... 11-14 Billing......... .. ... . .... .. ...... ..... . Other Network Elements Purpose Purpose This chapter describes other Network Elements (NEs) that comprise the iDEN network. and network management facilities. Each NE includes information on the key hardware components.0 05-Oct-07 6871000P02-A Functional Description 11-3 . The following NEs are included in this chapter: „ „ 11 iDEN Gateway (iGW) NetDispatch Messenger (NDM) SR 16. software function. 0 05-Oct-07 . Provides pseudo HA-DAP. and the bearer plane traffic is involved with Real Time Transport Protocol (RTP) data streams carrying voice traffic. and call control signaling using the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP). as well as Selective Dispatch Group Call (SDGC) calls between a 3G network and the iDEN network. Traffic types are divided into two different types. and additional information for the iGW. iHLR. Functional Description 11-4 6871000P02-A SR 16. including the type of encoding selected for the call. Whereas. The 3G network features high-speed access. Supports SDGC calls. The iGW provides the following functionality in the iDEN network: „ „ „ „ 11 Converts voice packets from 3G encoding to VSELP or AMBE. and iDAC functionality to the iDEN Horizontal Network (HN). Connects to the Operations and Maintenance Center-Radio (OMC-R) for operations and maintenance network communication. a 3G network may use a number of encoding algorithms. The SIP creates a call relationship for multimedia calls such as voice or Video over IP (VoIP). The control plane traffic is involved with the signaling and network management of the system. network management access. The iGW also functions as a Push-to-Talk over Cellular (PoC) server to the SIP domain for the 3G network. 11 iGW Overview The iGW performs signaling and media interworking for private Dispatch calls. the control plane and bearer plane. voice packets are transcoded using Vector Sum Excited Linear Prediction (VSELP) or Advanced Multi-Band Excitation Enhanced plus Two (AMBE++). IP routing in the iGW consists of configuring the iGTN routers. software. In the iDEN network. multi-media and data services over Internet Protocol (IP).Other Network Elements iGW Functional Description iGW Functional Description Introduction This subsection describes the hardware. The iGW converts the voice packets from the encoding standard used in the 3G network to VSELP or AMBE in the iDEN network. and configuring the individual NE (VSGW or 3G-XCDR). „ The iGW internal network uses the Open Shortest Path First (OSPF) routing protocol for all internal iGW IP Layer 3 routing. And SDP sets up all the call details. Connects the Dispatch subsystem with 3G SIP domains. Since iGTNs are the boundary between the local OSPF autonomous system and the external networks. and provides a layer 2 broadcast domain for any locally attached maintenance terminals.Other Network Elements iGW Functional Description The iGW Transport Network (iGTN) provides IP data transport to all NEs in the gateway (see Figure 11-1 iGW in the iDEN Network on page 11-5). The iGTN Virtual Local Area Network 2 (VLAN2) is used for inter-iGTN communication in OSPF Area 0. The Zynx IPSB router boards are also the DR and BDR for the internal chassis OSPF areas. Both iGTNs are also identified as the Designated Router (DR) and Backup Designated Router (BDR) for internal OSPF associations. VLAN2 serves as the native VLAN for inter-switch links. The internal network depends on the configuration of these routers as they serve as the Area Border Routers (ABRs) to the customer IP network. the VSGW and 3G-XCDR Zynx IPSB router boards perform an area border function and are classified as ABR.0 05-Oct-07 6871000P02-A Functional Description 11-5 . the iGTNs are identified as ASBR. Two Virtual Local Area Networks (VLANs) are required for the iGW internal networks. Virtual Local Area Network 3 (VLAN3) provides inter-chassis communication to support OSPF Area 1 of the VSGW bearer plane traffic. Figure 11-1 iGW in the iDEN Network SR 16. The interface between the iGW and the customer network is defined at the exterior interfaces of the iGTNs. Similarly. VLAN3 is used for inter-switch transport of the traffic associated with OSPF area 1 bearer. Other Network Elements iGW Functional Description Hardware Description The iGW is comprised of the following components: „ „ „ 11 iGW Transport Network (iGTN) 3G Transcoder (3G-XCDR) Voice and Signaling Gateway (VSGW) iGTN The iGTN is deployed in four stand-alone cabinets and provides all of the IP transport for the iGW. The 3G-XCDR Zynx Internet Protocol Switch Board (IPSB) routers perform an area border function. VSGW The VSGW provides interworking between the 3G SIP network and the iDEN network. The VSGW converts the standard RTP to the iDEN RTP (iRTP). The Zynx IPSB router boards are also the DR and BDR for the internal chassis OSPF areas. and also checks RTP packet integrity. The 3G-XCDR cabinet contains N+1 redundant 3G-XCDR NEs. The interface between the iGW and customer networks are defined at the exterior interfaces of the iGTNs. The iGTN cabinet is deployed in a duplex configuration and both routers are in active/active mode and are viewed as a single unit to the iDEN network. and the 3G network. The VSGW transfers call detail records to the billing server using FTP. and are classified as ABR.0 05-Oct-07 . the setup flows create a signaling path and a bearer path. 3G-XCDR The 3G-XCDR provides voice transcoding between iDEN VSELP and AMBE++. Functional Description 11-6 6871000P02-A SR 16. The VSGW may act as a pseudo-HA-iHLR by providing the hop route to the 3G network. The iGW is the network interface reference point for all external connectivity to the iDEN network. The VSGW Zynx IPSB router boards perform an area border function and are classified as ABR. The Zynx IPSB router boards are also the DR and BDR for the internal chassis OSPF areas. When a private Dispatch call is initiated. And each iGW NE relies on the iGTN routers for network connectivity. The bearer path carries the VoIP packets between the SIP and iDEN domains. 0 05-Oct-07 6871000P02-A Functional Description 11-7 .Other Network Elements iGW Functional Description Figure 11-2 iGW Cabinet Configuration Software Description This section contains the following software related information: „ „ „ 11 iGW feature VSGW billing Time synchronization SR 16. The following changes were made for SDGC calling on the Logical VSGW Configuration screen: „ VSGW Private Call Billing Enable. they are placed in the billing/unsent directory. A new Selective Dynamic Group Call Timers pane and associated parameters were also added. When an SDGC call is initiated. The billing files are then moved to the billing/sent directory after the files are sent to the Network Operations Center (NOC). The VSGW sends an OK response to the 3G network endpoint signaling that the Dispatch call is connected. and VSGW SDGC Billing Enable parameters were added to the NOC Billing Server Information for 3G pane. the iGW supported private Dispatch calls between two mobile stations. the External Domain-XCDR Interface Information pane was also added. All SNMP traps and syslog events in the iGW use the Universal Coordinated Time (UTC) time zone for all system timestamps. Functional Description 11-8 6871000P02-A SR 16. VSGW Billing Billing files are created in the /billing/active directory on one of the two Payload Home and Billing (PHaB) in each VSGW chassis. Now. the HA-DAP sends an SDGC Page Response Forward message to the VSGW. Default SDGC Call Priority and UFMI Cache Update Enable lines were added to the Subscriber Provisioning Default Information pane. The VSGW sends a Session Progress response and forwards a Proxy Page Request Forward message to the HA-DAP. the VSGW reserves transcoder resources to convert 3G voice to VSELP or AMBE++. „ The Logical VSGW SDGC Timers pane was added to the iGW Expert screen. Time Synchronization The Network Time Protocol (NTP) is used by the iGW NEs for time synchronization. And on the 3G-XCDR screen. the 3G network forwards an SIP invite request. When the billing files are closed by the billing application.0 05-Oct-07 .Other Network Elements iGW Functional Description iGW Feature The iGW-SDGC Enhancement feature impacts the iGW: iGW-SDGC Enhancement Previously. the iGW supports SDGCs between a 3G network and the iDEN network. and in some cases may be configured as an NTP server. When the iDEN subscriber unit (SU) responds to the page. and to convert RTP to the iRTP. The PHaB contains both the Pseudo iDEN Home Location Registers (piHLRs) and the billing application. „ The VSGW Billing Enabled parameter was renamed to VSGW Overall Billing Enable and the functionality has changed. The iGTN platform is an NTP client. Next. The CLI is only used in initial system startup. identifying the OMC-R IP address. The iGTN supports the use of Access Control Lists (ACL) to control which system in the customer IP network has the ability to access the SNMP functions of the routers. The configuration of SNMP on the iGTN routers includes identifying the community strings for both Read-Only (RO) and Read-Write (RW) functions. When the registration is complete. All of the iGW NEs use SNMP for remote configuration management. EGT4 EGT4 assists in the management and translation of network addresses for Integrated Services Digital Network (ISDN) IP and Universal Fleet Member ID (UFMI). iGTN SNMP Configuration The iGTN is not managed by the OMC-R. off-line troubleshooting. SR 16. the 3GXCDR accepts call setup requests from the VSGW. alarms. The VSGW and 3G-XCDR are configured as SNMP clients and report all alarms and traps to the OMC-R. CLI A CLI interface is available to perform operation and maintenance activities for the iGW NEs. The iGTN routers are configured to enable remote management through the SNMP. and trap reporting.Other Network Elements iGW Functional Description Network Management This section provides the following network management information: „ „ „ „ „ 11 3G-XCDR Shelf Application Manager (SAM) OMC-R network interface iGTN SNMP configuration Enhanced Global Title Translations Table Tool (EGT4) Command Line Interface (CLI) 3G-XCDR SAM The 3G-XCDR SAM registers with any VSGW that is provisioned in the iGW.0 05-Oct-07 6871000P02-A Functional Description 11-9 . OMC-R Network Interface The OMC-R provides network management functionality for the iGW NEs with the exception of the iGTN. The 3G-XCDR SAM tells each VSGW what channel element (pairs of vocoders) types are acceptable. and identifying the source address for all SNMP traps and alarms. and remote telnet management for configuration. The OMC-R also provides the communication interface for EGT4 and supports remote management through the use of SNMP version 2. and also mobile subscribers who are active in the iDEN network. commercial IP-solution offering NetDispatch services to the iDEN customer through the web-based Dispatch MessengerTM (DM). or All Frame Relay (AFR) backhaul mode. network management access. The IP network is either ethernet. Allows the service provider to configure the northbound T1 network in Split.0 05-Oct-07 . Functional Description 11-10 6871000P02-A SR 16. in areas where handsets are prohibited. Supports legacy and extended Dispatch service. and additional information for the NDM. 11 NDM Overview NDM provides a cost-effective. The DM application is accessible on a Personal Computer (PC) and connects the user to the ASP over an IP network. wireless LAN. „ The NDM is accessed through the DM application. NetDispatch adds messaging capabilities between IP Clients and subscriber units. The NDM functionality is available in fixed locations. Supports third-party development of the provisioning client interface. or a dialup modem connections. The NDM provides the following functionality in the iDEN network (see Figure 11-3): „ „ „ 11 Offers Dispatch Messenger for NetDispatch services. software. PC users who are connected to the service provider’s IP network use the DM to communicate with other PC users on the service provider’s IP.Other Network Elements NDM Functional Description NDM Functional Description Introduction This subsection describes the hardware. and in areas of poor or no Radio Frequency (RF) coverage. ASP The ASP terminates iDEN connectivity and handles NDM call processing. The NDM system is installed with two ASPs and two PTx-AS for redundancy and availability in the iDEN network.Other Network Elements NDM Functional Description Figure 11-3 NDM Connectivity in the iDEN Network Hardware Description The NDM is comprised of the following components: „ „ 11 Advanced Services Platform (ASP) Push-to-Talk Application Server (PTx -AS) All NDM components utilize the TS230 server. The NDM components receives power from the -48 V DC power system. Each ASP node in the NDM system is connected with one to four T1s. and the required maximum (200 calls per T1. The ASP nodes are deployed in an active/active configuration and are connected to the IP switch and the Rollobox using serial console cables for remote debugging. and each ASP has a minimum of 1 pseudo-EBTS site. The ASP appears to the Mobile Switching Office (MSO) as a pseudo-EBTS. and to the iDEN network over a T1/E1 interface. The NDM servers communicate to Dispatch Messenger users over an IP network. 800 calls/node) simultaneous call load.Front and Rear on page 11-13). which is a dual processor 2 Rack Unit (RU) server platform (see Figure 11-4 NDM Cabinet . SR 16.0 05-Oct-07 6871000P02-A Functional Description 11-11 . Each node independently supports the required maximum (80K) subscriber connection capacity. 146 GB hard disk PCI Slots—Slot 1 is the security accelerator card.Other Network Elements NDM Functional Description The ASP is comprised of the following components: „ „ „ „ „ Dual 2.4 Gigahertz (GHz) processors 2 Giga-Byte (GB) memory.0 05-Oct-07 . The PTx-AS servers are colocated with the ASP servers and are typically located at the iDEN MSO.4 GHz processors 2 GB memory. and Slot 3 is the ethernet card 146 GB ultra Small Computer System Interface (SCSI) disk drive „ Functional Description 11-12 6871000P02-A SR 16. The PTx-AS is comprised of the following components: „ „ „ Dual 2. Slot 2 is empty. 146 GB hard disk Peripheral Channel Interconnect (PCI) Slot 1 – security accelerator card PCI Slot 2 – T1 card PCI Slot 3 – ethernet card PTx-AS The PTx-AS is responsible for deploying the NDM application which includes user authentication and a Web browser. Other Network Elements NDM Functional Description Figure 11-4 NDM Cabinet .Front and Rear ASP and PTx Servers (Rear) ASP and PTx Servers (Front) Front Rear SR 16.0 05-Oct-07 6871000P02-A Functional Description 11-13 . Network Management This section contains the following network management information: „ „ „ „ 11 DM ASP EM NDM Provisioning Web Interface (PWI) NDM BU Admin Interface 11 DM DM is the Windows-based software application that enables Dispatch services and messaging capabilities for Dispatch users on an IP. Alarms and Events Alarm and events are available in real time from the Welcome page in the ASP Element Manager. call alert. and alarm statistics are collected and assigned to a unique file. The call data stored in the billing file is used by the administrator to create billing records for utilization charges and perform statistical analysis on call profiles. Statistics that are generated in the last 7 days are viewable on the ASP Element Manager (EM). At the start of each day of the week.0 05-Oct-07 . Statistics Statistics for private call. dispatch statistics.Other Network Elements NDM Functional Description Software Description This section includes the following software related information: „ „ „ 11 Billing Statistics Alarms and events Billing The NDM generates billing files that are unique from the HA-DAP. group call. a statistics file is generated for that particular day. The following features are available in the DM application: „ „ „ „ Instant Message Text to Speech Dispatch Voice Dispatch Voicemail Presence and Availability Dispatch Voice Notes Functional Description 11-14 6871000P02-A SR 16. Each billing file contains a record of completed DM calls that are processed by the ASP. and Emergency Group Call. and from a SU to a PC user.Other Network Elements NDM Functional Description To initiate a call. A PC user and a SU can initiate and receive the following Dispatch calls: Private Call. The call types available through the DM application depend on service provider network configuration and policies. and is forwarded to the HA-DAP where it is processed. The ASP can detect if PC users are online (logged in) or offline (logged out). A call can be initiated from one PC user to another PC user. Some service providers may not support NDM call types such as User Defined Group Call or Emergency Group Call. BU Admin accesses the ASP data store from a public IP through the PTx AS. Each Business Unit has a Business Unit Manager. Instant Message Text to Speech Dispatch Voice The Instant Message Text to Speech Dispatch Voice feature allows PC users to send text-to-speech messages to other PC users and/or mobile subscribers. BU Admin is provided with an account and a ID/password/e-mail address. the PC user selects the Private or Group Name/ID from the DM window and speaks into the microphone. The Instant Message Text to Speech Dispatch Voice feature is initiated only by a PC user. Calls that are initiated by PC users through the ASP are transparent to the iDEN network. SU and PC users can leave a message with the PC user’s Dispatch Voicemail. User Defined Group Call (UDGC). registered in the iDEN network. The presence and availability feature is only available for PC users. The NDM system also allows the iDEN technician to group NDM users into business units. but may be received by a PC user or a SU. Presence and Availability NDM provides real-time presence and availability information to all PC users. SR 16. Call Alert. A SU cannot initiate the Instant Message Text to Speech Dispatch Voice feature since this service requires the use of the DM and a PC. from a PC user to a SU.0 05-Oct-07 6871000P02-A Functional Description 11-15 . Dispatch Voicemail The Dispatch Voicemail feature allows PC users to receive voicemail for Private Calls and retrieve the message at a later time. These calls are processed as if they were initiated through an EBTS. Dispatch Voice Notes The Dispatch Voice Notes (DVN) feature allows a PC user to send prerecorded audio messages to another PC user. Only PC users can access the Dispatch Voicemail feature. This feature is not available to a SU because this service requires the use of the DM and a PC. Call setup information is sent over the PC user’s IP network or dial-up connection to the ASP. and Group Dispatch Call. or a SU in the iDEN network. or BU Admin assigned to manage users in that Business Unit. Every DM user is provisioned in the HA-iHLR and then the ASP for authentication. 11 NDM PWI The NDM PWI is used to provision the ASP. and provides configuration and fault and performance management for that node. Provisioning includes assigning user identity information for authentication. The NDM PWI is accessible through the ASP EM. 11 NDM BU Admin Web Interface The NDM BU Admin interface is used by an authorized 3rd party or customer representative to manage users and International Mobile Equipment Identifiers (IMEIs) assigned to a specific service provider business unit. and service related access. The service provider creates a business unit. 11 Functional Description 11-16 6871000P02-A SR 16. service providers can give user management operations for large clients to the clients themselves.Other Network Elements NDM Functional Description ASP EM The ASP EM is activated on each ASP node during installation.0 05-Oct-07 . and then assigns a business unit administrator to manage the Dispatch Messenger users. With the BU Admin interface. The ASP EM interface is accessible through the service provider’s IP network. 11-15 element manager 11-16 audio routing 8-34 Act) XCIPIO 5-6 Call and Data Services for Subscribers and Users 2-3 Call Intercept Provisioning Center 7-39 call monitoring/surveillance 2-4 cell 2-9 Cisco WAN Manager functionality 10-23 hardware description 10-23 network management 10-24 overview 10-23 PXM 10-23.Index Symbols Numerics 5K Sites 4-3 A Access Control Gateway (ACG) 6-13 ACG (Access Control Gateway 6-13 Advanced Services Platform. See BPX BU admin web interface 11-16 Business Change Control Channel.10-24 SES PNNI controller 10-24 software description 10-24 Cisco WAN Manager.0 05-Oct-07 6871000P02-A Functional Description i . 10-18 Alarm Management Controller card 9-16 Alarm on LMT login/logout 8-28. See BCCB C CALEA (Communications Assistance for Law Enforcement SR 16. See CALEA Configuration Management 2-6 Core Processor 7-28 CPU board 9-26 D DAP account and performance management 8-18 availability management 8-19 BCCB 1008 8-17 BCCB 1020 8-17 BCCB 862 8-16 call processing management 8-19 capacity 8-10 CCP layer 8-21 common agent 8-20 components 8-12 configuration and state management 8-19 core architectural models 8-18 CPU 8-13 database management 8-18 enhancements 8-16 event logs 8-20 fleet ID 8-11 fleet member ID 8-11 functionality 8-10 hardware description 8-12 iDEN menu 8-19 IOC 8-13 MAP 8-21 MSD 8-13 multiple simultaneous talk group ID 8-12 network capacity 8-10 network management 8-19 overview 8-10 R10K 8-12 R10K cabinet 8-14 R12K 2-way 8-12 R12K 4-way 8-12 R12K cabinet 8-14 resource management 8-18 ROC 8-13 site specific parameters 8-12 SMT menu 8-20 SSC 8-13 subscriber parameters 8-10 system control management 8-18 talk group ID 8-11 B BA 9-24 back panel 9-27 front view 9-26 hardware description 9-25 I/O Communications Transition board 9-27 mirror function 9-25 network management 9-29 OMC-R 9-29 software description 9-28 system monitor board 9-26 overview 9-24 Base Radio 6-9 in EBTS system 6-18 BCCB 1008 8-17 1020 8-17. See BA billing in the system 2-5 Broadband Packet eXchange. 8-29 862 8-16 Billing Accumulator. See ASP AirGen 2-6. See CWM Communications Assistance for law Enforcement Act. 8-39. 8-49 Alarms for Packet Data 9-29 All Frame Relay Interconnect subsystem 7-8 Packet Data subsystem 9-5 Radio Access Network subsystem 6-7 AMC card 9-16 APD capacity 8-58 front view 8-60 functionality 8-58 hardware description 8-59 HSSI I/O board 8-59 LED board 8-60 MMI 8-61 MTX board 8-59 network management 8-61 OMC-R interface 8-61 overview 8-58 power supply 8-59 software description 8-61 ASP 11-13. See DCS Digital Trunk Controller. iDEN protocol 5-17 Domain 2-7 Fleet member ID 8-11 Frame Relay 8-7.0 05-Oct-07 . See ENET Environmental Alarm System. 8-38 EGT4 client web browser 10-22 CORBA name service 10-22 functionality 10-20 hardware description 10-21 LDAP directory server 10-22 NBI access manager 10-21 NBI connectivity 10-22 NBI notification manager 10-21 NBI object manager 10-21 network management 10-22 overview 10-20 software description 10-21 web server 10-22 ELMT 8-33. See DAP Dispatch call processing 8-11 Dispatch Messenger. See FLPP Field Replaceable Units (FRUs) 9-11 Fleet ID 8-11 Functional Description ii 6871000P02-A SR 16. SR16. 8-51 Emergency Local Maintenance Terminal.0 4-7 Fiber Link Peripheral Processor. See GPS H HA-DAP alarm on LMT login/logout 8-28 BCCB 1020 8-29 capacity 8-23 database maintenance 8-31 database query 8-31 database replication 8-31 ELMT 8-33 feature 8-26 functionality 8-23 HA services layer 8-32 hardware description 8-24 iGW-SDGC enhancement feature 8-26 LMT 8-32 LMT master iVPU 8-29 network management 8-32 NGD enhancements 8-28 OSPF 8-32 overview 8-23 remote access security 8-28 root access control 8-29 RX7620 server 8-25 software description 8-26 HA-iHLR alarm on LMT login/logout 8-49 alarm panel 8-46 backup and restore CLI 8-51 cabinet 8-47 capacity 8-45 data collection time interval 8-49 database ASCII dump 8-50 debugging data collection tool 8-49 disk arrays 8-46 ELMT 8-51 ethernet physical port status 8-48 features 8-48 functionality 8-45 hardware description 8-46 health check 8-48 LEDs 8-46 LMT 8-50 LMT master iVPU 8-50 load shedding status 8-48 network management 8-50 NGD enhancements 8-49 OCP 8-46 overview 8-45 ping and TraceRoute 8-48 provisioning transaction log file 8-52 restricted access key 8-49 RMC 8-51 root access control 8-49 E EBTS brief description 6-8 cabinets 6-11 event logs 6-20 functional description 6-10 hardware description 6-10 network management 6-19 OMC-R 6-19 overview 6-10 software description 6-19 EBTS Frame Relay to Internet Protocol.Index urban ID 8-11 Data 1-6 Data Files 9-28 Database query 8-31 Database replication 8-31 DCS 6-8 Delivery Features for Service Providers 2-4 description 5-8 Digital Cross Connect Switch. See DTC Dispatch 1-9 Dispatch Application Processor. See FRIP FRIP 8-34. See ELMT Encryption Support for Dispatch 2-5 Enhanced Base Transceiver System See EBTS enhanced frame relay channel statistics 8-40 Enhanced Global Title Translation Table Tool. See EGT4 enhanced LMT capabilities 8-40 Enhanced Network. See DM 11-14 Dispatch voice notes 11-15 Dispatch voicemail 11-15 DM 11-14 initiate a call 11-15 documents. See EAS F Feature Matrix. See eFRIP EBTS Re-rack with Dual Band RFDS 4-4 eFRIP 8-36. 8-36 FRUs (Field Replaceable Units) 9-11 G Global 2-7 Global Positioning System Denial Response 4-5 Global Positioning System. 10-14 Frame Relay to Internet Protocol. 11-8 session description protocol 3-38 session initiation protocol 3-38 software description 11-7 time synchronization 11-8 VSGW 11-6 iGW-SDGC enhancement feature 8-26 iMU and EAS 6-16 initial registration 2-4 initial SU system contact 2-4 Instant Message Text to Speech Dispatch Voice 11-15 Interactive Voice Response device. See IWF Intregrated GigaBit Exchange. See iBSC iDEN Call Processor. See iDBAD 8-50 iDEN Dispatch Access Controller. See HA Home Location Register (HLR) 7-29 Horizontal Network. See iVR Interconnect subsystem description in iDEN 1-8 Facilities Interface 7-29 I/O Blade cards 7-16 IWF 7-33 Mixed Mode configuration 7-7 MSC 7-27 Next Generation Dispatch (NGD) configurations 7-5 overview 7-5 purpose 7-4 subsystem description 7-5 Interfaces for Customer-provided Administrative Data platforms 2-5 Internet Service Provider. See HAiHLR HN 8-36. See iDAC iDEN Dispatch Access Controller. See HADAP Highly Available-iDEN Home Location Register. See ISP Interworking Function. 10-22. See HN Horizontal Networking 2-5 HSSI I/O board 8-59 system technologies 1-5 iDEN Base Site Controller.Index software description 8-48 SRM 8-51 TS20 server 8-46 TS40 AlphaServer 8-46 Highly Available-Dispatch Application Processor. See iVPUd iDEN Vocoder Processing Unit. 10-20. See iMU iDEN Surveillance Gateway. 8-38. See iGW 11-4 iDEN Monitor Unit and Environmental Alarm System. See iDAC iDEN Gateway Dispatch Roaming Registration 4-2 iDEN Gateway. 11-4 Home Agent. See iSG iDEN Vocoder Processing Unit for Dispatch and Interconnect. See emu and EAS iDEN Monitor Unit. See iCP iDEN Database ASCII Dump. See iGW iDEN Gateway. See iVPUdi iDEN Vocoder Processing Unit for Dispatch. See iGX IOS Import / Export Tool for Airgen 2-6 IP Footprint Reduction 7-21 I I/O Communications Transition board (in BA) 9-27 iBSC architecture 7-11 coverage 7-11 functional description 7-9 hardware 7-13 hardware description 7-12 in the iDEN network 7-10 links and interfaces 7-21 links and interfaces description 7-22 network management 7-23 OMC-R 7-24 overview 7-9 software description 7-22 iCP board functions 7-16 boards 7-16 components 7-13 configurations 7-23 firmware downloads 7-24 frame layout 7-14 function 7-12 I/O Blade cards 7-16 Input/Output shelf 7-15 iDAC alarm panel 8-54 capacity 8-53 CPU board 8-54 functionality 8-53 GTT-IIC ASCII 8-57 hardware description 8-54 HSSI interface module 8-54 LEDs 8-54 LMT 8-57 module 8-54 network management 8-57 OMC-R network interface 8-57 OMC-R software interface 8-57 overview 8-53 software description 8-57 iDBAD 8-50 iDEN infrastructure for the MSO 1-8 network hierarchical structure 2-9 network protocols 5-11 protocol documents 5-17 system introduction 1-3 system organization 2-7 SR 16. See iVPU iGW 3G-XCDR 11-6 3G-XCDR SAM 11-9 cabinet 11-7 call flow 3-38 CLI 11-9 EGT4 11-9 feature 11-8 functionality 11-4 hardware description 11-6 iGTN 11-6 iGTN SNMP configuration 11-9 iGW-SDGC enhancement 11-8 network communication 11-5 network management 11-9 OMC-R network interface 11-9 overview 11-4 SDGC 11-4.0 05-Oct-07 6871000P02-A Functional Description iii . Index iSC2 description 6-14 front and rear Views 6-15 iSC3 description 6-13 front panel 6-13 iSG 3-36 alarm panel 8-64 cabinet 8-65 cooling fans 8-64 CPU 8-63 DC power distribution panel 8-64 functionality 8-62 hardware description 8-63 HSC board 8-64 HSSI adapter board 8-64 LMT 8-67 network management 8-66 overview 8-62 software description 8-66 SPA 8-66 iVPU board functions 7-20 cabinet 8-37 components 7-18 components description 7-17 enhanced frame relay channel statistics 8-40 enhanced LMT capabilities 8-40 enhancements 8-39 feature 8-39 front cage 7-19 front cage boards 7-19 function 7-12 functionality 8-34 HSRP protocol 8-43 iVPUd overview 8-34 iVPUdi overview 8-35 LMT master iVPU 8-41 LMT user accounts 7-25 MMI command interface 8-42 overview 8-34 rear cage 7-20 remotely manage iVPU 8-41 Rolling Software Upgrade 7-22 rolling software upgrade 8-42 root access control 8-40 VPU SPROC/ISB LED indicators 8-40 VRRP protocol 8-43 VRRP support on iVPU 8-41 iVPUd 8-34 final NGD configuration 8-8 FRIP 8-36 hardware description 8-36 horizontal function 8-36 in Mixed Mode 8-7 iVPUdi 8-7. 8-38 Mixed Mode 8-7 MLC functional description 7-31 Functional Description iv 6871000P02-A SR 16.8-50 enhanced capabilities 8-40 functionality 8-32 master iVPU 8-41 LMT Master iVPU 8-29 Load Shedding Packet Data subsystem 9-23 Radio Access Network subsystem 6-20 Local Maintenance Terminal. See LMT Location Area 2-8 Lynx 8-32. 8-49. See MSD MDG2 9-6 boards 9-8 Encryption Compression Processor boards 9-9 event logs 9-13 front view 9-8. 8-51 M Main Serial Port Transition board 9-28 Mass Storage Device. See LDAP LMT 8-32. 8-40.0 05-Oct-07 . 9-10 hardware description 9-7 MDGio board 9-9 MDGp board 9-9 MMI commands 9-13 network management 9-11 OMC-R 9-12 overview 9-6 RAG downloads 9-13 software description 9-11 MDG4 9-14 board layout 9-18 Cluster Management/Fault Recovery 9-22 event logs 9-22 front view 9-19 hardware description 9-16 in the iDEN Network 9-15 MDGc card 9-17 MDGd card 9-17 MDGv card 9-17 MMI commands 9-21 network management 9-20 OMC-R 9-20 overview 9-14 RAG Downloads 9-22 software description 9-19 system management software 9-19 User Interface Menu 9-21 mFRIP 8-36. 8-35 FRIP 8-38 hardware description 8-37 horizontal function 8-38 in Mixed Mode 8-8 IWF 7-33 back view 7-35 front view 7-35 hardware description 7-34 network management 7-36 overview 7-33 services 7-34 software description 7-36 L LDAP 10-22 LED board 8-60 legacy BSC functional description 7-26 Lifetime Audit Registration Renewal Required 4-3 Light Weight Directory Access Protocol. 25 hub 10-16 functionality 10-13 hardware description 10-14 Informix 10-18 LAN switch 10-16 N NDM alarms and events 11-14 ASP 11-11 billing 11-14 BU admin web interface 11-16 cabinet 11-13 dispatch voice notes 11-15 dispatch voicemail 11-15 DM 11-14 functionality 11-10 hardware description 11-11 instant message text to speech dispatch voice 11-15 network connections 11-11 network management 11-14 overview 11-10 presence and availability 11-15 PTx-AS 11-11.8-73 MGX 8850 8-70. 8-74 MGX functionality 8-69 network management 8-73 overview 8-68 redundancy 8-73 SES 8-74 SES node architecture 8-72 SES PNNI 8-70 software description 8-71 MPS Frame Relay to Internet Protocol.10-7 system processor 10-5 system processor applications 10-10 typical configuration 10-4 Ultra 60 10-9. See MDG4 MPS BPX 8-69.10-10 X-terminal clients 10-10 OMC-R (Next Generation) AirGen 10-18 capacity 10-14 download queue manager 10-17 external X. See mFRIP MSC components 7-28 functionality 7-26 hardware description 7-28 in the Interconnect subsystem 7-27 monitoring center 7-30 network management 7-30 Signal Interface 7-29 software description 7-30 VLR MSD 8-13 MTX board 8-59 Multi Gigabyte Exchange. 8-72. See MGX Multiple simultaneous talk group ID 8-12 protocols. 8-72. See NGD NGD configuration 6-6 features 7-6 final implementation 8-8 Mixed Mode 8-7 Split Mode 8-7 NGD System for Interconnect 7-6 for Packet Data 9-5 NGO network infrastructure 1-7 network management 1-10 O OCP 8-46 OLCC Display and Logging 7-25 OMC Password Policy Enhancements 4-3 OMC-R BA 9-29 configuration and load management 10-11 EBTS 6-19 Enterprise 3500 10-7. See MDG2 Mobile Data Gateway 4.Index hardware description 7-31 network management 7-32 software description 7-31 MMI 8-61 Mobile 7-26 Mobile Data Gateway 2.0 05-Oct-07 6871000P02-A Functional Description v .11-12 PWI 11-16 software description 11-14 statistics 11-14 network SR 16. 8-73 BPX functionality 8-68 cabinet 8-71 Cisco WAN Manager 8-73 CLI 8-74 functionality 8-68 hardware description 8-69 links 10-5 MGX 8820 8-70. See NDM new features Network Management Features for Network Operators 2-6 Next Generation Dispatch. 10-9 event/alarm management 10-11 fault management 10-12 functionality 10-4 hardware description 10-5 iBSC 7-24 Informix 10-10 MDG2 9-12 MDG4 9-20 MMI processor 10-9 MMI processor application 10-10 NE software loads 10-10 Netra 20 10-9.10-10 Netra 240 10-16 network management 10-11 OML 10-5 overview 10-4 performance management 10-11 redundancy 10-12 SDM/FT 7-39 security management 10-12 short description 10-10 SNMP 10-5 Sun Fire 4800 10-5. iDEN 5-11 Network Dispatch Messenger. See OSPF Operations and Maintenance Center. See OCP OSPF 8-32 Over-the-Air-Programming 2-4 Mixed Mode configuration 6-6 MMI commands 6-19 NGD configurations 6-5 NGD Mixed Mode configuration 6-7 overview 6-4 purpose 6-3 radio link functionality 6-8 status indicators 6-19 Radio Frequency Cabinet 6-12 Radio Frequency Distribution System (RFDS) 6-9 Radio Protocol 7-34 Region 2-7 Remote access security 8-28 Remote Management Console. See SDM/FT R Radio Access Network subsystem architecture 6-5 description 6-4 EBTS overview 6-10 general call functionality 6-7 iMU and EAS 6-16 key network elements 6-8 Functional Description vi 6871000P02-A SR 16. See OMC-R Operations and Maintenance Links.0 components diagram 1-8 SNMP 10-5 Spectrum Peripheral Module Enclosure.Index LDM download manager 10-17 Netra 240 backup server 10-16 Netra 440 10-13. See SMS Signaling Transfer Point.0 05-Oct-07 . See SPME Split Mode 8-7 Interconnect subsystem 7-8 Radio AccessNetwork subsystem 6-7 RSL card Configuration 7-17 Split Mode Configuration Interconnect subsystem 7-8 SSC 8-13 Standard System Controller. See STP Simple Network ManagementProtocol. See SRM Short Message Service. See SDGC Service Area 2-8 Service Resource Module. See PD PCI Mezzanine card 9-9 PDR Warning 7-25 Performance Management 2-6 police monitoring 5-6 Power Converter Module 9-26 Power supply 8-59 Power Supply Modules 9-10 Presence and availability 11-15 Private Call on 900 MHz (PC) 4-2 Processor Switching Module. 11-8 configuration changes 11-8 SDM//FT MMI commands 7-39 SDM/FT functional description 7-37 hardware description 7-38 monitored events 7-38 network management 7-39 OMC-R 7-39 overview 7-37 software description 7-39 Selective Dispatch Group Call. See SNMP simplified SR15. See PTx-AS PWI 11-16 PXM 10-23 S SCSI hard drive 9-27 SDGC 8-16. 3-36 Provisioning Web Interface. See PWI PTx-AS 11-11. See OML Operator Control Panel.11-12 Push-to-Talk Application Server. See RMC Remotely manage iVPU 8-41 Retuning Management Application (RMA) 4-4 RF Distribution System. 11-4.10-15 network management 10-19 Network Views 10-19 NTS 10-16 overview 10-13 software description 10-17 StorEdge 3510 disk array 10-16 SunRay X-terminal 10-16 OMC-R (Operations and Maintenance Center) 5-8 OML 10-5 On-Line Configuration Change 2-6 Online Configuration Change 7-25 Open Shortest Path First. See PXM protocol documents 5-17 iDEN network 5-11 Protocols 3-17. See SSC subscriber databases 2-5 subscriber services 1-4 Supernode Data Manager / Fault Tolerant. See RFDS RFDS 6-16 Cavity Combining RFDS 6-17 Duplex RFDS 6-17 RFDS (Radio Frequency Distribution System) 6-9 RMC 8-45. 8-51 Rolling software upgrade 8-42 Root access control 8-29 routing of voice 8-53 RSL Configurations 7-17 RX7620 server 8-25 back panel 8-26 front panel 8-25 P Packet Data 1-9 overview 9-4 Packet Data subsystem description 9-4 Ethernet board 9-26 Ethernet Port Connector board 9-27 indicators and controls 9-12 Input Power Switch 9-12 Input Power Transition board 9-28 IP Switch Board cards 9-16 NGD configurations 9-5 purpose 9-3 Packet Data subsystem indicators 9-12 Packet Data. See VSGW VRRP 8-43 VRRP support on iVPU 8-41 VSGW 8-16.11-5 billing 11-7 W wireless telephony 1-5 X XCIPIO 5-6 SR 16. See VLR VLR 7-29 mirroring 9-22 Voice and Signaling Gateway. 8-26.0 05-Oct-07 6871000P02-A Functional Description vii .Index SuperNode Data Manager/Fault Tolerant. 11-4. See VRRP Visiting Home Location Register. See SDM/FT Switch Matrix 7-28 system introduction 2-3 T Talk group ID 8-11 TS40 AlphaServer 8-46 Two-way Dispatch Radio 1-5 U Urban ID 8-11 urbans 2-8 user interface menu 9-21 V Virtual Router Redundancy Protocol 7-25 Virtual Router Redundancy Protocol. 0 05-Oct-07 .Index Functional Description viii 6871000P02-A SR 16. Inc. Patent and Trademark Office. All other product or service names are the property of their respective owners. 2007 6871000P02-A .MOTOROLA and the Stylized M logo are registered in the U.S. © Motorola.