System Release 8.0

DIMETRA™Dimetra IP Scalable (DIPS)

SYSTEM OVERVIEW

March 2012

*68015000452*B– 25400051086

© 2012 Motorola Solutions, Inc. All rights Reserved

Contents1 Radio System Concepts...............................................................................................................................1-1

1.1 What is a Radio System?....................................................................................................................1-11.1.1 Basic System Components ........................................................................................................1-1

1.1.1.1 Radio System Equipment ...................................................................................................1-21.1.1.2 Radio System Range..........................................................................................................1-2

1.1.2 Communication Types ..............................................................................................................1-31.1.2.1 Simplex ..........................................................................................................................1-31.1.2.2 Semi-Duplex....................................................................................................................1-31.1.2.3 Duplex............................................................................................................................1-4

1.1.3 Call Types ..............................................................................................................................1-41.1.3.1 Talkgroup Calls ................................................................................................................1-51.1.3.2 Multigroup Calls...............................................................................................................1-51.1.3.3 Announcement Calls .........................................................................................................1-51.1.3.4 Emergency Calls...............................................................................................................1-51.1.3.5 Ruthless Preemption..........................................................................................................1-51.1.3.6 Direct Mode Operation Calls...............................................................................................1-51.1.3.7 Site Wide Calls.................................................................................................................1-51.1.3.8 Private Calls ....................................................................................................................1-61.1.3.9 Individual Calls ................................................................................................................1-6

1.1.4 Basic Site Components .............................................................................................................1-61.1.4.1 Site Controller (SC)...........................................................................................................1-61.1.4.2 Base Stations (BTS) ..........................................................................................................1-61.1.4.3 Control Channel (CC) ........................................................................................................1-71.1.4.4 Traffic Channel (TCH) .......................................................................................................1-7

1.1.5 Radios ...................................................................................................................................1-81.1.6 Call Processing Basics..............................................................................................................1-8

1.1.6.1 Conventional and Trunked Radio Systems .............................................................................1-81.1.6.1.1 Conventional System Operation..................................................................................1-81.1.6.1.2 Trunked System Operation ........................................................................................1-9

1.1.6.2 Radio System Users ........................................................................................................ 1-101.1.6.2.1 Radio Users .......................................................................................................... 1-101.1.6.2.2 Talkgroups ........................................................................................................... 1-101.1.6.2.3 Multigroups .......................................................................................................... 1-11

1.1.7 Tracing a Basic Call ............................................................................................................... 1-111.2 Multiple Site Trunked Systems.......................................................................................................... 1-14

1.2.1 Major System Components...................................................................................................... 1-151.2.1.1 RF Sites ........................................................................................................................ 1-151.2.1.2 Mobile Switching Office (MSO) ........................................................................................ 1-16

1.2.2 Modes of Operation ............................................................................................................... 1-161.2.2.1 Wide Area Trunking with Interzone Trunking....................................................................... 1-171.2.2.2 Fall Back Modes............................................................................................................. 1-17

1.2.2.2.1 Zone Isolated Wide Area Trunking............................................................................ 1-171.2.2.2.2 Local Site Trunking................................................................................................ 1-171.2.2.2.3 Direct Mode Operation (DMO) ................................................................................ 1-18

1.3 Multizone Systems.......................................................................................................................... 1-181.3.1 Requirements for Multizone Communication .............................................................................. 1-18

1.3.1.1 Home Zone Mapping....................................................................................................... 1-191.3.1.2 Controlling Zone ............................................................................................................ 1-191.3.1.3 Participating Zone........................................................................................................... 1-20

1.3.2 Interzone Group Service Availability ......................................................................................... 1-201.3.3 Where Calls Occur................................................................................................................. 1-20

1.3.3.1 Single Site ..................................................................................................................... 1-201.3.3.2 Zone............................................................................................................................. 1-201.3.3.3 Multizones .................................................................................................................... 1-20

2 Dimetra IP System Technology.....................................................................................................................2-1

i

System Overview

2.1 Terrestrial Trunked Radio (TETRA) .....................................................................................................2-12.1.1 Spectrum Management .............................................................................................................2-22.1.2 Pi/4-DQPSK Modulation ..........................................................................................................2-32.1.3 ACELP Voice Compression.......................................................................................................2-42.1.4 Time Division Multiple Access ..................................................................................................2-5

2.1.4.1 TDMA for Dimetra IP Base Stations.....................................................................................2-52.1.4.2 TDMA for Dimetra IP Radios .............................................................................................2-5

2.2 Network Technology .........................................................................................................................2-52.2.1 Local Area Network.................................................................................................................2-6

2.2.1.1 Ethernet Technology..........................................................................................................2-62.2.1.2 Star Topology...................................................................................................................2-62.2.1.3 10Base-T and 100Base-T ...................................................................................................2-62.2.1.4 Virtual LANs ...................................................................................................................2-72.2.1.5 Switched Ethernet .............................................................................................................2-7

2.2.2 Wide Area Network .................................................................................................................2-72.2.2.1 E1 Carrier........................................................................................................................2-82.2.2.2 X.21 Link........................................................................................................................2-82.2.2.3 Frame Relay ....................................................................................................................2-9

2.2.3 Multi-LAN Sharing..................................................................................................................2-92.2.3.1 Multi-LAN Sharing ...........................................................................................................2-9

2.2.4 Cooperative WAN Routing (CWR) ............................................................................................2-92.2.4.1 Satellite Link Based WAN Connectivity .............................................................................. 2-11

2.2.5 Ethernet Site Links ................................................................................................................ 2-112.3 Digital Motorola Enhanced Trunked Radio (Dimetra) ............................................................................ 2-11

2.3.1 Dimetra IP System Components ............................................................................................... 2-112.3.2 Dimetra IP System Core ......................................................................................................... 2-122.3.3 Unicast Routing .................................................................................................................... 2-122.3.4 Multicast Routing .................................................................................................................. 2-132.3.5 Call Model ........................................................................................................................... 2-132.3.6 Traffic Planes........................................................................................................................ 2-15

2.3.6.1 Voice Control Plane......................................................................................................... 2-162.3.6.2 Audio Plane ................................................................................................................... 2-162.3.6.3 Data Plane ..................................................................................................................... 2-162.3.6.4 Network Management Plane ............................................................................................. 2-16

2.3.7 Cluster and Multicluster Architecture ........................................................................................ 2-172.4 End-to-End Secure Communication.................................................................................................... 2-172.5 System Summary............................................................................................................................ 2-18

3 Dimetra IP System Components ...................................................................................................................3-13.1 Mobile Switching Office (MSO) ..........................................................................................................3-1

3.1.1 System Server.........................................................................................................................3-13.1.1.1 Types of the System Server .................................................................................................3-2

3.1.2 Zone Controller.......................................................................................................................3-33.1.3 Network Management Subsystem ...............................................................................................3-3

3.1.3.1 Network Management Servers.............................................................................................3-53.1.3.2 Transport Network Performance Server.................................................................................3-63.1.3.3 Operations Support Systems................................................................................................3-6

3.1.3.3.1 Fault Management at the Zone Level ...........................................................................3-63.1.3.3.2 Configuration Management at the Zone Level ...............................................................3-63.1.3.3.3 Performance Management ........................................................................................3-63.1.3.3.4 Security Management at the Zone Level.......................................................................3-73.1.3.3.5 Network Management at the Cluster OSS.....................................................................3-73.1.3.3.6 Fault Management at the Cluster OSS..........................................................................3-73.1.3.3.7 Configuration Management at the Cluster OSS .............................................................3-73.1.3.3.8 Performance Management at the Cluster OSS................................................................3-73.1.3.3.9 Security Management at the Zone and Cluster OSS ........................................................3-83.1.3.3.10 Multicluster Network Management............................................................................3-83.1.3.3.11 Domain Controller..................................................................................................3-8

3.1.4 Data Subsystem.......................................................................................................................3-83.1.4.1 Data Gateway................................................................................................................. 3-10

ii

3.1.4.1.1 Packet Data Router (PDR) ....................................................................................... 3-103.1.4.1.2 Radio Network Gateway (RNG) ............................................................................... 3-103.1.4.1.3 Short Data Router (SDR)......................................................................................... 3-103.1.4.1.4 Gateway GPRS Support Node Routers (GGSN Routers) ............................................... 3-10

3.1.4.2 Data Resilience for Data Gateway ...................................................................................... 3-103.1.4.2.1 Redundant PDG and SDR ....................................................................................... 3-113.1.4.2.2 Redundant GGSN .................................................................................................. 3-113.1.4.2.3 Mobility Push Interface........................................................................................... 3-11

3.1.5 Telephone Interconnect Subsystem............................................................................................ 3-113.1.5.1 Motorola Telephone Interconnect Gateway .......................................................................... 3-133.1.5.2 Echo Canceller ............................................................................................................... 3-133.1.5.3 Enhanced Telephone Gateway (ETG) ................................................................................. 3-133.1.5.4 MTIG Firewall ............................................................................................................... 3-13

3.1.6 Provisioning and Authentication Centre ..................................................................................... 3-133.1.6.1 Provisioning Centre (PrC) ................................................................................................ 3-133.1.6.2 Clear Provisioning Centre (Clear PrC) ................................................................................ 3-143.1.6.3 Authentication Centre (AuC)............................................................................................. 3-14

3.1.7 MultiCADI Server ................................................................................................................. 3-143.1.8 Alias Server.......................................................................................................................... 3-153.1.9 Unified Network Services (UNS) Server .................................................................................... 3-153.1.10 Network Security Subsystem.................................................................................................. 3-16

3.1.10.1 Core Security Management Server.................................................................................... 3-183.1.10.1.1 Authentication Server and Replica Server ................................................................. 3-18

3.1.10.2 Customer Enterprise Network Interface Barrier ................................................................... 3-183.1.11 Network Time Server (NTS) .................................................................................................. 3-183.1.12 Terminal Server ................................................................................................................... 3-19

3.1.12.1 Remote Analog Access................................................................................................... 3-193.2 Network Transport Subsystem........................................................................................................... 3-19

3.2.1 Switches .............................................................................................................................. 3-223.2.1.1 Core LAN Switch ........................................................................................................... 3-223.2.1.2 Control Site LAN Switch.................................................................................................. 3-223.2.1.3 DMZ LAN Switch .......................................................................................................... 3-223.2.1.4 FAN-OUT LAN switch .................................................................................................... 3-223.2.1.5 Backhaul Switch............................................................................................................. 3-233.2.1.6 Aggregation Switch......................................................................................................... 3-23

3.2.2 Routers................................................................................................................................ 3-233.2.2.1 Gateway Router.............................................................................................................. 3-243.2.2.2 Core Router ................................................................................................................... 3-243.2.2.3 Exit Router .................................................................................................................... 3-243.2.2.4 Border Router ................................................................................................................ 3-243.2.2.5 Peripheral Network (PN) Router ........................................................................................ 3-253.2.2.6 The Combined Routers .................................................................................................... 3-253.2.2.7 Gateway GPRS Support Node ........................................................................................... 3-25

3.2.3 CWR Patch Panel .................................................................................................................. 3-253.3 Remote Sites.................................................................................................................................. 3-26

3.3.1 Base Transceiver Station (BTS)................................................................................................ 3-263.3.1.1 MTS LiTE..................................................................................................................... 3-273.3.1.2 MTS 1 .......................................................................................................................... 3-273.3.1.3 MTS 2 .......................................................................................................................... 3-283.3.1.4 MTS 4 .......................................................................................................................... 3-293.3.1.5 Redundant Base Station Site Link ...................................................................................... 3-303.3.1.6 Site Controller (SC)......................................................................................................... 3-303.3.1.7 Base Radio .................................................................................................................... 3-313.3.1.8 Breaker Panel................................................................................................................. 3-32

3.3.2 Control Sites......................................................................................................................... 3-323.3.2.1 Dispatch Subsystem ........................................................................................................ 3-32

3.3.2.1.1 Dispatch Console PC.............................................................................................. 3-333.3.2.1.2 Equipment connected to the Dispatch Console PC........................................................ 3-33

Desktop Speakers ........................................................................................................ 3-34

iii

System Overview

Desk Microphone ........................................................................................................ 3-34Footswitch ................................................................................................................. 3-34Emergency Beacon ...................................................................................................... 3-34

3.3.2.1.3 Logging System .................................................................................................... 3-34MCC 7500 Archiving Interface Server............................................................................. 3-35Logging Recorder........................................................................................................ 3-35Replay Station ............................................................................................................ 3-36

3.3.2.1.4 Conventional Channel Gateway (CCGW)................................................................... 3-363.3.2.1.5 MCC7500 Dispatch Communications Server .............................................................. 3-373.3.2.1.6 Secure Dispatch System (End-to-End Encryption (E2EE)) ............................................. 3-37

Secure ICCS Gateway .................................................................................................. 3-38End-2-End Encryption (E2EE) Call Logging..................................................................... 3-38

E2EE Call Logging Servers .................................................................................... 3-38E2EE Discreet Listening ICCS Gateway .......................................................................... 3-39

3.3.2.2 Types of Control Site ....................................................................................................... 3-393.3.2.2.1 Small Control Site.................................................................................................. 3-393.3.2.2.2 Large Control Site.................................................................................................. 3-40

3.4 Radios .......................................................................................................................................... 3-423.4.1 MTH800.............................................................................................................................. 3-423.4.2 MTP850 .............................................................................................................................. 3-433.4.3 MTP850 S............................................................................................................................ 3-443.4.4 MTP830 S............................................................................................................................ 3-453.4.5 MTP850Ex (ATEX) ............................................................................................................... 3-453.4.6 MTP810Ex (ATEX) ............................................................................................................... 3-463.4.7 CEP400 ............................................................................................................................... 3-473.4.8 TCR1000 ............................................................................................................................. 3-483.4.9 MTM800 Enhanced ............................................................................................................... 3-483.4.10 MTM5400.......................................................................................................................... 3-493.4.11 CM5000............................................................................................................................. 3-493.4.12 MTC100 PDA .................................................................................................................... 3-50

4 Dimetra IP Data Management ......................................................................................................................4-14.1 Radio System Databases ....................................................................................................................4-1

4.1.1 Call Processing Information.......................................................................................................4-14.1.1.1 User Configuration Server Database .....................................................................................4-14.1.1.2 Zone Database Server ........................................................................................................4-24.1.1.3 Home Location Register.....................................................................................................4-24.1.1.4 Visitor Location Register ....................................................................................................4-24.1.1.5 Zone Local Database .........................................................................................................4-24.1.1.6 Radio Control Manager (RCM) Database ..............................................................................4-24.1.1.7 Affiliation Database...........................................................................................................4-24.1.1.8 Radio User Information......................................................................................................4-2

4.1.2 Fault Management Information ..................................................................................................4-34.1.3 Statistical Data ........................................................................................................................4-3

4.1.3.1 System Statistics Server Database ........................................................................................4-34.1.3.2 Zone Statistics Server Database ...........................................................................................4-3

4.1.4 Database Summary ..................................................................................................................4-34.1.5 Hierarchical View....................................................................................................................4-44.1.6 Server Interaction ....................................................................................................................4-5

4.2 Server Failure Impacts .......................................................................................................................4-75 Dimetra IP Call Processing ..........................................................................................................................5-1

5.1 Configuration Information ..................................................................................................................5-15.1.1 Static User Configuration ..........................................................................................................5-2

5.1.1.1 Default Records................................................................................................................5-25.1.1.2 Identification Numbers.......................................................................................................5-3

5.1.1.2.1 Programming ID Numbers.........................................................................................5-35.1.1.3 Home Zones ....................................................................................................................5-35.1.1.4 Radio Identification ...........................................................................................................5-45.1.1.5 Radio User ......................................................................................................................5-5

5.1.1.5.1 Radio User to Radio Relationship ...............................................................................5-5

iv

5.1.1.6 Profiles ...........................................................................................................................5-55.1.1.6.1 Radio User Capabilities Profile...................................................................................5-55.1.1.6.2 Radio User Valid Sites Profile ....................................................................................5-65.1.1.6.3 Radio User Interconnect Profile ..................................................................................5-6

5.1.1.7 Templates ........................................................................................................................5-65.1.1.8 Configuration Updates .......................................................................................................5-65.1.1.9 Talkgroup........................................................................................................................5-6

5.1.1.9.1 TG/MG Capabilities Profile .......................................................................................5-65.1.1.10 Multigroup.....................................................................................................................5-7

5.1.1.10.1 TG/MG Valid Sites Profile .......................................................................................5-75.1.2 Infrastructure Configuration.......................................................................................................5-7

5.1.2.1 Source Site Adjacent Control Channel ..................................................................................5-75.2 Mobility Management .......................................................................................................................5-8

5.2.1 Mobility as viewed by the Radio.................................................................................................5-85.2.2 Mobility as viewed by the Fixed Network Equipment .....................................................................5-85.2.3 How the Location Registers are created .......................................................................................5-8

5.3 Call Processing .............................................................................................................................. 5-105.3.1 Controlling Zone ................................................................................................................... 5-105.3.2 Call Types ............................................................................................................................ 5-12

5.4 Group-Based Services ..................................................................................................................... 5-135.4.1 Talkgroup Call ...................................................................................................................... 5-13

5.4.1.1 Intrazone Talkgroup Call .................................................................................................. 5-135.4.1.1.1 Call Request ......................................................................................................... 5-135.4.1.1.2 Call Setup ............................................................................................................ 5-145.4.1.1.3 Call Grant ............................................................................................................ 5-145.4.1.1.4 Intrazone Talkgroup Call Audio Routing .................................................................... 5-155.4.1.1.5 Talkgroup Call Continuation and Teardown ................................................................ 5-15

5.4.1.2 Interzone Talkgroup Call .................................................................................................. 5-165.4.1.2.1 Interzone Talkgroup Call Request ............................................................................. 5-165.4.1.2.2 Interzone Talkgroup Call Setup ................................................................................ 5-175.4.1.2.3 Interzone Talkgroup Call Audio Routing .................................................................... 5-175.4.1.2.4 Interzone Talkgroup Call Continuation and Teardown................................................... 5-175.4.1.2.5 Roaming During a Talkgroup Call............................................................................. 5-18

5.4.2 Announcement Call ............................................................................................................... 5-185.4.2.1 Multi-Select (MSEL) and Patch Calls ................................................................................. 5-18

5.4.3 Emergency Services ............................................................................................................... 5-195.4.3.1 Emergency Alarm ........................................................................................................... 5-195.4.3.2 Emergency Call .............................................................................................................. 5-19

5.4.4 Site Wide Calls ..................................................................................................................... 5-205.4.5 Talkgroup Scanning ............................................................................................................... 5-20

5.5 Individual Call Services ................................................................................................................... 5-205.5.1 Private Call Request............................................................................................................... 5-21

5.5.1.1 Private Call Request Flow ................................................................................................ 5-215.5.1.2 Intrazone Private Call Audio Flow, Call Continuation, and Teardown........................................ 5-225.5.1.3 Roaming During a Private Call .......................................................................................... 5-225.5.1.4 Full-Duplex Private Calls ................................................................................................. 5-23

5.5.2 Telephone Interconnect ........................................................................................................... 5-235.5.2.1 Relationship between Components ..................................................................................... 5-245.5.2.2 Configuration ................................................................................................................. 5-24

5.5.2.2.1 Limiting Access to Interconnection Services ............................................................... 5-24Limiting Interconnect Calls Through Radio and User Configuration ...................................... 5-24

Individual Interconnect Profiles ............................................................................... 5-24Limiting Interconnect through Infrastructure Configuration ................................................. 5-24

Enabling or Disabling Interconnect Based on Shared Service ........................................ 5-24Limiting Interconnect Call Duration at the Zone Level ................................................. 5-25

5.5.2.2.2 Call Setup Restrictions............................................................................................ 5-255.5.2.2.3 Radio-to-Landline Interconnect Calls......................................................................... 5-25

Call Setup .................................................................................................................. 5-255.5.2.2.4 Landline-to-Radio Interconnect Calls......................................................................... 5-26

v

System Overview

5.5.2.3 Telephone Interconnect Call Continuation/Call Maintenance ................................................... 5-265.5.2.4 Telephone Interconnect Call Termination and Call Teardown................................................... 5-26

5.5.2.4.1 Radio-Initiated Termination During Active Interconnect Call ......................................... 5-265.5.2.4.2 Landline Initiated Termination During Active Interconnect Call...................................... 5-275.5.2.4.3 System Initiated Interconnect Call Termination............................................................ 5-27

5.5.2.5 Roaming During a Telephone Interconnect Call .................................................................... 5-275.5.2.5.1 Roaming During an Active Interconnect Call .............................................................. 5-275.5.2.5.2 Roaming during queuing of Telephone Interconnect Call ............................................... 5-275.5.2.5.3 Roaming While Ringing for Landline-to-Radio Call ..................................................... 5-27

5.6 Packet Data Services ....................................................................................................................... 5-275.6.1 Packet Data Service Initiation .................................................................................................. 5-285.6.2 Data Prioritization ................................................................................................................. 5-295.6.3 Multislot Packet Data ............................................................................................................. 5-295.6.4 Dynamic Data Channel ........................................................................................................... 5-305.6.5 End-to-End Encryption (E2EE) Packet Data ............................................................................... 5-30

5.7 Short Data Services ......................................................................................................................... 5-315.7.1 Short Data Store and Forward .................................................................................................. 5-315.7.2 End-to-End Encryption (E2EE) Short Data ................................................................................. 5-325.7.3 SDS in Local Site Trunking ..................................................................................................... 5-32

5.8 Authentication and Air Interface Encryption ........................................................................................ 5-325.8.1 Authentication ...................................................................................................................... 5-335.8.2 Air Interface Encryption ......................................................................................................... 5-33

5.8.2.1 Security Classes.............................................................................................................. 5-335.8.2.1.1 Security Class 1(SC1)............................................................................................. 5-345.8.2.1.2 Security Class 2 (SC2) ............................................................................................ 5-34

Encryption with the Static Cipher Key (SCK) ................................................................... 5-345.8.2.1.3 Security Class 3 (SC3) ............................................................................................ 5-34

Encryption with the Derived Cipher Key (DCK)................................................................ 5-34Encryption with the Common Cipher Key (CCK) .............................................................. 5-35

5.8.2.1.4 Security Class 3G (SC3G) ....................................................................................... 5-355.9 Busy Call Handling......................................................................................................................... 5-35

5.9.1 Priority Levels ...................................................................................................................... 5-355.9.2 Group Call Busies.................................................................................................................. 5-35

5.9.2.1 AllStart ......................................................................................................................... 5-365.9.2.2 FastStart........................................................................................................................ 5-36

5.9.3 Private Call Busies................................................................................................................. 5-365.9.4 Typical Reasons for Rejects ..................................................................................................... 5-37

5.10 Effects of Loss of Service on Call Processing ..................................................................................... 5-375.10.1 Loss of Service within a Zone ................................................................................................ 5-375.10.2 Conditions Necessary for Interzone Trunking ............................................................................ 5-38

5.10.2.1 Interzone Group Service Availability................................................................................. 5-385.10.2.1.1 Example 1 .......................................................................................................... 5-39

5.10.2.2 Interzone Individual Service Availability ........................................................................... 5-395.10.2.2.1 Conditions for Interzone Unit to Unit Calls ............................................................... 5-395.10.2.2.2 Example 1 .......................................................................................................... 5-405.10.2.2.3 Example 2 .......................................................................................................... 5-40

5.11 Interference Detection .................................................................................................................... 5-415.12 Zone Controller Switchover in Redundant Configuration ...................................................................... 5-42

5.12.1 Automatic Switchover .......................................................................................................... 5-425.12.2 User-Initiated Switchover ...................................................................................................... 5-425.12.3 System Behavior During Automatic Switchover ........................................................................ 5-43

5.12.3.1 Possible Call Processing Behavior During Recovery ............................................................ 5-445.12.3.1.1 Radio Scatter....................................................................................................... 5-44

5.12.3.2 Switching Back to the Standby Controller (User Initiated)..................................................... 5-455.12.3.2.1 Infrastructure Database Download........................................................................... 5-45

6 Dimetra IP System Features .........................................................................................................................6-16.1 Voice Services..................................................................................................................................6-1

6.1.1 Group Call .............................................................................................................................6-16.1.2 Announcement Call .................................................................................................................6-1

vi

6.1.3 Emergency Call.......................................................................................................................6-16.1.4 Individual Call (Semi-Duplex or Full-Duplex)...............................................................................6-26.1.5 Telephone Interconnect Call ......................................................................................................6-2

6.2 Data Services ...................................................................................................................................6-26.2.1 Status Transfer Service .............................................................................................................6-26.2.2 Emergency Alarm....................................................................................................................6-26.2.3 Short Data Transport Service .....................................................................................................6-36.2.4 Alphanumeric Text Service........................................................................................................6-36.2.5 Packet Data Service .................................................................................................................6-36.2.6 Data Resilience .......................................................................................................................6-46.2.7 Tetra Enhanced Data Services (TEDS).........................................................................................6-4

6.3 Supplementary Services .....................................................................................................................6-46.3.1 Busy Queuing and Call Back .....................................................................................................6-46.3.2 Queuing Priority......................................................................................................................6-46.3.3 Call Out.................................................................................................................................6-56.3.4 Recent User Priority.................................................................................................................6-56.3.5 Dynamic Site Assignment .........................................................................................................6-56.3.6 All Start/Fast Start ...................................................................................................................6-56.3.7 Critical Site Assignment ...........................................................................................................6-56.3.8 Talking Party Identification........................................................................................................6-66.3.9 Calling Line Identification Presentation .......................................................................................6-66.3.10 Dual Tone Multi-Frequency Overdial.........................................................................................6-66.3.11 Late Entry ............................................................................................................................6-66.3.12 Priority Monitor.....................................................................................................................6-66.3.13 Preemptive Priority Call ..........................................................................................................6-66.3.14 Preemptive Priority Call - Busy User Preemption .........................................................................6-76.3.15 Site Wide Call .......................................................................................................................6-76.3.16 Barring of Outgoing Calls (BOC)..............................................................................................6-76.3.17 Barring of Incoming Calls (BIC)...............................................................................................6-76.3.18 Requested Sites .....................................................................................................................6-76.3.19 RUA/RUI.............................................................................................................................6-76.3.20 Control Channel Immunity ......................................................................................................6-86.3.21 Control Room Head Number....................................................................................................6-86.3.22 Energy Economy Mode...........................................................................................................6-86.3.23 SDR Audit Logging ...............................................................................................................6-9

6.4 Call Logging features ........................................................................................................................6-96.4.1 Central Voice Logging..............................................................................................................6-96.4.2 Discreet Listening....................................................................................................................6-9

6.5 Redundancy of Critical Components................................................................................................... 6-106.6 Local Gateway Trunking .................................................................................................................. 6-116.7 Mobility Features............................................................................................................................ 6-11

6.7.1 Agency Priority Matrix ........................................................................................................... 6-116.7.2 Extended Range .................................................................................................................... 6-126.7.3 Subscriber Class .................................................................................................................... 6-126.7.4 Valid Sites............................................................................................................................ 6-126.7.5 Common Secondary Control Channel ........................................................................................ 6-126.7.6 eTETRA.............................................................................................................................. 6-12

6.8 Console Operator Features................................................................................................................ 6-126.8.1 Assignable Talkgroups............................................................................................................ 6-136.8.2 Assignable Speakers and Audio Summing.................................................................................. 6-136.8.3 Repeat Disable ...................................................................................................................... 6-136.8.4 Temporary Disable................................................................................................................. 6-136.8.5 Permanent Disable ................................................................................................................. 6-136.8.6 Trunking System Status .......................................................................................................... 6-136.8.7 Console Priority .................................................................................................................... 6-146.8.8 Status Message Display .......................................................................................................... 6-146.8.9 All Mute .............................................................................................................................. 6-146.8.10 Instant Transmit................................................................................................................... 6-146.8.11 Safety Switch ...................................................................................................................... 6-14

vii

System Overview

6.8.12 Intelligent Call Indicator........................................................................................................ 6-146.8.13 Supervisory Console User...................................................................................................... 6-156.8.14 Console Multi-Select ............................................................................................................ 6-156.8.15 All Points Bulletin Transmission............................................................................................. 6-156.8.16 Console Patch ..................................................................................................................... 6-156.8.17 Conventional Channel Patch .................................................................................................. 6-156.8.18 Console Acoustic Cross-Mute ................................................................................................ 6-156.8.19 Ambience Listening ............................................................................................................. 6-15

6.9 Console Management Features ......................................................................................................... 6-166.9.1 User Configuration Manager .................................................................................................... 6-166.9.2 Elite Admin Application ......................................................................................................... 6-16

6.10 Dimetra Enhanced Software Update ................................................................................................. 6-166.10.1 Upgrade Server ................................................................................................................... 6-166.10.2 Upgrade Console ................................................................................................................. 6-17

7 Dimetra IP Network Management .................................................................................................................7-17.1 System Management Objectives and Framework ....................................................................................7-17.2 Serviceability...................................................................................................................................7-2

7.2.1 Local Serviceability of the MSO.................................................................................................7-27.2.2 Remote Serviceability of the MSO..............................................................................................7-2

7.3 Network Management System ............................................................................................................7-37.3.1 Client/Server Networking..........................................................................................................7-3

7.3.1.1 Windows-Based Clients .....................................................................................................7-37.3.1.2 NM Client Applications .....................................................................................................7-3

7.3.1.2.1 Cluster-Level Applications ........................................................................................7-37.3.1.2.2 Zone-Level Applications ...........................................................................................7-4

7.3.1.3 Network Management System Servers ..................................................................................7-47.3.1.3.1 NM Zone-Level Servers (One Each Per Zone)...............................................................7-57.3.1.3.2 Cluster-Level Servers (One Each Per System) ...............................................................7-5

7.3.1.4 Zone-Level Servers ...........................................................................................................7-57.3.1.4.1 Air Traffic Router ....................................................................................................7-57.3.1.4.2 Zone Database Server ...............................................................................................7-57.3.1.4.3 Unified Event Manager Server....................................................................................7-57.3.1.4.4 Zone Statistics Server ...............................................................................................7-5

7.3.1.5 Cluster-Level Servers ........................................................................................................7-67.3.1.5.1 User Configuration Server .........................................................................................7-67.3.1.5.2 System Statistics Server ............................................................................................7-6

7.3.2 Core Services..........................................................................................................................7-67.4 FCAPS Model in the Dimetra IP System ...............................................................................................7-7

7.4.1 Fault Management ...................................................................................................................7-77.4.2 Configuration Management .......................................................................................................7-7

7.4.2.1 Configuration Management Applications ...............................................................................7-77.4.2.1.1 Cluster-Level Configuration: User Configuration Manager ..............................................7-77.4.2.1.2 Zone Level Configuration: Zone Configuration Manager.................................................7-8

7.4.3 Accounting Management ..........................................................................................................7-87.4.3.1 Air Traffic Information Access Data .....................................................................................7-87.4.3.2 Cluster-Level Air Traffic Information Access Packets ..............................................................7-87.4.3.3 Air Traffic Information Access Logger and Log Viewer............................................................7-87.4.3.4 Data Services Billing — Packet Data ....................................................................................7-87.4.3.5 Data Services Billing — Short Data......................................................................................7-8

7.4.4 Performance Management .........................................................................................................7-97.4.4.1 Zone Historical Reports Application .....................................................................................7-97.4.4.2 System Wide Historical Reports...........................................................................................7-97.4.4.3 Dynamic Reports ..............................................................................................................7-97.4.4.4 ZoneWatch ......................................................................................................................7-97.4.4.5 Affiliation Display .......................................................................................................... 7-10

7.4.5 Security Management............................................................................................................. 7-107.4.5.1 Temporary Disable .......................................................................................................... 7-107.4.5.2 Permanent Disable .......................................................................................................... 7-107.4.5.3 User Client Security ........................................................................................................ 7-10

viii

7.4.5.4 Security Partitioning........................................................................................................ 7-117.4.5.5 Authentication................................................................................................................ 7-117.4.5.6 Air Interface Encryption................................................................................................... 7-11

7.5 Multizone Fault Management............................................................................................................ 7-117.5.1 Multicluster Network Management ........................................................................................... 7-127.5.2 Multicluster Configuration Management .................................................................................... 7-13

7.5.2.1 User Configuration Server API .......................................................................................... 7-137.5.2.2 Infrastructure Reports ...................................................................................................... 7-15

7.5.3 Multicluster Performance Management...................................................................................... 7-167.5.4 Multicluster User Configuration Server Synchronization ............................................................... 7-167.5.5 Multicluster Authentication Centre Synchronization..................................................................... 7-17

7.6 Introduction to Network Management Applications............................................................................... 7-177.6.1 Network Management Applications Overview ............................................................................ 7-17

7.6.1.1 Motorola PRNM Suite Applications Overview ..................................................................... 7-177.6.1.2 Other Motorola Applications............................................................................................. 7-19

7.6.2 Private Radio Network Management Suite Applications................................................................ 7-197.6.2.1 Application Launcher ...................................................................................................... 7-207.6.2.2 Affiliation Display .......................................................................................................... 7-207.6.2.3 ATIA Log Viewer ........................................................................................................... 7-217.6.2.4 Custom Historical Reports ................................................................................................ 7-217.6.2.5 Dynamic Reports ............................................................................................................ 7-227.6.2.6 Unified Event Manager .................................................................................................... 7-227.6.2.7 Historical Reports ........................................................................................................... 7-237.6.2.8 Radio Control Manager .................................................................................................... 7-237.6.2.9 Radio Control Manager Reports......................................................................................... 7-237.6.2.10 Software Download Manager .......................................................................................... 7-247.6.2.11 System Profile .............................................................................................................. 7-247.6.2.12 User Configuration Manager............................................................................................ 7-247.6.2.13 Zone Configuration Manager ........................................................................................... 7-25

7.6.2.13.1 High-Level Objects in ZCM................................................................................... 7-257.6.2.14 Zone Profile ................................................................................................................. 7-267.6.2.15 ZoneWatch................................................................................................................... 7-26

7.6.3 Network Transport Management Applications ............................................................................ 7-277.6.3.1 InfoVista ....................................................................................................................... 7-277.6.3.2 Transport Network Configuration Tool (TNCT) .................................................................... 7-27

Appendix A Dimetra IP System Documentation ................................................................................................ A-1

ix

List of FiguresFigure 1-1 Basic Radio System ...................................................................................................................1-1Figure 1-2 Fixed Equipment.......................................................................................................................1-2Figure 1-3 Antenna Height and Coverage .....................................................................................................1-3Figure 1-4 Simplex Communication ............................................................................................................1-3Figure 1-5 Semi-Duplex Communication......................................................................................................1-4Figure 1-6 Radios to Base Station Relationship .............................................................................................1-7Figure 1-7 Conventional Radio System Example............................................................................................1-9Figure 1-8 Example: Trunked Radio System Channel Assignments ...................................................................1-9Figure 1-9 Basic Trunked Site .................................................................................................................. 1-10Figure 1-10 Example: Organization of Users in a Talkgroup ............................................................................ 1-11Figure 1-11 Example of Talkgroups in Multigroups........................................................................................ 1-11Figure 1-12 Trunked Call Initiation ............................................................................................................. 1-12Figure 1-13 Trunked Call Validation............................................................................................................ 1-13Figure 1-14 Trunked Call Completion.......................................................................................................... 1-14Figure 1-15 Multiple Site Trunked System.................................................................................................... 1-15Figure 1-16 RF Site.................................................................................................................................. 1-16Figure 1-17 Mobile Switching Office (MSO) ................................................................................................ 1-16Figure 1-18 Modes of Operation in a Dimetra System..................................................................................... 1-17Figure 1-19 Example: Multizone System...................................................................................................... 1-18Figure 1-20 Multizone System - Conditions for Interzone Trunking................................................................... 1-19Figure 2-1 TETRA defined Air Interface ......................................................................................................2-2Figure 2-2 European Frequency Spectrum - Overview ....................................................................................2-2Figure 2-3 European TETRA Radio Frequency Spectrum ................................................................................2-3Figure 2-4 Pi/4-DQPSK Modulation ............................................................................................................2-4Figure 2-5 ACELP Voice Compression ........................................................................................................2-4Figure 2-6 Time Division Multiple Access - Base Stations ...............................................................................2-5Figure 2-7 Time Division Multiple Access - Radio (Full-Duplex Operation)........................................................2-5Figure 2-8 E1 Carrier ................................................................................................................................2-8Figure 2-9 Cooperative WAN Routing - Example ......................................................................................... 2-10Figure 2-10 Ethernet Site Links - Example ................................................................................................... 2-11Figure 2-11 Unicast Routing ...................................................................................................................... 2-12Figure 2-12 Multicast Routing.................................................................................................................... 2-13Figure 2-13 Call Processing - Multicast Routing of Traffic............................................................................... 2-15Figure 2-14 Dimetra IP System Logical Traffic Planes .................................................................................... 2-16Figure 2-15 Clusters and Individual Zones.................................................................................................... 2-17Figure 2-16 Basic Secure Voice Operation .................................................................................................... 2-17Figure 2-17 Voice Transmission.................................................................................................................. 2-18Figure 3-1 HP DL360 G7 Server Front View .................................................................................................3-2Figure 3-2 Network Management Subsystem.................................................................................................3-4Figure 3-3 Data Subsystem ........................................................................................................................3-9Figure 3-4 Data Resilience ...................................................................................................................... 3-11Figure 3-5 Telephone Interconnect Subsystem ............................................................................................. 3-12Figure 3-6 Network Security Subsystem ..................................................................................................... 3-17Figure 3-7 Network Time Server ............................................................................................................... 3-19Figure 3-8 In-Reach® Server — LX-4048T Front Panel................................................................................. 3-19Figure 3-9 Transport Core with E1 Connections ........................................................................................... 3-20Figure 3-10 Transport Core with Ethernet Connections ................................................................................... 3-21Figure 3-11 Core LAN switch .................................................................................................................... 3-22Figure 3-12 Aggregation Switch Front View ................................................................................................. 3-23Figure 3-13 S6000 Router ......................................................................................................................... 3-23Figure 3-14 GGM 8000 Base Unit .............................................................................................................. 3-23Figure 3-15 CWR Patch Panel.................................................................................................................... 3-26Figure 3-16 MTS LiTE ............................................................................................................................ 3-27Figure 3-17 MTS 1 .................................................................................................................................. 3-28Figure 3-18 MTS 2 .................................................................................................................................. 3-29

xi

System Overview

