Motorola TETRA Infrastructure Technical Documentation Library Dimetra IPCompact8.1 System Overview DIPC

System Release 8.1

DIMETRA™ DIMETRA IP COMPACT (DIPC)/SCALABLE DIMETRA IP (SDIP)

SYSTEM OVERVIEW

October 2013

68015000701-C

© 2013 Motorola Solutions, Inc. All rights reserved

Copyrights The Motorola products described in this document may include copyrighted Motorola computer programs. Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyrighted computer programs. Accordingly, any copyrighted Motorola computer programs contained in the Motorola products described in this document may not be copied or reproduced in any manner without the express written permission of Motorola. © 2013 Motorola Solutions, Inc. All Rights Reserved No part of this document may be reproduced, transmitted, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without the prior written permission of Motorola Solutions, Inc. 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, except for the normal non-exclusive, royalty-free license to use that arises by operation of law in the sale of a product.

Disclaimer Please note that certain features, facilities, and capabilities described in this document may not be applicable to or licensed for use on a particular system, or may be dependent upon the characteristics of a particular mobile subscriber unit or configuration of certain parameters. Please refer to your Motorola contact for further information.

Trademarks MOTOROLA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC and are used under license. All other trademarks are the property of their respective owners.

European Union (EU) Waste of Electrical and Electronic Equipment (WEEE) directive

The European Union's WEEE directive requires that products sold into EU countries must have the crossed out trash bin label on the product (or the package in some cases). As defined by the WEEE directive, this cross-out trash bin label means that customers and end-users in EU countries should not dispose of electronic and electrical equipment or accessories in household waste. Customers or end-users in EU countries should contact their local equipment supplier representative or service centre for information about the waste collection system in their country.

i

CMM Labeling and Disclosure Table The People’s Republic of China requires that our 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. The first of the following examples means that the product contains no hazardous substances; the second means that the product contains hazardous substances, and has an Environmental Friendly Use Period (EFUP) of fifty years.

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 Disclosure Table, printed in simplified Chinese, is included with each customer order. An example of a Disclosure Table (in Chinese) follows:

iii

Service Information Government Technical Support, EA Solutions Support Centre (ESSC) The Government Technical Support, EA Solutions Support Centre (ESSC) provides a remote Technical Support Service to help customers resolve technical issues and quickly restore networks and systems. This team of highly skilled professionals is available to customers with current service agreements in place that include the Technical Support Service. The ESSC technical experts may be accessed through the EMEA Integrated Call Center either electronically or using the telephone numbers listed below. If you are unsure whether your current service agreement entitles you to benefit from this service, or if you would like more information about the Technical Support Service, contact your local customer support or account manager for further information.

Contact Details Email: [email protected] List of Telephone Numbers Country

In Country Number to Dial

AUSTRIA

01206091087

DENMARK

043682114

FRANCE

0157323434

GERMANY

06950070204

ITALY

0291483230

LITHUANIA

880 030 828

NETHERLANDS

0202061404

NORWAY

24159815

PORTUGAL

0217616160

RUSSIA

810 800 228 41044 (Alternative 810 800 120 1011)

SAUDI ARABIA

800 844 5345

SOUTH AFRICA

0800981900

SPAIN

0912754787

UNITED KINGDOM

02030 277499

All Other Countries

+44 2030 277499

European Systems Component Centre (ESCC) The European Systems Component Centre provides a repair service for infrastructure equipment. Customers requiring repair service should contact the Customer Information Desk to obtain a Return Material Authorization number. The equipment should then be shipped to the following address unless advised otherwise. Motorola GmbH, European Systems Component Centre, Am Borsigturm 130,13507 Berlin, Germany

v

System Overview

Contact Details • E-Mail: [email protected] • Telephone: +49 (0) 30 66861404 • Telefax: +49 (0) 30 66861426 • Monday – Friday 08:00 am to 06:00 pm (CET)

Parts Identification and Ordering Request for help in identification of non-referenced spare parts should be directed to the Customer Care Organization of Motorola’s local area representation. Orders for replacement parts, kits, and assemblies should be placed directly on Motorola’s local distribution organization or through the Extranet site Motorola Online at https://emeaonline.motorolasolutions.com.

Your Input If you have any comments, corrections, suggestions, ideas for this publication or any other requirements regarding Motorola publications, send an e-mail to [email protected].

Updated Versions of this Manual Verify the current version of the manual at our Extranet site, Motorola Online. Contact us at [email protected] for access.

vi

Document History Edition

Description

Date

68015000701-A

Initial Version

February 2013

68015000701-B

Updated graphics/diagrams. Fixed VPN Gateway model name.

March 2013

68015000701-C

Updated with changes connected with the introduction of HP rp5800

October 2013

vii

Contents 1

Radio System Concepts............................................................................................................................... 1-1 1.1 What is a Radio System?.................................................................................................................... 1-1 1.1.1 Basic System Components ........................................................................................................ 1-1 1.1.1.1 Radio System Equipment ................................................................................................... 1-1 1.1.1.2 Radio System Range.......................................................................................................... 1-2 1.1.2 Communication Types .............................................................................................................. 1-2 1.1.2.1 Simplex .......................................................................................................................... 1-3 1.1.2.2 Semi-Duplex.................................................................................................................... 1-3 1.1.2.3 Duplex............................................................................................................................ 1-4 1.1.3 Call Types .............................................................................................................................. 1-4 1.1.3.1 Talkgroup Calls ................................................................................................................ 1-4 1.1.3.2 Multigroup Calls............................................................................................................... 1-4 1.1.3.3 Object Calls ..................................................................................................................... 1-4 1.1.3.4 Announcement Calls ......................................................................................................... 1-5 1.1.3.5 Emergency Calls............................................................................................................... 1-5 1.1.3.6 Ruthless Preemption.......................................................................................................... 1-5 1.1.3.7 Direct Mode Operation Calls............................................................................................... 1-5 1.1.3.8 Site Wide Calls................................................................................................................. 1-5 1.1.3.9 Private Calls .................................................................................................................... 1-6 1.1.3.10 Telephone Interconnect Calls............................................................................................. 1-6 1.1.4 Types of Communication Channels ............................................................................................. 1-6 1.1.4.1 Control Channel (CC) ........................................................................................................ 1-6 1.1.4.2 Traffic Channel (TCH) ....................................................................................................... 1-6 1.1.5 Basic Site Components ............................................................................................................. 1-7 1.1.5.1 Site Controller (SC)........................................................................................................... 1-7 1.1.5.2 Base Radio (BR)............................................................................................................... 1-7 1.1.6 Radios ................................................................................................................................... 1-8 1.1.7 Call Processing Basics.............................................................................................................. 1-8 1.1.7.1 Trunked and Conventional Radio Systems ............................................................................. 1-9 1.1.7.1.1 Trunked System Operation ........................................................................................ 1-9 1.1.7.1.2 Conventional System Operation................................................................................ 1-10 1.1.7.2 Radio System Users ........................................................................................................ 1-11 1.1.7.2.1 Radio Users .......................................................................................................... 1-11 1.1.7.2.2 Talkgroups ........................................................................................................... 1-11 1.1.7.2.3 Multigroups .......................................................................................................... 1-12 1.1.8 Tracing a Basic Call ............................................................................................................... 1-13 1.2 Multiple Site Trunked Systems .......................................................................................................... 1-15 1.2.1 RF Sites............................................................................................................................... 1-16 1.2.2 Zone ................................................................................................................................... 1-17 1.2.3 Mobile Switching Office (MSO)............................................................................................... 1-17 1.3 Multizone Systems.......................................................................................................................... 1-18 1.3.1 Conditions for Multizone Communication .................................................................................. 1-19 1.3.1.1 Home Zone Mapping....................................................................................................... 1-19 1.3.1.2 Controlling Zone ............................................................................................................ 1-20 1.3.1.3 Participating Zone........................................................................................................... 1-20 1.3.2 Modes of Operation ............................................................................................................... 1-20 1.3.2.1 Wide Area Trunking with Interzone Trunking....................................................................... 1-21 1.3.2.2 Fall Back Modes............................................................................................................. 1-21 1.3.2.2.1 Zone Isolated Wide Area Trunking............................................................................ 1-21 1.3.2.2.2 Local Site Trunking................................................................................................ 1-22 1.3.2.2.3 Direct Mode Operation (DMO) ................................................................................ 1-22 1.3.3 Interzone Group Service Availability ......................................................................................... 1-22

ix

System Overview

1.3.4

2

3

x

Where Calls Occur................................................................................................................. 1-22 1.3.4.1 Single Site ..................................................................................................................... 1-22 1.3.4.2 Zone............................................................................................................................. 1-22 1.3.4.3 Multizones .................................................................................................................... 1-22 Dimetra IP System Technology..................................................................................................................... 2-1 2.1 Terrestrial Trunked Radio (TETRA) ..................................................................................................... 2-1 2.1.1 Spectrum Management ............................................................................................................. 2-2 2.1.2 Pi/4-DQPSK Modulation .......................................................................................................... 2-2 2.1.3 ACELP Voice Compression....................................................................................................... 2-3 2.1.4 Time Division Multiple Access .................................................................................................. 2-4 2.1.4.1 TDMA for Dimetra IP Base Stations..................................................................................... 2-4 2.1.4.2 TDMA for Dimetra IP Radios ............................................................................................. 2-5 2.2 Network Technology ......................................................................................................................... 2-5 2.2.1 Local Area Network................................................................................................................. 2-5 2.2.1.1 Ethernet Technology.......................................................................................................... 2-5 2.2.1.2 Star Topology................................................................................................................... 2-6 2.2.1.3 10Base-T and 100Base-T ................................................................................................... 2-6 2.2.1.4 Virtual LANs ................................................................................................................... 2-6 2.2.1.5 Switched Ethernet ............................................................................................................. 2-7 2.2.2 Wide Area Network ................................................................................................................. 2-7 2.2.2.1 E1 Carrier........................................................................................................................ 2-8 2.2.2.2 X.21 Link........................................................................................................................ 2-8 2.2.2.3 Frame Relay .................................................................................................................... 2-9 2.2.3 Cooperative WAN Routing (CWR) ............................................................................................ 2-9 2.2.4 Ethernet Site Links ................................................................................................................ 2-10 2.3 Digital Motorola Enhanced Trunked Radio (Dimetra) ............................................................................ 2-12 2.3.1 Dimetra IP System Components ............................................................................................... 2-12 2.3.2 Dimetra IP System Core ......................................................................................................... 2-12 2.3.3 Unicast Routing .................................................................................................................... 2-13 2.3.4 Multicast Routing .................................................................................................................. 2-13 2.3.5 Call Model ........................................................................................................................... 2-14 2.3.6 Traffic Planes........................................................................................................................ 2-16 2.3.6.1 Voice Control Plane......................................................................................................... 2-17 2.3.6.2 Audio Plane ................................................................................................................... 2-17 2.3.6.3 Data Plane ..................................................................................................................... 2-17 2.3.6.4 Network Management Plane ............................................................................................. 2-17 2.4 End-to-End Secure Communication.................................................................................................... 2-18 Dimetra IP System Components ................................................................................................................... 3-1 3.1 Mobile Switching Office (MSO) .......................................................................................................... 3-1 3.1.1 System Server......................................................................................................................... 3-1 3.1.1.1 Types of the System Server ................................................................................................. 3-2 3.1.2 Zone Controller....................................................................................................................... 3-2 3.1.3 Network Management Subsystem ............................................................................................... 3-3 3.1.3.1 Network Management Servers............................................................................................. 3-4 3.1.3.2 Operations Support Systems................................................................................................ 3-5 3.1.3.2.1 Fault Management at the Zone Level ........................................................................... 3-5 3.1.3.2.2 Configuration Management at the Zone Level ............................................................... 3-5 3.1.3.2.3 Security Management at the Zone Level....................................................................... 3-5 3.1.3.2.4 Network Management at the Cluster OSS ..................................................................... 3-6 3.1.3.2.5 Fault Management at the Cluster OSS.......................................................................... 3-6 3.1.3.2.6 Configuration Management at the Cluster OSS ............................................................. 3-6 3.1.3.2.7 Security Management at the Zone and Cluster OSS ........................................................ 3-6 3.1.3.2.8 Multicluster Network Management ............................................................................. 3-6 3.1.4 Data Subsystem....................................................................................................................... 3-7 3.1.4.1 Data Gateway................................................................................................................... 3-7

Document History

4

3.1.4.1.1 Packet Data Router (PDR) ......................................................................................... 3-7 3.1.4.1.2 Radio Network Gateway (RNG) ................................................................................. 3-7 3.1.4.1.3 Short Data Router (SDR)........................................................................................... 3-7 3.1.5 Telephone Interconnect Subsystem.............................................................................................. 3-8 3.1.5.1 Motorola Telephone Interconnect Gateway ............................................................................ 3-9 3.1.5.2 Echo Canceller ................................................................................................................. 3-9 3.1.5.3 Enhanced Telephone Gateway (ETG) ................................................................................... 3-9 3.1.6 Provisioning and Authentication Centre ....................................................................................... 3-9 3.1.6.1 Provisioning Centre (PrC) .................................................................................................. 3-9 3.1.6.2 Clear Provisioning Centre (Clear PrC) ................................................................................ 3-10 3.1.6.3 Authentication Centre (AuC)............................................................................................. 3-10 3.1.7 Network Time Server (NTS) .................................................................................................... 3-10 3.2 Network Transport Subsystem........................................................................................................... 3-11 3.2.1 Switches .............................................................................................................................. 3-13 3.2.1.1 Core LAN Switch ........................................................................................................... 3-13 3.2.1.2 Backhaul Switch............................................................................................................. 3-14 3.2.2 Routers................................................................................................................................ 3-14 3.2.2.1 Gateway GPRS Support Node ........................................................................................... 3-14 3.2.3 CWR Patch Panel .................................................................................................................. 3-14 3.3 Remote Sites.................................................................................................................................. 3-15 3.3.1 Base Transceiver Station (BTS)................................................................................................ 3-15 3.3.1.1 MTS LiTE..................................................................................................................... 3-16 3.3.1.2 MTS 1 .......................................................................................................................... 3-16 3.3.1.3 MTS 2 .......................................................................................................................... 3-17 3.3.1.4 MTS 4 .......................................................................................................................... 3-18 3.3.1.5 Redundant Base Station Site Link ...................................................................................... 3-19 3.3.1.6 Site Controller (SC)......................................................................................................... 3-19 3.3.1.7 Base Radio .................................................................................................................... 3-20 3.3.1.8 Breaker Panel................................................................................................................. 3-21 3.3.2 Control Sites......................................................................................................................... 3-21 3.3.2.1 Dispatch Subsystem ........................................................................................................ 3-22 3.3.2.1.1 Dispatch Console PC.............................................................................................. 3-24 3.3.2.1.2 Equipment connected to the Dispatch Console PC........................................................ 3-24 Desktop Speakers ........................................................................................................ 3-24 Desk Microphone ........................................................................................................ 3-24 Footswitch ................................................................................................................. 3-24 Emergency Beacon ...................................................................................................... 3-24 3.3.2.1.3 Logging System .................................................................................................... 3-25 MCC 7500 Archiving Interface Server............................................................................. 3-26 Logging Recorder........................................................................................................ 3-26 Replay Station ............................................................................................................ 3-26 3.3.2.1.4 Conventional Channel Gateway (CCGW)................................................................... 3-27 3.3.2.1.5 Secure Dispatch System (End-to-End Encryption (E2EE)) ............................................. 3-28 End-2-End Encryption (E2EE) Call Logging..................................................................... 3-28 E2EE Call Logging Servers .................................................................................... 3-28 3.4 Radios .......................................................................................................................................... 3-29 3.4.1 MTP3000 Series Overview...................................................................................................... 3-29 3.4.2 MTH800 Overview................................................................................................................ 3-31 3.4.3 MTP850 S/MTP850 FuG Overview .......................................................................................... 3-32 3.4.4 MTP830 S/MTP830 FuG Overview .......................................................................................... 3-33 3.4.5 MTP850 Ex/MTP810 Ex Overview .......................................................................................... 3-34 3.4.6 TCR1000 Overview ............................................................................................................... 3-36 3.4.7 MTM800 Enhanced Overview ................................................................................................. 3-36 3.4.8 MTM5x00MTM800 FuG/MTM800 FuG ET Overview ................................................................ 3-37 Dimetra IP Data Management ...................................................................................................................... 4-1

xi

System Overview

4.1

5

xii

Radio System Databases .................................................................................................................... 4-1 4.1.1 Call Processing Information....................................................................................................... 4-1 4.1.1.1 User Configuration Server Database ..................................................................................... 4-1 4.1.1.2 Zone Database Server ........................................................................................................ 4-2 4.1.1.3 Home Location Register..................................................................................................... 4-2 4.1.1.4 Visitor Location Register.................................................................................................... 4-2 4.1.1.5 Zone Local Database ......................................................................................................... 4-2 4.1.1.6 Radio Control Manager (RCM) Database .............................................................................. 4-2 4.1.1.7 Affiliation Database........................................................................................................... 4-2 4.1.1.8 Radio User Information...................................................................................................... 4-3 4.1.2 Fault Management Information .................................................................................................. 4-3 4.1.3 Statistical Data ........................................................................................................................ 4-3 4.1.3.1 Zone Statistics Server Database ........................................................................................... 4-3 4.1.4 Database Summary .................................................................................................................. 4-3 4.1.5 Hierarchical View .................................................................................................................... 4-4 4.1.6 Server Interaction .................................................................................................................... 4-5 Dimetra IP Call Processing .......................................................................................................................... 5-1 5.1 Configuration Information .................................................................................................................. 5-1 5.1.1 Static User Configuration .......................................................................................................... 5-1 5.1.1.1 Default Records................................................................................................................ 5-2 5.1.1.2 Identification Numbers....................................................................................................... 5-3 5.1.1.2.1 Programming ID Numbers......................................................................................... 5-3 5.1.1.3 Home Zones .................................................................................................................... 5-3 5.1.1.4 Radio Identification ........................................................................................................... 5-4 5.1.1.5 Radio User ...................................................................................................................... 5-5 5.1.1.6 Profiles ........................................................................................................................... 5-5 5.1.1.6.1 Radio User Capabilities Profile................................................................................... 5-5 5.1.1.6.2 Radio User Valid Sites Profile .................................................................................... 5-6 5.1.1.6.3 Radio User Interconnect Profile .................................................................................. 5-6 5.1.1.7 Templates ........................................................................................................................ 5-6 5.1.1.8 Configuration Updates ....................................................................................................... 5-6 5.1.1.9 Talkgroup ........................................................................................................................ 5-6 5.1.1.9.1 TG/MG Capabilities Profile ....................................................................................... 5-7 5.1.1.10 Object Group.................................................................................................................. 5-7 5.1.1.11 Barring of Incoming/Outgoing Calls ................................................................................... 5-7 5.1.1.12 Multigroup..................................................................................................................... 5-7 5.1.1.12.1 TG/MG Valid Sites Profile ....................................................................................... 5-7 5.1.2 Infrastructure Configuration....................................................................................................... 5-7 5.1.2.1 Source Site Adjacent Control Channel .................................................................................. 5-8 5.2 Mobility Management ....................................................................................................................... 5-8 5.2.1 Mobility as Viewed by the Radio ................................................................................................ 5-9 5.2.2 Mobility as Viewed by the Fixed Network Equipment .................................................................... 5-9 5.2.3 How the Location Registers are Created....................................................................................... 5-9 5.3 Call Processing .............................................................................................................................. 5-11 5.3.1 Call Types ............................................................................................................................ 5-11 5.4 Group-Based Services ..................................................................................................................... 5-11 5.4.1 Talkgroup Call ...................................................................................................................... 5-12 5.4.1.1 Intrazone Talkgroup Call .................................................................................................. 5-12 5.4.1.1.1 Call Request ......................................................................................................... 5-12 5.4.1.1.2 Call Setup ............................................................................................................ 5-13 5.4.1.1.3 Call Grant ............................................................................................................ 5-14 5.4.1.1.4 Intrazone Talkgroup Call Audio Routing .................................................................... 5-14 5.4.1.1.5 Talkgroup Call Continuation and Teardown ................................................................ 5-15 5.4.1.2 Interzone Talkgroup Call .................................................................................................. 5-15 5.4.1.2.1 Interzone Talkgroup Call Request ............................................................................. 5-16

Document History

5.5

5.6 5.7

5.8

5.4.1.2.2 Interzone Talkgroup Call Setup ................................................................................ 5-16 5.4.1.2.3 Interzone Talkgroup Call Audio Routing .................................................................... 5-17 5.4.1.2.4 Interzone Talkgroup Call Continuation and Teardown ................................................... 5-17 5.4.1.2.5 Roaming During a Talkgroup Call............................................................................. 5-17 5.4.2 Object Call ........................................................................................................................... 5-18 5.4.3 Announcement Call ............................................................................................................... 5-18 5.4.3.1 Multi-Select (MSEL) and Patch Calls ................................................................................. 5-19 5.4.4 Emergency Services ............................................................................................................... 5-19 5.4.4.1 Emergency Alarm ........................................................................................................... 5-19 5.4.4.2 Emergency Call .............................................................................................................. 5-19 5.4.5 Site Wide Calls ..................................................................................................................... 5-20 5.4.6 Talkgroup Scanning ............................................................................................................... 5-20 Individual Call Services ................................................................................................................... 5-21 5.5.1 Private Call Request............................................................................................................... 5-21 5.5.1.1 Private Call Request Flow ................................................................................................ 5-21 5.5.1.2 Intrazone Private Call Audio Flow, Call Continuation, and Teardown........................................ 5-22 5.5.1.3 Roaming During a Private Call .......................................................................................... 5-23 5.5.1.4 Full-Duplex Private Calls ................................................................................................. 5-23 5.5.2 Telephone Interconnect........................................................................................................... 5-23 5.5.2.1 Relationship between Components ..................................................................................... 5-24 5.5.2.2 Configuration ................................................................................................................. 5-25 5.5.2.2.1 Limiting Access to Interconnection Services ............................................................... 5-25 Limiting Interconnect Calls Through Radio and User Configuration ...................................... 5-25 Individual Interconnect Profiles ............................................................................... 5-25 Limiting Interconnect through Infrastructure Configuration ................................................. 5-25 Enabling or Disabling Interconnect Based on Shared Service ........................................ 5-25 Limiting Interconnect Call Duration at the Zone Level ................................................. 5-25 5.5.2.2.2 Call Setup Restrictions............................................................................................ 5-26 5.5.2.2.3 Radio-to-Landline Interconnect Calls......................................................................... 5-26 Call Setup .................................................................................................................. 5-26 5.5.2.2.4 Landline-to-Radio Interconnect Calls......................................................................... 5-27 5.5.2.3 Telephone Interconnect Call Continuation/Call Maintenance ................................................... 5-27 5.5.2.4 Telephone Interconnect Call Termination and Call Teardown................................................... 5-28 5.5.2.4.1 Radio-Initiated Termination During Active Interconnect Call ......................................... 5-28 5.5.2.4.2 Landline Initiated Termination During Active Interconnect Call...................................... 5-28 5.5.2.4.3 System Initiated Interconnect Call Termination............................................................ 5-28 5.5.2.5 Roaming During a Telephone Interconnect Call .................................................................... 5-28 5.5.2.5.1 Roaming During an Active Interconnect Call .............................................................. 5-28 5.5.2.5.2 Roaming during queuing of Telephone Interconnect Call............................................... 5-29 5.5.2.5.3 Roaming While Ringing for Landline-to-Radio Call ..................................................... 5-29 Short Data Services ......................................................................................................................... 5-29 5.6.1 Short Data Store and Forward .................................................................................................. 5-30 5.6.2 SDS in Local Site Trunking ..................................................................................................... 5-30 Authentication and Air Interface Encryption ........................................................................................ 5-30 5.7.1 Authentication ...................................................................................................................... 5-31 5.7.2 Air Interface Encryption ......................................................................................................... 5-31 5.7.2.1 Security Classes.............................................................................................................. 5-32 5.7.2.1.1 Security Class 1(SC1)............................................................................................. 5-33 5.7.2.1.2 Security Class 2 (SC2) ............................................................................................ 5-33 Encryption with the Static Cipher Key (SCK) ................................................................... 5-33 5.7.2.1.3 Security Class 3 (SC3) ............................................................................................ 5-33 Encryption with the Derived Cipher Key (DCK)................................................................ 5-33 Encryption with the Common Cipher Key (CCK) .............................................................. 5-33 5.7.2.1.4 Security Class 3G (SC3G) ....................................................................................... 5-34 Busy Call Handling ......................................................................................................................... 5-34

xiii

System Overview

5.8.1 5.8.2

6

Priority Levels ...................................................................................................................... 5-34 Group Call Busies.................................................................................................................. 5-34 5.8.2.1 AllStart ......................................................................................................................... 5-34 5.8.2.2 FastStart........................................................................................................................ 5-35 5.8.3 Private Call Busies................................................................................................................. 5-35 5.8.4 Typical Reasons for Rejects ..................................................................................................... 5-35 5.9 Effects of Loss of Service on Call Processing ....................................................................................... 5-36 5.9.1 Loss of Service within a Zone .................................................................................................. 5-36 5.9.2 Conditions Necessary for Interzone Trunking.............................................................................. 5-37 5.9.2.1 Interzone Group Service Availability .................................................................................. 5-37 5.9.2.1.1 Example 1 ............................................................................................................ 5-38 5.9.2.2 Interzone Individual Service Availability ............................................................................. 5-38 5.9.2.2.1 Conditions for Interzone Unit to Unit Calls ................................................................. 5-39 5.9.2.2.2 Example 1 ............................................................................................................ 5-39 5.9.2.2.3 Example 2 ............................................................................................................ 5-39 5.10 Interference Detection.................................................................................................................... 5-40 5.11 Zone Controller Switchover in Redundant Configuration ...................................................................... 5-41 5.11.1 Automatic Switchover........................................................................................................... 5-41 5.11.2 User-Initiated Switchover ...................................................................................................... 5-42 5.11.3 System Behavior During Automatic Switchover......................................................................... 5-42 5.11.3.1 Possible Call Processing Behavior During Recovery ............................................................ 5-43 5.11.3.1.1 Radio Scatter....................................................................................................... 5-43 5.11.3.2 Switching Back to the Standby Controller (User Initiated)..................................................... 5-44 5.11.3.2.1 Infrastructure Database Download ........................................................................... 5-44 Dimetra IP System Features ......................................................................................................................... 6-1 6.1 Voice Services.................................................................................................................................. 6-1 6.1.1 Group Call ............................................................................................................................. 6-1 6.1.2 Announcement Call ................................................................................................................. 6-1 6.1.3 Emergency Call....................................................................................................................... 6-1 6.1.4 Individual Call (Semi-Duplex or Full-Duplex)............................................................................... 6-1 6.1.5 Telephone Interconnect Call ...................................................................................................... 6-2 6.2 Data Services ................................................................................................................................... 6-2 6.2.1 Status Transfer Service ............................................................................................................. 6-2 6.2.2 Emergency Alarm.................................................................................................................... 6-2 6.2.3 Short Data Transport Service ..................................................................................................... 6-3 6.2.4 Alphanumeric Text Service........................................................................................................ 6-3 6.2.5 Packet Data Service ................................................................................................................. 6-4 6.2.6 Data Resilience ....................................................................................................................... 6-4 6.3 Supplementary Services ..................................................................................................................... 6-4 6.3.1 Busy Queuing and Call Back ..................................................................................................... 6-4 6.3.2 Queuing Priority...................................................................................................................... 6-4 6.3.3 Call Out................................................................................................................................. 6-5 6.3.4 Recent User Priority................................................................................................................. 6-5 6.3.5 Dynamic Site Assignment ......................................................................................................... 6-5 6.3.6 All Start/Fast Start ................................................................................................................... 6-5 6.3.7 Critical Site Assignment ........................................................................................................... 6-6 6.3.8 Talking Party Identification........................................................................................................ 6-6 6.3.9 Calling Line Identification Presentation ....................................................................................... 6-6 6.3.10 Dual Tone Multi-Frequency Overdial......................................................................................... 6-6 6.3.11 Late Entry ............................................................................................................................ 6-6 6.3.12 Priority Monitor..................................................................................................................... 6-6 6.3.13 Preemptive Priority Call .......................................................................................................... 6-7 6.3.14 Preemptive Priority Call - Busy User Preemption ......................................................................... 6-7 6.3.15 Site Wide Call ....................................................................................................................... 6-7 6.3.16 Barring of Incoming/Outgoing Calls .......................................................................................... 6-7

xiv

Document History

7

6.3.17 Telephony – BIC/BOC............................................................................................................ 6-8 6.3.18 Requested Sites ..................................................................................................................... 6-8 6.3.19 Control Channel Immunity ...................................................................................................... 6-8 6.3.20 Energy Economy Mode........................................................................................................... 6-8 6.3.21 SDR Audit Logging ............................................................................................................... 6-9 6.4 Call Logging features ........................................................................................................................ 6-9 6.4.1 Central Voice Logging .............................................................................................................. 6-9 6.5 Redundancy of Critical Components..................................................................................................... 6-9 6.6 Local Gateway Trunking .................................................................................................................. 6-10 6.7 Mobility Features............................................................................................................................ 6-11 6.7.1 Extended Range .................................................................................................................... 6-11 6.7.2 Subscriber Class .................................................................................................................... 6-11 6.7.3 Valid Sites............................................................................................................................ 6-11 6.7.4 Common Secondary Control Channel ........................................................................................ 6-11 6.8 Console Operator Features................................................................................................................ 6-11 6.8.1 Assignable Talkgroups............................................................................................................ 6-12 6.8.2 Assignable Speakers and Audio Summing .................................................................................. 6-12 6.8.3 Repeat Disable ...................................................................................................................... 6-12 6.8.4 Temporary Disable................................................................................................................. 6-12 6.8.5 Permanent Disable ................................................................................................................. 6-12 6.8.6 Trunking System Status .......................................................................................................... 6-13 6.8.7 Console Priority .................................................................................................................... 6-13 6.8.8 Status Message Display .......................................................................................................... 6-13 6.8.9 All Mute .............................................................................................................................. 6-13 6.8.10 Instant Transmit................................................................................................................... 6-13 6.8.11 Safety Switch ...................................................................................................................... 6-14 6.8.12 Intelligent Call Indicator........................................................................................................ 6-14 6.8.13 Supervisory Console User...................................................................................................... 6-14 6.8.14 Console Multi-Select ............................................................................................................ 6-14 6.8.15 All Points Bulletin Transmission............................................................................................. 6-14 6.8.16 Console Patch ..................................................................................................................... 6-14 6.8.17 Conventional Channel Patch .................................................................................................. 6-15 6.8.18 Console Acoustic Cross-Mute ................................................................................................ 6-15 6.8.19 Ambience Listening ............................................................................................................. 6-15 6.9 Console Management Features ......................................................................................................... 6-15 6.9.1 Elite Admin Application ......................................................................................................... 6-15 6.10 Dimetra Enhanced Software Update ................................................................................................. 6-16 6.10.1 Upgrade Server ................................................................................................................... 6-16 6.10.2 Upgrade Console ................................................................................................................. 6-16 6.11 Version Coexistence ...................................................................................................................... 6-16 Dimetra IP Network Management ................................................................................................................. 7-1 7.1 System Management Objectives and Framework .................................................................................... 7-1 7.2 Serviceability................................................................................................................................... 7-2 7.2.1 Remote Serviceability of the MSO .............................................................................................. 7-2 7.3 Network Management System ............................................................................................................ 7-2 7.3.1 Client/Server Networking.......................................................................................................... 7-3 7.3.1.1 Windows-Based Clients ..................................................................................................... 7-3 7.3.1.2 NM Client Applications ..................................................................................................... 7-3 7.3.1.2.1 Cluster-Level Applications ........................................................................................ 7-3 7.3.1.2.2 Zone-Level Applications ........................................................................................... 7-3 7.3.1.3 Network Management System Servers .................................................................................. 7-4 7.3.1.3.1 NM Zone-Level Servers (One Each Per Zone)............................................................... 7-4 7.3.1.3.2 Cluster-Level Servers (One Each Per System) ............................................................... 7-4 7.3.1.4 Zone-Level Servers ........................................................................................................... 7-5 7.3.1.4.1 Air Traffic Router .................................................................................................... 7-5

xv

System Overview

7.3.1.4.2 Zone Database Server ............................................................................................... 7-5 7.3.1.4.3 Unified Event Manager Server.................................................................................... 7-5 7.3.1.4.4 Zone Statistics Server ............................................................................................... 7-5 7.3.1.5 Cluster-Level Servers ........................................................................................................ 7-5 7.3.1.5.1 User Configuration Server ......................................................................................... 7-6 7.3.2 Core Services.......................................................................................................................... 7-6 7.4 FCAPS Model in the Dimetra IP System ............................................................................................... 7-6 7.4.1 Fault Management ................................................................................................................... 7-7 7.4.2 Configuration Management ....................................................................................................... 7-7 7.4.2.1 Configuration Management Applications ............................................................................... 7-7 7.4.2.1.1 Cluster-Level Configuration: User Configuration Manager .............................................. 7-7 7.4.2.1.2 Zone Level Configuration: Zone Configuration Manager................................................. 7-8 7.4.3 Accounting Management .......................................................................................................... 7-8 7.4.3.1 Air Traffic Information Access Data ..................................................................................... 7-8 7.4.3.2 Cluster-Level Air Traffic Information Access Packets .............................................................. 7-8 7.4.3.3 Air Traffic Information Access Logger and Log Viewer............................................................ 7-8 7.4.4 Performance Management ......................................................................................................... 7-8 7.4.4.1 Zone Historical Reports Application ..................................................................................... 7-9 7.4.4.2 Dynamic Reports .............................................................................................................. 7-9 7.4.4.3 ZoneWatch ...................................................................................................................... 7-9 7.4.4.4 Affiliation Display ............................................................................................................ 7-9 7.4.5 Security Management............................................................................................................. 7-10 7.4.5.1 Temporary Disable .......................................................................................................... 7-10 7.4.5.2 Permanent Disable .......................................................................................................... 7-10 7.4.5.3 User Client Security ........................................................................................................ 7-10 7.4.5.4 Security Partitioning........................................................................................................ 7-11 7.4.5.5 Authentication................................................................................................................ 7-11 7.4.5.6 Air Interface Encryption................................................................................................... 7-11 7.5 Multizone Fault Management............................................................................................................ 7-12 7.6 Introduction to Network Management Applications............................................................................... 7-13 7.6.1 Network Management Applications Overview ............................................................................ 7-13 7.6.1.1 Motorola PRNM Suite Applications Overview ..................................................................... 7-13 7.6.1.2 Other Motorola Applications............................................................................................. 7-15 7.6.2 Private Radio Network Management Suite Applications................................................................ 7-16 7.6.2.1 Application Launcher ...................................................................................................... 7-16 7.6.2.2 Affiliation Display .......................................................................................................... 7-16 7.6.2.3 ATIA Log Viewer ........................................................................................................... 7-17 7.6.2.4 Custom Historical Reports ................................................................................................ 7-17 7.6.2.5 Dynamic Reports ............................................................................................................ 7-18 7.6.2.6 Unified Event Manager .................................................................................................... 7-18 7.6.2.7 Historical Reports ........................................................................................................... 7-19 7.6.2.8 Radio Control Manager .................................................................................................... 7-19 7.6.2.9 Radio Control Manager Reports......................................................................................... 7-20 7.6.2.10 Software Download Manager .......................................................................................... 7-20 7.6.2.11 System Profile .............................................................................................................. 7-21 7.6.2.12 User Configuration Manager............................................................................................ 7-21 7.6.2.13 Zone Configuration Manager ........................................................................................... 7-22 7.6.2.13.1 High-Level Objects in ZCM................................................................................... 7-22 7.6.2.14 Zone Profile ................................................................................................................. 7-23 7.6.2.15 ZoneWatch................................................................................................................... 7-23 7.6.3 Network Transport Management Applications ............................................................................ 7-24 Appendix A Dimetra IP System Documentation ................................................................................................ A-1 Related Information............................................................................................................................................ I

xvi

List of Figures Figure 1-1 Figure 1-2 Figure 1-3 Figure 1-4 Figure 1-5 Figure 1-6 Figure 1-7 Figure 1-8 Figure 1-9 Figure 1-10 Figure 1-11 Figure 1-12 Figure 1-13 Figure 1-14 Figure 1-15 Figure 1-16 Figure 1-17 Figure 1-18 Figure 1-19 Figure 1-20 Figure 2-1 Figure 2-2 Figure 2-3 Figure 2-4 Figure 2-5 Figure 2-6 Figure 2-7 Figure 2-8 Figure 2-9 Figure 2-10 Figure 2-11 Figure 2-12 Figure 2-13 Figure 2-14 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 3-18

Basic Radio System ................................................................................................................... 1-1 Fixed Equipment....................................................................................................................... 1-2 Antenna Height and Coverage ..................................................................................................... 1-2 Simplex Communication ............................................................................................................ 1-3 Semi-Duplex Communication...................................................................................................... 1-3 Radios to Base Station Relationship ............................................................................................. 1-8 Example: Trunked Radio System Channel Assignments ................................................................... 1-9 Basic Trunked Site .................................................................................................................. 1-10 Conventional Radio System Example.......................................................................................... 1-11 Example: Organization of Users in a Talkgroup ............................................................................ 1-12 Example of Talkgroups in Multigroups........................................................................................ 1-12 Trunked Call Initiation ............................................................................................................. 1-13 Trunked Call Validation............................................................................................................ 1-14 Trunked Call Completion.......................................................................................................... 1-15 Multiple Site Trunked System.................................................................................................... 1-16 RF Site.................................................................................................................................. 1-17 Mobile Switching Office (MSO) ................................................................................................ 1-18 Example: Multizone System...................................................................................................... 1-18 Multizone System - Conditions for Interzone Trunking................................................................... 1-19 Modes of Operation in a Dimetra System..................................................................................... 1-21 TETRA defined Air Interface ...................................................................................................... 2-1 Pi/4-DQPSK Modulation ............................................................................................................ 2-3 ACELP Voice Compression ........................................................................................................ 2-4 Time Division Multiple Access - Base Stations ............................................................................... 2-4 Time Division Multiple Access - Radio (Full-Duplex Operation)........................................................ 2-5 E1 Carrier ................................................................................................................................ 2-8 Cooperative WAN Routing - Example ......................................................................................... 2-10 Ethernet Site Links- Example .................................................................................................... 2-11 Unicast Routing ...................................................................................................................... 2-13 Multicast Routing.................................................................................................................... 2-14 Call Processing - Multicast Routing of Traffic............................................................................... 2-16 Dimetra IP System Logical Traffic Planes .................................................................................... 2-17 Basic Secure Voice Operation .................................................................................................... 2-18 Voice Transmission.................................................................................................................. 2-19 HP DL360p Gen8 Server Front View ............................................................................................ 3-1 Network Management Subsystem................................................................................................. 3-3 Telephone Interconnect Subsystem ............................................................................................... 3-8 Network Time Server ............................................................................................................... 3-11 Transport Core with E1 Connections ........................................................................................... 3-12 Transport Core with Ethernet Connections ................................................................................... 3-13 CWR Patch Panel.................................................................................................................... 3-15 MTS LiTE ............................................................................................................................ 3-16 MTS 1 .................................................................................................................................. 3-17 MTS 2 .................................................................................................................................. 3-18 MTS 4 .................................................................................................................................. 3-19 Site Controller (SC) ................................................................................................................. 3-20 BTS Base Radio...................................................................................................................... 3-21 Control Site............................................................................................................................ 3-22 Dispatch Subsystem................................................................................................................. 3-23 MCC 7500 Dispatch Console Subsystem ..................................................................................... 3-24 MCC 7500 Emergency Beacon .................................................................................................. 3-25 GGM 8000 used for CCGW ...................................................................................................... 3-27

xvii

System Overview

Figure 3-19 Figure 3-20 Figure 3-21 Figure 3-22 Figure 3-23 Figure 3-24 Figure 3-25 Figure 3-26 Figure 3-27 Figure 3-28 Figure 3-29 Figure 3-30 Figure 3-31 Figure 3-32 Figure 3-33 Figure 3-34 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 5-9 Figure 5-10 Figure 5-11 Figure 5-12 Figure 5-13 Figure 5-14 Figure 6-1 Figure 7-1 Figure 7-2 Figure 7-3

xviii

Patching with a Conventional System.......................................................................................... 3-27 MCC 7500S Dispatch Console................................................................................................... 3-28 MTP3100/MTP3200 ................................................................................................................ 3-29 MTP3150MTP3250 ................................................................................................................ 3-30 MTH800 Portable ................................................................................................................... 3-31 MTP850 S ............................................................................................................................. 3-32 MTP850 FuG ......................................................................................................................... 3-32 MTP830 S ............................................................................................................................. 3-33 MTP830 FuG ......................................................................................................................... 3-34 MTP850 Ex ........................................................................................................................... 3-35 MTP810 Ex ........................................................................................................................... 3-35 TCR1000............................................................................................................................... 3-36 MTM800 Enhanced ................................................................................................................. 3-37 MTM5200 and MTM5400MTM800 FuG .................................................................................... 3-37 MTM5500MTM800 FuG ET in Mixed Dual Control Head Configuration with eCH and TSCH ............. 3-38 Telephone Style Control Head (TSCH)........................................................................................ 3-40 Server Interactions Defined ......................................................................................................... 4-5 UCM Home Zone Mapping Window............................................................................................. 5-4 Home Location Register ........................................................................................................... 5-10 Home Location Register - Visitor Location Register....................................................................... 5-10 Intrazone Talkgroup Request from a BTS Site............................................................................... 5-13 Talkgroup Call Grant ............................................................................................................... 5-14 Interzone Call Request ............................................................................................................. 5-16 Private Call ............................................................................................................................ 5-21 Telephone Interconnect in E1 networking..................................................................................... 5-24 Short Data Services ................................................................................................................. 5-29 Authentication ........................................................................................................................ 5-31 Encryption of Traffic................................................................................................................ 5-32 Reduced Interzone Service Availability ....................................................................................... 5-38 Interzone Individual Call with Radios in Their Home Zones ............................................................ 5-39 Interzone Individual Call with Radios Not in Their Home Zones ...................................................... 5-40 Zone with Geographical Redundancy .......................................................................................... 6-10 Multizone Fault Management - Client Access to Each Zone ............................................................ 7-12 Multizone Fault Management- Event Forwarding to a Customer-Supplied Fault Management System .................................................................................................................................. 7-12 PRNM Applications From a System Perspective ........................................................................... 7-14

List of Tables Table 3-1 Table 3-2 Table 4-1 Table 4-2 Table 4-3 Table 5-1 Table 5-2 Table 5-3 Table 5-4 Table 5-5 Table 6-1 Table 7-1 Table 7-2 Table 7-3 Table 7-4 Table 7-5 Table A-1

List of Telephone Numbers ........................................................................................................... v Types of System Server (constellations)......................................................................................... 3-2 MTM5x00 MTM800 FuG/MTM800 FuG ET Options.................................................................... 3-39 Summary of Database Administration Functions ............................................................................. 4-4 Hierarchical Listing of Servers Hosting Databases ........................................................................... 4-5 Server Interactions.................................................................................................................... 4-6 Short Subscriber Identity Ranges.................................................................................................. 5-5 Security Classes ...................................................................................................................... 5-32 Zone Call Service States ........................................................................................................... 5-37 Levels of Group Service Availability........................................................................................... 5-37 Call Processing Behavior During Recovery .................................................................................. 5-43 Console Priority Levels ............................................................................................................ 6-13 Air Interface Encryption - Security Features ................................................................................ 7-11 Motorola PRNM Suite Applications............................................................................................ 7-14 Other Motorola Applications .................................................................................................... 7-15 Object Classes in UCM ............................................................................................................ 7-22 High-Level Objects in ZCM ...................................................................................................... 7-22 ............................................................................................................................................. A-1 ................................................................................................................................................. I

xix

List of Processes 1.1.8 — Tracing a Basic Call....................................................................................................................................................1-13 2.3.5 — Call Model ..................................................................................................................................................................2-14 5.4.1.1.3 — Call Grant..............................................................................................................................................................5-14 5.4.1.1.4 — Intrazone Talkgroup Call Audio Routing .............................................................................................................5-14 5.4.1.1.5 — Talkgroup Call Continuation and Teardown.........................................................................................................5-15 5.5.1.1 — Private Call Request Flow .......................................................................................................................................5-21 5.5.1.2 — Intrazone Private Call Audio Flow, Call Continuation, and Teardown ...................................................................5-22 5.5.2.2.3.1 — Call Setup...........................................................................................................................................................5-26 5.6 — Short Data Services........................................................................................................................................................5-29 5.11.3 — System Behavior During Automatic Switchover......................................................................................................5-42

xxi

About System Overview This manual explains radio system concepts and describes the components and functionality of the Dimetra IP system. The purpose of this manual is to: • Describe the basic radio system concepts and call processing basics. • Provide an introduction to the various components and processes associated with the Dimetra IP system. This manual is an introduction to the Dimetra IP system. The information in this manual does not assume any pre-knowledge of the Dimetra IP system or radio concepts in general.

xxiii

What is Covered In This Manual? This manual provides information in the following areas: • 1 Radio System Concepts, page 1-1 provides an introduction to the basic concepts of conventional radio systems and Motorola trunked radio systems. • 2 Dimetra IP System Technology, page 2-1 discusses technology behind Dimetra IP system. • 3 Dimetra IP System Components, page 3-1 discusses the hardware components associated with the Dimetra IP System. • 4 Dimetra IP Data Management, page 4-1 presents an overview of the databases, servers, and Zone Controllers found in the Dimetra IP system. • 5 Dimetra IP Call Processing, page 5-1 presents an overview of call processing, which takes place at the MSO equipment in a Dimetra IP system. • 6 Dimetra IP System Features, page 6-1 lists and explains the features and options available for the Dimetra IP system. • 7 Dimetra IP Network Management, page 7-1 presents an overview of the FCAPS model as described by the International Organization for Standardization (ISO). It also discusses Private Network Management (PRNM), its software applications or tools used to manage the Dimetra IP system and Network Management Software Tools that support the management of the system and its component parts. • A Dimetra IP System Documentation, page A-1 contains information on related Dimetra IP system documentation, including third-party documentation.

xxv

Helpful Background Information Motorola offers various courses designed to assist in learning about the system. For information, go to http://www.motorolasolutions.com/training to view the current course offerings and technology paths.

xxvii

Related Information See A Dimetra IP System Documentation, page A-1. The appendix includes a full listing of the Dimetra IP system documentation and related documentation.

xxix

Icon Conventions The document set is designed to give the reader more visual cues. The following graphic icons are used throughout the documentation set. These icons and their associated meanings are described below.

SUGGESTION

A Suggestion implies a recommendation or tip from Motorola, which does not require to be followed, but may be helpful. There is no warning level associated with a Suggestion.

Notes contain information that is more important than the surrounding text, such as exceptions or preconditions. Also, refer the reader elsewhere for additional information, remind the reader how to complete an action (when it is not part of the current procedure, for instance), or tell the reader where information is located on the screen. There is no warning level associated with a Note.

An Important icon indicates information that is crucial to the discussion at hand, but which is not a Caution or a Warning. There is no warning level associated with the Important icon.

The Caution icon implies information that must be carried out in a certain manner to avoid problems, procedures that may or may not be necessary as determined by the reader’s system configuration, and so on. Although no damage occurs if the reader does not heed the caution, some steps may need repeating.

The signal word CAUTION may be used without the safety icon to state potential damage or injury that is not related to the product.

The Warning icon implies potential system damage if the instructions or procedures are not carried out exactly, or if the warning is not heeded.

The Danger icon implies information that, if disregarded, may result in severe injury or death of personnel. This is the highest level of warning.

xxxi

Style Conventions The following style conventions are used: Convention

Description

Bold

This typeface is used for names of, for instance, windows, buttons, and labels when these names appear on the screen (example: the Alarms Browser window). When it is clear that we are referring to, for instance, a button, the name is used alone (example: Click OK).

Monospacing font in bold

This typeface is used for words to be typed in exactly as they are shown in the text (example: In the Address field, type http://ucs01.ucs:9080/)

Monospacing font

This typeface is used for messages, prompts, and other text displayed on the computer screen (example: A new trap destination has been added).

Monospacing font in bold Italic

This typeface is used with angle brackets for words to be substituted by a specific member of the group that the words represent (example: ).

In sequences to be typed in, the angle brackets are omitted to avoid confusion as to whether the angle brackets are to be included in the text to be typed. Arial bold

This typeface is used for keyboard keys (example: Press Y, and then press Enter).

>

A > (right angle bracket) is used for indicating the menu or tab structure in instructions on how to select a certain menu item (example: File > Save) or a certain sub-tab.

xxxiii

1

Radio System Concepts Radio systems provide a convenient and timely method of communication for people engaged in various public safety-related, transportation, and service occupations. Radio systems differ in design based on the needs of the individual users. One radio system may support a towing company with a dispatcher and two tow trucks communicating back and forth. Another radio system may support the needs of a public utility company with a network of antenna towers and control sites and field personnel scattered across a wide geographic area. The type of radio system that you have depends on the needs of your individual organization.

1.1 What is a Radio System? A radio uses electromagnetic waves to send information across the air. This is accomplished by producing an electrical signal that moves back and forth, or oscillates, at a rapid rate. The rate at which a radio signal oscillates back and forth is called its frequency and is measured in Hertz (Hz). Most radio frequencies are in Megahertz (MHz), or millions of cycles per second.

1.1.1 Basic System Components A basic radio system consists of equipment that transmits and receives radio signals that are used to transport some type of information. The information carried by these radio signals can be audio or data. In the case of voice systems, the transmitter is used to produce and amplify a radio carrier signal which is combined, or modulated, with a voice signal from a microphone. The modulated radio signal is sent to an antenna, which radiates the signal into the air. The radiated signal is picked up by a receiving antenna and sent to a receiver. Here the radio signal is processed back into the original audio signal, which is fed into a loudspeaker so that the original voice message can be heard. See the Figure 1-1 Basic Radio System for components of a basic radio. Figure 1-1

Basic Radio System

Microphone 0

0

Antennas

0 0 0 0

Tra ns mitte r

Receiver

Loudspeaker

1.1.1.1 Radio System Equipment Two-way radio equipment can be classified as either fixed, mobile, or portable. Each of these units includes a transmitter (TX), receiver (RX), and antenna system.

68015000701-C - October 2013

1-1

System Overview

Fixed equipment is located at a central site. A base station is used to transmit the signal generated through the microphone to portable and mobile equipment located at some distance. The range of the base station depends on its power, antenna system, terrain, and environmental conditions. The location of the base station control is known as the Dispatch Centre. Figure 1-2

Fixed Equipment 0

0

0 0 0 0

Mobile and Portable equipment are the radios that are not fixed. Mobile radios are mounted in vehicles and portable radios are handheld devices carried by a person.

1.1.1.2 Radio System Range The range of a radio system is affected by many different factors. One of the most critical coverage factors is antenna height and location, because the range of a radio system is limited to the horizon as seen by the radio antenna. In general, the range of a radio system depends on the effective height of the antenna. Basically, the higher an antenna is installed, the greater an area receives coverage. Figure 1-3

Antenna Height and Coverage

1.1.2 Communication Types The communication type used depends on the number of users and the type of equipment available. Radio systems can use three types of communication: • 1.1.2.1 Simplex, page 1-3 • 1.1.2.2 Semi-Duplex, page 1-3

1-2

68015000701-C - October 2013

1.1.2.1 Simplex

• 1.1.2.3 Duplex, page 1-4

1.1.2.1 Simplex The most basic type of radio communication is simplex. Simplex communication consists of radio units operating on a single frequency. Because everyone transmits and receives on the same frequency, users cannot talk and listen at the same time. Simplex means transmission in one direction at a time. Figure 1-4

Simplex Communication

Single Frequency

A simplex radio system works well when there are only a few users who are closely located. When additional users are added to the system, the competition for the one available frequency can make it difficult to get a message across. In addition, great distances and natural obstacles such as high hills and tall buildings can interfere with the single frequency.

1.1.2.2 Semi-Duplex Semi-duplex communication uses two frequencies: one to receive and one to transmit. A radio operating in semi-duplex mode can only transmit or receive at any time. Radios operating on the Dimetra IP system use semi-duplex communication to communicate with the base stations during talkgroup and multigroup calls. A semi-duplex individual call is also supported in the Dimetra IP system. Figure 1-5

Semi-Duplex Communication

TX 851.0125 MHz

68015000701-C - October 2013

RX 806.0125 MHz

1-3

System Overview

1.1.2.3 Duplex Duplex communication uses different frequencies simultaneously, one to transmit and the second to receive. The transmitter output is isolated and separated in frequency to prevent blocking the input of its companion receiver. Also called full-duplex, this type of operation is used to indicate that the equipment can receive and transmit at the same time. Normally, fixed equipment (a base station) operates in full-duplex mode while mobile equipment typically operates in semi-duplex mode.

1.1.3 Call Types There are several possible types of voice calls that can be made. The examples are divided into two main types of call services: • Group-based call services Group-based calls are services that provide for group (one-to-many) communication. The types of group-based calls include: – 1.1.3.1 Talkgroup Calls, page 1-4 – 1.1.3.2 Multigroup Calls, page 1-4 – 1.1.3.3 Object Calls, page 1-4 – 1.1.3.4 Announcement Calls, page 1-5 – 1.1.3.5 Emergency Calls, page 1-5 – 1.1.3.6 Ruthless Preemption, page 1-5 – 1.1.3.7 Direct Mode Operation Calls, page 1-5 – 1.1.3.8 Site Wide Calls, page 1-5 • Individual call services Individual calls are services that provide for individual user to user communication. The types of individual calls include: – 1.1.3.9 Private Calls, page 1-6 – 1.1.3.10 Telephone Interconnect Calls, page 1-6

1.1.3.1 Talkgroup Calls Talkgroup calls are made from one radio (or dispatch console) to all other radios (or dispatch consoles) that are affiliated with the talkgroup. Talkgroup calls in the Dimetra IP system are semi-duplex, meaning that a participant in the call can only be transmitting or receiving at any time. When the call initiator releases their push-to-talk (PTT) switch, a hang timer begins. This hang timer maintains the call for a short time to allow any user in the talkgroup to press their PTT to respond. Talkgroup calls are typically the most common types of calls made in a public safety system.

1.1.3.2 Multigroup Calls Multigroup calls are talkgroup calls except that the calling radio (or dispatch console) is transmitting to two or more talkgroups.

1.1.3.3 Object Calls The object calls allow connections within specialized ad-hoc talkgroups, called object groups.

1-4

68015000701-C - October 2013

1.1.3.4 Announcement Calls

This feature may be applied in an airport system, where different functions carried out at the airport are linked to flights (that is objects), resulting in a flight-oriented communication system. When an airplane is arriving at an airport gate, different resources are necessary to service this flight, and for communication purposes these resources are grouped following a structure of flights and functional groups.

1.1.3.4 Announcement Calls An announcement call involves two or more talkgroups which are defined in a multigroup. A radio or console operator can transmit a message to all the talkgroups in the multigroup simultaneously by selecting a multigroup on the radio selector (or dispatch console screen). Any user affiliated with any talkgroup in the multigroup (or to the multigroup itself) receives the call.

1.1.3.5 Emergency Calls An emergency call is a specialized, high-priority version of a talkgroup or announcement call. Emergency calls always have the highest priority in the system. When an emergency call request is made when all traffic channels are busy, the request takes priority over any other type of call request. The emergency call is transmitted to the radio’s currently selected talkgroup or multigroup of the radio.

1.1.3.6 Ruthless Preemption This mode of operation causes the controller to look at the priority of the talkgroups assigned to the traffic channels and preempt the group with the lowest priority so the channel can be assigned to the emergency caller.

1.1.3.7 Direct Mode Operation Calls Radios can select direct mode operation (DMO) to directly communicate with other radios without calling through the system infrastructure. DMO calls are similar to the back-to-back or talkaround operation used in analog radio systems. In the Dimetra IP system, DMO supports group calls and emergency group calls with preemption. DMO does not currently support encryption, individual calls, or data services. Direct mode operation requires that radios are within the appropriate range for the call to be successful. Before the radio transmits in DMO, it first checks whether the channel is available. Once the push to talk (PTT) button is released, another member of the group is free to respond. Whenever a radio is making a DMO call, the radio user ID is displayed on the radios that are receiving the call. DMO supports group calls, preemptive emergency calls and private calls. Some mobile and portable radios also support end to end encryption in DMO. The radios can also communicate with a third-party DMO Gateway (supplied by the customer). Specific talkgroups can be configured to communicate with the DMO Gateway. The supported DMO Gateway uses 10 MHz transmit/receive offset frequencies.

1.1.3.8 Site Wide Calls Site Wide calls are calls made from a dispatch console to all radios registered with a particular site. This call reaches all radios registered with the site regardless of what talkgroups they may be part of.

68015000701-C - October 2013

1-5

System Overview

1.1.3.9 Private Calls Private calls allow properly equipped radios in the same system to enter into one-to-one conversations. The sender enters into the private conversation mode, selects a target radio by dialing an ID on a keypad, and presses the PTT (semi-duplex) or send (full-duplex) to initiate the call. The target radio indicates that a private call is being requested. Radios can be programmed to only receive calls, only from a programmed list, or call radios from a list or through the keypad. The Dimetra IP system supports both full-duplex and semi-duplex private calls.

1.1.3.10 Telephone Interconnect Calls Telephone Interconnect calls allow full-duplex communication between a radio and the public switched telephone network (PSTN). The connection to the PSTN is achieved through a customer-supplied private branch exchange (PABX). The radio user initiates a telephone interconnect call by dialing an external phone number. The phone enters then a “phone mode” reserved for the Telephone Interconnect Subsystem.

1.1.4 Types of Communication Channels There are two types of communication channels used in Dimetra IP radio system: • 1.1.4.1 Control Channel (CC), page 1-6 • 1.1.4.2 Traffic Channel (TCH), page 1-6

1.1.4.1 Control Channel (CC) The controller needs to be able to communicate with all radios in the system to receive call requests and send channel assignments to the radios in the field. This is the role of the control channel (CC). Each system has at least one of its channels assigned to function as a control channel. The other channels are used for voice and data communication. The control channels are always active. They transmit and receive the signaling to monitor and control the operation of the radios. The radios use control channels as long as they are not involved in a voice call. A radio uses a control channel to send in call requests or to receive call assignments. A radio always tunes to the control channel except when it is assigned to a call on a traffic channel. When a call is completed, the radios involved in the call switch back to the active control channel. To make a call on a trunked system, a radio user presses the push-to-talk (PTT) button on the radio. A call request is sent over a control channel to the controller. The controller assigns a channel to the user’s group and sends out an assignment message over a control channel telling all radios that have that particular group selected to switch to a specific traffic channel. Radios in the system send a signal to the controller, through the control channel, indicating their unique identification and talkgroup selection. This signal is sent whenever a radio is powered up or the radio user changes the position of the talkgroup selector. This process is known as affiliation.

1.1.4.2 Traffic Channel (TCH) When one of the members of a group requests voice or data services, the group is assigned its own traffic channel for the duration of the call. A group that is assigned to a particular traffic channel cannot be heard by members of a talkgroup assigned to another traffic channel.

1-6

68015000701-C - October 2013

1.1.5 Basic Site Components

In a trunked system, the traffic channels can be operated in one of two modes: Transmission Trunking, Message Trunking or Message Trunking with PTT ID. • Transmission Trunking The controller reclaims the traffic channel immediately after detecting a disconnect signal from the transmitting unit. The receiving radios immediately returns to the control channel. The entire request and assignment procedure is repeated for each PTT from the originator or a radio responding to the original call. • PTT-ID Trunking This allows a group to retain the assigned traffic channel for some time, after the transmitting unit releases the PTT. When a message trunked call is in progress, other radio users within the same group are allowed to key without returning to the control channel for a traffic channel assignment. This mode of operation provides positive identification of the transmitting radio and must be programmed in both the radio and the system.

1.1.5 Basic Site Components The main components of a basic site include the Site Controller and base radios.

1.1.5.1 Site Controller (SC) A Site Controller processes inbound and outbound signaling traffic, assigns base radios for traffic channel access, and generally monitors and maintains order at the site. The Site Controller maintains a database that keeps track of the Unit ID of each radio and the radio affiliations to talkgroups. The Site Controller in a single site performs the following call processing functions: • Services call requests • Recovers and decodes inbound signal requests • Maintains a database of active radios and their system permissions • Receives group affiliations • Checks call access privileges • Issues call grants • Monitors and controls each call sequence • Maintains a list of radios that are waiting for base station assignments • Selects and assigns traffic channels as required • Selects the control channel • Decodes control signals originated by the radios • Generates and encodes the proper outbound signaling packets for such purposes as directing system users to specific channels • Generates the data which is superimposed on all voice communications and is used to unmute the audio circuitry in receivers authorized to monitor audio transactions

1.1.5.2 Base Radio (BR) A base radio serves as the Radio Frequency (RF) interface between the system infrastructure and the radios. Base radios in a trunked system have three primary interfaces: • A receiver to pick up the RF signal from the radios

68015000701-C - October 2013

1-7

System Overview

• A transmitter to send RF signals to the radios • A wireline interface to send audio and control traffic to the system infrastructure Antenna systems for base stations are usually located on top of high structures such as buildings, hills, or towers. The base stations are normally located close to their antennas in order to minimize the losses inherent in the cables connecting the stations to the antennas. See Figure 1-6 Radios to Base Station Relationship for the relationship between the radios and a base station. Figure 1-6

Radios to Base Station Relationship

The BTS has several channels and these channels can either be designated to Control Channel (CC) or Traffic Channel (TCH), which are mentioned below.

1.1.6 Radios Radios are classified as mobile (vehicle-mounted) or portable (carried by a person, usually handheld) radios which provide users with the ability to make voice calls, send short data messages, or interface with mobile data equipment. Each radio is assigned a unique identification number that identifies the radio to the system. It also contains the logic circuitry necessary to perform the following trunking functions: • Generate and transmit requests for service in the form of data words that are then used to modulate the carrier frequency. • Interpret the signaling messages sent by the central controller. • Generate the frequency of the assigned traffic channel. • Generate tones to advise the radio user of the status of the call request.

1.1.7 Call Processing Basics Call processing is the sequence of events that the system goes through to handle a call request.

1-8

68015000701-C - October 2013

1.1.7.1 Trunked and Conventional Radio Systems

1.1.7.1 Trunked and Conventional Radio Systems There are two types of radio systems: • Trunked • Conventional

1.1.7.1.1 Trunked System Operation In trunked radio systems the users are not assigned to a fixed channel. Channels are common resources that are accessible to all users on an as-needed and as-available basis. When a radio user initiates a call, the system assigns an available channel to that call, eliminating the condition where one channel is busy while another channel is inactive. When the call is finished, the channel is released and made available for other users. See figure below for an example of channel assignments in a trunked radio system. Figure 1-7

Example: Trunked Radio System Channel Assignments

Channel 1

Channel 2

Channel 3

Trunking takes advantage of the fact that people do not talk on their radios continuously for 24 hours a day. Most radio users need access to a channel several times a day, but their total time on the system may not exceed five minutes each. Temporary channel assignment helps ensure that a channel is available when a conversation needs to take place. Trunking reduces the number of busies and improves the efficiency of the system resources. A call is busied if it has been placed in a queue due to no channel being available.

68015000701-C - October 2013

1-9

System Overview

Figure 1-8

Basic Trunked Site

Controller

CC

TCH

TCH

Channel 1

Channel 2

Channel 3

TCH

Channel 4

1.1.7.1.2 Conventional System Operation In conventional radio systems users share a common RF channel and compete for air time. In addition, users not only listen to other conversations, they must monitor other conversations before they can make a call of their own. Individual radio users are assigned a particular channel to use when communicating with their group. If one group has a lot of radio activity while another has only light usage, several people may be waiting to use their assigned channel, while the other channel sits idle. For example, channel 1 is providing services to group A; channel 2 is providing services to group B and thus cannot accept requests from group C; channel 3 is idle but cannot automatically provide services to group C. See the figure below.

1-10

68015000701-C - October 2013

1.1.7.2 Radio System Users

Figure 1-9

A

Conventional Radio System Example

A

Channel 1

B

C

Channel 2

D

D

Channel 3

1.1.7.2 Radio System Users The radio system stores information about users according to their individual location, and any groups to which they have been assigned. This following discusses the various user classifications that are available in a radio system.

1.1.7.2.1 Radio Users Personnel using the trunked system are assigned a radio that is active in the system. A radio record in the central controller is used to control the system features that the radio user is permitted to access.

1.1.7.2.2 Talkgroups A talkgroup is the basic unit of communication in a trunked system. In most organizations, radio users work in groups that are based on their functions and responsibilities. In a trunked radio system, these groups of radio users can be assigned to communication talkgroups that reflect their function or responsibilities. The figure below is an example of a talkgroup. Programming of talkgroups in a radio is based on the communication needs of radio users. A radio can be programmed with only one or with several talkgroups. Radio users selecting a particular talkgroup on their radio are assigned a traffic channel when someone in the group requests talkgroup call services. Group privacy during conversations is provided since only one talkgroup is assigned to each traffic channel. Each talkgroup is configured and identified in the system by a unique talkgroup ID.

68015000701-C - October 2013

1-11

System Overview

Figure 1-10

Example: Organization of Users in a Talkgroup

Ta lkgroup 1

Ta lkgroup 2

Ta lkgroup 3

1.1.7.2.3 Multigroups Several talkgroups can be combined to form a multigroup (also called an announcement group). Multigroups are assigned an ID from the same pool of numbers as the talkgroups. In this example, calls placed to Multigroup A would be heard by the radio users in Talkgroups 2 and 3. Figure 1-11

Example of Talkgroups in Multigroups

Ta lkgroup 2

Ta lkgroup 3

Ta lkgroup 1

Multigroup A

1-12

68015000701-C - October 2013

1.1.8 Tracing a Basic Call

1.1.8 Tracing a Basic Call Process Steps 1

When a radio user initiates a call, the radio signals to the system via the control channel and requests a traffic channel. In the figure below, Radio 1 is requesting a call, and Radio 2 and Radio 3 in Talkgroup B are listening on the control channel and detect the request for a call. The radios in Talkgroup A are also monitoring the control channel but ignore the call request because they are in different talkgroup.

In Figure 1-12 Trunked Call Initiation, Figure 1-13 Trunked Call Validation, and Figure 1-14 Trunked Call Completion, the arrows indicate the direction in which the information flows. Figure 1-12

Trunked Call Initiation

TETRA Carrier C

1

Ta lkgroup A

68015000701-C - October 2013

T

T

T

2

3

Ta lkgroup B

1-13

System Overview

2

The system validates the call request, assigns a traffic channel and signals a traffic channel grant to all radios of that group. The members of Talkgroup B respond by monitoring the temporarily assigned traffic channel. Radios in Talkgroup A continue to monitor the control channel as before. In the figure below, Radio 1 is transmitting on a traffic channel, and Radio 2 and Radio 3 are listening to the call. Figure 1-13

Trunked Call Validation

TETRA Carrier C

1

Ta lkgroup A 3

1-14

T

T

T

2

3

Ta lkgroup B

When the call is finished, all radios in Talkgroup B return to monitoring the control channel. The traffic channel becomes available for other radios.

68015000701-C - October 2013

1.2 Multiple Site Trunked Systems

Figure 1-14

Trunked Call Completion

TETRA Carrier C

T

T

1

Ta lkgroup A

T

2

3

Ta lkgroup B

1.2 Multiple Site Trunked Systems Multiple site trunked systems increase the size of the coverage area and provide radio communication in places that are out of reach of a single site trunked system. A multiple site system can be analyzed as a grouping of single site systems with a centrally located point of control and audio distribution. The central controller at each site supervises the equipment and radios at its location while the centralized control coordinates and oversees the operation of the individual sites. This coordination requires the use of a device that can communicate with the individual Site Controllers. A multiple site system allows radios to roam across large geographic areas without losing communication with their group. In addition, members of a group can be dispersed throughout the various sites in the system and still be able to communicate with each other. The following describes how this can be accomplished.

68015000701-C - October 2013

1-15

System Overview

Figure 1-15

Multiple Site Trunked System

Site Controller trolle r

RF Site Mobile Switching S wi witching Office ce Site Controller

RF Site

Site S ite Controller Con ontrolle r

RF Site

1.2.1 RF Sites An RF site is a geographical area within which a two-way radio infrastructure allows communication between two-way radios. It is the equivalent of a single site trunked system with additional control and audio links to a central mobile switching office (MSO). Under certain conditions, it can operate independently in local site trunking mode, but its normal mode of operation is in wide-area trunking with other RF sites. The figure below shows an example of an RF site.

1-16

68015000701-C - October 2013

1.2.2 Zone

Figure 1-16

RF Site

Site

1.2.2 Zone A zone consists of sites connected to the master site. The Zone Controller is the central point for all the equipment necessary to control and manage the sites in a zone.

1.2.3 Mobile Switching Office (MSO) A Mobile Switching Office (MSO) is a physical location hosting the equipment for the operation of a multiple site system. Equipment at the MSO coordinates call processing, assignment of system wide area resources, and distribution of audio to all the other sites in the system. Central equipment of a zone or several zones can be placed in the MSO.

68015000701-C - October 2013

1-17

System Overview

Figure 1-17

Mobile Switching Office (MSO)

Zone Controller Control Sites Mobile Switching Office Base Stations

1.3 Multizone Systems A multizone system refers to a radio system that contains several interconnected zones. This type of configuration provides a very wide area radio communications network based on the interconnection of many zones. A multizone system operates with virtually transparent boundaries, creating a homogeneous system operation over very large geographical areas. The Figure 1-18 Example: Multizone System shows an example of a multizone system. Figure 1-18

1-18

Example: Multizone System

68015000701-C - October 2013

1.3.1 Conditions for Multizone Communication

1.3.1 Conditions for Multizone Communication A multizone system contains the following elements, which are necessary to maintain system wide communication: • An active control path is required between any two zones in order to be able to coordinate a call that involves sites in more than one zone. • Interzone audio paths are needed to route the audio to any zone required by the location of the talkgroup members. Figure 1-19

Multizone System - Conditions for Interzone Trunking

Site 1

Site 4

Site 2

Co ol n tr d io Au

Ma s te r S ite Zone 1

ol n tr C o d io Au

Ma s te r S ite Zone 3

l ro nt C o u d io A Control Audio

Site 6

Ma s te r S ite Zone 2

Co n Au tro l d io

Site 9

Control Audio

Site 7

Co ntro l Au dio Control Audio Co n Au tro l d io

Co Au n tro di l o Control Audio

Co ntro l Au dio

Site 3

Site 5

Site 8

Multizone systems contain various hardware devices and software applications that allow the system to exchange control information between zones, establish audio paths between zones when necessary, track radio movement across sites or zones, and provide a management subsystem that can be accessed from any one of the zones. The terminology has expanded to include home zone mapping, controlling zone, and participating zone.

1.3.1.1 Home Zone Mapping Home zone mapping provides the capability to divide into ranges the total number of individual and talkgroup IDs that can be used in the system and to assign the ranges to the various zones. All of the home zone assignments for groups and individuals are compiled into two home zone maps: • Individuals to Home Zone • Groups to Home Zone

68015000701-C - October 2013

1-19

System Overview

The zone assigned to a particular ID is the home zone of this ID. The home zone to which an ID is assigned has an impact on how the system operates. Home zone assignment affects system operation in the following ways: • Configuration information is distributed throughout the system based on the home zone assignment of the ID. • A Zone Controller stores only the configuration information for those individual and group IDs that are home to that zone.

1.3.1.2 Controlling Zone For group call services, the home zone of the group is always the controlling zone for the call, regardless of the zone where the group member is currently registered. Depending on system configuration, this can impact the number of interzone calls versus the number of single-zone calls that take place in the system. This can then affect the number of interzone resources that are needed between any two pair of zones.

1.3.1.3 Participating Zone A participating zone is any zone containing one or more users involved with a call controlled by another zone. When a talkgroup member requests a call that requires more than one zone, the controlling zone receives acknowledgments from all participating zones before the call is granted. Resource allocation is invoked by a request sent from controlling zone to all participating zones. The acknowledgment from a participating zone is only sent if resource allocation is successful.

1.3.2 Modes of Operation The figure Figure 1-20 Modes of Operation in a Dimetra System shows the normal mode of operation and the three fall back modes with reduced capabilities: Zone Isolated Wide Area Trunking, Local Site Trunking and Direct Mode Operation (DMO).

1-20

68015000701-C - October 2013

1.3.2.1 Wide Area Trunking with Interzone Trunking

Figure 1-20

Modes of Operation in a Dimetra System

Local Site Trunking Zon e Is ola te d Wide Are a Trunking

Direct Operation Mode

Wide Area Trunking with Inte rzone Trunking

In the figure, the circles do not represent coverage. In reality, the coverage of base stations overlaps.

1.3.2.1 Wide Area Trunking with Interzone Trunking This is the normal operating state for each site in the system. If all sites are in wide area trunking with interzone trunking mode, there are communication paths covering the entire zone and the interzone links are functional. The Zone Controller is in control of call processing and audio routing; each site has an active control channel and at least one operational traffic channel. Interzone and site links must be operational to support the control and audio traffic between the remote sites, the MSO and other zones in the system.

1.3.2.2 Fall Back Modes There are three fall back modes in a Dimetra IP system detailed below: Zone Isolated Wide Area Trunking, Local Site Trunking and Direct Mode Operation.

1.3.2.2.1 Zone Isolated Wide Area Trunking Zone Isolated Wide Area Trunking is the mode a zone enters when interzone links are lost. Radios registered with the zone can still communicate with each other, but communication with radios in other zones is impossible.

68015000701-C - October 2013

1-21

System Overview

1.3.2.2.2 Local Site Trunking A mode of operation that takes place when there is a loss of the control path to a site or all the audio paths to a site are lost. The affected site operates as a single site trunked system providing services to radios registered with the site. Audio is not routed to the MSO, it remains within the site. The remote Site Controller is in control of call processing at the site while the Zone Controller maintains all other sites in wide area trunking. The site can stay in local site trunking mode as long as there is a good control path between the Site Controller and the registered base stations, an active control channel, and a working traffic channel.

1.3.2.2.3 Direct Mode Operation (DMO) If all connections to the Radio Network Infrastructure (RNI) are lost, the individual radios that support this feature can enter into direct mode operation. This means that the radio use its own antenna and amplifying power to communicate with other radios that support DMO and are within range.

1.3.3 Interzone Group Service Availability For group-based services, there are three possibilities for call requests: • Full interzone group service availability: All zones are in a state of interzone trunking with respect to the home zone of the group. • Reduced interzone group service availability: At least one participating zone is in interzone trunking with the home zone of the group and at least one zone is not. • Zone isolated group service availability: The zone can provide call services only within its own site resources.

1.3.4 Where Calls Occur Calls can occur in a single site, a single zone, and between zones (a multizone call).

1.3.4.1 Single Site Calls can take place within a single site, such as the call that was described in 1.1.8 Tracing a Basic Call, page 1-13. In a multiple site or multizone system, single site calls can also take place, such as the call described in 1.1.8 Tracing a Basic Call, page 1-13.

1.3.4.2 Zone Calls can take place between multiple sites within a zone. The Zone Controller arranges the necessary sites for the call, and the Site Controllers (SCs) for each site assign the channel needed for the call.

1.3.4.3 Multizones In a multizone system, calls can take place between more than one zone. The controllers at the MSO of each zone communicate with each other to coordinate the assignment of resources.

1-22

68015000701-C - October 2013

2

Dimetra IP System Technology The Dimetra IP system is a digital radio communications system that provides radio users with voice and data services over a very wide geographical area. Users at any location within the coverage area can press the Push-To-Talk (PTT) button on their radios to make calls to any valid group or individual located anywhere in the coverage area (which can cover thousands of square miles). The system requires a complex network of workstations, high-speed Local Area Network (LAN) and Wide Area Network (WAN) facilities, sophisticated databases, and management software. The Dimetra IP system allows communication across multizones and allows users from different zones to be combined into talkgroups. This means that users can communicate across a wide geographic area and use a wide range of communication capabilities, provided that the user configuration is well-planned and systematically implemented.

2.1 Terrestrial Trunked Radio (TETRA) The TETRA standard was developed by the European Telecommunications Standards Institute (ETSI) for private mobile radio. TETRA provides standardization for radio system services, system interfaces, and methods for registration and call processing. ETSI has defined TETRA as open standard to provide standardization and interoperability of telecommunication systems and their application. Some of the TETRA standards include: • 25 kHz carrier spacing • Pi/4-DQPSK modulation • ACELP voice compression • 36 kbps carrier data rate • 28.8 kbps user data rate • TDMA with 4 timeslots per carrier The TETRA standard defines the air interface between radios and the infrastructure. This enables radios from different suppliers to be used for basic TETRA operations regardless of the supplier of the infrastructure – see the figure below. Figure 2-1

TETRA defined Air Interface

Infrastructure

68015000701-C - October 2013

2-1

System Overview

The most typical users of a TETRA system include public safety, transportation, utilities, industrial organizations, government agencies, and private telecommunication agencies.

2.1.1 Spectrum Management Because frequency spectrum is a finite resource, the use of channels is authorized and licensed by government agencies in most countries. International regulations fall under the jurisdiction of the International Telecommunications Union (ITU). The European Telecommunications Standards Institute (ETSI) produces standards and regulations for telecommunications in the European region. How the spectrum is distributed among agencies is country specific. In all cases, a license to operate radio equipment is required and must be applied for with the appropriate governing body. The license is granted to operate on a particular frequency, or set of frequencies, with specific eligibility rules that must be met.

2.1.2 Pi/4-DQPSK Modulation A radio transmitter sends signaling across at a particular carrier frequency. To deliver intelligible traffic across this carrier, the radio transmitter modulates outbound traffic with the carrier signal. The receiver then demodulates the traffic from the carrier signal. The popular forms of modulation are amplitude modulation, frequency modulation, and phase modulation. The Dimetra IP system uses pi/4-Differential Quadrature Phase Shift Keying (pi/4-DQPSK) modulation. This modulation method uses phase shifts in the transmit frequency to reflect different digital values. As shown in the figure below, pi/4-DQPSK modulation uses eight separate carrier phases. Up to four possible phase shifts can be made from any phase point. Each possible shift in phase is assigned a two-digit binary value (00, 01, 10, 11). This is an improvement over many other phase shift keying methods which only provide a single-digit binary value for each phase shift. The phase shift example shows a transmission shift from phase 0 (in phase) to 3pi/4. The receiver would recognize this shift and declare the received value as 01. The next phase shift shown is from 3pi/4 to pi/2. The receiver would recognize this shift as a binary value of 10. Each point offers four possible phase shifts for the next transmission.

2-2

68015000701-C - October 2013

2.1.3 ACELP Voice Compression

Figure 2-2

Pi/4-DQPSK Modulation

2.1.3 ACELP Voice Compression Voice signaling must be compressed to maintain the high rates of traffic flow. The Dimetra IP system and its radios use the Algebraic Code Excited Linear Prediction (ACELP) compression method, according to the TETRA standard. Most voice compression methods are similar. The analog audio is first converted into some form of electronic or digital signaling, such as pulse code modulation (PCM). Any silence or redundant data is then noted and eliminated. Any remaining data is compared to a codebook. Each chunk of the data is replaced by an index number from the codebook. The receiver then receives the data, looks up the index numbers from its codebook, and reconstructs the data. The ACELP compression method uses voice prediction algorithms and filters, along with its own particular codebook, which allows quality audio to be synthesized in as little as 8 kbps. As shown in figure below, the radio processes 30 msec blocks of speech. The final compressed signal is placed in a TDMA timeslot for transmission.

68015000701-C - October 2013

2-3

System Overview

Figure 2-3

ACELP Voice Compression

2.1.4 Time Division Multiple Access The Dimetra base stations and radios use Time Division Multiple Access (TDMA). Each carrier signal is divided into four timeslots, creating four channels for each 25kHz carrier.

2.1.4.1 TDMA for Dimetra IP Base Stations Each base station can send a continuous stream of traffic for all four time slots. Since each base station is full-duplex, it is able to send and receive traffic simultaneously on its transmit and receive channels. As shown in the figure below, the first channel on the first base station is typically configured as the control channel. All other channels at the site (base stations 2-8) are configured as traffic channels or packet data channels as required. The first channel on base stations 2-4, however, are also configured with control channel capability, allowing any one of them to operate as a control channel if the primary control channel fails. The figure shows the typical channel configurations made for a site with up to eight base radios. Figure 2-4

2-4

Time Division Multiple Access - Base Stations

68015000701-C - October 2013

2.1.4.2 TDMA for Dimetra IP Radios

2.1.4.2 TDMA for Dimetra IP Radios Radios only operate on a single channel at any one time to send or receive traffic. Since the radios do not have true full-duplex capability, the radio switches between the transmit and receive channels to simulate full-duplex capability for telephone interconnect calls and full-duplex individual calls. The transmit and receive time slots are offset by two slots to accommodate this switching and to allow the radio to both send and receive traffic within each time frame. Figure 2-5

Time Division Multiple Access - Radio (Full-Duplex Operation)

2.2 Network Technology The Dimetra IP system is based on various networking technologies and architectures.

2.2.1 Local Area Network A Local Area Network (LAN) is a data communications system designed to link computers and peripheral devices such as printers and modems. LAN cabling has a limited usable distance of up to 100 m (329 ft) and is best used within a building or campus environment. The advantage of using a LAN is that users can share peripheral devices connected to the LAN instead of having those devices attached to each computer. Network users can also share information stored in the network server, such as databases and programs. In addition, network users can communicate with each other through messaging or email.

2.2.1.1 Ethernet Technology Ethernet technology refers to a LAN used to connect computers and peripheral devices (such as printers, modems) so they can be shared by users of the network. Originally developed to run at 10 Mbps, Ethernet networks can now run at 100 Mbps. Ethernet can use twisted pair, coaxial, or fiber optic cabling with BNC, RJ-45, or fiber optic connectors. The Institute of Electrical and Electronic Engineers (IEEE) created the 802.3 standard for the operation of 10 Mbps networks. There are various types of 802.3 standard, based on the type of cabling used: • 10Base-5 - Thick Ethernet • 10Base-2 - Thin Ethernet • 10Base-T - Twisted pair Ethernet • 10Base-FL - Fiber Optics

68015000701-C - October 2013

2-5

System Overview

Ethernet accesses data using Carrier Sense Multiple Access with Collision Detection (CSMA/CD). This method allows multiple users to access the network through a common cable. All devices attached to the network check for transmissions in progress, signals are checked at the start of transmission and during transmission. Signals are sent if no other transmission is detected; otherwise, the transmission is delayed. Collision detection is applied when two or more devices transmit at the same time. A device knows if a collision occurred when it does not receive its own transmission back. Each device stops transmission and attempts to retransmit after waiting a certain amount of time, which is different for each device and determined by an algorithm.

2.2.1.2 Star Topology The LAN topology most frequently used in Dimetra IP System is the star topology, where the end points on a network are connected to a common central device by point-to-point links. The information arriving at the common device is broadcast to all the end point devices; each device is responsible for determining whether the information is intended for it or not. Characteristics of the star topology include: • Twisted pair cable is used for the links between the central and end devices. • Link isolation is used-if a fault occurs on one link, the other links remain unaffected. • A switch serves as the central device. • The end devices share the available bandwidth.

2.2.1.3 10Base-T and 100Base-T 10Base-T Ethernet uses shielded or unshielded twisted pair cabling. The Dimetra IP system is installed with shielded twisted pair cabling (STP) to provide additional protection against interference. The following list demonstrates how the term 10Base-T is broken down: • 10 = 10 Megabits per second (Mbps) operation • Base = Baseband operation • T = Twisted pair cable used for network connections The Network Interface Card (NIC) performs the functions of a transceiver so that no external transceiver is needed for base stations. 10Base-T is used in a star topology configuration and thus requires the use of a hub or concentrator. The hub serves as a central switching station, controlling the incoming and outgoing signals. When using the star topology, if a station goes down it does not affect the rest of the network. Typically, an RJ-45 connector is found at each end of the UTP cabling. Pins 1 and 2 transmit data, pins 3 and 6 receive data, the other pins are not used. 100Base-T Ethernet, also called fast Ethernet, is an upgraded standard for connecting computers into a LAN. It works just like 10Base-T Ethernet except that it can transfer data at a peak rate of 100 Mbps. 10/100Base-T networks installed in Dimetra IP systems use shielded twisted pair cable rather than the more common unshielded twisted pair (UTP) cable. Category 5 cabling is required for the Dimetra IP system.

2.2.1.4 Virtual LANs The use of intelligent switches instead of passive hubs to form Ethernet networks permits the use of Virtual LAN (VLAN) technology. With VLAN technology, a network designer or network administrator can form Virtual Ethernet segments. In a conventional Ethernet LAN, a group of communicating stations were physically connected to a shared hub or a shared cable segment. All members of the group needed to be within 100 cable meters of that hub of the group. If one of the group members had to move to a new location, cabling changes would have to be made to accommodate the move.

2-6

68015000701-C - October 2013

2.2.1.5 Switched Ethernet

VLAN technology allows a system administrator to assign each port of a switch to members of different Ethernet segments. The MSOs in a Dimetra IP system use switches that support VLAN technology in an extended stackable configuration. The use of intelligent switches instead of passive hubs to form Ethernet networks permits the use of Virtual LAN (VLAN) technology, IEEE 801.2Q.

2.2.1.5 Switched Ethernet Switched Ethernet is a 10Base-T or 100Base-T system in which all devices are connected to a central distribution point through their own cable. With switched Ethernet, the central, passive hubs used to form conventional core LAN switches are replaced with intelligent switches. The switches allow each sending computer to be temporarily directly connected to a single receiving computer. The switch acts as the central point of a star topology network. Therefore, the two computers do not experience collisions, and the full bandwidth of the transmission medium is available to any two stations that wish to communicate. Switched Ethernet technologies are used to allow equipment to communicate within a zone. The system uses LAN transmission to handle the flow of intrazone data. It also uses Wide Area Network (WAN) transmission to handle the flow of interzone data. Three basic types of information are exchanged in the system: voice, call control, and network management traffic. Network management and control information must be exchanged between devices installed within each individual zone, and between devices installed in different zones. Ethernet and Frame Relay are the primary communication technologies used to implement high-speed exchanges of management, control, and voice traffic among the various devices within an individual zone. Routers are used to implement high-level transport connections between network nodes in the system. Routers make the LAN connections and WAN transmission facilities transparent to the network nodes that may be communicating either within the same zone or between one zone and another. Routers also allow alternate paths to be implemented between interconnected equipment to permit the system to continue operating should specific physical links fail.

2.2.2 Wide Area Network The three types of WAN technologies used are: leased lines (point to point), packet-switched, and circuit-switched. • Leased lines: Leased lines provide a dedicated single path through an external provider from one location to another. It is possible to use either E1 or Ethernet (see 2.2.4 Ethernet Site Links, page 2-10). Speeds range from 56 kbps to 2.048 Mbps in case of E1. In case of Ethernet the speeds vary depending on the provider. Leased lines provide dedicated service and no call setup time, but the bandwidth is not flexible. A 4-wire analog leased line provides slower speeds, generally up to 33.6 kbps. • Packet-switched networks: Packet-switched networks break messages apart into packets and tag each packet with source and destination addresses. Packet-switching has several advantages: – Packets can be routed around network problems – They can maximize link efficiency by making optimal use of bandwidth – They can be more cost effective than leased lines. Frame relay switching provides high-speed packet-switching over Permanent Virtual Circuits (PVCs) referenced by Data Link Connection Identifiers. Local Management Interface (LMI) extensions provide additional management capability. Frame relay includes a cyclic redundancy check (CRC) algorithm that detects corrupted bits. Any needed retransmission is performed at higher protocol layers such as TCP. • Circuit-switching:Circuit-switching provides a dedicated path between a sender and receiver for the duration of the communication. The advantages of the circuit-switched networks are dedicated circuits for the call and customers do not pay for idle bandwidth. Disadvantages are call setup time and potential

68015000701-C - October 2013

2-7

System Overview

under-utilization of the communication channel. Circuit-switching is useful for short duration transmissions, for feeders to main sites or for backup/disaster recovery situations.

2.2.2.1 E1 Carrier An E1 carrier is a telecommunications facility designed to carry digital information at a bit rate of 2.048 Mbps. In conventional telecommunications, the most common use for an E1 carrier is to connect central offices within an individual telephone company. Telephone companies also lease E1 carriers to their customers for their own private purposes. Most systems use E1 circuits to transmit digitized voice, management, and control traffic between zones. The Frame Relay protocols provide the means for exchanging information over the E1 communication facilities that connect remote zones. Various types of transmission media can be used in implementing a private E1 facility, such as various types of privately installed cabling or point-to-point microwave circuits. An E1 circuit is divided into 32 time slots, each of which implements a separate communication channel that can support a bit rate of 64,000 bps. Each of these individual channels is referred to as a Digital Signal Level zero (DS0) channel. The term framing refers to the order in which user bits and other information is transmitted over a physical transmission medium. An E1 frame comprises a total of 256 bits. Each of the 32 inputs is assigned a fixed time slot; the E1 uses a time-division multiplexing technique to divide the capacity of the carrier into 32 channels. The framing bit is used to create a pattern to help synchronize the equipment. The figure below illustrates the format of the E1 transmission frame. Figure 2-6

E1 Carrier

2.2.2.2 X.21 Link The X.21 link provides synchronous serial communications between the Data Terminal Equipment (DTE) of the customer and the Data Communication Equipment (DCE) of the carrier. The X.21 interface in a Dimetra system operates in full-duplex mode at speeds from 64 kbps to more than 360 kbps. All the signaling in the X.21 link is balanced, meaning that positive and negative pairs of signaling are always transferred together. The service provider supplies a synchronization clocking signal for the X.21 link.

CWR does not support the X.21 link. X.21 links can be used in the Dimetra IP system to support site links to BTS sites and control sites. The Dimetra IP system uses a 15-pin V.11 physical interface for connection to X.21 links.

2-8

68015000701-C - October 2013

2.2.2.3 Frame Relay

2.2.2.3 Frame Relay Frame Relay is a simplified form of connection-based, packet-switching service in which synchronous frames of data are routed to destinations indicated on the header information. Frame Relay assumes an error-free physical link and therefore does not guarantee data integrity. Error detection and correction responsibility is left with the end devices. Frame Relay uses the synchronous High-level Data Link Control (HDLC) frame format up to 4096 octets in length. Each frame contains a start flag, two octets that contain the information required for multiplexing across the link, the data information (payload), two octets generated by a Cyclic Redundancy Check (CRC) of the rest of the octets between the flags, and the end flag. Permanent Virtual Circuits (PVCs) are used to form a connection between any two devices attached to a Frame Relay cloud. Virtual circuits are logical, bidirectional, end-to-end connections that appear to the user as dedicated links. Each PVC is given a unique number on each physical circuit along the path between the two devices. This unique number is called a Data Link Connection Identifier (DLCI). The DLCI is automatically changed to the PVC number of the next physical circuit as it passes through each switch along the path. A DLCI is different from a network address in that it identifies a circuit in both directions, not a particular endpoint. A frame contains only one DLCI, not a source and destination. In general, the only DLCI numbers you see are those numbers assigned to the physical circuits on the perimeter of the Frame Relay cloud. DLCIs only have local significance and represent end-to-end virtual connections that have a permanently configured switching path to a certain destination. Thus, by having a system with several DLCIs configured, you can communicate simultaneously with several different sites.

2.2.3 Cooperative WAN Routing (CWR) The Motorola Cooperative WAN Routing (CWR) solution offers simple, reliable, passive relay panels controlled directly from the routers. In multizone systems, the routers are configured in pairs to provide path redundancy for audio and control packets. With CWR, the routers work to control an external relay panel to switch a group of 12 non-redundant E1 links between the two routers. One router is always considered as the "Active" router and the other router is considered as the "Inactive" router. Each router can be provisioned with two 12-port E1 modules, providing up to 24 E1 link terminations per router pair. CWR interfaces the master site in one zone to Radio Frequency (RF) sites, dispatch sites, and other zones. Frame relay Permanent Virtual Circuits (PVCs) are set up on all intrazone links. When Multilink Frame Relay (MFR) is used for higher bandwidth requirements, Constituent Virtual Circuits (CVCs) and Aggregated Virtual Circuit (AVCs) are also configured. The interzone links use MFR to bundle multiple E1 links together providing one logical link. E1s are configured as CVCs then, as one logical AVC. Multiple E1s are required between the zones that have physical connectivity.

68015000701-C - October 2013

2-9

System Overview

Figure 2-7

Cooperative WAN Routing - Example

2.2.4 Ethernet Site Links The ESL feature provides a means to establish Ethernet connections of three types: • Base Station links (single and redundant) • Inter-zone links • Remote control site links terminated at non-redundant control site routers

2-10

68015000701-C - October 2013

2.2.4 Ethernet Site Links

Ethernet links are supported over a Layer 2 or Layer 3 of the GBN (Ground Based Network). Each Ethernet link terminated at the Mobile Switching Office (MSO) is represented by an IP tunnel terminated at MSO routers. IP tunnels at the zone core are implemented either as all encrypted IPSec tunnels, or all unencrypted IPIP tunnels. A pair of backhaul switches per MSO are used to aggregate the IPSec and IPIP tunnels for site links and inter-MSO links. Figure 2-8

Ethernet Site Links- Example

Ethernet routers support either encrypted or unencrypted tunnels, however a mixed configuration of encrypted and unencrypted tunnels on the same router is not supported. When a zone core has a mixed configuration of encrypted and unencrypted tunnels, at least two pairs of Ethernet routers are required. One pair is configured to terminate the encrypted tunnels, and the other one is configured to terminate the unencrypted tunnels. Zone core routers with Ethernet-based WAN interfaces are always deployed in pairs. The primary router is connected to the primary backhaul switch and terminates the primary Ethernet links, and the secondary router is connected to the secondary backhaul switch and terminates the secondary Ethernet link. The Ethernet Site Links can be additionally protected by adding Backhaul Firewalls at the Zone core and at the remote control sites.

68015000701-C - October 2013

2-11

System Overview

2.3 Digital Motorola Enhanced Trunked Radio (Dimetra) 2.3.1 Dimetra IP System Components The basic components of the Dimetra IP system include: • Radios (portable or mobile) • Sites (Mobile Switching Office, control sites, and BTS sites) • Zones (composed of multiple sites) • Clusters (composed of multiple zones) • System (single zone, cluster or multizones) The Dimetra IP system distributes the call processing load between the zone or zones that comprise the system. User configuration information also is shared among the zones. Each zone has a Local Area Network (LAN). The LANs are interconnected through a high-speed transport network to form a Wide Area Network (WAN). The WAN allows user configuration information, call processing information, and audio to be conveyed throughout the system. Each zone is responsible for managing its own elements. This includes configuring the physical infrastructure, managing mobility within the zone, and processing calls within the zone. Some call features operate only within a zone, so they are defined as zone level functions.

2.3.2 Dimetra IP System Core At the centre of the Dimetra IP system is a transport core designed to carry the system applications. This transport core uses several network technologies to cover the needs of the communications system. The goal of the transport core is to create a large system solution that meets the following characteristics: • Scalable Platform: The transport core supports a number of zones/sites per system. Multizone systems are formed with max 1 cluster, containing up to 4 zones. • Digital only platform that supports Algebraic Code Excited Linear Prediction (ACELP) for voice transmission. • The systems support the operation of IP based consoles in a packet-based environment. • The transport core provides the ability to transparently transport vocoded audio. Once voice is vocoded, the digital information is passed all the way through the network with no conversions required. Conversion to the original audio format is required only at the destination receiver. The Dimetra IP system supports air interface encryption. • The transport core consists of a packet transportation network that is not concerned with what is contained in the packets. The Dimetra IP system includes an Internet Protocol (IP) based infrastructure that provides IP multicast technology for dispatch services and RF sites. This technology allows group calls to be set up, processed, and torn down easily in a packet environment, replacing circuit switched methods.

2-12

68015000701-C - October 2013

2.3.3 Unicast Routing

2.3.3 Unicast Routing Unicast routing involves sending one or more packets from a source device to a destination across the network. The source encapsulates its data in a packet and places a destination address in the header of the packet. Network transport devices, such as routers and switches, observe the destination address for incoming packets and direct the packets toward their destination. The Dimetra IP network uses various routing protocols for transporting packets. The figure below shows a source sending traffic across a network to a single destination Figure 2-9

Unicast Routing

D

S Most datagrams sent across a typical network use unicast messaging to deliver information between one point and another.

2.3.4 Multicast Routing Multicast routing involves a point-to-multipoint routing of traffic. Multicast differs from unicast, where packets are routed from one point to another. Multicast also differs from broadcast, where packets are sent from a single source to all the devices on the network. In a basic multicast operation, a multicast-capable router receives Internet Group Management Protocol (IGMP) to join a specific multicast group. The router, also known as a Rendezvous Point (RP), collects all the IGMP join messages to identify all the nodes that is receiving the multicast traffic. The router builds a multicast tree which includes all the recipients. When the source starts to send its packets, the RP receives the packets, replicates each packet, and sends the replicated packets to each device that has joined the multicast tree. The figure shows a source sending traffic to the RP, with the RP multicasting the traffic to multiple destinations.

68015000701-C - October 2013

2-13

System Overview

Figure 2-10

Multicast Routing

D

D

D

RP

S Since talkgroup and announcement calls involve routing of audio between a single source and multiple recipients, multicast routing works well with group-based audio routing. Multicast allows the transmitting radio audio to be distributed to the appropriate sites by the RP router. Without multicast, the source would have to separately address multiple copies of each packet to each of the individual recipients across the network. In the Dimetra IP network, all the devices associated with a particular call are instructed to join a specific multicast group. After the join messages are received from the devices, the RP propagates the multicast traffic to the appropriate devices, sites, and zone(s) that are involved in the call and that have sent their join message. The RP is typically defined as the router located near the receiving end of the multicast traffic, rather than a router located near the source of the traffic. This allows greater efficiency of network resources, since the higher volumes of multicast traffic is only spread across the receiving end of the network, rather than spreading all the replicated packets directly from the source location across the entire network. Multicast trees for audio traffic are set up as requested and are present only for the duration of the multicast call. A range of class-D IP addresses (addresses beginning with 224 -239) are designated as multicast group addresses.

2.3.5 Call Model When and where to use: The main purpose of a Dimetra IP system is to provide voice services to radios and dispatchers throughout the system. The process below describes how a talkgroup call is serviced by the system. See Figure 2-11 Call Processing - Multicast Routing of Traffic in conjunction with the following description of a basic multicast call example.

Process Steps

2-14

68015000701-C - October 2013

2.3.5 Call Model

1

A radio user presses the PTT button to talk to other users in the talkgroup. The radio transmits a Call Request on the RF control channel at the site. The Call Request is received by the control channel and forwarded to the site LAN. Before placing the Call Request packet on the site Ethernet LAN, the base station encapsulates the Call Request message in a User Datagram Protocol (UDP/IP) datagram with the destination IP address of the Zone Controller.

UDP is a transport layer protocol that resides on top of the IP. UDP provides a transaction-oriented, best-effort delivery service. IP is the Internet layer protocol tasked with defining how data is transferred across the network, how devices are addressed, and how to route data appropriately. IP defines a universal/global addressing method. It defines how to fragment, transport, and reassemble data packets 2

The IP packet network routes the Call Request packet to the Zone Controller. Upon receiving the Call Request message, the Zone Controller checks an internal database to determine the location of all members in the requested talkgroup (such as RF sites and remote dispatch site locations). The Zone Controller then assigns a multicast group address to the call and sends the assigned multicast group address to all the participating RF sites and the consoles at the MSO. This message is referred to as a Call Grant message and is sent in an IP datagram.

3

Upon receiving the Call Grant message, the RF and dispatch sites extract the IP multicast address from the Call Grant. The assigned traffic channels at RF sites and the consoles at the MSO generate a group Join message. The group Join message is an IP control packet.

4

Upon receiving the IP group Join message, the TETRA Site Controllers and dispatch site routers communicate with RP routers in the system to set up an IP multicast distribution tree. This tree is used to distribute voice payload traffic to all sites participating in the call.

5

The radio begins transmitting vocoded audio on the assigned RF traffic channel at its site. The audio is received by the traffic channel and is placed in an IP datagram destined to the assigned IP multicast address (as assigned in the Call Grant). The IP multicast packet is placed on the LAN.

6

The IP Multicast audio stream is distributed to all the RF and dispatch sites through the Rendezvous Point router and IP multicast tree.

7

When the first user dekeys and a second member of the talkgroup transmits while the call is still active (call hang time has not expired), the same multicast tree is used. Vocoded audio is received by the traffic channel at the new source site and placed in an IP packet destined for the Rendezvous Point router of the group. The IP packet flows down the same IP multicast tree generated earlier by the routers.

8

When the call is over (expiration of the message timer), the sites (RF or dispatch) generate an IP group Leave message. The Leave messages cause the multicast tree to be taken down.

The preferred mode of operation for a Dimetra IP system is message trunking with PTT-ID. This parameter is programmed in the system, through the User Configuration Manager (UCM), as message trunking, and in the radios, through their programming software, as PTT-ID.

68015000701-C - October 2013

2-15

System Overview

Figure 2-11

Call Processing - Multicast Routing of Traffic

2.3.6 Traffic Planes There are a number of logical traffic planes set up in the transport network. These are used to describe the communications paths which exist within the network and traffic types carried over those paths. The following traffic planes are the most important ones within Dimetra IP systems: • 2.3.6.1 Voice Control Plane, page 2-17 • 2.3.6.2 Audio Plane, page 2-17 • 2.3.6.3 Data Plane, page 2-17 • 2.3.6.4 Network Management Plane, page 2-17

2-16

68015000701-C - October 2013

2.3.6.1 Voice Control Plane

2.3.6.1 Voice Control Plane The traffic between the Zone Controller and the RF sites within a zone, and between Zone Controllers in different zones is called Voice Control traffic; the logical plane used to transport this information is called the Voice Control Plane. Voice Control traffic is responsible for setting up the audio path between the transmitting site and the receiving site or sites. The Zone Controller, through the voice control plane, receives talkgroup requests and sends messages to appropriate sites, assigning an IP multicast group address to use for the call. Control communication from the Zone Controller to the RF sites is accomplished using multicast; unicast is used for transmissions from the RF sites back to the Zone Controller.

2.3.6.2 Audio Plane The Audio Plane is made up of the unicast routes and multicast trees setup by voice control. Multicast is used to carry audio packets for all call types (group calls, private calls, telephone interconnect calls) between radios in a system (both intrazone and interzone).

2.3.6.3 Data Plane The Data Plane is made up of the unicast and multicast trees that are used as communication paths between the Zone Controller and the RNG for the different data services (packet data, short data) between radios in a system (both intrazone and interzone).

2.3.6.4 Network Management Plane The Network Management Plane carries all of the unicast network management traffic between the network devices (for example, routers and switches), the network management servers of the Operations Support System and radios. Dimetra IP systems use the same physical link for traffic from all three planes (See figure below). Figure 2-12

68015000701-C - October 2013

Dimetra IP System Logical Traffic Planes

2-17

System Overview

Traffic in the figure above denotes three types of traffic: • Audio traffic • Data traffic • Control traffic

2.4 End-to-End Secure Communication The Motorola secure voice and data solution enhances the encryption and security of two-way radio communication. When encryption is used to protect digital traffic, the transsmitting device uses an algorithm and an encryption key to transform clear digital messaging into an encrypted code. Modern algorithms do not just scramble messages, but convert messages bit-by-bit into an entirely different encrypted form. The figure below shows the basic process used for secure communication. The sender uses a particular key and algorithm to encrypt clear traffic. The traffic then passes across the medium in an encrypted form. The recipient then uses the same key and algorithm to decrypt the traffic. Figure 2-13

Basic Secure Voice Operation

Encryption protects the information from being deciphered and understood by anyone outside the system. Without the proper algorithm and the encryption key, any intercepted traffic is received as a bunch of garbled digital bits wrapped in packets. If there is no encryption, hobbyists or hostile groups can intercept and decipher traffic. The Motorola secure voice and data solution uses sophisticated algorithms to protect voice traffic. Depending on the algorithm used, a radio can be provisioned with a large number of keys. By rotating keys on a regular basis, it would be nearly impossible for an interceptor to find the correct key and decrypt the traffic. The figure below shows basic secure voice operation between two radios. The transmitting radio encrypts clear voice using a particular key (CG456) and transmits the encrypted voice to the transport network. The secure voice traffic is routed over the network while remaining in an encrypted form, and is transmitted to its intended recipient. The receiver radio then uses the same key (CG456) to decrypt the traffic and provide clear voice to the user.

2-18

68015000701-C - October 2013

2.4 End-to-End Secure Communication

Figure 2-14

Voice Transmission

Compared to Air Interface Encryption (AIE), the secure voice solution adds an additional level of confidentiality to the speech traffic and is an enhancement to the system. This service does not replace any of the other standard TETRA security mechanisms, and can coexist overlaid on AIE. The main difference between AIE and secure voice is that secure voice provides voice encryption all the way from one radio to another. AIE only provides security for messages between the base station and the radios and it does not provide any security for messages that exist within the infrastructure, whereas secure voice provides security between the end users, even within the infrastructure. Apart from voice, Motorola has also developed a solution for delivering encrypted data. End-to-End Encryption for Short Data and Packet Data (E2EE SD/PD) is an overlay service that allows secure (digitally encrypted) data communications between radios and data applications in the customer enterprise network (CEN). Encryption/decryption services are provided by the system endpoints: Packet Data Encryption Gateway (PDEG), Mobile Data Encryption Gateway (MDEG), Short Data Encryption Gateway (SDEG) and radios, so communication remains secure between the source and the destination. Secure data is a supplementary service located on a customer premises (the Switching and Managing (SwMI) infrastructure is not encryption aware). The solution is based on the current key management solution, in other words, a symmetrical key exchanged with the KMF. Digital encryption converts the digital data, using an encryption key together with an encryption algorithm, into an encrypted message which is then transmitted. Only an endpoint that shares the same encryption key and encryption algorithm is able to decrypt the transmission successfully. Other devices that do not have the proper key are not able to receive intelligible information. For more information see the Secure Voice, Data and Key Management manual.

68015000701-C - October 2013

2-19

3

Dimetra IP System Components

3.1 Mobile Switching Office (MSO) All the components that communicate over Ethernet are connected through multiple core LAN switches . These switches provide two separate internal LANs that are integrated to provide redundant links for critical network traffic. A Mobile Switching Office is a physical location that contains all the components necessary for controlling calls within a zone and for communicating with other zones to manage interzone calls (calls that go between zones). In addition, the MSOs provide the hardware and software components that are used for network management and system configuration.

One of the master sites (which are physical locations in Dimetra system containing one or more sets of zone control equipment) in a multizone system is generally designated as the cluster MSO. This MSO typically includes the cluster-level servers, including the combined User Configuration Server (UCS).

3.1.1 System Server The System Server is a platform on which most Dimetra IP servers are installed. The platform is a HP ProLiant DL360p Gen8 server with Red Hat Enterprise Linux 6.x, which provides a virtual environment, which allows to install Windows or RHEL Linux servers (containers, VPSs). These virtual servers, from the networking perspective, behave like separate devices. They are group on various physical servers, as described in 3.1.1.1 Types of the System Server, page 3-2. Figure 3-1

HP DL360p Gen8 Server Front View

68015000701-C - October 2013

3-1

System Overview

3.1.1.1 Types of the System Server The table below presents possible configurations, in which the server can be deployed in the system. Table 3-1

Types of System Server (constellations)

System Server Type

List of Entities

Primary Zone Server

Zone Controller, Upgrade Install Server

Secondary Zone Server

Redundant Zone Controller, Upgrade Install Server

Primary Management Server

User Configuration Server, Zone Database Server, Zone Statistics Server, Unified Event Manager, Air Traffic Router, Enhanced Authentication Centre

Primary Data Server

Short Data Router, Packet Data Router, Radio Network Gateway

Secondary Data Server

Short Data Router

MTIG-IP01

MTIG-IP01

MTIG-IP02

MTIG-IP02

MTIG-E101

MTIG-E101

MTIG-E102

MTIG-E102

3.1.2 Zone Controller The Zone Controller is a redundant server application that provides call processing for wide area radio communications and telephone interconnect calls. Zone Controller is responsible for: • Processing and generation of call-related signaling. • Control and allocation of air-interface resources. • Processing radio registration and group affiliations. • Control and allocation of Motorola Telephone Interconnect Gateway (MTIG) resources. • Collection, sharing, and arbitration registration information with other Zone Controllers in multizone systems. • Authentication at radio registration. Two redundant Zone Controllers are connected to the network through the core LAN switch . This switch provides connections over two separate virtual LANs, used to switch system resources between the Zone Controllers and provide high availability for call processing and resource management. While both Zone Controllers are powered and enabled at the same time, only one Zone Controller is actively participating in call processing tasks at any one time. A Zone Controller may have a redundant state of either active or standby. The Zone Controller responsible for call processing is in the active state. The Zone Controller that is not actively processing calls in the zone is in the standby state. The standby controller remains in standby mode until the active Zone Controller fails or until a switchover command is initiated. System information that is necessary for call processing is downloaded to both Zone Controllers. The Zone Controllers include hardware for storing data, controlling zone activities, and communicating with zone resources. In a non-redundant system the Zone Controller is hosted on the same physical server platform as the NM servers and in a redundant system one Zone Controller is hosted on the same physical server platform as the NM servers and the other Zone Controller on a separate server platform.

3-2

68015000701-C - October 2013

3.1.3 Network Management Subsystem

3.1.3 Network Management Subsystem The Network Management Subsystem is based on the client/server networking model. The NMS meshes seamlessly and scales with the other infrastructure elements across the packet-switched network. The network management subsystem uses the Microsoft® Windows operating system as the platform for the client personal computer (PC) workstation applications. Network management is a set of software tools that support the management of a complex radio communications system and its component parts, which include radios, computers, and inter-networking components. Network management tools support the maximization of resource availability while helping to minimize system downtime and maintenance costs. Network Management Subsystem

MTIG-E1 Server 1

Primary Management Server

MTIG-IP Server 1 Primary Zone Server

Primary Data Server GPS

To PABX

Figure 3-2

Secondary Zone Server

NTS

EC

KMF

NM Client

User Configuration Server Core LAN Switch 1&2 Air Traffic Router Zone Database Server Unified Event Manager MCC7500 Voice Logging Replay Station AIS Zone Statistics Server

E1 CGE1

Router

GGSN1

VPN Router

CWR Panel

E1 - GBN

BTS Remote Control Zone Other Zone

68015000701-C - October 2013

Cus tomer Network

Internet

VPN Client Mutually exclusive

3-3

System Overview

The server components of the Network Management subsystem reside on the Primary Management Server and include User Configuration Server (UCS), Zone Database Server (ZDS), Zone Statistics Server (ZSS), Unified Event Manager (UEM), System Statistics Server (SSS), and Air Traffic Router (ATR). Network management provides the tools, commonly known as FCAPS, for fault, configuration, accounting performance and security management. The network management functions in Dimetra IP are distributed across several applications and servers that are installed in one of three configurations: system, zone, and remote. The configurations are designated by the name Operations Support Systems (OSS). The individual network management building blocks of the Zone OSS and Cluster OSS can be divided into two categories: • Private Radio Network Management (PRNM) client applications such as: – ZoneWatch – Radio Control Manager (RCM) – Zone Configuration Manager (ZCM) – User Configuration Manager (UCM) – Radio Control Manager Reports (RCM Reports) – Historical Reports – Dynamic Reports – ATIA Log Viewer – Affiliation Display – Unified Event Manager (UEM) – Software Download Manager • Network Transport Management (NTM) client applications. – Network Configuration Tool Express (NCT) – Trivial File Transfer Protocol (TFTP)

3.1.3.1 Network Management Servers The NM subsystem includes the server applications listed below. Zone Level Servers: • Zone Database Server (ZDS) • Air Traffic Router (ATR) Server • Zone Statistics Server (ZSS) • Unified Event Manager Server (UEM) Cluster Level Servers: • User Configuration Server (UCS) • Unified Event Manager Server (UEM) (optional) For more information on Zone Level Servers and Cluster Level Servers, see 7 Dimetra IP Network Management, page 7-1.

3-4

68015000701-C - October 2013

3.1.3.2 Operations Support Systems

3.1.3.2 Operations Support Systems Operations Support Systems (OSS) is a term used to specify the devices used to manage the system. This includes network management servers and clients. • Zone OSS: The Zone OSS refers to the network management system for a given Zone. The servers are always colocated with the MSO equipment. Examples are Zone Database Server (ZDS), Air Traffic Router (ATR), Zone Statistics Server (ZSS), and Unified Event Manager (UEM). • Cluster OSS: The Cluster OSS manages a cluster of up to four zones from a single location. To accomplish its task, the Cluster OSS must have a routed path to all supported zones. The Cluster OSS consists of the combined User Configuration Server (UCS), Unified Event Manager Server, and the Network Transport Performance Server.

3.1.3.2.1 Fault Management at the Zone Level A zone includes a workstation containing the Unified Event Manager and the traps and MIBs to the networking equipment. This integrated set of tools is the core application for fault and configuration management for a majority of the transport devices in the system and provides the following services: • The Unified Event Manager provides the topology map, alarm browser, and MIB browser interface. • The Unified Event Manager application adds network management tools and hierarchical topology maps specific to Motorola devices. • Traps and MIBs add fault and performance network management tools for the networking devices.

3.1.3.2.2 Configuration Management at the Zone Level Zone-level configuration management tools are available to configure all the devices in the zone. To the network management user, there is a single integrated interface for accessing configuration information for all devices in the zone. The network management clients, which have the NTMS installed allow users to navigate to configure any device in the network. The tools for configuration management include: • Telnet can be used to access the Command Line Interface (CLI) of the routers and core LAN switch. • A script on the Network Management Client (NM Client) is used to back up and restore the HP core LAN switch OS and configuration file.

3.1.3.2.3 Security Management at the Zone Level All network management applications have defined access privileges for each user. All the applications support password protection at a minimum. A single login allows the user to access all the network management applications for which they have access privileges without having to login to multiple applications. The exception is InfoVista®. All network management applications have defined access privileges for each user. All the applications support password protection at a minimum. A single login allows the user to access all the network management applications for which they have access privileges without having to login to multiple applications. The routers and switches have an independent login which is required if a user telnets to the device. NM includes features for setting user privileges and controlling their access to view and/or modify information contained in the configuration databases. Optional Agency Partitioning software allows a system administrator to assign access privileges to specific applications. These applications include Configuration Manager, Radio Control Manager, Historical Reports, and ZoneWatch. The administrator can grant or restrict user access to particular zones in the cluster.

68015000701-C - October 2013

3-5

System Overview

3.1.3.2.4 Network Management at the Cluster OSS The Cluster OSS acts as a cluster-level integration point. Therefore, the Cluster OSS consists of applications to manage cluster wide settings. InfoVista® with integrated MIBs from all networking devices collects detailed network performance information at each Cluster OSS. In addition, some configuration needs to be done at the device level to report information appropriately to either the zone applications, the cluster OSS applications, or both. For example, the trap destination and community string needs to be configured for each device.

3.1.3.2.5 Fault Management at the Cluster OSS One of the UEM servers in each cluster is configured to collect and present information from all zones in the cluster. This allows a network administrator to view all the alarm and status indicators for all the equipment in the entire cluster.

Clusterwide Fault Management on some systems may only refer to Dimetra Radio System managed objects and not necessarily IP devices (Routers, LAN Switches) depending on network configurations.

3.1.3.2.6 Configuration Management at the Cluster OSS The cluster wide settings are set through the User Configuration Manager (UCM) which includes all the settings for radio users, talkgroups/multigroups, network management users, cluster wide parameters, and ZoneWatch settings within the particular cluster. Each cluster has its own User Configuration Server (UCS) to centrally store the cluster parameters. Cluster configuration settings are distributed to appropriate equipment in each zone as required.

3.1.3.2.7 Security Management at the Zone and Cluster OSS All network management applications have defined access privileges for each user. All the applications support password protection at a minimum. A single login allows the user to access all the applications for which they have access privileges without having to login to multiple applications. However, this does not include applications, such as Command Line Interface (CLI), that are resident on the networking devices. Users must log on to the networking devices to run resident network management applications.

3.1.3.2.8 Multicluster Network Management A network management client can be configured to access zone-level and cluster-level applications in one or more clusters. This allows the client to launch individual PRNM or NTM applications to manage faults, configure parameters, or monitor performance for any zone or cluster in the system. For multicluster configuration management, a User Configuration Server API (UCS-API) is available in each cluster. Centralized data distribution is obtained by using the collection of available UCS-API’s in the system. A home zone map can then be downloaded from one cluster and uploaded to all other clusters. Likewise any necessary information (such as RF sites and call routes) can be distributed from one cluster to all other clusters. For multicluster fault management, the Dimetra system allows trap forwarding to a customer-supplied fault management system. This allows a centralized collection of traps throughout the system.

3-6

68015000701-C - October 2013

3.1.4 Data Subsystem

3.1.4 Data Subsystem The data subsystem enables users of the Dimetra infrastructure to send data files in various formats using packet data services, whilst the short data services enables distribution of short text messages between radios and/or consoles. The figure below shows the equipment that supports data services.

3.1.4.1 Data Gateway The Data Gateway supports packet data services (PDR), Short Data Transport Service (SDTS), and Alphanumeric Text Service (ATS). The Data Gateway performs registration services for packet data users, maintains user permissions and mobility information, and provides routing of traffic to the radio network or the GGSN router. Inbound packet data traffic is received at a site over a packet data channel and sent through the network to the Data Gateway. The Data Gateway changes the packet encapsulation, checks permissions for the user (as configured through User Configuration Manager), and tunnels the traffic to the GGSN router. The GGSN router then provides IP tunneling via a border router to the customer enterprise network. If authentication is supported at the customer enterprise network, then the appropriate challenge and response handshake information must be exchanged before packet data services are granted to the user. If DHCP services are used, then a DHCP server at the CEN assigns an IP address to the packet data user terminal equipment when a packet data session is requested. Radio Network Gateway (RNG) and Packet Data Router (PDR) are jointly called Packet Data Gateway (PDG).

3.1.4.1.1 Packet Data Router (PDR) The Packet Data Router (PDR) interfaces with the Gateway GPRS and provides encapsulation to tunnel traffic to the GGSN router. The PDR provides access control for packet data radios, according to UCM settings which are locally stored in a Packet Data Home Location Register (PD-HLR).

3.1.4.1.2 Radio Network Gateway (RNG) The radio network gateway (RNG) interfaces with the remote sites to handle inbound/outbound packet data traffic between the remote sites and the PDG. The RNG provides a logical connection to the sites, and provides encapsulation of traffic between the PDR and the remote sites. The RNG also communicates with the Zone Controller to maintain a Packet Data Visitor Location Register (PD-VLR).

3.1.4.1.3 Short Data Router (SDR) The short data router (SDR) supports Short Data Transport Service and Alphanumeric Text Service in the system. The SDR routes short data messages (up to 140 characters) across the network according to the TETRA Short Subscriber Identities for radio users (ISSIs) and talkgroups/multigroups (GSSIs) as defined in the User Configuration Manager. For short data messages to radios, the SDR directs the messages to the appropriate RF site. For short data messages to a fixed customer enterprise network, the SDR maps the TETRA addressing to an IP address and forwards the short data message to the host using IP. Short data routing may be point-to-point or point-to-multipoint (broadcast). Depending on the capacity requirements, a Dimetra IP system can have one SDR per cluster or one SDR per zone for up to three zones in a cluster.

68015000701-C - October 2013

3-7

System Overview

3.1.5 Telephone Interconnect Subsystem The Telephone Interconnect subsystem provides an interface between the Dimetra radio network and an external telephone network, allowing telephone interconnect calls to be made between Dimetra radios and the external telephone network. The external telephone network consists of either a PABX or the PSTN through a PABX. The Motorola Telephone Interconnect Gateway (MTIG) is the device which provides transcoding of audio traffic between ACELP and pulse code modulation (PCM) audio required by the external network. Also, the MTIG provides a gateway for the call control and setup/teardown instructions exchanged between a Zone Controller and an external network in order to handle telephone calls. Telephone interconnect paths are defined in the Zone Configuration Manager (ZCM). Additional telephone interconnect settings for individual radio users, along with other cluster wide settings for telephone interconnect services, are made through the User Configuration Manager (UCM). Telephone Interconnect Subsystem

MTIG-E1 Server 1

Primary Management Server

MTIG-IP Server 1 Primary Zone Server

Primary Data Server GPS

To PABX

Figure 3-3

Secondary Zone Server

NTS

EC Core LAN Switch 1&2 KMF

NM Client

CGE1

MCC7500

Voice Logging Replay Station

Router

AIS

GGSN1

VPN Router

CWR Panel

E1 - GBN

BTS Remote Control Zone Other Zone

3-8

Cus tomer Network

Internet

VPN Client Mutually exclusive

68015000701-C - October 2013

3.1.5.1 Motorola Telephone Interconnect Gateway

MTIG is a general term used for all types of Motorola Telephone Interconnect Gateways. In specific terms, we can indicate a relevant type of MTIG. MTIG-E1 is an MTIG that uses QSIG signaling towards the PABX. MTIG-IP is an MTIG that uses SIP signalling towards the PABX. MTIG-E1 and MTIG-IP are mutually exclusive within a zone, but not within a system.

3.1.5.1 Motorola Telephone Interconnect Gateway The MTIG operates under the direction of the Zone Controller to transcode audio between ACELP and A-law or Mu-law PCM and to route this audio between the IP network and the customer-supplied PABX. The MTIG also generates any required tones for telephone interconnect operation and provides a gateway path for the control signalling between the Zone Controller and the PABX. The Zone Controller communicates with the MTIG over the LAN to direct the setup and teardown of telephone interconnect call. See the Telephone Interconnect manual.

3.1.5.2 Echo Canceller The Echo Canceller suppresses any echo from the external network that would otherwise be directed to the radio during a telephone interconnect call. The Echo Canceller is placed where the IP and E1 lines meet. The Echo Canceller is the interface between the MTIG-E1 and the customer-supplied PABX. The Echo Canceller contains a dual E1 card which is able to support up to 60 traffic channels. One Echo Canceller per MTIG-E1 is used, with a capacity of two E1s. If required, only one E1 is configured in the MTIG-E1 and Echo Canceller boxes. For more information about MTIG solutions, see Telephone Interconnect manual.

3.1.5.3 Enhanced Telephone Gateway (ETG) The ETG is a standard PABX, which together with the call route functionality of the Dimetra system provides routing and interfacing capabilities to multiple external networks. These are typically larger networks, which are required to connect to multiple user organization PABXs as well as PSTN. For this type of networks an Enhanced Telephone Gateway (ETG) is required. The Dimetra system typically connects to the ETG, which again connects to the various external networks, that is, customer PABXs or PSTN. The system typically uses one PABX call route per customer PABX. The PABX call route only needs to be configured for the zone to which the PABX is connected, that is, where the customer organization users are defined and the PABX is physically connected through the ETG. The call route is automatically distributed to other zones allowing the call route to be addressed from any zone. For more detailed description of Telephone Interconnect Subsystem, see the Telephone Interconnect manual.

3.1.6 Provisioning and Authentication Centre The Dimetra IP system includes a Provisioning Centre (PrC) and Authentication Centre (AuC) when air interface encryption or authentication are installed on the network. The PrC is primarily responsible for storing and provisioning keys for the radios. The AuC is primarily responsible for storing and distributing necessary authentication and air interface encryption keys across the network to infrastructure devices.

3.1.6.1 Provisioning Centre (PrC) The Provisioning Centre (PrC) is responsible for provisioning authentication and air interface encryption keys to each radio supporting encryption or authentication. The PrC connects with a Key Variable Loader (KVL), which is a handheld device used to manually load keys into radios and other infrastructure equipment. The PrC keys are generated n the PrC or imported to the PrC and loaded into a KVL for distribution to radios.

68015000701-C - October 2013

3-9

System Overview

After a KVL loads keys into a radio, the radio sends a receipt or acknowledge message. When the KVL is connected with the PrC again, the acknowledge messages are loaded into the PrC and the successful status of the key loading is maintained by the PrC. The PrC also outputs authentication material and air interface encryption keys by CD to the Authentication Centre. The AuC securely stores and uses these keys for authentication and air interface encryption purposes. The Provisioning Centre is isolated from the network. It includes a client, database server, and PrC server all integrated into one chassis. The PrC runs the Windows 7 operating system and provides a user interface for key management operations. The PrC uses CryptR 2 device for encryption and decryption of the key material.

3.1.6.2 Clear Provisioning Centre (Clear PrC) The Clear Provisioning Centre (Clear PrC) provides Mobile Subscriber (radio) Authentication without TETRA Air Interface Encryption. Clear PrC thus offers secure Authentication and Provisioning in Dimetra networks operating with a clear non-encrypted TETRA Air Interface. The Clear PrC is a stand-alone computer.

3.1.6.3 Authentication Centre (AuC) The Authentication Centre provides authentication and air interface encryption key management for the cluster. The Authentication Centre is provisioned with both authentication keys and air interface encryption keys. The Authentication Centre also generates several other keys which are used for secure delivery of key material over the network. For authentication, the Authentication Centre distributes the appropriate authentication material to the Zone Controllers. The Zone Controllers then use the authentication material to challenge radios that try to register with the system. For air interface encryption, the AuC stores and distributes encryption keys over the network to the appropriate infrastructure equipment for encrypting and decrypting traffic. Depending on specific configuration, and the AuC server can reside either on the Primary Management Server or on a separate hardware platform. The Authentication Centre can operate as a separate device, or as Enhanced AuC, which combines the functionality of both AuC and PrC. Keys in the AuC are stored in an encrypted form. The AuC uses CryptR 2 device for for encryption and decryption of the key material. Any attempts to tamper with the tamper-proof hardware causes an alarm to be sent to Unified Event Manager and causes the master key encryption key to be erased. For more detailed description of Provisioning and Authentication Subsystem, see Authentication and Provisioning Subsystem manual.

3.1.7 Network Time Server (NTS) The Network Time Server (NTS) together with the Zone Database Server (ZDS) provide a timing reference to the Dimetra system. It acts as a Network Time Protocol (NTP) server providing a UTC time and date reference to all IP connected system elements (NTP clients) that support the Network Time Protocol (NTP). The figure below shows the SyncServer S300 with Rubidium oscillator from Symmetricom.

3-10

68015000701-C - October 2013

3.2 Network Transport Subsystem

Figure 3-4

Network Time Server

For more detailed description of Network Time Server, see the Network Time Server manual.

3.2 Network Transport Subsystem The transport core (see the diagrams below) at the MSO supports the logical and physical structure with the following components and functions, depending on whether E1 or Ethernet configuration is used:

68015000701-C - October 2013

3-11

System Overview

Transport Core with E1 Connections

MTIG-E1 Server 1

Primary Management Server

MTIG-IP Server 1 Primary Zone Server

Primary Data Server GPS

To PABX

Figure 3-5

Secondary Zone Server

NTS

EC Core LAN Switch 1&2 KMF

E1 CGE1

NM Client

E1 CGE2

MCC7500

Voice Logging Replay Station

Border Router

AIS

GGSN1

VPN Router

CWR Panel

E1 - GBN

BTS Remote Control Zone Other Zone

3-12

Cus tomer Network

Internet

VPN Client Mutually exclusive

68015000701-C - October 2013

3.2.1 Switches

Transport Core with Ethernet Connections

MTIG-E1 Server 1

Primary Management Server

MTIG-IP Server 1 Primary Zone Server

Primary Data Server GPS

To PABX

Figure 3-6

Secondary Zone Server

NTS

EC Core LAN Switch 1&2 KMF

NM Client

Eth CGE1

Eth CGE2

BH Switch 01

BH Switch 02

ESL - GBN

BTS Remote Control Zone Other Zone

MCC7500

Voice Logging Replay Station

Border Router

Cus tomer Network

AIS

GGSN1

VPN Router

Internet

VPN Client Mutually exclusive

3.2.1 Switches The following functional types of switches are available:

3.2.1.1 Core LAN Switch The core LAN switch provides the interface for all servers, clients, and routers to connect into the core network. To meet system availability requirements multiple core LAN switches are used. The core LAN switches have a Network Management system to provide proactive fault management.

68015000701-C - October 2013

3-13

System Overview

A virtual LAN is set up on each of the core LAN switches. The purpose of these as Transitional LANs (TLAN1 and TLAN2) is to carry traffic between the various core, gateway, and exit routers. The core, gateway and exit routers connect to both TLANs. If an Ethernet port fails, traffic is transferred to the remaining TLAN. The core LAN switch is the main Ethernet switch used to interconnect all the Ethernet interfaces for all servers, clients, and routers. Devices are physically connected into the switch in a way that provides the highest reliability.

3.2.1.2 Backhaul Switch Ethernet links are terminated at the Mobile Switching Office (MSO) using two backhaul switches. Colocated zones at the MSO share the same backhaul switches. In Geographical Redundant deployment, there is one backhaul switch in each location.

3.2.2 Routers The master site network transport functions in the Dimetra system are provided by S6000 router and GGM 8000 gateway.

3.2.2.1 Gateway GPRS Support Node The Gateway GPRS Support Node Router (GGSN) is a device that supports the tunneling of traffic between the Dimetra IP network and the supported customer enterprise network. One side of the GGSN router provides an interface to the Motorola Radio Network Infrastructure (RNI) while the other side of the GGSN router attaches to a peripheral network to interface with the border routers of the Customer Enterprise Network (CEN).

3.2.3 CWR Patch Panel The CWR patch panels provide the connection between the core and exit routers and the E1 WAN infrastructure. Core and exit routers are configured in pairs to provide path redundancy for audio and control packets. With CWR, the pair of routers work cooperatively to control the CWR patch panel, which switches a group of 12 non-redundant E1 links between the two routers. Each pair of CWR core or exit routers is connected to a CWR patch panel via high-density E1 ports. The CWR patch panel’s RJ-48C connectors provide the connection to the E1 network. Each CWR patch panel provides the following connectors: • Two sets of two 62-pin high-density E1 connectors, each of which supports up to 12 E1 relays, for a total of up to 24 relays for each CWR patch panel. Core and exit routers are connected via the CWR patch panel in pairs of CWR peers: – The left hand set of high-density E1 connectors on the CWR patch panel attaches to the two 12-port E1 modules on one core or exit router. – The right hand set of high-density E1 connectors on the CWR patch panel attaches to the two 12-port E1 modules on the other core or exit router. • For each pair of CWR peers, one high-density E1 connector (either the right hand or the leviathan connector) supports the active relays, while the corresponding connector for the CWR peer provides redundancy and failover protection. • 24 RJ48-C connectors, each of which supports channelized connectivity at E1 line rates. These connectors provide the direct connections to the site and interzone links.

3-14

68015000701-C - October 2013

3.3 Remote Sites

Figure 3-7

CWR Patch Panel

3.3 Remote Sites The following describes the different types of remote sites supported in the Dimetra system: • 3.3.1 Base Transceiver Station (BTS), page 3-15 • 3.3.2 Control Sites, page 3-21

3.3.1 Base Transceiver Station (BTS) A Base Station serves as the Radio Frequency (RF) interface between the system infrastructure and the radios. Base Stations in a trunked system have three primary interfaces: • A receiver to pick up the RF signal from the radios • A transmitter to send RF signals to the radios • A wireline interface to send audio and control traffic to the system infrastructure The Dimetra IP system currently supports the following types of BTS: • MTS LiTE • MTS 1 • MTS 2 • MTS 4 The BTS connects to the MSO through a fractional E1, X.21 or Ethernet link. The main functions of the MTS are listed below: • Radio link formatting, coding, timing, framing and error control. • Timing control supervision to radios (Timing Advance). • Radio link quality measurements (Signal Quality Estimate). • Site to site frame synchronization. • Interface translation: radio link to network equipment. • Switching functions between multiple base transceivers (radio carriers). • Air Interface Encryption. • Local Site Trunking. • Operation, maintenance and administration agent. The MTS in all configurations has the following alarm inputs and control outputs: • 15 x 12V non-floating opto-isolated alarm inputs - available on the junction panel • 2 x Form A relay outputs with Common and Normally Open contacts - available on the junction panel

68015000701-C - October 2013

3-15

System Overview

• DOOR alarm - connected to the SC All these alarms and controls are connected to the Integrated Alarm Card (IAC) which is internal part of Site Controller (SC).

3.3.1.1 MTS LiTE The MTS LiTE is a single-BR base station designed for indoor working without the requirements for cooling fans. All modules can easily be accessed through the cabinet front door. Due to its small size a complete MTS 2 cabinet can easily be fitted into a 19" outdoor enclosure with heat exchanger. Note that the standard cabinet has air convection holes so that it is not environmentally protected against water or heavy dust. Figure 3-8

MTS LiTE

The MTS LiTE is available in the 260, 350, 380-430, 450-470 and 800 MHz frequency bands. A typical MTS LiTE Site configuration includes four major functional components: • Base Radio • Site Controller (SC) • RF Distribution System (RFDS) • Power Supply A Radio Frequency Distribution System (RFDS) distributes up to two Receive antennas to the base radio (BR). The duplexer enables a duplexed Receive/Transmit function on one antenna, which further reduces the total count on antennas per site.

3.3.1.2 MTS 1 The MTS 1 is a small, single base station designed to be wall mounted for indoor use or mast mounted for outdoor use in larger systems. For additional capacity, two MTS 1s can be connected to work in a dual configuration for additional capacity and resilience. The MTS 1 enclosure is dust tight and also protects against other environmental elements, such as water. The MTS 1 provides up to 4 channels in a single cabinet or up to 8 channels in a dual MTS 1 configuration. It is available in the 380 - 470 MHz frequency band. A typical MTS 1 site configuration includes four major functional components: • Base Radio

3-16

68015000701-C - October 2013

3.3.1.3 MTS 2

• Site Controller (SC) • Duplexer with Preselector path • Power Supply Unit The duplexer enables a duplexed Receive/Transmit function on one antenna, which further reduces the total count on antennas per site. The MTS 1 comes with several optional accessory kits such as solar shield for sun heat protection (for outdoor use). Figure 3-9

MTS 1

3.3.1.3 MTS 2 The MTS 2 is a small, very powerful base station designed for indoor working without the requirement for cooling fans. All modules can easily be accessed through the cabinet front door. Due to its small size a complete MTS 2 cabinet can easily be fitted into a 19" outdoor enclosure with heat exchanger. Note that the standard cabinet has air convection holes so that it is not environmentally protected against water or heavy dust.

68015000701-C - October 2013

3-17

System Overview

Figure 3-10

MTS 2

The MTS 2 provides up to 8 channels in a single 61 cm high cabinet. It is available in the 260, 350, 380-430, 450-470 and 800 MHz frequency bands. A typical MTS 2 Site configuration includes four major functional components: • Base Radio(s) • Site Controller (SC) • RF Distribution System (RFDS) • Power Supply A Radio Frequency Distribution System (RFDS) combines two transmit channels onto one antenna and distributes up to three Receive antennas to the base radios (BRs). The duplexer enables a duplexed Receive/Transmit function on one antenna, which further reduces the total count on antennas per site. The hybrid combiner is a wide band component and does not need to be tuned on a certain frequency. For expansions the main modules of the MTS 2 can be re used in an MTS 4. Expansions from MTS 2 to MTS 4 do not require any modification of the antenna installation. The antenna installation can be re used without any change and little more floor space is required for increased capacity supported by MTS 4.

3.3.1.4 MTS 4 MTS 4 is a high capacity base station. It provides up to 16 channels in a single 143 cm high cabinet or up to 32 channels in two cabinets. It is available in the 260, 350-370, 380-430, 450-470 and 800 MHz frequency bands. A typical MTS 4 Site configuration includes four major functional components: • Base Radio(s) • Site Controller (SC) • RF Distribution System (RFDS) • Power Supply

3-18

68015000701-C - October 2013

3.3.1.5 Redundant Base Station Site Link

Figure 3-11

MTS 4

A Radio Frequency Distribution System (RFDS) combines up to eight transmit channels onto just one antenna and distributes up to three receive antennas to multiple base radios. Duplexers enable a duplexed Receive/Transmit function, which further reduces the total count on antennas per site. For non-duplexed operation the MTS 4 also comes optionally with a Tx-postfilter that allows sufficient space for up to three preselectors. This configuration supports up to triple diversity un-duplexed with one Tx and three Rx antennas. The MTS 4 prime cabinet is built up out of two card cages above one another and supports up to four base radios. For expansions up to eight base radios an expansion cabinet of exactly the same size as the prime cabinet can be added. An MTS 4 card cage with Base Radios power supply and SC is identical to an MTS 2 with the filter and combiner section removed.

3.3.1.5 Redundant Base Station Site Link The primary purpose of the Redundant Base Station Site Link feature is to have two physically separate links to each base station. If one link is broken the other link is able to carry the traffic to the base station. The secondary purpose is to reduce the cost of leased lines by allowing base stations to be connected in a ring structure. When operating in a ring structure it is possible to connect base stations by microwave links, which is normally cheaper than using leased lines from a Ground Based Network (GBN) operator. Redundant Base Station Site Link feature includes also Satellite Links. If this feature is introduced, the BTS connects to the MSO through two fractional E1s (or X.21 link).

3.3.1.6 Site Controller (SC) The Site Controller (SC) manages site activity and assigns channels as requested by the Zone Controller. When communications to the MSO are not available, the SC is also able to perform local site trunking operation. The SC provides connection of either an X.21, E1 or Ethernet link to the MSO. The SC terminates the permanent virtual circuit (PVC) which is originated at the core router at the MSO, and distributes control, voice, and network management traffic to the base radios through a 10Base-2 Ethernet bus.

68015000701-C - October 2013

3-19

System Overview

Figure 3-12

Site Controller (SC)

A second SC can be installed at the BTS site to provide active/standby redundancy. Redundant Site Controllers are linked through a 10/100Base-T Ethernet interface. The SC also provides frequency reference and timing reference. The SC has a high stability oscillator to provide frequency reference signaling to the base radios. The SC also includes an internal GPS receiver which connects to a GPS antenna through an RF feeder to provide timing reference. If redundant SCs are installed at the site, both SCs require a separate GPS antenna connection. If NTS (Network Time Server) is present, it can be used as a secondary frequency reference A logical control path and logical manager path are maintained between the BTS site and the MSO. The control path delivers control traffic between the BTS site and the Zone Controller. The manager path delivers network management traffic between the BTS site and the network management servers. The SC software is loaded through the Software Download (SWDL) application. The configuration parameters for the SC are defined both through the Zone Configuration Manager and through Dimetra™ BTS (Base Transceiver Station) Service Software (TESS).

3.3.1.7 Base Radio Each BTS base radio supports a pair of 25 kHz transmit/receive frequencies. This physical pair of channels provides four inbound and outbound TDMA logical channels. Up to four control capable channels can be configured in the BTS. These four channels are spanned across the first TDMA slot of each of the four base radios installed in the first BTS rack. The base radio supports receiver diversity. Receiver diversity provides increased talkback range by the installation of two or three receiver modules in the base radio which are tuned to the same inbound frequency. Two receiver diversity is standard in a BTS base radio. The three receiver diversity option requires an additional receiver multicoupler tray to be installed in the rack to support additional inbound lines to the base stations. The base radio operates in the 380-460 MHz range, or in the 806-870 MHz range, depending on the type of BTS platform that has been purchased. The base radio provides 15 or 25 Watts (adjustable) of power output to the antenna system. Typical channel spacing between transmit and receive in a TETRA environment is 10 MHz. Therefore, a base station operating with a transmit (downlink) frequency of 390,500 MHz typically has a corresponding receive (uplink) frequency at 380,500 MHz.

3-20

68015000701-C - October 2013

3.3.1.8 Breaker Panel

Figure 3-13

BTS Base Radio

The base station is able to provide air interface encryption by applying a cipher key and a user-defined offset variable to the inbound/outbound coded traffic. To provision the base station for encryption, the base radio is loaded locally with a secret infrastructure key through a Key Variable Loader (KVL). This infrastructure key is used to decrypt cipher keys which are delivered over the network. The base radio uses the appropriate cipher key (SCK, DCK, or CCK) to encrypt outbound traffic and decrypt inbound traffic. The BTS base station software is loaded through the Software Download (SWDL) application. This application can load software to the entire BTS site over the network, or can load software directly to an isolated base radio through a direct connection. The configuration parameters for the BTS base station are defined both through the Zone Configuration Manager and through Dimetra™ BTS (Base Transceiver Station) Service Software.

3.3.1.8 Breaker Panel The breaker panel distributes power to the individual components in the BTS rack. The breaker panel receives two independent -48VDC inputs and has a number of breaker switches to switch power on and off for individual components in the rack. The breaker panel is located at the top of the BTS rack.

3.3.2 Control Sites Control sites are the locations where the users of the system (dispatchers and network managers) access the dispatch consoles and/or the network management terminals (NMTs). A control site can include a variety of equipment to serve its particular purpose in the system. It may have just dispatch consoles or NMTs or it may have both depending on the requirements. A control site uses the GGM 8000 Gateway as Control Site Router and can use a Conventional Channel Gateway and a core LAN switch. If needed, the site can support patching with four conventional channels. When the Control Site Router is also functioning as a CCGW it is not possible using Multilink Frame Relay (MFR) to increase the site link bandwidth.

68015000701-C - October 2013

3-21

System Overview

Figure 3-14

Control Site

GBN

Redundant WAN Link (optional)

WAN Link

Control Site Router / CCGW

LAN Switch

NM Client

4-Wire

Dispatch Console

3.3.2.1 Dispatch Subsystem The MCC 7500-series Dispatch Console Subsystem consists of the MCC 7500C Dispatch Console Subsystem and/or the MCC 7500S Secure Dispatch Console solution. The MCC dispatch subsystem includes all the equipment necessary to support the dispatch consoles. The dispatch consoles can be located at the MSO or can be remotely located at a control site. The figure below shows the components in the dispatch subsystem. The equipment consists of the MCC 7500-series Dispatch Console (and associated peripheral hardware), the MCC 7500 Archiving Interface Server (AIS) (and the associated logging recorder and replay station), and the Analog Conventional Channel Gateway (CCGW) (also known as the conventional base station interface).

3-22

68015000701-C - October 2013

3.3.2.1 Dispatch Subsystem

Figure 3-15

Dispatch Subsystem

Logging Re corde r

LAN S witch

Archiving Inte rfa ce S e rve r

WAN

BTS

Trunking S ite Cons ole S ite Route r w/ CCGW Re pla y S ta tion Loca l Ana log Conve ntiona l S ta tions

MCC7500 Cons ole s LAN S witch

Cons ole S ite (w/ Conve ntiona l) The MCC 7500-series Dispatch Console is Motorola’s high-tier radio dispatch console system. A console dispatch subsystem consists of the following components: • A Motorola-certified Dispatch Console PC • Accessories, such as headsets, speakers, desk microphone and a footswitch. • A logging system. (The Archiving Interface Server (AIS) and the associated logging recorder and replay station) • An Analog Conventional Channel Gateway (CCGW) (also known as the conventional base station interface) The dispatch console equipment connects directly to the radio system’s IP transport network. It uses the IP packet protocols for passing call control data and call audio through the system. The following figure shows a high-level diagram of how the MCC 7500-series equipment fits into the system.

68015000701-C - October 2013

3-23

System Overview

Figure 3-16

MCC 7500 Dispatch Console Subsystem

Archiving Replay Station

MCC7500/ MCC7500S Cons ole

Archiving Recorder Device

Ethe rne t S witch

Archiving Interface Server (AIS)

MCC7500/ MCC7500S Cons ole

WAN

Route r

3.3.2.1.1 Dispatch Console PC Each operator position in the dispatch centre consists of a Motorola-certified personal computer equipped with a keyboard and a mouse. The PC processor unit is an HP rp5800 computer with Windows 7 operating system installed.

3.3.2.1.2 Equipment connected to the Dispatch Console PC The following describes the peripheral equipment connected to the Dispatch Console PC.

Desktop Speakers The Dispatch Console PC supports two speakers through which a dispatch console operator can listen to audio. Each speaker on a dispatch console contains unique audio; that is, an audio source cannot appear in multiple speakers at a single dispatch console. The speaker is designed for use near computer monitors.

Desk Microphone The Dispatch Console PC supports a single desk microphone. The microphone is the AKG31/AKG33 and gooseneck GN 30E.

Footswitch The Dispatch Console PC can support a single footswitch with one pedal. The pedal controls the General Transmit feature. The footswitch allows users to operate the feature with their feet so their hands are freed for other tasks. If desired, the footswitch can be permanently fastened to the floor.

Emergency Beacon The Dispatch Console PC supports an emergency beacon that notifies the dispatcher with colored light when an emergency call is received. The Emergency Beacon feature is implemented as the set of green/yellow/red control lights and the buzzer served by the dedicated application. It is installed on the Dispatch Console PC. The hardware is connected to the computer via USB.

3-24

68015000701-C - October 2013

3.3.2.1.3 Logging System

Figure 3-17

MCC 7500 Emergency Beacon

3.3.2.1.3 Logging System Motorola’s logging system allows an agency to record audio transmissions as well as certain radio events from selected talkgroups/channels in a radio system. These recordings are archived for future playback and use by authorized users/administrators. The main features of the logging system are listed below: • Each recorder can be configured to record up to 256 conventional channels or trunking talkgroups or any combination of the two. • Each recorder can be configured to record a number of individual calls, based on a specific license. • Through the use of agency partitioning, only authorized transmissions may be recorded and/or accessed by the replay station. • The logging system has replay stations that are permissions-based, allowing users to only listen to appropriate channels/talkgoups. • The logging system allows users to conduct searches based on criteria such as time of transmission, channel, and other call data. • Recordings can be copied to transferable media. • The logging system can include multiple logging recorders, MCC 7500 Archiving Interface Servers and replay stations. There are three hardware devices within a logging system: • MCC 7500 Archiving Interface Server • Logging Recorder • Replay Station

68015000701-C - October 2013

3-25

System Overview

The MCC 7500 Archiving Interface Server provides an interface between Motorola’s radio system and the 3rd party logging solution hardware which allows audio transmissions and radio system events to be recorded together with associated call data. The MCC 7500 Archiving Interface Server monitors selected group resources (channels/talkgroups) and individual resources (radios, consoles) passes call-control information and audio to the recording device via the LAN. The recording device utilizes a 100 Mb Ethernet port to communicate with the MCC 7500 Archiving Interface Server and records this information on permanent or transferable media. The 3rd party logging solution provides a GUI called AIS Administrator that allows an administrator to choose which channels/talkgroups are to be recorded by each recorder. The 3rd party logging solution provides a user interface capable of allowing a user to identify actions/calls that occurred on the radio system, choose the desired call they wish to review, and play back the audio for that call through a 3rd party logging replay solution. The 3rd party logging solution reconstructs the playback audio from the vocoded samples that had been sent to the logging subsystem when the call occurred ensuring that the audio quality is equal to that of the original transmission. The logging system can be located on a dispatch console site, or on a logging only site without consoles. The logging site can be either centralized (colocated at the MSO) or decentralized (at remote control site).

MCC 7500 Archiving Interface Server The MCC 7500 Archiving Interface Server passes call control information and audio for each radio system resource that the user wants to record to the logging subsystem. The call control information passed to the logging subsystem includes identification of the talkgroup or channel transmitting, identification of the user making the call (unit ID, unit alias), the type of call (talkgroup call, emergency call, and so on), and other information. All this information is logged by the logging subsystem and is available for display back to the user upon playback. Each MCC 7500 Archiving Interface Server must be paired with its own recorder.

Logging Recorder The 3rd party logging recorder is shipped pre-installed with all the necessary software including a Protocol Processor licensed to operate with the Motorola MCC 7500 Archiving Interface Server and requires no direct interaction from a user or dispatcher. The recorder requires an IP address before it can be connected to the LAN. Once connected, it stores audio transmissions, call data and call events from the selected talkgroups/channels on specified transferable media. Recorders can store at least 48 hours worth of audio.

Replay Station Audio and events which have been recorded by the 3rd party logging recorder(s) are accessed via a 3rd party replay station. The replay station is a networked PC equipped with a keyboard, mouse, a monitor, and a speaker. The replay station software displays information such as logged events and call data such as audio/event starting time and duration of transmission. The replay station software also allows the user to listen to audio call recordings to the user through a graphical user interface. A replay station can access recordings on multiple 3rd party logging recorders, even ones which are not being used with MCC 7500 Archiving Interface Servers. This provides the user with a complete view of everything being recorded from a single point.

3-26

68015000701-C - October 2013

3.3.2.1.4 Conventional Channel Gateway (CCGW)

3.3.2.1.4 Conventional Channel Gateway (CCGW) Conventional Channel Gateway (CCGW) is a GGM 8000 gateway configured to operate as an interface between the Dimetra system and the conventional system. It allows working with and patching with conventional channels thus providing an easier transition period when going from an existing system to a Dimetra system. Figure 3-18

GGM 8000 used for CCGW

The CCGW allows up to 4 conventional channels to be connected to the console dispatch subsystem. At a small control site (which is a location where users access dispatch consoles and network management terminals) only the Conventional Channel Gateway function is performed by the Control Site Router. At all other control sites up to ten CCGWs may be installed. Figure 3-19

Patching with a Conventional System

Conventional Users

Conventional Channel

Conventional Channel

Dimetra Users

Conventional Dispatch Patch CCGW

Site Tie Lines

MCC7500 Dispatch

Site

Dispatch

68015000701-C - October 2013

Site

SwMI

Dispatch

3-27

System Overview

3.3.2.1.5 Secure Dispatch System (End-to-End Encryption (E2EE)) E2EE MCC7500S console solution is developed to provide end to end encrypted communication between radios and consoles. As illustrated in the figure below, the E2EE MCC7500S console solution is composed of three main entities: • Call Control Entity (CCE), also called Dispatch PC • CryptR • Audio Processing Entity (APE), also called Audio Module The KVL is not used in daily operation, but only used to load security keys to the CryptR. Figure 3-20

MCC 7500S Dispatch Console

X-zone

Dispatch PC

CryptR

Audio Module

Footswitch

SB

Filter Connector XLR

XLR

LLR

Sound Card

Kinesis USB

U

IRR

Headset

U SB

Site Switch

Digital Audio Adapter

Splitter Cable

XLR

Microphone

Speakers

End-2-End Encryption (E2EE) Call Logging E2EE Call Logging is similar to clear all logging, described previously in 3.3.2.1.3 Logging System, page 3-25with the following differences: • E2EE Call Logging allows for the logging of encrypted calls in an encrypted format. • CryptR handles the decryption of the calls in conjunction with a Replay Station.

E2EE Call Logging Servers E2EE logging solution is an enhancement of the clear-only solution and handles both clear and encrypted calls. It consists of the following servers: • MCC 7500 Archiving Interface Server (AIS)

3-28

68015000701-C - October 2013

3.4 Radios

• Voice Logger • Tape Storage

3.4 Radios Radios communicate with the RF sites using the TETRA standard. These radios support encryption, authentication, and interfacing for a data terminal.

3.4.1 MTP3000 Series Overview The MTP3100/MTP3200/MTP3250 MTP3150 is Motorola TETRA portable radio for mission critical communications. Figure 3-21

68015000701-C - October 2013

MTP3100/MTP3200

3-29

System Overview

Figure 3-22

MTP3150MTP3250

Providing higher power increases range and in-building performance, and so Motorola has added Class 3L (1.8W) power output option. Taken together with high receive sensitivity this radio has the capability for maintaining communications in the most demanding situations. It has an improved operational effectiveness through: • Update your availability and situation using Status Messaging - monitor the progress of job assignments, or call for support when needed. • Integrated GPS. Knowing where your resources are enables you to allocate tasks based on up-to-date information (MTP3250 only). The safety of MTP3000 Series is improved through: • Improved coverage in DMO operation, ensuring that users can communicate over a wider area or in buildings or built-up areas. • Silent emergency, hitting the emergency button alerts colleagues to critical situations but sends and updates your location, without showing any indication on the radio screen. • Rugged side connector. This new side connector with the range of available accessories ensures that connection is maintained even in the most violent of situations.

3-30

68015000701-C - October 2013

3.4.2 MTH800 Overview

3.4.2 MTH800 Overview Motorola MTH800 is a compact yet robust radio. Thanks to its form factor and rubber features, provides a comfortable and user-friendly tool you can depend on even in the toughest environments. Figure 3-23

MTH800 Portable

The MTH800 features an extensive set of tools designed to enhance the personal safety, security, and efficiency of both mission-critical and commercial users. Incorporating the latest technologies, it includes support for GPS Location Services, high-grade encryption, data services and much more – enhancing user safety and driving efficiencies. Ensuring full customer flexibility, two GPS protocols are supported, including the TETRA Location Information Protocol (LIP), allowing users to: • Control and reconfigure GPS parameters over-the-air. • Define location and event driven position updates. • Set profiles to enable different location update rules in various scenarios, such as emergency situations. • Ensure that location information is only sent to authorized users through innovative authentication processes. Compact and lightweight, the MTH800 advanced microprocessor and Digital Signaling Processor (DSP) support Motorola TETRA innovations including WAP, Multi-Slot Packet Data, Short Data Service (SDS), and Predictive Text Entry (iTAP). Full End-to-End encryption as well as TEA1, TEA2, or TEA3 air encryption may either be factory fitted, provisioned in-country or, alternatively, retro-fitted at a later date. Furthermore, the MTH800 65536–color, 130 by 130–pixel display provides accurate reproduction of faces and other images. This high quality delivers maximum image definition in a wide range of lighting conditions. An intuitive graphical user interface complements the high-resolution display. The interface encompasses a range of customizable features, including scalable fonts, assignable shortcuts to menu items and features. It also provides access up to 4000 talkgroups and a unified address book facility that can hold 2000 entries. User safety is further enhanced with the large, easy to use the emergency button, as well as the programmable rotary knob. The rotary knob with the push-button operation allows fast access to volume and talkgroup control. The 1 Watt speaker assures audio quality, as well as a 1 Watt class D audio amplifier, which combines to offer exceptional audio clarity with minimal distortion. Two microphones are also included – a top microphone for dispatcher calls, and a bottom microphone for one-to-one calls.

68015000701-C - October 2013

3-31

System Overview

3.4.3 MTP850 S/MTP850 FuG Overview The MTP850 S/MTP850 FuG is Motorola TETRA portable radio for mission critical communications. Incorporating all features of the MTP850, this radio includes an advanced Man Down sensor for exceptional user safety together with a new side connector for increased ruggedness. Figure 3-24

MTP850 S

Figure 3-25

MTP850 FuG

Providing higher power increases range and in-building performance, and so Motorola has added Class 3L (1.8W) power output option. Taken together with high receive sensitivity the MTP850 S/MTP850 FuG maintains communications in the most demanding situations. The MTP850 S/MTP850 FuG has an improved operational effectiveness through: • Access to information databases through integrated WAP browser - decide based on the latest information.

3-32

68015000701-C - October 2013

3.4.4 MTP830 S/MTP830 FuG Overview

• Update your availability and situation using Status Messaging - monitor the progress of job assignments, or call for support when needed. • Integrated GPS. Knowing where your resources are enables you to allocate tasks based on up-to-date information. The MTP850 SMTP850 FuG has an improved safety through: • Improved coverage in DMO operation, ensuring that users can communicate over a wider area or in buildings or built-up areas. • If the radio does not move in a specific time period, the Man Down feature sends an alert to the console operator. • If the radio tilts more than the programmed angle, the Man Down feature sends an alert to the console operator. • Silent emergency, hitting the emergency button alerts colleagues to critical situations but sends and updates your location, without showing any indication on the radio screen. • Rugged side connector. This new side connector with the range of available accessories ensures that connection is maintained even in the most violent of situations.

3.4.4 MTP830 S/MTP830 FuG Overview Motorola MTP830 S/MTP830 FuG TETRA portable terminals are the ideal choice when working in extreme conditions. These terminals deliver premium performance, while combining louder audio and enhanced ergonomics with simplified controls, allowing fire fighters and other first responders to focus on the task at hand. Figure 3-26

68015000701-C - October 2013

MTP830 S

3-33

System Overview

Figure 3-27

MTP830 FuG

Enlarged rotary knob allows better radio glove-friendly functionality, thus allowing easier control talkgroup and volume settings. Operating a radio under protective clothing can be challenging. The MTP830 S/MTP830 FuG can safely inter-operate with a wide range of specialist audio and push-to-talk equipment. Man Down detector allows an emergency alert signal to be triggered at your control room when the radio exceeds preset motion timer and tilt angle thresholds. The MTP830 S/MTP830 FuG can be configured to send location reports when the emergency button is pressed – helping control room staff coordinate a response more efficiently. The MTP830 S/MTP830 FuG automatically adjust audio settings based on pre-loaded profiles for detected accessories. It also enables selecting the best audio profile for different working environments. The combination of a highly sensitive RF receiver and transmission power that is adjustable to 1.8W provides extended operational range.

3.4.5 MTP850 Ex/MTP810 Ex Overview Motorola MTP850 Ex/MTP810 Ex TETRA portable radio provides comprehensive user safety and class leading ATEX specifications. The radio enables working in environments containing potentially explosive gas and dust. The radio also provides high-quality communication.

3-34

68015000701-C - October 2013

3.4.5 MTP850 Ex/MTP810 Ex Overview

Figure 3-28

MTP850 Ex

Figure 3-29

MTP810 Ex

The MTP850 Ex/MTP810 Ex ATEX TETRA terminals deliver safe and reliable communications for users with a powerful set of features to harness the capability of TETRA. The MTP850 Ex/MTP810 Ex deliver best in class audio performance in the typical noisy environments where specialist users from industry or public safety operate. The MTP850 Ex can be used in explosive gas and dust environments due to its high level of protection – including dust Zone 21 and 22. The MTP810Ex is a low tier solution for use in explosive gas and dust environments – dust Zone 22. Operational safety is further enhanced with a range of features including: • integrated GPS receiver providing the ability to locate personnel, improving user safety and resource management.

68015000701-C - October 2013

3-35

System Overview

• internal Man Down alert - this fully integrated solution triggers an emergency procedure when the carrier of the radio remains motionless far a set period or falls down. The simplified keypad with a large button surface makes the MTP850 Ex/MTP810 Ex easy to use with gloves. Combined with the large scalable display fonts and icons, the MTP850 Ex/MTP810 Ex facilitates operation in difficult environments with limited visibility. The integrated WAP browser and Multi-Slot packet data enables rapid access to critical information in the field. Applications are further enhanced with ability to have simultaneous Short Data Service (SDS) and Multi-Slot packet data services through the TNP1 protocol.

3.4.6 TCR1000 Overview Motorola is a world leader in the development and deployment of TETRA communication solutions, and the TCR1000 covert TETRA radio from Motorola is the smallest, body worn TETRA radio available. Figure 3-30

TCR1000

The Motorola TCR1000 Covert radio is the ideal solution to ensure secure communications in surveillance covert type operations allowing officers to blend right into the crowd. Motorola TCR1000 Covert TETRA radio delivers high-quality communication in a light and discrete package for those critical undercover applications. There are no compromises in the design of the TCR1000. Motorola worked closely with police forces to ensure that it is intuitive and simple to operate, truly Technology that is Second Nature. The TCR1000 incorporates control features matched to the needs of officers in covert operations. Its design enables easy hiding inside of light clothing. A unique portfolio of covert accessories complements the TCR1000 and offer additional flexible options for undercover officers. This radio operates at 1 watt and the option for a body mounted antenna ensures excellent coverage and maintains the discreetness of the radio. A small, easily concealable Remote Control Unit (RCU) controls the radio. The RCU allows the user to answer or to initiate calls, change talkgroups, and volume. It also allows using special surveillance features such as whisper mode or communication tones (like PTT Double Push feature). A connector is provided on the RCU to attach a remote PTT unit.

3.4.7 MTM800 Enhanced Overview Discerning professionals demand high-quality voice communications with fast access to mobile applications. The MTM800 Enhanced delivers on both, with SDS, Multi-Slot Packet Data and WAP options.

3-36

68015000701-C - October 2013

3.4.8 MTM5x00MTM800 FuG/MTM800 FuG ET Overview

Figure 3-31

MTM800 Enhanced

Developed for organizations where rugged and versatile mobile terminals are essential, Motorola MTM800 Enhanced is ideal for use where the application, location and/or circumstances demand fast, reliable, no-nonsense solutions. • Ease-of-operation in the most demanding situations – unsurpassed audio quality, intuitive keypad, and high-definition, color display combined with a sleek yet durable design. • Dust and water resistant to IP 54. rain, salt, fog, and dust protection tested to MIL 810 C/D/E/F for the standard control head. • Motorcycle control head rated IP67 for dust and water resistance The MTM800 Enhanced also supports the full suite of TETRA security functions, including air interface encryption, and End-to-End encryption. Users can request assistance by simply hitting the emergency button, which not only alerts colleagues to critical situations, but also sends an update dispatch on the user location. The radio is able to switch to covert mode at a press of a button. The radio has an integrated GPS receiver that enables users to locate their mobiles, and provides location-based services and mapping capabilities. The radio offers various installation possibilities from typical Dashboard installation to Dual Control Head installation using an additional junction box. Currently the following options are supported: • Trunnion Installation • Dashboard Installation • Desktop Installation • Remote Mount Installation • Motorcycle Installation • Dual Control Head Installation • Data Box Radio Installation

3.4.8 MTM5x00MTM800 FuG/MTM800 FuG ET Overview The MTM5x00MTM800 FuG/MTM800 FuG ET are a range of Tetra Mobiles that address both current and future critical communication needs. The MTM5x00MTM800 FuG/MTM800 FuG ET Series leverages the proven design of the previous Mobile generation, the MTM800 Enhanced as well as introducing enhancement and changes to further improve performance and usability. Figure 3-32

68015000701-C - October 2013

MTM5200 and MTM5400MTM800 FuG

3-37

System Overview

Figure 3-33 TSCH

MTM5500MTM800 FuG ET in Mixed Dual Control Head Configuration with eCH and

With its best in class RF sensitivity and 10 W transmit power capability, the MTM5400/MTM5500MTM800 FuG/MTM800 FuG ET Series set a new benchmark for TETRA RF performance. The MTM5400/MTM5500MTM800 FuG ET Series support multiple modes of operation that enable enhanced workflow management and improved communications in areas where network coverage is weak or unpredictable. The integrated DMO Repeater is Type 1A compliant, operating on just a single RF carrier for efficient spectrum usage. The MTM5400/MTM5500MTM800 FuG ET Series feature an integrated gateway that connects users operating in Direct Mode with control room staff and other colleagues on the trunked radio network. A comprehensive set of gateway services is supported, including configurable handling of individual and group calls. Advanced Remote Terminal Management enabled through software, this ground-breaking capability allows the MTM5x00MTM800 FuG/MTM800 FuG ET Series to stay live while being programmed and software upgraded. This feature works to maximize productivity and eliminate radio downtime. The MTM5200/MTM5400MTM800 FuG mobile offers comprehensive and flexible installation options. The radio is fully DIN-A compatible and supports a wide range of configurations including customized multiple control head, desk, and motorcycle install variants.

Do not connect MTM5200, MTM5400, and MTM800 FuG Control Heads to the Enhanced (Ethernet) MTM5500, MTM800 Fug ET radio (and the other way around). Even though mechanically possible, it is incorrect and will result in hardware malfunction (broken transceiver).

3-38

68015000701-C - October 2013

3.4.8 MTM5x00MTM800 FuG/MTM800 FuG ET Overview

Use proper Ethernet cables to connect Ethernet Expansion Head with TSCH and eCH. Transceiver can be broken if not connected properly.

MTM5x00MTM800 FuG/MTM800 FuG ET Model Comparison Table 3-2

MTM5x00 MTM800 FuG/MTM800 FuG ET Options MTM5200,MTM5400MTM800 FuG

MTM5500MTM800 FuG ET

Expansion Head Options

Expansion Head (single std connection)

Ethernet Expansion Head 2xstd, Ethernet type, Ethernet SIM reader and RS232.

Control Head Options

Standard Control Head

Expansion Head Enhanced (std and auxilary 25 PIN and RS232)

Remote Control Head

Remote Ethernet Control Head (eCH)

Telephone Style Control Head (TSCH)

IP67 Control Head Installation Options

Desk Mount (Control Centre)

Remote Mount Only

Remote Head Mount (car, ambulance, fire truck)

Multiple Control Heads

IP67 Mount (boat, motorcycle) User supplied terminal (Data Only Installation)

MTM5500MTM800 FuG ET Configurations MTM5500MTM800 FuG ET can be configured in one of the following five configurations: • Remote Mount installation with Ethernet Control Head (eCH) PMWN4024A • Remote Mount installation with Ethernet Telephone Style Control Head (TSCH) PMWN4025A • Dual Control Head with two eCH • Dual Control Head with two TSCH • Dual Control Head with mixed eCH and TSCH

Telephone Style Control Head (TSCH) In the Ethernet Dual Control Head solution, you can also use the TSCH type of Control Head. The TSCH can be installed both horizontally and vertically. The display on the Telephone Style Control Head can rotate, which increases its readability and facilitates operation. By default: • When the TSCH is off-hook, its display orientation is portrait. • When the TSCH is on-hook, its display orientation can take one of the following positions (depending on your service provider configuration): – Fixed Portrait – Clockwise Rotation

68015000701-C - October 2013

3-39

System Overview

– Counter Clockwise Rotation Figure 3-34

3-40

Telephone Style Control Head (TSCH)

68015000701-C - October 2013

4

Dimetra IP Data Management

4.1 Radio System Databases The system uses a variety of databases to provide communication services to individual users. Configuration data for users, talkgroups, and the system infrastructure are stored in these databases. Other types of information stored include system performance and fault data. The databases are the organizing element that transforms the computers and radios in the system into a versatile communications platform. The various databases include information concerning: • 4.1.1 Call Processing Information, page 4-1 • 4.1.2 Fault Management Information, page 4-3 • 4.1.3 Statistical Data, page 4-3 • 4.1.4 Database Summary, page 4-3

4.1.1 Call Processing Information The following describes the individual databases, the relationship between the databases, and the way the system uses the data. The following databases are covered here: • 4.1.1.1 User Configuration Server Database, page 4-1 • 4.1.1.2 Zone Database Server, page 4-2 • 4.1.1.3 Home Location Register, page 4-2 • 4.1.1.4 Visitor Location Register, page 4-2 • 4.1.1.5 Zone Local Database, page 4-2 • 4.1.1.6 Radio Control Manager (RCM) Database, page 4-2 • 4.1.1.7 Affiliation Database, page 4-2

4.1.1.1 User Configuration Server Database The User Configuration Server (UCS) stores information about radios, talkgroups, critical sites, Adjacent Control Channels (ACC), interzone control paths, and user security information for the cluster. Group and Unit ID home zone assignments are also made at the UCS level. The UCS provides the benefit of a single point of entry with automatic propagation of data throughout the cluster to all the zones in the cluster. Each zone database in the cluster receives all of the information entered at the UCS, allowing the zone databases to be used for restoring cluster-level data to the UCS if necessary. A UCS API is available, allowing a customer-supplied provisioning system to interface with the User Configuration Servers in all the clusters. This allows a centralized provisioning system to provide system wide configuration capability to all the User Configuration Servers throughout the system.

68015000701-C - October 2013

4-1

System Overview

4.1.1.2 Zone Database Server The Zone Database Server (ZDS) stores information about the zone configuration such as base stations, telephone connections, data servers, console sites, archive interface servers etc. The ZDS is managed by the Zone Data manager (ZCM).

4.1.1.3 Home Location Register The Home Location Register (HLR) stores the current zone location of any registered individual or affiliated group members whose configuration information is stored in the HLR. Groups and Individuals are treated differently for mobility purposes and therefore hosted by separate processes in the Zone Controller. These are called GHLR and IHLR respectively. The location information in the HLR is continually updated as radios are turned on and off, roam the system, and switch between talkgroups.

4.1.1.4 Visitor Location Register Each zone has a Visitor Location Register (VLR) to address the radios and talkgroups which are currently active in the zone. The VLR stores access configuration information for both individuals and groups along with their current site locations. The VLR resides in the Zone Controller.

4.1.1.5 Zone Local Database The Zone Local database, located in the Zone Controller, is a simplified text file containing much of the same infrastructure data that is found in the zone database. The primary reason that the local database exists is to allow continued communications within a zone in the case of a failure resulting in a Zone Controller reset while the zone database is not available. The local database allows the controller to provide wide area services in default mode until the HLR and VLR are restored with records from the ZDS/UCS.

4.1.1.6 Radio Control Manager (RCM) Database RCM Database contains radio events and radio commands monitored through RCM application. The radio commands monitoring functions available are Radio Check, Snapshot, Zone Status and events for Emergency Alarm. All monitoring displays are updated in real-time as the information becomes available in the system.

4.1.1.7 Affiliation Database The affiliation database contains real-time affiliation and deaffiliation information for radios, talkgroups, conventional consoles, channels and sites within a zone. Tracking radio users through a zone allows you to see which sites get the most use, how and when radio users access the system, and which talkgroups are involved in a particular call. The affiliation database resides on the Air Traffic Router (ATR) server. The ATR server receives radio call traffic in raw data packet format from the Zone Controller. The raw data packets are translated into Air Traffic Information Access (ATIA) packets by the ATR server and broadcast on the network as an ATIA stream. The radio call traffic information in this ATIA packet contains talkgroup and site affiliation and deaffiliation information for each radio user in a particular zone. The affiliation database collects this information and provides updates to PRNM management applications, such as Affiliation Display.

4-2

68015000701-C - October 2013

4.1.1.8 Radio User Information

4.1.1.8 Radio User Information Individual user permissions are provisioned through profiles that define characteristics common to a group of users. When a new user is entered into the system, the user is assigned an appropriate profile or profiles. Only the information unique to the user has to be keyed in. Talkgroups are organized in the same way, using talkgroup profiles to define characteristics common to a collection of talkgroups. This information is initially entered into the User Configuration Manager (UCM) as a single point of entry to avoid duplicating effort or generating mismatched databases. Afterwards, the information is replicated to each zone database.

4.1.2 Fault Management Information Unified Event Manager can collect integrated fault information from devices located in a zone. The server monitors faults from each of the devices and Local Area Network equipment (switches and routers) within the zone. It furthermore handles device discovery, supervision and synchronization.

4.1.3 Statistical Data The system organizes statistical information into reports. The data is collected based on groups specified by the administrator. The groups are based on object type, time interval, and number of intervals. For example, a collection group may be defined to collect statistics about talkgroups. A single collection group is not, however, capable of collecting statistics about both sites and zones – two separate collection groups would be needed. Also, a collection group collects statistics for a single collection interval.

4.1.3.1 Zone Statistics Server Database The Air Traffic Router (ATR) takes the Air Traffic Information Access (ATIA) stream and generate flat files with the information. The Zone Statistics Server (ZSS) database pulls this information and parses these records to the Report Players, which run on the Network Management client. The zone-wide statistical information in the ZSS Database summarizes call processing traffic. The reports generated can be one of two types: • Historical: these are static reports that cover a specific time interval. The amount of historical information that can be recovered depends on the specified time interval • Dynamic: These reports are real-time, short term reports that are updated for each interval of time selected by the user.

4.1.4 Database Summary The table below summarizes the pertinent information for each database, including its function, how it is accessed, and the server on which it resides.

68015000701-C - October 2013

4-3

System Overview

Table 4-1

Summary of Database Administration Functions

Database

Server

Function

UCS Database

UCS Database Server

The User Configuration Server is used for radio management as described in the following list: • Group and Unit ID Home Zone assignments are made at the UCS level. • Security information and other cluster-level parameters are set in the UCS. • Radios, talkgroups, critical sites, Adjacent Control Channels (ACC), and Interzone Control Path IDs are configured in the UCS.

Zone Database

Zone Database Server

All infrastructure configuration information for a specific zone, along with a copy of the user configuration information replicated from the UCS.

RCM Database

Air Traffic Router

The Radio Control Manager database carries information that allows the user to perform several monitoring and control functions.

Zone Statistics Server Database

Zone Statistical Server

Used in conjunction with Historical Reports Player to generate zone-wide reports.

Zone Local Database

Zone Controller

A copy of the local infrastructure database is downloaded to the Zone Controller once the ZDS is populated with the hardware configuration records of the zone. This copy of the local infrastructure database is stored in the Zone Controller to provide wide area communication in cases where the Zone Controller needs to re-initialize without having access to the ZDS.

Affiliation Database

Air Traffic Router

The affiliation database keeps track of the sites to which the individual radios are registered and the talkgroups to which they are affiliated.

4.1.5 Hierarchical View The table below shows the hierarchical listing of servers.

4-4

68015000701-C - October 2013

4.1.6 Server Interaction

Table 4-2

Hierarchical Listing of Servers Hosting Databases

Cluster-Level Servers

Zone-Level Servers

• User Configuration Server (UCS)

• Zone Controller (ZC) • Zone Database Server (ZDS)

• Unified Event Manager Server (UEM)

• Zone Statistics Server (ZSS) • Unified Event Manager Server (UEM) • Air Traffic Router (ATR)

One of zone-level Unified Event Manager servers can aggregate alarms from other zones.

4.1.6 Server Interaction As with many components of the Dimetra IP system, the system servers are highly interdependent; they rely heavily on each other to supply critical data in support of their individual functions. The figure below shows a high-level flow of information between the servers in the system. Each interaction is numbered. See the table below the figure for definitions of each of the numbered interactions. Figure 4-1

Server Interactions Defined

10

TNPS

UCS 10

1

10

16

UEM 10

10

15

5

ZDS

11

2

12

10

17

AUC

SSS

10

10

19

10

Dispatch Consoles

9

CCGW

3

ATR

ZSS

8 7

14

Client PCs

4

ZC 18

6

10

BTS

13

NTS

See below the descriptions of the above interactions.

68015000701-C - October 2013

4-5

System Overview

Table 4-3

Server Interactions

Interaction

4-6

Description

1

Replication/synchronization of database records occurs between the User Configuration Database (UCS) and each Zone Database. When changes are made to individual records in the UCM, the UCS replicates the new or changed information to each of the Zone Databases. The administrator can also run a synchronization command to force the UCS to download its entire database to a particular Zone Database Server (ZDS). If any problems occur with the integrity of the User Configuration Database, a full copy of the database can be restored (promoted) from any of the Zone Database Servers through the Administrator menu.

2

Radio (subset of UCS database) and infrastructure database export from the ZDS to the Zone Controller. The Zone Controller saves this information in its Local Database, and uses the information to create the home location register (HLR) for the zone. Diagnostic and fault information, including fault information proxied for other devices, are sent through this link to the ZDS.

3

Raw call traffic information is passed from the ZC to the ATR which formats the information and generates the Air Traffic Information Access (ATIA) stream. The ATR generates an ATIA Log, which contains records of the call processing information that are made available to the ATR. RCM information is passed from the ATR to the ZC.

4

Zone statistical data is sent from the ATR to the ZSS to compile statistical information on a per zone perspective.

5

Zone statistical data is sent from each ATR, within the cluster, to the SSS to compile statistical information on a per cluster perspective.

6

Site statistical data is sent from the BTS to the ZSS to compile statistical information on a per zone perspective.

7

Call requests, channel assignments, call terminations, and other call processing information is passed between the Zone Controller and the BTS sites. When a radio requests a call, the BTS site sends the request information to the ZC, the ZC determines how to set up the call, and the ZC sets up all the resources needed for the call.

8

Call requests, channel assignments, call terminations, and other call processing information is passed between the Zone Controller and the dispatch console.

9

Call requests, channel assignments, call terminations, and other call processing information is passed between the Zone Controller and the CCGW.

10

Unified Event Manager derives its listing of system objects from data received from other boxes. Device status information is derived from Simple Network Management Protocol (SNMP) agents.

11

The Zone Database Server sends any new or changed configuration information to the dispatch console. Fault information is sent from the consoles to the ZDS.

12

Configuration data is passed from the ZDS to the ATR.

13

The Network Time Server (NTS) is periodically polled for a time reference packet from other servers and network components.

68015000701-C - October 2013

4.1.6 Server Interaction

Table 4-3

Server Interactions (cont'd.) Interaction

Description Each client workstation runs the Private Radio Network Management (PRNM) Suite of applications. The following list shows the servers that support PRNM Suite applications: • UCS - User Configuration Manager, Zone Configuration Manager • ZSS - Zone Historical Reports 14

• UEM Server - Unified Event Manager • ATR - Zone Watch, Radio Control Manager, ATIA Log Viewer, Affiliation Display, RCM Reports If a server is disabled or is not available for some other reason, the associated applications do not start or are not able to retrieve or update information in the server.

15

Information about mobiles and infrastructure as input to authentication and encryption key generation.

16

Information about infrastructure as input to authentication and encryption key distribution.

17

Distribution of the authentication keys and encryption keys from AuC to the Zone Controller.

18

Distribution of the encryption keys from AuC to the BTS.

19

Configuration data is sent from ZDS to CCGW.

68015000701-C - October 2013

4-7

5

Dimetra IP Call Processing The Dimetra system consists of many separate pieces of hardware and software which together form a communications network. At the highest level, the system can be looked at from two main perspectives. • Physical, hardware-based component view — describes how the system components work together to move the necessary control and audio signals throughout the system to make calls happen. Using this view, you can organize the system components hierarchically, or by subsystem. • Logical, software-based system view. — describes how the management software (in all the elements of the fixed infrastructure) and mobile unit software work together to make calls happen. This approach provides an understanding of how the system is configured, how the system tracks mobile units as they roam throughout the coverage area, and how the system actually processes call requests made by mobile users. At the centre of call processing is the equipment at the MSO. This equipment provides the following functions: • The Zone Controller processes requests for registration, individual dispatch calls, group dispatch calls, and telephone interconnect calls, validates the requests and assigns the necessary resources to set up call services. • The Network Management (NM) subsystem provides the infrastructure, radio and user information necessary to coordinate the resources necessary for the different types of calls. • The network transport equipment (routers, switches) provides the IP connectivity to set up the paths that are required for call processing to take place. The network transport equipment makes it possible to send voice through the system as IP packets.

5.1 Configuration Information Configuration information is the foundation upon which all other aspects of call processing are built. Configuration information must be developed for the site, zone, and system levels, the radios, and console positions. Configuration information is required for the system infrastructure equipment, radios, and radio users. There are two basic types of configuration information: • User Configuration User configuration information consists of static or fixed user configuration. • Infrastructure Configuration Infrastructure configuration information defines how the underlying Fixed Network Equipment (FNE) handles signal flow. For example, this type of configuration determines which MTIG, site, and zone resources are assigned to a call. In general, this type of configuration is handled by Motorola personnel prior to and during system installation and will not be described further.

5.1.1 Static User Configuration Static configuration information, for call processing support, is used to identify individuals and groups that use the system and what services the system must provide to those individuals or talkgroups. Static configuration information is entered in two places: • The User Configuration Server (UCS) through the User Configuration Manager (UCM) application. Within this application, records are built for radios, radio users, dispatch consoles, talkgroups, and multigroups.

68015000701-C - October 2013

5-1

System Overview

Parameters that affect the operations of all radios in the system, such as site access denial, are also entered in the UCM. • The radios through their specific programming software. Static configuration information may be divided into four parts: • Home Zone assignment for individual and talkgroup IDs • Identification numbers and aliases for both individuals and talkgroups • Call services and system features allowed for that individual or talkgroup • Valid site settings for each individual and talkgroup

Valid site settings, in conjunction with the “Site Access Denial” setting (see 5.1.2 Infrastructure Configuration, page 5-7) play an important role in mobility management when a radio attempts to register or a group member attempts to register to a site. The static user configuration information is referenced by the system each time a radio attempts to register to a site and/or affiliate with a talkgroup.

Configuration information must be consistent when programming the UCS should be consistent with the configuration information in the radios.

5.1.1.1 Default Records The system can be configured to allow access to radios when no configuration information is available from the UCS. These radios are assigned a default configuration record automatically on initial system access. This default record gives them a predefined set of call services on the system. If the system is configured to disallow default access, a radio user cannot access the system without first having configuration information programmed in the UCS.

Default access allows all radio users and talkgroups to access the system with a predefined set of permissions. Individual control of radio users and talkgroups is not possible. This mode of operation is not recommended for use under normal operating conditions. The zone object in the Zone Configuration Manager (ZCM) configures and manages the attributes relating to a specific zone. The Zone Controllers use these parameters to allocate resources. The zone object configuration information is replicated from the Zone Database Server (ZDS) to the User Configuration Server (UCS). Two of the fields in the zone object record determine whether radios are allowed to access the system only if they have a record in the UCS, or whether they can access the system under default conditions using a default record. The fields are called Individual Default Access Permission and Talkgroup Default Access Permission.

5-2

68015000701-C - October 2013

5.1.1.2 Identification Numbers

5.1.1.2 Identification Numbers ID numbers are one of the key configuration elements that must be entered into the system. Based on the ID numbers that have been entered, the system determines the following: • Whether or not the individual radio or group is allowed to register at a site. • Which call services the individual radio or group can use • What system features the individual radio or group can use • Which zone is responsible for controlling the call (for group calls)

5.1.1.2.1 Programming ID Numbers Individual and group IDs information from the system fleetmap is programmed into the following areas of the system: • Using the UCM application, all individual and talkgroup IDs are entered in the UCS. • Using the applicable programming software, each radio is programmed with the system ID, its unique individual ID, and as many talkgroup IDs as needed.

Each console position uses one individual ID.

5.1.1.3 Home Zones The Home Zone mapping object in the UCM application provides the capability to divide into ranges the total number of individual and talkgroup IDs that can be used in the system and to assign the ranges to the various zones. All of the home zone assignments for groups and individuals are compiled into two home zone maps: • Individuals to Home Zone • Groups to Home Zone For example, Zone 1 can be assigned an Individual ID range that can include IDs 1000 - 1999, and a talkgroup ID Range that can include IDs 1-100. Zone 1 becomes the Home Zone to any radio or talkgroup programmed with a corresponding ID from the Zone 1 individual and talkgroup range tables. The figure below shows the home zone mapping window, which is part of the UCM application. The tabs in this window allow you to modify the individual and group home zone maps to associate a range of IDs with a particular zone. The record creates two tables, one for the individual IDs, and a separate table for the talkgroup IDs.

68015000701-C - October 2013

5-3

System Overview

Figure 5-1

UCM Home Zone Mapping Window

A system with a single zone requires that all individual and talkgroup IDs be assigned to Zone 1. IDs mapped to non-existing zones can not be used. Home Zone mapping requires that all IDs be accounted for in the ranges used to create a map. Whether the map consists of one range or 2048 ranges, IDs 0 through 16.777.215 must be assigned to the map.

5.1.1.4 Radio Identification The Radio object is used to create records that contain attributes related to the physical radio unit, such as its unique identity, serial number and interconnect capability. A radio record is required for each radio accessing the system. Objects created in an Elite dispatch operator position that need audio resources when active, such as talkgroup objects, also require a unique identification number. The identification is programmed in the User Configuration Manager. The total range of identification numbers used by the system is 16.777.215. The IDs are distributed as shown in the table below.

5-4

68015000701-C - October 2013

5.1.1.5 Radio User

Table 5-1

Short Subscriber Identity Ranges

ID Type

ID Range

Description

System

0

Reserved for the system.

Individual or Group

1 to 13.999.999

Available for individual or group short subscriber identities (ISSIs or GSSIs). Each ID can identify a unique group or individual. The same ID cannot be assigned as both an ISSI and GSSI.

Alias

14.000.000 to 14.999.999

Available for alias short subscriber identities (ASSIs).

Alias or Fleet

15.000.000 to 15.999.999

Available for ASSIs or Fleet Short Subscriber Numbers (FSSNs).

System

16.000.000 to 16.777.215

Reserved for the system infrastructure ID, gateway IDs, default records, and other system functions.

5.1.1.5 Radio User The Radio User object is used to create records that identify all users on the system and their capabilities. The object can also be used to modify existing records. A radio user record includes specific priority levels and access rights for dispatch and interconnect. To configure a radio user, you must know how they access the system and what capabilities they require for this access. Radio user records rely on the replication of data between the User Configuration Server (UCS) and the Zone Database Server (ZDS). For example, if a site is added to a specific zone in the Zone Configuration Manager (ZCM), it cannot be configured as a valid site in the radio user record until the information has been replicated to the UCS. If that site is deleted from the zone, the ZCM user continues to specify it as a valid site for a radio user until the UCS is notified of the deletion.

5.1.1.6 Profiles A profile is a master list of common attributes or capabilities used by radio users, talkgroups, and multigroups. Creating a profile allows you to enter the information one time and reference the profile from an individual record. One does not have to enter the information separately into each record. You can create a different profile for each type of function and group of users in your system, up to a maximum of 2000 profiles. Using a profile helps to reduce the amount of data that has to flow through the network between the UCM and the Zone Controller. Profile information includes data that relates to radios, radio users, and talkgroups who perform the same function. For example, all radio users associated with the Fire Department require the same resources, so you can use a profile to create a master file for their records. A record can have a one-to-one relationship with a profile (up to the 2000 profile limit), or many records can be mapped to the same profile.

5.1.1.6.1 Radio User Capabilities Profile The Radio User Capabilities Profile object defines access parameters for radio users such as: • Group/Private Call Priority Level • Announcement Call Enabled • Private Call (PC) Enabled • Group Call Enabled

68015000701-C - October 2013

5-5

System Overview

You can use a Radio User Capabilities Profile object to define a set of parameters that are common to a specific group of radio users. Every radio user is assigned a Radio User Capabilities Profile.

5.1.1.6.2 Radio User Valid Sites Profile Radio User Valid Sites Profile object is used to define a list of specific sites in the system the radio user has permission to access. Every radio user is assigned a Radio User Valid Sites Profile. You can use a Radio User Valid Sites Profile record to define a set of sites that are common to a specific group of radio users.

5.1.1.6.3 Radio User Interconnect Profile The Radio User Interconnect Profile object defines interconnect call capabilities for radio users. Every radio user is assigned a Radio User Interconnect Profile. You can use the Radio User Interconnect Profile record to define a set of parameters that are common to a specific group of radio users.

5.1.1.7 Templates A template provides the means to configure a record that can be applied to radio users who need the same set of system access parameters. Templates consist of a combination of attached profiles and parameters set directly on the record.

5.1.1.8 Configuration Updates During system operation, updates are sometimes needed to an existing user configuration information. Changes to a radio user configuration are entered in the UCS. Once entered, the changes are copied to the ZDS in each zone during the database replication process. Each ZDS then distributes the applicable Home Zone information to its Zone Controller; the Zone Controller uses this information to populate its Group Home Location Register (GHLR) and Individual Home Location Register (IHLR). For more information about User Profiles see Radio and Radio User Management.

5.1.1.9 Talkgroup The talkgroup object consists of information that identifies a group of radios that communicate and interact together on the system. Talkgroup and multigroup IDs are selected from the same range of valid IDs that are available for the individual IDs. The total range of identification numbers used by the system is 16.777.218. The IDs are distributed as follows: • ID 0 is reserved by the system and cannot be assigned to a radio, console resource, or group. • 1 - 9.999.999 are valid individual or group IDs. • 10.000.000 - 13.999.999 is the Dimetra extended range for individual or group IDs. • 14.000.000 - 16.777.214 is reserved. • 16.777.215 is used for site wide calls for addressing all units. • 16.777.216 is assigned to the SZ$INIT record. • 16.777.217 is assigned to the SZ$DEF record.

5-6

68015000701-C - October 2013

5.1.1.9.1 TG/MG Capabilities Profile

5.1.1.9.1 TG/MG Capabilities Profile The TG/MG (talkgroup/multigroup) Capabilities Profile object defines the capabilities for a talkgroup or multigroup. You can use the TG/MG Capabilities Profile record to define a set of parameters that are common to a specific talkgroup or multigroup. Each TG/MG Capabilities Profile contains capability parameters that can be customized per configured profile. Every talkgroup and multigroup is assigned a TG/MG Capabilities Profile. For more information on Talkgroup/Multigroup Capabilities Profiles, see Configuration Management, UCM.

5.1.1.10 Object Group Object Group allows to identify a group in the Object Call feature. The Object Group number consists of the prefix and the object number, which further consists of two parts – Subject and Instance. This gives the possibility to distinguish between different groups working with the same subject or to distinguish several instances of a subject. For more information see the Object Call manual.

5.1.1.11 Barring of Incoming/Outgoing Calls The BIC/BOC feature allows to control the permissions of radio users to initiate or receive calls from certain talkgroups. To configure this feature, create a Barring Profile, which specifies the subset of user IDs (SSIs) for which calls will be barred. BIC/BOC can control incoming or outgoing individual calls, group attachment and group call requests. For more information see the Barring of Incoming/Outgoing Calls manual.

5.1.1.12 Multigroup The Multigroup object is used to create records that identify a group of talkgroups that are the target of multigroup announcements.

5.1.1.12.1 TG/MG Valid Sites Profile The TG/MG Valid Sites Profile object defines which sites the talkgroup or multigroup has access permission for in the system. Every talkgroup and multigroup is assigned a Valid Site Profile. You can use the TG/MG Valid Sites Profile record to define a set of sites that are common to a specific talkgroup or multigroup.

5.1.2 Infrastructure Configuration The system object in the UCM configures parameters at the system level. These parameters are common for every zone and may affect all radios in the system. The system record is created when the system is staged for testing at the Motorola facility. Subsequently, the record can be opened to modify the fields that affect operation of the radios in the system. This record includes the system identification, access control timers such as the duration of the message timer for various types of calls, and maximum call duration for group or private calls. Another field included in this record is the Site Access Denial Type. This field works in conjunction with the Radio User Site Access Profile and TG/MG Site Access Profile records. Site access can be allowed or denied to Radio Users and TG/MG through the corresponding Site Access Profile record. The setting chosen for the Site Access Denial field in the system record has a direct impact on radio unit mobility.

68015000701-C - October 2013

5-7

System Overview

The type of rejection depends on the valid sites set for each radio and affiliated talkgroup in the corresponding UCM records. For example, with a site access denial setting of BOTH, if you have a Radio User that is valid at the site but a talkgroup that is not valid, the radio is allowed to register and stay at the site. The radio is allowed to make unit-to-unit calls but requests for a talkgroup call are rejected. Continuing this example, if the mobile user switches to another talkgroup, the radio unit sends another affiliation request, which is accepted or denied based upon the valid site setting for that group. If it is a valid group, the system begins to provide both group and individual call services at that site. Valid site and site access denial are the means by which a system manager can specifically control the operating sites and individual/talkgroup services for each radio.

5.1.2.1 Source Site Adjacent Control Channel The Source Site Adjacent Control Channel (ACC) object in the UCM provides a means to define which sites are in close RF proximity to any given site. ACCs allow a radio to learn about the control channel frequencies, current availability status, and service capabilities of nearby sites. The radios use this information for ranking potential control channel candidates that can be used in the event that the control channel of the current site becomes too weak for acceptable use. Radios attempt to move to one of the adjacent sites based on the control channel ranking.

System engineers create the new Source Site ACC record when configuring the system initially. Subsequent users can only open and modify the existing record. You must consider the ramifications when changing the initial configuration. In large systems, the radio codeplug may not contain all of the frequencies for adjacent sites to which the radio may need to roam. Additionally, new sites may be added to the system and it may be impractical to bring all of the radios in for reprogramming.

Selection and programming of the adjacent sites lists requires detailed knowledge of the systems coverage characteristics. Random selection of sites can severely impact system operation as radios may experience problems accessing the system.

5.2 Mobility Management Mobility Management encompasses the system tasks which track where every active individual and group member is located at any time. It utilizes the information supplied by the static configuration and the information supplied by the radios as they register, access, and move about the system. Individual radios must register at sites in the system. This allows them to make and receive individual-based call services. In addition, radios affiliate with a talkgroup so that they can participate in talkgroup calls and utilize other group-based call services. The system determines whether to accept or deny a registration/affiliation request based on configuration settings which are programmed into their UCM records and in the radio itself. Mobility management is the primary function performed by dynamic user configuration.

5-8

68015000701-C - October 2013

5.2.1 Mobility as Viewed by the Radio

5.2.1 Mobility as Viewed by the Radio To a radio, the system is simply a collection of control channels and sites. The radio constantly monitors its RF environment, and automatically switches to the best site available based upon received signal strength, internal programming and responses to registration and affiliation requests sent to the FNE.

5.2.2 Mobility as Viewed by the Fixed Network Equipment The Fixed Network Equipment (FNE) has two functions in mobility management: • To respond to the registration/affiliation requests from radio units • To track the current zone/site location of each registered individual radio unit and each affiliated talkgroup member To respond to registration/affiliation requests from radio units, the FNE in a zone where the unit is registering needs a copy of the access control information for that individual and/or group. The FNE in each zone also needs a place to store the site location of unit and group member.

5.2.3 How the Location Registers are Created The system uses a distributed processing architecture that shares the call processing load between the Zone Controllers in the different zones. To enable this, the responsibility for storing (and using) the configuration information is also spread among the zone(s) in the cluster. Each individual and group ID is assigned to a zone, based upon ID ranges, in the home zone mapping object in the UCS. The zone assigned to a particular ID is said to be the home zone of this ID. The home zone to which an ID is assigned has an impact on how the system operates. Home zone assignment affects system operation in the following ways: • Configuration information is distributed throughout the system based on the assignment of the home zone to a given ID. A Zone Controller stores only the configuration information for those individual and group IDs that are home to that zone. • For group call services, the home zone of the group is always the controlling zone for the call, regardless of the zone where the group member is currently registered. Depending on configuration, this can impact the number of interzone calls versus the number of single-zone calls that take place in the system. This, in turn, can affect the number of interzone resources that are needed between any two pair of zones. User configuration information is entered in the appropriate objects in the UCS: Radio and Radio User for individuals, Talkgroup and Multigroup for groups. Once entered, user configuration information is replicated automatically to each zone in the cluster, where it is stored in the master database of a zone. The replication process makes it possible, if needed, to use any zone to promote its copy of the user configuration information back to the UCS in the cluster. Next, based on the home zone mapping, each zone transfers the configuration information for its individuals and groups to the Home Location Register (HLR) in the Zone Controller. The home zone mapping information is replicated to each zone from the UCS in the form of map tables. There are two map tables: an individual to home zone map and a group to home zone map. Whenever any individual or group configuration information is needed by any zone, it gets that information from the HLR in the home zone of an individual or a group.

68015000701-C - October 2013

5-9

System Overview

Figure 5-2

Home Location Register

UCS

ZDS

ZDS Zone Controlle r

IHLR

Zone Controlle r IHLR GHLR

GHLR

Zone 1 Zone 2 The HLR stores access configuration information for both individuals and groups along with the current site location of the individual or group member. The VLR is a temporary copy that is placed in the zone where the radio is also present, and is deleted when the radio is shown up in another zone. When a radio is shown up in another zone, a new VLR is created again.

There are two VLRs - one for individuals and one for groups. The individual VLR stores the access configuration information and current site location for each registered individual radio unit in the zone. The group VLR stores the access configuration information for a group that has affiliated members in the zone along with the site location of each affiliated member. Figure 5-3

Home Location Register - Visitor Location Register

UCS

ZDS

ZDS Zone Controlle r

IHLR IVLR

Zone Controlle r

IHLR IVLR

GHLR GVLR

Zone 1

5-10

GHLR GVLR

Zone 2

68015000701-C - October 2013

5.3 Call Processing

All operator positions monitoring a talkgroup and the logging recorders assigned to a talkgroup affiliate with the system. Thus, operator positions and logging recorders have entries in an VLR of the zone.

5.3 Call Processing Call processing is the term used to describe the sequence of processes that service a call request of the radio user. Call processing can be divided into the following phases: • Call request • Call setup • Audio routing • Call continuation • Call teardown

5.3.1 Call Types The following describes several types of voice calls that can be made through the Dimetra IP system. The examples are divided between two main types of call services: • Group-based - Group-based calls are services that provide for effective group (one-to-many) communication. • Individual Calls - Individual calls are services that provide for effective individual (one-to-one) communication. The following describes these five call types using the call processing structure.

5.4 Group-Based Services The Dimetra IP system offers several types of group-based services. The following describes the following five types: • 5.4.1 Talkgroup Call, page 5-12 • 5.4.3 Announcement Call, page 5-18 • 5.4.4 Emergency Services, page 5-19 • 5.4.5 Site Wide Calls, page 5-20 • 5.4.6 Talkgroup Scanning, page 5-20

68015000701-C - October 2013

5-11

System Overview

5.4.1 Talkgroup Call The talkgroup is the primary level of communication in a trunked radio system. Most of the conversations a radio user participates in are talkgroup calls. The following describes in detail call processing for a talkgroup call. Two variations are shown: • An intrazone call - a talkgroup call where all resources are within one zone. • An interzone call - a talkgroup call where resources are in more than one zone.

5.4.1.1 Intrazone Talkgroup Call This is the most common type of call. Home zones are generally assigned to match up to geographic areas where radios are used most frequently, such as a patrol district or management area. When possible, talkgroups and radio users should be configured so that the majority of the calls take place within this geographic area, thus reducing the need for interzone resources.

5.4.1.1.1 Call Request A talkgroup call begins with a call request. The call request resolution determines whether the call is set up or not. A talkgroup call request is initiated when the caller selects the appropriate mode on the radio and then presses the PTT button. • When the caller presses the PTT button, the call request, in the form of an Inbound signaling Packet (ISP) is sent over the control channel to the current site. The information is passed to the Site Controller for processing and routing to the Zone Controller through the site router. • The Zone Controller, for the zone where the request originates, determines if this is a valid call request by checking the access configuration information stored in the VLR. If it is a valid request, the Zone Controller checks its talkgroup-to-home zone map table to see which zone is the home zone of the talkgroup. For group calls, the home zone of the group becomes the controlling zone for the call, regardless of which zone the caller is in when the request is made. When the call request originates from a BTS site, the request is encapsulated as 10Base-T Ethernet packets by the base station and is sent to the Site Controller. The controller then encapsulates the traffic in Frame Relay packets and transmits the traffic to the MSO.

5-12

68015000701-C - October 2013

5.4.1.1.2 Call Setup

Figure 5-4

Intrazone Talkgroup Request from a BTS Site

Dispatch Console

Gateway Router

Zone Controller

LAN Switch

Core Router

BTS

Patch Panel

BTS

5.4.1.1.2 Call Setup Once a valid call request is received, the Zone Controller starts to set up the call: • The Zone Controller checks the VLR to determine talkgroup affiliations and radio location. This information indicates which sites need to participate in the call. • The Zone Controller checks that all needed resources, such as channels at sites and consoles are available to establish the call. See 5.8 Busy Call Handling, page 5-34 for details.

68015000701-C - October 2013

5-13

System Overview

5.4.1.1.3 Call Grant When and where to use: Use the below process to see how to grant talkgroup calls. The figure illustrates the process. Figure 5-5

Talkgroup Call Grant

Dispatch Console

Gateway Router

Zone Controller

LAN Switch

Core Router

BTS

Patch Panel

BTS

Process Steps 1

Routing information is sent to the appropriate MSO and remote site routing equipment.

2

The Home Zone for the call request sets up a core router as the distribution point for the audio information. This audio focal point is known as the Rendezvous Point (RP) and its router becomes the Rendezvous Point router. The Rendezvous Point for intrazone audio is the core router.

3

Channel assignments are sent to the needed sites.

4

The Site Controllers in the BTS sites broadcast the channel assignment, through the main control channel (MCCH), to the radios and send the activation message to the assigned traffic channels. The assigned traffic channels send a join message back to the MSO.

5

The sites cause the activation of the receive and transmit circuits in the designated traffic channels.

6

The receiving radios tune to the assigned traffic channel at their respective sites.

7

The requesting radio electronically activates its transmitter.

5.4.1.1.4 Intrazone Talkgroup Call Audio Routing When and where to use: The process below explains voice communications, when the call is set up.

5-14

68015000701-C - October 2013

5.4.1.1.5 Talkgroup Call Continuation and Teardown

Process Steps 1

When the radio user speaks into the microphone of the radio, the radio converts the speaker's analog audio into ACELP and transmits the signal to the assigned traffic channel.

2

The audio signal is transmitted by the radio over the assigned frequency to the caller's site and received by the assigned traffic channel.

3

The traffic channel places the audio into the site's Ethernet LAN as IP packets and routes the audio signal through the site router to the assigned rendezvous point router (core router) at the MSO.

4

The rendezvous point router forwards the audio to any device that responded with a join message to the Zone Controller's call grant. The BTS base radios respond with a join message.

5

The talkgroup members already locked on to the traffic channel receive the audio.

5.4.1.1.5 Talkgroup Call Continuation and Teardown When and where to use: When the original speaker releases the PTT button, a control message is sent over the traffic channel. This message is extracted from the audio stream by the remote site and forwarded to the Zone Controller.

Control information flows continually during a call: over the control channel during call setup and embedded in the digital audio signal during the active call phases.

Process Steps 1

When the speaker releases the PTT button, a message is sent to the controlling Zone Controller. If the call is message trunked, a message hang time timer starts when the message is received. All system resources, previously assigned to the call, are held available during the timer's hang time period.

2

If a person responds to the initial caller, by pressing the PTT button within the hang timer period, the call continues. The message hang timer is reset and the new speaker's audio is routed as the source audio using the traffic channels and router assignments already allotted for this call.

5.4.1.2 Interzone Talkgroup Call The difference between an interzone call and an intrazone call is the other Zone Controllers that must be included in the call control process. In an interzone call, each zone controls its local resources in a similar manner to the previously described intrazone call. However, because the controlling zone must coordinate with the needed participating zones prior to granting the call, there is much more activity during the call request and setup phases.

68015000701-C - October 2013

5-15

System Overview

5.4.1.2.1 Interzone Talkgroup Call Request The call request is sent by the radio over the control channel at the local zone and site when the radio user presses the PTT button. This request is relayed through the remote site to the local Zone Controller. Based on the talkgroup ID information in the call request, the Zone Controller receiving the request checks its VLR and determines if the requester is able to make the call. The Zone Controller then checks the talkgroup-to-home zone map and determines if it is the home zone (and thus the controlling Zone Controller) for the call. If it is the home zone, the local Zone Controller becomes the controlling Zone Controller and takes responsibility for the call. The call request is acknowledged, and the controlling Zone Controller begins to set up the call. If the receiving zone is not the home zone, the call request is passed on to the appropriate Zone Controller, which accepts control of the call and becomes the controlling Zone Controller for the call (see figure below). Figure 5-6

Interzone Call Request

Zone 1

Zone 2 Dispatch Console

Gateway Router

Zone Controller

LAN Switch

Core Router

BTS

Gateway Router

Zone Controller

LAN Switch

Exit Router

Patch Panel

Exit Router

Core Router

Patch Panel Patch Panel

BTS

5.4.1.2.2 Interzone Talkgroup Call Setup The controlling Zone Controller determines which zones must be included in the call and sends a message to the appropriate Zone Controllers, requesting their participation in the call. All interzone call control messages between any pair of Zone Controllers goes over the Interzone Control Path between those two zones. There is an active Interzone Control Path between any two zones in the system. Each Zone Controller checks its VLR to determine which sites, along with which fixed resources, should be included in the call, and if all the resources are available to set up the call. The call is busied if any zone cannot participate due to lack of resources. If all the resources are available, the participating Zone Controllers acknowledge their participation back to the controlling zone. When all participating zones acknowledge the call request, the controlling Zone Controller grants the call. The grant message is sent to each participating zone through its active Interzone Control Path with the controlling zone. At this point, each zone is responsible for setting up the resources within its zone. Within each zone, the Zone Controller: • Assigns traffic channels at the appropriate sites within its zone. • Assigns the necessary audio resources and sends multicast addresses.

5-16

68015000701-C - October 2013

5.4.1.2.3 Interzone Talkgroup Call Audio Routing

• Notifies the consoles of the talkgroup call and its audio source, if needed. The Zone Controller relays the audio assignments and the channel assignments to the appropriate remote sites through their site control paths. • Once the resources are assigned, the rendezvous point router becomes the centre of control for audio distribution. At each site the Site Controller: • Activates the site assigned as the traffic channel. • Sends the traffic channel assignment to the affiliated radios over the control channel. The assigned traffic channel at RF sites send a join message to the RP after they receive the multicast address. As resources are set up in each zone, the radios in the talkgroup in each zone switch to the assigned traffic channel. The initiating user's radio activates the transmit circuitry and begins sending the audio to the receiver at the assigned traffic channel.

5.4.1.2.3 Interzone Talkgroup Call Audio Routing When the transmitting user speaks into the microphone, the audio signal is transmitted on the assigned traffic channel frequency and received by the site, which routes the audio stream to the core router at the local MSO. The core router relays the audio signal to the assigned sites through their remote site router, to the consoles and over the assigned interzone resources to the exit routers in the participating zones. The exit routers in the participating zones then route the audio to the core LAN switch , the core router, gateway router, consoles in their respective zones, and the assigned sites. The sites transmit the signal to the members of the target talkgroup.

5.4.1.2.4 Interzone Talkgroup Call Continuation and Teardown When the original speaker releases the PTT button a control message is sent over the traffic channel. This message is extracted from the audio stream by the remote site and forwarded to the controlling Zone Controller. In transmission trunking mode, the call is ended after the PTT released message is received. In message trunking mode, however, the controlling Zone Controller starts the message hang-time timer upon reception of the PTT released message. If another user in the talkgroup responds to the call within the hang-time period, the controlling Zone Controller receives the new call request (either from a site in its zone or from a participating Zone Controller), sees that it is for a talkgroup that has an active call, and continues the call using the resources currently assigned to the talkgroup. The audio source is the only resource change in this instance. The call is ended when no one from the talkgroup keys-up within the message hang-time period. The controlling Zone Controller sends a message to each participating zone to tear down the call. Each zone goes through the teardown process, disabling the audio and marking the resources used in the call as available for other call assignment.

5.4.1.2.5 Roaming During a Talkgroup Call When a receiving radio user in an active talkgroup call roams into a new zone, the call is continued automatically. Depending upon whether or not resources, such as a traffic channel, are available to set up the call at the new site, the roaming user experiences the following conditions: • If resources are available at the new site and the talkgroup call is already active in the new zone (there are talkgroup members at sites within the zone), the roaming user experiences a short loss of audio while the call is set up at the new site. • If resources are available in the zone to set up the call but the talkgroup call is not active (there are no affiliated talkgroup members in that zone), the roaming user experiences a longer loss of audio while the interzone call setup process takes place. The access control information needs to be transferred from the

68015000701-C - October 2013

5-17

System Overview

home zone HLR to the HLR in the new zone and from there to its VLR, the call request validated in the new zone, and a channel assigned and activated at the new site. • If resources are not available at the site or in the zone, the call continuation request to the new zone is placed in its busy queue. When the needed resources become available, the roaming user rejoins the call in process. A longer loss of audio occurs in this case.

5.4.2 Object Call The Object Call is a feature that allows to communicate with a talkgroup which is not permanently configured in the radio. A user on a radio terminal is able to call a group she or he is not member of, stay in the group, and push-to-talk into the group when needed. The radio will request attachment and temporary calls (group calls without being attached to the talkgroup) on object groups using private call signalling and the Switching and Management Infrastructure (SwMI) recognizes such Object Call requests by prefixes in the target number. Talkgroups defined for use with Object Call are called Object Groups for short. Object Groups are defined in a 2-dimensional structure and for each dimension the feature implicitly generates container talkgroups consisting of all the Object Groups sharing the same property in that dimension. Thus, any Object Group is part of 2 such container groups. For more details see the Object Call manual.

5.4.3 Announcement Call An announcement call involves all the radios assigned to a multigroup. A radio or dispatch console can initiate the announcement call selecting the multigroup. Any radios affiliated to any of the talkgroups assigned in the multigroup receive the call. Audio for an announcement call is routed through the infrastructure in the same manner as a talkgroup call.

The multigroup and all talkgroups in the multigroup must have the same home zone assignment.

All call requests in the busy queue for the affected radios are dropped. Multigroup information is programmed in two places: • One Multigroup per personality can be programmed in the radios. • Multigroup records must be created in the UCM database identifying the Multigroup itself as well as the individual talkgroups associated with that Multigroup. A radio unit with the selector in the Multigroup mode position can monitor talkgroup activity for talkgroups associated with the selected multigroup if and only if the monitored talkgroups have an affiliated member in the same zone as the monitoring radio. The system does not pass audio between zones exclusively for a unit that is scanning talkgroup activity while in multigroup mode.

5-18

68015000701-C - October 2013

5.4.3.1 Multi-Select (MSEL) and Patch Calls

5.4.3.1 Multi-Select (MSEL) and Patch Calls Multigroup calls can also be set up dynamically by dispatch operators by using the multi-select (MSEL) and patch features. The MSEL feature allows a dispatch operator to drag talkgroup icons into a resource window. The dispatch operator is then able to transmit to all the selected talkgroups simultaneously. The call to each talkgroup is then terminated when the dispatch operator releases the PTT. The patch feature allows a dispatch operator to assign talkgroups to a patch resource. The patch remains in effect until the dispatch operator explicitly terminates the patch. Each time a radio or dispatch operator transmits to the patched talkgroups, a call is established with all the patched talkgroups.

5.4.4 Emergency Services There are two types of emergency services: • Emergency alarm- A radio to console or Radio Control Manager (RCM) function that is sent over the control channel. • Emergency call- A radio or console call function.

5.4.4.1 Emergency Alarm When the emergency button on a radio is pressed, an emergency alarm is transmitted through the control channel. This alarm is forwarded to any consoles monitoring the radio's currently selected talkgroup or multigroup. Any RCM positions that are active, and have the currently selected talkgroup or multigroup as part of their list of attachments, also receive and display the emergency signal. If an RCM User is configured to receive "unattended emergency alarms", they may receive emergency alarms from radios whose talkgroups or multigroups are outside of their list of attachments, if there is no other RCM User online to receive the emergency alarm. The radio can be configured to enter emergency call mode automatically when the emergency button is pressed.

5.4.4.2 Emergency Call An emergency call is a specialized, high-priority version of a talkgroup or announcement call. Emergency calls always have the highest priority in the system. When an emergency call request is made, the request takes priority over any other type of call request. The emergency call can be programmed in the radio as tactical or revert. When programmed as tactical the call is made on the radio's currently selected talkgroup or multigroup. When programmed as revert, a talkgroup ID that identifies the user's emergency talkgroup must be programmed in the radio. If a traffic channel is not available at the requestor's site, ruthless preemption is used to assign a traffic channel. The lowest priority call at the site is terminated, and the traffic channel is granted to the emergency caller. An emergency call is routed to all affiliated talkgroup or multigroup members, including all console positions and logging recorders affiliated to talkgroup or multigroup. All needed resources for receiving sites are ruthlessly preempted. Once an emergency call is granted, it is handled by the system as a talkgroup call although emergency calls are message trunked with their own longer hang-time timer setting. The range for this timer is 0 to 3660 seconds, the default message hang-time for an emergency call is 30 seconds.

68015000701-C - October 2013

5-19

System Overview

A value of 3660 disables the message timer for emergency calls. Radio Users have unlimited time between PTTs. A console operator can initiate an emergency call on any talkgroup or multigroup being monitored. The system handles a console emergency call request the same as a radio-generated request, with one exception: a console generated emergency call has an unlimited hang time, so the call stays active until the operator “knocks down” the emergency call at the operator position.

Emergency calls initiated from the console are always processed in Ruthless Preemption mode when resources are not available to grant the call immediately.

5.4.5 Site Wide Calls A site wide call involves all the radios registered with a particular site at the time of the call. A site wide call reaches the radios registered with the site regardless of their talkgroup affiliations. Only dispatch consoles can initiate a site wide call.

5.4.6 Talkgroup Scanning Talkgroup Scanning and Priority Group Monitoring are closely related features. Priority Group Monitoring is an attribute of a TG defined within the infrastructure. A Priority Monitor TG can pull a user monitoring another TG call with a lower priority as defined within the radio unit, out of the call. Talkgroup Scanning is a best effort service in the radio, where the radio monitors talkgroup activity on a configurable list of groups at the site where the radio is registered. When no group activity exists for the MSs selected TG or associated multigroup and the radio is either idle on the MCCH or active on the PDCH and a call is initiated to a TG defined in the active scan list, speech is heard in the loudspeaker of the radio unit and the call is monitored. When a radio is active on the PDCH the data transfer is interrupted to join the group call and resumed when the group call ends. Note that a radio unit only receives call setup request for scanned groups if another radio at the same site has attached to the TG as it’s selected TG or if the site is configured as a critical site for the TG. When the radio is on the PDCH, another radio is required to be active on the PDCH at the same site and attached to one of the scanned groups as its selected TG before the setup is signaled on the PDCH. While monitoring a call, the radio unit responds to a new call setup to TGs in the active scan list, to the radios selected TG and associated multigroup, if the setup is to a group with higher scanning priority than the monitored call. The group identity of the TG being monitored is displayed in the radio unit's display. Note however that group calls are only signaled on the TCH of another call, when the new call is configured as a Priority Monitor group or the group call is an emergency call. During an active call the monitoring user may wish to participate in the call. When the monitored call is the selected TG (affiliated group) or associated multigroup of the served user, the operation of PTT results in a transmission request (normal operation) to this TG. However, for all other monitored calls, operation of PTT only results in a transmission request to the monitored TG when the radio is configured to "TalkBack" to the current active group call. Since scanning is always a best effort service at the radio, the end user should make a critical group its selected group. If groups are critical as far as the system administrator or network operator is concerned, these groups can be configured as Priority Monitor groups in the UCM and critical sites can be defined in the UCM as required when setting up the group call.

5-20

68015000701-C - October 2013

5.5 Individual Call Services

5.5 Individual Call Services Individual call services are available through the Dimetra IP system. The controlling zone is determined in a manner different from that used for group-based calls for this type of call service. In an individual call, the controlling zone is determined by the first radio to transmit audio. The following describes the call process operations for individual-based calls.

In individual calls, the initial call request goes over the control channel. An audio channel is not assigned until the target radio responds to the initial request. Audio channel resources are assigned once the target radio responds to the call request.

5.5.1 Private Call Request The below figure graphically represents a private call request within a single zone. Note that it is also possible to make private calls across zones. Figure 5-7

Private Call

Gateway Router

Zone Controller

LAN Switch

Core Router

BTS

Patch Panel

BTS

A private call begins with a call request. The call request resolution determines whether the call is set up or not. Requests are rejected if the target radio does not respond to the request or if the target radio is not registered with the system. Other reasons for a call to be rejected would be configuration-related (one of the radios blocked from private calls, site not allowed, and so on).

5.5.1.1 Private Call Request Flow When and where to use: The process below explains a private call request.

68015000701-C - October 2013

5-21

System Overview

Process Steps 1

A private call request is initiated when the caller selects the appropriate mode on the radio, and then enters the target radio's ID or selects it from a list.

2

When the caller presses the PTT button (semi-duplex) or presses the send button (full-duplex), the call request is sent over the control channel to the current site. The information is passed to the Site Controller for processing and routing to the Zone Controller at the initiator's MSO.

3

The Zone Controller receiving the call request checks its VLR to see if the requesting individual is configured to make private calls.

4

If the call is allowed, the Zone Controller checks its individual VLR to see if the target radio is currently registered in the zone, and if it is, at which site.

5

If the target radio is active (registered) in the same zone, the Zone Controller sends it a private call request over the control channel at its current site.

If the target radio is not in the current zone, the caller's Zone Controller determines the target radio's home zone by checking its individual-to-home zone map. 6

The caller's Zone Controller sends a message to the target radio's home Zone Controller requesting the current location of the target radio (which the home Zone Controller gets from its individual HLR).

7

Once the target radio's current zone is known, the receiving Zone Controller sends the call request to the Zone Controller in that zone.

8

The target radio's Zone Controller checks its individual VLR for the target's site location and sends the call request to the target radio through the control channel at its current site.

9

If the target radio is not registered with the system, the requester receives a call reject. Otherwise, the requester hears a ringing tone. If the target radio does not respond within the time-out period, the call request is ended.

10 If the target radio responds to the call request, the private call is set up.

5.5.1.2 Intrazone Private Call Audio Flow, Call Continuation, and Teardown When and where to use: This process describes the situation in which the private call connection is already established. See 5.5.1.1 Private Call Request Flow, page 5-21 for details.

5-22

68015000701-C - October 2013

5.5.1.3 Roaming During a Private Call

Process Steps 1

Audio is received by the assigned traffic channel at the local site and is routed to the RP at the zone.

2

The RP routes the audio packets through the exit routers where they get encapsulated as Frame Relay packets for transmission to the participating sites.

3

When the target user responds, the same path is used, but the source and destination of the audio are swapped.

4

For semi-duplex calls, the call is terminated when neither party responds within the defined message hang-time. Full-duplex calls are terminated when either party presses the end button.

5.5.1.3 Roaming During a Private Call The Dimetra IP system supports call continuation during roaming for private calls. When a non-transmitting radio user roams to a new site during a call, the audio is redirected automatically to the new site. The radio user experiences a brief interruption of the audio when moving to another site within the same zone. The audio interruption when moving to a site in a new zone may be slightly longer.

A transmitting radio user in an active individual call cannot roam automatically. When a transmitting radio fades out (due to moving away from the current site), the system detects the loss and begins the call termination process.

5.5.1.4 Full-Duplex Private Calls Radios or dispatch consoles can initiate full-duplex private calls, allowing both parties to simultaneously transmit and receive audio. Full-duplex private calls are supported for radio-to-console, console-to-radio, and radio-to-radio. For a radio to initiate a full-duplex private call, it must be configured with permission to do so through UCM. For full-duplex private calls, there is no hang timer that determines when the call is terminated. The call is initiated when the radio presses the send button, and the call terminates when one of the parties presses the end button. Full-duplex operation is simulated in the radio by switching between the uplink and downlink channels within each TDMA frame.

5.5.2 Telephone Interconnect Telephone interconnect capability allows radio users to initiate and receive full-duplex calls through a connection to the Public Switched Telephone Network or customer Private Automatic Branch Exchange. Besides the usual system infrastructure, telephone interconnect service requires a Motorola Telephone Interconnect Gateway, and customer-supplied Private Automatic Branch Exchange.

68015000701-C - October 2013

5-23

System Overview

To PABX

Figure 5-8

Telephone Interconnect in E1 networking

Dispatch Console

MTIG-E1 Zone Controller

Gateway Router

EC LAN Switch

Core Router Patch Panel BTS The telephone interconnect feature builds upon all of the configuration and infrastructure discussed up to this point. With talkgroup calls and unit-to-unit calls, all parties to the conversations all reside somewhere on the Dimetra IP system. For telephone interconnect calls, one of the parties is outside of the Dimetra IP system and is connected through landline telephone to the radios in the system.

The Dimetra IP system supports radio-to-landline and landline-to-radio interconnect calls. It does not support interconnect calls to and from talkgroups.

5.5.2.1 Relationship between Components The Zone Controller uses call control client software to interface with call control server software running on the Motorola Telephone Interconnect Gateway. The call control server software translates the Zone Controller’s commands into a format compatible with the PABX and forwards them to the PABX. In this way, the Zone Controller communicates to the PABX so that telephone interconnect calls can be made from radios to the PSTN, and from the PSTN to individual radios. In addition to audio transcoding, the Telephone Interconnect subsystem supports the generation of Dual Tone Multi-Frequency (DTMF) overdial tones (touch-tone), and other messaging tones (end-of-call warning). It is done using tone generation client and server software installed on the Motorola Telephone Interconnect Gateway. The MTIG is used for the tone generation, since digital radios cannot generate their own overdial tones (touch-tones). The tone generation capability is essential for accessing automated voice mail systems, or other types of automated resources in the PABX/PSTN network.

5-24

68015000701-C - October 2013

5.5.2.2 Configuration

5.5.2.2 Configuration Radios must be properly programmed to make and receive telephone interconnect calls.

5.5.2.2.1 Limiting Access to Interconnection Services Telephone interconnect services are intensive users of system resources. Each call requires a single channel which is dedicated for the duration of the call, and telephone calls typically last longer than talkgroup calls. Because of this fact, and because of direct toll costs, it is essential that you have the ability to limit the use of this feature.

Limiting Interconnect Calls Through Radio and User Configuration Radios can be programmed so they can receive telephone interconnect calls, but not initiate them. Radios can also be programmed with specific call lists (telephone numbers) and configured to prevent users from calling non-programmed telephone numbers.

Individual Interconnect Profiles Each radio is assigned an interconnect profile (the Radio User Interconnect Profile object in the UCM). The profile is created in the UCM and assigned to the radio user. Your system may have various individual interconnect profiles available for assignment to radio users. One of the settings in the individual interconnect profile specify a Priority Level. The system uses priority levels to determine the assignment of system resources during busy periods. There are ten levels of priority available, levels 1 through 10. The highest priority, level 1, is reserved for emergency calls. A telephone interconnect call can be assigned a priority level 2 through 10, depending on individual requirements. Level 2 is the highest assignable priority, while level 10 is the default priority setting. See 5.8 Busy Call Handling, page 5-34 for more information on how busied calls are handled by the system.

Limiting Interconnect through Infrastructure Configuration In addition to individual radio programming, the infrastructure can be configured to limit telephone interconnect services. This can be done through the Shared Service object and the Zone object in ZCM.

Enabling or Disabling Interconnect Based on Shared Service Table-Driven Shared Service feature is a method of balancing telephone interconnect capability with dispatch traffic. It allows the system manager to specify the maximum number and duration of interconnect calls which are allowed at any given time for each site. This is done using the Level of Service (LOS) object in the ZCM. A number of LOSs can be configured with different settings for maximum numbers and maximum duration of calls. These levels of service can then be assigned individually for two-hour time blocks throughout the day in the Shared Service object of the ZCM. Each site is configured with its own table.

Limiting Interconnect Call Duration at the Zone Level The Maximum Interconnect Call Duration timer is set in the Zone object of the ZCM to control the duration of an interconnect call. Before the interconnect call exceeds this time, an alert tone is generated to indicate that the call is about to end. When the warning period expires, the interconnect call is terminated.

68015000701-C - October 2013

5-25

System Overview

5.5.2.2.2 Call Setup Restrictions The following is a list of call setup restrictions: • The request for an interconnect call is placed in the busy queue if the radio initiates the call and no channel resources are available. • If no MTIGs are available, interconnect calls are busied until one becomes available. This means that the call is placed in a queue and can be active as soon as an MTIG becomes available. • Regardless of the infrastructure configuration, user limitations, or channel availability, programming of the radio can prevent interconnect calls from being attempted. • If shared service dictates that an interconnect call needs to be placed in the busy queue, the call is placed in the queue, even if there is a channel available at the site.

5.5.2.2.3 Radio-to-Landline Interconnect Calls Radio-to-landline calls are initiated with a request that includes all dialed digit information for the call. This allows the system to check dialing restrictions before granting the traffic channel for the call. Restricted phone numbers results in a denial of the interconnect call request.

Call Setup When and where to use: This process describes the events that occur during the setup of a successful radio-to-landline call.

5-26

68015000701-C - October 2013

5.5.2.2.4 Landline-to-Radio Interconnect Calls

Process Steps 1

The radio user initiates a telephone interconnect call according to how this is done on the specific type of radio.

2

The radio sends a telephone interconnect service call request over the control channel with the dialed digits information.

3

The system verifies that the radio is authorized for telephone interconnect service.

4

The system determines which zone's telephone interconnect is used for the call. The location of the Motorola Telephone Interconnect Gateway determines the controlling zone for the call, the point where the multicast addresses originate, and the location of the RP for the call.

5

Radio system resources are assigned to the call. The resources include the site where the radio is located, a gateway router for distribution to the network, resources in the MTIG for audio conversion between ACELP and PCM, and for timeslot or speech channel access to the external network.

6

The Zone Controller sends two multicast addresses, one for the receive side of the call and one for the transmit side. Transmission of the multicast addresses sets up the audio RP.

7

The MTIG and sites send a join message to the RP for the assigned multicast addresses.

8

The system checks the telephone number dialed to verify that the number represents a valid telephone number and that dialing restrictions allow the radio to initiate calls to the dialed telephone phone number.

9

A PABX-to-PSTN resource is selected for the call.

10 The PABX initiates the call to the PSTN. 11 Radio system resources are granted for the call. 12 The radio switches to the traffic channel. 13 The caller hears a ringing tone to indicate that the call is being placed.

5.5.2.2.4 Landline-to-Radio Interconnect Calls A telephone user initiates a landline-to-radio call by calling an access number. The system automatically locates the target radio, regardless of the radio's current zone registration, and routes the call through the network to the target radio. The radio must be registered in a site which is in wide-area trunking.

5.5.2.3 Telephone Interconnect Call Continuation/Call Maintenance When a radio-to-landline or landline-to-radio interconnect call is established, the radio moves over to the assigned traffic channel for the duration of the call. If necessary, the radio can move to the control channel to perform special functions, such as a fade condition, or to send a request to cancel the interconnect call.

68015000701-C - October 2013

5-27

System Overview

5.5.2.4 Telephone Interconnect Call Termination and Call Teardown Either the radio or the landline party can terminate a telephone interconnect call by hanging up. Either party is able to terminate the interconnect call when the call is in the active state, or at any point during the call setup process. An active call can be terminated by the system in the following cases: • The duration of an interconnect call exceeds a configured call duration limit. • Emergency group calls occur. • Priority monitored calls occur.

5.5.2.4.1 Radio-Initiated Termination During Active Interconnect Call The system can accommodate call termination requests sent on either the control channel or the traffic channel. Motorola brand radios send these requests over the control channel. If the radio is turned off during an interconnect call (active call, or while in a call setup state), the radio automatically cancels the interconnect call before deregistering from the system and powering down.

5.5.2.4.2 Landline Initiated Termination During Active Interconnect Call When the landline caller hangs up during an active interconnect call, the MTIG notifies the Zone Controller to terminate the call.

5.5.2.4.3 System Initiated Interconnect Call Termination The system can terminate a telephone interconnect call that exceeds one of the system timers. This is controlled by setting the Maximum Interconnect Call Duration timer in the Zone Configuration Managers (ZCM) zone object, in conjunction with the shared services configuration and current system loading. The system also disconnects an interconnect call if the participating radio does not rekey within a set time period. • Prior to automatic call termination, the system notifies both parties using an end-of-call warning tone. • After a set interval of time (set by the Interconnect Final setting in the ZCM Zone Configuration tab), the call is terminated.

5.5.2.5 Roaming During a Telephone Interconnect Call A radio can roam from one site to another during an interconnect call. This can occur during an active call, while the call is being set up, or while in a queued state. The following describes how roaming affects an active interconnect call, an interconnect call in a call setup state, or an interconnect call in the process of being terminated. For each scenario, there are several possibilities that can occur once the radio has roamed to the new site, depending on variables such as resource availability at the new site, and whether or not the radio is “valid” for this individual call activity at the new site. It is assumed that the radio has previously performed a full registration on the system.

5.5.2.5.1 Roaming During an Active Interconnect Call If a radio roams during an active interconnect call, the following takes place: • The Zone Controller determines whether the radio is valid for individual services at the new site, and that the new site is capable of interconnect service.

5-28

68015000701-C - October 2013

5.5.2.5.2 Roaming during queuing of Telephone Interconnect Call

• If the required resources at the new site are available, the Zone Controller grants the call immediately. • If the required resources at the new site are busy, the Zone Controller places the call in a busy queue. The landline user is not notified about the busy condition of the call.

5.5.2.5.2 Roaming during queuing of Telephone Interconnect Call If the Zone Controller determines that the required resources are not available during the setup of a radio-to-landline or landline-to-radio call, the call is dropped.

5.5.2.5.3 Roaming While Ringing for Landline-to-Radio Call If the radio roams while ringing for a landline-to-radio call, the call is dropped.

5.6 Short Data Services When and where to use: The ATS application is a purchasable optional software that can be used in a system to send text messages of maximum 500 characters in ASCII or 250 characters in Unicode from a host to a display on a radio and vice versa. For these messages a consumed report can be requested. Also broadcast messages can be sent to Individuals and Groups in selected regions. Short data traffic can be delivered concurrently with voice traffic or packet data traffic. Figure 5-9

Short Data Services

Gateway Router

Data Gateway (SDR)

LAN Switch

Core Router

BTS

68015000701-C - October 2013

Patch Panel

LAN Switch

Exit Router

Exit Router

Core Router

Patch Panel Patch Panel

BTS

5-29

System Overview

Process Steps 1

The radio, remote data terminal, or host creates a message, selects the Short Subscriber Identity (SSI) of the recipient, and sends the message. If a radio is sending the short data message, the message is delivered over the control channel.

2

The short data message is delivered to the short data router (SDR) within the cluster.

3

The SDR observes the SSI for the recipient of the message and checks the IHLR/VHLR information to determine where the recipient is located.

4

The SDR routes the short data message across the network to the intended recipient (host or radio).

5.6.1 Short Data Store and Forward A Store and Forward Server (SFS) hosts the S&F service and is colocated on the same platform along with the SDR. The SFS communicates with the SDR via a loopback IP address. The SFS is not connected to any other device in the Dimetra system. The installation of the SDR and SFS software is common and carried out during a one process. The Store and Forward Service is primarily implemented on the SFS, that is a Data Add-On Service (DAOS) extension to the SDR. It means that the SFS is colocated on the SDR, for example the Store and Forwards functionality and the SDTS/SDR functionality are deployed on the one physical device.

5.6.2 SDS in Local Site Trunking Short Data Services in Local Site Trunking feature enables a stand-alone base station working in LST mode to provide basic Short Data Services. This feature allows radios within one site to communicate with SDS messages. More detailed information about the SDS in LST can be found in Data Subsystem manual.

5.7 Authentication and Air Interface Encryption The Dimetra IP system supports authentication and air interface encryption to provide a level of security against different threats to the system such as theft of service, impersonation, denial of service attacks, and eavesdropping. Authentication and air interface encryption options in the Dimetra IP system include the following: • Authentication only • Authentication and air interface encryption (using TEA1) • Authentication and air interface encryption (using TEA2) • Authentication and air interface encryption (using TEA3) If a system includes both authentication and air interface encryption, either service can be enabled or disabled. The Dimetra IP system allows the following modes of system operation: • Authentication enabled and air interface encryption enabled • Authentication enabled and air interface encryption disabled • Authentication disabled and air interface encryption enabled

5-30

68015000701-C - October 2013

5.7.1 Authentication

• Authentication disabled and air interface encryption disabled

5.7.1 Authentication Authentication is used to verify that a radio accessing the system is valid, and to reject any unauthorized parties from accessing the system. The Dimetra IP system uses a challenge-response-result protocol to authenticate both the radio and the infrastructure. The authentication process begins with the infrastructure sending a challenge to the radio. The radio calculates a response based on the challenge, and sends the response to the infrastructure. If the response from the radio equals the expected response by the infrastructure, then the infrastructure indicates that the authentication result is successful and grants access to the system. If the response is not correct, then the infrastructure indicates that the authentication result has failed and rejects access to the system. Figure 5-10

Authentication

When the radio provides the response described above, and the radio supports mutual authentication, the radio also provides a challenge to the infrastructure. The infrastructure generates a calculated response to the radio to verify that it is genuine. If the infrastructure's result matches the result expected by the radio, then the radio indicates that the authentication result is successful to the infrastructure. On receipt of this successful indication, the infrastructure grants access to the system.

5.7.2 Air Interface Encryption Air interface encryption provides security for RF signaling between the infrastructure and radios. Air interface encryption is achieved by using a common encryption key in both an infrastructure base station and a radio, allowing the devices to encrypt traffic and decrypt traffic from one another. Air interface encryption can be applied to control, voice, and data traffic. Options can be purchased to support TETRA Encryption Algorithm 1 (TEA1), TETRA Encryption Algorithm 2 (TEA2) or TETRA Encryption Algorithm 3 (TEA3). The transmitting station uses the key and an offset value in an algorithm to encrypt the stream of traffic. The receiving station uses the same key and offset value through an algorithm to decrypt the stream of traffic. A proportion of the MAC header for the packets remain clear throughout the encryption process. An example of this process is shown in the figure.

68015000701-C - October 2013

5-31

System Overview

Figure 5-11

Encryption of Traffic

MAC He a de r Cle a r P a yloa d

Ke y Offs e t

MAC He a de r

Encryption Algorithm

Encrypte d P a yloa d

5.7.2.1 Security Classes Dimetra security is defined in terms of class. Each class has associated, mandatory or optional, features. Security classes and features associated with them are presented in the table. Table 5-2

Security Classes

Class

Authentication

OTAR

SCK Encryption

CCK/DCK Encryption

GCK

Enable/Disable

1

O

O (see note 3)

-

-

-

O

2

O

O

M

-

-

O O† O†

3

M (see note 1)

M (see note 2)

O

M

-

3G

M (see note 1)

M (see note 2)

O

M

M

M = Mandatory O = Optional - = Does not apply † = Recommended NOTE 1: Authentication is required for generation of DCK. NOTE 2: OTAR for CCK is mandatory, for other keys management OTAR mechanism is optional. NOTE 3: Required if key material is either distributed in preparation for security class transition, or during cell reselection to a cell of a different security class.

5-32

68015000701-C - October 2013

5.7.2.1.1 Security Class 1(SC1)

5.7.2.1.1 Security Class 1(SC1) A system operating as being Security Class 1(SC1), refers to a system operating with no air interface encryption at all.

5.7.2.1.2 Security Class 2 (SC2) A system operating as being Security Class 2 (SC2), refers to a system operating with SCK air interface encryption and TM-SCK OTAR or DM-SCK OTAR. If a system is prevented from running SC2 then a radio is not granted access when SC3 is not possible, see 5.7.2.1.3 Security Class 3 (SC3), page 5-33.

Encryption with the Static Cipher Key (SCK) The base stations and radios are provisioned with 32 Static Cipher Keys (SCKs). The system uses one SCK at a time, and broadcasts the number of the SCK (SCKN) that is currently being used in the system, between 0 and 31, to the radios. The radio selects the appropriate SCK (from its provisioned list of SCKs) to decrypt traffic from the infrastructure. The base station and radio use the SCK along with an offset value to encrypt and decrypt traffic from one another. SCK is used as a fall back encryption scheme when DCK/CCK air interface encryption is not possible (e.g. no authentication service, during site link failures, during interzone link failures, and so on). The SCK is also used when the authentication option is not installed or enabled. Dimetra supports a dynamic key change of SCK over the air interface using an On-The-Fly (OTF) mechanism.

5.7.2.1.3 Security Class 3 (SC3) A system operating as being Security Class 3 (SC3), refers to a system operating with DCK and CCK encryption, with TM-SCK used as fallback.

Encryption with the Derived Cipher Key (DCK) The Derived Cipher Key (DCK) is generated as a result of the authentication process, providing a unique encryption key for the radio. After authentication, the radio stores its calculation of DCK and a copy of DCK is stored in the infrastructure. The base station and radio use the unique DCK along with an offset value to encrypt and decrypt traffic from one another. DCK is not used for group calls. However, DCK supports group call services by allowing over-the-air rekeying of the Common Cipher Key (CCK) that sent to radios to use for encryption of group calls. DCK can only be used when authentication is installed and enabled in the cluster. A new DCK is created each time the radio authenticates with the system.

Encryption with the Common Cipher Key (CCK) The Common Cipher Key (CCK) is used to encrypt traffic for group calls. All radios registered on a cell share the same CCK for group calls. When an authenticated radio registers it requests that the infrastructure sends the current CCK (sealed with DCK) for use in protecting group calls and providing encryption of address identities. The radios decrypt CCK using their local calculation of DCK (from authentication). The Base Station and radio use the CCK along with an offset value to encrypt and decrypt traffic from one another. Identities used across the air interface are also encrypted using CCK. The system changes CCK daily.

68015000701-C - October 2013

5-33

System Overview

5.7.2.1.4 Security Class 3G (SC3G) A system operating as being Security Class 3G (SC3G), refers to a system operating with GCK and DCK/CCK encryption. In this mode encryption functionality is identical to the previous one with the addition that one or more talkgroups may use a dedicated Group Cipher Key (GCK).

5.8 Busy Call Handling The following describes how the system modifies the calling process to handle situations where resources are not available at the time a call request is made. A call request that cannot be granted the needed resources at the time the request is made is “busied” and the request is placed in the busy queue of the controlling Zone Controller. Calls are placed in the busy queue in the order in which they are received. However, each call type has a priority setting that influences the order in which calls in the busy queue are evaluated. Higher-priority calls are evaluated before lower-priority calls. Calls of equal priority are evaluated on the basis of the order in which they were placed in the queue.

5.8.1 Priority Levels Priority levels are used by the system to determine the assignment of system resources when multiple calls are competing for system resources. Emergency calls always have the highest level of priority. There are ten levels of priority: • Level 1 = The highest priority. Reserved for emergency calls. Level 1 cannot be assigned to any other call types. • Level 2-10 = May be assigned to talkgroup, individual, or telephone interconnect calls. Level 2 is the highest assignable priority, while level 10 is the default priority setting.

5.8.2 Group Call Busies Two calling features determine when group (talkgroup and multigroup) calls are busied: • AllStart™ • FastStart™ These calling features are assigned to the groups in the User Configuration Manager (UCM) application.

5.8.2.1 AllStart An AllStart setting for a group indicates that all the available resources for the call must be present for the call to start. An AllStart call requires the following resources before a call is granted: • A traffic channel at all sites that have affiliated group members. • All affiliated consoles and logging recorders to support console calls. • Encryption resources at the console interface if the call is secure. • A traffic channel at all critical sites. Critical sites for a talkgroup are designated in the TG/MG Site Access Profile record available in the UCM.

5-34

68015000701-C - October 2013

5.8.2.2 FastStart

If any of the above conditions are not met, the call is placed in the busy queue.

5.8.2.2 FastStart A FastStart™ setting for a group call indicates that only mandatory resources (that is, critical sites, critical resources and requested sites) are required to grant a call. Any other resources available at the time the call is set up are also included in the call. In FastStart™, not all affiliated members in a talkgroup must have a channel available in order for a call to start. FastStart™ requires the following resources before a call is granted: • A traffic channel at the site of the requestor. • All affiliated consoles and logging recorders to support console calls. • Encryption resources at the console/ICCS interface if the call is secure. • Encryption resources at the console interface if the call is secure. • A traffic channel at all critical sites.

When a group call is busied, the priority that is assigned to the call in the queue is determined by the higher of the individual priority of the talkgroup or the requestor. For example, if the talkgroup is priority 8 and the requestor is priority 5, then the call is queued with priority 5. If any of the above conditions are not met, the call is placed in the busy queue.

5.8.3 Private Call Busies Private calls are placed in the busy queue if the required resources for the call, including encryption, are not available at the time of the request.

When a private call is busied, the priority that is assigned to the call in the queue is determined by the better of the target or individual priority of the requestor. For example, if the target's priority is 8 and the priority of the requestor is 5, then the call is queued with priority 5. Private calls can have a priority level assigned that determines how the call request is serviced in the busy queue, the higher the priority, the sooner the call gets serviced.

5.8.4 Typical Reasons for Rejects When a radio requests a particular service, the Zone Controller can choose to grant the request, reject the request, or respond with a busy signal. When a service is granted, the Zone Controller assigns the appropriate resources and sends a message to the requestor granting the service. When the Zone Controller rejects a request, the Zone Controller sends a reject message to the requestor. When the Zone Controller is experiencing a busy situation, the Zone Controller sends a busy signal to the requestor.

68015000701-C - October 2013

5-35

System Overview

When a radio has been rejected from using a particular service, the Zone Controller sends an abort message to any resources that need to be released from the service, then sends a reject message to the radio. The following items are typical reasons why a radio may be rejected during registration or during a call request. • The radio may be sending an individual ID or talkgroup ID that is not loaded in the memory of the Zone Controller. • The radio may be requesting a service that is restricted or not available to the particular radio. • The system or the receiving radios may not support the call type requested by the initiating radio. • The system may be in a failure situation. Depending on the settings and the situation, the sites may be in local site trunking and only allow certain types of calls, or the Zone Controller may be using default access permissions. • The radio may be calling an individual or talkgroup that does not exist or that is not registered with the system. • The radio may not be configured to make the requested type of call. • For talkgroup calls, a console that should be attached to the call may not able to participate in the call. • The radio is not operating at one of its valid sites. • The zone is not able to communicate with the home zone of the initiating radio. • The zone is not in interzone trunking with the other zones that need to participate in the call. The particular resources may not be available for the call.

5.9 Effects of Loss of Service on Call Processing For purposes of this discussion, loss of service indicates that part of the infrastructure has failed, and that the failure affects the ability of calls to be made through some part of the system. The following describes the impact of loss of service on call processing. See 5.11 Zone Controller Switchover in Redundant Configuration, page 5-41 for a discussion of the impact of a Zone Controller switchover on call processing within a zone.

Generally, a service state for a site other than wide area trunking causes the radios at the affected site to attempt to register at a site that is in wide area trunking mode.

5.9.1 Loss of Service within a Zone Within a zone, two types of service states are available for sites that affect call processing: wide-area trunking and local site trunking. These states are listed in the table.

5-36

68015000701-C - October 2013

5.9.2 Conditions Necessary for Interzone Trunking

Table 5-3

Zone Call Service States

State

Definition

Wide-Area Trunking

Wide-area trunking is the normal state for a site within a zone. In this state, the site receives call processing instructions from the Zone Controller. A radio registered at the site can communicate with any other radio in the system. The basic criteria for wide area trunking includes an active RF site control path between Zone Controller and site, an enabled audio rendezvous point in the zone, a control channel and a traffic channel at a site.

Local Site Trunking

Local Site trunking mode is entered when the remote site loses communication with the Zone Controller. In this mode, the remote site takes over call processing responsibility. A radio registered at the site can communicate only with other radios registered at the same site.

5.9.2 Conditions Necessary for Interzone Trunking For each zone pair, the following conditions must be in place for interzone trunking to take place between the zones: • A functioning interzone control path between the Zone Controllers. • A functioning audio RP at each zone. • A valid talkgroup-to-home zone map in each zone. If any of these conditions are not met, the zone pair cannot enter interzone trunking with each other. The trunking state between zones determines how interzone calls are processed. Interzone call processing is divided into two types of services: • Group-based services • Individual-based services Group-based and individual-based services each have their own level of service availability, based on their interzone trunking state.

5.9.2.1 Interzone Group Service Availability The table describes three possible levels of service for group-based call requests in systems with three or more zones. Unified Event Manager provides an indication of the interzone trunking state between each pair of zones but there is no application that can indicate the level of service being provided. The information in the table can be applied to situations where the system appears normal but users do not have full access to their talkgroup. Table 5-4

Levels of Group Service Availability

Service Level

Description

Full Interzone

All zones are in a state of interzone trunking with respect to the home zone of the group.

Reduced Interzone

At least one participating zone is in interzone trunking with the home zone of the group, and at least one zone is not.

Zone Isolated

The current zone may only process the calls of the group locally within the zone. This occurs when either the participating zones have no interzone trunking with the home zone of the group, or when the home zone loses interzone trunking with all the other zones in the system. In such case the routers establish an alternate IP path.

68015000701-C - October 2013

5-37

System Overview

The three levels of group service availability are based on the perspective of a group member from the current zone to every other zone in the system, and whether the current zone is the assigned home zone of the group.

5.9.2.1.1 Example 1 It is possible for some members of a talkgroup to have zone isolated service for a short interval during loss of the links between the zones (generally microwave). • In the figure, the link between Zone 1 and Zone 3 is down (interruption of interzone trunking), while the links between Zones 1 and 2, and between Zones 2 and 3, are intact. • The home zone of the talkgroup A is Zone 1. • A user in Talkgroup A placing a call in Zone 1 or Zone 2 has full interzone service availability. • Talkgroup A members in Zone 3 have zone isolated group service availability for a short period of time while the master site routers reestablish the call through an alternate IP path, in this case, through Zone 2. Figure 5-12

Reduced Interzone Service Availability

5.9.2.2 Interzone Individual Service Availability Interzone individual services do not have the same service availability concepts as group calls. Interzone individual calls are always two-zone calls, with the controlling zone dynamically assigned as the zone responsible for initiating the audio.

5-38

68015000701-C - October 2013

5.9.2.2.1 Conditions for Interzone Unit to Unit Calls

5.9.2.2.1 Conditions for Interzone Unit to Unit Calls The following conditions must be in place for unit-to-unit calls to take place between the zones: • The two zones involved in the call must be in interzone trunking. • The zone of the call requestor must have, at minimum, an active Zone Controller to Zone Controller interzone control path between itself and the target radio's home zone so it can access the target radio's Individual HLR. • The target radio's zone must have, at minimum, an active Zone Controller to Zone Controller Interzone Control Path between itself and the requestor's home zone so it can access the requestor's individual HLR.

5.9.2.2.2 Example 1 • User 1 is in Zone 1, its individual home zone. • User 2 is in Zone 2, its individual home zone. • Zone 1 and Zone 2 are in interzone trunking. In this case, all criteria are met (see the figure below). Figure 5-13

Interzone Individual Call with Radios in Their Home Zones

5.9.2.2.3 Example 2 In a less commonly occurring example: • User 1 is in Zone 1 but its individual home zone is Zone 4. • User 2 is in Zone 2 but its individual home zone is in Zone 3. To make an interzone individual call between User 1 and User 2 (See the figure below), the following conditions must exist: • Zone 1 and Zone 2 must be in interzone trunking. • Zone 1 must have at least an Interzone Control Path to Zone 3. • Zone 2 must have at least an Interzone Control Path to Zone 4.

68015000701-C - October 2013

5-39

System Overview

Figure 5-14

Interzone Individual Call with Radios Not in Their Home Zones

5.10 Interference Detection Interference Detection gives the System Operator a warning of interference conditions affecting the uplink carrier frequency of any channel(s) within any system cell. Interference is defined as any RF signal, condition or characteristic that may adversely affect one or more radios within any cell of the system. This might include, for example, a malicious RF “jamming” signal; non-malicious interference caused by nearby equipment with poor EMC characteristics; or malfunction within a radio’s equipment that adversely affects other non-malfunctioning radios within the cell. Interference Detection offers a mechanism that automatically removes all channel resources affected by the interference from service, for the duration of the interference condition and transfer the service to other channels that are clear of interference. The procedure is the same for both Control, Voice and Data channels. The interference condition is clearly visible on the system fault management consoles, including the UEM console, as a “Yellow” state. The values that define the interference detection criteria shall be configurable for each cell of the system (BTS level), via BTS Service Software (TESS) for initial values and via the NM subsystem. The new parameters are manager owned. They comprise of three integer parameters: • Condition Alert Hysteresis. Proportional to the time taken to clear an interference condition, dependent also on the rate of packets received and the proportion of interference to non-interference packets. • Condition Alert Ratio. Proportional to the frequency of received interference packets that trigger an interference condition, dependent also on the ratio of interference to non-interference packets.

5-40

68015000701-C - October 2013

5.11 Zone Controller Switchover in Redundant Configuration

• Received Signal Level Threshold. The minimum received signal strength for corrupt packets to be classified as interference.

5.11 Zone Controller Switchover in Redundant Configuration The redundant Zone Controller in each zone provides protection against a hardware or software failure that may result in the loss of wide area trunking until the Zone Controller is repaired or recovers automatically. One controller actively processes calls and manages resources in the zone, while the other controller acts as a standby that can be brought online when the active controller is being serviced or has an internal failure that causes the loss of wide area trunking. The two controllers communicate with each other through the link connected directly between the two or, should that link fail, through the links connected to the core LAN switch . The direct link, also called the negotiating link, is used by the controllers to notify each other of their ability to maintain the zone in wide area trunking mode and to negotiate the switchover should that action be necessary. The core LAN switch establishes the connections between the controllers and the sites, and the MTIG. Although both controllers can receive network traffic, only one controller is actively in charge of the zone. Both controllers maintain links to the Network Management Subsystem in order to report individual controller status. The Redundant controller can be switched automatically or by user-initiated switchover. Automatic switchover takes place upon internal failure that causes the loss of wide area trunking or loss of dispatch operations. User-initiated switchover is done from the Zone Configuration Manager (ZCM) application in the Private Radio Network Management (PRNM) application Suite. In the event that access through ZCM is not possible due to failure, the Local User Terminal, through the Zone Controller Administration menu, may be used to perform the switchover.

Performing a user initiated switchover from the local user terminal could have adverse affects, like increased down time, on system operation and should only be used when access through the ZCM application is not possible. The following explains what causes an automatic switchover and how the system reacts when an automatic switchover occurs and when a user-initiated switchover occurs. • For information about performing the user-initiated switchover and Zone Controller redundancy and switchover, see Configuration Management, Call Processing Subsystem.

5.11.1 Automatic Switchover Automatic switchover occurs when a failure event within the controller causes a loss of wide area trunking for all sites or loss of dispatch operations. The failure event can be software- or hardware-based. The failures that trigger an automatic switchover are CPU failure, both power supplies failure, Ethernet connectivity failure and a manual disabling from a local Administrator menu.

68015000701-C - October 2013

5-41

System Overview

5.11.2 User-Initiated Switchover

Due to the severe system impact of a switchover event, user-initiated switchover should be initiated ONLY when absolutely necessary. User-initiated switchover is a feature that gives you the ability to disable the automatic switchover feature and perform a user-initiated controller switchover. The feature uses the Zone Configuration Manager (ZCM) application. If the Network Management link is down, and a user-initiated switchover still must be performed, switchover may be done through the Zone Controller Administration menu through the Local User Terminal. User initiated switchover is typically used when performing a software upgrade or performing maintenance such as replacing a faulty Field Replaceable Unit (FRU) that did not cause an automatic switchover.

Verify the health and status of the standby controller subsystem in Unified Event Manager before performing a user-initiated switchover or take any kind of action that results in a controller switchover.

5.11.3 System Behavior During Automatic Switchover When and where to use: When an automatic switchover to the redundant controller is commanded, the following sequence of events take place.

Process Steps

5-42

1

In case of failure of any crucial components causes the standby controller to compare its operational health against the health of the active controller. An automatic switchover is initiated if the standby controller is capable of wide area trunking.

2

If the standby controller is capable of wide area trunking, the standby controller informs the active controller, through the negotiation link, that it is going active and the active must go to standby.

3

All sites in the zone lose connectivity to the controller and subsequently enter local site trunking mode. If the controller has malfunctioned, the switch to local site trunking has probably already occurred.

4

All active wide area calls are ended including Talkgroup, Multigroup, Interconnect, Private, and Emergency. BTS sites revert to local site trunking mode.

5

All radios, upon receiving the local site trunking system status Outbound signaling Packet (OSP), leave their current site and search for a site in wide area trunking. Since all sites are in local site trunking mode, the radios return to the original site and inform the radio user of the local site trunking mode through audible tone and, when so equipped, with a visual indication. For more information see 5.11.3.1.1 Radio Scatter, page 5-43.

6

The sites constantly send link requests to the controller. Once the newly active controller is online, it acknowledges the link requests to bring the sites into wide area trunking.

68015000701-C - October 2013

5.11.3.1 Possible Call Processing Behavior During Recovery

As each site transitions to wide area trunking from local site trunking, they transmit a wide area System Status Outbound signaling Packet (OSP) to inform the radios of the change.

7

The time duration to transition from wide area trunking to local site trunking and return to wide area trunking varies depending on system size and configuration but should take less that two minutes. 8

If the radios ended up on a site other than their starting point during their search for a wide area trunking site, they transmit an Inbound signaling Packet (ISP).

9

The active controller begins gathering the current location of radios and talkgroup members from the affiliation tables sent from the sites.

Only limited wide area services are available until the controller receives all of the site affiliation tables. The time to recover the site affiliation information varies depending on the number of active radios, talkgroups, and the number of sites in the system, but should be less that twenty minutes. 10

For multizone systems, if the active controller is the controlling zone for an interzone call, it must also receive talkgroup affiliation information from the other zones before those zones are included in call requests. The time required varies depending on the number of radios and talkgroups in the system but in general should be less than 25 minutes. Prior to this being completed, interzone services to other zones may be affected.

11 The newly standby controller resets and if it initializes in service mode, the controller receives infrastructure, radio, and talkgroup information from the ZDS. This includes all infrastructure, radio user, and talkgroup configuration information.

5.11.3.1 Possible Call Processing Behavior During Recovery The table lists the types of call processing disruptions that may occur during the recovery of the primary controller. These disruptions could be caused by incomplete location and configuration data. Table 5-5

Call Processing Behavior During Recovery

Call Type

Possible Disruptions

Private Calls/Telephone Interconnect Calls

Calls to a target radios whose affiliation is not yet known to the controller are not successful.

Talkgroup/Announcement Calls

Talkgroup members need to have at least one affiliated member known by the controller at their site, to be included in talkgroup calls.

5.11.3.1.1 Radio Scatter All of the sites transition to local site trunking mode regardless of whether a controller switchover is automatic or user-initiated. The sites notify the radios of this change through a System Status Outbound signaling Packet (OSP). Upon receiving this OSP, the radios automatically start scanning the adjacent site list for another site that is still in wide area trunking mode unless the site that the radio is currently registered to is set to Always Preferred in the radio programming. When no wide area site is found, the radio stops scanning and returns the original site.

68015000701-C - October 2013

5-43

System Overview

Some radios can be registered at more than one site during controller switchover. Multiple registrations can occur if a radio happens to register to a new site while the radio is also searching the adjacent site list for a wide-area site. Because connectivity to the controller is temporarily lost during controller switchover, entries in some of the site registration tables do not get updated to reflect radios who have changed sites. Normally the controller de-registers radios when they roam out of a site, however, during a controller switchover the communications path from the controller to the site is temporarily unavailable preventing the controller from performing deregistration. The site transitions to wide area trunking mode when the site reestablishes a link with the controller. The site then notifies the radios of the change through System Status OSP. The wide area feature called Dynamic Site Assignment requires that the controller have up-to-date affiliation tables. All sites need to upload the affiliation tables to the controller. After the controller receives all of the uploads from the sites, it looks through the compiled affiliation table for radios that are registered on more than one site. If the controller finds duplicate affiliations it requests, through all sites where the radio shows registrations, that the radio reregister. This must happen before Dynamic Site Assignment can guarantee all intended parties are included in the call. The length of time it takes to update the affiliation tables depends on the number of sites, radios, and talkgroups in the system, but in general it should be less than twenty minutes from the time the first site transitions back to wide area trunking. As with radios, console affiliations must also be sent to the controller within the zone. This happens within the fist few minutes after the switchover occurs. For a given talkgroup to be monitored by the dispatch subsystem, at lease one console affiliation must be received for that talkgroup.

5.11.3.2 Switching Back to the Standby Controller (User Initiated)

Do not switch back to the standby controller until the Infrastructure database has been downloaded from the Zone Database Server (ZDS) or the system remains in local site trunking until the Infrastructure database has been downloaded. The download time varies by system configuration, but in general should take less than 10 minutes. If for some reason the newly active controller is not functioning properly, you may need to switch the standby controller back to active. This is considered a double switchover. The following is a description of what occurs when performing a double switchover before the standby controller has received the user configuration database from the ZDS.

5.11.3.2.1 Infrastructure Database Download The Zone Database Server contains infrastructure information such as the configuration information for the site and channel capabilities. The standby, reset controller does not have any knowledge of infrastructure objects until the database has been loaded into the controller memory.

5-44

68015000701-C - October 2013

5.11.3.2.1 Infrastructure Database Download

There is no indication that the download has completed other than the controller state changing to enabled idle or enabled active. The controller begins acknowledging the link requests from the sites once the database is downloaded. A link request contains information such as the site ID. The controller checks the site ID against the information in the database and requests the site's capabilities. The controller instructs the site to transition to wide area trunking if the capabilities are normal. The controller then requests the affiliation tables for radios and talkgroups. This operation is performed for every site in the system. The controller handles multiple sites simultaneously.

68015000701-C - October 2013

5-45

6

Dimetra IP System Features

6.1 Voice Services This following describes the voice services offered by the system. Unless stated otherwise, both radios and dispatch consoles can both initiate and receive these services.

6.1.1 Group Call The group call service allows a radio or dispatch console to establish a one-to-many communication with a group of users known as a talkgroup. The membership of a talkgroup is not a static membership configured within the infrastructure, but is determined by the radio users who have elected to be a member of that talkgroup at that time. Radios must affiliate with a talkgroup in order to be a member of a talkgroup. Once a talkgroup is assigned to a dispatch console, the dispatch console becomes a member of that talkgroup. A dispatch console may be a member of multiple talkgroups. The group call service is a semi-duplex service. Semi-duplex transmission means that only one user can transmit traffic in a call at any time. The system gives transmit permission to a single user. A group call is only terminated by the system.

6.1.2 Announcement Call An announcement call is a point to multi-point group call that provides the capability to communicate with multiple talkgroups simultaneously. The announcement call uses the TETRA group call service. An announcement call is made to a multigroup, which includes a number of talkgroups. Each talkgroup can be associated with one (and only one) multigroup.

6.1.3 Emergency Call The system supports an emergency call service. An emergency call can be either a group call or an announcement call. Emergency Call is a group call with the highest priority. When the system is busy, emergency calls are set up immediately by ruthlessly preempting the lowest priority call in progress. The lowest priority call is dropped and the required resources immediately granted to the emergency call.

6.1.4 Individual Call (Semi-Duplex or Full-Duplex) This service allows radios and dispatch consoles to initiate and receive semi-duplex or full-duplex TETRA Individual calls. This is a one-to-one communication with only the two parties involved in the call able to hear the communication. Hence it is known in Dimetra IP as a Private Call.

68015000701-C - October 2013

6-1

System Overview

Semi-duplex transmission means that only one user can transmit traffic in a call at any time. This is the characteristic mode for private calls in a PMR/PAMR system. Full-duplex transmission means that each user can transmit and receive traffic (talk and listen) at the same time. Telephone Interconnect calls are always full-duplex, so duplex individual calls appear to the user to be similar to telephone calls. The full duplex individual call service allows two parties in a TETRA system to communicate using full-duplex speech in three different ways: • Radio to console: (This call is initiated by an radio to a dispatch console) • Console to radio: (This call is initiated by a dispatch console to a radio) • Radio to radio: (This call is initiated by one radio to another radio)

6.1.5 Telephone Interconnect Call The telephone interconnect call service gives full duplex communication between a radio and a Private Automatic Branch eXchange (PABX) or Public Switched Telephone Network (PSTN) user. PSTN access is via a PABX. Full duplex means that both parties in the call can transmit and listen at the same time. The service allows a radio to initiate a telephone interconnect call by requesting an individual call to the telephone number and including the required external exchange number in the called request Similarly, PABX and PSTN users can initiate a telephone interconnect call to a radio by dialing an extension or radio number the radio.

6.2 Data Services This following describes the Data Services provided by the system. Unless stated otherwise both radios and dispatch consoles can both initiate and receive these services. The only supplementary services (see 6.3 Supplementary Services, page 6-4) applicable to all the Data Services are Air Interface Encryption and Talking Party Identification.

6.2.1 Status Transfer Service The Status Transfer Service allows a radio to send a precoded status message to the dispatch console system. The service uses the TETRA Short Data Service over the air interface. Only radios can send a status message and the service is only supported on the Main Control Channel (MCCH). The status message is delivered to all dispatch consoles that have the affiliated talkgroup of the radios assigned. The status message is only sent to dispatch consoles, not to radios that are members of the talkgroup. The Zone Controller generates an acknowledgment that is returned to the originating radio to indicate that the status message has been delivered to the dispatch console system.

6.2.2 Emergency Alarm The Emergency Alarm service allows a radio to send an emergency alarm to both the dispatch system and the Radio Control Manager (RCM) application. Only radios can send an Emergency Alarm and the Alarm is delivered to all dispatch consoles that have the affiliated talkgroup of the radio assigned. The status message is only sent to dispatch consoles, not to radios that are members of the talkgroup. The Zone Controller generates an acknowledgment that is returned to the originating radio to indicate that the Emergency Alarm has been received.

6-2

68015000701-C - October 2013

6.2.3 Short Data Transport Service

The system can also be configured so the RCM or Console acknowledges the Emergency Alarm.

6.2.3 Short Data Transport Service The Short Data Transport Service (SDTS) lets applications access the point-to-point or broadcast Short Data Service (SDS) transfer over the air. It supports messages of up to 140 characters per message. The SDS uses TETRA Short Subscriber Identity (SSI) addressing and data can be transferred between: • Radio to radio • Radio to fixed IP host (the IP host must have an assigned SSI and be registered with the Short Data Router) • Fixed IP host to radio group or broadcast (the destination devices must have assigned SSIs and be registered with the Short Data Router) • Fixed IP host to Fixed IP host SDS supports concurrent voice and data operation. Access to the SDTS is via the Peripheral Equipment Interface at the radios and via an IP connection to the Short Data Router (SDR) in the Dimetra infrastructure. In addition, there is an internal interface within Motorola radios to the SDTS, used for the Alphanumeric Text Service (ATS).

6.2.4 Alphanumeric Text Service The Alphanumeric Text Service (ATS) enables free text messages to be sent between radios, dispatch consoles and computers in the fixed network. It is analogous to the Short Message Service (SMS) familiar to GSM users. Often, the ATS application is run on a computer that also runs the Elite Dispatch application (a dispatch console), but it can be run on a stand-alone computer that may be external to the Dimetra IP system. The ATS application has the following features: • A message list which allows free text of up to 500 characters in Unicode or 1000 characters in ASCII to be entered and stored. • An address book which allows the radio name, department and Individual Short Subscriber Identity (ISSI) of the radio to be entered and stored. • Messages are sent by selecting one or more entries from the address book and either entering the text message to be sent or selecting a message from the message list. • Sent messages are displayed in the sent list which indicates the time and date the message was sent, whom the message was sent to and the status of the message. • The user can request notification that a message has been read. • Message broadcast to a stored address list, or to a stored list of sites. • When a message is received this is announced via audible and visual indication. The user is given the option to read the message immediately, or read the message later. • The radio application shall store up to 8 messages. If a new message arrives while the radio queue is full, the radio rejects the incoming message and the sender receives indication that delivery failed.

68015000701-C - October 2013

6-3

System Overview

6.2.5 Packet Data Service The Packet Data Service (PDS) is a bearer service that allows IP hosts to communicate using the Internet Protocol (IP). It is used to transport various types of data files in the system. Access to the PDS is via the Peripheral Equipment Interface at the radios and via an IP connection to the GGSN in the infrastructure.

6.2.6 Data Resilience Data resilience is the feature that takes the first steps to eliminate all ’Single Point of Failure’ points for data features: short data and packet data. The feature includes: • Warm standby SDR and PDG • Warm standby GGSN • Resilient Mobility Push • Remote failure recovery

6.3 Supplementary Services The following provides details for different supplementary services that are supported by the Dimetra IP system.

Supplementary Services are optional and subject to license fees.

6.3.1 Busy Queuing and Call Back Busy Queuing and Call Back is a Dimetra IP service that always supplements the Group Call, Individual Call and Telephone Interconnect services (voice services). The system supports queuing of voice calls whenever a traffic channel is required and no traffic channels are available. If there is no traffic channel available at one or more of the sites required for the call, the call is placed in a queue. When the required traffic channels for the call become available, the calling party is automatically called back to indicate that the call has now been set up and has initial transmit permission.

6.3.2 Queuing Priority Queuing Priority is a Dimetra IP service that always supplements the Group Call, Individual Call and Telephone Interconnect services.

6-4

68015000701-C - October 2013

6.3.3 Call Out

The system provides 10 levels of priority where level 1 is the highest and reserved for emergency group calls. The NM assigns levels 2-10 to individuals and talkgroups. The priority assigned to a group call is the individual priority of the calling party or the group priority, whichever is the higher. The priority level is used in the case where a system is busy and calls are queued. When the systems get busy, calls with higher priority are allocated traffic channels before calls with lower priority.

6.3.3 Call Out A Call Out alert is sent in the form of an individually addressed SDS text message to a radio or individually addressed SDS text messages to multiple radios. The SDS text message can be configured to contain a Talkgroup change for all target radios so that the users responding to the call out can communicate with each other. Example usage: In the event of a major fire, the dispatcher can alert police and fire officers in the field of the incident by an audio alarm or a text message with the aim to ask them to go to the scene of the incident. The users can then respond back to the dispatcher 'Coming' or 'Not coming'. The dispatcher knows which officers are present at the scene of the incident.

6.3.4 Recent User Priority Recent User Priority is a Dimetra IP service that always supplements the group call service. If, during a group call, a user is slow to make a response and the traffic channel is de-allocated, the call enters a recent user queue. If a user then responds within 10 seconds the call is given priority for a traffic channel over new calls (of the same priority) also waiting for a traffic channel allocation. Recent User Priority lets a talkgroup call have more conversational continuity when there is a busy queue.

6.3.5 Dynamic Site Assignment Dynamic Site Assignment is a Dimetra IP service that always supplements the group call service. Dynamic site assignment means that traffic channels are only assigned at sites where there are currently one or more members of the talkgroup registered. To accomplish this the system maintains a database that identifies, for each talkgroup, which sites should be included in a call at any given time

6.3.6 All Start/Fast Start All Start/Fast Start is a Dimetra IP service that supplements the group call service. For each talkgroup, the Network Manager (NM) can set the talkgroup to operate in either All Start or Fast Start modes. In All Start mode, if the system is busy and not all resources are available to set up a group call, the system waits for all required resources to become available before setting up a call. This ensures that all the sites having members of the talkgroup are included when the call begins. In Fast Start mode, the call is set up with whatever sites are available, while additional sites are added to the call as and when resources become available. This ensures that calls are set up as quickly as possible even when the system is busy.

68015000701-C - October 2013

6-5

System Overview

6.3.7 Critical Site Assignment Critical Site Assignment is a Dimetra IP service that supplements the group call service. For each talkgroup, the Network Manager (NM) can create a list of Critical Sites. These are sites that must be included in a group call for it to be set up. Thus, even when Fast Start is in operation, the call is not set up until channels are available at all the critical sites for the talkgroup. Furthermore, a group-call is always set up at a critical site, whether or not any members of the talkgroup are registered at the site.

6.3.8 Talking Party Identification Talking Party Identification is a Dimetra IP service that supplements group call, individual call and data services. Whenever a radio or dispatch console is transmitting, the ID of this talking party is always forwarded to the other (receiving) radios and dispatch consoles. If the talking party changes through normal conversation or through interruption, then the ID of the new talking party is again forwarded to the other radios or dispatch consoles in the call.

6.3.9 Calling Line Identification Presentation Calling Line Identification Presentation (CLIP) is a Dimetra IP service that always supplements the Telephone Interconnect Call service. It provides a (called) radio with the identity of a calling PABX or PSTN user if the calling party identity is present in the call set up from the external exchange.

6.3.10 Dual Tone Multi-Frequency Overdial Dual Tone Multi-Frequency (DTMF) Overdial is a Dimetra IP service that supplements the Telephone Interconnect Call service. This service allows a radio user send digital information as DTMF tones during the conversation phase of a call. This can be used for accessing services via the PABX or PSTN. All defined DTMF tones (0-9,A,B,C.D,*,#) are supported by the system.

6.3.11 Late Entry Late Entry is a Dimetra IP service that always supplements the group call and announcement call service. While a call is in progress on a traffic channel, late entry signaling is sent on the main control channel. This lets radios that failed to decode the initial call set up signaling (for whatever reason) to join a call in progress. The interval between late entry messages depends on system loading. Late entry signaling is identical to the initial call set up signaling and therefore an radio cannot distinguish between the two.

6.3.12 Priority Monitor Priority Monitor is a Dimetra IP service that supplements the group call service. The Network Manager (NM) can mark selected talkgroups or multigroups as priority groups. At sites where calls for these groups are being set up, the call set up messages are sent on all the traffic channels at the site where group calls are ongoing (in addition to the Main Control Channel (MCCH)). This gives those radios that can monitor more than one talkgroup the opportunity to exit the current call and jump to the priority group.

6-6

68015000701-C - October 2013

6.3.13 Preemptive Priority Call

In addition, any emergency call signaling is also sent on all the traffic channels at the sites where the emergency call is being set up.

6.3.13 Preemptive Priority Call This feature allows group calls and individual calls for Preemptive Priority Call (PPC) enabled radios, talkgroups and multigroups to be granted traffic resources by ruthless preemption should there be no free traffic channel at the requesting or destination sites when the call is set up. The network manager controls PPC, and the user cannot raise the priority of a call to PPC through the radio user interface. When traffic resources are available, PPC calls are set up as normal calls, however, if traffic channels are not available the Zone Controller preempts the necessary resources from normal calls of lower priority level. The ZC uses the preempted resources to continue the set-up procedure of the PPC call.

6.3.14 Preemptive Priority Call - Busy User Preemption Any individual radio or dispatcher can be enabled in the infrastructure for the Preemptive Priority call (PPC) supplementary service. Should a PPC enabled user initiate an individual call to a radio that is engaged in another, lower priority individual or telephone interconnect call, or involved in packet data transfer, then the new PPC call takes precedence and interrupt the existing call.

6.3.15 Site Wide Call The Site Wide Call (SWC) service is an enhancement to the standard group-call service and allows a console to communicate with all radios located at one or more sites. Generally, Site Wide calls also employ Preemptive Priority call (PPC), and in practice are often raised as emergency calls.

6.3.16 Barring of Incoming/Outgoing Calls Barring of Incoming Calls/Barring of Outgoing Calls (BIC/BOC) is a feature, which allows to control the communication of radio users to talkgroups. It allows to configure the permissions of radio users to initiate calls and to receive calls from certain talkgroups. The controlling mechanism covers private and talkgroup calls and applies to all radio and console users. This feature appears in two contexts: • BIC/BOC is often used with other features, like Object Call. This involves the creation of a Barring Profile in the User Configuration Manager. • BIC/BOC is also used as a Dimetra IP supplementary service of the Telephone Interconnect Call service. Each radio user can be barred by the Network Manager from making incoming outgoing telephone interconnect calls with certain specified numbers or number ranges. The numbers and ranges are specified in Exclusion Classes in the User Configuration Manager. For more information see Barring of Incoming/Outgoing Calls and Telephone Interconnect manuals.

68015000701-C - October 2013

6-7

System Overview

6.3.17 Telephony – BIC/BOC Barring of Telephone Interconnect Calls is a Dimetra IP supplementary service of the Telephone Interconnect Call service. Each radio user can be barred by the Network Manager from receiving incoming or initiating outgoing telephone interconnect calls with certain specified numbers or number ranges. The numbers and ranges are specified in Exclusion Classes. For more information, see Telephone Interconnect Subsystem manual.

6.3.18 Requested Sites Requested Sites is a Dimetra IP supplementary service that supplements the Group Call Service: The Network Manager can specify a list of requested sites for each talkgroup. When a group call is set up, the call is set up at each requested site even if there are no members of the talkgroup registered at these sites. In this way, requested sites are always in group calls for a talkgroup. This can be used to ensure that scanning radios (which are not affiliated) are able to receive talkgroup calls even if there are no affiliated talkgroup members at a site.

6.3.19 Control Channel Immunity The Control Channel Immunity feature maintains high availability of site resources during periods of interference and provides security for broadcast control channel information. Control Channel Immunity includes a number of different functions to protect the system and maintain operations, including the following: • Detect interference on uplink or downlink control channel carrier frequency • Report interference activities to Unified Event Manager • Scramble broadcast information pertaining to the main control channel carrier • Revert to another available control channel at the site during periods of interference When interference is detected on an uplink control channel carrier, a trap is sent to Unified Event Manager. If the interference signal exceeds the configured threshold, the Site Controller reverts to an alternate channel at the site which has control channel capability. The primary control channel is removed from service for the duration of the interference. The alternate channel then provides downlink control signaling and accepts uplink signaling from the radios. The Site Controller may terminate other services on a particular channel when the channel is required for control channel purposes. When a radio detects a failure or interference condition on the control channel downlink, the radio attempts to revert to one of the alternate control channels at the site. The site can be configured to just detect interference and send a trap to Unified Event Manager, or the site can be configured to automatically remove the carrier from service and revert to another available carrier (as described above). This operation is similar to the control channel fall back operation which is used during a control channel failure.

6.3.20 Energy Economy Mode The Energy Economy Mode is a feature on a Dimetra IP system and requires a separate NM licence. This feature enables the use of the Energy Economy Mode on a particular MTS/EBTS station (by radios that support this feature). When available for radios, this mode allows for battery saving operation.

6-8

68015000701-C - October 2013

6.3.21 SDR Audit Logging

6.3.21 SDR Audit Logging Audit logging is a Dimetra IP feature where configuration changes are logged so they can be examined at a later time. In Network Management the following actions are logged: • UCS configuration changes made via the UCM • UCS configuration changes made via the UCS API • ZDS configuration changes made via the ZCM • Diagnostic commands performed via the ZCM For the SDR the following changes are logged • Zone to SDR ID map • Broadcast region • Host The log contains the time of the activity, the identity of who performed the activity, and which activity was performed. The format of the log file is XML.

6.4 Call Logging features The following explains the call logging features available in the Dimetra IP system.

6.4.1 Central Voice Logging Motorola’s logging system allows an agency to record audio transmissions as well as certain radio events from selected talkgroups/channels and individuals in a radio system. These recordings are archived for future playback and use by authorized users/administrators. Motorola’s voice logging solution consists of three components listed below: • MCC 7500 Archiving Interface Server • Third party logging recorder • Third party replay station

For further information on the voice logging system, turn to the MCC 7500 Dispatch Consoles Subsystem manual.

6.5 Redundancy of Critical Components The Dimetra system offers redundant capacity for all components that are critical to transporting voice through the infrastructure. This means that any one component in the system can fail, and the radios are still able to communicate via voice.

68015000701-C - October 2013

6-9

System Overview

Redundant components can be added to other parts of the infrastructure — for instance to ensure traffic of short data massages. Furthermore, the system offers the possibility of geographical redundancy. With geographical redundancy the functioning and its redundant counterpart are placed in two different locations. This can be done to avoid physical damage to the system that impacts both the functioning and the redundant component. Figure 6-1

Zone with Geographical Redundancy Geographical Location 1

Geographical Location 2

To PABX/PSTN EC

MTIG-IP

EC

MTIG1

Primary Zone Server

00000

0

0000

Border Rouer

Patch Panel

0000

Patch Panel

0000

KMF

VPN Router 00000

00000

0

Core Gateway/ Exit Router(s)

0

VPN Router

0000

Border Rouer

Core LAN Switch 3 & 4

0000

00000

0

0000

Core LAN Switch 1 & 2 Core Gateway/ Exit Router(s)

00000

0 00000

GGSN

EAuC

0

0000

Secondary Zone Server

Fiber

0000

PDR

00000

00000

0

0000

NTS

SDR2

0000

MTIG1

SDR1

MTIG-IP

0

RNG

To PABX/PSTN

CEN

00000

00000

0

0

CEN

Bas e Stations Control Rooms Other Zones 0

Bas e Stations Control Rooms Other Zones

Transport Element

Primary Management Server

Application Element

Primary Data Server

Mutualy Exclusive

6.6 Local Gateway Trunking

00

0

Optional Application Element

Local Gateway Trunking is a disaster recovery feature designed to provide local resource functionality in the event of an MSO failure or a link failure between the base station and the MSO. In the event of an MSO or link failure the local MTS and console are able to connect to a local Dimetra IP Micro/LiTE system and provide full voice and short data functionality within the local coverage area of the Dimetra IP system.

6-10

68015000701-C - October 2013

6.7 Mobility Features

6.7 Mobility Features The following explains the mobility features in the Dimetra IP system.

6.7.1 Extended Range Range Extension for Air to Ground Stations is an enhancement of a base station so the existing 58 km cell limit is extended to 83 km.

6.7.2 Subscriber Class The Subscriber Class functionality is used to allow radios belonging to certain classes to use certain cells and likewise used to restrict radios belonging to certain classes from using certain cells. The Subscriber Class is a service criteria in cell selection, allowing/restricting radios for being used on certain cells. Subscriber Class is one of the features supporting Mobility. The other mobility features are Valid Sites and Cell Reselection Parameters.

6.7.3 Valid Sites Valid Sites is a Motorola Solutions service that supplements the individual and group call service. For each radio and talkgroup, the Network Manager (NM) can define a list of valid sites for the talkgroup. Users cannot use the site unless the site is listed as valid for that radio or talkgroup. If a radio roams to an invalid site , it is allowed to register, but cannot initiate or receive any calls. This is only signaled to the user when attempting to initiate a call. The valid sites for a radio or talkgroup can range from a single site to every site in the system. This feature lets the NM control the geographic extent of the radio or talkgroup. In addition, the NM can, for each site and each radio or talkgroup, enable or disable emergency calls at non-valid sites. This lets users make emergency calls to a talkgroup even if they are located at a non-valid site for the radio or talkgroup.

6.7.4 Common Secondary Control Channel Common Secondary Control Channel is a TETRA standard feature extending the signalling capacity of the Main Control Channel by using one or more additional channels for the messages otherwise only sent on the MCCH. Adding a C-SCCH, removes a channel from the normal voice and data service, so if a C-SCCH is added without knowing the load situation on the site it may actually reduce the overall service provided to the end user. Accordingly, an integral part of the C-SCCH feature, is a set of features that will help the network operator determine the right moment to increase or decrease the number of Common SCCHs. C-SCCH is only supported on the MTS.

6.8 Console Operator Features The following explains the console operator features available in the Dimetra IP system.

68015000701-C - October 2013

6-11

System Overview

6.8.1 Assignable Talkgroups In order for a dispatch console to communicate with a talkgroup, the talkgroup must first be defined as a resource within the console system. This is done using the User Configuration Manager (UCM). Once a talkgroup resource is define using UCM it can be assigned to individual dispatch consoles. Talkgroups can be assigned to dispatch consoles permanently (so that they are always available to the dispatch console) using Elite Admin or they can be assigned temporarily by the dispatch console, in which case they are only assigned until the Elite Dispatch application is next closed. Talkgroups are represented on the dispatch console as talkgroup windows. Talkgroup windows can be displayed in expanded or compressed format and can be grouped in folders.

6.8.2 Assignable Speakers and Audio Summing The dispatch consoles are equipped with two speakers, Speaker I and Speaker II. These are assignable to monitor any specific resource but are normally assigned as: • Speaker I monitors the audio of the currently selected talkgroup • Speaker II monitors the audio from all the (remaining) unselected talkgroups This lets the dispatch console user monitor the voice activity on all the assigned talkgroups. The volume of Speaker I and Speaker II can be set independently.

6.8.3 Repeat Disable The Repeat Disable feature allows a dispatch console to disable the talkgroup inbound audio from being repeated to the rest of the talkgroup. The feature allows Dimetra IP to emulate conventional Base Station operation. Once enabled, Repeat Disable is then effective for all group calls in that talkgroup until canceled.

6.8.4 Temporary Disable Dimetra IP allows a network management operator to temporarily disable or re-enable a radio over the air. The radio is unable to make or receive calls while it is disabled, even if the radio is turned off and turned back on. If the radio is turned on, it is still registered in the system and is able to roam.

6.8.5 Permanent Disable As well as Temporary Disable, Permanent Disable is also intended to protect a network from attack from a compromised or faulty radio. It shall be used when the radio is known to have been compromised, or has been suspected of compromise for a long time. Permanent disable of radio subscription, signaled by ITSI, allows disabling of subscription either of an integrated radio, or of SIM where a SIM is used. Unlike the temporary disable feature, mutual authentication is a precondition for permanent disable. Permanent Disable is a one way function, there is no equivalent enable function. The radio requires recovery and reprogramming before it can be used again.

6-12

68015000701-C - October 2013

6.8.6 Trunking System Status

6.8.6 Trunking System Status This feature provides a mechanism for dispatch consoles to determine the current zone status. The feature is similar to the Zone Status feature on the Radio Control Manager.

6.8.7 Console Priority Once a group call is in progress, dispatch consoles have the highest priority when the system sets the source of audio for the call. This lets a dispatch console interrupt a currently transmitting radio in a group call. There are different levels of priority within the dispatch console system. The table below shows the priority for the audio source in a group call. Table 6-1

Console Priority Levels

Priority Level

Audio Source

1

Primary Supervisory Console Instant Transmit

2

Secondary Supervisory Console Instant Transmit

3

Operator Console Instant Transmit

4

Any Console General Transmit

5

Radio Transmit

6.8.8 Status Message Display A status message that is sent from a radio appears in the stack of a talkgroup resource window of the Elite Dispatch application. The stack displays up to 24 entries. The talkgroup window in which the status message is displayed is the talkgroup to which the radio is currently affiliated.

6.8.9 All Mute The All Mute feature lets a dispatch console operator quickly mute all audio except the currently selected resource for a predetermined length of time. The time can range from 0 to 255 seconds.

6.8.10 Instant Transmit The Instant Transmit feature lets a dispatch console transmit to an unselected talkgroup with a single action without having to select the talkgroup first. It also gives the transmission a higher priority than using general transmit. Note that using instant transmit on an unselected talkgroup resource does not select that resource so any received audio is routed to the unselected speaker.

68015000701-C - October 2013

6-13

System Overview

6.8.11 Safety Switch The Safety Switch protects the dispatch console instant-transmit button from accidental use. The dispatch console system manager can protect the instant transmit button for each resource as required. To use a protected instant transmit button, the dispatch console operator must first select the safety switch, then press the instant transmit button within five seconds.

6.8.12 Intelligent Call Indicator The Intelligent Call Indicator feature lets a dispatch console operator know whether any other dispatch console in the zone has a talkgroup selected. When a group call is in progress for an unselected talkgroup, the (incoming) call indicator in the talkgroup window flashes if no other dispatch console has that talkgroup selected. If another dispatch console selects the talkgroup, the call indicator stops flashing. The call indicator always flashes on the selected talkgroup.

6.8.13 Supervisory Console User Multiple users in the zone may be configured with Supervisory Console User. This means that the console user has higher transmit priority. Optionally, one or more dispatch consoles in the zone can be designated secondary supervisory dispatch consoles. These dispatch consoles have audio priority over other dispatch console transmissions in a group when using the instant transmit feature.

6.8.14 Console Multi-Select This feature enables a dispatch console to transmit simultaneously to more than one talkgroup. A dispatch console that has been assigned a Multi-select resource can assign talkgroups to a Multi-Select resource. When the dispatch console initiates a call to the talkgroups in the Multi-Select resource, a call is established to each talkgroup and the console audio is routed to each talkgroup. When the dispatch console releases the PTT, the call to each talkgroup is terminated. (This is in contrast to Console Patch, where the talkgroups remain patched until the dispatch console explicitly terminates the patch).

6.8.15 All Points Bulletin Transmission An All-Points Bulletin is a method of transmitting to a multi-select group quickly and without first making the multi-select the selected resource. It can be viewed as an instant transmit, but for a multi-select group instead of a single resource.

6.8.16 Console Patch The Console Patch feature enables a dispatch console to patch together two or more talkgroups. A dispatch console that has been assigned a Patch resource can assign talkgroups to a Patch resource. The patch remains in effect until the dispatch console explicitly terminates it. Each time a user (radio or dispatch console) transmits to the patched talkgroups, a call is established to each talkgroup and the audio is routed to all the patched talkgroups.

6-14

68015000701-C - October 2013

6.8.17 Conventional Channel Patch

A Private call may be added to a Console Patch by first setting up the Private call, and then adding it to the patch configuration.

6.8.17 Conventional Channel Patch The Conventional Channel Patch feature lets a console user patch talkgroups to conventional channels that are connected to the system. Voice detection is used on patched conventional channels to initiate group calls.

6.8.18 Console Acoustic Cross-Mute This feature allows the acoustic muting of outbound transmissions from other dispatch consoles in the zone. This is typically used when dispatch consoles are located near to each other in the same dispatch centre to eliminate the possibility of acoustic feedback between the dispatch consoles. Cross-muting is configured via the User Configuration Manager.

6.8.19 Ambience Listening This feature allows a radio to be remotely set to transmit, without giving any external indication that a call is being set up or is in progress. Ambience Listening is implemented as a simplex individual call, so the radio does not receive any audio during the call and if the monitored radio is turned off during the ambience listening call, it continues to transmit, although it appears to have been turned off to the user. Ambience listening is always initiated by the infrastructure, either from a dispatch console or via a third party application interfacing through the console feature API.

6.9 Console Management Features Two applications are provided to manage the dispatch console system: • User Configuration Manager (UCM) • The Elite Admin application The UCM defines the attributes of the dispatch console system, whereas Elite Admin defines how information is presented on each dispatch console display.

6.9.1 Elite Admin Application The Elite Admin application defines how information is presented on each dispatch console. It provides for the configuration of the following items: • The default resource (talkgroup) windows and folders • The features available within each window • The items appearing in the menus • The buttons in the toolbar You can use Windows file permissions to control who can modify the files.

68015000701-C - October 2013

6-15

System Overview

If enabled, dispatch console operators can make limited changes to the configuration of their dispatch console (such as adding resources). These changes are temporary and are lost when the user logs out. Permanent changes to configurations can only be made using Elite Admin.

6.10 Dimetra Enhanced Software Update Dimetra Enhanced Software Update is a feature allowing for a centralized upgrade, backup and restore of the server applications.

6.10.1 Upgrade Server The Upgrade Server (UIS) is part of the enhanced upgrade framework, hosted on the MultiOS zone server. Primary UIS application is installed as a container on the Primary Zone Server, while secondary UIS application is installed as a separate container on the Secondary Zone server. Each zone will deploy its own UIS. UIS is responsible for upgrade application servers within the same zone where it is located. UIS to UIS interface will use file transfer and remote command execution protocols to synchronize data between all UIS servers deployed in the system.

6.10.2 Upgrade Console Upgrade Console is a web application used for controlling, executing and monitoring the upgrade process accessed from the NM Client PC. It is used for creating data backups, restoring data and upgrading software. Furthermore, the application is used for performing administrative tasks on the Dimetra Enhanced Software Update tool.

6.11 Version Coexistence Dimetra IP 8.1 system supports version coexistence with existing Dimetra IP 7.1 systems. This allows new Dimetra IP 8.1 clusters to be connected to existing Dimetra IP 7.1 clusters. The following limitations apply: • The features and capacity of a mixed system with coexisting 8.1 and 7.1 clusters are limited to the features and capacity of the 7.1 system. • Coexistence feature is dependent on hardware used in 7.1 clusters. For example, coexistence is possible for systems using Netra 240 or G7 as a server platform, while systems using CP1500 are not supported. • Within each cluster the mix of hardware is restricted to the hardware that is ship accepted on that release. For example, 7.1 cluster may include a Centracom console, but 8.1 cluster cannot. • The interconnected clusters may contain both DIPS and DIPC provided that DSS zones are in the same type (all E1 or all Ethernet).

Ethernet DSS can connect to E1 DIPS only after adding Ethernet Exit Routers to the DIPS zone. An E1 DSS cannot connect to an Ethernet DIPS because the Ethernet DIPS cannot support E1 Exit Routers and the E1 DSS cannot support Ethernet Exit Routers.

6-16

68015000701-C - October 2013

6.11 Version Coexistence

The features specific to Dimetra IP 8.1, like Object Call or BIC/BOC, are not available in such hybrid systems.

68015000701-C - October 2013

6-17

7

Dimetra IP Network Management The following provides an introduction to Network Management (NM) and the FCAPS model.

7.1 System Management Objectives and Framework As a telecommunications network, the Dimetra IP system needs to be managed as any other telecommunications network is managed. The Network Management (NM) subsystem can be viewed as a set of software applications or tools used to manage the system and its components. These tools are intended to maximize the available resources and minimize system downtime. Five key functional areas or services are associated with a network management framework: • Fault Management • Configuration Management • Accounting Management • Performance Management • Security Management The International Organization for Standardization (ISO) refers to this as the FCAPS model. The NM subsystem offers effective and efficient solutions that address each of the FCAPS requirements. The NM subsystem supports the following services: • Fault Management - Applications are included for monitoring the status of the transport network and the individual infrastructure components, displaying fault information, forwarding alert information, and performing diagnostic procedures. • Configuration Management - Facilities are provided for entering and maintaining the operational parameters of the infrastructure components and user devices (such as radios). • Accounting Management - NM supports the tracking of radio usage of the system by providing an interface to third-party accounting and/or billing applications. • Performance Management - Applications are available for monitoring, reporting, controlling, and optimizing the use of system resources. • Security Management - NM includes features for setting user privileges and controlling their access to view and/or modify information contained in the configuration databases. Systems continue to grow in size and technical complexity. Work demands are increasing on system administrators who are routinely faced with handling multiple tasks. Remote access leverages system administrators' time. At the same time, the mobile work force increasingly relies on radio communication services to fulfill their critical missions. Even a brief service interruption or degraded quality of service could impact organizational effectiveness, productivity, or safety. Rapid fault detection, notification, and repair require sophisticated tools that are technologically equal to the managed network. Features and benefits are detailed in the following.

68015000701-C - October 2013

7-1

System Overview

7.2 Serviceability Serviceability for a Dimetra system, at the MSO, is the capability to provide maintenance of the equipment either locally from a service terminal or remotely through modems or remote LAN connections. To facilitate service to the remote sites Dimetra™ BTS (Base Transceiver Station) Service Software (TESS) is available as a remote terminal (only from within the RNI) so many maintenance functions regarding the BTS sites can be done remotely via VPN Gateway. This clause describes the architecture by which the service organizations and other support functions can get access to elements in a Dimetra system. The maintenance procedures and functions such as fault and performance management are described in more detail in 7.6.2 Private Radio Network Management Suite Applications, page 7-16.

7.2.1 Remote Serviceability of the MSO Remote serviceability allows a technician to perform maintenance tasks from a remote service computer. For a remote service computer, the following access methods are available: • Certified solution: connect to the terminal server via a modem connection, either dial-up or direct connected on leased lines. • Project specific solution: connect to a border router and thus the IP network either via WAN links or via a modem. The modem can again be directly connected via leased line or a dial-up modem. The remote access computer is able to monitor the system and gain access to infrastructure products. When connecting, the remote access computer can gain access to the MSO by: • Console and/or ILOM interface to the MSO devices connected to the terminal server via the terminal server’s menu system • PPP IP connectivity to the MSO devices via the terminal server’s LAN connectivity The remote serviceability access means that a technician is allowed access to elements of the infrastructure for the following: • Configuration • Diagnostics • Event Log Reporting

7.3 Network Management System The Dimetra IP system features the Motorola Network Management (NM) System based on the client/server networking model. In the equipment room, the application and database servers run unattended on industrial-class computers based on the HP ProLiant DL360 Gen8 server platform. The server applications run on the Red Hat Enterprise Linux operating system.

7-2

68015000701-C - October 2013

7.3.1 Client/Server Networking

7.3.1 Client/Server Networking Application processing, data collection and storage are distributed across multiple computer servers and client PCs connected to a Local Area Network (LAN). The client PCs are commercial personal computers running the Microsoft® Windows operating system for networked computers. Authorized system managers or network administrator personnel use the client PCs to start and run the software applications for configuring, viewing equipment operational status, and monitoring network utilization and performance. The servers are industrial grade, high performance computers geared to handle the intense, typically real-time, data processing tasks associated with managing a single zone or handling specific cluster-level tasks, in multizone systems.

7.3.1.1 Windows-Based Clients The NM architecture distributes most of the user application processing to the client PCs. This approach yields important benefits: • Application performance is less dependent on the number of concurrent users and open applications; • Personnel typically responsible for managing a radio system or computer network are already familiar with, or easily trained to use, the GUI of PRNM applications that conform to Windows operating system conventions; and, • Remote operation performance over a limited bandwidth link (for example, a telephone line used for accessing the network remotely through dialup modems) is improved.

7.3.1.2 NM Client Applications The following NM applications run on or may be accessed from the NM client workstations:

7.3.1.2.1 Cluster-Level Applications • User Configuration Manager (UCM) - A management application used to enter and maintain configuration information for the User Configuration Server (UCS). The User Configuration Manager (UCM) configures System, radios, Security, and ZoneWatch Configuration objects. • System Profile - Displays how cluster-level applications are being used by the network management clients. It displays the users that are currently accessing cluster-level applications, the number of purchased licenses for these applications, and displays the number of licenses that are currently being used. System Profile displays information for the following applications: – User Configuration Manager (UCM) – System Profile – Software Download

7.3.1.2.2 Zone-Level Applications • Zone Profile - The Zone Profile application displays detailed information about the applications that are operating in the zone. In the Zone Profile application, the Application Usage tab displays how zone-level applications are being used by the network management clients. • Zone Configuration Manager (ZCM) - A management application used to enter and maintain configuration information for the Zone Database Server (ZDS). The ZCM configures the infrastructure equipment for the system. The ZCM is part of the Motorola Private Radio Network Management Suite.

68015000701-C - October 2013

7-3

System Overview

• ZoneWatch - (1) A Windows application that monitors trunking activity and radio call traffic for an individual zone in real time. This application is part of the Private Network Management Suite. (2) A Motorola software application that allows users to monitor activity within a zone • Affiliation Display - Affiliation Display is a Private Radio Network Management (PRNM) Suite management application that monitors how radio users travel between different sites in a zone and how they communicate with other members of their assigned talkgroup or even with members outside of their talkgroup within a particular zone. • Air Traffic Information Access (ATIA) Log Viewer - Data packets that contain talkgroup registration and site registration and deaffiliation/deregistration information for each radio user in a particular zone. The Air Traffic Router (ATR) collects this radio traffic information from the Zone Controller and broadcasts an information stream of these packets on the network. • Dynamic Reports - An application intended for short term monitoring. The display provides zone-level, real-time charts that illustrate channel utilization for all call types – group, private, interconnect, control channels, and dynamically blocked calls. • Historical Reports - A management application producing reports on radio infrastructure and radio resource usage within an identified zone. • Fault Manager using Unified Event Manager® - The Dimetra IP fault management application. Unified Event Manager identifies problems rapidly and provides functions and tools for notifying support personnel, tracking, diagnosing, and correcting faults. It also maintains a data warehouse, storing up to 30 days of event history. • Radio Control Manager (RCM) - A management application used to issue commands to radios and monitor events from radios. The Radio Control Manager (RCM) is part of the Motorola PRNM Suite. • Radio Control Manager Reports - The application provides reports of two types of functions of the RCM: radio commands initiated and radio events displayed. These applications input to or extract information from one or more of the NM servers where system configuration parameters are stored, transactional statistics are accumulated, real-time data streams are sourced, and supporting processes are performed. In addition to these “user applications,” the NM servers also run several autonomous processes in the background to support the ongoing operation of the system. Applications and processes are described later.

7.3.1.3 Network Management System Servers Motorola has integrated the NM application and database servers on the HP ProLiant DL360 Gen8 platform. The NM subsystem is comprised of the following servers at the zone and system levels of the system:

7.3.1.3.1 NM Zone-Level Servers (One Each Per Zone) • Air Traffic Router • Zone Database Server • Unified Event Manager Server • Zone Statistics Server

7.3.1.3.2 Cluster-Level Servers (One Each Per System) • User Configuration Server The role of each server is described in the following:

7-4

68015000701-C - October 2013

7.3.1.4 Zone-Level Servers

7.3.1.4 Zone-Level Servers The following describes zone-level servers.

7.3.1.4.1 Air Traffic Router The Air Traffic Router (ATR) hosts a variety of real-time, data processing applications to support user and system applications. Its functions include: • Providing the Affiliation Server, the “backend” of the Affiliation Display application • Processing real-time call transactions, being the information source for ZoneWatch and RCM • Serving as source of the Air Traffic Information Access (ATIA) data stream to third-party applications • Logging to disk ATIA data for viewing or export to a text file • Routing RCM command and status/messages to/from the Zone Controller • Routing call logging information from the Zone Controller to the Zone Statistics Server (ZSS) and System Statistics Server (SSS) • Hosting the statistics proxy agent for the Zone Controller as a source for dynamic and historical reports statistics

7.3.1.4.2 Zone Database Server The ZDS handles a variety of tasks, including: • Hosting the zone configuration database • Administering the standard and optional applications licenses • Authenticating network manager users accessing the system • Performing backend support services for user applications • Handling telephone interconnect record processing

7.3.1.4.3 Unified Event Manager Server The Unified Event Manager server handles most fault management tasks for the system. Unified Event Manager handles device discovery, supervision and synchronization.

7.3.1.4.4 Zone Statistics Server The Zone Statistics Server (ZSS) collects and stores zone-wide statistics regarding call processing traffic and air interface load. It derives this information from the Air Traffic Information Access (ATIA) stream supplied by the Air Traffic Router and from the sites. The ZSS serves up this information to the Historical Reports application, which is used to map out zone resource usage and performance.

7.3.1.5 Cluster-Level Servers The NM functions on the cluster level are performed by User Configuration Server.

68015000701-C - October 2013

7-5

System Overview

7.3.1.5.1 User Configuration Server The User Configuration Server (UCS) provides database storage and backend processes required for most system wide functions. Included are the radio records, talkgroup records, and services to automatically distribute and replicate these records in the ZDS for all zones in a multizone system. Only one UCS is required per single or multizone system. The UCS is accessible to authorized users from any client PC in the single or multizone system. To configure information for users during various stages of the system's life User Configuration Manager is used. The UCM spans cluster-level and zone-level configuration information. You can configure the following types of information: • System Configuration - Configuration of cluster-level parameters, such as Adjacent Control Channels (ACCs). • Radios - Configuration of talkgroups, multigroups, and radio users. • Security - Configuration of records that control cluster management functions • ZoneWatch Configuration - Configuration of zone-level parameters for ZoneWatch, such as filters, watch window definitions, and watch profiles. • External Configuration - Registration and configuration of all zones, RF sites and call routes that have been configured in other clusters of the system.

7.3.2 Core Services In addition to the user applications, the NM system performs a number of vital tasks and “core” services essential to its operation and maintenance. Network manager user authentication is one of the core tasks performed in conjunction with the ZDS. Another is the Application Launcher on client workstations from where each user application is started. The applications available to the user are displayed in a Microsoft® Explorer window; the License Manager running on the ZDS “checks out” a user license for the selected and authorized application. The NM system also time synchronizes the servers using Network Time Protocol (NTP) time synchronization. The ZDS serves as a secondary master clock if the primary, GPS-based reference at the MSO is not available. Finally, since the servers are interdependent, a Database Blocking process notifies users if the database is being shut down (such as for required maintenance) and terminates any open sessions. The NM provides the capability to backup each database to DAT-format cassettes. Since the UCS database is replicated in each ZDS, the system includes an application to rebuild the UCS database from the ZDS, thus providing an automatic backup of the user configuration database.

7.4 FCAPS Model in the Dimetra IP System This section details the FCAPS model as it applies to Dimetra IP systems. Many applications deal with one ore more areas in the model. Where necessary, single character symbols are used: • F for 7.4.1 Fault Management, page 7-7 • C for 7.4.2 Configuration Management, page 7-7 • A for 7.4.3 Accounting Management, page 7-8 • P for 7.4.4 Performance Management, page 7-8 • S for 7.4.5 Security Management, page 7-10

7-6

68015000701-C - October 2013

7.4.1 Fault Management

7.4.1 Fault Management Fault Management encompasses fault detection, fault isolation, and correction of abnormal operation. Central fault management tasks include: • Monitoring status history for a system and its components • Displaying system fault information • Performing diagnostics on components as needed Unified Event Manager is the fault management application for Dimetra IP systems. Unified Event Manager provides a centralized view of the operational status of an entire multizone or single zone system by displaying intuitive, graphical representations (subsystem topology maps) of the system. Problems are identified rapidly when they occur. Functions and tools also provide the ability to notify support personnel, track, diagnose, and correct faults in an effective manner. Unified Event Manager also maintains a data warehouse, storing up to 30 days of event history for report generation. Unified Event Manager offers a SNMP trap message forwarding capability to pass fault information to a higher level “Enterprise” network manager through a separate Network Interface Card (NIC).

7.4.2 Configuration Management Configuration Management gives the operator an interface for configuring the system. The interface specifies the operational parameters of devices used within a system, such as sites, base radios, switches, radios, individual users, and groups. Configuration Management establishes each component in the system, its relationship to other components, and the associated parameters of the component.

7.4.2.1 Configuration Management Applications Configuration Management applications provide a point of entry for configuring devices in the system. NM applications manage configuration information at two levels: the cluster level and the zone level.

7.4.2.1.1 Cluster-Level Configuration: User Configuration Manager The User Configuration Manager (UCM) is the network management application used to enter and maintain cluster-level configuration information. Through the UCM, the system manager can configure radios, talkgroups, critical sites, adjacent control channels, and security information at a cluster level. The UCM database stores parameters that govern access to the system and its features for the users. Stored information includes: • Identities, including radio serial number, user identifier, and group memberships • Radio user capabilities, such as priority level and the ability to place and receive telephone calls • Group and Multigroup capabilities, such as priority levels, and group memberships in multigroups • Radio user and group access to each site in the system. A network manager can limit a radio user or group to one site or a group of sites, prohibiting them from using other sites in the system • Operator information, such as privileges, passwords, network access, and identification

68015000701-C - October 2013

7-7

System Overview

7.4.2.1.2 Zone Level Configuration: Zone Configuration Manager The Zone Configuration Manager (ZCM) is a tool used to configure information for the radio system infrastructure (for example, Zone Controller, Site Controllers, base stations, and telephone interconnect devices) during various life stages of the system. Every zone has a ZCM to manage infrastructure in the zone, and each zone can support up to 100 sites, each with different infrastructure equipment. Types of information managed by the ZCM includes radio system infrastructure information for sites and equipment.

7.4.3 Accounting Management Accounting Management enables charges to be established for the use of resources in the system. The central tasks accomplished within accounting management include: • Informing users of costs incurred and resources consumed • Enabling accounting limits to be set and tariff schedules to be associated with resource use • Enabling costs to be combined where multiple resources are invoked to achieve a given communication objective The NM subsystem provides an optional licensed interface, Air Traffic Information Access (ATIA), to which third-party applications can interface for the purpose of collecting individual radio unit and talkgroup traffic data. The ATIA stream provides information on the activity of individual radio users and talkgroups, including number of calls, total call duration, number of busies, total busy time, and so on. This data can be used as input to an external accounting or billing package. Both intra- and interzone data is passed through the interface.

7.4.3.1 Air Traffic Information Access Data This interface provides the raw air traffic data for intrazone calls. With the addition of third-party products or services, ATIA allows the system owner/operator to generate billing information to charge individual departments or agencies for their use of the system.

7.4.3.2 Cluster-Level Air Traffic Information Access Packets Cluster-Level ATIA Packets provides air traffic data for interzone calls in a multizone system.

7.4.3.3 Air Traffic Information Access Logger and Log Viewer The ATIA Logger records daily worth of ATIA packets and stores them on the Air Traffic Router. The log may be viewed on a client PC.

7.4.4 Performance Management Performance Management tools are used to monitor, collect, log, and evaluate network performance and resource utilization data. Performance applications for the radio resources are described here. NM collects statistics of radio resource usage in the Zone Statistics Server (ZSS) for radio units, talkgroups, channels, sites, zones and system wide activity report generation.

7-8

68015000701-C - October 2013

7.4.4.1 Zone Historical Reports Application

Separate, performance applications display real-time communications activity (such as, ZoneWatch) or collect traffic statistics over predetermined intervals for report generation (such as, dynamic and historical reports). Historical statistics are aggregated into detailed and summarized reports on both an individual site, zone, and system wide basis. Statistics are available on an hourly basis for 10 days, daily for 62 days, and monthly for one year at a zone, site, channel, and user. Other statistics that are useful in troubleshooting, sizing, and monitoring the system are also collected. The system logs these statistics for a period of 62 days. NM also has archival and export features for saving reports or offline data analysis.

7.4.4.1 Zone Historical Reports Application This application produces reports on radio infrastructure, radio resource usage, and air interface usage within an identified zone. A predefined set of reports, with field selection capability, is supplied to produce “standard” or tailored reports. Custom reports can be developed using Historical Reports underlying Crystal Reports® reporting engine. Historical reports are generated automatically or on demand. Automatic reports are produced at a specific scheduled time and date or on a recurring time and date interval. Reports can be sent to the monitor screen, a printer, or saved as PDF, XML, HTML or Comma Separated Value (CSV) files.

7.4.4.2 Dynamic Reports Dynamic Reports are intended for short term monitoring. Report intervals may be set for 15 seconds, one minute or 15 minutes, and up to 100 intervals can be collected. Multiple objects and up to 12 statistics can be included in a single report. Like for the Historical Reports, a complete set of predefined Dynamic Reports is provided. Reports can be output to the client PC display, printer, or file. This display provides zone-level, real-time line charts that illustrate channel utilization for all call types - group, private, interconnect, control channels, and dynamically blocked calls.

7.4.4.3 ZoneWatch ZoneWatch is a performance management tool having customizable displays and grids to monitor real-time communications activity in a single zone. The information displayed can help system managers be proactive in making better resource planning decisions, such as when additional channels need to be added to busier sites. ZoneWatch Grid Screen: Air traffic within a single zone is displayed on a site/channel grid. Real-time call activity for each channel is displayed in its respective cell. ZoneWatch Control Display: This display presents call activity messages that can be used to isolate errors, trace the progress of a call and troubleshoot, or analyze current system activity. It also provides information about activity occurring on the control channels, such as rejects, emergency alarms, and unit affiliations.

7.4.4.4 Affiliation Display Upon initial power-up and as radio users move across a geographic area covered by one radio site to another, radios register to the zone and site now providing the radio service. The responsibility for providing radio service to the unit is thus “handed-off” to another zone and/or site. This mobility management function allows the Zone Controller to have knowledge of the site currently serving the unit, such that the unit can be immediately connected or included in private or group dispatch calls without having to broadcast to all sites.

68015000701-C - October 2013

7-9

System Overview

The Affiliation Display provides a dynamic view of the sites to which all operating units are currently registered, displaying zone, site, and talkgroup details. This feature makes it easy to track and troubleshoot radios in the system. Affiliation Display is not a vehicle or unit locator in an absolute sense; registration only suggests the area in which the unit may currently be operating based on the last registration of the unit and the radio coverage of the site. The focus of the Affiliation Display can be on an individual site, a specific talkgroup, or an individual radio. Graphing capabilities are also included.

7.4.5 Security Management Security Management controls or limits access to applications, certain features, and configuration data according to definable access privileges. All users must identify themselves to the system at logon by entering a name/ID and a password. The Agency Partitioning feature makes it easy to grant or restrict access by department, location, user type, application, and function.

7.4.5.1 Temporary Disable Dimetra IP allows a network management operator to temporarily disable or re-enable a radio over the air. The radio is unable to make or receive calls while it is disabled, even if the radio is turned off and turned back on. If the radio is turned on, it is still registered in the system and is able to roam.

7.4.5.2 Permanent Disable As well as Temporary Disable, Permanent Disable is also intended to protect a network from attack from a compromised or faulty radio. It shall be used when the radio is known to have been compromised, or has been suspected of compromise for a long time. Permanent disable of radio subscription, signaled by ITSI, allow disable of subscription either of the integrated radio, or of SIM where a SIM is used. Unlike the temporary disable feature, mutual authentication is a precondition for permanent disable. Performing Permanent Disable has a following effect: • All services are switched off. • No MMI functions are displayed. • All input and output ports are left in an inactive state. • All air interface keys stored in memory of the radio are deleted. • All identities stored in the codeplug, including its own ID (ITSI), and associated system identities are deleted. • The codeplug is marked as radio permanently disabled. • The codeplug is not recoverable or editable once it enters this state and can be only over-written with a new codeplug. Permanent Disable is a one way function, there is no equivalent enable function. The radio requires recovery and reprogramming before it can be used again.

7.4.5.3 User Client Security User Client Security provides the first level of security by denying access to all network management applications unless the user enters a valid logon name/ID and the corresponding password.

7-10

68015000701-C - October 2013

7.4.5.4 Security Partitioning

7.4.5.4 Security Partitioning Optional Security Partitioning allows a system administrator to assign access privileges to specific applications. These applications include Configuration Manager, RCM, Historical Reports, and ZoneWatch. The system administrator can also grant or restrict access to multizone.

7.4.5.5 Authentication Authentication prevents hostile or other unauthorized radios from registering with the system. Authentication sends a challenge to a registering radio. The radio must supply the appropriate response to access the system. If mutual authentication is being used, then the radio also sends a challenge to the infrastructure, and the infrastructure must supply a proper response. This ensures that both the infrastructure and the radio are both genuine. Authentication relies on a separate secret key for each radio provisioned in the cluster. This key is provisioned in the Provisioning Centre, Authentication Centre, and in the radio. For the Provisioning Centre and Authentication Centre, each key is stored in a secure form in a database encrypted with a tamper-proof crypto card. The key are also stored in a secure form in the radio. The Provisioning Centre is isolated from the network.

7.4.5.6 Air Interface Encryption Air interface encryption provides security for information that is being transmitted between the radios and the system infrastructure. Encryption prevents scanners and other more sophisticated equipment from collecting any intelligible traffic from users in the system. Encryption also prevents unauthorized users from being able to operate on the system without the appropriate key. The Dimetra IP system offers various air interface security features. See the list of them and the purposes they serve in the table below. Table 7-1

Air Interface Encryption - Security Features

Security Feature

Purpose

Air Interface Encryption - Dynamic Keys (DCK, GCK, CCK).

Encryption of a user and signaling data over the air interface using dynamically generated keys to protect against eavesdropping.

Air Interface Encryption - Static Keys (TM-SCK, DM-SCK).

Encryption of a user and signaling data over the air interface using predefined keys to protect against eavesdropping.

Over The Air Re-keying (OTAR).

Low cost key management.

Air interface encryption relies on Static Cipher Keys (TM-SCK used for encryption in Trunked Mode operation and DM-SCK used for encryption in Direct Mode operation) which are provisioned in the Provisioning Centre, Authentication Centre, and the individual radios. For the Provisioning Centre and Authentication Centre, these keys are stored in a secure form in a database encrypted with a tamper-proof crypto card. The keys are also stored a secure form in the radios. The Provisioning Centre is isolated from the network. Neither Static Keys nor Dynamic Keys (DCK, GCK, CCK) are distributed over the air. However, Common Cipher Keys (CCKs), which are used for group calls, are sealed with a DCK and sent over the air to radios for group calls as well as MGCK - the combination of GCK and CCK. The typical duration for the use of a CCK and DCK in the system is 24 hour and for GCK - 3 months.

68015000701-C - October 2013

7-11

System Overview

7.5 Multizone Fault Management Multizone fault management can be achieved through a network management client that has access to Unified Event Manager applications in each individual zone in the system. Since one Unified Event Manager server acts as a zone-level server in each zone, the client can view a zone connecting with the Unified Event Manager in the appropriate zone within a particular zone. Figure 7-1

Multizone Fault Management - Client Access to Each Zone

Multizone fault management can also be arranged through the forwarding of events to a central customer-supplied fault management system. This central fault management system can receive the forwarded traps from all zone-level Unified Event Manager servers in the system. The figure below illustrates the event forwarding from each zone Unified Event Manager server to a customer-supplied fault management platform. Figure 7-2 Multizone Fault Management- Event Forwarding to a Customer-Supplied Fault Management System

7-12

68015000701-C - October 2013

7.6 Introduction to Network Management Applications

7.6 Introduction to Network Management Applications Several applications are used to manage, monitor and troubleshoot your radio system. This section offers a brief description of these programs, along with their key features and information how to access them: • 7.6.1 Network Management Applications Overview, page 7-13 • 7.6.2 Private Radio Network Management Suite Applications, page 7-16 • 7.6.3 Network Transport Management Applications, page 7-24

7.6.1 Network Management Applications Overview A network management application is a software tool that helps you to manage a complex radio communications system and its components, including radios, computers, and networking components. Network management applications provide the following benefits for radio system networks: • Minimize system downtime and maintenance costs. • Maximize available resources by assisting with system resource planning. • Simplify monitoring and control of systems. • Reduce human intervention through monitoring. • Provide system security. • Reduce troubleshooting time. • Provide reporting tools to optimize system usage. • Provide near real-time monitoring.

7.6.1.1 Motorola PRNM Suite Applications Overview The PRNM Suite is a set of software applications or tools developed by Motorola to manage your radio system and its components, such as resources, users, and infrastructure. The figure shows the areas impacted by the PRNM Suite applications.

68015000701-C - October 2013

7-13

System Overview

Figure 7-3

PRNM Applications From a System Perspective

Cluster

Zone

Site

Unit

The table lists the Motorola PRNM Suite applications. These management applications are available through Application Launcher. Table 7-2

Motorola PRNM Suite Applications

Applications

FCAPS

Purpose

Application Launcher

N/A

A launch point for PRNM applications.

Software Download

C

A tool that provides software upgrades to specific devices.

System Profile

P

A tool that allows you to track usage at the system level. Shows the number of applications open, who is using the application, the number of available licenses, and the processes of the open applications.

User Configuration Manager

CS

The primary tool to configure and manage radio network users.

Affiliation Display

P

A tool to monitor radio, talkgroup, and site use. Affiliation Display spans zone, site, and radio unit levels in the figure above.

ATIA Log Viewer

P

A tool that allows you to view radio events occurring in the zone in a raw data format from the Air Traffic Router (ATR).

Dynamic Reports

AP

A report tool that provides predefined reports using data taken dynamically from the database.

Cluster-Level Applications:

Zone-Level Applications:

7-14

68015000701-C - October 2013

7.6.1.2 Other Motorola Applications

Table 7-2

Motorola PRNM Suite Applications (cont'd.)

Applications

FCAPS

Unified Event Manager includes:

FPS

The primary fault management tool that you can use to monitor the status of the system. Unified Event Manager spans system and zone-level activity in the figure above.

Historical Reports

AP

A reporting tool that uses predefined reports to show data from archived information. Historical Reports spans zone, site, and unit levels in the figure above.

Radio Control Manager Reports

AP

A reporting tool that provides reports on radio activity.

Radio Control Manager

CS

The primary tool used to control and monitor radio activity. Has configuration capability in the Dynamic regrouping feature. Radio Control Manager spans zone, site, and unit levels in the figure above.

Zone Configuration Manager

C

The primary tool used to configure infrastructure equipment and other zone-level parameters.

Zone Profile

P

A tool to track usage at a zone level. Shows the number of applications open, who is using the application, the number of available licenses, and the processes of the open applications.

ZoneWatch

FP

A tool that monitors call processing resource assignments, including channels, sites, and any hardware assigned to a call. ZoneWatch spans zone, site, and unit levels in the figure above.

• Unified Event Manager Administration

Purpose

• Unified Event Manager Web Browser • Unified Event Manager

7.6.1.2 Other Motorola Applications The table lists other Motorola applications that are used to configure RF infrastructure equipment and radios. Table 7-3

Other Motorola Applications

Application

FCAPS

Purpose

Dimetra™ BTS (Base Transceiver Station)

CF

A tool used to configure and service the Site Controllers and BTS base radios.

Customer Programming Software (CPS)

C

A tool that programs radios. You can also use it to learn the operating parameters, personalities, and modes of radios. This software is documented in the CPS application for your radio. The CPS Online Help is available from the Help menu.

68015000701-C - October 2013

7-15

System Overview

7.6.2 Private Radio Network Management Suite Applications The following describes the PRNM Suite applications, including how to access the applications using Application Launcher.

7.6.2.1 Application Launcher Application Launcher is the starting point to access the PRNM management Suite applications. Application Launcher provides a quick and easy way to access one or more management applications without going through the process of logging on to each application separately and entering your user name and password each time. Application Launcher provides two ways to access the applications: • Start menu • Windows Explorer window You can launch applications from the Start menu or an Explorer window that is launched from a desktop icon. The system manager assigns permissions to each user in the cluster. These permissions determine which applications, security groups, and objects you can access. These permissions also determine your view of the system by displaying only the cluster-level applications, zones, and zone-level applications for which you have access permissions in the Windows Explorer window. Application Launcher allows you access to the applications that manage and monitor the clusters and zones. It also allows you to do the following: • View applications available for the cluster and for each zone. • Change and store your password. • Change server access. • Exit Application Launcher in a secure manner so that the next user is prompted to log on.

7.6.2.2 Affiliation Display Affiliation Display is an PRNM Suite application that monitors the mobility of radios for a particular zone. Mobility describes how radio users travel between different sites in a zone and how they communicate with other members of their assigned talkgroup or even with members outside of their talkgroup. You can view a radio in more than one zone. As a radio roams from one site to another or changes talkgroups, Affiliation Display updates and displays the affiliation and deaffiliation information for a monitored radio. Affiliation Display enables you to view the association of a radio with a talkgroup and site. This information can be useful for troubleshooting and tracking of radios in the system and for monitoring the movement of traffic within a zone. The affiliation information is displayed in four ways: for the entire zone, by site ID, by talkgroup ID, or by radio ID. This information is near real-time data and is only available when the application is open. Specifically Affiliation Display allows you to do the following: • Monitor affiliation for one or more radios using the Radio Viewer at one or more sites. You can locate specified radios by ID. • Monitor affiliations by site using the Site Viewer and view a list of talkgroups or radios at a site. • Monitor affiliations by talkgroup using the Talkgroup Viewer. You can view information for sites at talkgroup or radios at talkgroup.

7-16

68015000701-C - October 2013

7.6.2.3 ATIA Log Viewer

Affiliation Display can be used to perform the following functions: • Monitor selected radios, talkgroups, and sites dynamically using the main window. Monitors affiliation and deaffiliation information for the location of radios and their current talkgroup at a site within a zone. • Note the radio communication about a site, so you can see how traffic moves within sites in a zone. By tracking selected talkgroups and radio users through a zone, you can see which sites get the most use. • From the Talkgroup Viewer, create a dynamic graphical display of radio usage at a site. The usage information is captured in a graph format for talkgroups and sites.

7.6.2.3 ATIA Log Viewer ATIA Log Viewer is a PRNM Suite application that allows you to view the raw ATIA data straight from the ATIA log.

You must first enable ATIA data logging through the ATR server's Administration menu. Otherwise, no ATIA log data is collected for viewing. The ATIA Log Viewer is a technician tool that allows you to examine air traffic historical data in a specified zone for one or more particular time intervals. You can also do the following: • View the radio events occurring in a zone. The information is the same as what you view from ZoneWatch, but is presented in a raw data format from the ATR server. Shows active sites, channel numbers, and radio affiliations. • View a log of what occurs on an hourly interval in the zone. The ATIA Log Viewer allows you to examine historical air traffic data in a specified zone for a particular time interval or intervals. This feature is normally used to examine data logs when debugging the system. The ATIA Log Viewer records the last 25 hours of ATIA data packets on the ATR server. The data is displayed on an hourly basis, and you can select which interval packets you want to view. The data is displayed in an easy-to-read format and can be printed or saved for future evaluation. Since the information displayed in the ATIA Log Viewer is a text document, you can format the information, if required using a third-party application.

7.6.2.4 Custom Historical Reports Custom Historical Reports is very similar to Historical Reports. Like Historical Reports, it uses a third-party application (Seagate® Crystal Reports®) but the difference is that you can create your own reports. You select the parameters for the report instead of using predefined parameters and templates that Historical Reports uses. If you need to customize your performance reports , the Custom Historical Reports is an software package that allows you to modify existing report templates and create new templates to meet your system needs. Using a report generator, you create a customized report with the parameters that you want. Custom Historical Reports uses Crystal Reports® to step you through a series of dialogue boxes to define each set of parameters that you could include in the report.

68015000701-C - October 2013

7-17

System Overview

The Custom Historical Report features apply only to Historical Reports and not to Dynamic Reports. Custom Historical Reports has the following features: • The Report Expert wizard from Crystal Report® allows you to select from parameters collected by the ATIA stream or other reports. • Reports may be customized to suit your individual needs. Customization includes: – Group and sorting – Charts (bar, line, 3-D) – Top and bottom X filtering – Calculated values – Cross tab, form, form letter, drill-down reports • Special formulas can be included in Custom Historical Reports to create certain effects.

7.6.2.5 Dynamic Reports Dynamic Reports is a PRNM Suite application that provides near real-time call data collection and allows you to display usage trends and patterns of activity for effective monitoring and reporting. Dynamic Reports is based on a third-party application (Seagate® Crystal Reports®). Dynamic Reports provides predefined parameters and template formats to display the value of multiple statistics for one or more managed objects. Once a report is activated, a Dynamic Report window appears and data is plotted according to the object and the time interval selected. At the end of each interval, a new set of statistical values is added to the display. When the display reaches the specified number of intervals, each new interval added causes the oldest interval to be removed from the display.

Dynamic Reports are not available at the cluster level. Use Dynamic Reports to monitor and report usage trends and patterns of activity. You can do the following: • Generate real-time line graphs for a zone or site. • Use predefined formats to display the value of multiple statistics for a zone or site. Use the data to make changes in how radios and talkgroups are managed. You can closely examine what happens during a shift or set period of time; for example, you can look at the busy count and see if calls are being missed. Based on your monitoring, you could recommend system expansion or decide to modify your system design to improve communication.

7.6.2.6 Unified Event Manager Unified Event Manager is a PRNM Suite application that is the primary fault management tool for your system. You can use Unified Event Manager to monitor the status of the zones.

7-18

68015000701-C - October 2013

7.6.2.7 Historical Reports

Unified Event Manager allows you to monitor the status of components at zone level, such as servers, Zone Controllers or sites in the zone. • The zone level submap displays only one zone. Unified Event Manager is the primary troubleshooting tool that allows you to view alarm information. You use Unified Event Manager to monitor the status of devices in the zone. • Submap views show the status of devices by color and the graphical representations of alarm information. • Alarm Categories show different categories of alarms, for the radio system, routers, or other devices. • Alarms Browsers show a record of what devices are sending alarms or events. Unified Event Manager communicates with managed RF system devices using Simple Network Management Protocol (SNMP), the industry standard communication protocol. Unified Event Manager integrates the fault management of Motorola devices and that of approved third-party devices.

7.6.2.7 Historical Reports Historical Reports is a PRNM Suite application that allows you to generate reports for cluster wide activity and for individual zones. These reports display data that is stored on the server. You can use Historical Reports for resource management. For example, you can determine if interconnect resources are being overused because too many interconnect calls appear in the report. Historical Reports allows you to do long term analysis of traffic data. The Historical Reports application generates reports of statistical data that is gathered at specific, predefined time intervals. You can then create reports from this data to monitor and analyze information about zones, sites, channels, talkgroups, and radio users. This data is displayed using predefined report templates and parameters. Historical Reports is based on a third-party application (Seagate® Crystal Reports®). Historical Reports uses predefined report templates and specified time intervals to create a report. You can use Historical Reports to do the following with the report: • View the reports on screen or print a hard copy. • Export the report to one of the following formats: – Comma Separated Values (CSV) - Creates a text file where entries are separated by commas. This format is suitable for export to database applications, such as Microsoft® Access. – HTML-Creates an HTML version of the report. This format is suitable for viewing in a number of external applications such as Web browsers and word processors. • Use the Report Scheduler window to schedule zone-wide and system wide reports to occur automatically at specified times with an output to a printer or data file.

7.6.2.8 Radio Control Manager The Radio Control Manager (RCM) is a PRNM Suite application used to monitor radio events, issue and monitor commands, and make informational queries of the system. The RCM enables you to monitor and manage radio events and commands and to search the database for radio status information. Using the RCM, you can do the following: • Submit radio commands over the air, select radios to receive the commands, and track the progress of the commands. After you issue a radio command, you can view the command and its status in the Command Monitor.

68015000701-C - October 2013

7-19

System Overview

• Submit queries to check the status of the radio. • Monitor events in real time as the information becomes available in the system. An event is an unsolicited message sent from a radio or a solicited command. You can view and acknowledge radio events in the system. • Create reports. You can create reports for emergency alarms, login sessions, and radio commands using the RCM Reports application.

All monitoring displays are updated in near real-time as the information becomes available in the system.

7.6.2.9 Radio Control Manager Reports Radio Control Manager (RCM) Reports is a PRNM Suite application that is used to create, view, print, and export standard reports from RCM. These reports use a common format so the data can be used in spreadsheets. The report information is gathered from current or archived entries in the RCM. RCM Reports enables you to present and analyze data showing RCM activity on the system. You can create reports that show the following: • Current Login sessions-View who is currently logged in. • Emergency alarm reports-Monitor a historical list of emergency alarms received by RCM in a selected period. • Radio commands-View radio commands grouped by command, user or radio. You can export RCM Reports as PDF, HTML, XML, or Comma Separated Values (CSV) files for use with other applications. All RCM reports can be scheduled.

7.6.2.10 Software Download Manager The Software Download (SWDL) Manager is a PRNM Suite application used to transfer and install new software from a central location at the zone core or locally at a remote site. Software Download supports loading to the Site Controllers and base stations. The SWDL Manager allows you to do the following tasks: • Download software to Site Controllers and base stations. • Upload log files from Site Controllers and base stations. • The configuration can be manipulated via a script installed on the NM client. After being manipulated or changed via the script, the configuration file can be downloaded to the base station again by the Software Download application. There is a single configuration file set for the base station which can be downloaded to the SC • When using the Software Download application, base station software files can be downloaded to more than one base station in parallel. • Determine the software version. • Obtain device IP information. • Query the Site Controller for the number of channels at the RF site. • Purge (delete) a software version from selected target devices. • Audit a session using historical information recorded by SWDL Manager.

7-20

68015000701-C - October 2013

7.6.2.11 System Profile

7.6.2.11 System Profile The System Profile is a PRNM Suite application that displays how cluster-level applications are being used by the network management clients. System Profile shows the following cluster-level Private Radio Network Management Suite (PRNM) applications: • User Configuration Manager (UCM) • Historical Reports • Software Download The System Profile application displays information about users that are accessing cluster-level applications. The following are key features: • User Application DistributionThe User Application Distribution tab displays a list of cluster-level applications that are being run on network management clients in the system. The User Application Distribution tab also shows the login name of the user and the time the application was started. • License Usage The Licence Usage tab shows the purchased licenses for each of the cluster-level applications and shows the number of licenses that are currently in use.

7.6.2.12 User Configuration Manager The User Configuration Manager (UCM) is a PRNM Suite application used to enter and maintain radio related configuration information for the User Configuration Server (UCS). The UCM configures information for initial configuration of the system and then is used as needed to update the information. To configure a Dimetra IP system, you need to enter information into both the UCM in each cluster, and the Zone Configuration Manager (ZCM) in each zone. When you initially configure or make changes in the UCM, the configuration information updates the UCS and is replicated to the Zone Database Server (ZDS) in each zone in the cluster. Use the UCM to perform the following tasks: • Configure cluster-level parameters for call capability, including the Adjacent Control Channels (ACCs) and interzone control paths. • Configure radios, radio users, talkgroups, and multigroups. • Configure security access for users in the system. • Configure the type of ZoneWatch windows that users want to monitor.

You must create at least one watch profile before you can start ZoneWatch. The UCM spans cluster-level and zone-level configuration information. The table below shows the objects classes.

68015000701-C - October 2013

7-21

System Overview

Table 7-4

Object Classes in UCM

Object Types

Description

System Configuration

Configuration of cluster-level parameters, such as Adjacent Control Channels. (ACCs) and interzone control paths.

Radios

Configuration of zone-level parameters, such as talkgroups and radio user information. You can also set up home zone mapping, sub-band restricted mapping, and use profiles to quickly create records.

Security

Configuration of cluster-level parameters for management users, such as security information.

ZoneWatch Configuration

Configuration of zone-level parameters for ZoneWatch, such as filters, watch window definitions, and watch profiles.

External Configuration

Registration and configuration of all zones, BTS sites and call routes that have been configured in other clusters of the system. Not applicable to single-cluster systems.

7.6.2.13 Zone Configuration Manager The Zone Configuration Manager (ZCM) is a PRNM Suite application that is used to configure and maintain operational parameters for equipment in the zone. The Zone Database Server (ZDS) hosts the ZCM database, which stores configuration information for the zone's infrastructure equipment. To configure a Dimetra IP system, you need to enter information into both the ZCM and the UCM. Use ZCM to manage the infrastructure in a zone. Infrastructure refers to the physical equipment in the zone, such as the BTS base radios, MTIGs, and the Zone Controller. Use the ZCM application to perform the following tasks: • Configure the zone infrastructure equipment. • Execute diagnostic commands to force a device in the zone into a certain functional state.

7.6.2.13.1 High-Level Objects in ZCM The ZCM spans zone-level configuration information. For example, you can configure zone-level parameters such as BTS sites. The table shows the high-level objects. Table 7-5

7-22

High-Level Objects in ZCM

Object Types

Description

Zone

Configures and manages the attributes relating to a zone.

Air Traffic Router

Configures the ATR server, which collect statistics on the system and distributes airtime usage data.

Zone Controller

Represents the Zone Controller for the zone. Provides access to the Rendezvous Point (RP) routers.

Level of Service

Configures the level of service availability for call requests, such as the number of interconnect calls allowed or the average maximum busy delay that is acceptable for group calls or interconnect calls.

Packet Data Gateway

Represents the packet data gateway.

68015000701-C - October 2013

7.6.2.14 Zone Profile

Table 7-5

High-Level Objects in ZCM (cont'd.) Object Types

Description

Application Platform

Configures the application platform, which hosts the MTIG application. Provides access to the MTIG object as well as the voice and line card related objects.

Console Site

Configures remote and colocated consoles.

BTS Site

Configures the BTS site operations within a zone, setting the parameters for a site so that it functions correctly in the system.

Switch

Configures the switch within a zone, plus the paths, slots, and cards, and connections for the switch.

Interconnect Subsystem

References the telephone interconnect equipment in the zone and represents the path selection for telephone interconnect calls.

7.6.2.14 Zone Profile Zone Profile is a PRNM Suite application that displays detailed information about the applications that are operating in the zone. Use Zone Profile to perform the following tasks: • View the zone-level application usage. • View the zone-level application license usage.

7.6.2.15 ZoneWatch ZoneWatch is a PRNM Suite application that lets you monitor radio call traffic for an individual zone in real time. This application uses different watch windows that allow you to display only the information you need to see. Examples of trunking activity and radio call traffic displayed in the watch windows include the following: • Radio IDs • Talkgroup IDs • Aliases • Specific call information • Channel assignments This application monitors all radio call activity by pulling trunking information from the Air Traffic Router (ATR) server, which receives updates from the Air Traffic Information Access (ATIA) stream distributed by the Zone Controller. ZoneWatch uses different types of watch windows to display zone, site, talkgroup, and radio information for a specific zone. The different window profiles, which contain window definitions and filters, define how to display the information and how to apply limits to the type of data that you can view. The following are examples of the types of information that you may choose to view: • Activity in a Zone You can open ZoneWatch to monitor radio call activity within a zone. You can see constantly updated information on who is using the system, where the radio users are located, what infrastructure resources are being used, and any significant changes in system usage. • Message Type Information can be selectively displayed by one or any combination of message types.

68015000701-C - October 2013

7-23

System Overview

• Raw Data A Raw Data filter allows the selection or exclusion of information. The data that is selected for inclusion is displayed as raw data (no formatting). • Site Information A site filter object allows you to specify the site that the ZoneWatch user wants to monitor. The site selection must consist of a site within the same zone as the ZoneWatch. The site filter essentially limits the view to only a specific site in a zone. You can, however, have other windows open to show information from other sites in the zone.

7.6.3 Network Transport Management Applications The following describes the launching mechanisms for the transport network management applications. These applications are accessible through the Network Transport Management (NTM) client.

7-24

68015000701-C - October 2013

Appendix A: Dimetra IP System Documentation This appendix provides a listing of manuals applicable to the hardware, software, and features in a Dimetra IP system. Table A-1

Document Title

Description

Glossary

The glossary provides a list of abbreviations, acronyms and terms used in the Dimetra IP system documentation.

Documentation Overview

The document provides a list of all documents delivered with your Dimetra IP system. Its primary purpose is to help you to find the information you are looking for.

System Overview

This manual provides basic radio system concepts, call processing basics, and an introduction to the various components and processes associated with the Dimetra IP system. The manual provides the background needed to comprehend the theory of operation and it provides equipment/subsystem functional descriptions. It also describes the role of the numerous network management software applications used for managing the system.

Standards and Guidelines for Communication Sites

This manual provides standards and guidelines to follow when setting up a Motorola communications site. Also known as R56 manual.

Zone Controller

This manual describes the Zone Controller which is responsible for processing calls, managing audio paths, controlling zone infrastructure, and providing services to subscribers and console operators.

System LAN Switches

This manual describes LAN switches used in the Dimetra IP system. Included are detailed procedures for installation, configuration and operation.

S6000 Router

This manual describes the S6000 router used in the Dimetra IP system. The router provides the following network transport functions for the whole system:

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

• Router used in E1 configurations, including gateway, core, and exit routers • Router used in Ethernet configurations, including discreet and combined routers GGM 8000 Gateway

68015000701-C - October 2013

This manual describes the GGM 8000 Gateway and how it is used in the Dimetra IP system. Included are detailed procedures for installation, configuration and maintenance.

A-1

System Overview

Table A-1

(cont'd.)

Document Title

Description

Cooperative WAN Routing

This manual describes the Cooperative WAN Routing (CWR) solution that allows core and exit routers to interface directly with site and interzone links through a simple, reliable, and passive relay panel. The core and exit routers are configured in pairs to provide path redundancy for audio and control packets. With CWR, the routers work to control an external relay panel to switch a group of 12 non-redundant E1 links between the two routers in a pair.

Ethernet Site Links

This manual contains information on the Ethernet Site Links (ESL) feature, which provides a means to establish Ethernet connections of the following type:

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

• Base station links (single and redundant) • Inter-zone links • Remote control site links terminated at non-redundant control site routers Link Encryption

This manual describes the technical solution for setting up Encryption and Authentication, which is an extension to the Ethernet Site Links (ESL) feature, on Routers and Base Stations.

Network Management Servers

This manual describes the Network Management (NM) Servers used in the Dimetra IP system. Included are detailed procedures for installation, configuration and maintenance. The NM servers are comprised of User Configuration Server (UCS), System Statistics Server (SSS), Zone Database Server (ZDS), Air Traffic Router Server (ATR), Zone Statistics Server (ZSS) and Unified Event Manager (UEM) Server.

Network Management Client

This manual provides an introduction to the hardware and software components associated with the Network Management (NM) Client. Included are detailed procedures for installation and configuration of the client.

Remote Access

This manual describes the Terminal Server which is used for local and remote serviceability, also referred to as out-of-band management. The manual provides an introduction to the hardware and software components associated with the Terminal Server. Included are detailed procedures for installation, configuration and troubleshooting the Terminal Server.

A-2

68015000701-C - October 2013

Appendix A Dimetra IP System Documentation

Table A-1

(cont'd.)

Document Title

Description

Network Time Server

This manual describes the Network Time Server (NTS), which provides a UTC time and date reference to all IP connected system elements (NTP clients) that support the Network Time Protocol (NTP). The manual contains all information necessary to install, configure and use the server in the system.

Backup and Restore Including FRU/FRE

This volume contains the system backup and restoration procedures and their impact on the services as well as pre and post-restoration checks. The volume also describes how to perform FRU/FRE procedures.

Safety Guidelines for Installation of Hardware and Software

This manual describes the general safety guidelines to be followed in connection with installation of hardware and software. It is a part of Backup and Restore Including FRU/FRE.

Server Software Restoration

This manual describes how to perform restoration of all application servers. Additionally it contains instructions for scheduling or creating a backup on-demand. It is a part of Backup and Restore Including FRU/FRE.

Server Hardware Restoration

This manual describes how to perform restoration of all system servers hosting application servers. The manual also describes how to perform FRU/FRE procedures for these servers. It is a part of Backup and Restore Including FRU/FRE.

Stand-alone Components Restoration

This manual describes how to backup and restore the following components of a new Dimetra IP system:

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

• Network Management (NM) Client • Standalone Provisioning Centre (PrC) Client • Key Management Facility (KMF) • Echo Canceller • CryptR2 It is a part of Backup and Restore Including FRU/FRE. Network Transport Restoration

This manual describes how to backup and restore the system LAN switches, routers, gateways, CWR Patch Panel, Terminal Server, and Network Time Server. It is a part of Backup and Restore Including FRU/FRE.

Console Sites Restoration

This manual describes how to backup and restore all components of the MCC 7500 subsystem, both its clear and secure versions. The manual also describes how to perform FRU/FRE procedures. It is a part of Backup and Restore Including FRU/FRE.

68015000701-C - October 2013

A-3

System Overview

Table A-1

(cont'd.)

Document Title

Description

MTS 1 Restoration

This manual describes how to backup and restore the Motorola Transceiver System (MTS) 1. The manual also describes how to perform FRU/FRE procedures. It is a part of Backup and Restore Including FRU/FRE.

MTS LiTE, MTS 2 and MTS 4 Restoration

This manual describes how to backup and restore the Motorola Transceiver System (MTS) LiTE, 2 and 4. The manual also describes how to perform FRU/FRE procedures. It is a part of Backup and Restore Including FRU/FRE.

EBTS Restoration

This manual describes how to backup and restore the Enhanced Base Transceiver System (EBTS). The manual also describes how to perform FRU/FRE procedures. It is a part of Backup and Restore Including FRU/FRE.

Fault Management

This manual provides an overview of Fault Management features and contains troubleshooting procedures.

Unified Event Manager

This manual provides an introduction to the Unified Event Manager (UEM). Included sections are a comprehensive introduction, tools used for troubleshooting, and system-level troubleshooting. UEM is an application that provides reliable fault management services for the Dimetra IP system.

ZoneWatch

This manual describes ZoneWatch which is a Private Radio Network Management (PRNM) Suite application that lets you monitor radio call traffic for an individual zone in real time. ZoneWatch uses different watch windows that allow you to display only the information you need to see.

System and Zone Profile

This manual describes the System Profile application and the Zone Profile application which are both a Private Radio Network Management (PRNM) Suite application. The System Profile application displays how system-level applications are being used by the network management clients. For instance, you can view information for applications in the system including the total number of applications purchased, number of licenses in use, and who is currently using the application. The Zone Profile application displays detailed information about applications that are operating in the zone. You can use Zone Profile to view the zone-level application usage and view the zone-level application license usage.

A-4

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

68015000701-C - October 2013

Appendix A Dimetra IP System Documentation

Table A-1

(cont'd.)

Document Title

Description

System Alarms and Events

This manual lists all the possible alarms for the system. It also covers transient alarm messages, which are known as technician messages. This manual is intended for technicians, network management personnel, or any other engineering personnel with responsibility for troubleshooting or monitoring the operational status of the system.

User Configuration Manager

This manual describes the User Configuration Manager (UCM) which is a Windows based, Private Radio Network Management (PRNM) Suite application. The UCM is used in the configuration of the system. It is also the tool used to modify configuration parameters. To configure a system, both the UCM and the Zone Configuration Manager (ZCM) are needed.

Zone Configuration Manager

This manual describes the Zone Configuration Manager (ZCM) which is a Private Radio Network Management (PRMN) Suite application. The ZCM is used to configure and maintain operational parameters for equipment in a system. To configure a system, both the ZCM and the User Configuration Manager (UCM) are needed.

Configuring Features

This manual describes radio features and their configuration. The manual contains a configuration checklist as well as configuration procedures for the key features of the system.

Software Download

This manual describes the Software Download (SWDL) Manager which is a Private Radio Network Management (PRNM) Suite application that can transfer and install new software in the Dimetra IP Base Transceiver Systems (BTS).

Radio Management

This manual describes the radio features available to radios in the Dimetra IP system.

Affiliation Display

This manual describes Affiliation Display which is a Private Radio Network Management (PRNM) suite application. Affiliation Display enables you to view the association of a radio with a talkgroup and site, information about conventional channels, console sites, and consoles and to monitor how radio users travel between different sites in a zone and how they communicate with other members of their assigned talkgroup or even with members outside of their talkgroup.

68015000701-C - October 2013

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

A-5

System Overview

Table A-1

(cont'd.)

Document Title

Description

ATIA Log Viewer

This manual describes the Air Traffic Information Access (ATIA) Log Viewer which is a Private Radio Network Management (PRNM) Suite application that displays log files generated by the Air Traffic Router (ATR). These log files contain records of all recent zone activity, such as site registrations and calls processed. ATIA Log Viewer allows you to view the raw ATIA data straight from the ATIA log.

Radio Control Manager

This manual describes the Radio Control Manager (RCM) which is a Private Radio Network Management (PRNM) Suite application used primarily by dispatchers to monitor and manage radio events, issue and monitor commands, and make informational queries of the system database.

Radio Control Manager Reports

This manual describes the Radio Control Manager (RCM) Reports which is a Private Radio Network Management (PRNM) Suite application that is used to create, view, print, schedule and export standard reports from RCM. These reports use a common format so the data can be used in spreadsheets. The report information reflects the actual RCM server database information except the Emergency Alarms.

Fleetmapping

This manual describes how to properly plan for, set up, and manage your system. The Motorola engineering team works with your organization to plan, and set up your system. Accurate operational requirements are needed to ensure a successful system plan. By properly configuring the Dimetra IP system to meet your operational needs, your organization will have the most efficient and effective communications system available.

Performance Management

This manual provides an overview of Performance Management features. By monitoring the performance of the system, you can identify potential problems before they occur as well as adjust system resources to provide optimum performance.

Dynamic Reports

This manual describes Dynamic Reports which is a Private Radio Network Management (PRNM) Suite application that provides predefined report templates you can use to display statistics for a zone, site or a console site (but not for a system) in near real time.

A-6

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

68015000701-C - October 2013

Appendix A Dimetra IP System Documentation

Table A-1

(cont'd.)

Document Title

Description

Historical Reports

This manual describes Historical Reports which is a Private Radio Network Management (PRNM) Suite application that allows you to generate reports for system-wide activity and for individual zones. These reports display data that is stored on the server. The Historical Reports application generates reports of statistical data that is gathered at specific, predefined time intervals. You can then create reports from this data to monitor and analyze information about zones, sites, channels, talkgroups, and users.

InfoVista

This manual describes InfoVista™ which is a customizable performance management application. InfoVista interfaces with, and gathers data from, multiple network devices supporting Simple Network Management Protocol (SNMP) including master site routers, Ethernet LAN switches, and WAN switches. The InfoVista client application is used to access server software and perform administrative tasks such as starting and stopping existing reports, adding an instance, or creating a new report.

Security Management

This manual provides a security overview for the Dimetra IP system. Attacks on communications networks could interrupt mission critical operations, compromise classified or restricted information, and contribute indirectly to loss of lives. The manual presents an overview of the security application users, describes the security groups and applications, and describes how to configure and optimize the applications for secure operation.

Agency Priority Matrix (APM)

This manual describes the Agency Priority Matrix which is a feature used for controlling which talkgroups or radio users can be assigned to each RF channel resource in the system. The manual describes how to configure, operate, maintain, and troubleshoot the Agency Priority Matrix.

Radio User Assignment/Radio User Identity (RUA/RUI)

This document describes the Radio User Assignment/Radio User Identity (RUA/RUI) feature. The purpose of this manual is to provide a user with a background knowledge on the feature as well as enable to install, configure and maintain the Alias Server. It also describes how to operate RUA/RUI from the Alias Provisioning Client.

68015000701-C - October 2013

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

A-7

System Overview

Table A-1

(cont'd.)

Document Title

Description

Data Subsystem

This manual describes the Data Subsystem and its components. It provides information on how to install, configure, operate and maintain the equipment and software including the Packet Data Gateway (PDG), Short Data Router (SDR), and Gateway GPRS Support Node (GGSN) Router. The Data Subsystem performs registration services for packet data users, maintains user permissions and mobility information, and provides routing of traffic to the radio network and the Gateway GPRS Support Node (GGSN) Router.

MultiCADI

This manual describes the Computer Aided Dispatch Interface (CADI) which is an Application Programming Interface (API) that provides the capability for systems external to the Dimetra IP SwMI to obtain information about, and exert some control over, radios. The CADI API enables third parties to write software applications called CADI clients that can receive events from, and submit commands to, the Dimetra IP SwMI. Multi-Computer Aided Dispatch Interface (MultiCADI) is a server application and an API, which enables third parties to develop application programs that can utilize the facilities provided by the CADI in the Dimetra IP system. The MultiCADI API builds upon the CADI API, but provides additional capabilities.

Telephone Interconnect

This manual provides the information necessary to install, configure, operate, and maintain the components in a Telephone Interconnect subsystem. The Telephone Interconnect subsystem provides an interface between the Dimetra IP radio network and an external telephone network, allowing telephone interconnect calls to be made between Dimetra IP radios and external telephones.

Active Directory/Domain Name Services

This manual describes Active Directory (AD) which is the service that provides access to enterprise-wide data and improved integration with the rest of the radio system. The manual contains procedures for installation and configuration of software necessary to make Active Directory operational. It also contains procedures for adding users and groups, and for backup and restore of Active Directory.

TESS Software User Guide

This manual is an introduction and guide to the use of the Dimetra BTS (Base Transceiver System) Service Software. Through the Dimetra BTS Service Software trained service personnel and systems engineers can configure and program a BTS.

A-8

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

68015000701-C - October 2013

Appendix A Dimetra IP System Documentation

Table A-1

(cont'd.)

Document Title

Description

Transport Network Device Manager (TNDM)

This manual describes the Transport Network Device Manager (TNDM), which allows you to deploy previously prepared configurations to network devices. It also allows for tasks such as: rebooting devices, uploading firmware, checking firmware version, configuration backup and restore, checking device connectivity.

Alphanumeric Text Service (ATS)

This manual describes the Alphanumeric Text Service (ATS) application, which enables text messages to be sent between Mobile Stations (MS), Dispatch Consoles and computers in the fixed network.

Backup/Restore Collector Application User Guide

This manual describes the Backup/Restore Collector application which provides a simple way of fetching backup files from a group of the Dimetra IP network elements via FTP. The network elements can be configured to run scheduled backups and store these backups on local disk – typically during the night when there is a smaller load of the system. The role of the Backup/Restore application is to collect these files and provide a centralized point of storage for them. The backup files are accessible by FTP for collection either manually or from a server running an automated procedure. The files can be restored from their centralized storage location back to the network elements.

UCS Synchronization Tool

This manual describes the User Configuration Server (UCS) Synchronization Tool, which provides automated intercluster configuration of some of the UCS objects that require to be registered in all clusters in a multicluster system.

Local Gateway Trunking

This manual describes the local gateway trunking functionality, its operational aspects, and its configuration.

Dimetra Enhanced Software Update User Guide

This manual describes the Dimetra Enhanced Software Update feature, which provides backup and restore functionality, and upgrade functionality.

68015000701-C - October 2013

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

A-9

System Overview

Table A-1

(cont'd.)

Document Title Authentication and Encryption Overview

Description

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

This manual gives an overview of the authentication and air interface encryption features in the Dimetra IP system including: • Description of the authentication and air interface encryption features • Description of the different aspects of secure encryption key management • Procedures for configuring these features in your system

Authentication Overview

This manual gives an overview of the authentication features in the Dimetra IP system including: • Description of the authentication features • Description of the different aspects of secure encryption key management • Procedures for configuring these features in your system

Authentication Centre (AuC) User Manual

This manual contains the installation, configuration and operation procedures for the Authentication Centre (AuC). It contains reference information and detailed descriptions of the GUI.

Clear Authentication Centre (AuC) User Manual

This manual contains the installation, configuration and operation procedures for the Clear Authentication Centre (AuC). It contains reference information and detailed descriptions of the GUI.

Provisioning Centre (PrC) User Manual

This manual describes how to use the Provisioning Centre (PrC) application. The main functions of the Provisioning Centre are: • Providing secure (encrypted) storage of subscriber keys • Providing secure upload and download facilities for subscriber keys and key data • Displaying up-to-date information about the key status of the radios • Exporting K-Ref data to permanent storage media • Generating audit trail and radio information.

A-10

68015000701-C - October 2013

Appendix A Dimetra IP System Documentation

Table A-1

(cont'd.)

Document Title

Description

Clear Provisioning Centre (CPrC) User Manual

This manual describes how to use the Clear Provisioning Centre (CPrC) application. The main functions of the Provisioning Centre are:

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

• Providing secure storage of subscriber keys • Providing secure upload and download facilities for subscriber keys and key data • Displaying up-to-date information about the key status of the radios • Exporting K-Ref data to permanent storage media • Generating audit trail and radio information. Secure Voice, Data and Key Management

This manual provides information on hardware, software and system operation, including procedures for installing the Key Management Facility (KMF) system and for using Over-The-Air-Key Management (OTAK) and Over-The-Ethernet-Key Management (OTEK) commands.

MCC 7500S Dispatch Console

This manual describes all necessary actions to configure and maintain the MCC 7500S console subsystem. The subsystem allows two-way console and radio - console transmissions to be encrypted and secure.

MCC 7500S ICCS Gateway

This manual describes installation, configuration, operation, maintenance and troubleshooting of the components in a secure Integrated Command and Control System (ICCS) gateway including the Pyramid PC and the multiplexer. The ICCS Gateway Subsystem is a type of MCC 7500 console site, designed to meet the demands of customers, who want to implement or already have implemented their own custom-developed Integrated Command and Control System, that is, a non-Motorola control room. This manual describes also the ICCS Gateway Discreet Listening feature on the Dimetra IP system.

CryptR and Audio Module for Replay

This manual describes installation, configuration, operation, maintenance and troubleshooting of Audio Module used for replay purposes and configuration of CryptR used for call logging. Together with the AIS and third party replay devices they are part of the End-to-End Encryption Call Logging Subsystem.

End-to-End Secure Packet Data and Short Data

This manual describes configuration and operation of the End-Two-End Encryption (E2EE) feature for short and packet data (SD, PD) on the Dimetra IP system.

68015000701-C - October 2013

A-11

System Overview

Table A-1

(cont'd.)

Document Title

Description

Network Security

This manual describes all necessary actions to install, configure and maintain the network security feature within the Dimetra IP system. The intention of the manual is to enable the reader to deploy the best possible level of security, which will protect the system against viruses, unauthorized authentication or attacks of hackers. The network security feature provides virus protection, authentication, and firewall protection.

End-to-End Encryption KVL3000 Plus User Guide

This manual describes how to configure the KVL 3000 Plus for initial use, and entering and storing encryption keys in to target devices, such as radios, CryptRs and Mobile CryptRs.

Air Interface Encryption KVL3000 Plus User Guide

This manual describes how to configure the KVL 3000 Plus for initial use, and entering and storing encryption keys in to target devices, such as radios and others in connection with Air Interface Encryption.

Dimetra KVL 4000 Air Interface Encryption and Authentication User Guide

This manual provides instructions for using the KVL 4000 Key Variable Loader to perform Air Interface Encryption and Authentication operations in Motorola Dimetra systems.

Dimetra KVL 4000 Authentication User Guide

This manual provides instructions for using the KVL 4000 Key Variable Loader to perform Authentication operations in Motorola Dimetra systems.

Dimetra KVL 4000 FLASHPort Upgrade User Guide

This manual provides instructions for upgrading/reinstalling the KVL application, upgrading the Security Adapter software, and applying security settings on the KVL.

Dimetra KVL 4000 AIEA/Auth Quick Start Guide

Provides basic information on KVL 4000 for Dimetra Air Interface Encryption and Authentication.

CryptR Instruction Manual

This manual covers hardware installation, main end-user operations and a proper maintenance of a range of devices based on the CryptR hardware platform.

MCC 7500-series Console Sites

This manual describes the hardware and software components associated with the MCC 7500-series console sites. It provides overviews of subsystem functions such as communications with the Zone Controller, different types of call setups, and descriptions of status and events.

A-12

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

68015000701-C - October 2013

Appendix A Dimetra IP System Documentation

Table A-1

(cont'd.)

Document Title

Description

MCC 7500C Dispatch Console

This manual describes the hardware and software components associated with the MCC 7500C Dispatch Console. It provides operation and troubleshooting procedures for the Elite Admin and Elite Dispatch software, and it provides an overview of MCC 7500C accessories.

MCC 7500 Archiving Interface Server

This manual provides an introduction to the hardware and software components associated with the MCC 7500 Archiving Interface Server. Included are detailed procedures for installation, configuration and operation of the server.

MCC 7500 Dispatch Communications Server

This manual describes the MCC 7500 Dispatch Communications Server. Included are detailed procedures for installation, configuration and operation of the server.

MCC 7500 Remote Dispatch Console

This manual provides a high level technical overview of the Remote Dispatch Console product and gives detailed procedures for its installation, configuration and maintenance.

MCC 7500 Discreet Listening

This manual describes Discreet Listening, which is a feature that enables real-time listening into one to one calls involving a specific radio user. Listening is possible for calls inside the Dimetra IP system or through telephone interconnect to an ordinary telephone. Using the Discreet Listening feature, a user is able to listen to calls involving the radio user without either of the calling parties knowing about it. The manual describes both the hardware and software used for the Discreet Listening feature, and contains procedures how to install, configure, and operate the feature.

MCC 7500 Analog Conventional Operation

This manual provides an introduction to the hardware and software components associated with the analog conventional feature of the MCC 7500 Dispatch Console.

MCC 7500-series Bandwidth Management

This manual provides an introduction to the bandwidth management, which is necessary in an MCC 7500-series console subsystem to ensure efficient transport for the services in your system (voice calls, data service and so on).

MCC 7500 Console Interoperability

This manual provides a technical overview and troubleshooting information for the interoperability feature. Console interoperability is the term for a radio system that supports call traffic involving both the CENTRACOM Gold Series and Motorola MCC 7500 dispatch consoles.

68015000701-C - October 2013

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

A-13

System Overview

Table A-1

(cont'd.)

Document Title

Description

MCC 7500C/MCC 7500S Elite Admin Software User Guide

This manual describes the Elite Admin software. The software creates a virtual desktop on the screen where resources that are part of the dispatch system are displayed graphically. Resources are grouped into folders, and one or more folders are stored as a configuration. The system administrator uses the Elite Admin software to set up configurations for the Elite Dispatch desktops that organize resources to meet specific user needs.

MCC 7500C/MCC 7500S Elite Dispatch Software User Guide

This manual describes the Elite Dispatch application which enables console dispatchers to communicate with radio resources.

MCC 7500 Emergency Beacon User Guide

This manual describes how to install, configure, operate, and test an emergency beacon installed on a console.

MCC 7500 Internationalization Process User Guide

This manual describes how to generate the translated text (appropriate to the target country or region) using the Internationalization Package. The translated text is generated for the following MCC 7500 products:

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

• Elite Dispatch, Elite Admin, Emergency Beacon, and Discreet Listening applications. • Elite Dispatch, Elite Admin, Emergency Beacon, and Discreet Listening online help files. Server Switchover

This manual describes redundancy types of server applications used in Dimetra IP system and contains instructions how to switch over server applications or entire physical servers.

Object Call

This manual provides a detailed description of the Object Call feature, as well as configuration procedures and troubleshooting information.

Barring of Incoming Calls/Barring of Outgoing Calls (BIC/BOC)

This manual provides detailed description of the Barring of Incoming Calls/Barring of Outgoing Calls (BIC/BOC) feature, as well as information on how to enable and initially configure the feature and troubleshoot problems.

Centralized Event Logging

This manual provides a detailed description of the Centralized Event Logging feature on Windows and Linux-based clients, as well as configuration procedures and troubleshooting information.

RF Sites MTS 1: Installation, Configuration, and Basic Service Manual

A-14

This manual describes all necessary actions to install, configure and maintain the Motorola Transceiver Station 1 (MTS 1) within the Dimetra IP System.

68015000701-C - October 2013

Appendix A Dimetra IP System Documentation

Table A-1

(cont'd.)

Document Title

Description

MTS LiTE, MTS 2, and MTS 4: Installation, Configuration, and Basic Service Manual

This manual describes all necessary actions to install, configure and maintain the Motorola Transceiver Station LiTE, 2 and 4 (MTS LiTE, MTS 2 and MTS 4) within the Dimetra IP System.

MTS Man Machine Interface (MMI) Commands

This manual describes the Man-Machine Interface commands used to test and configure MTS sites.

EBTS: Installation, Configuration, and Basic Service

This manual describes all necessary actions to install, configure and maintain the Enhanced Base Transceiver Systems (EBTS) within the Dimetra IP System.

MBTS: Installation, Configuration, and Basic Service

This manual describes all necessary actions to install, configure and maintain the Mini Base Transceiver Systems (MBTS) within the Dimetra IP System.

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

Customer Specific Manuals Cluster Hot Standby (CHS) Tools

This manual describes installation, configuration, and usage of the Cluster Hot Standby (CHS) Tools. CHS Tools are used to synchronize active and fallback clusters configurations and detect any discrepancies between them.

Cluster Hot Standby (CHS) Tools Online Help

Online help for the CHS application.

Dimetra IP Compact/Scalable Dimetra IP Specific Manuals System Reference Guide

This manual offers an introduction to the Dimetra IP Compact/Scalable Dimetra IP system. The information covers the major components of the system and the interconnection of components in the Mobile Switching Office (MSO), as well as troubleshooting information.

Managing Radio Users, Radios, Talkgroup Quick Reference Guide

This manual describes the most common day to day tasks related to the management of radio users, radios, and talkgroups.

Managing the Infrastructure Quick Reference Guide

This manual describes the three most common applications to use when monitoring and doing basic troubleshooting of your system: Unified Event Manager (UEM), ZoneWatch and Radio Control Manager (RCM). The guide gives a quick overview of the most common day to day tasks and activities.

Network Configuration Tool (NCT) Express

This manual describes the Network Configuration Tool (NCT) Express, which allows you to deploy previously prepared configurations to network devices. It also allows for tasks such as: rebooting devices, uploading firmware, checking firmware version, configuration backup and restore, checking device connectivity.

68015000701-C - October 2013

A-15

System Overview

Table A-1

(cont'd.)

Document Title

Description

DIPC Upgrade – Sun Fire X4170/HP ProLiant DL360 G7

This manual contains information and procedures necessary to upgrade a DIPC system from 7.0 to 8.1 release on Sun Fire X4170 and HP ProLiant DL360 G7 server platforms.

DIPC Upgrade – Sun Netra 240

This manual contains information and procedures necessary to upgrade a DIPC system from 7.0 to 8.1 release on Sun Netra 240 server platform.

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

Online Help Application Launcher Online Help

This online help describes how to operate the Application Launcher software.

Unified Event Manager (UEM) Online Help

This online help describes how to operate the Unified Event Manager application. It also covers detailed information on all system alarms and events.

ZoneWatch Online Help

This online help describes how to operate the ZoneWatch application.

System and Zone Profile Online Help

This online help describes how to operate the System and Zone Profile applications.

User Configuration Manager (UCM) Online Help

This online help describes how to operate the User Configuration Manager application.

Zone Configuration Manager (ZCM) Online Help

This online help describes how to operate the Zone Configuration Manager application.

Software Download Online Help

This online help describes how to operate the Software Download application.

Affiliation Display Online Help

This online help describes how to operate the Affiliation Display application.

ATIA Log Viewer Online Help

This online help describes how to operate the ATIA Log Viewer application.

Radio Control Manager (RCM) Online Help

This online help describes how to operate the Radio Control Manager application.

Radio Control Manager (RCM) Reports Online Help

This online help describes how to operate the Radio Control Manager Reports application.

Dynamic Reports Online Help

This online help describes how to operate the Dynamic Reports application.

Historical Reports Online Help

This online help describes how to operate the Historical Reports application.

A-16

68015000701-C - October 2013

Appendix A Dimetra IP System Documentation

Table A-1

(cont'd.)

Document Title

Description

Authentication Centre Online Help

This online help describes how to operate the Authentication Centre application.

Key Management Facility (KMF) Online Help

This online help describes how to operate the Key Management Facility applications.

BTS Service Software (TESS) Online Help

This online help describes how to operate the BTS Service Software.

MCC 7500 Elite Dispatch Software Online Help

This online help describes how to operate the MCC 7500 Elite Dispatch software.

MCC 7500 Elite Admin Software Online Help

This online help describes how to operate MCC 7500 Elite Admin software.

MCC 7500 Emergency Beacon Online Help

This online help describes how to operate MCC 7500 Emergency Beacon software.

MCC 7500 Discreet Listening Online Help

This online help describes how to operate the MCC 7500 Discreet Listening software.

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

Backup and Restore Including FRU/FRE for Upgrading Customers Common Hardware and Software Restoration

The purpose of this manual is to provide users with the information necessary to successfully restore the common hardware platforms (for clients and servers) and their respective operating systems used in a Dimetra IP system.

Call Processing, NM and Data Subsystems Restoration - Generation 2 System

This manual provides users with the procedures and FRU/FRE information needed to restore and back up the Zone Controller (ZC), Network Management (NM) servers and Data servers in a Generation 2 Dimetra IP system.

Call Processing, NM and Data Subsystems Restoration - Generation 3 System

This manual provides users with the procedures and FRU/FRE information needed to restore and back up the Zone Controller (ZC), Network Management (NM) servers and Data servers in a Generation 3 Dimetra IP system.

Standalone Subsystems and Components Restoration - Generation 2 System

This manual provides users with the procedures and FRU/FRE information needed to restore and back up standalone servers and components (MTIG, MultiCADI, Alias Server, Domain Controller, AuC/PrC and CryptR2) in a Generation 2 Dimetra IP system.

Standalone Subsystems and Components Restoration - Generation 3 System

This manual provides users with the procedures and FRU/FRE information needed to restore and back up standalone servers and components (MTIG, MultiCADI, Alias Server, Domain Controller, AuC/PrC and CryptR2) in a Generation 3 Dimetra IP system.

68015000701-C - October 2013

A-17

System Overview

Table A-1

(cont'd.)

Document Title

Description

Backup/Restore Collector Application User Guide Generation 2 System

This manual describes the Backup/Restore Collector application, which provides a simple way of fetching backup files from a group of the Dimetra IP network elements via FTP. The network elements can be configured to run scheduled backups and store these backups on local disk – typically during the night when there is a smaller load of the system. The role of the Backup/Restore application is to collect these files and provide a centralized point of storage for them. The backup files are accessible by FTP for collection either manually or from a server running an automated procedure. The files can be restored from their centralized storage location back to the network elements. This version of the manual is applicable to Generation 2 systems.

Backup/Restore Collector Application User Guide Generation 3 System

This manual describes the Backup/Restore Collector application, which provides a simple way of fetching backup files from a group of the Dimetra IP network elements via FTP. The network elements can be configured to run scheduled backups and store these backups on local disk – typically during the night when there is a smaller load of the system. The role of the Backup/Restore application is to collect these files and provide a centralized point of storage for them. The backup files are accessible by FTP for collection either manually or from a server running an automated procedure. The files can be restored from their centralized storage location back to the network elements. This version of the manual is applicable to Generation 3 systems.

A-18

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

68015000701-C - October 2013

Related Information Document Title

Description

Glossary

The glossary provides a list of abbreviations, acronyms and terms used in the Dimetra IP system documentation.

Documentation Overview

The document provides a list of all documents delivered with your Dimetra IP system. Its primary purpose is to help you to find the information you are looking for.

System Overview

This manual provides basic radio system concepts, call processing basics, and an introduction to the various components and processes associated with the Dimetra IP system. The manual provides the background needed to comprehend the theory of operation and it provides equipment/subsystem functional descriptions. It also describes the role of the numerous network management software applications used for managing the system.

Standards and Guidelines for Communication Sites

This manual provides standards and guidelines to follow when setting up a Motorola communications site. Also known as R56 manual.

Zone Controller

This manual describes the Zone Controller which is responsible for processing calls, managing audio paths, controlling zone infrastructure, and providing services to subscribers and console operators.

System LAN Switches

This manual describes LAN switches used in the Dimetra IP system. Included are detailed procedures for installation, configuration and operation.

S6000 Router

This manual describes the S6000 router used in the Dimetra IP system. The router provides the following network transport functions for the whole system:

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

• Router used in E1 configurations, including gateway, core, and exit routers • Router used in Ethernet configurations, including discreet and combined routers GGM 8000 Gateway

68015000701-C - October 2013

This manual describes the GGM 8000 Gateway and how it is used in the Dimetra IP system. Included are detailed procedures for installation, configuration and maintenance.

I

Related Information

(cont'd.)

Document Title

Description

Cooperative WAN Routing

This manual describes the Cooperative WAN Routing (CWR) solution that allows core and exit routers to interface directly with site and interzone links through a simple, reliable, and passive relay panel. The core and exit routers are configured in pairs to provide path redundancy for audio and control packets. With CWR, the routers work to control an external relay panel to switch a group of 12 non-redundant E1 links between the two routers in a pair.

Ethernet Site Links

This manual contains information on the Ethernet Site Links (ESL) feature, which provides a means to establish Ethernet connections of the following type:

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

• Base station links (single and redundant) • Inter-zone links • Remote control site links terminated at non-redundant control site routers

II

Link Encryption

This manual describes the technical solution for setting up Encryption and Authentication, which is an extension to the Ethernet Site Links (ESL) feature, on Routers and Base Stations.

Network Management Servers

This manual describes the Network Management (NM) Servers used in the Dimetra IP system. Included are detailed procedures for installation, configuration and maintenance. The NM servers are comprised of User Configuration Server (UCS), System Statistics Server (SSS), Zone Database Server (ZDS), Air Traffic Router Server (ATR), Zone Statistics Server (ZSS) and Unified Event Manager (UEM) Server.

Network Management Client

This manual provides an introduction to the hardware and software components associated with the Network Management (NM) Client. Included are detailed procedures for installation and configuration of the client.

Remote Access

This manual describes the Terminal Server which is used for local and remote serviceability, also referred to as out-of-band management. The manual provides an introduction to the hardware and software components associated with the Terminal Server. Included are detailed procedures for installation, configuration and troubleshooting the Terminal Server.

68015000701-C - October 2013

Related Information

(cont'd.)

Document Title

Description

Network Time Server

This manual describes the Network Time Server (NTS), which provides a UTC time and date reference to all IP connected system elements (NTP clients) that support the Network Time Protocol (NTP). The manual contains all information necessary to install, configure and use the server in the system.

Backup and Restore Including FRU/FRE

This volume contains the system backup and restoration procedures and their impact on the services as well as pre and post-restoration checks. The volume also describes how to perform FRU/FRE procedures.

Safety Guidelines for Installation of Hardware and Software

This manual describes the general safety guidelines to be followed in connection with installation of hardware and software. It is a part of Backup and Restore Including FRU/FRE.

Server Software Restoration

This manual describes how to perform restoration of all application servers. Additionally it contains instructions for scheduling or creating a backup on-demand. It is a part of Backup and Restore Including FRU/FRE.

Server Hardware Restoration

This manual describes how to perform restoration of all system servers hosting application servers. The manual also describes how to perform FRU/FRE procedures for these servers. It is a part of Backup and Restore Including FRU/FRE.

Stand-alone Components Restoration

This manual describes how to backup and restore the following components of a new Dimetra IP system:

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

• Network Management (NM) Client • Standalone Provisioning Centre (PrC) Client • Key Management Facility (KMF) • Echo Canceller • CryptR2 It is a part of Backup and Restore Including FRU/FRE. Network Transport Restoration

This manual describes how to backup and restore the system LAN switches, routers, gateways, CWR Patch Panel, Terminal Server, and Network Time Server. It is a part of Backup and Restore Including FRU/FRE.

Console Sites Restoration

This manual describes how to backup and restore all components of the MCC 7500 subsystem, both its clear and secure versions. The manual also describes how to perform FRU/FRE procedures. It is a part of Backup and Restore Including FRU/FRE.

68015000701-C - October 2013

III

Related Information

(cont'd.)

Document Title

Description

MTS 1 Restoration

This manual describes how to backup and restore the Motorola Transceiver System (MTS) 1. The manual also describes how to perform FRU/FRE procedures. It is a part of Backup and Restore Including FRU/FRE.

MTS LiTE, MTS 2 and MTS 4 Restoration

This manual describes how to backup and restore the Motorola Transceiver System (MTS) LiTE, 2 and 4. The manual also describes how to perform FRU/FRE procedures. It is a part of Backup and Restore Including FRU/FRE.

EBTS Restoration

This manual describes how to backup and restore the Enhanced Base Transceiver System (EBTS). The manual also describes how to perform FRU/FRE procedures. It is a part of Backup and Restore Including FRU/FRE.

Fault Management

This manual provides an overview of Fault Management features and contains troubleshooting procedures.

Unified Event Manager

This manual provides an introduction to the Unified Event Manager (UEM). Included sections are a comprehensive introduction, tools used for troubleshooting, and system-level troubleshooting. UEM is an application that provides reliable fault management services for the Dimetra IP system.

ZoneWatch

This manual describes ZoneWatch which is a Private Radio Network Management (PRNM) Suite application that lets you monitor radio call traffic for an individual zone in real time. ZoneWatch uses different watch windows that allow you to display only the information you need to see.

System and Zone Profile

This manual describes the System Profile application and the Zone Profile application which are both a Private Radio Network Management (PRNM) Suite application. The System Profile application displays how system-level applications are being used by the network management clients. For instance, you can view information for applications in the system including the total number of applications purchased, number of licenses in use, and who is currently using the application. The Zone Profile application displays detailed information about applications that are operating in the zone. You can use Zone Profile to view the zone-level application usage and view the zone-level application license usage.

IV

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

68015000701-C - October 2013

Related Information

(cont'd.)

Document Title

Description

System Alarms and Events

This manual lists all the possible alarms for the system. It also covers transient alarm messages, which are known as technician messages. This manual is intended for technicians, network management personnel, or any other engineering personnel with responsibility for troubleshooting or monitoring the operational status of the system.

User Configuration Manager

This manual describes the User Configuration Manager (UCM) which is a Windows based, Private Radio Network Management (PRNM) Suite application. The UCM is used in the configuration of the system. It is also the tool used to modify configuration parameters. To configure a system, both the UCM and the Zone Configuration Manager (ZCM) are needed.

Zone Configuration Manager

This manual describes the Zone Configuration Manager (ZCM) which is a Private Radio Network Management (PRMN) Suite application. The ZCM is used to configure and maintain operational parameters for equipment in a system. To configure a system, both the ZCM and the User Configuration Manager (UCM) are needed.

Configuring Features

This manual describes radio features and their configuration. The manual contains a configuration checklist as well as configuration procedures for the key features of the system.

Software Download

This manual describes the Software Download (SWDL) Manager which is a Private Radio Network Management (PRNM) Suite application that can transfer and install new software in the Dimetra IP Base Transceiver Systems (BTS).

Radio Management

This manual describes the radio features available to radios in the Dimetra IP system.

Affiliation Display

This manual describes Affiliation Display which is a Private Radio Network Management (PRNM) suite application. Affiliation Display enables you to view the association of a radio with a talkgroup and site, information about conventional channels, console sites, and consoles and to monitor how radio users travel between different sites in a zone and how they communicate with other members of their assigned talkgroup or even with members outside of their talkgroup.

68015000701-C - October 2013

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

V

Related Information

(cont'd.)

Document Title

Description

ATIA Log Viewer

This manual describes the Air Traffic Information Access (ATIA) Log Viewer which is a Private Radio Network Management (PRNM) Suite application that displays log files generated by the Air Traffic Router (ATR). These log files contain records of all recent zone activity, such as site registrations and calls processed. ATIA Log Viewer allows you to view the raw ATIA data straight from the ATIA log.

Radio Control Manager

This manual describes the Radio Control Manager (RCM) which is a Private Radio Network Management (PRNM) Suite application used primarily by dispatchers to monitor and manage radio events, issue and monitor commands, and make informational queries of the system database.

Radio Control Manager Reports

This manual describes the Radio Control Manager (RCM) Reports which is a Private Radio Network Management (PRNM) Suite application that is used to create, view, print, schedule and export standard reports from RCM. These reports use a common format so the data can be used in spreadsheets. The report information reflects the actual RCM server database information except the Emergency Alarms.

Fleetmapping

This manual describes how to properly plan for, set up, and manage your system. The Motorola engineering team works with your organization to plan, and set up your system. Accurate operational requirements are needed to ensure a successful system plan. By properly configuring the Dimetra IP system to meet your operational needs, your organization will have the most efficient and effective communications system available.

Performance Management

This manual provides an overview of Performance Management features. By monitoring the performance of the system, you can identify potential problems before they occur as well as adjust system resources to provide optimum performance.

Dynamic Reports

This manual describes Dynamic Reports which is a Private Radio Network Management (PRNM) Suite application that provides predefined report templates you can use to display statistics for a zone, site or a console site (but not for a system) in near real time.

VI

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

68015000701-C - October 2013

Related Information

(cont'd.)

Document Title

Description

Historical Reports

This manual describes Historical Reports which is a Private Radio Network Management (PRNM) Suite application that allows you to generate reports for system-wide activity and for individual zones. These reports display data that is stored on the server. The Historical Reports application generates reports of statistical data that is gathered at specific, predefined time intervals. You can then create reports from this data to monitor and analyze information about zones, sites, channels, talkgroups, and users.

InfoVista

This manual describes InfoVista™ which is a customizable performance management application. InfoVista interfaces with, and gathers data from, multiple network devices supporting Simple Network Management Protocol (SNMP) including master site routers, Ethernet LAN switches, and WAN switches. The InfoVista client application is used to access server software and perform administrative tasks such as starting and stopping existing reports, adding an instance, or creating a new report.

Security Management

This manual provides a security overview for the Dimetra IP system. Attacks on communications networks could interrupt mission critical operations, compromise classified or restricted information, and contribute indirectly to loss of lives. The manual presents an overview of the security application users, describes the security groups and applications, and describes how to configure and optimize the applications for secure operation.

Agency Priority Matrix (APM)

This manual describes the Agency Priority Matrix which is a feature used for controlling which talkgroups or radio users can be assigned to each RF channel resource in the system. The manual describes how to configure, operate, maintain, and troubleshoot the Agency Priority Matrix.

Radio User Assignment/Radio User Identity (RUA/RUI)

This document describes the Radio User Assignment/Radio User Identity (RUA/RUI) feature. The purpose of this manual is to provide a user with a background knowledge on the feature as well as enable to install, configure and maintain the Alias Server. It also describes how to operate RUA/RUI from the Alias Provisioning Client.

68015000701-C - October 2013

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

VII

Related Information

(cont'd.)

Document Title

Description

Data Subsystem

This manual describes the Data Subsystem and its components. It provides information on how to install, configure, operate and maintain the equipment and software including the Packet Data Gateway (PDG), Short Data Router (SDR), and Gateway GPRS Support Node (GGSN) Router. The Data Subsystem performs registration services for packet data users, maintains user permissions and mobility information, and provides routing of traffic to the radio network and the Gateway GPRS Support Node (GGSN) Router.

MultiCADI

This manual describes the Computer Aided Dispatch Interface (CADI) which is an Application Programming Interface (API) that provides the capability for systems external to the Dimetra IP SwMI to obtain information about, and exert some control over, radios. The CADI API enables third parties to write software applications called CADI clients that can receive events from, and submit commands to, the Dimetra IP SwMI. Multi-Computer Aided Dispatch Interface (MultiCADI) is a server application and an API, which enables third parties to develop application programs that can utilize the facilities provided by the CADI in the Dimetra IP system. The MultiCADI API builds upon the CADI API, but provides additional capabilities.

Telephone Interconnect

This manual provides the information necessary to install, configure, operate, and maintain the components in a Telephone Interconnect subsystem. The Telephone Interconnect subsystem provides an interface between the Dimetra IP radio network and an external telephone network, allowing telephone interconnect calls to be made between Dimetra IP radios and external telephones.

Active Directory/Domain Name Services

This manual describes Active Directory (AD) which is the service that provides access to enterprise-wide data and improved integration with the rest of the radio system. The manual contains procedures for installation and configuration of software necessary to make Active Directory operational. It also contains procedures for adding users and groups, and for backup and restore of Active Directory.

TESS Software User Guide

This manual is an introduction and guide to the use of the Dimetra BTS (Base Transceiver System) Service Software. Through the Dimetra BTS Service Software trained service personnel and systems engineers can configure and program a BTS.

VIII

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

68015000701-C - October 2013

Related Information

(cont'd.)

Document Title

Description

Transport Network Device Manager (TNDM)

This manual describes the Transport Network Device Manager (TNDM), which allows you to deploy previously prepared configurations to network devices. It also allows for tasks such as: rebooting devices, uploading firmware, checking firmware version, configuration backup and restore, checking device connectivity.

Alphanumeric Text Service (ATS)

This manual describes the Alphanumeric Text Service (ATS) application, which enables text messages to be sent between Mobile Stations (MS), Dispatch Consoles and computers in the fixed network.

Backup/Restore Collector Application User Guide

This manual describes the Backup/Restore Collector application which provides a simple way of fetching backup files from a group of the Dimetra IP network elements via FTP. The network elements can be configured to run scheduled backups and store these backups on local disk – typically during the night when there is a smaller load of the system. The role of the Backup/Restore application is to collect these files and provide a centralized point of storage for them. The backup files are accessible by FTP for collection either manually or from a server running an automated procedure. The files can be restored from their centralized storage location back to the network elements.

UCS Synchronization Tool

This manual describes the User Configuration Server (UCS) Synchronization Tool, which provides automated intercluster configuration of some of the UCS objects that require to be registered in all clusters in a multicluster system.

Local Gateway Trunking

This manual describes the local gateway trunking functionality, its operational aspects, and its configuration.

Dimetra Enhanced Software Update User Guide

This manual describes the Dimetra Enhanced Software Update feature, which provides backup and restore functionality, and upgrade functionality.

68015000701-C - October 2013

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

IX

Related Information

(cont'd.)

Document Title Authentication and Encryption Overview

Description

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

This manual gives an overview of the authentication and air interface encryption features in the Dimetra IP system including: • Description of the authentication and air interface encryption features • Description of the different aspects of secure encryption key management • Procedures for configuring these features in your system

Authentication Overview

This manual gives an overview of the authentication features in the Dimetra IP system including: • Description of the authentication features • Description of the different aspects of secure encryption key management • Procedures for configuring these features in your system

Authentication Centre (AuC) User Manual

This manual contains the installation, configuration and operation procedures for the Authentication Centre (AuC). It contains reference information and detailed descriptions of the GUI.

Clear Authentication Centre (AuC) User Manual

This manual contains the installation, configuration and operation procedures for the Clear Authentication Centre (AuC). It contains reference information and detailed descriptions of the GUI.

Provisioning Centre (PrC) User Manual

This manual describes how to use the Provisioning Centre (PrC) application. The main functions of the Provisioning Centre are: • Providing secure (encrypted) storage of subscriber keys • Providing secure upload and download facilities for subscriber keys and key data • Displaying up-to-date information about the key status of the radios • Exporting K-Ref data to permanent storage media • Generating audit trail and radio information.

X

68015000701-C - October 2013

Related Information

(cont'd.)

Document Title

Description

Clear Provisioning Centre (CPrC) User Manual

This manual describes how to use the Clear Provisioning Centre (CPrC) application. The main functions of the Provisioning Centre are:

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

• Providing secure storage of subscriber keys • Providing secure upload and download facilities for subscriber keys and key data • Displaying up-to-date information about the key status of the radios • Exporting K-Ref data to permanent storage media • Generating audit trail and radio information. Secure Voice, Data and Key Management

This manual provides information on hardware, software and system operation, including procedures for installing the Key Management Facility (KMF) system and for using Over-The-Air-Key Management (OTAK) and Over-The-Ethernet-Key Management (OTEK) commands.

MCC 7500S Dispatch Console

This manual describes all necessary actions to configure and maintain the MCC 7500S console subsystem. The subsystem allows two-way console and radio - console transmissions to be encrypted and secure.

MCC 7500S ICCS Gateway

This manual describes installation, configuration, operation, maintenance and troubleshooting of the components in a secure Integrated Command and Control System (ICCS) gateway including the Pyramid PC and the multiplexer. The ICCS Gateway Subsystem is a type of MCC 7500 console site, designed to meet the demands of customers, who want to implement or already have implemented their own custom-developed Integrated Command and Control System, that is, a non-Motorola control room. This manual describes also the ICCS Gateway Discreet Listening feature on the Dimetra IP system.

CryptR and Audio Module for Replay

This manual describes installation, configuration, operation, maintenance and troubleshooting of Audio Module used for replay purposes and configuration of CryptR used for call logging. Together with the AIS and third party replay devices they are part of the End-to-End Encryption Call Logging Subsystem.

End-to-End Secure Packet Data and Short Data

This manual describes configuration and operation of the End-Two-End Encryption (E2EE) feature for short and packet data (SD, PD) on the Dimetra IP system.

68015000701-C - October 2013

XI

Related Information

(cont'd.)

Document Title

Description

Network Security

This manual describes all necessary actions to install, configure and maintain the network security feature within the Dimetra IP system. The intention of the manual is to enable the reader to deploy the best possible level of security, which will protect the system against viruses, unauthorized authentication or attacks of hackers. The network security feature provides virus protection, authentication, and firewall protection.

End-to-End Encryption KVL3000 Plus User Guide

This manual describes how to configure the KVL 3000 Plus for initial use, and entering and storing encryption keys in to target devices, such as radios, CryptRs and Mobile CryptRs.

Air Interface Encryption KVL3000 Plus User Guide

This manual describes how to configure the KVL 3000 Plus for initial use, and entering and storing encryption keys in to target devices, such as radios and others in connection with Air Interface Encryption.

Dimetra KVL 4000 Air Interface Encryption and Authentication User Guide

This manual provides instructions for using the KVL 4000 Key Variable Loader to perform Air Interface Encryption and Authentication operations in Motorola Dimetra systems.

Dimetra KVL 4000 Authentication User Guide

This manual provides instructions for using the KVL 4000 Key Variable Loader to perform Authentication operations in Motorola Dimetra systems.

Dimetra KVL 4000 FLASHPort Upgrade User Guide

This manual provides instructions for upgrading/reinstalling the KVL application, upgrading the Security Adapter software, and applying security settings on the KVL.

Dimetra KVL 4000 AIEA/Auth Quick Start Guide

Provides basic information on KVL 4000 for Dimetra Air Interface Encryption and Authentication.

CryptR Instruction Manual

This manual covers hardware installation, main end-user operations and a proper maintenance of a range of devices based on the CryptR hardware platform.

MCC 7500-series Console Sites

This manual describes the hardware and software components associated with the MCC 7500-series console sites. It provides overviews of subsystem functions such as communications with the Zone Controller, different types of call setups, and descriptions of status and events.

XII

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

68015000701-C - October 2013

Related Information

(cont'd.)

Document Title

Description

MCC 7500C Dispatch Console

This manual describes the hardware and software components associated with the MCC 7500C Dispatch Console. It provides operation and troubleshooting procedures for the Elite Admin and Elite Dispatch software, and it provides an overview of MCC 7500C accessories.

MCC 7500 Archiving Interface Server

This manual provides an introduction to the hardware and software components associated with the MCC 7500 Archiving Interface Server. Included are detailed procedures for installation, configuration and operation of the server.

MCC 7500 Dispatch Communications Server

This manual describes the MCC 7500 Dispatch Communications Server. Included are detailed procedures for installation, configuration and operation of the server.

MCC 7500 Remote Dispatch Console

This manual provides a high level technical overview of the Remote Dispatch Console product and gives detailed procedures for its installation, configuration and maintenance.

MCC 7500 Discreet Listening

This manual describes Discreet Listening, which is a feature that enables real-time listening into one to one calls involving a specific radio user. Listening is possible for calls inside the Dimetra IP system or through telephone interconnect to an ordinary telephone. Using the Discreet Listening feature, a user is able to listen to calls involving the radio user without either of the calling parties knowing about it. The manual describes both the hardware and software used for the Discreet Listening feature, and contains procedures how to install, configure, and operate the feature.

MCC 7500 Analog Conventional Operation

This manual provides an introduction to the hardware and software components associated with the analog conventional feature of the MCC 7500 Dispatch Console.

MCC 7500-series Bandwidth Management

This manual provides an introduction to the bandwidth management, which is necessary in an MCC 7500-series console subsystem to ensure efficient transport for the services in your system (voice calls, data service and so on).

MCC 7500 Console Interoperability

This manual provides a technical overview and troubleshooting information for the interoperability feature. Console interoperability is the term for a radio system that supports call traffic involving both the CENTRACOM Gold Series and Motorola MCC 7500 dispatch consoles.

68015000701-C - October 2013

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

XIII

Related Information

(cont'd.)

Document Title

Description

MCC 7500C/MCC 7500S Elite Admin Software User Guide

This manual describes the Elite Admin software. The software creates a virtual desktop on the screen where resources that are part of the dispatch system are displayed graphically. Resources are grouped into folders, and one or more folders are stored as a configuration. The system administrator uses the Elite Admin software to set up configurations for the Elite Dispatch desktops that organize resources to meet specific user needs.

MCC 7500C/MCC 7500S Elite Dispatch Software User Guide

This manual describes the Elite Dispatch application which enables console dispatchers to communicate with radio resources.

MCC 7500 Emergency Beacon User Guide

This manual describes how to install, configure, operate, and test an emergency beacon installed on a console.

MCC 7500 Internationalization Process User Guide

This manual describes how to generate the translated text (appropriate to the target country or region) using the Internationalization Package. The translated text is generated for the following MCC 7500 products:

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

• Elite Dispatch, Elite Admin, Emergency Beacon, and Discreet Listening applications. • Elite Dispatch, Elite Admin, Emergency Beacon, and Discreet Listening online help files. Server Switchover

This manual describes redundancy types of server applications used in Dimetra IP system and contains instructions how to switch over server applications or entire physical servers.

Object Call

This manual provides a detailed description of the Object Call feature, as well as configuration procedures and troubleshooting information.

Barring of Incoming Calls/Barring of Outgoing Calls (BIC/BOC)

This manual provides detailed description of the Barring of Incoming Calls/Barring of Outgoing Calls (BIC/BOC) feature, as well as information on how to enable and initially configure the feature and troubleshoot problems.

Centralized Event Logging

This manual provides a detailed description of the Centralized Event Logging feature on Windows and Linux-based clients, as well as configuration procedures and troubleshooting information.

RF Sites MTS 1: Installation, Configuration, and Basic Service Manual

XIV

This manual describes all necessary actions to install, configure and maintain the Motorola Transceiver Station 1 (MTS 1) within the Dimetra IP System.

68015000701-C - October 2013

Related Information

(cont'd.)

Document Title

Description

MTS LiTE, MTS 2, and MTS 4: Installation, Configuration, and Basic Service Manual

This manual describes all necessary actions to install, configure and maintain the Motorola Transceiver Station LiTE, 2 and 4 (MTS LiTE, MTS 2 and MTS 4) within the Dimetra IP System.

MTS Man Machine Interface (MMI) Commands

This manual describes the Man-Machine Interface commands used to test and configure MTS sites.

EBTS: Installation, Configuration, and Basic Service

This manual describes all necessary actions to install, configure and maintain the Enhanced Base Transceiver Systems (EBTS) within the Dimetra IP System.

MBTS: Installation, Configuration, and Basic Service

This manual describes all necessary actions to install, configure and maintain the Mini Base Transceiver Systems (MBTS) within the Dimetra IP System.

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

Customer Specific Manuals Cluster Hot Standby (CHS) Tools

This manual describes installation, configuration, and usage of the Cluster Hot Standby (CHS) Tools. CHS Tools are used to synchronize active and fallback clusters configurations and detect any discrepancies between them.

Cluster Hot Standby (CHS) Tools Online Help

Online help for the CHS application.

Dimetra IP Compact/Scalable Dimetra IP Specific Manuals System Reference Guide

This manual offers an introduction to the Dimetra IP Compact/Scalable Dimetra IP system. The information covers the major components of the system and the interconnection of components in the Mobile Switching Office (MSO), as well as troubleshooting information.

Managing Radio Users, Radios, Talkgroup Quick Reference Guide

This manual describes the most common day to day tasks related to the management of radio users, radios, and talkgroups.

Managing the Infrastructure Quick Reference Guide

This manual describes the three most common applications to use when monitoring and doing basic troubleshooting of your system: Unified Event Manager (UEM), ZoneWatch and Radio Control Manager (RCM). The guide gives a quick overview of the most common day to day tasks and activities.

Network Configuration Tool (NCT) Express

This manual describes the Network Configuration Tool (NCT) Express, which allows you to deploy previously prepared configurations to network devices. It also allows for tasks such as: rebooting devices, uploading firmware, checking firmware version, configuration backup and restore, checking device connectivity.

68015000701-C - October 2013

XV

Related Information

(cont'd.)

Document Title

Description

DIPC Upgrade – Sun Fire X4170/HP ProLiant DL360 G7

This manual contains information and procedures necessary to upgrade a DIPC system from 7.0 to 8.1 release on Sun Fire X4170 and HP ProLiant DL360 G7 server platforms.

DIPC Upgrade – Sun Netra 240

This manual contains information and procedures necessary to upgrade a DIPC system from 7.0 to 8.1 release on Sun Netra 240 server platform.

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

Online Help Application Launcher Online Help

This online help describes how to operate the Application Launcher software.

Unified Event Manager (UEM) Online Help

This online help describes how to operate the Unified Event Manager application. It also covers detailed information on all system alarms and events.

ZoneWatch Online Help

This online help describes how to operate the ZoneWatch application.

System and Zone Profile Online Help

This online help describes how to operate the System and Zone Profile applications.

User Configuration Manager (UCM) Online Help

This online help describes how to operate the User Configuration Manager application.

Zone Configuration Manager (ZCM) Online Help

This online help describes how to operate the Zone Configuration Manager application.

Software Download Online Help

This online help describes how to operate the Software Download application.

Affiliation Display Online Help

This online help describes how to operate the Affiliation Display application.

ATIA Log Viewer Online Help

This online help describes how to operate the ATIA Log Viewer application.

Radio Control Manager (RCM) Online Help

This online help describes how to operate the Radio Control Manager application.

Radio Control Manager (RCM) Reports Online Help

This online help describes how to operate the Radio Control Manager Reports application.

Dynamic Reports Online Help

This online help describes how to operate the Dynamic Reports application.

Historical Reports Online Help

This online help describes how to operate the Historical Reports application.

XVI

68015000701-C - October 2013

Related Information

(cont'd.)

Document Title

Description

Authentication Centre Online Help

This online help describes how to operate the Authentication Centre application.

Key Management Facility (KMF) Online Help

This online help describes how to operate the Key Management Facility applications.

BTS Service Software (TESS) Online Help

This online help describes how to operate the BTS Service Software.

MCC 7500 Elite Dispatch Software Online Help

This online help describes how to operate the MCC 7500 Elite Dispatch software.

MCC 7500 Elite Admin Software Online Help

This online help describes how to operate MCC 7500 Elite Admin software.

MCC 7500 Emergency Beacon Online Help

This online help describes how to operate MCC 7500 Emergency Beacon software.

MCC 7500 Discreet Listening Online Help

This online help describes how to operate the MCC 7500 Discreet Listening software.

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

Backup and Restore Including FRU/FRE for Upgrading Customers Common Hardware and Software Restoration

The purpose of this manual is to provide users with the information necessary to successfully restore the common hardware platforms (for clients and servers) and their respective operating systems used in a Dimetra IP system.

Call Processing, NM and Data Subsystems Restoration - Generation 2 System

This manual provides users with the procedures and FRU/FRE information needed to restore and back up the Zone Controller (ZC), Network Management (NM) servers and Data servers in a Generation 2 Dimetra IP system.

Call Processing, NM and Data Subsystems Restoration - Generation 3 System

This manual provides users with the procedures and FRU/FRE information needed to restore and back up the Zone Controller (ZC), Network Management (NM) servers and Data servers in a Generation 3 Dimetra IP system.

Standalone Subsystems and Components Restoration - Generation 2 System

This manual provides users with the procedures and FRU/FRE information needed to restore and back up standalone servers and components (MTIG, MultiCADI, Alias Server, Domain Controller, AuC/PrC and CryptR2) in a Generation 2 Dimetra IP system.

Standalone Subsystems and Components Restoration - Generation 3 System

This manual provides users with the procedures and FRU/FRE information needed to restore and back up standalone servers and components (MTIG, MultiCADI, Alias Server, Domain Controller, AuC/PrC and CryptR2) in a Generation 3 Dimetra IP system.

68015000701-C - October 2013

XVII

Related Information

(cont'd.)

Document Title

Description

Backup/Restore Collector Application User Guide Generation 2 System

This manual describes the Backup/Restore Collector application, which provides a simple way of fetching backup files from a group of the Dimetra IP network elements via FTP. The network elements can be configured to run scheduled backups and store these backups on local disk – typically during the night when there is a smaller load of the system. The role of the Backup/Restore application is to collect these files and provide a centralized point of storage for them. The backup files are accessible by FTP for collection either manually or from a server running an automated procedure. The files can be restored from their centralized storage location back to the network elements. This version of the manual is applicable to Generation 2 systems.

Backup/Restore Collector Application User Guide Generation 3 System

This manual describes the Backup/Restore Collector application, which provides a simple way of fetching backup files from a group of the Dimetra IP network elements via FTP. The network elements can be configured to run scheduled backups and store these backups on local disk – typically during the night when there is a smaller load of the system. The role of the Backup/Restore application is to collect these files and provide a centralized point of storage for them. The backup files are accessible by FTP for collection either manually or from a server running an automated procedure. The files can be restored from their centralized storage location back to the network elements. This version of the manual is applicable to Generation 3 systems.

XVIII

Dimetra IP Scalable

Dimetra IP Compact/ Scalable Dimetra IP

68015000701-C - October 2013