Figure 3-19 MTS 4 .................................................................................................................................. 3-30Figure 3-20 Site Controller (SC) ................................................................................................................. 3-31Figure 3-21 BTS Base Radio...................................................................................................................... 3-32Figure 3-22 Dispatch Subsystem................................................................................................................. 3-33Figure 3-23 MCC 7500 Dispatch Console Subsystem ..................................................................................... 3-33Figure 3-24 MCC 7500 Emergency Beacon .................................................................................................. 3-34Figure 3-25 GGM 8000 used for CCGW ...................................................................................................... 3-36Figure 3-26 Patching with a Conventional System.......................................................................................... 3-36Figure 3-27 MCC 7500S Dispatch Console................................................................................................... 3-38Figure 3-28 E2EE Discreet Listening ICCS Gateway...................................................................................... 3-39Figure 3-29 Small Control Site ................................................................................................................... 3-40Figure 3-30 Large Control Site: Non Redundant ............................................................................................ 3-41Figure 3-31 Large Control Site: Redundant................................................................................................... 3-42Figure 3-32 MTH800 Radio....................................................................................................................... 3-43Figure 3-33 MTP850 Radio ....................................................................................................................... 3-44Figure 3-34 MTP850 S Radio .................................................................................................................... 3-44Figure 3-35 MTP 830 S Radio.................................................................................................................... 3-45Figure 3-36 MTP850Ex Radio ................................................................................................................... 3-46Figure 3-37 MTP810Ex Radio ................................................................................................................... 3-47Figure 3-38 CEP400 Radio ........................................................................................................................ 3-47Figure 3-39 TCR1000............................................................................................................................... 3-48Figure 3-40 MTM800 Enhanced Radio ........................................................................................................ 3-48Figure 3-41 MTM 5400 Radio.................................................................................................................... 3-49Figure 3-42 CM5000 ................................................................................................................................ 3-50Figure 3-43 MTC100 PDA ........................................................................................................................ 3-51Figure 4-1 Server Interactions Defined .........................................................................................................4-5Figure 5-1 UCM Home Zone Mapping Window.............................................................................................5-4Figure 5-2 Home Location Register .............................................................................................................5-9Figure 5-3 Home Location Register - Visitor Location Register....................................................................... 5-10Figure 5-4 Intrazone Talkgroup Request from a BTS Site............................................................................... 5-14Figure 5-5 Talkgroup Call Grant ............................................................................................................... 5-14Figure 5-6 Interzone Call Request ............................................................................................................. 5-16Figure 5-7 Private Call ............................................................................................................................ 5-21Figure 5-8 Telephone Interconnect in E1 networking..................................................................................... 5-23Figure 5-9 Packet Data Services................................................................................................................ 5-28Figure 5-10 Short Data Services ................................................................................................................. 5-31Figure 5-11 Authentication ........................................................................................................................ 5-33Figure 5-12 Encryption of Traffic................................................................................................................ 5-33Figure 5-13 Reduced Interzone Service Availability ....................................................................................... 5-39Figure 5-14 Interzone Individual Call with Radios in Their Home Zones ............................................................ 5-40Figure 5-15 Interzone Individual Call with Radios Not in Their Home Zones ...................................................... 5-41Figure 6-1 Zone with Geographical Redundancy .......................................................................................... 6-11Figure 7-1 Multizone Fault Management - Client Access to Each Zone ............................................................ 7-12Figure 7-2 Multizone Fault Management- Event Forwarding to a Customer-Supplied Fault Management

System .................................................................................................................................. 7-12Figure 7-3 Multicluster Network Management - Client Access to Each Cluster .................................................. 7-13Figure 7-4 Multicluster Configuration Management - Provisioning through the UCS API .................................... 7-14Figure 7-5 Infrastructure Reports Architecture ............................................................................................. 7-15Figure 7-6 Multicluster Performance Management - Client Access to Each Cluster ............................................. 7-16Figure 7-7 PRNM Applications From a System Perspective ........................................................................... 7-18

xii

List of TablesTable 2-1 TETRA System Capabilities...................................................................................................... 2-19Table 2-2 Dimetra IP System Capacity ..................................................................................................... 2-19Table 3-1 Types of System Server (constellations).........................................................................................3-2Table 4-1 Summary of Database Administration Functions .............................................................................4-4Table 4-2 Hierarchical Listing of Servers Hosting Databases ...........................................................................4-4Table 4-3 Server Interactions.....................................................................................................................4-5Table 4-4 Capacity Lost When Servers Fail..................................................................................................4-7Table 5-1 Short Subscriber Identity Ranges..................................................................................................5-4Table 5-2 Call Processing Equipment........................................................................................................ 5-11Table 5-3 Security Classes ...................................................................................................................... 5-34Table 5-4 Zone Call Service States ........................................................................................................... 5-38Table 5-5 Levels of Group Service Availability........................................................................................... 5-38Table 5-6 Call Processing Behavior During Recovery .................................................................................. 5-44Table 6-1 Console Priority Levels ............................................................................................................ 6-14Table 7-1 Air Interface Encryption - Security Features ................................................................................ 7-11Table 7-2 Motorola PRNM Suite Applications............................................................................................ 7-18Table 7-3 Other Motorola Applications .................................................................................................... 7-19Table 7-4 Object Classes in UCM ............................................................................................................ 7-25Table 7-5 High-Level Objects in ZCM...................................................................................................... 7-26Table A-1 List of Dimetra IP System Documentation .................................................................................... A-1

xiii

Document History

Edition Description Date68015000452-A Initial Version Nov. 2011

68015000452-B Introduction of the Unified Network Services (UNS) feature March 2012

xv

About System OverviewThis manual explains radio system concepts and describes the components and functionality of the Dimetra IPsystem.

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 anypre-knowledge of the Dimetra IP system or radio concepts in general.

xvii

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 radiosystems and Motorola trunked radio systems.

• 2 Dimetra IP System Technology, page 2-1discusses technology behind Dimetra IP system..

• 3 Dimetra IP System Components, page 3-1 discusses the hardware components associated with .

• 4 Dimetra IP Data Management, page 4-1 presents an overview of the databases, servers, and ZoneControllers found in the Dimetra IP system.

• 5 Dimetra IP Call Processing, page 5-1 presents an overview of call processing, which takes place at theMSO equipment in a Dimetra IP system.

• 6 Dimetra IP System Features, page 6-1 lists and explains the features and options available for the DimetraIP system.

• 7 Dimetra IP Network Management, page 7-1 presents an overview of the FCAPS model as described by theInternational Organization for Standardization (ISO). also discusses Private Network Management (PRNM),its software applications or tools used to manage the Dimetra IP system and Network Management SoftwareTools 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 systemdocumentation, including third-party documentation.

xix

Helpful Background Information

Course Name Course DescriptionDimetra IP System Training You this volume most helpful you have already attended the Dimetra IP

system training to learn the system operating principles.

xxi

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

xxiii

Icon ConventionsThe document set is designed to give the reader more visual cues. The following graphic icons are used throughoutthe 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, butmay 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 orpreconditions. Also, refer the reader elsewhere for additional information, remind the reader how tocomplete an action (when it is not part of the current procedure, for instance), or tell the reader whereinformation 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 Cautionor 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 avoidproblems, procedures that may or may not be necessary as determined by the reader’s systemconfiguration, and so on. Although no damage occurs if the reader does not heed the caution, somesteps may need repeating.

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

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

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

xxv

Style ConventionsThe following style conventions are used:

Convention DescriptionBold This typeface is used for names of, for instance, windows, buttons, and

labels when these names appear on the screen (example: the AlarmsBrowser window). When it is clear that we are referring to, for instance, abutton, the name is used alone (example: Click OK).

Monospacing font in bold This typeface is used for words to be typed in exactly as theyare shown in the text (example: In the Address field, typehttp://ucs01.ucs:9080/)

Monospacing font This typeface is used for messages, prompts, and other text displayed onthe computer screen (example: A new trap destination hasbeen added).

Monospacing font in boldItalic

This typeface is used with angle brackets for words to be substitutedby a specific member of the group that the words represent (example:<router number>).

In sequences to be typed in, the angle brackets are omittedto avoid confusion as to whether the angle brackets are to beincluded in the text to be typed.

Arial bold This typeface is used for keyboard keys (example: Press Y, and then pressEnter).

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

xxvii

1 Radio System ConceptsTopics Covered in this Chapter

• What is a Radio System?• Multiple Site Trunked Systems• Multizone Systems

Radio systems provide a convenient and timely method of communication for people engaged in various publicsafety-related, transportation, and service occupations. Radio systems differ in design based on the needs ofthe individual users. One radio system may support a towing company with a dispatcher and two tow truckscommunicating back and forth. Another radio system may support the needs of a public utility company with anetwork of antenna towers and control sites and field personnel scattered across a wide geographic area. The typeof radio system that you have depends on the needs of your individual organization. The following provides anintroduction to basic radio system concepts.

1.1 What is a Radio System?A radio uses electromagnetic waves to send information across the air. This is accomplished by producing anelectrical 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). Mostradio frequencies are in Megahertz (MHz), or millions of cycles per second.

1.1.1 Basic System ComponentsA basic radio system consists of equipment that transmits and receives radio signals that are used to transport sometype 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, whichradiates 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 processedback 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 figure for components of a basic radio.

Figure 1-1 Basic Radio System

�

��

� ��

Transmitter

Antennas

Receiver Loudspeaker

Microphone

- March 2012 1-1

System Overview

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 atransmitter (TX), receiver (RX), and antenna system.

Fixed equipment is located at a central site. A base station is used to transmit the signal generated through themicrophone to portable and mobile equipment located at some distance. The range of the base station depends on itspower, antenna system, terrain, and environmental conditions. The location of the base station control is knownas the Dispatch Centre.

Figure 1-2 Fixed Equipment

�

��

� ��

Base stations can have three types of control:

• Colocated Control - A Colocated Control base station is used when the position of the dispatcher is close tothe antenna site.

• Small Control - A Small Control base station is used when the dispatch position is up to 300 meters from thebase station. transmitter and receiver are located near the antenna site of the base station, the controls arehoused in a separate unit at the position of the dispatcher and connected to the base station a multi-core cable.

• Large Control - Large Control is used when the base station is located more than 300 meters from thedispatch position. Leased telephone lines or microwave links may be used to connect the base stationequipment with the control unit.

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

1.1.1.2 Radio System Range

The range of a radio system many different factors. One of the most critical coverage factors is antenna height andlocation, because the range of a radio system is limited to the horizon as seen by the radio antenna. In general, therange 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.

1-2 - March 2012

1.1.2 Communication Types

Figure 1-3 Antenna Height and Coverage

1.1.2 Communication TypesRadio systems use any of the three types of communication: simplex, semi-duplex, and full-duplex. Thecommunication type used depends on the number of users and the type of equipment available. The followingprovides a description of the three types of communication.

1.1.2.1 Simplex

The most basic type of radio communication is simplex. Simplex communication consists of radio units operatingon a single frequency. Because everyone transmits and receives on the same frequency, users cannot talk and listenat 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 usersare added to the system, the competition for the one available frequency can make it difficult to get a messageacross. In addition, great distances and natural obstacles such as high hills and tall buildings can interfere with thesingle frequency.

1.1.2.2 Semi-Duplex

Semi-duplex communication uses two frequencies: one to receive and one to transmit. A radio operating insemi-duplex mode can only transmit or receive at any time. Radios operating on the Dimetra IP system usesemi-duplex communication to communicate with the base stations during talkgroup and multigroup calls. Asemi-duplex individual call also the Dimetra IP system.

- March 2012 1-3

System Overview

Figure 1-5 Semi-Duplex Communication

RX 806.0125 MHzTX 851.0125 MHz

1.1.2.3 Duplex

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

1.1.3 Call TypesThe following describes the possible types of voice calls that can be made. The examples are divided betweentwo main types of call services:

• Group-based call services Group-based calls are services that provide for (one-to-many) communication.The following are examples of group-based calls:

– 1.1.3.1 Talkgroup Calls, page 1-5

– 1.1.3.2 Multigroup Calls, page 1-5

– 1.1.3.3 Announcement Calls, page 1-5

– 1.1.3.4 Emergency Calls, page 1-5

– 1.1.3.5 Ruthless Preemption, page 1-5

– 1.1.3.6 Direct Mode Operation Calls, page 1-5

– 1.1.3.7 Site Wide Calls, page 1-5

• Individual call services Individual calls are services that provide for to user communication. The followingare calls:

– 1.1.3.8 Private Calls, page 1-6

– 1.1.3.9 Individual Calls, page 1-6

The following provides a brief introduction to each of the call types.

1-4 - March 2012

1.1.3.1 Talkgroup Calls

1.1.3.1 Talkgroup Calls

Talkgroup calls are made from one radio (or dispatch console) to all other radios (or dispatch consoles) that areaffiliated with the talkgroup. Talkgroup calls in the Dimetra IP system are semi-duplex, meaning that a participant inthe 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 to allow any user in the talkgroup to presstheir 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 call except that the calling radio (or dispatch console) is transmitting to two ormore talkgroups.

1.1.3.3 Announcement Calls

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

1.1.3.4 Emergency Calls

An emergency call is a specialized, high-priority version of a talkgroup or announcement call. Emergency callsalways have the highest priority in the system. When an emergency call request is made during a when all trafficchannels are busy, the request takes priority over any other type of call request. The emergency call is transmitted tothe currently selected talkgroup or multigroup of the radio.

1.1.3.5 Ruthless Preemption

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

1.1.3.6 Direct Mode Operation Calls

Radios can select direct mode operation (DMO) to directly communicate with other radios without calling throughthe system infrastructure. DMO calls are the back-to-back or talkaround operation used in analog radio systems. Inthe Dimetra IP system, DMO supports group calls and emergency group calls with preemption. DMO does notcurrently support encryption, individual calls, or data services.

Direct mode operation requires that radios are the appropriate range for the call to be successful. Before the radiotransmits in DMO, it first checks whether the channel is available. Once the push to talk (PTT) is released, anothermember of the group is free to respond. Whenever a radio is making a DMO call, the radio user ID is displayedon the radios that are receiving the call.

DMO supports group calls, preemptive private calls. Some mobile and portable radios also support to endencryption in DMO.

The radios can also communicate with a third-party DMO Gateway (supplied by the customer). Specifictalkgroups can be configured to communicate with the DMO Gateway. The supported DMO Gateway uses 10MHz transmit/receive offset frequencies.

1.1.3.7 Site Wide Calls

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

- March 2012 1-5

System Overview

1.1.3.8 Private Calls

Private calls allow properly equipped radios in the same system to enter into one-to-one conversations. senderenters 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 throughthe keypad. The Dimetra IP system supports both full-duplex and semi-duplex private calls.

1.1.3.9 Individual Calls

Telephone interconnect calls allow full-duplex communication between a radio and the public switched telephonenetwork (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 Subsystem.

1.1.4 Basic Site ComponentsThe following describes the basic site components, including the Site Controller and base stations.

1.1.4.1 Site Controller (SC)

A Site Controller processes inbound and outbound signaling traffic, assigns base stations for traffic channel access,and generally monitors and maintains order at the site. The Site Controller maintains a database that the Unit IDof 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 tospecific channels

• Generates the data which is superimposed on all voice communications and is used to unmute the audiocircuitry in receivers authorized to monitor audio transactions

1.1.4.2 Base Stations (BTS)

A Base Station serves as the Radio Frequency (RF) interface between the system infrastructure and the radios. BaseStations 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

1-6 - March 2012

1.1.4.3 Control Channel (CC)

Antenna systems for base stations are located on top of high structures such as buildings, hills, or towers. Thebase stations are normally located close to their antennas minimize the losses inherent in the cables connectingthe stations to the antennas. See Figure 1-6 Radios to Base Station Relationship for the relationship between theradios 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 TrafficChannel (TCH), which are mentioned below.

1.1.4.3 Control Channel (CC)

The controller needs to be able to communicate with all radios in the system to receive call requests and send channelassignments to the radios in the field. This is the role of the control channel (CC). Each system has at least one of itschannels 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 operationof the radios. The radios are in communication with the control channels as long as they are not involved ina voice call.

A radio uses a control channel to send in call requests or to receive call assignments. A radio always tunes to thecontrol channel except when it is assigned to a call on a traffic channel. When a call is completed, the radiosinvolved 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 requestis sent over a control channel to the controller. The controller assigns a channel to the group and sends out anassignment message over a control channel telling all radios that have that particular group selected to switch to aspecific traffic channel.

All active radios in that group automatically switch to the assigned traffic channel. When the radio user initiating thecall begins speaking, the transmission is received by the base station and transmitted back out. radios in the groupreceive the radio signal, processes the signal to separate the audio from the RF and send the audio signal to thelocal loudspeaker so the users can hear the message.

Radios in the system send a signal to the controller, through the control channel, indicating their unique identificationand talkgroup selection. This signal is sent whenever a radio is powered up or the radio user changes the position ofthe talkgroup selector. This process is known as affiliation.

1.1.4.4 Traffic Channel (TCH)

When one of the members of a group requests traffic channel services, the group is assigned its own traffic channelfor the duration of the call. A group that is assigned to a particular traffic channel cannot be heard by members of atalkgroup assigned to another traffic channel.

- March 2012 1-7

System Overview

In a trunked system, the traffic channels can be operated in one of three modes: Transmission Trunking, MessageTrunking or Message Trunking with PTT ID.

• Transmission TrunkingThe controller reclaims the traffic channel immediately after detecting a disconnectsignal from the transmitting unit. The receiving radios immediately returns to the control channel. The entirerequest and assignment procedure is repeated for each PTT from the originator or a radio responding tothe original call.

• Message TrunkingThis allows a group to retain the assigned traffic channel when the transmitting unitreleases the PTT. When a message trunked call is in progress, other radio users within the same group areallowed to key without returning to the control channel for a traffic channel assignment.

• Message Trunking with PTT IDThis is message trunking with the additional requirement that a radioreturn to the control channel to send its individual ID anytime the PTT button is pressed. This mode ofoperation provides positive identification of the transmitting radio and must be programmed in both theradio and the system.

1.1.5 RadiosRadios are classified as mobile (vehicle-mounted) or portable (carried by a person, usually handheld) radios whichprovide 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 logiccircuitry necessary to perform the following trunking functions:

• Generate and transmit requests for service in the form of data words that are then used to modulatethe 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.6 Call Processing BasicsCall processing is the sequence of events that the system goes through to handle a call request. The followingprovides an introduction to the basics of call processing in a trunked system. The discussion includes a descriptionof the hardware components that are used in call processing, the types of calls available, and the flow a call takes asit makes its way through the system as well as an overview of the radio users and groups that the system supports.

1.1.6.1 Conventional and Trunked Radio Systems

There are two types of radio systems:

• Conventional

• Trunked

1.1.6.1.1 Conventional System Operation

In conventional radio systems users share a common RF channel and compete for air time. In addition, users notonly 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 onegroup has a lot of radio activity while another has only light usage, several people may be waiting to use theirassigned channel, while the other channel sits idle. For example, channel 1 is providing services to group A; channel2 is providing services to group B and thus cannot accept requests from group C; channel 3 is idle but cannotautomatically provide services to group C. See figure below.

1-8 - March 2012

1.1.6.1.2 Trunked System Operation

Figure 1-7 Conventional Radio System Example

A A B C D D

Channel 1 Channel 2 Channel 3

1.1.6.1.2 Trunked System Operation

In trunked radio systems the users are not assigned to a fixed channel. Channels are common resources that areaccessible to all users on an as-needed and as-available basis. When a radio user initiates a call, the system assignsan available channel to that call, eliminating the condition where one channel is busy while another channel isinactive. When the call is finished, the channel is released and made available for other users. See figure below foran example of channel assignments in a trunked radio system.

Figure 1-8 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. Mostradio users need access to a channel several times a day, but their total time on the system may not exceed fiveminutes each. Temporary channel assignment helps ensure that a channel is available when a conversation needs totake place.

Trunking reduces the number of busies and improves the efficiency of the system resources. A call is busied if it hasbeen placed in a queue due to no channel being available.

- March 2012 1-9

System Overview

Figure 1-9 Basic Trunked Site

Controller

Channel 1 Channel 2 Channel 3 Channel 4

CC TCH TCH TCH

1.1.6.2 Radio System Users

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

1.1.6.2.1 Radio Users

Personnel using the trunked system are assigned a radio that is active in the system. A radio record in the centralcontroller is used to control the system features that the radio user is permitted to access.

1.1.6.2.2 Talkgroups

A talkgroup is the basic unit of communication in a trunked system. In most organizations, radio users work ingroups that are based on their functions and responsibilities. In a trunked radio system, these groups of radio userscan be assigned to communication talkgroups that reflect their function or responsibilities. The figure below is anexample of a talkgroup.

Programming of talkgroups in a radio is based on the communication needs of radio users. A radio can beprogrammed with only one or with several talkgroups. Radio users selecting a particular talkgroup on their radioare assigned a traffic channel when someone in the group requests talkgroup call services. Group privacy duringconversations 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.

1-10 - March 2012

1.1.6.2.3 Multigroups

Figure 1-10 Example: Organization of Users in a Talkgroup

Talkgroup 1 Talkgroup 2 Talkgroup 3

1.1.6.2.3 Multigroups

Several talkgroups can be combined to form a multigroup (also called an announcement group). Multigroups areassigned an ID from the same pool of numbers as the talkgroups. In this example, calls placed to Multigroup Awould be heard by the radio users in Talkgroups 2 and 3.

Figure 1-11 Example of Talkgroups in Multigroups

Talkgroup 1

Talkgroup 2

Multigroup A

Talkgroup 3

1.1.7 Tracing a Basic Call

Process Steps

- March 2012 1-11

System Overview

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

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

Figure 1-12 Trunked Call Initiation

Talkgroup BTalkgroup A

1 2 3

TETRA Carrier

CT

TT

1-12 - March 2012

1.1.7 Tracing a Basic Call

2 The system validates the call request, assigns a traffic channel and signals a traffic channel grant to all radiosof 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

Talkgroup BTalkgroup A

1 2 3

TETRA Carrier

CT

TT

- March 2012 1-13

System Overview

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

Figure 1-14 Trunked Call Completion

Talkgroup BTalkgroup A

1 2 3

TETRA Carrier

CT

TT

1.2 Multiple Site Trunked SystemsMultiple site trunked systems increase the size of the coverage area and provide radio communication in placesthat 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 controland audio distribution. The central controller at each site supervises the equipment and radios at its location whilethe centralized control coordinates and oversees the operation of the individual sites. This coordination requires theuse 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 theirgroup. In addition, members of a group can be dispersed throughout the various sites in the system and still be ableto communicate with each other. The following describes how this can be accomplished.

1-14 - March 2012

1.2.1 Major System Components

Figure 1-15 Multiple Site Trunked System

Site Controller

RF Site

Site Controller

RF Site

Site Controller

RF Site

Site Con

Mobile SwitchingOffice

troller

ontroller Site Con

witchingce

Mobile SwiOffice

1.2.1 Major System ComponentsThe following describes the components or subsystems that may be found in a multiple site system.

1.2.1.1 RF Sites

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

- March 2012 1-15

System Overview

Figure 1-16 RF Site

Site

1.2.1.2 Mobile Switching Office (MSO)

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

Figure 1-17 Mobile Switching Office (MSO)

AudioDistributionSubsystem

ManagementSubsystem

Mobile SwitchingOffice

ZoneController Control

1.2.2 Modes of OperationThe figure Figure 1-18 Modes of Operation in a Dimetra System shows the normal mode of operation and thethree fall back modes with reduced capabilities: Zone Isolated Wide Area Trunking, Local Site Trunking andDirect Mode Operation (DMO).

1-16 - March 2012

1.2.2.1 Wide Area Trunking with Interzone Trunking

Figure 1-18 Modes of Operation in a Dimetra System

Wide Area Trunking with Interzone Trunking

Zone Isolated Wide AreaTrunking

Direct Operation

Mode

Local SiteTrunking

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

1.2.2.1 Wide Area Trunking with Interzone Trunking

The normal operating state for each site in the system. If all sites are in wide area trunking with interzone trunkingmode, there are communication paths covering the entire zone and the interzone links are functional. The ZoneController is in control of call processing and audio routing; each site has an active control channel and at leastone operational traffic channel. Interzone and site links must be operational to support the control and audio trafficbetween the remote sites, the MSO and other zones in the system.

1.2.2.2 Fall Back Modes

There are three fall back modes in a Dimetra IP system detailed below: Zone Isolated Wide Area Trunking, LocalSite Trunking and Direct Mode Operation.

1.2.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 withthe zone can still communicate with each other, but communication with radios in other zones is impossible.

1.2.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 siteare lost. The affected site operates as a single site trunked system providing services to radios registered with thesite. Audio is not routed to the MSO, it remains within the site. The remote Site Controller is in control of callprocessing at the site while the Zone Controller maintains all other sites in wide area trunking.

- March 2012 1-17

System Overview

The site can stay in local site trunking mode as long as there is a good control path between the Site Controller andthe registered base stations, an active control channel, and a working traffic channel.

1.2.2.2.3 Direct Mode Operation (DMO)

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

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

Figure 1-19 Example: Multizone System

1.3.1 Requirements for Multizone CommunicationA multizone system contains the following elements, which are necessary to maintain system wide communication:

• An active control path is required between any two pair of zones in order to be able to coordinate a call thatinvolves sites in more than one zone.

• Interzone audio paths are needed to route the audio to any zone required by the location of the talkgroupmembers.

1-18 - March 2012

1.3.1.1 Home Zone Mapping

Figure 1-20 Multizone System - Conditions for Interzone Trunking

Master SiteZone 1

Site 3

Site 2

Site 1 Site 4

Site 5

Site 6

Site 9Site 7

Site 8

Master SiteZone 2

Master SiteZone 3

ControlAudio

ControlAudio

ControlAudio

Con

trol

Aud

ioContro

l

Audio

ControlAudio

ControlAudio

Control

AudioCon

trol

Aud

io

Control

Audio

Con

trol

Audi

o

Control

Audio

Multizone systems contain various hardware devices and software applications that allow the system to exchangecontrol information between zones, establish audio paths between zones when necessary, track radio movementacross sites or zones, and provide a management subsystem that can be accessed from any one of the zones. Theterminology has expanded to include home zone mapping, controlling zone, and participating zone-three multizoneterms described in the following.

1.3.1.1 Home Zone Mapping

Home zone mapping provides the capability to divide into ranges the total number of individual and talkgroup IDsthat can be used in the system and to assign the ranges to the various zones. All of the home zone assignments forgroups and individuals are compiled into two home zone maps:

• Individuals to Home Zone• Groups to Home Zone

The zone assigned to a particular ID is the home zone of this ID. The home zone to which an ID is assigned has animpact 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 arehome 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 zonewhere the group member is currently registered. Depending on system configuration, this can impact the number ofinterzone calls versus the number of single-zone calls that take place in the system. This can then affect the numberof interzone resources that are needed between any two pair of zones.

- March 2012 1-19

System Overview

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. Whena talkgroup member requests a call that requires more than one zone, the controlling zone receives acknowledgmentsfrom all participating zones before the call is granted. Resource allocation is invoked by a request sent fromcontrolling zone to all participating zones. The acknowledgment from a participating zone is only sent if resourceallocation is successful.

1.3.2 Interzone Group Service AvailabilityFor 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 tothe home zone of the group.

• Reduced interzone group service availability: At least one participating zone is in interzone trunking withthe 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 siteresources.

1.3.3 Where Calls OccurCalls can occur in a single site, a single zone, and between multizones. The following are some examples ofwhere calls can occur.

1.3.3.1 Single Site

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

1.3.3.2 Zone

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

1.3.3.3 Multizones

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

1-20 - March 2012

2 Dimetra IP System Technology

Topics Covered in this Chapter

• Terrestrial Trunked Radio (TETRA)• Network Technology• Digital Motorola Enhanced Trunked Radio (Dimetra)• End-to-End Secure Communication• System Summary

The Dimetra IP system is a digital radio communications system that provides radio users with voice and dataservices over a very wide geographical area. Users at any location within the coverage area can press thePush-To-Talk (PTT) button on their radios to make calls to any valid group or individual located anywhere in thecoverage area (which can cover thousands of square miles).

The system requires a complex network of workstations, high-speed Local Area Network (LAN) and Wide AreaNetwork (WAN) facilities, sophisticated databases, and management software.

The Dimetra IP system allows communication across multizones and allows users from different zones to becombined into talkgroups. This means that users can communicate across a wide geographic area and use a widerange of communication capabilities, provided that the user configuration is well-planned and systematicallyimplemented.

2.1 Terrestrial Trunked Radio (TETRA)The (TETRA) standard was developed by the European Telecommunications Standards Institute (ETSI) for privatemobile radio. TETRA provides standardization for radio system services, system interfaces, and methods forregistration and call processing. ETSI has defined TETRA as open standard to provide standardization andinteroperability of telecommunication systems and their application.

Some of the TETRA standards include the following:

• 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 fromdifferent suppliers to be used for basic TETRA operations regardless of the supplier of the infrastructure – seethe figure below.

- March 2012 2-1

System Overview

Figure 2-1 TETRA defined Air Interface

Infrastructure

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 ManagementBecause frequency spectrum is a finite resource, the use of channels is authorized and licensed by governmentagencies in most countries. International regulations fall under the jurisdiction of the InternationalTelecommunications Union (ITU). The European Telecommunications Standards Institute (ETSI) producesstandards and regulations for telecommunications in the European region.

The frequency spectrum allocations in the European region are shown in Figure 2-2. Frequency allocations in otherregions are defined by their own governing agencies or committees and may be different than the spectrum shownbelow. Frequency allocations for TETRA users are between 380 and 430 MHz. Figure 2-3 European TETRA RadioFrequency Spectrum illustrates the specific TETRA range of frequencies.

Dimetra IP systems operating in other regions may be subject to other frequency spectrum allocations as defined bythe regional authorities.

Figure 2-2 European Frequency Spectrum - Overview

2-2 - March 2012

2.1.2 Pi/4-DQPSK Modulation

Figure 2-3 European TETRA Radio Frequency Spectrum

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 governingbody. The license is granted to operate on a particular frequency, or set of frequencies, with specific eligibilityrules that must be met.

2.1.2 Pi/4-DQPSK ModulationA radio transmitter sends signaling across at a particular carrier frequency. To deliver intelligible traffic across thiscarrier, the radio transmitter modulates outbound traffic with the carrier signal. The receiver then demodulates thetraffic 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. Thismodulation 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 phaseshifts 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-digitbinary value for each phase shift.

The phase shift example shows a transmission shift from phase 0 (in phase) to 3pi/4. The receiver would recognizethis shift and declare the received value as 01. The next phase shift shown is from 3pi/4 to pi/2. The receiver wouldrecognize this shift as a binary value of 10. Each point offers four possible phase shifts for the next transmission.

- March 2012 2-3

System Overview

Figure 2-4 Pi/4-DQPSK Modulation

2.1.3 ACELP Voice CompressionVoice signaling must be compressed to maintain the high rates of traffic flow. The Dimetra IP system and its radiosuse 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 ordigital 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 thecodebook. The receiver then receives the data, looks up the index numbers from its codebook, and reconstructsthe data.

The ACELP compression method uses voice prediction algorithms and filters, along with its own particularcodebook, which allows quality audio to be synthesized in as little as 8 kbps. As shown in figure below, the radioprocesses 30 msec blocks of speech. The final compressed signal is placed in a TDMA timeslot for transmission.

Figure 2-5 ACELP Voice Compression

2-4 - March 2012

2.1.4 Time Division Multiple Access

2.1.4 Time Division Multiple AccessThe Dimetra base stations and radios use Time Division Multiple Access (TDMA). Each carrier signal is dividedinto 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 figurebelow, the first channel on the first base station is typically configured as the control channel. All other channels atthe site (base stations 2-8) are configured as traffic channels or packet data channels as required. The first channelon base stations 2-4, however, are also configured with control channel capability, allowing any one of them tooperate as a control channel if the primary control channel fails. The figure shows the typical channel configurationsmade for a site with up to eight base radios.

Figure 2-6 Time Division Multiple Access - Base Stations

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 truefull-duplex capability, the radio switches between the transmit and receive channels to simulate full-duplex capabilityfor telephone interconnect calls and full-duplex individual calls. The transmit and receive time slots are offset by twoslots to accommodate this switching and to allow the radio to both send and receive traffic within each time frame.

Figure 2-7 Time Division Multiple Access - Radio (Full-Duplex Operation)

2.2 Network TechnologyThe following describes network concepts applicable to a Dimetra IP system.

- March 2012 2-5

System Overview

2.2.1 Local Area NetworkA Local Area Network (LAN) is a data communications system designed to link computers and peripheral devicessuch as printers and modems. LAN cabling has a limited usable distance of up to 100 m (329 ft) and is best usedwithin a building or campus environment. The advantage of using a LAN is that users can share peripheraldevices connected to the LAN instead of having those devices attached to each computer. Network users can alsoshare information stored in the network server, such as databases and programs. In addition, network users cancommunicate 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) sothey can be shared by users of the network. Originally developed to run at 10 Mbps, Ethernet networks can now runat 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 Mbpsnetworks. Based on the type of cabling used, the following is a list of the different versions of 802.3:

• 10Base-5 - Thick Ethernet

• 10Base-2 - Thin Ethernet

• 10Base-T - Twisted pair Ethernet

• 10Base-FL - Fiber Optics

Ethernet accesses data using Carrier Sense Multiple Access with Collision Detection (CSMA/CD). This methodallows multiple users to access the network through a common cable. All devices attached to the network check fortransmissions in progress, signals are checked at the start of transmission and during transmission. Signals are sent ifno other transmission is detected; otherwise, the transmission is delayed. Collision detection is applied when two ormore devices transmit at the same time. A device knows if a collision occurred when it does not receive its owntransmission back. Each device stops transmission and attempts to retransmit after waiting a certain amount oftime, 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 anetwork are connected to a common central device by point-to-point links. The information arriving at the commondevice is broadcast to all the end point devices; each device is responsible for determining whether the informationis 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 shieldedtwisted pair cabling (STP) to provide additional protection against interference. The following list demonstrateshow 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

2-6 - March 2012

2.2.1.4 Virtual LANs

The Network Interface Card (NIC) performs the functions of a transceiver so that no external transceiver is neededfor 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 startopology, if a station goes down it does not affect the rest of the network. Typically, an RJ-45 connector is found ateach 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. Itworks 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 commonunshielded 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 VirtualEthernet segments. In a conventional Ethernet LAN, a group of communicating stations were physically connectedto a shared hub or a shared cable segment. All members of the group needed to be within 100 cable meters of thathub of the group. If one of the group members had to move to a new location, cabling changes would have to bemade to accommodate the move.

VLAN technology allows a system administrator to assign each port of a switch to members of different Ethernetsegments. The MSOs in a Dimetra IP system use switches that support VLAN technology in an extended stackableconfiguration.

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 distributionpoint through their own cable. With switched Ethernet, the central, passive hubs used to form conventional coreLAN switches are replaced with intelligent switches. The switches allow each sending computer to be temporarilydirectly 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 isavailable to any two stations that wish to communicate.

Switched Ethernet technologies are used to allow equipment to communicate within a zone. The system usesLAN transmission to handle the flow of intrazone data. It also uses Wide Area Network (WAN) transmission tohandle the flow of interzone data.

Three basic types of information are exchanged in the system: voice, call control, and network managementtraffic. Network management and control information must be exchanged between devices installed within eachindividual zone, and between devices installed in different zones. Ethernet and Frame Relay are the primarycommunication technologies used to implement high-speed exchanges of management, control, and voice trafficamong the various devices within an individual zone.

Routers are used to implement high-level transport connections between network nodes in the system. Routers makethe LAN connections and WAN transmission facilities transparent to the network nodes that may be communicatingeither within the same zone or between one zone and another. Routers also allow alternate paths to be implementedbetween interconnected equipment to permit the system to continue operating should specific physical links fail.

2.2.2 Wide Area NetworkThe 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 toanother. It is possible to use either E1 or Ethernet (see 2.2.5 Ethernet Site Links, page 2-11). Speeds rangefrom 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-wireanalog leased line provides slower speeds, generally up to 33.6 kbps.

- March 2012 2-7

System Overview

• Packet-switched networks: Packet-switched networks break messages apart into packets and tag each packetwith 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 provideadditional management capability. Frame relay includes a cyclic redundancy check (CRC) algorithm thatdetects 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 durationof the communication. The advantages of the circuit-switched networks are dedicated circuits for the call andcustomers do not pay for idle bandwidth. Disadvantages are call setup time and potential under-utilizationof the communication channel. Circuit-switching is useful for short duration transmissions, for feeders tomain 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. Inconventional telecommunications, the most common use for an E1 carrier is to connect central offices within anindividual telephone company. Telephone companies also lease E1 carriers to their customers for their own privatepurposes. 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 facilitiesthat connect remote zones.

Various types of transmission media can be used in implementing a private E1 facility, such as various types ofprivately 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 thatcan support a bit rate of 64,000 bps. Each of these individual channels is referred to as a Digital Signal Levelzero (DS0) channel.

The term framing refers to the order in which user bits and other information is transmitted over a physicaltransmission medium. An E1 frame comprises a total of 256 bits. Each of the 32 inputs is assigned a fixed timeslot; the E1 uses a time-division multiplexing technique to divide the capacity of the carrier into 32 channels. Theframing bit is used to create a pattern to help synchronize the equipment. The figure below illustrates the format ofthe E1 transmission frame.

Figure 2-8 E1 Carrier

2.2.2.2 X.21 Link

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

2-8 - March 2012

2.2.2.3 Frame Relay

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 IPsystem uses a 15-pin V.11 physical interface for connection to X.21 links.

2.2.2.3 Frame Relay

Frame Relay is a simplified form of connection-based, packet-switching service in which synchronous frames of dataare routed to destinations indicated on the header information. Frame Relay assumes an error-free physical link andtherefore 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 theoctets between the flags, and the end flag.

Permanent Virtual Circuits (PVCs) are used to form a connection between any two devices attached to a FrameRelay cloud. Virtual circuits are logical, bidirectional, end-to-end connections that appear to the user as dedicatedlinks. Each PVC is given a unique number on each physical circuit along the path between the two devices. Thisunique number is called a Data Link Connection Identifier (DLCI). The DLCI is automatically changed to the PVCnumber of the next physical circuit as it passes through each switch along the path. A DLCI is different from anetwork address in that it identifies a circuit in both directions, not a particular endpoint. A frame contains onlyone 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 ofthe Frame Relay cloud. DLCIs only have local significance and represent end-to-end virtual connections that havea permanently configured switching path to a certain destination. Thus, by having a system with several DLCIsconfigured, you can communicate simultaneously with several different sites.

2.2.3 Multi-LAN SharingIn some cases it is possible to share some of the network transport equipment over more than one zone. It isdescribed in the following.

2.2.3.1 Multi-LAN Sharing

In order to combine several zone cores within one MSO (up to three zones within an MSO) a Multi-LAN ShareMSO concept is used. A Multi-LAN Share MSO is defined to have multiple zone cores that are colocated at thesame physical site.

A Multi-LAN Share MSO provides Intra-MSO connectivity. Within an Multi-LAN Share MSO, several VLANsand virtual ports are created on the Core LAN Switch and each exit router group to provide peer-to-peer InterZonecommunications between exit routers in the share. A maximum of six exit routers are supported in one Multi-LANShare MSO; one pair per individual zone core. To learn more about exit routers read Motorola Network Routersmanual.

A SZC can be added to an existing Multi-LAN Share MSO, but can only support a single zone. In order to supportmore than 3 zones within the MSO, Multi-LAN shares will be connected together, or connected to single zone cores.The links will be via E1 connection to the exit routers, to form so called Inter-MSO connections.

2.2.4 Cooperative WAN Routing (CWR)The Motorola® Cooperative WAN Routing (CWR) solution offers simple, reliable, passive relay panels controlleddirectly from the routers. In multizone systems, the routers are configured in pairs to provide path redundancy foraudio and control packets. With CWR, the routers work to control an external relay panel to switch a group of 12

- March 2012 2-9

System Overview

non-redundant E1 links between the two routers. One router is always considered as the "Active" router and theother 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. Framerelay 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 onelogical link. E1s are configured as CVCs then, as one logical AVC. Multiple E1s are required between the zonesthat have physical connectivity.

Figure 2-9 Cooperative WAN Routing - Example

2-10 - March 2012

2.2.4.1 Satellite Link Based WAN Connectivity

2.2.4.1 Satellite Link Based WAN Connectivity

• Only 2 MSOs can be connected via Satellite• Each MSO can be 1 zone only• Satellite link bandwidth is limited to 1Mb/s throughput

Satellite links are supported for connecting two single zone MSOs as depicted in Figure 2-10. Satellite linkconnectivity is limited to 1Mb/s.

2.2.5 Ethernet Site LinksThe ESL feature provides a means to establish Ethernet connections of the following type:

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

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

Figure 2-10 Ethernet Site Links - Example

Ethernet routers support either encrypted or unencrypted tunnels, however a mixed configuration of encrypted andunencrypted tunnels on the same router is not supported. When a zone core has a mixed configuration of encryptedand unencrypted tunnels, at least two pairs of Ethernet routers are required. One pair is configured to terminate theencrypted 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 isconnected to the primary backhaul switch and terminates the primary Ethernet links, and the secondary router isconnected to the secondary backhaul switch and terminates the secondary Ethernet link.

2.3 Digital Motorola Enhanced Trunked Radio(Dimetra)2.3.1 Dimetra IP System Components

The basic components of the Dimetra IP system are the following:

• 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)

- March 2012 2-11

System Overview

The Dimetra IP system distributes the call processing load between the zone or zones that comprise the system. Userconfiguration information also is shared among the zones. Each zone has a Local Area Network (LAN). The LANsare interconnected through a high-speed transport network to form a Wide Area Network (WAN). The WAN allowsuser 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 withina zone, so they are defined as zone level functions.

The following provides an introduction to the various components and processes associated with the Dimetra IPsystem.

2.3.2 Dimetra IP System CoreAt the centre of the Dimetra IP system is a transport core designed to carry the system applications. This transportcore 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 large number of zones/sites per system. Multizone systemsare formed with max 16 clusters , max 7 zones per cluster and max 56 zones per system.

• Digital only platform that supports Algebraic Code Excited Linear Prediction (ACELP) for voicetransmission.

• 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, thedigital information is passed all the way through the network with no conversions required. Conversionto the original audio format is required only at the destination receiver. The Dimetra IP system supportsair interface encryption.

• The transport core consists of a packet transportation network that is not concerned with what is contained inthe packets.

The Dimetra IP system includes an Internet Protocol (IP) based infrastructure that provides IP multicast technologyfor dispatch services and RF sites. This technology allows group calls to be set up, processed, and torn down easilyin a packet environment, replacing circuit switched methods.

2.3.3 Unicast RoutingUnicast 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. Networktransport devices, such as routers and switches, observe the destination address for incoming packets and direct thepackets 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-11 Unicast Routing

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

2-12 - March 2012

2.3.4 Multicast Routing

2.3.4 Multicast RoutingMulticast routing involves a point-to-multipoint routing of traffic. Multicast differs from unicast, where packetsare routed from one point to another. Multicast also differs from broadcast, where packets are sent from a singlesource 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 joinmessages to identify all the nodes that is receiving the multicast traffic. The router builds a multicast tree whichincludes all the recipients. When the source starts to send its packets, the RP receives the packets, replicates eachpacket, 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.

Figure 2-12 Multicast Routing

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 bedistributed to the appropriate sites by the RP router. Without multicast, the source would have to separately addressmultiple 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 multicastgroup. After the join messages are received from the devices, the RP propagates the multicast traffic to theappropriate 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 routerlocated near the source of the traffic. This allows greater efficiency of network resources, since the higher volumesof multicast traffic is only spread across the receiving end of the network, rather than spreading all the replicatedpackets 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. Arange of class-D IP addresses (addresses beginning with 224 -239) are designated as multicast group addresses.

2.3.5 Call ModelWhen and where to use:

The main purpose of a Dimetra IP system is to provide voice services to radios and dispatchers throughoutthe system. The process below describes how a talkgroup call is serviced by the system. See Figure2-13 Call Processing - Multicast Routing of Traffic in conjunction with the following description of abasic multicast call example.

Process Steps

- March 2012 2-13

System Overview

1 A radio user presses the PTT button to talk to other users in the talkgroup. The radio transmits a Call Requeston the RF control channel at the site. The Call Request is received by the control channel and forwarded tothe site LAN. Before placing the Call Request packet on the site Ethernet LAN, the base station encapsulatesthe Call Request message in a User Datagram Protocol (UDP/IP) datagram with the destination IP addressof 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 transferredacross the network, how devices are addressed, and how to route data appropriately. IP defines auniversal/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 Requestmessage, the Zone Controller checks an internal database to determine the location of all members in therequested talkgroup (such as RF sites and remote dispatch site locations). The Zone Controller then assigns amulticast group address to the call and sends the assigned multicast group address to all the participating RF sitesand 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 theCall Grant. The assigned traffic channels at RF sites and the consoles at the MSO generate a group Joinmessage. 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 communicatewith RP routers in the system to set up an IP multicast distribution tree. This tree is used to distribute voicepayload 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 receivedby the traffic channel and is placed in an IP datagram destined to the assigned IP multicast address (as assignedin 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 Pointrouter and IP multicast tree.

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

2-14 - March 2012

2.3.6 Traffic Planes

8 When the call is over (expiration of the message timer), the sites (RF or dispatch) generate an IP group Leavemessage. 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. Thisparameter is programmed in the system, through the User Configuration Manager (UCM), as messagetrunking, and in the radios, through their programming software, as PTT-ID.

Figure 2-13 Call Processing - Multicast Routing of Traffic

2.3.6 Traffic PlanesThere are a number of logical traffic planes set up in the transport network. These are used to describe thecommunications paths which exist within the network and traffic types carried over those paths. The followingtraffic planes are the most important ones within Dimetra IP systems:

• 2.3.6.1 Voice Control Plane, page 2-16

• 2.3.6.2 Audio Plane, page 2-16

• 2.3.6.3 Data Plane, page 2-16

• 2.3.6.4 Network Management Plane, page 2-16

- March 2012 2-15

System Overview

2.3.6.1 Voice Control Plane

Traffic between the Zone Controller and the RF sites within a zone, and between Zone Controllers in different zonesis called Voice Control traffic; the logical plane used to transport this information is called the Voice ControlPlane. Voice Control traffic is responsible for setting up the audio path between the transmitting site and thereceiving site or sites. The Zone Controller, through the voice control plane, receives talkgroup requests and sendsmessages to appropriate sites, assigning an IP multicast group address to use for the call. Control communicationfrom the Zone Controller to the RF sites is accomplished using multicast; unicast is used for transmissions fromthe 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 tocarry audio packets for all call types (group calls, private calls, telephone interconnect calls) between radios ina system (both intrazone and interzone).

2.3.6.3 Data Plane

The Data Plane is made up of the unicast and multicast trees that is used as communication paths between theZone 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-14 Dimetra IP System Logical Traffic Planes

Traffic in the figure above denotes three types of traffic:

• Audio traffic• Data traffic• Control traffic

2-16 - March 2012

2.3.7 Cluster and Multicluster Architecture

2.3.7 Cluster and Multicluster ArchitectureIn the Dimetra IP system, up to seven zones form a cluster, and up to sixteen clusters can form a full capacityDimetra IP system (which may include a maximum of 56 zones total). Each cluster includes a separate set ofcluster-level servers which manage operations in the cluster. These servers include a User Configuration Server(UCS), System Statistics Server (SSS), and the Transport Network Performance Server (TNPS).

Figure 2-15 Clusters and Individual Zones

2.4 End-to-End Secure CommunicationThe 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 keyto transform clear digital messaging into an encrypted code. Modern algorithms do not just scramble messages, butconvert messages bit-by-bit into an entirely different encrypted form. The figure below shows the basic processused for secure communication. The sender uses a particular key and algorithm to encrypt clear traffic. The trafficthen passes across the medium in an encrypted form. The recipient then uses the same key and algorithm todecrypt the traffic.

Figure 2-16 Basic Secure Voice Operation

Encryption protects the information from being deciphered and understood by anyone outside the system. Withoutthe proper algorithm and the encryption key, any intercepted traffic is received as a bunch of garbled digital bitswrapped in packets. If there is no encryption, hobbyists or hostile groups can intercept and decipher traffic.

- March 2012 2-17

System Overview

The Motorola secure voice and data solution uses sophisticated algorithms to protect voice traffic. Depending on thealgorithm used, a radio can be provisioned with a large number of keys. By rotating keys on a regular basis, it wouldbe 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 clearvoice using a particular key (CG456) and transmits the encrypted voice to the transport network. The secure voicetraffic 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.

Figure 2-17 Voice Transmission

Compared to Air Interface Encryption (AIE), the secure voice solution adds an additional level of confidentialityto the speech traffic and is an enhancement to the system. This service does not replace any of the other standardTETRA 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 fromone radio to another. AIE only provides security for messages between the base station and the radios and it doesnot provide any security for messages that exist within the infrastructure, whereas secure voice provides securitybetween the end users, even within the infrastructure.

Apart from voice, Motorola has also developed a solution for delivering encrypted data. End-to-End Encryptionfor 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 communicationremains secure between the source and the destination. Secure data is a supplementary service located on a customerpremises (the Switching and Managing (SwMI) infrastructure is not encryption aware). The solution is based on thecurrent key management solution, in other words, a symmetrical key exchanged with the KMF. Digital encryptionconverts the digital data, using an encryption key together with an encryption algorithm, into an encrypted messagewhich is then transmitted. Only an endpoint that shares the same encryption key and encryption algorithm is ableto decrypt the transmission successfully. Other devices that do not have the proper key are not able to receiveintelligible information.

For more information see Managing Secure Communications manual.

2.5 System SummaryThe first table summarizes the general TETRA system capabilities on a Dimetra IP system, while the next tablesummarizes the Dimetra IP system capacities.

2-18 - March 2012

2.5 System Summary

Table 2-1 TETRA System Capabilities

Feature SupportDigital frequency bands supported 260-275 MHz

350-470 MHz806-870 MHz

Air interface encryption types supported TEA1, TEA2, TEA3

Digital Codec ACELP (TETRA standard for speech coding)

The frequency bands provided above may differ based on the local regulations of your country.

Table 2-2 Dimetra IP System Capacity

Feature SupportMaximum number of zones per system 56 zones

Maximum number of clusters per system 16 clusters

Maximum number of zones per cluster 7 zones

Maximum number of BTS sites per zone 100 sites

Number of individual IDs per cluster 128000 IDs

Number of talkgroup IDs per cluster 64000 IDs

Maximum channels per BTS site (MTS LiTE, MTS 1/MTS2/MTS 4)

1/2/4/8 carriers with 4/8/16/32 TDMA channels

In systems with more than one cluster, each cluster can support the maximum number of individual andtalkgroup IDs shown in Table 2-2 Dimetra IP System Capacity . However, the maximum number ofindividual radios per zone is 64000. If talkgroups or individual radios operate in more than one cluster,their IDs must be provisioned identically in each cluster where the individual radios or talkgroup membersmay roam. This identical provisioning across multiple clusters can reduce the total number of radios andtalkgroups that can be provisioned in the system.

- March 2012 2-19

3 Dimetra IP System ComponentsTopics Covered in this Chapter

• Mobile Switching Office (MSO)• Network Transport Subsystem• Remote Sites• Radios

3.1 Mobile Switching Office (MSO)A Dimetra IP system can be a single zone system or it can have more zones, which then are part of clusters.Up to 7 zones can form a cluster.

All the components that communicate over Ethernet are connected through multiple core LAN switches . Theseswitches 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 callswithin 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 managementand system configuration.

One of the master sites (which are physical locations in Dimetra system containing one or more sets ofzone control equipment) in a multizone system is generally designated as the cluster MSO. This MSOtypically includes the cluster-level servers, including the combined User Configuration Server (UCS) andSystem Statistics Server (SSS). A single zone system does not require an SSS.

3.1.1 System ServerThe System Server is a platform on which most Dimetra IP servers are installed. The platform is a HP ProLiantDL360 G7 server with Red Hat Enterprise Linux 6, which provides a virtual environment, allowing to installWindows or RHEL Linux servers (containers, VPSs). These virtual servers, from the networking perspective,behave like separate devices. The following functional entities can be installed on the server:

• Alias Integrated Solution server• Key Management Facility• Core Security Management Server (Antivirus Server, RSA Server)• Firewall Manager• Domain Controller• Short Data Router• Packet Data Router• Radio Network Gateway• Zone Controller• System Statistic Server• Zone Database Server• Zone Statistic Server

- March 2012 3-1

System Overview

• Air Traffic Router• User Configuration Server• Alias Server• MultiCADI Server• InfoVista®

• Motorola Telephone Gateway with IP connectivity• Motorola Telephone Gateway with E1 connectivity• Unified Event Manager• Authentication Centre• Upgrade Install Server• Audio Gateway Server• Call Control Entity

Figure 3-1 HP DL360 G7 Server Front View

3.1.1.1 Types of the System Server

The table below presents possible configurations, in which HP ProLiant DL360 G7 can be deployed in the system.

Table 3-1 Types of System Server (constellations)

System Server Type List of EntitiesPrimary Zone Server Zone Controller, Core Security Management Server, Upgrade Install

Server, Zone level Domain Controller, Cluster level Domain Controller,Firewall Management Application

Secondary Zone Server Redundant Zone Controller, Core Security Management Server, UpgradeInstall Server, Zone level Domain Controller, Cluster level DomainController, Firewall Management Application

Primary Management Server User Configuration Server, Zone Database Server, Zone StatisticsServer, Unified Event Manager, System Statistics Server, Air TrafficRouter, Infovista Server, Alias Server, MultiCADI Server, EnhancedAuthentication Centre

Secondary Management Server User Configuration Server, Zone Database Server, Zone Statistics Server,Unified Event Manager, System Statistics Server, Air Traffic Router,Infovista Server, Alias Server, MultiCADI Server, Authentication Centre

Primary Data Server Short Data Router, Packet Data Router, Radio Network Gateway

Secondary Data Server Short Data Router, Packet Data Router, Radio Network Gateway

Dispatch Communication Server Call Control Entity, Audio Gateway Server, Upgrade Install Server

MTIG-IP01 MTIG-IP01

MTIG-IP02 MTIG-IP02

MTIG-E101 MTIG-E101

MTIG-E102 MTIG-E102

Primary Standalone EAuC Primary Standalone EAuC

Secondary Standalone EAuC Secondary Standalone EAuC

3-2 - March 2012

3.1.2 Zone Controller

3.1.2 Zone ControllerThe Zone Controller is a redundant processor that provides call processing for wide area radio communicationssystems and telephone interconnect devices for system operation. 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.

The Call Processing subsystem consists of the Zone Controller, which resides on the Primary Zone Server.

Two redundant Zone Controllers are connected to the network through the core LAN switch . This switch providesconnections over two separate virtual LANs, used to switch system resources between the Zone Controllers andprovide high availability for call processing and resource management. While both Zone Controllers are powered andenabled 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 responsiblefor call processing is in the active state. The Zone Controller that is not actively processing calls in the zoneis in the standby state. The standby controller remains in standby mode until the active Zone Controller fails oruntil a switchover command is initiated. System information that is necessary for call processing is downloadedto both Zone Controllers. The Zone Controllers include hardware for storing data, controlling zone activities,and communicating with zone resources.

For more detailed description of the Zone Controller, see Call Processing Subsystem manual.

3.1.3 Network Management SubsystemThe Network Management Subsystem is based on the client/server networking model. The NMS meshes seamlesslyand scales with the other infrastructure elements across the packet-switched network. The network managementsubsystem 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 supports the management of a complex radio communicationssystem and its component parts, which include radios, computers, and inter-networking components. Networkmanagement tools support the maximization of resource availability while helping to minimize system downtimeand maintenance costs.

- March 2012 3-3

System Overview

Figure 3-2 Network Management Subsystem

SecondaryManagement

ServerSecondary

Zone Server

PrimaryManagement

ServerPrimary

Zone Server

MTIG-E1 Server 1

EC

CWR CWR CWR CWR

SecondaryData

Server

NTS

MCC7500NM Client Voice Logging Replay Station AISGW2

To P

AB

X

GP

S

Core LAN Switch 1&2

GGSN 2

GGSN 1Primary Data

Server

E1 - Core 1

BTS / Remote Control Zone / Other Zone

E1 - E1 - E1 - E1 - E1 -

E1 - GBN

Customer Network

ICCS GW Router 1

ICCS Switch 1

ICCSFW 1

ICCS GW Router 2

ICCS GW Server ICCS

Switch 2

ICCSFW 2

ICCS GW Router 3

ICCS Switch 3

ICCSFW 3

ICCS GW Router 4

ICCS GW Server ICCS

Switch 4

ICCSFW 4

CENIBFW 2

CENIBFW 1

MTIGFW 1

MTIG-IPServer 1

TerminalServerClient

DMZ Switch 1&2

BorderRouter

BorderRouter

TerminalServer

Mutually exclusive

Secondary Zone Server

PrimaryZone Server

MTIG-E1 Server 1

EC

CWR CWR CWR CWR

SecondaryData

Server

NTS

MCC7500 Voice Logging Replay Station AISGW2

To P

AB

X

GP

S

Core LAN Switch 1&2

GGSN 2

GGSN 1Primary Data

Server

E1 - Core 1

BTS / Remote Control Zone / Other Zone

E1 - E1 - E1 - E1 - E1 -

E1 - GBNE1 - GBNE1 - GBN

Customer NetworkCustomer NetworkCustomer NetworkCustomer NetworkCustomer Network

ICCS GW Router 1

ICCS Switch 1

ICCSFW 1

ICCS GW Router 2

ICCS GW Server ICCS

Switch 2

ICCSFW 2

ICCS GW Router 3

ICCS Switch 3

ICCSFW 3

ICCS GW Router 4

ICCS GW Server ICCS

Switch 4

ICCSFW 4

CENIBFW 2

CENIBFW 1

MTIGFW 1

MTIG-IPServer 1

TerminalServerClient

DMZ Switch 1&2

BorderRouter

BorderRouter

TerminalServer

Mutually exclusive

Zone Database Server (ZDS)Unified Event Manager (UEM) Server

Zone Statistic Server (ZSS)Air Traffic Router (ATR)

User Configuration Server (UCS)System Statistic Server (SSS)

3-4 - March 2012

3.1.3.1 Network Management Servers

The server components of the Network Management subsystem reside on the Primary Management Serverand 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, AccountingPerformance and Security Management. The network management functions in Dimetra IP are distributed acrossseveral applications and servers that are installed in one of three configurations: system, zone, and remote. Theconfigurations are designated by the name Operations Support Systems (OSS). The following describes theindividual network management building blocks of the Zone OSS, Cluster OSS, and Multicluster OSS. Thesebuilding blocks 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.

– InfoVista®

– Transport Network Configuration Tool (TNCT)

– 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)

• System Statistics Server (SSS)

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

- March 2012 3-5

System Overview

3.1.3.2 Transport Network Performance Server

Zone level network transport management is conducted by Transport Network Performance Server (TNPS). Itmanages the network transport devices at the RF sites and control sites in the zone.

3.1.3.3 Operations Support Systems

Operations Support Systems (OSS) is a term used to specify the devices used to manage the system. This includesnetwork management servers and clients. There are three levels of the OSS: Zone, Cluster, and Multicluster.

• Zone OSS: The Zone OSS refers to the network management system for a given Zone. The servers arealways 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 seven zones from a single location. To accomplishits task, the Cluster OSS must have a routed path to all supported zones. The Cluster OSS consists of thecombined User Configuration Server (UCS) and System Statistics Server (SSS), Unified Event ManagerServer (optional), and the Network Transport Performance Server.

• Multicluster OSS: A maximum number of 16 clusters (56 zones) are supported in a multicluster Dimetra IPsystem. A network management client, which has the NTMS installed can access and configure informationfor all the clusters throughout the multicluster system from its location. The client is able to access UserConfiguration Manager for each individual cluster to configure radio users and system wide parametersfrom its location. The client is also able to run multicluster system performance reports and able to viewindividual InfoVista® reports from each of the clusters.

3.1.3.3.1 Fault Management at the Zone Level

A zone includes a workstation containing the Unified Event Manager and the traps and MIBs to the networkingequipment. This integrated set of tools is the core application for fault and configuration management for a majorityof 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 mapsspecific to Motorola devices.

• Traps and MIBs add fault and performance network management tools for the networking devices.

3.1.3.3.2 Configuration Management at the Zone Level

Zone-level configuration management tools are available to configure all the devices in the zone. To the networkmanagement user, there is a single integrated interface for accessing configuration information for all devices inthe zone. The network management clients, which have the NTMS installed allow users to navigate to configureany 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 coreLAN switch OS and configuration file.

3.1.3.3.3 Performance Management

The Network Transport Performance Server (NTPS) also known as InfoVista® is installed at the cluster levelto provide performance statistics. InfoVista® can generate reports and display performance information for thecluster-level core LAN switches and routers.

InfoVista® provides the following features:

• Discovery of all routers and core LAN switches.• Creation of single report instances for each discovered device. It can also provide group report instances.

3-6 - March 2012

3.1.3.3.4 Security Management at the Zone Level

• Manual or scheduled export report instances for archival purposes (The archives can be used at a later timeto retrieve the information).

• Creation of a One Button Disaster Recovery (OBDR) image that can later be used to restore a server.

3.1.3.3.4 Security Management at the Zone Level

All network management applications have defined access privileges for each user. All the applications supportpassword protection at a minimum. A single login allows the user to access all the network management applicationsfor 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 supportpassword protection at a minimum. A single login allows the user to access all the network management applicationsfor 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 includesfeatures for setting user privileges and controlling their access to view and/or modify information contained in theconfiguration databases. Optional Agency Partitioning software allows a system administrator to assign accessprivileges 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 inthe cluster.

3.1.3.3.5 Network Management at the Cluster OSS

The Cluster OSS acts as a cluster-level integration point. Therefore, the Cluster OSS consists of applicationsto manage cluster wide settings.

InfoVista® with integrated MIBs from all networking devices collects detailed network performance information ateach Cluster OSS.

In addition, some configuration needs to be done at the device level to report information appropriately to eitherthe zone applications, the cluster OSS applications, or both. For example, the trap destination and communitystring needs to be configured for each device.

3.1.3.3.6 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 thecluster. This allows a network administrator to view all the alarm and status indicators for all the equipment inthe entire cluster.

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

3.1.3.3.7 Configuration Management at the Cluster OSS

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

3.1.3.3.8 Performance Management at the Cluster OSS

Performance management tools are needed to do LAN performance management and trending. InfoVista® is installedat the Cluster OSS to perform this function for long term historical performance reports and trending on the LANdevices. This tool collects statistics and stores them to be displayed in real time, daily, weekly, and monthly graphs.

- March 2012 3-7

System Overview

InfoVista® is configured to collect statistics and provide report capability for the following devices:

• Core LAN Switches

• WAN links

• Core routers

• Gateway routers

• Exit routers

Although reports are preconfigured for the site routers and their links, they are not enabled unless the userspecifically turns them on. This is to reduce the traffic going across the site links and to reduce the overhead on theInfoVista server so it can focus on the core LAN switches and routers at the core sites.

InfoVista® is configured with integrated MIBs from the managed devices.

3.1.3.3.9 Security Management at the Zone and Cluster OSS

All network management applications have defined access privileges for each user. All the applications supportpassword protection at a minimum. A single login allows the user to access all the applications for which they haveaccess privileges without having to login to multiple applications. However, this does not include applications, suchas Command Line Interface (CLI), that are resident on the networking devices. Users must log on to the networkingdevices to run resident network management applications.

3.1.3.3.10 Multicluster Network Management

A network management client can be configured to access zone-level and cluster-level applications in one or moreclusters. This allows the client to launch individual PRNM or NTM applications to manage faults, configureparameters, 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 homezone map can then be downloaded from one cluster and uploaded to all other clusters. Likewise any necessaryinformation (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 faultmanagement system. This allows a centralized collection of traps throughout the system.

3.1.3.3.11 Domain Controller

To support MCC 7500 consoles redundant Domain Controllers on both zone and cluster level is recommended. TheDomain Controllers handle both DNS and Active Directory services for the defined AD domain. All zone DCsare DNS slaved to the zone ZDS. On zone level the Domain Controllers handles security and group informationfor the MCC 7500 consoles whereas the cluster Domain Controllers handle user accounts. Domain Controllerscan be installed at the Control Sites, because of the big amount of network traffic generated between DCs andMCC 7500 consoles.

For more detailed description of Network Management Subsystem, see Network Management Subsystem manual.

3.1.4 Data SubsystemThe data subsystem enables users of the Dimetra infrastructure to send data files in various formats using packet dataservices, 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-8 - March 2012

3.1.4 Data Subsystem

Figure 3-3 Data Subsystem

SecondaryManagement

ServerSecondary

Zone Server

PrimaryManagement

ServerPrimary

Zone Server

MTIG-E1 Server 1

EC

CWR CWR CWR CWR

SecondaryData

Server

Infovista NTS

MCC7500NM Client Voice Logging Replay Station AISGW2

To P

AB

X

GP

S

Core LAN Switch 1&2

GGSN 1Primary Data

Server

Core 1

BTS / Remote Control Zone / Other Zone

E1 - E1 - E1 - E1 - E1 -

E1 - GBN

Customer Network

ICCS GW Router 1

ICCS Switch 1

ICCSFW 1

ICCS GW Router 2

ICCS GW Server ICCS

Switch 2

ICCSFW 2

ICCS GW Router 3

ICCS Switch 3

ICCSFW 3

ICCS GW Router 4

ICCS GW Server ICCS

Switch 4

ICCSFW 4

CENIBFW 2

CENIBFW 1

MTIGFW 1

MTIG-IPServer 1

TerminalServerClient

DMZ Switch 1&2

BorderRouter

BorderRouter

TerminalServer

Mutually exclusive

GGSN 2

SecondaryManagement

ServerSecondary

Zone Server

PrimaryManagement

ServerPrimary

Zone Server

MTIG-E1 Server 1

EC

CWR CWR CWR CWR

Infovista NTS

MCC7500NM Client Voice Logging Replay Station AISGW2

To P

AB

X

GP

S

Core LAN Switch 1&2

Core 1

BTS / Remote Control Zone / Other Zone

E1 - E1 - E1 - E1 - E1 -

E1 - GBNE1 - GBNE1 - GBN

Customer NetworkCustomer NetworkCustomer NetworkCustomer NetworkCustomer Network

ICCS GW Router 1

ICCS Switch 1

ICCSFW 1

ICCS GW Router 2

ICCS GW Server ICCS

Switch 2

ICCSFW 2

ICCS GW Router 3

ICCS Switch 3

ICCSFW 3

ICCS GW Router 4

ICCS GW Server ICCS

Switch 4

ICCSFW 4

CENIBFW 2

CENIBFW 1

MTIGFW 1

MTIG-IPServer 1

TerminalServerClient

DMZ Switch 1&2

BorderRouter

BorderRouter

TerminalServer

Mutually exclusive

GGSN 2

Packet Data Router (PDR)Radio Network Gateway (RNG)

Short Data Router (SDR)

- March 2012 3-9

System Overview

3.1.4.1 Data Gateway

The Data Gateway supports packet data services (PDR), Short Data Transport Service (SDTS), and AlphanumericText Service (ATS). The Data Gateway performs registration services for packet data users, maintains userpermissions 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 DataGateway. The Data Gateway changes the packet encapsulation, checks permissions for the user (as configuredthrough User Configuration Manager), and tunnels the traffic to the GGSN router. The GGSN router then providesIP tunneling via a border router to the customer enterprise network.

If authentication is supported at the customer enterprise network, then the appropriate challenge and responsehandshake information must be exchanged before packet data services are granted to the user. If DHCP servicesare used, then a DHCP server at the CEN assigns an IP address to the packet data user terminal equipment when apacket 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 theGGSN router. The PDR provides access control for packet data radios, according to UCM settings which are locallystored 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 datatraffic between the remote sites and the PDG. The RNG provides a logical connection to the sites, and providesencapsulation of traffic between the PDR and the remote sites. The RNG also communicates with the ZoneController 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 ShortSubscriber Identities for radio users (ISSIs) and talkgroups/multigroups (GSSIs) as defined in the User ConfigurationManager. For short data messages to radios, the SDR directs the messages to the appropriate RF site. For shortdata messages to a fixed customer enterprise network, the SDR maps the TETRA addressing to an IP address andforwards 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 oneSDR per zone for up to three zones in a cluster.

3.1.4.1.4 Gateway GPRS Support Node Routers (GGSN Routers)

Data Subsystem also includes Gateway GPRS Support Node Router. For more detail see 3.2.2.7 Gateway GPRSSupport Node, page 3-25.

3.1.4.2 Data Resilience for Data Gateway

Data resilience is the feature that takes the first steps to eliminate all ’Single Point of Failure’ points for datafeatures: short data and packet data.

The feature includes:

• Warm standby SDR and PDG• Warm standby GGSN• Resilient Mobility Push• Remote failure recovery

3-10 - March 2012

3.1.4.2.1 Redundant PDG and SDR

The feature is supported:

• Only if the core switch is the HP ProCurve Switch (HP2610)

• Only by MNR GGSN

The redundant solution is shown in the figure below. Primary components (in green color) shall be connected to theprimary core switch. Redundant components (in blue color) shall be connected to the secondary core switch.

Figure 3-4 Data Resilience

3.1.4.2.1 Redundant PDG and SDR

Redundant solution is always a 2N redundancy.

When a failure of either the active (providing service) SDR or PDG is detected, the manual switchover processshould be initiated by a network operator.

3.1.4.2.2 Redundant GGSN

Failure is automatically detected via VRRP and the change over occurs from the Active to Standby GGSN. Notethat mobile users have to re-establish context activation to regain access to the Packet Data service followingthe GGSN change over.

3.1.4.2.3 Mobility Push Interface

Redundancy of the mobility push interface is based on the creation of a second path via the Secondary Gatewayrouter. The Secondary Gateway router is configured with a new set of RPs (multicast addresses). In order to useboth the primary and the secondary mobility interfaces the PDG and SDR join the RPs on both routers. The ZCis also joined to the two RPs: one on Gateway Router 1 and the other on Gateway Router 2. These are used formobility queries.

Primary mobility path is shown in Figure 3-4 Data Resilience by green arrows, whilst the Secondary mobilitypath is shown by blue arrows.

For more detailed description of Data Subsystem, see Data Subsystem manual.

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

- March 2012 3-11

System Overview

Figure 3-5 Telephone Interconnect Subsystem

SecondaryManagement

ServerSecondary

Zone Server

PrimaryManagement

ServerPrimary

Zone Server

MTIG-E1 Server 1

EC

CWR CWR CWR CWR

SecondaryData

Server

NTS

MCC7500NM Client Voice Logging Replay Station AISGW2

To P

AB

X

GP

S

Core LAN Switch 1&2

GGSN 2

GGSN 1Primary Data

Server

Core 1

BTS / Remote Control Zone / Other Zone

E1 - E1 - E1 - E1 - E1 -

E1 - GBN

Customer Network

ICCS GW Router 1

ICCS Switch 1

ICCSFW 1

ICCS GW Router 2

ICCS GW Server ICCS

Switch 2

ICCSFW 2

ICCS GW Router 3

ICCS Switch 3

ICCSFW 3

ICCS GW Router 4

ICCS GW Server ICCS

Switch 4

ICCSFW 4

CENIBFW 2

CENIBFW 1

MTIGFW 1

MTIG-IPServer 1

TerminalServerClient

DMZ Switch 1&2

BorderRouter

BorderRouter

TerminalServer

Mutually exclusive

SecondaryManagement

ServerSecondary

Zone Server

PrimaryManagement

ServerPrimary

Zone Server

CWR CWR CWR CWR

SecondaryData

Server

NTS

MCC7500NM Client Voice Logging Replay Station AISGW2

To P

AB

X

GP

S

Core LAN Switch 1&2

GGSN 2

GGSN 1Primary Data

Server

Core 1

BTS / Remote Control Zone / Other Zone

E1 - E1 - E1 - E1 - E1 -

E1 - GBNE1 - GBNE1 - GBN

Customer NetworkCustomer NetworkCustomer NetworkCustomer NetworkCustomer Network

ICCS GW Router 1

ICCS Switch 1

ICCSFW 1

ICCS GW Router 2

ICCS GW Server ICCS

Switch 2

ICCSFW 2

ICCS GW Router 3

ICCS Switch 3

ICCSFW 3

ICCS GW Router 4

ICCS GW Server ICCS

Switch 4

ICCSFW 4

CENIBFW 2

CENIBFW 1

TerminalServerClient

DMZ Switch 1&2

BorderRouter

BorderRouter

TerminalServer

3-12 - March 2012

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 canindicate a relevant type of MTIG. MTIG-E1 is an MTIG that uses QSIG signaling towards the PABX. MTIG-IPis an MTIG that uses SIP signalling towards the PABX. MTIG-E1 and MTIG-IP are mutually exclusive within azone, 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 orMu-law PCM and to route this audio between the IP network and the customer-supplied PABX. The MTIG alsogenerates any required tones for telephone interconnect operation and provides a gateway path for the controlsignalling between the Zone Controller and the PABX. The Zone Controller communicates with the MTIG over theLAN to direct the setup and teardown of telephone interconnect call. See the Telephone Interconnect Subsystemmanual.

3.1.5.2 Echo Canceller

The Echo Canceller suppresses any echo from the external network that would otherwise be directed to the radioduring a telephone interconnect call. The Echo Canceller is placed where the IP and E1 lines meet. The EchoCanceller is the interface between the MTIG-E1 and the customer-supplied PABX. The Echo Canceller contains adual E1 card which is able to support up to 60 traffic channels. One Echo Canceller per MTIG-E1 is used, with acapacity 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 Subsystem 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 providesrouting and interfacing capabilities to multiple external networks. These are typically larger networks, which arerequired to connect to multiple user organization PABXs as well as PSTN. For this type of networks an EnhancedTelephone Gateway (ETG) is required. The Dimetra system typically connects to the ETG, which again connects tothe various external networks, that is, customer PABXs or PSTN. The system typically uses one PABX call route percustomer 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 Telephone Interconnect Subsystem manual.

3.1.5.4 MTIG Firewall

In the MTIG solution based on IP networking, a firewall is used between the MTIG and the Internet in order toprotect the Dimetra network from direct exposure from the security risks.

3.1.6 Provisioning and Authentication CentreThe Dimetra IP system includes a Provisioning Centre (PrC) and Authentication Centre (AuC) when airinterface encryption or authentication are installed on the network. The PrC is primarily responsible for storingand provisioning keys for the radios. The AuC is primarily responsible for storing and distributing necessaryauthentication 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 toeach radio supporting encryption or authentication. The PrC connects with a Key Variable Loader (KVL), which isa handheld device used to manually load keys into radios and other infrastructure equipment. The PrC keys aregenerated n the PrC or imported to the PrC and loaded into a KVL for distribution to radios.

- March 2012 3-13

System Overview

After a KVL loads keys into a radio, the radio sends a receipt or acknowledge message. When the KVL is connectedwith the PrC again, the acknowledge messages are loaded into the PrC and the successful status of the key loading ismaintained 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 allintegrated into one chassis. The PrC runs the Windows 7 operating system and provides a user interface for keymanagement 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 AirInterface Encryption. Clear PrC thus offers secure Authentication and Provisioning in Dimetra networks operatingwith 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. TheAuthentication Centre also generates several other keys which are used for secure delivery of key material overthe network.

For authentication, the Authentication Centre distributes the appropriate authentication material to the ZoneControllers. The Zone Controllers then use the authentication material to challenge radios that try to register withthe system.

For air interface encryption, the AuC stores and distributes encryption keys over the network to the appropriateinfrastructure equipment for encrypting and decrypting traffic.

For air interface encryption, the AuC stores and distributes encryption keys over the network to the appropriateinfrastructure equipment for encrypting and decrypting traffic. In order to provide redundancy, additionalAuthentication Centre server running Windows 7 can be set up to operate in a standby mode. The standby server canbe selected to take over operations when the primary server is experiencing a failure. The AuC platform operatewith RAID level 1 (Redundancy) for reliability and availability of provisioned key material on the storage level. Thetwo servers are configured in primary/secondary mode.

Depending on specific configuration, and the AuC server can reside either on the Primary Management Server or ona separate hardware platform.

The Authentication Centre can operate as a separate device, or as Enhanced AuC, which combines the functionalityof both AuC and PrC.

Keys in the AuC are stored in an encrypted form. The AuC uses CryptR 2 device for for encryption and decryptionof the key material. Any attempts to tamper with the tamper-proof hardware causes an alarm to be sent to UnifiedEvent Manager and causes the master key encryption key to be erased.

For more detailed description of Provisioning and Authentication Subsystem, see Authentication and ProvisioningSubsystem manual.

3.1.7 MultiCADI ServerMulti-Computer Aided Dispatch Interface (MultiCADI) is a server that provides an Application ProgrammingInterface (API). This enables third parties to develop application programs that can utilize the facilities providedby the CADI in the system. The API builds upon the CADI API, but provides additional capabilities that are notavailable with the CADI.

3-14 - March 2012

3.1.8 Alias Server

MultiCADI software operates like a CADI client to the CADI server using the single session available whileoperating as a CADI server extending the CADI API functionality with up to 25 simultaneous CADI clients.MultiCADI provides ID range partitioning between CADI clients and user authentication when CADI sessionsare opened.

If there are multiple zones in a Dimetra IP SwMI then a CADI server exists per zone. Hence there can be more thanone MultiCADI in a system, up to a maximum limit of one MultiCADI for each zone/CADI server. In order tosupport command and event forwarding between zones, a communication path between every MultiCADI can beestablished where each MultiCADI communicating with every other MultiCADI in a mesh topology.

MultiCADI is intended to provide additional capabilities for the CADI. It offers the following capabilities thatare not available in the CADI:

• Support of up to 25 concurrent client sessions plus a client of the MultiCADI Server.

• Distribution of system and client events to clients based upon Individual Short Subscriber Identity (ISSIfiltering). As a result, clients can only receive events for ISSIs over which they have control.

• Validation of system and client commands based upon ISSI filtering, so that clients are restricted to sendcommands for ISSIs and GSSIs over which they have control.

• Support of aliasing services.

• Forwarding of designated CADI system events to clients in the home zone of the ISSI associated with anevent.

• Forwarding of designated CADI system commands to the home zone CADI server of the ISSI associatedwith a command.

• Additional validation for DGNA commands to enable a client to ‘DGNA’ a talkgroup into a radio, eventhough the client does not have control over the ISSI of the radio.

• Importing of a home zone map file from the Dimetra IP SwMI in support of the command/event forwarding.

MultiCADI is mandatory when Radio User Assignment/Radio User Identity (RUA/RUI) feature is required. It isthe MultiCADI API that allows third-party applications to access the aliasing services in the Dimetra SwMI.A client application based on the MultiCADI API can then be used to receive specific RUIS events and sendspecific RUIS commands. (For more information on RUA/RUI, refer to the Radio User Assignment/Radio UserIdentity (RUA/RUI) manual.)The Alias Integrated Solution (AIS) is in this release still supported, together with AIScommands and events. For more information on AIS, refer to Alias Integrated Solution Feature Manual.

For more detailed description of MultiCADI Server, see MultiCADI manual.

3.1.8 Alias ServerThe Alias Server processes the logon/off requests from the radio users and the book on/off requests from thethird-party clients. It keeps track of bindings between RUIs and ISSIs, that is which RUI is using which radio, andit handles the configuration of forwarding. Through the MultiCADI API it sends events to the third-party clientsas a result of a logon/off or book on/off. Similarly, it also provides third-party clients with query services such asenabling clients to determine the logged/booked on state of radio users and radios.

3.1.9 Unified Network Services (UNS) ServerThe section describes Unified Network Services (UNS) Server feature.

The Unified Network Services (UNS) Server is a communications exchange system that accepts request for presenceand location information from customer applications through Application Programming Interfaces (APIs) andtransmits the requests to remote radios on the radio networks. The service also receives presence and locationinformation from the remote radio and applies it to APIs for use by the customer applications. The Customer

- March 2012 3-15

System Overview

Enterprise Network (CEN) provides support services and applications that will vary with each implementation. TheUNS monitors the remote devices and provides communication services between the CEN and the radio networks.For Dimetra, the following implementations are available:

• Dimetra Location without Information Assurance (Dimetra Location)

• Dimetra Presence without Information Assurance (Dimetra Presence)

The UNS server is installed as a container on the MultiOS platform, and it is located in the screened network domain.

3.1.10 Network Security SubsystemNetwork Security is concerned with the security and protection of the network against malicious or unintentionalelectronic threats like virus or hacking attacks. It consists of a number of individual features:

• AntiVirus (A/V). Each MSO requires a Core Security Management Server equipped with the appropriateA/V Server software. One CSMS is elevated to be the Primary A/V Server serving the rest of the system bydistributing virus definition files to secondary A/V servers in other MSOs and A/V clients in its own MSO.

• Authentication and Two-Factor Authentication. The authentication server utilizes this database each timea client or FTP client (on the trusted side of the firewall) issues a request to the server as part of the processwhen a user has to be authorized before access is granted. Authentication is handled by the System CSMSthat serves the entire system. The Two-Factor Token based Authentication provided by the RSA ACE/Serverrequires two factors instead of just one: a memorized PIN number and a code generated by a token

• Firewall. Adding perimeter protection to the Dimetra system is achieved by adding a barrier between the“untrusted” network (CEN) and the trusted network (RNI). This barrier is called the Network InterfaceBarrier (NIB). NIB is introduced at the Master Site and the Large Control Sites.

• Monitoring from CEN. Security related alarms can be monitored from within the CEN. Access rights arecontrolled by means of user profiles defined at the CSMS. A RSA® client and a Juniper™ Firewall client areinstalled at the CEN host. All clients are then connected back to the respective CSMS.

3-16 - March 2012

3.1.10 Network Security Subsystem

Figure 3-6 Network Security Subsystem

SecondaryManagement

ServerSecondary

Zone Server

PrimaryManagement

ServerPrimary

Zone Server

MTIG-E1 Server 1

EC

CWR CWR CWR CWR

SecondaryData

Server

NTS

MCC7500NM Client Voice Logging Replay Station AISGW2

To P

AB

X

GP

S

Core LAN Switch 1&2

GGSN 2

GGSN 1Primary Data

Server

Core 1

BTS / Remote Control Zone / Other Zone

E1 - E1 - E1 - E1 - E1 -

E1 - GBN

Customer Network

ICCS GW Router 1

ICCS Switch 1

ICCSFW 1

ICCS GW Router 2

ICCS GW Server ICCS

Switch 2

ICCSFW 2

ICCS GW Router 3

ICCS Switch 3

ICCSFW 3

ICCS GW Router 4

ICCS GW Server ICCS

Switch 4

ICCSFW 4

CENIBFW 2

CENIBFW 1

MTIGFW 1

MTIG-IPServer 1

TerminalServerClient

DMZ Switch 1&2

BorderRouter

BorderRouter

TerminalServer

Mutually exclusive

SecondaryManagement

Server

PrimaryManagement

ServerMTIG-E1 Server 1

EC

CWR CWR CWR CWR

SecondaryData

Server

NTS

MCC7500NM Client Voice Logging Replay Station AISGW2

To P

AB

X

GP

S

Core LAN Switch 1&2

GGSN 2

GGSN 1Primary Data

Server

Core 1

BTS / Remote Control Zone / Other Zone

E1 - E1 - E1 - E1 - E1 -

E1 - GBNE1 - GBNE1 - GBN

Customer NetworkCustomer NetworkCustomer NetworkCustomer NetworkCustomer Network

ICCS GW Router 1

ICCS Switch 1

ICCSFW 1

ICCS GW Router 2

ICCS GW Server ICCS

Switch 2

ICCSFW 2

ICCS GW Router 3

ICCS Switch 3

ICCSFW 3

ICCS GW Router 4

ICCS GW Server ICCS

Switch 4

ICCSFW 4

MTIGFW 1

MTIG-IPServer 1

TerminalServerClient

BorderRouter

BorderRouter

TerminalServer

Mutually exclusive

Core Security Management Server (CSMS)NetScreen-Security Manager (NSM)

- March 2012 3-17

System Overview

3.1.10.1 Core Security Management Server

The Core Security Management Server (CSMS) consists of hardware and software components required to ensurethat only authorized users access the radio network system. The CSMS is required to safely enable use of systeminterfaces for remote service access and remote network management service activities.

The CSMS performs the following functions:

• Authentication of users to ensure secure remote access• Management of A/V for network clients

3.1.10.1.1 Authentication Server and Replica Server

The authentication service can be a single authentication server installed on the System CSMS, which then servesthe entire system.

A second configuration requires another authentication server to be installed on an MSO CSMS. This secondauthentication server is then configured as a replica server. If two authentication servers are installed they togetherensure that there is no single point of failure because the account database is available at both servers due to thereplica functionality. The authentication server at the System CSMS and the replica server exchanges informationallowing the replica server to also serve authentication requests in case the authentication server at the SystemCSMS is unreachable. However, the Terminal Server can solely use the System CSMS for authentication.

3.1.10.2 Customer Enterprise Network Interface Barrier

The Customer Enterprise Network Interface Barrier is a set of hardware and software components providingboundary enforcement and attack detection features to provide supplemental network security protection. The NIBsafely enables use of the system’s defined interfaces for integrated data, network management, computer-aideddispatch, and billing. Deploying NIBs at each connection point between radio system resources and externalnetworks and equipment provides an important and recommended level of security.

It is recommended that one NIB is established for each access point to the radio network. Up to sixNIBs are supported.

For more information on network security, see Network Security.

Basic components of the NIB include a firewall and a DMZ switch. These components are appropriately multipliedwhen the customer takes advantage of the Geographical Redundancy feature.

The following hardware and software components are part of the NIB system:

• Firewall - a Juniper SSG 140 appliance running Juniper ScreenOS Firmware.• Red Hat Enterprise Linux 4 Virtual Machine (VM) - a Firewall Management configuration tool installedon the CSMS.

• Juniper NetScreen-Security Manager - a tool required to properly manage and monitor the firewall.• Network Demilitarized Zone (DMZ) Switch - an switch that provides a distribution point from the firewallto the DMZ.

3.1.11 Network Time Server (NTS)The Network Time Server (NTS) together with the Zone Database Server (ZDS) provide a timing reference to theDimetra system. It acts as a Network Time Protocol (NTP) server providing a UTC time and date reference to all IPconnected system elements (NTP clients) that support the Network Time Protocol (NTP).

The figure below shows the SyncServer S300 with Rubidium oscillator from Symmetricom.

3-18 - March 2012

3.1.12 Terminal Server

Figure 3-7 Network Time Server

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

3.1.12 Terminal ServerOut-of-band management consists of one or more terminal servers. The servers provide interfaces to the core LANswitch on one side and to the modems on another. The LAN interface provides connections to all the serial (console)interfaces of all the devices at the MSO. This connection provides the means to program an IP address in anydevice which in turn allows access to all the other programmable functions. The modems allow for a method todial into the terminal server connected to the MSO LAN. Telnet is supported, as well as connectivity to the serialports of the routers, switches, and servers.

Figure 3-8 In-Reach® Server — LX-4048T Front Panel

3.1.12.1 Remote Analog Access

A feature supported by Dimetra is remote analog access. This allows properly configured PCs to dial into thenetwork and access the Network Management applications through the terminal server and the core LAN switch.

Once the dial up client is granted access to the system through a login and password, the client can launch the zonemanager applications or launch the Web browser to access the Unified Event manager server. Performance ofapplications such as ZoneWatch depends on the amount of bandwidth allocated to the connection.

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

- March 2012 3-19

System Overview

Figure 3-9 Transport Core with E1 Connections

SecondaryManagement

ServerSecondary

Zone Server

PrimaryManagement

ServerPrimary

Zone Server

MTIG-E1 Server 1

EC

CWR CWR CWR CWR

SecondaryData

Server

NTS

MCC7500NM Client Voice Logging Replay Station AISGW1 GW2

To P

AB

X

GP

S

Core LAN Switch 1&2

GGSN 2

GGSN 1Primary Data

Server

E1 - Core 2

E1 - Core 1

BTS / Remote Control Zone / Other Zone

E1 - Core 4

E1 - Core 3

E1 - Core 6

E1 - Core 5

E1 - Exit 2

E1 - Exit 1

E1 - GBN

Customer Network

ICCS GW Router 1

ICCS Switch 1

ICCSFW 1

ICCS GW Router 2

ICCS GW Server ICCS

Switch 2

ICCSFW 2

ICCS GW Router 3

ICCS Switch 3

ICCSFW 3

ICCS GW Router 4

ICCS GW Server ICCS

Switch 4

ICCSFW 4

CENIBFW 2

CENIBFW 1

MTIGFW 1

MTIG-IPServer 1

TerminalServerClient

DMZ Switch 1&2

BorderRouter

BorderRouter

TerminalServer

Mutually exclusive

BTS / Remote Control Zone / Other Zone

E1 - GBNE1 - GBNE1 - GBN

SecondaryManagement

ServerSecondary

Zone Server

PrimaryManagement

ServerPrimary

Zone Server

MTIG-E1 Server 1

EC

SecondaryData

Server

NTSTo P

AB

X

GP

SGGSN 2

GGSN 1Primary Data

Server

Customer NetworkCustomer NetworkCustomer NetworkCustomer NetworkCustomer Network

ICCSFW 1

ICCS GW Server

ICCSFW 2

ICCSFW 3

ICCS GW Server

ICCSFW 4

CENIBFW 2

CENIBFW 1

MTIGFW 1

MTIG-IPServer 1

DMZ Switch 1&2

Mutually exclusive

MCC7500NM Client Voice Logging Replay Station AIS

3-20 - March 2012

3.2 Network Transport Subsystem

Figure 3-10 Transport Core with Ethernet Connections

SecondaryManagement

ServerSecondary

Zone Server

PrimaryManagement

ServerPrimary

Zone Server

MTIG-E1 Server 1

EC

SecondaryData

Server

NTS

GP

S

Core LAN Switch 1&2

GGSN 2

GGSN 1Primary Data

Server

MCC7500NM Client Voice Logging Replay Station AIS

BTSRemote Control Zone

Other Zone

Eth CGE1

E1 - Core 4

Eth -Core 2

Eth CGE2

Eth Core 3

Eth Core 1

ESL - GBN

Customer Network

ICCS GW Router 1

ICCS Switch 1

ICCSFW 1

ICCS GW Router 2

ICCS GW Server ICCS

Switch 2

ICCSFW 2

ICCS GW Router 3

ICCS Switch 3

ICCSFW 3

ICCS GW Router 4

ICCS GW Server ICCS

Switch 4

ICCSFW 4

CENIBFW 2

CENIBFW 1

MTIGFW 1

MTIG-IPServer 1

DMZ Switch 1&2

BorderRouter

BorderRouter

BH Switch 01

BH Switch 02

TerminalServerClient

TerminalServer

Mutually exclusive

To P

AB

X

BTSRemote Control Zone

Other ZoneESL - GBNESL - GBNESL - GBNESL - GBNESL - GBNESL - GBN

SecondaryManagement

ServerSecondary

Zone Server

PrimaryManagement

ServerPrimary

Zone Server

MTIG-E1 Server 1

EC

SecondaryData

Server

NTS

GP

SGGSN 2

GGSN 1Primary Data

Server

Customer NetworkCustomer NetworkCustomer NetworkCustomer NetworkCustomer Network

ICCSFW 1

ICCS GW Server

ICCSFW 2

ICCSFW 3

ICCS GW Server

ICCSFW 4

CENIBFW 2

CENIBFW 1

MTIGFW 1

MTIG-IPServer 1

DMZ Switch 1&2

Mutually exclusive

To P

AB

X

MCC7500 Voice Logging Replay Station AIS

- March 2012 3-21

System Overview

3.2.1 SwitchesThe 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 aNetwork Management system to provide proactive fault management.

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

Figure 3-11 Core LAN switch

3.2.1.2 Control Site LAN Switch

A Control Site LAN switch provides switching between multiple MCC 7500 consoles and NMTs within onecontrol room. Depending on the size of the Control Site and whether it has a redundant site link, one, two orthree switches are used.

3.2.1.3 DMZ LAN Switch

The DMZ switch is required to provide isolation between customer networks and the trunked radio network. Allnetwork security devices connect through this switch.

Also, the DMZ LAN switch provides a redundant screened network for services that need firewall protection, forexample: zone unique ATIA subnets for ATIA Listeners. The goals of a screened network are:

• to protect the feature devices it is hosting• to protect the RNI• to enable the RNI to manage the feature devices

3.2.1.4 FAN-OUT LAN switch

FAN-OUT switch extends the number of Ethernet ports. Specifically:

• they extend the “NM and Dispatch” subnet on the MSO LAN switch which is used to connect colocatedControl Sites at the MSO

• they extend the “Vortex” subnet on the MSO LAN switch• they extend the “ZNM” subnet on the MSO LAN switch

3-22 - March 2012

3.2.1.5 Backhaul Switch

• they extend the ports of the DMZ switch for a large CENIB servicing zones and ATIA hosts to the limit

3.2.1.5 Backhaul Switch

The backhaul LAN switch model is HP 2610 (see Figure 3-11 Core LAN switch). Ethernet links are terminated atthe Mobile Switching Office (MSO) using two backhaul switches. Colocated zones at the MSO share the samebackhaul switches. In Geographical Redundant deployment, there is one backhaul switch in each location.

For more information on the backhaul switch see the Master Site LAN Switch manual.

3.2.1.6 Aggregation Switch

This switch acts as an aggregation core LAN switch in systems with Geographical Redundancy.

Figure 3-12 Aggregation Switch Front View

3.2.2 RoutersThe master site network transport functions in the Dimetra system are provided by S6000 router and GGM 8000gateway. The following functional types are available:

• 3.2.2.1 Gateway Router, page 3-24

• 3.2.2.2 Core Router, page 3-24

• 3.2.2.3 Exit Router, page 3-24

• 3.2.2.4 Border Router, page 3-24

• 3.2.2.5 Peripheral Network (PN) Router, page 3-25

• 3.2.2.6 The Combined Routers, page 3-25

• 3.2.2.7 Gateway GPRS Support Node, page 3-25

Figure 3-13 S6000 Router

Figure 3-14 GGM 8000 Base Unit

- March 2012 3-23

System Overview

3.2.2.1 Gateway Router

The gateway routers provide network isolation and routing of traffic for a number of components on the MSO LANincluding the Zone Controller, consoles, MTIG, and Packet Data Gateway. Any traffic intended for these devices issent to the gateway router then routed to the destination device. Redundant pairs of gateway routers are installed onseparate transitional LANs (TLANs) on the network to provide full redundancy.

Gateway routers are used for devices that require network redundancy and are multicasting beyond their local LAN.Gateway routers provide several benefits for the MSO:

• They provide a single access point or gateway to access the core and exit routers.• They isolate multicast traffic from the various hosts they are servicing.• They provide redundant connections for hosts with redundant interfaces (Zone Controller) or load balancingdevices.

The gateway routers have two 100Base-TX connections to the Core LAN Switch .

3.2.2.2 Core Router

The core routers perform routing of audio, data, control and network management traffic within the zone. Theyprovide control path redundancy and the segregation of network management traffic. The primary router providesthe necessary services to the sites while the secondary serves as the standby router.

The system requires a minimum of two core routers for 1:1 redundancy. Each core router has two separate LANconnections to the Ethernet switch. Each core router is capable of supporting any combination of up to 250 channelsand dispatch sites. Two core routers are added to the network for every additional 250 devices up to a limit of 700RF channels/dispatch sites in the zone. The core router can support both E1 based WAN and Ethernet based WAN.

3.2.2.3 Exit Router

Exit routers handle traffic to the interzone links. Exit routers also provide high speed Intra-MSO connectivitybetween zone cores (up to 3 zones) via the third Ethernet port. For more information turn to 2.2.3 Multi-LANSharing, page 2-9.

There are two exit routers in each LAN Share. The exit routers serve two primary functions in the system:

• Maintain the list of all active rendezvous points and the group prefixes served by each.• Route inter-zone and intra-zone traffic.

Exit routers with Ethernet WAN connectivity are deployed in legacy zone core (E1–based zone). Eth-exit routers arerequired to connect an E1–based zone to an Ethernet-based zone using Ethernet inter-zone links.

The exit router uses dynamic routes to deploy packets among its multiple connections on both the LAN and WANinterfaces. The packets destined for the control Ethernet interfaces on the Zone Controller, as well as the packetsfor network management, are routed through the Transitional LAN (TLAN) ports of the core LAN switch usingdynamic routes.

All routers supporting Multicast traffic now support the use of Static RP files. This eliminates the need for the Exitrouters to act as BSRs (bootstrap routers) during normal system operation.

The exit router can support both E1 based WAN and Ethernet based WAN.

3.2.2.4 Border Router

Border Routers are managed under the same conditions as the PN routers and handles the interface to the CustomerEnterprise Network (CEN). They connect to the Peripheral Network (PN) on one site and the CEN on the othersite. One or more Border Routers can be implemented at the CEN interface, however a redundant configuration isnot part of the baseline.

In general, the Border Router can be any type of router as long as it supports both the Border Gateway Protocol (BGP)to the Peripheral Network Router, IPinIP tunneling for PDS, and a Network Address Translation (NAT) interface.

3-24 - March 2012

3.2.2.5 Peripheral Network (PN) Router

3.2.2.5 Peripheral Network (PN) Router

The Peripheral Network (PN) Router refers to a router that forms a DeMilitarized Zone (DMZ) network forCustomer Interfacing and is independent from Dimetra and Customer IP domains. The PN router connects toGateway Routers, Control Sites, Customer Interface Routers (Border Routers) and to other PN routers.

Routers located in the DMZ are supported by the Router Manager and it is thus necessary to configure the PNrouters in the Router Manager in order to support these devices. However, this feature is only supported whennetwork security is not deployed.

The PN routers provide 1:1 redundancy at each geographical redundant Location, which may be for both singlelinks and dual links. Furthermore the PN supports redundant PN/DMZ connections and router redundancy toother MSOs and control sites.

For more detailed description of Network Transport Subsystem, see Network Transport Subsystem manual.

The Peripheral Network Router only supports E1-based WAN.

3.2.2.6 The Combined Routers

For Ethernet Site Links based systems we have one pair of Core/Gateway Routers (Eth-CG) or Core/Gateway/ExitRouters (Eth-CGE) deployed in the system.

Combined Eth-CG and Eth-CGE routers are supported to provide termination for Ethernet links to RF sites,remote control sites, and inter-MSO links. Combined routers are deployed in pairs. In a Geographical Redundantconfiguration each router is placed in a different geographical location.

For increased capacity additional core routers can be added.

For more detailed description of routers in Ethernet Site Links solution, see Ethernet Site Links manual and S6000Router manual.

3.2.2.7 Gateway GPRS Support Node

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

3.2.3 CWR Patch PanelThe 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-redundantE1 links between the two routers. Each pair of CWR core or exit routers is connected to a CWR patch panel viahigh-density E1 ports. The CWR patch panel’s RJ-48C connectors provide the connection to the E1 network. EachCWR 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 totalof up to 24 relays for each CWR patch panel. Core and exit routers are connected via the CWR patchpanel in pairs of CWR peers:

– The left hand set of high-density E1 connectors on the CWR patch panel attaches to the two 12-portE1 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 E1modules 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 redundancyand failover protection.

- March 2012 3-25

System Overview

• 24 RJ48-C connectors, each of which supports channelized connectivity at E1 line rates. These connectorsprovide the direct connections to the site and interzone links.

Figure 3-15 CWR Patch Panel

3.3 Remote SitesThe following describes the different types of remote sites supported in the Dimetra system:

• 3.3.1 Base Transceiver Station (BTS), page 3-26• 3.3.2 Control Sites, page 3-32

3.3.1 Base Transceiver Station (BTS)A Base Station serves as the Radio Frequency (RF) interface between the system infrastructure and the radios. BaseStations 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

3-26 - March 2012

3.3.1.1 MTS LiTE

• DOOR alarm - connected to the SC

All these alarms and controls are connected to the Integrated Alarm Card (IAC) which is internal part of SiteController (SC).

3.3.1.1 MTS LiTE

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

Figure 3-16 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). Theduplexer enables a duplexed Receive/Transmit function on one antenna, which further reduces the total count onantennas 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 outdooruse in larger systems. For additional capacity, two MTS 1s can be connected to work in a dual configuration foradditional capacity and resilience. The MTS 1 enclosure is dust tight and also protects against other environmentalelements, such as water. The MTS 1 provides up to 4 channels in a single cabinet or up to 8 channels in a dualMTS 1 configuration. It is available in the 380 - 470 MHz frequency band. A typical MTS 1 site configurationincludes four major functional components:

• Base Radio• Site Controller (SC)• Duplexer with Preselector path• Power Supply Unit

- March 2012 3-27

System Overview

The duplexer enables a duplexed Receive/Transmit function on one antenna, which further reduces the total counton antennas per site. The MTS 1 comes with several optional accessory kits such as solar shield for sun heatprotection (for outdoor use).

Figure 3-17 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 coolingfans. All modules can easily be accessed through the cabinet front door. Due to its small size a complete MTS 2cabinet can easily be fitted into a 19" outdoor enclosure with heat exchanger. Note that the standard cabinet has airconvection holes so that it is not environmentally protected against water or heavy dust.

3-28 - March 2012

3.3.1.4 MTS 4

Figure 3-18 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 distributesup to three Receive antennas to the base radios (BRs). The duplexer enables a duplexed Receive/Transmit functionon one antenna, which further reduces the total count on antennas per site. The hybrid combiner is a wide bandcomponent 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 donot require any modification of the antenna installation. The antenna installation can be re used without any changeand 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 32channels 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

- March 2012 3-29

System Overview

Figure 3-19 MTS 4

A Radio Frequency Distribution System (RFDS) combines up to eight transmit channels onto just one antenna anddistributes up to three receive antennas to multiple base radios. Duplexers enable a duplexed Receive/Transmitfunction, which further reduces the total count on antennas per site. For non-duplexed operation the MTS 4 alsocomes optionally with a Tx-postfilter that allows sufficient space for up to three preselectors. This configurationsupports 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 canbe added. An MTS 4 card cage with Base Radios power supply and SC is identical to an MTS 2 with the filterand 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 toeach base station. If one link is broken the other link is able to carry the traffic to the base station. The secondarypurpose is to reduce the cost of leased lines by allowing base stations to be connected in a ring structure. Whenoperating in a ring structure it is possible to connect base stations by microwave links, which is normally cheaperthan using leased lines from a Ground Based Network (GBN) operator. Redundant Base Station Site Link featureincludes 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. Whencommunications to the MSO are not available, the SC is also able to perform local site trunking operation. TheSC provides connection of either an X.21, E1 or Ethernet link to the MSO. The SC terminates the permanentvirtual circuit (PVC) which is originated at the core router at the MSO, and distributes control, voice, and networkmanagement traffic to the base radios through a 10Base-2 Ethernet bus.

3-30 - March 2012

3.3.1.7 Base Radio

Figure 3-20 Site Controller (SC)

A second SC can be installed at the BTS site to provide active/standby redundancy. Redundant Site Controllersare 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 providefrequency reference signaling to the base radios. The SC also includes an internal GPS receiver which connects toa GPS antenna through an RF feeder to provide timing reference. If redundant SCs are installed at the site, bothSCs require a separate GPS antenna connection. If NTS (Network Time Server) is present, it can be used as asecondary frequency reference

A logical control path and logical manager path are maintained between the BTS site and the MSO. The controlpath delivers control traffic between the BTS site and the Zone Controller. The manager path delivers networkmanagement traffic between the BTS site and the network management servers.

The SC software is loaded through the Software Download (SWDL) application. The configuration parameters forthe SC are defined both through the Zone Configuration Manager and through Dimetra™ BTS (Base TransceiverStation) 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 providesfour inbound and outbound TDMA logical channels. Up to four control capable channels can be configured in theBTS. These four channels are spanned across the first TDMA slot of each of the four base radios installed inthe first BTS rack.

The base radio supports receiver diversity. Receiver diversity provides increased talkback range by the installationof two or three receiver modules in the base radio which are tuned to the same inbound frequency. Two receiverdiversity is standard in a BTS base radio. The three receiver diversity option requires an additional receivermulticoupler 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 BTSplatform that has been purchased. The base radio provides 15 or 25 Watts (adjustable) of power output to the antennasystem. 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 correspondingreceive (uplink) frequency at 380,500 MHz.

- March 2012 3-31

System Overview

Figure 3-21 BTS Base Radio

The base station is able to provide air interface encryption by applying a cipher key and a user-defined offset variableto the inbound/outbound coded traffic. To provision the base station for encryption, the base radio is loaded locallywith a secret infrastructure key through a Key Variable Loader (KVL). This infrastructure key is used to decryptcipher keys which are delivered over the network. The base radio uses the appropriate cipher key (SCK, DCK, orCCK) to encrypt outbound traffic and decrypt inbound traffic.

The BTS base station software is loaded through the Software Download (SWDL) application. This applicationcan load software to the entire BTS site over the network, or can load software directly to an isolated base radiothrough a direct connection. The configuration parameters for the BTS base station are defined both through theZone 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 twoindependent -48VDC inputs and has a number of breaker switches to switch power on and off for individualcomponents in the rack. The breaker panel is located at the top of the BTS rack.

3.3.2 Control SitesControl sites are the locations where the users of the system (dispatchers and network managers) access the dispatchconsoles and/or the network management terminals (NMTs). A control site can include a variety of equipmentto serve its particular purpose in the system. It may have just dispatch consoles or NMTs or it may have bothdepending on the requirements.

3.3.2.1 Dispatch Subsystem

The dispatch subsystem can be either the MCC 7500 dispatch subsystem or the MCC 7500S secure consolesolution. The MCC dispatch subsystem includes all the equipment necessary to support the dispatch consoles. Thedispatch consoles can be located at the MSO or can be remotely located at a control site. The figure below showsthe components in the dispatch subsystem.

The equipment consists of the MCC 7500 Dispatch Console (and associated peripheral hardware), the MCC7500 Archiving Interface Server (AIS) (and the associated logging recorder and replay station), and the AnalogConventional Channel Gateway (CCGW) (also known as the conventional base station interface).

In addition, Active Directory Domain Controllers might be needed to support Domain Name Server (DNS) andActive Directory services for the MCC 7500 Dispatch Consoles.

3-32 - March 2012

3.3.2.1.1 Dispatch Console PC

An optional Discreet Listening PC and a replay station may be attached to the AIS.

Figure 3-22 Dispatch Subsystem

The MCC 7500 Dispatch Console is Motorola’s high-tier radio dispatch console system. A console dispatchsubsystem consists of the following components:

• A Motorola-certified Dispatch Console PC

• Accessories, such as headsets, speakers, desk microphone and a foot switch.

• A logging system. (The Archiving Interface Server (AIS) and the associated logging recorder and replaystation)

• 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 packetprotocols for passing call control data and call audio through the system. The following figure shows a high-leveldiagram of how the MCC 7500 equipment fits into the system.

Figure 3-23 MCC 7500 Dispatch Console Subsystem

3.3.2.1.1 Dispatch Console PC

Each operator position in the dispatch centre consists of a Motorola-certified personal computer equipped with akeyboard and a mouse. The PC processor unit is an HP Z200 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.

- March 2012 3-33

System Overview

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 multiplespeakers 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 andgooseneck GN 30E.

Footswitch

The Dispatch Console PC can support a single footswitch with one pedal. The pedal controls the General Transmitfeature.

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 whenan emergency call is received.

The Emergency Beacon feature is implemented as the set of green/yellow/red control lights and the buzzerserved by the dedicated application. It is installed on the Dispatch Console PC. The hardware is connected tothe computer via USB.

Figure 3-24 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 fromselected talkgroups/channels in a radio system. These recordings are archived for future playback and use byauthorized users/administrators.

3-34 - March 2012

3.3.2.1.3 Logging System

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 orany 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 bythe replay station.

• The logging system has replay stations that are permissions-based, allowing users to only listen toappropriate 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 andreplay stations.

There are three hardware devices within a logging system:

• MCC 7500 Archiving Interface Server• Logging Recorder• Replay Station

The MCC 7500 Archiving Interface Server provides an interface between Motorola’s radio system and the 3rd partylogging solution hardware which allows audio transmissions and radio system events to be recorded togetherwith associated call data.

The MCC 7500 Archiving Interface Server monitors selected group resources (channels/talkgroups) and individualresources (radios, consoles) passes call-control information and audio to the recording device via the LAN. Therecording device utilizes a 100 Mb Ethernet port to communicate with the MCC 7500 Archiving Interface Serverand records this information on permanent or transferable media.

The 3rd party logging solution provides a GUI called AIS Administrator that allows an administrator to choosewhich 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 thatoccurred on the radio system, choose the desired call they wish to review, and play back the audio for that callthrough a 3rd party logging replay solution. The 3rd party logging solution reconstructs the playback audio fromthe vocoded samples that had been sent to the logging subsystem when the call occurred ensuring that the audioquality 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. Thelogging 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 resourcethat the user wants to record to the logging subsystem. The call control information passed to the logging subsystemincludes 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 islogged 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 ProtocolProcessor licensed to operate with the Motorola MCC 7500 Archiving Interface Server and requires no directinteraction 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/channelson specified transferable media.

- March 2012 3-35

System Overview

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 replaystation. 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 startingtime and duration of transmission. The replay station software also allows the user to listen to audio call recordingsto 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 usedwith MCC 7500 Archiving Interface Servers. This provides the user with a complete view of everything beingrecorded from a single point.

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 theDimetra system and the conventional system. It allows working with and patching with conventional channels thusproviding an easier transition period when going from an existing system to a Dimetra system.

Figure 3-25 GGM 8000 used for CCGW

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

Figure 3-26 Patching with a Conventional System

3-36 - March 2012

3.3.2.1.5 MCC7500 Dispatch Communications Server

3.3.2.1.5 MCC7500 Dispatch Communications Server

MCC 7500 Dispatch Communications Server is designed to meet the demands of customers who want to implementor already have implemented their own custom-developed non-Motorola control room.

Dispatch Communications Server subsystem provides the interface between the MCC 7500 dispatch consolesubsystem and 3rd party applications and systems in a Large Control site. By means of the Console RemoteAPI Manager Service (CRAM), customers have full access to the same feature set as provided by MCC 7500dispatch consoles.

From a system viewpoint the Dispatch Communications Server subsystem:

• Provides an interface to 3rd party control rooms, also known as Integrated Command and Control Systems(ICCS)

• Provides audio in digital form (PCM A-law)

• Provides access to Motorola MCC 7500 Console Dispatch Application Programming Interface

The Dispatch Communications Server subsystem is composed of the following hardware elements::

• Dispatch Communications Server (HP ProLiant Dl360 G7)

• DCS LAN Switches

• DCS Routers

• DCS Firewall

• Terminal Server

• KVM Switch

If required, network security components (like firewall, CSMS) can be added.

3.3.2.1.6 Secure Dispatch System (End-to-End Encryption (E2EE))

E2EE MCC7500S console solution is developed to provide end to end encrypted communication between radiosand consoles. As illustrated in the figure below, the E2EE MCC7500S console solution is composed of threemain 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.

- March 2012 3-37

System Overview

Figure 3-27 MCC 7500S Dispatch Console

Secure ICCS Gateway

The Secure ICCS (Integrated Command and Control System) Gateway Subsystem provides the interface betweenthe MCC 7500S Dispatch Console Subsystem and 3rd party applications and systems in a Large Control site. Bymeans of the Console Remote API Manager Service (CRAM), customers have full access to the same feature set asprovided by MCC 7500S dispatch consoles.

Secure ICCS supports End-to-End encryption, which allows secure communication between ICCS Gateway PCand the radio units in the field. Encryption/decryption is made in the endpoints, so communication remains secureall the way.

The Secure ICCS MCC 7500S module consists of three physical components; the ICCS Gateway PC, the AudioModule, and a CryptR device.

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-34withthe 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. Itconsists of the following servers:

• MCC 7500 Archiving Interface Server (AIS)

• Voice Logger

• Tape Storage

3-38 - March 2012

3.3.2.2 Types of Control Site

E2EE Discreet Listening ICCS Gateway

With the Discreet Listening ICCS Gateway feature it is possible to create a Discreet Listening function in theICCS. The Discreet Listening ICCS Gateway enables listening to both Clear calls and encrypted calls throughthe following interfaces:

• Console Interface• Clear Voice Interface

Figure 3-28 E2EE Discreet Listening ICCS Gateway

3.3.2.2 Types of Control Site

The control site components can, if required, be located at an MSO, but are usually located at a Large Controlsite. Below, two types of control site are described:

• 3.3.2.2.1 Small Control Site, page 3-39• 3.3.2.2.2 Large Control Site, page 3-40

3.3.2.2.1 Small Control Site

A Small Control Site uses GGM 8000 as Control Site Router and can use a Conventional Channel Gateway and acore LAN switch. If needed, the site can support patching with four conventional channels.

- March 2012 3-39

System Overview

Besides the fixed 10/100Mb Ethernet port the GGM 8000 needs to be equipped with the following modules:

• WAN module for interfacing to Ground Base Network

• Optional second WAN module for redundant WAN link interfacing to Ground Base Network

• Optional 4-Wire E&M module for conventional channel patching

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.

Figure 3-29 Small Control Site

3.3.2.2.2 Large Control Site

A Large Control Site uses GGM 8000 gateway and S6000 router as Control Site Routers and can use a ConventionalChannel Gateway and a core LAN switch. If needed, the site can support patching with four conventional channels.

Besides the fixed Ethernet ports the Control Site Router needs to be equipped with the following modules:

• E1 WAN module for interfacing to Ground Base Network

• Optional second WAN module for redundant WAN link interfacing to Ground Base Network

The GGM 8000 and the S6000 further supports different dual site links configuration:

• Dual links by means of two GGM 8000 gateways. Each router has a link from a single WAN module. Thelinks support Non MFR only

• Dual links by means of a single GGM 8000 gateway but having two WAN modules, one per link. Thelinks support Non MFR only

• Dual links by means of two S6000 routers. Each router has a link from a single WAN module. The linkssupport both Non MFR and MFR

3-40 - March 2012

3.3.2.2.2 Large Control Site

• Dual links by means of a single S6000 router but having two WAN modules, one per link. The links supportboth Non MFR and MFR

• When running dual links using two routers, then 2 or 3 LAN switches are required (applied for both S6000and GGM 8000)

• When running dual links using one router, then 1, 2 or 3 LAN switches are required (applied for bothS6000 and GGM 8000)

The figures below show how a large sized MCC 7500 based Large Control site may be arranged. From a networkingperspective the large control site is just a bigger version of a medium sized control site supporting even moreconsoles due to the addition of a third core LAN switch . Please note that the Domain Controllers (DC) are optional.

Figure 3-30 Large Control Site: Non Redundant

- March 2012 3-41

System Overview

Figure 3-31 Large Control Site: Redundant

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

3.4.1 MTH800Motorola’s MTH800 is built on the experiences of the earlier released MTH650 and is further enhanced with anew “engine” and with an extensive range of new features, functions and benefits and offers as such a wide rangeof capabilities including, state of the art end-to-end encryption (E2E), a high-resolution color display as well as arevolutionary Automatic Personal Location Service (APLS) based on GPS.

From a hardware point of view the MTH800 has the same Ergonomics and form factor design as known from theMTH650, e.g. a rugged magnesium shell and rubber overmould.

With a resolution of 130 x 130 pixels and over 65,000 colors, the display provides accurate reproduction of facesand other images. Coupled with the latest backlighting technologies, the display provides maximum imagedefinition in a wide range of lighting conditions.

To harness the power of MTH800 a new easy to use graphical user interface is included including assignableshortcuts to menu items, more that 3000 talk groups as well as a unified phone book with 1000 phone numbersand 1000 private call numbers.

The MTH800 comes with a full single chip, low current consumption and high sensitivity - GPS receiver built intothe terminal. Furthermore, the MTH800 uses a new patented GPS antenna integrated into the TETRA antenna toensure optimal coverage. The solution includes a full terminal resident software application providing control ofall GPS parameters over the air.

While compact and lightweight the MTH800 introduces full E2E encryption with tamper protection, a choice ofalgorithms and Over-the-Air-Keying using Motorola’s proven Key Management Facilities. Dependant on securityrequirements the MTH800 can be factory fitted with E2E encryption OR it can be retrofitted and provisionedin-country at a later date.

3-42 - March 2012

3.4.2 MTP850

Figure 3-32 MTH800 Radio

3.4.2 MTP850The MTP850 is the latest available TETRA Hand portable terminal from Motorola. The terminal shares Softwareplatform with the MTH800, and as such their features are aligned e.g. in terms of End-to-End Encryption (E2E),GPS Location Services, WAP interface and usages of Multi Slot Packet Data. The MTP850’s Man MachineInterface is also aligned with the MTH800, so users of the MTH800 recognize the same menu easy-to-handlestructure as of the MTH800, and are able to benefit from the same high quality color display. From a form factorpoint of view the MTP850 comes with a new Ergonomic and form factor design, which provides both smaller sizeand lower weight compared to the MTH800. A Remote Speaker Microphone (RSM) connector is located on the sideof the terminal. The MTP850 has with a choice of two battery sizes, both of which are designed as one-piece unit toensure the firm attachment of the battery to the terminal and to allow one-handed change of battery.

- March 2012 3-43

System Overview

Figure 3-33 MTP850 Radio

3.4.3 MTP850 SIncorporating all of the features of the field proven MTP850, this terminal incorporates an advanced Man Downsensor for exceptional user safety together with a new side connector for increased ruggedness. Providing higherpower will increase range and in-building performance, and so Motorola has added Class 3L (1.8W) poweroutput option. Taken together with high receive sensitivity the MTP850 S has the capability for maintainingcommunications in the most demanding situations.

Figure 3-34 MTP850 S Radio

3-44 - March 2012

3.4.4 MTP830 S

3.4.4 MTP830 SMotorola’s MTP830 S TETRA portable radio is the ideal choice when working in extreme conditions. This radiodelivers premium performance, whilst combining louder audio and enhanced erogonomics with simplified controls,allowing fire fighters and other first responders to focus on the task at hand.

Figure 3-35 MTP 830 S Radio

3.4.5 MTP850Ex (ATEX)The MTP850Ex provides high quality audio communications with comprehensive class leading standards in ATEXspecifications allowing users to operate in environments where there is potentially explosive dust or gas. The radio isapproved to ATEX and IEC-Ex standards whilst maintaining high quality of speech in noisy environments, due to theVoice Compression Technology. The MTP850 Ex uses a coding technique called ACELP (Algebraic Code ExcitedLinear Prediction) and enables the Voice Compression technology to reduce the number of bits per second whilemaintaining the voice at an acceptable quality level. The MTP850Ex also has an integrated GPS for user locationalong with a “Man Down” alert, which triggers an emergency if a radio user remains motionless for a set period.

The MTP850Ex has a strong rugged design for optimum reliability in harsh conditions and its simplified keypadwith large buttons makes it easy to use with gloves. The integrated WAP browser and Multi-slot packet data furtherenables rapid access to critical information. Applications are further enhanced with ability to have simultaneousShort data Service (SDS) and Multi-Slot packet data services via TNP1 protocol.

- March 2012 3-45

System Overview

Figure 3-36 MTP850Ex Radio

3.4.6 MTP810Ex (ATEX)The MTP810Ex provides high quality audio communications with comprehensive class leading standards in ATEXspecifications allowing users to operate in environments where there is potentially explosive dust or gas. The radiois approved to ATEX and IEC-Ex standards whilst maintaining high quality of speech in noisy environments, due tothe DCR (Direct Conversion) technology. The main concept of this technology is down converting of the RF signaldirectly into a base band signal, skipping the intermediate stage of IF signal. The MTP 810Ex also has a strongrugged design for optimum reliability in harsh conditions and its simplified keypad with large buttons makes iteasy to use with gloves. The integrated WAP browser and Multi-slot packet data enables rapid access to criticalinformation. Applications are further enhanced with ability to have simultaneous Short data Service (SDS) andMulti-Slot packet data services via TNP1 protocol. Finally, the MTP850Ex has an integrated GPS for user locationalong with a “Man Down” alert, which triggers an emergency if a radio user remains motionless for a set period.

3-46 - March 2012

3.4.7 CEP400

Figure 3-37 MTP810Ex Radio

3.4.7 CEP400Motorola’s CEP 400 TETRA portable delivers the high performance and dependability required for enhancedworkforce productivity and assured user safety. Leveraging the best features of a two-way radio and a cellularphone, the lightweight and robust CEP400 has been engineered to ensure loud and clear communications even inhigh noise work environments.

Figure 3-38 CEP400 Radio

- March 2012 3-47

System Overview

3.4.8 TCR1000The Motorola Discreet TCR1000 secures communications in surveillance covert type operations.

Key features of TCR1000:

• Secure Communication for safety and protection of information

• Air Interface Encryption

• End-End Encryption

• Whisper mode for discrete use

• Integrated GPS option that allows users to be located in need of assistance

• Wide range of covert accessories to give its users flexibility in the way the radio can be worn

• Connection to extension battery for increased operational life

• Uses the same standard battery as cellular handsets

• CPS-Lite facility for changing the talk groups with a TETRA PDA

• Unique body worn double-loop antenna option increases range

• 1W, Class 4 Tx Power

Figure 3-39 TCR1000

3.4.9 MTM800 EnhancedThe MTM800 Enhanced has been developed for the Public Safety, industry and transport users. It is a versatileproduct that can be installed in remote mount, desk, dash mount or on a motorcycle. The introduction of theMTM800 Enhanced has been developed with the latest platform, common with the TETRA portable terminalsMTH800 and MTP850.

It enables features such as Multi Slot Packed Data (MSPD) or GPS. It has a large memory capacity, ready forfuture software upgrades and increase use of data. As optional modules Integrated GPS receiver and End-to-EndEncryption (E2E).

The MTM800 Enhanced is otherwise similar to MTM 800.

Figure 3-40 MTM800 Enhanced Radio

3-48 - March 2012

3.4.10 MTM5400

3.4.10 MTM5400The TEDS Ready MTM5400 TETRA DMO Gateway/Repeater mobile radio provides extended coverage,exceptional audio performance and high-speed data connectivity to address current and future critical communicationneeds of professional users. From advanced Over The Air terminal management capability, to integrated DMOrepeater-gateway and high-speed USB 2.0 interfacing, the rugged MTM5400 TETRA DMO Gateway/Repeatercombines a wide range of advanced features for enhanced usability and improved safety.

Figure 3-41 MTM 5400 Radio

3.4.11 CM5000The CM5000 is an advanced TETRA mobile radio terminal which has been designed using the latest digital radiocommunication and micro-computer technology. It enhances TETRA radio performance and usability in locationswhere coverage is limited.

With its full data capability and proven Motorola user interface, the CM5000 combines three modes of operation – aTETRA Mobile, a DMO Gateway and a DMO Repeater. When configured in ‘Gateway’ mode, it acts as a bridgebetween the trunked radio network and TETRA radios operating outside the network in Direct Mode (DMO). Whenconfigured in “Repeater” mode, it extends the range of DMO communication by receiving and re-broadcastingcommunications from other DMO users.

The following features are provided with the CM5000:

• A large screen full dot matrix color display

• High reliability design and production by adoption of surface mount technology and LSI devices

• Its sophisticated high performance is micro-computer controlled

• It has user friendly controls with audio and visual confidence indicators

• Multiple facilities and options, such as:

– Status Messages

– Emergency Call

– Multi-Site Roaming

– Serial Communication Port for PC Connection

– Data Communication Air Interface

– Serial Data Port

– GPS Receiver Connection

- March 2012 3-49

System Overview

Figure 3-42 CM5000

3.4.12 MTC100 PDAThe MTC100 is a robust TETRA Personal Digital Assistant (PDA) with wireless 802.11b/g and Bluetooth 1.1 &1.2 connectivity. It has high sensitivity GPS receiver. It is operated through four front and two side configurablebuttons, central navigation button, joy stick and the color touch screen. The PDA has an SD card slot for externalmemory cards and IrDA (infra red) port. The MTC100 supports synchronization of data between PC and TETRAPDA (Microsoft® Active Sync®)

The following software is provided with the MTC100 TETRA PDA:

• Windows Mobile® 5.0

• Office Mobile (Word Mobile, Excel Mobile, PowerPoint Mobile)

• Calculator

• Internet Explorer Mobile

• Outlook® Mobile (Outlook Calendar, Outlook Contacts, Outlook Messaging, Tasks, Notes Application,Spell Checker)

• Pictures & Videos (Image & Video viewer)

• Terminal Services Client

• Voice Recorder

• Windows Media® Player 10.x Mobile

• Motorola Tetra Explorer

3-50 - March 2012

3.4.12 MTC100 PDA

Figure 3-43 MTC100 PDA

- March 2012 3-51

4 Dimetra IP Data ManagementTopics Covered in this Chapter

• Radio System Databases• Server Failure Impacts

4.1 Radio System DatabasesThe system uses a variety of databases to provide communication services to individual users. Configuration datafor users, talkgroups, and the system infrastructure are stored in these databases. Other types of information storedinclude system performance and fault data. The databases are the organizing element that transforms the computersand 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 InformationThe following describes the individual databases, the relationship between the databases, and the way the systemuses 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 ControlChannels (ACC), interzone control paths, and user security information for the cluster. Group and Unit ID homezone assignments are also made at the UCS level. The UCS provides the benefit of a single point of entry withautomatic propagation of data throughout the cluster to all the zones in the cluster. Each zone database in thecluster receives all of the information entered at the UCS, allowing the zone databases to be used for restoringcluster-level data to the UCS if necessary.

A UCS API is available, allowing a customer-supplied provisioning system to interface with the User ConfigurationServers in all the clusters. This allows a centralized provisioning system to provide system wide configurationcapability to all the User Configuration Servers throughout the system.

- March 2012 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, telephoneconnections, data servers, console sites, archive interface servers, alias server 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 groupmembers whose configuration information is stored in the HLR. Groups and Individuals are treated differently formobility purposes and therefore hosted by separate processes in the Zone Controller. These are called GHLRand IHLR respectively. The location information in the HLR is continually updated as radios are turned on andoff, 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 inthe zone. The VLR stores access configuration information for both individuals and groups along with their currentsite 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 sameinfrastructure data that is found in the zone database. The primary reason that the local database exists is to allowcontinued communications within a zone in the case of a failure resulting in a Zone Controller reset while the zonedatabase is not available. The local database allows the controller to provide wide area services in default mode untilthe 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 radiocommands monitoring functions available are Radio Check, Snapshot, Zone Status and events for EmergencyAlarm. All monitoring 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 seewhich sites get the most use, how and when radio users access the system, and which talkgroups are involvedin a particular call.

The affiliation database resides on the Air Traffic Router (ATR) server. The ATR server receives radio call traffic inraw data packet format from the Zone Controller. The raw data packets are translated into Air Traffic InformationAccess (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 deaffiliationinformation for each radio user in a particular zone. The affiliation database collects this information and providesupdates to PRNM management applications, such as Affiliation Display.

4.1.1.8 Radio User Information

Individual user permissions are provisioned through profiles that define characteristics common to a group ofusers. When a new user is entered into the system, the user is assigned an appropriate profile or profiles. Onlythe 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 collectionof talkgroups.

4-2 - March 2012

4.1.2 Fault Management Information

This information is initially entered into the User Configuration Manager (UCM) as a single point of entry toavoid duplicating effort or generating mismatched databases. Afterwards, the information is replicated to eachzone database.

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

4.1.3 Statistical DataThe system organizes statistical information into reports.

The data is collected based on groups specified by the administrator. The groups are based on object type, timeinterval, and number of intervals. For example, a collection group may be defined to collect statistics abouttalkgroups. A single collection group is not, however, capable of collecting statistics about both sites and zones – twoseparate collection groups would be needed. Also, a collection group collects statistics for a single collection interval.

Two types of reports are supported: dynamic and historical. Dynamic reports are updated for each interval selectedby the user. Historical reports are static. Once the historical report is generated, it does not change.

4.1.3.1 System Statistics Server Database

Statistics concerning resource usage and allocation are kept in the SSS database. As an administrator, you usereports generated from system statistics to make decisions concerning resource usage and allocation.

The SSS Database is used in conjunction with the system reporting tools to provide Historical reports. Historicalreports are static and provide a snapshot of system usage for a specified time interval. Historical reports canbe manually or automatically generated.

Statistics are kept for sites, channels, zones, talkgroups, and users. Statistics are kept on call duration, busies, andcall counts.

4.1.3.2 Zone Statistics Server Database

The Air Traffic Router (ATR) takes the Air Traffic Information Access (ATIA) stream and generate flat files with theinformation. The Zone Statistics Server (ZSS) database pulls this information and parses these records to the ReportPlayers, which run on the Network Management client.

The zone-wide statistical information in the ZSS Database summarizes call processing traffic. The reports generatedcan be one of two types:

• Historical: these are static reports that cover a specific time interval. The amount of historical informationthat 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 selectedby the user.

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

- March 2012 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 managementas described in the following list:

• Group and Unit ID Home Zone assignments are madeat the UCS level.

• Security information and other cluster-level parametersare set in the UCS.

• Radios, talkgroups, critical sites, Adjacent ControlChannels (ACC), and Interzone Control Path IDs areconfigured in the UCS.

Zone Database Zone Database Server All infrastructure configuration information for a specificzone, along with a copy of the user configuration informationreplicated from the UCS.

RCM Database Air Traffic Router The Radio Control Manager database carries informationthat allows the user to perform several monitoring andcontrol functions.

SystemStatistics ServerDatabase

System Statistical Server Used in conjunction with Historical Reports Player togenerate cluster wide reports. A network management clientcan collect historical reports from all the clusters in thesystem.

Zone Statistics ServerDatabase

Zone Statistical Server Used in conjunction with Historical Reports Player togenerate zone-wide reports.

Zone Local Database Zone Controller A copy of the local infrastructure database is downloadedto the Zone Controller once the ZDS is populated with thehardware configuration records of the zone. This copy of thelocal infrastructure database is stored in the Zone Controllerto provide wide area communication in cases where theZone Controller needs to re-initialize without having accessto the ZDS.

Affiliation Database Air Traffic Router The affiliation database keeps track of the sites to which theindividual radios are registered and the talkgroups to whichthey are affiliated.

4.1.5 Hierarchical ViewThe table below shows the hierarchical listing of servers.

Table 4-2 Hierarchical Listing of Servers Hosting Databases

Cluster-Level Servers Zone-Level Servers• User Configuration Server (UCS)

• System Statistics Server (SSS)

• Unified Event Manager Server (UEM)

• Zone Controller (ZC)

• Zone Database Server (ZDS)

• Zone Statistics Server (ZSS)

• Unified Event Manager Server (UEM)

• Air Traffic Router (ATR)

4-4 - March 2012

4.1.6 Server Interaction

4.1.6 Server InteractionAs with many components of the Dimetra IP system, the system servers are highly interdependent; they rely heavilyon 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 isnumbered. See the table below the figure for definitions of each of the numbered interactions.

Figure 4-1 Server Interactions Defined

See below the descriptions of the above interactions.

Table 4-3 Server Interactions

Interaction Description

1

Replication/synchronization of database records occurs between the UserConfiguration Database (UCS) and each Zone Database. When changes aremade to individual records in the UCM, the UCS replicates the new or changedinformation to each of the Zone Databases. The administrator can also run asynchronization command to force the UCS to download its entire database to aparticular Zone Database Server (ZDS). If any problems occur with the integrityof the User Configuration Database, a full copy of the database can be restored(promoted) from any of the Zone Database Servers through the Administratormenu.

2

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

- March 2012 4-5

System Overview

Table 4-3 Server Interactions (cont'd.)

Interaction Description

3

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

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

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

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

7

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

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

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

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

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

12Configuration data is passed from the ZDS to the ATR. Fault events are sent tothe ATR. Configuration data for Dynamic Shared Services Algorithm (DSSA) issent to the ATR.

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

14

Each client workstation runs the Private Radio Network Management (PRNM)Suite of applications. The following list shows the servers that support PRNMSuite applications:

• UCS - User Configuration Manager, Zone Configuration Manager

• SSS - Cluster wide Historical Reports, Performance Reports

• ZSS - Zone Historical Reports

• UEM Server - Unified Event Manager

• ATR - Zone Watch, Radio Control Manager, ATIA Log Viewer, AffiliationDisplay, RCM Reports

If a server is disabled or is not available for some other reason, the associatedapplications do not start or are not able to retrieve or update information in theserver.

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

4-6 - March 2012

4.2 Server Failure Impacts

Table 4-3 Server Interactions (cont'd.)

Interaction Description

16 Information about infrastructure as input to authentication and encryption keydistribution.

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

18 Distribution of the encryption keys from AuC to the BTS.

19 If you use roaming profiles, the dispatch consoles stores the profile data on thedomain controller.

20 Configuration data is sent from ZDS to CCGW.

21

After installation of Cluster Level Domain Controller, Active Directory DNSrecords are transferred into the UCS master DNS server and replicated to all ZDSservers. All Active Directory Domain Controller DNS servers are DNS slaves ofthe UCS and ZDS Master DNS servers. Therefore, Active Directory cannot workwithout UCS and ZDS connectivity.

22

After installation of Zone or Site Level Domain Controller, Active Directory DNSrecords are transferred into the ZDS master DNS server and replicated to all UCSand ZDS servers. All Active Directory Domain Controller DNS servers are DNSslaves of the UCS and ZDS Master DNS servers. Therefore, Active Directorycannot work without UCS and ZDS connectivity.

4.2 Server Failure ImpactsEach server performs different duties or carries specific data. The impact of server failure on the rest of the system isdependent on the server that fails and the systems state at the time of the failure.

The table below illustrates the system capacity lost upon failure of each type of server.

Table 4-4 Capacity Lost When Servers Fail

Subsystem Server Capacity LostNetwork ManagementSubsystem

User ConfigurationServer

• Prevents the UCS database restore/replication process fromoccurring.

• Radio information cannot be edited, default radio recordsare not created, and home zone maps cannot be modified orviewed.

• Cluster-level parameters cannot be changed with the UserConfiguration Manager (UCM) application. Synchronizationof infrastructure changes made at the ZDS is not made untilthe UCS recovers.

The ability of the system to process call requests andassignments is not affected since the Zone Controllers

- March 2012 4-7

System Overview

Table 4-4 Capacity Lost When Servers Fail (cont'd.)

Subsystem Server Capacity Lostcan utilize the information in their HLR/VLRs to handlecall processing during this type of failure.

System StatisticsServer

Prevents the viewing of cluster wide statistics until the serveris available. ATR buffers the ZDS data for 8 hours. If the SSSbecomes available during that time, it is able to collect and storethe cluster-level statistics from the time it was down.

The ability of the system to process call requests andassignments is not affected since the Zone Controllerscan utilize the information in their HLR/VLRs to handlecall processing during this type of failure.

Zone DatabaseServer

• Results in the loss of most fault management functionality;zone configuration management, affiliation display; UCSdatabase restore from the affected zone and UCS databasereplication to the affected zone.

• Domain Name Server (DNS) services are lost.

• Users may be able to switch to a different ZDS at the loginprompt to recover network management application accessto other zones.

• Unified Event Manager alarms for sites do not come through.

The ability of the system to process call requests andassignments is not affected since the Zone Controllerscan utilize the information in their HLR/VLRs to handlecall processing during this type of failure.

Zone StatisticsServer

• Prevents the viewing of zone-wide historical reports andstatistics.

• Cluster-level statistics from the zone are unavailable. ATRbuffers 8 hours of data. If the ZSS recovers in this time, thenno ATR collected statistical information is lost. If the ZSSrecovery takes more than 8 hours, only the last 8 hours of datais available. The BTS buffer statistics for 15 minutes. In casethe ZSS do not recover within 10 minutes some periods ofsite statistics are lost.

The ability of the system to process call requests andassignments is not affected since the Zone Controllerscan utilize the information in their HLR/VLRs to handlecall processing during this type of failure.

4-8 - March 2012

4.2 Server Failure Impacts

Table 4-4 Capacity Lost When Servers Fail (cont'd.)

Subsystem Server Capacity LostAir Traffic Router • The ATIA packet data and zone statistics are no longer

available.

• Devices that are dependent on the ATIA stream are affected.

• Zone statistics upload to the ZSS and SSS are interrupted.Consolidation of zone and system statistics is delayed until theATR recovers, or 8 hours elapse.

• Affiliation data is unavailable for the zone. Dynamic Reportsare unavailable. ATIA Log Viewer is unavailable (cannotaccess log files). The Affiliation Display application becomesunavailable. ZoneWatch application data becomes unavailable.

• AuC, RCM and CADI becomes unavailable

The ability of the system to process call requests andassignments is not affected.

Unified EventManager Server

• Results in the loss of fault management functionality for thezone.

The ability of the system to process call requests andassignments is not affected since the Zone Controllerscan utilize the information in their HLR/VLRs to handlecall processing during this type of failure.

Call ProcessingSubsystem

Zone Controller • Dimetra IP systems are installed with redundant ZoneControllers. If the active Zone Controller fails, all sites in thezone go into local site trunking mode until the switch to theredundant Zone Controller is completed.

• Fault management is unavailable for devices whose faultmanagement information is proxied by the active ZoneController.

Console Subsystem Domain Controllers • The ability to log on to the console is lost if there are no cachedcredentials.

TelephoneInterconnectSubsystem

Motorola TelephoneInterconnectGateway

• Causes all telephone interconnect calls handled by the MTIGto be ended.

• Interconnect call requests are rejected.

- March 2012 4-9

5 Dimetra IP Call ProcessingTopics Covered in this Chapter

• Configuration Information• Mobility Management• Call Processing• Group-Based Services• Individual Call Services• Packet Data Services• Short Data Services• Authentication and Air Interface Encryption• Busy Call Handling• Effects of Loss of Service on Call Processing• Interference Detection• Zone Controller Switchover in Redundant Configuration

The Dimetra system consists of many separate pieces of hardware and software which together form acommunications network. At the highest level, the system can be looked at from two main perspectives.

• Physical, hardware-based component view. How the system components work together to move thenecessary control and audio signals throughout the system to make calls happen. Using this view, you canorganize the system components hierarchically, or by subsystem.

• Logical, software-based system view. How the management software (in all the elements of the fixedinfrastructure) and mobile unit software work together to make calls happen. This approach provides anunderstanding of how the system is configured, how the system tracks mobile units as they roam throughoutthe 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, andtelephone 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 informationnecessary 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 thatare required for call processing to take place. The network transport equipment makes it possible to sendvoice through the system as IP packets.

5.1 Configuration InformationConfiguration information is the foundation upon which all other aspects of call processing are built. Configurationinformation must be developed for the site, zone, and system levels, the radios, and console positions. Configurationinformation is required for the system infrastructure equipment, radios, and radio users.

There are two basic types of configuration information:

• User ConfigurationUser configuration information consists of static or fixed user configuration.

• Infrastructure ConfigurationInfrastructure 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

- March 2012 5-1

System Overview

resources are assigned to a call. In general, this type of configuration is handled by Motorola personnel priorto and during system installation and will not be described further.

5.1.1 Static User ConfigurationStatic configuration information, for call processing support, is used to identify individuals and groups that use thesystem 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. Withinthis application, records are built for radios, radio users, dispatch consoles, talkgroups, and multigroups.Parameters that affect the operations of all radios in the system, such as site access denial, are also entered inthe 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 InfrastructureConfiguration, page 5-7) play an important role in mobility management when a radio attempts toregister 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 siteand/or affiliate with a talkgroup.

Configuration information must be consistent when programming the UCS should be consistent with theconfiguration 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 theUCS. These radios are assigned a default configuration record automatically on initial system access. This defaultrecord gives them a predefined set of call services on the system. If the system is configured to disallow defaultaccess, 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 ofpermissions. Individual control of radio users and talkgroups is not possible. This mode of operation is notrecommended for use under normal operating conditions.

The zone object in the Zone Configuration Manager (ZCM) configures and manages the attributes relating toa specific zone. The Zone Controllers use these parameters to allocate resources. The zone object configurationinformation is replicated from the Zone Database Server (ZDS) to the User Configuration Server (UCS).

5-2 - March 2012

5.1.1.2 Identification Numbers

Two of the fields in the zone object record determine whether radios are allowed to access the system only if theyhave a record in the UCS, or whether they can access the system under default conditions using a default record. Thefields are called Individual Default Access Permission and Talkgroup Default Access Permission.

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 numbersthat 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 uniqueindividual 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 totalnumber 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 IDRange that can include IDs 1-100. Zone 1 becomes the Home Zone to any radio or talkgroup programmed with acorresponding 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 thiswindow allow you to modify the individual and group home zone maps to associate a range of IDs with a particularzone. The record creates two tables, one for the individual IDs, and a separate table for the talkgroup IDs.

- March 2012 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. IDsmapped 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 mapconsists 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 uniqueidentity, 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 talkgroupobjects, also require a unique identification number. The identification is programmed in the User ConfigurationManager.

The total range of identification numbers used by the system is 16.777.215. The IDs are distributed as shownin the table below.

Table 5-1 Short Subscriber Identity Ranges

ID Type ID Range DescriptionSystem 0 Reserved for the system.

Individual orGroup

1 to 13.999.999 Available for individual or group short subscriber identities (ISSIsor GSSIs). Each ID can identify a unique group or individual. Thesame ID cannot be assigned as both an ISSI and GSSI.

5-4 - March 2012

5.1.1.5 Radio User

Table 5-1 Short Subscriber Identity Ranges (cont'd.)

ID Type ID Range DescriptionAlias 14.000.000 to

14.999.999Available for alias short subscriber identities (ASSIs).

Alias or Fleet 15.000.000 to15.999.999

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

System 16.000.000 to16.777.215

Reserved for the system infrastructure ID, gateway IDs, defaultrecords, 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 objectcan also be used to modify existing records. A radio user record includes specific priority levels and access rightsfor dispatch and interconnect. To configure a radio user, you must know how they access the system and whatcapabilities they require for this access.

Radio user records rely on the replication of data between the User Configuration Server (UCS) and the ZoneDatabase 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 tothe UCS. If that site is deleted from the zone, the ZCM user continues to specify it as a valid site for a radio useruntil the UCS is notified of the deletion.

5.1.1.5.1 Radio User to Radio Relationship

A radio user can be associated with a specific radio or the radio user can take advantage of the RUA/RUI feature(Radio User Assignment/Radio User Identity). If not using RUA/RUI you associate the user with a radio byentering the ID of the radio into the radio user record. This relationship between the radio user and a radio allowsyou to change which radio a user may be attached to at any particular time. When using the RUA/RUI feature theradio user is able to pick up any radio and register with Dimetra network using Radio User identity and a sixdigit PIN. This feature also allows the dispatcher to assign a new radio to a certain radio user and have the userconfirm that it is the correct radio.

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 eachtype 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 theZone Controller. Profile information includes data that relates to radios, radio users, and talkgroups who perform thesame function. For example, all radio users associated with the Fire Department require the same resources, so youcan 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 canbe 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

- March 2012 5-5

System Overview

You can use a Radio User Capabilities Profile object to define a set of parameters that are common to a specificgroup 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 haspermission to access. Every radio user is assigned a Radio User Valid Sites Profile. You can use a Radio User ValidSites 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 isassigned a Radio User Interconnect Profile. You can use the Radio User Interconnect Profile record to define a set ofparameters 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 ofsystem access parameters. Templates consist of a combination of attached profiles and parameters set directly onthe record.

5.1.1.8 Configuration Updates

During system operation, updates are sometimes needed to an existing user configuration information. Changesto a radio user configuration are entered in the UCS. Once entered, the changes are copied to the ZDS in eachzone during the database replication process. Each ZDS then distributes the applicable Home Zone informationto 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 togetheron the system. Talkgroup and multigroup IDs are selected from the same range of valid IDs that are available forthe 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.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 specifictalkgroup or multigroup.

Each TG/MG Capabilities Profile contains capability parameters that can be customized per configuredprofile. Every talkgroup and multigroup is assigned a TG/MG Capabilities Profile. For more information onTalkgroup/Multigroup Capabilities Profiles, see Configuration Management, UCM.

5-6 - March 2012

5.1.1.10 Multigroup

5.1.1.10 Multigroup

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

5.1.1.10.1 TG/MG Valid Sites Profile

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

5.1.2 Infrastructure ConfigurationThe System object in the UCM configures parameters at the system level. These parameters are common for everyzone and may affect all radios in the system. The system record is created when the system is staged for testingat the Motorola facility. Subsequently, the record can be opened to modify the fields that affect operation of theradios in the system. This record includes the system identification, access control timers such as the duration of themessage 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 RadioUser Site Access Profile and TG/MG Site Access Profile records. Site access can be allowed or denied to RadioUsers 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.

The type of rejection depends on the valid sites set for each radio and affiliated talkgroup in the corresponding UCMrecords. For example, with a site access denial setting of BOTH, if you have a Radio User that is valid at the sitebut a talkgroup that is not valid, the radio is allowed to register and stay at the site. The radio is allowed to makeunit-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 affiliationrequest, which is accepted or denied based upon the valid site setting for that group. If it is a valid group, the systembegins 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 operatingsites 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 inclose RF proximity to any given site. ACCs allow a radio to learn about the control channel frequencies, currentavailability status, and service capabilities of nearby sites. The radios use this information for ranking potentialcontrol channel candidates that can be used in the event that the control channel of the current site becomes too weakfor 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 ramificationswhen changing the initial configuration.

In large systems, the radio codeplug may not contain all of the frequencies for adjacent sites to which the radiomay need to roam. Additionally, new sites may be added to the system and it may be impractical to bring all ofthe radios in for reprogramming.

- March 2012 5-7

System Overview

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

5.2 Mobility ManagementMobility Management encompasses the system tasks which track where every active individual and group memberis located at any time. It utilizes the information supplied by the static configuration and the information supplied bythe 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 callservices. In addition, radios affiliate with a talkgroup so that they can participate in talkgroup calls and utilizeother group-based call services.

The system determines whether to accept or deny a registration/affiliation request based on configuration settingswhich are programmed into their UCM records and in the radio itself. Mobility management is the primary functionperformed by dynamic user configuration.

5.2.1 Mobility as viewed by the RadioTo a radio, the system is simply a collection of control channels and sites. The radio constantly monitors its RFenvironment, and automatically switches to the best site available based upon received signal strength, internalprogramming and responses to registration and affiliation requests sent to the FNE.

5.2.2 Mobility as viewed by the Fixed Network EquipmentThe 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 talkgroupmember

To respond to registration/affiliation requests from radio units, the FNE in a zone where the unit is registering needsa copy of the access control information for that individual and/or group. The FNE in each zone also needs a placeto store the site location of unit and group member.

5.2.3 How the Location Registers are createdThe system uses a distributed processing architecture that shares the call processing load between the ZoneControllers in the different zones. To enable this, the responsibility for storing (and using) the configurationinformation 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 assignedhas 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 zoneto a given ID. A Zone Controller stores only the configuration information for those individual and groupIDs 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 ofthe zone where the group member is currently registered. Depending on configuration, this can impact the

5-8 - March 2012

5.2.3 How the Location Registers are created

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 forindividuals, Talkgroup and Multigroup for groups. Once entered, user configuration information is replicatedautomatically to each zone in the cluster, where it is stored in the master database of a zone. The replicationprocess makes it possible, if needed, to use any zone to promote its copy of the user configuration informationback to the UCS in the cluster.

Next, based on the home zone mapping, each zone transfers the configuration information for its individuals andgroups to the Home Location Register (HLR) in the Zone Controller. The home zone mapping information isreplicated to each zone from the UCS in the form of map tables. There are two map tables: an individual to homezone 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 theHLR in the home zone of an individual or a group.

Figure 5-2 Home Location Register

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

There are two VLRs - one for individuals and one for groups. The individual VLR stores the accessconfiguration 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 thezone along with the site location of each affiliated member.

- March 2012 5-9

System Overview

Figure 5-3 Home Location Register - Visitor Location Register

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

5.3 Call ProcessingCall 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 Controlling ZoneAssignment of controlling zone for interzone call services is based on the type of call. For multizone individualcalls, the zone location of the radio that first transmits audio becomes the controlling zone for the call, while thezone of the call recipient becomes the participating zone. A participating zone is any zone containing one or moreusers involved with a call controlled by another zone. When a talkgroup member requests a call that requiresmore than one zone, the controlling zone receives acknowledgments from all participating zones before the callis granted. Resource allocation is invoked by a request sent from controlling zone to all participating zones. Theacknowledgment from a participating zone is only sent if resource allocation is successful. For talkgroup calls, thehome zone of the talkgroup (as defined in the GHLR in the home zone of a group) becomes the controlling zone, and

5-10 - March 2012

5.3.1 Controlling Zone

all other zones with talkgroup members become participating zones. Throughout the duration of the call, all controldata and audio is routed from the zone of the originator to the controlling zone, then the audio is routed from thecontrolling zone to all participating zones. The controlling Zone Controller is responsible for managing the call andorganizing all participating Zone Controllers into the call.

The table below lists the components and equipment required to process a call request.

Table 5-2 Call Processing Equipment

Component Function

Zone Controller The Zone Controller processes service requests, location information,outbound commands, and maintains the HLR/VLR databases. The HLRand VLR are used to determine access rights and location of the radios andtalkgroups. Other Zone Controller databases provide information on siteavailability. One of its Ethernet connections is used to link with networkmanagement servers through the core LAN switch.The stored information makes it possible for the Zone Controller to reestablishwide area trunking in a single zone system and interzone trunking in amultizone system. The HLR and VLR use the default records after a ZoneController reset to allow the radios to operate in the system while the radiodatabase is being restored from the ZDS. A copy of the local infrastructuredatabase is downloaded to the Zone Controller once the ZDS is populatedwith the hardware configuration records of the zone. This copy of the localinfrastructure database is stored in the Zone Controller to provide wide areacommunication in cases where the Zone Controller needs to re-initializewithout having access to the ZDS.The Zone Controller uses Ethernet technology for the site link, interzone link,and link with the telephone interconnect device.

• Site Link - The Zone Controller uses this link for control and managementinformation from/to the sites.

• Interzone Link - A Zone Controller uses this link to send and receivescontrol and management information from other Zone Controllers. Theinterzone links are established through an exit router (via the CWR patchpanel).

Gateway routers Serve as the routing path for call processing control information and becomethe RP for Zone Controller to RF site control paths (SCPs). In multizonesystems the gateway routers also serve as the RP for IZCPs. In the ESLsolution the gateway router functionality is colocated with the first core router.

Core routers Act as the distribution point for audio, control information and networkmanagement traffic destined for the same zone sites. The core routers aredeployed in pairs, with each router connecting to the same CWR patch panelvia high-density cables. When a pair of core routers is connected to a CWRpatch panel, the routers are referred to as CWR (cooperative WAN routing)peers. The core routers become the RP for audio routing in the system due tothe multicast address sent by the Zone Controller. Information is transmittedwithin IP packets.

- March 2012 5-11

System Overview

Table 5-2 Call Processing Equipment (cont'd.)

Component Function

Exit routers Act as the distribution point for audio, control information and networkmanagement traffic destined for other zones. Like the core routers, the exitrouters are deployed in pairs, with each router connecting to the same CWRpatch panel via high-density cables. When a pair of exit routers is connected tothe CWR patch panel, the routers are referred to as CWR peers. Informationis passed as Frame Relay packets from the exit routers across the WANinfrastructure to other zones (via CWR patch panels). In the ESL solution theexit router functionality is colocated with the first core router.

Exit routers also provide high speed Intra-MSO connectivity between LANShares via the third Ethernet port. For more information turn to 2.2.3Multi-LAN Sharing, page 2-9

Backhaul switch A pair of backhaul switches per MSO are used to aggregate the IPSec and IPIPtunnels for site links and inter-MSO links.

Core LAN switch Provides the backbone for the routers within the master site to pass IP traffic.The Zone Controller communicates over this switch to reach the networkmanagement servers for radio and interzone information, to reach the corerouters and exit routers for intrazone and interzone transmissions, and selectthe MTIG resources for audio conversion and distribution to the consoleoperator and telephone interconnect.

CWR patch panels The CWR patch panels provide the connection between the core and exitrouters and the E1 WAN infrastructure. Core and exit routers are configuredin pairs to provide path redundancy for audio and control packets. WithCooperative WAN Routing (CWR), the pair of routers work cooperatively tocontrol the CWR patch panel, which switches non-redundant E1 links betweenthe two routers in groups of 12. Each pair of CWR core or exit routers isconnected to a relay panel via high-density E1 ports. The CWR patch panel’sRJ-48C connectors provide the connection to the E1 network.

MTIG The Motorola Telephone Interconnect Gateway (MTIG) operates under thedirection of the Zone Controller to vocode audio between ACELP and A-lawor Mu-law PCM and to route this audio between the IP network and the E1or Ethernet connecting to the customer-supplied PABX. The MTIG alsogenerates any required tones for telephone interconnect operation and providesa gateway path for the control signaling between the Zone Controller andthe PABX.

TETRA Site Controller (TSC) Serves as the site interface to the wide area infrastructure. Receives andtransmits control, audio, and management information. Accomplishes theFrame Relay - Ethernet conversions.

BTS Base Radios The BTS base radio provide the RF interface between the radios and thesystem.

5.3.2 Call TypesThe following describes several types of voice calls that can be made through the Dimetra IP system. The examplesare 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.

5-12 - March 2012

5.4 Group-Based Services

The following describes these five call types using the call processing structure.

5.4 Group-Based ServicesThe Dimetra IP system offers several types of group-based services. The following describes the following fivetypes:

• 5.4.1 Talkgroup Call, page 5-13

• 5.4.2 Announcement Call, page 5-18

• 5.4.3 Emergency Services, page 5-19

• 5.4.4 Site Wide Calls, page 5-20

• 5.4.5 Talkgroup Scanning, page 5-20

5.4.1 Talkgroup CallThe talkgroup is the primary level of communication in a trunked radio system. Most of the conversations aradio user participates in are talkgroup calls. The following describes in detail call processing for a talkgroupcall. 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 whereradios are used most frequently, such as a patrol district or management area. When possible, talkgroups and radiousers should be configured so that the majority of the calls take place within this geographic area, thus reducingthe 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. Atalkgroup call request is initiated when the caller selects the appropriate mode on the radio and then presses thePTT 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 forprocessing 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 bychecking the access configuration information stored in the VLR. If it is a valid request, the Zone Controllerchecks its talkgroup-to-home zone map table to see which zone is the home zone of the talkgroup. For groupcalls, the home zone of the group becomes the controlling zone for the call, regardless of which zone thecaller 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 thebase station and is sent to the Site Controller. The controller then encapsulates the traffic in Frame Relay packets andtransmits the traffic to the MSO.

- March 2012 5-13

System Overview

Figure 5-4 Intrazone Talkgroup Request from a BTS Site

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 informationindicates 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 toestablish the call. (See 5.9 Busy Call Handling, page 5-35 for details.)

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

Process Steps

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

5-14 - March 2012

5.4.1.1.4 Intrazone Talkgroup Call Audio Routing

2 The Home Zone for the call request sets up a core router as the distribution point for the audio information. Thisaudio 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 trafficchannels 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.

Process Steps

1 When the radio user speaks into the microphone of the radio, the radio converts the speaker's analog audio intoACELP 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 theassigned traffic channel.

3 The traffic channel places the audio into the site's Ethernet LAN as IP packets and routes the audio signalthrough 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 ZoneController'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 thetraffic channel. This message is extracted from the audio stream by the remote site and forwarded to the ZoneController.

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

Process Steps

- March 2012 5-15

System Overview

1 When the speaker releases the PTT button, a message is sent to the controlling Zone Controller. If the call ismessage 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.

Step result:

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

Step result:

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 includedin the call control process. In an interzone call, each zone controls its local resources in a similar manner to thepreviously described intrazone call. However, because the controlling zone must coordinate with the neededparticipating zones prior to granting the call, there is much more activity during the call request and setup phases.

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 pressesthe 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 VLRand determines if the requester is able to make the call. The Zone Controller then checks the talkgroup-to-homezone 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 responsibilityfor the call. The call request is acknowledged, and the controlling Zone Controller begins to set up the call. If thereceiving zone is not the home zone, the call request is passed on to the appropriate Zone Controller, which acceptscontrol of the call and becomes the controlling Zone Controller for the call (see figure below).

Figure 5-6 Interzone Call Request

5-16 - March 2012

5.4.1.2.2 Interzone Talkgroup Call Setup

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 theappropriate Zone Controllers, requesting their participation in the call. All interzone call control messages betweenany pair of Zone Controllers goes over the Interzone Control Path between those two zones. There is an activeInterzone 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 includedin the call, and if all the resources are available to set up the call. The call is busied if any zone cannot participatedue to lack of resources. If all the resources are available, the participating Zone Controllers acknowledge theirparticipation back to the controlling zone.

When all participating zones acknowledge the call request, the controlling Zone Controller grants the call. The grantmessage is sent to each participating zone through its active Interzone Control Path with the controlling zone. At thispoint, 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.• Notifies the consoles of the talkgroup call and its audio source, if needed. The Zone Controller relays theaudio 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 audiodistribution.

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 theassigned 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 trafficchannel frequency and received by the site, which routes the audio stream to the core router at the local MSO. Thecore router relays the audio signal to the assigned sites through their remote site router, to the consoles and over theassigned interzone resources to the exit routers in the participating zones. The exit routers in the participating zonesthen route the audio to the core LAN switch , the core router, gateway router, consoles in their respective zones, andthe 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 isextracted from the audio stream by the remote site and forwarded to the controlling Zone Controller. In transmissiontrunking 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 Controllerreceives the new call request (either from a site in its zone or from a participating Zone Controller), sees that it is fora talkgroup that has an active call, and continues the call using the resources currently assigned to the talkgroup. Theaudio 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 controllingZone Controller sends a message to each participating zone to tear down the call. Each zone goes through theteardown process, disabling the audio and marking the resources used in the call as available for other callassignment.

- March 2012 5-17

System Overview

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 aretalkgroup members at sites within the zone), the roaming user experiences a short loss of audio while thecall 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 noaffiliated talkgroup members in that zone), the roaming user experiences a longer loss of audio while theinterzone call setup process takes place. The access control information needs to be transferred from thehome zone HLR to the HLR in the new zone and from there to its VLR, the call request validated in the newzone, 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 isplaced in its busy queue. When the needed resources become available, the roaming user rejoins the call inprocess. A longer loss of audio occurs in this case.

5.4.2 Announcement CallAn announcement call involves all the radios assigned to a multigroup. A radio or dispatch console can initiatethe announcement call selecting the multigroup. Any radios affiliated to any of the talkgroups assigned in themultigroup receive the call. Audio for an announcement call is routed through the infrastructure in the samemanner 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 theindividual talkgroups associated with that Multigroup.

A radio unit with the selector in the Multigroup mode position can monitor talkgroup activity for talkgroupsassociated with the selected multigroup if and only if the monitored talkgroups have an affiliated member in thesame zone as the monitoring radio. The system does not pass audio between zones exclusively for a unit that isscanning talkgroup activity while in multigroup mode.

5.4.2.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 patchfeatures. The MSEL feature allows a dispatch operator to drag talkgroup icons into a resource window. The dispatchoperator is then able to transmit to all the selected talkgroups simultaneously. The call to each talkgroup is thenterminated 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 effectuntil the dispatch operator explicitly terminates the patch. Each time a radio or dispatch operator transmits to thepatched talkgroups, a call is established with all the patched talkgroups.

5-18 - March 2012

5.4.3 Emergency Services

5.4.3 Emergency ServicesThere are two types of emergency services:

• Emergency alarm- A radio to console or Radio Control Manager (RCM) function that is sent over thecontrol channel.

• Emergency call- A radio or console call function.

5.4.3.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. AnyRCM positions that are active, and have the currently selected talkgroup or multigroup as part of their list ofattachments, also receive and display the emergency signal. If an RCM User is configured to receive "unattendedemergency alarms", they may receive emergency alarms from radios whose talkgroups or multigroups are outside oftheir list of attachments, if there is no other RCM User online to receive the emergency alarm. The radio can beconfigured to enter emergency call mode automatically when the emergency button is pressed.

5.4.3.2 Emergency Call

An emergency call is a specialized, high-priority version of a talkgroup or announcement call. Emergency callsalways have the highest priority in the system. When an emergency call request is made, the request takes priorityover any other type of call request. The emergency call can be programmed in the radio as tactical or revert. Whenprogrammed as tactical the call is made on the radio's currently selected talkgroup or multigroup. When programmedas 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. Thelowest 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 andlogging recorders affiliated to talkgroup or multigroup. All needed resources for receiving sites are ruthlesslypreempted.

Once an emergency call is granted, it is handled by the system as a talkgroup call although emergency calls aremessage trunked with their own longer hang-time timer setting. The range for this timer is 0 to 3660 seconds, thedefault message hang-time for an emergency call is 30 seconds.

A value of 3660 disables the message timer for emergency calls. Radio Users have unlimited time betweenPTTs.

A console operator can initiate an emergency call on any talkgroup or multigroup being monitored. The systemhandles a console emergency call request the same as a radio-generated request, with one exception: a consolegenerated emergency call has an unlimited hang time, so the call stays active until the operator “knocks down” theemergency call at the operator position.

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

- March 2012 5-19

System Overview

5.4.4 Site Wide CallsA site wide call involves all the radios registered with a particular site at the time of the call. A site wide callreaches the radios registered with the site regardless of their talkgroup affiliations. Only dispatch consoles caninitiate a site wide call.

5.4.5 Talkgroup ScanningTalkgroup Scanning and Priority Group Monitoring are closely related features. Priority Group Monitoring is anattribute of a TG defined within the infrastructure. A Priority Monitor TG can pull a user monitoring another TGcall 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 configurablelist of groups at the site where the radio is registered. When no group activity exists for the MSs selected TG orassociated multigroup and the radio is either idle on the MCCH or active on the PDCH and a call is initiated to aTG 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 thegroup call ends. Note that a radio unit only receives call setup request for scanned groups if another radio at thesame 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 theradio is on the PDCH, another radio is required to be active on the PDCH at the same site and attached to one of thescanned 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 radiosselected TG and associated multigroup, if the setup is to a group with higher scanning priority than the monitoredcall. The group identity of the TG being monitored is displayed in the radio unit's display. Note however thatgroup calls are only signaled on the TCH of another call, when the new call is configured as a Priority Monitorgroup 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 selectedTG (affiliated group) or associated multigroup of the served user, the operation of PTT results in a transmissionrequest (normal operation) to this TG. However, for all other monitored calls, operation of PTT only results in atransmission 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 selectedgroup. If groups are critical as far as the system administrator or network operator is concerned, these groups canbe configured as Priority Monitor groups in the UCM and critical sites can be defined in the UCM as requiredwhen setting up the group call.

5.5 Individual Call ServicesIndividual call services are available through the Dimetra IP system. The controlling zone is determined in a mannerdifferent from that used for group-based calls for this type of call service. In an individual call, the controllingzone 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 assigneduntil the target radio responds to the initial request. Audio channel resources are assigned once the targetradio responds to the call request.

5-20 - March 2012

5.5.1 Private Call Request

5.5.1 Private Call RequestThe below figure graphically represents a private call request within a single zone. Note that it is also possible tomake private calls across zones.

Figure 5-7 Private Call

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 withthe system. Other reasons for a call to be rejected would be configuration-related (one of the radios blocked fromprivate 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.

Process Steps

1 A private call request is initiated when the caller selects the appropriate mode on the radio, and then enters thetarget 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 issent over the control channel to the current site. The information is passed to the Site Controller for processingand 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 tomake private calls.

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

- March 2012 5-21

System Overview

5 If the target radio is active (registered) in the same zone, the Zone Controller sends it a private call requestover 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 homezone 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 currentlocation 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 theZone Controller in that zone.

8 The target radio's Zone Controller checks its individual VLR for the target's site location and sends the callrequest 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 requesterhears 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 alreadyestablished. See 5.5.1.1 Private Call Request Flow, page 5-21 for details.

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 packetsfor 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-transmittingradio user roams to a new site during a call, the audio is redirected automatically to the new site. The radio userexperiences a brief interruption of the audio when moving to another site within the same zone. The audiointerruption 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 transmittingradio fades out (due to moving away from the current site), the system detects the loss and begins thecall termination process.

5-22 - March 2012

5.5.1.4 Full-Duplex Private Calls

5.5.1.4 Full-Duplex Private Calls

Radios or dispatch consoles can initiate full-duplex private calls, allowing both parties to simultaneously transmitand 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 isinitiated when the radio presses the send button, and the call terminates when one of the parties presses the endbutton. Full-duplex operation is simulated in the radio by switching between the uplink and downlink channelswithin each TDMA frame.

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

Figure 5-8 Telephone Interconnect in E1 networking

The telephone interconnect feature builds upon all of the configuration and infrastructure discussed up to thispoint. With talkgroup calls and unit-to-unit calls, all parties to the conversations all reside somewhere on theDimetra IP system.

For telephone interconnect calls, one of the parties is outside of the Dimetra IP system and is connected throughlandline telephone to the radios in the system.

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

- March 2012 5-23

System Overview

5.5.2.1 Relationship between Components

The Zone Controller uses call control client software to interface with call control server software running on theMotorola Telephone Interconnect Gateway. The call control server software translates the Zone Controller’scommands into a format compatible with the PABX and forwards them to the PABX. In this way, the ZoneController 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 ToneMulti-Frequency (DTMF) overdial tones (touch-tone), and other messaging tones (end-of-call warning). It is doneusing tone generation client and server software installed on the Motorola Telephone Interconnect Gateway. TheMTIG 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 automatedresources in the PABX/PSTN network.

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 isdedicated for the duration of the call, and telephone calls typically last longer than talkgroup calls. Because of thisfact, 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 canalso be programmed with specific call lists (telephone numbers) and configured to prevent users from callingnon-programmed telephone numbers. Individual radio users may be configured with maximum monthly call timesthrough the Radio User object in the UCM.

Individual Interconnect Profiles

Each radio is assigned an interconnect profile (the Radio User Interconnect Profile object in the UCM). The profileis created in the UCM and assigned to the radio user. Your system may have various individual interconnectprofiles available for assignment to radio users.

One of the settings in the individual interconnect profile specify a Priority Level. The system uses priority levelsto 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 canbe assigned a priority level 2 through 10, depending on individual requirements. Level 2 is the highest assignablepriority, while level 10 is the default priority setting.

See 5.9 Busy Call Handling, page 5-35 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 interconnectservices. This can be done through the Shared Service object and the Zone object in ZCM.

Enabling or Disabling Interconnect Based on Shared Service

The Shared Service feature is a more sophisticated method of balancing telephone interconnect capability withdispatch traffic. Two types of shared service are available:

• Table-Driven Shared ServiceA standard feature that allows the system manager to specify the maximum number and duration ofinterconnect calls which are allowed at any given time for each site. This is done using the Level of Service

5-24 - March 2012

5.5.2.2.2 Call Setup Restrictions

(LOS) object in the ZCM. A number of LOSs can be configured with different settings for maximum numbersand maximum duration of calls. These levels of service can then be assigned individually for two-hour timeblocks throughout the day in the Shared Service object of the ZCM. Each site is configured with its own table.

• Dynamic Shared ServiceDynamic Shared Service (DSS) is a feature that expands the table-driven shared service functionality.Dynamic shared service provides an automatic adjustment to the configured table-driven shared servicetables according to current system loading. DSS allows you to create more flexible telephone interconnectusage patterns which can be saved as different Levels of Service (LOS). These dynamic levels of service canthen be assigned individually for two-hour time blocks throughout the day in the Shared Service object of theZCM. 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 aninterconnect call. Before the interconnect call exceeds this time, an alert tone is generated to indicate that the call isabout to end. When the warning period expires, the interconnect call is terminated.

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 channelresources are available.

• If no MTIGs are available, interconnect calls are busied until one becomes available. This means that thecall 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 theradio 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 inthe 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 allowsthe system to check dialing restrictions before granting the traffic channel for the call. Restricted phone numbersresults 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 successfulradio-to-landline call.

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

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 MotorolaTelephone Interconnect Gateway determines the controlling zone for the call, the point where the multicastaddresses originate, and the location of the RP for the call.

- March 2012 5-25

System Overview

5 Radio system resources are assigned to the call. The resources include the site where the radio is located, agateway router for distribution to the network, resources in the MTIG for audio conversion between ACELPand 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 transmitside. 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 numberand 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 thetarget radio, regardless of the radio's current zone registration, and routes the call through the network to the targetradio. 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 assignedtraffic channel for the duration of the call. If necessary, the radio can move to the control channel to perform specialfunctions, such as a fade condition, or to send a request to cancel the interconnect call.

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 ableto 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 automaticallycancels the interconnect call before deregistering from the system and powering down.

5-26 - March 2012

5.5.2.4.2 Landline Initiated Termination During Active Interconnect Call

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 toterminate 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 bysetting the Maximum Interconnect Call Duration timer in the Zone Configuration Managers (ZCM) zone object, inconjunction with the shared services configuration and current system loading. The system also disconnects aninterconnect 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 thecall 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, oran interconnect call in the process of being terminated. For each scenario, there are several possibilities that canoccur 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 haspreviously 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, andthat the new site is capable of interconnect service.

• 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. Thelandline 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-landlineor 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 Packet Data ServicesThe Dimetra IP system supports the packet data feature, allowing mobile data terminals to communicate through theDimetra IP infrastructure to data hosts located in customer enterprise networks. A data gateway can be installed ineach zone to provide control and routing services for packet data traffic.

- March 2012 5-27

System Overview

Figure 5-9 Packet Data Services

The RNG provides the necessary encapsulation between the radio network and the PDR. The RNG also provides thelogical link connection and any necessary compression to deliver the outbound packet data traffic to the appropriatedestinations. The RNG hosts the packet data visitor location register (PD-VLR). The PD-VLR contains mobilityinformation and packet data channel assignments (if applicable) for all the packet data users that are currentlyregistered in the zone. The RNG receives updates to the PD-VLR from the Zone Controller.

The PDR provides encapsulation of traffic between the RNG and GGSN, provides mobility management of all packetdata users that are home to the zone, and provides access control according to the HLR/UCS settings. The PDRdelivers outbound traffic to the RNG with the appropriate destination address. The PDR hosts the packet data homelocation register (PD-HLR). The PD-HLR contains all the packet data service permissions and configuration forpacket data users that are home to the zone. The PDR receives updates to the PD-HLR from the zone database server.

The GGSN provides separation between the infrastructure and the customer enterprise network. The GGSNprovides IP tunneling via a border router to the customer enterprise network.

The border router operates in the DMZ, which is a less secure portion of the network. The border router provides thedirect connection to the CEN. If a data user is operating outside their home zone, or if a data user is accessing a CENwhich is in another zone, then a peripheral network router is also used to route the data-related traffic across zones.

The border router operates in the DMZ, which is a less secure portion of the network. The border router provides thedirect connection to the CEN.

5.6.1 Packet Data Service Initiation

Process Steps

1 The data terminal initiates the request for packet data service by establishing a point-to-point protocol (PPP)connection with the radio. The data terminal sends information including its static IP address (if applicable), theaccess point name (APN) for the packet data host, and challenge handshake authentication protocol (CHAP) ifRADIUS authentication is being used.

5-28 - March 2012

5.6.2 Data Prioritization

2 The radio requests access to a packet data channel (PDCH) at the BTS site. The radio sends the request alongwith its assigned resource allocation group (RAG).

3 The Site Controller evaluates the resource allocation group for the radio and assigns a packet data channel whichis configured to operate with the resource allocation group of the radio.

4 The radio sends the packet data request information over the PDCH, and the request is received by the radionetwork gateway (RNG) in the data gateway. The RNG forwards the request to the Packet Data Router (PDR).

5 The PDR checks the permissions for the radio according to its locally stored packet data home location register(PD-HLR). The PD-HLR includes permissions and settings that have been defined through UCM. If packet dataservices are permitted for the radio, the PDR forwards the request information over a GTP tunnel to the GGSN.

6 The GGSN establishes an IP tunnel to the customer enterprise network according to the APN in the request.This IP tunnel provides delivery of packet data traffic between the Dimetra IP network and the customerenterprise network. This tunnel originates at the GGSN, runs through the border router, and terminates at thecustomer enterprise network.

7 At the customer enterprise network, a DHCP server assigns a dynamic IP address to the data terminal if theterminal does not have a static IP address. If RADIUS authentication is supported, then a challenge handshakeauthentication protocol (CHAP) and password authentication protocol (PAP) are negotiated between theRADIUS server and the data terminal to ensure that both parties are genuine.

8 The packet data host establishes contact with the data terminal and packet data traffic between the data host andthe remote data terminal can flow across the infrastructure.

5.6.2 Data PrioritizationData Prioritization allows high-priority messages to be delivered faster regardless of the current loading of the datachannel. The feature works by assigning a relative priority to each datagram. This enables the datagram queue in thePDG to be reordered based on the priority of the individual datagrams. The priority is set on a application basis.This ensures that datagrams from critical applications that does not utilize a lot of bandwidth can be transmittedsuccessfully to the individual radios.

5.6.3 Multislot Packet DataMultislot Packet Data Channels (PDCH’s) are configured in the Network Manager as the number of MultislotPDCHs and their width (number of timeslots) at the site. The site then requests the required channels from the ZCand assembles the multislot PDCH from the acquired channels.

Based on the overall load at a site the width of a multislot PDCH can change dynamically. This can happen forseveral reasons:

• The SC can resize multislot PDCHs based on the overall channel utilization to optimize the use of systemresources and thereby minimize the risk of queuing voice call in the ZC or preempting data channels forhigher priority services. The operation is that the SC decreases the width of a multislot PDCH to a configuredminimum and thereby frees up resources in the ZC in case of high load/channel utilization at the site andincreased the width as the channel utilization decreases.

• In case of a higher priority service being initiated and no resources available the ZC can preempt a datachannel. In this case the SC resizes the multislot PDCH to free up the channel so that it can be used forthe higher priority service as requested by the ZC.

- March 2012 5-29

System Overview

5.6.4 Dynamic Data ChannelThe most resource efficient way to implement the TETRA Packet Data Service is usually to provide dedicatedpacket data channels. However, it is also possible to share channels between voice and data traffic. These sharedchannels are known as Dynamic Data Channels and are normally dedicated for the Dimetra Packet Data Service, butthey can be preempted by the following categories of voice calls: emergency calls, Preemptive Priority Calls, orcalls for talk groups that have been specifically enabled to preempt the dynamic packet data channel. Dynamic DataChannels are particularly effective at making efficient use of traffic resources for smaller systems, systems with arelatively light requirement for packet data, or where the packet data requirement fluctuates with time. Note thatDynamic Data Channels are also known as Semi-static PDCH.

5.6.5 End-to-End Encryption (E2EE) Packet DataEnd-to-End Encryption is an overlay service that allows secure (digitally encrypted) data communications betweenradios and data applications in the customer enterprise network (CEN). The primary use of this feature is to provideencryption from wireless data modems to a point inside the CEN for data devices such as GPS receivers andother data applications.

Encryption/decryption services are provided by the system endpoints, which for E2EE PD is provided by thePacket Data Encryption Gateway (PDEG). Only an endpoint that shares the same encryption key and encryptionalgorithm is able to decrypt the transmission successfully. Other devices that do not have the proper key arenot able to receive intelligible information.

The encryption key is vital to the security of the Dimetra secure system. If the key become known togroups or individuals outside your organization, they can decode your data traffic or even gain unauthorizedaccess to the network. You must therefore ensure that the encryption key is kept secret.

The radio and the PDEG data encryption key, can be centrally managed using a Key Management Facility server(KMF) in the CEN.

5-30 - March 2012

5.7 Short Data Services

5.7 Short Data ServicesWhen and where to use:

The ATS application is a purchasable optional software that can be used in a system to send text messagesof maximum 500 characters in ASCII or 250 characters in Unicode from a host to a display on a radioand vice versa. For these messages a consumed report can be requested. Also broadcast messages can besent to Individuals and Groups in selected regions.

Short data traffic can be delivered concurrently with voice traffic or packet data traffic.

Figure 5-10 Short Data Services

Process Steps

1 The radio, remote data terminal, or host creates a message, selects the Short Subscriber Identity (SSI) ofthe recipient, and sends the message. If a radio is sending the short data message, the message is deliveredover 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 todetermine where the recipient is located.

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

5.7.1 Short Data Store and ForwardA 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 theDimetra system. The installation of the SDR and SFS software is common and carried out during a one process.

- March 2012 5-31

System Overview

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 Forwardsfunctionality and the SDTS/SDR functionality are deployed on the one physical device.

5.7.2 End-to-End Encryption (E2EE) Short DataThe primary use of this feature is to provide encryption from wireless data modems to a point inside the CEN fordata devices such as text message recipients.

Encryption/decryption services are provided by the system endpoints, which for E2EE SD is provided by theShort Data Encryption Gateway (SDEG). Only an endpoint that shares the same encryption key and encryptionalgorithm is able to decrypt the transmission successfully. Other devices that do not have the proper key arenot able to receive intelligible information.

The encryption key is vital to the security of the Dimetra secure system. If the key become known togroups or individuals outside your organization, they can decode your data traffic or even gain unauthorizedaccess to the network. You must therefore ensure that the encryption key is kept secret.

The radio and the SDEG data encryption key, can be centrally managed using a Key Management Facility server(KMF) in the CEN.

5.7.3 SDS in Local Site TrunkingShort Data Services in Local Site Trunking feature enables a stand-alone base station working in LST mode toprovide 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.8 Authentication and Air Interface EncryptionThe Dimetra IP system supports authentication and air interface encryption to provide a level of security againstdifferent 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. TheDimetra 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

• Authentication disabled and air interface encryption disabled

5-32 - March 2012

5.8.1 Authentication

5.8.1 AuthenticationAuthentication is used to verify that a radio accessing the system is valid, and to reject any unauthorized partiesfrom accessing the system. The Dimetra IP system uses a challenge-response-result protocol to authenticate boththe radio and the infrastructure.

The authentication process begins with the infrastructure sending a challenge to the radio. The radio calculatesa response based on the challenge, and sends the response to the infrastructure. If the response from the radioequals the expected response by the infrastructure, then the infrastructure indicates that the authentication result issuccessful and grants access to the system. If the response is not correct, then the infrastructure indicates that theauthentication result has failed and rejects access to the system.

Figure 5-11 Authentication

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

5.8.2 Air Interface EncryptionAir interface encryption provides security for RF signaling between the infrastructure and radios. Air interfaceencryption is achieved by using a common encryption key in both an infrastructure base station and a radio, allowingthe 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), TETRAEncryption 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. Thereceiving station uses the same key and offset value through an algorithm to decrypt the stream of traffic. Aproportion of the MAC header for the packets remain clear throughout the encryption process. An example of thisprocess is shown in the figure.

Figure 5-12 Encryption of Traffic

5.8.2.1 Security Classes

Dimetra security is defined in terms of class. Each class has associated, mandatory or optional, features. Securityclasses and features associated with them are presented in the table.

- March 2012 5-33

System Overview

Table 5-3 Security Classes

Class Authentication OTAR SCKEncryption

CCK/DCKEncryption GCK

Enab-le/Dis-able

1 O O (see note 3) - - - O

2 O O M - - O

3 M (see note 1) M (see note 2) O M - O†

3G M (see note 1) M (see note 2) O M M O†

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 duringcell reselection to a cell of a different security class.

5.8.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.8.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 encryptionand TM-SCK OTAR or DM-SCK OTAR. If a system is prevented from running SC2 then a radio is not grantedaccess when SC3 is not possible, see 5.8.2.1.3 Security Class 3 (SC3), page 5-34.

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 atime, and broadcasts the number of the SCK (SCKN) that is currently being used in the system, between 0 and31, to the radios. The radio selects the appropriate SCK (from its provisioned list of SCKs) to decrypt trafficfrom 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. noauthentication service, during site link failures, during interzone link failures, and so on). The SCK is also usedwhen 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.8.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 encryptionkey for the radio. After authentication, the radio stores its calculation of DCK and a copy of DCK is stored inthe infrastructure.

5-34 - March 2012

5.8.2.1.4 Security Class 3G (SC3G)

The base station and radio use the unique DCK along with an offset value to encrypt and decrypt traffic from oneanother. DCK is not used for group calls. However, DCK supports group call services by allowing over-the-airrekeying 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 timethe 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 sharethe 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 usingtheir 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.

5.8.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/CCKencryption. In this mode encryption functionality is identical to the previous one with the addition that one or moretalkgroups may use a dedicated Group Cipher Key (GCK).

5.9 Busy Call HandlingThe following describes how the system modifies the calling process to handle situations where resources are notavailable 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 requestis 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 prioritysetting that influences the order in which calls in the busy queue are evaluated. Higher-priority calls are evaluatedbefore lower-priority calls. Calls of equal priority are evaluated on the basis of the order in which they wereplaced in the queue.

5.9.1 Priority LevelsPriority levels are used by the system to determine the assignment of system resources when multiple calls arecompeting for system resources. Emergency calls always have the highest level of priority. There are ten levelsof priority:

• Level 1 = The highest priority. Reserved for emergency calls. Level 1 cannot be assigned to any othercall types.

• Level 2-10 = May be assigned to talkgroup, individual, or telephone interconnect calls. Level 2 is thehighest assignable priority, while level 10 is the default priority setting.

5.9.2 Group Call BusiesTwo calling features determine when group (talkgroup and multigroup) calls are busied:

• AllStart™• FastStart™

- March 2012 5-35

System Overview

These calling features are assigned to the groups in the User Configuration Manager (UCM) application.

5.9.2.1 AllStart

An AllStart setting for a group indicates that all the available resources for the call must be present for the call tostart. 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/ICCS 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 AccessProfile record available in the UCM.

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

5.9.2.2 FastStart

A FastStart™ setting for a group call indicates that only mandatory resources (that is, critical sites, critical resourcesand requested sites) are required to grant a call. Any other resources available at the time the call is set up are alsoincluded in the call. In FastStart™, not all affiliated members in a talkgroup must have a channel available in orderfor 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 higherof the individual priority of the talkgroup or the requestor. For example, if the talkgroup is priority 8 andthe 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.9.3 Private Call BusiesPrivate calls are placed in the busy queue if the required resources for the call, including encryption, are notavailable 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 thebetter of the target or individual priority of the requestor. For example, if the target's priority is 8 and thepriority 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, thehigher the priority, the sooner the call gets serviced.

5-36 - March 2012

5.9.4 Typical Reasons for Rejects

5.9.4 Typical Reasons for RejectsWhen 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 resourcesand sends a message to the requestor granting the service. When the Zone Controller rejects a request, the ZoneController sends a reject message to the requestor. When the Zone Controller is experiencing a busy situation, theZone Controller sends a busy signal to the requestor.

When a radio has been rejected from using a particular service, the Zone Controller sends an abort message to anyresources that need to be released from the service, then sends a reject message to the radio. The following items aretypical 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 ZoneController.

• 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 inlocal site trunking and only allow certain types of calls, or the Zone Controller may be using default accesspermissions.

• The radio may be calling an individual or talkgroup that does not exist or that is not registered with thesystem.

• 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 particularresources may not be available for the call.

5.10 Effects of Loss of Service on Call ProcessingFor purposes of this discussion, loss of service indicates that part of the infrastructure has failed, and that the failureaffects 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.12 Zone Controller Switchoverin Redundant Configuration, page 5-42 for a discussion of the impact of a Zone Controller switchover on callprocessing within a zone.

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

5.10.1 Loss of Service within a ZoneWithin a zone, two types of service states are available for sites that affect call processing: wide-area trunking andlocal site trunking. These states are listed in the table.

- March 2012 5-37

System Overview

Table 5-4 Zone Call Service States

State DefinitionWide-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 atthe site can communicate with any other radio in the system. The basic criteria forwide area trunking includes an active RF site control path between Zone Controllerand site, an enabled audio rendezvous point in the zone, a control channel and atraffic channel at a site.

Local Site Trunking Local Site trunking mode is entered when the remote site loses communicationwith the Zone Controller. In this mode, the remote site takes over call processingresponsibility. A radio registered at the site can communicate only with other radiosregistered at the same site.

5.10.2 Conditions Necessary for Interzone TrunkingFor 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 trunkingstate 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 theirinterzone trunking state.

5.10.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 isno application that can indicate the level of service being provided. The information in the table can be applied tosituations where the system appears normal but users do not have full access to their talkgroup.

Table 5-5 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. Thisoccurs when either the participating zones have no interzone trunking with the home zoneof the group, or when the home zone loses interzone trunking with all the other zones inthe system. In such case the routers establish an alternate IP path.

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

5-38 - March 2012

5.10.2.1.1 Example 1

5.10.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 ofthe links between the zones (generally microwave).

• In the figure, the link between Zone 1 and Zone 3 is down (interruption of interzone trunking), while thelinks 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 timewhile the master site routers reestablish the call through an alternate IP path, in this case, through Zone 2.

Figure 5-13 Reduced Interzone Service Availability

5.10.2.2 Interzone Individual Service Availability

Interzone individual services do not have the same service availability concepts as group calls. Interzone individualcalls are always two-zone calls, with the controlling zone dynamically assigned as the zone responsible forinitiating the audio.

5.10.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 interzonecontrol 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 InterzoneControl Path between itself and the requestor's home zone so it can access the requestor's individual HLR.

- March 2012 5-39

System Overview

5.10.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).

Figure 5-14 Interzone Individual Call with Radios in Their Home Zones

5.10.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), 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.

5-40 - March 2012

5.11 Interference Detection

Figure 5-15 Interzone Individual Call with Radios Not in Their Home Zones

5.11 Interference DetectionInterference Detection gives the System Operator a warning of interference conditions affecting the uplink carrierfrequency of any channel(s) within any system cell. Interference is defined as any RF signal, condition orcharacteristic that may adversely affect one or more radios within any cell of the system. This might include, forexample, a malicious RF “jamming” signal; non-malicious interference caused by nearby equipment with poorEMC characteristics; or malfunction within a radio’s equipment that adversely affects other non-malfunctioningradios within the cell.

Interference Detection offers a mechanism that automatically removes all channel resources affected by theinterference from service, for the duration of the interference condition and transfer the service to other channels thatare 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 (BTSlevel), via TESS for initial values and via the NM subsystem. The new parameters are manager owned. Theycomprise of three integer parameters:

• Condition Alert Hysteresis. Proportional to the time taken to clear an interference condition, dependent alsoon 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 aninterference condition, dependent also on the ratio of interference to non-interference packets.

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

- March 2012 5-41

System Overview

5.12 Zone Controller Switchover in RedundantConfiguration

The redundant Zone Controller in each zone provides protection against a hardware or software failure that mayresult in the loss of wide area trunking until the Zone Controller is repaired or recovers automatically. Onecontroller actively processes calls and manages resources in the zone, while the other controller acts as a standbythat can be brought online when the active controller is being serviced or has an internal failure that causes theloss of wide area trunking.

The two controllers communicate with each other through the link connected directly between the two or, shouldthat link fail, through the links connected to the core LAN switch . The direct link, also called the negotiating link, isused by the controllers to notify each other of their ability to maintain the zone in wide area trunking mode andto negotiate the switchover should that action be necessary. The core LAN switch establishes the connectionsbetween the controllers and the sites, and the MTIG. Although both controllers can receive network traffic, onlyone controller is actively in charge of the zone. Both controllers maintain links to the Network ManagementSubsystem in order to report individual controller status.

The Redundant controller can be switched automatically or by user-initiated switchover. Automatic switchover takesplace upon internal failure that causes the loss of wide area trunking or loss of dispatch operations. User-initiatedswitchover is done from the Zone Configuration Manager (ZCM) application in the Private Radio NetworkManagement (PRNM) application Suite. In the event that access through ZCM is not possible due to failure, theLocal 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, likeincreased down time, on system operation and should only be used when access through the ZCMapplication is not possible.

The following explains what causes an automatic switchover and how the system reacts when an automaticswitchover occurs and when a user-initiated switchover occurs.

• For information about performing the user-initiated switchover and Zone Controller redundancy andswitchover, see Configuration Management, Call Processing Subsystem.

5.12.1 Automatic SwitchoverAutomatic switchover occurs when a failure event within the controller causes a loss of wide area trunking for allsites or loss of dispatch operations. The failure event can be software- or hardware-based. The failures that triggeran automatic switchover are CPU failure, both power supplies failure, Ethernet connectivity failure and a manualdisabling from a local Administrator menu.

5.12.2 User-Initiated Switchover

Due to the severe system impact of a switchover event, user-initiated switchover should be initiatedONLY when absolutely necessary.

User-initiated switchover is a feature that gives you the ability to disable the automatic switchover feature andperform 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

5-42 - March 2012

5.12.3 System Behavior During Automatic Switchover

may be done through the Zone Controller Administration menu through the Local User Terminal. User initiatedswitchover is typically used when performing a software upgrade or performing maintenance such as replacing afaulty 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 beforeperforming a user-initiated switchover or take any kind of action that results in a controller switchover.

5.12.3 System Behavior During Automatic SwitchoverWhen and where to use: When an automatic switchover to the redundant controller is commanded, the followingsequence of events take place.

Process Steps

1 In case of failure of any crucial components causes the standby controller to compare its operational healthagainst the health of the active controller. An automatic switchover is initiated if the standby controller iscapable 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 thecontroller 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 theircurrent site and search for a site in wide area trunking. Since all sites are in local site trunking mode, the radiosreturn 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.12.3.1.1 Radio Scatter, page 5-44.

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

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

The time duration to transition from wide area trunking to local site trunking and return to wide areatrunking 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 trunkingsite, they transmit an Inbound signaling Packet (ISP).

- March 2012 5-43

System Overview

9 The active controller begins gathering the current location of radios and talkgroup members from the affiliationtables 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 receivetalkgroup affiliation information from the other zones before those zones are included in call requests. The timerequired varies depending on the number of radios and talkgroups in the system but in general should be lessthan 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 talkgroupconfiguration information.

5.12.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-6 Call Processing Behavior During Recovery

Call Type Possible Disruptions

Private Calls/TelephoneInterconnect Calls

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

Talkgroup/Announcement Calls Talkgroup members need to have at least one affiliated member known bythe controller at their site, to be included in talkgroup calls.

5.12.3.1.1 Radio Scatter

All of the sites transition to local site trunking mode regardless of whether a controller switchover is automatic oruser-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 inwide area trunking mode unless the site that the radio is currently registered to is set to Always Preferred in the radioprogramming. When no wide area site is found, the radio stops scanning and returns the original site.

Some radios can be registered at more than one site during controller switchover. Multiple registrationscan occur if a radio happens to register to a new site while the radio is also searching the adjacent site listfor 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 controllerswitchover the communications path from the controller to the site is temporarily unavailable preventingthe controller from performing deregistration.

The site transitions to wide area trunking mode when the site reestablishes a link with the controller. The site thennotifies the radios of the change through System Status OSP.

5-44 - March 2012

5.12.3.2 Switching Back to the Standby Controller (User Initiated)

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 uploadsfrom 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, thatthe radio reregister. This must happen before Dynamic Site Assignment can guarantee all intended parties areincluded in the call.

The length of time it takes to update the affiliation tables depends on the number of sites, radios, and talkgroupsin the system, but in general it should be less than twenty minutes from the time the first site transitions back towide area trunking.

As with radios, console affiliations must also be sent to the controller within the zone. This happens within the fistfew minutes after the switchover occurs.

For a given talkgroup to be monitored by the dispatch subsystem, at lease one console affiliation must be receivedfor that talkgroup.

5.12.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 fromthe Zone Database Server (ZDS) or the system remains in local site trunking until the Infrastructuredatabase has been downloaded. The download time varies by system configuration, but in general shouldtake less than 10 minutes.

If for some reason the newly active controller is not functioning properly, you may need to switch the standbycontroller back to active. This is considered a double switchover. The following is a description of what occurswhen performing a double switchover before the standby controller has received the user configuration databasefrom the ZDS.

5.12.3.2.1 Infrastructure Database Download

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

There is no indication that the download has completed other than the controller state changing to enabledidle or enabled active.

The controller begins acknowledging the link requests from the sites once the database is downloaded. A linkrequest contains information such as the site ID. The controller checks the site ID against the information in thedatabase and requests the site's capabilities. The controller instructs the site to transition to wide area trunking if thecapabilities are normal. The controller then requests the affiliation tables for radios and talkgroups. This operation isperformed for every site in the system. The controller handles multiple sites simultaneously.

- March 2012 5-45

6 Dimetra IP System FeaturesTopics Covered in this Chapter

• Voice Services• Data Services• Supplementary Services• Call Logging features• Redundancy of Critical Components• Local Gateway Trunking• Mobility Features• Console Operator Features• Console Management Features• Dimetra Enhanced Software Update

6.1 Voice ServicesThis following describes the voice services offered by the system. Unless stated otherwise, both radios and dispatchconsoles can both initiate and receive these services.

6.1.1 Group CallThe group call service allows a radio or dispatch console to establish a one-to-many communication with a groupof users known as a talkgroup.

The membership of a talkgroup is not a static membership configured within the infrastructure, but is determined bythe radio users who have elected to be a member of that talkgroup at that time. Radios must affiliate with a talkgroupin order to be a member of a talkgroup. Once a talkgroup is assigned to a dispatch console, the dispatch consolebecomes 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 transmittraffic in a call at any time. The system gives transmit permission to a single user. A group call is only terminated bythe system.

6.1.2 Announcement CallAn announcement call is a point to multi-point group call that provides the capability to communicate with multipletalkgroups 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 beassociated with one (and only one) multigroup.

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

- March 2012 6-1

System Overview

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 TETRAIndividual calls. This is a one-to-one communication with only the two parties involved in the call able to hear thecommunication. Hence it is known in Dimetra IP as a Private Call.

Semi-duplex transmission means that only one user can transmit traffic in a call at any time. This is the characteristicmode for private calls in a PMR/PAMR system. Full-duplex transmission means that each user can transmit andreceive traffic (talk and listen) at the same time. Telephone Interconnect calls are always full-duplex, so duplexindividual calls appear to the user to be similar to telephone calls. The full duplex individual call service allows twoparties 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 CallThe telephone interconnect call service gives full duplex communication between a radio and a Private AutomaticBranch eXchange (PABX) or Public Switched Telephone Network (PSTN) user. PSTN access is via a PABX. Fullduplex 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 telephonenumber 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 orradio number the radio.

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

6.2.1 Status Transfer ServiceThe Status Transfer Service allows a radio to send a precoded status message to the dispatch console system. Theservice uses the TETRA Short Data Service over the air interface. Only radios can send a status message and theservice is only supported on the Main Control Channel (MCCH). The status message is delivered to all dispatchconsoles that have the affiliated talkgroup of the radios assigned. The status message is only sent to dispatchconsoles, 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 statusmessage has been delivered to the dispatch console system.

6.2.2 Emergency AlarmThe Emergency Alarm service allows a radio to send an emergency alarm to both the dispatch system and theRadio Control Manager (RCM) application.

Only radios can send an Emergency Alarm and the Alarm is delivered to all dispatch consoles that have theaffiliated talkgroup of the radio assigned. The status message is only sent to dispatch consoles, not to radios thatare members of the talkgroup.

6-2 - March 2012

6.2.3 Short Data Transport Service

The Zone Controller generates an acknowledgment that is returned to the originating radio to indicate that theEmergency Alarm has been received.

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

6.2.3 Short Data Transport ServiceThe 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 registeredwith 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 atthe radios and via an IP connection to the Short Data Router (SDR) in the Dimetra infrastructure. In addition, thereis an internal interface within Motorola radios to the SDTS, used for the Alphanumeric Text Service (ATS).

6.2.4 Alphanumeric Text ServiceThe Alphanumeric Text Service (ATS) enables free text messages to be sent between radios, dispatch consoles andcomputers 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 applicationhas the following features:

• A message list which allows free text of up to 500 characters in Unicode or 1000 characters in ASCII tobe 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 textmessage 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, whomthe 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 optionto 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, theradio rejects the incoming message and the sender receives indication that delivery failed.

6.2.5 Packet Data ServiceThe 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.

- March 2012 6-3

System Overview

Access to the PDS is via the Peripheral Equipment Interface at the radios and via an IP connection to the GGSN inthe infrastructure.

6.2.6 Data ResilienceData resilience is the feature that takes the first steps to eliminate all ’Single Point of Failure’ points for datafeatures: short data and packet data.

The feature includes:

• Warm standby SDR and PDG• Warm standby GGSN• Resilient Mobility Push• Remote failure recovery

6.2.7 Tetra Enhanced Data Services (TEDS)The TETRA Enhanced Data Services (TEDS) feature on a Dimetra IP system, requires a separate NM licence.TEDS is an extension of the current packet data solution in the Dimetra system. It offers higher data transmissionspeed, and its most important features are:

• Use of the 4-QAM, 16-QAM and 64-QAM modulations (in addition to the π/4-DQPSK modulation) andability to choose the most appropriate modulation for the current signal propagation environment.

• Use 50 kHz carrier frequency bandwidth (in addition to the 25kHz carrier frequency bandwidth)• TEDS is only an extension of the current packet data solution in Dimetra IP System and will thereforesupport all the features of the current packet data solution (for example Multi-slot packet data, sendingshort-data messages on PDCH/TEDS channels).

6.3 Supplementary ServicesThe 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 BackBusy Queuing and Call Back is a Dimetra IP service that always supplements the Group Call, Individual Calland Telephone Interconnect services (voice services).

The system supports queuing of voice calls whenever a traffic channel is required and no traffic channels areavailable. If there is no traffic channel available at one or more of the sites required for the call, the call is placed in aqueue. When the required traffic channels for the call become available, the calling party is automatically calledback to indicate that the call has now been set up and has initial transmit permission.

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

6-4 - March 2012

6.3.3 Call Out

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

6.3.3 Call OutA Call Out alert is sent in the form of an individually addressed SDS text message to a radio or individuallyaddressed SDS text messages to multiple radios. The SDS text message can be configured to contain a Talkgroupchange 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 theincident by an audio alarm or a text message with the aim to ask them to go to the scene of the incident. Theusers can then respond back to the dispatcher 'Coming' or 'Not coming'. The dispatcher knows which officers arepresent at the scene of the incident.

6.3.4 Recent User PriorityRecent User Priority is a Dimetra IP service that always supplements the group call service. If, during a groupcall, 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 thesame priority) also waiting for a traffic channel allocation. Recent User Priority lets a talkgroup call have moreconversational continuity when there is a busy queue.

6.3.5 Dynamic Site AssignmentDynamic Site Assignment is a Dimetra IP service that always supplements the group call service. Dynamic siteassignment means that traffic channels are only assigned at sites where there are currently one or more members ofthe 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 StartAll Start/Fast Start is a Dimetra IP service that supplements the group call service. For each talkgroup, the NetworkManager (NM) can set the talkgroup to operate in either All Start or Fast Start modes. In All Start mode, if thesystem is busy and not all resources are available to set up a group call, the system waits for all required resourcesto become available before setting up a call. This ensures that all the sites having members of the talkgroup areincluded when the call begins. In Fast Start mode, the call is set up with whatever sites are available, whileadditional sites are added to the call as and when resources become available. This ensures that calls are set upas quickly as possible even when the system is busy.

6.3.7 Critical Site AssignmentCritical Site Assignment is a Dimetra IP service that supplements the group call service. For each talkgroup, theNetwork Manager (NM) can create a list of Critical Sites. These are sites that must be included in a group call for itto be set up. Thus, even when Fast Start is in operation, the call is not set up until channels are available at all thecritical sites for the talkgroup.

Furthermore, a group-call is always set up at a critical site, whether or not any members of the talkgroup areregistered at the site.

- March 2012 6-5

System Overview

6.3.8 Talking Party IdentificationTalking 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 throughinterruption, then the ID of the new talking party is again forwarded to the other radios or dispatch consolesin the call.

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

6.3.10 Dual Tone Multi-Frequency OverdialDual Tone Multi-Frequency (DTMF) Overdial is a Dimetra IP service that supplements the Telephone InterconnectCall service. This service allows a radio user send digital information as DTMF tones during the conversation phaseof 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 EntryLate Entry is a Dimetra IP service that always supplements the group call and announcement call service. While acall is in progress on a traffic channel, late entry signaling is sent on the main control channel. This lets radios thatfailed to decode the initial call set up signaling (for whatever reason) to join a call in progress. The interval betweenlate entry messages depends on system loading. Late entry signaling is identical to the initial call set up signalingand therefore an radio cannot distinguish between the two.

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

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

6.3.13 Preemptive Priority CallThis feature allows group calls and individual calls for Preemptive Priority Call (PPC) enabled radios, talkgroupsand multigroups to be granted traffic resources by ruthless preemption should there be no free traffic channel at therequesting 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 userinterface.

When traffic resources are available, PPC calls are set up as normal calls, however, if traffic channels are notavailable the Zone Controller preempts the necessary resources from normal calls of lower priority level. The ZCuses the preempted resources to continue the set-up procedure of the PPC call.

6-6 - March 2012

6.3.14 Preemptive Priority Call - Busy User Preemption

6.3.14 Preemptive Priority Call - Busy User PreemptionAny 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 PPCcall takes precedence and interrupt the existing call.

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

6.3.16 Barring of Outgoing Calls (BOC)Barring of Outgoing Calls (BOC) is a Dimetra IP supplementary service of the Telephone Interconnect Call service.Each radio user can be barred by the Network Manager from making outgoing telephone interconnect calls to certainspecified numbers or number ranges. The numbers and ranges are specified in Exclusion Classes. Each radio usercan be associated with a single Exclusion Class. If a radio user attempts to make a call to a number that matches oneof the disallowed dialing patterns in the exclusion class the call is rejected.

6.3.17 Barring of Incoming Calls (BIC)Barring of Incoming Calls (BIC) 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 telephone interconnect calls fromcertain specified numbers or number ranges. The numbers and ranges are specified in Exclusion Classes. Each radiouser can be associated with a single Exclusion Class.

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

6.3.19 RUA/RUIThe Radio User Assignment/Radio User Identity (RUA/RUI) feature makes the system able to assign alphanumericuser names to radio users, and to authenticate the radio users in a logon process. The RUA/RUI feature makes itpossible for a dispatcher or a radio to recognize a radio user by a unique identity that is independent of the IDof the radio.

When RUA/RUI is applied in the system, you can define different profiles for a specific radio user identity (RUI).Some profiles are defined in the infrastructure, and some are defined in the radio. The profiles determine whichcapabilities are available to the radio user. The capabilities available at a specific time depend on whether the radiouser is logged on or not, and whether the radio requires log on or not.

- March 2012 6-7

System Overview

6.3.20 Control Channel ImmunityThe Control Channel Immunity feature maintains high availability of site resources during periods of interferenceand provides security for broadcast control channel information. Control Channel Immunity includes a number ofdifferent 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 theinterference signal exceeds the configured threshold, the Site Controller reverts to an alternate channel at the sitewhich has control channel capability. The primary control channel is removed from service for the duration of theinterference. The alternate channel then provides downlink control signaling and accepts uplink signaling from theradios. The Site Controller may terminate other services on a particular channel when the channel is required forcontrol channel purposes.

When a radio detects a failure or interference condition on the control channel downlink, the radio attempts torevert 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 beconfigured to automatically remove the carrier from service and revert to another available carrier (as describedabove). This operation is similar to the control channel fall back operation which is used during a control channelfailure.

6.3.21 Control Room Head NumberThe Control Room Head Number (CRHN) feature is designed to operate either with Motorola’s MCC7500 consolesor via an ICCS system, interfaced through the ICCS Gateway (ICCS GW).

When applied to an ICCS system CRHN feature defines the Head Number as a group of Console Nodes (resources)in the ICCS gateway and it allows an agency located in an ICCS control room to be uniquely identified in terms ofcall address, regardless of the Dispatch Consoles assigned to this agency. From a logical point of view this uniqueidentity materializes in a Head Number (ISSI) assigned to the agency in that ICCS control room. Therefore there arenot individual numbers/ID’s per dispatcher and it is up to the ICCS control room system to decide which DispatchConsole deals with which call, instead of the individual user calling an individual Dispatch Console.

When the CRHN feature is used directly with Motorola’s MCC 7500 Dispatch Consoles the Head Number groupsa number of consoles in a control room under one unique address and the infrastructure allocates the call toa particular Dispatch Console.

The Head Number (ISSI) is employed by the radio or console users to place individual calls towards an agency ina control room and it is also the number displayed in the radio or console when the user receives an individualor a group call from an agency’s console in a specific control room. The Control Room Head Number feature isconfigurable in the PRNM, and care must be taken in the configuration for the ICCS setup (Console Nodes) or theMCC7500 consoles setup to reflect the operation described above.

The Control Room Head Number feature is license controlled and can be enabled or disabled from the NMT.

6.3.22 Energy Economy ModeThe Energy Economy Mode is a feature on a Dimetra IP system and requires a separate NM licence. This featureenables 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 - March 2012

6.3.23 SDR Audit Logging

6.3.23 SDR Audit LoggingAudit 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 wasperformed. The format of the log file is XML.

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

6.4.1 Central Voice LoggingMotorola’s logging system allows an agency to record audio transmissions as well as certain radio events fromselected talkgroups/channels and individuals in a radio system. These recordings are archived for future playbackand 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 Subsystemmanual.

6.4.2 Discreet ListeningThe Dimetra IP system offer a Discreet Listening feature that enables a user to monitor one to one calls of selectedradios in real time. The Discreet Listening feature comes with a stand-alone PC that can be placed in a secludedroom and offers real-time audio from the selected radio without giving the radio user any indication that the callis being monitored. Monitoring can be performed on one to one calls within the Dimetra IP network and callsusing Telephone Interconnect.

The Discreet Listening feature offers the following:

• Monitoring of two radios simultaneously for the purpose of listening to audio• Real-time audio of one to one calls (radio to radio/radio to telephone/telephone to radio) on monitored radios

- March 2012 6-9

System Overview

• Possibility of connecting a third party recorder

• Log file records of radio activity on monitored radios

• Log file records of Discreet Listening user activities

For further information on the Discreet Listening feature, see the Discreet Listening Feature manual.

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

Redundant components can be added to other parts of the infrastructure — for instance to ensure trafficof short data massages.

Furthermore, the system offers the possibility of geographical redundancy. With geographical redundancy thefunctioning and its redundant counterpart are placed in two different locations. This can be done to avoid physicaldamage to the system that impacts both the functioning and the redundant component.

6-10 - March 2012

6.6 Local Gateway Trunking

Figure 6-1 Zone with Geographical Redundancy

CEN

Core LAN Switch 1 & 2

Core Gateway/ Exit Router(s)

FW1

DMZ Switch 1

MultiCADI

CWR Panel

DMZ Switch 2

RNG1 ECInfo Vista

ZSSUEMZDS

SSSUCS

ATR

MTIG1

ZC1

GGSN1

PDR1

SDR1

AuC

Alias Server

CSMS

Terminal Server 1

PatchPanel

BTSRemote Control Zone

Other Zone

Base StationsControl Rooms

Other Zones

To PABX/PSTN

BorderRouter

PN Routers

UNS

CEN

Core Gateway/ Exit Router(s)

FW2

MultiCADI

CWR Panel

DMZ Switch 3

RNG2ECInfo

VistaZSSUEMZDS

SSSUCS

ATR

MTIG2

ZC2

GGSN2

PDR2

SDR2

AuCBackup

Alias Server

CSMS

Terminal Server 2

PatchPanel

BTSRemote Control Zone

Other Zone

Base StationsControl RoomsOther Zones

To PABX/PSTN

BorderRouter

PN Routers

UNS

Geographical Location 1 Geographical Location 2

DMZ Switch 4

Fib

erF

iber

Application Element

Transport Element

Optional Application Element

Security Element

Core LAN Switch 3 & 4

6.6 Local Gateway TrunkingLocal Gateway Trunking is a disaster recovery feature designed to provide local resource functionality in the eventof 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 systemand provide full voice and short data functionality within the local coverage area of the Dimetra IP system.

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

6.7.1 Agency Priority MatrixThe purpose of the Agency Priority Matrix is to ensure that even in busy scenarios, the most critical radio usersand talkgroups have sufficient RF channel resources. The Agency Priority Matrix controls which talkgroups orradio units are permitted to be assigned a RF channel resource per site in the system. This feature does not preventemergency calls (group or Ambience Listening calls) from being set-up even though the called User Groupspercent of site resources has been reached.

- March 2012 6-11

System Overview

The matrix is a list of partitions known as User Groups that works system wide. A maximum of 100 User Groups isallowed in the system. The matrix contains information on the percent of RF channel resources a User Group isguaranteed to have available in the system on each site where it is configured. Once the User Group list has beendefined, the administrator associates each radio user and each talkgroup to a User Group, both of which are alsopresent on the User Configuration Manager.

6.7.2 Extended RangeRange Extension for Air to Ground Stations is an enhancement of a base station so the existing 58 km cell limit isextended to 83 km.

6.7.3 Subscriber ClassThe Subscriber Class functionality is used to allow radios belonging to certain classes to use certain cells andlikewise 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.

6.7.4 Valid SitesValid Sites is a Motorola Solutions service that supplements the individual and group call service. For each radioand talkgroup, the Network Manager (NM) can define a list of valid sites for the talkgroup. Users cannot use the siteunless 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 validsites 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, foreach site and each radio or talkgroup, enable or disable emergency calls at non-valid sites. This lets users makeemergency calls to a talkgroup even if they are located at a non-valid site for the radio or talkgroup.

6.7.5 Common Secondary Control ChannelCommon Secondary Control Channel is a TETRA standard feature extending the signalling capacity of theMain Control Channel by using one or more additional channels for the messages otherwise only sent on theMCCH. Adding a C-SCCH, removes a channel from the normal voice and data service, so if a C-SCCH is addedwithout 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 determinethe right moment to increase or decrease the number of Common SCCHs. C-SCCH is only supported on the MTS.

6.7.6 eTETRAeTETRA is a feature allowing to extend the capacity of the system operating in the standard 380-400 MHz band (nT)with the channels in the 410-430 MHz band (eT). The system assigns channels to eT-capable radios with preferenceto eT. It is transparent to users whether they have an nT radio or an eT radio.

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

6-12 - March 2012

6.8.1 Assignable Talkgroups

6.8.1 Assignable TalkgroupsIn order for a dispatch console to communicate with a talkgroup, the talkgroup must first be defined as a resourcewithin the console system. This is done using the User Configuration Manager (UCM). Once a talkgroup resourceis define using UCM it can be assigned to individual dispatch consoles. Talkgroups can be assigned to dispatchconsoles permanently (so that they are always available to the dispatch console) using Elite Admin or they canbe assigned temporarily by the dispatch console, in which case they are only assigned until the Elite Dispatchapplication is next closed.

Talkgroups are represented on the dispatch console as talkgroup windows. Talkgroup windows can be displayed inexpanded or compressed format and can be grouped in folders.

6.8.2 Assignable Speakers and Audio SummingThe dispatch consoles are equipped with two speakers, Speaker I and Speaker II. These are assignable to monitorany 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 SpeakerI and Speaker II can be set independently.

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

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

6.8.5 Permanent DisableAs well as Temporary Disable, Permanent Disable is also intended to protect a network from attack from acompromised or faulty radio. It shall be used when the radio is known to have been compromised, or has beensuspected of compromise for a long time.

Permanent disable of radio subscription, signaled by ITSI, allows disabling of subscription either of an integratedradio, or of SIM where a SIM is used. Unlike the temporary disable feature, mutual authentication is a preconditionfor permanent disable.

Permanent Disable is a one way function, there is no equivalent enable function. The radio requires recovery andreprogramming before it can be used again.

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

- March 2012 6-13

System Overview

6.8.7 Console PriorityOnce a group call is in progress, dispatch consoles have the highest priority when the system sets the source ofaudio for the call. This lets a dispatch console interrupt a currently transmitting radio in a group call. There aredifferent levels of priority within the dispatch console system. The table below shows the priority for the audiosource in a group call.

Table 6-1 Console Priority Levels

Priority Level Audio Source1 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 DisplayA status message that is sent from a radio appears in the stack of a talkgroup resource window of the Elite Dispatchapplication. The stack displays up to 24 entries. The talkgroup window in which the status message is displayed isthe talkgroup to which the radio is currently affiliated.

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

6.8.10 Instant TransmitThe Instant Transmit feature lets a dispatch console transmit to an unselected talkgroup with a single action withouthaving 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 receivedaudio is routed to the unselected speaker.

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

6.8.12 Intelligent Call IndicatorThe Intelligent Call Indicator feature lets a dispatch console operator know whether any other dispatch console inthe 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 anotherdispatch console selects the talkgroup, the call indicator stops flashing. The call indicator always flashes on theselected talkgroup.

6-14 - March 2012

6.8.13 Supervisory Console User

6.8.13 Supervisory Console UserMultiple users in the zone may be configured with Supervisory Console User. This means that the console user hashigher 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 theinstant transmit feature.

6.8.14 Console Multi-SelectThis feature enables a dispatch console to transmit simultaneously to more than one talkgroup. A dispatch consolethat 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 eachtalkgroup 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 ConsolePatch, where the talkgroups remain patched until the dispatch console explicitly terminates the patch).

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

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

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

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

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

6.8.19 Ambience ListeningThis feature allows a radio to be remotely set to transmit, without giving any external indication that a call isbeing set up or is in progress. Ambience Listening is implemented as a simplex individual call, so the radio doesnot receive any audio during the call and if the monitored radio is turned off during the ambience listening call,

- March 2012 6-15

System Overview

it continues to transmit, although it appears to have been turned off to the user. Ambience listening is alwaysinitiated by the infrastructure, either from a dispatch console or via a third party application interfacing throughthe console feature API.

6.9 Console Management FeaturesTwo 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 ispresented on each dispatch console display.

6.9.1 User Configuration ManagerThe User Configuration Manager (UCM) is an application used to enter and maintain radio related configurationinformation for the User Configuration Server (UCS).

The UCM configures information for initial configuration of the system and then is used as needed to update theinformation. 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 theUCM, the configuration information updates the UCS and is replicated to the Zone Database Server (ZDS) ineach zone in the cluster.

6.9.2 Elite Admin ApplicationThe Elite Admin application defines how information is presented on each dispatch console. It provides for theconfiguration 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.

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

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

6.10.1 Upgrade ServerThe Upgrade Server (UIS) is part of the enhanced upgrade framework, hosted on the MultiOS zone server. PrimaryUIS application is installed as a container on the Primary Zone Server, while secondary UIS application is installedas a separate container on the Secondary Zone server.

6-16 - March 2012

6.10.2 Upgrade Console

Each zone will deploy its own UIS. UIS is responsible for upgrade application servers within the same zone whereit is located. UIS to UIS interface will use file transfer and remote command execution protocols to synchronizedata between all UIS servers deployed in the system.

6.10.2 Upgrade ConsoleUpgrade Console is a web application used for controlling, executing and monitoring the upgrade process accessedfrom 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.

- March 2012 6-17

7 Dimetra IP Network ManagementTopics Covered in this Chapter

• System Management Objectives and Framework• Serviceability• Network Management System• FCAPS Model in the Dimetra IP System• Multizone Fault Management• Introduction to Network Management Applications

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

7.1 System Management Objectives and FrameworkAs a telecommunications network, the Dimetra IP system needs to be managed as any other telecommunicationsnetwork is managed. The Network Management (NM) subsystem can be viewed as a set of software applications ortools used to manage the system and its components. These tools are intended to maximize the available resourcesand 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 subsystemoffers 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 andthe individual infrastructure components, displaying fault information, forwarding alert information, andperforming diagnostic procedures.

• Configuration Management - Facilities are provided for entering and maintaining the operationalparameters 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 interfaceto third-party accounting and/or billing applications.

• Performance Management - Applications are available for monitoring, reporting, controlling, andoptimizing the use of system resources.

• Security Management - NM includes features for setting user privileges and controlling their access to viewand/or modify information contained in the configuration databases.

Systems continue to grow in size and technical complexity. Work demands are increasing on system administratorswho 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 theircritical missions. Even a brief service interruption or degraded quality of service could impact organizationaleffectiveness, productivity, or safety. Rapid fault detection, notification, and repair require sophisticated tools thatare technologically equal to the managed network. Features and benefits are detailed in the following.

- March 2012 7-1

System Overview

7.2 ServiceabilityServiceability for a Dimetra system, at the MSO, is the capability to provide maintenance of the equipment eitherlocally from a service terminal or remotely through modems or remote LAN connections. To facilitate service to theremote 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.

This clause describes the architecture by which the service organizations and other support functions can getaccess to elements in a Dimetra system. The maintenance procedures and functions such as fault and performancemanagement are described in more detail in 7.6.2 Private Radio Network Management Suite Applications, page 7-19.

7.2.1 Local Serviceability of the MSOLocal serviceability means the ability to service the system from a local service computer, which is colocatedat the MSO.

For a Geographical Redundant Zone every Geographical Redundant Zone MSO (Location) contains a terminalserver. These are the following connection options:

• Connect directly to the affected device and log in

• Connect to the affected device via the terminal server and log in

• Connect to the IP port on the affected device via the LAN switch

• Connect to the IP port on the affected device via the terminal server

Furthermore certain devices support an IP based out-of-band management functionality. This functionality allowsservice of the device even though its standard Ethernet port has failed or even when its operating system hascrashed. A dedicated Ethernet port provides this feature together with the device’s in-build hardware and softwaresupport. The IP based out-of-band features are:

• For HP servers: Integrated Lights-Out (iLO). The HP servers are capable of supporting iLO.

• For Sun servers: Integrated Lights-Out Manager (ILOM) is supported via dedicated NET MGT and SerialMGT port

The ILOM feature on Sun servers and the iLO feature on HP ProLiant servers are together considered as apackage for Lights Out Management of Dimetra devices, called ILOM/iLO feature. For new systems ILOM/iLOis mandatory, while for legacy systems it is optional.

7.2.2 Remote Serviceability of the MSORemote 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 connectedon leased lines.

• Project specific solution: connect to a border router and thus the IP network either via WAN links or via amodem. 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. Whenconnecting, 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 terminalserver’s menu system

• PPP IP connectivity to the MSO devices via the terminal server’s LAN connectivity

7-2 - March 2012

7.3 Network Management System

The remote serviceability access means that a technician is allowed access to elements of the infrastructurefor the following:

• Configuration• Diagnostics• Event Log Reporting

7.3 Network Management SystemThe Dimetra IP system features the Motorola Network Management (NM) System based on the client/servernetworking model.

In the equipment room, the application and database servers run unattended on industrial-class computers based onthe HP ProLiant DL360 G7 server platform. The server applications run on the Operating Solaris™ Environmentfrom Sun Microsystems™, a UNIX® operating system (OS) supported by industry standard network managementapplications and vendors of embedded software solutions.

7.3.1 Client/Server NetworkingApplication processing, data collection and storage are distributed across multiple computer servers and clientPCs connected to a Local Area Network (LAN). The client PCs are commercial personal computers runningthe Microsoft® Windows® operating system for networked computers. Authorized system managers or networkadministrator personnel use the client PCs to start and run the software applications for configuring, viewingequipment operational status, and monitoring network utilization and performance.

The servers are industrial grade, high performance computers geared to handle the intense, typically real-time, dataprocessing tasks associated with managing a single zone or handling specific cluster-level tasks, in multizonesystems.

7.3.1.1 Windows-Based Clients

The NM architecture distributes most of the user application processing to the client PCs. This approach yieldsimportant 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 familiarwith, or easily trained to use, the GUI of PRNM applications that conform to Windows operating systemconventions; and,

• Remote operation performance over a limited bandwidth link (for example, a telephone line used foraccessing 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 configurationinformation for the User Configuration Server (UCS). The User Configuration Manager (UCM) configuresSystem, radios, Security, and ZoneWatch Configuration objects.

• Historical Reports - A management application for multizone systems. Radio traffic statistics frommultizones, including interzone traffic, are accumulated in the System Statistics Server and collated toproduce cluster wide reports.

- March 2012 7-3

System Overview

• 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 licensesfor these applications, and displays the number of licenses that are currently being used. System Profiledisplays information for the following applications:

– User Configuration Manager (UCM)– Historical Reports– 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 areoperating in the zone. In the Zone Profile application, the Application Usage tab displays how zone-levelapplications are being used by the network management clients.

• Zone Configuration Manager (ZCM) - A management application used to enter and maintain configurationinformation for the Zone Database Server (ZDS). The ZCM configures the infrastructure equipment for thesystem. The ZCM is part of the Motorola Private Radio Network Management Suite.

• ZoneWatch - (1) A Windows application that monitors trunking activity and radio call traffic for anindividual zone in real time. This application is part of the Private Network Management Suite. (2) AMotorola software application that allows users to monitor activity within a zone

• Affiliation Display - Affiliation Display is a Private Radio Network Management (PRNM) Suitemanagement application that monitors how radio users travel between different sites in a zone and howthey communicate with other members of their assigned talkgroup or even with members outside of theirtalkgroup within a particular zone.

• Air Traffic Information Access (ATIA) Log Viewer - Data packets that contain talkgroup registration andsite registration and deaffiliation/deregistration information for each radio user in a particular zone. TheAir Traffic Router (ATR) collects this radio traffic information from the Zone Controller and broadcasts aninformation 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, controlchannels, and dynamically blocked calls.

• Historical Reports - A management application producing reports on radio infrastructure and radio resourceusage within an identified zone.

• Fault Manager using Unified Event Manager® - The Dimetra IP fault management application. UnifiedEvent 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 daysof event history.

• Radio Control Manager (RCM) - A management application used to issue commands to radios andmonitor 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 configurationparameters are stored, transactional statistics are accumulated, real-time data streams are sourced, and supportingprocesses are performed. In addition to these “user applications,” the NM servers also run several autonomousprocesses in the background to support the ongoing operation of the system. Applications and processes aredescribed later.

7.3.1.3 Network Management System Servers

Motorola has integrated the NM application and database servers on the HP ProLiant DL360 G7 platform.

The NM subsystem is comprised of the following servers at the zone and system levels of the system:

7-4 - March 2012

7.3.1.3.1 NM Zone-Level Servers (One Each Per Zone)

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• System Statistics Server (used on multizone clusters only)

The role of each server is described in the following:

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 systemapplications. 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 SystemStatistics Server (SSS)

• Hosting the statistics proxy agent for the Zone Controller as a source for dynamic and historical reportsstatistics

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 Managerhandles 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 airinterface load. It derives this information from the Air Traffic Information Access (ATIA) stream supplied by the AirTraffic Router and from the sites. The ZSS serves up this information to the Historical Reports application, which isused to map out zone resource usage and performance.

- March 2012 7-5

System Overview

7.3.1.5 Cluster-Level Servers

The following describes the cluster-level servers.

7.3.1.5.1 User Configuration Server

The User Configuration Server (UCS) provides database storage and backend processes required for most systemwide functions. Included are the radio records, talkgroup records, and services to automatically distribute andreplicate these records in the ZDS for all zones in a multizone system. Only one UCS is required per single ormultizone system. The UCS is accessible to authorized users from any client PC in the single or multizone system.The UCS is installed together with System Statistics Server (SSS) on the same physical server.

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 ofinformation:

• 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, watchwindow definitions, and watch profiles.

• External Configuration - Registration and configuration of all zones, RF sites and call routes that have beenconfigured in other clusters of the system.

7.3.1.5.2 System Statistics Server

The System Statistics Server (SSS) is the data repository for the statistics necessary to drive system wide HistoricalReports. The SSS is required only with multizone systems. Statistics such as the number of calls, push-to-talks,and busies are accumulated over preset time intervals. Data accumulated on an hourly basis for 10 days, daily for62 days, and monthly for one year. The SSS is installed together with User Configuration Server (UCS) on thesame physical server.

7.3.2 Core ServicesIn addition to the user applications, the NM system performs a number of vital tasks and “core” services essentialto its operation and maintenance. Network manager user authentication is one of the core tasks performed inconjunction with the ZDS. Another is the Application Launcher on client workstations from where each userapplication is started. The applications available to the user are displayed in a Microsoft® Explorer window; theLicense 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. TheZDS 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 isreplicated in each ZDS, the system includes an application to rebuild the UCS database from the ZDS, thus providingan automatic backup of the user configuration database.

7-6 - March 2012

7.4 FCAPS Model in the Dimetra IP System

7.4 FCAPS Model in the Dimetra IP SystemThis section details the FCAPS model as it applies to Dimetra IP systems. Many applications deal with one ore moreareas 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-9• S for 7.4.5 Security Management, page 7-10

7.4.1 Fault ManagementFault Management encompasses fault detection, fault isolation, and correction of abnormal operation. Centralfault 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 Managerprovides a centralized view of the operational status of an entire multizone or single zone system by displayingintuitive, graphical representations (subsystem topology maps) of the system. Problems are identified rapidly whenthey occur. Functions and tools also provide the ability to notify support personnel, track, diagnose, and correctfaults in an effective manner. Unified Event Manager also maintains a data warehouse, storing up to 30 days ofevent 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 ManagementConfiguration Management gives the operator an interface for configuring the system. The interface specifies theoperational parameters of devices used within a system, such as sites, base radios, switches, radios, individualusers, and groups. Configuration Management establishes each component in the system, its relationship to othercomponents, 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. NMapplications 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 maintaincluster-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 storesparameters 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

- March 2012 7-7

System Overview

• Radio user and group access to each site in the system. A network manager can limit a radio user or group toone 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

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 variouslife stages of the system. Every zone has a ZCM to manage infrastructure in the zone, and each zone can support upto 100 sites, each with different infrastructure equipment. Types of information managed by the ZCM includes radiosystem infrastructure information for sites and equipment.

7.4.3 Accounting ManagementAccounting Management enables charges to be established for the use of resources in the system. The central tasksaccomplished 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 communicationobjective

The NM subsystem provides an optional licensed interface, Air Traffic Information Access (ATIA), to whichthird-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 ofcalls, total call duration, number of busies, total busy time, and so on. This data can be used as input to an externalaccounting 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 orservices, ATIA allows the system owner/operator to generate billing information to charge individual departments oragencies 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 beviewed on a client PC.

7.4.3.4 Data Services Billing — Packet Data

The Packet Data Charging service is a feature that provides a billing system of a customer with raw data on utilizationof each radio within the Dimetra Packet Data service. The utilization of the packet data service is captured in the CallDetail Records (CDRs). Based on this data radios can be charged for the usage of the Packet Data bearer service.

The billing feature allows charging of every IP datagram routed to and from the Dimetra system.

7.4.3.5 Data Services Billing — Short Data

The Short Data Billing system allows charges to be made for every transmitted short data message in a Dimetrasystem. The Billing Information is stored on hard disk drives and can be downloaded (polled) by the customer viathe standard FTP protocol. The customer is responsible for the specification and provision of a suitable DownstreamBilling Processor (DBP). It is possible to switch SDS Billing on and off.

7-8 - March 2012

7.4.4 Performance Management

The Billing Mode, Billing Triggers and other billing parameters are configured locally at each Billing Node (SDR).

The billing system is monitored by the Unified Event Manager sub system and in case of any fault Unified Eventmanager is notified by an alarm from the related SDR.

7.4.4 Performance ManagementPerformance Management tools are used to monitor, collect, log, and evaluate network performance and resourceutilization data. Performance applications for the radio resources are described here.

NM collects statistics of radio resource usage in the Zone Statistics Server (ZSS) and System Statistics Server (SSS)for radio units, talkgroups, channels, sites, zones and system wide activity report generation.

Separate, performance applications display real-time communications activity (such as, ZoneWatch) or collect trafficstatistics over predetermined intervals for report generation (such as, dynamic and historical reports). Historicalstatistics are aggregated into detailed and summarized reports on both an individual site, zone, and system widebasis. 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 arealso collected. The system logs these statistics for a period of 62 days. NM also has archival and export featuresfor 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 anidentified zone. A predefined set of reports, with field selection capability, is supplied to produce “standard” ortailored reports. Custom reports can be developed using Historical Reports underlying Crystal Reports® reportingengine.

Historical reports are generated automatically or on demand. Automatic reports are produced at a specific scheduledtime and date or on a recurring time and date interval. Reports can be sent to the monitor screen, a printer, or savedas PDF, XML, HTML or Comma Separated Value (CSV) files.

7.4.4.2 System Wide Historical Reports

The system wide Historical Reports application is introduced with the NM system for multizone systems. Radiotraffic statistics from multizones, including interzone traffic, are accumulated in the System Statistics Server andcollated to produce system wide reports.

7.4.4.3 Dynamic Reports

Dynamic Reports are intended for short term monitoring. Report intervals may be set for 15 seconds, one minute or15 minutes, and up to 100 intervals can be collected. Multiple objects and up to 12 statistics can be included in asingle report. Like for the Historical Reports, a complete set of predefined Dynamic Reports is provided. Reportscan 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.4 ZoneWatch

ZoneWatch is a performance management tool having customizable displays and grids to monitor real-timecommunications activity in a single zone. The information displayed can help system managers be proactive inmaking 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 callactivity 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, tracethe progress of a call and troubleshoot, or analyze current system activity. It also provides information about activityoccurring on the control channels, such as rejects, emergency alarms, and unit affiliations.

- March 2012 7-9

System Overview

7.4.4.5 Affiliation Display

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

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 whichthe 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 ManagementSecurity Management controls or limits access to applications, certain features, and configuration data according todefinable access privileges. All users must identify themselves to the system at logon by entering a name/ID and apassword. The Agency Partitioning feature makes it easy to grant or restrict access by department, location, usertype, 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. Theradio is unable to make or receive calls while it is disabled, even if the radio is turned off and turned back on. If theradio 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 acompromised or faulty radio. It shall be used when the radio is known to have been compromised, or has beensuspected of compromise for a long time.

Permanent disable of radio subscription, signaled by ITSI, allow disable of subscription either of the integratedradio, or of SIM where a SIM is used. Unlike the temporary disable feature, mutual authentication is a preconditionfor 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 witha new codeplug.

Permanent Disable is a one way function, there is no equivalent enable function. The radio requires recovery andreprogramming 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 applicationsunless the user enters a valid logon name/ID and the corresponding password.

7-10 - March 2012

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 systemadministrator 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 sendsa challenge to a registering radio. The radio must supply the appropriate response to access the system. If mutualauthentication is being used, then the radio also sends a challenge to the infrastructure, and the infrastructure mustsupply 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 inthe Provisioning Centre, Authentication Centre, and in the radio. For the Provisioning Centre and AuthenticationCentre, each key is stored in a secure form in a database encrypted with a tamper-proof crypto card. The key are alsostored 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 thesystem infrastructure. Encryption prevents scanners and other more sophisticated equipment from collecting anyintelligible traffic from users in the system. Encryption also prevents unauthorized users from being able to operateon the system without the appropriate key.

The Dimetra IP system offers various air interface security features. See the list of them and the purposes theyserve 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 airinterface using dynamically generated keys to protectagainst eavesdropping.

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

Encryption of a user and signaling data over the airinterface using predefined keys to protect againsteavesdropping.

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 operationand 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 keysare stored in a secure form in a database encrypted with a tamper-proof crypto card. The keys are also stored asecure 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 CipherKeys (CCKs), which are used for group calls, are sealed with a DCK and sent over the air to radios for group calls aswell as MGCK - the combination of GCK and CCK. The typical duration for the use of a CCK and DCK in thesystem is 24 hour and for GCK - 3 months.

7.5 Multizone Fault ManagementMultizone fault management can be achieved through a network management client that has access to UnifiedEvent Manager applications in each individual zone in the system. Since one Unified Event Manager server actsas a zone-level server in each zone, the client can view a zone connecting with the Unified Event Manager in theappropriate zone within a particular zone.

- March 2012 7-11

System Overview

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-suppliedfault management system. This central fault management system can receive the forwarded traps from all zone-levelUnified Event Manager servers in the system. The figure below illustrates the event forwarding from each zoneUnified Event Manager server to a customer-supplied fault management platform.

Figure 7-2 Multizone Fault Management- Event Forwarding to a Customer-Supplied FaultManagement System

7.5.1 Multicluster Network ManagementNetwork Management of a multicluster system can be achieved through a network management client that isproperly configured with access to the individual clusters and zones. The properly configured client can accessand modify settings in each of the clusters and their corresponding zones.

The Dimetra IP system supports centralized fault management collection for the entire system through a Manager ofManagers platform.

7-12 - March 2012

7.5.2 Multicluster Configuration Management

7.5.2 Multicluster Configuration ManagementMulticluster configuration management can be achieved through an NM client. Properly configured networkmanagement clients can centrally access and modify the configuration settings each cluster individually in the system.

Figure 7-3 Multicluster Network Management - Client Access to Each Cluster

7.5.2.1 User Configuration Server API

Each UCS also provides an API, which provides an interface for a customer-supplied provisioning system that can beused for centralized nationwide configuration. This allows a centralized, coordinated configuration of all the clustersthroughout the system. It also helps to eliminate any conflicts of radio users, talkgroups, dispatch call services, andinterconnect call services across different clusters. The figure illustrates nationwide provisioning using the UCS API.

- March 2012 7-13

System Overview

Figure 7-4 Multicluster Configuration Management - Provisioning through the UCS API

Certain objects must be coordinated between clusters to allow radios to roam between clusters, to define call routesacross clusters, to define adjacent remote sites between clusters, and to support talkgroups and multigroups withmembers in multiple clusters. The UCS API supports provisioning and coordination of the following objects inmultiple clusters.

• Radio

• Radio User

• Radio User Capability Profile

• Radio User Interconnect Profile

• Talkgroup

• Multigroup

• Home Zone Mapping

• BTS Site

• Call Route

• External Call Route

Call routes and BTS site objects are defined in the individual zones in each cluster. The UCS API allows theseparameters to be uploaded from one cluster and downloaded into another cluster. Home zone mapping must beidentical in all clusters.

7-14 - March 2012

7.5.2.2 Infrastructure Reports

7.5.2.2 Infrastructure Reports

The Infrastructure Reports provides daily reports of selected infrastructure configuration data in a machine readableformat. The reports can be collected and used for system documentation, configuration control, configuration changeaudit - or any other purpose. The reports are provided for two boxes in the Dimetra system:

• The Zone Database Server (ZDS)• The Short Data Router (SDR)

The Infrastructure Reports are provided as files generated at a particular point in time during the night. The files canbe collected via FTP, using a special account for report collection. The format of the files is XML. The format isboth ideal for use by computer programs, and for reading by human beings.

It is the responsibility of a system external to the Dimetra system to collect the XML files. The interface doesnot provide any mechanism to ensure that files are collected, and the files on the ZDS and SDR are overwrittenafter one day.

Figure 7-5 Infrastructure Reports Architecture

The UCS does not provide a report interface. As all relevant data are replicated to the ZDS, the UCS data is availablevia the ZDS. Note that this implies that all ZDSs in a cluster provide identical UCS data.

The following data is available from the ZDS:

• Zone: Contains numerous call control and similar, related parameters. Zone specific.• BTS: Contains numerous call control and similar, related parameters. Zone specific.• BTS Base Radio: Mainly included to ensure that Base Radios are not added or deleted by mistake. Zonespecific.

• BTS Receiver: As Base Radio. Zone specific.• BTS Channel: Contains a number of call control and data related parameters. Zone specific.• System Object: Contains numerous parameters with cluster-wide scope. Identical for all ZDSs in a cluster.• Data System Object: Contains numerous data related parameters with cluster-wide scope. Identical for allZDSs in a cluster.

• Adjacent Control Channel: Contains data changed due to RF planning changes. Identical for all ZDSsin a cluster.

- March 2012 7-15

System Overview

For the SDR, all configuration information is available.

7.5.3 Multicluster Performance ManagementMulticluster performance management can be achieved through a properly configured network management client.The client can generate historical reports for each cluster individually. The client can also run InfoVista® reports forrouters in each cluster individually.

Figure 7-6 Multicluster Performance Management - Client Access to Each Cluster

7.5.4 Multicluster User Configuration Server SynchronizationThe UCS Synchronization Tool automates the exchange of the most important and numerous types of infrastructureconfiguration data between clusters. This tool supports the synchronization of the following records from a centrallocation:

• Home zone mapping• BTS sites• Call routes

BTS sites and call routes can be extracted from one cluster and inserted into some or all other clusters. A specifichome zone mapping table can be extracted from one cluster and inserted into some or all other clusters.

The UCS Synchronization Tool also supports import/export for offline updates of the home zone mapping tables. Ahome zone mapping table can be extracted from a cluster and saved to a file for offline updates. The updated homezone table can then be loaded into some or all other clusters.

7-16 - March 2012

7.5.5 Multicluster Authentication Centre Synchronization

7.5.5 Multicluster Authentication Centre SynchronizationOne AuC in a multicluster system is manually chosen as the master AuC. If the master AuC becomes unavailable, theremaining AuCs choose a new master amongst themselves. The master AuC distributes Static Cipher Keys (SCKs),Common Cipher Keys (CCKs) and system KEK (KEKm) to the other cluster AuCs in the system. This distributioncan be commanded by an AuC administrator or can be performed automatically according to a defined schedule.

During an update, each cluster AuC receives the keys and administers the key update to its local cluster. Eachcluster AuC then responds to the master AuC with the status of the update. All the AuCs in the system must beoperational when a key update is in progress.

Authentication material is managed locally by each AuC, independent of the master AuC.

7.6 Introduction to Network Management ApplicationsThe following provides a brief overview of each application used to manage your radio system, describes keyfeatures, and explains how to find additional information about the application within your documentation set.

. The following describes the function and the process for accessing the Network Management Applications. Itincludes information on the Private Radio Network Management (PRNM) Suite Application Launcher and theTransport Network Management Application Launcher.

This following contains:

• 7.6.1 Network Management Applications Overview, page 7-17• 7.6.2 Private Radio Network Management Suite Applications, page 7-19• 7.6.3 Network Transport Management Applications, page 7-27

7.6.1 Network Management Applications OverviewA network management application is a software tool that helps you to manage a complex radio communicationssystem 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 following lists the Motorola Private Radio Network Management (PRNM) Suite applications. The PRNM Suiteis 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.

- March 2012 7-17

System Overview

Figure 7-7 PRNM Applications From a System Perspective

The table lists the Motorola PRNM Suite applications. These management applications are available throughApplication Launcher.

Table 7-2 Motorola PRNM Suite Applications

Applications FCAP-S Purpose

Application Launcher N/A A launch point for PRNM applications.

Cluster-Level Applications:

Historical Reports (System Wide) AP A reporting tool that uses predefined reports to show data fromarchived information.

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. Showsthe number of applications open, who is using the application,the number of available licenses, and the processes of the openapplications.

User Configuration Manager CS The primary tool to configure and manage radio network users.

Zone-Level Applications:

Affiliation Display P A tool to monitor radio, talkgroup, and site use. AffiliationDisplay 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 zonein a raw data format from the Air Traffic Router (ATR).

Dynamic Reports AP A report tool that provides predefined reports using data takendynamically from the database.

7-18 - March 2012

7.6.1.2 Other Motorola Applications

Table 7-2 Motorola PRNM Suite Applications (cont'd.)

Applications FCAP-S Purpose

Unified Event Manager includes:

• Unified Event ManagerAdministration

• Unified Event ManagerWeb Browser

• Unified Event Manager

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

Historical Reports AP A reporting tool that uses predefined reports to show data fromarchived information. Historical Reports spans zone, site, andunit 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 thefigure above.

Zone Configuration Manager C The primary tool used to configure infrastructure equipment andother zone-level parameters.

Zone Profile P A tool to track usage at a zone level. Shows the number ofapplications open, who is using the application, the number ofavailable 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.

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 FCAP-S Purpose

Dimetra™ BTS (BaseTransceiver Station)

CF A tool used to configure and service the Site Controllers and BTS baseradios.

Customer ProgrammingSoftware (CPS)

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

7.6.2 Private Radio Network Management Suite ApplicationsThe following describes the PRNM Suite applications, including how to access the applications using ApplicationLauncher.

- March 2012 7-19

System Overview

7.6.2.1 Application Launcher

Application Launcher is the starting point to access the PRNM management Suite applications. ApplicationLauncher provides a quick and easy way to access one or more management applications without going through theprocess 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. Thesystem 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 bydisplaying only the cluster-level applications, zones, and zone-level applications for which you have accesspermissions in the Windows Explorer window.

Application Launcher allows you access to the applications that manage and monitor the clusters and zones. It alsoallows 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 othermembers of their assigned talkgroup or even with members outside of their talkgroup. You can view a radioin more than one zone.

As a radio roams from one site to another or changes talkgroups, Affiliation Display updates and displays theaffiliation 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 canbe useful for troubleshooting and tracking of radios in the system and for monitoring the movement of trafficwithin 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 locatespecified 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 attalkgroup or radios at talkgroup.

Affiliation Display can be used to perform the following functions:

• Monitor selected radios, talkgroups, and sites dynamically using the main window. Monitors affiliation anddeaffiliation 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. Bytracking 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 usageinformation is captured in a graph format for talkgroups and sites.

7-20 - March 2012

7.6.2.3 ATIA Log Viewer

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, noATIA log data is collected for viewing. See Master Site Core Elements, Network Management Subsystemfor detailed information. Data for Historical and Dynamic Reports is collected regardless of the ATIAlog setting.

The ATIA Log Viewer is a technician tool that allows you to examine air traffic historical data in a specified zonefor 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 radioaffiliations.

• 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 timeinterval or intervals. This feature is normally used to examine data logs when debugging the system. The ATIA LogViewer 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 theinformation displayed in the ATIA Log Viewer is a text document, you can format the information, if requiredusing 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-partyapplication (Seagate® Crystal Reports®) but the difference is that you can create your own reports. You select theparameters for the report instead of using predefined parameters and templates that Historical Reports uses.

If you need to customize your performance reports (zone-level and cluster-level Historical Reports only), theCustom Historical Reports is an software package that allows you to modify existing report templates and createnew templates to meet your system needs.

Using a report generator, you create a customized report with the parameters that you want. Custom HistoricalReports uses Crystal Reports® to step you through a series of dialogue boxes to define each set of parameters thatyou could include in the report.

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 theATIA 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

- March 2012 7-21

System Overview

– 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 todisplay 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 providespredefined parameters and template formats to display the value of multiple statistics for one or more managedobjects. Once a report is activated, a Dynamic Report window appears and data is plotted according to the objectand 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 thespecified 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 happensduring 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 toimprove 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. Youcan use Unified Event Manager to monitor the status of the zones.

Unified Event Manager allows you to monitor the status of components at zone level, such as servers, ZoneControllers 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 useUnified 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 ManagementProtocol (SNMP), the industry standard communication protocol.

Unified Event Manager integrates the fault management of Motorola devices and that of approved third-partydevices.

7-22 - March 2012

7.6.2.7 Historical Reports

7.6.2.7 Historical Reports

Historical Reports is a PRNM Suite application that allows you to generate reports for cluster wide activity andfor individual zones. These reports display data that is stored on the server. You can use Historical Reports forresource management. For example, you can determine if interconnect resources are being overused because toomany 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 timeintervals. 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. HistoricalReports 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 useHistorical 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 formatis 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 ofexternal applications such as Web browsers and word processors.

• Use the Report Scheduler window to schedule zone-wide and system wide reports to occur automatically atspecified 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 monitorcommands, 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 statusinformation. 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 thecommands. After you issue a radio command, you can view the command and its status in the CommandMonitor.

• 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 unsolicitedmessage 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 usingthe 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 exportstandard reports from RCM. These reports use a common format so the data can be used in spreadsheets. The reportinformation is gathered from current or archived entries in the RCM. RCM Reports enables you to present andanalyze data showing RCM activity on the system.

You can create reports that show the following:

• Current Login sessions-View who is currently logged in.

- March 2012 7-23

System Overview

• Emergency alarm reports-Monitor a historical list of emergency alarms received by RCM in a selectedperiod.

• 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 otherapplications. 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 softwarefrom a central location at the zone core or locally at a remote site. Software Download supports loading to the SiteControllers 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 orchanged via the script, the configuration file can be downloaded to the base station again by the SoftwareDownload application. There is a single configuration file set for the base station which can be downloadedto the SC

• When using the Software Download application, base station software files can be downloaded to morethan 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.6.2.11 System Profile

The System Profile is a PRNM Suite application that displays how cluster-level applications are being used by thenetwork management clients. System Profile shows the following cluster-level Private Radio Network ManagementSuite (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-levelapplications that are being run on network management clients in the system. The User ApplicationDistribution 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 applicationsand 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 relatedconfiguration information for the User Configuration Server (UCS).

7-24 - March 2012

7.6.2.13 Zone Configuration Manager

The UCM configures information for initial configuration of the system and then is used as needed to update theinformation. 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 theUCM, the configuration information updates the UCS and is replicated to the Zone Database Server (ZDS) ineach 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.

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 userinformation. 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 securityinformation.

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

External Configuration Registration and configuration of all zones, BTS sites and call routes that have beenconfigured 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 maintainoperational parameters for equipment in the zone. The Zone Database Server (ZDS) hosts the ZCM database, whichstores 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 asthe 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 BTSsites. The table shows the high-level objects.

- March 2012 7-25

System Overview

Table 7-5 High-Level Objects in ZCM

Object Types DescriptionZone Configures and manages the attributes relating to a zone.

Air Traffic Router Configures the ATR server, which collect statistics on the system and distributesairtime usage data.

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

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

Packet Data Gateway Represents the packet data gateway.

Application Platform Configures the application platform, which hosts the MTIG application. Providesaccess 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 sothat it functions correctly in the system.

Switch Configures the switch within a zone, plus the paths, slots, and cards, and connectionsfor the switch.

Interconnect Subsystem References the telephone interconnect equipment in the zone and represents the pathselection 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 operatingin 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 ZoneController.

7-26 - March 2012

7.6.3 Network Transport Management Applications

ZoneWatch uses different types of watch windows to display zone, site, talkgroup, and radio information for aspecific zone. The different window profiles, which contain window definitions and filters, define how to displaythe information and how to apply limits to the type of data that you can view. The following are examples ofthe 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 seeconstantly updated information on who is using the system, where the radio users are located, whatinfrastructure 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.• Raw Data A Raw Data filter allows the selection or exclusion of information. The data that is selected forinclusion 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 essentiallylimits the view to only a specific site in a zone. You can, however, have other windows open to showinformation from other sites in the zone.

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

7.6.3.1 InfoVista

InfoVista® is a customizable performance management application that interfaces with network devices supportingSNMP. By importing Management Information Base (MIB) files, InfoVista® can report and graph a wide varietyof data from multiple devices, such as routers and core LAN switches .

InfoVista® performs the following performance management tasks:

• Collects MIB data at any specified time interval.• Displays the collected data in daily, weekly, monthly, and yearly reports.• Reports and graphs single and multiple device information.• Provides customized reports using preconfigured standardized report templates for network transport devices.

InfoVista® is primarily a performance management tool that provides individual and group report types. Each reporttype has four templates to provide daily, weekly, monthly, and yearly reports.

You can use InfoVista® reports for proactive network performance, troubleshooting, and network capacity planning.Use InfoVista® to do the following:

• View Motorola custom reports for the Motorola network routers, Cisco® routers, core LAN switch, and theTransport Network Performance Server (TNPS).

• Filter (search) for a particular report.• Use the traps sent to HP OpenView and daily individual reports for troubleshooting purposes.• Navigate folders that are organized by system and zone.• Monitor the system for troubleshooting clues. You see activity on a device and use it to troubleshootthe device.

7.6.3.2 Transport Network Configuration Tool (TNCT)

Installed on the Network Management (NM) Client PC, the Transport Network Configuration Tool (TNCT)allows you to view configuration of the transport system devices for your Dimetra system, and perform networkmanagement tasks, which include:

• Configuration Backup

- March 2012 7-27

System Overview

• Configuration Batch Backup

• Configuration Restore

• Configuration Deployment

• GGSN Router Management

• Firmware Deployment

• Setting Boot Source for the device

• Initial Configuration Setup using serial connection

• Checking firmware version

TNCT provides configurations for the following devices and roles within your radio system. An (*) next to thedevice name indicates that TNCT provides dedicated deployment support for that device:

• Core Router

• Core LAN Switch

• Exit Router

• Gateway Router

• NM Dispatch Site Router, Site Switch (*), and Terminal Server

• Zone Terminal Server (*)

• Ethernet Core Gateway Router

• Ethernet Site Router

• Backhaul Switch

• Eth-Exit Router

• Eth-Core Router

• iLO Switch

7-28 - March 2012

Appendix A: Dimetra IP SystemDocumentation

This appendix provides a listing of manuals applicable to the hardware, software, and features in a Dimetra IP system.

Table A-1 List of Dimetra IP System Documentation

Document Title Description Dimetra IPScalable

Dimetra IPCompact/ScalableDimetra IP

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

Documentation Overview The document provides a list of all documentsdelivered with your Dimetra IP system. Its primarypurpose is to help you to find the information youare looking for.

System Overview This manual provides basic radio system concepts,call processing basics, and an introduction to thevarious components and processes associated withthe Dimetra IP system. The manual provides thebackground needed to comprehend the theory ofoperation and it provides equipment/subsystemfunctional descriptions. It also describes the roleof the numerous network management softwareapplications used for managing the system.

Standards and Guidelinesfor Communication Sites

This manual provides standards and guidelines tofollow when setting up a Motorola communicationssite. Also known as R56 manual.

Master Site Overview This manual provides an overview of the componentslocated at a master site and short descriptions oftheir function. The manual includes system diagramsof the master site and of the various subsystemslocated at the master site. The manual also includesan overview of installation of hardware and softwareat the master site, and it contains the standard racklayouts.

Zone Controller This manual describes the Zone Controller whichis responsible for processing calls, managing audiopaths, controlling zone infrastructure, and providingservices to subscribers and console operators.

System LAN Switches This manual describes LAN switches used in theDimetra IP system. Included are detailed proceduresfor installation, configuration and operation.

- March 2012 A-1

System Overview

Table A-1 List of Dimetra IP System Documentation (cont'd.)

Document Title Description Dimetra IPScalable

Dimetra IPCompact/ScalableDimetra IP

S6000 Router This manual describes the S6000 router used in theDimetra IP system. The router provides the followingnetwork transport functions for the whole system:

• Router used in E1 configurations, includinggateway, core, and exit routers

• Router used in Ethernet configurations, includingdiscreet and combined routers

GGM 8000 Gateway This manual describes the GGM 8000 Gateway andhow it is used in the Dimetra IP system. Includedare detailed procedures for installation, configurationand maintenance.

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

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

• Base station links (single and redundant)

• Inter-zone links

• Remote control site links terminated atnon-redundant control site routers

Link Encryption This manual describes the technical solution forRouter Encryption and Authentication, which is anextension to the Ethernet Site Links (ESL) feature.

Network ManagementServers

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 serverscomprise the User Configuration Server (UCS),System Statistics Server (SSS), Zone DatabaseServer (ZDS), Air Traffic Router Server (ATR), ZoneStatistics Server (ZSS) and Unified Event Manager(UEM) Server.

Network ManagementClient

This manual provides an introduction to the hardwareand software components associated with theNetwork Management (NM) Client. Included aredetailed procedures for installation and configurationof the client.

A-2 - March 2012

Appendix A Dimetra IP System Documentation

Table A-1 List of Dimetra IP System Documentation (cont'd.)

Document Title Description Dimetra IPScalable

Dimetra IPCompact/ScalableDimetra IP

Remote Access This manual describes the Terminal Server whichis used for local and remote serviceability, alsoreferred to as out-of-band management. The manualprovides an introduction to the hardware and softwarecomponents associated with the Terminal Server.Included are detailed procedures for installation,configuration and troubleshooting the TerminalServer.

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

Backup and RestoreIncluding FRU/FRE

This manual describes the system backup andrestoration procedures and their impact on theservices as well as pre and post-restoration checks.The manual also describes how to perform FRU/FREprocedures.

Safety Guidelines forInstallation of Hardwareand Software

This manual describes the general safety guidelinesto be followed in connection with installation ofhardware and software.

Server SoftwareRestoration

This manual describes how to perform restorationof all application servers. Additionally it containsinstructions for scheduling or creating a backupon-demand.

Server HardwareRestoration

This manual describes how to perform restoration ofall system servers hosting application servers. Themanual also describes how to perform FRU/FREprocedures for these servers.

Stand-alone ComponentsRestoration

This manual describes how to backup and restore thefollowing components of the system:

• Network Management (NM) Client

• Standalone Provisioning Centre (PrC) Client

• Key Management Facility (KMF)

• Echo Canceller

• CryptR2

Network TransportRestoration

This manual describes how to backup and restore thesystem LAN switches, routers, gateways, CWR PatchPanel, Terminal Server, and Network Time Server.

Console Site Restoration This manual describes how to backup and restore allcomponents of the MCC 7500 Subsystem, both itsclear and secure versions. The manual also describeshow to perform FRU/FRE procedures.

- March 2012 A-3

System Overview

Table A-1 List of Dimetra IP System Documentation (cont'd.)

Document Title Description Dimetra IPScalable

Dimetra IPCompact/ScalableDimetra IP

Base Station Restoration This manual describes how to backup and restorethe Motorola Transceiver System (MTS) and theEnhanced Base Transceiver System (EBTS). Themanual also describes how to perform FRU/FREprocedures.

Backup and RestoreAppendices

The Appendix provides information onBackup/Restore Collector Application, PeriodicMaintenance Inspection (PMI) and ServiceInformation.

Fault Management This manual provides an overview of FaultManagement features.

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

ZoneWatch This manual describes ZoneWatch which is aPrivate Radio Network Management (PRNM) Suiteapplication that lets you monitor radio call trafficfor an individual zone in real time. ZoneWatch usesdifferent watch windows that allow you to displayonly the information you need to see.

System and Zone Profile This manual describes the System Profile applicationand the Zone Profile application which are both aPrivate Radio Network Management (PRNM) Suiteapplication. The System Profile application displayshow system-level applications are being used bythe network management clients. For instance, youcan view information for applications in the systemincluding the total number of applications purchased,number of licenses in use, and who is currentlyusing the application. The Zone Profile applicationdisplays detailed information about applications thatare operating in the zone. You can use Zone Profileto view the zone-level application usage and view thezone-level application license usage.

System Alarms and Events This manual lists all the possible alarms for thesystem. It also covers transient alarm messages,which are known as technician messages. Thismanual is intended for technicians, networkmanagement personnel, or any other engineeringpersonnel with responsibility for troubleshooting ormonitoring the operational status of the system.

A-4 - March 2012

Appendix A Dimetra IP System Documentation

Table A-1 List of Dimetra IP System Documentation (cont'd.)

Document Title Description Dimetra IPScalable

Dimetra IPCompact/ScalableDimetra IP

User ConfigurationManager

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

Zone ConfigurationManager

This manual describes the Zone ConfigurationManager (ZCM) which is a Private Radio NetworkManagement (PRMN) Suite application. TheZCM is used to configure and maintain operationalparameters for equipment in a system. To configurea system, both the ZCM and the User ConfigurationManager (UCM) are needed.

Configuring Features This manual describes radio features and theirconfiguration. The manual contains a configurationchecklist as well as configuration procedures for thekey features of the system.

Software Download This manual describes the Software Download(SWDL) Manager which is a Private Radio NetworkManagement (PRNM) Suite application that cantransfer and install new software in the Dimetra IPBase Transceiver Systems (BTS).

Radio Management This manual describes the radio features available toradios in the Dimetra IP system.

Affiliation Display This manual describes Affiliation Display which is aPrivate Radio Network Management (PRNM) suiteapplication. Affiliation Display enables you to viewthe association of a radio with a talkgroup and site,information about conventional channels, consolesites, and consoles and to monitor how radio userstravel between different sites in a zone and how theycommunicate with other members of their assignedtalkgroup or even with members outside of theirtalkgroup.

ATIA Log Viewer This manual describes the Air Traffic InformationAccess (ATIA) Log Viewer which is a Private RadioNetwork Management (PRNM) Suite application thatdisplays log files generated by the Air Traffic Router(ATR). These log files contain records of all recentzone activity, such as site registrations and callsprocessed. ATIA Log Viewer allows you to view theraw ATIA data straight from the ATIA log.

- March 2012 A-5

System Overview

Table A-1 List of Dimetra IP System Documentation (cont'd.)

Document Title Description Dimetra IPScalable

Dimetra IPCompact/ScalableDimetra IP

Radio Control Manager This manual describes the Radio Control Manager(RCM) which is a Private Radio NetworkManagement (PRNM) Suite application usedprimarily by dispatchers to monitor and manage radioevents, issue and monitor commands, and makeinformational queries of the system database.

Radio Control ManagerReports

This manual describes the Radio Control Manager(RCM) Reports which is a Private Radio NetworkManagement (PRNM) Suite application that is usedto create, view, print, schedule and export standardreports from RCM. These reports use a commonformat so the data can be used in spreadsheets. Thereport information reflects the actual RCM serverdatabase information except the Emergency Alarms.

Fleetmapping This manual describes how to properly plan for,set up, and manage your system. The Motorolaengineering team works with your organization toplan, and set up your system. Accurate operationalrequirements are needed to ensure a successfulsystem plan. By properly configuring the DimetraIP system to meet your operational needs, yourorganization will have the most efficient and effectivecommunications system available.

PerformanceManagement

This manual provides an overview of PerformanceManagement features. By monitoring theperformance of the system, you can identify potentialproblems before they occur as well as adjust systemresources to provide optimum performance.

Dynamic Reports This manual describes Dynamic Reports which is aPrivate Radio Network Management (PRNM) Suiteapplication that provides predefined report templatesyou can use to display statistics for a zone, site or aconsole site (but not for a system) in near real time.

Historical Reports This manual describes Historical Reports which is aPrivate Radio Network Management (PRNM) Suiteapplication that allows you to generate reports forsystem-wide activity and for individual zones. Thesereports display data that is stored on the server. TheHistorical Reports application generates reports ofstatistical data that is gathered at specific, predefinedtime intervals. You can then create reports from thisdata to monitor and analyze information about zones,sites, channels, talkgroups, and users.

A-6 - March 2012

Appendix A Dimetra IP System Documentation

Table A-1 List of Dimetra IP System Documentation (cont'd.)

Document Title Description Dimetra IPScalable

Dimetra IPCompact/ScalableDimetra IP

InfoVista This manual describes InfoVista™ which is acustomizable performance management applicationthat is part of the Transport Network Management(TNM) application suite. InfoVista interfaces with,and gathers data from, multiple network devicessupporting Simple Network Management Protocol(SNMP) including master site routers, EthernetLAN switches, and WAN switches. The InfoVistaclient application is used to access server softwareand perform administrative tasks such as startingand stopping existing reports, adding an instance, orcreating a new report.

Security Management This manual provides a security overview for theDimetra IP system. Attacks on communicationsnetworks could interrupt mission critical operations,compromise classified or restricted information, andcontribute indirectly to loss of lives. The manualpresents an overview of the security applicationusers, describes the security groups and applications,and describes how to configure and optimize theapplications for secure operation.

Agency Priority Matrix(APM)

This manual describes the Agency Priority Matrixwhich is a feature used for controlling whichtalkgroups or radio users can be assigned to each RFchannel resource in the system. The manual describeshow to configure, operate, maintain, and troubleshootthe Agency Priority Matrix.

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

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

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

- March 2012 A-7

System Overview

Table A-1 List of Dimetra IP System Documentation (cont'd.)

Document Title Description Dimetra IPScalable

Dimetra IPCompact/ScalableDimetra IP

MultiCADI This manual describes the Computer AidedDispatch Interface (CADI) which is a server andan Application Programming Interface (API)that provide the capability for systems externalto the Dimetra IP SwMI to obtain informationabout, and exert some control over, radios. TheCADI API enables third parties to write softwareapplications called CADI clients that can receiveevents from, and submit commands to, the DimetraIP SwMI. Multi-Computer Aided Dispatch Interface(MultiCADI) is a server and an API, which enablesthird parties to develop application programs thatcan utilize the facilities provided by the CADI in theDimetra IP system. The MultiCADI API builds uponthe CADI API, but provides additional capabilities.

Telephone Interconnect This manual provides the information necessaryto install, configure, operate, and maintain thecomponents in a Telephone Interconnect subsystem.The Telephone Interconnect subsystem provides aninterface between the Dimetra IP radio network andan external telephone network, allowing telephoneinterconnect calls to be made between Dimetra IPradios and external telephones.

Active Directory/DomainName Services

This manual describes Active Directory (AD) whichis the service that provides access to enterprise-widedata and improved integration with the rest of theradio system. The manual contains procedures forinstallation and configuration of software necessaryto make Active Directory operational. It also containsprocedures for adding users and groups, and forbackup and restore of Active Directory.

TESS Software UserGuide

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

Transport NetworkConfiguration Tool(TNCT)

This manual describes the Transport NetworkConfiguration Tool (TNCT), which allows you todeploy previously prepared configurations to networkdevices. It also allows for tasks such as: rebootingdevices, uploading firmware, checking firmwareversion, configuration backup and restore, checkingdevice connectivity.

Alphanumeric TextService (ATS)

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

A-8 - March 2012

Appendix A Dimetra IP System Documentation

Table A-1 List of Dimetra IP System Documentation (cont'd.)

Document Title Description Dimetra IPScalable

Dimetra IPCompact/ScalableDimetra IP

Backup/Restore CollectorApplication User Guide

This manual describes the Backup/Restore Collectorapplication which provides a simple way of fetchingbackup files from a group of the Dimetra IP networkelements via FTP. The network elements can beconfigured to run scheduled backups and store thesebackups on local disk – typically during the nightwhen there is a smaller load of the system. The roleof the Backup/Restore application is to collect thesefiles and provide a centralized point of storage forthem. The backup files are accessible by FTP forcollection either manually or from a server runningan automated procedure. The files can be restoredfrom their centralized storage location back to thenetwork elements.

UCS Synchronization ToolManual

This manual describes the User ConfigurationServer (UCS) Synchronization Tool, which providesautomated intercluster configuration of some ofthe UCS objects that require to be registered in allclusters in a multicluster system.

Local Gateway Trunking This manual describes the local gateway trunkingfunctionality, its operational aspects, and itsconfiguration.

Dimetra EnhancedSoftware Update UserGuide

This manual describes the Dimetra EnhancedSoftware Update feature, which provides backup andrestore functionality, and upgrade functionality.

Authentication andProvisioning

This manual describes the installation andconfiguration of the Authentication Centre (AuC)and the Provisioning Centre (PrC). The manualcovers hardware installation and configuration ofthe Authentication Centre server, , AuthenticationCentre CryptR, modem and cabling. It also describeshow to install and configure all software for theAuthentication Centre and the Provisioning Centre.

Managing Authentication,Encryption andProvisioning

This manual describes management of theauthentication and air interface encryption featureoption in the Dimetra IP system including:

• Processes and procedures for managing operationof the authentication and air interface encryptionfeature

• Description of the authentication and air interfaceencryption features

• Discussions for handling compromised radios

• Discussion on planning and implementing yoursecurity policy

• Processes and procedures for managing encryptionkeys in the system infrastructure

- March 2012 A-9

System Overview

Table A-1 List of Dimetra IP System Documentation (cont'd.)

Document Title Description Dimetra IPScalable

Dimetra IPCompact/ScalableDimetra IP

• Description of the different aspects of secureencryption key management

Provisioning Centre UserManual

This manual describes how to use the ProvisioningCentre (PrC) application. The main functions of theProvisioning Centre are:

• Providing secure (encrypted) storage of radio keys

• Providing secure upload and download facilitiesfor radio keys and key data

• Displaying up-to-date information about the keystatus of the radios

• Exporting K-Ref data to permanent storage media

• Generating audit trail and radio information.

Clear Provisioning CentreUser Manual

This manual describes how to use the ClearProvisioning Centre (PrC) application. The mainfunctions of the Provisioning Centre are:

• Providing secure (encrypted) storage of radio keys

• Providing secure upload and download facilitiesfor radio keys and key data

• Displaying up-to-date information about the keystatus of the radios

• Exporting K-Ref data to permanent storage media

• Generating audit trail and radio information.

Secure Voice, Data andKey Management

This manual provides information on hardware,software and system operation, including proceduresfor 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 DispatchConsole

This manual describes all necessary actions to install,configure and maintain the MCC 7500S consolesubsystem. The subsystem allows two-way consoleand radio - console transmissions to be encryptedand secure.

A-10 - March 2012

Appendix A Dimetra IP System Documentation

Table A-1 List of Dimetra IP System Documentation (cont'd.)

Document Title Description Dimetra IPScalable

Dimetra IPCompact/ScalableDimetra IP

MCC 7500S ICCSGateway

This manual describes installation, configuration,operation, maintenance and troubleshooting ofthe components in a secure Integrated Commandand Control System (ICCS) gateway including thePyramid PC and the multiplexer. The ICCS GatewaySubsystem is a type of MCC 7500 console site,designed to meet the demands of customers, whowant to implement or already have implementedtheir own custom-developed Integrated Commandand Control System, that is, a non-Motorola controlroom. This manual describes also the ICCS GatewayDiscreet Listening feature on the Dimetra IP system.

CryptR and Audio Modulefor Replay

This manual describes installation, configuration,operation, maintenance and troubleshooting of AudioModule used for replay purposes and configurationof CryptR used for call logging. Together with theAIS and third party replay devices they are part of theEnd-to-End Encryption Call Logging Subsystem.

End-to-End Secure PacketData and Short Data

This manual describes configuration and operationof the End-Two-End Encryption (E2EE) feature forshort and packet data (SD, PD) on the Dimetra IPsystem.

Network Security This manual describes all necessary actions to install,configure and maintain the network security featurewithin the Dimetra IP system. The intention of themanual is to enable the reader to deploy the bestpossible level of security, which will protect thesystem against viruses, unauthorized authenticationor attacks of hackers. The network security featureprovides virus protection, authentication, and firewallprotection.

End-to-End EncryptionKVL3000 Plus User Guide

This manual describes how to configure the KVL3000 Plus for initial use, and entering and storingencryption keys in to target devices, such as radios,CryptRs and Mobile CryptRs.

Air Interface EncryptionKVL3000 Plus User Guide

This manual describes how to configure the KVL3000 Plus for initial use, and entering and storingencryption keys in to target devices, such asradios and others in connection with Air InterfaceEncryption.

CryptR InstructionManual

This manual covers hardware installation, mainend-user operations and a proper maintenance ofa range of devices based on the CryptR hardwareplatform.

- March 2012 A-11

System Overview

Table A-1 List of Dimetra IP System Documentation (cont'd.)

Document Title Description Dimetra IPScalable

Dimetra IPCompact/ScalableDimetra IP

MCC 7500 Console Sites This manual describes the hardware and softwarecomponents associated with the MCC 7500 DispatchConsole. It provides overviews of subsystemfunctions such as communications with the ZoneController, different types of call setups, anddescriptions of status and events. The manualalso provides detailed procedures for installation,configuration, and maintenance.

MCC 7500C DispatchConsole

This manual describes the hardware and softwarecomponents associated with the MCC 7500CDispatch Console. It provides procedures forinstalling the MCC 7500 Elite Admin and MCC 7500Elite Dispatch software, and it provides an overviewof MCC 7500 accessories.

MCC 7500 ArchivingInterface Server

This manual provides an introduction to the hardwareand software components associated with the MCC7500 Archiving Interface Server. Included aredetailed procedures for installation, configuration andoperation of the server.

MCC 7500 DispatchCommunications Server

This manual describes the MCC 7500 DispatchCommunications Server. Included are detailedprocedures for installation, configuration andoperation of the server.

MCC 7500 RemoteDispatch Console

This manual provides a high level technical overviewof the Remote Dispatch Console product and givesdetailed procedures for its installation, configurationand maintenance.

MCC 7500 DiscreetListening

This manual describes Discreet Listening, which isa feature that enables real-time listening into one toone calls involving a specific radio user. Listeningis possible for calls inside the Dimetra IP systemor through telephone interconnect to an ordinarytelephone. Using the Discreet Listening feature, auser is able to listen to calls involving the radio userwithout either of the calling parties knowing aboutit. The manual describes both the hardware andsoftware used for the Discreet Listening feature, andit describes how to install, configure, and operatethe system.

MCC 7500 AnalogConventional Operation

This manual provides an introduction to the hardwareand software components associated with the analogconventional feature of the MCC 7500 DispatchConsole. The manual contains detailed proceduresfor installation, configuration and optimization.

A-12 - March 2012

Appendix A Dimetra IP System Documentation

Table A-1 List of Dimetra IP System Documentation (cont'd.)

Document Title Description Dimetra IPScalable

Dimetra IPCompact/ScalableDimetra IP

MCC 7500 BandwidthManagement

This manual provides an introduction to thebandwidth management, which is necessary in anMCC 7500 console subsystem to ensure efficienttransport for the services in your system (voicecalls, data service and so on). Included aredetailed descriptions and procedures for operation,optimization and troubleshooting.

MCC 7500 ConsoleInteroperability

This manual provides a technical overview andtroubleshooting information for the interoperabilityfeature. Console interoperability is the term for aradio system that supports call traffic involving boththe CENTRACOM Gold Series and Motorola MCC7500 dispatch consoles.

MCC 7500 Elite AdminSoftware User Guide

This manual describes the MCC 7500 Elite Adminsoftware. The software creates a virtual desktopon the screen where resources that are part of thedispatch system are displayed graphically. Resourcesare grouped into folders, and one or more folders arestored as a configuration. The system administratoruses the Elite Admin software to set up configurationsfor the Elite Dispatch desktops that organizeresources to meet specific user needs.

MCC 7500 Elite DispatchSoftware User Guide

This manual describes the Motorola MCC 7500Elite Dispatch application which enables consoledispatchers to communicate with radio resources.

MCC 7500 EmergencyBeacon User Guide

This manual describes how to install, configure,operate, and test an emergency beacon installed on aconsole.

MCC 7500InternationalizationProcess User Guide

This manual describes how to generate the translatedtext (appropriate to the target country or region) usingthe Internationalization Package. The translated textis generated for the following MCC 7500C/MCC7500S products:

• Elite Dispatch, Elite Admin, Emergency Beacon,and Discreet Listening applications.

• Elite Dispatch, Elite Admin, Emergency Beacon,and Discreet Listening online help files.

RF Sites

MTS 1: Installation,Configuration, and BasicService Manual

This manual describes all necessary actions to install,configure and maintain the Motorola TransceiverStation 1 (MTS 1) within the Dimetra IP System.

MTS LiTE, MTS 2, andMTS 4: Installation,Configuration, and BasicService Manual

This manual describes all necessary actions to install,configure and maintain the Motorola TransceiverStation 2 and 4 (MTS 2 and MTS 4) within theDimetra IP System.

- March 2012 A-13

System Overview

Table A-1 List of Dimetra IP System Documentation (cont'd.)

Document Title Description Dimetra IPScalable

Dimetra IPCompact/ScalableDimetra IP

MTS Man MachineInterface Commands

This manual describes the Man-Machine Interfacecommands used to test and configure MTS sites.

EBTS: Installation,Configuration, and BasicService

This manual describes all necessary actions toinstall, configure and maintain the Enhanced BaseTransceiver Systems (EBTS) within the Dimetra IPSystem.

MBTS: Installation,Configuration, and BasicService

This manual describes all necessary actions to install,configure and maintain the Mini Base TransceiverSystems (MBTS) within the Dimetra IP System.

Customer Specific Manuals

Cluster Hot Standby(CHS) Tools

This manual describes installation, configuration, andusage of the Cluster Hot Standby (CHS) Tools. CHSTools are used to synchronize active and fallbackclusters configurations and detect any discrepanciesbetween 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 describes installation and maintenance ofthe Dimetra IP Compact/Scalable Dimetra IP system.The information covers the major components of thesystem and the interconnection of components in theMobile Switching Office (MSO).

Managing Radio Users,Radios, Talkgroup QuickReference Guide

This manual describes the most common day today tasks related to the management of radio users,radios, and talkgroups.

Managing theInfrastructure QuickReference Guide

This manual describes the three most commonapplications to use when monitoring and doingbasic troubleshooting of your system: Unified EventManager (UEM), ZoneWatch and Radio ControlManager (RCM). The guide gives a quick overviewof the most common day to day tasks and activities.

Network ConfigurationTool (NCT) Express

This manual describes the Network ConfigurationTool (NCT) Express, which allows you to deploypreviously prepared configurations to networkdevices. It also allows for tasks such as: rebootingdevices, uploading firmware, checking firmwareversion, configuration backup and restore, checkingdevice connectivity.

Online Help

Application LauncherOnline Help

This online help describes how to operate theApplication Launcher software.

A-14 - March 2012

Appendix A Dimetra IP System Documentation

Table A-1 List of Dimetra IP System Documentation (cont'd.)

Document Title Description Dimetra IPScalable

Dimetra IPCompact/ScalableDimetra IP

Unified Event Manager(UEM) Online Help

This online help describes how to operate the UnifiedEvent Manager application. It also covers detailedinformation on all system alarms and events.

ZoneWatch Online Help This online help describes how to operate theZoneWatch application.

System and Zone ProfileOnline Help

This online help describes how to operate the Systemand Zone Profile applications.

User ConfigurationManager (UCM) OnlineHelp

This online help describes how to operate the UserConfiguration Manager application.

Zone ConfigurationManager (ZCM) OnlineHelp

This online help describes how to operate the ZoneConfiguration Manager application.

Software DownloadOnline Help

This online help describes how to operate theSoftware Download application.

Affiliation Display OnlineHelp

This online help describes how to operate theAffiliation Display application.

ATIA Log Viewer OnlineHelp

This online help describes how to operate the ATIALog Viewer application.

Radio Control Manager(RCM) Online Help

This online help describes how to operate the RadioControl Manager application.

Radio Control Manager(RCM) Reports OnlineHelp

This online help describes how to operate the RadioControl Manager Reports application.

Dynamic Reports OnlineHelp

This online help describes how to operate theDynamic Reports application.

Historical Reports OnlineHelp

This online help describes how to operate theHistorical Reports application.

Authentication CentreOnline Help

This online help describes how to operate theAuthentication Centre application.

Key Management Facility(KMF) Online Help

This online help describes how to operate the KeyManagement Facility applications.

BTS Service Software(TESS) Online Help

This online help describes how to operate the BTSService Software.

MCC 7500 Elite DispatchSoftware Online Help

This online help describes how to operate the MCC7500 Elite Dispatch software.

MCC 7500 Elite AdminSoftware Online Help

This online help describes how to operate MCC 7500Elite Admin software.

MCC 7500 EmergencyBeacon Online Help

This online help describes how to operate MCC 7500Emergency Beacon software.

MCC 7500 DiscreetListening Online Help

This online help describes how to operate the MCC7500 Discreet Listening software.

- March 2012 A-15